SJ-20121112095141-003-LTE (V3.10.10) Alarm Handling (FDD) PDF

LTE Alarm Handling
Version: V3.10.10
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 © 2013 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.4 2013-02-05 Correct mistakes on spelling and punctuation.
R1.3 2012-11-08 198094440 is added.
R1.2 2012-10-18 198092215, 198092210 are revised.
R1.1 2012-08-10 These itmes have been updated:
l 198098463 is added.
l 198092022, 198092398, 198092311, 198092384,
198092385, 198092386, 198092387, 198092352,
198092279, 198092280, 198092462, 198092057 are
revidsed.
R1.0 2012-06-05 First edition
Serial Number: SJ-20121112095141-003
Publishing Date: 2013-02-05 (R1.4)
SJ-20121112095141-003|2013-02-05 (R1.4) ZTE Proprietary and Confidential

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

3.1 198092214 Hardware of Clock Module Fault ........................................................ 3-7

3.2 198092215 Lost of synchronization ..................................................................... 3-9
3.3 198092241 1588 clock source unavailable ......................................................... 3-10
3.4 198092216 1PPS Of Current Reference Clock is Lost ........................................3-11
3.5 198092217 Air Interface Clock Unavailable .........................................................3-11
3.6 198092415 Inner GNSS receiver has an alarm................................................... 3-12
3.7 198092416 Inner GNSS antenna has a cable alarm ........................................... 3-13
3.8 198092418 Outer Facepanel GNSS receiver has an alarm ................................. 3-13
3.9 198092419 Outer Facepanel GNSS antenna has a cable alarm .......................... 3-14
3.10 198092422 Outer Backpanel GNSS receiver has an alarm ............................... 3-15
3.11 198092423 Outer Backpanel GNSS antenna has a cable alarm......................... 3-16
3.12 198092426 GNSS cascading clock has an alarm.............................................. 3-16
3.13 198092008 FPGA register read/write error ....................................................... 3-17
3.14 198092298 MMC Fault ................................................................................... 3-18
3.15 198092057 The board is powered off ............................................................... 3-18
3.16 198092072 Board not-in-position ..................................................................... 3-19
3.17 198092203 Board not-configured alarm ........................................................... 3-20
3.18 198092400 Board smart powered-down........................................................... 3-21
3.19 198092009 Ethernet access network interface abnormal................................... 3-21
3.20 198092011 E1/T1 input port unavailable .......................................................... 3-22
3.21 198092012 E1/T1 output port unavailable ........................................................ 3-23
3.22 198092013 ES or SES detected on the E1 link in the past 15 minutes has
exceeded the threshold................................................................................... 3-23
3.23 198092401 E1 link self-loop ............................................................................ 3-24
3.24 198092311 IQ reported is failed ...................................................................... 3-25
3.25 198092383 Distributing IQ resource is failed .................................................... 3-25
3.26 198092384 IQ configuration failure .................................................................. 3-26
3.27 198092385 Optical port speed configuration failure........................................... 3-26
3.28 198092386 TDM port speed configuration failure.............................................. 3-27
3.29 198092387 RRU device delay parameter configuration failure ........................... 3-28
3.30 198092388 Power supply configuration failure.................................................. 3-28
3.31 198092032 Failed to operate Database ........................................................... 3-29
3.32 198092219 Baseband Subunit Fault ................................................................ 3-29
3.33 198092071 Abnormal temperature sensor........................................................ 3-30
3.34 198092352 Unmatched link mode at peer-end electrical port of Ethernet ........... 3-31
3.35 198092393 UES ethernet semiduplex alarm..................................................... 3-32
3.36 198092353 Configuration is failed.................................................................... 3-32
3.37 198092212 EPLD's register has a R/W failure alarm ......................................... 3-33
3.38 198092284 Input reference clock is abnormal................................................... 3-33
II

3.39 198092285 Internal clock is abnormal .............................................................. 3-34
3.40 198092286 The uplink frame at optical/electric port is unlocked......................... 3-35
3.41 198092287 The channel downlink frame is unlocked ........................................ 3-36
3.42 198092288 The PLL clock is unlocked ............................................................. 3-36
3.43 198092289 The optical/electric module is not in the position of optical port......... 3-37
3.44 198092290 The uplink optical/electric link is interrupted ................................... 3-38
3.45 198092291 The input frame synchronous signal is wrong.................................. 3-39
3.46 198092292 An alarm is given when an optical fiber is wrongly connected........... 3-39
3.47 198092295 RRU power-cut alarm ................................................................... 3-40
3.48 198092242 Ir link LCV alarm ........................................................................... 3-41
3.49 198092258 Lost of frame rate and frame number ............................................. 3-42
3.50 198092248 Optical module out-of-position alarm .............................................. 3-42
3.51 198092293 The Rx optical port at RRU has no light signal ................................ 3-43
3.52 198092294 The frame transferred over Rx port of RRU is unlocked ................... 3-44
3.53 198092254 Remote output power abnormal voltage alarm ................................ 3-44
3.54 198092255 Remote input power over-voltage alarm ......................................... 3-45
3.55 198092256 Remote input power under-voltage alarm ....................................... 3-46
3.56 198092269 Over-high temperature of RRU board............................................. 3-47
3.57 198092270 Slight-high temperature of RRU board............................................ 3-48
3.58 198092247 Over-high temperature of PA ........................................................ 3-48
3.59 198092274 Slight-high temperature of PA ........................................................ 3-49
3.60 198092245 Disable PA ................................................................................... 3-50
3.61 198092249 RF board PLL alarm...................................................................... 3-51
3.62 198092277 Clock module fault ........................................................................ 3-52
3.63 198092243 Abnormal DPD running status........................................................ 3-52
3.64 198092244 LNA alarm .................................................................................... 3-53
3.65 198092246 TMA channel input is over current.................................................. 3-54
3.66 198092250 Calibration file on TRx board is abnormal ....................................... 3-54
3.67 198092251 a block check error of downlink IQ channel alarm............................ 3-55
3.68 198092252 Downlink digital IF pre-distortion alarm ........................................... 3-56
3.69 198092253 Application software monitoring alarm ............................................ 3-57
3.70 198092257 Remote antenna over VSWR alarm ............................................... 3-57
3.71 198092272 The value of RSSI over reverse link is low ...................................... 3-58
3.72 198092273 The value of RSSI over reverse link is high..................................... 3-59
3.73 198092275 PA communication fault ................................................................. 3-60
3.74 198092276 Receiving RF channel fault ............................................................ 3-60
3.75 198092278 Abnormal power ........................................................................... 3-61
III

3.76 198092279 Downlink analog power exceeds rated value .................................. 3-62
3.77 198092280 Downlink digital power exceeds rated value ................................... 3-62
3.78 198092281 Downlink carrier baseband power is low ......................................... 3-63
3.79 198092282 Downlink carrier analog power is low.............................................. 3-64
3.80 198092283 Remote antenna VSWR alarm....................................................... 3-64
3.81 198092379 PA over power alarm..................................................................... 3-65
3.82 198092364 Calibrate Fail ................................................................................ 3-66
3.83 198092365 Low Power Exception.................................................................... 3-67
3.84 198092317 ACOM major alarm ....................................................................... 3-67
3.85 198092318 ACOM minor alarm ....................................................................... 3-68
3.86 198092319 ACOM hardware fault ................................................................... 3-68
3.87 198092320 ACOM communication link is interrupted ........................................ 3-69
3.88 198092321 ACOM software fault ..................................................................... 3-70
3.89 198092322 AISG EEPROM error .................................................................... 3-70
3.90 198092323 AISG flash erase error .................................................................. 3-71
3.91 198092324 AISG flash error............................................................................ 3-72
3.92 198092325 AISG other hardware error ............................................................ 3-72
3.93 198092326 AISG other software error.............................................................. 3-73
3.94 198092327 AISG RAM error ........................................................................... 3-74
3.95 198092328 AISG UART error.......................................................................... 3-74
3.96 198092330 ATMA major alarm ........................................................................ 3-75
3.97 198092331 ATMA minor alarm ........................................................................ 3-75
3.98 198092332 Failed to set gain .......................................................................... 3-76
3.99 198092333 ATMA hardware fault .................................................................... 3-77
3.100 198092334 ATMA communication link is interrupted ....................................... 3-77
3.101 198092335 ATMA software fault .................................................................... 3-78
3.102 198092336 Board configuration parameter error............................................. 3-79
3.103 198092337 RET motor fault .......................................................................... 3-79
3.104 198092339 RET hardware fault ..................................................................... 3-80
3.105 198092340 RET motor can't adjust ................................................................ 3-80
3.106 198092341 RET motor don't response the adjusting command........................ 3-81
3.107 198092342 RET communication link is interrupted.......................................... 3-82
3.108 198092343 RET don't calibrated.................................................................... 3-82
3.109 198092344 RET data don't scaled ................................................................ 3-83
3.110 198092345 RET position lost ......................................................................... 3-83
3.111 198092346 RET software fault ....................................................................... 3-84
3.112 198092374 UCI optical module of optical port is out of position ........................ 3-85
IV

3.113 198092375 UCI optical module of optical port has no light signal ..................... 3-85
3.114 198092376 UCI receiver frame at optical port is unlocked................................ 3-86
3.115 198092377 UCI fiber delay adjust is failed ...................................................... 3-87
3.116 198092378 Board PLL is unlocked................................................................. 3-87
3.117 198092049 Lightning protection device alarm ................................................. 3-88
3.118 198092051 PSU alarm .................................................................................. 3-89
3.119 198092052 PSU fan alarm ............................................................................ 3-89
3.120 198092068 Main power supply has a fault alarm ............................................ 3-90
3.121 198092206 Battery alarm .............................................................................. 3-90
3.122 198092207 AC power-cut alarm .................................................................... 3-91
3.123 198092208 Rectifier module alarm ................................................................ 3-92
3.124 198092209 Thermoelectric cooler alarm ........................................................ 3-92
3.125 198092259 Battery low-voltage alarm ............................................................ 3-93
3.126 198092260 Faulty external device connected at a dry contact ......................... 3-94
3.127 198092261 Outdoor lightning protection box alarm ......................................... 3-94
3.128 198092262 Breaker alarm in indoor lightning protection box ............................ 3-95
3.129 198092263 Lightning protection device alarm in indoor lightning protection
box ............................................................................................................... 3-96
3.130 198092264 Over-voltage alarm of main power input ....................................... 3-97
3.131 198092265 Main power input power-cut alarm................................................ 3-98
3.132 198092266 Under-voltage alarm of main power input...................................... 3-99
3.133 198092363 Faulty main power alarm ............................................................ 3-99
3.134 198092267 General fault of main power .......................................................3-100
3.135 198092268 PWR monitoring unit alarm ........................................................3-101
3.136 198092550 User-defined dry contact alarm 1 ................................................3-101
3.145 198092559 User-defined dry contact alarm 10...............................................3-107
3.146 198092560 User-defined dry contact alarm 11 ...............................................3-107

3.150 198092564 User-defined dry contact alarm 15............................................... 3-110
3.186 198092073 Embedded power AC-in Switch Off .............................................3-131
VI

3.187 198092074 Embedded power AC Power Off .................................................3-132
3.188 198092075 Embedded power SPD-C Broken ................................................3-133
3.189 198092076 Embedded power SPD-D Broken ................................................3-133
3.190 198092077 Embedded power AC Under-Volt ................................................3-134
3.191 198092078 Embedded power AC Over-Volt ..................................................3-135
3.192 198092079 Embedded power AC Current Over .............................................3-136
3.193 198092116 Embedded power AC Auxiliary Output Switch Off .........................3-136
3.194 198092447 Unbalanced AC phase voltage of built-in power ...........................3-137
3.195 198092448 High AC phase current of built-in power.......................................3-138
3.196 198092449 Missing AC phase voltage of built-in power .................................3-138
3.197 198092117 Embedded power Rectifier Module Fault......................................3-139
3.198 198092080 Embedded power SMR Over-Vout ..............................................3-140
3.199 198092081 Embedded power SMR Over-Iout................................................3-140
3.200 198092082 Embedded power SMR Fan Fault ...............................................3-141
3.201 198092083 Embedded power SMR PFC Fault ..............................................3-142
3.202 198092084 Embedded power SMR Over-Vin Off ...........................................3-142
3.203 198092085 Embedded power SMR Under-Vin Off .........................................3-143
3.204 198092086 Embedded power SMR H.T. Off ..................................................3-143
3.205 198092087 Embedded power SMR Env.H.T.Off.............................................3-144
3.206 198092088 Embedded power SMR Env.H.T..................................................3-144
3.207 198092089 Embedded power SMR L.Vin ......................................................3-145
3.208 198092090 Embedded power SMR Fuse Broken...........................................3-146
3.209 198092091 Embedded power SMR CommFail ..............................................3-146
3.210 198092236 Embedded power SMR Output Fault ...........................................3-147
3.211 198092394 Several faulty rectifiers ..............................................................3-148
3.212 198092092 Embedded power DC Under-Volt ................................................3-148
3.213 198092093 Embedded power DC Over-Volt ..................................................3-149
3.214 198092094 Embedded power DC Loop Broken .............................................3-150
3.215 198092095 Embedded power Bat Loop Broken .............................................3-150
3.216 198092096 Embedded power Bat Under-Volt ................................................3-151
3.217 198092097 Embedded power Bat Over-Temp ...............................................3-152
3.218 198092098 Embedded power TmpL Shut-Down............................................3-153
3.219 198092099 Embedded power 1st Shut-down ................................................3-153
3.220 198092100 Embedded power 2nd Shut-down ...............................................3-154
3.221 198092101 Embedded power DC SPD Broken..............................................3-155
3.222 198092102 Embedded power DCBreaker Alarm............................................3-156
3.223 198092103 Embedded power Bat Test Failure...............................................3-156
VII

3.224 198092104 Embedded power Bat Discharge.................................................3-157
3.225 198092237 Embedded power Bat Under-Temp .............................................3-158
3.226 198092238 Embedded power Bat Invalid-Temp .............................................3-159
3.227 198092239 Embedded power Battery Fault ...................................................3-159
3.228 198092450 Battery low-voltage cut-off of built-in power .................................3-160
3.229 198092451 Broken LLVD1 branch E of built-in power.....................................3-161
3.230 198092452 Broken LLVD1 branch of built-in power .......................................3-162
3.231 198092453 Broken LLVD2 branch E of built-in power.....................................3-163
3.232 198092454 Broken battery cut-off branch E of built-in power ..........................3-164
3.233 198092455 Broken battery cut-off branch of built-in power .............................3-165
3.234 198092456 Abnormal battery current of built-in power ...................................3-166
3.235 198092457 Abnormal CAN bus of built-in power ...........................................3-166
3.236 198092458 Abnormal battery of built-in power ..............................................3-167
3.237 198092459 Abnormal input dry contact of built-in power ................................3-168
3.238 198092460 High-temperature cut-off of built-in power ....................................3-168
3.239 198092234 Embedded power type configuration error ...................................3-169
3.240 198092235 Embedded power communication interruption..............................3-170
3.241 198096550 Alarm of fiber configuration .........................................................3-170
3.242 198096551 RRU unconfigured ....................................................................3-171
3.243 198096552 Difference of fiber time delay of two RRUs in same sector
exceeded system limit....................................................................................3-171
3.244 198096553 RRU Type is not consistent with configuration type.......................3-172
3.245 198096554 Failure of optical decoding in BBU...............................................3-172
3.246 198096555 Failure of optical decoding in RRU ..............................................3-173
3.247 198096556 IQ link input loses lock................................................................3-173
3.248 198096558 Downlink baseband power abnormal ...........................................3-174
3.249 198096559 RRU adjust channel or adjust cable fault .....................................3-175
3.250 198096560 Master and slave monitor link alarm ............................................3-175
3.251 198096561 Coherence alarm of antenna channel swing and phase ................3-176
3.252 198096562 RRU self check failed when power on .........................................3-176
3.253 198096563 RRU device alarm......................................................................3-177
3.254 198096565 Configurate parameter of RRU external device not consistent
with real parameter ........................................................................................3-178
3.255 198092433 RRU network interrupted alarm ...................................................3-178
3.256 198092434 Clock line abnormal connection in stack mode .............................3-179
3.257 198092435 Inter-frame Ethernet link broken in stack mode ............................3-179
3.258 198092436 Loss of clock synchronization at slave frame................................3-180
3.259 198092437 RRU radio frequency group unavailable ......................................3-181
VIII

3.260 198092438 Device in low temperature ..........................................................3-181
3.261 198092439 Uplink transport port of a base station operates in a different
mode from configured one..............................................................................3-182
3.262 198092461 BBU inter-subrack frame synchronization failure alarm ................3-183
3.263 198098431 Abnormal current alarm at NSBT port .........................................3-184
3.264 198098432 AISG/NSBT port turn-off alarm due to over current.......................3-185
3.265 198098434 Abnormal transmission power at antenna port .............................3-186
3.266 198098435 Closed-loop power control adjustment exceeding normal
range ............................................................................................................3-186
3.267 198098436 Failure in configuring power level ................................................3-187
3.268 198096568 RRU used power module is too hot .............................................3-188
3.269 198096569 RRU offline parameter check failure ...........................................3-188
3.270 198100270 Optical signals transmitted from BBU to RRU carry wrong clock
information ....................................................................................................3-189
3.271 198100271 Unlocked local oscillator alarm of RRU ........................................3-189
3.272 198100272 RRU inside clock unlocked .........................................................3-190
3.273 198100273 Downlink channel fault alarm ......................................................3-191
3.274 198100274 Downlink output power abnormal ................................................3-191
3.275 198098438 The internal power module in a RRU detects invalid lightning
protection circuit ............................................................................................3-192
3.276 198094412 Fault in BPL clock .....................................................................3-193
3.277 198094413 Fault in BPL hardware ................................................................3-194
3.278 198094414 Discontinuous frame number ......................................................3-194
3.279 198094415 Frame frequency abnormal.........................................................3-196
3.280 198094425 Optical module temperature is abnormal......................................3-197
3.281 198094426 Optical module bias current is abnormal ......................................3-198
3.282 198094427 Optical module transmit power is abnormal..................................3-199
3.283 198094428 Optical module inner voltage is abnormal ....................................3-199
3.284 198098439 ATMA works in bypass mode ......................................................3-200
Chapter 4 Environment Alarm................................................................... 4-1

4.1 198092307 Slight-high temperature of board........................................................ 4-2
4.2 198092308 Over-high temperature of board......................................................... 4-2
4.3 198092429 Board powered-down alarm because of high temperature ................... 4-3
4.4 198092371 CCM Remote MEP Error ................................................................... 4-4
4.5 198092372 CCM Message Error ......................................................................... 4-4
4.6 198092373 CCM Xconnect Error......................................................................... 4-5
4.7 198092053 Abnormal input voltage ..................................................................... 4-5
4.8 198092037 MP voltage abnormal ........................................................................ 4-6
IX

4.9 198092038 PP voltage abnormal......................................................................... 4-6
4.10 198092039 Over current of MP.......................................................................... 4-7
4.11 198092040 Over current of PP .......................................................................... 4-8
4.12 198092041 Fan failure ...................................................................................... 4-8
4.13 198092069 FCE-fan failure ............................................................................... 4-9
4.14 198092042 Abnormal temperature at air intake ................................................ 4-10
4.15 198092043 Abnormal temperature at air outlet ..................................................4-11
4.16 198092213 Abnormal temperature of board ..................................................... 4-12
4.17 198092044 Door control alarm ....................................................................... 4-12
4.18 198092045 Flooding alarm.............................................................................. 4-13
4.19 198092046 Smog alarm.................................................................................. 4-14
4.20 198092047 Infrared alarm .............................................................................. 4-14
4.21 198092048 Air conditioner fault ....................................................................... 4-15
4.22 198092105 Embedded power Environment is under-temperature ...................... 4-16
4.23 198092106 Embedded power Environment is over-temperature ........................ 4-16
4.24 198092107 Embedded power Environment temperature is invalid ..................... 4-17
4.25 198092108 Embedded power Environment is under-Humidity ........................... 4-18
4.26 198092109 Embedded power Environment is over-Humidity ............................. 4-18
4.27 198092110 Embedded power Environment humidity is invalid ........................... 4-19
4.28 198092111 Embedded power Smoke detected ................................................. 4-20
4.29 198092112 Embedded power Flood detected................................................... 4-20
4.30 198092113 Embedded power Door Magnet Alarm ............................................ 4-21
4.31 198092114 Embedded power Gate Embedded power Safety Alarm .................. 4-22
4.32 198092115 Glass Broken Alarm ...................................................................... 4-23
4.33 198092118 Embedded power Env-unit communication interruption.................... 4-23
4.34 198092119 Embedded power Heat Exchanger Fault......................................... 4-24
4.35 198098128 Over-loaded power ....................................................................... 4-25
4.36 198092462 Blocked dust proof net .................................................................. 4-25
Chapter 5 Processing Alarm ..................................................................... 5-1

