eNodeB Alarm Handling Reference

NetNumen U31(TDD LTE)
Unified Management System

eNodeB Alarm Handling Reference
Version: V2.00.041
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2012 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 ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No.
R1.1
R1.0
Serial Number: SJ-20120322151347-005
Publishing Date: 2012-04-15(R1.1)
SJ-20120322151347-005|2012-04-15(R1.1)
Contents
About This Manual
Chapter 1 Overview
Chapter 2 Communication Alarm
2.1 198092211 PLL unlocked alarm
2.2 198092230 SCTP association is interrupted
2.3 198092231 PPP Link is broken
2.4 198092232 HDLC Link is broken
2.5 198092233 SSCOP Link is broken
2.6 198092240 1588 clock link fault
2.7 198092313 PPP Link Loop
2.8 198092351 Local LMT's Force Connect
2.9 198092361 IMA group has fault
2.10 198092362 IMA/TC link has fault
2.11 198092367 802.1x authentication failed
2.12 198092369 LCK alarm
2.13 198092382 Configuration parameter of OAM Channel is wrong
2.14 198092399 BFD connection broken
2.15 198092402 TCP connection is broken
2.16 198092411 BITS clock fault
2.17 198092427 The number of SCTP streams is inconsistent
2.18 198092428 SCTP path is interrupted
2.19 198092431 The strength of received optical signal is abnormal
2.20 198092445 RRU inner GNSS (clock reference source) link alarm
2.21 198092446 RRU inner GNSS (clock reference source) link unavailable
2.22 198094825 Optical link which bearing S1/X2 signal breakdown error
2.23 198096564 RRU and outer LNA communication link broke
2.24 198092210 PLL reference clock lost alarm
Chapter 3 Equipment Alarm
3.1 198100270 Optical signals transmitted from BBU to RRU carry wrong clock
information
3.2 198100271 Unlocked local oscillator alarm of RRU
3.3 198100272 RRU inside clock unlocked
3.4 198100273 Downlink channel fault alarm
SJ-20120322151347-005|2012-04-15(R1.1)
3.12
3.13
3.14
3.15
3.16
3.17
3.18
3.19
3.20
3.21
3.22
3.23
3.24
3.25
3.26
3.27
3.28
3.29
3.30
3.31
3.32
3.33
3.34
3.35
3.36
3.37
3.38
3.39
3.40
3.41
II
SJ-20120322151347-005|2012-04-15(R1.1)
3.54198092
3.55198092
3.56198092
3.57198092
3.58198092
3.59198092
3.60198092
3.61198092
3.62198092
3.63198092
3.64198092
3.65198092
3.66198092
3.67198092
3.68198092
3.69198092
3.70198092
3.71198092
3.72198092
3.73198092
3.74198092
3.75198092
3.76198092
3.77198092
3.78198092
SJ-20120322151347-005|2012-04-15(R1.1)
3.79
3.80
3.81
3.82
3.83
3.84
3.85
3.86
3.87
3.88
3.89
3.90
3.91
3.92
3.93
3.94
3.95
3.96
3.97
3.98
3.99
3.106 198092277 Clock module fault

3.107 198092278 Abnormal power
SJ-20120322151347-005|2012-04-15(R1.1)
3.116 198092287 The channel downlink frame is unlocked

3.117 198092288 The PLL clock is unlocked
3.118 198092289 The optical/electric module is not in the position of optical port
3.119 198092290 The uplink optical/electric link is interrupted
3.120 198092291 The input frame synchronous signal is wrong
3.121 198092292 An alarm is given when an optical fiber is wrongly connected
3.122 198092293 The Rx optical port at RRU has no light signal
3.123 198092294 The frame transferred over Rx port of RRU is unlocked
3.124 198092295 RRU power-cut alarm
3.125 198092298 MMC Fault
3.126 198092311 IQ reported is failed
3.127 198092317 ACOM major alarm
3.128 198092318 ACOM minor alarm
3.129 198092319 ACOM hardware fault
3.130 198092320 ACOM communication link is interrupted
3.131 198092321 ACOM software fault
3.132 198092322 AISG EEPROM error
3.133 198092323 AISG flash erase error
3.134 198092324 AISG flash error
3.135 198092325 AISG other hardware error
3.136 198092326 AISG other software error
3.137 198092327 AISG RAM error
3.138 198092328 AISG UART error
3.139 198092330 ATMA major alarm
3.140 198092331 ATMA minor alarm
3.141 198092332 Failed to set gain
3.142 198092333 ATMA hardware fault
3.143 198092334 ATMA communication link is interrupted
3.144 198092335 ATMA software fault
3.145 198092336 Board configuration parameter error
3.146 198092337 RET motor fault
3.147 198092339 RET hardware fault
3.148 198092340 RET motor can't adjust
3.149 198092341 RET motor don't respond the adjusting command
3.150 198092342 RET communication link is interrupted
3.151 198092343 RET don't calibrated
3.152 198092344 RET data don't scaled
V
SJ-20120322151347-005|2012-04-15(R1.1)
3.153 198092345 RET position lost

3.154 198092346 RET software fault
3.155 198092352 Unmatched link mode at peer-end electrical port of Ethernet
3.156 198092353 Configuration is failed
3.157 198092363 Faulty main power alarm
3.158 198092364 Calibrate Fail
3.159 198092365 Low Power Exception
3.160 198092374 UCI optical module of optical port is out of position
3.161 198092375 UCI optical module of optical port has no light signal
3.162 198092376 UCI receiver frame at optical port is unlocked
3.163 198092377 UCI fiber delay adjust is failed
3.164 198092378 Board PLL is unlocked
3.165 198092379 PA over power alarm
3.166 198092383 Distributing IQ resource is failed
3.167 198092384 It is failed to configurate IQ
3.168 198092385 It is failed to configurate optical port speed
3.169 198092386 It is failed to configurate TDM port speed
3.170 198092387 It is failed to configurate RRU device delay parameter
3.171 198092388 It is failed to configurate power supply
3.172 198092393 UES ethernet semiduplex alarm
3.173 198092394 Several rectifiers faulty
3.174 198092400 Board smart powered-down
3.175 198092401 E1 link self-loop
3.176 198092409 GNSS antenna feeder alarm
3.177 198092415 The built-in-type GNSS receiver has an alarm
3.178 198092416 The built-in-type GNSS antenna has a feeder cable alarm
3.179 198092418 The external-panel-type GNSS receiver has an alarm
3.180 198092419 The external-panel-type GNSS antenna has a feeder cable
alarm
3.181 198092421 The external-panel-type GNSS receiver has an alarm, indicating
its foreground working mode is inconsistent with background
3.182 198092422 The external-backplane-type GNSS receiver has an alarm
3.183 198092423 The external-backplane-type GNSS antenna has a feeder cable
alarm
3.184 198092425 The external-backplane-type GNSS receiver has an alarm,
indicating its foreground working mode is inconsistent with background
3.185 198092426 GNSS cascading clock has an alarm
3.186 198092433 RRU network interrupted alarm
VI
SJ-20120322151347-005|2012-04-15(R1.1)
3.187 198092434 Clock line abnormal connection in stack mode

3.188 198092435 Inter-frame Ethernet link broken in stack mode
3.189 198092436 Loss of clock synchronization at slave frame
3.190 198092437 RU radio frequency group unavailable
3.191 198092438 Device in low temperature
3.192 198092439 Uplink transport port of a base station operates in a different
mode from configured one
3.193 198092447 Unbalanced AC phase voltage of built-in power
3.194 198092448 High AC phase current of built-in power
3.195 198092449 Missing AC phase voltage of built-in power
3.196 198092450 Battery low-voltage cut-off of built-in power
3.197 198092451 Broken LLVD1 branch E of built-in power
3.198 198092452 Broken LLVD1 branch of built-in power
3.199 198092453 Broken LLVD2 branch E of built-in power
3.200 198092454 Broken battery cut-off branch E of built-in power
3.201 198092455 Broken battery cut-off branch of built-in power
3.202 198092456 Abnormal battery current of built-in power
3.203 198092457 Abnormal CAN bus of built-in power
3.204 198092458 Abnormal battery of built-in power
3.205 198092459 Abnormal input dry contact of built-in power
3.206 198092460 High-temperature cut-off of built-in power
3.207 198092461 BBU inter-subrack frame synchronization failure alarm
3.208 198092550 User-defined dry contact alarm 1
VII
SJ-20120322151347-005|2012-04-15(R1.1)
3.224 198092566 User-defined dry contact alarm
3.258 198094800 SRIO Communication Abnormal
3.259 198094828 The board is unavailable
3.260 198094829 eBBU synchronization abnormal
SJ-20120322151347-005|2012-04-15(R1.1)
3.261 198096550 Alarm of fiber configuration

3.262 198096551 RRU unconfigured
3.263 198096552 Difference of fiber time delay of two RRUs in same sector
exceeded system limit
3.264 198096553 RRU Type is not consistent with configuration type
3.265 198096554 Failure of optical decoding in BBU
3.266 198096555 Failure of optical decoding in RRU
3.267 198096556 IQ link input loses lock
3.268 198096558 Downlink baseband power abnormal
3.269 198096558 Guide frequency that BBU sends to RRU is too high or too low
3.270 198096559 RRU adjust channel or adjust cable fault
3.271 198096560 Master and slave monitor link alarm
3.272 198096561 Coherence alarm of antenna channel swing and phase
3.273 198096562 RRU self check failed when power on
3.274 198096563 RRU device alarm
3.275 198096565 Configuration parameter of RRU external device not consistent
with real parameter
3.276 198096568 RRU used power module is too hot
3.277 198096569 RRU offline parameter check failure
3.278 198098431 Abnormal current alarm at NSBT port
3.279 198098432 AISG/NSBT port turn-off alarm due to over current
3.280 198098434 Abnormal transmission power at antenna port
3.281 198098435 Closed-loop power control adjustment exceeding normal
range
3.282 198098436 Failure in configuring power level
Chapter 4 Environment Alarm
4.1 198092429 Board powered-down alarm because of high temperature
4.2 198092462 Differential pressure alarm
4.3 198092037 MP voltage abnormal
4.4 198092038 PP voltage abnormal
4.5 198092039 Over current of MP
4.6 198092040 Over current of PP
4.7 198092041 Fan failure
4.8 198092042 Abnormal temperature at air intake
4.9 198092043 Abnormal temperature at air outlet
4.10 198092044 Door control alarm
4.11 198092045 Flooding alarm
4.12 198092046 Smog alarm
IX
SJ-20120322151347-005|2012-04-15(R1.1)
4.13
4.14
4.15
4.16
4.17
4.18
4.19
4.20
4.21
4.22
4.23
4.24
4.25
4.26
4.27
4.28
4.29
4.30
4.31
4.32
4.33
4.34
4.35
Chapter 5 Processing Alarm
board
SJ-20120322151347-005|2012-04-15(R1.1)
5.13198092
5.14198092
5.15198092
5.16198092
5.17198092
5.18198092
5.19198092
5.20198092
5.21198092
5.22198092
5.23198092
5.24198092
5.25198092
5.26198092
5.27198092
5.28198092
5.29198092
5.30198092
5.31198092
5.32198092
5.33198092
5.34198092
5.35198092
5.36198092
5.37198092
5.38198092
5.39198092
5.40 198094811 Cell Setup Failure
5.41 198094812 Cell Reconfiguration Failure
5.42 198094813 Parament Configuration Error
Chapter 6 QoS Alarm
alarm
searching alarm
6.5 198094826 PCI conflict alarm
SJ-20120322151347-005|2012-04-15(R1.1)
6.9 198092370 AIS alarm
Chapter 7 Notification
7.5 198092059 Alarm Storm

7.6 198092061 Module reset
7.12
7.13
7.14
7.15
7.16
7.17
7.18
7.19
7.20
7.21
7.22
7.23
7.24
7.25
7.26
7.27
7.28
7.29
7.30
hours
SJ-20120322151347-005|2012-04-15(R1.1)
7.31 198092035 E1 link bit error has been detected in the past 24 hours
Glossary
XIII
SJ-20120322151347-005|2012-04-15(R1.1)
XIV
SJ-20120322151347-005|2012-04-15(R1.1)
About This Manual

Purpose
This manual introduces the alarms and notifications that might occur during the product
installation, operation and maintenance.
Intended Audience
This manual is intended for:

l Base station deploy engineers
l Maintenance engineers
l Network management engineers
What Is in This Manual
This manual contains the following chapters:
Chapter
Chapter 1, Overview
Chapter 2, Communication Alarm
Chapter 3, Equipment Alarm
Chapter 4, Environment Alarm

Chapter 5, Processing Alarm
Chapter 6, QoS Alarm
Chapter 7, Notification
probable cause, system impact, and handling suggestion
SJ-20120322151347-005|2012-04-15(R1.1)
II
SJ-20120322151347-005|2012-04-15(R1.1)
Chapter
Overview1
Fault management is responsible for collecting information of failures and events that occur
during system operation or service processing.
The information, in the form of alarm or notification, is stored in database or displayed

on real-time basis via a user-oriented fault monitoring platform. Means such as
visual-interface monitor or history information query can be used to view current or
historical system operation and service processing status. Fault management enables
maintenance personnel to troubleshoot and take preventive measures to remove potential
fault and restore system and services as early as possible.
Fault is displayed in the form of alarm or notification.
Alarm
The fault that persists during system operation and affects system reliability and normal
services is referred to as an alarm. Alarm usually lasts until fault removal.
Due to its possible impact on normal system operation, alarm requires timely
troubleshooting in which alarm cause is identified, and the fault is located and handled.
Notification
Notification refers to the non-repeated/instantaneous fault or event that occurs during

system operation. Examples include board reset, signaling overload, etc.
Notification is mostly caused by sudden environment change or other accidental factors.
No special handling is required for the notification, which can be automatically removed by
the system. Only the notification that occurs persistently requires troubleshooting.
Alarm/Notification Information Structure

Alarm is classified into these types below according to alarm trigger condition and its
system impact:
l Equipment alarm: related with device hardware.

l Communication alarm: related with information transmission (ITU-T Recommendation
X.733).
l Processing alarm: related with software or process fault (ITU-T Recommendation
X.733).
l Environment alarm: related with the environment where the equipment is located
(ITU-T Recommendation X.733).
l QoS alarm: related with quality of service.
Each alarm contains the following contents:
1-1
SJ-20120322151347-005|2012-04-15(R1.1)
NetNumen U31(TDD LTE) eNodeB Alarm Handling Reference
l
l
There are four alarm levels, which are indicated in descending order of severity as
Critical, Major, Minor, and Normal.
à Critical alarm causes system breakdown and service interruption. It requires

immediate troubleshooting.
à Major alarm significantly affects system operation or weakens network service

capability. It requires troubleshooting as soon as possible.
à Minor alarm affects system operation and network service capability in a

non-significant way. It requires timely troubleshooting so as to avoid severity
escalation.
à Warning alarm poses a potential hazard to system operation and network service
capability. It requires troubleshooting at an appropriate time so as to avoid
severity escalation.
The degree of impact as described in the definition of alarm severity refers to the
impact of a single index, such as reliability and security. Once the impact on any
of the index reaches the specified threshold, the severity level of the alarm can be
roughly determined. If an alarm has an impact on multiple indices, alarm severity
should be escalated accordingly.
Note:
à Alarm severity can be modified in NetNumen U31 if necessary.

à Generally speaking, the default alarm severity is reasonably set. Users should
think twice before making any modification.
l System Impact
System impact refers to the impact that the alarm/notification incurs on system or
services.
l Probable Cause
Probable alarm/notification causes are enumerated to help users troubleshoot, find

preventive measures, and restore the system to normal state in a timely manner.
l Handling Suggestion
1-2
SJ-20120322151347-005|2012-04-15(R1.1)
Chapter 1 Overview
Troubleshooting measures and suggestions are provided. Pay attention to the

following tips when handling alarms/notifications.
à After recording the fault phenomenon, operation and maintenance personnel may
handle the fault step by step as described in the Solution of this manual. If the
fault is removed at any handling step, terminate the handling process. If the fault
is not removed, go ahead to the next handling step.
à If the fault cannot be removed, contact the local ZTE office as soon as possible.
1-3
SJ-20120322151347-005|2012-04-15(R1.1)
This page intentionally left blank.
1-4
SJ-20120322151347-005|2012-04-15(R1.1)
Chapter 2
Communication Alarm
Table of Contents
198092211 PLL unlocked alarm
198092231 PPP Link is broken

198092232 HDLC Link is broken
198092233 SSCOP Link is broken
198092240 1588 clock link fault
198092313 PPP Link Loop
198092351 Local LMT's Force Connect
198092361 IMA group has fault
198092362 IMA/TC link has fault
198092367 802.1x authentication failed
198092369 LCK alarm
198092399 BFD connection broken

198092402 TCP connection is broken
198092411 BITS clock fault
198092428 SCTP path is interrupted
2.1 198092211 PLL unlocked alarm

Detailed Information
Severity
System Impact
Probable Cause
2-1
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
using SYNCE function, this alarm has no impact on the board.
2. If SYNCE mode is supportable, this alarm requires replacing the

board.
2.2
Severity
System Impact
Probable Cause
Handling Suggestion
1) Check if there is FE port or PPP related alarm

Y=>exist, go to "2) deal with FE port or PPP related alarm".
N=>not exist, go to "2. Check if configuration of SCTP parameter is
correct"
2) Deal with FE port or PPP related alarm
Remove alarm according to disposal suggestions of FE port or PPP

related alarm. Judge if current alarm is recovered
Y=>alarm is recovered, close alarm dispose.
N=>alarm is not recovered, go to "2.Check if configuration of SCTP

coupling parameter is correct"
2. Check if configuration of SCTP coupling parameter is correct

1) Check configuration of SCTP coupling parameter after operation
and maintenance.
2) Check if remote address and port number of SCTP coupling is same

with local address and port number, FE port/PPP chose is same with
configuration of local.
Y=>Consistent, wait to build link with partner port go to "3) wait alarm
recover".
N=>Inconsistent, go to "3.Reconfiguration SCTP coupling.".

3) Wait alarm recover
Wait for a while, Determine whether the alarm is recovered.

N=>alarm is not recovered, please contact ZTE.
2-2
SJ-20120322151347-005|2012-04-15(R1.1)
3. Reconfiguration SCTP
1) Delete the error coupling in configuration window of SCTP coupling.

2) Add SCTP coupling in configuration window of SCTP coupling,
attribute value should be consistent with the right side. Check if alarm
is recovered after configuration.
Y=>alarm is recovered, close alarm dispose

2.3
Severity
System Impact
Probable Cause
Handling Suggestion
error alarm.
Y=>exist, go to "2. Deal with error alarm of E1/STM1 link".

N=>not exist, jump "3. Reset board".
2. Deal with error alarm of E1/STM1 link.
Remove the alarm according to disposal suggestions of E1/STM1 error

alarm. Determine whether the alarm is recovered.
Y=>alarm is recovered, close alarm disposal.

N=>alarm is not recovered, go to "3. Reset board".
3. Reset board
Reset board, wait 2 minutes, Determine whether the alarm is recovered.

N=>alarm is not recovered, go to "4. Replace board".

4. Replace board
Replace error board, wait 2 minutes, determine whether the alarm is

recovered.

2.4 198092232 HDLC Link is broken.

Severity
System Impact
SJ-20120322151347-005|2012-04-15(R1.1)
Probable Cause
Handling Suggestion
error alarm
Y=>exist, go to "2. Deal with error alarm of E1/STM1 link"

N=>not exist, go to "3. Reset board"
2. Deal with error alarm of E1/STM1 link
Remove the alarm according to disposal suggestions of E1/STM1 error

alarm. Determine whether the alarm is recovered
Y=>alarm is recovered, close alarm disposal

N=>alarm is not recovered, go to "3. Reset board"
3. Reset board
Reset board, wait 2 minutes, Determine whether the alarm is recovered

Y=>alarm is recovered, close alarm disposal
N=>alarm is not recovered, go to "4. Replace board"

4. Replace board
Replace error board, wait 2 minutes, determine whether the alarm is

recovered

2.5 198092233 SSCOP Link is broken.

Severity
System Impact
Probable Cause
Handling Suggestion
management interface, and if so, process in accordance with the
proposal suggestions of relevant alarms.
2. In configuration management interface, see base station side port

number, VPI, VCI, PVC bandwidth, which are required consistent with
the RNC-side configuration.
3. Reconfigure the PVC link.
(1) Remove the fault PVC link in the configuration management

interface.
(2) Add PVC link in the configuration management interface .
2-4
SJ-20120322151347-005|2012-04-15(R1.1)
4. Base station side use physical self-Link, which make base station
side of E1/T1 lines to from a ring , check whether the base station side
SSCOP alarm can recover. If the alarm cannot be restored, reset or
replace the board.
5. RNC side use physical self-Link, which make base station side
of E1/T1 lines to from a ring, check whether the base station side
SSCOP alarm can recover. If the alarm cannot be restored, then the
transmission line fault, check the connection and make sure the line is
normally connected.
6. Inform RNC to check transmission side of RNC.
2.6 198092240 1588 clock link fault

(1) The configured 1588 clock link has high packet loss ratio, exceeding
a threshold.
(2) When the standard Announce message is enabled, 1588 master

clock is abnormal and cannot be traced.
Severity
System Impact
Probable Cause
Handling Suggestion
2. Check whether the configuration parameters, related to transmission

(e.g.IP)and clock, are correct.
3. Check whether the corresponding master link has an alarm.
2.7 198092313 PPP Link Loop.

Severity
System Impact
Probable Cause
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
1) If the PPP is exist in E1/STM1/FE, check if there is a circle in

E1/STM1/FE links corresponds to the PPP.
Y=> exist, Cancel link loopback.
N=> not exist, no other treatment.
2.8 198092351 Local LMT's Force Connect

Severity
System Impact
Probable Cause
Handling Suggestion
2.9
Severity
System Impact
Board operation is normal.

2. Service Impact:
This IMA group is out of service, and the services loaded by this IMA
group are interrupted.
Probable Cause
2. E1/T1 cable connection has fault.
3. Base station or RNC configuration has fault.
Handling Suggestion
alarm is existed, Perform the recommended solution to process the

possible alarms.
Related Alarms:
Relay circuit has fault.

IMA/TC link has fault.
2. Check whether the local interfacing board has clock associated

alarms. If alarm is existed, Perform the recommended solution to
process the possible alarms.
Related Alarms:
Clock reference source is degraded.
2-6
SJ-20120322151347-005|2012-04-15(R1.1)
Clock reference source is lost.
2.10
Severity
System Impact
Probable Cause
Handling Suggestion
TC mode is configured, please check TC slot configuration for base

station and RNC. If the configuration is inconsistent, please correct it. If
IMA mode is configured, please check RNC's configuration, Such as
whether this E1/T1 link belong to IMA group or whether this E1/T1 link
have the same scrambling parameter the same as configuration for
base station. If RNC's configuration is wrong, please correct it.
2. Check relay transport equipment. Conduct loopback test at each
transport network node. During the loopback test, this link shouldn't
report any alarm like "E1/T1 link signal lost", "Relay circuit fault" or
"high BER of relay circuit".
2.11 198092367 802.1x authentication failed
Severity
System Impact
Probable Cause
Handling Suggestion
normal.
2. Please check whether the user identity and user password is

matched in dot1x configuration.
2-7
SJ-20120322151347-005|2012-04-15(R1.1)
2.12 198092369 LCK alarm

Severity
System Impact
Probable Cause
Handling Suggestion
Channel is wrong.
Severity
System Impact

2. Service Impact:
Only the whole table configuration is permitted by the system. Other

services are unavailable.
Probable Cause
data.
Handling Suggestion
OMM parameter.
Severity
System Impact
Probable Cause
2.BFD parameters are wrongly configured at local end or peer end.

3.It is failed to communicate with peer end at bottom layer.
4.Single board is faulty.
2-8
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
1) Check whether FE port exists.

Y=> Yes, go to "2) Handle FE port"
N=> No, go to "2. Check whether BFD parameters are correctly

configured."
2) Handle FE port
Follow the corresponding suggestion to handle the FE port problem.

Check whether the alarm is recovered.
Y=> Yes, end alarm process.
N=> No, go to "2. Check whether BFD parameters are correctly

configured."
2. Check whether BFD parameters are correctly configured.

1) Check BFD configuration parameters from LMT.
2) Check whether BFD remote address and port ID are the same as
local address and port ID configured at peer end, whether FE port
selection is the same as local configuration.
Y=> Yes, wait for a moment. The BFD connection setup to be initiated
on time. Then go to "3) Wait for alarm recovery."
N=> No, fo to "3. Re-configure BFD connection."

3) Wait for alarm recovery
Wait for a moment, check whether the alarm is recovered.

N=> No, Please Contact ZTE.
3. Re-configure BFD connection
1) Delete the faulty connection in the BFD Connection Configuration

interface.
2) Add BFD connection in the BFD Connection Configuration interface.

The attribute value must be the same as peer end. After configuration,
check whether the alarm is recovered.

N=> No, Please Contact ZTE.
2.15 198092402 TCP connection is broken.

Severity
System Impact
SJ-20120322151347-005|2012-04-15(R1.1)
Probable Cause
4. The board is fault.

Handling Suggestion
1) Check if there is FE port or PPP related alarm

Y=>exist, go to "2) deal with FE port or PPP related alarm".
N=>not exist, go to "2. Check if configuration of TCP parameter is
correct"
2) Deal with FE port or PPP related alarm
Remove alarm according to disposal suggestions of FE port or PPP

related alarm. Judge if current alarm is recovered
N=>alarm is not recovered, go to "2.Check if configuration of TCP

connection parameter is correct"
2. Check if configuration of TCP connection parameter is correct

1) Check configuration of TCP connection parameter after operation
and maintenance.
2) Check if remote address and port number of TCP connection is

same with local address and port number, FE port/PPP chose is same
with local configuration.
Y=>Consistent, wait to build link with partner port, go to "3) wait alarm
recover".
N=>Inconsistent, jump "3. Reconfiguration TCP connection.".

3) Wait alarm recover
Wait for a while, Determine whether the alarm is recovered.

N=>alarm is not recovered, please contact ZTE
3. Reconfigurate TCP connection
1) Delete the error connection in configuration management interface

of TCP connection.
2) Add TCP connection in configuration management interface of TCP

connection, attribute value should be consistent with the right side.
Check if alarm is recovered after configuration.
Y=>alarm is recovered, close alarm dispose

N=>alarm is not recovered, please contact ZTE
2.16 198092411 BITS clock fault

Severity
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
Work normally
2. Impact on Services:
System clock works in free oscillation mode, this may cause the
following impacts:
(1). Impact on Iub interface: If Iub interface adopts E1, periodic slip
code may happen at Iub interface; if Iub interface adopts FE, there is
no impact.
(2). Impact on inter base station soft handover: If this alarm doesn't
disappear for a long time, base station clock accuracy may not reach
3GPP standard. This will cause lower soft handover ratio.
Probable Cause
2. External reference source and cable are faulty.
3. The quality of clock reference source is poor.
4. The board is faulty.
Handling Suggestion
2. Check Whether external reference source is normal, whether the

external device of clock reference source stays in locked state.
3. Check whether the clock of synchronization network is normal,
whether external transport device has correct connection and
configuration.
4. Re-connect cables.
5. Inform transport engineers to check whether external transport

device is abnormal.
6. Replace the board.
2.17 198092427 The number of SCTP streams is

inconsistent.
Severity
System Impact
Probable Cause
Handling Suggestion
SJ-20120322151347-005|2012-04-15(R1.1)
2.18
Severity
System Impact
Work normally
2.Impact on services
If all paths of an SCTP association are interrupted, service signaling

may not be transmitted/received properly. Consequently, the
corresponding services borne over this SCTP association are
completely interrupted.
Probable Cause
2. Path parameters of this path are wrongly configured either at local

end or peer end.
3. This path related bottom layer fails to communicate with peer end.
Handling Suggestion
Check whether there is an alarm, indicating a faulty bottom-layer
link. If yes, please handle the problem according to relevant handling

suggestions.
2. In Configuration Management Interface, check SCTP association

configuration including parameters such as local address, local port,
remote address and remote port at the sides of base station and its
peer end. Both sides must have the consistent configuration.
3. Re-configure SCTP association.
(1) Delete the faulty SCTP association from the Configuration

Management Interface.
(2) Add an SCTP association to the Configuration Management

Interface.
4. Reset the board.
2.19 198092431 The strength of received optical signal

is abnormal
Severity
SJ-20120322151347-005|2012-04-15(R1.1)

System Impact
Probable Cause
Handling Suggestion
if the alarm disappears.

Y=>End of alarm processing.
N=>Go to step 2.
2. Replace the optical module or fiber. Check if the alarm disappears.

N=>Go to step 3.
3. Check whether the length of real optical fiber is longer than the
transmission distance supported by the optical module.
Y=>Replace the optical module.
N=>Please communicate with ZTE's customer service representative.
2.20 198092445 RRU inner GNSS (clock reference

source) link alarm
Severity
System Impact
Work normally
2.Impact on Services:
If this fault lasts for a long period, partial functions may not work
properly. In serious situation, it may cause service failure, for example,
radio link setup failure.
Probable Cause
Handling Suggestion
2-13
SJ-20120322151347-005|2012-04-15(R1.1)
2.21 198092446 RRU inner GNSS (clock reference

source) link unavailable
Severity
System Impact
Work normally
If this fault lasts for a long period, partial functions may not work
properly. In serious situation, it may cause service failure, for example,
radio link setup failure.
Probable Cause
links.
Handling Suggestion
2. Check whether the configured RRU has other relevant faults caused
by antenna feeder, receiver or satellite searching function.
2.22 198094825 Optical link which bearing S1/X2 signal

breakdown error
Severity
System Impact
Probable Cause
Handling Suggestion
link broke
Severity
System Impact
Probable Cause
Handling Suggestion
SJ-20120322151347-005|2012-04-15(R1.1)
2.24 198092210 PLL reference clock lost alarm

Severity
System Impact
Probable Cause
Handling Suggestion
using SYNCE function, this alarm has no impact on the board.

2. If SYNCE mode is supportable, this alarm requires replacing the
board.
2-15
SJ-20120322151347-005|2012-04-15(R1.1)
2-16
SJ-20120322151347-005|2012-04-15(R1.1)
Chapter 3 Alarm
Equipment
Table of Contents
198100270 Optical signals transmitted from BBU to RRU carry wrong clock
information
the threshold
198092032
198092049
198092051
198092052
198092057
198092068
198092071
198092072
198092073
198092074
198092075
198092076
198092077
198092078
198092079
198092080
198092081
198092082
198092083
198092084
198092085
198092086
198092087
198092088
SJ-20120322151347-005|2012-04-15(R1.1)
198092089 Embedded power SMR L.Vin

