Cisco Prime Unified Operations Manager 9.0 User Guide
Overview of Cisco Prime Unified Operations Manager
Downloads: This chapterpdf (PDF - 674.0KB) The complete bookPDF (PDF - 18.07MB) | Feedback

Overview of Cisco Prime Unified Operations Manager

Table Of Contents

Overview of Cisco Prime Unified Operations Manager

What Is Prime UOM?

What's New in This Release

Before Using Prime UOM

Launching Prime UOM

Logging Out

Using Prime UOM Multiple End-Customer Views

Creating Customer Folders (for Multiple End-Customer Views)

Configuring Users to View Customer Folders

NAT Support In Multiple End-Customer Views

Using Prime UOM for Day-to-Day Operations

Benefits of Prime UOM Unified Dashboard

About Monitored Events

Unified Dashboard

UC Opsview

Phone Health Summary

Top 5 Call Failure Locations

Top 5 WAN Traffic Locations

UC Services Health Summary

Top 5 Poor Call Quality Location

Top 5 Utilized Trunks/Route Groups

Fault Monitor Dashboard

Diagnostics Views Dashboard

Reports Dashboard

Event History Reports

Service Quality History Reports

Audio IP Phone Reports

Video IP Phones Report

Personalized Reports

What Administrative Tasks Do I Need to Perform?

Managing Devices

Configuring Notifications

Setting Polling and Thresholds

Setting System Settings

Managing External Cisco Unified Communications Management Links

Creating and Running Diagnostic Tests

How Does Prime UOM Work?

Users Perform Device Management and Configuration

Prime UOM Performs Ongoing Monitoring, Analysis, and Notification

Users Respond to Notifications and Events

Supported Special Characters List

Understanding the Basics

Starting Prime UOM

Adding the Prime UOM Home Page to the Internet Explorer Trusted Site Zone

Working with Prime UOM Windows

Using Displays and Reports

Filtering Display Data

Window Command Buttons

Paging and Sorting Displays and Reports

Viewing Data from Reports with Over 2,000 Records

Exporting Data from a Display or Report

Printing Displays or Reports

Selecting Objects and Groups

Using the Search Tool

Using the Search Tool to Locate a Device

Using the Search Tool to Locate a Phone

Using the Search Tool to Find a Location

Understanding Your User Role

Responding to Security Alerts

Responding to Messages About Device Limits


Overview of Cisco Prime Unified Operations Manager


These topics provide an overview of Cisco Prime Unified Operations Manager (Prime UOM):

What Is Prime UOM?, page 1-1

What's New in This Release, page 1-3

Before Using Prime UOM, page 1-3

Using Prime UOM Multiple End-Customer Views, page 1-6

Using Prime UOM for Day-to-Day Operations, page 1-8

How Does Prime UOM Work?, page 1-22

Understanding the Basics, page 1-27

What Is Prime UOM?

Cisco Prime Unified Operations Manager (Prime UOM) is a member of the Cisco Unified Communications family of products. It provides a comprehensive and efficient solution for network management and allows you to monitor Cisco Unified Communications deployments.

Prime UOM monitors and evaluates the current status of both the IP communications infrastructure and the underlying transport infrastructure in your network. Prime UOM uses open interfaces such as Simple Network Management Protocol (SNMP) and HTTP to remotely poll data from different devices in the IP communications deployment.


Note Prime UOM does not deploy any agent software on the devices being monitored and therefore is not disruptive to system operations.


Prime UOM increases productivity of network managers by enabling them to isolate problems quickly using:

Fault Monitor—Access to device views, event summaries, device and event details, as well as access to other management tools on devices, clusters, and phones. This component makes navigating fault management easier and allows you to quickly view relevant information. You can set the context views based on site or device group.

Service Level View—Displays a logical topology view of your IP telephony implementation. This logical view focuses on the cluster call control relationships.

Diagnostics—Access to key diagnostic tools and reports in one location. Distinct monitoring and diagnostic workflow allow you quickly identify network data for analysis.

Enterprise users can customize your view to include:

Summary views that include data on Cisco Unified Communications Manager Express (Cisco Unified CME) devices, Cisco Unified CM events, and cluster events across all devices in a cluster

Cluster views

Server views

Phone views

Voicemail views

Gateway views

Multiple customer end-users can view specific customer details and views.

Reports

Event History

Audio IP Phones

Personalized reports

Service Quality History

Video IP Phones

Clickable information in notification messages—Includes context-sensitive links to more detailed information about service outages.

Context-sensitive links to other Cisco tools—Help you to manage IP communications implementations.

Prime UOM also does the following:

Supports device pools—Collects this information for various reports and displays. Service Quality and phone registration related events can contain data at the device pool level.

Event enhancements—Event severity and description customizations are available across all displays and reports. You can also control events using suppression at the component level.

Presents service-quality events—Uses information from Cisco Unified Service Monitor, when it is also deployed, to:

Display Mean Opinion Scores (MOSs) associated with poor voice quality between pairs of endpoints involved in a call. These endpoints can be Cisco Unified IP Phones, Cisco Unity messaging systems, or voice gateways. It also displays other associated details about the voice-quality problem.

Enable you to perform a probable path trace between the two endpoints and report on any outages or problems on intermediate nodes in the path.

Highlights current connectivity-related and registration-related outages affecting Cisco Unified IP Phones in the network—In addition, it provides contextual information that enables you to locate and identify the IP phones involved.

Tracks IP communications devices and IP phone inventory—Tracks Cisco Unified IP phone status changes and creates a variety of reports that document move, add, and change operations on Cisco Unified IP Phones in the network. All phone reports and personalized reports now show device pool and partition information for the IP Phones.

Provides real-time notifications—Uses SNMP traps, syslog notifications, and e-mail to report the status of the network being monitored to a higher-level entity (typically, to a manager of managers).

Provides easy to use, scalable reports—Displays large networks using visual cues in map views as well as tabular reports to access management details of clusters and devices.

Enables coresidence with other Cisco Unified Communications Management software—Allows you to add links to Prime UOM to launch other Unified Communications management applications using the UC Management Suite tab. You can run Service Monitor, Provisioning Manager, and Service Statistics Manager in standalone mode or as coresident.

What's New in This Release

Prime UOM 9.0 has the following new features:

Support for 60,000 phones. See Cisco Unified Operations Manager 9.0 Installation Guide.

Support for Windows R2. See Cisco Unified Operations Manager 9.0 Installation Guide.

Reports data on route groups utilization in the Top 5 Utilized Trunks/Route dashlet. See Top 5 Utilized Trunks/Route Groups, page 1-16.

Added new Presence Server Diagnostic View portlets. See Presence Server Diagnostic View Portlets, page 3-17.

Added new performance counters for presence server. See Server Usage, Instant Messaging, and Conferencing Usage for Cisco Unified Presence Server, page A-31.

New events related to Cisco Unified Presence Server, Cisco Unified Borderless Element, and Route Groups supported by Prime UOM. See Supported Events, page E-3.

Support for VG-350 voice gateways. See Cisco Prime Unified Operations Manager 9.0 Supported Devices and Interoperable Software Table for more details.

Support for UCC Express Performance Pollling. See Cisco Prime Unified Operations Manager 9.0 Supported Devices and Interoperable Software Table for more details.

Support for MediaSense and Finesse. See Cisco Prime Unified Operations Manager 9.0 Supported Devices and Interoperable Software Table for more details.

Support for 3rd party devices.

Before Using Prime UOM

The person or team that installed Prime UOM should have completed the initial configuration before you start working with Prime UOM. The instructions for configuring Prime UOM are included in Installation Guide for Cisco Prime Unified Operations Manager.

This section contains:

Launching Prime UOM, page 1-5

Logging Out, page 1-6


Note For enterprise users, when Prime UOM is installed, it automatically synchronizes with the DCR and adds inventory. This is the default setting. For multiple end-customer users, devices must be manually added or imported.


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

