Chapter 8, Performance Monitoring

Performance-monitoring parameters (PMs) are used by service providers to gather, store, threshold, and report performance data for early detection of problems. In this chapter, PM parameters and concepts are defined for both electrical cards and optical cards.

For information about Ethernet PMs, see Chapter 9, "Ethernet Operation." Additional PM information can also be found under Digital transmission surveillance, in Telcordia's GR-1230-CORE, GR-820-CORE, and GR-253-CORE documents and the ANSI document entitled Digital Hierarchy - Layer 1 In-Service Digital Transmission Performance Monitoring.

8.1 Using the Performance Monitoring Screen

Table 8-1 Reference Topics for Performance Monitoring
Reference Topics
Using the Performance Monitoring Screen
Intermediate-Path Performance Monitoring Reference
Pointer Justification Count Reference
XTC DS1 Performance Monitoring Parameters
XTC DS3 Card Performance Monitoring Parameters
OC-3 Card Performance Monitoring Parameters
OC-12 Card Performance Monitoring Parameters
OC-48 Card Performance Monitoring Parameters

The following sections describe how to use basic screen elements such as tabs, menus, and informational columns. Figure 8-1 shows the Performance tab of Cisco Transport Controller (CTC) card-level view.

8.1.1 Viewing PMs

Before you view PMs, be sure you have created the appropriate circuits and provisioned the card according to your specifications. For information about circuit creation and card provisioning, see "Circuits and Tunnels" and Chapter 7, "Card Provisioning."

Note Rows relating directly to a card port are always present. Rows relating to an STS or virtual tunnel (VT) carried on the port appear at the time of circuit creation.

Procedure: View PM s

Step 1

Open the desired electrical or optical card. Double-click the card graphic in the main (node) view or right-click the card and select Open Card. (Clicking a card once only highlights the card.)

Step 3

View the PM parameter names that appear on the left portion of the screen in the Param column. The parameter numbers appear on the right portion of the screen in the Curr (current) and Prev (previous) columns.

8.1.2 Changing the Screen Intervals

Changing the screen view allows you to view PMs in 15-minute intervals or 24-hour periods. Figure 8-2 shows the time interval buttons on the Performance Monitoring screen. Thirty-three 15-minute periods and two one-day periods of performance monitoring can be displayed. Each period is displayed in one column. The 15-minute periods are anchored to the system clock quarter-hour marks. The one-day periods are anchored to the system clock one-day periods.

Note White fields with data indicate the number is applicable to the card. White fields without data indicate the field is inapplicable to the card. Yellow fields with data indicate that the field is applicable, but the data contained there is invalid.

Performance-monitoring data for OC-n cards is refreshed on entry to the performance-monitoring pane, or when the signal type is changed. It is not refreshed for Ethernet cards. Data can also refreshed by clicking the Refresh button ( Figure 8-2), or by choosing an auto-refresh time interval.

Note Choosing an auto-refresh period does not immediately refresh the data. The user must click the Refresh button, or select an auto-refresh period when changing the period, end, or monitored interface.

Note In a 1:1 or 1:n protection scheme, protection data is only available for the working or protect active card. The data is displayed in the working card performance-monitoring pane. In a 1+1 protection scheme, data is available for the working and protect active and standby cards. The data is displayed on each card pane.

Procedure: Select Fifteen-Minute PM Intervals on the Performance Monitoring Screen

Step 1

Open the electrical or optical card of choice. Double-click the card graphic in the main (node) view or right-click the card and select Open Card. (Clicking a card once highlights the card only.)

Step 4

Click the Refresh button. Performance-monitoring parameters display in 15-minute intervals synchronized with the time of day.

Step 5

View the Current column to find PM counts for the current 15-minute interval.

Each monitored performance parameter has corresponding threshold values for the current time period. If the value of the counter exceeds the threshold value for a particular 15-minute interval, a threshold crossing alert (TCA) will be raised. The value represents the counter for each specific performance-monitoring parameter.

Note

A TCA is a transient event. It is documented in the History pane if the Show Events check box is selected.

Step 6

View the Prev-N columns to find PM counts for the preceding 15-minute intervals.

Note If a complete 15-minute interval count is not possible, the value displays with a yellow background. An incomplete or incorrect count can be caused by changing node timing settings, changing the time zone settings on CTC, replacing a card, resetting a card, or by changing port states. When a complete count occurs, the subsequent 15-minute interval appears with a white background.

Procedure: Select Twenty-Four Hour PM Intervals on the Performance Monitoring Screen

Step 1

Open the electrical or optical card of choice. Double-click the card graphic in the main (node) view or right-click the card and select Open Card. (Clicking a card once highlights the card only.)

Step 4

Click the Refresh button. Performance monitoring displays in 24-hour periods synchronized with the time of day.

Step 5

View the Current column to find PM counts for the current 24-hour period.

Each monitored performance parameter has corresponding threshold values for the current time period. If the value of the counter exceeds the threshold value for a particular 24-hour period, a TCA will be raised. The value represents the counter for each specific performance-monitoring parameter.

Step 6

View the Prev columns to find PM counts for the preceding 24-hour period.

Note If a complete count over a 24-hour period is not possible, the value displays with a yellow background. An incomplete or incorrect count can be caused by changing node timing settings, changing the time zone settings on CTC, replacing a card, resetting a card, or by changing port states. When a complete count occurs, the subsequent 24-hour period appears with a white background.

Procedure: Clearing PM Data on the Performance Monitoring Screen

Step 2

Click the Clear button. The Clear Statistics dialog box appears. Click one of three options:

•

Selected interfaces. This refers to the port-level data, STS-level data, and VT-level data. Choosing this option will clear the entire set of displayed data at the NE level, rather than the selected row.

•

All interfaces on port [1]. Choosing this option will clear data for all interfaces at the NE level, including those not currently displayed, such as the ends, periods, and VTs.

•

All interfaces on card. Choosing this option will only clear the interfaces that apply to the selected card at the NE.

Step 3

Click OK. Clearing the data will invalidate all data for the current 15-minute period because the data does not reflect the full period.

Step 4

To cancel changes, click Cancel. bsequent 24-hour period appears with a white background.

8.1.3 Viewing Near-End and Far-End PMs

Select the Near End or Far End button depending on the PMs you wish to view. Only cards that allow both near-end and far-end monitoring have these buttons as an option. Figure 8-3 shows the Near End and Far End buttons on the Performance Monitoring screen.

Procedure: Select Near-End PMs on the Performance Monitoring Screen

Step 1

Open the electrical or optical card of choice. Double-click the card graphic in the main (node) view or right-click the card and select Open Card. (Clicking a card once highlights the card only.)

Step 4

Click the Refresh button. All PMs occurring for the selected card on the incoming signal are displayed.

Procedure: Select Far-End PMs on the Performance Monitoring Screen

Step 1

Open the electrical or optical card of choice. To do so, double-click the card graphic in the main (node) view or right-click the card and select Open Card. (Clicking a card once highlights the card only.)