198092090 Embedded power SMR Fuse Broken
198092091 Embedded power SMR CommFail
198092092 Embedded power DC Under-Volt
198092093 Embedded power DC Over-Volt
198092094 Embedded power DC Loop Broken
198092095 Embedded power Bat Loop Broken
198092096 Embedded power Bat Under-Volt
198092097 Embedded power Bat Over-Temp
198092098 Embedded power TmpL Shut-Down
198092099 Embedded power 1st Shut-down
198092100 Embedded power 2nd Shut-down
198092101 Embedded power DC SPD Broken
198092102 Embedded power DCBreaker Alarm
198092103 Embedded power Bat Test Failure
198092104 Embedded power Bat Discharge
198092116 Embedded power AC Auxiliary Output Switch Off
198092117 Embedded power Rectifier Module Fault
198092203 Board not-configured alarm
198092206 Battery alarm
198092207 AC power-cut alarm
198092208 Rectifier module alarm
198092209 Thermoelectric cooler alarm
198092212 EPLD's register has a R/W failure alarm
198092214 Hardware of Clock Module Fault
198092215 Lost of synchronization
198092216 Current Active Reference Source 1PPS Lost
198092217 Air Interface Clock Unavailable
198092219 Baseband Subunit Fault
198092234 Embedded power type configuration error
198092235 Embedded power communication interruption
198092236 Embedded power SMR Output Fault
198092237 Embedded power Bat Under-Temp
198092238 Embedded power Bat Invalid-Temp
198092239 Embedded power Battery Fault
198092241 1588 clock source unavailable
198092242 Ir link LCV alarm
198092243 Abnormal DPD running status
198092244 LNA alarm
198092245 Disable PA
198092246 TMA channel input is over current
198092247 Over-high temperature of PA
198092248 Optical module out-of-position alarm
198092249 RF board PLL alarm
198092250 Calibration file on TRx board is abnormal
3-2
SJ-20120322151347-005|2012-04-15(R1.1)
198092251
198092252
198092253
198092254
198092255
198092256
198092257
198092258
198092259
198092260
198092261
198092262
198092263
198092264
198092265
198092266
198092267
198092268
198092269
198092270
198092272
198092273
198092274
198092275
198092276
198092277
198092278
198092279
198092280
198092281
198092282
198092283
198092284
198092285
198092286
198092287
198092288
198092289
198092290
198092291
198092292
198092293
198092294
198092295
198092298
SJ-20120322151347-005|2012-04-15(R1.1)
198092311 IQ reported is failed

198092317 ACOM major alarm
198092318 ACOM minor alarm
198092319 ACOM hardware fault
198092320 ACOM communication link is interrupted
198092321 ACOM software fault
198092322 AISG EEPROM error
198092323 AISG flash erase error
198092324 AISG flash error
198092325 AISG other hardware error
198092326 AISG other software error
198092327 AISG RAM error
198092328 AISG UART error
198092330 ATMA major alarm
198092331 ATMA minor alarm
198092332 Failed to set gain
198092333 ATMA hardware fault
198092334 ATMA communication link is interrupted
198092335 ATMA software fault
198092336 Board configuration parameter error
198092337 RET motor fault
198092339 RET hardware fault
198092340 RET motor can't adjust
198092341 RET motor don't respond the adjusting command
198092342 RET communication link is interrupted
198092343 RET don't calibrated
198092344 RET data don't scaled
198092345 RET position lost
198092346 RET software fault
198092352 Unmatched link mode at peer-end electrical port of Ethernet
198092353 Configuration is failed
198092363 Faulty main power alarm
198092364 Calibrate Fail
198092365 Low Power Exception
198092374 UCI optical module of optical port is out of position
198092375 UCI optical module of optical port has no light signal
198092376 UCI receiver frame at optical port is unlocked
198092377 UCI fiber delay adjust is failed
198092378 Board PLL is unlocked
198092379 PA over power alarm
198092383 Distributing IQ resource is failed
198092384 It is failed to configurate IQ
198092385 It is failed to configurate optical port speed
198092386 It is failed to configurate TDM port speed
198092387 It is failed to configurate RRU device delay parameter
3-4
SJ-20120322151347-005|2012-04-15(R1.1)
198092388 It is failed to configurate power supply

198092393 UES ethernet semiduplex alarm
198092394 Several rectifiers faulty
198092400 Board smart powered-down
198092401 E1 link self-loop
198092409 GNSS antenna feeder alarm
198092415 The built-in-type GNSS receiver has an alarm
198092416 The built-in-type GNSS antenna has a feeder cable alarm
198092418 The external-panel-type GNSS receiver has an alarm
198092419 The external-panel-type GNSS antenna has a feeder cable alarm
198092421 The external-panel-type GNSS receiver has an alarm, indicating its
foreground working mode is inconsistent with background
198092422 The external-backplane-type GNSS receiver has an alarm
198092423 The external-backplane-type GNSS antenna has a feeder cable alarm.
3-96
198092425 The external-backplane-type GNSS receiver has an alarm, indicating
its foreground working mode is inconsistent with background
198092426 GNSS cascading clock has an alarm
198092433 RRU network interrupted alarm
198092434 Clock line abnormal connection in stack mode
198092435 Inter-frame Ethernet link broken in stack mode
198092436 Loss of clock synchronization at slave frame
198092437 RU radio frequency group unavailable
198092438 Device in low temperature
198092439 Uplink transport port of a base station operates in a different mode from
configured one
198092447 Unbalanced AC phase voltage of built-in power
198092448 High AC phase current of built-in power
198092449 Missing AC phase voltage of built-in power
198092450 Battery low-voltage cut-off of built-in power
198092451 Broken LLVD1 branch E of built-in power
198092452 Broken LLVD1 branch of built-in power
198092453 Broken LLVD2 branch E of built-in power
198092454 Broken battery cut-off branch E of built-in power
198092455 Broken battery cut-off branch of built-in power
198092456 Abnormal battery current of built-in power
198092457 Abnormal CAN bus of built-in power
198092458 Abnormal battery of built-in power
198092459 Abnormal input dry contact of built-in power
198092460 High-temperature cut-off of built-in power
198092461 BBU inter-subrack frame synchronization failure alarm
198092550 User-defined dry contact alarm 1
3-5
SJ-20120322151347-005|2012-04-15(R1.1)

3-6
SJ-20120322151347-005|2012-04-15(R1.1)
system limit
real parameter
Severity
System Impact
Probable Cause
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
2. If the fiber is well connected but the alarm lasts for a long time,
reset this RRU.
3. After resetting, if the problem cannot be removed, replace the RRU.
3.2 198100271 Unlocked local oscillator alarm of RRU

Severity
System Impact
Work normally
The local oscillator belongs to a board (master or slave). All the

board-related channels are closed and cannot bear services.
Probable Cause
Handling Suggestion
2. If the fiber is well connected but the alarm lasts for a long time,
reset this RRU.
3. After resetting, if the problem cannot be removed, replace the RRU.
3.3 198100272 RRU inside clock unlocked

Severity
System Impact
Probable Cause
Handling Suggestion
3-8
SJ-20120322151347-005|2012-04-15(R1.1)
3.4
Severity
System Impact
Work normally
Because RRU Tx channel cannot work properly, services borne on it

are interrupted.
Probable Cause
Handling Suggestion
ignore it.
2. If the alarm lasts for more than 10 minutes or occurs frequently,

replace RRU or check the corresponding baseband process board
at BBU end.
3.5 198100274 Downlink output power abnormal

Severity
System Impact
Work normally

are interrupted.
Probable Cause
fault).
2. Software fault.
Handling Suggestion
ignore it.

at BBU end.
3-9
SJ-20120322151347-005|2012-04-15(R1.1)
3.6
alarm
Severity
System Impact
Work normally

are interrupted.
Probable Cause
fault).
2. Software fault.
Handling Suggestion
ignore it.

at BBU end.
3.7 198092008 FPGA register read/write error

Severity
System Impact
The board is faulty.

2. Service Impact:
The board software update fails and the services provided by this board
is completely interrupted.
Probable Cause
Handling Suggestion
the alarm first.
2. Reset the board.
3-10
SJ-20120322151347-005|2012-04-15(R1.1)
3.8
abnormal
Severity
System Impact
Probable Cause
Handling Suggestion
is configured with the correct mode. In Test Management, check the

Ethernet interface connection test items.
2. Check the Ethernet interface connection indicator. If it is constantly

ON, it indicates that the physical connection is normal. If it flashes, it
indicates that there is data being transceived.
3. Check whether the Ethernet interface's physical connection is
normal. In Ethernet connection mode, at least one of the optical
interface and the Ethernet interface should be connected correctly.
When the connecting cable is extracted, the Ethernet interface's
connection indicator is OFF. when the connecting cable is inserted, the
Ethernet interface's connection indicator is constantly ON or flashes.
4. Remove and insert the board.
3.9 198092011 E1/T1 input port unavailable

Severity
System Impact
Probable Cause
Handling Suggestion
Management is the same as the one runs in base station.

2. Check DDF connections to find out whether jumpers are well
connected, there is no impurity, rubber-insulated wires are not in
short-circuit.
3. Check the ports of optical transceiver (or repeater) to find out whether
E1/T1 cables are tightly connected at the panels of SA/SE/PSA.
4. Check transmission link. Conduct loopback test to find which node
has a problem.
3-11
SJ-20120322151347-005|2012-04-15(R1.1)
5. Check whether link loopback test between BSC/RNC and

transmission network is normal.
6. Replace the E1/T1 connection cables at the panels of SA/SE/PSA.

7. Replace the input port of repeater (or optical transceiver).
3.10
Severity
System Impact
Probable Cause
Handling Suggestion
Management is the same as the one runs in base station.
2. Check DDF connections to find out whether jumpers are well
connected, there is no impurity, rubber-insulated wires are not in
short-circuit.
4. Check transmission link. Do loopback test to find which node has
a problem.


7. Replace the output port of repeater (or optical transceiver).
3.11 198092013 ES or SES detected on the E1 link in

the past 15 minutes has exceeded the threshold
Severity
System Impact
Probable Cause
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
clean. Confirm the RING and TIP line is not shorted.
2. Check transmission link. Do loopback test to find the bad node in

the transmission network.
3. Check the link between BSC/RNC and transmission network.

4. Firm the plug of connection line at SA face plate and optical
transceiver(or repeater).
5. Replace the port of optical transceiver or repeater.

6. Replace the connection line at SA face plate.
3.12 198092032 Failed to operate Database

Severity
System Impact
Probable Cause
Handling Suggestion
configuration is correct.
2. In the Configuration Management interface, operate configuration

data synchronization.
3.13 198092049 Lightning protection device alarm

Severity
System Impact
Work normally
The power interface cannot be protected from lightning attack.
3-13
SJ-20120322151347-005|2012-04-15(R1.1)
Probable Cause
dry contact alarm is wrongly configured. Note that there are two kinds
of status: normally closed, normally open.
2. The SPD is faulty because of lightning attack, not well grounded or

ageing failure.
3. The environment monitoring unit is faulty.
Handling Suggestion
contact alarm is correctly configured.
Note that different devices adopt different configuration methods at dry

contacts, which is determined by types of devices.
2. Check whether the monitoring cable at a dry contact is good. If not,

please replace it.
3. Replace the lightning protection box.

3.14 198092051 PSU alarm
Severity
System Impact
Probable Cause
Handling Suggestion
3.15 198092052 PSU fan alarm

Severity
System Impact
Probable Cause
Handling Suggestion
SJ-20120322151347-005|2012-04-15(R1.1)
Severity
System Impact

2. Service Impact:
The board's communication link is broken, and services the board

bears are interrupted.
Probable Cause
Handling Suggestion
additional information, check
whether the inserted board of the NE is inconsistent with that configured

at OMCB.
the board type of base station(X is 0~F):

CC 0x30XX
FS 0x34XX
SA 0x35XX
SE 0x36XX
PM 0x37XX
PSA 0x3CXX
FCE 0x62XX
TAM 0x64XX
2. Turn on the board's power supply.
3.17 198092068 Base station has a main power cut-off

alarm
Severity
System Impact
Board Operation is normal.

2. Service Impact:
1. Case 1
1)System operation will not be affected temporarily. In the long

run, system powers supply might become inadequate, leading to
degradation of service performance, or even service interruption.
2) If the alarm is generated in RRU, power amplifier will be automatically
off. The service on the RRU is down.
Probable Cause
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
2. Reset the board.
3. Replace the relevant dry contact cable.

4. Replace the board .
3.18
Severity
System Impact
Work normally
The system cannot monitor temperature of environment or devices.
Services are not affected.
Probable Cause
Handling Suggestion
handle the problem according to the following steps:

1. Check whether the temperature sensor has been installed.
2. Check whether the relevant cable is loose or broken.
3. Check whether the temperature sensor is broken.
If the temperature sensor should be installed on other boards, please
handle the problem according to the following steps.
1. Temperature sensor at wind inlet is abnormal.
(1). Remove and insert the fan board.
(2). Replace the fan board.
2. Temperature sensor at wind outlet is abnormal.

(1). Replace board.
3.19 198092072 Board not-in-position

Severity
System Impact

2. Service Impact:
The board can't bear any service.
3-16
SJ-20120322151347-005|2012-04-15(R1.1)
Probable Cause
board is configured, but actually no board is inserted in the slot.

2. The network management interface shows the slot in which the
board is configured, but the board is not inserted tightly.
board is configured, but the connection part is physically damaged.
Handling Suggestion
3.Replace the shelf.
Severity
System Impact
Probable Cause
2. The main air break switch's contact is disconnected or of bad contact.

3. The monitoring unit's socket is of bad contact or disconnected.
4. The monitoring unit is faulty.
5. The AC loop is short-circuited.
Handling Suggestion
2. Check the air break switch's contact.
3. Check whether the monitoring unit's socket is inserted properly.

4. Replace the monitoring unit.
3.21 198092074 Embedded power AC Power Off

Severity
System Impact
Probable Cause
2. The AC transducer's connection is faulty or the transducer is

damaged.

3-17
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
provide power supply.
2. Check whether the AC transducer's connection is normal and

whether the transducer has no problem.

3.22 198092075 Embedded power SPD-C Broken

Severity
System Impact
Probable Cause
2. The air break switch of the lightning protector is disconnected.

3. The lightning protector's base is of bad contact.
4. The lightning protector's detecting cable is disconnected or of bad

contact.

Handling Suggestion
2. Check whether the lightning protector's air break switch is closed.
3. Check whether the lightning protector's base is of bad contact.
4. Check whether the contact of the lightning protector's base is
disconnected or of bad contact.
5. Check the monitoring unit's connection.

3.23 198092076 Embedded power SPD-D Broken

Severity
System Impact
Probable Cause
2. The lightning protector's base is of bad contact.

contact.

3-18
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
2. Check whether the lightning protector's base is of bad contact.
3. Check whether the contact of the lightning protector's base is
4. Check the monitoring unit's connection.

3.24
Severity
System Impact
Probable Cause
2. The AC under-voltage value of the monitoring unit is set too high.

damaged.

Handling Suggestion
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.


3.25 198092078 Embedded power AC Over-Volt

Severity
System Impact
3-19
SJ-20120322151347-005|2012-04-15(R1.1)
Probable Cause
2. The AC over-voltage value of the monitoring unit is set too low.

damaged.

Handling Suggestion
2. If the detected AC voltage value is higher than the threshold value

for alarm of AC voltage being high, then appropriately increase the
threshold value.


3.26 198092079 Embedded power AC Current Over

Severity
System Impact
Probable Cause
Handling Suggestion
2. Check whether the AC input voltage is too low.

3. Check whether the AC power supply is overloaded.
3.27 198092080 Embedded power SMR Over-Vout

Severity
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
2. Check the monitoring unit's socket.

3. Replace the rectifier.
3.30 198092083 Embedded power SMR PFC Fault

3-21
SJ-20120322151347-005|2012-04-15(R1.1)
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
Probable Cause
Handling Suggestion
higher than the threshold value.
2. Improve the ventilation condition of the equipment room.

3.34 198092087 Embedded power SMR Env.H.T.Off

Severity
System Impact
Probable Cause
Handling Suggestion

3.35 198092088 Embedded power SMR Env.H.T

Severity
System Impact
Probable Cause
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).
2. The rectifier is damaged.
3-23
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion

3.36 198092089 Embedded power SMR L.Vin

Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
2. The AC voltage sampling is influenced.
3. The decision whether the AC power supply should be powered off is

influenced.
4. It influences the power supply for the base station.
Probable Cause
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
2. Check whether the AC power supply is powered down. If it is, then
set the current for the minimum load to be less than the current for the
present load. otherwise, check whether the RS485 communication
cable is of bad contact or disconnected, and whether the loop is
short-circuited.
3. Check whether the RS485 communication cable at the slot is broken.

5. Check and repair the signal cable at the slot.

3.39 198092092 Embedded power DC Under-Volt

Severity
System Impact
Probable Cause
Handling Suggestion
2. Check whether the DC under-voltage value of the monitoring unit

is set appropriately.

3-25
SJ-20120322151347-005|2012-04-15(R1.1)
3.40 198092093 Embedded power DC Over-Volt

Severity
System Impact
Probable Cause
2. The DC over-voltage value of the monitoring unit is set too low.

3. The rectifier is faulty.

Handling Suggestion
2. Check whether the DC under-voltage value of the monitoring unit


3.41 198092094 Embedded power DC Loop Broken

Severity
System Impact
Probable Cause
broken).
2. The detecting cable of the load's loop is disconnected or of bad
contact.

Handling Suggestion
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.

3-26
SJ-20120322151347-005|2012-04-15(R1.1)
3.42
Severity
System Impact
Probable Cause
2. The detecting cable of the battery's loop is disconnected or of bad

contact.

Handling Suggestion
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

4. Check whether the monitoring unit's socket is of bad contact or
disconnected.
3.43 198092096 Embedded power Bat Under-Volt

Severity
System Impact
Probable Cause
2. The battery's under-voltage value of the monitoring unit is set too

high.
3. The detecting cable of the battery is faulty.

3-27
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
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.
3.44 198092097 Embedded power Bat Over-Temp

Severity
System Impact
Probable Cause
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
2. Check whether the battery's over-temperature value of the

3. Check whether the battery's temperature sensor is damaged.

disconnected.
3.45 198092098 Embedded power TmpL Shut-Down

Severity
System Impact
Probable Cause
power-down in low-temperature environment.

3-28
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
2. Check whether the threshold value for power-down in

low-temperature environment of the monitoring unit is set appropriately.
disconnected.
3.46
Severity
System Impact
Probable Cause
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
voltage for first power-down.
2. Check whether the first power-down voltage of the monitoring unit

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.
3-29
SJ-20120322151347-005|2012-04-15(R1.1)
3.47
Severity
System Impact
Probable Cause
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
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.
3.48 198092101 Embedded power DC SPD Broken

Severity
System Impact
3-30
SJ-20120322151347-005|2012-04-15(R1.1)
Probable Cause
contact.
2. The DC lightning protector is damaged.
Handling Suggestion
2. Replace the DC lightning protector.
Severity
System Impact
Probable Cause
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
being small.
2. Check whether the control signal channel is normal.

3. Replace the DC contactor.
4 Replace the monitoring unit.
3.50 198092103 Embedded power Bat Test Failure

Severity
System Impact
Probable Cause
2. The battery is not connected correctly.
3. The power supply capability of the battery is not enough.

4. Parameters related to the battery test are not set appropriately.
3-31
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
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.
3.51 198092104 Embedded power Bat Discharge

Severity
System Impact
Probable Cause
for alarm.
2. The battery's current measurement is not accurate.

3. The threshold value for alarm is not appropriate.
4. The AC transducer or the monitoring unit is damaged, causing that

the current is beyond the detection range.
Handling Suggestion
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.
4. Check whether the current is beyond the detection range.

5. Replace the AC transducer or the monitoring unit.
3.52 198092116 Embedded power AC Auxiliary Output

Switch Off
Severity
System Impact
Probable Cause
2. The air break switch's contact is disconnected or of bad contact.

3-32
SJ-20120322151347-005|2012-04-15(R1.1)

Handling Suggestion
2. Check the air break switch's contact.

3.53 198092117 Embedded power Rectifier Module

Fault
Severity
System Impact
Probable Cause
2. The air break switch corresponding to the rectifier module is not

opened.
3. The rectifier module is pulled out.
4. The slots at the rectifier cabinet are damaged.

Handling Suggestion
2. Check whether the air break switch corresponding to the rectifier

is opened.
3. Check whether the rectifier which has the alarm is pulled out.
4. Check whether there is any slot at the rectifier cabinet is
short-circuited or burned.

3.54 198092203 Board not-configured alarm

Severity
System Impact
The board is not configured.

2. Service Impact:
There is no influence on services.
3-33
SJ-20120322151347-005|2012-04-15(R1.1)
Probable Cause
physical board is inserted.
Handling Suggestion
remove this physical board.
2. A board in-slot signal has been detected, but in fact this slot is not
configured with any board. If this happens, it means PM board is faulty.
Please replace the faulty PM board.
3.55
Severity
System Impact
Work normally
If the battery works for a long time, the system may not work properly.
In bad situation, services are interrupted.
Probable Cause
Handling Suggestion

2. Check whether the monitoring cable at dry contact is good. If not,

please replace it.
3. Check the master battery.

4. Reset the board.
5. Remove and insert the board again.
3.56 198092207 AC power-cut alarm

Severity
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
Work normally
Because AC power is cut, the system can only rely on the battery for
a while.
Probable Cause
Handling Suggestion
please replace it. .
2. Start diesel engine in an emergency.

3. Restore AC power as soon as possible.
3.57 198092208 Rectifier module alarm

Severity
System Impact
Work normally
Power cannot be normally supplied so that the system paralyzes and

services are interrupted.
Probable Cause
Handling Suggestion
please replace it.
Severity
System Impact
Work normally
When the thermoelectric cooler is faulty, battery lifetime may be

shortened. Furthermore, system services may also be affected.
Probable Cause
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
replace it.
2. Replace the cable connected the thermoelectric cooler.

3.59198092212 EPLD's register has a R/W failure alarm.

Severity
System Impact
Probable Cause
Handling Suggestion
10M clock refers to the clock crystal of master board, this alarm is
reported when crystal without output.
2-Serdes clock PLL loss
PLL is the clock chip, the input is a 10M clock, the output is multi-Serdes
clock; when the PLL without output or the output clock frequency is
not 61.44M, the alarm is reported .
3-Serdes clock lost
If the PLL lock, but the standby board did not report the Serdes, the
alarm is reported.
4-phase clock is lost
Phase clock refers to phase locked of soft PLL phase detector, the
alarm is reported when phase clock is lost
5-transfer alarm is abnormal
Standby board or mater board is each other's partner board, the alarm
is reported when either of them cannot receive alarm which is send by
partner board.
6-partner board transfer data is abnormal
3-36
SJ-20120322151347-005|2012-04-15(R1.1)
Standby board or mater board is each other's partner board, the alarm
is reported when data format or content of the alarm which is received
from partner has problem.
7-Frame synchronization signal error
The alarm is reported when standby board can not detected the alarm.
8-PLL clock of net port is lost
PLL clock of net port refers to the alarm outputted by PLL network port ,
the alarm is reported when the PLL lock without PLL clock.
9-PLL of net port is lost
PLL of net port refers to the PLL which provide work alarm to the PHY
chip and exchange chip, the alarm is reported when PLL chip meet
lose of lock.
Severity
System Impact
board is fault.
2. service influence:
when master board is fault, system can not work normally and the
corresponding clock modul of the outer board is alarm. It cause all
services are interrupted. If the slave board is fault, the system can run
normally. But master-to-slave switch cannot be executed when master
board is fault. It reduces the system reliability.
Probable Cause
Handling Suggestion
1. Reset board
2. Remove and insert board

2-Serdes clock PLL lost
1. Reset board
2. Check if the running version is correct

3-Serdes clock lost
1. Reset board

4. Change CC board to another CC slot

4-Phase clock lost
1. Reset board
5-Frame synchronization signal is wrong

1. Reset board

4. Change CC slot
6-PLL clock of net port is lost
3-37
SJ-20120322151347-005|2012-04-15(R1.1)
1. Reset board

7- PLL of net port is lost
1. Reset board
3.61
The board is in the mode of time or 3d-fix.And it is under the condition

of receiving satellite being normal. Fine adjustment cannot be done
on it in two hours after it begins to run normally. Alarm of OCXO not
locking will be reported.
2.Phase too large
The time of the subsidiary phase being used to control is more than 30
minutes. And it is not in the main phase's controlling.
3.Control voltage abnormal
OCXO causes control voltage beyond the range of 0X0500~0XFB00.
Severity
System Impact
board is fault.
when master board is fault, system cannot work normally and the
corresbording clock module of the outer board is alarm. It cause all
services are interrupted. If the slave board is fault, the system can run
normally. But master-to-slave switch cannot be executed when master
board is fault. It reduces the system reliability.
Probable Cause
Handling Suggestion
1. Diagnose the control phase to see whether the absolute value is

less than 10.
2. Do diagnoses several times in a half of an hour to see phases is

close to around 0.
3. If it cannot be convergent all the time, reset the board.

Phase too large:
1. Wait for 30 minutes to see whether it resumes.

2. Diagnose the subsidiary control phase to see whether the absolute
value is less than 10.
3. Do diagnoses several times in a half of an hour to see phases is

close to around 0.
3-38
SJ-20120322151347-005|2012-04-15(R1.1)
4. If it cannot be convergent all the time, reset the board.

Control voltage abnormal:
1. Reset the board.
2. Check the version which the board is running.
3.62 198092216 Current Active Reference Source 1PPS

Lost
Severity
System Impact
Probable Cause
signal.
2. For the outer card of receiver, outer receiver does not output 1PPS
signal.
3. For the 1588, the 1588 processer does not output 1PPS signal.
Handling Suggestion
accordance with real signa.
2.Secondly,to check whether the running version in the boare is correct.

3.Reset the board.
4.Pull and push the board.
3.63 198092217 Air Interface Clock Unavailable

Severity
System Impact
Probable Cause
3-39
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
configured, do it and observe. If it is configured, check whether there
is satellite receiving fault, 1588 packet loss rate fault or the current
reference clock source losing alarm. If there are alarms, deal with
them. Otherwise, change the board.
3.64 198092219 Baseband Subunit Fault

Severity
System Impact
Probable Cause
Handling Suggestion
error
Severity
System Impact
Probable Cause
Handling Suggestion
interruption
Severity
System Impact
Probable Cause
SJ-20120322151347-005|2012-04-15(R1.1)

Handling Suggestion

disconnected.
3.67 198092236 Embedded power SMR Output Fault

Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
under-temperature of battery.
2. The battery's under-temperature value of the monitoring unit is set

too high.

Handling Suggestion
2. Check whether the battery's over-temperature value of the


disconnected.
3-41
SJ-20120322151347-005|2012-04-15(R1.1)
3.69 198092238 Embedded power Bat Invalid-Temp

Severity
System Impact
Probable Cause
in the detection.

3. The temperature sensor of the battery is not connected.
Handling Suggestion
2. Check whether the temperature sensor is connected reliably.

3. Replace the temperature sensor.

3.70 198092239 Embedded power Battery Fault

Severity
System Impact
Probable Cause
battery capacity.
2. The connection to the power is not reliable.

5. The battery is faulty.
Handling Suggestion
capacity is configured properly.
2. Check whether the power is connected reliably.

disconnected.

5. Replace the battery.
3-42
SJ-20120322151347-005|2012-04-15(R1.1)
3.71 198092241 1588 clock source unavailable

Severity
System Impact
Probable Cause
Handling Suggestion
2.Check transmission parameter configuration and clock parameter

configuration, related to the link. For example, check whether the
primary clock IP is correctly configured.
3.72
Severity
System Impact

2. Service Impact:
Code error might occur to signaling and IQ, resulting in service

performance degradation and interruption
Probable Cause
Handling Suggestion
between the local board and the higher level board.

(1). Check the detailed information of this alarm on the fault
management interface. The detailed information of the alarm presents
the detailed information of defective optical port.
In the case of optical port 0 alarm, check the connection of the fiber
optics and the optical module between the local RRU and the higher
level board. Reconnect the fiber and the module if any insecure
connection is found.
In the case of optical port 1 alarm, check the connection of the

fiber optics and the optical module between the local RRU and the
lower level RRU. Reconnect the fiber and the module if any insecure
connection is found.
(2). Replace the fiber optics.
3-43
SJ-20120322151347-005|2012-04-15(R1.1)
2. Check the fiber optics between the boards for possible damage.
Replace the fiber if any damage is found.
3.73 198092243 Abnormal DPD running status

Severity
System Impact
Probable Cause
Handling Suggestion
3.74 198092244 LNA alarm
Severity
System Impact
Probable Cause
Handling Suggestion
2. Reset the board.
3. Replace the internal LNA of the board.

3.75 198092245 Disable PA

Severity
SJ-20120322151347-005|2012-04-15(R1.1)

System Impact
Probable Cause
Handling Suggestion
2. Check whether it has Remote input power over-voltage alarm in

fault management interface in OMCB, if it is right please handle with
the steps as follows:
(1) Check the antenna failure.
i. Check if RRU is connected to the antenna properly. Connect the

antenna in case it is not connected.
ii. Check if antenna feeder is properly connected. If there is any

problem with the connection, correct the problem according to the
construction diagram.
iii. Verify that the connector of the antenna feeder is tightened securely.
Fasten the connector if the connection is loose.
(2) Check the feeder standing waves of each level.
i. Check if the standing wave of feeder is normal. Replace the feeder if

the standing wave is not normal.
ii. If combiner is connected to the feeder, check if the standing wave of

the combiner is normal. Replace it if the standing wave is not normal
iii. Check if the antenna is normal. Replace or repair it if there is any
problem with the antenna.
(3) Check the RRU for possible failure.

i. Reset the board.
ii. Check the RRU for the poor connection of the RF cable. Fasten the
cable or replace it if any loose or disconnection is found.
iii. Check the power amplifier for possible failure. Replace the power
amplifier in case of any damage.
iv. Check the duplex for possible damage. Replace the duplex in case
of any damage.
v. Replace the board.
3.76 198092246 TMA channel input is over current

Severity
3-45
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
Probable Cause
2. The connection between TMA power cable and ground is in the state
of short circuit or low resistance;
3. TAC has fault;
4. TMA has fault.
Handling Suggestion
correctly.
2. Check if the state between TMA power cable and the ground is short
circuit or low resistance.
3.77 198092247 Over-high temperature of PA

Severity
System Impact
Work normally.
The PA output is closed so that its correspoinding RF channel has

no output power. Consequently, all services borne on the board are
interrupted.
Probable Cause
2. PA is abnormal.
Handling Suggestion
(1) Make sure the indoor air conditioner works properly.

(2) Make sure the fan runs normally.
RRU fault:
(1) Replace the PA.
(2) Replace the board.
3.78 198092248 Optical module out-of-position alarm

Severity
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
The board is normal.

2. Service Impact:
if port 0, board communication link is down. If port 1, the next board on

the service is down.
Probable Cause
Handling Suggestion
and FS functionality board. Ensure that optical module and fiber have
been installed.
2. Replace the optical module/fiber of FS functionality board. Replace

the optical module used by the faulty optical port.
3.79 198092249 RF board PLL alarm

Severity
System Impact
Work normally
2. Service Impact:
RF output is affected. RF channel cannot work normally. The service

on the board is down
Probable Cause
Handling Suggestion
version.
2. Reset the board.

3.80 198092250 Calibration file on TRx board is
abnormal
Severity
3-47
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
Work normally.
2. Service Impact:
1) Downlink calibration file abnormal, transmission power will be

inaccurate, affecting system coverage
2) Uplink calibration file abnormal, RSSI report error will increase,

affecting service performance
Probable Cause
Handling Suggestion
channel alarm
Severity
System Impact
Probable Cause
Handling Suggestion
Related alarms:
198084003 Clock module fault
198084004 Clock reference source is lost

198084006 Clock reference source is degraded
198084266 Clock has a critical alarm
198084301 Transport clock reference source is fault

198084303 Clock has significant alarm

198084231 RRU clock frequency drift
198084299 PLL unlock alarm
2. Reset board.
3.82 198092252 Downlink digital IF pre-distortion alarm

Severity
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
Probable Cause
Handling Suggestion
(related to abnormal power and VSWR) occurs. If yes, refer to the

corresponding alarm handling suggestion.
Related alarms:
198084065 Abnormal power

198084232 Digital power abnormal
198084045 Antenna VSWR alarm
198084046 Antenna over VSWR alarm
198084093 Remote antenna over VSWR alarm
198084094 Remote antenna VSWR alarm
2. Reset RF board.
3. Replace RF board.
3.83 198092253 Application software monitoring alarm

