|
|
The Cisco Digital Subscriber Line Manager (CDM) performance menus allow you to view real-time, current performance information within 10-second polled intervals on standard dialogs for interfaces and cards.
This chapter describes how to view performance data for the following interfaces and cards:
The Interface Performance window displays generic performance data for the selected interface.
To view the Interface Performance window:
The Interface Performance window appears (Figure 7-1).
Step 2 From the list boxes at left, select the relevant chassis, card, and interface. The interface performance information for the selected interface appears in the tabs at right.
Step 3 You can start or stop performance logging on the selected interface by clicking the appropriate button.
 |
Tips If either the Stop or Start button is already selected, you cannot select that button. |
The Interface Performance window (Figure 7-2) displays two tabs: Performance (1), and Performance (2).
The Performance (1) tab displays three areas: General Information, Packets/Octets Statistics, and Performance Logging.
The General Information area displays the following information:
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.
The Packets/Octets Statistics area displays the following information:
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---Total number of packets transmitted out of the interface, including framing characters.
Out Bits/sec---Average number of bits per second transmitted during the last five minute period.
Out Packets/sec---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 Performance Logging area allows you to start or stop global performance logging.
Start---Click Start to begin performance logging for all monitorable attributes on the chassis, for example, central processing unit (CPU) or ports.
Stop---Click Stop to stop global performance logging.
 |
