Installation Guide for Cisco Unified Operations Manager 2.3
Getting Started
Downloads: This chapterpdf (PDF - 368.0KB) The complete bookPDF (PDF - 1.65MB) | Feedback

Getting Started

Table Of Contents

Getting Started

Configuring Operations Manager to Monitor Devices

Understanding the DCR

Configuring the DCR in Master and Slave Mode

Adding Devices to the DCR

Configuring Operations Manager Physical Discovery

Configuring Credentials

Filtering Operations Manager Physical Discovery

Importing Devices Into the DCR

Configuring Automatic Device Selection in Operations Manager

Adding Devices Manually from the DCR to Operations Manager

Understanding Device States

Verifying Devices Added to Operations Manager using the Service Level View

Scheduling Inventory Collection

Editing the Device Inventory Collection Schedule

Adding a Phone Discovery Schedule

Troubleshooting Device Import and Inventory Collection

Understanding Inventory Collection Messages

Why Does a Device Go into the Partially Monitored State?

Why Does a Device Go into the Unreachable State?

Editing Device Configuration and Credentials

Modifying SNMP Timeout and Retries

Performing Manual Inventory Collection on Devices

Starting Operations Manager

Adding the Operations Manager Home Page to the Internet Explorer Trusted Site Zone

Adding Cisco Unified Communications Management Server Links from Operations Manager

Understanding and Configuring Security

Supported NMS Integration

Configuring SNMP Trap Receiving and Forwarding

Updating the SNMP Trap Receiving Port

Enabling Devices to Send Traps to Operations Manager

Enabling Cisco IOS-Based Devices to Send Traps to Operations Manager

Enabling Catalyst Devices to Send SNMP Traps to Operations Manager

Integrating Operations Manager Trap Receiving with NMSs or Trap Daemons

Configuring SNMP Trap Forwarding

Configuring Health Monitor

Configuring Cisco Unified Communications Manager for Use with Operations Manager

Configuring the Syslog Receiver on Cisco Unified Communications Manager

Activating Events in Operations Manager

(Optional) Configuring RTMT on Cisco Unified Communications Managers

Setting HTTP Credentials on Cisco Unified Communications Manager

Viewing Alerts

What's Next?


Getting Started


This section provides a minimum number of steps for setting up Cisco Unified Operations Manager (Operations Manager) and viewing diagnostic results. It includes:

Configuring Operations Manager to Monitor Devices

Starting Operations Manager

Adding Cisco Unified Communications Management Server Links from Operations Manager

Understanding and Configuring Security

Supported NMS Integration

Configuring SNMP Trap Receiving and Forwarding

Configuring Health Monitor

Configuring Cisco Unified Communications Manager for Use with Operations Manager

Viewing Alerts

What's Next?

Configuring Operations Manager to Monitor Devices

Operations Manager obtains devices to monitor from the CiscoWorks Common Services Device and Credentials Repository (DCR). The DCR is a common repository of devices and their credentials for use by individual applications.

For Operations Manager to monitor a device, it must first be added to the DCR. Once a device is added to the DCR, you can then add it to the Operations Manager inventory, which is separate from the DCR.


Note When Operations Manager is installed, it will automatically synchronize with the DCR and add inventory. This is the default setting.


You can add devices automatically from the DCR to Operations Manager by activating automatic synchronization (the default), or you can add them manually through the Device Selection page. For more information on how Operations Manager is affected by the DCR, see Understanding the DCR.


Note You should exclude the NMSROOT/databases directory from virus scanning. Problems can arise if database files are locked because of virus scanning.



Note NMSROOT is the directory where Operations Manager is installed on your system. If you selected the default directory during installation, it is C:\PROGRA~1\CSCOpx.


Table 3-1 lists some possible deployment scenarios for Operations Manager, and what you will need to do to add devices to Operations Manager inventory.

Table 3-1 Adding Devices to Inventory Scenarios 

Deployment Scenario
What to Do

Deploying Operations Manager as an independent server.

Automatically synchronizing your inventory with the DCR.

Add devices from the DCR using automatic synchronization. Automatic synchronization is the default setting, and you do not need to do anything.

If you have changed the synchronization setting from automatic, you will need to change it back. See Configuring Automatic Device Selection in Operations Manager.

Deploying Operations Manager as an independent server.

Manually controlling the devices that are added to inventory.

Manually add devices from the DCR. See Adding Devices Manually from the DCR to Operations Manager.

Deploying Operations Manager as an independent server.

You want to use automatic discovery, but not all the devices discovered through automatic discovery need to be managed in Operations Manager.

Add devices from the DCR using automatic synchronization.

Configure automatic synchronization to select devices based on parameters you set. See Configuring Automatic Device Selection in Operations Manager.

Deploying Operations Manager with CiscoWorks LAN Management Solution (LMS).

Using the Operations Manager DCR as the master DCR.

Automatically synchronizing your inventory with the DCR.

Set up the Operations Manager DCR as a master and the LMS DCRs as slaves. Configuring the DCR in Master and Slave Mode.

Run physical discovery. See Adding Devices to the DCR

Verify that automatic synchronization is configured in Operations Manager. See Configuring Automatic Device Selection in Operations Manager.

Deploying Operations Manager with LMS.

Synchronizing the Operations Manager DCR with an existing master DCR.

Automatically synchronizing your inventory with the DCR.

Set up the Operations Manager server DCR as a slave and one of the LMS DCRs as a master. Configuring the DCR in Master and Slave Mode.

Configure Operations Manager to add devices to a master DCR. See Adding Devices to the DCR.

Run physical discovery. See Adding Devices to the DCR

Verify that automatic synchronization is configured in Operations Manager. See Configuring Automatic Device Selection in Operations Manager.

Deploying Operations Manager with LMS.

Synchronizing the Operations Manager with an existing master DCR.

Manually controlling the devices managed by Operations Manager.

Set up the Operations Manager server DCR and the LMS server DCRs as slave and master. Configuring the DCR in Master and Slave Mode.

Configure Operations Manager to add devices to a master DCR. See Adding Devices to the DCR.

Run physical discovery. See Adding Devices to the DCR

Verify that manual synchronization is configured in Operations Manager. See Configuring Automatic Device Selection in Operations Manager.

Understanding the DCR