For more detailed information on device management, see Getting Started with Device Management, page 7-1.

After your devices have been synchronized with the DCR, Prime UOM is ready to monitor and analyze events, and provide notification of events in Unified Dashboard displays. Prime UOM uses the default polling parameters and threshold values, default inventory collection and purging schedules, and default views. You should determine whether the default values are adequate for your use.


Note The product we formerly referred to as Cisco Unified CallManager is now called Cisco Unified Communications Manager in versions after 4.3, 5.1, and 6.0. Versions earlier than 4.3 and 5.1 retain the Cisco Unified CallManager name. Throughout this document and in online help, any reference to Cisco Unified Communications Manager can also refer to Cisco Unified CallManager, unless explicitly noted.


Table 1-1 lists tasks that you may attend to, at your discretion, after the initial configuration. This table lists optional configuration tasks and some day-to-day tasks that you may want to address when you first start to use Prime UOM.

Table 1-1 Tasks to Consider when Initially Setting Up Prime UOM 

Initial Setup Tasks
Explanation
Reference

Subscribe users to receive e-mail notification of events and subscribe hosts to receive Prime UOM-generated SNMP traps.

Prime UOM displays the operational health of the IP telephony environment and IP fabric on the Events History display.

You can also subscribe users and hosts to receive e-mail or Prime UOM-generated SNMP traps, respectively, in response to events.

Using Notifications, page 14-1

Update polling parameters and threshold values.

Prime UOM provides default values. However, you can update the values based on your experience of the IP telephony environment and IP fabric.

You should apply the changes during a time of low activity on the network.

Configuring Polling and Thresholds, page 19-1

Enable the voice utilization polling settings.

By default, the voice utilization polling settings are not enabled. Prime UOM uses the statistics gathered during voice utilization polling for charting network performance.

For information on performance graphing, see Using Performance Graphs, page 6-1.

For information on setting polling parameters, see Managing Polling Parameters, page 19-14.

Set up synthetic tests to monitor IP telephony application health.

You can configure various tests to run at intervals against IP telephony elements, such as Cisco Unified Communications Managers.

Using Synthetic Tests, page 11-1

Set up Node-To-Node tests.

Node-To-Node tests monitor the response time and availability of multiprotocol networks on both an end-to-end and a hop-by-hop basis.

Using Node-To-Node Tests, page 13-1

Set up phone status tests to check the availability of key phones.

You can configure Prime UOM to test the availability of key phones in your network.

Using Phone Status Testing, page 10-1

Set up batch tests.

You can test the health and connectivity of a branch office. Batch tests consist of a set of synthetic tests that are run on voice applications and a set of phone tests that are run on real phones in the branch office.

Using Batch Tests, page 12-1

Set up Survivable Remote Site Telephony (SRST) tests.

After you import devices to Prime UOM, import a list identifying the source routers and target SRST routers in Prime UOM inventory.

This enables Prime UOM to perform regular tests and to notify you when a branch office failure requires SRST.

Understanding How Prime UOM Monitors SRST, page 9-1

Update the device inventory collection schedules.

Prime UOM provides a single default schedule for device inventory collection. You can use this schedule or suspend it.

Working with the Device Inventory Collection Schedule, page 7-60

Update phone discovery schedules.

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

Working with IP Phone Discovery, page 7-60

Update the Purging Scheduler.

By default, Prime UOM purges the database daily, at midnight. You can edit the schedule.

Setting System-Wide Parameters Using System Preferences, page 20-17

Configure Prime UOM to forward traps to a Network Management System (NMS).

Prime UOM can forward traps to other NMSs, such as HP OpenView and NetView.

Integrating SNMP Trap Receiving with Other Trap Daemons or NMSs, page 20-8

Set up cross-launch capabilities to other Cisco Unified Management products

Prime UOM allows you to create links to other Cisco Unified Management products such as Service Monitor and Service Statistics Manager so that you can run diagnostic reports and access other monitoring functions.

Setting Up Cisco Unified Communications Management Application Links, page 21-1

Set up trunk utilization

You can configure Prime UOM to monitor trunk utilization data.

Configuring Cluster Trunk Utilization, page 20-16


Launching Prime UOM

Prime UOM uses port 1741 or 80 for the HTTP server and port 443 for HTTPS server (SSL).

Prime UOM enterprise deployments support up to five simultaneous clients. Prime UOM multiple end-customer deployments support up to seven simultaneous clients.

To access the server from a client system:


Step 1 Enter any one of these URLs in your web browser:

If SSL is disabled, and if you have installed Prime UOM application on the default port, enter:

http://server_name:1741 or http://server_name:80

If SSL is enabled, and if you have installed Prime UOM application on the default port, enter:

https://server_name:443

where server_name is the hostname of the server on which you have installed the product.

If IIS is detected on your system, the port number 443 cannot be used because it causes port conflict. Instead, you can use a port number ranging from 1024 to 65535.

Step 2 Enter the user login and password.

Prime UOM opens with the Fault Monitor page displayed.

If Prime UOM is installed on an server with other LAN Management Solution (LMS) products, you may see a drop-down with the names of other non-LMS communities displayed in the top right corner of the home page.

The communities are listed based on the installed applications in the current server.

You can select any communities from the drop-down list.


Logging Out

To exit, click the Logout link displayed at the top right corner of user interface.

The log-in page appears.

Using Prime UOM Multiple End-Customer Views


Note This section applies to the multiple end-customer version of Prime UOM, which was selected when Prime UOM was installed.


When you installed Prime UOM, you selected either the single enterprise version of Prime UOM or the multiple end-customer version of Prime UOM. Each version provides a different customer view option.

The single enterprise version provides a single customer view, where Prime UOM can only see the devices for one particular customer. This option is usually used in a standard single enterprise environments.

The multiple end-customer version provides operators with multiple customer views. This option is used in managed service provider environments. This view allows a single operator to view the devices of multiple customers that are being managed by the operator.

To start using multiple customer views, you must do the following:

Creating Customer Folders (for Multiple End-Customer Views), page 1-7

Configuring Users to View Customer Folders, page 1-7

Creating Customer Folders (for Multiple End-Customer Views)

In the device selector, you will see an additional folder (that the single enterprise version does not have) called Customers. This folder contains all your customer views. Each customer has its own folder, which contains the devices for that customer.

You do not manually add these customer folders. The folders that are listed in the Customer folder are automatically added when you add devices for the customer.

So to see a customer's folder you must first add the customer's devices into Prime UOM.

There are two ways in which you can add devices to the multiple end-customer version of Prime UOM.

Manually add each device, see Adding Specific Devices from the DCR, page 7-7.

Import multiple devices, see Importing Devices into the DCR, page 7-14.


Note Automatic discovery of the devices cannot be used to add devices for the multiple end-customer version of Prime UOM.


After a device is added, the Customer folder appears in the group selectors throughout Prime UOM. The Customer folder now also contains the specific customer folder. The name of the customer's folder is the name for the customer that was specified when the device was added to Prime UOM.

All the devices for the at customer will appear in the customer's folder. This is the customer view for the specific customer.


Note If you did not specify a customer name for a device when it was added, the device will be listed in the Default subfolder, under the Customer folder.


Configuring Users to View Customer Folders

To enable a user to view customer folders you must configure the user accordingly. Specifically you must make sure that the Device Authorization field is enabled for the user.

For more information about user setup, see Configuring Users In Local RBAC Mode, page 20-28.

You may also want to set up custom user roles so that certain user types can only see specific groups of customers (as well as specific types of devices).

For more information about user role setup, see Configuring User Roles in Local RBAC Mode, page 20-28.

NAT Support In Multiple End-Customer Views

If your deployment supports NAT, there are certain configurations that you must set in Prime UOM. For details on NAT support, see NAT Support in Prime UOM, page 7-74.

Using Prime UOM for Day-to-Day Operations