Severity
System Impact
Probable Cause
Handling Suggestion
alarm.
Step: Open the Fault Management interface and check if an alarm

"communication link is interrupted alarm" appears to this board.
2. Check if the board has "The board parameter configuration is
incorrect" alarm.
Step: Open the Fault Management interface and check if an alarm "The
board parameter configuration is incorrect" appears to this board.
3. Reset the board.
3-49
SJ-20120322151347-005|2012-04-15(R1.1)
3.84 198092254 Remote output power abnormal

voltage alarm
Severity
System Impact

2. Service Impact:
The board or system might fail to work normally. The service on the
board might be down.
Probable Cause
Handling Suggestion
power supply in case of voltage error.

The normal rang of the power supply is:
DC voltage:-36 V - -60 V
AC voltage:80 V - 280 V
2. Replace the RRU power unit and wire the power unit to the RRU
interior module properly.
3.85198092255 Remote input power over-voltage alarm

Severity
System Impact

2. Service Impact:
No impact on service in short-time operation. Long-term operation
might result in board or system abnormity, and the service on the board
will be down.
Probable Cause
higher than alarm threshold 60 V(error ±1V).
3-50
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
threshold 280 V(the tolerance is +/-1V).
(1). Shut down the RRU and disconnect it from power socket. Check
whether the voltage of the AC input is higher than 281 V (the tolerance
is +/- 1V).
(2). Replace the voltage module RPWDC of RRU.

2. The DC input voltage of power module is higher than the alarm
whether the voltage of the DC input is higher than 61 V(the tolerance is
+/- 1V).
3.86 198092256 Remote input power under-voltage

alarm
Severity
System Impact

2. Service Impact:
No impact on service in short-time operation. Long-term operation

might result in board or system abnormity, and the service on the board
will be down.
Probable Cause
than alarm threshold 36 V(error ±1V).

Handling Suggestion
whether the voltage of the AC input is lower than 81 V(the tolerance is
+/- 1V).

2. The DC input voltage of power module is lower than the alarm
whether the voltage of the DC input is lower than 37 V(the tolerance is
+/- 1V).
3-51
SJ-20120322151347-005|2012-04-15(R1.1)
3.87
Severity
System Impact
Work normally.
2. Service Impact:
The board or system fails to work normally. The service on the board
is down.
Probable Cause
Handling Suggestion
(1). Check if RRU is connected to the antenna properly. Connect the

(2). Check if antenna feeder is properly connected. If there is any

(3). Verify that the connector of the antenna feeder is tightened

securely. Fasten the connector if the connection is loose.
2. Check the feeder standing waves of each level.
(1). Check if the standing wave of feeder is normal. Replace the feeder
if the standing wave is not normal.
(2). If combiner is connected to the feeder, check if the standing wave

of the combiner is normal. Replace it if the standing wave is not normal
(3). Check if the antenna is normal. Replace or repair it if there is any
3. Check the RRU for possible failure.

(1). Reset the board.
(2). Check the RRU for the poor connection of the RF cable. Fasten
the cable or replace it if any loose or disconnection is found.
(3). Check the power amplifier for possible failure. Replace the power
(4). Check the duplex for possible damage. Replace the duplex in
case of any damage.
(5). Replace the board.
3.88 198092258 Lost of frame rate and frame number

Severity
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Work normally
Because battery voltage is low, its lifetime is affected. If battery engergy

is used up, the system cannot work normally.
Probable Cause
Handling Suggestion
please replace it.
2. Charge the battery as soon as possible and wait until it restores to

normal voltage.
3.90 198092260 Faulty external device connected at

a dry contact
Severity
System Impact
Probable Cause
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
2. Reset the SA board.
3. Replace the cable that is connected to the dry contact.

4. Replace SA board.
3.91
Severity
System Impact
Work normally
Devices cannot be protected from lightning attack, but services will

not be affected.
Probable Cause
not well grounded or ageing failure.
Handling Suggestion


please replace it.
3. Replace the cable that is connected between RRU and outdoor

lightning protection box.

5. Replace RRU.
3.92 198092262 Breaker alarm in indoor lightning

protection box
Severity
3-54
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
Work normally
The breaker is associated to a power circuit. This power cuicuit has

no current. If it is used to supply power to RRU, services will surely
be affected.
Probable Cause
2. The dry contact is not well connected or correctly configured.
Handling Suggestion


please replace it.
3. Check the status of the breaker. Find out the reason for over-current
protectin or open circuit, then solve the problem.
4. Replace the breaker.
5. Reset the board.

3.93 198092263 Lightning protection device alarm in

indoor lightning protection box
Severity
System Impact
Work normally
Devices cannot be protected from lightning attack, but services will

not be affected.
Probable Cause
not well grounded or ageing failure.
3-55
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion


please replace it.
3. Check whether the input voltage of main power is normal. If not,

replace the main power.
Normal voltage range should be:

DC voltage: -36 V-60 V
AC voltage: 80 V~280 V
4. Reset the board.
6. Make sure the lightning protection device is well grounded.

3.94
Severity
System Impact
Work normally
Either the board or the system may not work properly. All services
borne on the board are interrupted.
Probable Cause
Handling Suggestion
abnormal. If yes, replace it.

DC voltage: -36 V~-60 V

please replace it.
3. Reset the board.

3-56
SJ-20120322151347-005|2012-04-15(R1.1)
3.95
Severity
System Impact
Work normally
Probable Cause
Handling Suggestion


please replace it.
3．Check whether input voltage of the main power module is abnormal.

If yes, replace it.

4. Reset the board.
3.96 198092266 Under-voltage alarm of main power

input
Severity
System Impact
Work normally
Probable Cause
SJ-20120322151347-005|2012-04-15(R1.1)

Handling Suggestion
If yes, replace it.


please replace it.
3. Reset the board.

3.97 198092267 General fault of main power

Severity
System Impact
Work normally
Situation 1: If non-RRU board reports this alarm, the system can work
properly for a while. But if this situation lasts for a long term, the system
must be lack of electricity.
Situation 2: If RRU reports this alarm, the system will automatically

close the relevant PA. As a result, services borne on the RRU are
interrupted.
Probable Cause
Handling Suggestion
Severity
System Impact
Work normally
If PWR monitoring unit reports this alarm, the power-related

performance cannot be correctly reported. But this doesn't affect
services.
3-58
SJ-20120322151347-005|2012-04-15(R1.1)
Probable Cause
Handling Suggestion
please replace it.
3.99
Severity
System Impact

The PA output is closed so that its corresponding RF channel has

no output power. Consequently, all services borne on the board are
interrupted.
Probable Cause
2. The fan has a fault.
Handling Suggestion

RRU fault:
(1) Replace the PA.

3.100 198092270 Slight-high temperature of RU board

Severity
System Impact
Probable Cause
2. The fan has a fault.
3. The air conditioner has a fault.

4. The temperature sensor in the fan subrack at control layer is faulty.
3-59
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion

RRU fault:
(1) Replace the PA.

3.101 198092272 The value of RSSI over reverse link

is low.
Severity
System Impact
Probable Cause
Handling Suggestion
abnormality through long-term observation and RRU reboot. If it is

caused by hardware, go to the flow of repairment.
3.102 198092273 The value of RSSI over reverse link

is high.
Severity
System Impact
Probable Cause
3-60
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
find out the interference source and handle it. However if it is poor
connection at antenna port, approach the corresponding site to handle
antenna port problem.
3.103 198092274 Slight-high temperature of PA

Severity
System Impact
Probable Cause
Handling Suggestion

RRU fault:
(1) Replace the PA.

3.104 198092275 PA communication fault

Severity
System Impact
Work normally.
2. Service Impact:
It is impossible to configure corresponding parameters of PA module.

The service on the board is down.
Probable Cause
connects PA and monitoring module.
3-61
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
2. Check the connection wire between the power amplifier and the
monitor module and ensure it is securely connected.
3. Replace the power amplifier module.
4. Replace the monitor module.
3.105 198092276 Receiving RF channel fault

Severity
System Impact
Work normally.
2. Service Impact:
The receiving channel of transceiver board cannot work normally. The

service on the board is down.
Probable Cause
Handling Suggestion
3.106 198092277 Clock module fault

or 122.88M, FR and FN signals, the system gives this alarm. When

peripheral board cannot detect local benchmark clock, 61.44M or
122.88M, FR and FN signals, sent from main control board, the system
also gives this alarm.
Severity
System Impact
Work normally.
2. Service Impact:
When master main control board has a fault, it brings several

problems: the system cannot work normally; peripheral board may
have corresponding fault alarm occurs at clock module; this clock fault
causes interruption of all services. When slave main control board
has a fault, the system may still work normally. But the problem is that
master/slave changeover cannot be initiated when master main control
board has a fault. As a result, system reliability is reduced.
3-62
SJ-20120322151347-005|2012-04-15(R1.1)
Probable Cause
Handling Suggestion
Severity
System Impact

2. Service Impact:
Transmission power might be abnormal, affecting downlink service

quality.
Probable Cause
Handling Suggestion
power slightly
Severity
System Impact
Work normally.
2. Service Impact:
Because PA output is closed, this RF channel doesn't output

transmission power. As a result, all services borne on the board are
interrupted.
Probable Cause
Handling Suggestion
SJ-20120322151347-005|2012-04-15(R1.1)

3.109 198092280 Downlink digital power exceeds rated
power slightly
Severity
System Impact
Work normally.
2. Service Impact:
Because PA output is closed, this RF channel doesn't output

transmission power. As a result, all services borne on the board are
interrupted.
Probable Cause
Handling Suggestion
low
Severity
System Impact
Probable Cause
Handling Suggestion
3-64
SJ-20120322151347-005|2012-04-15(R1.1)
3.111 198092282 Downlink carrier analog power is low

Severity
System Impact
Probable Cause
Handling Suggestion
3.112
Severity
System Impact
Probable Cause
Handling Suggestion
(1). Check if RRU is connected to the antenna properly. Connect the

(2). Check if antenna feeder is properly connected. If there is any

(3). Verify that the connector of the antenna feeder is tightened

securely. Fasten the connector if the connection is loose.
2. Check the feeder standing waves of each level.
(1). Check if the standing wave of feeder is normal. Replace the feeder
if the standing wave is not normal.
(2). If combiner is connected to the feeder, check if the standing wave

of the combiner is normal. Replace it if the standing wave is not normal
(3). Check if the antenna is normal. Replace or repair it if there is any
3. Check the RRU for possible failure.
3-65
SJ-20120322151347-005|2012-04-15(R1.1)
(1). Reset the board.
(2). Check the RRU for the poor connection of the RF cable. Fasten
the cable or replace it if any loose or disconnection is found.
(3). Check the amplifier for possible failure. Replace the power
(4). Check the duplex for possible damage. Replace the duplex in
case of any damage.
(5). Replace the board.
3.113
Severity
System Impact
Probable Cause
Handling Suggestion
please handle it.
2. Open the version management function, check whether FS running

version is correct.
3. Reset the board.

5. Insert the board to another slot.
3.114 198092285 Internal clock is abnormal

Severity
System Impact
Work normally
System services are interrupted.
3-66
SJ-20120322151347-005|2012-04-15(R1.1)
Probable Cause
Handling Suggestion
version is correct.
2. Reset the FS board.
3. Remove and insert the FS board.
3.115 198092286 The uplink frame at optical/electric

port is unlocked
Severity
System Impact
Work normally
Board logic cannot parse frame data so that system services are
interrupted.
Probable Cause
Handling Suggestion
type. If yes, process this alarm.

2. Reset the RRU forcibly.
3. Check whether the optical fiber/electrical cable between BBU and

RRU is well connected.
4. Remove and insert the corresponding optical/electric module.

5. Replace the corresponding optical/electric module.
6. Use an optical power meter to measure the optical fiber. Check
whether the power value is less than -18dbm. If yes, please check
whether the RRU is powered on.
3.116 198092287 The channel downlink frame is

unlocked
Severity
SJ-20120322151347-005|2012-04-15(R1.1)

System Impact
Work normally
The board logic cannot parse baseband frame data so that services
are interrupted.
Probable Cause
2. The channel board works abnormally.

3. The link to backplane is interrupted.
4. The forward link on the board is interrupted.
5. The 50 chip clock on the board is abnormal.
6. The FSYNC frame on the board is wrong.
Handling Suggestion
2. Check whether there is a clock alarm on board or CH board. If yes,
please handle it.
3. Reset the corresponding channel board.

4. Remove and insert the corresponding channel board.
5. Reset the board.
3.117 198092288 The PLL clock is unlocked

Severity
System Impact
Work normally
The external clock cannot be locked by PLL so that services are

interrupted.
Probable Cause
Handling Suggestion
running version is correct.

2. Reset the board.

3-68
SJ-20120322151347-005|2012-04-15(R1.1)
3.118 198092289 The optical/electric module is not in

the position of optical port
Severity
System Impact
Work normally
Because the optical/electrical module is not tightly inserted, the

corresponding services are interrupted.
Probable Cause
Handling Suggestion
interrupted
Severity
System Impact
Probable Cause
2. Either optical/electric module or optical fiber/electric cable is not

well inserted.
3. The optical/electric module on the board is broken.

4. The optical/electric module at RRU side is broken.
3-69
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
type. If yes, process it.
3. Check whether the optical fiber/electrical cable between BBU and

RRU is well connected.

3.120
is wrong
Severity
System Impact
Probable Cause
problem.
2. The clock receiving circuit on the board has a problem.

3. Board internal logic is abnormal.
4. Backplane has a problem.
Handling Suggestion
please handle it.
2. Reset the board.
3.121 198092292 An alarm is given when an optical

fiber is wrongly connected
Severity
SJ-20120322151347-005|2012-04-15(R1.1)

System Impact
Probable Cause
Handling Suggestion
the corresponding connector is clean.
2. Check whether the corresponding RRU has an alarm. If yes, please

handle it.
3. Reset the corresponding RRU forcibly.

whether the power value is less than -18dbm. If yes, please check the
corresponding transmission link.
3.122 198092293 The Rx optical port at RRU has no

light signal.
Severity
System Impact
Probable Cause
Handling Suggestion
2. Check whether the fibers are inserted properly and the fiber plug
is clean.
3. Remove and insert the optical module corresponding to the board.

4. Replace the optical module. corresponding to the board.
5. Check whether the power of received light is less than -18dbm.
3.123 198092294 The frame transferred over Rx port of

RRU is unlocked.
is unlocked.
3-71
SJ-20120322151347-005|2012-04-15(R1.1)

Severity
System Impact
Probable Cause
Handling Suggestion
is clean.

3.124 198092295 RRU power-cut alarm

Severity
System Impact
Probable Cause
Handling Suggestion
3.125 198092298 MMC Fault

Severity
System Impact
Probable Cause
3-72
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
is correct in Version Management.
2. Check whether the MMC status is normal in Diagnose Management.

3. Reset the board.
4. Check whether the board is inserted properly.

3.126 198092311 IQ reported is failed
IQ.
Severity
System Impact
Probable Cause
Handling Suggestion
3.127 198092317 ACOM major alarm

Severity
System Impact
Probable Cause
Handling Suggestion
3.128 198092318 ACOM minor alarm

SJ-20120322151347-005|2012-04-15(R1.1)
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
interrupted.
Severity
System Impact
Probable Cause
2. The communication link between ACOM device and the system

has a problem.
3. TAC board fault.

4. EMC fault
Handling Suggestion
station and ensure the connection is proper and secure.
2. Reset the RRU board.
3. Replacement the equipment.
3-74
SJ-20120322151347-005|2012-04-15(R1.1)
3.131 198092321 ACOM software fault

Severity
System Impact
Probable Cause
Handling Suggestion
3.132 198092322 AISG EEPROM error

AISG device type:

RET 1
ATMA 2
ACOM 241
Severity
System Impact
Probable Cause
Handling Suggestion
3.133 198092323 AISG flash erase error

AISG device type:

RET 1
ATMA 2
ACOM 241
Severity
System Impact
Probable Cause
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
3.134 198092324 AISG flash error

AISG device type:

RET 1
ATMA 2
ACOM 241
Severity
System Impact
Probable Cause
Handling Suggestion
3.135 198092325 AISG other hardware error
AISG device type:

RET 1
ATMA 2
ACOM 241
Severity
System Impact
Probable Cause
Handling Suggestion
3-76
SJ-20120322151347-005|2012-04-15(R1.1)
3.136 198092326 AISG other software error

AISG device type:

RET 1
ATMA 2
ACOM 241
Severity
System Impact
Probable Cause
Handling Suggestion
3.137 198092327 AISG RAM error

AISG device type:

RET 1
ATMA 2
ACOM 241
Severity
System Impact
Probable Cause
Handling Suggestion
3.138 198092328 AISG UART error

AISG device type:

RET 1
ATMA 2
ACOM 241
Severity
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
Probable Cause
Handling Suggestion
3.139 198092330 ATMA major alarm

Severity
System Impact
Probable Cause
Handling Suggestion
3.140 198092331 ATMA minor alarm

Severity
System Impact
Probable Cause
Handling Suggestion
3.141 198092332 Failed to set gain

AISG device type:

RET 1
ATMA 2
ACOM 241
3-78
SJ-20120322151347-005|2012-04-15(R1.1)
Severity
System Impact

2. Service Impact:
ATMA(ACOM) gain is inconsistent with the database record value,

resulting in incorrect RSSI value reported to the background
Probable Cause
Handling Suggestion
configuration), check power gain configuration. If the configuration is

incorrect, please correct the configuration.
2. Reset equipment.
3. Replace equipment.
3.142 198092333 ATMA hardware fault

Severity
System Impact
Probable Cause
Handling Suggestion
interrupted.
Severity
System Impact
The system fails to communicate with ATMA device. If link interruption

is caused by device damage, performance of the corresponding cell
will be degraded.
3-79
SJ-20120322151347-005|2012-04-15(R1.1)
Probable Cause
2. The communication link between ATMA device and the system has
a problem.
3. TAC board fault.

4. EMC fault.
Handling Suggestion
base station and ensure the connection is proper and secure.
3.144 198092335 ATMA software fault

Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
SJ-20120322151347-005|2012-04-15(R1.1)
Severity
System Impact
Probable Cause
Handling Suggestion
AISC equipment centralized management, select automatic calibrate

the RET equipment again .
2. Remount the RET motor and automatically calibrate it.

3. Replace the RET motor.
3.147 198092339 RET hardware fault

Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion

the RET equipment again.
2. Remount the RET motor.
3-81
SJ-20120322151347-005|2012-04-15(R1.1)
3.149 198092341 RET motor don't respond the

adjusting command
Severity
System Impact
Probable Cause
Handling Suggestion


3.150 198092342 RET communication link is

interrupted.
Severity
System Impact
Probable Cause
2. The communication cable between RET device and the system has
a problem.
3. TAC board fault.

4. EMC fault.
Handling Suggestion
station and ensure the connection is proper and secure.

3-82
SJ-20120322151347-005|2012-04-15(R1.1)
3.151 198092343 RET don't calibrated

Severity
System Impact
Probable Cause
Handling Suggestion


3.152 198092344 RET data don't scaled

Severity
System Impact
Probable Cause
Handling Suggestion
AISC equipment centralized management, select send the configuration

data for the RET equipment again.
2. Replace the motor.
3.153 198092345 RET position lost

Severity
System Impact
Probable Cause
SJ-20120322151347-005|2012-04-15(R1.1)

Handling Suggestion
2. Remount the motor and calibrate it automatically.

3. Replace the motor.
3.154 198092346 RET software fault

Severity
System Impact
Probable Cause
Handling Suggestion
electrical port of Ethernet

Severity
System Impact

Data packets transmitted via the Electrical Ethernet port may be lost.
This may lead to interrupted services.
Probable Cause
that connected to local base station.
Handling Suggestion
interface, check the configured working mode of electrical port at local

end and peer end. If the configuration is inconsistent, change the
local-end configuration to keep consistency.
3-84
SJ-20120322151347-005|2012-04-15(R1.1)
3.156 198092353 Configuration is failed.

Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Work normally
Situation 1: If non-RRU board reports this alarm, the system can work
properly for a while. But if this situation lasts for a long term, the system
must be lack of electricity.
Situation 2: If RRU reports this alarm, the system will automatically

close the relevant PA. As a result, services borne on the RRU are
interrupted.
Probable Cause
Handling Suggestion
3.158 198092364 Calibrate Fail
Severity
System Impact
Probable Cause
Handling Suggestion
and etc, If so, auto-calibrate after these alarms are processed.

2. Check the radio configuration data is complete and right.
3. Test if there exists hardware issue, if so, Replace it.
3-85
SJ-20120322151347-005|2012-04-15(R1.1)
3.159 198092365 Low Power Exception

Severity
System Impact
Probable Cause
Handling Suggestion
2. Check whether it exists PA disable alarm.

3. Check whether it exists alarm of calibrate alarm.
4. Check whether control word is normal, if not, do calibration again.
5. Change RRU.
3.160 198092374 UCI optical module of optical port is

out of position.
Severity
System Impact
Probable Cause
Handling Suggestion
no light signal.
Severity
System Impact
SJ-20120322151347-005|2012-04-15(R1.1)
Probable Cause
Handling Suggestion
is clean.

4. Replace the optical module corresponding to the board.
5. Check whether the power of received light is less than -18dbm or
the RGPS is powered on.
3.162 198092376 UCI receiver frame at optical port is

unlocked.
Severity
System Impact
Probable Cause
Handling Suggestion
is clean.

4. Replace the optical module corresponding to the board.
5. Check whether the power of received light is less than -18dbm,if less
than -18dbm please check the fibers link.
3.163 198092377 UCI fiber delay adjust is failed

Severity
System Impact
Probable Cause
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
2. Check whether UCI board is normal.
3.164 198092378 Board PLL is unlocked.

Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
PA.
2. TRx board is abnormal, which causes very high input power of PA.
3. RDM hasn't been calibrated, which causes very high input power of
PA.
4. PA has its own fault.
Handling Suggestion
Severity
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
speed.
Severity
System Impact
Probable Cause
Handling Suggestion
3-89
SJ-20120322151347-005|2012-04-15(R1.1)
3.169 198092386 It is failed to configurate TDM port

speed.
Severity
System Impact
Probable Cause
Handling Suggestion
delay parameter.
Severity
System Impact
Probable Cause
Handling Suggestion
supply.
Severity
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
3-91
SJ-20120322151347-005|2012-04-15(R1.1)
3.174 198092400 Board smart powered-down

Severity
System Impact
Probable Cause
Handling Suggestion
3.175 198092401 E1 link self-loop

Severity
System Impact

2. Service Impact:
Self-loop forms at the E1 physical interface of the board, which affects

communication.
Probable Cause
Handling Suggestion
Severity
System Impact
Work normally
2. Impact on services:
Board process capability is reduced. Partial functions cannot be

provided properly. In serious situation, this may cause service failure,
for example, radio link setup failure.
3-92
SJ-20120322151347-005|2012-04-15(R1.1)
Probable Cause
Handling Suggestion
(1) Check the connection of GNSS antenna feeder.

(2) Make tight connection or replace antenna feeder.
3.177 198092415 The built-in-type GNSS receiver has

an alarm.
Severity
System Impact
Work normally
2.Impact on services:
Board process capability is reduced. As a result, partial functions may

not work properly. In serious situation, some services may not be
provided, for example RL setup may fail.
Probable Cause
Handling Suggestion
(1) Reset the board.

3.178 198092416 The built-in-type GNSS antenna has a

feeder cable alarm
Severity
System Impact
Work normally

Probable Cause
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion

(2) Reconnect or replace the GNSS antenna feeder.
3.179 198092418 The external-panel-type GNSS

receiver has an alarm.
the configuration of external-panel-type GNSS reference source.

(1) RGPS receiver has no electricity supply.
(2) The receiver is faulty or the link to the external-panel-type GNSS

receiver is interrupted.
(3) The environmental temperature of RGPS receiver is abnormal.
Severity
System Impact
Work normally

Probable Cause
2. The receiver is broken, or the link between external-panel-type

receiver and CC board is interrupted or disconnected.
3. Environmental temperature exceeds the threshold or the temperature
sensor is faulty.
Handling Suggestion
problem.
2. Check whether the link between external-panel-type GNSS receiver

and CC is normal.
3. Check whether environmental temperature is normal (for example,

is there any high-heat large-power device?)

antenna has a feeder cable alarm.
Severity
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
Work normally

Probable Cause
Handling Suggestion

receiver has an alarm, indicating its foreground
working mode is inconsistent with background.
Severity
System Impact
Probable Cause
Handling Suggestion
CC is in normal state.
2. Check whether USR or UCI antenna feeder is well connected,

mushroom head is in normal state.
3. Check whether USR or UCI board works normally.
3.182 198092422 The external-backplane-type GNSS

receiver has an alarm.
the configuration of external-backplane-type GNSS reference source.

(1) RGPS receiver has no electricity supply.
(2) The receiver is faulty or the link to the external-backplane-type

GNSS receiver is interrupted.
(3) The environmental temperature of RGPS receiver is abnormal.
3-95
SJ-20120322151347-005|2012-04-15(R1.1)
Severity
System Impact
Work normally

Probable Cause
2. The receiver is broken, or the link between external-backplane-type

receiver and CC board is interrupted or disconnected.
3. Environmental temperature exceeds threshold or temperature
sensor is faulty.
Handling Suggestion
problem and supply power to it.
2. Check whether the link between external-backplane-type GNSS

receiver and CC is normal.
3. Check whether environmental temperature is normal (for example,

is there any high-heat large-power device?)

antenna has a feeder cable alarm.
Severity
System Impact
Work normally

Probable Cause
Handling Suggestion
3-96
SJ-20120322151347-005|2012-04-15(R1.1)

receiver has an alarm, indicating its foreground
working mode is inconsistent with background.
Severity
System Impact
Probable Cause
Handling Suggestion
CC is in normal state.
2. Check whether USR or UCI antenna feeder is well connected,

mushroom head is in normal state.
3. Check whether USR or UCI board works normally.
3.185
Severity
System Impact
Work normally

Probable Cause
this-level board through a channel.
2. The previous-level board fails to search satellites for several

reasons, for example, antenna feeder is in short circuit or the number of
searched satellites doesn't reach minimum requirement.
Handling Suggestion
2. Check the antenna status of previous-level board. Check whether

it can search satellites properly.
3. Reset the board.
3-97
SJ-20120322151347-005|2012-04-15(R1.1)

3.186 198092433 RRU network interrupted alarm
Severity
System Impact
Probable Cause
Handling Suggestion
is clean.

3.187 198092434 Clock line abnormal connection in

stack mode
Severity
System Impact
Probable Cause
Handling Suggestion
stack mode
Severity
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
Probable Cause
Handling Suggestion
2. Replace ETH1 line.
3. Check the configuration of both ends and make sure network port
modes are the same.
3.189 198092436 Loss of clock synchronization at

slave frame
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Work normally.
The corresponding channel is unavailable.
3-99
SJ-20120322151347-005|2012-04-15(R1.1)
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
-25℃). If yes, do nothing.

2. Remove and insert SA board.
3. Replace SA board.
3.192 198092439 Uplink transport port of a base station

operates in a different mode from configured one.
Severity
System Impact
Work normally
(1).Link mode configured by network management system isn't

executed. This may cause half-duplex working mode and loss of
service packets.
(2).The configured output rate restraint by network management

system doesn't take effect.
3-100
SJ-20120322151347-005|2012-04-15(R1.1)
Probable Cause
time.
Handling Suggestion
2. Configure correct link mode at local end so that the link stays in
full-duplex status.
3.193 198092447 Unbalanced AC phase voltage of

built-in power
Severity
System Impact
Probable Cause
Handling Suggestion
power
Severity
System Impact
be over high. This may cause air switch at AC input to be opened.

2.AC input return circuit works in high temperature. This accelerates
cable aging.
3.It affects power supply to a base station.
Probable Cause
indicate AC phase over-current alarm.

2.Power is over-loaded.
3.The monitoring unit used socket is poorly connected or its used cable
is broken.
4.The monitoring unit is broken.
3-101
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
2.Check whether AC input voltage is very low.

3.Check whether AC power is over-loaded.
4.Check whether the monitoring unit used socket is well connected and
its cable is in good status.
5.Replace the monitoring unit.
3.195 198092449 Missing AC phase voltage of built-in

power
Severity
System Impact
Probable Cause
2.AC transducer is not well connected or broken.
3.The monitoring unit used socket is not well connected or its cable is
broken.
Handling Suggestion
2.Check whether AC transducer is well connected and transducer

detection function is correct.
3.Check whether the monitoring unit used socket is well connected or

its cable is broken.
3.196 198092450 Battery low-voltage cut-off of built-in

power
Severity
System Impact
3-102
SJ-20120322151347-005|2012-04-15(R1.1)
Probable Cause
2.System temperature is higher than high-temperature cut-off threshold.

3.Battery's voltage reduces to be lower than low-voltage cut-off
threshold.
4.Battery's capacity reduces to be lower than low-capacity cut-off

threshold.
5.Power-cut time length reaches cut-off tolerant time threshold.

6.Battery's temperature sensor is broken.
7.The monitoring unit used socket is poorly connected or its cable is

broken.
Handling Suggestion
2.Check settings of the monitoring unit, for example, whether

"low-temperature cut-off threshold" and "high-temperature cut-off
threshold" are reasonable.
3.Check whether battery's voltage is lower than low-voltage cut-off

threshold.
4.Check whether low-voltage cut-off threshold configured for the

monitoring unit is reasonable.
5.Check whether the displayed capacity of the battery group is lower

than low-capacity cut-off threshold.
6.Check whether battery's temperature sensor is broken.

7.Check whether the monitoring unit used socket is poorly connected
or its cable is broken.
3.197 198092451 Broken LLVD1 branch E of built-in

power
Severity
System Impact
3-103
SJ-20120322151347-005|2012-04-15(R1.1)
Probable Cause
system takes LLVD1 action.
2.The configured "LLVD1 voltage" of the monitoring unit is

unreasonable.
3.Manual cut-off switch is in wrong state.

4.DC contactor connection is wrong.
5.DC contactor is broken.
6.SDCB board is broken.

Handling Suggestion
2.Check whether the configured "LLVD1 voltage" of the monitoring
unit is reasonable.
3.Check whether manual power-cut switch is in the state of "auto"or

"connected".
4.Check whether LLVD1 DC contactor is broken, the measured voltage

of both ends is 48V, DC contactor cable is fell off or broken.
5.Check the connections of DC contactor.
7.If SDCB board (hardware power-cut board) is configured, please

check whether cut-off action is caused by SDCB's fault.
3.198 198092452 Broken LLVD1 branch of built-in

power
Severity
System Impact
Probable Cause

unreasonable.


3-104
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
unit is reasonable.

"connected".

3.199 198092453 Broken LLVD2 branch E of built-in

power
Severity
System Impact
Probable Cause

unreasonable.


Handling Suggestion
unit is reasonable.

"connected".


3-105
SJ-20120322151347-005|2012-04-15(R1.1)
3.200 198092454 Broken battery cut-off branch E of

built-in power
Severity
System Impact
Probable Cause

threshold.

threshold.


broken.
Handling Suggestion


threshold.



3.201 198092455 Broken battery cut-off branch of

built-in power
Severity
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
supplied with power.

Probable Cause

threshold.

threshold.


broken.
Handling Suggestion


threshold.




3.202 198092456 Abnormal battery current of built-in
power
Severity
System Impact
Probable Cause
Handling Suggestion
SJ-20120322151347-005|2012-04-15(R1.1)
3.203 198092457 Abnormal CAN bus of built-in power

Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
power
Severity
System Impact
Probable Cause
Handling Suggestion
3-108
SJ-20120322151347-005|2012-04-15(R1.1)
3.206 198092460 High-temperature cut-off of built-in

