Cisco Cisco Prime Unified Operations Manager 8.7 白皮書
All contents are Copyright © 1992–2006 Cisco Systems, Inc. All rights reserved.
Page 32 of 112
4 Operations Manager Installation
4.1
Preinstallation Checks
• Dual homing (dual NIC), using 2 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 fail-over configuration, in case one of the NIC cards
fails) is supported.
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 fail-over configuration, in case one of the NIC cards
fails) is supported.
• Make sure that you change the default Cisco CallManager cluster ID setting (located
at CallManager Administration > Enterprise parameters). The default setting is Stand
Alone Cluster. Unless you change this entry, all of the clusters will have the same
cluster ID. This causes problems in Operations Manager. Changing the cluster ID
requires a restart of RIS Collector service, Windows SNMP service, and the
CCMadmin service. Perform these restarts on the publisher and then on the
subscribers.
Alone Cluster. Unless you change this entry, all of the clusters will have the same
cluster ID. This causes problems in Operations Manager. Changing the cluster ID
requires a restart of RIS Collector service, Windows SNMP service, and the
CCMadmin service. Perform these restarts on the publisher and then on the
subscribers.
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.
• Make sure that the Operations Manager server’s hostname is resolvable using DNS. If
DNS is not being used, edit the Windows hosts file and enter Operations Manager
hostname and IP address. The hosts file is located at
C:\Windows\system32\drivers\etc.
hostname and IP address. The hosts file is located at
C:\Windows\system32\drivers\etc.
# This file contains the mappings of IP addresses to hostnames. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding hostname.
# The IP address and the hostname should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
10.1.1.15
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding hostname.
# The IP address and the hostname should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
10.1.1.15
Operations Manager server.cisco.com # add the Operations Manager server IP address and
hostname entry into the hosts file if DNS is not being used on the network