This section describes the terminated SONET VT1.5 performance monitoring parameters. Terminated SONET VT1.5 path performance monitoring applies to VT1.5 paths cross-connected to a non-SONET interface (for example, DS1 or TMUX).
The following table lists the SONET VT1.5 path performance parameters that Alcatel-Lucent 1665 DMX monitors, including the default and ranges for the 15-minute and 1-day (24-hour) registers.
Facility |
Measured Provisionable Parameter |
15-Min |
1-Day | ||
---|---|---|---|---|---|
Default |
Range 1 |
Default |
Range 1 | ||
VT1.5 Path |
Coding Violations - Path, Path Far End (CV-P, CV-PFE) |
75 |
0–16383 |
750 |
0–1048575 |
V5 Errored Seconds - Path, Path Far End (ES-P, ES-PFE) |
40 |
0–900 |
900 |
0–65535 | |
V5 Severely Errored Seconds - Path, Path Far End (SES-P, SES-PFE) |
40 |
0–900 |
900 |
0–65535 | |
V5 Unavailable Seconds - Path, Path Far End (UAS-P, UAS-PFE) |
40 |
0–900 |
900 |
0–65535 | |
Failure Counts - Path, Path Far End (FC-P, FC-PFE) |
10 |
1–72 |
10 |
1–4095 |
When an individual performance monitoring parameter threshold is provisioned as zero (0), TCA reporting for the affected parameter is disabled.
Alcatel-Lucent 1665 DMX monitors the following near end SONET VT1.5 path parameters on incoming (from the SONET interface) VT1.5 signals.
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 VT Path Coding Violations (CVP) parameter for each SONET path is monitored. The VT Far-End CVP parameter increments as reported by the REI-V indication of the VT path overhead.
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 VT Path Errored Seconds (ESP) parameter for each SONET path is monitored. The VT Far-End ESP parameter increments once for each second where one or more Far-End VT Path layer BIP errors were reported by the far-end VT-PTE (using the REI-V indication), a one-bit RDI-V defect was present, or an ERDI-V (if supported) defect is detected.
Alcatel-Lucent 1665 DMX 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 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 DMX 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 VT Path Severely Errored Seconds (SESP) parameter for each SONET VT path is monitored. The VT Far-End SESP parameter increments once for each second where K or more BIP errors are reported by the far-end VT-PTE (using the REI-V indication), or a one bit RDI-V defect was present or (if ERDI-V is supported), an ERDI-V defect is detected. The integer value for K is set by standards (values are shown in Table 10).
Alcatel-Lucent 1665 DMX 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 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 VT Path Unavailable Seconds (UASP) parameter for each SONET path is monitored. The VT Far-End UASP parameter increments once for each second where VT Far-End SESP is detected after ten consecutive seconds with VT Far-End SESP detected. VT Far-End UASP continues to increment once for each second until ten consecutive seconds without VT Far-End SESP are detected.
The Near-End STS Path Failure Counts (FC-P) parameter for each SONET path is monitored. The FC-P parameter increments once for the beginning of each AIS-P event (AIS-P detected and cleared), LOP-P event (LOP-P detected and cleared), UNEQ-P event (UNEQ-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. 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.
November 2011 | Copyright © 2011 Alcatel-Lucent. All rights reserved. |