Step 4

Click the Refresh button. All PMs recorded by the far-end node for the selected card on the outgoing signal are displayed.

8.1.4 Using the Signal-Type Menu

Use the signal-type menus to monitor PMs for near-end or far-end signals on a selected port. Different signal-type menus appear depending on the card type and the circuit type. The appropriate types (DS1, DS3, VT path, STS path, OCn section, line) appear based on the card. For example, the XTC-28-3 has DS3, DS1, VT path, and STS path PMs. Figure 8-4 shows the signal-type menus on the Performance Monitoring screen for an OC48 card.

Procedure: Select Signal-Type Menus on the Performance Monitoring Screen

Step 1

Open the electrical or optical card of choice. Double-click the card graphic in the main (node) view or right-click the card and select Open Card. (Clicking a card once highlights the card only.)

Step 3

Click the signal-type menu. (For example, the OC48 card has a menu labeled STS.)

8.1.5 Using the Baseline Button

In Software R3.0 and higher, the Baseline button located on the far right of the screen clears the PM count displayed in the Current column, but does not clear the PM count on the card. The value is changed in the CTC software, but is not changed for the NE. When the current 15-minute or 24-hour time interval expires or the screen view changes, the total number of PM counts on the card and on the screen appear in the appropriate column, decrementing from the values at the time the command is performed.

The baseline values are discarded if you select a new port, interval, near-end, far-end, STS, or if you change views to a different screen and then return to the Performance Monitoring screen. The Baseline button enables you to easily see how quickly PM counts are rising without having to perform calculations. Figure 8-5 shows the Baseline button on the Performance Monitoring screen.

Procedure: Use the Baseline Button on the Performance Monitoring Screen

Step 1

Open the electrical or optical card of choice. Double-click the card graphic in the main (node) view or right-click the card and select Open Card. (Clicking a card once highlights the card only.)

8.1.6 Using the Clear Button

The Clear button located on the far right of the Performance Monitoring screen clears certain PM counts depending on the option selected. Figure 8-6 shows the Clear button on the Performance Monitoring screen.

Procedure: Use the Clear Button on the Performance Monitoring Screen

Step 1

Open the electrical or optical card of choice. Double-click the card graphic in the main (node) view or right-click the card and select Open Card. (Clicking a card once highlights the card only.)

•

Selected Interfaces: Clearing selected interfaces erases all PM counts associated with the selected radio buttons at the NE level. This refers to the port-level data, STS-level data, and VT-level data. Choosing this option will clear the entire set of displayed data at the NE level, rather than the selected row.

•

All interfaces on port x: Choosing this option will clear data for all interfaces at the NE level, including those not currently displayed, such as the ends, periods, and VTs.

•

All interfaces on card: Choosing this option will only clear the interfaces that apply to the selected card at the NE.

Threshold Reference

Thresholds are used to set error levels for each PM. You can program PM threshold ranges from the Provisioning > Threshold tabs on the card view. For procedures on provisioning card thresholds, such as line, path, and SONET thresholds, see the Card Provisioning chapter.

During the accumulation cycle, if the current value of a performance monitoring parameter reaches or exceeds its corresponding threshold value, a TCA is generated by the node and sent to CTC. TCAs provide early detection of performance degradation. When a threshold is crossed, the node continues to count the errors during a given accumulation period. If 0 is entered as the threshold value, the performance monitoring parameter is disabled. Figure 8-7 shows the Provisioning > Threshold tabs for an OC-48 card.

Change the threshold if the default value does not satisfy your error monitoring needs. For example, customers with a critical DS1 installed for 911 calls must guarantee the best quality of service on the line; therefore, they lower all thresholds so that the slightest error raises a TCA.

8.2 Intermediate-Path Performance Monitoring Reference

Intermediate-path-performance monitoring (IPPM) allows transparent monitoring of a constituent channel of an incoming transmission signal by a node that does not terminate that channel. In addition to the path-terminating equipment (PTE) on the XTC, such as DS1s and DS3s, an ONS 15327 can terminate optical lines. Table 8-2 shows ONS 15327 cards that are considered LTEs. Figure 8-8 shows the Provisioning > STS tabs for an OC-3 card.

Software R3.0 and higher allows LTE cards to monitor near-end PM data on individual STS payloads by enabling IPPM. After enabling IPPM provisioning on the line card, service providers can monitor large amounts of STS traffic through intermediate nodes, thus making troubleshooting and maintenance activities more efficient.

Table 8-2 Traffic Cards That Terminate the Line (LTEs)
Line Terminating Equipment
OC3 IR 1310	OC48 IR 1310
OC12 IR 1310	OC48 LR 1550
OC12 LR 1550

IPPM occurs only on STS paths that have IPPM enabled, and TCAs are raised only for PM parameters on the selected IPPM paths. The monitored IPPMs are STS CV-P, STS ES-P, STS SES-P, STS UAS-P, and STS FC-P. For more information about enabling IPPM, see Intermediate-Path Performance Monitoring Reference.

The ONS 15327 performs IPPM by examining the overhead in the monitored path and by reading all of the near-end path PMs in the incoming direction of transmission. The IPPM process allows the path signal to pass bidirectionally through the node completely unaltered.

For detailed information about specific PMs, locate the card name in the following sections and review the appropriate definition.

8.3 Pointer Justification Count Reference

Pointers are used to compensate for frequency and phase variations. Pointer justification counts indicate timing errors on SONET networks. When a network is out of synchronization, signal jitter and signal wander occur on the transported signal. Excessive wander can cause terminating equipment to slip. It also causes slips at the SDH and PDH boundaries.

Slips cause different effects in service. Voice service has intermittent audible clicks. Compressed voice technology has short transmission errors or dropped calls. Fax machines lose scanned lines or experience dropped calls. Digital video transmission has distorted pictures or frozen frames. Encryption service loses the encryption key, causing data to be retransmitted.

Pointers provide a way to align the phase variations in STS and VT payloads. The STS payload pointer is located in the H1 and H2 bytes of the line overhead. Clocking differences are measured by the offset in bytes from the pointer to the first byte of the STS synchronous payload envelope (SPE) called the J1 byte. Clocking differences that exceed the normal range of 0 to 782 can cause data loss.

Figure 8-9 shows pointer justification count parameters on the Performance Monitoring screen. You can enable PPJC and NPJC performance monitoring parameters for LTE cards. See Table 8-2 for a list of Cisco ONS 15327 LTE cards.

There are positive (PPJC) and negative (NPJC) pointer justification count parameters. PPJC is a count of path-detected (PPJC-Pdet) or path-generated (PPJC-Pgen) positive pointer justifications. NPJC is a count of path-detected (NPJC-Pdet) or path-generated (NPJC-Pgen) negative pointer justifications depending on the specific PM name.

A consistent pointer justification count indicates clock synchronization problems between nodes. A difference between the counts means the node transmitting the original pointer justification has timing variations with the node detecting and transmitting this count. Positive pointer adjustments occur when the frame rate of the SPE is too slow in relation to the rate of the STS 1.

