SJ-20140402111513-008-ZXMW NR8120 (V2.03.03) Alarm and Notification Handling Reference - 606555 PDF

ZXMW NR8120
Digital Microwave Transmission System
Alarm and Notification Handling Reference

Version: V2.03.03
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://support.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2014 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited.
Additionally, the contents of this document are protected by
contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit the ZTE technical support website http://support.zte.com.cn to inquire for related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No.
Revision Date
Revision Reason
R1.0
20140528
First edition
Serial Number: SJ-20140402111513-008

Publishing Date: 20140528(R1.0)
SJ-20140402111513-008|20140528(R1.0)
ZTE Proprietary and Confidential
Contents
About This Manual ......................................................................................... I
Chapter 1 Overview .................................................................................... 1-1
Chapter 2 Alarm.......................................................................................... 2-1
2.1 Environment Alarm............................................................................................. 2-1
2.1.1 401 DC input voltage abnormal ................................................................ 2-1
2.1.2 4001 Outdoor temperature alarm .............................................................. 2-2
2.1.3 4011 Outdoor access-control alarm .......................................................... 2-3
2.1.4 4012 Outdoor moisture alarm ................................................................... 2-3
2.1.5 4013 Outdoor smoke alarm ...................................................................... 2-4
2.1.6 4016 Outdoor lightning protection module alarm ........................................ 2-5
2.1.7 4017 Outdoor power supply unit alarm ...................................................... 2-5
2.1.8 4018 Outdoor fan alarm ........................................................................... 2-6
2.1.9 9301 Power environment under-temperature ............................................. 2-6
2.1.10 9302 Power environment over-temperature ............................................. 2-7
2.1.11 9303 Power environment invalid-temperature .......................................... 2-8
2.1.12 9304 Power environment under-humidity ................................................ 2-9
2.1.13 9305 Power environment over-humidity .................................................. 2-9
2.1.14 9306 Power environment invalid-humidity ............................................. 2-10
2.1.15 9307 Power smog alarm .......................................................................2-11
2.1.16 9308 Power flood alarm ........................................................................2-11
2.1.17 9309 Power magnetic door alarm ......................................................... 2-12
2.1.18 134218750 Dry contact alarm ............................................................... 2-13
2.1.22 134243759 MSTP port BPDU Guard .................................................... 2-15
2.1.23 134243760 MSTP port LOOP Guard .................................................... 2-15
2.1.24 134243761 MSTP port ROOT Guard .................................................... 2-16
2.1.25 134257778 FAN Control Temperature beyond threshold ........................ 2-16
2.1.26 134257780 Device overheated ............................................................. 2-17
2.2 Equipment Alarm.............................................................................................. 2-18
2.2.1 1002 Board is absent ............................................................................. 2-18
2.2.2 1004 Board is not configured .................................................................. 2-18
I
SJ-20140402111513-008|20140528(R1.0)
2.2.3 9001 AC input switch off ........................................................................ 2-19

2.2.4 9002 AC power off ................................................................................. 2-20
2.2.5 9003 SPD-C broken .............................................................................. 2-20
2.2.6 9004 SPD-D broken .............................................................................. 2-21
2.2.7 9005 AC under-voltage .......................................................................... 2-22
2.2.8 9006 AC over-voltage ............................................................................ 2-23
2.2.9 9101 SMR broken ................................................................................. 2-23
2.2.10 9102 SMR output over-voltage ............................................................. 2-24
2.2.11 9103 SMR output over-current .............................................................. 2-25
2.2.12 9104 SMR fan fault .............................................................................. 2-25
2.2.13 9105 SMR PFC fault ............................................................................ 2-26
2.2.14 9106 SMR input over-voltage and power off .......................................... 2-26
2.2.15 9107 SMR input under-voltage and power off ........................................ 2-27
2.2.16 9108 SMR host heater over-temp and power off .................................... 2-28
2.2.17 9109 SMR environment over-temp and power off .................................. 2-28
2.2.18 9110 SMR environment over-temp and load-reduction ........................... 2-29
2.2.19 9111 SMR under-voltage and load-reduction ......................................... 2-30
2.2.20 9112 SMR fuse broken ........................................................................ 2-30
2.2.21 9113 SMR communication failure ......................................................... 2-31
2.2.22 9201 DC output under-voltage .............................................................. 2-32
2.2.23 9202 DC output over-voltage ................................................................ 2-32
2.2.24 9203 DC load loop broken .................................................................... 2-33
2.2.25 9204 Battary loop broken ..................................................................... 2-34
2.2.26 9205 Battary under-voltage .................................................................. 2-34
2.2.27 9206 Battary over-temp ........................................................................ 2-35
2.2.28 9207 Power under-temp and power off .................................................. 2-36
2.2.29 9208 First power off ............................................................................. 2-37
2.2.30 9209 Second power off ........................................................................ 2-38
2.2.31 9210 DC SPD abnormal ....................................................................... 2-39
2.2.32 9211 Load breaker abnoraml ................................................................ 2-39
2.2.33 9212 Battary test failure ....................................................................... 2-40
2.2.34 9213 Battery discharge ........................................................................ 2-41
2.2.35 134217728 Clock reference source lost ................................................ 2-41
2.2.36 134217730 RTC clock alarm ................................................................ 2-43
2.2.37 134217735 Clock module fault ............................................................. 2-44
2.2.38 134217739 EEPROM error alarm ......................................................... 2-45
2.2.39 134218754 RPUB Under Voltage ......................................................... 2-45
II
SJ-20140402111513-008|20140528(R1.0)
2.2.40 134218778 CPU overload .................................................................... 2-46

2.2.41 134218779 Debug ip illegal .................................................................. 2-47
2.2.42 134218796 Actual Use MAC illegal ....................................................... 2-47
2.2.43 134218797 Device MAC conflict ........................................................... 2-48
2.2.44 134218798 Link between IDU and AOU is interrupted ............................ 2-48
2.2.45 134218800 Running cooperate-manged AOU version abnormal ............. 2-49
2.2.46 134218802 Service unauthorized ......................................................... 2-49
2.2.47 134218803 Service frozen ................................................................... 2-50
2.2.48 134237778 Loopback state in TDM port ................................................ 2-51
2.2.49 134237936 PRBS array transmit in E1 port ........................................... 2-52
2.2.50 134237937 MCLK signal of RTE is abnormal ........................................ 2-54
2.2.51 134237939 Force-E1-AIS ..................................................................... 2-54
2.2.52 134237940 Loopback state in Air E1 port .............................................. 2-55
2.2.53 134239932 Rf unit configuration mode invalid ....................................... 2-56
2.2.54 134239940 Rf unit power supply abnormal ............................................ 2-57
2.2.55 134239956 RDI alarm .......................................................................... 2-57
2.2.56 134239959 HC CFG data inconsistent in two ends of the link ................. 2-58
2.2.57 134239964 Rf unit type mismatch ......................................................... 2-58
2.2.58 134239965 Scan frequency enabled alarm ............................................ 2-59
2.2.59 134239966 CRC check fails ................................................................. 2-59
2.2.60 134241731 Optical Signal Lost ............................................................. 2-60
2.2.61 134241739 SFP speed does not match with configuration ...................... 2-61
2.2.62 134241740 ETH port SFP power abnormal ........................................... 2-62
2.2.63 134241741 MAC overflow of port .......................................................... 2-62
2.2.64 134243749 OSPF route has been discarded ......................................... 2-63
2.2.65 134243765 1588 clock PTP service setup failure ................................... 2-64
2.2.66 134243766 1588 clock PTP link abnormal ............................................. 2-64
2.2.67 134243767 1588 reference clock source unavailable ............................. 2-65
2.2.68 134243768 The Capture status of 1588 clock timeout ............................ 2-65
2.2.69 134243779 Device IP conflict ............................................................... 2-66
2.2.70 134317741 Loopback state in IF or modem port .................................... 2-66
2.2.71 134317764 RF outer loopback enabled ................................................. 2-67
2.2.72 134317765 TDM route has been discarded ........................................... 2-68
2.3 Processing alarm ............................................................................................. 2-68
2.3.1 6201 Software loading failure ................................................................. 2-68
2.3.2 6206 Running software version fault ....................................................... 2-69
2.3.3 6213 Board inserted incorrectly .............................................................. 2-71
III
SJ-20140402111513-008|20140528(R1.0)
2.3.4 6223 Firmware does not take effect ........................................................ 2-71

2.3.5 6224 Main BOOT CRC error .................................................................. 2-72
2.3.6 6225 Version has been roll back ............................................................. 2-73
2.3.7 134218745 Insufficient flash memory ...................................................... 2-73
2.3.8 134243738 OSPF interface configuration error ........................................ 2-74
2.3.9 134243739 OSPF virtual link interface configuration error ........................ 2-74
2.4 Communication Alarm ...................................................................................... 2-75
2.4.1 134217734 Received signal level alarm .................................................. 2-75
2.4.2 134217736 UAS alarm of radio .............................................................. 2-76
2.4.3 134237731 E1-ALOS ............................................................................. 2-76
2.4.4 134237759 E1-Code-Violation ................................................................ 2-78
2.4.5 134237763 Loss of Frames alarm .......................................................... 2-79
2.4.6 134237764 Late Frames alarm ............................................................... 2-80
2.4.7 134237765 Malformed Frames alarm ..................................................... 2-81
2.4.8 134237766 Misconnection alarm ............................................................ 2-82
2.4.9 134237767 Jitter Buffer Overrun alarm ................................................... 2-82
2.4.10 134237934 E1-AIS .............................................................................. 2-83
2.4.11 134237938 Air-E1-AIS ......................................................................... 2-85
2.4.12 134239928 Radio link failure alarm ....................................................... 2-85
2.4.13 134239929 Baseband alarm ................................................................ 2-86
2.4.14 134239930 RF unit fault ....................................................................... 2-87
2.4.15 134239931 Transmission unit invalid .................................................... 2-89
2.4.16 134239935 RF mute ............................................................................ 2-89
2.4.17 134239937 Modem part unlock ............................................................ 2-90
2.4.18 134239938 Protection function failure ................................................... 2-91
2.4.19 134239962 RF unit fatal error ............................................................... 2-92
2.4.20 134239963 RF unit error ...................................................................... 2-93
2.4.21 134239967 Security Link Id Inconsistent ............................................... 2-94
2.4.22 134241729 Ethernet port disconnected ................................................. 2-94
2.4.23 134241733 Optical module not in position ............................................. 2-96
2.4.24 134243751 RMEP CCM packet lost ...................................................... 2-96
2.4.25 134243752 RMEP CCM packet error .................................................... 2-97
2.4.26 134243753 RMEP Mac Status error ...................................................... 2-98
2.4.27 134243754 RMEP RDI ........................................................................ 2-98
2.4.28 134243755 Ethernet devices cross-connected ....................................... 2-99
2.4.29 134243769 EFM local link fault ............................................................. 2-99
2.4.30 134243770 EFM remote link fault ........................................................2-100
IV
SJ-20140402111513-008|20140528(R1.0)
2.4.31 134243771 EFM discovery process failure ...........................................2-100

2.4.32 134243776 EFM local link lost .............................................................2-101
2.4.33 134243783 APS Message detecting abnormal .....................................2-102
2.4.34 134243784 Ethernet client signal fail ....................................................2-102
2.4.35 134317734 Rf unit communication is interrupted ...................................2-103
2.5 QoS Alarm......................................................................................................2-104
2.5.1 134243772 EFM local link event ............................................................2-104
2.5.2 134243778 EFM loopback alarm ...........................................................2-104
Chapter 3 Notification ................................................................................ 3-1

3.1 Equipment Alarm................................................................................................ 3-1
3.1.1 10001 Board power-on completed ............................................................ 3-1
3.1.2 10006 Board power-on failed ................................................................... 3-1
3.1.3 134243731 8032 port blocked .................................................................. 3-2
3.1.4 134243732 8032 port unblocked .............................................................. 3-3
3.1.5 134243785 ERPS port blocked ................................................................ 3-3
3.1.6 134243786 ERPS port unblocked ............................................................. 3-4
3.1.7 134257783 CRC error in flash .................................................................. 3-4
3.1.8 134317731 Configuraiton file reloaded ...................................................... 3-5
3.1.9 134317740 IF and RF changeover ........................................................... 3-5
3.1.10 134317745 ACM change ....................................................................... 3-6
3.1.11 134317746 System time is modified ........................................................ 3-7
3.1.12 134317747 Clear performance data ........................................................ 3-7
3.1.13 134317749 Main clock reference source change ..................................... 3-8
3.2 Communication Alarm ........................................................................................ 3-8
3.2.1 134243728 LLDP global enable status changed ........................................ 3-8
3.2.2 134243729 Local management address of LLDP changed ......................... 3-9
3.2.3 134243730 Neighbor information of LLDP changed ................................. 3-10
3.2.4 134243780 MEP receive AIS packet ....................................................... 3-10
3.2.5 134243781 MEP receive LCK packet .......................................................3-11
3.2.6 134317743 SNCP channel changeover ...................................................3-11
3.2.7 134317760 SNCP+ channel changeover ................................................ 3-12
3.3 Processing alarm ............................................................................................. 3-12
3.3.1 134243733 OSPF interface status changed ............................................ 3-12
3.3.2 134243734 OSPF virtual interface status changed .................................. 3-13
3.3.3 134243735 OSPF neighbor status changed ............................................ 3-13
3.3.4 134243736 OSPF virtual neighbor status changed .................................. 3-14
3.3.5 134243740 OSPF interface receiving incorrect packet ............................. 3-15
V
SJ-20140402111513-008|20140528(R1.0)
3.3.6 134243741 OSPF virtual link interface receive wrong packet .................... 3-15
3.3.7 134243742 OSPF interface receiving incorrect LSR packet ...................... 3-16
3.3.8 134243743 OSPF receive DD pkt with wrong seq number ....................... 3-16
3.3.9 134243744 Receive Hello Packet without local router .............................. 3-17
3.3.10 134243745 Timeout for receiving OSPF hello packet ............................. 3-17
3.3.11 134243746 OSPF interface disabled by administrator ............................ 3-18
3.3.12 134243747 OSPF interface disabled physically ..................................... 3-18
3.3.13 134243748 Interface's neighbor changed .............................................. 3-19
3.3.14 134243762 SG add failed for parameter error ........................................ 3-19
3.3.15 134243763 The port failing to be aggregated into a LAG ........................ 3-20
3.3.16 134243764 The port quitting a LAG due to exception ............................. 3-20
3.3.17 134317735 Rf unit firmware upgraded .................................................. 3-21
3.4 QoS Alarm....................................................................................................... 3-22
3.4.1 134243773 EFM remote link event ......................................................... 3-22
3.4.2 134243774 EFM loopback indication ...................................................... 3-23
3.4.3 134243777 Local Discovery process reset .............................................. 3-23
3.5 Environment Alarm........................................................................................... 3-24
3.5.1 134317750 IDU Over-temperature protection .......................................... 3-24
VI
SJ-20140402111513-008|20140528(R1.0)
About This Manual

Purpose
This manual describes how to handle NR8120 alarms and notifications.
Intended Audience
This manual is intended for:
l
l
Maintenance engineers
On-duty staff in equipment room
What Is in This Manual

This manual has the following chapters:
Chapter
Description
1, Overview
Gives an overview of NR8120 alarms and notifications.
2, Alarms
Describes the alarms in terms of alarm properties, probable causes,

effect on the system, and handling procedure.
3, Notifications
Describes the notifications in terms of notification properties, probable

causes, effect on the system, and handling procedure.
I
SJ-20140402111513-008|20140528(R1.0)
This page intentionally left blank.
II
SJ-20140402111513-008|20140528(R1.0)
Chapter 1
Overview
Functions of Fault Management
The fault management system collects fault information from all the NEs in the managed
network in near real-time, such as boards, links, databases, and servers, and then
displays the collected fault information in the format of alarm or notification. The fault
management system helps the system administrator quickly locate and resolve faults
in the managed network. It also provides telecom operators, network management
departments, and equipment vendors with correct and timely alarm data to ensure stable
network operations.
Fault Indication
The fault management system indicates a fault or event occurring in the network in the
form of alarm or notification.
l
A fault is indicated in the form of alarm when it persists and affects the reliability
and services of the system. An alarm will be cleared only after the fault is resolved.
Immediate troubleshooting is required when alarms occur.
A notification indicates a non-repeatable or instantaneous fault or event in the
system, for example, board reset and signaling overload. Such a fault or event is
normally caused by a sudden environment change or other accidental factors. No
special handling is required because the fault or event causing a notification can be
automatically handled by the system. However, a frequently-reported notification
requires troubleshooting.
Alarm Format
The alarms defined for the NR8120are provided with the information such as property and
possible causes. For details, refer to Table 1-1.
Table 1-1 Alarm Format Description
Item
Description
Alarm Code
Uniquely identifies an alarm or an notification.
Alarm Information
Summarizes the fault information, such as the fault cause and phenomenon.
1-1
SJ-20140402111513-008|20140528(R1.0)
ZXMW NR8120 Alarm and Notification Handling Reference
Item
Description
Alarm Level
There are four alarm/notification severity levels, which are indicated in

descending order of severity as Critical, Major, Minor, and Warning.
l
Critical: indicates a fault that causes failures of system operations or

service capabilities. Immediate troubleshooting is required when a critical
alarm is reported.
Major: indicates a fault that seriously impacts proper system operations or

reduces service capabilities. Clearing the fault to restore the system as
soon as possible is required when a major alarm occurs.
Minor: indicates a fault that slightly influences proper system operations or

reduces service capabilities. Proper measures should be taken to clear
the fault in a timely manner and prevent the occurrence of more severe
alarms when a major alarm occurs.
Warning: indicates a fault that has a potential or gradual impact on proper

