Cisco Prime Collaboration Assurance Guide - Advanced, 10.0
Managing Inventory
Downloads: This chapterpdf (PDF - 1.67MB) The complete bookPDF (PDF - 8.14MB) | Feedback

Managing Inventory

Managing Inventory

Cisco Prime Collaboration performs continuous, real-time discovery of device inventory. You need to periodically update the inventory so that you have up-to-date information about your network. You can schedule how often you want to update inventory.

When you update inventory, the inventory synchronizes with the Prime Collaboration database. The Prime Collaboration inventory reflects every addition, deletion, and modification that occurs in the network after update.

View Inventory Details

In Prime Collaboration, devices are grouped based on the device type. The Device Group pane is available in the Device Work Center, Session Diagnostics (as a filter), Endpoint Diagnostics, and Alarms, and Events pages. You can select devices or endpoints from the groups you are interested in, to check inventory details, and to monitor sessions, endpoints, alarms, and events.

You can hover over the device host name column in the inventory table, and click the Device 360 ° view to see device details, such as alarms, interfaces, ports, environments, modules and other device-specific capabilities of that device. For more information, see Device 360 ° View.

In addition to the inventory table, the Device Work Center page contains System Information, Access Information, Interface Information, and Event Settings panes that appear below the inventory table. All of these panes are populated based on the last polled data. A device must be in the Managed state at least once for these details to be displayed.

Inventory Pane

The inventory table is available on the Device Work Center page; choose Operate > Device Work Center.

Each device that is managed by Prime Collaboration is modeled to display the physical inventory of a device (interface and peripherals). To view the inventory details for a device, click on a row in the Current Inventory pane.

To select multiple devices (first 500 entries), use the check box available on the top left corner of the Current Inventory pane.

You can change the visibility settings of the devices using the Edit option. This is enabled only for endpoints, predefined groups and userdefined groups. The visibility settings of the device can be changed only if the device is in the Managed state. Any change in visibility settings appear in the Session Diagnostics page. For more information, see Session Diagnostics.

You can modify the credentials and rediscover devices using the Modify Credentials option. Click on Job Progress in the confirmation message window and cross launch to the Jobs Management page to see the details of the discovery job.

You can change the event settings of the devices using the Customize Events option.

You can edit the Jitter, Average Period Latency, and Rx Packet Loss threshold settings of all devices except infrastructure devices using the Threshold Settings option. You can enable, disable or set different options for automatic troubleshooting using the Threshold Settings option.

You can suspend and resume the management of the device using the Suspend and Resume options. Inventory is not updated for devices in the Suspended state.

You can use the show drop-down list on the inventory table to filter devices based on the device type and state. For example, if you want to rediscover all deleted devices in your network, select Deleted from the show drop-down list. The inventory table will list all deleted devices. Perform rediscovery to discover these devices.

There are options such as Quick Filters, Advanced Filters to filter devices based on the device criteria. See Managing Device Groups.

The Total field in the upper right corner of the inventory table displays the device count. To view the number of devices in a group, select the group.

For example, to view the number of phone endpoints, select the Endpoints group in Device Group. The number of endpoints will be updated in the Total field. For more information on the device count, see the Field Descriptions for the Current Inventory table.

This table describes the fields on the Inventory table. Not all columns of the inventory table appear by default. To see all the columns, click the Settings option on the top right corner. You can export the inventory table as a CSV or a PDF file by clicking the Export icon at the upper right corner of the inventory table.

Table 1 Field Descriptions for the Current Inventory Table

Field

Description

Endpoint Name

Name assigned to the endpoint for ease of identification.

Extension

Directory Number of endpoints. This number helps to identify a device uniquely.

Phone Description

A unique description of the endpoints that you have added during configuring the devices on Cisco Unified Communications Manager (CUCM) or Cisco TelePresence Video Communication Server (VCS).

Host Name

Name assigned to the device for ease of identification.

Model

Device model, such as Catalyst3506G48PS.

IP Address

IP address used for managing the device. Click on the IP address to log into the device. Click on the quick view icon to launch the Device 360 Degree View for that device.

For routers and switches, you must associate a terminal client application, such as Putty, to log into the device.

Mac Address

MAC Address of the devices.

Software Type

Software running on the device, such as IOS, CatOS.

Software Version

Software version running on the device.

Device Pool

Only for CUCM registered devices.

Partition

Only for CUCM registered endpoints.

Serial Number

Applicable only for endpoints.

State

Status of the device.

Status Reason

Reason for the device status.

Type

The most applicable role or service of the device.

Capabilities

All other roles or services of the device.

Last Discovered

Date and time when the device was last discovered. The time will be according to the time zone set in the Prime Collaboration server.

Visibility

  • Not Applicable—Realtime visibility is not supported for this device.
  • Limited or Full visibility—Displayed only for endpoints, based on the visibility settings.

Customized Events

  • Green check mark displayed—Event settings are customized for the device using Customize Events tab.
  • Green check mark not displayed—Event settings are not customized for the device. The device uses global settings.

Mediatrace Role

  • Unsupported—Device does not support Cisco Mediatrace.
  • Transparent—Device supports Cisco Mediatrace but profile is not configured.
  • Responder—Cisco Mediatrace responder profile is enabled on the device. Enable this profile if you want to monitor and collect information on Cisco Mediatrace.
  • Initiator—Cisco Mediatrace initiator profile is enabled on the device. Enable this profile if you want to initiate Cisco Mediatrace sessions or polls.
  • Initiator/Responder—Cisco Mediatrace initiator and responder profiles are enabled on the device.

IP SLA Role

  • Unsupported—Device does not support Video IP SLA.
  • Not Configured—Device supports the Video IP SLA but the device is not configured.
  • Responder—IP SLA Responder profile is configured on the device. The device that is configured with this profile processes measurement packets and provides detailed time stamp information. The responder can send information about the destination device’s processing delay back to the source Cisco router.

Performance Monitor

  • Unsupported—Device does not support Cisco Performance Monitor.
  • Not Configured—Device supports Cisco Performance Monitor but the device is not configured.
  • Configured—Cisco Performance Monitor is enabled to allow you to monitor the flow of packets in your network and become aware of any issues that might impact the flow.

Device 360° View

You can get a concise summary information regarding any device through its 360° view. Rest your mouse over a device IP address, then click the quick view icon to launch the Device 360° View window. You can also do a global search for a device to see the device details in the Device 360° View.

