ZXSDR BS8800 U240 Indoor UMTS Macro Node B Alarm and Notification Handling Reference.pd

ZXSDR BS8800 U240Indoor UMTS Macro Node B

Alarm and Notifica-tion Handling Reference

Version V4.00.200f

ZTE CORPORATIONZTE Plaza, Keji Road South,Hi-Tech Industrial Park,Nanshan District, Shenzhen,P. R. China518057Tel: (86) 755 26771900Fax: (86) 755 26770801URL: http://ensupport.zte.com.cnE-mail: [email protected]

LEGAL INFORMATION

Copyright © 2006 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution ofthis document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPO-RATION 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 CORPORATIONor of their respective owners.

This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions are dis-claimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-in-fringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on theinformation contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subjectmatter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee,the user of this document shall not acquire any license to the subject matter herein.

ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.

Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision History

Revision No. Revision Date Revision Reason

R1.0 20090812 First Edition

Serial Number: sjzl20094680

Contents

Preface............................................................... i

Overview...........................................................1Overview of Fault Management......................................... 1

Fault View ..................................................................... 1

Alarm ....................................................................... 1

Notification ................................................................ 2

Alarm Information Struct................................................. 2

Notification Information Struct ......................................... 3

Equipment Alarm...............................................5198084037 TMB downlink bypass alarm ............................ 7

198084038 TMB uplink bypass alarm ................................ 9

198084039 TMA channel current input is interrupted........... 9

198084040 TMA channel input is over current ..................10

198084041 TMA channel input is over current

seriously...............................................................11

198084042 TMA channel input is under current. ................12

198084043 ATMA bypass alarm.......................................12

198084044 ATMA LNA alarm...........................................13

198084059 Downlink digital power greatly exceeds rated

power. ................................................................14

198084149 ATMA hardware fault ....................................14

198084150ATMA software fault .......................................14

198084199 Receiving antenna is imbalance ......................15

198084242 Dsp watchdog overflow..................................15

198084267 Clock minor alarm ........................................16

198084304 Board doesn’t support such configuration .........17

198084318 Failure alarm while raising the voltage of

adjustable power...................................................17

198084337 Type of base station is wrongly configured .........18

198084034 PPP Link Broken............................................18

198084035 PPP Link Unusable.........................................19

198084260 HDLC link has CRC alarm ...............................20

198084290 ETH port mode is unmatched with peer

end .....................................................................20

198084045 Antenna VSWR alarm ....................................21

198084046 Antenna over VSWR alarm .............................21

198084048 Calibration file on TRx board is abnormal .........22

198084056 Downlink digital IF pre-distortion alarm ...........23

198084058 Downlink digital power exceeds rated power

slightly.................................................................24

198084078 Surge protection device has a fault alarm .........24

198084085 Main power supply has a fault alarm................25

198084086 External device fault connected via dry

contact.................................................................25

198084087 Surge protection device in cabinet has a fault

alarm...................................................................26

198084311 Hardware alarm............................................26

198084293 RU board has slight high temperature..............27

198084294 PA slight over-temperature alarm....................27

198084295 DL IQ channel checking block alarm ................28

198084296 60ms tag lost alarm ......................................29

198084297 The configured operating frequency is out of

range...................................................................29

198084298 Test source file is abnormal ............................30

198084299 RRU02 PLL unlock alarm ................................30

198084300 Dry contact status alarm................................30

198084000 Failed to run FPGA software............................31

198084001 Failed to run DSP software .............................31

198084003 Clock module fault ........................................32

198084012 Board hardware fault.....................................32

198084013 Loss of Signal at Ir interface...........................33

198084060 RF board PLL alarm.......................................34

198084062 Transmission RF channel fault.........................34

198084063 Receiving RF channel fault .............................35

198084064 LNA alarm....................................................35

198084065 Improper power............................................35

198084066 The loading of DSP software failed ..................36

198084067 DSP run error...............................................36

198084073 Temperature sensor abnormity alarm ..............37

198084074 Temperature sensor not on-duty alarm ............37

198084075 Fan alarm ....................................................37

198084076 Heat exchanger alarm ...................................38

198084098 Battery Fault ................................................38

198084100 Remote output power improper voltage

alarm...................................................................39

198084132 PPP Link Configer is unmatched with peer

end .....................................................................39

198084133 PPP Failed to configure PPP link group..............40

198084200 Main input power over-voltage alarm...............41

198084201 Main input power under-voltage alarm.............41

198084202 Main input power powered-down alarm............42

198084231 RRU clock frequency drift ...............................42

198084232 Digital power improper ..................................43

198084235 Cpri signal of port 0 lost ................................43

198084236 Ir link FIFO improper.....................................44

198084237 RRU RTWP improper......................................45

198084257 UL IQ improper.............................................46

198084262 TDM CRC alarm ............................................46

198084263 RRU LOS alarm.............................................47

198084264 RRU LOF Alarm.............................................47

198084265 RRU powered-down alarm..............................48

198084266 Clock has a critical alarm ...............................48

198084272 Lightning arrester alarm at indoor lightning

protection box.......................................................50

198084273 Circuit breaker alarm at indoor lightning

protection box.......................................................51

198084274 Outdoor lightning protection box alarm ............51

198084275 Failed to download software ...........................52

198084276 Downlink DAC PLL unlock...............................52

198084286 PWR monitoring unit alarm ............................53

198084287 AC power-cut alarm ......................................53

198084288 Battery in low-voltage alarm ..........................54

198084289 Rectifier alarm..............................................54

198084301 Transport clock reference source is fault...........54

198084302 DSP AIF is improper ......................................55

198084306 Improper DPD running status .........................55

198084307 MP over-current alarm...................................56

198084308 PP over-current alarm ...................................56

198084310 The reported power has a CRC error................57

198084317 Self-defined dry contact alarm........................57

198084322 Backplane board has a clock alarm..................58

198084323 Intra-board clock alarm .................................58

198084324 Antenna data link performance alarm ..............59

198084325 Antenna data link error alarm.........................59

198084335 RRU02 PA over-high temperature alarm...........60

198084088 Remote input power over-voltage alarm...........60

198084089 Remote input power under-voltage alarm .........61

198084090 Remote input power powered-down

alarm...................................................................61

198084091 Remote output power over-current alarm .........62

198084092 Remote power output under-voltage

alarm...................................................................62

198084093 Remote antenna over VSWR alarm..................63

198084094 Remote antenna VSWR..................................64

198084136 Uplink channel runs abnormally ......................65

198084137 Downlink channel runs abnormally ..................65

198084139 PA over power alarm .....................................65

198084141 PA over temperature alarm ............................66

198084145 PA communication fault .................................66

198084146 RET motor fault ............................................67

198084147 RET hardware fault .......................................67

198084148 RET software fault.........................................68

198084151 ATMA communication link is interrupted...........68

198084152 RET communication link is interrupted .............69

198084153 ACOM hardware fault ....................................69

198084154 ACOM software fault......................................70

198084156 ACOM communication link is interrupted ..........70

198084208 AISG EEPROM error.......................................71

198084209 AISG flash erase error ...................................71

198084210 AISG flash error ...........................................71

198084211 AISG other hardware error.............................72

198084215 RET motor fault ............................................72

198084212 AISG other software error ..............................72

198084213 AISG RAM error ............................................73

198084214 AISG UART error...........................................73

198084216 RET motor can’t adjust ..................................73

198084217 RET motor don’t responed the adjusting

command ............................................................74

198084218 RET don’t calibrated ......................................74

198084219 RET data don’t scaled ....................................75

198084220 RET position lost...........................................75

198084221 ATMA minor alarm ........................................76

198084222 ATMA major alarm ........................................76

198084223 ACOM minor alarm........................................76

198084224 ACOM major alarm........................................77

198084234 PA Run Failed alarm ......................................77

198084255 E1T1 sliding code..........................................77

198084304 Board doesn’t support such configuration .........78

198084238 Frame SeqNo Failed ......................................79

198084240 AIF Interface Failed.......................................80

198084244 Software Load Abnormal................................80

198084239 HardWare TimeSlot Terminate Failed ...............81

198084241 Out RAM Read/Write Failed.............................81

198084243 Uplink Trx 60ms Abnormal .............................82

Communication Alarm .....................................83198084015 STM-1 optical signals are lost. ........................84

198084016 STM-1 loses frame synchronization .................85

198084017 STM-1 MSAIS (MS Alarm Indicator

Signal) .................................................................86

198084018 STM-1 AU4 loss of pointer..............................87

198084245 Physical param not consistent with radio

param..................................................................88

198084246 Radio param error.........................................88

198084247 Link3 of BUC software not response ................89

198084248 DSP software of BP board has no

response ..............................................................89

198084249 DBB parameter of BP board response

error....................................................................90

198084036 SCTP stream number mismatch ......................90

198084291 Configuration parameter of O&M Channel is

wrong ..................................................................91

198084312 E1/T1 link configuration is failed .....................91

198084313 Qos bandwidth configuration is failed...............92

198084314 IP clock configuration is failed.........................92

198084326 Physical param not consistant with radio

param..................................................................93

198084327 Radio param error.........................................93

198084282 Lost of frame number at optical port................93

198084283 Lost of frame rate and frame number ..............94

198084019 E1/T1 LOS (Loss Of Signal) alarm ...................94

198084020 E1/T1 link loss of frame alarm ........................95

198084021 E1/T1 loss of cell delineation alarm .................96

198084022 E1/T1 link loss of IMA frame alarm..................96

198084023 E1/T1 IMA group is not operational .................97

198084024 E1/T1 remote receiving fault ..........................98

198084025 E1/T1 link self-loop .......................................98

198084026 PVC fault .....................................................99

198084028 SSCOP signaling link is broken...................... 100

198084029 SSCOP transmission buffer is overflow ........... 101

198084030 SCTP associate association is inter-

rupted................................................................ 101

198084031 SCTP associate stream buffer is

congestion.......................................................... 102

198084032 SCTP associate network is congestion............ 103

198084230 Ir link LCV(line code violation) alarm ............. 103

198084271 Ethernet light and electricity lose .................. 104

198084305 Heat exchanger’s communication data lost

alarm................................................................. 104

Processing Alarm ..........................................107198084135 Database load fail ....................................... 108

198084250 IQ Config Failed .......................................... 109

198084251 IPTB Setup Link Failed ................................. 109

198084252 Require Radio Param timeout for times .......... 110

198084253 Control face Emac Interface Error ................. 110

198084254 User face Emac Interface Error ..................... 111

198084280 Write MDB and DBS failure........................... 111

198084281 Failed to allocate physical logic ..................... 112

198084292 AD9516 unlock alarm .................................. 112

198084319 License alarm due to authority limit............... 113

198084320 License alarm due to not being activated ......... 113

198084321 Physical parameters synchronization is

failure ................................................................ 114

198084268 IQ delay compensation value exceeds

limitation............................................................ 114

198084107 Board parameter synchronization

abnormity........................................................... 115

198084108 Board wrong insertion alarm ........................ 115

198084109 SNTP time adjustment failure alarm .............. 116

198084110 Running software version synchronization

failure ................................................................ 116

198084111 Slave software version synchronization

failure ................................................................ 117

198084112 Special software version synchronization

failure ................................................................ 117

198084113 Running Software version fault ..................... 118

198084114 Slave Software version fault ......................... 118

198084115 Special Software version fault....................... 119

198084116 Insufficient DOM space alarm ....................... 119

198084118 Failed to set gain ........................................ 119

198084119 Board configuration parameter error.............. 120

198084122 CPU over loading ........................................ 120

198084123 Board communication link is interrupted ......... 121

198084124 Database saved on master/slave board is

failed to be kept synchronous................................ 121

198084125 Database save failure .................................. 122

198084206 Software file is not identical with the DataBase

record................................................................ 123

198084207 Firmware file is not identical with the

DataBase record.................................................. 123

198084315 Board reboots alarm.................................... 124

198084316 Firmware version is failed to be

synchronized....................................................... 124

198084328 IQ Config Failed .......................................... 124

198084329 IPTB Setup Link Failed ................................. 125

198084330 Require Radio Param timeout for times .......... 125

198084331 Fail to write platform database...................... 126

198084332 Failed to allocate physical logic ..................... 126

198084333 Physical parameter synchronization

failure ................................................................ 127

198084334 Peripheral board IQ configuration failure ......... 127

198084004 Clock reference source is lost ....................... 128

198084006 Clock reference source is degraded ............... 130

198084101 Failed to configure TC port ........................... 131

198084102 Failed to configure PVC ................................ 132

198084103 Failed to configure FE port............................ 133

198084104 Failed to configure OMCB channel ................. 133

198084105 Failed to configure SCTP associate................. 134

198084106 Failed to configure TSI................................. 134

198084117 Monitor alarm of application software ............ 135

198084126 Failed to configure STM-1............................. 135

198084128 Failed to configure channelized STM-1 ........... 136

198084256 GPS receiver alarm ..................................... 136

198084129 Board startup notify .................................... 137

198084227 Failed to configure IMA group ....................... 137

198084228 IpVlan Configer Failed ................................. 138

198084233 Digital PA over power alarm ......................... 138

198084259 UL buffer is used up .................................... 139

198084284 PM under-voltage alarm............................... 139

198084285 PM over-voltage alarm................................. 140

198084130 Dry contact configuration Failed .................... 140

198084131 Node B reboot notification............................ 140

198084134 Master/slave changeover alarm .................... 141

Environment Alarm .......................................143198084068 Environmental temperature is high................ 143

198084069 Environmental temperature is low ................. 144

198084070 Device temperature is high .......................... 144

198084071 Device temperature is low............................ 145

198084072 Whole set temperature rising alarm............... 145

198084077 Gate safety alarm ....................................... 145

198084096 Flooded Fault ............................................. 146

198084097 Smog Fault ................................................ 146

QoS Alarm .....................................................149198084303 Clock has significant alarm........................... 149

Notification ...................................................151198084183 SSCOP fault ............................................... 151

198084184 ALCAP link fault .......................................... 152

198084185 SCTP association fault ................................. 153

198084186 Error PATHID alarm is received. .................... 153

198084188 PPP Link Recycle ......................................... 154

198084189 PAP authorize failed .................................... 154

198084190 CHAP authorize failed .................................. 155

198084191 CHAP oppose authorize failed ....................... 155

198084192 Alarm storm notification .............................. 155

198084258 Intra-board network port error ..................... 156

198084269 MAC address conflict ................................... 156

198084155 ACOM address conflict ................................. 157

198084180 E1/T1 HDB3 coding violation alarm ............... 157

198084193 Cell deletion notification............................... 158

198084196 ATMA device address conflict ........................ 158

198084197 RET device address conflict .......................... 159

198084261 The received frame number is not

continuous.......................................................... 159

198084168 Local benchmark clock is unlocked ................ 160

198084170 STM-1 B1 error code alarm .......................... 161


198084172 STM-1 B2 FEBEI (Far End Block) ................... 162


198084174 STM-1 B3 FEBEI (Far End Block Error

Indicator) alarm .................................................. 164

198084175 STM-1 MSRDI (MS Remote Defect Indicator)

alarm................................................................. 165

198084176 STM-1 HPRDI (High-order Path Remote Defect

Indicator) alarm .................................................. 166

198084177 STM-1 HPPLM (High-order Path Payload Level

Mismatch) .......................................................... 167

198084178 STM-1 loss of cell delineation ....................... 168

198084179 STM-1 Rx cell CRC error .............................. 168

198084270 IP address conflict....................................... 169

198084338 Ir link has violated 8B10B codes ................... 170

Preface

Purpose NetNumen M31™ mobile network element management system isthe intermediate system between the bottom level network man-agement system and higher level operation support layer. Thissystem provides a higher view point for the network management,and offer a centralized management to the various specialized net-works. By interfacing with various professional network manage-ment system, this system provides a new method of centralizedmanagement over the networks topology, alarming and perfor-mance which replaces the old distributed individual managementof specific networks. Also an unique interface to higher level ap-plications is provided.

NetNumen M31™ is completely based on object-oriented technol-ogy and advanced J2EE platform. It supports an unified access ofthe various network element equipments supplied by ZTE and pro-vides centralized management to the networks alarming, networkperformance, and cross-NE performance data analysis.

This manual introduces the alarms and notifications that mightoccur during the installation, operation and maintenance of ZTEZXSDR BS8800 U240 product. Alarm/Notification code and de-scription displayed by NetNumen M31™, probable cause for thealarm/notification, and the corresponding handling suggestion arecovered in this manual.

What Is in ThisManual

This manual contains the following chapters:

Chapter Summary

Chapter 1, Overview of FaultManagement

Introduces the concept of faultmanagement, as well as thedefinition, type, level classificationof alarm and notification.

Chapter 2, Equipment Alarm Introduces ZXSDR BS8800 U240equipment alarms with respect toalarm property, probable cause,system impact, and handlingsuggestion.

Chapter 3, Communication Alarm Introduces ZXSDR BS8800U240 communication alarmswith respect to alarm property,probable cause, system impact,and handling suggestion.

Chapter 4, Processing Alarm Introduces ZXSDR BS8800 U240processing alarms with respect toalarm property, probable cause,system impact, and handlingsuggestion.

Confidential and Proprietary Information of ZTE CORPORATION i

ZXSDR BS8800 U240 Alarm and Notification Handling Reference

Chapter Summary

Chapter 5, Environment Alarm Introduces ZXSDR BS8800 U240environment alarms with respectto alarm property, probable cause,system impact, and handlingsuggestion.

Chapter 6, QoS Alarm Introduces ZXSDR BS8800 U240QoS alarms with respect to alarmproperty, probable cause, systemimpact, and handling suggestion.

Chapter 7, Notification Introduces ZXSDR BS8800 U240notifications with respect tonotification property, probablecause, system impact, andhandling suggestion.

Intended Reader � Base Station Deploy Engineer

� Maintenance Engineer

� Network Management Engineer.

ii Confidential and Proprietary Information of ZTE CORPORATION

C h a p t e r 1

Overview

Table of ContentsOverview of Fault Management............................................. 1Fault View ......................................................................... 1Alarm Information Struct..................................................... 2Notification Information Struct ............................................. 3

Overview of FaultManagementFault management is responsible for collecting information of fail-ures and events that occur during system operation or service pro-cessing.

The information, in the form of alarm or notification, is stored indatabase or displayed on realtime basis via a user-oriented faultmonitoring platform. Means such as visual-interface monitor orhistory information query can be used to view current or histor-ical system operation and service processing status. Fault man-agement enables maintenance personnel to troubleshoot and takepreventive measures to remove potential fault and restore systemand services as early as possible.

Fault ViewFault is displayed in the form of alarm or notification.

Alarm

The fault that persists during system operation and affects systemreliability and normal services is referred to as an alarm. Alarmusually lasts until fault removal.

Due to its possible impact on normal system operation, alarm re-quires timely troubleshooting in which alarm cause is identified,and the fault is located and handled.

Confidential and Proprietary Information of ZTE CORPORATION 1


Notification

Notification refers to the non-repeated/instantaneous fault orevent that occurs during system operation. Examples includeboard reset, signaling overload, etc.

Notification is mostly caused by sudden environment changeor other accidental factors. No special handling is required forthe notification, which can be automatically removed by thesystem. Only the notification that occurs persistently requirestroubleshooting.

Alarm Information StructAlarm Property 1. Alarm Code

Alarm Code is the identifier which differentiates alarms.

Alarm Code is defined by a 32-bit field indicating the specificcode value.

2. Description

Alarm description reflects such content as fault cause and faultphenomenon in a simple and straightforward way.

3. Severity

There are four alarm levels, which are indicated in descendingorder of severity as Critical, Major, Minor, and Warning.

� Critical alarm causes system breakdown and service inter-ruption. It requires immediate troubleshooting.

� Major alarm significantly affects system operation or weak-ens network service capability. It requires troubleshootingas soon as possible.

� Minor alarm affects system operation and network servicecapability in a non-significant way. It requires timely trou-bleshooting so as to avoid severity escalation.

� Warning poses a potential hazard to system operation andnetwork service capability. It requires troubleshooting atan appropriate time so as to avoid severity escalation.

The degree of impact as described in the definition of alarmseverity refers to the impact of a single index, such as reliabilityand security. Once the impact on any of the index reachesthe specified threshold, the severity level of the alarm can beroughly determined. If an alarm has an impact on multipleindices, alarm severity should be escalated accordingly.

2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Overview

Note:

� Alarm severity can be modified in NetNumenM31 NMS (net-work management system) if necessary.

� Generally speaking, the default alarm severity is reason-ably set. Users should think twice before making any mod-ification.

In addition, the severity of a few alarms is undefined. It is upto users to define the severity of such alarms.

4. Alarm Type

Alarm is classified into six types according to alarm trigger con-dition and its system impact.

� Equipment alarm: related with device hardware.

� Communication alarm: related with information trans-mission (ITU-T Recommendation X.733).

� Processing alarm: related with software or process fault(ITU-T Recommendation X.733).

� Environment alarm: related with the environment wherethe equipment is located (ITU-T Recommendation X.733).

� QoS alarm: related with degradation of service quality(ITU-T Recommendation X.733).

� OMS alarm: related with the NMS.

Probable Cause Probable alarm causes are enumerated to help users troubleshoot,find preventive measures, and restore the system to normal statein a timely manner.

System Impact System impact refers to the impact that the alarm incurs on sys-tem or services.

HandlingSuggestion

Troubleshooting measures and suggestions are provided. Pay at-tention to the following tips when handling alarms.

� After recording the fault phenomenon, O&M personnel mayhandle the fault step by step as described in the Handling Sug-gestion Section of this manual. If the fault is removed (alarmrestored) 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 assoon as possible.

Notification InformationStruct

NotificationProperty

1. Notification Code

Notification code is the identifier to differentiate notifications.



Notification code is defined by a 32-bit field indicating the spe-cific code value.

2. Description

Notification description reflects such content as fault cause andfault phenomenon in a simple and straightforward way.

3. Importance

There are two levels of notification importance: Importantand Ordinary.

4. Notification Type

No notification type exists.

Probable Cause Probable notification causes are enumerated to help users trou-bleshoot, find preventive measures, and restore the system tonormal state in a timely manner.

System Impact System impact refers to the impact that the notification incurs onsystem or services.

HandlingSuggestion

Troubleshooting measures and suggestions are provided.

Pay attention to the following tips when handling notifications.

� After recording the fault phenomenon, O&M personnel mayhandle the fault step by step as described in the Handling Sug-gestion Section of this manual. If the fault is removed at anyhandling step, terminate the handling process. If the fault isnot removed, go ahead to the next handling step.

� If the fault cannot be removed, or the system normal operationcannot be restored, contact the local ZTE office as soon aspossible.


C h a p t e r 2

Equipment Alarm

Table of Contents198084037 TMB downlink bypass alarm ................................ 7198084038 TMB uplink bypass alarm .................................... 9198084039 TMA channel current input is interrupted............... 9198084040 TMA channel input is over current ......................10198084041 TMA channel input is over current seriously. .........11198084042 TMA channel input is under current. ....................12198084043 ATMA bypass alarm...........................................12198084044 ATMA LNA alarm...............................................13198084059 Downlink digital power greatly exceeds ratedpower. ............................................................................14198084149 ATMA hardware fault ........................................14198084150ATMA software fault ...........................................14198084199 Receiving antenna is imbalance ..........................15198084242 Dsp watchdog overflow......................................15198084267 Clock minor alarm ............................................16198084304 Board doesn’t support such configuration .............17198084318 Failure alarm while raising the voltage of ad-justable power ..................................................................17198084337 Type of base station is wrongly configured............18198084034 PPP Link Broken................................................18198084035 PPP Link Unusable.............................................19198084260 HDLC link has CRC alarm ...................................20198084290 ETH port mode is unmatched with peer end..........20198084045 Antenna VSWR alarm ........................................21198084046 Antenna over VSWR alarm .................................21198084048 Calibration file on TRx board is abnormal .............22198084056 Downlink digital IF pre-distortion alarm ...............23198084058 Downlink digital power exceeds rated powerslightly.............................................................................24198084078 Surge protection device has a fault alarm.............24198084085 Main power supply has a fault alarm....................25198084086 External device fault connected via dry con-tact .................................................................................25198084087 Surge protection device in cabinet has a faultalarm...............................................................................26198084311 Hardware alarm................................................26198084293 RU board has slight high temperature..................27198084294 PA slight over-temperature alarm........................27198084295 DL IQ channel checking block alarm ....................28198084296 60ms tag lost alarm ..........................................29198084297 The configured operating frequency is out ofrange...............................................................................29198084298 Test source file is abnormal ................................30198084299 RRU02 PLL unlock alarm ....................................30198084300 Dry contact status alarm....................................30198084000 Failed to run FPGA software................................31



