User Guide for Cisco Unified Operations Manager 8.5
Using Device Management
Downloads: This chapterpdf (PDF - 1.05MB) The complete bookPDF (PDF - 14.64MB) | Feedback

Using Device Management

Table Of Contents

Using Device Management

Getting Started with Device Management

Discovering Devices Automatically

Overview about Devices

Device Prerequisites

Types of Devices that Operations Manager Monitors

Ports and Interfaces that Operations Manager Monitors

Understanding the Device and Credentials Repository

Adding Specific Devices from the DCR

Adding Devices to the DCR

Creating a Read-Only Cisco Unified Communications Manager User Account for Polling

Creating a Read-Only WMI User Account for Polling Cisco Unity Devices

Configuring Operations Manager Physical Discovery

Importing Devices into the DCR

Exporting Device Information from the DCR to a File

Events that Trigger DCR and Operations Manager Synchronization

DCR Masters and Slaves

Masters and Slaves Configuration for Manual Mode

Viewing the Discovered Devices Report

Configuring Device Management

Checking Device States and Discovery Settings

Importing Devices into Operations Manager

Importing Devices from the DCR

How Operations Manager Identifies Devices Imported from the DCR

How Operations Manager Handles Containing and Contained Devices

Automatically Importing DCR Devices

Manually Importing DCR Devices

Determining Which Devices Are in the DCR But Not in Operations Manager

Viewing the IP Address Report Page

Verifying Device Import

Troubleshooting Import and Inventory Collection

Why Does the Device or License Import Fail if the CSV File is Not in CSCOpx?

Why Does a Device Go into the Partially Monitored State?

Why Does a Device Go Into the Unreachable State?

Why Does a End Point Show as Unregistered in Reports and Diagnostic Pages

Manual Inventory Cleanup

Working with Device Management

Understanding the Modify/Delete Devices Page

Editing Device Configuration and Credentials

Performing Manual Inventory Collection on Devices

Viewing Device Details

Using the Modify/Delete Devices Page to Generate a Device Report

Using the Device Management: Summary Page to Generate a Device Report

Understanding Device Reports

Using Device Discovery

Setting Up Auto Discovery Configuration in Operations Manager

Configuring Credentials

Filtering Physical Discovery

Working with Cluster Device Discovery

Getting Device Information

Starting the Detailed Device View

Understanding the Layout of the Detailed Device View

Viewing Device Elements in Detail

Information Shown in the Detailed Device View

Suspending/Resuming Devices

Suspending a Device Using Device Configuration

Suspending Device Monitoring from DDV

Suspending/Resuming a Device Component

Deleting Devices

Collecting Device Inventory

Scheduling Inventory Collection

Working with the Device Inventory Collection Schedule

Working with IP Phone Discovery

Determining the Media Server Account to Use for Cisco Unified Communications Manager Access

Viewing Discovery Status

Editing SNMP Timeout and Retries

Configuring LDAP

Launching Operations Manager Tools

Viewing Event Information

Viewing Event History

Viewing Device Information

Viewing Associated Phones

Launching the Path Analysis Tool

Viewing Performance Monitoring

Setting Up Synthetic Tests

Setting Up Node-To-Node Tests

Setting Up Node-To-Node Test Graphs

Setting Up SRST Monitoring

Configuring Threshold Settings

Configuring Polling Settings

Suspending Devices

Resuming Devices

Adding a Device

Deleting Devices

Creating User-Defined Groups

Launching Administration Pages for Devices

NAT Support in Operations Manager


Using Device Management


These topics explain how to use Cisco Unified Operations Manager (Operations Manager) Device Management:

Getting Started with Device Management, page 15-1

Configuring Device Management, page 15-17

Checking Device States and Discovery Settings, page 15-17

Importing Devices into Operations Manager, page 15-19

Working with Device Management, page 15-29

Using Device Discovery, page 15-35

Getting Device Information, page 15-42

Collecting Device Inventory, page 15-53

Launching Operations Manager Tools, page 15-60


Timesaver To view the online video tutorial about automatic device discovery, see Cisco.com or click on the E-learning icon in the online help.


Getting Started with Device Management

These topics include information about device management and how to get started:

Discovering Devices Automatically, page 15-3

Overview about Devices, page 15-3

Understanding the Device and Credentials Repository, page 15-6

Adding Devices to the DCR, page 15-8

Importing Devices into the DCR, page 15-14

Events that Trigger DCR and Operations Manager Synchronization, page 15-15

DCR Masters and Slaves, page 15-15

Creating User-Defined Groups, page 15-69

For Operations Manager to monitor a device, it must first be added to the CiscoWorks Common Services Device and Credentials Repository (DCR). After a device is added to the DCR, you must then add it to the Operations Manager inventory, which is separate from the DCR.

There are three ways to add devices into the Operations Manager inventory from the DCR (see Table 15-1):

Table 15-1 Adding Devices into the Operations Manager Inventory

Inventory Collection Options
Description

1. Discover devices automatically.1

Use default settings (no action required).

Configure discovery settings for automatic discovery. See Adding Specific Devices from the DCR, page 15-7.

For a video tutorial on automatic device discovery, click on the E-Learning icon in the online help.

2. Manually add devices.

Adding Devices to the DCR, page 15-8

3. Import devices.

Importing Devices into the DCR, page 15-14

1 Device credentials are required to collect inventory information.


For information on how to add devices into the DCR, see the CiscoWorks Common Services online help or user guide documentation.

Using the Operations Manager device management pages, you can perform the following operations:

Configure automatic synchronization to include specific devices, phones Adding Specific Devices from the DCR, page 15-7

Add or import devices from the DCR (see Adding Specific Devices from the DCR, page 15-7, or Importing Devices into the DCR, page 15-14).

Export device information to a file (see Exporting Device Information from the DCR to a File, page 15-14).

Edit device configuration (see Editing Device Configuration and Credentials, page 15-31).

Delete devices (see Deleting Devices, page 15-52).

Select devices to be added to Operations Manager from the DCR (see Importing Devices from the DCR, page 15-19).

View device details (see Viewing Device Details, page 15-33).

Perform inventory collection on devices (see Performing Manual Inventory Collection on Devices, page 15-32).

Get status of device or phone discovery collection (see Viewing Discovery Status, page 15-57).

Suspend and resume Operations Manager device management (see Suspending/Resuming Devices, page 15-49).

As Operations Manager performs inventory collection on devices, they pass through various device states until they are fully recognized by Operations Manager (see Verifying Device Import, page 15-24 for details).

After a device is in Operations Manager inventory, Operations Manager monitors the device and its components according to the polling and threshold settings that apply to the device group (when it is added to the DCR, the DCR assigns the device to a device group).

Discovering Devices Automatically

When Operations Manager is installed, you can choose to use the default setting of automatically synchronizing with the DCR to add inventory.

If you do not want to manage all your network devices, 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 Device and Credentials Repository, page 15-6.

You may need to configure certain devices so that Operations Manager can display all pertinent data. For a list of required device configuration changes, see Overview about Devices, page 15-3.


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


NMSROOT is the directory where Operations Manager is installed on your system. If you selected the default directory during installation, it can be entered as "C:\Program Files\CSCOpx" or C:\PROGRA~1\CSCOpx.


Tip For a video tutorial on automatic device discovery, click on the E-Learning icon in the online help.


Overview about Devices

This section includes detailed information about how to ready your devices for the Operations Manager inventory:

Device Prerequisites, page 15-3

Types of Devices that Operations Manager Monitors, page 15-5

Creating a Read-Only Cisco Unified Communications Manager User Account for Polling, page 15-10

Creating a Read-Only WMI User Account for Polling Cisco Unity Devices, page 15-12

Device Prerequisites

When working with device management, note the following:

If a monitored device is removed from the network, it will continue to be in the Monitored state until the next inventory collection occurs, even though the device is unreachable. If a device is unreachable, an Unreachable event appears for this device in Fault Monitor that contain event information.

Configuration changes on a device are discovered by Operations Manager only during the inventory collection process. Therefore any changes to a device's configuration will not be shown by Operations Manager until the next inventory collection, after the configuration change.

If Static NAT Environment is not enabled using the Operations Manager system preferences, Network Address Translation (NAT)-enabled devices cannot be monitored by Operations Manager. For more information, see Setting System-Wide Parameters Using System Preferences, page 19-19.

If Cisco Discovery Protocol (CDP) is not enabled on a media server (either it is disabled or not responding), Operations Manager will not discover the device correctly and the device will be moved to the Unsupported state.

In order to successfully receive Cisco Unified Communications Manager syslog messages, you must add the syslog receiver from the serviceability web page. See Configuring Syslog Receiver on Cisco Unified Communications Manager, page F-5.

In order for Operations Manager to view forwarded Windows events from Windows-based devices as SNMP traps, you must configure the event to trap forwarder utility (evntwin.exe). Evntwin configures the translation of events to traps based on information in the Evntwin configuration file.

It is installed when the Windows SNMP service is installed. You need to select the event numbers that you want to forward as SNMP traps. See Configuring SNMP Trap Receiving and Forwarding, page 19-5.

If the Operations Manager server is using Access Control Server (ACS) mode, ACS may limit the devices you are permitted to view. For more information, see Device-Based Filtering, page 19-32.

If the Operations Manager server is using Access Control Server (ACS) mode and you want to provide access to a cluster for any user, all the devices in the cluster must be explicitly added into the ACS configuration for that user. It should include Unified CM nodes, gateways, Unity devices, gatekeepers, and so on.

If DNS is configured on a device, ensure Operations Manager can resolve the DNS name for that device. Check the DNS Server configuration to make sure it is correct. This is critical for Unified CM, Unified Presence Server, and Unity Connection devices, since without DNS resolution certain monitoring features do not work.

When you add devices, the HTTP (and HTTPS) port numbers are optional. These settings are automatically detected.

When you add devices that have multiple interfaces and HTTP administrative access, you must manage the device in Operations Manager using the same interface on which you have enabled HTTP administrative access.

You must enter the Windows username and password when you add Cisco Unified Contact Center, Cisco Unity Connection, Cisco Unity, and Cisco Personal Assistant. These JDBC credentials are entered in the Primary Credentials field in the DCR.

To enable Operations Manager to provide the correct phone count for the Communications Manager Express and Cisco Unity Express (CUE), you must use the following configuration:

ephone 8 
mac-address 001A.E2BC.3EFB 
type 7945  

where type is equal to the phone model type. If you are unsure of your model type, see Cisco.com for details on all phone model types, or enter type?.

For information on how phone counts are displayed in Device Management Summary window, see How Are Phone Counts Displayed in Fault Monitor, Diagnostics Views, and Reports?, page 1-22.

If a UC500 Series router is running Unified CM Express, configure "type" under ephone config for each phone so that the cmeEphoneModel MIB variable of CISCO-CME_MIB will return the correct phone model. This enables Operations Manager to discover the phones registered with Unified CM Express.

For a Cisco Unity Express that is attached to a Unified CM Express to display in the Service Level View, you must use the following configuration:

dial-peer voice 2999 voip  <where voip tag 2999 must be different from voicemail> 
destination-pattern 2105  <prefix must be the full E.164 of configured voicemail 2105> 
session protocol sipv2 
session target ipv4:10.10.1.121 
dtmf-relay sip-notify 
codec g711ulaw 
no vad 
! 
! 
telephony-service 
voicemail 2105

where the dial-peer VoIP tag, 2999, is not equal to the voicemail number, and the destination-pattern, 2105, is equal to the voicemail number. This will allow Unity Express to display properly in the Service Level View.

Operations Manager manages a device when the device's management state is set to True; conversely, Operations Manager does not manage a device when its management state is set to False.

A device with a management state set to False is called a suspended device. You can also selectively unmanage device components (see Suspending/Resuming a Device Component, page 15-51).

For information on how many devices Operations Manager can manage, see the Installation Guide for Cisco Unified Operations Manager. If the Operations Manager inventory exceeds your device limit, you will see a warning message. For more information, see Responding to Messages About Device Limits, page 1-30.

Types of Devices that Operations Manager Monitors

When devices are added to the DCR, they are assigned to Common Services System Defined Groups. The group to which the DCR assigns the device depends on the device type users specify when they add the device. If a user does not select a device type, or selects the wrong device type, the DCR designates the device as Unsupported, and it is assigned to the Common Services Unsupported group.

Operations Manager assigns a device type when it performs inventory collection on the device.

For examples of the types of devices that Operations Manager monitors, see Table 16-1 on page 16-3.

For a detailed list of devices that Operations Manager supports, see Supported Device Table for Cisco Unified Operations Manager on Cisco.com at http://www.cisco.com/en/US/products/ps6535/products_device_support_tables_list.html.

