Cisco Cisco Unified Operations Manager 8.0 White Paper
© 2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 8 of 70
Preparing Devices to Be Monitored by Operations Manager
For Operations Manager to manage and monitor devices successfully, the following conditions should be met:
●
SNMPv3 credentials
1
or SNMPv2 read community string must be configured on each device.
●
SNMPv2 write community string must be configured on each device (needed only for certain routers and
switches on which IP service-level agreement, or 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 devices for Cisco IOS and Cisco
Catalyst devices.
●
IP connectivity must be verified between the devices and the Operations Manager server.
●
For Cisco IOS and 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
Cisco Discovery Protocol should be enabled on all the Cisco devices.
●
If Cisco Discovery Protocol is disabled (WAN interfaces usually have Cisco Discovery Protocol disabled),
use the ping sweep option. Make sure that you can ping the device from the Operations Manager server.
Cisco IOS Devices
This section describes the steps that should be performed to set up Cisco IOS devices for network management.
Note:
All steps may not be required, and some steps can be expanded with more functionality.
After performing these steps, save the configuration to nonvolatile random-access memory (NVRAM) by using one
of the following commands:
write memory
or
copy running-config startup-config
SNMPv2 Community Strings
Operations Manager can use SNMPv2 read community strings to retrieve fault and performance information from
the devices. Some of the features in Operations Manager (node-to-node tests, Survivable Remote Site Telephony
[SRST] monitoring, and phone status tests) also require SNMP write community strings to configure IP SLA
(formerly known as the Service Assurance Agent) on certain devices.
If you intend to use these features, be sure to configure SNMP write community strings on these devices. All
SNMP community strings must match on the devices and in the Operations Manager default credentials
repository.
To configure SNMPv2 community strings on a Cisco IOS device, use the following global configuration
commands:
snmp-server community <read-community-string> RO
snmp-server community <write-community-string> RW
1
Operations Manager supports SNMPv1, SNMPv2c, and SNMPv3AuthNoPriv mode. SNMPv3 support for AUTH=None is not
present in Operations Manager. Due to this condition, Operations Manager cannot be used with devices having SNMPv3,
AUTH=None.
AUTH=None.