The Device and Credentials Repository (DCR) is a centralized device repository for sharing device information across applications. It provides a single place for managing device credentials and attributes, ensuring consistency across applications. Individual applications can query the DCR for a device list, device attributes, and device credentials. Changes to the DCR are propagated to applications that support the DCR, such as Operations Manager and LMS applications. (Service Monitor and Service Statistics Manager neither use nor support the DCR.)


Note A device must be added to the DCR before it can be added to the Operations Manager inventory (see Adding Devices to the DCR).


Once a device is added to the DCR, you can add it to the Operations Manager inventory (the Operations Manager inventory is separate from the DCR). When a device is added to the DCR, the DCR assigns a DCR ID to every managed component. The DCR maps components to devices using either the device name or the IP address. When the device is added to Operations Manager, Operations Manager maps the DCR ID to the device name during inventory collection.

Operations Manager also uses the DCR ID to verify whether the device or component already exists in the Operations Manager inventory. (Further information on how Operations Manager identifies devices—such as whether Operations Manager uses an IP address or DNS name as the device name—is provided in User Guide For Cisco Unified Operations Manager 2.3 or the online help.)

You can add devices automatically from the DCR to Operations Manager by activating automatic synchronization (which is the default), or you can add them selectively by deactivating using the Device Selection page. When a device is deleted it may or may not be deleted from the DCR. Deletion is determined by how Operations Manager is configured with the DCR (for details on deleting devices, see User Guide For Cisco Unified Operations Manager 2.3 or the online help).

The synchronization between the DCR and the Operations Manager inventory is controlled from the Device Selection page.

For automatic synchronization (this is the default), see Configuring Automatic Device Selection in Operations Manager.

For manual synchronization (in which you selectively add devices from the DCR to the Operations Manager inventory), see Adding Devices Manually from the DCR to Operations Manager.


Note Do not confuse the Operations Manager physical discovery process (which adds devices to the DCR) or the Operations Manager inventory collection process (which probes devices and updates components in Operations Manager inventory) with the DCR synchronization process. Operations Manager inventory collection is a process that affects only the Operations Manager inventory.


Configuring the DCR in Master and Slave Mode

By default, the DCR on the Operations Manager server is configured as a standalone or independent repository. If you decide to configure the DCR for Operations Manager as a master or a slave, the procedures for doing so are thoroughly documented in the CiscoWorks Common Services online help and in User Guide for CiscoWorks Common Services. (To access the CiscoWorks Common Services online help, from the Operations Manager home page, click the CiscoWorks link in the top right corner of the page. The CiscoWorks home page appears; click the Help button.)


Note Ensure that the versions of Operations Manager and Common Services are compatible before configuring the master and slave mode. See the Supported and Interoperable Devices and Software Table for Cisco Unified Operations Manager 2.3 for compatibility information.


You must perform prerequisite tasks and you must configure the master and the slave in the proper order. The following procedure can help you get started and locate the information you need in the online help.


Note To start Operations Manager, see Starting Operations Manager.



Step 1 From the Operations Manager home page, click the CiscoWorks link in the top right corner of the page. The CiscoWorks home page appears in another window.

Step 2 On the CiscoWorks home page, select Common Services > Device and Credentials > Admin. The Administration page appears.

Step 3 Select Mode Settings from the TOC in the left pane. The Mode Settings window appears.

Step 4 Click the Help link in the top right corner of the page. Find the instructions for completing the master-slave configuration prerequisites. These include:

Adding a peer server user on the system with the master DCR.

Creating a System Identity User on the system with the slave DCR.

Copying security certificates.

Follow the instructions in the online help to complete the prerequisites and to configure a master and a slave in the correct order.


Adding Devices to the DCR

Devices are added to the DCR through the Operations Manager Add Devices page (Devices > Device Management > Add Devices).


Note To add devices to the DCR using bulk import (importing from an NMS or from a file), see Importing Devices Into the DCR.



Step 1 Select Devices > Device Management > Add Devices. The Add Devices page appears.

Step 2 Enter the following:

IP address or hostname. Multiple devices can be entered at the same time, using a comma-separated list.


Note When adding multiple devices at the same time, all the devices must be the same type of device and use the same credentials.


Enter SNMPv2c/SNMPv1 credentials.

Enter SNMPv3 credentials.

Enter HTTP credentials (only required for Cisco Unified Communications Manager).

Windows credentials (only required for Windows-based MCS application servers).

Step 3 Click OK.


Configuring Operations Manager Physical Discovery


Step 1 Select Devices > Device Management > Auto-Discovery Configuration. The Auto-Discovery Configuration page appears.


Note You can also access the Discovery Configuration page from the Device Management: Summary page, by clicking the Configure button.



Note Discovery requires SNMP and/or SNMPv3 credentials. If the credentials are not configured, when you click Discovery Configuration, an empty Discovery Configuration page appears and you will only have the option of configuring credentials. Select the Credentials radio button, then click Add; the Configure Credentials page appears (see Configuring Credentials).


Step 2 If the Discovery radio button is not selected, select it.

Step 3 Do one of the following:

Select the Use Communications Manager or Cisco Discovery Protocol (CDP) check box, and do one of the following:

Enter seed devices using a comma-separated list of IP addresses.


Note When using a Cisco Unified Communications Manager as the seed device, the following types of devices are discovered:

    - Other Cisco Unified Communications Managers in the network
    - Cisco Unity
    - MGCP Voice Gateways
    - H.323 Voice Gateways
    - Gatekeepers
    - CTI applications configured with CTI ports on the discovered Cisco Unified      Communications Managers

    In addition to the Cisco Unified Communications Manager-based discovery, the following types of discoveries occur, resulting in additional devices being added to the inventory:
    - CDP-based discovery
    - ARP-based discovery
    - Route table-based discovery


Select the Use devices currently in the system check box.

Select a hop count.


Note Discovery may skip more than the number of hops selected. Discovery uses multiple technologies to discover devices, which may result in devices violating L2 or L3 hops. If you are using Hop count to limit discovery, an alternate way of achieving the same objective is to use the Include and Exclude filters from the Discovery Configuration page (see Filtering Operations Manager Physical Discovery).


or

Select the Use ping sweep check box. The seed devices and the ping sweep options can be used in an either/or mode.

When selecting the Use Ping Sweep check box, specify a comma-separated list of IP address ranges using the /netmask specification.

For example, use 172.20.57.1/24 to specify a ping sweep range starting from 172.20.57.1 and ending at 172.20.57.255.