system operations or service capabilities. Warning messages need to
be analyzed and proper measures should be taken to clear the fault in a
timely manner and avoid more severe alarms.
The impact degree described in the definition of alarm severity refers to the
impact on a single index, for example, reliability or security. Once the impact
on any index reaches the specified threshold, the severity level of the alarm
can be roughly determined. If an alarm has an impact on multiple indices, its
severity level should be escalated accordingly.
Alarm Type
Based on the triggering condition and system impact, alarms/notification can

be classified into the following five types:
l
Equipment alarm: related with equipment hardware faults.
Communication alarm: related with information transmission faults (ITU-T

Recommendation X.733).
Processing error alarm: related with software or processing faults (defined

in ITU-T Recommendation X.733).
Environmental alarm: related with the environment where the equipment is

located (defined in ITU-T Recommendation X.733).
l
Probable Cause
QoS alarm: related with equipment operation performance or indexes.
Provides probable alarm/notification causes to help users troubleshoot, find

preventive measures, and restore the system to normal state in a timely
manner.
System Impact
Provides the consequence of each alarm/notification and the impact on the

system and services.
1-2
SJ-20140402111513-008|20140528(R1.0)
Chapter 1 Overview
Item
Description
Handling
Provides the troubleshooting steps and suggestions.
Suggestion
During the alarm handling process, the following tips needs your attention:
l
After recording the fault information, O&M personnel needs to handle the
fault step by step as suggested. If there is no otherwise specified and the
fault is solved (that is, alarm is cleared), the alarm handling process ends.
If the fault persists, go to the next step.
If fault cannot be removed, contact the local ZTE office.
1-3
SJ-20140402111513-008|20140528(R1.0)
1-4
SJ-20140402111513-008|20140528(R1.0)
Chapter 2
Alarm
Table of Contents
Environment Alarm.....................................................................................................2-1
Equipment Alarm......................................................................................................2-18
Processing alarm .....................................................................................................2-68
Communication Alarm ..............................................................................................2-75
QoS Alarm .............................................................................................................2-104
2.1 Environment Alarm

2.1.1 401 DC input voltage abnormal
Alarm Property
l
l
l
l
Alarm Code:401
Alarm Information:This alarm is reported when the DC input voltage is out of range
and cleared when the voltage becomes normal.
Alarm Level:Major
Alarm Type:Environment Alarm
Sub-code Description
0.Over-voltage;
1.Under-voltage.
System Impact
1.
2.
Board Status:The power board may be faulty.

Service Impact: The board or system cannot operate properly. The services carried
on the board are interrupted.
Probable Cause
1. The input voltage of PM board is higher than the upper threshold 60V, known as
overvoltage.
2. The input voltage of PM board is lower than the lower threshold 40V, known as
undervoltage.
2-1
SJ-20140402111513-008|20140528(R1.0)
Handling Suggestion
1. For under-voltage:
(1) Ensure that the PM board is configured on the GUI and well conected by the power
line.
(2) Use a multimeter or other tools to check the input voltage of DC supply system. If
the voltage is lower than 40V, replace the DC supply. If the voltage is higher than 40V,
replace the PM board.
2. For Over-voltage: Use a multimeter or other tools to check the output voltage of DC
supply system. If the voltage is higher than or equal to 60V, replace the DC supply
system. If the voltage is lower than 60V, replace the PM board.
2.1.2 4001 Outdoor temperature alarm

Alarm Property
l
l
l
l
Alarm Code:4001
Alarm Information:The temperature of the outdoor monitoring device is abnormal.
Alarm Level:Minor
1. Temperature is low;
2. Temperature is high;
3. Temperature is invalid.
System Impact
Outdoor is abnormal,don't affect system.
Probable Cause
1.
2.
3.
4.
5.
Dustproof net is blocked.

Air conditioner is faulty.
Heat exchanger is faulty.
Threshold Configuration error exists.
Environment Monitor Unit is faulty.
Handling Suggestion
1. Clean dustproof net.
2. Ensure that air conditioner operation is normal.
3. Check whether the heat exchanger is faulty.If yes,please refer to the corresponding
handling manual.
2-2
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
2.1.3 4011 Outdoor access-control alarm

Alarm Property
l
l
l
l
Alarm Code:4011
Alarm Information:The access-control module of the outdoor monitoring device is
abnormal.
Alarm Level:Major
None
System Impact
Outdoor is abnormal,don't affect system
Probable Cause
1. The door is not closed.
2. The environment monitoring unit is faulty.
Handling Suggestion
1. Ensure that the rack door is closed.
2. Replace the sensor cable of door access control.
3. Replace FCE board.
2.1.4 4012 Outdoor moisture alarm

Alarm Property
l
l
l
l
Alarm Code:4012
Alarm Information:The moisture condition of the outdoor monitoring device is
abnormal.
Alarm Level:Minor
None
System Impact
2-3
SJ-20140402111513-008|20140528(R1.0)
Probable Cause
1. Base station is flooded.
2. Environment Monitor Unit is faulty.
Handling Suggestion
1. Check if base station is flooded. If yes, power off base station. Clear the water away.
Wait until the equipment is dry. Then power on the equipment.
2. Replace water sensor.
3. Reset FCE board.
4. Replace FCE board.
2.1.5 4013 Outdoor smoke alarm

Alarm Property
l
l
l
l
Alarm Code:4013
Alarm Information:The smoke sensor of the outdoor monitoring device is abnormal.
Alarm Level:Minor
None
System Impact
Probable Cause
1. The base station has smog.
Handling Suggestion
1. Check if there is smog in base station.
If yes, switch off the base station and isolate the source of smog. Switch on the system
after the smog source is removed.
2. Replace the smog sensor.
3. Reset the board.
4. Replace the board.
2-4
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
2.1.6 4016 Outdoor lightning protection module alarm

Alarm Property
l
l
Alarm Code:4016
Alarm Information:The lightning protection module of the outdoor monitoring device
is abnormal.
l
l
Alarm Level:Minor
1. Lightning protection trunk node contact 1 is abnormal;
2. Lightning protection trunk node contact 2 is abnormal.
System Impact
Probable Cause
1. Failure with the lightning protection arrester caused by lightning damage, poor
grounding or parts aging, etc.
Handling Suggestion
1. Check the trunk node configuration in the dry contact alarm configuration in the
configuration resource management interface,
Make sure the configuration of the dry contact is in accordance with the actual
equipments installed.
2. Check the monitor cable connection with the dry contact.Replace the cable in case of
cable failure.
3. Replace the lightning arrester.
2.1.7 4017 Outdoor power supply unit alarm

Alarm Property
l
l
l
l
Alarm
Alarm
Alarm
Alarm
Code:4017
Information:Power supply was abnormal.
Level:Minor
Type:Environment Alarm
None
2-5
SJ-20140402111513-008|20140528(R1.0)
System Impact
Probable Cause
1. Monitor is faulty.
2. PSU is faulty.
Handling Suggestion
1. Check whether the monitor cable is connected properly.
2. Replace the PSU module.
2.1.8 4018 Outdoor fan alarm

Alarm Property
l
l
l
l
Alarm
Alarm
Alarm
Alarm
Code:4018
Information:Fan was in fault.
Level:Minor
Every subcode represents a fan number.
System Impact
Probable Cause
1. Fan is not inserted.
2. Monitoring line is faulty.
3. Fan box is faulty.
Handling Suggestion
1. Check whether the fan box has been installed.
2. Check whether the monitor cable is connected properly.
3. Replace the fan box.
2.1.9 9301 Power environment under-temperature

Alarm Property
l
Alarm Code:9301
2-6
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
l
l
l
Alarm Information:The environment temperature is less than set value of the

environment.
Alarm Level:Minor
None
System Impact
The battery's capacity is influenced.
Probable Cause
1. The environment temperature is lower than the threshold value for alarm.
2. The temperature sensor is damaged.
3. The monitoring unit is faulty.
Handling Suggestion
1. Check the temperature in the equipment room, and improve the equipment room
condition.
2. Appropriately adjust the threshold value for alarm.
3. Replace the temperature sensor.
4. Replace the monitoring unit.
2.1.10 9302 Power environment over-temperature

Alarm Property
l
l
l
l
Alarm Code:9302
Alarm Information:The environment temperature is higher than set value of the
environment.
Alarm Level:Minor
None
System Impact
1.
2.
3.
The battery's capacity is influenced.

The maximum load capacity of the rectifier is influenced.
The system security is influenced, fire might be caused due to over-temperature.
2-7
SJ-20140402111513-008|20140528(R1.0)
Probable Cause
1. The environment temperature is higher than the threshold value for alarm.
2. The temperature sensor is damaged.
3. The AC transducer or the monitoring unit is damaged.
Handling Suggestion
condition.
2. Appropriately adjust the threshold value for alarm.
4. Check whether the current is beyond the detection range.
5. Replace the AC transducer or the monitoring unit.
2.1.11 9303 Power environment invalid-temperature

Alarm Property
l
l
l
l
Alarm Code:9303
Alarm Information:The temperature of the environment is invalid.
Alarm Level:Minor
None
System Impact
The equipment environment temperature detection is influenced.
Probable Cause
1.
2.
3.
4.
The environment temperature exceeds the normal range allowed in the detection.
The temperature sensor is damaged.
The temperature sensor is not connected.
The AC transducer or the monitoring unit is damaged.
Handling Suggestion
condition.
2. Check whether the temperature sensor is connected reliably.
2-8
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
2.1.12 9304 Power environment under-humidity

Alarm Property
l
l
l
l
Alarm Code:9304
Alarm Information:The environment humidity is less than set value of the enviroment
humidity.
Alarm Level:Minor
None
System Impact
The antistatic capability of the power supply is influenced, which might cause equipment
damage.
Probable Cause
1. The environment humidity is lower than the threshold value for alarm.
2. The humidity sensor is damaged.
Handling Suggestion
1.
2.
3.
4.
Check the humidity in the equipment room, and improve the equipment room condition.
Appropriately adjust the threshold value for alarm.
Replace the humidity sensor.
Replace the monitoring unit.
2.1.13 9305 Power environment over-humidity

Alarm Property
l
l
l
l
Alarm Code:9305
Alarm Information:The environment humidity is higher than set value of the enviroment
humidity.
Alarm Level:Minor
None
2-9
SJ-20140402111513-008|20140528(R1.0)
System Impact
The anti-insulation and crush-resistance capability of the power supply is influenced, and
the board tends to be affected by damp and corrosion.
Probable Cause
1. The environment humidity is higher than the threshold value for alarm.
2. The humidity sensor is damaged.
3. The AC transducer or the monitoring unit is damaged.
Handling Suggestion
1.
2.
3.
4.
5.
Appropriately adjust the threshold value for alarm.
Check whether the current is beyond the detection range.
Replace the AC transducer or the monitoring unit.
2.1.14 9306 Power environment invalid-humidity

Alarm Property
l
l
l
l
Alarm Code:9306
Alarm Information:The humidity of the environment is invalid.
Alarm Level:Minor
None
System Impact
The equipment environment humidity detection is influenced.
Probable Cause
1.
2.
3.
4.
The environment humidity exceeds the normal range allowed in the detection.
The humidity sensor is damaged.
The humidity sensor is not connected.
The AC transducer or the monitoring unit is damaged.
Handling Suggestion
1.
2.
3.
4.
Check whether the humidity sensor is connected reliably.
Check whether the current is beyond the detection range.
2-10
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
2.1.15 9307 Power smog alarm

Alarm Property
l
l
l
l
Alarm
Alarm
Alarm
Alarm
Code:9307
Information:The sensor detects the smog.
Level:Critical
None
System Impact
The system security is influenced, and the system might be on fire.
Probable Cause
1. The smoke alarm signal is detected.
2. The smoke sensor is damaged.
Handling Suggestion
1. Check whether there is any smoke. If there is, then disconnect the AC power supply
input and locate the fault. After the fault is removed, power on again, and restart the
sensor.
2. Replace the smoke sensor.
2.1.16 9308 Power flood alarm

Alarm Property
l
l
l
l
Alarm
Alarm
Alarm
Alarm
Code:9308
Information:The sensor detects the water.
Level:Minor
None
System Impact
The system security is influenced.
2-11
SJ-20140402111513-008|20140528(R1.0)
Probable Cause
1. The flooding alarm signal is detected.
2. The sensor is damaged.
Handling Suggestion
1. Improve the equipment room condition.
2. Replace the sensor.
2.1.17 9309 Power magnetic door alarm

Alarm Property
l
l
l
l
Alarm Code:9309
Alarm Information:The sensor detects the magmetic door is open,and something
comes in.
Alarm Level:Minor
None
System Impact
The burglarproof security of the equipment is influenced.
Probable Cause
1. The equipment room's door is opened.
2. The sensor is damaged.
3. The door-status-switch detecting port is not connected, or the detecting cable is
disconnected.
4. The door-status-switch is not installed appropriately, that is, the door status switch can
not be attracted normally after the door is closed.
Handling Suggestion
1. Check whether the door is closed.
2. Check whether the detecting cable is connected correctly.
3. Check whether the door status switch is installed correctly, and whether the switch can
be attracted normally after the door is closed.
4. Replace the door-status-switch sensor.
2-12
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
2.1.18 134218750 Dry contact alarm

Alarm Property
l
l
l
l
Alarm
Alarm
Alarm
Alarm
Code:134218750
Information:Reference alarm parameters.
Level:Critical
None
System Impact
External device status change
Probable Cause
Input Signal Change on EDI Input Port.
Handling Suggestion
Check the external Device state.

Alarm Property
l
l
l
l
Alarm
Alarm
Alarm
Alarm
Code:134218751
Level:Major
None
System Impact
Probable Cause
Handling Suggestion
2-13
SJ-20140402111513-008|20140528(R1.0)

Alarm Property
l
l
l
l
Alarm
Alarm
Alarm
Alarm
Code:134218752
Level:Minor
None
System Impact
Probable Cause
Handling Suggestion

Alarm Property
l
l
l
l
Alarm
Alarm
Alarm
Alarm
Code:134218753
Level:Warning
None
System Impact
Probable Cause
Handling Suggestion
2-14
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
2.1.22 134243759 MSTP port BPDU Guard

Alarm Property
l
l
l
l
Alarm Code:134243759
Alarm Information:The alarm is reported if the port is protocol-down due to the BPDU
Guard function (This port will block and be out of STP computation).The Alarm will
disapear when XSTP global disable, XSTP port disable, port phy-down and ethernet
port close.
Alarm Level:Major
None
System Impact
The port is blocked for some time.
Probable Cause
The BPDU packet is received at the edge port.
Handling Suggestion
Check whether the port is connected to a user terminal, whether should be configured as
an edge port.
2.1.23 134243760 MSTP port LOOP Guard

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if the port is blocked due to the LOOP Guard
function. The Alarm will disapear when XSTP global disable, XSTP port disable,
phy-down and ethernet port close.
Alarm Level:Major
None
System Impact
2-15
SJ-20140402111513-008|20140528(R1.0)
Probable Cause
The port configured with LOOP Guard function does not receive the BPDU packet for a
long time.
Handling Suggestion
Check whether the port should be configured with LOOP Guard function, whether the link
is congested, whether there are unidirectional link problems, and whether the port receives
and sends BPDU packets properly.
2.1.24 134243761 MSTP port ROOT Guard

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if the port is blocked due to the ROOT Guard
function. The Alarm will disapear when XSTP global disable, XSTP port disable, phy
down and ethernet port close.
Alarm Level:Major
None
System Impact
Probable Cause
The port configured with ROOT Guard function receives a high-priority configuration
message.
Handling Suggestion
Check where the high-level priority BPDU packet comes from, whether the port should be
configured with ROOT Guard function, whether there are network attacks, and whether
the configuration such as bridge priority is correct.
2.1.25 134257778 FAN Control Temperature beyond threshold

Alarm Property
l
l
l
Alarm Information:The alarm is reported if the fan control temperature exceeds the
limit (-25~55 degree).
Alarm Level:Minor
2-16
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
None
System Impact
The system emission performance degrades. This may create error codes.
Probable Cause
The fan control temperature exceeds the limit (-25~55 degree).
Handling Suggestion
1.check the fan speed is normal, check if there is fan lost speed alarm.
2.1.26 134257780 Device overheated

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if the working temperature of a board exceeds
the upper limit.
Alarm Level:Critical
None
System Impact
The system heat dissipation performance is affected, which may cause error codes.
Probable Cause
1. The working temperature is too high.
2. The fan cannot work properly.
3. The board hardware is faulty.
Handling Suggestion
1. Check the working temperature of the equipment room. If the temperature is too high,
ensure that the cooling devices are working properly.
2. Check whether the fans fail to work. If yes, replace the fans.
3. If the alarm persists after the preceding steps, it indicates that the board in the
corresponding slot is faulty. Replace the board.
2-17
SJ-20140402111513-008|20140528(R1.0)
2.2 Equipment Alarm

2.2.1 1002 Board is absent
Alarm Property
l
l
l
l
Alarm Code:1002
Alarm Information:This alarm is reported if the board is configured on the client GUI,
but the board is not inserted in the configured slot.
Alarm Type:Equipment Alarm
None
System Impact
1.
2.
Board Status:The board may be faulty.

Service Impact:The board cannot bear any service.
Probable Cause
1. The board is not inserted at the slot that is configured on the client GUI.
2. The board is not inserted tightly at the slot that is configured on the client GUI.
3. The board inserted at the slot that is configured on the client GUI is physically
damaged.
Handling Suggestion
1. Check whether the board is inserted into the slot.If yes, go to step 2. If no, insert the
board.
2. Pull out and insert the board into the slot.If the alarm persists, go to step 3.
2.2.2 1004 Board is not configured

