Sj-20141110151550-003-Zxsdr Uniran Tdd-Lte (v3.20.50) Alarm Handling

ZXSDR UniRAN
TD-LTE Base Station
Alarm Handling
Version: V3.20.50.31
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: 800@zte.com.cn
LEGAL INFORMATION
Copyright 2015 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
R2.2
2015-07-27
Updated Version: V3.20.50.31

Added "198098320 Optical interface reception link degraded".
Added "198097606 The PB link is broken ".
Added "198098474 RRU fan failure".
Added "198094868 The link between eNodeB and iCS is broken".
Updated "198097604 Software runs abnormally".
Updated "198094830 S1 link is broken".
Updated "198094831 X2 link is broken".
Updated "198094862 X2 link state updating notification".
R2.1
2015-04-24

Added 198097680 POE power supply abnormal.
Added 198098020 The Ethernet communication abnormal.
Added 198097174 The operator certificate fails to be obtained.
Added 198097940 LMT is logged in.
Added 198092215 Lost of synchronization
SJ-20141022095204-005|2015-07-27 (R2.2)
ZTE Proprietary and Confidential
Revision No.
Revision Date
Revision Reason
Added 198092431 The received optical power of the optical
module is abnormal
Added 198100078 Abnormal input dry contact one of built-in
power
Added 198100079 Abnormal input dry contact two of built-in
power
Added 198100080 Abnormal input dry contact three of built-in
power
Added 198100081 Abnormal input dry contact four of built-in
power
Updated 198100276 RRU fiber delay beyond the limit.
Updated 198098468 External extended device fault.
Updated 198094839 Reverse link RSSI minor alarm.
Updated 198094840 Reverse link RSSI major alarm.
Deleted 198094751 The Ethernet communication abnormal.
Deleted 198094752 POE power supply abnormal.
Deleted 198094463 Secondary cell outage.
R2.0
2015-04-09

Added 198098030 Carrier downlink data problem.
Added 198098021 High BER at the electrical port.
Added 198094863 S1 GTP-U path unavailable.
Added 198094864 X2 GTP-U path unavailable.
Added 198094865 S1 GTP-U Path link state upadating
notification.
Added 198094866 X2 GTP-U Path link state upadating
notification.
Updated 198092396 Hot patch fault.
Updated 198094861 S1 link-break statistics notification.
Updated 198094833 eNodeB is out of service.
Revision No.
Revision Date
Revision Reason
R1.1
2015-01-09

Updated 198097605 The RRU link is broken.
Updated 198096835 GNSS receiver fault.
Updated 198098440 Disable PA.
Updated 198100015 Several faulty rectifiers.
Updated 198100062 Embedded power Bat Test Failure.
R1.0
2014-10-28

First edition.
Serial Number: SJ-20141110151550-003

Publishing Date: 2015-07-27 (R2.2)
SJ-20141022095204-005|2015-07-27 (R2.2)
Contents
About This Manual ......................................................................................... I
Chapter 1 Overview .................................................................................... 1-1
Chapter 2 Processing Error Alarm............................................................ 2-1
2.1 198092014 SNTP time adjustment failure ............................................................ 2-2
2.2 198092017 Software loading failure..................................................................... 2-4
2.3 198092019 Failure in active/standby synchronization ........................................... 2-4
2.4 198092027 Failure in repairing a version package ................................................ 2-5
2.5 198092029 Hardware type is different from the configuration ................................ 2-6
2.6 198092066 Failure in uncompressing the LMT software........................................ 2-9
2.7 198092070 Initialization failure .......................................................................... 2-10
2.8 198092348 The board is being initialized ........................................................... 2-10
2.9 198092390 CPU over loading highly...................................................................2-11
2.10 198092391 CPU over loading.......................................................................... 2-12
2.11 198092395 Running software rollback.............................................................. 2-13
2.12 198092396 Hot patch fault .............................................................................. 2-14
2.13 198092397 Failure in finding the board-related software ID ............................... 2-15
2.14 198092443 IR changeover failure .................................................................... 2-16
2.15 198096551 RRU unconfigured ........................................................................ 2-17
2.16 198096832 Line clock source fault................................................................... 2-18
2.17 198096833 SyncE clock fault .......................................................................... 2-22
2.18 198096834 1PPS+TOD clock source fault........................................................ 2-24
2.19 198097050 Baseband unit is being initialized ................................................... 2-29
2.20 198097404 Resource usage rate is too high..................................................... 2-30
2.21 198097510 The NE does not support the configured parameters ...................... 2-31
2.22 198097511 Parameter configuration error ........................................................ 2-38
2.23 198097567 Version package fault.................................................................... 2-45
2.24 198097568 Version repository file problem....................................................... 2-46
2.25 198097604 Software runs abnormally .............................................................. 2-47
2.26 198097605 The RRU link is broken ................................................................ 2-49
2.27 198097606 The PB link is broken .................................................................... 2-51
2.28 198097613 LMT is logged in ........................................................................... 2-53
2.29 198097650 Configuration Data Loading Abnormal ............................................ 2-53
2.30 198097651 Configuration data unmatched with the license ............................... 2-54
I
SJ-20141022095204-005|2015-07-27 (R2.2)
2.31 198097670 The system has no the available License file .................................. 2-55
2.32 198097673 The license file will soon fall due .................................................... 2-56
2.33 198098464 Parameter configuration error ........................................................ 2-57
2.34 198100275 RRU software version is abnormal ................................................. 2-61
2.35 198100276 RRU fiber delay beyond the limit .................................................... 2-62
2.36 198094815 Rule library of performance statistics hasn't been loaded or loaded
unsuccessfully................................................................................................ 2-63
2.37 198094838 Cell parameter configuration failure................................................ 2-64
2.38 198094858 Cell shutdown alarm ..................................................................... 2-65
Chapter 3 QoS Alarm ................................................................................. 3-1

3.1 198092368 Ethernet RDI alarm ........................................................................... 3-1
3.2 198092380 The EFM link is broken ..................................................................... 3-2
3.3 198096837 GNSS receiver satellite searching fault .............................................. 3-4
3.4 198097174 The operator certificate fails to be obtained ........................................ 3-6
3.5 198097672 System capacity overload.................................................................. 3-8
3.6 198094826 PCI conflict alarm ............................................................................. 3-9
3.7 198094827 PCI confusion alarm........................................................................ 3-10
3.8 198094832 LTE cell outage............................................................................... 3-12
3.9 198094833 eNodeB is out of service ................................................................. 3-14
3.10 198094834 Wireless interference detection is abnormal.................................... 3-16
3.11 198094835 Cell portion of super cell is out of service ........................................ 3-17
3.12 198094842 MRO fault alarm ........................................................................... 3-19
3.13 198094843 Different vendor PCI conflict alarm ................................................. 3-20
3.14 198094844 Different vendor PCI confusion alarm ............................................. 3-22
3.15 198094853 Cell sleeping alarm ....................................................................... 3-23
3.16 198094854 Cell performance deterioration alarm.............................................. 3-24
3.17 198094855 Cell cooperating parameter configuration abnormal......................... 3-26
3.18 198094856 The system capacity will exceed the License limit ........................... 3-27
Chapter 4 Environment Alarm................................................................... 4-1

4.1 198092042 The temperature at the air intake is abnormal ..................................... 4-1
4.2 198092044 Door control alarm ............................................................................ 4-3
4.3 198092045 Flooding alarm ................................................................................. 4-5
4.4 198092046 Smog alarm...................................................................................... 4-7
4.5 198092047 Infrared alarm................................................................................. 4-10
4.6 198092048 Air conditioner fault ......................................................................... 4-12
4.7 198092053 The input voltage is abnormal.......................................................... 4-14
4.8 198092105 Embedded power Environment is under-temperature ........................ 4-16
II
SJ-20141022095204-005|2015-07-27 (R2.2)
4.9 198092106 Embedded power Environment is over-temperature .......................... 4-18

4.10 198092107 Embedded power Environment temperature is invalid ..................... 4-19
4.11 198092108 Embedded power Environment is under-Humidity ........................... 4-20
4.12 198092109 Embedded power Environment is over-Humidity ............................. 4-22
4.13 198092110 Embedded power Environment humidity is invalid ........................... 4-23
4.14 198092111 Embedded power Smoke detected ................................................. 4-24
4.15 198092112 Embedded power Flood detected................................................... 4-26
4.16 198092113 Embedded power Door Magnet Alarm ............................................ 4-27
4.17 198092114 Embedded power Gate Embedded power Safety Alarm................... 4-28
4.18 198092115 Glass Broken Alarm ...................................................................... 4-30
4.19 198092118 Embedded power Env-unit communication interruption.................... 4-32
4.20 198092119 Embedded power Heat Exchanger Fault......................................... 4-33
4.21 198092462 Blocked dust proof net .................................................................. 4-35
4.22 198097061 Temperature abnormal .................................................................. 4-36
4.23 198098128 Power over-loaded ....................................................................... 4-38
4.24 198092550~198092599 Battery pack fan failed. ............................................... 4-39
Chapter 5 Equipment Alarm ...................................................................... 5-1

5.1 198092049 Lightning protection device alarm....................................................... 5-3
5.2 198092051 PSU alarm ....................................................................................... 5-5
5.3 198092052 PSU fan alarm .................................................................................. 5-7
5.4 198092057 The board is powered off................................................................... 5-9
5.5 198092068 Main power supply has a fault alarm ................................................ 5-12
5.6 198092069 FCE fan failure ............................................................................... 5-14
5.7 198092071 Temperature sensor abnormal ........................................................ 5-15
5.8 198092072 The board is not in position ............................................................. 5-16
5.9 198092073 Embedded power AC-in Switch Off .................................................. 5-18
5.10 198092074 Embedded power AC Power Off .................................................... 5-20
5.11 198092075 Embedded power SPD-C Broken ................................................... 5-21
5.12 198092076 Embedded power SPD-D Broken................................................... 5-23
5.13 198092077 Embedded power AC Under-Volt ................................................... 5-25
5.14 198092078 Embedded power AC Over-Volt ..................................................... 5-27
5.15 198092082 Embedded power SMR Fan Fault .................................................. 5-28
5.16 198092083 Embedded power SMR PFC Fault ................................................. 5-30
5.17 198092084 Embedded power SMR Over-Vin Off .............................................. 5-30
5.18 198092085 Embedded power SMR Under-Vin Off ............................................ 5-31
5.19 198092086 Embedded power SMR H.T. Off ..................................................... 5-33
5.20 198092087 Embedded power SMR Env.H.T.Off................................................ 5-34
III
SJ-20141022095204-005|2015-07-27 (R2.2)
5.21 198092088 Embedded power SMR Env.H.T .................................................... 5-35

5.22 198092089 Embedded power SMR L.Vin......................................................... 5-36
5.23 198092090 Embedded power SMR Fuse Broken ............................................. 5-37
5.24 198092091 Embedded power SMR CommFail ................................................. 5-38
5.25 198092094 Embedded power DC Loop Broken ................................................ 5-40
5.26 198092095 Embedded power Bat Loop Broken................................................ 5-42
5.27 198092096 Embedded power Bat Under-Volt ................................................... 5-43
5.28 198092097 Embedded power Bat Over-Temp .................................................. 5-46
5.29 198092098 Embedded power TmpL Shut-Down............................................... 5-47
5.30 198092099 Embedded power 1st Shut-down ................................................... 5-49
5.31 198092100 Embedded power 2nd Shut-down .................................................. 5-51
5.32 198092101 Embedded power DC SPD Broken................................................. 5-53
5.33 198092102 Embedded power DC Breaker Alarm.............................................. 5-54
5.34 198092103 Embedded power Bat Test Failure ................................................. 5-56
5.35 198092117 Embedded power Rectifier Module Fault ........................................ 5-57
5.36 198092203 The board is not configured ........................................................... 5-59
5.37 198092206 Battery alarm ................................................................................ 5-60
5.38 198092207 AC power-cut alarm ...................................................................... 5-62
5.39 198092208 Rectifier module alarm .................................................................. 5-64
5.40 198092209 Thermoelectric cooler alarm .......................................................... 5-66
5.41 198092215 Lost of synchronization.................................................................. 5-68
5.42 198092217 No available clock source at air-interface........................................ 5-69
5.43 198092234 Embedded power type configuration error ...................................... 5-71
5.44 198092235 Embedded power communication interruption................................. 5-72
5.45 198092237 Embedded power Bat Under-Temp ................................................ 5-73
5.46 198092238 Embedded power Bat Invalid-Temp................................................ 5-75
5.47 198092239 Embedded power Battery Fault...................................................... 5-76
5.48 198092259 Battery low-voltage alarm .............................................................. 5-78
5.49 198092260 Faulty external device connected at a dry contact ........................... 5-80
5.50 198092261 Outdoor lightning protection box alarm ........................................... 5-82
5.51 198092262 Breaker alarm in indoor lightning protection box.............................. 5-84
5.52 198092263 Lightning protection device alarm in indoor lightning protection
box ................................................................................................................ 5-86
5.53 198092264 Over-voltage alarm of main power input ......................................... 5-88
5.54 198092265 Main power input power-cut alarm ................................................. 5-91
5.55 198092266 Under-voltage alarm of main power input ....................................... 5-93
5.56 198092267 General fault of main power........................................................... 5-95
5.57 198092268 PWR monitoring unit alarm ............................................................ 5-97
IV
SJ-20141022095204-005|2015-07-27 (R2.2)
5.58 198092292 Optical fiber connection error ......................................................... 5-99

5.59 198092295 Device power down......................................................................5-100
5.60 198092363 Faulty main power alarm ..............................................................5-101
5.61 198092394 Several faulty rectifiers .................................................................5-103
5.62 198092426 The GNSS cascading clock is faulty ..............................................5-104
5.63 198092435 Inter-subrack Ethernet link broken in stack mode ...........................5-107
5.64 198092447 Unbalanced AC phase voltage of built-in power .............................5-108
5.65 198092449 Missing AC phase voltage of built-in power....................................5-109
5.66 198092450 Battery low-voltage cut-off of built-in power.................................... 5-111
5.67 198092451 Broken LLVD1 branch E of built-in power....................................... 5-113
5.68 198092452 Broken LLVD1 branch of built-in power.......................................... 5-115
5.69 198092453 Broken LLVD2 branch E of built-in power....................................... 5-117
5.70 198092454 Broken battery cut-off branch E of built-in power ............................ 5-119
5.71 198092455 Broken battery cut-off branch of built-in power ...............................5-121
5.72 198092456 Abnormal battery current of built-in power......................................5-123
5.73 198092457 Abnormal CAN bus of built-in power..............................................5-124
5.74 198092458 Abnormal battery of built-in power.................................................5-125
5.75 198092459 Abnormal input dry contact of built-in power...................................5-126
5.76 198092460 High-temperature cut-off of built-in power ......................................5-127
5.77 198092461 Failure in frame synchronization between BBU subracks ................5-129
5.78 198092550~198092599 User-defined dry contact alarm ..................................5-131
5.79 198096830 Too large phase difference between clock sources.........................5-133
5.80 198096831 1588 clock source fault.................................................................5-136
5.81 198096835 GNSS receiver fault .....................................................................5-138
5.82 198096836 GNSS antenna feeder link fault.....................................................5-144
5.83 198096838 Clock source abnormal in stack mode ...........................................5-147
5.84 198097004 Board hardware fault....................................................................5-148
5.85 198097060 Board communication link interrupted............................................5-149
5.86 198097109 E1/T1 link is interrupted................................................................5-150
5.87 198097680 POE power supply abnormal ........................................................5-152
5.88 198098111 Fan failure ...................................................................................5-153
5.89 198098251 The working mode of the Ethernet port doesn't match the peer end
....................................................................................................................5-154
5.90 198098314 Inter-board data link abnormal. .....................................................5-155
5.91 198098315 Input clock of the board abnormal. ................................................5-156
5.92 198098318 Unavailable optical module ..........................................................5-158
5.93 198098320 Optical interface reception link degraded .......................................5-160
5.94 198098440 Disable PA ..................................................................................5-162
V
SJ-20141022095204-005|2015-07-27 (R2.2)
5.95 198098465 VSWR of the antenna feeder abnormal .........................................5-163

5.96 198098466 Temperature abnormal .................................................................5-165
5.97 198098467 Internal fault ................................................................................5-166
5.98 198098468 External extended device fault ......................................................5-167
5.99 198098469 Abnormal RX channel ..................................................................5-172
5.100 198098470 Blocked resources manually .......................................................5-174
5.101 198098471 Carrier downlink data problem ....................................................5-175
5.102 198098472 RRU Power Abnormal Alarm ......................................................5-176
5.103 198098473 The baseband signal input to the TX channel is abnormal.............5-178
5.104 198098474 RRU fan failure ..........................................................................5-179
5.105 198092117 Embedded power Rectifier Module Fault......................................5-180
5.106 198092091 Embedded power SMR CommFail ..............................................5-182
5.107 198100078 Abnormal input dry contact one of built-in power ..........................5-184
5.108 198100079 Abnormal input dry contact two of built-in power...........................5-185
5.109 198100080 Abnormal input dry contact three of built-in power ........................5-186
5.110 198100081 Abnormal input dry contact four of built-in power ..........................5-187
5.111 198100280 The output power of the TX channel is abnormal ..........................5-188
5.112 198100283 Smart antenna calibration is abnormal .........................................5-189
5.113 198094829 eNodeB synchronization abnormal ..............................................5-191
5.114 198094839 Reverse link RSSI minor alarm ...................................................5-191
5.115 198094840 Reverse link RSSI major alarm ...................................................5-192
5.116 198094847 RF channel attenuation consistency alarm ...................................5-193
5.117 198094848 Antenna calibration failure...........................................................5-194
5.118 198097680 POE power supply abnormal.......................................................5-195
Chapter 6 Communication Alarm.............................................................. 6-1

6.1 198092013 High BER rate at the E1/T1 link ......................................................... 6-1
6.2 198092230 The SCTP association is broken ........................................................ 6-3
6.3 198092231 The PPP link is broken...................................................................... 6-4
6.4 198092232 The HDLC link is broken ................................................................... 6-6
6.5 198092233 The SSCOP link is broken................................................................. 6-7
6.6 198092361 The IMA group is faulty ..................................................................... 6-8
6.7 198092362 The IMA/TC link is faulty ................................................................. 6-10
6.8 198092399 The BFD connection is broken..........................................................6-11
6.9 198092401 E1/T1 link self-loop ......................................................................... 6-12
6.10 198092402 The TCP connection is broken....................................................... 6-13
6.11 198092428 The SCTP path is broken .............................................................. 6-15
6.12 198092431 The received optical power of the optical module is abnormal .......... 6-17
VI
SJ-20141022095204-005|2015-07-27 (R2.2)
6.13 198096839 RRU inner GNSS clock source abnormal ....................................... 6-18
6.14 198097169 The next hop IP is unreachable...................................................... 6-20
6.15 198097171 Authentication failure..................................................................... 6-21
6.16 198097172 Configuration parameter of OAM Channel is wrong......................... 6-22
6.17 198097175 Remote server unreachable........................................................... 6-24
6.18 198098252 The physical Ethernet link is broken .............................................. 6-26
6.19 198098319 Optical port receiving link failure .................................................... 6-27
6.20 198094830 S1 link is broken ........................................................................... 6-30
6.21 198094831 X2 link is broken ........................................................................... 6-32
6.22 198094852 All MME associations interrupted ................................................... 6-35
6.23 198094863 S1 GTP-U path unavailable ........................................................... 6-35
6.24 198094864 X2 GTP-U path unavailable ........................................................... 6-36
6.25 198094868 The link between eNodeB and iCS is broken .................................. 6-37
Chapter 7 Notification ................................................................................ 7-1

7.1 198092031 Board initialization process completes................................................ 7-2
7.2 198092033 Board power-on failed ....................................................................... 7-2
7.3 198092034 Bit error has been detected during E1 physical layer in the past 24
hours ............................................................................................................... 7-3
7.4 198092035 E1 link bit error has been detected in the past 24 hours....................... 7-4
7.5 198092058 Software version recover succeed ..................................................... 7-5
7.6 198092059 Alarm Storm ..................................................................................... 7-5
7.7 198092063 Switchover completes ....................................................................... 7-6
7.8 198092271 Local benchmark clock unlocked ....................................................... 7-7
7.9 198092312 PPP Negotiatory IP Conflict............................................................... 7-8
7.10 198092314 IP Conflict ...................................................................................... 7-9
7.11 198092315 Mac Conflict.................................................................................. 7-10
7.12 198092381 EFM Link has error data .................................................................7-11
7.13 198092392 Product process fails to power on .................................................. 7-12
7.14 198092441 IR changeover successful.............................................................. 7-13
7.15 198092442 No need for IR changeover............................................................ 7-13
7.16 198092444 SSCOP fault................................................................................. 7-14
7.17 198096557 Uplink IQ link error ........................................................................ 7-15
7.18 198096566 RRU alarm reset ........................................................................... 7-15
7.19 198097804 Um interface implements clock synchronization via software ........... 7-16
7.20 198097805 MP voltage abnormal .................................................................... 7-17
7.21 198097806 PP voltage abnormal..................................................................... 7-18
7.22 198097864 Product process power-on completes............................................. 7-19
VII
SJ-20141022095204-005|2015-07-27 (R2.2)
7.23 198097865 Switchover fails............................................................................. 7-19

7.24 198097866 port Active/standby switchover notification...................................... 7-20
7.25 198097867 Power Amplifier (PA) switch for smart carrier power-on/off ............... 7-22
7.26 198097907 Opening of Node B via USB finishes .............................................. 7-23
7.27 198097940 LMT is logged in ........................................................................... 7-23
7.28 198097964 LCK indication .............................................................................. 7-24
7.29 198097965 CCM Remote MEP Error ............................................................... 7-25
7.30 198097966 CCM Message Error ..................................................................... 7-26
7.31 198097967 CCM Xconnect Error ..................................................................... 7-28
7.32 198097968 AIS indication ............................................................................... 7-29
7.33 198098000 Unavailable POD .......................................................................... 7-30
7.34 198098001 Unconfigured POD........................................................................ 7-32
7.35 198098002 The License is entering to trying urgency state ............................... 7-33
7.36 198098003 The license file will soon fall due .................................................... 7-34
7.37 198098005 System capacity overload.............................................................. 7-34
7.38 198098020 The Ethernet communication abnormal .......................................... 7-35
7.39 198098021 High BER at the electrical port ....................................................... 7-36
7.40 198098030 Carrier downlink data problem ....................................................... 7-38
7.41 198098316 The received optical power is abnormal.......................................... 7-39
7.42 198094861 S1 link-break statistics notification.................................................. 7-41
7.43 198094862 X2 link state updating notification ................................................... 7-42
7.44 198094865 S1 GTP-U Path link state updating notification ................................ 7-44
7.45 198094866 X2 GTP-U Path link state updating notification ................................ 7-46
7.46 198098459 Unavailable alarm of time slot turn-off function ................................ 7-48
7.47 198094849 Cloud scheduling cell link fault ....................................................... 7-49
7.48 198094857 The system capacity will exceed the License limit ........................... 7-51
Glossary .......................................................................................................... I
VIII
SJ-20141022095204-005|2015-07-27 (R2.2)
About This Manual

Purpose
This manual introduces the alarms and notifications that might occur during the product
installation, operation and maintenance.
Intended Audience
This manual is intended for:
l
l
Maintenance engineers
Network management monitoring employee
What Is in This Manual

This manual contains the following chapters:
Chapter
Summary
Chapter 1, Overview
Describes the concept of fault management
Chapter 2, Processing Error Alarm
Describes processing error alarms with respect to alarm

information, cause, impact, and handling action
Chapter 3, QoS Alarm
Describes QoS alarms with respect to alarm information,

cause, impact, and handling action
Chapter 4, Environment Alarm
Describes environment alarms with respect to alarm

Chapter 5, Equipment Alarm
Describes equipment alarms with respect to alarm

Chapter 6, Communication Alarm
Describes communication alarms with respect to alarm

Chapter 7, Notification
Describes notification with respect to alarm information,

cause, impact, and handling action
I
SJ-20141022095204-005|2015-07-27 (R2.2)
This page intentionally left blank.
II
SJ-20141022095204-005|2015-07-27 (R2.2)
Chapter 1
Overview
Fault management is responsible for collecting information of failures and events that occur
during system operation or service processing.
The information, in the form of alarm or notification, is stored in database or displayed
on real-time basis via a user-oriented fault monitoring platform. Means such as
visual-interface monitor or history information query can be used to view current or
historical system operation and service processing status. Fault management enables
maintenance personnel to troubleshoot and take preventive measures to remove potential
fault and restore system and services as early as possible.
Fault is displayed in the form of alarm or notification.
Alarm
The fault that persists during system operation and affects system reliability and normal
services is referred to as an alarm. Alarm usually lasts until fault removal.
Due to its possible impact on normal system operation, alarm requires timely
troubleshooting in which alarm cause is identified, and the fault is located and handled.
Notification
Notification refers to the non-repeated/instantaneous fault or event that occurs during
system operation. Examples include board reset, signaling overload, etc.
Notification is mostly caused by sudden environment change or other accidental factors.
No special handling is required for the notification, which can be automatically removed by
the system. Only the notification that occurs persistently requires troubleshooting.
Alarm/Notification Information Structure

Each alarm/notification contains the following contents:
l
Alarm Code
Alarm Code is the identifier which differentiates alarms/notifications, which is defined
by a 32-bit field indicating the specific code value.
l
l
Alarm Name
Alarm Severity
There are four levels for alarm, which are indicated in descending order of severity as
Critical, Major, Minor, and Warning.
Critical alarm causes system breakdown and service interruption. It requires

immediate troubleshooting.
1-1
SJ-20141022095204-005|2015-07-27 (R2.2)
ZXSDR UniRAN Alarm Handling
Major alarm significantly affects system operation or weakens network service

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

non-significant way. It requires timely troubleshooting so as to avoid severity
escalation.
Warning alarm poses a potential hazard to system operation and network service
capability. It requires troubleshooting at an appropriate time so as to avoid
severity escalation.
The degree of impact as described in the definition of alarm severity refers to the
impact of a single index, such as reliability and security. Once the impact on any
of the index reaches the specified threshold, the severity level of the alarm can be
roughly determined. If an alarm has an impact on multiple indices, alarm severity
should be escalated accordingly.
Note:
Alarm severity can be modified in NetNumen U31 if necessary.
Generally speaking, the default alarm severity is reasonably set. Users should
think twice before making any modification.
There is only one severity level for notification: Notification.

l
Alarm Type
Alarm is classified into these types below according to alarm trigger condition and its
system impact:
Equipment alarm: related with device hardware.
Communication alarm:
Recommendation X.733).
related
Processing error alarm:

Recommendation X.733).
related with software or operation fault (ITU-T
Environment alarm: related with the environment where the equipment is located
(ITU-T Recommendation X.733).
QoS alarm: related with quality of service.
with
information
transmission
(ITU-T
Alarm Cause
Probable alarm causes are enumerated to help users troubleshoot, find preventive
measures, and restore the system to normal state in a timely manner.
Impact
System impact refers to the impact that the alarm/notification incurs on system or
services.
1-2
SJ-20141022095204-005|2015-07-27 (R2.2)
Chapter 1 Overview
Action
Troubleshooting measures and suggestions are provided.
following tips when handling alarms/notifications.
Pay attention to the
After recording the fault phenomenon, operation and maintenance personnel may
handle the fault step by step as described in the Solution of this manual. If the
fault is removed at any handling step, terminate the handling process. If the fault
is not removed, go ahead to the next handling step.
If the fault cannot be removed, contact the local ZTE office as soon as possible.
1-3
SJ-20141022095204-005|2015-07-27 (R2.2)
1-4
SJ-20141022095204-005|2015-07-27 (R2.2)
Chapter 2
Processing Error Alarm

Table of Contents
198092014 SNTP time adjustment failure ..................................................................2-2
198092017 Software loading failure ...........................................................................2-4
198092019 Failure in active/standby synchronization .................................................2-4
198092027 Failure in repairing a version package......................................................2-5
198092029 Hardware type is different from the configuration ....................................2-6
198092066 Failure in uncompressing the LMT software .............................................2-9
198092070 Initialization failure .................................................................................2-10
198092348 The board is being initialized..................................................................2-10
198092390 CPU over loading highly ........................................................................2-11
198092391 CPU over loading...................................................................................2-12
198092395 Running software rollback......................................................................2-13
198092396 Hot patch fault .......................................................................................2-14
198092397 Failure in finding the board-related software ID ......................................2-15
198092443 IR changeover failure.............................................................................2-16
198096551 RRU unconfigured .................................................................................2-17
198096832 Line clock source fault ...........................................................................2-18
198096833 SyncE clock fault ...................................................................................2-22
198096834 1PPS+TOD clock source fault................................................................2-24
198097050 Baseband unit is being initialized ...........................................................2-29
198097404 Resource usage rate is too high.............................................................2-30
198097510 The NE does not support the configured parameters ............................2-31
198097511 Parameter configuration error.................................................................2-38
198097567 Version package fault.............................................................................2-45
198097568 Version repository file problem ...............................................................2-46
198097604 Software runs abnormally ......................................................................2-47
198097605 The RRU link is broken .........................................................................2-49
198097606 The PB link is broken .............................................................................2-51
198097613 LMT is logged in ....................................................................................2-53
198097650 Configuration Data Loading Abnormal ...................................................2-53
198097651 Configuration data unmatched with the license ......................................2-54
198097670 The system has no the available License file .........................................2-55
198097673 The license file will soon fall due ............................................................2-56
198098464 Parameter configuration error ................................................................2-57
198100275 RRU software version is abnormal .........................................................2-61
198100276 RRU fiber delay beyond the limit............................................................2-62
198094815 Rule library of performance statistics hasn't been loaded or loaded
unsuccessfully..........................................................................................................2-63
2-1
SJ-20141022095204-005|2015-07-27 (R2.2)
198094838 Cell parameter configuration failure........................................................2-64

198094858 Cell shutdown alarm ..............................................................................2-65
2.1 198092014 SNTP time adjustment failure

Alarm Information
l
l
l
l
Alarm code: 198092014

Name: SNTP time adjustment failure
Alarm severity: Minor
Alarm type: Processing Error Alarm
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
I. Impact on the equipment:
None.
II. Impact on the services:
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
ManagementManaged
ElementSystem
ParameterTime Configuration, and check whether the IP addresses of the NTP
server and standby SNTP server are the same as planned.
YesStep 2.
NoSubstep b.
b. Change the IP addresses of the servers to the planned IP addresses of the current
network.
c.
Synchronize the configurations to the corresponding NE.
d. After 15 minutes, check whether the alarm is cleared.

YesEnd.
NoStep 2.
2-2
SJ-20141022095204-005|2015-07-27 (R2.2)
Chapter 2 Processing Error Alarm
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).
YesStep 3.
NoSubstep b.
b. Enable the SNTP service.
c.
Select Dynamic ManagementDynamic CommandSDRManaged Network

ElementTime, and synchronize NE time. Check whether the synchronization
is successful.
YesSubstep d.
NoStep 3.

YesEnd.
NoStep 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.
YesSubstep b.
NoContact the customer service center.
b. Use the brsping tool on the base station server to check whether the
communication with the SNTP is normal.
YesSubstep c.
NoContact ZTE technical support.
c.
Select Dynamic Management > Dynamic Command > SDR > Managed
Network Element > Time, and synchronize NE time. Check whether the
synchronization is successful.
YesSubstep d.

YesEnd.
2-3
SJ-20141022095204-005|2015-07-27 (R2.2)
2.2 198092017 Software loading failure

Alarm Information
l
l
l
l

Name: Software loading failure
Alarm severity: Major
Alarm Description
This alarm occurs when the board fails to load CPU/DSP/FPGA/RamdiskPlus software
versions.
Alarm Cause
1. The board software version is not correct.
2. The board hardware is faulty.
Impact
None.
All of the services operating on the board are interrupted.
Action
Select Software Version ManagementUpgrade Management from the menu. The
Upgrade Management tab is displayed. Redownload all planned version packages.
Wait 30 minutes, and check whether the alarm is cleared.
YesEnd.
2.3 198092019 Failure in active/standby

synchronization
Alarm Information
l
l
l
l

Name: Failure in active/standby synchronization
2-4
SJ-20141022095204-005|2015-07-27 (R2.2)
Alarm Description
This alarm occurs when the active/standby synchronization fails.
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
Wait 30 minutes, and check whether the alarm has been cleared.
YesEnd.
NoStep 2.
2. Confirm the slot of the backup board and reset the board based on the rack
number/shelf number/slot number in the Detail Information dialog box.
YesEnd.
2.4 198092027 Failure in repairing a version package

Alarm Information
l
l
l
l

Name: Failure in repairing a version package
Alarm severity: Critical
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.
2-5
SJ-20141022095204-005|2015-07-27 (R2.2)
Alarm Cause
The version package fails to be repaired.
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.
YesStep 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.
YesEnd.
2.5 198092029 Hardware type is different from the

configuration
Alarm Information
l
l
l
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.
2-6
SJ-20141022095204-005|2015-07-27 (R2.2)
Impact
None.
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.
YesStep 2.
NoStep 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.
b. Synchronize the configuration to the NE.
c.
YesEnd.
3. Replace the board with the planned board/RRU based on the rack number/shelf
number/slot number in the Detailed Information dialog box. 15 minutes, and check
whether the alarm has been cleared.
YesEnd.
2-7
SJ-20141022095204-005|2015-07-27 (R2.2)

l
The cabinet type is inconsistent with that configured in the OMC:

check whether the cabinet type matches the network planning.
YesStep 2.
NoStep 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.
c.
YesEnd.
3. Based on the NE information in the Detail Information dialog box, replace the
cabinet with the planned cabinet.
YesEnd.
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.
YesStep 2.
NoStep 3.
2. Change the configuration to be the same as the network planning.
a. Select Configuration Management > Element Managed > 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
c.
YesEnd.
3. Replace the board with the planned physical board based on the rack
number/shelf number/slot number in the Detail Information dialog box. 15
minutes, and check whether the alarm has been cleared.
2-8
SJ-20141022095204-005|2015-07-27 (R2.2)
YesEnd.
2.6 198092066 Failure in uncompressing the LMT

software
Alarm Information
l
l
l
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
whether the alarm is cleared.
YesEnd.
2-9
SJ-20141022095204-005|2015-07-27 (R2.2)
2.7 198092070 Initialization failure

Alarm Information
l
l
l
l

Name: Initialization failure
Alarm Description
This alarm occurs when a hardware/software/data error occurs during initialization.
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
YesEnd.
2.8 198092348 The board is being initialized

Alarm Information
l
l
l
l

Name: The board is being initialized
Alarm Description
This alarm occurs when the board is rebooted and being initialized.
2-10
SJ-20141022095204-005|2015-07-27 (R2.2)
Alarm Cause
1. The board resetting command is executed.
2. The board is powered on.
3. The board automatically resets due to software error.
Impact
None.
The board is in initialization status, and all of the services operating on the board are
interrupted.
Action
YesEnd.
2.9 198092390 CPU over loading highly

Alarm Information
l
l
l
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.
2-11
SJ-20141022095204-005|2015-07-27 (R2.2)
Action
1. Check if the system is in traffic peak period.
YesEnd.
NoStep 2.
2. It is recommended to evaluate network planning in depth and optimize network
planning.
YesEnd.
2.10 198092391 CPU over loading

Alarm Information
l
l
l
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.
YesEnd.
NoStep 2.
2. It is recommended to evaluate network planning in depth and optimize network
planning.
2-12
SJ-20141022095204-005|2015-07-27 (R2.2)

YesEnd.
2.11 198092395 Running software rollback

Alarm Information
l
l
l
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.
YesStep 3.
NoStep 2.
2. Change the related parameters in the Configuration Management window based on
the prompt information.
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.
YesEnd.
2-13
SJ-20141022095204-005|2015-07-27 (R2.2)
2.12 198092396 Hot patch fault

Alarm Information
l
l
l
l

Name: Hot patch fault
Alarm Description
This alarm occurs when the board fails to download/upload/uninstall a hot patch.
Alarm Cause
1. The board hot patch software version is not correct.
Impact
None.
The services that the board bears might be interrupted.
Action
menu. The Upgrade Task Management tab is displayed. Re-download the target
hot patch version package.
YesEnd.
No Step 2.
2. Reset the board based on the rack number/shelf number/slot number in the Detail
Information dialog box. Refer to Reset Boards.
YesEnd.
No Contact ZTE technical support.
2-14
SJ-20141022095204-005|2015-07-27 (R2.2)
2.13 198092397 Failure in finding the board-related

software ID
Alarm Information
l
l
l
l

Name: Failure in finding the board-related software ID
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).
YesSubstep b.
NoSubstep 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
check whether the alarm is cleared.
YesEnd.
NoStep 2.
2-15
SJ-20141022095204-005|2015-07-27 (R2.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.
Wait 30 minutes and check whether the alarm is cleared.
YesEnd.
NoStep 2.
2. Reset the board in accordance with the slot, shelf, and rack information in the Detail
YesEnd.
2.14 198092443 IR changeover failure

Alarm Information
l
l
l
l

Name: IR changeover failure
Alarm Description
This alarm occurs when IR changeover fails.
Alarm Cause
IR changeover fails.
Impact
None.
All the services on the board are blocked.
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).
YesStep 2.
NoSubstep b.
2-16
SJ-20141022095204-005|2015-07-27 (R2.2)
b. Connect the optical fiber correctly.