Step 4 In the Run pane, configure when physical discovery should run.

If you want physical discovery to run immediately, select the now radio button.

If you want to schedule physical discovery to run at certain intervals, do one of the following:

Select daily; enter the time and select the days on which physical discovery should run.

Select the every radio button; choose how often you want physical discovery to run, enter the times between which you want it to run, and select the day on which it should run.

Step 5 Click OK.


Configuring Credentials

Discovery requires SNMP and/or SNMPv3 credentials. If the credentials are not configured when you try to configure discovery, you will only be able to access the Configure Credentials page. You must enter SNMP and/or SNMPv3 credentials before running discovery.


Step 1 Select Devices > Device Management > Auto-Discovery Configuration > Credentials. The Configure Credentials page appears.

Step 2 Click Add.


Note If you are changing the existing credentials for a device, select the target device and then click Edit. Using this edit option only allows you to change the credentials. If you want to change the target device, you must delete the entire row and then re-add all the details.


Step 3 Enter the following:

IP address or hostname. Multiple devices can be entered at the same time, using a comma-separated list.


Note When adding multiple devices at the same time, all the devices must be the same type of device and use the same credentials. If you are using wildcard entries, only the following formats are supported: *.*.*.* or 10.76.93.[39-43].


(Optional) Change the SNMP timeout and retries.

SNMPv2c/SNMPv1 credentials.

SNMPv3 credentials.

HTTP credentials (only required for Cisco Unified Communications Manager).

Windows credentials (only required for Windows-based MCS application servers).

Step 4 Click OK.


Filtering Operations Manager Physical Discovery

You can configure Operations Manager physical discovery to filter out devices. This is optional; it is not required to run physical discovery.


Step 1 Select Devices > Device Management > Auto-Discovery Configuration > Filters and Schedule. The Filters and Schedule page appears.

Step 2 Select the Filters radio button. Table 3-2 describes the optional filters that are available to you when running physical discovery.

Table 3-2 Physical Discovery Filters 

Filter
Description
IP Address

(Optional) Enter comma-separated IP addresses or IP address ranges for devices that you want to:

Include—In the auto-discovery process.

Exclude—From the auto-discovery process.

You can use wildcards when specifying the IP address range.

An asterisk (*) denotes the octet range of 1-255. Also, the octet range can be constrained using the [xxx-yyy] notation.

For example:

To include all devices in the 172.20.57/24 subnet in the auto-discovery process, enter an include filter of 172.20.57.*.

To exclude devices in the IP address range of 172.20.57.224 - 172.20.57.255 from the auto-discovery process, enter an exclude filter of 172.20.57.[224-255].

Both types of wildcards can be used in the same range specification; for example, 172.20.[55-57].*. If both include and exclude filters are specified, the exclude filter is applied first before the include filter. Once a filter is applied to an auto-discovered device, no other filter criterion will be applied to the device. If a device has multiple IP addresses, the device will be processed for auto-discovery as long as it has one IP address that satisfies the include filter.

DNS Domain

(Optional) Enter comma-separated DNS domain names for devices that you want to:

Include—In auto-discovery processing.

Exclude—From auto-discovery processing.

The DNS names can be specified using wildcards. An asterisk (*) matches any combination of mixed uppercase and lowercase alphanumeric characters, along with the hyphen (-) and underscore (_) characters, of an arbitrary length. A question mark (?) matches a single uppercase or lowercase alphanumeric character or a hyphen or an underscore character. For example:

*.cisco.com matches any DNS name ending with .cisco.com.

*.?abc.com matches any DNS name ending with .aabc.com, .babc.com, and so on.

SysLocation

(Optional) Enter comma-separated strings that will match the string value stored in the sysLocation OID in MIB-II, for devices that you want to:

Include—In auto-discovery processing.

Exclude—From auto-discovery processing.

The location strings can be specified using wildcards. An asterisk (*) matches, up to an arbitrary length, any combination of mixed uppercase and lowercase alphanumeric characters, hyphen (-), underscore (_), and, white space (spaces and tabs). A question mark (?) wildcard matches a single occurrence of any of the above characters. For example, a SysLocation filter of San * will match all SysLocation strings starting with San Francisco, San Jose, etc.


Step 3 Click Apply.


Importing Devices Into the DCR

For bulk import (from an NMS or from a file) Operations Manager provides you a direct link to the DCR (Devices > Device Management > Import Devices).


Step 1 Select Devices > Device Management > Import Devices. The CiscoWorks Common Services Import Devices page appears.

Step 2 Enter the import information.


Note If you need help importing, click the Help button on the page, and the Common Services online help opens.



Configuring Automatic Device Selection in Operations Manager

Operations Manager uses automatic synchronization by default. Use the following procedure to change manual synchronization to automatic synchronization.


Note If you are running the synchronization process for the first time, it may take several hours for Operations Manager to collect inventory for all of the devices, depending on how many devices are being added to Operations Manager.



Note Devices must exist in the DCR before you can add them to Operations Manager.



Step 1 Select Devices > Device Management > Device Selection. The Device Selection page appears.

Step 2 Activate the Automatic radio button.

Step 3 Click Apply. Operations Manager will be synchronized with the DCR; any DCR devices currently not in Operations Manager will be added. Operations Manager will perform inventory collection for the new devices that are being added.

Step 4 Verify whether any duplicate devices exist, by selecting Devices > Device Management > IP Address Report.


Note If you do not require the duplicate device for your deployment, remove it (for information on deleting devices, see User Guide For Cisco Unified Operations Manager 2.3 or the online help).



Adding Devices Manually from the DCR to Operations Manager

If Operations Manager is configured for automatic device selection, you do not need to perform this procedure. With manual device selection, you need to manually select devices to monitor. You will need to do this periodically after devices have been added to the DCR. For example, if you run Operations Manager physical discovery on a weekly basis, you should consider checking for new devices that you want to monitor after discovery completes.


Note Devices must exist in the DCR before you can add them to Operations Manager.



Step 1 Select Devices > Device Management > Device Selection. The Device Selection page appears.

Step 2 Select the Manual radio button. All devices that are not in Operations Manager inventory are available through the device selector.

Step 3 Select devices the following ways:

Entering device names or IP addresses in the Device Display Name, and clicking Filter.

Using the group selector.

Step 4 If you want to see the devices you have selected, click the Selection tab, and a list of devices appears.