198084001 Failed to run DSP software .................................31198084003 Clock module fault ............................................32198084012 Board hardware fault.........................................32198084013 Loss of Signal at Ir interface...............................33198084060 RF board PLL alarm...........................................34198084062 Transmission RF channel fault.............................34198084063 Receiving RF channel fault .................................35198084064 LNA alarm .......................................................35198084065 Improper power................................................35198084066 The loading of DSP software failed ......................36198084067 DSP run error...................................................36198084073 Temperature sensor abnormity alarm ..................37198084074 Temperature sensor not on-duty alarm ................37198084075 Fan alarm ........................................................37198084076 Heat exchanger alarm .......................................38198084098 Battery Fault ....................................................38198084100 Remote output power improper voltagealarm...............................................................................39198084132 PPP Link Configer is unmatched with peerend .................................................................................39198084133 PPP Failed to configure PPP link group..................40198084200 Main input power over-voltage alarm...................41198084201 Main input power under-voltage alarm.................41198084202 Main input power powered-down alarm................42198084231 RRU clock frequency drift ...................................42198084232 Digital power improper ......................................43198084235 Cpri signal of port 0 lost ....................................43198084236 Ir link FIFO improper.........................................44198084237 RRU RTWP improper..........................................45198084257 UL IQ improper.................................................46198084262 TDM CRC alarm ................................................46198084263 RRU LOS alarm.................................................47198084264 RRU LOF Alarm.................................................47198084265 RRU powered-down alarm..................................48198084266 Clock has a critical alarm ...................................48198084272 Lightning arrester alarm at indoor lightning pro-tection box .......................................................................50198084273 Circuit breaker alarm at indoor lightning protec-tion box ...........................................................................51198084274 Outdoor lightning protection box alarm................51198084275 Failed to download software ...............................52198084276 Downlink DAC PLL unlock...................................52198084286 PWR monitoring unit alarm ................................53198084287 AC power-cut alarm ..........................................53198084288 Battery in low-voltage alarm ..............................54198084289 Rectifier alarm..................................................54198084301 Transport clock reference source is fault...............54198084302 DSP AIF is improper ..........................................55198084306 Improper DPD running status .............................55198084307 MP over-current alarm.......................................56198084308 PP over-current alarm .......................................56198084310 The reported power has a CRC error....................57198084317 Self-defined dry contact alarm............................57198084322 Backplane board has a clock alarm......................58198084323 Intra-board clock alarm .....................................58198084324 Antenna data link performance alarm ..................59198084325 Antenna data link error alarm.............................59198084335 RRU02 PA over-high temperature alarm...............60198084088 Remote input power over-voltage alarm...............60198084089 Remote input power under-voltage alarm.............61


Chapter 2 Equipment Alarm

198084090 Remote input power powered-down alarm............61198084091 Remote output power over-current alarm.............62198084092 Remote power output under-voltage alarm...........62198084093 Remote antenna over VSWR alarm......................63198084094 Remote antenna VSWR......................................64198084136 Uplink channel runs abnormally ..........................65198084137 Downlink channel runs abnormally ......................65198084139 PA over power alarm .........................................65198084141 PA over temperature alarm ................................66198084145 PA communication fault .....................................66198084146 RET motor fault ................................................67198084147 RET hardware fault ...........................................67198084148 RET software fault.............................................68198084151 ATMA communication link is interrupted...............68198084152 RET communication link is interrupted .................69198084153 ACOM hardware fault ........................................69198084154 ACOM software fault..........................................70198084156 ACOM communication link is interrupted ..............70198084208 AISG EEPROM error ..........................................71198084209 AISG flash erase error .......................................71198084210 AISG flash error ...............................................71198084211 AISG other hardware error.................................72198084215 RET motor fault ................................................72198084212 AISG other software error ..................................72198084213 AISG RAM error ................................................73198084214 AISG UART error...............................................73198084216 RET motor can’t adjust ......................................73198084217 RET motor don’t responed the adjusting com-mand ..............................................................................74198084218 RET don’t calibrated ..........................................74198084219 RET data don’t scaled........................................75198084220 RET position lost...............................................75198084221 ATMA minor alarm ............................................76198084222 ATMA major alarm ............................................76198084223 ACOM minor alarm............................................76198084224 ACOM major alarm............................................77198084234 PA Run Failed alarm ..........................................77198084255 E1T1 sliding code..............................................77198084304 Board doesn’t support such configuration .............78198084238 Frame SeqNo Failed ..........................................79198084240 AIF Interface Failed...........................................80198084244 Software Load Abnormal....................................80198084239 HardWare TimeSlot Terminate Failed ...................81198084241 Out RAM Read/Write Failed ................................81198084243 Uplink Trx 60ms Abnormal .................................82

198084037 TMB downlinkbypass alarm

Alarm Property � Alarm Code: 198084037

� Description: TMB downlink bypass alarm

� Severity: Minor



� Alarm Type: Equipment Alarm

Probable Cause 1. Primary channel over-power alarm:

this alarm is given when the detected maximum output powerexceeds 47.3dBm ± 0.5dB. In this case, Tx channel works inbypass state.

2. Primary channel over-VSWR alarm:

when the value of VSWR exceeds 1.8, only an alarm is given,auto-protection shut-down function is not required. When thevalue of VSWR exceeds 2.8 and output power is greater than35dBm, an alarm is given; meanwhile, auto-protection shut-down function is required. In this case, Tx channel works inbypass state.

3. Primary channel over-temperature alarm:

TMB has its own temperature detection function. When itsinternal maximum working temperature exceeds 95 degreesCelsius ± 5 degrees Celsius, this alarm is given. In this, Txchannel works in bypass state.

4. Primary channel DC over-current alarm:

when the DC current exceeds 150% of normal working current,this alarm is given. In this case, Tx channel works in bypassstate.

5. Primary channel device fault alarm:

for example, working voltage is out of -40VDC~-57VDC range,PA is broken. In this case, Tx channel works in bypass state.

6. TMB gate alarm:

when TMB gate is opened, alarm indicator is required at PAUpanel. The alarm information may be viewed through RS485.When TMB gate is closed, this alarm disappears.

7. PAU and TMB communication abnormity alarm:

PAU communicates with TMB through RS485. This type ofalarm includes: software download is abnormal, RF channelbetween PAU and TMB is not connected, communication is in-terrupted abnormally, etc. When this happens, an alarm indi-cator must display this status at PAU panel. The alarm infor-mation may be viewed through RS485.

System Impact 1. Board Status: Board operation is normal.2. Service Impact: Cell downlink coverage extent is affected.



HandlingSuggestion

TMB is powered down and powered on.Check if the alarm is recov-ered.

198084038 TMB uplinkbypass alarm


� Description: TMB uplink bypass alarm

� Severity: Minor


Probable Cause Receiving channel LNA is abnormal.

System Impact 1. Board Status: Board operation is normal.2. Service Impact: Cell uplink coverage extent is affected.

HandlingSuggestion

TMB is powered down and powered on.Check if the alarm is recov-ered.

198084039 TMA channelcurrent input is interrupted.


� Description: TMA channel current input is interrupted.

� Severity: Major


Probable Cause 1. The TMA associated power cable is not well connected.2. The configured threshold is different from real TMA threshold.3. The TMA associated power cable is in the state of open circuit.4. TAC fault.5. TMA fault.

System Impact 1. Board Status: Board operation is normal.2. Service Impact: The TMA does not work normally and cell cov-

erage extent is affected.

HandlingSuggestion

1. Check if the alarm threshold of TMA power supply is configuredcorrectly.

Check if the configured minimum current is consistent with realTMA threshold (Generally speaking, it is assumed as fault whenTMA power current is less than 40mA). If the result is nega-tive, change the alarm threshold of TMA power supply; Changethe configured minimum threshold of power current so that it



is consistent with real TAM threshold; Check if the alarm is re-covered.

2. Check if power cable of TMA channel is well connected

Check if the associated power cable of TMA channel is wellconnected. If the result is negative, reconnect the cable; Checkif the alarm is recovered.

3. Check if the state between TMA power cable and ground isopen circuit or high resistance.

Use multi-meter to detect if the state between TMA power cableand ground is open circuit or high resistance. If the result ispositive, replace this cable; Check if the alarm is recovered.

4. Replace TAC.

Replace TAC; Wait for 2 minutes; Check if the alarm is recov-ered.

5. Replace TMA.

Replace TMA; Wait for 2 minutes; Check if the alarm is recov-ered.

198084040 TMA channelinput is over current


� Description: TMA channel input is over current

� Severity: Major


Probable Cause 1. The configured threshold is not consistent with real TMAthreshold.

2. The connection between TMA power cable and ground is in thestate of short circuit or low resistance.

3. TAC fault.4. TMA fault.

System Impact 1. Board Status: Board operation is normal.2. Service Impact: Cell coverage is slightly affected.

HandlingSuggestion


Check if the configured minimum current is consistent with realTMA threshold (General speaking, it is assumed as over currentwhen the TMA power current is greater than 135mA and lessthan 200mA). If negative, change the alarm threshold of TMApower supply; Change the configured upper limit of workingcurrent so that it is consistent with real TMA threshold; Checkif the alarm is recovered.

2. Check if the state between TMA power cable and the ground isshort circuit or low resistance.



Use multi-meter to check if the state between TMA power cableand ground is short circuit or low resistance. If positive, replacethe cable; Check if the alarm is recovered.

3. Replace TAC.


4. Replace TMA.


198084041 TMA channelinput is over currentseriously.


� Description: TMA channel input is over current seriously.

� Severity: Major


Probable Cause 1. The configured threshold is inconsistent with real TMA thresh-old.

2. The connection between TMA cable and ground is in the stateof short circuit.

3. TAC fault.4. TMA fault.

System Impact 1. Board Status: Board operation is normal.2. Service Impact: Cell coverage is greatly affected.

HandlingSuggestion

1. Check if TMA power current is normal.

Let TAC not provide power to ATMA; use multi-meter to checkif TAC output voltage is normal. If positive, skip to "2 Check ifthe state between TMA power cable and ground is short circuitor low resistance". If negative, skip to "3 Replace TAC".

2. Check if the state between TMA power cable and ground isshort circuit or low resistance.

Use multi-meter to check if the state between TMA power cableand ground is short circuit or low resistance. If positive, replacethis cable; Check if the alarm is recovered.

3. Replace TAC.


4. Replace TMA.




198084042 TMA channelinput is under current.


� Description: TMA channel input is under current.

� Severity: Major


Probable Cause 1. The configured threshold is incorrect.2. The TMA associated power cable is in the state of open circuit

or high resistance.3. TAC fault.4. TMA fault.

System Impact 1. Board Status: Board operation is normal.2. Service Impact: Cell coverage extent is slightly affected.

HandlingSuggestion


Check if the configured lower limit of working current is con-sistent (Generally speaking, the default threshold of TMA un-der-current alarm is 70~80mA). If negative, change the alarmthreshold of TMA power supply; Change the configured lowerlimit of TMA working current; check if the alarm is recovered.

2. Check if the state between TMA power cable and ground isopen circuit or high resistance.

Use multi-meter to check if the state between TMA power ca-ble and ground is open circuit or high resistance. If positive,replace this cable; Check if the alarm is recovered.

3. Replace TAC.


4. Replace TMA.


198084043 ATMA bypassalarm


� Description: ATMA bypass alarm

� Severity: Major


Probable Cause 1. ATMA is seriously over-current or without any gain.



2. Power supply part of TAC is broken.

System Impact 1. Board Status: Board operation is normal.2. Service Impact: Gain is 0 dB. Power is off, in bypass status.

Cell coverage extent is greatly affected.

HandlingSuggestion

1. Reset TAC.

Reset TAC through O&M console; Wait for 2 minutes; Check ifthe alarm is recovered.

2. Check if ATMA power supply is normal.

Let TAC not provide power to ATMA; use multi-meter to check ifTAC output voltage is normal. If positive, indicating ATMA hasa problem, skip to "3 Replace ATMA". If negative, indicatingTAC has a problem, skip to "4 Replace TAC".

3. Replace ATMA.

Replace ATMA; Check if the alarm is recovered.

4. Replace TAC.

Replace TAC; Check if the alarm is recovered.

198084044 ATMA LNAalarm


� Description: ATMA LNA alarm

� Severity: Warning


Probable Cause 1. ATMA is over current for a short time or its gain is reduced.2. The internal alarm detection circuit of ATMA LNA is broken,

which causes false alarm.

System Impact 1. Board Status: Board operation is normal.2. Service Impact: TMA gain decreases and system coverage ex-

tent is affected.

HandlingSuggestion

1. Reset TAC.

Reset TAC through O&M console; Wait for 2 minutes; Check ifthe alarm is recovered.

2. Check if ATMA power supply is normal.

Let TAC not provide power to ATMA; Use multi-meter to check ifTAC output voltage is normal. If positive, indicating ATMA hasa problem, skip to "3 Replace ATMA". If negative, indicatingTAC has a problem, skip to "4 Replace TAC".

3. Replace ATMA.

Replace ATMA; Check if the alarm is recovered.

4. Replace TAC.

Replace TAC; check if the alarm is recovered.



198084059 Downlink digitalpower greatly exceeds ratedpower.


� Description: Downlink digital power greatly exceeds ratedpower.

� Severity: Major


Probable Cause Input digital signal is wrong.

System Impact 1. Board Status: Board Operation is normal.2. Service Impact: RF output quality is affected.

HandlingSuggestion

When this alarm occurs, Please contact ZTE.

198084149 ATMA hardwarefault


� Description: ATMA hardware fault

� Severity: Major


Probable Cause Parameter error.

System Impact Service Impact: ATMA works abnormally, which might cause theperformance of corresponding cell to degrade.

HandlingSuggestion

1. Reset EMC. Wait for 2 minutes and check if the alarm is recov-ered.

2. Replace EMC. Wait for 2 minutes and check if the alarm is re-covered.

198084150ATMA softwarefault


� Description: ATMA software fault

� Severity: Major




Probable Cause Parameter error.

System Impact Service Impact: ATMA works abnormally, which might cause theperformance of corresponding cell to degrade.

HandlingSuggestion

1. Reset EMC. Wait for 2 minutes and check if the alarm is recov-ered.

2. Replace EMC. Wait for 2 minutes and check if the alarm is re-covered.

198084199 Receivingantenna is imbalance


� Description: Receiving antenna is imbalance

� Severity: Major


Probable Cause When the receive mode of cell antenna is diversity or multi-an-tenna receive, if there is configure wrong of receive antenna ornot well contacted in cell, will reported this alarm.

System Impact 1. Board Status: Board Operation is normal.2. Service Impact: Diversity reception gain decreases, affecting

system reception performance.

HandlingSuggestion

1. Check if the receive RF unit of local cell is configured rightlyin LMT. If negative, amend the configure of local cell RF unit;Check if the alarm is recovered.

2. Check if the Master and Slave antennas of associated cell con-tacted well. If negative, contact antenna anew; Check if thealarm is recovered.

3. Check if the diversity antenna of neighborhood sector con-tacted rightly. If positive, contact antenna anew; Check if thealarm is recovered.

4. Replace the antenna; Check if the alarm is recovered.

198084242 Dsp watchdogoverflow


� Description: Dsp watchdog overflow

� Severity: Critical




Probable Cause 1. The optical switching board does not work properly.2. The link is disconnected between baseband and RF.3. The RF board does not work properly.

System Impact 1. Board Status: Board operation is normal.2. Service Impact: The UBPG board software does not operate

properly and the services provided by this board are completelyinterrupted.

HandlingSuggestion

1. Check the local board fiber connection and make sure the con-nection is correct and secure.

2. Check whether the opposite RF board is in proper operation.3. Check whether the opposite optical switch board is in normal

operation.4. Reset the board.5. Reset the opposite RF board.6. Reset the opposite optical switch board.7. Replace the board.8. Reset the opposite RF board.9. Reset the opposite optical switch board.

198084267 Clock minoralarm


� Description: Clock minor alarm

� Severity: Minor


Probable Cause Clock reference source is unlocked.

System Impact 1. Board Status: Board operation is normal.2. Service Impact: operation of board software is abnormal. Per-

formance of the service on the board is degraded.

HandlingSuggestion

1. Check if the fault board has corresponding software versionfault alarm. If positive, according to suggestions on handlingsoftware version fault alarm, remove this alarm; Check if thealarm is recovered.

2. Reset board Reset the fault board and wait for 2 minutes;Check is the alarm is recovered.

3. Replace the fault board and wait for 2 minutes; Check if thealarm is recovered.



198084304 Board doesn’tsupport such configuration


� Description: Board doesn’t support such configuration.

� Severity: Minor

� Alarm Type: Equipment alarm

Probable Cause The CC board does not support this function.

System Impact It has no impact to the services.

HandlingSuggestion

1. Acquire the actual name of the CC board.

Method of acquiring: open Asset Management Report windowand run “Get the hardware Information of the Board ”Then theCCType item is the actual name of the CC board.

The relations between the actual name and the configurationsupported are as below:

i. CC0: E1 0 to 15 channels and embedded GPS supported;2MHz clock configuration not supported.

ii. CC1: E1 0 to 7 channels and embedded GPS supported;2MHz clock configuration not supported.

iii. CC2: E1 0 to 7 channels supported; embedded GPS notsupported; 2MHz clock configuration supported.

2. Replace the board with compatible boards or modify the con-figuration to meet the actual boards used.

198084318 Failure alarmwhile raising the voltage ofadjustable power


� Description: Failure alarm while raising the voltage of ad-justable power

� Severity: Major


Probable Cause Adjustable power module has a fault.

System Impact 1. Board Status: Work normally.2. Service Impact: If power voltage cannot be raised, the biggest

problem is cell coverage area is reduced. This may easily causeblind cell, or handover area may be changed.



HandlingSuggestion

Check the power module of RRU. If it is broken, replace the brokenpower module of RRU; Check if the alarm is recovered.

198084337 Type of basestation is wrongly configured


� Description: Type of base station is wrongly configured

� Severity: Major


Probable Cause The type of base station is wrong or FCE accessing type is wrong.

System Impact Service Impact: FCE runs abnormally so that fan speed cannot beadjusted. This may cause too high temperature of base stationand normal service may be affected.

HandlingSuggestion

1. Perform entire-table configuration according to the mappingrelation between type of base station and FCE.

2. Download suitable software specification package, whichis matched with type of base station. Then update boardsoftware.

198084034 PPP Link BrokenAlarm Property � Alarm Code: 198084034

� Description: PPP Link Broken

� Severity: Major


Probable Cause Iub interface PPP link is faulty.

System Impact The services on this PPP link are unavailable.

HandlingSuggestion

1. On NMS fault management interface (realtime monitor), checkif the following alarm occurs. If yes, refer to the correspondingalarm handling suggestion.

Related alarms:

� 198084019 E1/T1 LOS (Loss Of Signal) alarm

� 198084020 E1/T1 link loss of frame alarm

� 198084021 E1/T1 loss of cell delineation alarm

� 198084024 E1/T1 remote receiving fault

2. Check the jumper setting of SA/SE board. Ensure that thejumper of SA/SE board is properly configured in terms of E1cable type.



3. On Node B side, use physical cable to perform local Node Bself-loop. Check if the alarm can be restored on Node B side.If no, reset or replace board.

4. On RNC side, use physical cable to perform Node B E1/T1 self-loop. Check if the PPP alarm on Node B side can be restored. Ifno, transmission link must be faulty. Check cable connection.Ensure that the cabling is correct.

5. Check transmission on RNC side.

198084035 PPP LinkUnusable


� Description: PPP Link Unusable

� Severity: Major


Probable Cause Iub interface PPP link is faulty.

System Impact The services on this PPP link are unavailable.

HandlingSuggestion

1. On NMS fault management interface (realtime monitor), checkif the following alarm occurs. If yes, refer to the correspondingalarm handling suggestion.

Related alarms:





2. Check the jumper setting of SA/SE board. Ensure that thejumper of SA/SE board is properly configured in terms of E1cable type.

3. On Node B side, use physical cable to perform local Node Bself-loop. Check if the alarm can be restored on Node B side.If no, reset or replace board.

4. On RNC side, use physical cable to perform Node B E1/T1 self-loop. Check if the PPP alarm on Node B side can be restored. Ifno, transmission link must be faulty. Check cable connection.Ensure that the cabling is correct.

5. Check transmission on RNC side.



198084260 HDLC link hasCRC alarm


� Description: HDLC link has CRC alarm

� Description: HDLC link has CRC alarm


Probable Cause 1. Contact between fiber and optical port is poor. FS/RRU opticalmodule is faulty.

2. FS board clock is abnormal.3. RRU clock is abnormal.

System Impact In serious case, links and services on the board are down.

HandlingSuggestion

1. Ensure that the contact between fiber and optical port is good.2. Replace FS optical module and RRU optical module.3. Unplug and plug board.4. Replace board.

198084290 ETH port modeis unmatched with peer end


� Description: ETH port mode is unmatched with peer end



Probable Cause Port mode configured at local end and that configured at oppositeend are inconsistent.

System Impact Packet loss occurs to data communication at the network port.Service interruption might occur.

HandlingSuggestion

1. Check if the following alarm occurs to board. If yes, refer tothe corresponding alarm handling suggestion.

Related alarm: 198084271 Ethernet light and electricity lose

2. On NMS configuration management interface (Ethernet config-uration in IUB Transmission (Full IP)), check the port workingmode configured at local end. Check the corresponding con-figuration at opposite end.

� If the configuration at both ends is inconsistent, modifyconfiguration to keep consistency.

� If the configuration at both ends is consistent, first modifythe port working mode at local end, then re-modify it tothe previous mode.



198084045 Antenna VSWRalarm


� Description: Antenna VSWR alarm

� Severity: Minor


Probable Cause 1. Antenna feeder is faulty.2. Board is faulty.

System Impact Cell coverage area shrinks.

HandlingSuggestion

1. Check antenna feeder.

i. Check if RRU is connected to antenna. If no, connect RRUand the antenna.

ii. Check the cabling of antenna feeder. If the cabling is incor-rect, reconnect the cable according to the correspondinginstallation drawing.

iii. Check if the connectors of antenna feeder are tightlyscrewed down. If not, screw down the connectors tight.

2. Check the VSWR of antenna feeder by level.

i. Check if the feeder VSWR is normal. If no, replace feeder.

ii. If antenna feeder is connected to combiner, check if thecombiner VSWR is normal. If abnormal, replace combiner.

iii. Check antenna integrity. If the antenna is damaged, re-place or repair antenna.

3. Check RRU.

i. Reset board.

ii. Check the cabling of RF cable in RRU. If the connection isloose or disconnected, replace or properly install RF cable.

iii. Check if the power amplifier is faulty. If yes, replace poweramplifier.

iv. Check if the duplexer is faulty. If yes, replace duplexer.

v. Replace board.

198084046 Antenna overVSWR alarm


� Description: Antenna over VSWR alarm

� Severity: Major




Probable Cause 1. Antenna feeder is faulty.2. Board is faulty.

System Impact There is no transmission power output for the RF channel. Serviceinterruption occurs.

HandlingSuggestion

1. Check antenna feeder.

i. Check if RRU is connected to antenna. If no, connect RRUand the antenna.

