User Guide for Cisco Unified Operations Manager 2.1
Using Device Management
Downloads: This chapterpdf (PDF - 569.0KB) The complete bookPDF (PDF - 11.8MB) | Feedback

Using Device Management

Table Of Contents

Using Device Management

Getting Started with Device Management

Device Prerequisites

Types of Devices that Operations Manager Monitors

Ports and Interfaces that Operations Manager Monitors

Understanding the Device and Credentials Repository

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

Understanding the Device Summary and Device States

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?

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

Understanding Device Reports

Suspending/Resuming Devices

Deleting Devices

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

Adding an LDAP Server

Modifying LDAP Server Configuration

Deleting an LDAP Server


Using Device Management


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

Getting Started with Device Management

Understanding the Device Summary and Device States

Importing Devices into Operations Manager

Working with Device Management

Getting Started with Device Management

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


Note When Operations Manager is installed, it automatically synchronizes with the DCR and adds inventory. This is the default setting.


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


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



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


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

Add or import devices into the DCR (see Adding Devices to the DCR, or Importing Devices into the DCR).

Export device information to a file (see Exporting Device Information from the DCR to a File).

Edit device configuration (see Editing Device Configuration and Credentials).

Delete devices (see Deleting Devices).

Select devices to be added to Operations Manager from the DCR (see Importing Devices from the DCR).

View device details (see Viewing Device Details).

Perform inventory collection on devices (see Performing Manual Inventory Collection on Devices).

Suspend and resume Operations Manager device management (see Suspending/Resuming Devices).

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 for details). Once 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).

Device Prerequisites

When working with device management, remember 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. The only way that you will know that this device is unreachable, is when an Unreachable alert appears for this device in the Alerts and Events display.

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

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, refer to Device-Based Filtering, page 20-22.

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 Windows 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 Views and Reports?, page 1-19.

If a UC500 Series router is running Communications Manager 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 Communications Manager Express.

Starting in release 2.1, for a Cisco Unity Express that is attached to a Unified Communications Manager 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.

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-3

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 3-27).

For information on how many devices Operations Manager can manage, refer to 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-24.

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. (For devices with no specified device type, 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 17-1 on page 17-3.


Note 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 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).


Once a device is added to the DCR, you can add it to the Operations Manager inventory (the Operations Manager inventory is separate from the DCR). When a device is added to the DCR, the DCR assigns a DCR ID to every managed component.The DCR maps components to devices using either the device name or 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 16-3).

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

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

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

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

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

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


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


Adding Devices to the DCR

Add devices to the DCR from the Operations Manager Add Devices page (Devices > Device Management > Add Devices).

Figure 16-1 shows an example of the Add Devices page.

Figure 16-1 Add Devices Page


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



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


Note You can also access the Add Devices page from the Discovered Devices report. (See Viewing the Discovered Devices Report.)


Step 2 Enter the following:

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


Note When 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)

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


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

Depending on your software, perform one of the following procedures to create a read-only Cisco Unified Communications Manager user account:

Creating a Read-Only Cisco Unified Communications Manager 4.x User Account (Windows)

Creating a Read-Only Cisco Unified Communications Manager 5.0 and Above User Account (Linux)

Creating a Read-Only Cisco Unified Communications Manager 4.x User Account (Windows)

Use the following procedure to set up a read-only user account that allows polling of your Unified Communications Manager device (version 4.x).


Step 1 Create a new read-only user (for example, cuomuser) on the CCMAdmin Page, by selecting Users > Add a new User.

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

Step 3 Assign the new read-only user to a Read Only user group (CUOM Access) by selecting Users > Access Rights > Assign Privileges to User Group.

Step 4 Enable multi-level admin (MLA) on the Cisco Unified Communications Manager by selecting Users > Access Rights > Configure MLA Parameters.

Step 5 Restart the Tomcat Web Service on the Communications Manager by selecting Cisco Unified CallManager Serviceability > Tools > Control Center.

Step 6 Log into Operations Manager as the read-only user and add the Communications Manager by selecting Devices > Device Management > Add Devices.


Creating a Read-Only Cisco Unified Communications Manager 5.0 and Above User Account (Linux)

Use the following procedure to set up a read-only user account that allows polling of your Unified Communications Manager device (version 5.0 and above).

Procedure


Step 1 Create a new read-only application user (for example, cuomuser) on the CCMAdmin page by selecting User Management > Application User and clicking Add New after entering the new application user name.

Step 2 Create a new user group that contains the new read-only user (for example, CUOM Access) by selecting User Management > User Group, then enter Standard CCM Read Only and click the Copy icon (see Figure 16-2). Enter your new user group, for example, CUOM Access, and click OK.

Figure 16-2

User Group Copy Window

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