On CTC, the count fields for PPJC and NPJC PMs appear white and blank unless they are enabled on the Provisioning > Line tabs. Figure 8-10 shows the PJStsMon# menu on the Provisioning screen. Pointer justification is only enabled for one STS at a time.

8.4 Performance Monitoring for Electrical Cards

The following sections define performance monitoring parameters for the XTC DS1 and XTC DS3 electrical cards.

8.4.1 XTC DS1 Performance Monitoring Parameters

Figure 8-11 shows the signal types that support far-end PMs. Far-end VT and STS path-performance monitoring is supported for the DS1 card. Far-end DS1 path-performance monitoring is not supported for the DS1 card. Figure 8-12 shows where overhead bytes detected on the ASICs produce performance monitoring parameters for the DS1 cards.

Note The XX in the illustration above represents all PMs listed below with the given prefix and/or suffix.

Table 8-3 DS1 Line PMs for the XTC DS1 Cards
Parameter	Definition
DS1 CV-L	Code Violation Line (CV-L) indicates the number of coding violations occurring on the line. This parameter is a count of bipolar violations (BPVs) and excessive zeros (EXZs) occurring over the accumulation period.
DS1 ES-L	Errored Seconds Line (ES-L) is a count of the seconds containing one or more anomalies (bipolar violations + excessive zeros, or BPV + EXZ) and/or defects (loss of signal) on the line.
DS1 SES-L	Severely Errored Seconds Line (SES-L) is a count of the seconds containing more than a particular quantity of anomalies (bipolar violations + excessive zeros, or BPV + EXZ > 1544) and/or defects on the line.
DS1 LOSS-L	Loss of Signal Seconds Line (LOSS-L) is a count of one-second intervals containing one or more Loss of Signal (LOS) defects.

Table 8-4 DS1 Receive Path PMs for the XTC DS1 Cards
Parameter	Definition
Note Under the Provisioning > Threshold tab, the DS1 cards have user-defined thresholds for the DS1 receive (Rx) path PMs. In the Threshold tab they are displayed as Code Violation (CV), Errored Seconds (ES), Severely Errored Seconds (SES), Unavailable Seconds (UAS), Alarm Indication Signal (AISS), and Seconds Frame/Alarm Indication Signal (SAS) without the Rx prefix.
DS1 Rx AISS-P	Receive Path Alarm Indication Signal (Rx AISS-P) means an alarm indication signal occurred on the receive end of the path. This parameter is a count of seconds containing one or more Alarm Indication Signal (AIS) defects.
DS1 Rx CV-P	Receive Path Code Violation (Rx CV-P) means a coding violation occurred on the receive end of the path. For DS1-ESF paths, this parameter is a count of detected CRC-6 errors. For the DS1-SF paths, the Rx CV-P parameter is a count of detected frame-bit errors (FE).
DS1 Rx ES-P	Receive Path Errored Seconds (Rx ES-P) is a count of the seconds containing one or more anomalies and/or defects for paths on the receive end of the signal. For DS1-ESF paths, this parameter is a count of one-second intervals containing one or more CRC-6 errors, or one or more CS events, or one or more Severely Errored Frame (SEF) or Alarm Indication Signal (AIS) defects. For DS1-SF paths, the Rx ES-P parameter is a count of one-second intervals containing one or more frame-bit errors (FE) events, or one or more CS events, or one or more SEF or AIS defects.
DS1 Rx SAS-P	Receive Path Severely Errored Seconds Frame/Alarm Indication Signal (Rx SAS-P) is a count of one-second intervals containing one or more SEFs or one or more Alarm Indication Signal (AIS) defects on the receive end of the signal.
DS1 Rx SES-P	Receive Path Severely Errored Seconds (Rx SES-P) is a count of the seconds containing more than a particular quantity of anomalies and/or defects for paths on the receive end of the signal. For the DS1-ESF paths, this parameter is a count of seconds when 320 or more CRC-6 errors or one or more Severely Errored Frame (SEF) or Alarm Indication Signal (AIS) defects occurred. For DS1-SF paths, a Severely Errored Second (SES) is a second containing either the occurrence of four frame-bit errors (FEs) or one or more SEF or AIS defects.
DS1 Rx UAS-P	Receive Path Unavailable Seconds (Rx UAS-P) is a count of one-second intervals when the DS1 path is unavailable on the receive end of the signal. The DS1 path is unavailable at the onset of 10 consecutive seconds that qualify as Severely Errored Seconds (SESs), and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as Severely Errored Seconds Path (SES-Ps). The ten seconds with no SES-Ps are excluded from unavailable time.

Table 8-5 DS1 Transmit Path PMs for the XTC DS1 Cards
Parameter	Definition
Note Under the Performance tab, the displayed DS1 Tx path PM values are based on calculations performed by the card and therefore have no user-defined thresholds. The tab is labeled "Elect[rical] Path Threshold."
DS1 Tx AIS-P	Transmit Path Alarm Indication Signal (Tx AIS-P) means an alarm indication signal occurred on the transmit end of the path. This parameter is a count of seconds containing one or more Alarm Indication Signal (AIS) defects.
DS1 Tx CV-P	Transmit Path Code Violation (Tx CV-P) means a coding violation occurred on the transmit end of the path. For DS1-ESF paths, this parameter is a count of detected CRC-6 errors. For the DS1-SF paths, the Tx CV-P parameter is a count of detected frame-bit errors (FEs).
DS1 Tx ES-P	Transmit Path Errored Seconds (Tx ES-P) is a count of the seconds containing one or more anomalies and/or defects for paths on the transmit end of the signal. For DS1-ESF paths, this parameter is a count of one-second intervals containing one or more CRC-6 errors, or one or more CS events, or one or more Severely Errored Frame (SEF) or Alarm Indication Signal (AIS) defects. For DS1-SF paths, the Tx ES-P parameter is a count of one-second intervals containing one or more frame bit error (FE) events, or one or more CS events, or one or more SEF or AIS defects.
DS1 Tx SAS-P	Transmit Path Severely Errored Seconds Frame/Alarm Indication Signal (Tx SAS-P) is a count of one-second intervals containing one or more SEFs or one or more Alarm Indication Signal (AIS) defects on the transmit end of the signal.
DS1 Tx SES-P	Transmit Path Severely Errored Seconds (Tx SES-P) is a count of the seconds containing more than a particular quantity of anomalies and/or defects for paths on the transmit end of the signal. For the DS1-ESF paths, this parameter is a count of seconds when 320 or more CRC-6 errors or one or more Severely Errored Frame (SEF) or Alarm Indication Signal (AIS) defects occurred. For DS1-SF paths, a Severely Errored Second (SES) is a second containing either the occurrence of four frame-bit errors (FEs) or one or more SEF or AIS defects.
DS1 Tx UAS-P	Transmit Path Unavailable Seconds (Tx UAS-P) is a count of one-second intervals when the DS1 path is unavailable on the transmit end of the signal. The DS1 path is unavailable at the onset of 10 consecutive seconds that qualify as Severely Errored Seconds (SESs), and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as SESs. The ten seconds with no SESs are excluded from unavailable time.

