Cisco Cisco Prime Unified Operations Manager 8.7 White Paper
All contents are Copyright © 1992–2006 Cisco Systems, Inc. All rights reserved.
Page 18 of 112
Step 6
In the dialog box, under Community Information, provide a community name.
Step 7
Select the SNMP version by selecting the radio box for SNMP v1 or SNMP
v2c.
v2c.
Step 8
(Optional) Enter one or more IP addresses in the IP Address field (containing
"dots") and click Insert to enable access solely for this community from the
NMS with the IP address provided.
"dots") and click Insert to enable access solely for this community from the
NMS with the IP address provided.
Step 9
Click Save.
The community name appears in the Configured Communities section at the top of the
dialog box.
Note: You can remove the community name by highlighting the name in the Configured
Communities section and clicking Remove Community. Changes become effective after
you click OK.
3.1.5 Cisco CallManager
The following configuration options on the Cisco CallManager need to be configured for
Operations Manager to discover and manage the Cisco CallManager. Failure to do so
may result in incomplete monitoring of the Cisco CallManager and cause some features
in Operations Manager to behave inconsistently,
Operations Manager to discover and manage the Cisco CallManager. Failure to do so
may result in incomplete monitoring of the Cisco CallManager and cause some features
in Operations Manager to behave inconsistently,
3.1.5.1 HTTP Credentials
Operations Manager uses the AVVID XML Layer (AXL) API in addition to SNMP to
manage Cisco CallManager. This means that Operations Manager will make SOAP calls
over HTTP through the AXL interface to collect fault and performance information from
the Cisco CallManager. Operations Manager needs an HTTP username/password to
execute these queries. When you add or discover a Cisco CallManager with Operations
Manager, you must supply a username/password or that Cisco CallManager will enter the
partially monitored state (see section 5.3.3, Device Discovery Process). The
username/password do not need to be administrator credentials. Any set of credentials
with read level access that will get authorized for the URL
manage Cisco CallManager. This means that Operations Manager will make SOAP calls
over HTTP through the AXL interface to collect fault and performance information from
the Cisco CallManager. Operations Manager needs an HTTP username/password to
execute these queries. When you add or discover a Cisco CallManager with Operations
Manager, you must supply a username/password or that Cisco CallManager will enter the
partially monitored state (see section 5.3.3, Device Discovery Process). The
username/password do not need to be administrator credentials. Any set of credentials
with read level access that will get authorized for the URL
http://server-name/ccmadmin
will
suffice.
3.1.5.2 HTTPS Configuration and Security Certificates
Cisco CallManager 4.1 or later supports enabling Secure Socket Layers (SSLs) on virtual
directories. If you intend to secure the communication between Operations Manager and
Cisco CallManager, you will need to enable SSL on the Cisco CallManager and
specifically certain virtual directories.
directories. If you intend to secure the communication between Operations Manager and
Cisco CallManager, you will need to enable SSL on the Cisco CallManager and
specifically certain virtual directories.
• CCMApi: Operations Manager uses services in this virtual directory to perform
AXL/SOAP database queries.
• SOAP: Operations Manager uses services in this virtual directory to perform
AXL/SOAP device queries.