363-206-285
Maintenance Description
Issue 3 June 2001
9-47
eight errors per STS-1 frame. The contents of the three line B2 parity violation
counters associated with the OC-3 line are added to form a composite B2 parity
violation count. Coding violations are not counted during seconds that contain a
line AIS, LOS, LOF, or during a UAS. The B2 parity violations are counted and
thresholded independently for the service and protection lines.
Errored Seconds (ES) 9
An "errored second" is a second in which one or more B2 parity violations are
detected. An ES "type A" is a second in which exactly one B2 parity violation is
detected. An ES "type B" is a second in which more than one and less than 32 for
OC-3, or 12 for EC-1, B2 parity violations are detected. Seconds that are UAS are
not counted as ES. A second that contains a line AIS, LOS, LOF or is a UAS is not
counted as a type A or type B ES. All three of these parameters are counted and
thresholded independently for the service and protection lines.
Severely Errored Seconds (SES) 9
A “severely errored second” is a second in which 32 or more for OC-3 or, 12 or
more for EC-1, B2 parity violations are detected or one in which a LOS, LOF or line
AIS occurs. A UAS is not counted as an SES. SESs are counted and thresholded
independently for the service and protection lines.
Unavailable Seconds (UAS) 9
An “unavailable second” is a second during which the OC-3 line is "unavailable." A
line is considered unavailable from the beginning of X consecutive SESs until the
beginning of Y consecutive seconds, none of which is severely errored. X is equal
to 10 seconds or, in the case of a failure, the line signal failure. Y is equal to 10
seconds of no SESs or line signal failure. UAS are counted and thresholded
independently for OC-3 interface service and protection lines.
Line Protection Switch Counts 9
Line protection switch counts is the count of the number of protection switches
FROM the working OC-3 interface line. The count is independently counted and
thresholded for both the service and the protection line.
STS Pointer Justification Count (PJC) 9
This feature provides a TCA from a DDM-2000 shelf when the STS pointer
justification count in a performance bin exceeds a user provisioned threshold value.
STS PJCs for each SONET line interface are accumulated in 15 minute and 24
hour performance monitoring bins. The TCA is sent via a TL1 autonomous
message to the OS and is available through CIT and TL1 PM reports. PJCs are not
accumulated during one second intervals in which an STS-1 is in the LOP or AIS
state.
To Next Page
Loading...
Need help?
General