Ports and Interfaces that Operations Manager Monitors

The following describes the default ports and interfaces that Operations Manager monitors or does not monitor:

Ports (switches)—By default, Operations Manager monitors trunk ports but does not monitor access ports.

An access port is a switch port that is connected to a host or device that Operations Manager does not monitor; that is, an end-station port.

A trunk port is a port that connects to a Cisco network device running Cisco Discovery Protocol (CDP). In other words, a trunk port connects to a router, or to a switch that the same Operations Manager server manages.

Interfaces (routers)—By default, Operations Manager monitors all interfaces listed in the ifTable.

During inventory collection only (by default), BRI B-Channel interfaces (for voice) are unmanaged.

During inventory collection only (by default), PRI B-Channel interfaces are unmanaged.

Understanding the Device and Credentials Repository

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 all applications.


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, page 15-8).


After 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 IP address. When the DCR device is added to Operations Manager, Operations Manager maps the DCR ID to a device name during inventory collection (see Table 15-4 on page 15-20).

Operations Manager also uses the DCR ID to verify if 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 Importing Devices from the DCR, page 15-19.)

You can add devices from the DCR to Operations Manager automatically by activating automatic synchronization (which is the default), or you can add them selectively by deactivating using the DCR 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 (see Deleting Devices, page 15-52).

For information on deleting components of aggregate devices, see How Operations Manager Handles Containing and Contained Devices, page 15-21.

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

For automatic synchronization (this is the default), see Automatically Importing DCR Devices, page 15-21.

For manual synchronization (in which you selectively add devices from the DCR to the Operations Manager inventory), see Manually Importing DCR Devices, page 15-22.

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.

Adding Specific Devices from the DCR

Operations Manager automatically synchronizes the DCR with its inventory. This synchronization includes all network devices. If you use this default setting it may substantially slow your server's performance depending on the size of your network. You may want to create a subset of devices or clusters for Operations Manager to add to the Operations Manager inventory.

Add specific devices from the DCR to the Operations Manager manually using the DCR Device Selection.

To add specific devices manually from the DCR:


Step 1 Select Administration > Device Management > Device Configuration > DCR Device Selection.

The DCR Device Selection page appears.

You can also access the Add Devices page from the Discovered Devices report. (See Viewing the Discovered Devices Report, page 15-16.)

Step 2 Click Manual and select specific devices to be entered.

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

While adding multiple devices at one time, all the devices must be the same type and use the same credentials.

SNMPv2c/SNMPv1 credentials

SNMPv3 credentials

HTTP credentials (only required for Cisco Unified Communications Manager and Cisco Unified Presence Server)

JDBC credentials—Only required for the following devices:

Cisco Unified Contact Center

Cisco Unity

Cisco Unity Connection

Cisco Personal Assistant

Windows-based versions of Cisco Unified Communications Manager

Step 3 Click OK.


Adding Devices to the DCR

To add devices into the DCR from Operations Manager manually use the Add Devices page (Administration > Device Management > Device Configuration > Add Devices).

Figure 15-1 shows an example of the Add Devices page for Enterprise devices. Figure 15-2 shows an example of the Add Devices page for MSP devices. The NAT check box enables additional fields on the page.

Figure 15-1 Add Devices Page for Enterprise Mode

Figure 15-2 Add Devices Page for MSP Mode


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



Step 1 Select Administration > Device Management > Device Configuration > Add Devices.

The Add Devices page appears.

You can also access the Add Devices page from the Discovered Devices report. (See Viewing the Discovered Devices Report, page 15-16.)

Step 2 Enter the following:

If your device is an Enterprise device:

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

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

If your device is NAT-enabled:

Select the NAT check box.

Enter the Global IP address, Local IP address, and Local DNS.

When adding multiple devices, at one time, use a comma-separated list. Use empty space in between commas while adding multiple Local IP Address and Local DNS Name. Local DNS Name is not a fully-qualified domain name (FQDN).

SNMPv2c/SNMPv1 credentials

SNMPv3 credentials

HTTP credentials (only required for Cisco Unified Communications Manager and Cisco Unified Presence Server)

JDBC credentials for 4.x CCM—Required only for Windows-based MCS application servers including the following devices. Enter the Windows username using the format: Domain name\Username or Username.

Cisco Unified Contact Center

Cisco Unity

Cisco Unity Connection

Cisco Personal Assistant

Windows-based versions of Cisco Unified Communications Manager

Step 3 Click OK.


Caution Certain monitoring features may not be available if DNS name is not resolved. For details about DNS name resolution, see Device Prerequisites, page 15-3.


Creating a Read-Only Cisco Unified Communications Manager User Account for Polling

To set up a read-only user account that allows polling of your Unified CM device (version 6.0 and above) for Linux:


Step 1 Create a new read-only application user (for example, cuomuser) on the CCMAdmin page by selecting User Management > Application User.

Step 2 Click Add New after entering the new application user name.

Step 3 Create a new user group that contains the new read-only user (for example, CUOM Access) by selecting User Management > User Group.

Step 4 Enter Standard CCM Read Only and click the Copy icon (see Figure 15-3).

Step 5 Enter your new user group, for example, CUOM Access, and click OK.

Figure 15-3

User Group Copy Window

Step 6 Add the new cuomuser to that user group (for example, CUOM Access) by clicking Add Application Users to Group.

Step 7 Add the Standard AXL API Access role to the read-only user group by selecting User Management > User Group, clicking the Roles icon that appears on the CUOM Access group line (see Figure 15-4).

Step 8 Click Assign Role to Group in the window that appears.

Step 9 Add Standard AXL API Access and click Save.

Figure 15-4

Roles Icon in User Group Window

To verify the cuomuser role permissions, select User Management > Application User, select cuomuser, and check the following roles under Permission Information—Roles:

The CUOM Access group (or whatever name you assigned) should contain the following roles:

# Standard AXL API Access

# Standard CCM Admin Users

# Standard CCMADMIN Read Only

# Standard SERVICEABILITY Read Only

Step 10 Log into Operations Manager as the read-only user.

Step 11 Add the Communications Manager by selecting Administration > Device Management > Device Configuration > Add Devices.


Creating a Read-Only WMI User Account for Polling Cisco Unity Devices

In order to provide a safe and secure environment for files, such as polling logs, you must create a non-administrative user account to perform polling on Windows Management Instrumentation (WMI) for Unity devices.

To create a read-only WMI user account for polling Cisco Unity devices:


Step 1 Log into the Unity server with an administrator account.

Step 2 Create a non-administrator or read-only user.

Step 3 Open the WMI Control console by clicking Start, click Run, type wmimgmt.msc.

Step 4 Click OK.

Step 5 Set the permission for the user, right-clicking WMI Control.

Step 6 Click on Properties, and click on the Security tab.

Step 7 Select CIMV2 from namespace navigation window, click on security.

Step 8 Add the user just created, click Add (or select Everyone from the user name window).

Step 9 Select the following permissions from the permission window:

Execute Method

Enable Account

Remote Enable

Read Security

Step 10 Click OK on the security and WMI control windows, and close the WMI management window.


Configuring Operations Manager Physical Discovery

To configure Operations Manager Discovery:


Step 1 Select Administration > Device Management > Device Configuration > Device Credentials.

The Configure Credentials page appears.

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

Step 2 Click Add.

The Configure Credentials page appears (see Configuring Credentials, page 15-13).

Step 3 Enter the following:

Target devices wild card entry. Multiple devices can be entered at one time, using a comma-separated list.

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

SNMP timeout and retries

SNMPv2c/SNMPv1 credentials (SNMP write community string is required for IP SLA diagnostic tests)

SNMPv3 credentials

HTTP credentials (only required for Cisco Unified Communications Manager and Cisco Unified Presence Server)

WMI credentials—Only required for Windows-based MCS application servers including the following devices:

Cisco Unified Contact Center

Cisco Unity

Cisco Unity Connection

Cisco Personal Assistant

Windows-based versions of Cisco Unified Communications Manager


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.

Other credentials may be required based on the devices, as noted below. Credentials are stored in the Device and Credentials Repository (DCR) and in the Operations Manager inventory.

To configure credentials:


Step 1 Select Administration > Device Management > Auto Discovery Configuration > Credentials.

The Configure Credentials page appears.

Step 2 Click Add.

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 a time, using a comma-separated list.

While adding multiple devices at one 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 (SNMP write community string is required for IP SLA diagnostic tests)

SNMPv3 credentials

HTTP credentials (only required for Cisco Unified Communications Manager and Cisco Unified Presence Server)

WMI credentials—Only required for Windows-based MCS application servers including the following devices:

Cisco Unified Contact Center

Cisco Unity

Cisco Unity Connection

Cisco Personal Assistant

Windows-based versions of Cisco Unified Communications Manager

Step 4 Click OK.


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 (Administration > Device Management > Device Configuration > Import Devices). For additional details, click Help to view the Common Services help.

To import devices into the DCR:


Step 1 Select Administration > Device Management > Device Configuration > Import Devices.

The CiscoWorks Common Services Import Devices page appears.

Step 2 Enter the import information.

To import devices successfully into Operations Manager, the input import CSV file should have Read permission for the USERS group. When importing the CSV file from another directory, ensure that you have casuser permission on the file or import the CSV file directly from the CSCOpx directory.


Note Ensure the import file contains the optional user-defined fields (user_defined_field_3 and user_defined_field_2) which are required for NAT-enabled device importing. These fields correspond to Local IP and Local DNS Name, respectively.


Certain monitoring features may not be available if DNS name is not resolved. For details about DNS name resolution, see Device Prerequisites, page 15-3.

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


Tip When you export the devices from Operations Manager, the user permissions to the .csv file are set such that when you import the same file, Operations Manager cannot accept it. Instead, import a copy of the same .csv file, because the permissions are correctly set.



Exporting Device Information from the DCR to a File

To export device information to a file, Operations Manager provides you a direct link to the DCR. For additional details, click Help to view the Common Services help.


Step 1 To export device information to a file: Select Administration > Device Management > Device Configuration >Export Devices.

The CiscoWorks Common Services Device Export page appears.

Step 2 Enter the export information.

If you need help exporting, click the Help button on the page, and the Common Services online help opens. You can either choose to export credentials or not using the Export Device Credentials check box. Export credentials are exported in clear text.


Tip When you export the devices from Operations Manager, the user permissions to the .csv file are set such that when you import the same file, Operations Manager cannot accept it. Instead, import a copy of the same .csv file, because the permissions are correctly set.



Events that Trigger DCR and Operations Manager Synchronization

The following events will trigger synchronization between the Operations Manager inventory and the DCR:

Devices are added or deleted, or their credentials (IP address, SNMP credentials, MDF type) are changed in the DCR. (This also triggers a device inventory collection in Operations Manager).

DCR is changed from:

Master to slave

Standalone (single server) to slave

DCR is restored from a different domain.

See these topics for more information:

Importing Devices from the DCR, page 15-19

Determining the Media Server Account to Use for Cisco Unified Communications Manager Access, page 15-57

DCR Masters and Slaves

By default, the DCR mode is standalone (single server), and one DCR is supported per server. However, you can configure the DCR to use a master/slave model. In this model, the master DCR is the primary repository residing on a CiscoWorks server.

Slave DCRs reside on other CiscoWorks servers, and replicate the DCR master. Any change in the master DCR is propagated to slave DCRs. This allows applications on different servers to use a synchronized device inventory. Using the master/slave model is transparent to Operations Manager.

If the DCR used by your instance of Operations Manager is changed from master to slave, or from standalone to slave, the DCR device list is synchronized with the Operations Manager inventory.

All devices are removed from the Operations Manager inventory (regardless of DCR synchronization mode). If Operations Manager is configured to use manual synchronization, all DCR devices will appear in the Device Selector (as devices that are not in Operations Manager).

For automatic synchronization, all DCR devices are added to the Operations Manager inventory.

Whenever the DCR mode is changed (to or from master, slave, or standalone) you must perform a daemon manager restart.


Note Remember to manually stop the OMHealthMonitor Windows Service when you perform maintenance activities. Not doing so may result in processes being restarted that have been intentionally stopped.


For details on OMHealthMonitor, see Monitoring Operations Manager Process Health, page 19-50. Then run the following commands:

net stop crmdmgtd
net start crmdmgtd

Inventory collection for the devices in master and slave configurations in Operations Manager happen independently. This may result in the status of these devices displaying differently in Operations Manager.


For more information on the DCR master/slave model, see the CiscoWorks online help.

Masters and Slaves Configuration for Manual Mode

This section describes the procedures you must perform if you are going to use Operations Manager in a master and slave configuration with manual device selection configured in Operations Manager.