c.
After 15 minutes, check whether the alarm is cleared.

YesEnd.
NoStep 2.
2. Check whether the optical module connection is correct.

a. Check whether the optical module connection is correct (for example, the optical
module connection is secure).
YesStep 3.
NoSubstep b.
b. Connect the optical module correctly.
c.

YesEnd.
NoStep 3.
3. Replace the optical fiber. 15 minutes, check whether the alarm is cleared.
YesEnd.
NoStep 4.
4. Replace the optical module. 15 minutes, check whether the alarm is cleared.
YesEnd.
2.15 198096551 RRU unconfigured

Alarm Information
l
l
l
l

Name: RRU unconfigured
Detailed Description
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.
2-17
SJ-20141022095204-005|2015-07-27 (R2.2)
Impact
None.
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.
YesStep 2.
NoStep 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.
b. Synchronize the configurations to the corresponding NE.
c.

YesEnd.
3. Remove the corresponding RRU in accordance with the additional alarm information.
YesEnd.
2.16 198096832 Line clock source fault

Alarm Information
l
l
l
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-18
SJ-20141022095204-005|2015-07-27 (R2.2)
2. Cable fault.
3. Up level connected device fault.
4. Poor quality of the up level device clock.
5. Board hardware fault.
Impact
None.
The system clock is in free oscillation status. The quality of the services on this board is
affected.
Action
Perform the following operations based on the additional alarm information in alarm details:
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.
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 SetClock Device, check
whether the reference clock source type is the same as planned.
Yes Step 2.
NoSubstep b.
b. Delete the incorrect configuration and configure the clock reference source
correctly in accordance with the network planning.
c.

YesEnd.
NoStep 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).
YesStep 3.
NoSubstep b.
b. Connect the cables properly.
YesEnd.
2-19
SJ-20141022095204-005|2015-07-27 (R2.2)
NoStep 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.
YesStep 8.
NoStep 4.
4. Reset the SA board.
YesEnd.
NoStep 5.
5. Reset the board based on the Rack Number, Shelf Number and Slot Number
information in alarm details. Refer to Reset Boards.
YesEnd.
NoStep 6.
6. Replace the SA board.
YesEnd.
NoStep 7.
7. Replace the board in accordance with the Rack Number, Shelf Number and Slot
Number information in alarm details. 15 minutes, check whether the alarm is
cleared.
YesEnd.
NoStep 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).
YesContact ZTE technical support.
NoSubstep b.
b. Ask the corresponding maintenance personnel to remove the fault.
YesEnd.
l
Clock signal quality of BITS-2MHz is poor/Clock signal quality of BITS-2Mbps is poor:

2-20
SJ-20141022095204-005|2015-07-27 (R2.2)
1. Ask the maintenance personnel to check whether the BITS clock source is in
locked status.
YesStep 3.
NoStep 2.
2. Ask the corresponding maintenance personnel to remove the fault.
YesEnd.
No Step 3.
3. Reset the board based on the Rack Number, Shelf Number and Slot Number in
alarm details. Refer to Reset Boards.
YesEnd.
NoStep 4.
Number in alarm details. 15 minutes, check whether the alarm is cleared.
YesEnd.
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.
YesStep 3.
NoStep 2.
YesEnd.
NoStep 3.
YesEnd.
NoStep 4.
YesEnd.
2-21
SJ-20141022095204-005|2015-07-27 (R2.2)
2.17 198096833 SyncE clock fault

Alarm Information
l
l
l
l

Name: SyncE clock fault
Alarm Description
This alarm occurs in the following conditions:
l
l
l
l
The quality of synchronous Ethernet clock extracted from SSM messages is poor.
SSM messages are lost.
Clock signals cannot be detected.
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:

1. Check whether related alarms exist.
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-22
SJ-20141022095204-005|2015-07-27 (R2.2)
b. Check whether the alarm is cleared.

YesEnd.
NoStep 2.
2. Check whether the clock reference source is correct.
B8200, confirm the main control board slot (slot 1 or slot 2) configured for
the reference clock source. Select ClockDevice SetClock Device, check
whether the reference clock source type is the same as planned.
YesStep 3.
NoSubstep b.
b. Delete the incorrect configuration and configure the clock reference source
correctly in accordance with the network planning.
c.

YesEnd.
NoStep 3.
YesEnd.
No Step 4.
4. Replace the board connected with the SyncE cable. 15 minutes, check whether
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.
NoStep 2.
YesEnd.
NoStep 3.
2-23
SJ-20141022095204-005|2015-07-27 (R2.2)

YesEnd.
NoStep 4.
YesEnd.
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.
YesStep 3.
No Step 2.
YesEnd.
NoStep 3.
Yes End.
NoStep 4.
YesEnd.
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.
YesEnd.
2.18 198096834 1PPS+TOD clock source fault

Alarm Information
l

2-24
SJ-20141022095204-005|2015-07-27 (R2.2)
l
l
l
Name: 1PPS+TOD clock source fault

Alarm Description
l
l
l
The 1PPS+TOD reference source doesn't receive messages from the serial port.
The 1PPS+TOD reference source's pulse per second (PPS) status is unavailable.
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.
YesSubstep e.
No Substep b.
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 SetClock Device, and delete
1PPS+TOD or 1PPS+TOD backup clock reference source of the local BTS.
c.

2-25
SJ-20141022095204-005|2015-07-27 (R2.2)

YesEnd.
e. Check whether the 1PPS+TOD output configuration of the upper level device
is the same as planned.
YesStep 2.
NoSubstep f.
f.
Ask the corresponding maintenance personnel to modify the 1PPS+TOD

output configuration to that as planned.
YesEnd.
NoStep 2
2. Check whether the 1PPS+TOD clock cable is securely connected.

YesStep 4
NoStep 3
3. Connect the cable correctly.
YesEnd.
NoStep 4.
4. Change a cable.
YesEnd.
NoStep 5.
YesEnd.
NoStep 6.
YesEnd.
l
1PPS+TOD
reference
source
Pulse
Per
Second(PPS)
status
unavailable/1PPS+TOD backup source Pulse Per Second(PPS) status
unavailable:
is
is
2-26
SJ-20141022095204-005|2015-07-27 (R2.2)
1. Check whether clock-related alarms exist in the upper level device in accordance
with the network planning.
YesStep 2.
2. Ask the corresponding maintenance personnel to clear the alarm(s).
YesEnd.
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
confirm the main control board slot (slot 1 or slot 2) configured for the reference
clock source. Select ClockDevice SetClock 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.
NoStep 3.
3. Modify the baud rate configuration to that of the upper level device.
YesEnd.
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.
YesStep 3.
NoStep 2.
YesEnd.
NoStep 3.
3. Change a cable.
YesEnd.
NoStep 4.
2-27
SJ-20141022095204-005|2015-07-27 (R2.2)
4. Reset the board in accordance with the Rack Number, Shelf Number and Slot
Number in alarm details. Refer to Reset Boards.
YesEnd.
NoStep 5.
YesEnd.
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.
NoStep 2.
2. Reset the board in accordance with the Rack Number, Shelf Number and Slot
Number in alarm details. Refer to Reset Boards.
YesEnd.
NoStep 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
details.
YesEnd.
NoStep 4.
YesEnd.
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:
198096835 GNSS receiver fault
2-28
SJ-20141022095204-005|2015-07-27 (R2.2)
198096836 GNSS antenna feeder link fault

198096837 GNSS receiver satellite searching fault
2. Handle the alarms according to corresponding proposals.
3. After 15 minutes, check whether the alarm is cleared.
YesEnd.
2.19 198097050 Baseband unit is being initialized

Alarm Information
l
l
l
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.
Action
YesEnd.
2-29
SJ-20141022095204-005|2015-07-27 (R2.2)
2.20 198097404 Resource usage rate is too high

Alarm Information
l
l
l
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.
YesEnd.
NoStep 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).
YesEnd.
2-30
SJ-20141022095204-005|2015-07-27 (R2.2)
2.21 198097510 The NE does not support the

configured parameters
Alarm Information
l
l
l
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.
l
l
l
l
l
l
l
l
l
l
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 services on the board may be interrupted or the service quality may be affected.
The configured receiver operating 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.
2-31
SJ-20141022095204-005|2015-07-27 (R2.2)
Configured dry contact beyond the hardware support capatity: Additional configured
dry contact can not be normal use, some or all of the services on this base station
may be interrupted, or the service quality may be affected.
Configured E1/T1 beyond the hardware support capatity: Additional configured
E1/T1 can not be normal use, some or all of the services on this base station may be
Action
Perform the following operations according to the additional alarm information in the alarm
details:
l
Optical module rate mismatch:

1. Verify that the rate of the optical interface is configured correctly.
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.
YesStep 2.
NoSubstep b.
b. Re-configure the rate of the optical interface as planned.
c.
d. Wait for 15 minutes, and check whether the alarm is cleared.

YesEnd.
NoStep 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
details.
Wait for 15 minutes, and check whether the alarm is cleared.
YesEnd.
l
Optical interface operating mode mismatch:

1. Verify that the operating mode of the optical interface is configured correctly.
a. Select Configuration Management > Managed Element > Transmission
Network > UMTS (For example) > Physical Hosting > Physical Layer
Port, and check whether the Ethernet configuration parameter is configured
as planned.
YesStep 2.
NoSubstep b.
2-32
SJ-20141022095204-005|2015-07-27 (R2.2)
b. Modify the Ethernet configuration parameter as planned.

c.

YesEnd.
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.
YesEnd.
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.
YesStep 2.
NoSubstep b.
b. Modify the transmission mode as planned.
c.

YesEnd.
NoStep 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.
YesEnd.
l
The configured rate is not supported by the optical interface board:

1. Verify that the rate of the optical interface is configured correctly.
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 according to the rack number/shelf number/slot
number in the alarm details.
YesStep 2.
2-33
SJ-20141022095204-005|2015-07-27 (R2.2)
NoSubstep b.
c.

YesEnd.
NoStep 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.
NoSubstep b.
b. Replace the optical interface board with one that supports the planned rate
according to the actual network plans.
YesEnd.
l
The configured clock source is not supported by the board:

1. Verify that the clock reference source is configured correctly.
a. Select Configuration Management > Managed Element >
DeviceCabinet (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.
YesStep 2.
NoSubstep b.
b. Re-configure the clock reference source as planned.
c.

YesEnd.
NoStep 2.
NoSubstep b.
2-34
SJ-20141022095204-005|2015-07-27 (R2.2)
b. Replace the board with one that supports the planned clock reference source
YesEnd.
l
The configured receiver type is not supported by the board:

1. Verify that the type of the GNSS receiver hardware is configured correctly.
Cabinet (For example, B8200), check the main control board slot configured
for the clock reference source (slot 1 or slot 2). Select ClockDevice
SetClock Device, and check whether the type of the GNSS receiver
hardware is configured as planned.
YesStep 2.
NoSubstep b.
b. Re-configure the type of the GNSS receiver hardware as planned.
c.

YesEnd.
NoStep 2.
NoSubstep b.
b. Replace the board with one that supports the planned type of the GNSS
receiver hardware according to the actual network plans. for 15 minutes, and
YesEnd.
l
The configured functional mode is not supported by the board:

1. Verify that the functional mode of the board is configured correctly.
Cabinet (For example, B8200), and check whether the functional mode
of the board is configured as planned according to the rack number/shelf
YesStep 2.
NoSubstep b.
2-35
SJ-20141022095204-005|2015-07-27 (R2.2)
b. Re-configure the functional mode of the board as planned.

c.

YesEnd.
NoStep 2.
NoSubstep b.
b. Replace the board with one that supports the planned functional mode
YesEnd.
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.
Cabinet (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
YesStep 2.
NoSubstep b.
b. Re-configure the link mode of the uplink transmission port as planned.
c.

YesEnd.
NoStep 2.
2. Contact the maintenance personnel for the peer to ensure that link mode is
configured correctly.
YesEnd.
l
Incorrect parameter configurations/failure in configuration validation:

2-36
SJ-20141022095204-005|2015-07-27 (R2.2)

YesEnd.
l
The configured receiver operating type is not supported by the board:

1. Verify that the operating mode of the receiver is configured correctly.
Cabinet (For example, B8200) > GNSS Device Set > GNSS Set, and
check whether the operating mode of the receiver is configured as planned
YesStep 2.
NoSubstep b.
b. Re-configure the operating mode of the receiver as planned.
c.

YesEnd.
NoStep 2.
NoSubstep b.
b. Replace the board with one that supports the planned operating mode
YesEnd.
l
Configured dry contact beyond the hardware support capatity:

1. Verify that the number or index of dry contact is configured correctly.
Cabinet (For example, B8200) > Dry Contact Device, and check whether
the number of configured dry contact is not greater than or the index
of configured dry contact is smaller than that of the hardware supports
NoSubstep b.
2-37
SJ-20141022095204-005|2015-07-27 (R2.2)
b. Reduce the number or index of configured dry contact or repalce the board
with one that supports the configured number of dry contact as planned.
c.

YesEnd.
l
Configured E1/T1 beyond the hardware support capatity:

1. Verify that the number or ID of E1/T1 is configured correctly.
Network > UMTS (for example) > Physical Hosting > Physical Layer Port,
and check whether the number of configured E1/T1 is not greater than or the
E1/T1 ID is smaller than that of the hardware supports.
NoSubstep b.
b. Reduce the number or ID of configured E1/T1 or repalce the board with one
that supports the configured number of E1/T1 as planned.
c.

YesEnd.
2.22 198097511 Parameter configuration error

Alarm Information
l
l
l
l

Name: Parameter configuration error
Alarm Description
This alarm occurs when the configured parameter is incorrect.
Alarm Cause
Parameters are configured incorrectly.
Impact
None.
2-38
SJ-20141022095204-005|2015-07-27 (R2.2)

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.
Cabinet (For example, B8200). Select Optical Port Device SetOptical
Port Device of the verified optical interface board, and check whether the
optical interface rate is configured.
NoSubstep b.
c.

YesEnd.
l
No baseband board rate configured during IQ channel establishment:

Contact ZTE technical support.
The optical module protocol type of the optical interface board not matching that of
the RRU:
1. Select Configuration ManagementManaged 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
a. Select Configuration ManagementManaged ElementDeviceCabinet
(For example, B8200). Select Optical Port Device SetOptical Port Device
of the verified optical interface board, and check whether the optical module
protocol type is configured as planned.
Yes -> Contact ZTE technical support.
NoSubstep b.
2-39
SJ-20141022095204-005|2015-07-27 (R2.2)
b. Re-configure the optical module protocol type as planned.

c.

YesEnd.
NoStep 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
configured as planned.
YesContact the customer service center.
NoSubstep b.
b. Re-configure the optical module protocol type as planned.
c.

YesEnd.
l
Failure in IQ channel resource allocation:

1. Select Configuration ManagementManaged ElementDevice,
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.
YesStep 3.
NoSubstep b.
c.

YesEnd.
NoStep 3.
3. Verify that cells of all the wireless standards are configured as planned.
a. Select Configuration ManagementManaged ElementRadio Parameter,
and check whether cells are configured as planned.
2-40
SJ-20141022095204-005|2015-07-27 (R2.2)

NoSubstep b.
b. Select Configuration ManagementManaged ElementRadio Parameter,
and modify the cell configurations as planned.
c.

YesEnd.
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
corresponding handling suggestions. Related alarms are as follows:
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).)
2. Check whether the alarm is cleared.
YesEnd.
The rate of the baseband board not matching the switching rate supported by the
optical interface board (local board):
1.
Verify that the name of the physical board is set to be the same as that of the
real board on site.
Select Configuration Management -> Managed Element -> Device -> Cabinet (For
example, B8200), and check whether the name of the physical board is set to be
the same as that of the real board on site according to the rack number/shelf
NoStep 2.
2. Re-configure the name of the physical board to that of the real board on site.
a. Select Configuration Management -> Managed Element -> Device -> Cabinet
(For example, B8200), and configure the name of the physical board to that of
the real board on site according to the rack number/shelf number/slot number
c.

2-41
SJ-20141022095204-005|2015-07-27 (R2.2)
YesEnd.
l
The configured power required by the board exceeding the power supply capacity of
the PM:
1. Select Dynamic ManagementDynamic CommandSDRDevice 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).
YesStep 3.
3. Verify that the board is configured as planned.
a. Check whether the board is configured as planned.
NoSubstep b.
b. Re-configure the board as planned.
c.

YesEnd.
l
The number of SCTP flows mismatch:

1. Select
Configuration
ManagementManaged
ElementTransport
NetworkUMTS (for example)Signalling and BusinessSCTP, 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 ZTE technical support.
NoStep 2.
2. Select
Configuration
ManagementManaged
ElementTransport
NetworkUMTS (for example)Signalling and BusinessSCTP, and modify
the number of outgoing/incoming flows on the local-end equipment to be
consistent with that configured on the remote-end device.
3. Synchronize the configurations to the corresponding NE.
YesEnd.
The optical interface rate on the local-end equipment not matching that on the
remote-end equipment:
2-42
SJ-20141022095204-005|2015-07-27 (R2.2)
1. Verify that the optical interface rate on the local-end equipment is configured
correctly.
(For example, B8200)Optical Port Device SetOptical Port Device, and
check whether the rate of the optical interface is configured as planned
YesStep 2.
NoSubstep b.
b. Modify the rate of the optical interface as planned.
c.

YesEnd.
NoStep 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.
NoSubstep 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. for 15 minutes, and check whether the alarm is cleared.
YesEnd.
l
The ABIS ports of both main control boards disabled:

1. Select Configuration ManagementManaged ElementDeviceCabinet (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.
YesStep 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.).
YesEnd.
2-43
SJ-20141022095204-005|2015-07-27 (R2.2)

l
The ABIS port configuration not matching the network cables connected on the
front-end:
1. Select Configuration ManagementManaged ElementDeviceCabinet (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
YesEnd.
Failure in TDM resource configuration:

1. 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:
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).)
YesEnd.
2. Verify that cells of all the wireless standards are configured as planned.
a. Select Configuration ManagementManaged ElementRadio Parameter,
and check whether cells are configured as planned.
NoSubstep b.
b. Select Configuration ManagementManaged ElementRadio Parameter,
and modify the cell configurations as planned.
c.

YesEnd.
2-44
SJ-20141022095204-005|2015-07-27 (R2.2)
2.23 198097567 Version package fault

Alarm Information
l
l
l
l

Name: Version package fault
Alarm Description
l
l
l
The software in the version package does not exist.

The software in the version package is damaged.
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
Perform the following operations in accordance with the information in the Remark field of
the Detail Information dialog box:
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.
Upgrade Task Management tab is displayed. Re-download the software
package obtained in Step 2.
YesEnd.
2-45
SJ-20141022095204-005|2015-07-27 (R2.2)

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.
NoStep 5.
Upgrade Task Management tab is displayed. Re-download the software
package.
YesEnd.
5. Right-click the package in the query result, and select Create Delete Package
Task from the shortcut menu to delete the package.
YesEnd.
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
YesEnd.
2.24 198097568 Version repository file problem

Alarm Information
l
l
l
l

Name: Version repository file problem
2-46
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
YesEnd.
2.25 198097604 Software runs abnormally

Alarm Information
l
l
l
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
l
The board software is not operating properly:

The board software process is not successfully started.
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-47
SJ-20141022095204-005|2015-07-27 (R2.2)
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:

1. Reset the board in accordance with the slot, shelf, and rack information in the
Detail Information dialog box. Refer to Reset Boards.
YesEnd.
NoStep 2.
2. Power off reset the board in accordance with the slot, shelf, and rack information
in the Detail Information dialog box. Refer to Reset Boards.
Wait 15 minutes, and check whether the alarms are cleared.
YesEnd.
The product process is not operating properly:

1. Check the abnormal product process in accordance with the information in the
Remark field of the Detail Information dialog box.
2. Select Dynamic Management > Dynamic Command > SDR > Managed
Network Element. The corresponding tab is displayed. Reset the abnormal
product process.
YesEnd.
NoStep 3.
Upgrade Task Management tab is displayed. Download, pre-activate, activate,
and apply the planned software package for the abnormal product process.
2-48
SJ-20141022095204-005|2015-07-27 (R2.2)
YesEnd.
l
The subunit software is not operating properly:

Reset the board in accordance with the slot, shelf, and rack information in the Detail
YesEnd.
2.26 198097605 The RRU link is broken

Alarm Information
l
l
l
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.
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.
2-49
SJ-20141022095204-005|2015-07-27 (R2.2)
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
198092029 Hardware type is different from the configuration
198098318 Unavailable optical module
198098319 Optical port receiving link failure
198092292 Optical fiber connection error
198092295 Device power down
198097604 Software runs abnormally
198097605 The RRU link is broken
198097060 Board communication link interrupted
198097004 Board hardware fault
198097511 Parameter configuration error
c.
Check whether the alarms are cleared.

YesEnd.
NoStep 2.
2. Verify that related alarms are not raised.

a. Check whether related alarms are raised. If they are raised, resolve the faults in
accordance with the corresponding handling suggestions. Related alarms are as
follows:
198098464 Parameter configuration error
b. Check whether the alarms are cleared.
YesEnd.
NoStep 3.
YesEnd.
2-50
SJ-20141022095204-005|2015-07-27 (R2.2)
NoStep 4.
4. Power off reset the board in accordance with the slot, shelf, and rack information in
the Detail Information dialog box. Refer to Reset Boards.
YesEnd.
2.27 198097606 The PB link is broken

Alarm Information
l
l
l
l

Name: The PB link is broken
Alarm Description
This alarm occurs when the PB loses software heart-beat for a time longer than the
specified period.
Alarm Cause
1. The PB works abnormally.
2. The communication link between the PB and the main control board is faulty.
Impact
None.
Action
1. Verify that related alarms are not raised on its upper-level board.
a. Select Configuration Management > Rack Graph > Topology View/Physical
View. The corresponding tab is displayed. View the slot, shelf, and rack
information of its upper-level board.
b. Check whether the alarms are raised on its upper-level board. If related alarms
are raised, resolve the faults in accordance with the corresponding handling
suggestions. Related alarms are as follows:
The board is powered off (198092057)
2-51
SJ-20141022095204-005|2015-07-27 (R2.2)
The board is not in position (198092072)

The board is not configured (198092203)
The board is being initialized (198092348)
Software loading failure (198092017)
Initialization failure (198092070)
Hardware type is different from the configuration (198092029)
Unavailable optical module (198098318)
Optical port receiving link failure (198098319)
Optical fiber connection error (198092292)
Device power down (198092295)
Software runs abnormally (198097604)
Board communication link interrupted (198097060)
Board hardware fault (198097004)
Parameter configuration error (198097511)
c.
Check whether the alarms are cleared.

Yes -> End.
No -> Step 2.

a. Check whether related alarms are raised. If they are raised, resolve the faults in
follows:
Parameter configuration error (198098464)
Yes -> End.
No -> Step 3.
Yes -> End.
No -> Step 4.
4. Power off reset the board in accordance with the slot, shelf, and rack information in
the Detail Information dialog box. Refer to Reset Boards.
Yes -> End.
2-52
SJ-20141022095204-005|2015-07-27 (R2.2)
No -> Contact ZTE technical support.
2.28 198097613 LMT is logged in

Alarm Information
l
l
l
l

Name: LMT is logged in
Alarm severity: Warning
Alarm Description
The alarm occurs when LMT is logged in.
Alarm Cause
LMT is logged in.
Impact
None.
None.
Action
1. Check whether the connected LMT is authorized by the carrier.
YesEnd.
NoStep 2.
2. Select Dynamic Management > Dynamic Command > SDR > Managed Network
Element > LMT. The LMT tab is displayed. Disconnect the LMT.
YesEnd.
2.29 198097650 Configuration Data Loading Abnormal

Alarm Information
l
l
l

Name: Configuration Data Loading Abnormal
2-53
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
Action
Select Configuration Management > Data Synchronization.
The Data
Synchronization dialog box is displayed. Start an incremental synchronization or a
whole table synchronization operation.
YesEnd.
2.30 198097651 Configuration data unmatched with

the license
Alarm Information
l
l
l
l

Name: Configuration data unmatched with the license
Alarm Description
This alarm occurs when a configured value is different from the corresponding effective
value permitted by the license.
2-54
SJ-20141022095204-005|2015-07-27 (R2.2)
Alarm Cause
A configured value is different as the corresponding effective value permitted by the
license.
Impact
None.
Some or all of the services on the base station are blocked.
Action
1. Verify that the configuration data is consistent with the effective data.
a. Select LTE eNodeB Level License Management -> Query License Authentication
Result. In the query results, check whether the configuration data is consistent
with the effective data.
b. If the configured value of any parameter is different from the effective value, modify
the parameter value according to the rules specified in the license.
c.
Send the configuration data to the NE.
d. Wait for 15 minutes and check whether the alarm is cleared.

YesEnd.
NoStep 2.
2. Apply for a new license.
a. After obtaining the new license file, select LTE eNodeB Level License
Management -> Load License File and load the new license.
b. Wait for 15 minutes and check whether the alarm is cleared.
YesEnd.
2.31 198097670 The system has no the available

License file
Alarm Information
l
l
l
l

Name: The system has no the available License file
2-55
SJ-20141022095204-005|2015-07-27 (R2.2)
The License authentication File has not been loaded to the eNodeB.
Alarm Cause
The system support capacity is limited.
Impact
None.
The system operates in the minimum support capacity. All optional functions are disabled,
and the default capacity is provided.
Action
1. Verify that there is an available license file.
a. Check whether there is an available license file.
YesStep 2.
NoStep b.
b. Contact the vendor and apply for a license file.
2. Select LTE eNodeB Level License Management > Load License File and load the
new license.
YesEnd.
2.32 198097673 The license file will soon fall due

Alarm Information
l
l
l
l

Name: The license file will soon fall due
The license file will soon fall due.
Alarm Cause
2-56
SJ-20141022095204-005|2015-07-27 (R2.2)
Impact
None.
After the license file expires, maybe part or all of the services carried on this base station
are blocked.
Action
1. Contact the vendor and apply for a license file again.
2. Select LTE eNodeB Level License Management > Load License File, and load the
license file again.
YesEnd.
2.33 198098464 Parameter configuration error

Alarm Information
l
l
l
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
Parameters are configured incorrectly.
Impact
None.
Some or all of the services on the board may be interrupted or the service quality may be
affected.
2-57
SJ-20141022095204-005|2015-07-27 (R2.2)
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/The interval between frequency points
is too far.
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.
NoStep 2.
and 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.
YesEnd.
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
RRURF device SetRF Port ObjectTx/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.
YesStep 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
NoSubstep b.
b. Select Configuration Management > Managed Element > Radio
Parameter, and modify the frequency point configurations of the carrier of
the corresponding wireless standards as planned.
c.

2-58
SJ-20141022095204-005|2015-07-27 (R2.2)
YesEnd.
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.
NoStep 2.
2. Modify the attenuation level of the static power of the carrier to 12 dB.
YesEnd.
Failure in IQ parameter configuration:

