T2000 Alarms

1.A_LOC
major
LOC – Loss Of Clock

The A_LOC is an alarm indicating the loss of clock in the upstream direction of the bus.

Impact on System: When the A_LOC alarm occurs, the services carried by the board path are interrupted.
Possible Causes:
1) The PDH equipment interconnected to the service path is faulty.
2) The service type is incorrectly configured.
3) The service cross-connection is incorrectly configured.
4) The board hardware is faulty.
5) The cross-connect and timing board is faulty.

2.ALM_GFP_dCSF
critical

The ALM_GFP_dCSF is an alarm indicating GFP loss of client signal. When the source end cannot receive
the client signal, it sends the management frame to the sink end. When the sink end receives the management frame,
this alarm occurs.
Impact on System: During data transmission, the source end cannot receive the client signal. The services
lose packets or are interrupted.
Possible Causes:
1) The external port is not enabled.
2) The interface module is wrong. For example, the optical module is absent or does not match, or the
optical/electrical signal is lost.
3) The physical link fails.

3.ALM_GFP_dLFD
major

The ALM_GFP_dLFD is an alarm indicating GFP loss of frame delineation. When GFP frames are detected
out of synchronization, this alarm occurs.
Impact on System: During data transmission, failure in GFP framing causes service interruption.
Possible Causes:
1) The number of uplink or downlink timeslots bound with the VCTRUNK at the local station is
inconsistent with the number of downlink or uplink timeslots bound with the corresponding VCTRUNK at the
opposite station.
2) Bit errors are present in the timeslots bound with the VCTRUNK.

4.ASP_INDI
major

The APS_INDI is an alarm indicating the APS state. This alarm occurs when the MSP is in the switching state.
Impact on System: When the APS_INDI alarm occurs, the automatic protection switching or the switching
triggered by the external command occurs. The protected services are switched to the protection channel for
transmission. The alarm does not affect the services. If the protection channel fails at this time, the services are
interrupted.
 Possible Causes
1) An external command, including manual switching, forced switching, and exercise switching, is issued.
2) After the R_LOS, R_LOF, MS_AIS, B2_EXC, or B2_SD alarm occurs, the MSP group changes to the
switching state.
3) The service board is faulty.
4) The cross-connect board is faulty.
5) The attributes of the MSP group are incorrectly configured.

5.AU_AIS
major

The AU_AIS is the administrative unit (AU) alarm indication. When the pointer value received on the receive
side of the local optical interface is all "1"s, the AU_AIS alarm is reported.
Impact on System: When the AU_AIS alarm occurs, the path-level services are interrupted if the network is
not protected. In this case, the AU-AIS alarm occurs at the downstream station.
Possible Causes:
1) A higher-level alarm, such as R_LOS, R_LOF, R_OOF, B1_EXC or B2_EXC, occurs in the system.
2) The service is incorrectly configured.
3) The AIS signal is transmitted at the opposite station.
4) The transmit unit (such as cross-connect boards or line boards) at the opposite station is faulty.
5) The receive unit at the local station is faulty.

6.B1_EXC
minor

The B1_EXC is an alarm indicating that the number of regenerator section B1 bit errors in the signals received
over the line crosses the threshold.
Impact on System: When the B1_EXC occurs, the quality of the transmitted services is heavily degraded, the
system inserts the AU_AIS alarm in the cross-connection direction.
Possible Causes:
1) The received signals are heavily attenuated.
2) The fiber connector is dirty.
3) The fiber connector is loose.
4) The attenuation value specified in the fiber attenuator is extremely high or low.
5) The transmit unit at the opposite station is faulty.
6) The receive unit at the local station is faulty.

7.B1_SD
minor
SD – Signal Degradation

The B1_SD is an alarm indicating that regenerator section B1 signals received over the line are degraded.
When a line board has detected the B1 byte, showing that the bit error ratio of the regenerator section signals
exceeds the specified threshold value (default value: 1 x 10–6), the B1_SD alarm is reported.
Impact on System: When the B1_SD alarm occurs, the quality of the transmitted services is heavily degraded.
Possible Causes:
1) The received signals are heavily attenuated.
2) The fiber connector is dirty.
3) The fiber connector is loose.
4) The attenuation value specified in the fiber attenuator is extremely high or low.
5) The transmit unit at the opposite station is faulty.
6) The receive unit at the local station is faulty.
 8.B2_EXC
minor

The B2_EXC is an alarm indicating that the number of multiplex section B2 bit errors in the signals received
over the line exceeds the specified value. When a line board has detected the B2 byte, showing that the bit error
ratio of the multiplex section signals exceeds the value 1 x 10-3 ), the B2_EXC alarm is reported.
Impact on System: When the B2_EXC occurs, the quality of the transmitted services is heavily degraded.
The system returns the M1 byte to the opposite end, showing the MS_REI alarm. Consequently, the opposite station
reports the MS_REI alarm.
Possible Causes:
1) The number of B1 bit errors is extremely high.
2) The received signals are heavily attenuated.
3) The fiber connector is dirty.
4) The fiber connector is loose.
5) The attenuation value specified in the fiber attenuator is extremely high or low.
6) The transmit unit at the opposite station is faulty.
7) The receive unit at the local station is faulty.