power
Severity
System Impact
Probable Cause

broken.
Handling Suggestion
2.Check whether the configured "high-temperature cut-off threshold" of

the monitoring unit is reasonable.

3.207 198092461 BBU inter-subrack frame

synchronization failure alarm
Severity
System Impact
Inter-subrack service may not work properly.

Inter-subrack IQ data is abnormally accumulated and inter-subrack

Probable Cause
cannot meet the requirement for sharing inter-subrack IQ data.
Handling Suggestion
connected.
2. In stack configuration, replace the clock cable.
3. Check whether the IQ optical fiber between subracks is too long.

4. Cancel inter-subrack services.
3-109
SJ-20120322151347-005|2012-04-15(R1.1)

Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
devices.
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
Probable Cause
Handling Suggestion
devices.
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
3-112
SJ-20120322151347-005|2012-04-15(R1.1)

Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
devices.
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
Probable Cause
Handling Suggestion
devices.
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
3-115
SJ-20120322151347-005|2012-04-15(R1.1)

Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
devices.
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
Probable Cause
Handling Suggestion
devices.
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
3-118
SJ-20120322151347-005|2012-04-15(R1.1)

Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
devices.
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
Probable Cause
Handling Suggestion
devices.
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
3-121
SJ-20120322151347-005|2012-04-15(R1.1)

Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
devices.
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
Probable Cause
Handling Suggestion
devices.
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
3-124
SJ-20120322151347-005|2012-04-15(R1.1)

Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
devices.
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
Probable Cause
Handling Suggestion
devices.
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
3-127
SJ-20120322151347-005|2012-04-15(R1.1)

Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
SJ-20120322151347-005|2012-04-15(R1.1)
3.259 198094828 The board is unavailable

Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
3-129
SJ-20120322151347-005|2012-04-15(R1.1)
3.262 198096551 RRU unconfigured

Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
Check downlink fiber time delay of each RRU in the sector(for example,
R08i and R11 cannot be configured in the same sector).
2. Check the distance between 2 RRUs in the sector, the longest
distance should be less than 10km.
3.264 198096553 RRU Type is not consistent with
configuration type
Severity
System Impact
Probable Cause
Handling Suggestion
SJ-20120322151347-005|2012-04-15(R1.1)
3.265 198096554 Failure of optical decoding in BBU

Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
transmitting and receiving is normal.

2. Reset RRU.
3. Replace board.
3.267 198096556 IQ link input loses lock

Severity
System Impact
Probable Cause
Handling Suggestion
normal.
2. if it is normal, reset board.

3. Replace board.
3-131
SJ-20120322151347-005|2012-04-15(R1.1)
3.268 198096558 Downlink baseband power abnormal

Severity
System Impact
Probable Cause
Handling Suggestion
RRU is too high or too low

Severity
System Impact
Probable Cause
Handling Suggestion
fault.
Severity
System Impact
Probable Cause
Handling Suggestion
SJ-20120322151347-005|2012-04-15(R1.1)
3.271 198096560 Master and slave monitor link alarm

Severity
System Impact
Probable Cause
Handling Suggestion
2.Replace RRU.
3.Replace the communication cable of 485.

4.Configurate master/slave RRU sector
3.272 198096561 Coherence alarm of antenna channel

swing and phase
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
2. Channel DAC clock lose lock;
3. Channel DUC/DDC time sequence abnormal;

4. Channel ADC init failure;
5. DSP of RRU is abnormal.
Handling Suggestion
SJ-20120322151347-005|2012-04-15(R1.1)
3.274 198096563 RRU device alarm

Severity
System Impact
Probable Cause
Handling Suggestion
2. Check if offline parameter in eeprom is normal.

3. Replace RRU.
3.275 198096565 Configuration parameter of RRU

external device not consistent with real parameter
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
3-134
SJ-20120322151347-005|2012-04-15(R1.1)
3.277 198096569 RRU offline parameter check failure

Severity
System Impact
Probable Cause
Handling Suggestion
3.278
port exceeds its upper working limit configured at background, or the

value of channel current exceeds NSBT maximum current.
2. An under-current alarm is reported when the current value at NSBT
port is smaller than its lower working limit configured at background.
Severity
System Impact
Probable Cause
working limit of a tower mounted amplifier.

2. The equipment is faulty.
(1). Either RET antenna or a tower mounted amplifier has too large
leakage current.
(2). An antenna is broken.
(3). At end of the antenna feeder, a connector is not tightly connected.

(4). Board hardware circuit is broken.
3-135
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
configured, either too low or too high?
Y=> If the threshold is wrongly configured, change it and wait for 30

seconds. Check whether the alarm disappears. If yes, the alarm
process ends. if not, go to step 2.
N=> If the threshold is correctly configured, go to step 2.

2. Check all connections of the antenna system. For example, is feeder
connector screwed down tightly or is there any short circuit? After
checking, wait for 30 seconds and check whether the alarm disappears.
Y=> If yes, the alarm process ends.
N=> If not, go to step 3.
3. Record alarm information and contact with ZTE.
3.279 198098432 AISG/NSBT port turn-off alarm due

to over current
Severity
System Impact
Probable Cause
Handling Suggestion
inconsistent with the working voltage of the connected tower mounted

amplifier or AISG device.
Y=> If the voltage is wrongly configured, change it and wait for 60

seconds. Check whether the alarm disappears. If yes, the alarm
process ends. if not, go to step 2.
N=> If the voltage is correctly configured, go to step 2.

2. Check all connections of the antenna system. For example, is the
feeder connector screwed down tightly or is there any short circuit?
After checking, wait for 30 seconds and check whether the alarm
disappears.
Y=> If yes, the alarm process ends.

N=> If not, go to step 3.
3. Record alarm information and contact with ZTE.
3-136
SJ-20120322151347-005|2012-04-15(R1.1)
3.280 198098434 Abnormal transmission power at

antenna port
Severity
System Impact
Probable Cause
Handling Suggestion
2. Check whether PA works normally.
3. Check whether the physical link between PA and duplexer is normal.
3.281198098435 Closed-loop power control adjustment

exceeding normal range
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
Probable Cause
Handling Suggestion
3-138
SJ-20120322151347-005|2012-04-15(R1.1)
Chapter 4
Environment Alarm
Table of Contents
198092429 Board powered-down alarm because of high temperature

198092462 Differential pressure alarm
198092037 MP voltage abnormal
198092038 PP voltage abnormal
198092039 Over current of MP
198092040 Over current of PP
198092041 Fan failure
198092042 Abnormal temperature at air intake
198092043 Abnormal temperature at air outlet
198092044 Door control alarm
198092045 Flooding alarm
198092046 Smog alarm
198092047 Infrared alarm
198092048 Air conditioner fault
198092053 Voltage of DC input is abnormal
198092069 FCE-fan failure
198092105 Embedded power Environment is under-temperature
198092106 Embedded power Environment is over-temperature
198092107 Embedded power Environment temperature is invalid
198092108 Embedded power Environment is under-Humidity
198092109 Embedded power Environment is over-Humidity
198092110 Embedded power Environment humidity is invalid
198092111 Embedded power Smoke detected
198092112 Embedded power Flood detected
198092113 Embedded power Door Magnet Alarm
198092114 Embedded power Gate Embedded power Safety Alarm
198092115 Glass Broken Alarm
198092118 Embedded power Env-unit communication interruption
198092119 Embedded power Heat Exchanger Fault
198092213 Board temperature abnormal alarm
198092307 Slight-high temperature of board
198092308 Over-high temperature of board
198092371 CCM Remote MEP Error
198092372 CCM Message Error
198092373 CCM Xconnect Error
4-1
SJ-20120322151347-005|2012-04-15(R1.1)
4.1 198092429 Board powered-down alarm because

of high temperature
Severity
System Impact
The board is faulty

The board is powered down. All services borne on the board are
interrupted.
Probable Cause
limit.
Handling Suggestion
2. Check whether the fan runs normally.
3. Check surrounding environment, e.g. does air conditioner work

normally? are there any high heat and power devices?
4.2 198092462 Differential pressure alarm

Severity
System Impact
Work normally
Cables may be stolen and water may enter the cabinet. Both may
cause reduced service performance, even service interruption.
Probable Cause
contact alarm is wrongly configured. Note that there are two kinds of
status: normally closed, normally open.
2. The top cover of the cabinet is not closed.

Handling Suggestion
2. Replace the cable that is connected to the differential pressure

sensor.
4-2
SJ-20120322151347-005|2012-04-15(R1.1)
4.3 198092037 MP voltage abnormal

Severity
System Impact
Probable Cause
threshold, it is over-voltage, and will restore when the voltage is lower

than the upper threshold.
2. When the MP voltage reported by PM/PSA board is lower than the

lower threshold, it is under-voltage, and will restore when the voltage
exceeds the lower threshold.
Handling Suggestion
Severity
System Impact
Probable Cause
threshold, it is over-voltage, and will restore when the voltage is lower

than the upper threshold.
2. When the PP voltage reported by PM/PSA board is lower than the

lower threshold, it is under-voltage, and will restore when the voltage
exceeds the lower threshold.
Handling Suggestion
2. Replace the PM/PSA board.
4.5 198092039 Over current of MP

Severity
System Impact

2. Service Impact:
The power to the over-current board is turn off and the services
provided by this board is completely interrupted.
4-3
SJ-20120322151347-005|2012-04-15(R1.1)
Probable Cause
Handling Suggestion
2. Replace the corresponding board.

3. Replace PM board.
4. Replace the backplane.
4.6 198092040 Over current of PP

Severity
System Impact

2. Service Impact:
The power to the over-current board is turn off and the services
provided by this board is completely interrupted.
Probable Cause
Handling Suggestion
2. Replace the corresponding board.

3. Replace PM board.
4. Replace the backplane.
4.7 198092041 Fan failure

Severity
System Impact

2. Service Impact:
The equipment temperature may become over high which may cause
the board of the system to work improperly.
Probable Cause
Handling Suggestion
4-4
SJ-20120322151347-005|2012-04-15(R1.1)
4.8
Severity
System Impact
Work normally
Either the board or the system may not work properly. Consequently,
service performance is worsen or services may even be interrupted.
Probable Cause
1. The dustproof net is blocked.
2. The air conditioner is faulty.
3. The heat exchanger is faulty.
4. Wrong threshold is configured.
In the case of low temperature at air outlet:
1. The environmental temperature is lower than the configured lower

limit.
Handling Suggestion
1. Wash and clean the dustproof net.
2. Check whether the air conditioner works properly. Make sure it

works normally.
3. Check whether the heat exchanger is faulty. If yes, please handle it

according to relevant heat exchanger manual.
4. Check whether the upper limit of configured environmental

temperature is 50℃. If not, please correct it.
6. Replace the fan subrack.

7. Replace the SA board.
In the case of high temperate at air intake:
1. Check whether the environmental temperature is lower than -25℃. If

yes, do nothing.
2. Replace the heat exchanger.
3. Check whether the lower limit of configured environmental

temperature is -25℃. If not, please correct it.
5. Replace the fan subrack.

6. Replace the SA board.
4-5
SJ-20120322151347-005|2012-04-15(R1.1)
4.9
Severity
System Impact
Work normally
II. Impact on Services:
Either the board or the system may not work properly. Consequently,
service performance is worsen or services may even be interrupted.
Probable Cause
1. The dustproof net is blocked.
2. The environmental temperature is out of normal working range.

In the case of low temperature at air outlet:
The environment temperature is lower than acceptable working

temperature.
Handling Suggestion
1. Wash and clean the dustproof net.
2. Check whether the air conditioner works properly. Make sure it

works normally.
In the case of high temperaute at air intake:
1. Check whether the envirnmental temperature is lower than -25℃. If

yes, do nothing.
2. Remove and insert SA/PSA board.

3. Replace SA/PSA board.
4.10 198092044 Door control alarm

Severity
System Impact
Work normally
Cables are probably stolen or water may enter the device. These may
cause reduced service performance or even service interruption.
Probable Cause
2. The door is not closed.
4-6
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
4.11
Severity
System Impact
Work normally
The board or system may not work properly. As a result, services borne
on the board are interrupted.
Probable Cause
of status: normally closed, normally open..
2. The base station is flooded.

Handling Suggestion
base station and drain water. Do not power on the device unless it
becomes completely dry.
2. Replace the flooding sensor.

4.12 198092046 Smog alarm

Severity
System Impact
Work normally
No impact
4-7
SJ-20120322151347-005|2012-04-15(R1.1)
Probable Cause
2. The base station detects smog.

Handling Suggestion
off the base station and locate the problem. Do not power on the device
unless the problem is completely solved.
2. Replace the smog sensor.
3. Reset the board.
4.13 198092047 Infrared alarm

Severity
System Impact
Probable Cause
2. Someone enters the equipment room.

Handling Suggestion
Severity
4-8
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
Work normally
This may cause other alarms such as device high temperature alarm,
whole-set temperature rise alarm, or the board or system may not work
properly. The high temperature rise may further cause reduced service
performance and even service interruption.
Probable Cause
2. The air conditioner is faulty.
Handling Suggestion
2. Replace the air conditioner.
4.15
Severity
System Impact
Probable Cause
Handling Suggestion
higher than or equal to over-voltage threshold by multimeter or other

tools. Replace the DC supply system if so. Replace the power board
PM if not.
Under-voltage: Check whether the input voltage of DC supply system

is lower than under-voltage threshold by multimeter or other tools.
Replace the DC supply system if so. Replace the power board PM if
not.
4.16 198092069 FCE-fan failure

SJ-20120322151347-005|2012-04-15(R1.1)
Severity
System Impact

2. Service Impact:
The equipment temperature may become over high which may cause
the board of the system to work improperly.
Probable Cause
Handling Suggestion
under-temperature.
Severity
System Impact
Probable Cause
Handling Suggestion
equipment room condition.
2. Appropriately adjust the threshold value for alarm.

4.18 198092106 Embedded power Environment is

over-temperature.
Severity
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
Probable Cause
for alarm.
Handling Suggestion


4.19 198092107 Embedded power Environment

temperature is invalid.
Severity
System Impact
Probable Cause
in the detection.
2. The temperature sensor is damaged.
3. The temperature sensor is not connected.
4. The AC transducer or the monitoring unit is damaged.
Handling Suggestion
2. Check whether the temperature sensor is connected reliably.


4-11
SJ-20120322151347-005|2012-04-15(R1.1)

under-Humidity.
Severity
System Impact
Probable Cause
Handling Suggestion

3. Replace the humidity sensor.

over-Humidity.
Severity
System Impact
Probable Cause
Handling Suggestion


4-12
SJ-20120322151347-005|2012-04-15(R1.1)
4.22 198092110 Embedded power Environment

humidity is invalid.
Severity
System Impact
Probable Cause
the detection.
2. The humidity sensor is damaged.

3. The humidity sensor is not connected.
Handling Suggestion
2. Check whether the humidity sensor is connected reliably.


4.23 198092111 Embedded power Smoke detected

Severity
System Impact
Probable Cause
Handling Suggestion
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.

4.24 198092112 Embedded power Flood detected

Severity
System Impact
SJ-20120322151347-005|2012-04-15(R1.1)
Probable Cause
2. The sensor is damaged.
Handling Suggestion
2. Replace the sensor.
Severity
System Impact
Probable Cause
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 cannot be attracted normally after the door is closed.
Handling Suggestion
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.

4.26 198092114 Embedded power Gate Embedded
power Safety Alarm
Severity
System Impact
Probable Cause
3. The door status switch is not installed appropriately, that is, the door
status switch can not be attracted normally after the door is closed.
4-14
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
2. Check whether the door status switch is installed correctly, and

whether the switch can be attracted normally after the door is closed.
3. Replace the door-status-switch sensor.
4.27 198092115 Glass Broken Alarm

Severity
System Impact
Probable Cause
Handling Suggestion
2. Replace the sensor.
4.28 198092118 Embedded power Env-unit

communication interruption
Severity
System Impact
Probable Cause
board, but the monitoring unit indicates that the environment monitoring
board is configured.
2. The communication cable of the environment monitoring board is

disconnected.
3. The monitoring unit or the environment monitoring board is damaged.

Handling Suggestion
actual configuration.
2. Check the communication cable of the environment monitoring

board.

disconnected.
4. Replace the environment monitoring board or the monitoring unit.
4-15
SJ-20120322151347-005|2012-04-15(R1.1)
4.29198092119 Embedded power Heat Exchanger Fault

Severity
System Impact
Probable Cause
Handling Suggestion
disconnected.
2. Check whether the heat exchanger is damaged or the temperature is

beyond the allowed range.
3. Replace the heat exchanger.

4.30 198092213 Board temperature abnormal alarm

Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Work normally
Services borne on the board are not interrupted.
4-16
SJ-20120322151347-005|2012-04-15(R1.1)
Probable Cause
Handling Suggestion

4.32 198092308 Over-high temperature of board

Severity
System Impact
Probable Cause
Handling Suggestion

4.33 198092371 CCM Remote MEP Error

Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
SJ-20120322151347-005|2012-04-15(R1.1)
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
4-18
SJ-20120322151347-005|2012-04-15(R1.1)
Chapter 5 Alarm
Processing
Table of Contents
198094815
198096567
198092010
198092014
198092016
198092017
198092019
198092022
198092024
198092025
198092027
198092029
198092030
198092060
198092066
198092070
198092309
198092310
198092347
198092348
198092360
198092366
198092390
198092391
198092395
198092396
198092397
198092398
198092403
198092404
198092405
198092406
198092407
198092408
198092412
198092413
198092414
SJ-20120322151347-005|2012-04-15(R1.1)
198092430 Optical module rate does not match
198094811 Cell Setup Failure

198094812 Cell Reconfiguration Failure
198094813 Parament Configuration Error
Unavailable
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact

II. Service Impact:
The board fails to communicate with the master CC board, leading

to interruption of board services.
Probable Cause
2. The link between this board and master CC board is faulty.
Handling Suggestion
is proper.
2. Insert the configured board to the correct slot.

3. If board self-link is broken, reset the board.
5.4 198092014 SNTP time adjustment failure alarm

Severity
System Impact
Probable Cause
Handling Suggestion
2. Stop Windows Time service on SNTP server. then change server

starting mode to be manual mode.
3. Close Windows firewall on SNTP server.
4. Check network quality between a network element and SNTP server.

5. Select SNTP-forced Time Adjustment.
5.5 198092016 Clock reference source configuration

error
Severity
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact

2. Service Impact:
The services borne on the board may have low performance. In serious
situation, the services may be interrupted.
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
running specification package again.

5.7 198092019 Failure in synchronizing the version of

master board with slave board.
Severity
5-4
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
Work normally
Situation 1: If without master/slave changeover, services are not

affected. But system reliability is reduced because the system cannot
provide master/slave changeover function.
Situation 2: If master/slave changeover happens, the software related

boards may not work properly. As a result, all services borne on the
board are interrupted.
Probable Cause
Handling Suggestion
Severity
System Impact
The board fails to obtain version. Except for hot patch and MMC
version, the board cannot boot normally if the relevant software is
missing.
Except for hot patch and MMC version, the board cannot work properly
if the relevant software is missing. And all services borne on the board
are interrupted.
Probable Cause
Handling Suggestion
version package again.
5.9 198092024 DOM is lack of space
Severity
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
in BIN directory.
2. Replace the slave board.
5.11 198092027 Failure in repairing specification

package
Severity
5-6
SJ-20120322151347-005|2012-04-15(R1.1)

System Impact
Work normally
Even though the booting is successful, all prepheral boards cannot

boot, so no services can be borne.
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
configuratin.
2. Remove the wrong board and insert a correct board.

3. If this alarm cannot be recovered automatically after removing the
board, an operator needs to delete the board configuration manually.
5.13 198092030 Abnormal software in specification

package
Severity
5-7
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
corresponding board cannot be powered on after reset.

2. If a specification package has an abnormal file, it cannot be activated
or handed over.
3. If running specification package or its running patch is abnormal,

services may be affected after reset. The severity depends on its
importance. If it is other specification package, services are not
affected.
Probable Cause
Handling Suggestion
specification package.
5.14 198092060 LMT login alarm

Severity
System Impact
Probable Cause
Handling Suggestion
software
Severity
System Impact
Probable Cause
Handling Suggestion
5-8
SJ-20120322151347-005|2012-04-15(R1.1)
5.16 198092070 Board software fault

Severity
System Impact
Work normally
II. Impact on Services:
Even though the booting is successful, all peripheral boards cannot

Probable Cause
version.
2. The board has a hardware fault.
Handling Suggestion
start this running specification package again.
Severity
System Impact

2. Service Impact:
System clock enters free oscillation state, which affects services in

the following ways:
(1). Iub interface: If Iub adopts E1, code-sliding happens periodically at

Iub interface. If Iub adopts FE, there is no influence.
(2). Inter-Base station soft handover: An alarm cannot be recovered for

a long time. The possible reason is base station clock accuracy cannot
meet 3GPP requirement due to aging problem. Consequently, soft
handover success rate is reduced.
Probable Cause
2. External reference clock and cable are faulty.

4. Single board is faulty.
5-9
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
2. Check whether external reference source is normal. Find the

external device, which outputs reference clock. Check whether the
clock is unlocked.
3. Check whether synchronous network clock is normal. Check whether

external transmission device is properly connected and configured.
5. Inform the responsible transmission engineer to check whether

external transmission device works properly.
6. Replace single board.
5.18
Severity
System Impact

2. Service Impact:
System clock enters free oscillation state, which affects services in

the following ways:
(1). Iub interface: If Iub adopts E1, code-sliding happens periodically at

Iub interface. If Iub adopts FE, there is no influence.
(2). Inter-Base station soft handover: An alarm cannot be recovered for

a long time. The possible reason is base station clock accuracy cannot
meet 3GPP requirement due to aging problem. Consequently, soft
handover success rate is reduced.
Probable Cause
2. External reference clock and cable are faulty.

4. SSM is lost.
5. Single board is faulty.
5-10
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
2. Check whether external reference source is normal. Find the

external device, which outputs reference clock. Check whether the
clock is unlocked.
3. Check whether synchronous network clock is normal. Check whether
external transmission device is properly connected and configured.
4. If SSM is enabled, find the external device, which outputs reference
clock. Check whether it transmits SSM.
6. Inform the responsible transmission engineer to check whether

external transmission device works properly.
7. Replace single board.
5.19 198092347 The fan control policy is not existed

Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
necessary.
Severity
System Impact
Probable Cause
Handling Suggestion
5.22 198092366 Configuration Fail
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact

2. Service Impact:
Board processing capability declines, probably leading to radio link

or service establishment failure.
Probable Cause
5-12
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
5.24 198092391 CPU over loading

Severity
System Impact

2. Service Impact:
Board processing capability declines, probably leading to radio link

or service establishment failure.
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact

2. Service Impact:
The board software update fails and the services provided by this board
is completely interrupted.
Probable Cause
board, is incorrect.
Handling Suggestion
management interface of OMCB.

2. Reset the board.
5.27 198092397 Failure in finding this board-related

software ID
Severity
System Impact
Single board cannot get version software. Except for hot patch and
MMC version, other software is missing. As a result, the corresponding
board fails to boot.
Except for hot patch and MMC version, other software is missing.
Consequently, single board cannot work properly and all services borne
on the board are interrupted.
Probable Cause
2. The alarming board has a hardware fault.
Handling Suggestion
XXX.temp, please download it again from NMS by means of software

version management function. Otherwise, you must activate it.
2. Reset the faulty board.
3. Replace the faulty board.
5-14
SJ-20120322151347-005|2012-04-15(R1.1)
5.28 198092398 MMC running software version doesn't

exist.
Severity
System Impact
The board cannot obtain the relevant software version. As a result, it

cannot boot normally after reset.
The board cannot work properly, so all services borne on the board
are interrupted.
Probable Cause
(no associated SWID)

Handling Suggestion
Severity
System Impact
work normally
The faulty frequency are associated to some services. Those services

are interrupted.
Probable Cause
frequency or duplex.
Handling Suggestion
5-15
SJ-20120322151347-005|2012-04-15(R1.1)
5.30 198092404 Center frequency configuration error

Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
5-16
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
work normally
The faulty frequency are associated to some services. Those services

are interrupted.
Probable Cause
Handling Suggestion
5-17
SJ-20120322151347-005|2012-04-15(R1.1)

5.35
Severity
System Impact
Because 1PPS+TOD signal cannot be properly obtained, board clock

may run abnormally.
Clock synchronization and frame synchronization cannot be

guaranteed. This will affect soft handover.
Probable Cause
2. The cable, connected to previous cascading node, is broken or in

poor contact.
3. Clock cascading cable is not tightly connected or in poor contact.

4. The end of clock cascading cable is unqualified.
5. The receiving Baud rate is different from that transmitted by
previous-level of node.
Handling Suggestion
2. Remove and insert clock cascading cable to ensure correct

connection.
3. Set receiving Baud rate to be the same as that transmitted by

previous cascading node.
4. Check whether the status of previous-level of clock source is normal.
5.36 198092413 1PPS+TOD standby source fault

Severity
System Impact
Failure in obtaining 1PPS+TOD signals.

Clock synchronization and frame synchronization cannot be
guaranteed. This will affect soft handover.
5-18
SJ-20120322151347-005|2012-04-15(R1.1)
Probable Cause
2. The cable, connected to previous cascading node, is broken or in

poor contact.
3. Clock cascading cable is not tightly connected or in poor contact.

4. The end of clock cascading cable is unqualified.
5. The receiving Baud rate is different from that transmitted by
previous-level of node.
Handling Suggestion
2. Remove and insert clock cascading cable to ensure correct

connection.
3. Set receiving Baud rate to be the same as that transmitted by

previous cascading node.
4. Check whether the status of previous-level of clock source is normal.
5.37 198092414 SyncE clock unavailable (SyncE+1588)

Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Work normally
The service performance in the corresponding cell becomes worse. In

serious situation, the services are interrupted.
Probable Cause
OMC.
5-19
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
module rate. Then check if the alarm disappears.
5.39 198092432 Optical modules have mismatched

transmission distance
Severity
System Impact
Probable Cause
Handling Suggestion
distance. After that, check if the alarm disappears.

5.40 198094811 Cell Setup Failure

Severity
System Impact
Probable Cause
Handling Suggestion
BBU's configuration manual)
2.Check if the communication link between the RRU used by the cell
and the BBU is normal.If the RRU is faulty,first handle RRU's alarm.
3.Reset the faulty CC board.
4.Replace the faulty CC board.
5-20
SJ-20120322151347-005|2012-04-15(R1.1)
5.41 198094812 Cell Reconfiguration Failure

Severity
System Impact
Probable Cause
Handling Suggestion
BBU's configuration manual).
2.Check if the communication link between the RRU used by the cell
and the BBU is normal.If the RRU is faulty,first handle RRU's alarm.
3.Reset the faulty CC board.
4.Replace the faulty CC board.
5.42 198094813 Parament Configuration Error

Severity
System Impact
Probable Cause
Handling Suggestion
5-21
SJ-20120322151347-005|2012-04-15(R1.1)
5-22
SJ-20120322151347-005|2012-04-15(R1.1)
Chapter 6
QoS Alarm
Table of Contents
alarm
198094826 PCI conflict alarm
198094827 PCI confusion alarm
198092350 RRU pre-download is failed
198092368 Ethernet remote fault alarm(RDI)
198092370 AIS alarm
198092380 EFM Link is broken
receiver
Severity
System Impact
Work normally
Board process capability is reduced. Partial functions cannot be

provided properly. In serious situation, this may cause service failure,
for example, radio link setup failure.
Probable Cause
Handling Suggestion
(1) Check the connection of GNSS antenna feeder to ensure correct

connection.
(2) Check the direction of antenna so that there is no obstacle in front

of it.
6-1
SJ-20120322151347-005|2012-04-15(R1.1)
6.2 198092417 The built-in-type GNSS receiver has a

satellite searching alarm
Severity
System Impact
Work normally

Probable Cause
Handling Suggestion
(1) Check the connection of GNSS antenna feeder and ensure it is OK.
(2) Check whether the direction of GNSS antenna is suitable (e.g. Is
there any obstacle surrounding the antenna?)
6.3
has a satellite searching alarm.
Severity
System Impact
Work normally