1. Re-configure the IQ data code.
Cabinet (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.
c.

YesEnd.
NoStep 2.
2. Re-configure the rate of the optical interface.

Cabinet (For example, B8200) > Optical Port Device Set > Optical Port
Device, and modify the rate of the optical interface to that supported by the
RRU according to the rack number/shelf number/slot number in the alarm
details.
c.

YesEnd.
Failure in carrier power configuration:

Verify that the carrier power is configured correctly.
2-59
SJ-20141022095204-005|2015-07-27 (R2.2)

and check whether the sum of the carrier power configured for each single channel
exceeds the rated power.
YesStep 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.
YesEnd.
l
The total power exceeding the rated power:

and 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.
YesEnd.
No wireless configurations:
and modify the carrier configurations to ensure that each RRU channel is
configured with at least one carrier.
YesEnd.
Failure in configuration of wireless frequency point interference parameters:

and 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.
YesEnd.
Failure in delay parameter configuration:

Contact the customer service center.
2-60
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
YesEnd.
2.34 198100275 RRU software version is abnormal

Alarm Information
l
l
l
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.
2-61
SJ-20141022095204-005|2015-07-27 (R2.2)
3. The software version file is excessively large.
Impact
None.
None.
Action
1. Select Software Version Management > Upgrade Management. The Upgrade
Management tab is displayed. Re-download all version packages planned for the
current network.
YesEnd.
NoStep 2.
2. Reset the board in accordance with the Rack Number, Shelf Number, and Slot Number
in alarm details. 15 minutes, check whether the alarm is cleared.
YesEnd.
2.35 198100276 RRU fiber delay beyond the limit

Alarm Information
l
l
l
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.
2-62
SJ-20141022095204-005|2015-07-27 (R2.2)
All the services on the RRU may be interrupted.
Action
l
If the "Difference in length of two uplink optical lines" prompt is displayed, perform the
following operations:
1. Replace them by two RRU optical fibers of equal length.
YesEnd.
If the "Difference in length of two uplink optical lines" prompt is not displayed, perform
the following operations:
1. Adjust the fiber delay timing advance TA.
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 details and the measured TA value in the additional
alarm information in the alarm details.
c.

YesEnd.
NoStep 2.
2. Shorten the length of the optical fiber according to the actual requirements.
YesEnd.
2.36 198094815 Rule library of performance statistics

hasn't been loaded or loaded unsuccessfully
Alarm Information
l
l
l
l

Name: Rule library of performance statistics hasn't been loaded or loaded
unsuccessfully
2-63
SJ-20141022095204-005|2015-07-27 (R2.2)
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.37 198094838 Cell parameter configuration failure

Alarm Information
l
l
l
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.
The parameter configuration of the equipment is inconsistent with that of the NMS. There
is no impact on services.
2-64
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
a. Select Configuration ManagementRadio ParameterLTE TDDE-UTRAN
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.

YesEnd.
NoContact technical support.
3. Check user plane parameters.

Service Configuration, check user plane-related parameters, and modify as
required.
c.

YesEnd.
4. Check RRU-related parameter configuration.

TDD Cell, check RRU-related parameters (for example, frequency point) in the
cell records, and modify as required.
c.

YesEnd.
2.38 198094858 Cell shutdown alarm

Alarm Information
l
l
l
l

Name: Cell shutdown alarm
2-65
SJ-20141022095204-005|2015-07-27 (R2.2)
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 ManagementLTE TDDE-UTRAN TDD CellStart Up Cell, select
and start up the alarmed cell.
YesEnd.
2-66
SJ-20141022095204-005|2015-07-27 (R2.2)
Chapter 3
QoS Alarm
Table of Contents
198092368 Ethernet RDI alarm ..................................................................................3-1
198092380 The EFM link is broken ............................................................................3-2
198096837 GNSS receiver satellite searching fault ....................................................3-4
198097174 The operator certificate fails to be obtained..............................................3-6
198097672 System capacity overload ........................................................................3-8
198094826 PCI conflict alarm.....................................................................................3-9
198094827 PCI confusion alarm...............................................................................3-10
198094832 LTE cell outage ......................................................................................3-12
198094833 eNodeB is out of service ........................................................................3-14
198094834 Wireless interference detection is abnormal ...........................................3-16
198094835 Cell portion of super cell is out of service ...............................................3-17
198094842 MRO fault alarm.....................................................................................3-19
198094843 Different vendor PCI conflict alarm.........................................................3-20
198094844 Different vendor PCI confusion alarm.....................................................3-22
198094853 Cell sleeping alarm ................................................................................3-23
198094854 Cell performance deterioration alarm .....................................................3-24
198094855 Cell cooperating parameter configuration abnormal ...............................3-26
198094856 The system capacity will exceed the License limit ..................................3-27
3.1 198092368 Ethernet RDI alarm

Alarm Information
l
l
l
l

Name: Ethernet RDI alarm
Alarm type: Qos 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.
3-1
SJ-20141022095204-005|2015-07-27 (R2.2)
Impact
None.
The Ethernet link may be broken, and services are affected.
Action
1. Ensure that the CFM parameters are correctly set.
a. Select
Configuration
ManagementManaged
ElementTransmission
NetworkRadio Standard (such as UMTS)Network DetectionMD/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.
YesStep 2.
NoSubstep b.
b. Change the settings of the CFM parameters at the local end to be the same as
the network planning.
c.
Synchronize the configuration to the NE.
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.
YesEnd.
NoStep 2.
2. Check whether the settings of the CFM parameters of all network devices match the
network planning.
NoChange the settings to be the same as the network planning.
3.2 198092380 The EFM link is broken

Alarm Information
l
l
l
l

Name: The EFM link is broken
3-2
SJ-20141022095204-005|2015-07-27 (R2.2)
Chapter 3 QoS Alarm
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. The physical Ethernet link is not connected properly.
None.
Action
1. Ensure that the local EFM parameters are correctly set.
a. Select
Configuration
ManagementManaged
ElementTransmission
NetworkRadio Standard (such as UMTS)Network DetectionEthernet
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.
YesStep 2.
NoSubstep b.
b. Change the settings of the EFM parameters at the local end to be the same as the
network planning.
c.
d. Wait 15 minutes, and check whether the alarm is cleared.

YesEnd.
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.
YesStep 3.
NoSubstep b.
b. Change the settings of the peer EFM parameters to be the same as the network
planning.
c.

YesEnd.
NoStep 3.
3-3
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
YesStep 4.
NoSubstep b.
b. Replace the board based on the rack number/shelf number/slot number in the
Detail Information dialog box.
Wait 30 minutes, and check whether the notification is reported again.
YesStep 4.
NoEnd.
4. Ensure that the cable connector of the local device is secured.
a. Check whether the cable connector of the local device is loose.
YesSubstep b.
NoStep 5.
b. Reconnect the cable.
Wait 15 minutes, and check whether the notification is raised again.
YesStep 6.
NoEnd.
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.
YesStep 6.
NoSubstep b.
b. Replace the cable.
YesStep 6.
NoEnd.
6. Inform the maintenance personnel of the peer device to check whether the interface,
cable, and device are operating properly.
NoResolve the peer device fault.
3.3 198096837 GNSS receiver satellite searching fault

Alarm Information
l
l

Name: GNSS receiver satellite searching fault
3-4
SJ-20141022095204-005|2015-07-27 (R2.2)
Chapter 3 QoS Alarm
l
l

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.
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
1. Check whether the antenna and feeder are blocked by a structure.
YesStep 2.
NoStep 3.
2. Move the antenna of the GNSS to another place or remove the structure that blocks
the signal.
YesEnd.
NoStep 3.
3. Check whether there is a GNSS interference source in the neighboring environment.
YesStep 4.
NoStep 5.
4. Remove the interference source.
YesEnd.
NoStep 5.
5. Replace the GNSS antenna.
3-5
SJ-20141022095204-005|2015-07-27 (R2.2)

Yes End.
NoStep 6.
6. Reset the receiver.
a. Select Configuration ManagementManaged ElementDeviceB8200,
clock source. Select ClockDevice SetClock Device, check whether the GNSS
receiver is UCI_RGPS.
YesSubstep b.
NoStep 7.
b. Select Dynamic ManagementDynamic Command -> SDRManaged 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.
YesEnd.
NoStep 7.
7. Reset the board based on the Rack Number, Shelf Number and Slot Number in alarm
details. Refer to Reset Boards.
YesEnd.
NoStep 8.
YesEnd.
3.4 198097174 The operator certificate fails to be

obtained
Alarm Information
l
l
l
l

Name: The operator certificate fails to be obtained
Alarm type: QoS alarm
3-6
SJ-20141022095204-005|2015-07-27 (R2.2)
Chapter 3 QoS Alarm
This alarm occurs when the initial application or update of the base station operator
certificate fails.
Alarm Cause
l
l
The parameters about the certificate management protocol are incorrectly configured.
The communication link fails.
Impact
None.
If IPsec is configured, maybe IPsec connections cannot be established, and all service
messages on IPsec channels cannot be transmitted or received normally.
Action
1. Verify that the parameters about the certificate management protocol are correctly
configured.
Network > LTE FDD (for example) > Network Security > Certificate
Management Protocol Configuration, and check whether the following
parameters are configured to the same values as the existing network planning:
transmission protocol type, CA server type, IP address of CA server, transport
layer port of CA server, CA server path, domain name of base station certificate,
domain name of base station certificate's issuer, and private key length of base
station certificate.
YesStep 2.
NoSubstep b.
b. Modify the parameters about the certificate management protocol in accordance
with the existing network planning.
c.
Synchronize configuration data to the corresponding NE.
d. After 15 minutes, check whether this alarm is cleared.

YesEnd.
NoStep 2.
2. Ask opposite-end maintenance personnel to verify that the configuration data of the
certificate management protocol is correct.
After 15 minutes, check whether this alarm is cleared.
YesEnd.
3-7
SJ-20141022095204-005|2015-07-27 (R2.2)
NoStep 3.
3. Verify that the transmission addresses of the local end and opposite end can be
accessed.
a. Perform a ping command to the server address, and check whether responses
are received.
NoSubstep b.
b. Check whether the IP addresses of the nodes (BSC, RNC, and switching
equipment) along the transmission path and the routing entries are correct based
on the network planning.
NoSubstep c.
c.
Correctly configure the IP addresses of the nodes (BSC, RNC, and switching
equipment) along the transmission path and the routing entries based on the
network planning.
After 15 minutes, check whether this alarm is cleared.
YesEnd.
3.5 198097672 System capacity overload

Alarm Information
l
l
l
l

Name: System capacity overload
The system capacity will exceed the license limit soon.
Alarm Cause
Impact
None.
FDD uplink traffic overload: affecting user access.
3-8
SJ-20141022095204-005|2015-07-27 (R2.2)
Chapter 3 QoS Alarm
FDD downlink traffic overload: affecting user access.
Action
2. Select LTE eNodeB Level License Management -> Load License File, and load the
license file again.
YesEnd.
3.6 198094826 PCI conflict alarm

Alarm Information
l
l
l
l

Name: PCI conflict alarm
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 SON Management -> 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".
YesSubstep c.
NoStep 2.
3-9
SJ-20141022095204-005|2015-07-27 (R2.2)
c.
Check whether the "Resolving PCI Conflict or Confusion at The Appointed Time
Switch" function for the PCI policy is "Open".
YesSubstep d.
NoSubstep e.
d. Check "The Appointed Time Used to Resolving PCI Conflict or Confusion". When
the time expires, check whether the alarm is cleared.
YesEnd.
e. Wait for 15 minutes. Select SON Management -> SON Management Tree -> SON
Monitor Management -> Real-Time Monitoring -> Optimization Monitoring, and
check whether something related to PCI exists.
YesSubstep f.
NoSubstep g.
f.
Wait until the PCI-related information on the self optimization monitoring interface
is cleared.
g. Check whether the alarm is cleared.

YesEnd.
2. Wait in controlled mode of the PCI policy and check whether the alarm is cleared.
YesEnd.
3.7 198094827 PCI confusion alarm

Alarm Information
l
l
l
l

Name: PCI confusion alarm
Two neighborhood cells of a certain cell have the identical physical cell ID configuration.
Alarm Cause
3-10
SJ-20141022095204-005|2015-07-27 (R2.2)
Chapter 3 QoS Alarm
Impact
I. Board status:
Operates properly.
Action
YesSubstep c.
NoStep 2.
c.
YesSubstep d.
NoSubstep e.
YesEnd.
YesSubstep f.
NoSubstep g.
f.
is cleared.

YesEnd.
YesEnd.
3-11
SJ-20141022095204-005|2015-07-27 (R2.2)
3.8 198094832 LTE cell outage

Alarm Information
l
l
l
l

Name: LTE cell outage
When LTE cell is deleted or failure is detected, this alarm is reported.
Alarm Cause
1. The S1 link is faulty.
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.
The services in the cell are interrupted.
Action
1. View alarm details and find the cause of the alarm.
"Caused by S1 link fault"Step 2.
"Caused by CC board fault"Step 3.
"Caused by clock is unlocked"Step 4.
"Caused by BP board fault"Step 5.
"Caused by RRU board fault"Step 6.
"Caused by cell configuration fault"Step 7.
"Caused by Cell portion outage" -> Step 8.
"Cell error"Contact technical support.
2. Check whether S1-related alarms exist.
a. Check whether the following alarms exist. If yes, remove them according to
corresponding handling suggestions. The related alarm is as follows:
S1 link is broken (198094830)
3-12
SJ-20141022095204-005|2015-07-27 (R2.2)
Chapter 3 QoS Alarm

YesEnd.
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)
YesEnd.
4. Check whether clock-related alarms exist.
eNodeB synchronization abnormal (198094829)
YesEnd.
5. Check whether BP board-related alarms exist.
YesEnd.
6. Check whether RRU-related alarms exist.
3-13
SJ-20141022095204-005|2015-07-27 (R2.2)

The RRU link is broken (198097605)
Temperature abnormal (198098466)
YesEnd.
7. Further check alarm details.
a. Follow the alarm prompt to find and modify related configurations in Configuration
Management.
c.

YesEnd.

a. Check whether the following alarms exist in History Alarm List. If yes, remove
them according to corresponding handling suggestions. The related alarm is as
follows:
Cell portion of super cell is out of service (198094835)
YesEnd.
3.9 198094833 eNodeB is out of service

Alarm Information
l
l
l
l

Name: eNodeB is out of service
When the eNB is unavailable caused by fault, this alarm will be reported.
3-14
SJ-20141022095204-005|2015-07-27 (R2.2)
Chapter 3 QoS Alarm
Alarm Cause
There is no available S1 link, CC board or external reference clock.
Impact
I. Board status:
Operates properly.
The eNodeB fails to provide services.
Action
1. Check whether the eNodeB is configured with S1AP.
a. Select Configuration Management -> Radio Parameter -> LTE FDD -> Resource
Interface Configuration -> S1AP, and check whether there is S1AP record
available.
YesStep 2.
NoSubstep b.
b. Add an available S1AP record in the list.
c.
Synchronize the configuration data to the eNodeB, wait 5 minutes and check
YesEnd.
NoStep 2.
2. Check whether S1-related alarms exist.

YesEnd.
NoStep 3.
3. Check whether CC board-related alarms exist.
YesEnd.
NoStep 4.
3-15
SJ-20141022095204-005|2015-07-27 (R2.2)

YesEnd.
3.10 198094834 Wireless interference detection is

abnormal
Alarm Information
l
l
l
l

Name: Wireless interference detection is abnormal
When uplink service receives same frequency interference, this alarm is reported.
Alarm Cause
1. The uplink subframe is interfered and the NI value exceeds the limit.
2. The guard period (GP) for this eNodeB is interfered and the NI value exceeds the limit.
Impact
I. Board status:
Operates properly.
The services that the cell bears may be affected and the service quality is degraded.
Action
1. Check whether related alarms exist in neighboring stations.
a. Check whether related alarms exist in neighboring stations. If such alarms exist,
remove them based on the corresponding handling suggestion. The related alarm
is as follows:
3-16
SJ-20141022095204-005|2015-07-27 (R2.2)
Chapter 3 QoS Alarm
YesEnd.
NoStep 2.
2. Check the uplink and downlink subframe distribution configuration of the
intra-frequency neighboring cells.
TDD Cell, and check whether "Uplink-Downlink Subframe Configuration" of the
intra-frequency neighboring cell is different from that of this cell.
YesSubstep b.
NoStep 3.
b. Modify "Uplink-Downlink Subframe Configuration" of the intra-frequency
neighboring cell for consistency.
c.
Synchronize the configuration data to the eNodeB.
d. Check whether the alarm is cleared.

YesEnd.
NoStep 3.
3. Check the frequency band adjustment parameters configured in the intra-frequency
neighboring cell.
a. Select Configuration ManagementSystem ParameterFrequency adjust
configuration, and check whether the configurations of the "Adjust Mode Of
Frequency" and "Adjust Value Of Frequency" parameters are consistent with
each other.
YesContact technical support.
NoSubstep b.
b. Select Configuration ManagementSystem ParameterFrequency adjust
configuration, and modify the configurations of the "Adjust Mode Of Frequency"
and "Adjust Value Of Frequency" parameters for consistency with those of the
intra-frequency eNodeB according to the configuration manual.
c.
d. Check whether the alarm is cleared.

YesEnd.
3.11 198094835 Cell portion of super cell is out of

service
Alarm Information
l

3-17
SJ-20141022095204-005|2015-07-27 (R2.2)
l
l
l
Name: Cell portion of super cell is out of service

Cell portion of supper cell is out of service due to resource allocation failure or hardware
fault.
Alarm Cause
1. Baseband unit is at fault.
2. Radio frequency unit is at fault.
3. The Configuration of baseband unit or radio frequency unit is failed.
Impact
I. Board status:
Operates properly.
Service in CP will be interfered.
Action
"Caused by baseband unit fault"Step 2.
"Caused by radio frequency unit fault"Step 3.
"Caused by configuration failure"Step 4.
2. Check whether baseband-unit-related alarms exist.
Initialization failure (198092070)198092070
YesEnd.
3-18
SJ-20141022095204-005|2015-07-27 (R2.2)
Chapter 3 QoS Alarm
3. Check whether radio-frequency-unit-related alarms exist.

Board communication link interrupted (198097060)198097060
Board hardware fault (198097004)198097004
The RRU link is broken (198097605)198097605
Temperature abnormal (198098466)198098466
YesEnd.
4. Further check alarm details.
a. Follow the alarm prompt to find and modify related configurations in Configuration
Management.
c.

YesEnd.
3.12 198094842 MRO fault alarm

Alarm Information
l
l
l
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.
3-19
SJ-20141022095204-005|2015-07-27 (R2.2)
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
"Unknown"Contact technical support.
"Too early HO"Step 2.
"Too late HO"Step 2.
"HO to wrong cell"Step 2.
"Ping-pong HO"Step 2.
2. Check SON-related MRO policies.
-> SON Policy Query, and query the MRO policy for the alarmed eNodeB.
b. Wait until "Minimum interval between automatic MOR parameter optimizations" in
the MRO policy expires, and check whether the alarm is cleared.
YesEnd.
3.13 198094843 Different vendor PCI conflict alarm

Alarm Information
l
l
l
l

Name: Different vendor PCI conflict alarm
The physical cell ID of neighborhood cell is identical.
3-20
SJ-20141022095204-005|2015-07-27 (R2.2)
Chapter 3 QoS Alarm
Alarm Cause
Impact
I. Board status:
Operates properly.
Action
YesSubstep c.
NoStep 2.
c.
YesSubstep d.
NoSubstep e.
YesEnd.
YesSubstep f.
NoSubstep g.
f.
is cleared.

YesEnd.
3-21
SJ-20141022095204-005|2015-07-27 (R2.2)
YesEnd.
3.14 198094844 Different vendor PCI confusion alarm

Alarm Information
l
l
l
l

Name: Different vendor 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
YesSubstep c.
NoStep 2.
c.
YesSubstep d.
NoSubstep e.
YesEnd.
3-22
SJ-20141022095204-005|2015-07-27 (R2.2)
Chapter 3 QoS Alarm

YesSubstep f.
NoSubstep g.
f.
is cleared.

YesEnd.
YesEnd.
3.15 198094853 Cell sleeping alarm

Alarm Information
l
l
l
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.
3-23
SJ-20141022095204-005|2015-07-27 (R2.2)
-> 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".
YesStep 2.
NoStep 3.
2. Wait for five minutes, and check whether the alarm is cleared.
YesEnd.
3. Delete the cell manually and re-establish a cell through the NMS.
a. Select Dynamic ManagementLTE TDDE-UTRAN TDD CellImmediately
Shut Down Cell, and shut down the alarmed cell.
b. Select Dynamic ManagementLTE TDDE-UTRAN TDD CellStart Up Cell,
c.

YesEnd.
3.16 198094854 Cell performance deterioration alarm

Alarm Information
l
l
l
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.
3-24
SJ-20141022095204-005|2015-07-27 (R2.2)
Chapter 3 QoS Alarm
The service quality in the cell is degraded.
Action
1. Check SON-related self-healing policies.
-> 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".
YesStep 2.
NoSubstep c.
c.
Check whether the "KPI Cell Self-healing Switch" function for the self-healing
policy is "Open".
YesStep 3.
NoSubstep d.
d. Check whether the "Switch of Determined Mobility Parameter Change for Outage
Cell Based on KPI" function for the self-healing policy is "Open".
YesStep 2.
NoStep 4.
2. Wait until "The Period of Waiting for Manual Recovering Performance Fault Cell Timer"
expires and check whether the alarm is cleared.
YesEnd.
3. Wait for about an hour and check whether the alarm is cleared.
YesEnd.
4. Delete the cell manually and re-establish a cell through the NMS.
a. Select Dynamic ManagementLTE TDDE-UTRAN TDD CellImmediately
Shut Down Cell, and shut down the alarmed cell.
b. Select Dynamic ManagementLTE TDDE-UTRAN TDD CellStart Up Cell,
c.
Wait for fifteen minutes, and check whether the alarm is cleared.
YesEnd.
3-25
SJ-20141022095204-005|2015-07-27 (R2.2)
3.17 198094855 Cell cooperating parameter

configuration abnormal
Alarm Information
l
l
l
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:
Operates properly.
Cell coordination fails to function properly.
Action
1. Select Configuration ManagementCell Coordination, and check whether there are
inconsistent parameter configurations for cell coordination.
YesStep 2.
2. Correct parameter configurations according to the check results.
3. Synchronize the configuration data to the eNodeB.
YesEnd.
3-26
SJ-20141022095204-005|2015-07-27 (R2.2)
Chapter 3 QoS Alarm
3.18 198094856 The system capacity will exceed the

License limit
Alarm Information
l
l
l
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.
YesEnd.
3-27
SJ-20141022095204-005|2015-07-27 (R2.2)
3-28
SJ-20141022095204-005|2015-07-27 (R2.2)
Chapter 4
Environment Alarm
Table of Contents
198092042 The temperature at the air intake is abnormal ..........................................4-1
198092044 Door control alarm ...................................................................................4-3
198092045 Flooding alarm .........................................................................................4-5
198092046 Smog alarm .............................................................................................4-7
198092047 Infrared alarm ........................................................................................4-10
198092048 Air conditioner fault ................................................................................4-12
198092053 The input voltage is abnormal ................................................................4-14
198092105 Embedded power Environment is under-temperature.............................4-16
198092106 Embedded power Environment is over-temperature...............................4-18
198092107 Embedded power Environment temperature is invalid............................4-19
198092108 Embedded power Environment is under-Humidity..................................4-20
198092109 Embedded power Environment is over-Humidity ....................................4-22
198092110 Embedded power Environment humidity is invalid..................................4-23
198092111 Embedded power Smoke detected.........................................................4-24
198092112 Embedded power Flood detected...........................................................4-26
198092113 Embedded power Door Magnet Alarm....................................................4-27
198092114 Embedded power Gate Embedded power Safety Alarm .........................4-28
198092115 Glass Broken Alarm ...............................................................................4-30
198092118 Embedded power Env-unit communication interruption ..........................4-32
198092119 Embedded power Heat Exchanger Fault ................................................4-33
198092462 Blocked dust proof net ...........................................................................4-35
198097061 Temperature abnormal...........................................................................4-36
198098128 Power over-loaded ................................................................................4-38
198092550~198092599 Battery pack fan failed. .......................................................4-39
4.1 198092042 The temperature at the air intake is

abnormal
Alarm Information
l
l
l
l

Name: The temperature at the air intake is abnormal
Alarm type: Environment Alarm
4-1
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
2. The environment temperature is too high.
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.
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 ManagementManaged ElementDevice -> BBU (such as
B8200)SA/PSA/FABEnvironment 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
c.

YesEnd.
NoStep 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.
YesEnd.
4-2
SJ-20141022095204-005|2015-07-27 (R2.2)
Chapter 4 Environment Alarm
NoStep 3.
3. Ensure that the air intake of the equipment is not blocked or clean the air filter.
YesEnd.
4.2 198092044 Door control alarm

Alarm Information
l
l
l
l

Name: Door control alarm
Alarm Description
This alarm is reported when a door control sensor is used but the door is not closed.
Alarm Cause
1. The normally open or closed setting of the alarm related to the dry contact is not correctly
set.
2. The door is not closed.
3. The cable is not correctly connected or the cable is faulty.
4. The environmental monitoring unit 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
1. Check the dry contact setting.
a. Select Configuration ManagementManaged ElementDeviceBBU (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
4-3
SJ-20141022095204-005|2015-07-27 (R2.2)
YesStep 2.
No Substep b.
b. Select Configuration ManagementManaged ElementDeviceBBU (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.
c.

YesEnd.
NoStep 2.
2. Check the door control.
a. Check whether the door control is in closed status.
Yes Step 3.
NoSubstep b.
b. Ensure that the door control is in closed status.
YesEnd.
NoStep 3.
3. Check the cable connected to the sensor.
a. Check whether the cable to the sensor is correctly connected (for example,
whether the interface is secured).
YesSubstep c.
NoSubstep b.
b. Re-connect the cable.
YesEnd.
NoSubstep c.
c.
Check whether the cable is in good condition.

YesStep 4.
NoSubstep d.
d. Replace the cable with a proper one.

YesEnd.
NoStep 4.
4-4
SJ-20141022095204-005|2015-07-27 (R2.2)
4. Replace the door control sensor.

YesEnd.
NoStep 5.
Information dialog box.
Wait 15 minutes, and check whether the alarm is cleared. Refer to Reset Boards.
YesEnd.
NoStep 6.
6. Replace the board in accordance with the slot, shelf, and rack information in the Detail
Wait 15 minutes, and check whether the alarm is cleared. the customer service center.
4.3 198092045 Flooding alarm

Alarm Information
l
l
l
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.
3. The cable is not correctly connected or is faulty.
Impact
The devices may be damaged if they are flooded.
4-5
SJ-20141022095204-005|2015-07-27 (R2.2)
If any devices are damaged, all or some of the services on this base station may be
Action
YesStep 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
c.

YesEnd.
NoStep 2.
2. Ensure that the base station is not flooded with water.
a. Check whether the base station is flooded with water.
YesSubstep b.
No Step 3.
b. Switch off the base station and drain away water. Power on the device after it is
dry.
YesEnd.
NoStep 3.
a. Check whether the cable to the sensor is correctly connected (for example,
YesSubstep c.
NoSubstep b.
4-6
SJ-20141022095204-005|2015-07-27 (R2.2)
YesEnd.
NoSubstep c.
c.

Yes Step 4.
NoSubstep d.

YesEnd.
NoStep 4.
4. Replace the flooded sensor.
YesEnd.
NoStep 5.
YesEnd.
NoStep 6.
Information dialog box. 15 minutes, and check whether the alarm is cleared.
YesEnd.
4.4 198092046 Smog alarm

Alarm Information
l
l
l
l

Name: Smog alarm
Alarm Description
This alarm is reported when the smog sensor connected at a dry contact detects a smog
situation.
4-7
SJ-20141022095204-005|2015-07-27 (R2.2)
Alarm Cause
set.
2. The base station detects smoke.
Impact
If any fire hazards exist, the devices may be damaged.
Action
YesStep 2.
No Substep b.
c.

YesEnd.
NoStep 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.
YesSubstep b.
NoStep 3.
4-8
SJ-20141022095204-005|2015-07-27 (R2.2)
b. Check whether the smoke source may potentially affect the normal operation of
the device.
YesSubstep c.
NoSubstep 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.
YesEnd.
NoStep 3.
d. Remove the smoke source.

YesEnd.
NoStep 3.
a. Check whether the cable is correctly connected (for example, whether the interface
is secured).
YesSubstep c.
NoSubstep b.
YesEnd.
NoSubstep c.
c.

YesStep 4.
NoSubstep d.

YesEnd.
NoStep 4.
4. Replace the smoke sensor.
YesEnd.
NoStep 5.
4-9
SJ-20141022095204-005|2015-07-27 (R2.2)

YesEnd.
NoStep 6.
4.5 198092047 Infrared alarm

Alarm Information
l
l
l
l

Name: Infrared alarm
Alarm Description
None.
Alarm Cause
set.
2. Some unauthorized persons or animals enter the equipment room.
Impact
Action
4-10
SJ-20141022095204-005|2015-07-27 (R2.2)
YesStep 2.
No Substep b.
c.

YesEnd.
NoStep 2.
2. Ensure that no unauthorized persons or animals enter the equipment room.
a. Check whether some persons or animals enter the equipment room.
YesSubstep b.
NoStep 3.
b. Check whether the persons are authorized.
YesEnd.
NoSubstep c.
c.
Make the persons or animals leave the equipment room.

YesEnd.
NoStep 3.

is secured).
YesSubstep c.
NoSubstep b.
YesEnd.
NoSubstep c.
c.

Yes Step 4.
4-11
SJ-20141022095204-005|2015-07-27 (R2.2)
NoSubstep d.
YesEnd.
NoStep 4.
4. Replace the infrared sensor.
YesEnd.
NoStep 5.
YesEnd.
NoStep 6.
YesEnd.
4.6 198092048 Air conditioner fault

Alarm Information
l
l
l
l

Name: Air conditioner fault
Alarm Description
None.
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 air conditioner is faulty.
4. The monitoring unit is faulty.
4-12
SJ-20141022095204-005|2015-07-27 (R2.2)
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
1. Check the dry contact configuration.
a. Select Configuration ManagementManaged ElementDeviceB8200, and
check whether the alarm status of the dry contact device is the same as the
alarm status in the really connected contact device in accordance with the Rack
Number, Shelf Number, and Slot Number in the alarm details.
YesStep 2.
NoSubstep b.
b. Select Configuration ManagementManaged ElementDeviceB8200, 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.
c.

YesEnd.
NoStep 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).
YesSubstep c.
NoSubstep b.
b. Connect the dry contact cable properly.
YesEnd.
No Substep c.
c.
c.Check whether the dry contact cable is in good condition.

YesStep 3.
NoSubstep d.
4-13
SJ-20141022095204-005|2015-07-27 (R2.2)
d. Change a dry contact cable.

YesEnd.
NoStep 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).
YesSubstep b.
NoStep 4.
b. Connect the air conditioner power cable correctly.
YesEnd.
NoStep 4.
4. Change an air conditioner.
YesEnd.
NoStep 5.
YesEnd.
No Step 6.
YesEnd.
4.7 198092053 The input voltage is abnormal

Alarm Information
l
l
l
l

Name: The input voltage is abnormal
4-14
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
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 ManagementManaged ElementDevice -> 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).
YesStep 2.
NoSubstep 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.
c.

YesEnd.
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.
4-15
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
YesSubstep 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.
YesEnd.
Other types of boards:

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.
YesSubstep 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.
YesEnd.
4.8 198092105 Embedded power Environment is

under-temperature
Alarm Information
l
l
l
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.
4-16
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
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 environment temperature is higher than the lower environment
temperature threshold.
a. Log in to the real-time information window of the embedded power monitoring
module, and check the environment temperature.
b. Check whether the environment temperature is lower than the lower environment
temperature threshold (default: -5 ).
YesSubstep c.
NoStep 2.
c.
Improve the ventilation (for example, ensuring the proper functioning of air
conditioners and high-power heating devices).
d. Wait 15 minutes and check whether the alarm is cleared.

YesEnd.
NoStep 2.
2. Replace the temperature sensor.
YesEnd.
NoStep 3.
3. Replace the monitoring unit. 15 minutes, check whether the alarm is cleared.
YesEnd.
4-17
SJ-20141022095204-005|2015-07-27 (R2.2)

over-temperature
Alarm Information
l
l
l
l

Name: Embedded power Environment is over-temperature
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 ).
YesSubstep c.
NoStep 2.
c.

4-18
SJ-20141022095204-005|2015-07-27 (R2.2)
YesEnd.
NoStep 2.
YesEnd.
NoStep 3.
YesEnd.
4.10 198092107 Embedded power Environment