Step 5 Click Select. Operations Manager will perform inventory collection on the devices that are being added.

Step 6 Verify whether any duplicate devices exist, by selecting Devices > Device Management > IP Address Report.


Note If you do not require the duplicate device for your deployment, remove it (for information on deleting devices, see User Guide For Cisco Unified Operations Manager 2.3 or the online help).



For more information, see User Guide for Cisco Unified Operations Manager 2.3.

Understanding Device States

The Device Management: Summary page lists the device states for all devices in the Operations Manager inventory. The Device Management: Summary page appears when you select Devices > Device Management.

Table 3-3 Device States 

State
Description

Monitored

The device has been successfully imported, and is fully managed by Operations Manager.

Partially Monitored

The device has been successfully imported by some of the data collectors1 in Operations Manager, but not all. If a device is in this state, you should take action to ensure that the device becomes monitored.

Monitoring Suspended

Monitoring of the device is suspended.

Inventory Collection in Progress

Operations Manager is probing the device. This is the beginning 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. See Troubleshooting Device Import and Inventory Collection.

Unsupported

The device is not supported by Operations Manager.

1 Data collector is a term used to refer to all back-end applications that are involved in device discovery and device data collection.

1 Table 3-4 displays the states that devices go through while they are being added to Operations Manager inventory, and what causes a device to go into a particular device state.


Table 3-4 Transition States of Devices when Being Added to Inventory 

Start Inventory Collection
Result of Inventory Collection
Resulting Device State

Inventory collection in progress.

Successfully discovered.

Monitored.

Inventory collection in progress.

Not all credentials were supplied or some services were down.

Partially Monitored.

Inventory collection in progress.

SNMP information is not configured.

Device is not responding.

Device is not reachable.

Device credentials are not correct.

Unreachable.

Inventory collection in progress.

The device model is not recognized.

The software version is not supported.

Unsupported


.

Verifying Devices Added to Operations Manager using the Service Level View

One way you can verify that your devices have been added to Operations Manager inventory is by looking at the Service Level View. This also provides you with quick access to many of the Operations Manager tools.

If you find that problems have occurred during inventory collection, see Troubleshooting Device Import and Inventory Collection.


Step 1 Select Monitoring Dashboard > Service Level View. The Service Level View display appears, displaying a logical topology view of your IP telephony implementation.


For more information, see User Guide for Cisco Unified Operations Manager 2.3 or the Operations Manager online help.

Scheduling Inventory Collection

There are separate inventory collection schedules for devices and phones. There is only one inventory collection schedule for devices. You cannot create additional schedules; you can only edit the existing schedule. For IP phones, you can create multiple inventory collection schedules.

On the Inventory Collection Schedule page (Devices > Device Management > Inventory Collection > Device), you can edit, suspend, or resume the device inventory collection schedule. (See Editing the Device Inventory Collection Schedule.)

On the IP Phone Discovery Schedule page (Devices  > Device Management  > Inventory Collection > IP Phone), you can add, edit, or delete the IP Phone discovery schedules. (See Adding a Phone Discovery Schedule.)

Editing the Device Inventory Collection Schedule


Step 1 Select Devices > Device Management > Inventory Collection > Device. The Device Inventory Collection page appears.

Step 2 Click Edit. The Inventory Collection Schedule: Edit page appears.

Step 3 Change the desired scheduling information.

Step 4 Click OK.

Step 5 Click Yes.


Adding a Phone Discovery Schedule


Step 1 Select Devices > Device Management > Inventory Collection > IP Phone Details. The IP Phone Discovery Schedule page appears.

Step 2 Click Add. The Add Schedule dialog box appears.

Step 3 Enter the following:

A name for the discovery schedule

The day of the week when you want discovery to occur

The time of the day when you want discovery to occur

Step 4 Click OK.


Troubleshooting Device Import and Inventory Collection

Problems might occur during physical discovery (Operations Manager adds devices to the DCR) and can also occur during inventory collection (Operations Manager adds devices to its inventory for monitoring).


Note If device inventory collection or discovery is being performed over a slow network connection, or if the devices are unusually slow in responding to SNMP or HTTP requests, you can change the ivr.properties file to prevent Operations Manager from timing out during discovery or inventory collection. The file is located in the NMSROOT/conf/ivr folder.

To increase the time allocated for discovery or inventory collection, change the property messageFactor:6 to messageFactor:10. The higher the number, the longer Operations Manager waits before timing out.


To troubleshoot device inventory collection, try the following:

If a device is not responding, confirm all device credentials and readd the device. See Editing Device Configuration and Credentials.

If device inventory collection times out for several devices, increase SNMP timeout settings. See Modifying SNMP Timeout and Retries.

View device error information on the Modify/Delete Device page. See Performing Manual Inventory Collection on Devices.

Verify that the device is operational during the import and that it supports MIB II.

Check the reason for devices being in the Unreachable state. See Starting Operations Manager.

After troubleshooting the problem, check the device status. See Verifying Devices Added to Operations Manager using the Service Level View.

The Modify/Delete Devices page displays device information and data collection information. You can use Modify/Delete Devices to determine the current state of a device and view data collection errors.


Step 1 Select Devices > Device Management > Modify/Delete Devices. The Modify/Delete Devices page opens.

Step 2 Expand the folder that contains your device (according to its inventory collection status; see Verifying Devices Added to Operations Manager using the Service Level View).

Step 3 Click the device name or IP address. The device information is populated.

Step 4 Look under Data Collection Status Information for error information (see Starting Operations Manager).

Step 5 Perform the required actions to clear the error.


Understanding Inventory Collection Messages

Table 3-5 lists messages that might be shown for devices that are in the Unreachable state.

Table 3-5 Inventory Collection Error Messages 

Message
Meaning
Action

SNMP Timeout

The device is in the Unreachable state because the SNMP read-only community string for the device is incorrect.

See Editing Device Configuration and Credentials to enter the correct read community string for the device.

Others: Missing IP Address or Data Collector Timeout

The device is in the Unreachable state because of some other reason. It could be that DNS resolution for the device failed or the data collector timed out.

Click the device on the Modify/Delete Devices page. The error message displays the exact problem.

If the IP address is missing:

Readd the device with the correct IP address.

or

Make sure that Operations Manager can resolve the device name: try adding the domain name as part of the device name.

If the data collector times out, restart the daemon manager to get all data collectors in sync.


