|
|
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 view the Interface Performance window, follow these steps:
The Interface Performance window appears (Figure 8-1).
Step 2 From the list boxes at the left, select the relevant chassis, card, and interface.
The interface performance information for the selected interface appears in the tabs.
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 contains two tabs—Performance (1), and Performance (2), which are described in the following sections.
The Performance (1) tab (see Figure 8-1) contains three areas:
Table 8-1 defines the fields that are in the Performance (1) tab.
| Field | Definition | ||
|---|---|---|---|
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 | 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. | ||
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.
|
The Performance (2) tab (Figure 8-2) displays the Error Statistics area.
Table 8-2 defines the fields that are located in the Performance (2) tab.
| Field | Definition |
|---|---|
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 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 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. |
The DS3 Interface Performance window displays performance data for the DS3 port on the NI-2 card.
To view the DS3 Interface Performance window, follow these steps:
The DS3 Interface Performance window appears (Figure 8-3).
Step 2 From the list boxes at the left, select the relevant chassis, card, and DS3 interface.
The current performance information for the selected DS3 interface appears.
The DS3 Interface Performance window contains two areas—DS3 Statistics, and Far End DS3 Statistics. Table 8-3 defines the fields that are located in the DS3 Interface Performance window.
| Field | Definition |
|---|---|
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 | The count of the far end unavailable seconds encountered by the port interface. |
To view the ADSL Interface Performance window, follow these steps:
The ADSL Interface Performance window appears (Figure 8-4).
 |