temperature is invalid
Alarm Information
l
l
l
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.
4-19
SJ-20141022095204-005|2015-07-27 (R2.2)
YesStep 2.
NoSubstep b.
b. Reconnect the temperature sensor.
YesEnd.
NoStep 2.
YesEnd.
NoStep 3.
3. Verify that the monitoring unit is properly connected.
a. Check whether the monitoring unit is properly connected.
YesStep 4.
NoSubstep b.
b. Connect the monitoring unit properly.
YesEnd.
No Step 4.
YesEnd.

under-Humidity
Alarm Information
l
l
l
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.
4-20
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
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%).
YesStep 2.
NoStep 3.
2. Improve the ventilation (for example, ensuring the proper functioning of air
conditioners).
YesEnd.
NoStep 3.
3. Replace the humidity sensor.
YesEnd.
NoStep 4.
Yes End.
4-21
SJ-20141022095204-005|2015-07-27 (R2.2)

over-Humidity
Alarm Information
l
l
l
l

Name: Embedded power Environment is over-Humidity
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%).
YesStep 2.
NoStep 3.
2. Improve the ventilation (for example, ensuring the proper functioning of air
conditioners).
4-22
SJ-20141022095204-005|2015-07-27 (R2.2)
YesEnd.
NoStep 3.
YesEnd.
NoStep 4.
Yes End.
4.13 198092110 Embedded power Environment

humidity is invalid
Alarm Information
l
l
l
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
4-23
SJ-20141022095204-005|2015-07-27 (R2.2)
Action
1. Verify that the humidity sensor is properly connected.
a. Check whether the humidity sensor is properly connected.
YesStep 2.
NoSubstep b.
b. Reconnect the humidity sensor.
YesEnd.
NoStep 2.
YesEnd.
NoStep 3.
YesStep 4.
NoSubstep b.
b. Connect the monitoring unit properly. After 15 minutes, check whether the alarm
is cleared.
YesEnd.
No Step 4.
YesEnd.
4.14 198092111 Embedded power Smoke detected

Alarm Information
l
l
l
l

Name: Embedded power Smoke detected
Alarm Description
This alarm occurs when the sensor detects smoke.
4-24
SJ-20141022095204-005|2015-07-27 (R2.2)
Alarm Cause
1. Smoke alarms are reported.
2. The smoke sensor is faulty.
Impact
If any fire hazards exist, the devices may be damaged.
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.
YesSubstep b.
NoStep 2.
b. Check whether there are potential risks at the smoke source that may affect the
normal operation of the devices.
YesSubstep c.
NoSubstep d.
c.
Cut off the AC input of the power supply, eliminate all the smoke hazards, and
restart the power supply.
YesEnd.
NoStep 2.
d. Eliminate the smoke source.

YesEnd.
NoStep 2.
2. Replace the smoke sensor.
YesEnd.
NoStep 3.
4-25
SJ-20141022095204-005|2015-07-27 (R2.2)
YesEnd.
4.15 198092112 Embedded power Flood detected

Alarm Information
l
l
l
l

Name: Embedded power Flood detected
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.
YesSubstep b.
NoStep 2.
b. Cut off the power supply, remove the water, and restart the power supply after the
devices are dry.
YesEnd.
No Step 2.
2. Replace the flood sensor.
4-26
SJ-20141022095204-005|2015-07-27 (R2.2)

YesEnd.
No Step 3.
YesEnd.
4.16 198092113 Embedded power Door Magnet Alarm

Alarm Information
l
l
l
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.
YesStep 2.
4-27
SJ-20141022095204-005|2015-07-27 (R2.2)
NoSubstep b.
b. Verify that the cabinet door is closed.
YesEnd.
No Step 2.
2. Check the sensor cable.
a. Check whether the sensor cable is properly connected (for example, whether the
interface connection is loose or wrong).
YesSubstep c.
No Substep b.
b. Connect the sensor cable properly.
YesEnd.
NoSubstep c.
c.
Check whether the sensor cable is in good condition.

YesStep 3.
NoSubstep d.
d. Replace the cable.

YesEnd.
NoStep 3.
3. Replace the magnetic door switch sensor.
YesEnd.
NoStep 4.
YesEnd.
4.17 198092114 Embedded power Gate Embedded

power Safety Alarm
Alarm Information
l

4-28
SJ-20141022095204-005|2015-07-27 (R2.2)
l
l
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.
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.
YesStep 2.
NoSubstep b.
b. Verify that the cabinet door is closed.
YesEnd.
No Step 2.
YesSubstep c.
No Substep b.
4-29
SJ-20141022095204-005|2015-07-27 (R2.2)

YesEnd.
NoSubstep c.
c.

YesStep 3.
NoSubstep d.

YesEnd.
NoStep 3.
3. Replace the door access control sensor.
YesEnd.
NoStep 4.
YesEnd.
4.18 198092115 Glass Broken Alarm

Alarm Information
l
l
l
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
4-30
SJ-20141022095204-005|2015-07-27 (R2.2)

Action
1. Verify that the glass of the equipment room is not damaged.
a. Check whether the glass of the equipment room is damaged.
YesSubstep b.
NoStep 2.
b. Replace the glass.
YesEnd.
NoStep 2.
Yes Substep c.
NoSubstep b.
YesEnd.
NoSubstep c.
c.

YesStep 3.
No Substep d.

YesEnd.
NoStep 3.
3. Replace the glass sensor.
YesEnd.
NoStep 4.
4-31
SJ-20141022095204-005|2015-07-27 (R2.2)
YesEnd.
4.19 198092118 Embedded power Env-unit

communication interruption
Alarm Information
l
l
l
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.
YesStep 2.
NoSubstep b.
b. Install the environment monitoring board.
4-32
SJ-20141022095204-005|2015-07-27 (R2.2)
YesEnd.
NoStep 2.
2. Verify that the cable to the environment monitoring board is not disconnected or
broken.
a. Check whether the cable to the environment monitoring board is disconnected or
broken.
YesSubstep b.
No Step 3.
b. Reconnect or replace the cable.
YesEnd.
NoStep 3.
YesStep 4.
NoSubstep b.
YesEnd.
NoStep 4.
4. Replace the environment monitoring board. 15 minutes, check whether the alarm is
cleared.
YesEnd.
No Step 5.
YesEnd.
4.20 198092119 Embedded power Heat Exchanger Fault

Alarm Information
l
l
l
l

Name: Embedded power Heat Exchanger Fault
4-33
SJ-20141022095204-005|2015-07-27 (R2.2)
Alarm Description
This alarm occurs when the heat exchanger is damaged or the temperature is beyond the
allowed range.
Alarm Cause
1. The heat exchanger is faulty.
2. The socket of the monitoring unit is not in good contact or the monitoring unit is
disconnected.
3. The monitoring unit is damaged.
Impact
The over temperature may affect the lifespan of the equipment.
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.
YesSubstep b.
NoStep 2.
YesEnd.
No Step 2.
YesStep 3.
NoSubstep b.
YesEnd.
NoStep 3.
3. Replace the heat exchanger. 15 minutes, check whether the alarm is cleared.
YesEnd.
4-34
SJ-20141022095204-005|2015-07-27 (R2.2)
NoStep 4.
YesEnd.
4.21 198092462 Blocked dust proof net

Alarm Information
l
l
l
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 overtemperature may affect the life of the equipment.
The temperature inside the cabinet increases, causing services to be affected.
Action
1. Check the settings of the dry contact device.
YesStep 2.
NoSubstep b.
4-35
SJ-20141022095204-005|2015-07-27 (R2.2)

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
accordance with the slot, shelf, and rack information in the Detail Information
dialog box.
c.

YesEnd.
NoStep 2.
2. Check the cable connected to the dry contact.
is secured).
YesSubstep c.
NoSubstep b.
YesEnd.
NoSubstep c.
c.

YesStep 3.
NoSubstep d.

YesEnd.
No Step 3.
3. Clean the air filter.
YesEnd.
4.22 198097061 Temperature abnormal

Alarm Information
l
l
l

Name: Temperature abnormal
4-36
SJ-20141022095204-005|2015-07-27 (R2.2)
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
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 suggestion. The related alarm is as follows:
198098111 Fan failure
YesEnd.
NoStep 2.
2. Check the temperature threshold of the air intake.
a. Select
Configuration
ManagementManaged
Element
->
DeviceB8200SA/PSA/FABEnvironment 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
c.

YesEnd.
No Step 3.
4-37
SJ-20141022095204-005|2015-07-27 (R2.2)
3. Improve the ventilation (for example, troubleshooting air conditioner faults and heating
device faults).
YesEnd.
NoStep 4.
4. Clean the air intake and the filter.
YesEnd.
4.23 198098128 Power over-loaded

Alarm Information
l
l
l
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.
a. Select Configuration ManagementManaged ElementDeviceCabinet, and
check whether the configurations of the load board are the same as planned.
YesStep 2.
4-38
SJ-20141022095204-005|2015-07-27 (R2.2)
NoSubstep b.
b. Modify the configurations to those as planned.
c.

YesEnd.
NoStep 2.
2. Check whether the configurations of the power board are the same as planned.
a. Select Configuration ManagementManaged ElementDeviceCabinet, and
check whether the configurations of the power board are the same as planned.
YesStep 3.
NoSubstep 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.

YesEnd.
NoStep 2.
3. Replace the power board.
YesEnd.
4.24 198092550~198092599 Battery pack fan failed.

Alarm Information
l
l
l
l
Alarm code: 198092550~198092599

Name: Battery pack fan failed.
Alarm Description
This alarm is reported when the battery pack fan stops.
Alarm Cause
4-39
SJ-20141022095204-005|2015-07-27 (R2.2)
3. The fan of the battery does not operate.
Impact
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
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 alarm details.
YesStep 2.
NoSubstep b.
Number in alarm details.
c.

YesEnd.
NoStep 2.
YesSubstep c.
NoSubstep b.
YesEnd.
No Substep c.
c.
Check whether the dry contact cable is in good condition.

YesStep 3.
4-40
SJ-20141022095204-005|2015-07-27 (R2.2)
NoSubstep d.
YesEnd.
NoStep 3.
3. Verify that the fan operates.
a. Check whether the fan operates.
YesSubstep b.
NoStep 4.
b. Replace the fan.
YesEnd.
NoStep 4.
details.
Yes End.
NoStep 5.
5. Remove and install the board in accordance with the Rack Number, Shelf Number and
Slot Number in alarm details.
YesEnd.
NoStep 6.
YesEnd.
4-41
SJ-20141022095204-005|2015-07-27 (R2.2)
4-42
SJ-20141022095204-005|2015-07-27 (R2.2)
Chapter 5
Equipment Alarm
Table of Contents
198092049 Lightning protection device alarm.............................................................5-3
198092051 PSU alarm ...............................................................................................5-5
198092052 PSU fan alarm .........................................................................................5-7
198092057 The board is powered off .........................................................................5-9
198092068 Main power supply has a fault alarm ......................................................5-12
198092069 FCE fan failure.......................................................................................5-14
198092071 Temperature sensor abnormal ..............................................................5-15
198092072 The board is not in position ....................................................................5-16
198092073 Embedded power AC-in Switch Off ........................................................5-18
198092074 Embedded power AC Power Off ............................................................5-20
198092075 Embedded power SPD-C Broken...........................................................5-21
198092076 Embedded power SPD-D Broken...........................................................5-23
198092077 Embedded power AC Under-Volt ...........................................................5-25
198092078 Embedded power AC Over-Volt .............................................................5-27
198092082 Embedded power SMR Fan Fault ..........................................................5-28
198092083 Embedded power SMR PFC Fault .........................................................5-30
198092084 Embedded power SMR Over-Vin Off......................................................5-30
198092085 Embedded power SMR Under-Vin Off....................................................5-31
198092086 Embedded power SMR H.T. Off .............................................................5-33
198092087 Embedded power SMR Env.H.T.Off .......................................................5-34
198092088 Embedded power SMR Env.H.T ............................................................5-35
198092089 Embedded power SMR L.Vin .................................................................5-36
198092090 Embedded power SMR Fuse Broken .....................................................5-37
198092091 Embedded power SMR CommFail .........................................................5-38
198092094 Embedded power DC Loop Broken........................................................5-40
198092095 Embedded power Bat Loop Broken........................................................5-42
198092096 Embedded power Bat Under-Volt...........................................................5-43
198092097 Embedded power Bat Over-Temp ..........................................................5-46
198092098 Embedded power TmpL Shut-Down ......................................................5-47
198092099 Embedded power 1st Shut-down ...........................................................5-49
198092100 Embedded power 2nd Shut-down ..........................................................5-51
198092101 Embedded power DC SPD Broken ........................................................5-53
198092102 Embedded power DC Breaker Alarm .....................................................5-54
198092103 Embedded power Bat Test Failure .........................................................5-56
198092117 Embedded power Rectifier Module Fault................................................5-57
198092203 The board is not configured ...................................................................5-59
198092206 Battery alarm .........................................................................................5-60
5-1
SJ-20141022095204-005|2015-07-27 (R2.2)
198092207 AC power-cut alarm ...............................................................................5-62

198092208 Rectifier module alarm ...........................................................................5-64
198092209 Thermoelectric cooler alarm...................................................................5-66
198092215 Lost of synchronization ..........................................................................5-68
198092217 No available clock source at air-interface ...............................................5-69
198092234 Embedded power type configuration error..............................................5-71
198092235 Embedded power communication interruption........................................5-72
198092237 Embedded power Bat Under-Temp ........................................................5-73
198092238 Embedded power Bat Invalid-Temp........................................................5-75
198092239 Embedded power Battery Fault..............................................................5-76
198092259 Battery low-voltage alarm.......................................................................5-78
198092260 Faulty external device connected at a dry contact ..................................5-80
198092261 Outdoor lightning protection box alarm...................................................5-82
198092262 Breaker alarm in indoor lightning protection box.....................................5-84
198092263 Lightning protection device alarm in indoor lightning protection box .......5-86
198092264 Over-voltage alarm of main power input.................................................5-88
198092265 Main power input power-cut alarm .........................................................5-91
198092266 Under-voltage alarm of main power input...............................................5-93
198092267 General fault of main power ...................................................................5-95
198092268 PWR monitoring unit alarm ....................................................................5-97
198092292 Optical fiber connection error .................................................................5-99
198092295 Device power down .............................................................................5-100
198092363 Faulty main power alarm......................................................................5-101
198092394 Several faulty rectifiers.........................................................................5-103
198092426 The GNSS cascading clock is faulty.....................................................5-104
198092435 Inter-subrack Ethernet link broken in stack mode .................................5-107
198092447 Unbalanced AC phase voltage of built-in power ...................................5-108
198092449 Missing AC phase voltage of built-in power ..........................................5-109
198092450 Battery low-voltage cut-off of built-in power .......................................... 5-111
198092451 Broken LLVD1 branch E of built-in power ............................................. 5-113
198092452 Broken LLVD1 branch of built-in power ................................................ 5-115
198092453 Broken LLVD2 branch E of built-in power ............................................. 5-117
198092454 Broken battery cut-off branch E of built-in power .................................. 5-119
198092455 Broken battery cut-off branch of built-in power .....................................5-121
198092456 Abnormal battery current of built-in power............................................5-123
198092457 Abnormal CAN bus of built-in power ....................................................5-124
198092458 Abnormal battery of built-in power........................................................5-125
198092459 Abnormal input dry contact of built-in power.........................................5-126
198092460 High-temperature cut-off of built-in power ............................................5-127
198092461 Failure in frame synchronization between BBU subracks .....................5-129
198092550~198092599 User-defined dry contact alarm.........................................5-131
198096830 Too large phase difference between clock sources ..............................5-133
198096831 1588 clock source fault ........................................................................5-136
198096835 GNSS receiver fault .............................................................................5-138
198096836 GNSS antenna feeder link fault............................................................5-144
5-2
SJ-20141022095204-005|2015-07-27 (R2.2)
Chapter 5 Equipment Alarm
198096838 Clock source abnormal in stack mode..................................................5-147

198097004 Board hardware fault............................................................................5-148
198097060 Board communication link interrupted ..................................................5-149
198097109 E1/T1 link is interrupted .......................................................................5-150
198097680 POE power supply abnormal ...............................................................5-152
198098111 Fan failure ............................................................................................5-153
198098251 The working mode of the Ethernet port doesn't match the peer end ....5-154
198098314 Inter-board data link abnormal. ............................................................5-155
198098315 Input clock of the board abnormal. .......................................................5-156
198098318 Unavailable optical module .................................................................5-158
198098320 Optical interface reception link degraded .............................................5-160
198098440 Disable PA ...........................................................................................5-162
198098465 VSWR of the antenna feeder abnormal................................................5-163
198098466 Temperature abnormal.........................................................................5-165
198098467 Internal fault.........................................................................................5-166
198098468 External extended device fault .............................................................5-167
198098469 Abnormal RX channel ..........................................................................5-172
198098470 Blocked resources manually ................................................................5-174
198098471 Carrier downlink data problem .............................................................5-175
198098472 RRU Power Abnormal Alarm ...............................................................5-176
198098473 The baseband signal input to the TX channel is abnormal ...................5-178
198098474 RRU fan failure ....................................................................................5-179
198092117 Embedded power Rectifier Module Fault..............................................5-180
198092091 Embedded power SMR CommFail .......................................................5-182
198100078 Abnormal input dry contact one of built-in power ..................................5-184
198100079 Abnormal input dry contact two of built-in power ..................................5-185
198100080 Abnormal input dry contact three of built-in power................................5-186
198100081 Abnormal input dry contact four of built-in power..................................5-187
198100280 The output power of the TX channel is abnormal .................................5-188
198100283 Smart antenna calibration is abnormal .................................................5-189
198094829 eNodeB synchronization abnormal.......................................................5-191
198094839 Reverse link RSSI minor alarm ............................................................5-191
198094840 Reverse link RSSI major alarm ............................................................5-192
198094847 RF channel attenuation consistency alarm...........................................5-193
198094848 Antenna calibration failure....................................................................5-194
198097680 POE power supply abnormal ...............................................................5-195
5.1 198092049 Lightning protection device alarm

Alarm Information
l
l
l
l

Name: Lightning protection device alarm
Alarm type: Equipment Alarm
5-3
SJ-20141022095204-005|2015-07-27 (R2.2)
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
set.
3. The lightning protection device is faulty due to the lightning damage, poor contact or
aging.
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
YesStep 2.
No Substep b.
c.

YesEnd.
NoStep 2.
5-4
SJ-20141022095204-005|2015-07-27 (R2.2)
is secured).)
YesSubstep c.
NoSubstep b.
b. Reconnect the cable to the dry contact.
YesEnd.
NoSubstep c.
c.

YesStep 3.
NoSubstep d.

YesEnd.
NoStep 3.
3. Replace the lightning protection box. 15 minutes, and check whether the alarm is
cleared.
YesEnd.
5.2 198092051 PSU alarm

Alarm Information
l
l
l
l

Name: PSU alarm
Alarm Description
This alarm is reported when PSU is broken or its monitoring cable is not well connected.
Alarm Cause
3. The PSU module is faulty.
5-5
SJ-20141022095204-005|2015-07-27 (R2.2)
Impact
None.
None.
Action
Shelf Number, and Slot Number in the alarm details.
YesStep 2.
NoSubstep b.
c.

YesEnd.
NoStep 2.
YesSubstep c.
NoSubstep b.
YesEnd.
NoSubstep c.
c.

YesStep 3.
NoSubstep d.

5-6
SJ-20141022095204-005|2015-07-27 (R2.2)
YesEnd.
NoStep 3.
3. Replace the PSU module.
YesEnd.
5.3 198092052 PSU fan alarm

Alarm Information
l
l
l
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
5-7
SJ-20141022095204-005|2015-07-27 (R2.2)
YesStep 2.
NoSubstep b.
c.

YesEnd.
NoStep 2.
2. Check whether the fan box is correctly installed.
a. Check whether the fan box is correctly installed.
YesStep 3.
NoSubstep b.
b. Correctly install a fan box.
c.

Yes End.
NoStep 3.

YesSubstep c.
NoSubstep b.
YesEnd.
NoSubstep c.
c.

YesStep 4.
NoSubstep d.

YesEnd.
NoStep 4.
4. Replace a fan box.
5-8
SJ-20141022095204-005|2015-07-27 (R2.2)

YesEnd.
5.4 198092057 The board is powered off

Alarm Information
l
l
l
l

Name: The board is powered off
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.
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:

Remove and reinstall the board based on the rack number/shelf number/slot number
in the Detail Information dialog box.
YesEnd.
The service power supply is cut off:

5-9
SJ-20141022095204-005|2015-07-27 (R2.2)

Parameter configuration error (198097511) (The board required power
exceeds the PM's supplying capability)
YesEnd.
NoStep 2.
2. Verify that the board is configured as planned.
a. Check whether the board is configured as planned.
NoSubstep b.
b. Re-configure the board as planned.
c.

YesEnd.
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.
YesEnd.
NoStep 2.
2. Install the board to another slot.
a. Check whether the board can be installed to another slot based on the network
planning.
YesSubstep b.
NoStep 3.
b. Install the board to another slot.
c.
Select Configuration Management -> Managed ElementDeviceRack

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.

YesEnd.
5-10
SJ-20141022095204-005|2015-07-27 (R2.2)
NoStep 3.
3. Replace the board based on the rack number/shelf number/slot number in the
YesEnd.
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 fault
YesEnd.
NoStep 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.
YesEnd.
NoStep 3.
3. Ensure that the air intake of the equipment is not blocked or clean the air filter.
YesEnd.
The management power supply is cut off manually/The service power supply is
cut off manually:
Select Dynamic ManagementDynamic CommandSDRDevice Group from the
menu. The Device Group tab is displayed. Power on the board based on the rack
YesEnd.
The service power supply is cut off by intelligent control:

5-11
SJ-20141022095204-005|2015-07-27 (R2.2)
This intelligent operation is automatically performed by the board for power saving
purposes, and no action is required.
5.5 198092068 Main power supply has a fault alarm

Alarm Information
l
l
l
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
The board is operating properly.
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
5-12
SJ-20141022095204-005|2015-07-27 (R2.2)
YesStep 2.
No Substep b.
c.

YesEnd.
NoStep 2.
is secured).
Yes Substep c.
NoSubstep b.
YesEnd.
NoSubstep c.
c.

YesStep 3.
NoSubstep d.

YesEnd.
NoStep 3.
YesEnd.
NoStep 4.
4. Replace the master power supply with a proper one. 15 minutes, and check whether
YesEnd.
5-13
SJ-20141022095204-005|2015-07-27 (R2.2)
NoStep 5.
5.6 198092069 FCE fan failure

Alarm Information
l
l
l
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.
Action
1. Ensure that the air intake of the fan is not blocked.
YesEnd.
NoStep 2.
2. Replace the fan in accordance with the fan number/slot, shelf, and rack information in
the Detail Information dialog box. 15 minutes, and check whether the alarm is cleared.
YesEnd.
5-14
SJ-20141022095204-005|2015-07-27 (R2.2)
5.7 198092071 Temperature sensor abnormal

Alarm Information
l
l
l
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.
a. Check whether the temperature sensor has been installed.
YesStep 2.
NoSubstep b.
b. Install a temperature sensor.
Yes End.
NoStep 2.
2. Check the temperature sensor cable.
a. Check whether the temperature sensor cable connection is loose or the cable is
damaged.
YesSubstep b.
5-15
SJ-20141022095204-005|2015-07-27 (R2.2)
NoStep 3.
b. Unplug and plug the cable, or replace the cable.
YesEnd.
NoStep 3.
3. Change the temperature sensor.
YesEnd.
If the alarm board is SA/SE/PSA/PM, the operations are as follows:
YesEnd.
NoStep 2.
YesEnd.
5.8 198092072 The board is not in position

Alarm Information
l
l
l
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.
5-16
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
YesStep 2.
NoSubstep b.
b. Select Configuration ManagementManaged Element -> DeviceRack Graph
from the menu. The Rack Graph tab is displayed. Delete the board configuration
of the corresponding slot.
c.

YesEnd.
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.
YesStep 3.
No Substep b.
b. Install the board based on the network planning.
YesEnd.
NoStep 4.
3. Remove and reinstall the board based on the rack number/shelf number/slot number
YesEnd.
5-17
SJ-20141022095204-005|2015-07-27 (R2.2)
NoStep 4.
a. Check whether the board can be installed to another slot based on the network
planning.
YesSubstep b.
c.
Select Configuration ManagementManaged ElementDeviceRack 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.

YesEnd.
5.9 198092073 Embedded power AC-in Switch Off

Alarm Information
l
l
l
l

Name: Embedded power AC-in Switch Off
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.
5-18
SJ-20141022095204-005|2015-07-27 (R2.2)

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.
YesSubstep b.
NoStep 2.
b. Check whether the AC input is short-circuited.
Yes Substep c.
NoSubstep d.
c.
Troubleshoot the AC short circuits.
d. Close the active AC air circuit breaker.

YesEnd.
NoStep 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.
NoStep 3.
YesEnd.
NoStep 3.
3. Check whether the monitoring unit installation is correct.
YesStep 4.
NoSubstep b.
YesEnd.
No Step 4.
5-19
SJ-20141022095204-005|2015-07-27 (R2.2)
YesEnd.
5.10 198092074 Embedded power AC Power Off

Alarm Information
l
l
l
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
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.
YesSubstep b.
NoStep 2.
b. Restore the AC power by using a diesel generator or other emergency power
supply devices.
5-20
SJ-20141022095204-005|2015-07-27 (R2.2)
YesEnd.
NoStep 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.
YesSubstep b.
NoStep 3.
YesEnd.
NoStep 3.
3. Check whether the monitoring unit is properly connected.
YesStep 4.
NoSubstep b.
YesEnd.
No Step 4.
YesEnd.
5.11 198092075 Embedded power SPD-C Broken

Alarm Information
l
l
l
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.
5-21
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
YesEnd.
NoStep 2.
2. Check whether the lightning protection air circuit breaker is closed.
a. Check whether the lightning protection air circuit breaker is closed.
YesStep 3.
NoSubstep b.
b. Close the lightning protection air circuit breaker.
YesEnd.
NoStep 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).
YesStep 4.
NoSubstep b.
b. Secure the lightning protector base or remove the rust.
YesEnd.
NoStep 4.
5-22
SJ-20141022095204-005|2015-07-27 (R2.2)
4. Check whether the lightning protector base contact-point cable is disconnected.

a. Check whether the lightning protector base contact-point cable is disconnected.
YesSubstep b.
NoStep 5.
YesEnd.
NoStep 5.
YesStep 6.
NoSubstep b.
YesEnd.
No Step 6.
YesEnd.
5.12 198092076 Embedded power SPD-D Broken

Alarm Information
l
l
l
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.
5-23
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
YesEnd.
NoStep 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).
YesStep 3.
NoSubstep b.
b. Secure the lightning protector base or remove the rust.
YesEnd.
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.
YesSubstep b.
NoStep 4.
YesEnd.
NoStep 4.
5-24
SJ-20141022095204-005|2015-07-27 (R2.2)
YesStep 5.
NoSubstep b.
YesEnd.
NoStep 5.
YesEnd.
5.13 198092077 Embedded power AC Under-Volt

Alarm Information
l
l
l
l

Name: Embedded power AC Under-Volt
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.
5-25
SJ-20141022095204-005|2015-07-27 (R2.2)
Action
1. Check whether the AC voltage is under the lower AC voltage threshold.
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).
YesSubstep c.
NoStep 2.
c.
Troubleshoot the AC input failure of the embedded power.

YesEnd.
NoStep 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.
YesSubstep b.
NoStep 3.
YesEnd.
NoStep 3.
YesStep 4.
NoSubstep b.
YesEnd.
No Step 4.
YesEnd.
5-26
SJ-20141022095204-005|2015-07-27 (R2.2)
5.14 198092078 Embedded power AC Over-Volt

Alarm Information
l
l
l
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.
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).
YesSubstep c.
NoStep 2.
c.

YesEnd.
NoStep 2.
5-27
SJ-20141022095204-005|2015-07-27 (R2.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.
YesSubstep b.
NoStep 3.
YesEnd.
NoStep 3.
YesStep 4.
NoSubstep b.
YesEnd.
NoStep 4.
YesEnd.
5.15 198092082 Embedded power SMR Fan Fault

Alarm Information
l
l
l
l

Name: Embedded power SMR Fan Fault
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.
5-28
SJ-20141022095204-005|2015-07-27 (R2.2)
Impact
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).
YesSubstep b.
NoStep 2.
b. Remove the blockage.
YesEnd.
NoStep 2.
YesStep 3.
NoSubstep b.
YesEnd.
NoStep 3.
3. Replace the rectifier where the alarm is located. 15 minutes, check whether the alarm
is cleared.
YesEnd.
NoStep 4.
YesEnd.
5-29
SJ-20141022095204-005|2015-07-27 (R2.2)
5.16 198092083 Embedded power SMR PFC Fault

Alarm Information
l
l
l
l

Name: Embedded power SMR PFC Fault
Alarm Description
This alarm occurs when Power Factor Correction (PFC) encounters one of the following
problems:
l
l
l
The PFC input is overcurrent.

The PFC output is overvoltage.
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
1. Replace the rectifier where the alarm is located.
YesEnd.
5.17 198092084 Embedded power SMR Over-Vin Off

Alarm Information
l
l
l
l

Name: Embedded power SMR Over-Vin Off
5-30
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
2. The rectifier is faulty.
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: 295305 V).
YesSubstep c.
NoStep 2.
c.

YesEnd.
NoStep 2.
is cleared.
YesEnd.
5.18 198092085 Embedded power SMR Under-Vin Off

Alarm Information
l

5-31
SJ-20141022095204-005|2015-07-27 (R2.2)
l
l
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: 8090 V).
YesSubstep c.
NoStep 2.
c.

YesEnd.
NoStep 2.
is cleared.
YesEnd.
5-32
SJ-20141022095204-005|2015-07-27 (R2.2)
5.19 198092086 Embedded power SMR H.T. Off

Alarm Information
l
l
l
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 ).
YesSubstep c.
NoStep 2.
c.
Improve the ventilation (for example, eliminating the impact of air conditioner faults
and high-power heating devices on the environment).

YesEnd.
5-33
SJ-20141022095204-005|2015-07-27 (R2.2)
No Step 2.
is cleared.
Yes End.
5.20 198092087 Embedded power SMR Env.H.T.Off

Alarm Information
l
l
l
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.
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 ).
YesSubstep c.
5-34
SJ-20141022095204-005|2015-07-27 (R2.2)
NoStep 2.
c.

YesEnd.
NoStep 2.
is cleared.
YesEnd.
5.21 198092088 Embedded power SMR Env.H.T

Alarm Information
l
l
l
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
The rectifier load capacity is lowered, and the normal power supply to the base station is
affected.
5-35
SJ-20141022095204-005|2015-07-27 (R2.2)
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 ).
YesSubstep c.
NoStep 2.
c.

YesEnd.
NoStep 2.
is cleared.
YesEnd.
5.22 198092089 Embedded power SMR L.Vin

Alarm Information
l
l
l
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.
Alarm Cause
1. The AC input voltage of the rectifier is lower than the under-voltage load-reduction
threshold.
Impact
None.
5-36
SJ-20141022095204-005|2015-07-27 (R2.2)

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).
YesSubstep c.
NoStep 2.
c.

YesEnd.
NoStep 2.
is cleared.
YesEnd.
5.23 198092090 Embedded power SMR Fuse Broken

Alarm Information
l
l
l
l

Name: Embedded power SMR Fuse Broken
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.
5-37
SJ-20141022095204-005|2015-07-27 (R2.2)
Impact
None.
affected.
Action
1. Replace the output fuse of the rectifier where the alarm is located. 15 minutes, check
YesEnd.
NoStep 2.
is cleared.
YesEnd.
5.24 198092091 Embedded power SMR CommFail

Alarm Information
l
l
l
l

Name: Embedded power SMR CommFail
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.
5-38
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
YesStep 2.
NoStep 3.
198092074 Embedded power AC Power Off
YesEnd.
NoStep 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.
YesStep 4.
NoSubstep b.
b. Re-connect or replace the cable.
YesEnd.
NoStep 4.
4. Replace the rectifier where the alarm is located. for 15 minutes, and check whether
YesEnd.
NoStep 5.
5. Replace the monitoring unit. for 15 minutes, and check whether the alarm is cleared.
5-39
SJ-20141022095204-005|2015-07-27 (R2.2)
YesEnd.
5.25 198092094 Embedded power DC Loop Broken