5.1 198092309 Line clock has the fault...................................................................... 5-2
5.2 198092310 SyncE clock has the fault .................................................................. 5-3
5.3 198092414 SyncE clock unavailable (SyncE+1588) ............................................. 5-4
5.4 198092412 1PPS+TOD source fault ................................................................... 5-4
5.5 198092413 1PPS+TOD Backup source fault ........................................................ 5-5
5.6 198092463 BSP initialization failure..................................................................... 5-6
5.7 198092348 Board initialization ............................................................................ 5-7
5.8 198092390 CPU over loading highly alarm........................................................... 5-7

5.9 198092391 CPU over loading ............................................................................. 5-8
5.10 198092347 The fan control policy is not existed ................................................. 5-8
5.11 198092014 SNTP time adjustment failure alarm ................................................. 5-9
5.12 198092016 Clock reference source configuration error ..................................... 5-10
5.13 198092017 Failure in loading software............................................................. 5-10
5.14 198092070 Board software has fault.................................................................5-11
5.15 198092022 Running software version doesn't exist........................................... 5-12
5.16 198092027 Failure in repairing specification package ....................................... 5-13
5.17 198092029 Wrong board insertion ................................................................... 5-13
5.18 198092030 Abnormal software in specification package.................................... 5-14
5.19 198092395 Running software rollback ............................................................. 5-15
5.20 198092396 Board hot patch fault ..................................................................... 5-15
5.21 198092397 Failure in finding this board-related software ID .............................. 5-16
5.22 198092398 MMC running software version doesn't exist ................................... 5-17
5.23 198092443 IR changeover failure ................................................................... 5-17
5.24 198092066 Failure in uncompressing LMT software ......................................... 5-18
5.25 198092360 Product process is abnormal ......................................................... 5-19
5.26 198092060 LMT accessing ............................................................................. 5-19
5.27 198092430 Optical module rate does not match ............................................... 5-20
5.28 198092432 Optical modules have mismatched transmission distance................ 5-20
5.29 198092366 Configuration Fail.......................................................................... 5-21
5.30 198092403 Carrier frequency configuration error .............................................. 5-22
5.31 198092404 Center frequency configuration error .............................................. 5-22
5.32 198092405 Work pattern configuration error..................................................... 5-23
5.33 198092406 IQ parameter configuration error .................................................... 5-23
5.34 198092407 Delay parameter configuration error ............................................... 5-24
5.35 198092408 Carrier power configuration error.................................................... 5-25
5.36 198096567 BOOT software upgrade failure...................................................... 5-25
5.37 198098437 The configured total power exceeds rated value ............................. 5-26
5.38 198100275 RRU software version is abnormal ................................................. 5-26
5.39 198092010 Board communication link is interrupted ......................................... 5-27
5.40 198092019 Failure in synchronizing the version of master board with slave
board ............................................................................................................. 5-28
5.41 198092024 DOM is lack of space .................................................................... 5-29
5.42 198092025 Failure in synchronizing software version of main control board ....... 5-29
5.43 198094418 Rule library of performance statistics hasn't been loaded or loaded
unsuccessfully................................................................................................ 5-30
5.44 198094429 Optical module rate does not match ............................................... 5-31
XI

5.45 198094434 Optical modules have mismatched transmission distance................ 5-31
5.46 198098463 Two small carrier frequency interval ............................................... 5-32
Chapter 6 QoS Alarm ................................................................................. 6-1

6.1 198092417 Inner GNSS receiver has a satellite searching alarm........................... 6-1
6.2 198092420 Outer Facepanel GNSS receiver has a satellite searching alarm.......... 6-2
6.3 198092424 Outer Backpanel GNSS receiver has a satellite searching alarm.......... 6-3
6.4 198092368 Ethernet remote fault alarm(RDI) ....................................................... 6-3
6.5 198092380 EFM Link is broken ........................................................................... 6-4
6.6 198092370 AIS alarm ......................................................................................... 6-4
6.7 198094419 Cell outage....................................................................................... 6-5
6.8 198094422 eNodeB is out of service ................................................................... 6-6
6.9 198094440 Cell portion is out of service............................................................... 6-7
Chapter 7 Notification ................................................................................ 7-1

7.1 198092059 Alarm Storm ..................................................................................... 7-2
7.2 198092063 Switchover completed ....................................................................... 7-2
7.3 198092064 Switchover failed .............................................................................. 7-2
7.4 198092065 Board switchover failed ..................................................................... 7-3
7.5 198092392 Product process fails to power on ...................................................... 7-3
7.6 198092058 Software version recover succeed ..................................................... 7-4
7.7 198092441 IR changeover successful ................................................................ 7-4
7.8 198092442 No need for IR changeover ............................................................... 7-5
7.9 198092440 End of loading product process ......................................................... 7-5
7.10 198092444 SSCOP fault .................................................................................. 7-5
7.11 198092381 EFM Link has error data .................................................................. 7-6
7.12 198092031 Board power-on done notification..................................................... 7-7
7.13 198092054 Slave board powered-on notification ................................................ 7-7
7.14 198092055 Active-to-standby switchover completed ........................................... 7-7
7.15 198092056 Standby-to-active switchover completed........................................... 7-8
7.16 198092033 Board power-on failed ..................................................................... 7-8
7.17 198092061 Module reset .................................................................................. 7-9
7.18 198092062 Module status error ......................................................................... 7-9
7.19 198092228 Main board product process power-on............................................ 7-10
7.20 198092229 Slave board product process power-on .......................................... 7-10
7.21 198092297 Uplink optical/electrical link has high BER ...................................... 7-10
7.22 198092271 Local benchmark clock unlocked ....................................................7-11
7.23 198092316 ACOM address conflict.................................................................. 7-12
7.24 198092329 ATMA device address conflict ........................................................ 7-13
XII

7.25 198092338 RET device address conflict .......................................................... 7-13
7.26 198096557 Uplink IQ link error ........................................................................ 7-14
7.27 198096566 RRU alarm reset ........................................................................... 7-14
7.28 198098433 Unavailable alarm of time slot turn-off function ................................ 7-15
7.29 198097907 Opening of Node B via USB finishes .............................................. 7-15
7.30 198097804 Um interface implements clock synchronization via software............ 7-16
7.31 198092034 Bit error has been detected during E1 physical layer in the past 24
hours ............................................................................................................. 7-16
7.32 198092035 E1 link bit error has been detected in the past 24 hours................... 7-17
7.33 198092312 PPP Negotiatory IP Conflict ........................................................... 7-18
7.34 198092314 IP Conflict .................................................................................... 7-18
7.35 198092315 Mac Conflict ................................................................................. 7-18
7.36 198094432 DSP error notification .................................................................... 7-19
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
Related Documentation
The following documentation is related to this manual:
l ZXSDR B8200 L200 LTE Baseband Unit Fault Management Operation Guide
l ZXSDR B8200 L200 LTE Baseband Unit Troubleshooting Guide

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

LTE Alarm Handling
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

LTE Alarm Handling
This page intentionally left blank.
1-4

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

LTE Alarm Handling
2.1 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.2 198092411 BITS clock fault

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

Chapter 2 Communication Alarm
System Impact
I. Board Status:
Work normally.
II. Impact on Service:
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.3 198092361 IMA group has fault

Alarm happens when IMA group is configured successfully, but IMA group cannot reach normal
working status.
Severity
Major
2-3

LTE Alarm Handling
System Impact
I. Board Status:
Board operation is normal.
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:
198092362 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.
2.4 198092362 IMA/TC link has fault

This alarm is reported when IMA group sub-link/TC link has a fault.
Severity
Major
System Impact
I. Board Status:
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.
2-4

Handling Suggestion
1. Check the link configuration between base station and RNC:

l If TC mode is configured, please check TC slot configuration for base station and RNC.
l If the configuration is inconsistent, please correct it.
l 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
l 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.5 198092230 SCTP association is interrupted

This alarm is given when SCTP association setup is failed, local end has received close notification
from its peer end, or there is no response after continuously sending data to its peer end.
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.
2-5

LTE Alarm Handling
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, jump "2) deal with FE port or PPP related alarm".
N->not exist, jump "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, jump "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 jump "3) wait alarm recover".
N->Inconsistent, jump "3) Reconfigure SCTP coupling".
3) Wait alarm recover.
Wait for a while, Determine whether the alarm is recovered.
N->alarm is not recovered, please contact ZTE.
3. Reconfigure 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.6 198092231 PPP Link is broken

Iub link has fault.
Severity
Critical
System Impact
Commands and services in the PPP are interrupted.
Probable Cause
PPP Link is broken.
2-6

Handling Suggestion
1. If PPP exist in E1/STM1, check if the related E1/STM1 link has error alarm.
Y->exist, jump "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, jump "3. Reset board".
3. Reset board.
Reset board, wait 2 minutes, Determine whether the alarm is recovered.
N->alarm is not recovered, jump "4. Replace board".
4. Replace board.
Replace error board, wait 2 minutes, determine whether the alarm is recovered.
N->alarm is not recovered, please contact ZTE
2.7 198092232 HDLC Link is broken

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.
Probable Cause
HDLC Link is broken.
2-7

LTE Alarm Handling
Handling Suggestion
1. If HDLC exist in E1/STM1, check if the related E1/STM1 link has error alarm.
Y->exist, jump "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.
N->alarm is not recovered, jump "3. Reset board".
3. Reset board.
Reset board, wait 2 minutes, Determine whether the alarm is recovered.
N->alarm is not recovered, jump "4. Replace board".
4. Replace board.
Replace error board, wait 2 minutes, determine whether the alarm is recovered.
2.8 198092402 TCP connection is broken

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.
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.
2-8

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, jump "2) deal with FE port or PPP related alarm".
N->not exist, jump "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, jump "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 jump "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.
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
2.9 198092233 SSCOP Link is broken

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 received and send so that the services are interrupted.
2-9

LTE Alarm Handling
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 .
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 can not 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 can not 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.10 198092313 PPP Link Loop

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-10

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.11 198092367 802.1x authentication failed

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.12 198092369 LCK alarm

ETH-LCK informs MEP to lock data service stream.
Severity
Major
2-11

LTE Alarm Handling
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
OMCB channel is abnormal and need to configurate correct channel data.
Severity
Major
System Impact
I. Board Status:
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

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.
2-12

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.
Handling Suggestion
1. Check whether FE port exists.

1) Check whether FE port exists.
Y->Skip to “2) Handle FE port”.
N->Skip 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->End alarm process.
N->Skip 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->Wait for a moment. The BFD connection setup to be initiated on time. Then skip to “3) Wait for
alarm recovery”.
N->Skip to “3. Re-configure BFD connection”.
3) Wait for alarm recovery.
Wait for a moment, check whether the alarm is recovered.
Y->End alarm process.
N-> 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.
Y-> End alarm process.
N->Please Contact ZTE.
2-13

LTE Alarm Handling
2.15 198092427 The number of SCTP streams is

inconsistent
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.16 198092428 SCTP path is interrupted

This alarm is reported when a SCTP path transmits a heartbeat message but there is no response, or
the number of retransmission attempts exceeds its maximum retransmissions.
Severity
Major
2-14

System Impact
I. Board Status:
Work normally.
II. 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.17 198092351 Local LMT's Force Connect

Local LMT's Force Connect.
Severity
Warning
System Impact
None
2-15

LTE Alarm Handling
Probable Cause
Local LMT Connect base station forcedly.
Handling Suggestion
None
2.18 198092211 PLL unlocked alarm

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.
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.19 198092210 PLL reference clock lost alarm

This alarm is reported when the PLL used reference clock is lost.
Severity
Major
2-16

System Impact
The SyncE Clock used by the board is affected.
Probable Cause
1. The reference clock is wrongly configured.

2. The configured synchronous Ethernet has a broken link.
Handling Suggestion
1. Check whether the synchronous Ethernet is configured with correct reference clock.
2. Check whether the synchronous Ethernet related link is normal.
2.20 198092431 The strength of received optical signal

is abnormal
This alarm is reported when the received power by an optical module is too high or too low.
Severity
Minor
System Impact
I. Board Status:
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.
2-17

LTE Alarm Handling
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.21 198096564 RRU and outer LNA communication

link broke
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-18