Why Does a Device Go into the Partially Monitored State?

Table 3-6 explains the possible reasons for the error codes that you see in the Modify/Delete Devices page, that occur for partially monitored devices.

Why Cisco Unified Communications Manager May Go into the Partially Monitored State

If the incorrect HTTP credentials were entered for a Cisco Unified Communications Manager, it may go into the Partially Monitored state. When this occurs none of the Perfmon Counters are polled. To change device credentials, see Editing Device Configuration and Credentials.

If ports 135, 145, and 1025-65000 are not open in a firewall setup, Cisco Unified Communications Manager goes into the Partially Monitored state. Verify that these ports are open. If you need to open the ports, after doing so, rediscover the device.

Why Certain Voice Applications May Go into the Partially Monitored State

The following devices may go into the Partially Monitored state:

Cisco IP Contact Center

Cisco Unity Connection

Cisco Unity

Cisco Personal Assistant

If insufficient windows credentials are provided during the addition of these devices, they become partially monitored, and some of their WMI attributes are not polled. To change device credentials, see Editing Device Configuration and Credentials.

Table 3-6 Error Shown on the Modify/Delete Devices Page 

Error Shown on the Modify/Delete Devices Page
Reason
Resolution Steps

Error Code = CCM Authentication Failure

Error Message = Success:WrongCredentials

This message indicates that either Unified Communications Manager http credentials are not entered or the credentials provided are incorrect.

Verify that you provided the correct http credentials in the DCR by using the credentials to log in to the Cisco Unified Communications Manager Admin page, and rediscover the device.

Error Code= CCM Authentication Failure

Error Message= Success:UnknownCredentialError

This message indicates that SNMP management MIBs are not responding. The MIBs and their associated errors could be one of the following:

MIB-2—The ipAddressTable is not responding.

CISCO-CCM-MIB—The ccmTable is not responding. Specifically the ccmClusterId attribute is not responding.

Inventory collection could not find the ccmVersion detail. This may be because the ccmVersion attribute in the CISCO-CCM-MIB is not responding.

Restart the SNMP Agent on the system and rediscover the device.

Error Code = CCM Authentication Failure

Error Message = Success:WebServiceDown

Http service is not running or responding to requests from Operations Manager.

Verify that the web server is running by launching the Cisco Unified Communications Manager Admin page.

Check the firewall to see if it is blocking the HTTP/HTTPS connection between Cisco Unified Communications Manager and Operations Manager.

Error Code = CCM Authentication Failure

Error Message = Success: HTTPSCertificateNotImported

The Cisco Unified Communications Manager certificate has failed.

Do the following:

1. Check the file IPToHostName.txt in the CSCOpx\lib\jre\lib\security folder. It should contain an entry like the following:

deviceip>=<hostname> record for each 
of the ccm For e.g. 
10.76.91.115=blrsd1

2. Go to the keytool utility location <NMSROOT>\CSCOpx\lib\jre\bin.

3. Run the following command:

keytool -list -keystore 
<NMSROOT>\CSCOpx\lib\jre\lib\securit
y\cacerts

The downloaded certificates are displayed.

4. Verify that there is an entry similar to the following for the Cisco Unified Communications Manager:

Certificate fingerprint (MD5): 
AC:B6:94:A5:9C:17:E0:D7:91:52:9B:B1:
97:06:A6:E4 
cn=ct-sd, ou=nmtg, o=cisco systems, 
l=bangalore, st=Karnataka, c=in, Oct 
26, 200 5, trustedCertEntry

5. Rediscover the device.


Why Does a Device Go into the Unreachable State?

Devices may go into the Unreachable state due to the following reasons:

SNMP timeout

Data collector timeout

If an SNMP timeout occurs, verify the SNMP access credentials provided during discovery.

If a data collector timeout occurs, verify that the SNMP management interface is not a serial or a generic interface (such as Frame Relay with the subnet mask 255.255.255.252). You should always access SNMP details using an Ethernet interface.

Editing Device Configuration and Credentials

After you add devices, you can change their configuration setup through the Modify/Delete Devices page.


Note You can also change device credentials directly though the DCR device management pages. Operations Manager provides you with a link to the CiscoWorks Common Services Device Management page. From Operations Manager, select Devices > Device Credentials. For more details on using CiscoWorks Common Services Device Management, see the CiscoWorks Common Services online help.



Step 1 Select Devices > Device Management > Modify/Delete Devices. The Modify/Delete Devices page opens.

Step 2 Expand the folder that contains your devices.

Step 3 Select the device or device group that you want to update.

Step 4 Click Edit. The Edit Device Configuration: Change Credentials page appears.

If you select a single device, all the existing credentials for that device are populated in the Edit Device Configuration: Change Credentials page (asterisks populate the field). If you select multiple devices, only a comma-separated list of IP addresses is displayed.


Note The auto-populated credentials (asterisks) do not reflect the actual credentials; they only indicate that credentials are available.


Step 5 You can update the following credentials:

SNMPv2c/SNMPv1

SNMPv3

HTTP

WMI


Note If you are changing credentials for a device that also has a duplicate, be sure to change the credentials on both devices in case the primary device is deleted.


Step 6 Click OK.


Modifying SNMP Timeout and Retries

If an SNMP query does not respond in time, Operations Manager times out. Operations Manager retries contacting the device for as many times as you indicate. The timeout period is doubled for every subsequent retry.

For example, if the timeout value is 4 seconds and the retries value is 3 seconds, Operations Manager waits 4 seconds before the first retry, 8 seconds before the second retry, and 16 seconds before the third retry.

The SNMP timeout and retry values are global settings. Change these values as follows:


Step 1 Select Devices > Device Management > Inventory Collection > SNMP Configuration. The SNMP Configuration page appears.

Step 2 Select a new SNMP timeout setting. The default is 4 seconds.

Step 3 Select a new Number of Retries setting. The default is 3 retries.

Step 4 Click Apply. Click Yes to confirm.


Performing Manual Inventory Collection on Devices

Through the Modify/Delete Devices page, you can manually collect inventory on devices or device groups. When inventory collection takes place, if there are any changes to a device or group configuration, the new settings will overwrite any previous settings.


Note Configuration changes on a device are discovered by Operations Manager only during discovery (inventory collection) of the device. Therefore any changes to a device's configuration are not shown by Operations Manager until the next inventory collection after the configuration change.