Step 4 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 16-3). Then click Assign Role to Group in the window that displays. Add Standard AXL API Access and click Save.

Figure 16-3

Roles Icon in User Group Window

Step 5 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 6 Log into Operations Manager as the read-only user and add the Communications Manager by selecting Devices > Device Management > 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.

Procedure


Step 1 Log in to 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, and then click OK.

Step 4 To set the permission for the user, right-click WMI Control, click on Properties, click on the Security tab.

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

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

Step 7 Select the following permissions from the permission window:

Execute Method

Enable Account

Remote Enable

Read Security

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


Configuring Operations Manager Physical Discovery

Procedure


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


Note 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).

Step 3 Enter the following:

Target devices wild card entry. Multiple devices can be entered at one 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.


SNMP timeout and retries

SNMPv2c/SNMPv1 credentials

SNMPv3 credentials

HTTP credentials (only required for Cisco Unified Communications Manager)

WMI 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


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.

Procedure


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

Step 2 Click Add.


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


Step 3 Enter the following:

IP address or hostname. Multiple devices can be entered at 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

SNMPv3 credentials

HTTP credentials (only required for Cisco Unified Communications Manager)

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

Procedure


Step 1 Select Devices > 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:

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

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


Note 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

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


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

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

When selecting the Use Ping Sweep check box, specify a comma-separated list of IP address ranges using the /netmask specification. For example, use 172.20.57.1/24 to specify a ping sweep range starting from 172.20.57.1 and ending at 172.20.57.255.


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


4. Select the Filters radio button and enter the filter information. Table 16-1 describes the optional filters that are available to you when running physical discovery. Click Advanced Filters to display additional filter options.

Table 16-1 Physical Discovery Filters 

Filter
Description

IP Address

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

Include—In the auto-discovery process.

Exclude—From the auto-discovery process.

You can use wildcards when specifying the IP address range.

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

For example:

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

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

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

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.

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

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

*.?abc.com matches any DNS name ending with .aabc.com, 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.

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


Step 3 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.


Importing Devices into the DCR

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

Procedure


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

Step 2 Enter the import information.


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

Procedure


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

Step 2 Enter the export information.


Note If you need help exporting, 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.



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

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

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. First, 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.


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

net stop crmdmgtd
net start crmdmgtd

For more information on the DCR master/slave model, refer to the Common Services 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 In the Device Selection page, set device selection to manual. (See Manually Importing DCR Devices.)

Step 2 Configure Operations Manager as a slave server. (For information on configuring the DCR master/slave model, refer to the Common Services online help.)

All the devices will be present 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.


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


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



Understanding the Device Summary and Device States

The Device Management: Summary page lists the device states for all devices in the Operations Manager inventory. The Device Management: Summary page appears when you select Devices > Device Management. Figure 16-4 shows an example of the Device Management: Summary page.

Figure 16-4 Device Management: Summary Page

Table 16-2 describes the information displayed on the Device Management: Summary page.

Table 16-2 Device Management: Summary Page 

Heading/Button
Description

State

Lists the state the devices are in, from the following possibilities:

Monitored

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

Partially Monitored

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

Monitoring Suspended

Monitoring of the device is suspended.

Inventory Collection in Progress

Operations Manager is probing the device. This is the beginning state, when the device is first added; a device is also in this state during periodic inventory collection. Some of the data collectors may still be gathering device information.

Unreachable

Operations Manager cannot manage the device. See Troubleshooting Import and Inventory Collection.

Unsupported

The 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

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

Total Phones

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

Device Selection

The current mode for device selection from the DCR. See Importing Devices into Operations Manager.

Last Discovery

The date and time when last performed physical discovery.

Next Discovery

The date and time when will next perform physical discovery.

Configure

To configure physical discovery. See Adding Devices to the DCR.

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

Using manual synchronization between the DCR and Operations Manager (see Manually Importing DCR Devices)


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


Importing Devices from the DCR

Once 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 Devices > Device Management, and check the Device Selection setting.


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 16-3 shows how Operations Manager names devices, depending on how the devices are added to the DCR.

Table 16-3 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

DNS name only

Uses the DNS name, even if not resolvable

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.

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.



Note Once 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 Appendix G, "Polling—SNMP and ICMP."

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 16-4 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.


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 Select Devices > Device Management > Device Selection. The Device Selection page appears.

Step 2 Activate the automatic radio button.

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

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


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




Note 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 20-13. For information about device-based licensing, see Responding to Messages About Device Limits, page 1-24.


For information about the inventory collection schedule, see Scheduling Inventory Collection.

Manually Importing DCR Devices

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


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

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

Step 3 Select devices the following ways:

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

Using the group selector.

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

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

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


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




Note 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 20-13. For information about device-based licensing, see Responding to Messages About Device Limits, page 1-24.


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

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:

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