These topics briefly describe Prime UOM functions that you may use frequently. On a day-to-day basis, operations personnel are likely to use the Unified Dashboard displays to monitor the IP telephony environment.

No more than five simultaneous Prime UOM enterprise users are recommended if all users view the portals, perform tests, and create reports on a constant basis. For multiple end-customer users, no more than seven simultaneous clients are recommended.

These displays can include Fault Monitor or any of the Diagnostics views.

This section contains:

Benefits of Prime UOM Unified Dashboard, page 1-8

About Monitored Events, page 1-9

You can customize the Unified Dashboard to include additional displays. For details on adding or removing portlets, see Customizing Your Dashboard, page 3-2.

Network administrators and operators might similarly use the Unified Dashboard displays to assess network health and the phone reports to solve IP and video phone problems.

In addition, network administrators and operators will use:

Fault Monitor—To manage the real-time information about the operational status of your network devices.

Device Management—To keep the inventory of devices that Prime UOM monitors current.

Notification Services—To ensure that the right users and systems receive e-mail or SNMP traps in response to events on selected devices, device groups, and clusters.

To make the most effective use of Prime UOM on a day-to-day basis, network administrators and operators also need to understand the impact of operations on configuration and administration tasks. An overview is provided in Scheduling Prime UOM Tasks, page 20-4.

The Prime UOM functions that support day-to-day operations are further described in the following topics:

Benefits of Prime UOM Unified Dashboard, page 1-8

About Monitored Events, page 1-9

Unified Dashboard, page 1-10

Diagnostics Views Dashboard, page 1-17

Reports Dashboard, page 1-17

What Administrative Tasks Do I Need to Perform?, page 1-19

Benefits of Prime UOM Unified Dashboard

The benefits of Prime UOM Dashboard are:

Easy access to information —You can view diagnostic portlets, access the Fault Monitor to view devices, phones, and clusters event data, run important reports, or complete server maintenance or administrative tasks.

Easy customization—You can modify and personalize your dashboard, adding portlets, changing portlet titles and configuring your dashboard layout to display what you want to see.

Lightweight GUI—Data is displayed in the Unified Dashboard and use of external pop-up windows are minimized.

For more information on the portal, see Understanding the Diagnostics View for Enterprise Users, page 3-1.

About Monitored Events

An event is the actual issue seen on a device, component, phone, or cluster in the network. Each event is assigned a unique identification number. When the event changes its state, it is assigned a new event ID.

Event History allows you to identify all previous events for a given device. To search Event History, Use the Search by Device option instead of the Search by Event ID option. This is because the same device can have more than one event ID from the past.

When a device is deleted from Prime UOM, all corresponding events are also deleted. For more information on events, see Events Processed, page E-1.

This section contains:

Event Types

Event States

Event Severities

Event Types

There are two types of events:

Device events—Seen on events displays. Device events include:

Device events

Cluster events

Phone events

Service Quality events—Seen in the Fault Monitor and other Diagnostic view portlets.

Event States

Event states include:

Active—Whenever any issues occur in the network, a corresponding event is generated in Prime UOM.

Cleared—There are two types of cleared events:

When the issue gets resolved in the network, a Cleared event is generated. The corresponding active event is removed and replaced by a cleared event.

If the corresponding cleared event cannot be generated, Prime UOM generates an auto- cleared event. The event details page provides this information if the event was auto-cleared.

The time interval for auto-cleared event generation varies for different types of events. For information on event details, see Supported Events, page E-3. For information on trap-based events, see Multiple Processed SNMP Traps and the Event Details Displayed for Them, page C-1.

Even if an auto-cleared event is generated, the issue may not be resolved in the network. The time intervals for generating cleared events are based on the minimum time required by the administrator to look into the issue and fix it.

To avoid missing any important events that may have occurred over a weekend, we recommend that you check the Event History for 30 to 60 minutes.

To identify automatically cleared events, look for the following in the event details:

Cleared by: Cisco Unified Operations Manager has automatically cleared this event. 
 
   

Cleared events do not appear in the Fault Monitor Fault Summary tab.

UserCleared—When an event is manually cleared from the dashboard, it moves into the UserCleared state. If you are aware of the issue and not interested in seeing it on the dashboard, you can manually clear the event.

When the corresponding cleared event is generated, it eventually moves from UserCleared state to Cleared state. This event change appears in the user interface and can also be seen as part of event history. UserCleared events are stored in the database to remind you that you are not interested in that instance of the event.

It continues to remain in the database until a cleared event is generated for it. UserCleared event states do not mean that the issue is resolved in the network. The issue may continue to exists in the network. Such events will be shown on the Event History Display window for a duration of around 30 to 60 minutes. UserCleared events do not appear in the Fault Monitor Fault Summary tab.

Acknowledged—When an event is acknowledged from the user interface, it moves into the acknowledged state. If you are aware of the issue and are currently working on it, it can be acknowledged. When the issue is fixed in the network or if it is time for auto-clear, the event moves into the Cleared state.

Event Severities

The event can have one of the following severity levels:

Critical.

Warning.

Informational.

The highest event severity is shown as the event severity level in the Event Details View for the respective device.

Unified Dashboard

The Unified Dashboard provides access to the main tasks that you can perform. This includes monitoring, diagnostics, reporting and administrative functions. See the following sections for a details:

UC Opsview, page 1-11

Fault Monitor Dashboard, page 1-17

Diagnostics Views Dashboard, page 1-17

Reports Dashboard, page 1-17

What Administrative Tasks Do I Need to Perform?, page 1-19

UC Opsview

UC Opsview provides a single view summary of the entire UC phone network status. UC Opsview provides the following dashlets within the UC Opsview:

Phone Health Summary

Top 5 Call Failure Locations

Top 5 WAN Traffic Locations

UC Services Health Summary

Top 5 Poor Call Quality Location

Top 5 Utilized Trunks/Route Groups

Phone Health Summary

The Phone Health Summary dashlet provides a summary of the status of all the phones in the network. The dashboard displays the summary as a pie chart or table. You can view a summary for hard phones and soft phones. A phone report displays phone inventory details for the selected type.

The dashlet shows details about phones in the following modes:

Unregistered—Phones that are not registered with Cisco Unified CM, and are not in energy save or SRST mode.

Registered—Phones that are registered with Cisco Unified CM.

Energy save mode—Phones that are in energy save mode.

Unknown—Phones that are in Unknown or Rejected state.

SRST mode—Phones that were registered with Cisco Unified CM, then were unregistered, and are currently likely to be registered with the SRST router.

Troubleshooting

Troubleshooting is available only for phones in Unregistered and SRST modes.

Right-click the pie chart, and then click Troubleshoot to open the Phone Troubleshooting window.

The left pane displays the top five locations by phone count. The X axis shows the location name. If there is a common location across multiple clusters, such as Hub_None, then the cluster name is also specified along with the location name. The Y axis shows the number of phones.

For phones in Unregistered state, the X axis shows either the Cisco Unified CME IP address or the actual location of the Cisco Unified CM cluster.

For phones in SRST state, the X axis shows the SRST IP address.

Click the bar in the bar chart to open device topology view, which shows all of the impacted devices in the right pane of the dashboard.

Right-click the device icons to open cross-launch options that are available in the Service Level View. The device icon changes based on the event severity associated with the device. Click the icons to open the phone details for the selected device; they appear in the bottom pane.

When you place the cursor on the Extensions column, a popup opens, showing the phone details and launch points for:

UCM Diagnostic View (see Server View Portlets, page 3-38 for details)

Phone View (see Phone View Portlets, page 3-33 for details)

Phone Reachability Test (see Adding a Phone Status Test—Using the Create Phone Status Test Page, page 10-4 for details)

Phone Registration Test (see Creating a Phone Registration Test, page 11-7 for details)

Top 5 Call Failure Locations

