Table of Contents
Advertisement
Performance Monitoring for Optical Cards
Table 8-32 Near-End SONET Path H-byte PMs for the OC-3 Card
Parameter
PPJC-Pdet
NPJC-Pdet
PPJC-Pgen
NPJC-Pgen
Table 8-33 Near-End SONET Path PMs for the OC-3 Card
Parameter
Note
STS CV-P
STS ES-P
STS FC-P
STS SES-P
STS UAS-P
Cisco ONS 15454 Installation and Operations Guide
8-36
Definition
Positive Pointer Justification Count, STS Path Detected (PPJC-Pdet) is a
count of the positive pointer justifications detected on a particular path on
an incoming SONET signal.
Negative Pointer Justification Count, STS Path Detected (NPJC-Pdet) is a
count of the negative pointer justifications detected on a particular path on
an incoming SONET signal.
Positive Pointer Justification Count, STS Path Generated (PPJC-Pgen) is
a count of the positive pointer justifications generated for a particular path
to reconcile the frequency of the SPE with the local clock.
Negative Pointer Justification Count, STS Path Generated (NPJC-Pgen) is
a count of the negative pointer justifications generated for a particular
path to reconcile the frequency of the synchronous payload envelope
(SPE) with the local clock.
Definition
SONET path PMs will not count unless IPPM is enabled. For additional information, see the
"Enable Intermediate-Path Performance Monitoring" procedure on page
IPPM feature is not supported in Software R3.1. However, SONET path PMs can be monitored
by logging into the far-end node directly.
Near-End STS Path Coding Violations (CV-P) is a count of BIP errors
detected at the STS path layer (i.e., using the B3 byte). Up to eight BIP
errors can be detected per frame; each error increments the current CV-P
second register.
Near-End STS Path Errored Seconds (ES-P) is a count of the seconds
when one or more STS path BIP 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 ES-P.
Near-End STS Path Failure Counts (FC-P) is a count of the number of
near-end STS path failure events. A failure event begins with an AIS-P
failure, an LOP-P failure, a UNEQ-P failure, or a TIM-P failure is
declared, or 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 (SES-P) is a count of the
seconds when K (2400) or more STS path BIP 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 SES-P.
Near-End STS Path Unavailable Seconds (UAS-P) is a count of the
seconds when the STS path was unavailable. An STS path becomes
unavailable when ten consecutive seconds occur that qualify as SES-Ps,
and it continues to be unavailable until ten consecutive seconds occur that
do not qualify as SES-Ps.
Chapter 8
Performance Monitoring
7-25. The far-end
November 2001
Advertisement
Table of Contents