9.B2_SD
minor

The B2_SD is an alarm that multiplex section B2 signals received over the line are degraded. When a line
board has detected the B2 byte, showing that the bit error ratio of the multiplex section signals exceeds the value 1 x
10-6), the B2_SD alarm is reported.
Impact on System: When the B2_SD alarm occurs, the quality of the transmitted services is heavily
degraded. The system returns the M1 byte to the opposite end, showing the MS_REI alarm. Consequently, the
remote station reports the MS_REI alarm.
Possible Causes:
1) The number of B1 bit errors is extremely high.
2) The received signals are heavily attenuated.
3) The fiber connector is dirty.
4) The fiber connector is loose.
5) The attenuation value specified in the fiber attenuator is extremely high or low.
6) The transmit unit at the remote station is faulty.
7) The receive unit at the local station is faulty.

10.B3_EXC
major

The B3_EXC is an alarm indicating that the number of higher order path B3 bit errors in the signals received
over the line crosses the threshold. When a line board has detected the B3 byte, showing that the bit error ratio of
the higher order path signals exceeds the value 1 x 10-3 ), the B3_EXC alarm is reported.
Impact on System: When the B3_EXC alarm occurs, bit errors occur in the path-level services. The system
returns the G1 byte to the opposite end, showing the HP_REI alarm. Consequently, the opposite station reports the
HP_REI alarm. If the AU_AIS alarm is inserted when the B3_EXC alarm occurs, the system returns the G1 byte to
the opposite end, showing the HP_RDI alarm. Consequently, the remote station generates the HP_RDI alarm.
Possible Causes:
1) The received signals are heavily attenuated.
2) The fiber connector is dirty.
3) The fiber connector is loose.
4) The attenuation value specified in the fiber attenuator is extremely high or low.
5) The transmit unit at the opposite station is faulty.
6) The receive unit at the local station is faulty.
 11.B3_SD
minor

The B3_SD is an alarm indicating that the higher order path B3 signals received over the line are degraded.
When a line board has detected the B3 byte, showing that the bit error ratio of the higher order path signals exceeds
the value 1 x 10-6 ), the B3_SD alarm is reported.
Impact on System: When the B3_SD alarm occurs, bit errors occur in the path-level services. The system
returns the G1 byte to the opposite end, showing the HP_REI alarm. Consequently, the opposite station reports the
HP_REI alarm. If the AU_AIS alarm is inserted when the B3_SD alarm occurs, the system returns the G1 byte to
the opposite station, showing the HP_RDI alarm. Consequently, the opposite station generates the HP_RDI alarm.
Possible Causes:
1) The number of B1 or B2 bit errors is extremely high.
2) The received signals are heavily attenuated.
3) The fiber connector is dirty.
4) The fiber connector is loose.
5) The attenuation value specified in the fiber attenuator is extremely high or low.
6) The transmit unit at the opposite station is faulty.
7) The receive unit at the local station is faulty.

12.BD_STATUS
major

The BD_STATUS is an alarm indicating that the physical board is offline. This alarm occurs when the logical
board is created on the T2000 but the physical board is not inserted in the subrack.
Impact on System: Since the physical board is not inserted in the equipment, the data that is configured on
the NE cannot be issued to this board. Thus, configuration of services fails.
Possible Causes:
1) The board is not inserted, or it's not properly inserted.
2) The inter-board communication is faulty.
3) The board software is faulty and thus cannot communicate with the NE.
4) The board is faulty.
5) The board is cold reset or warm reset.

13.BD_VER_NMAT
major

The BD_VER_NMAT is an alarm indicating that the board software versions mismatch. If the board software
version is not consistent with that specified in the version mapping table, the BD_VER_NMAT alarm is reported.
Impact on System: In the case of the BD_VER_NMAT alarm, no services are interrupted.
Possible Causes:
1) The board software version is not consistent with that specified in the version configuration table.

14.BIP_EXC
minor

The BIP_EXC is an alarm indicating that the number of BIP bit errors exceeds the specified value. If a board
has detected that the number of BIP2 bit errors in the V5 byte exceeds the specified BIP_EXC alarm threshold value
(default value: 10-3 ), the BIP_EXC alarm is reported.
Impact on System: When the BIP_EXC alarm occurs, the VC-12 service quality is degraded.
Possible Causes:
1) Some higher-level alarms occur in the system.
2) The optical power is improper.
 3) The receive unit at the local station is faulty.
4) The transmit unit of the upstream board is faulty.

15.BIP_SD
minor