The Top 5 Call Failure Locations dashlet shows the five locations that are experiencing the most call failures in the last hour. Prime UOM aggregates the available CDR data at fixed time intervals and displays it in this dashlet.

See Service Monitor documentation for details about the criteria used for classifying a call as a failed call.


Note It is possible for the Service Monitor CDR Diagnostic Report to have more recent data than what is available via the dashlet at any particular time.


If the dashlet does not contain any data, check whether:

The Service Monitor license is installed. The dashlet works only if this license is installed.

Service Monitor has been added in Prime UOM.

The clusters are configured with Service Monitor as their billing server. This ensures that the CDR records are pushed to Service Monitor.

The top five locations are chosen taking into account all the clusters that are added in Prime UOM. For example, if three clusters are added in Prime UOM, and each cluster has 30 locations, then the top five locations are chosen from among these 90 locations.

The X axis shows the location name. If there is a common location across multiple clusters, such as Hub_None, then the cluster name is also specified along with the location name.

The Y axis shows the number of failed calls.

The Z axis shows the percentage of failed calls, represented as bubbles.

If there are fewer than five locations that are experiencing call failures, only those locations are shown. If the percentage of failed calls in a location is less than 0.5, the location is ignored.

Troubleshooting

Click the bubble in the Z axis to open a popup that contains the following details for a location:

Cluster

Failed Calls

Total Calls

Click Troubleshoot to open the Call Failure Troubleshooting page.

On this page:

The Call Status History pane at the top left provides a bar chart showing call status history for the last 24 hours.

The Call Distribution by Release Code pane at the top right provides hourly details about call failure distribution by release code. By default, the details for the most recent hour is displayed.

Click the bar in the bar chart in Call Status History pane to open the call distribution pie chart for a particular hour.

Click the pie chart in the Call Distribution by Release Code pane to open the Release Code Details pane at the bottom of the page. This pane provides details about the calls.

Top 5 WAN Traffic Locations

The Top 5 WAN Traffic Locations dashlet provides information about the five locations for which bandwidth usage is the highest.

The table shows the location name, the number of calls failed in the last hour, and the bandwidth used, as a percentage, per location.

By default, the table is sorted based on the number of failed calls. If there are no failed calls, then the table is sorted based on bandwidth used. Also, if two or more locations have the same number of failed calls, the sort order is based on the bandwidth used.

Bandwidth Usage Legend:

1 to 50 percent—Green

50 to 70 percent—Orange

70 to 100 percent—Red

Click the location name to view a graph that provides details on the bandwidth consumed, active calls, and No BW Failed calls.

The data for the last hour is shown. Data is polled every four minutes.

The right side of the Y axis shows the number of calls. The left side of the Y axis displays the bandwidth.

The brown line indicates No BW Failed calls. The green line indicates active calls. Active calls shows all the calls that are active at a particular point of time. In case of No BW Failed calls, the graph shows the number of failed calls in each four minute interval.

You can view tooltips that display active calls, No BW failed calls, and bandwidth used when you place the cursor on the X axis coordinates for each four-minute interval, on the lines that indicate the active or failed calls.


Note During daemon manager restart, or if a device is newly added, some data might be missing.


If the bandwidth usage is constant, there is a variation in the shade across the graph.

UC Services Health Summary

The UC Services Health Summary dashlet provides the most recent data about the number of Unified Communications applications that are down or active.

The X axis displays the number of applications. The Y axis displays the application type.

Green indicates applications that are active. Orange indicates applications that are down.

You can click in the bar to open a popup that provides the following details:

Name—IP address or DNS name of the application.

IP Address

Error Reason—The reason the application is down.

Troubleshoot—Click to open a troubleshooting page and the Event Details page for the application. The details available on the troubleshooting page depend on the application type:

Cisco Unified Communications Manager—UCM Diagnostic View

Cisco Unity Connection—Voicemail Diagnostic View

Other devices—Detailed Device View

The following table gives details about the services and events that are considered in classifying the application as down.

Application
Event
Service Affected

Cisco Unified Communications Manager

ServiceDown

Call Manager service

ServiceStopped

Call Manager service

Unresponsive1 .

 

Cisco Unified Communications Manager Business Edition

ServiceDown

Call Manager service

ServiceDown

Connection Conversation Manager

ServiceStopped

Call Manager service

ServiceStopped

Connection Conversation Manager

Unresponsive

 

Cisco Unity Connection

ServiceDown

Connection Conversation Manager

ServiceStopped

Connection Conversation Manager

Unresponsive

 

Cisco IP Communicator

ComponentDown

 

Unresponsive

 

IPCCExpress

ServiceDown

CRS Node Manager-CRS Cluster View Daemon

ServiceDown

Unified CCX Node Manager-Cisco Unified CCX Cluster View Daemon

ServiceDown

Cisco Unified CCX Node Manager-Cisco Unified CCX Cluster View Daemon

ServiceDown

Cisco Unified CCX Engine

ServiceDown

Cisco Application Engine

Unresponsive

 

Cisco Unified MeetingPlace Enterprise

ServiceDown:

MeetingPlace System Integrity Manager

ServiceDown

Cisco Unified MeetingPlace System Integrity Manager

Unresponsive

 

Cisco Unified MeetingPlace Express

ServiceDown

MeetingPlace Application

ServiceDown

MeetingPlace Web Conference Core

Unresponsive

 

Cisco Unified Customer Voice Portal

ServiceDown

ProductName:vxm

Unresponsive

 

Cisco Unified Presence Server

ServiceDown

Cisco UPS Presence Engine

ServiceDown

Cisco UP Presence Engine

ServiceStopped

Cisco UPS Presence Engine

ServiceStopped

Cisco UP Presence Engine

Unresponsive

 
1 Only ICMP Unresponsive is considered, SNMP unresponsive is not be considered. This is applicable for all applications.

If the device is unreachable, it is marked as down.

Top 5 Poor Call Quality Location

The Top 5 Poor Call Quality Location dashlet provides information about the five locations experiencing the poorest call quality in the last hour.

See Service Monitor documentation for information about the criteria for poor calls.

The X axis shows the location. The Y axis shows the number of poor calls. The Z axis shows the percentage of poor calls, represented as bubbles. If the percentage of failed calls in a location is less than 0.5, the location is ignored.

The data is shown based on the availability of Cisco Voice Transmission Quality (CVTQ) data. Prime UOM aggregates the available CVTQ data at fixed time intervals and displays it in this dashlet.


Note It is possible for the Service Monitor CVTQ Diagnostic Report to have more recent data than what is available via the dashlet at any particular time.


Troubleshooting

Click the bubble to open a popup that has the details about the following:

Cluster

Poor calls

Total calls.

Click Troubleshoot to open the Call Quality Troubleshooting page.

On this page:

The Call Quality Trend pane at the top left shows the poor calls for the last 24 hours, per location.

The Impacted Devices pane at the top right shows the devices that are involved in the call for that particular hour. By default, the impacted devices for the most recent hour are shown. Click any bar in the Call Quality Trend pane to view the details about impacted devices for that hour.

Click the bars in the Impacted Devices pane to open the Call Details pane at the bottom of the page.

The Call Details pane displays the following details:

Cluster ID

Caller

Directory Number

Device Type

Codec

Location

Device Pool

Called

Directory Number

Device Type

Codec

Location

Device Pool

Signalling Time

Duration(s)

MOS

Impairment Details

Jitter (ms)

Latency

Packet Loss

Top 5 Utilized Trunks/Route Groups

The Top 5 Utilized Trunks/Route Groups dashlet provides information about the five most utilized trunks/route groups in terms of channel usage (indicated in blue). If channel usage is constant, there is a variation in the shade across the graph.

The table for trunks shows the following details:

Name—The trunk name.

Gateway IP—Click the IP link to open the Gateway summary page.

Route Group—The route group to which the trunk belongs. If gateway or trunk does not belong to any of the route groups, the value is shown as N/A.