Alarm Property
l
l
l
l
Alarm Code:1004
Alarm Information:This alarm is reported if the board is not configured on the client
GUI, but the board is inserted in slot.
Every subcode represents a slot.
2-18
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
System Impact
1.
Board Status:
The board is not configured.
2.
Service Impact:
There is no influence on services.
Probable Cause
Board is not configured at user interface in background.
Handling Suggestion
Check that whether the board is inserted at foreground,but the board is not configured at
background.
2.2.3 9001 AC input switch off

Alarm Property
l
l
l
l
Alarm
Alarm
Alarm
Alarm
Code:9001
Information:AC input switch is off.
Level:Critical
Type:Equipment Alarm
None
System Impact
1.
2.
The rectifier fails to work normally, only the battery can work.
When the battery runs out, the base station is powered down.
Probable Cause
1.
2.
3.
4.
5.
The air break switch of the main AC input is not closed.

The main air break switch's contact is disconnected or of bad contact.
The monitoring unit's socket is of bad contact or disconnected.
The monitoring unit is faulty.
The AC loop is short-circuited.
Handling Suggestion
1.
2.
3.
4.
If the air break switch of the main AC input is not closed, then close it.
Check the air break switch's contact.
Check whether the monitoring unit's socket is inserted properly.
2-19
SJ-20140402111513-008|20140528(R1.0)
2.2.4 9002 AC power off

Alarm Property
l
l
l
l
Alarm Code:9002
Alarm Information:The mains supply is cut off and there is no standby AC input.
None
System Impact
1.
2.
3.
The rectifier fails to work normally, only the battery can work.
The system does not implement battery management.
When the battery runs out, the base station is powered down.
Probable Cause
1.
2.
3.
4.
The AC power supply is powered down.

The AC transducer's connection is faulty or the transducer is damaged.
Handling Suggestion
1. If the AC power supply is powered down, use the generator to provide power supply.
2. Check whether the AC transducer's connection is normal and whether the transducer
has no problem.
3. Check whether the monitoring unit's socket is inserted properly.
2.2.5 9003 SPD-C broken

Alarm Property
l
l
l
l
Alarm
Alarm
Alarm
Alarm
Code:9003
Information:The class C arrester is faulty.
Level:Minor
None
2-20
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
System Impact
The lightning protector fails.
Probable Cause
1.
2.
3.
4.
5.
6.
The lightning protector is damaged.

The air break switch of the lightning protector is disconnected.
The lightning protector's base is of bad contact.
The lightning protector's detecting cable is disconnected or of bad contact.
Handling Suggestion
1.
2.
3.
4.
The lightning protector is damaged. Replace the lightning protector.

Check whether the lightning protector's air break switch is closed.
Check whether the lightning protector's base is of bad contact.
Check whether the contact of the lightning protector's base is disconnected or of bad
contact.
5. Check the monitoring unit's connection.
2.2.6 9004 SPD-D broken

Alarm Property
l
l
l
l
Alarm
Alarm
Alarm
Alarm
Code:9004
Information:The class D arrester is faulty.
Level:Minor
None
System Impact
The lightning protector fails.
Probable Cause
1.
2.
3.
4.
5.
The lightning protector is damaged.

The lightning protector's base is of bad contact.
The lightning protector's detecting cable is disconnected or of bad contact.
2-21
SJ-20140402111513-008|20140528(R1.0)
Handling Suggestion
1.
2.
3.
4.
5.

Ensure that the lightning protector's base is of good contact.
Ensure that the contactor of the lightning unit is connected and of good contact.
Ensure that the monitoring unit is well connected.
2.2.7 9005 AC under-voltage

Alarm Property
l
l
l
l
Alarm Code:9005
Alarm Information:The AC input phase voltage is lower than phase threshold.
Alarm Level:Minor
Every subcode represents a input line/phase .
System Impact
The load capacity of the power supply is influenced, which also affects the normal power
supply for the base station.
Probable Cause
1.
2.
3.
4.
5.
The AC input voltage is low.

The AC under-voltage value of the monitoring unit is set too high.
Handling Suggestion
1. Improve the power supply quality of the equipment room.
2. If the detected AC voltage value is lower than the threshold value for alarm of AC
voltage being low, then appropriately decrease the threshold value.
has no problem.
2-22
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
2.2.8 9006 AC over-voltage

Alarm Property
l
l
l
l
Alarm Code:9006
Alarm Information:The AC input phase voltage is higher than phase threshold.
Alarm Level:Minor
Every subcode represents a input line/phase .
System Impact
1.
2.
The operation safety of the rectifier is influenced.

The rectifier will automatically power off for protection.
Probable Cause
1.
2.
3.
4.
5.
The AC input voltage is high.

The AC over-voltage value of the monitoring unit is set too low.
Handling Suggestion
1. Improve the power supply quality of the equipment room.
2. If the detected AC voltage value is higher than the threshold value for alarm of AC
voltage being high, then appropriately increase the low threshold value.
has no problem.
2.2.9 9101 SMR broken

Alarm Property
l
l
l
l
Alarm
Alarm
Alarm
Alarm
Code:9101
Information:One of the rectifier is abnormal.
Level:Critical
Every subcode represents a rectifier.
2-23
SJ-20140402111513-008|20140528(R1.0)
System Impact
The load capacity of the power supply is influenced, which also affects the normal power
supply for the base station.
Probable Cause
1.
2.
3.
4.
5.
6.
The rectifier is faulty.

The input door according to rectifier is closed.
The rectifier is pulled out.
The rectifier door is damaged.
Handling Suggestion
1.
2.
3.
4.
5.
6.
Check the working state of rectifier,and replace it if damaged.

Check whether the door according to rectifier is open.
Check whether the rectifier is pulled out or not.
Check whether the rectifier is short or burned out.
2.2.10 9102 SMR output over-voltage

Alarm Property
l
l
l
l
Alarm
Alarm
Alarm
Alarm
Code:9102
Information:Rectifier output over-voltage.
Level:Critical
System Impact
1.
2.
The rectifier will be powered off for protection.

It influences the power supply for the base station.
Probable Cause
1. The rectifier's output voltage is abnormal.
2. The rectifier is damaged.
Handling Suggestion
1. Pull out the rectifier and plug it in again, and make it powered on.
2-24
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
2. Replace the rectifier.
2.2.11 9103 SMR output over-current

Alarm Property
l
l
l
l
Alarm
Alarm
Alarm
Alarm
Code:9103
Information:Rectifier output over-current.
Level:Critical
System Impact
1. The rectifier will be powered off for protection.
3. It influences the power supply for the base station.
Probable Cause
1. The over-current protection circuit of the rectifier is faulty.
Handling Suggestion
1. Pull out the rectifier and plug it in again, and make it powered on.
2.2.12 9104 SMR fan fault

Alarm Property
l
l
l
l
Alarm
Alarm
Alarm
Alarm
Code:9104
Information:The fan of the rectifier is abnormal.
Level:Critical
System Impact
2-25
SJ-20140402111513-008|20140528(R1.0)
Probable Cause
1. The rectifier's fan is damaged or blocked by some foreign body.
2. The monitoring unit's socket is of bad contact or disconnected.
Handling Suggestion
1.
2.
3.
4.
Check whether the fan is blocked by some foreign body.

Check the monitoring unit's socket.
Replace the rectifier.
2.2.13 9105 SMR PFC fault

Alarm Property
l
l
l
l
Alarm
Alarm
Alarm
Alarm
Code:9105
Information:Rectifier PFC module is faulty.
Level:Critical
System Impact
Probable Cause
The PFC circuit of the rectifier is faulty.
Handling Suggestion
2.2.14 9106 SMR input over-voltage and power off

Alarm Property
l
l
l
l
Alarm Code:9106
Alarm Information:Rectifier AC input over-voltage and power off.
2-26
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
System Impact
Probable Cause
1. The AC input voltage of the rectifier is higher than the threshold value of over-voltage
protection.
Handling Suggestion
1. Check whether the AC voltage is higher than the threshold value.
2.2.15 9107 SMR input under-voltage and power off

Alarm Property
l
l
l
l
Alarm Code:9107
Alarm Information:Rectifier AC input under-voltage and power off.
System Impact
Probable Cause
1. The AC input voltage of the rectifier is lower than the threshold value of under-voltage
protection.
Handling Suggestion
1. Check whether the AC voltage is lower than the threshold value.
2-27
SJ-20140402111513-008|20140528(R1.0)
2.2.16 9108 SMR host heater over-temp and power off

Alarm Property
l
l
l
l
Alarm Code:9108
Alarm Information:The temperature of the heater sink is higher than the protection
point, which causes the rectifier to shut down.
System Impact
Probable Cause
1. The heat radiator of the rectifier is too hot.
Handling Suggestion
1. Check whether the temperature of the rectifier's heat radiator is higher than the
threshold value.
2. Improve the ventilation condition of the equipment room.
2.2.17 9109 SMR environment over-temp and power off

Alarm Property
l
l
l
l
Alarm Code:9109
Alarm Information:The temperature of the rectifier is higher than the protection point,
which causes the rectifier to shut down.
System Impact
2-28
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
Probable Cause
1. The environment temperature of the rectifier is too high.
Handling Suggestion
threshold value.
2.2.18 9110 SMR environment over-temp and load-reduction

Alarm Property
l
l
l
l
Alarm Code:9110
Alarm Information:The temperature of the rectifier is too high which causes the output
power of the rectifier to derate.
System Impact
1. The load capacity of the rectifier is influenced.
Probable Cause
1. The environment temperature of the rectifier is higher than the threshold temperature
for load-reduction (i.e. if the threshold temperature for load-reduction is exceeded, the
power supply will be powered off for some loads).
Handling Suggestion
threshold value.
2-29
SJ-20140402111513-008|20140528(R1.0)
2.2.19 9111 SMR under-voltage and load-reduction

Alarm Property
l
l
l
l
Alarm Code:9111
Alarm Information:The rectifier AC input voltage is too low which causes the output
power of the rectifier to derate.
System Impact
1.The load capacity of the rectifier is influenced.
3.It influences the power supply for the base station.
Probable Cause
1. The AC input voltage of the rectifier is lower than the threshold voltage for
under-voltage load-reduction.
Handling Suggestion
1. Check whether the AC voltage is lower than the threshold value.
2.2.20 9112 SMR fuse broken

Alarm Property
l
l
l
l
Alarm Code:9112
Alarm Information:The output fuse of the rectifier is blown.
System Impact
2-30
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
Probable Cause
1. The output fuse in the rectifier is burned.
Handling Suggestion
2.2.21 9113 SMR communication failure

Alarm Property
l
l
l
l
Alarm Code:9113
Alarm Information:The communication between the rectifier and monitoring unit is
abnormal.
System Impact
1.
2.
3.
4.
The system fails to implement battery management.

The AC voltage sampling is influenced.
The decision whether the AC power supply should be powered off is influenced.
Probable Cause
1. The RS485 communication cable of the rectifier is broken or short-circuited.
2. The monitoring crystal-oscillator's frequency of the rectifier is not calibrated.
3. When the AC power supply is powered down, the actual load is smaller than the
threshold value of the minimum load.
Handling Suggestion
1. Check if whether all communication of rectifier are broken.
2. Check whether power off and set the lowest loader current threshold is smaller than
the current loader current.
3. Check the RS485.
communication cable is broken or short.
5. Check and maintain the communication cables.
2-31
SJ-20140402111513-008|20140528(R1.0)
6. Replace the monitoring units.
2.2.22 9201 DC output under-voltage

Alarm Property
l
l
l
l
Alarm Code:9201
Alarm Information:The DC output voltage is lower than threshold.
Alarm Level:Minor
None
System Impact
Although it has no influence on the system, it is necessary to find out the alarm cause to
avoid other faults.
Probable Cause
1.
2.
3.
4.
The DC output voltage is lower than the threshold value.

The DC under-voltage value of the monitoring unit is set too high.
Handling Suggestion
1.
2.
3.
4.
Check the DC output voltage.

Check whether the DC under-voltage value of the monitoring unit is set appropriately.
2.2.23 9202 DC output over-voltage

Alarm Property
l
l
l
l
Alarm Code:9202
Alarm Information:The DC output voltage is higher than threshold.
Alarm Level:Major
None
2-32
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
System Impact
The rectifier will be powered off for protection, only the battery can work.
Probable Cause
1.
2.
3.
4.
5.
The DC output voltage is high.

The DC over-voltage value of the monitoring unit is set too low.
The rectifier is faulty.
Handling Suggestion
1.
2.
3.
4.
5.
Check the DC output voltage.

Check whether the DC over-voltage value of the monitoring unit is set appropriately.
2.2.24 9203 DC load loop broken

Alarm Property
l
l
l
l
Alarm
Alarm
Alarm
Alarm
Code:9203
Information:The DC loop is open.
Level:Critical
Every subcode represents a loop.
System Impact
The power supply for the load is influenced.
Probable Cause
1.
2.
3.
4.
The fuse of the load's loop is burned (or the air break switch is broken).
The detecting cable of the load's loop is disconnected or of bad contact.
Handling Suggestion
1. Check whether the load's loop is short-circuited.
2. Check whether the capacity of the fuse (or air break switch) is set appropriately.
3. The detecting cable of the load's loop is disconnected or of bad contact.
2-33
SJ-20140402111513-008|20140528(R1.0)

2.2.25 9204 Battary loop broken

Alarm Property
l
l
l
l
Alarm
Alarm
Alarm
Alarm
Code:9204
Information:The battery loop is open.
Level:Critical
Every subcode represents a battary.
System Impact
1.
When the loops of all batteries are broken, the system fails to implement battery
management.
2.
The loops of all battery groups are broken. After the AC power supply is powered
down, the base station is also powered down.
Probable Cause
1.
2.
3.
4.
The fuse of the battery's loop is burned.

The detecting cable of the battery's loop is disconnected or of bad contact.
Handling Suggestion
1. Check whether the load's loop is short-circuited, and whether the capacity of the
battery's fuse is set appropriately.
2. Check whether the threshold value for the fuse alarm of the monitoring unit is set
appropriately.
3. Check whether the detecting cable of the battery's loop is disconnected or of bad
contact.
4. Check whether the monitoring unit's socket is of bad contact or disconnected.
2.2.26 9205 Battary under-voltage

Alarm Property
l
l
Alarm Code:9205
Alarm Information:The battery voltage is lower than threshold.
2-34
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
l
l
Alarm Level:Major
System Impact
Although it has no influence on the system, it is necessary to find out the alarm cause to
avoid other faults.
Probable Cause
1.
2.
3.
4.
5.
The battery's voltage is low.

The battery's under-voltage value of the monitoring unit is set too high.
The detecting cable of the battery is faulty.
Handling Suggestion
1. Check the battery's output voltage.
2. Check whether the battery's under-voltage value of the monitoring unit is set
appropriately.
3. Check whether the monitoring unit's socket is inserted properly, and whether the cable
is broken or of bad contact.
2.2.27 9206 Battary over-temp

Alarm Property
l
l
l
l
Alarm Code:9206
Alarm Information:The battery temperature is higher than threshold.
Alarm Level:Minor
System Impact
The battery's service lifetime is influenced.
2-35
SJ-20140402111513-008|20140528(R1.0)
Probable Cause
1. The battery's temperature is higher than the threshold value of over-temperature of
battery.
2. The battery's over-temperature value of the monitoring unit is set too low.
3. The temperature sensor of the battery is damaged.
Handling Suggestion
1. Check the battery's temperature.
2. Check whether the battery's over-temperature value of the monitoring unit is set
appropriately.
3. Check whether the battery's temperature sensor is damaged.
2.2.28 9207 Power under-temp and power off

Alarm Property
l
l
l
l
Alarm Code:9207
Alarm Information:The environment temperature is lower than threshold, which
causes all the loads to shut down.
None
System Impact
Probable Cause
1. The system temperature is lower than the temperature for power-down in
low-temperature environment.
2. The temperature sensor of the battery is damaged.
Handling Suggestion
1. Check the battery's temperature.
2. Check whether the threshold value for power-down in low-temperature environment
of the monitoring unit is set appropriately.
2-36
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
3. Check whether the battery's temperature sensor is damaged.

2.2.29 9208 First power off

Alarm Property
l
l
l
l
Alarm Code:9208
Alarm Information:The battery voltage is lower than threshold, which causes the
secondary loads to shut down.
None
System Impact
The secondary load is powered down.
Probable Cause
1. When the battery's voltage decreases to the threshold value for first power-down, the
system performs the first power-down operation.
2. The first power-down voltage of the monitoring unit is not set appropriately.
3. The manual power-down switch is set incorrectly.
4. The DC contactor is connected incorrectly.
5. The DC contactor is damaged.
6. The SDCB board is damaged.
Handling Suggestion
1. Check the battery's voltage to see whether it is lower than the voltage for first
power-down.
2. Check whether the first power-down voltage of the monitoring unit is set appropriately.
3. Check the manual power-down switch to see whether it is in the automatic status or
the connected status.
4. Check whether the first power-down DC contactor is damaged. Measure whether there
is 48 V voltage at the two ends of the DC contactor's control coil, and check whether
the control coil is disconnected or broken.
5. Check the DC contactor's cable connection.
6. If the Shut-Down Control Board (SDCB) is configured, then check whether the
power-down is caused by SDCB fault.
2-37
SJ-20140402111513-008|20140528(R1.0)
2.2.30 9209 Second power off