ii. Check the cabling of antenna feeder. If the cabling is incor-rect, reconnect the cable according to the correspondinginstallation drawing.

iii. Check if the connectors of antenna feeder are tightlyscrewed down. If not, screw down the connectors tight.

2. Check the VSWR of antenna feeder by level.

i. Check if the feeder VSWR is normal. If no, replace feeder.

ii. If antenna feeder is connected to combiner, check if thecombiner VSWR is normal. If abnormal, replace combiner.

iii. Check antenna integrity. If the antenna is damaged, re-place or repair antenna.

3. Check RRU.

i. Reset board.

ii. Check the cabling of RF cable in RRU. If the connection isloose or disconnected, replace or properly install RF cable.

iii. Check if the power amplifier is faulty. If yes, replace poweramplifier.

iv. Check if the duplexer is faulty. If yes, replace duplexer.

v. Replace board.

198084048 Calibration fileon TRx board is abnormal


� Description: Calibration file on TRx board is abnormal

� Severity: Minor


Probable Cause Board calibration data is missing or damaged.

System Impact 1. Case 1

Downlink calibration file is abnormal, possibly leading to inac-curate transmission power and diminishing system coveragearea.

2. Case 2



Uplink calibration file is abnormal, possibly leading to greatererror of the reported Received Signal Strength Indicator (RSSI)and degrading service performance.

HandlingSuggestion

1. Reset board.2. Replace board.

198084056 Downlink digitalIF pre-distortion alarm


� Description: Downlink digital IF pre-distortion alarm



Probable Cause 1. DPD Flash loading fails.2. DPD initialization fails.3. Channel self-test fails.4. DPD startup fails.5. FPGA OP SPI operation fails.

System Impact RF output quality is affected. Board services are down.

HandlingSuggestion

1. On NMS fault management interface, check if the followingalarm (related to abnormal power and VSWR) occurs. If yes,refer to the corresponding alarm handling suggestion.

Related alarms:

� 198084065 Abnormal power

� 198084232 Digital power abnormal

� 198084045 Antenna VSWR alarm

� 198084046 Antenna over VSWR alarm

� 198084093 Remote antenna over VSWR alarm

� 198084094 Remote antenna VSWR alarm

2. Reset RF board.3. Replace RF board.



198084058 Downlink digitalpower exceeds rated powerslightly


� Description: Downlink digital power exceeds rated powerslightly



Probable Cause The digital power of DUC-combined IQ channel exceeds threshold.

System Impact RF output quality is degraded.

HandlingSuggestion


198084078 Surge protectiondevice has a fault alarm


� Description: Surge protection device has a fault alarm

� Severity: Minor


Probable Cause 1. Surge protection device is faulty.2. Environment Monitor Unit is faulty.

System Impact Operation of the surge protection device is abnormal. The equip-ment becomes unprotected against lightning strokes. Service isnot affected.

HandlingSuggestion

1. Replace surge protection device.2. Reset SA board.3. Replace dry contact cable.4. Replace SA board.



198084085 Main powersupply has a fault alarm


� Description: Main power supply has a fault alarm

� Severity: Major


Probable Cause 1. Main power supply is faulty.2. Environment Monitor Unit is faulty.

System Impact 1. Case 1

When this alarm is declared in non-RRU board, system opera-tion will not be affected temporarily. In the long run, systempowers supply might become inadequate, leading to degrada-tion of service performance, or even service interruption.

2. Case 2

When this alarm is declared in RRU board, power amplifier willbe automatically shut down by the system. Services on theRRU are down.

HandlingSuggestion

1. Replace main power supply.2. Reset SA board.3. Replace the relevant dry contact cable.4. Replace SA board.

198084086 External devicefault connected via drycontact


� Description: External device fault connected via dry contact

� Severity: Minor



System Impact No impact on service.

HandlingSuggestion




198084087 Surge protectiondevice in cabinet has a faultalarm


� Description: Surge protection device in cabinet has a faultalarm

� Severity: Minor



System Impact Operation of the surge protection device is abnormal. The equip-ment becomes vulnerable to lightning strokes. Service is not af-fected.

HandlingSuggestion


198084311 Hardware alarmAlarm Property � Alarm Code: 198084311

� Description: Hardware alarm



Probable Cause 1. BPC’s TDM interface is abnormal.

FS is not tightly inserted.

BPC is not tightly inserted.

FS has a hardware fault.

BPC has a hardware fault.

System clock has a fault.

2. BPC’s FPGA has DDR2 self-check failure.

BPC’s temperature is too high.

BPC’s FPGA invalidation.

BPC’s FPGA has DDR2 RAM fault.

System clock has a fault.

System Impact IQ channel becomes abnormal, affecting service quality. In seriouscase, link interruption occurs.



HandlingSuggestion

1. Please insert the FS tightly.2. Please insert the BPC tightly.3. FS has a hardware fault.

i. Soft-reset the FS.

ii. Power off the FS.

iii. Replace the fault FS Board.

4. BPC has a hardware fault.

i. Soft-reset the BPC.

ii. Power off the BPC.

iii. Replace the fault BPC Board.

5. BPC’s temperature is too high, check if the fan works normallyand clear the dust of dustproof net.

6. System clock has a fault.

i. Check if there has master-slave switching, and check if bothclocks of CC have been adjust.

ii. Check if there have clock alarm and AD9516 alarm on BPCor FS.

198084293 RU board hasslight high temperature


� Description: RU board has slight high temperature

� Severity: Minor


Probable Cause 1. Board temperature is too high.2. Fan is abnormal.

System Impact Board operation might be abnormal in the system.

HandlingSuggestion

Check if Fan operation is normal and if board temperature is toohigh.

198084294 PA slightover-temperature alarm


� Description: PA slight over-temperature alarm

� Severity: Minor




Probable Cause 1. Board temperature is too high.2. Fan is abnormal.


HandlingSuggestion

1. Check if the following alarms occur. If yes, refer to the corre-sponding alarm handling suggestion.

Related alarm:198084075 Fan alarm

2. Check if Fan operation is normal and if board temperature istoo high.

198084295 DL IQ channelchecking block alarm


� Description: DL IQ channel checking block alarm

� Severity: Major


Probable Cause Data reception error occurs on downlink IQ channel.

System Impact Communication link between UBPG to RRU downlink might befaulty.

HandlingSuggestion

1. Check if the following alarm (clock abnormal) occurs in BBU.

Related alarms:

� 198084003 Clock module fault

� 198084004 Clock reference source is lost

� 198084006 Clock reference source is degraded

� 198084266 Clock has a critical alarm

� 198084301 Transport clock reference source is fault

� 198084303 Clock has significant alarm

� 198084060 RF board PLL alarm

� 198084231 RRU clock frequency drift

� 198084299 PLL unlock alarm

2. Reset board.



198084296 60ms tag lostalarm


� Description: 60ms tag lost alarm

� Severity: Major


Probable Cause Downlink 60 ms tag is not received.

System Impact Communication link between UBPG and RRU downlink might befaulty.

HandlingSuggestion

1. Check if the IQ distribution of the subcarrier of relevant RRUboard is normal. The IQ distribution can be queried on CC via“ShowIQCfg”.

2. Check if the following alarm (clock abnormal) occurs in BBU.

Related alarms:


� 198084004 Clock reference source is lost








3. Reset board.

198084297 The configuredoperating frequency is out ofrange


� Description: The configured operating frequency is out ofrange



Probable Cause The difference between configured frequency and central fre-quency is over 5 M.



System Impact The services related to the faulty frequency are interrupted.

HandlingSuggestion

Configure the frequency in such a way that the difference betweenthe configured frequency and central frequency is within 5 M. Thenthe alarm will be restored.

198084298 Test source fileis abnormal


� Description: Test source file is abnormal

� Severity: Major


Probable Cause The file does not exist. The file is damaged or faulty.

System Impact IQ test source data loading fails.

HandlingSuggestion

Replace the relevant test source file.

198084299 RRU02 PLLunlock alarm


� Description: RRU02 PLL unlock alarm

� Severity: Major


Probable Cause 1. Corresponding subcode PLL circuit is abnormal.2. Input clock is abnormal.

System Impact Normal service is affected.

HandlingSuggestion

1. Unplug and plug board. Wait for 2 minutes.2. Replace board.

198084300 Dry contactstatus alarm


� Description: Dry contact status alarm



� Severity: Minor


Probable Cause The nature of this alarm is an external environment input alarmthat is not related with the equipment itself, such as smog, tem-perature, flood, external power, etc.


HandlingSuggestion

1. Check if the equipment related to this dry contact is faulty.2. Perform dry contact self-loop. Check if the dry contact is faulty.

If yes, replace board.

198084000 Failed to runFPGA software


� Description: Failed to run FPGA software



Probable Cause 1. Incorrect FPGA software version of this alarm board on theMain Control board

2. Board failure.

System Impact The services provided by this board are completely interrupted.

HandlingSuggestion

1. Re-download the software version on the software manage-ment interface.

2. Replace the board.

198084001 Failed to runDSP software


� Description: Failed to run DSP software



Probable Cause 1. Incorrect DSP software version of this alarm board on the MainControl board

2. Board failure.




HandlingSuggestion

� Re-download the software version on the software manage-ment interface.

� Replace the board.

198084003 Clock modulefault


� Description: Clock module fault



Probable Cause Hardware failure.

System Impact In the case of the active main control board failure, the systemdoes not provide normal operation, and the peripheral boardsmight have alarm of the corresponding clock module which causesinterruption to all the services on this board. In the case of thestandby main control board failure, the system may provide nor-mal operation but the active board and standby boards switchingover will not succeed which reduces the reliability of the system.

HandlingSuggestion

1. Reset the board.2. Plug/unplug the board.

198084012 Board hardwarefault


� Description: Hardware failure on the board.



Probable Cause The 64MHz clock is lost on the board.

System Impact The board fails to provide bearer service.

HandlingSuggestion

1. Reset the board.2. Replace the board.



198084013 Loss of Signal atIr interface


� Description: Loss of Signal at Ir interface

� Severity: Major


Probable Cause 1. Failure in the fiber optics, the optical module, or the connectionon this level board.

2. The board on the lower level is not properly powered on.3. Failure in the fiber optics, the optical module on the lower level

board.4. Hardware failure on the lower level board.

System Impact The board with the failure works normally, but the board with op-tical port has failure.

The “Loss of Signal at Ir interface” alarm occurred to the FS boardduring the RRU reset process is an accompanying alarm. Theservices beard by the system will be interrupted during the re-set process.

If the alarm occurs to the FS board, all the services of the systemwill be interrupted.

If the alarm occurs to the RTR, the services beard on the lowerlevel RRU will be interrupted.

HandlingSuggestion

Check the Fault Management window for the RRU correspondingalarms. Perform the recommended solution to process the alarm,if any.

Related alarm: 198084315 Board reboots alarm

1. Check for the failure in the fiber optics, the optical module, orthe connection on this board.

i. Check for failure in the fiber optics connection between thelower level RRU and the BBU (when the alarm is with FS),or the local level RRU (when the alarm is on RTR).Self-loopor replace the fiber if the physical appearance of the fiberdoes not bear any visible damage.

ii. Replace the optical port corresponding to FS, or the opticalmodule corresponding to the optical port 1 of the local RRU.

2. Check the power supply to the lower level board.

Check the power supply to the lower level board and check theRUN indicator on the RMB board.

3. Check for the failure in the fiber optics, the optical module.

i. Check for the possible failure in the fiber optics connectionbetween the optical port 0 of the lower level RRU and theoptical port 1 of the FS board, or the local level RRU. Re-place the fiber if the physical appearance of the fiber doesnot bear any visible damage.



ii. Replace the board with alarm and the optical module of thelower level RRU.

4. Check for the possible hardware failure with the lower levelRRU.

i. Check the fiber optics and the optical module of the lowerlevel RRU. If the fiber optics and the optical module areboth normal, then

ii. Reset the lower level RRU.

iii. Replace the lower level RRU.

198084060 RF board PLLalarm


� Description: RF board PLL alarm

� Severity: Major


Probable Cause 1. The base station software version is incorrect.2. Hardware failure with the board.

System Impact The RF output is influenced and the RF channel does not operatenormally which completely interrupts the services provided by thisboard.

HandlingSuggestion

1. Check the current software version of BS and ensure it is thecorrect version.


198084062 TransmissionRF channel fault


� Description: Transmission RF channel fault

� Severity: Major


Probable Cause It failed to initialize the local board IC.

System Impact The transmission channel of the RX/TX board does not operatenormally which completely interrupts the services provided by thisboard.



HandlingSuggestion


198084063 Receiving RFchannel fault


� Description: Receiving RF channel fault

� Severity: Major


Probable Cause It failed to initialize the board IC.

System Impact The receiving channel of the RX/TX board does not operate nor-mally which completely interrupts the services provided by thisboard.

HandlingSuggestion


198084064 LNA alarmAlarm Property � Alarm Code: 198084064

� Description: LNA alarm

� Severity: Major


Probable Cause 1. The internal LNA of RRU is damaged.2. The internal LNA alarm detector circuit of RRU is damaged.

System Impact The service coverage range is influence.

HandlingSuggestion

1. Replace the internal LNA of RRU.2. Reset the board.3. Replace the internal LNA of the board.4. Replace the board.

198084065 Improper powerAlarm Property � Alarm Code: 198084065

� Description: Improper power

� Severity: Major




Probable Cause 1. The power amplifier is not turn on.2. The power of the power amplifier is improper.3. The board failure.

System Impact The transmission power might be improper which affects the qual-ity of downlink service.

HandlingSuggestion

1. Turn on the power amplifier.2. Replace the power amplifier.

198084066 The loading ofDSP software failed


� Description: The loading of DSP software failed

� Severity: Major


Probable Cause 1. FPGA detection fails.2. SDRAM detection fails

System Impact The pre-distortion feature is not available which reduces the anal-ogy transmission power. The services provided by this board maybe completely interrupted under extreme condition.

HandlingSuggestion


198084067 DSP run errorAlarm Property � Alarm Code: 198084067

� Description: DSP run error

� Severity: Major


Probable Cause 1. The DSP response to command times out.2. DSP running error

System Impact The pre-distortion parameter fails to update dynamically. It mayreduce the analogy transmission power.

HandlingSuggestion

1. Wait 10 minutes for the system to recover automatically.2. Reset the board.3. Replace the board.



198084073 Temperaturesensor abnormity alarm


� Description: temperature sensor abnormity alarm

� Severity: Minor


Probable Cause Temperature sensor failure.

System Impact System is unable to monitor the environment temperature and thedevice temperature, but no impact to the services.

HandlingSuggestion

Replace the board.

198084074 Temperaturesensor not on-duty alarm


� Description: temperature sensor not on-duty alarm

� Severity: Minor


Probable Cause 1. Temperature sensor failure.2. The fault with the environment monitoring unit.

System Impact System is unable to monitor the environment temperature and thedevice temperature, but no impact to the services.

HandlingSuggestion

1. Replace the board.2. Replace the cable connecting FCE.3. Replace the FCE board.

198084075 Fan alarmAlarm Property � Alarm Code: 198084075

� Description: Fan alarm

� Severity: Major


Probable Cause 1. Fan failure.2. The fault with the environment monitoring unit.



System Impact The equipment temperature may become over high which maycause the board of the system to work improperly.

HandlingSuggestion

1. Replace FA2. Replace the SA board.

198084076 Heat exchangeralarm


� Description: Heat exchanger alarm

� Severity: Major


Probable Cause 1. The heater exchange temperature is overhigh.2. The heat exchanger has failure.3. The heater of heat exchanger has failure.4. The heat exchanger control board has failure.

System Impact The heat exchanger works improperly which may cause overhighor overlow temperature of the equipments and affect the normalservices.

HandlingSuggestion

1. Replace the heat exchanger fan.2. Replace the heat exchanger heater.3. Replace the heat exchanger control board.4. Replace the heat exchanger.

198084098 Battery FaultAlarm Property � Alarm Code: 198084098

� Description: Battery Fault

� Severity: Minor


Probable Cause 1. Battery fault is detected by Node B.2. The fault with the environment monitoring unit.

System Impact The battery fault impairs the normal operation of the system andcauses service interruption.

HandlingSuggestion

1. Check the dry contact configuration in the dry contact alarmconfiguration in the configuration resource management inter-face.

Make sure the configuration of the dry contact is in accordancewith the actual equipments installed.

2. Check the monitor cable connection with the dry contact. Re-place the cable in case of cable error.



3. Check the active battery.4. Reset the board.5. Replace the board.

198084100 Remote outputpower improper voltagealarm


� Description: Remote output power improper voltage alarm

� Severity: Major


Probable Cause The power module output is improper.

The normal range of the power module output is: 25V-32V.

System Impact The system is unable to operate normally, and the services pro-vided by this board are interrupted.

HandlingSuggestion

1. Check the power input voltage of the power module. Replacethe power supply in case of voltage error.

The normal rang of the power supply is:

� DC voltage:-36 V - -60 V

� AC voltage:80 V - 280 V

2. Replace the RRU power unit and wire the power unit to the RRUinterior module properly.

198084132 PPP LinkConfiger is unmatched withpeer end


� Description: PPP Link Configer is unmatched with peer end

� Severity: Major


Probable Cause 1. The PPP protocol types of the two ends are inconsistent.2. When the protocol type is MLPPP, the protocols on the ends of

the HDLC link are not consistent.



System Impact The SCTP link based on PPP protocol type fails to establish.

HandlingSuggestion

1. Check the PPP protocol type configuration.

Check the PPP protocol type configured at the local end to makesure it is consistent with the remote end.

To check the PPP protocol type: open the configuration man-agement interface and select IUB Transmission(Full IP) and se-lect Global Port Layer Management and check the PPP protocoltype.

2. Check the HDLC link configuration.

Check the HLC protocol type configured at the local end tomake sure it is consistent with the remote end.

To check the HDLC protocol type: open the configuration man-agement interface and select the IUB Transmission(Full IP) andselect Physical Layer Management and check the HDLC link in-cluded in the MLPPP.


198084133 PPP Failed toconfigure PPP link group


� Description: Failed to configure PPP link group

� Severity: Major


Probable Cause The failure of the PPP link group parameter configuration on theboard.

System Impact The PPP link group does not operate normally, and the SCTP beardon the PPP fails to setup the communication link.

HandlingSuggestion

1. Check the PPP protocol type configuration.

Check the PPP protocol type configured at the local end to makesure it is consistent with the remote end.

To check the PPP protocol type: open the configuration man-agement interface and select IUB Transmission(Full IP) and se-lect Global Port Layer Management and check the PPP protocoltype.

2. Check the HDLC link configuration.

Check the HLC protocol type configured at the local end tomake sure it is consistent with the remote end.

To check the HDLC protocol type: open the configuration man-agement interface and select the IUB Transmission(Full IP) andselect Physical Layer Management and check the HDLC link in-cluded in the MLPPP.



3. Delete the PPP link group and reconfigure it.4. Reset the board.5. Replace the board.

198084200 Main input powerover-voltage alarm


� Description: Main input power over-voltage alarm

� Severity: Major


Probable Cause 1. The improper voltage input of the active power supply.2. The fault with the environment monitoring unit.


HandlingSuggestion

1. Check the active power module for the proper voltage input.Replace the active power supply in case of voltage error.




2. Check the dry contact cable to ensure the cable is intact, andis securely connected.


198084201 Main input powerunder-voltage alarm


� Description: Main input power under-voltage alarm

� Severity: Major




HandlingSuggestion

1. 1. Check the active power module for the proper voltage input.Replace the active power supply in case of voltage error.






2. Check the dry contact cable to ensure the cable is intact, andis securely connected.


198084202 Main input powerpowered-down alarm


� Description: Main input power powered-down alarm

� Severity: Major




HandlingSuggestion









198084231 RRU clockfrequency drift


� Description: RRU clock frequency drift



� Severity: Minor


Probable Cause 1. BBU Clock Fault2. RRU Clock Fault

System Impact There is no impact to the service for the current drift range. Ifthe drift continues to increase, the BBU-RRU communication linkmight be interrupted and the service will be interrupted.

HandlingSuggestion

1. Check for BBU clock fault.

Open the Fault Management Interface to see if the alarm occursto other RRU too. If this alarm occurs to other RRU, then resetor replace the FS board; if no similar alarm occurs to otherRRU, then replace the CC board.

2. Replace the RRU.3. Check for RRU clock fault. Replace the local level RRU if this

alarm occurs to the local level RRU only.

198084232 Digital powerimproper


� Description: Digital power improper

� Severity: Major


Probable Cause 1. Realtime cell block.2. IQ Configuration error.

System Impact The downlink transmission becomes improper and RRU loses dig-ital power output. The Node B becomes faulty status and the UEfails to access.

HandlingSuggestion

1. Unblock the realtime cell.2. Reset the board.

198084235 Cpri signal ofport 0 lost


� Cpri signal of port 0 lost





Probable Cause 1. (When the local RRU is the first level) Failure with the fiberoptics and the optical module between the FS board and thelocal RRU.

2. (When the local RRU is not the first level) Failure with the fiberoptics and the optical module of the local RRU.

3. (When the local RRU is not the first level) Failure with the higherlevel RRU.

4. Reset the FS when the system is in normal operation, the RRUwill report this alarm which will recover after the FS is rebooted.In this case the alarm does not require any processing.

System Impact Reset the FS when the system is in normal operation, the RRU willreport this alarm which will recover after the FS is rebooted. Inthis case the alarm does not perform impact the services. In othercases, the communication link of the board is off of connection, andthe board does not bear any service.

HandlingSuggestion

1. (When the local RRU is the first level) Check the possible failurewith the fiber optics and the optical module between the FSboard and the local RRU.

i. Check for the possible failure in the fiber optics connectionbetween the local level RRU and the FS board. Replace thefiber if the physical appearance of the fiber does not bearany visible damage.

ii. Replace the optical module between the FS board and thelocal RRU.

2. (When the local RRU is not the first level) Check for the possiblefailure with the fiber optics and the optical module of the higherlevel RRU.

i. Check for the possible failure in the fiber optics connectionbetween the local level RRU and the higher level RRU. Re-place the fiber if the physical appearance of the fiber doesnot bear any visible damage.

ii. Replace the optical module between the local RRU and thehigher level RRU.

3. (When the local RRU is not the first level) Check for the possiblefailure with the higher level RRU.

i. Check the power supply to the higher level RRU to ensureits normal power supply.

ii. Reset the higher level RRU.

198084236 Ir link FIFOimproper


� Description: Ir link FIFO improper

� Severity: Minor




Probable Cause 1. Failure with the local RRU in the star networking mode.2. Failure with the higher level RRU in the chain networking mode.3. Ignore this alarm from the RTR when error occurs with the BPC

channel.

System Impact It might realign the FIFO and cause instant improper IQ signal andreduces the service performance.

HandlingSuggestion

1. Reset this level RRU.2. Check if this level RRU is the first level. When this level RRU is

the first level, reset the associated FS board; when this levelRRU is not the first level, reset the higher level RRU.

198084237 RRU RTWPimproper


� Description: RRU RTWP improper

� Severity: Minor


Probable Cause 1. Diversity antenna that is configured in the system does notexist (such as indoor coverage and outdoor full direction site)and there is no load connected to the RRU diversity.

2. The antenna feeder system is faulty and Antenna VSWR alarmor Remote antenna over VSWR alarm occurs. Check the an-tenna feeder system as it is possibly caused by the antennafeeder system.

3. The board failure.

System Impact The service coverage range might be reduced.

HandlingSuggestion

1. Diversity antenna that is configured in the system does notexist (such as indoor coverage and outdoor full direction site)and there is no load connected to the RRU diversity. Connectthe diversity with proper load.

2. The antenna feeder system is faulty and Antenna VSWR alarmor Remote antenna over VSWR alarm occurs. Resolve the twoalarms first.

3. Check the RF board for possible failure.

i. Check the RRU interior RF cable and its connection. Fastenthe cable or replace it if any problem is found.

ii. Check the duplex for possible damage. Replace the duplexin case of any damage.