The BIP_SD is an alarm indicating that the BIP signals are degraded. If a board has detected that the number
of BIP2 bit errors in the V5 byte exceeds the specified BIP_SD alarm threshold value (default value: 10-6 ), the
BIP_SD alarm is reported.
Impact on System: When the BIP_SD alarm occurs, the quality of the services carried over the path of the
board is degraded. If lower order SNCP is configured and lower order bit error threshold-crossing switching is
enabled, this alarm will trigger the lower order bit error threshold-crossing switching. When the BIP_SD alarm
occurs, the board returns the LP_REI alarm to the opposiste end.
Possible Causes:
1) Some higher-level bit error alarms occur in the system.
2) The number of BIP2 bit errors is huge in the lower order services.
3) The transmit unit of the upstream board is faulty.
4) The receive unit at the local station is faulty.

16.COMMUN_FAIL
major

The COMMUN_FAIL is an alarm of inter-board communication failure. This alarm occurs when the
communication between the SCC and other boards is interrupted.
Impact on System: When this alarm occurs, the protection switching function of the system will fail or the
board will be unable to operate. Thus, the newly-added services go faulty.
Possible Causes:
1) The board is faulty.
2) The board is reset.

17.DOWN_E1_AIS
major

The DOWN_E1_AIS is an indication alarm of the downstream 2 Mbit/s signals. If a tributary board has
detected that the value of the downstream E1 signals is all "1"s, the DOWN_E1_AIS alarm is reported.
Impact on System: When the DOWN_E1_AIS alarm occurs, the E1 signals in the board path are unavailable.
Possible Causes:
1) A higher-level alarm, such as R_LOS, R_LOC, R_LOF or MS_AIS, occurs at the local station.
2) The UP_E1_AIS or T_ALOS alarm occurs at the local board.
3) The local board is faulty.
4) The cross-connect and timing board is faulty.

18.ETH_LOS
critical
LOS – Loss Of Signal

The ETH_LOS is an alarm indicating loss of network port connection. This alarm occurs when the Ethernet
network port cannot receive Ethernet signals.
Impact on System: When the ETH_LOS alarm occurs, the network port cannot receive data and the services
are interrupted.
 Possible Causes:
1) The port is enabled, but the network cable or fiber of the network port is improperly connected.
2) The network cable or fiber is faulty.
3) The remote transmit end is faulty.
4) The local receive end is faulty.

19.HARD_BAD
critical

The HARD_BAD is a hardware failure alarm. This alarm occurs when the board detects a hardware exception.
Impact on System: When the HARD_BAD alarm occurs, an active/standby switching is not available if the
board is a protection board, and the services may be interrupted.
Possible Causes:
1) The power supply fails.
2) The hardware detects a fault of its own.
3) The chip fails.
4) The check of a key register fails.
5) A type III BUS_ERR alarm occurs.

20.HP_RDI
minor
HP – Highorder Path – от VC4 нагоре

The HP_RDI is a remote defect indication in the higher order path.

Impact on System: When the HP_RDI alarm occurs, the local station is not affected. This alarm just shows
that the path-level services at the remote end are interrupted.
Possible Causes:
1) The HP_RDI alarm is an accompanying alarm. When the opposite station reports an alarm (such as
AU_AIS, AU_LOP, HP_TIM or HP_SLM) from the relevant path of the line board, the opposite station returns the
HP_RDI alarm to the local station.

21.HP_REI
warning

The HP_REI is a remote error indication in the higher order path.

Impact on System: When the HP_REI alarm occurs, the local station is not affected. This alarm just shows
that bit errors are received at an intermediate station, and the quality of the transmitted higher order services is
degraded.
Possible Causes:
1) The HP_REI alarm is an accompanying alarm. When an intermediate station has detected an alarm
(such as B3_EXC or B3_SD) of B3 bit errors, it returns an HP_REI alarm to the local station.
 22.HP_SLM
minor
SLM – Signal Label Mismatch

The HP_SLM is a signal label mismatch alarm in the higher order path. When a line board has detected that
the received C2 byte is inconsistent with the C2 byte to be received, the HP_SLM alarm is reported.
Impact on System: If the AU_AIS alarm is inserted when the HP_SLM alarm occurs, the path service is
interrupted. Moreover, the HP_RDI alarm is returned to the opposite station.
Possible Causes:
1) The service type is incorrectly configured.
2) The signal identification overhead (C2 byte) to be received in the higher order path does not match the
received signal identification overhead (C2 byte) at the local station. Moreover, the received C2 byte is not 0x00.

23.HP_TIM
minor

The HP_TIM is a trace identifier mismatch alarm in the higher order path.
Impact on System: If the AU_AIS alarm is inserted when the HP_TIM alarm occurs, the path service is
interrupted. Moreover, the HP_RDI alarm is returned to the opposite station.
Possible Causes:
1) The service cross-connections are incorrectly configured.
2) The J1 byte is incorrectly configured.

24.HP_UNEQ
minor

The HP_UNEQ is an alarm indicating that no signals are loaded in the higher order path, and the value of the
received C2 byte is 0x00.
Impact on System: If the AU_AIS alarm is inserted when the HP_UNEQ alarm occurs, the path service is
interrupted. Moreover, the HP_RDI alarm is returned to the opposite station.
Possible Causes:
1) No services are configured at the opposite station.
2) No services are configured at the upstream station.
3) The received C2 byte is 0.

