eNodeB Alarm Handling Reference PDF

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. Revision Date Revision Reason
R1.1 2012–4–15 Version Upgrade
R1.0 2011–12–20 First Edition
Serial Number: SJ-20120322151347-005
Publishing Date: 2012-04-15(R1.1)
SJ-20120322151347-005|2012-04-15(R1.1) ZTE Proprietary and Confidential

Contents
About This Manual ......................................................................................... I
Chapter 1 Overview .................................................................................... 1-1
Chapter 2 Communication Alarm.............................................................. 2-1
2.1 198092211 PLL unlocked alarm .......................................................................... 2-1
2.2 198092230 SCTP association is interrupted. ........................................................ 2-2
2.3 198092231 PPP Link is broken. .......................................................................... 2-3
2.4 198092232 HDLC Link is broken. ........................................................................ 2-3
2.5 198092233 SSCOP Link is broken. ..................................................................... 2-4
2.6 198092240 1588 clock link fault .......................................................................... 2-5
2.7 198092313 PPP Link Loop.................................................................................. 2-5
2.8 198092351 Local LMT's Force Connect .............................................................. 2-6
2.9 198092361 IMA group has fault........................................................................... 2-6
2.10 198092362 IMA/TC link has fault. ...................................................................... 2-7
2.11 198092367 802.1x authentication failed ............................................................. 2-7
2.12 198092369 LCK alarm ...................................................................................... 2-8
2.13 198092382 Configuration parameter of OAM Channel is wrong. .......................... 2-8
2.14 198092399 BFD connection broken ................................................................... 2-8
2.15 198092402 TCP connection is broken................................................................ 2-9
2.16 198092411 BITS clock fault............................................................................. 2-10
2.17 198092427 The number of SCTP streams is inconsistent...................................2-11
2.18 198092428 SCTP path is interrupted. .............................................................. 2-12
2.19 198092431 The strength of received optical signal is abnormal ......................... 2-12
2.20 198092445 RRU inner GNSS (clock reference source) link alarm ...................... 2-13
2.21 198092446 RRU inner GNSS (clock reference source) link unavailable ............. 2-14
2.22 198094825 Optical link which bearing S1/X2 signal breakdown error ................. 2-14
2.23 198096564 RRU and outer LNA communication link broke ............................... 2-14
2.24 198092210 PLL reference clock lost alarm....................................................... 2-15
Chapter 3 Equipment Alarm ...................................................................... 3-1

3.1 198100270 Optical signals transmitted from BBU to RRU carry wrong clock
information ....................................................................................................... 3-7
3.2 198100271 Unlocked local oscillator alarm of RRU............................................... 3-8
3.3 198100272 RRU inside clock unlocked ................................................................ 3-8
3.4 198100273 Downlink channel fault alarm ............................................................. 3-9

3.5 198100274 Downlink output power abnormal ....................................................... 3-9
3.6 198100274 Downlink output under/over-power alarm ......................................... 3-10
3.7 198092008 FPGA register read/write error ......................................................... 3-10
3.8 198092009 Ethernet access network interface abnormal .....................................3-11
3.9 198092011 E1/T1 input port unavailable .............................................................3-11
3.10 198092012 E1/T1 output port unavailable ........................................................ 3-12
3.11 198092013 ES or SES detected on the E1 link in the past 15 minutes has
exceeded the threshold................................................................................... 3-12
3.12 198092032 Failed to operate Database ........................................................... 3-13
3.13 198092049 Lightning protection device alarm................................................... 3-13
3.14 198092051 PSU alarm.................................................................................... 3-14
3.15 198092052 PSU fan alarm .............................................................................. 3-14
3.16 198092057 The board is powered off ............................................................... 3-14
3.17 198092068 Base station has a main power cut-off alarm................................... 3-15
3.18 198092071 Abnormal temperature sensor........................................................ 3-16
3.19 198092072 Board not-in-position ..................................................................... 3-16
3.20 198092073 Embedded power AC-in Switch Off ................................................ 3-17
3.21 198092074 Embedded power AC Power Off .................................................... 3-17
3.22 198092075 Embedded power SPD-C Broken................................................... 3-18
3.23 198092076 Embedded power SPD-D Broken................................................... 3-18
3.24 198092077 Embedded power AC Under-Volt ................................................... 3-19
3.25 198092078 Embedded power AC Over-Volt ..................................................... 3-19
3.26 198092079 Embedded power AC Current Over................................................ 3-20
3.27 198092080 Embedded power SMR Over-Vout ................................................. 3-20
3.28 198092081 Embedded power SMR Over-Iout .................................................. 3-21
3.29 198092082 Embedded power SMR Fan Fault .................................................. 3-21
3.30 198092083 Embedded power SMR PFC Fault ................................................. 3-21
3.31 198092084 Embedded power SMR Over-Vin Off .............................................. 3-22
3.32 198092085 Embedded power SMR Under-Vin Off ............................................ 3-22
3.33 198092086 Embedded power SMR H.T. Off ..................................................... 3-22
3.34 198092087 Embedded power SMR Env.H.T.Off................................................ 3-23
3.35 198092088 Embedded power SMR Env.H.T .................................................... 3-23
3.36 198092089 Embedded power SMR L.Vin......................................................... 3-24
3.37 198092090 Embedded power SMR Fuse Broken ............................................. 3-24
3.38 198092091 Embedded power SMR CommFail ................................................. 3-24
3.39 198092092 Embedded power DC Under-Volt ................................................... 3-25
3.40 198092093 Embedded power DC Over-Volt ..................................................... 3-26
3.41 198092094 Embedded power DC Loop Broken ................................................ 3-26
II

3.42 198092095 Embedded power Bat Loop Broken................................................ 3-27
3.43 198092096 Embedded power Bat Under-Volt ................................................... 3-27
3.44 198092097 Embedded power Bat Over-Temp .................................................. 3-28
3.45 198092098 Embedded power TmpL Shut-Down............................................... 3-28
3.46 198092099 Embedded power 1st Shut-down ................................................... 3-29
3.47 198092100 Embedded power 2nd Shut-down .................................................. 3-30
3.48 198092101 Embedded power DC SPD Broken................................................. 3-30
3.49 198092102 Embedded power DCBreaker Alarm............................................... 3-31
3.50 198092103 Embedded power Bat Test Failure ................................................. 3-31
3.51 198092104 Embedded power Bat Discharge.................................................... 3-32
3.52 198092116 Embedded power AC Auxiliary Output Switch Off............................ 3-32
3.53 198092117 Embedded power Rectifier Module Fault ........................................ 3-33
3.54 198092203 Board not-configured alarm ........................................................... 3-33
3.55 198092206 Battery alarm ................................................................................ 3-34
3.56 198092207 AC power-cut alarm ...................................................................... 3-34
3.57 198092208 Rectifier module alarm .................................................................. 3-35
3.58 198092209 Thermoelectric cooler alarm ......................................................... 3-35
3.59 198092212 EPLD's register has a R/W failure alarm. ........................................ 3-36
3.60 198092214 Hardware of Clock Module Fault .................................................... 3-36
3.61 198092215 Lost of synchronization.................................................................. 3-38
3.62 198092216 Current Active Reference Source 1PPS Lost .................................. 3-39
3.63 198092217 Air Interface Clock Unavailable ...................................................... 3-39
3.64 198092219 Baseband Subunit Fault ................................................................ 3-40
3.65 198092234 Embedded power type configuration error ...................................... 3-40
3.66 198092235 Embedded power communication interruption................................. 3-40
3.67 198092236 Embedded power SMR Output Fault .............................................. 3-41
3.68 198092237 Embedded power Bat Under-Temp ................................................ 3-41
3.69 198092238 Embedded power Bat Invalid-Temp................................................ 3-42
3.70 198092239 Embedded power Battery Fault...................................................... 3-42
3.71 198092241 1588 clock source unavailable ....................................................... 3-43
3.72 198092242 Ir link LCV alarm ........................................................................... 3-43
3.73 198092243 Abnormal DPD running status........................................................ 3-44
3.74 198092244 LNA alarm .................................................................................... 3-44
3.75 198092245 Disable PA ................................................................................... 3-44
3.76 198092246 TMA channel input is over current.................................................. 3-45
3.77 198092247 Over-high temperature of PA ........................................................ 3-46
3.78 198092248 Optical module out-of-position alarm .............................................. 3-46
III

3.79 198092249 RF board PLL alarm...................................................................... 3-47
3.80 198092250 Calibration file on TRx board is abnormal ....................................... 3-47
3.81 198092251 a block check error of downlink IQ channel alarm............................ 3-48
3.82 198092252 Downlink digital IF pre-distortion alarm ........................................... 3-48
3.83 198092253 Application software monitoring alarm ............................................ 3-49
3.84 198092254 Remote output power abnormal voltage alarm ................................ 3-50
3.85 198092255 Remote input power over-voltage alarm ......................................... 3-50
3.86 198092256 Remote input power under-voltage alarm ....................................... 3-51
3.87 198092257 Remote antenna over VSWR alarm ............................................... 3-52
3.88 198092258 Lost of frame rate and frame number ............................................. 3-52
3.89 198092259 Battery low-voltage alarm .............................................................. 3-53
3.90 198092260 Faulty external device connected at a dry contact ........................... 3-53
3.91 198092261 Outdoor lightning protection box alarm ........................................... 3-54
3.92 198092262 Breaker alarm in indoor lightning protection box.............................. 3-54
3.93 198092263 Lightning protection device alarm in indoor lightning protection box
..................................................................................................................... 3-55
3.94 198092264 Over-voltage alarm of main power input ......................................... 3-56
3.95 198092265 Main power input power-cut alarm ................................................. 3-57
3.96 198092266 Under-voltage alarm of main power input ....................................... 3-57
3.97 198092267 General fault of main power .......................................................... 3-58
3.98 198092268 PWR monitoring unit alarm ........................................................... 3-58
3.99 198092269 Over-high temperature of RU board ............................................... 3-59
3.100 198092270 Slight-high temperature of RU board ............................................ 3-59
3.101 198092272 The value of RSSI over reverse link is low. .................................. 3-60
3.102 198092273 The value of RSSI over reverse link is high. ................................. 3-60
3.103 198092274 Slight-high temperature of PA ...................................................... 3-61
3.104 198092275 PA communication fault ............................................................... 3-61
3.105 198092276 Receiving RF channel fault .......................................................... 3-62
3.106 198092277 Clock module fault ...................................................................... 3-62
3.107 198092278 Abnormal power.......................................................................... 3-63
3.108 198092279 Downlink analog power exceeds rated power slightly .................... 3-63
3.109 198092280 Downlink digital power exceeds rated power slightly ..................... 3-64
3.110 198092281 Downlink carrier baseband power is low ....................................... 3-64
3.111 198092282 Downlink carrier analog power is low ............................................ 3-65
3.112 198092283 Remote antenna VSWR alarm ..................................................... 3-65
3.113 198092284 Input reference clock is abnormal ................................................. 3-66
3.114 198092285 Internal clock is abnormal ............................................................ 3-66
3.115 198092286 The uplink frame at optical/electric port is unlocked ....................... 3-67
IV

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

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

3.187 198092434 Clock line abnormal connection in stack mode .............................. 3-98
3.188 198092435 Inter-frame Ethernet link broken in stack mode ............................. 3-98
3.189 198092436 Loss of clock synchronization at slave frame................................. 3-99
3.190 198092437 RU radio frequency group unavailable .......................................... 3-99
3.191 198092438 Device in low temperature .........................................................3-100
3.192 198092439 Uplink transport port of a base station operates in a different
mode from configured one. ...........................................................................3-100
3.193 198092447 Unbalanced AC phase voltage of built-in power ...........................3-101
3.194 198092448 High AC phase current of built-in power.......................................3-101
3.195 198092449 Missing AC phase voltage of built-in power .................................3-102
3.196 198092450 Battery low-voltage cut-off of built-in power .................................3-102
3.197 198092451 Broken LLVD1 branch E of built-in power.....................................3-103
3.198 198092452 Broken LLVD1 branch of built-in power .......................................3-104
3.199 198092453 Broken LLVD2 branch E of built-in power.....................................3-105
3.200 198092454 Broken battery cut-off branch E of built-in power ..........................3-106
3.201 198092455 Broken battery cut-off branch of built-in power .............................3-106
3.202 198092456 Abnormal battery current of built-in power ...................................3-107
3.203 198092457 Abnormal CAN bus of built-in power ...........................................3-108
3.204 198092458 Abnormal battery of built-in power ..............................................3-108
3.205 198092459 Abnormal input dry contact of built-in power ................................3-108
3.206 198092460 High-temperature cut-off of built-in power ....................................3-109
3.207 198092461 BBU inter-subrack frame synchronization failure alarm .................3-109
3.208 198092550 User-defined dry contact alarm 1 ................................................ 3-110
3.211 198092553 User-defined dry contact alarm 4................................................. 3-111
3.217 198092559 User-defined dry contact alarm 10............................................... 3-113
3.218 198092560 User-defined dry contact alarm 11 ............................................... 3-113
VII

3.235 198092577 User-defined dry contact alarm 28...............................................3-120
3.258 198094800 SRIO Communication Abnormal .................................................3-128
3.259 198094828 The board is unavailable ............................................................3-129
3.260 198094829 eBBU synchronization abnormal .................................................3-129
VIII

3.261 198096550 Alarm of fiber configuration .........................................................3-129
3.262 198096551 RRU unconfigured ....................................................................3-130
3.263 198096552 Difference of fiber time delay of two RRUs in same sector
exceeded system limit....................................................................................3-130
3.264 198096553 RRU Type is not consistent with configuration type.......................3-130
3.265 198096554 Failure of optical decoding in BBU...............................................3-131
3.266 198096555 Failure of optical decoding in RRU ..............................................3-131
3.267 198096556 IQ link input loses lock................................................................3-131
3.268 198096558 Downlink baseband power abnormal ...........................................3-132
3.269 198096558 Guide frequency that BBU sends to RRU is too high or too low ......3-132
3.270 198096559 RRU adjust channel or adjust cable fault. ....................................3-132
3.271 198096560 Master and slave monitor link alarm ............................................3-133
3.272 198096561 Coherence alarm of antenna channel swing and phase ................3-133
3.273 198096562 RRU self check failed when power on .........................................3-133
3.274 198096563 RRU device alarm......................................................................3-134
3.275 198096565 Configuration parameter of RRU external device not consistent
with real parameter ........................................................................................3-134
3.276 198096568 RRU used power module is too hot. ............................................3-134
3.277 198096569 RRU offline parameter check failure ...........................................3-135
3.278 198098431 Abnormal current alarm at NSBT port .........................................3-135
3.279 198098432 AISG/NSBT port turn-off alarm due to over current.......................3-136
3.280 198098434 Abnormal transmission power at antenna port .............................3-137
3.281 198098435 Closed-loop power control adjustment exceeding normal
range ............................................................................................................3-137
3.282 198098436 Failure in configuring power level ................................................3-137
Chapter 4 Environment Alarm................................................................... 4-1

4.1 198092429 Board powered-down alarm because of high temperature ................... 4-2
4.2 198092462 Differential pressure alarm ................................................................ 4-2
4.3 198092037 MP voltage abnormal ........................................................................ 4-3
4.4 198092038 PP voltage abnormal......................................................................... 4-3
4.5 198092039 Over current of MP ........................................................................... 4-3
4.6 198092040 Over current of PP ............................................................................ 4-4
4.7 198092041 Fan failure........................................................................................ 4-4
4.8 198092042 Abnormal temperature at air intake .................................................... 4-5
4.9 198092043 Abnormal temperature at air outlet ..................................................... 4-6
4.10 198092044 Door control alarm ......................................................................... 4-6
4.11 198092045 Flooding alarm ................................................................................ 4-7
4.12 198092046 Smog alarm.................................................................................... 4-7
IX

4.13 198092047 Infrared alarm ................................................................................ 4-8
4.14 198092048 Air conditioner fault ......................................................................... 4-8
4.15 198092053 Voltage of DC input is abnormal. ...................................................... 4-9
4.16 198092069 FCE-fan failure ............................................................................... 4-9
4.17 198092105 Embedded power Environment is under-temperature. ..................... 4-10
4.18 198092106 Embedded power Environment is over-temperature. ....................... 4-10
4.19 198092107 Embedded power Environment temperature is invalid. .....................4-11
4.20 198092108 Embedded power Environment is under-Humidity. .......................... 4-12
4.21 198092109 Embedded power Environment is over-Humidity. ............................ 4-12
4.22 198092110 Embedded power Environment humidity is invalid. .......................... 4-13
4.23 198092111 Embedded power Smoke detected ................................................. 4-13
4.24 198092112 Embedded power Flood detected................................................... 4-13
4.25 198092113 Embedded power Door Magnet Alarm ............................................ 4-14
4.26 198092114 Embedded power Gate Embedded power Safety Alarm .................. 4-14
4.27 198092115 Glass Broken Alarm ...................................................................... 4-15
4.28 198092118 Embedded power Env-unit communication interruption.................... 4-15
4.29 198092119 Embedded power Heat Exchanger Fault......................................... 4-16
4.30 198092213 Board temperature abnormal alarm................................................ 4-16
4.31 198092307 Slight-high temperature of board .................................................... 4-16
4.32 198092308 Over-high temperature of board ..................................................... 4-17
4.33 198092371 CCM Remote MEP Error ............................................................... 4-17
4.34 198092372 CCM Message Error ..................................................................... 4-17
4.35 198092373 CCM Xconnect Error ..................................................................... 4-18
Chapter 5 Processing Alarm ..................................................................... 5-1

5.1 198094815 Performance Measurement Rule Library Unavailable .......................... 5-2
5.2 198096567 BOOT software upgrade failure ......................................................... 5-2
5.3 198092010 Board communication link is interrupted ............................................. 5-2
5.4 198092014 SNTP time adjustment failure alarm ................................................... 5-3
5.5 198092016 Clock reference source configuration error ......................................... 5-3
5.6 198092017 Failure in loading software................................................................. 5-4
5.7 198092019 Failure in synchronizing the version of master board with slave
board. .............................................................................................................. 5-4
5.8 198092022 Running software version doesn't exist. ............................................ 5-5
5.9 198092024 DOM is lack of space ........................................................................ 5-5
5.10 198092025 Failure in synchronizing software version of master control board ...... 5-6
5.11 198092027 Failure in repairing specification package.......................................... 5-6
5.12 198092029 Wrong board insertion ..................................................................... 5-7

5.13 198092030 Abnormal software in specification package...................................... 5-7
5.14 198092060 LMT login alarm ............................................................................. 5-8
5.15 198092066 Failure in uncompressing LMT software ........................................... 5-8
5.16 198092070 Board software fault ........................................................................ 5-9
5.17 198092309 Line clock has the fault.................................................................... 5-9
5.18 198092310 SyncE clock has the fault. ............................................................. 5-10
5.19 198092347 The fan control policy is not existed ................................................5-11
5.20 198092348 Board initialization..........................................................................5-11
5.21 198092360 Product process is abnormal.......................................................... 5-12
5.22 198092366 Configuration Fail.......................................................................... 5-12
5.23 198092390 CPU over loading highly alarm....................................................... 5-12
5.24 198092391 CPU over loading.......................................................................... 5-13
5.25 198092395 Running software rollback ............................................................. 5-13
5.26 198092396 Board hot patch fault ..................................................................... 5-13
5.27 198092397 Failure in finding this board-related software ID .............................. 5-14
5.28 198092398 MMC running software version doesn't exist. .................................. 5-15
5.29 198092403 Carrier frequency configuration error .............................................. 5-15
5.30 198092404 Center frequency configuration error .............................................. 5-16
5.31 198092405 Work pattern configuration error..................................................... 5-16
5.32 198092406 IQ parameter configuration error .................................................... 5-16
5.33 198092407 Delay parameter configuration error ............................................... 5-17
5.34 198092408 Carrier power configuration error.................................................... 5-17
5.35 198092412 1PPS+TOD source fault ............................................................... 5-18
5.36 198092413 1PPS+TOD standby source fault ................................................... 5-18
5.37 198092414 SyncE clock unavailable (SyncE+1588).......................................... 5-19
5.38 198092430 Optical module rate does not match ............................................... 5-19
5.39 198092432 Optical modules have mismatched transmission distance................ 5-20
5.40 198094811 Cell Setup Failure ......................................................................... 5-20
5.41 198094812 Cell Reconfiguration Failure........................................................... 5-21
5.42 198094813 Parament Configuration Error ........................................................ 5-21
Chapter 6 QoS Alarm ................................................................................. 6-1

6.1 198092410 Satellite searching alarm of GNSS receiver ....................................... 6-1
6.2 198092417 The built-in-type GNSS receiver has a satellite searching alarm........... 6-2
6.3 198092420 The external-panel-type GNSS receiver has a satellite searching
alarm. .............................................................................................................. 6-2
6.4 198092424 The external-backplane-type GNSS receiver has a satellite
searching alarm................................................................................................ 6-3
6.5 198094826 PCI conflict alarm ............................................................................. 6-3
XI

6.6 198094827 PCI confusion alarm.......................................................................... 6-3
6.7 198092350 RRU pre-download is failed. .............................................................. 6-4
6.8 198092368 Ethernet remote fault alarm(RDI) ....................................................... 6-4
6.9 198092370 AIS alarm ......................................................................................... 6-4
6.10 198092380 EFM Link is broken. ........................................................................ 6-5
Chapter 7 Notification ................................................................................ 7-1