iii. Replace the board.



198084257 UL IQ improperAlarm Property � Alarm Code: 198084257

� Description: UL IQ improper



Probable Cause Error with the TDM channel.

� The error with the clock of the BPC board or the FS board.

� The error with the socket of the BPC board or the FS board.

� The BPC board or the FS board connection is not secure andfirm.

� The hardware failure with the backplane connection cable.

� The hardware failure with the FS board or the BPC board

System Impact It provides potential impact to the system and may possibly de-crease the service quality.

HandlingSuggestion

1. Re-plug the associated FS board.2. Plug/unplug the board.3. Replace the board.

198084262 TDM CRC alarmAlarm Property � Alarm Code: 198084262

� Description: TDM CRC alarm

� Severity: Minor


Probable Cause 1. Poor contact between the FS board and the backplane.2. Poor contact between the BPC board and the backplane.3. The FS board hardware failure4. The BPC board hardware failure.

System Impact It may possibly decrease the service quality or cause interruptionthe service in the extreme conditions.

HandlingSuggestion

1. Check the contact between the FS board and the backplane,re-plug the FS board firmly.

2. Check the contact between the BPC board and the backplane,re-plug the BPC board firmly.

3. Check for the possible FS board hardware failure

i. Reset the board.

ii. Replace the board.

4. Check for the possible BPC board hardware failure

i. Reset the board.




198084263 RRU LOS alarmAlarm Property � Alarm Code: 198084263

� Description: RRU LOS alarm



Probable Cause 1. The poor connection with the fiber optics or the optical modulebetween the alarming RRU and the higher level board.

2. The connection failure with the fiber optics or the optical mod-ule between the alarming RRU and the higher level board.

System Impact The communication link on this board is off connection and theservices provided by this board is completely interrupted.

HandlingSuggestion

1. Check the possible failure with the fiber optics and the opti-cal module between the alarming RRU and the higher level FSboard.

Check the possible failure with the fiber optics and the opticalmodule between the RRU and the FS board, and re-plug thefiber and the optical module firmly.

2. Check for the possible connection failure with the fiber optics orthe optical module between the alarming RRU and the higherlevel board.

i. Check the possible failure with the fiber optics and the opti-cal module between the RRU and the FS board, make surethe fiber and the optical module are connected firmly.

ii. Replace the fiber optics and the optical module of the RRUand the FS separately.

198084264 RRU LOF AlarmAlarm Property � Alarm Code: 198084264

� Description: RRU LOF alarm



Probable Cause 1. The poor connection with the fiber optics or the optical modulebetween the alarming RRU and the higher level board.

2. The connection failure with the fiber optics or the optical mod-ule between the alarming RRU and the higher level board.


HandlingSuggestion

1. Check the possible failure with the fiber optics and the opti-cal module between the alarming RRU and the higher level FSboard.



Check the possible failure with the fiber optics and the opticalmodule between the RRU and the FS board, and re-plug thefiber and the optical module firmly.

2. Check for the possible connection failure with the fiber optics orthe optical module between the alarming RRU and the higherlevel board.

i. Check the possible failure with the fiber optics and the opti-cal module between the RRU and the FS board, make surethe fiber and the optical module are connected firmly.

ii. Replace the fiber optics and the optical module of the RRUand the FS separately.

198084265 RRUpowered-down alarm

Alarm Property 1. Alarm Code: 1980842652. Description: RRU powered-down alarm3. Severity: Critical4. Alarm Type: Equipment alarm

Probable Cause 1. The corresponding RRU is powered down.2. RRU power supply is unstable.


HandlingSuggestion

1. The power supply to the corresponding RRU is interrupted, itis required to check and resume the RRU power supply at thestation.

2. Check the voltage of RRU power supply and ensure stable volt-age.

198084266 Clock has acritical alarm


� Description: Clock has a critical alarm.



Probable Cause 1. AD9516 is unlocked.

i. Hardware failure with the active main control board.

ii. Board hardware fault

2. FPGA clock alarm.



i. The active main control board is reset.

ii. Hardware failure with the active main control board.

iii. Hardware failure with the board.

3. Frame error.




4. The Fsync clock is lost




5. 10M is lost.

The hardware failure with the local board.

6. 80M is lost.

The hardware failure with the board.

7. The serdes clock is lost


ii. Hardware failure with the board.

System Impact The error with the clock module may possibly decrease the servicequality or cause interruption the service in the extreme conditions.

HandlingSuggestion

Check the detailed information of this alarm on the fault manage-ment interface. The detailed information of this alarm presentsthe cause of the alarm which helps to find the processing methodquickly.

The suggested process method for each alarm cause is describedbelow:

� Alarm cause: AD9516 unlock,80M lost, serdes clock lost.

i. Reset the active main control board.

ii. Replace the active main control board.

iii. Reset the board.

iv. Replace the board.

� The causes of the alarm: FPGA clock alarm, frame error, Fsyncclock lost.

i. Check if the active CC is reset. If it is reset, then this alarmis a normal response that requires no processing.

ii. Reset the active main control board.

iii. Replace the active main control board.

iv. Reset the board.

v. Replace the board.

� The cause of the alarm: 10M lost.

i. Reset the board.




198084272 Lightningarrester alarm at indoorlightning protection box


� Description: Lightning arrester alarm at indoor lightning pro-tection box

� Severity: Minor


Probable Cause � The fault with the environment monitoring unit.

� Failure with the lightning arrester caused by lightning damage,poor grounding or parts aging, etc.

System Impact None.

HandlingSuggestion








4. Reset the board.5. Replace the board.6. Check the grounding of the lightning arrester to ensure secure

grounding.7. Replace the lightning arrester



198084273 Circuit breakeralarm at indoor lightningprotection box


� Description: Circuit breaker alarm at indoor lightning protec-tion box

� Severity: Major


Probable Cause 1. The circuit breaker is in over-current protected status, or isopen circuited.

2. The fault with the environment monitoring unit.

System Impact Power supply interruption occurs to the corresponding power line.

The RRU service interruption occurs if the faulty power line is pro-vided to the RRU.

HandlingSuggestion



2. Check the monitor cable connection with the dry contact. Re-place the cable in case of cable failure.

3. Check the switch of the circuit breaker to find out the causeof the over-current protection or open circuit and resolve thedefect.

4. Replace the circuit breaker.5. Reset the board.6. Replace the board.

198084274 Outdoorlightning protection boxalarm


� Description: Outdoor lightning protection box alarm

� Severity: Minor


Probable Cause 1. Failure with the outdoor lightning protection boThe failure withthe outdoor lightning arrester caused by lightning damage,poor grounding or parts aging, etc.



2. The fault with the environment monitoring unit.

System Impact The lightning protection is invalid.

HandlingSuggestion




3. Replace the dry contact connection cable between the RRU andthe outdoor lightning protection bo

4. Replace the lightning arrester5. Replace the RRU.

198084275 Failed todownload software


� Description: Download software failed



Probable Cause 1. Incorrect software version of this alarm board on the Main Con-trol board.

2. Board failure.

System Impact The board software update fails and the services provided by thisboard is completely interrupted.

HandlingSuggestion

1. Re-download the software version on the software manage-ment interface.


198084276 Downlink DACPLL unlock


� Description: Downlink DAC PLL unlock

� Severity: Major


Probable Cause RRU hardware failure.



System Impact The downlink link is disconnected, and the system is out of oper-ation. The services provided by this board are completely inter-rupted.

HandlingSuggestion


198084286 PWR monitoringunit alarm


� Description: PWR monitoring unit alarm

� Severity: Minor


Probable Cause 1. The dry contact connection cable is disconnected.2. The monitoring unit is damaged.

System Impact The power monitoring unit operates improperly, and fails to reportthe power data.

HandlingSuggestion


2. Replace the monitoring unit.

198084287 AC power-cutalarm


� Description: AC power-cut alarm

� Severity: Minor


Probable Cause 1. The dry contact connection cable is disconnected.2. The AC power supply is interrupted, or the other defects that

cause interruption to the AC supply.

System Impact The AC power is offline, the system works on the temporary bat-tery supply.

HandlingSuggestion


2. Use the emergency generator.3. Recover the AC power supply as soon as possible.



198084288 Battery inlow-voltage alarm


� Description: Battery in low-voltage alarm

� Severity: Minor


Probable Cause 1. The dry contact connection cable is disconnected.2. The AC power supply is interrupted, or the other defects that

cause interruption to the AC supply.

System Impact The battery lifetime could be shortened by low voltage operation.The system is unreliable and may cease operation and service im-mediately when the power supply is exhausted.

HandlingSuggestion


2. Recharge the battery as soon as possible until the battery volt-age is higher than the normal value.

198084289 Rectifier alarmAlarm Property � Alarm Code: 198084289

� Description: Rectifier alarm

� Severity: Minor


Probable Cause 1. The dry contact connection cable is disconnected.2. The rectifier works improperly.

System Impact The power supply is unreliable and may cause interruption to theoperation and service.

HandlingSuggestion


2. Replace the Rectifier module.

198084301 Transport clockreference source is fault


� Description: Transport clock reference source is fault

� Severity: Major




Probable Cause 1. The frequency offset of MT9040 8K clock reference source isover large.

2. Board failure.

System Impact Error with the E1/T1 link, may impair the transmission quality andimpair the service quality.

HandlingSuggestion

1. Check if the higher level E1/T1 equipments (including the RNC,the microwave, etc )is in normal operation. Open the rack mapon the Configuration Management window and check if the DTBboard is in normal operation.


198084302 DSP AIF isimproper


� Description DSP AIF is improper



Probable Cause The BPC board hardware failure.

System Impact The random access does not work. The board is reset and the linkis interrupted which completely interrupts the services providedby this board.

HandlingSuggestion

1. Wait for 10 seconds. The board will reset automatically if thealarm persists.


198084306 Improper DPDrunning status


� Description: Improper DPD running status

� Severity: Minor


Probable Cause 1. DPD soft reset fails.2. The expected DPD signal is improper.3. The DPD feedback signal is out of range.4. The DPD delay device fails.



5. The DPD adaptive detection error is too high.

System Impact The downlink power output drops and the quality of RF outputdeclines.

HandlingSuggestion

The system can recover automatically without manual interven-tion.

198084307 MP over-currentalarm


� Description: MP over-current alarm



Probable Cause 1. Failure with the board.2. Failure with the PM board.

System Impact The power to the over-current board is turn off and the servicesprovided by this board is completely interrupted

HandlingSuggestion

1. Re-plug the over-current board.2. Replace the over-current board.3. Switch the active board and the standby board.4. Replace the board.

198084308 PP over-currentalarm


� Description: PP over-current alarm



Probable Cause 1. Failure with the board.2. Failure with the PM board.

System Impact The power to the over-current board is turn off and the servicesprovided by this board is completely interrupted.

HandlingSuggestion

1. Re-plug the over-current board.2. Replace the over-current board.3. Switch the active board and the standby board.4. Replace the board.



198084310 The reportedpower has a CRC error


� Description: The reported power has a CRC error

� Severity: Minor


Probable Cause 1. Error with the crc power data reported.2. The RRU board failure.

System Impact It may possibly decrease the service quality of the PA service (theUPA/DPA service) or cause interruption the service at the extremeconditions.

HandlingSuggestion

1. Check if the UL IQ improper alarm occurs.

If this alarm occurs, follow the suggestion to this alarm.

Related alarm: 198084257 UL IQ improper

2. Review the topology structure and check the fiber optics con-nection between the FS board and the RU boards connectedwith it.

3. Replace the optical module on the associated FS board.

Replace the optical module on the RU board connected withthe associated FS board if the alarm persists.

4. Reset the RU board connected with the associated FS board.5. Replace the RU board connected with the associated FS board.

198084317 Self-defined drycontact alarm


� Description: Self-defined dry contact alarm

� Severity: Minor


Probable Cause The exterior device failure connected to the dry contact.




HandlingSuggestion

Perform different process methods according to the type of theexterior devices.

198084322 Backplane boardhas a clock alarm


� Description: Backplane board has a clock alarm



Probable Cause 1. On backplane board, 61.44M is lost.2. On backplane board, 10ms is error.3. On backplane board, frame number is error.4. On backplane board, 60ms is error.

System Impact In serious situation, all services on the board will be interrupted;in minor situation, there is no influence on services.

HandlingSuggestion

1. Check if there is a PLL or clock related alarm on master CCboard.

2. If there is such an alarm and it cannot be recovered within 5minutes, reset the board. After reset, if the alarm still exists,it means this board has a fault. In this case, replace it with anew board.

198084323 Intra-board clockalarm


� Description: Intra-board clock alarm



Probable Cause 1. AIF GTP 122.88M clock lost.2. AD9516 lost lock.

System Impact Baseband board auto-reset so that all services are interrupted.

HandlingSuggestion

1. The system will auto-reset this board.2. If the alarm is not recovered after 3 times of reset, replace this

board.



198084324 Antenna datalink performance alarm


� Description: Antenna data link performance alarm

� Severity: Minor


Probable Cause Data link at bottom layer has an error code.

System Impact There is no influence on services.

HandlingSuggestion

1. Check UBPG, FS and RRU to find if there is relevant clock alarm,such as "backplane board clock alarm" or "intra-board clockalarm".

2. If there is no relevant clock alarm, it means either UL or DLfiber link has performance problem.

198084325 Antenna datalink error alarm


� Description: Antenna data link error alarm



Probable Cause 1. UL link is abnormal.2. DL link is abnormal.

System Impact In serious situation, corresponding IQ channel is blocked and allcorresponding services are interrupted due to UL error; DL errorcauses all carriers on the board to be unavailable. In minor situa-tion, there is no influence on UL/DL services.

HandlingSuggestion

1. Check UBPG, FS and RRU to find if there is relevant clock alarm,such as "backplane board clock alarm" or "intra-board clockalarm". If there is relevant clock alarm, it means either "back-plane board" or "intra-board clock" has a problem. Please han-dle the problem accordingly.

2. Check if there is an "antenna data link performance alarm". Ifyes, it means system clock or fiber link at bottom layer hasperformance problem.

3. Check if there is "IQ configuration failure" alarm. If yes, itmeans incorrect IQ configuration. Please check BBU and RRUto make sure they can run normally.

4. If there is no any of above alarms, please open version man-agement function to re-load DSP/FPGA software version of thisboard. Wait until Node B reboot is finished, then check if thealarm is recovered or not.



198084335 RRU02 PAover-high temperature alarm


� Description: RRU02 PA over-high temperature alarm



Probable Cause 1. The fan at PA layer works abnormally so that there is a heat-cooling problem.

2. PA is abnormal.

System Impact There is influence on services. The PA associated logic carrier isblocked.

HandlingSuggestion

Check if the fan is abnormal or PA temperature is too high.

198084088 Remote inputpower over-voltage alarm


� Description: Remote input power over-voltage alarm

� Severity: Major


Probable Cause 1. The AC input voltage of power module is higher than the alarmthreshold 280v (the tolerance is +/-1V).

2. The DC input voltage of power module is higher than the alarmthreshold 60v (the tolerance is +/-1V).

System Impact There is no impact on the system if it is short time operation only.For long period operation, the board or the system might fail tooperate properly and the service on this board will be interrupted.

HandlingSuggestion

1. The AC input voltage of power module is higher than the alarmthreshold 280v (the tolerance is +/-1V).

i. Shut down the RRU and disconnect it from power socket.Check whether the voltage of the AC input is higher than281V (the tolerance is +/- 1V).

ii. Replace the voltage module RPWDC of RRU.


i. Shut down the RRU and disconnect it from power socket.Check whether the voltage of the DC input is higher than61V (the tolerance is +/- 1V).




198084089 Remote inputpower under-voltage alarm


� Description: Remote input power under-voltage alarm

� Severity: Major


Probable Cause 1. The AC input voltage of power module is lower than the alarmthreshold 80v (the tolerance is +/-1V).


System Impact There is no impact on the system if it is short time operation only.For long period operation, the board or the system might fail tooperate properly and the service on this board will be interrupted.

HandlingSuggestion

1. The AC input voltage of power module is lower than the alarmthreshold 80v (the tolerance is +/-1V).

i. Shut down the RRU and disconnect it from power socket.Check whether the voltage of the AC input is lower than81V (the tolerance is +/- 1V).


2. The DC input voltage of power module is lower than the alarmthreshold 36v (the tolerance is +/-1V).

i. Shut down the RRU and disconnect it from power socket.Check whether the voltage of the DC input is lower than37V (the tolerance is +/- 1V).


198084090 Remote inputpower powered-down alarm


� Description: Remote input power powered-down alarm

� Severity: Major


Probable Cause 1. The power module is not working abnormally.2. Failure with the RRU power module RPWDC.

System Impact The board or the system fails to operate normally, and the servicesprovided by this board are interrupted.



HandlingSuggestion

1. Check if the power module is working abnormally.

Shut down RRU and remove the -48V power plug. Check thepower socket with multi-meter for the voltage difference be-tween the -48V terminal and the -48VGND terminal.

2. Check for the possible failure with the RRU power module RP-WDC.

Replace the voltage module RPWDC of RRU, and connect theinterior modules in RPWDC and RRU properly. Turn on thesystem.

198084091 Remote outputpower over-current alarm


� Description: Remote output power over-current alarm

� Severity: Major


Probable Cause The power module output is abnormal.

System Impact The board or the system may fail to operate normally, and theservices provided by this board are interrupted.

HandlingSuggestion

Replace the voltage module of the board, and connect the interiormodules in RPWDC and RF board properly. Turn on the system.

198084092 Remote poweroutput under-voltage alarm


� Description: Remote power output under-voltage alarm

� Severity: Major


Probable Cause 1. The power module input is not normal.2. The power module output is abnormal.

System Impact The board or the system may fail to operate normally, and theservices provided by this board are interrupted.

HandlingSuggestion

1. The power module input voltage is low or not normal.2. Replace the voltage module RPWDC of RRU, and connect the

interior modules in RPWDC and RRU properly. Turn on thesystem.



198084093 Remote antennaover VSWR alarm


� 198084093 Remote antenna over VSWR alarm

� Severity: Major


Probable Cause 1. The antenna failure2. The board failure.

System Impact The board or the system fails to operate normally, and the servicesprovided by this board are interrupted.

HandlingSuggestion

1. Check the antenna failure.

i. Check if RRU is connected to the antenna properly. Connectthe antenna in case it is not connected.

ii. Check if antenna feeder is properly connected. If thereis any problem with the connection, correct the problemaccording to the construction diagram.

iii. Verify that the connector of the antenna feeder is tightenedsecurely. Fasten the connector if the connection is loose.

2. Check the feeder standing waves of each level.

i. Check if the standing wave of feeder is normal. Replacethe feeder if the standing wave is not normal.

ii. If combiner is connected to the feeder, check if the standingwave of the combiner is normal. Replace it if the standingwave is not normal

iii. Check if the antenna is normal. Replace or repair it if thereis any problem with the antenna.

3. Check the RRU for possible failure.

i. Reset the board.

ii. Check the RRU for the poor connection of the RF cable.Fasten the cable or replace it if any loose or disconnectionis found.

iii. Check the power amplifier for possible failure. Replace thepower amplifier in case of any damage.

iv. Check the duplex for possible damage. Replace the duplexin case of any damage.




198084094 Remote antennaVSWR


� Description: Remote antenna over VSWR alarm

� Severity: Major


Probable Cause 1. The antenna failure2. The board failure.

System Impact No influence to the services on this board.

HandlingSuggestion


i. Check if RRU is connected to the antenna properly. Connectthe antenna in case it is not connected.

ii. Check if antenna feeder is properly connected. If thereis any problem with the connection, correct the problemaccording to the construction diagram.

iii. Verify that the connector of the antenna feeder is tightenedsecurely. Fasten the connector if the connection is loose.

2. Check the feeder standing waves of each level.

i. Check if the standing wave of feeder is normal. Replacethe feeder if the standing wave is not normal.

ii. If combiner is connected to the feeder, check if the standingwave of the combiner is normal. Replace it if the standingwave is not normal

iii. Check if the antenna is normal. Replace or repair it if thereis any problem with the antenna.

3. Check the RRU for possible failure.

i. Reset the board.

ii. Check the RRU for the poor connection of the RF cable.Fasten the cable or replace it if any loose or disconnectionis found.

iii. Check the amplifier for possible failure. Replace the poweramplifier in case of any damage.

iv. Check the duplex for possible damage. Replace the duplexin case of any damage.




198084136 Uplink channelruns abnormally


� Description: Uplink channel runs abnormally



Probable Cause The clock is not working properly.

System Impact The board failure.

The system will release all subscribers and reset the board. Thefailure will be recovered after board restarts, and normal operationwill resume.

HandlingSuggestion

Replace the board.

198084137 Downlinkchannel runs abnormally


� Description: Downlink channel runs abnormally



Probable Cause The clock is not working properly.

System Impact The board failure. The system will release all subscribers and resetthe board.

The failure will be recovered after board restarts, and normal op-eration will resume.

HandlingSuggestion

Replace the board.

198084139 PA over poweralarm


� Description: PA over power alarm





Probable Cause 1. The RRU board failure.2. The BPC board failure.

System Impact The power output is turned off and no transmission power outputis supplied on this RF channel which completely interrupts the ser-vices provided by this board.

HandlingSuggestion


198084141 PA overtemperature alarm


� Description: PA over temperature alarm



Probable Cause 1. The environmental temperature is over high.2. The RRU failure.

System Impact The power output is turned off and no transmission power outputis supplied on this RF channel which completely interrupts the ser-vices provided by this board.

HandlingSuggestion

1. The environmental temperature is over high.

i. Ensure the normal operation of the indoor air conditioning.

ii. Ensure the normal operation of the environment fan.

2. The RRU failure.

i. Replace the power amplifier.


198084145 PAcommunication fault


� Description: PA communication fault



Probable Cause The PA communication failure.

The connection wire between the power amplifier and the monitormodule is loose.



System Impact The board failure.

The system fails to set the power amplifier which completely in-terrupts the services provided by this board.

HandlingSuggestion

1. Reset the board.2. Check the connection wire between the power amplifier and

the monitor module and ensure it is securely connected.3. Replace the power amplifier module.4. Replace the monitor module.

198084146 RET motor faultAlarm Property � Alarm Code: 198084146

� Description: RET motor fault

� Severity: Major


Probable Cause Failed to find the adjusting motor of the power adjusted antenna.

System Impact The RET motor malfunctions and cause the performance drop inthe cell.

HandlingSuggestion

Check the adjusting motor.

198084147 RET hardwarefault


� Description: RET hardware fault.

� Severity: Major


Probable Cause The failure with the power adjusted antenna.




HandlingSuggestion

Check the power adjusted antenna hardware.

198084148 RET softwarefault


� Description: RET software fault.

� Severity: Major


Probable Cause The power adjusted antenna parameter is not configured properly.


HandlingSuggestion

Check the system parameters.

198084151 ATMAcommunication link isinterrupted


� Description: ATMA communication link is interrupted.

� Severity: Major


Probable Cause 1. Failure with the ATMA equipment.2. Failure with the communication cable between the ATMA equip-

ment and the system.3. Failure with the environment monitoring board.

System Impact The system fails to communicate with the ATMA equipment. If theequipment has failure, the operation performance of the cell willdrop.

HandlingSuggestion

1. Check the communication cable between ATMA equipment andNode B and ensure the connection is proper and secure.

2. Reset the RRU board.3. Replacement the equipment



198084152 RETcommunication link isinterrupted


� Description: RET communication link is interrupted.

� Severity: Major


Probable Cause 1. Failure with the RET equipment.2. Failure with the communication cable between the RET equip-

ment and the system.3. Failure with the environment monitoring board.

System Impact The system fails to communicate with the AISG device and fails tomanage and detect alarm.

If the equipment has any failure, the operation performance of thecell will drop.

HandlingSuggestion

1. Check the communication cable between RET equipment andNode B and ensure the connection is proper and secure.


198084153 ACOM hardwarefault