Alarm Information
l
l
l
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.
3. The socket of the monitoring unit is not in good contact or the cable of the monitoring
unit is disconnected.
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.
YesSubstep b.
NoStep 2.
b. Troubleshoot the short circuits.
YesEnd.
NoStep 2.
5-40
SJ-20141022095204-005|2015-07-27 (R2.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.
YesSubstep c.
NoStep 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.
YesEnd.
NoStep 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.
YesSubstep b.
NoStep 4.
YesEnd.
NoStep 4.
YesStep 5.
NoSubstep b.
YesEnd.
NoStep 5.
YesEnd.
5-41
SJ-20141022095204-005|2015-07-27 (R2.2)
5.26 198092095 Embedded power Bat Loop Broken

Alarm Information
l
l
l
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.
YesSubstep b.
No Step 2.
YesEnd.
NoStep 2.
2. Verify that the capacity of the battery corresponding to the fuse is properly configured.
5-42
SJ-20141022095204-005|2015-07-27 (R2.2)
a. Select CtrlSetup ParaSys ParaBat.1 Cap., and check the battery capability
configuration.
b. Check whether the capacity of the battery matches the specifications of the fuse.
YesStep 3
NoSubstep c.
c.
Modify the configuration of the battery capacity and replace the fuse.
YesEnd.
NoStep 3.
3. Verify that the circuit detection cable is not disconnected or broken.

a. Check whether the circuit detection cable is disconnected or broken.
YesSubstep b.
NoStep 4.
YesEnd.
NoStep 4.
YesStep 5
NoSubstep b.
YesEnd.
NoStep 5.
Yes End.
5.27 198092096 Embedded power Bat Under-Volt

Alarm Information
l
l
l

Name: Embedded power Bat Under-Volt
5-43
SJ-20141022095204-005|2015-07-27 (R2.2)
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).
YesStep 2.
NoStep 5.
YesSubstep b.
NoStep 3.
b. Restore the AC power supply by using a diesel generator or other emergency
power supply devices.
YesEnd.
5-44
SJ-20141022095204-005|2015-07-27 (R2.2)
NoStep 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.
YesSubstep c.
No Step 4.
c.
Reduce load devices.

YesEnd.
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.
YesSubstep b.
NoStep 5.
b. After the battery test is completed, wait for 15 minutes, and check whether the
alarm is cleared.
YesEnd.
No Step 5.
YesStep 6.
NoSubstep b.
YesEnd.
NoStep 6.
YesEnd.
5-45
SJ-20141022095204-005|2015-07-27 (R2.2)
5.28 198092097 Embedded power Bat Over-Temp

Alarm Information
l
l
l
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
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.
b. Check whether the temperature of the battery is higher than the upper battery
temperature threshold (default: 45 ).
YesSubstep c.
NoStep 2.
c.

5-46
SJ-20141022095204-005|2015-07-27 (R2.2)
YesEnd.
NoStep 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.
YesSubstep b.
NoStep 3.
YesEnd.
NoStep 3.
3. Replace the temperature sensor of the battery.
YesEnd.
NoStep 4.
YesStep 5
NoSubstep b.
YesEnd.
NoStep 5.
Yes End.
5.29 198092098 Embedded power TmpL Shut-Down

Alarm Information
l
l
l
l

Name: Embedded power TmpL Shut-Down
5-47
SJ-20141022095204-005|2015-07-27 (R2.2)
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 ).
YesSubstep c.
NoStep 2.
c.

YesEnd.
NoStep 2.
or broken.
YesSubstep b.
NoStep 3.
5-48
SJ-20141022095204-005|2015-07-27 (R2.2)

YesEnd.
No Step 3.
YesEnd.
NoStep 4.
YesStep 5
NoSubstep b.
YesEnd.
No Step 5.
YesEnd.
5.30 198092099 Embedded power 1st Shut-down

Alarm Information
l
l
l
l

Name: Embedded power 1st Shut-down
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-49
SJ-20141022095204-005|2015-07-27 (R2.2)
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
YesSubstep b.
NoStep 2.
YesEnd.
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.
YesStep 3.
NoSubstep b.
b. Adjust the status of the switch of the manual power-off device to automatic or
connected.
YesEnd.
NoStep 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.
YesSubstep b.
NoStep 4.
5-50
SJ-20141022095204-005|2015-07-27 (R2.2)

YesEnd.
NoStep 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.
YesSubstep b.
NoStep 5.
b. Replace the LLVD1 DC contactor.
YesEnd.
No Step 5.
5. Replace the board if the SDCB board is configured on site. for 15 minutes, and check
YesEnd.
NoStep 6.
YesEnd.
5.31 198092100 Embedded power 2nd Shut-down

Alarm Information
l
l
l
l

Name: Embedded power 2nd Shut-down
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-51
SJ-20141022095204-005|2015-07-27 (R2.2)

5. The SDCB board is faulty.
Impact
None.
All the services on the base station are interrupted.
Action
YesSubstep b.
NoStep 2.
YesEnd.
NoStep 2.
connected status.
YesStep 3.
NoSubstep b.
connected.
YesEnd.
NoStep 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.
YesSubstep b.
NoStep 4.
5-52
SJ-20141022095204-005|2015-07-27 (R2.2)

YesEnd.
NoStep 4.
4. Verify that the LLVD2 DC contactor is in good condition.
YesSubstep b.
NoStep 5.
b. Replace the LLVD2 DC contactor.
YesEnd.
NoStep 5.
5. Replace the board if the SDCB board is configured on site. for 15 minutes, and check
YesEnd.
NoStep 6.
6. Replace the monitoring unit.
YesEnd.
5.32 198092101 Embedded power DC SPD Broken

Alarm Information
l
l
l
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.
5-53
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
YesSubstep b.
NoStep 2.
YesEnd.
NoStep 2.
2. Replace the DC lightning protector. 15 minutes, check whether the alarm is cleared.
YesEnd.
NoStep 3.
YesEnd.
5.33 198092102 Embedded power DC Breaker Alarm

Alarm Information
l
l
l
l

Name: Embedded power DC Breaker Alarm
Alarm Description
This alarm occurs when the DC output breaker becomes faulty.
5-54
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
YesStep 3.
NoStep 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.
YesSubstep b.
NoStep 3.
YesEnd.
No Step 3.
3. Replace the DC contactor.
YesEnd.
NoStep 4.
YesEnd.
5-55
SJ-20141022095204-005|2015-07-27 (R2.2)
5.34 198092103 Embedded power Bat Test Failure

Alarm Information
l
l
l
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.
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.
NoSubstep 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.
YesEnd.
NoStep 2.
2. Verify that the battery test parameters are properly configured.

5-56
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
YesStep 3.
NoSubstep b.
b. Modify the maximum test time and the final test voltage to the default values.
c.

YesEnd.
NoStep 3.
3. Replace the battery, and retest the battery capacity after the battery is fully charged.
YesEnd.
5.35 198092117 Embedded power Rectifier Module

Fault
Alarm Information
l
l
l
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.
5-57
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
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.
YesStep 3.
NoSubstep b.
b. Connect the rectifier properly.
Yes End.
NoStep 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.
YesStep 3.
NoSubstep b.
b. Close the input air circuit breaker.
YesEnd.
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).
YesStep 4.
No Substep b.
YesEnd.
NoStep 5.
5. Change the installation slot of the rectifier.
5-58
SJ-20141022095204-005|2015-07-27 (R2.2)

YesEnd.
NoStep 6
YesStep 7
NoSubstep b.
YesEnd.
NoStep 6.
Yes End.
5.36 198092203 The board is not configured

Alarm Information
l
l
l
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.
5-59
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
YesStep 2.
NoStep 3.
2. Configure the board based on the network planning.
a. Select Configuration ManagementManaged ElementDevice -> 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.
c.

YesEnd.
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.
YesEnd.
5.37 198092206 Battery alarm

Alarm Information
l
l
l
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.
5-60
SJ-20141022095204-005|2015-07-27 (R2.2)
Impact
None.
Long-period operation may lead to system operation anomaly, and all services on the base
station may be blocked.
Action
YesStep 2.
NoSubstep b.
c.

YesEnd.
NoStep 2.
YesSubstep c.
NoSubstep b.
YesEnd.
No Substep c.
c.

YesStep 3.
NoSubstep d.

5-61
SJ-20141022095204-005|2015-07-27 (R2.2)

YesEnd.
NoStep 3.
Yes End.
NoStep 4.
Slot Number in the alarm details.
YesEnd.
NoStep 5.
YesEnd.
NoStep 6.
6. Place storage batteries.
YesEnd.
5.38 198092207 AC power-cut alarm

Alarm Information
l
l
l
l

Name: AC power-cut alarm
Alarm Description
This alarm is reported when the main power is cut.
Alarm Cause
5-62
SJ-20141022095204-005|2015-07-27 (R2.2)

3. The AC power supply fails, or there is no AC power input because of other failures.
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
YesStep 2.
NoSubstep b.
c.

YesEnd.
NoStep 2.
YesSubstep c.
NoSubstep b.
YesEnd.
No Substep c.
c.

5-63
SJ-20141022095204-005|2015-07-27 (R2.2)
YesStep 3.
NoSubstep d.
YesEnd.
NoStep 3.
YesSubstep b.
NoStep 4.
b. Restore the AC power by using a diesel generator or other emergency power
supply devices.
YesEnd.
NoStep 4.
YesEnd.
No Step 5.
Slot Number in the alarm details.
YesEnd.
NoStep 6.
Yes End.
5.39 198092208 Rectifier module alarm

Alarm Information
l
l

Name: Rectifier module alarm
5-64
SJ-20141022095204-005|2015-07-27 (R2.2)
l
l

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
YesStep 2.
No Substep b.
c.

YesEnd.
NoStep 2.
5-65
SJ-20141022095204-005|2015-07-27 (R2.2)
is secured).)
YesSubstep c.
NoSubstep b.
YesEnd.
NoSubstep c.
c.

YesStep 3.
NoSubstep d.

YesEnd.
NoStep 3.
3. Replace the rectification module. 15 minutes, and check whether the alarm is cleared.
YesEnd.
5.40 198092209 Thermoelectric cooler alarm

Alarm Information
l
l
l
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.
5-66
SJ-20141022095204-005|2015-07-27 (R2.2)
Impact
None.
When the thermoelectric cooler is faulty, battery lifetime may be shortened. Furthermore,
system services may also be affected.
Action
YesStep 2.
No Substep b.
c.

YesEnd.
NoStep 2.
is secured).)
YesSubstep c.
NoSubstep b.
YesEnd.
NoSubstep c.
c.

YesStep 3.
NoSubstep d.
5-67
SJ-20141022095204-005|2015-07-27 (R2.2)

YesEnd.
NoStep 3.
YesEnd.
NoStep 4.
4. Replace the thermoelectric refrigerating unit with a proper one. 15 minutes, and check
YesEnd.
NoStep 5.
5.41 198092215 Lost of synchronization

Alarm Information
l
l
l
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.
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.
Control voltage abnormal

Control voltage is beyond the range.
5-68
SJ-20141022095204-005|2015-07-27 (R2.2)
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: The system cannot operate properly, and all bearer services are
interrupted.
Action
YesEnd.
NoStep 2.
2. Replace the board based on the rack number/shelf number/slot number in the Detail
YesEnd.
5.42 198092217 No available clock source at

air-interface
Alarm Information
l
l
l
l

Name: No available clock source at air-interface
5-69
SJ-20141022095204-005|2015-07-27 (R2.2)
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).
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 ManagementManaged Element -> DeviceB8200, and
confirm the main control board slot (slot 1 or slot 2) is configured for the reference
clock source. Select ClockDevice SetClock Device, and check whether the
configured reference clock source type is the same as planned.
YesStep 2.
NoSubstep b.
b. Reconfigure the reference clock source type based on the network planning.
c.

YesEnd.
No Step 2.
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
5-70
SJ-20141022095204-005|2015-07-27 (R2.2)

198096831 1588 clock source fault
198096839 RRU inner GNSS clock source abnormal
YesEnd.
NoStep 3.
YesEnd.
NoStep 4.
YesEnd.
5.43 198092234 Embedded power type configuration

error
Alarm Information
l
l
l
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.
5-71
SJ-20141022095204-005|2015-07-27 (R2.2)
Action
1. Verify that the type of the power supply is configured correctly.
a. Select Configuration ManagementManaged Element -> DeviceBTS Auxiliary
Peripheral DeviceExternal Device, and re-configure the type of the power supply
according to the corresponding information in the additional alarm information in
the alarm details.
c.

YesEnd.
NoStep 2.
2. Replace the power supply.

YesEnd.
5.44 198092235 Embedded power communication

interruption
Alarm Information
l
l
l
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.
5-72
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
Yes Step 2.
NoSubstep b.
YesEnd.
NoStep 2.
YesStep 3.
NoSubstep b.
YesEnd.
NoStep 3.
YesEnd.
5.45 198092237 Embedded power Bat Under-Temp

Alarm Information
l
l
l
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.
5-73
SJ-20141022095204-005|2015-07-27 (R2.2)

disconnected.
Impact
If the temperature is too low, the life of the battery will be affected.
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 ).
YesSubstep c.
NoStep 2.
c.

YesEnd.
NoStep 2.
or broken.
YesSubstep b.
NoStep 3.
YesEnd.
NoStep 3.
5-74
SJ-20141022095204-005|2015-07-27 (R2.2)

YesEnd.
NoStep 4.
YesStep 5
NoSubstep b.
YesEnd.
NoStep 5.
Yes End.
5.46 198092238 Embedded power Bat Invalid-Temp

Alarm Information
l
l
l
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.
5-75
SJ-20141022095204-005|2015-07-27 (R2.2)

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.
YesStep 2
NoSubstep b.
b. Reconnect the temperature sensor.
YesEnd.
NoStep 2.
YesEnd.
NoStep 3.
YesStep 4
NoSubstep b.
YesEnd.
NoStep 4.
Yes End.
5.47 198092239 Embedded power Battery Fault

Alarm Information
l
l

Name: Embedded power Battery Fault
5-76
SJ-20141022095204-005|2015-07-27 (R2.2)
l
l

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.
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 CtrlSetup ParaSys ParaBat.1 Cap., and check the configured battery
capability.
b. Check whether the configured battery capacity matches that of the installed
battery.
YesStep 2.
NoSubstep 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.

YesEnd.
NoStep 2.
2. Verify that the battery is properly installed.
a. Check whether the battery is properly installed.
YesStep 3.
5-77
SJ-20141022095204-005|2015-07-27 (R2.2)
NoSubstep b.
b. Reinstall the battery.
c.

YesEnd.
NoStep 3.

YesStep 4.
NoSubstep b.
c.

YesEnd.
NoStep 4.
4. Replace the battery and retest the battery capacity after the battery is fully charged.
YesEnd.
NoStep 5.
5. Replace the monitoring unit and retest the battery capacity after the battery is fully
charged. 15 minutes, check whether the alarm is cleared.
YesEnd.
5.48 198092259 Battery low-voltage alarm

Alarm Information
l
l
l
l

Name: Battery low-voltage alarm
Alarm Description
This alarm is reported when the battery is under voltage.
5-78
SJ-20141022095204-005|2015-07-27 (R2.2)
Alarm Cause
set.
3. The battery voltage is too low.
Impact
If the voltage is too low, the life of the battery will be affected.
affected.
Action
YesStep 2.
No Substep b.
c.

YesEnd.
NoStep 2.
is secured).)
YesSubstep c.
NoSubstep b.
5-79
SJ-20141022095204-005|2015-07-27 (R2.2)

YesEnd.
NoSubstep c.
c.

YesStep 3.
NoSubstep d.

YesEnd.
NoStep 3.
3. Charge the battery. After the battery voltage reaches the normal or a higher value,
YesEnd.
5.49 198092260 Faulty external device connected at

a dry contact
Alarm Information
l
l
l
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.
5-80
SJ-20141022095204-005|2015-07-27 (R2.2)

Services may be affected depending on the connected devices.
Action
YesStep 2.
No Substep b.
c.

YesEnd.
NoStep 2.
is secured).)
YesSubstep c.
NoSubstep b.
YesEnd.
NoSubstep c.
c.

YesStep 3.
NoSubstep d.

YesEnd.
5-81
SJ-20141022095204-005|2015-07-27 (R2.2)
NoStep 3.
YesEnd.
NoStep 4.
5.50 198092261 Outdoor lightning protection box alarm

Alarm Information
l
l
l
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
5-82
SJ-20141022095204-005|2015-07-27 (R2.2)
YesStep 2.
No Substep b.
c.

YesEnd.
NoStep 2.
is secured).)
YesSubstep c.
NoSubstep b.
YesEnd.
NoSubstep c.
c.

YesStep 3.
NoSubstep d.

YesEnd.
NoStep 3.
3. Replace the lightning box with a proper one. Refer to Reset Boards.
YesEnd.
5-83
SJ-20141022095204-005|2015-07-27 (R2.2)
5.51 198092262 Breaker alarm in indoor lightning

protection box
Alarm Information
l
l
l
l

Name: Breaker alarm in indoor lightning protection box
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
YesStep 2.
No Substep b.
5-84
SJ-20141022095204-005|2015-07-27 (R2.2)
c.

YesEnd.
NoStep 2.
is secured).)
YesSubstep c.
NoSubstep b.
YesEnd.
NoSubstep c.
c.

YesStep 3.
NoSubstep d.

YesEnd.
NoStep 3.
3. Check the status of the circuit breaker.
a. Check whether the circuit breaker is disconnected.
YesSubstep b.
NoStep 4.
b. Identify the cause and resolve the fault.
YesEnd.
NoStep 4.
4. Replace the circuit breaker.
YesEnd.
NoStep 5.
5-85
SJ-20141022095204-005|2015-07-27 (R2.2)
YesEnd.
NoStep 6.
YesEnd.
5.52 198092263 Lightning protection device alarm in

indoor lightning protection box
Alarm Information
l
l
l
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
5-86
SJ-20141022095204-005|2015-07-27 (R2.2)

YesStep 2.
No Substep b.
c.

YesEnd.
NoStep 2.
is secured).
Yes Substep c.
NoSubstep b.
YesEnd.
NoSubstep c.
c.

YesStep 3.
NoSubstep d.

YesEnd.
NoStep 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
5-87
SJ-20141022095204-005|2015-07-27 (R2.2)
AC power voltage: 80 V to 80 V
YesSubstep b.
NoStep 4.
b. Replace the master power supply with a proper one. 15 minutes, and check
YesEnd.
NoStep 4.
4. Ensure that the lightening proof device is properly grounded.
a. Check whether the lightening proof device is properly grounded.
Yes Step 5.
NoSubstep b.
b. Replace the lightning box. 15 minutes, and check whether the alarm is cleared.
YesEnd.
NoStep 5.
YesEnd.
NoStep 6.
5.53 198092264 Over-voltage alarm of main power input

Alarm Information
l
l
l
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.
5-88
SJ-20141022095204-005|2015-07-27 (R2.2)
Alarm Cause
set.
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
YesStep 2.
No Substep b.
c.

YesEnd.
NoStep 2.
is secured).)
YesSubstep c.
NoSubstep b.
5-89
SJ-20141022095204-005|2015-07-27 (R2.2)

YesEnd.
NoSubstep c.
c.

YesStep 3.
NoSubstep d.

YesEnd.
NoStep 3.
3. Ensure that the input voltage of the master power module is proper.
range:
AC power voltage:80 V to 280 V
YesSubstep b.
NoStep 4.
b. Replace the master power supply with a proper one.
YesEnd.
NoStep 4.
YesEnd.
NoStep 5.
YesEnd.
5-90
SJ-20141022095204-005|2015-07-27 (R2.2)
5.54 198092265 Main power input power-cut alarm

Alarm Information
l
l
l
l

Name: Main power input power-cut 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
YesStep 2.
No Substep b.
5-91
SJ-20141022095204-005|2015-07-27 (R2.2)
c.

YesEnd.
NoStep 2.
is secured).)
YesSubstep c.
NoSubstep b.
YesEnd.
NoSubstep c.
c.

YesStep 3.
NoSubstep d.

YesEnd.
NoStep 3.
3. Ensure that the input voltag of the master power module is proper.
range:
YesSubstep b.
NoStep 4.
YesEnd.
No Step 4.
5-92
SJ-20141022095204-005|2015-07-27 (R2.2)

YesEnd.
NoStep 5.
YesEnd.
5.55 198092266 Under-voltage alarm of main power

input
Alarm Information
l
l
l
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
5-93
SJ-20141022095204-005|2015-07-27 (R2.2)

YesStep 2.
No Substep b.
c.

YesEnd.
NoStep 2.
is secured).
Yes Substep c.
NoSubstep b.
YesEnd.
NoSubstep c.
c.

YesStep 3.
NoSubstep d.

YesEnd.
NoStep 3.
3. Ensure that the input voltag of the master power module is proper.
range:
5-94
SJ-20141022095204-005|2015-07-27 (R2.2)

YesSubstep b.
NoStep 4.
YesEnd.
No Step 4.
YesEnd.
NoStep 5.
YesEnd.
5.56 198092267 General fault of main power

Alarm Information
l
l
l
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
5-95
SJ-20141022095204-005|2015-07-27 (R2.2)
None.
1) If the alarm arises on the board, the system operation is not affected temporarily, but the
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
YesStep 2.
No Substep b.
c.

YesEnd.
NoStep 2.
a. Check whether the cable to the dry contact is correctly connected (for example,
YesSubstep c.
NoSubstep b.
YesEnd.
NoSubstep c.
c.

Yes Step 3.
5-96
SJ-20141022095204-005|2015-07-27 (R2.2)
NoSubstep d.
YesEnd.
NoStep 3.
YesEnd.
NoStep 4.
YesEnd.
NoStep 5.
YesEnd.
5.57 198092268 PWR monitoring unit alarm

Alarm Information
l
l
l
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.
5-97
SJ-20141022095204-005|2015-07-27 (R2.2)
Impact
None.
The PWR monitoring unit fails to report data properly, and service may be affected.
Action
YesStep 2.
NoSubstep b.
c.

YesEnd.
NoStep 2.
is secured).
YesSubstep c.
NoSubstep b.
YesEnd.
NoSubstep c.
c.

YesStep 3.
NoSubstep d.
5-98
SJ-20141022095204-005|2015-07-27 (R2.2)
d. Replace the cable with a proper one. 15 minutes, and check whether the alarm is
cleared.
YesEnd.
NoStep 3.
3. Replace the monitoring unit with a proper one. 15 minutes, and check whether the
alarm is cleared.
YesEnd.
5.58 198092292 Optical fiber connection error

Alarm Information
l
l
l
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.
The services of cell associated to the optical port are interrupted.
Action
1. Select Configuration ManagementManaged Element -> DeviceRack
GraphTopology 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.
YesEnd.
5-99
SJ-20141022095204-005|2015-07-27 (R2.2)
5.59 198092295 Device power down

Alarm Information
l
l
l
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.
YesSubstep b.
NoStep 2.
b. Resolve the power line fault.
YesEnd.
NoStep 2.
2. Resolve the external power device fault.
YesEnd.
5-100
SJ-20141022095204-005|2015-07-27 (R2.2)
5.60 198092363 Faulty main power alarm

Alarm Information
l
l
l
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
YesStep 2.
No Substep b.
5-101
SJ-20141022095204-005|2015-07-27 (R2.2)
c.

YesEnd.
NoStep 2.
is secured).)
YesSubstep c.
NoSubstep b.
YesEnd.
NoSubstep c.
c.

YesStep 3.
NoSubstep d.

YesEnd.
NoStep 3.
YesEnd.
NoStep 4.
YesEnd.
NoStep 5.
YesEnd.
5-102
SJ-20141022095204-005|2015-07-27 (R2.2)
5.61 198092394 Several faulty rectifiers

Alarm Information
l
l
l
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
on the corresponding handling suggestions. The related alarms are as follows:
198092117 Embedded power Rectifier Module Fault
198092082 Embedded power SMR Fan Fault
198092083 Embedded power SMR PFC Fault
198092084 Embedded power SMR Over-Vin Off
198092085 Embedded power SMR Under-Vin Off
198092086 Embedded power SMR H.T. Off
198092087 Embedded power SMR Env.H.T.Off
5-103
SJ-20141022095204-005|2015-07-27 (R2.2)
198092088 Embedded power SMR Env.H.T

198092089 Embedded power SMR L.Vin
198092090 Embedded power SMR Fuse Broken
198092091 Embedded power SMR CommFail
YesEnd.
NoStep 2.
2. Check whether any AC voltage phase is lost.
module, and check whether any AC input voltage phase is lost.
YesSubstep b.
NoStep 3.
b. Troubleshoot the AC input failure of the embedded power.
YesEnd.
is cleared.
YesEnd.
5.62 198092426 The GNSS cascading clock is faulty

Alarm Information
l
l
l
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.
Alarm Cause
1. The GNSS information channel between the upper-level board and the local board is
abnormal.
5-104
SJ-20141022095204-005|2015-07-27 (R2.2)
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
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:
YesStep 2.
2. Handle the alarms according to corresponding suggestions.
3. After 15 minutes, check whether the alarm is cleared.
YesEnd.
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.
NoSubstep b.
b. Select Configuration Management -> Managed ElementDeviceB8200, and
clock source. Select ClockDevice SetClock Device, and delete the GNSS
cascading reference clock source of the local base station .
c.

5-105
SJ-20141022095204-005|2015-07-27 (R2.2)
YesEnd.
e. Select Configuration ManagementManaged ElementDeviceB8200, and
clock source. Select ClockDevice Set, and check whether the configured
cascading clock output mode is GNSS cascading output.
YesStep 2.
NoSubstep f.
f.
Select Configuration ManagementManaged ElementDeviceB8200, 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.
YesEnd.
NoStep 2.
2. Check whether the GNSS cascading clock cable is securely connected.
YesStep 4.
No Step 3.
YesEnd.
No Step 4.
4. Change a cable.
YesEnd.
NoStep 5.
YesEnd.
NoStep 6.
YesEnd.
5-106
SJ-20141022095204-005|2015-07-27 (R2.2)
5.63 198092435 Inter-subrack Ethernet link broken in

stack mode
Alarm Information
l
l
l
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.
YesStep 2.
NoSubstep b.
b. Connect the Ethernet cables properly.
YesEnd.
NoStep 2.
2. Replace the stack Ethernet cables.
YesEnd.
No Step 3.
5-107
SJ-20141022095204-005|2015-07-27 (R2.2)
3. Check whether the operation modes of the network ports of the two stack shelves are
the same.
a. Select
Configuration
ManagementManaged
ElementTransmission
NetworkUMTSPhysical HostingPhysical Layer Port, and check whether
the operation modes are the same.
NoSubstep b.
b. Set the operation modes of the network ports to self-adaptive.
c.

YesEnd.
5.64 198092447 Unbalanced AC phase voltage of

built-in power
Alarm Information
l
l
l
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.
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.
5-108
SJ-20141022095204-005|2015-07-27 (R2.2)
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).
YesSubstep c.
NoStep 2.
c.

YesEnd.
No Step 2.
YesEnd.
5.65 198092449 Missing AC phase voltage of built-in

power
Alarm Information
l
l
l
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.
5-109
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
YesStep 2.
NoSubstep b.
b. Connect the AC input cable properly.
YesEnd.
NoStep 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.
YesSubstep b.
NoStep 3.
YesEnd.
NoStep 3.
YesStep 4.
NoSubstep b.
YesEnd.
NoStep 4.
YesEnd.
5-110
SJ-20141022095204-005|2015-07-27 (R2.2)
5.66 198092450 Battery low-voltage cut-off of built-in

power
Alarm Information
l
l
l
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
Action
Embedded power AC Power Off (198092074)
YesEnd.
NoStep 2.
5-111
SJ-20141022095204-005|2015-07-27 (R2.2)

connected status.
YesStep 3.
No Substep b.
connected.
YesEnd.
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.
YesSubstep b.
NoStep 4.
YesEnd.
No Step 4.
4. Verify that the power-off DC contactor of the battery is in good condition.
YesSubstep b.
NoStep 5.
b. Replace the power-off DC contactor of the battery.
YesEnd.
No Step 5.
YesStep 6.
NoSubstep b.
YesEnd.
5-112
SJ-20141022095204-005|2015-07-27 (R2.2)
NoStep 6.
YesEnd.
5.67 198092451 Broken LLVD1 branch E of built-in

power
Alarm Information
l
l
l
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.
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
YesSubstep b.
NoStep 2.
5-113
SJ-20141022095204-005|2015-07-27 (R2.2)

YesEnd.
NoStep 2.
configuration.
YesStep 3.
NoSubstep c.
c.
YesEnd.
NoStep 3.

YesSubstep b.
NoStep 4.
YesEnd.
NoStep 4.
YesStep 5.
NoSubstep b.
YesEnd.
NoStep 5.
YesEnd.
5-114
SJ-20141022095204-005|2015-07-27 (R2.2)
5.68 198092452 Broken LLVD1 branch of built-in power

Alarm Information
l
l
l
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
YesSubstep b.
NoStep 2.
YesEnd.
NoStep 2.
configuration.
5-115
SJ-20141022095204-005|2015-07-27 (R2.2)
YesStep 3.
NoSubstep c.
c.
YesEnd.
NoStep 3.
3. Verify that the preset circuit breaker threshold is appropriate.

a. Select Setup ParaAlarm Para, and check the circuit breaker threshold.
b. Check whether the preset circuit breaker threshold (default: 0.5 V) is appropriate.
YesStep 4.
NoSubstep c.
c.
Modify the circuit breaker threshold to the default value.

YesEnd.
NoStep 4.

YesSubstep b.
NoStep 5.
YesEnd.
NoStep 5.
YesStep 6.
NoSubstep b.
YesEnd.
NoStep 6.
Yes End.
5-116
SJ-20141022095204-005|2015-07-27 (R2.2)
5.69 198092453 Broken LLVD2 branch E of built-in

power
Alarm Information
l
l
l
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
YesSubstep b.
NoStep 2.
YesEnd.
NoStep 2.
5-117
SJ-20141022095204-005|2015-07-27 (R2.2)
configuration.
YesStep 3.
NoSubstep c.
c.
YesEnd.
NoStep 3.

YesStep 4.
NoSubstep c.
c.

YesEnd.
NoStep 4.

YesSubstep b.
NoStep 5.
YesEnd.
NoStep 5.
YesStep 6.
NoSubstep b.
YesEnd.
5-118
SJ-20141022095204-005|2015-07-27 (R2.2)
NoStep 6.
Yes End.
5.70 198092454 Broken battery cut-off branch E of

built-in power
Alarm Information
l
l
l
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
YesSubstep b.
NoStep 2.
5-119
SJ-20141022095204-005|2015-07-27 (R2.2)

YesEnd.
NoStep 2.
configuration.
YesStep 3.
NoSubstep c.
c.
YesEnd.
NoStep 3.

YesStep 4.
NoSubstep c.
c.

YesEnd.
NoStep 4.

YesSubstep b.
NoStep 5.
YesEnd.
NoStep 5.
YesStep 6.
5-120
SJ-20141022095204-005|2015-07-27 (R2.2)
NoSubstep b.
YesEnd.
NoStep 6.
Yes End.
5.71 198092455 Broken battery cut-off branch of

built-in power
Alarm Information
l
l
l
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.
Action
5-121
SJ-20141022095204-005|2015-07-27 (R2.2)
YesSubstep b.
NoStep 2.
YesEnd.
NoStep 2.
configuration.
YesStep 3.
NoSubstep c.
c.
YesEnd.
NoStep 3.

YesStep 4.
NoSubstep c.
c.

YesEnd.
NoStep 4.

YesSubstep b.
NoStep 5.
YesEnd.
NoStep 5.
5-122
SJ-20141022095204-005|2015-07-27 (R2.2)

YesStep 6.
NoSubstep b.
YesEnd.
NoStep 6.
Yes End.
5.72 198092456 Abnormal battery current of built-in

power
Alarm Information
l
l
l
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.
Action
Replace the monitoring unit.
5-123
SJ-20141022095204-005|2015-07-27 (R2.2)
YesEnd.
5.73 198092457 Abnormal CAN bus of built-in power

Alarm Information
l
l
l
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
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.
YesStep 2.
2. Reconnect or replace the bus.
YesEnd.
5-124
SJ-20141022095204-005|2015-07-27 (R2.2)
5.74 198092458 Abnormal battery of built-in power

