Table Of Contents
Using Performance Graphs
How to Use Performance Graphs
What Metrics Can I Include on a Graph?
Performance Graphing Notes
Launching a Performance Graph
Working with Graphs
Understanding How to Use the Graph Window
Channel Status Graphing Example
Working with a Merged Graph
Troubleshooting Performance Graphs
Using Performance Graphs
These topics explain how to use performance graphs:
•
How to Use Performance Graphs
•Working with Graphs
How to Use Performance Graphs
Cisco Prime Unified Operations Manager (Cisco Prime UOM) allows 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 Service Level View, Detailed Device View, Event Details page, some portal pages, and Node-to-Node Tests page.
You can create performance graphs from the current or real-time data when:
•Voice utilization polling is enabled for devices. (See Editing Polling Parameters.)
Since voice utilization polling is disabled by default, you must edit the polling parameters to enable polling.
•Data is available on disk from node-to-node tests that you have configured. (See Working with Node-To-Node Tests.)
The following topics describe the data you can graph and help you to understand the information displayed:
•What Metrics Can I Include on a Graph?
•Performance Graphing Notes
•Launching a Performance Graph
•Working with Graphs
•Troubleshooting Performance Graphs
What Metrics Can I Include on a Graph?
When you create a performance graph (see Launching a Performance Graph), you select devices and then select among metrics that are appropriate to those devices. Table 7-1 summarizes the types of metrics that you can graph for each device type.
Table 7-2 summarizes the node-to-node test metrics that you can graph.
Table 7-1 Utilization Metrics that You Can Graph by Device Type
Device Type
|
CPU
|
Memory
|
Calls
|
Port Utilization
|
Channel Utilization
|
Device-Specific Usage
|
Cisco Unified Communications Manager
|
X
|
X
|
X1
|
|
•BRI
•FXS
•FXO
•T1/E1 PRI
•T1 CAS
|
Cisco Unified CM Resource Utilization:
•MOH multicast
•MOH unicast
•MTP resource
•Transcoder
•Hardware conference
•Software conference
•Percentage conference active
•Percentage conference streams active
•CTI links active
•Registered analog access
•Registered MGCP gateways
•Registered hardware phones
|
Cisco Unified Communications Manager Express
|
X
|
X
|
X2
|
|
|
•IP phones registered
•Key IP phones registered
|
Cisco Unified Communications Manager-controlled MGCP3 gateways
|
|
|
|
•FXS
•FXO
|
•T1/E1 PRI
•T1 CAS
•BRI4
|
|
Cisco Unified Communications Manager Cluster
|
X
|
X
|
X5
|
|
•BRI
•FXS
•FXO
•T1/E1 PRI
•T1 CAS
|
Cisco Unified CM Resource Utilization:
•Location bandwidth available (launched from the Diagnostics > locations portlet
|
Voice Mail Gateway
|
X
|
|
|
Voice mail and PBX ports
|
|
|
Gatekeeper
|
X
|
X
|
|
|
|
Zones6
|
Cisco IOS gateways
|
X
|
X
|
X7
|
•E&M
•FXO
•FXS
|
•T1/E1 PRI
•T1/E1 CAS
•BRI
|
DSP8
|
SRST
|
X
|
X
|
|
|
|
Minutes in SRST mode
|
Unity
|
X
|
X
|
|
•Inbound
•Outbound
|
|
|
Unity Express
|
X
|
|
|
•Inbound
•Outbound
|
|
•Capacity utilization
•Session utilization
•Orphaned mailboxes
|
Unity Connection
|
X
|
X
|
|
•Inbound
•Outbound
•Total number of active ports
•Total number of ports
•Total number of active inbound ports
•Total number of inbound ports
•Total number of active outbound ports
•Total number of outbound ports
|
|
VM Used
|
Unified CCE
|
X
|
X
|
|
|
|
•Number of contact center agents currently logged into Unified CCE
•Number of calls in progress in Unified CCE
•Number of inbound calls per second
|
Cisco Unified Border Element
|
|
|
|
•Incoming and outgoing call volume per interface
•Incoming and outgoing call volume per dial peer
•Total incoming and outgoing call volume per IP interface
•Total incoming and outgoing call volume per dial peer
•Active SIP calls
•Active H323 calls
•Transcode sessions usage
•MTP sessions usage
|
|
•Active incoming and outgoing calls per interface
•Active incoming and outgoing calls per dial peer
•Total number of incoming and outgoing calls per IP interface
•Total number of incoming and outgoing calls per dial peer
•Number of active calls using SIP
•Number of active calls using H323
•Percentage used Transcode sessions
•Percentage used MTP sessions9
|
Cisco Meeting Place
|
X
|
X
|
|
•Percentage Used Audio Ports
•Percentage Used Video Ports10
|
|
|
Cisco Unified Presence Server
|
X
|
X
|
|
|
|
•Percentage VM Used
•Active IM Sessions
•Login Rate
•Online Users
•Total XMPP Client Connections
|
Cisco Voice Portal
|
X
|
X
|
|
•Number Of Ports In Use
•Total Number Of Ports Requested
•Total Number Of Ports Request Denied
|
|
•Total Number Of Calls
|
The data files for the performance metrics listed in Table 7-1 are located on the server, in the NMSROOT\data\gsu\_#GSUdata#_ directory.
If you do not have access to the directory, contact a local administrator for the server where Cisco Prime UOM is installed. The filenames are created using the device name and the date. These files are retained for 72 hours, after which they are purged.
NMSROOT is the directory where Cisco Prime UOM is installed on your system. If you selected the default directory during installation, it can be entered as "C:\Program Files\CSCOpx" or C:\PROGRA~1\CSCOpx.
Table 7-2 Graphable Metrics for Node-to-Node Tests
Node-to-Node Test
|
Graphable Metrics
|
UDP Jitter for VoIP
|
•Source-to-destination packet loss.
•Destination-to-source packet loss.
•Source to destination jitter.
•Destination to source jitter.
•Average latency.
•Node-to-Node quality.
|
Ping Echo
|
Round-trip response time.
|
Ping Path Echo
|
Round-trip response time.
|
UDP Echo
|
Round-trip response time.
|
Gatekeeper Registration Delay
|
Registration response time.
|
Real-Time Transport
|
•Interarrival jitter.
•Packet loss.
•R factor.
•Conversational quality.
•Listening quality.
|
The data files for the performance metrics listed in Table 7-2 are located on the server, in the NMSROOT\data\N2Ntests directory. The data files in this folder are purged after 31 days. If you do not have access to the directory, contact a local administrator for the server where Cisco Prime UOM is installed.
NMSROOT is the directory where Cisco Prime UOM is installed on your system. If you selected the default directory during installation, it can be entered as "C:\Program Files\CSCOpx" or C:\PROGRA~1\CSCOpx.
Performance Graphing Notes
This section contains information you should be aware of when working with performance graphs.
Table 7-3 Performance Graphing Notes
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.
1. Select the device for which you want to graph performance metrics.
2. Select Performance.
A metrics dialog box appears.
3. Select the desired metrics, and click Next.
A dialog box appears, listing the MGCP gateway ports.
4. Select a port, and then click View.
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.
|
Zone Home text box. The zone is located on the gatekeeper system.
|
Enter the location on the gatekeeper system. This location is configured through the gatekeeper.
For details on the location bandwidth, see the Gatekeeper documentation.
1. Select the device for which you want to graph the zone home.
2. Select Performance.
A metrics dialog box appears.
3. Select the Zone Home check box.
4. Enter the location on the gatekeeper where the zone home resides.
5. Click View.
|
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.
|
Cisco Prime UOM does not display a performance graph for all Unified Contact Center Enterprise (CCE) machines
|
Cisco Prime UOM 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 Service Monitor is collecting data and Cisco Prime UOM is configured properly to receive this data.
|
Launching a Performance Graph
The performance graphs are available through the following:
•Service Level View—See Launching Cisco Prime UOM Tools.
•Event Details page—See Understanding the Layout of the Event Details Page.
•Detailed Device View—See Understanding the Layout of the Detailed Device View.
•Node-to-Node Tests page—See Viewing Test Trending.
•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. See Working with Dashboard Views, page 3-4.
Before you Begin
•Verify that Cisco Prime UOM 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. See Verifying Device Import.
•Enable the voice utilization polling settings. By default the voice utilization polling settings are not enabled. Cisco Prime UOM uses the statistics gathered during voice utilization polling for charting network performance. See Voice Utilization Settings—Polling and Editing Polling Parameters.
•Review the Performance Graphing Notes.
To launch a performance graph from the Service Level View:
Step 1 In the Service Level View (see Using the Service Level View), choose a cluster then right-click on the device for which you want to see the performance metrics.
If you want to select multiple devices, hold the Ctrl key when clicking the devices in the map view.
Step 2 From the menu, select Performance Graph.
The Metrics Selection dialog box appears within the Performance Dashboard window.
Step 3 Select one or more desired metrics, and click Add.
The performance graphs appears within the dashboard, displaying one or more graphs (see Figure 7-1).
If not all expected values are plotted on a graph, the most likely reason is that one or more values are very small in comparison to the maximum value. For example, for the values 250, 2, and 1, the smaller values, 2 and 1, will not be plotted.
If you receive errors while creating performance graphs, you can look in the Error.log file for error details. The log file is located in the NMSROOT\data\gsu\_#GSUdata#_ directory. Also, see Troubleshooting Performance Graphs.
Working with Graphs
This section covers these topics:
•Understanding How to Use the Graph Window
•Working with a Merged Graph
•Troubleshooting Performance Graphs
Understanding How to Use the Graph Window
This topic covers the following:
•Graph Window Layout
•Graph Command Buttons
•Graph Data Options
•Graph Display Options
•Channel Status Graphing Example
Performance graphs provide real-time information and historical information.
You can perform the following tasks while working with graphs:
Task
|
Action
|
Add a graph
|
Select the Plus icon on the user interface.
|
Merge graph
|
Select the Merge command button.
|
Select data for a specific block and move data with slider
|
Use the sliders that appear in the graph to specify range.
|
Maximize or minimize graphs
|
Select the Collapse/Expand command button.
|
Open graph in a separate window
|
Select the Detach command button.
|
Change between line and bar charts
|
Select the Chart drop-down menu.
|
View as a chart
|
•Select the Chart/Grid view icon.
|
View as a grid and save as in Excel
|
•Select the Chart/Grid view icon. Displays in a tabular format. which you can save as an Excel file.
|
Change metrics (if using two or more metrics)
|
Use the Metric Selector.
|
Zoom or pan to display specific sections of a graph
|
Select the Pan/Zoom icon. Displays specific sections of a graph.
|
Save graphs
|
Select View as Grid icon and then Export to Excel.
|
For an example of how to use a graph window, see Channel Status Graphing Example.
Graph Window Layout
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. Multiple performance graph windows have the same layout as shown in Figure 7-1.
Each graph contains the following information:
•Title—Reflects the metric.
•X axis—Shows a time line.
•Y axis—Displays the unit of measure.
•Legend—Includes the name of the metric and color, if more than one metric is displayed in a merged graph.
Figure 7-1 Performance Graph Window Layout
Graph Command Buttons
The following command buttons appear in various graphs:
•Merge—Merges two or more graphs into a separate graph
•Refresh—Updates the graph data in real-time.
•Collapse/Expand—Enlarges the window to full-size or reduces it to just the header.
•Detach—Opens a separate window that contains the same graph to allow you to continue to monitor this graph while your perform other tasks in Cisco Prime UOM.
•Close—Closes the graph.
Graph Data Options
Graphs display real-time data. You can choose from various data options when using the Zoom in including:
•Real Time
•Hourly Average
•Hourly Max
•Hourly Min
•History
•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 Cisco Prime UOM selects points at regular intervals and plots them in the graph.
Graph Display Options
You can show graphs as line or grid or display them as an image. You can zoom in on a section of the graph or pan specific parts of the graph. You can add metrics to a graph.
•Add a new graph to the current Performance Dashboard—Click the green Add Graph icon.
•Add metrics of different units to an existing Performance Dashboard—Click using the Merge icon. Graph displays metrics with dual axis. You can select and deselect metrics on a graph and replot.
•Chart/Grid view—Displays in a chart or a tabular format. which you can save as an Excel file.
•Line/Bar chart—Displays in line or bar chart.
•Pan/Zoom—Displays specific sections of a graph.
Channel Status Graphing Example
Use the following graphic examples of how to manipulate a Channel Status graph:
•To see the Metrics Selection window where you can select metrics such as the port/DS1 name for the E1 PRI Channel Status graph, see Figure 7-2.
•Click the green plus sign button at the top right of the Performance Dashboard to add a new graph, see Figure 7-3.
•To view what a resulting channel status graph looks like, see Figure 7-3.
•To select channels to display from the Channels Selection button, see Figure 7-4
•To maximize the Channel Status graph so you can monitor the graph while performing other Cisco Prime UOM tasks, use the Detach command button.See Figure 7-5.
•To view how to select a data range for your graph, see Figure 7-6.
Figure 7-2 Selecting Metrics for Channel Status
Figure 7-3 Resulting E1 PRI Channel Status Graph
Figure 7-4 Selecting Channels from the Channel Selector
Figure 7-5 Maximizing the Graph Using the Detach Command Button
Figure 7-6 Selecting a Custom Date Range
Working with a Merged Graph
When you select the Merge pencil icon on one of multiple graphs displayed on a page, you can select individual graph metrics to merge into a single, scaled graph. See Figure 7-7.
Figure 7-7 Multiple Graphs Displayed in a Performance Graph Window with Metrics Selector
In a merged, scaled graph, the following information is displayed:
•X axis—Shows a time line.
•Y axis—Shows numbers, but no unit of measure. The unit of measure is included in the legend.
•Dual axis—Displays when metrics displayed are different units.
•Legend—Includes the name of the device from which the data was gathered, the name of the metric, the ratio by which the data is scaled, and the unit of measure.
An example of a merged graph appears in Figure 7-8.
Figure 7-8 Merged Performance Graph
Troubleshooting Performance Graphs
Note For information about what is displayed on graphs, see Channel Status Graphing Example.
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 Cisco Prime UOM 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.
In the second case (when Cisco Prime UOM is checking for the data file), an error message saying something like No data file is available appears. The error messages appear in the performance graphing log file (Error.log) located at NMSROOT\data\gsu\_#GSUdata#_ directory.
NMSROOT is the directory where Cisco Prime UOM is installed on your system. If you selected the default directory during installation, it can be entered as "C:\Program Files\CSCOpx" or C:\PROGRA~1\CSCOpx.
For information about what is displayed on graphs, see Channel Status Graphing Example.
Table 7-4 describes the errors and their possible causes, for both of these types of situations. Possible causes for the errors provide a starting point for you to investigate and take corrective action.
Table 7-4 Troubleshooting Performance Graphing Errors
Error
|
Possible Causes
|
Cannot collect data.
|
•Account and credentials are not the same on all Cisco Unified Communications Managers in the cluster. If this is required, see Determining the Media Server Account to Use for Cisco Unified CM Access.
•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 Cisco Prime UOM 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 Device Table for Cisco Prime Unified Operations Manager on Cisco.com.
|
|
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 Cisco Prime UOM.
•Incorrect credentials in Cisco Prime UOM.
To add credentials, see Editing Device Configuration and 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 Cisco Prime UOM. For instructions, see Viewing Device Details.
If the Cisco Unified Communications Manager version number that is stored in Cisco Prime UOM is incorrect, re-add the device. See Understanding the Device and Credentials Repository.
For device support information, see Supported Device Table for Cisco Prime Unified Operations Manager on Cisco.com.
|
|
Cannot collect WMI counters from the device.
|
•The device maybe unreachable due to network problems.
•An incorrect hostname, username, and/or password was used.
•The Remote Procedure Call (RPC) service is not running on the device.
•The current user does not have permission to query WMI.
|
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 Cisco Prime UOM. For instructions, see Viewing Device Details.
If the Cisco Unified Communications Manager version number that is stored in Cisco Prime UOM is incorrect, re-add the device. See Understanding the Device and Credentials Repository.
For device support information, see Supported Device Table for Cisco Prime Unified Operations Manager on Cisco.com.
|
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 (see Viewing Polling Parameters); 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.
|
•Service Monitor must be configured properly using the maximum capacity.
•Cisco Prime UOM must have Service Monitor added to the Unified Communications Management Suite.
|
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 (see Verifying Device Import). If the device is in the Unreachable state, verify that the device's credentials are correct and rediscover the device (see Performing Manual Inventory Collection on Devices).
•If a gray line or a gray area appears in a graph, hover your mouse over it to obtain a tooltip with an explanation.
•To collect performance data for Cisco Unity Connection, Unity, Unity Express or IP Contact Center, the Windows Management Instrumentation (WMI) credential is required. When adding these devices to Cisco Prime UOM, verify that the WMI username and password are provided.
Feedback