In addition to viewing device information such as status, location, you can also view modules, alarms, and interfaces on the device, invoke tools like ping, and traceroute for that device. You can also raise a TAC case and post a question in the support community.


Note


If you are using Internet Explorer 9, ensure that you have the recommended browser settings to view the Device 360° View window. Press F12 in your browser and set the following:
  • IE9 Browser Mode: IE9 Compat View
  • Document Mode: IE9 standards

Launch the browser again to view the Device 360° view window


The 360° Device View window contains the following device details:

Table 2 Field/Buttons and their Description

Field

Descriptions

State

You can hover on the State icon to know the state of the device. Different colors of the icon represent different states.

Status Reason

You can hover over the icon to know the status reason of the device and any additional activities you need to perform to make all features work. Different colors of the icon correspond to the state the device is in.

Host Name

Host IP /Global IP Address

You can click the IP address to launch the device management page. To log into routers and switches, ensure that you click on the IP address and associate a terminal client application, such as TELNET or SSH.

MAC Address

MAC address of the device.

Type

The device type or primary role or capability of the device is mentioned on the right corner below the hostname row. For example, Finesse, CUCM or Unity Connection.

Version

Software version of the device.

Last discovered

Time stamp of last successful discovery.

Cluster ID

Cluster ID of the cluster the device belongs to. You can click on the cluster ID to launch the Cluster Details page.

Click the support community icon to open the Cisco Support Community Dialog box which has the related posts and discussions filtered for the device. You can post a question for that device.

You can go to the support pages of other devices, and also visit the support community page of Prime Collaboration. To visit the Prime Collaboration page, click Visit the Cisco Support Community, click on Navigate to a Community Topic and Post pane, then click Collaboration, Voice and Video. In the Collaboration, Voice and Video Communities table, click Prime Collaboration Management.

You can post questions in the Cisco Prime Collaboration Community forum, and look for related questions or information in existing discussions, videos, and additional documents for your issues.

For business impacting technical issues, we recommend that you open a service request with Cisco TAC for timely support.

Click the support case icon to raise a support case for this device. You need cisco.com login credentials to do this. For more information, see Contacting Cisco Technical Assistance Center for Support.

Click the ping icon to ping the device and get ping statistics, such as the number of packets transmitted and received, packet loss (in percentage), and the time taken to reach the device by ping in milliseconds (ms).

Click the traceroute icon to know the route to reach the device, the number of hops to reach the device, and the time elapsed at each hop in milliseconds (ms).

Click the tasks icon, and select from the drop-down list to perform multiple tasks such as launching performance graphs and managing thresholds.
Note   

The options available depend on the device you have selected.

Other device-specific information is as follows:

Table 3 Device 360° View - Tabs Description

Tabs

Description

Alarms

It includes the following:
  • Severity—Severity of the alarm
  • Status—Status of the alarm
  • Name—Name of the device
  • Component—Name of the component that has alarms
  • Last Updated—Time stamp of the last alarm generation.

Interfaces

It includes details on interfaces, voice interface and port (whichever applicable for the device). It specifies the card is playing on a particular port, and the capability of the card. The following information is available for the interface, voice interface and port:

  • Operation Status—Operational state of the device
  • Admin Status—Administrative status of the interface
  • Name—Description of the device
  • Address—Physical address of the device
  • Type—Device type

Card/Services

It includes the following:

  • Name—Description of the voice/service
  • Version—Version of the card/service
  • Status—Status of the card/service

Port

Environment

It includes:

  • Power supply
  • Fan
  • Temperature sensor
  • Voltage sensor

Device-specific details


Note


The fields displayed depend on the device you have selected.


Metric Charts

You can view metric charts for voice devices (excluding phones) and CTS. These charts appear only for devices in managed state and for which at least one poling cycle is over.


Note


It will take time for the chart to appear after the device is in managed state. This is because polling has to be completed to fetch data for these charts.

These charts display values for CPU, Memory and Hard Disk utilization etc. You can view maximum, minimum and current value (in percentage or bytes in MB) of the last hour. Each bar on the metric chart denotes a period of four minutes, thus there are 15 bars, each denoting the value for four minutes. The figures in brown represent the minimum value, and the figures in blue represent the maximum value for the last hour.

You can click See More to launch performance graphs for some devices.


Note


The metric charts and performance graphs availability depend on the device you have selected.

System Information

The System Information pane contains the credential details for all devices except the TelePresence Server:

Field

Description

Object ID

System Object ID of the endpoint.

Up Time

Duration for which the device has been running.

Contact

Contact details of the endpoint.

Location

System location of the endpoint.

Primary Capability

Primary service running on the device.

Capabilities

All other services (other than primary service) running on the device.

Detailed Device View

The Detailed Device View opens a detailed view of the device (as a popup window). This view is available as a link in the System Information pane.

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 CM, Voice Services, Work Flow, Synthetic Tests, and so on.
  • Suspend or resume management of a device or a device component so the device is no longer polled, or polling is resumed.
  • Launch other tools such as performance graphs, Diagnostic View, and so on.

If you have reset the Managed State of any device components (such as Interfaces, Environment or System) in Detailed Device View, ensure that you save the changes. To save the changes, go to Administration > System Setup > Polling & Threshold > UC Polling & Threshold Priority Setting page, click Save, and then click Apply. These changes will be saved in the database and will appear in the Detailed Device View after the next polling cycle.

Diagnostic View

You can view the important statistics and details of this and other network management applications that are installed on your network management server, on a single page instead of navigating through several pages to view the required data.

In the Device Work Center page, the Diagnostic View links are available only for voice network devices such as Cisco Unified CM clusters, Cisco Unified CMs, Cisco Unity Connection, Cisco Unified Presence, Voice Gateway, and so on. These views are not available for video network devices (such as Cisco VCS, TelePresence, and so on) and phone endpoints.

Access Information

The Access Information pane contains the following details for all devices:

Field

Description

Credential Profile Name

Credential profile used for the selected device for discovery.

SNMP Access Level

If you have defined SNMP credentials in the Credential Profiles, Read Only is displayed.

SNMP Version

Defined SNMP version in the Credential Profiles.

CLI Access Level

If you have defined CLI credentials, Prime Collaboration checks whether the access level is Read Only or Read Write. The appropriate value is displayed based on the verification.

This field is not displayed if the credential is not mandatory for Prime Collaboration.

HTTP Access Level

If you have defined the HTTP credentials in the Credential Profiles, Read Only is displayed.