25.HSC_UNAVAIL
minor

The HSC_UNAVAIL is an alarm indicating that the standby cross-connect board is unavailable. This alarm is
reported by the standby cross-connect board only.
Impact on System: When the HSC_UNAVAIL alarm occurs, the services may be interrupted in the case of
cross-connect board switching.
Possible Causes:
1) After a successful cold reset of the standby cross-connect board, the time that elapsed is less than five
minutes.
2) For the service board, its logical board and physical board do not match.
3) The standby cross-connect board has a type II BUS_ERR alarm.
4) A service board detects that the standby cross-connect board is faulty.
5) The standby cross-connect board is in the bad status.
 26.IN_PWR_ABN
major
in_pwr_abn – input power abnormal

The IN_PWR_ABN is an alarm indicating that the input optical power is asbnormal.
Impact on System: When the IN_PWR_ABN alarm occurs, the service transmission performance is affected.
In the case of severe alarm, the services are interrupted.
Possible Causes:
1) The fiber is bent heavily.
2) The fiber connection is dirty.
3) The fiber connector is loose.
4) The transmit unit at the opposite station is faulty.
5) The receive unit at the local station is faulty.

27.IN_PWR_HIGH
critical

The IN_PWR_HIGH is an alarm of too high input power. This alarm occurs when a board detects that the
actual input power is higher than the upper threshold of the input power reference value.
Impact on System: After the IN_PWR_HIGH alarm occurs, the services at the optical interface contain bit
errors. Too high input power also causes damages to the laser.
Possible Causes:
1) The launched optical power at the opposite station is too high.
2) The type of the selected optical module is not proper.

28.IN_PWR_LOW
critical

The IN_PWR_LOW is an alarm of too low input power. This alarm occurs when a board detects that the
actual input power is lower than the lower threshold of the input power reference value.
Impact on System: After the IN_PWR_LOW alarm occurs, the services at the optical interface contain bit
errors.
Possible Causes:
1) The launched optical power at the opposite station is too low.
2) The fiber performance is degraded.
3) The type of the selected optical module is not proper.

29.J0_MM
minor

The J0_MM is a trace identifier mismatch alarm. When a line board has detected that the received J0 byte at
the relevant optical interface is inconsistent with the J0 byte to be received, the J0_MM alarm is reported.
Impact on System: When the J0_MM alarm occurs, the services are not affected.
Possible Causes:
1) The J0 byte to be transmitted at the opposite end is inconsistent with the J0 byte to be received at the
local end.
 30.LCAS_BAND_DECREASED
minor

The LCAS_BAND_DECREASED is an alarm indicating that the LCAS service bandwidth decreased. This
alarm occurs when the LCAS function is enabled, part or all of the physical paths that are bound with the
VCTRUNK are in the idle state and carry no payload, because the path are not successfully added or the paths fail
after being added.
Impact on System: When the LCAS_BAND_DECREASED alarm occurs, it indicates that the service
bandwidth has decreased. If the bandwidth available for carrying services is lower than the configured bandwidth,
the services will lose packets. If the bandwidth all fails, the services on the VCTRUNK will be interrupted.
Possible Causes:
1) The failure in the physical paths bound with the VCTRUNK causes the alarms such as AIS, LOP,
UNEQ, LOM, and SD.
2) The number of the uplink or downlink timeslots bound with the VCTRUNK is inconsistent with the
number of the downlink or uplink timeslots bound with the corresponding opposite VCTRUNK.
3) The cross-connection is incorrectly bound.

31.LCAS_FOP
major

The LCAS_FOP is an alarm indicating the failure of the LCAS protocol. When the LCAS protocol detects
abnormalities that may cause the negotiation failure, this alarm occurs.
Impact on System: When the LCAS_FOP alarm occurs, it indicates that the timeslot event is abnormally
reported. The bandwidth may be decreased or the services may be interrupted.
Possible Causes:
1) Only unidirectional services are configured.
2) Bidirectional services are configured, but the services in one direction fail.
3) The LCAS function is disabled at the opposite end.

32.LCAS_FOPR
major

The LCAS_FOPR is an alarm indicating the failure of the LCAS protocol in the receive direction. When the
sink end of the LCAS module detects abnormalities, the LCAS negotiation is unavailable or incorrect and this alarm
occurs.
Impact on System: When the LCAS_FOPR alarm occurs, it indicates that the protocol state machine in the
receive direction is in confusion. The negotiation may be abnormal.
Possible Causes:
1) The downlink VCG receives repeated sequence numbers due to wrong configurations or link bit errors.
2) The LCAS function of the opposite VCG is disabled.
3) The downlink VCG simultaneously receives the FIXED and other LCAS control bytes due to wrong
configurations or link bit errors.
4) The cross-connection is incorrectly bound.

33.LCAS_PLCR
minor

