Xtc Ds3 Card Performance Monitoring Parameters - Cisco ONS 15327 User Documentation

Chapter 8 Performance Monitoring
Table 8-8
Parameter
STS CV-P
STS ES-P
STS FC-P
STS SES-P
STS UAS-P

8.4.2 XTC DS3 Card Performance Monitoring Parameters

Figure 8-13
detected on the ASICs produce performance monitoring parameters for the XTC DS3 cards.
June 2002
SONET Path PMs for the XTC DS1 Cards
Definition
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.
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.
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.
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).
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.
shows the signal types that support far-end PMs.
Performance Monitoring for Electrical Cards
Figure 8-14 shows where overhead bytes
Cisco ONS 15327 User Documentation, R3.3
8-21