Inventory collection occurs only for active devices. Suspended devices do not go through inventory collection. If some of the devices you are selecting for inventory collection are suspended devices, Operations Manager displays messages indicating that only the active devices will go through inventory collection.


Note Do not confuse the Operations Manager physical discovery process (which adds devices to the DCR) or the Operations Manager inventory collection process (which probes devices and updates components in Operations Manager inventory) with the DCR synchronization process. Operations Manager inventory collection is a process that affects only the Operations Manager inventory.


The following events also trigger inventory collection:

The entire Operations Manager inventory is polled. This is controlled by the inventory collection schedule. (See Scheduling Inventory Collection.)

Operations Manager is using automatic synchronization with the DCR, and a device is added, or a change is made to a device in the DCR. Such DCR changes include a device being deleted or having its credentials (IP address, SNMP credentials, MDF type) changed.

Operations Manager is using manual synchronization with the DCR, and a device is added to Operations Manager using the Device Selection page.


Note If you are using the ACS login module, the System Identity user that is configured in ACS should have permission to run all the job management-related tasks in Common Services and the rediscovery task in Operations Manager.

When rediscovery occurs, all devices in the system are discovered. Therefore, this task should be made available only to the person who has access to all devices in the network.



Step 1 Select Devices > Device Management > Modify/Delete Devices. The Modify/Delete Devices page appears.

Step 2 Select the device or group for which you want to perform inventory collection.

Step 3 Click Rediscover. Inventory collection is started.


Starting Operations Manager

You can access Operations Manager from either the Operations Manager server or a client system.


NoteIf a client system is available, we recommend that you perform all configuration and day-to-day activities from the client system. If a client system is not available, the Operations Manager server must also meet all the system requirements for a client system (for client system requirements, see Table 1-4).

Disable any popup blocker utility that is installed on your client system before launching Operations Manager

By default, SSL is not enabled in Common Services. If you upgraded to Operations Manager 2.3 and SSL was enabled before the upgrade, it remains enabled after the upgrade.


Starting Operations Manager on a Client System

In Internet Explorer, enter the Operations Manager server's IP Address or DNS name followed by the port number 1741. For example, http://<om_server name>:1741.

Starting Operations Manager on the Operations Manager Server

From the Windows desktop, select Start > All Programs > Cisco Unified Operations Manager > Cisco Unified Operations Manager.


Note If Enhanced Security is enabled on the Windows 2003 system, you must add the Operations Manager home page to the Internet Explorer Trusted Sites Zone. You will not be able to access the Cisco Unified Operations Manager home page until it is added to the trusted sites.


Adding the Operations Manager Home Page to the Internet Explorer Trusted Site Zone

If Enhanced Security is enabled on the Windows 2003 system, you must perform the following procedure before you can access the Operations Manager home page.


Step 1 Open Operations Manager and select Start > All Programs > Cisco Unified Operations Manager > Cisco Unified Operations Manager.

Step 2 From the File menu, select Add this site to.

Step 3 Click Trusted Sites Zone.

Step 4 In the Trusted Sites dialog box, click Add to move the site to the list.

Step 5 Click Close.

Step 6 Refresh the page to view the site from its new zone.

Step 7 Check the Status bar of the browser to confirm that the site is in the Trusted Sites Zone.


Adding Cisco Unified Communications Management Server Links from Operations Manager

Use this procedure to add a link to a locally installed or remotely installed Service Monitor server from Operations Manager. For important details about Service Monitor event and trap processing, as well as licensing, see the online help or the User Guide for Cisco Unified Operations Manager 2.3.

You can also link to Provisioning Manager and Service Statistics Manager servers. See the Operations Manager online help or the User Guide for Cisco Unified Operations Manager 2.3 for instructions.


Step 1 Select UC Management Suite > Service Monitor. The Service Monitor page appears.

Step 2 Click Add. The Add Service Monitor page appears.

Step 3 Enter data in the following fields:

IP Address—IP address of a remote server where Service Monitor is installed.

Protocol—HTTP or HTTPS.

Port—Port by which Service Monitor is accessed. Cannot be left blank.

Status—Selection for whether to use this Service Monitor as a cross-launch server.

Remarks—Optional.

Step 4 Click Add. The Service Monitor page appears, displaying information for the newly added Service Monitor.


Understanding and Configuring Security

Operations Manager supports the following security-related mechanisms:

SNMPv3 protocol (Authentication/No-Privacy option)—Operations Manager supports the Authentication/No-Privacy option between the server and the device.

Local security or Cisco Secure ACS—Access to tasks within Operations Manager is either controlled by local security (Common Services Local Login Module) or Cisco Secure ACS. Local security is enabled on the server by default. Operations Manager supports integration with Cisco Secure ACS. For more information, see Security Configuration with Cisco Secure ACS, page C-1.

SSL—Secure Socket Layer (SSL) is an application-level protocol that enables secure transactions of data through privacy, authentication, and data integrity. It relies upon certificates, public keys, and private keys. (SSL is not enabled in Common Services by default.) You can enable or disable SSL depending on the need to use secure access. Operations Manager supports SSL between clients and the server.

To get started with configuring security, see Setting Up Security in the Configuring the Server chapter of User Guide for CiscoWorks Common Services 3.2.

Supported NMS Integration

Operations Manager supports integration with network management systems (NMSs) that reside in your network. Operations Manager does not support an NMS residing on the same system as Operations Manager.

Operations Manager listens for traps from managed devices on port 162 (the default). If your network devices are already sending traps to another management application, configure that application to forward traps to Operations Manager.

Operations Manager forwards traps to destinations that you specify, as follows:

To forward pass-through traps, see Configuring SNMP Trap Receiving and Forwarding.

To forward processed traps, see "Managing SNMP Trap Notifications" in the "Using Notification Services" chapter of User Guide for Cisco Unified Operations Manager 2.3.

For more information on pass-through and processed traps, see the appendix "Processed and Pass-through Traps, and Other Unidentified Traps and Events" in User Guide for Cisco Unified Operations Manager 2.3.

Configuring SNMP Trap Receiving and Forwarding

Operations Manager can receive traps on any available port and forward them to a list of devices and ports. This capability enables Operations Manager to easily work with other trap processing applications. However, you must enable SNMP on your devices and configure SNMP to send traps either directly to Operations Manager or to one of the following:

An NMS

A trap daemon