Channel Usage—Channel usage, as a percentage.

The table for route groups shows the following details:

Name—The route group name.

Cluster Name—The name of the cluster to which the route group belongs.

Channel Usage—Channel usage, as a percentage.

Channel Usage Legend:

1 to 50 percent—Green

50 to 70 percent—Orange

70 to 100 percent—Red

Click the channel utilization bar to display a graph that plots trunk utilization or route group utilization against time. The data for the last hour is displayed.

You can view popups that display the usage as a percentage when you place the cursor on the X axis coordinates for each four-minute interval. The tooltip displays the time, and the channel usage as a percentage. To open a detailed performance graph showing trunk or route usage, click the points on the graph or the channel utilization bar that correspond to the X axis coordinates.


NoteTI and E1 trunks are supported; SIP trunks are not supported.

SIP route groups are not supported.

Only route groups with pure MGCP gateways are supported.

Fault Monitor Dashboard

Fault Monitor is a a real-time dashboard that displays event information on devices, clusters, and phones. Cisco Prime Unified Operations Manager (Prime UOM) uses Fault Monitor to manage the real-time information about the operational status of your network.

In addition to displaying the event data in Fault Monitor, the backend processes of Fault Monitor share the information with all of the other Prime UOM windows. The displays are designed so that you can set them up and leave them running. This provides an ongoing monitoring tool that alerts you when something needs attention.

When a fault occurs in your network, Prime UOM generates an event or events. If the event occurs on an element in your active view (a logical grouping of device groups), it is shown in any of the monitoring tools, including Fault Monitor.

Diagnostics Views Dashboard

The Diagnostics Views dashboard allows you to view important statistics and details of this and other network management applications installed on your network management server. You can see all of this on a single page, instead of navigating through several pages. For details on the available views, see Using the Portal in Cisco Prime Unified Operations Manager, page 3-1.

Reports Dashboard

Prime UOM enables you to generate several types of reports. See the following sections for a description of the reports you can access through the Reports tab:

Event History Reports, page 1-18

Service Quality History Reports, page 1-18

Audio IP Phone Reports, page 1-18

Video IP Phones Report, page 1-18

Personalized Reports, page 1-19

Event History Reports

Event history provides the history of Prime UOM events. The stored history includes event information and properties (component name and MIB attributes) and annotations (informational text entered by Prime UOM users).

The Event History report can display information for both devices and clusters.

You can start Event History in the following ways:

From the Fault Monitor Device or Event Details display.

From any event details display through the Actions menu.

By selecting Reports > Event History > Event History or Reports > Service Quality Event History > Event History.

This method provides historical information about all events in the Event History database. The Event History database retains information for the events that occurred within the last year.

You can use Event History to generate customized reports of specific events, specific dates, and specific device groups.

Service Quality History Reports

Service Quality History reports enable you to view service quality events that occurred during the past year. The available information includes event status and date, related devices, MOS value, codec type, and other event details.

Service Quality is useful only if you have purchased a license for Cisco Unified Service Monitor (Service Monitor). For more information, see User Guide for Cisco Unified Service Monitor.

Audio IP Phone Reports

Audio IP phone reports provide detailed phone data that reflect the current status of phones in your network.

Audio IP phone reports enable you to search for a few phones, list a specific set of phones, such as phones connected to a switch, phones in SRST mode and phones that are CTI applications, ATA devices, or Cisco 1040 sensors. You can also view all audio phones and lines.

You can also run phone status change reports to collect data on IP phone moves, phone audits, removed IP phones, extension changes, duplicate MAC/IPs, suspect phones, and export phone data.

Video IP Phones Report

Video IP phones reports provide detailed video phone data that reflect the current status of video IP phones in your network. These reports enable you to search for a few video phones, list a specific set of video phones, such as phones connected to a switch or phones in SRST mode. You can also view all video IP phones and lines.

You can also run phone status change reports to collect data on video phone moves, phone audits, removed video IP phones, extension changes, and export phone data.

Personalized Reports

The Personalized Report enables you to configure a report for the devices, phones, and diagnostic tests that interest you. Other users cannot configure or view this report from Prime UOM.

What Administrative Tasks Do I Need to Perform?

Prime UOM includes the following administrative tasks you need to perform to make it run smoothly:

Managing Devices, page 1-19

Configuring Notifications, page 1-20

Setting Polling and Thresholds, page 1-20

Setting System Settings, page 1-20

Managing External Cisco Unified Communications Management Links, page 1-20

Creating and Running Diagnostic Tests, page 1-20

Managing Devices

Device Management involves maintaining the inventory of devices that Prime UOM monitors so that it is current.

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

Before Prime UOM can start to monitor your network:

You need to configure the DCR and Prime UOM device selection. Configuring the DCR involves understanding the options and deciding what is best for your site.

Prime UOM needs to complete inventory collection.

The following scenario describes the process for managing devices:

Table 1-2 lists the steps that you need to complete.

Table 1-2 How to Start Monitoring Devices

 
Description
References

Step 1 

Add devices to the DCR.

You have three options:

 

Use Prime UOM to add devices to the DCR. This is called physical discovery

Understanding the Device and Credentials Repository, page 7-6

Share a master repository with applications on other servers.

Bulk import using a seed file to import devices into the DCR.

See the instructions in the Common Services online help.

Step 2 

Configure device selection.

Automatically Importing DCR Devices, page 7-22

Manually Importing DCR Devices, page 7-23

Step 3 

Allow inventory collection to complete and start to monitor devices.

Using the Modify/Delete Devices Page to Generate a Device Report, page 7-36

Step 4 

Verify device import by using the Fault Monitor.

Verifying Device Import, page 7-25

Configuring Notifications

In addition to watching network conditions as they change on the Unified Dashboard displays, you can use notification services to automatically notify users and other systems when specific changes occur on selected devices, device groups, and clusters.

To do so, you must create subscriptions for either e-mail notification or Prime UOM-generated SNMP trap notification.

Subscriptions comprise:

A list of devices and device groups of interest

The status and severity of alarms for which you want notification

One or more recipients

You can add, edit, and delete subscriptions whenever you need to disseminate the status and severity of alarms changes.

Setting Polling and Thresholds

Prime UOM is preconfigured with default settings for polling parameters and thresholds for each system-defined device, device pool, port, and interface group. Optionally, you can change them. For details on how to set customized polling and threshold settings, see Updating Polling Parameters and Thresholds, page 19-10.

You should ensure that polling is enabled if you want to collect certain device data.

Setting System Settings

To set system settings, see Performing System Administration Tasks, page 20-27. Some system settings are required.

Managing External Cisco Unified Communications Management Links

You can add links to Prime UOM to launch other Cisco Unified Communications Management Suite applications such as Service Monitor, Provisioning Manager, and Service Statistics Manager, see Setting Up Cisco Unified Communications Management Application Links, page 21-1.

Creating and Running Diagnostic Tests

Prime UOM provides five types of diagnostic tests; see the following sections for a description of each:

Phone Status Tests, page 1-21

Phone Tests, page 1-21

Synthetic Tests, page 1-21

Batch Tests, page 1-21

Node-to-Node Tests, page 1-22

Phone Status Tests

Phone status testing uses Cisco IOS IP Service Level Agreement (IP SLA) technology to monitor the status of key phones in the network. A phone status test consists of the following:

A list of IP phones to test, selected by you.

A testing schedule that you configure.

IP SLA-based pings from an IP SLA-capable device (for example, a switch, a router, or a voice router) to the IP phones and, optionally, pings from Prime UOM to the IP phones.

Phone Tests

The on-demand phone testing takes control of a real phone in the network and makes a call from that phone to another phone. Phone tests use the JTAPI credential.

The JTAPI credential must be configured in Communications Manager. The JTAPI phone tests now support E.164 ("+") dialing support and phones with extensions in this format. While running a phone test on demand, the JTAPI credentials must be provided in the phone test creation UI.