Alarm Information
l
l
l
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 CtrlSetup ParaSys ParaBat.1 Cap., and check the configured battery
capability.
b. Check whether the configured battery capacity matches that of the installed
battery.
YesStep 2.
NoSubstep 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.

YesEnd.
5-125
SJ-20141022095204-005|2015-07-27 (R2.2)
NoStep 2.
2. Verify that the battery is properly installed.
a. Check whether the battery is properly installed.
YesStep 3.
NoSubstep b.
b. Reinstall the battery.
c.

YesEnd.
NoStep 3.

YesStep 4.
NoSubstep b.
c.

YesEnd.
NoStep 4.
4. Replace the battery and retest the battery capacity after the battery is fully charged.
YesEnd.
NoStep 5.
5. Replace the monitoring unit and retest the battery capacity after the battery is fully
charged. 15 minutes, check whether the alarm is cleared.
YesEnd.
5.75 198092459 Abnormal input dry contact of built-in

power
Alarm Information
l
l
l

Name: Abnormal input dry contact of built-in power
5-126
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
YesStep 2.
NoSubstep b.
b. Troubleshoot the external device.
YesEnd.
NoStep 2.
Yes End.
5.76 198092460 High-temperature cut-off of built-in

power
Alarm Information
l
l
l
l

Name: High-temperature cut-off of built-in power
5-127
SJ-20141022095204-005|2015-07-27 (R2.2)
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 ).
YesSubstep c.
NoStep 2.
c.

YesEnd.
NoStep 2.
or broken.
YesSubstep b.
NoStep 3.
5-128
SJ-20141022095204-005|2015-07-27 (R2.2)

YesEnd.
No Step 3.
YesEnd.
NoStep 4.
YesStep 5.
NoSubstep b.
YesEnd.
No Step 5.
YesEnd.
5.77 198092461 Failure in frame synchronization

between BBU subracks
Alarm Information
l
l
l
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.
5-129
SJ-20141022095204-005|2015-07-27 (R2.2)
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 ElementDevice, 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.
YesStep 2.
NoSubstep b.
b. Modify the stack mode of BBU shelves as planned.
YesEnd.
No Step 2.
2. Remove and re-install the stack clock cable.
YesEnd.
NoStep 3.
3. Replace the stack clock cable. for 15 minutes, and check whether the alarm is cleared.
YesEnd.
NoStep 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.
YesSubstep b.
b. Shorten the length of the optical fiber.
YesEnd.
5-130
SJ-20141022095204-005|2015-07-27 (R2.2)
5.78 198092550~198092599 User-defined dry contact

alarm
Alarm Information
l
l
l
l
Alarm code: 198092550~198092599

Name: User-defined dry contact alarm
Alarm Description
When there is a fault on the User-defined dry contact, the alarm is reported.
Alarm Cause
set.
3. 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
YesStep 2.
No Substep b.
5-131
SJ-20141022095204-005|2015-07-27 (R2.2)
c.

YesEnd.
NoStep 2.
is secured).
Yes Substep c.
NoSubstep b.
YesEnd.
NoSubstep c.
c.

YesStep 3.
NoSubstep d.
d. Replace the cable with a proper one. 15 minutes, and check whether the alarm is
cleared.
YesEnd.
NoStep 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).
YesSubstep b.
NoStep 4.
b. Resolve the fault in accordance with the instructions of the external device.
YesEnd.
No Step 4.
YesEnd.
NoStep 5.
5-132
SJ-20141022095204-005|2015-07-27 (R2.2)
YesEnd.
5.79 198096830 Too large phase difference between

clock sources
Alarm Information
l
l
l
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
YesSubstep b.
NoStep 2.
5-133
SJ-20141022095204-005|2015-07-27 (R2.2)
b. Select Configuration ManagementManaged NEDeviceCabinet (for

example, B8200), and check the main control board slot (slot 1 or slot 2)
configured for the clock reference source. Select ClockDevice SetClock
Device, and check whether the length of the GNSS antenna feeder cable is
configured according to the actual conditions.
YesStep 2.
NoSubstep c.
c.
Modify the length of the GNSS antenna feeder cable to the actual values.
d. Synchronize the configurations to the corresponding NE.

e. Wait for 15 minutes, and check whether the alarm is cleared.
YesEnd.
NoStep 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.
YesSubstep b.
NoStep 3.
b. Select Configuration ManagementManaged ElementDeviceCabinet (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.
NoSubstep c.
c.

YesEnd.
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.
YesSubstep b.
NoStep 4.
b. Select Configuration ManagementManaged NEDevice -> Cabinet (for
configured for the clock reference source. Select ClockDevice SetClock Device,
5-134
SJ-20141022095204-005|2015-07-27 (R2.2)
and check whether the Cascade cable length and Fixed delay compensation are
configured according to the actual conditions.
YesStep 4.
NoSubstep c.
c.
Modify the Cascade cable length and Fixed delay compensation to the actual
values.

YesEnd.
NoStep 4.
4. Verify that the clock source contains SyncE+1588.
a. Check whether the clock source contains SyncE+1588 according to the additional
YesSubstep b.
NoStep 5.
b. Select Configuration ManagementManaged NEDeviceCabinet (for
configured for the clock reference source. Select ClockDevice SetClock
Device, and check whether the Fixed delay compensation is configured the same
as the actual conditions.
YesStep 5.
NoSubstep c.
c.
Modify the Fixed delay compensation to the actual value.

YesEnd.
NoStep 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.
YesSubstep b.
NoStep 6.
b. Select Configuration ManagementManaged ElementDeviceCabinet (for
example, B8200), and check the slot on the UCI board (slot 5 or slot 7). Select
GNSS Device SetGNSS Set, and check whether the length of the GNSS
antenna feeder cable is configured according to the actual conditions.
5-135
SJ-20141022095204-005|2015-07-27 (R2.2)
YesStep 6.
NoSubstep c.
c.

YesEnd.
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.
YesSubstep b.
b. Check whether there is any GNSS interference source in the neighboring
environment by using a frequency sweeper.
YesSubstep c.
c.
Clear the interference source.

YesEnd.
5.80 198096831 1588 clock source fault

Alarm Information
l
l
l
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.
5-136
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
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
YesEnd.
NoStep 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%.
YesStep 3.
NoSubstep b.
b. Ask the corresponding maintenance personnel to remove the fault.
YesEnd.
NoStep 3.
If the clock level/traceable clock information is abnormal:
Ask the corresponding maintenance personnel to remove the fault.
YesEnd.
NoStep 3.
3. Check whether the IP clock parameters are configured correctly.
5-137
SJ-20141022095204-005|2015-07-27 (R2.2)
a. Select
Configuration
ManagementManaged
ElementTransmission
NetworkUMTSIP ClockIP Clock Parameters and check whether the
network protocol, IP clock transmission mode, and the synchronization server
address are the same as planned.
NoSubstep b.
b. Modify them to the settings as planned.
c.

YesEnd.
5.81 198096835 GNSS receiver fault

Alarm Information
l
l
l
l

Name: GNSS receiver fault
Alarm Description
l
l
This alarm occurs when the inner GNSS receiver has a fault or is unavailable.
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.
5-138
SJ-20141022095204-005|2015-07-27 (R2.2)
Impact
None.
Action
l
Inner GNSS receiver communication failure/1PPS of Inner GNSS receiver is lost:

YesEnd.
NoStep 2.
YesEnd.
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.
YesEnd.
The external front panel GNSS receiver communication failure/1PPS of the external
front panel GNSS receiver is lost:
1. Select Configuration ManagementManaged ElementDeviceB8200, and
clock source. Select ClockDevice SetClock 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.
YesSubstep b
NoSubstep c.
5-139
SJ-20141022095204-005|2015-07-27 (R2.2)
b. Switch on power supply of the receiver.

YesEnd.
NoSubstep c.
c.
Check whether cables are connected properly.

YesSubstep e.
NoSubstep d.
d. Connect the cables correctly.

YesEnd.
NoSubstep e.
e. Change the cables.
YesEnd.
NoSubstep f.
f.
Replace the BeiDou receiver.

YesEnd.
RGPS:
a. Check whether cables are connected properly.
YesSubstep c.
NoSubstep b.
b. Connect the cables correctly.
YesEnd.
NoSubstep c.
c.
Change the cables.

YesEnd.
NoSubstep d.
d. Replace the RGPS.

YesEnd.
5-140
SJ-20141022095204-005|2015-07-27 (R2.2)

UCI_RGPS:
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)
YesEnd.
NoSubstep c.
c.
Select Dynamic ManagementDynamic CommandSDRManaged

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.
YesEnd.
NoSubstep d.
d. Check whether cables are connected properly.

YesSubstep f.
NoSubstep e.
e. Connect the cables correctly.
YesEnd.
NoSubstep f.
f.
Change a cable.
YesEnd.
NoSubstep 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,
YesEnd.
USR1_A:
a. Check whether the USR1_A board operates properly.
5-141
SJ-20141022095204-005|2015-07-27 (R2.2)
YesSubstep b.
NoSubstep e.
b. Check whether the cable is connected properly.
Yes Substep d.
NoSubstep c.
c.
Connect the cable correctly.

YesEnd.
NoSubstep d.
d. Change the cable.

YesEnd.
NoSubstep e.
e. Replace the USR1_A board.
YesEnd.
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 .
YesStep 2.
NoStep 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
YesEnd.
NoStep 3.
3. Select Dynamic Management -> Dynamic CommandSDR-> 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.
YesEnd.
NoStep 4.
5-142
SJ-20141022095204-005|2015-07-27 (R2.2)
4. Replace the receiver in accordance with the panel or back panel information in
the additional information.
YesEnd.
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)
YesEnd.
NoStep 2.
2. Select Dynamic ManagementDynamic CommandSDR-> 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.
YesEnd.
NoStep 3.
3. In Dynamic Management, reset the main control board.
YesEnd.
NoStep 4.
4. Check whether the cable is connected properly.
YesStep 6.
NoStep 5.
YesEnd.
NoStep 6.
6. Change a cable.
5-143
SJ-20141022095204-005|2015-07-27 (R2.2)

YesEnd.
NoStep 7.
7. Replace the receiver connected to this board in accordance with the Rack
Number, Shelf Number and Slot Number in alarm details. 15 minutes, check
Yes End.
5.82 198096836 GNSS antenna feeder link fault

Alarm Information
l
l
l
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.
5-144
SJ-20141022095204-005|2015-07-27 (R2.2)
a. Check whether cables are connected properly (for example, whether the port is
loose or the cable is not connected).
YesStep 2.
NoSubstep b.
b. Connect the cables correctly.
YesEnd.
NoStep 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).
YesSubstep b.
NoStep 3.
b. Replace the connector.
YesEnd.
NoStep 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.
NoSubstep 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.
YesStep 4.
NoSubstep d.
d. Replace the feeder cable in accordance with the GNSS installation manual.
YesEnd.
NoStep 4.
4. Check whether the lightning arrester operates properly.
5-145
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
YesSubstep c.
NoSubstep 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.
YesStep 5.
NoSubstep d.
d. Replace the lightning arrester in accordance with the GNSS installation manual.
15 minutes, check whether the alarm is cleared.
Yes End.
NoStep 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.
YesSubstep c.
NoSubstep 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.
YesStep 6.
No Substep d.
d. Replace the jumper cable in accordance with the GNSS installation manual. 15
minutes, check whether the alarm is cleared.
YesEnd.
NoStep 6.
6. Replace the GNSS antenna.
YesEnd.
NoStep 7.
5-146
SJ-20141022095204-005|2015-07-27 (R2.2)
7. Reset the receiver. Refer to Reset Boards.

a. Select Configuration ManagementManaged ElementDeviceB8200,
clock source. Select ClockDevice SetClock Device, check whether the GNSS
receiver is UCI_RGPS.
YesSubstep b.
No Step 8.
b. Select Dynamic ManagementDynamic CommandSDR -> 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.
YesEnd.
No Step 8.
YesEnd.
NoStep 9.
YesEnd.
5.83 198096838 Clock source abnormal in stack mode

Alarm Information
l
l
l
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.
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.
5-147
SJ-20141022095204-005|2015-07-27 (R2.2)
Impact
None.
Cross-shelf (master-slave) services are affected.
Action
1. Remove and reinstall the stack clock cable.
YesEnd.
NoStep 2.
2. Replace the stack clock cable. 15 minutes, check whether the alarm is cleared.
YesEnd.
No Step 3.
3. Reset the main control board on the slave shelf. Refer to Reset Boards.
YesEnd.
NoStep 4.
4. Replace the main control board on the slave shelf. 15 minutes, check whether the
alarm is cleared.
YesEnd.
5.84 198097004 Board hardware fault

Alarm Information
l
l
l
l

Name: Board hardware fault
Alarm Description
This alarm occurs when the board has a hardware fault.
Alarm Cause
Board hardware fault.
5-148
SJ-20141022095204-005|2015-07-27 (R2.2)
Impact
None.
Action
1. Reset the board in accordance with the Rack Number, Shelf Number and Slot Number
information in alarm details. Refer to Reset Boards.
YesEnd.
NoStep 2.
2. Check whether the board hardware testing function is available in the toolbar during
the diagnosis testing.
YesStep 3.
NoStep 4.
3. Test the board during the diagnosis testing and further perform corresponding
operations in accordance with the testing result.
YesEnd.
NoStep 4.
YesEnd.
5.85 198097060 Board communication link interrupted

Alarm Information
l
l
l
l

Name: Board communication link interrupted
Alarm Description
This alarm occurs when the communication link of the board is broken.
5-149
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
YesEnd.
NoStep 2.
a. Check whether the board can be installed to another slot in accordance with the
network planning data.
YesSubstep b.
c.
Select Configuration Management -> Managed ElementDeviceRack Graph.

The Rack Graph tab is displayed. Delete the board configuration of the previous
slot, and configure the baord for the new slot.

YesEnd.
5.86 198097109 E1/T1 link is interrupted

Alarm Information
l
l
l
l

Name: E1/T1 link is interrupted
5-150
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
YesStep 2.
NoSubstep b.
b. Reconnect the equipment cables.
YesEnd.
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.
YesStep 3.
NoSubstep b.
b. Reconnect or replace the cable between the equipment and the grounding busbar.
5-151
SJ-20141022095204-005|2015-07-27 (R2.2)
YesEnd.
NoStep 3.
3. Replace the E1/T1 cables on the SA/SE/PSA front panels.
YesEnd.
NoStep 4.
4. Change the location of the transmission equipment port or replace the repeater.
YesEnd.
5.87 198097680 POE power supply abnormal

Alarm Information
l
l
l
l

Name: POE power supply abnormal
Alarm Description
The voltage of POE is abnormal.
Alarm Cause
l
l
The -48 voltage of PB is abnormal.

Ethernet cable or PicoRRU on the corresponding port is short circuit.
Impact
Equipment on the corresponding port may not be power supplied.
The services operating on the corresponding port are interrupted.
Action
1. Remove the corresponding Ethernet cable in accordance with the slot, shelf, and
rack information in the Detail Information dialog box, then check whether the alarm
is cleared.
YesStep 2.
5-152
SJ-20141022095204-005|2015-07-27 (R2.2)
NoStep 4.
2. Replace the Ethernet cable, wait 15 minutes, check whether the alarm is cleared.
YesEnd.
NoStep 3.
3. Replace the PicoRRU, wait 15 minutes, check whether the alarm is cleared.
YesEnd.
NoStep 4.
4. Replace the PB board, wait 15 minutes, check whether the alarm is cleared.
YesEnd.
5.88 198098111 Fan failure

Alarm Information
l
l
l
l

Name: Fan failure
Alarm Description
This alarm occurs when the fan is faulty.
Alarm Cause
1. The fan or air inlet is blocked.
Impact
Action
1. Clean the fan blade and ensure that the air inlet is not blocked.
5-153
SJ-20141022095204-005|2015-07-27 (R2.2)
YesEnd.
NoStep 2.
2. Replace the fan in accordance with the shelf, rack information in the Detail Information
dialog box.
YesEnd.
5.89 198098251 The working mode of the Ethernet port

doesn't match the peer end
Alarm Information
l
l
l
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.
Action
1. Check whether the operation mode of the Ethernet port is the same as planned.
a. Select Configuration Management -> Managed ElementTransmission
NetworkUMTSPhysical Hosting -> Physical Layer Port, and check whether
the operation mode of the Ethernet port is the same as planned.
5-154
SJ-20141022095204-005|2015-07-27 (R2.2)
NoSubstep b.
b. Modify the operation mode to that as planned.
c.

YesEnd.
NoStep 2.
2. Ask the maintenance personnel of the peer end to modify the operation mode to that
as planned.
YesEnd.
5.90 198098314 Inter-board data link abnormal.

Alarm Information
l
l
l
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.
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.
5-155
SJ-20141022095204-005|2015-07-27 (R2.2)
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
YesEnd.
NoStep 2.
details.
After 15 minutes, check whether the alarm is cleared. Refer to Reset Boards.
YesEnd.
No Step 3.
Slot Number in the detailed alarm information.
YesEnd.
5.91 198098315 Input clock of the board abnormal.

Alarm Information
l
l
l
l

Name: Input clock of the board abnormal.
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.
5-156
SJ-20141022095204-005|2015-07-27 (R2.2)
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
YesEnd.
NoStep 2.
YesEnd.
NoStep 3.
Slot Number in the detailed alarm information.
YesEnd.
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.
Yes End.
NoStep 3.
5-157
SJ-20141022095204-005|2015-07-27 (R2.2)
YesEnd.
5.92 198098318 Unavailable optical module

Alarm Information
l
l
l
l

Name: Unavailable optical module
Alarm type: Equipment alarm
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
details:
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.
YesStep 2.
5-158
SJ-20141022095204-005|2015-07-27 (R2.2)
NoSubstep b.
b. Install an optical or electrical module.
Waiting for 15 minutes, and then check whether the alarm disappears.
YesEnd.
NoStep 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.
YesEnd.
NoStep 3.
alarm details, replace the optical or electrical module.
YesEnd.
NoStep 4.
4. Select Dynamic ManagementDynamic CommandSDRDevice Group. Based
on the information about rack No., frame No., and slot No. in alarm details, perform
power-off reset on the board.
YesEnd.
The optical module is faulty:
YesEnd.
NoStep 2.
YesEnd.
NoStep 3.
3. Select Dynamic ManagementDynamic CommandSDRDevice Group. Based
on the information about rack No., frame No., and slot No. in alarm details, perform
power-off reset on the board.
5-159
SJ-20141022095204-005|2015-07-27 (R2.2)
YesEnd.
5.93 198098320 Optical interface reception link

degraded
Alarm Information
l
l
l
l

Name: Optical interface reception link degraded
If the number of jitter times of an "Optical port receiving link failure" alarm caused by link
reception frame out-of-lock and a high bit error rate exceeds this threshold in a past period
of time, this alarm is raised.
Alarm Cause
1. Fibers or cables are damaged.
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. The optical or electrical module of the peer equipment is damaged.
5. The actual fiber length is longer than the maximum length supported by the optical
module.
6. The peer equipment is operating abnormally.
Impact
None.
May cause service quality to become worse.
Action
1. 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:
5-160
SJ-20141022095204-005|2015-07-27 (R2.2)
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 2.
c.
During diagnostic tests, diagnose the board based on the information about rack
port No. in alarm details, query the maximum distance supported by the optical
module, and then check whether fiber length is longer 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. Verify that optical fibers are properly connected.
Yes -> Substep f.
No -> Substep g.
f.
Check whether the surfaces of fiber connectors are dirty.

Yes -> Substep h.
No -> Substep i.
g. Properly connecting the optical 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 2.
5-161
SJ-20141022095204-005|2015-07-27 (R2.2)
No -> Substep j.
j.
Replace fibers.
Yes -> End.
No -> Step 2.
Yes -> End.
No -> Step 3.
Yes -> End.
No -> Step 4.
4. Inform the maintenance personnel of the peer equipment to check whether the peer
equipment is abnormal.
Yes -> Maintenance personnel handle peer equipment faults.
5.94 198098440 Disable PA

Alarm Information
l
l
l
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.
5-162
SJ-20141022095204-005|2015-07-27 (R2.2)
Impact
None.
The service supported by the channel is interrupted.
Action
a. Check whether related alarms are raised. If they are raised, Handle the alarms in
follows:
198098465 VSWR of the antenna feeder abnormal
198098466 Temperature abnormal
198098467 Internal fault
YesEnd.
NoStep 2.
2. Select Dynamic Management -> Dynamic CommandSDRDevice GroupRRU to
enable the PA of the corresponding channel
YesEnd.
NoStep 3.
YesEnd.
5.95 198098465 VSWR of the antenna feeder abnormal

Alarm Information
l
l
l
l

Name: VSWR of the antenna feeder abnormal
5-163
SJ-20141022095204-005|2015-07-27 (R2.2)
Alarm Description
This alarm occurs when the VSWR of the antenna feeder exceeds the threshold.
Alarm Cause
The antenna feeder cable is wrongly connected.
Impact
None.
When the standing wave ratio level is set to minor, there is no impact on the services on
this channel.
When the standing wave ratio level is set to critical, lowering the transmit power may reduce
the forward coverage range.
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.
The lower VSWR threshold (minor VSWR threshold) for LTE FDD is set to 2, and
the upper threshold (critical VSRW threshold) is set to 3 by default. The lower
VSWR threshold for TD-LTE is set to 2.6, and the upper threshold is set to 4 by
default. In most cases, you can modify the lower VSRW threshold if required, but
setting the lower VSWR threshold to be less than 1.5 is not recommended.
YesStep 2.
NoSubstep b.
b. Configure the threshold of the standing wave ratio to higher values as needed.
c.

YesEnd.
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.
YesStep 3.
NoSubstep b.
5-164
SJ-20141022095204-005|2015-07-27 (R2.2)
b. Connect the cables of the antenna and feeder to the RRU correctly.
c.

YesEnd.
NoStep 3.
3. Verify that the cables are properly connected.

a. Check whether the cables are properly connected (For example, the connectors
are not secured).
YesStep 4.
NoSubstep b.
b. Troubleshoot the circuit faults.
c.

YesEnd.
NoStep 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.
YesStep 5.
NoSubstep b.
b. Replace the board according to the rack number/shelf number/slot number in the
alarm details.
YesEnd.
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.
YesEnd.
5.96 198098466 Temperature abnormal

Alarm Information
l
l
l

Name: Temperature abnormal
5-165
SJ-20141022095204-005|2015-07-27 (R2.2)
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
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).
YesEnd.
NoStep 2.
YesEnd.
5.97 198098467 Internal fault

Alarm Information
l
l
l
l

Name: Internal fault
Alarm Description
This alarm occurs when a fault occurs during device running process.
5-166
SJ-20141022095204-005|2015-07-27 (R2.2)
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
YesEnd.
NoStep 2.
2. In the diagnostic test, check whether the board hardware detection function is available
in the toolbar.
YesStep 3.
3. Perform the board hardware detection operation, and take action in accordance with
the test result.
YesEnd.
5.98 198098468 External extended device fault

Alarm Information
l
l
l
l

Name: External extended device fault
Alarm Description
This alarm occurs when the external extended device has wrong configuration parameter
or it works improperly.
5-167
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
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 ManagementDynamic CommandSDRAISG Device, and
reset the AISG device according to the antenna number/rack number/device type
in the additional alarm information in the alarm details.
YesEnd.
NoStep 2.
2. Replace the device according to the antenna number/rack number/device type in
YesEnd.
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.
YesStep 2.
NoSubstep b.
b. Re-connect the cable.
5-168
SJ-20141022095204-005|2015-07-27 (R2.2)
c. Wait for 15 minutes, and check whether the alarm is cleared.

YesEnd.
NoStep 2.
2. Reset the board according to the rack number/shelf number/slot number in the
YesEnd.
NoStep 3.
YesEnd.
l
Device address conflict:

Scan and add a new device in the AISG device management.
YesEnd.
Failure in gain configuration:

1. Re-configure the uplink gain of the device.
a. Select Configuration ManagementManaged ElementDeviceBTS
Auxiliary Peripheral DeviceAntenna ServiceTMS Device, and configure
the uplink gain to the value within the scope of gains supported by the device.
c.

YesEnd.
NoStep 2.
2. Select Dynamic Management -> Dynamic CommandSDRAISG Device, and

reset the AISG device according to the antenna number/rack number/device type
in the additional alarm information in the alarm details.
YesEnd.
l
Electrical machine faults, or the electrical machine unable to be adjusted:
5-169
SJ-20141022095204-005|2015-07-27 (R2.2)

perform RET calibration according to the antenna number/rack number/device
type in the additional alarm information in the alarm details.
YesEnd.
NoStep 2.
2. Re-install the electrical machine, and re-perform RET calibration.
YesEnd.
NoStep 3.
YesEnd.
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
YesEnd.
NoStep 2.
2. Re-install the electrical machine, and re-perform RET calibration.
YesEnd.
NoStep 3.
YesEnd.
Working in bypass mode:

configure the tower mounted amplifier to the normal mode according to the
5-170
SJ-20141022095204-005|2015-07-27 (R2.2)
antenna number/rack number/device type in the additional alarm information in

the alarm details.
YesEnd.
NoStep 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.
YesEnd.
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
ManagementManaged
ElementDeviceRRUPowerOutlet Set-> PowerOutlet, and check
whether the undercurrent/overcurrent alarm threshold percentages are
YesStep 2.
NoSubstep b.
b. Modify the alarm threshold percentages as planned.
c.

YesEnd.
NoStep 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).
YesStep 3.
NoSubstep b.
b. Re-connect the cables.
c.

YesEnd.
NoStep 3.

5-171
SJ-20141022095204-005|2015-07-27 (R2.2)

YesEnd.
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.
a. Select
Configuration
ManagementManaged
ElementDeviceRRUAISG 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
YesStep 2.
NoSubstep b.
b. Modify the device type to be the same as that of the actual device.
c.

YesEnd.
NoStep 2.
YesEnd.
l
Tilt of RET is faulty:

1. Select Dynamic Management -> Dynamic Command -> SDR -> AISG Device, and
perform RET calibration according to the antenna number/rack number/device
type/right tilt value in the additional alarm information in the alarm details.
YesEnd.
5.99 198098469 Abnormal RX channel

Alarm Information
l
l

Name: Abnormal RX channel
5-172
SJ-20141022095204-005|2015-07-27 (R2.2)
l
l

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
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.
YesStep 2.
2. Clear the external interference sources.
YesEnd.
Imbalanced main set/diversity receiving:
1. Verify that the switch of detecting the main set/diversity balance is configured correctly:
a. Select Configuration ManagementManaged ElementDeviceRF Device
SetRF Port objectTx Device, and check whether the main set/diversity
balance detection is configured as planned according to the rack number/shelf
YesStep 2.
5-173
SJ-20141022095204-005|2015-07-27 (R2.2)
NoSubstep b.
b. Modify the main set/diversity balance detection as planned.
c.

YesEnd.
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.
YesStep 3.
NoSubstep b.
b. Connect the cables of the antenna and feeder to the RRU correctly.
c.

YesEnd.
NoStep 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.
YesSubstep b.
b. Clear the external interference sources.
YesEnd.
5.100 198098470 Blocked resources manually

Alarm Information
l
l
l
l

Name: Blocked resources manually
Alarm Description
This alarm occurs when resources are blocked manually.
5-174
SJ-20141022095204-005|2015-07-27 (R2.2)
Alarm Cause
The resources are blocked manually.
Impact
None.
The blocked resources cannot process services.
Action
l
Enable the PA:

Select Dynamic ManagementDynamic CommandSDRDevice GroupRRU.
The corresponding tab is displayed. Enable the PA.
YesEnd.
Block the board:

Select Dynamic Management -> Dynamic CommandSDRDevice Group. The
Device Group tab is displayed. Unblock the board.
YesEnd.
5.101 198098471 Carrier downlink data problem

Alarm Information
l
l
l
l

Name: Carrier downlink data problem
This alarm is reported when the downlink IQ channel of the RRU receives incorrect data.
5-175
SJ-20141022095204-005|2015-07-27 (R2.2)
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:
Optical port receiving link failure (198098319)
The received optical power of the optical module is abnormal (198092431)
YesEnd.
NoStep 2.
YesEnd.
5.102 198098472 RRU Power Abnormal Alarm

Alarm Information
l
l
l
l

Name: RRU Power Abnormal Alarm
Alarm Description
This alarm occurs when the detected RRU power is abnormal.
5-176
SJ-20141022095204-005|2015-07-27 (R2.2)
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
YesEnd.
NoStep 2.
2. Power off reset the board according to the rack number/shelf number/slot number in
the alarm details. Refer to Reset Boards.
YesEnd.
NoStep 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.
YesEnd.
NoStep 4.
Element, and reset the NE.
5-177
SJ-20141022095204-005|2015-07-27 (R2.2)

YesEnd.
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.
YesEnd.
NoStep 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.
YesEnd.
NoStep 7.
7. Replace the board according to the rack number/shelf number/slot number displayed
in the alarm details. for 15 minutes, and check whether the alarm is cleared.
YesEnd.
5.103 198098473 The baseband signal input to the TX

channel is abnormal
Alarm Information
l
l
l
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.
5-178
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
a. Select Configuration ManagementManaged ElementDevice, 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
in substep a.
YesEnd.
NoStep 2.
2. Select Dynamic ManagementDynamic CommandSDRDevice Group, and reset
the main control board.
YesEnd.
5.104 198098474 RRU fan failure

Alarm Information
l
l
l
l

Name: RRU fan failure
This alarm occurs when the fan on the Fan Control Element (RRU) is faulty.
5-179
SJ-20141022095204-005|2015-07-27 (R2.2)
Alarm Cause
1. The fan is blocked.
Impact
The equipment temperature might be too high, overtemperature may affect the life of the
equipment.
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.
Yes -> End.
5.105 198092117 Embedded power Rectifier Module

Fault
Alarm Information
l
l
l
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.
5-180
SJ-20141022095204-005|2015-07-27 (R2.2)
2.
3.
4.
5.
6.
The air circuit breaker corresponding to the rectifier module is disconnected.

The rectifier module is faulty.
The slots in the rectifier cabinet are damaged.
The socket of the monitoring unit does not have good contact or is disconnected.
The monitoring unit is faulty.
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.
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.
a. 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.
5-181
SJ-20141022095204-005|2015-07-27 (R2.2)
b. Replace the rectifier where the alarm is located.

Yes End.
No Step 4.
4. Change the installation slot of the rectifier.
Yes End.
No Step 5.
Yes Step 6.
No Substep b.
Yes End.
No Step 6.
YesEnd.
5.106 198092091 Embedded power SMR CommFail

Alarm Information
l
l
l
l

Name: Embedded power SMR CommFail
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.
5-182
SJ-20141022095204-005|2015-07-27 (R2.2)
3. If the AC power supply is powered off, the actual load is lower than the lower load
threshold.
Impact
Action
1. Check whether this alarm exists in all rectifiers.
YesStep 2.
NoStep 3.
Embedded power AC Power Off (198092074)
YesEnd.
NoStep 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.
YesStep 4.
NoSubstep b.
YesEnd.
NoStep 4.
5-183
SJ-20141022095204-005|2015-07-27 (R2.2)

YesEnd.
NoStep 5.
YesEnd.
5.107 198100078 Abnormal input dry contact one of

built-in power
Alarm Information
l
l
l
l

Name: Abnormal input dry contact one of built-in power
Alarm Description
This alarm occurs when the input dry contact one is abnormal.
Alarm Cause
Impact
None.
may be affected.
Action
YesStep 2.
NoSubstep b.
5-184
SJ-20141022095204-005|2015-07-27 (R2.2)

YesEnd.
NoStep 2.
YesEnd.
5.108 198100079 Abnormal input dry contact two of

built-in power
Alarm Information
l
l
l
l

Name: Abnormal input dry contact two of built-in power
Alarm Description
This alarm occurs when the input dry contact two is abnormal.
Alarm Cause
Impact
None.
may be affected.
Action
YesStep 2.
NoSubstep b.
5-185
SJ-20141022095204-005|2015-07-27 (R2.2)

YesEnd.
NoStep 2.
YesEnd.
5.109 198100080 Abnormal input dry contact three of

built-in power
Alarm Information
l
l
l
l

Name: Abnormal input dry contact three of built-in power
Alarm Description
This alarm occurs when the input dry contact three is abnormal.
Alarm Cause
Impact
None.
may be affected.
Action
YesStep 2.
NoSubstep b.
5-186
SJ-20141022095204-005|2015-07-27 (R2.2)

YesEnd.
NoStep 2.
YesEnd.
5.110 198100081 Abnormal input dry contact four of

