Cisco Cisco Prime Unified Operations Manager 8.7 Libro bianco
All contents are Copyright © 1992–2006 Cisco Systems, Inc. All rights reserved.
Page 19 of 112
Note: SSL is not enabled on the CCMApi and Soap virtual directories, by default. For
information on enabling SSL (using Windows Internet Information Services (IIS), see
Cisco CallManager Security Guide for the appropriate release of Cisco CallManager.
Also see the Using Device Manager chapter in User Guide for Cisco Unified Operations
Manager.
information on enabling SSL (using Windows Internet Information Services (IIS), see
Cisco CallManager Security Guide for the appropriate release of Cisco CallManager.
Also see the Using Device Manager chapter in User Guide for Cisco Unified Operations
Manager.
Enabling HTTPS on Cisco CallManager
Step 1
On the Cisco CallManager system, select Administrative Tools > Internet
Services Manager.
Services Manager.
Step 2
Click the server that is displayed.
Step 3
Right-click the Virtual directory (Soap and CCMApi) and click Properties.
Step 4
Go to the Directory Security tab and under Secure Communications, click Edit.
Step 5
In the dialog box, select the Require SSL check box and click Apply.
Note: If this procedure does not work, you might need to restart IIS service from the
Control Panel.
3.1.5.3 Cluster Name of a Cisco CallManager Cluster
Operations Manager relies on the cluster name 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 name,
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 name of these Cisco
CallManagers so that they have different names.
To change the cluster name of a Cisco CallManager, do the following:
uniquely identify and manage the Cisco CallManager deployment. Therefore, if two
Cisco CallManager deployments belonging to different clusters have the same name,
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 name of these Cisco
CallManagers so that they have different names.
To change the cluster name of a Cisco CallManager, do the following:
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.
Enterprise Configuration page is displayed.
Step 3
In the Cluster ID field, enter a new cluster name. The default is
StandAloneCluster. This should be changed so it is unique for every cluster.
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 (of voice). To minimize disruption, be sure to schedule this task for a
time when system maintenance is being done.
If OM is already managing the Call Manager and you are changing the cluster name, then
the cluster names in the Service Level View will not reflect the new cluster name. You
have to delete and readd the CMs in OM again for it reflect the new cluster name.