Raisecom
iTN2100 (P100R002) Hardware Description
Raisecom Technology Co., Ltd.
Table 6-7 Alarms of the OPCOM3500E-2STM1/4-M
Attenuation of received signals is over great.
The peer sender fails.
The connector of fiber is dirty or improperly connected.
The local receiver fails.
The TX clock of the peer device fails.
Optical signals do not match.
The local RX reference clock fails.
The received trace byte of the local device and the sent trace
byte of the peer device are inconsistent.
Services are improperly configured.
The AU-AIS alarm of the VC4 channel is triggered by MS-
AIS, R-LOS, or R-LOF alarms.
Services are improperly configured.
The peer device sends AU-AIS alarms.
The TX part of the peer device or the RX part of the local
device fails.
The RX part of the peer device fails.
Services are improperly configured on the peer device.
Bit Error Rate (BER) of the local device is over great.
BER in the multiplexing section is over high.
Optical signals are improperly transmitted.
The performance of the local card is bad.
Multiplexing section alarm LED
Alarm signals are inserted in the optical signals sent by the
peer device.
The peer device is a regenerator and receives LOS, LOF, or
OOF alarms.
High-order Path (HP) Loss of Multiframe (LOM) alarm
Services are improperly configured.
Byte H4 is lost or incorrect.
HP Trace byte (J1) mismatch alarm
The received HPtrace byte of the local device and the sent
HP trace byte of the peer device are inconsistent.
Services are improperly configured.
HP signal marking byte (C2) mismatch alarm
The received signal marking byte of the local device and the
sent signal marking byte of the peer device are inconsistent.
Services are improperly configured.
Services are improperly configured.
The channel of the peer device fails.
Higher–level alarms, such as R-LOS, trigger the alarm.
The crossconnection card fails, SDH data received from the
backplane is incorrect.
The interface between the tributary card and the cross
connection card fails.
Services are improperly configured.
The Low-order Path (LP) trace identifiers of the local device
and the peer device are inconsistent.
Services are improperly configured.