Table 8-6 VT Path PMs for the XTC DS1 Cards
Parameter	Definition
CV-V	Code Violation VT Layer (CV-V) is a count of the B IP errors detected at the VT path layer. Up to two B IP errors can be detected per VT superframe, with each error incrementing the current CV-V second register.
ES-V	Errored Seconds VT Layer (ES-V) is a count of the seconds when at least one VT Path B IP error was detected. An Alarm Indication Signal VT Layer (AIS-V) defect (or a lower-layer, traffic-related, near-end defect) or a Loss of Pointer VT layer (LOP-V) defect can also cause an ES-V.
SES-V	Severely Errored Seconds VT Layer (SES-V) is a count of seconds when K (600) or more VT Path B IP errors were detected. SES-V can also be caused by an Alarm Indication Signal VT Layer (AIS-V) defect (or a lower-layer, traffic-related, near-end defect) or a Loss of Pointer VT layer (LOP-V) defect.
UAS-V	Unavailable Second VT Layer (UAS-V) is a count of the seconds when the VT path is considered unavailable. A VT path becomes unavailable at the onset of ten consecutive seconds that qualify as Severely Errored Seconds VT Layer (SES-Vs), and continues to be unavailable until the onset of ten consecutive seconds occur that do not qualify as SES-Vs.

Table 8-7 Far-End VT Path PMs for the XTC DS1 Card
Parameter	Definition
CV-VFE	Far-End VT Path Coding Violations (CV-VFE) is a count of the number of B IP errors detected by the far-end VT path-terminating equipment (PTE) and reported back to the near-end VT PTE using the REI-V indication in the VT path overhead. Only one B IP error can be indicated per VT superframe using the REI-V bit. The current CV-VFE second register is incremented for each B IP error indicated by the incoming REI-V.
ES-VFE	Far-End VT Path Errored Seconds (ES-VFE) is a count of the seconds when at least one VT path B IP error was reported by the far-end VT PTE, or a one-bit RDI-V defect was present.
SES-VFE	Far-End VT Path Severely Errored Seconds (SES-VFE) is a count of the seconds when K (600) or more VT path B IP errors were reported by the far-end VT PTE or a one-bit RDI-V defect was present.
UAS-VFE	Far-End VT Path Unavailable Seconds (UAS-VFE) is a count of the seconds when the VT path is unavailable at the far-end. A VT path is considered unavailable at the onset of ten consecutive seconds that qualify as Far-End VT Path Severely Errored Seconds (SES-VFEs), and continues to be considered unavailable until the onset of 10 consecutive seconds that do not qualify as SES-VFEs.

Table 8-8 SONET Path PMs for the XTC DS1 Cards
Parameter	Definition
STS CV-P	Near-End STS Path Coding Violations (STS CV-P) is a count of B IP errors detected at the STS path layer (i.e., using the B3 byte). Up to eight B IP errors can be detected per frame, with each error incrementing the current CV-P second register.
STS ES-P	Near-End STS Path Errored Seconds (STS ES-P) is a count of the seconds when at least one STS path B IP error was detected. An AIS-P defect (or a lower-layer, traffic-related, near-end defect) or an LOP-P defect can also cause an STS ES-P.
STS FC-P	Near-End STS Path Failure Counts (STS FC-P) is a count of the number of near-end STS path failure events. A failure event begins when an AIS-P failure, an LOP-P failure, a UNEQ-P, or a TIM-P failure is declared. A failure event also begins if the STS PTE that is monitoring the path supports ERDI-P for that path. The failure event ends when these failures are cleared.
STS SES-P	Near-End STS Path Severely Errored Seconds (STS SES-P) is a count of the seconds when K (2400) or more STS path B IP errors were detected. An AIS-P defect (or a lower-layer, traffic-related, near-end defect) or an LOP-P defect can also cause an STS Severely Errored Seconds Path (SES-P).
STS UAS-P	Near-End STS Path Unavailable Seconds (UAS-P) is a count of the one-second intervals when the STS path is unavailable. An STS path is unavailable at the onset of ten consecutive seconds that qualify as Severely Errored Seconds Path (SES-Ps), and continues to be unavailable until the onset of ten consecutive seconds that do not qualify as SES-Ps. The ten seconds with no SES-Ps are excluded from unavailable time.

8.4.2 XTC DS3 Card Performance Monitoring Parameters

Figure 8-13 shows the signal types that support far-end PMs. Figure 8-14 shows where overhead bytes detected on the ASICs produce performance monitoring parameters for the XTC DS3 cards.

Note The XX in the illustration above represents all PMs listed below with the given prefix and/or suffix.

Table 8-9 Near-End DS3 Line PMs for the XTC DS3 Cards
Parameter	Definition
DS3 CV-L	Code Violation Line (CV-L) indicates the number of coding violations occurring on the line. This parameter is a count of bipolar violations (BPVs) and excessive zeros (EXZs) occurring over the accumulation period.
DS3 ES-L	Errored Seconds Line (ESL) is a count of the seconds containing one or more anomalies (bipolar violations + excessive zeros, or BPV + EXZ) and/or defects (loss of signal) on the line.
DS3 SES-L	Severely Errored Seconds Line (SES-L) is a count of the seconds containing more than a particular quantity of anomalies (bipolar violations + excessive zeros, or BPV + EXZ > 44) and/or defects on the line.
DS3 LOSS-L	Loss of Signal Seconds Line (LOSS-L) is a count of one-second intervals containing one or more Loss of Signal (LOS) defects.

Table 8-10 Near-End SONET Path PMs for the XTC DS3 Cards
Parameter	Definition
STS CV-P	Near-End STS Path Coding Violations (STS CV-P) is a count of B IP errors detected at the STS path layer (i.e., using the B3 byte). Up to eight B IP errors can be detected per frame; each error increments the current CV-P second register.
STS ES-P	Near-End STS Path Errored Seconds (STS ES-P) is a count of the seconds when at least one STS path B IP error was detected. An AIS-P defect (or a lower-layer, traffic-related, near-end defect) or an LOP-P defect can also cause an STS ES-P.
STS FC-P	Near-End STS Path Failure Counts (STS FC-P) is a count of the number of near-end STS path failure events. A failure event begins when an AIS-P failure, an LOP-P failure, a UNEQ-P, or a TIM-P failure is declared. A failure event also begins if the STS PTE that is monitoring the path supports ERDI-P for that path. The failure event ends when these failures are cleared.
STS SES-P	Near-End STS Path Severely Errored Seconds (STS SES-P) is a count of the seconds when K (2400) or more STS path B IP errors were detected. An AIS-P defect (or a lower-layer, traffic-related, near-end defect) or an LOP-P defect can also cause an STS Severely Errored Second Path (SES-P).
STS UAS-P	Near-End STS Path Unavailable Seconds (STS UAS-P) is a count of the one-second intervals when the STS path is unavailable. An STS path is unavailable at the onset of ten consecutive seconds that qualify as Severely Errored Seconds Path (SES-Ps), and continues to be unavailable until the onset of ten consecutive seconds that do not qualify as SES-Ps. The ten seconds with no SES-Ps are excluded from unavailable time.