Note Four DMT interfaces are created automatically when you deploy a DMT 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 the left, select the relevant chassis, card, and ADSL interface.
The current performance information for the selected ADSL interface appears.
The ADSL Interface Performance window contains six tabs.
The Line Performance (1) tab (see Figure 8-4) contains two areas—Agent Reset and Current 15 Minutes. Table 8-4 defines the fields that are located in the Line Performance tab.
|
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 | Definition |
|---|---|
| Agent Reset | |
Loss of Signal | The total number of loss of signal failures since the last reset. |
Initialization Attempts | The 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. |
| Current 15 Minutes | |
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 contains two areas—Current Day and Previous 1 Day (Figure 8-5).
|
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. |
|
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. |
Table 8-5 defines the fields that are located in the Line Performance (2) tab.
| Field | Definitions |
|---|---|
| Current Day | |
Loss of Signal | Number of seconds since there was a 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 a loss of link during the current day. |
Loss of Power | Number of seconds since there was a 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 a 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 | |
Loss of Signal | Number of seconds since there was a 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 a loss of link during the previous day. |
Loss of Power | Number of seconds over which there was a 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 a 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 8-6).
Table 8-6 defines the fields that are in the Fast Channel Performance (1) tab.
| Field | Definition |
|---|---|
| Agent Reset | |
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 | |
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 contains two areas—Current Day and Previous 1 Day (Figure 8-7).
Table 8-7 defines the fields that are in the Fast Channel Performance (2) tab.
| Attribute | Definition |
|---|---|
| Current Day | |
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 | |
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 8-8).
Table 8-8 defines the fields that are in the Interleave Channel Performance (1) tab.
| Field | Definition |
|---|---|
| Agent Reset | |
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 | |
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 8-9).
Table 8-9 defines the fields that are in the Interleave Channel Performance (2) tab.
| Field | Definition |
|---|---|
| Current Day | |
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 IDSL Interface Performance window, follow these steps:
The IDSL Interface Performance window appears (Figure 8-10).
|
Note Four DMT interfaces are created automatically when you deploy a DMT card. These DMT interfaces are actually ATM over IDSL over DMT interfaces. This hierarchy 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 IDSL interface, it is identified as a DMT interface. |
Step 2 From the list boxes at the left, select the relevant chassis, card, and IDSL interface.
The current performance information for the selected IDSL interface appears.
The IDSL Interface Performance window contains two tabs:
The Line Performance (1) tab, which is shown in Figure 8-10, contains two areas—Agent Reset and Current 15 Minutes. Table 8-10 defines the fields that are located in the Line Performance tabs.
|
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 | Definition |
|---|---|
| Agent Reset | |
Coding Violations | Number of coding violations since reset. |
Errored Seconds | Number of errored seconds since reset. |
Severely Errored Seconds | Number of severely errored seconds since reset. |
HDLC Coding Violations | Number of HDLC coding violations since reset. |
HDLC Aborts | Number of HDLC aborts since reset. |
HDLC Frames | Number of HDLC frames with a nonintegral number of octets received since reset. |
Short HDLC Frames | Number of HDLC frames with less than five octets received since reset. |
Long HDLC Frames | Number of HDLC frames with more than 8192 octets received since reset. |
Valid Intervals | Number of previous near-end performance data 15-minute intervals for which data was collected. |
Invalid Intervals | The number of near-end performance data 15-minute intervals in the range from 0 to (current number of valid intervals) for which no data is available. |
| Current 15 Minutes | |
Coding Violations | Number of coding violations in the current 15-minute interval. |
Errored Seconds | Number of errored seconds in the current 15-minute interval. |
Severely Errored Seconds | Number of severely errored seconds in the current 15-minute interval. |
HDLC Coding Violations | Number of HDLC coding violations in the current 15-minute interval. |
HDLC Aborts | Number of HDLC aborts in the current 15-minute interval. |
HDLC Frames | Number of HDLC frames with a non-integral number of octets received in the current 15-minute interval. |
Short HDLC Frames | Number of HDLC frames with less than five octets received in the current 15-minute interval. |
Long HDLC Frames | Number of HDLC frames with more than 8192 octets received in the current 15-minute interval. |
Elapsed Time | Number of seconds that have elapsed in the specified interval. A full interval is 900 seconds. |
The Line Performance (2) tab contains two areas—Current Day and Previous 1 Day (Figure 8-11).
|
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. |
|
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. |
Table 8-11 defines the fields that are located in the Line Performance (2) tab.
| Field | Definitions |
|---|---|
| Current Day | |
Coding Violations | Number of coding violations during the current day. |
Errored Seconds | Number of errored seconds that have elapsed during the current day. |
Severely Errored Seconds | Number of severely errored seconds during the current day. |
HDLC Coding Violations | Number of HDLC coding violations during the current day. |
HDLC Aborts | Number of HDLC aborts during the current day. |
HDLC Frames | Number of HDLC frames with a nonintegral number of octets received during the current day. |
Short HDLC Frames | Number of HDLC frames with less than five octets received during the current day. |
Long HDLC Frames | Number of HDLC frames with more than 8192 octets received during the current day. |
Elapsed Time | Number of seconds that have elapsed since the beginning of the current 1-day interval. |
| Previous 1 Day | |
Coding Violations | Number of coding violations during the current day. |
Errored Seconds | Number of errored seconds that have elapsed during the current day. |
Severely Errored Seconds | Number of severely errored seconds during the current day. |
HDLC Coding Violations | Number of HDLC coding violations during the current day. |
HDLC Aborts | Number of HDLC aborts during the current day. |
HDLC Frames | Number of HDLC frames with a nonintegral number of octets received during the current day. |
Short HDLC Frames | Number of HDLC frames with less than five octets received during the current day. |
Long HDLC Frames | Number of HDLC frames with more than 8192 octets received during the current day. |
Monitoring Seconds | Number of seconds over which data was collected or monitored during the previous day. |
Step 2 Choose Cisco DSL Manager > Logical > FR/PPP Connection > FR/PPP Connection Management > Performance from the object menu.
The FR—ATM Connection Performance Window opens to the FR EndPoint tab, which is shown in Figure 8-12.
The FR EndPoint tab has three areas:
The fields on the FR EndPoint tab are described in Table 8-12. The fields in the Receive and Transmit Parameters area are the same; values for each are described.
| Field | Description |
|---|---|
Frames | Receive—Displays the number of frames received Transmit—Displays the number of frames sent, or transmitted. |
Octets | Receive—Displays the number of octets received. This counter counts octets from the beginning of the frame relay header field to the end of user data. Transmit—Displays the number of octets transmitted. This counter counts octets from the beginning of the frame relay header field to the end of user data. |
FECN1s | Receive—Displays the number of frames received from the network with the FECN bit set. Transmit—Displays the number of frames that are sent to the network with the FECN bit set. |
BECN2s | Receive—Displays the number of frames received from the network with the BECN bit set. Transmit—Displays the number of frames sent to the network with the BECN bit set. |
DE3s | Receive—Displays the number of frames received with the DE bit set. Transmit—Displays the number of frames sent with the DE bit set. |
Discards | Receive—Displays the number of frames received that were discarded at ingress. Possible reasons are policing and congestion. Transmit—Displays the number of frames that were to be transmitted but were discarded. Possible reasons are policing or lack of buffers. |
| Tagged | |
FECNs | Displays the number of frames for which the switch set the FECN bit. |
BECNs | Displays the number of frames for which the switch set the BECN bit. |
DEs | Displays the number of frames for which the switch set the DE bit. |
| 1FECN = Forward Explicit Congestion Notification 2BECN = Backward Explicit Congestion Notification 3DE = discard eligibility |
The FR—ATM Connection Performance FR—ATM Internetworking tab is shown in Figure 8-13.
This tab has one area, Counters. The fields on the FR—ATM tab are described in Table 8-13.
| Field | Description |
|---|---|
CRC Errors | Displays the number of reassembled frames intended to be transmitted on this connection for which the AAL5 PDU1 had CRC2 errors, and were thus discarded. |
Length Errors | Displays the number of reassembled frames intended to be transmitted on this connection for which the AAL5 PDU trailer length fields did not match the actual PDU length, and were thus discarded. |
Discard Frames in Total | Displays the number of frames intended to be transmitted on this connection that were discarded due to any reason including those described in other objects in this table (that is, frames that were discarded because insufficient buffer space was available for reassembling the frame.) |
Unknown Prots Received | Displays the number of frames received with unknown protocol. This event is counted only for connections with service interworking in translation mode. For other types of connections, this count will remain at zero. |
Unknown Prots Transmitted | Displays the number of outbound frames that were not transmitted because they contained an unknown protocol. This event is counted only for connections with service interworking in translation mode. For other types of connections, this count will remain at zero. |
Reassembly Timeouts | Displays the number of reassembly timeouts. |
| 1PDU = protocol data unit 2CRC = cyclic redundancy check |
To view the ATM Interface Performance data window, follow these steps:
The ATM Interface Performance window appears (Figure 8-14).
|
Note Four DMT interfaces are created automatically when you deploy a DMT 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 the left, select the relevant chassis, card, and ATM interface. The current performance information for the selected ATM interface appears.
The Performance tab contains four areas:
The fields on these areas are described in Table 8-14.
|
Note Received and transmitted gauges are displayed from a subscriber 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. |
|
Note The cause code values that are listed in this table apply to User Network Interface (UNI) Version 3.0 and UNI Version 3.1. A cause code value alerts you that something is wrong with your ISDN connection. A cause code value applies to 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. |
| Field | Definition | ||
|---|---|---|---|
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 increments 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 increments whenever one of the following conditions occurs:
| ||
Called Party Events | Indicates the number of Called Party Responsible For Unsuccessful Call messages transmitted from this interface. This counter increments 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:
| ||
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 increments 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 following cause code values:
| ||
Unavailable Routes | Number of Route Unavailability messages transmitted from this interface. This counter increments 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 Resources | Number of Resource Unavailability messages transmitted from this interface. This counter increments 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:
| ||
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. | ||
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. | ||
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, follow these steps:
The SONET Interface Performance window appears (Figure 8-15).
Step 2 From the list boxes at the left, select the relevant chassis, card, and SONET interface.
The current performance information for the selected SONET interface appears.
The SONET Interface Performance window contains four tabs:
Table 8-15 defines the fields that are in the SONET Interface Performance window—Section tab (see Figure 8-15).
| Field | Definition |
|---|---|
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 contains two areas—Line and Far End Line (Figure 8-16).
Table 8-16 defines the fields that are in the Line tab. The Line and Far End Line areas contain the same fields.
| Field | Definition |
|---|---|
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 contains two areas—Path and Far End Path (Figure 8-17).
Table 8-17 defines the fields that are in the Path tab. The Path and Far End Path areas contain the same fields.
| Field | Definition |
|---|---|
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 8-18).
Table 8-18 defines the fields that are in the Virtual Tributary tab. The Virtual Tributary and Far End Virtual Tributary areas contain the same fields.
| Field | Definition |
|---|---|
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 SDSL Performance window displays performance data for the SDSL interfaces.
To view the SDSL Performance window, follow these steps:
The SDSL Performance window appears (Figure 8-19).
Step 2 From the list boxes at the left, select the relevant chassis, card, and SDSL interface. The current performance information for the selected SDSL interface appears.
The SDSL Performance window contains four areas:
Table 8-19 defines the fields that are in the SDSL Performance window.
| Field | Definition |
|---|---|
Line Initializations | Number of line initializations that occurred during the preceding full-day interval. |
LOSQ Seconds | Number of LOSQ failures experienced by the STU-C since agent reset. |
Elapsed Time | Amount of time that has elapsed since the beginning of the current day. |
LOSQ Seconds | Number of LOSQ failures experienced by the STU-C since agent reset. |
Valid Intervals | Number of previous 15-minute intervals during which valid near-end performance data was collected. |
Line Initializations | Number of line initializations that occurred since the agent was last reset. |
Invalid Performance Intervals | Number of 15-minute intervals, in the range 0 to STU-C valid intervals, during which no near-end performance data was available. |
The Interface Performance window displays performance data for the flexiCAP interfaces.
To view the Interface Performance window, follow these steps:
The Interface Performance window appears (Figure 8-20).
Step 2 From the list boxes at the left, select the relevant chassis, card, and flexiCAP interface.
The current performance information for the selected flexiCAP interface appears.
The Interface Performance window contains two tabs—Performance (1) and Performance (2). These tabs are described in the following sections.
The Performance (1) tab (see Figure 8-20) contains three areas:
Table 8-20 defines the fields that are in these areas.
| Field | Definition | ||
|---|---|---|---|
Resets | Number of resets that have occurred. | ||
Transmitted Bandwidth Utilization | Percentage of bandwidth used in the outbound direction. | ||
Received Bandwidth Utilization | Percentage of bandwidth used in the incoming direction. | ||
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. | ||
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.
|
Figure 8-21 shows the Performance (2) tab.
Table 8-21 defines the fields that are in the Interface Performance window—Performance (2) tab.
| Field | Definition |
|---|---|
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 were 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 was full. |
CRC Errored Packets | Number of input packets that had cyclic redundancy checksum errors. |
The ATM Interface Performance window displays performance data for the flexiDMT interfaces.
To view the ATM Interface Performance window, follow these steps:
The ATM Interface Performance window appears (Figure 8-22).
Step 2 From the list boxes at the left, select the relevant chassis, card, and flexiDMT interface.
The current performance information for the selected flexiDMT interface appears.
|
Note The information provided by this window is identical to the information provided for an ATM interface on a 4DMT card. Refer to the "Viewing ATM Interface Performance Data" section. |
The Module Performance window displays current performance data for any selected NI-2 card or line card.
|
Note Module performance attributes displayed 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, follow these steps:
The Module Performance window appears (Figure 8-23).
Step 2 From the list boxes at the left, select the relevant chassis and card. The current performance information for the selected card appears.
The Module Performance window contains two areas—CPU Usage and Performance Logging. Table 8-22 defines the fields that are located in the Module Performance window.
| Field | Definition | ||
|---|---|---|---|
CPU Busy% | Shows the CPU put to use in terms of percentage. | ||
Average (1 min.) | Shows the percentage CPU usage averaged over the previous one-minute interval. | ||
Average (5 min.) | Shows the percentage CPU usage averaged over the previous five-minute interval. | ||
Start button | Click to begin performance polling on a specified card.
| ||
Stop button | Click to stop performance polling on a specified card. |
This chapter describes how to use the Performance Manager window to view historical data as well as current data in the form of a line chart, bar chart, or table. This chapter describes how to view performance data on the following objects:
You can open the Performance Manager within the Map Viewer (Viewer) window. After you open the Map Viewer window, perform the following steps:
The Performance window opens to the Line Chart tab, which is shown in Figure 8-24.
The DS3 Interface Performance window consists of three selection areas and three tabs. Choose the parameters you want from the selection areas.
Step 2 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 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 3 In the Time Period area, select the following time parameters:
Step 4 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 5 Click Refresh Screen. This 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).
Step 6 A line chart of the performance information you requested appears at the right. You can click any of the three tabs to display your data differently.
|
Note The performance information corresponds to the attribute raw values. 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-23 defines the options that are located in the Monitored Attributes list (see Figure 8-24).
| Option | Definition |
|---|---|
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 (see Figure 8-24) displays the retrieved data in a graphical format. 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 regarding 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 (see Figure 8-24) is shown as a bar chart with the retrieved data. Blue represents the values retrieved and red identifies any polled values missed.
The Table Display tab (see Figure 8-24) displays the data retrieved in a tabular format. 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.
|
Note A polling events key appears for a selection. |
When you deploy a DMT line card, four ATM over ADSL over DMT interfaces are created automatically. 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 the one desired in the Performance Manager list box.
You can open the Performance Manager within the Map Viewer (Viewer) window. After you open one of these windows, perform the following steps:
The DMT Performance window appears, with the Line Chart tab displayed by default (Figure 8-25).
The Performance Manager window consists of three areas and three tabs. Choose the parameters you want from the selection areas.
Step 2 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 3 In the Time Period area, select the following time parameters.
Step 4 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 5 Click Refresh Screen. This 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 attribute raw values. 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 Aug 29 08:49:18 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.