The LCAS_PLCR is an alarm indicating partial loss of capacity in the LCAS receive direction. When the
LCAS function of the VCTRUNK is enabled, in the receive direction, the number of paths that carry load is less
than the number of paths configured and is not zero.
Impact on System: When the LCAS_PLCR alarm occurs, it indicates that the available bandwidth in the
receive direction is reduced. The services are not interrupted.
 Possible Causes:
1) Bidirectional services are not configured.
2) The number of members in the uplink of the opposite end is less than that in the downlink of the local
end.
3) The path communication fails because the cross-connection is wrong or the physical link is improperly
connected.

34.LCAS_PLCT
minor

The LCAS_PLCT is an alarm indicating partial loss of capacity in the LCAS transmit direction. When the
LCAS function of the VCTRUNK is enabled, in the transmit direction, the number of paths that carry load is less
than the number of paths configured and is not zero.
Impact on System: When the LCAS_PLCT alarm occurs, it indicates that the available bandwidth in the
transmit direction is reduced. The services will lose packets when the actual service traffic is larger than the
available bandwidth in the transmit direction.
Possible Causes:
1) Bidirectional services are not configured.
2) The number of members in the downlink of the opposite end is less than that in the uplink of the local
end.
3) The path communication fails because the cross-connection is wrong or the physical link is improperly
connected.

35.LCAS_TLCR
major

The LCAS_TLCR is an alarm indicating the total loss of capacity in the LCAS receive direction. When the
LCAS function of the VCTRUNK is enabled, in the receive direction, the number of paths that carry load is zero,
whereas the number of paths configured is not zero.
Impact on System: When the LCAS_TLCR alarm occurs, it indicates that the available bandwidth in the
receive direction is reduced to zero. The services in the receive direction are interrupted.
Possible Causes:
1) Bidirectional services are not configured.
2) The uplink of the opposite end is not bound with members.
3) The path communication fails because the cross-connection is wrong or other alarms are present.

36.LCAS_TLCT
major

The LCAS_TLCT is an alarm indicating total loss of capacity in the LCAS transmit direction. When the
LCAS function of the VCTRUNK is enabled, in the transmit direction, the number of paths that carry load is zero,
whereas the number of paths configured is not zero.
Impact on System: When the LCAS_TLCT alarm occurs, it indicates that the available bandwidth in the
transmit direction is reduced to zero. The services in the transmit direction are interrupted.
Possible Causes:
1) The downlink of the opposite end is not bound with members.
2) The path communication fails because the cross-connection is wrong or other alarms are present.
 37.LP_RDI
minor
LP – Lowerorder Path – до VC-3

The LP_RDI is a remote defect indication alarm in the lower order path. If a board has detected that bit 8 of
the V5 byte in the VC-12 lower order path is 1 or bit 5 of the G1 byte in the VC-3 lower order path is 1, the LP_RDI
alarm is reported.
Impact on System: When the LP_RDI alarm occurs, the local station is not affected. This alarm just shows
that the opposite station fails to receive signals.
Possible Causes:
1) The opposite station has received the TU_AIS, TU_LOP, LP_TIM, LP_UNEQ, HP_LOM or HP_PLM
alarm.
2) The receive unit at the opposite station is faulty.
3) The transmit unit at the local station is faulty.

38.LP_REI
minor

The LP_REI is a remote error indication alarm in the lower order path. When a board has detected that bit 3 of
the V5 byte is 1 or any of bits 1–4 of the G1 byte is 1, the LP_REI alarm is reported.
Impact on System: When the LP_REI alarm occurs, the services at the local station are not affected. This
alarm just shows that some bit errors occur in the signals received in the lower order path at the opposite station.
Possible Causes:
1) The LP_REI alarm is an accompanying alarm. When an tributary board at the opposite station has
detected a bit error alarm, such as BIP_SD, BIP_EXC, B3_SD or B3_EXC, it returns an LP_REI alarm to the local
station.
2) Bit errors are received in the lower order path at the opposite station.
3) The transmit part at the local station is faulty.

40.LP_SLM
minor

The LP_SLM is a signal label mismatch alarm in the lower order path. If a board has detected that the signal
label mismatch event occurs in the V5 or C2 byte, the LP_SLM alarm is reported.
Impact on System: When the LP_SLM occurs, the mapping structure of the lower order services received on
the tributary board is incorrect. As a result, the services are abnormal (VC12: V5[b5–b7], VC3: C2).
Possible Causes:
1) The signal label configuration for the lower order path at the local station is inconsistent with that at the
opposite station.
2) The service type is incorrectly configured.

41.LP_TIM
minor
TIM – Trace Identifier Mismach

The LP_TIM is a trace identifier mismatch alarm in the lower order path. If a board has detected that the J2 or
J1 byte does not match, the LP_TIM alarm is reported.
Impact on System: The system is not affected.
Possible Causes:
1) The trace identifier of the lower order path at the local station is inconsistent with that at the opposite
station.
2) The service cross-connection configuration is incorrect.
 42.MS_AIS
major