2.22 198092445 RRU inner GNSS (clock reference

source) link alarm
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
System Impact
I. Board Status:
Work normally.
II. 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.23 198092446 RRU inner GNSS (clock reference

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

LTE Alarm Handling
System Impact
I. Board Status:
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.24 198097169 ICMPARP detects unavailable target IP

ICMPARP detects unavailable target IP.
Severity
Major
System Impact
Signaling cannot be received or transmitted properly so that all services borne over this route are
interrupted.
Probable Cause
The target IP route is disconnected. Please check configuration or networking situation.
Handling Suggestion
Please check configuration and networking situation.
2-20

2.25 198094416 CPRI link abnormal

This alarm occurs when the link between the BBU and an RRU is abnormal.
Severity
Major
System Impact
The services on the Common Public Radio Interface (CPRI) link are interrupted.
Probable Cause
1. The optical fiber is not installed properly.

2. The optical module is not in position.
3. The optical fiber connectors are not clean.
4. The rate of the optical module does not match that of the optical fiber.
5. The rate of the optical module is not supported by the current version.
6. The version operating on the RRU is incorrect.
7. The RRU is faulty.
8. The BPL board is faulty.
9. The transmission network is faulty.
10. The optical fiber is faulty.
Handling Suggestion
1. Check whether the optical fiber is inserted into the correct optical port.
l Yes -> Go to step 2.
l No -> Insert the optical fiber into the correct optical port, and check whether the alarm is resolved.
à Yes -> No further action is required.
à No -> Go to step 2.
2. Check whether the optical fiber connectors are clean.
l No -> Clean the connector, insert it into the correct optical port, and check whether the alarm is
resolved.
3. Check whether the rate of the optical module matches the rate supported by the current version.
l No -> Replace the optical module, and check whether the alarm is resolved.
2-21

LTE Alarm Handling
4. Check whether the rate of the optical module matches that of the optical fiber.
l No -> Replace the optical fiber or the optical module, and check whether the alarm is resolved.
5. Check whether the running software version of the RRU is correct.
l No -> Modify the software version, and check whether the alarm is resolved.
6. Use an optical power meter to measure the uplink/downlink receive power to see whether it is
higher than -18 dBm.
l Yes -> Contact the transmission network maintenance personnel to check whether the
transmission network is faulty.
à Yes -> Troubleshoot the transmission network fault, and check whether the alarm is resolved.
t Yes -> No further action is required.
t No -> Go to step 7.
l No -> Go to step 7.
7. Reset the faulty board.
In the detailed alarm information, if the Remark field contains content like uplink LOS, uplink LOF, or
LOOP, reset the RRU.
In the detailed alarm information, if the Remark field contains content like downlink LOS or downlink
LOF, reset the BPL board.
Check whether the alarm is resolved.
l Yes -> No further action is required.
8. Replace the faulty board.
In the detailed alarm information, if the Remark field contains content like uplink LOS, uplink LOF,
or LOOP, replace the RRU.
In the detailed alarm information, if the Remark field contains content like downlink LOS or downlink
LOF, replace the BPL board.
Check whether the alarm is resolved.
9. Replace the optical fiber, and check whether the alarm is resolved.
l No -> Contact Vendor's Technical Support.
2-22

2.26 198094420 S1 link is broken

This alarm occurs when the Stream Control Transmission Protocol (SCTP) association is interrupted
or S1 AP fails to be established.
Severity
Critical
System Impact
The link between the eNodeB and the MME is broken, and the eNodeB cannot provide services.
Probable Cause
1. The SCTP association is broken.

2. The S1 AP fails to be established.
Handling Suggestion
1. Check the detailed alarm information to see whether the Remark field contains content like SCTP
association being broken.
l Yes -> Verify that the eNodeB is connected to the core network properly, and check whether
the alarm is resolved.
2. Check the detailed alarm information to see whether the Remark field contains content like S1 AP
establishment failure.
l Yes -> Verify that the eNodeB is configured with cells and S1 parameters are configured properly,
synchronize the configuration data to that of the eNodeB, and check whether the alarm is
resolved.
à No -> Contact Vendor's Technical Support.
2-23

LTE Alarm Handling
2.27 198094421 X2 link is broken

This alarm occurs when the SCTP association is interrupted or X2 AP fails to be established.
Severity
Major
System Impact
The link between two neighbor eNodeBs is broken, which will affect the X2 interface switchover
between the two eNodeBs.
Probable Cause
1. The SCTP association is broken.

2. The X2 AP fails to be established.
Handling Suggestion
1. Check the detailed alarm information to see whether the Remark field contains content like SCTP
association being broken.
l Yes -> Verify that the eNodeB is connected to the core network properly, and check whether
2. Check the detailed alarm information to see whether the Remark field contains content like X2 AP
establishment failure.
l Yes -> Verify that the eNodeB is configured with cells and X2 parameters are configured properly,
synchronize the configuration data to that of the eNodeB, and check whether the alarm is
resolved.
2-24

2.28 198094430 The strength of received optical signal

is abnormal
This alarm occurs when the receive optical power of the optical module is too low or too high.
Severity
Minor
System Impact
The optical port link is broken.
Probable Cause
1. The receive power of the optical module is too low.

2. The receive power of the optical module is too high.
Handling Suggestion
1. Verify that the optical module and optical fiber are connected properly, and check whether the
alarm is resolved.
Yes -> No further action is required.
No -> Go to step 2.
2. Replace the optical module or optical fiber, and check whether the alarm is resolved.
No -> Contact Vendor's Technical Support.
2-25

LTE Alarm Handling
2-26

Chapter 3
Equipment Alarm
Table of Contents
198092214 Hardware of Clock Module Fault ..............................................................3-7
198092215 Lost of synchronization ............................................................................3-9
198092241 1588 clock source unavailable ...............................................................3-10
198092216 1PPS Of Current Reference Clock is Lost .............................................3-11
198092217 Air Interface Clock Unavailable ..............................................................3-11
198092415 Inner GNSS receiver has an alarm.........................................................3-12
198092416 Inner GNSS antenna has a cable alarm .................................................3-13
198092418 Outer Facepanel GNSS receiver has an alarm ......................................3-13
198092419 Outer Facepanel GNSS antenna has a cable alarm...............................3-14
198092422 Outer Backpanel GNSS receiver has an alarm ......................................3-15
198092423 Outer Backpanel GNSS antenna has a cable alarm...............................3-16
198092426 GNSS cascading clock has an alarm .....................................................3-16
198092008 FPGA register read/write error ...............................................................3-17
198092298 MMC Fault .............................................................................................3-18
198092057 The board is powered off .......................................................................3-18
198092072 Board not-in-position..............................................................................3-19
198092203 Board not-configured alarm....................................................................3-20
198092400 Board smart powered-down ...................................................................3-21
198092009 Ethernet access network interface abnormal..........................................3-21
198092011 E1/T1 input port unavailable...................................................................3-22
198092012 E1/T1 output port unavailable ................................................................3-23
198092013 ES or SES detected on the E1 link in the past 15 minutes has exceeded
the threshold ............................................................................................................3-23
198092401 E1 link self-loop .....................................................................................3-24
198092311 IQ reported is failed ...............................................................................3-25
198092383 Distributing IQ resource is failed ............................................................3-25
198092384 IQ configuration failure...........................................................................3-26
198092385 Optical port speed configuration failure ..................................................3-26
198092386 TDM port speed configuration failure .....................................................3-27
198092387 RRU device delay parameter configuration failure..................................3-28
198092388 Power supply configuration failure .........................................................3-28
198092032 Failed to operate Database....................................................................3-29
198092219 Baseband Subunit Fault.........................................................................3-29
198092071 Abnormal temperature sensor................................................................3-30
198092352 Unmatched link mode at peer-end electrical port of Ethernet .................3-31
198092393 UES ethernet semiduplex alarm.............................................................3-32
198092353 Configuration is failed ............................................................................3-32
3-1

LTE Alarm Handling
198092212 EPLD's register has a R/W failure alarm ................................................3-33

198092284 Input reference clock is abnormal ..........................................................3-33
198092285 Internal clock is abnormal ......................................................................3-34
198092286 The uplink frame at optical/electric port is unlocked ...............................3-35
198092287 The channel downlink frame is unlocked................................................3-36
198092288 The PLL clock is unlocked .....................................................................3-36
198092289 The optical/electric module is not in the position of optical port ..............3-37
198092290 The uplink optical/electric link is interrupted ..........................................3-38
198092291 The input frame synchronous signal is wrong.........................................3-39
198092292 An alarm is given when an optical fiber is wrongly connected ................3-39
198092295 RRU power-cut alarm ...........................................................................3-40
198092242 Ir link LCV alarm ....................................................................................3-41
198092258 Lost of frame rate and frame number .....................................................3-42
198092248 Optical module out-of-position alarm......................................................3-42
198092293 The Rx optical port at RRU has no light signal .......................................3-43
198092294 The frame transferred over Rx port of RRU is unlocked .........................3-44
198092254 Remote output power abnormal voltage alarm .......................................3-44
198092255 Remote input power over-voltage alarm.................................................3-45
198092256 Remote input power under-voltage alarm...............................................3-46
198092269 Over-high temperature of RRU board ....................................................3-47
198092270 Slight-high temperature of RRU board ...................................................3-48
198092247 Over-high temperature of PA .................................................................3-48
198092274 Slight-high temperature of PA ................................................................3-49
198092245 Disable PA .............................................................................................3-50
198092249 RF board PLL alarm...............................................................................3-51
198092277 Clock module fault .................................................................................3-52
198092243 Abnormal DPD running status................................................................3-52
198092244 LNA alarm .............................................................................................3-53
198092246 TMA channel input is over current..........................................................3-54
198092250 Calibration file on TRx board is abnormal...............................................3-54
198092251 a block check error of downlink IQ channel alarm ..................................3-55
198092252 Downlink digital IF pre-distortion alarm ..................................................3-56
198092253 Application software monitoring alarm....................................................3-57
198092257 Remote antenna over VSWR alarm .......................................................3-57
198092272 The value of RSSI over reverse link is low .............................................3-58
198092273 The value of RSSI over reverse link is high ............................................3-59
198092275 PA communication fault..........................................................................3-60
198092276 Receiving RF channel fault ....................................................................3-60
198092278 Abnormal power.....................................................................................3-61
198092279 Downlink analog power exceeds rated value..........................................3-62
198092280 Downlink digital power exceeds rated value ..........................................3-62
198092281 Downlink carrier baseband power is low ................................................3-63
198092282 Downlink carrier analog power is low .....................................................3-64
198092283 Remote antenna VSWR alarm ...............................................................3-64
198092379 PA over power alarm..............................................................................3-65
3-2

Chapter 3 Equipment Alarm
198092364 Calibrate Fail .........................................................................................3-66

198092365 Low Power Exception ............................................................................3-67
198092317 ACOM major alarm ................................................................................3-67
198092318 ACOM minor alarm ................................................................................3-68
198092319 ACOM hardware fault ...........................................................................3-68
198092320 ACOM communication link is interrupted................................................3-69
198092321 ACOM software fault..............................................................................3-70
198092322 AISG EEPROM error .............................................................................3-70
198092323 AISG flash erase error ..........................................................................3-71
198092324 AISG flash error .....................................................................................3-72
198092325 AISG other hardware error.....................................................................3-72
198092326 AISG other software error ......................................................................3-73
198092327 AISG RAM error.....................................................................................3-74
198092328 AISG UART error...................................................................................3-74
198092330 ATMA major alarm .................................................................................3-75
198092331 ATMA minor alarm .................................................................................3-75
198092332 Failed to set gain ...................................................................................3-76
198092333 ATMA hardware fault ............................................................................3-77
198092334 ATMA communication link is interrupted.................................................3-77
198092335 ATMA software fault...............................................................................3-78
198092336 Board configuration parameter error ......................................................3-79
198092337 RET motor fault......................................................................................3-79
198092339 RET hardware fault ................................................................................3-80
198092340 RET motor can't adjust...........................................................................3-80
198092341 RET motor don't response the adjusting command ................................3-81
198092342 RET communication link is interrupted ...................................................3-82
198092343 RET don't calibrated ..............................................................................3-82
198092344 RET data don't scaled ...........................................................................3-83
198092345 RET position lost....................................................................................3-83
198092346 RET software fault .................................................................................3-84
198092374 UCI optical module of optical port is out of position ................................3-85
198092375 UCI optical module of optical port has no light signal .............................3-85
198092376 UCI receiver frame at optical port is unlocked ........................................3-86
198092377 UCI fiber delay adjust is failed................................................................3-87
198092378 Board PLL is unlocked ...........................................................................3-87
198092049 Lightning protection device alarm...........................................................3-88
198092051 PSU alarm .............................................................................................3-89
198092052 PSU fan alarm .......................................................................................3-89
198092068 Main power supply has a fault alarm .....................................................3-90
198092206 Battery alarm .........................................................................................3-90
198092207 AC power-cut alarm ...............................................................................3-91
198092208 Rectifier module alarm ...........................................................................3-92
198092209 Thermoelectric cooler alarm ..................................................................3-92
198092259 Battery low-voltage alarm.......................................................................3-93
198092260 Faulty external device connected at a dry contact ..................................3-94
3-3

LTE Alarm Handling
198092261 Outdoor lightning protection box alarm...................................................3-94

198092262 Breaker alarm in indoor lightning protection box.....................................3-95
198092263 Lightning protection device alarm in indoor lightning protection box ......3-96
198092264 Over-voltage alarm of main power input.................................................3-97
198092265 Main power input power-cut alarm .........................................................3-98
198092266 Under-voltage alarm of main power input...............................................3-99
198092363 Faulty main power alarm .......................................................................3-99
198092267 General fault of main power ................................................................3-100
198092268 PWR monitoring unit alarm .................................................................3-101
198092550 User-defined dry contact alarm 1 .........................................................3-101
198092559 User-defined dry contact alarm 10 .......................................................3-107
198092560 User-defined dry contact alarm 11........................................................3-107
198092564 User-defined dry contact alarm 15 ....................................................... 3-110
3-4


198092073 Embedded power AC-in Switch Off ......................................................3-131
198092074 Embedded power AC Power Off ..........................................................3-132
198092075 Embedded power SPD-C Broken.........................................................3-133
198092076 Embedded power SPD-D Broken.........................................................3-133
198092077 Embedded power AC Under-Volt .........................................................3-134
198092078 Embedded power AC Over-Volt ...........................................................3-135
198092079 Embedded power AC Current Over......................................................3-136
198092116 Embedded power AC Auxiliary Output Switch Off ................................3-136
198092447 Unbalanced AC phase voltage of built-in power ...................................3-137
198092448 High AC phase current of built-in power ...............................................3-138
198092449 Missing AC phase voltage of built-in power .........................................3-138
198092117 Embedded power Rectifier Module Fault..............................................3-139
198092080 Embedded power SMR Over-Vout .......................................................3-140
198092081 Embedded power SMR Over-Iout ........................................................3-140
198092082 Embedded power SMR Fan Fault ........................................................3-141
198092083 Embedded power SMR PFC Fault .......................................................3-142
198092084 Embedded power SMR Over-Vin Off....................................................3-142
198092085 Embedded power SMR Under-Vin Off..................................................3-143
198092086 Embedded power SMR H.T. Off ...........................................................3-143
198092087 Embedded power SMR Env.H.T.Off .....................................................3-144
198092088 Embedded power SMR Env.H.T ..........................................................3-144
198092089 Embedded power SMR L.Vin ...............................................................3-145
198092090 Embedded power SMR Fuse Broken ...................................................3-146
198092091 Embedded power SMR CommFail .......................................................3-146
198092236 Embedded power SMR Output Fault....................................................3-147
198092394 Several faulty rectifiers ........................................................................3-148
198092092 Embedded power DC Under-Volt .........................................................3-148
198092093 Embedded power DC Over-Volt ...........................................................3-149
198092094 Embedded power DC Loop Broken......................................................3-150
198092095 Embedded power Bat Loop Broken......................................................3-150
198092096 Embedded power Bat Under-Volt.........................................................3-151
3-5

LTE Alarm Handling
198092097 Embedded power Bat Over-Temp ........................................................3-152

198092098 Embedded power TmpL Shut-Down ....................................................3-153
198092099 Embedded power 1st Shut-down .........................................................3-153
198092100 Embedded power 2nd Shut-down ........................................................3-154
198092101 Embedded power DC SPD Broken ......................................................3-155
198092102 Embedded power DCBreaker Alarm ....................................................3-156
198092103 Embedded power Bat Test Failure .......................................................3-156
198092104 Embedded power Bat Discharge..........................................................3-157
198092237 Embedded power Bat Under-Temp ......................................................3-158
198092238 Embedded power Bat Invalid-Temp......................................................3-159
198092239 Embedded power Battery Fault............................................................3-159
198092450 Battery low-voltage cut-off of built-in power .........................................3-160
198092451 Broken LLVD1 branch E of built-in power .............................................3-161
198092452 Broken LLVD1 branch of built-in power ...............................................3-162
198092453 Broken LLVD2 branch E of built-in power .............................................3-163
198092454 Broken battery cut-off branch E of built-in power ..................................3-164
198092455 Broken battery cut-off branch of built-in power ....................................3-165
198092456 Abnormal battery current of built-in power ...........................................3-166
198092457 Abnormal CAN bus of built-in power ...................................................3-166
198092458 Abnormal battery of built-in power .......................................................3-167
198092459 Abnormal input dry contact of built-in power ........................................3-168
198092460 High-temperature cut-off of built-in power ............................................3-168
198092234 Embedded power type configuration error............................................3-169
198092235 Embedded power communication interruption......................................3-170
198096550 Alarm of fiber configuration ..................................................................3-170
198096551 RRU unconfigured ..............................................................................3-171
198096552 Difference of fiber time delay of two RRUs in same sector exceeded
system limit ............................................................................................................3-171
198096553 RRU Type is not consistent with configuration type ..............................3-172
198096554 Failure of optical decoding in BBU .......................................................3-172
198096555 Failure of optical decoding in RRU .......................................................3-173
198096556 IQ link input loses lock .........................................................................3-173
198096558 Downlink baseband power abnormal ...................................................3-174
198096559 RRU adjust channel or adjust cable fault..............................................3-175
198096560 Master and slave monitor link alarm.....................................................3-175
198096561 Coherence alarm of antenna channel swing and phase .......................3-176
198096562 RRU self check failed when power on ..................................................3-176
198096563 RRU device alarm................................................................................3-177
198096565 Configurate parameter of RRU external device not consistent with real
parameter...............................................................................................................3-178
198092433 RRU network interrupted alarm............................................................3-178
198092434 Clock line abnormal connection in stack mode.....................................3-179
198092435 Inter-frame Ethernet link broken in stack mode ...................................3-179
198092436 Loss of clock synchronization at slave frame........................................3-180
198092437 RRU radio frequency group unavailable...............................................3-181
3-6

198092438 Device in low temperature....................................................................3-181

198092439 Uplink transport port of a base station operates in a different mode from
configured one .......................................................................................................3-182
198092461 BBU inter-subrack frame synchronization failure alarm .......................3-183
198098431 Abnormal current alarm at NSBT port .................................................3-184
198098432 AISG/NSBT port turn-off alarm due to over current ..............................3-185
198098434 Abnormal transmission power at antenna port ....................................3-186
198098435 Closed-loop power control adjustment exceeding normal range...........3-186
198098436 Failure in configuring power level .........................................................3-187
198096568 RRU used power module is too hot......................................................3-188
198096569 RRU offline parameter check failure ....................................................3-188
198100270 Optical signals transmitted from BBU to RRU carry wrong clock
information .............................................................................................................3-189
198100271 Unlocked local oscillator alarm of RRU ................................................3-189
198100272 RRU inside clock unlocked ..................................................................3-190
198100273 Downlink channel fault alarm ...............................................................3-191
198100274 Downlink output power abnormal .........................................................3-191
198098438 The internal power module in a RRU detects invalid lightning protection
circuit .....................................................................................................................3-192
198094412 Fault in BPL clock ...............................................................................3-193
198094413 Fault in BPL hardware .........................................................................3-194
198094414 Discontinuous frame number ...............................................................3-194
198094415 Frame frequency abnormal ..................................................................3-196
198094425 Optical module temperature is abnormal..............................................3-197
198094426 Optical module bias current is abnormal ..............................................3-198
198094427 Optical module transmit power is abnormal..........................................3-199
198094428 Optical module inner voltage is abnormal.............................................3-199
198098439 ATMA works in bypass mode ...............................................................3-200
3.1 198092214 Hardware of Clock Module Fault

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 backboard's serdes clock is lost, the alarm is reported.
4-Frame synchronization signal error
The alarm is reported when backboard can not detected the signal.
5-clock between partner boards abnormal.
3-7

LTE Alarm Handling
Standby board or master board is each other's partner board, the alarm is reported when either of
them cannot receive clock which is send by partner board.
6-data between partner boards abnormal.
Standby board or master board is each other's partner board, the alarm is reported when data which
is received from partner has problem.
7-phase clock is lost
Phase clock refers to clock of soft PLL phase detector, the alarm is reported when phase clock is lost
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
I. Board Status:
Board is fault.
II. Service influence:
When master board is fault, system cannot work normally and the corresponding 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 can not be executed when master board is fault. It
reduces the system reliability.
Probable Cause
None
Handling Suggestion
l 10M clock lost

1. Reset board.
2. Plug board.
l Serdes clock PLL lost
1. Reset board.
2. Check if the running version is correct.
3. Plug board.
l Serdes clock lost
1. Reset board.
3. Plug board.
4. Change the main control board to another main control board slot.
3-8

l Frame synchronization signal is wrong

1. Reset board.
3. Plug board.
4. Change CC slot.
l Phase clock lost
1. Reset board.
2. Plug board.
l PLL clock of net port is lost
1. Reset board.
3. Plug board.
l PLL of net port is lost
1. Reset board.
2. Plug board.
3.2 198092215 Lost of synchronization

1. OCXO can not lock

Under the condition of reference source 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
Control voltage is beyond the range.
Severity
Major
System Impact
I. Board Status:
Board is fault.
when master board is fault, system can not work normally and the corresponding clock module of the
outer board is alarm. It causes 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.
3-9

LTE Alarm Handling
Probable Cause
1. The problem of crystal.

2. Board is fault.
Handling Suggestion
OCXO can not lock:

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 can not 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.
4. If it can not 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.3 198092241 1588 clock source unavailable

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-10

3.4 198092216 1PPS Of Current Reference Clock is Lost

1PPS Of Current Reference Clock is 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 panel receiver, outer panel receiver does not output 1PPS signal.
3. For the 1588, the 1588 processor does not output 1PPS signal.
Handling Suggestion
1. Check whether the configured referent signal is in accordance with real signal.
2. Check whether the running version in the board is correct.
3. Reset the board.
4. Pull and push the board.
3.5 198092217 Air Interface Clock Unavailable

When air interface clock isn't configured, 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
System Impact
I. Board Status:
Board run normally.
Services in the board are interrupted completely.
3-11

LTE Alarm Handling
Probable Cause
1. Does not configure the air interface clock source.

2. The air interface clock source cannot be lock (clock source interrupted seriously, beyond adjust
threshold of crystal oscillator, or crystal oscillator fault).
Handling Suggestion
Check whether the air interface clock source is configured.

l If it is not configured, do it and observe.
l 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.6 198092415 Inner GNSS receiver has an alarm

This alarm is reported when the inner GNSS receiver has a fault or is unavailable.
Severity
Critical
System Impact
I. Board Status:
Work normally.
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 receiver

(1) Reset the board.
(2) Replace the board.
3-12

3.7 198092416 Inner GNSS antenna has a cable alarm

This alarm is reported when the inner GNSS's antenna has a faulty cable.
Severity
Major
System Impact
I. Board Status:
Work normally.
Probable Cause
GNSS receiver's antenna cable is faulty.
Handling Suggestion
Check the faulty antenna cable.

(1) Check the connection of GNSS antenna cable.
(2) Reconnect or replace the GNSS antenna feeder.
3.8 198092418 Outer Facepanel GNSS receiver has an

alarm
This alarm is reported when one of the following situations happens in the configuration of Outer
Facepanel GNSS reference source.
(1) RGPS receiver has no electricity supply.
(2) The receiver is faulty or the link to Outer Facepanel GNSS receiver is interrupted.
(3) The environmental temperature of RGPS receiver is abnormal.
Severity
Minor
3-13

LTE Alarm Handling
System Impact
I. Board Status:
Work normally.
II. Impact on services:
Probable Cause
1. RGPS receiver has a power cut problem.

2. The receiver is broken, or the link between Outer Facepanel GNSS receiver and the main control
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 Outer Facepanel GNSS receiver and CC is normal.
3. Check whether environmental temperature is normal (for example, is there any high-heat
large-power device?)
3.9 198092419 Outer Facepanel GNSS antenna has a

cable alarm
This alarm is reported when the Outer Facepanel GNSS receiver has a faulty cable.
Severity
Major
System Impact
I. Board Status:
Work normally.
Probable Cause
Outer Facepanel GNSS receiver has a faulty antenna cable.
3-14

Handling Suggestion

(1) Check the connection of antenna cable.
(2) Reconnect or replace the antenna cable.
3.10 198092422 Outer Backpanel GNSS receiver has

an alarm
This alarm is reported when one of the following situations happens in the configuration of Outer
Backpanel GNSS reference source.
(1) RGPS receiver has no electricity supply.
(2) The receiver is faulty or the link to Outer Backpanel GNSS receiver is interrupted.
(3) The environmental temperature of RGPS receiver is abnormal.
Severity
Minor
System Impact
I. Board Status:
Work normally.
Probable Cause
1. RGPS receiver has a power cut problem.

2. The receiver is broken, or the link between Outer Backpanel GNSS receiver and the main control
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?)
3-15

LTE Alarm Handling
3.11 198092423 Outer Backpanel GNSS antenna has

a cable alarm
This alarm is reported when Outer Backpanel GNSS receiver has a faulty cable.
Severity
Major
System Impact
I. Board Status:
Work normally.
Probable Cause
Outer Backpanel GNSS receiver has a faulty antenna cable.
Handling Suggestion

(1) Check the connection of antenna cable.
(2) Reconnect or replace the antenna cable.
3.12 198092426 GNSS cascading clock has an alarm

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

System Impact
I. Board Status:
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.13 198092008 FPGA register read/write error

None
Severity
Major
System Impact
I. Board Status:
The board is faulty.
II. 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.
3-17

LTE Alarm Handling
Handling Suggestion
1. Check whether the board has over-temperature alarm, if yes, handle the alarm first.
2. Reset the board.
3.14 198092298 MMC Fault

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

2. MMC is broken.
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.15 198092057 The board is powered off

The board is powered off.
Severity
Major
3-18

System Impact
I. Board Status:
II. 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 whether the board has an over-temperature alarm, if yes, handle the alarm first.
2. 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
3. Turn on the board's power supply.
3.16 198092072 Board not-in-position

This alarm is reported when the board is configured in the network management interface but actually
is not inserted in the slot.
Severity
Major
System Impact
I. Board Status:
II. Impact: on Service:
The board can't bear any service.
3-19

LTE Alarm Handling
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. Remove and insert the board;
3. Replace the shelf.
3.17 198092203 Board not-configured alarm

This alarm is reported when a board is not configured in network management interface, but it
is inserted into a real slot.
Severity
Minor
System Impact
I. Board Status:
The board is not configured.
There is no influence on services.
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-20

3.18 198092400 Board smart powered-down

During energy-saving period, partial boards are powered down because of fewer services.
Severity
Warning
System Impact
I. Board Status:
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.19 198092009 Ethernet access network interface

abnormal
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
3-21

LTE Alarm Handling
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.
l If it is constantly ON, it indicates that the physical connection is normal.
l If it flashes, it indicates that there is data being transmitted/received.
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.
l When the connecting cable is extracted, the Ethernet interface's connection indicator is OFF.
l When the connecting cable is inserted, the Ethernet interface's connection indicator is constantly
ON or flashes.
4. Extract and insert the board.
3.20 198092011 E1/T1 input port unavailable

The main control 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.
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-22

3.21 198092012 E1/T1 output port unavailable

The main control 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,
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.22 198092013 ES or SES detected on the E1 link in

the past 15 minutes has exceeded the threshold
The main control 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
3-23

LTE Alarm Handling
System Impact
None
Probable Cause
None
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.23 198092401 E1 link self-loop

E1 link self-loop is detected.
Severity
Major
System Impact
I. Board Status:
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-24

3.24 198092311 IQ reported is failed

The alarm is reported in the main control board when product process fails to report IQ.
Severity
Minor
System Impact
I. Board Status:
None.
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 Optical Signal Output Interface Board and RRU.
Handling Suggestion
1. Reconfigure TDM speed or Opt speed.

2. Check radio Mode.
3. Reconfigure protocol of Optical Signal Output Interface Board or RRU.
3.25 198092383 Distributing IQ resource is failed

The alarm is reported when calculating IQ ranks is failed in the main control board.
Severity
Minor
System Impact
I. Board Status:
3-25

LTE Alarm Handling
Probable Cause
1. Input parameter is not valid.

2. Bandwidth is not enough.
Handling Suggestion
Reconfigure IQ on configuration management interface of OMCB.
3.26 198092384 IQ configuration failure

The alarm is reported when it is failed to configure IQ parameters for the Optical Signal Output
Interface Board.
Severity
Minor
System Impact
I. Board Status:
Probable Cause
1. Input parameter is not valid.