Alarm Property
l
l
l
l
Alarm Code:9209
Alarm Information:The battery voltage is lower than threshold, which causes all the
loads to shut down.
None
System Impact
The base station is powered down, and the communication is interrupted.
Probable Cause
1. When the battery's voltage decreases to the threshold value for second power-down,
the system performs the second power-down operation.
2. The second power-down voltage of the monitoring unit is not set appropriately.
3. The manual power-down switch is set incorrectly.
4. The DC contactor is connected incorrectly.
5. The DC contactor is damaged.
6. The SDCB board is damaged.
Handling Suggestion
1. Check the battery's voltage to see whether it is lower than the voltage for second
power-down.
2. Check whether the second power-down voltage of the monitoring unit is set
appropriately.
3. Check the manual power-down switch to see whether it is in the automatic status or
the connected status.
4. Check whether the second power-down DC contactor is damaged. Measure whether
there is 48 V voltage at the two ends of the DC contactor's control coil, and check
whether the control coil is disconnected or broken.
5. Check the DC contactor's cable connection.
6. If the Shut-Down Control Board (SDCB) is configured, then check whether the
power-down is caused by SDCB fault.
2-38
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
2.2.31 9210 DC SPD abnormal

Alarm Property
l
l
l
l
Alarm
Alarm
Alarm
Alarm
Code:9210
Information:DC SPD abnormal.
Level:Major
None
System Impact
The lightning protection capability is influenced.
Probable Cause
1.
2.
3.
4.
5.
6.
The DC lightning protector is damaged.

The lightning protector's detecting cable is disconnected.
The lightning protector's of bad contact.
The lightning protector's detect line is broken or bad contact.
Handling Suggestion
1.
2.
3.
4.

Check whether the lightning protector's air break switch is closed.
Check whether the lightning protector's base is of bad contact.
Check whether the contact of the lightning protector's base is disconnected or of bad
contact.
5. Check the monitoring unit's connection.
2.2.32 9211 Load breaker abnoraml

Alarm Property
l
l
l
l
Alarm
Alarm
Alarm
Alarm
Code:9211
Information:DC breaker is broken.
Level:Minor
Every subcode represents a breaker.
2-39
SJ-20140402111513-008|20140528(R1.0)
System Impact
If the circuit breaker can not be powered down normally, then the battery might be
discharged.
Probable Cause
1. The DC contactor is damaged, there is one or two power-down alarms but no
power-down operation is performed.
2. The load's current is very small, and the current of the loop where the load is located
changes little before and after power-down.
3. The control loop of system power-down is broken (such as that the terminal is not
connected or the control signal cable is broken).
4. The output of the monitoring control signal is abnormal.
Handling Suggestion
1.
2.
3.
4.
No handling is required if the problem is due to the load's current being small.
Check whether the control signal channel is normal.
Replace the DC contactor.
2.2.33 9212 Battary test failure

Alarm Property
l
l
l
l
Alarm Code:9212
Alarm Information:The battery test time is shorter than the maximum test time and the
test is over.
Alarm Level:Warning
None
System Impact
It does not influence the power supply for the base station.
Probable Cause
1.
2.
3.
4.
Before the test time expires, the battery discharge is stopped.

The battery is not connected correctly.
The power supply capability of the battery is not enough.
Parameters related to the battery test are not set appropriately.
2-40
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
Handling Suggestion
1. Check whether the battery is connected correctly.
2. After the battery is fully charged, perform the test again. The test succeeds, and the
alarm is removed automatically.
3. According to the power supply's load and the battery's capacity, appropriately set parameters such as the test time and the test voltage.
4. Replace the battery.
2.2.34 9213 Battery discharge

Alarm Property
l
l
l
l
Alarm
Alarm
Alarm
Alarm
Code:9213
Information:Battery discharge.
Level:Minor
None
System Impact
Probable Cause
1.
2.
3.
4.
The battery's discharge current is larger than the threshold value for alarm.
The battery's current measurement is not accurate.
The threshold value for alarm is not appropriate.
The AC transducer or the monitoring unit is damaged, causing that the current is
beyond the detection range.
Handling Suggestion
1. Check whether the battery is in the discharge status.
2. Adjust the zero parameter and the slope parameter of the monitoring unit, and calibrate
the detection precision.
3. Appropriately adjust the threshold value for the alarm of battery discharge.
2.2.35 134217728 Clock reference source lost

Alarm Property
l
2-41
SJ-20140402111513-008|20140528(R1.0)
l
l
Alarm Information:The alarm is reported if the RCU can not detect the clock signal
(including local traffic clock, air interface clock,and the external clock reference source
)and the RCU clock therefore remains in free oscillation status.
Alarm Level:Minor
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
RCU 1PPS+TOD clock lost;

RCU BITS clock lost;
Slot2 clock lost;
Slot3 clock lost;
Slot4 clock lost;
Slot5 clock lost;
Slot6 clock lost;
Slot7 clock lost;
Slot8 clock lost;
RCU NMS clock lost;
RCU GbE clock lost;
1588 clock lost;
Slot4 second clock lost;
AOU GbE port clock lost;
AOU GbO port clock lost;
AOU radio port clock lost;
AOU multiplex port clock lost;
RCU TDMEXT clock lost;
System Impact
The system can not lock the clock. The SDH and E1 traffic may be interrupted or error
codes may be generated.
Probable Cause
The equipment can not detect the external clock source.
Handling Suggestion
Counter measures are taken based on different clocks:
1. For master 1PPS+TOD clock and master BITS clock,ensure that clock signals are
input to the CLK IN/OUT interface on the RCU (RCMU) panel and that clock cable is
2-42
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
connected properly and undamaged. If the alarm remains, replace the RCU (RCMU)
board.
2. For clock at the local end,ensure that cables are connected to the corresponding
ports on the IDU/ACMUA panel properly.If the alarm remains,replace the ACMUA/RTU
(RCMU)board.
3. For the air interface clock,ensure that the radio link is locked, that is, the LINK indicator on the ACMUA/RMU board(RCMU,RMEA daughter card) keeps on.If the alarm
remains, replace the ACMUA/RMU board(RCMU,RMEA daughter card).
4. For the GbE clock, ensure that the GbE ports on RCU/RTU/RCMU/ACMUA board
connects with the proper cables.If the alarm remains,replace the RCU/RTU/RCMU
/ACMUA board.
2.2.36 134217730 RTC clock alarm

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if the master RTC clock timing fails.
Alarm Level:Minor
1. RTC clock failure;
2. RTC clock not set.
System Impact
The system time is inaccurate. When this alarm is reported, the system enters the soft
timing state and the system scale accuracy decreases.
Probable Cause
1. The battery (CR2032) on main control board fails.
2. The RTC time chip fails.
Handling Suggestion
1. Correct the time manually or automatically.
2. Ensure that the main control board has battery on. If the alarm remains, the battery
may run out or is faulty. In this case, replace the battery (CR2032).
3. If the alarm remains, you can infer that the RTC on the main control board is faulty.
Replace the faulty one.
2-43
SJ-20140402111513-008|20140528(R1.0)
2.2.37 134217735 Clock module fault

Alarm Property
l
l
Alarm Information:The alarm is reported when system clock locked state is abnormal
.
l
l
1. Clock unlock;
2. PLL Unlock;
3. Clock quality deteriorated.
System Impact
I. Board Status:
The board is faulty.
II. Service Impact:
In the case of the active main control board failure, the system does not provide normal
operation, and the peripheral boards might have alarm of the corresponding clock module
which causes interruption to all the services on this board.
Probable Cause
1. Clock unlock is reported when the equipment can not detect all the configured external
clock sources.
2. When the equipment occurs PLL unlock:.
(1)The configured clock source can not be locked or the local oscillator is used.
(2)The RCU(RCMU) has a hardware fault.
3. When the equipment occurs clock quality deteriorated:.
(1)The clock source is 7ppm offset from the oscillation frequency.
(2)The clock source exceeds the oscillation pull range.
(3)The difference between two adjacent phases is more than 334.4ns for 3 seconds.
Handling Suggestion
1. For the clock unlock: resume the lost clock sources and the alarm should have been
removed.
2. For the PLL unlock:
(1)Ensure that the whole network use the same clock source or process the alarm by
referring to the corresponding method.
2-44
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
(2)If the alarm remains after the above step, you can infer that a harware fault may
occur in the RCU(RCMU) board.Replace the faulty board.
3. For the clock quality deteriorated:
(1)If the traffic clock is set to "In-Use Clock First", ensure that the clock source is
available and the alarm will disappear.
(2)If the traffic clock is set to "Only Master" or "Optimal Clock First", set to make the
clock source available and the alarm will disappear.
2.2.38 134217739 EEPROM error alarm

Alarm Property
l
l
l
l
Alarm Information:This alarm is reported when EEPROM data error or in vain.
1.
2.
3.
4.
5.
6.
7.
8.
9.
MAC address EEPROM data error;

Product infomation EEPROM data error;
Product asii information EEPROM data error;
TX EEPROM data error;
AOU EEPROM data error;
MAC address is in vain;
Board serial NO. is in vain;
TX board serial NO.is in vain;
AOU board serial NO. is in vain;
System Impact
This alarm does not affect any traffic
Probable Cause
EEPROM data error or is null value.
Handling Suggestion
Correct error EEPROM data or evaluate the null value data with tool software.
2.2.39 134218754 RPUB Under Voltage

Alarm Property
l
2-45
SJ-20140402111513-008|20140528(R1.0)
l
l
l
Alarm Information:This alarm is reported if no power is supplied of RPUB or the power

supply is under voltage.
Alarm Level:Minor
None
System Impact
If RPUB-PS1 and RPUB-PS2 are powered off simultaneously, the Rf unit will be powered
off and the radio link will be broken.
Probable Cause
1. RPUB Under Voltage.
2. The RPUB board is faulty.
Handling Suggestion
1. Ensure voltage is normal.
2. Ensure that cables of RPUB are connected and operating properly.
3. Replace the RPUB board.
2.2.40 134218778 CPU overload

Alarm Property
l
l
l
l
Alarm Information:This alarm is reported when CPU load is over the threshold which
set by user.
Alarm Level:Minor
None
System Impact
This alarm does not affect any traffic, but it may cause device to slow down.
Probable Cause
CPU is overloaded.
Handling Suggestion
Remove the traffic that fails to work or restart your device.
2-46
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
2.2.41 134218779 Debug ip illegal

Alarm Property
l
l
l
l
Alarm
Alarm
Alarm
Alarm
Code:134218779
Information:Debug ip is illegal.
Level:Minor
1. Auto priavate ip;
2. Ip conflict with the device ip or staitc route ip.
System Impact
This alarm does not affect any traffic, but debug device need Auto Private Ip Address.
Probable Cause
Debug ip is illegal.
Handling Suggestion
Reconfig debug ip address.
2.2.42 134218796 Actual Use MAC illegal

Alarm Property
l
l
l
l
Alarm Information:Actual use MAC number too few or mac is invalid(all 0xffall 0 or
multicast mac).
None
System Impact
Network management line may be broken down, and Protocol may be failed.
Probable Cause
Actual Use MAC illegal.
2-47
SJ-20140402111513-008|20140528(R1.0)
Handling Suggestion
1. Update MAC.
2. Re-burn EEPROM.
2.2.43 134218797 Device MAC conflict

Alarm Property
l
l
l
l
Alarm Information:Device MAC conflict, Please Update MAC.
None
System Impact
Network management line may be broken down, and Protocol may be failed.
Probable Cause
Actual Use MAC is Different With Mac of E2PROM.
Handling Suggestion
1.Update MAC.
2.2.44 134218798 Link between IDU and AOU is interrupted

Alarm Property
l
l
l
l
Alarm Information:This alarm is reported when the communication link between IDU
and AOU is interrupted.
Alarm Level:Major
None
System Impact
IDU can not supervise AOU.
2-48
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
Probable Cause
1. The IDU port for connecting AOU works abnormally.
2. The AOU port for connecting IDU works abnormally.
3. The cable between IDU and AOU is abnormal.
Handling Suggestion
1. Check AOU is connected to IDU.
2. Check cable between AOU and IDU is nromal.
2.2.45 134218800 Running cooperate-manged AOU version

abnormal
Alarm Property
l
l
l
l
Alarm Information:This alarm is reported when IDU detects
cooperate-managed AOU run version differs from the IDU run version.
Alarm Level:Major
that
the
Every subcode represents a cooperate-manged AOU virtual slot.
System Impact
Cooperate-Manged AOU version run abnormal.
Probable Cause
The cooperate-managed AOU running version differs from the IDU running version.
Handling Suggestion
Reload the cooperate-manged AOU software.
2.2.46 134218802 Service unauthorized

Alarm Property
l
l
l
l
Alarm
Alarm
Alarm
Alarm
Code:134218802
Information:Service is unauthorized.
Level:Major
2-49
SJ-20140402111513-008|20140528(R1.0)
None
System Impact
The alarm has no influence on current system.
After 180 days the service
will be interrupted automatically(1.The following functions will be closed
EFM,1588V2,ACM,SLMS and CESoETH.2.The following functions will be frozen
CFM,PLA,Frame Compression,XPIC,LACP,LACP and ERP.3.The capacity will be
minimized).
Probable Cause
Authorization is rejected,or the link between EMS and NE is broken.
Handling Suggestion
1. Check the links are loss or not, between NE and EMS, EMS and licences center.
2. Open License Info page in LMT, find out the license functions which is authorization
failed
. Close the these functions or decrease the capacity.
3. Open License Info page in LMT, check the license available time.Buy required license
in time.
2.2.47 134218803 Service frozen

Alarm Property
l
l
l
l
Alarm
Alarm
Alarm
Alarm
Code:134218803
Information:Service is frozen.
Level:Critical
None
System Impact
The service is interruptedthe following functions is closedEFM,1588V2,ACM,SLMS
and
CESoETH.the
following
functions
is
frozen CFM,PLA,Frame
Compression,XPIC,LACP,LACP and ERP.the capacity is minimized.
Probable Cause
The unauthorized status exceeds the time limit.
2-50
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
Handling Suggestion
Recover from frozen state in EMS.
2.2.48 134237778 Loopback state in TDM port

Alarm Property
l
l
l
l
Alarm Information:TDM loopback. The alarm is reproted when the port on the RTU
board (RCMU board or RTEA daughter card) is in loopback (inner/outer) status.
134283264. E1-1 port (LMT displays E1-1);
2-51
SJ-20140402111513-008|20140528(R1.0)

268500992. STM1-1 port (LMT displays STM1-1);
268566528. STM1-2 port (The rate is STM1 and LMT displays STM1-2.);
335675392. STM4-2 Port (The rate is STM4 and LMT displays STM4-2);
System Impact
Traffic is interrupted when the wireless link port is in loopback status.
Probable Cause
1. The loopback function is enabled for testing or maintenance.
2. The RTU board(RCMU board or RTEA daughter card) that reports the alarm is faulty.
Handling Suggestion
1. If the alarm is caused by loopback that is set for testing or maintenance, disable the
loopback function after the testing or maintenance is completed.
2. If the alarm persists after the preceding step, you can infer that the RTU board is faulty.
Replace the board.
2.2.49 134237936 PRBS array transmit in E1 port

Alarm Property
l
l
l
l
Alarm Information:TDM PRBS Test. The alarm is reproted when the E1 port is
transmitting PRBS array.
1. E1 port 1 on the panel;
2-52
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
4 on the panel;
5 on the panel;
6 on the panel;
7 on the panel;
8 on the panel;
9 on the panel;
10 on the panel;
11 on the panel;
12 on the panel;
13 on the panel;
14 on the panel;
15 on the panel;
16 on the panel;
17 on the panel;
18 on the panel;
19 on the panel;
20 on the panel;
21 on the panel;
22 on the panel;
23 on the panel;
24 on the panel;
25 on the panel;
26 on the panel;
27 on the panel;
28 on the panel;
29 on the panel;
30 on the panel;
31 on the panel;
32 on the panel;
System Impact
Traffic is interrupted when the port is transmitting PRBS array .
Probable Cause
1.The PRBS array transmission is enabled for testing or maintenance.
Handling Suggestion
1.If the alarm is caused by PRBS transmission that is set for testing or maintenance,
disable the PRBS transmission function after the testing or maintenance is completed.
2-53
SJ-20140402111513-008|20140528(R1.0)
2.2.50 134237937 MCLK signal of RTE is abnormal

Alarm Property
l
l
l
l
Alarm Information:Because of lossing MCLK of RTE, LIU is abnormal and E1 traffic
is interrupted.
None
System Impact
E1 traffic will be interrupt
Probable Cause
MCLK signal of RTE is abnormal.
Handling Suggestion
1. Check RTE is fixed on the main board or not.
2. Cold reboot.
2.2.51 134237939 Force-E1-AIS

Alarm Property
l
l
l
l
Alarm Information:The alarm is reproted when the E1 port on the RTU board is
transmitting force-AIS data.
1.
2.
3.
4.
5.
6.
7.
8.
9.
E1
E1
E1
E1
E1
E1
E1
E1
E1
port
port
port
port
port
port
port
port
port
1
2
3
4
5
6
7
8
9
on
on
on
on
on
on
on
on
on
the
the
the
the
the
the
the
the
the
panel;
panel;
panel;
panel;
panel;
panel;
panel;
panel;
panel;
2-54
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
10 on the panel;
11 on the panel;
12 on the panel;
13 on the panel;
14 on the panel;
15 on the panel;
16 on the panel;
17 on the panel;
18 on the panel;
19 on the panel;
20 on the panel;
21 on the panel;
22 on the panel;
23 on the panel;
24 on the panel;
25 on the panel;
26 on the panel;
27 on the panel;
28 on the panel;
29 on the panel;
30 on the panel;
31 on the panel;
32 on the panel;
System Impact
Traffic is interrupted when the port is transmitting force-AIS data.
Probable Cause
1.The force-AIS transmission is enabled for testing or maintenance.
Handling Suggestion
1.If the alarm is caused by force-AIS that is set for testing or maintenance, disable the
function after the testing or maintenance is completed.
2.2.52 134237940 Loopback state in Air E1 port

