EXFO FTB-8100 Series, User Manual

Page: 210 / 518

SONET Tabs
198
FTB-8100 Series Transport Blazer
HOP RX (SONET)
Alarm Analysis
³
AIS-P (Alarm Indication Signal - Path): The AIS-P alarm is declared
when the H1 and H2 bytes for an STS path contain an all-ones pattern
in three consecutive frames or more.
³
LOP-P
(Loss Of Pointer - Path): The LOP alarm indicates that a valid
pointer is not found in N consecutive frames (where 8
≤
N
≤
10), or that
N consecutive NDFs (“1001” pattern) are detected (non-concatenated
payloads).
³
LOM
(Loss Of Multiframe): For VT structured SONET frames, the LOM
alarm indicates that the system loss track of the H4 byte multiframe
indicator sequence.
³
RDI-P (Remote Defect Indication - Path): The RDI-P alarm is declared
when bits 5, 6, and 7 of the G1 byte contain the “100” or “111” pattern
in five consecutive frames.
³
TIM-P
(Trace Identifier Mismatch - Path): The TIM-P defect indicates
that the received J1 Trace doesn’t match the expected message value.
The TIM-P alarm is only available when
Enable TIM-P
check box from
J1 Trace section has been selected.
³
PLM-P
(Payload Label Mismatch - Path): The PLM-P is declared upon
receipt of five consecutive frames with mismatched STS signal labels
(C2 byte).
³
UNEQ-P (Unequipped - Path): UNEQ-P is declared when the C2 bytes
contain “00 H” in five consecutive frames.
³
PDI-P (Payload Defect Indication - Path): For VT-tructured STS-1 SPE,
the PDI-P is declared when detecting LOP-V, AIS-V, DS3 AIS, DS3 LOS,
or DS3 OOF defect on any VT or DS3 payload that it embeds into the
STS SPE that it is originating. For non-VT-structured STS-1 or STS-Nc
SPE, thePDI-P is declared when receiving the hexadecimal FC code
(C2 byte).