7.1 198092054 Slave board powered-on notification .................................................. 7-2
7.2 198092055 Active-to-standby switchover completed............................................. 7-2
7.3 198092056 Standby-to-active switchover completed............................................. 7-2
7.4 198092058 Succeed in repairing the specification package................................... 7-2
7.5 198092059 Alarm Storm ..................................................................................... 7-3
7.6 198092061 Module reset .................................................................................... 7-3
7.7 198092062 Module status error........................................................................... 7-3
7.8 198092063 Switchover completed ....................................................................... 7-3
7.9 198092064 Switchover failed .............................................................................. 7-4
7.10 198092065 Board switchover failed ................................................................... 7-4
7.11 198092228 Main board product process power-on.............................................. 7-4
7.12 198092229 Slave board product process power-on ............................................ 7-4
7.13 198092271 Local benchmark clock unlocked ..................................................... 7-5
7.14 198092297 Uplink optical/electrical link has high BER ........................................ 7-5
7.15 198092312 PPP Negotiatory IP Conflict ............................................................. 7-6
7.16 198092314 IP Conflict ...................................................................................... 7-6
7.17 198092315 Mac Conflict ................................................................................... 7-6
7.18 198092316 ACOM address conflict.................................................................... 7-6
7.19 198092329 ATMA device address conflict .......................................................... 7-7
7.20 198092338 RET device address conflict ............................................................ 7-8
7.21 198092349 RRU pre-download is successful...................................................... 7-8
7.22 198092381 EFM Link has error data .................................................................. 7-8
7.23 198092392 Product process fails to power on .................................................... 7-9
7.24 198094823 DPD Running Status Abnormal........................................................ 7-9
7.25 198096557 Uplink IQ link error .......................................................................... 7-9
7.26 198096566 RRU alarm reset ........................................................................... 7-10
7.27 198098433 Unavailable alarm of time slot turn-off function ................................ 7-10
7.28 198092031 Board power-on done notification................................................... 7-10
7.29 198092033 Board power-on failed ....................................................................7-11
7.30 198092034 Bit error has been detected during E1 physical layer in the past 24
hours ..............................................................................................................7-11
XII

7.31 198092035 E1 link bit error has been detected in the past 24 hours....................7-11
Glossary .......................................................................................................... I
XIII

XIV

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 Summary
Chapter 1, Overview Describes the concept of fault management
Chapter 2, Communication Alarm Describes communication alarms with respect to detailed

information, severity, probable cause, system impact, and
handling suggestion
Chapter 3, Equipment Alarm Describes equipment alarms with respect to detailed

handling suggestion
Chapter 4, Environment Alarm Describes environment alarms with respect to detailed

handling suggestion
Chapter 5, Processing Alarm Describes processing alarms with respect to detailed

handling suggestion
Chapter 6, QoS Alarm Describes QoS alarms with respect to detailed

handling suggestion
Chapter 7, Notification Describes notification with respect to detailed information,

probable cause, system impact, and handling suggestion

II

Chapter 1
Overview
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

NetNumen U31(TDD LTE) eNodeB Alarm Handling Reference
l 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.
l Alarm Name
l Detailed Information
Detailed Information reflects such content as fault cause and fault phenomenon.
l Alarm Severity
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

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

This page intentionally left blank.
1-4

Chapter 2
Communication Alarm
Table of Contents
198092211 PLL unlocked alarm .................................................................................2-1
198092230 SCTP association is interrupted. ..............................................................2-2
198092231 PPP Link is broken. .................................................................................2-3
198092232 HDLC Link is broken. ...............................................................................2-3
198092233 SSCOP Link is broken. ............................................................................2-4
198092240 1588 clock link fault .................................................................................2-5
198092313 PPP Link Loop. ........................................................................................2-5
198092351 Local LMT's Force Connect ....................................................................2-6
198092361 IMA group has fault..................................................................................2-6
198092362 IMA/TC link has fault................................................................................2-7
198092367 802.1x authentication failed .....................................................................2-7
198092369 LCK alarm ...............................................................................................2-8
198092382 Configuration parameter of OAM Channel is wrong. ................................2-8
198092399 BFD connection broken ...........................................................................2-8
198092402 TCP connection is broken. .......................................................................2-9
198092411 BITS clock fault ......................................................................................2-10
198092427 The number of SCTP streams is inconsistent.........................................2-11
198092428 SCTP path is interrupted........................................................................2-12
198092431 The strength of received optical signal is abnormal ................................2-12
198092445 RRU inner GNSS (clock reference source) link alarm ............................2-13
198092446 RRU inner GNSS (clock reference source) link unavailable ...................2-14
198094825 Optical link which bearing S1/X2 signal breakdown error .......................2-14
198096564 RRU and outer LNA communication link broke ......................................2-14
198092210 PLL reference clock lost alarm ...............................................................2-15
2.1 198092211 PLL unlocked alarm

Detailed Information PLL is unlocked.
Severity Major
System Impact Because PLL is unlocked, its output clock cannot meet system
requirement. As a result, PHY may not work normally in SNYCE mode.
Probable Cause PLL has no reference clock input or the reference clock is in poor
quality.
2-1

Handling Suggestion 1. If the board is only used as an ordinary data switching board without
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 198092230 SCTP association is interrupted.

Detailed Information 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.
Severity Critical
System Impact The transmission of Nbap signaling might fail and the services provided
by this association might be interrupted.
Probable Cause 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.
Handling Suggestion 1. Check if there is FE port or PPP related alarm

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

Chapter 2 Communication Alarm
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 198092231 PPP Link is broken.

Detailed Information Iub link has fault.
Severity Critical
System Impact Commands and services in the PPP are interrupted.
Probable Cause PPP Link is broken.
Handling Suggestion 1. If PPP exist in E1/STM1, check if the related E1/STM1 link has
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.

Detailed Information Alarm happens when HDLC run into bad link in the process of
negotiation.
Severity Critical
System Impact bottom-layer link of communication may be interrupted.
2-3

Probable Cause HDLC Link is broken.
Handling Suggestion 1. If HDLC exist in E1/STM1, check if the related E1/STM1 link has
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.

Detailed Information Alarm happens when Sscop link cannot send NBAP or ALCAP data in
time that causes cumulate data that need be sent exceeds cache limit.
Severity Critical
System Impact It may lead service command cannot be receive and send so that the
services are interrupted.
Probable Cause 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.
Handling Suggestion 1. Check if there are related alarms in real-time monitor of alarm
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

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