� Description: ACOM hardware fault.

� Severity: Major


Probable Cause The hardware configuration parameter is incorrect.

System Impact The ACOM malfunctions and cause the performance drop in thecell.

HandlingSuggestion

1. Reset the associated RRU board.2. Replacement the equipment



198084154 ACOM softwarefault


� Description: ACOM software fault.

� Severity: Major


Probable Cause The software configuration parameter is incorrect.

System Impact The ACOM malfunctions and cause the performance drop in thecell.

HandlingSuggestion

1. Reset the associated RRU board.2. Replacement the equipment.

198084156 ACOMcommunication link isinterrupted


� Description: ACOM communication link is interrupted.

� Severity: Major


Probable Cause 1. The equipment fails.2. Failure with the communication cable between equipment and

Node B3. Failure with the environment monitoring board.

System Impact Node B fails to communicate with the ACOM equipment whichcauses the operation performance drop with the cell.

HandlingSuggestion

1. Check the communication cable between RET equipment andNode B and ensure the connection is proper and secure.




198084208 AISG EEPROMerror


� Description: AISG EEPROM error

� Severity: Minor


Probable Cause The AISG-EEPROM parameter is incorrect.

System Impact The AISG malfunctions and cause the performance drop in the cell.

HandlingSuggestion

1. Reset the equipment.2. Replacement the equipment

198084209 AISG flash eraseerror


� Description: AISG flash erase error

� Severity: Minor


Probable Cause The AISG-FLASH parameter is incorrect.


HandlingSuggestion

1. Reset the equipment.2. Replacement the equipment

198084210 AISG flash errorAlarm Property � Alarm Code: 198084210

� Description: AISG flash error

� Severity: Minor


Probable Cause The AISG-FLASH parameter is incorrect.


HandlingSuggestion

1. Reset the equipment.2. Replace the equipment.



198084211 AISG otherhardware error


� Description: AISG other hardware error.

� Severity: Minor


Probable Cause The AISG configuration parameter is incorrect.


HandlingSuggestion


198084215 RET motor faultAlarm Property � Alarm Code: 198084215

� Description: RET motor fault

� Severity: Major


Probable Cause The failure with the RET motor.


HandlingSuggestion

1. Open the Base station Configuration Management window,open AISC equipment centralized management, select auto-matic calibrate the RET equipment again .

2. Remount the RET motor and automatically calibrate it.3. Replace the RET motor.

198084212 AISG othersoftware error


� Description: AISG other software error.

� Severity: Minor


Probable Cause The AISG software configuration parameter is incorrect.




HandlingSuggestion


198084213 AISG RAM errorAlarm Property � Alarm Code: 198084213

� Description: AISG RAM error

� Severity: Minor


Probable Cause The AISG-RAM parameter is incorrect.


HandlingSuggestion


198084214 AISG UARTerror


� Description: AISG UART error

� Severity: Minor


Probable Cause The AISG-UART parameter is incorrect.


HandlingSuggestion


198084216 RET motor can’tadjust


� Description: RET motor can’t adjust

� Severity: Major


Probable Cause RET motor does not work to adjust the antenna.




HandlingSuggestion

1. Open the Base station Configuration Management window,open AISC equipment centralized management, select auto-matic calibrate the RET equipment again.

2. Remount the RET motor.3. Replace the RET motor.

198084217 RET motordon’t responed the adjustingcommand


� Description: RET motor don’t responed the adjusting com-mand

� Severity: Minor


Probable Cause RET motor does not respond to the adjusting command.


HandlingSuggestion



198084218 RET don’tcalibrated


� Description: RET don’t calibrated

� Severity: Major


Probable Cause RET fails to calibrate.


HandlingSuggestion





198084219 RET data don’tscaled


� Description: RET data don’t scaled.

� Severity: Major


Probable Cause RET data fails to scale.


HandlingSuggestion

1. Open the Base station Configuration Management window,open AISC equipment centralized management, select sendthe configuration data for the RET equipment again.

2. Replace the motor.

198084220 RET position lostAlarm Property � Alarm Code: 198084220

� Description: RET position lost

� Severity: Minor


Probable Cause The RET position data is lost.


HandlingSuggestion


2. Remount the motor and calibrate it automatically.3. Replace the motor.



198084221 ATMA minoralarm


� Description: ATMA minor alarm

� Severity: Minor


Probable Cause The minor failure with ATMA.

System Impact The operation performance drops in the cell.

HandlingSuggestion


198084222 ATMA majoralarm


� Description: ATMA major alarm

� Severity: Major


Probable Cause The ATMA has a major failure.


HandlingSuggestion


198084223 ACOM minoralarm


� Description: ACOM minor alarm

� Severity: Minor


Probable Cause The ACOM has a minor failure




HandlingSuggestion


198084224 ACOM majoralarm


� Description: ACOM major alarm

� Severity: Major


Probable Cause The ACOM has a major failure.


HandlingSuggestion


198084234 PA Run Failedalarm


� Description: PA Run Failed alarm

� Severity: Major


Probable Cause The RRU failure.

System Impact The entire system loses power output and the subscriber fails toaccess.

HandlingSuggestion


198084255 E1T1 slidingcode


� Description: E1T1 sliding code

� Severity: Minor




Probable Cause The hardware failure or the link failure.

System Impact The board may work normally.

When multiple clock references are configured, select the availableclock reference per priority sequence, and the system will operatenormally. When all the clock references configured are lost, thesystem clock will choose to remain or return to free-run mode andthe impact to the system is as below:

1. Iub interface

� STM-1 connection.

There is no influence to the operation of Node B, but thenext level of cascaded Node B might be influenced.

� E1 connection.

No impact for the ITC mode, the periodical slide code mightoccur to the Iub interface after long period operation at CTCmode.

2. Handover between Node B base stations.

If the clock accuracy of Node B fails to meet 3GPP requirement,the success rate of the handover might drop.

HandlingSuggestion


198084304 Board doesn’tsupport such configuration


� Description: Board doesn’t support such configuration.

� Severity: Minor


Probable Cause The CC board does not support this function.


HandlingSuggestion

1. Acquire the actual name of the CC board.

Method of acquiring: open Asset Management Report windowand run “Get the hardware Information of the Board ”Then theCCType item is the actual name of the CC board.

The relations between the actual name and the configurationsupported are as below:

i. CC0: E1 0 to 15 channels and embedded GPS supported;2MHz clock configuration not supported.

ii. CC1: E1 0 to 7 channels and embedded GPS supported;2MHz clock configuration not supported.



iii. CC2: E1 0 to 7 channels supported; embedded GPS notsupported; 2MHz clock configuration supported.

2. Replace the board with compatible boards or modify the con-figuration to meet the actual boards used.

198084238 Frame SeqNoFailed


� Description: Frame SeqNo Failed



Probable Cause 1. The backplane 61.44M is lost.2. The backplane 10ms has error.3. The backplane frame no. has error.4. The backplane 60ms has error.

System Impact When the error is minor, there is no impact on the system; whenthe error is serious, all services on this board will be interrupted.

HandlingSuggestion

1. Check the active CC board for any possible alarms about phase-lock loop and or clock. If there is any alarm, wait 5 minutesfor the system to recover.

Related Alarms


� 198084004 Clock reference source is lost.











198084240 AIF InterfaceFailed


� Description: AIF Interface Failed



Probable Cause 1. Uplink error.2. Downlink error.

System Impact When the error is minor, there is no impact on the uplink/downlinkservices. When the error is serious, the uplink error will congestthe corresponding IQ channel by, all services will be interrupted;the downlink error could interrupt the carrier frequency of the en-tire board.

HandlingSuggestion

1. Check the Fault Management window for the alarms corre-sponding to UBPG board, FS board, RRU board. Perform therecommended solution to process the alarm, if any.

Related Alarms

� 198084238 Frame SeqNo Failed

� 198084292 AD9516 unlock alarm

2. Check if there is any alarm related to IQ configuration failure.If there is such alarm, then the IQ configuration is incorrect.Perform the recommended solution to process the alarm(s) andmake sure that the BBU board and the RRU board is in normaloperation.

Related alarm: 198084250 IQ Config Failed

3. Open Version Manage interface and reload the DSP/FPGA ver-sion of this board, then wait for the base station to reboot.

198084244 Software LoadAbnormal


� Description: Software Load Abnormal



Probable Cause 1. The DSP or FPGA software version of the board is incorrect.2. Hardware failure with the board.

System Impact The board software does not operate properly and the servicesprovided by this board is completely interrupted.



HandlingSuggestion

1. Open Version Manage interface and update the DSP/FPGA ver-sion of this board.

2. Reset the board.

198084239 HardWareTimeSlot Terminate Failed


� Description: HardWare TimeSlot Terminate Failed



Probable Cause 1. FPGA software operation error.2. 61.44M clock error.

System Impact The UBPG board software does not operate properly and the ser-vices provided by this board are completely interrupted.

HandlingSuggestion

1. Check the board for the related alarms. Perform the recom-mended solution to process the possible alarms.

Related alarm : 198084238 Frame SeqNo Failed.

2. Open Version Manage interface and update the FPGA versionof this board.

198084241 Out RAMRead/Write Failed


� Description: Out RAM Read/Write Failed

� Severity: Minor


Probable Cause The UBPG board hardware has failure.

System Impact The UBPG board software does not operate properly and the ser-vices provided by this board are completely interrupted.

HandlingSuggestion

� Reset the board.

� Replace the board.



198084243 Uplink Trx 60msAbnormal


� Description: Uplink Trx 60ms Abnormal



Probable Cause 1. The optical switching board does not work properly.2. The link is disconnected between baseband and RF.3. The RF board does not work properly.

System Impact The corresponding IQ channel is congested which causes interrup-tion to its services.

HandlingSuggestion

1. Check the local board fiber connection and make sure the con-nection is correct and secure.

2. Check whether the opposite RF board is in proper operation.3. Check whether the opposite optical switch board is in normal

operation.4. Reset the board.5. Reset the opposite RF board.6. Reset the opposite optical switch board.7. Replace the board.8. Reset the opposite RF board.9. Reset the opposite optical switch board.


C h a p t e r 3

Communication Alarm

Table of Contents198084015 STM-1 optical signals are lost. ............................84198084016 STM-1 loses frame synchronization .....................85198084017 STM-1 MSAIS (MS Alarm Indicator Signal) ...........86198084018 STM-1 AU4 loss of pointer..................................87198084245 Physical param not consistent with radioparam..............................................................................88198084246 Radio param error.............................................88198084247 Link3 of BUC software not response ....................89198084248 DSP software of BP board has no response...........89198084249 DBB parameter of BP board response error ..........90198084036 SCTP stream number mismatch ..........................90198084291 Configuration parameter of O&M Channel iswrong ..............................................................................91198084312 E1/T1 link configuration is failed .........................91198084313 Qos bandwidth configuration is failed...................92198084314 IP clock configuration is failed.............................92198084326 Physical param not consistant with radioparam..............................................................................93198084327 Radio param error.............................................93198084282 Lost of frame number at optical port....................93198084283 Lost of frame rate and frame number ..................94198084019 E1/T1 LOS (Loss Of Signal) alarm .......................94198084020 E1/T1 link loss of frame alarm ............................95198084021 E1/T1 loss of cell delineation alarm .....................96198084022 E1/T1 link loss of IMA frame alarm......................96198084023 E1/T1 IMA group is not operational .....................97198084024 E1/T1 remote receiving fault ..............................98198084025 E1/T1 link self-loop ...........................................98198084026 PVC fault .........................................................99198084028 SSCOP signaling link is broken.......................... 100198084029 SSCOP transmission buffer is overflow............... 101198084030 SCTP associate association is interrupted ........... 101198084031 SCTP associate stream buffer is congestion ......... 102198084032 SCTP associate network is congestion................ 103198084230 Ir link LCV(line code violation) alarm ................. 103198084271 Ethernet light and electricity lose ...................... 104198084305 Heat exchanger’s communication data lostalarm............................................................................. 104



198084015 STM-1 opticalsignals are lost.


� Description: STM-1 optical signals are lost.

� Severity: Major

� Alarm Type: Communications Alarm

Probable Cause 1. Receiving optical fiber is abnormal.2. Peer-end optical port is fault.3. Local-end optical port is fault.4. Transmission BER (Bit Error Rate) is too high.

1. 2.34.

System Impact 1. Board Status: Board operation is normal.2. Service Impact: The receiving direction of the fiber link is in-

terrupted, resulting in interruption of the service on this fiberlink.

HandlingSuggestion

1. Check if fiber connection is abnormal.

Check if receiving and transmitting fibers are reversely con-nected. If positive, reconnect fibers according to correct re-ceiving and transmitting direction; Check if the alarm is recov-ered.

2. Check and clear fiber abnormality.

Check and clear fiber abnormality, check if the alarm is recov-ered.

3. Check if local optical interface module is abnormal.

Check if local optical interface module is abnormal. If positive,handle the fault on the local optical interface board; Check ifthe alarm is recovered.

Caution:

Setting the fault optical interface to work in loop back modecannot remove this alarm.

4. Replace optical interface board.

Replace optical interface board; Wait for 2 minutes; When theboard runs normally, check if the alarm is recovered.

Caution:

Replacing optical interface board will cause interruption of allservices carried on the boardtherefore, please choose appro-priate time to replace it.

5. Check if the peer-end fiber link is abnormal.


Chapter 3 Communication Alarm

i. Remote device fault? Please remove the fault of peer-enddevice.

ii. Optical fiber fault? Please ask your customer for help tosolve the optical transmission problem.

198084016 STM-1 losesframe synchronization


� Description: STM-1 loses frame synchronization

� Severity: Major


Probable Cause 1. Receiving optical fiber is abnormal.2. Peer-end optical port is fault.3. Local-end optical port is fault.4. Transmission BER (Bit Error Rate) is too high.5. Transmission clock is abnormal.



HandlingSuggestion

1. Check if local optical interface board has LOS alarm.

Check if the corresponding optical interface board has LOSalarm. If positive, according to suggestions for LOS alarm,try to remove this alarm. Check if current alarm is recovered.

2. Check if the optical interface board has clock alarm.

Check if the corresponding optical interface board has trans-mission clock alarm. If positive, according to suggestions fortransmission clock alarm on optical interface board, try to re-move this alarm.


i. Check if local optical interface module is abnormal. If posi-tive, process the abnormity of local optical interface board;Check if current alarm is recovered.

ii. Replace optical interface board. Wait until the board hasfinished booting. Check if the alarm is recovered.

Caution:


4. Check if RNC or transport device clock status is normal.



Try to remove RNC or transport device clock fault, and checkif the alarm is recovered.

198084017 STM-1 MSAIS(MS Alarm Indicator Signal)


� Description: STM-1 MSAIS (MS Alarm Indicator Signal)

� Severity: Major


Probable Cause 1. Transmitting optical fiber is abnormal.2. Peer-end optical port is fault.3. Local-end optical port is fault.4. Transmission BER (Bit Error Rate) is too high.

System Impact 1. Board Status: Board operation is normal.2. Service Impact: The transmitting direction of the fiber link is

interrupted, resulting in interruption of the service on this fiberlink.

HandlingSuggestion

1. Check if fiber connection is abnormal.

Check if receiving and transmitting fibers are reversely con-nected. If positive, reconnect fibers according to correct re-ceiving and transmitting direction; Check if the alarm is recov-ered.

2. Check and clear fiber abnormality.

Check and clear the abnormality of optical fiber; Check if thealarm is recovered.


Check if local optical interface module is abnormal. If positive,process the abnormality of local optical interface board; Checkif the alarm is recovered.


Replace optical interface board. Wait until the board has fin-ished booting. Check if the alarm is recovered.

Caution:

Replacing optical interface board will cause interruption of allservices carried on the board, therefore, please choose appro-priate time to replace it.


� Remote device fault? Please remove the fault of peer-enddevice.



� Optical fiber fault ? Please ask your customer for help tosolve the optical transmission problem.

198084018 STM-1 AU4 lossof pointer


� Description: STM-1 AU4 loss of pointer

� Severity: Major


Probable Cause 1. Receiving optical fiber is abnormal.2. Peer-end optical port is fault.3. Local-end optical port is fault.4. Transmission BER (Bit Error Rate) is too high.5. Transmission clock is not synchronous.6. The STM–1 frame structure is wrong.



HandlingSuggestion

1. Check if local optical interface board has relevant alarm

Check if the associated optical interface board has LOS or LOFalarm. If positive, according to relevant suggestions for thesealarms, try to remove these alarms. Check if current alarm isrecovered.

2. Check if the optical interface board has clock alarm.

Check if the associated optical interface board has transmissionclock alarm. If positive, according to suggestions for transmis-sion clock alarm on optical interface board, try to remove thisalarm. Check if current alarm is recovered.


Check if local optical interface module is abnormal. If positive,process the abnormality of local optical interface board. Checkif current alarm is recovered.


Replace optical interface board. Wait until the board has fin-ished booting. Check if the alarm is recovered.



Caution:



Try to remove RNC or transport device clock fault, and checkif the alarm is recovered.


i. Remote device fault ? Please remove the fault of peer-enddevice.

ii. Optical fiber fault ? Please ask your customer for help tosolve the optical transmission problem.

198084245 Physical paramnot consistent with radioparam


� Description: Physical param not consistent with radio param



Probable Cause Parameter configuration between OMCB and OMCR is inconsistent.

System Impact 1. Board Status: Board operation is normal.2. Service Impact: New radio configuration fails to take effect.

The whole system will be unavailable after power-on startup.

HandlingSuggestion

1. Check if the parameter configuration between OMCB and OMCRis inconsistent. Main checking items include GSM-related ra-dio parameters, such as cell, carrier frequency and frequencyband, etc.

2. Reset board.

198084246 Radio paramerror


� Description: Radio param error





Probable Cause OMCR radio parameter configuration is incorrect.

System Impact 1. Board Status: Board operation is normal.2. Service Impact: Carrier frequency is unavailable.

HandlingSuggestion

1. Check the link between CC board and BSC. Ensure that the linkis normal.

2. Reset board.

198084247 Link3 of BUCsoftware not response


� Description: Link3 of BUC software not response

� Severity: Minor


Probable Cause 1. Operation of the upper layer software of baseband board isabnormal.

2. The communication link between master CC board and base-band board is down.

System Impact 1. Board Status: Board operation is normal.2. Service Impact: The corresponding UBPG board services are

interrupted.

HandlingSuggestion

1. Check if the following alarm occurs in the baseband board. Ifyes, refer to the corresponding alarm handling suggestion.

Related alarm: 198084123 Board communication link is inter-rupted.

2. Reset the entire BS.

198084248 DSP software ofBP board has no response


� Description: DSP software of BP board has no response



Probable Cause Operation of the board DSP software is abnormal.



System Impact 1. Board Status: Board operation is normal.2. Service Impact: The carrier frequency on this DSP is unavail-

able.

HandlingSuggestion

1. On NMS software management interface, update DSP soft-ware.

2. Reset board.

198084249 DBB parameterof BP board response error


� Description: DBB parameter of BP board response error

� Severity: Minor


Probable Cause 1. Operation of the board DSP software is abnormal.2. Parameter configuration error exists.

System Impact 1. Board Status: Board operation is normal.2. Service Impact: The carrier frequency on this DSP is unavail-

able.

HandlingSuggestion

1. Check if the radio parameter configuration on OMCR side iscorrect.

2. On NMS software management interface, update the boardDSP software.

3. Reset board.

198084036 SCTP streamnumber mismatch


� Description: SCTP stream number mismatch

� Severity: Major

� Alarm Type: Communication alarm

Probable Cause The number of in/out SCTP streams configured at Node B and thatconfigured at RRN are inconsistent.

System Impact The cell can be established, but subsequent NBAP process mightfail. UE access fails.

HandlingSuggestion

On NMS configuration management interface (Transmission LayerManagement in IUB Transmission (Full IP)), check the number ofin/out SCTP streams configured at Node B. Check the correspond-



ing configuration at RNC. Ensure that the configuration at bothends is consistent.

198084291 Configurationparameter of O&M Channelis wrong


� Description: Configuration parameter of O&M Channel is wrong



Probable Cause OMM Gateway IP address and Node B IP address configured atNMS might be wrong. BSC NE restores OMM Gateway IP addressand Node B IP address with backup data.

System Impact Only whole table configuration is permitted by the system. Otherservices are unavailable.

HandlingSuggestion

Configure the system with the correct whole table data. Wait forthe system to reboot. Re-access the system after reset.

198084312 E1/T1 linkconfiguration is failed


� Description: E1/T1 link configuration is failed

� Severity: Major


Probable Cause E1/T1 link configuration error leads to E1/T1 link configuration fail-ure at BSP.

System Impact E1/T1 fails to function properly, leading to failure in sending andreceiving NBAP signaling.

HandlingSuggestion

1. On NMS configuration management interface (Physical LayerManagement in IUB Transmission (Full IP)), delete the E1/T1configuration. Perform reconfiguration.




198084313 Qos bandwidthconfiguration is failed


� Description: Qos bandwidth configuration is failed

� Severity: Major


Probable Cause QoS bandwidth configuration error leads to QoS bandwidth con-figuration failure at BSP.

System Impact BSP fails to distribute bandwidth based on QoS. QoS priority can-not be guaranteed.

HandlingSuggestion

1. On NMS configuration management interface (Global PortLayer Management in IUB Transmission (Full IP)), delete theQoS configuration. Perform reconfiguration.


198084314 IP clockconfiguration is failed


� Description: IP clock configuration is failed

� Severity: Major


Probable Cause IP clock configuration is wrong.

System Impact IP clock fails to function properly. Node B fails to obtain clockinformation from RNC.

HandlingSuggestion

1. On NMS configuration management interface (IP Clock config-uration in IUB Transmission (Full IP)), check the IP clock con-figured at Node B side. Check if the IP clock configured at NodeB side and that configured at RNC side are consistent. Ensurethat the configuration at both sides is consistent.

2. On NMS configuration management interface (IP Clock con-figuration in IUB Transmission (Full IP)), delete the IP clockconfiguration on Node B side. Perform reconfiguration.




198084326 Physical paramnot consistant with radioparam


� Description: Physical param not consistant with radio param



Probable Cause Parameter configuration between OMCB and OMCR is inconsistent.

System Impact New radio configuration fails to take effect. The whole system willbe unavailable after power-on startup.

HandlingSuggestion

1. Check if the parameter configuration between OMCB and OMCRis inconsistent. Main checking items include GSM-related radioparameters, such as cell, carrier frequency, frequency band,etc..

2. Reset board.

198084327 Radio paramerror


� Description: Radio param error



Probable Cause OMCR radio parameter configuration is incorrect.

System Impact Carrier frequency is unavailable.

HandlingSuggestion

1. Check the link between CC board and BSC. Ensure that the linkis normal.

2. Reset board.

198084282 Lost of framenumber at optical port


� Description: Lost of frame number at optical port



� Severity: Minor


Probable Cause 1. Optical module of the board is not in place.2. Frame number loss occurs at the board optical port that is con-

nected to FS/upper-layer board.

System Impact Board communication link is down. Board services are interrupted.

HandlingSuggestion

1. Check if optical module and fiber have been installed at localboard and FS board. Ensure that optical module and fiber havebeen installed.

2. Replace the optical module/fiber of FS board. Replace the op-tical module used by the faulty optical port.

198084283 Lost of framerate and frame number


� Description: Lost of frame rate and frame number

� Severity: Minor


Probable Cause 1. The frame number received at the board optical interface con-nected to FS/upper-layer board is discontinuous.

2. The board optical interface connected to FS board fails to re-ceive frame frequency for 160 consecutive milliseconds.

System Impact Board communication link is down. Board services are interrupted.

HandlingSuggestion

Replace the optical module/fiber of FS board. Replace the opticalmodule used by the faulty optical port.

198084019 E1/T1 LOS(Loss Of Signal) alarm


� Description: E1/T1 LOS (Loss Of Signal) alarm

� Severity: Major


Probable Cause Hardware fault or link fault

