STS-N performance parameters

Overview

This section describes the performance monitoring parameters on terminated (STS-1) and intermediate STS-N (STS-1, STS-3c, STS-12c) paths that are cross-connected through the system. Intermediate SONET STS-N path performance monitoring applies to STS-N paths cross-connected to another SONET interface. Terminated SONET STS-N path performance monitoring applies to STS-N paths cross-connected to a non-SONET interface (for example, DS3).

Monitored parameters

The following table lists the SONET STS-N path performance parameters that Alcatel-Lucent 1665 DMXtend monitors, including the default and ranges for the 15-minute and 1-day (24-hour) registers.

Table 5-16: SONET STS-N performance parameters

Facility

Measured Provisionable Parameter

15-Min

1-Day

Default

Range 1

Default

Range 1

STS-192c Path

Coding Violations (CV-P), CV-PFE

20

0–16383

200

0–1048575

STS-48c Path

Coding Violations (CV-P), CV-PFE

300

0–16383

3000

0–1048575

STS-12c Path

Coding Violations (CV-P), CV-PFE

75

0–16383

750

0–1048575

STS-3c Path

Coding Violations (CV-P), CV-PFE

25

0–16383

250

0–1048575

STS-1 Path

Coding Violations (CV-P), CV-PFE

15

0–900

150

0–65535

STS-192c Path

Errored Seconds (ES-P), ES-PFE

16

0–16383

160

0–1048575

STS-48c Path

Errored Seconds (ES-P), ES-PFE

240

0–16383

2400

0–1048575

STS-12c Path

Errored Seconds (ES-P), ES-PFE

60

0–16383

600

0–1048575

STS-3c Path

Errored Seconds (ES-P), ES-PFE

20

0–16383

200

0–1048575

STS-1 Path

Errored Seconds (ES-P), ES-PFE

12

0–900

100

0–65535

STS-N Path

FC-P, FC-PFE

10

1–72

10

1–4095

Severely Errored Seconds (SES-P), SES-PFE

3

0–900

7

0–65535

Unavailable Seconds (UAS-P), UAS-PFE

10

0–900

10

0–65535

Notes:
  1. When an individual performance monitoring parameter threshold is provisioned as zero (0), TCA reporting for the affected parameter is disabled.

STS-N path parameters

Alcatel-Lucent 1665 DMXtend monitors the following near end SONET STS path parameters on incoming (from the SONET interface) STS-N signals.

Coding violations (CV-P)

The Near-End STS Path Coding Violations (CVP) parameter for each SONET path is monitored. The CVP parameter increments once for each BIP error detected at the STS path layer (the B3 byte of the incoming SONET STS Path overhead). Up to 8 BIP errors can be detected per frame.

The Far-End STS Path Coding Violations (CVP) parameter for each SONET path is monitored. The Far-End CVP parameter increments as reported by the REI-P indication of the STS path overhead.

Errored seconds (ES-P)

The Near-End STS Path Errored Seconds (ESP) parameter for each SONET path is monitored. The ESP parameter increments once for each second where one or more STS Path layer BIP errors are detected or an AIS-P, LOP-P, or UNEQ-P defect is detected.

The Far-End STS Path Errored Seconds (ESP) parameter for each SONET path is monitored. The Far-End ESP parameter increments once for each second where one or more Far-End STS Path layer BIP errors are detected as reported by the REI-P indication of the line overhead or an RDI-P defect is present, or an ERDI-P (if supported) defect is detected.

Alcatel-Lucent 1665 DMXtend detects 1-bit RDI, but treats it as though it is the high order bit of a 3-bit ERDI in that it includes UNEQ.

Severely errored seconds (SES-P)

The Near-End STS Path Severely Errored Seconds (SESP) parameter for each SONET path is monitored. The SESP parameter increments once for each second where K or more STS Path layer BIP errors are detected or an AIS-P, LOP-P, or UNEQ-P defect is detected. The integer value for K is set by standards and is selectable (values are shown in Table 8). Alcatel-Lucent 1665 DMXtend detects 1-bit RDI, but treats it as though it is the high order bit of a 3-bit ERDI in that it includes UNEQ.

The Far-End STS Path Severely Errored Seconds (SESP) parameter for each SONET path is monitored. The Far-End SESP parameter increments once for each second where K or more STS Path layer BIP errors are detected as reported by the REI-P indication of the path overhead or a one bit RDI-P defect was present or (if ERDI-P is supported), an ERDI-P defect is detected. The integer value for K is set by standards and selectable (values are shown in Table 8).

Alcatel-Lucent 1665 DMXtend detects 1-bit RDI, but treats it as though it is the high order bit of a 3-bit ERDI in that it includes UNEQ.

Unavailable seconds (UAS-P)

The Near-End STS Path Unavailable Seconds (UASP) parameter for each SONET path is monitored. The UASP parameter increments once for each second where SESP is detected after ten consecutive seconds with SESP detected. UASP continues to increment once for each second until ten consecutive seconds without SESP are detected.

The Far-End STS Path Unavailable Seconds (UASP) parameter for each SONET path is monitored. The Far-End UASP parameter increments once for each second where Far-End SESP is detected after ten consecutive seconds with Far-End SESP detected. Far-End UASP continues to increment once for each second until ten consecutive seconds without Far-End SESP are detected.

Failure counts path (FC-P)

The Near-End STS Path Unavailable Seconds (UASP) parameter for each SONET path is monitored. The UASP parameter increments once for each second where SESP is detected after ten consecutive seconds with SESP detected. UASP continues to increment once for each second until ten consecutive seconds without SESP are detected.

The Far-End STS Path Failure Counts (FC-P) parameter for each SONET path is monitored. The Far-End FC-P parameter increments once for the beginning of each RFI-P event (RFI-P detected and cleared). A failure that begins in one period and ends in another period, is counted in the period in which it begins.

STS-N path PM report

Use the Performance → Reports → STSn Path command to obtain the STS-N Path PM Report. For more information about the STS-N path parameters and the Performance → Reports → STSn Path command, see the WaveStar® CIT online help.

September 2013Copyright © 2013 Alcatel-Lucent. All rights reserved.