Detailed Information This alarm is reported in one of the following situations:
(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 Minor
System Impact none
Probable Cause 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.
Handling Suggestion 1. Check whether the physical connection to CC is normal.

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.

Detailed Information Alarm happens when PPP in LCP process receives Link Loop at three
times.
Severity Major
System Impact PPP link circle.
Probable Cause PPP Link Circle.
2-5

Handling Suggestion Check if there is a circle in physical links .

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

Detailed Information Local LMT's Force Connect.
Severity Warning
System Impact None
Probable Cause Local LMT Connect base station forcedly.
Handling Suggestion None
2.9 198092361 IMA group has fault.

Detailed Information Alarm happens when IMA group is configured successfully, but IMA
group cannot reach normal working status.
Severity Major
System Impact 1. Board Status:

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 1. Transport relay equipment has fault or configuration is not right.
2. E1/T1 cable connection has fault.
3. Base station or RNC configuration has fault.
Handling Suggestion 1. Check whether the local interfacing board has the E1/T1 alarms. If
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

Clock reference source is lost.
2.10 198092362 IMA/TC link has fault.

Detailed Information This alarm is reported when IMA group sub-link/TC link has a fault.
Severity Major

2. Service Impact:
Transport bandwidth and service capacity will be affected.
Probable Cause 1. Transport relay equipment has fault or configuration is error.

2. Base station or RNC configuration is error.
Handling Suggestion 1. Check the link configuration between base station and RNC: If
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

Detailed Information Dot1x authentication process is abnormal.
Severity Minor
System Impact The transmitting and receiving of IP packets is abnormal.
Probable Cause 1. The physical link is broken.

2. User Id and password are not matched in dot1x configuration.
Handling Suggestion 1. Please check whether the link of authenticator and supplicant is
normal.
2. Please check whether the user identity and user password is
matched in dot1x configuration.
2-7

2.12 198092369 LCK alarm

Detailed Information ETH-LCK informs MEP to lock data service stream.
Severity Major
System Impact Transmission of ethernet service is broke.
Probable Cause It happens enterprising lock of data stream.
Handling Suggestion Please check ethernet device in another side.
2.13 198092382 Configuration parameter of OAM

Channel is wrong.
Detailed Information OMCB channel is abnormal and need to configurate correct channel
data.
Severity Major

2. Service Impact:
Only the whole table configuration is permitted by the system. Other
services are unavailable.
Probable Cause OMCB channel is abnormal and need to configurate correct channel
data.
Handling Suggestion Reconfigurate system by the whole table data that contains correct
OMM parameter.
2.14 198092399 BFD connection broken

Detailed Information 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.
Severity Major
System Impact Signaling may not be received/transmitted properly. Accordingly, the

corresponding services borne over the connection are interrupted.
Probable Cause 1.Local end is in FE configuration.

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

Handling Suggestion 1. Check whether FE port exists.

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.

Detailed Information 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.
Severity Critical
System Impact The transmission of signaling might fail and the services provided by
this association might be interrupted.
2-9

Probable Cause 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.
4. The board is fault.
Handling Suggestion 1. Check if there is FE port or PPP related alarm

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

Detailed Information This alarm is reported when CC board fails to detect BITS clock signal
or the detected clock signals have poor quality.
Severity Minor
2-10


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 1. The configured clock reference source doesn't exist.

2. External reference source and cable are faulty.
3. The quality of clock reference source is poor.
4. The board is faulty.
Handling Suggestion 1. Check whether wrong reference source is configured.

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.
Detailed Information The configured number of outgoing/incoming SCTP streams is
inconsistent with that negotiated.
Severity Minor
System Impact Signaling may not be sent/received properly. As a result, partial

services borne over the SCTP link may be interrupted.
Probable Cause 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.
Handling Suggestion Check whether the number of outgoing/incoming SCTP streams is

correctly configured at both local end and peer end.
2-11

2.18 198092428 SCTP path is interrupted.

Detailed Information 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.
Severity Major
System Impact 1.Board Status:

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 1. Path parameters (FE and PPP) are wrongly configured at local end.
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 1. In Alarm Management Interface, view real time alarm information.
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
Detailed Information This alarm is reported when the received power by an optical module is
too high or too low.
Severity Minor
2-12


Work normally
The service performance in the corresponding cell is reduced.
Probable Cause 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.
Handling Suggestion 1. Check the connections of optical module and fiber. After that, check
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
Detailed Information 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.
Severity Minor

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 1. The link between RRU and BBU is abnormal.

2. RRU searches satellites abnormally.
Handling Suggestion 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.
2-13

2.21 198092446 RRU inner GNSS (clock reference

source) link unavailable
Detailed Information In the configuration of RRU inner GNSS clock reference source, this
alarm is reported when all configured RRU links are abnormal.
Severity Major

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 No available message can be obtained from all the configured RRU
links.
Handling Suggestion 1. Check whether the configured RRU communication links are normal.
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
Detailed Information Optical module loss signal.
Severity Critical
System Impact S1/X2 interface link breakdown, fail to communicate.
Probable Cause Optical fiber breakdown.
Handling Suggestion Check optical module and Optical links.
2.23 198096564 RRU and outer LNA communication

link broke
Detailed Information RRU and outer LNA communication link broke.
Severity Major
System Impact The RRU may not tune remote LNA normally.
Probable Cause RRU and external LNA communication link broke.
Handling Suggestion Check the connection of external LNA and RRU.
2-14

2.24 198092210 PLL reference clock lost alarm

Detailed Information 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.
Severity Major
System Impact Because the working clock on PHY's synchronous Ethernet is lost, the
corresponding Ethernet port cannot work properly.
Probable Cause PLL has no 25M clock output.
Handling Suggestion 1. If the board is only used as an ordinary data switching board without
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

2-16

Chapter 3
Equipment Alarm
Table of Contents
198100270 Optical signals transmitted from BBU to RRU carry wrong clock
information .................................................................................................................3-7
198100271 Unlocked local oscillator alarm of RRU ....................................................3-8
198100272 RRU inside clock unlocked ......................................................................3-8
198100273 Downlink channel fault alarm ...................................................................3-9
198100274 Downlink output power abnormal .............................................................3-9
198100274 Downlink output under/over-power alarm ...............................................3-10
198092008 FPGA register read/write error ...............................................................3-10
198092009 Ethernet access network interface abnormal..........................................3-11
198092011 E1/T1 input port unavailable...................................................................3-11
198092012 E1/T1 output port unavailable ................................................................3-12
198092013 ES or SES detected on the E1 link in the past 15 minutes has exceeded
the threshold ............................................................................................................3-12
198092032 Failed to operate Database....................................................................3-13
198092049 Lightning protection device alarm...........................................................3-13
198092051 PSU alarm .............................................................................................3-14
198092052 PSU fan alarm .......................................................................................3-14
198092057 The board is powered off .......................................................................3-14
198092068 Base station has a main power cut-off alarm..........................................3-15
198092071 Abnormal temperature sensor................................................................3-16
198092072 Board not-in-position..............................................................................3-16
198092073 Embedded power AC-in Switch Off ........................................................3-17
198092074 Embedded power AC Power Off ............................................................3-17
198092075 Embedded power SPD-C Broken...........................................................3-18
198092076 Embedded power SPD-D Broken...........................................................3-18
198092077 Embedded power AC Under-Volt ...........................................................3-19
198092078 Embedded power AC Over-Volt .............................................................3-19
198092079 Embedded power AC Current Over........................................................3-20
198092080 Embedded power SMR Over-Vout .........................................................3-20
198092081 Embedded power SMR Over-Iout ..........................................................3-21
198092082 Embedded power SMR Fan Fault ..........................................................3-21
198092083 Embedded power SMR PFC Fault .........................................................3-21
198092084 Embedded power SMR Over-Vin Off......................................................3-22
198092085 Embedded power SMR Under-Vin Off....................................................3-22
198092086 Embedded power SMR H.T. Off .............................................................3-22
198092087 Embedded power SMR Env.H.T.Off .......................................................3-23
198092088 Embedded power SMR Env.H.T ............................................................3-23
3-1

198092089 Embedded power SMR L.Vin .................................................................3-24

198092090 Embedded power SMR Fuse Broken .....................................................3-24
198092091 Embedded power SMR CommFail .........................................................3-24
198092092 Embedded power DC Under-Volt ...........................................................3-25
198092093 Embedded power DC Over-Volt .............................................................3-26
198092094 Embedded power DC Loop Broken........................................................3-26
198092095 Embedded power Bat Loop Broken........................................................3-27
198092096 Embedded power Bat Under-Volt...........................................................3-27
198092097 Embedded power Bat Over-Temp ..........................................................3-28
198092098 Embedded power TmpL Shut-Down ......................................................3-28
198092099 Embedded power 1st Shut-down ...........................................................3-29
198092100 Embedded power 2nd Shut-down ..........................................................3-30
198092101 Embedded power DC SPD Broken ........................................................3-30
198092102 Embedded power DCBreaker Alarm ......................................................3-31
198092103 Embedded power Bat Test Failure .........................................................3-31
198092104 Embedded power Bat Discharge............................................................3-32
198092116 Embedded power AC Auxiliary Output Switch Off ..................................3-32
198092117 Embedded power Rectifier Module Fault................................................3-33
198092203 Board not-configured alarm....................................................................3-33
198092206 Battery alarm .........................................................................................3-34
198092207 AC power-cut alarm ...............................................................................3-34
198092208 Rectifier module alarm ...........................................................................3-35
198092209 Thermoelectric cooler alarm ..................................................................3-35
198092212 EPLD's register has a R/W failure alarm. ...............................................3-36
198092214 Hardware of Clock Module Fault ............................................................3-36
198092215 Lost of synchronization ..........................................................................3-38
198092216 Current Active Reference Source 1PPS Lost .........................................3-39
198092217 Air Interface Clock Unavailable ..............................................................3-39
198092219 Baseband Subunit Fault.........................................................................3-40
198092234 Embedded power type configuration error..............................................3-40
198092235 Embedded power communication interruption........................................3-40
198092236 Embedded power SMR Output Fault......................................................3-41
198092237 Embedded power Bat Under-Temp ........................................................3-41
198092238 Embedded power Bat Invalid-Temp........................................................3-42
198092239 Embedded power Battery Fault..............................................................3-42
198092241 1588 clock source unavailable ...............................................................3-43
198092242 Ir link LCV alarm ....................................................................................3-43
198092243 Abnormal DPD running status................................................................3-44
198092244 LNA alarm .............................................................................................3-44
198092245 Disable PA .............................................................................................3-44
198092246 TMA channel input is over current..........................................................3-45
198092247 Over-high temperature of PA .................................................................3-46
198092248 Optical module out-of-position alarm......................................................3-46
198092249 RF board PLL alarm...............................................................................3-47
198092250 Calibration file on TRx board is abnormal...............................................3-47
3-2

Chapter 3 Equipment Alarm
198092251 a block check error of downlink IQ channel alarm ..................................3-48

198092252 Downlink digital IF pre-distortion alarm ..................................................3-48
198092253 Application software monitoring alarm....................................................3-49
198092254 Remote output power abnormal voltage alarm .......................................3-50
198092255 Remote input power over-voltage alarm.................................................3-50
198092256 Remote input power under-voltage alarm...............................................3-51
198092257 Remote antenna over VSWR alarm .......................................................3-52
198092258 Lost of frame rate and frame number .....................................................3-52
198092259 Battery low-voltage alarm.......................................................................3-53
198092260 Faulty external device connected at a dry contact ..................................3-53
198092261 Outdoor lightning protection box alarm...................................................3-54
198092262 Breaker alarm in indoor lightning protection box.....................................3-54
198092263 Lightning protection device alarm in indoor lightning protection box ......3-55
198092264 Over-voltage alarm of main power input.................................................3-56
198092265 Main power input power-cut alarm .........................................................3-57
198092266 Under-voltage alarm of main power input...............................................3-57
198092267 General fault of main power ..................................................................3-58
198092268 PWR monitoring unit alarm ...................................................................3-58
198092269 Over-high temperature of RU board .......................................................3-59
198092270 Slight-high temperature of RU board......................................................3-59
198092272 The value of RSSI over reverse link is low. ...........................................3-60
198092273 The value of RSSI over reverse link is high. ..........................................3-60
198092274 Slight-high temperature of PA ................................................................3-61
198092275 PA communication fault..........................................................................3-61
198092276 Receiving RF channel fault ....................................................................3-62
198092277 Clock module fault .................................................................................3-62
198092278 Abnormal power.....................................................................................3-63
198092279 Downlink analog power exceeds rated power slightly.............................3-63
198092280 Downlink digital power exceeds rated power slightly .............................3-64
198092281 Downlink carrier baseband power is low ................................................3-64
198092282 Downlink carrier analog power is low .....................................................3-65
198092283 Remote antenna VSWR alarm ...............................................................3-65
198092284 Input reference clock is abnormal ..........................................................3-66
198092285 Internal clock is abnormal ......................................................................3-66
198092286 The uplink frame at optical/electric port is unlocked ...............................3-67
198092287 The channel downlink frame is unlocked................................................3-67
198092288 The PLL clock is unlocked .....................................................................3-68
198092289 The optical/electric module is not in the position of optical port ..............3-69
198092290 The uplink optical/electric link is interrupted ..........................................3-69
198092291 The input frame synchronous signal is wrong.........................................3-70
198092292 An alarm is given when an optical fiber is wrongly connected ................3-70
198092293 The Rx optical port at RRU has no light signal. ......................................3-71
198092294 The frame transferred over Rx port of RRU is unlocked. ........................3-71
198092295 RRU power-cut alarm ...........................................................................3-72
198092298 MMC Fault .............................................................................................3-72
3-3

198092311 IQ reported is failed ...............................................................................3-73

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

198092388 It is failed to configurate power supply....................................................3-90

198092393 UES ethernet semiduplex alarm.............................................................3-91
198092394 Several rectifiers faulty...........................................................................3-91
198092400 Board smart powered-down ...................................................................3-92
198092401 E1 link self-loop .....................................................................................3-92
198092409 GNSS antenna feeder alarm ..................................................................3-92
198092415 The built-in-type GNSS receiver has an alarm. ......................................3-93
198092416 The built-in-type GNSS antenna has a feeder cable alarm .....................3-93
198092418 The external-panel-type GNSS receiver has an alarm............................3-94
198092419 The external-panel-type GNSS antenna has a feeder cable alarm. ........3-94
198092421 The external-panel-type GNSS receiver has an alarm, indicating its
foreground working mode is inconsistent with background. ......................................3-95
198092422 The external-backplane-type GNSS receiver has an alarm. ...................3-95
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. .................................3-97
198092426 GNSS cascading clock has an alarm .....................................................3-97
198092433 RRU network interrupted alarm..............................................................3-98
198092434 Clock line abnormal connection in stack mode.......................................3-98
198092435 Inter-frame Ethernet link broken in stack mode .....................................3-98
198092436 Loss of clock synchronization at slave frame..........................................3-99
198092437 RU radio frequency group unavailable ...................................................3-99
198092438 Device in low temperature ...................................................................3-100
198092439 Uplink transport port of a base station operates in a different mode from
configured one. .....................................................................................................3-100
198092447 Unbalanced AC phase voltage of built-in power ...................................3-101
198092448 High AC phase current of built-in power ...............................................3-101
198092449 Missing AC phase voltage of built-in power .........................................3-102
198092450 Battery low-voltage cut-off of built-in power .........................................3-102
198092451 Broken LLVD1 branch E of built-in power .............................................3-103
198092452 Broken LLVD1 branch of built-in power ...............................................3-104
198092453 Broken LLVD2 branch E of built-in power .............................................3-105
198092454 Broken battery cut-off branch E of built-in power ..................................3-106
198092455 Broken battery cut-off branch of built-in power ....................................3-106
198092456 Abnormal battery current of built-in power ...........................................3-107
198092457 Abnormal CAN bus of built-in power ...................................................3-108
198092458 Abnormal battery of built-in power .......................................................3-108
198092459 Abnormal input dry contact of built-in power ........................................3-108
198092460 High-temperature cut-off of built-in power ............................................3-109
198092461 BBU inter-subrack frame synchronization failure alarm ........................3-109
198092550 User-defined dry contact alarm 1 ......................................................... 3-110
3-5


198092559 User-defined dry contact alarm 10 ....................................................... 3-113
198092560 User-defined dry contact alarm 11........................................................ 3-113
198092577 User-defined dry contact alarm 28 .......................................................3-120
3-6


198094800 SRIO Communication Abnormal ..........................................................3-128
198094828 The board is unavailable ......................................................................3-129
198094829 eBBU synchronization abnormal ..........................................................3-129
198096550 Alarm of fiber configuration ..................................................................3-129
198096551 RRU unconfigured ..............................................................................3-130
198096552 Difference of fiber time delay of two RRUs in same sector exceeded
system limit ............................................................................................................3-130
198096553 RRU Type is not consistent with configuration type ..............................3-130
198096554 Failure of optical decoding in BBU .......................................................3-131
198096555 Failure of optical decoding in RRU .......................................................3-131
198096556 IQ link input loses lock .........................................................................3-131
198096558 Downlink baseband power abnormal ...................................................3-132
198096558 Guide frequency that BBU sends to RRU is too high or too low............3-132
198096559 RRU adjust channel or adjust cable fault..............................................3-132
198096560 Master and slave monitor link alarm.....................................................3-133
198096561 Coherence alarm of antenna channel swing and phase .......................3-133
198096562 RRU self check failed when power on ..................................................3-133
198096563 RRU device alarm................................................................................3-134
198096565 Configuration parameter of RRU external device not consistent with
real parameter........................................................................................................3-134
198096568 RRU used power module is too hot......................................................3-134
198096569 RRU offline parameter check failure ....................................................3-135
198098431 Abnormal current alarm at NSBT port .................................................3-135
198098432 AISG/NSBT port turn-off alarm due to over current ..............................3-136
198098434 Abnormal transmission power at antenna port ....................................3-137
198098435 Closed-loop power control adjustment exceeding normal range...........3-137
198098436 Failure in configuring power level .........................................................3-137
3.1 198100270 Optical signals transmitted from BBU to

RRU carry wrong clock information
Detailed Information Optical signals transmitted from BBU to RRU carry wrong clock
information.
Severity Critical

Work normally
RRU cannot provide services.
Probable Cause PLL clock is unloced at optical port
3-7

Handling Suggestion 1. Check fiber connection.

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

Detailed Information RRU reports an unlocked local oscillator alarm.
Severity Critical

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 1. IF sampling clock is unlocked or lost.

2. RF PLL clock is unlocked.
Handling Suggestion 1. Check fiber connection.

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

Detailed Information This alarm is reported when a kind of clock signal in RRU is unlocked,
including IF clock, DAC clock, ADC clock, inside FPGA clock.
Severity Major

Work normally
The quality of services may be reduced.
Probable Cause RRU internal clock (e.g. IF clock, DAC clock, ADC clock, FPGA inside
clock) is unlocked.
Handling Suggestion 1. Reset RRU.

2. If it doesn't work, replace the RRU.
3-8

3.4 198100273 Downlink channel fault alarm

Detailed Information This alarm is reported when the value of RRU Tx channel gain is too
low.
Severity Major

Work normally
Because RRU Tx channel cannot work properly, services borne on it
are interrupted.
Probable Cause 1. RRU hardware fault.

2. RRU software fault.
3. Abnormal baseband power.
Handling Suggestion 1. If the alarm occurs occasionally and lasts for less than 10 minutes,
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

Detailed Information This alarm is reported when the value of RRU Tx channel power is
too high or low.
Severity Major

Work normally
are interrupted.
Probable Cause 1. Hardware fault (either Tx channel fault or power detection channel
fault).
2. Software fault.
ignore it.
at BBU end.
3-9

3.6 198100274 Downlink output under/over-power

alarm
Detailed Information This alarm is reported when the value of RRU Tx channel power is
too high or low.
Severity Major

Work normally
are interrupted.
Probable Cause 1. Hardware fault (either Tx channel fault or power detection channel
fault).
2. Software fault.
ignore it.
at BBU end.
3.7 198092008 FPGA register read/write error

Detailed Information None
Severity Major

The board is faulty.
2. Service Impact:
The board software update fails and the services provided by this board
is completely interrupted.
Probable Cause The board's logic cannot work normally.
Handling Suggestion 1. Check whether the board has over-temperature alarm, if yes, handle
the alarm first.
2. Reset the board.
3-10

3.8 198092009 Ethernet access network interface

abnormal
Detailed Information Ethernet access network interface abnormal.
Severity Major
System Impact Ethernet is unavailable. If there is no E1 connection, base station may

be dropped.
Probable Cause None
Handling Suggestion 1. In Configuration Management, check whether the Ethernet interface

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

Detailed Information 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.
Severity Major
System Impact None
Probable Cause None
Handling Suggestion 1. Check whether the frame format configured in Configuration

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

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 198092012 E1/T1 output port unavailable

Detailed Information 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.
Severity Major
System Impact None
Probable Cause None
Handling Suggestion 1. Check whether the frame format configured in Configuration

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
Detailed Information 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.
Severity Warning
System Impact None
Probable Cause None
3-12

Handling Suggestion 1. Check E1/T1 line connection in DDF rack .Confirm DDF rack is
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

Detailed Information During the CC board's power-on process, if CC fails to obtain the board
configuration from database, this alarm is reported.
Severity Major
System Impact Board power-on failed.
Probable Cause 1. The database query fails.

2. The database query succeeds but the data is abnormal.
3. Board status setting fails.
Handling Suggestion 1. In the Configuration Management interface, check whether board

configuration is correct.
2. In the Configuration Management interface, operate configuration
data synchronization.
3.13 198092049 Lightning protection device alarm

Detailed Information This alarm is reported when the lightning protection device has a fault
due to lightning attack, not well grounded or ageing failure.
Severity Minor

Work normally
The power interface cannot be protected from lightning attack.
3-13

Probable Cause 1. View the relevant network management interface and finds that the
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 1. Select Configuration Resource Management and check whether dry
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

Detailed Information This alarm is reported when PSU is broken or its monitoring cable is
not well connected.
Severity Minor
System Impact None
Probable Cause None
Handling Suggestion 1. Check whether the monitoring cable of PSU is well connected.
2. Replace PSU module.
3.15 198092052 PSU fan alarm

Detailed Information This alarm is reported when the PSU fan is faulty.
Severity Minor
System Impact None
Probable Cause None
Handling Suggestion 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

Detailed Information The board is powered off
3-14

Severity Major

2. Service Impact:
The board's communication link is broken, and services the board
bears are interrupted.
Probable Cause The board is powered-off.
Handling Suggestion 1. Check the addition information of the alarm. If the alarm has
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
Detailed Information When the system detects that external main power supply has a fault,
this alarm is reported through dry contact.
Severity Major

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 1. Main power supply is faulty.

2. Environment Monitor Unit is faulty.
3-15

Handling Suggestion 1. Replace main power supply.

2. Reset the board.
3. Replace the relevant dry contact cable.
4. Replace the board .
3.18 198092071 Abnormal temperature sensor

Detailed Information This alarm is reported when the temperature sensor is abnormal.
Severity Warning

Work normally
The system cannot monitor temperature of environment or devices.
Services are not affected.
Probable Cause 1. The sensor is not connected.

2. The cable connected to the sensor is broken.
3. The sensor is broken.
Handling Suggestion If the temperature sensor should be installed on FCE board, please
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

Detailed Information This alarm is reported when the board is configured in the network
management interface but actually is not inserted in the slot.
Severity Major

2. Service Impact:
The board can't bear any service.
3-16

Probable Cause 1. The network management interface shows the slot in which the
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.
3. The network management interface shows the slot in which the
board is configured, but the connection part is physically damaged.
Handling Suggestion 1.Insert a board in the slot.

2.Unplug and plug the board.
3.Replace the shelf.
3.20 198092073 Embedded power AC-in Switch Off

Detailed Information AC input switch is OFF.
Severity Critical
System Impact 1. The rectifier fails to work normally, only the battery can work.
2. When the battery runs out, the base station is powered down.
Probable Cause 1. The air break switch of the main AC input is not closed.
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 1. If the air break switch of the main AC input is not closed, then close it.
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

Detailed Information The mains supply is cut off and there is no standby AC input.
Severity Critical
System Impact 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.
Probable Cause 1. The AC power supply is powered down.

2. The AC transducer's connection is faulty or the transducer is
damaged.
3-17

Handling Suggestion 1. If the AC power supply is powered down, use the generator to
provide power supply.
2. Check whether the AC transducer's connection is normal and
whether the transducer has no problem.
3.22 198092075 Embedded power SPD-C Broken

Detailed Information The class C arrester loop is faulty.
Severity Minor
System Impact The lightning protector fails.
Probable Cause 1. The lightning protector is damaged.

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 1. The lightning protector is damaged. Replace the lightning protector.
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

Detailed Information The class D arrester loop is faulty.
Severity Minor
System Impact The lightning protector fails.
Probable Cause 1. The lightning protector is damaged.

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

Handling Suggestion 1. The lightning protector is damaged. Replace the lightning protector.
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 198092077 Embedded power AC Under-Volt

Detailed Information The AC input phase voltage is lower than Phase.OverVolt.
Severity Minor
System Impact The load capacity of the power supply is influenced, which also affects
the normal power supply for the base station.
Probable Cause 1. The AC input voltage is low.

2. The AC under-voltage value of the monitoring unit is set too high.
damaged.
Handling Suggestion 1. Improve the power supply quality of the equipment room.
2. If the detected AC voltage value is lower than the threshold value
for alarm of AC voltage being low, then appropriately decrease the
threshold value.
3.25 198092078 Embedded power AC Over-Volt

Detailed Information The AC input phase voltage is higher than Phase UnderVolt.
Severity Minor
System Impact 1. The operation safety of the rectifier is influenced.

2. The rectifier will automatically power off for protection.
3-19

Probable Cause 1. The AC input voltage is high.

2. The AC over-voltage value of the monitoring unit is set too low.
damaged.
Handling Suggestion 1. Improve the power supply quality of the equipment room.
2. If the detected AC voltage value is higher than the threshold value
for alarm of AC voltage being high, then appropriately increase the
threshold value.
3.26 198092079 Embedded power AC Current Over

Detailed Information The AC input current is higher than the AC current maximum.
Severity Minor
System Impact 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.
3. It influences the power supply for the base station.
Probable Cause 1. The AC input current is larger than the threshold value for the alarm.
2. The power supply's load is too heavy.
Handling Suggestion 1. Check the threshold value of the monitoring unit's AC input current.
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

Detailed Information Rectifier output over-voltage.
Severity Critical
3-20

System Impact 1. The rectifier will be powered off for protection.

Probable Cause 1. The rectifier's output voltage is abnormal.

2. The rectifier is damaged.
Handling Suggestion 1. Pull out the rectifier and plug it in again, and make it powered on.
2. Replace the rectifier.
3.28 198092081 Embedded power SMR Over-Iout

Detailed Information Rectifier output over-current.
Severity Critical

Probable Cause 1. The over-current protection circuit of the rectifier is faulty.

Handling Suggestion 1. Pull out the rectifier and plug it in again, and make it powered on.
3.29 198092082 Embedded power SMR Fan Fault

Detailed Information The fan of the rectifier is abnormal.
Severity Critical

Probable Cause 1. The rectifier's fan is damaged or blocked by some foreign body.
Handling Suggestion 1. Check whether the fan is blocked by some foreign body.
2. Check the monitoring unit's socket.
3.30 198092083 Embedded power SMR PFC Fault

Detailed Information This alarm is reported when the rectifier-related PFC has one of these
faults: over-current input, over-voltage output or under-voltage output.
3-21

Severity Critical

Probable Cause The PFC circuit of the rectifier is faulty.
Handling Suggestion Replace the rectifier.
3.31 198092084 Embedded power SMR Over-Vin Off

Detailed Information Rectifier AC input over-voltage.
Severity Critical

Probable Cause 1. The AC input voltage of the rectifier is higher than the threshold
value of over-voltage protection.
Handling Suggestion 1. Check whether the AC voltage is higher than the threshold value.
3.32 198092085 Embedded power SMR Under-Vin Off

Detailed Information Rectifier AC input under-voltage.
Severity Critical
System Impact 1. The rectifier will have current-limiting output or be powered off for
protection.
Probable Cause 1. The AC input voltage of the rectifier is lower than the threshold value
of under-voltage protection.
Handling Suggestion 1. Check whether the AC voltage is lower than the threshold value.
3.33 198092086 Embedded power SMR H.T. Off

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


Probable Cause 1. The heat radiator of the rectifier is too hot.

Handling Suggestion 1. Check whether the temperature of the rectifier's heat radiator is
higher than the threshold value.
2. Improve the ventilation condition of the equipment room.
3.34 198092087 Embedded power SMR Env.H.T.Off

Detailed Information The ambient temperature of the rectifier is too high which causes the
rectifier to shut down.
Severity Critical

Probable Cause 1. The environment temperature of the rectifier is too high.

3.35 198092088 Embedded power SMR Env.H.T

Detailed Information The ambient temperature of the rectifier is too high which causes the
output power of the rectifier to derate.
Severity Critical
System Impact 1. The load capacity of the rectifier is influenced.

Probable Cause 1. The environment temperature of the rectifier is higher than

the threshold temperature for load-reduction (i.e. if the threshold
temperature for load-reduction is exceeded, the power supply will be
powered off for some loads).
3-23

3.36 198092089 Embedded power SMR L.Vin

Detailed Information The rectifier AC input voltage is too low which causes the output power
of the rectifier to derate.
Severity Critical
System Impact 1. The load capacity of the rectifier is influenced.

Probable Cause 1. The AC input voltage of the rectifier is lower than the threshold
voltage for under-voltage load-reduction.
Handling Suggestion 1. Check whether the AC voltage is lower than the threshold value.
3.37 198092090 Embedded power SMR Fuse Broken

Detailed Information The output fuse of the rectifier is blown.
Severity Critical

Probable Cause 1. The output fuse in the rectifier is burned.

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

Detailed Information The communication between the rectifier and monitoring unit is
abnormal.
Severity Critical
3-24

System Impact 1. The system fails to implement battery management.

2. The AC voltage sampling is influenced.
3. The decision whether the AC power supply should be powered off is
influenced.
Probable Cause 1. The RS485 communication cable of the rectifier is broken or

short-circuited.
2. The monitoring crystal-oscillator's frequency of the rectifier is not
calibrated.
3. When the AC power supply is powered down, the actual load is
smaller than the threshold value of the minimum load.
Handling Suggestion 1. Check whether the communication of all rectifiers is interrupted.

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

Detailed Information The DC output voltage is lower than DC OverVolt.
Severity Minor
System Impact 1. Although it has no influence on the system, it is necessary to find out
the alarm cause to avoid other faults.
Probable Cause 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.
Handling Suggestion 1. Check the DC output voltage.

2. Check whether the DC under-voltage value of the monitoring unit
is set appropriately.
3-25

3.40 198092093 Embedded power DC Over-Volt

Detailed Information The DC output voltage is higher than DC UnderVolt.
Severity Major
System Impact The rectifier will be powered off for protection, only the battery can work.
Probable Cause 1. The DC output voltage is high.

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

2. Check whether the DC under-voltage value of the monitoring unit
3.41 198092094 Embedded power DC Loop Broken

Detailed Information The DC loop is open.
Severity Critical
System Impact The power supply for the load is influenced.
Probable Cause 1. The fuse of the load's loop is burned (or the air break switch is
broken).
2. The detecting cable of the load's loop is disconnected or of bad
contact.
Handling Suggestion 1. Check whether the load's loop is short-circuited.

2. Check whether the capacity of the fuse (or air break switch) is set
appropriately.
3. The detecting cable of the load's loop is disconnected or of bad
contact.
3-26

3.42 198092095 Embedded power Bat Loop Broken

Detailed Information The battery loop is open.
Severity Critical
System Impact 1. When the loops of all batteries are broken, the system fails to
implement battery management.
2. The loops of all battery groups are broken. After the AC power
supply is powered down, the base station is also powered down.
Probable Cause 1. The fuse of the battery's loop is burned.

2. The detecting cable of the battery's loop is disconnected or of bad
contact.
Handling Suggestion 1. Check whether the load's loop is short-circuited, and whether the
capacity of the battery's fuse is set appropriately.
2. Check whether the threshold value for the fuse alarm of the
monitoring unit is set appropriately.
3. Check whether the detecting cable of the battery's loop is
4. Check whether the monitoring unit's socket is of bad contact or
disconnected.
3.43 198092096 Embedded power Bat Under-Volt

Detailed Information The battery voltage is lower than Batt.UnderVolt.
Severity Major
System Impact Although it has no influence on the system, it is necessary to find out
the alarm cause to avoid other faults.
Probable Cause 1. The battery's voltage is low.

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

Handling Suggestion 1. Check the battery's output voltage.

2. Check whether the battery's under-voltage value of the monitoring
unit is set appropriately.
3. Check whether the monitoring unit's socket is inserted properly, and
whether the cable is broken or of bad contact.
3.44 198092097 Embedded power Bat Over-Temp

Detailed Information The temperature of battery is higher than Batt.OverTemp.
Severity Minor
System Impact The battery's service lifetime is influenced.
Probable Cause 1. The battery's temperature is higher than the threshold value of
over-temperature of battery.
2. The battery's over-temperature value of the monitoring unit is set
too low.
3. The temperature sensor of the battery is damaged.
Handling Suggestion 1. Check the battery's temperature.

2. Check whether the battery's over-temperature value of the
3. Check whether the battery's temperature sensor is damaged.
disconnected.
3.45 198092098 Embedded power TmpL Shut-Down

Detailed Information The ambient temperature is lower than TmpL Shut Down, causing all
the loads to shut down.
Severity Critical
System Impact It influences the power supply for the base station.
Probable Cause 1. The system temperature is lower than the temperature for
power-down in low-temperature environment.
3-28


2. Check whether the threshold value for power-down in
low-temperature environment of the monitoring unit is set appropriately.
disconnected.
3.46 198092099 Embedded power 1st Shut-down

Detailed Information When the battery voltage is lower than LVD1 Voltage, the less important
loads are shut down.
Severity Critical
System Impact The secondary load is powered down.
Probable Cause 1. When the battery's voltage decreases to the threshold value for first
power-down, the system performs the first power-down operation.
2. The first power-down voltage of the monitoring unit is not set
appropriately.
3. The manual power-down switch is set incorrectly.
4. The DC contactor is connected incorrectly.
5. The DC contactor is damaged.
6. The SDCB board is damaged.
Handling Suggestion 1. Check the battery's voltage to see whether it is lower than the
voltage for first power-down.
2. Check whether the first power-down voltage of the monitoring unit
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

3.47 198092100 Embedded power 2nd Shut-down

Detailed Information When the battery voltage is lower than LVD2 Voltage, all the loads
are shut down.
Severity Critical
System Impact The base station is powered down, and the communication is
interrupted.
Probable Cause 1. When the battery's voltage decreases to the threshold value for
second power-down, the system performs the second power-down
operation.
2. The second power-down voltage of the monitoring unit is not set
appropriately.
3. The manual power-down switch is set incorrectly.
4. The DC contactor is connected incorrectly.
5. The DC contactor is damaged.
6. The SDCB board is damaged.
Handling Suggestion 1. Check the battery's voltage to see whether it is lower than the
voltage for second power-down.
2. Check whether the second power-down voltage of the monitoring
unit is set appropriately.
3. Check the manual power-down switch to see whether it is in the
automatic status or the connected status.
4. Check whether the second power-down DC contactor is damaged.
Measure whether there is 48 V voltage at the two ends of the
DC contactor's control coil, and check whether the control coil is
disconnected or broken.
5. Check the DC contactor's cable connection.
6. If the Shut-Down Control Board (SDCB) is configured, then check
whether the power-down is caused by SDCB fault.
3.48 198092101 Embedded power DC SPD Broken

Detailed Information The DC arrester is faulty.
Severity Critical
System Impact The lightning protection capability is influenced. Replace the lightning
protector in time.
3-30

Probable Cause 1. The lightning protector's detecting cable is disconnected or of bad

