Cisco Cisco Unified Operations Manager 8.5 White Paper
Deployment Guide
© 2010 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 32 of 65
The self-signed certificates are present in the Master and Slave based on the information provided during
Certificate Setup. Certificate Setup is accessed from Administration > Server > Security > Single Server
Management > Certificate Setup. (Set up with Hostname/DNS name as Resolvable DNS Name while
entering the information in Certificate Setup.)
Step 3. Restart the daemons in both machines.
Step 4. Add the certificates from Master to Slave and vice versa.
You can do this through Peer Server Certificate Setup, accessed from Administration > Server > Security
> Multi-Server Trust Management > Peer Server Certificate Setup.
Step 5. In the Master, go to Administration > Device and Credentials > Administration > Mode Settings, and
set it in the Master mode.
Step 6. In the Slave, go to Administration > Device and Credentials > Administration > Mode Settings and set
it in the Slave mode and add the Master’s Hostname.
Manual Device Import
To add one or more devices individually into Operations Manager, go to Administration > Device Management >
Device Configuration > Device Selection. On the Device Selection page, you can add a single device at a time
into the system. Make sure that the Cisco Remote Serviceability Kit (RSK) is installed on all Cisco Unity and Cisco
Unity Connection servers.
Device Discovery Process
Device States
●
Monitored: The device has been successfully imported and is fully managed by Operations Manager. All
devices should be in the Monitored state.
●
Partially Monitored: The Cisco Unified Communications Manager has been successfully imported in
Operations Manager, but only using SNMP. If a device is in this state, you should check the HTTP credentials
and make sure that the device becomes fully monitored. HTTP credentials are needed for Cisco Unified
Communications Manager and Cisco Unified Presence Server.
●
Monitoring Suspended: Monitoring of the device is suspended.
●
Inventory Collection in Progress: Operations Manager is probing the device. This is the initial state, when the
device is first added. A device is also in this state during periodic inventory collection. Some of the data
collectors may still be gathering device information.
●
Unreachable: Operations Manager cannot manage the device. This can occur if the device cannot be pinged,
if SNMP service is not enabled, or if the R/O community string provided is incorrect, SNMP may be blocked.
●
Unsupported: The device is not supported by Operations Manager. IP phones discovered using a ping sweep
will be placed into this category.
The blue number in the Number of Devices column is a hyperlink that brings up device information.
You can determine the reason why a device is unreachable on the Modify/Delete Devices page (Administration >
Device Management > Device Configurations > Modify/Delete Devices). In the Modify/Delete Devices page,
open the All Unreachable devices (or Unsupported) folder. Click the device name/IP address (not the check box).
The Data Collector Status Information section provides a detailed error code.