built-in power
Alarm Information
l
l
l
l

Name: Abnormal input dry contact fiur of built-in power
Alarm Description
This alarm occurs when the input dry contact four is abnormal.
Alarm Cause
Impact
None.
may be affected.
Action
YesStep 2.
NoSubstep b.
5-187
SJ-20141022095204-005|2015-07-27 (R2.2)

YesEnd.
NoStep 2.
YesEnd.
5.111 198100280 The output power of the TX channel

is abnormal
Alarm Information
l
l
l
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.
5-188
SJ-20141022095204-005|2015-07-27 (R2.2)
a. Select Alarm MonitoringHistory Alarms, and check whether the alarm is raised
frequently.
YesStep 2.
NoSubstep b.
b. Check whether the alarm lasts for less than 10 minutes.
YesSubstep c.
NoStep 2.
c.

YesEnd.
No Step 2.
RRU where the alarm is located. Refer to Reset Boards.
a. Select Configuration ManagementManaged ElementDevice, 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
in substep a. Refer to Reset Boards.
YesEnd.
NoStep 3.
3. Replace the board according to the rack number/shelf number/slot number in the alarm
details.
YesEnd.
5.112 198100283 Smart antenna calibration is abnormal

Alarm Information
l
l
l
l

Name: Smart antenna calibration is abnormal
5-189
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
YesStep 2.
NoSubstep b.
b. Connect the cable correctly.
c.

YesEnd.
NoStep 2.
2. Check whether connectors of the antenna and feeder are secured.

a. Check whether connectors of the antenna and feeder are secured.
YesStep 2.
NoSubstep b.
b. Secure the connectors.
c.

YesEnd.
NoStep 3.
YesEnd.
5-190
SJ-20141022095204-005|2015-07-27 (R2.2)
5.113 198094829 eNodeB synchronization abnormal

Alarm Information
l
l
l
l

Name: eNodeB synchronization abnormal
eNodeB's clock PLL can not lock any configured clock source.
Alarm Cause
The duration when the PLL is in holdover, free running or assist phase control status
exceeds the alarm threshold.
Impact
I. Board status:
Operates properly.
Air interface synchronization may be affected. When the synchronization timeout function
is enabled, the eNodeB services are interrupted.
Action
1. Check whether related alarms exist. If such alarms exist, remove them based on the
corresponding handling suggestion. The related alarm is as follows:
No available clock source (198092217)
YesEnd.
No1. There is strong external interference..
5.114 198094839 Reverse link RSSI minor alarm

Alarm Information
l
l
l

Name: Reverse link RSSI minor alarm
5-191
SJ-20141022095204-005|2015-07-27 (R2.2)
The value of RSSI over reverse link exceeds level 1 threshold, and below level 2 threshold,
this alarm is reported.
Alarm Cause
There is strong external interference.
Impact
I. Board status:
Operates properly.
Uplink coverage of the cell shrinks or user uplink services fail to be accessed.
Action
1. Check the NI statistics in the KPIs to determine whether there is strong interference in
the wireless network.
a. Select PerformanceHistory Performance Data Query, view the NI counters
(C373586700 C373586899) and check whether interference exists.
YesSubstep b.
b. Locate and eliminate the interference source. Check whether the alarm is cleared.
YesEnd.
5.115 198094840 Reverse link RSSI major alarm

Alarm Information
l
l
l
l

Name: Reverse link RSSI major alarm
The value of RSSI over reverse link exceeds level 2 threshold, this alarm is reported.
5-192
SJ-20141022095204-005|2015-07-27 (R2.2)
Alarm Cause
There is strong external interference.
Impact
I. Board status:
Operates properly.
Uplink coverage of the cell shrinks or user uplink services fail to be accessed.
Action
1. Check the NI statistics in the KPIs to determine whether there is strong interference in
the wireless network.
a. Select PerformanceHistory Performance Data Query, view the NI counters
(C373586700 C373586899) and check whether interference exists.
YesSubstep b.
b. Locate and eliminate the interference source. Check whether the alarm is cleared.
YesEnd.
5.116 198094847 RF channel attenuation consistency

alarm
Alarm Information
l
l
l
l

Name: RF channel attenuation consistency alarm
The power difference of RF channels is greater than alarm threshold.
Alarm Cause
Incorrect installation of the RF cable may cause this alarm.
Impact
I. Board status:
5-193
SJ-20141022095204-005|2015-07-27 (R2.2)
Operates properly.
The uplink and downlink power and the service throughput of the cell may be decreased.
Action
1. Check the installation of the RF cable.
a. Check whether the installation of the RF cable is correct.
YesStep 2.
NoSubstep b.
b. Re-install the RF cable and check whether the alarm is cleared.
YesEnd.
NoStep 2.
2. Check whether the RF cable is loose.
a. Check whether the RF cable is loose.
YesSubstep b.
b. Fix the RF cable and check whether the alarm is cleared.
YesEnd.
5.117 198094848 Antenna calibration failure

Alarm Information
l
l
l
l

Name: Antenna calibration failure
Antenna calibration failure.
Alarm Cause
1. The antenna channel hardware is faulty.
2. The antenna channel is manually blocked
Impact
I. Board status:
5-194
SJ-20141022095204-005|2015-07-27 (R2.2)
Operates properly.
The beam forming of the cell may be affected and the service quality may be degraded.
Action
1. Check whether the antenna channel is manually blocked.
a. Select Diagnosis TestCombine Test, select the alarmed RRU board and "IR RRU
Status Query", and click OK.
b. Check whether the diagnosis result "TX-ANT* Manual Operation Status" (* for
RRU antenna ID) is "Start Up".
YesStep 3.
NoStep 2.
2. Unblock the antenna channel.
a. Select Dynamic ManagementSDRDevice GroupTCMUnblock RRU
Channel, and unblock the alarmed RRU channel.
b. Wait for three hours.
c.

YesEnd.
NoStep 3.
3. Reset the RRU.

a. Select Dynamic ManagementSDRDevice GroupBoard Hardware Reset,
and reset the alarmed RRU.
b. Check whether the alarm is cleared after the RRU operates properly.
YesEnd.
5.118 198097680 POE power supply abnormal

Alarm Information
l
l
l
l

Name: POE power supply abnormal
The voltage of POE is abnormal.
5-195
SJ-20141022095204-005|2015-07-27 (R2.2)
Alarm Cause
1. The -48 voltage of PB is abnormal.
2. Ethernet cable or PicoRRU on the corresponding port is short circuit.
Impact
Equipment on the corresponding port may not be power supplied.
Action
1. Remove the corresponding ethernet cable in accordance with the slot, shelf, and
rack information in the Detail Information dialog box, then check whether the alarm
is cleared.
YesStep 2.
NoStep 4.
2. Replace the ethernet cable, wait 15 minutes, and check whether the alarm is cleared.
YesEnd.
NoStep 3.
3. Replace the PicoRRU, wait 15 minutes, and check whether the alarm is cleared.
YesEnd.
NoStep 4.
4. Replace the PB board, wait 15 minutes, and check whether the alarm is cleared.
YesEnd.
5-196
SJ-20141022095204-005|2015-07-27 (R2.2)
Chapter 6
Communication Alarm
Table of Contents
198092013 High BER rate at the E1/T1 link ...............................................................6-1
198092230 The SCTP association is broken ..............................................................6-3
198092231 The PPP link is broken.............................................................................6-4
198092232 The HDLC link is broken ..........................................................................6-6
198092233 The SSCOP link is broken .......................................................................6-7
198092361 The IMA group is faulty ............................................................................6-8
198092362 The IMA/TC link is faulty ........................................................................6-10
198092399 The BFD connection is broken ............................................................... 6-11
198092401 E1/T1 link self-loop ................................................................................6-12
198092402 The TCP connection is broken ...............................................................6-13
198092428 The SCTP path is broken.......................................................................6-15
198092431 The received optical power of the optical module is abnormal ................6-17
198096839 RRU inner GNSS clock source abnormal...............................................6-18
198097169 The next hop IP is unreachable..............................................................6-20
198097171 Authentication failure .............................................................................6-21
198097172 Configuration parameter of OAM Channel is wrong ...............................6-22
198097175 Remote server unreachable...................................................................6-24
198098252 The physical Ethernet link is broken ......................................................6-26
198098319 Optical port receiving link failure ............................................................6-27
198094830 S1 link is broken ....................................................................................6-30
198094831 X2 link is broken ....................................................................................6-32
198094852 All MME associations interrupted ...........................................................6-35
198094863 S1 GTP-U path unavailable ...................................................................6-35
198094864 X2 GTP-U path unavailable ...................................................................6-36
198094868 The link between eNodeB and iCS is broken .........................................6-37
6.1 198092013 High BER rate at the E1/T1 link

Alarm Information
l
l
l
l

Name: High BER rate at the E1/T1 link
Alarm type: Communications Alarm
6-1
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
YesStep 2.
NoSubstep b.
b. Reconnect the equipment cables.
YesEnd.
NoStep 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.
YesStep 3.
NoSubstep b.
b. Reconnect or replace the cable between the equipment and the grounding busbar.
YesEnd.
6-2
SJ-20141022095204-005|2015-07-27 (R2.2)
Chapter 6 Communication Alarm
NoStep 3.
3. Replace the E1/T1 cables on the SA/SE/PSA front panels.
YesEnd.
NoStep 4.
4. Change the location of the transmission equipment port or replace the repeater.
YesEnd.
6.2 198092230 The SCTP association is broken

Alarm Information
l
l
l
l

Name: The SCTP association is broken
Alarm Description
l
l
l
The Stream Control Transmission Protocol (SCTP) association fails to be established.

The notification that the opposite end is shut down is received.
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
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.
6-3
SJ-20141022095204-005|2015-07-27 (R2.2)
a. Select
Configuration
ManagementManaged
ElementTransmission
NetworkProduct (such as UMTS)Signaling and BusnissSCTP 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.
NoSubstep b.
b. Change the setting of the SCTP association at the local end to be the same as the
network planning.
c.

YesEnd.
NoStep 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.
NoSubstep 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.
NoSubstep 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.
YesEnd.
6.3 198092231 The PPP link is broken

Alarm Information
l
l
l
l

Name: The PPP link is broken
6-4
SJ-20141022095204-005|2015-07-27 (R2.2)
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 broken
YesEnd.
NoStep 2.
2. Ensure that the PPP link is correctly configured.
a. Select
Configuration
ManagementManaged
ElementTransimission
NetworkRadio Standard (such as UMTS)IP TransportPPP Link from the
menu. The PPP Link tab is displayed. Check whether the PPP encapsulation
type matches the network planning.
NoSubstep b.
b. Change the PPP encapsulation type of the local end to be the same as the network
planning.
c.

YesEnd.
6-5
SJ-20141022095204-005|2015-07-27 (R2.2)
6.4 198092232 The HDLC link is broken

Alarm Information
l
l
l
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
a. If the related alarm has been raised, take the corresponding action based on the
alarm handling suggestion. The related alarm is as follows:
YesEnd.
NoStep 2.
2. Ensure that the HDLC channel is correctly configured.
a. Select
Configuration
ManagementManaged
NetworkRadio Standard (such as UMTS)IP TransportHDLC Channel from
the menu. The HDLC Channel tab is displayed. Check whether the time slot bit
mapping matches the network planning
NoSubstep b.
b. Change the time slot bit mapping of the local end to be the same as the network
planning.
6-6
SJ-20141022095204-005|2015-07-27 (R2.2)
c.

YesEnd.
6.5 198092233 The SSCOP link is broken

Alarm Information
l
l
l
l

Name: The SSCOP link is broken
Alarm Description
l
l
l
The SSCOP link fails to be established.

Alarm Cause
The PVC parameters are not configured correctly.
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 IMA/TC link is faulty
YesEnd.
NoStep 2.
6-7
SJ-20141022095204-005|2015-07-27 (R2.2)
2. Ensure that the SaalUni parameters are correctly set.

a. Select
Configuration
ManagementManaged
ElementTransmission
NetworkRadio Standard (such as UMTS)ATM Transport NetworkSaalUni
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.
YesStep 3.
NoSubstep b.
b. Change the settings of the SaalUni parameters at the local end to be the same as
the network planning.
c.

YesEnd.
NoStep 3.
3. Inform the maintenance personnel of the peer device to check whether the
transmission is abnormal.
YesMaintenance personnel of the peer device resolve the transmission fault.
6.6 198092361 The IMA group is faulty

Alarm Information
l
l
l
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.
6-8
SJ-20141022095204-005|2015-07-27 (R2.2)
Impact
None.
All the services of the IMA group are interrupted.
Action
198096832 Line clock source fault
198097109 E1/T1 link is interrupted
YesEnd.
NoStep 2.
2. Verify that the IMA parameters are configured correctly.
a. Select Configuration ManagementManaged Element -> Transmission
NetworkUMTS (for example)ATM Transport Network -> ATM Layer Link,
and check whether the ATM layer protocol type, Enable descrambling, Frame
length, Clock mode, Used physical layer port and Used channelized SMT-1 are
YesStep 3.
NoSubstep b.
b. Modify the corresponding IMA parameters as planned.
c.

YesEnd.
NoStep 3.
3. Contact the maintenance personnel for the peer to verify that the switching devices
including RNC are configured correctly.
YesEnd.
6-9
SJ-20141022095204-005|2015-07-27 (R2.2)
6.7 198092362 The IMA/TC link is faulty

Alarm Information
l
l
l
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.
Action
1. Verify that the IMA/TC parameters are configured correctly.
a. Select
Configuration
ManagementManaged
ElementTransmission
NetworkUMTS (for example)ATM Transport NetworkATM 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
YesStep 2.
NoSubstep b.
b. Modify the corresponding IMA/TC parameters as planned.
c.

YesEnd.
6-10
SJ-20141022095204-005|2015-07-27 (R2.2)
NoStep 2.
2. Contact the maintenance personnel for the peer to verify that the switching devices
including RNC are configured correctly.
YesEnd.
NoStep 3.
3. Contact the corresponding maintenance personnel to verify that transmission data is
YesEnd.
6.8 198092399 The BFD connection is broken

Alarm Information
l
l
l
l

Name: The BFD connection is broken
Alarm Description
l
l
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.
6-11
SJ-20141022095204-005|2015-07-27 (R2.2)
Action
1. Ensure that the BFD parameters are correctly set.
a. Select
Configuration
ManagementManaged
ElementTransmission
NetworkRadio Standard (such as UMTS)Network DetectionBidirectional
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.
YesStep 2.
NoSubstep b.
b. Change the settings of the BFD parameters at the local end to be the same as
those at the peer end.
c.

YesEnd.
NoStep 2.
NoSubstep b.
path are correct.
NoSubstep c.
c.
path.
YesEnd.
6.9 198092401 E1/T1 link self-loop

Alarm Information
l
l

Name: E1/T1 link self-loop
6-12
SJ-20141022095204-005|2015-07-27 (R2.2)
l
l

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.
YesSubstep b.
No Step 2.
b. Connect the E1/T1 cable correctly.
YesEnd.
NoStep 2.
2. Contact the corresponding maintenance personnel to verify that transmission is
YesEnd.
6.10 198092402 The TCP connection is broken

Alarm Information
l
l
l
l

Name: The TCP connection is broken
6-13
SJ-20141022095204-005|2015-07-27 (R2.2)
Alarm Description
l
l
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
YesEnd.
NoStep 2.
2. Ensure that the PPP link is correctly configured.
a. Select
Configuration
ManagementManaged
NetworkRadio Standard (such as UMTS)IP TransportPPP Link from the
menu. The PPP Link tab is displayed. Check whether the PPP encapsulation
type matches the network planning.
YesStep 3.
NoSubstep b.
b. Change the PPP encapsulation type of the local end to be the same as the network
planning.
c.

6-14
SJ-20141022095204-005|2015-07-27 (R2.2)
YesEnd.
NoStep 3.
3. Ensure that the TCP parameters are correctly set.
a. Select
Configuration
ManagementManaged
ElementTransmission
NetworkRadio Standard (such as UMTS)Signaling and BusnissTCP 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.
NoSubstep b.
b. Change the TCP setting of the local end to be the same as the network planning.
c.

YesEnd.
6.11 198092428 The SCTP path is broken

Alarm Information
l
l
l
l

Name: The SCTP path is broken
Alarm Description
l
l
No response to the heartbeat is received in some path of the SCTP association.

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.
6-15
SJ-20141022095204-005|2015-07-27 (R2.2)

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
a. Select
Configuration
ManagementManaged
ElementTransmission
NetworkRadio 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.
YesStep 2.
NoSubstep b.
network planning.
c.

YesEnd.
NoStep 2.
NoSubstep b.
path are correct.
NoSubstepc
c.
path.
YesEnd.
6-16
SJ-20141022095204-005|2015-07-27 (R2.2)
6.12 198092431 The received optical power of the

optical module is abnormal
Alarm Information
l
l
l
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
1. The optical fiber is damaged.
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,
slot, shelf, and rack information in the Detail Information dialog box.
YesSubstep c.
NoStep 2.
2. Check whether the fiber length exceeds the maximum distance that the optical module
supports.
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 maximum distance that
the optical module supports in accordance with the optical port number in the Detail
Information dialog box. Check whether the fiber length exceeds the maximum
distance that the optical module supports.
YesSubstep b.
6-17
SJ-20141022095204-005|2015-07-27 (R2.2)
NoStep 3.
b. Check whether the fiber length can be shortened.
YesSubstep c
NoSubstep d
c.
Shorten the fiber length.

YesEnd.
NoStep 3.
d. Replace the optical module with a proper one that can support the transmission
distance.
YesEnd.
NoStep 4.
3. Replace the optical module in accordance with the optical port, slot, shelf, and rack
YesEnd.
NoStep 4.
4. Replace the fiber in accordance with the optical port, slot, shelf, and rack information
YesEnd.
6.13 198096839 RRU inner GNSS clock source

abnormal
Alarm Information
l
l
l
l

Name: RRU inner GNSS clock source abnormal
6-18
SJ-20141022095204-005|2015-07-27 (R2.2)
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
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:
The RRU link is broken(198097605)
GNSS receiver fault(198096835)
GNSS antenna feeder link fault(198096836)
GNSS receiver satellite searching fault(198096837)
YesEnd.
NoStep 2.
YesEnd.
6-19
SJ-20141022095204-005|2015-07-27 (R2.2)
6.14 198097169 The next hop IP is unreachable

Alarm Information
l
l
l
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.
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.
NetworkNetwork DetectionRouting 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.
YesStep 2.
NoSubstep b.
b. Select
Configuration
ManagementManaged
ElementTransmission
NetworkNetwork DetectionRouting 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.
c.

YesEnd.
No Step 2.
6-20
SJ-20141022095204-005|2015-07-27 (R2.2)
2. Inform maintenance personnel of the peer end to check the transmission.

YesMaintenance personnel of the peer end resolve the transmission fault.
6.15 198097171 Authentication failure

Alarm Information
l
l
l
l

Name: Authentication failure
Alarm Description
This alarm occurs when abnormality occurs during authentication process.
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.
YesStep 2.
NoSubstep b.
b. Replace the board in accordance with the Rack Number, Shelf Number, and Slot
YesEnd.
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.
6-21
SJ-20141022095204-005|2015-07-27 (R2.2)
YesSubstep b.
NoStep 3.
b. Connect the cable correctly.
YesEnd.
NoStep 3.
3. Check the connection cable of the local device.
a. Check whether the connection cable of the local device is not damaged.
YesStep 4.
NoSubstep b.
b. Replace the cable.
Yes End.
NoStep 4.
4. Check whether the local DOT1X parameter is configured correctly.
a. Select Configuration Management -> Managed ElementTransmission
NetworkUMTSNetwork 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.
NoSubstep b.
b. Modify the local DOT1X parameter to the setting as planned.
c.

YesEnd.
6.16 198097172 Configuration parameter of OAM

Channel is wrong
Alarm Information
l
l
l
l

Name: Configuration parameter of OAM Channel is wrong
6-22
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
Impact
None.
The system allows the whole table synchronization only, and other services cannot be
used.
Action
1. Select Configuration ManagementManaged 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.
YesStep 3.
NoStep 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).
YesEnd.
6-23
SJ-20141022095204-005|2015-07-27 (R2.2)
6.17 198097175 Remote server unreachable

Alarm Information
l
l
l
l

Name: Remote server unreachable
Alarm type: Communication Alarm
This alarm occurs when the link between the base station and the remote server is
disconnected.
Alarm Cause
The link between the base station and the remote server is disconnected.
Impact
None.
None.
Action
1. Verify SCA Configuration.
a. Select Configuration Management -> Managed Element -> Radio Parameter ->
LTE TDD (for example) -> E-UTRAN Services Configuration -> SCA Configuration
and check whether the SCA UDP configuration is used.
YesStep 2.
NoSubstep b.
b. Select Configuration Management -> Managed Element -> Radio Parameter ->
LTE TDD (for example) -> E-UTRAN Services Configuration -> SCA Configuration
and check whether the SCTP configuration is used.
YesStep 3.
NoSubstep c.
c.
Enable the SCA UDP or SCTP based on the network planning.

e. Wait for 15 minutes and check whether the alarm is cleared.
YesEnd.
NoStep 4.
6-24
SJ-20141022095204-005|2015-07-27 (R2.2)
2. Verify that the destination IP address for signaling collection is correctly configured.
a. Select Configuration Management -> Managed Element -> Transmission Network
-> LTE TDD (for example) -> Signalling and Bussiness -> SCA UDP and check
whether the configured destination IP address for signaling collection is the same
as the IP address of the remote server.
YesStep 4.
NoSubstep b.
b. Modify the destination IP address to the IP address of the remote server.
c.
Send the configuration data to the NE.

YesEnd.
NoStep 4.
3. Verify that the destination IP address for signaling collection is correctly configured.
a. Select Configuration Management -> Managed Element -> Transmission Network
-> LTE TDD (for example) -> Signalling and Bussiness -> SCTP and check whether
the configured destination IP address for signaling collection is the same as the
IP address of the remote server.
YesStep 4.
NoSubstep b.
b. Modify the destination IP address to the IP address of the remote server.
c.

YesEnd.
NoStep 4.
4. Verify that the local and remote transport addresses are reachable.
a. Select Diagnosis Test -> Diagnosis -> IP Channel Test and check whether the local
transport address and remote transport address are reachable.
NoSubstep b.
b. Check whether the intermediate switching equipment (such as a switch) is
correctly configured.
NoSubstep c.
c.
Modify the configuration of the intermediate switching equipment.
d. Send the configuration data to the NE.

e. Wait for 15 minutes and check whether the alarm is cleared.
6-25
SJ-20141022095204-005|2015-07-27 (R2.2)
YesEnd.
6.18 198098252 The physical Ethernet link is broken

Alarm Information
l
l
l
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.
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.
YesStep 2.
NoSubstep b.
YesEnd.
NoStep 2.
2. Replace the cable with a proper one. 15 minutes, and check whether the alarm is
cleared.
6-26
SJ-20141022095204-005|2015-07-27 (R2.2)
YesEnd.
6.19 198098319 Optical port receiving link failure

Alarm Information
l
l
l
l

Name: Optical port receiving link failure
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. 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. The optical or electrical module of the peer equipment is damaged.
5. The actual fiber length is longer than the maximum length supported by the optical
module.
6. The optical or electrical module rate on the local or peer end does not match.
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:
The NE does not support the configured parameters (198097510)
6-27
SJ-20141022095204-005|2015-07-27 (R2.2)
b. b. Check whether the alarm disappears.

YesEnd.
NoStep 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
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.
YesSubstep c.
NoStep 3.
c.
During diagnostic tests, diagnose the board based on the information about rack
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.
YesSubstep d.
NoSubstep e.
d. Replace the optical module with a proper one or reduce fiber length.
Waiting for 15 minutes, Check whether the alarm disappears.
YesEnd.
NoSubstep e.
e. Check whether fiber connections are normal.
YesSubstep f.
NoSubstep g.
f.
Check whether the surfaces of fiber connectors are dirty.

YesSubstep h.
NoSubstep i.
g. Connect fibers.
6-28
SJ-20141022095204-005|2015-07-27 (R2.2)
YesEnd.
NoSubstep i.
h. Clean the fiber connectors.
YesEnd.
NoSubstep i.
i.
Check whether fibers are in good condition.

YesStep 3.
NoSubstep j.
j.
Replace fibers.
YesEnd.
NoStep 3.
3. Check whether the optical module rate on the local or peer end match.
a. Check whether the optical module rate on the local or peer end match.
YesStep 4.
NoSubstep b.
b. Configuration or replace rate matching optical module.
YesEnd.
NoStep 4.
YesEnd.
NoStep 4.
YesEnd.
NoStep 5.
6. Inform the maintenance personnel of the peer equipment to check whether the peer
equipment is abnormal.
YesMaintenance personnel handle peer equipment faults.
6-29
SJ-20141022095204-005|2015-07-27 (R2.2)
6.20 198094830 S1 link is broken

Alarm Information
l
l
l
l

Name: S1 link is broken
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.
Action
"S1 SCTP association is interrupted"Step 2.
"S1AP setup fail"Step 4.
Network > TD-LTE > 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.
YesStep 3.
NoSubstep b.
6-30
SJ-20141022095204-005|2015-07-27 (R2.2)
network planning.
c.

YesEnd.
NoStep 3.
YesContact ZTE technical support
NoSubstep b.
path are correct.
NoSubstep c.
c.
path.
YesEnd.
4. Check whether the eNodeB is configured with cells.

a. Select Configuration Management > Radio Parameter > TD-LTE > E-UTRAN
TDD Cell, and check whether there are cell records available.
YesStep 5.
NoSubstep b.
b. Add a cell record in the list.
c.
Synchronize the configuration data to the eNodeB and check whether the alarm
is cleared.
YesEnd.
NoStep 5.
5. Check whether the S1 configuration parameter is valid.

TDD Cell, and check whether the TAC in the cell record is supported by the core
network.
6-31
SJ-20141022095204-005|2015-07-27 (R2.2)
YesStep 6.
NoSubstep b.
b. Modify the tracking area code to a value supported by the core network.
c.
is cleared.
YesEnd.
NoStep 6.
6. Check whether the PLMNLIST is correct.

TDD 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.
NoSubstep 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.
c.
is cleared.
YesEnd.
6.21 198094831 X2 link is broken

Alarm Information
l
l
l
l

Name: X2 link is broken
When there is at least one X2 interface failure, 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:
6-32
SJ-20141022095204-005|2015-07-27 (R2.2)
Operates properly.
The link between two neighboring eNodeBs is broken, and the X2 interface switchover
between the eNodeBs may be affected.
Action
1. Check whether "X2 link state updating notification" exist in Notification Monitor.
YesStep 2.
"X2 SCTP association is interrupted"Step 3.
"X2AP setup fail"Step 5.
network planning.
YesStep 4.
NoSubstep b.
network planning.
c.

YesEnd.
NoStep 4.
NoSubstep b.
path are correct.
NoSubstep c.
6-33
SJ-20141022095204-005|2015-07-27 (R2.2)
c.
path.
YesEnd.

a. Check whether related alarms exist.
If yes, remove them according to
eNodeB is out of service (198094833)
b. Check whether the related alarm is cleared.
YesEnd.
NoStep 6.
6. 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
alarm is as follows:
e. Check whether the related alarm is cleared.
YesEnd.
NoStep 7.
7. 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 > TD-LTE, view "X2
Black List", and check whether the eNodeBs corresponding to the alarmed X2
interface is on the list.
YesSubstep b.
b. Delete the record from the X2 black list.
c.
is cleared.
6-34
SJ-20141022095204-005|2015-07-27 (R2.2)
YesEnd.
6.22 198094852 All MME associations interrupted

Alarm Information
l
l
l
l

Name: All MME associations interrupted
All associations connected with MME are interrupted.
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
YesEnd.
6.23 198094863 S1 GTP-U path unavailable

Alarm Information
l
l

Name: S1 GTP-U path unavailable
6-35
SJ-20141022095204-005|2015-07-27 (R2.2)
l
l

When there is at least one the path between eNodeB and xGW is unavailable, this alarm
will be reported.
Alarm Cause
l
l
l
The routing table of eNodeB is wrong.

xGW is faulty.
The transmission link between eNodeB and XGW is faulty.
Impact
I. Board status:
Operates properly.
The service provided by the GTPU path is completely interrupted.
Action
Check whether there are any relevant alarms or not.
1. View notification monitoring information and check whether or not there is an S1
GTP-U Path link state upadating notification (198094865).
YesStep 2.
2. Handle all the notifications whose details include the word "Unavailable" according
to the suggestions provided in the S1 GTP-U Path link state upadating notification
(198094865)
Wait for 10 minutes and check whether the alarm is cleared or not.
YesEnd.
6.24 198094864 X2 GTP-U path unavailable

Alarm Information
l
l
l
l

Name: X2 GTP-U path unavailable
6-36
SJ-20141022095204-005|2015-07-27 (R2.2)
When there is at least one X2-U path between eNodeB is unavailable, this alarm will be
reported.
Alarm Cause
l
l
l

Peer end is faulty.
The transmission link of X2-U path is faulty.
Impact
I. Board status:
Operates properly.
The X2 handover will fail.
Action
Check whether there are any relevant alarms or not.
1. View notification monitoring information and check whether or not there is an X2
GTP-U Path link state upadating notification (198094866).
YesStep 2.
2. Handle all the notifications whose details include the word "Unavailable" according
to the suggestions provided in the X2 GTP-U Path link state upadating notification
(198094866).
Wait for 10 minutes and check whether the alarm is cleared or not.
YesEnd.
6.25 198094868 The link between eNodeB and iCS is

broken
Alarm Information
l
l
l
l

Name: The link between eNodeB and iCS is broken
6-37
SJ-20141022095204-005|2015-07-27 (R2.2)
When the link between eNodeB and iCS is broken, this alarm will be reported.
Alarm Cause
The SCTP association is broken.
Impact
I. Board status:
Operates properly.
The link between the eNodeB and the iCS is broken, iCS function such as CSS can not
be used.
Action
network planning.
Yes -> Step 2.
No -> Substep b.
network planning.
c.

Yes -> End.
No -> Step 2.
Yes -> Contact ZTE technical support
No -> Substep b.
path are correct.
Yes -> Contact ZTE technical support
6-38
SJ-20141022095204-005|2015-07-27 (R2.2)
No -> Substep c.
c.
path.
Yes -> End.
6-39
SJ-20141022095204-005|2015-07-27 (R2.2)
6-40
SJ-20141022095204-005|2015-07-27 (R2.2)
Chapter 7
Notification
Table of Contents
198092031 Board initialization process completes .....................................................7-2
198092033 Board power-on failed..............................................................................7-2
198092034 Bit error has been detected during E1 physical layer in the past 24 hours .7-3
198092035 E1 link bit error has been detected in the past 24 hours ...........................7-4
198092058 Software version recover succeed ...........................................................7-5
198092059 Alarm Storm.............................................................................................7-5
198092063 Switchover completes ..............................................................................7-6
198092271 Local benchmark clock unlocked .............................................................7-7
198092312 PPP Negotiatory IP Conflict .....................................................................7-8
198092314 IP Conflict ................................................................................................7-9
198092315 Mac Conflict...........................................................................................7-10
198092381 EFM Link has error data ........................................................................ 7-11
198092392 Product process fails to power on ..........................................................7-12
198092441 IR changeover successful ......................................................................7-13
198092442 No need for IR changeover ....................................................................7-13
198092444 SSCOP fault ..........................................................................................7-14
198096557 Uplink IQ link error .................................................................................7-15
198096566 RRU alarm reset ....................................................................................7-15
198097804 Um interface implements clock synchronization via software .................7-16
198097805 MP voltage abnormal .............................................................................7-17
198097806 PP voltage abnormal..............................................................................7-18
198097864 Product process power-on completes ....................................................7-19
198097865 Switchover fails......................................................................................7-19
198097866 port Active/standby switchover notification .............................................7-20
198097867 Power Amplifier (PA) switch for smart carrier power-on/off .....................7-22
198097907 Opening of Node B via USB finishes......................................................7-23
198097940 LMT is logged in ....................................................................................7-23
198097964 LCK indication .......................................................................................7-24
198097965 CCM Remote MEP Error........................................................................7-25
198097966 CCM Message Error ..............................................................................7-26
198097967 CCM Xconnect Error..............................................................................7-28
198097968 AIS indication.........................................................................................7-29
198098000 Unavailable POD ...................................................................................7-30
198098001 Unconfigured POD.................................................................................7-32
198098002 The License is entering to trying urgency state ......................................7-33
198098003 The license file will soon fall due ............................................................7-34
198098005 System capacity overload ......................................................................7-34
7-1
SJ-20141022095204-005|2015-07-27 (R2.2)
198098020 The Ethernet communication abnormal..................................................7-35