contact.
2. The DC lightning protector is damaged.
Handling Suggestion 1. Check whether the detecting cable is disconnected or of bad contact.
2. Replace the DC lightning protector.
3.49 198092102 Embedded power DCBreaker Alarm

Detailed Information DC breaker breaks.
Severity Minor
System Impact If the circuit breaker can not be powered down normally, then the
battery might be discharged.
Probable Cause 1. The DC contactor is damaged, there is one or two power-down

alarms but no power-down operation is performed.
2. The load's current is very small, and the current of the loop where
the load is located changes little before and after power-down.
3. The control loop of system power-down is broken (such as that the
terminal is not connected or the control signal cable is broken).
4. The output of the monitoring control signal is abnormal.
Handling Suggestion 1. No handling is required if the problem is due to the load's current
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

Detailed Information The test stops but the test duration does not reach the maximum test
time.
Severity Warning
System Impact It does not influence the power supply for the base station.
Probable Cause 1. Before the test time expires, the battery discharge is stopped.
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

Handling Suggestion 1. Check whether the battery is connected correctly.

2. After the battery is fully charged, perform the test again. The test
succeeds, and the alarm is removed automatically.
3. According to the power supply's load and the battery's capacity,
appropriately set parameters such as the test time and the test voltage.
4. Replace the battery.
3.51 198092104 Embedded power Bat Discharge

Detailed Information The battery is being discharged.
Severity Minor
Probable Cause 1. The battery's discharge current is larger than the threshold value
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 1. Check whether the battery is in the discharge status.

2. Adjust the zero parameter and the slope parameter of the monitoring
unit, and calibrate the detection precision.
3. Appropriately adjust the threshold value for the alarm of battery
discharge.
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
Detailed Information The air break switch of the standby AC output is not closed.
Severity Minor
System Impact The power supply from standby AC output is influenced.
Probable Cause 1. The air break switch of the standby AC output is not closed.
2. The air break switch's contact is disconnected or of bad contact.
3-32

Handling Suggestion 1. Close the air break switch of the standby AC output.
2. Check the air break switch's contact.
3.53 198092117 Embedded power Rectifier Module

Fault
Detailed Information A rectifier module is faulty.
Severity Critical
System Impact The normal load capacity of the power supply is influenced, which also
affects the power supply for the base station.
Probable Cause 1. The rectifier module is faulty.

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 1. Check the rectifier's working status, and replace the rectifier.
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

Detailed Information This alarm is reported when a board is not configured in network
management interface, but it is inserted into a real slot.
Severity Minor

The board is not configured.
2. Service Impact:
There is no influence on services.
3-33

Probable Cause 1. The Network Management interface shows an idle slot, but a
physical board is inserted.
2. PM has a fault. A board in-slot signal has been detected, but in fact
this slot is not configured with any board.
Handling Suggestion 1. Configure this board in the Network Management interface, or

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 198092206 Battery alarm

Detailed Information This alarm is reported when the system detects that the external battery
at a dry contact is faulty.
Severity Minor

Work normally
If the battery works for a long time, the system may not work properly.
In bad situation, services are interrupted.
Probable Cause 1. A base station detects the faulty battery.

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

Detailed Information This alarm is reported when the main power is cut.
Severity Minor
3-34


Work normally
Because AC power is cut, the system can only rely on the battery for
a while.
Probable Cause 1. The dry contact is disconnected.

2. AC power-cut happens or there is no AC input due to abnormity.
Handling Suggestion 1. Check whether the monitoring cable at dry contact is good. If not,
please replace it. .
2. Start diesel engine in an emergency.
3. Restore AC power as soon as possible.
3.57 198092208 Rectifier module alarm

Detailed Information This alarm is reported when the rectifier works abnormally.
Severity Minor

Work normally
Power cannot be normally supplied so that the system paralyzes and
Probable Cause 1. The dry contact is disconnected.

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

Detailed Information This alarm is reported when the thermoelectric cooler is faulty.
Severity Minor

Work normally
When the thermoelectric cooler is faulty, battery lifetime may be
shortened. Furthermore, system services may also be affected.
Probable Cause 1. The thermoelectric cooler is faulty.

3-35

Handling Suggestion 1. Check whether the thermoelectric cooler is broken. If yes, please
replace it.
2. Replace the cable connected the thermoelectric cooler.
3.59 198092212 EPLD's register has a R/W failure alarm.

Detailed Information 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.
Severity Major
System Impact Both clock selection and switchover functions are affected.
Probable Cause 1. HOST bus is abnormal

2. MCU component is abnormal
3. EPLD component is abnormal
Handling Suggestion 1. Remove and insert the board.

3.60 198092214 Hardware of Clock Module Fault

Detailed Information 1-10M clock lost
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

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 Critical
System Impact 1. board condition:

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 None
Handling Suggestion 1-10M clock lost

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

1. Reset board
7- PLL of net port is lost
1. Reset board
3.61 198092215 Lost of synchronization

Detailed Information 1.Alarm of OCXO not locking
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 Major

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 1. The problem of crystal.

2. Board is fault.
Handling Suggestion Alarm of OCXO not locking:

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

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
Detailed Information Current Active Reference Source 1PPS Lost
Severity Minor
System Impact Long term lost can cause clock and fame cannot be synchronous, and
soft switch cannot be achieved.
Probable Cause 1. For the satellite receiver, the satellite receiver does not output 1PPS
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 1.Firstly,to check whether the configured referent signal is in

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

Detailed Information 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.
Severity Major

board run normally.
services in the board are interrupted completely.
Probable Cause 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).
3-39

Handling Suggestion Check whether the air interface clock source is configured. If it is not
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

Detailed Information When main core can't receive the slave's heartbeat in a while,alarm
is reported.
Severity Critical
System Impact Base band subunit cannot work normally.
Probable Cause Base band subunit has fault.
Handling Suggestion Reset the board.
3.65 198092234 Embedded power type configuration

error
Detailed Information The type of the power is different from the actual configuration.
Severity Major
System Impact The detection of the power alarm is influenced.
Probable Cause The type of the power is different from the actual configuration.
Handling Suggestion 1. Reconfigure the power.

2. Replace the power.
3.66 198092235 Embedded power communication

interruption
Detailed Information The communication of the power is interrupted.
Severity Major
System Impact The detection of the power alarm is influenced.
Probable Cause 1. The link to the power is faulty.

3-40

Handling Suggestion 1. Check whether the link to the power is normal.

disconnected.
3.67 198092236 Embedded power SMR Output Fault

Detailed Information SMR Output Fault
Severity Critical
Probable Cause The rectifier is damaged.
Handling Suggestion 1. Pull out the 1.rectifier and plug it in again, and make it powered on.
3.68 198092237 Embedded power Bat Under-Temp

Detailed Information The temperature of battery is less than Batt.UnderTemp.
Severity Minor
System Impact The battery's service lifetime is influenced.
Probable Cause 1. The battery's temperature is lower than the threshold value of
under-temperature of battery.
2. The battery's under-temperature value of the monitoring unit is set
too high.

2. Check whether the battery's over-temperature value of the
disconnected.
3-41

3.69 198092238 Embedded power Bat Invalid-Temp

Detailed Information The temperature of battery is an invalid value.
Severity Minor
System Impact The battery temperature detection is influenced.
Probable Cause 1. The environment temperature exceeds the normal range allowed
in the detection.
3. The temperature sensor of the battery is not connected.

2. Check whether the temperature sensor is connected reliably.
3. Replace the temperature sensor.
3.70 198092239 Embedded power Battery Fault

Detailed Information The battery is faulty.
Severity Critical
System Impact When all the battery is faulty, the base station will be powered down
after the AC power supply is powered down.
Probable Cause 1. The battery is not installed, but the monitoring unit configured the
battery capacity.
2. The connection to the power is not reliable.
5. The battery is faulty.
Handling Suggestion 1. Check whether the battery is installed, and whether the battery
capacity is configured properly.
2. Check whether the power is connected reliably.
disconnected.
5. Replace the battery.
3-42

3.71 198092241 1588 clock source unavailable

Detailed Information 1588 clock link channel is unavailable.
Severity Minor
System Impact 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
Probable Cause There is no available 1588 clock link
Handling Suggestion 1.Check whether the CC physical connection is normal.

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 198092242 Ir link LCV alarm

Detailed Information Ir link LCV(line code violation) error exceeds threshold, this alarm
is reported.
Severity Warning

2. Service Impact:
Code error might occur to signaling and IQ, resulting in service
performance degradation and interruption
Probable Cause 1. Poor fiber connection;

2. Optical module defect;
3. Ir interface chipset work abnormally.
Handling Suggestion 1. Check the possible failure with the fiber optics and the optical module
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

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

Detailed Information DPD running status is abnormal.
Severity Warning
System Impact I. Board Status:

Board Operation is normal
II. Service Impact:
RF output quality and service performance are affected
Probable Cause DPD chip runs abnormally.
Handling Suggestion The system can recover automatically without manual intervention.
3.74 198092244 LNA alarm

Detailed Information When working voltage or gain of LNA is out of normal working range,
the system will give this alarm.
Severity Major

Board Operation is normal
II. Service Impact:
Service coverage extent is affected
Probable Cause 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.
Handling Suggestion 1. Replace the internal LNA of RRU.

2. Reset the board.
3. Replace the internal LNA of the board.
3.75 198092245 Disable PA

Detailed Information This alarm is given when it detects that PA is in the closed status.
Severity Minor
3-44

System Impact Service interruption
Probable Cause 1. PA is disable by operation in OMCB.

2. Close PA in corresponding channel when Remote antenna over
VSWR alarm is reported.
Handling Suggestion 1. Check setting of PA status in OMCB.

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

Detailed Information This alarm is reported when the system detects that TMA channel input
current is over threshold (135~140mA), but less than 200mA.
Severity Major
3-45


Work normally
2. Service Impact:
Cell coverage is slightly affected
Probable Cause 1. The configured threshold is not consistent with real TMA threshold;
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 1. Check if the alarm threshold of TMA power supply is configured
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

Detailed Information The temperature of PA exceeds over-high temperature threshold.
Severity Critical

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 1. The fan at PA layer is abnormal, which causes a cooling fault.
2. PA is abnormal.
Handling Suggestion High environmental temperature:

(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

Detailed Information Optical module out-of-position.
Severity Minor
3-46


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 Optical module out-of-position.
Handling Suggestion 1. Check if optical module and fiber have been installed at local board
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

Detailed Information RF board has detected that PLL is not locked.
Severity Critical

Work normally
2. Service Impact:
RF output is affected. RF channel cannot work normally. The service
on the board is down
Probable Cause 1. Clock input from main control board is wrong;

2. Board hardware fault.
Handling Suggestion 1. Check the current software version of BS and ensure it is the correct
version.
2. Reset the board.
3.80 198092250 Calibration file on TRx board is

abnormal
Detailed Information The calibration file on TRx board is incomplete or damaged.
Severity Minor
3-47


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 The corresponding board calibration data is incomplete or damaged.
Handling Suggestion 1. Reset board.

2. Replace board.
3.81 198092251 a block check error of downlink IQ

channel alarm
Detailed Information DL IQ channel is error in receiving data.
Severity Major

2. Service Impact:
Downlink communication is abnormal from UBPG to RRU
Probable Cause Downlink IQ channel receives wrong data
Handling Suggestion 1. Check if the following alarm (clock abnormal) occurs in BBU.
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
198084060 RF board PLL alarm
198084231 RRU clock frequency drift
198084299 PLL unlock alarm
2. Reset board.
3.82 198092252 Downlink digital IF pre-distortion alarm

Detailed Information Digital IF pre-distortion fault.
Severity Major
3-48


Work normally.
2. Service Impact:
RF output quality is affected. The service on the board is down.
Probable Cause 1. DPD chip runs abnormally;

2. Software operation on DPD is failed.
Handling Suggestion 1. On NMS fault management interface, check if the following alarm
(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

Detailed Information RRU doesn't send a heart-beat message to BBU.
Severity Critical
System Impact 1.Work normally.

2. Service Impact:
The service on the board might be down
Probable Cause RRU communication is broken or software is abnormal
Handling Suggestion 1. Check if the board has "Board communication link is interrupted"
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

3.84 198092254 Remote output power abnormal

voltage alarm
Detailed Information The output voltage of power module is abnormal.
Severity Major

2. Service Impact:
The board or system might fail to work normally. The service on the
board might be down.
Probable Cause Power module output is abnormal.
Handling Suggestion 1. Check the power input voltage of the power module. Replace the
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.85 198092255 Remote input power over-voltage alarm

Detailed Information 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).
Severity Major

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 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).
3-50

Handling Suggestion 1. The AC input voltage of power module is higher than the alarm
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
Detailed Information 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).
Severity Major

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 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).
Handling Suggestion 1. The AC input voltage of power module is lower than the alarm
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

3.87 198092257 Remote antenna over VSWR alarm

Detailed Information VSWR at antenna port is higher than limit(2.5~3.0).
Severity Major

Work normally.
2. Service Impact:
The board or system fails to work normally. The service on the board
is down.
Probable Cause The value of VSWR is greater than (2.5~3.0), there is very strong
same-frequency interference signal, or RRU is faulty
Handling Suggestion 1. Check the antenna failure.

(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

Detailed Information Discontinuous frame number alarm, frame rate not received alarm
within 160ms.
Severity Minor
3-52


Work normally.
2. Service Impact:
Board communication link is down. The board on the service is down.
Probable Cause 1. Frame number is discontinuous.

2. There is no frame rate received within 160ms.
Handling Suggestion 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

Detailed Information This alarm is reported when the battery is under voltage.
Severity Minor

Work normally
Because battery voltage is low, its lifetime is affected. If battery engergy
is used up, the system cannot work normally.
Probable Cause The battery voltage is very low.
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
Detailed Information This alarm is reported when the external device at a dry contact is faulty.
Severity Minor

Work normally
It doesn't affect services.
Probable Cause Locate the alarm cause according to real external devices.
3-53

Handling Suggestion 1. Replace the lightning protection device.

2. Reset the SA board.
3. Replace the cable that is connected to the dry contact.
4. Replace SA board.
3.91 198092261 Outdoor lightning protection box alarm

Detailed Information Outdoor lightning protection box is faulty.
Severity Minor

Work normally
Devices cannot be protected from lightning attack, but services will
not be affected.
Probable Cause 1. The lightning protection device is faulty because of lightning attack,
not well grounded or ageing failure.
2. The dry contact is not well connected or correctly configured.
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
Detailed Information The breaker in an indoor lightning protection box is protected against
over current or turns in open circuit.
Severity Major
3-54


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 1. The breaker is protected against over current or turns in open circuit.
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
Detailed Information The lightning protection device in an indoor lightning protection box
has a fault.
Severity Minor

Work normally
Devices cannot be protected from lightning attack, but services will
not be affected.
Probable Cause 1. The lightning protection device is faulty because of lightning attack,
not well grounded or ageing failure.
3-55

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 198092264 Over-voltage alarm of main power input

Detailed Information This alarm is reported when the system detects that input voltage of the
main power at dry contact is abnormal.
Severity Major

Work normally
Either the board or the system may not work properly. All services
borne on the board are interrupted.
Probable Cause 1. The input voltage of main power is abnormal.

2. The environment monituring unit (EMU) is faulty.
Handling Suggestion 1. Check whether the input voltage of the main power module is
abnormal. If yes, replace it.
DC voltage: -36 V~-60 V
please replace it.
3. Reset the board.
3-56

3.95 198092265 Main power input power-cut alarm

Detailed Information This alarm is reported when the system detects that main power input
at dry contact is abnormal.
Severity Major

Work normally

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
Detailed Information This alarm is reported when the system detects that main power input
at dry contact is abnormal.
Severity Major

Work normally

3-57

Handling Suggestion 1. Check whether input voltage of the main power module is abnormal.
If yes, replace it.
please replace it.
3. Reset the board.
3.97 198092267 General fault of main power

Detailed Information This alarm is reported when the system detects that the main power at
dry contact is faulty.
Severity Major

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 1. The main power is faulty.

3.98 198092268 PWR monitoring unit alarm

Detailed Information This alarm is reported when PWR monitoring unit is abnormal.
Severity Minor

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

Probable Cause PW monitoring unit is broken.
please replace it.
2. Replace the environment monitoring unit.
3.99 198092269 Over-high temperature of RU board

Detailed Information The temperature of RU exceeds over-high temperature threshold.
Severity Critical

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 1. The device temperature is over high.

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.

RRU fault:
(1) Replace the PA.
3.100 198092270 Slight-high temperature of RU board

Detailed Information The temperature of RU exceeds slight-high temperature threshold.
Severity Major

Work normally
The PA reduces its RF channel transmissionn power by 2db.
Probable Cause 1. The device temperature is over high.

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


RRU fault:
(1) Replace the PA.
3.101 198092272 The value of RSSI over reverse link

is low.
Detailed Information 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.
Severity Minor
System Impact 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.
Probable Cause Receiving channel is broke.
Handling Suggestion Confirm that whether it is caused by software abnormality or hardware

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.
Detailed Information 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.
Severity Minor
System Impact Uplink coverage of the cell shrinks or user uplink service cannot be
accessed.
Probable Cause 1. There is strong external interference.

2. Poor connection at antenna port causes Tx spurious emission,
which disturbs Rx.
3-60

Handling Suggestion Locate the interference problem. If it is strong external interference,

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

Detailed Information The temperature of PA exceeds slight-high temperature threshold.
Severity Major

Work normally
The PA reduces its RF channel transmissionn power by 2db.
Probable Cause 1. The fan at PA layer is abnormal, which causes a cooling fault.
2. PA is abnormal.

RRU fault:
(1) Replace the PA.
3.104 198092275 PA communication fault

Detailed Information This alarm is reported when the communication between PA and
monitoring module is failed.
Severity Critical

Work normally.
2. Service Impact:
It is impossible to configure corresponding parameters of PA module.
The service on the board is down.
Probable Cause PA communication module has a fault or the cable is loosen, which
connects PA and monitoring module.
3-61

Handling Suggestion 1. Reset the board.

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

Detailed Information 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.
Severity Critical

Work normally.
2. Service Impact:
The receiving channel of transceiver board cannot work normally. The
service on the board is down.
Probable Cause It is failed to initialize chips on RF board.

3.106 198092277 Clock module fault

Detailed Information When main control board cannot detect local benchmark clock, 61.44M
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 Critical

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

Probable Cause Hardware has fault.

3.107 198092278 Abnormal power

Detailed Information 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).
Severity Major

2. Service Impact:
Transmission power might be abnormal, affecting downlink service
quality.
Probable Cause 1. PA is not enabled.

2. PA transmit power is abnormal;
3. TRx board has a fault.
Handling Suggestion 1. Turn on the power amplifier.

2. Replace the power amplifier.
3.108 198092279 Downlink analog power exceeds rated

power slightly
Detailed Information This alarm is given when analog power exceeds rated power by
0.1~1dB for above 20 times.
Severity Critical

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 1.Software is abnormal.

2.Hardware is broken.
Handling Suggestion 1.If software is abnormal, find the problem and update software.
2.If hardware is broke, go to the flow of repairment.
3-63

3.109 198092280 Downlink digital power exceeds rated

power slightly
Detailed Information 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.
Severity Critical

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 1. Input digital signal from BBU is wrong.

2. RRU software is abnormal.
3. RRU hardware is abnormal.

2. Replace board.
3.110 198092281 Downlink carrier baseband power is

low
Detailed Information 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.
Severity Warning
System Impact Decreased transmission power causes cell coverage to shrink. Or

services cannot be provided due to wrong transmission signals.
Probable Cause 1. Input digital signal from BBU is wrong.

2. RRU software is abnormal.
3. RRU hardware is abnormal.

2. Replace board.
3-64

3.111 198092282 Downlink carrier analog power is low

Detailed Information This alarm is given when carrier analog power exceeds rated power
by 0.1~1dB for above 20 times.
Severity Warning
System Impact Decreased transmission power causes cell coverage to shrink. Or

services cannot be provided due to wrong transmission signals.
Probable Cause 1. Software is abnormal.

2. Hardware is broken.
Handling Suggestion 1. If software is abnormal, find the problem and update software.
2. If hardware is broke, go to the flow of repairment.
3.112 198092283 Remote antenna VSWR alarm

Detailed Information VSWR at antenna port is higher than limit(1.5~2.0), but lower than
limit(2.5~3.0).
Severity Major

2. Service Impact:
The service on the board is not affected.
Probable Cause 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.
Handling Suggestion 1. Check the antenna failure.