This field is not displayed if the credential is not mandatory for Prime Collaboration.

JTAPI Access Level

If you have defined the JTAPI credentials in the Credential Profiles, Read Only is displayed.

This field is not displayed if the credential is not mandatory for Prime Collaboration.

Interface Information

The Interface Information pane contains the following details for CTS, Cisco Codec, CTMS, Cisco MCU, Cisco MSE, and Cisco TelePresence Server.

Field

Description

Physical Address

Physical address of the device.

Name

Name of the device.

Type

Type of the device.

MTU

Maximum transmission unit. Maximum packet size, in bytes, that this interface can handle.

Speed

Speed of the device in Mbps.

CDP

Whether the CDP is enabled (True) or disabled (False.)

Operational Status

Operational state of the device.

Admin

Administrative status of the interface.

Global Search Options for Prime Collaboration Assurance

Table 4 Global Search Options for Prime Collaboration Assurance

Search

Variable

Sample String Format

Exceptions and Allowed Search Strings

Phone

DN

10002|1000*| 100*| 1*| *0002

Alphanumeric characters, dash, period, and underscore.

IP

10.64.101.162 | 10.64.101.* | *

Alphanumeric characters, dash, period, and underscore. The special character % does not retrieve results.

MAC

00260bd75cf8| 00260bd75cf*| 00260bd*| 0*| 00*

Dash, period, underscore, are not allowed. Alphanumeric and blank space are allowed.

Phone Description

San Jose

-

Device

IP

10.78.22.129|

10.78.22.*| 10.*

Alphanumeric characters, dash, period, underscore, and space.

DNS

cussmtest-15.cisco.com

If the domain name is not resolvable, the IP address is displayed in the search results.

Location

Name

US-Texas| US*|*

Alphanumeric characters, dash, period, underscore and blank space are not allowed.

TelePresence

IP

10.78.22.77| . | 10.78.22.*| 10.78.*.*|

10.*.*.*| *.

Ampersand (&) and blank space are not allowed.

User

First Name

or

Last Name

HS

John

Alphanumeric characters, dash, underscore and blank space are not allowed.

Search Results

Search Parameter

Search Result

TelePresence

Host Name, Device Type, Model, Software Type, Software Version, and State. You can click on the icon next to the device name to launch the Endpoint 360 View for that TelePresence endpoint.

Phone

IP Address, IPv6 Address, MAC Address, Load ID, Description, and Model. You can click on the icon next to the device name to launch the Endpoint 360 View for that phone.

Device

Name, IP Address, Status, and Device Type. When you perform a device search, all phones and TelePresence endpoints are also included in this search. You can click on the icon next to the device name to launch the Endpoint or Device 360 View for that device.

Note    The information displayed depends on the device you have searched for.

Location

Cluster ID, Call Failure Troubleshooting, and Call Quality Troubleshooting. You can click Call Failure Troubleshooting to launch the Call Failure Troubleshooting page. You can click Call Quality Troubleshooting to launch the Call Quality Troubleshooting page.

User

First Name, and Last Name. You can click on the icon next to the device name to launch the User 360 View for that user.


Note


  • The devices in deleted state do not appear in the search results.
  • Phone search shows audio phones only. TelePresence endpoints are not displayed as part of phone search.
  • E20 devices are shown as TelePresence search results only.
  • When you search for phones using the MAC address in the global search option, do not use colon or hyphen or dots in between.
  • The global search option is not available in Prime Collaboration Assurance - Standard.

Search Use Cases

You can search for the following by:
Table 5 Search Use Cases

To search for...

Perform/Use

All devices belonging to a particular customer.

Select the customer from the global customer selection drop-down list at the top right of your screen, select the Device search icon, and then enter the search string *.

Cisco Jabber

Phone Search

E20

TelePresence Search

Infrastructure devices

Device Search

IP address of a device with a partial IP address.

Device Search - For example search with a string such as 10.*

List of all users associated with a particular customer.

Select the customer from the global customer selection drop-down list at the top right of your screen, select the User search icon and then enter the search string *.

Event Settings

The Event Settings pane contains the following details for endpoints and infrastructure devices.

Field

Description

Sessions

Name

Packet loss, jitter, and/or latency for which the threshold values are set.

Minor Threshold

Displays threshold values for minor alarms.

Major Threshold

Displays threshold values for major alarms.

Critical Threshold

Displays threshold values for critical alarms.

Enabled

Event enabled or disabled.

Automatic Troubleshooting

If enabled, displays event severity.

Endpoints

Category

Categories such as endpoint and service infrastructure.

Alarm Condition

Condition defined for the alarm to trigger.

Enabled

Event enabled or disabled.

Severity

Displays the severity: Critical, Major, or Minor.

The default threshold values are set for Rx packet loss, jitter, and/or latency for all endpoints. To view Default Event Settings and to customize values, see Customizing Alarms and Events.

You can further customize these settings for a single endpoint or a set of endpoints using Customize Events option in the current inventory table. See View Inventory Details.

Assurance Inventory Summary

The Inventory Summary lists the count of devices based on the device state. The Total column displays the total number of devices in a particular state. The device count is available as a cross-launch to the Inventory table in Device Work Center. When you click on any count, you will be directed to the Inventory table, where you can see all the devices in that particular state.

The Assurance Inventory Summary is available as a slider at the bottom of your UI browser. You can view the details when you scroll down. The Assurance Inventory Summary data is refreshed every 30 seconds.

Table 6 Assurance Inventory Summary - Field Descriptions

Field

Descriptions

Unused IP Phones

Total number of phones that are not registered with Cisco Unified CM for more than 24 hours, or yet to be registered by Cisco Unified CM.

Partially Managed

Devices which are in managed state but have some credentials missing. These credentials are not mandatory for managing inventory, but required for all other features, such as session monitoring or troubleshooting to work. You can click on the corresponding number to cross launch to see a list of all devices in the inventory table which are managed but with insufficient credentials. This count is updated only when you perform rediscovery after adding the credentials.

Mass Endpoints

This column excludes the phone count.


Note


Although the Total Count column contains the sum of the Infrastructure Devices, Mass Endpoints, and TelePresence Endpoints columns combined for each device state, you may see some inconsistency in the number of devices in the Total Count column. This difference can happen when the computation includes device types in Unknown state from the inventory.


Device-Specific Inventory Details

CTS, Cisco Codec, MX, E20, MXP, and Polycom

Table 7 CTS, Cisco Codec, MX, E20, MXP, and Polycom