To send traps directly to Operations Manager, perform the tasks in Enabling Devices to Send Traps to Operations Manager. To integrate SNMP trap receiving with an NMS or a trap daemon, follow the instructions in Integrating Operations Manager Trap Receiving with NMSs or Trap Daemons.

Updating the SNMP Trap Receiving Port

By default, Operations Manager receives SNMP traps on port 162. If you need to change the port, you can do so.


Step 1 Select Administration > Preferences. The System Preferences page appears.

Step 2 In the Trap Receiving Port field, enter the port number.

Step 3 Click Apply.


For a list of ports that Operations Manager uses, see Verifying TCP and UDP Ports that Operations Manager Uses, page 2-7.

Enabling Devices to Send Traps to Operations Manager

Because Operations Manager uses SNMP MIB variables and traps to determine device health, you must configure devices to provide this information. For any Cisco devices that you want Operations Manager to monitor, SNMP must be enabled and the device must be configured to send SNMP traps to the Operations Manager server.

Make sure your devices are enabled to send traps to Operations Manager by using the command line or GUI interface appropriate for your device:

Enabling Cisco IOS-Based Devices to Send Traps to Operations Manager

Enabling Catalyst Devices to Send SNMP Traps to Operations Manager

Enabling Cisco IOS-Based Devices to Send Traps to Operations Manager

For devices running Cisco IOS software, provide the following commands:

(config)# snmp-server [community string] ro
(config)# snmp-server enable traps
(config)# snmp-server host [a.b.c.d] traps [community string]

where [community string] indicates an SNMP read-only community string and [a.b.c.d] indicates the SNMP trap receiving host (the Operations Manager server).

For more information, see the appropriate command reference guide.


Step 1 Log in to Cisco.com.

Step 2 Select Support > Cisco IOS and NX-OS Software.

Step 3 Select the Cisco IOS Software release version used by your Cisco IOS-based devices.

Step 4 Under Reference Guides, select the appropriate command reference guide.


Note Periodically, information on Cisco.com is reorganized and, as a result, navigation paths change. If this happens, use Search to look for Cisco IOS Command References.



Enabling Catalyst Devices to Send SNMP Traps to Operations Manager

For devices running Catalyst software, provide the following commands:

(enable)# set snmp community read-only [community string]
(enable)# set snmp trap enable all
(enable)# set snmp trap [a.b.c.d] [community string]

Where [community string] indicates an SNMP read-only community string and [a.b.c.d] indicates the SNMP trap receiving host (the Operations Manager server).

For more information, see the appropriate command reference guide.


Step 1 Log in to Cisco.com.

Step 2 Select Products & Services.

Step 3 Under Network Systems, select Switches.

Step 4 Select the appropriate Cisco Catalyst series switch.

Step 5 In the Support box, select References—you might be prompted to log in to Cisco.com—and select the appropriate command reference guide.


Note Periodically, information on Cisco.com is reorganized and, as a result, navigation paths change. If this happens, try using Search to look for Catalyst Command References.



Integrating Operations Manager Trap Receiving with NMSs or Trap Daemons

You might need to complete one or more of the following steps to integrate SNMP trap receiving with other trap daemons and other Network Management Systems (NMSs):

Add the host where Operations Manager is running to the list of trap destinations in your network devices. See Enabling Devices to Send Traps to Operations Manager. Specify port 162 as the destination trap port.

If your network devices are already sending traps to another management application, configure that application to forward traps to Operations Manager.

Table 3-7 describes scenarios for SNMP trap receiving and lists the advantages of each.

Table 3-7 Configuration Scenarios for Trap Receiving 

Scenario
Advantages

Network devices send traps to port 162 of the host where Operations Manager is running. Operations Manager receives the traps and forwards them to the NMS.

No reconfiguration of the NMS is required.

No reconfiguration of network devices is required.

Operations Manager provides a reliable trap reception, storage, and forwarding mechanism.

NMS continues to receive traps on port 162 on the host where the NMS is running.

Network devices continue to send traps to port 162.

The NMS receives traps on default port 162 and forwards them to port 162 on the host where Operations Manager is running.

No reconfiguration of the NMS is required.

No reconfiguration of network devices is required.

Operations Manager does not receive traps dropped by the NMS.


Configuring SNMP Trap Forwarding

By default, Operations Manager does not forward unprocessed SNMP traps. However, you can configure it to do so.


Step 1 Select Administration  > Preferences. The System Preferences page appears.

Step 2 Under Trap Forwarding Parameters enter:

An IP address or DNS name for the server.

A port number on which the server can receive traps.

Step 3 Click the Apply button.


Configuring Health Monitor

The Health Monitor utility monitors Operations Manager processes, notes when a process stops and restarts, and can send e-mail updates. To get e-mail updates, perform this procedure.


Step 1 Edit the <NMSROOT>/HealthMonitor/conf/HealthMonitor.cfg file.

Step 2 Enter a value for each of these parameters:

SMTP_Server—SMTP mail server address.

Receiver_Email_ID—E-mail ID for the administrator to be notified

Sender_Email_ID—E-mail ID that identifies the sender

Step 3 After you update the file, put the updates into effect by restarting the HealthMonitor service. From the command line, enter these commands:

net stop HealthMonitor

net start HealthMonitor


For more information, see User Guide for Cisco Unified Operations Manager 2.3.

Configuring Cisco Unified Communications Manager for Use with Operations Manager

For Operations Manager to discover and manage Cisco Unified Communications Manager, you must either perform the configurations described in this section or verify that the existing Cisco Unified Communications Manager settings are correct. Incorrect settings cause incomplete monitoring of Cisco Unified Communications Manager, resulting in inconsistent behavior in some Operations Manager features.

This topic contains the following tasks:

Configuring the Syslog Receiver on Cisco Unified Communications Manager

Activating Events in Operations Manager

(Optional) Configuring RTMT on Cisco Unified Communications Managers

Setting HTTP Credentials on Cisco Unified Communications Manager

You can also see the online help for additional details on how to configure voice application systems and software for use with Operations Manager.

Configuring the Syslog Receiver on Cisco Unified Communications Manager

To successfully receive Cisco Unified Communications Manager syslog messages, you must add the syslog receiver from the device's serviceability web page. Use the following procedure to perform the necessary steps.

For additional details on which syslog events map to Unified Communications Manager releases, see the Event appendix in the Cisco Unified Operations Manager User Guide 2.3.


