Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 
Community Member

CUOM 2.0 cluster question

We have a CCM 4.2 (4 CCM servers, 2 IPCC servers, 1 Unity and 1 CCC ) and CUCM 6.0 (1CCM, 1 IPCC server) cluster simultaneously used in our organization. The CUCM came in much later. Well, my question is when I added the 6x CallManager as a device to the CUOM for monitoring, it came up grayed.

My question however is that if 2 different CallManager Clusters can coexist on CUOM? we Have CUOM version 2.0

Cisco Employee

Re: CUOM 2.0 cluster question

Operations Manager relies on the Cluster ID of the Cisco CallManager cluster to uniquely identify and manage the Cisco CallManager deployment. Therefore, if two Cisco CallManager deployments belonging to different clusters have the same Cluster ID, Operations Manager cannot manage them as two distinct clusters.

Cisco CallManagers (starting with version 3) have a default cluster name of StandAloneCluster. If you are managing multiple Cisco CallManager deployments belonging to different clusters within the same Operations Manager, you will need to change the Cluster ID of these Cisco CallManagers so that they have unique names.

To change the Cluster ID of a Cisco CallManager, execute the following steps:

Step 1. Open the Cisco CallManager Administration page.

Step 2. From the menu, select System, and choose Enterprise Parameters. The Enterprise Configuration page is displayed.

Step 3. In the Cluster ID field, enter a new Cluster ID. The default is StandAloneCluster. This should be changed so it is unique for every cluster.

Step 4. Click Update.

You will need to restart the Cisco CallManager service and the RIS DB Monitor service for these changes to take effect. Restarting these Cisco CallManager services causes a service disruption (this is for voice services only). To minimize disruption, be sure to schedule this task for a time when system maintenance is being done.

If Operations Manager is already managing the Call Manager and you are changing the Cluster ID, then the Cluster IDs in the Service Level View will not reflect the new Cluster ID. You have to delete and re-add the CMs in OM again for it reflect the new Cluster ID.

From the OM Deplyment Guide:



Community Member

Re: CUOM 2.0 cluster question

CUCM 6.x is not supported in CUOM 2.0. CUCM 6.0 is supported in CUOM 2.0.1 and later. CUCM 6.1 is supported in CUOM 2.0.2 and later. The latest version is CUOM 2.0.3 and that is the latest maintenance image. They all use the same licenses as 2.0. Here are the compatibility guides for CUOM.

***Note that you cannot upgrade to CUOM 2.0.3 directly. You can only upgrade from 2.0.2 to 2.0.3.

CreatePlease to create content