Table Of Contents
Managing Performance
10.1 What Is Performance Management?
10.2 What Performance Data Is Available?
10.2.1 Types of Reports
10.3 How Is Performance Data Collected?
10.3.1 Enabling Performance Monitoring
10.3.2 Understanding the PM Service Pane
10.3.3 Understanding the Individual PM Service Panes
10.3.4 Activating or Deactivating Performance Monitoring
10.3.5 Enabling or Disabling PM Data Collection on an Individual NE
10.3.6 Enabling or Disabling PM Data Collection by PM Category for CTC-Based NEs
10.3.7 Enabling PM Data Collection for the ONS 15501, ONS 15530, and ONS 15540
10.3.8 Enabling or Disabling PM Data Collection by Module for the ONS 15800, ONS 15801, or ONS 15808
10.3.9 Enabling or Disabling PM Retrieval Fail Alarms for CTC-Based NEs
10.3.10 Specifying the PM Data Display
10.3.11 Viewing the Robust PM Collection Queue
10.3.12 Using the Self Monitor Table
10.3.13 Filtering the Self Monitor Table
10.4 How Do I Query, View, Filter, and Graph PM Data?
10.4.1 Using the PM Table Query
10.4.2 Launching the PM Table for Layer 3 Links from the Network Map
10.4.3 Using the Statistics Report for Voice-Enabled Products
10.4.4 Managing Real-Time PM Data
10.4.5 Filtering PM Data
10.4.6 Generating an HTML Report for PM Tables—CRS-1 and XR 12000
10.4.7 Using PM Data Graphs
10.4.8 Understanding How CTM Displays the Interface Field
10.5 What Types of Data Reports Are Available for MGX Voice Gateway Devices?
10.5.1 Viewing Raw Data Reports
10.5.2 Viewing Utilization Data
10.5.3 Viewing Performance Data Reports
10.5.4 Exporting the Data Report
Managing Performance
This chapter includes the following information:
•
What Is Performance Management?
•What Performance Data Is Available?
•How Is Performance Data Collected?
•How Do I Query, View, Filter, and Graph PM Data?
•What Types of Data Reports Are Available for MGX Voice Gateway Devices?
Note Appendix F, "Performance Data" contains field descriptions for each PM table.
10.1 What Is Performance Management?
Performance management (PM) in a network is the configuration and measurement of network traffic for the purpose of providing a consistent and predictable level of service. PM involves monitoring the network activity and adjusting the design and/or the configuration of the network in order to improve its performance and traffic handling. It provides network and system performance reporting for determining acute and chronic problems, service level reporting, and performance optimization.
Measuring performance can identify:
•Normal baseline network performance, which can then be compared to perceived abnormal network behavior
•Current or potential utilization problems
•Slow response time
•Application, server, and network availability
•Optimum data transfer times
Performance data is useful for capacity reporting when drafting budgets or considering network redesigns. It can be used to identify congestion and trouble areas in the network that need to be relieved, either through additional equipment or through network reconfiguration. It can also be used to identify devices that are being underutilized or have available chassis slots.
Performance measurement includes:
•Performance monitoring—The collection of performance-related data from network devices. This data is useful for fine-tuning the performance of the device and for monitoring potentially service-affecting problems.
•Performance reporting—The presentation of the collected data, which can then be used to analyze faults, growth, and capacity of the network.
You can set thresholds on the reported performance data. These thresholds generate events that can be used in performance and fault management.
The PM process is as follows:
1. Gather network data and statistics
2. Analyze network performance and identify critical issues
3. Optimize network performance
4. Plan customer capacity
5. Plan network capacity
10.2 What Performance Data Is Available?
The following areas of performance are useful for measurement:
•Availability—The amount of time for which a network system or application is available to the user. From a network perspective, availability is the reliability of the individual components in the network. Accurately measuring availability of a distributed network is difficult and not very practical.
•Response time—The time required for traffic to travel between two points, typically measured for a round trip; the time it takes a packet to reach its destination and for a response to return to the sender. Response time is the best measure of how users perceive the network's performance.
•Accuracy—The amount of interface traffic that does not result in error. Accuracy can be expressed in terms of a percentage that compares the success rate to the total packet rate over a period of time. A decreased accuracy rate should be used to trigger a closer investigation of the network.
•Utilization—Measures the use of a particular resource over time. Utilization is usually expressed as a percentage of a resource's maximum operational capacity. It can be used to identify congestion or potential congestion throughout the network, as well as underutilized resources. Sudden jumps in resource utilization can indicate a fault condition.
With CTM, you can view PM data sorted by:
•NE model
•PM type
•PM category
Note PM data collection is not available for the ONS 15216, Cisco Catalyst 6509, or Cisco MDS 9000.
Note Make sure that the NE and the CTM server are synchronized. The NE generates PM statistics at 15-minute or 1-day intervals. The server collects 1-day PM data at 00:00 Greenwich Mean Time (GMT), regardless of the NE time or its time zone.
Note When configuring PM data collection, enable PM data collection for an NE on only one CTM server. CTC-based NEs do not support simultaneous sessions on HTTP for bulk PM data collection. If you enable PM data collection on multiple CTM servers, one of the servers might time out with the following error messages:
Server Error: 503 Service Unavailable
Operating System Error Nr:3997698: S_objLib_OBJ_UNAVAILABLE
Too many concurrent PM downloads
Note An alarm is generated for every piece of lost PM data for CTC-based NEs or MGX devices. A PM lost alarm (15 minutes or 1 day) is generated when CTM cannot collect PM data for 15 minutes or for 1 day when the NE's PM data collection is set to either 15 Min Robust or 1 Day Robust. If there are outstanding PM Retrieval Fail alarms, these alarms are cleared and the PM lost alarm is generated.
For voice-enabled products, CTM also collects statistics which can be viewed using the Statistics Report. Statistics are numerical values derived from the contents of event counters that are located on the service modules in the switch. The counters record the number of occurrences for a particular network event. A single switch contains separate counters for hundreds of discrete network events.
The event counters on the service modules continue to accumulate the counts of network events whether or not the counters are ever read by an operator or collected by the CTM workstation. If the content of a counter is read by you or by another application, the counter value is defined as a statistic. A single statistic refers to a counter value for a single entity; for example, a line. If you enable statistics on an NE that has 100 lines, you are dealing with 100 entities that are associated with separate sets of counters. If you requested CTM to collect statistics for that NE, CTM collects all the counter values for all the lines under that NE. If each line has 10 counters, this results in the collection of 1000 statistic values from that NE alone on every collection cycle.
Table 10-1 lists the types of statistics for voice-enabled products.
Table 10-1 Statistics Types for Voice-Enabled Products
Name
|
Description
|
Summary Statistics
|
Specifies that the summary statistics are accessible through the command line interface (CLI); for example, the dspchancnt command on the MGX nodes. See Appendix D, "Statistics Summary for Voice-Enabled Products."
Summary statistics, which are also referred to as real-time statistics, can also be accessed using SNMP through the Diagnostic Center. Summary or real-time statistics are not collected by CTM.
Note The statistics name and statistics value for the real-time counters are also used for fault management. See Chapter 9, "Managing Faults," and Appendix G, "Supported Real-Time Counters for Voice-Enabled Products."
|
Interval Statistics
|
Provides a record of the number of events over the previous 15 minutes.
Interval statistics are also known as history statistics, and are derived from the same event counters as summary statistics.
Note Interval statistics are collected by CTM using FTP.
|
The following statistic examples are used:
•Performance monitoring at network and element levels
•Resource and capacity planning
•Threshold crossing alerts; for example, alarms
•Usage records for billing
•Traffic management
10.2.1 Types of Reports
For voice-enabled products, reports of the statistics data that are collected from the switch are viewed in the Statistics Report. Choose Performance > MGX Voice Gateway > Statistics Report. Drag the NE to the right-most pane to display the statistics. The following report functions are available in the drop-down list:
•Raw Data Report
•Utilization Data Report
•Performance Data Report
10.2.1.1 Raw Data Report
The Raw Data Report selects and displays statistics data from the database:
•Lines
•Cards
•Ports
•PhysLine (physical lines)
•IMA
•Paths
•Connections
•Protocol
•PNNI Statistics
By using the Raw Data Report, you can:
•Select the statistics for the report and time period
•Display statistics information by viewing the object description; for example, port, line, card, time period for the statistics collected, statistics type, statistics value, and peak value
•Generate a report for multiple objects; for example, ports of different cards with different statistics
•Export data into .csv format
•Modify the report parameters and regenerate the report
•List the endpoint for the selected port for the Raw Data Report on connections
10.2.1.2 Utilization Data Report
Depending on the selected object, the Utilization Data Report lists the top utilized connections and ports. The Utilization Data Report supports VXSM connection reports.
You can use the utilization of an object to display a list of top utilized objects. The utilization for any object is calculated as a sum of percent bytes from the network and the percent bytes are transmitted to the network.
10.2.1.3 Performance Data Report
The Performance Data Report provides performance numbers for ports in a graphical format. Port Traffic Summary performance report types are supported.
All the performance numbers are given as an average over the time period. The following performance percentages are plotted:
•Total number of cells received
•Total number of cells transmitted
•Time in service
10.3 How Is Performance Data Collected?
Performance data collection is the process of collecting performance-related data from network devices and storing them in a database or data file. This information can then be used for locating, diagnosing, and correcting network problems to increase network reliability and effectiveness, and to ensure that fault management can be more than just handling emergencies. The data can also be used to increase the productivity of network users. There are two methods of collecting performance data:
•Active polling—Involves actively obtaining specific management data from network devices. The collected data is then stored in a database and used later for reporting. The advantage of active polling is that as long as a managed device is accessible, data is collected and stored at regular intervals. A disadvantage is that collecting large amounts of data can impact the performance of the managed device or the network. Also, reports might take a long time to generate.
•Event reporting—A managed device or agent generates a trap or event that is received and logged. This method requires that events be generated based only on thresholds, and the EMS assumes that the lack of an event indicates that the item being measured is performing within acceptable ranges. The advantage here is that the potential impact to the network is lessened. The disadvantages of event reporting are that traps are unreliable and you might not be able to determine the start or stop of an event. It can also be difficult to determine the duration and frequency of an event.
10.3.1 Enabling Performance Monitoring
Performance monitoring is optional, but you must enable it if you want to monitor threshold alarms and performance parameters.
Performance monitoring can be enabled on NEs by using the device CLI or CiscoView.
•For information about using the CLI, see the relevant hardware documentation.
•For information about using CiscoView, see Appendix I, "Using CiscoView to Configure and Monitor ONS 15501, ONS 15530, and ONS 15540 NEs."
Note PM data collection is resource intensive in terms of CPU, disk space, and DCN utilization, so you should exercise proper planning and resource monitoring for PM data collection.
10.3.2 Understanding the PM Service Pane
Use the PM Service pane (Administration > Control Panel) to activate or deactivate global PM data collection and change NE PM data collection parameters. When you click Save to save your change, the change takes effect immediately.
Table 10-2 Field Descriptions for the PM Service Pane
Field
|
Description
|
PM Data Storage
|
PM data storage status. If set to Normal, all performance data collected is displayed in the PM data tables. If set to Optimized, performance data with zero values and invalid flag data is not displayed and is not stored in the database.
|
Robust PM Collection Queue
|
Number of 15-minute and 1-day outstanding robust PM registers. Click Clear Robust PM Queue to clear the queue.
|
PM 15-Min Retrieval Fail Alarm
|
Enable or disable a retrieval fail alarm for 15-minute PM data. Check the Enable check box; then, enter the number of seconds between each retry, and enter the number of retries to attempt before the alarm is generated.
|
PM 1-Day Retrieval Fail Alarm
|
Enable or disable a retrieval fail alarm for 1-day PM data. Check the Enable check box; then, enter the number of minutes between each retry, and enter the number of retries to attempt before the alarm is generated.
|
Real-Time PM Performance Parameters
|
When a real-time PM session is running, it polls the NE for x number of attributes every 10 to 900 seconds. The data it returns is stored entirely in transient memory. Use the following fields to limit the scope of the real-time PM session:
•Maximum no. of concurrent real-time PM sessions—Specify the maximum number of concurrent real-time PM sessions allowed per client. The range is from 1 to 5 sessions; the Cisco default is 5.
•Maximum no. of polled real-time PM objects—Specify the maximum number of objects that can be polled in a single real-time PM session. The range is from 1 to 75 objects; the Cisco default is 75.
•Maximum no. of rows held in cache—Specify the maximum number of rows that can be held in the real-time memory buffer per session. When this limit is reached, the oldest rows are removed from the buffer to make room for new rows. The range is from 100 to 5,000 rows; the Cisco default is 1,000.
|
10.3.3 Understanding the Individual PM Service Panes
The PM Service properties pane (Administration > Control Panel > PM Service) displays information about the status of performance monitoring for the selected NE. You can also stop or start an individual PM service instance. The individual PM service panes are broken down by NE:
•ONS 15302/ONS 15305
•ONS 15310/ONS 15327/ONS 15454
•ONS 15454 SDH
•ONS 155xx
•ONS 15600
•ONS 15600 SDH
•ONS 158xx
•CRS-1
•MGX Voice Gateway
•XR 12000
10.3.3.1 ONS 15302/ONS 15305
The ONS 15302/ONS 15305 PM Service pane displays PM service information for ONS 15302 and ONS 15305 NEs. Table 10-3 provides descriptions.
Table 10-3 Field Descriptions for the ONS 15302/ONS 15305 PM Service Pane
Field
|
Description
|
Service Status
|
Current status of the service: Active or Not Active.
|
Service Action
|
Stops or starts a process. Notice that the Service Action button toggles between Activate and Deactivate, and that the Service Status field changes accordingly.
|
Error Level
|
Choose the error level for alarms on the selected NE to include in the error log (Critical, Major, Minor, Informational, Debug, or Trace). Critical, major, minor, and informational errors are logged to the database; trace and debug information is logged to a log file.
Caution CTM performance will degrade significantly if the trace or debug option is left on. All operations will slow down and you may lose alarm and event notifications. Use trace or debug only when troubleshooting with a customer support engineer.
|
Threshold
|
Number of NEs that will be serviced by one instance of the PM service.
|
10.3.3.2 ONS 15310/ONS 15327/ONS 15454
The ONS 15310/ONS 15327/ONS 15454 PM Service pane displays PM service information for the ONS 15310, ONS 15327, and ONS 15454 SONET NEs. Table 10-4 provides descriptions.
Table 10-4 Field Descriptions for the ONS 15310/ONS 15327/ONS 15454 PM Service Pane
Field
|
Description
|
PM Configuration Tab
|
Service Status
|
Current status of the service: Active or Not Active.
|
Service Action
|
Stops or starts a process. Notice that the Service Action button toggles between Activate and Deactivate, and that the Service Status field changes accordingly.
|
Error Level
|
Choose the error level for alarms on the selected NE to include in the error log (Critical, Major, Minor, Informational, Debug, or Trace). Critical, major, minor, and informational errors are logged to the database; trace and debug information is logged to a log file.
Caution CTM performance will degrade significantly if the trace or debug option is left on. All operations will slow down and you may lose alarm and event notifications. Use trace or debug only when troubleshooting with a customer support engineer.
|
Threshold
|
Number of NEs that will be serviced by one instance of the PM service.
|
PM Collection Parameters Tab
|
DS1 PM Collection
|
Enable or disable DS1 PM data collection.
|
DS3 PM Collection
|
Enable or disable DS3 PM data collection.
|
Physical/Section/Line PM Collection
|
Enable or disable physical, section, and line PM data collection on OC-N cards.
|
STS PM Collection
|
Enable or disable SONET STS Path PM data collection.
|
VT PM Collection
|
Enable or disable SONET VT Path PM data collection.
|
Data PM Collection
|
Enable or disable data (Ethernet, POS, SAN, 8B10B) PM data collection.
|
Physical/OTN PM Collection
|
Enable or disable physical, OTN G.709 Section, OTN G.709 Path, and OTN FEC PM data collection on DWDM cards.
|
SNMP PM Collection
|
Enable or disable CoS PM data collection.
|
E1 PM Collection
|
Enable or disable E1 PM data collection.
|
PM Service Instance
|
Start Service Instance, Stop Service Instance
|
Allows you to stop or start an individual PM service instance. If you click Start Service Instance, the service status changes to Running. If you click Stop Service Instance, the status changes to Stopped.
The list of managed NEs shows which NEs are currently being managed by the selected service instance. If you stop the specified service instance, the NEs in the list are no longer managed.
|
10.3.3.3 ONS 15454 SDH
The ONS 15454 SDH PM Service pane displays PM service information for the ONS 15454 SDH NE. Table 10-5 provides descriptions.
Table 10-5 Field Descriptions for the ONS 15454 SDH PM Service Pane
Field
|
Description
|
PM Configuration Tab
|
Service Status
|
Current status of the service: Active or Not Active.
|
Service Action
|
Stops or starts a process. Notice that the Service Action button toggles between Activate and Deactivate, and that the Service Status field changes accordingly.
|
Error Level
|
Choose the error level for alarms on the selected NE to include in the error log (Critical, Major, Minor, Informational, Debug, or Trace). Critical, major, minor, and informational errors are logged to the database; trace and debug information is logged to a log file.
Caution CTM performance will degrade significantly if the trace or debug option is left on. All operations will slow down and you may lose alarm and event notifications. Use trace or debug only when troubleshooting with a customer support engineer.
|
Threshold
|
Number of NEs that will be serviced by one instance of the PM service.
|
PM Collection Parameters Tab
|
E1 PM Collection
|
Enable or disable E1 PM data collection.
|
E3 PM Collection
|
Enable or disable E3 PM data collection.
|
E4 PM Collection
|
Enable or disable E4 PM data collection.
|
DS3I PM Collection
|
Enable or disable DS3I PM data collection.
|
High Order PM Collection
|
Enable or disable high order PM data collection.
|
Low Order PM Collection
|
Enable or disable low order (VC-3, VC-11, and VC-12) PM data collection.
|
Data PM Collection
|
Enable or disable data (Ethernet, POS, SAN, and 8B10B) PM data collection.
|
Physical/Section PM Collection
|
Enable or disable physical or section (regenerator section [RS] and multiplex section [MS]) PM data collection on STM-N cards.
|
Physical/OTN PM Collection
|
Enable or disable physical, OTN G.709 Section, OTN G.709 Path, and OTN FEC PM data collection on DWDM cards.
|
SNMP PM Collection
|
Enable or disable CoS PM data collection.
|
DS1 PM Collection
|
Enable or disable DS1 PM data collection.
|
PM Service Instance
|
Start Service Instance, Stop Service Instance
|
Allows you to stop or start an individual PM service instance. If you click Start Service Instance, the service status changes to Running. If you click Stop Service Instance, the status changes to Stopped.
The list of managed NEs shows which NEs are currently being managed by the selected service instance. If you stop the specified service instance, the NEs in the list are no longer managed.
|
10.3.3.4 ONS 155xx
The ONS 155xx PM Service pane displays PM service information for the ONS 155xx NE. Table 10-6 provides descriptions.
Table 10-6 Field Descriptions for the ONS 155xx PM Service Pane
Field
|
Description
|
Service Status
|
Current status of the service: Active or Not Active.
|
Service Action
|
Stops or starts a process. Notice that the Service Action button toggles between Activate and Deactivate, and that the Service Status field changes accordingly.
|
Error Level
|
Choose the error level for alarms on the selected NE to include in the error log (Critical, Major, Minor, Informational, Debug, or Trace). Critical, major, minor, and informational errors are logged to the database; trace and debug information is logged to a log file.
Caution CTM performance will degrade significantly if the trace or debug option is left on. All operations will slow down and you may lose alarm and event notifications. Use trace or debug only when troubleshooting with a customer support engineer.
|
Threshold
|
Number of NEs that will be serviced by one instance of the PM service.
|
10.3.3.5 ONS 15600
The ONS 15600 PM Service pane displays PM service information for the ONS 15600 SONET NEs. Table 10-7 provides descriptions.
Table 10-7 Field Descriptions for the ONS 15600 PM Service Pane
Field
|
Description
|
PM Configuration Tab
|
Service Status
|
Current status of the service: Active or Not Active.
|
Service Action
|
Stops or starts a process. Notice that the Service Action button toggles between Activate and Deactivate, and that the Service Status field changes accordingly.
|
Error Level
|
Choose the error level for alarms on the selected NE to include in the error log (Critical, Major, Minor, Informational, Debug, or Trace). Critical, major, minor, and informational errors are logged to the database; trace and debug information is logged to a log file.
Caution CTM performance will degrade significantly if the trace or debug option is left on. All operations will slow down and you may lose alarm and event notifications. Use trace or debug only when troubleshooting with a customer support engineer.
|
Threshold
|
Number of NEs that will be serviced by one instance of the PM service.
|
PM Collection Parameters Tab
|
Physical/Section/Line PM Collection
|
Enable or disable physical, section, and line PM data collection.
|
STS PM Collection
|
Enable or disable SONET STS Path PM data collection.
|
Data PM Collection
|
Enable or disable data (Ethernet and POS) PM data collection.
|
PM Service Instance
|
Start Service Instance, Stop Service Instance
|
Allows you to stop or start an individual PM service instance. If you click Start Service Instance, the service status changes to Running. If you click Stop Service Instance, the status changes to Stopped.
The list of managed NEs shows which NEs are currently being managed by the selected service instance. If you stop the specified service instance, the NEs in the list are no longer managed.
|
10.3.3.6 ONS 15600 SDH
The ONS 15600 SDH PM Service pane displays PM service information for the ONS 15600 SDH NEs. Table 10-8 provides descriptions.
Table 10-8 Field Descriptions for the ONS 15600 SDH PM Service Pane
Field
|
Description
|
PM Configuration Tab
|
Service Status
|
Current status of the service: Active or Not Active.
|
Service Action
|
Stops or starts a process. Notice that the Service Action button toggles between Activate and Deactivate, and that the Service Status field changes accordingly.
|
Error Level
|
Choose the error level for alarms on the selected NE to include in the error log (Critical, Major, Minor, Informational, Debug, or Trace). Critical, major, minor, and informational errors are logged to the database; trace and debug information is logged to a log file.
Caution CTM performance will degrade significantly if the trace or debug option is left on. All operations will slow down and you may lose alarm and event notifications. Use trace or debug only when troubleshooting with a customer support engineer.
|
Threshold
|
Number of NEs that will be serviced by one instance of the PM service.
|
PM Collection Parameters Tab
|
Physical/RS/MS PM Collection
|
Enable or disable physical, RS, and MS PM data collection.
|
High Order PM Collection
|
Enable or disable high-order PM data collection.
|
PM Service Instance
|
Start Service Instance, Stop Service Instance
|
Allows you to stop or start an individual PM service instance. If you click Start Service Instance, the service status changes to Running. If you click Stop Service Instance, the status changes to Stopped.
The list of managed NEs shows which NEs are currently being managed by the selected service instance. If you stop the specified service instance, the NEs in the list are no longer managed.
|
10.3.3.7 ONS 158xx
The ONS 158xx PM Service pane displays PM service information for the ONS 158xx NE. Table 10-9 provides descriptions.
Table 10-9 Field Descriptions for the ONS 158xx PM Service Pane
Field
|
Description
|
Service Status
|
Current status of the service: Active or Not Active.
|
Service Action
|
Stops or starts a process. Notice that the Service Action button toggles between Activate and Deactivate, and that the Service Status field changes accordingly.
|
Error Level
|
Choose the error level for alarms on the selected NE to include in the error log (Critical, Major, Minor, Informational, Debug, or Trace). Critical, major, minor, and informational errors are logged to the database; trace and debug information is logged to a log file.
Caution CTM performance will degrade significantly if the trace or debug option is left on. All operations will slow down and you may lose alarm and event notifications. Use trace or debug only when troubleshooting with a customer support engineer.
|
Threshold
|
Number of NEs that will be serviced by one instance of the PM service.
|
15-Min Collection Delay
|
Delay between different 15-minute PM data collection periods (in seconds).
|
1-Day Collection Delay
|
Delay between different 1-day PM data collection periods (in seconds).
|
10.3.3.8 CRS-1
The CRS-1 PM Service pane displays PM service information for the CRS-1 NE. Table 10-10 provides descriptions.
Table 10-10 Field Descriptions for the CRS-1 PM Service Pane
Field
|
Description
|
Service Status
|
Current status of the service: Active or Not Active.
|
Service Action
|
Stops or starts a process. Notice that the Service Action button toggles between Activate and Deactivate, and that the Service Status field changes accordingly.
|
Error Level
|
Choose the error level for alarms on the selected NE to include in the error log (Critical, Major, Minor, Informational, Debug, or Trace). Critical, major, minor, and informational errors are logged to the database; trace and debug information is logged to a log file.
Caution CTM performance will degrade significantly if the trace or debug option is left on. All operations will slow down and you may lose alarm and event notifications. Use trace or debug only when troubleshooting with a customer support engineer.
|
Threshold
|
Number of NEs that will be serviced by one instance of the PM service.
|
10.3.3.9 MGX Voice Gateway
The MGX Voice Gateway PM Service pane displays PM service information for MGX devices. Table 10-11 provides descriptions.
Table 10-11 Field Descriptions for the MGX Voice Gateway PM Service Pane
Field
|
Description
|
Service Status
|
Current status of the service: Active or Not Active.
|
Service Action
|
Stops or starts a process. Notice that the Service Action button toggles between Activate and Deactivate, and that the Service Status field changes accordingly.
|
Error Level
|
Choose the error level for alarms on the selected NE to include in the error log (Critical, Major, Minor, Informational, Debug, or Trace). Critical, major, minor, and informational errors are logged to the database; trace and debug information is logged to a log file.
Caution CTM performance will degrade significantly if the trace or debug option is left on. All operations will slow down and you may lose alarm and event notifications. Use trace or debug only when troubleshooting with a customer support engineer.
|
Threshold
|
Number of NEs that will be serviced by one instance of the PM service.
|
PM Service Instance
|
Start Service Instance, Stop Service Instance
|
Allows you to stop or start an individual PM service instance. If you click Start Service Instance, the service status changes to Running. If you click Stop Service Instance, the status changes to Stopped.
The list of managed NEs shows which NEs are currently being managed by the selected service instance. If you stop the specified service instance, the NEs in the list are no longer managed.
|
10.3.3.10 XR 12000
The XR 12000 PM Service pane displays PM service information for XR 12000 NEs. Table 10-12 provides descriptions.
Table 10-12 Field Descriptions for the XR 12000 PM Service Pane
Field
|
Description
|
Service Status
|
Current status of the service: Active or Not Active.
|
Service Action
|
Stops or starts a process. Notice that the Service Action button toggles between Activate and Deactivate, and that the Service Status field changes accordingly.
|
Error Level
|
Choose the error level for alarms on the selected NE to include in the error log (Critical, Major, Minor, Informational, Debug, or Trace). Critical, major, minor, and informational errors are logged to the database; trace and debug information is logged to a log file.
Caution CTM performance will degrade significantly if the trace or debug option is left on. All operations will slow down and you may lose alarm and event notifications. Use trace or debug only when troubleshooting with a customer support engineer.
|
Threshold
|
Number of NEs that will be serviced by one instance of the PM service.
|
10.3.4 Activating or Deactivating Performance Monitoring
Step 1 In the Domain Explorer window, choose Administration > Control Panel.
Step 2 In the Control Panel window, expand PM Service.
Step 3 Select an NE type.
Step 4 All the NEs monitored by the server stop collecting PM data if you click the Deactivate button in the PM Configuration tab > Service Action field. (Notice that the service status toggles to Not Active.) Click Activate to resume PM data collection.
Note If you need to activate or deactivate the PM Service again, go to the Service Monitor table (Administration > Service Monitor in the Domain Explorer) to verify that the service has stopped or started before clicking the Activate or Deactivate button again.
Step 5 Ensure that the PM Service has started. In the Domain Explorer, choose Administration > Service Monitor. The Service Monitor table should include an entry for the relevant PM Service.
Note If the PM Service is active and the NE time is changed so that the difference between the CTM server time and the NE time is 30 minutes, the existing PM buckets (for the time stamps corresponding to the next collection interval on the NE, after the time change) collected by CTM are marked as In Maintenance. CTM collects PM buckets again for the same time stamps.
10.3.5 Enabling or Disabling PM Data Collection on an Individual NE
Step 1 In the Domain Explorer or Subnetwork Explorer tree, select the NE node for which to stop or start PM data collection. The Network Element Properties pane opens.
Step 2 In the PM Collection area of the Status tab, set the PM data collection state. Options vary by NE type:
•15 Min—Check this box to enable collection of PM data every 15 minutes. Uncheck to disable PM data collection.
•1 Day—Check this box to enable collection of PM data every 24 hours. Uncheck to disable PM data collection.
•15 Min Robust—Check this box to enable collection of PM data every 15 minutes and attempt to fill in gaps in PM data collection should they occur.
•1 Day Robust—Check this box to enable collection of PM data every 24 hours and attempt to fill in gaps in PM data collection should they occur.
Caution If robust PM data collection is enabled, do not set PM data storage to Optimized.
Note•You cannot collect robust PM data until at least one 15-minute or one 1-day interval has been collected in normal operation.
•Robust PM data collection applies only to CTC-based NEs and to the ONS 15302, ONS 15305, ONS 15530, ONS 15540, ONS 15800, ONS 15801, and ONS 15808. Robust PM data collection is not supported for the ONS 15216, ONS 15501, Catalyst 6509, CRS-1, XR 12000, MGX, or MDS 9000.
Note•For the CRS-1 and XR 12000, set the PM data collection state to 15 Min. Unlike other NEs, the CRS-1 and XR 12000 notify CTM when PM data is ready to be collected based on what is configured by the user on the NE. The CRS-1 and XR 12000 use TFTP to send PM files to a TFTP server and notify the CTM server when finished. PM files are not purged from the TFTP server after CTM retrieves them; therefore, you must monitor disk space and purge files when required.
•Enabling PM data collection for the CRS-1 and XR 12000 requires configuring PM on the router through the CLI. See Table 2-7 on page 2-17.
Step 3 Click Save to save changes to the database.
Step 4 In the confirmation dialog box, click Yes. The changes take effect immediately.
Note The maximum number of ONS 15302 and ONS 15305 NEs that can have PM data collection enabled is 10 for a small network, 30 for a medium network, and 50 for a large or high-end network.
10.3.6 Enabling or Disabling PM Data Collection by PM Category for CTC-Based NEs
Step 1 In the Domain Explorer window, choose Administration > Control Panel.
Step 2 In the Control Panel window, expand PM Service.
Step 3 Complete one of the following options:
•For the ONS 15310, ONS 15327, or ONS 15454 SONET, choose ONS 15310/ONS 15327/ONS 15454.
•For the ONS 15454 SDH, choose ONS 15454 SDH.
•For the ONS 15600 SONET, choose ONS 15600.
•For the ONS 15600 SDH, choose ONS 15600 SDH.
Step 4 Click the PM Collection Parameters tab, and enable or disable the various PM parameters. The following tables describe each parameter in detail:
•For the ONS 15310, ONS 15327, and ONS 15454 SONET, see Table 10-4.
•For the ONS 15454 SDH, see Table 10-5.
•For the ONS 15600 SONET, see Table 10-7.
•For the ONS 15600 SDH, see Table 10-8.
Step 5 After making your selections, click Save.
10.3.7 Enabling PM Data Collection for the ONS 15501, ONS 15530, and ONS 15540
Before viewing performance data for an ONS 15501, ONS 15530, or ONS 15540, enable performance monitoring on the NE in the Domain Explorer or by using the CLI or CiscoView.
Caution If robust PM data collection is enabled, do not set PM data storage to Optimized.
•To enable PM in the Domain Explorer, select an ONS 155xx NE in the Domain Explorer tree; then, set the PM data collection in the Network Element Properties pane to 15 Min, 1 Day, 15 Min Robust, or 1 Day Robust.
•To enable performance monitoring through CiscoView, start CiscoView and enable Optical Supervisory Channel (OSC) port monitoring, transparent port monitoring, and wave port monitoring. For information about CiscoView, see Appendix I, "Using CiscoView to Configure and Monitor ONS 15501, ONS 15530, and ONS 15540 NEs."
•To enable PM through the CLI, log into the NE and enter the monitor enable command. For more information, refer to the relevant hardware documentation.
10.3.8 Enabling or Disabling PM Data Collection by Module for the ONS 15800, ONS 15801, or ONS 15808
Performance monitoring can be enabled or disabled for the individual modules in the ONS 15800, ONS 15801, or ONS 15808 system.
Caution The PM Service must be active before enabling performance monitoring on the ONS 15800, ONS 15801, or ONS 15808 NE or module. If the PM Service is not active, there might be inconsistencies between data collected for the NE and data collected for the module. See
Activating or Deactivating Performance Monitoring for instructions on how to enable performance monitoring on an NE.
Step 1 In the Domain Explorer or Subnetwork Explorer tree, select an ONS 15800, ONS 15801, or ONS 15808 node and choose Configuration > NE Explorer.
Step 2 In the NE Explorer window, choose Performance > Enable/Disable PM by module. The PM Module table opens, showing the current PM data collection status of the selected ONS 1580x NE module. Table 10-13 describes the fields in the PM Module table.
Step 3 In the PM Module table, choose File > Set PM Collection Status (or click the Enable/Disable PM tool). The PM Collection Status dialog box opens.
Step 4 In the PM Collection Status dialog box, complete the following:
•To enable PM for a specific module, select the module name from the PM Disabled list and click Add.
•To disable PM data collection for a specific module, select the module name from the PM Enabled list and click Remove.
Step 5 Click OK.
If Autorefresh Data is enabled, the changes you made in the PM Collection Status dialog box appear automatically in the PM Module table. If autorefresh is disabled, click the Refresh Data tool in the PM Module table to see the changes.
Note If all modules in the PM Collection Status dialog box are disabled, PM data collection on the NE is also disabled. If at least one module in the PM Collection Status dialog box is enabled, PM data collection on the NE is enabled.
Table 10-13 Field Descriptions for the PM Module Table
Column Name
|
Description
|
NE ID
|
Name of the selected NE.
|
Module Name
|
Name of the selected module.
|
Physical Location
|
Physical location of the NE.
|
PM Collection Status
|
Current PM data collection status of the selected module.
|
10.3.9 Enabling or Disabling PM Retrieval Fail Alarms for CTC-Based NEs
Enabling the PM retrieval fail alarm allows CTM to monitor failed collection of PM data when PM collection is set to either 15 Min Robust or 1 Day Robust. It lets you set the number of times for CTM to collect PM data before declaring PM data retrieval failure.
Step 1 In the Domain Explorer window, choose Administration > Control Panel.
Step 2 Click PM Service. The PM Service pane opens.
Step 3 To enable 15-min PM retrieval fail alarms, click Enable in the PM 15-min Retrieval Fail Alarm area; then, specify the following:
•Seconds between Retries—Wait time between attempts to retrieve PM data. The Cisco default is 5 seconds.
•Number of Retries—Number of times to retrieve PM data. The Cisco default is 6 retries.
Step 4 To enable 1-day PM retrieval fail alarms, click Enable in the PM 1-day Retrieval Fail Alarm area; then, specify the following:
•Minutes between Retries—Wait time between attempts to retrieve PM data. The Cisco default is 15 seconds.
•Number of Retries—Number of times to retrieve PM data. The Cisco default is 6 retries.
Step 5 Click Save.
10.3.10 Specifying the PM Data Display
For CTC-based and ONS 155xx NEs, the display of PM data is affected by the PM Data Storage setting in the Control Panel. To specify whether to display PM data in normal or optimized mode for CTC-based and ONS 155xx NEs:
Step 1 In the Domain Explorer window, choose Administration > Control Panel.
Step 2 Click PM Service. The PM Service pane opens.
Step 3 Specify the PM data storage from the pull-down menu:
•Normal—All performance data is collected and displayed in the PM data tables.
•Optimized—Performance data with zero values and invalid flag data is not displayed and is not stored in the database.
Caution If robust PM data collection is enabled, do not set PM data storage to Optimized.
Step 4 Click Save.
10.3.11 Viewing the Robust PM Collection Queue
Step 1 In the Domain Explorer window, choose Administration > Control Panel.
Step 2 Click PM Service. The PM Service pane opens.
Step 3 In the Robust PM Collection Queue area are the following read-only fields:
•Number of 15-Minute Registers Outstanding—Number of performance data collections carried out every 15 minutes that are not yet scheduled for collection.
•Number of 1-Day Registers Outstanding—Number of performance data collections carried out every 24 hours that are not yet scheduled for collection.
Step 4 (Optional) Click Clear Robust PM Queue to clear the queue. Then, click Save.
10.3.12 Using the Self Monitor Table
When CTM comes close to or exceeds the limits of its performance, it might result in a reduction in the response time of the system. In this case, error messages are displayed to tell you to restore normal operation. The Self Monitor table allows you to monitor parameters that help in determining when CTM is close to the limit of its performance.
The Self Monitor table displays information about CTM threshold parameters. These parameters are collected and evaluated based on the NE model types. Self-monitoring can be used for CPU usage, memory usage, and disk usage. You can filter the Self Monitor table on the collection time, the model type, and the parameter name.
To view the Self Monitor table, choose Administration > Self Monitor in the Domain Explorer. Table 10-14 provides descriptions.
Table 10-14 Field Descriptions for the Self Monitor Table
Column Name
|
Description
|
NE ID
|
Name of the selected NE. If you open the Self Monitor table without selecting an NE, the NE ID is CTM.
|
Parameter Name
|
Name of the parameter. See the Alarm Configuration pane in the Control Panel for a list of monitored parameters.
|
Model Type
|
NE model type. When NE model types are not applicable, "System" is displayed as the model type.
|
Collection Time (time zone)
|
Time when CTM collected the parameter data.
|
Value
|
Total number of seconds to retrieve the information for the name of the parameter.
|
10.3.13 Filtering the Self Monitor Table
Step 1 In the Self Monitor table, choose File > Filter (or click the Filter Data tool). The Filter dialog box opens.
Step 2 Specify the filter parameters described in Table 10-15.
Step 3 After making your selections, click OK.
Table 10-15 Field Descriptions for the Self Monitor Table Filter Dialog Box
Tab
|
Description
|
Collection Time (time zone)
|
You can filter data for a specified time period, ranging from the past hour to the past 180 days. Additionally, you can click the User Specified radio button to specify an exact filter starting and ending time by month, day, year, and hour. The time zone can be GMT, a user-defined offset from GMT, or local time, depending on what is specified in the User Preferences dialog box. If you want to filter data and the time period is not important, click No Time Specified.
|
Model Type
|
You can move NE model types back and forth between the list of available model types and selected model types. The filter runs on the model types in the Selected Model Type list.
|
Parameter Name
|
You can move parameters back and forth between the list of available parameter names and selected parameter names. The filter runs on the parameters in the Selected Parameter Names list.
|
10.4 How Do I Query, View, Filter, and Graph PM Data?
This section describes the tools you use to query, view, filter, and graph the data displayed in PM tables.
10.4.1 Using the PM Table Query
The PM table query opens when you select an NE, group, or domain node in the Domain Explorer and choose Performance > PM Query by Category or PM Query by NE Model.
•Use the PM Query by Category wizard to filter PM data based on the PM category.
•Use the PM Query by NE Model wizard to filter PM data by NE model.
10.4.1.1 PM Query by Category Wizard
Use the PM Query by Category wizard to view PM data by PM category.
Note The PM Query by Category wizard is not supported for the ONS 155xx, Cisco CRS-1, Cisco XR 12000, or Cisco MGX.
Step 1 In the Domain Explorer tree, select the management domain, group, or NE node for which to view historical performance data and choose Performance > PM Query by PM Category. Table 10-16 describes the fields in the PM Query by Category wizard. Fields shown depend on the PM category selected.
Step 2 In the Category area, select the category and type from the drop-down lists.
Step 3 Select the PM data collection interval (15 Minute, 1 Day, or Real-Time).
Note The Real-Time option is disabled if you select a management domain or group node. The Real-Time option is enabled only if you select a single NE in the Domain Explorer tree.
Step 4 (Optional) Click Next.
Note Depending on the NE type selected, some of the following screens might not appear. If a screen does not appear, skip the step and move on to the next one.
Step 5 In the Near End/Far End Selection screen, select whether to filter for near-end or far-end PM data; then, click Next.
Step 6 In the Module Category screen, select the module category from the list; then, click Next.
Step 7 In the Physical Location screen, depending on the NE type, select the rack, subrack, slot, subslot, and port from the list; then, click Next.
Step 8 In the Module Type Selection screen, add or remove module types from the lists; then, click Next.
Step 9 Click Finish. The PM table opens. See Appendix F, "Performance Data" for field descriptions for each PM table.
Table 10-16 Field Descriptions for the PM Query by Category Wizard
Field
|
Description
|
Category Selection Screen
|
Category
|
Select a PM category from the list. Available categories vary by selected NE.
|
Type
|
Select a PM query type for the NE. PM types vary by selected category.
|
15 Minute
|
Filters for PM data received in the last 15 minutes. 15-minute PM data can be queried for a range of time from the past hour to the past 30 days.
|
1 Day
|
Filters for PM data received in the last day. 1-day PM data can be queried for a range of time from the past 7 days to the past 180 days.
|
Real-Time (CTC-based NEs)
|
Launches a real-time PM report, which allows you to examine the current value of a PM parameter in granularities finer than the standard 15-minute or 1-day interval. You can view and modify the polling interval for the real-time PM reporting session. You can end a real-time PM session at any time and export the data.
Note You can also launch a real-time PM session from a selected row in a PM table. This is useful if you want to query on a single physical location (for example, Slot 1, Port 1).
|
User Specified
|
Specify an exact filter starting and ending time by month, day, year, and hour.
|
Near End/Far End Selection Screen
|
Near End
|
Filters for near-end PM data.
|
Far End
|
Filters for far-end PM data.
|
Module Category Screen
|
Module Category
|
Select a module category from the list. Available categories vary by selected NE. This screen appears only if you select Ethernet as both the category and type in the Category Selection screen.
|
Physical Location Screen
|
Physical Location
|
Filters PM data by slot, subslot, or port. Use the lists to select the slot, subslot, or port for which you want to display PM data. For the ONS 1580x, PM data is filtered by rack, subrack, and slot.
|
Module Type Selection Screen
|
Available Modules
|
List of modules available for the selected PM filtering. Select a module and click Add to move it to the Selected Modules field.
|
Selected Modules
|
List of modules that are selected for the specified PM filtering. Select a module and click Remove to remove it from filtering consideration.
|
Table 10-17 shows which PM tables are available for each category.
Table 10-17 PM Tables by Category
Category
|
PM Tables
|
SONET
|
SONET Section PM table
|
SONET Line PM table
|
SONET STS Path PM table
|
SONET VT1.5 Path PM table
|
SONET VT2 Path PM table
|
SDH
|
SDH Regenerator Section PM table
|
SDH Multiplex Section PM table
|
SDH Higher Order Virtual Container PM table
|
SDH Lower Order VC3 PM table
|
SDH Lower Order VC12 PM table
|
SDH Lower Order VC11 PM table
|
SDH CoS PM table
|
SDH SAN PM table
|
DSn
|
DS1 PM table
|
DS3 PM table
|
DS3I PM table
|
DWDM
|
B1 Counters PM table
|
FEC Counters PM table
|
B1 and FEC Counters PM table
|
Ethernet Parameters PM table
|
Edge SDH
|
Edge SDH Regeneration Section PM table
|
Edge SDH Multiplex Section PM table
|
Edge SDH Higher Order VC4 PM table
|
Edge SDH Lower Order PM table
|
Edge Statistics
|
Edge Statistics DCC PM table
|
Edge Statistics LAN PM table
|
Edge Statistics WAN PM table
|
En
|
E1 PM table
|
E3 PM table
|
E4 PM table
|
Ethernet
|
Ethernet PM table
|
Ethernet POS PM table
|
Ethernet CoS PM table
|
Ethernet GFP PM table
|
OTN
|
OTN Section PM table
|
OTN Path PM table
|
OTN FEC PM table
|
Optical
|
Optical Physical PM table
|
SAN
|
SAN PM table
|
8B10B
|
8B10B PM table
|
10.4.1.2 PM Query by NE Model Wizard
Use the PM Query by NE Model wizard to view PM data by NE model.
Step 1 Make sure that performance monitoring is enabled on the NE. See Activating or Deactivating Performance Monitoring.
Step 2 In the Domain Explorer tree, select the management domain, group, or NE node for which to view historical performance data and choose Performance > PM Query by NE Model. Table 10-18 describes the fields in the PM Query by NE Model wizard. Fields depend on the type of NE and PM selected.
Step 3 In the NE Model area, select the NE model and NE type from the drop-down lists.
Step 4 Select the PM data collection interval (15 Minute, 1 Day, or Real-Time).
Note The Real-Time option is disabled if you select a management domain or group node. The Real-Time option is enabled only if you select a single NE in the Domain Explorer tree.
Step 5 (Optional) Click Next.
Note Depending on the NE type selected, some of the following screens might not appear. If a screen does not appear, skip the step and move on to the next one.
Step 6 In the Near End/Far End Selection screen, select whether to filter for near-end or far-end PM data; then, click Next.
Step 7 In the Module Category screen, select the module category from the list; then, click Next.
Step 8 In the Physical Location screen, depending on the NE type, select the rack, subrack, slot, subslot, and port from the list; then, click Next.
Step 9 In the Module Type Selection screen, add or remove module types from the lists; then, click Next.
Step 10 Click Finish. The PM table opens. See Appendix F, "Performance Data" for field descriptions for each PM table.
Table 10-18 Field Descriptions for the PM Query by NE Model Wizard
Field
|
Description
|
NE Model Selection Screen
|
NE Model
|
Select an NE model from the list.
|
Type
|
Select a PM query type for the NE. The PM types vary by selected NE model.
|
15 Minute
|
Filters for PM data received in the last 15 minutes. 15-minute PM data can be queried for a range of time from the past hour to the past 30 days.
|
1 Day
|
Filters for PM data received in the last day. 1-day PM data can be queried for a range of time from the past 7 days to the past 180 days.
|
Real-Time (CTC-based, CRS-1, and XR 12000 NEs only)
|
Launches a real-time PM report, which allows you to examine the current value of a PM parameter in granularities finer than the standard 15-minute or 1-day interval. You can view and modify the polling interval for the real-time PM reporting session. You can end a real-time PM session at any time and export the data.
Note You can also launch a real-time PM session from a selected row in a PM table. This is useful if you want to query on a single physical location (for example, Slot 1, Port 1).
|
User Specified
|
Specify an exact filter starting and ending time by month, day, year, and hour.
|
Near End/Far End Selection Screen
|
Near End
|
Filters for near-end PM data.
|
Far End
|
Filters for far-end PM data.
|
Module Category Screen
|
Module Category
(CTC-based and ONS 1580x NEs only)
|
Select a module category from this list. Available categories vary by selected NE. This screen appears only if you select amplifiers, transponders, or demux from the Type field for the ONS 1580x, or if you select Ethernet for CTC-based NEs.
|
Physical Location Screen
|
Slot
|
Filters PM data by slot.
|
Port
|
Filters PM data by port.
|
Rack (ONS 1580x only)
|
Filters PM data by rack.
|
Subrack (ONS 1580x only)
|
Filters PM data by subrack.
|
Subslot (ONS 15530 and ONS 15540 only)
|
Filters PM data by subslot.
|
Module Type Selection Screen
|
Available Modules
|
List of modules available for the selected PM filtering. Select a module and click Add to move it to the Selected Module field.
|
Selected Modules
|
List of modules that are selected for the specified PM filtering. Select a module and click Remove to remove it from filtering consideration.
|
GSR-IOX Real-Time PM Attribute Selection Screen
|
Interface Name (also Card, Physical Location, and so on)
|
Select the type of entity to monitor from this list. The label changes depending on the type of PM selected.
|
Available PM Attributes
|
List of real-time attributes available for the selected PM filtering. Select an attribute and click Add to move it to the Selected PM Attributes field.
|
Selected PM Attributes
|
List of real-time attributes that are selected for the specified PM filtering. Select an attribute and click Remove to remove it from filtering consideration.
|
Table 10-19 shows which PM tables are available for each NE.
Table 10-19 PM Tables by NE Type
NE
|
Available PM Tables
|
CRS-1
|
Interface GC PM table
|
Interface DR PM table
|
BGP Peer PM table
|
Node CPU PM table
|
Node Memory PM table
|
Node Process PM table
|
MPLS Interface PM table
|
MPLS LDP PM table
|
OSPF V2 PM table
|
Cisco Catalyst 6509
|
—
|
Cisco MDS 9000
|
—
|
ONS 15216
|
—
|
ONS 15302
|
—
Note See Table 10-17, "PM Tables by Category."
|
ONS 15305
|
—
Note See Table 10-17, "PM Tables by Category."
|
ONS 15310
|
Physical PM table
|
SONET Section PM table
|
SONET Line PM table
|
SONET STS Path PM table
|
SONET VT1.5 Path PM table
|
DS3 PM table
|
DS1 PM table
|
POS PM table
|
Ethernet PM table
|
GFP PM table
|
ONS 15327
|
SONET Section PM table
|
SONET Line PM table
|
SONET STS Path PM table
|
SONET VT Path PM table
|
DS3 PM table
|
DS1 PM table
|
Ethernet PM table
|
ONS 15454 SONET
|
Physical PM table
|
SONET Section PM table
|
SONET Line PM table
|
SONET STS Path PM table
|
SONET VT1.5 Path PM table
|
SONET VT2 PM table
|
DS3 PM table
|
DS1 PM table
|
Ethernet PM table
|
E1 PM table
|
POS PM table
|
CoS PM table
|
OTN G.709 Section PM table
|
OTN G.709 Path PM table
|
OTN FEC PM table
|
SAN PM table
|
8B10B PM table
|
GFP PM table
|
ONS 15454 SDH
|
Physical PM table
|
Regenerator Section PM table
|
Multiplex Section PM table
|
Higher Order Virtual Container PM table
|
Lower Order VC3 PM table
|
Lower Order VC11 PM table
|
Lower Order VC12 PM table
|
E4 PM table
|
E3 PM table
|
E1 PM table
|
DS1 PM table
|
DS3 PM table
|
Ethernet PM table
|
POS PM table
|
CoS PM table
|
OTN G.709 Section PM table
|
OTN G.709 Path PM table
|
OTN FEC PM table
|
SAN PM table
|
8B10B PM table
|
GFP PM table
|
ONS 15501
|
Physical PM table
|
ONS 15530
|
SONET Section PM table
|
Line PM table
|
CDL PM table
|
Physical PM table
|
FC Port Errors PM table
|
Ether History PM table
|
ONS 15540 ESP, ESPx
|
SONET Section PM table
|
Line PM table
|
CDL PM table
|
Physical PM table
|
ONS 15600 SONET
|
Physical PM table
|
SONET Section PM table
|
SONET Line PM table
|
SONET STS Path PM table
|
Ethernet PM table
|
POS PM table
|
GFP PM table
|
ONS 15600 SDH
|
Physical PM table
|
Regenerator Section PM table
|
Multiplex Section PM table
|
High Order Virtual Container PM table
|
ONS 15800, ONS 15801
|
Amplifiers PM table
|
Transponders PM table
|
Demux PM table
|
Control and Monitoring Processor PM table
|
Input/Output Card PM table
|
Line Service Module PM table
|
Optical Add/Drop Multiplexer PM table
|
Subrack Common Function PM table
|
Optical Switching Unit PM table
|
ONS 15808
|
Amplifiers Long Haul PM table
|
Amplifiers Extended Long Haul PM table
|
Transponders PM table
|
Mux/Demux/Channel Processor PM table
|
Control and Monitoring Processor PM table
|
Band Combiner and Splitter ELH PM table
|
Optical Add/Drop Multiplexer PM table
|
Alarm Interface Unit PM table
|
Optical Service Channel Modem PM table
|
Shelf Control Unit PM table
|
Optical Channel Protection Unit PM table
|
XR 12000
|
Interface GC PM table
|
Interface DR PM table
|
BGP Peer PM table
|
Node CPU PM table
|
Node Memory PM table
|
Node Process PM table
|
MPLS Interface PM table
|
MPLS LDP PM table
|
OSPF V2 PM table
|
10.4.2 Launching the PM Table for Layer 3 Links from the Network Map
Step 1 In the Domain Explorer or Subnetwork Explorer tree, click a node and choose File > Network Map (or click the Open Network Map tool).
Step 2 Right-click a Layer 3 link in the Network Map and choose Link PM Data from the right-click menu.
10.4.3 Using the Statistics Report for Voice-Enabled Products
To launch the Statistics Report, you can:
•Choose Performance > MGX Voice Gateway > Statistics Report in the Domain Explorer window
•Click the Statistics Report icon in the Diagnostic Center, Chassis View, or Configuration Center
•Choose Tools > Statistics Report in the Diagnostic Center, Chassis View, or Configuration Center
•Right-click an NE and choose Tools > Statistics Report in the Diagnostic Center, Chassis View, or Configuration Center
The Statistics Report window has two panes:
•Report Parameters—Displays the name for each statistic along with the time period parameters in GMT, a user-defined offset from GMT, or local time, depending on what is specified in the User Preferences dialog box.
Note CTM automatically updates the time display for daylight saving time.
•Report Data—Displays the parameters for the report data.
You can use the Statistics Report to view reports of statistics data that are collected from the switch.
Note RPM cards are not supported for the Statistics Report.
Table 10-20 lists the report types that are supported for each NE from the hierarchy pane.
Table 10-20 Report Types for Each Voice-Enabled NE
NE
|
Report Types
|
Network
|
Supports the following report types:
•Raw Data Report for cards, lines, ports, physical lines, protocol, and PNNI, in the network.
•Performance Data Report for ports in the network.
•Utilization Data Report for ports in the network.
|
Node
|
Supports the following report types:
•Raw Data Report for cards, lines, ports, physical lines, protocol, and PNNI, on the node.
•Performance Data Report for ports on the node.
•Utilization Data Report for ports on the node.
|
Card
|
Supports the following report types:
•Raw Data Report for all ports, protocol, and physical lines on the card.
|
Port
|
Supports the following report types:
•Raw Data Report for ports and connections on the selected port.
•Performance Data Report for connections on the selected port.
•Utilization Data Report for connections on the selected port.
|
Line
|
Supports the following report types:
•Raw Data Report for the line. If applicable, additional statistics are shown for physical lines.
|
Paths
|
Supports the Raw Data Report for paths.
|
10.4.4 Managing Real-Time PM Data
CTM supports the ability to launch a real-time PM report from the PM Query wizard or from a single row in a PM table. This feature allows you to examine the current value of a PM parameter in granularities finer than the standard 15-minute or 1-day interval. You can view and modify the polling interval for the real-time PM reporting session.
Note Real-time PM reporting applies only to CTC-based, CRS-1, and XR 12000 NEs.
The following real-time PM selection options are available:
•Polling—When selected, CTM periodically polls the selected PM parameter(s) on the selected NE. The polling intervals are:
–10 to 900 seconds—For CTC-based NEs
–60 to 900 seconds—For CRS-1 and XR 12000 NEs
Note You can specify the real-time polling interval in the Real-Time Polling dialog box. See Changing the Real-Time Polling Interval.
•Refresh—Allows you to start polling of real-time attributes if real-time polling is disabled in the Real-Time Polling dialog box.
•Baseline—When selected, the most recently collected data set is saved into a buffer. All new values are recalculated as they arrive based on the saved baseline values.
Note Not all values can be saved as a baseline. For example, null and string values cannot be saved as baseline values.
•Clear Baseline—Sets the baseline values to zero.
•Clear—Clears the current real-time PM buffer of all values.
Each 15-minute or 1-day PM table has a corresponding real-time PM table. However, not all of the fields in the historical PM tables are shown in the real-time PM tables. The first fields in real-time PM tables are:
•NE ID—Name of the selected NE.
•Module Name—Module for which PM data is displayed.
•Physical Location—Slot and port number for which PM data is displayed.
•Interface—Interface name of the selected NE.
•Time Stamp—Time when the performance statistics were collected.
•Validity—Whether or not the entry is valid. If the value is True, all PM data shown in the selected row is valid. If the value is False, some of the PM data shown in the row is invalid.
The remaining fields are the actual real-time attributes being polled.
When a real-time PM session is running, it polls the NE for x number of attributes every 10 to 900 seconds. The data it returns is stored entirely in transient memory. You can use the PM Service properties pane in the Control Panel window to limit the scope of the real-time PM session. See Understanding the PM Service Pane.
•To launch a real-time PM report from the PM Query wizard, see PM Query by Category Wizard or PM Query by NE Model Wizard. In the NE Model Selection screen, click the Real-Time radio button.
•To launch a real-time PM report from a single row in a PM table, select a row and choose View > Launch Real-Time Performance Session.
Note Use the toolbar icons to manage the real-time display. See Appendix A, "Icons and Menus Displayed in CTM" for an explanation of the icons.
10.4.4.1 Changing the Real-Time Polling Interval
By default, the real-time PM session polls the attributes every 10 seconds for CTC-based NEs and every 60 seconds for CRS-1 and XR 12000 NEs. You can configure the polling interval from 10 to 900 seconds. (For the CRS-1 and XR 12000, the polling interval is 60 to 900 seconds.)
Step 1 Launch a real-time PM table.
Step 2 Choose View > Specify Real-Time Polling Interval (or click the Specify the Real-Time Polling Interval tool). The Real-Time Polling dialog box opens.
Step 3 In the Specify Real-Time Polling Interval text box, enter a number from 10 to 900 seconds. (For the CRS-1 or XR 12000, enter a number from 60 to 900 seconds.)
Step 4 Complete one of the following options:
•To save the change, click Apply.
•To save the most recently collected data set into a buffer, click Baseline. All new values are recalculated as they arrive based on the saved baseline values.
Tip To set the baseline values to zero, click Clear Baseline. This disables the baseline set.
•To discard changes and close the dialog box, click Cancel.
10.4.4.2 Enabling or Disabling Real-Time Polling
Step 1 Launch a real-time PM table.
Step 2 Choose View > Specify Real-Time Polling Interval (or click the Specify the Real-Time Polling Interval tool).
Step 3 To disable real-time polling, uncheck the Enable Real-Time Auto Polling check box. To enable real-time polling, leave this check box checked. When automatic polling is enabled, you do not need to manually refresh the real-time PM table.
Step 4 Click Apply.
10.4.4.3 Understanding the "No Data Available" Value for CRS-1 and XR 12000 NEs
For CRS-1 and XR 12000 NEs, the first real-time performance data sample always shows "No data available." It takes at least one sample interval before the NE makes a data sample available for viewing. Periodically, one of the samples also shows "No data available." With the recommended settings, this value is returned once per hour, or more frequently depending on the CLI settings applied to the NE. For example, while monitoring the generic counters, the following CLI commands are required on the NE:
performance-mgmt statistics interface generic-counters template
RealTimePM_InterfaceGC_template sample-size 60
This setting results in one sample per hour showing as "No data available." If the sample size is set to a lower number, the "No data available" value appears more frequently. If the sample size is set to 15, the "No data available" value appears every 15 minutes. This behavior is caused by the NE periodically terminating the monitoring sessions. CTM re-establishes the monitoring sessions automatically, but one sample is lost each time. For time periods of one hour or longer, it is recommended that you use historical rather than real-time PM data sessions.
Two additional scenarios can cause "No data available" to appear:
1. When a monitoring session is established by a user (for example, at 01:00 a.m.), and a second user views the data starting at 01:30 a.m., the second user will observe "No data available" at 02:00 a.m., and not at 02:30 a.m. as expected.
2. When two users monitor the same data simultaneously, and one user closes the monitoring window, the second user will lose one sample when the session is closed.
10.4.5 Filtering PM Data
Use the Filter dialog box to filter data according to criteria that you select, and then display the results in a table. Table 10-21 describes the fields in the filter.
Note The Filter dialog box is not available for real-time PM data.
Table 10-21 Field Descriptions for the PM Table Filter
Tab
|
Description
|
Time Stamp (also Time Period)
|
Filters PM data for a specified time period, ranging from the past hour to the past 6 months. Additionally, you can click the User Specified radio button to specify an exact filter starting and ending time by month, day, year, and hour. The time zone used can be GMT, an offset from GMT, or local time, depending on what you specified in the User Preferences dialog box. If you want to filter events and the time period is not important, click No Time Specified.
|
NE ID (also Network Elements)
|
Filters PM data by NE. PM data will display for NEs in the Selected list. Use the Add and Remove buttons to select the NEs for which you want to display PM data.
|
Module Name (also Managed Entities; not available for all NEs)
|
Filters PM data by module. PM data will display for modules in the Selected list. Use the Add and Remove buttons to select the modules for which you want to display PM data.
|
Physical Location
|
Filters PM data by rack, subrack, slot, subslot, card, or port. (Options depend on the type of NE selected.) Use the lists to select the entity for which you want to display PM data.
|
Other (CRS-1 and XR 12000 only)
|
Filters PM data by criteria specific to the type of PM data being collected. Depending on the type of PM data, values include:
•Interface name
•IP address
•Process ID
You can check the Disregard All Other Filter Criteria check box to base the filter on only the selected type of PM data.
|
10.4.6 Generating an HTML Report for PM Tables—CRS-1 and XR 12000
Use the HTML Report dialog box to generate an HTML report based on the data in the selected CRS-1 or XR 12000 PM table. You can generate a report for selected rows or for all rows on the current page. A maximum of 1,000 rows per page can be exported. You can select the individual column(s) that you want to display in the report by checking the corresponding check box(es); the list of columns varies dynamically based on the selected PM table.
After making your selection, click OK; the browser window appears with the HTML report. The report is saved automatically on the client system. (The default directory is C:\Cisco\TransportManagerClient<version_number>\reports or /opt/CiscoTransportManagerClient<version_number>/reports.) Use your browser's Print option to print the report.
10.4.7 Using PM Data Graphs
PM tables contain a Plot tab that allows you to plot historical or real-time PM data in a graphical view that is stored in the CTM database. You can plot a maximum of three PM parameters at a time per graph. You can select a line or bar graph type and you can display multiple traces on the same set of axes for comparison. CTM automatically scales the graph's Y-axis to best show the values of the measured parameters. You can launch a graph of PM data for the following data types:
•One PM parameter on one board
•Multiple PM parameters on one board
Note Parameters must have similarly scaled ranges, such as errored seconds and severely errored seconds. For example, you cannot plot bit errored rate and errored seconds on the same graph. Instead, these parameters are plotted on separate graphs.
•One PM parameter on multiple boards
Note Boards must all support the selected PM parameter.
Step 1 View PM data either by NE model (see PM Query by NE Model Wizard) or by PM category (see PM Query by Category Wizard).
Step 2 From the PM table, select the row of the NE, port, or slot for which you want to view the PM data on a graph.
Step 3 Choose View > Plot (or click the Plot tool).
Note To plot the graph, you must choose View > Plot or click the Plot tool. If you simply click the Plot tab (without choosing View > Plot or clicking the Plot tool), the graph is not filled out.
In the Plot tab, the graph is displayed. The graph can plot a maximum of three PM parameters. The graph's status bar displays the selection context in the following format:
<NE ID>:<Module>:<Physical Location>:<Slot>:<Port>:<Interface>:<Time Stamp [Time Zone]>
Step 4 Use the plot-specific toolbar buttons to manage the graphical display. Choose View > Zoom In, Zoom Out, or Fit in Window to adjust the zoom level. You can also click the Zoom In, Zoom Out, or Fit in Window tools.
10.4.7.1 Configuring a Graph
To modify the parameters that are plotted in a graph:
Step 1 From the PM table, select the row for which you want to view the PM data on a graph.
Step 2 Choose View > Graph Configure (or click the Configure Graphing Parameters tool). The Graph Parameters Selection dialog box opens.
Step 3 For historical PM graphs, select the start and end times in the Time Panel area. Select the month, day, year, hour, and minute from the corresponding pull-down menus.
Note Real-time PM graphs do not have a Time Panel area, because a time range does not apply to real-time data.
Step 4 In the Parameter Selection area, select the parameters from the Available Parameters list that you want to plot in the graph. You can generate a maximum of three graphs and each graph can plot a maximum of three parameters.
Step 5 Click the Add button that corresponds to the graph where the parameter will be plotted. Selected parameters are listed in the Selected Parameters: Graph <number> list.
Step 6 To remove parameters from the Selected Parameters: Graph <number> list, select the parameter and click Remove.
Step 7 Click OK. The graph is displayed in the Plot tab. The status bar displays the module name, physical location, interface, date range, and time stamp range.
Step 8 You can adjust the zoom level for each graph. Click a graph and choose View > Zoom In, Zoom Out, or Fit in Window. You can also click the Zoom In, Zoom Out, or Fit in Window tools.
Step 9 You can normalize or restore the Y axes values in historical PM graphs. Choose View > Normalize Y Axes or Restore Y Axes (or click the Normalize Y Axes or Restore Y Axes tools). The Normalize option allows you to normalize axes values and compare data of the same type (for example, receive versus transmit packets). The Restore option restores axes values to the previous graph visualization.
Note The Normalize and Restore options do not apply to real-time PM graphs.
10.4.7.2 Printing a Graph
Step 1 After viewing PM data on a graph or configuring a graph, choose File > Print Graph (or click the Print Graph tool). The Print dialog box opens.
Step 2 Select your printer and configure the Page Setup options, as necessary.
Step 3 Click OK.
Note PM graphs might not print completely on some printers with the default Page Setup settings. In this case, you need to change the printer setup. To do this, click Printer in the Print dialog box. Click Properties. Click Advanced. Change the scaling to a value that prints the complete graph; for example, 10% or 20%. Click OK.
10.4.8 Understanding How CTM Displays the Interface Field
CTM displays the Interface field in PM tables as follows:
•CRS-1 or XR 12000
CTM representation:
<Interface_type><rack_number>/<slot_number>/<CPU_instance_running_IOX_or_SPA_number><port_number>
For example, GigabitEthernet0/1/0/0 represents Gigabit Ethernet port 0 in slot 1 of rack 0 for CPU 0 on a complete line card. In case of shared port adaptors (SPAs), the third field represents the SPA number.
•ONS 15302 and ONS 15305
CTM representation:
<Interface_type>#<Interface_type_number>AUG4-<AUG4_number>/AUG1-<AUG1_number>/TUG3-<TUG3_number>/TUG2-<TUG2_number>/TU12-<TU12_number>
where:
–<Interface_type> is the affected interface object
–<Interface_type_number> is the interface number
–<AUG4_number> is the AUG4 number (applies to VC-4, VC3, and VC12)
–<AUG1_number> is the AUG1 number (applies to VC-4, VC3, and VC12)
–<TUG3_number> is the TUG3 number (applies only to VC3 and VC12 interfaces)
–<TUG2_number> is the TUG2 number (applies only to VC12 interfaces)
–<TU12_number> is the TU2 number (applies only to VC12 interfaces)
•SDH
CTM representation:
<Interface_type>#<VC4_number>/VC3-<VC3_number>/TUG2-<TUG2_number>/VC12-<VC12_number>
where:
–<Interface_type> is the affected interface object (for example, VC4, VC4-2c, VC3, VC12, and so on)
–<VC4_number> is the VC4 number in that interface (applies only to VC4, VC3, and VC12 interfaces)
–<VC3_number> is the VC3 number in that VC4 (applies only to VC3 interfaces)
–<TUG2_number> is the TUG2 number in that VC3 (applies only to VC12 interfaces)
–<VC12_number> is the VC12 number in that TUG2 (applies only to VC12 interfaces)
For example, for alarms on a VC12 interface with VC4_number=1, VC3_number=2, TUG2_number=1, and VC12_number=2, CTM displays VC12 #1/VC3-2/TUG2-1/VC12-2, where the first field is the affected interface and VC4 number (#<VC4_number>). The example indicates that the alarm is on the VC12 interface with the VC4 number equal to 1 (VC12 #1).
•SONET
CTM representation:
<Interface_type>#<STS_number>/<VT_group_number>-<VT_number_in_group>
where:
–<Interface_type> is the affected interface object (for example, STS1, STS3c, VT-1, and so on)
–<STS_number> is the STS number on that interface (applies only to STS and VT interfaces)
–<VT_group_number> is the VT group number for that STS number (applies only to VT interfaces)
–<VT_number_in_group> is the VT number in that VT group (applies only to VT interfaces)
For example:
–For a VT path-level alarm with STS_number=1, VT_group_number=2, and VT_number_in_group=1, CTM displays VT-1 #1/2-1, where the first field is the affected interface and STS number (#<STS_number>). The example indicates that the alarm is a VT path-level alarm with STS_number=1 (VT-1 #1).
–For an STS path-level alarm with STS_number=1, CTM displays STS3c #1, where the first field is the affected interface and STS number (#<STS_number>). The example indicates that the alarm is an STS path-level alarm with STS_number=1 (STS3c #1).
Note The ONS 1580x does not support an Interface field. The PM table shows the physical location of the card.
10.5 What Types of Data Reports Are Available for MGX Voice Gateway Devices?
When performance data has been collected, the next step is to generate reports to present the data in the most useful form; for example, as a summary for an at-a-glance indication of the health of the network, or as an in-depth detailed report for analysis.
An at-a-glance report can provide quick information on any fault or failure on the network.
A more detailed report can be generated to help you understand traffic flows and how traffic changes over time.
This section includes the following information that is specific to MGX devices:
•Viewing Raw Data Reports
•Viewing Utilization Data
•Viewing Performance Data Reports
•Exporting the Data Report
10.5.1 Viewing Raw Data Reports
The Raw Data Report Parameters pane in the Statistics Report displays the history statistics data for the selected statistics and the time period parameters.
These tasks are used to configure the Raw Data Reports:
•Generating a Raw Data Report
•Exporting the Raw Data Report
•Generating a Raw Data Report for Connection Endpoints
For more information on the supported objects for each report type, see Table 10-20.
10.5.1.1 Generating a Raw Data Report
Multiple Raw Data Reports can be generated at the same time.
Step 1 In the Statistics Report, move the node from the hierarchy pane to the right-hand pane.
Step 2 Choose Raw Data Report from the drop-down list. See Figure 10-1.
Step 3 Choose the Raw Data Report types from the drop-down list.
Step 4 Choose the Report Parameter type from the drop-down list.
Step 5 Check the check box to activate the selected statistics for the chosen report parameter. To activate all the statistics, check the Select check box.
Note If you choose a different report parameter type and did not uncheck the statistics from the previous report parameter, the previous checked statistics are also reported. You must uncheck all the statistics before you choose a different report parameter.
Step 6 From the Time Period Parameters area:
a. Choose one of the following time period schedules:
–TOD (Time of Day). This value is specified by the user.
–Prev Hour
–Prev Day
–Prev Week
b. Enter the start date in dd/mm/yyyy in the Start Date field.
c. Enter the start time in h:mm in the Start Time field.
d. Enter the end date in dd/mm/yyyy in the End Date field.
e. Enter the end time in h:mm in the End Time field.
Step 7 Click Generate Report to generate the Raw Data Report with the given parameters.
After receiving all the data, you can verify from the status bar that the report has been generated completely. If no data is available, the status bar reports that the Raw Data Report has no data to report.
Note To stop generating the Raw Data Report, click Stop Report Generation.
Figure 10-1 Statistics Report Window—Raw Data Report
10.5.1.2 Exporting the Raw Data Report
After generating the Raw Data Report, you can verify that the report has been exported. To export the Raw Data Report at the node level, see Exporting the Data Report.
10.5.1.3 Generating a Raw Data Report for Connection Endpoints
You can select a port in the Statistics Report and retrieve all the connections for the port. All the connection data reports are retrieved for the Raw Data Report, Utilization Data Report, and Performance Data Report at the same time.
Step 1 In the Domain Explorer, choose Configuration > MGX Voice Gateway > Configuration Center to open the Configuration Center.
Step 2 Click the Connections tab.
Step 3 Drag the node from the hierarchy to the right-hand pane to display the Connection Browser window.
Step 4 Click the Connection List tab and enter the number of connections you want to retrieve in the Connection Count to be retrieved field. To retrieve all the connections, enter an asterisk (*).
Step 5 Click Get to retrieve the connections. For example, you can retrieve connections for both local and remote endpoints for the node.
The Connection Browser window appears with the number of connections matching the filtering criteria. A list of connections that have either local or remote endpoints is displayed in the connection list.
Step 6 Right-click the connection type from the list of connections and choose Statistics Report.
Step 7 Choose Raw Data Report from the drop-down list.
Step 8 Choose Raw Data Report for Conn from the drop-down list.
Step 9 Choose the Report Parameter Connection type from the drop-down list.
Step 10 Check the check box to activate the selected statistics. To activate all the statistics, check the Select check box.
Note If you choose a different report parameter type and did not uncheck the statistics from the previous report parameter, the previous checked statistics are also reported. You must uncheck all the statistics before you choose a different report parameter.
Step 11 From the Time Period Parameters area:
a. Choose one of the following time period schedules:
–TOD (Time of Day). This value is specified by the user.
–Prev Hour
–Prev Day
–Prev Week
b. Enter the start date in dd/mm/yyyy in the Start Date field.
c. Enter the start time in h:mm in the Start Time field.
d. Enter the end date in dd/mm/yyyy in the End Date field.
e. Enter the end time in h:mm in the End Time field.
Step 12 Click Generate Report to generate connection end point reports with the given parameters.
After receiving all the data, you can verify that the connection endpoint list for the selected port is displayed.
If no data is available, the status bar reports that the Raw Data Report has no data to report.
Note To stop generating the Raw Data Report, click Stop Report Generation.
10.5.2 Viewing Utilization Data
The Utilization Data Report verifies all ports and connections. Utilization is based on percentage of total bits received in seconds and total bits transmitted in seconds. You specify the parameters listed that crosses the threshold value.
These tasks are used to configure Utilization Data Reports:
•Calculating the Percent Utilization for Top Utilization Reports
•Generating a Utilization Data Report
•Exporting the Utilization Data Report
•Generating a Utilization Data Report for Connection Endpoints
For more information on the supported objects for each report type, see Table 10-20.
10.5.2.1 Calculating the Percent Utilization for Top Utilization Reports
For percent utilization, the data is aggregated over a time period specified in the report.
Table 10-22 lists the calculations for the ports and connections.
Table 10-22 Percent Utilization Calculations for Top Utilization Reports
Type
|
Calculation
|
Ports
|
—
|
Percent bytes received from the network (number of packets or cells) received per second or port speed * 100
|
Percent bytes transmitted to the network (number of packets or cells) transmitted per second or port speed * 100
|
Percent utilization of the port = percent bytes received from the network + percent bytes transmitted to the network
|
Table 10-23 lists the method conversion that are used to convert data to bits per second (bps).
Table 10-23 Method Conversions for Endpoints
Endpoint
|
Method Conversion
|
ATM
|
Convert cells received to bits per second by using the conversion formula; for example, each cell has a 48 B payload:
bps = (number cells received / (bucket interval * 60)) * 48 * 8
|
Voice and Data
|
Convert packets to bits per second (each packet has 24 bytes):
bps = ((number packets received / (bucket interval * 60)) * 24 * 8
|
10.5.2.2 Generating a Utilization Data Report
Multiple Utilization Data Reports can be generated at the same time.
Step 1 In the Statistics Report, move the node from the hierarchy pane to the right-hand pane.
Step 2 Choose Utilization Data Report from the drop-down list. See Figure 10-2.
Step 3 Choose Utilization Report for Port from the drop-down list.
Step 4 Enter the threshold percentage in the Utilization Threshold Percentage field.
Note The threshold is the minimum utilization percentage after which you want to report; for example, a 90% threshold report details data of > 90%.
Step 5 From the Time Period Parameters area:
a. Choose one of the following time period schedules:
–TOD—(Time of Day) This value is specified by the user.
–Prev Hour
–Prev Day
–Prev Week
b. Enter the start date in dd/mm/yyyy in the Start Date field.
c. Enter the start time in h:mm in the Start Time field.
d. Enter the end date in dd/mm/yyyy in the End Date field.
e. Enter the end time in h:mm in the End Time field.
Step 6 Click Generate Report to generate the Utilization Data Report for the threshold percentage.
Note If the Utilization Data Report lists more than 100 results, you must change the parameters and narrow the query.
After receiving all the data, you can verify the data by using the formula conversions (see Table 10-22 and Table 10-23). If no data is available, the status bar reports that the Utilization Data Report has no data to report.
Note To stop generating the Utilization Data Report, click Stop Report Generation.
Figure 10-2 Statistics Report Window—Utilization Report
10.5.2.3 Exporting the Utilization Data Report
After generating the Utilization Data Report, you can verify that the report has been exported. To export the Utilization Data Report at the node level, see Exporting the Data Report.
10.5.2.4 Generating a Utilization Data Report for Connection Endpoints
You can select a port in the Statistics Report and retrieve all the connections for the port. All the connection data reports are retrieved for the Raw Data Report, Utilization Data Report, and Performance Data Report at the same time.
Step 1 In the Domain Explorer, click the node and choose Configuration > MGX Voice Gateway > Configuration Center.
Step 2 In Configuration Center, click the Connections tab.
Step 3 Drag the node to the right-hand pane to display the Connection Browser window. Click the Connection List tab.
Step 4 Enter the number of connections you want to retrieve in the Connection Count to be retrieved field. To retrieve all the connections, enter an asterisk (*).
Step 5 Click Get to retrieve the connections. For example, you can retrieve connections for both local and remote endpoints for the node.
The Connection Browser window appears with the number of connections matching the filtering criteria. A list of connections that have either local or remote endpoints is displayed in the connection list.
Step 6 Right-click the connection type from the list of connections and choose Statistics Report.
Step 7 Choose Utilization Data Report from the drop-down list.
The Utilization Data Report Connections window is displayed.
Step 8 Choose Utilization Data Report from the drop-down list:
Step 9 Choose Utilization Report for Conn from the drop-down list.
Step 10 Enter the threshold percentage in the Utilization Threshold Percentage field.
Step 11 From the Time Period Parameters area:
a. Choose one of the following time period schedules:
–TOD—(Time of Day) This value is specified by the user.
–Prev Hour
–Prev Day
–Prev Week
b. Enter the start date in dd/mm/yyyy in the Start Date field.
c. Enter the start time in h:mm in the Start Time field.
d. Enter the end date in dd/mm/yyyy in the End Date field.
e. Enter the end time in h:mm in the End Time field.
Step 12 Click Generate Report to generate the Utilization Data Report for the threshold percentage.
Note If the Utilization Data Report lists more than 100 results, you can change the parameters and narrow the query.
The Utilization Data Report shows the connections that have crossed the specified threshold. After receiving all the data, you can verify the data by using the formula conversions (see Table 10-22 and Table 10-23). If no data is available, the status bar reports that the Utilization Data Report has no data to report.
10.5.3 Viewing Performance Data Reports
Table 10-24 lists the performance data information in a given time period for the selected object.
Table 10-24 Performance Data Report Information
Object Type
|
Description
|
Ports
|
Displays both receive percentage and transmit percentage.
|
Connections
|
Displays both local and remote endpoints for receive percentage and transmit percentage along with service, in seconds.
|
For more information on the supported objects for each report type, see Table 10-20.
These tasks are used to configure Performance Data Reports:
•Calculating the Statistics Percentages for the Performance Data Report
•Generating the Performance Data Report for a Port
•Displaying the Performance Data Report for a Port
•Generating the Performance Data Report for Connections
•Displaying the Performance Data Report for Connections
10.5.3.1 Calculating the Statistics Percentages for the Performance Data Report
You can calculate the statistics percentages for the Performance Data Report.
Table 10-25 lists the statistics for port performance.
Table 10-25 Port Performance Statistics
Port Type
|
Percentage Bytes Received (Stats ID)
|
Percentage Bytes Transmitted (Stats ID)
|
Cisco MGX 8850 (PXM45) ATM (AXSM)
|
Egress CLP0 Cells From backplane (6) + Egress CLP1 Cells From backplane (7)
|
Ingress CLP0 Cells to backplane (4) + Ingress CLP1 Cells to backplane (5)
|
Cisco MGX 8850 (PXM45) ATM (AXSM-E)
|
CLP0 cells transmitted (Ingress) (61) + CLP1 cells transmitted (Ingress) (62)
|
CLP0 cells transmitted(0) + CLP1 cells transmitted(1)
|
Cisco MGX 8850 (PXM45)
|
Bytes Received (1)
|
Bytes Transmitted (10)
|
Table 10-26 lists the statistics for connection performance.
Table 10-26 Connection Performance Statistics
Endpoint Type
|
Percentage Bytes Received (Stats ID)
|
Percentage Bytes Transmitted (Stats ID)
|
Percentage of Time in Service (Stats ID)
|
Cisco MGX 8880 (VXSM)
|
No. ingress cells to network (0)
|
No. egress cells to network (5)
|
—
|
Cisco MGX 8880 (VISM-PR)
|
Total num cells received (1)
|
Total num cells Tx (0)
|
—
|
Cisco MGX 8850 (PXM45) AXSM
|
Ingress CLP0 Cells From Port + Ingress
CLP1 Cells From Port) - (Ingress CLP0+1 cells discarded)
|
Egress CLP0 Cells to Port(7) + Egress
CLP1 Cells to Port(8)
|
—
|
Cisco MGX 8850 (PXM45) AXSM-E
|
CLP0 cells from port (5)+ CLP1 cells from port (6)
|
CLP1 cells to the port(19) + CLP1 cells to the port (20)
|
—
|
10.5.3.2 Generating the Performance Data Report for a Port
Multiple Performance Data Reports can be generated at the same time.
Step 1 In the Statistics Report Tool, drag the port from the hierarchy pane to the right-hand pane.
Step 2 Choose Performance Data Report from the drop-down list. See Figure 10-3.
Step 3 Choose Performance Data Report for Port from the drop-down list.
Step 4 From the Time Period Parameters area:
a. Choose one of the following time period schedules:
–TOD—(Time of Day) This value is specified by the user.
–Prev Hour
–Prev Day
–Prev Week
b. Enter the start date in dd/mm/yyyy in the Start Date field.
c. Enter the start time in h:mm in the Start Time field.
d. Enter the end date in dd/mm/yyyy in the End Date field.
e. Enter the end time in h:mm in the End Time field.
Step 5 Click Generate Report to generate the Performance Data Report for the port. If no data is available, the status bar reports that the Performance Data Report has no data to report.
Note To stop generating the Performance Data Report, click Stop Report Generation.
Figure 10-3 Statistics Report Window—Performance Data Report
10.5.3.3 Displaying the Performance Data Report for a Port
After you finish generating the Performance Data Report (see Generating the Performance Data Report for a Port), you must ensure that the graphical information is correct. For example, you must verify that the report shows the correct port object identifier according to the entity label specifications.
Step 1 Verify the performance data information by using the formulas. For information about the formulas for a port, see Table 10-25.
The performance data information for the port is displayed.
Step 2 Click Close to close the report summary.
10.5.3.4 Generating the Performance Data Report for Connections
You can select a port in the Statistics Report and retrieve all the connections for the port. All the connection data reports are retrieved for the Raw Data Report, Utilization Data Report, and Performance Data Report at the same time.
Step 1 In Domain Explorer, select the node and choose Configuration > MGX Voice Gateway > Configuration Center.
Step 2 In Configuration Center, click the Connections tab.
Step 3 Drag the node to the right-hand pane to display the Connection Browser window.
Step 4 Click the Connection List tab.
Step 5 Enter the number of connections you want to retrieve in the Connection Count to be Retrieved field. To retrieve all the connections, enter an asterisk (*).
Step 6 Click Get to retrieve the connections. For example, you can retrieve connections for both local and remote endpoints for the node.
The Connection Browser window appears with the number of connections matching the filtering criteria. A list of connections that have either local or remote endpoints is displayed in the connection list.
Step 7 Right-click the connection type from the list of connections and choose Statistics Report. The Statistics Report opens.
Step 8 Choose Performance Data Report from the drop-down list.
Step 9 Choose Performance Data Report for Conn from the drop-down list.
Step 10 From the Time Period Parameters area:
a. Choose one of the following time period schedules:
–TOD—(Time of Day) This value is specified by the user.
–Prev Hour
–Prev Day
–Prev Week
b. Enter the start date in dd/mm/yyyy in the Start Date field.
c. Enter the start time in h:mm in the Start Time field.
d. Enter the end date in dd/mm/yyyy in the End Date field.
e. Enter the end time in h:mm in the End Time field.
Step 11 Click Select Connection(s) to view the available connections.
Step 12 Select the connection.
Step 13 Click Next.
Step 14 Click Generate Report to generate the report for connection endpoints.
Note To stop generating the Performance Data Report, click Stop Report Generation.
10.5.3.5 Displaying the Performance Data Report for Connections
After you finish generating the Performance Data Report, you must ensure that the report displays one chart for the performance data of the connection local endpoint and the other chart for the performance data of the connection remote endpoint.
Step 1 Verify the performance data information by using the formulas. For information about the formulas for a port, see Table 10-25.
The performance data information for connection endpoints is displayed.
Step 2 Click Close to close the report summary.
10.5.4 Exporting the Data Report
After generating the Data Report, you can verify that the report has been exported.
Step 1 After generating a Raw Data Report, click Export Report to export the report data.
Step 2 Choose one of the following radio buttons in the Format area:
•CSV—Comma-separated value file.
•Tab—Tab-separated value file.
Step 3 Click Browse to select the location to save the results of the query.
Step 4 Click Export to export the report data to the file.