8.5 Performance Monitoring for Optical Cards

The following sections define performance monitoring parameters and definitions for the OC-3, OC-12, and OC-48 cards.

8.5.1 OC-3 Card Performance Monitoring Parameters

Figure 8-15 shows where overhead bytes detected on the ASICs produce performance monitoring parameters for the OC-3 card.

Note For PM locations relating to protection switch counts, see the GR-253-CORE document.

Table 8-11 Near-End Section PMs for the OC-3 Card
Parameter	Definition
CV-S	Section Coding Violation (CV-S) is a count of B IP errors detected at the section-layer (i.e. using the B1 byte in the incoming SONET signal). Up to eight section B IP errors can be detected per STS-N frame, with each error incrementing the current CV-S second register.
ES-S	Section Errored Seconds (ES-S) is a count of the number of seconds when at least one section-layer B IP error was detected or a Severely Errored Frame (SEF) or Loss of Signal (LOS) defect was present.
SES-S	Section Severely Errored Seconds (SES-S) is a count of the seconds when K (see GR-253 for value) or more section-layer B IP errors were detected or a (Severely Errored Frame) SEF or Loss of Signal (LOS) defect was present.
SEFS-S	Section Severely Errored Framing Seconds (SEFS-S) is a count of the seconds when a Severely Errored Frame (SEF) defect was present. A (Severely Errored Frame) SEF defect is expected to be present during most seconds when a Loss of Signal (LOS) or Loss of Frame (LOF) defect is present. However, there can be situations when the SEFS-S parameter is only incremented based on the presence of the SEF defect.

Table 8-12 Near-End Line Layer PMs for the OC-3 Cards Card
Parameter	Definition
CV-L	Code Violation Line (CV-L) is a count of B IP errors detected at the line-layer (i.e. using the B2 bytes in the incoming SONET signal). Up to 8 x N B IP errors can be detected per STS-N frame; each error increments the current CV-L second register.
ES-L	Errored Seconds Line (ES-L) is a count of the seconds when at least one line-layer B IP error was detected or an AIS-L defect was present.
SES-L	Severely Errored Seconds Line (SES-L) is a count of the seconds when K (see GR-253-CORE for values) or more line-layer B IP errors were detected or an AIS-L defect was present.
UAS-L	Near-End Line Unavailable Seconds (UAS-L) is a count of the seconds when the line is considered unavailable. A line becomes unavailable at the onset of ten consecutive seconds that qualify as Severely Errored Seconds Line (SES-Ls), and continues to be unavailable until the onset of ten consecutive seconds occur that do not qualify as SES-Ls.
FC-L	Near-End Line Failure Count (FC-L) is a count of the number of near-end line failure events. A failure event begins when an AIS-L failure is declared or when a lower-layer traffic-related, near-end failure is declared. This failure event ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period where it begins.

Table 8-13 Near-End Protection-Switching PMs for the OC-3 Cards
Parameter	Definition
For information about Troubleshooting UPSR switch counts, see the alarm troubleshooting information in Chapter 14, "Alarm Troubleshooting". For information about creating circuits that perform a switch, see "Circuits and Tunnels."
PSC (1+1 protection)	In a 1+1 protection scheme for a working card, Protection Switching Count (PSC) is a count of the number of times service switches from a working card to a protection card plus the number of times service switches back to the working card. For a protection card, PSC is a count of the number of times service switches to a working card from a protection card plus the number of times service switches back to the protection card. The PSC PM is only applicable if revertive line-level protection switching is used. Note BLSR is not supported on the OC-3 card; therefore, the PSC-W, PSC-S and PSC-R PMs do not increment.
PSD	Protection Switching Duration (PSD) applies to the length of time, in seconds, that service is carried on another line. For a working line, PSD is a count of the number of seconds that service was carried on the protection line. For the protection line, PSD is a count of the seconds that the line was used to carry service. The PSD PM is only applicable if revertive line-level protection switching is used. Note BLSR is not supported on the OC-3 card; therefore, the Protection Switching Duration-Working (PSD-W), Protection Switching Duration-Span (PSD-S), and Protection Switching Duration-Ring (PSD-R) PMs do not increment.

Table 8-14 Near-End SONET Path H-Byte PMs for the OC-3 Card
Parameter	Definition
Note On CTC, the count fields for Positive Point Justification Count (PPJC) and Negative Pointer Justification Count (NPJC) PMs appear white and blank unless they are enabled on the Provisioning > Line tabs. See Pointer Justification Count Reference.
PPJC-Pdet	Positive Pointer Justification Count path-detected (PPJC-Pdet) is a count of the positive pointer justifications detected on a particular path on an incoming SONET signal.
NPJC-Pdet	Negative Pointer Justification Count path-detected (NPJC-Pdet) is a count of the negative pointer justifications detected on a particular path on an incoming SONET signal.
PPJC-Pgen	Positive Pointer Justification Count path-generated (PPJC-Pgen) is a count of the positive pointer justifications generated for a particular path to reconcile the frequency of the SPE with the local clock.
NPJC-Pgen	Negative Pointer Justification Count path-generated (NPJC-Pgen) is a count of the negative pointer justifications generated for a particular path to reconcile the frequency of the SPE with the local clock.

Table 8-15 Near-End SONET Path PMs for the OC-3 Card
Parameter	Definition
Note SONET path PMs will not count unless IPPM is enabled. For additional information, see the "Intermediate-Path Performance Monitoring Reference" section.
STS CV-P	Near-End STS Path Coding Violations (STS CV-P) is a count of B IP errors detected at the STS path layer (i.e., using the B3 byte). Up to eight B IP errors can be detected per frame; each error increments the current CV-P second register.
STS ES-P	Near-End STS Path Errored Seconds (STS ES-P) is a count of the seconds when one or more STS path B IP errors were detected. An AIS-P defect (or a lower-layer, traffic-related, near-end defect) or an LOP-P defect can also cause an STS ES-P.
STS FC-P	Near-End STS Path Failure Counts (STS FC-P) is a count of the number of near-end STS path failure events. A failure event begins with an AIS-P failure, an LOP-P failure, a UNEQ-P failure, or a TIM-P failure is declared, or if the STS PTE that is monitoring the path supports ERDI-P for that path. The failure event ends when these failures are cleared.
STS SES-P	Near-End STS Path Severely Errored Seconds (STS SES-P) is a count of the seconds when K (2400) or more STS path B IP errors were detected. An AIS-P defect (or a lower-layer, traffic-related, near-end defect) or an LOP-P defect can also cause an STS Severely Errored Seconds Path (SES-P).
STS UAS-P	Near-End STS Path Unavailable Seconds (STS UAS-P) is a count of the seconds when the STS path is considered unavailable. An STS path becomes unavailable at the onset of ten consecutive seconds that qualify as Severely Errored Seconds Path (SES-Ps), and continues to be unavailable until the onset of ten consecutive seconds that do not qualify as SES-Ps.

