Table of Contents

Viewing Interface Performance

Performance (1) Tab
Performance (2) Tab

Viewing DS3 Interface Performance Data

Performance Tab

Viewing ADSL Interface Performance Data

Line Performance (1) Tab
Line Performance (2) Tab
Fast Channel Performance (1) Tab
Fast Channel Performance (2) Tab
Interleave Channel Performance (1) Tab
Interleave Channel Performance (2) Tab

Viewing ATM Interface Performance Data
Viewing SONET Interface Performance Data

Section Tab
Line Tab
Path Tab
Virtual Tributary Tab

Viewing Module Performance Data
Viewing Historical Performance Data

Viewing DS3 or OC-3 Interface Performance Data

Monitored Attributes Option Definitions
Line Chart Tab
Bar Chart Tab
Table Display Tab
Missed Polls

Viewing ATM over ADSL over DMT Interface Performance Data

Viewing Current and Historical Performance Data

This chapter describes how to use the Performance Manager window to view real-time, current performance information within 10-second polled intervals on standard dialog windows for interfaces and cards. This chapter also describes how to view historical performance data using the Performance Manager window.

This chapter includes the following sections:

• Viewing Interface Performance

• Viewing DS3 Interface Performance Data

• Viewing ADSL Interface Performance Data

• Viewing ATM Interface Performance Data

• Viewing SONET Interface Performance Data

• Viewing Module Performance Data

• Viewing Historical Performance Data

Viewing Interface Performance

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 at the 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 8-2) displays two tabs—Performance (1), and Performance (2).

Performance (1) Tab

The Performance (1) tab displays three areas:

• General Information

• Packets/Octets Statistics

• Performance Logging

Table 8-1 defines the details that are located in the Performance (1) tab.

Table 8-1: Interface Performance Window—Performance (1) Tab Detail Definitions

Detail	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. Note   Performance logging logs data that can be displayed using the Performance Manager window.

Performance (2) Tab

Table 8-2 defines the details that are located in the Performance (2) tab.
Table 8-2: Interface Performance Window—Performance (2) Tab Detail Definitions

Detail	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 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.

Viewing DS3 Interface Performance Data

The DS3 Interface Performance window displays performance data for the DS3 port on the NI-2 card.

The DS3 Interface Performance window appears (Figure 8-3).

Performance Tab

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 Performance tab.

Table 8-3: DS3 Interface Performance Window—Field Definitions

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	Number of the far end unavailable seconds encountered by the port interface.

Viewing ADSL Interface Performance Data

To view the ADSL Interface Performance data 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.

Line Performance (1) Tab

The Line Performance (1) tab window contains two areas—Agent Reset and Current 15 Minutes. Table 8-4 defines the fields for these areas.

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.

Table 8-4: ADSL Performance Window—Line Performance (1) Tab Field Definitions

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.

Line Performance (2) Tab

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.

Table 8-5: Line Performance (2) Tab Field Definitions

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.

Fast Channel Performance (1) Tab

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.

Table 8-6: Fast Channel Performance (1) Tab Field Definitions

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.

Fast Channel Performance (2) Tab

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.

Table 8-7: Fast Channel Performance (2) Tab Field Definitions

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.
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.

Interleave Channel Performance (1) Tab

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 located in the Interleave Channel Performance (1) tab.

Table 8-8: Interleave Channel Performance (1) Tab Field Definitions

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.

Interleave Channel Performance (2) Tab

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 located in the Interleave Channel Performance (2) tab.

Table 8-9: Interleave Channel Performance (2) Tab Fields Definitions

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.

Viewing ATM Interface Performance Data

To view the ATM Interface Performance data window, follow these steps:

The ATM 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 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 at the right.

---

The Performance tab contains four areas—Transmitted, Received, Connection Established, SSCOP.

---

Note   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.

---

Table 8-10 defines the fields of the Performance tab.

Table 8-10: ATM Interface Performance Window—Performance Tab Field Definitions

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 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: Expiry of any network timer Receipt of a Release or Release Complete message Recovery on timer expiry
Called Party Events	Indicates the 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 8-11. Note   A cause code value alerts you that something is wrong with your ISDN connection. 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.
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 cause code values listed in Table 8-12. Note   These cause code values apply to both UNI Version 3.0 and UNI Version 3.1.
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 8-13. Note   These cause code values apply to both UNI Version 3.0 and UNI Version 3.1.
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 8-14. Note   These cause code values apply to both UNI 3.0 and UNI 3.1
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: SSCOP Connection Disconnect Counter—The abnormal occurrence of the event is characterized by the expiry 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 expiries 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—Occurs upon receipt of a BGN PDU or RESYNC PDU.

