Cisco Cisco Unified Operations Manager 8.0 White Paper
Operations Manager Deployment Best Practices
All contents are Copyright © 1992–2006 Cisco Systems, Inc. All rights reserved.
Page 89 of 112
8 Troubleshooting Tips
See the following sections:
• Section 8.1, Troubleshooting Notes
• Section 8.2, Common Issues
• Section 8.3, Frequently Asked Questions
• Section 8.2, Common Issues
• Section 8.3, Frequently Asked Questions
8.1
Troubleshooting Notes
• Do not place the Operations Manager server on a network restricting SNMP.
Check your SNMP access lists and make sure to enter the Operations Manager
server. Operations Manager requires SNMP v2 write community strings only to
configure the IP SLA for the node-to-node tests.
server. Operations Manager requires SNMP v2 write community strings only to
configure the IP SLA for the node-to-node tests.
• Do not place the Cisco 1040 on a network where DHCP is being monitored and
restricted. The MAC address of the Cisco 1040 may need to be entered into a
DHCP management system application for the Cisco 1040 DHCP to work. Check
the switch port configuration of the port that the Cisco 1040 is plugged into.
DHCP management system application for the Cisco 1040 DHCP to work. Check
the switch port configuration of the port that the Cisco 1040 is plugged into.
• The Cisco 1040 currently does not support CDP. Thus, make sure the Cisco 1040
is on a single VLAN; do not use auxiliary VLANs.
• Make sure to open ports on your firewall to allow the Cisco 1040 to be placed on
a demilitarized zone (DMZ).
8.2
Common Issues
Installation
1. What should one check before installing Operations manager?
A: Check the following before installing Operations Manager
• Make sure you have only one NIC card enabled on the box
• Critical: Check the time on the machine. If you change the time after CUOM
installation you may need to reinstall the OS to get CUOM to work.
• Ensure the IP Address to Machine name mapping in DNS and host name of
the local machine are the same
1. In the command prompt run nslookup <ipaddress>. This should show you
1. In the command prompt run nslookup <ipaddress>. This should show you
the hostname of the machine.
2. Run ipconfig /all and check the hostname and domain name. This should
be the same as what you obtained in nslookup
3. Finally from the command prompt run ping <hostname> where hostname
is the fully qualified name of the machine that you got from nslookup.