Step 1 To configure for Manual mode: Set device selection to manual. (See Manually Importing DCR Devices, page 15-22.)

Step 2 Configure Operations Manager as a slave server.

For information on configuring the DCR master/slave model, see the Common Services online help.)

All the devices will be in the local DCR and not in Operations Manager.

Step 3 In the Device Selection page, select the Manual radio button.

The CS tree will contain all the devices that are present in the master server. This allows you to select all the devices that are not present in Operations Manager.


Viewing the Discovered Devices Report

The Discovered Devices report lists all the devices that Operations Manager has discovered. It also enables you to select the devices that you want to add to the DCR.

To view the Discovered Devices report:


Step 1 Select Administration > Device Management > Device Configuration> Device Summary.

The Device Management: Summary page appears.

Step 2 Next to the Last Discovery field, click View Report.

The Discovered Devices report opens.

The report lists the following:

IP address of the device.

Device Name—This field is populated when a DNS Domain filter is set during discovery configuration. If a DNS Domain filter is not specified, the device name field displays not available.

Has Credentials—Either True or False appears. This is based on whether discovery was able to discover the credentials.

Status of the device—There are three possible values: Added to Operations Manager, Updated in Operations Manager, Unreachable.

The Add button at the bottom of the report enables you to add the devices that you have selected to the DCR.


Configuring Device Management

Use Device Management > Device Configuration to perform the following tasks:

Table 15-2 Device Management Configuration Tasks

Tasks
Description

Checking Device Status and Discovery Settings

Checking Device States and Discovery Settings, page 15-17

Adding Devices

Adding Specific Devices from the DCR, page 15-7

Adding Devices to the DCR, page 15-8

Importing Devices

Importing Devices into the DCR, page 15-14

Exporting Devices

Exporting Device Information from the DCR to a File, page 15-14

Modifying or Deleting Devices

Understanding the Modify/Delete Devices Page, page 15-29

Selecting DCR Devices

Automatically Importing DCR Devices, page 15-21

Manually Importing DCR Devices, page 15-22

Running an IP Address Report

Viewing the IP Address Report Page, page 15-23

Configuring Device Credentials

Editing Device Configuration and Credentials, page 15-31

Using Device Groups

Managing Groups, page 16-1


Checking Device States and Discovery Settings

The Device Management Summary page lists the device states for all devices in the Operations Manager inventory. Select Administration > Device Management > Device Configuration > Device Summary to view the page.

To view the status on phone discovery collection, see Viewing and Scheduling Phone XML Discovery Status, page 15-57.

Table 15-3 describes the information displayed on the Device Management Summary page.

Table 15-3 Device Management: Summary Page 

Heading/Button
Description

State

Lists the number of devices in the following states:

Monitored

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

Partially Monitored

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 Import and Inventory Collection, page 15-25.

Unsupported

Device is not supported by Operations Manager.

NA

When there is no Unity Express in the Communications Manager Express cloud, the Unity Express state displays NA.

Total Devices

Number of devices that are in each device state. The blue numbers are links to device reports. When you click a blue number a device report for that specific device state opens. See Understanding Device Reports, page 15-34.

Total Phones

Number of phones monitored. The blue number links to the All IP Phones/Lines report. See Understanding Audio IP Phone Inventory Reports, page 12-14.

A link to the Unknown Phones Report appears next to the title of the report.

Total Phone Lines

Number of phone lines monitored. The blue number links to the All IP Phones/Lines report. See Understanding Audio IP Phone Inventory Reports, page 12-14.

A link to the Unknown Phones Report appears next to the title of the report.

Unknown Phone Count

Number of phones that are not in the inventory.

Device Selection

Current mode for device selection from the DCR. See Importing Devices into Operations Manager, page 15-19.

Last Discovery

Date and time when last performed physical discovery.

Next Discovery

Date and time when will next perform physical discovery.

Configure

Configures physical discovery. Selecting the Configure button takes you to the Configure Credentials page. See Configuring Credentials, page 15-36.

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


Importing Devices into Operations Manager

A device must be in the Device and Credentials Repository (DCR) before you can add it to the Operations Manager inventory (see Adding Devices to the DCR, page 15-8). Operations Manager supports two methods of device import from the DCR:

Using automatic synchronization between the DCR and Operations Manager (see Automatically Importing DCR Devices, page 15-21)

Using manual synchronization between the DCR and Operations Manager (see Manually Importing DCR Devices, page 15-22)

Once discovery is complete, then the CDT discovery will start. Once this is complete, then the phone discovery will start. This is an automatic process. There is no need to start it manually.

Avoiding Conflicts with Other Cisco Unified Management Suite Applications

If Operations Manager, Provisioning Manager, and Service Monitor are deployed in the same network and are provisioning and managing the same set of devices, the administrators must plan synchronization activities.

When planning synchronization activities, note the following:

Operations Manager—When Operations Manager is performing a synchronization with either a Call Processor or a Unified Message Processor device, the Operations Manager administrator should not be discovering the device at the same time.

Service Monitor—When Operations Manager is performing a synchronization with either a Call Processor or a Unified Message Processor device, the Service Monitor administrator should not be adding or verifying the device as a data source at the same time.

To import devices successfully into Operations Manager, the input import CSV file should have Read permission for the USERS group. When importing the CSV file from another directory, ensure that you have casuser permission on the file or import the CSV file directly from the CSCOpx directory.

When importing devices for the NAT environment into Operations Manager, you must ensure you have chosen the System Preference to turn on NAT or add two extra attributes into the CSV file to ensure NAT-enabled device Local IP address and Local DNS Name are included.

Importing Devices from the DCR

After a device has been added to the DCR, it can be added to the Operations Manager inventory:

Automatically (whenever there is an addition or change), if Device Selection is set to automatic in the Device Management: Summary page.

Manually (on a device-by-device basis), if Device Selection is set to Manual in the Device Management: Summary page.

To verify which setting you are using, select Administration > Device Management > Device Configuration > DCR Device Selection.

This section contains:

How Operations Manager Handles Containing and Contained Devices, page 15-21

How Operations Manager Identifies Devices Imported from the DCR, page 15-20

Events that Trigger DCR and Operations Manager Synchronization, page 15-15

Polling—SNMP and ICMP, page G-1

Troubleshooting Import and Inventory Collection, page 15-25

Importing Devices into Operations Manager, page 15-19


Note Your login determines whether you can import devices into Operations Manager


How Operations Manager Identifies Devices Imported from the DCR

When a device is added to Operations Manager from the DCR, Operations Manager attempts to resolve the DNS name (hostname). Operations Manager does not use the DCR Display Name.

Table 15-4 shows how Operations Manager names devices, depending on how the devices are added to the DCR.

Table 15-4 How Operations Manager Determines Device Names 

When device is added to DCR with...
Operations Manager does the following:

IP address and hostname (DNS name)

Uses the DNS name, if Operations Manager can resolve it

Uses the IP address, if Operations Manager cannot resolve the DNS name

IP address only

Uses the DNS name, if Operations Manager can resolve the IP address

Uses the IP address, if Operations Manager cannot resolve the DNS name. Certain monitoring features may not be available if DNS name is not resolved. For details about DNS name resolution, see Device Prerequisites, page 15-3.

DNS name only

Uses the DNS name, even if not resolvable. For details about DNS name resolution, see Device Prerequisites, page 15-3.

 

IP address, and the IP address was already added to the DCR (this is allowed in the DCR)

Chooses one IP address and the other becomes a duplicate. For details on how to determine if you have duplicate devices, see Viewing the IP Address Report Page, page 15-23.

IP address, and the IP address corresponds to two interfaces of the same physical device

Chooses one IP address and the other becomes a duplicate. For details on how to determine if you have duplicate devices, see Viewing the IP Address Report Page, page 15-23.


After a device is added to the DCR with a specified MDF type and sysUnified Communications ID, no one can overwrite it, even if it is incorrect. The only exception is if no sysUnified Communications ID is supplied, as described in the previous table.

For information on how Operations Manager performs polling and discovery, see Polling—SNMP and ICMP, page G-1

How Operations Manager Handles Containing and Contained Devices

Operations Manager supports contained and containing devices (also referred to as aggregate devices). These are devices that have a parent/child relationship with another device, such as a Catalyst switch (parent) containing an MSFC (child). The switch is considered the containing device, and the MSFC is the contained device.

Table 15-5 How Operations Manager Handles Containing and Contained Devices 

Action
Effect on Device
Containing
Contained
Adding to Operations Manager (regardless of DCR synchronization mode)
 

Containing

Added

Added1

 

Contained

N/A

N/A

Inventory Collecting in Operations Manager
 

Containing

Inventory collected

Inventory collected

 

Contained

No effect

Inventory collected

Removing from Operations Manager
 

Containing

Deleted

Deleted from Operations Manager (but not deleted from DCR)

 

Contained

No effect

Deleted

Removing from DCR
 

Containing

Deleted

Deleted

 

Contained

No effect

Deleted

Suspending in Operations Manager
 

Containing

Suspended

Suspended

 

Contained

No effect

Suspended

Resuming in Operations Manager
 

Containing

Resumed

Resumed

 

Contained

No effect

Resumed only if containing device is resumed

1 When a containing device is added to the DCR, the DCR does not recognize the contained devices. However, when the device is added to Operations Manager, the contained devices are probed by Operations Manager and added to the Operations Manager inventory.


Automatically Importing DCR Devices

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

For a video tutorial on automatic device discovery, click on the E-Learning button in the Online help.


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.



Step 1 To automatically import devices: Select Administration > Device Management > Device Configuration > DCR Device Selection.

The DCR 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 Administration > Device Management > Device Configuration > IP Address Report.

If you do not require the duplicate device for your deployment, remove it (see Deleting Devices, page 15-52).


If you exceed your device limit, Operations Manager will continue to operate, but you will notice that devices are not being added to Operations Manager. Check the license log as described in Accessing and Deleting Log Files, page 19-21.

For information about device-based licensing, see Responding to Messages About Device Limits, page 1-30.

For information about the inventory collection schedule, see Scheduling Inventory Collection, page 15-53.

Manually Importing DCR Devices

Use the following procedure to change automatic synchronization to manual synchronization.

To change automatic synchronization to manual synchronization:


Step 1 Select Administration > Device Management > Device Configuration > DCR Device Selection.

The DCR 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.

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

Step 4 Click Select.

Operations Manager performs inventory collection on the devices that are being added.

Step 5 Verify whether any duplicate devices exist, by selecting Administration > Device Management > Device Configuration > IP Address Report.

If you do not require the duplicate device for your deployment, remove it (see Deleting Devices, page 15-52).


If you exceed your device limit, Operations Manager displays a warning message. You can get more information from the license log as described in Accessing and Deleting Log Files, page 19-21. For information about device-based licensing, see Responding to Messages About Device Limits, page 1-30.

For information about how to handle duplicate devices, refer to Viewing the IP Address Report Page, page 15-23.

Determining Which Devices Are in the DCR But Not in Operations Manager

To identify devices that are in the DCR but not in Operations Manager, use the Device Selection page. In the Device Selection page with the Manual radio button selected, the device selector lists the devices that are not in Operations Manager. Devices may not be in Operations Manager for these reasons:

Devices have not been added to Operations Manager because Operations Manager is using manual DCR synchronization.

Devices were deleted from Operations Manager. (Devices you delete from Operations Manager are not deleted from the DCR.)


Note Devices you delete can only be added back into Operations Manager using manual import.


See Manually Importing DCR Devices, page 15-22 on how to access the Device Selection page.

For information about moving devices from the DCR into Operations Manager, see Manually Importing DCR Devices, page 15-22. For information about duplicate devices, see Viewing the IP Address Report Page, page 15-23.

Viewing the IP Address Report Page

The IP Address Report page lists all the IP addresses of the devices that are added to Operations Manager. The IP address list includes both the IP addresses of the devices in the DCR (including devices that are not monitored by Operations Manager) and the IP addresses of all the devices in inventory.

To view the IP Address Reportpage, select Administration > Device Management > Device Configuration > IP Address Report. The IP Address Report page appears.

Table 15-6 describes the information found in the IP Address Report.

The IP Address Report page displays the following:

The IP addresses for all the devices in the DCR, but not in Operations Manager inventory. The IP Address Report may only display the IP address (if added) and the DCR display name.

The IP addresses for all the devices in Operations Manager inventory.

All the IP addresses known for each of the devices in Operations Manager inventory. If there is more than one IP address for a monitored device, all the IP addresses are displayed. The DCR Display Name column displays N/A and the Device Name and Managed IP Address columns will have the same entries for the corresponding device.