Table 8-11 defines the cause code values for the called party in the Performance window.

Table 8-12 defines the cause code values for the calling party in the Performance window.

Table 8-12: Cause Code Values for Calling Party Events

Cause Code Value	Definition
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)

Table 8-13 defines the cause code values for the unavailable routes in the Performance window.

Table 8-13: Cause Code Values for Unavailable Routes

Cause Code Value	Definition
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.

---

Table 8-14 defines the cause code values for the unavailable resources in the Performance window.

Table 8-14: Cause Code Values for Unavailable Resources

Cause Code Value	Definition
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

Viewing SONET Interface Performance Data

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 1   In the Map Viewer window, within the CDM Manager view, right-click a NI-2 card and select Cisco DSL Manager > Physical > Interface > SONET > Performance.

The SONET Interface Performance window appears (Figure 8-11).

Section Tab

Table 8-15 defines the fields that are in the Section.

Table 8-15: SONET Interface Performance Window—Section Tab Field Definitions

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.

Line Tab

The Line tab contains two areas—Line and Far End Line (Figure 8-12).

Table 8-16 defines the fields that are located in the Line tab.

Table 8-16: SONET Interface Performance Window—Line Tab Field Definitions

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.

Path Tab

The Path tab contains two areas—Path and Far End Path (Figure 8-13).

Table 8-17 defines the fields that are located in the Path tab.

Table 8-17: SONET Interface Performance Window—Path Tab Field Definitions

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.

Virtual Tributary Tab

The Virtual Tributary tab contains two areas—Virtual Tributary and Far End Virtual Tributary (Figure 8-14).

Table 8-18 defines the fields that are located in the Virtual Tributary tab.

Table 8-18: SONET Interface Performance Window—Virtual Tributary Tab Field Definitions

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.

Viewing Module Performance Data

The Module Performance window displays current performance data for a selectedNI-2 card or DMT line card.

---

Note   Module performance fields 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:

---

Step 1   In the Map Viewer window, within the CDM Manager view, right-click a chassis, NI-2, or DMT object and select Cisco DSL Manager > Physical > Module > Performance.

The Module Performance window appears (Figure 8-15).

The Module Performance window contains two areas—CPU Usage and Performance Logging. Table 8-15 defines the details that are located in the Performance tab.
Table 8-19: Module Performance Window—Performance Tab Detail Definitions

Detail	Definition
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.
Start	Begin 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.
Stop	End performance polling on a specified card.

Viewing Historical Performance Data

This section 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 section describes how to view DS3 or OC-3 interface performance data and how to view ATM over ADSL over DMT interface performance data.

Viewing DS3 or OC-3 Interface Performance Data

You can open the Performance Manager within the Map Viewer (Viewer) window. After you open the Map Viewer window, perform the following steps:

Step 2   Choose Tools > Performance Manager. The Performance window appears, with the Line Chart tab displayed by default (Figure 8-16).

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 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.

In the Time Period area, select the time parameters.

Step 4   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 5   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 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 check box to view the data from the selected start date to the current time. By selecting this option, you do not need to update the End Date and Time fields.

Step 7   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 check box 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 8   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 9   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 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.

---

---

Monitored Attributes Option Definitions

Table 8-20 defines the options that are located in the Monitored Attributes list (see Figure 8-16).

Table 8-20: DS3 Interface Performance Window—Monitored Attributes Option Definitions

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.

Line Chart Tab

The Line Chart tab displays the retrieved data in a graphical format (see Figure 8-16). 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.

Bar Chart Tab

The information on this tab is shown as a bar chart with the retrieved data (see Figure 8-16). Blue represents the values retrieved and red identifies any polled values missed.

Table Display Tab

This tab displays the data retrieved in a tabular format (see Figure 8-16). 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.

Missed Polls

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 start 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.

---

Viewing ATM over ADSL over DMT Interface Performance Data

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.

The Performance Manager window consists of three left areas, and three tabbed sections at right. Select the parameters you want from the left 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.

In the Time Period area, select the time parameters.

Step 3   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 4   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 check box 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 5   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 6   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 check box 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 7   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 8   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 when Now is selected or when 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 9   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: Thu Aug 31 11:05:27 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.