2. Bandwidth is not enough.
Handling Suggestion
Reconfigure IQ on configuration management interface of OMCB.
3.27 198092385 Optical port speed configuration failure

The alarm is reported when optical port speed configuration is failed in Optical Signal Output Interface
Board.
3-26

Severity
Minor
System Impact
I. Board Status:
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.28 198092386 TDM port speed configuration failure

The alarm is reported when it is failed to configure TDM port speed for the Optical Signal Output
Interface Board.
Severity
Minor
System Impact
I. Board Status:
Probable Cause
TDM port speed is not valid.
Handling Suggestion
Reconfigure TDM port speed on configuration management interface of OMCB.
3-27

LTE Alarm Handling
3.29 198092387 RRU device delay parameter

configuration failure
The alarm is reported when it is failed to configure RRU device delay parameter for the Optical
Signal Output Interface Board.
Severity
Minor
System Impact
I. Board Status:
It will effect fiber-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.30 198092388 Power supply configuration failure

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
System Impact
I. Board Status:
It will effect board power supply.
It will not affect service.
3-28

Probable Cause
1. Power supply configuration is failed when the total power of all the board configurated in OMCB
exceeds available power of PM.
2. Product process is not loaded so that the system cannot obtain board power information.
Handling Suggestion
Reconfigure power supply on configuration management interface of OMCB.
3.31 198092032 Failed to operate Database

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.32 198092219 Baseband Subunit Fault

When main core can't receive the slave's heartbeat in a while, alarm is reported.
3-29

LTE Alarm Handling
Severity
Critical
System Impact
Base band subunit cannot work normally.
Probable Cause
Base band subunit has fault.
Handling Suggestion
Reset the board.
3.33 198092071 Abnormal temperature sensor

This alarm is reported when the temperature sensor is abnormal.
Severity
Warning
System Impact
I. Board Status:
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.
3-30

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

I. Extract and insert the fan board.
II. Replace the fan board.
à 2. Temperature sensor at wind outlet is abnormal.
I. Replace board.
3.34 198092352 Unmatched link mode at peer-end

electrical port of Ethernet
This alarm is reported when Electrical Ethernet port at local end works in different mode from that at
peer end.
Severity
Warning
System Impact
I. Board Status:
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.
3-31

LTE Alarm Handling
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.35 198092393 UES ethernet semiduplex alarm

Link is in semiduplex status.
Severity
Major
System Impact
I. Board Status:
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 link mode configuration.
3.36 198092353 Configuration is failed

Configuration is failed.
Severity
Major
System Impact
Impact configuration
3-32

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.37 198092212 EPLD's register has a R/W failure alarm

EPLD register R/W test fails. It is explained as: CPU reads/writes to/from EPLD register, this
operation returns a value, but the value is different from configured value.
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.38 198092284 Input reference clock is abnormal

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

LTE Alarm Handling
System Impact
I. Board Status:
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.39 198092285 Internal clock is abnormal

This alarm is reported when FPGA main clock and Serdes reference clock signals on board are
abnormal.
Severity
Critical
System Impact
I. Board Status:
Work normally
System services are interrupted.
Probable Cause
The internal clock is abnormal.
3-34

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.40 198092286 The uplink frame at optical/electric port

is unlocked
This alarm is reported when the uplink frame at optical/electric port is unlocked.
Severity
Critical
System Impact
I. Board Status:
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 -18 dbm. If yes, please check whether the RRU is powered on.
3-35

LTE Alarm Handling
3.41 198092287 The channel downlink frame is

unlocked
This alarm is given when channel downlink TDM frame is unlocked, i.e. failure in detecting TDM
frame header.
Severity
Critical
System Impact
I. Board Status:
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;
6. Remove and insert the board;
3.42 198092288 The PLL clock is unlocked

This alarm is reported when PLL chip cannot output FPGA main clock or Serdes reference clock
due to unlocked PLL.
3-36

Severity
Critical
System Impact
I. Board Status:
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.43 198092289 The optical/electric module is not in

the position of optical port
This alarm is reported when optical/electric port is not well connected.
Severity
Minor
System Impact
I. Board Status:
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.
3-37

LTE Alarm Handling
Handling Suggestion

3.44 198092290 The uplink optical/electric link is

interrupted
This alarm is reported when optical port has detected LOS or the value of cable LCV exceeds its
threshold.
Severity
Critical
System Impact
I. Board Status:
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.
Handling Suggestion
1. Check whether there is a RRU alarm, which is not "not detected" type. If yes, process it.
3. Check whether the optical fiber/electrical cable between BBU and RRU is well connected.
3-38

3.45 198092291 The input frame synchronous signal

is wrong
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
System Impact
I. Board Status:
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.46 198092292 An alarm is given when an optical fiber

is wrongly connected
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-39

LTE Alarm Handling
System Impact
I. Board Status:
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.
than -18 dbm. If yes, please check the corresponding transmission link.
3.47 198092295 RRU power-cut alarm

The alarm is reported when RRU detects that power voltage is lower than a certain value.
Severity
Critical
System Impact
I. Board Status:
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.
3-40

Handling Suggestion
1. Check whether the power cable at RRU side is abnormal.

2. Check whether the external power device has a fault.
3.48 198092242 Ir link LCV alarm

Ir link LCV(line code violation) error exceeds threshold, this alarm is reported.
Severity
Warning
System Impact
I. Board Status:
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.
i. 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.
l 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.
l 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.
ii. Replace the fiber optics.
2. Check the fiber optics between the boards for possible damage. Replace the fiber if any damage is
found.
3-41

LTE Alarm Handling
3.49 198092258 Lost of frame rate and frame number

Discontinuous frame number alarm, frame rate not received alarm within 160 ms.
Severity
Minor
System Impact
I. Board Status:
Work normally.
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 160 ms.
Handling Suggestion
Replace the optical module/fiber of FS functionality board. Replace the optical module used by
the faulty optical port.
3.50 198092248 Optical module out-of-position alarm

Optical module out-of-position.
Severity
Minor
System Impact
I. Board Status:
The board is normal.
If port 0, board communication link is down. If port 1, the next board on the service is down.
3-42

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.51 198092293 The Rx optical port at RRU has no light

signal
The alarm will be reported when the receiving optical port of RRU in the chain has no optical signal
received.
Severity
Critical
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

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 -18 dbm.
3-43

LTE Alarm Handling
3.52 198092294 The frame transferred over Rx port of

RRU is unlocked
The alarm will be reported when the CPRI frame of RRU in the chain is unlocked.
Severity
Critical
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.
Handling Suggestion

3.53 198092254 Remote output power abnormal

voltage alarm
The output voltage of power module is abnormal.
Severity
Major
3-44

System Impact
I. Board Status:
The board or system may not work properly.
The services borne on the board are interrupted.
Probable Cause
Power module output is abnormal.
Handling Suggestion
1. Check input voltage of the power module. If the value is out of a normal range, replace input power
module. Otherwise, skip to step 2.
2. Power off, then reset the RU.
3. Replace the RU.
3.54 198092255 Remote input power over-voltage alarm

The input AC voltage of power module is higher than alarm threshold, or the direct current voltage of
power module is higher than alarm threshold.
Severity
Major
System Impact
I. Board Status:
Board Operation is normal.
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, or the direct current voltage of
power module is higher than alarm threshold.
3-45

LTE Alarm Handling
Handling Suggestion
1. The AC input voltage of power module is higher than the alarm threshold.
i. Shut down the RRU and disconnect it from power socket. Check whether the voltage of the AC
input is higher than alarm threshold.
ii. Replace the voltage module RPWDC of RRU.
2. The DC input voltage of power module is higher than the alarm threshold.
i. Shut down the RRU and disconnect it from power socket. Check whether the voltage of the DC
input is higher than alarm threshold.
3.55 198092256 Remote input power under-voltage

alarm
The input AC voltage of power module is lower than alarm threshold, or the direct current voltage of
power module is lower than alarm threshold.
Severity
Major
System Impact
I. Board Status:
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, or the direct current voltage of
power module is lower than alarm threshold.
3-46

Handling Suggestion
1. The AC input voltage of power module is lower than the alarm threshold.
i. Shut down the RRU and disconnect it from power socket. Check whether the voltage of the AC
input is lower than alarm threshold.
2. The DC input voltage of power module is lower than the alarm threshold.
i. Shut down the RRU and disconnect it from power socket. Check whether the voltage of the DC
input is lower than alarm threshold.
3.56 198092269 Over-high temperature of RRU board

The temperature of RRU exceeds over-high temperature threshold.
Severity
Critical
System Impact
I. Board Status:
The board is faulty
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.
Handling Suggestion
l High environmental temperature:

1. Make sure the indoor air conditioner works properly.
2. Make sure the fan runs normally.
l RRU fault:
1. Replace the PA.
3-47

LTE Alarm Handling
3.57 198092270 Slight-high temperature of RRU board

The temperature of RRU exceeds slight-high temperature threshold.
Severity
Major
System Impact
I. Board Status:
Work normally.
The PA reduces its RF channel transmission power by 2 db.
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.
Handling Suggestion

l RRU fault:
1. Replace the PA.
3.58 198092247 Over-high temperature of PA

The temperature of PA exceeds over-high temperature threshold.
Severity
Critical
3-48

System Impact
I. Board Status:
Work normally.
The PA output is closed so that its corresponding RF channel has no output power. Consequently, all
Probable Cause
1. The fan at PA layer is abnormal, which causes a cooling fault.

2. PA is abnormal.
Handling Suggestion
l High environmental temperature

l RRU fault:
1. Replace the PA.
3.59 198092274 Slight-high temperature of PA

The temperature of PA exceeds slight-high temperature threshold.
Severity
Major
System Impact
I. Board Status:
Work normally.
The PA reduces its RF channel transmission power by 2 db.
Probable Cause
1. The fan at PA layer is abnormal, which causes a cooling fault.

2. PA is abnormal.
3-49

LTE Alarm Handling
Handling Suggestion

l RRU fault:
1. Replace the PA.
3.60 198092245 Disable PA

This alarm is given when it detects that PA is in the closed status.
Severity
Minor
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-50