Synthetic Tests

Synthetic tests are used to measure the availability of voice applications. Synthetic tests verify whether the voice application can service requests from a user. For example, you can use synthetic tests to verify that phones can register with a Cisco Unified Communications Manager.

Synthetic tests use synthetic phones to measure the availability of voice applications by emulating your actions. For example, a synthetic test places a call between clusters and then checks whether the call is successful.

Prime UOM supports synthetic testing for the following:

Cisco Unified Communications Manager and Cisco Unified Communications Manager Express

Cisco TFTP Server

Cisco Emergency Responder

Cisco Unity and Cisco Unity Express

Batch Tests

Batch tests enable you to test the health and connectivity of a branch office. Batch tests consist of a set of synthetic tests that are run on voice applications (for example, Cisco Unified Communications Manager Express or Cisco Unity Express) that are deployed in a branch office and a set of phone tests that are run on real phones in the branch office.

Batch tests can be run once a day to verify the health of the voice network in the branch office.

Node-to-Node Tests

Node-To-Node tests monitor the response time and availability of multiprotocol networks on both an end-to-end and a hop-by-hop basis. After collecting this data, you can use the Prime UOM graphing function to examine changes in network performance metrics. You can select, display, and chart network performance data in real time.

How Does Prime UOM Work?

These topics provide a simplified view of Prime UOM user tasks and Prime UOM processing:

Users Perform Device Management and Configuration, page 1-22

Prime UOM Performs Ongoing Monitoring, Analysis, and Notification, page 1-25

Users Respond to Notifications and Events, page 1-26

Users Perform Device Management and Configuration

Users supply the information that tells Prime UOM what to monitor. Figure 1-1 shows a user importing devices and phones, and performing optional configuration tasks to optimize Prime UOM.

Figure 1-1 The Role of User Input

Users supply the following information:

Devices—You must import devices and, as your IP telephony environment and IP fabric change, you must add and delete them accordingly. Prime UOM can perform periodic inventory collection for enterprise users, refreshing the inventory of phones, known devices, and device components.

For multiple end-user customers, Prime UOM performs updates to existing inventory, but you must manually perform device import or add new devices to ensure your inventory is accurate.


Note Prime UOM monitors only supported devices. To see the device support table for Prime UOM, log into Cisco.com.


In order to manage a subscriber in Prime UOM, SNMP Service needs to be enabled on the device. Otherwise the device cannot be managed.

For example, for Communications Manager clusters and phone discovery to occur for all Publisher and Subscriber nodes, SNMP Service needs to be enabled on all the Communications Managers and the devices need to be added to Prime UOM with their read access credentials.

See the device documentation for details on enabling SNMP Service.

Phones:

Phone Status Tests—To perform phone status tests, you must select the phones to test by importing tests for phones that are already managed by Prime UOM.

SRST Monitoring—To determine when phones are running under SRST, you must import information for tests.

Supported IP telephony applications—Prime UOM polls and rediscovers the devices on which supported IP telephony applications (for example, Cisco Unified Communications Manager) run, just as it does for any other supported device that you import.

In addition, you can set up synthetic tests to monitor IP telephony applications such as Cisco Emergency Responder.

You can decide how to manage the information about events and traps that Prime UOM produces. For example, you can:

Create user-defined device groups for enterprise users or for multiple end-customer users create customer groups during device import or add. This enables users to monitor specific groups of devices on the Unified Dashboard displays.

Create subscriptions to send e-mail and generated SNMP trap notification to users and systems, respectively.

Determine where to forward traps by configuring the port to which Prime UOM forwards them.

You can also control how often Prime UOM gathers data. Prime UOM receives traps in real time, but you can change the frequency with which it performs the following tasks:

Polling—You can change the default polling parameters for device groups, altering the polling interval, timeout, and number of retries.

Device discovery—You can suspend the default discovery schedule.

Phone discovery—You can add, delete, or edit the schedules for phone discovery.

Synthetic testing—You can change the frequency with which tests are run. In addition, you can change the range of time during which tests do not run.

Phone status testing—You can set the interval for phone status tests.

Node-to-Node testing—You can schedule the frequency with which tests should run.

SRST monitoring—When you import SRST information, you set the intervals at which tests run. You can update SRST information by importing it again.

Prime UOM Performs Ongoing Monitoring, Analysis, and Notification

Prime UOM continuously gathers information from devices, device groups, clusters, and device components, analyzing and prioritizing events, and raising events.

Figure 1-2 Prime UOM Continuously Monitors the IP Fabric

Prime UOM generates events based on the following activities:

Polling—During polling, Prime UOM identifies conditions that warrant generating an event, such as device unreachable or interface down.

Managing thresholds—After polling, Prime UOM compares the data it collected against threshold values for the devices. If threshold values exceed or do not meet limits, Prime UOM generates the appropriate event.

For example, if a T1 port's utilization is higher than 90 percent, Prime UOM raises an event in the Events History Display. For details on how Operations Manager manages both syslog and real-time monitoring collected thresholds, see Configuring Polling and Thresholds, page 19-1.

Receiving SNMP traps—Prime UOM listens for traps on the default port or the port that you have configured for SNMP trap receiving. Prime UOM will process the traps from known, supported devices.

Testing—You can configure Prime UOM to run the following types of tests:

Synthetic testing—Synthetic testing of selected functions on a Cisco Unified Communications Manager can uncover problems that Prime UOM reports.

Phone status testing—Prime UOM can use IP SLA technology to monitor the reachability of key phones in the network.

Node-to-Node testing—Prime UOM can use IP SLA technology to test the response time and availability of multiprotocol networks on both an end-to-end and a hop-by-hop basis.

SRST testing—Prime UOM can alert you when a branch office is operating under SRST.

As Prime UOM generates events and event conditions change, Prime UOM determines when to send e-mail notification to subscribers and when to generate SNMP traps to send to other systems.

For additional information, see the following topics:

MIBs Polled and Perfmon Counter Objects Used, page B-1

Processed SNMP Traps, page C-1

Events Processed, page E-1

Polling—SNMP and ICMP, page F-1

How Prime UOM Calculates Repeated Restarts and Flapping, page G-1

Users Respond to Notifications and Events

Most users will monitor the condition of the IP telephony system by using the Fault Monitor display; others will respond to e-mail. External hosts will receive generated SNMP traps. Figure 1-3 shows how you can respond using the Events History display.

Figure 1-3 Users Respond to Events

Supported Special Characters List

Prime UOM supports the special characters in Table 1-3. If your device or device information contains unsupported characters, there may be unexpected results if any of the unsupported characters are used in any of the fields shown in Fault Monitor or Service Quality events reports.

The supported special characters may be different across various applications and for various screens and user input.

See the Release Notes for Cisco Prime Unified Operations Manager for details on how to deal with unsupported characters.

Table 1-3 Supported Special Characters in Prime UOM

Character or Digit
Description

A to Z

All upper case letters

a to z

All lower case letters

Digits 0 through 9

All numbers

#

Number sign or hash mark

$

Currency symbol

&

Ampersand

_

Underscore

:

Colon

+

Plus sign

?

Question mark

( )

Left and right parentheses

{}

Wavy brackets


Understanding the Basics

These topics help you to work with and understand the Prime UOM user interface:

Starting Prime UOM, page 1-27

Working with Prime UOM Windows, page 1-28

Using Displays and Reports, page 1-30

Selecting Objects and Groups, page 1-33

Using the Search Tool, page 1-35

Understanding Your User Role, page 1-36

Responding to Security Alerts, page 1-36

Responding to Messages About Device Limits, page 1-37

Starting Prime UOM

You can access Prime UOM from either the Prime UOM server or a client system.

If a client system is available, it is recommended that you perform all configurations and day-to-day activities on the client system.