System Impact The physical bandwidth available will decrease, which poses noimpact to the service in most cases. If signal on all link is lost,then all services will be interrupted.



HandlingSuggestion

1. Check the local E1/T1 connection.

i. Check if the E1/T1 connection is correct.

ii. Check if the local E1/T1 device is faulty.

iii. Open the physical bear window of the configuration man-agement interface and check the settings of E1/T1.

2. Check the counterpart E1/T1 connection. For the detailed pro-cedure please refer to the RNC section.


198084020 E1/T1 link lossof frame alarm


� Description: E1/T1 link loss of frame alarm

� Severity: Major


Probable Cause Hardware fault or link fault

System Impact 1. The impact to the clock: 2Mbis clock is lost if the alarm occurswith the 8th E1; the line clock is lost if the alarm occurs to allE1.

2. The impact to the Iub interface: no impact for Node B whenSTM-1 connection is used at Iub interface, the lower level NodeB might be affected. If E1 connection is used, no impact forthe ITC mode, the periodical slide code might occur to the Iubinterface after long period operation. at CTC mode.

3. The impact to the handover between Node B base station: theaccuracy of the Node B clock might degenerate and fail to meetthe 3GPP requirement and reduces the success rate of the han-dover when the Node B clock is extracted from this E1 link.

HandlingSuggestion


i. Check if the E1/T1connection is correct.







198084021 E1/T1 loss ofcell delineation alarm


� Description: E1/T1 loss of cell delineation alarm

� Severity: Major


Probable Cause 1. The E1/T1 configuration is not correct.2. The E1/T1 transmission link is improper.3. The E1/T1 transmission relay is improper.4. The counterpart equipment is improper.

System Impact 1. For the Iub interface of UNI mode (TC mode), the servicesbeard on the E1/T1 link will be interrupted. If NCP is beard onthis E1/T1 link, this Node b is not able to operate. If CCP isbeard on this E1/T1 link, and only one CCP is configured forthe Node B, this Node b is not able to operate

2. For the Iub interface of IMA mode, if there is normal othernormal E1/T1 available in the same group, then the service willnot be interrupted, but congestion due to shortened bandwidthmight occur.

3. For the E1/T1 link for cascading, the cascaded service mightbe interrupted.

HandlingSuggestion


i. Check if the E1/T1connection is correct.





198084022 E1/T1 link lossof IMA frame alarm


� Description: E1/T1 link loss of IMA frame alarm

� Severity: Major


Probable Cause 1. E1/T1 failure2. The group configuration of the IMA link is not correct3. Local IMA failure.



4. The counterpart IMA failure.5. Clock synchronization error.

System Impact This IMA link becomes out of service, ant the bandwidth of the IMAgroup of this link is decreased. Cell lost might occur if the originaltransmission bandwidth is wider than the original IMA group band-width after the removal of the faulty IMA link; if the bandwidth isnot wider, then the communication remains normal.

HandlingSuggestion

1. Check the local interfacing board for the E1/T1 alarms. Performthe recommended solution to process the possible alarms.

Related Alarms



2. Check the local interfacing board for clock associated alarms.Perform the recommended solution to process the possiblealarms.

Related Alarms



3. Check if the local IMA group is faulty.4. Check the failure with the E1/T1 relay line or the remote coun-

terpart IMA group.

198084023 E1/T1 IMA groupis not operational


� Description: E1/T1 IMA group is not operational

� Severity: Major


Probable Cause 1. E1/T1 failure2. The group configuration of the IMA link is not correct3. Local IMA failure.4. The counterpart IMA failure.

System Impact This IMA group becomes out of service, and the services beard bythis IMA group are interrupted.

HandlingSuggestion

1. Check the local interfacing board for the E1/T1 alarms. Performthe recommended solution to process the possible alarms.

Related Alarms



� 198084022 E1/T1 link loss of IMA frame alarm



2. Check the local interfacing board for clock associated alarms.Perform the recommended solution to process the possiblealarms.

Related Alarms



3. Open the physical bear window of the configuration manage-ment interface and check the settings of E1/T1.

4. Check if the local E1/T1 device is faulty.5. Check the E1/T1 trunk line to the remote end for any failure.

198084024 E1/T1 remotereceiving fault


� Description: E1/T1 remote receiving fault

� Severity: Minor


Probable Cause 1. The E1/T1 transmission link is improper.2. The E1/T1 transmission trunk line is improper.3. The remote end equipment failure4. The local end equipment failure

System Impact 1. For the Iub interface of UNI mode, the services beard on theE1/T1 link will be interrupted. If NCP is beard on this UNI link,this Node b is not able to operate. If CCP is beard on this UNIlink, and only one CCP is configured for the Node B, then thisNode B is not able to operate



HandlingSuggestion

1. Check if the E1/T1connection is correct.2. Check if the local E1/T1 device is faulty.3. Check the E1/T1 trunk line to the remote end for any failure.

198084025 E1/T1 linkself-loop


� Description: E1/T1 link self-loop



� Severity: Minor


Probable Cause Customer has set E1 link to be looped back locally or remotely.

System Impact 1. For the Iub interface of UNI mode (TC mode), the servicesbeard on the E1/T1 link will be interrupted.



HandlingSuggestion

Check whether the E1/T1 link is in self-looping status.

198084026 PVC faultAlarm Property � Alarm Code: 198084026

� Description: PVC fault

� Severity: Major


Probable Cause 1. Failure with the Iub port that bears this PVC.2. The PVC parameter configuration is incorrect.3. The remote end does not support OAM F5 loop back test.

System Impact The services provided by this PVC are interrupted.

HandlingSuggestion

1. Check the local interfacing board for IUB alarms affecting PVClink. Perform the recommended solution to process the possi-ble alarms.

Related Alarms

� 198084023 E1/T1 IMA group is not operational

� E1/T1 link loss of IMA frame alarm


2. Check for whether the configurations of VPI and VCI are correctin the AAL2 link and the AAL5 link in the transmission resourceinterface.

3. Check for whether the remote end supports OAM F5 loop backtest.

4. Perform self-loop test. If the alarm disappears, it means thefailure is with the transmission line or the remote end. Checkfor whether the failure is with the remote end equipments.




198084028 SSCOPsignaling link is broken


� Description: SSCOP signaling link is broken

� Severity: Major


Probable Cause 1. Physical link failure with the Node B for the PVC link.2. The Node B PVC parameter configuration is incorrect.3. The board failure.

System Impact The transmission of Nbap signaling and Alcap signaling might failand the services provided by this PVC might be interrupted. Ifthere is no other PVC of the same type available between RNC andNode B, the entire Node B operation will fail.

HandlingSuggestion

1. Check the Fault Management window for the correspondingalarms. Perform the recommended solution to process thealarm, if any.

Related Alarms





� 198084023 E1/T1 IMA group is not operational


� 198084026 PVC fault

2. Open the IUB Transmission(Full IP) and select Link Layer Man-agement in configuration management interface and check ifthe port no used by Node B, the bandwidth of VPI, VCI, PVCare with the parameter configured at RNC.

3. Re configure the PVC link.

i. Delete the faulty PVC link configured in the IUB Transmis-sion(Full IP) and select Link Layer Management in configu-ration management interface.

ii. Add the PVC link in the IUB Transmission(Full IP) and se-lect Link Layer Management in configuration managementinterface.

4. Use physical cable at Node end to self-loop test the remoteRNC, and check if the SSCOP alarm disappear at the RNC end.

5. Use physical cable at Node end to self-loop test the E1/T1 ca-ble, and check if the SSCOP alarm disappear at the RNC end.

6. Reset the board.7. Replace the board.8. Use physical cable at RNC end to self-loop test the local RNC,

and check if the SSCOP alarm disappear at the RNC end.9. Use physical cable at RNC end to self-loop test the remote Node

B, and check if the SSCOP alarm disappears at the Node B end.



198084029 SSCOPtransmission buffer isoverflow


� Description: SSCOP transmission buffer is overflow

� Severity: Major


Probable Cause 1. Node B clock failure.2. The link bandwidth is under-configured.3. Poor transmission quality.4. The board failure.

System Impact SSCOP discards the higher level signaling data requiring transmis-sion when transmission buffer overflow is detected. Part of thehigher level signaling data sent to RNC is lost.

HandlingSuggestion

1. Check the Fault Management window for the clock correspond-ing alarms. Perform the recommended solution to process thealarm, if any.

Related Alarms



2. Open the IUB Transmission(Full IP) and select Link Layer Man-agement in configuration management interface and check ifthe PVC bandwidth configured at Node B are with the param-eter configured at RNC.


198084030 SCTP associateassociation is interrupted


� Description: SCTP associate association is interrupted.

� Severity: Major


Probable Cause 1. The local FE parameter configuration is incorrect.2. The association parameter configuration of the local end or the

remote end is incorrect.3. The bottom layer fails to communicate with the counterpart

end.4. The board failure.



System Impact The transmission of Nbap signaling might fail and the services pro-vided by this association might be interrupted.

HandlingSuggestion

1. Check the Fault Management window for the correspondingalarms. Perform the recommended solution to process thealarm, if any.

Related Alarms

� FE loss of signal alarm

� E1/T1 loss of signal alarm

2. Open the IUB Transmission(Full IP) and select TransmissionLayer Management in configuration management interface andcheck the Node B configuration for whether the local end ad-dress, local port, remote address, remote port are consistentwith the parameters configured at RNC.

3. Re-configure SCTP association

i. Delete the faulty association in the IUB Transmission(FullIP) and select Transmission Layer Management in configu-ration management interface.

ii. Add the SCTP association in the IUB Transmission(Full IP)and select Transmission Layer Management in configurationmanagement interface.


198084031 SCTP associatestream buffer is congestion


� Description: SCTP associate stream buffer is congestion

� Severity: Major


Probable Cause The frequency of the application layer sending data to a certainstream of SCTP associate is over-high.

System Impact The NBAP signaling data will be discarded when the stream bufferis full, and the service quality drops.

HandlingSuggestion

1. Wait 15 minutes for the system to recover.2. Reset the board.3. Replace the board.



198084032 SCTP associatenetwork is congestion


� Description: SCTP associate network is congestion

� Severity: Major


Probable Cause 1. The counterpart system is overloaded and unable to respondin time.

2. Physical link failure.

System Impact The NBAP signaling interaction efficiency will drop, and continuousnetwork congestion will cause interruption to association.

HandlingSuggestion

1. Wait 15 minutes for the system to recover.2. Reset the board.3. Replace the board.

198084230 Ir link LCV(linecode violation) alarm


� Description: Ir link LCV(line code violation) alarm

� Severity: Minor


Probable Cause 1. Check the possible failure with the fiber optics and the opticalmodule between the local board and the higher level board.

2. The fiber damage between the boards.

System Impact Bit error might occur to the signaling tracing and the IQ, whichmay decrease the service quality or cause interruption the servicein extreme conditions.

HandlingSuggestion

1. Check the possible failure with the fiber optics and the opticalmodule between the local board and the higher level board.

i. Check the detailed information of this alarm on the faultmanagement interface. The detailed information of thealarm presents the detailed information of defective opticalport.

In the case of optical port 0 alarm, check the connection ofthe fiber optics and the optical module between the localRRU and the higher level board. Reconnect the fiber andthe module if any insecure connection is found.

In the case of optical port 1 alarm, check the connection ofthe fiber optics and the optical module between the local



RRU and the lower level RRU. Reconnect the fiber and themodule if any insecure connection is found.

ii. Replace the fiber optics.

2. Check the fiber optics between the boards for possible damage.Replace the fiber if any damage is found.

198084271 Ethernet lightand electricity lose


� Description: Ethernet light and electricity lose

� Severity: Major


Probable Cause 1. Net cable failure2. The opposite net port is faulty.3. The local net port is faulty.

System Impact The net port data transmission is interrupted, and the service isnot available.

HandlingSuggestion

1. Check the net cable for any failure

i. Check the local net cable and the counterpart net cable andensure the network connection is firm and secure.

ii. Replacing the net cable. Use proper 1000M net cable if1000m net port is adopted.

2. Check the counterpart net port for any failure.

Connect the counterpart net port with another net port with agood net cable. If the network connection is normal, then thefailure is with the local net port; if the network connection fails,then the failure is with the counterpart net port. Try connectingthe base station later when the counterpart net port is ok.

3. Check the local net port for any failure.

Reset the board.

198084305 Heatexchanger’s communicationdata lost alarm


� Description: Heat exchanger’s communication data lost alarm



� Severity: Minor


Probable Cause 1. The heat exchanger is not turned on.2. The 485 wire between heat exchanger and SA is absent.3. The 485 wire is connected to the 232 port of SA.4. Heat exchanger operation failure.

System Impact The data enquiry and alarm report of heat exchanger is affectedand no impact on the services may result.

HandlingSuggestion

1. Turn on the heat exchanger.2. Check the wire between heat exchanger and SA to secure the

connection.3. Replace the heat exchanger.



This page is intentionally blank.


C h a p t e r 4

Processing Alarm

Table of Contents198084135 Database load fail ........................................... 108198084250 IQ Config Failed.............................................. 109198084251 IPTB Setup Link Failed..................................... 109198084252 Require Radio Param timeout for times .............. 110198084253 Control face Emac Interface Error ..................... 110198084254 User face Emac Interface Error ......................... 111198084280 Write MDB and DBS failure............................... 111198084281 Failed to allocate physical logic ......................... 112198084292 AD9516 unlock alarm ...................................... 112198084319 License alarm due to authority limit................... 113198084320 License alarm due to not being activated ........... 113198084321 Physical parameters synchronization is fail-ure ................................................................................ 114198084268 IQ delay compensation value exceeds limita-tion ............................................................................... 114198084107 Board parameter synchronization abnor-mity .............................................................................. 115198084108 Board wrong insertion alarm ............................ 115198084109 SNTP time adjustment failure alarm .................. 116198084110 Running software version synchronization fail-ure ................................................................................ 116198084111 Slave software version synchronization fail-ure ................................................................................ 117198084112 Special software version synchronization fail-ure ................................................................................ 117198084113 Running Software version fault ......................... 118198084114 Slave Software version fault ............................. 118198084115 Special Software version fault........................... 119198084116 Insufficient DOM space alarm ........................... 119198084118 Failed to set gain ............................................ 119198084119 Board configuration parameter error.................. 120198084122 CPU over loading ............................................ 120198084123 Board communication link is interrupted ............ 121198084124 Database saved on master/slave board is failedto be kept synchronous .................................................... 121198084125 Database save failure ...................................... 122198084206 Software file is not identical with the DataBaserecord............................................................................ 123198084207 Firmware file is not identical with the DataBaserecord............................................................................ 123198084315 Board reboots alarm........................................ 124198084316 Firmware version is failed to be synchro-nized ............................................................................. 124198084328 IQ Config Failed.............................................. 124198084329 IPTB Setup Link Failed..................................... 125198084330 Require Radio Param timeout for times .............. 125



198084331 Fail to write platform database ......................... 126198084332 Failed to allocate physical logic ......................... 126198084333 Physical parameter synchronization failure ......... 127198084334 Peripheral board IQ configuration failure ............ 127198084004 Clock reference source is lost ........................... 128198084006 Clock reference source is degraded ................... 130198084101 Failed to configure TC port ............................... 131198084102 Failed to configure PVC .................................... 132198084103 Failed to configure FE port ............................... 133198084104 Failed to configure OMCB channel ..................... 133198084105 Failed to configure SCTP associate..................... 134198084106 Failed to configure TSI..................................... 134198084117 Monitor alarm of application software ................ 135198084126 Failed to configure STM-1................................. 135198084128 Failed to configure channelized STM-1 ............... 136198084256 GPS receiver alarm ......................................... 136198084129 Board startup notify ........................................ 137198084227 Failed to configure IMA group ........................... 137198084228 IpVlan Configer Failed ..................................... 138198084233 Digital PA over power alarm ............................. 138198084259 UL buffer is used up ........................................ 139198084284 PM under-voltage alarm................................... 139198084285 PM over-voltage alarm..................................... 140198084130 Dry contact configuration Failed ........................ 140198084131 Node B reboot notification................................ 140198084134 Master/slave changeover alarm ........................ 141

198084135 Database loadfail


� Description: Database load fail


� Alarm Type: Processing Alarm

Probable Cause Loading database fail.

System Impact 1. Board Status: Board operation is normal.2. Service Impact:

i. If loading of R_SWPAT and R_SWCONF tables fails, allboards except CC board and transmission board will fail towork normally. The service on such boards will be down.

ii. If loading of R_TESTSW table fails, the formerly activatedrecord will stop taking effect.

iii. If loading of R_PMTASK table fails, the summarization ofperformance measurement task needs to be re-initialized.

iv. If loading of the remaining tables fails, the system impactdiffers and the specific impact is trivial.

HandlingSuggestion

Check out which table loading fails.

1. R_SWPATR_SWCONF loading fail.


Chapter 4 Processing Alarm

Download software, and test it again.

2. R_TESTSW loading fails.

Testing software again.

3. R_PMTASK loading fails.

Originating the task of statistical performance measurementagain.

198084250 IQ Config FailedAlarm Property � Alarm Code: 198084250

� Description: IQ Config Failed



Probable Cause 1. Database access error occurs.2. Software is abnormal during creation of binding relationship.3. Baseband resource is insufficient.4. Sending of IQ configuration request fails.5. Physical logic distributed by MDB is wrong.

System Impact 1. Board Status: Board operation is normal.2. Service Impact: The carrier frequency whose configuration

fails is unavailable.

HandlingSuggestion

1. Check if baseband resource are sufficient. If insufficient, checkif UBPG configuration is proper.

2. Reset board.

198084251 IPTB Setup LinkFailed


� Description: IPTB Setup Link Failed



Probable Cause 1. SCTP link is unstable.2. Software is faulty.

System Impact 1. Board Status: Board operation is normal.2. Service Impact: Voice channel is unavailable.



HandlingSuggestion

1. Check if SCTP link is stable.2. Reset board.

198084252 Require RadioParam timeout for times


� Description: Require Radio Param timeout for times

� Severity: Minor


Probable Cause 1. Required parameters are unconfigured at OMCR.2. SCTP link is interrupted.

System Impact 1. Board Status: Board operation is normal.2. Service Impact: The whole system is unavailable.

HandlingSuggestion

1. Check if the configuration of GSM-related radio parameters iscorrect at OMCR.

2. On NMS configuration management interface, delete the con-figuration of carrier frequency or cell. Perform parameter re-configuration.

3. Reset board.

198084253 Control faceEmac Interface Error


� Description: Control face Emac Interface Error



Probable Cause Packet loss at EMAC interface.

System Impact 1. Board Status: Board operation is normal.2. Service Impact: The carrier frequency of the faulty board is

unavailable.

HandlingSuggestion




198084254 User face EmacInterface Error


� Description: User face Emac Interface Error



Probable Cause 1. Transmission is faulty.2. Microcode processing error exists.

System Impact 1. Board Status: Board operation is normal.2. Service Impact: Silence fault occurs in both directions.

HandlingSuggestion

1. Check the transmission link between CC board and BSC. Ensurethat SCTP association is normal and no link interruption exists.


198084280 Write MDB andDBS failure


� Description: Write MDB and DBS failure



Probable Cause Database operation error.

System Impact 1. Board Status: Board operation is normal.2. Service Impact: Fail to write to database platform and the

database platform is empty. The LMT\OMCB display is influ-enced, the GSM service is not influenced.

HandlingSuggestion

1. Check and ensure the normal operation of the CC and the BSCtransmission link.




198084281 Failed to allocatephysical logic


� Description: Failed to allocate physical logic



Probable Cause The RF resource is insufficient during OMCB configuration.

System Impact 1. Board Status: Board operation is normal.2. Service Impact: The carrier frequency not successfully dis-

tributed is not able to perform service. If it is in the systemstarting process, all the services fail to start.

HandlingSuggestion

1. Check whether the radio parameter configurations of OMCRand OMCB are consistent, including the GSM related cell, car-rier frequency, frequency band etc.

2. Reset the CC board.

198084292 AD9516 unlockalarm


� Description: AD9516 unlock alarm



Probable Cause 1. AIF GTP 122.88M clock loss occurs.2. Loss of lock occurs to AD9516.

System Impact 1. Board Status: The board is faulty.2. Service Impact: Baseband board automatically resets. All ser-

vices are interrupted.

HandlingSuggestion

1. Wait for automatic board reset.2. If the alarm persists after the board resets three times, replace

board.



198084319 License alarmdue to authority limit


� Description: License alarm due to authority limit



Probable Cause System configuration exceeds corresponding maximum grantedLicense.

System Impact 1. Board Status: work normally.2. Service Impact: The corresponding function is provided ac-

cording to maximum granted license so that service may notbe affected.

HandlingSuggestion

Increase the maximum granted License, and then update licensefile from License control center. Check if the alarm is recovered.

198084320 License alarmdue to not being activated


� Description: License alarm due to not being activated



Probable Cause 1. License file doesn’t exist.2. License file exists but the license is illegal.

System Impact 1. Board Status: work normally.2. Service impact: Base Station runs under minimum granted

License. The service is affected from the following aspects:

� Situation 1: single cell;

� Situation 2: 16 UL CEs and 16 DL CEs;

� Situation 3: PA power 20W;

� Situation 4: other License control function is unavailable.



HandlingSuggestion

Dispatch or update correct License file from License control center.Check if the alarm is recovered.

198084321 Physicalparameters synchronizationis failure


� Description: Physical parameters synchronization is failure



Probable Cause The UBPG board of GSM is not configured in the net manager.

System Impact 1. Board status: Singble board is normal.2. Influence on service: The system fails to work.

HandlingSuggestion

If the current mode is GSM single mode or GW dual mode, config-ure the UBPG board at the configuration management interface;otherwise change the mode to W single mode.

198084268 IQ delaycompensation valueexceeds limitation


� Description: IQ delay compensation value exceeds limitation

� Severity: Minor

� Alarm Type: Processing alarm

Probable Cause

Note:

A refers to the fiber distance between BBU and the furthest RRU.B refers to the fiber distance between BBU and the nearest RRU.

1. In OTSR cell (low frequency carrier or medium frequency car-rier), A is longer than B by more than 56 km.

2. In OTSR cell (low frequency carrier or medium frequency car-rier), A is longer than B by more than 28 km.



System Impact Near the RRU where the alarm is declared, there is not signal cov-erage. Service coverage area shrinks.

HandlingSuggestion

1. On NMS configuration management interface, modify topologystructure in such a way that the distance difference between Aand B is within the accepted range.

2. Relocate RRU to make the RRU fiber distance within the ac-cepted range.

198084107 Board parametersynchronization abnormity


� Description: Board parameter synchronization abnormity

� Severity: Major


Probable Cause 1. The board is not inserted.2. Board link is interrupted.

System Impact The board fails to work based on the reconfigured parameters.Board services are down.

HandlingSuggestion

1. Ensure that the board is inserted in place.2. Reset board.

198084108 Board wronginsertion alarm


� Description: Board wrong insertion alarm

� Severity: Major


Probable Cause The configured board type is inconsistent with the type of boardon rack.

System Impact Board resets repeatedly. Board services are interrupted.



HandlingSuggestion

Ensure that the configured board type and the type of board onrack are consistent.

198084109 SNTP timeadjustment failure alarm


� Description: SNTP time adjustment failure alarm

� Severity: Minor


Probable Cause 1. IP address configuration for SNTP time adjustment server iswrong.

2. SNTP server is faulty.3. Network problem exists.

System Impact System time is inaccurate, but service is not affected.

HandlingSuggestion

1. On NMS configuration management interface (BS equipmentresource management), perform SNTP time adjustment.

2. On NMS configuration management interface, check if the con-figuration of SNTP server IP address is correct.

3. End the “Windows Time” service of SNTP server. Modify theservice startup mode to manual startup.

4. Shut down Windows firewall at SNTP server.5. Check the network quality between NE and SNTP server.

198084110 Runningsoftware versionsynchronization failure


� Description: Running software version synchronization failure