Field

Description

TelePresence Endpoint

(Data displayed based on selected endpoint type CTS, Cisco Codec, MX, E20, MXP, or Polycom.)

Endpoint Name

Name assigned to the endpoint for ease of identification.

Directory Number

IP phone details as defined in the endpoint.

Call Controller

CUCM Address

Hostname or IP address of the Cisco Unified CM server where the endpoint is registered.

CUCM Cluster ID

Identification of the Cisco Unified CM cluster where the Cisco Unified CM server is registered.

VCS Address

Hostname or IP address of the VCS server where the endpoint is registered.

VCS Cluster ID

Identification of the VCS cluster where the VCS server is registered.

Registration Status

Registration status of the endpoint with call processor (Cisco Unified CM or VCS). If Cisco Unified CM or VCS is not managed, the information displayed is N/A.

H323 ID

H.323 ID configured on the Cisco Codec device.

E164 No

E164 number configured on the Cisco Codec device.

H323 Gatekeeper Address

Network address of the gatekeeper to which the Cisco Codec device is registered.

SIP URI

Registered SIP URI on the Cisco Codec device.

SIP Proxy Address

SIP proxy address that is configured manually on the Cisco Codec device.

Application Manager

CTSMAN

Hostname or IP address of the application manager where the CTS is integrated.

TMS

Hostname or IP address of the application manager where the Cisco Codec device is integrated.

Switch Details

Connected To Switch

Details of the switch to which the endpoint is connected.

Port Connected

Details of the switch port to which the endpoint is connected.

Peripherals

Name

Peripheral type, such as uplink, phone, camera, display, touch screen monitor, microphone.

Note   

CTS systems support TelePresence Touch Screen monitoring.

Position

Position of the peripheral, such as front_center for a microphone.

MAC Address

MAC address of the peripheral.

Software Version

Software version running on the peripheral.

Model

Model of the peripheral.

Serial

Serial number of the peripheral.

Make

Manufacturer’s details for the peripheral.

Firmware Version

Firmware version of the peripheral.

Hardware Version

Hardware version of the peripheral.

Midlet Version

Midlet version running on the peripheral.


Note


Prime Collaboration does not support peripheral details for Cisco TelePresence 150 MXP.


Table 8 Cisco Jabber for TelePresence Video (Movi)

Field

Description

Movi

Endpoint Name

Name assigned to the endpoint for ease of identification.

SIP URI

Registered SIP URI on the Cisco Jabber for TelePresence Video (Movi) endpoint.

VCS Address

Hostname or IP address of the VCS where the endpoint is registered.

VCS Cluster ID

Identification of the VCS cluster where the VCS is registered.

Table 9 Cisco Unified IP Phone 8900 and 9900 Series, and Cisco Cius

Field

Description

CUCM Endpoint

Endpoint Name

Name assigned to the endpoint for ease of identification.

Model

Model of the endpoint, such as CP-8945 or CP-9971.

Directory Number

IP phone details as defined in the endpoint.

Serial Number

Serial number of the endpoint.

Description

Description of the endpoint as defined in the call processor.

Call Controller

CUCM Address

Hostname or IP address of the Cisco Unified CM server where the endpoint is registered.

CUCM Cluster ID

Identification of the Cisco Unified CM cluster where the Cisco Unified CM server is registered.

Registration Status

Registration status of the endpoint with call processor (Cisco Unified CM). If Cisco Unified CM is not managed, the information displayed is N/A.

Switch Details

Connected To Switch

Details of the switch to which the endpoint is connected.

Port Connected

Details of the switch port to which the endpoint is connected.

Network Configuration

(Data displayed only for Cisco Cius endpoint.)

Wi-Fi Details

Status

Displays the status of the wi-fi connection, such as connected or not connected.

IP Address

IP address used to manage the endpoint when connected using a wi-fi network.

Default Router

IP address of the default router to which the endpoint is connected.

Access Point Name

Name of the access point to which the endpoint is connected.

Ethernet Details

Status

Displays the status of the Ethernet connection, such as connected or not connected.

IP Address

IP address used to manage the endpoint when connected using Ethernet.

Default Router

IP address of the default router to which the endpoint is connected.


Note


For discovery of Cisco Cius and Cisco Unified IP Phone 8900 and 9900 series, you must enable the HTTP interface. If the HTTP interface is not enabled, these devices will not appear in the inventory table.


For Cisco Cius devices, the standard phone description available in the inventory is SEP and MAC address.

CTMS

Table 10 CTMS

Field

Description

Multipoint Switch

Timezone

Time zone configured on the multipoint switch.

SKU

Hardware Model

Model number of the media convergence server on which the multipoint switch is running.

Software Version

Version of multipoint switch administration software currently installed.

OS Version

Operating System version.

Hostname

Hostname configured for the multipoint switch.

IP Address

IP address used to manage the multipoint switch.

Subnet Mask

Subnet mask used on the IP address.

MAC Address

MAC address of the media convergence server on which the multipoint switch software is running. This MAC address belongs to Ethernet interface 0 (the eth0 network interface card [NIC]). With failover, this MAC address persists, although another Ethernet interface becomes active.

Switch Details

Connected To Switch

Details of the switch to which the multipoint switch is connected.

Port Connected

Details of the switch port to which the multipoint switch is connected.

Ad hoc Segments

Maximum number of segments that are available for impromptu meetings. The maximum number is 48.

Maximum Segments

Total number of segments (individual video displays) that this multipoint switch can handle. The maximum number is 48.

Schedulable

Number of segments available at any one time for scheduled meetings. The multipoint switch automatically derives this value by subtracting the defined number of ad hoc Segments from the defined number of maximum segments.

CTS-Manager and Cisco TMS

Table 11 CTS-Manager and Cisco TMS

Field

Description

Application Manager

SKU

Hardware Model

Model number of the server on which the application manager is running.

Software Version

Version of administration software currently installed.

OS Version

Operating System version.

Hostname

Hostname configured for the application manager.

IP Address

IP address used to manage the application manager.

Subnet Mask

Subnet mask used on the IP address.

MAC Address

MAC address number supplied for the application manager.

System Connectivity (see note following this table)

Exchange Server: Data displayed only if Calendaring service (Scheduling API mode) is configured in the CTS-Manager.

Status

Whether the exchange server is running or down.

IP Address

IP address assigned to the exchange server.

Software Version

Version of software currently installed on the exchange server.