Table 8-16 Far-End Line Layer PMs for the OC-3 Card
Parameter	Definition
CV-L	Code Violation Line (CV-L) is a count of B IP errors detected by the far-end LTE and reported back to the near-end LTE using the REI-L indication in the line overhead. For SONET signals at rates below OC-48, up to 8 x N B IP errors per STS-N frame can be indicated using the REI-L. For OC-48 signals, up to 255 B IP errors per STS-N frame can be indicated. The current CV-L second register is incremented for each B IP error indicated by the incoming REI-L.
ES-L	Errored Seconds Line (ES-L) is a count of the seconds when at least one line-layer B IP error was reported by the far-end LTE or an RDI-L defect was present.
SES-L	Severely Errored Seconds Line (SES-L) is a count of the seconds when K (see GR-253-CORE for values) or more line-layer B IP errors were reported by the far-end LTE or an RDI-L defect was present.
UAS-L	UAS-L is a count of the seconds when the line is unavailable at the far end. A line becomes unavailable at the onset of ten consecutive seconds that qualify as SES-LFEs, and continues to be unavailable until the onset of ten consecutive seconds occur that do not qualify as SES-LFEs.
FC-L	FC-L is a count of the number of far-end line failure events. A failure event begins when RFI-L failure is declared, and it ends when the RFI-L failure clears. A failure event that begins in one period and ends in another period is counted only in the period where it began.

8.5.2 OC-12 Card Performance Monitoring Parameters

Figure 8-16 shows the signal types that support far-end PMs. Figure 8-17 shows where overhead bytes detected on the ASICs produce performance monitoring parameters for the OC-12 card.

Note PMs on the protect STS are not supported for BLSR. The XX in the illustration above represents all PMs listed below with the given prefix and/or suffix.

Note For PM locations relating to protection switch counts, see the GR-1230-CORE document.

Table 8-17 Near-End Section PMs for the OC-12 Card
Parameter	Definition
CV-S	CV-S is a count of B IP errors detected at the section-layer (i.e. using the B1 byte in the incoming SONET signal). Up to eight section B IP errors can be detected per STS-N frame; each error increments the current CV-S second register.
ES-S	ES-S is a count of the number of seconds when at least one section-layer B IP error was detected or a (Severely Errored Frame) SEF or Loss of Signal (LOS) defect was present.
SES-S	SES-S is a count of the seconds when K (see GR-253 for value) or more section-layer B IP errors were detected or a Severely Errored Frame (SEF) or Loss of Signal (LOS) defect was present.
SEFS-S	SEFS-S is a count of the seconds when a (Severely Errored Frame) SEF defect was present. An SEF defect is expected to be present during most seconds when a Loss of Signal (LOS) or Loss of Frame (LOF) defect is present. However, there may be situations when the SEFS-S parameter is only incremented based on the presence of an SEF defect.

Table 8-18 Near-End Line Layer PMs for the OC-12 Card
Parameter	Definition
CV-L	Code Violation Line (CV-L) is a count of B IP errors detected at the line-layer (i.e. using the B2 bytes in the incoming SONET signal). Up to 8 x N B IP errors can be detected per STS-N frame; each error increments the current CV-L second register.
ES-L	Errored Seconds Line (ES-L) is a count of the seconds when at least one line-layer B IP error was detected or an AIS-L defect was present.
SES-L	Severely Errored Seconds Line (SES-L) is a count of the seconds when K (see GR-253 for values) or more line-layer B IP errors were detected or an AIS-L defect was present.
UAS-L	UAS-L is a count of the seconds when the line is unavailable. A line becomes unavailable at the onset of ten consecutive seconds that qualify as Severely Errored Seconds Line (SES-Ls), and continues to be unavailable until the onset of ten consecutive seconds that do not qualify as SES-Ls.
FC-L	FC-L is a count of the number of near-end line failure events. A failure event begins when an AIS-L failure or a lower-layer traffic-related, near-end failure is declared. This failure event ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period where it begins.

Table 8-19 Near-End SONET Path H-byte PMs for the OC-12 Card
Parameter	Definition
Note On CTC, the count fields for Positive Point Justification Count (PPJC) and Negative Pointer Justification Count (NPJC) PMs appear white and blank unless they are enabled on the Provisioning > Line tabs. See Pointer Justification Count Reference.
PPJC-Pdet	Positive Pointer Justification Count path-detected (PPJC-Pdet) is a count of the positive pointer justifications detected on a particular path on an incoming SONET signal.
NPJC-Pdet	Negative Pointer Justification Count path-detected (NPJC-Pdet) is a count of the negative pointer justifications detected on a particular path on an incoming SONET signal.
PPJC-Pgen	Positive Pointer Justification Count path-generated (PPJC-Pgen) is a count of the positive pointer justifications generated for a particular path to reconcile the frequency of the SPE with the local clock.
NPJC-Pgen	Negative Pointer Justification Count path-generated (NPJC-Pgen) is a count of the negative pointer justifications generated for a particular path to reconcile the frequency of the SPE with the local clock.

Table 8-20 Near-End Protection-Switching PMs for the OC-12 Card
Parameter	Definition
For information about Troubleshooting UPSR switch counts, see Chapter 14, "Alarm Troubleshooting." For information about creating circuits that perform a switch, see "Circuits and Tunnels."
PSC (BLSR)	For a protect line in a 2-fiber ring, Protection Switching Count (PSC) refers to the number of times a protection switch has occurred either to a particular span's line protection or away from a particular span's line protection. Therefore, if a protection switch occurs on a 2-fiber BLSR, the PSC of the protection span to which the traffic is switched will increment, and when the switched traffic returns to its original working span from the protect span, the PSC of the protect span will increment again. Note 4-fiber BLSR is not supported on the OC-12 card; therefore, the PSC-S and PSC-R PMs do not increment.
PSC (1+1 protection)	In a 1+1 protection scheme for a working card, Protection Switching Count (PSC) is a count of the number of times service switches from a working card to a protection card plus the number of times service switches back to the working card. For a protection card, PSC is a count of the number of times service switches to a working card from a protection card plus the number of times service switches back to the protection card. The PSC PM is only applicable if revertive line-level protection switching is used.
PSD	For an active protection line in a 2-fiber BLSR, Protection Switching Duration (PSD) is a count of the number of seconds that the protect line is carrying working traffic following the failure of the working line. PSD increments on the active protect line and Protection Switching Duration-Working (PSD-W) increments on the failed working line. Note 4-fiber BLSR is not supported on the OC-12 card; therefore, the Protection Switching Duration-Span (PSD-S), and Protection Switching Duration-Ring (PSD-R) PMs do not increment.
PSC-W	For a working line in a 2-fiber BLSR, Protection Switching Count-Working (PSC-W) is a count of the number of times traffic switches away from the working capacity in the failed line and back to the working capacity after the failure is cleared. PSC-W increments on the failed working line and PSC increments on the active protect line.
PSD-W	For a working line in a 2-fiber BLSR, Protection Switching Duration-Working (PSD-W) is a count of the number of seconds that service was carried on the protection line. PSD-W increments on the failed working line and PSD increments on the active protect line.