The MS_AIS is an indication alarm in the multiplex section. When the last three bits of the K2 byte are 111 in
five frames consecutively received on the receive side of the local optical station, the MS_AIS alarm is reported.
This alarm shows that the signals in the multiplex section corresponding to the optical interface that reports the
alarm are useless.
Impact on System: If the MSP switching or the PP switching is configured, the alarm will trigger the
protection switching. Otherwise, the services are interrupted. After the MS_AIS occurs, the board automatically
returns the MS_RDI alarm to the opposite station. Consequently, the opposite station reports the MS_RDI alarm.
Possible Causes:
1) Some higher-level alarms (such as R_LOS or R_LOF) occur in the system.
2) The working and protection cross-connect and timing boards are out of position at the opposite station.
3) The cross-connect and timing board at the opposite station is faulty.
4) The transmit unit at the opposite station is faulty.
5) The receive unit at the local station is faulty.

43.MS_RDI
minor

The MS_RDI is a remote defect indication in the multiplex section. When the last three bits of the K2 byte are
110 in five frames consecutively received on the receive side of the local optical station, the MS_RDI alarm is
reported. When the opposite station generates the MS_AIS alarm, it returns the alarm to the local station.
Impact on System: When the MS_RDI alarm occurs, the local station is not affected. This alarm just shows
that the services at the opposite station are interrupted.
Possible Causes:
1) The opposite station has received an alarm, such as R_LOS, R_LOC, R_LOF, MS_AIS, B2_EXC or
B2_SD.
2) The receive unit at the opposite station is faulty.
3) The transmit unit at the local station is faulty.

44.MS_REI
warning

The MS_REI is an indication alarm that bit errors occur at the remote end of the multiplex section. When the
receive side of the local optical station receives the M1 byte, which shows that the number of block bit errors
detected by BIP-Nx24 (B2) at the opposite station, the MS_REI alarm is reported.
Impact on System: When the MS_REI alarm occurs, the number of B2 bit errors received at the opposite
station is beyond the specified value range. The services at the local station are not affected, but the service quality
at the opposite station is degraded.
Possible Causes:
1) The number of B2 bit errors received at the opposite station is beyond the specified value range.

45.P_AIS
major

The P_AIS is an alarm indication signal of the E3/T3 service at the PDH interface. If a tributary board has
detected that the input PDH signals in the E3/T3 service are all "1"s or the detected T3 service is 1010..., the P_AIS
alarm is reported.
Impact on System: When the P_AIS alarm occurs, the AIS alarm occurs in the payload of the PDH E3/T3
service. Consequently, the E3/T3 service is unavailable.
 Possible Causes:
1) The TU_AIS or TU_LOP alarm occurs in the relevant path of the board.
2) The transmission line is faulty.
3) The PDH equipment at the opposite station output the AIS signal.

46.P_LOC
major

The P_LOC is an alarm indicating loss of input clock at the PDH side of the E3/T3 tributary board.
Impact on System: When the P_LOC alarm occurs, it indicates that the input clock at the PDH side of the
E3/T3 tributary board is lost. Synchronization fails for the services with a large amount of bit errors or the signal.
Possible Causes:
1) The input signal is not the E3/T3 signal.
2) The clock of the input PDH signal is lost.

47.P_LOF
major
LOF – Loss Of Frame

The P_LOF is an alarm indicating the loss of frame in the E3/T3 service at the PDH interface. If the PDH
service fails to receive the frame alignment signal, the P_LOF alarm is reported.
Impact on System: When the P_LOF alarm occurs, the PDH services of the board are unavailable.
Possible Causes:
1) The service frame format is incorrectly configured.
2) The board hardware is faulty.

48.P_LOS
major

The P_LOS is an alarm indicating the loss of analog signals at the 34M/45M interface.
Impact on System: When the P_LOS alarm occurs, the PDH services of the board are unavailable. If the port
that reports the P_LOS alarm is the current synchronization clock source for the NE, the synchronization clock
source switching occurs.
Possible Causes:
1) The 34M/45M service is not accessed.
2) The 34M/45M output interface at the DDF is loose or has fallen off.
3) The 34M/45M input interface at the local station is loose or has fallen off.
4) The board is faulty.
5) The cable is faulty.
6) The switch is reset.

49.POWER_ABNORMAL
major

The POWER_ABNORMAL alarm is an alarm of power supply failure. This alarm occurs if the power supply
of a board becomes abnormal.
Impact on System: When the POWER_ABNORMAL alarm occurs, the power supply functions abnormally,
and the board may not be able to function normally.
Possible Causes:
1) The power supply module of the board becomes faulty.
 50.R_LOC
critical

The R_LOC is an alarm indicating loss of clock.

Impact on System: When the R_LOC alarm occurs, the clock in the signals received by the line board at the
optical interface is lost. As a result, the services at the optical interface are unavailable. If the MSP switching or the
path protection switching is configured, the alarm will trigger the protection switching. If the port that reports the
R_LOC alarm is the current synchronization clock source for the NE, the alarm will trigger the synchronization
clock source switching. When the R_LOC alarm occurs, the board returns the MS_RDI alarm to the opposite
station.
Possible Causes:
1) The clock extraction module on the line board is faulty.
2) The cross-connect and timing board at the opposite station is faulty or is out of position.