LDAP Server: Date displayed only if Active Directory is configured in CTS-Manager.

Status

Whether the LDAP server is running or down.

IP Address

IP address assigned to the LDAP server.

Software Version

Version of software currently installed on the LDAP server.


Note


For CTS-Manager, the System Connectivity pane is visible only for versions 1.7 and 1.8. Also, the CTS-Manager user configured in the Prime Collaboration application must have administrative privileges in CTS-Manager.


Cisco Unified CM

Table 12 Cisco Unified CM

Field

Description

Call Processor

Cluster ID

Parameter that provides a unique identifier for the cluster. This parameter is used in Call Detail Records (CDRs), so collections of CDR records from multiple clusters can be traced to their sources. The default is StandAloneCluster.

Publisher Hostname

Hostname configured for the cluster publisher.

Registered CTS Endpoints

Number of registered endpoints on the call processor.

Total CTS Endpoints

Total number of endpoints.

Table 13 Cisco MCU and MSE

Field

Description

MCU or MSE Details

(Data displayed based on selected conferencing device: MCU or MSE.)

Hardware Model

Model number of the media convergence server on which the multipoint switch is running.

Serial Number

Serial Number of the Multipoint Control Unit (MCU).

Software Version

Version of multipoint switch administration software currently installed.

MCU Type/Device Type

Type of the MCU or device.

Build Version

Build version of the installed software.

Manufacturer

Manufacturer’s name.

Hostname

Hostname configured in the device (MCU or Media Service Engine).

IP Address

Local IP address of the MCU or Media Service Engine (MSE) network interface used to access the MCU or MSE web user interface.

Subnet Mask

Subnet mask used on the IP address.

MAC Address

Fixed hardware MAC address of the Ethernet port.

Connected To Router

IP address of the router to which the MCU or MSE is connected.

Cluster Type

Whether the cluster is a master or slave. If the cluster is configured, Not Configured is displayed.

Total Video Ports

Number of video ports configured in MCU. (Data displayed only for MCU devices.)

Total Audio Ports

Number of audio ports configured in MCU. (Data displayed only for MCU devices.)

SIP (Data displayed only for MCU devices.)

Status

Whether the SIP registration is enabled or disabled.

Proxy

Network address of the SIP proxy.

Domain

Network address of the SIP registrar to which the MCU has registered.

H.323 (Data displayed only for MCU devices.)

Status

Whether the H.323 gatekeeper registration is enabled or disabled.

Gatekeeper ID

Identifier used by the MCU to register with the H.323 gatekeeper.

Gatekeeper Address

Network address of the gatekeeper to which the MCU has registered.

MSE Blades

(Data displayed only for MSE.)

Type

Type of the blade.

Slot

Slot number. Slot 1 is MSE Supervisor; slots 2-10 are blades.

Software Version

Version of the software used.

Status

Status of the blade: OK or absent.

Port A IP Address

IP address of Port A.

Port B IP Address

IP address of Port B.

Table 14 Cisco VCS

Field

Description

Call Processor

Cluster ID

Cluster Name that is used to identify one cluster of VCSs from another.

Master

Name of the VCS peer that is configured as the cluster master.

Registered Endpoints

Number of endpoints registered to the VCS.

Peers

Number of VCS peers configured within the cluster.

VCS Configuration

Timezone

Time zone that is configured on the VCS.

Maximum Traversal Calls

Number of traversal call licenses available on the VCS.

Maximum Non-Traversal Calls

Number of non-traversal call licenses available on the VCS.

Maximum Registrations

Number of endpoints that can be registered with the VCS.

Expressway

Whether the VCS Expressway is configured.

Interworking

Whether the VCS is configured to allow H.323 systems to connect to SIP systems.

Encryption

Whether AES encryption is available in the software build.

Find Me

Whether FindMe is enabled or disabled.

Device Provisioning

Whether the provisioning server is enabled on the VCS.

Dual Network Interface

Whether the LAN 2 interface on the VCS Expressway is enabled.

Starter Pack

Whether the Starter Pack option key is installed.


Note


Prime Collaboration manages both the Cisco VCS application and appliance.


Table 15 Cisco TelePresence Conductor

Field

Description

TelePresence Conductor

Name

Hostname configured for the conductor.

IP Address

IP address of the conductor.

Software Version

Version of software currently installed.

Cluster Master

Name of the conductor peer that is configured as the cluster master.

Cluster Peers

Number of conductor peers configured within the cluster.

Total Registered MCUs

Number of MCUs registered to the conductor.

Software ID

Identification of the software on the conductor.

Hardware Serial Number

Serial number of the conductor hardware.

Registered MCUs

Name

Name of the MCU registered to the conductor.

IP Address

IP address of the MCU registered to the conductor.

Type

Type of the MCU registered to the conductor.

Pool

MCU pool to which the MCU belongs.

Blacklisted

Listed MCUs are not used by the conductor.

Blacklisted Reason

Reason why the MCUs are not used by the conductor.

Media Load: Allocated/In Use/ Max Available

Media load allocated and in use, and the maximum available load.

Signalled Load: Allocated/In Use/ Max Available

Signalled load allocated and in use, and the maximum available load.


Note


Only Cisco TelePresence Conductor-controlled MCU cascading is supported.


Updating and Collecting Inventory Details

Updating and collecting inventory details depend on the type of network deployed: voice, video or both. It also depends on the data you want to collect at a given point. The following table recommends when to update inventory based on your network.

Table 16 Recommendations for Updating Inventory

Description

Task

If you have both voice and video endpoints deployed in your network, and want to collect data on both.

Perform Update Inventory (choose Operate > Device Work Center > Update Inventory). For more information, see Updating Inventory.

If you have both voice and video endpoints deployed in your network, and you want to collect data on video endpoints only.

Perform Update Inventory (choose Operate > Device Work Center > Update Inventory). For more information, see Updating Inventory.

If you have both voice and video endpoints deployed in your network, and you want to collect data on voice endpoints only.

Perform IP Phone Inventory Collection and Cluster Data Discovery (choose Administration > System Setup > Assurance Setup). For more information, see Collecting Inventory Details.

If you have only a voice network

Perform IP Phone Inventory Collection and Cluster Data Discovery (choose Administration > System Setup > Assurance Setup). For more information, see Collecting Inventory Details.

If you have only a video network

Perform Update Inventory (choose Operate > Device Work Center > Update Inventory). For more information, see Updating Inventory.

Updating Inventory