The 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 on how to access the Device Selection page.

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

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.

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.


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



Step 1 Select Devices > Device Management > IP Address Report. The IP Address Report page appears. Figure 16-5 shows an example of the IP Address Report page.


Note For deleting duplicate devices, Deleting Devices.



Figure 16-5 IP Address Report Page

Table 16-5 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.


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 Devices > Device Management > Modify/Delete Devices. The Modify/Delete Devices page opens. Figure 16-6 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. The 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.


Note For a complete explanation of the device states, see Understanding the Device Summary and Device States.


Step 4 If the device is not in the Monitored state, refer to Troubleshooting Import and Inventory Collection.



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


Note If device inventory collection or discovery is being performed over a slow network connection, or if the devices are unusually slow in responding to SNMP or HTTP requests, you can change the ivr.properties file to 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.



Note 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 the following:

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

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

Why Does a Device Go into the Partially Monitored State?

Why Does a Device Go Into the Unreachable State?


Step 1 Select Devices > Device Management > Modify/Delete Devices. The Modify/Delete Devices page opens. Figure 16-6 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).

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

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

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 16-6 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 may go into the partially monitored state

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

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.

Table 16-6 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.

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

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

5. 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 = CCM Authentication Failure

Error Message = Success:WrongCredentials

This message indicates that either the Cisco Unified Communications Manager 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 Unified Communications Manager Admin page.

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

3. Rediscover the device.

Error Code= CCM Authentication Failure

Error Message= Success:UnknownCredentialError

This message indicates that SNMP management MIBs are not responding. The specific error could be one of the following:

MIB-2—The ipAddressTable is not responding.

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

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

1. If the MIB-2 is not responding, restart the SNMP Agent on the system and rediscover the device.

2. If the CISCO-CCM-MIB is not responding, restart the Cisco Unified Communications Manager Service.

3. Rediscover the device.

Error Code = CCM 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 Unified Communications Manager Admin page.

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

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

Error Code = CCM Authentication Failure

Error Message = Success: HTTPSCertificateNotImported

The Cisco Unified Communications Manager certificate download has failed.

Do the following:

1. Check the size of the cacerts file located at C:\PROGRA~1\CSCOpx\lib\jre\lib\security\cacerts. If the file size is not zero, then try to delete and add the Cisco Unified Communications Manager node in question.

2. If the file size is zero, then follow the below steps:

a. Delete the device [Cisco Unified Communications Manager] completely from Operations Manager and CS [Device .. Device .. Management .. Modify/Delete Devices link].

b. Enter pdterm InventoryCollector.

c. Copy C:\PROGRA~1\CSCOpx\setup\dependency\jre2\lib\security\cacerts. C:\PROGRA~1\CSCOpx\lib\jre\lib\security\cacerts.

d. Change the directory to the following:

cd C:\PROGRA~1\CSCOpx\lib\jre\lib\security

e. Copy IPToHostName.txt IPToHostName.txt.orig.

f. Delete IPToHostName.txt.

g. Enter pdexec InventoryCollector.

h. Read the device [Cisco Unified Communications Manager].

i. If after you complete the previous steps, the Cisco Unified Communications Manager nodes are still partially monitored due to insufficient credentials, follow the procedures to manually import the security certificates in Operations Manager. See Cisco Unified Operations Manager 2.0 Deployment Best Practices on Cisco.com for details on how to repair Cisco Unified Communications Manager nodes that are partially monitored due to insufficient credentials.


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.

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 Select Devices > Device Management > 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

Understanding the Modify/Delete Devices Page

Editing Device Configuration and Credentials

Performing Manual Inventory Collection on Devices

Viewing Device Details

Suspending/Resuming Devices

Deleting Devices

Scheduling Inventory Collection

Viewing Discovery Status

Editing SNMP Timeout and Retries

Configuring LDAP

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 16-6 shows the Modify/Delete Devices page.

Figure 16-6 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.


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. Figure 16-7 shows an example of the device selector.

Figure 16-7 Modify/Delete Devices Selector

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?).

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?).

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

Viewing Device Details

Suspending/Resuming Devices

Deleting Devices

Scheduling Inventory Collection

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



Step 1 Select Devices > Device Management > Modify/Delete Devices. The Modify/Delete Devices page opens. Figure 16-6 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.


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


Step 5 You can update the following credentials:

SNMPv2c/SNMPv1

SNMPv3

HTTP

WMI


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


Step 6 Click OK.


Performing Manual Inventory Collection on Devices

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


Note Configuration changes on a device are discovered by Operations Manager only during discovery (inventory collection) of the device. Therefore any changes to a device's configuration 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.


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


The following events will also trigger inventory collection:

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

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

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