Alarm Property
l
l
l
l
Alarm Information:TDM air E1 port loopback. The alarm is reproted when the port on
the RMU board is in loopback status.
2-55
SJ-20140402111513-008|20140528(R1.0)
Every subcode represents a E1 port.
System Impact
Traffic is interrupted when the E1 port is in loopback status.
Probable Cause
2. The RMU board(RCMU board) that reports the alarm is faulty.
Handling Suggestion
2. If the alarm persists after the preceding step, you can infer that the RMU board is faulty.
Replace the board.
2.2.53 134239932 Rf unit configuration mode invalid

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if Rf unit does not support the issued
configuration mode.
None
System Impact
The traffic carried by the board is interrupted.
Probable Cause
1. The Rf unit does not support the configuration of the corresponding mode.
2. The Rf unit is faulty.
Handling Suggestion
Replace the Rf unit.
2-56
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
2.2.54 134239940 Rf unit power supply abnormal

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported when the -48V power supply of Rf unit is
abnormal or lost.
Alarm Level:Major
None
System Impact
If the power supply of Rf unit is abnormal, the power supply of If unit (RCMU board or
RTEA daughter card)also becomes abnormal, and the problems of error codes or service
interruption will occur.
Probable Cause
The hardware of power supply is faulty or the power supply is abnormal.
Handling Suggestion
1. Ensure that the power supply is normal.
2. Replace the Rf unit power supply.
2.2.55 134239956 RDI alarm

Alarm Property
l
l
l
l
Alarm Information:Remote modem RX IF LOS alarm is set;.
None
System Impact
Traffic interrupted.
Probable Cause
1. The working modes,bandwidths and frequencies are
2-57
SJ-20140402111513-008|20140528(R1.0)
set differently between local and remote devices.

2. The RSL at local device is low.
3. The modem part is faulty.
Handling Suggestion
1. Make sure the working mode,bandwidth and frequency are the same at both local
device and remote device.
2. Raise the power at local device.
3. Replace the faulty board .
2.2.56 134239959 HC CFG data inconsistent in two ends of the link

Alarm Property
l
l
l
l
Alarm
Alarm
link.
Alarm
Alarm
Code:134239959
Information:HC configuration parameters is inconsistent with two ends of the
Level:Critical
None
System Impact
HC fuction is invalid.
Probable Cause
HC configuration parameters is inconsistent with two ends of the link.
Handling Suggestion
1.AOU:Check configuration and make sure HC configuration parameters consistent with
two ends of link. 2.IDU: retry configurate HC and synchronization to the other end of link.
2.2.57 134239964 Rf unit type mismatch

Alarm Property
l
l
l
l
Alarm Information:Real Rf unit type and configured Rf unit type do not match.
Alarm Level:Minor
2-58
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
None
System Impact
Some Rf unit types can not support 512QAM and 1024QAM
Probable Cause
Real Rf unit type and configured Rf unit type do not match
Handling Suggestion
Modify Rf unit type configuration or change the Rf unit.
2.2.58 134239965 Scan frequency enabled alarm

Alarm Property
l
l
l
l
Alarm Information:Local or neighbor has enabled scan frequency function.
None
System Impact
Rf unit is mutedtraffic interrupted
Probable Cause
Local or neighbor has enabled scan frequency function
Handling Suggestion
Waiting for scan frequency finished or disable the scan frequency function.
2.2.59 134239966 CRC check fails

Alarm Property
l
l
l
l
Alarm Information:CRC check fails when IQ is calibrating.
2-59
SJ-20140402111513-008|20140528(R1.0)
None
System Impact
RF performance is affected.
Probable Cause
CRC check fails when IQ is calibrating
Handling Suggestion
Replace the board.
2.2.60 134241731 Optical Signal Lost

Alarm Property
l
l
l
l
Alarm
Alarm
Alarm
Alarm
Code:134241731
Information:Ethernet SFP port signal loss.
Level:Critical
1. RTUH GbE1 port;
2. RTUH GbE2 port;
3. RTUH GbE3 port;
11.RTUN GbE1 port;
12.RTUN GbE2 port;
13.RTUN GbE3 port;
14.RTUN GbE4 port;
21.RCMU GbE1 port;
22.RCMU GbE2 port;
23.RCMU GbE3 port;
24.RCMU GbE4 port;
25.ACMUA GbO port.
System Impact
2-60
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
Probable Cause
Optical fiber is not connected.
Handling Suggestion
Check the optical fiber connection.
2.2.61 134241739 SFP speed does not match with configuration

Alarm Property
l
l
l
l
Alarm Information:SFP speed does not match with configuration.
Alarm Level:Major
1. RTUH GbE1 port;
2. RTUH GbE2 port;
3. RTUH GbE3 port;
11.RTUN GbE1 port;
12.RTUN GbE2 port;
13.RTUN GbE3 port;
14.RTUN GbE4 port;
21.RCMU GbE1 port;
22.RCMU GbE2 port;
23.RCMU GbE3 port;
24.RCMU GbE4 port;
25.ACMUA GbO port.
System Impact
Traffic is abnormal.
Probable Cause
1. SFP module type is wrong.
2. SFP port speed configuration is wrong.
Handling Suggestion
1. Replace the SFP which is match with configuration.
2. Change the SFP port speed configuration as to match with SFP type.
2-61
SJ-20140402111513-008|20140528(R1.0)
2.2.62 134241740 ETH port SFP power abnormal

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if the system detects that the SFP power is
out of the range.
Alarm Level:Warning
1. RTUH GbE1 port;
2. RTUH GbE2 port;
3. RTUH GbE3 port;
11.RTUN GbE1 port;
12.RTUN GbE2 port;
13.RTUN GbE3 port;
14.RTUN GbE4 port;
21.RCMU GbE1 port;
22.RCMU GbE2 port;
23.RCMU GbE3 port;
24.RCMU GbE4 port;
25.ACMUA GbO port.
System Impact
when the power is abnormal of SFP,this may lead to interruption of business through this
port.
Probable Cause
SFP is faulty.
Handling Suggestion
1. Replace the SFP.
2. Check the optical fiber connection.
2.2.63 134241741 MAC overflow of port

Alarm Property
l
2-62
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
l
l
l
Alarm Information:The MAC overflow alarm will be reported if the MAC number on a
certain port, which MAC limit has been set, exceeds the limit.
Alarm Level:Minor
1. Normal ethernet port;
2. PLA port;
3. LACP port.
System Impact
If the MAC on a certain port exceeds the
limit,the new-coming frame will be dropped,the MAC can not be learned as well.
Probable Cause
The learned MAC number on a certain port exceeds the limit.
Handling Suggestion
1. Improve the level of MAC limit on the alarm port.
2. Flush the MAC on the alarm port.
2.2.64 134243749 OSPF route has been discarded

Alarm Property
l
l
l
l
Alarm Information:OSPF route has been discarded, because it conflict with debug ip.
Alarm Level:Minor
None
System Impact
This alarm may affect DCN.
Probable Cause
OSPF route conflict with debug ip.
Handling Suggestion
Reconfig debug ip address.
2-63
SJ-20140402111513-008|20140528(R1.0)
2.2.65 134243765 1588 clock PTP service setup failure

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if the 1588 conversation setup time exceeds
threshold, and the PTP conversation setup failure is reported.
Alarm Level:Major
None
System Impact
The conversation connection setup fails, and the opposite-end master device of the
conversation cannot be taken as the currnt synchronization master device.
Probable Cause
The PTP configuration is incorrect or the network is abnormal.
Handling Suggestion
1. Ensure that the slave device configurations such as the destination address and PTP
configuration.
2. Check the network connections between the slave device and the master device.
2.2.66 134243766 1588 clock PTP link abnormal

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if a PTP link has serious packet loss problem.
Alarm Level:Major
None
System Impact
The 1588 slave clock link detects that the link becomes abnormal due to serious packet
loss problem. The master link alarm may cause 1588 master/slave link changeover. A
slave link that has the alarm may not be selected as the link to which the changeover is
performed.
2-64
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
Probable Cause
The link packet loss rate exceeds the threshold.
Handling Suggestion
Check the network connections between the master device and the slave device.
2.2.67 134243767 1588 reference clock source unavailable

Alarm Property
l
l
l
l
Alarm Information:The alarm of 1588 reference clock source unavailable is reported
if all PTP links are abnormal.
Alarm Level:Major
None
System Impact
The 1588 reference clock source is unavailable, and the system performs changeover to
other reference clock source through the clock protection function.
Probable Cause
All PTP links are abnormal.
Handling Suggestion
Check the network connection of all PTP links.
2.2.68 134243768 The Capture status of 1588 clock timeout

Alarm Property
l
l
l
l
Alarm Information:In the case of the 1588 clock functioning as the system reference
clock source, the alarm is reported if the Capture status duration exceeds the
threshold.
Alarm Level:Major
None
2-65
SJ-20140402111513-008|20140528(R1.0)
System Impact
The system clock PLL cannot be locked properly when the 1588 reference clock source
is taken as the system reference clock source. The system performs changeover to other
reference clock source through the clock protection function.
Probable Cause
In the case that 1588 clock is taken as the system reference clock source, the duration of
the system clock PLL being in the Capture status exceeds the threshold.
Handling Suggestion
1. Check the pakcet loss rate.
2. Cold start the device.
2.2.69 134243779 Device IP conflict

Alarm Property
l
l
l
l
Alarm Information:Device IP conflict, please check configuration on IP setting page.
None
System Impact
Network management line may be broken down, and OSPF may be failed.
Probable Cause
The same IP address was configured to different equipment.
Handling Suggestion
Please check system parameter page.
2.2.70 134317741 Loopback state in IF or modem port

Alarm Property
l
l
l
Alarm Information:Loopback at the wireless link port. The alarm is reported when the
port on the (MU/RCMU/RMEA) board is in loopback status (IF/baseband).
Alarm Level:Major
2-66
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
2.Setting modulation and demodulation loopback;
4.Setting IF loopback.
System Impact
Traffic is interrupted when the wireless link port is in loopback status.
Probable Cause
2. The board that reports the alarm is faulty.
Handling Suggestion
2. If the alarm persists after the preceding step, replace the faulty RMU board
(RCMU/RMEA daughter card).
2.2.71 134317764 RF outer loopback enabled

Alarm Property
l
l
l
l
Alarm
Alarm
Alarm
Alarm
Code:134317764
Information:RF outer loopback is enabled.
Level:Critical
None
System Impact
Remote traffic looped.
Probable Cause
RF outer loopback enabled and it is for debug
Handling Suggestion
Close the RF outer loopback function.
2-67
SJ-20140402111513-008|20140528(R1.0)
2.2.72 134317765 TDM route has been discarded

Alarm Property
l
l
l
l
Alarm Information:The alarm is reproted when TDM route is dropped due to air
capacity is not enough. Please find the detail information from TDM route Info page.
Alarm Level:Major
None
System Impact
Probable Cause
Air capacity is not enough
Handling Suggestion
1. Please check the valid condition from TDM route Info page.
2. Modify workmode modulation configuration and make sure it is in the range of the valid
condition.
2.3 Processing alarm

2.3.1 6201 Software loading failure
Alarm Property
l
l
l
l
Alarm Code:6201
Alarm Information:The alarm is reported when the CPU/FPGA or other software fails
to be loaded.
Alarm Level:Major
Alarm Type:Processing alarm
0.CPU Version;
1.FPGA Version;
29.PVG Firmware;
30.PVG CFG Version;
2-68
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
31.ODU Firmware.
System Impact
1.
Board Status:
The board is faulty.
2.
Service Impact:
Board services are down.
Probable Cause
1. The board's software version, which is saved on the main control board, is incorrect.
2. The board is faulty.
Handling Suggestion
1. Download official version and active it if the run version is default version.
2. Download the run version again and reboot the board if the run version is official
version.
2.3.2 6206 Running software version fault

Alarm Property
l
l
l
l
Alarm Code:6206
Alarm Information:When the main control board detects that the running software
version does not exist or is faulty, this alarm is reported.
Alarm Level:Major
[8250]
3145728. RCUA CPU version;
3145729. RCUB CPU version;
3147776. RCUA FPGA version;
3147777. RCUB FPGA version;
9568784. RMUB CPU version;
9570832. RMUB FPGA version;
9570833. RMUB FPGA version(1.0);
9597456. RMUB FW version;
9599504. RMUB PVG CFG version(1.0);
9601552. RMUB ODU Firmware(1.0);
2-69
SJ-20140402111513-008|20140528(R1.0)
9568800. RMUC,RMUD CPU version;

9570848. RMUC,RMUD FPGA version;
9570849. RMUC FPGA version(1.0);
9597472. RMUC,RMUD FW version;
9599520. RMUC PVG CFG version(1.0);
9630210. PVG CFG version;
9628162. PVG Firmware;
9632258. ODU Firmware;
9503265. RTUA,RTUB,RTUC,RTUH,RTUN CPU version;
9503424. RTUM CPU version;
9505280. RTUA FPGA version;
9505296. RTUB FPGA FUNC=0 version;
9505297. RTUB FPGA FUNC=1 version;
9505312. RTUC FPGA version;
9505392. RTUH FPGA version;
9505488. RTUN FPGA version;
[8120]
3145732. RCMU CPU version;
3147780. RCMU FPGA version;
3205636. RCMU PVG Firmware;
3207684. RCMU PVG CFG version;
3209732. ODU Firmware;
[8950]
3145773.CPU file;
3147781.FPGA file;
3205637.PVG_FW file;
2354.SRU_CFG file;
3207685.PVG_CFG file;
System Impact
1.
Board Status:
Board operation is normal.
2.
Service Impact:
Board functions improperly, and board services are down.
2-70
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
Probable Cause
1. The running software is damaged.
2. The running software is lost.
3. The running software does not exist in the software package.
Handling Suggestion
In Software Version Management, re-download the correct software version package.
2.3.3 6213 Board inserted incorrectly

Alarm Property
l
l
l
l
Alarm Code:6213
Alarm Information:This alarm is reported when the main control board detects that the
inserted board differs from the configured board.
Alarm Level:Major
1. The module ID of the board inserted at NE is different from the configured board;
2. The type of the board inserted at NE is different from the configured board.
System Impact
I. Board Status:
Board operation is normal.
II. Service Impact:
Board functions improperly, and board services are down.
Probable Cause
The board type configured at background is incorrect, or the board is incorrectly inserted
at foreground.
Handling Suggestion
1. Enter configuration management interface,reconfigure the correct board type in shelf
interface.
2. Insert a correct board at foreground.
2.3.4 6223 Firmware does not take effect

Alarm Property
l
Alarm Code:6223
2-71
SJ-20140402111513-008|20140528(R1.0)
l
l
l
Alarm Information:It is need to hard reset the board in order to active the new load
firmware.
Alarm Level:Major
1. BOOT does not take effect;
2. EPLD does not take effect.
System Impact
The new firmware does not take effect.
Probable Cause
Firmware has loaded, it is need to hard reset the board to become effective.
Handling Suggestion
Hard reset this board.
2.3.5 6224 Main BOOT CRC error

Alarm Property
l
l
l
l
Alarm Code:6224
Alarm Information:The alarm is reported when the main BOOT CRC is error.
None
System Impact
It will lead to active BOOT fail
Probable Cause
The main BOOT CRC error is detected when the activing firmware, it leads to active boot
fail.
Handling Suggestion
Reset this board, active the firmware again.
2-72
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
2.3.6 6225 Version has been roll back

Alarm Property
l
l
Alarm Code:6225
Alarm Information:The alarm is reported when the actived version power on fail,
and it lead to version active fail .
l
l
Alarm Level:Major
None
System Impact
Version acitve fail
Probable Cause
There is abnormal during the actived version power on.
Handling Suggestion
1. Download new standby package.
2. Delete the standby package.
2.3.7 134218745 Insufficient flash memory

Alarm Property
l
l
l
l
Alarm Information:This alarm is reported when flash memory does not have sufficient
space.
Alarm Level:Major
None
System Impact
This alarm does not affect any traffic, but it may lead to fail to save data.
Probable Cause
The flash memory is insufficient.
2-73
SJ-20140402111513-008|20140528(R1.0)
Handling Suggestion
1. On the version management page,delete the backup version package file.
2. Delete the redundant files,including backup patch packages,black-box files,and
performance data files.
2.3.8 134243738 OSPF interface configuration error

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if the OSPF interface configuration is
incorrect.
None
System Impact
This alarm may cause that the neighbor relation cannot be established properly.
Probable Cause
The interface configurations at the two ends are different. The interface configurations
include version number, area configuration, network mask, Hello timer interval, and Dead
timer interval.
Handling Suggestion
Ensure that the interface configurations at the two ends are consistent.
2.3.9 134243739 OSPF virtual link interface configuration error

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if the OSPF virtual interface configuration is
incorrect.
Alarm Level:Major
None
2-74
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
System Impact
This alarm may cause that the virtual neighbor relation cannot be established properly.
Probable Cause
The virtual interface configurations at the two ends are different. The virtual interface
configurations include version number, area configuration, network mask, Hello timer
interval, and Dead timer interval.
Handling Suggestion
Ensure that the virtual interface configurations at the two ends are consistent.
2.4 Communication Alarm

2.4.1 134217734 Received signal level alarm
Alarm Property
l
l
l
l
Alarm Information:The alarm is reported when the Rf unit's received signal level
exceeds the specified threshold.For AOU,it refers to RF received singal level exceeds
the threshold.
Alarm Level:Minor
Alarm Type:Communication Alarm
1. The actual received level is higher than the given upper threshold;
2. The actual received level is lower than the given lower threshold.
System Impact
It does not affect the traffic carried by the board,but may cause incomplete data.
Probable Cause
The alarm is reported when the RF received level exceeds the specified threshold.
Handling Suggestion
1.
Adjust the threshold(Path for 8250 2.0/8950/8120 LMT: Performance->Performance

Threshold.Path for 8250 1.0 LMT: Radio Link->Radio Link Configuration->Set RF
Parameter).
2. Adjust the Rf unit RSL.
2-75
SJ-20140402111513-008|20140528(R1.0)
2.4.2 134217736 UAS alarm of radio