51.R_LOF
critical

The R_LOF is an alarm indicating loss of frame on the receive side of the line. When the correct A1A2 byte is
not contained in five frames consecutively received on the receive side of the local optical station, the R_LOF alarm
is reported.
Impact on System: When the R_LOF alarm occurs, the services are interrupted, and the AIS signal is inserted
in the downstream station. When the R_LOF occurs, the system automatically returns the MS_RDI alarm to the
upstream station. Consequently, the upstream station reports the MS_RDI alarm.
Possible Causes:
1) The fiber is incorrectly connected.
2) The received optical power is improper.
3) The signals transmitted at the opposite station do not have the frame structure.
4) The receive unit at the local station is faulty.

52.R_LOS
critical

The R_LOS is an alarm indicating loss of signal on the receive side of the line.
Impact on System: When the R_LOS alarm occurs, the services are interrupted, and the AIS signal is inserted
at the downstream station. When the R_LOS occurs, the system automatically returns the MS_RDI alarm to the
upstream station. Consequently, the upstream station generates the MS_RDI alarm.
Possible Causes:
1) The fiber is cut or is not connected.
2) The laser is shut down.
3) Signals in the line are heavily attenuated.
4) The receive unit at the local station is faulty.
5) The transmit unit (including the clock board) at the opposite station is faulty.

53.R_OOF
critical

The R_OOF is an alarm indicating that the frame header can not be identified for five consecutive frames in
the received signals of the line board. The board enters the out-of-frame stated.
Impact on System: When the R_OOF alarm occurs, the services are interrupted, and the AIS signal is inserted
at the downstream station. When the R_OOF occurs, the system automatically returns the MS_RDI alarm to the
upstream station. Consequently, the upstream station generates the MS_RDI alarm. If the out-of-frame state lasts 3
ms, the loss-of-frame state is entered. The equipment generates the R_LOF alarm indicating the loss of frame.
 Possible Causes:
1) The received signals are heavily attenuated.
2) Excessive bit errors occur during transmission.
3) The synchronization clock source is severely out of synchronization.
4) The transmit unit at the opposite station is faulty.
5) The receive unit at the local station is faulty.

54.S1_SYN_CHANGE
major

The S1_SYN_CHANGE is an alarm indicating that, in the S1 byte mode, the clock source is switched. This
alarm occurs when, in the SSM mode, the traced clock source is switched.
Impact on System: When the S1_SYN_CHANGE alarm occurs, the traced clock source is switched in the
SSM mode. If the new clock source has a lower quality, pointer justifications and bit errors are generated, and as a
result the quality of services is affected.
Possible Causes:
1) There is a fiber cut.
2) The external BITS is interrupted.
3) The S1_SYN_CHANGE alarm occurs at the upstream station.

55.SYN_BAD
minor

The SYN_BAD is a synchronization source degrade alarm. This alarm occurs when the clock source traced by
the equipment is degraded.
Impact on System: When the SYN_BAD alarm occurs, tracing the relevant clock source may cause service
bit errors.
Possible Causes:
1) The quality of the traced clock source is degraded.
2) The clock board that reports the SYN_BAD alarm has a hardware failure.

56.SECU_ALM
major

The SECU_ALM is an alarm indicating that an illegal user fails to log in to the NE.
Impact on System: The SECU_ALM alarm has the following impact on the system:
The SECU_ALM alarm is ended soon after it is reported. When the SECU_ALM occurs, an illegal user fails to log
in to the NE. When the password to a user account is incorrectly entered three times, the user account is forbidden
temporarily. After two minutes, the user can log in to the NE again.
Possible Causes:
1) An illegal user tries to log in to the EN.

57.SYNC_FAIL
major

The SYNC_FAIL is an alarm indicating that the batch backup of the databases of the active and standby SCC
boards fails.
Impact on System: The synchronization failure between the active and standby SCC boards results in the
failure of the active/standby protection function of the SCC boards.
 Possible Causes:
1) The software versions of the active and standby SCC boards are inconsistent.
2) The communication fails during the batch backup of the databases of the active and standby SCC
boards.
3) Message sending fails or the database is detected damaged during the batch backup of the databases of
the active and standby SCC boards.

58.T_ALOS
major

The T_ALOS is an alarm indicating the loss of analog signals at the E1 or T1 interfaces. If no service signals
are input at the 2 Mbit/s port, the T_ALOS alarm is reported.
Impact on System: When the T_ALOS alarm occurs, the PDH services are interrupted. If the interface that
reports the P_LOS alarm is the current synchronization clock source for the NE, the synchronization clock source
switching occurs. When the T_ALOS alarm occurs, the tributary board will insert the E1_AIS signal.
Possible Causes:
1) The E1 or T1 services are not accessed.
2) The output port of the E1 or T1 interface on the DDF side is disconnected or loose.
3) The cable is faulty.
4) The interconnected equipment is faulty.
5) The interface board is faulty.
6) The board is faulty.