� Severity: Major


Probable Cause 1. Software version of CC board is wrong.2. Hard disk space of slave CC board is insufficient.3. Slave CC board is faulty.

System Impact 1. Board Status

The board is faulty.

2. Service Impact



� Master/Slave switching does not occur.

The service is not affected, but system reliability is affected,which means that master/slave switching function is dis-abled.

� Master/Slave switching occurs.

Software-related board might function improperly. Boardservices might be interrupted.

HandlingSuggestion

1. Delete the special software version that has not been test-ac-tivated on slave CC board.

2. On NMS software management interface, download the properspecial software version.

3. Replace board.

198084111 Slave softwareversion synchronizationfailure


� Description: Slave software version synchronization failure

� Severity: Minor




HandlingSuggestion



3. Replace board.

198084112 Special softwareversion synchronizationfailure


� Description: Special software version synchronization failure

� Severity: Minor






HandlingSuggestion



3. Replace board.

198084113 RunningSoftware version fault


� Description: Running Software version fault

� Severity: Major


Probable Cause 1. Running software is damaged.2. After downloading running software version package, add con-

figuration of the board that corresponds to the software.

System Impact Board functions improperly, and board services are down.

HandlingSuggestion

On NMS software management interface, download the properversion package.

198084114 Slave Softwareversion fault


� Description: Slave Software version fault

� Severity: Minor


Probable Cause Slave software version file is damaged.


HandlingSuggestion

On NMS software management interface, download the properversion package.



198084115 Special Softwareversion fault


� Description: Special Software version fault

� Severity: Minor


Probable Cause The special software version file in the hard disk of master CCboard is damaged.

System Impact � If the software is not test-activated, service will not be af-fected.

� The board whose software has been test-activated fails to workproperly. Board services are down.

HandlingSuggestion

On NMS software management interface, re-download specialsoftware version package.

198084116 Insufficient DOMspace alarm


� Description: Insufficient DOM space alarm

� Severity: Major


Probable Cause There is no available DOM (Disk on Module) space.


HandlingSuggestion

1. On NMS software management interface, delete slave versionpackage file.

2. On NMS software management interface, delete the specialsoftware version file that has not been test-activated.

198084118 Failed to set gainAlarm Property � Alarm Code: 198084118

� Description: Failed to set gain

� Severity: Major




Probable Cause 1. Gain parameter configuration is wrong.2. Link interruption occurs to ATMA(ACOM) equipment.3. ATMA(ACOM) equipment is not in place.

System Impact The ATMA(ACOM) gain is inconsistent with gain parameter config-uration, leading to inaccurate RSSI value reported by NMS.

HandlingSuggestion

1. On NMS configuration management interface (tower top am-plifier configuration), check power gain configuration. If theconfiguration is incorrect, please correct the configuration.

2. Reset equipment.3. Replace equipment.

198084119 Boardconfiguration parametererror


� Description: Board configuration parameter error

� Severity: Major


Probable Cause 1. Parameter configuration does not exist.2. Parameter configuration is wrong.3. Hardware is faulty.

System Impact The board is faulty, and board services are interrupted.

HandlingSuggestion

Reset board.

198084122 CPU overloading


� Description: CPU over loading

� Severity: Major


Probable Cause The system is in traffic peak period. The traffic is heavy.

System Impact Board processing capability declines, probably leading to radio linkor service establishment failure.

HandlingSuggestion

Check if the system is in traffic peak period.

� Peak Period



It is recommended to evaluate network planning in depth andoptimize network planning.

� Non-Peak Period

198084123 Boardcommunication link isinterrupted


� Description: Board communication link is interrupted



Probable Cause 1. The board that has been configured does not exist on the rack.2. The link between this board and master CC board is faulty.

System Impact � Board is faulty.

� The board fails to communicate with the master CC board,leading to interruption of board services.

HandlingSuggestion

1. Insert the configured board into the corresponding slot of theBS.

2. Board link is interrupted. Reset board.3. Board transfer link is interrupted. Check if link interruption

alarm exists in the transfer board located between the faultyboard and master CC board. If yes, please refer to the corre-sponding alarm handling suggestion.

198084124 Databasesaved on master/slaveboard is failed to be keptsynchronous


� Description: Database saved on master/slave board is failedto be kept synchronous

� Severity: Major




Probable Cause The link between master board and slave board is congested orinterrupted, leading to timeout of data synchronization.

System Impact � Master board is faulty.

Master board will be faulty when any of the following two con-ditions are satisfied.

� Master board fails to boot properly.

� Master board database and slave board database are in-consistent.

In this case, master/slave switching will fail, affecting systemreliability.

� Master board is normal.

No impact on service.

HandlingSuggestion

Reset slave board.

198084125 Database savefailure


� Description: Database save failure

� Severity: Major


Probable Cause 1. Available DOM space is insufficient.2. DOM file system is faulty.3. DOM hardware is faulty.

System Impact � The board is faulty.

� Updated data fail to be saved. Application of the updated datafails after Node B reset, leading to service failure.

HandlingSuggestion

1. On NMS software management interface, delete slave versionpackage file.




198084206 Software fileis not identical with theDataBase record


� Description: Software file is not identical with the DataBaserecord

� Severity: Major


Probable Cause Software file does not exist, but relevant database record exists.

System Impact � When the inconsistency exists in the running version fileand the corresponding database record, the correspondingperipheral board will function improperly. Board services willbe down.

� When the inconsistency exists in the slave version file and thecorresponding database record, service will not be affected.

� When the inconsistency exists in the special version file andthe corresponding database record and the special version istest activated, the corresponding peripheral board will functionimproperly. Board services will be down.

HandlingSuggestion

On NMS software management interface, download the propersoftware version.

198084207 Firmware fileis not identical with theDataBase record


� Description: Firmware file is not identical with the DataBaserecord

� Severity: Major


Probable Cause Firmware file does not exist, or the file size is not the same withthat in the database record.

System Impact � Firmware upgrade fails.

� No impact on service.

HandlingSuggestion

On NMS software management interface, download the firmwareversion package which is consistent with that in the databaserecord.



198084315 Board rebootsalarm


� Description: Board reboots alarm

� Severity: Major


Probable Cause 1. Reset board command is issued by user.2. The board is powered on and reboots.3. Automatic board reset is caused by software error.

System Impact Board services are interrupted during board initialization.

HandlingSuggestion

The alarm will be restored after board initialization. No handlingis necessary.

198084316 Firmwareversion is failed to besynchronized


� Description: Firmware version is failed to be synchronized

� Severity: Major


Probable Cause 1. Firmware version of CC board is wrong.2. On slave CC board, DOM space is insufficient.3. Slave CC board is faulty.


HandlingSuggestion

1. Delete the special version that has not been test activated onslave CC board.

2. On software management interface, download the proper ver-sion package.

3. Replace board.

198084328 IQ Config FailedAlarm Property � Alarm Code: 198084328

� Description: IQ Config Failed



� Severity: Major


Probable Cause 1. Database access error occurs.2. Software is abnormal during creation of binding relationship.3. Baseband resource is insufficient.4. Sending of IQ configuration request fails.5. Physical logic distributed by MDB is wrong.

System Impact The carrier frequency whose configuration fails is unavailable.

HandlingSuggestion

1. Check if baseband resource are sufficient. If insufficient, checkif UBPG configuration is proper.

2. Reset board.

198084329 IPTB Setup LinkFailed


� Description: IPTB Setup Link Failed

� Severity: Minor


Probable Cause 1. SCTP link is unstable.2. Software is faulty.

System Impact Voice channel is unavailable.

HandlingSuggestion

1. Check if SCTP link is stable.2. Reset board.

198084330 Require RadioParam timeout for times


� Description: Require Radio Param timeout for times

� Severity: Minor


Probable Cause 1. Required parameters are unconfigured at OMCR.2. SCTP link is interrupted.

System Impact The whole system is unavailable.



HandlingSuggestion

1. Check if the configuration of GSM-related radio parameters iscorrect at OMCR.

2. On NMS configuration management interface, delete the con-figuration of carrier frequency or cell. Perform parameter re-configuration.

3. Reset board.

198084331 Fail to writeplatform database


� Description: Fail to write platform database

� Severity: Minor


Probable Cause Database operation error.

System Impact Failed to write platform database. Platform database is empty.There is influence on LMT\OMCB display, but GSM services are notaffected.

HandlingSuggestion

There is no influence on services so that it is unnecessary for anyoperation.

198084332 Failed to allocatephysical logic


� Description: Failed to allocate physical logic

� Severity: Major


Probable Cause The RF resource is insufficient during OMCB configuration.

System Impact The carrier frequency not successfully distributed is not able toperform service. If it is in the system starting process, all theservices fail to start.

HandlingSuggestion

1. Check whether the radio parameter configurations of OMCRand OMCB are consistent, including the GSM related cell, car-rier frequency, frequency band etc.

2. Reset the CC board.



198084333 Physicalparameter synchronizationfailure


� Description: Physical parameter synchronization failure

� Severity: Major


Probable Cause The UBPG board of GSM is not configured in the net manager.

System Impact The system fails to work.

HandlingSuggestion

If the current mode is GSM single mode or GW dual mode, config-ure the UBPG board at the configuration management interface;otherwise change the mode to W single mode.

198084334 Peripheral boardIQ configuration failure


� Description: Peripheral board IQ configuration failure

� Severity: Major


Probable Cause Either RRU or FS runs abnormally; or initialization is not complete;either RRU or FS board is not inserted, but it is configured at OMCBside; or RRU board has a hardware fault.

System Impact The unsuccessfully configured carrier is unavailable.

HandlingSuggestion

1. Check peripheral boards (especially RRU) and make sure theywork normally. Check RRU or FS configuration in configurationmanagement function and check if they are inserted or not inreality.

2. Open configuration management function to reset this board.



198084004 Clock referencesource is lost


� Description: Clock reference source is lost.

� Severity: Minor


Probable Cause 1. The configured clock reference source does not exist.2. Failure with the external reference clock or its cable.3. The board failure.

System Impact 1. Case 1: When multiple clock references are configured, selectthe available clock reference per priority sequence, and thesystem will operate normally.

2. Case 2: when all the clock references configured are lost, thesystem clock will choose to remain or return to free-run modeand the impact to the system is as below:

i. For the Iub interface: When E1 connection is used by Iubinterface, then periodical slide code might occur to the Iubinterface. When FE connection is used by Iub, then thereis no System Impact.

ii. The impact to the soft handover between Node B base sta-tion: over a long period of the alarm, the accuracy of theNode B clock might degenerate and fail to meet the 3GPPrequirement and reduces the success rate of soft handover.

HandlingSuggestion

Check the detailed information of this alarm on the fault manage-ment interface. The detailed information of the alarm presents thedetailed information of Clock reference source lost.

1. Check if an incorrect reference source is configured.

Check if an unavailable reference source is configured (such asa GPS configuration whereas no actual GPC source is availablein the system.)If yes, open the clock priority configuration inthe configuration management interface, modify the setting ofclock reference source to the actual system condition.

2. Check if the external clock reference is correct.

i. When the clock reference is a line clock and active/standbymain control board is used, reset the local board if no alarmoccurs to the corresponding board; check the E1 interfacefor any physical connection failure if a same alarm occursto the corresponding board, such as the secure connectionof each connector, the open-circuitry in the cables. Useloopback method to test the connection by directly con-necting the RX end to the TX end. If a 198084025 E1/T1link self-loop alarm occurs on the alarm monitor interfaceof the network management application, it means the linkis physically connected, otherwise means a physical con-nection failure.

ii. When the clock reference is a GPS clock and active/standbymain control board is used, replace the GPS card if no alarmoccurs to the corresponding board; check the power divider



and the cables for any physical connection failure if a samealarm occurs to the corresponding board, such as the con-nector between the GPS antenna and the GPS feeder, theconnector between the GPS jumper and the GPS feeder. Ifa lightning arrestor exists, check for any damage to it, andcheck the proper and secure connection between the SMAconnector of GPS jumper and the REF interface on the maincontrol board.

iii. When the clock reference is a BITS-2MHz clock and ac-tive/standby main control board is used, reset the maincontrol board if no alarm occurs to the correspondingboard; if a same alarm occurs to the corresponding board,check the BITS-2MHz clock connection interface for anyphysical connection failure, such as the secure connectionof each connector, the proper and secure connectionbetween the SMA connector of GPS jumper and the REFinterface on the main control board, and the operationstatus of the BITS-2MHz clock source and its output to theboard.

iv. When the clock reference is a BITS-2Mbps clock andactive/standby main control board is used, reset the maincontrol board if no alarm occurs to the correspondingboard; if a same alarm occurs to the corresponding board,check the BITS-2Mbps clock connection interface for anyphysical connection failure, such as the secure connectionof each connector, the cable, and the operation status ofthe BITS-2MHz clock source and its output to the board.Use loopback method to test the connection by directlyconnecting the RX end to the TX end. Please refer tothe case of line clock as BITS-2Mbps clock uses the 8thchannel of E1 channel.

v. When the clock reference is IP clock, check first the net ca-ble connection. If the net cable is free of damage, then pinthe server IP on the Node machine. If the ping commandfailed, check the networks configuration, including verify-ing both the IP in the configuration management interfaceand the IP ID in the router management lead to the FEport, and check if the base station clock ID on the networkmanager interface is greater than 3. If it is greater than3, delete this parameter and configure again. Check if theclock resource configuration is consistent with the param-eter of the station scheduled, with the focus on if the IP onconfiguration management interface and the IP and subnetmask code in the router management are consistent withthe schedule.

3. The board failure.

i. Reset the board.




198084006 Clock referencesource is degraded


� Description: Clock reference source is degraded.

� Severity: Minor


Probable Cause 1. The poor quality of the clock reference source.2. Failure with the cable connection.3. The board failure.

System Impact The system clock will choose free-run mode and the impact to thesystem is as below:

1. For the Iub interface: if E1 is used by Iub interface, then pe-riodical slide code might occur to the Iub interface. When FEconnection is used by Iub, then there is no System Impact.

2. The impact to the soft handover between Node B base station:over a long period of the alarm, the accuracy of the Node Bclock might degenerate and fail to meet the 3GPP requirementand reduces the success rate of soft handover.

HandlingSuggestion

Check the detailed information of this alarm on the fault manage-ment interface. The detailed information of the alarm presents thedetailed information of Clock reference source degeneration.

1. In the case of degeneration of the GPS clock integrated or ex-ternally connected.

i. Check the GPS feeder and the GPS card. Check the con-nector between the GPS antenna and the GPS feeder, theconnector between the GPS jumper and the GPS feeder. Ifa lightning arrestor exists, check for any damage to it, andcheck the proper and secure connection or the feeder forpossible damage. The proper and secure connection be-tween SMA connector of GPS jumper to the REF interfaceon the CC board.

ii. If alarms occur to both the active board and the standbyboard, check the lightning arrestor and the GPS antenna.If the connection and feeder are both normal, replace thelightning arrestor and/or the GPS antenna.

iii. Reinstall the GPS card and the antenna feeder


2. In the case of degeneration of the cascaded GPS clock

i. Check if the high level device has lock the clock. Check theclock reference output device for the clock locking status.

ii. Reinstall the cable.


3. In the case of degeneration of the BITS-2MHz clock

i. Check if the external clock reference is correct.

ii. Reinstall the cable.




4. In the case of degeneration of the BITS-2MBps clock

i. Check whether the clock reference is normal. Check theclock reference output device for the clock locking status.

ii. Check whether the transmission is normal.

iii. Reinstall the cable.


5. In the case of degeneration of the line clock on local board.

i. Check if the external clock reference is correct. Check theclock reference output device for the clock locking status.

ii. Check if the synchronization networks is normal. Check ifthe external transmission equipment is properly wired andconfigured.



v. Contac transmission engineer to check for possible failurewith the external transmission equipment.

6. In the case of degeneration of the line clock on other board orthe IEEE1588 clock.

i. Check if the external clock reference is correct. Check theclock reference output device for the clock locking status.

ii. Check if the synchronization networks is normal. Check ifthe external transmission equipment is properly wired andconfigured.



v. Contac transmission engineer to check for possible failurewith the external transmission equipment.

198084101 Failed toconfigure TC port


� Description: Failed to configure TC port

� Severity: Major


Probable Cause The TC parameter configuration is wrong.

System Impact The TC port is out of normal operation.

1. If this TC port is used to bear signaling link, then the corre-sponding signaling link is disconnected.



� For NCP link, the cell fails to set up.

� For CCP link, user access is impaired.

2. If this TC port is used to bear user data, then the user accessis impaired.

HandlingSuggestion

1. Open the IUB Transmission(Full IP) and select Physical LayerManagement in configuration management interface and checkif the E1 link ID of TC is configured.

2. Delete the TC data configured in the IUB Transmission(Full IP)and select IP/Static Router Layer Management in configurationmanagement interface, set up another configuration.


198084102 Failed toconfigure PVC


� Description: Failed to configure PVC

� Severity: Major


Probable Cause The PVC parameter configuration is wrong.

System Impact The PVC link is out of normal operation.

1. If this PVC link is used to bear signaling link, then the corre-sponding signaling link is disconnected.

� For NCP link, the cell fails to set up.

� For CCP link, user access is impaired.

2. If this PVC link is used to bear user data, then the user accessis impaired.

HandlingSuggestion

1. Open the IUB Transmission(Full IP) and select Link Layer Man-agement in configuration management interface and check ifthe PVC parameter used by the Node B is consistent with thePVC parameter configured at the RNC.

2. Delete the PVC parameter configured in the IUB Transmis-sion(Full IP) and select Link Layer Management in configurationmanagement interface, set up another configuration.




198084103 Failed toconfigure FE port


� Description: Failed to configure FE port

� Severity: Major


Probable Cause 1. The board is out of normal status.2. The FE parameter configuration is wrong.

System Impact � FE is out of normal operation, the SCTP association based onFE fails to work normally.

� The signaling link beard by the FE is disconnected and the cellfails to set up, and the user access fails.

HandlingSuggestion

1. Open the IUB Transmission(Full IP) and select TransmissionLayer Management in configuration management interface andcheck if the FE parameter by Node B is correct.

2. Delete the FE parameter configured in the IUB Transmis-sion(Full IP) and select Transmission Layer Management inconfiguration management interface, set up another config-uration.


198084104 Failed toconfigure OMCB channel


� Description: Failed to configure OMCB channel

� Severity: Major


Probable Cause The OMCB channel parameter configuration is wrong.

System Impact The OMC B background NM fails to access, the base station is dis-connected.

HandlingSuggestion

1. Open the IUB Transmission(Full IP) and select TransmissionLayer Management in configuration management interface andcheck if the OM gateway IP used by the Node B is consistentwith the IP configured at the RNC.

2. Delete the OMC-B parameter configured in the IUB Transmis-sion(Full IP) and select Transmission Layer Management in con-figuration management interface, set up another configuration.




198084105 Failed toconfigure SCTP associate


� Description: Failed to configure SCTP associate

� Severity: Major


Probable Cause The SCTP associate parameter configuration is incorrect.

System Impact The associate is out of normal operation and the cell fails to setup, and the user access fails.

HandlingSuggestion

1. Open the IUB Transmission(Full IP) and select TransmissionLayer Management in configuration management interface andcheck if the Node B SCTP associate parameter. Check if theparameters are consistent with the SCTP configured at RNC,including Local Port ID, Remote Port ID, Local IP, Remote IP,Traffic No. etc.

2. Delete the SCTP parameter configured in the IUB Transmis-sion(Full IP) and select Transmission Layer Management in con-figuration management interface, set up another configuration.


198084106 Failed toconfigure TSI


� Description: Failed to configure TSI

� Severity: Major


Probable Cause The TSI parameter configuration is incorrect.

System Impact When TSI is out of normal operation, the base station servicesof cross-connection based control plane and user plane might beinterrupted.

HandlingSuggestion

1. Delete the TSI parameter configured in the IUB Transmis-sion(Full IP) and select IP/Static Router Layer Management inconfiguration management interface, set up another config-uration.




198084117 Monitor alarm ofapplication software


� Description: Monitor alarm of application software



Probable Cause 1. The communication error with the main control board.2. The board parameter configuration is incorrect.3. The board software is running improperly.


HandlingSuggestion

1. Check if the board has “Board communication link is inter-rupted” alarm.

Step: Open the Fault Management interface and check if analarm “communication link is interrupted alarm” appears to thisboard.

2. Check if the board has “The board parameter configuration isincorrect” alarm.

Step: Open the Fault Management interface and check if analarm “The board parameter configuration is incorrect.” ap-pears to this board.


198084126 Failed toconfigure STM-1


� Description: Failed to configure STM-1

� Severity: Major


Probable Cause The STM-1 parameter configuration is incorrect.

System Impact STM-1 is out of normal operation.

The signaling link beard by STM-1 is disconnected and the cell failsto set up, and the user access fails.

HandlingSuggestion

1. Delete the STM-1 parameter configured in the IUB Transmis-sion(Full IP) and select Physical Layer Management in config-uration management interface, set up another configuration.Configure the parameter attribute per the network topology.

2. Reset the board.




198084128 Failed toconfigure channelizedSTM-1


� Description: Failed to configure channelized STM-1

� Severity: Major


Probable Cause Channelized STM-1 parameter configuration error

System Impact Channelized STM-1 is out of normal operation.

The signaling link beard by STM-1 is disconnected and the cell failsto set up, and the user access fails.

HandlingSuggestion

1. Delete the channelized STM-1 parameter configured in the IUBTransmission(Full IP) and select Physical Layer Managementin configuration management interface, set up another con-figuration. Configure the parameter attribute per the networktopology.


198084256 GPS receiveralarm


� Description: GPS receiver alarm

� Severity: Minor


Probable Cause 1. The antenna failure2. The GPS receiver failure.

System Impact The processing performance of the board declines, and some fea-tures do not operate normally, and the wireless link establishingmight fail in extreme conditions.

HandlingSuggestion


i. Check and ensure the GPS antenna feeder connection.

ii. Check the direction of the feeder and ensure it is free ofobstacle.



iii. Connect or replace the feeder.

2. Check the GPS receiver failure.

i. Reset the board.


198084129 Board startupnotify


� Description: Board startup notify

� Severity: Minor


Probable Cause 1. Reset board command is executed by user.2. The board is being rebooted.3. The board is rebooted by software error.

System Impact The services provided by this board are interrupted.

HandlingSuggestion

Open the fault management interface and check the history alarmof the board for cause of the board’s reset. No process is requiredif the reset is caused by the user’s operation.

198084227 Failed toconfigure IMA group


� Description: Failed to configure IMA group

� Severity: Major


Probable Cause The Iub port already exists or the parameter is wrong, both endsof IMA group parameters are not configured consistently.

System Impact The IMA group is out of normal operation.

The signaling link beard by the IMA group is disconnected and thecell fails to set up, and the user access fails.

HandlingSuggestion

1. Open the IUB Transmission(Full IP) and select Physical LayerManagement in configuration management interface and checkif the E1 link ID of IMA group is configured.

2. Delete the IMA group parameter configured in the IUB Trans-mission(Full IP) and select Layer Management in configurationmanagement interface, set up another configuration




198084228 IpVlan ConfigerFailed


� Description: Vlan Configuration Failed

� Severity: Major


Probable Cause The failure in performing Vlan parameter to the board.

System Impact Vlan is out of normal operation.

The signaling link beard by the IpVlan is disconnected and the cellfails to set up, and the user access fails.

HandlingSuggestion

1. Delete the Global Port parameter configured in the IUB Trans-mission(Full IP) and Global Port Layer Management in config-uration management interface, set up another configuration.


198084233 Digital PA overpower alarm


� Description Digital PA over power alarm

� Severity: Minor


Probable Cause 1. Error occurs with the data transmission of RRU due to exteriorintervene and system detects the digit power is 2 dbm higherthan the rated power.

2. Error occurs with the FS data transmission and system detectsthe digit power is 2 dbm higher than the rated power.