Note Performance logging logs data that can be displayed using the Performance Manager application. |
The Performance (2) tab displays a single Error Statistics area.
The Error Statistics area displays the following information:
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 permitted 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 is 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 are 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.
The DS3 Interface Performance window displays performance data for the DS3 port on the NI-2 management card.
To view the DS3 Interface Performance window:
The DS3 Interface Performance window appears (Figure 7-3).
Step 2 From the list boxes at left, select the relevant chassis, card, and DS3 interface. The current performance information for the selected DS3 interface appears at right.
The DS3 Interface Performance window has one tab, Performance.
The Performance tab has two areas: DS3 Statistics, and Far End DS3 Statistics.
DS3 Statistics
The DS3 Statistics area of the Performance tab displays the following attributes:
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.
Far End DS3 Statistics
The Far End DS3 Statistics area on the Performance tab displays the following attributes:
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.
To view the ADSL Interface Performance data window:
The ADSL Interface Performance window appears (Figure 7-4).
|
Note Four DMT interfaces are created automatically 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 ADSL interface, it is identified as a DMT interface. |
Step 2 From the list boxes at left, select the relevant chassis, card, and ADSL interface. The current performance information for the selected ADSL interface appears at right.
The ADSL Performance window has six tabs: Line Performance (1), Line Performance (2), Fast Channel Performance (1), Fast Channel Performance (2), Interleave Channel (1), and Interleave Channel (2).
The Line Performance (1) tab window contains two areas: Agent Reset and Current 15 Minutes.
Agent Reset
|
Note The Agent refers to the Cisco DSLAM chassis. |
The Agent Reset area displays the following attributes:
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 Failures---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.
The Current 15 Minutes area displays information collected during the most recent 15 minute interval for which performance monitoring information was derived:
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 window contains two areas: Current Day and Previous 1 Day (Figure 7-5).
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.
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.
Previous 1 Day
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.
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 contains two areas: Agent Reset and Current 15 Minutes (Figure 7-6).
Agent Reset
The Agent Reset area displays the following attributes:
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.
Current 15 Minutes
The Current 15 Minutes area displays the following attributes:
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 Fast Channel Performance (2) tab contains two areas: Current Day and Previous 1 Day (Figure 7-7).
Current Day
The Current Day area displays the following attributes:
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---The 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.
Previous 1 Day
The Previous 1 Day area displays the following attributes:
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 contains two areas: Agent Reset and Current 15 Minutes (Figure 7-8).
Agent Reset
The Agent Reset area displays the following attributes:
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.
Current 15 Minutes
The Current 15 Minutes area displays the following attributes:
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 contains two areas: Current Day and Previous 1 Day (Figure 7-9).
Current Day
The Current Day area displays the following attributes:
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.
Previous 1 Day
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:
The ATM Interface Performance window appears (Figure 7-10).
|
Note Four DMT interfaces are created automatically 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 2 From the list boxes at left, select the relevant chassis, card, and ATM interface. The current performance information for the selected ATM interface appears at right.
The ATM Interface Performance window has one tab, Performance.
The Performance tab contains four areas:
Transmitted and Received
Received and transmitted gauges are displayed from a subscriber's point of view; that is, the transmitted values show the number of cells per second the subscriber is transmitting and the received values show the number of cells per second the subscriber is receiving.
Both the Transmitted and Received areas display the same attribute parameters, as follows:
Restarts---Number of restart activity errors 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 Expiries 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 Parity 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, which contains one of the cause code values listed in Table 7-1.
|
Note A cause code value alerts you that something is wrong with your ISDN connection. |
|
Note A cause code value applies to both User Network Interface (UNI) Version 3.0 and UNI Version 3.1. A UNI is an interface point between ATM end users and a private ATM switch, or between a private ATM switch and the public carrier ATM network. |
| Cause Code Value | Meaning |
|---|---|
17 | User busy |
18 | No user responding |
21 | All rejected |
22 | Number changed |
23 | User rejects all calls with calling line ID restriction (CLIR) |
27 | Destination out of order |
31 | Normal, unspecified |
88 | Incompatible destination |
Calling Parity Events---Number of Calling Parity 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 cause code values listed in Table 7-2.
|
Note These cause code values apply to both UNI 3.0 and UNI 3.1. |
| Cause Code Value | Meaning |
|---|---|
28 | Invalid number format (address incomplete) |
43 | Access information discarded |
57 | Bearer capability not authorized |
65 | Bearer capability not implemented |
73 | Unsupported combination of traffic parameters |
78 | AAL parameters cannot be supported (UNI 3.1 only) |
91 | Invalid transit network selection |
93 | AAL parameters cannot be supported (UNI 3.0 only) |
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 listed in Table 7-3.
|
Note These cause code values apply to both UNI 3.0 and UNI 3.1. |
| Cause Code Value | Meaning |
|---|---|
1 | Unallocated (unassigned) number |
2 | No route to specified transit network |
3 | No route to destination |
|
Note For this counter, Release Complete messages that are a reply to a previous Release message and contain the same cause code value, are redundant (for counting purposes) and should not be counted. |
Unavailable Resources---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 cause code values listed in Table 7-4.
|
Note These cause code values apply to both UNI 3.0 and UNI 3.1 |
| Cause Code Value | Meaning |
|---|---|
35 | Requested VPCI / VCI not available |
37 | User cell rate not available (UNI 3.1 only) |
38 | Network out of order |
41 | Temporary failure |
45 | No VPCI / VCI available |
47 | Resource unavailable, unspecified |
49 | Quality of Service unavailable |
51 | User cell rate not available (UNI 3.0 only) |
58 | Bearer capability not presently available |
63 | Service or option not available, unspecified |
92 | Too many pending add party requests |
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.
Connection Established
The Connection Established area displays the following attributes:
Incoming---Number of switched virtual circuits (SVCs) virtual channel (or Circuit) connections (VCCs) established at the signaling entity for incoming connections.
Outgoing---Number of SVC VCCs established at the signaling entity for outgoing connections.
SSCOP
The Service-Specific Connection-Oriented Protocol (SSCOP) area displays the following attributes:
Connection Event---Displays the SSCOP Connection Events Counter. The counter counts the sum of the following errors:
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:
The SONET Interface Performance window appears (Figure 7-11).
Step 2 From the list boxes at left, select the relevant chassis, card, and SONET interface. The current performance information for the selected SONET interface appears at right.
The SONET Interface Performance window contains four tabbed sections:
The Section tab window contains one area: Section. The Section area displays the following attributes:
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 Line tab contains two areas, Line and Far End Line (Figure 7-12).
Line
The Line area displays the following attributes:
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.
Far End Line
The Far End Line area displays the following attributes:
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---Number of Unavailable Seconds encountered by the SONET interface.
Coding Violations---Number of Coding Violations encountered by the SONET interface.
The Path tab contains two areas, Path and Far End Path (Figure 7-13).
Path
The Path area displays the following attributes:
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.
Far End Path
The Far End Path area displays the following attributes:
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 contains two areas, Virtual Tributary and Far End Virtual Tributary (Figure 7-14).
Virtual Tributary
The Virtual Tributary area displays the following attributes:
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.
Far End Virtual Tributary
The Far End Virtual Tributary area displays the following attributes:
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 module, for example, either an NI-2 management card or a DMT line card.
|
Note Module performance attributes displayed only relate to CPU performance. This means that modules without their own CPU display the same values as the CPU card in the chassis. |
To view the Module Performance window:
The Module Performance window appears (Figure 7-15).
Step 2 From the list boxes at left, select the relevant chassis and module. The current performance information for the selected module appears at right.
The Module Performance window contains one tab, Performance.
The Performance tab window contains two areas: CPU Usage and Performance Logging.
CPU Usage
The CPU Usage area displays the following details:
CPU Busy%---Displays the CPU put to use in terms of percentage.
Average (1 min.)---Displays the percentage CPU usage averaged over the previous one minute interval.
Average (5 min.)---Displays the percentage CPU usage averaged over the previous five minute interval.
Performance Logging
The Performance Logging area has two buttons, a Start and a Stop button. You can begin Performance Polling on a specified card or stop performance polling on a specified card.
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 hand corner of each window.
Posted: Mon Jul 31 05:55:12 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.