Alarm Property
l
l
l
l
Alarm Information:This alarm is reported when UAS(unavailable seconds of
neighborhood time)change of radio is detected.
None
System Impact
This alarm affects traffic.
Probable Cause
The radio link signal degrades.
Handling Suggestion
1. If the air interface is unlocked or MSE is bad, modify the radio link configuration
parameters to ensure the link works properly.
2. If the fault persists, after the preceding steps,replace ACMUA/RMU(RCMU/RMEA
daughter card) or Rf unit.
2.4.3 134237731 E1-ALOS

Alarm Property
l
l
l
l
Alarm Information:The alarm indicates that electrical signal is interrupted at physical
layer. The local end does not receive the switchover signal or electrical signals sent
by other equipment.
1.
2.
3.
4.
5.
6.
E1
E1
E1
E1
E1
E1
port
port
port
port
port
port
1
2
3
4
5
6
on
on
on
on
on
on
the
the
the
the
the
the
panel;
panel;
panel;
panel;
panel;
panel;
2-76
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
7 on the panel;
8 on the panel;
9 on the panel;
10 on the panel;
11 on the panel;
12 on the panel;
13 on the panel;
14 on the panel;
15 on the panel;
16 on the panel;
17 on the panel;
18 on the panel;
19 on the panel;
20 on the panel;
21 on the panel;
22 on the panel;
23 on the panel;
24 on the panel;
25 on the panel;
26 on the panel;
27 on the panel;
28 on the panel;
29 on the panel;
30 on the panel;
31 on the panel;
32 on the panel;
System Impact
The E1 receiving relay signal carried by the TU is interrupted.
Probable Cause
1. The input E1 cable is connected reversely or broken.
2. The connection between E1 cable and external device (DDF) fails.
3. E1 port is faulty.
Handling Suggestion
1. Ensure that E1 cable is unbroken and connected properly.
2. Ensure that the equipment connected to E1 cable such as DDF is working properly.
3. If the alarm persists after the preceding steps, the E1 port may be faulty. Replace the
RTU board.
2-77
SJ-20140402111513-008|20140528(R1.0)
2.4.4 134237759 E1-Code-Violation

Alarm Property
l
l
l
l
Alarm Information:A CV is detected when coding errors occur in line side transmission.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
1 on the panel;
2 on the panel;
3 on the panel;
4 on the panel;
5 on the panel;
6 on the panel;
7 on the panel;
8 on the panel;
9 on the panel;
10 on the panel;
11 on the panel;
12 on the panel;
13 on the panel;
14 on the panel;
15 on the panel;
16 on the panel;
17 on the panel;
18 on the panel;
19 on the panel;
20 on the panel;
21 on the panel;
22 on the panel;
23 on the panel;
24 on the panel;
25 on the panel;
26 on the panel;
27 on the panel;
28 on the panel;
29 on the panel;
30 on the panel;
31 on the panel;
32 on the panel;
2-78
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
System Impact
The E1 signal carried by the TU is lost, and the service is interrupted.
Probable Cause
1.
2.
3.
4.
The input E1 cable is connected reversely or broken.

The connection between E1 cable and external device (DDF) fails.
device is not properly grounding maybe cause this alarm.
E1 port is faulty.
Handling Suggestion
1.
2.
3.
4.
Ensure that E1 cable is unbroken and connected properly.

Ensure that the equipment connected to E1 cable such as DDF is working properly.
All devices must be properly grounding.
If the alarm persists after the preceding steps, the E1 port may be faulty. Replace the
RTU board.
2.4.5 134237763 Loss of Frames alarm

Alarm Property
l
l
l
l
Alarm Information:Detection of lost CESoETH frames is accomplished by use of the
sequence number, either from the RTP header or the CESoETH control word. If the
frame loss ratio persists above the defined threshold for 2 seconds, a Loss of Frames
alarm will be reported. The Loss of Frames alarm will be cleared if frame loss ratio
remains below the defined threshold for 10 seconds.
Every subcode represents a CES path:;
1~16 are used for E1 port 1~16;
101~163 are used for optical port 1;
164~226 are used for optical port 2.
System Impact
The CES flow over the link is interrupted.
Probable Cause
1. The clock is not synchronous.
2. The CES configurations at both ends of the link are not consistent.
3. The bandwidth of EVC is too low, and the link is congestion.
2-79
SJ-20140402111513-008|20140528(R1.0)
4. The radio link is abnormal.

5. Cable, optical fiber or optical module is faulty.
Handling Suggestion
1.
2.
3.
4.
5.
Ensure there are no clock alarm reported.

Ensure the CES configurations at both ends of the link are the same.
Increase the bandwith of EVC.
Ensure there are no radio link alarm reported.
Replace the cable, optical fiber and optical module. Ensure the cable, optical fiber are
connected properly.
2.4.6 134237764 Late Frames alarm

Alarm Property
l
l
l
l
Alarm Information:If CESoETH frames late arrive after their scheduled playout time,
these frames are considered as lost frames. If the percentage of late arriving frames
exceeds the defined level for 2 seconds, a Late Frame alarm will be reported. The
Late Frame alarm will be cleared if the percentage of late arriving frames stays under
the defined threshold for 10 seconds.
System Impact
Probable Cause
1. The clock is not synchronous.
2. The bandwidth of EVC is too low, and the link is congestion.
Handling Suggestion
1. Ensure there are no clock alarm reported.
2. Increase the bandwith of EVC.
2-80
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
3. Replace the cable, optical fiber and optical module. Ensure the cable, optical fiber are
connected properly.
2.4.7 134237765 Malformed Frames alarm

Alarm Property
l
l
Alarm Information:A malformed frame is either or both of the following conditions
apply: 1) If RTP is used, the PT value in its RTP header does not correspond to one
of the PT values allocated for this direction of the emulated circuit. 2) For CESoETH
frames containing valid TDM data with the defect indicator L=0, and for which the
actual payload size can be unambiguously determined, the payload size does not
match the size defined for this flow
If the percentage of malformed CESoETH frames persists above a defined level for 2
seconds, a Malformed Frames alarm will be reported. The Malformed Frames alarm
will be cleared if no malformed packets have been detected for 10 seconds.
l
l
System Impact
Probable Cause
1.
2.
3.
4.
The CES configurations is incorrect.

The bandwidth of EVC is too low, and the link is congestion.
The radio link is abnormal.
Cable, optical fiber or optical module is faulty.
Handling Suggestion
1.
2.
3.
4.
Ensure the CES configurations are correct.

Increase the bandwith of EVC.
Replace the cable, optical fiber and optical module. Ensure the cable, optical fiber are
connected properly.
2-81
SJ-20140402111513-008|20140528(R1.0)
2.4.8 134237766 Misconnection alarm

Alarm Property
l
l
l
l
Alarm Information:Should a frame be wrongly directed to a CES IWF, it is possible for
it to be mis-interpreted as a genuine CESoETH frame. If the percentage of such stray
frames persists above the defined level for 2 seconds, the Misconnection alarm will
be reported. The Misconnection alarm will be cleared if no stray frames have been
detected for 10 seconds.
Alarm Level:Major
System Impact
The CES flow over the link may be anomalous.
Probable Cause
1. The CES configurations at both ends of the link are not consistent.
2. The radio link is abnormal.
Handling Suggestion
1. Ensure the CES configurations at both ends of the link are the same.
2. Ensure there are no radio link alarm reported.
3. Ensure the cable, optical fiber are connected properly.
2.4.9 134237767 Jitter Buffer Overrun alarm

Alarm Property
l
l
Alarm Information:The main purpose of jitter buffer is to smooth out variation in arrival
time of the CESoETH frames. Either overrun or underrun conditions may occur. The
Jitter Buffer Overrun condition occurs when the jitter buffer at the TDM-bound IWF
cannot accommodate the
2-82
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
newly arrived valid CESoETH frame in its entirety. The Jitter Buffer Underrun condition
occurs when there is no correctly received CESoETH payload ready to be played out
on the TDM interface, and replacement data must be played out instead. Primarily
this occurs due to frames lost in the MEN, or discarded due to error conditions, hence
this is not usually identified separately.
If the percentage of frames causing Jitter Buffer Overruns persists above the defined
level for 2 seconds, a Jitter Buffer Overrun alarm will be reported. The Jitter Buffer
Overrun alarm will be cleared if no cases of jitter buffer overrun have been detected
for 10 seconds.
l
l
System Impact
Probable Cause
1.
2.
3.
4.
The clock is not synchronous.

The radio link signal degrades, and the jitter increases.
The configuration of jitter buffer is too small.
Too many network hops lead to jitter increase.
Handling Suggestion
1.
2.
3.
4.
Ensure there are no clock alarm reported.

Increase the jitter buffer.
Decrease the network hops.
2.4.10 134237934 E1-AIS

Alarm Property
l
l
Alarm Information:The alarm indicates that every bit of the input singnal is "1"
The E1-AIS alarm is reported if 255 consecutive bits in the received signal is "1".
2-83
SJ-20140402111513-008|20140528(R1.0)
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
E1
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
port
1 on the panel;
2 on the panel;
3 on the panel;
4 on the panel;
5 on the panel;
6 on the panel;
7 on the panel;
8 on the panel;
9 on the panel;
10 on the panel;
11 on the panel;
12 on the panel;
13 on the panel;
14 on the panel;
15 on the panel;
16 on the panel;
17 on the panel;
18 on the panel;
19 on the panel;
20 on the panel;
21 on the panel;
22 on the panel;
23 on the panel;
24 on the panel;
25 on the panel;
26 on the panel;
27 on the panel;
28 on the panel;
29 on the panel;
30 on the panel;
31 on the panel;
32 on the panel;
System Impact
The E1 receiving relay signal carried by the TU is interrupted.
Probable Cause
1. The E1 signal sent from uplink equipment to NR8250 equipment is invalid, that is,
every bit in the signal is "1".
2. The RTU board that reports the alarm is faulty.
2-84
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
Handling Suggestion
1. Ensure that signal from the uplink direction is correct, that is, the not every bit of the
signal is 1.
2. If the alarm still exists, it indicates that the RTU board is faulty. Please replace it.
2.4.11 134237938 Air-E1-AIS

Alarm Property
l
l
Alarm Information:The alarm indicates that every bit of the input singnal is "1"
The Air-E1-AIS alarm is reported if 255 consecutive bits in the received signal is "1"
from the air E1 port.
l
l
Every subcode represents a E1 port.
System Impact
The E1 receiving signal carried by the MU is interrupted.
Probable Cause
1. The E1 signal sent to the equipment is invalid, that is, every bit in the signal is "1".
2. The RMU board that reports the alarm is faulty.
Handling Suggestion
1. Ensure that signal from air port is correct, that is, the not every bit of the signal is 1.
2. If the alarm still exists, it indicates that the RMU board is faulty. Please replace it.
2.4.12 134239928 Radio link failure alarm

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if the IF is unlocked due to abnormal external
clock of the IF unit or internal hardware fault.
None
2-85
SJ-20140402111513-008|20140528(R1.0)
System Impact
1.
2.
In non-protection mode, traffic is interrupted.

In protection mode:
-Traffic is interrupted if both active and standby traffic units are unlocked.
-Switchover takes place if active and standby traffic units are not unlocked.
Probable Cause
1. The IF is unlocked.
2. The IF circuit is faulty.
Handling Suggestion
Replace the RMU board(RCMU/RMEA daughter card).
2.4.13 134239929 Baseband alarm

Alarm Property
l
l
l
l
Alarm
Alarm
Alarm
Alarm
Code:134239929
Information:It is the alarm detected in the Modem.
Level:Critical
Type:Communication Alarm
1. The CPU running is suspended in modulation and demodulation.
System Impact
For subcode 1:
1. In non-protection mode, the traffic is interrupted.
2. In protection mode, if both the active and standby traffic units are suspended, the traffic
is interrupted. otherwise, the active/standby changeover is performed, and the service
is not affected.
Probable Cause
1. The configurations at both ends are incorrect.
2. The local transceiver and the remote transceiver are faulty.
3. The shelf at the local end is faulty.
Handling Suggestion
1. Ensure that the configurations at the two ends including Rf unit frequency, mRf
unitlation modes, and bandwidth are consistent and correct.
2. Check whether the local end reports the unlock alarm. If yes, replace the RMU
board(RCMU/RMEA daughter card),otherwise, go to step 3.
2-86
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
3. Check whether the remote end reports the unlock alarm. If yes, replace the RMU
board(RCMU/RMEA daughter card).
2.4.14 134239930 RF unit fault

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if the Rf unit detects a fault.
0. Tx RF PLL unlocked;
1. Tx IF PLL unlocked;
2. Rx RF PLL unlocked;
3. Rx IF PLL unlocked;
4. Rf unit transmit power is 3db lower than target value;
5. Rf unit cable compensation out of range alarm;
6. Rf unit RX AGC loop out of range alarm;
7. TRX_EEPROM alarm;
8. Telemetry communication alarm;
9. IFC_EEPROM alarm;
10. TX input level low or input signal absence alarm;
11. Calibration alarm;
12. RF Loopback alarm;
13. TX input signal is too high (3db higher);
20. Rf unit TX Power is higher than Max TX Power allowed by current modulation;
21. PA is disabled;
22. Rf unit PA is too hot;
23. Rf unit is rebooting;
System Impact
Sub-codes affect the running of traffic as follows:
Sub-code 0: In protection mode, it leads to switchover between active and standby traffic
units. in non-protection mode, it leads to traffic interruption.
2-87
SJ-20140402111513-008|20140528(R1.0)
Sub-code 4: It may lead to error codes.
Sub-code 7: It may lead to traffic interruption.
Sub-code 10: Traffic is interrupted because ODU disables the power amplifier forcibly.
Sub-code 22: PA is too hot,Traffic is interrupted because ODU disables the power amplifier
automatically.
Probable Cause
The description of alarm sub-codes are as follows:
0.Rf unit failure.
1.Rf unit failure.
2.Rf unit failure.
3.Rf unit failure.
4.Rf unit failure.
5.The power of the IF signal sent from IDU to Rf unit is low.
6.The power of the RF signal received by Rf unit is low.
7.Rf unit failure.
8. MU board or IF cable is faulty.
9. Rf unit failure.
10.MU board or IF cable is faulty.
11.Rf unit failure.
12.Rf unit RF Loopback is enabled.
13.If board failure.
20.The configured TX Power is too high.
21.Rf unit PA is disabled.
22.Rf unit failure.
2-88
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
23.Rf unit is rebooting.
Handling Suggestion
Process the sub-codes as follows:
2.4.15 134239931 Transmission unit invalid

Alarm Property
l
l
l
l
Alarm Information:The transmission unit fails due to alarms (1+1 protection and 1+0
protection are distinguishe through subcode).
0. Traffic unit failure (1+1) caused by the If unit alarm (IF unlock, modulated part is not
working properly,baseband part is not working properly);
1. Traffic unit failure (1+0) caused by the If unit alarm (IF unlock,modulated part is not
working properly, baseband part is not working properly);
2. Traffic unit failure (1+1) caused by the Rf unit alarm (RF PLL unlock at sender,IF PLL
unlock at sender,RF PLL unlock at receiver.IF PLL unlock at receiver);
3. Traffic unit failure (1+0) caused by the Rf unit alarm (RF PLL unlock at sender, IF PLL
unlock at sender, RF PLL unlock at receiver, IF PLL unlock at receiver);
System Impact
The traffic carried by the traffic unit is interrupted.
Probable Cause
1. Rf unit link is broken.
2. The If board(RCMU,RMEA daughter card) or the Rf unit is faulty.
Handling Suggestion
1. Ensure that the Rf unit is rightly connected.
2. Replace the If board(RCMU/RMEA daughter card) or Rf unit that reports the alarm.
2.4.16 134239935 RF mute

Alarm Property
l
l
l
Alarm Information:The alarm is reported if the Mute is enable by user.
Alarm Level:Major
2-89
SJ-20140402111513-008|20140528(R1.0)
None
System Impact
1.
2.
In non-protection mode, traffic is interrupted.

In protection mode:
-Traffic is interrupted when choose a Rf unit mute enable if use FD and SD.
-Traffic is not interrupted when choose a Rf unit mute enable if use HSB,but traffic is
interrupt if choose two ODU mute enable.
Probable Cause
1. In non-protection mode, users set the "Rf unit Mute Enable"manually.
2. In protection mode:
(1)If FD is used, users manually set one Rf unit "Rf unit Mute Enable".
(2)If HSB and SD are used, users set two Rf unit by "Mute Enable" manually.
Handling Suggestion
Close the Rf unit mute enable function.
2.4.17 134239937 Modem part unlock

Alarm Property
l
l
l
l
Alarm Information:The modulation and demodulation part is unlocked.
None
System Impact
1.
2.
In non-protection mode, the traffic is interrupted.

In protection mode, if both the active and standby traffic units are unlocked, the traffic
is interrupted. otherwise, the active/standby changeover is performed.
Probable Cause
1. The working modes,bandwidth is not same for local and far, or local Tx frequency is
not same as far Rx frequency, or local Rx frequency is not same as far Tx frequency.
2-90
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
2. ODU switch on MU panel(RCMU/RMEA daughter card) is closed.