(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.61 198092249 RF board PLL alarm

RF board has detected that PLL is not locked.
Severity
Critical
System Impact
I. Board Status:
Work normally
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-51

LTE Alarm Handling
3.62 198092277 Clock module fault

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
System Impact
I. Board Status:
Work normally.
l 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.
l 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.
Probable Cause
Hardware has fault.
Handling Suggestion
1. Reset the board.

2. Plug/unplug the board.
3.63 198092243 Abnormal DPD running status

DPD running status is abnormal.
Severity
Warning
3-52

System Impact
I. Board Status:
Board Operation is normal
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.64 198092244 LNA alarm

When working voltage or gain of LNA is out of normal working range, the system will give this alarm.
Severity
Major
System Impact
I. Board Status:
Board Operation is normal
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-53

LTE Alarm Handling
3.65 198092246 TMA channel input is over current

This alarm is reported when the system detects that TMA channel input current is over threshold
(135~140 mA), but less than 200mA.
Severity
Major
System Impact
I. Board Status:
Work normally.
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.66 198092250 Calibration file on TRx board is

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

System Impact
I. Board Status:
Work normally.
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 calibration data associated to this board is missing or damaged.
Handling Suggestion
1. Reset board.
2. Replace board.
3.67 198092251 a block check error of downlink IQ

channel alarm
DL IQ channel is error in receiving data.
Severity
Major
System Impact
I. Board Status:
Downlink communication is abnormal from UBPG to RRU.
Probable Cause
Downlink IQ channel receives wrong data.
3-55

LTE Alarm Handling
Handling Suggestion
1. Check if the following alarm (clock abnormal) occurs in BBU.

Related alarms:
198092277 Clock module fault
198092249 RF board PLL alarm
2. Reset board.
3.68 198092252 Downlink digital IF pre-distortion alarm

Digital IF pre-distortion fault.
Severity
Major
System Impact
I. Board Status:
Work normally.
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:
198092278 Abnormal power
198092283 Antenna VSWR alarm
198092257 Remote antenna over VSWR alarm
198092283 Remote antenna VSWR alarm
2. Reset RF board.
3. Replace RF board.
3-56

3.69 198092253 Application software monitoring alarm

RRU doesn't send a heart-beat message to BBU.
Severity
Critical
System Impact
I. Board Status:
Work normally.
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. 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. 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.70 198092257 Remote antenna over VSWR alarm

VSWR at antenna port is higher than limit (2.5~3.0).
Severity
Major
3-57

LTE Alarm Handling
System Impact
I. Board Status:
Work normally.
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.

2. Check the feeder standing waves of each level.
normal.
3. Check the RRU for possible failure.
i. Reset the board.
iii. Check the power amplifier for possible failure. Replace the power amplifier in case of any damage.
3.71 198092272 The value of RSSI over reverse link is

low
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.
3-58

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.72 198092273 The value of RSSI over reverse link is

high
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.
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-59

LTE Alarm Handling
3.73 198092275 PA communication fault

This alarm is reported when the communication between PA and monitoring module is failed.
Severity
Critical
System Impact
I. Board Status:
Work normally.
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.
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.74 198092276 Receiving RF channel fault

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
3-60

System Impact
I. Board Status:
Work normally.
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.
Handling Suggestion
1. Reset the board.

3.75 198092278 Abnormal power

After cell setup, the TRx board will report this alarm when it detects that the absolute difference
between digital power and analog power exceeds threshold (>6 dB).
Severity
Major
System Impact
I. Board Status:
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-61

LTE Alarm Handling
3.76 198092279 Downlink analog power exceeds rated

value
This alarm is given when analog power exceeds rated power by 0.1~1 dB for above 20 times.
Severity
Critical
System Impact
I. Board Status:
Work normally.
Because PA output is closed, this RF channel doesn't output transmission power. As a result, all
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.77 198092280 Downlink digital power exceeds rated

value
The system will give this alarm when high layer software has detected that digital power exceeds
rated power (see notes) by 0.1~1 dB for 20 times within one minute.
Severity
Critical
3-62

System Impact
I. Board Status:
Work normally.
Because PA output is closed, this RF channel doesn't output transmission power. As a result, all
Probable Cause
1. Input digital signal from BBU is wrong.

2. RRU software is abnormal.
3. RRU hardware is abnormal.
Handling Suggestion
1. Reset board.
2. Replace board.
3.78 198092281 Downlink carrier baseband power is

low
The system will give this alarm when high layer software has detected that digital power exceeds
rated power (see notes) by 0.1~1 dB 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.
3-63

LTE Alarm Handling
Handling Suggestion
1. Reset board.
2. Replace board.
3.79 198092282 Downlink carrier analog power is low

This alarm is given when carrier analog power exceeds rated power by 0.1~1 dB 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.80 198092283 Remote antenna VSWR alarm

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

System Impact
I. Board Status:
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.

2. Check the feeder standing waves of each level.
normal.
3. Check the RRU for possible failure.
i. Reset the board.
iii. Check the amplifier for possible failure. Replace the power amplifier in case of any damage.
3.81 198092379 PA over power alarm

The output power of PA exceeds rated power by 2~3 dB.
Severity
Critical
3-65

LTE Alarm Handling
System Impact
I. Board Status:
Work normally.
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.
Handling Suggestion
1. Reset the board.

3.82 198092364 Calibrate Fail

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-66

3.83 198092365 Low Power Exception

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.84 198092317 ACOM major alarm

When ACOM major alarm , this alarm is reported.
Severity
Major
System Impact
Impact on Service:
Major fault occurs in ACOM, which might cause the performance of corresponding cell to degrade.
Probable Cause
ACOM major fault.
3-67

LTE Alarm Handling
Handling Suggestion
1. Reset the equipment.

2. Replace the equipment.
3.85 198092318 ACOM minor alarm

When ACOM minor alarm , this alarm is reported.
Severity
Minor
System Impact
Impact on Service:
Minor fault occurs in ACOM, which might cause the performance of corresponding cell to degrade.
Probable Cause
ACOM minor fault.
Handling Suggestion

3.86 198092319 ACOM hardware fault

When ACOM hardware has a fault, this alarm is reported.
Severity
Major
System Impact
Service Impact:
ACOM operation is abnormal, which might cause the performance of corresponding cell to degrade.
3-68

Probable Cause
Parameter error.
Handling Suggestion
1. Reset the associated RRU board.

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

interrupted
When ACOM communication link is interrupted, this alarm is reported.
Severity
Major
System Impact
Impact on Service:
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-69

LTE Alarm Handling
3.88 198092321 ACOM software fault

When ACOM software has a fault, this alarm is reported.
Severity
Major
System Impact
Service Impact:
ACOM operation is abnormal, and the configuration will not take effect, which might cause the
performance of corresponding cell to degrade.
Probable Cause
Parameter error.
Handling Suggestion
1. Reset the associated RRU board.

3.89 198092322 AISG EEPROM error

When AISG EEPROM is error, this alarm is reported.

AISG device type:
RET 1
ATMA 2
ACOM 241
Severity
Minor
System Impact
I. Impact on Service:
AISG operation is abnormal, which might cause the performance of corresponding cell to degrade.
3-70

Probable Cause
Parameter error.
Handling Suggestion

3.90 198092323 AISG flash erase error

When AISG flash erase error, this alarm is reported.

AISG device type:
RET 1
ATMA 2
ACOM 241
Severity
Minor
System Impact
Probable Cause
Parameter error
Handling Suggestion

3-71

LTE Alarm Handling
3.91 198092324 AISG flash error

When AISG flash write error, this alarm is reported.

AISG device type:
RET 1
ATMA 2
ACOM 241
Severity
Minor
System Impact
I. Service Impact:
Probable Cause
Parameter error
Handling Suggestion

3.92 198092325 AISG other hardware error

When AISG other hardware has a error, this alarm is reported.

AISG device type:
RET 1
ATMA 2
ACOM 241
Severity
Minor
3-72

System Impact
Probable Cause
Parameter error
Handling Suggestion

3.93 198092326 AISG other software error

When AISG other software has a error, this alarm is reported.

AISG device type:
RET 1
ATMA 2
ACOM 241
Severity
Minor
System Impact
Probable Cause
Parameter error
Handling Suggestion

3-73

LTE Alarm Handling
3.94 198092327 AISG RAM error

When AISG RAM is error, this alarm is reported.

AISG device type:
RET 1
ATMA 2
ACOM 241
Severity
Minor
System Impact
Probable Cause
Parameter error
Handling Suggestion

3.95 198092328 AISG UART error

When AISG UART is error, this alarm is reported.

AISG device type:
RET 1
ATMA 2
ACOM 241
Severity
Minor
3-74

System Impact
Probable Cause
Parameter error
Handling Suggestion

3.96 198092330 ATMA major alarm

When ATMA major alarm, this alarm is reported.
Severity
Major
System Impact
Major fault occurs in ATMA, which might cause the performance of corresponding cell to degrade.
Probable Cause
ATMA major fault
Handling Suggestion

3.97 198092331 ATMA minor alarm

When ATMA minor alarm, this alarm is reported.
3-75

LTE Alarm Handling
Severity
Minor
System Impact
Minor fault occurs in ATMA, which might cause the performance of corresponding cell to degrade.
Probable Cause
ATMA minor fault
Handling Suggestion

3.98 198092332 Failed to set gain

This alarm is reported when it is failed to set ATMA gain.

AISG device type:
RET 1
ATMA 2
ACOM 241
Severity
Major
System Impact
I. Board Status:
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.
3-76

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.99 198092333 ATMA hardware fault

When ATMA hardware has a fault, this alarm is reported.
Severity
Major
System Impact
Service Impact:
ATMA works abnormally, which might cause the performance of corresponding cell to degrade.
Probable Cause
Parameter error
Handling Suggestion
Reset EMC.
3.100 198092334 ATMA communication link is

interrupted
When ATMA communication link is interrupted, this alarm is reported.
Severity
Major
3-77

LTE Alarm Handling
System Impact
Impact on Service:
The system fails to communicate with ATMA device. If link interruption is caused by device damage,
performance of the corresponding cell will be degraded.
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
3.101 198092335 ATMA software fault

When ATMA software has a fault, this alarm is reported.
Severity
Major
System Impact
Service Impact:
ATMA works abnormally, which might cause the performance of corresponding cell to degrade.
Probable Cause
Parameter error.
Handling Suggestion
Reset EMC.
3-78

3.102 198092336 Board configuration parameter error

During the period of starting configuration or board running, this alarm is reported if a wrong
configuration parameter is found. This configuration parameter is delivered from main control board.
Severity
Major
System Impact
I. Board Status:
II. Service Impact:
The service on the board is down.
Probable Cause
1. The system has no such board configuration parameter.

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

When RET motor has a fault, this alarm is reported.
Severity
Major
System Impact
Impact on Service:
Operation of RET motor is down, which might cause the performance of corresponding cell to degrade.
Probable Cause
RET motor fault.
3-79

LTE Alarm Handling
Handling Suggestion
1. Open the Base station Configuration Management window, open AISG 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.104 198092339 RET hardware fault

When RET hardware has a fault, this alarm is reported.
Severity
Major
System Impact
I. Service Impact:
RET motor works abnormally, which might cause the performance of corresponding cell to degrade.
Probable Cause
1. RET hardware fault.

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

When RET motor can't adjust, this alarm is reported.
Severity
Major
3-80

System Impact
Impact on Service:
Probable Cause
RET motor can't adjust.
Handling Suggestion
management, select automatic calibrate the RET equipment again.
2. Remount the RET motor.
3.106 198092341 RET motor don't response the

adjusting command
When RET don't response the adjusting command, this alarm is reported.
Severity
Minor
System Impact
Impact on Service:
Probable Cause
RET motor don't response the adjusting command.
Handling Suggestion
3-81

LTE Alarm Handling
3.107 198092342 RET communication link is interrupted

When AISG device communication link is interrupted, this alarm is reported.
Severity
Major
System Impact
The system fails to communicate with AISG device, and fails to perform management and alarm
detection. If link interruption is caused by device damage, performance of the corresponding cell
will be degraded.
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
3.108 198092343 RET don't calibrated

When RET don't calibrated, this alarm is reported.
Severity
Major
System Impact
Operation of RET motor is down. Thus the configuration cannot take effect.
3-82

Probable Cause
RET don't calibrated
Handling Suggestion
3.109 198092344 RET data don't scaled

When RET data don't scaled, this alarm is reported.
Severity
Major
System Impact
Probable Cause
RET data don't scaled
Handling Suggestion
management, select send the configuration data for the RET equipment again.
2. Replace the motor.
3.110 198092345 RET position lost

When RET position lost, this alarm is reported.
3-83

LTE Alarm Handling
Severity
Minor
System Impact
Probable Cause
RET position lost
Handling Suggestion
2. Remount the motor and calibrate it automatically.
3. Replace the motor.
3.111 198092346 RET software fault

When RET software has a fault, this alarm is reported.
Severity
Major
System Impact
I. Service Impact:
RET motor works abnormally, which might cause the performance of corresponding cell to degrade.
Probable Cause
Parameter error.
Handling Suggestion
Check the system parameters.
3-84

3.112 198092374 UCI optical module of optical port is

out of position
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.113 198092375 UCI optical module of optical port has

no light signal
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-85

LTE Alarm Handling
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;

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

unlocked
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;

4. Replace the optical module corresponding to the board;
5. Check whether the power of received light is less than -18 dbm,if less than -18 dbm please
check the fibers link.
3-86

3.115 198092377 UCI fiber delay adjust is failed

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.
Handling Suggestion
1. Check whether the antenna of RGPS is normal.

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

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.
3-87

LTE Alarm Handling
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.117 198092049 Lightning protection device alarm

This alarm is reported when the lightning protection device has a fault due to lightning attack, not well
grounded or ageing failure.
Severity
Minor
System Impact
I. Board Status:
Work normally.
The power interface cannot be protected from lightning attack.
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-88

3.118 198092051 PSU alarm

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.119 198092052 PSU fan alarm

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-89

LTE Alarm Handling
3.120 198092068 Main power supply has a fault alarm

When the system detects that external main power supply has a fault, this alarm is reported through
dry contact.
Severity
Major
System Impact
I. Board Status:
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.
Handling Suggestion
1. Replace main power supply.

2. Reset the board.
3. Replace the relevant dry contact cable.
4. Replace the board .
3.121 198092206 Battery alarm

This alarm is reported when the system detects that the external battery at a dry contact is faulty.
Severity
Minor
3-90

System Impact
I. Board Status:
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.

Handling Suggestion
configured.
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.122 198092207 AC power-cut alarm

This alarm is reported when the main power is cut.
Severity
Minor
System Impact
I. Board Status:
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.
3-91

LTE Alarm Handling
Handling Suggestion
2. Start diesel engine in an emergency.
3. Restore AC power as soon as possible.
3.123 198092208 Rectifier module alarm

This alarm is reported when the rectifier works abnormally.
Severity
Minor
System Impact
I. Board Status:
Work normally.
Power cannot be normally supplied so that the system paralyzes and services are interrupted.
Probable Cause
1. The dry contact is disconnected.

2. The rectifier module works abnormally.
Handling Suggestion
2. Replace the rectifier module.
3.124 198092209 Thermoelectric cooler alarm

This alarm is reported when the thermoelectric cooler is faulty.
Severity
Minor
3-92

System Impact
I. Board Status:
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.

Handling Suggestion
1. Check whether the thermoelectric cooler is broken. If yes, please replace it.
2. Replace the cable connected the thermoelectric cooler.
3. Replace board.
3.125 198092259 Battery low-voltage alarm

This alarm is reported when the battery is under voltage.
Severity
Minor
System Impact
I. Board Status:
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.
Handling Suggestion
2. Charge the battery as soon as possible and wait until it restores to normal voltage.
3-93

LTE Alarm Handling
3.126 198092260 Faulty external device connected at

a dry contact
This alarm is reported when the external device at a dry contact is faulty.
Severity
Minor
System Impact
I. Board Status:
Work normally.
It doesn't affect services.
Probable Cause
Locate the alarm cause according to real external devices.
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.127 198092261 Outdoor lightning protection box

alarm
Outdoor lightning protection box is faulty.
Severity
Minor
3-94

System Impact
I. Board Status:
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.
Handling Suggestion
configured.
3. Replace the cable that is connected between RRU and outdoor lightning protection box.
5. Replace RRU.
3.128 198092262 Breaker alarm in indoor lightning

protection box
The breaker in an indoor lightning protection box is protected against over current or turns in open
circuit.
Severity
Major
System Impact
I. Board Status:
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.
3-95

LTE Alarm Handling
Probable Cause
1. The breaker is protected against over current or turns in open circuit.

Handling Suggestion
configured.
3. Check the status of the breaker. Find out the reason for over-current protection or open circuit,
then solve the problem.
4. Replace the breaker.
5. Reset the board.
3.129 198092263 Lightning protection device alarm in

indoor lightning protection box
The lightning protection device in an indoor lightning protection box has a fault.
Severity
Minor
System Impact
I. Board Status:
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-96

Handling Suggestion
configured.
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.130 198092264 Over-voltage alarm of main power

input
This alarm is reported when the system detects that input voltage of the main power at dry contact is
abnormal.
Severity
Major
System Impact
I. Board Status:
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.
3-97

LTE Alarm Handling
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
3. Reset the board.
3.131 198092265 Main power input power-cut alarm

This alarm is reported when the system detects that main power input at dry contact is abnormal.
Severity
Major
System Impact
I. Board Status:
Work normally.
Probable Cause

Handling Suggestion
configured.
3. Check whether input voltage of the main power module is abnormal. If yes, replace it.
4. Reset the board.
3-98

3.132 198092266 Under-voltage alarm of main power

input
This alarm is reported when the system detects that main power input at dry contact is abnormal.
Severity
Major
System Impact
I. Board Status:
Work normally.
Probable Cause

Handling Suggestion
1. Check whether input voltage of the main power module is abnormal. If yes, replace it.
3. Reset the board.
3.133 198092363 Faulty main power alarm

This alarm is reported when the system detects that the main power at dry contact is faulty.
Severity
Major
3-99

LTE Alarm Handling
System Impact
I. Board Status:
Work normally.
l 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.
l 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.

2. The environment monitoring unit (EMU) is faulty.
Handling Suggestion
None
3.134 198092267 General fault of main power

This alarm is reported when the system detects that the main power at dry contact is faulty.
Severity
Major
System Impact
I. Board Status:
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-100

Handling Suggestion
None
3.135 198092268 PWR monitoring unit alarm

This alarm is reported when PWR monitoring unit is abnormal.
Severity
Minor
System Impact
I. Board Status:
Work normally.
If PWR monitoring unit reports this alarm, the power-related performance cannot be correctly
reported. But this doesn't affect services.
Probable Cause
PW monitoring unit is broken.
Handling Suggestion
2. Replace the environment monitoring unit.
3.136 198092550 User-defined dry contact alarm 1

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

LTE Alarm Handling
System Impact
I. Board Status:
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.

Severity
Minor
System Impact
I. Board Status:
Probable Cause
Handling Suggestion
3-102


Severity
Minor
System Impact
I. Board Status:
Probable Cause
Handling Suggestion

Severity
Minor
System Impact
I. Board Status:
Probable Cause
3-103

LTE Alarm Handling
Handling Suggestion

Severity
Minor
System Impact
I. Board Status:
Probable Cause
Handling Suggestion

Severity
Minor
3-104

System Impact
I. Board Status:
Probable Cause
Handling Suggestion

Severity
Minor
System Impact
I. Board Status:
Probable Cause
Handling Suggestion
3-105

LTE Alarm Handling

Severity
Minor
System Impact
I. Board Status:
Probable Cause
Handling Suggestion

Severity
Minor
System Impact
I. Board Status:
Probable Cause
3-106

Handling Suggestion

Severity
Minor
System Impact
I. Board Status:
Probable Cause
Handling Suggestion

Severity
Minor
3-107

LTE Alarm Handling
System Impact
I. Board Status:
Probable Cause
Handling Suggestion

Severity
Minor
System Impact
I. Board Status:
Probable Cause
Handling Suggestion
3-108


Severity
Minor
System Impact
I. Board Status:
Probable Cause
Handling Suggestion

Severity
Minor
System Impact
I. Board Status:
Probable Cause
3-109

LTE Alarm Handling
Handling Suggestion

Severity
Minor
System Impact
I. Board Status:
Probable Cause
Handling Suggestion

Severity
Minor
3-110

System Impact
I. Board Status:
Probable Cause
Handling Suggestion

Severity
Minor
System Impact
I. Board Status:
Probable Cause
Handling Suggestion
3-111

LTE Alarm Handling

Severity
Minor
System Impact
I. Board Status:
Probable Cause
Handling Suggestion

Severity
Minor
System Impact
I. Board Status:
Probable Cause
3-112

Handling Suggestion

Severity
Minor
System Impact
I. Board Status:
Probable Cause
Handling Suggestion

Severity
Major
3-113

LTE Alarm Handling
System Impact
I. Board Status:
Probable Cause
Handling Suggestion

Severity
Major
System Impact
I. Board Status:
Probable Cause
Handling Suggestion
3-114


Severity
Major
System Impact
I. Board Status:
Probable Cause
Handling Suggestion

Severity
Major
System Impact
I. Board Status:
Probable Cause
3-115

LTE Alarm Handling
Handling Suggestion

Severity
Major
System Impact
I. Board Status:
Probable Cause
Handling Suggestion

Severity
Major
3-116

System Impact
I. Board Status:
Probable Cause
Handling Suggestion

Severity
Major
System Impact
I. Board Status:
Probable Cause
Handling Suggestion
3-117

LTE Alarm Handling

Severity
Major
System Impact
I. Board Status:
Probable Cause
Handling Suggestion

Severity
Major
System Impact
I. Board Status:
Probable Cause
3-118

Handling Suggestion

Severity
Major
System Impact
I. Board Status:
Probable Cause
Handling Suggestion

Severity
Major
3-119

LTE Alarm Handling
System Impact
I. Board Status:
Probable Cause
Handling Suggestion

Severity
Major
System Impact
I. Board Status:
Probable Cause
Handling Suggestion
3-120


Severity
Major
System Impact
I. Board Status:
Probable Cause
Handling Suggestion

Severity
Major
System Impact
I. Board Status:
Probable Cause
3-121

LTE Alarm Handling
Handling Suggestion

Severity
Major
System Impact
I. Board Status:
Probable Cause
Handling Suggestion

Severity
Major
3-122

System Impact
I. Board Status:
Probable Cause
Handling Suggestion

Severity
Major
System Impact
I. Board Status:
Probable Cause
Handling Suggestion
3-123

LTE Alarm Handling

Severity
Major
System Impact
I. Board Status:
Probable Cause
Handling Suggestion

Severity
Major
System Impact
I. Board Status:
Probable Cause
3-124

Handling Suggestion

Severity
Major
System Impact
I. Board Status:
Probable Cause
Handling Suggestion

Severity
Major
3-125

LTE Alarm Handling
System Impact
I. Board Status:
Probable Cause
Handling Suggestion

Severity
Major
System Impact
I. Board Status:
Probable Cause
Handling Suggestion
3-126


Severity
Major
System Impact
I. Board Status:
Probable Cause
Handling Suggestion

Severity
Major
System Impact
I. Board Status:
Probable Cause
3-127

LTE Alarm Handling
Handling Suggestion

Severity
Major
System Impact
I. Board Status:
Probable Cause
Handling Suggestion

Severity
Critical
3-128

System Impact
I. Board Status:
Probable Cause
Handling Suggestion

Severity
Critical
System Impact
I. Board Status:
Probable Cause
Handling Suggestion
3-129

LTE Alarm Handling

Severity
Critical
System Impact
I. Board Status:
Probable Cause
Handling Suggestion

Severity
Critical
System Impact
I. Board Status:
Probable Cause
3-130

Handling Suggestion

Severity
Critical
System Impact
I. Board Status:
Probable Cause
Handling Suggestion
3.186 198092073 Embedded power AC-in Switch Off

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.
3-131

LTE Alarm Handling
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.187 198092074 Embedded power AC Power Off

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.
Handling Suggestion
1. If the AC power supply is powered down, use the generator to provide power supply.
2. Check whether the AC transducer's connection is normal and whether the transducer has no
problem.
3. Check whether the monitoring unit's socket is inserted properly.
3-132

3.188 198092075 Embedded power SPD-C Broken

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.189 198092076 Embedded power SPD-D Broken

The class D arrester loop is faulty.
Severity
Minor
System Impact
The lightning protector fails.
3-133

LTE Alarm Handling
Probable Cause
1. The lightning protector is damaged.

2. The lightning protector's base is of bad contact.
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 disconnected or of bad contact.
4. Check the monitoring unit's connection.
3.190 198092077 Embedded power AC Under-Volt

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.
3-134

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;
problem;
3.191 198092078 Embedded power AC Over-Volt

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.
Probable Cause
1. The AC input voltage is high.

2. The AC over-voltage value of the monitoring unit is set too low.
Handling Suggestion
1. Improve the power supply quality of the equipment room;

2. If the detected AC voltage value is higher than the threshold value for alarm of AC voltage being
high, then appropriately increase the threshold value;
problem;
4. Check whether the monitoring unit's socket is inserted properly.
3-135

LTE Alarm Handling
3.192 198092079 Embedded power AC Current Over

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.193 198092116 Embedded power AC Auxiliary Output

Switch Off
The air break switch of the standby AC output is not closed.
Severity
Minor
System Impact
1. The power supply from standby AC output is influenced.
3-136

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.
Handling Suggestion
1. Close the air break switch of the standby AC output;

2. Check the air break switch's contact;
3.194 198092447 Unbalanced AC phase voltage of

built-in power
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-137

LTE Alarm Handling
3.195 198092448 High AC phase current of built-in

power
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.
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.
3.196 198092449 Missing AC phase voltage of built-in

power
AC phase is missing.
Severity
Major
3-138

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.197 198092117 Embedded power Rectifier Module

Fault
A rectifier module is faulty.
Severity
Critical
System Impact
1. 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.
3-139

LTE Alarm Handling
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.198 198092080 Embedded power SMR Over-Vout

Rectifier output over-voltage.
Severity
Critical
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.199 198092081 Embedded power SMR Over-Iout

Rectifier output over-current.
Severity
Critical
3-140

System Impact

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.200 198092082 Embedded power SMR Fan Fault

The fan of the rectifier is abnormal.
Severity
Critical
System Impact

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. Replace the rectifier;
4. Replace the monitoring unit;
3-141

LTE Alarm Handling
3.201 198092083 Embedded power SMR PFC Fault

This alarm is reported when the rectifier-related PFC has one of these faults: over-current input,
over-voltage output or under-voltage output.
Severity
Critical
System Impact

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

Rectifier AC input over-voltage.
Severity
Critical
System Impact

Probable Cause
1. The AC input voltage of the rectifier is higher than the threshold value of over-voltage protection.
3-142

Handling Suggestion
1. Check whether the AC voltage is higher than the threshold value;

3.203 198092085 Embedded power SMR Under-Vin Off

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.204 198092086 Embedded power SMR H.T. Off

The temperature of the heat sink is too high.
Severity
Critical
System Impact

3-143

LTE Alarm Handling
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.205 198092087 Embedded power SMR Env.H.T.Off

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

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

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.206 198092088 Embedded power SMR Env.H.T

The ambient temperature of the rectifier is too high which causes the output power of the rectifier
to derate.
3-144

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).
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.207 198092089 Embedded power SMR L.Vin

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.
3-145

LTE Alarm Handling
Handling Suggestion
1. Check whether the AC voltage is lower than the threshold value;

3.208 198092090 Embedded power SMR Fuse Broken

The output fuse of the rectifier is blown.
Severity
Critical
System Impact

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.209 198092091 Embedded power SMR CommFail

The communication between the rectifier and monitoring unit is abnormal.
Severity
Critical
3-146

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.210 198092236 Embedded power SMR Output Fault

SMR Output Fault.
Severity
Critical
System Impact
Probable Cause
3-147

LTE Alarm Handling
Handling Suggestion
1. Pull out the 1.rectifier and plug it in again, and make it powered on.
3.211 198092394 Several faulty rectifiers

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.212 198092092 Embedded power DC Under-Volt

The DC output voltage is lower than DC OverVolt.
Severity
Minor
3-148

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.213 198092093 Embedded power DC Over-Volt

The DC output voltage is higher than DC UnderVolt.
Severity
Major
System Impact
1. 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.
3-149

LTE Alarm Handling
Handling Suggestion
1. Check the DC output voltage;

2. Check whether the DC under-voltage value of the monitoring unit is set appropriately;
4. Replace the rectifier;
3.214 198092094 Embedded power DC Loop Broken

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.215 198092095 Embedded power Bat Loop Broken

The battery loop is open.
3-150

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 disconnected or of bad contact;
4. Check whether the monitoring unit's socket is of bad contact or disconnected;
3.216 198092096 Embedded power Bat Under-Volt

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.
3-151

LTE Alarm Handling
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.
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.217 198092097 Embedded power Bat Over-Temp

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 monitoring unit is set appropriately.
3. Check whether the battery's temperature sensor is damaged;
3-152

3.218 198092098 Embedded power TmpL Shut-Down

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 cut-off in low-temperature environment.
Handling Suggestion
1. Check the battery's temperature;

2. Check whether the threshold value for cut-off in low-temperature environment of the monitoring
unit is set appropriately;
3. Check whether the battery's temperature sensor is damaged;
3.219 198092099 Embedded power 1st Shut-down

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.
3-153

LTE Alarm Handling
Probable Cause
1. When the battery's voltage decreases to the threshold value for first cut-off, the system performs
the first cut-off operation.
2. The first cut-off voltage of the monitoring unit is not set appropriately.
3. The manual cut-off 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 cut-off;
2. Check whether the first cut-off voltage of the monitoring unit is set appropriately;
3. Check the manual cut-off switch to see whether it is in the automatic status or the connected status;
4. Check whether the first cut-off DC contactor is damaged. Measure whether there is 48V 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 cut-off is caused
by SDCB fault.
3.220 198092100 Embedded power 2nd Shut-down

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.
3-154

Probable Cause
1. When the battery's voltage decreases to the threshold value for second cut-off, the system
performs the second cut-off operation.
2. The second cut-off voltage of the monitoring unit is not set appropriately.
3. The manual cut-off 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 cut-off;
2. Check whether the second cut-off voltage of the monitoring unit is set appropriately;
3. Check the manual cut-off switch to see whether it is in the automatic status or the connected status;
4. Check whether the second cut-off DC contactor is damaged. Measure whether there is 48V
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 cut-off is caused
by SDCB fault.
3.221 198092101 Embedded power DC SPD Broken

The DC arrester is faulty.
Severity
Critical
System Impact
The lightning protection capability is influenced. Replace the lightning protector in time.
Probable Cause

2. The DC lightning protector is damaged.
3-155

LTE Alarm Handling
Handling Suggestion
1. Check whether the detecting cable is disconnected or of bad contact;

2. Replace the DC lightning protector;
3.222 198092102 Embedded power DCBreaker Alarm

DC breaker breaks.
Severity
Minor
System Impact
If the circuit breaker cannot be powered down normally, then the battery might be discharged.
Probable Cause
1. The DC contactor is damaged, there is one or two cut-off alarms but no cut-off 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 cut-off.
3. The control loop of system cut-off 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.223 198092103 Embedded power Bat Test Failure

The test stops but the test duration does not reach the maximum test time.
3-156

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.
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.224 198092104 Embedded power Bat Discharge

The battery is being discharged.
Severity
Minor
System Impact
It influences the power supply for the base station.
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.
3-157