198098021 High BER at the electrical port ...............................................................7-36
198098030 Carrier downlink data problem ...............................................................7-38
198098316 The received optical power is abnormal .................................................7-39
198094861 S1 link-break statistics notification .........................................................7-41
198094862 X2 link state updating notification...........................................................7-42
198094865 S1 GTP-U Path link state updating notification.......................................7-44
198094866 X2 GTP-U Path link state updating notification.......................................7-46
198098459 Unavailable alarm of time slot turn-off function .......................................7-48
198094849 Cloud scheduling cell link fault ...............................................................7-49
198094857 The system capacity will exceed the License limit ..................................7-51
7.1 198092031 Board initialization process completes

Alarm Information
l
l
l
l

Name: Board initialization process completes
Alarm severity: Notification
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.
7.2 198092033 Board power-on failed

Alarm Information
l
l

Name: Board power-on failed
7-2
SJ-20141022095204-005|2015-07-27 (R2.2)
Chapter 7 Notification
l
l

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
7.3 198092034 Bit error has been detected during E1

physical layer in the past 24 hours
Alarm Information
l
l
l
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.
7-3
SJ-20141022095204-005|2015-07-27 (R2.2)
Impact
None.
None.
Action
7.4 198092035 E1 link bit error has been detected in

the past 24 hours
Alarm Information
l
l
l
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
7-4
SJ-20141022095204-005|2015-07-27 (R2.2)
7.5 198092058 Software version recover succeed

Alarm Information
l
l
l
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 ManagementUpgrade Task Management. The Task List tab is
displayed. Download, pre-activate, activate, and apply the upgrade software package.
7.6 198092059 Alarm Storm

Alarm Information
l
l
l
l

Name: Alarm Storm
Alarm Description
This notification occurs when the number of alarms reported within a period of time exceeds
a threshold.
7-5
SJ-20141022095204-005|2015-07-27 (R2.2)
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).
YesStep 2.
2. Handle the alarms in accordance with the corresponding handling suggestions.
7.7 198092063 Switchover completes

Alarm Information
l
l
l
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.
7-6
SJ-20141022095204-005|2015-07-27 (R2.2)
Action
7.8 198092271 Local benchmark clock unlocked

Alarm Information
l
l
l
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.
YesStep 2.
NoEnd.
7-7
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
YesStep 3.
NoEnd.
3. Replace the board according to the rack number/shelf number/slot number in the alarm
details.
NoEnd.
7.9 198092312 PPP Negotiatory IP Conflict

Alarm Information
l
l
l
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 ManagementManaged Element -> Transmission
NetworkRadio 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
7-8
SJ-20141022095204-005|2015-07-27 (R2.2)
2. Synchronize the configuration to the NE.

NoEnd.
7.10 198092314 IP Conflict

Alarm Information
l
l
l
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.
a. Select
Configuration
ManagementManaged
ElementTransmission
NetworkRadio Standard (such as UMTS)IP TransportIP Layer. The IP
Layer tab is displayed. Check whether the IP address is set in accordance with
the network planning data.
YesStep 2.
NoSubstep b.
b. Modify the IP address in accordance with the network planning data.
c.

7-9
SJ-20141022095204-005|2015-07-27 (R2.2)
d. Wait 15 minutes, and check whether the notification is raised again.

NoEnd.
2. Check whether the IP addresses of all devices in the network are set in accordance
with the network planning data.
NoModify the corresponding IP addresses in accordance with the network planning
data.
7.11 198092315 Mac Conflict

Alarm Information
l
l
l
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.
YesStep 2.
2. Construct the network in accordance with the network planning.
7-10
SJ-20141022095204-005|2015-07-27 (R2.2)

NoEnd.
7.12 198092381 EFM Link has error data

Alarm Information
l
l
l
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.
YesStep 2.
NoSubstep b.
b. Replace the board in accordance with the slot, shelf, and rack information in the
YesStep 2.
NoEnd.
2. Verify that the cable connector of the local device is secured.
a. Check whether the cable connector of the local device is secured.
YesStep 3.
NoSubstep b.
7-11
SJ-20141022095204-005|2015-07-27 (R2.2)
b. Reconnect the cable correctly.

YesStep 3.
NoEnd.
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.
YesStep 4.
NoSubstep b.
b. Replace the cable with a proper one.
notification is raised again.
15 minutes, and check whether the
YesStep 4.
No End.
4. Inform maintenance personnel of the peer device to check whether the interface, cable,
and device are in good condition.
NoResolve the peer device fault.
7.13 198092392 Product process fails to power on

Alarm Information
l
l
l
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.
7-12
SJ-20141022095204-005|2015-07-27 (R2.2)
Action
7.14 198092441 IR changeover successful

Alarm Information
l
l
l
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
7.15 198092442 No need for IR changeover

Alarm Information
l
l
l
l

Name: No need for IR changeover
Alarm Description
This notification occurs when there is no need to perform IR switchover.
Alarm Cause
There is no need to perform IR switchover.
7-13
SJ-20141022095204-005|2015-07-27 (R2.2)
Impact
None.
None.
Action
7.16 198092444 SSCOP fault

Alarm Information
l
l
l
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
7-14
SJ-20141022095204-005|2015-07-27 (R2.2)
7.17 198096557 Uplink IQ link error

Alarm Information
l
l
l
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.
YesEnd.
NoStep 2.
2. Replace the board.
YesEnd.
7.18 198096566 RRU alarm reset

Alarm Information
l
l
l

Name: RRU alarm reset
7-15
SJ-20141022095204-005|2015-07-27 (R2.2)
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.
YesStep 2
NoSubstep b
b. After 15 minutes, check whether the alarm is cleared.
YesEnd.
NoStep 2
2. Replace the board.
YesEnd.
7.19 198097804 Um interface implements clock

synchronization via software
Alarm Information
l
l

Name: Um interface implements clock synchronization via software
7-16
SJ-20141022095204-005|2015-07-27 (R2.2)
l
l

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
7.20 198097805 MP voltage abnormal

Alarm Information
l
l
l
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.
7-17
SJ-20141022095204-005|2015-07-27 (R2.2)
Action
Replace the board in accordance with the Rack Number, Shelf Number, and Slot Number
in alarm details.
After 15 minutes, check whether the notification is raised again.
NoEnd.
7.21 198097806 PP voltage abnormal

Alarm Information
l
l
l
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 ManagementManaged Element -> DeviceB8200, 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.
NoStep 2.
b. Check whether there is a switch on the front panel of the board.
YesSubstep c.
7-18
SJ-20141022095204-005|2015-07-27 (R2.2)
NoStep 2.
c.
Set the switch to ON.

After 15 minutes, check whether the notification is raised again.
NoEnd.
2. Replace the board in accordance with the Rack Number, Shelf Number, and Slot
Number in alarm details. 15 minutes, check whether the notification is raised again.
NoEnd.
7.22 198097864 Product process power-on completes

Alarm Information
l
l
l
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
7.23 198097865 Switchover fails

Alarm Information
l

7-19
SJ-20141022095204-005|2015-07-27 (R2.2)
l
l
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
7.24 198097866 port Active/standby switchover

notification
Alarm Information
l
l
l
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.
2. The local-end or remote-end device is abnormal.
Impact
None.
7-20
SJ-20141022095204-005|2015-07-27 (R2.2)

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.
YesEnd.
NoStep 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.
YesSubstep b.
NoStep 3.
c.
YesSubstep d.
NoStep 3.
d. Check whether the active port is set to active according to the additional alarm
YesEnd.
NoStep 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.
YesSubstep c.
NoStep 4.
c.
Check whether the active port is set to active according to the additional alarm
YesEnd.
NoStep 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.
YesSubstep b.
7-21
SJ-20141022095204-005|2015-07-27 (R2.2)

b. Check whether the active port is set to active according to the additional alarm
YesEnd.
7.25 198097867 Power Amplifier (PA) switch for smart

carrier power-on/off
Alarm Information
l
l
l
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.
Action
1. Select Configuration ManagementManaged ElementSystem ParameterPower
Saving Parameter, and check whether the power-saving switch is set to On.
YesStep 2.
7-22
SJ-20141022095204-005|2015-07-27 (R2.2)
2. Select Configuration ManagementManaged ElementRadio ParameterUMTS

(for example), and check whether the carrier shutdown switch corresponding to the
RRU where the alarm is located is set to On.
YesEnd.
7.26 198097907 Opening of Node B via USB finishes

Alarm Information
l
l
l
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
7.27 198097940 LMT is logged in

Alarm Information
l
l
l
l

Name: LMT is logged in
Alarm Description
This notification occurs when LMT is logged in.
7-23
SJ-20141022095204-005|2015-07-27 (R2.2)
Alarm Cause
LMT is logged in.
Impact
None.
None.
Action
1. Check whether the connected LMT is authorized by the carrier.
YesEnd.
NoStep 2.
Element > LMT. The LMT tab is displayed. Disconnect the LMT.
7.28 198097964 LCK indication

Alarm Information
l
l
l
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.
7-24
SJ-20141022095204-005|2015-07-27 (R2.2)
Action
1. Ensure that the CFM parameters on the local end are correctly set.
NetworkNetwork DetectionMD/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.
YesStep 2.
NoSubstep b.
b. Select
Configuration
ManagementManaged
ElementTransmission
Modify the CFM parameters on the local end in accordance with the network
planning data.
c.

YesStep 2.
NoEnd.
2. Check whether the CFM parameters of all devices are set in accordance with the
NoModify the settings in accordance with the network planning data.
7.29 198097965 CCM Remote MEP Error

Alarm Information
l
l
l
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.
7-25
SJ-20141022095204-005|2015-07-27 (R2.2)
Impact
None.
The Ethernet link may become unstable, and service are affected.
Action
a. Select
Configuration
ManagementManaged
ElementTransmission
YesStep 2.
NoSubstep b.
b. Select
Configuration
ManagementManaged
ElementTransmission
planning data.
c.
YesEnd.
NoStep 2.
7.30 198097966 CCM Message Error

Alarm Information
l
l
l
l

Name: CCM Message Error
7-26
SJ-20141022095204-005|2015-07-27 (R2.2)
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
YesStep 2.
NoSubstep b.
b. Select
Configuration
ManagementManaged
ElementTransmission
planning data.
c.
YesEnd.
NoStep 2.
7-27
SJ-20141022095204-005|2015-07-27 (R2.2)
7.31 198097967 CCM Xconnect Error

Alarm Information
l
l
l
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
YesStep 2.
NoSubstep b.
b. Select
Configuration
ManagementManaged
ElementTransmission
planning data.
c.
7-28
SJ-20141022095204-005|2015-07-27 (R2.2)
YesEnd.
NoStep 2.
7.32 198097968 AIS indication

Alarm Information
l
l
l
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).
Impact
None.
Action
a. Select
Configuration
ManagementManaged
ElementTransmission
are set in accordance with the network planning data.
7-29
SJ-20141022095204-005|2015-07-27 (R2.2)
YesStep 2.
NoSubstep b.
b. Select
Configuration
ManagementManaged
ElementTransmission
planning data.
c.

YesStep 2.
NoEnd.
7.33 198098000 Unavailable POD

Alarm Information
l
l
l
l

Name: Unavailable POD
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.
7-30
SJ-20141022095204-005|2015-07-27 (R2.2)
a. Select Configuration ManagementManaged ElementSystem Parameter, and

check whether the number of the PMU devices connected with the base station is
YesStep 2.
NoSubstep b.
b. Modify the number of the PMU devices connected with the base station as
planned.
c.
d. Select Diagnosis TestDiagnosisExternal DeviceBase Station Power Test,

and choose an NE to start testing.
e. Wait for 5 minutes, and check whether the notification is reported again.
YesStep 2.
NoEnd.
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.
YesStep 3.
NoSubstep b.
b. Connect the PMU devices as planned.
c.
Select Diagnosis TestDiagnosisExternal DeviceBase Station Power Test,

d. Wait for 5 minutes, and check whether the notification is reported again.
YesStep 3.
NoEnd.
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.
YesSubstep b.
c.

NoEnd.
7-31
SJ-20141022095204-005|2015-07-27 (R2.2)
7.34 198098001 Unconfigured POD

Alarm Information
l
l
l
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 ManagementManaged ElementSystem Parameter, and
check whether the number of the PMU devices connected with the base station is
YesStep 2.
NoSubstep b.
b. Modify the number of the PMU devices connected with the base station as
planned.
c.
d. Select Diagnosis TestDiagnosisExternal DeviceBase Station Power Test,

e. Wait for 5 minutes, and check whether the notification is reported again.
YesStep 2.
NoEnd.
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.
7-32
SJ-20141022095204-005|2015-07-27 (R2.2)

NoSubstep b.
b. Connect the PMU devices as planned.
c.

NoEnd.
7.35 198098002 The License is entering to trying

urgency state
Alarm Information
l
l
l
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.
Impact
None.
The system operates in the maximum support capacity. All optional functions are not
authenticated, and the maximum capacity is provided.
Action
7-33
SJ-20141022095204-005|2015-07-27 (R2.2)
7.36 198098003 The license file will soon fall due

Alarm Information
l
l
l
l

Name: The license file will soon fall due
Alarm Cause
Impact
None.
Action
license file again.
YesEnd.
7.37 198098005 System capacity overload

Alarm Information
l
l
l
l

Name: System capacity overload
Alarm Description
7-34
SJ-20141022095204-005|2015-07-27 (R2.2)
Alarm Cause
Impact
None.
FDD uplink traffic overload: affecting user access.
FDD downlink traffic overload: affecting user access
Action
license file again.
YesEnd.
7.38 198098020 The Ethernet communication abnormal

Alarm Information
l
l
l
l

Name: The Ethernet communication abnormal
Alarm Description
The Ethernet heartbeat link of PB is faulty.
Alarm Cause
1.The physical link is fault.
2.PicoRRU software runs abnormal.
3.PB software runs abnormal.
Impact
None.
7-35
SJ-20141022095204-005|2015-07-27 (R2.2)
Action
1. Check whether any related alarm exists:
a. If yes, remove it based on the corresponding handling suggestion. Related alarms
are as follows:
YesEnd.
NoStep 2.
2. Get the position of PicoRRU in accordance with the port, slot, shelf, and rack
3. Select Dynamic Management -> SDR -> Equipment Group-> ResetBoard, reset
PicoRRU.
Yesend.
NoStep 4.
4. Get the position of PB in accordance with the slot, shelf, and rack information in the
5. Select Dynamic Management -> SDR -> Equipment Group-> ResetBoard, reset PB.
Yesend.
7.39 198098021 High BER at the electrical port

Alarm Information
l
l
l
l

Name: High BER at the electrical port
Alarm Description
This notification occurs when the Ethernet BER is higher than the alarm threshold.
Alarm Cause
l
The Ethernet cable is not installed properly at the local end or at the remote end.
7-36
SJ-20141022095204-005|2015-07-27 (R2.2)
l
l
l
l
The Ethernet cable is damaged.

The local equipment port or the remote equipment port is damaged.
The Ethernet cable is longer than 100 m.
The remote equipment is not operating properly.
Impact
None.
The services of the cell associated to the optical port are interrupted or the service quality
is affected.
Action
1. Check whether the local end has any related alarm.
a. Check whether the local end has any related alarm. If yes, handle the alarm in
accordance with the corresponding alarm suggestion. The related alarm is as
follows:
b. Wait for 10 minutes, and check whether there is any alarm clearance notification
reported.
YesEnd.
NoStep 2.
2. Extract and insert the Ethernet cable, wait for 10 minutes, and check whether there is
any alarm clearance notification reported.
YesEnd.
NoStep 3.
3. Replace the Ethernet cable, wait for 10 minutes, and check whether there is any alarm
clearance notification reported.
YesEnd.
NoStep 4.
4. Notify the maintenance personnel at the remote end to check whether the equipment
is operating properly.
YesPerform troubleshooting to remove the faults.
7-37
SJ-20141022095204-005|2015-07-27 (R2.2)
7.40 198098030 Carrier downlink data problem

Alarm Information
l
l
l
l

Name: Carrier downlink data problem
Alarm Description
This notification occurs when the downlink IQ channel of the RRU receives incorrect data.
Alarm Cause
The downlink IQ channel receives incorrect data.
Impact
None.
None.
Action
1. Check whether clock-related alarms occur on the main control board.
a. Check whether clock-related alarms occur on the main control board. If so, handle
the faults based on the corresponding treatment suggestions. The relevant alarm:
Too large phase difference between clock sources (198096830)
Input clock of the board abnormal (198098315)
1PPS+TOD clock source fault (198096834)
SyncE clock fault (198096833)
1588 clock source fault (198096831)
Clock source abnormal in stack mode (198096838)
b. Check whether the alarm disappears.
YesEnd.
NoStep 2.
2. Check whether transmission-related alarms exist.
a. Check whether transmission-related alarms exist. If so, handle the faults based
on the corresponding treatment suggestions. The relevant alarm:
7-38
SJ-20141022095204-005|2015-07-27 (R2.2)
Bit error has been detected during E1/T1 physical layer in the past 24 hours (198
092034)
E1/T1 link bit error has been detected in the past 24 hours (198092035)
YesEnd.
NoStep 3.
3. Check whether clock-related alarms occur on RRU.
a. Check whether clock-related alarms occur on RRU. If so, handle the faults based
on the corresponding treatment suggestions. The relevant alarm:
RRU inner GNSS clock source abnormal (198096839)
Local benchmark clock unlocked (198092271)
YesEnd.
NoStep 4.
YesEnd.
7.41 198098316 The received optical power is abnormal

Alarm Information
l
l
l
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
1. The optical fiber is damaged.
2. The optical module is aging.
3. The actual optical fiber length is longer than the length supported by the optical module.
7-39
SJ-20141022095204-005|2015-07-27 (R2.2)
Impact
None.
Action
1. Remove and re-install the fiber or optical module in accordance with the optical port,
slot, shelf, and rack information in the Detail Information dialog box.
YesEnd.
NoStep 2.
2. Check whether the fiber length exceeds the maximum distance that the optical module
supports.
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 maximum distance that
the optical module supports in accordance with the optical port number in the Detail
Information dialog box. Check whether the fiber length exceeds the maximum
distance that the optical module supports.
YesSubstep b.
NoStep 3.
b. Check whether the fiber length can be reduced.
YesSubstep c.
NoSubstep d.
c.
Reduce the fiber length.

YesEnd.
NoStep 3.
d. Replace the optical module with a proper one. 15 minutes, and check whether the
alarm is cleared.
YesEnd.
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. 15 minutes, and check whether the
alarm is cleared.
YesEnd.
7-40
SJ-20141022095204-005|2015-07-27 (R2.2)
NoStep 4.
4. Replace the fiber in accordance with the optical port, slot, shelf, and rack information in
the Detail Information dialog box. 15 minutes, and check whether the alarm is cleared.
YesEnd.
7.42 198094861 S1 link-break statistics notification

Alarm Information
l
l
l
l

Name: S1 link-break statistics notification
Alarm Description
Notification of S1 interface link-break statistics in 24 hours.
Alarm Cause
Notification of S1 interface link-break statistics in 24 hours.
Impact
None.
If the number of S1 link-break is zero, there is no impact to services. Otherwise, the link
between the eNodeB and the MME is broken, and the eNodeB may fail to provide services.
Action
1. Check whether the "S1 link is broken(198094830)" alarms is cleared.
YesStep 3.
NoStep 2.
2. Refer to "S1 link is broken(198094830)" corresponding handling suggestions.
3. Check whether the number of S1 link-break in 24 hours is larger than the number of
"S1 link is broken(198094830)" alarm .
YesStep 4.
NoEnd.
7-41
SJ-20141022095204-005|2015-07-27 (R2.2)
4. If the number of S1 link-break in 24 hours is larger than the number of "S1 link is
broken(198094830)" alarm, it means that S1 link was break shortly. Check the alarm
cause, see the handling suggestions of "S1 link is broken(198094830)" alarm.
7.43 198094862 X2 link state updating notification

Alarm Information
l
l
l
l

Name: X2 link state updating notification
Alarm Description
When the state of X2 interface is changed, this notification will be reported.
Alarm Cause
2. The X2AP fails to be established (due to negotiation failure or no cells available under
the eNodeB).
3. The X2 interface is back to normal state.
Impact
None.
If the X2 interface isn't in normal state, the X2 interface switchover between eNodeBs will
be interrupted.
Action
1. View the details of the notification and find the cause of the problem.
"X2 SCTP association is interrupted"Step 2.
"X2AP setup fail"Step 4.
network planning.
YesStep 3.
7-42
SJ-20141022095204-005|2015-07-27 (R2.2)
NoSubstep b.
network planning.
c.

YesEnd.
NoStep 3.
NoSubstep b.
path are correct.
NoSubstep c.
c.
path.
YesEnd.

a. Check whether related alarms exist.
If yes, remove them according to
b. Check whether the related alarm is cleared.
YesEnd.
NoStep 5.
5. 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.
7-43
SJ-20141022095204-005|2015-07-27 (R2.2)
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
alarm is as follows:
e. Check whether the related alarm is cleared.
YesEnd.
NoStep 6.
6. 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 > TD-LTE, view "X2
Black List", and check whether the eNodeBs corresponding to the alarmed X2
interface is on the list.
YesSubstep b.
b. Delete the record from the X2 black list.
c.
is cleared.
YesEnd.
7.44 198094865 S1 GTP-U Path link state updating

notification
Alarm Information
l
l
l
l

Name: S1 GTP-U Path link state updating notification
Alarm Description
When the state of S1 GTP-U Path is changed, this notification will be reported.
Alarm Cause
l
l
l

xGW is faulty.
The transmission link between eNodeB and xGW is faulty.
7-44
SJ-20141022095204-005|2015-07-27 (R2.2)
Impact
None.
The service provided by the GTP-U path is completely interrupted.
Action
1. Check whether the word "Unavailable" is present in the notification details or not. The
S1 user plane path whose notification details include the word "Unavailable" is faulty.
YesStep 2.
NoEnd.
2. Select Configuration Management > Transmission Network > IP Configuration
and check whether the Default Gateway parameter is correctly configured or not.
Select Configuration Management > Transmission Network > Static Routing and
check whether the Static Routing Table parameter is correctly configured or not.
YesStep 4.
NoStep 3.
3. Modify the values of the Default GateWay and Static Routing Table parameters and
synchronize the configurations to the eNodeB.
Wait for 10 minutes and check whether the notification is cleared or not and whether
the word "Unavailable" in the notification details is changed to "Available" or not.
YesEnd.
NoStep 4.
4. Check whether or not the xGW can be successfully pinged from the eNodeB.
YesStep 6.
NoStep 5.
5. Troubleshoot the transmission link between the eNodeB and the xGW.
Wait for 10 minutes after the link fault is removed and check whether the notification is
cleared or not and whether the word "Unavailable" in the notification details is changed
to "Available" or not.
YesEnd.
NoStep 6.
6. Check whether the xGW operates properly or not.
NoStep 7.
7. Contact the customer service center of the xGW to troubleshoot the xGW.
7-45
SJ-20141022095204-005|2015-07-27 (R2.2)
Wait for 10 minutes after the xGW resumes operation and check whether the
notification is cleared or not and whether the word "Unavailable" in the notification
details is changed to "Available" or not.
YesEnd.
NoContact ZTE technical support
7.45 198094866 X2 GTP-U Path link state updating

notification
Alarm Information
l
l
l
l

Name: X2 GTP-U Path link state updating notification
Alarm Description
When the state of X2 GTP-U Path is changed, this notification will be reported.
Alarm Cause
l
l
l

Peer end is faulty.
The transmission link of X2-U path is faulty.
Impact
None.
The X2 handover will fail.
Action
1. Check whether the word "Unavailable" is present in the notification details or not. The
X2 user plane path whose notification details include the word "Unavailable" is faulty.
YesStep 2.
NoEnd.
2. Check whether there are any relevant alarms or not.
a. Check whether there are any relevant alarms or not. If yes, troubleshoot according
to the handling suggestions for the following alarms:
X2 link is broken (198094831)
7-46
SJ-20141022095204-005|2015-07-27 (R2.2)
b. Wait for 10 minutes and check whether the notification is cleared or not and
whether the word "Unavailable" in the notification details is changed to "Available"
or not.
YesEnd.
NoStep 3.
3. Select Configuration Management > Transmission Network > IP Configuration
and check whether the Default Gateway parameter is correctly configured or not.
Select Configuration Management > Transmission Network > Static Routing and
check whether the Static Routing Table parameter is correctly configured or not.
YesStep 5.
NoStep 4.
4. Modify the values of the Default GateWay and Static Routing Table parameters and
synchronize the configurations to the eNodeB. Wait for 10 minutes and check whether
the notification is cleared or not and whether the word "Unavailable" in the notification
YesEnd.
NoStep 5.
5. Check whether the peer eNodeB at the remote end of the X2-U path operates properly
or not.
YesStep 7.
NoStep 6.
6. Troubleshoot the peer eNodeB. Wait for 10 minutes after the peer eNodeB resumes
operation and check whether the notification is cleared or not and whether the word
"Unavailable" in the notification details is changed to "Available" or not.
YesEnd.
NoStep 7.
7. Check whether or not the peer eNodeB at the remote end of the X2-U path can be
successfully pinged from the local eNodeB.
NoStep 8.
8. Troubleshoot the transmission link between the two eNodeBs at both ends of the
X2-U path. Wait for 10 minutes after the link fault is removed and check whether
the notification is cleared or not and whether the word "Unavailable" in the notification
YesEnd.
7-47
SJ-20141022095204-005|2015-07-27 (R2.2)
7.46 198098459 Unavailable alarm of time slot turn-off

function
Alarm Information
l
l
l
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.
NoStep 2.
2. Verify that the time slot shutdown parameters are properly configured.
a. Select Configuration ManagementManaged ElementDeviceRF Device
SetRF Port ObjectPA, and check whether the switch of shutting down
the PA based on time slots is closed according to the rack number/shelf
7-48
SJ-20141022095204-005|2015-07-27 (R2.2)
NoSubstep b.
b. Disable the switch of shutting down the PA according to time slots.
c.

YesEnd.
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
YesEnd.
7.47 198094849 Cloud scheduling cell link fault

Alarm Information
l
l
l
l

Name: Cloud scheduling cell link fault
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.
7-49
SJ-20141022095204-005|2015-07-27 (R2.2)
The alarmed cell may be back to static ICIC.
Action
1. Check whether the cloud scheduling function is enabled for the alarmed cell.
TDDICIC, and check whether the "Downlink ICIC Mode Select Flag" parameter
is set to "Cloud ICIC".
YesStep 2.
NoSubstep b.
b. Modify the value of the "Downlink ICIC Mode Select Flag" parameter to "Cloud
ICIC".
c.
d. Wait for several seconds and check whether the notification is cleared.
YesEnd.
NoStep 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
alarms are as follows:
Cell outage (198094832)
b. Wait for several seconds and check whether the notification is cleared.
YesEnd.
NoStep 3.
3. Check whether the status of the CC board and CS board of the cloud scheduler is
normal.
a. Select Dynamic ManagementSDRQuery Board, and check whether the status
of the CC board and CS board is normal.
YesStep 4.
NoSubstep 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:
c.
Wait for several seconds and check whether the notification is cleared.
YesEnd.
7-50
SJ-20141022095204-005|2015-07-27 (R2.2)
NoStep 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.
YesContact technical support.
NoSubstep b.
b. Remove the transmission fault.
c.
Check whether the notification is cleared.

YesEnd.
7.48 198094857 The system capacity will exceed the

License limit
Alarm Information
l
l
l
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.
YesEnd.
7-51
SJ-20141022095204-005|2015-07-27 (R2.2)
7-52
SJ-20141022095204-005|2015-07-27 (R2.2)
Glossary
ALCAP
- Access Link Control Application Protocol
BBU
- Base Band Unit
BER
- Bit Error Rate
BFD
- Bidirectional Forwarding Detection
BSC
- Base Station Controller
CCM
- Communication Control Module
CFM
- Connectivity Fault Management
CPU
- Central Processing Unit
EFM
- Ethernet in the First Mile
GNSS
- Global Navigation Satellite System
HDLC
- High-level Data Link Control
HDMI
- High-Definition Multimedia Interface
IMA
- Inverse Multiplexing over ATM
LMT
- Local Maintenance Terminal
MEP
- MEG End Point
MME
- Mobility Management Entity
MRO
- Mobility Robustness Optimization
I
SJ-20141022095204-005|2015-07-27 (R2.2)
NE
- Network Element
OAM
- Operation, Administration and Maintenance
OMC
- Operation & Maintenance Center
PA
- Power Amplifier
POE
- power over Ethernet
PPP
- Point to Point Protocol
PSU
- Power Supervision Unit
PVC
- Permanent Virtual Channel
PWR
- Power
QoS
- Quality of Service
RNC
- Radio Network Controller
RRU
- Remote Radio Unit
SA
- Site Alarm
SCTP
- Stream Control Transmission Protocol
SNTP
- Simple Network Time Protocol
SSCOP
- Service Specific Connection Oriented Protocol
TCP
- Transmission Control Protocol
UCI
- Universal Clock Interface
VSWR
- Voltage Standing Wave Ratio
II
SJ-20141022095204-005|2015-07-27 (R2.2)
Glossary
eNodeB
- Evolved NodeB
xGW
- Extendable Gateway
III
SJ-20141022095204-005|2015-07-27 (R2.2)

Sj-20141110151550-003-Zxsdr Uniran Tdd-Lte (v3.20.50) Alarm Handling

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sj-20141110151550-003-Zxsdr Uniran Tdd-Lte (v3.20.50) Alarm Handling

Uploaded by

Copyright:

Available Formats

ZXSDR UniRAN

TD-LTE Base Station

Additionally, the contents of this document are protected by

contractual confidentiality obligations.

Updated Version: V3.20.50.31

Updated Version: V3.20.50.30

ZTE Proprietary and Confidential

Updated Version: V3.20.50.30

Updated Version: V3.20.50.20

Updated Version: V3.20.50.06

Serial Number: SJ-20141110151550-003

ZTE Proprietary and Confidential

ZTE Proprietary and Confidential

Chapter 3 QoS Alarm ................................................................................. 3-1

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

ZTE Proprietary and Confidential

4.9 198092106 Embedded power Environment is over-temperature .......................... 4-18

Chapter 5 Equipment Alarm ...................................................................... 5-1

ZTE Proprietary and Confidential

5.21 198092088 Embedded power SMR Env.H.T .................................................... 5-35

ZTE Proprietary and Confidential

5.58 198092292 Optical fiber connection error ......................................................... 5-99

ZTE Proprietary and Confidential

5.95 198098465 VSWR of the antenna feeder abnormal .........................................5-163

Chapter 6 Communication Alarm.............................................................. 6-1

ZTE Proprietary and Confidential

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

ZTE Proprietary and Confidential

7.23 198097865 Switchover fails............................................................................. 7-19

ZTE Proprietary and Confidential

About This Manual

What Is in This Manual

Describes the concept of fault management

Chapter 2, Processing Error Alarm

Describes processing error alarms with respect to alarm

Chapter 3, QoS Alarm

Describes QoS alarms with respect to alarm information,

Chapter 4, Environment Alarm

Describes environment alarms with respect to alarm

Chapter 5, Equipment Alarm

Describes equipment alarms with respect to alarm

Chapter 6, Communication Alarm

Describes communication alarms with respect to alarm

Describes notification with respect to alarm information,

ZTE Proprietary and Confidential

This page intentionally left blank.

ZTE Proprietary and Confidential

Alarm/Notification Information Structure

Critical alarm causes system breakdown and service interruption. It requires

ZTE Proprietary and Confidential

ZXSDR UniRAN Alarm Handling

Major alarm significantly affects system operation or weakens network service

Minor alarm affects system operation and network service capability in a

Alarm severity can be modified in NetNumen U31 if necessary.

There is only one severity level for notification: Notification.

Equipment alarm: related with device hardware.

Processing error alarm:

related with software or operation fault (ITU-T

QoS alarm: related with quality of service.

ZTE Proprietary and Confidential

Pay attention to the

ZTE Proprietary and Confidential

ZXSDR UniRAN Alarm Handling