3. The RSL at local device is low.
4. The modem part of ACMUA/MU board(RCMU/RMEA daughter card)is faulty.
Handling Suggestion
1. Make sure the working mode,bandwidth for local and far is same, and local Tx
frequency and far Rx fequency is same,local Rx frequency and far Tx frequency is
same.
2. Open the ODU's switch on MU panel.
3. Raise the power at remote device.
4. Replace the faulty ACMUA/MU board(RCMU/RMEA daughter card).
2.4.18 134239938 Protection function failure

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if protection function fails.
None
System Impact
The receive-end protection function that is configured with does not take effect, thus the
protection cannot be implemented.
Probable Cause
1. Protection function fails when powers on to initialize.
2. The standby IF hardware is unlock.
3. The standby IF hardware is faulty.
Handling Suggestion
1. Restart the standby MU (RCMU) board,and let it power on again.
2. If the standby IF hardware is unlock,please configure the protection parameters
again,if it is still unlock,please handle it following below steps.
3. Check that the Rf unit's switch on MU panel is closed or not ,if so,please open it,if it is
still unlock after open the switch,please raise the power of remote end.
4. Replace the faulty If board(RCMU/RMEA daughter card).
2-91
SJ-20140402111513-008|20140528(R1.0)
2.4.19 134239962 RF unit fatal error

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported as critical alarm if the Rf unit detects a fault
that will impact raido link.
0. Tx RF PLL unlocked;
1. Tx IF PLL unlocked;
2. Rx RF PLL unlocked;
3. Rx IF PLL unlocked;
4. Rf unit transmit power is 3db lower than target value;
5. TRX_EEPROM alarm;
6. TX input level low or input signal absence alarm;
7. Rf unit PA is too hot.
System Impact
Sub-code 0~
3: In protection mode, it leads to switchover between active and standby traffic units. in
non-protection mode, it leads to traffic interruption.
4: It may lead to error codes.
5: It may lead to traffic interruption.
6: Traffic is interrupted because Rf unit disables the power amplifier forcibly.
7: PA is too hot,Traffic is interrupted because Rf unit disables the power amplifier
automatically.
Probable Cause
0. Rf unit failure Cause Tx RF PLL unlocked.
1. Rf unit failure Cause Tx IF PLL unlocked.
2. Rf unit failure Cause Rx RF PLL unlocked.
3. Rf unit failure Cause Rx IF PLL unlocked.
4. Rf unit failure Cause Rf unit transmit power is lower than target value.
5. Rf unit failure Cause TRX_EEPROM alarm.
6. If board or IF cable is faulty.
7. Rf unit failure.
2-92
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
Handling Suggestion
0~3.Power off and then restart the Rf unit. If the alarm persists, replace the Rf unit.
4~5.Replace the Rf unit.
6.Replace the IF cable. If the alarm persists, replace the If board.
7.Cool the Rf unit, If the alarm persists, replace the Rf unit.
2.4.20 134239963 RF unit error

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported when Rf unit find out that Rf unit is manually
configured by user or some events that will not impact radio link.
Alarm Level:Minor
0. Telemetry communication alarm;
1. RF Loopback alarm;
2. RX RF input signal below threshold (10-6 receiver threshold + 3dB);
3. Rf unit TX Power is higher than Max TX Power allowed by current modulation;
4.
PA is disabled;
5. Rf unit is rebooting.
System Impact
0: None.
1:TX signal is transmitted and also loop back to IDU.
2:None.
3:None.
4:No Tx signal will be transmitted.
5:It may lead to error codes.
Probable Cause
0.If
1.
2.
3.
4.
5.
board or IF cable is faulty.

Rf unit RF Loopback is enabled.
The receiving power is near to or below the RSSI threshold.
The configured TX Power is too high.
Rf unit PA is disabled.
Rf unit is rebooting.
2-93
SJ-20140402111513-008|20140528(R1.0)
Handling Suggestion
0.Ignore this alarm when 1+1 protection mode was configured and traffic is normal.
1. Replace the IF cable. If the alarm persists, replace the If board.
2. Disable RF loopback. If the alarm persists, replace the Rf unit.
3. Increase the remote Rf unit's transmitting power. Adjust and improve the link path.
4. Configure TX Power allowed by current modulation.
5. If sub-codes 1 and 2 appear, re-configure the frequency and power, and then set TX
UNMUTE. If the alarm persists, check sub-code and find out whether the PA is too hot.
If yes, wait till the PA cools down.
6. Wait for the Rf unit rebooting, the alarm will be cleared automatically.
2.4.21 134239967 Security Link Id Inconsistent

Alarm Property
l
l
l
l
Alarm Information:Local security link id is inconsistent with neighbor's.
None
System Impact
Probable Cause
1. Local security link id is inconsistent with neighbor's.
2. Radio link status is abnormal.
Handling Suggestion
1. Check configuration and make sure loacl and neighbor security link id configuration
parameters consistent.
2. Check the radio link status and make sure it is normal.
2.4.22 134241729 Ethernet port disconnected

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported when the Ethernet port is in linkdown status.
2-94
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
RCU NMS port or RTUM FE1 port;

RCU GbE port or RTUM FE2 port;
RCU TDMEX port or RTUM FE3 port;
RTUM FE4 port;
RTUM GbE1 port;
RTUM GbE2 port;
RTUH GbE1 port;
RTUH GbE2 port;
RTUH GbE3 port;
RTUN GbE1 port;
RTUN GbE2 port;
RTUN GbE3 port;
RTUN GbE4 port;
20.RCMU NMS port;
25.RCMU GbE1 port;
26.RCMU GbE2 port;
27.RCMU GbE3 port;
28.RCMU GbE4 port;
29.ACMUA GbE port;
30.ACMUA multiplex port;
System Impact
Ethernet traffic at the port where an alarm is reported is interrupted.
Probable Cause
1. Cable is disconnected at local end.
2. Network cable is faulty at local end.
3. The network cable of relay device connected to microwave boards is not connected
normally.
4. Network port is faulty at local end.
Handling Suggestion
1. If the network cable is not connected normally,please connect cable to the port.
2. If the network cable is faulty,please replace the network cable.
3. If the network of relay device is not connected well,please check the cable is whether
good or not,and connect it to relay device normally.
4. If the network port is bad,please replace the board.
2-95
SJ-20140402111513-008|20140528(R1.0)
2.4.23 134241733 Optical module not in position

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported when the Ethernet port SFP lost.
1. RTUH GbE1 port;
2. RTUH GbE2 port;
3. RTUH GbE3 port;
11.RTUN GbE1 port;
12.RTUN GbE2 port;
13.RTUN GbE3 port;
14.RTUN GbE4 port;
21.RCMU GbE1 port;
22.RCMU GbE2 port;
23.RCMU GbE3 port;
24.RCMU GbE4 port;
25.ACMUA GbO port.
System Impact
Ethernet traffic at the port where an alarm is reported is interrupted.
Probable Cause
SFP is not in position.
Handling Suggestion
1. Replace the Ethernet SFP.
2.4.24 134243751 RMEP CCM packet lost

Alarm Property
l
l
l
Alarm Information:The alarm is reported if LMEP does not receive the CCM packet of
RMEP within 3.5 CCM periods.
Alarm Level:Major
2-96
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
None
System Impact
It does not affect the traffic carried by the board.
Probable Cause
1. No MEP is configured at the opposite-end NE or MEP level is not same.
2. The bearer layer is faulty.
3. The network is seriously congested.
Handling Suggestion
1. Ensure the MEP at the opposite end is exist and in correct level.
2. Ensure that the bearer layer is normal.
3. Ensure that the network is not congested.
2.4.25 134243752 RMEP CCM packet error

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if LMEP receives incorrect CCM packet.
Alarm Level:Major
None
System Impact
Probable Cause
RMEP is faulty or RMEP configuration is incorrect.
Handling Suggestion
Check the configuration of the RMEP in the alarm.
2-97
SJ-20140402111513-008|20140528(R1.0)
2.4.26 134243753 RMEP Mac Status error

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if LMEP receives the CCM packet in which
the Mac status information is abnormal.
Alarm Level:Major
None
System Impact
Probable Cause
The Mac status of the MEPs in the MA is abnormal.
Handling Suggestion
Check the port status of the RMEPs in the MA.
2.4.27 134243754 RMEP RDI

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if LMEP receives the CCM packet in which
the RDI information is abnormal.
Alarm Level:Major
None
System Impact
Probable Cause
Some MEPs in the same MA has alarms.
2-98
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
Handling Suggestion
Check the MEP in alarm in the MA.
2.4.28 134243755 Ethernet devices cross-connected

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if LMEP receives the CCM packet from MEP
of other MA.
Alarm Level:Major
None
System Impact
Probable Cause
1. The MA names on the two ends are different.
2. The network has circle or cross connection.
Handling Suggestion
1. Ensure that the MA names at the two ends are the same.
2. Ensure that the MD levels at the two ends are the same.
3. Ensure that there is no cross connection on the service link.
2.4.29 134243769 EFM local link fault

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if link fault is detected at the local port.
1. Link Fault;
2. Dying Gasp;
3. Critical Event.
2-99
SJ-20140402111513-008|20140528(R1.0)
System Impact
If the local link is faulty, the service at the port may be disconnected.
Probable Cause
The local end detects link fault.
Handling Suggestion
Check the physical connections of the local optical port.
2.4.30 134243770 EFM remote link fault

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if the local end detects the link fault
information sent from the remote end.
1. Link Fault;
2. Dying Gasp;
3. Critical Event.
System Impact
If the remote link is faulty, the service at the port may be disconnected.
Probable Cause
The remote end detects link fault.
Handling Suggestion
Check the physical connections of the remote optical port.
2.4.31 134243771 EFM discovery process failure

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if the discovery process fails.
2-100
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
1.
2.
3.
4.
Local connection failure;

The local OAM does not receive the OAM packet within specified time;
The remote OAM does not satisfy the requirement of the local OAM;
The local OAM does not satisfy the requirement of the remote OAM;
System Impact
The service at the port may be disconnected.
Probable Cause
The discovery process fails.
Handling Suggestion
1. Check whether there are alarms related to the optical module or boards. If there are,
remove the alarms.
2. Check whether the optical fibers or cables are faulty. Replace the faulty fiber or cable
if there is any.
3. Check the OAM parameter setting of NEs at the two ends to see whether they are
consistent.
4. Check whether the Tunnel bandwidth reaches the maximum limit. If it does, perform
Tunnel capacity expansion or find out the source that illegally transmits the large
amount of data and solve the problem.
2.4.32 134243776 EFM local link lost

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if heartbeat is lost at the local end and the
remote end of EFM.
None
System Impact
The link is disconnected.
Probable Cause
Heartbeat is lost at the local end and the remote end of EFM.
2-101
SJ-20140402111513-008|20140528(R1.0)
Handling Suggestion
Check the link connectivity.
2.4.33 134243783 APS Message detecting abnormal

Alarm Property
l
l
l
l
Alarm Information:When ELPS subsystem detect APS Message lost or APS message
A, B, R, T bit mismatch trigger the notice.
Alarm Level:Major
1.
2.
3.
4.
5.
Not receive APS packet in 17.5 second;

A bit not matching,APS channel mismatch;
B bit don't match,the switch type mismatch;
R bit does not match,revertive type mismatch;
T bit does not match,bridge type mismatch.
System Impact
Can lead to linear protection failure.
Probable Cause
When ELPS subsystem detect APS Message lost or APS message A, B, R, T bit mismatch
trigger the notice.
Handling Suggestion
For APS lost notice check physical link and configuration, other notice check protect group
configuration.
2.4.34 134243784 Ethernet client signal fail

Alarm Property
l
l
l
l
Alarm Information:The RMEP detected a failure or defect event in the Ethernet client
signal.
Alarm Level:Major
None
2-102
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
System Impact
Probable Cause
1. The RMEP detected a failure or defect event in the Ethernet client signal.
Handling Suggestion
1. Ensure the RMEP is configured correctly.
2. Ensure that the client layer is normal.
2.4.35 134317734 Rf unit communication is interrupted

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if establishing an Rf unit link fails or the Rf
unit link is broken.
None
System Impact
The traffic transmitted between the local and remote ends is interrupted.
Probable Cause
1. The Rf unit is not powered on.
2. If board(RCMU/RMEA daughter card) of the IDU is faulty.
3. The Rf unit is faulty.
Handling Suggestion
1. Ensure that the IF cable is good, and the IF head is made correctly, and needed to
ensure that the power supply to the Rf unit is normal (40V~60V) in 8250 equipment.
2. If the alarm remains after the preceding step, the If board (RCMU/RMEA daughter
card) may be faulty. Replace the faulty board.
3. If the alarm remains, replace the Rf unit.
2-103
SJ-20140402111513-008|20140528(R1.0)
2.5 QoS Alarm

2.5.1 134243772 EFM local link event
Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if EFM detects a local link event.
Alarm Level:Major
Alarm Type:QoS Alarm
1.
2.
3.
4.
Errored
Errored
Errored
Errored
Symbol Period Event;

Frame Event;
Frame Period Event;
Frame Seconds Summary Event.
System Impact
The link performance is affected.
Probable Cause
1. The number of errored symbols of the physical layer within the unit time exceeds the
preset threshold.
2. The number of errored frames of the MAC layer within the unit time exceeds the preset
threshold.
3. The number of errored frames of MAC layer within the unit frame amount exceeds the
preset threshold.
4. The number of errored frame seconds of the MAC layer within the unit time exceeds
the preset threshold.
Handling Suggestion
Check the link performance.
2.5.2 134243778 EFM loopback alarm

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if EFM initiates loopback or responds a
loopback instruction.
Alarm Level:Minor
2-104
SJ-20140402111513-008|20140528(R1.0)
Chapter 2 Alarm
1. Start a loopback test;
2. Respond a loopback test.
System Impact
This alarm indicates that the service is in the loopback status.
Probable Cause
The loopback test is started manually at the local end or the remote end.
Handling Suggestion
1. Ensure that the remote loopback response parameter of the port that reports the alarm
is disabled.
2. Check the ETH_EFM_LOOPBACK alarm of the remote NE and find out the port that
initiates loopback towards the remote NE.
2-105
SJ-20140402111513-008|20140528(R1.0)
2-106
SJ-20140402111513-008|20140528(R1.0)
Chapter 3
Notification
Table of Contents
Equipment Alarm........................................................................................................3-1
Communication Alarm ................................................................................................3-8
Processing alarm .....................................................................................................3-12
QoS Alarm ...............................................................................................................3-22
Environment Alarm...................................................................................................3-24
3.1 Equipment Alarm

3.1.1 10001 Board power-on completed
Alarm Property
l
l
l
l
Alarm Code:10001
Alarm Information:The notification is reported when the board is powered on.
Alarm Level:Notification
None
System Impact
None
Probable Cause
The board is powered on.
Handling Suggestion
The board is powered on.
3.1.2 10006 Board power-on failed

Alarm Property
l
Alarm Code:10006
3-1
SJ-20140402111513-008|20140528(R1.0)
l
l
l
Alarm Information:The notification is reported when the board fails to be powered on

due to the board's basic process power-on failure or timeout.
1. Process power-on failure;
2. Process power-on timeout.
System Impact
Board can not be normal.
Probable Cause
It is the notification of board's basic process failing to be powered on or timeout.
Handling Suggestion
1. Check whether some module part is timeout,if so,please replace the software version.
2. Check whether module error occurs,if so,please modify the configuration.
3.1.3 134243731 8032 port blocked

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if the 8032 protocol operation blocks the port.
1. The port is blocked due to local link disconnection;
2. The RPL OWNER port is blocked due to being controlled by the 8032 protocol.
System Impact
This alarm may cause traffic transmission path switchover and service interruption.
Probable Cause
The equipment port is blocked due to 8032 protocol operation.
Handling Suggestion
If the alarm code is 1, check the east-port and west-port link of the equipment that reports
the alarm.
3-2
SJ-20140402111513-008|20140528(R1.0)
Chapter 3 Notification
3.1.4 134243732 8032 port unblocked

Alarm Property
l
l
l
l
Alarm
Alarm
port.
Alarm
Alarm
Code:134243732
Information:The alarm is reported if the 8032 protocol operation unblocks the
Level:Notification
1. The port is unblocked due to local link recovery;
2. The RPL OWNER port is unblocked due to the SF packet being received.
System Impact
Probable Cause
The equipment port is unblocked due to 8032 protocol operation.
Handling Suggestion
No processing is required.
3.1.5 134243785 ERPS port blocked

Alarm Property
l
l
l
l
Alarm
Alarm
port.
Alarm
Alarm
Code:134243785
Information:The alarm is reported if the ERPS protocol operation blocks the
Level:Notification
1.
2.
3.
4.
The
The
The
The
port is blocked due to local link disconnection;

RPL OWNER port is blocked;
port is blocked due to the local MS/FS command;
port is blocked due to instance initialization;
System Impact
3-3
SJ-20140402111513-008|20140528(R1.0)
Probable Cause
The equipment port is blocked due to ERPS protocol operation.
Handling Suggestion
If the alarm code is 1,check the east-port and west-port link of the equipment that reports
the alarm.
3.1.6 134243786 ERPS port unblocked

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if the ERPS protocol operation unblocks the
port.
None
System Impact
None
Probable Cause
The equipment port is unblocked due to ERPS protocol operation
Handling Suggestion
None.
3.1.7 134257783 CRC error in flash

Alarm Property
l
l
l
l
Alarm Information:CRC error flag,which is appeared when the history alarm or event
CRC error.
1.Represents history alarm; 2.Represents event.
3-4
SJ-20140402111513-008|20140528(R1.0)
System Impact
Data write to flash fail,it will lead to the device's history alarm or event lose.
Probable Cause
Bad block exists in the flash.
Handling Suggestion
Replace RCU/RCMU board.
3.1.8 134317731 Configuraiton file reloaded