Probable Cause
Handling Suggestion
(2) Check whether the direction of GNSS antenna is suitable (e.g.is
6-2
SJ-20120322151347-005|2012-04-15(R1.1)
Chapter 6 QoS Alarm
6.4
receiver has a satellite searching alarm.
Severity
System Impact
Work normally

Probable Cause
Handling Suggestion
(2) Check whether the direction of GNSS antenna is suitable (e.g.is
6.5 198094826 PCI conflict alarm

Severity
System Impact
Probable Cause
Handling Suggestion
Severity
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
cell's coverage.
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
that has relationship with other MEP fault; In single MEP, not receiving
ETH-RDI means the total MEG has no fault.
2.It is used to monitor remote performance: It reflects fault condition

that has happened in remote side and can be used to input of
performance monitoring process.
Handling Suggestion
6.9 198092370 AIS alarm
SJ-20120322151347-005|2012-04-15(R1.1)
Chapter 6 QoS Alarm
Severity
System Impact
Probable Cause
Handling Suggestion
Severity
System Impact
Probable Cause
Handling Suggestion
6-5
SJ-20120322151347-005|2012-04-15(R1.1)
6-6
SJ-20120322151347-005|2012-04-15(R1.1)
Chapter 7
Notification
Table of Contents
198092054
198092055
198092056
198092058
198092059
198092061
198092062
198092063
198092064
198092065
198092228
198092229
198092271
198092297
198092312
198092314
198092315
198092316
198092329
198092338
198092349
198092381
198092392
198094823
198096557
198096566
198098433
198092031
198092033
198092034
hours
7-1
SJ-20120322151347-005|2012-04-15(R1.1)
7.1 198092054 Slave board powered-on notification

System Impact
Probable Cause
Handling Suggestion
System Impact
Probable Cause
Handling Suggestion
System Impact
Probable Cause
Handling Suggestion
package
System Impact
Work normally
Even though the booting is successful, all peripheral boards cannot

Probable Cause
7-2
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
specification package again. After that, activate it.
7.5 198092059 Alarm Storm

System Impact
Probable Cause
the threshold value.
Handling Suggestion
7.6 198092061 Module reset

System Impact
Probable Cause
Handling Suggestion
7.7 198092062 Module status error
System Impact
Probable Cause
Handling Suggestion
7.8 198092063 Switchover completed

System Impact
SJ-20120322151347-005|2012-04-15(R1.1)
Probable Cause
Handling Suggestion
7.9 198092064 Switchover failed
System Impact
Probable Cause
Handling Suggestion
7.10 198092065 Board switchover failed
System Impact
Probable Cause
Handling Suggestion
System Impact
Probable Cause
Handling Suggestion
System Impact
Probable Cause
Handling Suggestion
SJ-20120322151347-005|2012-04-15(R1.1)
7.13
System Impact
Probable Cause
Handling Suggestion
configured. If yes, check whether the clock reference source is normal

(e.g. there is no alarm about lost of clock reference source or degraded
clock quality).
2. Reset the faulty board (note: resetting CC board will cause all
services borne on the board to be interrupted, so please choose proper
time to conduct this reset operation).
3. Replace the faulty board (note: resetting CC board will cause all
services borne on the board to be interrupted, so please choose proper
time to conduct this reset operation).
7.14 198092297 Uplink optical/electrical link has high

BER
System Impact
Work normally
The performance of cell services, associated to the optical port,

becomes worse.
Probable Cause
exceeds the configured threshold.
Handling Suggestion
connected and the corresponding connector is clean.
2. Reset the corresponding RRU forcibly.
3. Remove and insert the corresponding optical module.

4. Replace the corresponding optical module.

7-5
SJ-20120322151347-005|2012-04-15(R1.1)
7.15 198092312 PPP Negotiatory IP Conflict

System Impact
Probable Cause
Handling Suggestion
7.16 198092314 IP Conflict
System Impact
Probable Cause
Handling Suggestion
7.17 198092315 Mac Conflict
System Impact
Probable Cause
Handling Suggestion
7.18 198092316 ACOM address conflict
device, but user does not re-scan AISG device, then the address
conflict will affect existing device to communicate normally. When the
address conflict occurs, base station will try to detect and recover it.
After recovery, the system will give this alarm notification. However,
only the existing device can resume to normal communication. The
newly inserted device must be scanned before it can be recognized and
managed by base station.
7-6
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
No impact on service. Communication of the AISG device formerly

affected by address conflict is restored, but the newly inserted device
has not been identified. The newly inserted device can be identified
and managed by base station only after device scan.
Probable Cause
connected AISG device.
existing AISG device.

Handling Suggestion
box then add a new device.
7.19
System Impact
Communication of the AISG device formerly affected by address conflict

is restored, but the newly inserted device has not been identified. The
newly inserted device can be identified and managed by base station
only after device scan.
Probable Cause

Handling Suggestion
box then add a new device.
7-7
SJ-20120322151347-005|2012-04-15(R1.1)
7.20
System Impact
Communication of the AISG device formerly affected by address conflict

is restored, but the newly inserted device has not been identified. The
newly inserted device can be identified and managed by base station
only after device scan.
Probable Cause

Handling Suggestion
device.
System Impact
Probable Cause
Handling Suggestion
7.22 198092381 EFM Link has error data
System Impact
Probable Cause
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
first switchboard is normal.
System Impact
Probable Cause
Handling Suggestion
7.24
Severity
System Impact
Probable Cause
2.Input Baseband Signal Too Small.

3.Feedback Baseband Signal Too Large.
4.Feedback Baseband Signal Too Small.
5.Signal Correlation Small.
6.Link Delay Out Of Limit.

7.FPGA Data Acquisition Failure.
8.Clipping Invalid.
9.DPD Invalid.
10.FPGA Register RW Error.

11.PA Compress Over Limit.
12.Table Gain Over Limit.
13.Dsp Power Adjustment Over Limit.
Handling Suggestion
7.25 198096557 Uplink IQ link error

7-9
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
Probable Cause
Handling Suggestion
7.26 198096566 RRU alarm reset

System Impact
Probable Cause
Handling Suggestion
function
System Impact
Probable Cause
Handling Suggestion
function.
2. Check whether RRU works normally.
3. In other case, please close the time slot closing function at

background.
7.28 198092031 Board power-on done notification

System Impact
Probable Cause
SJ-20120322151347-005|2012-04-15(R1.1)
Handling Suggestion
System Impact
Probable Cause
Handling Suggestion
System Impact
Probable Cause
Handling Suggestion
is no impurity, rubber-insulated wires are not in short-circuit.

has a problem.


6. Replace the port of repeater (or optical transceiver).
7.31 198092035 E1 link bit error has been detected in

the past 24 hours
7-11
SJ-20120322151347-005|2012-04-15(R1.1)
System Impact
Probable Cause
Handling Suggestion
is no impurity, rubber-insulated wires are not in short-circuit.

has a problem.


6. Replace the port of repeater (or optical transceiver).
7-12
SJ-20120322151347-005|2012-04-15(R1.1)
Glossary
AISG
- Antenna Interface Standards Group
- 天线接口标准组
BBU
- BaseBand Unit
- 基带单元
CPU
- Central Processing Unit
- 中央处理器
DPD
- Digital Pre-Distortion
- 数字预失真
IMA
- Inverse Multiplexing over ATM
- ATM反向复用
LNA
- Low Noise Amplifier
- 低噪声放大器
MMC
- Module Management Controller
- 模块管理控制器
PLL
- Phase Locked Loop
- 锁相环
PSU
- Power Supervision Unit
- 电源监控单元
QoS
- Quality of Service
- 服务质量
RET
- Remote Electrical Tilt
- 远程控制电子下倾角
RF
- Radio Frequency
- 射频
SJ-20120322151347-005|2012-04-15(R1.1)
RRU
- Remote Radio Unit
- 远端射频单元
SCTP
- Stream Control Transmission Protocol
- 流控制传输协议
TCP
- Transfer Control Protocol
- 传输控制协议
VSWR
- Voltage Standing Wave Ratio
- 电压驻波比
II
SJ-20120322151347-005|2012-04-15(R1.1)
. Any reproduction or
without the prior written
ent are protected by
r service marks, of ZTE
esentations or conditions
ss for a particular purpose,
mages resulting from the
ights or applications
en license between ZTE
e to the subject matter
oduct without further notice.

ated information.
Revision Date
2012-4-15
2011-12-20
ZTE Proprietary and Confidential
I
1-1
2-1
2-1
2-2
2-3
2-3
2-4
2-5
2-5
2-6
2-6
2-7
2-7
2-8
2-8
2-8
2-9
2-10
2-11
2-12
2-12
2-13
2-14
2-14
2-14
2-15
3-1
3-7
3-8
3-8
3-9
3.5 198100274 Downlink output power abnormal

3.6 198100274 Downlink output under/over-power alarm
3.7 198092008 FPGA register read/write error
3.8 198092009 Ethernet access network interface abnormal
3.9 198092011 E1/T1 input port unavailable
3.10 198092012 E1/T1 output port unavailable
3.11 198092013 ES or SES detected on the E1 link in the past 15 minutes has
exceeded the threshold
198092032 Failed to operate Database
198092049 Lightning protection device alarm
198092051 PSU alarm
198092052 PSU fan alarm
198092057 The board is powered off
198092068 Base station has a main power cut-off alarm
198092071 Abnormal temperature sensor
198092072 Board not-in-position
198092073 Embedded power AC-in Switch Off
198092074 Embedded power AC Power Off
198092075 Embedded power SPD-C Broken
198092076 Embedded power SPD-D Broken
198092077 Embedded power AC Under-Volt
198092078 Embedded power AC Over-Volt
198092079 Embedded power AC Current Over
198092080 Embedded power SMR Over-Vout
198092081 Embedded power SMR Over-Iout
198092082 Embedded power SMR Fan Fault
198092083 Embedded power SMR PFC Fault
198092084 Embedded power SMR Over-Vin Off
198092085 Embedded power SMR Under-Vin Off
198092086 Embedded power SMR H.T. Off
198092087 Embedded power SMR Env.H.T.Off
198092088 Embedded power SMR Env.H.T
198092089 Embedded power SMR L.Vin
198092090 Embedded power SMR Fuse Broken
198092091 Embedded power SMR CommFail
198092092 Embedded power DC Under-Volt
198092093 Embedded power DC Over-Volt
198092094 Embedded power DC Loop Broken
3.42 198092095 Embedded power Bat Loop Broken

3.43 198092096 Embedded power Bat Under-Volt
3.44 198092097 Embedded power Bat Over-Temp
3.45 198092098 Embedded power TmpL Shut-Down
3.46 198092099 Embedded power 1st Shut-down
3.47 198092100 Embedded power 2nd Shut-down
3.48 198092101 Embedded power DC SPD Broken
3.49 198092102 Embedded power DCBreaker Alarm
3.50 198092103 Embedded power Bat Test Failure
3.51 198092104 Embedded power Bat Discharge
3.52 198092116 Embedded power AC Auxiliary Output Switch Off
3.53 198092117 Embedded power Rectifier Module Fault
Board not-configured alarm
Battery alarm
AC power-cut alarm
Rectifier module alarm
Thermoelectric cooler alarm
EPLD's register has a R/W failure alarm
Hardware of Clock Module Fault
Lost of synchronization
Current Active Reference Source 1PPS Lost
Air Interface Clock Unavailable
Baseband Subunit Fault
Embedded power type configuration error
Embedded power communication interruption
Embedded power SMR Output Fault
Embedded power Bat Under-Temp
Embedded power Bat Invalid-Temp
Embedded power Battery Fault
1588 clock source unavailable
Ir link LCV alarm
Abnormal DPD running status
LNA alarm
Disable PA
TMA channel input is over current
Over-high temperature of PA
Optical module out-of-position alarm
III

198092250 Calibration file on TRx board is abnormal
198092251 a block check error of downlink IQ channel alarm
198092252 Downlink digital IF pre-distortion alarm
198092253 Application software monitoring alarm
198092254 Remote output power abnormal voltage alarm
198092255 Remote input power over-voltage alarm
198092256 Remote input power under-voltage alarm
198092258 Lost of frame rate and frame number
198092259 Battery low-voltage alarm
198092260 Faulty external device connected at a dry contact
198092261 Outdoor lightning protection box alarm
198092262 Breaker alarm in indoor lightning protection box
198092263 Lightning protection device alarm in indoor lightning protection box
3-55
198092264 Over-voltage alarm of main power input
198092265 Main power input power-cut alarm
198092266 Under-voltage alarm of main power input
198092267 General fault of main power
198092268 PWR monitoring unit alarm
198092269 Over-high temperature of RU board
3.100 198092270 Slight-high temperature of RU board
3.101 198092272 The value of RSSI over reverse link is low
3.102 198092273 The value of RSSI over reverse link is high
3.103 198092274 Slight-high temperature of PA
3.104 198092275 PA communication fault
3.105 198092276 Receiving RF channel fault
3.108 198092279 Downlink analog power exceeds rated power slightly

3.109 198092280 Downlink digital power exceeds rated power slightly
3.110 198092281 Downlink carrier baseband power is low
3.111 198092282 Downlink carrier analog power is low
3.112 198092283 Remote antenna VSWR alarm
3.113 198092284 Input reference clock is abnormal
3.114 198092285 Internal clock is abnormal
3.115 198092286 The uplink frame at optical/electric port is unlocked
IV
3-67
3-68
3-69
3-69
3-70
3-70
3-71
3-71
3-72
3-72
3-73
3-73
3-73
3-74
3-74
3-75
3-75
3-75
3-76
3-76
3-77
3-77
3-77
3-78
3-78
3-78
3-79
3-79
3-80
3-80
3-80
3-81
3-81
3-82
3-82
3-83
3-83
3-83
3-84
3-84
3-85
3-85
3-85
3-86
3-86
3-86
3-87
3-87
3-88
3-88
3-88
3-89
3-89
3-90
3-90
3-90
3-91
3-91
3-92
3-92
3-92
3-93
3-93
3-94
3-94
3-95
3-95
3-96
3-97
3-97
3-98
3-98
3-98
3-99
3-99
3-100
3-100
3-101
3-101
3-102
3-102
3-103
3-104
3-105
3-106
3-106
3-107
3-108
3-108
3-108
3-109
3-109
3-110
3-110
3-110
3-111
3-111
3-111
3-112
3-112
3-113
3-113
3-113
3-114
3-114
3-114
3-115
3-115

17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
VIII
3-129
3-130
3-130
3-130
3-131
3-131
3-131
3-132
3-132
3-132
3-133
3-133
3-133
3-134
3-134
3-134
3-135
3-135
3-136
3-137
3-137
3-137
4-1
4-2
4-2
4-3
4-3
4-3
4-4
4-4
4-5
4-6
4-6
4-7
4-7
198092047 Infrared alarm

198092048 Air conditioner fault
198092053 Voltage of DC input is abnormal
198092069 FCE-fan failure
198092105 Embedded power Environment is under-temperature
198092106 Embedded power Environment is over-temperature
198092107 Embedded power Environment temperature is invalid
198092108 Embedded power Environment is under-Humidity
198092109 Embedded power Environment is over-Humidity
198092110 Embedded power Environment humidity is invalid
198092111 Embedded power Smoke detected
198092112 Embedded power Flood detected
198092113 Embedded power Door Magnet Alarm
198092114 Embedded power Gate Embedded power Safety Alarm
198092115 Glass Broken Alarm
198092118 Embedded power Env-unit communication interruption
198092119 Embedded power Heat Exchanger Fault
198092213 Board temperature abnormal alarm
198092307 Slight-high temperature of board
198092308 Over-high temperature of board
198092371 CCM Remote MEP Error
198092372 CCM Message Error
198092373 CCM Xconnect Error
5.1 198094815 Performance Measurement Rule Library Unavailable

5.2 198096567 BOOT software upgrade failure
5.3 198092010 Board communication link is interrupted
5.4 198092014 SNTP time adjustment failure alarm
5.5 198092016 Clock reference source configuration error
5.6 198092017 Failure in loading software
5.7 198092019 Failure in synchronizing the version of master board with slave
5.8 198092022 Running software version doesn't exist

5.9 198092024 DOM is lack of space
5.10 198092025 Failure in synchronizing software version of master control board
5.11 198092027 Failure in repairing specification package
5.12 198092029 Wrong board insertion
X
Abnormal software in specification package

LMT login alarm
Failure in uncompressing LMT software
Board software fault
Line clock has the fault
SyncE clock has the fault
The fan control policy is not existed
Board initialization
Product process is abnormal
Configuration Fail
CPU over loading highly alarm
CPU over loading
Running software rollback
Board hot patch fault
Failure in finding this board-related software ID
MMC running software version doesn't exist
Carrier frequency configuration error
Center frequency configuration error
Work pattern configuration error
IQ parameter configuration error
Delay parameter configuration error
Carrier power configuration error
1PPS+TOD source fault
1PPS+TOD standby source fault
SyncE clock unavailable (SyncE+1588)
Optical module rate does not match
Optical modules have mismatched transmission distance
6.1 198092410 Satellite searching alarm of GNSS receiver

6.2 198092417 The built-in-type GNSS receiver has a satellite searching alarm
6.3 198092420 The external-panel-type GNSS receiver has a satellite searching
6.4 198092424 The external-backplane-type GNSS receiver has a satellite
XI
6.6 198094827 PCI confusion alarm

6.7 198092350 RRU pre-download is failed
6.8 198092368 Ethernet remote fault alarm(RDI)
6.10 198092380 EFM Link is broken
7.1 198092054 Slave board powered-on notification

7.2 198092055 Active-to-standby switchover completed
7.3 198092056 Standby-to-active switchover completed
7.4 198092058 Succeed in repairing the specification package
7.7 198092062 Module status error

7.8 198092063 Switchover completed
7.9 198092064 Switchover failed
7.10 198092065 Board switchover failed
7.11 198092228 Main board product process power-on
198092229 Slave board product process power-on
198092271 Local benchmark clock unlocked
198092297 Uplink optical/electrical link has high BER
198092312 PPP Negotiatory IP Conflict
198092314 IP Conflict
198092315 Mac Conflict
198092316 ACOM address conflict
198092329 ATMA device address conflict
198092338 RET device address conflict
198092349 RRU pre-download is successful
198092381 EFM Link has error data
198092392 Product process fails to power on
198094823 DPD Running Status Abnormal
198096557 Uplink IQ link error
198096566 RRU alarm reset
198098433 Unavailable alarm of time slot turn-off function
198092031 Board power-on done notification
198092033 Board power-on failed
198092034 Bit error has been detected during E1 physical layer in the past 24
XII
7-11
I
ring the product
Summary
Describes the concept of fault management
Describes communication alarms with respect to detailed
information, severity, probable cause, system impact, and
handling suggestion
Describes equipment alarms with respect to detailed
handling suggestion
Describes environment alarms with respect to detailed
handling suggestion
Describes processing alarms with respect to detailed
handling suggestion
Describes QoS alarms with respect to detailed
handling suggestion
Describes notification with respect to detailed information,
nd events that occur
e or displayed
eans such as
w current or
ement enables
o remove potential
bility and normal
uires timely
d and handled.
occurs during
ccidental factors.
atically removed by
dition and its
(ITU-T Recommendation
T Recommendation
equipment is located
Alarm/Notification Code
Alarm/Notification Code is the identifier which differentiates alarms/notifications.
Alarm/Notification Code is defined by a 32-bit field indicating the specific code value.
Alarm Name
Detailed Information reflects such content as fault cause and fault phenomenon.
Alarm Severity
severity as
ption. It requires
ns network service
ce capability in a
n and network service

set. Users should
eshoot, find
enance personnel may
as soon as possible.

198092230 SCTP association is interrupted
198092382 Configuration parameter of OAM Channel is wrong
198092427 The number of SCTP streams is inconsistent
198092431 The strength of received optical signal is abnormal

198092445 RRU inner GNSS (clock reference source) link alarm
198092446 RRU inner GNSS (clock reference source) link unavailable
198094825 Optical link which bearing S1/X2 signal breakdown error
198096564 RRU and outer LNA communication link broke
198092210 PLL reference clock lost alarm
PLL is unlocked.
Major
Because PLL is unlocked, its output clock cannot meet system
requirement. As a result, PHY may not work normally in SNYCE mode.
PLL has no reference clock input or the reference clock is in poor
quality.
1. If the board is only used as an ordinary data switching board without
198092230 SCTP association is interrupted.

This alarm is given when SCTP association setup is failed, local end
has received close notification from its peer end, or there is no response
after continuously sending data to its peer end.
Critical
The transmission of Nbap signaling might fail and the services provided
by this association might be interrupted.
1. Local FE configuration or PPP is error.
2. The related parameters of local or the opposite are error.
3. The bottom-layer cannot communicate with the opposite site.
4. The board is fault.
1. Check if there is FE port or PPP related alarm

198092231 PPP Link is broken.
Iub link has fault.
Critical
Commands and services in the PPP are interrupted.
PPP Link is broken.
1. If PPP exist in E1/STM1, check if the related E1/STM1 link has
Alarm happens when HDLC run into bad link in the process of
negotiation.
Critical
bottom-layer link of communication may be interrupted.
2-3
HDLC Link is broken.

1. If HDLC exist in E1/STM1, check if the related E1/STM1 link has
Alarm happens when Sscop link cannot send NBAP or ALCAP data in
time that causes cumulate data that need be sent exceeds cache limit.
Critical
It may lead service command cannot be receive and send so that the
1. The physics link that base station carries PVC link is fault.
2. Base station PVC's parameters are configured wrongly.
3. Board is fault.
1. Check if there are related alarms in real-time monitor of alarm
This alarm is reported in one of the following situations:
Minor
none
1. It is impossible to communicate with master clock of this link.
2. This link encounters a serious network congestion problem.
3. When the standard Announce message is enabled, it is impossible
to trace master clock source of the link.
1. Check whether the physical connection to CC is normal.
Alarm happens when PPP in LCP process receives Link Loop at three
times.
Major
PPP link circle.
PPP Link Circle.
2-5
Check if there is a circle in physical links .
Local LMT's Force Connect.

Warning
None
Local LMT Connect base station forcedly.
None
198092361 IMA group has fault.
Alarm happens when IMA group is configured successfully, but IMA
group cannot reach normal working status.
Major
1. Board Status:
1. Transport relay equipment has fault or configuration is not right.

1. Check whether the local interfacing board has the E1/T1 alarms. If
198092362 IMA/TC link has fault.

This alarm is reported when IMA group sub-link/TC link has a fault.
Major
1. Board Status:
2. Service Impact:
Transport bandwidth and service capacity will be affected.
1. Transport relay equipment has fault or configuration is error.
2. Base station or RNC configuration is error.
1. Check the link configuration between base station and RNC: If
Dot1x authentication process is abnormal.
Minor
The transmitting and receiving of IP packets is abnormal.
1. The physical link is broken.
2. User Id and password are not matched in dot1x configuration.
1. Please check whether the link of authenticator and supplicant is
ETH-LCK informs MEP to lock data service stream.

Major
Transmission of ethernet service is broke.
It happens enterprising lock of data stream.
Please check ethernet device in another side.
2.13 198092382 Configuration parameter of OAM
OMCB channel is abnormal and need to configurate correct channel
data.
Major
1. Board Status:
OMCB channel is abnormal and need to configurate correct channel
Reconfigurate system by the whole table data that contains correct
2.14 198092399 BFD connection broken

Failure in setting up BFD connection, receiving a peer-end closed
information, or not receiving response from peer-end after continuously
sending data for several times.
Major
Signaling may not be received/transmitted properly. Accordingly, the
corresponding services borne over the connection are interrupted.
1.Local end is in FE configuration.
1. Check whether FE port exists.

An alarm is reported when one of these situation happens: TCP link
setup is unsuccessful, a peer-end closed notification message is
received, or there is no response after continuously sending data to
peer end for several times.
Critical
The transmission of signaling might fail and the services provided by
this association might be interrupted.
2-9
1. Local FE configuration or PPP is error.

2. TCP parameters of local or the opposite are error.
3. The bottom-layer cannot communicate with the opposite site.
1. Check if there is FE port or PPP related alarm

This alarm is reported when CC board fails to detect BITS clock signal
or the detected clock signals have poor quality.
Minor
2-10
1. Board Status:
1. The configured clock reference source doesn't exist.
1. Check whether wrong reference source is configured.
The configured number of outgoing/incoming SCTP streams is

inconsistent with that negotiated.
Minor
Signaling may not be sent/received properly. As a result, partial
services borne over the SCTP link may be interrupted.
1. The number of outgoing/incoming streams configured at local end is
inconsistent with peer end.
2. The number of outgoing/incoming streams negotiated is inconsistent
with configured due to some restrictions.
Check whether the number of outgoing/incoming SCTP streams is
correctly configured at both local end and peer end.
2-11
198092428 SCTP path is interrupted.

This alarm is reported when a SCTP path transmits a heartbeat
message but there is no response, or the number of retransmission
attempts exceeds its maximum retransmissions.
Major
1.Board Status:
1. Path parameters (FE and PPP) are wrongly configured at local end.
1. In Alarm Management Interface, view real time alarm information.
cal signal
This alarm is reported when the received power by an optical module is
too high or too low.
Minor
2-12
1. Board Status:
Work normally
The service performance in the corresponding cell is reduced.
1. The optical fiber is broken.
2. The optical module is aged.
3. The real length of an optical fiber exceeds the transmission distance
supported by the optical module.
1. Check the connections of optical module and fiber. After that, check
In the configuration of RRU inner GNSS clock reference source, this

alarm is reported when the system fails to obtain synchronous signals
or the obtained synchronous signals cannot be used.
Minor
1. Board Status:
1. The link between RRU and BBU is abnormal.

2. RRU searches satellites abnormally.
1. Check whether the communication link is normal.
2. Check whether RRU has other relevant faults caused by antenna
feeder, receiver or satellite searching function.
In the configuration of RRU inner GNSS clock reference source, this

alarm is reported when all configured RRU links are abnormal.
Major
1. Board Status:
No available message can be obtained from all the configured RRU
1. Check whether the configured RRU communication links are normal.
1/X2 signal
Optical module loss signal.
Critical
S1/X2 interface link breakdown, fail to communicate.
Optical fiber breakdown.
Check optical module and Optical links.
2.23 198096564 RRU and outer LNA communication
RRU and outer LNA communication link broke.
Major
The RRU may not tune remote LNA normally.
RRU and external LNA communication link broke.
Check the connection of external LNA and RRU.
2-14
Output of PLL has 4 ways, where the third way is directed to PHY with
no detection by EPLD. EPLD detects another way in output of PLL. The
value in EPLD offset 0x48 register read by MCU is sent to CC through
IPMI, and then be sent to OMCB.
Major
Because the working clock on PHY's synchronous Ethernet is lost, the
corresponding Ethernet port cannot work properly.
PLL has no 25M clock output.
1. If the board is only used as an ordinary data switching board without
198100271 Unlocked local oscillator alarm of RRU

198100272 RRU inside clock unlocked
198100273 Downlink channel fault alarm
198100274 Downlink output power abnormal
198100274 Downlink output under/over-power alarm
198092008 FPGA register read/write error
198092009 Ethernet access network interface abnormal
198092011 E1/T1 input port unavailable
198092012 E1/T1 output port unavailable
198092013 ES or SES detected on the E1 link in the past 15 minutes has exceeded
Failed to operate Database

Lightning protection device alarm
PSU alarm
PSU fan alarm
The board is powered off
Base station has a main power cut-off alarm
Abnormal temperature sensor
Board not-in-position
Embedded power AC-in Switch Off
Embedded power AC Power Off
Embedded power SPD-C Broken
Embedded power SPD-D Broken
Embedded power AC Under-Volt
Embedded power AC Over-Volt
Embedded power AC Current Over
Embedded power SMR Over-Vout
Embedded power SMR Over-Iout
Embedded power SMR Fan Fault
Embedded power SMR PFC Fault
Embedded power SMR Over-Vin Off
Embedded power SMR Under-Vin Off
Embedded power SMR H.T. Off
Embedded power SMR Env.H.T.Off
Embedded power SMR Env.H.T
3-1
3-24
3-24
3-24
3-25
3-26
3-26
3-27
3-27
3-28
3-28
3-29
3-30
3-30
3-31
3-31
3-32
3-32
3-33
3-33
3-34
3-34
3-35
3-35
3-36
3-36
3-38
3-39
3-39
3-40
3-40
3-40
3-41
3-41
3-42
3-42
3-43
3-43
3-44
3-44
3-44
3-45
3-46
3-46
3-47
3-47
a block check error of downlink IQ channel alarm

Downlink digital IF pre-distortion alarm
Application software monitoring alarm
Remote output power abnormal voltage alarm
Remote input power over-voltage alarm
Remote input power under-voltage alarm
Remote antenna over VSWR alarm
Lost of frame rate and frame number
Battery low-voltage alarm
Faulty external device connected at a dry contact
Outdoor lightning protection box alarm
Breaker alarm in indoor lightning protection box
Lightning protection device alarm in indoor lightning protection box
Over-voltage alarm of main power input
Main power input power-cut alarm
Under-voltage alarm of main power input
General fault of main power
PWR monitoring unit alarm
Over-high temperature of RU board
Slight-high temperature of RU board
The value of RSSI over reverse link is low
The value of RSSI over reverse link is high
Slight-high temperature of PA
PA communication fault
Receiving RF channel fault
Clock module fault
Abnormal power
Downlink analog power exceeds rated power slightly
Downlink digital power exceeds rated power slightly
Downlink carrier baseband power is low
Downlink carrier analog power is low
Remote antenna VSWR alarm
Input reference clock is abnormal
Internal clock is abnormal
The uplink frame at optical/electric port is unlocked
The channel downlink frame is unlocked
The PLL clock is unlocked
The optical/electric module is not in the position of optical port
The uplink optical/electric link is interrupted
The input frame synchronous signal is wrong
An alarm is given when an optical fiber is wrongly connected
The Rx optical port at RRU has no light signal
The frame transferred over Rx port of RRU is unlocked
RRU power-cut alarm
MMC Fault
3-3
3-73
3-73
3-73
3-74
3-74
3-75
3-75
3-75
3-76
3-76
3-77
3-77
3-77
3-78
3-78
3-78
3-79
3-79
3-80
3-80
3-80
3-81
3-81
3-82
3-82
3-83
3-83
3-83
3-84
3-84
3-85
3-85
3-85
3-86
3-86
3-86
3-87
3-87
3-88
3-88
3-88
3-89
3-89
3-90
3-90
3-90
3-91
3-91
3-92
3-92
3-92
3-93
3-93
3-94
3-94
3-95
3-95
able alarm.
3-97
3-97
3-98
3-98
3-98
3-99
3-99
3-100
t mode from
3-100
3-101
3-101
3-102
3-102
3-103
3-104
3-105
3-106
3-106
3-107
3-108
3-108
3-108
3-109
3-109
3-110
3-110
3-110
3-111
3-111
3-111
3-112
3-112
3-113
3-113
3-113
3-114
3-114
3-114
3-115
3-115
3-116
3-116
3-116
3-117
3-117
3-117
3-118
3-118
3-119
3-119
3-119
3-120
3-120
3-120
3-121
3-121
3-122
3-122
3-122
3-123
3-123
3-123
3-124
3-124
3-125
3-125
3-125
3-126
3-126
3-126
3-127
3-127
3-128

198094800 SRIO Communication Abnormal
198094828 The board is unavailable
198094829 eBBU synchronization abnormal
198096550 Alarm of fiber configuration
198096551 RRU unconfigured
198096552 Difference of fiber time delay of two RRUs in same sector exceeded
198096553 RRU Type is not consistent with configuration type

198096554 Failure of optical decoding in BBU
198096555 Failure of optical decoding in RRU
198096556 IQ link input loses lock
198096558 Downlink baseband power abnormal
198096558 Guide frequency that BBU sends to RRU is too high or too low
198096559 RRU adjust channel or adjust cable fault
198096560 Master and slave monitor link alarm
198096561 Coherence alarm of antenna channel swing and phase
198096562 RRU self check failed when power on
198096563 RRU device alarm
198096565 Configuration parameter of RRU external device not consistent with
198096568 RRU used power module is too hot

198096569 RRU offline parameter check failure
198098431 Abnormal current alarm at NSBT port
198098432 AISG/NSBT port turn-off alarm due to over current
198098434 Abnormal transmission power at antenna port
198098435 Closed-loop power control adjustment exceeding normal range
198098436 Failure in configuring power level
3.1 198100270 Optical signals transmitted from BBU to
RRU carry wrong clock information
Optical signals transmitted from BBU to RRU carry wrong clock
information.
Critical
1.Board Status:
Work normally
RRU cannot provide services.
PLL clock is unloced at optical port
3-7
1. Check fiber connection.
m of RRU
RRU reports an unlocked local oscillator alarm.
Critical
1.Board Status:
1. IF sampling clock is unlocked or lost.

2. RF PLL clock is unlocked.
1. Check fiber connection.
This alarm is reported when a kind of clock signal in RRU is unlocked,

including IF clock, DAC clock, ADC clock, inside FPGA clock.
Major
1.Board Status:
Work normally
The quality of services may be reduced.
RRU internal clock (e.g. IF clock, DAC clock, ADC clock, FPGA inside
clock) is unlocked.
1. Reset RRU.
2. If it doesn't work, replace the RRU.
198100273 Downlink channel fault alarm

This alarm is reported when the value of RRU Tx channel gain is too
low.
Major
1.Board Status:
1. RRU hardware fault.

2. RRU software fault.
3. Abnormal baseband power.
1. If the alarm occurs occasionally and lasts for less than 10 minutes,
This alarm is reported when the value of RRU Tx channel power is
too high or low.
Major
1.Board Status:
1. Hardware fault (either Tx channel fault or power detection channel

198100274 Downlink output under/over-power

This alarm is reported when the value of RRU Tx channel power is
too high or low.
Major
1.Board Status:
1. Hardware fault (either Tx channel fault or power detection channel

None
Major
1. Board Status:
The board's logic cannot work normally.

1. Check whether the board has over-temperature alarm, if yes, handle
198092009 Ethernet access network interface

Ethernet access network interface abnormal.
Major
Ethernet is unavailable. If there is no E1 connection, base station may
be dropped.
None
1. In Configuration Management, check whether the Ethernet interface
The CC board periodically checks the alarm status of E1/T1 link. It is
used to indicate the connection status and the communication quality of
the transmission link.
Major
None
None
1. Check whether the frame format configured in Configuration
198092012 E1/T1 output port unavailable

The CC board periodically checks the alarm status of E1/T1 link,
and reports whether the trunk cable is available according to the
check result. It is used to indicate the connection status and the
communication quality of the transmission link.
Major
None
None
1. Check whether the frame format configured in Configuration
1 link in
The CC board periodically checks the error code of E1/T1 link, and
reports this alarm according to the statistics. It is used to indicate the
error code condition of the transmission link.
Warning
None
None
3-12
1. Check E1/T1 line connection in DDF rack .Confirm DDF rack is
During the CC board's power-on process, if CC fails to obtain the board

configuration from database, this alarm is reported.
Major
Board power-on failed.
1. The database query fails.
2. The database query succeeds but the data is abnormal.
3. Board status setting fails.
1. In the Configuration Management interface, check whether board
This alarm is reported when the lightning protection device has a fault
due to lightning attack, not well grounded or ageing failure.
Minor
1. Board Status:
1. View the relevant network management interface and finds that the
1. Select Configuration Resource Management and check whether dry

This alarm is reported when PSU is broken or its monitoring cable is
not well connected.
Minor
None
None
1. Check whether the monitoring cable of PSU is well connected.
2. Replace PSU module.
This alarm is reported when the PSU fan is faulty.

Minor
None
None
1. Check whether a fan box is installed.
2. Check whether the monitoring cable of PSU is well connected.
3. Replace the fan box.
3.16 198092057 The board is powered off

The board is powered off
3-14
Major
1. Board Status:
The board is powered-off.

1. Check the addition information of the alarm. If the alarm has
er cut-off
When the system detects that external main power supply has a fault,
this alarm is reported through dry contact.
Major
1. Board Status:
1. Main power supply is faulty.

2. Environment Monitor Unit is faulty.
3-15
1. Replace main power supply.
198092071 Abnormal temperature sensor

This alarm is reported when the temperature sensor is abnormal.
Warning
1. Board Status:
1. The sensor is not connected.
2. The cable connected to the sensor is broken.
3. The sensor is broken.
If the temperature sensor should be installed on FCE board, please
This alarm is reported when the board is configured in the network

management interface but actually is not inserted in the slot.
Major
1. Board Status:
1.Insert a board in the slot.

2.Unplug and plug the board.
3.20 198092073 Embedded power AC-in Switch Off
AC input switch is OFF.
Critical
1. The rectifier fails to work normally, only the battery can work.
2. When the battery runs out, the base station is powered down.
1. The air break switch of the main AC input is not closed.
1. If the air break switch of the main AC input is not closed, then close it.
The mains supply is cut off and there is no standby AC input.

Critical
1. The rectifier fails to work normally, only the battery can work.
2. The system does not implement battery management.
3. When the battery runs out, the base station is powered down.
1. The AC power supply is powered down.
1. If the AC power supply is powered down, use the generator to

The class C arrester loop is faulty.
Minor
The lightning protector fails.
1. The lightning protector is damaged.
1. The lightning protector is damaged. Replace the lightning protector.
The class D arrester loop is faulty.

Minor
The lightning protector fails.
1. The lightning protector is damaged.
1. The lightning protector is damaged. Replace the lightning protector.

198092077 Embedded power AC Under-Volt
The AC input phase voltage is lower than Phase.OverVolt.
Minor
The load capacity of the power supply is influenced, which also affects
the normal power supply for the base station.
1. The AC input voltage is low.
1. Improve the power supply quality of the equipment room.
The AC input phase voltage is higher than Phase UnderVolt.

Minor
1. The operation safety of the rectifier is influenced.
2. The rectifier will automatically power off for protection.
1. The AC input voltage is high.

1. Improve the power supply quality of the equipment room.
The AC input current is higher than the AC current maximum.

Minor
1. Over-current for a long time might cause the air break switch of the
AC input to break.
2. The AC input loop might be too hot, and the cable might be aging.
1. The AC input current is larger than the threshold value for the alarm.
2. The power supply's load is too heavy.
1. Check the threshold value of the monitoring unit's AC input current.
Rectifier output over-voltage.

Critical
3-20
1. The rectifier will be powered off for protection.

1. The rectifier's output voltage is abnormal.
1. Pull out the rectifier and plug it in again, and make it powered on.
3.28 198092081 Embedded power SMR Over-Iout
Rectifier output over-current.
Critical
1. The over-current protection circuit of the rectifier is faulty.
1. Pull out the rectifier and plug it in again, and make it powered on.
3.29 198092082 Embedded power SMR Fan Fault
The fan of the rectifier is abnormal.
Critical
1. The rectifier's fan is damaged or blocked by some foreign body.
1. Check whether the fan is blocked by some foreign body.
This alarm is reported when the rectifier-related PFC has one of these
faults: over-current input, over-voltage output or under-voltage output.
Critical
The PFC circuit of the rectifier is faulty.
Replace the rectifier.
3.31 198092084 Embedded power SMR Over-Vin Off
Rectifier AC input over-voltage.
Critical
1. The AC input voltage of the rectifier is higher than the threshold
value of over-voltage protection.
1. Check whether the AC voltage is higher than the threshold value.
3.32 198092085 Embedded power SMR Under-Vin Off
Rectifier AC input under-voltage.
Critical
1. The rectifier will have current-limiting output or be powered off for
protection.
1. The AC input voltage of the rectifier is lower than the threshold value
of under-voltage protection.
1. Check whether the AC voltage is lower than the threshold value.
3.33 198092086 Embedded power SMR H.T. Off

The temperature of the heat sink is too high.
Critical
3-22

1. The heat radiator of the rectifier is too hot.
1. Check whether the temperature of the rectifier's heat radiator is
The ambient temperature of the rectifier is too high which causes the
rectifier to shut down.
Critical
1. The environment temperature of the rectifier is too high.
The ambient temperature of the rectifier is too high which causes the
output power of the rectifier to derate.
Critical
1. The load capacity of the rectifier is influenced.
1. The environment temperature of the rectifier is higher than
The rectifier AC input voltage is too low which causes the output power
of the rectifier to derate.
Critical
1. The load capacity of the rectifier is influenced.
1. The AC input voltage of the rectifier is lower than the threshold
voltage for under-voltage load-reduction.
1. Check whether the AC voltage is lower than the threshold value.
3.37 198092090 Embedded power SMR Fuse Broken

The output fuse of the rectifier is blown.
Critical
1. The output fuse in the rectifier is burned.
1. If both soldering tool and a professional are available, please replace
the fuse.
2. If not, please replace the rectifier.
3.38 198092091 Embedded power SMR CommFail
The communication between the rectifier and monitoring unit is
abnormal.
Critical
3-24
1. The system fails to implement battery management.
1. The RS485 communication cable of the rectifier is broken or
1. Check whether the communication of all rectifiers is interrupted.
The DC output voltage is lower than DC OverVolt.

Minor
1. Although it has no influence on the system, it is necessary to find out
the alarm cause to avoid other faults.
1. The DC output voltage is lower than the threshold value.
2. The DC under-voltage value of the monitoring unit is set too high.
1. Check the DC output voltage.
The DC output voltage is higher than DC UnderVolt.

Major
The rectifier will be powered off for protection, only the battery can work.
1. The DC output voltage is high.
1. Check the DC output voltage.
The DC loop is open.

Critical
The power supply for the load is influenced.
1. The fuse of the load's loop is burned (or the air break switch is
1. Check whether the load's loop is short-circuited.
198092095 Embedded power Bat Loop Broken

The battery loop is open.
Critical
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.
1. The fuse of the battery's loop is burned.
1. Check whether the load's loop is short-circuited, and whether the

The battery voltage is lower than Batt.UnderVolt.
Major
Although it has no influence on the system, it is necessary to find out
the alarm cause to avoid other faults.
1. The battery's voltage is low.
1. Check the battery's output voltage.
The temperature of battery is higher than Batt.OverTemp.

Minor
The battery's service lifetime is influenced.
1. The battery's temperature is higher than the threshold value of
1. Check the battery's temperature.
-Down
The ambient temperature is lower than TmpL Shut Down, causing all
the loads to shut down.
Critical
It influences the power supply for the base station.
1. The system temperature is lower than the temperature for
198092099 Embedded power 1st Shut-down

When the battery voltage is lower than LVD1 Voltage, the less important
loads are shut down.
Critical
The secondary load is powered down.
1. When the battery's voltage decreases to the threshold value for first
1. Check the battery's voltage to see whether it is lower than the
198092100 Embedded power 2nd Shut-down

When the battery voltage is lower than LVD2 Voltage, all the loads
are shut down.
Critical
The base station is powered down, and the communication is
interrupted.
1. When the battery's voltage decreases to the threshold value for
1. Check the battery's voltage to see whether it is lower than the
The DC arrester is faulty.

Critical
The lightning protection capability is influenced. Replace the lightning
protector in time.

1. Check whether the detecting cable is disconnected or of bad contact.
3.49 198092102 Embedded power DCBreaker Alarm

DC breaker breaks.
Minor
If the circuit breaker can not be powered down normally, then the
battery might be discharged.
1. The DC contactor is damaged, there is one or two power-down
1. No handling is required if the problem is due to the load's current
The test stops but the test duration does not reach the maximum test
time.
Warning
It does not influence the power supply for the base station.
1. Before the test time expires, the battery discharge is stopped.
1. Check whether the battery is connected correctly.

The battery is being discharged.
Minor
1. The battery's discharge current is larger than the threshold value
1. Check whether the battery is in the discharge status.
ry Output
The air break switch of the standby AC output is not closed.
Minor
The power supply from standby AC output is influenced.
1. The air break switch of the standby AC output is not closed.

1. Close the air break switch of the standby AC output.
A rectifier module is faulty.

Critical
The normal load capacity of the power supply is influenced, which also
affects the power supply for the base station.
1. The rectifier module is faulty.
1. Check the rectifier's working status, and replace the rectifier.
This alarm is reported when a board is not configured in network

management interface, but it is inserted into a real slot.
Minor
1. Board Status:
1. The Network Management interface shows an idle slot, but a
2. PM has a fault. A board in-slot signal has been detected, but in fact
this slot is not configured with any board.
1. Configure this board in the Network Management interface, or
198092206 Battery alarm

This alarm is reported when the system detects that the external battery
at a dry contact is faulty.
Minor
1. Board Status:
1. A base station detects the faulty battery.

This alarm is reported when the main power is cut.
Minor
3-34
1. Board Status:
1. The dry contact is disconnected.

2. AC power-cut happens or there is no AC input due to abnormity.
This alarm is reported when the rectifier works abnormally.

Minor
1. Board Status:
1. The dry contact is disconnected.

2. The rectifier module works abnormally.
2. Replace the rectifier module.
3.58 198092209 Thermoelectric cooler alarm

This alarm is reported when the thermoelectric cooler is faulty.
Minor
1. Board Status:
1. The thermoelectric cooler is faulty.
3-35
1. Check whether the thermoelectric cooler is broken. If yes, please
lure alarm.
EPLD register R/W test fails. It is explained as: CPU reads/writes
to/from EPLD register, this operation returns a value, but the value is
different from configured value.
Major
Both clock selection and switchover functions are affected.
1. HOST bus is abnormal
2. MCU component is abnormal
3. EPLD component is abnormal
3.60 198092214 Hardware of Clock Module Fault
1-10M clock lost
Critical
1. board condition:
None
1-10M clock lost

198092215 Lost of synchronization
1.Alarm of OCXO not locking
Major
1. board condition:
1. The problem of crystal.

2. Board is fault.
Alarm of OCXO not locking:
urce 1PPS
Current Active Reference Source 1PPS Lost
Minor
Long term lost can cause clock and fame cannot be synchronous, and
soft switch cannot be achieved.
1. For the satellite receiver, the satellite receiver does not output 1PPS
1.Firstly,to check whether the configured referent signal is in
When air interface clock isn't configurated, or air interface clock sources
cannot be lock(clock source is interrupted seriously to beyond the clock
threshold, or crystal oscillator is error), alarm is reported.
Major
1. board condition:
board run normally.
services in the board are interrupted completely.
Does not configurate the air interface clock source. Or the air interface
clock source cannot be lock(clock source interrupted seriously, beyond
adjust threshold of crystal oscillator, or crystal oscillator fault).
Check whether the air interface clock source is configured. If it is not
When main core can't receive the slave's heartbeat in a while,alarm

is reported.
Critical
Base band subunit cannot work normally.
Base band subunit has fault.
Reset the board.
3.65 198092234 Embedded power type configuration
The type of the power is different from the actual configuration.
Major
The detection of the power alarm is influenced.
The type of the power is different from the actual configuration.
1. Reconfigure the power.
2. Replace the power.
3.66 198092235 Embedded power communication
The communication of the power is interrupted.
Major
The detection of the power alarm is influenced.
1. The link to the power is faulty.
3-40
1. Check whether the link to the power is normal.
ut Fault
SMR Output Fault
Critical
The rectifier is damaged.
1. Pull out the 1.rectifier and plug it in again, and make it powered on.
3.68 198092237 Embedded power Bat Under-Temp

The temperature of battery is less than Batt.UnderTemp.
Minor
The battery's service lifetime is influenced.
1. The battery's temperature is lower than the threshold value of

The temperature of battery is an invalid value.
Minor
The battery temperature detection is influenced.
1. The environment temperature exceeds the normal range allowed
The battery is faulty.

Critical
When all the battery is faulty, the base station will be powered down
after the AC power supply is powered down.
1. The battery is not installed, but the monitoring unit configured the
1. Check whether the battery is installed, and whether the battery

1588 clock link channel is unavailable.

Minor
For the case that only 1588 clock source is configured at OMC, if the
lost packet problem lasts for a long time, it is impossible to achieve clock
synchronization, frame synchronization and successful soft handover
There is no available 1588 clock link
1.Check whether the CC physical connection is normal.
198092242 Ir link LCV alarm

Ir link LCV(line code violation) error exceeds threshold, this alarm
is reported.
Warning
1. Board Status:
1. Poor fiber connection;

2. Optical module defect;
3. Ir interface chipset work abnormally.
1. Check the possible failure with the fiber optics and the optical module
DPD running status is abnormal.

Warning
I. Board Status:
Board Operation is normal
II. Service Impact:
RF output quality and service performance are affected
DPD chip runs abnormally.
The system can recover automatically without manual intervention.
When working voltage or gain of LNA is out of normal working range,

the system will give this alarm.
Major
I. Board Status:
Board Operation is normal
II. Service Impact:
Service coverage extent is affected
1. Board is not properly installed or backplane slot has a problem;
2. Internal LNA is damaged;
3. Internal LNA alarm detection circuit is broken, therefore, false alarm
is reported.
1. Replace the internal LNA of RRU.
This alarm is given when it detects that PA is in the closed status.

Minor
3-44
Service interruption
1. PA is disable by operation in OMCB.
2. Close PA in corresponding channel when Remote antenna over
VSWR alarm is reported.
1. Check setting of PA status in OMCB.
This alarm is reported when the system detects that TMA channel input
current is over threshold (135~140mA), but less than 200mA.
Major
1. Board Status:
Work normally
2. Service Impact:
Cell coverage is slightly affected
1. The configured threshold is not consistent with real TMA threshold;
1. Check if the alarm threshold of TMA power supply is configured
The temperature of PA exceeds over-high temperature threshold.

Critical
1. Board Status:
1. The fan at PA layer is abnormal, which causes a cooling fault.
High environmental temperature:

on alarm
Optical module out-of-position.
Minor
3-46
1. Board Status:
Optical module out-of-position.

1. Check if optical module and fiber have been installed at local board
RF board has detected that PLL is not locked.

Critical
1. Board Status:
1. Clock input from main control board is wrong;

2. Board hardware fault.
1. Check the current software version of BS and ensure it is the correct
The calibration file on TRx board is incomplete or damaged.
Minor
1. Board Status:
The corresponding board calibration data is incomplete or damaged.

1. Reset board.
2. Replace board.
3.81 198092251 a block check error of downlink IQ
DL IQ channel is error in receiving data.
Major
1. Board Status:
2. Service Impact:
Downlink communication is abnormal from UBPG to RRU
Downlink IQ channel receives wrong data
1. Check if the following alarm (clock abnormal) occurs in BBU.
tion alarm
Digital IF pre-distortion fault.
Major
3-48
1. Board Status:
Work normally.
2. Service Impact:
RF output quality is affected. The service on the board is down.
1. DPD chip runs abnormally;
2. Software operation on DPD is failed.
1. On NMS fault management interface, check if the following alarm
ing alarm
RRU doesn't send a heart-beat message to BBU.
Critical
1.Work normally.
2. Service Impact:
The service on the board might be down
RRU communication is broken or software is abnormal
1. Check if the board has "Board communication link is interrupted"
The output voltage of power module is abnormal.

Major
1. Board Status:
Power module output is abnormal.

1. Check the power input voltage of the power module. Replace the
age alarm
The input AC voltage of power module is higher than alarm threshold
280 V(error ±1V), or the direct current voltage of power module is
higher than alarm threshold 60 V(error ±1V).
Major
1. Board Status:
The input AC voltage of power module is higher than alarm threshold
280 V(error ±1V), or the direct current voltage of power module is
1. The AC input voltage of power module is higher than the alarm
The input AC voltage of power module is lower than alarm threshold

80 V(error ±1V), or the direct current voltage of power module is lower
than alarm threshold 36 V(error ±1V).
Major
1. Board Status:
The input AC voltage of power module is lower than alarm threshold

80 V(error ±1V), or the direct current voltage of power module is lower
1. The AC input voltage of power module is lower than the alarm

VSWR at antenna port is higher than limit(2.5~3.0).
Major
1. Board Status:
The value of VSWR is greater than (2.5~3.0), there is very strong

same-frequency interference signal, or RRU is faulty
1. Check the antenna failure.
number
Discontinuous frame number alarm, frame rate not received alarm
within 160ms.
Minor
3-52
1. Board Status:
Work normally.
2. Service Impact:
Board communication link is down. The board on the service is down.
1. Frame number is discontinuous.
2. There is no frame rate received within 160ms.
Replace the optical module/fiber of FS functionality board. Replace the
optical module used by the faulty optical port.
3.89 198092259 Battery low-voltage alarm

This alarm is reported when the battery is under voltage.
Minor
1. Board Status:
The battery voltage is very low.
cted at
This alarm is reported when the external device at a dry contact is faulty.
Minor
1. Board Status:
Work normally
It doesn't affect services.
Locate the alarm cause according to real external devices.
3-53
1. Replace the lightning protection device.
198092261 Outdoor lightning protection box alarm

Outdoor lightning protection box is faulty.
Minor
1. Board Status:
1. The lightning protection device is faulty because of lightning attack,

The breaker in an indoor lightning protection box is protected against

over current or turns in open circuit.
Major
1. Board Status:
1. The breaker is protected against over current or turns in open circuit.

alarm in
The lightning protection device in an indoor lightning protection box
has a fault.
Minor
1. Board Status:
1. The lightning protection device is faulty because of lightning attack,

198092264 Over-voltage alarm of main power input
This alarm is reported when the system detects that input voltage of the
main power at dry contact is abnormal.
Major
1. Board Status:
1. The input voltage of main power is abnormal.

2. The environment monituring unit (EMU) is faulty.
1. Check whether the input voltage of the main power module is
198092265 Main power input power-cut alarm

This alarm is reported when the system detects that main power input
at dry contact is abnormal.
Major
1. Board Status:
This alarm is reported when the system detects that main power input
at dry contact is abnormal.
Major
1. Board Status:

3-57
1. Check whether input voltage of the main power module is abnormal.
This alarm is reported when the system detects that the main power at
dry contact is faulty.
Major
1. Board Status:
1. The main power is faulty.

None
3.98 198092268 PWR monitoring unit alarm
This alarm is reported when PWR monitoring unit is abnormal.
Minor
1. Board Status:
PW monitoring unit is broken.

2. Replace the environment monitoring unit.
198092269 Over-high temperature of RU board

The temperature of RU exceeds over-high temperature threshold.
Critical
1. Board Status:
1. The device temperature is over high.
3. The air conditioner has a fault.

4. The temperature sensor in the fan subrack at control layer is faulty.
RU board
The temperature of RU exceeds slight-high temperature threshold.
Major
1. Board Status:
Work normally
The PA reduces its RF channel transmissionn power by 2db.
1. The device temperature is over high.
rse link
This alarm is given when the detected value of RSSI is below lower
threshold. However, this alarm will disappear when the value is lower
than recovery threshold, otherwise the alarm remains.
Minor
If only a channel has low RSSI value, capacity per cell may be reduced
and uplink coverage in the cell may shrink. If all channels have low
RSSI value, user uplink service cannot be accessed.
Receiving channel is broke.
Confirm that whether it is caused by software abnormality or hardware
rse link
This alarm is given when the detected value of RSSI is over higher
threshold. However, this alarm will disappear when the value is greater
than recovery threshold, otherwise the alarm remains.
Minor
Uplink coverage of the cell shrinks or user uplink service cannot be
accessed.
1. There is strong external interference.
2. Poor connection at antenna port causes Tx spurious emission,
which disturbs Rx.

Locate the interference problem. If it is strong external interference,
The temperature of PA exceeds slight-high temperature threshold.

Major
1. Board Status:
Work normally
The PA reduces its RF channel transmissionn power by 2db.
1. The fan at PA layer is abnormal, which causes a cooling fault.
2. PA is abnormal.
This alarm is reported when the communication between PA and

monitoring module is failed.
Critical
1. Board Status:
PA communication module has a fault or the cable is loosen, which
1. Reset the board.

This alarm is reported when the system detects that receiving channel
is unavailable because it is failed to initialize receiving channel chip
on RF board.
Critical
1. Board Status:
It is failed to initialize chips on RF board.

1. Reset the board.
When main control board cannot detect local benchmark clock, 61.44M
Critical
1. Board Status:

Hardware has fault.
1. Reset the board.
3.107 198092278 Abnormal power

After cell setup, the TRx board will report this alarm when it detects
that the absolute difference between digital power and analog power
exceeds threshold (>6dB).
Major
1. Board Status:
1. PA is not enabled.
2. PA transmit power is abnormal;
3. TRx board has a fault.
1. Turn on the power amplifier.
2. Replace the power amplifier.
3.108 198092279 Downlink analog power exceeds rated
This alarm is given when analog power exceeds rated power by
0.1~1dB for above 20 times.
Critical
1. Board Status:
1.Software is abnormal.
2.Hardware is broken.
1.If software is abnormal, find the problem and update software.
2.If hardware is broke, go to the flow of repairment.
3-63
eeds rated
The system will give this alarm when high layer software has detected
that digital power exceeds rated power (see notes) by 0.1~1dB for 20
times within one minute.
Critical
1. Board Status:
1. Input digital signal from BBU is wrong.

2. RRU software is abnormal.
3. RRU hardware is abnormal.
1. Reset board.
2. Replace board.
3.110 198092281 Downlink carrier baseband power is
The system will give this alarm when high layer software has detected
that digital power exceeds rated power (see notes) by 0.1~1dB for 20
times within one minute.
Warning
Decreased transmission power causes cell coverage to shrink. Or
services cannot be provided due to wrong transmission signals.
1. Input digital signal from BBU is wrong.
2. RRU software is abnormal.
3. RRU hardware is abnormal.
1. Reset board.
2. Replace board.
wer is low
This alarm is given when carrier analog power exceeds rated power
by 0.1~1dB for above 20 times.
Warning
Decreased transmission power causes cell coverage to shrink. Or
services cannot be provided due to wrong transmission signals.
1. Software is abnormal.
2. Hardware is broken.
1. If software is abnormal, find the problem and update software.
2. If hardware is broke, go to the flow of repairment.
198092283 Remote antenna VSWR alarm
VSWR at antenna port is higher than limit(1.5~2.0), but lower than
limit(2.5~3.0).
Major
1. Board Status:
2. Service Impact:
The service on the board is not affected.
Antenna VSWR is higher than limit(1.5~2.0) and lower than
limit(2.5~3.0), or there has strong interferential signals of the same
frequency, or RRU has fault.
1. Check the antenna failure.

198092284 Input reference clock is abnormal
This alarm is reported when 10% error has been detected on input
frequency clock, sent from main control board.
Critical
1. Board Status:
Work normally
System services work abnormally.
1. The reference clock sent from main control board is abnormal.
2. Backplane has a problem.
3. The board is abnormal.
4. The board logic is not downloaded.
1. Check whether the main control board has a clock alarm. If yes,
This alarm is reported when FPGA main clock and Serdes reference
clock signals on board are abnormal.
Critical
1. Board Status:
The internal clock is abnormal.

1. Open the version management function, check whether FS running
electric
This alarm is reported when the uplink frame at optical/electric port
is unlocked.
Critical
1. Board Status:
1. The optical fiber/electric cable between BBU and RRU is abnormal.

2. Board clock is abnormal.
3. RRU works abnormally.
1. Check whether there is a RRU alarm, which is not "not detected"
This alarm is given when channel downlink TDM frame is unlocked, i.e.
failure in detecting TDM frame header.
Critical
3-67
1. Board Status:
1. A channel board is not inserted.
1. Check whether the corresponding channel board works normally.
This alarm is reported when PLL chip cannot output FPGA main clock
or Serdes reference clock due to unlocked PLL.
Critical
1. Board Status:
PLL on the board works abnormally.

1. Open the Version Management function. Then check whether the
is not in
This alarm is reported when optical/electric port is not well connected.
Minor
1. Board Status:
1. Optical/electric module is in poor contaction with the board.

2. Optical/electric module is broken.
3. Optical/electric module has a broken port.
3.119 198092290 The uplink optical/electric link is
This alarm is reported when optical port has detected LOS or the value
of cable LCV exceeds its threshold.
Critical
1. Board Status:
Work normally
The cell services, associated to this optical port, are interrupted.
1. Either optical fiber or electric cable is broken.
1. Check whether there is a RRU alarm, which is not "not detected"

198092291 The input frame synchronous signal
The synchronous information, sent from main control board, is parsed.
This alarm is reported when the parsed information, for example, frame
frequency or frame number, is wrong.
Major
1. Board Status:
Work normally
System services are interrupted.
1. The output synchronous signal from main control board has a
1. Check whether the main control board has a clock alarm. If yes,
This alarm is reported when Rx fiber and Tx fiber are cross-connected

to the optical ports of the same FS board.
Critical
3-70
1. Board Status:
Work normally
The cell services, associated to the optical port, are interrupted.
1. Optical fibers are in cross connection. This is wrong.
2. RRU has a fault.
3. Board has a fault so that it sends a wrong control word.
1. Check whether the corresponding optical fiber is well connected and
The alarm will be reported when the receiving optical port of RRU in the
chain has no optical signal received.
Minor
Optical link is interrupted. This happens between two optical ports,
either from previous RRU to this RRU, or from this RRU to next RRU.
The Rx fiber is not well connected to optical port of RRU or optical
module is broken.
Rx port of
The alarm will be reported when the CPRI frame of RRU in the chain

Minor
Optical link is interrupted. This happens between two optical ports,
either from previous RRU to this RRU, or from this RRU to next RRU.
1. The Rx fiber is not well connected to optical port of RRU or optical
module is broken.
2. RRU receiving board is fault.
The alarm is reported when RRU detects that power voltage is lower
than a certain value.
Critical
1. Board Status:
Work normally
The corresponding cell cannot provide services.
1. At RRU side, main power source is abnormal.
2. The external power device of RRU is faulty.
1. Check whether the power cable at RRU side is abnormal.
2. Check whether the external power device has a fault.
Exception in MMC.
Critical
Board fails to power on.
1. MMC is not written.
2. MMC is broken.
1. Check whether the software version of the board and the PM board
The alarm is reported in CC board when product process fails to report
Minor
I. Board Status:
None.
II. Service Impact:
It will effect calling.
1. It has no Opt speed or TDM speed correspondingly.
2. Radio Mode is not valid.
3. Protocol is incompatible between FS and RRU.
1. Reconfigure TDM speed or Opt speed.
2. Check Radio Mode.
3. Reconfigure protocol of FS or RRU.
When ACOM major alarm,this alarm is reported.

Major
Service Impact:
Major fault occurs in ACOM, which might cause the performance of
corresponding cell to degrade.
ACOM major fault
1. Reset the equipment.
2. Replace the equipment.
When ACOM minor alarm,this alarm is reported.

3-73
Minor
Service Impact:
Minor fault occurs in ACOM, which might cause the performance of
ACOM minor fault
3.129 198092319 ACOM hardware fault

When ACOM hardware has a fault, this alarm is reported.
Major
Service Impact:
ACOM operation is abnormal, which might cause the performance of
Parameter error
1. Reset the associated RRU board.
3.130 198092320 ACOM communication link is
When ACOM communication link is interrupted, this alarm is reported.
Major
Service Impact:
Communication between ACOM device and the system is down, which
might cause the performance of corresponding cell to degrade.
1. ACOM device fault.
1. Check the communication cable between RET equipment and base
When ACOM software has a fault, this alarm is reported.

Major
Service Impact:
ACOM operation is abnormal, and the configuration will not take effect,
which might cause the performance of corresponding cell to degrade.
Parameter error
1. Reset the associated RRU board.
When AISG EEPROM is error, This alarm is reported.

Minor
Service Impact:
AISG operation is abnormal, which might cause the performance of
Parameter error
When AISG flash erase error, This alarm is reported.
Minor
Service Impact:
Parameter error
3-75

When AISG flash write error, This alarm is reported.
Minor
Service Impact:
Parameter error
When AISG other hardware has a error, This alarm is reported.
Minor
Service Impact:
Parameter error
When AISG other software has a error, This alarm is reported.
Minor
Service Impact:
Parameter error
When AISG RAM is error, This alarm is reported.

Minor
Service Impact:
Parameter error
When AISG UART is error, This alarm is reported.
Minor
3-77
Service Impact:
Parameter error
When ATMA major alarm, this alarm is reported.

Major
Service Impact:
Major fault occurs in ATMA, which might cause the performance of
ATMA major fault
When ATMA minor alarm, this alarm is reported.

Minor
Service Impact:
Minor fault occurs in ATMA, which might cause the performance of
ATMA minor fault
This alarm is reported when it is failed to set ATMA gain.
Major
1. Board Status:
1. Parameter error.
2. ATMA(ACOM) device link is interrupted.
3. ATMA(ACOM) device is not on-duty.
1. On NMS configuration management interface (tower top amplifier
When ATMA hardware has a fault, this alarm is reported.

Major
Service Impact:
ATMA works abnormally, which might cause the performance of
Parameter error
1. Reset EMC.
3.143 198092334 ATMA communication link is
When ATMA communication link is interrupted, this alarm is reported.
Major
Service Impact:
1. ATMA device fault.
1. Check the communication cable between ATMA equipment and
When ATMA software has a fault, this alarm is reported.

Major
Service Impact:
ATMA works abnormally, which might cause the performance of
Parameter error
Reset EMC.
3.145 198092336 Board configuration parameter error
During the period of starting configuration or board running, this alarm is
reported if a wrong configuration parameter is found. This configuration
parameter is delivered from main control board.
Major
1. Board Status:
2. Service Impact:
1.The system has no such board configuration parameter.
2.Configuration parameter error. 3. Hardware error .
Reset board.
3.146 198092337 RET motor fault
When RET motor has a fault, this alarm is reported.
3-80
Major
Service Impact:
Operation of RET motor is down, which might cause the performance
of corresponding cell to degrade.
RET motor fault
1. Open the Base station Configuration Management window, open
When RET hardware has a fault, this alarm is reported.

Major
Service Impact:
RET motor works abnormally, which might cause the performance of
1. RET hardware fault.
2. EMC fault.
Check the power adjusted antenna hardware.
3.148 198092340 RET motor can't adjust
When RET motor can't adjust, this alarm is reported.
Major
Service Impact:
RET motor can't adjust
When RET don't respond the adjusting command, this alarm is reported.
Minor
Service Impact:
RET motor don't respond the adjusting command
When AISG device communication link is interrupted, this alarm is

reported.
Major
Service Impact:
The system fails to communicate with AISG device, and fails to perform
management and alarm detection. If link interruption is caused by
device damage, performance of the corresponding cell will be degraded.
1. RET device fault.
1. Check the communication cable between RET equipment and base

When RET don't calibrated, this alarm is reported.

Major
Service Impact:
Operation of RET motor is down. Thus the configuration cannot take
effect.
RET don't calibrated
When RET data don't scaled, this alarm is reported.

Major
Service Impact:
effect.
RET data don't scaled
When RET position lost, this alarm is reported.

Minor
Service Impact:
effect.
RET position lost
3-83
When RET software has a fault, this alarm is reported.

Major
Service Impact:
RET motor works abnormally, which might cause the performance of
Parameter error
Check the system parameters.
3.155 198092352 Unmatched link mode at peer-end
The peer-end electrical Ethernet port has different link mode from this
end.
Warning
1. Board Status:
The Ethernet electrical port configured at peer end is inconsistent with
Select Ethernet Configuration function in the Configuration Management
Configuration is failed.
Major
Impact configuration.
Configuration is wrong or hardware is faulty.
Check if the configuration parameter from OMCB or CC is right and
the board is broken.
3.157 198092363 Faulty main power alarm

This alarm is reported when the system detects that the main power at
dry contact is faulty.
Major
1. Board Status:
1. The main power is faulty.

None
Calibrate operation is failed.

Major
It will affect service in total sector.
Calibrate operation makes mistakes.
1. Check if other alarms exists, such as over-heated alarm, clock alarm
The total sending power is abnormal.

Major
It will affect service in total sector.
The total sending power is lower than threshold.
1. Check whether the total power is normal.
al port is
This alarm is reported when optical module of optical port is not well
connected.
Critical
The optical module of optical port is not well inserted to UCI so that
optical port cannot work.
1. Optical module is in poor contact with UCI.
2. Optical module is broke.
3. UCI board is broke.
1. Remove and insert the optical module in corresponding to the board.
2. Replace the optical module in corresponding to the board.
3.161 198092375 UCI optical module of optical port has
This alarm is reported when optical module of optical port has detected
LOS or the value of cable LCV exceeds its threshold.
Critical
Optical signal is lost at optical port of UCI so that optical port cannot
work.
3-86
1. Rx/Tx optical fiber is wrongly connected.

2. Optical module is in poor contact with single board.
3. The optical module at UCI side is broke.
4. The optical module at RGPS side is broke.
1. Reset the RGPS forcibly.
l port is
This alarm is given when the receiver frame at UCI optical port is
unlocked, i.e. failure in detecting K-code header.
Critical
RPGS to UCI optical link is broke.
1. The optical fiber from RGPS to FS is abnormal or Optical module
is broke.
2. UCI works abnormally.
1. Reset the RGPS forcibly.
This alarm is reported when check the fiber delay adjust is overtime.
Critical
UCI fiber delay adjust is failed, so it cannot calibrate 1PPS of RGPS
and 1PPS or TOD cannot be output to CC also.
1. the antenna of RGPS is broke.
2. UCI board is broke.
3-87
1. Check whether the antenna of RGPS is normal.
Board FPGA inner PLL is unlocked.

Critical
Logic inner PLL is unlocked, so that the board communication may
be abnormal.
1.The clock from CC to UCI board is loss.
2.The FPGA of UCI board works abnormal.
1. Check whether the clock from CC to UCI board is normal.
2. Check whether the FPGA of UCI board version is right.
3.165 198092379 PA over power alarm

The output power of PA exceeds rated power by 2 dB~3 dB.
Critical
1.Work normally.
2. Service Impact:
Power amplifier output is off. No transmission power output exists on
RF channel. The service on the board is down.
1. Baseband power is abnormal, which causes very high input power of
1. Reset the board.
3.166 198092383 Distributing IQ resource is failed.

The alarm is reported when calculating IQ ranks is failed in CC board.
Minor
3-88
1. Board Status:
2. Service Impact:
1. Input parameter is not valid.
2. Bandwidth is not enough.
Reconfigure IQ on configuration management interface of OMCB.
3.167 198092384 It is failed to configurate IQ.
The alarm is reported when IQ configuration is failed in FS board.
Minor
1. Board Status:
2. Service Impact:
1. Input parameter is not valid.
2. Bandwidth is not enough.
Reconfigure IQ on configuration management interface of OMCB.
3.168 198092385 It is failed to configurate optical port
The alarm is reported when optical port speed configuration is failed
in FS board.
Minor
1. Board Status:
2. Service Impact:
It will effect RRU link and IQ configuration.
Optical port speed is not valid.
Reconfigure optical port speed on configuration management interface
of OMCB.
The alarm is reported when TDM port speed configuration is failed

in FS board.
Minor
1. Board Status:
2. Service Impact:
TDM port speed is not valid.
Reconfigure TDM port speed on configuration management interface of
OMCB.
3.170 198092387 It is failed to configurate RRU device
The alarm is reported when RRU device delay parameter configuration
is failed in FS board.
Minor
1. Board Status:
2. Service Impact:
It will effect fibre-optical delay calculating.
It is failed to check RRU topo configuration according to RRU rack.
Reconfigure RRU topo on configuration management interface of
OMCB.
3.171 198092388 It is failed to configurate power
The alarm is reported when the total power of all the board configurated
in OMCB exceeds available power of PM that cause power supply
configuration is failed.
Minor
3-90
1. Board Status:
It will effect board power supply.
2. Service Impact:
It will not effect service.
Power supply configuration is failed when the total power of all the
board configurated in OMCB exceeds available power of PM.
Reconfigure power supply on configuration management interface of
OMCB.
3.172 198092393 UES ethernet semiduplex alarm
Link is in semiduplex status.
Major
1. Board Status:
2. Service Impact:
It may cause data packet loss if there is a large quantity of data.
Link is in semiduplex status.
Check the physical linkmode configuration.
3.173 198092394 Several rectifiers faulty
2 or more rectifiers are faulty.
Critical
It may affect power module to carry load so that base station cannot
be properly powered.
1. Several rectifiers are faulty.
2. The faulty rectifiers are associated to input air switch. The input air
switch breaks.
3. Open phase happens.
1. Check working status of the faulty rectifiers.
2. Check whether open phase happens.
3. Replace the faulty rectifiers.
During energy-saving period, partial boards are powered down because

of fewer services.
Warning
1. Board Status:
No
No
During energy-saving period, partial boards are powered down because
of fewer services.
This requires no special handling. The powered-down boards will
be powered on automatically when energy-saving period finishes or
services increase.
E1 link self-loop is detected.

Major
1. Board Status:
E1 link self-loop is detected.
Check link connection.
3.176 198092409 GNSS antenna feeder alarm
This alarm is reported when GNSS antenna feeder is faulty.
Major
1. Board Status:
GNSS antenna feeder fault.

Check antenna feeder fault
iver has
This alarm is reported when the built-in-type GNSS receiver has a fault
or is unavailable.
Critical
1.Board Status:
GNSS receiver is broken.

Check the faulty GNSS antenna
nna has a
This alarm is reported when the built-in-type GNSS antenna has a
faulty feeder cable.
Major
1. Board Status:
GNSS antenna feeder is faulty.

3-93
Check the faulty GNSS antenna feeder.
This alarm is reported when one of the following situations happens in
Minor
1.Board Status:
1. RGPS receiver has a power cut problem.
1. Check whether RGPS has no electricity supply. If yes, handle the
This alarm is reported when the external-panel-type GNSS receiver

has a faulty feeder cable.
Major
3-94
1.Board Status:
The external-panel-type GNSS receiver has a faulty feeder cable.

Check the faulty antenna feeder.
This alarm is reported when CC has detected that the receiver mode
configured at background is different from that directly read from
foreground hardware.
Minor
None
1. The receiver mode is wrongly configured.
2. The receiver mode configured at background is inconsistent with
foreground.
1. If it is front-panel wiring, check whether the link between USR and
e GNSS
This alarm is reported when one of the following situations happens in
Minor
1.Board Status:
1. RGPS receiver has a power cut problem.
1. Check whether RGPS has no electricity supply. If yes, handle the
e GNSS
This alarm is reported when the external-backplane-type GNSS
receiver has a faulty feeder cable.
Major
1.Board Status:
The external-backplane-type GNSS antenna has a faulty feeder cable.

Check the faulty antenna feeder.
e GNSS
This alarm is reported when CC has detected that the receiver mode
configured at background is different from that directly read from
foreground hardware.
Minor
None
1. The receiver mode is wrongly configured.
2. The receiver mode configured at background is inconsistent with
foreground.
1. If it is front-panel wiring, check whether the link between USR and
198092426 GNSS cascading clock has an alarm

This alarm is reported when there is a link or satellite searching problem
in GNSS cascading clock mode.
Major
1.Board Status:
1. GNSS information fails to be transferred from previous-level board to
1. Check whether the inter-board cable is in normal state.

The alarm will be reported when the receiving optical port of RRU in
network has no optical signal received.
Major
The optical link in RRU network is broken (the receiving optical port of
RRU has no optical signal received).
The fiber is not well connected to optical port of RRU or optical module
is broken.
This alarm is reported when clock line is abnormal in stack mode.

Major
1. Board Status:
Work normally
Inter-frame services between master and slave frame are affected.
1. Stack clock line is not properly inserted.
2. Stack clock line is broken.
1. Remove and insert the stack clock line again.
2. Replace the stack clock line.
3.188 198092435 Inter-frame Ethernet link broken in
This alarm is reported when inter-frame Ethernet Eth1 link is broken
in stack mode.
Major
3-98
1. Board Status:
Work normally
Services of slave frame are interrupted.
1. ETH1 line is not properly inserted.
2. ETH1 line is broken.
3. Network port rates at both ends are different after the changing of
network port modes.
1. Remove and insert ETH1 line again.
This alarm is reported when it fails to synchronize slave clock with

master clock in stack mode.
Major
1. Board Status:
Work normally
Inter-frame services between master and slave frame are affected.
1. Stack clock line is faulty.
2. CC board on slave frame has a hardware fault.
1.Check whether stack clock line is firmly inserted.
2.Replace the stack clock line.
3.Replace the CC board on slave frame.
3.190 198092437 RU radio frequency group unavailable
This alarm is reported when RU channel cannot bear services during
calibration or other manual operations.
Major
1. Board Status:
RU cannot provide services properly during the period of some manual

operations (e.g. TOC measurement, OP training, calibration, radio
interference scanning).
Wait until the manual operations finish.
3.191 198092438 Device in low temperature
This alarm is reported when the system detects that a device stays in
very low temperature, lower than configured lower limit.
Major
1.Board Status:
Work normally
A board or the system may work improperly.
1. Environmental temperature is out of normal range.
2. SA board is faulty.
1. Check whether environmental temperature is too low (lower than
ase station
Uplink transport port of a base station operates in a different mode
from configured one.
Minor
1. Board Status:
1. The configured link mode at background is wrong.

2. The link mode at peer end changes.
3. Network cable is inserted again after it has been removed for a long
1. Check the configuration of peer end.
AC phase voltage is unbalanced.

Major
The output of 3-phase rectifier is affected, but there is no any influence
on single-phase rectifier.
1.AC power network has a problem.
2. The monitoring unit is broken, which leads to false detection.
1. Check the value of AC input voltage.
3.194 198092448 High AC phase current of built-in
AC phase current is high.
Major
1.If AC phase current stays high for a long time, AC input current must
1.AC input phase current is larger than the threshold, which is used to
1.Check AC phase current threshold of the monitoring unit.
f built-in
AC phase is missing.
Major
1.Rectifier may not work properly.
2.It affects power supply to a base station.
1.AC input cable is fell off.
1.Check whether AC input cable is correctly connected.
of built-in
The battery's voltage is lower than power-cut setting value so that all
power load has to be powered down.
Critical
It affects power supply to a base station.
1.System temperature is lower than low-temperature cut-off threshold.

1.Check battery's temperature.
LLVD1 extended branch is broken.

Major
The circuit breaker in the LLVD1 extended branch is opened so that the
connected base station is powered down.
1.When the battery's voltage reduces to LLD1 voltage threshold, the

1.Check whether the battery's voltage is lower than LLVD1 voltage.
LLVD1 branch is broken.

Major
The circuit breaker in the LLVD1 non-extended branch is opened so
that the connected base station is powered down.

LLVD2 branch is broken.
Major
The circuit breaker in the LLVD2 extended branch is opened so that the
connected base station is powered down.

Battery's cut-off extended branch is broken.
Major
The circuit breaker in the cut-off extended branch is opened so that the
connected battery doesn't work and base station cannot be supplied
with power.

Battery's cut-off branch is broken.
Major
3-106
The circuit breaker in the cut-off non-extended branch is opened so

that the connected battery doesn't work and base station cannot be

built-in
Battery's current is abnormal.
Minor
The battery may be over-charged or under-charged. This will affect
battery's performance and base station may not work properly.
1.The monitoring unit has a problem.
2.The configured parameter for the battery's current is wrong.
Replace the monitoring unit.
3-107
in power
CAN bus is abnormal.
Minor
The communication with the rectifier is interrupted. This will affect
battery's performance and management function.
CAN bus is interrupted.
Check whether CAN bus cable is fell off.
3.204 198092458 Abnormal battery of built-in power
Abnormal status is detected for the battery.
Critical
It doesn't affect power supply to a base station. But energy-saving
control will be affected.
1. The battery discharging ability is not strong.
2. The battery is not well charged.
Replace the battery.
3.205 198092459 Abnormal input dry contact of built-in
The input dry contact gives an alarm.
Critical
It doesn't affect power supply to a base station. But the dry contact
connected device may not report an alarm properly.
2.The input detection hardware has a problem.
2. Check SCDB (hardware circuit board).
built-in
Environmental temperature is higher than high-temperature cut-off
threshold so that the battery is removed.
Critical
It affects power supply to a base station.
This alarm is reported when frame synchronization is unsuccessful

between BBU subracks.
Minor
1. Board Status:
The clock phase provided by CC board in real application environment
1. In stack configuration, check whether the clock cable is tightly

When there is a fault on the User-defined dry contact, the alarm is

reported.
Minor
1. Board Status:
2. Service Impact:
No impact on service
There is a fault on the User-defined dry contact.
Perform different process methods according to the type of the exterior
devices.

reported.
Minor
1. Board Status:
2. Service Impact:
devices.

reported.
Minor
1. Board Status:
2. Service Impact:
3-110

reported.
Minor
1. Board Status:
2. Service Impact:
devices.

reported.
Minor
1. Board Status:
2. Service Impact:
devices.

reported.
Minor
3-111
1. Board Status:
2. Service Impact:

reported.
Minor
1. Board Status:
2. Service Impact:
devices.

reported.
Minor
1. Board Status:
2. Service Impact:
devices.

reported.
Minor
1. Board Status:
2. Service Impact:
devices.

reported.
Minor
1. Board Status:
2. Service Impact:
devices.

reported.
Minor
1. Board Status:
2. Service Impact:
3-113

reported.
Minor
1. Board Status:
2. Service Impact:
devices.

reported.
Minor
1. Board Status:
2. Service Impact:
devices.

reported.
Minor
3-114
1. Board Status:
2. Service Impact:

reported.
Minor
1. Board Status:
2. Service Impact:
devices.

reported.
Minor
1. Board Status:
2. Service Impact:
devices.

reported.
Minor
1. Board Status:
2. Service Impact:
devices.
reported.
Minor
1. Board Status:
2. Service Impact:
devices.

reported.
Minor
1. Board Status:
2. Service Impact:
3-116

reported.
Minor
1. Board Status:
2. Service Impact:
devices.

reported.
Major
1. Board Status:
2. Service Impact:
devices.

reported.
Major
3-117
1. Board Status:
2. Service Impact:

reported.
Major
1. Board Status:
2. Service Impact:
devices.

reported.
Major
1. Board Status:
2. Service Impact:
devices.

reported.
Major
1. Board Status:
2. Service Impact:
devices.

reported.
Major
1. Board Status:
2. Service Impact:
devices.

reported.
Major
1. Board Status:
2. Service Impact:
3-119

reported.
Major
1. Board Status:
2. Service Impact:
devices.

reported.
Major
1. Board Status:
2. Service Impact:
devices.

reported.
Major
3-120
1. Board Status:
2. Service Impact:

reported.
Major
1. Board Status:
2. Service Impact:
devices.
reported.
Major
1. Board Status:
2. Service Impact:
devices.

reported.
Major
1. Board Status:
2. Service Impact:
devices.

reported.
Major
1. Board Status:
2. Service Impact:
devices.

reported.
Major
1. Board Status:
2. Service Impact:
3-122

reported.
Major
1. Board Status:
2. Service Impact:
devices.

reported.
Major
1. Board Status:
2. Service Impact:
devices.

reported.
Major
3-123
1. Board Status:
2. Service Impact:

reported.
Major
1. Board Status:
2. Service Impact:
devices.

reported.
Major
1. Board Status:
2. Service Impact:
devices.

reported.
Major
1. Board Status:
2. Service Impact:
devices.

reported.
Major
1. Board Status:
2. Service Impact:
devices.

reported.
Major
1. Board Status:
2. Service Impact:
3-125

reported.
Major
1. Board Status:
2. Service Impact:
devices.

reported.
Major
1. Board Status:
2. Service Impact:
devices.

reported.
Critical
3-126
1. Board Status:
2. Service Impact:

reported.
Critical
1. Board Status:
2. Service Impact:
devices.

reported.
Critical
1. Board Status:
2. Service Impact:
devices.

reported.
Critical
1. Board Status:
2. Service Impact:
devices.

reported.
Critical
1. Board Status:
2. Service Impact:
devices.
3.258 198094800 SRIO Communication Abnormal

Serial Rapid IO switch works improperly in the board.
Minor
If this alarm can be cleared timely and the frequency of occurrence
of this alarm is low,it will impact services beared by the board a
little.Otherwise,all the services beared by the board will be interrupted.
1.Software fault.
2.Hardware fault.
1.Reset the faulty BPL board.
2.Replace the faulty BPL board.
3-128
CC board can't receive keep-alive message from the peripheral BPL

board.
Major
Service running on this core maybe interrupted,the board process
ability descends.
1.Software fault.
2.Hardware fault.
1.Reset BPL board.
2.If the alarm didn't recovered after BPL reset, please replace the faulty
BPL board.
3.260 198094829 eBBU synchronization abnormal

eBBU synchronization state is under unhold status and can not lock
any configured clock source.
Critical
Affect air interface syncronization state,cell blocked,can not establish
service cell.
The PLL is under holdover, free oscillation or auxiliary phase control
state over a period of time defined by alarm threshold.
1.Check if there is clock source alarm,and handle it.
2.Check if CC board is running correctly.
3.261 198096550 Alarm of fiber configuration

The optical port is configured, but the fiber length or rate mismatch.
Critical
The optical port cannot enter normal work state.
Optical module does not match.
Re-configurate optical port or replace optical module in practice.
RRU connected to the BBU unconfigured.

Major
The RRU cannot work normally.
There is a unconfigured RRU along with this BBU port, or the last
RRU's downlink port is connected to BBU.
Remove redundant RRU, or configure the RRU correctly.
3.263 198096552 Difference of fiber time delay of two
RRUs in same sector exceeded system limit
Difference of fiber time delay of two RRUs in same sector exceeded
system limit.
Major
In downlink, the measurement of optical fibre's delay may be
failure,thereby the RRU can not enter normal work state.
Difference of fiber time delay of two RRU in one sector exceeded
system limit(usually 32 chips).
1. Reboot all RRUs in this sector to recalculate the fiber time-delay.
RRU Type is not consistent with configuration type.
Critical
The RRU can not enter normal work state.
RRU Type is not consistent with configurated type.
Check the real and configurated type of RRU, be sure that they are
same.
3-130
n BBU
Failure of optical decoding in BBU.
Major
Those RRUs attached to BBU via this optical port maybe not provide
service.
Serdes data signal is lost.
If normal, reset board, else replace it.
3.266 198096555 Failure of optical decoding in RRU
Failure of optical decoding in RRU.
Major
The RRU containing the optical port or the next RRU connected via the
optical port may be lost to BBU.
Serdes data signal is lost.
1. Check whether connection between RRU and fiber is normal, or
IQ link input loses lock.

Major
The quality of service tend to decrease.
IQ link input lose lock.
1. Check whether the Baseband Board and IQ(SBMP of B322) board is
abnormal
Baseband IQ data power from BBU exceeded the rated power or lower
than the least power.
Major
The RRU will not establish the frequecy successfully.
The baseband IQ data power that BBU sends to RRU extended or
lower than rated power.
Check the state and configuration of BBU, or change the port with that
of stable RRU to figure out the problem.
3.269 198096558 Guide frequency that BBU sends to
RRU DwPCH power from BBU exceeded the rated power or lower
than the least power.
Major
The RRU will not establish the frequecy successfully.
The DwPCH power that BBU sends to RRU extended or lower than
rated power.
Check the state and configuration of BBU, or change the port with that
of stable RRU to figure out the problem.
3.270 198096559 RRU adjust channel or adjust cable
RRU adjust channel or adjust cable fault.
Major
It causes the failure of the antenna adjustment of the RRU.
Antenna adjust channel fault, or adjust cable disconnected(RRU with
muti-channel has an antenna adjust port which is connected to the
outside antenna adjust port by a cable).
1. Check whether adjust cable link correctly.
2. Check whether the cable is good.
3. replace the RRU.
3-132
nk alarm
Master and slave monitor link alarm.
Major
The primary RRU and the secondary RRU can not work in concordance,
only one of them can be used.
1. Master/slave control failure;
2. 485 master/slave cable pins error.
1.Switch master/standby clock cable.
a channel
The amplitude or phase among TX channels or RX channels is different.
Major
The radio signal may be affected.
When difference is too much between channels in antenna adjusting,
Antenna adjusting ends. Maybe problem exist in other place.
1. Software start to use standard offline parameter.
2. Check if offline parameter in eeprom is normal.
3. Replace RRU.
3.273 198096562 RRU self check failed when power on

RRU self check failed when power on.
Major
The RRU can not work normally.
1. Channel DAC/DUC/DDC initialization failure;
Replace RRU.
3-133
RRU device alarm.

Major
It affects the antenna adjustment of the RRU, and also has affect to
transmit or receive RF signal. Consequently affect telecom quality.
Usually offline parameter is abnormal; sometimes maybe RRU Board is
not plug in.
1. Software start to use standard offline parameter.
Configuration parameter of RRU external device not consistent with
real parameter.
Major
The device outside the RRU may not work normally.
Configurated type of RRU external device not consistent with real type.
Check the real type and configurated type of RRU external device to
make them the same.
3.276 198096568 RRU used power module is too hot.

RRU used power module is too hot.
Major
RRU output power is adjusted downwards.
RRU used power module is too hot.
If the power module continuously stays at high temperature, for
example, for more than five days, please replace the RRU.
k failure
Read and check the RRU saved offline parameter, but the check
process fails.
Major
The antenna may not be properly calibrated. As a result, RF signals
may not be properly transmitted or received and service quality is
surely affected.
Read and check the RRU saved offline parameter, but the check
process fails.
1. Software enables standard offline parameter.
2. Check whether the offline parameter saved in EEPROM is correct.
3. Replace the RRU.
198098431
Minor
1. Board Status:
Work normally
Cell coverage is affected.
1. The threshold configured at background is inconsistent with typical
1. Check the alarming threshold configured at background. Is it wrongly
rm due
Channel current is larger than the maximum value allowed by
AISG/NSBT power moduel.
Minor
1. Board Status:
Work normally
Cell coverage is affected.
1. The antenna system is in the status of short circuit.
2. The connector at NSBT port has a short-circuit problem.
3. RRU equipment has a short-circuit problem.
1. Check whether the configured voltage at AISG/NSBT port is
There is a big difference between transmission power at antenna port

and digital power.
Minor
1.Board Status:
Work normally
Services and cell coverage are affected.
The transmission power at antenna port has big difference from digital
power, bigger than alarm threshold.
1. Check whether calibration is successful.
djustment
The closed-loop power control process tries to adjust the power at
antenna port, but the adjusted value exceeds a normal range.
Minor
1.Board Status:
Work normally
RRU transmission power becomes inaccurate.
The closed-loop power control process tries to adjust the power at
antenna port, but the adjusted value exceeds a normal range.
1. Check whether RRU environmental temperature exceeds normal
working range.
2. Check whether PA gain changes greatly as temperature drifts.
3.282 198098436 Failure in configuring power level

Failure in configuring power level.
Minor
3-137
1.Board Status:
Work normally
RRU transmission power becomes inaccurate.
Failure in configuring power level
Check whether the static power level configured at background is legal.
4-2
4-2
4-3
4-3
4-3
4-4
4-4
4-5
4-6
4-6
4-7
4-7
4-8
4-8
4-9
4-9
4-10
4-10
4-11
4-12
4-12
4-13
4-13
4-13
4-14
4-14
4-15
4-15
4-16
4-16
4-16
4-17
4-17
4-17
4-18
ecause
This alarm is reported when the board temperature exceeds upper limit
and cannot work properly.
Major
1. Board Status:
1. The board surface encounters high temperature, exceeding upper
2. The board internal temperature is over high.

1. Check whether the dustproof net is blocked.
This alarm is reported when the top cover of a cabinet is not closed.
Major
1.Board Status:
1. View the relevant network management interface and finds the dry
1. Check whether the top cover is closed. If not, close it.
MP voltage.
Minor
Affect the power supply of the boards that they cannot bear any service.
1. When the MP voltage reported by PM/PSA board exceeds the upper
Replace the PM/PSA board.

4.4 198092038 PP voltage abnormal
PP voltage.
Major
Affect the power supply of the boards that they cannot bear any service.
1. When the PP voltage reported by PM/PSA board exceeds the upper
1. In a case that PM is configured in master/slave mode, check whether

the PM panel has a switch. If yes, please set it to be ON.
Over current of MP.

Minor
1. Board Status:
The MP current status of PM/PSA board's load is checked periodically.

If over-current is detected, this alarm is reported.
1. Remove and insert the corresponding board.
Over current of PP.

Minor
1. Board Status:
The PP current status of PM/PSA board's load is checked periodically.
If over-current is detected, this alarm is reported.
1. Remove and insert the corresponding board.
Fan failure.
Minor
1. Board Status:
1. Fan failure.
2. The fault with the environment monitoring unit.
1. Check whether the fan power supply link is normal.
2. Replace the fan.
198092042 Abnormal temperature at air intake

The temperature at air intake is abnormal.
Minor
1. Board Status:
In the case of high temperature at air intake:

198092043 Abnormal temperature at air outlet

The temperature at air outlet is abnormal.
Minor
I. Board Status:
In the case of high temperature at air outlet:
This alarm is reported when a door control sensor is used but the
door is not closed.
Major
1. Board Status:
1. Check whether the door is closed. If not, please close the door.
2. Replace the cable, which is connected to the door control sensor.
198092045 Flooding alarm

This alarm is reported when the flooding sensor connected at a dry
contact detects a flooding situation.
Minor
1. Board Status:
1. Check whether the base station is flooded. If yes, power off the
This alarm is reported when the smog sensor connected at a dry

contact detects a smog situation.
Minor
1. Board Status:
1. Check whether there is smog inside the base station. If yes, power
None
Minor
1. Board Status:
Work normally
No impact.
1. Check whether someone enters the equipment room.

2. Check whether the cable connected to the infrared sensor is good.
3. Check whether the infrared sensor is good.
4.14 198092048 Air conditioner fault

None
Minor
1. Board Status:
1. Check whether the cable connected to the air conditioner is good.
198092053 Voltage of DC input is abnormal.

Voltage of DC input is abnormal.
Major
1. Board Status:
2. Service Impact:
The lightning protection is invalid.
When the input voltage of PM board is higher than the upper threshold,
it is over-voltage.
When the input voltage of PM board is lower than the lower threshold,
it is under-voltage.
Over-voltage: Check whether the input voltage of DC supply system is
FCE-fan failure
4-9
Minor
1. Board Status:
1. Fan failure.
2. The fault with the environment monitoring unit.
1. Check whether the fan power supply link is normal.
2. Replace the fan.
The environment temperature is lower than environment
under-temperature that is set.
Minor
The battery's capacity is influenced.
1. The environment temperature is lower than the threshold value for
alarm.
1. Check the temperature in the equipment room, and improve the
The environment temperature is higher than environment

over-temperature that is set.
Minor
4-10
1. The battery's capacity is influenced.

2. The maximum load capacity of the rectifier is influenced.
3. The system security is influenced, fire might be caused due to
over-temperature.
1. The environment temperature is higher than the threshold value

The environment temperature is an invalid value.

Minor
The equipment environment temperature detection is influenced.
1. The environment temperature exceeds the normal range allowed
The environment humidity is lower than Environment under-humidity

that is set.
Minor
The antistatic capability of the power supply is influenced, which might
cause equipment damage.
1. The environment humidity is lower than the threshold value for alarm.
1. Check the humidity in the equipment room, and improve the
The environment humidity is higher than Environment over-humidity

that is set.
Minor
The anti-insulation and crush-resistance capability of the power supply
is influenced, and the board tends to be affected by damp and corrosion.
1. The environment humidity is higher than the threshold value for
alarm.
The environment humidity is an invalid value.

Minor
The equipment environment humidity detection is influenced.
1. The environment humidity exceeds the normal range allowed in
The sensor detects the smoke.

Critical
The system security is influenced, and the system might be on fire.
1. The smoke alarm signal is detected.
2. The smoke sensor is damaged.
1. Check whether there is any smoke. If there is, then disconnect the
The sensor detects the water.

Minor
The system security is influenced.
4-13
1. The flooding alarm signal is detected.

1. Improve the equipment room condition.
4.25 198092113 Embedded power Door Magnet Alarm

The sensor detects that the equipment room's door is opened.
Minor
The burglarproof security of the equipment is influenced.
1. The equipment room's door is opened.
1. Check whether the door is closed.

The sensor detects that the access control of the cabinet is not closed.
Major
1. The cabinet's door is opened.
1. Check whether the door is closed.
The sensor detects that the glass is broken.

Minor
1. The relevant alarm signal is detected.
1. Check whether the equipment room's glass is broken.
The communication of the system environment monitoring unit is

interrupted.
Major
The normal detection of environment parameters is influenced.
1. The power supply is not configured with the environment monitoring
1. Check whether the monitoring unit's setting is in accordance with the
nger Fault
The heat exchanger is damaged or the temperature is beyond the
allowed range.
Major
The normal heat dissipation of the power supply is influenced.
The board temperature exceeds its alarming threshold.

Minor
If board temperature is over high or over low, the board may not work
properly.
The board temperature is over high or over low, exceeds its alarming
thresholds.
1. Check whether the fan works properly.
4.31 198092307 Slight-high temperature of board

The board temperature exceeds slight-high temperature threshold.
Warning
1. Board Status:
1. Environmental temperature exceeds a threshold.

2. The fan is faulty.
3. The temperature sensor on the board is faulty.
The board temperature exceeds over-high temperature threshold.

Major
The board may not work properly. As a result, services borne on the
board are interrupted.
1. Environmental temperature exceeds a threshold.
2. The fan is faulty.
3. The temperature sensor on the board is faulty.
Remote MEP detected by CCM is broke.

Major
It will affect stability of ethernet link.
Remote MEP detected by CCM is broke.
Please check ethernet transmission link and configuration of
transmission device.
4.34 198092372 CCM Message Error
The message send by CCM has error.
Major
4-17
The message send by CCM has error.

4.35 198092373 CCM Xconnect Error

CCM message has conflict with configuration.
Major
CCM message has conflict with configuration.
Performance Measurement Rule Library Unavailable

BOOT software upgrade failure
Board communication link is interrupted
SNTP time adjustment failure alarm
Clock reference source configuration error
Failure in loading software
Failure in synchronizing the version of master board with slave board
Running software version doesn't exist
DOM is lack of space
Failure in synchronizing software version of master control board
Failure in repairing specification package
Wrong board insertion
Abnormal software in specification package
LMT login alarm
Failure in uncompressing LMT software
Board software fault
Line clock has the fault
SyncE clock has the fault
The fan control policy is not existed
Board initialization
Product process is abnormal
Configuration Fail
CPU over loading highly alarm
CPU over loading
Running software rollback
Board hot patch fault
Failure in finding this board-related software ID
MMC running software version doesn't exist
Carrier frequency configuration error
Center frequency configuration error
Work pattern configuration error
IQ parameter configuration error
Delay parameter configuration error
Carrier power configuration error
1PPS+TOD source fault
1PPS+TOD standby source fault
SyncE clock unavailable (SyncE+1588)
5-1
198092432 Optical modules have mismatched transmission distance
5.1 198094815 Performance Measurement Rule Library

Cause new loading rule library unusable and subsequent granularity
data statistics abnormal.
Major
Cause new loading rule library unusable and subsequent granularity
data statistics abnormal.
1.Database access failure.
2.Rule library configuration restrictions check failure.
3.Allocate UB failure.
1.LMT or OMC reconfig a new usable rule library.
2.Reset the eBBU to handle,or perform eBBU version problem location.
5.2 198096567 BOOT software upgrade failure

RRU boot version upgrade failure
Minor
Boot cannot be upgraded to new version. After rollback, RRU can run
normally.
During RRU boot upgrading process, either flash writing or boot
handover fails, which causes boot version to be rolled back.
Try to upgrade boot version manually. If it fails again, please replace
RRU.
5.3 198092010 Board communication link is interrupted

This alarm is reported when the communication link between peripheral
board and master main control board, or between slave main control
board and master main control board.
Critical
5-2
I. Board Status:
1. The board that has been configured does not exist on the rack.
1. In stack mode, check whether inter-frame network cable connection
SNTP server doesn't boot or its link has a fault.

Minor
I. Board Status:
II. Service Impact:
System time is inaccurate, but service is not affected.
1. IP address configuration for SNTP time adjustment server is wrong.
2. SNTP server is faulty.
3. Network problem exists.
1. Check whether SNTP Server Address is correct.
uration
During the period of starting configuration or board running, this alarm is
reported if a wrong configuration parameter is found. This configuration
parameter is delivered from main control board.
Major
5-3
1. Board Status:
1. Parameter configuration does not exist.

2. Parameter configuration is wrong.
Reset board.
5.6 198092017 Failure in loading software
This alarm is reported when the CPU/DSP/FPGA on a board fails to
load software.
Major
1. Board Status:
All services borne on the board are interrupted.
1. The software version saved on the main control board is wrong.
2. This board has a hardware fault.
1. Log in Software Version Management interface and download the
ersion of
This alarm is reported by the slave board when it fails to synchronize
version files with master board.
Major
1.Board Status:
The slave board fails to synchronize version files saved in relevant

directory with the master board.
1. Log in Software Version Management interface and download the
specification package again.
2. Reset the slave board.
5.8 198092022 Running software version doesn't exist.

This alarm is reported when the main control board finds that the
running software version doesn't exist.
Major
1.Board Status:
1. Running software is broken.

2. Runing software is missing.
3. The running software has no associated SWID.
Log in Software Version Management interface and download correct
This alarm is reported when DOM has no sufficient space.
Minor
5-5
1. Board Status:
Work normally
There is no impact on services.
DOM has no sufficient space.
Log in Software Version Management interface, then delete slave
version package file and firmware package file.
5.10 198092025 Failure in synchronizing software
version of master control board
This alarm is reported when the master control board fails to
synchronize version files with slave board.
Major
1. Board Status:
The slave control board resets.
The master/slave changeover function cannot be performed.
1. The software version associated to the master control board is
wrong.
2. The DOM on the slave board is lack of space.
3. The standby control board has a hardware fault.
1. Delete all files from the slave control board except for those saved
During board powered-on process, the system detects that the

specification package flag is abnormal. In this case, the system starts
to repair the specification package. This alarm is reported when the
repairing operation is unsuccessful.
Critical

1. Board Status:
Specification package fails to be repaired.

Enter Software Version Management interface to download the
specification package again. After that, activate it.
5.12 198092029 Wrong board insertion

The main control board has detected that the inserted board to
a physical slot is different from that configured in the network
management system.
Major
1. Board Status:
The board cannot boot properly.
The board cannot work properly. All services borne on it are interrupted.
1. The board is wrongly configured as shown in the Configuration
Management interface.
2. A wrong board entity is inserted.
1. Enter Configuration Management interface to correct the board
During version consistency check, if the version in a specification

package doesn't exist in DOM or is broken, this alarm is reported.
Major
1. If running specification package or its running patch is abnormal, the

During version consistency check, if the version in a specification
package doesn't exist in DOM or is broken, this alarm is reported.
Enter Software Version Management interface and reload software
The alarm is reported when LMT is logged in

Warning
None
The alarm is reported when LMT is logged in, and is resumed when LMT
is logged off(The LMT existence time can be calculated according to
the time of alarm being reported and the time of alarm being resumed) .
None
5.15 198092066 Failure in uncompressing LMT
During the VMP powered-on process, version software is downloaded.
This alarm is reported when it is failed to uncompress LMT software
in the web directory.
Minor
None
1. LMT software is illegal.
2. DOM is lack of space.
Check whether the LMT software is created correctly. Then download it
again and activate the specification package.
A faulty board fails to download/load/uninstall software

Major
I. Board Status:
1. The board software saved on the main control board uses wrong
1. Enter the Software Version Management interface to download and
5.17 198092309 Line clock has the fault.

This alarm is reported when CC board fails to detect reference clock
signal from the corresponding line or the quality of clock signal is poor.
Minor
1. Board Status:
1. Check whether reference source is wrongly configured.

198092310 SyncE clock has the fault.
This alarm is reported when one of the problems occurs: the quality of
synchronous Ethernet clock, extracted from an SSM, is poor; SSM is
lost; logic clock signal cannot be detection; or quality of clock reference
source is poor.
Minor
1. Board Status:
1. Check whether reference source is wrongly configured.

existed
It is failed to find a fan control policy for current SA or FCE board.
Major
1. It affects speed auto-adjustment of the corresponding fan.
2. Both base station and the relevant boards have too high temperature.
1. The mapping file between policy and scenario is not delivered.
2. The mapping file between policy and scenario is incomplete.
3. The policy file is not delivered.
4. The policy file is incomplete
1. Re-deliver the file about mapping relation between policy and
scenario.
2. Re-deliver the policy file.
5.20 198092348 Board initialization

This alarm is reported when a board reboots and then enters into the
initial state.
Major
1. Board Status:
The board is initialized.
2. Service Impact:
Board services are interrupted during board initialization.
1. Reset board command is issued by user.
2. The board is powered on and reboots.
3. Automatic board reset is caused by software error.
5-11
The alarm will be restored after board initialization. No handling is
5.21 198092360 Product process is abnormal.

The status of product process is abnormal.
Major
The product process works abnormally.
The product process is not dispatched in time.
Reset product process
Configuration makes mistakes.

Major
RRU cannot work normally and affect system service.
configuration makes mistakes.
1. Check the appended information of the alarm, Check if the OMC
configuration data is right.
2. Change the board.
5.23 198092390 CPU over loading highly alarm

An alarm is given when the system has constantly detected CPU usage
exceeds high alarm threshold.
Major
1. Board Status:
The system is in traffic peak period and the traffic is heavy.
1. Check if the system is in traffic peak period.

2. If it is non-peak period, it is recommended to evaluate network
planning in depth and optimize network planning.
An alarm is given when the system has constantly detected CPU usage
exceeds low alarm threshold.
Minor
1. Board Status:
The system is in traffic peak period and the traffic is heavy.

1. Check if the system is in traffic peak period.
2. If it is non-peak period, it is recommended to evaluate network
planning in depth and optimize network planning.
5.25 198092395 Running software rollback

The alarm is reported when the software of main control board rollbacks.
Major
1. Board Status:
2. Service Impact:
Board services are down.
Error happens when update software.
Check whether version file is correct in the active Software Package, at
the same time download and active the Software Package again.
5.26 198092396 Board hot patch fault

A faulty board fails to download/upload/uninstall hot patch.
Minor
5-13
1. Board Status:
1. The board's software version, which is saved on the main control
1. Re-download the hot patch software version on the software
It is failed to find board software ID according to hardware information

set of the faulty board.
Major
1. Board Status:
1. The content of R_SWID table saved on CC board is incomplete.
1. If the specification package in base station is not in the form of
on doesn't
This alarm is reported when the main control board finds that MMC
running software version doesn't exist.
Warning
1. Board Status:
1. MMC running software is broken.

2. MMC running software is lost.
3. MMC running software doesn't exist in the specification package
Enter the Software Version Management interface to download correct

specification package again.
5.29 198092403 Carrier frequency configuration error

This alarm is reported when Carrier frequency is out of the rated range
of center frequency or duplex range.
Critical
1. Board status:
The configured carrier frequency is out of the defined range of center
The alarm will be recovered automatically when carrier frequency is

configured within the rated range of center frequency and duplex range.
on error
This alarm is reported when a board has detected that the delivered
center frequency from CC board is wrong. This happens during initial
or running period.
Critical
1.Board status:
Work normally.
1. Carrier frequency is not configured in the system.
2. The carrier frequency is wrongly configured.
3. Hardware is faulty.
1. Configure correct carrier frequency
2. Reset the board
5.31 198092405 Work pattern configuration error

work pattern from BBU is wrong.
Critical
1.Board status:
Work normally.
1. Work pattern is not configured in the system.
2. The work pattern is wrongly configured.
Configure correct work pattern
5.32 198092406 IQ parameter configuration error
IQ parameter from BBU is wrong.
Critical
1.Board status:
Work normally.
1. IQ parameter is not configured in the system.
2. The IQ parameter is wrongly configured.
Configure correct IQ parameter
5.33 198092407 Delay parameter configuration error
delay parameter from BBU is wrong.
Critical
1.Board status:
Work normally.
The delay parameter is wrongly configured.
Check delay parameter in BBU
5.34 198092408 Carrier power configuration error
carrier power from BBU is wrong.
Critical
1. Board status:
1. Carrier power is not configured in the system.

2. The carrier power is wrongly configured.
Configure correct carrier power

198092412 1PPS+TOD source fault
1PPS+TOD reference source doesn't receive messages via serial
port; 1PPS+TOD reference source has unavailable PPS (pulse per
second) status; 1PPS+TOD reference source cannot obtain time of day
information for a certain period.
Minor
1.Board Status:
1. Previous-level of clock source is unavailable.
1. Replace clock cascading cable.
1PPS+TOD standby source cannot receive messages via serial

port; 1PPS+TOD standby source has unavailable PPS (pulse per
second) status; 1PPS+TOD standby source cannot obtain time of day
information for a certain period.
Minor
1. Board Status:
1. Previous-level of clock source is unavailable.
1. Replace clock cascading cable.
ncE+1588)
This alarm is reported when SyncE clock is unavailable in SyncE+1588
mode.
Warning
If SSM messages are constantly lost for long time, phases may not
be synchronized.
Phase synchronization source is lost.
Check SyncE clock reference source.
5.38 198092430 Optical module rate does not match
This alarm is reported when the speed of an optical module is
inconsistent with its configured value.
Major
1. Board Status:
The actual optical module cannot support the speed configured by
Set the speed of optical module to be lower or equal to real optical
This alarm is reported when the length of optical fiber is beyond the
transmission distance of an optical module.
Minor
1. Board Status:
Work normally
The services borne on the corresponding link may be interrupted.
Optical fiber length is beyond optical module transmission distance
Replace the optical module so that it can support longer transmission
Failed to setup cell,unable to offer service.

Major
Unable to setup cell,cause service could not be processed,severely
affect service quality.
1.The parameters of cell is configured incorrectly.
2.The BaseBand processing unit or RRU or other module timed out for
cell setup.
1.Check if the parameters of cell is configured correctly.(Reference
Fail to reconfigure parameters of the cell.

Major
Failed to reconfigure cell which leads to services interruption at this
moment and unable to offer services any more.
1.The parameters of cell is configured incorrectly.
2.The BaseBand processing unit or RRU or other module timed out for
cell reconfiguration.
1.Check if the parameters of cell is configured correctly(Reference
The key parameters on board configured failure.

Major
Will affect the service process and service quality.
1.The key parameters is configured incorrectly.
1.Check the error description of the alarm, and be sure that the current
value is right(Reference BBU's configuration manual).

198092410 Satellite searching alarm of GNSS receiver
198092417 The built-in-type GNSS receiver has a satellite searching alarm
198092420 The external-panel-type GNSS receiver has a satellite searching alarm...6-2
198092424 The external-backplane-type GNSS receiver has a satellite searching
6.1 198092410 Satellite searching alarm of GNSS

This alarm is reported when GNSS receiver fails to search satellites or
the number of searched satellites doesn't reach minimum requirement.
Minor
1. Board Status:
GNSS receiver fails to search satellites or the number of searched

satellites doesn't reach minimum requirement.
Check antenna feeder fault
er has a
This alarm is reported when the built-in-type GNSS antenna fails to
search satellites or the number of searched satellites doesn't reach
minimum requirement.
Minor
1.Board Status:
GNSS receiver fails to search satellites or the number of searched

Check the faulty of GNSS antenna feeder.
198092420 The external-panel-type GNSS receiver

This alarm is reported when the external-panel-type GNSS receiver
fails to search satellites or the number of searched satellites doesn't
reach minimum requirement.
Minor
1.Board Status:
The GNSS receiver fails to search satellites or the number of searched

Check the fault of GNSS antenna feeder.

198092424 The external-backplane-type GNSS
This alarm is reported when the external-backplane-type GNSS
receiver fails to search satellites or the number of searched satellites
doesn't reach minimum requirement.
Minor
1.Board Status:
The GNSS receiver fails to search satellites or the number of searched

Check the fault of GNSS antenna feeder.
The physical cell ID of neighborhood cell is identical.

Major
Affect the UE access and handover performance which is under the
cell's coverage.
A pair of neighborhood cells has the identical physical cell ID parameter
while detecting the neighborhood cells' relation configuration.
1.Lauch eNB's SON PCI function in this area.
2.Modify PCI of the conflict cell until PCI conflict alarm disappears.
6.6 198094827 PCI confusion alarm

Two neighborhood cells of a certain cell have the identical physical
cell ID configuration.
Major
6-3
Affect the UE access and handover performance which is under the
Two neighborhood cells of a certain cell have identical physical cell ID

parameter while detecting the neighborhood cells' relation configuration.
1.Lauch eNB's SON PCI function in this area.
2.Modify PCI of the confusion cell until PCI confusion alarm disappears.
6.7 198092350 RRU pre-download is failed.

Version download is successful or changing boot initial file is failed
when pre-download RRU.
Minor
None
1. RRU is not working normally.
2. There is no sufficient space in the RRU disk.
3. RRU file system has fault.
1. when RRU is working normally, download the software package
again.
2. Clear rubbish file in RRU.
6.8 198092368 Ethernet remote fault alarm(RDI)

Exchange fault information between MEP.
Minor
1.Error management of single side: receiving MEP detects a RDI fault
Please check ethernet transmission link.
ETH-AIS stops alarm when service level detects fault.

6-4
Major
ETH-AIS stops alarm when service level detects fault.
Please check ethernet transmission link.
6.10 198092380 EFM Link is broken.
EFM of ethernet detects that link has fault.
Major
It will cause that ethernet link is broken.
The handshake between base station and the first switchboard is failed.
Please check whether the transport link between base station and the
first switchboard is normal.
Slave board powered-on notification

Active-to-standby switchover completed
Standby-to-active switchover completed
Succeed in repairing the specification package
Alarm Storm
Module reset
Module status error
Switchover completed
Switchover failed
Board switchover failed
Main board product process power-on
Slave board product process power-on
Local benchmark clock unlocked
Uplink optical/electrical link has high BER
PPP Negotiatory IP Conflict
IP Conflict
Mac Conflict
ACOM address conflict
ATMA device address conflict
RET device address conflict
RRU pre-download is successful
EFM Link has error data
Product process fails to power on
DPD Running Status Abnormal
Uplink IQ link error
RRU alarm reset
Unavailable alarm of time slot turn-off function
Board power-on done notification
Board power-on failed
Bit error has been detected during E1 physical layer in the past 24
198092035 E1 link bit error has been detected in the past 24 hours
This is a notification message when the slave board is successfully

powered on.
None
The standby board is powered on.
None
7.2198092055 Active-to-standby switchover completed
Active-to-standby switchover is complete.
None
Active-to-standby switchover notification.
None
7.3 198092056 Standby-to-active switchover completed
Standby-to-active switchover is complete
None
Standby-to-active switchover notification.
None
7.4 198092058 Succeed in repairing the specification
During board powered-on process, the system detects that the
specification package flag is abnormal. In this case, the system starts
to repair the specification package. This notification is reported when
the repairing operation is successful.
1. Board Status:
Specification package is repaired successfully.
Enter the Software Version Management interface to download the
When the number of alarms reported during a certain period of time

exceeds the threshold value, the notification is reported.
The alarm cannot be reported during the alarm storm.
The number of alarms reported during a certain period of time exceeds
Find an alarm code from additional alarm information. Then handle the
alarm according to the alarm code.
Module reset
The module has been reset.
The module has been reset.
None
The partner machine is in error status. This status is read from signal
line by bottom-layer BSP.
The module's status is abnormal.
The module's status is abnormal.
2. This abnormity seldom happens. Once it happens, please inform
RD center for fault location.
The switchover is completed.

Switching succeeded.
7-3
Switching succeeded.
None
This alarm is reported when active-to-standby or standby-to-active

switchover operation fails.
Switching failed.
Switching failed.
None
The switchover condition is not satisfied.

CC boards are configured in active/standby mode, but switchover
doesn't work. This reduces system reliability.
Switchover is not allowed.
None
7.11 198092228 Main board product process power-on
Main board product process power-on notification.
None
The process is powered on.
None
7.12 198092229 Slave board product process power-on
Slave board product process power-on notification.
None
The process is powered on.
None
7-4
198092271 Local benchmark clock unlocked

This alarm is reported when Local benchmark clock is unlocked on
the local benchmark clock.
Service Impact:
If the accuracy of base station clock doesn't meet 3GPP requirement,
the inter-Base station handover successful ratio must be affected.
1. Reference source is not configured.
2. Reference source is lost or degraded.
1. Use OMC to check whether clock reference source has been
has high
This notification is reported when FS detects that LCV bit error rate
at optical port exceeds threshold.
1. Board Status:
The measured LCV bit error rate from the link between BBU and RRU
1. Check whether the optical fiber between BBU and RRU is well
Alarm happens when PPP Negotiatory IP Conflicts with IP that is

configurated.
PPP link is interrupted or PPP's negotiation is fail.
The IP of PPP which gets from negotiation with the other side is
different from itself IP before.
Please check the PPP address configuration and modify.
Alarm happens when original IP in ARP message is the same as

interface IP.
Base station can't communicate.
The IP of the station is conflicted.
Please check the IP address configuration in the net.
Alarm happens when original Mac in ARP message is the same as

interface Mac.
Base station can't communicate.
The MAC of the station is conflicted.
None
A new device is inserted. If its address conflicts with existing AISG

Service Impact:
1. This alarm notification may be given if quick deplug-and-plug the
2. Otherwise, new device is inserted, which has conflict address with
On Base station configuration management interface management

interface, scan AISG in AISG Devices Centralized Management dialog
198092329 ATMA device address conflict

Service Impact:
On Base station configuration management interface management

interface, scan AISG in AISG Devices Centralized Management dialog

198092338 RET device address conflict
Service Impact:
On base station configuration management interface, scan AISG in

AISG Devices Centralized Management dialog box then add a new
7.21 198092349 RRU pre-download is successful

Version download is successful or changing boot initial file is successful
None
Version download is successful or changing boot initial file is successful
None
EFM of ethernet detects that link has error data.

It has effect on ethernet stability.
Ethernet EFM protocol detects error data in the transport link.
7-8
Please check whether the transport link between base station and the
7.23 198092392 Product process fails to power on
Product process fails to power on.
It will affect power-on of product process.
1. Product process fails to power on.
2. Product process power-on is overtime.
None
198094823 DPD Running Status Abnormal
DPD module running status is abnormal in RRU.
None
The downlink power output drops and the quality of RF output
declines.
1.Input Baseband Signal Too Large.
1.Reset the faulty RRU.

2.Replace the faulty RRU.
IQ link from IQ switch card to base band card error.
The quality of service may be affected.

IQ link exception.
Unplug and plug boards, including IQ exchange board. If problem
exists, replace board.
RRU alarm reset.

The service accessed by this RRU may be interrupted.
1. DSP software system error.
2. RRU internal communication has fault.
3. Other reason.
Replace RRU if it happens frequently.
7.27 198098433 Unavailable alarm of time slot turn-off
This alarm is reported when time slot turn-off function cannot be used
because of some constraints on PA hardware or status.
1. Board Status:
Work normally
The time slot turn-off function cannot be used.
1. PA hardware has some constraints.
2. PA is abnormally closed.
1. Check whether the current hardware supports the time slot closing
Board power-on done notification.

None
The board is powered on.
7-10
None
7.29 198092033 Board power-on failed
The board fails to be powered on due to the board's basic process
power-on failure or timeout.
Board's power-on failure will cause the board to reset.
1. process power-on failed.
2. Process power-on timeout.
None
7.30 198092034 Bit error has been detected during E1
physical layer in the past 24 hours
Bit error has been detected during E1 physical layer in the past 24
hours.
Influence the communication quality.
Transmission link has a problem. Do statistics on trunk for 24 hours,
then find one of these abnormities: lost of receiving clock, lost of
receiving carrier, output open-circuit, output over-current and link code
violation. Thus, this notification is given.
1. Check DDF connections: whether jumpers are well connected, there
ected in
E1 link bit error has been detected in the past 24 hours.
Influence the communication quality.

Transmission link has a problem. Do statistics on trunk for 24 hours to
measure error second, severely error second, unavailable second.
When a measured value exceeds its threshold, this alarm is reported.
1. Check DDF connections: whether jumpers are well connected, there

Revision Reason
Version Upgrade
First Edition
3-9
3-10
3-10
3-11
3-11
3-12
3-12
3-13
3-13
3-14
3-14
3-14
3-15
3-16
3-16
3-17
3-17
3-18
3-18
3-19
3-19
3-20
3-20
3-21
3-21
3-21
3-22
3-22
3-22
3-23
3-23
3-24
3-24
3-24
3-25
3-26
3-26
3-27
3-27
3-28
3-28
3-29
3-30
3-30
3-31
3-31
3-32
3-32
3-33
3-33
3-34
3-34
3-35
3-35
3-36
3-36
3-38
3-39
3-39
3-40
3-40
3-40
3-41
3-41
3-42
3-42
3-43
3-43
3-44
3-44
3-44
3-45
3-46
3-46
3-47
3-47
3-48
3-48
3-49
3-50
3-50
3-51
3-52
3-52
3-53
3-53
3-54
3-54
3-56
3-57
3-57
3-58
3-58
3-59
3-59
3-60
3-60
3-61
3-61
3-62
3-62
3-63
3-63
3-64
3-64
3-65
3-65
3-66
3-66
3-67

3-116
3-116
3-116
3-117
3-117
3-117
3-118
3-118
3-119
3-119
3-119
3-120
3-120
3-120
3-121
3-121
3-122
3-122
3-122
3-123
3-123
3-123
3-124
3-124
3-125
3-125
3-125
3-126
3-126
3-126
3-127
3-127
3-128
3-128
3-128
3-129
3-129

4-8
4-8
4-9
4-9
4-10
4-10
4-11
4-12
4-12
4-13
4-13
4-13
4-14
4-14
4-15
4-15
4-16
4-16
4-16
4-17
4-17
4-17
4-18
5-1
5-2
5-2
5-2
5-3
5-3
5-4
5-4
5-5
5-5
5-6
5-6
5-7
5-7
5-8
5-8
5-9
5-9
5-10
5-11
5-11
5-12
5-12
5-12
5-13
5-13
5-13
5-14
5-15
5-15
5-16
5-16
5-16
5-17
5-17
5-18
5-18
5-19
5-19
5-20
5-20
5-21
5-21
6-1
6-1
6-2
6-2
6-3
6-3
6-3
6-4
6-4
6-4
6-5
7-1
7-2
7-2
7-2
7-2
7-3
7-3
7-3
7-3
7-4
7-4
7-4
7-4
7-5
7-5
7-6
7-6
7-6
7-6
7-7
7-8
7-8
7-8
7-9
7-9
7-9
7-10
7-10
7-10
7-11
7-11

s/notifications.
specific code value.
t phenomenon.
2-1
2-2
2-3
2-3
2-4
2-5
2-5
2-6
2-6
2-7
2-7
2-8
2-8
2-8
2-9
2-10
2-11
2-12
2-12
2-13
2-14
2-14
2-14
2-15
of OAM
munication
3-7
3-8
3-8
3-9
3-9
3-10
3-10
3-11
3-11
3-12
utes has exceeded
3-12
3-13
3-13
3-14
3-14
3-14
3-15
3-16
3-16
3-17
3-17
3-18
3-18
3-19
3-19
3-20
3-20
3-21
3-21
3-21
3-22
3-22
3-22
3-23
3-23

3-48
3-48
3-49
3-50
3-50
3-51
3-52
3-52
3-53
3-53
3-54
3-54
3-55
3-56
3-57
3-57
3-58
3-58
3-59
3-59
3-60
3-60
3-61
3-61
3-62
3-62
3-63
3-63
3-64
3-64
3-65
3-65
3-66
3-66
3-67
3-67
3-68
3-69
3-69
3-70
3-70
3-71
3-71
3-72
3-72

3-128
3-128
3-129
3-129
3-129
3-130
ector exceeded
3-130
3-130
3-131
3-131
3-131
3-132
3-132
3-132
3-133
3-133
3-133
3-134
consistent with
3-134
3-134
3-135
3-135
3-136
3-137
3-137
3-137
d from BBU to

Switch Off
Over-Iout
an Fault
Over-Vin Off
nder-Vin Off
use Broken
ommFail
aker Alarm
le Fault
onfiguration
unication
der-Temp
ownlink IQ
box alarm
ower input
exceeds rated
and power is
ric link is
signal
rameter error
t peer-end
ptical port has
e is failed.
e optical port
e RRU device
e power
ex alarm
n alarm
k broken in
up unavailable
of built-in
lt-in power
tact of built-in
ct alarm 2
ct alarm 3
ct alarm 4
ct alarm 5
ct alarm 6
ct alarm 7
ct alarm 8
ct alarm 10
ct alarm 11
ct alarm 12
ct alarm 13
ct alarm 14
ct alarm 15
ct alarm 16
ct alarm 18
ct alarm 19
ct alarm 20
ct alarm 21
ct alarm 22
ct alarm 23
ct alarm 24
ct alarm 26
ct alarm 27
ct alarm 28
ct alarm 29
ct alarm 30
ct alarm 31
ct alarm 32
ct alarm 34
ct alarm 35
ct alarm 36
ct alarm 37
ct alarm 38
ct alarm 39
ct alarm 40
ct alarm 42
ct alarm 43
ct alarm 44
ct alarm 45
ct alarm 46
ct alarm 47
ct alarm 48
ct alarm 50
bnormal
abnormal
delay of two
ing in RRU
BU sends to
adjust cable
hen power on

e is too hot.
Abnormal current alarm at NSBT port

1. An over-current alarm is reported when the current value at NSBT
ower level
nment is
Magnet Alarm
of board
5-2
5-2
5-2
5-3
5-3
5-4
5-4
5-5
5-5
5-6
5-6
5-7
5-7
5-8
5-8
5-9
5-9
5-10
5-11
5-11
5-12
5-12
5-12
5-13
5-13
5-13
5-14
5-15
5-15
5-16
5-16
5-16
5-17
5-17
5-18
5-18
5-19
5-19
5-20
5-20
5-21
5-21
nt Rule Library
k is interrupted
doesn't exist.
software
uration error
on error
on error
ration error
ion error
s not match
6-1
6-2
e searching alarm...6-2
atellite searching
6-3
6-3
6-3
6-4
6-4
6-4
6-5
of GNSS
S receiver
7-2
7-2
7-2
7-2
7-3
7-3
7-3
7-3
7-4
7-4
7-4
7-4
7-5
7-5
7-6
7-6
7-6
7-6
7-7
7-8
7-8
7-8
7-9
7-9
7-9
7-10
7-10
7-10
7-11
7-11
7-11
ver completed
ver completed
specification
ess power-on
cess power-on
ccessful
power on
e slot turn-off
ed during E1

eNodeB Alarm Handling Reference

Cargado por

Información del documento

Título original

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

eNodeB Alarm Handling Reference

Cargado por

Copyright:

Formatos disponibles

NetNumen U31(TDD LTE)

Unified Management System

3.106 198092277 Clock module fault

3.116 198092287 The channel downlink frame is unlocked

3.153 198092345 RET position lost

3.187 198092434 Clock line abnormal connection in stack mode

3.261 198096550 Alarm of fiber configuration

6.9 198092370 AIS alarm

7.5 198092059 Alarm Storm

About This Manual

This manual is intended for:

What Is in This Manual

This manual contains the following chapters:

Chapter 3, Equipment Alarm

Chapter 4, Environment Alarm

Chapter 6, QoS Alarm

probable cause, system impact, and handling suggestion

The information, in the form of alarm or notification, is stored in database or displayed

Fault is displayed in the form of alarm or notification.

Notification refers to the non-repeated/instantaneous fault or event that occurs during

Alarm/Notification Information Structure

l Equipment alarm: related with device hardware.

NetNumen U31(TDD LTE) eNodeB Alarm Handling Reference

à Critical alarm causes system breakdown and service interruption. It requires

à Major alarm significantly affects system operation or weakens network service

à Minor alarm affects system operation and network service capability in a

à Alarm severity can be modified in NetNumen U31 if necessary.

Probable alarm/notification causes are enumerated to help users troubleshoot, find

Troubleshooting measures and suggestions are provided. Pay attention to the

NetNumen U31(TDD LTE) eNodeB Alarm Handling Reference

This page intentionally left blank.

198092211 PLL unlocked alarm

198092231 PPP Link is broken

198092399 BFD connection broken

198092428 SCTP path is interrupted

2.1 198092211 PLL unlocked alarm

NetNumen U31(TDD LTE) eNodeB Alarm Handling Reference

2. If SYNCE mode is supportable, this alarm requires replacing the

1) Check if there is FE port or PPP related alarm

2) Deal with FE port or PPP related alarm

Remove alarm according to disposal suggestions of FE port or PPP

Y=>alarm is recovered, close alarm dispose.

N=>alarm is not recovered, go to "2.Check if configuration of SCTP

2. Check if configuration of SCTP coupling parameter is correct

2) Check if remote address and port number of SCTP coupling is same

N=>Inconsistent, go to "3.Reconfiguration SCTP coupling.".

Wait for a while, Determine whether the alarm is recovered.

1) Delete the error coupling in configuration window of SCTP coupling.

Y=>alarm is recovered, close alarm dispose

Y=>exist, go to "2. Deal with error alarm of E1/STM1 link".

2. Deal with error alarm of E1/STM1 link.

Remove the alarm according to disposal suggestions of E1/STM1 error

Y=>alarm is recovered, close alarm disposal.

Reset board, wait 2 minutes, Determine whether the alarm is recovered.

N=>alarm is not recovered, go to "4. Replace board".

Replace error board, wait 2 minutes, determine whether the alarm is

Y=>alarm is recovered, close alarm disposal.

2.4 198092232 HDLC Link is broken.

NetNumen U31(TDD LTE) eNodeB Alarm Handling Reference

Y=>exist, go to "2. Deal with error alarm of E1/STM1 link"

2. Deal with error alarm of E1/STM1 link

Remove the alarm according to disposal suggestions of E1/STM1 error

Y=>alarm is recovered, close alarm disposal