Duplicate device entries from the DCR. If there is more than one entry for the same device in the DCR (this can occur by varying the DCR display name), the IP Address Report identifies the duplicate entries and appends the display names with the corresponding IP address entry in the DCR Display Name column.

The duplicate entries in the DCR are identified by having more than one display name in the DCR Display Name column of the IP Address Report.

Support for NAT-enabled devices to include data for Local IP Address and Local DNS Name, as well as indicating that a device is NAT-enabled.

For deleting duplicate devices, Deleting Devices, page 15-52.


Table 15-6 IP Address Report Page

Heading
Description

IP Address

IP address known to Operations Manager.

DCR Display Name

Display name used when the device was added to the DCR.

Device Name

Device name as seen in Operations Manager. Clicking the device name opens the Detailed Device View page for the device.

Managed IP Address

IP address of the device through which Operations Manager manages the device.

Is NAT Enabled

Lists whether this device has NAT support enabled.

Local IP Address

If NAT-enabled, displays the local IP address for the device.

Local DNS Name

If NAT-enabled, displays the local DNS name for the device.


Verifying Device Import

After adding a device, you can verify that it has been imported by using the Modify/Delete Devices page.


Step 1 Select Administration > Device Management > Device Configuration > Modify/Delete Devices.

The Modify/Delete Devices page opens. Figure 15-5 shows an example of the Modify/Delete Devices page.

Step 2 In the device selector, locate the device you added.

Step 3 Click on the device.

Device information appears in the right pane. Verify that Device Status is Monitored. A Monitored state on the device indicates that it was imported successfully.

For a complete explanation of the device states, see Checking Device States and Discovery Settings, page 15-17.

If the device is not in the Monitored state, refer to Troubleshooting Import and Inventory Collection, page 15-25.



Tip If your device appears in the device selector under the All Monitored Devices group, it was fully imported into Operations Manager. Only the devices in the All Partially Monitored Devices group and the All Unreachable Devices group were not imported fully into Operations Manager.


Troubleshooting Import and Inventory Collection

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 avoid 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.

NMSROOT is the directory where Operations Manager is installed on your system. If you selected the default directory during installation, it can be entered as "C:\Program Files\CSCOpx" or C:\PROGRA~1\CSCOpx.

For information on why you may receive device or license import errors, see Why Does the Device or License Import Fail if the CSV File is Not in CSCOpx?, page 15-26

For information on why your devices or phones are not going into the Monitored state, see the following:

Why Does a Device Go into the Partially Monitored State?, page 15-26

Why Does a Device Go Into the Unreachable State?, page 15-28

Why Does a End Point Show as Unregistered in Reports and Diagnostic Pages, page 15-28


Caution Operations Manager will be unable to collect the correct information if it cannot resolve the Unified CM name using DNS. Ensure the Unified CM is added to the DNS. For details about DNS name resolution, see Device Prerequisites, page 15-3.

To troubleshoot Import and Inventory Collection problems:.


Step 1 Select Administration > Device Management > Device Configuration > Modify/Delete Devices.

The Modify/Delete Devices page opens. Figure 15-5 shows an example of the Modify/Delete Devices page.

Step 2 Expand the folder that contains your device (according to its inventory collection status; refer to Verifying Device Import, page 15-24).

Step 3 Click the device name or IP address.

Device information is populated.

Step 4 Look under Data Collection Status Information for error information.

Step 5 Perform the required actions to clear the error.


Why Does the Device or License Import Fail if the CSV File is Not in CSCOpx?

If the device or license import file (*.csv) is imported from any folder other than the install-directory CSCOpx, the import fails and gives the following error:

ERROR: Import from file failed. REASON: File C:/Documents and Settings/Administrator/Desktop/backup-csv.csv does not exist. Please check the permissions of this file/directory.

Do the following:

When you export the devices from Operations Manager, the user permissions to the .csv file are set such that when you import the same file, Operations Manager cannot accept it. Instead, import a copy of the same .csv file, because the permissions are correctly set.

Ensure that you have casuser permissions.

Why Does a Device Go into the Partially Monitored State?

Table 15-8 explains the possible reasons for the error codes seen on the Modify/Delete Devices page that occur for partially monitored devices.

Why Cisco Unified Communications Manager or Unified Presence Server may go into the partially monitored state

If the incorrect HTTP credentials were entered or if no credentials are provided for certain Cisco devices (see Table 15-7), the device may go into the partially monitored state. When this occurs none of the Perfmon Counters will be polled. To change device credentials, see Editing Device Configuration and Credentials, page 15-31.

Table 15-7 Cisco Devices Requiring HTTP Credentials

Cisco Device Name

Unified Communications Manager

Unified Presence Server


Why certain voice applications may go into the partially monitored state

This explanation describes why the following devices may go into the partially monitored state:

Cisco Unified Contact Center

Cisco Unity Connection

Cisco Unity

Cisco Personal Assistant

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

Table 15-8 Error Shown on the Modify/Delete Devices Page 

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

Error Code = WMI Authentication Failure

Error Message = Success: Incorrect WMI Credential or Insufficient Privileges

The message indicates that either the credentials are incorrect or user does not have sufficient privilege to reach the device.

WMI credentials are for a user who is not an administrator.

1. Check if the Windows Management Instrumentation (WMI) credentials are correct.

2. If credentials are correct, and the device is in the Partially Monitored State, verify that Operations Manager is able to reach the device with the credentials provided, using the following steps:

a. Open the command prompt on the Operations Manager machine, type wbemtest, and click OK.

b. In the new popup, click Connect.

c. In the Connect popup for NameSpace text field, enter: \\<ccmip>\root\cimv2 instead of root\default.

d. Enter the User Name and password and click Login.

Login should succeed for Operations Manager to move the device in to a fully monitored state.

If the login fails, check that the Operations Manager machine and CCM are in different domains. If yes, include the domain name when you add a device.

If login has failed, see if a firewall may be blocking packets.

If login is successful in step 2;

a. Try restarting Windows Management Instrumentation service on Cisco Unified Communications Manager.

b. Rediscover the device.

Error Code = WMI Authentication Failure

Error Message = Success: No Windows Credential for WMI Access

No Windows credential provided.

1. Go to the Modify/Delete screen.

2. Select the device under All Partially Monitored Device. WMI Authentication Failure category, and click Edit.

3. Enter the WMI credential and click OK.

Error Code = HTTP Authentication Failure

Error Message = Success:WrongCredentials

This message indicates that either the Cisco device HTTP credentials are not entered or the credentials provided are incorrect.

1. Verify that you provided the correct HTTP credentials in the DCR by using the credentials to log in to the Cisco device.

2. Verify if the same credentials work for https://DEVICEIP/ast/astisapi.dll?QueryService.

3. Rediscover the device.

Error Code = HTTP Authentication Failure

Error Message = Success:WebServiceDown

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

1. Verify that the web server is running by launching the Cisco device.

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

3. For Cisco Unified Communications Manager 5.0, verify that 8433 and 8080 are not blocked.


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 Framerelay with the subnet mask 255.255.255.252). You should always access SNMP details using an Ethernet interface.

Why Does a End Point Show as Unregistered in Reports and Diagnostic Pages

If all the Cisco Unified CM nodes are not managed in Operations Manager, Operations Manager displays the end points that are registered to those unmanaged Unified CM nodes as unknown instead of unregistered.

To ensure that all the end points are discovered properly, ensure all the Unified CM nodes in Operations Manager are managed.

Manual Inventory Cleanup

To clean up your inventory, you must delete all devices. This includes all monitored devices, as well as devices in the Unreachable and Unsupported states.


Step 1 To manually clean the inventory:Select Administration > Device Management > Device Configuration > Modify/Delete Devices.

The Modify/Delete Devices page opens.

Step 2 In the device selector, select the check box next to All Devices.

Step 3 Click Delete.


Note It is essential that you delete all of the devices.



Working with Device Management

The topics covered in this section include:

Understanding the Modify/Delete Devices Page, page 15-29

Editing Device Configuration and Credentials, page 15-31

Performing Manual Inventory Collection on Devices, page 15-32

Viewing Device Details, page 15-33

Suspending/Resuming Devices, page 15-49

Deleting Devices, page 15-52

Scheduling Inventory Collection, page 15-53

Viewing Discovery Status, page 15-57

Editing SNMP Timeout and Retries, page 15-58

Configuring LDAP, page 15-58

Understanding the Modify/Delete Devices Page

Performing inventory collection, viewing details, suspending and resuming device monitoring, editing credentials, and deleting devices are controlled by the Modify/Delete Devices page. Figure 15-5 shows the Modify/Delete Devices page.

Figure 15-5 Modify/Delete Devices Page


Note If at any time while using the Modify/Delete Devices page, you want to refresh the view, click the Refresh button.


The Modify/Delete Devices page contains two panes. The left pane displays a device selector, from which you select the device or group that you want to update or delete. The right pane displays the information for the selected object. Besides displaying device information, the right pane displays data collection information.


Tip If there is an error during device discovery, an error code and error message appear at the bottom of the right pane. For troubleshooting information see Troubleshooting Import and Inventory Collection, page 15-25.


The devices that appear in the device selector are organized in folders, based on whether they are monitored by Operations Manager. The folders appear only if there is a device to go in the folder.

Under the All Devices folder, devices are placed in the following possible subfolders:

All Monitored Devices—Contains devices that are fully monitored in the Operations Manager inventory.

All Monitoring Suspended Devices—Contains devices for which monitoring has been suspended. A user manually suspends monitoring of the device by Operations Manager.

All Partially Monitored Devices—Contains devices that have been successfully imported by some of the data collectors in Operations Manager (see Why Does a Device Go into the Partially Monitored State?, page 15-26).

All Unreachable Devices—Contains devices that were not successfully imported into Operations Manager. Descriptions of the errors are displayed in the right pane, next to Error Message (see Why Does a Device Go Into the Unreachable State?, page 15-28).

All Unsupported Devices—Contains devices that were not imported into Operations Manager because they are not supported.

Details about, and procedures for, performing inventory collection, viewing details, or deleting devices using this page are provided in these topics:

Performing Manual Inventory Collection on Devices, page 15-32

Viewing Device Details, page 15-33

Suspending/Resuming Devices, page 15-49

Deleting Devices, page 15-52

Scheduling Inventory Collection, page 15-53

Editing Device Configuration and Credentials

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


Note You can also change device credentials though the Auto Discovery Configuration page. (See Configuring Credentials, page 15-13.)



Step 1 Select Administration > Device Management > Device Configuration > Modify/Delete Devices.

The Modify/Delete Devices page opens. Figure 15-5 shows an example of the Modify/Delete Devices page.

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.

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

You can update the following credentials:

SNMPv2c/SNMPv1

SNMPv3

HTTP

WMI

For NAT-enabled devices only:

Local IP Address

Local DNS Name

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 5 Click OK.


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.

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 will not be 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.

If a device is not in DNS (or DNS-resolvable), then the discovered device name is just the IP address. If the devices are DNS resolvable, then the managed name displays.

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 will also trigger inventory collection:

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

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.

If you are using the ACS login module, the System Identity user that is configured in ACS should have permissions 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 will be discovered. Therefore, this task should be made available only to the person who has access to all devices in the network.



Step 1 Select Administration > Device Management > Device Configuration > 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.


Viewing Device Details

You can select devices and view information about them in a report. There are several ways you can generate this report using:

The Modify/Delete Devices page, where you can view details about particular devices that you choose. See Using the Modify/Delete Devices Page to Generate a Device Report, page 15-33.

The Device Management: Summary page, where you can view details about all the devices in a particular device state. See Using the Device Management: Summary Page to Generate a Device Report, page 15-34.

The Fault Monitor page, where you can access the Detailed Device View in the Actions hover over for the device.

The Service Level View, where you can select a cloud view and drill down to access device and phone information. See Viewing Devices and Clusters from Service Level View, page 4-11.

The device report provides basic information about the device such as name, IP address, when it was added, and so on. (For a description of a device detail display, see Understanding Device Reports, page 15-34.)

If you require more detailed information about a device, use the Detailed Device View. It provides information about device components, including hardware and software information, environment, connectivity, interface components, and so on. (For a description of the Detailed Device View, see Table 15-11, "Detailed Device View—Command Buttons".)

Figure 15-5 shows an example of the Modify/Delete Devices page. Devices are organized in folders according to their device state. (See Checking Device States and Discovery Settings, page 15-17.)

Using the Modify/Delete Devices Page to Generate a Device Report


Step 1 Select Administration > Device Management > Device Configuration > Modify/Delete Devices.

The Modify/Delete Devices page appears.

