Cisco Cisco Unified Operations Manager 8.6 White Paper

Page of 112
All contents are Copyright © 1992–2006 Cisco Systems, Inc.   All rights reserved. 
Page 29 of 112 
Step 7 
Restart the web service. (For the select root node, above Default Web Site, 
right-click and select Restart IIS
 
 
Note: For more information, see the Cisco CallManager Security Guide documentation. 
From OM version 1.1 onwards, the certificates will be import into OM automatically. 
During device addition, please enter HTTP credentials. OM does the rest. 
3.3.3 Check Routing and Firewalls 
Ensure that any firewalls between the Operations Manager server and the managed 
devices are configured to allow management traffic through. See Section 3.3.6 for 
information on which ports should be opened. 
Also, ensure that there is connectivity between devices to be managed and the Operations 
Manager server. Even if a route exists to a network behind a managed device, that does 
not mean that one exists to (and from) the device itself. 
3.3.4 Network Address Translation (NAT) 
Operations Manager has limited support for NAT environments. For Operations Manager 
to support devices behind a NAT firewall, ensure that you have both IP and SNMP 
connectivity to the NATted IP addresses from the Operations Manager server. You can 
verify this by using ping commands and using an SNMP MIB browser.  
Also, ensure that you do not have duplicate IP addresses across NAT domains that you 
are trying to manage with the same Operations Manager server. If overlapping IP address 
ranges exist, then you will need to dedicate different Operations Manager servers to 
manage these domains. 
3.3.5 Network Time Protocol 
To be able to correlate events across multiple devices, the devices need to have the same 
perception of the time. To achieve this, configure the Network Time Protocol (NTP) on 
the devices. For information on how to configure this functionality, refer to the Cisco 
device configuration documentation or 
http://www.cisco.com/univercd
. NTP is not