(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

(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 198092284 Input reference clock is abnormal

Detailed Information This alarm is reported when 10% error has been detected on input
frequency clock, sent from main control board.
Severity Critical

Work normally
System services work abnormally.
Probable Cause 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.
Handling Suggestion 1. Check whether the main control board has a clock alarm. If yes,
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

Detailed Information This alarm is reported when FPGA main clock and Serdes reference
clock signals on board are abnormal.
Severity Critical

Work normally
System services are interrupted.
3-66

Probable Cause The internal clock is abnormal.
Handling Suggestion 1. Open the version management function, check whether FS running
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
Detailed Information This alarm is reported when the uplink frame at optical/electric port
is unlocked.
Severity Critical

Work normally
Board logic cannot parse frame data so that system services are
interrupted.
Probable Cause 1. The optical fiber/electric cable between BBU and RRU is abnormal.
2. Board clock is abnormal.
3. RRU works abnormally.
Handling Suggestion 1. Check whether there is a RRU alarm, which is not "not detected"
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
Detailed Information This alarm is given when channel downlink TDM frame is unlocked, i.e.
failure in detecting TDM frame header.
Severity Critical
3-67


Work normally
The board logic cannot parse baseband frame data so that services
are interrupted.
Probable Cause 1. A channel board is not inserted.

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 1. Check whether the corresponding channel board works normally.
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

Detailed Information This alarm is reported when PLL chip cannot output FPGA main clock
or Serdes reference clock due to unlocked PLL.
Severity Critical

Work normally
The external clock cannot be locked by PLL so that services are
interrupted.
Probable Cause PLL on the board works abnormally.
Handling Suggestion 1. Open the Version Management function. Then check whether the
running version is correct.
2. Reset the board.
3-68

3.118 198092289 The optical/electric module is not in

the position of optical port
Detailed Information This alarm is reported when optical/electric port is not well connected.
Severity Minor

Work normally
Because the optical/electrical module is not tightly inserted, the
corresponding services are interrupted.
Probable Cause 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.
Handling Suggestion 1. Remove and insert the corresponding optical/electric module.

3.119 198092290 The uplink optical/electric link is

interrupted
Detailed Information This alarm is reported when optical port has detected LOS or the value
of cable LCV exceeds its threshold.
Severity Critical

Work normally
The cell services, associated to this optical port, are interrupted.
Probable Cause 1. Either optical fiber or electric cable is broken.

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

Handling Suggestion 1. Check whether there is a RRU alarm, which is not "not detected"
type. If yes, process it.
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.
3.120 198092291 The input frame synchronous signal

is wrong
Detailed Information 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.
Severity Major

Work normally
System services are interrupted.
Probable Cause 1. The output synchronous signal from main control board has a
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 1. Check whether the main control board has a clock alarm. If yes,
please handle it.
2. Reset the board.
3.121 198092292 An alarm is given when an optical

fiber is wrongly connected
Detailed Information This alarm is reported when Rx fiber and Tx fiber are cross-connected
to the optical ports of the same FS board.
Severity Critical
3-70


Work normally
The cell services, associated to the optical port, are interrupted.
Probable Cause 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.
Handling Suggestion 1. Check whether the corresponding optical fiber is well connected and
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.
Detailed Information The alarm will be reported when the receiving optical port of RRU in the
chain has no optical signal received.
Severity Minor
System Impact Optical link is interrupted. This happens between two optical ports,
either from previous RRU to this RRU, or from this RRU to next RRU.
Probable Cause The Rx fiber is not well connected to optical port of RRU or optical
module is broken.
Handling Suggestion 1. Reset the RRU forcibly.

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.
Detailed Information The alarm will be reported when the CPRI frame of RRU in the chain
is unlocked.
3-71

Severity Minor
System Impact Optical link is interrupted. This happens between two optical ports,
either from previous RRU to this RRU, or from this RRU to next RRU.
Probable Cause 1. The Rx fiber is not well connected to optical port of RRU or optical
module is broken.
2. RRU receiving board is fault.

is clean.
3.124 198092295 RRU power-cut alarm

Detailed Information The alarm is reported when RRU detects that power voltage is lower
than a certain value.
Severity Critical

Work normally
The corresponding cell cannot provide services.
Probable Cause 1. At RRU side, main power source is abnormal.

2. The external power device of RRU is faulty.
Handling Suggestion 1. Check whether the power cable at RRU side is abnormal.
2. Check whether the external power device has a fault.
3.125 198092298 MMC Fault

Detailed Information Exception in MMC.
Severity Critical
System Impact Board fails to power on.
Probable Cause 1. MMC is not written.

2. MMC is broken.
3-72

Handling Suggestion 1. Check whether the software version of the board and the PM board
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

Detailed Information The alarm is reported in CC board when product process fails to report
IQ.
Severity Minor

None.
II. Service Impact:
It will effect calling.
Probable Cause 1. It has no Opt speed or TDM speed correspondingly.

2. Radio Mode is not valid.
3. Protocol is incompatible between FS and RRU.
Handling Suggestion 1. Reconfigure TDM speed or Opt speed.

2. Check Radio Mode.
3. Reconfigure protocol of FS or RRU.
3.127 198092317 ACOM major alarm

Detailed Information When ACOM major alarm,this alarm is reported.
Severity Major
System Impact Service Impact:

Major fault occurs in ACOM, which might cause the performance of
corresponding cell to degrade.
Probable Cause ACOM major fault
Handling Suggestion 1. Reset the equipment.

2. Replace the equipment.
3.128 198092318 ACOM minor alarm

Detailed Information When ACOM minor alarm,this alarm is reported.
3-73

Severity Minor

Minor fault occurs in ACOM, which might cause the performance of
Probable Cause ACOM minor fault

3.129 198092319 ACOM hardware fault

Detailed Information When ACOM hardware has a fault, this alarm is reported.
Severity Major

ACOM operation is abnormal, which might cause the performance of
Probable Cause Parameter error
Handling Suggestion 1. Reset the associated RRU board.

2. Replacement the equipment.
3.130 198092320 ACOM communication link is

interrupted.
Detailed Information When ACOM communication link is interrupted, this alarm is reported.
Severity Major

Communication between ACOM device and the system is down, which
might cause the performance of corresponding cell to degrade.
Probable Cause 1. ACOM device fault.

2. The communication link between ACOM device and the system
has a problem.
3. TAC board fault.
4. EMC fault
Handling Suggestion 1. Check the communication cable between RET equipment and base
station and ensure the connection is proper and secure.
2. Reset the RRU board.
3-74

3.131 198092321 ACOM software fault

Detailed Information When ACOM software has a fault, this alarm is reported.
Severity Major

ACOM operation is abnormal, and the configuration will not take effect,
which might cause the performance of corresponding cell to degrade.
Handling Suggestion 1. Reset the associated RRU board.

3.132 198092322 AISG EEPROM error

Detailed Information When AISG EEPROM is error, This alarm is reported.
AISG device type:
RET 1
ATMA 2
ACOM 241
Severity Minor

AISG operation is abnormal, which might cause the performance of

3.133 198092323 AISG flash erase error

Detailed Information When AISG flash erase error, This alarm is reported.
AISG device type:
RET 1
ATMA 2
ACOM 241
Severity Minor

3-75


3.134 198092324 AISG flash error

Detailed Information When AISG flash write error, This alarm is reported.
AISG device type:
RET 1
ATMA 2
ACOM 241
Severity Minor


3.135 198092325 AISG other hardware error

Detailed Information When AISG other hardware has a error, This alarm is reported.
AISG device type:
RET 1
ATMA 2
ACOM 241
Severity Minor


3-76

3.136 198092326 AISG other software error

Detailed Information When AISG other software has a error, This alarm is reported.
AISG device type:
RET 1
ATMA 2
ACOM 241
Severity Minor


3.137 198092327 AISG RAM error

Detailed Information When AISG RAM is error, This alarm is reported.
AISG device type:
RET 1
ATMA 2
ACOM 241
Severity Minor


3.138 198092328 AISG UART error

Detailed Information When AISG UART is error, This alarm is reported.
AISG device type:
RET 1
ATMA 2
ACOM 241
Severity Minor
3-77



3.139 198092330 ATMA major alarm

Detailed Information When ATMA major alarm, this alarm is reported.
Severity Major

Major fault occurs in ATMA, which might cause the performance of
Probable Cause ATMA major fault

3.140 198092331 ATMA minor alarm

Detailed Information When ATMA minor alarm, this alarm is reported.
Severity Minor

Minor fault occurs in ATMA, which might cause the performance of
Probable Cause ATMA minor fault

3.141 198092332 Failed to set gain

Detailed Information This alarm is reported when it is failed to set ATMA gain.
AISG device type:
RET 1
ATMA 2
ACOM 241
3-78

Severity Major

2. Service Impact:
ATMA(ACOM) gain is inconsistent with the database record value,
resulting in incorrect RSSI value reported to the background
Probable Cause 1. Parameter error.

2. ATMA(ACOM) device link is interrupted.
3. ATMA(ACOM) device is not on-duty.
Handling Suggestion 1. On NMS configuration management interface (tower top amplifier

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

Detailed Information When ATMA hardware has a fault, this alarm is reported.
Severity Major

ATMA works abnormally, which might cause the performance of
Handling Suggestion 1. Reset EMC.
3.143 198092334 ATMA communication link is

interrupted.
Detailed Information When ATMA communication link is interrupted, this alarm is reported.
Severity Major

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

Probable Cause 1. ATMA device fault.

2. The communication link between ATMA device and the system has
a problem.
3. TAC board fault.
4. EMC fault.
Handling Suggestion 1. Check the communication cable between ATMA equipment and
base station and ensure the connection is proper and secure.
3.144 198092335 ATMA software fault

Detailed Information When ATMA software has a fault, this alarm is reported.
Severity Major

ATMA works abnormally, which might cause the performance of
Handling Suggestion Reset EMC.
3.145 198092336 Board configuration parameter error

Detailed Information 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.
Severity Major

2. Service Impact:
Probable Cause 1.The system has no such board configuration parameter.

2.Configuration parameter error. 3. Hardware error .
Handling Suggestion Reset board.
3.146 198092337 RET motor fault

Detailed Information When RET motor has a fault, this alarm is reported.
3-80

Severity Major

Operation of RET motor is down, which might cause the performance
of corresponding cell to degrade.
Probable Cause RET motor fault
Handling Suggestion 1. Open the Base station Configuration Management window, open
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

Detailed Information When RET hardware has a fault, this alarm is reported.
Severity Major

RET motor works abnormally, which might cause the performance of
Probable Cause 1. RET hardware fault.

2. EMC fault.
Handling Suggestion Check the power adjusted antenna hardware.
3.148 198092340 RET motor can't adjust

Detailed Information When RET motor can't adjust, this alarm is reported.
Severity Major

Probable Cause RET motor can't adjust
the RET equipment again.
2. Remount the RET motor.
3-81

3.149 198092341 RET motor don't respond the

adjusting command
Detailed Information When RET don't respond the adjusting command, this alarm is reported.
Severity Minor

Probable Cause RET motor don't respond the adjusting command
3.150 198092342 RET communication link is

interrupted.
Detailed Information When AISG device communication link is interrupted, this alarm is
reported.
Severity Major

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.
Probable Cause 1. RET device fault.

2. The communication cable between RET device and the system has
a problem.
3. TAC board fault.
4. EMC fault.
Handling Suggestion 1. Check the communication cable between RET equipment and base
station and ensure the connection is proper and secure.
3-82

3.151 198092343 RET don't calibrated

Detailed Information When RET don't calibrated, this alarm is reported.
Severity Major

Operation of RET motor is down. Thus the configuration cannot take
effect.
Probable Cause RET don't calibrated
3.152 198092344 RET data don't scaled

Detailed Information When RET data don't scaled, this alarm is reported.
Severity Major

effect.
Probable Cause RET data don't scaled
AISC equipment centralized management, select send the configuration
data for the RET equipment again.
2. Replace the motor.
3.153 198092345 RET position lost

Detailed Information When RET position lost, this alarm is reported.
Severity Minor

effect.
Probable Cause RET position lost
3-83

2. Remount the motor and calibrate it automatically.
3. Replace the motor.
3.154 198092346 RET software fault

Detailed Information When RET software has a fault, this alarm is reported.
Severity Major

RET motor works abnormally, which might cause the performance of
Handling Suggestion Check the system parameters.
3.155 198092352 Unmatched link mode at peer-end

electrical port of Ethernet
Detailed Information The peer-end electrical Ethernet port has different link mode from this
end.
Severity Warning

Data packets transmitted via the Electrical Ethernet port may be lost.
This may lead to interrupted services.
Probable Cause The Ethernet electrical port configured at peer end is inconsistent with
that connected to local base station.
Handling Suggestion Select Ethernet Configuration function in the Configuration Management

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

3.156 198092353 Configuration is failed.

Detailed Information Configuration is failed.
Severity Major
System Impact Impact configuration.
Probable Cause Configuration is wrong or hardware is faulty.
Handling Suggestion Check if the configuration parameter from OMCB or CC is right and
the board is broken.
3.157 198092363 Faulty main power alarm

Detailed Information This alarm is reported when the system detects that the main power at
dry contact is faulty.
Severity Major

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 1. The main power is faulty.

3.158 198092364 Calibrate Fail

Detailed Information Calibrate operation is failed.
Severity Major
System Impact It will affect service in total sector.
Probable Cause Calibrate operation makes mistakes.
Handling Suggestion 1. Check if other alarms exists, such as over-heated alarm, clock alarm
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

3.159 198092365 Low Power Exception

Detailed Information The total sending power is abnormal.
Severity Major
System Impact It will affect service in total sector.
Probable Cause The total sending power is lower than threshold.
Handling Suggestion 1. Check whether the total power is normal.

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.
Detailed Information This alarm is reported when optical module of optical port is not well
connected.
Severity Critical
System Impact The optical module of optical port is not well inserted to UCI so that
optical port cannot work.
Probable Cause 1. Optical module is in poor contact with UCI.

2. Optical module is broke.
3. UCI board is broke.
Handling Suggestion 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

no light signal.
Detailed Information This alarm is reported when optical module of optical port has detected
LOS or the value of cable LCV exceeds its threshold.
Severity Critical
System Impact Optical signal is lost at optical port of UCI so that optical port cannot
work.
3-86

Probable Cause 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.
Handling Suggestion 1. Reset the RGPS forcibly.

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.
Detailed Information This alarm is given when the receiver frame at UCI optical port is
unlocked, i.e. failure in detecting K-code header.
Severity Critical
System Impact RPGS to UCI optical link is broke.
Probable Cause 1. The optical fiber from RGPS to FS is abnormal or Optical module
is broke.
2. UCI works abnormally.
Handling Suggestion 1. Reset the RGPS forcibly.

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

Detailed Information This alarm is reported when check the fiber delay adjust is overtime.
Severity Critical
System Impact UCI fiber delay adjust is failed, so it cannot calibrate 1PPS of RGPS
and 1PPS or TOD cannot be output to CC also.
Probable Cause 1. the antenna of RGPS is broke.

2. UCI board is broke.
3-87

Handling Suggestion 1. Check whether the antenna of RGPS is normal.

2. Check whether UCI board is normal.
3.164 198092378 Board PLL is unlocked.

Detailed Information Board FPGA inner PLL is unlocked.
Severity Critical
System Impact Logic inner PLL is unlocked, so that the board communication may
be abnormal.
Probable Cause 1.The clock from CC to UCI board is loss.

2.The FPGA of UCI board works abnormal.
Handling Suggestion 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

Detailed Information The output power of PA exceeds rated power by 2 dB~3 dB.
Severity Critical
System Impact 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.
Probable Cause 1. Baseband power is abnormal, which causes very high input power of
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.

3.166 198092383 Distributing IQ resource is failed.

Detailed Information The alarm is reported when calculating IQ ranks is failed in CC board.
Severity Minor
3-88


2. Service Impact:
Probable Cause 1. Input parameter is not valid.

2. Bandwidth is not enough.
Handling Suggestion Reconfigure IQ on configuration management interface of OMCB.
3.167 198092384 It is failed to configurate IQ.

Detailed Information The alarm is reported when IQ configuration is failed in FS board.
Severity Minor

2. Service Impact:
Probable Cause 1. Input parameter is not valid.

2. Bandwidth is not enough.
Handling Suggestion Reconfigure IQ on configuration management interface of OMCB.
3.168 198092385 It is failed to configurate optical port

speed.
Detailed Information The alarm is reported when optical port speed configuration is failed
in FS board.
Severity Minor

2. Service Impact:
It will effect RRU link and IQ configuration.
Probable Cause Optical port speed is not valid.
Handling Suggestion Reconfigure optical port speed on configuration management interface

of OMCB.
3-89

3.169 198092386 It is failed to configurate TDM port

speed.
Detailed Information The alarm is reported when TDM port speed configuration is failed
in FS board.
Severity Minor

2. Service Impact:
Probable Cause TDM port speed is not valid.
Handling Suggestion Reconfigure TDM port speed on configuration management interface of

OMCB.
3.170 198092387 It is failed to configurate RRU device

delay parameter.
Detailed Information The alarm is reported when RRU device delay parameter configuration
is failed in FS board.
Severity Minor

2. Service Impact:
It will effect fibre-optical delay calculating.
Probable Cause It is failed to check RRU topo configuration according to RRU rack.
Handling Suggestion Reconfigure RRU topo on configuration management interface of

OMCB.
3.171 198092388 It is failed to configurate power

supply.
Detailed Information 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.
Severity Minor
3-90


It will effect board power supply.
2. Service Impact:
It will not effect service.
Probable Cause Power supply configuration is failed when the total power of all the
board configurated in OMCB exceeds available power of PM.
Handling Suggestion Reconfigure power supply on configuration management interface of

OMCB.
3.172 198092393 UES ethernet semiduplex alarm

Detailed Information Link is in semiduplex status.
Severity Major

2. Service Impact:
It may cause data packet loss if there is a large quantity of data.
Probable Cause Link is in semiduplex status.
Handling Suggestion Check the physical linkmode configuration.
3.173 198092394 Several rectifiers faulty

Detailed Information 2 or more rectifiers are faulty.
Severity Critical
System Impact It may affect power module to carry load so that base station cannot
be properly powered.
Probable Cause 1. Several rectifiers are faulty.

2. The faulty rectifiers are associated to input air switch. The input air
switch breaks.
3. Open phase happens.
Handling Suggestion 1. Check working status of the faulty rectifiers.

2. Check whether open phase happens.
3. Replace the faulty rectifiers.
3-91

3.174 198092400 Board smart powered-down

Detailed Information During energy-saving period, partial boards are powered down because
of fewer services.
Severity Warning

No
No
Probable Cause During energy-saving period, partial boards are powered down because
of fewer services.
Handling Suggestion This requires no special handling. The powered-down boards will
be powered on automatically when energy-saving period finishes or
services increase.
3.175 198092401 E1 link self-loop

Detailed Information E1 link self-loop is detected.
Severity Major

2. Service Impact:
Self-loop forms at the E1 physical interface of the board, which affects
communication.
Probable Cause E1 link self-loop is detected.
Handling Suggestion Check link connection.
3.176 198092409 GNSS antenna feeder alarm

Detailed Information This alarm is reported when GNSS antenna feeder is faulty.
Severity Major

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

Probable Cause GNSS antenna feeder fault.
Handling Suggestion Check antenna feeder fault

(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.
Detailed Information This alarm is reported when the built-in-type GNSS receiver has a fault
or is unavailable.
Severity Critical

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 GNSS receiver is broken.
Handling Suggestion Check the faulty GNSS antenna

(1) Reset the board.
3.178 198092416 The built-in-type GNSS antenna has a

feeder cable alarm
Detailed Information This alarm is reported when the built-in-type GNSS antenna has a
faulty feeder cable.
Severity Major

Work normally
Probable Cause GNSS antenna feeder is faulty.
3-93

Handling Suggestion Check the faulty GNSS antenna feeder.

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

receiver has an alarm.
Detailed Information This alarm is reported when one of the following situations happens in
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 Minor

Work normally
Probable Cause 1. RGPS receiver has a power cut problem.

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 1. Check whether RGPS has no electricity supply. If yes, handle the
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.
Detailed Information This alarm is reported when the external-panel-type GNSS receiver
has a faulty feeder cable.
Severity Major
3-94


Work normally
Probable Cause The external-panel-type GNSS receiver has a faulty feeder cable.
Handling Suggestion Check the faulty antenna feeder.


receiver has an alarm, indicating its foreground
working mode is inconsistent with background.
Detailed Information This alarm is reported when CC has detected that the receiver mode
configured at background is different from that directly read from
foreground hardware.
Severity Minor
System Impact None
Probable Cause 1. The receiver mode is wrongly configured.

2. The receiver mode configured at background is inconsistent with
foreground.
Handling Suggestion 1. If it is front-panel wiring, check whether the link between USR and
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.
Detailed Information This alarm is reported when one of the following situations happens in
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

Severity Minor

Work normally
Probable Cause 1. RGPS receiver has a power cut problem.

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 1. Check whether RGPS has no electricity supply. If yes, handle the
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.
Detailed Information This alarm is reported when the external-backplane-type GNSS
receiver has a faulty feeder cable.
Severity Major

Work normally
Probable Cause The external-backplane-type GNSS antenna has a faulty feeder cable.
Handling Suggestion Check the faulty antenna feeder.

3-96


receiver has an alarm, indicating its foreground
working mode is inconsistent with background.
Detailed Information This alarm is reported when CC has detected that the receiver mode
configured at background is different from that directly read from
foreground hardware.
Severity Minor
System Impact None
Probable Cause 1. The receiver mode is wrongly configured.

2. The receiver mode configured at background is inconsistent with
foreground.
Handling Suggestion 1. If it is front-panel wiring, check whether the link between USR and
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 198092426 GNSS cascading clock has an alarm

Detailed Information This alarm is reported when there is a link or satellite searching problem
in GNSS cascading clock mode.
Severity Major

Work normally
Probable Cause 1. GNSS information fails to be transferred from previous-level board to

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 1. Check whether the inter-board cable is in normal state.

2. Check the antenna status of previous-level board. Check whether
it can search satellites properly.
3. Reset the board.
3-97

3.186 198092433 RRU network interrupted alarm

Detailed Information The alarm will be reported when the receiving optical port of RRU in
network has no optical signal received.
Severity Major
System Impact The optical link in RRU network is broken (the receiving optical port of
RRU has no optical signal received).
Probable Cause The fiber is not well connected to optical port of RRU or optical module
is broken.

is clean.
3.187 198092434 Clock line abnormal connection in

stack mode
Detailed Information This alarm is reported when clock line is abnormal in stack mode.
Severity Major

Work normally
Inter-frame services between master and slave frame are affected.
Probable Cause 1. Stack clock line is not properly inserted.

2. Stack clock line is broken.
Handling Suggestion 1. Remove and insert the stack clock line again.
2. Replace the stack clock line.
3.188 198092435 Inter-frame Ethernet link broken in

stack mode
Detailed Information This alarm is reported when inter-frame Ethernet Eth1 link is broken
in stack mode.
Severity Major
3-98


Work normally
Services of slave frame are interrupted.
Probable Cause 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.
Handling Suggestion 1. Remove and insert ETH1 line again.

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
Detailed Information This alarm is reported when it fails to synchronize slave clock with
master clock in stack mode.
Severity Major

Work normally
Inter-frame services between master and slave frame are affected.
Probable Cause 1. Stack clock line is faulty.

2. CC board on slave frame has a hardware fault.
Handling Suggestion 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

Detailed Information This alarm is reported when RU channel cannot bear services during
calibration or other manual operations.
Severity Major

Work normally.
The corresponding channel is unavailable.
3-99

Probable Cause RU cannot provide services properly during the period of some manual
operations (e.g. TOC measurement, OP training, calibration, radio
interference scanning).
Handling Suggestion Wait until the manual operations finish.
3.191 198092438 Device in low temperature

Detailed Information This alarm is reported when the system detects that a device stays in
very low temperature, lower than configured lower limit.
Severity Major

Work normally
A board or the system may work improperly.
Probable Cause 1. Environmental temperature is out of normal range.

2. SA board is faulty.
Handling Suggestion 1. Check whether environmental temperature is too low (lower than
-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.
Detailed Information Uplink transport port of a base station operates in a different mode
from configured one.
Severity Minor

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

Probable Cause 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
time.
Handling Suggestion 1. Check the configuration of peer end.

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
Detailed Information AC phase voltage is unbalanced.
Severity Major
System Impact The output of 3-phase rectifier is affected, but there is no any influence
on single-phase rectifier.
Probable Cause 1.AC power network has a problem.

2. The monitoring unit is broken, which leads to false detection.
Handling Suggestion 1. Check the value of AC input voltage.

3.194 198092448 High AC phase current of built-in

power
Detailed Information AC phase current is high.
Severity Major
System Impact 1.If AC phase current stays high for a long time, AC input current must
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 1.AC input phase current is larger than the threshold, which is used to
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

Handling Suggestion 1.Check AC phase current threshold of the monitoring unit.

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
Detailed Information AC phase is missing.
Severity Major
System Impact 1.Rectifier may not work properly.

2.It affects power supply to a base station.
Probable Cause 1.AC input cable is fell off.

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 1.Check whether AC input cable is correctly connected.

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
Detailed Information The battery's voltage is lower than power-cut setting value so that all
power load has to be powered down.
Severity Critical
System Impact It affects power supply to a base station.
3-102

Probable Cause 1.System temperature is lower than low-temperature cut-off threshold.

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 1.Check battery's temperature.

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
Detailed Information LLVD1 extended branch is broken.
Severity Major
System Impact The circuit breaker in the LLVD1 extended branch is opened so that the
connected base station is powered down.
3-103

Probable Cause 1.When the battery's voltage reduces to LLD1 voltage threshold, the
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 1.Check whether the battery's voltage is lower than LLVD1 voltage.
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
Detailed Information LLVD1 branch is broken.
Severity Major
System Impact The circuit breaker in the LLVD1 non-extended branch is opened so
that the connected base station is powered down.
unreasonable.
3-104

unit is reasonable.
"connected".
3.199 198092453 Broken LLVD2 branch E of built-in

power
Detailed Information LLVD2 branch is broken.
Severity Major
System Impact The circuit breaker in the LLVD2 extended branch is opened so that the
connected base station is powered down.
unreasonable.
unit is reasonable.
"connected".
3-105

3.200 198092454 Broken battery cut-off branch E of

built-in power
Detailed Information Battery's cut-off extended branch is broken.
Severity Major
System Impact 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.

threshold.
threshold.
broken.

threshold.
3.201 198092455 Broken battery cut-off branch of

built-in power
Detailed Information Battery's cut-off branch is broken.
Severity Major
3-106

System Impact 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
supplied with power.

threshold.
threshold.
broken.

threshold.
3.202 198092456 Abnormal battery current of built-in

power
Detailed Information Battery's current is abnormal.
Severity Minor
System Impact The battery may be over-charged or under-charged. This will affect
battery's performance and base station may not work properly.
Probable Cause 1.The monitoring unit has a problem.

2.The configured parameter for the battery's current is wrong.
Handling Suggestion Replace the monitoring unit.
3-107

3.203 198092457 Abnormal CAN bus of built-in power

Detailed Information CAN bus is abnormal.
Severity Minor
System Impact The communication with the rectifier is interrupted. This will affect
battery's performance and management function.
Probable Cause CAN bus is interrupted.
Handling Suggestion Check whether CAN bus cable is fell off.
3.204 198092458 Abnormal battery of built-in power

Detailed Information Abnormal status is detected for the battery.
Severity Critical
System Impact It doesn't affect power supply to a base station. But energy-saving
control will be affected.
Probable Cause 1. The battery discharging ability is not strong.

2. The battery is not well charged.
Handling Suggestion Replace the battery.
3.205 198092459 Abnormal input dry contact of built-in

power
Detailed Information The input dry contact gives an alarm.
Severity Critical
System Impact It doesn't affect power supply to a base station. But the dry contact
connected device may not report an alarm properly.
Probable Cause 1.The monitoring unit is broken.

2.The input detection hardware has a problem.
Handling Suggestion 1. Replace the monitoring unit.

2. Check SCDB (hardware circuit board).
3-108

3.206 198092460 High-temperature cut-off of built-in

power
Detailed Information Environmental temperature is higher than high-temperature cut-off
threshold so that the battery is removed.
Severity Critical
System Impact It affects power supply to a base station.
Probable Cause 1.System temperature is higher than high-temperature cut-off threshold.

broken.

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
Detailed Information This alarm is reported when frame synchronization is unsuccessful
between BBU subracks.
Severity Minor

Inter-subrack service may not work properly.
Inter-subrack IQ data is abnormally accumulated and inter-subrack
Probable Cause The clock phase provided by CC board in real application environment
cannot meet the requirement for sharing inter-subrack IQ data.
Handling Suggestion 1. In stack configuration, check whether the clock cable is tightly
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

3.208 198092550 User-defined dry contact alarm 1

Detailed Information When there is a fault on the User-defined dry contact, the alarm is
reported.
Severity Minor

2. Service Impact:
No impact on service
Probable Cause There is a fault on the User-defined dry contact.
Handling Suggestion Perform different process methods according to the type of the exterior
devices.

reported.
Severity Minor

2. Service Impact:
devices.

reported.
Severity Minor

2. Service Impact:
3-110

devices.

reported.
Severity Minor

2. Service Impact:
devices.

reported.
Severity Minor

2. Service Impact:
devices.

reported.
Severity Minor
3-111


2. Service Impact:
devices.

reported.
Severity Minor

2. Service Impact:
devices.

reported.
Severity Minor

2. Service Impact:
devices.
3-112


reported.
Severity Minor

2. Service Impact:
devices.

reported.
Severity Minor

2. Service Impact:
devices.

reported.
Severity Minor

2. Service Impact:
3-113

devices.

reported.
Severity Minor

2. Service Impact:
devices.

reported.
Severity Minor

2. Service Impact:
devices.

reported.
Severity Minor
3-114


2. Service Impact:
devices.

reported.
Severity Minor

2. Service Impact:
devices.

reported.
Severity Minor

2. Service Impact:
devices.
3-115


reported.
Severity Minor

2. Service Impact:
devices.

reported.
Severity Minor

2. Service Impact:
devices.

reported.
Severity Minor

2. Service Impact:
3-116

devices.

reported.
Severity Minor

2. Service Impact:
devices.

reported.
Severity Major

2. Service Impact:
devices.

reported.
Severity Major
3-117


2. Service Impact:
devices.

reported.
Severity Major

2. Service Impact:
devices.

reported.
Severity Major

2. Service Impact:
devices.
3-118


reported.
Severity Major

2. Service Impact:
devices.

reported.
Severity Major

2. Service Impact:
devices.

reported.
Severity Major

2. Service Impact:
3-119

devices.

reported.
Severity Major

2. Service Impact:
devices.

reported.
Severity Major

2. Service Impact:
devices.

reported.
Severity Major
3-120


2. Service Impact:
devices.

reported.
Severity Major

2. Service Impact:
devices.

reported.
Severity Major

2. Service Impact:
devices.
3-121


reported.
Severity Major

2. Service Impact:
devices.

reported.
Severity Major

2. Service Impact:
devices.

reported.
Severity Major

2. Service Impact:
3-122

devices.

reported.
Severity Major

2. Service Impact:
devices.

reported.
Severity Major

2. Service Impact:
devices.

reported.
Severity Major
3-123


2. Service Impact:
devices.

reported.
Severity Major

2. Service Impact:
devices.

reported.
Severity Major

2. Service Impact:
devices.
3-124


reported.
Severity Major

2. Service Impact:
devices.

reported.
Severity Major

2. Service Impact:
devices.

reported.
Severity Major

2. Service Impact:
3-125

devices.

reported.
Severity Major

2. Service Impact:
devices.

reported.
Severity Major

2. Service Impact:
devices.

reported.
Severity Critical
3-126


2. Service Impact:
devices.

reported.
Severity Critical

2. Service Impact:
devices.

reported.
Severity Critical

2. Service Impact:
devices.
3-127


reported.
Severity Critical

2. Service Impact:
devices.

reported.
Severity Critical

2. Service Impact:
devices.
3.258 198094800 SRIO Communication Abnormal

Detailed Information Serial Rapid IO switch works improperly in the board.
Severity Minor
System Impact 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.
Probable Cause 1.Software fault.

2.Hardware fault.
Handling Suggestion 1.Reset the faulty BPL board.

2.Replace the faulty BPL board.
3-128

3.259 198094828 The board is unavailable

Detailed Information CC board can't receive keep-alive message from the peripheral BPL
board.
Severity Major
System Impact Service running on this core maybe interrupted,the board process
ability descends.
Probable Cause 1.Software fault.

2.Hardware fault.
Handling Suggestion 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

Detailed Information eBBU synchronization state is under unhold status and can not lock
any configured clock source.
Severity Critical
System Impact Affect air interface syncronization state,cell blocked,can not establish
service cell.
Probable Cause The PLL is under holdover, free oscillation or auxiliary phase control
state over a period of time defined by alarm threshold.
Handling Suggestion 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

Detailed Information The optical port is configured, but the fiber length or rate mismatch.
Severity Critical
System Impact The optical port cannot enter normal work state.
Probable Cause Optical module does not match.
Handling Suggestion Re-configurate optical port or replace optical module in practice.
3-129

3.262 198096551 RRU unconfigured

Detailed Information RRU connected to the BBU unconfigured.
Severity Major
System Impact The RRU cannot work normally.
Probable Cause There is a unconfigured RRU along with this BBU port, or the last
RRU's downlink port is connected to BBU.
Handling Suggestion 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
Detailed Information Difference of fiber time delay of two RRUs in same sector exceeded
system limit.
Severity Major
System Impact In downlink, the measurement of optical fibre's delay may be

failure,thereby the RRU can not enter normal work state.
Probable Cause Difference of fiber time delay of two RRU in one sector exceeded
system limit(usually 32 chips).
Handling Suggestion 1. Reboot all RRUs in this sector to recalculate the fiber time-delay.
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
Detailed Information RRU Type is not consistent with configuration type.
Severity Critical
System Impact The RRU can not enter normal work state.
Probable Cause RRU Type is not consistent with configurated type.
Handling Suggestion Check the real and configurated type of RRU, be sure that they are
same.
3-130

3.265 198096554 Failure of optical decoding in BBU

Detailed Information Failure of optical decoding in BBU.
Severity Major
System Impact Those RRUs attached to BBU via this optical port maybe not provide
service.
Probable Cause Serdes data signal is lost.
Handling Suggestion If normal, reset board, else replace it.
3.266 198096555 Failure of optical decoding in RRU

Detailed Information Failure of optical decoding in RRU.
Severity Major
System Impact The RRU containing the optical port or the next RRU connected via the
optical port may be lost to BBU.
Probable Cause Serdes data signal is lost.
Handling Suggestion 1. Check whether connection between RRU and fiber is normal, or
transmitting and receiving is normal.
2. Reset RRU.
3. Replace board.
3.267 198096556 IQ link input loses lock

Detailed Information IQ link input loses lock.
Severity Major
System Impact The quality of service tend to decrease.
Probable Cause IQ link input lose lock.
Handling Suggestion 1. Check whether the Baseband Board and IQ(SBMP of B322) board is
normal.
2. if it is normal, reset board.
3. Replace board.
3-131

3.268 198096558 Downlink baseband power abnormal

Detailed Information Baseband IQ data power from BBU exceeded the rated power or lower
than the least power.
Severity Major
System Impact The RRU will not establish the frequecy successfully.
Probable Cause The baseband IQ data power that BBU sends to RRU extended or
lower than rated power.
Handling Suggestion 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 is too high or too low
Detailed Information RRU DwPCH power from BBU exceeded the rated power or lower
than the least power.
Severity Major
System Impact The RRU will not establish the frequecy successfully.
Probable Cause The DwPCH power that BBU sends to RRU extended or lower than
rated power.
Handling Suggestion 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

fault.
Detailed Information RRU adjust channel or adjust cable fault.
Severity Major
System Impact It causes the failure of the antenna adjustment of the RRU.
Probable Cause 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).
Handling Suggestion 1. Check whether adjust cable link correctly.

2. Check whether the cable is good.
3. replace the RRU.
3-132

3.271 198096560 Master and slave monitor link alarm

Detailed Information Master and slave monitor link alarm.
Severity Major
System Impact The primary RRU and the secondary RRU can not work in concordance,
only one of them can be used.
Probable Cause 1. Master/slave control failure;

2. 485 master/slave cable pins error.
Handling Suggestion 1.Switch master/standby clock cable.

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
Detailed Information The amplitude or phase among TX channels or RX channels is different.
Severity Major
System Impact The radio signal may be affected.
Probable Cause When difference is too much between channels in antenna adjusting,
Antenna adjusting ends. Maybe problem exist in other place.
Handling Suggestion 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

Detailed Information RRU self check failed when power on.
Severity Major
System Impact The RRU can not work normally.
Probable Cause 1. Channel DAC/DUC/DDC initialization failure;

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 Replace RRU.
3-133

3.274 198096563 RRU device alarm

Detailed Information RRU device alarm.
Severity Major
System Impact It affects the antenna adjustment of the RRU, and also has affect to
transmit or receive RF signal. Consequently affect telecom quality.
Probable Cause Usually offline parameter is abnormal; sometimes maybe RRU Board is
not plug in.
Handling Suggestion 1. Software start to use standard offline parameter.

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
Detailed Information Configuration parameter of RRU external device not consistent with
real parameter.
Severity Major
System Impact The device outside the RRU may not work normally.
Probable Cause Configurated type of RRU external device not consistent with real type.
Handling Suggestion 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.

Detailed Information RRU used power module is too hot.
Severity Major
System Impact RRU output power is adjusted downwards.
Probable Cause RRU used power module is too hot.
Handling Suggestion If the power module continuously stays at high temperature, for
example, for more than five days, please replace the RRU.
3-134

3.277 198096569 RRU offline parameter check failure

Detailed Information Read and check the RRU saved offline parameter, but the check
process fails.
Severity Major
System Impact 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.
Probable Cause Read and check the RRU saved offline parameter, but the check
process fails.
Handling Suggestion 1. Software enables standard offline parameter.

2. Check whether the offline parameter saved in EEPROM is correct.
3. Replace the RRU.
3.278 198098431 Abnormal current alarm at NSBT port

Detailed Information 1. An over-current alarm is reported when the current value at NSBT
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 Minor

Work normally
Cell coverage is affected.
Probable Cause 1. The threshold configured at background is inconsistent with typical

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

Handling Suggestion 1. Check the alarming threshold configured at background. Is it wrongly

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
Detailed Information Channel current is larger than the maximum value allowed by
AISG/NSBT power moduel.
Severity Minor

Work normally
Cell coverage is affected.
Probable Cause 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.
Handling Suggestion 1. Check whether the configured voltage at AISG/NSBT port is

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

3.280 198098434 Abnormal transmission power at

antenna port
Detailed Information There is a big difference between transmission power at antenna port
and digital power.
Severity Minor

Work normally
Services and cell coverage are affected.
Probable Cause The transmission power at antenna port has big difference from digital
power, bigger than alarm threshold.
Handling Suggestion 1. Check whether calibration is successful.

2. Check whether PA works normally.
3. Check whether the physical link between PA and duplexer is normal.
3.281 198098435 Closed-loop power control adjustment

exceeding normal range
Detailed Information The closed-loop power control process tries to adjust the power at
antenna port, but the adjusted value exceeds a normal range.
Severity Minor

Work normally
RRU transmission power becomes inaccurate.
Probable Cause The closed-loop power control process tries to adjust the power at
antenna port, but the adjusted value exceeds a normal range.
Handling Suggestion 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

Detailed Information Failure in configuring power level.
Severity Minor
3-137


Work normally
RRU transmission power becomes inaccurate.
Probable Cause Failure in configuring power level
Handling Suggestion Check whether the static power level configured at background is legal.
3-138

Chapter 4
Environment Alarm
Table of Contents
198092429 Board powered-down alarm because of high temperature........................4-2
198092462 Differential pressure alarm .......................................................................4-2
198092037 MP voltage abnormal ...............................................................................4-3
198092038 PP voltage abnormal................................................................................4-3
198092039 Over current of MP ..................................................................................4-3
198092040 Over current of PP ...................................................................................4-4
198092041 Fan failure ...............................................................................................4-4
198092042 Abnormal temperature at air intake ..........................................................4-5
198092043 Abnormal temperature at air outlet ...........................................................4-6
198092044 Door control alarm ..................................................................................4-6
198092045 Flooding alarm .........................................................................................4-7
198092046 Smog alarm .............................................................................................4-7
198092047 Infrared alarm .........................................................................................4-8
198092048 Air conditioner fault ..................................................................................4-8
198092053 Voltage of DC input is abnormal...............................................................4-9
198092069 FCE-fan failure ........................................................................................4-9
198092105 Embedded power Environment is under-temperature.............................4-10
198092106 Embedded power Environment is over-temperature...............................4-10
198092107 Embedded power Environment temperature is invalid............................4-11
198092108 Embedded power Environment is under-Humidity. .................................4-12
198092109 Embedded power Environment is over-Humidity. ...................................4-12
198092110 Embedded power Environment humidity is invalid. .................................4-13
198092111 Embedded power Smoke detected.........................................................4-13
198092112 Embedded power Flood detected...........................................................4-13
198092113 Embedded power Door Magnet Alarm....................................................4-14
198092114 Embedded power Gate Embedded power Safety Alarm ........................4-14
198092115 Glass Broken Alarm ...............................................................................4-15
198092118 Embedded power Env-unit communication interruption ..........................4-15
198092119 Embedded power Heat Exchanger Fault ................................................4-16
198092213 Board temperature abnormal alarm........................................................4-16
198092307 Slight-high temperature of board............................................................4-16
198092308 Over-high temperature of board .............................................................4-17
198092371 CCM Remote MEP Error........................................................................4-17
198092372 CCM Message Error ..............................................................................4-17
198092373 CCM Xconnect Error..............................................................................4-18
4-1

4.1 198092429 Board powered-down alarm because

of high temperature
Detailed Information This alarm is reported when the board temperature exceeds upper limit
and cannot work properly.
Severity Major

The board is faulty
The board is powered down. All services borne on the board are
interrupted.
Probable Cause 1. The board surface encounters high temperature, exceeding upper
limit.
2. The board internal temperature is over high.
Handling Suggestion 1. Check whether the dustproof net is blocked.

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

Detailed Information This alarm is reported when the top cover of a cabinet is not closed.
Severity Major

Work normally
Cables may be stolen and water may enter the cabinet. Both may
cause reduced service performance, even service interruption.
Probable Cause 1. View the relevant network management interface and finds the dry
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 1. Check whether the top cover is closed. If not, close it.
2. Replace the cable that is connected to the differential pressure
sensor.
4-2

Chapter 4 Environment Alarm
4.3 198092037 MP voltage abnormal

Detailed Information MP voltage.
Severity Minor
System Impact Affect the power supply of the boards that they cannot bear any service.
Probable Cause 1. When the MP voltage reported by PM/PSA board exceeds the upper
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 Replace the PM/PSA board.
4.4 198092038 PP voltage abnormal

Detailed Information PP voltage.
Severity Major
System Impact Affect the power supply of the boards that they cannot bear any service.
Probable Cause 1. When the PP voltage reported by PM/PSA board exceeds the upper
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 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.
2. Replace the PM/PSA board.
4.5 198092039 Over current of MP

Detailed Information Over current of MP.
Severity Minor

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

Probable Cause The MP current status of PM/PSA board's load is checked periodically.
If over-current is detected, this alarm is reported.
Handling Suggestion 1. Remove and insert the corresponding board.

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

Detailed Information Over current of PP.
Severity Minor

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 The PP current status of PM/PSA board's load is checked periodically.
If over-current is detected, this alarm is reported.
Handling Suggestion 1. Remove and insert the corresponding board.

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

Detailed Information Fan failure.
Severity Minor

2. Service Impact:
The equipment temperature may become over high which may cause
the board of the system to work improperly.
Probable Cause 1. Fan failure.

2. The fault with the environment monitoring unit.
Handling Suggestion 1. Check whether the fan power supply link is normal.
2. Replace the fan.
4-4

4.8 198092042 Abnormal temperature at air intake

Detailed Information The temperature at air intake is abnormal.
Severity Minor

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 In the case of high temperature at air intake:

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.
2. The heat exchanger is faulty.
Handling Suggestion In the case of high temperature at air intake:

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

4.9 198092043 Abnormal temperature at air outlet

Detailed Information The temperature at air outlet is abnormal.
Severity Minor

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 In the case of high temperature at air outlet:

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 In the case of high temperature at air intake:

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

Detailed Information This alarm is reported when a door control sensor is used but the
door is not closed.
Severity Major

Work normally
Cables are probably stolen or water may enter the device. These may
cause reduced service performance or even service interruption.
2. The door is not closed.
4-6

Handling Suggestion 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.
4.11 198092045 Flooding alarm

Detailed Information This alarm is reported when the flooding sensor connected at a dry
contact detects a flooding situation.
Severity Minor

Work normally
The board or system may not work properly. As a result, services borne
on the board are interrupted.
of status: normally closed, normally open..
2. The base station is flooded.
Handling Suggestion 1. Check whether the base station is flooded. If yes, power off the
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

Detailed Information This alarm is reported when the smog sensor connected at a dry
contact detects a smog situation.
Severity Minor

Work normally
No impact
4-7

2. The base station detects smog.
Handling Suggestion 1. Check whether there is smog inside the base station. If yes, power
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 Minor

Work normally
No impact.
2. Someone enters the equipment room.
Handling Suggestion 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

Severity Minor
4-8


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.
2. The air conditioner is faulty.
Handling Suggestion 1. Check whether the cable connected to the air conditioner is good.
2. Replace the air conditioner.
4.15 198092053 Voltage of DC input is abnormal.

Detailed Information Voltage of DC input is abnormal.
Severity Major

2. Service Impact:
The lightning protection is invalid.
Probable Cause 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.
Handling Suggestion Over-voltage: Check whether the input voltage of DC supply system is
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

Detailed Information FCE-fan failure
4-9

Severity Minor

2. Service Impact:
The equipment temperature may become over high which may cause
the board of the system to work improperly.
Probable Cause 1. Fan failure.

2. The fault with the environment monitoring unit.
Handling Suggestion 1. Check whether the fan power supply link is normal.
2. Replace the fan.
4.17 198092105 Embedded power Environment is

under-temperature.
Detailed Information The environment temperature is lower than environment
under-temperature that is set.
Severity Minor
System Impact The battery's capacity is influenced.
Probable Cause 1. The environment temperature is lower than the threshold value for
alarm.
2. The temperature sensor is damaged.
Handling Suggestion 1. Check the temperature in the equipment room, and improve the
equipment room condition.
2. Appropriately adjust the threshold value for alarm.

over-temperature.
Detailed Information The environment temperature is higher than environment
over-temperature that is set.
Severity Minor
4-10

System Impact 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.
Probable Cause 1. The environment temperature is higher than the threshold value
for alarm.
3. The AC transducer or the monitoring unit is damaged.
4.19 198092107 Embedded power Environment

temperature is invalid.
Detailed Information The environment temperature is an invalid value.
Severity Minor
System Impact The equipment environment temperature detection is influenced.
Probable Cause 1. The environment temperature exceeds the normal range allowed
in the detection.
3. The temperature sensor is not connected.
2. Check whether the temperature sensor is connected reliably.
4-11


under-Humidity.
Detailed Information The environment humidity is lower than Environment under-humidity
that is set.
Severity Minor
System Impact The antistatic capability of the power supply is influenced, which might
cause equipment damage.
Probable Cause 1. The environment humidity is lower than the threshold value for alarm.
2. The humidity sensor is damaged.
Handling Suggestion 1. Check the humidity in the equipment room, and improve the
3. Replace the humidity sensor.

over-Humidity.
Detailed Information The environment humidity is higher than Environment over-humidity
that is set.
Severity Minor
System Impact The anti-insulation and crush-resistance capability of the power supply
is influenced, and the board tends to be affected by damp and corrosion.
Probable Cause 1. The environment humidity is higher than the threshold value for
alarm.
4-12

4.22 198092110 Embedded power Environment

humidity is invalid.
Detailed Information The environment humidity is an invalid value.
Severity Minor
System Impact The equipment environment humidity detection is influenced.
Probable Cause 1. The environment humidity exceeds the normal range allowed in
the detection.
3. The humidity sensor is not connected.
2. Check whether the humidity sensor is connected reliably.
4.23 198092111 Embedded power Smoke detected

Detailed Information The sensor detects the smoke.
Severity Critical
System Impact The system security is influenced, and the system might be on fire.
Probable Cause 1. The smoke alarm signal is detected.

2. The smoke sensor is damaged.
Handling Suggestion 1. Check whether there is any smoke. If there is, then disconnect the
AC power supply input and locate the fault. After the fault is removed,
power on again, and restart the sensor.
2. Replace the smoke sensor.
4.24 198092112 Embedded power Flood detected

Detailed Information The sensor detects the water.
Severity Minor
System Impact The system security is influenced.
4-13

Probable Cause 1. The flooding alarm signal is detected.

2. The sensor is damaged.
Handling Suggestion 1. Improve the equipment room condition.

2. Replace the sensor.
4.25 198092113 Embedded power Door Magnet Alarm

Detailed Information The sensor detects that the equipment room's door is opened.
Severity Minor
System Impact The burglarproof security of the equipment is influenced.
Probable Cause 1. The equipment room's door is opened.

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 1. Check whether the door is closed.

2. Check whether the detecting cable is connected correctly.
3. Check whether the door status switch is installed correctly, and
whether the switch can be attracted normally after the door is closed.
4. Replace the door-status-switch sensor.
4.26 198092114 Embedded power Gate Embedded

power Safety Alarm
Detailed Information The sensor detects that the access control of the cabinet is not closed.
Severity Major
Probable Cause 1. The cabinet's door is opened.

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

Handling Suggestion 1. Check whether the door is closed.

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

Detailed Information The sensor detects that the glass is broken.
Severity Minor
Probable Cause 1. The relevant alarm signal is detected.

Handling Suggestion 1. Check whether the equipment room's glass is broken.

2. Replace the sensor.
4.28 198092118 Embedded power Env-unit

communication interruption
Detailed Information The communication of the system environment monitoring unit is
interrupted.
Severity Major
System Impact The normal detection of environment parameters is influenced.
Probable Cause 1. The power supply is not configured with the environment monitoring
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 1. Check whether the monitoring unit's setting is in accordance with the
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

4.29 198092119 Embedded power Heat Exchanger Fault

Detailed Information The heat exchanger is damaged or the temperature is beyond the
allowed range.
Severity Major
System Impact The normal heat dissipation of the power supply is influenced.
Probable Cause 1. The heat exchanger is faulty.

Handling Suggestion 1. Check whether the monitoring unit's socket is of bad contact or
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

Detailed Information The board temperature exceeds its alarming threshold.
Severity Minor
System Impact If board temperature is over high or over low, the board may not work
properly.
Probable Cause The board temperature is over high or over low, exceeds its alarming
thresholds.
Handling Suggestion 1. Check whether the fan works properly.

2. Check whether the dustproof net is blocked.
4.31 198092307 Slight-high temperature of board

Detailed Information The board temperature exceeds slight-high temperature threshold.
Severity Warning

Work normally
Services borne on the board are not interrupted.
4-16

Probable Cause 1. Environmental temperature exceeds a threshold.

2. The fan is faulty.
3. The temperature sensor on the board is faulty.

4.32 198092308 Over-high temperature of board

Detailed Information The board temperature exceeds over-high temperature threshold.
Severity Major
System Impact The board may not work properly. As a result, services borne on the
board are interrupted.
Probable Cause 1. Environmental temperature exceeds a threshold.

2. The fan is faulty.
3. The temperature sensor on the board is faulty.

4.33 198092371 CCM Remote MEP Error

Detailed Information Remote MEP detected by CCM is broke.
Severity Major
System Impact It will affect stability of ethernet link.
Probable Cause Remote MEP detected by CCM is broke.
Handling Suggestion Please check ethernet transmission link and configuration of

transmission device.
4.34 198092372 CCM Message Error

Detailed Information The message send by CCM has error.
Severity Major
4-17

Probable Cause The message send by CCM has error.

4.35 198092373 CCM Xconnect Error

Detailed Information CCM message has conflict with configuration.
Severity Major
Probable Cause CCM message has conflict with configuration.

4-18

Chapter 5
Processing Alarm
Table of Contents
198094815 Performance Measurement Rule Library Unavailable...............................5-2
198096567 BOOT software upgrade failure................................................................5-2
198092010 Board communication link is interrupted...................................................5-2
198092014 SNTP time adjustment failure alarm.........................................................5-3
198092016 Clock reference source configuration error...............................................5-3
198092017 Failure in loading software .......................................................................5-4
198092019 Failure in synchronizing the version of master board with slave board. ....5-4
198092022 Running software version doesn't exist. ..................................................5-5
198092024 DOM is lack of space ...............................................................................5-5
198092025 Failure in synchronizing software version of master control board............5-6
198092027 Failure in repairing specification package.................................................5-6
198092029 Wrong board insertion..............................................................................5-7
198092030 Abnormal software in specification package.............................................5-7
198092060 LMT login alarm ......................................................................................5-8
198092066 Failure in uncompressing LMT software...................................................5-8
198092070 Board software fault .................................................................................5-9
198092309 Line clock has the fault. ...........................................................................5-9
198092310 SyncE clock has the fault. ......................................................................5-10
198092347 The fan control policy is not existed ......................................................5-11
198092348 Board initialization..................................................................................5-11
198092360 Product process is abnormal..................................................................5-12
198092366 Configuration Fail...................................................................................5-12
198092390 CPU over loading highly alarm...............................................................5-12
198092391 CPU over loading...................................................................................5-13
198092395 Running software rollback......................................................................5-13
198092396 Board hot patch fault..............................................................................5-13
198092397 Failure in finding this board-related software ID ....................................5-14
198092398 MMC running software version doesn't exist. .........................................5-15
198092403 Carrier frequency configuration error......................................................5-15
198092404 Center frequency configuration error......................................................5-16
198092405 Work pattern configuration error.............................................................5-16
198092406 IQ parameter configuration error ............................................................5-16
198092407 Delay parameter configuration error.......................................................5-17
198092408 Carrier power configuration error ...........................................................5-17
198092412 1PPS+TOD source fault ........................................................................5-18
198092413 1PPS+TOD standby source fault ...........................................................5-18
198092414 SyncE clock unavailable (SyncE+1588) .................................................5-19
5-1

198092430 Optical module rate does not match.......................................................5-19

198092432 Optical modules have mismatched transmission distance ......................5-20
198094811 Cell Setup Failure ..................................................................................5-20
198094812 Cell Reconfiguration Failure...................................................................5-21
198094813 Parament Configuration Error ................................................................5-21
5.1 198094815 Performance Measurement Rule Library

Unavailable
Detailed Information Cause new loading rule library unusable and subsequent granularity
data statistics abnormal.
Severity Major
System Impact Cause new loading rule library unusable and subsequent granularity
data statistics abnormal.
Probable Cause 1.Database access failure.

2.Rule library configuration restrictions check failure.
3.Allocate UB failure.
Handling Suggestion 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

Detailed Information RRU boot version upgrade failure
Severity Minor
System Impact Boot cannot be upgraded to new version. After rollback, RRU can run
normally.
Probable Cause During RRU boot upgrading process, either flash writing or boot
handover fails, which causes boot version to be rolled back.
Handling Suggestion Try to upgrade boot version manually. If it fails again, please replace
RRU.
5.3 198092010 Board communication link is interrupted

Detailed Information 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.
Severity Critical
5-2

Chapter 5 Processing Alarm

II. Service Impact:
The board fails to communicate with the master CC board, leading
to interruption of board services.
Probable Cause 1. The board that has been configured does not exist on the rack.
2. The link between this board and master CC board is faulty.
Handling Suggestion 1. In stack mode, check whether inter-frame network cable connection
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

Detailed Information SNTP server doesn't boot or its link has a fault.
Severity Minor

II. Service Impact:
System time is inaccurate, but service is not affected.
Probable Cause 1. IP address configuration for SNTP time adjustment server is wrong.
2. SNTP server is faulty.
3. Network problem exists.
Handling Suggestion 1. Check whether SNTP Server Address is correct.

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
Detailed Information 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.
Severity Major
5-3


2. Service Impact:
The services borne on the board may have low performance. In serious
situation, the services may be interrupted.
Probable Cause 1. Parameter configuration does not exist.

2. Parameter configuration is wrong.
Handling Suggestion Reset board.
5.6 198092017 Failure in loading software

Detailed Information This alarm is reported when the CPU/DSP/FPGA on a board fails to
load software.
Severity Major

All services borne on the board are interrupted.
Probable Cause 1. The software version saved on the main control board is wrong.
2. This board has a hardware fault.
Handling Suggestion 1. Log in Software Version Management interface and download the
running specification package again.
5.7 198092019 Failure in synchronizing the version of

master board with slave board.
Detailed Information This alarm is reported by the slave board when it fails to synchronize
version files with master board.
Severity Major
5-4


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 The slave board fails to synchronize version files saved in relevant
directory with the master board.
Handling Suggestion 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.

Detailed Information This alarm is reported when the main control board finds that the
running software version doesn't exist.
Severity Major

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 1. Running software is broken.

2. Runing software is missing.
3. The running software has no associated SWID.
Handling Suggestion Log in Software Version Management interface and download correct
version package again.
5.9 198092024 DOM is lack of space

Detailed Information This alarm is reported when DOM has no sufficient space.
Severity Minor
5-5


Work normally
There is no impact on services.
Probable Cause DOM has no sufficient space.
Handling Suggestion 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
Detailed Information This alarm is reported when the master control board fails to
synchronize version files with slave board.
Severity Major

The slave control board resets.
The master/slave changeover function cannot be performed.
Probable Cause 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.
Handling Suggestion 1. Delete all files from the slave control board except for those saved
in BIN directory.
2. Replace the slave board.
5.11 198092027 Failure in repairing specification

package
Detailed Information 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.
Severity Critical
5-6


Work normally
Even though the booting is successful, all prepheral boards cannot
boot, so no services can be borne.
Probable Cause Specification package fails to be repaired.
Handling Suggestion Enter Software Version Management interface to download the

specification package again. After that, activate it.
5.12 198092029 Wrong board insertion

Detailed Information The main control board has detected that the inserted board to
a physical slot is different from that configured in the network
management system.
Severity Major

The board cannot boot properly.
The board cannot work properly. All services borne on it are interrupted.
Probable Cause 1. The board is wrongly configured as shown in the Configuration

Management interface.
2. A wrong board entity is inserted.
Handling Suggestion 1. Enter Configuration Management interface to correct the board

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
Detailed Information During version consistency check, if the version in a specification
package doesn't exist in DOM or is broken, this alarm is reported.
Severity Major
5-7

System Impact 1. If running specification package or its running patch is abnormal, the
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 During version consistency check, if the version in a specification

package doesn't exist in DOM or is broken, this alarm is reported.
Handling Suggestion Enter Software Version Management interface and reload software
specification package.
5.14 198092060 LMT login alarm

Detailed Information The alarm is reported when LMT is logged in
Severity Warning
System Impact None
Probable Cause 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) .
5.15 198092066 Failure in uncompressing LMT

software
Detailed Information 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.
Severity Minor
System Impact None
Probable Cause 1. LMT software is illegal.

2. DOM is lack of space.
Handling Suggestion Check whether the LMT software is created correctly. Then download it
again and activate the specification package.
5-8

5.16 198092070 Board software fault

Detailed Information A faulty board fails to download/load/uninstall software
Severity Major

Work normally
II. Impact on Services:
Even though the booting is successful, all peripheral boards cannot
Probable Cause 1. The board software saved on the main control board uses wrong
version.
2. The board has a hardware fault.
Handling Suggestion 1. Enter the Software Version Management interface to download and
start this running specification package again.
5.17 198092309 Line clock has the fault.

Detailed Information 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.
Severity Minor

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.

2. External reference clock and cable are faulty.
4. Single board is faulty.
5-9

Handling Suggestion 1. Check whether reference source is wrongly configured.

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 198092310 SyncE clock has the fault.

Detailed Information 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.
Severity Minor

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.

2. External reference clock and cable are faulty.
4. SSM is lost.
5. Single board is faulty.
5-10

Handling Suggestion 1. Check whether reference source is wrongly configured.

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

Detailed Information It is failed to find a fan control policy for current SA or FCE board.
Severity Major
System Impact 1. It affects speed auto-adjustment of the corresponding fan.

2. Both base station and the relevant boards have too high temperature.
Probable Cause 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
Handling Suggestion 1. Re-deliver the file about mapping relation between policy and
scenario.
2. Re-deliver the policy file.
5.20 198092348 Board initialization

Detailed Information This alarm is reported when a board reboots and then enters into the
initial state.
Severity Major

The board is initialized.
2. Service Impact:
Board services are interrupted during board initialization.
Probable Cause 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

Handling Suggestion The alarm will be restored after board initialization. No handling is
necessary.
5.21 198092360 Product process is abnormal.

Detailed Information The status of product process is abnormal.
Severity Major
System Impact The product process works abnormally.
Probable Cause The product process is not dispatched in time.
Handling Suggestion Reset product process
5.22 198092366 Configuration Fail

Detailed Information Configuration makes mistakes.
Severity Major
System Impact RRU cannot work normally and affect system service.
Probable Cause configuration makes mistakes.
Handling Suggestion 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

Detailed Information An alarm is given when the system has constantly detected CPU usage
exceeds high alarm threshold.
Severity Major

2. Service Impact:
Board processing capability declines, probably leading to radio link
or service establishment failure.
Probable Cause The system is in traffic peak period and the traffic is heavy.
5-12

Handling Suggestion 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.24 198092391 CPU over loading

Detailed Information An alarm is given when the system has constantly detected CPU usage
exceeds low alarm threshold.
Severity Minor

2. Service Impact:
Board processing capability declines, probably leading to radio link
or service establishment failure.
Probable Cause The system is in traffic peak period and the traffic is heavy.
Handling Suggestion 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

Detailed Information The alarm is reported when the software of main control board rollbacks.
Severity Major

2. Service Impact:
Board services are down.
Probable Cause Error happens when update software.
Handling Suggestion 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

Detailed Information A faulty board fails to download/upload/uninstall hot patch.
Severity Minor
5-13


2. Service Impact:
The board software update fails and the services provided by this board
is completely interrupted.
Probable Cause 1. The board's software version, which is saved on the main control
board, is incorrect.
Handling Suggestion 1. Re-download the hot patch software version on the software
management interface of OMCB.
2. Reset the board.
5.27 198092397 Failure in finding this board-related

software ID
Detailed Information It is failed to find board software ID according to hardware information
set of the faulty board.
Severity Major

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 1. The content of R_SWID table saved on CC board is incomplete.

2. The alarming board has a hardware fault.
Handling Suggestion 1. If the specification package in base station is not in the form of
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

5.28 198092398 MMC running software version doesn't

exist.
Detailed Information This alarm is reported when the main control board finds that MMC
running software version doesn't exist.
Severity Warning

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 1. MMC running software is broken.

2. MMC running software is lost.
3. MMC running software doesn't exist in the specification package
(no associated SWID)
Handling Suggestion Enter the Software Version Management interface to download correct
specification package again.
5.29 198092403 Carrier frequency configuration error

Detailed Information This alarm is reported when Carrier frequency is out of the rated range
of center frequency or duplex range.
Severity Critical
System Impact 1. Board status:

work normally
The faulty frequency are associated to some services. Those services
are interrupted.
Probable Cause The configured carrier frequency is out of the defined range of center
frequency or duplex.
Handling Suggestion The alarm will be recovered automatically when carrier frequency is
configured within the rated range of center frequency and duplex range.
5-15

5.30 198092404 Center frequency configuration error

Detailed Information 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.
Severity Critical
System Impact 1.Board status:

Work normally.
Probable Cause 1. Carrier frequency is not configured in the system.

2. The carrier frequency is wrongly configured.
3. Hardware is faulty.
Handling Suggestion 1. Configure correct carrier frequency

2. Reset the board
5.31 198092405 Work pattern configuration error

work pattern from BBU is wrong.
Severity Critical

Work normally.
Probable Cause 1. Work pattern is not configured in the system.

2. The work pattern is wrongly configured.
Handling Suggestion Configure correct work pattern
5.32 198092406 IQ parameter configuration error

IQ parameter from BBU is wrong.
Severity Critical
5-16


Work normally.
Probable Cause 1. IQ parameter is not configured in the system.

2. The IQ parameter is wrongly configured.
Handling Suggestion Configure correct IQ parameter
5.33 198092407 Delay parameter configuration error

delay parameter from BBU is wrong.
Severity Critical

Work normally.
Probable Cause The delay parameter is wrongly configured.
Handling Suggestion Check delay parameter in BBU
5.34 198092408 Carrier power configuration error

carrier power from BBU is wrong.
Severity Critical
System Impact 1. Board status:

work normally
The faulty frequency are associated to some services. Those services
are interrupted.
Probable Cause 1. Carrier power is not configured in the system.

2. The carrier power is wrongly configured.
Handling Suggestion Configure correct carrier power
5-17

5.35 198092412 1PPS+TOD source fault

Detailed Information 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.
Severity Minor

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 1. Previous-level of clock source is unavailable.

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 1. Replace clock cascading cable.

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

Detailed Information 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.
Severity Minor

Failure in obtaining 1PPS+TOD signals.
Clock synchronization and frame synchronization cannot be
guaranteed. This will affect soft handover.
5-18

Probable Cause 1. Previous-level of clock source is unavailable.

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 1. Replace clock cascading cable.

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)

Detailed Information This alarm is reported when SyncE clock is unavailable in SyncE+1588
mode.
Severity Warning
System Impact If SSM messages are constantly lost for long time, phases may not
be synchronized.
Probable Cause Phase synchronization source is lost.
Handling Suggestion Check SyncE clock reference source.
5.38 198092430 Optical module rate does not match

Detailed Information This alarm is reported when the speed of an optical module is
inconsistent with its configured value.
Severity Major

Work normally
The service performance in the corresponding cell becomes worse. In
serious situation, the services are interrupted.
Probable Cause The actual optical module cannot support the speed configured by
OMC.
5-19

Handling Suggestion Set the speed of optical module to be lower or equal to real optical
module rate. Then check if the alarm disappears.
5.39 198092432 Optical modules have mismatched

transmission distance
Detailed Information This alarm is reported when the length of optical fiber is beyond the
transmission distance of an optical module.
Severity Minor

Work normally
The services borne on the corresponding link may be interrupted.
Probable Cause Optical fiber length is beyond optical module transmission distance
Handling Suggestion Replace the optical module so that it can support longer transmission
distance. After that, check if the alarm disappears.
5.40 198094811 Cell Setup Failure

Detailed Information Failed to setup cell,unable to offer service.
Severity Major
System Impact Unable to setup cell,cause service could not be processed,severely

affect service quality.
Probable Cause 1.The parameters of cell is configured incorrectly.

2.The BaseBand processing unit or RRU or other module timed out for
cell setup.
Handling Suggestion 1.Check if the parameters of cell is configured correctly.(Reference

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

5.41 198094812 Cell Reconfiguration Failure

Detailed Information Fail to reconfigure parameters of the cell.
Severity Major
System Impact Failed to reconfigure cell which leads to services interruption at this
moment and unable to offer services any more.
Probable Cause 1.The parameters of cell is configured incorrectly.

2.The BaseBand processing unit or RRU or other module timed out for
cell reconfiguration.
Handling Suggestion 1.Check if the parameters of cell is configured correctly(Reference

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

Detailed Information The key parameters on board configured failure.
Severity Major
System Impact Will affect the service process and service quality.
Probable Cause 1.The key parameters is configured incorrectly.
Handling Suggestion 1.Check the error description of the alarm, and be sure that the current
value is right(Reference BBU's configuration manual).
5-21

5-22

Chapter 6
QoS Alarm
Table of Contents
198092410 Satellite searching alarm of GNSS receiver .............................................6-1
198092417 The built-in-type GNSS receiver has a satellite searching alarm ..............6-2
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
alarm..........................................................................................................................6-3
198094826 PCI conflict alarm.....................................................................................6-3
198094827 PCI confusion alarm.................................................................................6-3
198092350 RRU pre-download is failed. ....................................................................6-4
198092368 Ethernet remote fault alarm(RDI) .............................................................6-4
198092370 AIS alarm.................................................................................................6-4
198092380 EFM Link is broken. .................................................................................6-5
6.1 198092410 Satellite searching alarm of GNSS

receiver
Detailed Information This alarm is reported when GNSS receiver fails to search satellites or
the number of searched satellites doesn't reach minimum requirement.
Severity Minor

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 GNSS receiver fails to search satellites or the number of searched
satellites doesn't reach minimum requirement.
Handling Suggestion Check antenna feeder fault

(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

6.2 198092417 The built-in-type GNSS receiver has a

satellite searching alarm
Detailed Information 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.
Severity Minor

Work normally
Probable Cause GNSS receiver fails to search satellites or the number of searched
Handling Suggestion Check the faulty of GNSS antenna feeder.

(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 198092420 The external-panel-type GNSS receiver

has a satellite searching alarm.
Detailed Information 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.
Severity Minor

Work normally
Probable Cause The GNSS receiver fails to search satellites or the number of searched
Handling Suggestion Check the fault of GNSS antenna feeder.

(2) Check whether the direction of GNSS antenna is suitable (e.g.is
6-2

Chapter 6 QoS Alarm

receiver has a satellite searching alarm.
Detailed Information 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.
Severity Minor

Work normally
Probable Cause The GNSS receiver fails to search satellites or the number of searched
Handling Suggestion Check the fault of GNSS antenna feeder.

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

Detailed Information The physical cell ID of neighborhood cell is identical.
Severity Major
System Impact Affect the UE access and handover performance which is under the
cell's coverage.
Probable Cause A pair of neighborhood cells has the identical physical cell ID parameter
while detecting the neighborhood cells' relation configuration.
Handling Suggestion 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

Detailed Information Two neighborhood cells of a certain cell have the identical physical
cell ID configuration.
Severity Major
6-3

System Impact Affect the UE access and handover performance which is under the
cell's coverage.
Probable Cause Two neighborhood cells of a certain cell have identical physical cell ID
parameter while detecting the neighborhood cells' relation configuration.
Handling Suggestion 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.

Detailed Information Version download is successful or changing boot initial file is failed
when pre-download RRU.
Severity Minor
System Impact None
Probable Cause 1. RRU is not working normally.

2. There is no sufficient space in the RRU disk.
3. RRU file system has fault.
Handling Suggestion 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)

Detailed Information Exchange fault information between MEP.
Severity Minor
Probable Cause 1.Error management of single side: receiving MEP detects a RDI fault
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 Please check ethernet transmission link.
6.9 198092370 AIS alarm

Detailed Information ETH-AIS stops alarm when service level detects fault.
6-4

Chapter 6 QoS Alarm
Severity Major
Probable Cause ETH-AIS stops alarm when service level detects fault.
Handling Suggestion Please check ethernet transmission link.
6.10 198092380 EFM Link is broken.

Detailed Information EFM of ethernet detects that link has fault.
Severity Major
System Impact It will cause that ethernet link is broken.
Probable Cause The handshake between base station and the first switchboard is failed.
Handling Suggestion Please check whether the transport link between base station and the
first switchboard is normal.
6-5

6-6

Chapter 7
Notification
Table of Contents
198092054 Slave board powered-on notification ........................................................7-2
198092055 Active-to-standby switchover completed ..................................................7-2
198092056 Standby-to-active switchover completed ..................................................7-2
198092058 Succeed in repairing the specification package........................................7-2
198092059 Alarm Storm.............................................................................................7-3
198092061 Module reset............................................................................................7-3
198092062 Module status error ..................................................................................7-3
198092063 Switchover completed..............................................................................7-3
198092064 Switchover failed......................................................................................7-4
198092065 Board switchover failed............................................................................7-4
198092228 Main board product process power-on .....................................................7-4
198092229 Slave board product process power-on ....................................................7-4
198092271 Local benchmark clock unlocked .............................................................7-5
198092297 Uplink optical/electrical link has high BER ...............................................7-5
198092312 PPP Negotiatory IP Conflict .....................................................................7-6
198092314 IP Conflict ................................................................................................7-6
198092315 Mac Conflict.............................................................................................7-6
198092316 ACOM address conflict ............................................................................7-6
198092329 ATMA device address conflict ..................................................................7-7
198092338 RET device address conflict.....................................................................7-8
198092349 RRU pre-download is successful .............................................................7-8
198092381 EFM Link has error data ..........................................................................7-8
198092392 Product process fails to power on ............................................................7-9
198094823 DPD Running Status Abnormal................................................................7-9
198096557 Uplink IQ link error ...................................................................................7-9
198096566 RRU alarm reset ....................................................................................7-10
198098433 Unavailable alarm of time slot turn-off function .......................................7-10
198092031 Board power-on done notification...........................................................7-10
198092033 Board power-on failed............................................................................7-11
198092034 Bit error has been detected during E1 physical layer in the past 24
hours........................................................................................................................7-11
198092035 E1 link bit error has been detected in the past 24 hours .........................7-11
7-1

7.1 198092054 Slave board powered-on notification

Detailed Information This is a notification message when the slave board is successfully
powered on.
System Impact None
Probable Cause The standby board is powered on.
7.2 198092055 Active-to-standby switchover completed

Detailed Information Active-to-standby switchover is complete.
System Impact None
Probable Cause Active-to-standby switchover notification.
7.3 198092056 Standby-to-active switchover completed

Detailed Information Standby-to-active switchover is complete
System Impact None
Probable Cause Standby-to-active switchover notification.
7.4 198092058 Succeed in repairing the specification

package
Detailed Information 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.

Work normally
Even though the booting is successful, all peripheral boards cannot
Probable Cause Specification package is repaired successfully.
7-2

Chapter 7 Notification
Handling Suggestion Enter the Software Version Management interface to download the
specification package again. After that, activate it.
7.5 198092059 Alarm Storm

Detailed Information When the number of alarms reported during a certain period of time
exceeds the threshold value, the notification is reported.
System Impact The alarm cannot be reported during the alarm storm.
Probable Cause The number of alarms reported during a certain period of time exceeds
the threshold value.
Handling Suggestion Find an alarm code from additional alarm information. Then handle the
alarm according to the alarm code.
7.6 198092061 Module reset

Detailed Information Module reset
System Impact The module has been reset.
Probable Cause The module has been reset.
7.7 198092062 Module status error

Detailed Information The partner machine is in error status. This status is read from signal
line by bottom-layer BSP.
System Impact The module's status is abnormal.
Probable Cause The module's status is abnormal.
Handling Suggestion 1. Remove and insert the board.

2. This abnormity seldom happens. Once it happens, please inform
RD center for fault location.
7.8 198092063 Switchover completed

Detailed Information The switchover is completed.
System Impact Switching succeeded.
7-3

Probable Cause Switching succeeded.
7.9 198092064 Switchover failed

Detailed Information This alarm is reported when active-to-standby or standby-to-active
switchover operation fails.
System Impact Switching failed.
Probable Cause Switching failed.
7.10 198092065 Board switchover failed

Detailed Information The switchover condition is not satisfied.
System Impact CC boards are configured in active/standby mode, but switchover

doesn't work. This reduces system reliability.
Probable Cause Switchover is not allowed.
7.11 198092228 Main board product process power-on

Detailed Information Main board product process power-on notification.
System Impact None
Probable Cause The process is powered on.
7.12 198092229 Slave board product process power-on

Detailed Information Slave board product process power-on notification.
System Impact None
Probable Cause The process is powered on.
7-4

7.13 198092271 Local benchmark clock unlocked

Detailed Information This alarm is reported when Local benchmark clock is unlocked on
the local benchmark clock.

If the accuracy of base station clock doesn't meet 3GPP requirement,
the inter-Base station handover successful ratio must be affected.
Probable Cause 1. Reference source is not configured.

2. Reference source is lost or degraded.
Handling Suggestion 1. Use OMC to check whether clock reference source has been
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
Detailed Information This notification is reported when FS detects that LCV bit error rate
at optical port exceeds threshold.

Work normally
The performance of cell services, associated to the optical port,
becomes worse.
Probable Cause The measured LCV bit error rate from the link between BBU and RRU
exceeds the configured threshold.
Handling Suggestion 1. Check whether the optical fiber between BBU and RRU is well
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

7.15 198092312 PPP Negotiatory IP Conflict

Detailed Information Alarm happens when PPP Negotiatory IP Conflicts with IP that is
configurated.
System Impact PPP link is interrupted or PPP's negotiation is fail.
Probable Cause The IP of PPP which gets from negotiation with the other side is
different from itself IP before.
Handling Suggestion Please check the PPP address configuration and modify.
7.16 198092314 IP Conflict

Detailed Information Alarm happens when original IP in ARP message is the same as
interface IP.
System Impact Base station can't communicate.
Probable Cause The IP of the station is conflicted.
Handling Suggestion Please check the IP address configuration in the net.
7.17 198092315 Mac Conflict

Detailed Information Alarm happens when original Mac in ARP message is the same as
interface Mac.
System Impact Base station can't communicate.
Probable Cause The MAC of the station is conflicted.
7.18 198092316 ACOM address conflict

Detailed Information A new device is inserted. If its address conflicts with existing AISG
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


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 1. This alarm notification may be given if quick deplug-and-plug the
connected AISG device.
2. Otherwise, new device is inserted, which has conflict address with
existing AISG device.
Handling Suggestion On Base station configuration management interface management

interface, scan AISG in AISG Devices Centralized Management dialog
box then add a new device.
7.19 198092329 ATMA device address conflict


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.
Handling Suggestion On Base station configuration management interface management

interface, scan AISG in AISG Devices Centralized Management dialog
box then add a new device.
7-7

7.20 198092338 RET device address conflict


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.
Handling Suggestion On base station configuration management interface, scan AISG in

AISG Devices Centralized Management dialog box then add a new
device.
7.21 198092349 RRU pre-download is successful

Detailed Information Version download is successful or changing boot initial file is successful
System Impact None
Probable Cause Version download is successful or changing boot initial file is successful
7.22 198092381 EFM Link has error data

Detailed Information EFM of ethernet detects that link has error data.
System Impact It has effect on ethernet stability.
Probable Cause Ethernet EFM protocol detects error data in the transport link.
7-8

Handling Suggestion Please check whether the transport link between base station and the
first switchboard is normal.
7.23 198092392 Product process fails to power on

Detailed Information Product process fails to power on.
System Impact It will affect power-on of product process.
Probable Cause 1. Product process fails to power on.

2. Product process power-on is overtime.
7.24 198094823 DPD Running Status Abnormal

Detailed Information DPD module running status is abnormal in RRU.
Severity None
System Impact The downlink power output drops and the quality of RF output
declines.
Probable Cause 1.Input Baseband Signal Too Large.

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 1.Reset the faulty RRU.

2.Replace the faulty RRU.
7.25 198096557 Uplink IQ link error

Detailed Information IQ link from IQ switch card to base band card error.
7-9

System Impact The quality of service may be affected.
Probable Cause IQ link exception.
Handling Suggestion Unplug and plug boards, including IQ exchange board. If problem
exists, replace board.
7.26 198096566 RRU alarm reset

Detailed Information RRU alarm reset.
System Impact The service accessed by this RRU may be interrupted.
Probable Cause 1. DSP software system error.

2. RRU internal communication has fault.
3. Other reason.
Handling Suggestion Replace RRU if it happens frequently.
7.27 198098433 Unavailable alarm of time slot turn-off

function
Detailed Information This alarm is reported when time slot turn-off function cannot be used
because of some constraints on PA hardware or status.

Work normally
The time slot turn-off function cannot be used.
Probable Cause 1. PA hardware has some constraints.

2. PA is abnormally closed.
Handling Suggestion 1. Check whether the current hardware supports the time slot closing
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

Detailed Information Board power-on done notification.
System Impact None
Probable Cause The board is powered on.
7-10

7.29 198092033 Board power-on failed

Detailed Information The board fails to be powered on due to the board's basic process
power-on failure or timeout.
System Impact Board's power-on failure will cause the board to reset.
Probable Cause 1. process power-on failed.

2. Process power-on timeout.
7.30 198092034 Bit error has been detected during E1

physical layer in the past 24 hours
Detailed Information Bit error has been detected during E1 physical layer in the past 24
hours.
System Impact Influence the communication quality.
Probable Cause 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.
Handling Suggestion 1. Check DDF connections: whether jumpers are well connected, there
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
Detailed Information E1 link bit error has been detected in the past 24 hours.
7-11

System Impact Influence the communication quality.
Probable Cause 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.
Handling Suggestion 1. Check DDF connections: whether jumpers are well connected, there
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

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
- 射频
I

RRU
- Remote Radio Unit
- 远端射频单元
SCTP
- Stream Control Transmission Protocol
- 流控制传输协议
TCP
- Transfer Control Protocol
- 传输控制协议
VSWR
- Voltage Standing Wave Ratio
- 电压驻波比
II

eNodeB Alarm Handling Reference PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

eNodeB Alarm Handling Reference PDF

Hochgeladen von

Copyright:

Verfügbare Formate

NetNumen U31(TDD LTE)

Unified Management System

Revision No. Revision Date Revision Reason

R1.1 2012–4–15 Version Upgrade

R1.0 2011–12–20 First Edition

Serial Number: SJ-20120322151347-005

Publishing Date: 2012-04-15(R1.1)

SJ-20120322151347-005|2012-04-15(R1.1) ZTE Proprietary and Confidential

Chapter 3 Equipment Alarm ...................................................................... 3-1

SJ-20120322151347-005|2012-04-15(R1.1) ZTE Proprietary and Confidential

SJ-20120322151347-005|2012-04-15(R1.1) ZTE Proprietary and Confidential

SJ-20120322151347-005|2012-04-15(R1.1) ZTE Proprietary and Confidential

SJ-20120322151347-005|2012-04-15(R1.1) ZTE Proprietary and Confidential

SJ-20120322151347-005|2012-04-15(R1.1) ZTE Proprietary and Confidential

SJ-20120322151347-005|2012-04-15(R1.1) ZTE Proprietary and Confidential

SJ-20120322151347-005|2012-04-15(R1.1) ZTE Proprietary and Confidential

SJ-20120322151347-005|2012-04-15(R1.1) ZTE Proprietary and Confidential

Chapter 4 Environment Alarm................................................................... 4-1

SJ-20120322151347-005|2012-04-15(R1.1) ZTE Proprietary and Confidential

Chapter 5 Processing Alarm ..................................................................... 5-1

SJ-20120322151347-005|2012-04-15(R1.1) ZTE Proprietary and Confidential

Chapter 6 QoS Alarm ................................................................................. 6-1

SJ-20120322151347-005|2012-04-15(R1.1) ZTE Proprietary and Confidential

Chapter 7 Notification ................................................................................ 7-1

SJ-20120322151347-005|2012-04-15(R1.1) ZTE Proprietary and Confidential

SJ-20120322151347-005|2012-04-15(R1.1) ZTE Proprietary and Confidential

SJ-20120322151347-005|2012-04-15(R1.1) ZTE Proprietary and Confidential

What Is in This Manual

Chapter 1, Overview Describes the concept of fault management

Chapter 2, Communication Alarm Describes communication alarms with respect to detailed

Chapter 3, Equipment Alarm Describes equipment alarms with respect to detailed

Chapter 4, Environment Alarm Describes environment alarms with respect to detailed

Chapter 5, Processing Alarm Describes processing alarms with respect to detailed

Chapter 6, QoS Alarm Describes QoS alarms with respect to detailed

Chapter 7, Notification Describes notification with respect to detailed information,

SJ-20120322151347-005|2012-04-15(R1.1) ZTE Proprietary and Confidential

SJ-20120322151347-005|2012-04-15(R1.1) ZTE Proprietary and Confidential

Alarm/Notification Information Structure

SJ-20120322151347-005|2012-04-15(R1.1) ZTE Proprietary and Confidential

SJ-20120322151347-005|2012-04-15(R1.1) ZTE Proprietary and Confidential

Troubleshooting measures and suggestions are provided. Pay attention to the

SJ-20120322151347-005|2012-04-15(R1.1) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20120322151347-005|2012-04-15(R1.1) ZTE Proprietary and Confidential

2.1 198092211 PLL unlocked alarm

SJ-20120322151347-005|2012-04-15(R1.1) ZTE Proprietary and Confidential

2.2 198092230 SCTP association is interrupted.

Probable Cause 1. Local FE configuration or PPP is error.

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

SJ-20120322151347-005|2012-04-15(R1.1) ZTE Proprietary and Confidential

2.3 198092231 PPP Link is broken.

System Impact Commands and services in the PPP are interrupted.

Probable Cause PPP Link is broken.

2.4 198092232 HDLC Link is broken.

System Impact bottom-layer link of communication may be interrupted.

SJ-20120322151347-005|2012-04-15(R1.1) ZTE Proprietary and Confidential

Probable Cause HDLC Link is broken.

2.5 198092233 SSCOP Link is broken.

SJ-20120322151347-005|2012-04-15(R1.1) ZTE Proprietary and Confidential

2.6 198092240 1588 clock link fault

System Impact none

Probable Cause 1. It is impossible to communicate with master clock of this link.

Handling Suggestion 1. Check whether the physical connection to CC is normal.