Step 2 For each device for which you want to view details, in the device selector, expand the folders where the device is located.

Step 3 Select a device by clicking the box next to it. Do this for each device for which you want to view details. If you want to view details for all of the devices in a group, click the box next to the group.

Step 4 Click View.

A report appears, listing the device information.


Using the Device Management: Summary Page to Generate a Device Report


Step 1 To use the Device Management: Summary page for generating a device report:Select Administration > Device Management > Device Configuration > Device Summary.

The Device Management: Summary page appears.

Step 2 Locate the device state for which you want to view the devices.

Step 3 In the number column that corresponds to the device state, click the number.

A report appears, listing the device information.


Note If the number in the column is zero, you will not be able to generate a report.



Understanding Device Reports

A device report displays details for the devices that you select. See Viewing Device Details, page 15-33 for information on selecting devices.

In the Monitored or Partially Monitored devices reports, a Suspend button appears at the bottom of the report. You can use this button to suspend the monitoring of all the devices in the report.

Similarly, the Monitoring Suspended report provides you with a Resume button, so that you can resume monitoring of all the devices in the report.

Table 15-9 describes the information displayed in a device report.

Table 15-9 Device Report 

Heading/Button
Description

Device Type

Device type.

Device Name

Device name. Clicking the link opens a Detailed Device View for the device. See Understanding the Layout of the Detailed Device View, page 15-44.

IP Address

Device IP address.

Is NAT Enabled

Lists whether this device has NAT support enabled.

Local IP Address

If NAT-enabled, displays the local IP address for the device.

Local DNS Name

If NAT-enabled, displays the local DNS name for the device.

Device Capabilities

Functions that a device can perform; for example, switch, voice gateway, Cisco Unified Communications Manager, Host, and so on.

Status

Current state the device is in.

Monitored Since

Time and date that inventory collection was first completed for the device.

Last Inventory Collection

Time and date that inventory collection was last completed for the device.

Exports all data to either a CSV file or a PDF file on your computer.

Reformats the displayed records into print-friendly format, and displays them in a new browser window.

Displays the help page for this display or report.

Suspend or Resume

Depending on the report, a Suspend button or a Resume button may appear at the bottom of the report. This button enables you to either suspend or resume monitoring of all of the devices in the report.

Suspend—Available in the Monitored and Partially Monitored device report.

Resume—Available in the Monitoring Suspended device report.


Using Device Discovery

This section includes these topics:

Setting Up Auto Discovery Configuration in Operations Manager, page 15-35

Filtering Physical Discovery, page 15-36

Working with Cluster Device Discovery, page 15-40


Timesaver To view the online video tutorial about automatic device discovery, see Cisco.com or click on the E-Learning icon in the online help.


Setting Up Auto Discovery Configuration in Operations Manager

This section provides information on how Operations Manager enables you to configure the following for inventory collection:

Device credentials specifically for the Operations Manager inventory. See Configuring Credentials, page 15-36.

Discovery options (CDP, logical cluster discovery using a seed device, or ping sweep). See Filtering Physical Discovery, page 15-36.

Filter specific IP addresses, DNS locations, and Syslocations to include or exclude from the discovery. See Filtering Physical Discovery, page 15-36.

Discovery schedule options. See Filtering Physical Discovery, page 15-36.

Automatic device cluster discovery. See Working with Cluster Device Discovery, page 15-40.

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 Other credentials may be required based on the devices, as noted below. Credentials are stored in the Device and Credentials Repository (DCR) and in the Operations Manager inventory.Select Administration > Device Management > Auto Discovery Configuration > Credentials.

The Configure Credentials page appears.

Step 2 Click Add.

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 a time, using a comma-separated list.


Note When adding multiple devices at one 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 (SNMP write community string is required for IP SLA diagnostic tests)

SNMPv3 credentials

HTTP credentials (only required for Cisco Unified Communications Manager and Cisco Unified Presence Server)

WMI credentials—Only required for Windows-based MCS application servers including the following devices:

Cisco Unified Contact Center

Cisco Unity

Cisco Unity Connection

Cisco Personal Assistant

Windows-based versions of Cisco Unified Communications Manager

Step 4 Click OK.


Filtering 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 Administration > Device Management > Auto Discovery Configuration > Filters and Schedule.

The Filters and Schedule page appears.

Step 2 Select one of the following options (Discovery or Filters):

Select the Discovery radio button, then:

a. Select the Cisco Discovery Protocol (CDP), the Use Logical Cluster Discovery check box, or both, and do one of the following:

b. Enter seed devices using a comma-separated list of IP addresses. The discovery is restricted to one cluster. If you want to perform discovery of multiple clusters, then enter the publisher address for all the clusters, separated by commas, in the Seed device text box.

When using logical cluster discovery, 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

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

c. Select the Use devices currently in the system check box.

Use devices currently in the system is enabled only if Use Cisco Discovery Protocol (CDP) or Use Logical Cluster Discovery is selected.

d. Select the Use ping sweep check box.

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

While 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.


Note Ping sweep cannot be selected with CDP or cluster discovery.


Select the Filters radio button and enter the filter information.

Table 15-10 describes the optional filters that are available to you when running physical discovery. You can click Advanced Filters to display additional filter option.

Table 15-10 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. After 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.

Advanced Filters

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.

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, or .babc.com, etc.

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.

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 In the Run pane, specify 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, then enter the time and select the day on which physical discovery should run.

If you want cancel a physical discovery that is scheduled to run in the future, select the disable radio button.

Step 4 Click OK.

You can now look in the Device Management Summary to see device activity.


Working with Cluster Device Discovery

The following topics are covered in this section:

About Cluster Device Discovery, page 15-40

Prerequisites to Running Device Discovery, page 15-40

Scheduling or Viewing Cluster Device Discovery, page 15-41


Timesaver To view the online video tutorial about cluster device discovery, see Cisco.com or click on the E-learning icon in the online help.


About Cluster Device Discovery

Cluster device discovery is performed by the Common Devices Table (CDT) module. This allows Operations Manager to consolidate the inventory and the device registration information it collects from Unified Communications Managers (Unified CM). It collects two different categories of information from Unified CMs:

Cluster configuration data including Redundancy group, Devicepool, Location, Region, RouteList, RouteGroup, RoutePattern, Partition, and so on. This also includes the entities provisioned in the cluster such as phones, voice mail endpoints, media resources, gateways, and trunks.

Registration information— Registration information corresponds to all the entities which register with the Unified CM cluster. This includes Device IP, Registration status, the Unified CM server to which the entity is registered currently, the latest registration/unregistration timestamp, and the status reason.

The registration information is collected once an hour. This can be configured using a configuration file. This information is collected from all the subscriber nodes in the clusters to which the entities like phones or gateways register.

For this data collection to occur successfully it requires:

Cisco RIS Data Collector to be running in 4.x versions of Unified CM.

Cisco SOAP - CDRonDemand Service to be running in other versions of Unified CM.

The data collected from the Unified CM cluster is used in other modules such as the Diagnostics view, phone inventory, service level view, and Voice Health Monitor (VHM).

Prerequisites to Running Device Discovery

Ensure the following prerequisites for data collection are completed before using Cluster Device Discovery.

1. Data is collected from Publisher/First node through AXL. Therefore, the publisher should be in fully in monitored state with proper HTTP credentials entered and the AXL Web Service should be running in the publisher.

2. AXL is not supported in Unified CM versions prior to 4.x. These clusters cannot be monitored.

3. If the Unified CM publisher is configured using name in the CUCM section/System Server section of CM Administration, then this name must be resolvable through DNS from the Operations Manager server. Otherwise, an entry must be configured for this name in the hosts files for the data collection to proceed further.

4. Any changes in the registration information are updated through processing the relevant syslogs from the Unified CM. For Operations Manager to be able to receive syslogs and process configurations required in the Unified CM, you must perform the steps in Configuring Syslog Receiver on Cisco Unified Communications Manager, page F-5.

Syslog processing can detect the following for the entities registered to the Unified CM cluster:

Any registration changes on entities such as phone, voice mail endpoint, gateways, and so on.

Any new phones provisioned in the cluster are detected and updated to the inventory.

Scheduling Between Discoveries

If any of the following changes occur on the cluster configuration before the scheduled periodic data collection and you want these changes to appear in Operations Manager immediately, you must use the Run Now option to ensure the following types of data are collected:

New device pools, location, region, redundancy group, Route List, Route Group, Route pattern or Partition added, deleted or modified in the cluster.

Changes in membership of any end point to the device pool or association of any end point to the redundancy group.

New subscriber added to or deleted from the Unified CM cluster.

Changes in membership of any subscriber to the redundancy group.

Changes in membership of any gateway to Route group or Route Group to Route List.

This option triggers data collection and synchronizes all the clusters monitored in Operations Manager.

If changes are limited to a specific cluster, the publisher of the cluster can be rediscovered by using Administration > Device Management > Device Configuration > Modify/Delete Devices.

Scheduling or Viewing Cluster Device Discovery

Operations Manager collects cluster configuration from the Cisco Unified CM once a day as well as at startup. This periodic discovery data collection is done by default at midnight daily. You can change this default schedule using the Cluster Device Discovery.

When you select Administration > Device Management > Inventory Collection > Cluster Device Discovery, you can view cluster device discovery status or set the schedule to run a discovery.

For information about how cluster device discovery is performed, see About Cluster Device Discovery, page 15-40.


Step 1 Select Administration > Device Management > Inventory Collection > Cluster Device Discovery.

The Cluster Device Discovery window displays the following:

Discovery Status—Displays the status of the discovery process using any of the following categories:

In progress—When you start SEGServer for the first time or restart it, discovery takes place automatically and the status appears as In Progress.

Completed—The discovery process is complete.

Not available. Try after some time—Appears when you start SEGServer for the first time, or restart it, and the discovery process has not yet begun.

Last Discovery Start Time—Displays the start time of the last discovery.

Last Discovery End Time—Displays the end time of the last discovery.

Device Schedule using the hour and minute set for the discovery reoccurrence.

Step 2 Click Apply to set the discovery schedule for a future discovery or Run Now to run the cluster discovery immediately.


Getting Device Information


Note For definitions for the information that is displayed in the Detailed Device View, see Performance Counters Shown in the Detailed Device View, page A-1.


The Detailed Device View provides extensive information on the devices and device components listed in Starting the Detailed Device View, page 15-42. You can view information on devices that Operations Manager is currently monitoring, as well as devices whose monitoring you have suspended.

In the Detailed Device View, you can do the following:

View hardware and software information on system, environment, connectivity, and interface components

View hardware and software information on subcomponents of aggregate devices

View application status for Cisco Unified Communications Manager, Voice Services, Work Flow, and Synthetic Tests.

Suspend or resume management of a device or a device component so the device is no longer polled, or polling is resumed. See Suspending Device Monitoring from DDV, page 15-50 or Suspending/Resuming a Device Component, page 15-51.

Launch other Operations Manager tools such as performance graphs

Starting the Detailed Device View

You can start the Detailed Device View from within the various displays You can

Click a device link,

Hover over a device name and select the Detailed Device View from the Actions list

Start the Event Details page and select the Detailed Device View from the Actions list.

In many reports or pages in Operations Manager, you can click on a device name to open the Device Details or the Detailed Device View for the device.

You cannot display a Detailed Device View for unidentified trap devices. For more information on unidentified traps, see Processed SNMP Traps, page C-1.


Step 1 From the Fault Monitor dashboard, hover over a device in the Device Name column.

The Device Details popup displays.

Step 2 Click the Detailed Device View in the Action links located at the bottom of the popup. (See Figure 15-6 for an example.)

Step 3 Click Refresh to redisplay the page.


Figure 15-6 provides an example of a Detailed Device View.

Figure 15-6 Detailed Device View

1

Component categories pane. See Component Categories Pane, page 15-44.

4

Windows tool bar. See Window Tools Area, page 15-46.

2

System information pane. See System Information Pane, page 15-44.

5

Command button area. See Command Buttons Area, page 15-46.

3

Tools. See Actions (Tools You Can Use to Perform Tasks), page 15-44.

6

Record count. See Record Count, page 15-46.


Understanding the Layout of the Detailed Device View

These topics provide details about the information in the Detailed Device View. For more information, see Performance Counters Shown in the Detailed Device View, page A-1.

Component Categories Pane

The component categories pane lists the components of the device or cluster. If you select a component, you can view detailed information pertaining to that component, such as CPU usage for a processor, TotalUsedMemory for memory, and so forth.

If the device you are viewing is an aggregate device, the subdevice also appears in the component categories pane.

To display a complete Detailed Device View of the subcomponent, click the Launch New DDV for This Device button. This button appears after you select the subdevice from the device tree.