Alarm Property
l
l
l
l
Alarm Information:The notification is reported if the configuration file is reloaded.
2.Loading front-end configuration files fails;
3.Synchronizing back-end whole table configuration files fails.
System Impact
This event affects traffic quality because the manual loading of configuration files requires
a reboot of the equipment.
Probable Cause
1. Loading the entire table fails.
2. Loading the database fails when the system starts.
Handling Suggestion
Ensure that the whole table configuration file is complete. If it is not complete, replace it
with a complete one.
3.1.9 134317740 IF and RF changeover

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if the IF board or the Rf unit changeovers.
3-5
SJ-20140402111513-008|20140528(R1.0)
4.IF board and Rf unit switchover fails;
5.IF board and Rf unit switchover succeeds;
6.Rf unit switchover fails;
7.Rf unit switchover succeeds;
System Impact
Traffic may remain unavailable for 300ms and error codes are generated as a result.
Probable Cause
1. The IF board fails.
2. The Rf unit fails.
3. The switchover can be caused by lost or abnormal clock signal from the enclosure,
hard resetting of the board, board power-off, or hardware fault of the board.
Handling Suggestion
1. If the alarm is caused by If unit(RCMU/RMEA), replace it.
2. If the alarm is caused by Rf unit, replace the Rf unit.
3. If the alarm still exists, replace the enclosure.
3.1.10 134317745 ACM change

Alarm Property
l
l
l
l
Alarm Information:The notification is reported if the ACM mode is changed.
None
System Impact
The traffic capacity changes with the adjustment of modulation scheme, but the traffic is
not interrupted.
Probable Cause
The alarm is caused by user configuration if the ACM is not enabled. If the ACM is enabled,
the alarm is caused by the change of link condition.
3-6
SJ-20140402111513-008|20140528(R1.0)
Handling Suggestion
The alarm is reported when user configuration or the change of link condition leads to ACM
change. This is not a fault.
3.1.11 134317746 System time is modified

Alarm Property
l
l
l
l
Alarm Information:The notification is reported if the system time is modified due to
SNTPbased time calibration.
None
System Impact
It does not affect the traffic carried by the board, but may cause incomplete data.
Probable Cause
The system time is modified.
Handling Suggestion
Make sure that the SNTP server time is accurate.
3.1.12 134317747 Clear performance data

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported when the NE's performance date is cleared.
None
System Impact
It does not affect the traffic carried by the board,but may cause incomplete data.
3-7
SJ-20140402111513-008|20140528(R1.0)
Probable Cause
1. The user clears the performance data.
2. The board restarts.
3. The board is unavailable(board is absent or configuration is update or function ID is
changed),and can not report the heartbeat messages between boards normally.
Handling Suggestion
If the board is unavailable,make sure the board is inserted or configured correctly,and
powers on normally.
3.1.13 134317749 Main clock reference source change

Alarm Property
l
l
l
l
Alarm Information:The notification is reported if the main clock reference changes.The
information of the main clock reference reported contains rack NO.shelf NO.slotNO.
And port ID.
None
System Impact
None
Probable Cause
Main clock reference source change.
Handling Suggestion
Check link status of last main Clock reference source if necessary.
3.2 Communication Alarm

3.2.1 134243728 LLDP global enable status changed
Alarm Property
l
l
Alarm Information:The alarm is reported when the LLDP global enable status is
changed.
3-8
SJ-20140402111513-008|20140528(R1.0)
l
l
1. The LLDP global enable status is disabled;
2. The LLDP global enable status is enabled.
System Impact
This alarm does not affect the traffic carried by the board. If LLDP global enable status is
disabled, all ports cannot send the LLDP packet and will not process the received LLDP
packet.
Probable Cause
Change the configuration of LLDP global enable.
Handling Suggestion
3.2.2 134243729 Local management address of LLDP changed

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported when the local management address is
changed.
None
System Impact
Probable Cause
Change Local management address
Handling Suggestion
3-9
SJ-20140402111513-008|20140528(R1.0)
3.2.3 134243730 Neighbor information of LLDP changed

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported when the neighbor information is changed.
1.
2.
3.
4.
5.
A new neighbor is added;

The shutdown packet is received and the neighbor information is deleted;
The neighbor information is changed;
The neighbor information adding fails;
The neighbor information is aging and deleted.
System Impact
Probable Cause
1.
2.
3.
4.
The packet of a new neighbor is received.

The shutdown packet is received,and the neighbor information is deleted.
The neighbor information change packet is received.
The number of neighbor exceeds the maximum limit, and the neighbor adding
operation fails.
5. A neighbor is aging and deleted.
Handling Suggestion
3.2.4 134243780 MEP receive AIS packet

Alarm Property
l
l
l
l
Alarm Information:MEP receive AIS packet with same level and will suppress alarm.
None
3-10
SJ-20140402111513-008|20140528(R1.0)
System Impact
It does not affect the traffic carried by the board
Probable Cause
Lower MD may has defect.
Handling Suggestion
Check if lower MD has alarm.
3.2.5 134243781 MEP receive LCK packet

Alarm Property
l
l
l
l
Alarm Information:MEP receive LCK packet with same level and will suppress alarm.
None
System Impact
It does not affect the traffic carried by the board
Probable Cause
Local MD or lower MD may has administrative lock.
Handling Suggestion
Notify the suppression of alarms in local MD.
3.2.6 134317743 SNCP channel changeover

Alarm Property
l
l
l
l
Alarm Information:The event is reported if hardware occurs interruption when the
master or slave channel changeovers.
None
3-11
SJ-20140402111513-008|20140528(R1.0)
System Impact
The traffic is interrupt during changeover.
Probable Cause
The master or slave channel is unvailable.
Handling Suggestion
Perform active/standby channel changeover manually or forcedly.
3.2.7 134317760 SNCP+ channel changeover

Alarm Property
l
l
l
l
Alarm Information:The event is reported if SNCP+ switch occurs.
None
System Impact
The traffic is interrupt during changeover.
Probable Cause
The master or slave channel is unvailable.
Handling Suggestion
Perform active/standby channel changeover manually or forcedly.
3.3 Processing alarm

3.3.1 134243733 OSPF interface status changed
Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if the OSPF interface status is changed.
3-12
SJ-20140402111513-008|20140528(R1.0)
None
System Impact
None
Probable Cause
The OSPF interface status is changed.
Handling Suggestion
No processing is required.All OSPF interface
Loopback/Down/Waiting/PTP/Backup/DROther/DR.
status
packets
include:
3.3.2 134243734 OSPF virtual interface status changed

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if the OSPF virtual interface status is
changed.
None
System Impact
None
Probable Cause
The OSPF virtual interface status is changed.
Handling Suggestion
No processing is required.All OSPF interface
Loopback/Down/Waiting/PTP/Backup/DROther/DR.
status
packets
include:
3.3.3 134243735 OSPF neighbor status changed

Alarm Property
l
3-13
SJ-20140402111513-008|20140528(R1.0)
l
l
l
Alarm Information:The alarm is reported if the OSPF interface neighbor status is

changed.
None
System Impact
None
Probable Cause
The status of an OSPF interface neighbor is changed.
Handling Suggestion
No processing is required.All OSPF interface neighbor status packets include:
Down/Init/2Way/ExStart/Exchange/Load/Full.
3.3.4 134243736 OSPF virtual neighbor status changed

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if the OSPF virtual interface neighbor status
is changed.
None
System Impact
None
Probable Cause
The status of an OSPF virtual interface neighbor is changed.
Handling Suggestion
No processing is required.All OSPF interface neighbor status packets include:
Down/Init/2Way/ExStart/Exchange/Load/Full.
3-14
SJ-20140402111513-008|20140528(R1.0)
3.3.5 134243740 OSPF interface receiving incorrect packet

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if OSPF interface receives incorrect packet,
which cannot be parsed.
None
System Impact
This alarm may cause LSDB synchronization failure.
Probable Cause
The contents of the DD, LSR, LSAck, and LSU packets are incorrect.
Handling Suggestion
3.3.6 134243741 OSPF virtual link interface receive wrong packet

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if OSPF virtual interface receives incorrect
packet, which cannot be parsed.
None
System Impact
This alarm may cause LSDB synchronization failure on virtual link.
Probable Cause
The contents of the DD, LSR, LSAck, and LSU packets are incorrect
3-15
SJ-20140402111513-008|20140528(R1.0)
Handling Suggestion
3.3.7 134243742 OSPF interface receiving incorrect LSR packet

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if OSPF interface receives incorrect LSR
packet from the neighbor.
None
System Impact
This alarm may cause LSDB resynchronization.
Probable Cause
The requested LSA does not exist or the interface does not support the requested LSA
type.
Handling Suggestion
3.3.8 134243743 OSPF receive DD pkt with wrong seq number

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if OSPF interface receives DD packet that
contains incorrect sequence number from the neighbor.
None
System Impact
This alarm may cause LSDB resynchronization.
3-16
SJ-20140402111513-008|20140528(R1.0)
Probable Cause
The active/standby neigotiation flag or the sequence number is incorrect during DD
exchange.
Handling Suggestion
3.3.9 134243744 Receive Hello Packet without local router

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported when the Hello packet received at the
interface where OSPF is implemented does not include this router.
None
System Impact
The state machine returns to the initial state.
Probable Cause
The link status is changed.
Handling Suggestion
Check the link status.
3.3.10 134243745 Timeout for receiving OSPF hello packet

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported when it is timeout for receiving the Hello
packet at the interface where OSPF is implemented.
None
3-17
SJ-20140402111513-008|20140528(R1.0)
System Impact
The interface to the neighbor is disabled.
Probable Cause
The neighbor makes no response.
Handling Suggestion
Check the neighbor status.
3.3.11 134243746 OSPF interface disabled by administrator

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if OSPF interface is disabled by administrator.
None
System Impact
The neighbor status is changed, and the route may be recalculated.
Probable Cause
The OSPF interface is disabled by administrator in EMS or LMT.
Handling Suggestion
Check whether the interface configuration is enabled.
3.3.12 134243747 OSPF interface disabled physically

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if OSPF interface is physically disabled, and
the network media might be disconnected.
None
3-18
SJ-20140402111513-008|20140528(R1.0)
System Impact
The neighbor status is changed, and the route may be recalculated.
Probable Cause
The network media is disconnected.
Handling Suggestion
Check the pyhsical connections.
3.3.13 134243748 Interface's neighbor changed

Alarm Property
l
l
l
l
Alarm Information:OSPF interface's neighbor state changed.
None
System Impact
Adjacency will be re-build.
Probable Cause
Neighbor IP or RouterID changed, or adjcency releationship is lost.
Handling Suggestion
Check new configuration for neighbor's IP or RouterID.
3.3.14 134243762 SG add failed for parameter error

Alarm Property
l
l
l
l
Alarm Information:The notification is reported when SG para error in add operation.
None
3-19
SJ-20140402111513-008|20140528(R1.0)
System Impact
Lacp can not run normal when config sg
Probable Cause
Add a SG failed .
Handling Suggestion
Notify users that sg add failed for para error.
3.3.15 134243763 The port failing to be aggregated into a LAG

Alarm Property
l
l
l
l
Alarm Information:The notification is reported when the port fails to be aggregated into
a LAG.
None
System Impact
Probable Cause
The port fails to be aggregated into a LAG.
Handling Suggestion
Notify users that the port fails to be aggregated into a LAG.
3.3.16 134243764 The port quitting a LAG due to exception

Alarm Property
l
l
l
l
Alarm Information:The notification is reported when the port quits from a LAG due to
some exception.
3-20
SJ-20140402111513-008|20140528(R1.0)
None
System Impact
Probable Cause
The port quits from a LAG due to some exception.
Handling Suggestion
Notify users that the port quits from a LAG due to some exception.
3.3.17 134317735 Rf unit firmware upgraded

Alarm Property
l
l
l
l
Alarm Information:The alarm is reported if the Rf unit software version is upgraded
through local IDU,FTP mode or Rf unit patch upgrade mode.
0.Local upgrading fails;
1. Local upgrading succeeds;
2. FTP upgrading fails;
3. FTP upgrading succeeds;
4. Rf unit patch upgrading fails;
5. Rf unit patch upgrading succeeds.
System Impact
Upgrading the Rf unit firmware manually leads to this event. The event does not affect any
traffic.
Probable Cause
1. For upgrade through IDU or Rf unit patch, the alarm may be caused by the incomplete
or incorrect software files.
2. For upgrade in FTP mode, the alarm may be caused by incorrect setting of the FTP
server or FTP software or by the incomplete or incorrect software files.
Handling Suggestion
It is an event for notifying users to upgrade the Rf unit firmware.
3-21
SJ-20140402111513-008|20140528(R1.0)
1. For upgrade failure through IDU or Rf unit patch, ensure that the Rf unit software files
in IDU flash memory or patch packet correct and complete.
2. For upgrade failure in FTP mode, ensure that
(1) The IP address of the FTP server is set correctly.
(2) The user name and password of the FTP software are set correctly.
(3) The new software files are correct and complete.
3.4 QoS Alarm

3.4.1 134243773 EFM remote link event
Alarm Property
l
l
l
l
Alarm Information:The notification is reported if EFM receives a link event from the
remote end.
1.
2.
3.
4.
Errored
Errored
Errored
Errored
Symbol Period Event;

Frame Event;
Frame Period Event;
Frame Seconds Summary Event;
System Impact
The link performance is affected.
Probable Cause
1. The number of errored symbols of the physical layer within the unit time exceeds the
preset threshold.
2. The number of errored frames of the MAC layer within the unit time exceeds the preset
threshold.
3. The number of errored frames of MAC layer within the unit frame amount exceeds the
preset threshold.
4. The number of errored frame seconds of the MAC layer within the unit time exceeds
the preset threshold.
Handling Suggestion
Check the link performance.
3-22
SJ-20140402111513-008|20140528(R1.0)
3.4.2 134243774 EFM loopback indication

Alarm Property
l
l
l
l
Alarm Information:The notification is reported if EFM performs loopback indication.
1. Starting loopback fails;
2. Stopping loopback fails.
System Impact
This notification indicates the loopback operation status.
Probable Cause
The loopback test is started manually at the local end or the remote end.
Handling Suggestion
None.
3.4.3 134243777 Local Discovery process reset

Alarm Property
l
l
l
l
Alarm Information:The notification is reported if EFM restarts the discovery process.
None
System Impact
EFM state is abnormal.
Probable Cause
EFM restarts the discovery process.
Handling Suggestion
None.
3-23
SJ-20140402111513-008|20140528(R1.0)
3.5 Environment Alarm

3.5.1 134317750 IDU Over-temperature protection
Alarm Property
l
l
l
l
Alarm Information:The IDU device temperature is too high, automatically cold restart
in order to protect the IDU device.
None
System Impact
IDU can not work normly, restart in order to protect the device.
Probable Cause
The temperature of the IDU work environment is too high.
Handling Suggestion
Cool down the temperature of the IDU work environment.
3-24
SJ-20140402111513-008|20140528(R1.0)

SJ-20140402111513-008-ZXMW NR8120 (V2.03.03) Alarm and Notification Handling Reference - 606555 PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

SJ-20140402111513-008-ZXMW NR8120 (V2.03.03) Alarm and Notification Handling Reference - 606555 PDF

Hochgeladen von

Copyright:

Verfügbare Formate

ZXMW NR8120

Digital Microwave Transmission System

Alarm and Notification Handling Reference

Additionally, the contents of this document are protected by

contractual confidentiality obligations.

Serial Number: SJ-20140402111513-008

ZTE Proprietary and Confidential

ZTE Proprietary and Confidential

2.2.3 9001 AC input switch off ........................................................................ 2-19

ZTE Proprietary and Confidential

2.2.40 134218778 CPU overload .................................................................... 2-46

ZTE Proprietary and Confidential

2.3.4 6223 Firmware does not take effect ........................................................ 2-71

ZTE Proprietary and Confidential

2.4.31 134243771 EFM discovery process failure ...........................................2-100

Chapter 3 Notification ................................................................................ 3-1

ZTE Proprietary and Confidential

ZTE Proprietary and Confidential

About This Manual

What Is in This Manual

Gives an overview of NR8120 alarms and notifications.

Describes the alarms in terms of alarm properties, probable causes,

Describes the notifications in terms of notification properties, probable

ZTE Proprietary and Confidential

This page intentionally left blank.

ZTE Proprietary and Confidential

Uniquely identifies an alarm or an notification.

ZTE Proprietary and Confidential

ZXMW NR8120 Alarm and Notification Handling Reference

There are four alarm/notification severity levels, which are indicated in

Critical: indicates a fault that causes failures of system operations or

Major: indicates a fault that seriously impacts proper system operations or

Minor: indicates a fault that slightly influences proper system operations or

Warning: indicates a fault that has a potential or gradual impact on proper

Based on the triggering condition and system impact, alarms/notification can

Equipment alarm: related with equipment hardware faults.

Communication alarm: related with information transmission faults (ITU-T

Processing error alarm: related with software or processing faults (defined

Environmental alarm: related with the environment where the equipment is

QoS alarm: related with equipment operation performance or indexes.

Provides probable alarm/notification causes to help users troubleshoot, find

Provides the consequence of each alarm/notification and the impact on the

ZTE Proprietary and Confidential

Provides the troubleshooting steps and suggestions.

If fault cannot be removed, contact the local ZTE office.

ZTE Proprietary and Confidential

ZXMW NR8120 Alarm and Notification Handling Reference

This page intentionally left blank.

ZTE Proprietary and Confidential

2.1 Environment Alarm

Board Status:The power board may be faulty.

ZTE Proprietary and Confidential

ZXMW NR8120 Alarm and Notification Handling Reference

2.1.2 4001 Outdoor temperature alarm

Dustproof net is blocked.

ZTE Proprietary and Confidential

2.1.3 4011 Outdoor access-control alarm

2.1.4 4012 Outdoor moisture alarm

ZTE Proprietary and Confidential

ZXMW NR8120 Alarm and Notification Handling Reference

2.1.5 4013 Outdoor smoke alarm

ZTE Proprietary and Confidential

2.1.6 4016 Outdoor lightning protection module alarm