Table 8-21 Near-End Protection-Switching Path PMs for the OC-12 Card
Parameter	Definition
Note SONET path PMs will not count unless IPPM is enabled. For additional information, see the "Intermediate-Path Performance Monitoring Reference" section.
STS CV-P	Near-End STS Path Coding Violations (STS CV-P) is a count of B IP errors detected at the STS path layer (i.e., using the B3 byte). Up to eight B IP errors can be detected per frame; each error increments the current CV-P second register.
STS ES-P	Near-End STS Path Errored Seconds (STS ES-P) is a count of the seconds when at least one STS path B IP error was detected. An AIS-P defect (or a lower-layer, traffic-related, near-end defect) or an LOP-P defect can also cause an STS ES-P.
STS FC-P	Near-End STS Path Failure Counts (STS FC-P) is a count of the number of near-end STS path failure events. A failure event begins with an AIS-P failure, an LOP-P failure, a UNEQ-P failure or a TIM-P failure is declared, or if the STS PTE that is monitoring the path supports ERDI-P for that path. The failure event ends when these failures are cleared.
STS SES-P	Near-End STS Path Severely Errored Seconds (STS SES-P) is a count of the seconds when K (2400) or more STS path B IP errors were detected. An AIS-P defect (or a lower-layer, traffic-related, near-end defect) or an LOP-P defect can also cause an STS Severely Errored Seconds Path (SES-P).
STS UAS-P	Near-End STS Path Unavailable Seconds (STS UAS-P) is a count of one-second intervals when the STS path is unavailable. An STS path is unavailable at the onset of ten consecutive seconds that qualify as Severely Errored Seconds Path (SES-Ps), and continues to be unavailable until the onset of ten consecutive seconds occur that do not qualify as SES-Ps. The ten seconds with no SES-Ps are excluded from unavailable time.

Table 8-22 Far-End Line Layer PMs for the OC-12 Card
Parameter	Definition
CV-L	Code Violation Line (CV-L) is a count of B IP errors detected by the far-end LTE and reported back to the near-end LTE using the REI-L indication in the line overhead. For SONET signals at rates below OC-48, up to 8 x N B IP errors per STS-N frame can be indicated using the REI-L. For OC-48 signals, up to 255 B IP errors per STS-N frame can be indicated. The current CV-L second register is incremented for each B IP error indicated by the incoming REI-L.
ES-L	Errored Seconds Line (ES-L) is a count of the seconds when at least one line-layer B IP error was reported by the far-end LTE or an RDI-L defect was present.
SES-L	Severely Errored Seconds Line (SES-L) is a count of the seconds when K (see GR-253-CORE for values) or more line-layer B IP errors were reported by the far-end LTE or an RDI-L defect was present.
UAS-L	UAS-L is a count of the seconds when the line is considered unavailable at the far end. A line is considered unavailable at the onset of ten consecutive seconds that qualify as SES-LFEs, and continues to be unavailable until the onset of ten consecutive seconds that do not qualify as SES-LFEs.
FC-L	FC-L is a count of the number of far-end line failure events. A failure event begins when RFI-L failure is declared and ends when the RFI-L failure clears. A failure event that begins in one period and ends in another period is counted only in the period where it began.

8.5.3 OC-48 Card Performance Monitoring Parameters

Figure 8-18 shows the signal types that support far-end PMs. Figure 8-19 shows where overhead bytes detected on the ASICs produce performance monitoring parameters for the OC-48 cards.

Note PMs on the protect STS are not supported for BLSR. The XX in the illustration above represents all PMs listed below with the given prefix and/or suffix.

Note For PM locations relating to protection switch counts, see the GR-1230-CORE document.

Table 8-23 Near-End Section PMs for the OC-48 Cards
Parameter	Definition
CV-S	CV-S is a count of B IP errors detected at the section-layer (i.e. using the B1 byte in the incoming SONET signal). Up to eight section B IP errors can be detected per STS-N frame; each error increments the current CV-S second register.
ES-S	ES-S is a count of the number of seconds when at least one section-layer B IP error was detected or a Severely Errored Frame (SEF) or Loss of Signal (LOS) defect was present.
SES-S	SES-S is a count of the seconds when K (see GR-253 for value) or more section-layer B IP errors were detected or a Severely Errored Frame (SEF) or Loss of Signal (LOS) defect was present.
SEFS-S	SEFS-S is a count of the seconds when a Severely Errored Frame (SEF) defect was present. An SEF defect is expected to be present during most seconds when a Loss of Signal (LOS) or Loss of Frame (LOF) defect is present. However, there may be situations when the SEFS-S parameter is only incremented based on the presence of an SEF defect.

Table 8-24 Near-End Line Layer PMs for the OC-48 Cards
Parameter	Definition
CV-L	Code Violation Line (CV-L) is a count of B IP errors detected at the line-layer (i.e. using the B2 bytes in the incoming SONET signal). Up to 8 x N B IP errors can be detected per STS-N frame; each error increments the current CV-L second register.
ES-L	Errored Seconds Line (ES-L) is a count of the seconds when at least one line-layer B IP error was detected or an AIS-L defect was present.
SES-L	Severely Errored Seconds Line (SES-L) is a count of the seconds when K (see GR-253 for values) or more line-layer B IP errors were detected or an AIS-L defect was present.
UAS-L	UAS-L is a count of the seconds when the line is considered unavailable. A line becomes unavailable at the onset of ten consecutive seconds that qualify as Severely Errored Seconds Line (SES-Ls), and continues to be unavailable until the onset of ten consecutive seconds that do not qualify as SES-Ls.
FC-L	FC-L is a count of the number of near-end line failure events. A failure event begins when an AIS-L failure or a lower-layer traffic-related, near-end failure is declared. This failure event ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period where it begins.

Table 8-25 Near-End SONET Path H-byte PMs for the OC-48 Cards
Parameter	Definition
Note On CTC, the count fields for Positive Point Justification Count (PPJC) and Negative Pointer Justification Count (NPJC) PMs appear white and blank unless they are enabled on the Provisioning > Line tabs. See the "Pointer Justification Count Reference" section.
PPJC-Pdet	Positive Pointer Justification Count path-detected (PPJC-Pdet) is a count of the positive pointer justifications detected on a particular path on an incoming SONET signal.
NPJC-Pdet	Negative Pointer Justification Count path-detected (NPJC-Pdet) is a count of the negative pointer justifications detected on a particular path on an incoming SONET signal.
PPJC-Pgen	Positive Pointer Justification Count path-generated (PPJC-Pgen) is a count of the positive pointer justifications generated for a particular path to reconcile the frequency of the SPE with the local clock.
NPJC-Pgen	Negative Pointer Justification Count path-generated (NPJC-Pgen) is a count of the negative pointer justifications generated for a particular path to reconcile the frequency of the SPE with the local clock.

