Cisco Cisco Unified Operations Manager 8.0 White Paper

Page 11 of 112

3 Pre-Installation Tasks

This section describes the minimum configuration tasks that should be performed on
Cisco IOS

, Cisco Catalyst

®,

, and Cisco Media Convergence Server devices before

attempting to manage them using Operations Manager. It should be noted that this is not
an exhaustive configuration guide. Depending on the functionality required, further
device configuration may be required. For comprehensive information, see Performance
and Fault Management from Cisco Press as well as Cisco.com.

3.1

Preparing Devices to be Monitored By

Operations Manager

For Operations Manager to manage and monitor devices successfully, the following
conditions should be met:

• SNMP v3 credentials*, or SNMP v2 read community string must be

configured on each device.

• SNMP v2 write community string must be configured on each device (needed

only for certain Routers and Switches on which IP SLA tests will be
configured).

• IP SNMP access lists should include the IP address of the Operations Manager

server.

• The sysName of the device must be the same as the hostname of the for Cisco

IOS and Cisco Catalyst devices.

• IP connectivity must be verified between the devices and the Operations

Manager server.

• For Cisco IOS, Cisco Catalyst devices, one of the interface IP addresses must

be designated as the management IP address, and it should be defined as a
loopback IP address.

• If Operations Manager is going to discover the network through an automated

discovery process, then CDP should be enabled on all the Cisco devices.

• If CDP is disabled (WAN interfaces usually have CDP disabled), use the ping

sweep option. Ensure that you can ping the device from the Operations
Manager server.

* SNMP v3 has limited support in Operations Manager. The SNMP v3 support for AUTH=None is not
present in Operations Manager. Due to this condition, Operations Manager cannot be used with devices
having SNMP V3, AUTH=None.