3. The BPC transmission signal of the local RRU is over high, andsystem detects the digit power is 2 dbm higher than the ratedpower.

System Impact The analog power rises with the results of power amplifier switch-ing off, deleting cell, UE disconnection, and the services providedby this RRU are interrupted.



HandlingSuggestion

1. Reset the FS connected to the physical channel of this board.2. Reset the BPC of the cell of the board.3. Reset the board.4. Replace the board.

198084259 UL buffer is usedup


� Description: UL buffer is used up



Probable Cause The UL buffer is full and unable to store new data.

System Impact 1. Impact to the board.

The board failure.

2. Impact to the service.

The system will release associated user and reset the board.

HandlingSuggestion

System will reset the board if the alarm lasts for over 10 seconds.No process is needed.

198084284 PMunder-voltage alarm


� Description: PM under-voltage alarm

� Severity: Major


Probable Cause 1. Poor connection of power cable.2. The board is damaged.

System Impact The board is out of power and the system operation becomes im-proper, the service will be interrupted.

HandlingSuggestion

1. Reconnect or replace the power cable to this board.2. Replace the board.



198084285 PM over-voltagealarm


� Description: PM over-voltage alarm

� Severity: Major


Probable Cause 1. Poor connection of power cable.2. The board is damaged.

System Impact The board is out of power and the system operation becomes im-proper, the service will be interrupted.

HandlingSuggestion

1. Reconnect or replace the power cable to this board.2. Replace the board.

198084130 Dry contactconfiguration Failed


� Description: Dry contact configuration Failed

� Severity: Minor


Probable Cause The operation of dry contact configuration failed

System Impact The dry contact will report alarm.

HandlingSuggestion

Check the dry contact configuration in the dry contact alarm con-figuration in the configuration resource management interface.


198084131 Node B rebootnotification


� Description: Node B reboot notification

� Severity: Minor




Probable Cause The base station is reset.

� The base station is reset by user.

� The base station is power interrupted and is reset.

System Impact The board reboots.

The service is not available until the reboot finishes.

HandlingSuggestion

1. No process is needed if the base station is reset by user.2. If the base station is power interrupted and reset, ensure the

normal power supply to the base station.

198084134 Master/slavechangeover alarm


� Description: Master/slave changeover alarm

� Severity: Minor


Probable Cause The changeover operation is initiated by user or it is because themaster main control board has a fault.

System Impact The changeover between the master/slave boards may cause in-terruption to the services.

HandlingSuggestion

1. No process is needed if the changeover is performed by user.2. Check the master main control board for possible failure if the

changeover is performed by the system.


C h a p t e r 5

Environment Alarm

Table of Contents198084068 Environmental temperature is high.................... 143198084069 Environmental temperature is low ..................... 144198084070 Device temperature is high .............................. 144198084071 Device temperature is low................................ 145198084072 Whole set temperature rising alarm................... 145198084077 Gate safety alarm ........................................... 145198084096 Flooded Fault ................................................. 146198084097 Smog Fault .................................................... 146

198084068 Environmentaltemperature is high


� Description: Environmental temperature is high

� Severity: Major

� Alarm Type: Environment alarm

Probable Cause 1. Dustproof net is blocked.2. Air conditioner is faulty.3. Heat exchanger is faulty.4. Configuration error exists.5. Environment Monitor Unit is faulty.

System Impact Board/System operation might become abnormal, leading todegradation of service performance, or even service interruption.

HandlingSuggestion

1. Clean dustproof net.2. Ensure that air conditioner operation is normal.3. Check if the heat exchanger is faulty. If yes, please refer to

the corresponding handling manual.4. Check environment monitoring configuration to see if the upper

limit of environment temperature is 50 degrees Celsius. If no,correct the configuration.

5. Reset SA board.6. Replace Fan module.7. Replace SA board.



198084069 Environmentaltemperature is low


� Description: Environmental temperature is low

� Severity: Major


Probable Cause 1. Temperature of the environment where the rack is located isbelow the configured lower limit of environment temperature.

2. Heat exchanger is faulty.3. Environment Monitor Unit is faulty.

System Impact The board might be damaged. System operation might becomeabnormal, leading to degradation of service performance, or evenservice interruption.

HandlingSuggestion

1. Check if the actual temperature of the environment where therack is located is too low (below -25 degrees Celsius). If yes,no handling is necessary.

2. Replace heat exchanger.3. Check environment monitoring configuration to see if the lower

limit of environment temperature is -25 degrees Celsius. If no,correct the configuration.

4. Reset SA board.5. Replace Fan module.6. Replace SA board.

198084070 Devicetemperature is high


� Description: Device temperature is high

� Severity: Major


Probable Cause 1. Dustproof net is blocked.2. Environment temperature exceeds the upper threshold.


HandlingSuggestion

1. Clean dustproof net.2. Ensure that air conditioner operation is normal.


Chapter 5 Environment Alarm

198084071 Devicetemperature is low


� Description: Device temperature is low

� Severity: Major


Probable Cause Environment temperature is below lower threshold, leading todegradation of service performance, or even service interruption.

System Impact Board/System operation might become abnormal.

HandlingSuggestion

1. Check if the actual temperature of the environment where therack is located is too low (below -25 degrees Celsius). If yes,no handling is necessary.

2. Unplug and plug SA board.3. Replace SA board.

198084072 Whole settemperature rising alarm


� Description: Whole set temperature rising alarm

� Severity: Major


Probable Cause 1. Dustproof net is blocked.2. Environment Monitor Unit is faulty.


HandlingSuggestion

1. Clean dustproof net.2. Reset SA board.3. Replace Fan module.4. Replace SA board.

198084077 Gate safetyalarm


� Description: Gate safety alarm



� Severity: Minor


Probable Cause 1. Rack door is not closed.2. Environment Monitor Unit is faulty.

System Impact The cable might be stolen or vulnerable to water inflow, leading todegradation of service performance and service interruption.

HandlingSuggestion

1. Ensure that the rack door is closed.2. Replace the sensor cable of door access control.3. Replace FCE board.

198084096 Flooded FaultAlarm Property � Alarm Code: 198084096

� Description: Flooded Fault

� Severity: Minor


Probable Cause 1. Node B is flooded.2. Environment Monitor Unit is faulty.

System Impact The board or system might fail to work properly. Board servicesmight be interrupted.

HandlingSuggestion

1. Check if Node B is flooded. If yes, power off Node B. Clear thewater away. Wait until the equipment is dry. Then power onthe equipment.

2. Replace water sensor.3. Reset FCE board.4. Replace FCE board.

198084097 Smog FaultAlarm Property � Alarm Code: 198084097

� Description: Smog Fault

� Severity: Minor


Probable Cause 1. Smog is detected by Node B.2. The fault with the environment monitoring unit.

System Impact None.

HandlingSuggestion

1. Check if there is smog in Node B.

If yes, switch off the base station and isolate the source ofsmog. Switch on the system after the smog source is removed.

2. Replace the smog sensor.


Chapter 5 Environment Alarm



C h a p t e r 6

QoS Alarm

Table of Contents198084303 Clock has significant alarm............................... 149

198084303 Clock hassignificant alarm


� Description: Clock has significant alarm.

� Severity: Major

� Alarm Type: QoS alarm

Probable Cause 1. FS Clock has a significant alarm




2. BPC clock has a significant alarm




System Impact It may decrease the service quality or cause interruption the ser-vice in the extreme conditions.

HandlingSuggestion

Check the detailed information of this alarm on the fault manage-ment interface. The detailed information of this alarm presentsthe cause of the alarm which helps to find the processing methodquickly.

The suggested process method for each alarm cause is describedbelow:

1. No processing is needed if the master main control bard isreset.

2. Hardware failure with the active main control board.

i. Reset the active main control board.

ii. Replace the master main control board.



3. Hardware failure with the local board.

i. Reset the board.



C h a p t e r 7

Notification

Table of Contents198084183 SSCOP fault ................................................... 151198084184 ALCAP link fault .............................................. 152198084185 SCTP association fault ..................................... 153198084186 Error PATHID alarm is received. ........................ 153198084188 PPP Link Recycle ............................................. 154198084189 PAP authorize failed ........................................ 154198084190 CHAP authorize failed ...................................... 155198084191 CHAP oppose authorize failed ........................... 155198084192 Alarm storm notification .................................. 155198084258 Intra-board network port error ......................... 156198084269 MAC address conflict ....................................... 156198084155 ACOM address conflict ..................................... 157198084180 E1/T1 HDB3 coding violation alarm ................... 157198084193 Cell deletion notification................................... 158198084196 ATMA device address conflict ............................ 158198084197 RET device address conflict .............................. 159198084261 The received frame number is not continu-ous................................................................................ 159198084168 Local benchmark clock is unlocked .................... 160198084170 STM-1 B1 error code alarm .............................. 161198084171 STM-1 B2 error code alarm .............................. 162198084172 STM-1 B2 FEBEI (Far End Block) ....................... 162198084173 STM-1 B3 error code alarm .............................. 163198084174 STM-1 B3 FEBEI (Far End Block Error Indicator)alarm............................................................................. 164198084175 STM-1 MSRDI (MS Remote Defect Indicator)alarm............................................................................. 165198084176 STM-1 HPRDI (High-order Path Remote Defect In-dicator) alarm................................................................. 166198084177 STM-1 HPPLM (High-order Path Payload Level Mis-match)........................................................................... 167198084178 STM-1 loss of cell delineation ........................... 168198084179 STM-1 Rx cell CRC error .................................. 168198084270 IP address conflict .......................................... 169198084338 Ir link has violated 8B10B codes ....................... 170

198084183 SSCOP faultNotificationProperty

� Notification Code: 198084183

� Description: SSCOP fault

� Importance: Ordinary



Probable Cause 1. Node B clock is faulty.2. The PVC bandwidth configured for AAL5 at Node B side is too

small.3. The transmission is of inferior quality.

System Impact NBAP and AlCAP signaling data fails to be transmitted and receivednormally. The service is interrupted.

HandlingSuggestion

1. On NMS fault management interface (Realtime Alarm Monitor),check if related alarms exist. If yes, follow the correspondingalarm handling suggestions.

Related alarms:



� 198084026 PVC fault

2. Check the configuration of PVC bandwidth.

On Base station configuration management interface manage-ment interface, choose IUB Transmission (ATM) > LinkLayer Management, and check the PVC bandwidth at localend and ensure that it is consistent with the peer end.


198084184 ALCAP link faultNotificationProperty


� Description: ALCAP link fault


Probable Cause � ALCAP link is congested.

� ALCAP message is invalid.

� ALCAP message is lack of necessary parameters.

� ALCAP message contains invalid factors.

� ALCAP timer times out.

� ALCAP message contains strange parameters.

System Impact This notification has impact on the process of establishing bearerand thus affects service access.

HandlingSuggestion

1. Check AAL2 Path status.

Do as follows:

On Base station configuration management interface manage-ment interface, choose IUB Transmission (ATM) > LinkLayer Management, and check if the AAL2 Path at local endis in blocked state. If yes, unblock it.

2. Check the Alcap protocol version configuration.


Chapter 7 Notification

Check the Alcap protocol version configured at local side andensure the configurations at both ends are consistent. If theyare inconsistent, change the Node B or RNC software version.


198084185 SCTPassociation fault



� Description: SCTP association fault


Probable Cause SCTP fails to apply for resources.

System Impact This notification has impact on association establishment and thetransmission and receipt of NBAP signaling.

HandlingSuggestion

1. Wait for 15 minutes and then check if the fault is eliminated.2. On Base station configuration management interface manage-

ment interface, choose IUB Transmission (Full IP) > Trans-mission Layer Management, and delete the SCTP associa-tion and re-configure it.


198084186 Error PATHIDalarm is received.



� Description: Error PATHID alarm is received.


Probable Cause The received PathId parameter does not exist at Node B side.

System Impact This notification has impact on the process of establishing bearerand thus affects service access.

HandlingSuggestion

1. Check AAL2 Path configuration.

Check the AAL2 Path configuration at local end and ensure thatit is consistent with the peer end.




198084188 PPP LinkRecycle



� Description: PPP Link Recycle


Probable Cause Loopback connection exists in the physical link at Iub interface.

System Impact None.

HandlingSuggestion

1. 1. Check real-time alarm information.

Do as follows:

On NMS fault management interface (Realtime Alarm Monitor),check if the related alarm exists. If yes, follow the correspond-ing handling suggestion.

Related alarm:

198084025 E1/T1 link self-loop

2. 2. Reset the board.3. 3. Replace the board.

198084189 PAP authorizefailed



� Description: PAP authorize failed


Probable Cause The authentication user name and password are wrong.

System Impact PPP link fails to be established.

HandlingSuggestion

1. Check PPP authentication parameters.

Check the PPP authentication parameters configured at localend. The authentication user name and password must beconsistent with those at peer end.




198084190 CHAP authorizefailed



� Description: CHAP authorize failed




HandlingSuggestion

1. Check PPP authentication parameters.

Check the PPP authentication parameters configured at localend. The authentication user name and password must beconsistent with those at peer end.


198084191 CHAP opposeauthorize failed



� Description: CHAP oppose authorize failed




HandlingSuggestion

1. On Base station configuration management interface manage-ment interface, choose IUB Transmission (Full IP) > GlobalPort Layer Management, and set the PPP authentication pa-rameter to Authentication Disabled.


198084192 Alarm stormnotification



� Description: Alarm storm notification




Probable Cause Alarm and alarm restoration occurs alternately.

System Impact None.

HandlingSuggestion

1. Locate the original alarm.

Do as follows:

On NMS fault management interface, view the alarm details(that is, the alarm code and subcode of the storm) of the notifi-cation to determine the original alarm causing the alarm storm.If the alarm storm restores automatically after a period of time,no handling operation is required.

2. Follow the suggestions for handling the source alarm to handlethis alarm.

198084258 Intra-boardnetwork port error



� Description: Intra-board network port error


Probable Cause DSP runs abnormally or network port is faulty. As a result, the datapackets received from DSP are not continuous and some packetsare lost.

System Impact Some DSP upper link data is lost. In most serious case, the serviceprocessing capacity is degraded.

HandlingSuggestion


198084269 MAC addressconflict



� Description: MAC address conflict


Probable Cause MAC addresses conflict.

System Impact The communication is interrupted or abnormal. All services aretotally interrupted.

HandlingSuggestion

1. Locate the two boards or hosts whose MAC addresses conflict.2. Change the MAC addresses of the conflicting boards or hosts.

Or, disconnect them from the network.3. Reset the board.




198084155 ACOM addressconflict



� Description: ACOM address conflict


Probable Cause The address of the newly connected AISG device is the same asthat of the existing one.

System Impact The service is not affected. The existing AISG device restores nor-mal communication. The newly connected device is not identified.

HandlingSuggestion

On Base station configuration management interface managementinterface, scan AISG in AISG Devices Centralized Manage-ment dialog box then add a new device.

198084180 E1/T1 HDB3coding violation alarm



� Description: E1/T1 HDB3 coding violation alarm


Probable Cause 1. E1/T1 setting is incorrect.2. E1/T1 transmission link connection is exceptional.3. E1/T1 transmission trunk has a problem.4. The peer-end device is abnormal.5. E1/T1 grounding does not meet relevant criterion.

System Impact E1/T1 link data reception is affected. Data is lost, and in mostserious case, the service carried by the link is interrupted.

HandlingSuggestion

1. Check if alarms related to E1/T1 link exists on local interfaceboard.

Related alarms:




2. Check if transmission clock alarm exists on local interfaceboard.

3. Check if local interface board is faulty.4. Check and ensure the device is correctly grounded.



5. Check and ensure the clock of RNC or transmission device is innormal state.

198084193 Cell deletionnotification



� Description: Cell deletion notification


Probable Cause 1. The local cell is faulty.2. The local cell is congested.3. RNC initiates cell deletion.

System Impact All services carried by the cell are interrupted.

HandlingSuggestion

1. Check and ensure the local cell works normally.2. Check and ensure that RNC and Node B are correctly con-

nected.

198084196 ATMA deviceaddress conflict



� Description: ATMA device address conflict


Probable Cause The address of the newly connected AISG device is the same asthat of the existing ATMA device.

System Impact The affected AISG device restores normal communication. Thenewly connected device, however, is not identified. It can be iden-tified and managed by Node B only after being scanned.

HandlingSuggestion

On Base station configuration management interface managementinterface, scan AISG in AISG Devices Centralized Manage-ment dialog box then add a new device.



198084197 RET deviceaddress conflict



� Description: RET device address conflict


Probable Cause The address of the newly connected AISG device is the same asthat of the existing RET device.

System Impact The affected AISG device restores normal communication. Thenewly connected device, however, is not identified. It can be iden-tified and managed by Node B only after being scanned.

HandlingSuggestion

On base station configuration management interface, scan AISGin AISG Devices Centralized Management dialog box then adda new device.

198084261 The receivedframe number is notcontinuous



� Description: The received frame number is not continuous


Probable Cause 1. RRU is faulty and the generated frame number is incorrect.2. FS board is faulty.3. The link between RRU and FS hardware is faulty.

System Impact Increase the BER of uplink access users.

HandlingSuggestion

1. By referring to the topology structure, reset the RF board linkedwith the board.

2. Check and ensure that fibers, optical modules, and cables be-tween the board and its linked RF board are correctly con-nected.

3. Replace the RF board linked with the board.4. Reset the board.5. Replace the board.



198084168 Localbenchmark clock is unlocked


� Notification code: 198084168

� Description: Local benchmark clock is unlocked


Probable Cause 1. Reference source is not configured.2. Reference source is lost or degraded.

System Impact Service Impact: If Node B clock accuracy does not meet 3GPP re-quirements, it may affect the success ratio of inter-Node B handoff.

HandlingSuggestion

1. Check if clock reference source is configured.

Through O&M console, check if reference source is configured.If negative, configure clock reference source. Through O&Mconsole, configure the usable clock reference source; Check ifthe alarm is recovered.

2. Check if clock reference source is normal.

Check if there is clock reference source lost or degradationalarm. If positive, according to relevant suggestions for clockreference source alarm, try to remove the alarm. Check if theclock lost alarm on the board is recovered.

3. Reset fault board.

Reset the fault board; Wait until the board runs normally;Check if the alarm is recovered.

Caution:

Resetting the main control board will cause interruption of allservices carried by the board, therefore, please choose appro-priate time to reset it.

4. Replace fault board.

Replace the fault board; Wait until the board runs normally;Check if the alarm is recovered.



Caution:

Replacing the main control board will cause interruption of allservices carried by the board, therefore, please choose appro-priate time to replace it.

198084170 STM-1 B1 errorcode alarm



� Description: STM-1 B1 error code alarm


Probable Cause The transmission quality is deteriorated (optical signal is over-power or under-power); there is strong electromagnetic interfer-ence source near optical port; optical connector is unclean; deviceworking environment is over-temperature, etc.

System Impact Service Impact: Serious code error occurs in the receiving direc-tion of the fiber link. Service data on this fiber link might be lost.

HandlingSuggestion

1. Check if STM-1 physical link has an alarm.

Check if STM-1 physical link has an alarm. If positive, accord-ing to relevant suggestions, try to solve the alarm. Wait for 15minutes. Observe if the alarm is still reported.

2. Check if optical interface board has transmission clock alarm.

Check if optical interface board has transmission clock alarm.If positive, according to relevant suggestions for transmissionclock alarm, try to remove this alarm. Wait for 15 minutes.Observe if the alarm is still reported.


i. Check if local optical interface module is abnormal. If posi-tive, process the abnormality of local optical interface mod-ule. Observe if the alarm is still reported.

ii. Replace optical interface board. Wait until the board hasfinished booting. Observe if the alarm is still reported.


Check if RNC or transport device clock status is normal. Ifnegative, remove RNC or transport device clock fault. Observeif this alarm is still reported.










HandlingSuggestion










198084172 STM-1 B2FEBEI (Far End Block)



� Description: STM-1 B2 FEBEI (Far End Block)


Probable Cause 1. Sending fiber is abnormal.2. Peer-end optical port has a fault.3. Local optical port has a fault.



4. Transmission BER is very high.5. Transmission clock is not synchronous.

System Impact Service Impact: Code error occurs in the receiving direction of thefiber link. Service data on this fiber link might be lost.

HandlingSuggestion

















HandlingSuggestion




Check if optical interface board has transmission clock alarm.If positive, according to relevant suggestions for transmission



clock alarm, try to remove this alarm. Wait for 15 minutes.Observe if the alarm is still reported.






198084174 STM-1 B3FEBEI (Far End Block ErrorIndicator) alarm



� Description: STM-1 B3 FEBEI (Far End Block Error Indicator)alarm


Probable Cause 1. Sending fiber is abnormal.2. Peer-end optical port has a fault.3. Local optical port has a fault.4. Transmission BER is very high.5. Transmission clock is not synchronous.

System Impact Service Impact: Code error occurs in the receiving direction of thefiber link. Service data on this fiber link might be lost.

HandlingSuggestion












198084175 STM-1 MSRDI(MS Remote DefectIndicator) alarm



� Description: STM-1 MSRDI (MS Remote Defect Indicator)alarm



System Impact Service Impact: Interruption in the receiving direction of the fiberlink is detected by peer-end. The service on this fiber link mightbe down.

HandlingSuggestion




Check if optical interface board has transmission clock alarm.If positive, according to relevant suggestions for transmissionclock alarm, try to remove the alarm. Wait for 15 minutes.Observe if the alarm is still reported.


i. Check if local optical interface module is abnormal. If posi-tive, Process the abnormality of local optical interface mod-ule. Observe if the alarm is still reported.



Check if the peer-end fiber link is abnormal. Observe if thealarm is still reported.





198084176 STM-1 HPRDI(High-order Path RemoteDefect Indicator) alarm



� Description: STM-1 HPRDI (High-order Path Remote Defect In-dicator) alarm



System Impact Service Impact: Interruption in the receiving direction of the fiberlink occurs. The service on this fiber link might be down.

HandlingSuggestion














198084177 STM-1 HPPLM(High-order Path PayloadLevel Mismatch)



� Description: STM-1 HPPLM (High-order Path Payload Level Mis-match)


Probable Cause 1. Receiving fiber is abnormal2. Peer-end optical port has a fault.3. Local optical port has a fault.4. Transmission BER is very high.


HandlingSuggestion














198084178 STM-1 loss ofcell delineation



� Description: STM-1 loss of cell delineation


Probable Cause 1. Receiving fiber is abnormal.2. Peer-end optical port has a fault.3. Local optical port has a fault.4. Transmission BER is very high.


HandlingSuggestion












198084179 STM-1 Rx cellCRC error



� Description: STM-1 Rx cell CRC error




Probable Cause 1. Transmission clock is not synchronous.2. Receiving fiber is abnormal.3. Peer-end optical port has a fault.4. Local optical port has a fault.5. Transmission BER is very big.


HandlingSuggestion












198084270 IP addressconflict



� Description: IP address conflict


Probable Cause Another board/host on the network has the same IP address.

System Impact Service Impact: Communication is down or abnormal. All servicesare interrupted.

HandlingSuggestion

1. Find the board/host which has the same IP address.2. Change the conflict IP address or disconnect the board/host.3. Check if this alarm is recovered.



198084338 Ir link hasviolated 8B10B codes



� Description: Ir link has violated 8B10B codes


Probable Cause 1. The optical fiber between FS and RRU is in poor contact.2. The optical module on FS or RRU is not well connected.

System Impact Service Impact: There is no influence on service running, but thequality of communication via Ir port will be reduced.

HandlingSuggestion

1. Check the connection of optical module and optical fiber be-tween FS and RRU: is the interface loosen? If yes, pleasetightly and gently connect it.

2. Is there any damaged optical fiber? If yes, please replace itwith a good fiber when the Node B is not used.


ZXSDR BS8800 U240 Indoor UMTS Macro Node B Alarm and Notification Handling Reference.pd

Documents

Transcript of ZXSDR BS8800 U240 Indoor UMTS Macro Node B Alarm and Notification Handling Reference.pd