System Information Pane

The system information pane provides information such as the system name, IP address, SysUnified Communications ID, system contact, and so forth. Table 15-13 on page 15-47 lists the Detailed Device View information you will see for each device type. See Viewing Device Elements in Detail, page 15-47.

If the system information pane lists an attribute with no value, it is because of one of the following reasons:

The attribute is not populated.

The attribute is not configured correctly.

The attribute does not apply to the device.

You can suspend or resume device or component monitoring by clicking the Suspend or Resume button (the button shown depends on the component's current managed state). These functions are described in these sections:

Suspending Device Monitoring from DDV, page 15-50

Suspending/Resuming Devices, page 15-50

Actions (Tools You Can Use to Perform Tasks)

The Actions or Tools list enables you to launch other Operations Manager tools as well as external applications from the Detailed Device View. The tools that are available to you may vary depending on the device type and its configuration.

The following options can be seen in the Launch Tools menu as well as the Device and Event hoverover windows:

Administrative Pages—Opens the administrative page of the device. The options that appear depend on the device; some examples are:

Call Manager Express (CME)

Cisco Unity Connection (CUC)/CUCxN/UC Administration Cisco Unity Express (CUE)

Cisco Unified Mobility Advantage (CUMA)

Meeting Place (MP)

Meeting Place Express (MPE)

Personal Assistant (PA)

Router

SIP Proxy Server

TelePresence

UCC Express

Unity

UCM Serviceability, or UCM Trace Configuration

Associated Phones—Opens an Associated Phones report (see Viewing Associated Phones, page 15-62).

Associated TelePresence

Connectivity Details—Opens the Connectivity Detail View (see Working with the Connectivity Detail View, page 4-5).

Detailed Device View—Opens a Detailed Device View for the device (see Starting the Detailed Device View, page 15-42).

Device Center—Opens the Device Center page of the Operations Manager Server (see Using Device Management, page 15-1).

Event Details—Opens the Event Details page (seeViewing Event Details, page 3-24 and Accessing the Events Details Page, page 3-21).

Event History—Opens an Event History report (see Understanding the Event History Report, page 11-8).

Expert Advisor/Unified Expert Advisor

Launch SLV—Displays the Service Level View for the associated cluster or device (see

Message Waiting Indicator Test—Displays the Message Waiting Indicator Test.

Name of Synthetic Test—Opens the Create Synthetic Test page (see Creating Synthetic Tests, page 8-6). The options that appear depend on the device. For synthetic test details, see Getting Started with Synthetic Tests, page 8-1.

Node-To-Node Test Graph—Opens the Node-To-Node Test Configuration page (see Creating a Single Node-To-Node Test, page 10-2).

Path Analysis Tool—Opens the Path Analysis Tool (see Launching the Path Analysis Tool, page 15-63).

Performance Graph—Shows performance monitoring (see How to Use Performance Graphs, page 6-1).

Polling Parameters—Opens the Polling Parameters: Edit page (see Editing Polling Parameters, page 18-14).

SQ Alert Detail

SQ Event History

SQ Event History Home

SRST Test—Opens the SRST Test Configuration page (see Configuring a Single SRST Test as Needed, page 17-10).

TelePresence in Cluster

Threshold Parameters—Opens the Managing Thresholds: Edit page (see Editing Operations Manager Thresholds, page 18-31).

UCM Diagnostic View

UMC Quality Reportings

Voicemail Diagnostic View

Window Tools Area

The top-right corner of the Detailed Device View contains available tools buttons. All buttons are described in Table 15-11.

Table 15-11 Detailed Device View Page—Window Tools Buttons

Icon
Meaning
Described in...

Exports the current display to a PDF file.

Exporting Data from a Display or Report, page 1-25

Opens a printer-friendly version for printing.

Printing Displays or Reports, page 1-26

Opens the online help.

Where is the Help button?, page 1-22


Record Count

The record count lists the number of information types available on the device.

Command Buttons Area

In addition to the Suspend and Resume button in the system information pane, the command button area provides other ways to respond to events.

Table 15-12 Detailed Device View—Command Buttons

Button
Action

Suspend or Resume

Either activates or deactivates monitoring of the device. Only one option is available at a time, depending on the state of the device. See Suspending Device Monitoring from DDV, page 15-50.

Refresh

Refreshes the Detailed Device View page. (The Detailed Device View is not automatically refreshed; you must do so manually.)


Launch Information

The launch information shows the current time on the server when the Detailed Device View display is being viewed. If you refresh the page, the time is updated.

Viewing Device Elements in Detail

This topic explains what the Detailed Device View displays for different device classes. See Information Shown in the Detailed Device View, page 15-47.

Information Shown in the Detailed Device View

Unity Connection 2.1 ports are not monitored by Operations Manager. In the Detailed Device View the following Unity Connection port details are displayed as Not Available (N/A):

Total number of unity connection ports.

Number of ports currently active.

Number of inbound ports.

Number of outbound ports.

Number of inbound ports currently active.

Number of outbound ports currently active.

Also, the left pane of the Detailed Device View does not display a Unity Connection Ports option.

Table 15-13 shows the types of device information displayed for the various device types that Operations Manager supports. For more information, see Performance Counters Shown in the Detailed Device View, page A-1.

Table 15-13 Device Information Provided by the Detailed Device View 

Device Type
Status Reported by Detailed Device View
Device-Specific Components Reported by Detailed Device View
Subcomponents Reported by Detailed Device View 1
Environment
System
Interface
Connectivity
Application 2

Content Networking

 

X

X

       

Digital Voice Gateway

   

X

X

     

Gatekeeper

X

X

X

X

     

IPSLA

X

X

X

       

MRP

 

X

X

X

     

Personal Assistant

       

X

   

Media Server

X

X

X

 

X

Cisco Unified Communications Manager

Performance Counters3

 

Phone Access Switch

X

X

X

       

Probe

X

X

X

       

Routers

X

X

X

     

RSM, MSM, MSFC

SPE

 

X

   

X

   

SSP

 

X

X

       

Switch

X

X

X

     

RSM, MSM, MSFC

Unified Communications Manager or Cluster

           

Media Servers, Digital Voice Gateways,
Voice Gateways, VoiceMail Gateways

Unified Contact Center Enterprise (formerly IPCC)

X

X

X

 

X

Functional components:

CTI Gateway

CTI Unified Communications Server

Administrator Workstation

Logger

NIC

Unified CCE Components

Peripheral Gateway

Peripheral Interface Manager

Router

Performance Counters3

 

Unity

X

X

X

 

X

   

Unity Express

 

X

X

 

X

Performance Counters3

 

Voice Gateway

X

X

X

X

X

Cisco Unified Communications Manager Express, SRST-enabled
Cisco Unity Connection

IOS GW Performance Counters3

RSM, MSM, MSFC

VoiceMail Gateway

 

X

X

X

     

1 You can display a new Detailed Device View for each of these subcomponents.

2 Voice applications and synthetic testing.

3 For descriptions of the Performance Counters, see Performance Counters Shown in the Detailed Device View, page A-1.


The status categories—Environment, System, Interface, and so forth—list different entries depending upon the device class. The following are some examples of what you may see under the status categories:

Environment: Temperature, fan, power supply, voltage information.

System: Hard disk, RAM, processor, virtual memory information

Interface: Card, interface, port, voice port information

The Voice Port entry displays information for T1, E1, FXS, and FXO ports, as well as Ethernet and Gigabit Ethernet ports that have IP phones connected to them. When new Ethernet ports with phones connected to them are discovered, the Voice Port information is updated after a manual refresh of the Detailed Device View.

Connectivity: Cluster connectivity information such as cluster name, Cisco Unified Communications Manager status, Cisco Unified Communications Manager list, Active Cisco Unified Communications Manager

Application: Voice Services, Cisco Unified Communications Manager information

Suspending/Resuming Devices

When you stop monitoring a device, Operations Manager no longer polls that device for information. Subsequent events (including traps) are ignored and no longer processed.

You can suspend a device several ways:

Suspending a Device Using Device Configuration, page 15-49

Suspending Device Monitoring from DDV, page 15-50

Suspending a Device Using Device Configuration


Step 1 Select Administration > Device Management > Device Configuration > Modify/Delete Devices.

The Modify/Delete Devices page appears.

Step 2 Select the devices that you want to suspend or resume.

Step 3 Do one of the following:

Click Suspend to change the device's current managed state to Suspended. Operations Manager no longer polls any device components, nor does it process any traps. The device is moved to the Suspended Devices view. Subsequent events (including traps) are ignored and no longer processed.

Click Resume to change the device's current managed state to Active. Operations Manager resumes polling and trap processing on the device, and the device is moved out of the Suspended Devices view and back into its previous view.


Note When you resume a device, you must also perform the apply changes action in Polling and Thresholds (see Applying Changes, page 18-67).



Suspending Device Monitoring from DDV

You can stop monitoring a device by selecting it and clicking the Suspend button in the Detailed Device View (DDV). Conversely, you can resume monitoring by clicking the Resume button. These actions are also available for suspending and resuming specific components. See these topics for more information:

Suspending/Resuming Devices, page 15-49

Suspending/Resuming a Device Component, page 15-51

Suspending/Resuming Devices

When you stop monitoring a device (That is, change its monitored state to False) Operations Manager no longer polls that device for information. Subsequent events (including traps) are ignored and no longer processed.

When you suspend a device, the active events on the device are moved to the Cleared state. Also, a Suspended event occurs on the device, which you can view in the device's Event Details page. This happens to ensure that:

You cannot mistakenly remove important information from the display when you suspend a device (when events are cleared, they are removed from the Fault Monitor).

You can easily resume the device.


Step 1 From Fault Monitor, hover over the device name or IP address. (Devices not managed are in the Suspended Devices view.)

The Device Details popup page opens.

Step 2 Click on the Action link to cross launch Detailed Device View.

The Detailed Device View window opens.

Step 3 Do one of the following:

Click Suspend to change the device's managed state to Suspended. Operations Manager no longer polls any device components, nor does it process any traps. All events are moved to the Cleared state. The device event is moved to the Suspended Devices view. Subsequent events (including traps) are ignored and no longer processed.

Click Resume to change the device's managed state to Active. Operations Manager resumes polling and trap processing on the device, and the device event is moved out of the Suspended Devices view and back into its previous view.


Note When you resume a device, you must also perform the apply changes action in Polling and Thresholds (see Applying Changes, page 18-67).


Click Refresh to redisplay the page.


Figure 15-7 provides an example of the Detailed Device View for a suspended device.

Figure 15-7 Detailed Device View—Suspended Device

Suspending/Resuming a Device Component

You can unmanage or remanage device components using the Detailed Device View. When you unmanage a component (that is, change its managed state to False) Operations Manager no longer polls that component for information. Subsequent events (including traps) are ignored and no longer processed.


Note You cannot resume a device component if the parent device is suspended. You must resume the parent device first.



Step 1 From Fault Monitor, hover over the device name or IP address. (Devices not managed are in the Suspended Devices view.)

The Device Details popup page opens.

Step 2 Click on the Action link to cross launch Detailed Device View.

The Detailed Device View window opens.

Step 3 Select the component with the instance you want to unmanage.

Step 4 Locate the instance you want to unmanage, and make your change using the list in the Managed State column.

Step 5 Click Submit.


Figure 15-8 shows the location of the Managed State column for a managed application (Voice Services).

Figure 15-8 Editing the Managed State of a Device Component

Deleting Devices

There are two inventories where devices exist, in Operations Manager and in the DCR, so when you delete a device it can be removed from either inventory. How Operations Manager is configured with the DCR determines from which inventory a device is deleted. For Operations Manager/DCR configurations, see DCR Masters and Slaves, page 15-15.

Which inventory a device is removed from when it is deleted depends on the Operations Manager and DCR configuration as follows:

Standalone mode—The device is removed from both the Operations Manager and the DCR inventory.

Master mode—The device is removed from both the Operations Manager and the DCR inventory.

Slave mode—The device is removed only from the Operations Manager inventory.

While a device is being deleted, Operations Manager does not allow any inventory collection, suspend operations, or resume operations to be performed on the device. When you delete a containing device, all of the contained devices are deleted.

Even if a device is deleted from Operations Manager, if the device is configured to send traps to Operations Manager, Operations Manager will still receive traps and will process the trap as an unidentified traps in Fault Monitor.

Guidelines for Deleting Devices

The following guidelines are helpful when you are considering deleting devices from your network:

If you only want to suspend the managed state of a device, you do not need to delete the device from Operations Manager. For more details on suspending and resuming the managed state of a device, see the Suspending/Resuming Devices, page 15-49.

Depending upon the load that exists on the system, Operations Manager takes approximately 15 to 40 seconds to delete a device.

When you turn off a device in the network and do not want it to be monitored by Operations Manager any longer, you will need to remove the device from Operations Manager or you will be unable to remove events from Fault Monitor. To remove devices use one of the following procedures:

Access Service Level Views and locate the device which you need to remove. Right click the device and select Delete Device.

Select Administration > Device Management > Device Configuration > Modify/Delete Devices. Select the device by clicking on the check box, then click Delete. By deleting the device in Operations Manager, all the existing events in the Fault Monitor will also be removed.


Note Your login determines whether you can perform this operation.



Step 1 Select Administration > Device Management >Device Configuration > Modify/Delete Devices.

The Modify/Delete Devices page appears.

Step 2 Select the device or group that you want to delete.

Step 3 Click Delete.

Step 4 In the confirmation box, click Yes.


Collecting Device Inventory

The following topics are included in this section:

Scheduling Inventory Collection, page 15-53

Setting Up Auto Discovery Configuration in Operations Manager, page 15-35

Scheduling Inventory Collection

Operations Manager collects data from monitored devices and updates the information about the devices themselves and the phones registered with managed devices. There are separate inventory collection schedules for devices, phones, and clusters. You cannot create additional schedules. You can only edit the existing schedule. For IP phones, you can create multiple inventory collection schedules.

The following topics are covered in this section:

Working with the Device Inventory Collection Schedule, page 15-54

Working with IP Phone Discovery, page 15-55

Determining the Media Server Account to Use for Cisco Unified Communications Manager Access, page 15-57

Viewing Discovery Status, page 15-57

Working with Cluster Device Discovery, page 15-40

Editing SNMP Timeout and Retries, page 15-58

Scheduling or Viewing Cluster Device Discovery, page 15-41

Configuring LDAP, page 15-58

For an overview of the inventory collection tasks, see Table 15-14.

Table 15-14 Inventory Collection Overview

Task
Description

Schedule inventory collection of devices

In the Inventory Collection Schedule page (Administration > Device Management > Inventory Collection > Device), you can edit, suspend, or, resume the device inventory collection schedule. (See Working with the Device Inventory Collection Schedule, page 15-54.)

Schedule inventory collection of phones

In the IP Phone Discovery Schedule page (Administration > Device Management > Inventory Collection > IP Phone), you can add, edit, or delete the IP phone discovery schedules. (See Working with IP Phone Discovery, page 15-55.)

Determine the Media Server account to use for your Cisco Unified CM access

To enable Operations Manager to access a Cisco Unified Communications Manager, you must supply the username and password for an account on the media server. See Determining the Media Server Account to Use for Cisco Unified Communications Manager Access, page 15-57.

View discovery status

You can view both device and phone discovery status, including Viewing and Scheduling Phone XML Discovery Status, page 15-57

Schedule inventory collection of cluster devices

In the Cluster Device Discovery page (Administration > Device Management > Inventory Collection > Cluster Device Discovery), you can add, edit, or delete the cluster device discovery schedules. (See Working with Cluster Device Discovery, page 15-40.)

Configure Simple Network Management Protocol (SNMP) parameters

To prevent Operations Manager timeouts, you can reset the SNMP parameters. See Editing SNMP Timeout and Retries, page 15-58.

Access parameters for Lightweight Directory Access Protocol (LDAP) servers

To connect to a Lightweight Directory Access Protocol (LDAP) server to access information for Operations Manager use, see Configuring LDAP, page 15-58.


Working with the Device Inventory Collection Schedule

You can perform the following tasks with the device inventory collection schedule:

Editing the Device Inventory Collection Schedule, page 15-54

Suspending and Resuming the Inventory Collection Schedule, page 15-55

Editing the Device Inventory Collection Schedule


Step 1 Select Administration > 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.


Suspending and Resuming the Inventory Collection Schedule

To suspend and resume the inventory collection schedule, select Administration > Device Management > Inventory Collection > Device.

The Device Inventory Collection page appears.

If the schedule is active and you want to stop it from performing inventory collection, click Suspend.

If the schedule is not active and you want Operations Manager to perform inventory collection at a scheduled time, click Resume.


Working with IP Phone Discovery

When you select Administration > Device Management > Inventory Collection > IP Phone, you can perform the following tasks:

Viewing IP Phone Collection Status, page 15-55

Adding an IP Phone Discovery Schedule, page 15-56

Editing an IP Phone Discovery Schedule, page 15-56

Deleting an IP Phone Discovery Schedule, page 15-56

Viewing IP Phone Collection Status

To view the IP Phone collection status, select Administration > Device Management > Inventory Collection > IP Phone.

The IP Phone Discovery Schedule page appears.

The IP Phone Collection Status pane displays the following:

Collection Status—Displays the status of the discovery process. The status could be any one of the following:

In progress—When you start PIFServer for the first time or restart it, discovery takes place automatically and the status appears as In Progress.

Complete—The discovery process is complete.

Not available. Try after some time—Appears when you start PIFServer for the first time, or restart it, and the discovery process has not yet begun.

Last Collection Start Time—Displays the start time of the last discovery.

Last Collection End Time—Displays the end time of the last discovery.


Adding an IP Phone Discovery Schedule


Step 1 Select Administration > Device Management > Inventory Collection > IP Phone.

The IP Phone Discovery Schedule page appears.

Step 2 Click Add.

The Add Schedule dialog box appears.

Step 3 Enter the following:

Name for the discovery schedule

Day of the week when you want discovery to occur

Time of the day when you want discovery to occur

Step 4 Click OK.


Editing an IP Phone Discovery Schedule


Step 1 Select Administration > Device Management > Inventory Collection > IP Phone.

The IP Phone Discovery Schedule page appears.

Step 2 Select the phone discovery schedule that you want to edit.

Step 3 Click Edit.

The Edit Discovery Schedule dialog box appears.

Step 4 You can change the following:

Name of the discovery schedule

Day of the week when you want discovery to occur

Time of the day when you want discovery to occur

Step 5 Click OK.

Step 6 After all your changes are done, click Apply.


Deleting an IP Phone Discovery Schedule


Step 1 Select Administration > Device Management > Inventory Collection > IP Phone.

The IP Phone Discovery Schedule page appears.

Step 2 Click Delete.

Step 3 In the confirmation box, click Yes.


Determining the Media Server Account to Use for Cisco Unified Communications Manager Access

To enable Operations Manager to access a Cisco Unified Communications Manager, you must supply the username and password for an account on the media server.

The account to use depends upon the Cisco Unified CM version and might also depend on whether multilevel administration access (MLA) is enabled for the Cisco Unified CM. Table 15-15 lists the options.

Table 15-15 Username and Password  for Accessing the Cisco Unified Communications Manager 

Cisco Unified Communications Manager Version on Media Server
MLA Enabled
or Disabled for Cisco Unified Communications Manager
Required Account

6.0 or later

Enabled

A multilevel administration access account with either full access or read-only access to the Standard Serviceability Functional Group.

Disabled

Valid Windows 2000 administrator account on the media server.


Viewing Discovery Status

In Operations Manager, you can view the discovery status of the devices and the phones being added.

To determine the discovery status of the devices that are being added, use the Device Management: Summary page. For details on accessing and understanding the Device Management: Summary page, see Checking Device States and Discovery Settings, page 15-17.

To view the discovery status of the XML phones that are being added, use the Phone XML Collection Status page. You can also change the schedule of phone discovery using this page. For details on accessing and understanding the Phone XML Collection Status page, see Viewing and Scheduling Phone XML Discovery Status, page 15-57.

Viewing and Scheduling Phone XML Discovery Status

To view the discovery status of the phones that are being added to Operations Manager or schedule when phone discovery takes place, you can use the Phone XML Collection page. The default scheduled start for phone XML discovery is daily at 3 p.m. Phone XML discovery collects serial number, load ID, and App ID for each phone.

To view the phone XML discovery status for the phones that are being added to Operations Manager and to schedule the phone XML discovery, you can use this Phone XML Collection page.


Step 1 Select Administration > Device Management > Inventory Collection > Phone XML.

The Phone XML Collection page appears.

Field
Description

Collection Status

Status of current collection process. States include: complete, pending, and scheduled.

Last Collection Start Time

Date and time when the last performed phone discovery started.

Last Collection Stop Time

Date and time when the last performed phone discovery stopped.

Phone XML Collection Schedule

Enables you to change the default 3 p.m. data collection.


Step 2 Click Apply to accept any scheduling changes.

Step 3 In the confirmation box, click OK.


Editing SNMP Timeout and Retries

If an SNMP query does not respond in time, Operations Manager will time out. It will then retry contacting the device for as many times as listed under the snmpretries attribute in the configuration file. The timeout period is doubled for every subsequent retry.

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

The SNMP timeout and retries are global settings.

The default values are:

Timeout—4 seconds

Retries—3


Step 1 Select Administration > Device Management > Inventory Collection > SNMP Configuration.

The SNMP Configuration page appears.

Step 2 Select a new SNMP timeout setting.

Step 3 Select a new Number of Retries setting.

Step 4 Click Apply.

Step 5 In the confirmation box, click Yes.


Configuring LDAP

The follow topics are covered in this section:

Adding an LDAP Server, page 15-59

Modifying LDAP Server Configuration, page 15-59

Deleting an LDAP Server, page 15-60

Adding an LDAP Server

Operations Manager can be configured to connect to a Lightweight Directory Access Protocol (LDAP) server, so that Operations Manager can access user information stored in the LDAP server.


Note LDAP servers that use SSL authentication are not supported by Operations Manager.


To add an LDAP server:


Step 1 Select Administration > Device Management > Inventory Collection > LDAP Configuration.

The LDAP Server Configuration page appears.

Step 2 Click Add.

The Add LDAP Server page opens.

Step 3 In the Connection Details area, do the following:

Enter the LDAP server name or IP address.

Enter the port number—Port used for LDAP requests on the LDAP server.

If you want to use anonymous login for authentication, select the Use Anonymous Login check box.

Enter an admin DN—If your LDAP server requires authentication for lookups, set this to the name of a user who has permission to search the subtree specified in the search base.

Enter the password for the LDAP server and reconfirm the password.

Enter a search base—Set this parameter to the search base for LDAP lookups. This search base should include all users who must be returned from the lookup.

Step 4 In LDAP Search Parameters, do the following:

Enter a name for the search.

Enter a telephone number—Enter the number as it is stored in the LDAP server.

Enter a telephone filter—Enter the exact telephone number prefix. This enables Operations Manager to get only extension number details for each person from the LDAP server.

This will be correlated with the extension number obtained from Cisco Unified Communications Manager, to display the username.

Step 5 Click Add.


Modifying LDAP Server Configuration


Step 1 Select Administration > Device Management > Inventory Collection > LDAP Configuration.

The LDAP Server Configuration page appears.

Step 2 Select the LDAP server that you want to change.

Step 3 Click Modify.

The Edit LDAP Server Configuration page appears.

In the LDAP Server Connection Details area, you can change the following:

LDAP server name or IP address.

Port number—Port used for LDAP requests on the LDAP server.

Whether to use anonymous login for authentication—Select or deselect the Use Anonymous Login check box.

An admin DN—If your LDAP server requires authentication for lookups, set this to the name of a user who has permission to search the subtree specified in the search base.

Password for the LDAP server—Be sure to reconfirm the password.

A search base—Set this parameter to the search base for LDAP lookups. This search base should include all users who must be returned from the lookup.

In the LDAP Search Parameters area, you can change the following:

Common name.

Telephone number—Enter the number as it is stored in the LDAP server.

Telephone filter—Enter the exact telephone number prefix. This enables Operations Manager to get only extension number details for each person from the LDAP server. This will be correlated with the extension number obtained from Cisco Unified Communications Manager, to display the username.

Step 4 Click Edit.


Deleting an LDAP Server


Step 1 Select Administration > Device Management > Inventory Collection > LDAP Configuration.

The LDAP Server Configuration page appears.

Step 2 Select the LDAP server that you want to delete.

Step 3 Click Delete.


Launching Operations Manager Tools

You can access several Operations Manager tools as well as external applications using the Tools menu.


Note You will have access to these tools only if you have proper authorization, according to either the CiscoWorks security model or CiscoSecure Access Control Server security model, depending on which your system is using. See Configuring Users (ACS and Non-ACS), page 19-29.


You may be able to do the following from Tools:

View event information for a device (see Viewing Event Information, page 15-62).

View event history for a device (see Viewing Event History, page 15-62).

View device information (see Viewing Device Information, page 15-62).

View associated phones for a Cisco Unified Communications Manager (see Viewing Associated Phones, page 15-62).

Launch the Path Analysis tool (see Launching the Path Analysis Tool, page 15-63).

View performance monitoring (see Viewing Performance Monitoring, page 15-65).

Set up synthetic tests on a device (see Setting Up Synthetic Tests, page 15-65).

Set up node-to-node tests on a device (see Setting Up Node-To-Node Tests, page 15-66).

Set up SRST monitoring for a device (see Setting Up SRST Monitoring, page 15-66).

Edit polling and threshold settings (see Configuring Threshold Settings, page 15-67 and Configuring Polling Settings, page 15-67).

Create user-defined groups (see Creating User-Defined Groups, page 15-69).

Launch administration pages for devices (see Launching Administration Pages for Devices, page 15-69).

Launch external applications (see Troubleshooting Service Level View, page 4-17).

Viewing Event Information


Step 1 In the map display pane or details window, right-click on the device for which you want to view event information.

Step 2 From the menu, select Event Details.

If the tool or application you want to launch does not appear in the menu, click the More Tools menu item. This launches a secondary menu.

The Event Details page for the selected device appears. For a description of the Event Details page, see Starting the Event Details Page, page 3-9.


Viewing Event History


Step 1 In the map display pane, right-click on the device for which you want to view event history.

Step 2 From the menu, select Event History.

If the tool or application you want to launch does not appear in the menu, click the More Tools menu item. This launches a secondary menu.

An Event History report for the selected device appears. For a description of the Event History report, see Understanding the Event History Report, page 11-8.


Viewing Device Information

To view device information:


Step 1 In the map display pane, right-click on the device for which you want to view information.

Step 2 From the menu, select Detailed Device View.

If the tool or application you want to launch does not appear in the menu, click the More Tools menu item. This launches a secondary menu.

The Detailed Device View for the selected device appears. For a description of the Detailed Device View, see Viewing Device Elements in Detail, page 15-47.


Viewing Associated Phones

You can view an associated phones report.

If you are viewing an associated phones report for a switch, the report displays the phones that are connected to the switch.

If you are viewing an associated phones report for a Cisco Unified Communications Manager or Cisco Unified Communications Manager Express, the report displays all phones that are registered to the Cisco Unified Communications Manager or Cisco Unified Communications Manager Express.


Note The Associated Phones report can be launched from either the Event Details page, or from the Detailed Device View page using the Tools Launch menu. (See Getting Device and Event Details, page 3-21, or Understanding the Layout of the Detailed Device View, page 15-44.)



Step 1 In the map display pane, right-click on the phone, Cisco Unified Communications Manager, or Cisco Unified Communications Manager Express for which you want to view associated phones.

Step 2 From the menu, select Phone Details.

If the tool or application you want to launch does not appear in the menu, click the More Tools menu item. This launches a secondary menu.

An Associated Phones report for the selected device appears. For a description of the IP Phone Detail reports, see Understanding Audio IP Phone Inventory Reports, page 12-14.


Launching the Path Analysis Tool

The Path Analysis tool provides hop-by-hop latency information for all the Layer 3 devices. It uses the ping path echo operation of IP SLA. The Path Analysis tool can be launched for any IP SLA-enabled device.

You can select an IP SLA-enabled source and/or a destination device from either the view pane or the map display pane and launch the tool.


Note The Path Analysis tool can also be launched from the Service Quality Events Detail page using the Tools Launch menu. (See Using the Service Quality Event Details Display, page 5-4.)



Step 1 In the map display pane, right-click on the device for which you want to run the Path Analysis tool.

To select multiple devices, use the Ctrl-click operation to select the devices, and then Ctrl-right click to open the menu.

Step 2 From the menu, select Path Analysis Tool.

The Path Analysis Tool page appears.

If the tool or application you want to launch does not appear in the menu, click the More Tools menu item. This launches a secondary menu.

Step 3 Verify that the source and destination devices are correct.

Step 4 Click Start Trace.

The Credentials for Source Device dialog box appears.

Step 5 Enter source devices' credentials.

Step 6 Click OK.

The tool runs and the results are displayed on the Path Analysis Tool page. Figure 15-9 shows an example of a Path Analysis tool.


Figure 15-9 Path Analysis Tool

Heading
Description

Hop ID

Hop ID.

Device IP Address

Device's IP address.

Device Type

Icon representing the type of device.

Status

Icon representing the status of the device.

Latency from Source

Latency in milliseconds.

Tools

Other Operations Manager tools that you can run on the device. This list will vary depending on the device. Some examples are:

Node-to-Node tests

SRST tests


Viewing Performance Monitoring

You can select and examine changes in network performance metrics. You can select, display, and chart network performance data in real time.


Step 1 In the map display pane, right-click on the device for which you want to view performance.

Step 2 From the menu, select Performance.

The Select Metrics dialog box appears.

Step 3 Select one or more desired metrics, and click Add.

A performance graph window appears, displaying one or more graphs (see Figure 6-1).

If the tool or application you want to launch does not appear in the menu, click the More Tools menu item. This launches a secondary menu.

Step 4 Select the metrics you want to graph.

The metrics must have the same units.

Step 5 Click View Graph.

A performance and capacity planning graph appears. For details about working with the performance graphs, see How to Use Performance Graphs, page 6-1.


Setting Up Synthetic Tests


Step 1 In the map display pane, right-click on the device for which you want to set up a synthetic test.

Step 2 From the menu, select a synthetic test.

Step 3 Your choices will vary depending on the device. For synthetic test details, see Getting Started with Synthetic Tests, page 8-1.

If the tool or application you want to launch does not appear in the menu, click the More Tools menu item. This launches a secondary menu.

The Create Synthetic Test page appears. For details on creating synthetic tests, see Creating Synthetic Tests, page 8-6.


Setting Up Node-To-Node Tests

To set up node-to-node tests:


Step 1 In the map display pane, right-click on the device for which you want to set up a node-to-node test.

Step 2 From the menu, select Node-to-Node Test.

If the tool or application you want to launch does not appear in the menu, click the More Tools menu item. This launches a secondary menu.

The Node-To-Node Test Configuration page appears. For details on creating node-to-node tests, see Creating a Single Node-To-Node Test, page 10-2.


Setting Up Node-To-Node Test Graphs


Step 1 In the map display pane, right-click on the device for which you want to set up a node-to-node test graph.

Step 2 From the menu, select Node-to-Node Test Graphs.

If the tool or application you want to launch does not appear in the menu, click the More Tools menu item. This launches a secondary menu.

The Node-To-Node Test Configuration page appears. For details on creating node-to-node tests, see Creating a Single Node-To-Node Test, page 10-2.


Setting Up SRST Monitoring


Step 1 In the map display pane, right-click on the device for which you want to set up SRST monitoring.

Step 2 From the menu, select Survivable Remote Site Telephony Test.

If the tool or application you want to launch does not appear in the menu, click the More Tools menu item. This launches a secondary menu.

The SRST Test Configuration page appears. For details on creating SRST tests, see Configuring a Single SRST Test as Needed, page 17-10.


Configuring Threshold Settings


Step 1 In the map display pane, right-click on the device for which you want to change the threshold settings.

Step 2 From the menu, select Threshold Parameters.

If the tool or application you want to launch does not appear in the menu, click the More Tools menu item. This launches a secondary menu.

The Managing Thresholds: Edit page appears. For details on editing thresholds, see Editing Operations Manager Thresholds, page 18-31.


Configuring Polling Settings


Step 1 In the map display pane, right-click on the device for which you want to change the polling settings.

Step 2 From the menu, select Polling Parameters.

If the tool or application you want to launch does not appear in the menu, click the More Tools menu item. This launches a secondary menu.

The Polling Parameters: Edit page appears. For details on editing polling parameters, see Editing Polling Parameters, page 18-14.


Suspending Devices


Step 1 In the map view pane, select the devices (use Ctrl-click to select the objects) that you want to suspend.

Step 2 Press Ctrl and right-click to open the menu.

Step 3 From the menu, select Suspend Device.

An informational dialog box appears.

Step 4 Click OK.


Resuming Devices


Step 1 In the map view pane, select the devices (use Ctrl-click to select the objects) that you want to resume.

Step 2 Press Ctrl and right-click to open the menu.

Step 3 From the menu, select Resume Device.

An informational dialog box appears, displaying a message similar to this:

Monitoring will be resumed for the selected 1 device(s). Be sure to apply your changes 
in the PTM UI. Click here to apply the changes. 

If you do not apply changes, the device will not be monitored. If you need to apply changes later, see Applying Changes, page 18-67.

Step 4 Click OK.


Adding a Device

If you can see a device that is not monitored in the Service Level View, you can add it to Operations Manager using this procedure.


Step 1 In the map display pane, select the Unmanaged Devices folder.

The Unmanaged Devices report displays.

Step 2 Select a device or multiple devices to add and click Add.

The Add Devices dialog box appears, displaying the IP address (or addresses) for the devices that you selected in the Device Information field.

Step 3 Enter credentials for the device.

Step 4 Click OK.

The devices are added.


Deleting Devices


Step 1 In the map display pane, select the devices that you want to delete.

Step 2 Use Ctrl-click to select the objects in the View pane.

Step 3 Press Ctrl and right-click to open the menu.

Step 4 From the menu, select Delete Device.

A confirmation dialog box appears.

Step 5 Click Yes.

The devices are deleted.


For more information, see Deleting Devices, page 15-52.

Creating User-Defined Groups

Service Level View provides you with a quick way to create a new user-defined group, by selecting either devices or groups. You cannot edit existing user-defined groups or create rules for populating groups through this page.

Administrative grouping activities are performed from the Group Administration and Configuration page (for details, see Managing Groups, page 16-1.)


Step 1 In the map display pane, select the devices or groups (use Ctrl-click to select the objects) that you want to group.

Step 2 Press Ctrl and right-click to open the menu.

Step 3 From the menu, select Group Devices.

The Create Group menu appears.

If the tool or application you want to launch does not appear in the menu, click the More Tools menu item. This launches a secondary menu.

Step 4 Do the following:

Enter a group name

(Optional) Enter a description

Select which dashboard displays you want the group to appear in as a view

Step 5 Click Create.


Launching Administration Pages for Devices

Service Level View provides you with links to the administration pages of the monitored devices. The availability of these pages depends on the device type. For example, Cisco Unified Communications Manager and Cisco Unity devices provide access to their administration pages.In the map display pane, right-click on the device whose administration page you want to open.


Step 1 In the map display pane, right-click on the device whose administration page you want to open.

Step 2 From the menu, select the administration page link.

The following list shows the possible options (depending on the device):

Cisco Emergency Responder Administration

Cisco IP Contact Center Administration

Cisco MeetingPlace Express Administration

Cisco Unified Communications Manager Administration

Cisco Unified Communications Manager Express Administration

Cisco Unified Communications Manager Serviceability

Cisco Unified Presence Server Administration

Cisco Unified SIP Proxy Server Administration

Cisco Unity Administration

Cisco Unity Connection Administration

Cisco Unity Express Administration

Gateway Administration

TelePresence

If the tool or application you want to launch does not appear in the menu, click the More Tools menu item. This launches a secondary menu.

The administration page opens.


NAT Support in Operations Manager

In certain deployments, Operations Manager may be behind a gateway. If your deployment includes this scenario and you want to support NAT, you must first set up support for NAT in Operations Manager.

Use the following list of actions to configure Operations Manager and your devices behind gateways:

To add a device into Operations Manager that allows you to input and collect information about NAT IP, Private IP, and Domain/Host Name on the Device information page, you must enable Static NAT Environment on the System Preferences page.

Select the Static NAT Environment check box to add Local IP and NAT mode IP in the Device Add page.

To use an import seed file that supports NAT-enabled devices, you must append two new columns to each line for NAT-enabled devices.

The first column is user_defined_field_3 which corresponds to the Local IP attribute. The second column is user_defined_field_2 which corresponds to the Local DNS Name attribute. These columns are optional and can be empty for devices that do not have NAT enabled.

There are limitations to NAT support in Operations Manager. Some of the limitations are listed in the specific online help sections, while others are listed below:

Service Level View > Unmanaged Devices page will list only Local IP Addresses for devices in NAT mode, but may display the Call Manager name on this page, if you have configured the DNS name for the device. As a result, adding an unmanaged NAT-enabled device from this page may fail.

Any information collected through phone polling is not collected for Unified CMs in a NAT environment. For details, see Understanding Phone Polling, page 12-33.

If you use the import seed file to import devices into the DCR, you must include the attributes for Local IP and Local DNS Name. See Importing Devices into Operations Manager, page 15-19.