Performance Monitoring at the Data Layer
SDH/SONET Performance
The supported set of performance counters for the Section/Regeneration Section and
Line/Multiplex Section are shown in Table 101.
Counter Type Description
Errored Second This counter is increased for each second in which
one or more CV/BBEs, traffic disruptive defects,
connection defects, or BIP-8 violations are detected.
Severely Errored Second This counter is increased for each second in which the
number of bit parity violations is higher than a
configurable threshold, or in the case of traffic
disruptive or connection defects. The SES threshold
defaults to 30% of the transmitted frames. This
threshold applies to all relevant entities in the Network
Element.
Severely Errored Framing
Second
This counter is increased for each second with Out of
Frame (OOF)/Severely Errored Framing Seconds
(SEFS) or traffic disruptive defects.
Coding Violations
Background Block Errors
This counter is increased for each parity
violation/background block error. Given one second
for which the SES counter is increased, the parity
violations registered in this second are not counted.
Unavailable Seconds When more than 10 consecutive seconds of SES are
recorded, the unavailable second (UAS) state is
entered. The UAS counter is increased for each
second this state persists. These 10 consecutive
seconds are added to the counter. To exit the UAS
state, more than 10 consecutive seconds without
SES must be recorded. These 10 seconds are
considered available seconds
Table 101: SDH/SONET Counter Descriptions
Note
A Trace Identifier Mismatch (TIM) alarm is considered a traffic
disruption.
The Management Data Guide provides a per module overview of the counters supported
for each port, as well as the maximum value that can be recorded and the record type.
FSP 3000R7 Maintenance and Troubleshooting Manual - Product Release 16.2 - Document Issue A 643
To Next Page
Loading...