The Update Inventory task helps you to synchronize the Prime Collaboration inventory database with the network. During this task, accessibility verification is not performed (see the Update Inventory Lifecycle chart).

Perform the Update Inventory task when:

  • You want to synchronize the database for all devices managed in your network. You cannot update the inventory for only a few selected devices.
  • You want to define a periodic Update Inventory job to keep the Prime Collaboration database up-to-date.
  • There are any changes in the network devices’ interfaces.

    Note


    New devices added to the network will not be identified.


Figure 1. Update Inventory Lifecycle

We recommend that you define a periodic Update Inventory job to keep the Prime Collaboration database up-to-date.

To update inventory:


    Step 1   Choose Operate > Device Work Center.
    Step 2   In the Device Work Center page, click Update Inventory.
    Step 3   If you want to update inventory based on device status, check the Update devices based on device criteria check box in the Update Inventory window.

    If you choose to update the inventory based on device status, an accessibility information check is performed. If you do not, the inventory is updated with all devices in the Managed state. Device accessibility is not checked.

    To schedule a periodic update inventory job, go to add Step 4. To run the job immediately, go to Step 5.

    Step 4   Enter the job name and the scheduling details. See Job Schedule - Field Descriptions for field descriptions.
    Step 5   Click Run Now to immediately run the update inventory job, or click Schedule to schedule the periodic update inventory job at a later time.
    Step 6   Check the status of your job by doing one of the following:
    • If you clicked Run Now, click the progress details in the progress window that appears.
    • Click the Discovery Jobs button on the Device Work Center page.

    Job Schedule - Field Descriptions

    Table 17 Job Schedule - Field Descriptions

    Field

    Description

    Start Time

    Select Start Time to enter the start date and time in the yyyy/MM/dd and hh:mm AM/PM format, respectively. Alternatively, click the date picker to select the start date and time from the calendar. The displayed time is the client browser time. The scheduled periodic job runs at this specified time.

    Recurrence

    Select None, Hourly, Daily, Weekly, or Monthly to specify the job period.

    Settings

    Details of the job period.

    End Time

    If you do not want to specify an end date/time, click No End Date/Time. Click End at to enter the end date and time in the yyyy/MM/dd and hh:mm AM/PM format respectively.

    Inventory Details Collection

    Prime Collaboration supports on-demand inventory update for managed devices by collecting and updating data about the devices and the phones registered to them.

    All additions, deletions, and modifications of phones, XML phones, and clusters are reflected in the inventory. There are separate inventory collection schedules for phones and clusters. For details on cluster discovery, see Cluster Data Discovery Settings.

    You cannot create additional schedules; you can only edit an existing schedule. For phones, you can create multiple inventory collection schedules.


    Note


    You can schedule periodic discovery of Cisco Unified CM clusters only. Phones registered with other clusters are not discovered. For more information, see Cluster Data Discovery Settings.


    As Prime Collaboration performs inventory collection of phones and Cisco Unified CM clusters, these phones and clusters pass through various device states until they are fully recognized by Prime Collaboration (see Device States for details).

    You can specify how often to collect information about the phones and clusters that are managed in Inventory Collection. To schedule Inventory Collection, choose Administration > System Setup > Assurance Setup. For an overview of inventory collection tasks, see the following table.

    Table 18 Overview of Inventory Collection Tasks

    Task

    Description

    Schedule inventory collection of IP Phones

    Choose Administration > System Setup > Assurance Setup  > IP Phone Inventory Collection Settings to add, edit, or delete the IP phone discovery schedules. (For more information, see IP Phone Discovery Schedule.)

    Schedule inventory collection of Phone XML

    Choose Administration > System Setup > Assurance Setup  > IP Phone XML Inventory Collection Settings to schedule phone XML discovery. (For more information, see Scheduling IP Phone XML Discovery Schedule.)

    Schedule inventory collection of cluster devices

    Choose Administration > System Setup > Assurance Setup  > Cluster Data Discovery Settings to add, edit, or delete the cluster device discovery schedules. (For more information, see Cluster Data Discovery Settings.)

    IP Phone Discovery Schedule

    When you choose Administration > System Setup > Assurance Setup  > IP Phone Inventory Collection Settings, you can perform the following tasks:

    Viewing and Adding an IP Phone Collection Status

    To view IP phone collection status, choose Administration > System Setup > Assurance Setup  > IP Phone Inventory Collection Settings.

    The IP Phone Collection Status pane displays the information mentioned in the following table.

    Table 19 IP Phone Collection Status - Field Descriptions

    Fields

    Description

    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

    Prime Collaboration provides six default schedules for phone discovery. You can update or delete them; you can also add up to 10 phone discovery schedules.

    To add an IP phone schedule:


      Step 1   Choose Administration > System Setup > Assurance Setup   > IP Phone Inventory Collection Settings.
      Step 2   On the IP Phone Discovery Schedule page, click Add.
      Step 3   Enter the required information in the Add Schedule dialog box.
      Step 4   Click OK.

      Editing an IP Phone Discovery Schedule

      To edit an IP phone discovery schedule:


        Step 1   Choose Administration > System Setup > Assurance Setup   > IP Phone Inventory Collection Settings.
        Step 2   On the IP Phone Discovery page, select a phone discovery schedule and click Edit.
        Step 3   In the Edit Discovery Schedule dialog box, make the desired changes and click OK.
        Step 4   Click Apply.

        Deleting an IP Phone Discovery Schedule

        To delete an IP phone discovery schedule:


          Step 1   Choose Administration > System Setup > Assurance Setup   > IP Phone Inventory Collection Settings.
          Step 2   In the IP Phone Discovery Schedule page, click Delete.
          Step 3   In the confirmation message box, click Yes.

          Scheduling IP Phone XML Discovery Schedule

          To schedule when phone discovery should take place, you can use the Phone XML Collection page. The default scheduled start for Phone XML discovery is daily at 3:00 p.m. Phone XML discovery collects serial number, load ID, and App ID for each phone.

          To schedule an IP Phone XML discovery:


            Step 1   Choose Administration > System Setup > Assurance Setup   > IP Phone XML Inventory Collection Settings.
            Step 2   In the Phone XML Collection page, make the desired changes.
            Step 3   Click Apply, then click OK in the confirmation message box.

            Phone Lines Report

            The Phone Lines Report (available from Operate > Device Work Center > Phone Lines) displays a consolidated list of voice and video endpoints in your network. This report is updated based on IP phone discovery. For more information, see IP Phone Discovery Schedule.

            The Column Filter option allows you to hide any of the default columns in the report and select other columns of data to display. Reports on video and voice phones or lines are available at Report > Interactive Reports . For more information on phone reports, see Voice Reports.

            Exporting Device Lists and Credentials

            You can export device lists, and device credentials to a file. You could use this file to modify the device list and credentials and import it later. This feature is only available to users with network administrator, super administrator, and system administrator roles.

            To export device list and credentials:


              Step 1   Choose Operate > Device Work Center > Export.
              Step 2   Select Device list and Credentials, and enter a name for the output file. (Only CSV and XML file format is supported.)
              Step 3   Click Export. This file contains encrypted credentials only.
              Step 4   In the dialog box that appears, do one of the following:
              • Click Open to review the information.
              • Click Save to save the CSV or XML file on your local system.

              Suspending and Resuming Managed Devices

              You can suspend a device that is in the Managed state. After the device is moved to the Suspended state, Prime Collaboration does not monitor this device. That is, session, endpoint, and inventory details are not updated and alarms are not triggered for this device.

              The following are behaviors for a device in the Suspended state:

              • If a device is in the Suspended state, Prime Collaboration does not poll the devices.
              • If a suspended endpoint joins a new session, the endpoint is shown as Unknown in the Session Topology pane.
              • If a suspended endpoint is already in an in-progress session, the endpoint icon (in the Session Topology pane) changes to Unknown immediately after the endpoint state is changed to Suspended.
              • If CTS-Manager is suspended, new session data is not imported and the CTS-Manager polling is not performed. The existing session data (last polled data) is displayed in the Prime Collaboration server.
              • If Cisco Unified CM publisher is suspended, Prime Collaboration does not poll the registered endpoints that belong to that corresponding Cisco Unified CM cluster.
              • If there are any active alarms, they are not cleared immediately. You can either manually clear the alarms; otherwise, they are cleared automatically after they expire (by default, in 24 hours). No new alarms are triggered for a suspended device.
              • If a suspended endpoint is already in a troubleshooting job, you cannot troubleshoot from the suspended endpoint. However, you can troubleshoot up to the suspended endpoint.
              • If a device is suspended, the Endpoint Utilization report does not contain any data for this device.

              To suspend or resume managed devices:


                Step 1   Choose Operate > Device Work Center.
                Step 2   From the Current Inventory table, select managed or suspended devices.
                Step 3   Click Suspend or Resume.
                Step 4   In the confirmation message box, click OK.

                Deleting Devices

                You can delete devices that are in the Unknown, Unreachable, Inaccessible, Undiscoverable, Suspended, and Unsupported states. You cannot delete devices in the Managed state.

                After a device is deleted, it is not listed in the Current Inventory table, but the details are available in the Prime Collaboration server. To rediscover a deleted device, see Rediscovering Devices. You can access the deleted device’s details as part of the past session data.

                To delete a device:


                  Step 1   Choose Operate > Device Work Center.
                  Step 2   From the Current Inventory table, select devices to delete.

                  You can use the quick filter to get a list of devices in the desired state.

                  Step 3   Click Delete.
                  Step 4   In the confirmation message box, click OK.
                  Note   

                  You cannot delete phones directly from the inventory using the delete option. Phones are deleted automatically when the clusters with which they are registered are deleted. The inventory is updated only after a rediscovery is performed.


                  Configuring Prime Collaboration Deployment

                  Cisco Prime Collaboration Deployment is an application designed to assist in the management of Unified Communication applications. It allows you to perform tasks such as migration, of old clusters to new virtual machines, fresh installs, and upgrades on existing clusters.

                  For more information, see the Cisco Prime Collaboration Deployment Administration Guide.

                  To configure the Prime Collaboration Deployment Manager,


                    Step 1   Choose Administration -> System Setup -> Assurance Setup -> Cisco Prime 360 Integration.
                    Step 2   Enter the IP Address that you want to configure and click Save.
                    Step 3   Choose Administration -> Deployment Manager to launch the Deployment Manager page.

                    Performance Graphs

                    Prime Collaboration enables you to select and examine changes in network performance metrics. You can select, display, and chart network performance data using real time, as well as collected data.

                    You can access the performance graphs through the Topology View, Detailed Device View, Alarm & Events page, and Node-to-Node Tests page, Device 360 degree view, and Diagnostic Summary pages. You can create performance graphs from the current or real-time data when:
                    • Voice utilization polling is enabled for devices.
                    • Data is available on disk from node-to-node tests that you have configured.
                    • Device is in managed state.

                    Note


                    You can view performance graphs for voice devices (excluding phones) only. These graphs appear only for devices in managed state and for which at least one polling cycle is over.


                    Performance Graphing Notes

                    This section contains information you should be aware of when working with performance graphs.

                    Summary

                    Explanation

                    Cisco recommends following these guidelines for optimal performance graph viewing.

                    The following guidelines are recommended:
                    • No more than five metrics be selected for one graph.
                    • No more than ten graphs on the user interface.
                    • No more than ten items selected for merge.
                    • No more than ten items for Node-to-Node graphing.

                    An MGCP gateway on a Catalyst 6000 switch. When you have all three capabilities (voice gateway, switch, and MGCP) performance graphing cannot graph all the data. Only the common metrics are available for graphing.

                    When graphing performance metrics for a device that has these three capabilities (voice gateway, switch, and MGCP) you will only be able to graph the common metrics. In the Event Details page you cannot graph HighUtilization events.

                    A voice gateway, MGCP, and H323 on a router. When you have all these capabilities on one device, each metric displays two graphs.

                    When graphing performance metrics for a device that has these capabilities (voice gateway, MGCP, H323, and router), each metric displays two graphs. Also, when graphing multiple devices or devices that have multiple polling intervals, the least common multiple is used to plot the x axis. Real-time graphs will refresh at this common polling interval.

                    In the Select Metrics dialog box for Unified CCE, you will see the following fields:
                    • Agents logged on
                    • Calls in progress
                    • Inbound Calls per second

                    To view a performance graph for any of these metrics, you must enter the name of the Unified CCE instance for which you want the information, in the field next to Instance Name.

                    Each Unified CCE contains a list of enterprise contact center applications, which are identified by their instance name.

                    Prime Collaboration does not display a performance graph for all Unified Contact Center Enterprise (CCE) machines

                    Prime Collaboration only collects data for Unified CCEs that have router capabilities. To verify your Unified CCE’s capabilities, you can run a device report through device management, and look for Unified CCE or IPCC Router in the Device Capabilities column of the Device report.

                    You cannot view a performance graph for Unified CCEs that do not have router capabilities. Instead, you will get a message window stating such.

                    Cisco Unity Express servers (CUES) graph real-time data and update in real-time. You can switch from line to bar charts and zoom in on specific data to troubleshoot and find peak utilization periods.

                    Ensure Prime Collaboration is collecting data and is configured properly to receive this data.

                    Launching a Performance Graph

                    The performance graphs are available through the following:
                    • Topology View
                    • Device 360 degree View - Click on the Launch Tools icon, and then click on Performance Graph.
                    • Event Details page
                    • Detailed Device View
                    • Node-to-Node Tests page
                    • Diagnostics views—UCM Cluster Call Usage Summary in Server and Cluster views, UCM Resource Utilization Summary and UCM Cluster Location Summary in Cluster view, and trunk utilization can be accessed through the UCM Resource Utilization Summary portlet. in the Cluster view.
                    Before you Begin
                    • Verify that Prime Collaboration is monitoring the devices for which you want to collect utilization statistics. This includes the Cisco Unified Communications Manager that the ports are registered to.
                    • Verify that voice utilization polling settings are enabled. Prime Collaboration uses the statistics gathered during voice utilization polling for charting network performance.
                    • Review the Performance Graphing Notes.

                    Performance Graph Window

                    Performance graphs provide real-time information and historical information.

                    When you launch a performance graph, one line graph is displayed for each metric that you select. Each line graph contains 16 data points displayed in real time. The following table provides details on the data options.

                    Graph Data Option

                    Description

                    Real Time

                    When you launch a performance graph, it shows real time data by default.

                    Hourly Average

                    When you select Hourly Average, the performance graph shows average data for the hour.

                    Hourly Max

                    When you select Hourly Max, the performance graph shows peak data for the hour.

                    Hourly Min

                    When you select Hourly Min, the performance graph shows minimum data for the hour.

                    History

                    When you select History, the performance graph shows hourly average data for seven days.

                    All

                    Displays all data. Graphs display up to a maximum of 130 points. If data ranges in the Zoom/Pan view contain more than 130 points, then Prime Collaboration selects points at regular intervals and plots them in the graph.

                    Troubleshooting Performance Graphs

                    This section contains information that will help you if you encounter problems generating performance graphs. If you encounter an error, it will likely appear either when you select Performance Graphing from the menu, or when Prime Collaboration is checking for the data file to graph. In the first case (when selecting Performance Graphing), you will see an error message that describes the problem and an action to take. The following table describes the errors and their possible causes, for both of these types of cases.

                    Error

                    Possible Causes

                    Cannot collect data.

                    • Account and credentials are not the same on all Cisco Unified Communications Managers in the cluster.
                    • HTTP server problems:
                      • HTTP server on the device is down.
                      • HTTP server is operational, but the Cisco Unified Communications Manager is down.
                    • Device unreachable because of a network problem.
                    • Performance Monitor process on the media server is down.
                    • The Cisco Unified Communications Manager that the MGCP gateway is registered to is not in Prime Collaboration inventory.
                    • Device capability is not supported. Performance graphing supports the following: Cisco Unity, Cisco Unity Express, Cisco Unified Communications Manager, Cisco Unified Communications Manager Express, SRST, H.323 devices, and Voice Mail Gateways.
                    • Device is suspended or deleted.
                    • Device platform is not support.

                    For device support information, see Supported Devices for Cisco Prime Collaboration .

                    Cannot collect data because of the following:
                    • The username or password for the device is empty.
                    • The system has the wrong credentials for the device.
                    • The device does not have credential information.
                    • No credentials in Prime Collaboration.
                    • Incorrect credentials in Prime Collaboration.

                    To add credentials, see Managing Device Credentials.

                    Cannot collect data from the device because of the following:
                    • A processing error occurred.
                    • Parsing or processing errors occurred.
                    • Internal initialization errors occurred.
                    • Initialization problems occurred in the device data collector.
                    Incorrect Cisco Unified Communications Manager version. Check the following:
                    • The version of the Cisco Unified Communications Manager that is running on the device.
                    • The Cisco Unified Communications Manager version number that is stored in Prime Collaboration.
                    • If the Cisco Unified Communications Manager version number that is stored in Prime Collaboration is incorrect, re-add the device.

                    For device support information, see Supported Devices for Cisco Prime Collaboration .

                    Cannot collect data from the device. The certificate hostname/IP Address cannot be mapped to the URL hostname/IP Address.

                    The device is not in DNS.

                    Incomplete data collected because an error occurred in communicating with the device.

                    Incorrect Cisco Unified Communications Manager version. Check the following:
                    • The version of the Cisco Unified Communications Manager that is running on the device.
                    • The Cisco Unified Communications Manager version number that is stored in Prime Collaboration.
                    • If the Cisco Unified Communications Manager version number that is stored in Prime Collaboration is incorrect, re-add the device.

                    For device support information, see Supported Devices for Cisco Prime Collaboration .

                    Cannot collect data because of the following:
                    • The device returned no data from a required MIB.
                    • The device received no MIB data.
                    • No data from a required MIB.
                    • A required MIB is not populated on the device.
                    • No MIBs returned data.
                    • Device is unreachable due to a network problem.
                    • Device credentials do not contain a valid SNMP community read string.
                    • SNMP response slow; data collection timed out.
                    • The rate of queries on the Cisco Unified Communications Manager exceeds the limit.
                    • An error has occurred in the data processing stage.

                    Too many queries on a Cisco Unified CM 6.0 or later.

                    Check the polling settings; they should not be less than three minutes.

                    • The Cisco Unified Communications Manager did not have enough time to handle the query requests.
                    • An error has occurred in the data processing stage.

                    Query exceeded time limit on Cisco Unified CM 6.0 or later.

                    Cisco Unity or Unity Express trunk utilization graphs are not working.

                    Prime Collaboration must be configured properly using the maximum capacity.

                    When working with performance graphs, remember the following:
                    • If you are not able to collect performance data and you do not see an error message (either a popup message or a message in the log file) indicating the problem, you should verify the status of the device. To do so, use the View/Rediscover/Delete Devices page. If the device is in the Unreachable state, verify that the device's credentials are correct and rediscover the device.
                    • If a gray line or a gray area appears in a graph, hover your mouse over it to obtain a tool tip with an explanation.