Table 8-26 Near-End Protection-Switching PMs for the OC-48 Cards
Parameter	Definition
For information about Troubleshooting UPSR switch counts, see Chapter 14, "Alarm Troubleshooting." For information about creating circuits that perform a switch, see "Circuits and Tunnels."
PSC (BLSR)	For a protect line in a 2-fiber ring, Protection Switching Count (PSC) refers to the number of times a protection switch has occurred either to a particular span's line protection or away from a particular span's line protection. Therefore, if a protection switch occurs on a 2-fiber BLSR, the PSC of the protection span to which the traffic is switched will increment, and when the switched traffic returns to its original working span from the protect span, the PSC of the protect span will increment again.
PSC (1+1 protection)	In a 1+1 protection scheme for a working card, PSC is a count of the number of times service switches from a working card to a protection card plus the number of times service switches back to the working card. For a protection card, PSC is a count of the number of times service switches to a working card from a protection card plus the number of times service switches back to the protection card. The PSC PM is only applicable if revertive line-level protection switching is used.
PSD	For an active protection line in a 2-fiber BLSR, Protection Switching Duration (PSD) is a count of the number of seconds that the protect line is carrying working traffic following the failure of the working line. PSD increments on the active protect line and Protection Switching Duration-Working (PSD-W) increments on the failed working line.
PSC-W	For a working line in a 2-fiber BLSR, PSC-W is a count of the number of times traffic switches away from the working capacity in the failed line and back to the working capacity after the failure is cleared. PSC-W increments on the failed working line and PSC increments on the active protect line.
PSD-W	For a working line in a 2-fiber BLSR, PSD-W is a count of the number of seconds that service was carried on the protection line. Protection Switching Duration-Working (PSD-W) increments on the failed working line and PSD increments on the active protect line.

Table 8-27 Near-End SONET Path PMs for the OC-48 Cards
Parameter	Definition
Note SONET path PMs will not count unless IPPM is enabled. For additional information, see the "Intermediate-Path Performance Monitoring Reference" section.
STS CV-P	Near-End STS Path Coding Violations (STS CV-P) is a count of B IP errors detected at the STS path layer (i.e., using the B3 byte). Up to eight B IP errors can be detected per frame; each error increments the current CV-P second register.
STS ES-P	Near-End STS Path Errored Seconds (STS ES-P) is a count of the seconds when at least one STS path B IP error was detected. An AIS-P defect (or a lower-layer, traffic-related, near-end defect) or an LOP-P defect can also cause an STS ES-P.
STS FC-P	Near-End STS Path Failure Counts (STS FC-P) is a count of the number of near-end STS path failure events. A failure event begins with an AIS-P failure, an LOP-P failure, a UNEQ-P failure or a TIM-P failure is declared, or if the STS PTE that is monitoring the path supports ERDI-P for that path. The failure event ends when these failures are cleared.
STS SES-P	Near-End STS Path Severely Errored Seconds (STS SES-P) is a count of the seconds when K (2400) or more STS path B IP errors were detected. An AIS-P defect (or a lower-layer, traffic-related, near-end defect) or an LOP-P defect can also cause an STS Severely Errored Seconds Path (SES-P).
STS UAS-P	Near-End STS Path Unavailable Seconds (STS UAS-P) is a count of the one-second intervals when the STS path is unavailable. The STS path is unavailable at the onset of ten consecutive seconds that qualify as Severely Errored Seconds Path (SES-Ps), and continues to be unavailable until the onset of ten consecutive seconds that do not qualify as SES-Ps. The ten seconds with no SES-Ps are excluded from available time.

Table 8-28 Far-End Line Layer PMs for the OC-48 Cards
Parameter	Definition
CV-L	Code Violation Line (CV-L) is a count of B IP errors detected by the far-end LTE and reported back to the near-end LTE using the REI-L indication in the line overhead. For SONET signals at rates below OC-48, up to 8 x N B IP errors per STS-N frame can be indicated using the REI-L. For OC-48 signals, up to 255 B IP errors per STS-N frame can be indicated. The current CV-L second register is incremented for each B IP error indicated by the incoming REI-L.
ES-L	Errored Seconds Line (ES-L) is a count of the seconds when at least one line-layer B IP error was reported by the far-end LTE or an RDI-L defect was present.
SES-L	Severely Errored Seconds Line (SES-L) is a count of the seconds when K (see GR-253-CORE for values) or more line-layer B IP errors were reported by the far-end LTE or an RDI-L defect was present.
UAS-L	UAS-L is a count of the seconds when the line is considered unavailable at the far end. A line becomes unavailable at the onset of ten consecutive seconds that qualify as SES-LFEs, and continues to be unavailable until the onset of ten consecutive seconds that do not qualify as SES-LFEs.
FC-L	FC-L is a count of the number of far-end line failure events. A failure event begins when RFI-L failure is declared and ends when the RFI-L failure clears. A failure event that begins in one period and ends in another period is counted only in the period where it began.

Table Of Contents

Performance Monitoring

8.1 Using the Performance Monitoring Screen

8.1.1 Viewing PMs

Procedure: View PM s

8.1.2 Changing the Screen Intervals

Procedure: Select Fifteen-Minute PM Intervals on the Performance Monitoring Screen

Procedure: Select Twenty-Four Hour PM Intervals on the Performance Monitoring Screen

Procedure: Clearing PM Data on the Performance Monitoring Screen

8.1.3 Viewing Near-End and Far-End PMs

Procedure: Select Near-End PMs on the Performance Monitoring Screen

Procedure: Select Far-End PMs on the Performance Monitoring Screen

8.1.4 Using the Signal-Type Menu

Procedure: Select Signal-Type Menus on the Performance Monitoring Screen

8.1.5 Using the Baseline Button

Procedure: Use the Baseline Button on the Performance Monitoring Screen

8.1.6 Using the Clear Button

Procedure: Use the Clear Button on the Performance Monitoring Screen

Threshold Reference

8.2 Intermediate-Path Performance Monitoring Reference

8.3 Pointer Justification Count Reference

8.4 Performance Monitoring for Electrical Cards

8.4.1 XTC DS1 Performance Monitoring Parameters

8.4.2 XTC DS3 Card Performance Monitoring Parameters

8.5 Performance Monitoring for Optical Cards

8.5.1 OC-3 Card Performance Monitoring Parameters

8.5.2 OC-12 Card Performance Monitoring Parameters

8.5.3 OC-48 Card Performance Monitoring Parameters