ZTE LTE Alarm and Notification Handling Reference

ZXSDR UniBTS
Base Station
Alarm and Notification Handling Reference
V4.13.10.20
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://support.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2014 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit the ZTE technical support website http://support.zte.com.cn to inquire for related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R1.0 2014–06–30 First Edition
Serial Number: SJ-20140610145724-023
Publishing Date: 2014-06-30（R1.0）
SJ-20140610145724-023|2014-06-30（R1.0） ZTE Proprietary and Confidential

Contents
About This Manual ......................................................................................... I
Chapter 1 Overview .................................................................................... 1-1
1.1 Overview of Fault Management........................................................................... 1-1
1.2 Fault View.......................................................................................................... 1-1
1.2.1 Alarm ...................................................................................................... 1-1
1.2.2 Notification............................................................................................... 1-1
1.3 Alarm Information Structure ................................................................................ 1-2
1.4 Notification Information Structure......................................................................... 1-3
Chapter 2 Alarm.......................................................................................... 2-1

2.1 Equipment Alarm................................................................................................ 2-1
2.1.1 198093022 The board is powered off due to overtemperature ..................... 2-1
2.1.2 198093023 GPS clock reference source lost major alarm ........................... 2-3
2.1.3 198093024 GPS clock reference source lost critical alarm .......................... 2-4
2.1.4 198093028 E1 port of local switch is overflowing. ....................................... 2-6
2.1.5 198093050 The input clock of the board is abnormal. ................................. 2-7
2.1.6 198093051 Internal clock of the board is abnormal. .................................... 2-8
2.1.7 198093052 Board internal communication interface alarm ........................ 2-10
2.1.8 198093053 Carrier uplink data is abnormal .............................................. 2-13
2.1.9 198093054 DSP of the board runs abnormally ......................................... 2-14
2.1.10 198093055 DSP hardware detection fails............................................... 2-15
2.1.11 198093060 Device power down............................................................. 2-16
2.1.12 198093061 The optical module is not in position..................................... 2-17
2.1.13 198093062 Optical module fault ............................................................ 2-18
2.1.14 198093814 Clock has a critical alarm..................................................... 2-19
2.1.15 198093853 Abnormal RF power ............................................................ 2-22
2.1.16 198094010 Imbalanced Rx antenna ...................................................... 2-23
2.1.17 198093863 Failure alarm while raising the voltage of adjustable power ..... 2-24
2.1.18 198093864 RTWP abnormal ................................................................. 2-25
2.1.19 198094028 Software runs abnormally .................................................... 2-26
2.1.20 198094029 The baseband service is abnormal....................................... 2-27
2.1.21 198094030 The uplink data verification is abnormal. .............................. 2-29
2.1.22 198096407 Heat exchanger alarm ......................................................... 2-32
2.1.23 198096408 FCE board not-configured alarm .......................................... 2-32

2.1.24 198096412 Too close GU frequency spacing alarm ................................ 2-34
2.1.25 198096413 TAM channel disabled due to over current ............................ 2-35
2.1.26 198096416 Tower mounted amplifier power alarm .................................. 2-36
2.1.27 198096418 LNA Branch Broken ............................................................ 2-38
2.1.28 198096420 Too close GL frequency spacing alarm ................................. 2-39
2.1.29 198096421 Base station saves energy .................................................. 2-40
2.1.30 198096424 User-defined dry contact alarm 51 ....................................... 2-41
2.1.60 198096454 User-defined dry contact alarm 81 ......................................2-101
II

2.1.65 198096459 User-defined dry contact alarm 86 ...................................... 2-111
2.1.79 198096473 User-defined dry contact alarm 100.....................................2-139
2.1.80 198096474 Wrong configuration of site type ..........................................2-141
2.1.81 198096475 Wrong configuration of cabinet type ....................................2-142
2.1.82 198096490 TAM Channel over/under-current ........................................2-143
2.1.83 198092215 Lost of synchronization.......................................................2-145
2.1.84 198092289 The optical module is not in position....................................2-146
2.1.85 198092433 RRU physical layer link is interrupted ..................................2-147
2.1.86 198098313 Optical module fault ...........................................................2-148
2.1.87 198092550 User-defined dry contact alarm 1 ........................................2-149
2.1.97 198092560 User-defined dry contact alarm 11.......................................2-169
III

2.1.110 198092573 User-defined dry contact alarm 24 .....................................2-195
2.1.118 198092581 User-defined dry contact alarm 32 ..................................... 2-211
IV

2.1.137 198100277 The baseband signal input to the TX channel is
abnormal .............................................................................................2-249
2.1.138 198092049 Lightning protection device alarm ......................................2-250
2.1.139 198092051 PSU alarm.......................................................................2-252
2.1.140 198092052 PSU fan alarm .................................................................2-253
2.1.141 198092057 The board is powered off ..................................................2-255
2.1.142 198092068 Main power supply has a fault alarm .................................2-258
2.1.143 198092069 FCE fan failure.................................................................2-260
2.1.144 198092071 Temperature sensor abnormal .........................................2-261
2.1.145 198092072 The board is not in position...............................................2-263
2.1.146 198092073 Embedded power AC-in Switch Off ...................................2-264
2.1.147 198092074 Embedded power AC Power Off .......................................2-266
2.1.148 198092075 Embedded power SPD-C Broken ......................................2-268
2.1.149 198092076 Embedded power SPD-D Broken ......................................2-270
2.1.150 198092077 Embedded power AC Under-Volt ......................................2-271
2.1.151 198092078 Embedded power AC Over-Volt ........................................2-273
2.1.152 198092079 Embedded power AC Current Over ...................................2-275
2.1.153 198092080 Embedded power SMR Over-Vout ....................................2-277
2.1.154 198092081 Embedded power SMR Over-Iout......................................2-277
2.1.155 198092082 Embedded power SMR Fan Fault .....................................2-278
2.1.156 198092083 Embedded power SMR PFC Fault ....................................2-280
2.1.157 198092084 Embedded power SMR Over-Vin Off .................................2-281
2.1.158 198092085 Embedded power SMR Under-Vin Off ...............................2-282
2.1.159 198092086 Embedded power SMR H.T. Off ........................................2-283
2.1.160 198092087 Embedded power SMR Env.H.T.Off...................................2-284
2.1.161 198092088 Embedded power SMR Env.H.T........................................2-285
2.1.162 198092089 Embedded power SMR L.Vin ............................................2-286
2.1.163 198092090 Embedded power SMR Fuse Broken.................................2-287
2.1.164 198092091 Embedded power SMR CommFail ....................................2-288
2.1.165 198092092 Embedded power DC Under-Volt ......................................2-290
2.1.166 198092093 Embedded power DC Over-Volt ........................................2-292
2.1.167 198092094 Embedded power DC Loop Broken ...................................2-294
2.1.168 198092095 Embedded power Bat Loop Broken ...................................2-296
2.1.169 198092096 Embedded power Bat Under-Volt ......................................2-298
2.1.170 198092097 Embedded power Bat Over-Temp .....................................2-300
2.1.171 198092098 Embedded power TmpL Shut-Down..................................2-302

2.1.172 198092099 Embedded power 1st Shut-down ......................................2-303
2.1.173 198092100 Embedded power 2nd Shut-down .....................................2-305
2.1.174 198092101 Embedded power DC SPD Broken....................................2-308
2.1.175 198092102 Embedded power DC Breaker Alarm.................................2-309
2.1.176 198092103 Embedded power Bat Test Failure.....................................2-310
2.1.177 198092104 Embedded power Bat Discharge....................................... 2-311
2.1.178 198092116 Embedded power AC Auxiliary Output Switch Off ...............2-313
2.1.179 198092117 Embedded power Rectifier Module Fault............................2-315
2.1.180 198092203 The board is not configured ..............................................2-317
2.1.181 198092206 Battery alarm ...................................................................2-318
2.1.182 198092207 AC power-cut alarm .........................................................2-320
2.1.183 198092208 Rectifier module alarm .....................................................2-322
2.1.184 198092209 Thermoelectric cooler alarm..............................................2-324
2.1.185 198092217 No available clock source at air-interface...........................2-326
2.1.186 198092234 Embedded power type configuration error .........................2-328
2.1.187 198092235 Embedded power communication interruption....................2-329
2.1.188 198092236 Embedded power SMR Output Fault .................................2-330
2.1.189 198092237 Embedded power Bat Under-Temp ...................................2-331
2.1.190 198092238 Embedded power Bat Invalid-Temp ...................................2-333
2.1.191 198092239 Embedded power Battery Fault .........................................2-334
2.1.192 198092259 Battery low-voltage alarm .................................................2-336
2.1.193 198092260 Faulty external device connected at a dry contact ..............2-338
2.1.194 198092261 Outdoor lightning protection box alarm ..............................2-340
2.1.195 198092262 Breaker alarm in indoor lightning protection box .................2-341
2.1.196 198092263 Lightning protection device alarm in indoor lightning
protection box ......................................................................................2-344
2.1.197 198092264 Over-voltage alarm of main power input ............................2-346
2.1.198 198092265 Main power input power-cut alarm.....................................2-348
2.1.199 198092266 Under-voltage alarm of main power input...........................2-351
2.1.200 198092267 General fault of main power ..............................................2-353
2.1.201 198092268 PWR monitoring unit alarm ...............................................2-355
2.1.202 198092292 Optical fiber connection error ............................................2-357
2.1.203 198092295 Device power down..........................................................2-358
2.1.204 198092363 Faulty main power alarm ..................................................2-359
2.1.205 198092394 Several faulty rectifiers .....................................................2-361
2.1.206 198092426 The GNSS cascading clock is faulty ..................................2-362
2.1.207 198092435 Inter-subrack Ethernet link broken in stack mode ...............2-365
2.1.208 198092447 Unbalanced AC phase voltage of built-in power .................2-366
VI

2.1.209 198092448 High AC phase current of built-in power.............................2-367
2.1.210 198092449 Missing AC phase voltage of built-in power........................2-369
2.1.211 198092450 Battery low-voltage cut-off of built-in power ........................2-371
2.1.212 198092451 Broken LLVD1 branch E of built-in power...........................2-373
2.1.213 198092452 Broken LLVD1 branch of built-in power..............................2-375
2.1.214 198092453 Broken LLVD2 branch E of built-in power...........................2-377
2.1.215 198092454 Broken battery cut-off branch E of built-in power ................2-379
2.1.216 198092455 Broken battery cut-off branch of built-in power ...................2-381
2.1.217 198092456 Abnormal battery current of built-in power..........................2-383
2.1.218 198092457 Abnormal CAN bus of built-in power..................................2-384
2.1.219 198092458 Abnormal battery of built-in power .....................................2-385
2.1.220 198092459 Abnormal input dry contact of built-in power.......................2-386
2.1.221 198092460 High-temperature cut-off of built-in power ..........................2-387
2.1.222 198092461 Failure in frame synchronization between BBU
subracks .............................................................................................2-389
2.1.223 198096830 Too large phase difference between clock sources .............2-391
2.1.224 198096831 1588 clock source fault.....................................................2-394
2.1.225 198096835 GNSS receiver fault .........................................................2-396
2.1.226 198096836 GNSS antenna feeder link fault .........................................2-402
2.1.227 198096838 Clock source abnormal in stack mode ...............................2-405
2.1.228 198097004 Board hardware fault ........................................................2-406
2.1.229 198097060 Board communication link interrupted................................2-407
2.1.230 198097109 E1/T1 link is interrupted....................................................2-409
2.1.231 198098111 Fan failure........................................................................2-410
2.1.232 198098251 The working mode of the Ethernet port doesn't match the
peer end ............................................................................................. 2-411
2.1.233 198098314 Inter-board data link abnormal. .........................................2-412
2.1.234 198098315 Input clock of the board abnormal. ....................................2-413
2.1.235 198098318 Unavailable optical module ..............................................2-415
2.1.236 198098440 Disable PA.......................................................................2-417
2.1.237 198098465 VSWR of the antenna feeder abnormal .............................2-418
2.1.238 198098466 Temperature abnormal .....................................................2-420
2.1.239 198098467 Internal fault ....................................................................2-421
2.1.240 198098468 External extended device fault ..........................................2-422
2.1.241 198098469 Abnormal RX channel ......................................................2-427
2.1.242 198098470 Blocked resources manually .............................................2-429
2.1.243 198098471 Carrier downlink data problem ..........................................2-430
2.1.244 198098472 RRU Power Abnormal Alarm ............................................2-431
VII

abnormal .............................................................................................2-433
2.1.246 198100280 The output power of the TX channel is abnormal................2-434
2.1.247 198100283 Smart antenna calibration is abnormal...............................2-435
2.1.248 198094400 Downlink digital power exceeds threshold..........................2-437
2.1.249 198094401 Downlink analog power exceeds threshold ........................2-438
2.1.250 198094402 The difference of digital and analog power is abnormal.......2-439
2.1.251 198094403 Antenna feeder VSWR alarm ...........................................2-440
2.1.252 198094404 Antenna feeder VSWR serious alarm ................................2-442
2.1.253 198094405 Slight-high temperature of PA ...........................................2-444
2.1.254 198094406 Over-high temperature of PA ............................................2-446
2.1.255 198094407 RRU power supply abnormal ...........................................2-447
2.1.256 198094408 RRU RF PLL unlock.........................................................2-448
2.1.257 198094409 Abnormal temperature of board ........................................2-449
2.1.258 198094412 Fault in BPL clock ...........................................................2-450
2.1.259 198094413 Fault in BPL hardware......................................................2-451
2.1.260 198094414 Discontinuous frame number ............................................2-452
2.1.261 198094415 Frame frequency abnormal...............................................2-454
2.1.262 198094425 Optical module temperature is abnormal............................2-456
2.1.263 198094426 Optical module bias current is abnormal ............................2-456
2.1.264 198094427 Optical module transmit power is abnormal........................2-457
2.1.265 198094428 Optical module inner voltage is abnormal ..........................2-458
2.1.266 198094431 RSSI power is abnormal ...................................................2-459
2.1.267 198094437 RRU power-cut alarm ......................................................2-460
2.1.268 198094441 RRU feedback power exceeds threshold ...........................2-461
2.2 Communication Alarm .....................................................................................2-462
2.2.1 198093027 IPTB local switch setup fails. ................................................2-462
2.2.2 198093057 No optical signal is received at the optical port.......................2-463
2.2.3 198093058 Optical fiber connection error................................................2-465
2.2.4 198093059 The frames received at the optical port lose lock....................2-466
2.2.5 198096410 Heat exchanger's communication data lost alarm ..................2-468
2.2.6 198092286 Loss of frames to be received at the optical port ...................2-469
2.2.7 198092290 No optical signal is received at the optical port.......................2-472
2.2.8 198092431 The received optical power of the optical module is
abnormal .............................................................................................2-474
2.2.9 198092013 High BER rate at the E1/T1 link ............................................2-476
2.2.10 198092230 The SCTP association is broken .........................................2-477
2.2.11 198092231 The PPP link is broken .......................................................2-479
VIII

2.2.12 198092232 The HDLC link is broken.....................................................2-480
2.2.13 198092233 The SSCOP link is broken ..................................................2-481
2.2.14 198092361 The IMA group is faulty ......................................................2-483
2.2.15 198092362 The IMA/TC link is faulty.....................................................2-484
2.2.16 198092399 The BFD connection is broken............................................2-485
2.2.17 198092401 E1/T1 link self-loop ............................................................2-487
2.2.18 198092402 The TCP connection is broken............................................2-488
2.2.19 198092428 The SCTP path is broken ...................................................2-490
2.2.20 198096839 RRU inner GNSS clock source abnormal ............................2-491
2.2.21 198097169 The next hop IP is unreachable...........................................2-492
2.2.22 198097171 Authentication failure..........................................................2-493
2.2.23 198097172 Configuration parameter of OAM Channel is wrong..............2-495
2.2.24 198098252 The physical Ethernet link is broken ...................................2-496
2.2.25 198098319 Optical port receiving link failure .........................................2-497
2.2.26 198094416 CPRI link abnormal ............................................................2-500
2.2.27 198094420 S1 link is broken ................................................................2-503
2.2.28 198094421 X2 link is broken ................................................................2-505
2.2.29 198094430 The strength of received optical signal is abnormal ..............2-507
2.2.30 198094455 All MME associations interrupted ........................................2-509
2.3 Wrong Operation Alarm ...................................................................................2-510
2.3.1 198093020 Software run-time exceptions ...............................................2-510
2.3.2 198093021 Config error alarm................................................................2-512
2.3.3 198093056 Software loading is abnormal................................................2-514
2.3.4 198093922 Board configuration parameter error......................................2-515
2.3.5 198093939 Insufficient IQ channel resource............................................2-516
2.3.6 198093955 Number of RACH packets in a cell exceeds alarm
threshold .............................................................................................2-517
2.3.7 198094027 BBS parameters are not matched .........................................2-518
2.3.8 198093981 Digital PA over power alarm .................................................2-519
2.3.9 198092014 SNTP time adjustment failure ...............................................2-521
2.3.10 198092017 Software loading failure......................................................2-523
2.3.11 198092019 Failure in active/standby synchronization .............................2-523
2.3.12 198092027 Failure in repairing a version package .................................2-524
2.3.13 198092029 Hardware type is different from the configuration .................2-525
2.3.14 198092066 Failure in uncompressing the LMT software.........................2-528
2.3.15 198092070 Initialization failure .............................................................2-528
2.3.16 198092348 The board is being initialized ..............................................2-529
2.3.17 198092390 CPU over loading highly .....................................................2-530
IX

2.3.18 198092391 CPU over loading...............................................................2-531
2.3.19 198092395 Running software rollback ..................................................2-532
2.3.20 198092396 Hot patch fault ...................................................................2-533
2.3.21 198092397 Failure in finding the board-related software ID ....................2-533
2.3.22 198092443 IR changeover failure .........................................................2-535
2.3.23 198096551 RRU unconfigured .............................................................2-536
2.3.24 198096832 Line clock source fault........................................................2-537
2.3.25 198096833 SyncE clock fault ...............................................................2-541
2.3.26 198096834 1PPS+TOD clock source fault.............................................2-544
2.3.27 198097050 Baseband unit is being initialized ........................................2-548
2.3.28 198097404 Resource usage rate is too high..........................................2-549
2.3.29 198097510 The NE does not support the configured parameters ...........2-550
2.3.30 198097511 Parameter configuration error .............................................2-556
2.3.31 198097567 Version package fault.........................................................2-563
2.3.32 198097568 Version repository file problem............................................2-564
2.3.33 198097604 Software runs abnormally ...................................................2-565
2.3.34 198097605 The RRU link is broken .....................................................2-567
2.3.35 198097613 LMT is logged in ................................................................2-569
2.3.36 198097650 Configuration Data Loading Abnormal .................................2-570
2.3.37 198097670 The system has no the available License file .......................2-571
2.3.38 198097671 The optional feature is not usable .......................................2-571
2.3.39 198098464 Parameter configuration error .............................................2-572
2.3.40 198100275 RRU software version is abnormal ......................................2-576
2.3.41 198100276 RRU fiber delay beyond the limit .........................................2-577
2.3.42 198094411 Board configuration parameter error ....................................2-578
2.3.43 198094418 Rule library of performance statistics hasn't been loaded or
loaded unsuccessfully ..........................................................................2-579
2.3.44 198094429 Optical module rate does not match ....................................2-580
2.3.45 198094442 Cell parameter configuration failure.....................................2-581
2.3.46 198094461 Cell shutdown alarm ..........................................................2-583
2.4 Environment Alarm..........................................................................................2-583
2.4.1 198096400 Device temperature is high ...................................................2-583
2.4.2 198096491 Cabinet temperature is abnormal ..........................................2-584
2.4.3 198092042 The temperature at the air intake is abnormal ........................2-586
2.4.4 198092044 Door control alarm ...............................................................2-587
2.4.5 198092045 Flooding alarm ....................................................................2-590
2.4.6 198092046 Smog alarm.........................................................................2-592
2.4.7 198092047 Infrared alarm......................................................................2-594

2.4.8 198092048 Air conditioner fault ..............................................................2-597
2.4.9 198092053 The input voltage is abnormal...............................................2-599
2.4.10 198092105 Embedded power Environment is under-temperature ...........2-601
2.4.11 198092106 Embedded power Environment is over-temperature .............2-602
2.4.12 198092107 Embedded power Environment temperature is invalid ..........2-604
2.4.13 198092108 Embedded power Environment is under-Humidity ................2-605
2.4.14 198092109 Embedded power Environment is over-Humidity ..................2-606
2.4.15 198092110 Embedded power Environment humidity is invalid ................2-608
2.4.16 198092111 Embedded power Smoke detected ......................................2-609
2.4.17 198092112 Embedded power Flood detected........................................2-610
2.4.18 198092113 Embedded power Door Magnet Alarm .................................2-612
2.4.19 198092114 Embedded power Gate Embedded power Safety Alarm........2-613
2.4.20 198092115 Glass Broken Alarm ...........................................................2-615
2.4.21 198092118 Embedded power Env-unit communication interruption.........2-617
2.4.22 198092119 Embedded power Heat Exchanger Fault..............................2-618
2.4.23 198092462 Blocked dust proof net .......................................................2-620
2.4.24 198097061 Temperature abnormal .......................................................2-621
2.4.25 198098128 Power over-loaded ............................................................2-623
2.4.26 198092550~198092599 Battery pack fan failed. ....................................2-624
2.5 QoS Alarm......................................................................................................2-626
2.5.1 198093817 Clock has significant alarm ...................................................2-626
2.5.2 198094025 Cell finds no traffic ...............................................................2-628
2.5.3 198092368 Ethernet RDI alarm ..............................................................2-629
2.5.4 198092380 The EFM link is broken ........................................................2-630
2.5.5 198096837 GNSS receiver satellite searching fault .................................2-632
2.5.6 198094419 Cell outage..........................................................................2-634
2.5.7 198094422 eNodeB is out of service ......................................................2-637
2.5.8 198094444 PCI conflict alarm ................................................................2-637
2.5.9 198094445 PCI confusion alarm.............................................................2-639
2.5.10 198094446 MRO fault alarm ................................................................2-640
2.5.11 198094452 Different vendor PCI conflict alarm ......................................2-641
2.5.12 198094453 Different vendor PCI confusion alarm ..................................2-642
2.5.13 198094454 Different vendor MRO fault alarm........................................2-644
2.5.14 198094456 Cell sleeping alarm ............................................................2-645
2.5.15 198094457 Cell performance deterioration alarm...................................2-646
2.5.16 198094458 Cell cooperating parameter configuration abnormal..............2-647
2.5.17 198094459 The system capacity will exceed the License limit ................2-648
XI

Chapter 3 Notification ................................................................................ 3-1
3.1 198093025 Base station access notification ......................................................... 3-2
3.2 198093026 RU Channel is calibrating or testing ................................................... 3-3
3.3 198093063 The received optical power of the optical module is abnormal .............. 3-3
3.4 198093064 Radio parameter requests timeout ..................................................... 3-5
3.5 198093065 Radio parameter requests respond .................................................... 3-6
3.6 198093997 Cell deletion notification .................................................................... 3-7
3.7 198096477 Board reboots................................................................................... 3-8
3.8 198092031 Board initialization process completes................................................ 3-9
3.9 198092033 Board power-on failed ....................................................................... 3-9
3.10 198092034 Bit error has been detected during E1 physical layer in the past 24
hours ............................................................................................................. 3-10
3.11 198092035 E1 link bit error has been detected in the past 24 hours ....................3-11
3.12 198092058 Software version recover succeed ................................................. 3-12
3.13 198092059 Alarm Storm ................................................................................. 3-12
3.14 198092063 Switchover completes ................................................................... 3-13
3.15 198092271 Local benchmark clock unlocked ................................................... 3-14
3.16 198092312 PPP Negotiatory IP Conflict ........................................................... 3-15
3.17 198092314 IP Conflict .................................................................................... 3-16
3.18 198092315 Mac Conflict ................................................................................. 3-17
3.19 198092381 EFM Link has error data ................................................................ 3-18
3.20 198092392 Product process fails to power on .................................................. 3-19
3.21 198092441 IR changeover successful.............................................................. 3-20
3.22 198092442 No need for IR changeover............................................................ 3-20
3.23 198092444 SSCOP fault................................................................................. 3-21
3.24 198096557 Uplink IQ link error ........................................................................ 3-22
3.25 198096566 RRU alarm reset ........................................................................... 3-22
3.26 198097804 Um interface implements clock synchronization via software ........... 3-23
3.27 198097805 MP voltage abnormal .................................................................... 3-24
3.28 198097806 PP voltage abnormal..................................................................... 3-25
3.29 198097864 Product process power-on completes............................................. 3-26
3.30 198097865 Switchover fails............................................................................. 3-27
3.31 198097866 port Active/standby switchover notification...................................... 3-27
3.32 198097867 Power Amplifier (PA) switch for smart carrier power-on/off ............... 3-29
3.33 198097907 Opening of Node B via USB finishes .............................................. 3-30
3.34 198097964 LCK indication .............................................................................. 3-30
3.35 198097965 CCM Remote MEP Error ............................................................... 3-32
3.36 198097966 CCM Message Error ..................................................................... 3-33
XII

3.37 198097967 CCM Xconnect Error ..................................................................... 3-34
3.38 198097968 AIS indication ............................................................................... 3-35
3.39 198098000 Unavailable POD .......................................................................... 3-36
3.40 198098001 Unconfigured POD........................................................................ 3-38
3.41 198098002 The License is entering to trying urgency state ............................... 3-39
3.42 198098003 The license file will soon fall due .................................................... 3-40
3.43 198098004 The configuration data exceeds the License limit ............................ 3-40
3.44 198098316 The received optical power is abnormal.......................................... 3-41
3.45 198098459 Unavailable alarm of time slot turn-off function ................................ 3-43
3.46 198094410 PA shutdown notification ............................................................... 3-44
3.47 198094432 DSP error notification .................................................................... 3-45
3.48 198094449 Cloud scheduling cell link fault ....................................................... 3-46
3.49 198094450 Whole-band scanning start ............................................................ 3-48
3.50 198094451 Whole-band scanning end ............................................................. 3-48
3.51 198094857 The system capacity will exceed the License limit ........................... 3-49
Glossary .......................................................................................................... I
XIII

This page intentionally left blank.
XIV

About This Manual
Purpose
This manual introduces the alarms and notifications that might occur during the installation,
operation, and maintenance of ZTE ZXSDR UniBTS product. Alarm/Notification code and
description displayed by NetNumen M31™, possible causes for these alarms/notifications,
and the corresponding handling suggestions are covered in this manual.
Intended Audience
l Commissioning engineer
l Maintenance engineer
l Network management engineer
What Is in This Manual
Chapter Summary
Chapter 1, Overview Introduces the concept of fault management, as

well as the definition, type, level classification of
alarm and notification.
Chapter 2, Alarm Introduces ZXSDR UniBTS alarms.
Chapter 3, Notification Introduces ZXSDR UniBTS notifications.
Related Documentation
The following documentation is related to this manual:
l 《 ZXSDR UniBTS (V4.13) MOM User Guide 》
l 《 Components Replacement 》

II

Chapter 1
Overview
Table of Contents
Overview of Fault Management ..................................................................................1-1
Fault View ..................................................................................................................1-1
Alarm Information Structure........................................................................................1-2
Notification Information Structure................................................................................1-3
1.1 Overview of Fault Management

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 realtime 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.
1.2 Fault View

Fault is displayed in the form of alarm or notification.
1.2.1 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.
1.2.2 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.
1-1

ZXSDR UniBTS Alarm and Notification Handling Reference
1.3 Alarm Information Structure

Alarm Property
1. Alarm Code
Alarm Code is the identifier which differentiates alarms.
Alarm Code is defined by a 32-bit field indicating the specific code value.
2. Alarm level
There are four alarm levels, which are indicated in descending order of severity as
Critical, Major, Minor, and Warning.
l Critical alarm causes system breakdown and service interruption. It requires
immediate troubleshooting.
l Major alarm significantly affects system operation or weakens network service
capability. It requires troubleshooting as soon as possible.
l Minor alarm affects system operation and network service capability in a
non significant way. It requires timely troubleshooting so as to avoid severity
escalation.
l Warning 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:
l Alarm severity can be modified in NetNumenM31 NMS (network management
system) if necessary.
l Generally speaking, the default alarm severity is reasonably set. Users should
think twice before making any modification.
In addition, the severity of a few alarms is undefined. It is up to users to define the

severity of such alarms.
3. Alarm Type
Alarm is classified into five types 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).
1-2

Chapter 1 Overview
l Wrong operation alarm: related with software or operation fault (ITU-T

Recommendation X.733).
l Environment alarm: related with the environment where the equipment is lo-
cated (ITU-T Recommendation X.733).
l QoS alarm: related with degradation of service quality (ITU-T Recommendation
X.733).
Impact
It refers to the impact that the alarm incurs on boards and services.
Alarm Cause
Possible alarm causes are enumerated to help users troubleshoot, find preventive
measures, and restore the system to normal state in a timely manner.
Action
Troubleshooting measures and suggestions are provided. Pay attention to the following
tips when handling alarms.
l After recording the fault phenomenon, Operation & Maintenance personnel may
handle the fault step by step as described in the Handling Suggestion Section of this
manual. If the fault is removed (alarm restored) at any handling step, terminate the
handling process. If the fault is not removed, go ahead to the next handling step.
l If the fault cannot be removed, contact the local ZTE office as soon as possible.
1.4 Notification Information Structure

Notification Property
1. Notification Code
Notification code is the identifier to differentiate notifications.
Notification code is defined by a 32-bit field indicating the specific code value.
2. Alarm level
There is only one notification severity level: Notification.
Impact
It refers to the impact that the notification incurs on boards and services.
Alarm Cause
Possible notification causes are enumerated to help users troubleshoot, find preventive
measures, and restore the system to normal state in a timely manner.
1-3

Action
Troubleshooting measures and suggestions are provided. Pay attention to the following
tips when handling alarms.
l After recording the fault phenomenon, Operation & Maintenance personnel may
handle the fault step by step as described in the Handling Suggestion Section of this
manual. If the fault is removed (alarm restored) at any handling step, terminate the
handling process. If the fault is not removed, go ahead to the next handling step.
l If the fault cannot be removed, contact the local ZTE office as soon as possible.
1-4

Chapter 2
Alarm
Table of Contents
Equipment Alarm........................................................................................................2-1
Communication Alarm ............................................................................................2-462
Wrong Operation Alarm..........................................................................................2-510
Environment Alarm.................................................................................................2-583
QoS Alarm .............................................................................................................2-626
2.1 Equipment Alarm

2.1.1 198093022 The board is powered off due to overtemperature
Alarm Information
l Alarm code: 198093022
l Name: The board is powered off due to overtemperature
l Alarm severity: Critical
l Alarm type: Equipment alarm
Detailed Description
The UBPG board is powered off due to too high temperature.
Alarm Cause
1. The fan is stopped.
2. The FA board is not in position.
Impact
1. Board status:
The board is faulty
2. Service impact:
The services may be affected.
Action
1. Check whether the fan is stopped.
If yes, go to step 2.
2-1

If no, go to step 3.
2. Replace the fan immediately to prevent the board from burning due to rapid increase in
temperature. Wait for five minutes after the fan is replaced and check whether the alarm
is cleared.
If yes, no further action is required.
3. Check whether there is "the SA board is not in position" alarm (198097055) or "Board
communication link interrupted" alarm (198097060) or "Hardware type is different from
the configuration" alarm (198097558). If there is any, handle the alarm according to the
corresponding alarm handling suggestion. Check whether the alarm is cleared.
4. Reset the SA board. Wait for 15 minutes and check whether the alarm is cleared.

5. Unplug and plug the SA board. Wait for 15 minutes and check whether the alarm is
cleared.
6. Replace the SA board. Wait for 15 minutes and check whether the alarm is cleared.
7. Check whether the environmental temperature is too high and whether the air
conditioners are operating properly.
8. Reduce the environmental temperature. After that, wait for five minutes and check
whether the alarm is cleared.

9. Replace the board for which the alarm is reported in accordance with the rack No., shelf
No. and slot No. in the detailed alarm information. Wait for 15 minutes and check whether
the alarm is cleared.
If no, contact the ZTE technical support.
2-2

Chapter 2 Alarm
2.1.2 198093023 GPS clock reference source lost major alarm

Alarm Information
l Name: GPS clock reference source lost major alarm
l Alarm severity: Major
When the CC board fails to detect the external reference clock source signal, the CC board
enters the free oscillation state. When the timeout time reaches the threshold that the
operator has set for major alarms, the clock reference source major alarm is reported.
Alarm Cause
1. The configured GPS reference clock source does not exist.
2. The board is faulty.
3. The cables are faulty.
Impact
1. Board status:
The board is operating properly.
2. Service impact:
Case 1: If the reference clock is lost, the system selects an available reference clock with
the highest priority in accordance with the priority configuration, and the system operation
will not be affected.
Case 2: If all reference clocks are lost, the system clock stays at the remaining state or
the free oscillation state. The possible impacts are: 1) Iub interface: If E1 is used at the
Iub interface, periodical slip code may occur at the Iub interface. If FE is used at the
Iub interface, the services will not be affected. 2)Inter-NodeB soft handover: If the alarm
persists for a long time and cannot be cleared, the Node B clock precision may not meet
the 3GPP requirement due to aging, and the soft handover success rate may be affected.
Action
1. Check whether relevant alarms exist.
1. Check whether there is any relevant alarm. If yes, handle the alarms in accordance
with the relevant alarm handling suggestions. The relevant alarms are:
GNSS antenna feeder link fault (198096836)
GNSS receiver satellite searching fault (198096837)
GNSS receiver fault (198096835)
2-3

b. Check whether the alarm is cleared.

2. In accordance with the rack No., shelf No., and slot No. in the alarm details, power off
and reset the board.
Wait for 15 minutes and check whether the alarm is cleared.
3. In accordance with the rack No., shelf No., and slot No. in the alarm details, unplug and
plug the board.
4. In accordance with the rack No., shelf No., and slot No. in the alarm details, replace
2.1.3 198093024 GPS clock reference source lost critical alarm

Alarm Information
l Name: GPS clock reference source lost critical alarm
When the CC board fails to detect the signals from the external reference clock source, the
CC board enters the free oscillation state. When the timeout time reaches the threshold
that the operator has set for critical alarms, the clock reference source critical alarm is
reported.
Alarm Cause
1. The configured GPS reference clock source does not exist.
3. The cables are faulty.
2-4

Chapter 2 Alarm
Impact
1. Board status:
2. Service impact:
Case 1: If the reference clock is lost, the system selects an available reference clock with
the highest priority in accordance with the priority configuration, and the system operation
is not affected.
Case 2: If all reference clocks are lost, the system clock stays at the remaining state
or the free oscillation state. The possible impacts are: 1) Iub interface: If E1 is used
at the Iub interface, periodical slip code may occur at the Iub interface. If FE is used
at the Iub interface, the services will not be affected. 2)Inter-NodeB soft handover: If
the alarm persists for a long time and cannot be cleared, the Node B clock precision
may not meet the 3GPP requirement due to aging, and the soft handover success rate
may be affected. 3) If the synchronization mode is frame number synchronization, the
system cannot ensure frame number synchronization any more. If the synchronization
mode is frequency synchronization, the system cannot ensure frequency synchronization
any more.
Action
1. Check whether there is any relevant alarm.
1. Check whether there is any relevant alarm. If yes, handle the alarms in accordance
with the relevant alarm handling suggestions. The relevant alarms are:
GNSS antenna feeder link fault (198096836)
GNSS receiver satellite searching fault (198096837)
GNSS receiver fault (198096835)
plug the board.
2-5

2.1.4 198093028 E1 port of local switch is overflowing.

Alarm Information
l Name: E1 port of local switch is overflowing.
l Alarm severity: Warning
The E1 port overflows.
Alarm Cause
The flow on the E1 port exceeds the upper threshold of the basic bandwidth.
Impact
1. Board status:
2. Service impact:
None.
Action
Expand the cascaded bandwidth:
1. Add a pair of E1 lines at the interface of the shelf where the CC board is located, and
record the port number of the E1 line.
2. On the OMMB, in the Modify Area of the BTS, select Managed Element > Transmission
Network > GSM > Physical Hosting > Physical Layer Port, and add a physical layer port
with transmission medium of E1.
Network > GSM > Physical Hosting > IP Transport > HDLC Channel, and add an HDLC
channel with the physical layer port number configured in step 2.
Network > GSM > Physical Hosting > IP Transport > PPP Link, and add a PPP link with
2-6

Chapter 2 Alarm
the HDLC Channel number configured in step 3, add a base station IP address for E1
cascade, set the PPP type to PPP or ML-PPP.
5. Save the configuration, perform incremental synchronization, and issue the
configuration to the base station.
6. Check whether the alarm is cleared.
2.1.5 198093050 The input clock of the board is abnormal.

Alarm Information
l Name: The input clock of the board is abnormal.
The 61.44 M clock signals or the timesyn signals sent from the backplane are abnormal or
the clock synchronization signals generated by timesyn are abnormal.
Alarm Cause
subcode0:
1. The 61.44 M clock output from the CC board is faulty.

2. The 61.44 M clock transmitted by the backplane is faulty.
3. The 61.44 M line of the board is faulty.
subcode1:
1. The timeSync frame synchronization signal output from the CC board is faulty.
2. The timeSync frame synchronization signal sent from the backplane is faulty.
3. The timesync frame synchronization signal line of the board is faulty.
Impact
1. Board status: The board is faulty.
2. Service impact: The services are affected.
Action
2-7

a. Check whether there is any relevant alarm on the active CC board. If yes, handle the
alarms in accordance with the corresponding alarm handling suggestion. The relevant
alarms are:
Board hardware fault (198097004)
b. Wait for five minutes and check whether the alarm is cleared.
plug the board.
and rest the board.
If no, contact the ZTE support center.
2.1.6 198093051 Internal clock of the board is abnormal.

Alarm Information
l Name: Internal clock of the board is abnormal.
The clock generated by the clock chip or FPGA chip of the board is abnormal.
Alarm Cause
1. The 61.44 M clock between the reference source boards is abnormal.
2. The PLL B is unlocked.
2-8

Chapter 2 Alarm
3. The 61.44 M clock generated by the clock chip B is abnormal.

4. The 61.44 M clock generated by the FPGA chip is abnormal.
5. The SRIO clock is abnormal.
Impact
1. Board status: The board is faulty.
Action
a. Check whether there is any relevant alarm. If yes, handle the alarms in accordance
with the corresponding alarm handling suggestion. The relevant alarm is:
"The input clock of the board is abnormal." (198093050) with the additional information
"61.44M clock abnormal"
plug the board.

2-9

2.1.7 198093052 Board internal communication interface alarm

Alarm Information
l Name: Board internal communication interface alarm
SRIO/AIF/TDM serdes bottom interface link alarm.
Alarm Cause
1. The link between DSP and FPGA is abnormal.
2. The link between the local FPGA and the remote FPGA is abnormal.
Impact
1. Board status: The board is operating properly.
Action
Handle the alarm according to the additional information in the alarm details:
For "UBPG3 SRIO bottom-layer alarm (BBU FPGA)" and "UBPG3 SRIO bottom-layer
alarm (DBB)" , do the following operations:
a. Check whether there is any relevant alarm. If yes, handle the alarm in accordance with
the corresponding alarm handling suggestion. The relevant alarm is:
Internal clock of the board is abnormal. (198093051)
plug the board.
2-10

Chapter 2 Alarm

For "UBPG 0/1/2 AIF bottom-layer alarm(BBU FPGA)" and "UBPG 0/1/2 AIF state is
abnormal(DBB)", do the following operations:
with the corresponding alarm handling suggestion. The relevant alarms are:
"The input clock of the board is abnormal. (198093050)" with the additional information
plug the board.
For "Data from UBPG0/1/2/3 TDM channel of back board is abnormal (BBU FPGA)", do
the following operations:
2-11

with the corresponding alarm handling suggestion. The relevant alarms are:
The input clock of the board is abnormal.(198093050) with the additional information
3. Power off and reset the board at the remote end according to the additional information
"Slot number of FS board or UBPG2 board from the opposite end".
plug the board.
5. Unplug and plug the board at the remote end according to the additional information
"Slot number of FS board or UBPG2 board from the opposite end".
7. Replace the board at the remote end according to the additional information "Slot
number of FS board or UBPG2 board from the opposite end".
2-12

Chapter 2 Alarm
2.1.8 198093053 Carrier uplink data is abnormal

Alarm Information
l Name: Carrier uplink data is abnormal
The carrier doesn't receive any uplink 60 ms flag, or the circle of 60 ms is wrong.
Alarm Cause
1. Routing configuration error.
2. Frame header data error.
3. Bottom-layer data link error.
Impact
I. Board status: The board operates properly.
II. Service impact: Services are affected.
Action
1. In accordance with the alarm parameters, power off and reset the RRU corresponding
to the alarm carrier.
3. Reset FS or UBPG2.
plug or replace the optical module and fibers.
2-13


2.1.9 198093054 DSP of the board runs abnormally

Alarm Information
l Name: DSP of the board runs abnormally
The DSP operates improperly.
Alarm Cause
The DSP operates improperly.
Impact
I. Board status: The board is faulty.
Action
1. The alarm can be cleared automatically. Wait for five minutes and check whether the
alarm is cleared.
then plug the board.
2-14

Chapter 2 Alarm
2.1.10 198093055 DSP hardware detection fails.

Alarm Information
l Name: DSP hardware detection fails.
DDR or Efuse detection fails.
Alarm Cause
DSP hardware failure.
Impact
Action
2-15


2.1.11 198093060 Device power down

Alarm Information
l Name: Device power down
This alarm is generated when the device detects that the voltage is lower than the preset
threshold.
Alarm Cause
1. The mains supply is unusual.
2. The external power supply device is faulty.
Impact
I. Board status:
None
II. Service impact:
Services are unavailable in the corresponding cell.
Action
1. Check whether the power supply circuit is good.
a. Check whether the cables and connectors have faults such as short circuit, and poor
contact.
If yes, go to substep b.
b. Remove the power supply circuit fault.
2. Check whether the external power supply device is faulty.
2-16

Chapter 2 Alarm

2.1.12 198093061 The optical module is not in position

Alarm Information
l Name: The optical module is not in position
l Alarm severity: Minor
This alarm is generated when the in-position signal of the optical module is not detected.
Alarm Cause
1. No optical/electrical module is inserted to the optical interface.
2. The optical/electrical module is not inserted properly.
3. The optical/electrical module is in poor contact with the board due to dirt.
4. The optical/electrical module is damaged.
5. The port of the optical/electrical module is damaged.
Impact
I. Board status:
The board operates properly.
II. Service impact:
The services of the cell associated to the optical port are interrupted.
Action
1. Check whether the optical/electrical module is inserted.
3. In accordance with the rack No., shelf No., slot No. and optical interface No. in the alarm
details, check whether the optical/electrical module is inserted into the corresponding port.
If no, go to substep b.
b. Insert the optical/electrical module.
2-17

2. In accordance with the rack No., shelf No., slot No. and optical interface No. in the
alarm details, unplug and plug the optical/electrical module.
alarm details, replace the optical/electrical module.
2.1.13 198093062 Optical module fault

Alarm Information
l Name: Optical module fault
This alarm is generated when the sending laser of the optical module is faulty or the
communication between the optical module and the board is abnormal.
Alarm Cause
The optical/electrical module is not well connected to the board or the optical/electrical
module is faulty.
Impact
I. Board status:
II. Service impact:
The services of the cell associated to the optical port are interrupted.
Action
2-18

Chapter 2 Alarm
3. On the client, select Dynamic Management->Dynamic Commands->SDR->Device
Group. In accordance with the rack No., shelf No., and slot No. in the alarm details,
power off and reset the board.
2.1.14 198093814 Clock has a critical alarm

Alarm Information
l Name: Clock has a critical alarm
l Alarm type: Equipment Alarm
Alarm Description
When clock module has a critical fault, this alarm is reported
Alarm Cause
System clock is lost/serdes clock is lost.
1. The active main control board is faulty.
2. The board hardware is faulty.
fpga clock alarm/frame abnormal/Fsync clock is lost.
1. The active main control board is reset.
2. The active main control board is faulty.
10M clock is lost/Phase detection clock is lost.
The board hardware is faulty.
Impact
l I. Impact on the equipment:
None.
2-19

l II. Impact on the services:

The clock module is improper. The services borne on the board may be entirely or
partially interrupted, or the service quality is affected.
Action
Perform the following operations based on the additional alarm information:
System clock is lost/Phase detection clock is lost/serdes clock is lost
1. Select Dynamic Management from the menu. The Dynamic Management page is
displayed. Select Dynamic Command -> SDR -> Device Group from the left navigation
tree, run the Query Board command, and then check the slot of the active main control
board. Reset the active main control board in accordance with the slot information.
After 30 minutes, and check whether this alarm is cleared.
l Yes -> End.
l No -> Step 2.
2. Replace the active main control board in accordance with the slot information. Refer
to Components Replacement.
l Yes -> End.
l No -> Step 3.
3. Reset the board in accordance with the rack number, shelf number and slot number
displayed in the alarm information. Refer to Reset Boards.
l Yes -> End.
l No -> Step 4.
4. Replace the board in accordance with the rack number, shelf number and slot number
displayed in the alarm information. Refer to Components Replacement.
l Yes -> End.
l No -> Contact the customer service center.
fpga clock alarm/frame abnormal/Fsync clock is lost
1. Verify that the active main control board is reset.
a. Select Dynamic Management from the menu. The Dynamic Management page
is displayed. Select Dynamic Command -> SDR -> Device Group from the
navigation tree, run the Query Board command, and then check the slot of the
active main control board.
b. Select Alarm Monitoring -> History Alarms. Check whether any related historical
alarm exists on the active main control board within five minutes around the time
when the alarm is generated. The related alarm is as follows:
198096477 Board reboots
2-20

Chapter 2 Alarm
l Yes -> Substep c.

l No -> Step 2.
c. After 15 minutes, check whether this alarm is cleared.
l Yes -> End.
l No -> Step 2.
2. Reset the active main control board in accordance with the slot information. Refer to
Reset Boards.
l Yes -> End.
l No -> Step 3.
3. Replace the active main control board in accordance with the slot information. Refer

l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
10M clock is lost

l Yes -> End.
l No -> Step 2.
l Yes -> End.

2-21

2.1.15 198093853 Abnormal RF power

Alarm Information
l Name: Abnormal RF power
After cell setup, the TRx board will report this alarm when it detects that the absolute
difference between digital power and analog power exceeds threshold (>6dB).
Alarm Cause
1. The amplifier is shut down.
2. The amplifier is faulty.
Impact
I. Impact on the equipment:
None.
II. Impact on the services:
When the transmission power is low, the services borne on the board may be entirely or
When the transmission power is high, adjacent cells may be interfered.
Action
1. Select Dynamic Management from the menu. The Dynamic Management page is
displayed. Select Dynamic Command -> SDR -> Device Group -> RRU from the navigation
tree, and then run the PA On command.
Yes -> End.
No -> Contact the customer service center.

displayed in the alarm information.

Yes -> End.
No -> Step 3.
2-22

Chapter 2 Alarm
Yes -> End.
2.1.16 198094010 Imbalanced Rx antenna

Alarm Information
l Name: Imbalanced Rx antenna
Alarm Description
When the two Rx antennas within the same set of RF boards differ greatly in the receiving
performance, this alarm is reported.
Alarm Cause
l The antenna is not connected based on the configuration.
l The antenna is not poorly contacted.
l The receive channel of the RRU board is invalid.
Impact
l Impact on the equipment:
None.
l Impact on the services:
The diversity reception gain decreases, affecting system reception performance.
Services borne by this board may be partially interrupted or the service quality may
be affected.
Action
1. Verify that the cables of the antenna are correctly connected.
a. Check whether the cables of the antenna are correctly connected.
l Yes -> Step 2.
l No -> Substep b.
b. Connect the cable correctly.
l Yes -> End.
2-23

l No -> Step 2.
2. Verify that the cables of the antenna are not loose or broken.
a. Check whether the cables of the antenna are loose or broken.
l No -> Substep b.
l No -> Step 3.
b. Reconnect or replace the cable.
l Yes -> End.
l No -> Step 3.
3. Query the rack number, shelf number, slot number of the corresponding RF board
and then replace the RF board in accordance with the Local cell no. parameter in the
additional alarm information.

l Yes -> End.
2.1.17 198093863 Failure alarm while raising the voltage of

adjustable power
Alarm Information
l Name: Failure alarm while raising the voltage of adjustable power
Alarm Description
As power climbs, power voltage is increased. If it is abnormal to raise the power, this alarm
is given.
Alarm Cause
The power module is faulty.
Impact
None.
The quality of the downlink signals is poor, affecting the downlink capacity. Services
borne by this board may be partially blocked or the service quality may be affected.
2-24

Chapter 2 Alarm
Action
l Yes -> End.
l No -> Step 2.
l Yes -> End.

2.1.18 198093864 RTWP abnormal

Alarm Information
l Name: RTWP abnormal
Alarm Description
RRU's RTWP exceed threshold
Alarm Cause
l The amplifier on the receiver channel is faulty.
l The configured receive port is not configured with the antenna or electrical load.
l The RRU board is faulty.
Impact
None.
The coverage of services is decreased. The services borne by the base station may
be partially or entirely affected.
Action
1. Verify that no related alarm exists.
2-25

a. Check whether any alarm related to the faulty port exists in accordance with the
additional alarm information. If such alarms exist, remove them based on the
corresponding handling suggestion. The related alarm is as follows:
198098468 External extended device fault
b. Check whether this alarm is cleared.
l Yes -> End.
l No -> Step 2.
l Yes -> End.
l No -> Step 3.
3. Check the RF cable connected to the faulty port.
a. Check whether the RF cable connected to the faulty port is loose or damaged.
l No -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
2.1.19 198094028 Software runs abnormally

Alarm Information
l Name: Software runs abnormally
Alarm Description
This alarm is reported when DSP core is abnormal.
Alarm Cause
l The clock or temperature is abnormal.
2-26

Chapter 2 Alarm
l The board hardware is faulty.

l The software operates abnormally.
Impact
None.
All the services on the board are interrupted.
Action
1. The board is automatically restarted when the alarm is generated. Select Alarm
Monitoring -> History Alarms, and then check whether the any related historical alarm
exists.
a. Check whether any related alarm exists. If such alarms exist, remove them based
on the corresponding handling suggestion. The related alarms are as follows:
198093814 Clock has a critical alarm
198093817 Clock has significant alarm
198096400 Device temperature is high
198097061 Temperature abnormal
Yes -> End.
No -> Step 2.
2. Select Alarm Monitor->History Alarms, and check whether the alarm is raised
frequently.
l Yes -> Step 3.
l No -> End.
l Yes -> End.
2.1.20 198094029 The baseband service is abnormal.

Alarm Information
l Name: The baseband service is abnormal.
2-27

Alarm Description
The baseband detects that the service data is abnormal and reports the fault.
Alarm Cause
Impact
None.
The board cannot bear more services.
Action
1. Reset the RRU board. Refer to Reset Boards.
a. Query the rack number, shelf number, and slot number of the corresponding
RRU board in accordance with the Cell Index parameter in the additional alarm
information.
b. Reset the board based on the rack number/shelf number/slot number verified in
substep a. Refer to Reset Boards.
l Yes -> End.
l No -> Step 2.
l Yes -> End.
l No -> Step 3.
l Yes -> End.

2-28

Chapter 2 Alarm
2.1.21 198094030 The uplink data verification is abnormal.

Alarm Information
l Name: The uplink data verification is abnormal.
Alarm Description
l Check error of uplink TDM channle.
l Check error of the uplink power report.
Alarm Cause
TDM check error:
l The socket of the baseband process board or optical interface board is abnormal.
l The baseband process board or optical interface board is not installed properly.
l The wires on the back panel are faulty.
l The baseband process board or the optical interface board is faulty.
Check error of the uplink power report:
l The clock of the baseband process board or optical interface board is abnormal.
l The socket of the baseband process board or optical interface board is abnormal.
l The baseband process board or optical interface board is not installed properly.
l The wires on the back panel are faulty.
l The baseband process board or the optical interface board is faulty.
l The optical module or optical fiber is abnormal.
Impact
None.
If a check error of uplink TDM channel exists, the services borne by the board are
interrupted.
If a check error of the uplink power report exists, the DPA or UPA service are abnormal.
Action
TDM check error:
1. Remove and install the board in accordance with the rack number, shelf number and
slot number displayed in the alarm information.
2-29


l Yes -> End.
l No -> Step 2.
2. Install the baseband process board into another slot.
a. Check whether the baseband process board can be installed into another slot.
l Yes -> Substep b.
l No -> Step 3.
b. Install the board to another slot.
c. Select Configuration Management -> Managed Element , double-click Device.
The Rack Graph page is displayed. Delete the board configuration in the slot,
and then configure the board in another slot.
d. Synchronize the configurations to the corresponding NE.
l Yes -> End.
l No -> Step 3.
l Yes -> End.
l No -> Step 4.
4. Remove and install the optical interface board.
a. The TDM of channels 0 to 2 is connected to slot 3 of the optical interface board.
The TDM of channel 3-5 is connected to slot 4 of the optical interface board.
b. Remove and install the board based on the slot number verified in substep a.
l Yes -> End.
l No -> Step 5.
5. Install the optical interface board into another slot.
a. Check whether the optical interface board can be installed into another slot in
accordance with the plan of the existing network and the slot number verified in
step 4.
l Yes -> Substep b.
l No -> Step 6.
c. Select Configuration Management -> Managed Element , double-click Device.
The Rack Graph page is displayed. Delete the board configuration in the slot,
and then configure the board in another slot.
2-30

Chapter 2 Alarm

l Yes -> End.
l No -> Step 6.
6. Replace the board based on the slot number of the optical interface board verified in
step 4. Refer to Components Replacement.
l Yes -> End.
Check error of the power report:
on the corresponding handling suggestion. The related alarm is as follows:
The uplink data verification is abnormal (198094030) (TDM check error)
l Yes -> End.
l No -> Step 2.
2. Verify that the optical fiber between the optical interface board and the RF board is
properly connected.
a. Check whether the optical fiber between the optical interface board and the RF
board is properly connected.
l Yes -> Step 3.
l No -> Substep b.
b. Reconnect or replace the optical fiber.
l Yes -> End.
l No -> Step 3.
3. Replace the optical module on the optical interface board. Refer to Components Rep
lacement.
l Yes -> End.
l No -> Step 4.
4. Replace the optical module on the RF board connected to the optical interface board.
l Yes -> End.
l No -> Step 5.
5. Replace the RF board connected to the optical interface board. Refer to Components
Replacement.
2-31

l Yes -> End.

2.1.22 198096407 Heat exchanger alarm

Alarm Information
l Name: Heat exchanger alarm
This alarm is reported when heat exchanger has a fault.
Alarm Cause
1. The temperature of the heat exchanger is too high.
2. The heat exchanger is faulty.
3. The heater of the heat exchanger is faulty.
4. The control board of the heat exchanger is faulty.
Impact
If the temperature is too low or too high, the lifespan of the equipment may be affected.
The heat exchanger operates abnormally so that the equipment temperature is too high
or too low. The services borne by the base station may be entirely or partially interrupted,
or the service quality may be affected.
Action
1. Replace the heat exchanger.
After 15 minutes, check whether this alarm is cleared.
Yes -> End.
2.1.23 198096408 FCE board not-configured alarm

Alarm Information
2-32

Chapter 2 Alarm
l Name: FCE board not-configured alarm

Alarm Description
This alarm is reported when a FCE board is not configured in network management
interface, but it is inserted into a real slot.
Alarm Cause
The FCE board is not configured in the network management system, but the FCE board
is actually connected.
Impact
None.
None.
Action
198096474 Wrong configuration of site type
198096475 Wrong configuration of cabinet type

l Yes -> End.
l No -> Step 2.
2. Configure the FCE board.
a. Select Configuration Management -> Managed Element , double-click Device,
The Rack Graph page is displayed. Configure the corresponding FCE board in
accordance with the rack number, shelf number, and slot number in the alarm
information.
b. Synchronize the configurations to the corresponding NE.

l Yes -> End.
2-33

2.1.24 198096412 Too close GU frequency spacing alarm

Alarm Information
l Name: Too close GU frequency spacing alarm
Alarm Description
This alarm is reported when GU carrier frequency spacing of RRU is too close (less than
2.4M).
Alarm Cause
The interval between the GSM carrier wave frequency point and the UMTS carrier wave
frequency point of the RRU board is smaller than half of the total bandwidth of the carrier
waves.
Impact
None.
The services borne by the faulty carrier wave are interrupted.
Action
1. Verify that the carrier wave frequency points are configured based on the plan.
a. Select Configuration Management -> Managed NE -> Radio Parameter, and then
check whether the GSM and UMTS carrier wave frequency points are configured
based on the plan.
l Yes -> Contact the customer service center.
l No -> Substep b.
b. Select Configuration Management -> Managed NE -> Radio Parameter, and then
modify the configurations of the GSM and UMTS carrier wave frequency points in
accordance with the plan.
c. Synchronize the configurations to the corresponding NE.

l Yes -> End.
2-34

Chapter 2 Alarm
2.1.25 198096413 TAM channel disabled due to over current

Alarm Information
l Name: TAM channel disabled due to over current
Alarm Description
TAM channel current is more than 2 times of configured normal working current, or TAM
channel current exceeds maximum permitted current.
Alarm Cause
l The overcurrent threshold is not configured in accordance with the amplifier.
l A short circuit or low resistance fault exists on the power cable between the amplifier
and the TAM.
l The amplifier or the TAM board is faulty.
Impact
None.
The service coverage in the cell is affected. All or some of the services on this base
station may be interrupted, or the service quality may be affected.
Action
1. Verify that no short circuit or low resistance exists on the power cable of the amplifier.
a. Check whether short circuit or low resistance exists on the power cable of the
amplifier.
l Yes -> Substep b.
l No -> Step 2.
b. Fix the short circuit or low resistance faults on the power cable.
l Yes -> End.

l No -> Step 2.
2. Verify that the actual current of the amplifier does not exceed the maximum current
supported by the TAM board.
a. Check the actual current of the amplifier (refer to the datasheet of the amplifier).
2-35

b. Check whether the actual current of the amplifier exceeds the maximum current
supported by the TAM board. The supported current ranges of the TAM boards
are described as follows:
TAM0 (0-600mA)
TAM1 (0-900mA)
TAM2 (0-850mA)
l Yes -> Step 4.
l No -> Step 3.
3. Verify that the actual current of the amplifier does not exceed the overcurrent threshold
of the TAM board.
a. Select Configuration Management -> Managed Element -> Device -> B8200,
select Power Outlet Set -> PowerOutlet in accordance with the rack number, shelf
number, and slot number in the alarm information, and then check the Working
current value parameter . The overcurrent threshold is calculated as follows:
TAM0: Working current value * 2.5
b. Check whether the actual current of the amplifier is higher than the overcurrent
threshold.
l Yes -> Substep c.
l No -> Step 4.
c. Modify the value of the Working current value parameter to ensure that the actual
current of the amplifier is lower than the overcurrent threshold.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
2.1.26 198096416 Tower mounted amplifier power alarm

Alarm Information
l Name: Tower mounted amplifier power alarm
2-36

Chapter 2 Alarm

Alarm Description
The channel is enabled, but the current is smaller than 60 mA.
Alarm Cause
l The TAM channel current threshold is configured incorrectly.
l The cable between the amplifier and the TAM is in poor contact.
Impact
None.
The service coverage in the cell is slightly affected. All or some of the services on this
base station may be interrupted, or the service quality may be affected.
Action
1. Verify that the power cable of the tower mounted amplifier is properly connected.
a. Check whether the power cable of the tower mounted amplifier is properly
connected.
l No -> Substep b.
l Yes -> Step 2.
b. Troubleshoot the power cable.

l Yes -> End.
l No -> Step 2.
2. Check the actual alarm detection mode of the amplifier (refer to the datasheet of the
amplifier).
Current detection mode -> Step 3.

Mark-space ratio detection mode -> Step 4.
3. Verify that the threshold of under current is properly configured.
b. Select Configuration Management -> Managed Element -> Device -> B8200,
and then select Power Outlet Set -> Power Outlet in accordance with the rack
number, shelf number, and slot number in the alarm information, and then check
the Working current value.
2-37

c. Modify the value of the Under current alarm threshold percent parameter to
ensure that the product of Working current value and Under current alarm
threshold percent is lower than the actual current.
l Yes -> End.
l No -> Step 4.

l Yes -> End.
2.1.27 198096418 LNA Branch Broken

Alarm Information
l Name: LNA Branch Broken
Alarm Description
LNA Branch Broken
Alarm Cause
l The alarm detection mode of the TAM board is not configured correctly.
l The connection relationships between the amplifier channels and the TAM board is
are correctly established. Channel B can only be connected to an odd channel.
l The amplifier channels are faulty.
Impact
None.
The service coverage in the cell is affected. All or some of the services on this base
station may be interrupted, or the service quality may be affected.
2-38

Chapter 2 Alarm
Action
1. Verify that the Alarm detection mode parameter of the TAM board is configured
correctly.
a. Check the actual alarm detection mode of the amplifier (refer to the datasheet of
the amplifier).
select Power Outlet Set -> Power Outlet in accordance with the rack number,
shelf number, and slot number in the alarm information, and then modify the
Alarm detection mode parameter the same to the amplifier .
l Yes -> End.
l No -> Step 2.
2. Verify that the connection relationships between the amplifier channels and the TAM
board are correct.
a. Check whether channel B of the amplifier is connected to an odd channel (1, 3, or
5) of the TAM board.
l Yes -> Step 3.
l No -> Substep b.
b. Exchange the connections for channels A and B.
l Yes -> End.
l No -> Step 3.
l Yes -> End.
2.1.28 198096420 Too close GL frequency spacing alarm

Alarm Information
l Name: Too close GL frequency spacing alarm
Alarm Description
This alarm is reported when GL carrier frequency spacing of RRU is too close.
2-39

Alarm Cause
The interval between the GSM carrier wave frequency point and the LTE carrier wave
frequency point of the RRU board is smaller than half of the total bandwidth of the carrier
waves.
Impact
None.
The services borne by the faulty carrier wave are interrupted.
Action
1. Verify that the carrier wave frequency points are configured based on the plan.
a. Select Configuration Management -> Managed NE -> Radio Parameter, and then
check whether the GSM and LTE carrier wave frequency points are configured
based on the plan.
l No -> Substep b.
b. Select Configuration Management -> Managed NE -> Radio Parameter, and then
modify the configurations of the GSM and LTE carrier wave frequency points in
accordance with the plan.
l Yes -> End.
2.1.29 198096421 Base station saves energy

Alarm Information
l Name: Base station saves energy
Alarm Description
This alarm is reported when main power of a base station is faulty or base station enters
energy-saving mode during self-defined period.
2-40

Chapter 2 Alarm
Alarm Cause
The primary power supply of the base station is faulty:
The storage battery needs to be switched to energy saving mode after supplying power
for a time of period.
Smart power-off:
The user configures the smart power-off function in accordance with service load to save
energy. No handling is required.
Impact
None.
Action
The primary power supply of the base station is faulty.
1. Check whether the primary power supply is proper.
l No -> Step 2.
2. Troubleshoot the primary power supply, and then check whether this alarm is cleared
after 15 minutes.
l Yes -> End.
Smart power-off.
The user configures the smart power-off function in accordance with service load to save
energy. No handling is required.
2.1.30 198096424 User-defined dry contact alarm 51

Alarm Information
l Name: User-defined dry contact alarm 51
Alarm Description
When there is a fault on the User-defined dry contact, the alarm is reported.
2-41

Alarm Cause
l The normally open or closed setting of the alarm related to the dry contact is not
correctly set.
l The cable is not correctly connected or is faulty.
l The dry contact device is faulty.
Impact
Operation of other equipment may be affected depending on the connected devices.
Services may be affected depending on the connected devices.
Action
1. Check the dry contact setting.
a. Select Configuration Management -> Managed Element -> Device -> BBU (such
as B8200). The corresponding tab is displayed. Select the dry contact, and
check whether the alarm setting is the same as that of the actually connected
dry contact device in accordance with the slot, shelf, and rack information in the
Detail Information dialog box.
l Yes -> Step 2.
l No -> Substep b.
b. Select Configuration Management -> Managed Element -> Device -> BBU (such
modify the alarm setting to be the same as that of the actually connected dry
contact device in accordance with the slot, shelf, and rack information in the Detail
Information dialog box.
c. Synchronize the configuration to the NE.
d. Wait 15 minutes, and check whether the alarm is cleared.

l Yes -> End.
l No -> Step 2.
2. Check the cable connected to the dry contact.

a. Check whether the cable is correctly connected (for example, whether the interface
is secured).
l Yes -> Substep c.
l No -> Substep b.
b. Reconnect the cable to the dry contact.
Wait 15 minutes, and check whether the alarm is cleared.

l Yes -> End.
l No -> Substep c.
2-42

Chapter 2 Alarm
c. Check whether the cable is in good condition.

l Yes -> Step 3.
l No -> Substep d.
d. Replace the cable with a proper one. Refer to Components Replacement.
l Yes -> End.
l No -> Step 3.
3. Check the dry contact device.
a. Check whether the connected device is faulty (for the detailed procedure, refer to
the instructions of the connected device).
l Yes -> Substep b.
l No -> Step 4.
b. Resolve the fault in accordance with the instructions of the external device.
l Yes -> End.
l No -> Step 4.
4. Reset the board in accordance with the slot, shelf, and rack information in the Detail
Information dialog box. Refer to Reset Boards.
l Yes -> End.
l No -> Step 5.
5. Replace the board in accordance with the slot, shelf, and rack information in the Detail
Information dialog box. Refer to Components Replacement.
l Yes -> End.

Alarm Information
Alarm Description
2-43

Alarm Cause
correctly set.
Impact
Action
l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.

is secured).
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.
2-44

Chapter 2 Alarm

l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
2-45

Alarm Cause
correctly set.
Impact
Action
l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.

is secured).
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.
2-46

Chapter 2 Alarm

l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
2-47

Alarm Cause
correctly set.
Impact
Action
l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.

is secured).
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.
2-48

Chapter 2 Alarm

l Yes -> Step 3.
l No -> Substep d.
d. Replace the cable with a proper one.
l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
2-49

Alarm Cause
correctly set.
Impact
Action
l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.

is secured).
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.
2-50

Chapter 2 Alarm

l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
2-51

Alarm Cause
correctly set.
Impact
Action
l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.

is secured).
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.
2-52

Chapter 2 Alarm

l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
2-53

Alarm Cause
correctly set.
Impact
Action
l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.

is secured).
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.
2-54

Chapter 2 Alarm

l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Cause
correctly set.
2-55

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
2-56

Chapter 2 Alarm

l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-57

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-58

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-59

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-60

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-61

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-62

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-63

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-64

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-65

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-66

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-67

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-68

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-69

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l
l Yes -> Step 3.
l No -> Substep d.
2-70

Chapter 2 Alarm
l Yes -> End.

l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.


Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-71

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
d. d. Replace the cable with a proper one.
Yes -> End.
2-72

Chapter 2 Alarm
No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-73

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-74

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-75

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-76

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-77

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-78

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-79

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-80

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-81

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-82

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-83

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-84

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-85

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-86

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-87

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-88

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-89

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-90

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-91

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-92

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-93

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-94

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-95

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-96

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-97

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-98

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-99

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-100

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-101

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
l Check whether the cable is correctly connected (for example, whether the
interface is secured).
à Yes -> Substep c.
à No -> Substep b.
l Reconnect the cable to the dry contact.
à Yes -> End.
à No -> Substep c.
l Check whether the cable is in good condition.
à Yes -> Step 3.
à No -> Substep d.
l Replace the cable with a proper one.
2-102

Chapter 2 Alarm
à Yes -> End.

à No -> Step 3.
l Check whether the connected device is faulty (for the detailed procedure, refer to
à Yes -> Substep b.
à No -> Step 4.
l Resolve the fault in accordance with the instructions of the external device.
à Yes -> End.

à No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-103

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-104

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-105

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-106

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-107

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-108

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-109

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-110

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-111

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-112

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-113

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-114

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-115

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-116

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-117

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-118

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-119

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-120

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-121

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-122

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-123

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-124

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-125

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-126

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-127

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-128

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-129

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-130

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-131

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-132

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-133

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-134

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-135

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-136

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-137

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-138

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.

l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
correctly set.
2-139

Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
2-140

Chapter 2 Alarm
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.
2.1.80 198096474 Wrong configuration of site type

Alarm Information
l Name: Wrong configuration of site type
Alarm Description
The configured site type is inconsistent with reality.
Alarm Cause
The base station is not configured in accordance with its actual type.
Impact
Overtemperature condition may exist in the base station, which may shorten
equipment lifespan.
2-141


The base station may be protected from overtemperature, and the services on the
base station are interrupted.
Action
1. Select Configuration Management -> Managed Element, and then check whether NE
types are in accord with the plan.
l No -> Step 2.
2. Configure the type of the NE in accordance with the network plan.
a. Add an NE and configure the type of the NE based on the plan.

b. Select Configuration Management -> Configuration Data Upload from NE to
synchronize the configurations to the EMS.

l Yes -> End.
2.1.81 198096475 Wrong configuration of cabinet type

Alarm Information
l Name: Wrong configuration of cabinet type
Alarm Description
The configured cabinet type is inconsistent with reality.
Alarm Cause
The cabinets are not configured in accordance with actual types.
Impact
Overtemperature condition may exist in the base station, which may shorten
equipment lifespan.
The cabinets of outdoor base stations and Metrocell base stations can be categorized
as multiple types. If the configuration is wrong, speed adjustment and number of the
RSU and BBU boards are not in accord with the actual requirements.
2-142

Chapter 2 Alarm
Action
1. Select Configuration Management -> Managed Element, and then check whether
cabinet types are in accord with the plan.
l Yes -> Step 3.
l No -> Step 2.
2. Configure the type of the cabinets in accordance with the network plan.
a. Add an NE and configure the type of the cabinet based on the plan.
b. Select Configuration Management -> Configuration Data Upload from NE to
synchronize the configurations to the OMM.
l Yes -> End.
l No -> Step 3.
3. Verify that the cabinets on site are in accord with the network plan.
a. Check whether the cabinets on site are in accord with the network plan.
l No -> Substep b.
b. Replace the cabinets. Refer to Components Replacement.
l Yes -> End.
2.1.82 198096490 TAM Channel over/under-current

Alarm Information
l Name: TAM Channel over/under-current
Alarm Description
l TAM channel current is higher than the configured upper limit of working current, but
less than 2 times of configured normal working current.（over-current).
l When TAM channel current is lower than the configured lower limit of its working
current, the alarm is reported（under-current).
Alarm Cause
l The threshold is not configured in accordance with the threshold of the amplifier.
l The Alarm detection mode parameter of the TAM board is not configured correctly.
l The cable between the amplifier and the TAM board is not connected properly.
2-143

Impact
None.
The service coverage in the cell is slightly affected. All or some of the services on this
base station may be interrupted, or the service quality may be affected.
Action
1. Verify that the power cable of the tower mounted amplifier is properly connected.
a. Check whether the power cable of the tower mounted amplifier is properly
connected.
l No -> Substep b.
l Yes -> Step 2.
b. Troubleshoot the power cable.
l Yes -> End.
l No -> Step 2.
2. Verify that the Alarm detection mode parameter of the TAM board is configured
correctly.
a. Check the actual alarm detection mode of the amplifier (refer to the datasheet of
the amplifier).
shelf number, and slot number in the alarm information, and then modify the
Alarm detection mode parameter the same to the amplifier .
l Yes -> End.
l No -> Step 3.
3. Verify that the threshold of over current or under current is properly configured.
shelf number, and slot number, and then modify the Over current alarm threshold
percent and the Under current alarm threshold percent parameters to ensure that
the actual current of the amplifier is higher than the under current alarm threshold
and lower than the over current alarm threshold.
2-144

Chapter 2 Alarm

l Yes -> End.
l No -> Step 4.
l Yes -> End.
2.1.83 198092215 Lost of synchronization

Alarm Information
l Name: Lost of synchronization
Alarm Description
l 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.
l 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.
l Control voltage abnormal Control voltage is beyond the range.
Alarm Cause
The board is faulty.
Impact
None.
Macro base station:

If the active main control board is faulty, the system cannot operate properly, and
the corresponding clock module alarms arise on peripheral boards. This results in
the interruption of all bearer services. If the standby main control board is faulty, the
system operation is not affected, but the system reliability is degraded (if the active
board is faulty, the active/standby switchover cannot be performed).
Micro base station:
2-145

The system cannot operate properly, and all bearer services are interrupted.
Action
1. Reset the board based on the rack number/shelf number/slot number in the Detail
l Yes -> End.
l No -> Step 2.
2. Replace the board based on the rack number/shelf number/slot number in the Detail

l Yes -> End.
2.1.84 198092289 The optical module is not in position

Alarm Information
l Name: The optical module is not in position
Alarm Description
This alarm occurs when in-position signal of the optical module is not detected.
Alarm Cause
l No optical/electrical module is inserted into the optical port.
l The optical/electrical module is not inserted properly.
l The optical/electrical module is in bad contact with the board due to pollution.
l The optical/electrical module is damaged.
l The port of the optical/electrical module is damaged.
Impact
None.
The services of cell associated to the optical port are interrupted.
2-146

Chapter 2 Alarm
Action
1. Ensure that the optical/electrical module is installed.
a. Check whether the corresponding port is installed with the optical/electrical module
in accordance with the optical port, slot, shelf, and rack information in the Detail
l Yes -> Step 2.
l No -> Substep b.
b. Install the optical/electrical module.
l Yes -> End.
l No -> Step 2.
2. Remove and re-install the optical/electrical module in accordance with the optical port,
slot, shelf, and rack information in the Detail Information dialog box.
l Yes -> End.
l No -> Step 3.
3. Replace the optical/electrical module in accordance with the optical port, slot, shelf,
and rack information in the Detail Information dialog box. Refer to Components Repl
acement.

l Yes -> End.
2.1.85 198092433 RRU physical layer link is interrupted

Alarm Information
l Name: RRU physical layer link is interrupted
Alarm Description
This alarm occurs when no optical signal is received at the receiving optical port of an RRU
in the network.
Alarm Cause
The optical fiber is not well connected to the optical port of the RRU or the optical module
is damaged.
2-147

Impact
None.
The service performance of the corresponding cell is degraded.
Action
1. Select Configuration Management -> Managed Element -> Device -> Rack Graph ->
Topology View. The corresponding tab is displayed. Determine the rack number of the
RRU related to the faulty link in accordance with the slot, shelf, and rack information in
the Detail Information dialog box and optical number and link information in the Remark
field.
2. Verify that no related alarms are raised on the corresponding RRU.
a. Check whether related alarms are raised on the corresponding RRU. If related
alarms are raised, troubleshoot them in accordance with the corresponding
handling suggestions. Related alarms are as follows:
198097604 Software runs abnormally
198097605 The RRU link is broken
198092295 Device power down
198092286 Loss of frames to be received at the optical port
198092290 No optical signal is received at the optical port

b. Check whether the alarms are cleared.
l Yes -> End.
l No -> Step 3.
3. Reset the board in accordance with rack number of the RRU (determined in Step 1).
Refer to Reset Boards. Refer to Reset Boards.
Wait 15 minutes, and check whether the alarms are cleared.
l Yes -> End.
2.1.86 198098313 Optical module fault

Alarm Information
l Name: Optical module fault
2-148

Chapter 2 Alarm
Alarm Description
This alarm occurs when the sending laser of the optical module is faulty or the
communication between the optical module and the board is abnormal.
Alarm Cause
The optical/electrical module is not well connected to the board or the optical/electrical
module is fault.
Impact
None.
Action
l Yes -> End.
l No -> Step 2.
acement.
l Yes -> End.
l No -> Step 3.
3. Select Dynamic Management -> Dynamic Command -> SDR -> Device Group. The
Device Group tab is displayed. Reset the board in accordance with the slot, shelf, and
rack information in the Detail Information dialog box.
l Yes -> End.

Alarm Information
2-149

Alarm Description
Alarm Cause
correctly set.
Impact
Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.
is secured).
l Yes -> Substep c.
l No -> Substep b.
2-150

Chapter 2 Alarm

l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.

l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
2-151

Alarm Description
Alarm Cause
correctly set.
Impact

Action
l Yes -> Step 2.
l No -> Substep b.
l Yes -> End.
l No -> Step 2.

is secured).
l Yes -> Substep c.
l No -> Substep b.
2-152

Chapter 2 Alarm

l Yes -> End.
l No -> Substep c.
l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
2-153

Alarm Cause
correctly set.
Impact
Action
l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.

is secured).
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.
2-154

Chapter 2 Alarm

l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
2-155

Alarm Cause
correctly set.
Impact
Action
l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.

is secured).
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.
2-156

Chapter 2 Alarm

l Yes -> Step 3.
l No -> Substep d.
l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
2-157

Alarm Cause
l The normally open or closed setting of the alarm related to the dry contact is not correctly set.
Impact

Action
a. Select Configuration Management -> Managed Element -> Device -> BBU (such as B8200).
The corresponding tab is displayed. Select the dry contact, and check whether the alarm set-
ting is the same as that of the actually connected dry contact device in accordance with the
l Yes -> Step 2.
l No -> Substep b.
b. Select Configuration Management -> Managed Element -> Device -> BBU (such as B8200).
The corresponding tab is displayed. Select the dry contact, and modify the alarm setting to
be the same as that of the actually connected dry contact device in accordance with the slot,
shelf, and rack information in the Detail Information dialog box.

l Yes -> End.
l No -> Step 2.
a. Check whether the cable is correctly connected (for example, whether the interface is secured).
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.
2-158

Chapter 2 Alarm

l Yes -> End.
l No -> Step 3.
a. Check whether the connected device is faulty (for the detailed procedure, refer to the instruc-
tions of the connected device).
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
4. Reset the board in accordance with the slot, shelf, and rack information in the Detail Information
dialog box. Refer to Reset Boards.
l Yes -> End.
l No -> Step 5.
5. Replace the board in accordance with the slot, shelf, and rack information in the Detail Information
dialog box. Refer to Components Replacement.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
2-159

Impact

Action
l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep b.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
2-160

Chapter 2 Alarm
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
2-161

Impact

Action
l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
2-162

Chapter 2 Alarm
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
2-163

Impact

Action
l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
2-164

Chapter 2 Alarm
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
2-165

Impact

Action
l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
2-166

Chapter 2 Alarm
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
2-167

Impact

Action
l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
2-168

Chapter 2 Alarm
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
2-169

Impact

Action
l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
2-170

Chapter 2 Alarm
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
2-171

Impact

Action
l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
2. 2. Check the cable connected to the dry contact.
a. a. Check whether the cable is correctly connected (for example, whether the interface is
secured).
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
2-172

Chapter 2 Alarm
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
2-173

Impact

Action
l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
2-174

Chapter 2 Alarm
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
2-175

Impact

Action
l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
2-176

Chapter 2 Alarm
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
2-177

Impact

Action
l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
2-178

Chapter 2 Alarm
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
2-179

Impact

Action
l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
2-180

Chapter 2 Alarm
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
2-181

Impact

Action
l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
2-182

Chapter 2 Alarm
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
2-183

Impact

Action
l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
2-184

Chapter 2 Alarm
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
2-185

Impact

Action
l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
2-186

Chapter 2 Alarm
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
2-187

Impact

Action
l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
2-188

Chapter 2 Alarm
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
l 2. The cable is not correctly connected or is faulty.
l 3. The dry contact device is faulty.
2-189

Impact

Action
l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
2-190

Chapter 2 Alarm
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
l 1. The normally open or closed setting of the alarm related to the dry contact is not correctly set.
l 2. The cable is not correctly connected or is faulty.
l 3. The dry contact device is faulty.
2-191

Impact

Action
l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
2-192

Chapter 2 Alarm
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
2-193

Impact

Action
l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
2-194

Chapter 2 Alarm
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
2-195

Impact

Action
l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
2-196

Chapter 2 Alarm
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
2-197

Impact

Action
l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
2-198

Chapter 2 Alarm
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
2-199

Impact

Action
l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
2-200

Chapter 2 Alarm
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
2-201

Impact

Action
l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
2-202

Chapter 2 Alarm
l Yes -> Substep b.

l No -> Step 4.
l Yes -> End.
l No -> Step 4.
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
Impact

Action
2-203

l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
2-204

Chapter 2 Alarm
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
Impact

Action
2-205

l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
2-206

Chapter 2 Alarm
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
Impact

Action
2-207

l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
2-208

Chapter 2 Alarm
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
Impact

Action
2-209

l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
2-210

Chapter 2 Alarm
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
Impact

Action
2-211

l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
2-212

Chapter 2 Alarm
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
Impact

Action
2-213

l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
2-214

Chapter 2 Alarm
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
Impact

Action
2-215

l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
2-216

Chapter 2 Alarm
l Yes -> End.
l No -> Step 5.
dialog box.Refer to Components Replacement.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
Impact

Action
2-217

l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
2-218

Chapter 2 Alarm
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
Impact

Action
2-219

l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
2-220

Chapter 2 Alarm
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
Impact

Action
2-221

l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
2-222

Chapter 2 Alarm
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
Impact

Action
2-223

l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
2-224

Chapter 2 Alarm
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
hen there is a fault on the User-defined dry contact, the alarm is reported.
Alarm Cause
Impact

Action
2-225

l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.
b. b. Reconnect the cable to the dry contact.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
2-226

Chapter 2 Alarm
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
Impact

Action
2-227

l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
2-228

Chapter 2 Alarm
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
Impact

Action
2-229

l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
2-230

Chapter 2 Alarm
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
Impact

Action
2-231

l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
2-232

Chapter 2 Alarm
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
hen there is a fault on the User-defined dry contact, the alarm is reported.
Alarm Cause
Impact

Action
2-233

l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
2-234

Chapter 2 Alarm
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
Impact

Action
2-235

l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
2-236

Chapter 2 Alarm

l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
Impact

Action
2-237

l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
2-238

Chapter 2 Alarm
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
Impact

Action
2-239

l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
2-240

Chapter 2 Alarm
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
Impact

Action
2-241

l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
2-242

Chapter 2 Alarm
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
Impact

Action
2-243

l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
2-244

Chapter 2 Alarm
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
Impact

Action
2-245

l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
2-246

Chapter 2 Alarm
l Yes -> End.
l No -> Step 5.
l Yes -> End.

Alarm Information
Alarm Description
Alarm Cause
Impact

Action
2-247

l Yes -> Step 2.
l No -> Substep b.

l Yes -> End.
l No -> Step 2.
l Yes -> Substep c.
l No -> Substep b.

l Yes -> End.
l No -> Substep c.

l Yes -> Step 3.
l No -> Substep d.

l Yes -> End.
l No -> Step 3.
l Yes -> Substep b.
l No -> Step 4.
l Yes -> End.
l No -> Step 4.
2-248

Chapter 2 Alarm
l Yes -> End.
l No -> Step 5.
l Yes -> End.

abnormal
Alarm Information
l Name: The baseband signal input to the TX channel is abnormal
Alarm Description
This alarm occurs when the Baseband IQ data power from the base-band unit exceeds
the rated power or is lower than the minimum power.
Alarm Cause
The baseband IQ data power sent by the baseband unit to the RF unit exceeds the rated power or is
lower than the lower power threshold.
Impact

None
If the frequency point of the RF unit fails to be set up, all or some of the services on this channel
may be interrupted, or the service quality may be affected.
2-249

Action
1. Reset the baseband board or the optical interface board that is connected with the RRU where
the alarm is located.
a. Select Configuration Management -> Managed Element -> Device, and double-click Device.
The Physical View and Topology View are displayed. Check the rack, shelf and slot of the
baseband board or the optical interface board that is connected with the RRU where the alarm
is located according to the rack number/shelf number/slot number in the alarm details.
b. Reset the board according to the rack number/shelf number/slot number verified in substep a.
Refer to Reset Boards.
Wait for 15 minutes, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 2.
2. Select Dynamic Management -> Dynamic Command -> SDR -> Device Group, and reset the
main control board. Refer to Reset Boards.
l Yes -> End.
2.1.138 198092049 Lightning protection device alarm

Alarm Information
l Name: Lightning protection device alarm
Alarm Description
This alarm is reported when the lightning protection device has a fault due to lightning
attack, not well grounded or ageing failure.
Alarm Cause
1. The normally open or closed setting of the alarm related to the dry contact is not correctly
set.
2. The cable is not correctly connected or is faulty.
3. The lightning protection device is faulty due to the lightning damage, poor contact or
aging.
4. The environmental monitoring unit is faulty.
2-250

Chapter 2 Alarm
Impact
The equipment may be struck by lightning during a thunderstorm and be damaged.
When the equipment is damaged, all or some of the services on the base station may be
blocked.
Action
a. Select Configuration Management→Managed Element→Device→BBU (such
Yes→Step 2.
No →Substep b.
b. Select Configuration Management→Managed Element→Device→BBU (such as
B8200). The corresponding tab is displayed. Select the dry contact, and modify
the alarm setting to be the same as that of the actually connected dry contact
device in accordance with the slot, shelf, and rack information in the Detail
Yes→End.
No→Step 2.
is secured).)
Yes→Substep c.
No→Substep b.
Yes→End.
No→Substep c.
Yes→Step 3.
No→Substep d.
2-251


Yes→End.
No→Step 3.
3. Replace the lightning protection box. Refer to Components Replacement.
Yes→End.
No→Contact the customer service center.
2.1.139 198092051 PSU alarm

Alarm Information
l Name: PSU alarm
Alarm Description
This alarm is reported when PSU is broken or its monitoring cable is not well connected.
Alarm Cause
1. The normally open/closed setting of this dry contact alarm is wrong.
2. The cable connection is wrong or the cable is faulty.
3. The PSU module is faulty.
4. The monitoring unit is faulty.
Impact
None.
None.
Action
1. Check the dry contact configuration.
a. Select Configuration Management→Managed Element→Device→B8200, and
check whether the alarm status of the dry contact device is the same as the alarm
status in the really connected contact device according to the Rack Number,
Shelf Number, and Slot Number in the alarm details.
2-252

Chapter 2 Alarm
Yes→Step 2.
No→Substep b.
b. Select Configuration Management→Managed Element→Device→B8200, and
change the alarm status of the dry contact device to the alarm status of the really
connected contact device according to the Rack Number, Shelf Number, and Slot
Number in the alarm details.
d. After 15 minutes, check whether the alarm is cleared.
Yes→End.
No→Step 2.
2. Check the dry contact cable.
a. Check whether the dry contact cable connection is correct (for example, whether
the interface connection is loose or wrong).
Yes→Substep c.
No→Substep b.
b. Connect the dry contact cable properly.
After 15 minutes, check whether the alarm is cleared.
Yes→End.
No→Substep c.
c. Check whether the dry contact cable is in good condition.
Yes→Step 3.
No→Substep d.
d. Change a dry contact cable.
Yes→End.
No→Step 3.
3. Replace the PSU module. Refer to Components Replacement.
Yes→End.
2.1.140 198092052 PSU fan alarm

Alarm Information
2-253

l Name: PSU fan alarm

Alarm Description
This alarm is reported when the PSU fan is faulty.
Alarm Cause
2. The fan box is not correctly installed.
4. The PSU module is faulty.
Impact
None.
None.
Action
Yes→Step 2.
No→Substep b.
Yes→End.
No→Step 2.
2. Check whether the fan box is correctly installed.
a. Check whether the fan box is correctly installed.
2-254

Chapter 2 Alarm
Yes→Step 3.
No→Substep b.
b. Correctly install a fan box.
c. After 15 minutes, check whether the alarm is cleared.
Yes→ End.
No→Step 3.

Yes→Substep c.
No→Substep b.
Yes→End.
No→Substep c.
Yes→Step 4.
No→Substep d.
Yes→End.
No→Step 4.
4. Replace a fan box. Refer to Components Replacement.
Yes→End.
No→ Contact the customer service center.
2.1.141 198092057 The board is powered off

Alarm Information
l Name: The board is powered off
2-255

Alarm Description
This alarm occurs when the board is powered off.
Alarm Cause
1. The board temperature is too high.
2. The board encounters an overcurrent problem.
3. The OMC powers off the board.
4. The software is abnormal.
Impact
None.
The services operating on the board are interrupted.
Action
Perform the following operations based on the information in the Remark field of the Detail
Information dialog box:
l The management power supply is cut off/The service power supply is cut off:
Remove and reinstall the board based on the rack number/shelf number/slot number
in the Detail Information dialog box.
Yes→End.
l The management power supply is cut off due to overcurrent/The service power supply
is cut off due to overcurrent:
1. Remove and reinstall the board based on the rack number/shelf number/slot
number in the Detail Information dialog box.
Yes→End.
No→ Step 2.
2. Install the board to another slot.
a. Check whether the board can be installed to another slot based on the network
planning.
Yes→Substep b.
No→Step 3.
2-256

Chapter 2 Alarm
c. Select Configuration Management -> Managed Element→Device→Rack

Graph from the menu. The Rack Graph tab is displayed. Delete the board
configuration of the original slot, and configure the board in the new slot.
d. Synchronize the configuration to the NE.
Yes→End.
No→Step 3.
3. Replace the board based on the rack number/shelf number/slot number in the
Yes→End.
l The power supply is cut off due to overtemperature:
1. Ensure that no related alarm is raised.
a. Check whether the related alarm is raised. If the related alarm has been raised,
take action based on the alarm handling suggestion. The related alarm is as
follows:
198098111 Fan failure
Yes→End.
No→Step 2.
2. Improve the ventilation conditions of the equipment room (for example, repair the
air conditioner and keep the device away from the high-power and heat-producing
devices).
After the ambient environment is restored, wait 15 minutes and check whether the
alarm is cleared.
Yes→End.
No→Step 3.
3. Ensure that the air intake of the equipment is not blocked or clean the air filter.
Yes→End.
l The management power supply is cut off manually/The service power supply is cut
off manually:
Select Dynamic Management→Dynamic Command→SDR→Device Group from the
menu. The Device Group tab is displayed. Power on the board based on the rack
number/shelf number/slot number in the Detail Information dialog box.
2-257


Yes→End.
l The service power supply is cut off by intelligent control:
This intelligent operation is automatically performed by the board for power saving
purposes, and no action is required.
2.1.142 198092068 Main power supply has a fault alarm

Alarm Information
l Name: Main power supply has a fault alarm
Alarm Description
When the system detects that external main power supply has a fault, this alarm is reported
through dry contact.
Alarm Cause
set.
3. The master power supply is faulty.
Impact
1) If the alarm arises on a board, the system operation is not affected temporarily, but the
power supply may be exhausted if the board operates for a long time, causing the service
performance to be degraded or services to be interrupted.
2) If the alarm arises on an RRU, the system stops the PA operation, and All services
operating on the RRU are interrupted.
Action
2-258

Chapter 2 Alarm

Yes→Step 2.
No →Substep b.
Yes→End.
No→Step 2.
is secured).
Yes →Substep c.
No→Substep b.
Yes→End.
No→Substep c.
Yes→Step 3.
No→Substep d.
Yes→End.
No→Step 3.
Yes→End.
2-259

No→Step 4.
4. Replace the master power supply with a proper one. Refer to Components Replace
ment.
Yes→End.
No→Step 5.
Wait 15 minutes, and check whether the alarm is cleared. Refer to Components Repl
acement.
Yes→End.
2.1.143 198092069 FCE fan failure

Alarm Information
l Name: FCE fan failure
Alarm Description
This alarm occurs when the fan on the Fan Control Element (FCE) is faulty.
Alarm Cause
1. The fan is blocked.
2. The fan is faulty.
Impact
The equipment temperature might be too high, overtemperature may affect the life of the
equipment.

The equipment temperature might be too high, causing the boards or the entire system
unable to operate properly. As a result, the service performance will decrease and the
services will even be interrupted.
2-260

Chapter 2 Alarm
Action
1. Ensure that the air intake of the fan is not blocked.
Yes→End.
No→Step 2.
2. Replace the fan in accordance with the fan number/slot, shelf, and rack information in
the Detail Information dialog box. Refer to Components Replacement.
Yes→End.
2.1.144 198092071 Temperature sensor abnormal

Alarm Information
l Name: Temperature sensor abnormal
Alarm Description
This alarm occurs when the temperature sensor is faulty.
Alarm Cause
1. The sensor is not connected.
2. The cable connected to the sensor is damaged.
3. The sensor is damaged.
Impact
None.
None.
Action
Perform the following operations based on the board type in alarm details:
If the alarm board is FCE, the operations are as follows:
1. Check the temperature sensor.
2-261

a. Check whether the temperature sensor has been installed.

Yes→Step 2.
No→Substep b.
b. Install a temperature sensor.
Yes→ End.
No→Step 2.
2. Check the temperature sensor cable.
a. Check whether the temperature sensor cable connection is loose or the cable is
damaged.
Yes→Substep b.
No→Step 3.
b. Unplug and plug the cable, or replace the cable.
Yes→End.
No→Step 3.
3. Change the temperature sensor.
Yes→End.
If the alarm board is SA/SE/PSA/PM, the operations are as follows:

1. Reset the board based on the Rack Number, Shelf Number and Slot Number in alarm
details. Refer to Reset Boards.

Yes→End.
No→Step 2.
2. Replace the board in accordance with the Rack Number, Shelf Number and Slot
Number in alarm details.
After 15 minutes, check whether the alarm is cleared. Refer to Components Replace
ment.
Yes→End.
2-262

Chapter 2 Alarm
2.1.145 198092072 The board is not in position

Alarm Information
l Name: The board is not in position
Alarm Description
This alarm occurs when the board is configured on the OMC but no board in-position signal
is detected in the actual slot.
Alarm Cause
1. The board is configured on the OMC but is not inserted in the actual slot.
2. The board is configured on the OMC but is not inserted in the actual slot tightly.
3. The board is configured on the OMC but the actual connection part is physically
damaged.
Impact
None.
The board cannot process services.
Action
1. Ensure that the board has been planned.
a. View the rack number/shelf number/slot number recorded in the Detail Information
dialog box based on the network planning, and check whether the slot has been
planned with a board.
Yes→Step 2.
No→Substep b.
b. Select Configuration Management→Managed Element -> Device→Rack Graph
from the menu. The Rack Graph tab is displayed. Delete the board configuration
of the corresponding slot.
Wait 15 minutes, and check whether the alarm has been cleared.
Yes→End.
2-263

2. Ensure that the board has been physically installed.

a. Check whether the board has been installed based on the rack number/shelf
number/slot number in the Detail Information dialog box.
Yes→Step 3.
No →Substep b.
b. Install the board based on the network planning.
Yes→End.
No→Step 4.
3. Remove and reinstall the board based on the rack number/shelf number/slot number
in the Detail Information dialog box.
Yes→End.
No→Step 4.
a. Check whether the board can be installed to another slot based on the network
planning.
Yes→Substep b.
c. Select Configuration Management→Managed Element→Device→Rack Graph

from the menu. The Rack Graph tab is displayed. Delete the board configuration
of the original slot, and configure the board in the new slot.
Yes→End.
2.1.146 198092073 Embedded power AC-in Switch Off

Alarm Information
l Name: Embedded power AC-in Switch Off
2-264

Chapter 2 Alarm
Alarm Description
This alarm occurs when the air break switch of the AC input is switched to OFF.
Alarm Cause
1. The active AC input air circuit breaker is off.
2. The active air circuit breaker contact-point cable does not have good contact or is
disconnected.
3. The socket of the monitoring unit does not have good contact or is disconnected.
5. The AC loop is short-circuited.
Impact
None.
The rectifiers cannot operate, and the system relies on the power supply from storage
batteries. When the power supply from the storage batteries is insufficient, the base station
may power down, and all the services on the base station may be blocked.
Action
1. Check whether the active AC input air circuit breaker is disconnected.
a. Check whether the active AC input air circuit breaker is disconnected.
Yes→Substep b.
No→Step 2.
b. Check whether the AC input is short-circuited.
Yes →Substep c.
No→Substep d.
c. Troubleshoot the AC short circuits.
d. Close the active AC air circuit breaker.
Yes→End.
No→Step 2.
2. Check whether the air circuit breaker detection cable is disconnected.
a. Check whether the air circuit breaker detection cable is disconnected.
Yes→ Substep b.
No→Step 3.
2-265


Yes→End.
No→Step 3.
3. Check whether the monitoring unit installation is correct.
a. Check whether the monitoring unit is properly connected.
Yes→Step 4.
No→Substep b.
b. Connect the monitoring unit properly.
Yes→End.
No→ Step 4.
4. Replace the monitoring unit. Refer to Components Replacement.
Yes→End.
2.1.147 198092074 Embedded power AC Power Off

Alarm Information
l Name: Embedded power AC Power Off
Alarm Description
This alarm occurs when the mains supply is powered off but there is no standby input AC
power supply.
Alarm Cause
1. The AC power supply fails.
2. The AC transducer is not connected properly or the transducer is damaged.
Impact
2-266

Chapter 2 Alarm
None.
The power supply has no AC input, and the system relies on the power supply from storage
batteries. When the power supply from the storage batteries is insufficient, the base station
may power down, and all the services on the base station may be blocked.
Action
1. Check the AC power supply.
a. Check whether the AC power supply is powered off or there is no AC power input
because of other failures.
Yes→Substep b.
No→Step 2.
b. Restore the AC power by using a diesel generator or other emergency power
supply devices.
Yes→End.
No→Step 2.
2. Check whether the detection cable of the AC transducer is disconnected.
a. Check whether the detection cable of the AC transducer is disconnected.
Yes→Substep b.
No→Step 3.
Yes→End.
No→Step 3.
3. Check whether the monitoring unit is properly connected.
Yes→Step 4.
No→Substep b.
Yes→End.
No→ Step 4.
2-267

Yes→End.
2.1.148 198092075 Embedded power SPD-C Broken

Alarm Information
l Name: Embedded power SPD-C Broken
Alarm Description
This alarm occurs when the Surge Protection Device C (SPD-C) becomes faulty.
Alarm Cause
1. The lightning protector is damaged.
2. The lightning protection air circuit breaker is disconnected.
3. The lightning protector base is does not have good contact.
4. The detection cable of the lightning protector is disconnected or does not have good
contact.
Impact
The lightning arrester has failed, and the equipment may be struck by lightning during a
thunderstorm and be damaged.
blocked.
Action
1. Change the lightning protection module.
Yes→End.
No→Step 2.
2. Check whether the lightning protection air circuit breaker is closed.
a. Check whether the lightning protection air circuit breaker is closed.
2-268

Chapter 2 Alarm
Yes→Step 3.
No→Substep b.
b. Close the lightning protection air circuit breaker.
Yes→End.
No→Step 3.
3. Check whether the lightning protector base has good contact.
a. Check whether the lightning protector base has good contact (for example, check
whether loose connection or rust exists).
Yes→Step 4.
No→Substep b.
b. Secure the lightning protector base or remove the rust.
Yes -> End.
No→Step 4.
4. Check whether the lightning protector base contact-point cable is disconnected.
a. Check whether the lightning protector base contact-point cable is disconnected.
Yes→Substep b.
No→Step 5.
Yes→End.
No→Step 5.
Yes→Step 6.
No→Substep b.
Yes→End.
No→ Step 6.
Yes→End.
2-269

2.1.149 198092076 Embedded power SPD-D Broken

Alarm Information
l Name: Embedded power SPD-D Broken
Alarm Description
This alarm occurs when the Surge Protection Device D (SPD-D) becomes faulty.
Alarm Cause
1. The lightning protector is damaged.
2. The lightning protector base is does not have good contact.
3. The detection cable of the lightning protector is disconnected or does not have good
contact.
Impact
The lightning arrester has failed, and the equipment may be struck by lightning during a
thunderstorm and be damaged.
blocked.
Action
1. Change the lightning protection module.
Yes→End.
No→Step 2.
2. Check whether the lightning protector base has good contact.
a. Check whether the lightning protector base has good contact (for example, check
whether loose connection or rust exists).
Yes→Step 3.
2-270

Chapter 2 Alarm
No→Substep b.
b. Secure the lightning protector base or remove the rust.
Yes→End.
No→ Step 3.
3. Check whether the lightning protector base contact-point cable is disconnected.
a. Check whether the lightning protector base contact-point cable is disconnected.

Yes→Substep b.
No→Step 4.

Yes→End.
No→Step 4.
Yes→Step 5.
No→Substep b.

Yes→End.
No→Step 5.
Yes→End.
2.1.150 198092077 Embedded power AC Under-Volt

Alarm Information
l Name: Embedded power AC Under-Volt
2-271

Alarm Description
This alarm occurs when the input AC phase voltage is lower than the under-voltage
threshold of phase voltage.
Alarm Cause
1. The AV input voltage is lower than the lower threshold.
Impact
None.
The power load capacity is lowered, and the normal power supply to the base station is
affected. When the base station powers down, all the services on the base station are
affected.
Action
1. Check whether the AC voltage is under the lower AC voltage threshold.
a. Log in to the real-time information window of the embedded power monitoring
module, and check the AC input voltage value.
b. Check whether the AC input voltage is under than the lower AC voltage threshold
(default: 154 V).
Yes→Substep c.
No→Step 2.
c. Troubleshoot the AC input failure of the embedded power.
Yes→End.
No→Step 2.
2. Check whether the detection cable of the AC transducer is disconnected.
a. Check whether the detection cable of the AC transducer is disconnected.
Yes→Substep b.
No→Step 3.
2-272

Chapter 2 Alarm
Yes→End.
No→Step 3.
Yes→Step 4.
No→Substep b.
Yes→End.
No→ Step 4.
Yes→End.
2.1.151 198092078 Embedded power AC Over-Volt

Alarm Information
l Name: Embedded power AC Over-Volt
Alarm Description
This alarm occurs when the input AC phase voltage is higher than the over-voltage
threshold of phase voltage.
Alarm Cause
1. The AV input voltage is higher than the upper threshold.
Impact
An overvoltage may affect the life of the equipment.
2-273

The rectifier may shut down for protection, and the normal power supply to the base station
is affected. When the base station powers down, all the services on the base station are
affected.
Action
1. Check whether the AC voltage is higher the upper AC voltage threshold.
b. Check whether the AC input voltage is higher than the upper AC voltage threshold
(default: 286 V).
Yes→Substep c.
No→Step 2.
Yes→End.
No→Step 2.
2. Check whether the detection cable of the AC transducer is not disconnected.
a. Check whether the detection cable of the AC transducer is not disconnected.
Yes→Substep b.
No→Step 3.
Yes→End.
No→Step 3.
Yes→Step 4.
No→Substep b.
Yes→End.
No→Step 4.
Yes→End.
2-274

Chapter 2 Alarm
2.1.152 198092079 Embedded power AC Current Over

Alarm Information
l Name: Embedded power AC Current Over
Alarm Description
This alarm occurs when the input AC current is higher than the over-current threshold of
AC current.
Alarm Cause
1. The AC current is higher than the upper threshold.
2. The AC input voltage is too low.
3. The load to the power supply is to high.
Impact
Long-period overcurrent may lead to the overtemperature of the AC input loop and the
ageing of cables.
Long-period overcurrent may lead to the disconnection of the AC input air circuit breaker.
When the base station powers down, all the services on the base station are blocked.
Action
1. Check whether the AC current is higher than the upper AC current threshold.
module, and check the AC input current value.
b. Check whether the AC input current is higher than the upper AC current threshold
(default: 80 A).
Yes→ Step 2.
No→Step 4.
2. Check whether the AC input voltage is too low.
2-275


b. Check whether the AC input voltage is lower than the standard AC input voltage.
Yes→Substep c.
No→Step 3.
Yes -> End.
No→Step 3.
3. Check whether AC overload exists.
module, and check the AC input current and voltage values.
b. Calculate the actual electric power according to the current and voltage values.
Check whether the actual electric power exceeds the rated power of the embedded
power supply.
Yes→Substep c.
No→Step 4.
c. Reduce load devices.

Yes→End.
No→Step 4.
Yes→Step 5.
No→Substep b.

Yes→End.
No→ Step 5.

Yes→End.
2-276

Chapter 2 Alarm
2.1.153 198092080 Embedded power SMR Over-Vout

Alarm Information
l Name: Embedded power SMR Over-Vout
Alarm Description
This alarm occurs when the output voltage of a rectifier is higher than the output
over-voltage threshold.
Alarm Cause
1. The rectifier output power is abnormal.
2. The rectifier is faulty.
Impact
The overvoltage may affect the life of the equipment.
affected.
Action
1. Remove and install the rectifier where the alarm is located.
Yes→End.
No→Step 2.
2. Replace the rectifier where the alarm is located. Refer to Components Replacement.
Yes→End.
2.1.154 198092081 Embedded power SMR Over-Iout

Alarm Information
2-277

l Name: Embedded power SMR Over-Iout

Alarm Description
This alarm occurs when the output current of a rectifier is higher than the output
over-current threshold.
Alarm Cause
1. The overcurrent protection circuit of the rectifier is faulty.
Impact
The overcurrent may affect the life of the equipment.
affected.
Action
Yes -> End.
No→Step 2.
Yes→End.
2.1.155 198092082 Embedded power SMR Fan Fault

Alarm Information
l Name: Embedded power SMR Fan Fault
2-278

Chapter 2 Alarm
Alarm Description
This alarm occurs when the fans of a rectifier become faulty.
Alarm Cause
1. The rectifier fan is damaged or blocked by some foreign objects.
Impact
The overtemperature may affect the life of the equipment.
affected.
Action
1. Check whether the fan is blocked up.
a. Check whether the fan is blocked (for example, the fan palms have stopped or the
air outlet is blocked).
Yes→Substep b.
No→Step 2.
b. Remove the blockage.
Yes→End.
No→Step 2.
Yes→Step 3.
No→Substep b.
Yes→End.
No→Step 3.
2-279

Yes→End.
No→Step 4.
Yes→End.
2.1.156 198092083 Embedded power SMR PFC Fault

Alarm Information
l Name: Embedded power SMR PFC Fault
Alarm Description
This alarm occurs when Power Factor Correction (PFC) encounters one of the following
problems:
l The PFC input is overcurrent.
l The PFC output is overvoltage.
l The PFC output is undervoltage.
Alarm Cause
The PFC circuit of the rectifier is faulty.
Impact
None.
The rectifier shuts down, and the normal power supply to the base station is affected. If
the base station powers down, all the services on the base station are interrupted.
Action
Replace the rectifier where the alarm is located. Refer to Components Replacement.
Yes→End.
2-280

Chapter 2 Alarm
2.1.157 198092084 Embedded power SMR Over-Vin Off

Alarm Information
l Name: Embedded power SMR Over-Vin Off
Alarm Description
This alarm occurs when the input voltage of the rectifier is higher than the upper input
voltage limit.
Alarm Cause
1. The AC input voltage of the rectifier is higher than the overvoltage protection threshold.
Impact
The overvoltage may affect the life of the equipment.
affected.
Action
1. Check whether the AC voltage is higher than the overvoltage threshold.
b. Check whether the AC input voltage is higher than the overvoltage threshold
(default: 295–305 V).
Yes→Substep c.
No→Step 2.
Yes→End.
No→Step 2.
2-281

Yes→End.
2.1.158 198092085 Embedded power SMR Under-Vin Off

Alarm Information
l Name: Embedded power SMR Under-Vin Off
Alarm Description
This alarm occurs when the input voltage of the rectifier is lower than the lower input voltage
limit.
Alarm Cause
1. The AC input voltage of the rectifier is lower than the under-voltage protection threshold.
Impact
None.
The rectifier may limit the output current or shut down for protection, and the normal power
supply to the base station is affected. When the base station powers down, all the services
on the base station are affected.
Action
1. Check whether the AC voltage is lower than the under-voltage threshold.
b. Check whether the AC input voltage is lower than the under-voltage threshold
(default: 80–90 V).
Yes→Substep c.
No→Step 2.
Yes→End.
2-282

Chapter 2 Alarm
No→Step 2.
Yes→End.
2.1.159 198092086 Embedded power SMR H.T. Off

Alarm Information
l Name: Embedded power SMR H.T. Off
Alarm Description
This alarm occurs when the heat exchanger temperature of the rectifier is higher than the
upper temperature limit, and the rectifier output will be disabled.
Alarm Cause
1. The temperature of the main rectifier heat sink is higher than the overtemperature
threshold.
Impact
affected.
Action
1. Check whether the temperature of the rectifier is higher than the over-temperature
threshold.
module, and check the rectifier temperature.
b. Check whether the rectifier temperature is higher than the over-temperature
threshold (default: 105 ℃).
Yes→Substep c.
2-283

No→Step 2.
c. Improve the ventilation (for example, eliminating the impact of air conditioner faults
and high-power heating devices on the environment).
d. Wait 15 minutes and check whether the alarm is cleared.
Yes→End.
No →Step 2.
Yes→ End.
2.1.160 198092087 Embedded power SMR Env.H.T.Off

Alarm Information
l Name: Embedded power SMR Env.H.T.Off
Alarm Description
This alarm occurs when the environment temperature of the rectifier is higher than the
upper temperature limit, and the rectifier will be shut down.
Alarm Cause
1. The environmental temperature of the rectifier is higher than the overtemperature
threshold.
Impact
affected.
2-284

Chapter 2 Alarm
Action
1. Check whether the ambient temperature of the rectifier is higher than the
over-temperature threshold.
module, and check the ambient temperature.
b. Check whether the ambient temperature is higher than the over-temperature
threshold (default: 75 ℃).
Yes→Substep c.
No→Step 2.
Yes→End.
No→Step 2.
Yes→End.
2.1.161 198092088 Embedded power SMR Env.H.T

Alarm Information
l Name: Embedded power SMR Env.H.T
Alarm Description
This alarm occurs when the output of a rectifier derates linearly due to too high environment
temperature.
Alarm Cause
1. The environmental temperature of the rectifier is higher than the overtemperature
load-reduction threshold.
Impact
2-285


The rectifier load capacity is lowered, and the normal power supply to the base station is
affected.
Action
1. Check whether the ambient temperature of the rectifier is higher than the
over-temperature load-reduction threshold.
module, and check the ambient temperature.
b. Check whether the ambient temperature is higher than the over-temperature
load-reduction threshold (default: 55 ℃).
Yes→Substep c.
No→Step 2.
Yes→End.
No→Step 2.
Yes→End.
2.1.162 198092089 Embedded power SMR L.Vin

Alarm Information
l Name: Embedded power SMR L.Vin
Alarm Description
This alarm occurs when the output of a rectifier derates linearly due to too low input voltage.
2-286

Chapter 2 Alarm
Alarm Cause
1. The AC input voltage of the rectifier is lower than the under-voltage load-reduction
threshold.
Impact
None.
The rectifier load capacity is lowered, and the normal power supply to the base station is
affected. When the load equipment powers down, all or some of the services on the base
station may be affected.
Action
1. Check whether the AC voltage is lower than the under-voltage load-reduction
threshold.
b. Check whether the AC input voltage is lower than the under-voltage load-reduction
threshold (default: 176 V).
Yes→Substep c.
No→Step 2.
Yes→End.
No→Step 2.
Yes→End.
2.1.163 198092090 Embedded power SMR Fuse Broken

Alarm Information
l Name: Embedded power SMR Fuse Broken
2-287

Alarm Description
This alarm occurs when the output of a rectifier derates linearly due to too low input voltage.
Alarm Cause
1. The output fuse wire in the rectifier is disconnected.
Impact
None.
affected.
Action
1. Replace the output fuse of the rectifier where the alarm is located. Refer to Compone
nts Replacement.
Yes→End.
No→Step 2.
Yes→End.
2.1.164 198092091 Embedded power SMR CommFail

Alarm Information
l Name: Embedded power SMR CommFail
2-288

Chapter 2 Alarm
Alarm Description
This alarm occurs when the communication between a rectifier and the monitoring unit is
disconnected.
Alarm Cause
1. The RS485 communication cable of the rectifier is disconnected or short-circuited.
2. The monitoring crystal oscillator frequency in the rectifier is not calibrated.
3. If the AC power supply is powered off, the actual load is lower than the lower load
threshold.
Impact
The over voltage or temperature condition may affect the lifespan of the equipment.
The monitoring unit cannot manage batteries or take AC voltage samples. This makes it
difficult to determine whether the AC power supply is powered off, and the normal power
supply to the base station may be affected. If the base station powers down, all the services
on the base station are interrupted.
Action
1. Check whether this alarm exists in all rectifiers.
Yes→Step 2.
No→Step 3.
2. Verify that related alarms are cleared.
a. Check whether any related alarm exists. Clear any alarm according to the
corresponding handling suggestions. Related alarm is as follows:
198092074 Embedded power AC Power Off
Yes→End.
No→Step 3.
3. Verify that the main CAN bus of the rectifier where the alarm is located is properly
connected.
a. Check whether the main CAN bus of the rectifier where the alarm is located is
properly connected, for example, whether the main CAN bus is not in good contact
or disconnected, or the communication loop is short-circuited.
2-289

Yes→Step 4.
No→Substep b.
b. Re-connect or replace the cable.
Yes→End.
No→Step 4.
Yes→End.
No→Step 5.

Yes→End.
2.1.165 198092092 Embedded power DC Under-Volt

Alarm Information
l Name: Embedded power DC Under-Volt
Alarm Description
This alarm occurs when the output DC voltage is lower than the preset DC undervoltage
threshold.
Alarm Cause
1. The DC output voltage is lower than the lower DC voltage threshold.
2. The AC input voltage is low.

3. The AC load is overloaded.
4. The battery is in test status.
5. The socket of the monitoring unit is not in good contact or the cable of the monitoring
unit is disconnected.
2-290

Chapter 2 Alarm
Impact
The lifespan of the battery may be affected.
All or some of the services on this base station may be interrupted, or the service quality
may be affected.
Action
1. Verify that the DC output voltage is not lower than the lower DC voltage threshold.
module, and check the DC output voltage value.
b. Check whether the DC output voltage is lower than the lower DC voltage threshold
(default: 48V).
Yes→Step 2.
No→Step 5.
Yes→Substep b.
No→Step 3.
b. Restore the AC power supply by using a diesel generator or other emergency
power supply devices.
Yes→End.
No→Step 3.
3. Verify that overload does not exist.
module, and check the output current value and the DC output voltage value of
the rectifier.
b. Calculate the actual electric power according to the current and voltage values,
and check whether the actual electric power exceeds the rated power of the
embedded power supply.
Yes→Substep c.
No→ Step 4.
2-291

Yes→End.
No→ Step 4.
4. Verify that the battery is not in test status.
module, and check whether the battery management mode is in test status.
Yes→Substep b.
No→Step 5.
b. After the battery test is completed, wait for 15 minutes, and check whether the
alarm is cleared.
Yes→End.
No→ Step 5.
5. Verify that the monitoring unit is properly connected.

Yes→Step 6.
No→Substep b.
Yes→End.
No→Step 6.
Yes→End.
2.1.166 198092093 Embedded power DC Over-Volt

Alarm Information
l Name: Embedded power DC Over-Volt
Alarm Description
This alarm occurs when the output DC voltage is higher than the preset DC overvoltage
threshold.
2-292

Chapter 2 Alarm
Alarm Cause
1. The DC output voltage is higher than the upper DC voltage threshold.
2. The AC input voltage is too high.
3. The socket of the monitoring unit is not in good contact or the monitoring unit is
disconnected.
Impact
The over voltage condition may affect the lifespan of the equipment.
The rectifier shuts down, and the base station depends on the power supply of the battery.
If the power of the battery is insufficient, all the services on the base station will be affected.
Action
1. Verify that the DC output voltage is lower than the upper DC voltage threshold.
module, and check the DC output voltage value.
b. Check whether the DC output voltage is higher than the upper DC voltage
threshold (default: 58 V).
Yes→ Step 2
No→Step 3.
a. Check whether the AC input voltage is higher than the standard AC input voltage.
Yes→Substep b.
No→Step 3.
b. Troubleshoot the AC input failure of the embedded power.
Yes→ End.
No→Step 3.
Yes→Step 4
No→Substep b.
2-293

Yes→End.
No→ Step 4.
Yes→End.
2.1.167 198092094 Embedded power DC Loop Broken

Alarm Information
l Name: Embedded power DC Loop Broken
Alarm Description
This alarm occurs when the load loop is broken.
Alarm Cause
1. The fuse of the load circuit blows (or the air switch is disconnected).
2. The detection cable of the load circuit is broken or is not in good contact.
Impact
None.
The power supply of the load is affected. If power supply fails, some of all of the services
on this base station may be interrupted, or the service quality may be affected.
Action
1. Verify that there are no short circuits among the load circuits.
a. Check whether there are short circuits among the load circuits.
Yes→Substep b.
No→Step 2.
2-294

Chapter 2 Alarm
b. Troubleshoot the short circuits.

Yes→End.
No→Step 2.
2. Verify that the capacity of the fuse (or the air switch) is properly configured.
module, and check the DC current value.
b. Check whether the DC current value exceeds the rated current supported by the
fuse or the air switch.
Yes→Substep c.
No→Step 3.
c. Replace the fuse or the air switch with one that has proper rated current which
must be greater than the DC current value.
Yes→End.
No→Step 3.
3. Verify that the load circuit detection cable is secured or is properly connected.
a. Check whether the circuit detection cable is not secured or is broken.
Yes→Substep b.
No→Step 4.
Yes→End.
No→Step 4.
Yes→Step 5.
No→Substep b.
Yes→End.
No→Step 5.
2-295

Yes→End.
2.1.168 198092095 Embedded power Bat Loop Broken

Alarm Information
l Name: Embedded power Bat Loop Broken
Alarm Description
This alarm occurs when the battery loop is broken.
Alarm Cause
1. The circuit fuse blows.
2. The circuit detection cable is broken or is not in good contact.
disconnected.
Impact
None.
All circuits of the battery group are broken. The base station will power down after AC
power failure. If the base station powers down, all the services on the base station may
be interrupted.
Action
1. Verify that there are no short circuits.
a. Check whether there are short circuits.
Yes→Substep b.
No →Step 2.
Yes→End.
No→Step 2.
2-296

Chapter 2 Alarm
2. Verify that the capacity of the battery corresponding to the fuse is properly configured.
a. Select Ctrl→Setup Para→Sys Para→Bat.1 Cap., and check the battery capability
configuration.
b. Check whether the capacity of the battery matches the specifications of the fuse.
Yes→Step 3
No→Substep c.
c. Modify the configuration of the battery capacity and replace the fuse.
Yes→End.
No→Step 3.
3. Verify that the circuit detection cable is not disconnected or broken.
a. Check whether the circuit detection cable is disconnected or broken.
Yes→Substep b.
No→Step 4.

Yes→End.
No→Step 4.
Yes→Step 5
No→Substep b.
Yes→End.
No→Step 5.

Yes→ End.
2-297

2.1.169 198092096 Embedded power Bat Under-Volt

Alarm Information
l Name: Embedded power Bat Under-Volt
Alarm Description
This alarm occurs when the battery voltage is lower than the preset battery undervoltage
threshold.
Alarm Cause
1. The voltage of the battery is lower than the lower battery voltage threshold.
2. The battery detection cable is faulty.
Impact
The lifespan of the battery may be affected.
Low power supply of the battery may cause the power-down of the base station, which
results in that all the services on the base station are interrupted.
Action
1. Verify that the output voltage of the battery is not lower than the lower battery voltage
threshold.
module, and check the output voltage value of the battery.
b. Check whether the output voltage of the battery is lower than the lower battery
voltage threshold (default: 47 V).
Yes→Step 2.
No→Step 5.
2-298

Chapter 2 Alarm
Yes→Substep b.
No→Step 3.
Yes→End.
No→Step 3.
the rectifier.
Yes→Substep c.
No→ Step 4.
Yes→End.
No→ Step 4.
4. Verify that the battery is not in test status.
module, and check whether the battery management mode is in test status.
Yes→Substep b.
No→Step 5.
b. After the battery test is completed, wait for 15 minutes, and check whether the
alarm is cleared.
Yes→End.
No→ Step 5.
Yes→Step 6.
No→Substep b.
2-299

Yes→End.
No→Step 6.
Yes→End.
2.1.170 198092097 Embedded power Bat Over-Temp

Alarm Information
l Name: Embedded power Bat Over-Temp
Alarm Description
This alarm occurs when the battery operating temperature is higher than the preset battery
overtemperature threshold.
Alarm Cause
1. The temperature of the battery is higher than the upper battery temperature threshold.
2. The temperature sensor of the battery is damaged.
disconnected.
Impact
The over temperature may affect the lifespan of the equipment.
If the base station depends on the power supply of the battery, all the services on the base
station may be interrupted.
Action
1. Verify that the temperature of the battery is lower than the upper battery temperature
threshold.
module, and check the temperature of the battery.
2-300

Chapter 2 Alarm
b. Check whether the temperature of the battery is higher than the upper battery
temperature threshold (default: 45 ℃).
Yes→Substep c.
No→Step 2.
c. Improve the ventilation (for example, ensuring the proper functioning of air
conditioners and high-power heating devices).
Yes→End.
No→Step 2.
2. Check the cable to the temperature sensor of the battery.
a. Check whether the cable to the temperature sensor of the battery is disconnected
or broken.
Yes→Substep b.
No→Step 3.
Yes→End.
No→Step 3.
3. Replace the temperature sensor of the battery.
Yes→End.
No→Step 4.
Yes→Step 5
No→Substep b.
Yes→End.
No→Step 5.
Yes→ End.
2-301

2.1.171 198092098 Embedded power TmpL Shut-Down

Alarm Information
l Name: Embedded power TmpL Shut-Down
Alarm Description
If the environmental temperature is lower than low-temperature power-cut threshold, all
loads are powered donw. Once this happens, this alarm is reported.
Alarm Cause
1. The battery temperature is lower than that in low temperature state.
disconnected.
Impact
None.
The normal power supply to the base station will be affected. If the base station powers
down, all the services on the base station will be interrupted.
Action
1. Verify that the battery temperature is higher than that in low temperature state.
b. Check whether the battery temperature is lower than that in low temperature state
(default: -15 ℃).
Yes→Substep c.
No→Step 2.
Yes→End.
2-302

Chapter 2 Alarm
No→Step 2.
or broken.
Yes→Substep b.
No→Step 3.
Yes→End.
No→ Step 3.
Yes→End.
No→Step 4.

Yes→Step 5
No→Substep b.
Yes→End.
No→ Step 5.
Yes→End.
2.1.172 198092099 Embedded power 1st Shut-down

Alarm Information
l Name: Embedded power 1st Shut-down
2-303

Alarm Description
If battery voltage is lower than LLVD1 threshold, the less important loads are powered
down. Once this happens, this alarm is reported.
Alarm Cause
1. The voltage of the battery is lower than the LLVD1 voltage threshold.
2. The switch of the manual power-off device is incorrectly configured.
3. The cable of the DC contactor is not properly connected.
4. The DC contactor is faulty.
5. The SDCB board is faulty.
Impact
None.
The minor load powers down. Some of the services on this base station may be interrupted
or the service quality may be affected.
Action
Yes→Substep b.
No→Step 2.
Yes→End.
No→ Step 2.
2. Check the status of the switch of the manual power-off device.
a. Check whether the switch of the manual power-off device is in automatic or
connected status.
Yes→Step 3.
No→Substep b.
b. Adjust the status of the switch of the manual power-off device to automatic or
connected.
2-304

Chapter 2 Alarm

Yes→End.
No→Step 3.
3. Verify that the cable of the LLVD1 DC contactor is in secured or is properly connected.
a. Check whether the cable of the LLVD1 DC contactor is not secured or is broken.
Yes→Substep b.
No→Step 4.
Yes→End.
No→Step 4.
4. Verify that the LLVD1 DC contactor is in good condition.
a. Measure the voltages on both ends of the coil, and check whether the voltage
value is close to 0V.
Yes→Substep b.
No→Step 5.
b. Replace the LLVD1 DC contactor.
Yes→End.
No →Step 5.
5. Replace the board if the SDCB board is configured on site. Refer to Components
Replacement.
Yes→End.
No→Step 6.
Yes→End.
2.1.173 198092100 Embedded power 2nd Shut-down

Alarm Information
l Name: Embedded power 2nd Shut-down
2-305


Alarm Description
If battery voltage is lower than LLVD2 threshold, all loads are powered down. Once this
happens, this alarm is reported.
Alarm Cause
1. The voltage of the battery is lower than the LLVD2 voltage threshold.
2. The switch of the manual power-off device is incorrectly configured.
3. The DC connector is incorrectly connected.
5. The SDCB board is faulty.
Impact
None.
All the services on the base station are interrupted.
Action
Yes→Substep b.
No→Step 2.
Yes→End.
No→Step 2.
connected status.
Yes→Step 3.
No→Substep b.
2-306

Chapter 2 Alarm
connected.
Yes→End.
No→Step 3.
3. Verify that the cable of the LLVD2 DC contactor is secured or is properly connected.
a. Check whether the cable of the LLVD2 DC contactor is not secured or is broken.
Yes→Substep b.
No→Step 4.
Yes→End.
No→Step 4.
4. Verify that the LLVD2 DC contactor is in good condition.
Yes→Substep b.
No→Step 5.
b. Replace the LLVD2 DC contactor.
Yes→End.
No→Step 5.
5. Replace the board if the SDCB board is configured on site. Refer to Components
Replacement.
Yes→End.
No→Step 6.

Yes→End.
2-307

2.1.174 198092101 Embedded power DC SPD Broken

Alarm Information
l Name: Embedded power DC SPD Broken
Alarm Description
This alarm occurs when the DC lightning protector becomes faulty.
Alarm Cause
1. The detection cable is disconnected or not in good contact.
2. The DC lightning protector is faulty.
Impact
The lightning protector is damaged, and the equipment may be struck and damaged by
lightning in thunderstorms.
interrupted.
Action
1. Verify that the detection cable of the DC lightning protector is not disconnected or
broken.
a. Check whether the detection cable of the DC lightning protector is disconnected
or broken.
Yes→Substep b.
No→Step 2.
Yes→End.
No→Step 2.
2. Replace the DC lightning protector. Refer to Components Replacement.
Yes→End.
2-308

Chapter 2 Alarm
No→Step 3.
Yes→End.
2.1.175 198092102 Embedded power DC Breaker Alarm

Alarm Information
l Name: Embedded power DC Breaker Alarm
Alarm Description
This alarm occurs when the DC output breaker becomes faulty.
Alarm Cause
2. The current of the load is low, and the loop current before and after power-off changes
a little.
3. The power-off control loop of the system is disconnected.
4. The output monitoring control signal is abnormal.
Impact
Overdischarge may cause battery damage.
If the base station is powered by the battery, all the services on the base station may be
interrupted.
Action
1. Check whether the current of the load is higher than 3A.
Yes→Step 3.
No→Step 2.
2. Verify that the control signal cable is secured or properly connected.
a. Check whether the detection cable of the DC lightning protector is not secured or
is broken.
2-309

Yes→Substep b.
No→Step 3.
Yes→End.
No→ Step 3.
3. Replace the DC contactor. Refer to Components Replacement.
Yes→End.
No→Step 4.
Yes→End.
2.1.176 198092103 Embedded power Bat Test Failure

Alarm Information
l Name: Embedded power Bat Test Failure
Alarm Description
This alarm occurs when the battery test stops but the test duration does not reach the
maximum test time.
Alarm Cause
1. The battery completes discharge before the test time expires.
2. The battery is not properly connected.
3. The power of the battery is insufficient.
4. Battery test parameters are improperly configured.
Impact
None.
2-310

Chapter 2 Alarm
If the power of the battery is insufficient, all the services on the base station may be
interrupted.
Action
1. Verify that the battery is properly connected.
a. Check whether the battery is properly connected.
Yes -> Substep c.
No→Substep b.
b. Re-connect the battery.
c. Retest the battery capacity after the battery is fully charged.
After the test, wait for 15 minutes, and check whether the alarm is cleared.
Yes→End.
No→Step 2.
2. Verify that the battery test parameters are properly configured.
a. Select Parameter Configuration→Battery Parameter in the embedded power
monitoring module, and check whether the maximum test time (default: 8 h) and
the final test voltage (default: 46 V) are properly configured.
Yes→Step 3.
No→Substep b.
b. Modify the maximum test time and the final test voltage to the default values.
Yes→End.
No→Step 3.
3. Replace the battery, and retest the battery capacity after the battery is fully charged.
Refer to Components Replacement.
Yes→End.
2.1.177 198092104 Embedded power Bat Discharge

Alarm Information
l Name: Embedded power Bat Discharge
2-311

Alarm Description
This alarm occurs when the battery is being discharged.
Alarm Cause
1. The discharge current of the battery is too large.
2. The preset discharge threshold is not appropriate.
3. The AC transmitter is faulty.
Impact
None.
Long-term depending on the power supply of the battery may cause the power-down of
the base station. If the base station powers down, all the services on the base station will
be interrupted.
Action
Yes→Substep b.
No→Step 2.
supply devices.
Yes→End.
No→Step 2.
2. Verify that the preset discharge threshold is appropriate.
a. Select Setup Para→Alarm Para, and check whether the preset discharge
threshold (default: -10 A) is appropriate.
Yes→Step 3
No→Substep b.
b. Adjust the discharge threshold to the default value.
2-312

Chapter 2 Alarm
Yes -> End.

No→Step 3.
3. Verify that the current detection cable is not disconnected or broken.
a. Check whether the current detection cable is disconnected or broken.
Yes→Substep b.
No→Step 4.

Yes→End.
No→Step 4.

Yes→Step 5
No→Substep b.
Yes→End.
No→Step 5.
Yes→End.
2.1.178 198092116 Embedded power AC Auxiliary Output Switch

Off
Alarm Information
l Name: Embedded power AC Auxiliary Output Switch Off
Alarm Description
This alarm occurs when the air break switch of the standby AC output is turned off.
2-313

Alarm Cause
1. The backup AC output air circuit breaker is off.
2. The air circuit breaker detection contact-point cable does not have good contact or is
disconnected.
Impact
None.
When the active output fails and the backup output cannot provide power normally, all the
services on the base station are blocked.
Action
1. Check whether the standby AC output air circuit breaker is closed.
a. Check whether the standby AC output air circuit breaker is closed.
Yes→Step 2.
No→Substep b.
b. Close the standby AC output air circuit breaker.
Yes→End.
No→Step 2.
2. Check whether the contact point of the standby AC output air circuit breaker has good
contact.
a. Check whether the contact point of the standby AC output air circuit breaker has
good contact (for example, check whether loose connection or rust exists).
Yes→Step 3.
No→Substep b.
b. Connect the cable at the fixed contact point or remove the rust.
Yes→End.
No→Step 3.
Yes→Step 4.
2-314

Chapter 2 Alarm
No→Substep b.
Yes→End.
No→Step 4.

Yes→End.
2.1.179 198092117 Embedded power Rectifier Module Fault

Alarm Information
l Name: Embedded power Rectifier Module Fault
Alarm Description
This alarm occurs when a rectifier module becomes faulty.
Alarm Cause
1. The rectifier module is not connected.
2. The air circuit breaker corresponding to the rectifier module is disconnected.
3. The rectifier module is faulty.
4. The slots in the rectifier cabinet are damaged.

Impact
None.

The normal power supply to the base station is affected. When the base station powers
down, all the services on the base station are blocked.
2-315

Action
1. Check whether the rectifier where the alarm is located is properly connected.
a. Check whether the rectifier where the alarm is located is properly connected.
Yes→Step 3.
No→Substep b.
b. Connect the rectifier properly.
Yes→ End.
No→Step 2.
2. Check whether the rectifier input air circuit breaker where the alarm is located is closed.
a. Check whether the rectifier input air circuit breaker where the alarm is located is
closed.
Yes→Step 3.
No→Substep b.
b. Close the input air circuit breaker.
Yes→End.
No→ Step 3.
3. Check whether the operating status of the rectifier where the alarm is located is normal.
Check whether the operating status of the rectifier where the alarm is located is normal
(for example, the fault indicator is lit).
Yes→Step 4.
No →Substep b.
4. Replace the rectifier where the alarm is located.
Yes -> End.
No→Step 5.
5. Change the installation slot of the rectifier.
Yes→End.
No→Step 6
Yes→Step 7
2-316

Chapter 2 Alarm
No→Substep b.
Yes→End.
No→Step 6.
Yes→ End.
2.1.180 198092203 The board is not configured

Alarm Information
l Name: The board is not configured
Alarm Description
This alarm occurs when the board is not configured on the OMC but is inserted in the
actual slot.
Alarm Cause
1. The board is not configured on the OMC but is inserted in the actual slot.
2. The slot in which the board is inserted is inconsistent with that configured on the OMC.
Impact
None.
The services operating on the board are affected.
Action
1. Check the information in the Remark field of the Detail Information dialog box based
on the network planning, and ensure that the slot has been planned with a board.
Yes→Step 2.
No→Step 3.
2-317

2. Configure the board based on the network planning.

a. Select Configuration Management→Managed Element→Device -> Rack Graph
from the menu. The Rack Graph tab is displayed. Configure the board to be
the same as the network planning based on the rack number/shelf number in the
Detail Information dialog box and the slot information in the Remark field.
b. Synchronize the configuration to the NE.
c. Wait 15 minutes, and check whether the alarm is cleared.
Yes→End.
3. Remove the board based on the rack number/shelf number in the Detail Information
dialog box and the slot information in the Remark field.
Yes→End.
2.1.181 198092206 Battery alarm

Alarm Information
l Name: Battery alarm
Alarm Description
This alarm is reported when the system detects that the external battery at a dry contact
is faulty.
Alarm Cause

3. Storage batteries are faulty.
Impact
None.
2-318

Chapter 2 Alarm
Long-period operation may lead to system operation anomaly, and all services on the base
station may be blocked.
Action
Yes→Step 2.
No→Substep b.
Yes→End.
No→Step 2.
Yes→Substep c.
No→Substep b.
Yes→End.
No→ Substep c.
Yes→Step 3.
No→Substep d.

Yes→End.
No→Step 3.
2-319

Yes→ End.
No→Step 4.
4. Remove and install the board in accordance with the Rack Number, Shelf Number and
Slot Number in the alarm details.
Yes→End.
No→Step 5.
ment.
Yes→End.
No→Step 6.
6. Place storage batteries.

Yes→End.
2.1.182 198092207 AC power-cut alarm

Alarm Information
l Name: AC power-cut alarm
Alarm Description
This alarm is reported when the main power is cut.
Alarm Cause

3. The AC power supply fails, or there is no AC power input because of other failures.
2-320

Chapter 2 Alarm
Impact
None.
The AC power supply has failed, and the system relies on the temporary power supply
from storage batteries. Long-period operation in this condition may cause all or some of
the services on the base station to be blocked, or affect service quality.
Action
Yes→Step 2.
No→Substep b.
Yes→End.
No→Step 2.
Yes→Substep c.
No→Substep b.
Yes→End.
No→ Substep c.
Yes→Step 3.
No→Substep d.
2-321


Yes→End.
No→Step 3.
Yes→Substep b.
No→Step 4.
supply devices.
Yes→End.
No→Step 4.
Yes→End.
No→ Step 5.
Slot Number in the alarm details.
Yes→End.
No→Step 6.
Number in alarm details. Refer to Components Replacement.
Yes→ End.
2.1.183 198092208 Rectifier module alarm

Alarm Information
l Name: Rectifier module alarm
2-322

Chapter 2 Alarm
Alarm Description
This alarm is reported when the rectifier works abnormally.
Alarm Cause
set.
3. The rectification module is not operating properly.
Impact
None.
Power cannot be normally supplied so that the system paralyzes and services are
interrupted.
Action
Yes→Step 2.
No →Substep b.


Yes→End.
No→Step 2.
2-323

is secured).)
Yes→Substep c.
No→Substep b.
Yes→End.
No→Substep c.
Yes→Step 3.
No→Substep d.
Yes→End.
No→Step 3.
3. Replace the rectification module. Refer to Components Replacement.
Yes→End.
2.1.184 198092209 Thermoelectric cooler alarm

Alarm Information
l Name: Thermoelectric cooler alarm
Alarm Description
This alarm is reported when the thermoelectric cooler is faulty.
Alarm Cause
set.
3. The thermoelectric refrigerating unit is faulty.
2-324

Chapter 2 Alarm
Impact
None.
When the thermoelectric cooler is faulty, battery lifetime may be shortened. Furthermore,
system services may also be affected.
Action
Yes→Step 2.
No →Substep b.
Yes→End.
No→Step 2.
is secured).)
Yes→Substep c.
No→Substep b.
Yes→End.
No→Substep c.
2-325

Yes→Step 3.
No→Substep d.
Yes→End.
No→Step 3.
Wait 15 minutes, and check whether the alarm is cleared. Refer to Reset Boards.
Yes→End.
No→Step 4.
4. Replace the thermoelectric refrigerating unit with a proper one. Refer to Components
Replacement.
Yes→End.
No→Step 5.
acement.
Yes→End.
2.1.185 198092217 No available clock source at air-interface

Alarm Information
l Name: No available clock source at air-interface
Alarm Description
This alarm occurs when the air-interface clock source is not configured or the air-interface
clock source cannot be locked (due to serious interference, crystal oscillator adjustment
threshold being exceeded, or crystal oscillator fault).
2-326

Chapter 2 Alarm
Alarm Cause
1. The air-interface clock source is not configured or the clock source configuration is
wrong.
2. The air-interface clock source cannot be locked (the clock source interference is serious
or exceeds the crystal oscillator adjustment limit, or the crystal oscillator is faulty).
Impact
None.
All the services on the base station are blocked.
Action
1. Check whether the GNSS receiver hardware configuration is correct.
a. Select Configuration Management→Managed Element -> Device→B8200, and
confirm the main control board slot (slot 1 or slot 2) is configured for the reference
clock source. Select ClockDevice Set→Clock Device, and check whether the
configured reference clock source type is the same as planned.
Yes→Step 2.
No→Substep b.
b. Reconfigure the reference clock source type based on the network planning.
Yes→End.
No→ Step 2.
2. Check whether related alarms exist.
a. Check whether the following alarms exist. If yes, handle them according to
corresponding suggestions.
198092426 The GNSS cascading clock is faulty
198096834 1PPS+TOD clock source fault
198096835 GNSS receiver fault
198096836 GNSS antenna feeder link fault
198096837 GNSS receiver satellite searching fault
198096831 1588 clock source fault
198096839 RRU inner GNSS clock source abnormal
2-327

Yes→End.
No→Step 3.
Yes→End.
No→Step 4.
Yes→End.
2.1.186 198092234 Embedded power type configuration error

Alarm Information
l Name: Embedded power type configuration error
Alarm Description
This alarm occurs when the power supply type is different from the actual configuration.
Alarm Cause
The power supply type is different from the actual configuration.
Impact
None.
Resolution of the power supply alarms is affected, and services are not affected.
Action
1. Verify that the type of the power supply is configured correctly.
a. Select Configuration Management→Managed Element -> Device→BTS Auxiliary
Peripheral Device→External Device, and re-configure the type of the power supply
2-328

Chapter 2 Alarm
according to the corresponding information in the additional alarm information in

the alarm details.
c. Wait for 15 minutes, and check whether the alarm is cleared.
Yes→End.
No→Step 2.
2. Replace the power supply. Refer to Components Replacement.
Yes→End.
2.1.187 198092235 Embedded power communication interruption

Alarm Information
l Name: Embedded power communication interruption
Alarm Description
This alarm occurs when the communication of the power supply is interrupted.
Alarm Cause
1. The link connected to the power supply is faulty.
2. The monitoring unit's socket is of bad contact or disconnected.
Impact
None.
Resolution of the power supply alarms is affected, and services are not affected.
Action
1. Check the RS232 cable connection between the power supply and the SA.
a. Check whether the RS232 cable connection between the power supply and the
SA is not secured or is broken.
2-329

Yes →Step 2.
No→Substep b.
Yes→End.
No→Step 2.
Yes→Step 3.
No→Substep b.
Yes→End.
No→Step 3.
Yes→End.
2.1.188 198092236 Embedded power SMR Output Fault

Alarm Information
l Name: Embedded power SMR Output Fault
Alarm Description
This alarm occurs when the output of a rectifier is abnormal.
Alarm Cause
The rectifier is faulty.
Impact
None.
2-330

Chapter 2 Alarm

affected.
Action
Yes→ End.
No→Step 2.
Yes→End.
2.1.189 198092237 Embedded power Bat Under-Temp

Alarm Information
l Name: Embedded power Bat Under-Temp
Alarm Description
This alarm occurs when the battery operating temperature is lower than the preset battery
undertemperature threshold.
Alarm Cause
1. The temperature of the battery is lower than the lower battery temperature threshold.
disconnected.
Impact
If the temperature is too low, the life of the battery will be affected.
2-331

interrupted.
Action
1. Verify that the temperature of the battery is higher than the lower battery temperature
threshold.
b. Check whether the temperature of the battery is lower than the lower battery
temperature threshold (default: -5 ℃).
Yes→Substep c.
No→Step 2.
Yes→End.
No→Step 2.
or broken.
Yes→Substep b.
No→Step 3.
Yes→End.
No→Step 3.
Yes→End.
No→Step 4.
Yes→Step 5
No→Substep b.
2-332

Chapter 2 Alarm
Yes→End.
No→Step 5.
Yes→ End.
2.1.190 198092238 Embedded power Bat Invalid-Temp

Alarm Information
l Name: Embedded power Bat Invalid-Temp
Alarm Description
This alarm occurs if the battery operating temperature is an invalid value.
Alarm Cause
1. The temperature sensor of the battery is disconnected.
disconnected.
Impact
If the temperature is too low or too high, the life of the battery will be affected.
The monitoring unit cannot detect the temperature of the battery. This may affect the
normal power supply to the base station, and all the services on the base station may be
interrupted.
Action
1. Verify that the temperature sensor is properly connected.
a. Check whether the temperature sensor is properly connected.
Yes→Step 2
No→Substep b.
2-333

b. Reconnect the temperature sensor.

Yes→End.
No→Step 2.
Yes→End.
No→Step 3.
Yes→Step 4
No→Substep b.
Yes→End.
No→Step 4.

Yes→ End.
2.1.191 198092239 Embedded power Battery Fault

Alarm Information
l Name: Embedded power Battery Fault
Alarm Description
This alarm occurs when the battery becomes faulty.
Alarm Cause
1. The battery capacity is configured, but no battery is installed.
2. The battery is not properly connected.
2-334

Chapter 2 Alarm
disconnected.
4. The battery is damaged.
Impact
None.
If all the batteries are faulty, and the AC power supply is powered off, all the services on
the base station will be interrupted.
Action
1. Verify that the configured battery capacity matches that of the installed battery.
a. Select Ctrl→Setup Para→Sys Para→Bat.1 Cap., and check the configured battery
capability.
b. Check whether the configured battery capacity matches that of the installed
battery.
Yes→Step 2.
No→Substep c.
c. Configure the battery capacity to the nominal capacity of the installed battery.
d. Retest the battery capacity after the battery is fully charged.
Yes→End.
No→Step 2.
2. Verify that the battery is properly installed.
a. Check whether the battery is properly installed.
Yes→Step 3.
No→Substep b.
b. Reinstall the battery.
Yes→End.
No→Step 3.
2-335

Yes→Step 4.
No→Substep b.
Yes→End.
No→Step 4.
4. Replace the battery and retest the battery capacity after the battery is fully charged.
Yes→End.
No→Step 5.
5. Replace the monitoring unit and retest the battery capacity after the battery is fully
charged. Refer to Components Replacement.
Yes→End.
2.1.192 198092259 Battery low-voltage alarm

Alarm Information
l Name: Battery low-voltage alarm
Alarm Description
This alarm is reported when the battery is under voltage.
Alarm Cause
set.
3. The battery voltage is too low.
Impact
2-336

Chapter 2 Alarm
If the voltage is too low, the life of the battery will be affected.
affected.
Action
Yes→Step 2.
No →Substep b.
Yes→End.
No→Step 2.
is secured).)
Yes→Substep c.
No→Substep b.
Yes→End.
No→Substep c.
Yes→Step 3.
No→Substep d.
2-337


Yes→End.
No→Step 3.
3. Charge the battery. After the battery voltage reaches the normal or a higher value,
check whether the alarm is cleared.
Yes→End.
2.1.193 198092260 Faulty external device connected at a dry

contact
Alarm Information
l Name: Faulty external device connected at a dry contact
Alarm Description
This alarm is reported when the external device at a dry contact is faulty.
Alarm Cause
set.

3. The dry contact device is faulty.
Impact
None.
Action

2-338

Chapter 2 Alarm
Yes→Step 2.
No →Substep b.
Yes→End.
No→Step 2.
is secured).)
Yes→Substep c.
No→Substep b.
Yes→End.
No→Substep c.
Yes→Step 3.
No→Substep d.
Yes→End.
No→Step 3.
Yes→End.
No→Step 4.
2-339

acement.
Yes→End.
2.1.194 198092261 Outdoor lightning protection box alarm

Alarm Information
l Name: Outdoor lightning protection box alarm
Alarm Description
Outdoor lightning protection box is faulty.
Alarm Cause
set.

3. The lightning proof device is faulty due to the lightning damage, poor contact or aging.
Impact
blocked.
Action
Yes→Step 2.
No →Substep b.
2-340

Chapter 2 Alarm

Yes→End.
No→Step 2.
is secured).)
Yes→Substep c.
No→Substep b.
Yes→End.
No→Substep c.
Yes→Step 3.
No→Substep d.
Yes→End.
No→Step 3.
3. Replace the lightning box with a proper one. Refer to Reset Boards.
Yes→End.
2.1.195 198092262 Breaker alarm in indoor lightning protection box

Alarm Information
l Name: Breaker alarm in indoor lightning protection box
2-341

Alarm Description
The breaker in an indoor lightning protection box is protected against over current or turns
in open circuit.
Alarm Cause
set.
3. The circuit breaker is under overcurrent protection or is disconnected.
Impact
None.
The power line of the corresponding circuit breaker is disconnected. If the circuit breaker
feeds the RRU, services are affected.
Action
Yes→Step 2.
No →Substep b.
Yes→End.
No→Step 2.
2-342

Chapter 2 Alarm
is secured).)
Yes→Substep c.
No→Substep b.
Yes→End.
No→Substep c.
Yes→Step 3.
No→Substep d.
Yes→End.
No→Step 3.
3. Check the status of the circuit breaker.
a. Check whether the circuit breaker is disconnected.
Yes→Substep b.
No→Step 4.
b. Identify the cause and resolve the fault.
Yes→End.
No→Step 4.
4. Replace the circuit breaker.
Yes→End.
No→Step 5.
Yes→End.
No→Step 6.
2-343


Yes→End.
2.1.196 198092263 Lightning protection device alarm in indoor

lightning protection box
Alarm Information
l Name: Lightning protection device alarm in indoor lightning protection box
Alarm Description
The lightning protection device in an indoor lightning protection box has a fault.
Alarm Cause
set.
3. The lightning proof device is faulty due to the lightning damage, poor contact or aging.
Impact
blocked.
Action
Yes→Step 2.
No →Substep b.
2-344

Chapter 2 Alarm

Yes→End.
No→Step 2.
is secured).
Yes →Substep c.
No→Substep b.
Yes→End.
No→Substep c.
Yes→Step 3.
No→Substep d.
Yes→End.
No→Step 3.
3. Check the input voltage of the master power module.
a. Check whether the input voltage of the master power module is within the following
range:
DC power voltage: -36 V to -60V
AC power voltage: 80 V to 80 V
Yes→Substep b.
No→Step 4.
b. Replace the master power supply with a proper one. Refer to Components Repla
cement.
2-345

Yes→End.
No→Step 4.
4. Ensure that the lightening proof device is properly grounded.
a. Check whether the lightening proof device is properly grounded.
Yes →Step 5.
No→Substep b.
b. Replace the lightning box. Refer to Components Replacement.
Yes→End.
No→Step 5.
Yes→End.
No→Step 6.
acement.
Yes→End.
2.1.197 198092264 Over-voltage alarm of main power input

Alarm Information
l Name: Over-voltage alarm of main power input
Alarm Description
This alarm is reported when the system detects that input voltage of the main power at dry
contact is abnormal.
Alarm Cause
set.
2-346

Chapter 2 Alarm

3. The input voltage of the master power supply is abnormal.
4. The Environmental Monitoring Unit (EMU) is faulty.
Impact
The over voltage condition may affect the lifespan of the equipment.
Either the board or the system may not work properly. All services borne on the board are
interrupted.
Action
Yes→Step 2.
No →Substep b.
Yes→End.
No→Step 2.
is secured).)
Yes→Substep c.
No→Substep b.
Yes→End.
2-347

No→Substep c.
Yes→Step 3.
No→Substep d.
Yes→End.
No→Step 3.
3. Ensure that the input voltage of the master power module is proper.
range:
AC power voltage:80 V to 280 V
Yes→Substep b.
No→Step 4.
b. Replace the master power supply with a proper one.
Yes→End.
No→Step 4.
Yes→End.
No→Step 5.
Yes→End.
2.1.198 198092265 Main power input power-cut alarm

Alarm Information
l Name: Main power input power-cut alarm
2-348

Chapter 2 Alarm

Alarm Description
This alarm is reported when the system detects that main power input at dry contact is
abnormal.
Alarm Cause
set.
Impact
None.
interrupted.
Action
Yes→Step 2.
No →Substep b.
Yes→End.
No→Step 2.
2-349


is secured).)
Yes→Substep c.
No→Substep b.
Yes→End.
No→Substep c.
Yes→Step 3.
No→Substep d.
Yes→End.
No→Step 3.
3. Ensure that the input voltag of the master power module is proper.
range:
Yes→Substep b.
No→Step 4.
Yes→End.
No →Step 4.
Yes→End.
No→Step 5.
2-350

Chapter 2 Alarm
Yes→End.
2.1.199 198092266 Under-voltage alarm of main power input

Alarm Information
l Name: Under-voltage alarm of main power input
Alarm Description
This alarm is reported when the system detects that main power input at dry contact is
abnormal.
Alarm Cause
set.

Impact
If the voltage is too low, the life of the equipment will be affected.
interrupted.
Action
Yes→Step 2.
No →Substep b.
2-351


Yes→End.
No→Step 2.
is secured).
Yes →Substep c.
No→Substep b.
Yes→End.
No→Substep c.
Yes→Step 3.
No→Substep d.
Yes→End.
No→Step 3.
3. Ensure that the input voltag of the master power module is proper.
range:
Yes→Substep b.
No→Step 4.
Yes→End.
2-352

Chapter 2 Alarm
No →Step 4.
Yes→End.
No→Step 5.
Yes→End.
2.1.200 198092267 General fault of main power

Alarm Information
l Name: General fault of main power
Alarm Description
This alarm is reported when the system detects that the main power at dry contact is faulty.
Alarm Cause
set.
Impact
None.
1) If the alarm arises on the board, the system operation is not affected temporarily, but the
2-353

2) If the alarm arises on the RRU, the system stops the operation of the power amplifier
unit, and All services operating on the RRU are interrupted.
Action
Yes→Step 2.
No →Substep b.
Yes→End.
No→Step 2.
a. Check whether the cable to the dry contact is correctly connected (for example,
whether the interface is secured).
Yes→Substep c.
No→Substep b.
Yes→End.
No→Substep c.
Yes→ Step 3.
No→Substep d.
Yes→End.
No→Step 3.
2-354

Chapter 2 Alarm
Yes→End.
No→Step 4.
ment.
Yes→End.
No→Step 5.
Yes→End.
2.1.201 198092268 PWR monitoring unit alarm

Alarm Information
l Name: PWR monitoring unit alarm
Alarm Description
This alarm is reported when PWR monitoring unit is abnormal.
Alarm Cause
set.
3. The PWR monitoring unit is damaged.
Impact
None.
2-355

The PWR monitoring unit fails to report data properly, and service may be affected.
Action
Yes→Step 2.
No→Substep b.
Yes→End.
No→Step 2.
is secured).
Yes→Substep c.
No→Substep b.
Yes→End.
No→Substep c.
Yes→Step 3.
No→Substep d.
Yes→End.
No→Step 3.
2-356

Chapter 2 Alarm
3. Replace the monitoring unit with a proper one. Refer to Components Replacement.
Yes→End.
2.1.202 198092292 Optical fiber connection error

Alarm Information
l Name: Optical fiber connection error
Alarm Description
This alarm occurs when the optical fiber is connected incorrectly.
Alarm Cause
1. The optical fibers are crossly connected improperly.
2. The incorrect optical port is used.
Impact
None.
Action
1. Select Configuration Management→Managed Element -> Device→Rack
Graph→Topology View. The Topology View tab is displayed.View the connection
relationship of the optical port in accordance with the optical port, slot, shelf, and rack
information in the Detail Information dialog box.
2. Reconnect the fiber in accordance with the connection relationship.
Yes→End.
2-357

2.1.203 198092295 Device power down

Alarm Information
l Name: Device power down
Alarm Description
This alarm occurs when the device detects that the voltage is lower than the preset
threshold.
Alarm Cause
1. The mains is abnormal.
2. The external power supply device is faulty.
Impact
None.
Services are unavailable in the corresponding cell.
Action
1. Verify that the power-feeding lines of the device are in good condition.
a. Check whether the cables and connectors have broken circuits or poor contacts.
Yes→Substep b.
No→Step 2.
b. Resolve the power line fault.
Yes→End.
No→Step 2.
2. Resolve the external power device fault.

Yes→End.
2-358

Chapter 2 Alarm
2.1.204 198092363 Faulty main power alarm

Alarm Information
l Name: Faulty main power alarm
Alarm Description
This alarm is reported when the system detects that the main power at dry contact is faulty.
Alarm Cause
set.
Impact
None.
1) If the alarm arises on a board, the system operation is not affected temporarily, but the
2) If the alarm arises on an RRU, the system stops the PA operation, and All services
operating on the RRU are interrupted.
Action
Yes→Step 2.
No →Substep b.
2-359

Yes→End.
No→Step 2.
is secured).)
Yes→Substep c.
No→Substep b.
Yes→End.
No→Substep c.
Yes→Step 3.
No→Substep d.
Yes→End.
No→Step 3.
Yes→End.
No→Step 4.
ment.
Yes→End.
No→Step 5.
2-360

Chapter 2 Alarm

Yes→End.
2.1.205 198092394 Several faulty rectifiers

Alarm Information
l Name: Several faulty rectifiers
Alarm Description
This alarm occurs when two or more than two rectifiers are faulty.
Alarm Cause
1. Multiple rectifiers are faulty.
2. The input air circuit breaker corresponding to the rectifier is disconnected.
3. One AC power phase is lost.
Impact
None.
affected.
Action
1. Check whether any related alarm exists.
a. Check whether any related alarm exists. If such an alarm exists, remove it based
on the corresponding handling suggestions. The related alarms are as follows:
198092117 Embedded power Rectifier Module Fault
198092080 Embedded power SMR Over-Vout
198092081 Embedded power SMR Over-Iout
198092082 Embedded power SMR Fan Fault
198092083 Embedded power SMR PFC Fault
198092084 Embedded power SMR Over-Vin Off
2-361

198092085 Embedded power SMR Under-Vin Off

198092086 Embedded power SMR H.T. Off
198092087 Embedded power SMR Env.H.T.Off
198092088 Embedded power SMR Env.H.T
198092089 Embedded power SMR L.Vin
198092090 Embedded power SMR Fuse Broken
198092091 Embedded power SMR CommFail
198092236 Embedded power SMR Output Fault
Yes→End.
No→Step 2.
2. Check whether any AC voltage phase is lost.
module, and check whether any AC input voltage phase is lost.
Yes→Substep b.
No→Step 3.
b. Troubleshoot the AC input failure of the embedded power.
Yes -> End.
Yes→End.
2.1.206 198092426 The GNSS cascading clock is faulty

Alarm Information
l Name: The GNSS cascading clock is faulty
Alarm Description
In Global Navigation Satellite System (GNSS) cascading reference clock source mode,
this alarm occurs when the link fails to operate properly or satellite searching fails.
2-362

Chapter 2 Alarm
Alarm Cause
1. The GNSS information channel between the upper-level board and the local board is
abnormal.
2. The satellite search by the upper-level board is abnormal due to an open or short circuit
of the GPS antenna and feeder, or the received satellite signal is weaker than the set
searching threshold.
Impact
None.
Some or all of the services on the base station are blocked.
Action
Perform the following operations based on the additional alarm information in alarm details:
Satellite search failed or 1PPS is lost:
1. According to network planning, check whether the following alarms exist on the
upper-level equipment of the GNSS cascading clock:
Yes→Step 2.
2. Handle the alarms according to corresponding suggestions.
3. After 15 minutes, check whether the alarm is cleared.
Yes→End.
The serial port of the GNSS cascading clock source cannot receive any message:
1. According to network planning, check whether the GNSS cascading clock parameters
are configured correctly in the same-level and upper-level BBUs.
a. Check whether the reference clock source planned for this base station contains
the GNSS cascading clock.
Yes→ Substep e.
No→Substep b.
b. Select Configuration Management -> Managed Element→Device→B8200, and
2-363

clock source. Select ClockDevice Set→Clock Device, and delete the GNSS
cascading reference clock source of the local base station .
Yes→End.
e. Select Configuration Management→Managed Element→Device→B8200, and
confirm the main control board slot (slot 1 or slot 2) configured for the reference
clock source. Select ClockDevice Set, and check whether the configured
cascading clock output mode is GNSS cascading output.
Yes→Step 2.
No→Substep f.
f. Select Configuration Management→Managed Element→Device→B8200, and
clock source. Select ClockDevice Set, and change the configured cascading
clock output mode to GNSS cascading output.
g. Synchronize the configurations to the corresponding NE.
h. After 15 minutes, check whether the alarm is cleared.
Yes→End.
No→Step 2.
2. Check whether the GNSS cascading clock cable is securely connected.
Yes→Step 4.
No→ Step 3.
3. Connect the cable correctly.
Yes→End.
No→ Step 4.
4. Change a cable.
Yes→End.
No→Step 5.
Yes→End.
No→Step 6.
2-364

Chapter 2 Alarm
Yes→End.
2.1.207 198092435 Inter-subrack Ethernet link broken in stack mode

Alarm Information
l Name: Inter-subrack Ethernet link broken in stack mode
Alarm Description
This alarm occurs when the inter-subrack Ethernet link (ETH1) is broken in stack mode.
Alarm Cause
1. The network cable is not connected properly.
2. The network cable is damaged.
3. The interface modes of the master and slave shelves are different.
Impact
None.
All the services on the slave shelf are blocked.
Action
1. Check whether the stack Ethernet cables are connected properly.
a. Check whether the stack Ethernet cables are connected properly.
Yes→Step 2.
No→Substep b.
b. Connect the Ethernet cables properly.
Wait 15 minutes and check whether the alarm is cleared.
Yes→End.
No→Step 2.
2-365

2. Replace the stack Ethernet cables.

Yes→End.
No→ Step 3.
3. Check whether the operation modes of the network ports of the two stack shelves are
the same.
a. Select Configuration Management→Managed Element→Transmission
Network→UMTS→Physical Hosting→Physical Layer Port, and check whether
the operation modes are the same.
Yes→Contact the customer service center.
No→Substep b.
b. Set the operation modes of the network ports to self-adaptive.
Yes→End.
2.1.208 198092447 Unbalanced AC phase voltage of built-in power

Alarm Information
l Name: Unbalanced AC phase voltage of built-in power
Alarm Description
This alarm occurs when the AC phase voltage is not balanced.
Alarm Cause
1. The AC power network is faulty.
Impact
When the difference between phase-to-neutral voltages is too large, equipment life may
be affected.
2-366

Chapter 2 Alarm
When the rectifier output is abnormal, the normal power supply to the base station is
affected. Some of the services on the base station may be blocked, or service quality
may be affected.
Action
1. Check whether a difference between AC phase-to-neutral voltages is higher than the
AC imbalance threshold.
module, and check the AC phase-to-neutral voltage values, and calculate the
differences.
b. Check whether a difference between AC phase-to-neutral voltages is higher than
the AC imbalance threshold (default: 55 V).
Yes→Substep c.
No→Step 2.
Yes→End.
No→ Step 2.
Yes→End.
2.1.209 198092448 High AC phase current of built-in power

Alarm Information
l Name: High AC phase current of built-in power
Alarm Description
This alarm occurs when the AC phase voltage is too high.
Alarm Cause
1. The AC input current is higher than the upper AC current threshold.
2. The AC input voltage is too low.
3. The power supply is overloaded.
2-367

Impact
Long-period overcurrent may lead to the overtemperature of the AC input loop and the
ageing of cables.
Long-period overcurrent leads to the overtemperature of the AC input, which may result
in the disconnection of the air switch of the AC input. If the base station powers down, all
the services on the base station are interrupted.
Action
1. Verify that the AC input current is not higher than the upper AC current threshold.
module, and check the AC input current value.
b. Check whether the AC input current is higher than the upper AC current threshold
(default: 80 A).
Yes→ Step 2.
No→Step 3.
2. Verify that the AC input voltage is normal.
b. Check whether the AC input voltage is lower than the standard AC input voltage.
Yes→Substep b.
No→Step 3.
c. Troubleshoot the AC input fault of the embedded power supply.

After related faults are handled, wait for 15 minutes, and check whether the alarm
is cleared.
Yes→End.
No →Step 3.

the rectifier.
2-368

Chapter 2 Alarm
Yes→Substep c.
No→Step 4.
Yes→End.
No→Step 4.
Yes→Step 5.
No→Substep b.
Yes→End.
No→Step 5.
Yes→End.
2.1.210 198092449 Missing AC phase voltage of built-in power

Alarm Information
l Name: Missing AC phase voltage of built-in power
Alarm Description
This alarm occurs when an AC phase lacks.
Alarm Cause
1. The AC input cable is disconnected.
2-369

Impact
None.
The rectifier cannot operate normally, and the normal power supply to the base station is
affected.
Action
1. Check the connection of the AC input cable.
a. Check whether the connection of the AC input cable is correct.
Yes→Step 2.
No→Substep b.
b. Connect the AC input cable properly.
Yes→End.
No→Step 2.
2. Check whether the detection cable of the AC transducer is not disconnected.
a. Check whether the detection cable of the AC transducer is not disconnected.
Yes→Substep b.
No→Step 3.
Yes→End.
No→Step 3.
Yes→Step 4.
No→Substep b.
Yes→End.
2-370

Chapter 2 Alarm
No→Step 4.
Yes→End.
2.1.211 198092450 Battery low-voltage cut-off of built-in power

Alarm Information
l Name: Battery low-voltage cut-off of built-in power
Alarm Description
This alarm occurs when the battery voltage is lower than the preset voltage threshold for
battery power-down and all loads are powered down.
Alarm Cause
1. The voltage of the battery is lower than the power-off voltage threshold of the battery.
Impact
None.
If all the batteries are powered off and the AC power supply is powered off, all the services
on the base station are interrupted.
Action
Embedded power AC Power Off (198092074)
Yes→End.
2-371

No→Step 2.
connected status.
Yes→Step 3.
No→ Substep b.
connected.
Yes→End.
No →Step 3.
3. Verify that the cable of the power-off DC contactor of the battery is secured or is
properly connected.
a. Check whether the cable of the power-off DC contactor of the battery is not secured
or is broken.
Yes→Substep b.
No→Step 4.
Yes→End.
No →Step 4.
4. Verify that the power-off DC contactor of the battery is in good condition.
Yes→Substep b.
No→Step 5.
b. Replace the power-off DC contactor of the battery.
Yes→End.
No →Step 5.
Yes→Step 6.
No→Substep b.
2-372

Chapter 2 Alarm

Yes→End.
No→Step 6.
Yes→End.
2.1.212 198092451 Broken LLVD1 branch E of built-in power

Alarm Information
l Name: Broken LLVD1 branch E of built-in power
Alarm Description
This alarm occurs when the extended branch of Load Low Voltage Disconnect 1 (LLVD1)
is broken.
Alarm Cause
1. The fuse of the LLVD1 extended branch blows (or is broken).
2. The detection cable of the LLVD1 extended branch is broken or is not in good contact.
disconnected.
4. The monitoring unit is damaged.
Impact
None.
All devices connected to the branch power down, and all or some of the services on the
base station may be interrupted.
Action
Yes→Substep b.
2-373

No→Step 2.
Yes→End.
No→Step 2.
configuration.
Yes→Step 3.
No→Substep c.
Yes→End.
No→Step 3.
Yes→Substep b.
No→Step 4.
Yes→End.
No→Step 4.
Yes→Step 5.
No→Substep b.
Yes→End.
No→Step 5.
Yes→End.
2-374

Chapter 2 Alarm
2.1.213 198092452 Broken LLVD1 branch of built-in power

Alarm Information
l Name: Broken LLVD1 branch of built-in power
Alarm Description
This alarm occurs when the LLVD1 branch is broken.
Alarm Cause
1. The fuse of the LLVD1 branch blows (or is broken).
2. The detection cable of the LLVD1 branch is broken or is not in good contact.
disconnected.
Impact
None.
Action
Yes→Substep b.
No→Step 2.
Yes→End.
No→Step 2.
2-375

configuration.
Yes→Step 3.
No→Substep c.
Yes→End.
No→Step 3.
3. Verify that the preset circuit breaker threshold is appropriate.
a. Select Setup Para→Alarm Para, and check the circuit breaker threshold.
b. Check whether the preset circuit breaker threshold (default: 0.5 V) is appropriate.
Yes→Step 4.
No→Substep c.
c. Modify the circuit breaker threshold to the default value.
Yes→End.
No→Step 4.
Yes→Substep b.
No→Step 5.
Yes→End.
No→Step 5.
Yes→Step 6.
No→Substep b.
Yes→End.
No→Step 6.
2-376

Chapter 2 Alarm

Yes→ End.
2.1.214 198092453 Broken LLVD2 branch E of built-in power

Alarm Information
l Name: Broken LLVD2 branch E of built-in power
Alarm Description
This alarm occurs when the LLVD2 branch is broken.
Alarm Cause
1. The fuse of the LLVD2 extended branch blows (or is broken).
2. The detection cable of the LLVD2 extended branch is broken or is not in good contact.
disconnected.
Impact
None.
Action
Yes→Substep b.
No→Step 2.
2-377

Yes→End.
No→Step 2.
configuration.
Yes→Step 3.
No→Substep c.
Yes→End.
No→Step 3.
Yes→Step 4.
No→Substep c.
Yes→End.
No→Step 4.
Yes→Substep b.
No→Step 5.
Yes→End.
No→Step 5.
Yes→Step 6.
No→Substep b.
2-378

Chapter 2 Alarm

Yes→End.
No→Step 6.
Yes→ End.
2.1.215 198092454 Broken battery cut-off branch E of built-in power

Alarm Information
l Name: Broken battery cut-off branch E of built-in power
Alarm Description
This alarm occurs when the battery power-down extended branch is broken.
Alarm Cause
1. The fuse of the battery power-down extended branch blows (or is broken).
2. The detection cable of the battery power-down extended branch is broken or is not in
good contact.
disconnected.
Impact
None.
Action
Yes→Substep b.
2-379

No→Step 2.
Yes→End.
No→Step 2.
configuration.
Yes→Step 3.
No→Substep c.
Yes→End.
No→Step 3.
Yes→Step 4.
No→Substep c.
Yes→End.
No→Step 4.
Yes→Substep b.
No→Step 5.
Yes→End.
No→Step 5.
2-380

Chapter 2 Alarm
Yes→Step 6.
No→Substep b.
Yes→End.
No→Step 6.

Yes→ End.
2.1.216 198092455 Broken battery cut-off branch of built-in power

Alarm Information
l Name: Broken battery cut-off branch of built-in power
Alarm Description
This alarm occurs when the battery power-down branch is broken.
Alarm Cause
1. The fuse of the battery power-down branch blows (or is broken).
2. The detection cable of the battery power-down branch is broken or is not in good contact.
disconnected.
Impact
None.
2-381

Action
Yes→Substep b.
No→Step 2.
Yes→End.
No→Step 2.
configuration.
Yes→Step 3.
No→Substep c.
Yes→End.
No→Step 3.
Yes→Step 4.
No→Substep c.
Yes→End.
No→Step 4.
Yes→Substep b.
No→Step 5.
2-382

Chapter 2 Alarm
Yes→End.
No→Step 5.
Yes→Step 6.
No→Substep b.

Yes→End.
No→Step 6.

Yes→ End.
2.1.217 198092456 Abnormal battery current of built-in power

Alarm Information
l Name: Abnormal battery current of built-in power
Alarm Description
This alarm occurs when the battery current is abnormal.
Alarm Cause
The monitoring unit is faulty.
Impact
Batteries may be overcharged or undercharged, and the battery life will be affected.

If the base station depends on the power supply of the batteries, all or some of the services
on the base station may be interrupted.
2-383

Action
Replace the monitoring unit. Refer to Components Replacement.
Yes→End.
2.1.218 198092457 Abnormal CAN bus of built-in power

Alarm Information
l Name: Abnormal CAN bus of built-in power
Alarm Description
This alarm occurs when the Controller Area Network (CAN) bus is abnormal.
Alarm Cause
The CAN bus communication is interrupted.
Impact
The over voltage or temperature condition may affect the lifespan of the equipment.
The monitoring unit cannot manage batteries or take AC voltage samples. This makes it
difficult to determine whether the AC power supply is powered off, and the normal power
supply to the base station may be affected. If the base station powers down, all the services
on the base station may be interrupted.
Action
Verify that the CAN bus is not disconnected or broken.
1. Check whether the CAN bus is disconnected or broken.
Yes→Step 2.
2. Reconnect or replace the bus.
Yes→End.
2-384

Chapter 2 Alarm
2.1.219 198092458 Abnormal battery of built-in power

Alarm Information
l Name: Abnormal battery of built-in power
Alarm Description
This alarm occurs when the battery is abnormal.
Alarm Cause
1. The battery is not correctly installed.
2. The capacity of the battery is not enough, or the battery is undercharged.
disconnected.
Impact
None.
interrupted.
Action
1. Verify that the configured battery capacity matches that of the installed battery.
a. Select Ctrl→Setup Para→Sys Para→Bat.1 Cap., and check the configured battery
capability.
b. Check whether the configured battery capacity matches that of the installed
battery.
Yes→Step 2.
No→Substep c.
c. Configure the battery capacity to the nominal capacity of the installed battery.
d. Retest the battery capacity after the battery is fully charged.
Yes→End.
No→Step 2.
2-385

2. Verify that the battery is properly installed.

a. Check whether the battery is properly installed.
Yes→Step 3.
No→Substep b.
b. Reinstall the battery.
Yes→End.
No→Step 3.
Yes→Step 4.
No→Substep b.
Yes→End.
No→Step 4.
4. Replace the battery and retest the battery capacity after the battery is fully charged.
Yes→End.
No→Step 5.
5. Replace the monitoring unit and retest the battery capacity after the battery is fully
charged. Refer to Components Replacement.
Yes→End.
2.1.220 198092459 Abnormal input dry contact of built-in power

Alarm Information
l Name: Abnormal input dry contact of built-in power
2-386

Chapter 2 Alarm
Alarm Description
This alarm occurs when the input dry contact is abnormal.
Alarm Cause
1. The external device is faulty.
Impact
None.
may be affected.
Action
1. Verify that the device connected to the input dry contact can operate normally.
a. Check whether the device connected to the input dry contact can operate normally.
Yes→Step 2.
No→Substep b.
b. Troubleshoot the external device.
Yes→End.
No→Step 2.
Yes→ End.
2.1.221 198092460 High-temperature cut-off of built-in power

Alarm Information
l Name: High-temperature cut-off of built-in power
2-387

Alarm Description
This alarm occurs when the environment temperature is higher than the preset
high-temperature threshold for power-down and the battery stops working.
Alarm Cause
1. The battery temperature is higher than that in high temperature state.
2. The temperature sensor of the battery is faulty.
disconnected.
Impact
None.
The normal power supply to the base station may be affected. If the base station powers
down, all the services on the base station may be interrupted.
Action
1. Verify that the battery temperature is lower than that in high temperature state.
b. Check whether the battery temperature is higher than that in high temperature
state (default: 50 ℃).
Yes→Substep c.
No→Step 2.
Yes→End.
No→Step 2.
or broken.
Yes→Substep b.
No→Step 3.
2-388

Chapter 2 Alarm

Yes→End.
No→ Step 3.
Yes→End.
No→Step 4.
Yes→Step 5.
No→Substep b.
Yes→End.
No→ Step 5.
Yes→End.
2.1.222 198092461 Failure in frame synchronization between BBU

subracks
Alarm Information
l Name: Failure in frame synchronization between BBU subracks
Alarm Description
This alarm occurs when frame synchronization between BBU subracks fails.
Alarm Cause
The clock phase provided by the main control board does not satisfy the inter-shelf IQ data
sharing requirement.
2-389

Impact
None.
The IQ data between shelves is not properly accumulated, and all the services on the slave
shelf are interrupted.
Action
1. Verify that the operating mode of the base station is configured as planned.
a. Select Configuration Management -> Managed Element→Device, and
double-click Device. The Physical View and Topology View are displayed. Click
Back to List to enter the equipment list window. Check whether the stack mode
of BBU shelves is configured as planned.
Yes→Step 2.
No→Substep b.
b. Modify the stack mode of BBU shelves as planned.
Yes→End.
No →Step 2.
2. Remove and re-install the stack clock cable.
Yes→End.
No→Step 3.
3. Replace the stack clock cable. Refer to Components Replacement.
Yes→End.
No→Step 4.
4. Verify that the IQ optical fiber of the cross shelf is of the proper length.
a. Check whether the length of the IQ optical fiber of the cross shelf is longer than
10 m.
Yes→Substep b.
b. Shorten the length of the optical fiber.
Yes→End.
2-390

Chapter 2 Alarm
2.1.223 198096830 Too large phase difference between clock

sources
Alarm Information
l Name: Too large phase difference between clock sources
Alarm Description
This alarm occurs when the phase difference between the active clock source and the first
standby clock source exceeds the preset threshold.
Alarm Cause
1. The clock source is interfered.
2. The delay of the clock source introduction device is not properly configured.
Impact
None.
If the first standby clock source of the base station is the same as the active clock source of
the adjacent base station, both base stations may interfere with each other and the service
quality is affected.
Action
1. Verify that the clock source contains any built-in GNSS, external front panel GNSS or
external backplane GNSS.
a. Check whether the clock source contains any built-in GNSS, external front panel
GNSS or external backplane GNSS according to the additional alarm information
in the alarm details.
Yes→Substep b.
No→Step 2.
b. Select Configuration Management→Managed NE→Device→Cabinet (for
example, B8200), and check the main control board slot (slot 1 or slot 2)
configured for the clock reference source. Select ClockDevice Set→Clock
2-391

Device, and check whether the length of the GNSS antenna feeder cable is
configured according to the actual conditions.
Yes→Step 2.
No→Substep c.
c. Modify the length of the GNSS antenna feeder cable to the actual values.
e. Wait for 15 minutes, and check whether the alarm is cleared.
Yes→End.
No→Step 2.
2. Verify that the clock source contains GNSS built in the RRU.
a. Check whether the clock source contains GNSS built in RRU according to the
additional alarm information in the alarm details.
Yes→Substep b.
No→Step 3.
b. Select Configuration Management→Managed Element→Device→Cabinet (for
example, RRU)→GNSS Device Set -> GNSS Set, and check whether the
length of the GNSS antenna feeder cable is configured according to the actual
conditions.
Yes →Step 3.
No→Substep c.
Yes→End.
No →Step 3.
3. Verify that the clock source contains 1PPS+TOD or 1PPS+TOD backup.
a. Check whether the clock source contains 1PPS+TOD or 1PPS+TOD backup
according to the additional alarm information in the alarm details.
Yes→Substep b.
No→Step 4.
b. Select Configuration Management→Managed NE→Device -> Cabinet (for
configured for the clock reference source. Select ClockDevice Set→Clock Device,
and check whether the Cascade cable length and Fixed delay compensation are
configured according to the actual conditions.
Yes→Step 4.
2-392

Chapter 2 Alarm
No→Substep c.
c. Modify the Cascade cable length and Fixed delay compensation to the actual
values.
Yes→End.
No→Step 4.
4. Verify that the clock source contains SyncE+1588.
a. Check whether the clock source contains SyncE+1588 according to the additional
alarm information in the alarm details.
Yes→Substep b.
No→Step 5.
b. Select Configuration Management→Managed NE→Device→Cabinet (for
configured for the clock reference source. Select ClockDevice Set→Clock
Device, and check whether the Fixed delay compensation is configured the same
as the actual conditions.
Yes→Step 5.
No→Substep c.
c. Modify the Fixed delay compensation to the actual value.
Yes→End.
No→Step 5.
5. Verify that the clock source contains the backplane 1PPS+TOD.
a. Check whether the clock source contains the backplane 1PPS+TOD according to
the additional alarm information in the alarm details.
Yes→Substep b.
No→Step 6.
b. Select Configuration Management→Managed Element→Device→Cabinet (for
example, B8200), and check the slot on the UCI board (slot 5 or slot 7). Select
GNSS Device Set→GNSS Set, and check whether the length of the GNSS
antenna feeder cable is configured according to the actual conditions.
Yes→Step 6.
No→Substep c.
2-393


Yes→End.
No →Step 6.
6. Verify that the clock source contains any built-in GNSS, external front plane GNSS,
external backplane GNSS, GNSS built in RRU or backplane 1PPS+TOD.
a. Check whether the clock source contains any built-in GNSS, external front panel
GNSS, external backplane GNSS, GNSS built in RRU or backplane 1PPS+TOD
according to the additional alarm information in the alarm details.
Yes→Substep b.
b. Check whether there is any GNSS interference source in the neighboring
environment by using a frequency sweeper.
Yes→Substep c.
c. Clear the interference source.
d. Wait for 15 minutes, and check whether the alarm is cleared.
Yes→End.
2.1.224 198096831 1588 clock source fault

Alarm Information
l Name: 1588 clock source fault
Alarm Description
This alarm occurs when the 1588 clock source is unavailable or the link is faulty.
Alarm Cause
1. There is no 1588 clock link channel available.
2. It is impossible to communicate with master clock of the link.
3. The link encounters a serious network congestion problem.
4. When the standard message format is enabled, it is impossible to trace master clock
source of the link.
2-394

Chapter 2 Alarm
Impact
None.
If only clock 1588 is configured as the clock reference source, and if packets get lost for a
long time, soft switch cannot be guaranteed, and the services on this base station may be
blocked and service quality is affected.
Action
198098252 The physical Ethernet link is broken
Yes→End.
No→Step 2.
2. Select Diagnosis Test and query clock 1588 to check whether the packet loss rate,
clock level, and traceable clock are abnormal.
If the packet loss rate is not in normal status:
a. Check whether the packet loss rate is almost 100%.
Yes→Step 3.
No→Substep b.
b. Ask the corresponding maintenance personnel to remove the fault.
Yes→End.
No→Step 3.
If the clock level/traceable clock information is abnormal:
Ask the corresponding maintenance personnel to remove the fault.
Yes→End.
No→Step 3.
3. Check whether the IP clock parameters are configured correctly.
Network→UMTS→IP Clock→IP Clock Parameters and check whether the
network protocol, IP clock transmission mode, and the synchronization server
address are the same as planned.
2-395


No→Substep b.
b. Modify them to the settings as planned.
Yes→End.
2.1.225 198096835 GNSS receiver fault

Alarm Information
l Name: GNSS receiver fault
Alarm Description
l This alarm occurs when the inner GNSS receiver has a fault or is unavailable.
l This alarm occurs in one of the following conditions when the external front panel or
external backplane GNSS reference source is configured:
à The RGPS receiver is powered off.
à The receiver is faulty or the link to the external front panel GNSS receiver is
interrupted.
à The temperature of the RGPS receiver is abnormal.
à The main control board detects that the receiver mode read from the hardware is
inconsistent with that configured on the OMC.
Alarm Cause
1. The GNSS receiver is damaged or the link connected with the receiving unit is abnormal.
2. The RGPS receiver is powered off.

3. The environmental temperature exceeds the threshold or the temperature sensor is
faulty.
Impact
None.
2-396

Chapter 2 Alarm
The processing capability of the board is reduced. Some functions cannot operate
properly. In serious cases, wireless links cannot be established, and all or some of the
services on this board may be blocked, and service quality is affected.
Action
l Inner GNSS receiver communication failure/1PPS of Inner GNSS receiver is lost:
1. Reset the board based on the Rack Number, Shelf Number and Slot Number in
alarm details. Refer to Reset Boards.
Yes→End.
No→Step 2.
Yes→End.
l The external front panel RGPS receiver is powered off/The external backplane RGPS
receiver is powered off:
Switch on power supply of the RGPS receiver on the front or back panel.
Yes→End.
l The external front panel GNSS receiver communication failure/1PPS of the external
front panel GNSS receiver is lost:
1. Select Configuration Management→Managed Element→Device→B8200, and
clock source. Select ClockDevice Set→Clock Device, check the GNSS receiver
type, for example, external BeiDou receiver, RGPS, UCI_RGPS, or USR1_A.
2. Perform the corresponding operations for different receivers:
External BeiDou receiver:
a. Check whether the BeiDou receiver is powered off.
Yes→Substep b
No→Substep c.
b. Switch on power supply of the receiver.
Yes→End.
2-397

No→Substep c.
c. Check whether cables are connected properly.
Yes→Substep e.
No→Substep d.
d. Connect the cables correctly.
Yes→End.
No→Substep e.
e. Change the cables.
Yes→End.
No→Substep f.
f. Replace the BeiDou receiver.
Yes→End.
RGPS:
a. Check whether cables are connected properly.
Yes→Substep c.
No→Substep b.
b. Connect the cables correctly.
Yes→End.
No→Substep c.
c. Change the cables.
Yes→End.
No→Substep d.
d. Replace the RGPS. Refer to Components Replacement.
Yes→End.
UCI_RGPS:
2-398

Chapter 2 Alarm
a. Check whether any related alarm exists. If the related alarm exists, remove it
based on the corresponding handling suggestion. The related alarms are as
follows:
198096835 GNSS receiver fault (The RGPS receiver whose clock reference
is provided by the front panel is powered off)
Yes→End.
No→Substep c.
c. Select Dynamic Management→Dynamic Command→SDR→Managed
Network Element and reset the RGPS to reset the receiver connected to this
board in accordance with Rack Number, Shelf Number, and Slot Number in
alarm details.
Yes→End.
No→Substep d.
d. Check whether cables are connected properly.
Yes→Substep f.
No→Substep e.
e. Connect the cables correctly.
Yes→End.
No→Substep f.
f. Change a cable.
Yes→End.
No→Substep g.
g. Replace the receiver connected with this board in accordance with the Rack
Number, Shelf Number and Slot Number in alarm details. After 15 minutes,
Yes→End.
USR1_A:
a. Check whether the USR1_A board operates properly.
Yes→Substep b.
2-399

No→Substep e.
b. Check whether the cable is connected properly.
Yes →Substep d.
No→Substep c.
c. Connect the cable correctly.
Yes→End.
No→Substep d.
d. Change the cable.
Yes→End.
No→Substep e.
e. Replace the USR1_A board.
Yes→End.
l The temperature of the external front panel RGPS receiver is abnormal/The
temperature of the external backplane RGPS receiver is abnormal:
1. Check whether the environmental temperature exceeds 55 ℃.
Yes→Step 2.
No→Step 3.
2. Reduce the temperature (for example, eliminating the impact of air conditioner
faults and high-power heating devices in the environment).
After the environmental temperature is reduced, wait 15 minutes and check
Yes→End.
No→Step 3.
3. Select Dynamic Management -> Dynamic Command→SDR-> Managed Network
Element and reset the RGPS to reset the receiver connected to this board in
accordance with the panel or back panel information in the additional information
in alarm details.
Yes→End.
No→Step 4.
4. Replace the receiver in accordance with the panel or back panel information in
the additional information.
2-400

Chapter 2 Alarm

Yes→End.
l The external backplane GNSS receiver communication failure/1PPS of the external
backplane GNSS receiver is lost:
a. Check whether any related alarm exists. If the related alarm exists, remove
it based on the corresponding handling suggestion. The related alarms are as
follows:
198096835 GNSS receiver fault (The RGPS receiver whose clock reference is
provided by the front panel is powered off)
Yes→End.
No→Step 2.
2. Select Dynamic Management→Dynamic Command→SDR-> Managed Network
Element and reset the RGPS to reset the external back panel receiver connected
to this board in accordance with Rack Number, Shelf Number, and Slot Number
in alarm details.
Yes→End.
No→Step 3.
3. In Dynamic Management, reset the main control board.
Yes→End.
No→Step 4.
4. Check whether the cable is connected properly.
Yes→Step 6.
No→Step 5.
Yes→End.
No→Step 6.
6. Change a cable.
2-401

Yes→End.
No→Step 7.
7. Replace the receiver connected to this board in accordance with the Rack
Number, Shelf Number and Slot Number in alarm details. Refer to Components
Replacement.
Yes→ End.
2.1.226 198096836 GNSS antenna feeder link fault

Alarm Information
l Name: GNSS antenna feeder link fault
Alarm Description
This alarm occurs when the antenna feeder of the inner/external front panel/external
backplane GNSS receiver is faulty.
Alarm Cause
1. The GNSS antenna cable is not connected properly, or is damaged or is penetrated by
water.
2. The GNSS lightning arrester is damaged.
3. The GNSS antenna is damaged.
Impact
None.
Action
1. Check whether GNSS antenna feeder cables are connected properly.
2-402

Chapter 2 Alarm
a. Check whether cables are connected properly (for example, whether the port is
loose or the cable is not connected).
Yes→Step 2.
No→Substep b.
b. Connect the cables correctly.
Yes→End.
No→Step 2.
2. Check whether the connector that connects the antenna and the feeder is in normal
status.
a. Check whether the connector that connects the antenna and the feeder is in
normal status (whether it is rusty or is penetrated by water).
Yes→Substep b.
No→Step 3.
b. Replace the connector.
Yes→End.
No→Step 3.
3. Check whether the cable of the feeder is in good condition.
a. Disconnect the GNSS antenna from the feeder, and disconnect the feeder from
the lightning arrester.
b. On one end of the feeder, measure the resistance between the feeder core and
the shielding layer by using a multimeter. Check whether the resistance is infinity.
Yes →Substep c.
No→Substep d.
c. On one end of the feeder, create a short circuit between the feeder core and the
shielding layer. On the other end, measure the resistance between the feeder core
and the shielding layer by using a multimeter. Check whether the resistance is 0.
Yes→Step 4.
No→Substep d.
d. Replace the feeder cable in accordance with the GNSS installation manual.
Yes→End.
No→Step 4.
4. Check whether the lightning arrester operates properly.
2-403

a. Disconnect the lightning arrester from the feeder, and disconnect the lightning
arrester from the jumper.
b. Measure the resistance between the core and the ground on both ends of the
lightning arrester by using a multimeter. Check whether the resistance is infinity.
Yes→Substep c.
No→Substep d.
c. Measure the resistance between two cores on both ends of the lightning arrester
by using a multimeter. Check whether the resistance is 0. If the lightning arrester
has two output channels, check the resistance between the core of CH1 and the
core of the input channel.
Yes→Step 5.
No→Substep d.
d. Replace the lightning arrester in accordance with the GNSS installation manual.
Yes→ End.
No→Step 5.
5. Check whether the jumper cable is in good condition.
a. Disconnect the lightning arrester from the jumper, and disconnect the jumper from
the board.
b. On one end of the feeder, measure the resistance between the jumper core and
the shielding layer by using a multimeter. Check whether the resistance is infinity.
Yes→Substep c.
No→Substep d.
c. On one end of the jumper, create a short circuit between the jumper core and the
shielding layer. On the other end, measure the resistance between the jumper
core and the shielding layer by using a multimeter. Check whether the resistance
is 0.
Yes→Step 6.
No→ Substep d.
d. Replace the jumper cable in accordance with the GNSS installation manual. Refer
Yes→End.
No→Step 6.
6. Replace the GNSS antenna. Refer to Components Replacement.
2-404

Chapter 2 Alarm
Yes→End.
No→Step 7.
7. Reset the receiver. Refer to Reset Boards.
a. Select Configuration Management→Managed Element→Device→B8200,
clock source. Select ClockDevice Set→Clock Device, check whether the GNSS
receiver is UCI_RGPS.
Yes→Substep b.
No→ Step 8.
b. Select Dynamic Management→Dynamic Command→SDR -> Managed Network
Element and reset the RGPS to reset the external receiver connected to this board
in accordance with Rack Number, Shelf Number, and Slot Number in alarm details.
Yes→End.
No→ Step 8.
Yes→End.
No→Step 9.
Yes→End.
2.1.227 198096838 Clock source abnormal in stack mode

Alarm Information
l Name: Clock source abnormal in stack mode
Alarm Description
This alarm occurs when the clock line is abnormal in stack mode, or when it fails to
synchronize the slave clock with the master clock in stack mode.
2-405

Alarm Cause
1. The stack clock cable is not connected properly or is damaged.
2. The main control board on the slave subrack is faulty.
Impact
None.
Cross-shelf (master-slave) services are affected.
Action
1. Remove and reinstall the stack clock cable.
Yes→End.
No→Step 2.
2. Replace the stack clock cable. Refer to Components Replacement.
Yes→End.
No→ Step 3.
3. Reset the main control board on the slave shelf. Refer to Reset Boards.
Yes→End.
No→Step 4.
4. Replace the main control board on the slave shelf. Refer to Components Replaceme
nt.
Yes→End.
2.1.228 198097004 Board hardware fault

Alarm Information
l Name: Board hardware fault
2-406

Chapter 2 Alarm
Alarm Description
This alarm occurs when the board has a hardware fault.
Alarm Cause
Board hardware fault.
Impact
None.
All the services on the board are blocked.
Action
1. Reset the board in accordance with the Rack Number, Shelf Number and Slot Number
information in alarm details. Refer to Reset Boards.
Yes→End.
No→Step 2.
2. Check whether the board hardware testing function is available in the toolbar during
the diagnosis testing.
Yes→Step 3.
No→Step 4.
3. Test the board during the diagnosis testing and further perform corresponding
operations in accordance with the testing result.
Yes→End.
No→Step 4.
Yes→End.
2.1.229 198097060 Board communication link interrupted

Alarm Information
2-407

l Name: Board communication link interrupted

Alarm Description
This alarm occurs when the communication link of the board is broken.
Alarm Cause
The link between this board and master main control board is faulty.
Impact
None.
The board cannot communicate with the main control master board, causing the services
operating on the board to be interrupted.
Action
1. Remove the re-install the board in accordance with the slot, shelf, rack information in
the Detail Information dialog box.
Yes→End.
No→Step 2.
a. Check whether the board can be installed to another slot in accordance with the
network planning data.
Yes→Substep b.

c. Select Configuration Management -> Managed Element→Device→Rack Graph.
The Rack Graph tab is displayed. Delete the board configuration of the previous
slot, and configure the baord for the new slot.
Yes→End.
2-408

Chapter 2 Alarm
2.1.230 198097109 E1/T1 link is interrupted

Alarm Information
l Name: E1/T1 link is interrupted
Alarm Description
The system checks the Bit Error Rate (BES) information of E1/T1 link periodically, and
reports the alarm according to the statistical data. This alarm is used to indicate error
code situation over the transmission link. When the error code situation is serious, a link
broken alarm is reported.
Alarm Cause
The E1/T1 physical link is abnormal.
Impact
None.
All the services on the E1/T1 link are interrupted.
Action
1. Verify that the cable of the equipment is connected properly.
a. Check whether the cables in the distribution frame, the transmission equipment
(for example, the optical transceiver or the repeater) ports and E1/T1 on the
SA/SE/PSA front panels are connected properly, for example, whether there is
any short circuit between the cores or wires of a cable because of any unsecured
connector or other objects around the distribution frame.
Yes→Step 2.
No→Substep b.
b. Reconnect the equipment cables.
Yes→End.
No →Step 2.
2. Verify that the grounding busbar of the equipment is connected properly.
a. Check whether the distribution frame, the transmission equipment and the base
station are connected properly to the same grounding busbar, and whether any of
2-409

the following situations occurs: the cable is too thin, connectors are not secured,
the grounding busbar is corroded, the joint is insulated or there is no grounding
busbar.
Yes→Step 3.
No→Substep b.
b. Reconnect or replace the cable between the equipment and the grounding busbar.
Yes→End.
No→Step 3.
3. Replace the E1/T1 cables on the SA/SE/PSA front panels.
Yes→End.
No→Step 4.
4. Change the location of the transmission equipment port or replace the repeater.
Yes→End.
2.1.231 198098111 Fan failure

Alarm Information
l Name: Fan failure
Alarm Description
This alarm occurs when the fan is faulty.
Alarm Cause
1. The fan or air inlet is blocked.
2. The fan is faulty.
Impact
2-410

Chapter 2 Alarm
The equipment temperature might be too high, causing the boards or the entire system
unable to operate properly. As a result, the service performance will decrease and the
services will even be interrupted.
Action
1. Clean the fan blade and ensure that the air inlet is not blocked.
Yes→End.
No→Step 2.
2. Replace the fan in accordance with the shelf, rack information in the Detail Information
dialog box.
acement.
Yes→End.
2.1.232 198098251 The working mode of the Ethernet port doesn't

match the peer end
Alarm Information
l Name: The working mode of the Ethernet port doesn't match the peer end
Alarm Description
This alarm occurs when the Ethernet port at the local end works in different mode from
that at the peer end.
Alarm Cause
The working mode configured on the peer end Ethernet port is inconsistent with that of the
local end.
Impact
None.
Data may get lost during transmission through the Ethernet port. All or some of the services
on this board may be blocked, or quality of the services is affected.
2-411

Action
1. Check whether the operation mode of the Ethernet port is the same as planned.
a. Select Configuration Management -> Managed Element→Transmission
Network→UMTS→Physical Hosting -> Physical Layer Port, and check whether
the operation mode of the Ethernet port is the same as planned.
No→Substep b.
b. Modify the operation mode to that as planned.
Yes→End.
No→Step 2.
2. Ask the maintenance personnel of the peer end to modify the operation mode to that
as planned.
Yes→End.
2.1.233 198098314 Inter-board data link abnormal.

Alarm Information
l Name: Inter-board data link abnormal.
Alarm Description
This alarm occurs when loss of frame (LOS) is detected in the data link.
Alarm Cause
The inter-board link is broken.
Impact
None.
TDM link cannot operate properly. All the services on this board are blocked.
2-412

Chapter 2 Alarm
SRIO link exception: The configured coordination service is interrupted. Services on this
board may be blocked partially and service quality may be affected.
Action
1. Check whether the board in the other slot has any related alarm.
a. Check whether alarms exist on the board in accordance with the board slot
information in the additional alarm information in alarm details. If an alarm exists,
remove it based on the corresponding handling suggestion. The related alarms
are as follows:
198092348 The board is being initialized
198097060 Board communication link interrupted
198092057 The board is powered off
198092029 Hardware type is different from the configuration
198097004 Board hardware fault

Yes→End.
No→Step 2.
details.
After 15 minutes, check whether the alarm is cleared. Refer to Reset Boards.
Yes→End.
No→ Step 3.
Slot Number in the detailed alarm information.

Yes -> End.
2.1.234 198098315 Input clock of the board abnormal.

Alarm Information
l Name: Input clock of the board abnormal.
2-413

Alarm Description
This alarm occurs when the board input clock is deviated.
Alarm Cause
1. The inter-board clock link is wrongly connected.
2. The clock receiving module on the board is abnormal.
Impact
None.
Some or all of the services on this board may be blocked.
Action
Input reference clock/Input synchronization clock:
a. Check whether any clock-related alarm exists. If an alarm exists, remove it based
Yes→End.
No→Step 2.
Yes→End.
No→Step 3.
Slot Number in the detailed alarm information.
Yes→End.
Peer-end board input clock/Peer-end board input data:
1. Reset the board (the main control board in the other slot) based on the Rack Number,
Shelf Number and Slot Number in alarm details. Refer to Reset Boards.
2-414

Chapter 2 Alarm

Yes→ End.
No→Step 3.
ment.
Yes→End.
2.1.235 198098318 Unavailable optical module

Alarm Information
l Name: Unavailable optical module
1. If the optical module is not in position, this alarm is reported.
2. If the optical module is faulty, this alarm is reported.
Alarm Cause
1. No optical/electrical module is inserted into the optical port.
2. The optical/electrical module is not inserted properly.
3. The optical/electrical module is in bad contact with the board due to pollution.
4. The optical/electrical module is damaged.
5. The port of the optical/electrical module is damaged.
Impact
None.
Action
Perform the following operations according to the additional alarm information in the alarm
details:
2-415

The optical module is not in position:

1. Check whether the optical or electrical module is installed.
a. Based on the information about rack No., frame No., slot No., and optical port No.
in alarm details, check whether the optical or electrical module is installed in the
corresponding port.
Yes→Step 2.
No→Substep b.
b. Install an optical or electrical module.
Waiting for 15 minutes, and then check whether the alarm disappears.
Yes→End.
No→Step 2.
2. Based on the information about rack No., frame No., slot No., and optical port No. in
alarm details, remove the optical or electrical module, and then install it again.
Yes→End.
No→Step 3.
alarm details, replace the optical or electrical module.
Yes→End.
No→Step 4.
4. Select Dynamic Management→Dynamic Command→SDR→Device Group. Based
on the information about rack No., frame No., and slot No. in alarm details, perform
power-off reset on the board.
Yes→End.
The optical module is faulty:
Yes→End.
No→Step 2.
2-416

Chapter 2 Alarm
Yes→End.
No→Step 3.
3. Select Dynamic Management→Dynamic Command→SDR→Device Group. Based
on the information about rack No., frame No., and slot No. in alarm details, perform
power-off reset on the board.
Yes→End.
2.1.236 198098440 Disable PA

Alarm Information
l Name: Disable PA
Alarm Description
This alarm is given when it detects that PA is in the closed status.
Alarm Cause
1. The PA is disabled manually.
2. The PA is closed when the Remote antenna over VSWR alarm is reported.
3. The PA is disabled due to an internal fault.
Impact
None.
The service supported by the channel is interrupted.
Action
1. Verify that related alarms are not raised.
a. Check whether related alarms are raised. If they are raised, Handle the alarms in
accordance with the corresponding handling suggestions. Related alarms are as
follows:
198098465 VSWR of the antenna feeder abnormal
198098466 Temperature abnormal
2-417

198098467 Internal fault

Yes→End.
No→Step 2.
2. Select Dynamic Management -> Dynamic Command→SDR→Device Group→RRU to
enable the PA of the corresponding channel
Yes→End.
No→Step 3.
Yes→End.
2.1.237 198098465 VSWR of the antenna feeder abnormal

Alarm Information
l Name: VSWR of the antenna feeder abnormal
Alarm Description
This alarm occurs when the VSWR of the antenna feeder exceeds the threshold.
Alarm Cause
1. The antenna feeder cable is wrongly connected.
2. There is a same-frequency interference signal.
3. The RRU is faulty.
Impact
None.
2-418

Chapter 2 Alarm
When the standing wave ratio level is set to critical, all the services on this channel are
interrupted.
When the standing wave ratio level is set to minor, there is no impact on the services on
this channel.
Action
1. Verify that the threshold of the standing wave ratio is properly configured.
a. Select Configuration Management -> Managed
Element→Device→RRU→Environment Monitoring Device, and check
whether the upper limit and the lower limit of the standing wave ratio
threshold are properly configured according to the rack number/shelf
number/slot number in the alarm details.
Yes→Step 2.
No→Substep b.
b. Configure the threshold of the standing wave ratio to higher values as needed.
Yes→End.
No→ Step 2.
2. Verify that the cables of the antenna and feeder equipment are correctly connected.
a. Check whether the cables of the antenna and feeder are correctly connected to
the RRU.
Yes→Step 3.
No→Substep b.
b. Connect the cables of the antenna and feeder to the RRU correctly.
Yes→End.
No→Step 3.
3. Verify that the cables are properly connected.
a. Check whether the cables are properly connected (For example, the connectors
are not secured).
Yes→Step 4.
No→Substep b.
b. Troubleshoot the circuit faults.
Yes→End.
2-419

No→Step 4.
4. Verify that the RRU is faulty or the antenna and feeder system is faulty by using
crosscheck.
a. Connect the antenna and feeder system of a normal RRU to the RRU where the
alarm is located. Wait for 15 minutes, and check whether the alarm is cleared.
Yes→Step 5.
No→Substep b.
b. Replace the board according to the rack number/shelf number/slot number in the
alarm details. Refer to Components Replacement.
Yes→End.
5. Check the standing wave ratios of the antenna, the combiner and the feeder in
sequence, locate the faulty components, and replace or repair them.
Yes→End.
2.1.238 198098466 Temperature abnormal

Alarm Information
l Name: Temperature abnormal
Alarm Description
This alarm occurs when the device temperature exceeds the threshold.
Alarm Cause
1. The environment temperature is too high.
2. Ventilation fault.
3. Device fault.
Impact
2-420

Chapter 2 Alarm

All services operating on the board are interrupted.
Action
1. Improve the ventilation conditions of the equipment room (for example, repair the air
conditioner or fan, or ensure that the passage is not blocked).
Yes→End.
No→Step 2.
Yes→End.
2.1.239 198098467 Internal fault

Alarm Information
l Name: Internal fault
Alarm Description
This alarm occurs when a fault occurs during device running process.
Alarm Cause
Software is abnormal, or the internal hardware of the device is abnormal.
Impact
None.
The bearer service performance is degraded or services are interrupted.
Action
2-421


Yes→End.
No→Step 2.
2. In the diagnostic test, check whether the board hardware detection function is available
in the toolbar.
Yes→Step 3.
3. Perform the board hardware detection operation, and take action in accordance with
the test result.
Yes→End.
2.1.240 198098468 External extended device fault

Alarm Information
l Name: External extended device fault
Alarm Description
This alarm occurs when the external extended device has wrong configuration parameter
or it works improperly.
Alarm Cause
1. The external extended device is faulty.
2. The external extended device is configured with incorrect parameters.
3. The external extended device has a faulty connection.
Impact
None.
Some of the services on this board may be interrupted or the service quality may be
affected.
2-422

Chapter 2 Alarm
Action
details:
l Other hardware errors, other software errors, RAM error, UART error, TMA critical
alarm level, TMA minor alarm level, hardware fault, software fault, EEPROM error,
FLASH erase error, FLASH error, or external LNA fault:
1. Select Dynamic Management→Dynamic Command→SDR→AISG Device, and
reset the AISG device according to the antenna number/rack number/device type
in the additional alarm information in the alarm details.
Yes→End.
No→Step 2.
2. Replace the device according to the antenna number/rack number/device type
in the additional alarm information in the alarm details. Refer to Components
Replacement.
Yes→End.
l Communication link disconnected, or the link between the RRU and the external LNA
disconnected:
a. Check whether the communication cable between the external extended device
and the base station system is connected properly.
Yes→Step 2.
No→Substep b.
b. Re-connect the cable.
Yes→End.
No→Step 2.
2. Reset the board according to the rack number/shelf number/slot number in the
Yes→End.
No→Step 3.
Replacement.
2-423


Yes→End.
l Device address conflict:
Scan and add a new device in the AISG device management.
Yes→End.
l Failure in gain configuration:
1. Re-configure the uplink gain of the device.
a. Select Configuration Management→Managed Element→Device→BTS
Auxiliary Peripheral Device→Antenna Service→TMS Device, and configure
the uplink gain to the value within the scope of gains supported by the device.

Yes→End.
No→Step 2.
2. Select Dynamic Management -> Dynamic Command→SDR→AISG Device, and
reset the AISG device according to the antenna number/rack number/device type
in the additional alarm information in the alarm details.

Yes→End.
l Electrical machine faults, or the electrical machine unable to be adjusted:
perform RET calibration according to the antenna number/rack number/device
type in the additional alarm information in the alarm details.
Yes→End.
No→Step 2.
2. Re-install the electrical machine, and re-perform RET calibration.

Yes→End.
No→Step 3.
2-424

Chapter 2 Alarm

Replacement.
Yes→End.
l Failure in data storage, no configuration data, no response from the electrical machine
to the adjustment command, unable to perform calibration, or incorrect location value
responded by the electrical machine:
perform configuration data transmission and then RET calibration according to
the antenna number/rack number/device type in the additional alarm information
Yes→End.
No→Step 2.
2. Re-install the electrical machine, and re-perform RET calibration.
Yes→End.
No→Step 3.
Replacement.
Yes→End.
l Working in bypass mode:
configure the tower mounted amplifier to the normal mode according to the
antenna number/rack number/device type in the additional alarm information in
the alarm details.
Yes→End.
No→Step 2.
2. Reset the device according to the antenna number/rack number/device type in
the additional alarm information in the alarm details. Refer to Reset Boards.
2-425

Yes→End.
l Abnormal current on the NSBT port, or the overcurrent switch of the AISG
interface/NSBT port disconnected:
1. Verify the alarm threshold of the current is properly configured:
a. Select Configuration Management→Managed
Element→Device→RRU→PowerOutlet Set-> PowerOutlet, and check
whether the undercurrent/overcurrent alarm threshold percentages are
configured as planned.
Yes→Step 2.
No→Substep b.
b. Modify the alarm threshold percentages as planned.

Yes→End.
No→Step 2.
2. Verify that the cables of the antenna and feeder system are properly connected.
a. Check whether the cables of the antenna and feeder system are properly
connected (For example, the connectors are not secured, or there are short
circuits).
Yes→Step 3.
No→Substep b.
b. Re-connect the cables.
Yes→End.
No→Step 3.
Replacement.

Yes→End.

l The inconsistency of the RET antenna type, or the inconsistency of the external LNA
type:
1. Verify that the type of the external extended device is set to be the same as that
of the actual device.
2-426

Chapter 2 Alarm
a. Select Configuration Management→Managed

Element→Device→RRU→AISG Device, and check whether the type of the
device is set to be the same as that of the actual device according to
the antenna number/rack number/device type in the additional
alarm information in the alarm details.
Yes→Step 2.
No→Substep b.
b. Modify the device type to be the same as that of the actual device.
Yes→End.
No→Step 2.
Replacement.
Yes→End.
2.1.241 198098469 Abnormal RX channel

Alarm Information
l Name: Abnormal RX channel
Alarm Description
This alarm occurs when it is detected that a Rx channel is abnormal.
Alarm Cause
1. External interference may exist.
2. Spurious signals of the transmitting channel are on the receiving channel.
3. The passive intermodulation signals of the antenna and feeder system are relatively
large and are on the receiving channel.
Impact
2-427

None.
Some of the services on this board may be interrupted or the service quality may be
affected.
Action
details:
Low RSSI, high RSSI, or too great interference:
1. Perform RRU frequency scanning during the diagnosis testing, and check whether the
receiving signals are interfered by external interference sources.
Yes→Step 2.
2. Clear the external interference sources.
Yes→End.
Imbalanced main set/diversity receiving:
1. Verify that the switch of detecting the main set/diversity balance is configured correctly:
a. Select Configuration Management→Managed Element→Device→RF Device
Set→RF Port object→Tx Device, and check whether the main set/diversity
balance detection is configured as planned according to the rack number/shelf
Yes→Step 2.
No→Substep b.
b. Modify the main set/diversity balance detection as planned.
Yes→End.
No→ Step 2.
2. Verify that the cables of the antenna and feeder equipment are correctly connected.
the RRU.
Yes→Step 3.
No→Substep b.
b. Connect the cables of the antenna and feeder to the RRU correctly.
2-428

Chapter 2 Alarm

Yes→End.
No→Step 3.
3. Verify that the receiving signals are not interfered by external interference sources.
a. Perform RRU frequency scanning during the diagnosis testing, and check whether
the receiving signals are interfered by external interference sources.
Yes→Substep b.
b. Clear the external interference sources.
Yes→End.
2.1.242 198098470 Blocked resources manually

Alarm Information
l Name: Blocked resources manually
Alarm Description
This alarm occurs when resources are blocked manually.
Alarm Cause
The resources are blocked manually.
Impact
None.
The blocked resources cannot process services.
Action
Perform the following operations in accordance with the information in the Remark field of
the Detail Information dialog box:
l Enable the PA:
2-429

Select Dynamic Management→Dynamic Command→SDR→Device Group→RRU.

The corresponding tab is displayed. Enable the PA.
Yes→End.
l Block the board:
Select Dynamic Management -> Dynamic Command→SDR→Device Group. The
Device Group tab is displayed. Unblock the board.
Yes→End.
2.1.243 198098471 Carrier downlink data problem

Alarm Information
l Name: Carrier downlink data problem
This alarm is reported when the downlink IQ channel of the RRU receives incorrect data.
Alarm Cause
1. The downlink IQ channel receives incorrect data.
2. An optical fiber is disconnected.
Impact
None.
The supported services are degraded or may be interrupted.
Action
a. Check whether related alarms are raised. If they are raised, Handle the alarms in
follows:
2-430

Chapter 2 Alarm
Optical port receiving link failure (198098319)

The received optical power of the optical module is abnormal (198092431)
Yes→End.
No→Step 2.
Yes→End.
2.1.244 198098472 RRU Power Abnormal Alarm

Alarm Information
l Name: RRU Power Abnormal Alarm
Alarm Description
This alarm occurs when the detected RRU power is abnormal.
Alarm Cause
1. The hardware of the RRU channel is faulty.
2. The RRU software version is incorrect.
3. The optical fiber link is faulty.
4. The BBU hardware is abnormal or the BBU software version is incorrect.
Impact
None.
The performance of the services on this channel is decreased.
Action
1. Reset the board according to the rack number/shelf number/slot number in the alarm
2-431


Yes→End.
No→Step 2.
2. Power off and reset the board according to the rack number/shelf number/slot number
Yes→End.
No→Step 3.
3. Reset the baseband board or the optical interface board that is connected with the
RRU where the alarm is located. Refer to Reset Boards.
a. Select Configuration Management→Managed Element→Device, and double-click
Device. The Physical View and Topology View are displayed. Check the
rack, shelf and slot of the baseband board or the optical interface board that
is connected with the RRU where the alarm is located according to the rack
number/shelf number/slot number in the alarm details.
b. Reset the board according to the rack number/shelf number/slot number verified
in substep a.
Yes→End.
No→Step 4.
4. Select Dynamic Management→Dynamic Command→SDR→Managed Network
Element, and reset the NE.
Yes→End.
No→ Step 5.
5. Remove and re-install the optical fibers and optical modules on the corresponding
optical interfaces according to the rack number/shelf number/slot number in the alarm
details.
Yes→End.
No→Step 6.
6. Remove and install the optical fibers and optical modules on the corresponding optical
interfaces according to the rack number/shelf number/slot number of the baseband
board or the optical interface board verified in step 3.
Yes→End.
No→Step 7.
2-432

Chapter 2 Alarm
7. Replace the board according to the rack number/shelf number/slot number displayed
in the alarm details. Refer to Components Replacement.
Yes→End.

abnormal
Alarm Information
l Name: The baseband signal input to the TX channel is abnormal
This alarm occurs when the Baseband IQ data power from the base-band unit exceeds
the rated power or is lower than the minimum power.
Alarm Cause
The baseband IQ data power sent by the baseband unit to the RF unit exceeds the rated
power or is lower than the lower power threshold.
Impact
None.
If the frequency point of the RF unit fails to be set up, all or some of the services on this
channel may be interrupted, or the service quality may be affected.
Action
RRU where the alarm is located.

2-433

in substep a.
Yes→End.
No→Step 2.
2. Select Dynamic Management→Dynamic Command→SDR→Device Group, and reset
the main control board.
Yes→End.
2.1.246 198100280 The output power of the TX channel is abnormal

Alarm Information
l Name: The output power of the TX channel is abnormal
Alarm Description
This alarm occurs when the power on the radio unit transmission channel is too high or
too low.
Alarm Cause
1. Hardware is faulty (TxChannel is faulty or power detection channel is faulty).
2. Software is faulty.
3. The baseband power is abnormal.
Impact
None.
The TxChannel of the RF unit cannot operate properly, and all the services on this channel
are interrupted.
Action
1. Verify that the alarm is not raised frequently.
2-434

Chapter 2 Alarm
a. Select Alarm Monitoring→History Alarms, and check whether the alarm is raised
frequently.
Yes→Step 2.
No→Substep b.
b. Check whether the alarm lasts for less than 10 minutes.
Yes→Substep c.
No→Step 2.
Yes→End.
No →Step 2.
RRU where the alarm is located. Refer to Reset Boards.

in substep a. Refer to Reset Boards.

Yes→End.
No→Step 3.
3. Replace the board according to the rack number/shelf number/slot number in the alarm
details. Refer to Components Replacement.
Yes→End.
2.1.247 198100283 Smart antenna calibration is abnormal

Alarm Information
l Name: Smart antenna calibration is abnormal
2-435

Alarm Description
This alarm occurs when a smart antenna fails to be calibrated.
Alarm Cause
1. Antenna and feeder cable connection fault.
2. RRU channel fault.
Impact
None.
If the sending or receiving channel is faulty, the services carried by this channel are
blocked.
If the intelligent antenna cannot be calibrated properly, the performance of the antenna is
affected.
Action
1. Check the antenna feeder cable.
a. Check whether the antenna and feeder are connected correctly.
Yes→Step 2.
No→Substep b.
Yes→End.
No→Step 2.
2. Check whether connectors of the antenna and feeder are secured.
a. Check whether connectors of the antenna and feeder are secured.
Yes→Step 2.
No→Substep b.
b. Secure the connectors.
Yes→End.
No→Step 3.
2-436

Chapter 2 Alarm
Yes→End.
2.1.248 198094400 Downlink digital power exceeds threshold

Alarm Information
l Name: Downlink digital power exceeds threshold
This alarm is raised when the digital power sent by the BBU to the RRU exceeds the rated
power 1 dB.
Alarm Cause
The optical link error rate between the BBU and the RRU is too high, or transmission quality
is poor.
Impact
I. Board status:
Operates properly.
II. Impact on services:
The RRU RF output signal is deteriorated. Service traffic is decreased or interrupted.
Action
CPRI link abnormal (198094416)
Yes→Step 4.
No→Step 2.
2. Select Configuration Management→Device→BTS Auxiliary Peripheral
Device→Cable→Fiber Cable, check the rack, shelf, and slot information of the BPL
connected to the RRU.
3. In Dynamic Management→SDR→Device Group→Board Reset, select the BPL
recorded in step 2 and reset it.
2-437

Yes→Step 4.
No→Contact ZTE technical support.
4. In Dynamic Management→SDR→Device Group→RRU→Enable PA, according to the
rack ID, shelf ID, slot ID, and channel ID in detailed alarm information, enable the PA
that is shut down due to power exceeding the threshold. End alarm handling.
2.1.249 198094401 Downlink analog power exceeds threshold

Alarm Information
l Name: Downlink analog power exceeds threshold
This alarm is raised when the RRU finds that the transmit power of an antenna interface
exceeds the threshold.
Alarm Cause
1. The downlink digital power exceeds the rated power.
2. A fault occurs on the downlink transmission path.
Impact
I. Board status:
The RRU may shut down the PA or the PA may be damaged.
All the services that the RRU bears may be interrupted.
Action
Downlink digital power exceeds threshold (198094400)
Yes→End.
No→Step 2.
2. According to the rack ID, shelf ID and slot ID in detailed alarm information, determine
the RRU location.
2-438

Chapter 2 Alarm
3. In Dynamic Management→SDR→Device Group→Board Reset, reset the alarmed

RRU.
Yes→End.
2.1.250 198094402 The difference of digital and analog power is

abnormal
Alarm Information
l Name: The difference of digital and analog power is abnormal
The difference between the analog power sent by the RRU and the digital power sent by
the BBU exceeds the threshold.
Alarm Cause
1. The PA is shut down.
2. The PA is abnormal.
3. The transceiving board is faulty.
Impact
I. Board status:
Operates properly.
Transmit power of the RRU is inaccurate, which affects the coverage area of the cell. If
the transmit power is too high, the coverage area of the cell is increased. If the transmit
power is too low, the coverage area of the cell is decreased.
Action
Downlink analog power exceeds threshold (198094401)
Antenna feeder VSWR serious alarm (198094404)
2-439


Yes→End.
No→Step 2.
2. According to the rack ID, shelf ID and slot ID in detailed alarm information, determine
the RRU location. According to information in the additional text, determine the ID of
the alarmed channel.
3. In Diagnosis Test→Combined Test, select the alarmed RRU and query the PA
attributes of the RRU. View the result of checking the PAX status switch to check
whether the PA is shut down.
Yes→Step 4.
No→Step 5.
that is shut down. After 5 minutes, check whether this alarm is cleared.
Yes→End.
No→Step 5.
RRU.
Yes→End.
2.1.251 198094403 Antenna feeder VSWR alarm

Alarm Information
l Name: Antenna feeder VSWR alarm
The antenna feeder SWR is equal to or greater than 2.0 and smaller than 3.0 (the SWR
threshold is set in configuration management).
Alarm Cause
1. The antenna feeder is not connected fast to the RRU RF cable.
2. The impedance of the antenna feeder does not match that of the RRU.
3. The antenna feeder is faulty.
2-440

Chapter 2 Alarm
4. RF cables inside the RRU are not connected fast.

Impact
I. Board status:
Operates properly.
The RRU RF output quality is deteriorated. The performance of downlinks is affected. The
coverage area of the cell may be decreased.
Action
1. Verify that the SWR threshold is properly configured.
a. In Configuration Management→Managed
Element→Device→RRU→Environment Monitoring Device, based on the rack
ID, shelf ID, and slot ID in detailed alarm information, check whether the lower
limit of the SWR threshold is properly configured.
Yes→Step 2.
No→Substep b.
b. Increase the SWR threshold according to actual needs.
d. After 15 minutes, check whether this alarm is cleared.
Yes→End.
No→Step 2.
2. Check whether cables in the antenna feeder system are connected correctly.
the RRU.
Yes→Step 3.
No→Substep b.
b. Correctly connect the cables of the antenna and feeder to the RRU.
Yes→End.
No→Step 4.
3. Check whether the cables are properly connected.
are not in good contact).
Yes→Step 4.
2-441

No→Substep b.
b. Eliminate line faults.
Yes→End.
No→Step 5.
4. Verify that the RRU is faulty or the antenna feeder system is faulty by using crosscheck.
a. Connect the antenna feeder system of a normal RRU to the RRU where the alarm
is located. Wait for 15 minutes, and check whether the alarm is cleared.
Yes→End.
No→Substep b.
b. Replace the RRU board.
Yes→End.
5. Check the SWRs of the antenna, the combiner and the feeder in sequence, locate the
faulty components, and replace or repair them.
Yes→End.
2.1.252 198094404 Antenna feeder VSWR serious alarm

Alarm Information
l Name: Antenna feeder VSWR serious alarm
The antenna feeder SWR is equal to or greater than 3.0 (the SWR threshold is set in
configuration management).
Alarm Cause
1. The antenna feeder is not connected fast to the RRU RF cable.
2. The impedance of the antenna feeder does not match that of the RRU.
3. The antenna feeder is faulty.
4. RF cables inside the RRU are not connected fast.
2-442

Chapter 2 Alarm
Impact
I. Board status:
The PA is shut down.
Action
1. Verify that the SWR threshold is properly configured.
a. In Configuration Management→Managed
Element→Device→RRU→Environment Monitoring Device, based on the rack
ID, shelf ID, and slot ID in detailed alarm information, check whether the lower
limit of the SWR threshold is properly configured.
Yes→Step 2.
No→Substep b.
b. Increase the SWR threshold according to actual needs.
d. In Dynamic Management→SDR→Device Group→RRU→Enable PA, according to
the rack ID, shelf ID, slot ID, and antenna feeder ID in detailed alarm information,
enable the PA that is shut down due to SWR exceeding the threshold.
Yes→End.
No→Step 2.
2. Check whether cables in the antenna feeder system are connected correctly.
the RRU.
Yes→Step 3.
No→Substep b.
b. Correctly connect the cables of the antenna and feeder to the RRU.
c. In Dynamic Management→SDR→Device Group→RRU→Enable PA, according to
Yes→End.
No→Step 3.
3. Check whether the cables are properly connected.
2-443

are not in good contact).
Yes→Step 4.
No→Substep b.
b. Eliminate line faults.
c. In Dynamic Management→SDR→Device Group→RRU→Enable PA, according to
Yes→End.
No→Step 4.
4. Verify that the RRU is faulty or the antenna feeder system is faulty by using crosscheck.
a. Connect the antenna feeder system of a normal RRU to the alarmed RRU.
b. In Dynamic Management→SDR→Device Group→RRU→Enable PA, according to
Yes→End.
No→Substep c.
c. Replace the RRU board.
Yes→End.
5. Check the SWRs of the antenna, the combiner and the feeder in sequence, locate the
faulty components, and replace or repair them.
rack ID, shelf ID, slot ID, and antenna feeder ID in detailed alarm information, enable
the PA that is shut down due to SWR exceeding the threshold.
Yes→End.
2.1.253 198094405 Slight-high temperature of PA

Alarm Information
l Name: Slight-high temperature of PA
2-444

Chapter 2 Alarm

This alarm is raised when the PA temperature is equal to or higher than 85 ℃ and lower
than 100 ℃.
Alarm Cause
1. The PA is operating under high loads for a long time.
3. Power supply of the RRU is abnormal.
4. The PA is faulty.
Impact
I. Board status:
Operates properly.
The coverage area of the cell is decreased.
Action
1. Wait for 30 minutes, and check whether the alarm is cleared automatically.
Yes→End.
No→Step 2.
2. Improve the ventilation in the equipment room (for example, troubleshooting air
conditioner faults, fan faults, channel congestion faults).
After the environment is improved, wait for 15 minutes and check whether the alarm
is cleared.
Yes→End.
No→Step 3.
RRU power supply abnormal (198094407)
Yes→End.
2-445

No→Step 4.
4. According to the rack ID, shelf ID and slot ID in detailed alarm information, replace the
board.
Yes→End.
2.1.254 198094406 Over-high temperature of PA

Alarm Information
l Name: Over-high temperature of PA
This alarm is raised when the PA temperature is equal to or higher than 100 ℃. This alarm
is cleared when the PA temperature is lower than 95 ℃.
Alarm Cause
1. The PA is operating under high loads for a long time.
3. Power supply of the RRU is abnormal.
4. The PA is faulty.
Impact
I. Board status:
Action
Yes→Step 4.
No→Step 2.
2-446

Chapter 2 Alarm
is cleared.
Yes→Step 4.
No→Step 3.
RRU power supply abnormal (198094407)
Yes→Step 4.
No→Step 5.
that is shut down due to power exceeding the threshold. End alarm handling.
board.
Yes→End.
2.1.255 198094407 RRU power supply abnormal

Alarm Information
l Name: RRU power supply abnormal
The input or output of the power module on the RRU is over voltage or under voltage.
Alarm Cause
1. The external input voltage is too high or too low.
2. The power module is faulty.
2-447

Impact
I. Board status:
The RRU may not operate properly or the RRU is damaged.
Services that the RRU bears may be interrupted.
Action
1. Check whether the input voltage of the external power supply is normal by using a
multimeter.
Yes→Step 3.
No→Step 2.
2. Replace the power supply. Wait for 30 minutes, and check whether the alarm is
cleared.
Yes→End.
No→Step 3.
RRU. .
Yes→End.
2.1.256 198094408 RRU RF PLL unlock

Alarm Information
l Name: RRU RF PLL unlock
The RF PPL of the RRU cannot lock the reference clock.
Alarm Cause
1. Frequency points are configured incorrectly.
2. The hardware is faulty.
Impact
I. Board status:
2-448

Chapter 2 Alarm
The RRU may shut down the PA.

Action
1. Check the frequency point configuration.
a. In Configuration Management→Radio Parameter→LTE FDD→E-UTRAN CELL,
check whether the frequency configuration of the cell configured on the RRU is
correct.
Yes→Step 2.
No→Substep b.
b. Modify the frequency point to a value within the frequency range, and synchronize
the change configuration. After 10 minutes, check whether this alarm is cleared.
Yes→End.
No→Step 2.
2. In Dynamic Management→SDR→Device Group→Board reset, according to the rack
ID, shelf ID, and slot ID in detailed alarm information, reset the alarmed RRU.
Yes→End.
2.1.257 198094409 Abnormal temperature of board

Alarm Information
l Name: Abnormal temperature of board
The board temperature is higher than 75 ℃ or lower than -15 ℃.
Alarm Cause
1. The environmental temperature exceeds the normal working temperature range of the
equipment.
Impact
I. Board status:
2-449

The RRU automatically decreases the power by 1 dB, which may cause the RRU to operate
improperly or be damaged..
The coverage area of the cell may be decreased. If the RRU is damaged, cells borne over
it cannot provide services.
Action
Yes→End.
No→Step 2.
is cleared.
Yes→End.
2.1.258 198094412 Fault in BPL clock

Alarm Information
l Name: Fault in BPL clock
The BPL has no clock, its clock signal is abnormal, or its clock is out of lock.
Alarm Cause
1. The clock of the main-control board is faulty.
2. The output clock of the backplane is faulty.
3. The hardware of the clock module on the alarmed device is faulty.
Impact
I. Board status:
The board is unavailable.
The cell using this BPL cannot provide services.
2-450

Chapter 2 Alarm
Action
a. Check whether any clock-related alarm exists. If such alarms exist, remove them
based on the corresponding handling suggestion. The related alarms are as
follows:
Yes→End.
No→Step 2.
2. According to the rack ID, shelf ID, and slot ID in detailed alarm information, reset the
board.
Yes→End.
No→Step 3.
3. According to the rack ID, shelf ID, and slot ID in detailed alarm information, remove
the board and reinstall it.
Yes→End.
2.1.259 198094413 Fault in BPL hardware

Alarm Information
l Name: Fault in BPL hardware
An error occurs on a component or communication link on the board.
Alarm Cause
The hardware is faulty.
Impact
I. Board status:
The board is unavailable.
2-451


The cell using this BPL cannot provide services.
Action
1. According to the rack ID, shelf ID, and slot ID in detailed alarm information, reset the
board.
Yes→End.
No→Step 2.
2. According to the rack ID, shelf ID, and slot ID in detailed alarm information remove the
board and reinstall it.
Yes→End.
No→Step 3.
board.
Yes→End.
2.1.260 198094414 Discontinuous frame number

Alarm Information
l Name: Discontinuous frame number
Frame numbers received by the BPL or the RRU are not continuous.
Alarm Cause
BPL:
1. The main-control board switches over its clock reference source.
2. The clock-locking status of the main-control board is changed from unlocked into locked.
3. The crystal oscillator of the main-control board is aged.
RRU:
2-452

Chapter 2 Alarm
1. The link from the BBU to the RRU is faulty.
Impact
I. Board status:
Operates properly.
All downlink UEs in the cell are asynchronous, and services are interrupted.
Action
Yes→End.
No→Step 2.
2. According to the rack ID, shelf ID, and slot ID in detailed alarm information, check
whether the alarmed board is a BPL board.
Yes→Step 4.
No→Step 3.
whether the alarmed board is an RRU.
Yes→Step 6.
a. Check whether any related alarm exists on the main-control board. If such alarms
exist, remove them based on the corresponding handling suggestion. The related
alarm is as follows:
Yes→End.
No→Step 5.
board.
Yes→End.
2-453


Yes→End.
No→Step 7.
RRU.
Yes→End.
2.1.261 198094415 Frame frequency abnormal

Alarm Information
l Name: Frame frequency abnormal
The frame frequency received by the BPL or the RRU is abnormal.
Alarm Cause
BPL:
1. The main-control board switches over its clock reference source.
2. The clock-locking status of the main-control board is changed from unlocked into locked.
3. The crystal oscillator of the main-control board is aged.
RRU:
1. The link from the BBU to the RRU is faulty.
Impact
I. Board status:
Operates properly.
All downlink UEs in the cell are asynchronous, and services are interrupted.
Action
2-454

Chapter 2 Alarm
Yes→End.
No→Step 2.
whether the alarmed board is a BPL board.
Yes→Step 4.
No→Step 3.
whether the alarmed board is an RRU.
Yes→Step 6.
a. Check whether any related alarm exists on the main-control board. If such alarms
exist, remove them based on the corresponding handling suggestion. The related
Yes→End.
No→Step 5.
board.
Yes→End.
Yes→End.
No→Step 7.
RRU.
Yes→End.
2-455

2.1.262 198094425 Optical module temperature is abnormal

Alarm Information
l Name: Optical module temperature is abnormal
The temperature of the optical module is too high or too low.
Alarm Cause
The optical module is abnormal.
Impact
I. Board status:
Operates properly.
Optical fiber connection between the BBU and the RRU is abnormal. Services may be
interrupted.
Action
1. According to the rack ID, shelf ID, slot ID, and optical port ID in detailed alarm
information, replace the optical module.
Yes→End.
No→Step 2.
2. In Dynamic Management→Dynamic Command→SDR→Device Group, according to
the rack ID, shelf ID, and slot ID in detailed alarm information, power off the board and
reset it.
Yes→End.
2.1.263 198094426 Optical module bias current is abnormal

Alarm Information
2-456

Chapter 2 Alarm
l Name: Optical module bias current is abnormal

The bias current of the optical module is too low or too high.
Alarm Cause
Impact
I. Board status:
Operates properly.
interrupted.
Action
Yes→End.
No→Step 2.
reset it.
Yes→End.
2.1.264 198094427 Optical module transmit power is abnormal

Alarm Information
l Name: Optical module transmit power is abnormal
2-457

The transmit power of the optical module is too low or too high.
Alarm Cause
Impact
I. Board status:
Operates properly.
interrupted.
Action
information, remove the optical module and reinstall it.
Yes→End.
No→Step 2.
Yes→End.
No→Step 3.
reset it.
Yes→End.
2.1.265 198094428 Optical module inner voltage is abnormal

Alarm Information
l Name: Optical module inner voltage is abnormal
2-458

Chapter 2 Alarm
The internal voltage of the optical module is too low or too high.
Alarm Cause
Impact
I. Board status:
Operates properly.

interrupted.
Action
Yes→End.
No→Step 2.
reset it.
Yes→End.
2.1.266 198094431 RSSI power is abnormal

Alarm Information
l Name: RSSI power is abnormal
The power of the RSSI is too low or too high.
2-459

Alarm Cause
1. The uplink path of the RRU is faulty, which causes the power to be too low.
2. Great interferences exist in the environment, which causes the power to be too high.
Impact
I. Board status:
Operates properly.
Services may be interrupted, or uplink traffic decreases.
Action
Contact ZTE technical support.
2.1.267 198094437 RRU power-cut alarm

Alarm Information
l Name: RRU power-cut alarm
This alarm occurs when an RRU detects that its voltage is lower than the threshold.
Alarm Cause
Power supply of the RRU is faulty.
Impact
I. Board status:
RRU equipment fails to operate properly.
There is no service available in the cell configured on the RRU.
Action
1. Check whether the power supply equipment of the RRU operates properly.
Yes→Step 4.
No→Step 2.
2. Provide the RRU with proper power supply equipment.
2-460

Chapter 2 Alarm
3. Check whether the RRU is powered on and whether the alarm is cleared.
Yes→End.
No→Contact technical support.
4. Power the RRU and whether the alarm is cleared.
Yes→End.
2.1.268 198094441 RRU feedback power exceeds threshold

Alarm Information
l Name: RRU feedback power exceeds threshold
This alarm occurs when RRU power is interfered by other RRU in condition that two RRUs
are configured with poor quality combiner.
Alarm Cause
Power interference between RRUs occurs if two RRUs are configured with poor quality
combiners.
Impact
I. Board status:
Action
1. Check whether the isolation of the combiner is proper.
Yes→Step 3.
No→Step 2.
2. Replace the combiner with a new one.
3. Enable the PA by selecting Dynamic Management→SDR→Device Group→RRU→PA
On and check whether the alarm is cleared.
Yes→End.
No→Step 4.
2-461

4. Reset the RRU and check whether the alarm is cleared after the RRU operates
properly.
Yes→End.
2.2 Communication Alarm

2.2.1 198093027 IPTB local switch setup fails.
Alarm Information
l Name: IPTB local switch setup fails.
l Alarm type: Communication alarm
The local IPTB switch setup fails.
Alarm Cause
1. The IP configuration of the base station is incorrect in the OMCR system.
2. In the LocalSwitch parameter configuration for the base station, more than two IP
addresses are configured for the uplink port.
Impact
1. Board status:
2. Service impact:
The system fails to provide the local switch function.
Action
1. On the OMCR, check whether the SDR IP is equal to the Local IP of SCTP.
2. On the LMT/OMMB, check whether the uplink port of the "LocalSwitch" parameter has
only one IP address.
a. Select Managed NE > Radio Parameters > GSM > Local Switch.
b. Check the uplink direction, and view the destination IP address to see whether there is
only one IP address.
2-462

Chapter 2 Alarm
2.2.2 198093057 No optical signal is received at the optical port

Alarm Information
l Name: No optical signal is received at the optical port
This alarm is generated when the optical interface does not receive any optical signal.
Alarm Cause
1. The optical fiber/cable is damaged.
2. The optical/electrical module or the optical fiber/cable at the local end or the opposite
end is not connected properly.
3. The optical/electrical module at the local end or the opposite end is damaged.
4. The RRU is not connected.
5. The RRU operated improperly.
Impact
Action
1. Check whether relevant alarms exist at the local end.
1. Check whether relevant alarms exist at the local end. If yes, handle the alarms by
referring to the handling suggestions. The relevant alarm is:
The NE does not support the configured parameters (198097510)
2. Check whether the receiving power of the optical module is normal.
a. In the diagnosis test, test the board in accordance with the rack No., shelf No., and
slot No. in the alarm details. In accordance with the optical interface No. in the alarm
details, check the receiving power of the optical module. The receiving sensitivities of the
commonly used optical modules are as follows:
1.25 G (-19 dBm)
2.5 G (-17 dBm)
2-463

6 G (-15 dBm)）
10 G (-13 dBm)
b. Check whether the receiving power of the optical module is lower than the sensitivity.
If yes, go to substep c.
c. In the diagnosis test, test the board in accordance with the rack No., shelf No., and slot
No. in the alarm details. In accordance with the optical interface No. in the alarm details,
check the maximum distance supported by the optical module and check whether the fiber
length exceeds the maximum value.
If no, go to substep e.
d. Use a proper optical module or shorten the fiber distance.
e. Check whether the fiber is connected properly.
If yes, go to substep f.
If no, go to substep g.
f. Check whether the fiber connector is stained.
If yes, go to substep h.
If no, go to substep i.
g. Connect the fiber properly.
h. Clean the fiber connector.
i. Check whether the fiber is intact.
If no, go to substep l.
l. Replace the fiber.
2-464

Chapter 2 Alarm

5. Notify the maintenance personnel at the opposite end to check whether the equipment
is operating properly.
If yes, the maintenance personnel determines that the equipment fault at the opposite does
not exist.
2.2.3 198093058 Optical fiber connection error

Alarm Information
l Name: Optical fiber connection error
This alarm is generated when the optical fiber is connected improperly.
Alarm Cause
1. The optical fibers are crossly connected improperly.
2. The incorrect optical interface is used.
Impact
2-465

Action
1. Select Configuration Management->Managed Element->Equipment->Rack
Diagram->Topology View. In accordance with the rack No., shelf No., slot No., and optical
interface No. in the alarm details, check the connection relation of the optical interface.
2. Connect the fiber again in accordance with the connection relation.
2.2.4 198093059 The frames received at the optical port lose lock.
Alarm Information
l Name: The frames received at the optical port lose lock.
Frame synchronization error occurs on the optical CPRI communication or bit error ratio
is too high.
Alarm Cause
1. The ends of optical fiber/cable are polluted.
2. The optical fiber/cable link is operating improperly.
3. The device at the opposite end is operating improperly.
Impact
Action
1. Check whether relevant alarms exist at the local end.
1. Check whether relevant alarms exist at the local end. If yes, handle the alarms by
referring to the handling suggestions. The relevant alarm is:
2-466

Chapter 2 Alarm
2. Check whether the receiving power of the optical module is normal.

a. In the diagnosis test, test the board in accordance with the rack No., shelf No., and
slot No. in the alarm details. In accordance with the optical interface No. in the alarm
details, check the receiving power of the optical module. The receiving sensitivities of the
commonly used optical modules are as follows:
1.25 G （-19 dBm）
2.5 G （-17 dBm）
6 G （-15 dBm）
10 G （-13 dBm）
b. Check whether the receiving power of the optical module is lower than the sensitivity.
c. In the diagnosis test, test the board in accordance with the rack No., shelf No., and slot
d. Use a proper optical module or shorten the fiber distance.
e. Check whether the fiber is connected properly.
If yes, go to substep f.
If no, go to substep g.
f. Check whether the fiber connector is stained.
If yes, go to substep h.
g. Connect the fiber properly.
2-467

i. Check whether the fiber is intact.
If no, go to substep l.
l. Replace the fiber.

5. Notify the maintenance personnel at the opposite end to check whether the equipment
is operating properly.
If yes, the maintenance personnel determines that the equipment fault at the opposite does
not exist.
2.2.5 198096410 Heat exchanger's communication data lost alarm

Alarm Information
l Name: Heat exchanger's communication data lost alarm
l Alarm type: Communications Alarm
Alarm Description
This alarm is given if within 30 seconds, CC board cannot receive any information
periodically reported from heat exchanger.
2-468

Chapter 2 Alarm
Alarm Cause
l The heat exchanger is not powered on.
l The connection between the heat exchanger and the SA is improper.
l The heat exchanger is faulty.
Impact
None.
None.
Action
1. Verify that the heat exchanger is powered on.
a. Check whether the heat exchanger is powered on.
l Yes -> Step 2.
l No -> Substep b.
b. Power on the heat exchanger.
l Yes -> End.
l No -> Step 2.
2. Verify that the heat exchanger is correctly connected to the SA.
a. Check whether the heat exchanger is correctly connected to the SA (for example,
check whether the cable is connected, or the ends of the cable are secured).
l Yes -> Step 3.
l No -> Substep b.
l Yes -> End.
l No -> Step 3.
3. Replace the heat exchanger. Refer to Components Replacement.
l Yes -> End.
2.2.6 198092286 Loss of frames to be received at the optical port

Alarm Information
2-469

l Name: Loss of frames to be received at the optical port

Alarm Description
This alarm occurs when the Loss Of Frame (LOF) problem or error codes are detected at
the optical port.
Alarm Cause
l The ends of optical fiber/electrical cable are polluted.
l The optical fiber/electrical cable link is not operating properly.
l The device at the opposite end is not operating properly.
Impact
None.
Action
1. Ensure that the related alarm is cleared on the local end.
a. Check whether the related alarm is raised on the local end. If the related alarm is
raised, resolve it in accordance with the corresponding handling suggestion. The
related alarm is as follows:
198097510 The NE does not support the configured parameters
l Yes -> End.
l No -> Step 2.
2. Ensure that the receiving power of the optical module is proper.
a. Start a diagnostic test for the board in accordance with the slot, shelf, and rack
information in the Detail Information dialog box. View the receiving power of the
optical module in accordance with the optical port number in the Detail Information
dialog box. The receiving sensitivity of the common optical module is as follows:
1.25G (-19dBm)
2.5G (-17dBm)
6G (-15dBm)
10G (-13dBm)
b. Check whether the receiving power of the optical module is less than the sensitivity.
l Yes -> Substep c.
2-470

Chapter 2 Alarm
l No -> Step 3.
c. Start a diagnostic test for the board in accordance with the slot, shelf, and rack
information in the Detail Information dialog box. View the maximum distance that
the optical module supports in accordance with the optical port number in the Detail
Information dialog box, and check whether the fiber length exceeds the maximum
distance.
l Yes -> Substep d.
l No -> Substep e.
d. Replace the optical module with a proper one or shorten the fiber length.
l Yes -> End.
l No -> Substep e.
e. Check whether the fiber is properly connected.
l Yes -> Substep f.
l No -> Substep g.
f. Check whether the intersecting surface of the fiber connector is polluted.
l Yes -> Substep h.
l No -> Substep i.
g. Reconnect the fiber.
l Yes -> End.
l No -> Substep i.
l Yes -> End.
l No -> Substep i.
i. Check whether the fiber is in good condition.
l Yes -> Step 3.
l No -> Substep l.
j. Replace the fiber. Refer to Components Replacement.

l Yes -> End.
l No -> Step 3.
l Yes -> End.
l No -> Step 4.
2-471

and rack information in the Detail Information dialog box Refer to Components Repla
cement.
l Yes -> End.
l No -> Step 5.
5. Inform maintenance personnel of the peer device to check whether the peer device is
not operating properly.
l Yes -> Maintenance personnel of the peer device resolve the fault.
2.2.7 198092290 No optical signal is received at the optical port

Alarm Information
l Name: No optical signal is received at the optical port
Alarm Description
This alarm occurs when no optical signal is received at the optical port.
Alarm Cause
l The optical fiber/electrical cable is damaged.
l The optical/electrical module or the optical fiber/electrical cable at the local end or the
opposite end is not connected properly.
l The optical/electrical module at the local end or the opposite end is damaged.
Impact
None.
Action
1. Ensure that the related alarm is cleared on the local end.
a. Check whether the related alarm persists on the local end. If the related
alarm persists, handle the alarmin accordance with the corresponding handling
suggestion. The related alarm is as follows:
198097510 The NE does not support the configured parameters
2-472

Chapter 2 Alarm

l Yes -> End.
l No -> Step 2.
2. Ensure that the receiving power of the optical module is proper.
information in the Detail Information dialog box. Check the receiving power of the
optical module in accordance with optical port number in the Detail Information
dialog box. The receiving sensitivity of the common optical module is as follows:
1.25G (-19dBm)
2.5G (-17dBm)
6G (-15dBm)
10G (-13dBm)
b. Check whether the receiving power of the optical module is less than the sensitivity.
l Yes -> Substep c.
l No -> Step 3.
c. Start a diagnostic test for the board in accordance with the slot, shelf, and rack
Information dialog box. Check whether the fiber length exceeds the maximum
distance.
l Yes -> Substep d.
l No -> Substep e.
d. Replace the optical module with a proper one or shorten the fiber length. Refer to
Components Replacement.
l Yes -> End.
l No -> Substep e.
e. Check whether the fiber is properly connected.
l Yes -> Substep f
l No -> Substep g.
f. Check whether the intersecting surface of the fiber connector is polluted.
l Yes -> Substeph
l No -> Substep i.
g. Connect the fiber.
l Yes -> End.
l No -> Substep i.
2-473

l Yes -> End.

l No -> Substep i.
i. Check whether the fiber is in good condition.
l Yes -> Step 3.
l No -> Substep l.
j. Replace the fiber. Refer to Components Replacement.
l Yes -> End.
l No -> Step 3.
3. 3. Remove and re-install the optical/electrical module in accordance with the optical
port, slot, shelf, and rack information in the Detail Information dialog box.
l Yes -> End.
l No -> Step 4.
4. 4. Replace the optical/electrical module in accordance with the optical port, slot, shelf,
acement.
l Yes -> End.
l No -> Step 5.
5. 5. Inform maintenance personnel of the peer device to check whether the peer device
is not operating properly.
l Yes -> Maintenance personnel of the peer device troubleshoot the fault.
2.2.8 198092431 The received optical power of the optical module

is abnormal
Alarm Information
l Name: The received optical power of the optical module is abnormal
Alarm Description
This alarm occurs when the receiving optical power of the optical module is too low or too
high.
Alarm Cause
l The optical fiber is damaged.
2-474

Chapter 2 Alarm
l The optical module is aging.

l The actual optical fiber length is longer than the length supported by the optical mod-
ule.
Impact
None.
Action
1. Remove and re-install the fiber or optical module in accordance with the optical port,
l Yes -> End.
l No -> Step 2.
2. Check whether the fiber length exceeds the maximum distance that the optical module
supports.
distance that the optical module supports.
l Yes -> Substep b.
l No -> Step 3.
b. Check whether the fiber length can be shortened.
l Yes -> Substep c.
l No -> Substep d.
c. Shorten the fiber length.
l Yes -> End.
l No -> Step 3.
d. Replace the optical module with a proper one that can support the transmission
distance.
Wait 15 minutes, and check whether the alarm is cleared. Refer to Components
Replacement.
l Yes -> End.
l No -> Step 4.
3. Replace the optical module in accordance with the optical port, slot, shelf, and rack
information in the Detail Information dialog box. Refer to Components Replacement.
2-475


l Yes -> End.
l No -> Step 4.
4. Replace the fiber in accordance with the optical port, slot, shelf, and rack information
in the Detail Information dialog box. Refer to Components Replacement.
l Yes -> End.
2.2.9 198092013 High BER rate at the E1/T1 link

Alarm Information
l Name: High BER rate at the E1/T1 link
Alarm Description
The main control board periodically collects the Bit Error Rate (BES) information of the
E1/T1 bottom-layer link, and reports the alarm in accordance with the statistics. It indicates
the BES of the entire transmission link.
Alarm Cause
The physical E1/T1 link may be abnormal.
Impact
None.
Quality of the services on the E1/T1 link is affected.
Action
a. Check whether the cables in the distribution frame, the transmission equipment
(for example, the optical transceiver or the repeater) ports and E1/T1 on the
SA/SE/PSA front panels are connected properly, for example, whether there is
any short circuit between the cores or wires of a cable because of any unsecured
connector or other objects around the distribution frame.
Yes→Step 2.
No→Substep b.
2-476

Chapter 2 Alarm
b. Reconnect the equipment cables.

Yes→End.
No→Step 2.
2. Verify that the grounding busbar of the equipment is connected properly.
a. Check whether the distribution frame, the transmission equipment and the base
station are connected properly to the same grounding busbar, and whether any of
the following situations occurs: the cable is too thin, connectors are not secured,
the grounding busbar is corroded, the joint is insulated or there is no grounding
busbar.
Yes→Step 3.
No→Substep b.
b. Reconnect or replace the cable between the equipment and the grounding busbar.
Yes→End.
No→Step 3.
3. Replace the E1/T1 cables on the SA/SE/PSA front panels. Refer to Components Re
placement.
Yes→End.
No→Step 4.
4. Change the location of the transmission equipment port or replace the repeater.
Yes→End.
2.2.10 198092230 The SCTP association is broken

Alarm Information
l Name: The SCTP association is broken
Alarm Description
This alarm occurs in the following conditions:
l The Stream Control Transmission Protocol (SCTP) association fails to be established.
2-477

l The notification that the opposite end is shut down is received.

l Data is transmitted to the opposite end for several times but no response is returned.
Alarm Cause
1. The SCTP association parameters of the local end and the opposite end are not
configured correctly.
2. The transmission link is faulty.
Impact
None.
Service signaling messages may not be sent and received normally, and all of the services
operating on the SCTP association are interrupted.
Action
1. Ensure that the SCTP association is correctly configured.
Network→Product (such as UMTS)→Signaling and Busniss→SCTP from the
menu. The SCTP tab is displayed. Check whether the settings of the local port
number, remote address and port number, and the used IP-layer configuration
match the network planning.
No→Substep b.
b. Change the setting of the SCTP association at the local end to be the same as the
network planning.
c. Synchronize the configuration to the NE.。
Yes→End.
No→Step 2.
2. Check whether the transport address from the local end to the remote end is reachable.
a. Ping the remote address of the SCTP association, and check whether an
acknowledgement can be received.
No→Substep b.
b. Based on the network planning, check whether the settings of the IP address and
the route of each node (such as the BSC/RNC/switching device) over the transport
path are correct.
2-478

Chapter 2 Alarm

No→Substep c.
c. Based on the network planning, change the settings of the IP address and the
route of each node (such as the BSC/RNC/switching device) over the transport
path.
Yes→End.
2.2.11 198092231 The PPP link is broken

Alarm Information
l Name: The PPP link is broken
Alarm Description
This alarm occurs when the PPP link is broken.
Alarm Cause
1. The configuration of the PPP link is incorrect.
2. The corresponding E1/T1 link is faulty.
Impact
None.
All of the signaling messages and services operating on the PPP link are interrupted.
Action
a. Check whether the related alarm is raised. If the related alarm is raised, take
action based on the alarm handling suggestion. The related alarm is as follows:
198097109 E1/T1 link is interrupted
Yes→End.
No→Step 2.
2-479

2. Ensure that the PPP link is correctly configured.

a. Select Configuration Management→Managed Element→Transimission
Network→Radio Standard (such as UMTS)→IP Transport→PPP Link from the
menu. The PPP Link tab is displayed. Check whether the PPP encapsulation
type matches the network planning.
No→Substep b.
b. Change the PPP encapsulation type of the local end to be the same as the network
planning.
Yes→End.
2.2.12 198092232 The HDLC link is broken

Alarm Information
l Name: The HDLC link is broken
Alarm Description
This alarm occurs when the HDLC link is broken.
Alarm Cause
1. The configuration of the HDLC link is incorrect.
2. The transmission quality of the corresponding E1/T1 link decreases.
Impact
None.

All of the signaling messages and services operating on the HDLC link are interrupted.
Action
2-480

Chapter 2 Alarm
a. If the related alarm has been raised, take the corresponding action based on the
alarm handling suggestion. The related alarm is as follows:
Yes→End.
No→Step 2.
2. Ensure that the HDLC channel is correctly configured.
Network→Radio Standard (such as UMTS)→IP Transport→HDLC Channel from
the menu. The HDLC Channel tab is displayed. Check whether the time slot bit
mapping matches the network planning
No→Substep b.
b. Change the time slot bit mapping of the local end to be the same as the network
planning.
Yes→End.
2.2.13 198092233 The SSCOP link is broken

Alarm Information
l Name: The SSCOP link is broken
Alarm Description
l The SSCOP link fails to be established.

Alarm Cause
The PVC parameters are not configured correctly.
2-481

Impact
None.
Service signaling messages and ALCAP signaling messages may not be sent and received
normally, and all of the services operating on the SSCOP link are interrupted.
Action
198092362 The IMA/TC link is faulty

Yes→End.
No→Step 2.
2. Ensure that the SaalUni parameters are correctly set.
Network→Radio Standard (such as UMTS)→ATM Transport Network→SaalUni
from the menu. The SaalUni tab is displayed. Check whether the settings of the
used ATM-layer link, virtual path number, virtual channel number, and AAL5 flow
attributes match the network planning.
Yes→Step 3.
No→Substep b.
b. Change the settings of the SaalUni parameters at the local end to be the same as
the network planning.
Yes→End.
No→Step 3.
3. Inform the maintenance personnel of the peer device to check whether the
transmission is abnormal.
Yes→Maintenance personnel of the peer device resolve the transmission fault.
2-482

Chapter 2 Alarm
2.2.14 198092361 The IMA group is faulty

Alarm Information
l Name: The IMA group is faulty
Alarm Description
This alarm occurs when an Inverse Multiplexing over ATM (IMA) group cannot operate
properly after it is configured.
Alarm Cause
1. The system clock is abnormal.
2. The transmission relay device is faulty or incorrectly configured.
3. The E1/T1 cable connection is faulty.
4. The base station or the RNC is not configured properly.
Impact
None.
All the services of the IMA group are interrupted.
Action
corresponding handling suggestions. Related alarms are as follows:
198096832 Line clock source fault
Yes→End.
No→Step 2.
2. Verify that the IMA parameters are configured correctly.
a. Select Configuration Management→Managed Element -> Transmission
Network→UMTS (for example)→ATM Transport Network -> ATM Layer Link,
and check whether the ATM layer protocol type, Enable descrambling, Frame
2-483

length, Clock mode, Used physical layer port and Used channelized SMT-1 are
Yes→Step 3.
No→Substep b.
b. Modify the corresponding IMA parameters as planned.
Yes→End.
No→Step 3.
3. Contact the maintenance personnel for the peer to verify that the switching devices
including RNC are configured correctly.
Yes→End.
2.2.15 198092362 The IMA/TC link is faulty

Alarm Information
l Name: The IMA/TC link is faulty
Alarm Description
This alarm occurs when a sublink of the IMA group or the TC link becomes faulty.
Alarm Cause
1. The transmission relay device is faulty or incorrectly configured.
2. The base station or the RNC is not configured properly.
Impact
None.

The transmission bandwidth is reduced and the service traffic of the system is decreased.
2-484

Chapter 2 Alarm
Action
1. Verify that the IMA/TC parameters are configured correctly.
Network→UMTS (for example)→ATM Transport Network→ATM Layer Link, and
check whether the ATM layer protocol type is set to IMA or TC.
If the ATM layer protocol type is set to IMA, check whether the Enable
descrambling, Frame length, Clock mode, Used physical layer port and Used
channelized SMT-1 are configured as planned.
If the ATM layer protocol type is set to TC, check whether the Enable descrambling,
Used physical layer port, Time slot bit mapping and Used channelized SMT-1 are
Yes→Step 2.
No→Substep b.
b. Modify the corresponding IMA/TC parameters as planned.
Yes→End.
No→Step 2.
2. Contact the maintenance personnel for the peer to verify that the switching devices
including RNC are configured correctly.
Yes→End.
No→Step 3.
3. Contact the corresponding maintenance personnel to verify that transmission data is
Yes→End.
2.2.16 198092399 The BFD connection is broken

Alarm Information
l Name: The BFD connection is broken
2-485

Alarm Description
l The Bidirectional Forwarding Detection (BFD) connection fails to be established.
Alarm Cause
1. The BFD parameters of the local end and the opposite end are not configured correctly.
Impact
None.
Signaling messages may not be sent and received normally, and all of the services
operating on the connection are interrupted.
Action
1. Ensure that the BFD parameters are correctly set.
Network→Radio Standard (such as UMTS)→Network Detection→Bidirectional
Forwarding Detection from the menu. The Bidirectional Forwarding Detection
tab is displayed. Check whether the settings of the used UDP bearer, peer IP,
multi-hop detection, and BFD authentication match the network planning.
Yes→Step 2.
No→Substep b.
b. Change the settings of the BFD parameters at the local end to be the same as
those at the peer end.
Yes→End.
No→Step 2.
No→Substep b.
2-486

Chapter 2 Alarm
path are correct.
No→Substep c.
path.
Yes→End.
2.2.17 198092401 E1/T1 link self-loop

Alarm Information
l Name: E1/T1 link self-loop
Alarm Description
This alarm occurs when the E1/T1 link is self-looped.
Alarm Cause
The physical E1/T1 link may be abnormal.
Impact
None.
All the services on the E1/T1 link are interrupted.
Action
1. Verify that there is no self-loop E1/T1 cable in the distribution frame.
a. Check whether there is a self-loop E1/T1 cable in the distribution frame.
Yes→Substep b.
No →Step 2.
b. Connect the E1/T1 cable correctly.
2-487


Yes→End.
No→Step 2.
2. Contact the corresponding maintenance personnel to verify that transmission is
Yes→End.
2.2.18 198092402 The TCP connection is broken

Alarm Information
l Name: The TCP connection is broken
Alarm Description
l The Transfer Control Protocol (TCP) connection fails to be established.
Alarm Cause
1. The local FE configuration or PPP configuration is incorrect.
2. The TCP parameters of the local end and the opposite end are not configured correctly.
Impact
None.
Signaling messages may not be sent and received normally, and all of the services
operating on the TCP connection are interrupted.
Action
2-488

Chapter 2 Alarm
Yes→End.
No→Step 2.
2. Ensure that the PPP link is correctly configured.
Network→Radio Standard (such as UMTS)→IP Transport→PPP Link from the
menu. The PPP Link tab is displayed. Check whether the PPP encapsulation
type matches the network planning.
Yes→Step 3.
No→Substep b.
b. Change the PPP encapsulation type of the local end to be the same as the network
planning.
Yes→End.
No→Step 3.
3. Ensure that the TCP parameters are correctly set.

Network→Radio Standard (such as UMTS)→Signaling and Busniss→TCP from
the menu. The TCP tab is displayed. Check whether the settings of the used
IP address, used bandwidth resources, remote address, and QoS match the
network planning.

No→Substep b.
b. Change the TCP setting of the local end to be the same as the network planning.

Yes→End.
2-489

2.2.19 198092428 The SCTP path is broken

Alarm Information
l Name: The SCTP path is broken
Alarm Description
l No response to the heartbeat is received in some path of the SCTP association.
l The number of retransmitting data is larger than the maximum retransmission number
of the path.
Alarm Cause
1. The SCTP association parameters of the local end and the opposite end are not
Impact
None.
If all paths of an SCTP association are broken, the service signaling cannot be transferred
properly, causing the services that the SCTP association bears to interrupt.
Action
1. Ensure that the SCTP association is correctly configured.
Network→Radio Standard (such as UMTS)→Singalling and Busniss -> SCTP
from the menu. The SCTP tab is displayed. Check whether the settings of
the local port number, remote address and port number, and the used IP-layer
configuration match the network planning.
Yes→Step 2.
No→Substep b.
b. Change the setting of the SCTP association at the local end to be the same as the
network planning.
2-490

Chapter 2 Alarm
Yes→End.
No→Step 2.
No→Substep b.
path are correct.
No→Substepc
path.
Yes→End.
2.2.20 198096839 RRU inner GNSS clock source abnormal

Alarm Information
l Name: RRU inner GNSS clock source abnormal
Alarm Description
This alarm occurs when all RRU links are abnormal, one synchronization information
cannot be obtained from one link, or the obtained synchronization information is
unavailable in the configuration of RRU inner GNSS clock reference source.
Alarm Cause
1. The communication link between the RRU and the BBU is abnormal.
2. Searching satellite abnormal on the RRU.
Impact
2-491

None.
If the fault persists for a long time, some functions may not operate properly. In serious
cases, wireless links cannot be created. Services on this base station may be partially
blocked or the quality of services may be affected.
Action
a. Check whether any related alarm exists on the RRU.If such an alarm exists,
remove it based on the corresponding handling suggestion. The related alarms
are as follows:
Yes→End.
No→Step 2.
Yes→End.
2.2.21 198097169 The next hop IP is unreachable

Alarm Information
l Name: The next hop IP is unreachable
Alarm Description
This alarm occurs when the next hop IP address is unreachable.
Alarm Cause
1. The target IP address is not configured correctly.
2. The transmission network is faulty.
2-492

Chapter 2 Alarm
Impact
None.
Signaling messages may not be sent or received normally, causing All services operating
on the connection are interrupted.
Action
1. Ensure that the route detection object parameter is correctly set.
Network→Network Detection→Routing Detection Object. The corresponding
tab is displayed. Check whether the destination IP and the used IP-layer are
configured in accordance with the network planning data.
Yes→Step 2.
No→Substep b.
b. Select Configuration Management→Managed Element→Transmission
Network→Network Detection→Routing Detection Object. The corresponding tab
is displayed. Modify the settings of the destination IP and the used IP layer in
accordance with the network planning data.

Yes→End.
No →Step 2.
2. Inform maintenance personnel of the peer end to check the transmission.
Yes→Maintenance personnel of the peer end resolve the transmission fault.
2.2.22 198097171 Authentication failure

Alarm Information
l Name: Authentication failure
Alarm Description
This alarm occurs when abnormality occurs during authentication process.
2-493

Alarm Cause
1. Interrupted physical link.
2. The user ID and password do not match those configured on the authentication server.
Impact
None.
Packet sending/receiving through the Ethernet link is affected. All or some of the services
on this base station may be blocked.
Action
1. Check whether the network interface of the local device is not damaged.
a. Check whether the network interface of the local device is not damaged.
Yes→Step 2.
No→Substep b.
b. Replace the board in accordance with the Rack Number, Shelf Number, and Slot
Yes→End.
No→ Step 2.
2. Check whether the cable connector of the local device is loose.
a. Check whether the cable connector of the local device is loose.
Yes→Substep b.
No→Step 3.
Yes→End.
No→Step 3.
3. Check the connection cable of the local device.
a. Check whether the connection cable of the local device is not damaged.
Yes→Step 4.
No→Substep b.
b. Replace the cable. Refer to Components Replacement.
2-494

Chapter 2 Alarm
Yes→ End.
No→Step 4.
4. Check whether the local DOT1X parameter is configured correctly.
a. Select Configuration Management -> Managed Element→Transmission
Network→UMTS→Network Security -> DOT1X Parameter and check whether
the Ethernet link, authentication user name, authentication password, maximum
authentication times, the time for waiting for the EAP packet from the peer end,
and the time for waiting for authentication response are the same as planned.
No→Substep b.
b. Modify the local DOT1X parameter to the setting as planned.

Yes→End.
2.2.23 198097172 Configuration parameter of OAM Channel is

wrong
Alarm Information
l Name: Configuration parameter of OAM Channel is wrong
Alarm Description
OMCB channel is abnormal and need to configurate correct channel data.
Alarm Cause
It is successful to build link automatically in transport /It is trying to build link automatically/It
is trying to build link assistantly /It is successful to build link assistantly in FE
transport/Finish negotiating link auto-setup parameters:
The OMCB channel is not operating properly, and the OMCB channel should be correctly
configured.
OMCB channel rolls back/The base station starts an O&M channel auto-recovery function:
The link is broken when the base station configuration is synchronized, causing the
configuration to be rolled back.
2-495

Impact
None.
The system allows the whole table synchronization only, and other services cannot be
used.
Action
1. Select Configuration Management→Managed Element. The corresponding tab is
displayed. Check whether the settings of the physical bearer, IP transport or ATM
transport, network detection, network security, static routes, and OMC channnel are
set in accordance with the network planning data.
Yes→Step 3.
No→Step 2.
2. Modify the settings of the physical bearer, IP transport or ATM transport, network
detection, network security, static routes, and OMC channnel in accordance with the
3. Synchronize the configuration to the NE (whole table synchronization).
Yes→End.
2.2.24 198098252 The physical Ethernet link is broken

Alarm Information
l Name: The physical Ethernet link is broken
Alarm Description
This alarm occurs when the Ethernet connection has been configured and the system
detects that the physical Ethernet link is broken.
Alarm Cause
Ethernet port is configured, but no Ethernet cable is connected to it or the network cable
is damaged.
2-496

Chapter 2 Alarm
Impact
None.
The Ethernet transmission services borne on the board may be interrupted.
Action
1. Verify that the Ethernet cable is correctly connected.
a. Check whether the Ethernet cable for the corresponding port is correctly
connected in accordance with the slot, shelf, rack information in the Detail
Information dialog box and the port information in the Remark field.
Yes→Step 2.
No→Substep b.
b. Reconnect the cable.
Yes→End.
No→Step 2.
2. Replace the cable with a proper one. Refer to Components Replacement.
Yes→End.
2.2.25 198098319 Optical port receiving link failure

Alarm Information
l Name: Optical port receiving link failure
l Alarm type: Communication Alarm
1. If loss of optical port K code is severe, this alarm is reported.
2. If the bit errors of the optical port are severe, this alarm is reported.
3. If the optical port does not receive optical signals, this alarm is reported.
Alarm Cause
1. Fibers or cables are damaged.
2-497

2. The surfaces of fibers or cables are dirty.

3. The optical or electrical module on the local or peer end is not fully inserted into the slot.
4. Fibers or cables are not connected firmly.
5. The optical or electrical module of the peer equipment is damaged.
6. The actual fiber length is longer than the maximum length supported by the optical
module.
7. The peer equipment is operating abnormally.
Impact
None.
The services of cell associated to the optical port are interrupted or the service quality may
be affected.
Action
1. Check whether the relevant alarms occur on the local end.
a. a. Check whether the relevant alarms occur on the local end. If so, handle the
faults based on the corresponding treatment suggestions. The relevant alarm:
b. b. Check whether the alarm disappears.
Yes→End.
No→Step 2.
2. Check whether the received optical power of the optical module is normal.
a. During diagnostic tests, diagnose the board based on the information about rack
No., frame No., and slot No. in alarm details. Base on the information about optical
port No. in alarm details, check whether the received optical power of the optical
module. The receiving sensitivities of common optical modules are described as
follows:
1.25G (-19 dBm)
2.5G (-17 dBm)
6G (-15 dBm)
10G (-13 dBm)
b. Check whether the received power of the optical module is lower than the receiving
sensitivity.
Yes→Substep c.
No→Step 3.
2-498

Chapter 2 Alarm
c. During diagnostic tests, diagnose the board based on the information about rack
No., frame No., and slot No. in alarm details. Base on the information about optical
port No. in alarm details, query the maximum distance supported by the optical
module, and then check whether fiber length is long than the maximum distance
supported by the optical module.
Yes→Substep d.
No→Substep e.
d. Replace the optical module with a proper one or reduce fiber length.
Waiting for 15 minutes, Check whether the alarm disappears.
Yes→End.
No→Substep e.
e. Check whether fiber connections are normal.
Yes→Substep f.
No→Substep g.
f. Check whether the surfaces of fiber connectors are dirty.
Yes→Substep h.
No→Substep i.
g. Connect fibers.
Waiting for 15 minutes, check whether the alarm disappears.
Yes→End.
No→Substep i.
h. Clean the fiber connectors.
Yes→End.
No→Substep i.
i. Check whether fibers are in good condition.
Yes→Step 3.
No→Substep j.
j. Replace fibers.
Yes→End.
No→Step 3.
2-499

Yes→End.
No→Step 4.
Yes→End.
No→Step 5.
5. Inform the maintenance personnel of the peer equipment to check whether the peer
equipment is abnormal.
Yes→Maintenance personnel handle peer equipment faults.
2.2.26 198094416 CPRI link abnormal

Alarm Information
l Name: CPRI link abnormal
The link from the BBU to the RRU is abnormal.
Alarm Cause
1. The optical fiber is not installed in a correct position.
2. The optical module is not present.
3. The connectors of the optical fibers are not clean.
4. The rate of the optical module does not match that of optical fibers.
5. The rate of the optical module is inconsistent with version requirements.
6. The RRU software version is incorrect.
7. The RRU board is faulty.
8. The BPL board is faulty.
9. The transmission network is faulty.
10. The optical fiber is damaged.
Impact
I. Board status:
2-500

Chapter 2 Alarm
Operates properly.
If the optical module is not present or has no optical signals, services that are borne by
the corresponding RRU of the link are interrupted. Under other situations, services may
be interrupted.
Action
l The optical module is not present.
1. Check whether the optical module is installed.
a. According to the rack ID, shelf ID, slot ID, and optical port ID in detailed
alarm information, check whether the optical module is installed in the
corresponding port.
Yes→Step 2.
No→Substep b.
b. Install the optical module correctly.
Yes→End.
No→Step 2.
information, remove the optical module and reinstall it.
Yes→End.
No→Step 3.
Yes→End.
No→Step 4.
4. In Dynamic Management→Dynamic Command→SDR→Device Group,
according to the rack ID, shelf ID, and slot ID in detailed alarm information, power
off the board and reset it.
Yes→End.
l Others:
2-501

a. Check whether the related alarm exists on this board. If such alarms exist,
remove them based on the corresponding handling suggestion. The related
alarms are as follows:
Optical module rate does not match (198094429)
The strength of received optical signal is abnormal (198094430)
Optical module transmit power is abnormal (198094427)
Yes→End.
No→Step 2.
information, check the optical fiber. (Note: In the additional text,
a. Check whether the optical fiber is connected properly.
Yes→Step b.
No→Substep c.
b. Check whether connectors of the optical fiber are contaminated.
Yes→Substep d.
No→Substep e.
c. Connect the optical fiber properly.
Yes→End.
No→Substep b.
d. Clean connectors of the optical fiber.
Yes→End.
No→Substep e.
e. Check whether the optical fiber is intact.
Yes→Step 3.
No→Step f.
f. Replace the optical fiber.
Yes→End.
No→Step 3.
information, remove the optical module and reinstall it. (Note: In the additional
text,
2-502

Chapter 2 Alarm

Yes→End.
No→Step 4.
information, replace the optical module. (Note: In the additional text,
Yes→End.
No→Step 5.
information, follow step 2 to check the optical fiber and optical module of the
peer-end board.
Yes→End.
2.2.27 198094420 S1 link is broken

Alarm Information
l Alarm code：198094420
l Name：S1 link is broken
l Alarm severity：Critical
l Alarm type：Communication alarm
When SCTP association is broken or S1AP setup fails, this alarm will be reported.
Alarm Cause
1. The SCTP association is broken.
2. The S1AP fails to be established (due to negotiation failure or no cells available under
the eNodeB).
Impact
I. Board status:
Operates properly.
The link between the eNodeB and the MME is broken, and the eNodeB may fail to provide
services.
2-503

Action
1. View alarm details and find the cause of the alarm.
"S1 SCTP association is interrupted"→Step 2.
"S1AP setup fail"→Step 3.
a. Check whether the following alarms exist. If yes, remove them according to
corresponding handling suggestions. The related alarm is as follows:
The SCTP association is broken (198092230)
Yes→End.
3. Check whether the eNodeB is configured with cells.
a. Select Configuration Management→Radio Parameter→LTE FDD→E-UTRAN
FDD Cell, and check whether there are cell records available.
Yes→Step 3.
No→Substep b.
b. Add a cell record in the list.
c. Synchronize the configuration data to the eNodeB and check whether the alarm
is cleared.
Yes→End.
No→Step 4.
4. Check whether the S1 configuration parameter is valid.
FDD Cell, and check whether the TAC in the cell record is supported by the core
network.
Yes→Step 5.
No→Substep b.
b. Modify the tracking area code to a value supported by the core network.
is cleared.
Yes→End.
No→Step 5.
5. Check whether the PLMNLIST is correct.
FDD Cell, view the PLMN records used by the cell from the PLMN List, and check
whether the PLMN and core network have the common configurations.
2-504

Chapter 2 Alarm
Yes→Contact technical support.

No→Substep b.
b. Modify the parameters of the PLMN used by the cell and make sure that the PLMN
and core network have the common configurations.
is cleared.
Yes→End.
2.2.28 198094421 X2 link is broken

Alarm Information
l Name：X2 link is broken
l Alarm severity：Major
When SCTP association is broken or X2AP setup fail, this alarm will be reported.
Alarm Cause
2. The X2AP fails to be established (due to negotiation failure or no cells available under
the eNodeB).
Impact
I. Board status:
Operates properly.
The link between two neighboring eNodeBs is broken, and the X2 interface switchover
between the eNodeBs may be affected.
Action
"X2 SCTP association is interrupted"→Step 2.
"X2AP setup fail"→Step 3.
2-505

Yes→End.
a. Check whether related alarms exist. If yes, remove them according to
eNodeB is out of service (198094422)
b. Check whether the related alarm is cleared.
Yes→End.
No→Step 4.
4. Check whether related alarms exist in the peer eNodeB corresponding to the X2
interface of this eNodeB.
a. View alarm details and obtain the X2 association ID corresponding to the alarm.
b. Select Configuration Management→Transmission Network→Signalling and
Business→SCTP, and find the record corresponding to the X2 association ID.
c. View the remote IP address from this X2 association ID record and verify the peer
NE.
d. In the Alarm Monitoring window, check whether the peer NE-related alarms exist.
If yes, remove them according to corresponding handling suggestions. The related
e. Check whether the related alarm is cleared.
Yes→End.
No→Step 5.
5. Check whether the local and remote eNodeBs corresponding to the alarmed X2
interface are configured with an X2 black list.
a. Select Configuration Management→Radio Parameter→LTE FDD, view "X2 Black
List", and check whether the eNodeBs corresponding to the alarmed X2 interface
is on the list.
Yes→Substep b.
b. Delete the record from the X2 black list.
2-506

Chapter 2 Alarm
is cleared.
Yes→End.
2.2.29 198094430 The strength of received optical signal is

abnormal
Alarm Information
l Name: The strength of received optical signal is abnormal
The receive optical power of the optical module is too low or too high.
Alarm Cause
1. The receive power of the optical module is too low.
2. The receive power of the optical module is too high.
Impact
I. Board status:
Operates properly.
interrupted.
Action
1. Check whether the following problems exist on the optical fiber.
a. Start a diagnostic test for the board based on the rack ID, shelf ID, and slot ID
in detailed alarm information. According to the optical port ID in detailed alarm
information, view the maximum distance supported by the optical module, and
check whether the length of the optical fiber exceeds the maximum distance.
Yes→Substep b.
No→Substep c.
b. Replace an appropriate optical module or reduce the length of the optical fiber.
2-507

Yes→End.
No→Substep c.
c. Check whether the optical fiber is connected properly.
Yes→Substep d.
No→Substep e.
d. Check whether connectors of the optical fiber are contaminated.
Yes→Substep f.
No→Substep g.
e. Connect the optical fiber properly.
Yes→End.
No→Substep d.
f. Clean connectors of the optical fiber.
Yes→End.
No→Substep g.
g. Check whether the optical fiber is intact.
Yes→Step 2.
No→Substep h.
h. Replace the optical fiber.
Yes→End.
No→Step 2.
information. remove the optical module and reinstall it.
Yes→End.
No→Step 3.
Yes→End.
No→Step 4.
4. Check whether the following problems exist on the optical fiber to the peer-end board.
2-508

Chapter 2 Alarm
a. Check whether the optical fiber is connected properly.

Yes→Substep b.
No→Substep c.
b. Check whether connectors of the optical fiber are contaminated.
Yes→Substep d.
No→Step 5.
c. Connect the optical fiber properly.
Yes→End.
No→Substep b.
d. Clean connectors of the optical fiber.
Yes→End.
No→Step 5.
5. Remove the optical module and reinstall it. After 15 minutes, check whether this alarm
is cleared.
Yes→End.
No→Step 6.
6. Replace the optical module. After 15 minutes, check whether this alarm is cleared.
Yes→End.
No→Step 7.
7. Reset the board. After 15 minutes, check whether this alarm is cleared.
Yes→End.
2.2.30 198094455 All MME associations interrupted

Alarm Information
l Name：All MME associations interrupted
All associations connected with MME are interrupted.
2-509

Alarm Cause
All the SCTP association is broken.
Impact
I. Board status:
Operates properly.
All connections between the eNodeB and MME are broken and the eNodeB fails to provide
services.
Action
1. Check whether related alarms exist. If yes, remove at least one of them according to
S1 link is broken (198094420)
Yes→End.
2.3 Wrong Operation Alarm

2.3.1 198093020 Software run-time exceptions
Alarm Information
l Name: Software run-time exceptions
l Alarm type: Wrong operation alarm
The software is not running properly.
Alarm Cause
1. The IPTB setup fails.
2. The interface is configured incorrectly.
Impact
1. Board status:
2-510

Chapter 2 Alarm

2. Service impact:
Action
For "IPTB setup failure" and "Radio parameter error between BUC and DBB ", do the
following operations:
plug the board.
If no, contact technical support.
For "Radio parameter error between GSPS and BUC", do the following operations:
2. Power off and reset the CC board.
plug the board.
2-511


4. Unplug and plug the CC board.
6. Replace the CC board.
2.3.2 198093021 Config error alarm

Alarm Information
l Name: Config error alarm
The configuration is incorrect.
Alarm Cause
The configuration is incorrect.
Impact
1. Board status:
2. Service impact:
2-512

Chapter 2 Alarm
Action
Insufficient number of configured OMMB TRXs:
1. On the OMMR, select Configuration Management > GSM Logical Function
Configuration > Cell Function Configuration, and check the configuration of the GSM
cells and TRXs. On the OMMB, select Configuration Management > Radio Parameters
> GSM, and check the configuration of the GSM cells, TRXs, and channel resources to
find whether there are cells (TRXs) configured on the OMMR but not configured on the
OMMB.
If no, no further action is required.
2. On the OMMB GUI, add the corresponding cells (TRXs).
Insufficient baseband resources:
1. On the OMMB, select Configuration Management > Equipment Configuration, and add
UBPG boards till the alarm is cleared.
Inconsistent TRX frequency bands on the OMMB and OMMR:
1. Check whether the TRX frequency bands on the OMMB (Configuration Management >
Radio Parameters > GSM > TRX) are consistent with those on the OMMR (Configuration
Management > GSM Logical Function Configuration > Cell Function Configuration > TRX).
2. Modify the frequency band configurations to be consistent. In the OMMB Configuration
Management window, add the RRU rack with the same frequency band and related
configurations such as optical ports and RF information, and apply them to the RRU. After
the alarm is cleared, no further action is required.
Insufficient RRU resources (due to insufficient bandwidth):

1. On the OMMB diagnosis view, select GSM > Query GSM Physical Logical Relations,
and find the logical TRXs that are not successfully allocated. On the OMMB, select
Configuration Management > Equipment to configure the RRUs in the duplex range,
and select Configuration Management > Radio Parameters > GSM to configure the
corresponding cell channel resources, cells, and TRXs. The alarm is cleared.
Unconfigured bearing resources on the GSM user plane:
1. On the OMMB, select Configuration Management > Transmission > Signaling and
Service > Service and DSCP Mapping to configure the TRAFMAP table.
Unconfigured GSM association resources:
1. On the OMMB, select Configuration Management > Transmission > Signaling and
Service > SCTP to configure the association information. The alarm is cleared.
2-513

2.3.3 198093056 Software loading is abnormal

Alarm Information
l Name: Software loading is abnormal
FPGA or DSP software loading fails.
Alarm Cause
1. FPGA software version is incorrect.
2. DSP software version is incorrect.
3. FPGA or DSP hardware is faulty.
Impact
Action
1. The alarm can be cleared automatically. Wait for five minutes and check whether the
alarm is cleared.
2-514

Chapter 2 Alarm

2.3.4 198093922 Board configuration parameter error

Alarm Information
l Name: 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.
Alarm Cause
1. The configurations of some parameters of the local cell do not exist.
2. The configurations of some parameters of the local cell are incorrect.
Impact
None.
The board is faulty. All the services on the board are interrupted.
Action
1. Check whether the parameters of the local cell are configured in accordance with the
plan of the existing network.
a. Select Configuration Management -> Managed NE -> Radio Parameter -> UMTS ->
UMTS Sector -> Local Cell, check whether the parameters of the local cell are configured
in accordance with the plan of the existing network.
Yes -> Step 2.
No -> Substep b.
b. Modify the parameters of the local cell in accordance with the plan of the existing
network.
2-515

Yes -> End.

No -> Step 2.
Yes -> End.
2.3.5 198093939 Insufficient IQ channel resource

Alarm Information
l Name: Insufficient IQ channel resource
Alarm Description
This alarm is reported when IQ optical port resource is exhausted.
Alarm Cause
The IQ channel resource is insufficient.
Impact
None.
The application for IQ resource fails, and the services borne by the board are
interrupted.
Action
1. Check whether the parameters of the local cell are configured in accordance with the
plan of the existing network.
a. Select Configuration Management -> Managed NE -> Radio Parameter -> UMTS
-> UMTS Sector -> Local Cell, check whether the parameters of the local cell are
configured in accordance with the plan of the existing network.
l Yes -> Step 2.
l No -> Substep b.
b. Modify the parameters of the local cell in accordance with the plan of the existing
network.
2-516

Chapter 2 Alarm

l Yes -> End.
l No -> Step 2.
2. Release some cells.
a. Select Configuration Management -> Managed NE -> Radio Parameter -> UMTS
-> UMTS Sector -> Local Cell, and then delete some cells.
l Yes -> End.
2.3.6 198093955 Number of RACH packets in a cell exceeds alarm

threshold
Alarm Information
l Name: Number of RACH packets in a cell exceeds alarm threshold
Alarm Description
Number of RACH packets in a cell per minute exceeds a specified threshold.
Alarm Cause
A great number of users request for access in one minute. The number of accessed users
exceeds the configured threshold.
Impact
None.
Access of the user in the cell is affected. The services borne by the board may be
Action
1. After 60 minutes, check whether this alarm is cleared.
l Yes -> End.
2-517

2.3.7 198094027 BBS parameters are not matched

Alarm Information
l Name: BBS parameters are not matched
This alarm is reported when the preamble detection paramter is wrongly configured for
baseband process chip and the relevant cell cannot work properly.
Alarm Cause
The parameters of the cell are not configured in accordance with the capability of the board.
Impact
None.

Action
1. Verify that the PRACH parameter of the RNC cell is correctly configured.
a. In the RNC network management system, select Configuration Management -> RNC
Radio Management Resource, select the service cell as required, open the PRACH tab
on the Advanced Parameter Manager page, and then check whether only one R99 Prach
is configured.
Yes -> Contact the customer service center.
No -> Substep b.
b. Modify the value of the PRACH parameter to ensure that only one R99 Prach is
configured.
c. Synchronize the configuration.

Yes -> End.
2-518

Chapter 2 Alarm
2.3.8 198093981 Digital PA over power alarm

Alarm Information
l Name: Digital PA over power alarm
Alarm Description
When system detects the output power of digital PA exceeds rated power by 2dbm
will report this alarm. When DSP detects the output power of digital PA exceeds fixed
threshold, also will report the alarm by CPU.
Alarm Cause
l The total power of all cells of the RRU exceeds the rated power.
l The optical fiber between the RRU board and the BBU board is abnormal.
l The FS board is faulty.
l The baseband process board is faulty.
Impact
The amplifier may be damaged.
The amplifier is shut down due to constant overpower. The services borne by the
board are entirely interrupted.
Action
1. Verify that the total power of all cells does not exceed the rated power.
a. Check whether the total power of all cells of the RRU exceeds the rated power
in accordance with the rack number, shelf number, and slot number in the alarm
information.
Yes -> Substep b.
No -> Step 2.
b. Reconfigure the power of the cell in accordance with the plan of the existing
network.
l Yes -> End.
2-519

l No -> Step 2.
l Yes -> End.
l No -> Step 3.
3. Reset the optical interface board. Refer to Reset Boards.
a. Select Configuration Management -> Managed Element , double-click Device.
The Rack Graph page is displayed with the Physical View and Topology View tabs.
On the Topology View tab, query the slot of the optical interface board connected
to the RRU board.
b. Reset the board based on the slot number verified in substep a. Refer to Reset
Boards.
l Yes -> End.
l No -> Step 4.
4. Reset the baseband process board. Refer to Reset Boards.

a. Determine the slot of the baseband process board in accordance with the rack
number, shelf number, and slot number in the alarm information.
b. Reset the board based on the slot number verified in substep a.

l Yes -> End.
l No -> Step 5.
5. Replace the optical fiber. Refer to Components Replacement.
l Yes -> End.
l No -> Step 6.

l Yes -> End.
l No -> Step 7.
7. Replace the board based on the slot number of the optical interface board verified in
step 3. Refer to Components Replacement.
l Yes -> End.

l No -> Step 8.
2-520

Chapter 2 Alarm
8. Replace the board based on the slot number of the baseband process board verified
in step 4. Refer to Components Replacement.
l Yes -> End.
2.3.9 198092014 SNTP time adjustment failure

Alarm Information
l Name: SNTP time adjustment failure
Alarm Description
The Simple Network Time Protocol (SNTP) server is not started or the link is faulty.
Alarm Cause
1. The IP address configuration of the SNTP time synchronization server is wrong.
2. The SNTP server is faulty.
3. Network fault.
Impact
None.
The system time is inaccurate, but does not affect services.
Action
1. Check whether the IP address configuration of the SNTP server is correct.
a. Select Configuration Management→Managed Element→System
Parameter→Time Configuration, and check whether the IP addresses of the NTP
server and standby SNTP server are the same as planned.
Yes→Step 2.
No→Substep b.
b. Change the IP addresses of the servers to the planned IP addresses of the current
network.
2-521


Yes→End.
No→Step 2.
2. Check whether the SNTP service on the SNTP server is normal.
a. Check whether the SNTP service on the SNTP server is normal (refer to the SNTP
service configurations of the operating system).
Yes→Step 3.
No→Substep b.
b. Enable the SNTP service.
c. Select Dynamic Management→Dynamic Command→SDR→Managed Network
Element→Time, and synchronize NE time. Check whether the synchronization
is successful.
Yes→Substep d.
No→Step 3.
Yes→End.
No→Step 3.
3. Check whether the communication between the base station and SNTP server is
normal.
a. Use the ping tool on the SNTP server to check whether the communication with
the base station is normal.
Yes→Substep b.
b. Use the brsping tool on the base station server to check whether the
communication with the SNTP is normal.
Yes→Substep c.
c. Select Dynamic Management→Dynamic Command→SDR→Managed Network
Element→Time, and synchronize NE time. Check whether the synchronization
is successful.
Yes→Substep d.
Yes→End.
2-522

Chapter 2 Alarm
2.3.10 198092017 Software loading failure

Alarm Information
l Name: Software loading failure
Alarm Description
This alarm occurs when the board fails to load CPU/DSP/FPGA software versions.
Alarm Cause
1. The board software version is not correct.
Impact
None.
All of the services operating on the board are interrupted.
Action
Select Software Version Management→Upgrade Management from the menu. The
Upgrade Management tab is displayed. Redownload all planned version packages.
Yes→End.
2.3.11 198092019 Failure in active/standby synchronization

Alarm Information
l Name: Failure in active/standby synchronization
Alarm Description
This alarm occurs when the active/standby synchronization fails.
2-523

Alarm Cause
The standby board fails to synchronize version files with the active board.
Impact
None.
The active/standby switchover is not performed: Services are not affected, but the system
reliability is degraded
The active/standby switchover is performed: The software-related boards cannot operate
properly, and all of the services operating on the board are interrupted.
Action
1. Select Software Version Management→Upgrade Management from the menu. The
Yes→End.
No→Step 2.
2. Confirm the slot of the backup board and reset the board based on the rack
Yes→End.
2.3.12 198092027 Failure in repairing a version package

Alarm Information
l Name: Failure in repairing a version package
Alarm Description
During the board power-on process, this alarm occurs when the system detects that a
version package flag is abnormal and fails to repair the version package.
Alarm Cause
The version package fails to be repaired.
2-524

Chapter 2 Alarm
Impact
None.
All the controlled boards cannot boot properly and cannot bear any service.
Action
1. After the alarm is raised, wait 15 minutes, and check whether the alarm has been
cleared.
Yes→Step 2.
2. Select Software Version Management→Upgrade Task Management from the menu.
The Upgrade Task Management tab is displayed. Download, pre-activate, and apply
the upgrade version package.
After the status in the task list is displayed as successful, wait 30 minutes and check
whether the alarm has been cleared. Check whether the alarm has been cleared.
Yes→End.
2.3.13 198092029 Hardware type is different from the configuration

Alarm Information
l Name: Hardware type is different from the configuration
Alarm Description
This alarm occurs when the main control board detects that the type of the board installed
in the actual slot or the RRU or the TANK is different from that configured in the OMC.
Alarm Cause
1. The board is not configured properly on the OMC.
2. The actually installed board ,the connected RRU or the Tank is not of the correct type.
Impact
None.
2-525


The board type or RRU type does not match the configuration: The board cannot operate
properly, and all of the services operating on the board are interrupted.
The physical type of the board does not match the configuration: All of the services
operating on the board may be affected.
The cabinet type does not match the configuration: Temperature sensor or fan alarms are
misreported. The fan noise is too large or the heat dissipation requirement cannot be met
(in this case, the board temperature is too high, causing services to be affected).
Action
Perform the following operations based on the information in the Remark field of the Detail
Information dialog box:
l The module group ID of the physically connected board is inconsistent with that
configured in the OMC/The logical type of the physically connected board is
inconsistent with that configured in the OMC/The PA type of the physically connected
device is inconsistent with that configured in the OMC/The frequency band of the
physically connected device is inconsistent with that configured in the OMC/The
physically connected RRU type is inconsistent with that configured in the OMC:
1. Based on the information in the Remark field of the Detail Information dialog box,
check whether the board type or RRU type matches the network planning.
Yes→Step 2.
No→Step 3.
2. Change the configuration to be the same as the network planning.
a. Select Configuration Management→Managed Element→Device→Rack
Graph from the menu. The Rack Graph dialog box is displayed. Set the
board type or RRU type to be the same as the network planning based on the
rack number/shelf number/slot number in the Detail Information dialog box.
c. Wait 15 minutes, and check whether the alarm has been cleared.
Yes→End.
3. Replace the board with the planned board/RRU based on the rack number/shelf
number/slot number in the Detailed Information dialog box. Refer to Components
Replacement.
Yes→End.
l The cabinet type is inconsistent with that configured in the OMC:
2-526

Chapter 2 Alarm
check whether the cabinet type matches the network planning.
Yes→Step 2.
No→Step 3.
2. Change the cabinet type to be the same as the network planning.
a. In the Configuration Management window, create an NE, and set the cabinet
type to be the same as the network planning.
b. In the Configuration Management window, upload the configuration from the
NE.
Yes→End.
3. Based on the NE information in the Detail Information dialog box, replace the
cabinet with the planned cabinet.
Yes→End.
l The physical type of the physically connected board is inconsistent with that configured
in the OMC:
check whether the physical type of the board matches the network planning.
Yes→Step 2.
No→Step 3.
2. Change the configuration to be the same as the network planning.
a. Select Configuration Management→Managed Element→Device→Shelf
(such as B8200) from the menu. The corresponding tab is displayed. Set
the board name to the planned physical board name based on the rack
Yes→End.
3. Replace the board with the planned physical board based on the rack
number/shelf number/slot number in the Detail Information dialog box. Refer to
Components Replacement.
Yes→End.
2-527

2.3.14 198092066 Failure in uncompressing the LMT software

Alarm Information
l Name: Failure in uncompressing the LMT software
Alarm Description
This alarm occurs when the LMT software fails to be decompressed to the WEB directory.
Alarm Cause
1. The LMT software is incorrect.
2. The disk space of the NE is not sufficient.
Impact
None.
None.
Action
1. Select Dynamic Management→Dynamic Command→SDR -> Device Group. The
Device Group tab is displayed. Clean the files on the disk.
2. Select Software Version Management→Upgrade Task Management. The Upgrade
Task Management tab is displayed. Download all planned software packages for the
current network.
After the status displayed in the task list is All Successful, wait 30 minutes, and check
Yes→End.
2.3.15 198092070 Initialization failure

Alarm Information
l Name: Initialization failure
2-528

Chapter 2 Alarm

Alarm Description
This alarm occurs when a hardware/software/data error occurs during initialization.
Alarm Cause
Impact
None.
All of the services operating on the board are interrupted.
Action
Select Software Version Management→Upgrade Management from the menu. The
Yes→End.
2.3.16 198092348 The board is being initialized

Alarm Information
l Name: The board is being initialized
Alarm Description
This alarm occurs when the board is rebooted and being initialized.
Alarm Cause
1. The board resetting command is executed.
2. The board is powered on.
3. The board automatically resets due to software error.
2-529

Impact
None.
The board is in initialization status, and all of the services operating on the board are
interrupted.
Action
Yes→End.
2.3.17 198092390 CPU over loading highly

Alarm Information
l Name: CPU over loading highly
Alarm Description
An alarm is given when the system has constantly detected CPU usage exceeds high
alarm threshold.
Alarm Cause
The system is in traffic peak period and the traffic is heavy.
Impact
None.
Board processing capability declines, all or some of the services on this board may be
interrupted, or the service quality may be affected.
Action
1. Check if the system is in traffic peak period.
Yes→End.
No→Step 2.
2-530

Chapter 2 Alarm
2. It is recommended to evaluate network planning in depth and optimize network

planning.
Yes→End.
2.3.18 198092391 CPU over loading

Alarm Information
l Name: CPU over loading
Alarm Description
An alarm is given when the system has constantly detected CPU usage exceeds low alarm
threshold.
Alarm Cause
The system is in traffic peak period and the traffic is heavy.
Impact
None.
Board processing capability declines, all or some of the services on this board may be
Action
1. Check if the system is in traffic peak period.
Yes→End.
No→Step 2.
2. It is recommended to evaluate network planning in depth and optimize network

planning.
Yes→End.
2-531

2.3.19 198092395 Running software rollback

Alarm Information
l Name: Running software rollback
Alarm Description
This alarm occurs when the main control board rolls back the version package.
Alarm Cause
The upgraded version package or data is incorrect.
Impact
None.
The actual running version package is inconsistent with the version package set from the
OMC.
Action
1. Select Configuration Management→Data Synchronization from the menu. The Data
Synchronization dialog box is displayed. Click the Check Parameter button, and check
whether the result is successful.
Yes→Step 3.
No→Step 2.
2. Change the related parameters in the Configuration Management window based on
the prompt information.
The Upgrade Task Management tab is displayed. Download, pre-activate, and apply
the upgrade version package.
After the status in the task list is displayed as successful, wait 30 minutes and check
whether the alarm has been cleared.
Yes→End.
2-532

Chapter 2 Alarm
2.3.20 198092396 Hot patch fault

Alarm Information
l Name: Hot patch fault
Alarm Description
This alarm occurs when the board fails to download/upload/uninstall a hot patch.
Alarm Cause
Impact
None.
The services that the board bears might be interrupted.
Action
The Upgrade Task Management tab is displayed. Re-download the target hot patch
version package.
Yes→End.
No→ Step 2.
2. Reset the board based on the rack number/shelf number/slot number in the Detail
Yes→End.
2.3.21 198092397 Failure in finding the board-related software ID

Alarm Information
l Name: Failure in finding the board-related software ID
2-533


Alarm Description
This alarm occurs when the software ID required by the controlled board cannot be found
on the main control board.
Alarm Cause
1. The configuration file on the main control board is damaged or lost.
Impact
None.
Because the software is missing, the board cannot operate properly except for hot patches
and MMC version. This may cause services that the board bears to interrupt.
Action
1. Verify that the operating software package is a fix package.
a. Select Software Version Management→Query Task Management. The Task List
tab is displayed. Create a query task, and check whether the operating software
package is a fix package (the filename ends up with the temp suffix).
Yes→Substep b.
No→Substep c.
b. Select Software Version Management→Upgrade Task Management. The Task
List tab is displayed. Re-download, pre-activate, activate, and apply the upgrade
software package.
After the status displayed in the task list is All successful, wait 30 minutes, and
Yes→End.
No→Step 2.
c. Select Software Version Management→Upgrade Task Management. The Task
List tab is displayed. Re-download all planned software packages for the current
network.
Yes→End.
No→Step 2.
2-534

Chapter 2 Alarm
Yes→End.
2.3.22 198092443 IR changeover failure

Alarm Information
l Name: IR changeover failure
Alarm Description
This alarm occurs when IR changeover fails.
Alarm Cause
IR changeover fails.
Impact
None.
Action
1. Check whether the operator fiber connection is proper.
a. Check whether the optical fiber connection is proper (for example, check whether
there is any optical fiber connection error, loose optical fiber connection, or broken
optical fiber).
Yes→Step 2.
No→Substep b.
b. Connect the optical fiber correctly.
Yes→End.
No→Step 2.
2. Check whether the optical module connection is correct.
2-535

a. Check whether the optical module connection is correct (for example, the optical
module connection is secure).
Yes→Step 3.
No→Substep b.
b. Connect the optical module correctly.
Yes→End.
No→Step 3.
3. Replace the optical fiber. Refer to Components Replacement.
Yes→End.
No→Step 4.
4. Replace the optical module. Refer to Components Replacement.
Yes→End.
2.3.23 198096551 RRU unconfigured

Alarm Information
l Name: RRU unconfigured
RRU connected to the BBU unconfigured.
Alarm Cause
1. An RRU that is not configured exists on a BBU optical interface.
2. The downlink optical interface of the last level RRU is connected to the BBU optical
interface.
Impact
None.
2-536

Chapter 2 Alarm
The RRU that is not configured cannot provide services.
Action
1. Check the additional alarm information to make sure that whether to plan the RRU
based on the network planning.
Yes→Step 2.
No→Step 3.
2. Configure the RRU based on the network planning.
a. Select Configuration Management→Managed Element→Device→Cabinet, and
configure the RRU in accordance with the additional alarm information.
Yes→End.
3. Remove the corresponding RRU in accordance with the additional alarm information.
Yes→End.
2.3.24 198096832 Line clock source fault

Alarm Information
l Name: Line clock source fault
Alarm Description
This alarm occurs when the main control board fails to detect clock signals from the clock
reference source at the line side or the quality of clock signal is poor.
Alarm Cause
1. The configured clock reference source is unavailable.
2. Cable fault.
3. Up level connected device fault.
4. Poor quality of the up level device clock.
5. Board hardware fault.
2-537

Impact
None.
The system clock is in free oscillation status. The quality of the services on this board is
affected.
Action
l Clock of BITS-2MHz is lost/Clock of BITS-2Mbps is lost/Line clock in the local board
is lost/Line clock in other board is lost:
1. Check whether the clock reference source is correct.
confirm the main control board slot (slot 1 or slot 2) configured for the
reference clock source. Select ClockDevice Set→Clock Device, check
whether the reference clock source type is the same as planned.
Yes →Step 2.
No→Substep b.
b. Delete the incorrect configuration and configure the clock reference source
correctly in accordance with the network planning.
Yes→End.
No→Step 2.
2. Check whether cables are connected properly.
a. Check whether cables are connected properly (for example, whether the port
is loose or the cable is not connected).
Yes→Step 3.
No→Substep b.
b. Connect the cables properly.
Yes→End.
No→Step 3.
3. Check the E1/T1 device on the same level.
Connect the TX to the RX of the E1/T1 device. After 15 minutes, check whether
the alarm is cleared.
2-538

Chapter 2 Alarm
Yes→Step 8.
No→Step 4.
4. Reset the SA board.
Yes→End.
No→Step 5.
5. Reset the board based on the Rack Number, Shelf Number and Slot Number
information in alarm details. Refer to Reset Boards.
Yes→End.
No→Step 6.
6. Replace the SA board. Refer to Components Replacement.
Yes→End.
No→Step 7.
Number information in alarm details. Refer to Components Replacement.
Yes→End.
No→Step 8.
8. Check whether devices on the upper level operate properly.
a. Check whether devices on the upper level (for example, switches and BITS
clock source) operate properly (whether there are alarms and whether they
are powered on).
No→Substep b.
b. Ask the corresponding maintenance personnel to remove the fault.
Yes→End.
l Clock signal quality of BITS-2MHz is poor/Clock signal quality of BITS-2Mbps is poor:
1. Ask the maintenance personnel to check whether the BITS clock source is in
locked status.
Yes→Step 3.
No→Step 2.
2-539

2. Ask the corresponding maintenance personnel to remove the fault.

Yes→End.
No→ Step 3.
Yes→End.
No→Step 4.
Yes→End.
l Signal quality of the line clock in the local board is poor/Signal quality of the line clock
in other board is poor:
1. Ask the maintenance personnel of the upper level device (for example, BSC, RNC,
or switches) to check whether the clock is in locked status.
Yes→Step 3.
No→Step 2.

Yes→End.
No→Step 3.
Yes→End.
No→Step 4.
Yes→End.
2-540

Chapter 2 Alarm
2.3.25 198096833 SyncE clock fault

Alarm Information
l Name: SyncE clock fault
Alarm Description
l The quality of synchronous Ethernet clock extracted from SSM messages is poor.
l SSM messages are lost.
l Clock signals cannot be detected.
l Quality of the clock reference source is poor.
Alarm Cause
1. The configured clock reference source is unavailable.
2. Cable fault.
3. Up level connected device fault.
4. Poor quality of the up level device clock.
5. Board hardware fault.
6. SSM packets get lost.
Impact
None.
The system clock is in free oscillation status. The quality of the services on this board is
affected.
Action
l SyncE clock is lost:
a. Check whether any related alarm exists. If the related alarm exists, remove
it based on the corresponding handling suggestion. The related alarm is as
follows:
The physical Ethernet link is broken (198098252)
2-541


Yes→End.
No→Step 2.
2. Check whether the clock reference source is correct.
a. Select Configuration Management→Managed Element -> Device→B8200,
confirm the main control board slot (slot 1 or slot 2) configured for the
reference clock source. Select ClockDevice Set→Clock Device, check
whether the reference clock source type is the same as planned.
Yes→Step 3.
No→Substep b.
b. Delete the incorrect configuration and configure the clock reference source
correctly in accordance with the network planning.
Yes→End.
No→Step 3.
Yes→End.
No→ Step 4.
4. Replace the board connected with the SyncE cable. Refer to Components Repla
cement.
Yes→ End.
l Signal quality of SyncE clock is poor:
1. Ask the maintenance personnel of the upper level transmission device to check
whether the clock of the transmission device is in locked status.
Yes →Step 3.
No→Step 2.
Yes→End.
No→Step 3.
2-542

Chapter 2 Alarm
Yes→End.
No→Step 4.
cement.
Yes→End.
l SSM message is lost:
1. Ask the maintenance personnel of the upper level transmission device to check
whether the transmission device can send SSM packets properly.
Yes→Step 3.
No →Step 2.
Yes→End.
No→Step 3.
Yes→ End.
No→Step 4.
cement.
Yes→End.
l Clock quality of previous-level device is poor/Previous level of device has wrong
configuration of master/slave GB PHY:
Ask the corresponding maintenance personnel to remove the fault.
Yes -> End.
2-543

2.3.26 198096834 1PPS+TOD clock source fault

Alarm Information
l Name: 1PPS+TOD clock source fault
Alarm Description
l The 1PPS+TOD reference source doesn't receive messages from the serial port.
l The 1PPS+TOD reference source's pulse per second (PPS) status is unavailable.
l The 1PPS+TOD reference source cannot obtain time of day (TOD) information for a
certain period.
Alarm Cause
1. The previous-level clock source is unavailable.
2. The HDMI cable connected to the previous cascading node, is in poor contact or broken.
3. The receiving baud rate is different from the sending baud rate of the previous cascading
node.
Impact
None.
Clock and frame cannot be synchronized, softswitch cannot be guaranteed, and thus the
quality of the services on the board is affected.
Action
l 1PPS+TOD reference source cannot receive messages via serial port/1PPS+TOD
backup source cannot receive messages via serial port:
1. Check the configuration of the clock reference source of this level and whether
the 1PPS+TOD output configuration of the upper level device is correct.
a. Check whether the reference clock source planned for this BTS contains the
1PPS+TOD or 1PPS+TOD.
Yes→Substep e.
No→ Substep b.
2-544

Chapter 2 Alarm
b. Select Configuration Management→Managed Element→Device→B8200,

and confirm the main control board slot (slot 1 or slot 2) configured for the
reference clock source. Select ClockDevice Set→Clock Device, and delete
1PPS+TOD or 1PPS+TOD backup clock reference source of the local BTS.
Yes→End.
e. Check whether the 1PPS+TOD output configuration of the upper level device
is the same as planned.
Yes→Step 2.
No→Substep f.
f. Ask the corresponding maintenance personnel to modify the 1PPS+TOD
output configuration to that as planned.
Yes→End.
No→Step 2
2. Check whether the 1PPS+TOD clock cable is securely connected.
Yes→Step 4
No→Step 3
Yes→End.
No→Step 4.
4. Change a cable.
Yes→End.
No→Step 5.
Yes→End.
No→Step 6.
2-545


Yes→End.
l 1PPS+TOD reference source Pulse Per Second(PPS) status is
unavailable/1PPS+TOD backup source Pulse Per Second(PPS) status is
unavailable:
1. Check whether clock-related alarms exist in the upper level device in accordance
with the network planning.
Yes→Step 2.
2. Ask the corresponding maintenance personnel to clear the alarm(s).
Yes→End.
l 1PPS+TOD reference source cannot obtain Time of Day(TOD) information for
a specific period/1PPS+TOD backup source cannot obtain Time of Day(TOD)
information for a specific period:
1. Select Configuration Management→Managed Element→Device→B8200, and
clock source. Select ClockDevice Set→Clock Device, and check the output baud
rate of the 1PPS+TOD or 1PPS+TOD backup clock reference source.
2. Check whether the baud rate configuration is the same as that of the upper level
device.
No→Step 3.
3. Modify the baud rate configuration to that of the upper level device.
Yes→End.
l 1PPS of the 1PPS+TOD reference source is lost/1PPS of the backup 1PPS+TOD
reference source is lost:
1. Check whether the 1PPS+TOD clock cable is securely connected.
Yes→Step 3.
No→Step 2.
Yes→End.
2-546

Chapter 2 Alarm
No→Step 3.
3. Change a cable.
Yes→End.
No→Step 4.
4. Reset the board in accordance with the Rack Number, Shelf Number and Slot
Number in alarm details. Refer to Reset Boards.
Yes→End.
No→Step 5.
Yes→End.
l Backplane 1PPS+TOD source cannot receive messages via serial port/1PPS of the
backplane 1PPS+TOD reference source is lost:
1. Reset the UCI board in slot 5 in this shelf (For the 3U shelf, reset the UCI board in
slot 7) in accordance with Rack Number and Shelf Number in alarm details. Refer
to Reset Boards.
Yes→ End.
No→Step 2.
2. Reset the board in accordance with the Rack Number, Shelf Number and Slot
Number in alarm details. Refer to Reset Boards.
Yes→End.
No→Step 3.
3. Replace the UCI board in slot 5 in this shelf (For the 3U shelf, replace the UCI
board in slot 7) in accordance with Rack Number and Shelf Number in alarm
Yes→End.
No→Step 4.
2-547


Yes→End.
l Backplane 1PPS+TOD source Pulse Per Second(PPS) status is unavailable:
1. Check the UCI board in slot 5 in this shelf (For the 3U shelf, check the UCI board
in slot 7) in accordance with Rack Number and Shelf Number in alarm details.
The related alarms are as follows:
2. Handle the alarms according to corresponding proposals.
3. After 15 minutes, check whether the alarm is cleared.
Yes→End.
2.3.27 198097050 Baseband unit is being initialized

Alarm Information
l Name: Baseband unit is being initialized
This alarm occurs when the baseband unit is being initialized during the restart process.
Alarm Cause
1. A user executes a dynamic command, which results in the reset of the main control
board.
2. The base station is being upgraded.
3. A software error occurs, which results in the reset of the main control board.
Impact
None.
The baseband unit is in initialization status, and the services operating on the base station
are interrupted.
2-548

Chapter 2 Alarm
Action
Yes→End.
2.3.28 198097404 Resource usage rate is too high

Alarm Information
l Name: Resource usage rate is too high
Alarm Description
This alarm occurs when resource usage rate is too high.
Alarm Cause
The resource usage rate is too high.
Impact
None.
Insufficient storage space: there is no negative influence on services.
Action
1. Select Dynamic Management→Dynamic Command→SDR -> Device Group. The
Device Group tab is displayed. Clean the files on the disk in accordance with the slot,
shelf, rack information in the Detail Information dialog box.
Yes→End.
No→Step 2.
2. Select Software Version Management→Query Task Management. The Query Task
List tab is displayed. Create a new query task. On the Package Status tab, delete the
firmware software package (type: Firmware) and backup software package (status:
Standby).
Yes→End.
2-549

2.3.29 198097510 The NE does not support the configured

parameters
Alarm Information
l Name: The NE does not support the configured parameters
Alarm Description
This alarm occurs when the NE doesn't support the configured parameters.
Alarm Cause
The configured parameters do not match with the hardware module.
Impact
None.
Optical module rate mismatch: Part of the services on this board may be interrupted or the
service quality may be affected.
Optical interface operating mode mismatch: None.
The configured transmission mode is not supported by the board: All the services on the
board may be interrupted.
The configured rate is not supported by the optical interface board: Some or all of the
services on the board may be interrupted or the service quality may be affected.
The configured clock source is not supported by the board: Some or all of the services on
the board may be interrupted or the service quality may be affected.
The configured receiver type is not supported by the board: Some or all of the services on
the board may be interrupted or the service quality may be affected.
The configured functional mode is not supported by the board: Some or all of the services
on the board may be interrupted or the service quality may be affected.
The actual link mode of the uplink transmission port of the base station is not consistent
with the configured mode: The configured link mode does not take effect, which may lead
to half-duplex transmission, packet loss and poor service quality.
Incorrect parameter configurations or failure in configuration validation: Some or all of the
2-550

Chapter 2 Alarm
The configured receiver operating mode is not supported by the board: Some or all of the
Action
details:
l Optical module rate mismatch:
1. Verify that the rate of the optical interface is configured correctly.
a. Select Configuration Management -> Managed Element→Device→Cabinet
(For example, B8200)→Optical Port Device Set-> Optical Port Device, and
check whether the rate of the optical interface is configured as planned
according to the rack number/shelf number/slot number/optical interface
number in the alarm details.
Yes→Step 2.
No→Substep b.
b. Re-configure the rate of the optical interface as planned.
Yes→End.
No→Step 2.
2. Replace the optical module with one that supports the configured rate according to
the rack number/shelf number/slot number/optical interface number in the alarm
Yes→End.
l Optical interface operating mode mismatch:
1. Verify that the operating mode of the optical interface is configured correctly.
Network→UMTS (For example)→Physical Hosting→Physical Layer Port,
and check whether the Ethernet configuration parameter is configured as
planned.
Yes→Step 2.
No→Substep b.
b. Modify the Ethernet configuration parameter as planned.
2-551

Yes→End.
2. Replace the optical module with one that supports the configured operating mode
according to the rack number/shelf number/slot number/optical interface number
in the alarm details. Refer to Components Replacement.
Yes→End.
l The configured transmission mode is not supported by the board:
1. Verify that the transmission mode of the board is configured correctly.
Network→UMTS (For example)→Physical Hosting→Physical Layer Port,
and check whether the transmission mode is configured as planned.
Yes→Step 2.
No→Substep b.
b. Modify the transmission mode as planned.
Yes→End.
No→Step 2.
2. Replace the board with one that supports the configured transmission mode
according to the rack number/shelf number/slot number in the alarm details.
Yes→End.
l The configured rate is not supported by the optical interface board:
1. Verify that the rate of the optical interface is configured correctly.
a. Select Configuration Management→Managed Element→Device→Cabinet
(For example, B8200)→Optical Port Device Set-> Optical Port Device, and
check whether the rates of all the optical interfaces are configured as planned
Yes→Step 2.
No→Substep b.
2-552

Chapter 2 Alarm

Yes→End.
No→Step 2.
2. Verify that the real board on site is configured as planned.
a. Check whether the real board on site is configured as planned according to
the rack number/shelf number/slot number in the alarm details.
Yes→Contact ZTE technical contact.
No→Substep b.
b. Replace the optical interface board with one that supports the planned rate
according to the actual network plans. Refer to Components Replacement.
Yes→End.
l The configured clock source is not supported by the board:
1. Verify that the clock reference source is configured correctly.
(For example, B8200)→ClockDevice Set→Clock Device, and check whether
the category and type of the clock reference source are configured as
planned according to the rack number/shelf number/slot number in the alarm
details.
Yes→Step 2.
No→Substep b.
b. Re-configure the clock reference source as planned.
Yes→End.
No→Step 2.
No→Substep b.
b. Replace the board with one that supports the planned clock reference source
Yes→End.
2-553


l The configured receiver type is not supported by the board:
1. Verify that the type of the GNSS receiver hardware is configured correctly.
a. Configuration Management→Managed Element→Device→Cabinet (For
example, B8200), check the main control board slot configured for the clock
reference source (slot 1 or slot 2). Select ClockDevice Set→Clock Device,
and check whether the type of the GNSS receiver hardware is configured as
planned.
Yes→Step 2.
No→Substep b.
b. Re-configure the type of the GNSS receiver hardware as planned.
Yes→End.
No→Step 2.
No→Substep b.
b. Replace the board with one that supports the planned type of the GNSS
receiver hardware according to the actual network plans. Refer to Compo
nents Replacement.
Yes→End.
l The configured functional mode is not supported by the board:
1. Verify that the functional mode of the board is configured correctly.
(For example, B8200), and check whether the functional mode of the board
is configured as planned according to the rack number/shelf number/slot
Yes→Step 2.
No→Substep b.
b. Re-configure the functional mode of the board as planned.
2-554

Chapter 2 Alarm
Yes→End.
No→Step 2.
No→Substep b.
b. Replace the board with one that supports the planned functional mode
Yes→End.
l The actual link mode of the uplink transmission port of the base station is not consistent
with the configured mode:
1. Verify that the link mode of the uplink transmission port is configured correctly.
(For example, B8200)→Ethernet Switching Device Set→Ethernet Switching
Device, and check whether the link mode of the uplink transmission port
is configured as planned according to the rack number/shelf number/slot
Yes→Step 2.
No→Substep b.
b. Re-configure the link mode of the uplink transmission port as planned.
Yes→End.
No→Step 2.
2. Contact the maintenance personnel for the peer to ensure that link mode is
Yes→End.
l Incorrect parameter configurations/failure in configuration validation:
Synchronize the configurations to the corresponding NE.
Yes→End.
2-555


l The configured receiver operating type is not supported by the board:
1. Verify that the operating mode of the receiver is configured correctly.
(For example, B8200)→GNSS Device Set→GNSS Set, and check whether
the operating mode of the receiver is configured as planned according to the
rack number/shelf number/slot number in the alarm details.
Yes→Step 2.
No→Substep b.
b. Re-configure the operating mode of the receiver as planned.
Yes→End.
No→Step 2.
No→Substep b.
b. Replace the board with one that supports the planned operating mode
Yes→End.
2.3.30 198097511 Parameter configuration error

Alarm Information
l Name: Parameter configuration error
Alarm Description
This alarm occurs when the configured parameter is incorrect.
2-556

Chapter 2 Alarm
Alarm Cause
Parameters are configured incorrectly.
Impact
None.
All the services on the board may be interrupted.
Action
details:
l No optical interface rate configured during IQ channel establishment:
1. Select Configuration Management→Managed Element→Device, and
double-click Device. The Physical View and Topology View are displayed. Verify
the slots of all the optical interface boards connected to the RRU.
2. Verify that all the optical interface boards are configured with optical interface
rates.
a. Select Configuration Management -> Managed Element→Device→Cabinet
(For example, B8200). Select Optical Port Device Set→Optical Port Device
of the verified optical interface board, and check whether the optical interface
rate is configured.
No→Substep b.
Yes→End.
l No baseband board rate configured during IQ channel establishment:
Contact the customer service center.
l The optical module protocol type of the optical interface board not matching that of
the RRU:
1. Select Configuration Management→Managed Element -> Device, and
the slots and the optical interface of the optical interface board connected to the
RRU and the corresponding RRU rack number.
2. Verify that the optical module protocol type of the optical interface board is
2-557


of the verified optical interface board, and check whether the optical module
protocol type is configured as planned.
No→Substep b.
b. Re-configure the optical module protocol type as planned.
Yes→End.
No→Step 3.
3. Verify that the optical module protocol type of the RRU is configured correctly.
of the verified RRU, and check whether the optical module protocol type is
No→Substep b.
b. Re-configure the optical module protocol type as planned.
Yes→End.
l Failure in IQ channel resource allocation:
1. Select Configuration Management→Managed Element→Device, and
the slots of all the optical interface boards connected to the RRU.
2. Verify that the rate of the optical interface is configured as planned.
of the verified optical interface board, and check whether the rate of the
optical interface is configured as planned.
Yes→Step 3.
No→Substep b.
2-558

Chapter 2 Alarm
Yes→End.
No→Step 3.
3. Verify that cells of all the wireless standards are configured as planned.
a. Select Configuration Management→Managed Element→Radio Parameter,
and check whether cells are configured as planned.
No→Substep b.
b. Select Configuration Management→Managed Element→Radio Parameter,
and modify the cell configurations as planned.
Yes→End.
l Failure in IQ channel resource configuration:
Verify that related alarms are cleared.
1. Check whether any related alarm exists. Clear any alarm according to the
The NE does not support the configured parameters (198097510) (The configured
rate is not supported by the optical interface board.)
Parameter configuration error (198097511) (The rate of the baseband board
does not match the switching rate supported by the optical interface board (local
board).)
Yes→End.
l The rate of the baseband board not matching the switching rate supported by the
optical interface board (local board):
1. Verify the slot information in the additional alarm information according to the rack
number/shelf number/slot number in the alarm details, and check whether the
board types of the slots are configured as planned.
No→Step 2.
2. Re-configure the board type as planned.
3. Synchronize the configurations to the corresponding NE.
Yes→End.
2-559


l The configured power required by the board exceeding the power supply capacity of
the PM:
1. Select Dynamic Management→Dynamic Command→SDR→Device Group,
query the power supply situation of the boards, and verify their relations.
2. Check whether the total power of the boards exceeds the power provided by
the power supply board (Refer to the power indexes described in the hardware
manual).
Yes→Step 3.
3. Verify that the board is configured as planned.
a. Check whether the board is configured as planned.

No→Substep b.
b. Re-configure the board as planned.

Yes→End.
l The number of SCTP flows mismatch:
1. Select Configuration Management→Managed Element→Transport
Network→UMTS (for example)→Signalling and Business→SCTP, and check
whether the number of outgoing/incoming flows matches the association
parameter configured on the remote-end device (for example, BSC, RNC, or
switching device).
Yes→ Contact the customer service center.

No→Step 2.
2. Select Configuration Management→Managed Element→Transport
Network→UMTS (for example)→Signalling and Business→SCTP, and modify
the number of outgoing/incoming flows on the local-end equipment to be
consistent with that configured on the remote-end device.

Yes→End.
l The optical interface rate on the local-end equipment not matching that on the
remote-end equipment:
2-560

Chapter 2 Alarm
1. Verify that the optical interface rate on the local-end equipment is configured
correctly.
(For example, B8200)→Optical Port Device Set→Optical Port Device, and
check whether the rate of the optical interface is configured as planned
Yes→Step 2.
No→Substep b.
b. Modify the rate of the optical interface as planned.
Yes→End.
No→Step 2.
2. Check the optical module installed on the remote-end equipment.
a. Check whether the maximum rate supported by the optical module installed
on the remote-end equipment is equal to or greater than the planned optical
interface rate.
No→Substep b.
b. Replace the optical module installed on the optical interface of the remote-end
equipment with one that supports the rate configured for the local-end optical
interface. Refer to Components Replacement.
Yes→End.
l The ABIS ports of both main control boards disabled:
1. Select Configuration Management→Managed Element→Device→Cabinet (for
example, B8200)→GigaBit Ethernet, and check whether the ports whose
physical port is 0 on both main control boards are configured to be disabled (The
Enable physical port or not option is set to No.) according to the rack/shelf/slot
information of the main control boards.
Yes→Step 2.
2. Configure the port whose physical port is 0 on one of the two main control boards
to be enabled (The Enable physical port or not option is set to Yes.).
2-561

Yes→End.
l The ABIS port configuration not matching the network cables connected on the
front-end:
1. Select Configuration Management→Managed Element→Device→Cabinet (for
example, B8200)→GigaBit Ethernet, and check whether the ports whose physical
port is 0 on both main control boards are configured to be enabled (The Enable
physical port or not option is set to Yes.) according to the rack number/shelf
Yes→End.
l Failure in TDM resource configuration:
Parameter configuration error (198097511) (Sub-alarm code description: The
rate of the baseband board does not match the switching rate supported by
the optical interface board (local board).)
Yes→End.
2. Verify that cells of all the wireless standards are configured as planned.
a. Select Configuration Management→Managed Element→Radio Parameter,
and check whether cells are configured as planned.
No→Substep b.

and modify the cell configurations as planned.

Yes→End.
2-562

Chapter 2 Alarm
2.3.31 198097567 Version package fault

Alarm Information
l Name: Version package fault
Alarm Description
l The software in the version package does not exist.
l The software in the version package is damaged.
l The software required by the board running does not exist in the version package.
Alarm Cause
1. The version package on the NE is incomplete (software missing or damaged).
2. The software of the version package is not downloaded to the NE.
3. The version package doesn't contain the software required by the board operation.
Impact
None.
This alarm may cause the board startup failure or the startup failure after the reset.
Services borne on the board may be interrupted.
Action
l The software in the software package is not operating properly:
1. Select Software Version Management→Query Task Management. The Task List
tab is displayed. Create a query task and execute it.
2. Determine the version number matching the information in the Remark field in
accordance with the package standard, type, and status in the query result.
3. Select Software Version Management→Upgrade Task Management. The
Upgrade Task Management tab is displayed. Re-download the software package
obtained in Step 2.
Yes→End.
2-563


l Backup or firmware software package:
1. Select Software Version Management→Query Task Management. The Task List
tab is displayed. Create a query task and execute it.
2. Determine the version number matching the information in the Remark field in
accordance with the package standard, type, and status in the query result.
3. Determine whether the corresponding software package (obtained in Step 2)
should be kept.
Yes→ Step 4.
No→Step 5.
4. Select Software Version Management -> Upgrade Task Management. The
Upgrade Task Management tab is displayed. Re-download the software package.

Yes→End.
5. Right-click the package in the query result, and select Create Delete Package
Task from the shortcut menu to delete the package.
Yes→End.
l The operating software package does not exist:
Select Software Version Management→Upgrade Task Management. The Upgrade
Task Management tab is displayed. Download all software packages planned for the
current network.
If the status displayed in the task list is All successful, wait 30 minutes, and check
Yes→End.
2.3.32 198097568 Version repository file problem

Alarm Information
l Name: Version repository file problem
2-564

Chapter 2 Alarm
This alarm is reported when a version repository is present but its file is damaged.
Alarm Cause
The repository file is damaged or missing.
Impact
None.
In load-sharing mode, the operation or replacement of the backup component may be
affected. There is no negative influence on services.
Action
Select Software Version Management→Special Task Management. The Task List tab is
displayed. Create a file repository task.
Yes→End.
2.3.33 198097604 Software runs abnormally

Alarm Information
l Name: Software runs abnormally
Alarm Description
This alarm occurs when the board, the board product process, or the sub-unit software of
the board runs abnormally.
Alarm Cause
The board software is not operating properly:
Heartbeat messages cannot be properly reported to the main control master board.
The product process is not operating properly:
The product process cannot be scheduled in time or is not operating properly, causing
heartbeat messages not to be properly reported to the management process.
2-565

The subunit software is not operating properly:

The link between the board subunit and main control unit is broken or the subunit software
is not operating properly, causing heartbeat messages not to be properly reported to the
main control unit.
Impact
None.
All services operating on the board, board subunit or product process are interrupted.
Action
l The board software is not operating properly:
a. Check whether related alarms are raised. If they are raised, Handle the
alarms in accordance with the corresponding handling suggestions. Related

198097511 Parameter configuration error
Yes→End.
No→Step 2.
2. Reset the board in accordance with the slot, shelf, and rack information in the
Yes→End.
No→Step 3.
3. Reset the board in accordance with the slot, shelf, and rack information in the
Wait 15 minutes, and check whether the alarms are cleared. Refer to Reset Boa
rds.
Yes→End.
l The product process is not operating properly:
2-566

Chapter 2 Alarm
1. Check the abnormal product process in accordance with the information in the
Remark field of the Detail Information dialog box.
Element. The corresponding tab is displayed. Reset the abnormal product
process.
Yes→End.
No→Step 3.
3. Select Software Version Management→Upgrade Task Management. The
Upgrade Task Management tab is displayed. Download, pre-activate, activate,
and apply the planned software package for the abnormal product process.
Yes→End.
l The subunit software is not operating properly:
Reset the board in accordance with the slot, shelf, and rack information in the Detail
Wait 15 minutes, and check whether the alarm is cleared. Reset Boards
Yes→End.
2.3.34 198097605 The RRU link is broken

Alarm Information
l Name: The RRU link is broken
Alarm Description
This alarm occurs when the RRU loses software heart-beat for a time longer than the
specified period.
Alarm Cause
1. The RRU works abnormally.
2. The communication link between the RRU and the main control board is faulty.
2-567

Impact
None.
The services operating on the board are interrupted.
Action
1. Verify that related alarms are not raised on the RRU and its upper-level board.
a. Select Configuration Management -> Rack Graph→Topology View (or select
Configuration Management -> Rack Graph→Physical View). The corresponding
tab is displayed. View the slot, shelf, and rack information of the RRU (where the
alarms are raised) and its upper-level board.
b. Check whether the alarms are raised on the RRU and its upper-level board. If
related alarms are raised, resolve the faults in accordance with the corresponding
handling suggestions. Related alarms are as follows:
198092057 The board is powered off
198092072 The board is not in position
198092203 The board is not configured
198092348 The board is being initialized
198092017 Software loading failure
198092070 Initialization failure
198092289 The optical module is not in position
198092292 Optical fiber connection error
198092295 Device power down
198097604 Software runs abnormally
198097060 Board communication link interrupted
c. Check whether the alarms are cleared.
Yes→End.
No→Step 2.
2-568

Chapter 2 Alarm

a. Check whether related alarms are raised. If they are raised, resolve the faults in
follows:
Yes→End.
No→Step 3.
Wait 15 minutes, and check whether the alarms are cleared. Refer to Reset Boards.
Yes→End.
No→Step 4.
Wait 15 minutes, and check whether the alarms are cleared. Refer to Reset Boards.
Yes→End.
2.3.35 198097613 LMT is logged in

Alarm Information
l Name: LMT is logged in
Alarm Description
The alarm occurs when LMT is logged in.
Alarm Cause
LMT is logged in.
Impact
None.
2-569


None.
Action
1. Check whether the connected LMT is authorized by the carrier.
Yes→End.
No→Step 2.
Element→LMT. The LMT tab is displayed. Disconnect the LMT.
Yes→End.
2.3.36 198097650 Configuration Data Loading Abnormal

Alarm Information
l Name: Configuration Data Loading Abnormal
This alarm is reported when the system loads the backup data and is powered on if the
configuration file of the active MO is damaged.
Alarm Cause
The master MO configuration file is damaged.
Impact
None.
The configuration between the front-end and back-end subsystems may not be consistent,
and the incremental synchronization or whole table synchronization should be performed
to avoid the impact on services.
2-570

Chapter 2 Alarm
Action
Select Configuration Management→Data Synchronization. The Data Synchronization
dialog box is displayed. Start an incremental synchronization or a whole table
synchronization operation.
Yes→End.
2.3.37 198097670 The system has no the available License file

Alarm Information
l Name: The system has no the available License file
The License authentication File has not been loaded to the eNodeB.
Alarm Cause
The system support capacity is limited.
Impact
The system operates in the minimum support capacity. All optional functions are disabled,
and the default capacity is provided.
Action
Please quickly load the License File to the eNodeB from the OMC.
2.3.38 198097671 The optional feature is not usable

Alarm Information
l Name: The optional feature is not usable
The optional feature is not usable for license limit.
2-571

Alarm Cause
The optional feature is not usable.
Impact
The optional feature is not usable.
Action
Please buy the feature.
2.3.39 198098464 Parameter configuration error

Alarm Information
l Name: Parameter configuration error
Alarm Description
This alarm occurs when the delivered parameters are wrong from main control board
during configuration initialization or running period.
Alarm Cause
Impact
None.
Some or all of the services on the board may be interrupted or the service quality may be
affected.
Action
l The interval between frequency points is too close/The frequency point of the carrier
exceeds the scope of the central frequency point/The frequency point of the carrier
exceeds the frequency scope of the equipment.
Verify that frequency points of the carrier are configured as planned.
1. Select Configuration Management→Managed Element→Radio Parameter, and
check whether the frequency points of the carrier are configured as planned.
2-572

Chapter 2 Alarm

No→Step 2.
modify the frequency point configurations of the carrier of the corresponding
wireless standards as planned.
4. Wait for 15 minutes, and check whether the alarm is cleared.
Yes→End.
l Failure in central frequency point configuration:
1. Verify that the central frequency point is not configured to 0.
Select Configuration Management→Managed Element→Device, and select
RRU→RF device Set→RF Port Object→Tx/Rx Device according to the rack
number/shelf number/slot number in the alarm details (Confirm whether it is a
Tx device or an Rx device). Check whether the transmitting/receiving central
frequency point is set to 0.
Yes→Step 2.
2. Verify that the frequency points of the carrier are configured as planned.
a. Select Configuration Management -> Managed Element→Radio Parameter,
and check whether the frequency points of the carrier are configured as
planned.
No→Substep b.
and modify the frequency point configurations of the carrier of the
corresponding wireless standards as planned.
Yes→End.
l Failure in power level configuration:
Verify that the attenuation level of the static power of the carrier is configured correctly.
1. Select Configuration management -> Managed Element→Radio
Parameter→GSM→GSM Cell Channel Resource, and check whether the
attenuation level of the static power of the carrier is set to 12 dB.
2-573

No→Step 2.
2. Modify the attenuation level of the static power of the carrier to 12 dB.
Yes→End.
l Failure in IQ parameter configuration:
1. Re-configure the IQ data code.
(For example, B8200), and configure the functional mode of the board to IQ
Compressed according to the rack number/shelf number/slot number in the
alarm details.
Yes→End.
No→Step 2.
2. Re-configure the rate of the optical interface.
(For example, B8200)→Optical Port Device Set→Optical Port Device,
and modify the rate of the optical interface to that supported by the RRU
Yes→End.
l Failure in carrier power configuration:
Verify that the carrier power is configured correctly.
check whether the sum of the carrier power configured for each single channel
exceeds the rated power.
Yes→Step 2.
2. Modify the carrier power to ensure that the sum of the carrier power configured
for each single channel does not exceed the rated power.
Yes→End.
2-574

Chapter 2 Alarm

l The total power exceeding the rated power:
modify the carrier power to ensure that the sum of the carrier power configured
for an RRU channel does not exceed the maximum nominal power supported by
the RRU channel.
Yes→End.
l No wireless configurations:
modify the carrier configurations to ensure that each RRU channel is configured
with at least one carrier.
Yes→End.
l Failure in configuration of wireless frequency point interference parameters:
modify the numbers of interference frequency points and interference bandwidths
to ensure that the interference frequency points are within the scope of the
frequency points supported by the RRU hardware.
Yes→End.
l Failure in delay parameter configuration:
Contact the customer service center.
l Frame header offset configuration not supported by the RRU/Frame header offset
configuration failure responded by the RRU:
1. Select Configuration Management -> Managed Element→System
Parameter→Frequency adjust configuration, and increment or reduce the
adjustment volumes for different frequency bands according to their default
values.
Yes→End.
2-575

2.3.40 198100275 RRU software version is abnormal

Alarm Information
l Name: RRU software version is abnormal
Alarm Description
This alarm occurs when the RRU fails to download or load a software/firmware version.
Alarm Cause
Download failure:
1. The RRU software version file does not exist on the BBU.
2. Software version file download timeout.
3. The software version file is excessively large.
Activation failure:
1. The RRU version file does not exist.
2. The RRU version file is damaged.
3. The software version is not compatible with the hardware version.
4. The activation fails.

5. RRU responding timeout.
Loading failure and version rollback:
1. The RRU version file is damaged.
Download file does not exist/download timeout/download file is excessively large:
1. The RRU version file does not exist.
2. Software version file download timeout.
3. The software version file is excessively large.
Impact
None.

None.
2-576

Chapter 2 Alarm
Action
1. Select Software Version Management→Upgrade Management. The Upgrade
Management tab is displayed. Re-download all version packages planned for the
current network.
Yes→End.
No→Step 2.
2. Reset the board in accordance with the Rack Number, Shelf Number, and Slot Number
in alarm details. Refer to Components Replacement.
Yes→End.
2.3.41 198100276 RRU fiber delay beyond the limit

Alarm Information
l Name: RRU fiber delay beyond the limit
Alarm Description
This alarm occurs when the RRU optical fiber delay measured by the BBU in a preset
timing advance (TA) exceeds the RRU processing range.
Alarm Cause
1. The length of the equivalent optical fiber does not meet the standard.
2. The TA value is not properly configured.
None.
All the services on the RRU may be interrupted.
Action
1. Adjust the fiber delay timing advance TA.
a. Select Configuration Management→Managed Element→Device→Cabinet (for
example, B8200)→Optical Port Device Set, and adjust the fiber delay timing
advance according to the rack number/shelf number/slot number in the alarm
2-577

details and the measured TA value in the additional alarm information in the alarm
details.
Yes→End.
No→Step 2.
2. Shorten the length of the optical fiber according to the actual requirements.
Yes→End.
2.3.42 198094411 Board configuration parameter error

Alarm Information
l Name: Board configuration parameter error
When the RRU is starting up or operating, the main-control board reports the “configuration
parameter error” alarm.
Alarm Cause
Impact
I. Board status:
Operates properly.
If the frequency point is configured incorrectly, the cell cannot provide any service. If the
maximum transmit power of the cell is configured incorrectly, the service quality of the cell
is deteriorated.
Action
1. Check the detailed information in the additional text of the alarm.
a. Check whether a receive RF configuration error exists.
Yes→Step 2.
2-578

Chapter 2 Alarm
No→Substep b.
b. Check whether a transmit RF configuration error exists.
Yes→Step 3.
No→Substep c.
c. Check whether a transmit power configuration error exists.
Yes→Step 4.

2. In Configuration Management→Radio Parameter→LTE FDD→E-UTRAN CELL,
modify “central frequency of uplink (MHz)” in the cell record form of this RRU into the
correct value, and synchronize the modified configuration to the base station side.
Check whether the alarm is cleared.
Yes→End.
3. In Configuration Management→Radio Parameter→LTE FDD→E-UTRAN CELL,
modify “central frequency of downlink (MHz)” in the cell record form of this RRU into
the correct value, and synchronize the modified configuration to the base station side.
Check whether the alarm is cleared.
Yes→End.
4. In Configuration Management→Radio Parameter→LTE FDD→Resource Interface
Configuration→Baseband Resource, find the alarmed board according to the rack ID,
shelf ID, and slot ID in detailed alarm information, modify “maximum transmit power
of baseband resources (dBm)” and “actual transmit power of baseband resources
(dBm)” the correct value, and synchronize the modified configuration to the base
station side. Check whether the alarm is cleared.
Yes→End.
2.3.43 198094418 Rule library of performance statistics hasn't been

loaded or loaded unsuccessfully
Alarm Information
l Name ： Rule library of performance statistics hasn't been loaded or loaded
unsuccessfully
l Alarm severity：Minor
2-579

Rule library of performance statistics has not been loaded from OMC to eNodeB, or
eNodeB processed it unsuccessfully after it was loaded.
Alarm Cause
1. The rule library have not been loaded.
2. The rule library fails to load.
Impact
I. Board status:
Operates properly.
There is no impact on services, but the OMC fails to collect KPI statistics.
Action
Contact technical support.
2.3.44 198094429 Optical module rate does not match

Alarm Information
l Name: Optical module rate does not match
The optical port rate configured on the OMM exceeds the rate range supported by the
optical module.
Alarm Cause
The installed optical module does not support the optical port rate configured on the OMM.
Impact
I. Board status:
Operates properly.
The link between the BBU and the RRU is disconnected. Services that are borne over the
corresponding RRU of the link are interrupted.
2-580

Chapter 2 Alarm
Action
1. Verify that the optical port rate is configured correctly.
a. In Configuration Management→Managed Element→Device→Shelf (For example,
B8200)→Optical Port Device Set→ Optical Port Device, according to the rack ID,
shelf ID, slot ID, and optical port ID in detailed alarm information, check whether
the optical port rate is configured as that planned in the existing network.
Yes→Step 2.
No→Substep b.
b. Reconfigure the optical port rate based on the network planning.
d. After 15 minutes, check whether this alarm is cleared.
Yes→End.
No→Step 2.
information, replace the optical module into one that supports the configured rate.
Yes→End.
2.3.45 198094442 Cell parameter configuration failure

Alarm Information
l Name：Cell parameter configuration failure
This alarm occurs when fail to reconfigure parameters of existing cell, and cell parameter
configuration will roll back.
Alarm Cause
The cell parameters configured on the NMS fail to pass the verification and are invalid.
The cell parameter configuration is rolled back.
Impact
I. Board status:
Operates properly.
2-581


The parameter configuration of the equipment is inconsistent with that of the NMS. There
is no impact on services.
Action
1. Check alarm details.
"Baseband parameter configure error"→Step 2.
"RNLU parameter configure error"→Step 3.

"RRU parameter configure error"→Step 4.
2. Check BPL parameters.
Service Configuration, check BPL-related parameters, and modify as required.
b. Synchronize the configuration data to the eNodeB.
c. Check whether the alarm is cleared.
Yes→End.
3. Check user plane parameters.
Service Configuration, check user plane-related parameters, and modify as
required.
Yes→End.
4. Check RRU-related parameter configuration.

FDD Cell, check RRU-related parameters (for example, frequency point) in the
cell records, and modify as required.

Yes→End.
2-582

Chapter 2 Alarm
2.3.46 198094461 Cell shutdown alarm

Alarm Information
l Name：Cell shutdown alarm
l Alarm severity：Warning
Cell is shut down by manual.
Alarm Cause
The cell is manually blocked.
Impact
I. Board status:
Operates properly.
The services in the cell are interrupted.
Action
1. Select Dynamic Management→LTE FDD→E-UTRAN FDD Cell→Start Up Cell, select
and start up the alarmed cell.
Yes→End.
2.4 Environment Alarm

2.4.1 198096400 Device temperature is high
Alarm Information
l Name: Device temperature is high
l Alarm type: Environment Alarm
2-583

Alarm Description
This alarm is reported when system detected environmental temperature is higher than
configured upper limit of device temperature.
Alarm Cause
l The air filter is blocked.
l The environmental temperature exceeds the allowed temperature range.
Impact
If the temperature is too high, the lifespan of the equipment may be affected.
The board or the system may operate abnormally. The services borne by the board
or the base station may be entirely or partially interrupted, or the services quality may
be affected.
Action
1. Verify that the air filter is not blocked.
a. Check whether the air filter is blocked.
l Yes -> Substep b.
l No -> Step 2.
b. Clear the air filter.
l Yes -> End.
l No -> Step 2.
2. Verify that the air conditioner operates properly.
a. Check whether the air conditioner operates properly (for example, check whether
the power is on, or the conditioner is operational).
l No -> Substep b.
b. Troubleshoot the air conditioner.
l Yes -> End.
2.4.2 198096491 Cabinet temperature is abnormal

Alarm Information
2-584

Chapter 2 Alarm
l Name: Cabinet temperature is abnormal

Alarm Description
This alarm is reported when the system detects the cabinet 's temperature is higher than
configured upper limit or when the system detects the cabinet's temperature is lower than
confiured lower limit.
Alarm Cause
l The fan is faulty.
l The air conditioner is faulty.
l The monitoring unit is faulty.
Impact
If the temperature is too low or too high, the lifespan of the equipment may be affected.
The board or the system may operate abnormally. The services borne by the board
or the base station may be entirely or partially interrupted, or the services quality may
be affected.
Action
a. Check whether any fan-related alarm exists. If such alarms exist, remove them
based on the corresponding handling suggestion. The related alarm is as follows:
198092069 FCE fan failure
l Yes -> End.
l No -> Step 2.
2. Verify that the air conditioner operates properly.
a. Check whether the air conditioner operates properly (for example, check whether
the power supply is proper, the cooling and heating functions are proper).
l Yes -> Step 3.
l No -> Substep b.
b. Troubleshoot the air conditioner.

l Yes -> End.
l No -> Step 3.
2-585

3. Verify that the temperature threshold of the cabinet is properly configured.

a. Select Configuration Management -> Managed Element -> Device, select FCE
-> Environment Monitoring Device in accordance with the rack number and shelf
number in the alarm information, check whether the parameters Upper limit, Lower
limit, Recovery value of upper limit alarm, and Recovery value of lower limit alarm
are configured based on the plan.
l No -> Substep b.
b. Modify the temperature threshold of the cabinet in accordance with the plan of the
existing network.
l Yes -> End.
2.4.3 198092042 The temperature at the air intake is abnormal

Alarm Information
l Name: The temperature at the air intake is abnormal
Alarm Description
This alarm occurs when the temperature at air intake is abnormal.
Alarm Cause
Overtemperature:
1. The air intake or air filter is blocked.
3. The alarm threshold related to the temperature is not properly set.
Undertemperature:
1. The ambient temperature is too low.
2. The alarm threshold related to the temperature is not properly set.
Impact
If the temperature is too low or too high, the life of the equipment will be affected.
2-586

Chapter 2 Alarm

It might cause boards or the system unable to operate properly and service performance
to degrade, and even cause the services to interrupt.
Action
1. Check the temperature threshold of the air intake.
a. Select Configuration Management→Managed Element→Device -> BBU (such as
B8200)→SA/PSA/FAB→Environment Monitoring Device. The corresponding tab
is displayed. Change the upper and lower limits of the air intake temperature to
the following default settings:
Upper limit: 50 ℃
Lower limit: -20 ℃
Yes→End.
No→Step 2.
2. Improve the ventilation conditions of the equipment room (for example, repair the air
conditioner, heat exchanger, and heater, and stop using the unnecessary high-power
and heat-producing devices).
After the ambient environment is restored, wait 15 minutes, and check whether the
alarm is cleared.
Yes→End.
No→Step 3.
3. Ensure that the air intake of the equipment is not blocked or clean the air filter.
Yes→End.
2.4.4 198092044 Door control alarm

Alarm Information
l Name: Door control alarm
Alarm Description
This alarm is reported when a door control sensor is used but the door is not closed.
2-587

Alarm Cause
set.
2. The door is not closed.
3. The cable is not correctly connected or the cable is faulty.
Impact
The devices may be lost or damaged.
If any devices are lost or damaged, all or some of the services on this base station may
be interrupted, or the service quality may be affected.
Action
Yes→Step 2.
No →Substep b.
B8200). The corresponding tab is displayed Select the dry contact, and modify the
alarm setting to be the same as that of the actually connected dry contact device
in accordance with the slot, shelf, and rack information in the Detail Information
dialog box.
Yes→End.
No→Step 2.
2. Check the door control.
a. Check whether the door control is in closed status.
Yes →Step 3.
No→Substep b.
b. Ensure that the door control is in closed status.
2-588

Chapter 2 Alarm

Yes→End.
No→Step 3.
3. Check the cable connected to the sensor.
a. Check whether the cable to the sensor is correctly connected (for example,
Yes→Substep c.
No→Substep b.
b. Re-connect the cable.
Yes→End.
No→Substep c.
Yes→Step 4.
No→Substep d.
Yes→End.
No→Step 4.
4. Replace the door control sensor.
Yes→End.
No→Step 5.
Yes→End.
No→Step 6.
acement.
Yes→End.
2-589

2.4.5 198092045 Flooding alarm

Alarm Information
l Name: Flooding alarm
Alarm Description
This alarm is reported when the flooding sensor connected at a dry contact detects a
flooding situation.
Alarm Cause
set.
2. The base station is flooded with water.
Impact
The devices may be damaged if they are flooded.
If any devices are damaged, all or some of the services on this base station may be
Action
Yes→Step 2.
No →Substep b.

2-590

Chapter 2 Alarm
Yes→End.
No→Step 2.
2. Ensure that the base station is not flooded with water.
a. Check whether the base station is flooded with water.
Yes→Substep b.
No→ Step 3.
b. Switch off the base station and drain away water. Power on the device after it is
dry.
Yes→End.
No→Step 3.
a. Check whether the cable to the sensor is correctly connected (for example,
Yes→Substep c.
No→Substep b.
Yes→End.
No→Substep c.
Yes →Step 4.
No→Substep d.
Yes→End.
No→Step 4.
4. Replace the flooded sensor.
Yes→End.
2-591

No→Step 5.
Yes→End.
No→Step 6.
Yes→End.
2.4.6 198092046 Smog alarm

Alarm Information
l Name: Smog alarm
Alarm Description
This alarm is reported when the smog sensor connected at a dry contact detects a smog
situation.
Alarm Cause
set.
2. The base station detects smoke.
Impact
If any fire hazards exist, the devices may be damaged.
2-592

Chapter 2 Alarm
Action
Yes→Step 2.
No →Substep b.
Yes→End.
No→Step 2.
2. Ensure that no smoke arises in the environment where the base station is located.
a. Check whether smoke arises in the environment where the base station is located.
Yes→Substep b.
No→Step 3.
b. Check whether the smoke source may potentially affect the normal operation of
the device.
Yes→Substep c.
No→Substep d.
c. Switch off the power supply of the base station. After the hidden danger of smoke
is eliminated, switch on the power supply again.
Yes→End.
No→Step 3.
d. Remove the smoke source.
Yes→End.
No→Step 3.
2-593

is secured).
Yes→Substep c.
No→Substep b.
Yes→End.
No→Substep c.
Yes→Step 4.
No→Substep d.
Yes→End.
No→Step 4.
4. Replace the smoke sensor.
Yes→End.
No→Step 5.
Yes→End.
No→Step 6.
acement.
Yes→End.
2.4.7 198092047 Infrared alarm

Alarm Information
2-594

Chapter 2 Alarm
l Name: Infrared alarm

Alarm Description
None.
Alarm Cause
set.
2. Some unauthorized persons or animals enter the equipment room.
Impact
Action
Yes→Step 2.
No →Substep b.
Yes→End.
No→Step 2.
2-595

2. Ensure that no unauthorized persons or animals enter the equipment room.

a. Check whether some persons or animals enter the equipment room.
Yes→Substep b.
No→Step 3.
b. Check whether the persons are authorized.
Yes→End.
No→Substep c.
c. Make the persons or animals leave the equipment room.
Yes→End.
No→Step 3.
is secured).
Yes→Substep c.
No→Substep b.
Yes→End.
No→Substep c.
Yes→ Step 4.
No→Substep d.
Yes→End.
No→Step 4.
4. Replace the infrared sensor.
Yes→End.
No→Step 5.
2-596

Chapter 2 Alarm
Yes→End.
No→Step 6.
Yes→End.
2.4.8 198092048 Air conditioner fault

Alarm Information
l Name: Air conditioner fault
Alarm Description
None.
Alarm Cause
3. The air conditioner is faulty.

Impact
None.

This alarm may lead to the equipment high-temperature alarm, overall system
high-temperature alarm, or system operation anomaly. Some or all of the services on this
base station or board may be blocked, and service quality may be affected.
Action

check whether the alarm status of the dry contact device is the same as the
2-597

alarm status in the really connected contact device in accordance with the Rack
Number, Shelf Number, and Slot Number in the alarm details.
Yes→Step 2.
No→Substep b.
Yes→End.
No→Step 2.
Yes→Substep c.
No→Substep b.
Yes→End.
No→ Substep c.
c. c.Check whether the dry contact cable is in good condition.
Yes→Step 3.
No→Substep d.
Yes→End.
No→Step 3.
3. Check whether the air conditioner power cable is normal.
a. Check whether the air conditioner power cable is normal (for example, whether
the connector is loose or cable is damaged).
Yes→Substep b.
No→Step 4.
b. Connect the air conditioner power cable correctly.
2-598

Chapter 2 Alarm
Yes→End.
No→Step 4.
4. Change an air conditioner.
Yes→End.
No→Step 5.
Yes→End.
No→ Step 6.
Yes→End.
2.4.9 198092053 The input voltage is abnormal

Alarm Information
l Name: The input voltage is abnormal
Alarm Description
This alarm occurs when the input voltage is abnormal.
Alarm Cause
Over voltage: The input voltage of the external power system exceeds the upper limit.
Under voltage: The input voltage of the external power system is below the lower limit.
Impact
Overvoltage may affect the lifespan of the equipment.
2-599

Undervoltage will cause the service board be powered down due to insufficient power, and
the services will be affected.
Action
Perform the following operations in accordance with the board type in the Detail Information
dialog box:
PM-type board:
1. Check the threshold setting of the DC input voltage.
a. Select Configuration Management→Managed Element→Device -> Rack Graph.
The Rack Graph tab is displayed. Select Environment Monitoring Device, and
check whether the Upper Limit, Recovery value of upper limit alarm, Lower limit,
and Recovery value of lower limit parameters of the PM board are set to the default
values (for details, refer to the MO User Guide).
Yes→Step 2.
No→Substep b.
b. Change the settings of the Upper Limit, Recovery value of upper limit alarm, Lower
limit, and Recovery value of lower limit alarm parameters of the PM board to the
default values.
Yes→End.
2. Check the input voltage of the external power system.
a. Use a multimeter or other tools to view the input voltage of the external power
system.
b. Check whether the input voltage of the external power system is larger than the
setting of the Recovery value of upper limit alarm parameter or smaller than the
setting of the Recovery value of lower limit alarm parameter.
Yes→Substep c.
c. Change the input voltage of the external power system to be smaller than the
setting of the Recovery value of upper limit alarm parameter and larger than the
setting of the Recovery value of lower limit alarm parameter.
Yes→End.
Other types of boards:
2-600

Chapter 2 Alarm
Verify that the input voltage of the external power system is within a proper range.
1. Use a multimeter or other tools to view the input voltage of the external power system.
2. Check whether the input voltage of the external power system is larger than the setting
of the Recovery value of upper limit alarm parameter or smaller than the setting of the
Recovery value of lower limit alarm parameter.
Yes→Substep c.
3. Change the input voltage of the external power system to be smaller than the setting
of the Recovery value of upper limit alarm parameter and larger than the the setting of
the Recovery value of lower limit alarm parameter.
Yes→End.
2.4.10 198092105 Embedded power Environment is

under-temperature
Alarm Information
l Name: Embedded power Environment is under-temperature
Alarm Description
This alarm occurs when the environment temperature is lower than the preset
under-temperature threshold.
Alarm Cause
1. The environment temperature is lower than the lower environment temperature
threshold.
2. The temperature sensor is faulty.

Impact
If the temperature is too low, the life of the equipment may be affected.
2-601

may be affected.
Action
1. Verify that the environment temperature is higher than the lower environment
temperature threshold.
module, and check the environment temperature.
b. Check whether the environment temperature is lower than the lower environment
temperature threshold (default: -5 ℃).
Yes→Substep c.
No→Step 2.
Yes→End.
No→Step 2.
2. Replace the temperature sensor.
Yes→End.
No→Step 3.

Yes→End.
2.4.11 198092106 Embedded power Environment is

over-temperature
Alarm Information
l Name: Embedded power Environment is over-temperature
2-602

Chapter 2 Alarm
Alarm Description
This alarm occurs when the environment temperature is higher than the preset
over-temperature threshold.
Alarm Cause
1. The environment temperature is higher than the upper environment temperature
threshold.
Impact
If the temperature is too high, the life of the equipment may be affected.
may be affected.
Action
1. Verify that the environment temperature is lower than the upper environment
temperature threshold.
module, and check the environment temperature.
b. Check whether the environment temperature is higher than the upper environment
temperature threshold (default: 45 ℃).
Yes→Substep c.
No→Step 2.
Yes→End.
No→Step 2.
Yes→End.
No→Step 3.
2-603

Yes→End.
2.4.12 198092107 Embedded power Environment temperature is

invalid
Alarm Information
l Name: Embedded power Environment temperature is invalid
Alarm Description
This alarm occurs if the environment temperature is an invalid value.
Alarm Cause
1. The temperature sensor is not properly connected.
Impact
If the temperature is too low or too high, the life of the equipment will be affected.
If the temperature is too low or too high, all or some of the services on this base station
may be interrupted or the service quality may be affected.
Action
1. Verify that the temperature sensor is properly connected.
a. Check whether the temperature sensor is properly connected.
Yes→Step 2.
No→Substep b.
b. Reconnect the temperature sensor.
Yes→End.
No→Step 2.
2-604

Chapter 2 Alarm

Yes→End.
No→Step 3.
Yes→Step 4.
No→Substep b.
Yes→End.
No→ Step 4.
Yes→End.
2.4.13 198092108 Embedded power Environment is under-Humidity

Alarm Information
l Name: Embedded power Environment is under-Humidity
Alarm Description
This alarm occurs when the environment humidity is lower than the preset under-humidity
threshold.
Alarm Cause
1. The environment humidity is lower than the lower environment humidity threshold.
2. The humidity sensor is faulty.
Impact
The anti-static capability of the power supply declines, which is likely to cause damages
to devices and components.
2-605


may be affected.
Action
1. Verify that the environment humidity is higher than the lower environment humidity
threshold.
module, and check the environment humidity.
b. Check whether the environment humidity is lower than the lower environment
humidity threshold (default: 20%).
Yes→Step 2.
No→Step 3.
2. Improve the ventilation (for example, ensuring the proper functioning of air
conditioners).

Yes→End.
No→Step 3.
3. Replace the humidity sensor.
Yes→End.
No→Step 4.
Yes→ End.
2.4.14 198092109 Embedded power Environment is over-Humidity

Alarm Information
l Name: Embedded power Environment is over-Humidity
2-606

Chapter 2 Alarm
Alarm Description
This alarm occurs when the environment humidity is higher than the preset over-humidity
threshold.
Alarm Cause
1. The environment humidity is higher than the upper environment humidity threshold.
Impact
The anti-insulation and crush-resistance capability of the power supply declines, and the
devices may be easily corroded by moisture.
may be affected.
Action
1. Verify that the environment humidity is lower than the upper environment humidity
threshold.
module, and check the environment humidity.
b. Check whether the environment humidity is higher than the upper environment
humidity threshold (default: 90%).
Yes→Step 2.
No→Step 3.
2. Improve the ventilation (for example, ensuring the proper functioning of air
conditioners).
Yes→End.
No→Step 3.
Yes→End.
No→Step 4.
2-607

Yes→ End.
2.4.15 198092110 Embedded power Environment humidity is invalid

Alarm Information
l Name: Embedded power Environment humidity is invalid
Alarm Description
This alarm occurs if the environment humidity is an invalid value.
Alarm Cause
1. The humidity sensor is not properly connected.
Impact
If the humidity is too high, the anti-insulation and crush-resistance capability of the power
supply may decline. In this case, the devices may be easily corroded by moisture. If the
humidity is too low, the anti-static capability of the power supply may decline. In this case,
the devices may be easily damaged.
If the humidity is too low or too high, all or some of the services on this base station may
Action
1. Verify that the humidity sensor is properly connected.
a. Check whether the humidity sensor is properly connected.
Yes→Step 2.
No→Substep b.
b. Reconnect the humidity sensor.
Yes→End.
No→Step 2.
2-608

Chapter 2 Alarm

Yes→End.
No→Step 3.
Yes→Step 4.
No→Substep b.
b. Connect the monitoring unit properly. After 15 minutes, check whether the alarm
is cleared.
Yes→End.
No→ Step 4.
Yes→End.
2.4.16 198092111 Embedded power Smoke detected

Alarm Information
l Name: Embedded power Smoke detected
Alarm Description
This alarm occurs when the sensor detects smoke.
Alarm Cause
1. Smoke alarms are reported.
2. The smoke sensor is faulty.
Impact
If any fire hazards exist, the devices may be damaged.
2-609

Action
1. Verify that there is no smoke in the environment where devices are located.
a. Check whether there is smoke in the environment where devices are located.
Yes→Substep b.
No→Step 2.
b. Check whether there are potential risks at the smoke source that may affect the
normal operation of the devices.
Yes→Substep c.
No→Substep d.
c. Cut off the AC input of the power supply, eliminate all the smoke hazards, and
restart the power supply.
Yes→End.
No→Step 2.
d. Eliminate the smoke source.
Yes→End.
No→Step 2.
2. Replace the smoke sensor.
Yes→End.
No→Step 3.
Yes→End.
2.4.17 198092112 Embedded power Flood detected

Alarm Information
l Name: Embedded power Flood detected
2-610

Chapter 2 Alarm
Alarm Description
This alarm occurs when the sensor detects flood.
Alarm Cause
1. Flood alarms are detected.
2. The flood sensor is faulty.
Impact
The devices may be damaged if they are flooded.
Action
1. Verify that no devices are flooded.
a. Check whether there are devices flooded.

Yes→Substep b.
No→Step 2.
b. Cut off the power supply, remove the water, and restart the power supply after the
devices are dry.
Yes→End.
No→ Step 2.
2. Replace the flood sensor.

Yes→End.
No→ Step 3.

Yes→End.
2-611

2.4.18 198092113 Embedded power Door Magnet Alarm

Alarm Information
l Name: Embedded power Door Magnet Alarm
Alarm Description
This alarm occurs when the sensor detects that the door status switch of the equipment
room is opened.
Alarm Cause
1. The cabinet door is open.
2. The cable to the magnetic door switch sensor is not properly connected.
3. The magnetic door switch sensor is faulty.
4. The magnetic door switch is not properly installed.

Impact
Action
1. Check the cabinet door.
a. Check whether the cabinet door is closed.
Yes→Step 2.
No→Substep b.
b. Verify that the cabinet door is closed.

Yes→End.
No→ Step 2.
2. Check the sensor cable.
2-612

Chapter 2 Alarm
a. Check whether the sensor cable is properly connected (for example, whether the
interface connection is loose or wrong).
Yes→Substep c.
No→ Substep b.
b. Connect the sensor cable properly.
Yes→End.
No→Substep c.
c. Check whether the sensor cable is in good condition.
Yes→Step 3.
No→Substep d.
d. Replace the cable.
Yes→End.
No→Step 3.
3. Replace the magnetic door switch sensor.
Yes→End.
No→Step 4.
Yes→End.
2.4.19 198092114 Embedded power Gate Embedded power Safety

Alarm
Alarm Information
l Name: Embedded power Gate Embedded power Safety Alarm
Alarm Description
This alarm occurs when the sensor detects that the door of a cabinet with access control
is not closed.
2-613

Alarm Cause
1. The cabinet door is open.
2. The cable to the door access control sensor is not properly connected.
3. The door access control sensor is faulty.
4. The door access control switch is not properly installed.
Impact
Action
1. Check the cabinet door.
a. Check whether the cabinet door is closed.
Yes→Step 2.
No→Substep b.
b. Verify that the cabinet door is closed.
Yes→End.
No→ Step 2.
Yes→Substep c.
No→ Substep b.
Yes→End.
No→Substep c.
Yes→Step 3.
No→Substep d.
2-614

Chapter 2 Alarm

Yes→End.
No→Step 3.
3. Replace the door access control sensor.
Yes→End.
No→Step 4.
Yes→End.
2.4.20 198092115 Glass Broken Alarm

Alarm Information
l Name: Glass Broken Alarm
Alarm Description
This alarm occurs when the sensor detects that the glass is broken.
Alarm Cause
1. The alarm indicating that the glass is broken is detected.
2. The glass sensor is faulty.
Impact

2-615

Action
1. Verify that the glass of the equipment room is not damaged.
a. Check whether the glass of the equipment room is damaged.
Yes→Substep b.
No→Step 2.
b. Replace the glass.
Yes→End.
No→Step 2.
Yes→ Substep c.
No→Substep b.
Yes→End.
No→Substep c.
Yes→Step 3.
No→ Substep d.
Yes→End.
No→Step 3.
3. Replace the glass sensor.
Yes→End.
No→Step 4.
Yes→End.
2-616

Chapter 2 Alarm
2.4.21 198092118 Embedded power Env-unit communication

interruption
Alarm Information
l Name: Embedded power Env-unit communication interruption
Alarm Description
This alarm occurs when the communication of the system environment monitoring unit is
interrupted.
Alarm Cause
1. The monitoring unit is configured, but no environment monitoring board is installed.
2. The cable to the environment monitoring board is disconnected.
3. The environment monitoring board is faulty.
Impact
If the monitored environment index (such as temperature, humidity, voltage, and current)
exceeds the preset threshold, the life of the equipment may be affected.
may be affected.
Action
1. Verify that the environment monitoring board is installed.
a. Check whether the environment monitoring board is installed.
Yes→Step 2.
No→Substep b.
b. Install the environment monitoring board.
Yes→End.
No→Step 2.
2. Verify that the cable to the environment monitoring board is not disconnected or
broken.
2-617

a. Check whether the cable to the environment monitoring board is disconnected or

broken.
Yes→Substep b.
No →Step 3.
Yes→End.
No→Step 3.
Yes→Step 4.
No→Substep b.
Yes→End.
No→Step 4.
4. Replace the environment monitoring board. Refer to Components Replacement.
Yes→End.
No→ Step 5.
Yes→End.
2.4.22 198092119 Embedded power Heat Exchanger Fault

Alarm Information
l Name: Embedded power Heat Exchanger Fault
Alarm Description
This alarm occurs when the heat exchanger is damaged or the temperature is beyond the
allowed range.
2-618

Chapter 2 Alarm
Alarm Cause
1. The heat exchanger is faulty.
disconnected.
Impact
may be affected.
Action
1. Verify that the cable to the heat exchanger is not disconnected or broken.
a. Check whether the cable to the heat exchanger is disconnected or broken.
Yes→Substep b.
No→Step 2.
Yes→End.
No→ Step 2.
Yes→Step 3.
No→Substep b.
Yes→End.
No→Step 3.
3. Replace the heat exchanger. Refer to Components Replacement.
Yes→End.
No→Step 4.
2-619


Yes→End.
2.4.23 198092462 Blocked dust proof net

Alarm Information
l Name: Blocked dust proof net
Alarm Description
This alarm is reported when dust proof net is blocked.
Alarm Cause
set.
3. The air filter is blocked.
Impact
The temperature inside the cabinet increases, causing services to be affected.
Action
1. Check the settings of the dry contact device.
Yes→Step 2.
No→Substep b.
B8200). The corresponding tab is displayed. Modify the alarm status of the dry
contact to be the same as that of the actually connected dry contact device in
2-620

Chapter 2 Alarm
accordance with the slot, shelf, and rack information in the Detail Information
dialog box.
Yes→End.
No→Step 2.
is secured).
Yes→Substep c.
No→Substep b.

Yes→End.
No→Substep c.
Yes→Step 3.
No→Substep d.
Yes→End.
No →Step 3.
3. Clean the air filter.

Yes→End.
2.4.24 198097061 Temperature abnormal

Alarm Information
l Name: Temperature abnormal
2-621

Alarm Description
This alarm occurs when the board temperature is higher than the over temperature
threshold.
Alarm Cause
1. The environmental temperature exceeds the threshold.
2. The air intake or filter is blocked.
3. fan fault.
Impact
Action
198098111 Fan failure
Yes→End.
No→Step 2.
2. Check the temperature threshold of the air intake.
a. Select Configuration Management→Managed Element ->
Device→B8200→SA/PSA/FAB→Environment Monitoring Device, and set the
upper and lower temperature thresholds of the air intake to the default values.
The default values are as follows:
Upper threshold: 50 ℃
Lower threshold: -20 ℃
Yes→End.
No→ Step 3.
3. Improve the ventilation (for example, troubleshooting air conditioner faults and heating
device faults).
2-622

Chapter 2 Alarm
Yes→End.
No→Step 4.
4. Clean the air intake and the filter.
Yes→End.
2.4.25 198098128 Power over-loaded

Alarm Information
l Name: Power over-loaded
Alarm Description
This alarm occurs when the load power exceeds the preset threshold.
Alarm Cause
1. The configured power approximates or even exceeds the maximum power supported
by the PM board.
2. The board is damaged.
Impact
None.
All boards are powered off, and services on this base station are blocked.
Action
1. Check whether the configurations of the board are the same as planned.
check whether the configurations of the load board are the same as planned.
Yes→Step 2.
No→Substep b.
b. Modify the configurations to those as planned.
2-623


Yes→End.
No→Step 2.
2. Check whether the configurations of the power board are the same as planned.
check whether the configurations of the power board are the same as planned.
Yes→Step 3.
No→Substep b.
b. Modify the configurations to those as planned.
c. Synchronize the configurations to the corresponding NE, and ensure that the
configurations are the same as planned.
Yes→End.
No→Step 2.
3. Replace the power board. Refer to Components Replacement.
Yes→End.
2.4.26 198092550~198092599 Battery pack fan failed.

Alarm Information
l Alarm code: 198092550~198092599
l Name: Battery pack fan failed.
Alarm Description
This alarm is reported when the battery pack fan stops.
Alarm Cause
3. The fan of the battery does not operate.
Impact
2-624

Chapter 2 Alarm
The temperature of the battery may be excessively high after long time operation, which
reduces the life of the battery.
If the high temperature affects power supply, all the services on the base station are
blocked.
Action
Shelf Number, and Slot Number in alarm details.
Yes→Step 2.
No→Substep b.
Yes→End.
No→Step 2.
Yes→Substep c.
No→Substep b.
Yes→End.
No→ Substep c.
Yes→Step 3.
No→Substep d.
2-625

Yes→End.
No→Step 3.
3. Verify that the fan operates.
a. Check whether the fan operates.
Yes→Substep b.
No→Step 4.
b. Replace the fan.
Yes→End.
No→Step 4.
details.
Yes→ End.
No→Step 5.
Slot Number in alarm details.
Yes→End.
No→Step 6.
ment.
Yes→End.
2.5 QoS Alarm

2.5.1 198093817 Clock has significant alarm
Alarm Information
l Name: Clock has significant alarm
l Alarm type: Qos Alarm
2-626

Chapter 2 Alarm
Alarm Description
A major clock alarm.
Alarm Cause
l The active main control board is reset.
l The active main control board is faulty.
Impact
None.
The clock module is abnormal. The services borne on the board may be entirely or
Action
1. Verify that the active main control board was never reset.
a. Select Dynamic Management from the menu. The Dynamic Management page
is displayed. Select Dynamic Command -> SDR -> Device Group from the
navigation tree, run the Query Board command, and then check the slot of the
active main control board.
b. Select Alarm Monitoring -> History Alarms. Check whether any related historical
alarm exists on the active main control board within five minutes around the time
when this alarm is generated. The related alarm is as follows:
198096477 Board reboots
l Yes -> Substep c.
l No -> Step 2.
l Yes -> End.
l No -> Step 2.
2. Check whether the active main control board is faulty.
a. Select Alarm Monitoring -> History Alarms, check whether any related alarm exists
on the active main control board in accordance with the slot of the active main
control board. The related alarm is as follows:
198093814 Clock has a critical alarm

l No -> Substep b.
l No -> Step 3.
b. Reset the active main control board. Refer to Reset Boards.
2-627


l Yes -> End.
l No -> Substep c.
c. Remove and install the active main control board.
l Yes -> End.
l No -> Step 3.
l Yes -> End.
l No -> Step 4.
4. Remove and install the board in accordance with the rack number, shelf number and
slot number displayed in the alarm information.
l Yes -> End.
2.5.2 198094025 Cell finds no traffic

Alarm Information
l Name: Cell finds no traffic
Alarm Description
This alarm is reported when, for a period of time, low RL setup successful ratio or low RL
recovery ratio is detected, or few correct RACH packets are received.
Alarm Cause
l The services on the baseband process board are abnormal.
l The services on the RF board are abnormal.
Impact
None.
2-628

Chapter 2 Alarm
The baseband process board or the RF board is reset. The services borne by the
board are interrupted during board resetting.
Action
1. Select Alarm Monitoring -> History Alarms, and then check whether the alarm was
generated in the same local cell for multiple times within 48 hours in accordance with
the Local cell no. parameter in the additional alarm information.
l Yes -> Step 2.
l No -> End.
2. Query the rack number, shelf number, and slot number of the RF board in accordance
with the local cell number, and then replace the RF board.
l Yes -> End.
l No -> Step 2.
3. Query the rack number, shelf number, and slot number of the baseband process board
in accordance with the local cell number, and then replace the baseband process
board.
l Yes -> End.
2.5.3 198092368 Ethernet RDI alarm

Alarm Information
l Name: Ethernet RDI alarm
Alarm Description
This alarm occurs when data switching between Maintenance End Points (MEPs) fails.
Alarm Cause
The local Maintenance End Point (MEP) receives a Remote Defect Indication (RDI) alarm
from the opposite MEP.
Impact
None.
2-629

The Ethernet link may be broken, and services are affected.
Action
1. Ensure that the CFM parameters are correctly set.
Network→Radio Standard (such as UMTS)→Network Detection→MD/MA/MP
from the menu. The MD/MA/MP tab is displayed. Check whether the settings
of the used physical port, MD level, MD name, used Ethernet link, VLAN ID,
MA name, CCM detection duration, MEP whole network number, MEP type,
local/remote MEP detailed configuration, and CCM detection match the network
planning.
Yes→Step 2.
No→Substep b.
b. Change the settings of the CFM parameters at the local end to be the same as
the network planning.
d. Wait 15 minutes, and check whether the information in the Remark field of the
Detailed information dialog box (related to the notification that is raised again)
shows that the notification has been cleared.
Yes→End.
No→Step 2.
2. Check whether the settings of the CFM parameters of all network devices match the
network planning.
No→Change the settings to be the same as the network planning.
2.5.4 198092380 The EFM link is broken

Alarm Information
l Name: The EFM link is broken
Alarm Description
This alarm occurs when the Ethernet in the First Mile (EFM) link handshake fails.
Alarm Cause
1. The EFM parameters configured on the base station and the switch are incorrect.
2-630

Chapter 2 Alarm
2. The physical Ethernet link is not connected properly.

None.
Action
1. Ensure that the local EFM parameters are correctly set.
Network→Radio Standard (such as UMTS)→Network Detection→Ethernet
Fault Detection Configuration from the menu. The Ethernet Fault Detection
Configuration tab is displayed. Check whether the EthernetOam role, OAM
session timeout period, packet-sending interval, and the used physical-layer port
match the network planning.
Yes→Step 2.
No→Substep b.
b. Change the settings of the EFM parameters at the local end to be the same as the
network planning.
Yes→End.
No→ Step 2.
2. Ensure that the EFM parameters of the peer end are correctly set.
a. Inform the maintenance personnel of the peer device to check whether the settings
of the EFM parameters match the network planning.
Yes→Step 3.
No→Substep b.
b. Change the settings of the peer EFM parameters to be the same as the network
planning.
Yes→End.
No→Step 3.
3. Ensure that the network interface of the local device is not physically damaged.
a. Check whether the network interface of the local device is not physically damaged.
Yes→Step 4.
No→Substep b.
2-631

b. Replace the board based on the rack number/shelf number/slot number in the
Wait 30 minutes, and check whether the notification is reported again.
Yes→Step 4.
No→End.
4. Ensure that the cable connector of the local device is secured.
a. Check whether the cable connector of the local device is loose.
Yes→Substep b.
No→Step 5.
Wait 15 minutes, and check whether the notification is raised again.
Yes→Step 6.
No→End.
5. Ensure that the cable of the local device is not physically damaged.
a. Check whether the cable of the local device is not physically damaged.
Yes→Step 6.
No→Substep b.
b. Replace the cable.
Yes→Step 6.
No→End.
6. Inform the maintenance personnel of the peer device to check whether the interface,
cable, and device are operating properly.

No→Resolve the peer device fault.
2.5.5 198096837 GNSS receiver satellite searching fault

Alarm Information
l Name: GNSS receiver satellite searching fault
2-632

Chapter 2 Alarm
Alarm Description
This alarm occurs when the GNSS receiver fails to search satellites or the number of
searched satellites doesn't reach threshold.
Alarm Cause
1. The antenna and feeder are blocked by a structure.
2. Interference exists in the neighboring environment.
Impact
None.
Action
1. Check whether the antenna and feeder are blocked by a structure.
Yes→Step 2.
No→Step 3.
2. Move the antenna of the GNSS to another place or remove the structure that blocks
the signal.
Yes→End.
No→Step 3.
3. Check whether there is a GNSS interference source in the neighboring environment.
Yes→Step 4.
No→Step 5.
4. Remove the interference source.
Yes→End.
No→Step 5.
5. Replace the GNSS antenna. Refer to Components Replacement.
Yes→ End.
2-633

No→Step 6.
6. Reset the receiver.
clock source. Select ClockDevice Set→Clock Device, check whether the GNSS
receiver is UCI_RGPS.
Yes→Substep b.
No→Step 7.
b. Select Dynamic Management→Dynamic Command -> SDR→Managed Network
Element and reset the RGPS to reset the external receiver connected to this board
in accordance with Rack Number, Shelf Number, and Slot Number in alarm details.
Yes→End.
No→Step 7.
Yes→End.
No→Step 8.
Yes→End.
2.5.6 198094419 Cell outage

Alarm Information
l Name：Cell outage
l Alarm type：QoS alarm
When cell is deleted or failure is detected, this alarm is reported.
Alarm Cause
1. The S1 link is faulty.
2-634

Chapter 2 Alarm
2. The CC board, BPL board, or RRU for the cell is faulty.

3. The cell is not configured successfully.
4. The clock is unlocked.
Impact
I. Board status:
Operates properly.
Action
"Caused by S1 link fault"→Step 2.
"Caused by CC board fault"→Step 3.
"Caused by clock is unlocked"→Step 4.
"Caused by BPL board fault"→Step 5.
"Caused by RRU board fault"→Step 6.
"Caused by cell configuration fault"→Step 7.
"Cell error"→Contact technical support.
2. Check whether S1-related alarms exist.
S1 link is broken (198094420)
Yes→End.
3. Check whether CC board-related alarms exist.
corresponding handling suggestions. The related alarms are as follows:
Configuration parameter of OAM Channel is wrong (198097172)
Inter-subrack Ethernet link broken in stack mode (198092435)
Yes→End.
4. Check whether clock-related alarms exist.
2-635

eNodeB synchronization abnormal (198094829)
Yes→End.
5. Check whether BPL board-related alarms exist.
The board is powered off (198092057)
The board is not in position (198092072)
Initialization failure (198092070)
Hardware type is different from the configuration (198092029)
Software runs abnormally (198097604)
Board communication link interrupted (198097060)
Yes→End.
6. Check whether RRU-related alarms exist.
The board is powered off (198092057)
Initialization failure (198092070)
Hardware type is different from the configuration (198092029)
Software runs abnormally (198097604)
Board communication link interrupted (198097060)
The RRU link is broken (198097605)
Temperature abnormal (198098466)
Yes→End.
7. Further check alarm details.
2-636

Chapter 2 Alarm
a. Follow the alarm prompt to find and modify related configurations in Configuration
Management.
Yes→End.
2.5.7 198094422 eNodeB is out of service

Alarm Information
l Name：eNodeB is out of service
When all the cells are out of service, this alarm is reported.
Alarm Cause
All the LTE FDD cells are faulty.
Impact
I. Board status:
Operates properly.
The eNodeB fails to provide services.
Action
Handle the alarm according to the handling suggestions for the alarm "Cell outage"
(198094419). Check whether the alarm is cleared.
Yes→End.
2.5.8 198094444 PCI conflict alarm

Alarm Information
l Name：PCI conflict alarm
2-637

The physical cell ID of neighborhood cell is identical.
Alarm Cause
Two neighboring cells with the identical physical cell ID are detected during neighborhood
configuration detection for the NE.
Impact
I. Board status:
Operates properly.
UE access and handover performance within the cell's coverage may be affected.
Action
1. Check SON PCI policy information.
a. Select MO SDR SON Configuration Application→SON Management Tree→SON
Policy Management→SON Policy Query, and query the PCI policy for the alarmed
eNodeB.
b. Check whether the "Run Mode" of the PCI policy is "Free Mode".
Yes→Substep c.
No→Step 2.
c. Check whether the "Resolving PCI Conflict or Confusion at The Appointed Time
Switch" function for the PCI policy is "Open".
Yes→Substep d.
No→Substep e.
d. Check "The Appointed Time Used to Resolving PCI Conflict or Confusion". When
the time expires, check whether the alarm is cleared.
Yes→End.
e. Wait for 15 minutes. Select MO SDR SON Configuration Application→SON
Management Tree→SON Monitor Management, and check whether something
related to PCI exists.
Yes→Substep f.
No→Substep g.
2-638

Chapter 2 Alarm
f. Wait until the PCI-related information on the self optimization monitoring interface
is cleared.
g. Check whether the alarm is cleared.
Yes→End.
2. Wait in controlled mode of the PCI policy and check whether the alarm is cleared.
Yes→End.
2.5.9 198094445 PCI confusion alarm

Alarm Information
l Name：PCI confusion alarm
Two neighborhood cells of a certain cell have the identical physical cell ID configuration.
Alarm Cause
Impact
I. Board status:
Operates properly.
Action
eNodeB.
Yes→Substep c.
No→Step 2.
2-639

Yes→Substep d.
No→Substep e.
Yes→End.
Yes→Substep f.
No→Substep g.
is cleared.
Yes→End.
Yes→End.
2.5.10 198094446 MRO fault alarm

Alarm Information
l Name：MRO fault alarm
During mobile robust optimization, switch early, switch too late, switch to wrong cell,
ping-pong switch will cause this alarm.
Alarm Cause
1. Too early handover.
2. Too late handover.
2-640

Chapter 2 Alarm
3. Handover to a wrong cell.

4. Ping-pong handover.
Impact
I. Board status:
Operates properly.
UE handover performance within the cell's coverage may be affected.
Action
Check SON-related MRO policies.
1. Select MO SDR SON Configuration Application→SON Management Tree→SON
Policy Management→SON Policy Query, and query the MRO policy for the alarmed
eNodeB.
2. Wait until "Minimum interval between automatic MOR parameter optimizations" in the
MRO policy expires, and check whether the alarm is cleared.
Yes→End.
2.5.11 198094452 Different vendor PCI conflict alarm

Alarm Information
l Name：Different vendor PCI conflict alarm
The physical cell ID of neighborhood cell is identical.
Alarm Cause
Impact
I. Board status:
Operates properly.
2-641

Action
eNodeB.
Yes→Substep c.
No→Step 2.
Yes→Substep d.
No→Substep e.
Yes→End.
Yes→Substep f.
No→Substep g.
is cleared.
Yes→End.
Yes→End.
2.5.12 198094453 Different vendor PCI confusion alarm

Alarm Information
l Name：Different vendor PCI confusion alarm
2-642

Chapter 2 Alarm
Two neighborhood cells of a certain cell have the identical physical cell ID configuration.
Alarm Cause
Impact
I. Board status:
Operates properly.
Action
eNodeB.
Yes→Substep c.
No→Step 2.
Yes→Substep d.
No→Substep e.
Yes→End.
Yes→Substep f.
No→Substep g.
is cleared.
2-643

Yes→End.
Yes→End.
2.5.13 198094454 Different vendor MRO fault alarm

Alarm Information
l Name: Different vendor MRO fault alarm
l Alarm type: QoS alarm
During mobile robust optimization, switch early, switch too late, switch to wrong cell,
ping-pong switch will cause this alarm.
Alarm Cause
1. Too early handover.
2. Too late handover.
3. Handover to a wrong cell.
4. Ping-pong handover.
Impact
I. Board status:
Operates properly.
UE handover performance within the cell's coverage may be affected.
Action
Check SON-related MRO policies.
1. Select MO SDR SON Configuration Application→SON Management Tree→SON Policy
Management→SON Policy Query, and query the MRO policy for the alarmed eNodeB.
2. Wait until "Minimum interval between automatic MOR parameter optimizations" in the
MRO policy expires, and check whether the alarm is cleared.
Yes→End.
2-644

Chapter 2 Alarm
2.5.14 198094456 Cell sleeping alarm

Alarm Information
l Name：Cell sleeping alarm
The cell has no online user in detecting period.
Alarm Cause
There are no online users in the cell during detection period.
Impact
I. Board status:
Operates properly.
The cell fails to provide services.
Action
1. Check SON-related self-healing policies.
Policy Management→SON Policy Query, and query the self-healing policy for the
alarmed eNodeB.
b. Check whether the "Sleeping Cell Self-healing Enable" function for the self-healing
policy is "Open".
Yes→Step 2.
No→Step 3.
2. Wait for five minutes, and check whether the alarm is cleared.
Yes→End.
3. Delete the cell manually and re-establish a cell through the NMS.
a. Select Dynamic Management→LTE FDD→E-UTRAN FDD Cell→Immediately
Shut Down Cell, and shut down the alarmed cell.
b. Select Dynamic Management→LTE FDD→E-UTRAN FDD Cell→Start Up Cell,
2-645

Yes→End.
2.5.15 198094457 Cell performance deterioration alarm

Alarm Information
l Name：Cell performance deterioration alarm
The key performance indicator of the cell deteriorated.
Alarm Cause
The key performance indicators of the cell are deteriorated, such as RRC Establishment
Success Rate, E-RAB Setup Success Rate, and E-RAB Drop rate.
Impact
I. Board status:
Operates properly.
The service quality in the cell is degraded.
Action
1. Check SON-related self-healing policies.
Policy Management→SON Policy Query, and query the self-healing policy for the
alarmed eNodeB.
b. Check whether the "KPI Cell Self-healing Switch" and "Switch of Determined
Mobility Parameter Change for Outage Cell Based on KPI" functions of the
self-healing policy are "Open".
Yes→Step 2.
No→Substep c.
c. Check whether the "KPI Cell Self-healing Switch" function for the self-healing
policy is "Open".
Yes→Step 3.
No→Substep d.
2-646

Chapter 2 Alarm
d. Check whether the "Switch of Determined Mobility Parameter Change for Outage
Cell Based on KPI" function for the self-healing policy is "Open".
Yes→Step 2.
No→Step 4.
2. Wait until "The Period of Waiting for Manual Recovering Performance Fault Cell Timer"
expires and check whether the alarm is cleared.
Yes→End.
3. Wait for about an hour and check whether the alarm is cleared.
Yes→End.
4. Delete the cell manually and re-establish a cell through the NMS.
a. Select Dynamic Management→LTE FDD→E-UTRAN FDD Cell→Immediately
Shut Down Cell, and shut down the alarmed cell.
b. Select Dynamic Management→LTE FDD→E-UTRAN FDD Cell→Start Up Cell,
c. Wait for fifteen minutes, and check whether the alarm is cleared.
Yes→End.
2.5.16 198094458 Cell cooperating parameter configuration

abnormal
Alarm Information
l Name：Cell cooperating parameter configuration abnormal
The parameter configuration related with cooperating cell is abnormal.
Alarm Cause
The eNodeB detects that the configuration of some parameters for cell coordination that
must be consistent is inconsistent.
Impact
I. Board status:
2-647

Operates properly.
Cell coordination fails to function properly.
Action
1. Select Configuration Management→Cell Coordination, and check whether there are
inconsistent parameter configurations for cell coordination.
Yes→Step 2.
2. Correct parameter configurations according to the check results.
3. Synchronize the configuration data to the eNodeB.
Yes→End.
2.5.17 198094459 The system capacity will exceed the License limit
Alarm Information
l Name：The system capacity will exceed the License limit
The system capacity will exceed the License limit.
Alarm Cause
The system capacity will exceed the license limit.
Impact
I. Board status:
Operates properly.
None.
Action
1. Buy new capacity.
2-648

Chapter 2 Alarm
Yes→End.
2-649

2-650

Chapter 3
Notification
Table of Contents
198093025 Base station access notification ...............................................................3-2
198093026 RU Channel is calibrating or testing .........................................................3-3
198093063 The received optical power of the optical module is abnormal ..................3-3
198093064 Radio parameter requests timeout ...........................................................3-5
198093065 Radio parameter requests respond ..........................................................3-6
198093997 Cell deletion notification ...........................................................................3-7
198096477 Board reboots ..........................................................................................3-8
198092031 Board initialization process completes .....................................................3-9
198092033 Board power-on failed..............................................................................3-9
198092034 Bit error has been detected during E1 physical layer in the past 24
hours........................................................................................................................3-10
198092035 E1 link bit error has been detected in the past 24 hours .........................3-11
198092058 Software version recover succeed .........................................................3-12
198092059 Alarm Storm...........................................................................................3-12
198092063 Switchover completes ............................................................................3-13
198092271 Local benchmark clock unlocked ...........................................................3-14
198092312 PPP Negotiatory IP Conflict ...................................................................3-15
198092314 IP Conflict ..............................................................................................3-16
198092315 Mac Conflict...........................................................................................3-17
198092381 EFM Link has error data ........................................................................3-18
198092392 Product process fails to power on ..........................................................3-19
198092441 IR changeover successful ......................................................................3-20
198092442 No need for IR changeover ....................................................................3-20
198092444 SSCOP fault ..........................................................................................3-21
198096557 Uplink IQ link error .................................................................................3-22
198096566 RRU alarm reset ....................................................................................3-22
198097804 Um interface implements clock synchronization via software .................3-23
198097805 MP voltage abnormal .............................................................................3-24
198097806 PP voltage abnormal..............................................................................3-25
198097864 Product process power-on completes ....................................................3-26
198097865 Switchover fails......................................................................................3-27
198097866 port Active/standby switchover notification .............................................3-27
198097867 Power Amplifier (PA) switch for smart carrier power-on/off .....................3-29
198097907 Opening of Node B via USB finishes......................................................3-30
198097964 LCK indication .......................................................................................3-30
198097965 CCM Remote MEP Error........................................................................3-32
198097966 CCM Message Error ..............................................................................3-33
3-1

198097967 CCM Xconnect Error..............................................................................3-34

198097968 AIS indication.........................................................................................3-35
198098000 Unavailable POD ...................................................................................3-36
198098001 Unconfigured POD.................................................................................3-38
198098002 The License is entering to trying urgency state ......................................3-39
198098003 The license file will soon fall due ............................................................3-40
198098004 The configuration data exceeds the License limit ...................................3-40
198098316 The received optical power is abnormal .................................................3-41
198098459 Unavailable alarm of time slot turn-off function .......................................3-43
198094410 PA shutdown notification ........................................................................3-44
198094432 DSP error notification.............................................................................3-45
198094449 Cloud scheduling cell link fault ...............................................................3-46
198094450 Whole-band scanning start ....................................................................3-48
198094451 Whole-band scanning end .....................................................................3-48
198094857 The system capacity will exceed the License limit ..................................3-49
3.1 198093025 Base station access notification

Alarm Information
l Name: Base station access notification
l Alarm severity: Notification
A notification about base station access is released.
Alarm Cause
The working link of the base station is changed.
Impact
1. Board status:

2. Service impact:
The services on the base station may be interrupted temporarily.
Action
None
3-2

Chapter 3 Notification
3.2 198093026 RU Channel is calibrating or testing

Alarm Information
l Name: RU Channel is calibrating or testing
The RU channel is being calibrated or tested.
Alarm Cause
The RU cannot provide normal services during some manual operations, for example, TOC
measurement, OP training, and radio interference scanning. Some alarms are generated
on the RU, causing that the channel cannot operate properly or the keep-alive process
between the CC and the RU becomes abnormal.
Impact
1. Board status:
2. Service impact:
The corresponding channel is unavailable.
Action
3.3 198093063 The received optical power of the optical

module is abnormal
Alarm Information
l Name: The received optical power of the optical module is abnormal
3-3

This alarm is generated when the received optical power of the optical module is too low
or too high.
Alarm Cause
2. The optical module is aging.
4. The actual length of the optical fiber is longer than the length supported by the optical
module.
Impact
I. Board status:
II. Service impact:
The service performance of the cell associated to the optical port degrades.
Action
alarm details, unplug and plug the optical fiber or optical module.
2. Check whether the length of the fiber exceeds the maximum distance supported by the
optical module.
a. In the diagnosis test, test the board in accordance with the rack No., shelf No., and slot
If yes, go to substep b.
b. Check whether the fiber distance can be shortened.
If yes, go to substep d.
c. Shorten the fiber distance.
3-4

d. Replace an optical module that supports the transmission distance.

alarm details, replace the optical module.
alarm details, replace the optical fiber.

3.4 198093064 Radio parameter requests timeout

Alarm Information
l Name: Radio parameter requests timeout
Requests for radio parameters time out.
Alarm Cause
2. The GSM user plane resources are configured incorrectly or not configured.
3. The BSC version is incorrect.
4. The base station or BSC software is abnormal.
Impact
I. Board status: The board operates properly.
II. Service impact: For the initial power-on, the service will be unavailable. In other cases,
the service may be affected.
3-5

Action
1. Check whether relevant alarms exist.
1. Check whether relevant alarms exist. If yes, handle the alarms by referring to the
handling suggestions. The relevant alarm is:
Config error alarm (198093021), (remark: GSM user plane iptb resource is not configured
or configuration error.)
3. Check whether the BSC version matches the base station version by referring to the
*.**.*** Version Specification delivered with the base station version.
If yes, contact the technical support.
4. Upgrade the BSC version or base station version.
3.5 198093065 Radio parameter requests respond

Alarm Information
l Name: Radio parameter requests respond
Requests for radio parameters respond.
Alarm Cause
None
3-6

Impact
I. Board status:
II. Service impact:
There is no influence on services.
Action
None
3.6 198093997 Cell deletion notification

Alarm Information
l Name: Cell deletion notification
The system reports this notification when a cell is deleted.
Alarm Cause
1. The local cell is faulty.
2. The local cell is congested.
3. The RNC initiates a cell deletion request.
Impact
None.
All the services in the cell are interrupted.
Action
1. Check whether the local cell is faulty.
Yes -> Step 2.
No -> Step 3.
2. Verify that the RF board and the interface board operate properly.
3-7

a. Query the rack number, shelf number, and slot number of the RF board and interface
board in accordance with the local cell number.
b. Select Dynamic Management from the menu. The Dynamic Management page is
displayed. Select Dynamic Command -> SDR -> Device Group from the navigation tree,
run the Query Board command, and then check whether the RF board and the interface
board are faulty.
Yes -> Substep c.
No -> Step 3.
c. Remove the alarms on the RF board and interface board, after 15 minutes, and then
check whether the board is cleared.
Yes -> End.
No-> Step 3.
3. Check the cable connected the RNC to the NodeB.
a. Check whether the cable connected the RNC to the NodeB is loose or broken.
Yes -> Substep b.
No -> Step 2.
After 15 minutes, and check whether the notification is reported again.
No ->End.
3.7 198096477 Board reboots

Alarm Information
l Name: Board reboots
Alarm Description
This alarm happens when single board starts normally after reset.
Alarm Cause
l Reset board command is executed by user.
l The board is being rebooted.
l The board is rebooted by software error.
3-8

Impact
The board is initialized.
The services provided by this board are interrupted.
Action
Open the fault management interface and check the history alarm of the board for cause
of the board's reset. No process is required if the reset is caused by the user's operation.
3.8 198092031 Board initialization process completes

Alarm Information
l Name: Board initialization process completes
Alarm Description
This notification occurs when the board finishes powered-on process.
Alarm Cause
The board is powered.
Impact
None.
None.
Action
No action is required.
3.9 198092033 Board power-on failed

Alarm Information
l Name: Board power-on failed
3-9


Alarm Description
This notification occurs when the board fails to be powered on because basic process fails
to start or is timeout.
Alarm Cause
1. The board basic process fails to start.
2. The board basic process startup is timeout.
Impact
None.

Action
3.10 198092034 Bit error has been detected during E1

physical layer in the past 24 hours
Alarm Information
l Name: Bit error has been detected during E1 physical layer in the past 24 hours
Alarm Description
This notification occurs when error code is detected on the E1 physical layer within the
past 24 hours.
Alarm Cause
The transmission link is abnormal. The loss of the receive clock and loss of the received
carrier of the relay links, output open circuit, output overcurrent, abnormal line codes
measured in the past 24 hours exceed the thresholds.
3-10

Impact
None.
None.
Action
3.11 198092035 E1 link bit error has been detected in

the past 24 hours
Alarm Information
l Name: E1 link bit error has been detected in the past 24 hours
Alarm Description
This notification occurs when error code is detected on the E1 link within the past 24 hours.
Alarm Cause
The transmission link is abnormal. The number of error codes, the number of serious error
codes, and the number of unavailable seconds of the relay link measured in the past 24
hours exceed the thresholds.
Impact
None.
None.
Action
3-11

3.12 198092058 Software version recover succeed

Alarm Information
l Name: Software version recover succeed
Alarm Description
During the power-on process of the board, this notification occurs when the system detects
that the software version package is incorrect and successfully recovers the package.
Alarm Cause
The software package is successfully recovered.
Impact
None.
All of the peripheral boards cannot be properly started, and services cannot be processed
by these boards.
Action
Select Software Version Management→Upgrade Task Management. The Task List tab is
displayed. Download, pre-activate, activate, and apply the upgrade software package.
3.13 198092059 Alarm Storm

Alarm Information
l Name: Alarm Storm
Alarm Description
This notification occurs when the number of alarms reported within a period of time exceeds
a threshold.
3-12

Alarm Cause
The number of alarms reported during a certain period of time exceeds the preset
threshold.
Impact
None.
The alarm cannot be reported during the storm period, and the services operating on the
board may be affected.
Action
1. In the alarm monitoring window, check whether there are frequently reported alarms
(including current alarms and historical alarms) over a short period (such as two
seconds).
Yes→Step 2.
2. Handle the alarms in accordance with the corresponding handling suggestions.
3.14 198092063 Switchover completes

Alarm Information
l Name: Switchover completes
Alarm Description
This notification occurs when the board switchover is completed.
Alarm Cause
The active/standby board switchover is completed.
Impact
None.
None.
3-13

Action
3.15 198092271 Local benchmark clock unlocked

Alarm Information
l Name: Local benchmark clock unlocked
Alarm Description
This notification occurs when the PLL of the local benchmark clock loses lock.
Alarm Cause
1. The clock reference source is not configured.
2. The clock reference source is lost or the quality of the clock reference source is
decreased.
Impact
None.
If the clock accuracy of the base station does not meet 3GPP requirements, the success
rate of inter-base station handover is affected
Action
198096831 1588 clock source fault
198096832 Line clock source fault
198096833 SyncE clock fault
198096834 1PPS+TOD clock source fault
b. Wait for 30 minutes, and check whether the notification is reported again.
Yes→Step 2.
No→End.
3-14

2. Reset the board according to the rack number/shelf number/slot number in the alarm
Wait for 15 minutes, and check whether the notification is reported again.
Yes→Step 3.
No→End.
3. Replace the board according to the rack number/shelf number/slot number in the alarm
Wait for 15 minutes, and check whether the notification is reported again.
No→End.
3.16 198092312 PPP Negotiatory IP Conflict

Alarm Information
l Name: PPP Negotiatory IP Conflict
Alarm Description
If the PPP is in the IP Control Protocol (IPCP) stage, this notification occurs when the
negotiated IP address is different from the configured IP address
Alarm Cause
The base station IP obtained through the PPP negotiation with the peer end is different
from the configured address.
Impact
None.
Services may be interrupted due to the broken PPP link or failed PPP negotiation.
Action
1. Select Configuration Management→Managed Element -> Transmission
Network→Radio Standard (such as UMTS)→IP Transport -> PPP Link. The PPP
Link tab is displayed. Change the base station IP address to all zeros or to a new
IP address in accordance with the information in the Remark field of the Detail
3-15

2. Synchronize the configuration to the NE.

No→End.
3.17 198092314 IP Conflict

Alarm Information
l Name: IP Conflict
Alarm Description
This notification occurs when a base station detects that the source IP address in a
received Address Resolution Protocol (ARP) message is the same as that of the local
interface.
Alarm Cause
The IP address of the base station conflicts with that in the received ARP message.
Impact
None.
The base station may fail to communicate with the peer end properly, and transient service
interruptions occur.
Action
1. Verify that the base station IP is correctly configured.
Network→Radio Standard (such as UMTS)→IP Transport→IP Layer. The IP
Layer tab is displayed. Check whether the IP address is set in accordance with
the network planning data.
Yes→Step 2.
No→Substep b.
b. Modify the IP address in accordance with the network planning data.
3-16

d. Wait 15 minutes, and check whether the notification is raised again.

No→End.
2. Check whether the IP addresses of all devices in the network are set in accordance
with the network planning data.
No→Modify the corresponding IP addresses in accordance with the network planning
data.
3.18 198092315 Mac Conflict

Alarm Information
l Name: Mac Conflict
Alarm Description
This notification occurs when a base station detects that the source Medium Access
Control (MAC) address in a received ARP message is the same as that of the local
interface.
Alarm Cause
The MAC address of the base station conflicts with that in the received ARP message.
Impact
None.
The base station may fail to communicate with the peer end properly, and transient service
interruptions occur.
Action
1. Check whether there are physical loop connections in the network environment.
Yes→Step 2.
2. Construct the network in accordance with the network planning.
3-17


No→End.
3.19 198092381 EFM Link has error data

Alarm Information
l Name: EFM Link has error data
Alarm Description
This notification occurs when EFM detects that the link is faulty.
Alarm Cause
The EFM protocol detects incorrect data on the link.
Impact
None.
The Ethernet link may become unstable, and services are affected.
Action
1. Verify that the network interface of the local device is not damaged.
a. Check whether the network interface of the local device is not damaged.
Yes→Step 2.
No→Substep b.
b. Replace the board in accordance with the slot, shelf, and rack information in the
Yes→Step 2.
No→End.
2. Verify that the cable connector of the local device is secured.
a. Check whether the cable connector of the local device is secured.
Yes→Step 3.
No→Substep b.
3-18

b. Reconnect the cable correctly.

Yes→Step 3.
No→End.
3. Verify that the connection cable of the local device is in good condition.
a. Check whether the connection cable of the local device is in good condition.
Yes→Step 4.
No→Substep b.
b. Replace the cable with a proper one. Refer to Components Replacement.
Yes→Step 4.
No→ End.
4. Inform maintenance personnel of the peer device to check whether the interface, cable,
and device are in good condition.
No→Resolve the peer device fault.
3.20 198092392 Product process fails to power on

Alarm Information
l Name: Product process fails to power on
Alarm Description
This notification occurs when the product process fails to be started.
Alarm Cause
1. The product process fails to start.
2. The product process startup is timeout.
Impact
None.
3-19

Action
3.21 198092441 IR changeover successful

Alarm Information
l Name: IR changeover successful
Alarm Description
This notification occurs when the IR switchover succeeds.
Alarm Cause
The IR switchover succeeds.
Impact
None.
None.
Action
3.22 198092442 No need for IR changeover

Alarm Information
l Name: No need for IR changeover
Alarm Description
This notification occurs when there is no need to perform IR switchover.
3-20

Alarm Cause
There is no need to perform IR switchover.
Impact
None.
None.
Action
3.23 198092444 SSCOP fault

Alarm Information
l Name: SSCOP fault
Alarm Description
This notification occurs when data transmission becomes abnormal on the Service Specific
Connection Oriented Protocol (SSCOP) signaling link.
Alarm Cause
1. The clock of the IMA line on the base station is faulty.
2. The AAL5 PVC bandwidth configured on the base station is too small.
3. The transmission quality is poor.
Impact
None.
None.
Action
3-21

3.24 198096557 Uplink IQ link error

Alarm Information
l Name: Uplink IQ link error
Alarm Description
This notification occurs when error code is detected on the uplink IQ from the IQ switching
board to the baseband board.
Alarm Cause
The IQ link is abnormal.
Impact
None.
Services on this board may be partially blocked or the quality of services may be affected.
Action
1. Remove and then reinstall the board in accordance with the Rack Number, Shelf
Number and Slot Number in alarm details.
Yes→End.
No→Step 2.
2. Replace the board. Refer to Components Replacement.
Yes→End.
3.25 198096566 RRU alarm reset

Alarm Information
l Name: RRU alarm reset
3-22

Alarm Description
This notification occurs when an RRU resets due to a fault.
Alarm Cause
1. The DSP software system fails.
2. Internal RRU communication fails.
3. Other causes.
Impact
None.
During board resetting, all or some of the services on this board are or may be blocked,
and the quality of services may be affected.
Action
1. Check whether the alarm is raised frequently.
a. In Alarm Monitor->History Alarms, check whether the alarm is raised frequently.
Yes→Step 2
No→Substep b
b. After 15 minutes, check whether the alarm is cleared.
Yes→End.
No→Step 2
2. Replace the board. Refer to Components Replacement.
Yes→End.
3.26 198097804 Um interface implements clock

synchronization via software
Alarm Information
l Name: Um interface implements clock synchronization via software
3-23


Alarm Description
This notification occurs when the air-interface clock is being synchronized through
software.
Alarm Cause
The air interface clock is being synchronized through software.
Impact
None.
Calls may be dropped in fast mode of air-interface soft synchronization.
Action
3.27 198097805 MP voltage abnormal

Alarm Information
l Name: MP voltage abnormal
Alarm Description
This notification occurs when MP voltage is abnormal.
Alarm Cause
The management power voltage is higher than the upper threshold or lower than the low
threshold.
Impact
None.
Board power supply is affected, and the services on this board are blocked.
3-24

Action
Replace the board in accordance with the Rack Number, Shelf Number, and Slot Number
in alarm details. Refer to Components Replacement.
After 15 minutes, check whether the notification is raised again.
No→End.
3.28 198097806 PP voltage abnormal

Alarm Information
l Name: PP voltage abnormal
Alarm Description
This notification occurs when PP voltage is abnormal.
Alarm Cause
The service power voltage is higher than the upper threshold or lower than the low
threshold.
Impact
None.
Board power supply is affected, and the services on this board are blocked.
Action
1. Check whether the power board is operating in master/slave mode.
a. Select Configuration Management→Managed Element -> Device→B8200, and
check whether the power board is operating in master/slave mode. To locate the
board, check the Rack Number, Shelf Number and Slot Number information in
alarm details.
Yes →Substep b.
No→Step 2.
b. Check whether there is a switch on the front panel of the board.
Yes→Substep c.
3-25

No→Step 2.
c. Set the switch to ON.
No→End.
2. Replace the board in accordance with the Rack Number, Shelf Number, and Slot
No→End.
3.29 198097864 Product process power-on completes

Alarm Information
l Name: Product process power-on completes
Alarm Description
This notification occurs when product process is successfully powered on.
Alarm Cause
The process is powered on.
Impact
None.

None.
Action
3-26

3.30 198097865 Switchover fails

Alarm Information
l Name: Switchover fails
Alarm Description
This notification occurs when active-to-standby or standby-to-active switchover operation
fails, or the switchover condition is not satisfied.
Alarm Cause
Switching failed.
Impact
None.
None.
Action
3.31 198097866 port Active/standby switchover

notification
Alarm Information
l Name: port Active/standby switchover notification
Alarm Description
port Active/standby switchover notification
Alarm Cause
1. The cable is not properly connected to the original active port.
3-27

2. The local-end or remote-end device is abnormal.
Impact
None.
When the standby port acts as the active port, the next port switch may fail and the services
may be affected.
Action
1. Check whether the active port is set to active according to the additional alarm
information in the alarm details.
Yes -> End.
No→Step 2.
2. Verify that the cable of the active port is properly connected.
a. Check whether the cable of the active port is not secured or is broken.
Yes→Substep b.
No→Step 3.
c. Wait for 15 minutes, and check whether the notification is reported again.
Yes→Substep d.
No→Step 3.
d. Check whether the active port is set to active according to the additional alarm
Yes→End.
No→Step 3.
3. Verify that related alarms does not exist on the local-end device.
a. Check whether any related alarm exists on the local-end device. Clear any alarm
according to the corresponding handling suggestions. Related alarm is as follows:
198092380 The EFM link is broken
b. Wait for 15 minutes, and check whether the notification is reported again.
Yes→Substep c.
No→Step 4.
c. Check whether the active port is set to active according to the additional alarm
Yes→End.
3-28

No→Step 4.
4. Contact the maintenance personnel for the peer to ensure the normal operation of the
device.
a. Wait for 15 minutes, and check whether the notification is reported again.
Yes→Substep b.
b. Check whether the active port is set to active according to the additional alarm
Yes→End.
3.32 198097867 Power Amplifier (PA) switch for smart

carrier power-on/off
Alarm Information
l Name: Power Amplifier (PA) switch for smart carrier power-on/off
Alarm Description
This alarm is reported when all carriers of a channel are powered off or powered on again.
Alarm Cause
When the switch of disabling the PA during intelligent carrier power-off is set to On, all the
carriers on the channel are powered off or powered on.
Impact
None.
If the PA is disabled when the carrier is intelligently powered off, all the services on the
board are interrupted.
If the PA is enabled when the carrier is intelligently powered on, all the services on the
board are restored.
3-29

Action
1. Select Configuration Management→Managed Element→System Parameter→Power
Saving Parameter, and check whether the power-saving switch is set to On.
Yes→Step 2.
2. Select Configuration Management→Managed Element→Radio Parameter→UMTS
(for example), and check whether the carrier shutdown switch corresponding to the
RRU where the alarm is located is set to On.
Yes→End.
3.33 198097907 Opening of Node B via USB finishes

Alarm Information
l Name: Opening of Node B via USB finishes
Alarm Description
This notification occurs when a NodeB is commissioned through the USB function.
Alarm Cause
The NodeB site-opening via USB is complete.
Impact
None.
None.
Action
3.34 198097964 LCK indication

Alarm Information
3-30

l Name: LCK indication

Alarm Description
This notification occurs when the Ethernet Locked signal (ETH-LCK) function notifies the
MEP of the server layer (sublayer) to lock the data service flow.
Alarm Cause
The management flow lockout occurs at the port of the 802.1ag-compliant device.
Impact
None.
Action
1. Ensure that the CFM parameters on the local end are correctly set.
Network→Network Detection→MD/MA/MP. The corresponding tab is displayed.
Check whether the settings of the physical port, MD level, MD name, used
Ethernet link, VLAN ID, MA name, CCM detection period, MEP whole network
number, MEP type, local/remote MEP detailed configuration, and CCM detection
are set in accorance with the network planning data.
Yes→Step 2.
No→Substep b.
Modify the CFM parameters on the local end in accordance with the network
planning data.
Yes→Step 2.
No→End.
2. Check whether the CFM parameters of all devices are set in accordance with the
No→Modify the settings in accordance with the network planning data.
3-31

3.35 198097965 CCM Remote MEP Error

Alarm Information
l Name: CCM Remote MEP Error
Alarm Description
This notification occurs when the CCM detects that the remote MEP link is broken.
Alarm Cause
The remote MEP link detected by CCM is broken.
Impact
None.
The Ethernet link may become unstable, and service are affected.
Action
Yes→Step 2.
No→Substep b.
planning data.
Yes→End.
3-32

No→Step 2.
3.36 198097966 CCM Message Error

Alarm Information
l Name: CCM Message Error
Alarm Description
This notification occurs when the received CCM message is incorrect.
Alarm Cause
The parameters of the received CCM message do not match the configuration.
Impact
None.
Action
Yes→Step 2.
No→Substep b.
3-33

planning data.
Yes→End.
No→Step 2.
3.37 198097967 CCM Xconnect Error

Alarm Information
l Name: CCM Xconnect Error
Alarm Description
This notification occurs when the received CCM message is consistent with the
configuration data.
Alarm Cause
The parameters of the received CCM message do not match the configuration, but are
similar to the configuration of the peer MEP.
Impact
None.
Action
3-34


Yes→Step 2.
No→Substep b.
planning data.
Yes→End.
No→Step 2.
3.38 198097968 AIS indication

Alarm Information
l Name: AIS indication
Alarm Description
This notification occurs when the Ethernet Alarm Indication Signal (ETH-AIS) function
detects a fault at the server layer (sublayer).
Alarm Cause
The ETH-AIS function detects a fault at the server layer (sublayer).
3-35

Impact
None.
Action

are set in accordance with the network planning data.
Yes→Step 2.
No→Substep b.
planning data.
Yes→Step 2.
No→End.

3.39 198098000 Unavailable POD

Alarm Information
l Name: Unavailable POD
l Alarm type: Operation Alarm
3-36

The POD is available in the configuration table, but does not report the power information.
Alarm Cause
The number of PODs received is less than the configured value.
Impact
None.
None.
Action
1. Verify that the number of the PMU devices is configured correctly.
a. Select Configuration Management→Managed Element→System Parameter, and
check whether the number of the PMU devices connected with the base station is
Yes→Step 2.
No→Substep b.
b. Modify the number of the PMU devices connected with the base station as
planned.
d. Select Diagnosis Test→Diagnosis→External Device→Base Station Power Test,
and choose an NE to start testing.
e. Wait for 5 minutes, and check whether the notification is reported again.
Yes→Step 2.
No→End.
2. Verify that the number of the PMU devices actually connected is configured correctly.
a. Check whether the number of the PMU devices actually connected is configured
as planned.
Yes→Step 3.
No→Substep b.
b. Connect the PMU devices as planned.
c. Select Diagnosis Test→Diagnosis→External Device→Base Station Power Test,
d. Wait for 5 minutes, and check whether the notification is reported again.
Yes→Step 3.
3-37

No→End.
3. Verify that the cable of the PMU device is properly connected.
a. Check whether the cable of the PMU device is not secured or is broken.
Yes→Substep b.
No→End.
3.40 198098001 Unconfigured POD

Alarm Information
l Name: Unconfigured POD
The POD is unavailable in the configuration table, but reports the power information.
Alarm Cause
The number of PODs in the configuration table is less than that of PODs received.
Impact
None.
None.
Action
1. Verify that the number of the PMU devices is configured correctly.
a. Select Configuration Management→Managed Element→System Parameter, and
check whether the number of the PMU devices connected with the base station is
3-38

Yes→Step 2.
No→Substep b.
b. Modify the number of the PMU devices connected with the base station as
planned.
d. Select Diagnosis Test→Diagnosis→External Device→Base Station Power Test,
e. Wait for 5 minutes, and check whether the notification is reported again.
Yes→Step 2.
No→End.
2. Verify that the number of the PMU devices actually connected is configured correctly.
a. Check whether the number of the PMU devices actually connected is configured
as planned.
No→Substep b.
b. Connect the PMU devices as planned.
No→End.
3.41 198098002 The License is entering to trying

urgency state
Alarm Information
l Name: The License is entering to trying urgency state
The license urgency command is opened.
Alarm Cause
License authentication is not required for all control items in the system.
3-39

Impact
The system operates in the maximum support capacity. All optional functions are not
authenticated, and the maximum capacity is provided.
Action
3.42 198098003 The license file will soon fall due

Alarm Information
l Name: The license file will soon fall due
l Alarm type: Operation alarm
The license file will soon fall due.
Alarm Cause
Impact
Action
Please quickly appy for the new license file.
3.43 198098004 The configuration data exceeds the

License limit
Alarm Information
l Name: The configuration data exceeds the License limit
The configuration data exceeds the License limit.
3-40

Alarm Cause
The exceeding data is not invalid for configuration parameter.
Impact
The exceeding data is not invalid for configuration parameter.
Action
Please modify the exceeding configuration data.
3.44 198098316 The received optical power is abnormal

Alarm Information
l Name: The received optical power is abnormal
Alarm Description
This alarm occurs when the receiving optical power of the optical module is too low or too
high.
Alarm Cause
2. The optical module is aging.
3. The actual optical fiber length is longer than the length supported by the optical module.
Impact
None.
Action
1. Remove and re-install the fiber or optical module in accordance with the optical port,
Yes→End.
No→Step 2.
3-41

2. Check whether the fiber length exceeds the maximum distance that the optical module
supports.
distance that the optical module supports.
Yes→Substep b.
No→Step 3.
b. Check whether the fiber length can be reduced.

Yes→Substep c.
No→Substep d.
c. Reduce the fiber length.

Yes→End.
No→Step 3.
d. Replace the optical module with a proper one. Refer to Components Replaceme
nt.
Yes→End.
No →Step 4.
3. Replace the optical module in accordance with the optical port, slot, shelf, and rack
information in the Detail Information dialog box. Refer to Components Replacement.
Yes→End.
No→Step 4.
4. Replace the fiber in accordance with the optical port, slot, shelf, and rack information
in the Detail Information dialog box. Refer to Components Replacement.

Yes→End.
3-42

3.45 198098459 Unavailable alarm of time slot turn-off

function
Alarm Information
l Name: Unavailable alarm of time slot turn-off function
Alarm Description
This notification occurs when time slot turn-off function cannot be used because of some
constraints on PA hardware or status.
Alarm Cause
1. PA hardware has some constraints.
2. PA is abnormally closed.
Impact
None.
Not supported by the PA hardware: None.
PA closed abnormally: All the services on this PA are interrupted.
Action
details:
l Not supported by the PA hardware:
1. Check whether the time slot shutdown function is supported by the equipment
hardware.
No→Step 2.
2. Verify that the time slot shutdown parameters are properly configured.
a. Select Configuration Management→Managed Element→Device→RF Device
Set→RF Port Object→PA, and check whether the switch of shutting down
the PA based on time slots is closed according to the rack number/shelf
3-43

No→Substep b.
b. Disable the switch of shutting down the PA according to time slots.
Yes→End.
l PA closed abnormally:
Verify that related alarms are cleared.
1. Check whether any related alarm exists. Clear any alarm according to the
198098440 Disable PA
Yes→End.
3.46 198094410 PA shutdown notification

Alarm Information
l Name: PA shutdown notification
When the “Downlink analog power exceeds threshold”, “Antenna feeder VSWR serious
alarm” or “Over-high temperature of PA” alarm occurs, the system automatically shuts
down the PA, and reports this notification to the OMC.
Alarm Cause
The PA is shut down due to other alarms, such as “Downlink analog power exceeds
threshold”, “Antenna feeder VSWR serious alarm” and “Over-high temperature of PA”
alarms.
Impact
I. Board status:
Operates properly.
3-44

The RRU has no RF output, and all the services that the RRU bears may be interrupted.
Action
Antenna feeder VSWR serious alarm (198094404)
Over-high temperature of PA (198094406)
b. Check whether any new notification is reported.
Yes→Step 2.
No→End.
that is shut down due to power exceeding the threshold.
Wait for 10 minutes, and check whether any new notification is reported.
Yes→Contact ZTE technical support.
No→End.
3.47 198094432 DSP error notification

Alarm Information
l Name: DSP error notification
The DSP is faulty.
Alarm Cause
The DSP is faulty.
Impact
I. Board status:
The DSP is reset.
3-45

Services may be interrupted.
Action
According to the rack ID, shelf ID and slot ID in detailed alarm information, replace the
RRU.
After 30 minutes, check whether this notification is still reported..
Yes→End.
3.48 198094449 Cloud scheduling cell link fault

Alarm Information
l Name：Cloud scheduling cell link fault
l Alarm severity：Notification
Cloud scheduler can not receive the period message of a controlled cell for a long time.
Alarm Cause
1. The status of the controlled cell is abnormal.
2. The status of the cloud scheduler's CC board is abnormal.
3. The cloud scheduling function is not enabled for the controlled cell.
4. The transmission link between the cloud scheduler and the controlled cell is abnormal.
Impact
I. Board status:
Operates properly.
The alarmed cell may be back to static ICIC.
Action
1. Check whether the cloud scheduling function is enabled for the alarmed cell.
FDD→ICIC, and check whether the "Downlink ICIC Mode Select Flag" parameter
is set to "Cloud ICIC".
Yes→Step 2.
3-46

No→Substep b.
b. Modify the value of the "Downlink ICIC Mode Select Flag" parameter to "Cloud
ICIC".
c. Synchronize the configuration data to the eNodeB.
d. Wait for several seconds and check whether the notification is cleared.
Yes→End.
No→Step 2.
a. Check whether the alarms related to the alarmed cell exist. If such alarms exist,
remove them based on the corresponding handling suggestion. The related
Cell outage (198094419)
b. Wait for several seconds and check whether the notification is cleared.
Yes→End.
No→Step 3.
3. Check whether the status of the CC board and CS board of the cloud scheduler is
normal.
a. Select Dynamic Management→SDR→Query Board, and check whether the status
of the CC board and CS board is normal.
Yes→Step 4.
No→Substep b.
b. Check whether CC and CS-related alarms exist. If yes, remove them according
to corresponding handling suggestions. The related alarms are as follows:
Configuration parameter of OAM Channel is wrong (198097172)
Inter-subrack Ethernet link broken in stack mode (198092435)
c. Wait for several seconds and check whether the notification is cleared.
Yes→End.
No→Step 4.
4. Check whether the transmission between the eNodeB corresponding to the alarmed
cell and the cloud scheduler is proper.
a. Check whether the transmission link between the eNodeB corresponding to the
alarmed cell and the cloud scheduler is in good condition.
Yes→Contact technical support.
No→Substep b.
b. Remove the transmission fault.
3-47

c. Check whether the notification is cleared.

Yes→End.
3.49 198094450 Whole-band scanning start

Alarm Information
l Name: Whole-band scanning start
Whole-band scanning started.
Alarm Cause
The cell's services are interrupted because the frequency point of the cell is changed when
whole-band frequency scanning starts.
Impact
I. Board status:
Operates properly.
Action
None.
3.50 198094451 Whole-band scanning end

Alarm Information
l Name: Whole-band scanning end
Whole-band scanning ended.
3-48

Alarm Cause
The cell's services are restored because the frequency point of the cell is back to normal
when whole-band frequency scanning ends.
Impact
I. Board status:
Operates properly.
None.
Action
None.
3.51 198094857 The system capacity will exceed the

License limit
Alarm Information
l Name：The system capacity will exceed the License limit
l Alarm severity：Notification
The system capacity will exceed the License limit.
Alarm Cause
The system capacity will exceed the license limit.
Impact
I. Board status:
Operates properly.
None.
Action
1. Buy new capacity.
Yes→End.
3-49

3-50

Glossary
ALCAP
- Access Link Control Application Protocol
BER
- Bit Error Rate
BFD
- Bidirectional Forwarding Detection
CCM
- Communication Control Module
CFM
- Connectivity Fault Management
EFM
- Ethernet in the First Mile
GNSS
- Global Navigation Satellite System
HDLC
- High-level Data Link Control
IMA
- Inverse Multiplexing over ATM
LMT
- Local Maintenance Terminal
MEP
- MEG End Point
MME
- Mobility Management Entity
MRO
- Mobility Robustness Optimization
OAM
- Operation, Administration and Maintenance
PPP
- Point-to-Point Protocol
PSU
- Power Supervision Unit
PVC
- Permanent Virtual Channel

PWR
- Power
SCTP
- Stream Control Transmission Protocol
SMR
- Switching Mode Rectifier
SNTP
- Simple Network Time Protocol
SSCOP
- Service Specific Connection Oriented Protocol
TCP
- Transmission Control Protocol
VSWR
- Voltage Standing Wave Ratio
II

ZTE LTE Alarm and Notification Handling Reference

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

ZTE LTE Alarm and Notification Handling Reference

Загружено:

Авторское право:

Доступные форматы

ZXSDR UniBTS

Revision No. Revision Date Revision Reason

R1.0 2014–06–30 First Edition

Serial Number: SJ-20140610145724-023

Publishing Date: 2014-06-30（R1.0）

SJ-20140610145724-023|2014-06-30（R1.0） ZTE Proprietary and Confidential

Chapter 2 Alarm.......................................................................................... 2-1

SJ-20140610145724-023|2014-06-30（R1.0） ZTE Proprietary and Confidential

SJ-20140610145724-023|2014-06-30（R1.0） ZTE Proprietary and Confidential

SJ-20140610145724-023|2014-06-30（R1.0） ZTE Proprietary and Confidential

SJ-20140610145724-023|2014-06-30（R1.0） ZTE Proprietary and Confidential

SJ-20140610145724-023|2014-06-30（R1.0） ZTE Proprietary and Confidential

SJ-20140610145724-023|2014-06-30（R1.0） ZTE Proprietary and Confidential

SJ-20140610145724-023|2014-06-30（R1.0） ZTE Proprietary and Confidential

SJ-20140610145724-023|2014-06-30（R1.0） ZTE Proprietary and Confidential

SJ-20140610145724-023|2014-06-30（R1.0） ZTE Proprietary and Confidential

SJ-20140610145724-023|2014-06-30（R1.0） ZTE Proprietary and Confidential

SJ-20140610145724-023|2014-06-30（R1.0） ZTE Proprietary and Confidential

SJ-20140610145724-023|2014-06-30（R1.0） ZTE Proprietary and Confidential

SJ-20140610145724-023|2014-06-30（R1.0） ZTE Proprietary and Confidential

SJ-20140610145724-023|2014-06-30（R1.0） ZTE Proprietary and Confidential

What Is in This Manual

Chapter 1, Overview Introduces the concept of fault management, as

Chapter 2, Alarm Introduces ZXSDR UniBTS alarms.

Chapter 3, Notification Introduces ZXSDR UniBTS notifications.

SJ-20140610145724-023|2014-06-30（R1.0） ZTE Proprietary and Confidential

SJ-20140610145724-023|2014-06-30（R1.0） ZTE Proprietary and Confidential

1.1 Overview of Fault Management

1.2 Fault View

SJ-20140610145724-023|2014-06-30（R1.0） ZTE Proprietary and Confidential

1.3 Alarm Information Structure

In addition, the severity of a few alarms is undefined. It is up to users to define the

SJ-20140610145724-023|2014-06-30（R1.0） ZTE Proprietary and Confidential

l Wrong operation alarm: related with software or operation fault (ITU-T

1.4 Notification Information Structure

There is only one notification severity level: Notification.

SJ-20140610145724-023|2014-06-30（R1.0） ZTE Proprietary and Confidential

SJ-20140610145724-023|2014-06-30（R1.0） ZTE Proprietary and Confidential

2.1 Equipment Alarm

SJ-20140610145724-023|2014-06-30（R1.0） ZTE Proprietary and Confidential

If yes, no further action is required.

If yes, no further action is required.

If no, contact the ZTE technical support.

SJ-20140610145724-023|2014-06-30（R1.0） ZTE Proprietary and Confidential

2.1.2 198093023 GPS clock reference source lost major alarm

SJ-20140610145724-023|2014-06-30（R1.0） ZTE Proprietary and Confidential

b. Check whether the alarm is cleared.

2.1.3 198093024 GPS clock reference source lost critical alarm

SJ-20140610145724-023|2014-06-30（R1.0） ZTE Proprietary and Confidential

SJ-20140610145724-023|2014-06-30（R1.0） ZTE Proprietary and Confidential

2.1.4 198093028 E1 port of local switch is overflowing.

SJ-20140610145724-023|2014-06-30（R1.0） ZTE Proprietary and Confidential

2.1.5 198093050 The input clock of the board is abnormal.

1. The 61.44 M clock output from the CC board is faulty.

3. The timesync frame synchronization signal line of the board is faulty.

2. Service impact: The services are affected.

SJ-20140610145724-023|2014-06-30（R1.0） ZTE Proprietary and Confidential

2.1.6 198093051 Internal clock of the board is abnormal.

SJ-20140610145724-023|2014-06-30（R1.0） ZTE Proprietary and Confidential

3. The 61.44 M clock generated by the clock chip B is abnormal.

If yes, no further action is required.

If yes, no further action is required.

If no, contact the ZTE technical support.

SJ-20140610145724-023|2014-06-30（R1.0） ZTE Proprietary and Confidential