If a client system is not available, the Prime UOM server must also meet all the system requirements for a client system (for client system requirements, see Installation Guide for Cisco Unified Prime UOM).

Starting Prime UOM on a Client System

In Internet Explorer enter the Prime UOM server's IP Address or DNS name followed by the port number 1741 or 80. For example, http://om_server_name:1741.

Starting Prime UOM on the Prime UOM Server

From the Windows desktop select Start > All Programs > Cisco Unified Prime UOM and Service Monitor > Cisco Unified Prime UOM and Service Monitor.

If Enhanced Security is enabled on the Windows 2003 system, you must add the Prime UOM home page to the Internet Explorer Trusted Sites Zone.

You will not be able to access the Cisco Prime Unified Operations Manager home page until it is added to the trusted sites. (See Adding the Prime UOM Home Page to the Internet Explorer Trusted Site Zone, page 1-28.)

Devices and voice applications, as well as the Prime UOM server must have fully-qualified domain names or be included in the host name file.

Adding the Prime UOM Home Page to the Internet Explorer Trusted Site Zone

If Enhanced Security is enabled on the Windows 2003 system, you must do the following before you can access Prime UOM's home pag:


Step 1 Open Prime UOM, select Start > Programs > Cisco Unified Prime UOM > Cisco Unified Prime UOM.

Step 2 In the File menu, click Add this site to.

Step 3 Click Trusted Sites Zone.

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

Step 5 Click Close.

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

Step 7 Check the Status bar of the browser to confirm that the site is in the trusted sites zone.


Working with Prime UOM Windows

This topic focuses on questions you may have when you first start to work with the Prime UOM user interface:

Why do I see the error "The page cannot be displayed"?, page 1-28

When I press the Enter key, why doesn't Prime UOM complete the current task?, page 1-28

Where is the Help button?, page 1-29

How Are Dates and Times Displayed?, page 1-29

How Are Phone Counts Displayed in Fault Monitor, Diagnostics Views, and Reports?, page 1-29

Using the Search Tool, page 1-35

Why do I see the error "The page cannot be displayed"?

Prime UOM displays links to more detailed information. Right-clicking a link and selecting Open in New Window is not supported. It is expected behavior for this error to appear.

When I press the Enter key, why doesn't Prime UOM complete the current task?

Prime UOM does not accept pressing the Enter key as a substitute for clicking buttons, such as OK, Finish, or Next, on the application page.

Where is the Help button?

The Help button is located in the top right corner of the window. On some windows help may be a question mark icon.

To start help:


Step 1 Click the Help button in the top right corner.

If you have a display open, click the question mark icon.

If you have selected an option in the navigation tree, the context-sensitive help for that option is displayed.

Help is displayed in a separate browser window that remains open until you close it. Online help includes an index and search capability.

Step 2 Click on the E-Learning button in the Help header.

A separate browser opens and displays the first video. You may select from several videos.


How Are Dates and Times Displayed?

Dates and times displayed by Prime UOM reflect the date, time, and time zone set on the server where Prime UOM is installed. If the client system that you use to run Prime UOM is located in a time zone other than the time zone set on the server, you will notice the difference; for example:

Status "as of" the current date and time will not display your local time and time zone and may not match your local date.

Dates and times shown for previous events are recorded (and displayed) with the server time stamp, which is offset from your local time.

There are no settings that you can change on the client, to affect the time zone displayed by Prime UOM. However, you can obtain information about the time zone acronyms and offsets used by Prime UOM in Release Notes for Cisco Prime Unified Operations Manager 2.0. You can view the release notes on Cisco.com.

How Are Phone Counts Displayed in Fault Monitor, Diagnostics Views, and Reports?

The total physical phone count may be displayed differently in some reports and pages in Prime UOM. Table 1-4 describes how phone lines display in Prime UOM.

Table 1-4 Phone Count Display

Screen or Page
Description

Device Management: Summary

Total Phones shows the total number of unique physical phones in the managed network. The count does not include multiple lines for the same phones.

When you click on the number, it launches a report that shows multiline phones with comma-separated extensions in the same row.

Reports: All IP Phones/Lines

Shows all audio phone lines in the network in a report. Multiline phones are represented by different rows and records.

Reports > Audio or Video IP Phones/Lines

Shows all audio or video phone lines in the network (in Prime UOM user interface) in a report. Multiline phones are represented by different rows and records.

Diagnostic Views portlets: Click to view all phones

Shows all phone lines in the network in a report. Multiline phones are represented by different rows and records.

Cluster View: Summary Panel

Registered phone count indicates the total number of unique physical phones registered in the selected cluster.

Unregistered phone count indicates the total count of unique physical phones unregistered in selected cluster.


Using Displays and Reports

Prime UOM presents information in displays and reports. The displays and reports usually use tables to format the information. The tables help you to handle information by providing the following features. Depending on the report, the features available in each report may vary:

Filter—You can manipulate how data is displayed based using filter parameters. Filter fields may change depending on the window. See Filtering Display Data, page 1-31.

Search—You can search on a string of characters to locate an IP address or hostname.

Sort—You can sort a display in the order you prefer by clicking any clickable column heading. See Paging and Sorting Displays and Reports, page 1-32.

Page sizing—You can change the number of rows to view on a page. You must refresh the page in order to view the new page size.

Direct page access (only in reports)—You can browse a report screen by screen or jump to any screen number in the range by entering a screen number.


Note A report can show up to 2,000 records. If more than 2,000 records exist and you need to access the additional records, you can export all records using the data export icon.


Data export—You can export data from a display to a comma-separated values (CSV) file, a Portable Document Format (PDF) file, or both, depending upon the display that you are using. See the icon in Table 1-5. Some reports may not be exportable.

Print-friendly format—You can format the display for a printer and print the result from the browser. Like the display, the print-friendly browser display includes a maximum of 1,000 records. See the icon in Table 1-5.

Add unmanaged devices—From the Unmanaged Devices report you can add devices into the DCR.

Refresh—Redisplays the table page. See the icon in Table 1-5.

Clear—Returns the table display to its original state.

Help—Access help page. See the icon in Table 1-5.

This section contains:

Filtering Display Data, page 1-31

Paging and Sorting Displays and Reports, page 1-32

Viewing Data from Reports with Over 2,000 Records, page 1-32

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

Printing Displays or Reports, page 1-33

Filtering Display Data

Filters allow you to manipulate tables and displays to show information, based on your selected parameters. Display filter parameters vary, depending on the window.

After you use an event filter, the filter is applied to all of your views until you change the filter. Other users are not affected by your filter choices. When you close the display, your filters are removed. Filters do not affect severity icons in the view pane.

For details on filtering data in Fault Monitor, see Filtering Events or Devices, page 4-10.

To apply filter:


Step 1 Click the filtering button in the tool button area at the top-right of the display.

You should click Reset if any data appears in the filter window.

Step 2 Enter the filter parameters.

You may be able to select from a selector, use wildcards, or select specific dates as your filter parameters.

Step 3 Click Apply Filter.

Step 4 Click Reset to start over and reenter new filter parameters.


Window Command Buttons

The command buttons in Table 1-5 may be available in various Prime UOM windows.

Table 1-5 Window Command Buttons

Icon
Action

Refreshes data in each panel or table.

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

Exports all data to either a CSV file or a PDF file.

Sets window preferences.

Accesses the help page for this display or report.


Paging and Sorting Displays and Reports

The sort order for any display or report is indicated by a triangle in the column heading. A triangle pointing down, indicates records in descending order, which is the default. A triangle pointing up, indicates records in ascending order.

To sort a display, click any blue column heading label.

The first time you click a column heading on a previously unsorted column, data in that column is sorted in descending order. If you click the column heading again, the records will be sorted in the reverse order.

When you sort a display or report, if there are more than 1,000 records available, all records are sorted, not just those that are displayed. The first 1,000 records are displayed after sorting. For the Events History display, the limit is 1,000 records.