Step 1 On your Cisco Unified Communications Manager, select Cisco Unified Serviceability from the Navigation pull-down in the top-right corner of the device's home screen.

Step 2 Select Alarm > Configuration.

For an example of the serviceability page for a version 5.x device, see Figure 3-1. The serviceability page may display differently depending on your device version.

Figure 3-1 Unified Serviceability Web Page for a Unified Communications Manager Version 5.x Device


Caution Do not use the Unified Communications Manager enterprise service parameter to configure the syslog receiver for Operations Manager syslog integration. When the enterprise parameter is enabled, all syslog messages (with matching severity levels) are sent regardless of what is intended to be processed by Operations Manager.

Step 3 Select the correct alarm configuration elements for your particular machine as shown in the following table.

For This Unified Communications Manager Version...
Select These Alarm Configuration Elements...

4.x

Cisco CallManager

5.x

Server > Service > Cisco AMC Service

Server > Service > Cisco CDR Agent

Server > Service > Cisco CDR Repository Manager

Server > Service > Cisco CallManager

Server > Service > Cisco Database Layer Monitoring

Server > Service > Cisco DRF Client

Server > Service > Cisco DRF Master

6.x and later

Service Group > CM Services > Service > Cisco CallManager

Service Group > CDR Service > Cisco CDR Agent and Cisco CDR Repository Manager

Service Group > Database and Admin Services > Cisco Database Layer Monitoring

Service Group > Performance and Monitoring Services > Cisco AMC Service

Service Group > Backup and Restore > Cisco DRF Client and Cisco DRF Master


Step 4 Click the Enable Alarm check box, select the proper Alarm Event Level (see the Alarm Configuration Settings in Cisco Unified Serviceability Administration Guide for Cisco Unified Communications Manager on Cisco.com), and enter the Operations Manager server name or IP address in Server Name text box.

For Unified Communications Manager 5.x or later, select AMC Service, and set the alarm event level to Warning. For all other devices, set the alarm event level to Error. Provide any necessary information based on your Cisco Unified Communications Manager.

Step 5 Check Apply to all nodes.

Step 6 Click Save.


Note Syslog messages have a limitation of 1,024 characters (including the heading). Some syslog-based event details may not contain the full information due to this syslog limitation. If the syslog message exceeds this limit, it is truncated to 1,024 characters by the syslog sender.



Activating Events in Operations Manager

Most device events appear in the Alerts and Events display after the device has been added to the Operations Manager database. However, several events are not displayed in Operations Manager by default. You must activate the following events to enable Operations Manager to display them:

Number Of Registered Gateways Increased

Number Of Registered Gateways Decreased

Number Of Registered MediaDevices Increased

Number Of Registered MediaDevices Decreased


Note These events are raised at the cluster level; therefore, individual device information might not be available in the event description. To access individual device information, use the RTMT tool. Select Filter > Devices > MediaDevices or Gateway, then select the check box for all states and generate the report. This report displays all registered and unregistered media devices or gateways.


To activate these event pairs, perform the following steps:


Step 1 Open the NMSROOT\conf\seg\sysLogConfig.xml file.

Step 2 Remove the comment for Syslog by removing the lines marked.

Step 3 Restart the SEGServer process.


(Optional) Configuring RTMT on Cisco Unified Communications Managers

Operations Manager uses the same polling rate and threshold settings as the Real-Time Monitoring Tool (RTMT). In normal operation, you do not need to do anything. The default will work properly.


Note Configuring RTMT impacts Unified Communications Manager and Operations Manager performance.


If you want to have a lower polling rate, increase the polling rate to monitor in real time, then update the parameter settings on Cisco Unified Communications Manager. Use the following procedure to perform these steps.


Step 1 Go to the Unified Communications Manager Administration page.

Step 2 To change polling rates:

For CallManager 5.x and later, select System > Service Parameter > publisher > Cisco AMC Service, then change the Data Collection Polling rate value.

For CallManager 4.x, select Service > Service Parameter > publisher > Cisco RIS Data Collector, then change the Data Collection Polling rate value.

Step 3 To change threshold parameters:

a. Install and launch RTMT.

b. Select AlarmCentral.

c. Select a specific alert and right-click to launch Alert Property.


Setting HTTP Credentials on Cisco Unified Communications Manager

Operations Manager uses the Administrative XML Layer (AXL) API in addition to SNMP to manage Cisco Unified Communications Manager. This means that Operations Manager makes SOAP calls over HTTP via the AXL interface to collect fault and performance information from Cisco Unified Communications Manager. Operations Manager requires the HTTP username and password in order to execute these queries. The username and password do not need to have administrator privileges. You only need credentials with read-level access to http://server-name/ccmadmin.

Viewing Alerts

You can view alerts using the monitoring dashboard displays. Select Monitoring Dashboard and choose from the following displays:

Service Level View

Alerts and Events

Service Quality Alerts

IP Phone Status

What's Next?

After discovery completes Operations Manager is monitoring your network, Table 3-8 summarizes tasks that you might want to perform to customize Operations Manager for your specific deployment.


Note All these tasks are optional; they are not required for Operations Manager to monitor your network.


Table 3-8 Setting Up Operations Manager 

Task
Description

Configure notifications

In addition to learning about alerts by monitoring the Monitoring Dashboard displays, you can subscribe users to receive e-mail and hosts to receive Operations Manager-generated SNMP traps in response to alerts.

Configure views for the Monitoring Dashboard displays

Views are logical groupings of devices that appear in the Monitoring Dashboard displays (Service Level View, Alerts and Events, Phone Activities, and Service Quality Alerts). Whenever you create a new user-defined group on the Group Administration and Configuration page, a corresponding view is created.

Configure polling parameters and thresholds

Operations Manager provides default values for polling parameters and threshold values. However, you can update the values as needed for your network. You should plan to apply the changes when activity on the Operations Manager server is low.

By default, Operations Manager does not set the voice utilization polling settings. If you want to use Operations Manager's performance monitoring capabilities, you must first enable voice utilization polling.

Configure purging

By default, Operations Manager purges the database daily at midnight. You can modify the schedule.

Configure inventory collection

Operations Manager provides a single default schedule for inventory collection. You can use that schedule, or you can suspend it.


To use Operations Manager more fully, you might want to perform additional configuration tasks. See the online help or User Guide for Cisco Unified Operations Manager 2.3 for information on using and configuring Operations Manager.