59.T_LOC
major

The T_LOC is an alarm indicating that there is no clock on the transmit line side. This alarm occurs if there is
no clock on the line side of a board when a service is being transmitted.
Impact on System: When the T_LOC alarm occurs, the services are interrupted.
Possible Causes:
1) The cross-connect and timing board is faulty or offline, which causes no clock on the receive line side.

60.T_LOS
major

The T_LOS is an alarm indicating the loss of input signal at the line side in the transmit direction. This alarm
occurs when no optical signal is detected at the line side in the transmit direction.
Impact on System: When the T_LOS alarm occurs, no optical signal is received on the port. Accordingly, the
communication cannot be performed and the data cannot be transmitted.
Possible Causes:
1) The service board is not installed well or is faulty.
2) The line board is not installed well or is faulty.
3) The cross-connect board is not installed well or is faulty.
4) The clock source of the active and standby cross-connect boards fails or is of poor quality.
 61.TU_AIS
major

The TU_AIS is a TU alarm indication signal. If a board has detected that the signals in the TU path are all
"1"s, the TU_AIS alarm is reported.
Impact on System: When the TU_AIS alarm occurs, the services in the path are interrupted.
Possible Causes:
1) Some higher-level alarms, such as R_LOS, R_LOF or HP_SLM, occur in the system.
2) The service cross-connection configuration is incorrect.
3) The relevant path at the opposite station is faulty.
4) The cross-connect board is faulty.

62.TU_LOP
major
LOP – Loss Of Pointer

The TU_LOP is an alarm indicating the loss of pointer in the TU. If a board has detected that the TU-PTR
value is an invalid pointer or NDF reversion in eight consecutive frames, the TTU_LOP alarm is reported.
Impact on System: When the TU_LOP alarm occurs, the services in the TU path are interrupted. When the
TU_LOP alarm occurs, the system returns the LP_RDI alarm to the opposite station.
Possible Causes:
1) Some higher-level alarms, such as R_LOS, R_LOF or HP_SLM, occur in the system.
2) The service cross-connection configuration is incorrect.
3) The relevant path at the opposite station is faulty.
4) The cross-connect and timing board is faulty.

63.UP_E1_AIS
minor

The UP_E1_AIS is an alarm indication of the upstream 2 Mbit/s signals. If a tributary board has detected that
the upstream E1 signals are all "1"s, the UP_E1_AIS alarm is reported.
Impact on System: When the UP_E1_AIS alarm occurs, the E1 signals are unavailable.
Possible Causes:
1) The TU_LOP, T_ALOS or TU_AIS alarm occurs at the opposite station.
2) A hardware fault alarm, such as PLL_FAIL or CHIP_FAIL, occurs on the board at the opposite station.
3) The local board is faulty.

64.VC_AIS
critical

The VC_AIS is an alarm indication signal of the virtual channel (VC) connection. When a forward or
backward VC connection that is set with the segment and end point attribute receives the AIS cell, the VC_AIS
alarm is reported, showing that the upstream services are abnormal.
Impact on System: The continuity check (CC) sink of an upstream connection is activated, but the relevant
CC source is not activated, and no user cells are received because the current bandwidth is zero. In this case, the
upstream station reports the CC_LOC alarm, and the AIS cells are inserted at the downstream station. Consequently,
the local station generates the VC_AIS alarm. The services are not interrupted, but are unavailable in the
connection. In other cases, the relevant VC connections have been interrupted when the VC_AIS alarm occurs.
Moreover, the AIS cells are continuously inserted at the downstream station. In addition, the RDI cells are returned
to the upstream station.
 Possible Causes:
1) An NE of the upstream connection fails to receive signals in the SDH path. For example, an SDH alarm,
such as R_LOS, R_LOF, MS_AIS, AU_AIS, AU_LOP, TU_AIS or TU_LOP, occurs at the NE.
2) The LCD alarm occurs at an ATM port of the upstream connection.
3) The CC sink of an upstream connection is activated, but the relevant CC source is not activated, and no
user cells are received because the current bandwidth is zero. In this case, the upstream station reports the CC_LOC
alarm, and the AIS cells are inserted at the downstream station. Consequently, the local station generates the
VC_AIS alarm.
4) The ATM processing chip of the board is faulty.

65.VC_RDI
major

The VC_RDI is a remote defect indication of the virtual channel (VC) connection. When a forward or
backward VC connection that is set with the segment end point attribute receives the RDI cells, the VC_RDI is
reported, showing that the downstream services are abnormal.
Impact on System: When the VC_RDI alarm occurs, the services are not affected. This alarm just shows that
the services in the receive direction of the downstream VC connection are abnormal. The AIS cells are received in a
segment point of the connection, and the RDI cells are returned to the upstream VC connection.
Possible Causes:
1) The VC_AIS alarm occurs in the receive direction of the downstream connection.
2) The ATM processing chip of the board is faulty.