Cisco Cisco Unified Operations Manager 8.5 White Paper
Deployment Guide
© 2010 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 26 of 65
Task Number
Task Description
Pass/Fail Result
5
Confirm that network firewall security allows proper connectivity
6
Add the voice gateway to Operations Manager
Cisco 1040 Sensor
1
Configure the DHCP scope to provide Option 150 with the IP address of the TFTP server
2
Connect Port 1 to a port configured for a single VLAN
3
Connect Port 2 to the SPAN port on the switch
4
Add the 1040 Sensor to Service Monitor
5
Copy the 1040 Sensor image file on the TFTP server
6
Copy the 1040 Sensor configuration file to the TFTP server
7
Add the 1040 Sensor to Service Monitor
Cisco IP Phones
Confirm that all phones were discovered automatically when the Communications Manager server
was added
was added
Note: Cisco has observed network ACLs preventing Operations Manager from accessing phones
over HTTP. This causes IP phone reporting issues.
over HTTP. This causes IP phone reporting issues.
Catalyst Switch
Configure SNMP ACL to allow Operations Manager servers
Configure SNMP on the switch
Configure NTP
Verify that Cisco Discovery Protocol is enabled
Add the LAN switch to Operations Manager
Operations Manager Installation
Preinstallation Checks
●
Dual homing (dual network interface card [NIC]), using two different IP addresses, is not supported on
Operations Manager. If, during installation, you receive a warning message to edit a file named
gatekeeper.cfg, then your server is dual homed, and you must disable one of the NIC interfaces before
adding any devices to Operations Manager. Using two NICs with a single IP address (a failover configuration,
in case one of the NICs fails) is supported.
●
If you are using an IBM server, make sure that the Windows service ibm director wmi cim server is stopped
and changed to Manual before installation. The installation program checks whether the cim server is running
at the start of the installation process. If the service is running, the installation program displays the error
message and stops.
●
.Net service disturbs some Operations Manager processes causing them not to operate normally. We
recommend that you uninstall .Net service from the system before installing Operations Manager.
●
Make sure that IIS is disabled before installation. If IIS is enabled when the installation program starts, the
installation program displays an error message and stops.
●
Make sure that you change the default Cisco Unified Communications Manager cluster ID setting (accessed
from Communications Manager Administration > Enterprise parameters).
The default setting is
StandAloneCluster
. Unless this entry is changed, all of the clusters will have the
same cluster ID. This will result in problems in Operations Manager. Changing the cluster ID requires a
restart of the CCMadmin service on all nodes. Perform these restarts on the publisher and then on the
subscribers.
Note:
If Operations Manager is already managing the Cisco Unified Communications 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