LTE Alarm Handling
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.225 198092237 Embedded power Bat Under-Temp

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

2. Check whether the battery's over-temperature value of the monitoring unit is set appropriately.
3. Check whether the battery's temperature sensor is damaged.
4. Check whether the monitoring unit's socket is of bad contact or disconnected.
3-158

3.226 198092238 Embedded power Bat Invalid-Temp

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

2. Check whether the temperature sensor is connected reliably.
3. Replace the temperature sensor.
4. Check whether the current is beyond the detection range.
3.227 198092239 Embedded power Battery Fault

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.
3-159

LTE Alarm Handling
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.
5. Replace the battery.
3.228 198092450 Battery low-voltage cut-off of built-in

power
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.
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.
3-160

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.229 198092451 Broken LLVD1 branch E of built-in

power
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.
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.
3-161

LTE Alarm Handling
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.
6. If SDCB board (hardware power-cut board) is configured, please check whether cut-off action
is caused by SDCB's fault.
3.230 198092452 Broken LLVD1 branch of built-in

power
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.
Probable Cause
3-162

Handling Suggestion

3.231 198092453 Broken LLVD2 branch E of built-in

power
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.
Probable Cause
3-163

LTE Alarm Handling
Handling Suggestion

3.232 198092454 Broken battery cut-off branch E of

built-in power
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.
Probable Cause

3-164

Handling Suggestion

threshold.
3.233 198092455 Broken battery cut-off branch of

built-in power
Battery's cut-off branch is broken.
Severity
Major
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.
Probable Cause

3-165

LTE Alarm Handling
Handling Suggestion

threshold.
3.234 198092456 Abnormal battery current of built-in

power
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.235 198092457 Abnormal CAN bus of built-in power

CAN bus is abnormal.
3-166

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.236 198092458 Abnormal battery of built-in power

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-167

LTE Alarm Handling
3.237 198092459 Abnormal input dry contact of built-in

power
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

2. The input detection hardware has a problem.
Handling Suggestion

2. Check SCDB (hardware circuit board).
3.238 198092460 High-temperature cut-off of built-in

power
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.
3-168

Probable Cause

Handling Suggestion

2. Check whether the configured "high-temperature cut-off threshold" of the monitoring unit is
reasonable.
3.239 198092234 Embedded power type configuration

error
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-169

LTE Alarm Handling
3.240 198092235 Embedded power communication

interruption
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.

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

3.241 198096550 Alarm of fiber configuration

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
3-170

Handling Suggestion
Re-configurate optical port or replace optical module in practice.
3.242 198096551 RRU unconfigured

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.243 198096552 Difference of fiber time delay of two

RRUs in same sector exceeded system limit
Difference of fiber time delay of two RRUs in same sectore exceeded system limit.
Severity
Major
System Impact
In downlink, the measurement of optical fiber's delay may be failure, thereby the RRU cannot enter
normal work state.
3-171

LTE Alarm Handling
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 configurated in the same sector).
2. Check the distance between 2 RRUs in the sector, the longest distance should be less than 10km.
3.244 198096553 RRU Type is not consistent with

configuration type
RRU Type is not consistent with configuration type.
Severity
Critical
System Impact
The RRU cannot 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.245 198096554 Failure of optical decoding in BBU

Failure of optical decoding in BBU.
Severity
Major
3-172

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.246 198096555 Failure of optical decoding in RRU

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.247 198096556 IQ link input loses lock

IQ link input loses lock.
3-173

LTE Alarm Handling
Severity
Major
System Impact
The quality of service tend to decrease.
Probable Cause
IQ link input lose lock.
Handling Suggestion
1. Check whether baseband board and IQ(SBMP of B322) board is normal.

2. if it is normal, reset board.
3. Replace board.
3.248 198096558 Downlink baseband power abnormal

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 frequency 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-174

3.249 198096559 RRU adjust channel or adjust cable

fault
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 multi-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.250 198096560 Master and slave monitor link alarm

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

2. 485 master/slave cable pins error.
3-175

LTE Alarm Handling
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.251 198096561 Coherence alarm of antenna channel

swing and phase
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.252 198096562 RRU self check failed when power on

RRU self check failed when power on.
Severity
Major
3-176

System Impact
The RRU cannot 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.253 198096563 RRU device alarm

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-177

LTE Alarm Handling
3.254 198096565 Configurate parameter of RRU

external device not consistent with real parameter
Configurate 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 configured type of RRU external device to make them the same.
3.255 198092433 RRU network interrupted alarm

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.
3-178

Handling Suggestion

3.256 198092434 Clock line abnormal connection in

stack mode
This alarm is reported when clock line is abnormal in stack mode.
Severity
Major
System Impact
I. Board Status:
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.257 198092435 Inter-frame Ethernet link broken in

stack mode
This alarm is reported when inter-frame Ethernet Eth1 link is broken in stack mode.
3-179

LTE Alarm Handling
Severity
Major
System Impact
I. Board Status:
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.258 198092436 Loss of clock synchronization at

slave frame
This alarm is reported when it fails to synchronize slave clock with master clock in stack mode.
Severity
Major
System Impact
I. Board Status:
Work normally.
Inter-frame services between master and slave frame are affected.
Probable Cause
1. Stack clock line is faulty.

2. The main control board on slave frame has a hardware fault.
3-180

Handling Suggestion
1. Check whether stack clock line is firmly inserted.

2. Replace the stack clock line.
3. Replace the main control board on slave frame.
3.259 198092437 RRU radio frequency group

unavailable
This alarm is reported when RRU channel cannot bear services during calibration or other manual
operations.
Severity
Major
System Impact
I. Board Status:
Work normally.
The corresponding channel is unavailable.
Probable Cause
RRU 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.260 198092438 Device in low temperature

This alarm is reported when the system detects that a device stays in very low temperature, lower
than configured lower limit.
3-181

LTE Alarm Handling
Severity
Major
System Impact
I. Board Status:
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°C). If yes, do nothing.
2. Remove and insert SA board.
3. Replace SA board.
3.261 198092439 Uplink transport port of a base station

operates in a different mode from configured one
Uplink transport port of a base station operates in a different mode from configured one.
Severity
Minor
System Impact
I. Board Status:
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-182

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.262 198092461 BBU inter-subrack frame

synchronization failure alarm
This alarm is reported when frame synchronization is unsuccessful between BBU subracks.
Severity
Minor
System Impact
I. Board Status:
Inter-subrack service may not work properly.
Inter-subrack IQ data is abnormally accumulated and inter-subrack services are interrupted.
Probable Cause
The clock phase provided by the main control 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-183

LTE Alarm Handling
3.263 198098431 Abnormal current alarm at NSBT port

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
System Impact
I. Board Status:
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.
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-184

3.264 198098432 AISG/NSBT port turn-off alarm due

to over current
Channel current is larger than the maximum value allowed by AISG/NSBT power moduel.
Severity
Minor
System Impact
I. Board Status:
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-185

LTE Alarm Handling
3.265 198098434 Abnormal transmission power at

antenna port
There is a big difference between transmission power at antenna port and digital power.
Severity
Minor
System Impact
I. Board Status:
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.266 198098435 Closed-loop power control adjustment

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

System Impact
I. Board Status:
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.267 198098436 Failure in configuring power level

Failure in configuring power level.
Severity
Minor
System Impact
I. Board Status:
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-187

LTE Alarm Handling
3.268 198096568 RRU used power module is too hot

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.269 198096569 RRU offline parameter check failure

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.
3-188

Handling Suggestion
1. Software enables standard offline parameter.

2. Check whether the offline parameter saved in EEPROM is correct.
3. Replace the RRU.
3.270 198100270 Optical signals transmitted from BBU

to RRU carry wrong clock information
Optical signals transmitted from BBU to RRU carry wrong clock information.
Severity
Critical
System Impact
I. Board Status:
Work normally.
RRU cannot provide services.
Probable Cause
PLL clock is unloced at optical port
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.271 198100271 Unlocked local oscillator alarm of

RRU
RRU reports an unlocked local oscillator alarm.
3-189

LTE Alarm Handling
Severity
Critical
System Impact
I. Board Status:
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.272 198100272 RRU inside clock unlocked

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
System Impact
I. Board Status:
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.
3-190

Handling Suggestion
1. Reset RRU
2. If it doesn't work, replace the RRU.
3.273 198100273 Downlink channel fault alarm

This alarm is reported when the value of RRU Tx channel gain is too low.
Severity
Major
System Impact
I. Board Status:
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.274 198100274 Downlink output power abnormal

This alarm is reported when the value of RRU Tx channel power is too high or low.
Severity
Major
3-191

LTE Alarm Handling
System Impact
I. Board Status:
Work normally.
Because RRU Tx channel cannot work properly, services borne on it are interrupted.
Probable Cause
1. Hardware fault (either Tx channel fault or power detection channel fault).

2. 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.275 198098438 The internal power module in a RRU

detects invalid lightning protection circuit
This alarm is reported when the lightning protection circuit in the internal power module of a RRU
becomes invalid.
Severity
Major
System Impact
I. Board Status:
No
If any lightning attack may damage the RRU power module. There is a potential risk that services
may be interrupted.
Probable Cause
The lightning protection circuit in the internal power module of RRU is invalid.
3-192

Handling Suggestion
1. Reset RRU and check whether the alarm disappears.

2. Turn off and turn on the RRU to check whether the alarm disappears.
3. Replace the RRU.
3.276 198094412 Fault in BPL clock

This alarm occurs when the Baseband Processing for LTE (BPL) board does not have a clock, the
clock signal is abnormal, or the clock loses lock.
Severity
Major
System Impact
1. Impact on the BPL board:

The BPL board is unavailable.
2. Impact on the service:
The cell that uses the BPL board cannot provide services.
Probable Cause
1. The Control and Clock Module (CC) board is faulty.

2. The clock outputted by the backplane is faulty.
3. The clock module of the alarmed device is faulty.
Handling Suggestion
1. Check whether there is any alarm related to the CC board.

l Yes -> Handle the alarm in accordance with the solution of the related alarm, and check whether
2. Reset the BPL board, and check whether the alarm is resolved.
3. Extract and insert the BPL board for three times, and check whether the alarm is resolved.
3-193

LTE Alarm Handling
4. Replace the BPL board, and check whether the alarm is resolved.
3.277 198094413 Fault in BPL hardware

This alarm occurs when the board or the communication link is faulty.
Severity
Major
System Impact

The BPL board is unavailable.
The cell that uses the BPL board cannot provide services.
Probable Cause
The hardware is faulty.
Handling Suggestion
1. Reset the BPL board, and check whether the alarm is resolved.
2. Extract and insert the BPL board for three times, and check whether the alarm is resolved.
3. Replace the BPL board, and check whether the alarm is resolved.
3.278 198094414 Discontinuous frame number

This alarm occurs when frame numbers received by the BPL board or an RRU are inconsecutive.
3-194

Severity
Major
System Impact

None
2. Impact on the RRU:
None
All UEs in the cell are out of synchronization in downlink and the services are interrupted.
Probable Cause
Causes related to the BPL board:

1. The CC board switches to the reference clock source.
2. The status of the CC board is changed from unlocked to locked.
3. The crystal oscillator of the CC board is aging.
Causes related to the RRU:
The link between the BBU and RRU is faulty.
Handling Suggestion
1. If the alarm is reported by the BPL board, go to step 2. If the alarm is reported by an RRU, go
to step 6.
à Yes -> No action is required.
3. Check the clock source status to see whether clock source switchover occurs.
l Yes -> Wait for the system to restore the clock source status. After the clock source status is
restored, check whether the alarm is resolved.
4. Check whether the reference clock source quality is stable.
l No -> If the reference clock source is Global Positioning System (GPS), check whether there
is any GPS-related alarm. If the reference clock source is 1588, check whether there is any
1588-related alarm.
3-195

LTE Alarm Handling
à Yes -> Handle the alarm in accordance with the solution of the related alarm, and check
whether the alarm is resolved.
5. Replace the CC board, and check whether the alarm is resolved.
6. Replace the optical fiber from the BBU to the RRU, enable the PA, and check whether the alarm
is resolved.
3.279 198094415 Frame frequency abnormal

This alarm occurs when a frame frequency received by the BPL board or an RRU is abnormal.
Severity
Major
System Impact

None
None
All UEs in the cell are out of synchronization in downlink and the services are interrupted.
Probable Cause
Causes related to the BPL board:

1. The CC board switches to the reference clock source.
2. The status of the CC board is changed from unlocked to locked.
3. The crystal oscillator of the CC board is aging.
Causes related to the RRU:
1. The link between the BBU and RRU is faulty.
3-196

Handling Suggestion
1. If the alarm is reported by the BPL board, go to step 2. If the alarm is reported by the RRU, go
to step 6.
3. Check the clock source status to see whether clock source switchover occurs.
l Yes -> Wait for the system to restore the clock source status. After the clock source status is
restored, check whether the alarm is resolved.
4. Check whether the reference clock source quality is stable.
l No -> If the reference clock source is GPS, check whether there is any GPS-related alarm. If the
reference clock source is 1588, check whether there is any 1588-related alarm.
à Yes -> Handle the alarm in accordance with the solution of the related alarm, and check
5. Replace the CC board, and check whether the alarm is resolved.
6. Replace the optical fiber from the BBU to the RRU, enable the PA, and check whether the alarm
is resolved.
3.280 198094425 Optical module temperature is

abnormal
This alarm occurs when the temperature of the optical module is too high or too low.
3-197

LTE Alarm Handling
Severity
Minor
System Impact
The optical communication between the BBU and RRU is abnormal, and the service might be
interrupted.
Probable Cause
The optical module is not operating properly.
Handling Suggestion
Replace the optical module or make the temperature of the optical module be normal, and check
3.281 198094426 Optical module bias current is

abnormal
This alarm occurs when the bias current of the optical module is too low or too high.
Severity
Minor
System Impact
interrupted.
Probable Cause
Handling Suggestion
Replace the optical module, and check whether the alarm is resolved.
3-198

3.282 198094427 Optical module transmit power is

abnormal
This alarm occurs when the transmit power of the optical module is too low or too high.
Severity
Minor
System Impact
interrupted.
Probable Cause
Handling Suggestion
3.283 198094428 Optical module inner voltage is

abnormal
This alarm occurs when the internal voltage of the optical module is too low or too high.
Severity
Minor
System Impact
interrupted.
Probable Cause
3-199

LTE Alarm Handling
Handling Suggestion
3.284 198098439 ATMA works in bypass mode

This alarm is reported when the TMA subunit cannot report the correct value of gain due to in bypass
mode.
Severity
Minor
System Impact
I. Board Status:
Work normally.
The TMA subunit is in bypass mode. This causes degraded cell performance.
Probable Cause
The TMA subunit is in bypass mode.
Handling Suggestion
1. Set the TMA subunit to be in normal mode.

2. Reset the device.
3. Replace the device.
3-200

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

LTE Alarm Handling
4.1 198092307 Slight-high temperature of board

The board temperature exceeds slight-high temperature threshold.
Severity
Warning
System Impact
I. Board Status:
Work normally.
Services borne on the board are not interrupted.
Probable Cause
1. Environmental temperature exceeds a threshold.

2. The fan is faulty.
3. The temperature sensor on the board is faulty.
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 198092308 Over-high temperature of board

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.
4-2

Chapter 4 Environment Alarm
Probable Cause
1. Environmental temperature exceeds a threshold.

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

and power devices?
4.3 198092429 Board powered-down alarm because

of high temperature
This alarm is reported when the board temperature exceeds upper limit and cannot work properly.
Severity
Major
System Impact
I. Board Status:
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

and power devices?
4-3

LTE Alarm Handling
4.4 198092371 CCM Remote MEP Error

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.5 198092372 CCM Message Error

The message send by CCM has error.
Severity
Major
System Impact
Probable Cause
The message send by CCM has error.
Handling Suggestion
4-4

4.6 198092373 CCM Xconnect Error

CCM message has conflict with configuration.
Severity
Major
System Impact
Probable Cause
CCM message has conflict with configuration.
Handling Suggestion
4.7 198092053 Abnormal input voltage

This alarm is reported when the input voltage is abnormal.
Severity
Major
System Impact
I. Board Status:
Work normally.
The power supply to other boards may be affected. As a result, services borne on these boards
may be affected.
Probable Cause
When the value of PM input voltage is higher than over-voltage threshold, it means over voltage.
When the value of PM input voltage is lower than under-voltage threshold, it means under voltage.
4-5

LTE Alarm Handling
Handling Suggestion
l Over-voltage: Check whether the input voltage of DC supply system is higher than or equal to
over-voltage recovery threshold by multimeter or other tools. Replace the DC supply system if
so; Replace the power board PM if not.
l Under-voltage: Check whether the input voltage of DC supply system is lower than under-voltage
recovery threshold by multimeter or other tools. Replace the DC supply system if so; Replace
the power board PM if not.
4.8 198092037 MP voltage abnormal

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.9 198092038 PP voltage abnormal

PP voltage.
Severity
Major
4-6

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 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.10 198092039 Over current of MP

Over current of MP.
Severity
Minor
System Impact
I. Board Status:
II. 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 MP current status of PM/PSA board's load is checked periodically. If over-current is detected,
Handling Suggestion
1. Remove and insert the corresponding board;

2. Replace the corresponding board;
3. Replace PM board;
4. Replace the backplane.
4-7

LTE Alarm Handling
4.11 198092040 Over current of PP

Over current of PP.
Severity
Minor
System Impact
I. Board Status:
II. 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,
Handling Suggestion
1. Remove and insert the corresponding board;

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

Fan failure.
Severity
Minor
4-8

System Impact
I. Board Status:
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.13 198092069 FCE-fan failure

FCE-fan failure.
Severity
Minor
System Impact
I. Board Status:
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-9

LTE Alarm Handling
4.14 198092042 Abnormal temperature at air intake

The temperature at air intake is abnormal.
Severity
Minor
System Impact
I. Board Status:
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 intake:
1. The environmental temperature is lower than the configured lower limit.
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°C. If not, please
correct it.
5. Reset the SA/PSA board.
6. Replace the fan subrack.
7. Replace the SA/PSA board.
In the case of low temperature at air intake:
1. Check whether the environmental temperature is lower than -25°C. If yes, do nothing.
2. Replace the heat exchanger.
4-10

3. Check whether the lower limit of configured environmental temperature is -25°C. If not, please
correct it.
4. Reset the SA/PSA board.
5. Replace the fan subrack.
6. Replace the SA/PSA board.
4.15 198092043 Abnormal temperature at air outlet

The temperature at air outlet is abnormal.
Severity
Minor
System Impact
I. Board Status:
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 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 outlet:

1. Wash and clean the dustproof net.
2. Check whether the air conditioner works properly. Make sure it works normally.
In the case of low temperature at air outlet:
1. Check whether the envirnmental temperature is lower than -25°C. If yes, do nothing.
2. Remove and insert SA/PSA board.
3. Replace SA/PSA board.
4-11

LTE Alarm Handling
4.16 198092213 Abnormal temperature of board

The board temperature exceeds temperature alarming threshold.
Severity
Minor
System Impact
The board may not work properly because of over-high or over-low temperature.
Probable Cause
The board temperature is over high or over low, beyond the corresponding alarming threshold.
Handling Suggestion
1. Check whether the fan subrak works normally.

4.17 198092044 Door control alarm

This alarm is reported when a door control sensor is used but the door is not closed.
Severity
Major
System Impact
I. Board Status:
Work normally.
Cables are probably stolen or water may enter the device. These may cause reduced service
performance or even service interruption.
4-12

Probable Cause
2. The door is not closed.
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.
3. Replace board.
4.18 198092045 Flooding alarm

This alarm is reported when the flooding sensor connected at a dry contact detects a flooding situation.
Severity
Minor
System Impact
I. Board Status:
Work normally.
The board or system may not work properly. As a result, services borne on the board are interrupted.
Probable Cause
configured. Note that there are two kinds 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.
3. Reset the board.
4-13

LTE Alarm Handling
4.19 198092046 Smog alarm

This alarm is reported when the smog sensor connected at a dry contact detects a smog situation.
Severity
Minor
System Impact
I. Board Status:
Work normally.
No impact
Probable Cause
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.20 198092047 Infrared alarm

None
Severity
Minor
4-14

System Impact
I. Board Status:
Work normally.
No impact.
Probable Cause
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.21 198092048 Air conditioner fault

None
Severity
Minor
System Impact
I. Board Status:
Work normally.
This may cause other alarms such as device high temperature alarm, whole-set temperature rise
alarm, or the board or system may not work properly. The high temperature rise may further cause
reduced service performance and even service interruption.
Probable Cause
2. The air conditioner is faulty.
4-15

LTE Alarm Handling
Handling Suggestion
1. Check whether the cable connected to the air conditioner is good.
2. Replace the air conditioner.
4.22 198092105 Embedded power Environment is

