|
|
This chapter describes the CDM performance windows on which you can view real-time, current performance information within 10-second polled intervals for interfaces and line cards. This chapter also describes how to access CDM windows that display historical performance data.
This chapter includes the following sections:
The Interface Performance window displays generic performance data for the selected interface. To open the Interface Performance window, complete the following steps:
Step 2 Choose Cisco DSL Manager > Physical > Interface > Generic > Performance.
The Interface Performance window opens, which is shown in Figure 8-1. The window opens to the Performance (1) tab.
Step 3 From the list boxes on the left, select the relevant chassis, card, and interface.
The interface performance information for the selected interface displays on the right.
Step 4 Click Start to start performance logging on the selected interface, for example, central processing unit (CPU) or ports.
 |
Note Performance logging logs data that can be displayed using the Performance Manager application. |
Step 5 Click Stop to stop global performance logging.
 |
Tips If you have already clicked the Stop or Start button, you cannot click that button again. |
The Performance (1) tab displays three areas—General Information, Packets/Octets Statistics, and Performance Logging. The fields on this tab are described in Table 8-1.
| Field | Description |
|---|---|
Resets | Number of times the interface resets internally. |
Transmitted Bandwidth Utilization | Percentage of the bandwidth for transmitting data that is being used. |
Received Bandwidth Utilization | Percentage of the bandwidth for receiving data that is being used. |
In Octets | Total number of packets received on the interface, including framing characters. |
In Bits/sec | Average number of bits per second received during the last five-minute period. |
In Packets/sec | Average number of packets per second received during the last five-minute period. |
In Unicast Packets | Number of packets received by the layer that were not addressed as multicast or broadcast packets. |
In Multicast Packets | Number of packets received by the layer addressed as multicast. |
In Broadcast Packets | Number of packets received by the layer addressed as broadcast. |
Out Octets | The total number of packets transmitted out of the interface, including framing characters. |
Out Bits/sec | The average number of bits per second transmitted during the last five minute period. |
Out Packets/sec | The average number of packets per second transmitted during the last five minute period. |
Out Unicast Packets | Number of packets transmitted by the layer that were not addressed as multicast or broadcast packets. |
Out Multicast Packets | Number of packets transmitted by the layer addressed as multicast packets. |
Out Broadcast Packets | Number of packets transmitted by the layer addressed as broadcast packets. |
The Interface Performance window also contains a Performance (2) tab, which is shown in Figure 8-2.
The Performance (2) tab displays a single Error Statistics area; the fields in this area are described in Table 8-2.
| Field | Description |
|---|---|
Runts | Number of input packets that were smaller than the physical media permits. |
Giants | Number of input packets input that were larger than the physical media permits. |
Collisions | Number of output collisions detected on this interface. |
Aborted Packets | Number of input packets that were aborted. |
Ignored Packets | Number of input packets ignored by the selected interface. |
Overrun Packets | Number of input packets that arrived too quickly for the hardware to receive. |
Misaligned Packets | Number of misaligned input packets. |
In Errored Packets | Number of input packets that contained errors. |
In Discarded Packets | Number of input packets selected to be discarded even though no errors are found. |
In Packets Dropped | Number of packets dropped because the input queue was full. |
Out Errored Packets | Number of outbound packets that could not be transmitted because of errors. |
Out Discarded Packets | Number of outbound packets selected to be discarded even though no errors had been detected. |
Out Packets Dropped | Number of outbound packets dropped because the output queue is full. |
CRC Errored Packets | Number of input packets that contain cyclic redundancy checksum errors. |
Step 2 Choose Cisco DSL Manager > Physical > Interface > DS3 > Performance.
The DS3 Interface Performance window opens, which is shown in Figure 8-3. The DS3 Interface Performance window has one tab, the Performance tab.
Step 3 From the list boxes on the left, select the relevant chassis, card, and DS3 interface.
The current performance information for the selected DS3 interface appears on the right.
The Performance tab contains two areas, DS3 Statistics, and Far End DS3 Statistics. The fields on this tab are described in Table 8-3.
| Field | Descriptions |
|---|---|
C-bit Coding Violations | Number of C-bit coding violations encountered by the port interface. |
C-bit Errored Seconds | Number of C-bit errored seconds detected by the port interface. |
C-bit Severely Errored Seconds | Number of C-bit severely errored seconds detected by the port interface. |
P-bit Errored Seconds | Number of P-bit errored seconds detected by the port interface. |
P-bit Severely Errored Seconds | Number of P-bit severely errored seconds encountered by the port interface. |
P-bit Coding Violations | Number of P-bit coding violations detected by the port interface. |
Line Coding Violations | Number of line coding violations detected by the port interface. |
Line Errored Seconds | Number of line errored seconds detected by the port interface. |
Severely Errored Framing Seconds | Number of severely errored framing seconds detected by the port interface. |
Unavailable Seconds | Unavailable seconds encountered by the port interface. |
C-bit Coding Violations | Number of far end C-bit coding violations encountered by the port interface. |
C-bit Severely Errored Seconds | Number of far end C-bit severely errored seconds detected by the port interface. |
C-bit Errored Seconds | Number of far end C-bit errored seconds detected by the port interface. |
Unavailable Seconds | Number of far end unavailable seconds encountered by the port interface. |
You can view performance data about the ADSL interface on the ADSL Interface Performance window. Complete the following steps to view ADSL performance data:
Step 2 Choose Cisco DSL Manager > Physical > Interface > ADSL > Performance.
The ADSL Interface Performance window opens, which is shown in Figure 8-4.
|
Note The software automatically creates four DMT interfaces when you deploy a DMT line card. These DMT interfaces are actually ATM over ADSL over DMT interfaces, which means that all three interfaces are combined in CDM and identified by the last specific DMT interface. Therefore, when you view performance information for an ADSL interface, it is identified as a DMT interface. |
Step 3 From the list boxes on the left, select the relevant chassis, card, and ADSL interface. The current performance information for the selected ADSL interface appears on the right.
The ADSL Performance window contains six tabs:
The fields on these tabs are described in the following sections.
The Line Performance (1) tab contains two areas—Agent Reset and Current 15 Minutes. These fields are described in Table 8-4.
|
Note The agent refers to the Cisco DSLAM chassis. |
|
Note The Current 15 Minutes area displays information collected during the most recent 15-minute interval for which performance monitoring information was derived. |
| Field | Description |
|---|---|
Loss of Signal | Total number of loss of signal failures since the last reset. |
Initialization Attempts | Total number of line initialization attempts since reset. It includes both successful and failed attempts. |
Loss of Link | Number of loss of link failures since reset. |
Loss of Power | Number of loss of power failures since reset. |
Errored Seconds | Number of errored seconds since reset. |
Loss of Frame | Number of loss of framing failures since reset. |
Valid Intervals | Number of previous intervals for which valid data has been stored. |
Invalid Intervals | Number of previous intervals for which invalid data has been stored. |
Loss of Signal | Number of seconds in the current 15-minute interval during which loss of signal was detected. |
Initialization Attempts | Number of line initialization attempts in the current 15-minute interval. It includes both successful and failed attempts. |
Loss of Link | Number of seconds in the current 15-minute interval during which loss of link was detected. |
Loss of Power | Number of seconds in the current 15-minute interval during which loss of power was detected. |
Errored Seconds | Number of errored seconds in the current 15-minute interval. |
Loss of Frame | Number of seconds in the current 15-minute interval during which loss of framing was detected. |
Elapsed Time | Number of seconds that have elapsed in the specified interval. A full interval is 900 seconds. |
The Line Performance (2) tab, which is shown in Figure 8-5, contains two areas—Current Day and Previous 1 Day (Figure 8-5).
The fields on this tab are described in Table 8-5.
|
Note The Previous 1 Day area displays the time in the previous 1-day interval during which the performance monitoring information was actually counted. This value is normally the same as the total interval duration except when performance monitoring data cannot be collected for any reason. Typically, elapsed 1-day time is copied into monitored seconds when the 1-day rollover occurs. |
|
Note The Current Day area displays the time in the current day during which the performance monitoring information is actually counted. This value is normally the same as the total interval duration except in when performance monitoring data cannot be collected for any reason. |
| Field | Description |
|---|---|
Loss of Signal | Number of seconds since there was loss of signal during the current day. |
Initialization Attempts | Number of line initialization attempts in the day. It includes both successful and failed attempts. |
Loss of Link | Number of seconds since there was loss of link during the current day. |
Loss of Power | Number of seconds since there was loss of power during the current day. |
Errored Seconds | Number of errored seconds that have elapsed during the current day. |
Loss of Frame | Number of seconds since there was loss of framing during the current day. |
Elapsed Time | Number of seconds that have elapsed since the beginning of the current 1-day interval. |
Loss of Signal | Number of seconds since there was loss of signal during the previous day. |
Initialization Attempts | Number of line initialization attempts in the previous day. It includes both successful and failed attempts. |
Loss of Link | Number of seconds over which there was loss of link during the previous day. |
Loss of Power | Number of seconds over which there was loss of power during the previous day. |
Errored Seconds | Number of errored seconds that have elapsed during the current day. |
Loss of Frame | Number of seconds over which there was loss of framing during the previous day. |
Monitored Seconds | Number of seconds over which data was collected or monitored during the previous day. |
The Fast Channel Performance (1) tab, which is shown in Figure 8-6, contains two areas—Agent Reset and Current 15 Minutes.
The fields on this tab are described in Table 8-6.
| Field | Description |
|---|---|
Transmitted Blocks | Number of blocks of data transmitted since the last agent reset. |
Uncorrected Blocks | Number of uncorrected blocks of data transmitted since the last agent reset. |
Corrected Blocks | Number of corrected blocks of data transmitted since the last agent reset. |
Valid Intervals | Number of intervals since the last agent reset during which data monitoring was valid. |
Invalid Intervals | Number of intervals since the last agent reset during which data monitoring was not valid. |
Received Blocks | Number of blocks of data received since the last agent reset. |
Transmitted Blocks | Number of blocks of data transmitted during the current 15-minute interval. |
Uncorrected Blocks | Number of uncorrected blocks of data transmitted during the current 15-minute interval. |
Corrected Blocks | Number of corrected blocks of data transmitted during the current 15-minute interval. |
Time Elapsed | Amount of time that has elapsed since the start of the current 15-minute interval. |
Received Blocks | Number of blocks of data received during the current 15-minute interval. |
The Fast Channel Performance (2) tab, which is shown in Figure 8-7, contains two areas—Current Day and Previous 1 Day.
The fields on this tab are described in Table 8-7.
| Field | Description |
|---|---|
Transmitted Blocks | Number of blocks of data transmitted during the current day interval. |
Uncorrected Blocks | Number of uncorrected blocks of data transmitted during the current day interval. |
Corrected Blocks | Number of corrected blocks of data transmitted during the current day interval. |
Time Elapsed | Amount of time that has elapsed since the start of the current day interval. |
Received Blocks | Number of blocks of data received during the current day interval. |
Transmitted Blocks | Number of blocks of data transmitted during the previous day interval. |
Uncorrected Blocks | Number of uncorrected blocks of data transmitted during the previous day interval. |
Corrected Blocks | Number of corrected blocks of data transmitted during the previous day interval. |
Received Blocks | Number of blocks of data received during the previous day interval. |
Monitored Seconds | Number of seconds during the previous day interval when data was monitored. |
The Interleave Channel Performance (1) tab, which is shown in Figure 8-8, contains two areas—Agent Reset and Current 15 Minutes (Figure 8-8).
The fields on this tab are described in Table 8-8.
| Field | Description |
|---|---|
Transmitted Blocks | Number of blocks of data transmitted since the last agent reset. |
Uncorrected Blocks | Number of uncorrected blocks of data transmitted since the last agent reset. |
Corrected Blocks | Number of corrected blocks of data transmitted since the last agent reset. |
Valid Intervals | Number of intervals since the last agent reset during which data monitoring was valid. |
Invalid Intervals | Number of intervals since the last agent reset during which data monitoring was not valid. |
Received Blocks | Number of blocks of data received since the last agent reset. |
Transmitted Blocks | Number of blocks of data transmitted during the current 15-minute interval. |
Uncorrected Blocks | Number of uncorrected blocks of data transmitted during the current 15-minute interval. |
Corrected Blocks | Number of corrected blocks of data transmitted during the current 15-minute interval. |
Time Elapsed | The amount of time that has elapsed since the start of the current 15-minute interval. |
Received Blocks | Number of blocks of data received during the current 15-minute interval. |
The Interleave Channel Performance (2) tab, which is shown in Figure 8-9, contains two areas—Current Day and Previous 1 Day.
The fields on this tab are described in Table 8-9.
| Field | Description |
|---|---|
Transmitted Blocks | Number of blocks of data transmitted during the current day interval. |
Uncorrected Blocks | Number of uncorrected blocks of data transmitted during the current day interval. |
Corrected Blocks | Number of corrected blocks of data transmitted during the current day interval. |
Monitored Seconds | Number of seconds during the current day interval when data was monitored. |
Received Blocks | Number of data blocks received during the current day interval. |
Transmitted Blocks | Number of blocks of data transmitted during the previous day interval. |
Uncorrected Blocks | Number of uncorrected blocks of data transmitted during the previous day interval. |
Corrected Blocks | Number of corrected blocks of data transmitted during the previous day interval. |
Monitored Seconds | Number of seconds during the previous day interval when data was monitored. |
Received Blocks | Number of data blocks received during the previous day interval. |
To view the ATM Interface Performance data window, complete the following steps:
Step 2 Choose Cisco DSL Manager > Physical > Interface > ATM > Performance.
The ATM Interface Performance window opens, which is shown in Figure 8-10. The ATM Interface Performance window has one tab, the Performance tab.
|
Note CDM automatically creates four DMT interfaces when you deploy a DMT line card. These DMT interfaces are actually ATM over ADSL over DMT interfaces. This means that all three interfaces are combined in CDM and identified by the last specific DMT interface. Therefore, when you view performance information for an ATM interface, it is identified as a DMT interface. |
Step 3 From the list boxes on the left, select the relevant chassis, card, and ATM interface.
The current performance information for the selected ATM interface appears on the right.
The Performance tab contains four areas:
These tabs are described in the following sections.
Received and transmitted gauges are displayed from a subscriber point of view. The transmitted values display the number of cells per second that the subscriber is transmitting. The received values display the number of cells per second that the subscriber is receiving.
The Transmitted and Received areas display the same attribute parameters, which are described in Table 8-10.
| Field | Description | ||||
|---|---|---|---|---|---|
Restarts | Number of Restart Activity errors that are transmitted from this interface. The Restart Activity Counter provides a count of host, switch, or network restart activity. This counter is incremented when transmitting a Restart message. | ||||
Timer Expires | Number of Timer Expiries transmitted from this interface. The Timer Expires counter provides a count of network timer expiries, and to some extent, host or switch timer expiries. The Timer Expiries counter is incremented whenever one of the following conditions occurs:
| ||||
Called Party Events | Number of Called Party Responsible For Unsuccessful Call messages transmitted from this interface. This counter is incremented when a Release, Release Complete (only when not preceded by a Release message for the same call), Add Party Reject, or Status message is transmitted that contains one of the cause code values that are as follows:
| ||||
Calling Party Events | Number of Calling Party Events messages transmitted from this interface. This counter monitors error events that occur due to the originating user performing an incorrect action. This counter is incremented when a Release, Release Complete (only when not preceded by a Release message for the same call), Add Party Reject, or Status message is transmitted that contains one of the following cause code values:
| ||||
Unavailable Routes | Number of Route Unavailability messages transmitted from this interface. This counter is incremented when a Release, Release Complete (only when not preceded by a Release message for the same call), Add Party Reject, or Status message is transmitted that contains one of the following cause code values:
| ||||
Number of Resource Unavailability messages transmitted from this interface. This counter is incremented when a Release, Release Complete (only when not preceded by a Release message for the same call), Add Party Reject, or Status message is received that contains one of the following cause code values.
| |||||
Setup Attempts | Number of call setup attempts (both successful and unsuccessful) transmitted on this interface. | ||||
Number of Cells | Number of cells transmitted on this interface, including p2p and p2mp cells. | ||||
Bandwidth Utilization | Displays the used bandwidth as a percentage of the maximum bandwidth supported by the port. |
The Connection Established area displays the fields that are described in Table 8-11:
| Field | Description |
|---|---|
Incoming | Number of switched virtual connections (SVCs) virtual channel connections (VCCs) established at the signaling entity for incoming connections. |
Outgoing | Number of SVC VCCs established at the signaling entity for outgoing connections. |
The Service-Specific Connection-Oriented Protocol (SSCOP) area displays the Connection Event. This field displays the SSCOP Connection Events counter. The counter counts the sum of the errors as described in Table 8-12.
| Counter | Description |
|---|---|
SSCOP Connection Disconnect Counter | The abnormal occurrence of the event is characterized by the expiration of Timer_NO_RESPONSE. (The event is communicated to the layer management with MAA-ERROR code P. Refer to ITU-T Q.2110 [13].) |
SSCOP Connection Initiation Failure | The condition indicates the inability to establish an SSCOP connection. The event occurs whenever the number of expires of the connection control timer (Timer_CC) exceeds the MaxCC or upon receipt of a connection reject message BGREJ PDU. (The event is communicated to layer management with MAA-ERROR code O. Refer to ITU-T Q.2110.) |
SSCOP Connection Re-establ/Resynch |
The inverse multiplexing over ATM (IMA) Group Performance and Link Performance windows display information about the IMA connections. These windows are described in the following sections.
To open the IMA Group Performance window, complete the following steps:
Step 2 Choose Cisco DSL Manager > Physical > Interface > IMA Group > Performance from the object menu.
The IMA Group Performance window, which is shown in Figure 8-11, opens.
This window contains two areas—Operation and Failures. The fields on this window are described inTable 8-13.
| Field | Description |
|---|---|
Running Time | Displays a count of the IMA group running seconds. |
Unavailable Time | Displays a count of the IMA group unavailable seconds. |
No. of near-end Group Failures | Displays the number of times that a near-end group failure (Config-Abort, Insufficient-Links) has been reported since power up or reboot. |
No. of far-end Group Failures | Displays the number of times that a far-end group failure (Config-Abort-FE, Insufficient-Links-FE, Blocked-FE) has been reported since power up or reboot. This is an optional attribute. |
To open the IMA Link Performance window, complete the following steps:
Step 2 Choose Cisco DSL Manager > Physical > Interface > IMA Link > Performance from the object window.
The IMA Link Performance window, which is shown in Figure 8-12, opens.
This window includes the following areas:
The fields on this window are described in Table 8-14.
| Field | Description |
|---|---|
Relative Delay with least delay link | The latest measured delay on this link relative to the link, in the same IMA group, with the least delay. |
Displays a count of errored, invalid, or missing ICP1 cells, except during SES2-IMA or UAS3-IMA conditions. | |
OIF Anomalies | Displays the number of OIF anomalies, except during SES-IMA or UAS-IMA conditions, at the near-end. This is an optional attribute. |
No. of Transmit Stuffs | Displays a count of stuff events that are inserted in the transmit direction in the current 15-minute interval. This is an optional attribute. |
No. of Receive Stuffs | Displays a count of stuff events that are inserted in the receive direction in the current 15-minute interval. This is an optional attribute. |
| Near End | |
Unavailable Seconds | Displays a count of unavailable seconds at the near end in one of the previous 96 individual 15-minute intervals. Unavailability begins at the onset of 10 contiguous SES-IMA and ends at the onset of 10 contiguous seconds with no SES-IMA. |
Severely Errored Seconds | Displays a count of 1-second intervals that contain one of the following items except during a UAS-IMA condition, in the previous 24 hour interval:
Invalid 15-minute intervals count as 0. |
No. of Failures | Displays the number of transmit failures and receive failures at the near end. |
Unusable seconds | Displays a count of unusable seconds at the near end. |
| Far End | |
Unavailable Seconds | Displays a count of unavailable seconds at the far end in one of the previous 96, individual 15-minute interval. Unavailability begins at the onset of 10 contiguous SES-IMA-FE and ends at the onset of 10 contiguous seconds with no SES-IMA-FE. |
Severely Errored Seconds | Displays a count of 1-second intervals that contain one or more RDI8-IMA defects, except during a UAS-IMA-FE condition, in the previous 24 hour interval. Invalid 15-minute intervals count as 0. |
No. of Failures | Displays the number of transmit failures and receive failures at the far end. |
Unusable seconds | Displays a count of unusable seconds at the far end. |
The SONET Interface Performance window displays performance data for the SONET interfaces.
|
Note SONET and OC-3 interfaces are the same thing. |
To view the SONET Interface Performance window, follow these steps:
Step 2 Choose Cisco DSL Manager > Physical > Interface > SONET > Performance.
The SONET Interface Performance window opens, which is shown in Figure 8-13.
Step 3 From the list boxes on the left, select the relevant chassis, card, and SONET interface.
The current performance information for the selected SONET interface appears on the right.
The SONET Interface Performance window contains four tabs:
The fields on these tabs are described in the following sections.
The Section tab window contains one area, Section. The fields on this tab are described in Table 8-15.
| Field | Description |
|---|---|
Errored Seconds | Total number of errored seconds encountered by the SONET interface. |
Severely Errored Seconds | Number of severely errored seconds encountered by the SONET interface. |
Severely Errored Framing Seconds | Total number of severely errored framing seconds encountered by the SONET interface. |
Coding Violations | Number of coding violations encountered by the SONET interface. |
The Line tab, which is shown in Figure 8-14, contains two areas—Line and Far End Line.
The fields on this tab are described in Table 8-16.
| Field | Description |
|---|---|
Errored Seconds | Total number of errored seconds encountered by the SONET interface. |
Severely Errored Seconds | Number of severely errored seconds encountered by the SONET interface. |
Unavailable Seconds | Total number of unavailable seconds encountered by the SONET interface. |
Coding Violations | Number of coding violations encountered by the SONET interface. |
Errored Seconds | Total number of errored seconds encountered by the SONET interface. |
Severely Errored Seconds | Number of severely errored seconds encountered by the SONET interface. |
Unavailable Seconds | Total number of unavailable seconds encountered by the SONET interface. |
Coding Violations | Number of coding violations encountered by the SONET interface. |
The Path tab, which is shown in Figure 8-15, contains two areas—Path and Far End Path.
The fields on this tab are described in Table 8-17.
| Field | Description |
|---|---|
Errored Seconds | Total number of errored seconds encountered by the SONET interface. |
Severely Errored Seconds | Number of severely errored seconds encountered by the SONET interface. |
Unavailable Seconds | Total number of unavailable seconds encountered by the SONET interface. |
Coding Violations | Number of coding violations encountered by the SONET interface. |
Errored Seconds | Total number of errored seconds encountered by the SONET interface. |
Severely Errored Seconds | Number of severely errored seconds encountered by the SONET interface. |
Unavailable Seconds | Total number of unavailable seconds encountered by the SONET interface. |
Coding Violations | Number of coding violations encountered by the SONET interface. |
The Virtual Tributary tab, which is shown in Figure 8-16, contains two areas—Virtual Tributary and Far End Virtual Tributary.
The fields on this tab are described in Table 8-18.
| Field | Description |
|---|---|
Errored Seconds | Total number of errored seconds encountered by the SONET interface. |
Severely Errored Seconds | Number of severely errored seconds encountered by the SONET interface. |
Unavailable Seconds | Total number of unavailable seconds encountered by the SONET interface. |
Coding Violations | Number of coding violations encountered by the SONET interface. |
Errored Seconds | Total number of errored seconds encountered by the SONET interface. |
Severely Errored Seconds | Number of severely errored seconds encountered by the SONET interface. |
Unavailable Seconds | Total number of unavailable seconds encountered by the SONET interface. |
Coding Violations | Number of coding violations encountered by the SONET interface. |
The Module Performance window displays current performance data for any selected card such as an NI-2 card or a DMT line card.
|
Note Module performance attributes that display only relate to CPU performance. This means that cards without their own CPU display the same values as the CPU card in the chassis. |
To view the Module Performance window, complete the following steps:
Step 2 Choose Cisco DSL Manager > Physical > Module > Performance.
The Module Performance window opens, which is shown in Figure 8-17.
Step 3 From the list boxes on the left, select the relevant chassis and card.
Step 4 Click Start to begins performance polling on a specified card.
|
Note After you start performance logging on a card, the state of that card changes to PerfMonitoring. The state of a card, chassis or interface is displayed in the bottom left corner of each window. |
Step 5 Click Stop to stop performance polling on a specified card.
The current performance information for the selected card appears at the right.
The Performance tab contains two areas—CPU Usage and Performance Logging. The fields on this tab are described in Table 8-19.
| Detail | Description |
|---|---|
CPU Busy% | Displays the CPU put to use in terms of percentage. |
Average (1 min) | Percentage CPU usage averaged over the previous one-minute interval. |
Average (5 min) | Percentage CPU usage averaged over the previous five-minute interval. |
This section describes how to access the windows that display historical performance data. The Performance Manager window displays historical data as well as current data in the form of a line chart, bar chart, or table; the Performance menu displays only current data in a raw numerical format. You access both performance options through the Map Viewer window.
This section includes the following sections:
You can open the Performance Manager within the Map Viewer window. After you open the Map Viewer window, complete the following steps:
Step 2 Choose Tools > Performance Manager.
The Performance Manager window opens, which is shown in Figure 8-18, with the Line Chart tab displayed by default.
The Performance Manager window consists of three list boxes on the left, and three tabbed sections on the right. Select the parameters that you want to monitor from the list boxes.
Step 3 From the Monitored Attributes list, select the attribute you want to monitor.
You can select multiple contiguous attributes in a list by holding down the Shift key and then selecting the first and last attributes in the list. You can select multiple individual attributes by holding down the Ctrl key and clicking individual items. Information for all selected attributes is shown in the table display. Only the first selected attribute is shown in the line chart or bar chart.
Step 4 In the Time Period area, select the time parameters.
Step 5 Set the Start Date.
Step 6 Enter the date on which you want to begin viewing performance data in the Start Date entry boxes; use the format mm/dd/yyyy.
Step 7 Set the Start Time.
Enter the time you want the performance data to start on in the Start Time data entry boxes. Set a start time and an end time using the 24-hour clock notation. The times are inclusive.
Step 8 Set the End Date.
You have two options when setting the end date. Enter the date on which you want to stop viewing performance data in the End Date entry boxes. The format must be mm/dd/yyyy. Or, select the Now checkbox to view the data from the selected start date to the current time. If you select this option, you do not need to update the End Date and Time fields.
Step 9 Set the End Time.
You have two options when setting the end time. Enter the end date on which you wish to stop viewing performance data in the End Time entry boxes. The format must be mm/dd/yyyy. Or, select the Now checkbox to view the data from the selected start date to the current time. By selecting this option, you do not have to update the end date and time fields.
Step 10 Use the down arrow to select the Summary interval.
The summary interval is the period of time over which the rule is applied. This varies according to the attribute selected. You can select the Raw option, which displays performance data in its most detailed format, not summarized.
|
Note If you select Raw, the bar chart view is not available, and the Summary Rule option is dimmed. |
Step 11 Click Refresh Screen.
Refreshing the screen initiates your request for data. Refresh Screen is blue when it is available for selection and dimmed when not available. The Refresh Screen button is available for selection if Now is selected or if any criteria has changed and you have moved the cursor away from the changed value (for example, by pressing the Tab key or by using the mouse).
A line chart of the performance information that you request displays on the right. You can click any of the three tabs to display your data in a different chart format.
|
Note The performance information corresponds with the raw value of the attributes. If you select a summary period, the information is displayed according to the summary rule. No summary period is associated with raw data. |
Table 8-20 describes the options in the Monitored Attributes list. See Figure 8-18.
| Attribute | Description |
|---|---|
Section Errored Seconds | Number of errored seconds encountered by a SONET section in the latest 15-minute interval. |
Section Severely Errored Seconds | Number of severely errored seconds encountered by a SONET section in the latest 15-minute interval. |
Section Severely Errored Framing Seconds | Number of severely errored framing seconds encountered by a SONET section in the latest 15-minute interval. |
Section Coding Violations | Number of coding violations encountered by a SONET section in the latest 15-minute interval. |
Line Errored Seconds | Number of errored seconds encountered by a SONET line in the latest 15-minute interval. |
Line Severely Errored Seconds | Number of severely errored seconds encountered by a SONET line in the latest 15-minute interval. |
Line Unavailable Seconds | Number of unavailable seconds encountered by a SONET line in the latest 15-minute interval. |
Line Coding Violations | Number of coding violations encountered by a SONET line in the latest 15-minute interval. |
The Line Chart tab displays the retrieved data in a graphical format (see Figure 8-18). The X-axis depicts the time at which the polling was done, and the Y-axis depicts the value retrieved or the value when the equipment did not respond properly.
Further information about the element, units, and missed polls is provided, using the appropriate color coding displayed at the top of the chart. Blue represents the values retrieved and red identifies any polled values missed.
The information on the Bar Chart tab displays as a bar chart with the retrieved data (see Figure 8-18). Blue represents the values retrieved and red identifies any polled values missed.
This tab displays the data retrieved in a tabular format (see Figure 8-18). The first column shows the time of polling, and the second column shows the retrieved values. Blue represents the values retrieved and red identifies any polled values missed.
In some circumstances, possibly due to Cisco EMF being shut down or heavy network loads, an object may fail to be monitored. This is known as a missed poll. All missed polls are indicated by a yellow point on Performance Manager graphs and charts. The last valid value collected is shown. A missed poll affects the summary data and you should not rely upon such data.
Performance Manager graphs and charts also indicate when an attribute started and stopped being polled due to history storage criteria being added, edited, or removed. Start and stop polling events are shown in charts and tables. The pstart polling events point is shown in green, and the stop polling events point is shown in red.
|
Note A polling events key appears for a selection. |
When you deploy a DMT line card, CDM automatically creates four ATM over ADSL over DMT interfaces. For simplification, these interfaces are generally referred to as DMT interfaces throughout CDM. In a sense, the three technologies are combined in one interface. You can view performance information for any one of these technologies by selecting it in the Performance Manager list box.
You can open the Performance Manager within the Map Viewer window. After you have opened one of these windows, complete the following steps:
Step 2 Choose Tools > Performance Manager, which is shown in Figure 8-19.
The Performance Manager window opens, which is shown in Figure 8-20, with the Line Chart tab displayed by default.
The Performance Manager window consists of three list boxes on the left side, and three tabbed sections on the right. Select the parameters you want from the left areas.
Step 3 From the Monitored Attributes list, select the attribute you want to monitor.
This list includes attributes for ATM, ADSL, and DMT interfaces. You can select multiple contiguous attributes in a list by holding down the Shift key and then selecting the first and last attributes in the list. You can select multiple individual attributes by holding down the Ctrl key and clicking on individual items. Information for all selected attributes is shown in the table display. Only the first selected attribute is shown in the line chart or bar chart.
Step 4 In the Time Period area, select the time parameters.
Step 5 Set the Start Date.
Enter the date on which you want to begin viewing performance data in the Start Date entry boxes. The format must be mm/dd/yyyy.
Step 6 Set the End Date.
You have two options when setting the end date. Enter the date on which you want to stop viewing performance data in the End Date entry boxes. The format must be mm/dd/yyyy. Or, select the Now checkbox to view the data from the selected start date to the current time. By selecting this option, you need not update the end date and time fields.
Step 7 Set the Start Time.
Enter the time when you want the performance data to start in the Start Time data entry boxes. Set a start time and an end time using the 24-hour clock notation. The times are inclusive.
Step 8 Set the End Time.
You have two options when setting the end time. Enter the end date on which you wish to stop viewing performance data in the End Time entry boxes. The format must be mm/dd/yyyy. Or, select the Now checkbox to view the data from the selected start date to the current time. By selecting this option, you do not have to update the End Date and Time fields.
Step 9 From the drop-down list, select the Summary interval.
The summary interval is the period of time over which the rule is applied. This varies according to the attribute selected. You can select the Raw option, which displays performance data in its most detailed format, not summarized.
|
Note If you select Raw, the bar chart view is not available, and the Summary Rule option is dimmed. |
Step 10 Click Refresh Screen.
Clicking Refresh Screen initiates your request for data. Refresh Screen is blue when it is available for selection and dimmed when not available. Refresh Screen is available for selection if Now is selected or if any criteria has changed and you have moved the cursor away from the changed value (for example, by pressing the Tab key or by using the mouse).
A line chart of the performance information you requested appears at the right. You can click on any of the three tabs to display your data differently.
|
Note The performance information corresponds to the raw values of the attribute. If you select a summary period, the information is displayed according to the summary rule. No summary period is associated with raw data. |
Posted: Tue Sep 5 09:22:14 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.