Note If you are using the ACS login module, the System Identity user that is configured in ACS should have 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 Devices > Device Management > Modify/Delete Devices. The Modify/Delete Devices page appears.

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

Step 3 Click Rediscover. Inventory collection is started.


Viewing Device Details

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

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

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

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


Note 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 Viewing Device Elements in Detail, page 3-22.)


Figure 16-7 shows an example of the Modify/Delete Devices page. Devices are organized in folders according to their device state. (See Understanding the Device Summary and Device States.)

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


Step 1 Select Devices > Device Management > 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 Select Devices > Device Management. 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 for information on selecting devices.


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


Figure 16-8 shows an example of a device report.

Figure 16-8 Device Report

Table 16-7 describes the information displayed in a device report.

Table 16-7 Device Report 

Heading/Button
Description

Device Type

Device type.

Device Name

Device name. Link to the Detailed Device View for the device. Clicking the link opens a Detailed Device View for the device. See Understanding the Layout of the Detailed Device View, page 3-20.

IP Address

Device IP address.

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

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

Last Inventory Collection

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

Downloads the Device Details display to a file on your computer.

Displays the report in a printer-friendly format.

Opens the Operations Manager online help.

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.


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.

When you suspend a device, the active alerts and events on the device are moved to the Cleared state. No suspended management events are generated. The suspended alert information moves from the All Alerts view to the Suspended Devices view. The status of the suspended alert is cleared and the latest event category displays as suspended. The alert is removed within 30 to 60 minutes if the corresponding device status is not resumed within this timeframe.

When you resume a device, Operations Manager resumes the processing of events for that device. No resumed management events are generated on resuming the device. The status of the alert is cleared and the latest event category displays Resumed if there are no active events for that device. An alert for a resumed device is a special case when you can see an alert with zero events. If the resumed device has active events (which means the problem exists in the device), then the status of the resumed alert will be active and latest event category will be updated as per the event category. If you resume a device after a suspended alert has been purged, then a new alert is generated after resuming a device; alternately, the same suspended alert is updated.


Note You can also suspend or resume the monitoring of devices in the following ways:

From a device report. See Understanding Device Reports.

Through the Detailed Device View. From here, you can suspend a device or specific device components. For more information on using the Detailed Device View to suspend device monitoring, see the following:

Suspending/Resuming Devices, page 3-26

Suspending/Resuming a Device Component, page 3-27



Step 1 Select Devices > Device Management > 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 19-60).



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.

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.

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.

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

When a Cisco Unity or a Unified Contact Center device is deleted from Operations Manager, RPC keepalive packets will continue to be exchanged between the device and Operations Manager until either the Operations Manager or the device is restarted.

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 alerts and events from the Alerts and Events displays. 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 Devices > Device Management > Modify/Delete Devices. Select the device by clicking on the checkbox, then click Delete. By deleting the device in Operations Manager, all the existing events in the Alerts and Events display will also be removed.


Note Your login determines whether you can perform this operation.



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


Scheduling Inventory Collection

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

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

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

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

Suspending and Resuming the Inventory Collection Schedule

Editing the Device Inventory Collection Schedule


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

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

Step 3 Change the desired scheduling information.

Step 4 Click OK.

Step 5 Click Yes.


Suspending and Resuming the Inventory Collection Schedule


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

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

Step 3 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 Devices > Device Management > Inventory Collection > IP Phone, you can perform the following tasks:

Viewing IP Phone Collection Status

Adding an IP Phone Discovery Schedule

Editing an IP Phone Discovery Schedule

Deleting an IP Phone Discovery Schedule

Viewing IP Phone Collection Status


Step 1 Select Devices > 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 Devices > 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:

A name for the discovery schedule

The day of the week when you want discovery to occur

The time of the day when you want discovery to occur

Step 4 Click OK.


Editing an IP Phone Discovery Schedule


Step 1 Select Devices > 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:

The name of the discovery schedule

The day of the week when you want discovery to occur

The time of the day when you want discovery to occur

Step 5 Click OK.

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


Deleting an IP Phone Discovery Schedule


Step 1 Select Devices > 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 Communications Manager version and might also depend on whether multilevel administration access (MLA) is enabled for the Cisco Unified Communications Manager. Table 16-8 lists the options.

Table 16-8 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

Earlier than 4.0

Enabled or disabled

Valid Windows 2000 administrator account on the media server.

4.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 use the Device Management: Summary page to determine the discovery status of the devices that are being added. For details on accessing and understanding the Device Management: Summary page, see Understanding the Device Summary and Device States.

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 Devices > 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

Adding an LDAP Server

Modifying LDAP Server Configuration

Deleting an LDAP Server

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.



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

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

The LDAP server name or IP address.

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

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

Step 5 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 6 Click Edit.


Deleting an LDAP Server


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