under-temperature
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;
3. Replace the temperature sensor;

over-temperature
The environment temperature is higher than environment over-temperature that is set.
Severity
Minor
4-16

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.
Handling Suggestion
4.24 198092107 Embedded power Environment

temperature is invalid
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.
4-17

LTE Alarm Handling
Handling Suggestion
2. Check whether the temperature sensor is connected reliably;

under-Humidity
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 equipment room condition;
3. Replace the humidity sensor;

over-Humidity
The environment humidity is higher than Environment over-humidity that is set.
4-18

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.
Handling Suggestion
4.27 198092110 Embedded power Environment

humidity is invalid
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.
4-19

LTE Alarm Handling
Handling Suggestion
2. Check whether the humidity sensor is connected reliably;
4.28 198092111 Embedded power Smoke detected

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.29 198092112 Embedded power Flood detected

The sensor detects the water.
Severity
Minor
4-20

System Impact
The system security is influenced.
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.30 198092113 Embedded power Door Magnet Alarm

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.
4-21

LTE Alarm Handling
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.31 198092114 Embedded power Gate Embedded

power Safety Alarm
The sensor detects that the access control of the cabinet is not closed.
Severity
Major
System Impact
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.
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-22

4.32 198092115 Glass Broken Alarm

The sensor detects that the glass is broken.
Severity
Minor
System Impact
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.33 198092118 Embedded power Env-unit

communication interruption
The communication of the system environment monitoring unit is interrupted.
Severity
Major
System Impact
The normal detection of environment parameters is influenced.
4-23

LTE Alarm Handling
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;
4. Replace the environment monitoring board or the monitoring unit.
4.34 198092119 Embedded power Heat Exchanger Fault

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

Handling Suggestion

2. Check whether the heat exchanger is damaged or the temperature is beyond the allowed range.
3. Replace the heat exchanger.
4-24

4.35 198098128 Over-loaded power

This alarm is reported when load power exceeds a certain threshold.
Severity
Major
System Impact
I. Board Status:
The board may have a fault.
A potential impact is that either a board or the system may not work properly.
Probable Cause
1. Too many load boards are configured. The required power reaches or even exceeds the maximum
supported by the PM board;
2. This board is broken.
Handling Suggestion
1. Check whether the number of configured boards exceeds the maximum supported by the PM
board.
2. Replace the PM board.
4.36 198092462 Blocked dust proof net

This alarm is reported when dust proof net is blocked.
Severity
Major
4-25

LTE Alarm Handling
System Impact
I. Board Status:
None
None
III. Other impacts:
It causes the rise of temperature in the cabinet.
Probable Cause
1. The corresponding dry contact can be configured at network management interface. Its normally
closed/open status is wrongly configured.
2. The dust proof net is blocked.
Handling Suggestion
1. Check the configuration of dry contact.

2. Clean up dust proof net.
4-26

Chapter 5
Processing Alarm
Table of Contents
198092309 Line clock has the fault ............................................................................5-2
198092310 SyncE clock has the fault .........................................................................5-3
198092414 SyncE clock unavailable (SyncE+1588) ...................................................5-4
198092412 1PPS+TOD source fault ..........................................................................5-4
198092413 1PPS+TOD Backup source fault ..............................................................5-5
198092463 BSP initialization failure ...........................................................................5-6
198092348 Board initialization....................................................................................5-7
198092390 CPU over loading highly alarm.................................................................5-7
198092391 CPU over loading.....................................................................................5-8
198092347 The fan control policy is not existed ........................................................5-8
198092014 SNTP time adjustment failure alarm.........................................................5-9
198092016 Clock reference source configuration error.............................................5-10
198092017 Failure in loading software .....................................................................5-10
198092070 Board software has fault ........................................................................5-11
198092022 Running software version doesn't exist ..................................................5-12
198092027 Failure in repairing specification package...............................................5-13
198092029 Wrong board insertion............................................................................5-13
198092030 Abnormal software in specification package...........................................5-14
198092395 Running software rollback......................................................................5-15
198092396 Board hot patch fault..............................................................................5-15
198092397 Failure in finding this board-related software ID ....................................5-16
198092398 MMC running software version doesn't exist ..........................................5-17
198092443 IR changeover failure ............................................................................5-17
198092066 Failure in uncompressing LMT software.................................................5-18
198092360 Product process is abnormal..................................................................5-19
198092060 LMT accessing ......................................................................................5-19
198092430 Optical module rate does not match.......................................................5-20
198092432 Optical modules have mismatched transmission distance ......................5-20
198092366 Configuration Fail...................................................................................5-21
198092403 Carrier frequency configuration error......................................................5-22
198092404 Center frequency configuration error......................................................5-22
198092405 Work pattern configuration error.............................................................5-23
198092406 IQ parameter configuration error ............................................................5-23
198092407 Delay parameter configuration error.......................................................5-24
198092408 Carrier power configuration error ...........................................................5-25
198096567 BOOT software upgrade failure..............................................................5-25
198098437 The configured total power exceeds rated value ....................................5-26
5-1

LTE Alarm Handling
198100275 RRU software version is abnormal .........................................................5-26

198092010 Board communication link is interrupted.................................................5-27
198092019 Failure in synchronizing the version of master board with slave board ...5-28
198092024 DOM is lack of space .............................................................................5-29
198092025 Failure in synchronizing software version of main control board .............5-29
198094418 Rule library of performance statistics hasn't been loaded or loaded
unsuccessfully..........................................................................................................5-30
198094429 Optical module rate does not match.......................................................5-31
198094434 Optical modules have mismatched transmission distance ......................5-31
198098463 Two small carrier frequency interval .......................................................5-32
5.1 198092309 Line clock has the fault

This alarm is reported when the main control board fails to detect reference clock signal from the
corresponding line or the quality of clock signal is poor.
Severity
Minor
System Impact
I. Board Status:
II. Service Impact:
System clock enters free oscillation state, which affects services in the following ways:
1. Iub interface: If Iub adopts E1, code-sliding happens periodically at Iub interface. If Iub adopts FE,
there is no influence.
2. Inter-base station soft handover: An alarm cannot be recovered for a long time. The possible
reason is base station clock accuracy cannot meet 3GPP requirement due to aging problem.
Consequently, soft handover success rate is reduced.
Probable Cause

2. External reference clock and cable are faulty.
5-2

Chapter 5 Processing Alarm
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.2 198092310 SyncE clock has the fault

This alarm is reported when one of the problems occurs: the quality of synchronous Ethernet clock,
extracted from an SSM, is poor; SSM is lost; logic clock signal cannot be detection; or quality of
clock reference source is poor.
Severity
Minor
System Impact
I. Board Status:
II. Service Impact:
System clock enters free oscillation state, which affects services in the following ways:
1. Iub interface: If Iub adopts E1, code-sliding happens periodically at Iub interface. If Iub adopts FE,
there is no influence.
2. Inter-base station soft handover: An alarm cannot be recovered for a long time. The possible
reason is base station clock accuracy cannot meet 3GPP requirement due to aging problem.
Consequently, soft handover success rate is reduced.
Probable Cause

2. External reference clock and cable are faulty.
4. SSM is lost.
5-3

LTE Alarm Handling
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.3 198092414 SyncE clock unavailable (SyncE+1588)

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.4 198092412 1PPS+TOD source fault

1PPS+TOD reference source doesn't receive messages via serial port; 1PPS+TOD reference source
has unavailable PPS (pulse per second) status; 1PPS+TOD reference source cannot obtain time of
day information for a certain period.
5-4

Severity
Minor
System Impact
I. Board Status:
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.5 198092413 1PPS+TOD Backup source fault

1PPS+TOD Backup source cannot receive messages via serial port; 1PPS+TOD Backup source
has unavailable PPS (pulse per second) status; 1PPS+TOD Backup source cannot obtain time of
day information for a certain period.
Severity
Minor
System Impact
I. Board Status:
Failure in obtaining 1PPS+TOD signals.
Clock synchronization and frame synchronization cannot be guaranteed. This will affect soft handover.
5-5

LTE Alarm Handling
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.6 198092463 BSP initialization failure

The alarm is reported when BSP is powered on, but fails to initialize.
Severity
Major
System Impact
I. Board Status:
Board is faulty.
All services borne on the board may be interrupted.
Probable Cause
BSP fails to initialize.
Handling Suggestion
1. Reset the board.

5-6

5.7 198092348 Board initialization

This alarm is reported when a board reboots and then enters into the initial state.
Severity
Major
System Impact
I. Board Status:
The board is initialized.
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.
Handling Suggestion
The alarm will be restored after board initialization. No handling is necessary.
5.8 198092390 CPU over loading highly alarm

An alarm is given when the system has constantly detected CPU usage exceeds high alarm threshold.
Severity
Major
System Impact
I. Board Status:
Board processing capability declines, probably leading to radio link or service establishment failure.
5-7

LTE Alarm Handling
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.9 198092391 CPU over loading

An alarm is given when the system has constantly detected CPU usage exceeds low alarm threshold.
Severity
Minor
System Impact
I. Board Status:
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.10 198092347 The fan control policy is not existed

It is failed to find a fan control policy for current SA or FCE board.
5-8

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.11 198092014 SNTP time adjustment failure alarm

SNTP server doesn't boot or its link has a fault.
Severity
Minor
System Impact
I. Board Status:
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.
5-9

LTE Alarm Handling
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.12 198092016 Clock reference source configuration

error
During the period of starting configuration or board running, this alarm is reported if a wrong
configuration parameter is found. This configuration parameter is delivered from main control board.
Severity
Major
System Impact
I. Board Status:
II. 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.13 198092017 Failure in loading software

This alarm is reported when the CPU/DSP/FPGA on a board fails to load software.
5-10

Severity
Major
System Impact
I. Board Status:
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.14 198092070 Board software has fault

When the software of CPU/DSP/FPGA board fails to be downloaded or uploaded or uninstalled,

Severity
Major
System Impact
I. Board Status:
Probable Cause
1. The board's software version, which is saved on the main control board, is incorrect.
5-11

LTE Alarm Handling
Handling Suggestion
1. Re-download the software version on the software management interface of OMCB.

5.15 198092022 Running software version doesn't exist

This alarm is reported when the main control board finds that the running software version doesn't
exist.
Severity
Major
System Impact
I. Board Status:
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. If the
system surely doesn't need the missing software version, delete this alarm record manually from EMS.
5-12

5.16 198092027 Failure in repairing specification

package
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
System Impact
I. Board Status:
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.17 198092029 Wrong board insertion

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

LTE Alarm Handling
System Impact
I. Board Status:
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.18 198092030 Abnormal software in specification

package
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
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.
5-14

Handling Suggestion
Enter Software Version Management interface and reload software specification package.
5.19 198092395 Running software rollback

The alarm is reported when the software of main control board rollbacks.
Severity
Major
System Impact
I. Board Status:
II. 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.20 198092396 Board hot patch fault

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

LTE Alarm Handling
System Impact
I. Board Status:
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.21 198092397 Failure in finding this board-related

software ID
It is failed to find board software ID according to hardware information set of the faulty board.
Severity
Major
System Impact
I. Board Status:
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 the main control board is incomplete.
2. The alarming board has a hardware fault.
5-16

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.22 198092398 MMC running software version doesn't

exist
This alarm is reported when the main control board finds that MMC running software version doesn't
exist.
Severity
Warning
System Impact
I. Board Status:
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.
If the system surely doesn't need the missing software version, delete this alarm record manually
from EMS.
5.23 198092443 IR changeover failure

This alarm is reported when IR changeover fails.
5-17

LTE Alarm Handling
Severity
Critical
System Impact
None
Probable Cause
IR changeover fails.
Handling Suggestion
None
5.24 198092066 Failure in uncompressing LMT

software
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-18

5.25 198092360 Product process is abnormal

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.26 198092060 LMT accessing

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).
Handling Suggestion
None
5-19

LTE Alarm Handling
5.27 198092430 Optical module rate does not match

This alarm is reported when the speed of an optical module is inconsistent with its configured value.
Severity
Major
System Impact
I. Board Status:
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.
Handling Suggestion
Set the speed of optical module to be lower or equal to real optical module rate. Then check if
5.28 198092432 Optical modules have mismatched

transmission distance
This alarm is reported when the length of optical fiber is beyond the transmission distance of an
optical module.
Severity
Minor
5-20

System Impact
I. Board Status:
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
5.29 198092366 Configuration Fail

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-21

LTE Alarm Handling
5.30 198092403 Carrier frequency configuration error

This alarm is reported when Carrier frequency is out of the rated range of center frequency or duplex
range.
Severity
Critical
System Impact
I. 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.31 198092404 Center frequency configuration error

This alarm is reported when a board has detected that the delivered center frequency from the main
control board is wrong. This happens during initial or running period.
Severity
Critical
System Impact
I. Board status:
Work normally.
5-22

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.32 198092405 Work pattern configuration error

This alarm is reported when a board has detected that the delivered work pattern from BBU is wrong.
Severity
Critical
System Impact
I. Board status:
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.33 198092406 IQ parameter configuration error

This alarm is reported when a board has detected that the delivered IQ parameter from BBU is wrong.
5-23

LTE Alarm Handling
Severity
Critical
System Impact
I. Board status:
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.34 198092407 Delay parameter configuration error

This alarm is reported when a board has detected that the delivered delay parameter from BBU is
wrong.
Severity
Critical
System Impact
I. Board status:
Work normally.
Probable Cause
The delay parameter is wrongly configured.
Handling Suggestion
Check delay parameter in BBU.
5-24

5.35 198092408 Carrier power configuration error

This alarm is reported when a board has detected that the delivered carrier power from BBU is wrong.
Severity
Critical
System Impact
I. 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.36 198096567 BOOT software upgrade failure

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.
5-25

LTE Alarm Handling
Handling Suggestion
Try to upgrade boot version manually. If it fails again, please replace RRU.
5.37 198098437 The configured total power exceeds

rated value
BBU configures all carriers of this channel with certain power. But the sum of power exceeds the
rated value declared by RU.
Severity
Major
System Impact
I. Board Status:
Work normally.
The services borne on the faulty channel are interrupted.
Probable Cause
The configured total power of this channel is too large.
Handling Suggestion
Configure correct carrier power via the configuration management function. Make sure that the sum of
all carrier power over the RU channel doesn't exceed maximum power supported by this RU channel.
5.38 198100275 RRU software version is abnormal

This alarm is reported when RRU software or firmware version fails to be downloaded or uploaded.
Severity
Major
5-26

System Impact
I. Board Status:
RRU runs normally and the running version may not be the wanted one.
Services on RRU can run normally.
Probable Cause
1. Download failure: this RRU software version doesn't exist in BBU, download operation is time out,
the software package is too big, or other reason causes this failure.
2. Activation failuer: RRU version doesn't exist or is damaged, software version doesn't match with
hardware version, activiation operation is unsuccessful, or RRU takes too long time to give response.
3. Uploadd failure: Because the existing RRU version is broken, upload operation fails. As a result,
previous version has to be rolled back.
4. Ohter download problem: RRU downloads version files from BBU. This download operation fails
because a file doesn't exist or too big, or download operation is time out.
Handling Suggestion
1. Check the RRU version saved in BBU.

2. Check the existing RRU running version. If it is wrong, please download the correct version
and activate it.
5.39 198092010 Board communication link is

interrupted
This alarm is reported when the communication link between peripheral board and master main
control board, or between slave main control board and master main control board.
Severity
Critical
System Impact
I. Board Status:
II. Service Impact:
The board fails to communicate with the master main control board, leading to interruption of board
services.
5-27

LTE Alarm Handling
Probable Cause
1. The board that has been configured does not exist on the rack.
2. The link between this board and master main control 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.40 198092019 Failure in synchronizing the version of

master board with slave board
This alarm is reported by the slave board when it fails to synchronize version files with master board.
Severity
Major
System Impact
I. Board Status:
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-28

5.41 198092024 DOM is lack of space

This alarm is reported when DOM has no sufficient space.
Severity
Minor
System Impact
I. Board Status:
Work normally.
There is no impact on services.
Probable Cause
DOM has no sufficient space.
Handling Suggestion
1. Execute disk clearing function via the network management interface.

2. Delete firmware specification package and all standby specification packages via the software
version management interface.
5.42 198092025 Failure in synchronizing software

version of main control board
This alarm is reported when the master control board fails to synchronize version files with slave
board.
Severity
Major
System Impact
I. Board Status:
The slave control board resets.
The master/slave changeover function cannot be performed.
5-29

LTE Alarm Handling
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.43 198094418 Rule library of performance statistics

hasn't been loaded or loaded unsuccessfully
This alarm occurs when the performance statistic rules library is not downloaded to the eNodeB from
the OMC or the eNodeB fails to process the loaded library.
Severity
Minor
System Impact
1. Impact on the alarmed device:

The processing capability of the device degrades.
The service quality degrades or the service fails to be established.
Probable Cause
1. The performance statistic rules library is not loaded.

2. The performance statistic rules library contains incorrect files.
Handling Suggestion
1. Check whether the running software version is correct.

l No -> Download the correct version file, activate it, and go to step 2.
2. Start the eNodeB, and check whether the alarm is resolved.
5-30

5.44 198094429 Optical module rate does not match

This alarm occurs when the configured optical port rate is out of the rate range supported by the
optical module.
Severity
Major
System Impact
The link between the BBU and RRU is broken.
Probable Cause
The actual optical module does not support the configured optical port rate.
Handling Suggestion
Configure the rate of the optical port to be less than or equal to the rate of the optical module, and
check whether the alarm is resolved.
l No -> Contact vendor's Technical Support.
5.45 198094434 Optical modules have mismatched

transmission distance
This alarm occurs when the actual length of an optical fiber is larger than the transmission distance
of the optical module.
Severity
Minor
System Impact
The service on the optical port link might be interrupted.
5-31

LTE Alarm Handling
Probable Cause
The actual optical fiber length is longer than the maximum transmission distance supported by the
optical module.
Handling Suggestion
Use an optical module that has longer transmission distance to replace the current one or use a
shorter optical fiber. Check whether the alarm is resolved.
No -> Contact Vendor's Technical Support.
5.46 198098463 Two small carrier frequency interval

This alarm is reported when the interval between 2 carrier frequency points of RRU is smaller than a
specified value.
Severity
Major
System Impact
I. Board Status:
Work normally.
Service performance may be affected.
Probable Cause
The interval between 2 carrier frequency points of RRU is smaller than a specified value.
Handling Suggestion
Check whether there is any conflict between the configured carrier frequency points.
5-32

Chapter 6
QoS Alarm
Table of Contents
198092417 Inner GNSS receiver has a satellite searching alarm ...............................6-1
198092420 Outer Facepanel GNSS receiver has a satellite searching alarm .............6-2
198092424 Outer Backpanel GNSS receiver has a satellite searching alarm .............6-3
198092368 Ethernet remote fault alarm(RDI) .............................................................6-3
198092380 EFM Link is broken ..................................................................................6-4
198092370 AIS alarm.................................................................................................6-4
198094419 Cell outage ..............................................................................................6-5
198094422 eNodeB is out of service ..........................................................................6-6
198094440 Cell portion is out of service .....................................................................6-7
6.1 198092417 Inner GNSS receiver has a satellite

searching alarm
This alarm is reported when the inner GNSS antenna fails to search satellites or the number of
searched satellites doesn't reach minimum requirement.
Severity
Minor
System Impact
I. Board Status:
Work normally.
Probable Cause
GNSS receiver fails to search satellites or the number of searched satellites doesn't reach minimum
requirement.
6-1

LTE Alarm Handling
Handling Suggestion
Check the faulty antenna feeder.

(1) Check the connection of GNSS antenna feeder and ensure it is OK.
(2) Check whether the direction of antenna is suitable (e.g. Is there any obstacle surrounding the
antenna?)
6.2 198092420 Outer Facepanel GNSS receiver has a

satellite searching alarm
This alarm is reported when Outer Facepanel GNSS receiver fails to search satellites or the number
of searched satellites doesn't reach minimum requirement.
Severity
Minor
System Impact
I. Board Status:
Work normally.
Probable Cause
The GNSS receiver fails to search satellites or the number of searched satellites doesn't reach
minimum requirement.
Handling Suggestion

(1) Check the connection of antenna cable and ensure it is OK.
(2) Check whether the direction of antenna is suitable (e.g.is there any obstacle surrounding the
antenna?)
6-2

Chapter 6 QoS Alarm
6.3 198092424 Outer Backpanel GNSS receiver has a

satellite searching alarm
This alarm is reported when Outer Backpanel GNSS receiver fails to search satellites or the number
of searched satellites doesn't reach minimum requirement.
Severity
Minor
System Impact
I. Board Status:
Work normally.
Probable Cause
The GNSS receiver fails to search satellites or the number of searched satellites doesn't reach
minimum requirement.
Handling Suggestion
Check the fault of antenna cable.