Viewing Data from Reports with Over 2,000 Records

If more than 2,000 records exist, they cannot all be shown in a report. A message will be displayed to notify you when this is the case. If you want to see data for all of the records, you must export the data to a CSV or PDF file. See Exporting Data from a Display or Report, page 1-32.

You may be able to change which of the more than 2,000 records are displayed by sorting the report. See Paging and Sorting Displays and Reports, page 1-32.

Exporting Data from a Display or Report

Most displays and reports can be exported as CSV files and as PDF files. Exported data may differ depending on which deployment you have installed. For example, multiple end customer deployments may display the Customer Name field.


Note To open a PDF file, you must have Adobe Acrobat Reader 4.0 or higher installed on your client system. However, you can save a file as a PDF file even if you do not have Acrobat Reader on your system.


To export data from a display or report:


Step 1 Click the data export icon located on the top-right side of the display or report. See the icon in Table 1-5.

If the Export to dialog box appears, select one of the following and click OK:

CSV

PDF

Step 2 Save the export file in one of the following ways:

If you selected PDF and have Adobe Acrobat Reader installed on your client system, the PDF file opens. To save the PDF file, select File > Save as from the browser and follow the instructions to save the file.

If you selected PDF and do not have Adobe Acrobat Reader installed, or if you selected CSV, follow the instructions to save the file.


If you use newer versions of Internet Explorer, the default settings for new security features can prevent file download windows from being displayed. For system requirements, see the Installation Guide for Cisco Unified Prime UOM.

If you have set the custom levels of security in Internet Explorer to medium or greater, the option automatic prompt to file download is disabled.

If you try to download data to a PDF or CSV file from Prime UOM to a client that does not have Adobe Acrobat Reader or Microsoft Excel installed, nothing happens. The PDF file or the spreadsheet is not displayed and you are not prompted to save the file.

To enable file download windows to display, do this on your desktop:


Step 1 In Internet Explorer, select Tools > Options.

Step 2 Select the Security tab and click Custom Level.

Step 3 Scroll to Downloads and for automatic prompt to file download, select Enable.


Printing Displays or Reports

To print displays or reports:


Step 1 Click the printer icon located at the top-right side of the display or report. See the icon in Table 1-5.

A new browser window opens, displaying the data in print-friendly format.

Step 2 Print the display from the new browser window.


Selecting Objects and Groups

As you use Prime UOM, you will often need to select something (for example a device or a device group) before you can view information or complete a task. Groups and devices displayed in a selector differ, depending upon the application.

This topic explains what is displayed in the selectors, and how to use the selectors. The different types of groups are:

CS@item-daily—Groups that are controlled by Common Services. Subgroups are System Defined and User Defined Groups.

These groups are different from the Prime UOM groups. These groups are available only in enterprise deployments.

OM@item-daily—Groups that are controlled by Prime UOM.

System Defined Groups—The default grouping of devices in Common Services. System Defined groups cannot be deleted or edited.

For a description of each system defined group, see Working with System-Defined Groups, page 9-3.

User Defined Groups—Groups that you can edit or create to reflect the way you manage the network.

Subgroups are System Defined, User Defined, and groups you create. See Understanding Prime UOM Groups, page 9-1.

For multiple end-customer users, the Customers subgroup is also available. It contains a Default subgroup. You can create custom groups during device configuration. See Configuring Device Management, page 7-18.

You can also search for specific objects or devices using the Search Tool.

See Using the Search Tool to Locate a Device, page 1-35 or Using the Search Tool to Locate a Phone, page 1-35 for details on searching.

When you select the radio button for a group in the device selector, you select every device that is a member of the group. Figure 1-4 displays the Device Selector with All Devices Selected. You can see each device group lists the critical, warning, and informational events for each category.

Figure 1-4 Device Selector with All Devices Selected

Using the Search Tool

You can use the Search tool to:

Locate a device. See Using the Search Tool to Locate a Device, page 1-35.

Locate a phone. See Using the Search Tool to Locate a Phone, page 1-35.

Find a Location. See Using the Search Tool to Find a Location, page 1-35

Using the Search Tool to Locate a Device

To search for a specific device using the search field at the top of the view pane:


Step 1 Select the Device object type from the drop-down list.

Step 2 Enter a name or IP address or DNS name.

Step 3 Click the Arrow icon to begin the search.


Using the Search Tool to Locate a Phone

The following limitations exist for phone search:

Phone search displays a maximum of 100 phones.

If more than 100 phones are present, a warning message displays.

If a matching phone is connected to a Communications Manager Express (CME) device (rather than CCM), then you must use the phone search tree to launch the tools for those phones that display under CME clouds.

search for a specific phone:


Step 1 Select the Phone option from the drop-down list

Step 2 Enter the appropriate number for the phone (extension number, IP address, or MAC address).

The search allows wild card entries for all of these entries.

Step 3 Click the Arrow icon to run the search.


Using the Search Tool to Find a Location

To search for a specific location using the search field at the top of the view pane:


Step 1 Select Location from the drop-down list.

Step 2 Enter the location name.

Step 3 Click the Arrow icon to begin the search.

The results displays the links to the Call Failure troubleshooting view and the Call Quality troubleshooting view for that location.

See the Troubleshooting in the following sections for more details:

Top 5 Poor Call Quality Location

Top 5 Call Failure Locations


Understanding Your User Role

When you log in to Prime UOM, you enter the username and password assigned to you by a System Administrator. Your username is associated with either a CiscoWorks role or a Cisco Secure Access Control Server (ACS) role.

By default, CiscoWorks and ACS roles are the same, but an ACS administrator can edit the ACS roles. User roles control the functions that you are allowed to see and use. If you cannot locate a function in Prime UOM, the task is not permitted for the user role.

For more information, view the Permission Report to determine which tasks are permitted for each user role. To do this:

Select Administration > Server Administration (Common Services) >  Server > Reports > Permission Report and click Generate Report.

You can also view the ACS report by logging into the ACS server and selecting Shared Profile Components. See the ACS online help for more information.

For more information, see these topics:

Configuring Users (ACS and Local RBAC), page 20-27

Using Prime UOM in ACS Mode, page 20-30

Customizing User Roles, page 20-29

Responding to Security Alerts

The first time that you connect to the Cisco Prime Unified Operations Manager server, you will see a Security Alert window displayed. You should install the self-signed security certificate. You should do this once, on each client system that you use to access Prime UOM.

If you see a Security Alert Window with a message that the certificate has expired, you should contact a user with System Administrator privileges to create a self-signed security certificate. You can then install it.

If you do not install the self-signed security certificate, you may not be able to access some Prime UOM application pages.

To install this certificate:


Step 1 Click the View Certificates button on the Security Alert window.

The Certificate window is displayed.

Step 2 Install the certificate as follows:

a. Click the Install Certificate button.

The Certificate Import Wizard window is displayed.

b. Follow the instructions provided by the Certificate Import wizard.


Responding to Messages About Device Limits

If you exceed your server's device limit, Prime UOM will continue to work, but it will not allow you to import any more devices.


Note For evaluation licenses, Prime UOM phone count is 1,000 and the device limit is 300. If you have purchased licenses for more than 1,000 phones, then device limit is 2,000.


What happens next depends on whether you use automatic synchronization between the Device and Credentials Repository (DCR) and the Prime UOM inventory, or you add DCR devices to the Prime UOM inventory individually:

Manual synchronization with DCR—When you use the Device Selector page to move devices from the DCR into Prime UOM, Prime UOM will display a message warning you that you cannot import any more devices (see Understanding the Device and Credentials Repository, page 7-6).

Automatic synchronization with DCR—You will notice that devices do not appear on the Prime UOM pages. You can check the license log for more information (see Accessing and Deleting Log Files, page 20-20).

For information about device-based licensing, see Installation Guide for Cisco Prime Unified Operations Manager.