(1) Check the connection of antenna cable and ensure it is OK.
(2) Check whether the direction of antenna is suitable (e.g.is there any obstacle surrounding the
antenna?)
6.4 198092368 Ethernet remote fault alarm(RDI)

Exchange fault information between MEP.
Severity
Minor
System Impact
6-3

LTE Alarm Handling
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.5 198092380 EFM Link is broken

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.6 198092370 AIS alarm

ETH-AIS stops alarm when service level detects fault.
Severity
Major
6-4

Chapter 6 QoS Alarm
System Impact
Probable Cause
ETH-AIS stops alarm when service level detects fault.
Handling Suggestion
Please check ethernet transmission link.
6.7 198094419 Cell outage

This alarm occurs when a cell is deleted or fails.
Severity
Major
System Impact
The services in the cell are interrupted.
Probable Cause
1. The cell is blocked.

2. The S1 link is faulty.
3. The CC board, BPL board, or RRU in the cell is faulty.
4. The cell configuration fails.
5. The clock is unlocked.
Handling Suggestion
1. Check the detailed alarm information to see whether the Remark field contains content like "Cell
blocked".
l Yes -> Manually unblock the blocked cell, and check whether the alarm is resolved.
2. Check whether there is any alarm related to clock losing lock.
6-5

LTE Alarm Handling
3. Check whether there is any alarm reported by the CC board, BPL board or RRU that the cell uses.
4. Verify that the cell parameter configuration is correct and the data is synchronized to that of the
eNodeB, and check whether the alarm is resolved.
6.8 198094422 eNodeB is out of service

This alarm occurs when all LTE FDD cells of an eNodeB are out of service.
Severity
Critical
System Impact
The eNodeB cannot provide services.
Probable Cause
There is no LTE FDD cell available for the eNodeB, or the LTE FDD cells are faulty or blocked.
Handling Suggestion
1. Check whether there is any cell being blocked.

l Yes -> Unblock the blocked cells. Check whether there are cells becoming available.
à Yes -> Check whether the alarm is resolved.
6-6

Chapter 6 QoS Alarm
2. Perform troubleshooting for the faulty cells in accordance with the solution of the "Cell outage"
alarm. Check whether there are cells becoming available.
l Yes -> Check whether the alarm is resolved.
6.9 198094440 Cell portion is out of service

Cell portion in supper-cell is out of service due to configuration failure or hardware fault.
Severity
Major
System Impact
Service in CP will be interfered.
Probable Cause
1 .IQ resource configuration fail. There is not enough optical bandwidth to support cell portion setup.
2. Carrier configuration fail. Carrier frequency, cell bandwidth or power is beyond RRU capability.
3. RRU fault.
Handling Suggestion
1. Check the detailed alarm information to see whether the Remark field contains "IQ configuration
error".
l Yes -> Change cell parameter configuration according to optical bandwidth. Check if the alarm
is cleared.
l No -> Go to step 2
2. Check the detailed alarm information to see whether the Remark field contains "Carrier
configuration error".
l Yes -> Change carrier frequency, cell bandwidth or power according to RRU capability. Check if
the alarm is cleared.
à Y -> No further action is required.
6-7

LTE Alarm Handling
3. Check the detailed alarm information to see whether the Remark field contains "RRU fault".
l Yes -> Check if there is alarm from RRU which the cell uses. Process the alarm according to its
processing method. Check if the alarm is cleared.
à No -> Please communicate with vendor's customer service.
l No -> Please communicate with vendor's customer service.
6-8

Chapter 7
Notification
Table of Contents
198092059 Alarm Storm.............................................................................................7-2
198092063 Switchover completed..............................................................................7-2
198092064 Switchover failed......................................................................................7-2
198092065 Board switchover failed............................................................................7-3
198092392 Product process fails to power on ............................................................7-3
198092058 Software version recover succeed ...........................................................7-4
198092441 IR changeover successful .......................................................................7-4
198092442 No need for IR changeover ......................................................................7-5
198092440 End of loading product process ...............................................................7-5
198092444 SSCOP fault ...........................................................................................7-5
198092381 EFM Link has error data ..........................................................................7-6
198092031 Board power-on done notification.............................................................7-7
198092054 Slave board powered-on notification ........................................................7-7
198092055 Active-to-standby switchover completed ..................................................7-7
198092056 Standby-to-active switchover completed ..................................................7-8
198092033 Board power-on failed..............................................................................7-8
198092061 Module reset............................................................................................7-9
198092062 Module status error ..................................................................................7-9
198092228 Main board product process power-on ...................................................7-10
198092229 Slave board product process power-on ..................................................7-10
198092297 Uplink optical/electrical link has high BER .............................................7-10
198092271 Local benchmark clock unlocked ...........................................................7-11
198092316 ACOM address conflict ..........................................................................7-12
198092329 ATMA device address conflict ................................................................7-13
198092338 RET device address conflict...................................................................7-13
198096557 Uplink IQ link error .................................................................................7-14
198096566 RRU alarm reset ....................................................................................7-14
198098433 Unavailable alarm of time slot turn-off function .......................................7-15
198097907 Opening of Node B via USB finishes......................................................7-15
198097804 Um interface implements clock synchronization via software. ................7-16
198092034 Bit error has been detected during E1 physical layer in the past 24
hours........................................................................................................................7-16
198092035 E1 link bit error has been detected in the past 24 hours .........................7-17
198092312 PPP Negotiatory IP Conflict ...................................................................7-18
198092314 IP Conflict ..............................................................................................7-18
198092315 Mac Conflict...........................................................................................7-18
198094432 DSP error notification.............................................................................7-19
7-1

LTE Alarm Handling
7.1 198092059 Alarm Storm

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.2 198092063 Switchover completed

The switchover is completed.
System Impact
Switching succeeded.
Probable Cause
Switching succeeded.
Handling Suggestion
None
7.3 198092064 Switchover failed

This alarm is reported when active-to-standby or standby-to-active switchover operation fails.
7-2

Chapter 7 Notification
System Impact
Switching failed.
Probable Cause
Switching failed.
Handling Suggestion
None
7.4 198092065 Board switchover failed

The switchover condition is not satisfied.
System Impact
The main control boards are configured in active/standby mode, but switchover doesn't work. This
reduces system reliability.
Probable Cause
Switchover is not allowed.
Handling Suggestion
None
7.5 198092392 Product process fails to power on

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-3

LTE Alarm Handling
Handling Suggestion
None
7.6 198092058 Software version recover succeed

During the board's power-on process, the flag of the software package is abnormal. Repair the
software package. When the repair succeeds, this notification is reported.
System Impact
I. Board Status:
In a situation of normal start, all peripheral boards won't start normally, let alone bear services.
Probable Cause
Software version recover succeed
Handling Suggestion
Enter software version management interface to download and activate the specification package
again.
7.7 198092441 IR changeover successful

This notification message is reported when IR changeover is successful.
System Impact
None
Probable Cause
IR changeover is successful.
Handling Suggestion
None
7-4

7.8 198092442 No need for IR changeover

This notification message is reported when there is no need for IR changeover.
System Impact
None
Probable Cause
There is no need for IR changeover.
Handling Suggestion
None
7.9 198092440 End of loading product process

This notification is given when product process has been loaded.
System Impact
None
Probable Cause
Product process has been loaded.
Handling Suggestion
None
7.10 198092444 SSCOP fault

SSCOP signaling link is abnormal during data transmission.
7-5

LTE Alarm Handling
System Impact
NBAP and AlCAP signaling data fails to be transmitted and received normally. The service is
interrupted.
Probable Cause
1. Base station clock is faulty.

2. The PVC bandwidth configured for AAL5 at base station side is too small.
3. The transmission is of inferior quality.
Handling Suggestion
1. On the NetNumen M31 fault management interface (Real-time Alarm Monitor), check if related
alarms exist. If yes, follow the corresponding alarm handling suggestions.
Related alarms:
198084019 E1/T1 LOS (Loss Of Signal) alarm
198084022 E1/T1 link loss of IMA frame alarm
198084026 PVC fault
2. Check the configuration of PVC bandwidth.
On Base station configuration management interface, choose IUB Transmission (ATM) > Link Layer
Management, and check the PVC bandwidth at local end and ensure that it is consistent with the
peer end.
3. Reset the board.
7.11 198092381 EFM Link has error data

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.
Handling Suggestion
Please check whether the transport link between base station and the first switchboard is normal.
7-6

7.12 198092031 Board power-on done notification

Board power-on done notification.
System Impact
None
Probable Cause
The board is powered on.
Handling Suggestion
None
7.13 198092054 Slave board powered-on notification

This is a notification message when the slave board is successfully powered on.
System Impact
None
Probable Cause
The standby board is powered on.
Handling Suggestion
None
7.14 198092055 Active-to-standby switchover

completed
Active-to-standby switchover is complete.
7-7

LTE Alarm Handling
System Impact
None
Probable Cause
Active-to-standby switchover notification.
Handling Suggestion
None
7.15 198092056 Standby-to-active switchover

completed
Standby-to-active switchover is complete.
System Impact
None
Probable Cause
Standby-to-active switchover notification.
Handling Suggestion
None
7.16 198092033 Board power-on failed

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.
7-8

Probable Cause
1. process power-on failed.

2. Process power-on timeout.
Handling Suggestion
None
7.17 198092061 Module reset

Module reset.
System Impact
The module has been reset
Probable Cause
The module has been reset
Handling Suggestion
None
7.18 198092062 Module status error

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

2. This abnormity seldom happens. Once it happens, please inform RD center for fault location.
7-9

LTE Alarm Handling
7.19 198092228 Main board product process power-on

Main board product process power-on notification.
System Impact
None
Probable Cause
The process is powered on
Handling Suggestion
None
7.20 198092229 Slave board product process power-on

Slave board product process power-on notification.
System Impact
None
Probable Cause
The process is powered on.
Handling Suggestion
None
7.21 198092297 Uplink optical/electrical link has high

BER
This notification is reported when FS detects that LCV bit error rate at optical port exceeds threshold.
7-10

System Impact
I. Board Status:
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.22 198092271 Local benchmark clock unlocked

This alarm is reported when Local benchmark clock is unlocked on the local benchmark clock.
System Impact
I.Impact on Service:
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.
7-11

LTE Alarm Handling
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 the main control 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 the main control board will cause all services borne on
the board to be interrupted, so please choose proper time to conduct this reset operation).
7.23 198092316 ACOM address conflict

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.
System Impact
No impact on service. Communication of the AISG device formerly affected by address conflict is
restored, but the newly inserted device has not been identified. The newly inserted device can be
identified and managed by base station only after device scan.
Probable Cause
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-12

7.24 198092329 ATMA device address conflict

System Impact
Communication of the AISG device formerly affected by address conflict is restored, but the newly
inserted device has not been identified. The newly inserted device can be identified and managed by
base station only after device scan.
Probable Cause
Handling Suggestion
On Base station configuration management interface management interface, scan AISG in AISG
Devices Centralized Management dialog box then add a new device.
7.25 198092338 RET device address conflict

System Impact
Communication of the AISG device formerly affected by address conflict is restored, but the newly
inserted device has not been identified. The newly inserted device can be identified and managed by
base station only after device scan.
7-13

LTE Alarm Handling
Probable Cause
Handling Suggestion
On base station configuration management interface, scan AISG in AISG Devices Centralized
Management dialog box then add a new device.
7.26 198096557 Uplink IQ link error

IQ link from IQ switch card to base band card error.
System Impact
The quality of service may be affected.
Probable Cause
IQ link exception
Handling Suggestion
Remove and insert boards, including IQ exchange board. If problem exists, replace board.
7.27 198096566 RRU alarm reset

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.
7-14

Handling Suggestion
Replace RRU if it happens frequently
7.28 198098433 Unavailable alarm of time slot turn-off

function
This alarm is reported when time slot turn-off function cannot be used because of some constraints
on PA hardware or status.
System Impact
I. Board 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.29 198097907 Opening of Node B via USB finishes

This notification is reported when opening of Node B via USB finishes.
System Impact
I. Board Status:
Normal
No influence
7-15

LTE Alarm Handling
Probable Cause
Opening of Node B via USB finishes.
Handling Suggestion
None
7.30 198097804 Um interface implements clock

synchronization via software.
This notification is reported when the Um-interface clock is being synchronized via software.
System Impact
I. Board Status:
None
If it is the fast adjustment process to implement Um-interface clock synchronization via software,
calls may be dropped.
Probable Cause
The Um-interface clock is being synchronized via software.
Handling Suggestion
None
7.31 198092034 Bit error has been detected during E1

physical layer in the past 24 hours
Bit error has been detected during E1 physical layer in the past 24 hours.
System Impact
Influence the communication quality.
7-16

Probable Cause
Transmission link has a problem. Do statistics on trunk for 24 hours, then find one of these
abnormalities: 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,
6. Replace the port of repeater (or optical transceiver).
7.32 198092035 E1 link bit error has been detected in

the past 24 hours
E1 link bit error has been detected 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 to measure errored second,
severely errored 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,
6. Replace the port of repeater (or optical transceiver).
7-17

LTE Alarm Handling
7.33 198092312 PPP Negotiatory IP Conflict

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.34 198092314 IP Conflict

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.35 198092315 Mac Conflict

Alarm happens when original Mac in ARP message is the same as interface Mac.
7-18

System Impact
Base station can't communicate.
Probable Cause
The MAC of the station is conflicted.
Handling Suggestion
None
7.36 198094432 DSP error notification

This notification occurs when the DSP becomes faulty.
System Impact

The DSP will be reset.
The service carried by the DSP will be interrupted.
Probable Cause
The DSP is faulty.
Handling Suggestion
Replace the RRU, and check whether the notification is reported any more.
l Yes -> Contact Vendor's Technical Support.
l No -> No further action is required.
7-19

LTE Alarm Handling
7-20

Glossary
ACOM
- Antenna Combiner
- 天线合路器
ADC
- Automatic Device Configuration
- 自动设备配置
AISG
- Antenna Interface Standards Group
- 天线接口标准组
ALCAP
- Access Link Control Application Protocol
- 接入层链路控制应用协议
BBU
- BaseBand Unit
- 基带单元
BFD
- Bidirectional Forwarding Detection
- 双向转发检测
BSP
- Board Support Package
- 板级支持包
CCM
- Communication Control Module
- 通信控制模块
CPU
- Central Processing Unit
- 中央处理器
DAC
- Digital Analog Converter
- 数模转换器
EEPROM
- Electrically Erasable Programmable Read-Only Memory
- 电可擦可编程只读存储器
EFM
- Ethernet in the First Mile
- 第一英里以太网

LTE Alarm Handling
EMC
- Electromagnetic Compatibility
- 电磁兼容性
EPLD
- Erasable Programmable Logic Device
- 可擦除、可编程逻辑器件
FPGA
- Field Programmable Gate Array
- 现场可编程门阵列
HDLC
- High-level Data Link Control
- 高级数据链路控制协议
IMA
- Inverse Multiplexing over ATM
- ATM反向复用
LCP
- Link Control Protocol
- 链路控制协议
LMT
- Local Maintenance Terminal
- 本地维护终端
LNA
- Low Noise Amplifier
- 低噪声放大器
LOS
- Loss Of Signal
- 信号丢失
MAC
- Medium Access Control
- 媒介接入控制
MCU
- Micro Control Unit
- 微控制单元
MEP
- MEG End Point
- MEG终端点
MMC
- Module Management Controller
- 模块管理控制器
II

Glossary
NBAP
- Node B Application Part
- Node B应用部分
NSBT
- NodeB-Side Smart Bias Tee
- 设备供电和控制信号的耦合/解耦
PLL
- Phase Locked Loop
- 锁相环
PSU
- Power Supervision Unit
- 电源监控单元
PVC
- Permanent Virtual Channel
- 永久虚连接
PWR
- Power
- 电源
QoS
- Quality of Service
- 服务质量
RDI
- Remote Defect Indication
- 远端缺陷指示
RET
- Remote Electrical Tilt
- 远程控制电子下倾角
RNC
- Radio Network Controller
- 无线网络控制器
RRU
- Remote Radio Unit
- 远端射频单元
RSSI
- Received Signal Strength Indicator
- 接收信号的强度指示
SCTP
- STREAM CONTROL TRANSMISSION PROTOCOL
- 流控制传输协议
III

LTE Alarm Handling
SNTP
- Simple Network Time Protocol
- 简单网络时间协议
SSCOP
- Service Specific Connection Oriented Protocol
- 业务特定面向连接协议
SSM
- Synchronization Status Message
- 同步状态消息
TAC
- Telecom Alarm Connector
- 电信告警连接器
TCP
- Transmission Control Protocol
- 传输控制协议
TMA
- Tower Mounted Amplifier
- 塔顶放大器
VCI
- Virtual Channel Identifier
- 虚拟通道标识
VPI
- Virtual Path Identifier
- 虚拟通道标识符
IV

SJ-20121112095141-003-LTE (V3.10.10) Alarm Handling (FDD) PDF

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

SJ-20121112095141-003-LTE (V3.10.10) Alarm Handling (FDD) PDF

Diunggah oleh

Hak Cipta:

Format Tersedia

LTE Alarm Handling

Revision No. Revision Date Revision Reason

R1.4 2013-02-05 Correct mistakes on spelling and punctuation.

R1.3 2012-11-08 198094440 is added.

R1.2 2012-10-18 198092215, 198092210 are revised.

R1.1 2012-08-10 These itmes have been updated:

R1.0 2012-06-05 First edition

Serial Number: SJ-20121112095141-003

Publishing Date: 2013-02-05 (R1.4)

SJ-20121112095141-003|2013-02-05 (R1.4) ZTE Proprietary and Confidential

Chapter 3 Equipment Alarm ...................................................................... 3-1

SJ-20121112095141-003|2013-02-05 (R1.4) ZTE Proprietary and Confidential

SJ-20121112095141-003|2013-02-05 (R1.4) ZTE Proprietary and Confidential

SJ-20121112095141-003|2013-02-05 (R1.4) ZTE Proprietary and Confidential

SJ-20121112095141-003|2013-02-05 (R1.4) ZTE Proprietary and Confidential

SJ-20121112095141-003|2013-02-05 (R1.4) ZTE Proprietary and Confidential

SJ-20121112095141-003|2013-02-05 (R1.4) ZTE Proprietary and Confidential

SJ-20121112095141-003|2013-02-05 (R1.4) ZTE Proprietary and Confidential

SJ-20121112095141-003|2013-02-05 (R1.4) ZTE Proprietary and Confidential

Chapter 4 Environment Alarm................................................................... 4-1

SJ-20121112095141-003|2013-02-05 (R1.4) ZTE Proprietary and Confidential

Chapter 5 Processing Alarm ..................................................................... 5-1

SJ-20121112095141-003|2013-02-05 (R1.4) ZTE Proprietary and Confidential

SJ-20121112095141-003|2013-02-05 (R1.4) ZTE Proprietary and Confidential

Chapter 6 QoS Alarm ................................................................................. 6-1

Chapter 7 Notification ................................................................................ 7-1

SJ-20121112095141-003|2013-02-05 (R1.4) ZTE Proprietary and Confidential

SJ-20121112095141-003|2013-02-05 (R1.4) ZTE Proprietary and Confidential

SJ-20121112095141-003|2013-02-05 (R1.4) 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-20121112095141-003|2013-02-05 (R1.4) ZTE Proprietary and Confidential

SJ-20121112095141-003|2013-02-05 (R1.4) ZTE Proprietary and Confidential

Alarm/Notification Information Structure

SJ-20121112095141-003|2013-02-05 (R1.4) ZTE Proprietary and Confidential

SJ-20121112095141-003|2013-02-05 (R1.4) ZTE Proprietary and Confidential

Troubleshooting measures and suggestions are provided. Pay attention to the

SJ-20121112095141-003|2013-02-05 (R1.4) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20121112095141-003|2013-02-05 (R1.4) ZTE Proprietary and Confidential

SJ-20121112095141-003|2013-02-05 (R1.4) ZTE Proprietary and Confidential

2.1 198092240 1588 clock link fault

This alarm is reported in one of the following situations:

1. It is impossible to communicate with master clock of this link.

1. Check whether the physical connection to CC is normal.

2.2 198092411 BITS clock fault

SJ-20121112095141-003|2013-02-05 (R1.4) ZTE Proprietary and Confidential

1. The configured clock reference source doesn't exist.

1. Check whether wrong reference source is configured.

2.3 198092361 IMA group has fault

SJ-20121112095141-003|2013-02-05 (R1.4) ZTE Proprietary and Confidential

1. Transport relay equipment has fault or configuration is not right.

2.4 198092362 IMA/TC link has fault

1. Transport relay equipment has fault or configuration is error.

SJ-20121112095141-003|2013-02-05 (R1.4) ZTE Proprietary and Confidential

1. Check the link configuration between base station and RNC:

2.5 198092230 SCTP association is interrupted