V2,V3 Alarms

ZXG10 iBSCBase Station Controller

Alarm Handling Reference

Version 6.20.61

ZTE CORPORATIONNO. 55, Hi-tech Road South, ShenZhen, P.R.ChinaPostcode: 518057Tel: (86) 755 26771900Fax: (86) 755 26770801URL: http://ensupport.zte.com.cnE-mail: [email protected]

LEGAL INFORMATION

Copyright © 2010 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.1 20101010 Updated to V6.20.614

R1.0 20100720 First edition

Author:Mo Shenghua

Serial Number: SJ-20100524164252-020

Content

About This Manual............................................. I

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

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

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

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

Alarm ........................................................................... 2

Alarm Property........................................................... 2

Probable Cause .......................................................... 3

System Impact........................................................... 3

Handling Suggestion ................................................... 3

Notification .................................................................... 4

Notification Property ................................................... 4

Probable Cause .......................................................... 4

System Impact........................................................... 4

Handling Suggestion ................................................... 4

Equipment Alarm...............................................5198000002 Loss of optical signal .....................................13

198000256 Ethernet link to OMC is broken. ......................15

198000518 Trunk link is used for CSU loop back test..........15

198001026 Loss of ATM Cell Synchronization over E1 Link

...........................................................................16

198001027 ATM link is down...........................................17

198001284 The phase of 8K, 16K clock, input to

backplane board, is not matched .............................17

198001285 SDH/SONET:Excessive Error Code ..................18

198001286 Input clock of board lost ................................18

198001792 Loss of SDH transmission link.........................19

198002560 Board CPU overload ......................................21

198002561 High temperature on CPU board......................21

198005121 Inter-shelf media plane links abnormal ............22

Confidential and Proprietary Information of ZTE CORPORATION I

ZXG10 iBSC Alarm Handling Reference

198005124 Capacity of TRUNK communication is

insufficient............................................................23

198005125 GE optical connection is cross connected..........24

198005376 Internal media port of board is abnormal .........25

198005381 Input clock is abnormal .................................26

198005389 CPU sub card in position is not configured in

the database.........................................................26

198005390 CPU sub card is missing from slot but is

configured in database ...........................................27

198005395 External port abnormal ..................................27

198005396 Exceptional communication on UIM board or

back plane ...........................................................28

198005399 DSP resource is unavailable............................29

198005403 Board SRAM self-check fails ...........................30

198005404 Board OCXO oven fault ..................................31

198005405 Clock board phase-lock loop work mode

abnormal..............................................................31

198005632 Hard disk usage rate exceeds threshold. .........32

198005633 OMP hard disk is faulty ..................................32

198005635 The board is not plugged firmly ......................33

198005636 SMBUS error ................................................33

198005637 Back card does not match with front

board...................................................................34

198005638 LVDS signal unlocked ....................................34

198005639 High Error Rate of Optical Interface ................35

198005640 FPGA exception ............................................36

198005641 Port Link Down .............................................36

198005643 Phase-lock loop work mode abnormal ..............37

198005644 The channel in a sub card is down...................37

198005645 Sub card abnormal .......................................38

198005646 Phase-lock loop unlocked ..............................39

198005647 High BER on E1 link ......................................40

198005648 Control plane port of backboard joining

switching chip is exceptional ..................................40

198005655 Errors detected in DSP...................................41

198005656 Input clock of subcard lost .............................41

198005657 Error of LVDS path frame detection ................42

198005658 Failure in diagnosing link loop back of large T

network ...............................................................43

II Confidential and Proprietary Information of ZTE CORPORATION

198005660 Physical link down between master port and

slave port .............................................................43

198005661 Physical link down between media interface

ports....................................................................44

198005662 IDE running overtime ....................................44

198005663 Component fault ...........................................45

198005665 Fault on board (GPS) ....................................45

198005667 E1 is looped back..........................................46

198005668 Cross-linked E1 alarm ...................................47

198005669 Synchronization status check of FPGA

failed ...................................................................48

198005671 Sending or receiving packets using the

cascade ports inner board failed ..............................48

198005893 Memory check failed .....................................49

198006400 Cx29704 runs abnormally ..............................49

198015874 Data traffic to PSN board is congested .............50

198015875 GLI table lookup failed...................................50

198015876 GLI exception packets statistic over

threshold..............................................................51

198015877 GLIQV SRAM/DRAM error...............................51

198019456 All high-speed links between line card and

switching boards are out of synchronization ..............52

198019465 CSIX RX and TX packets is abnormal ...............53

198019712 APS channel mismatched ...............................53

198019713 APS mode mismatched ..................................54

198019714 APS configuration alarm.................................55

198019715 MS APS channel gets errors............................56

198019968 No response to request L2 Forwarding Table

information from DBS. ...........................................57

198019969 No response to request L2 Forwarding Table

port information from SCS. .....................................57

198019970 Resource board can't get L2 Forwarding

Table. ..................................................................59

198025601 TSNB internal connection chip fault .................59

198025602 TDM switch abnormal ....................................60

198026116 PP2S output clock lost ...................................60

198026117 PP2S clock reference lost ...............................61

198026118 16CHIP clock reference lost............................61

198026127 Loss of Level 3 reference source clock .............62

198026128 Loss of Level2 reference source clock .............62

Confidential and Proprietary Information of ZTE CORPORATION III


198026129 Loss of Level1 reference source clock ..............63

198026131 CLKG board PLL is unlocked. Clock will drift

...........................................................................64

198026133 Output clock lost...........................................64

198028672 80g chip abnormal ........................................65

198029952 802.3ah link fault .........................................65

198030208 Fault alarm of CFM........................................66

198066033 T-net center is fault ......................................67

198066038 The version of the EPU does not accord with

that of the RPU .....................................................67

198066070 Board offline or CPU in reset status for a long

period ..................................................................68

198087000 Dry contact alarm 1 ......................................68









198087009 Dry contact alarm 10.....................................72



198087012 EAM dry contact 1 alarm ...............................73

198087013 EAM dry contact 2 alarm................................73







198087100 CMM/CMB FLASH programming failure.............76

198087101 HW link broken.............................................77

198087102 Power overvoltage/undervoltage alarm ............77

198087103 13M input clock failure...................................77

198087104 Frame No. inconsistent between software and

hardware..............................................................78

198087105 FCLK clock failure .........................................78

198087106 SYNCLK clock failure .....................................79

IV Confidential and Proprietary Information of ZTE CORPORATION

198087107 Master and slave communication link

failure ..................................................................79

198087108 Standby CMM/CMB board is not in

position................................................................80

198087109 Standby CMM/CMB board abnormal.................80

198087110 CMM/CMB board has powered off. ...................81

198087111 Master rack communication link alarm ............81

198087112 Communication link alarm between master

and slave rack (left) ..............................................82

198087113 Communication link alarm between master

and slave rack (right) ............................................82

198087114 A interface E1 recieves TRX alarm...................83

198087115 A interface E1 reciever out of frame alarm .........83

198087116 A interface E1 sender forward-bit-slip

indication .............................................................84

198087117 A interface E1 sender backward-bit-slip

indication .............................................................85

198087118 A interface E1 reciever forward-bit-slip

indication .............................................................85

198087119 A interface E1 reciever backward-bit-slip

indication .............................................................86

198087120 A interface E1 remote alarm...........................86

198087121 B interface E1 recieves TRX alarm...................87

198087122 B interface E1 reciever out of frame alarm .........88

198087123 B interface E1 sender forward-bit-slip

indication .............................................................88

198087124 B interface E1 sender backward-bit-slip

indication .............................................................89

198087125 B interface E1 reciever forward-bit-slip

indication .............................................................90

198087126 B interface E1 reciever backward-bit-slip

indication .............................................................90

198087127 B interface E1 remote alarm...........................91

198087128 C interface E1 recieves TRX alarm...................91

198087129 C interface E1 reciever out of frame alarm .........92

198087130 C interface E1 sender forward-bit-slip

indication .............................................................93

198087131 C interface E1 sender backward-bit-slip

indication .............................................................93

Confidential and Proprietary Information of ZTE CORPORATION V


198087132 C interface E1 reciever forward-bit-slip

indication .............................................................94

198087133 C interface E1 reciever backward-bit-slip

indication .............................................................94

198087134 C interface E1 remote alarm...........................95

198087135 D interface E1 recieves TRX alarm...................96

198087136 D interface E1 reciever out of frame

alarm...................................................................96

198087137 D interface E1 sender forward-bit-slip

indication .............................................................97

198087138 D interface E1 sender backward-bit-slip

indication .............................................................98

198087139 D interface E1 reciever forward-bit-slip

indication .............................................................98

198087140 D interface E1 reciever backward-bit-slip

indication .............................................................99

198087141 D interface E1 remote alarm...........................99

198087142 E interface E1 recieves TRX alarm ................. 100

198087143 E interface E1 reciever out of frame

alarm................................................................. 101

198087144 E interface E1 sender forward-bit-slip

indication ........................................................... 101

198087145 E interface E1 sender backward-bit-slip

indication ........................................................... 102

198087146 E interface E1 reciever forward-bit-slip

indication ........................................................... 103

198087147 E interface E1 reciever backward-bit-slip

indication ........................................................... 103

198087148 E interface E1 remote alarm......................... 104

198087149 F interface E1 recieves TRX alarm ................. 104

198087150 F interface E1 reciever out of frame

alarm................................................................. 105

198087151 F interface E1 sender forward-bit-slip

indication ........................................................... 106

198087152 F interface E1 sender backward-bit-slip

indication ........................................................... 106

198087153 F interface E1 reciever forward-bit-slip

indication ........................................................... 107

198087154 F interface E1 reciever backward-bit-slip

indication ........................................................... 107

VI Confidential and Proprietary Information of ZTE CORPORATION

198087155 F interface E1 remote alarm ......................... 108

198087156 G interface E1 recieves TRX alarm................. 109

198087157 G interface E1 reciever out of frame

alarm................................................................. 109

198087158 G interface E1 sender forward-bit-slip

indication ........................................................... 110

198087159 G interface E1 sender backward-bit-slip

indication ........................................................... 111

198087160 G interface E1 reciever forward-bit-slip

indication ........................................................... 111

198087161 G interface E1 reciever backward-bit-slip

indication ........................................................... 112

198087162 G interface E1 remote alarm......................... 112

198087163 H interface E1 recieves TRX alarm................. 113

198087164 H interface E1 reciever out of frame

alarm................................................................. 114

198087165 H interface E1 sender forward-bit-slip

indication ........................................................... 114

198087166 H interface E1 sender backward-bit-slip

indication ........................................................... 115

198087167 H interface E1 reciever forward-bit-slip

indication ........................................................... 116

198087168 H interface E1 reciever backward-bit-slip

indication ........................................................... 116

198087169 H interface E1 remote alarm......................... 117

198087170 Temperature alarm...................................... 117

198087171 Fan not-in-position alarm............................. 118

198087172 Fan control board CPU alarm ....................... 118

198087173 Fan alarm ................................................. 118

198087174 Fan environment temperature alarm.............. 119

198087175 Fan 1 alarm ............................................... 119

198087176 Fan 2 alarm ............................................... 120

198087177 Fan controller module alarm......................... 121

198087178 Low Noise Amplifier (LNA) alarm................... 121

198087179 Tower amplifier power alarm ........................ 121

198087180 SWR of AEM HYCOM minor alarm.................. 122

198087181 SWR of AEM HYCOM major alarm.................. 122

198087182 AEM power alarm(BTS V2) ........................... 123

198087183 AEM type alarm(BTS V2).............................. 123

198087184 AEM not-in-posion alarm (BTS V2) ................ 124

Confidential and Proprietary Information of ZTE CORPORATION VII


198087185 AEM power alarm........................................ 124

198087186 LNA0 overcurrent alarm............................... 125

198087187 LNA0 overcurrent alarm............................... 125

198087188 Tower amplifier 0 overcurrent alarm .............. 126

198087189 Tower amplifier 1 overcurrent alarm .............. 126

198087190 SWR of AEM HYCOM minor alarm ................. 127

198087191 SWR of AEM HYCOM major alarm ................. 128

198087192 AEM type alarm .......................................... 128

198087193 AEM not-in-posion alarm.............................. 129

198087194 CHP DSP0 of TPU initialization failure(BTS

V2).................................................................... 130

198087195 CHP DSP1 of TPU initialization failure............. 130



198087198 Uplink ADC chip initialization failure............... 132

198087199 Uplink ADC resource unavailable ................... 132

198087200 CIP resource unavailable.............................. 132

198087201 Uplink failure.............................................. 133

198087202 TPU FLASH Memory failure(BTS V2) .............. 133

198087203 Watchdog of TPU CHP DSP0 overflow(BTS

V2).................................................................... 134

198087204 Watchdog of TPU CHP DSP1 overflow............. 134



198087207 Watchdog of FUC overflow............................ 135

198087208 Wrong configuration of TPU Channel 0 ........... 136








198087216 Cell parameter configuration mismatch

(processing error) (BTS V2) .................................. 140

198087217 Software version of FUC mismatch(BTS

V2).................................................................... 140

198087218 Software version of CHP mismatch(BTS

V2).................................................................... 141

VIII Confidential and Proprietary Information of ZTE CORPORATION

198087219 FUC has not responsed with CMM in time (BTS

V2).................................................................... 141

198087220 LAPD communication link between FUC and

BSC broken ........................................................ 142

198087221 Communication between CMM and FUC

breaks (communication) (BTS V2) ......................... 142

198087222 CIP of TPU initialization failure ...................... 143

198087223 Wrong parameter configuration for CIP .......... 144

198087224 Watchdog of TPU CIP overflow ...................... 144

198087225 Software version of CIP mismatch................. 145

198087226 Clock alarm for TPU and CMM....................... 145

198087227 TPU power alarm(BTS V2)............................ 145

198087228 TPU frame No. alarm................................... 146

198087229 TPU CHP DSP0 initialization failure ................ 146

198087230 ADC resource unavailable............................. 147

198087231 CHP frame numbers has fault. ...................... 147

198087232 BURST interruption error ............................. 148

198087233 TPU FLASH memory failure........................... 148

198087234 TPU CHP DSP0 watchdog overflow................. 149

198087235 Wrong configuration for TRX Channel 0.......... 149

198087236 Wrong configuration of TRX Channel 1 ........... 150







198087243 Cell configuration parameter mismatch .......... 154

198087244 FUC software version mismatch .................... 154

198087245 CHP software version mismatch .................... 155

198087246 CU software version mismatch...................... 155

198087247 HDLC communication link between CMB and

FUC broken......................................................... 156

198087248 LAPD communication link between FUC and

BSC broken ........................................................ 156

198087249 CU initialization failure................................. 157

198087250 CU parameter configuration error.................. 158

198087252 TPU power alarm ........................................ 158

198087253 FU frame number error alarm....................... 159

Confidential and Proprietary Information of ZTE CORPORATION IX


198087254 Rx Local Oscillator (LO) PLL1 lost lock

alarm................................................................. 159

198087255 Rx Local Oscillator (LO) PLL2 lose lock

alarm................................................................. 160

198087256 Tx Local Oscillator (LO) PLL1 lose lock

alarm................................................................. 160

198087257 Tx Local Oscillator (LO) PLL2 lose lock

alarm................................................................. 161

198087258 52M reference clock PLL lose lock alarm......... 161

198087259 Tx IF Local Oscillator (LO) PLL lose lock

alarm................................................................. 162

198087260 EEPROM resource unavailable alarm .............. 162

198087261 FPGA interface failure .................................. 163

198087262 PA VSWR alarm(BTS V2).............................. 163

198087263 PA overtemperature minor alarm(BTS V2)

......................................................................... 164

198087264 PA overtemperature major alarm(BTS

V2).................................................................... 164

198087265 PA output power alarm ................................ 165

198087266 PA power overvoltage.................................. 165

198087267 PA power is undervoltage ............................ 166

198087268 Downlink checksum error of DLRC_AL1.......... 166

198087269 DUC chip initialization failure ........................ 166

198087270 80w PA VSWR alarm ................................... 167

198087271 80w PA 's temperature is a litter high. ........... 167

198087272 80w PA overtemperature major alarm............ 168

198087273 80w PA output power alarm ......................... 168

198087274 80w PA power overvoltage ........................... 169

198087275 80w PA 's power is undervoltage . ................. 169

198087276 80w PA not-in-position alarm........................ 170

198087277 TXIF lock is lost. ......................................... 170

198087278 TPF clock is unlocked................................... 170

198087279 TXRF lost lock alarm.................................... 171

198087280 RXRF clock is unlocked . .............................. 172

198087281 13 MHz clock is lost..................................... 172

198087282 60ms synchronous clock lost alarm ............... 173

198087283 8M clock of HW is lost. ................................ 173

198087284 HW 8K synchronous signal is lost . ................ 174

198087285 RF board 52MHz clock lost alarm................... 174

198087286 First ADC clock is lost. ................................. 175

X Confidential and Proprietary Information of ZTE CORPORATION

198087287 Second ADC clock is lost. ............................. 176

198087288 PA power is overvoltage............................... 176

198087289 PA power is undervoltage............................. 177

198087290 PA VSWR alarm .......................................... 177

198087291 PA temperature is a little high. (TRX level

alarm, exceeds 80℃) ........................................... 177198087292 PA temperature is much more higher. (TRX

level alarm, exceeds 95 ℃) ................................... 178198087293 PA forward power(3db) alarm....................... 179

198087294 RTU power is abnormal................................ 179

198087295 The temperature of RTU power is too

high................................................................... 180

198087296 The output of RTU power is overvoltage. ......... 180

198087297 RTU power input abnormal alarm .................. 181

198087298 IQ calibration parameters are abnormal. ......... 181

198087299 EAM heat exchanger alarm........................... 181

198087300 CMB0 heating film alarm.............................. 182

198087301 CMB1 heating film alarm.............................. 182

198087302 EAM has had smoke . .................................. 183

198087303 EAM has had water...................................... 183

198087304 EAM lightning protection alarm. .................... 184

198087305 EAM backdoor access is intruded................... 184

198087306 EAM frontdoor access is intruded. ................. 185

198087307 EAM PWR monitoring unit has fault................ 185

198087308 FIB heating film alarm ................................. 185

198087309 EAM heat exchanger control board has

fault. ................................................................. 186

198087310 EAM heat exchanger external circulation fan 2

alarm................................................................. 186

198087311 EAM heat exchanger external circulation fan 1

alarm................................................................. 187

198087312 EAM heat exchanger internal circulation fan 2

alarm................................................................. 187

198087313 EAM heat exchanger internal circulation fan 1

alarm................................................................. 188

198087314 EAM heat exchanger 's 485 communication

has fault............................................................. 188

198087315 EAM temperature is abnormal....................... 189

198087316 EAM TRX layer mixed-flow fan 1 has

fault. ................................................................. 189

Confidential and Proprietary Information of ZTE CORPORATION XI



fault. ................................................................. 189


fault. ................................................................. 190

198087319 Communication is broken between EAM and

CMB. ................................................................. 190

198087320 Power undervoltage alarm............................ 191

198087321 Inner fan engine 2 alarm (for M8202)............ 191

198087322 Inner fan engine 1 alarm (for M8202)............ 192

198087323 Outer fan engine 2 and 4 alarm (for

M8202) .............................................................. 192

198087324 Outer fan engine 1 and 3 alarm (for

M8202) .............................................................. 193

198087325 Rack temperature minor alarm ..................... 193

198087326 Rack temperature major alarm ..................... 194

198087327 Layer 3 fan 1 alarm (for M8206) ................... 194









198087340 FR device failure ......................................... 198

198087342 Cell interruption alarm................................. 199

198087361 The CRC calibration of PA parameter turns to

be error . ........................................................... 200

198087379 OMP reboot alarm....................................... 200

198087386 SYNCLK losing lock alarm............................. 201

198087387 Status of TX1 filter alarm............................. 201




198087391 FCU power undervoltage alarm ..................... 203

198087392 FCU minor alarm ........................................ 203

198087403 ABIS-E1 transmission related clock alarm of

CCI board........................................................... 203

198087404 Local working clock alarm of CCI board.......... 204

198087405 13M clock alarm of CCI board . ..................... 204

XII Confidential and Proprietary Information of ZTE CORPORATION

198087406 CCI opposite board alarm ............................ 205

198087407 IQ FPGA internal clock alarm ........................ 205

198087408 IQ FPGA light interface alarm ...................... 205

198087409 IQ FPGA LVDS interface alarm ...................... 206

198087410 IQ FPGA internal data alarm......................... 206

198087411 13M and 61.44M clock lost alarm .................. 207

198087412 FR or FN has error....................................... 207

198087413 26MHz and 52MHz Phase Locked Loop (PLL)

lose lock alarm.................................................... 208

198087414 Detect failure alarm of uplink 60ms

hyperframe synchronization head .......................... 208

198087415 Checking block data error alarm ................... 209

198087416 Uplink LVDS SERDES lost lock alarm.............. 209

198087417 FN error alarm............................................ 209

198087432 Diversity antenna lost.................................. 210

198087433 Diversity antenna identical. .......................... 210

198087443 Diversity antenna lost alarm......................... 211

198087444 Diversity antenna identical alarm .................. 211

198087451 Board does not support 16MHW. ................... 211

198087452 CMB CPU overload alarm ............................. 212

198087453 Signalling HDLC is broken . .......................... 212

198087454 Main dimensional HDLC broken alarm ............ 213

198087455 FIB configuration exception alarm ................. 213

198087456 FIB software layer 3 no response .................. 214

198087457 FIB CPU overload alarm ............................... 214

198087458 BVC block alarm ......................................... 215

198087460 +12V voltage alarm .................................... 215

198087461 -12V voltage alarm ..................................... 216

198087462 DSP 1.2V voltage alarm............................... 216

198087463 6.4V voltage alarm...................................... 216

198087464 5V voltage alarm ........................................ 217

198087470 Fan engine not-in-position alarm................... 217

198087471 Fan engine rotation speed alarm ................... 218

198087472 CMB and FNCB RS485 link broken alarm......... 218

198087473 DTPU CPU is overloaded............................... 218



198087483 GPS signal synchronization exception ............ 219

198087484 Second pulse lost alarm............................... 220

198087485 Antenna open-circuit alarm .......................... 220

Confidential and Proprietary Information of ZTE CORPORATION XIII


198087486 Antenna short-circuit alarm.......................... 221

198087487 Lost satellite alarm...................................... 221

198087505 GUP board connection failure........................ 222

198088000 DTPU does not support baseband

freqency-hopping alarm........................................ 222

198088001 PA voltage adjusting path has broken. ........... 223

198088002 PA voltage adjusting read/write error. ............ 223

198088003 PA voltage adjusting parameter turns to be

error. ................................................................. 224

198088004 Access iBSC failure...................................... 224

198088005 Control link broken...................................... 225

198088006 Operation link broken(CS)............................ 225

198088007 Operation link broken(PS) ............................ 225

198088008 Parameter configuration mismatch ................ 226

198088009 DSP initialization failure ............................... 226

198088010 Parameter configuration failure of

AD6537.............................................................. 227

198088011 Tx PLL lost lock alarm.................................. 227

198088012 Wrong parameter configuration for

EEPROM ............................................................. 227

198088013 FLASH memory fault ................................... 228

198088014 DSP works abnormally. ................................ 228

198088015 FPGA interface fault .................................... 229

198088016 CHP frame porcessing error alarm................. 229

198088017 Wrong receive channel of RF ........................ 229

198088018 Acquiring DNS failure under dynamic

configured IP mode.............................................. 230

198088019 Analysis failure of DNS domain name ............ 230

198088020 IPSec start failure ....................................... 231

198088021 Frequency point and HTRG mismatch

alarm................................................................. 231

198088022 DHCP automatically acquiring IP address

failure ................................................................ 231

198088023 Overhigh temperature alarm ........................ 232

198088024 Voltage abnormity....................................... 232

198088025 Abis link switch alarm.................................. 233

198088027 DIP E1 rack, rack type error ......................... 233

198088028 DIP E1 rack, rack number error .................... 233

198088029 DIP E1 rack, slave rack port 1 error............... 234

198088030 DIP E1 rack, slave rack port 2 error............... 234

XIV Confidential and Proprietary Information of ZTE CORPORATION

198088031 DIP E1 rack,satellite back up flag error .......... 235

198088032 DIP E1 rack, OAM time slot error. .................. 235

198088033 DIP IP rack,access mode error(IP or

IPOE)................................................................. 236

198088034 DIP IP rack,rack number error ...................... 236

198088035 DIP IP rack,site number error ....................... 236

198088036 DIP IP rack,sequence number error ............... 237

198088037 Mains power failure alarm ............................ 237

Communication Alarm ...................................239198000519 Trunk error ................................................ 240

198000520 Trunk abnormal .......................................... 241

198001824 Abnormal status in SDH/SONET .................... 242

198001825 High BER on SDH / Sonet link....................... 246

198003841 The control plane retransfer ratio over the

threshold............................................................ 247

198005122 Loss of Active/standby communication

link.................................................................... 247

198005126 Incorrect FE Routing Connection ................... 248

198005127 FE Link Error Alarm..................................... 249

198005128 Duplicate rack and shelf............................... 249

198005378 Board HW Error .......................................... 250

198005382 Communication between power board and

OMP is abnormal ................................................. 251

198005397 Communication of RAWMACIP channel is

abnormal............................................................ 251

198005401 Test packet check abnormal ......................... 252

198005651 IP / MAC address conflict ............................. 253

198005664 The rate of error code in a mate link is high at

GUIM ................................................................. 253

198005666 The number of the error packets from MAC

port exceeds the threshold.................................... 254

198015617 Some frames Received by

FE/GE/ATM/MP/POS/E1 Port are faulty.................... 255

198015618 Faulty frames received by port over

threshold............................................................ 256

198015873 PSN board is sending out incorrect

frames ............................................................... 257

198018689 UID unavailable .......................................... 257

198019208 Timing of Near-End IMA Group Failure ........... 258

198019212 Near-End Sending Link Broken ..................... 258

Confidential and Proprietary Information of ZTE CORPORATION XV


198019213 LIF Alarm of Near-End Receiving Link ............ 259

198019214 LODS Alarm of Near-End Receiving Link ......... 259

198019215 RDI Alarm of Far End Receiving Link.............. 260

198019216 Near-End Receiving Link Faults ..................... 261

198019218 Near-End Receiving Link Broken.................... 261

198019223 Ne Group is in fault state. ............................ 262

198022784 BFD Session Interrupted .............................. 262

198029953 The Ethernet port state is OAM loop back

......................................................................... 264

198066000 Abis link broken.......................................... 264

198066003 Control plane communication is abnormal

between board and its home module ...................... 265

198066004 Control plane communication is abnormal

between MP and OMP........................................... 266

198066005 SCCP subsystem unavailable ........................ 266

198066007 Broadband link overload .............................. 267

198066008 MTP2 link sending overload ......................... 268

198066009 MTP2 link reception overload ....................... 269

198066010 MTP3 Signalling Point Inaccessible ................ 269

198066011 MTP3 link unavailable .................................. 270

198066012 MTP3 cluster inaccessible ............................. 271

198066014 M3UA Signalling Point Inaccessible ................ 271

198066015 SUA subsystem unavailable.......................... 272

198066016 SUA office inaccessible ................................ 273

198066019 Association link broken ................................ 274

198066020 STC Signalling Point Inaccessible .................. 275

198066026 Association path broken............................... 275

198066029 PPP link broken........................................... 276

198066030 BSCIP configuration error in database............ 277

198066066 AAL2 Path locally blocked............................. 278

198066067 AAL2 Path remotely blocked ......................... 278

198066068 AAL2 Path blocked by broken PVC ................. 279

198066071 Link broken for board fault ........................... 279

198087336 Rack Abis control link broken........................ 279

198087337 Site Abis control link broken ......................... 280

198087343 Front PC communication link broken

alarm................................................................. 281

198087352 NSVC failure alarm...................................... 282

198087775 super site exchanged to the satellitic ABIS

link.................................................................... 282

XVI Confidential and Proprietary Information of ZTE CORPORATION

198088026 IPOE uplink and downlink congestion

alarm................................................................. 283

Handling Alarm .............................................285198005120 T Network Connection Not Conform to

Configuration ...................................................... 286

198005123 Incorrect configuration for inserted board or

device................................................................ 286

198005387 Alarm due to inconsistent MP type................. 287

198005388 Startup file does not exist ............................ 287

198005398 Office ID is not set correctly with control

shelf .................................................................. 288

198005402 Database config is different from file named

bootcfg.ini .......................................................... 288

198005649 Port configuration is incorrect ....................... 289

198005659 Formats of audio resource inconsistent .......... 290

198005889 Version Switches While Board Doesn't

Reset ................................................................. 290

198005890 Function EPLD Update Failure ....................... 291

198005891 Inconsistent BOOT/EPLD Version No. with

Database Configurations....................................... 291

198005892 Boot Version Fails to Write to Backup

Region ............................................................... 292

198007936 Memory file buffer overflow.......................... 292

198015360 Microcode Is Abnormal ................................ 293

198018944 PVC link is down ......................................... 293

198019207 Near-End IMA Group Configuration

Failure ............................................................... 294

198020225 Protocol stack requested system configuration

information timeout ............................................. 295

198023040 Number of alarms exceeds threshold. ............ 296

198025600 Connection Check be Disabled in board.......... 296

198066006 Broadband link congestion .......................... 297

198066013 MTP3 link congestion................................... 298

198066018 Association congestion................................. 298

198066021 STC office congestion .................................. 299

198066027 SNTP failure ............................................... 299

198066031 OMP alarm pool is full, unable to store any

more alarms. ...................................................... 300

198066032 Loss of NTP time synchronisation .................. 300

198066063 MTP3 link sending flow control alarm ............. 301

Confidential and Proprietary Information of ZTE CORPORATION XVII


198087251 FUC L3 software no response

temporarily......................................................... 301

198087380 TRX manual block alarm .............................. 302

198087482 Data loading exception alarm ....................... 302

198087513 Board Ethernet port overload alarm............... 303

198087768 Resource Availability Alarm of UPPB DSP......... 303

Environment Alarm .......................................305198025856 Rack temperature is high ............................. 305

198025857 Low temperature in Rack ............................ 306

198025858 Room temperature is higher than high

threshold ........................................................... 307

198025859 Room temperature is lower than low threshold

......................................................................... 307

198025860 Rack voltage is high ................................... 308

198025861 rack voltage is low ...................................... 309

198025862 Humidity is high ......................................... 309

198025863 Humidity is low........................................... 310

198025864 Fault in fan plug-in box ............................... 310

198025865 Rack door alarm ......................................... 311

198025866 Smoke detected ......................................... 311

198025867 Infrared alarm............................................ 312

198025868 Lightning alarm .......................................... 313

198025869 Loss of DC power supply to rack ................... 313

198029184 SNTP server is unavailable ........................... 314

QoS Alarm .....................................................315198015361 Ring and queue overload alarm..................... 315

198023296 Inter-board message communication flow

rate exceeds the alarm threshold........................... 316

198066069 The number of times of signaling data transfer

exceeds the allowed threshold of the license ........... 316

198087341 FR congestion............................................. 317

198087344 MSC overload control alarm at FUC

mode................................................................. 317

198087345 CPU overload control alarm at FUC mode......... 318

198087346 Signaling point congestion control alarm at

FUC mode .......................................................... 318

198087347 MSC overload control alarm at SYS

mode................................................................. 319

198087348 CPU overload control alarm at SYS mode......... 319

XVIII Confidential and Proprietary Information of ZTE CORPORATION

198087349 Signaling point congestion control alarm at

SYS mode .......................................................... 320

198087350 CS CCCH overload ...................................... 320

198087351 PS CCCH overload....................................... 321

198087435 A interface resource statistic alarm................ 321

198087436 NSVC resource statistics alarm ..................... 322

198087437 TCH resources statistics alarm ...................... 322

198087438 Assignment failure alarm ............................. 323

198087468 LAPD congestion alarm ................................ 323

198087506 NSE block alarm ......................................... 324

198087507 SGSN is blocked. ........................................ 324

198087758 Manual User Access control alarm ................. 325

198087759 CPU overload control alarm at Paging

mode................................................................. 325

Glossary ........................................................327

Confidential and Proprietary Information of ZTE CORPORATION XIX


This page is intentionally blank.

XX Confidential and Proprietary Information of ZTE CORPORATION

About This Manual

Purpose This manual introduces the alarms that might occur during theinstallation, operation and maintenance of ZXG10 BSS product.Alarm code and description displayed by NetNumen M31 central-ized NMS, probable cause for the alarm, and the correspondinghandling suggestion are covered in this manual.

IntendedAudience

� System engineers

� Maintenance engineers

What Is in ThisManual

This manual contains the following chapters.

Chapter Summary

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

Chapter 2, Equipment Alarm Introduces BSS equipment alarmswith respect to alarm property,probable cause, system impact,and handling suggestion.

Chapter 3, Communication Alarm Introduces BSS communicationalarms with respect to alarmproperty, probable cause, systemimpact, and handling suggestion.

Chapter 4, Processing Alarm Introduces BSS processing alarmswith respect to alarm property,probable cause, system impact,and handling suggestion.

Chapter 5, Environment Alarm Introduces BSS environmentalarms with respect to alarmproperty, probable cause, systemimpact, and handling suggestion.

Chapter 6, QoS Alarm Introduces BSS QoS alarmswith respect to alarm property,probable cause, system impact,and handling suggestion.

Confidential and Proprietary Information of ZTE CORPORATION I



II Confidential and Proprietary Information of ZTE CORPORATION

C h a p t e r 1

Overview

This chapter introduces the concept of fault management, as wellas the definition, type, level classification of alarm.

Table of ContentsOverview of Fault Management............................................. 1Fault View ......................................................................... 1Alarm ............................................................................... 2Notification ........................................................................ 4

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 through a user-orientedfault monitoring platform. Means such as visual-interface moni-tor or history information query can be used to view current orhistorical system operation and service processing status. Faultmanagement enables maintenance personnel to troubleshoot andtake preventive measures to remove potential fault and restoresystem and 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.

Confidential and Proprietary Information of ZTE CORPORATION 1


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.

Notification

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

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.

AlarmAlarm Property

Alarm Code Alarm code is the identifier which differentiates alarms.

Alarm code is defined by a 32-bit field indicating the specific codevalue.

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

Severity There are four alarm levels, which are indicated in descending or-der of severity as Critical, Major, Minor, and Warning.

� Critical alarm causes system breakdown and service interrup-tion. It requires immediate troubleshooting.

� Major alarm significantly affects system operation or weakensnetwork service capability. It requires troubleshooting as soonas 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 and net-work service capability. It requires troubleshooting at an ap-propriate time so as to avoid severity escalation.

The degree of impact as described in the definition of alarm sever-ity refers to the impact of a single index, such as reliability andsecurity. Once the impact on any of the index reaches the speci-fied threshold, the severity level of the alarm can be roughly de-termined. If an alarm has an impact on multiple indices, alarmseverity should be escalated accordingly.

2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Overview

Note:

� Alarm severity can be modified in NetNumen R31 NMS (Net-work Management System) if necessary.

� The default alarm severity is reasonably set. Users shouldthink twice before making any modification.

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

Alarm Type Alarm is classified into six types according to alarm trigger condi-tion and its system impact:

� Equipment alarm: related with device hardware.

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

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

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

� QoS alarm: related with degradation of service quality (ITU-TRecommendation 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.

Handling Suggestion

Troubleshooting measures and suggestions are provided.

Pay attention to the following tips when handling alarms.

� After recording the fault phenomenon, OAM 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.

NotificationNotification Property

Notification Code Notification code is the identifier to differentiate notifications.

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

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

Importance There are two levels of notification importance: Important andOrdinary.

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.

Handling Suggestion

Troubleshooting measures and suggestions are provided.

Pay attention to the following tips when handling notifications.

� After recording the fault phenomenon, OAM 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 Contents198000002 Loss of optical signal .........................................13198000256 Ethernet link to OMC is broken. ..........................15198000518 Trunk link is used for CSU loop back test..............15198001026 Loss of ATM Cell Synchronization over E1 Link......................................................................................16198001027 ATM link is down...............................................17198001284 The phase of 8K, 16K clock, input to backplaneboard, is not matched ........................................................17198001285 SDH/SONET:Excessive Error Code ......................18198001286 Input clock of board lost ....................................18198001792 Loss of SDH transmission link.............................19198002560 Board CPU overload ..........................................21198002561 High temperature on CPU board..........................21198005121 Inter-shelf media plane links abnormal ................22198005124 Capacity of TRUNK communication is insuffi-cient ................................................................................23198005125 GE optical connection is cross connected..............24198005376 Internal media port of board is abnormal .............25198005381 Input clock is abnormal .....................................26198005389 CPU sub card in position is not configured in thedatabase ..........................................................................26198005390 CPU sub card is missing from slot but is configuredin database.......................................................................27198005395 External port abnormal......................................27198005396 Exceptional communication on UIM board or backplane ..............................................................................28198005399 DSP resource is unavailable................................29198005403 Board SRAM self-check fails ...............................30198005404 Board OCXO oven fault ......................................31198005405 Clock board phase-lock loop work mode abnor-mal .................................................................................31198005632 Hard disk usage rate exceeds threshold. .............32198005633 OMP hard disk is faulty ......................................32198005635 The board is not plugged firmly ..........................33198005636 SMBUS error ....................................................33198005637 Back card does not match with front board...........34198005638 LVDS signal unlocked ........................................34198005639 High Error Rate of Optical Interface ....................35198005640 FPGA exception ................................................36198005641 Port Link Down .................................................36198005643 Phase-lock loop work mode abnormal ..................37198005644 The channel in a sub card is down.......................37198005645 Sub card abnormal ...........................................38198005646 Phase-lock loop unlocked ..................................39198005647 High BER on E1 link ..........................................40



198005648 Control plane port of backboard joining switchingchip is exceptional ............................................................40198005655 Errors detected in DSP ......................................41198005656 Input clock of subcard lost .................................41198005657 Error of LVDS path frame detection ....................42198005658 Failure in diagnosing link loop back of large T net-work................................................................................43198005660 Physical link down between master port and slaveport .................................................................................43198005661 Physical link down between media interfaceports ...............................................................................44198005662 IDE running overtime ........................................44198005663 Component fault...............................................45198005665 Fault on board (GPS) ........................................45198005667 E1 is looped back..............................................46198005668 Cross-linked E1 alarm .......................................47198005669 Synchronization status check of FPGA failed .........48198005671 Sending or receiving packets using the cascadeports inner board failed ......................................................48198005893 Memory check failed .........................................49198006400 Cx29704 runs abnormally ..................................49198015874 Data traffic to PSN board is congested .................50198015875 GLI table lookup failed.......................................50198015876 GLI exception packets statistic over thresh-old ..................................................................................51198015877 GLIQV SRAM/DRAM error...................................51198019456 All high-speed links between line card and switch-ing boards are out of synchronization ...................................52198019465 CSIX RX and TX packets is abnormal ...................53198019712 APS channel mismatched ...................................53198019713 APS mode mismatched ......................................54198019714 APS configuration alarm.....................................55198019715 MS APS channel gets errors................................56198019968 No response to request L2 Forwarding Table in-formation from DBS...........................................................57198019969 No response to request L2 Forwarding Table portinformation from SCS.........................................................57198019970 Resource board can't get L2 Forwarding Ta-ble. .................................................................................59198025601 TSNB internal connection chip fault .....................59198025602 TDM switch abnormal ........................................60198026116 PP2S output clock lost .......................................60198026117 PP2S clock reference lost ...................................61198026118 16CHIP clock reference lost................................61198026127 Loss of Level 3 reference source clock .................62198026128 Loss of Level2 reference source clock .................62198026129 Loss of Level1 reference source clock ..................63198026131 CLKG board PLL is unlocked. Clock will drift .........64198026133 Output clock lost...............................................64198028672 80g chip abnormal ............................................65198029952 802.3ah link fault .............................................65198030208 Fault alarm of CFM............................................66198066033 T-net center is fault ..........................................67198066038 The version of the EPU does not accord with thatof the RPU........................................................................67198066070 Board offline or CPU in reset status for a longperiod..............................................................................68198087000 Dry contact alarm 1 ..........................................68198087001 Dry contact alarm 2 ..........................................69198087002 Dry contact alarm 3 ..........................................69


Chapter 2 Equipment Alarm

198087003 Dry contact alarm 4 ..........................................69198087004 Dry contact alarm 5 ..........................................70198087005 Dry contact alarm 6 ..........................................70198087006 Dry contact alarm 7 ..........................................71198087007 Dry contact alarm 8 ..........................................71198087008 Dry contact alarm 9 ..........................................71198087009 Dry contact alarm 10.........................................72198087010 Dry contact alarm 11.........................................72198087011 Dry contact alarm 12.........................................73198087012 EAM dry contact 1 alarm ...................................73198087013 EAM dry contact 2 alarm....................................73198087014 EAM dry contact 3 alarm....................................74198087015 EAM dry contact 4 alarm....................................74198087016 EAM dry contact 5 alarm....................................75198087017 EAM dry contact 6 alarm....................................75198087018 EAM dry contact 7 alarm....................................75198087019 EAM dry contact 8 alarm....................................76198087100 CMM/CMB FLASH programming failure.................76198087101 HW link broken.................................................77198087102 Power overvoltage/undervoltage alarm ................77198087103 13M input clock failure ......................................77198087104 Frame No. inconsistent between software andhardware..........................................................................78198087105 FCLK clock failure .............................................78198087106 SYNCLK clock failure .........................................79198087107 Master and slave communication link failure .........79198087108 Standby CMM/CMB board is not in position...........80198087109 Standby CMM/CMB board abnormal.....................80198087110 CMM/CMB board has powered off. .......................81198087111 Master rack communication link alarm ................81198087112 Communication link alarm between master andslave rack (left) ................................................................82198087113 Communication link alarm between master andslave rack (right) ..............................................................82198087114 A interface E1 recieves TRX alarm.......................83198087115 A interface E1 reciever out of frame alarm ...........83198087116 A interface E1 sender forward-bit-slip indica-tion .................................................................................84198087117 A interface E1 sender backward-bit-slip indica-tion .................................................................................85198087118 A interface E1 reciever forward-bit-slip indica-tion .................................................................................85198087119 A interface E1 reciever backward-bit-slip indica-tion .................................................................................86198087120 A interface E1 remote alarm...............................86198087121 B interface E1 recieves TRX alarm.......................87198087122 B interface E1 reciever out of frame alarm ...........88198087123 B interface E1 sender forward-bit-slip indica-tion .................................................................................88198087124 B interface E1 sender backward-bit-slip indica-tion .................................................................................89198087125 B interface E1 reciever forward-bit-slip indica-tion .................................................................................90198087126 B interface E1 reciever backward-bit-slip indica-tion .................................................................................90198087127 B interface E1 remote alarm...............................91198087128 C interface E1 recieves TRX alarm.......................91198087129 C interface E1 reciever out of frame alarm ...........92198087130 C interface E1 sender forward-bit-slip indica-tion .................................................................................93



198087131 C interface E1 sender backward-bit-slip indica-tion .................................................................................93198087132 C interface E1 reciever forward-bit-slip indica-tion .................................................................................94198087133 C interface E1 reciever backward-bit-slip indica-tion .................................................................................94198087134 C interface E1 remote alarm...............................95198087135 D interface E1 recieves TRX alarm.......................96198087136 D interface E1 reciever out of frame alarm ...........96198087137 D interface E1 sender forward-bit-slip indica-tion .................................................................................97198087138 D interface E1 sender backward-bit-slip indica-tion .................................................................................98198087139 D interface E1 reciever forward-bit-slip indica-tion .................................................................................98198087140 D interface E1 reciever backward-bit-slip indica-tion .................................................................................99198087141 D interface E1 remote alarm ..............................99198087142 E interface E1 recieves TRX alarm ..................... 100198087143 E interface E1 reciever out of frame alarm.......... 101198087144 E interface E1 sender forward-bit-slip indica-tion ............................................................................... 101198087145 E interface E1 sender backward-bit-slip indica-tion ............................................................................... 102198087146 E interface E1 reciever forward-bit-slip indica-tion ............................................................................... 103198087147 E interface E1 reciever backward-bit-slip indica-tion ............................................................................... 103198087148 E interface E1 remote alarm............................. 104198087149 F interface E1 recieves TRX alarm ..................... 104198087150 F interface E1 reciever out of frame alarm.......... 105198087151 F interface E1 sender forward-bit-slip indica-tion ............................................................................... 106198087152 F interface E1 sender backward-bit-slip indica-tion ............................................................................... 106198087153 F interface E1 reciever forward-bit-slip indica-tion ............................................................................... 107198087154 F interface E1 reciever backward-bit-slip indica-tion ............................................................................... 107198087155 F interface E1 remote alarm ............................. 108198087156 G interface E1 recieves TRX alarm..................... 109198087157 G interface E1 reciever out of frame alarm ......... 109198087158 G interface E1 sender forward-bit-slip indica-tion ............................................................................... 110198087159 G interface E1 sender backward-bit-slip indica-tion ............................................................................... 111198087160 G interface E1 reciever forward-bit-slip indica-tion ............................................................................... 111198087161 G interface E1 reciever backward-bit-slip indica-tion ............................................................................... 112198087162 G interface E1 remote alarm ............................ 112198087163 H interface E1 recieves TRX alarm..................... 113198087164 H interface E1 reciever out of frame alarm ......... 114198087165 H interface E1 sender forward-bit-slip indica-tion ............................................................................... 114198087166 H interface E1 sender backward-bit-slip indica-tion ............................................................................... 115198087167 H interface E1 reciever forward-bit-slip indica-tion ............................................................................... 116



198087168 H interface E1 reciever backward-bit-slip indica-tion ............................................................................... 116198087169 H interface E1 remote alarm............................. 117198087170 Temperature alarm ......................................... 117198087171 Fan not-in-position alarm................................. 118198087172 Fan control board CPU alarm ........................... 118198087173 Fan alarm ..................................................... 118198087174 Fan environment temperature alarm.................. 119198087175 Fan 1 alarm ................................................... 119198087176 Fan 2 alarm ................................................... 120198087177 Fan controller module alarm............................. 121198087178 Low Noise Amplifier (LNA) alarm....................... 121198087179 Tower amplifier power alarm ............................ 121198087180 SWR of AEM HYCOM minor alarm...................... 122198087181 SWR of AEM HYCOM major alarm...................... 122198087182 AEM power alarm(BTS V2) ............................... 123198087183 AEM type alarm(BTS V2).................................. 123198087184 AEM not-in-posion alarm (BTS V2) .................... 124198087185 AEM power alarm............................................ 124198087186 LNA0 overcurrent alarm................................... 125198087187 LNA0 overcurrent alarm................................... 125198087188 Tower amplifier 0 overcurrent alarm .................. 126198087189 Tower amplifier 1 overcurrent alarm .................. 126198087190 SWR of AEM HYCOM minor alarm ..................... 127198087191 SWR of AEM HYCOM major alarm ..................... 128198087192 AEM type alarm .............................................. 128198087193 AEM not-in-posion alarm.................................. 129198087194 CHP DSP0 of TPU initialization failure(BTSV2)................................................................................ 130198087195 CHP DSP1 of TPU initialization failure................. 130198087196 CHP DSP2 of TPU initialization failure................. 131198087197 CHP DSP3 of TPU initialization failure................. 131198087198 Uplink ADC chip initialization failure................... 132198087199 Uplink ADC resource unavailable ....................... 132198087200 CIP resource unavailable.................................. 132198087201 Uplink failure.................................................. 133198087202 TPU FLASH Memory failure(BTS V2) .................. 133198087203 Watchdog of TPU CHP DSP0 overflow(BTSV2)................................................................................ 134198087204 Watchdog of TPU CHP DSP1 overflow................. 134198087205 Watchdog of TPU CHP DSP2 overflow................. 135198087206 Watchdog of TPU CHP DSP3 overflow................. 135198087207 Watchdog of FUC overflow ............................... 135198087208 Wrong configuration of TPU Channel 0 ............... 136198087209 Wrong configuration of TPU Channel 1 ............... 136198087210 Wrong configuration of TPU Channel 2 ............... 137198087211 Wrong configuration of TPU Channel 3 ............... 137198087212 Wrong configuration of TPU Channel 4 ............... 138198087213 Wrong configuration of TPU Channel 5 ............... 138198087214 Wrong configuration of TPU Channel 6 ............... 139198087215 Wrong configuration of TPU Channel 7 ............... 139198087216 Cell parameter configuration mismatch (process-ing error) (BTS V2).......................................................... 140198087217 Software version of FUC mismatch(BTS V2) ......... 140198087218 Software version of CHP mismatch(BTS V2) ......... 141198087219 FUC has not responsed with CMM in time (BTSV2)................................................................................ 141198087220 LAPD communication link between FUC and BSCbroken ........................................................................... 142



198087221 Communication between CMM and FUC breaks(communication) (BTS V2)................................................ 142198087222 CIP of TPU initialization failure .......................... 143198087223 Wrong parameter configuration for CIP .............. 144198087224 Watchdog of TPU CIP overflow.......................... 144198087225 Software version of CIP mismatch..................... 145198087226 Clock alarm for TPU and CMM........................... 145198087227 TPU power alarm(BTS V2)................................ 145198087228 TPU frame No. alarm....................................... 146198087229 TPU CHP DSP0 initialization failure .................... 146198087230 ADC resource unavailable ................................ 147198087231 CHP frame numbers has fault. .......................... 147198087232 BURST interruption error ................................. 148198087233 TPU FLASH memory failure............................... 148198087234 TPU CHP DSP0 watchdog overflow..................... 149198087235 Wrong configuration for TRX Channel 0.............. 149198087236 Wrong configuration of TRX Channel 1 ............... 150198087237 Wrong configuration of TRX Channel 2 ............... 150198087238 Wrong configuration of TRX Channel 3 ............... 151198087239 Wrong configuration of TRX Channel 4 ............... 152198087240 Wrong configuration of TRX Channel 5 ............... 152198087241 Wrong configuration of TRX Channel 6 ............... 153198087242 Wrong configuration of TRX Channel 7 ............... 153198087243 Cell configuration parameter mismatch .............. 154198087244 FUC software version mismatch ........................ 154198087245 CHP software version mismatch ........................ 155198087246 CU software version mismatch.......................... 155198087247 HDLC communication link between CMB and FUCbroken ........................................................................... 156198087248 LAPD communication link between FUC and BSCbroken ........................................................................... 156198087249 CU initialization failure..................................... 157198087250 CU parameter configuration error...................... 158198087252 TPU power alarm ............................................ 158198087253 FU frame number error alarm........................... 159198087254 Rx Local Oscillator (LO) PLL1 lost lock alarm......... 159198087255 Rx Local Oscillator (LO) PLL2 lose lockalarm............................................................................. 160198087256 Tx Local Oscillator (LO) PLL1 lose lock alarm......... 160198087257 Tx Local Oscillator (LO) PLL2 lose lock alarm......... 161198087258 52M reference clock PLL lose lock alarm............. 161198087259 Tx IF Local Oscillator (LO) PLL lose lockalarm............................................................................. 162198087260 EEPROM resource unavailable alarm .................. 162198087261 FPGA interface failure ...................................... 163198087262 PA VSWR alarm(BTS V2).................................. 163198087263 PA overtemperature minor alarm(BTS V2) ......... 164198087264 PA overtemperature major alarm(BTS V2).......... 164198087265 PA output power alarm .................................... 165198087266 PA power overvoltage...................................... 165198087267 PA power is undervoltage ................................ 166198087268 Downlink checksum error of DLRC_AL1.............. 166198087269 DUC chip initialization failure ............................ 166198087270 80w PA VSWR alarm ....................................... 167198087271 80w PA 's temperature is a litter high. ............... 167198087272 80w PA overtemperature major alarm ............... 168198087273 80w PA output power alarm ............................. 168198087274 80w PA power overvoltage ............................... 169198087275 80w PA 's power is undervoltage . ..................... 169198087276 80w PA not-in-position alarm............................ 170



198087277 TXIF lock is lost. ............................................. 170198087278 TPF clock is unlocked....................................... 170198087279 TXRF lost lock alarm........................................ 171198087280 RXRF clock is unlocked . .................................. 172198087281 13 MHz clock is lost......................................... 172198087282 60ms synchronous clock lost alarm ................... 173198087283 8M clock of HW is lost. .................................... 173198087284 HW 8K synchronous signal is lost . .................... 174198087285 RF board 52MHz clock lost alarm....................... 174198087286 First ADC clock is lost. ..................................... 175198087287 Second ADC clock is lost. ................................. 176198087288 PA power is overvoltage................................... 176198087289 PA power is undervoltage................................. 177198087290 PA VSWR alarm .............................................. 177198087291 PA temperature is a little high. (TRX level alarm,exceeds 80℃) ................................................................. 177198087292 PA temperature is much more higher. (TRX levelalarm, exceeds 95 ℃) ...................................................... 178198087293 PA forward power(3db) alarm........................... 179198087294 RTU power is abnormal.................................... 179198087295 The temperature of RTU power is too high. ......... 180198087296 The output of RTU power is overvoltage. ............ 180198087297 RTU power input abnormal alarm ...................... 181198087298 IQ calibration parameters are abnormal. ............ 181198087299 EAM heat exchanger alarm............................... 181198087300 CMB0 heating film alarm.................................. 182198087301 CMB1 heating film alarm.................................. 182198087302 EAM has had smoke . ...................................... 183198087303 EAM has had water.......................................... 183198087304 EAM lightning protection alarm. ........................ 184198087305 EAM backdoor access is intruded....................... 184198087306 EAM frontdoor access is intruded. ..................... 185198087307 EAM PWR monitoring unit has fault. .................. 185198087308 FIB heating film alarm..................................... 185198087309 EAM heat exchanger control board hasfault. ............................................................................. 186198087310 EAM heat exchanger external circulation fan 2alarm............................................................................. 186198087311 EAM heat exchanger external circulation fan 1alarm............................................................................. 187198087312 EAM heat exchanger internal circulation fan 2alarm............................................................................. 187198087313 EAM heat exchanger internal circulation fan 1alarm............................................................................. 188198087314 EAM heat exchanger 's 485 communication hasfault. ............................................................................. 188198087315 EAM temperature is abnormal........................... 189198087316 EAM TRX layer mixed-flow fan 1 has fault. ......... 189198087317 EAM TRX layer mixed-flow fan 2 has fault. ......... 189198087318 EAM TRX layer mixed-flow fan 3 has fault. ......... 190198087319 Communication is broken between EAM andCMB. ............................................................................. 190198087320 Power undervoltage alarm................................ 191198087321 Inner fan engine 2 alarm (for M8202)................ 191198087322 Inner fan engine 1 alarm (for M8202)................ 192198087323 Outer fan engine 2 and 4 alarm (for M8202) ......... 192198087324 Outer fan engine 1 and 3 alarm (for M8202) ......... 193198087325 Rack temperature minor alarm ......................... 193198087326 Rack temperature major alarm ......................... 194198087327 Layer 3 fan 1 alarm (for M8206) ....................... 194



198087328 Layer 3 fan 2 alarm (for M8206) ....................... 194198087329 Layer 3 fan 3 alarm (for M8206) ....................... 195198087330 Layer 2 fan 1 alarm (for M8206) ....................... 195198087331 Layer 2 fan 2 alarm (for M8206) ....................... 196198087332 Layer 2 fan 3 alarm (for M8206) ....................... 196198087333 Layer 1 fan 1 alarm (for M8206) ....................... 197198087334 Layer 1 fan 2 alarm (for M8206) ....................... 197198087335 Layer 1 fan 3 alarm (for M8206) ....................... 198198087340 FR device failure ............................................. 198198087342 Cell interruption alarm..................................... 199198087361 The CRC calibration of PA parameter turns to beerror ............................................................................. 200198087379 OMP reboot alarm........................................... 200198087386 SYNCLK losing lock alarm ................................ 201198087387 Status of TX1 filter alarm................................. 201198087388 Status of TX2 filter alarm................................. 201198087389 Status of TX3 filter alarm................................. 202198087390 Status of TX4 filter alarm................................. 202198087391 FCU power undervoltage alarm ......................... 203198087392 FCU minor alarm ............................................ 203198087403 ABIS-E1 transmission related clock alarm of CCIboard............................................................................. 203198087404 Local working clock alarm of CCI board.............. 204198087405 13M clock alarm of CCI board . ......................... 204198087406 CCI opposite board alarm ................................ 205198087407 IQ FPGA internal clock alarm ............................ 205198087408 IQ FPGA light interface alarm .......................... 205198087409 IQ FPGA LVDS interface alarm .......................... 206198087410 IQ FPGA internal data alarm............................. 206198087411 13M and 61.44M clock lost alarm ...................... 207198087412 FR or FN has error........................................... 207198087413 26MHz and 52MHz Phase Locked Loop (PLL) loselock alarm ...................................................................... 208198087414 Detect failure alarm of uplink 60ms hyperframesynchronization head ....................................................... 208198087415 Checking block data error alarm ....................... 209198087416 Uplink LVDS SERDES lost lock alarm.................. 209198087417 FN error alarm................................................ 209198087432 Diversity antenna lost...................................... 210198087433 Diversity antenna identical. .............................. 210198087443 Diversity antenna lost alarm............................. 211198087444 Diversity antenna identical alarm ...................... 211198087451 Board does not support 16MHW. ....................... 211198087452 CMB CPU overload alarm ................................. 212198087453 Signalling HDLC is broken . .............................. 212198087454 Main dimensional HDLC broken alarm................ 213198087455 FIB configuration exception alarm ..................... 213198087456 FIB software layer 3 no response ...................... 214198087457 FIB CPU overload alarm ................................... 214198087458 BVC block alarm ............................................. 215198087460 +12V voltage alarm ........................................ 215198087461 -12V voltage alarm ......................................... 216198087462 DSP 1.2V voltage alarm................................... 216198087463 6.4V voltage alarm ......................................... 216198087464 5V voltage alarm ............................................ 217198087470 Fan engine not-in-position alarm....................... 217198087471 Fan engine rotation speed alarm ....................... 218198087472 CMB and FNCB RS485 link broken alarm ............ 218198087473 DTPU CPU is overloaded................................... 218198087480 Status of TX5 filter alarm................................. 219



198087481 Status of TX6 filter alarm................................. 219198087483 GPS signal synchronization exception ................ 219198087484 Second pulse lost alarm................................... 220198087485 Antenna open-circuit alarm .............................. 220198087486 Antenna short-circuit alarm.............................. 221198087487 Lost satellite alarm ......................................... 221198087505 GUP board connection failure............................ 222198088000 DTPU does not support baseband freqency-hop-ping alarm...................................................................... 222198088001 PA voltage adjusting path has broken. ............... 223198088002 PA voltage adjusting read/write error. ................ 223198088003 PA voltage adjusting parameter turns to be er-ror. ................................................................................ 224198088004 Access iBSC failure.......................................... 224198088005 Control link broken ......................................... 225198088006 Operation link broken(CS)................................ 225198088007 Operation link broken(PS) ................................ 225198088008 Parameter configuration mismatch .................... 226198088009 DSP initialization failure ................................... 226198088010 Parameter configuration failure of AD6537 ......... 227198088011 Tx PLL lost lock alarm...................................... 227198088012Wrong parameter configuration for EEPROM......... 227198088013 FLASH memory fault ....................................... 228198088014 DSP works abnormally. .................................... 228198088015 FPGA interface fault ........................................ 229198088016 CHP frame porcessing error alarm..................... 229198088017 Wrong receive channel of RF ............................ 229198088018 Acquiring DNS failure under dynamic configuredIP mode ......................................................................... 230198088019 Analysis failure of DNS domain name ................ 230198088020 IPSec start failure ........................................... 231198088021 Frequency point and HTRG mismatch alarm......... 231198088022 DHCP automatically acquiring IP address fail-ure ................................................................................ 231198088023 Overhigh temperature alarm ............................ 232198088024 Voltage abnormity........................................... 232198088025 Abis link switch alarm...................................... 233198088027 DIP E1 rack, rack type error ............................. 233198088028 DIP E1 rack, rack number error ........................ 233198088029 DIP E1 rack, slave rack port 1 error................... 234198088030 DIP E1 rack, slave rack port 2 error................... 234198088031 DIP E1 rack,satellite back up flag error .............. 235198088032 DIP E1 rack, OAM time slot error. ...................... 235198088033 DIP IP rack,access mode error(IP or IPOE) ......... 236198088034 DIP IP rack,rack number error .......................... 236198088035 DIP IP rack,site number error ........................... 236198088036 DIP IP rack,sequence number error ................... 237198088037 Mains power failure alarm ................................ 237

198000002 Loss of opticalsignal

Alarm Property � Alarm Code:198000002

� Description:Loss of optical signal



� Severity:Major

� Alarm Type:Equipment Alarm

Probable Cause 1. The receiving optical fiber/module of local equipment is faulty.Receiving optical fiber is faulty or disconnected. Optical con-nector is polluted. Receiving optical module is faulty.

2. The transmitting optical fiber of opposite equipment is faulty.Transmitting optical fiber is faulty or disconnected. Opticalconnector is polluted.

3. The receiving optical power at local end is excessively low. Op-tical power attenuation on the receiving fiber transmission lineat local end is too much. Transmitting optical power at oppo-site end is too low.

4. Operation of LOS insertion is performed at opposite end. Man-ual operation of LOS insertion is performed in diagnostic test,and optical module is shutdown by force.

5. Optical fiber and optical module is incompatible. The fibertransmission rate and the optical module wavelength are in-compatible.

Specific Problem 1. The receiving optical fiber/module of local equipment is faulty.Receiving optical fiber is faulty or disconnected. Optical con-nector is polluted. Receiving optical module is faulty.

2. The transmitting optical fiber of opposite equipment is faulty.Transmitting optical fiber is faulty or disconnected. Opticalconnector is polluted.

3. The receiving optical power at local end is excessively low. Op-tical power attenuation on the receiving fiber transmission lineat local end is too much. Transmitting optical power at oppo-site end is too low.


5. Optical fiber and optical module is incompatible. The fibertransmission rate and the optical module wavelength are in-compatible.

System Impact The optical interface fails to work normally. If the optical inter-face is configured with APS protection, service will be switched toprotection optical interface. Otherwise, all services on the opticalinterface will be down.

HandlingSuggestion

1. Carry out loop test to determine whether the alarm is causedby local end or opposite end. Perform fiber self-loop at lo-cal equipment. If the alarm persists, fault might lie in localequipment. If the alarm disappears, inform the opposite endto troubleshoot.

2. Replace the optical module.

3. Replace fiber.

4. Replace board.



198000256 Ethernet link toOMC is broken.


� Description:Ethernet link to OMC is broken.

� Severity:Minor


Probable Cause 1. No network cable is connected with Network Port OMC or OMC2on rear board.

2. Network cable is disconnected or cable connector is loose.

3. Network port on the board is faulty.

Specific Problem 1. No network cable is connected with Network Port OMC or OMC2on rear board.

2. Network cable is disconnected or cable connector is loose.

3. Network port on the board is faulty.

System Impact Master/slave switching will occur if OMP is configured in mas-ter/slave mode. If master/slave switching is normal, systemwill not be affected. If master/slave switching is abnormal, OMPboard will fail to obtain version package from NMS, leading toboard power-on failure, UE access failure, and interruption ofongoing services.

HandlingSuggestion

1. Ensure that network cable is connected to Network Port OMCor OMC

2. Unplug and plug the network cable on Network Port OMC orOMC2 Of OMP board

3. Check if OMC or OMC2 network cable works normally. If no,replace the cable.

198000518 Trunk link isused for CSU loop back test


� Description:Trunk link is used for CSU loop back test

� Severity:Minor


Probable Cause The equipment at end A sends CSU link building code to end B, andthis trunk link is set to loop back at end B. And CSU test starts.Ifthis trunk link is not used for CSU loop back test, this alarm won'tbe triggered.

Specific Problem The equipment at end A sends CSU link building code to end B, andthis trunk link is set to loop back at end B. And CSU test starts.If



this trunk link is not used for CSU loop back test, this alarm won'tbe triggered.

System Impact The configured trunk link is blocked.

HandlingSuggestion

End A sends the command of canceling CSU loop back to end B.

198001026 Loss of ATMCell Synchronization overE1 Link


� Description:Loss of ATM Cell Synchronization over E1 Link

� Severity:Minor


Probable Cause 1. Cell Header HEC (Header Error Check) is damaged, leading tocell location failure in physical layer frame.

2. The alarm is caused by bottom layer fault. Cell HEC is handleddifferently at local end and opposite end.

Specific Problem 1. Cell Header HEC (Header Error Check) is damaged, leading tocell location failure in physical layer frame.

2. The alarm is caused by bottom layer fault. Cell HEC is handleddifferently at local end and opposite end.

System Impact Data reception on E1 link is abnormal. If merely one E1 link isavailable for the port, all services on the board will be down. Other-wise, port bandwidth will be affected, leading to decreased accessbandwidth. The number of successful upper-layer service accessrelated to the port will decrease, but service interruption will notoccur.

HandlingSuggestion

1. Check if the following alarm occurs in the board. If yes, refer tothe corresponding alarm handling suggestion. Related alarms:519 Trunk error 520 Trunk abnormal

2. On NMS configuration management interface, check ifSDH/SONET mode is configured for both ends. Ensure thatthe configuration at both ends is consistent.

3. Use meter measurement or loop test to judge whether thealarm is caused by local end or opposite end. Meter Measure-ment Use a trunk test meter to test whether the trunk receiv-ing signals at local end are normal. If normal, fault might liein local equipment. If abnormal, troubleshoot at opposite end.Loop Test Perform self-loop at local trunk. If the alarm persists,fault might lie in local equipment. If the alarm disappears, in-form the opposite end to troubleshoot.

4. Replace trunk cable.

5. Replace board.



198001027 ATM link is downAlarm Property � Alarm Code:198001027

� Description:ATM link is down

� Severity:Minor


Probable Cause 1. Bottom layer physical link is abnormal.

2. HEC handling at local end and opposite end is inconsistent.

Specific Problem 1. Bottom layer physical link is abnormal.

2. HEC handling at local end and opposite end is inconsistent.

System Impact Communication at ATM port is down. All services based on thetrunk are interrupted.

HandlingSuggestion

1. Check if the following board alarm occurs. If yes, refer to cor-responding alarm handling suggestion. Related alarms: 519Trunk error 520 Trunk abnormal

2. On NMS configuration management interface, check ifSDH/SONET mode configuration exists at both ends. Ensurethat the configuration at both ends is consistent.

3. Use meter measurement or loop test to judge whether thealarm is caused by local end or opposite end. Meter Mea-surement Use a trunk test meter to test whether the receivingtrunk signals at local end are normal. If normal, fault mightlie in local equipment. If abnormal, troubleshoot at oppositeend. Loop Test Perform self-loop at local trunk. If the alarmpersists, fault might lie in local equipment. If the alarm disap-pears, troubleshoot at opposite end.


5. Replace board.

198001284 The phase of8K, 16K clock, input tobackplane board, is notmatched


� Description:The phase of 8K, 16K clock, input to backplaneboard, is not matched

� Severity:Minor


Probable Cause 1. Clock cable is not properly connected.



2. Clock board is faulty.

Specific Problem 1. Clock cable is not properly connected.

2. Clock board is faulty.

System Impact The system fails to achieve synchronization so that the board cannot work normally. As a result, UE can not be accessed and ser-vices borne on the board are interrupted.

HandlingSuggestion

1. Check the clock input cable and ensure that the cable is goodand well connected.

2. Clock board changeover.

3. UIM/GUIM board changeover.

4. Replace the board.

198001285 SDH/SONET:Excessive Error Code


� Description:SDH/SONET:Excessive Error Code

� Severity:Minor


Probable Cause The board experiences reset. The SETS chip and the crystal oscil-lator need to be fully preheated.

Specific Problem The board experiences reset. The SETS chip and the crystal oscil-lator need to be fully preheated.

System Impact SDH/SONET equipment can work. However, call loss or noise oc-curs to all voice services on this optical path, and bit error occurson the data service channel.

HandlingSuggestion

Normal procedure after board reset, please wait for the end ofwarm-up procedure. Clock tests can be taken unless this alarm iscleared.

198001286 Input clock ofboard lost


� Description:Input clock of board lost

� Severity:Minor


Probable Cause 1. The board is not in place (not properly inserted) in the slot.



2. Clock cable is disconnected.

3. Clock cable is faulty.

4. Board is faulty.

Specific Problem 1. The board is not in place (not properly inserted) in the slot.

2. Clock cable is disconnected.

3. Clock cable is faulty.

4. Board is faulty.

System Impact The board fails to synchronize with system clock so that it can notwork normally. As a result, UE can not be accessed and servicesborne on the board are interrupted.

HandlingSuggestion

1. Check if the clock (input) cable at the shelf is intact and prop-erly connected.

2. Check if the following alarm occurs in the board. If yes, refer tothe corresponding alarm handling suggestion. Related alarm:5635 The board is not plugged firmly


198001792 Loss of SDHtransmission link


� Description:Loss of SDH transmission link

� Severity:Major


Probable Cause 1. The alarm occurs when the receiving optical power is below op-tical receiver sensitivity. Generally speaking, normal receivingoptical power range for optical modules is between -28 dBmand -8 dBm. Optical signals within this range can be detected.Probable causes for the alarm include: 1. The receiving opti-cal fiber/module of local SDH equipment is faulty. Receivingoptical fiber is faulty or disconnected. Optical connector is pol-luted. Receiving optical module is faulty.

2. The transmitting optical fiber of opposite SDH equipment isfaulty. Transmitting optical fiber is faulty or disconnected. Op-tical connector is polluted.

3. The optical transmission line of SDH equipment is faulty. Tailfiber and flange between fiber distribution frame and the equip-ment at local end are faulty or disconnected. The related con-nector is in poor contact.

4. The receiving optical power at local end is excessively low. Op-tical power attenuation on the fiber transmission line at receiv-ing end is too much. Opposite-end transmitting optical poweris too low.




6. Optical fiber and optical module is incompatible. The fibertransmission rate of STM signals and the optical module wave-length are incompatible.

Specific Problem 1. The alarm occurs when the receiving optical power is below op-tical receiver sensitivity. Generally speaking, normal receivingoptical power range for optical modules is between -28 dBmand -8 dBm. Optical signals within this range can be detected.Probable causes for the alarm include: 1. The receiving opti-cal fiber/module of local SDH equipment is faulty. Receivingoptical fiber is faulty or disconnected. Optical connector is pol-luted. Receiving optical module is faulty.

2. The transmitting optical fiber of opposite SDH equipment isfaulty. Transmitting optical fiber is faulty or disconnected. Op-tical connector is polluted.

3. The optical transmission line of SDH equipment is faulty. Tailfiber and flange between fiber distribution frame and the equip-ment at local end are faulty or disconnected. The related con-nector is in poor contact.

4. The receiving optical power at local end is excessively low. Op-tical power attenuation on the fiber transmission line at receiv-ing end is too much. Opposite-end transmitting optical poweris too low.


6. Optical fiber and optical module is incompatible. The fibertransmission rate of STM signals and the optical module wave-length are incompatible.

System Impact SDH/SONET fails to work normally, leading to UE access failure onSDH/SONET and interruption of ongoing services.

HandlingSuggestion

1. Use meter measurement or loop test to judge whether thealarm is caused by local end or opposite end. Meter Mea-surement Use a SDH test meter or optical power meter to testwhether the receiving optical signals at local end are normal.If normal, fault might lie in local equipment. If abnormal, faultlies in opposite end or on transmission side. Inform the op-posite end or transmission side to troubleshoot. Loop TestPerform fiber self-loop at local SDH equipment. If the alarmpersists, fault might lie in local equipment. If the alarm disap-pears, inform the opposite end to troubleshoot.

2. Replace optical module.

3. Replace optical fiber.

4. Replace board.



198002560 Board CPUoverload


� Description:Board CPU overload

� Severity:Major


Probable Cause 1. Excessive data traffic at higher layer.

2. System is performing data synchronization or saving.

3. CPU alarm threshold setting is under configured.

Specific Problem 1. Excessive data traffic at higher layer.

2. System is performing data synchronization or saving.

3. CPU alarm threshold setting is under configured.

System Impact CPU occupancy indicates the current status of system operation.CPU overloaded, or over high occupancy, is usually caused by ser-vice or operation that consume much time. It has the followingimpact on the system: Services with low priority level have littleor no access to the processing of CPU, which reduces processingspeed of the services or even halts the processing. System boardcould reset under excessively overloading conditions, causing in-terruption to the service it performs.

HandlingSuggestion

1. Open the rack map on the Configuration Management window,select Board, right click and select Board Property. Check theCPU overload threshold setting on the CPU Information tab.Please reset CPU overload threshold if the CPU overload thresh-old value is too low. It will take 30 seconds for the new settingto take effect. Recommended threshold value: 80% for lowlevel load threshold, 90% for high level load threshold.

2. Check for the record of data synchronization, data saving orother file operations in the network manager log files. Thoseoperations might increase the CPU utilization rate radically, andit might take 2 minutes.

3. Check for the record of new board added or version upgradeoperation in the network manager log files. Version upgradingoperation might increase CPU utilization rate radically, and itmight take 2 minutes.

198002561 Hightemperature on CPU board


� Description:High temperature on CPU board

� Severity:Major




Probable Cause 1. Fan faulty.

2. High temperature in rack.

3. CPU overload.

Specific Problem 1. Fan faulty.

2. High temperature in rack.

3. CPU overload.

System Impact Automatic CPU reset might occur.

HandlingSuggestion

1. In NMS Configuration Management interface, click Rack. Rightclick the concerned board > Show Board Properties Page >CPU1 or CPU

2. Check 2 parameters: Low/High threshold of alarm tempera-ture, Reset temperature. If the settings are low, please adjustthe High threshold of alarm temperature and the Reset tem-perature. The new settings will be valid after 30 seconds. Rec-ommended Thresholds: High threshold of alarm temperature:90 degrees Celsius, Reset temperature: 95 degrees Celsius.2. Observe the thermometer in machine room to know roomtemperature. If it is high, please take effective measures tocool down.

3. Check the surface of the boards. Does it have much dust? Ifyes, please clean it for better cooling.

4. Check the air intake and air outlet of the rack. Does it havemuch dust? If yes, please clean it for better ventilation.

5. Make sure the fan(s) on the rack works normally.

6. Replace the fault board.

198005121 Inter-shelf mediaplane links abnormal


� Description:Inter-shelf media plane links abnormal

� Severity:Major


Probable Cause 1. The fiber connection is error between shelves, or the fiber isnot physically plugged.

2. The background configuration of the board is inconsistent withits foreground physical connection.

3. The transceiver of the board link detection packet is excep-tional.

Specific Problem 1. The fiber connection is error between shelves, or the fiber isnot physically plugged.



2. The background configuration of the board is inconsistent withits foreground physical connection.

3. The transceiver of the board link detection packet is excep-tional.

System Impact The inter-shelf service bandwidth is reduced. The inter-shelf ser-vices may be interrupted if no backup is configured.

HandlingSuggestion

1. In the NMS Configuration Management interface, select UnitConnection Relation, then compare the configuration with ac-tual physical connection. If it is different, adjust connectioncables according to the configuration.

2. Check the connection of optical fiber and make sure it is in crossconnection. Is there any relevant alarm? If yes, please solvethe problem according to recommended handling suggestions.Relevant Alarm: 5125 GE optical transceiver module is wronglyconnected to left/right board slots at opposite end

3. Replace the optical fiber or the optical transceiver module sothat the SD indicator for the corresponding port is on.

4. Replace the local board.

5. Replace the opposite board.

198005124 Capacity ofTRUNK communication isinsufficient


� Description:Capacity of TRUNK communication is insufficient

� Severity:Minor


Probable Cause 1. Connection failure

2. Line failure

3. Board failure

4. Rear board failure .

Specific Problem 1. Connection failure

2. Line failure

3. Board failure

4. Rear board failure .

System Impact There is no impact on services when TRUNK connection is notadopted for inter-shelf control plane communication. Howeverif TRUNK connection is adopted, this alarm indicates insufficientnetwork communication capability. This may cause congestion atcontrol plane. During heavy traffic period, this may cause muchdelay or services interruption in extreme condition.



HandlingSuggestion

1. Check whether TRUNK connection is used for inter-shelf controlplane. If not, no handling is required.

2. Check the number of connections, i.e. 4 FEs and 2 GEs arerequired. Complete the connections if there is any missing.

3. Check whether the connection is correct. The correct connec-tion is described as below: For FE port trunk, if UIM board isinstalled on BUSN shelf, then TRUNK connection is not sup-ported. In this case, this alarm won't occur. If UIM is installedon other shelf, FE7, FE8, FE9 and FE10 work together to forma TRUNK port. However if it is GUIM board, FE3, FE4, FE5and FE6 form a TRUNK port. For CHUB board, every 4 adja-cent FE ports form a TRUNK port, such as FE1~FE4, FE5~FE8etc. For each trunk port, All the 4 RE ports must be connected,and direct connection is recommended. For GE port trunk, 2GE interfaces (CHUB board inter-connection) are connected incross-connection mode. The #1 GE port on the left board onthe local shelf corresponds to the #1 GE port on the left boardon the opposite shelf; the #2 GE port on the left board on thelocal shelf corresponds to the #2 GE port on the right boardof opposite shelf. The #1 GE port on the right board on thelocal shelf corresponds to the #2 GE port on the left board onthe opposite shelf, and the #2 GE port on the left board on thelocal shelf corresponds to the #2 GE port on the right board onthe opposite shelf.

4. Replace the cable or optical module.

5. Replace the rear board.

6. Replace the connected board.

198005125 GE opticalconnection is crossconnected


� Description:GE optical connection is cross connected

� Severity:Minor


Probable Cause 1. fibre connected to wrong module.

2. GE optical transceiver module in wrong slot.

3. transmit and receive fibres crossed.

Specific Problem 1. fibre connected to wrong module.

2. GE optical transceiver module in wrong slot.

3. transmit and receive fibres crossed.

System Impact Cause interruption to all services performed on this shelf.



HandlingSuggestion

Check the fiber optics for its proper cross connection

198005376 Internal mediaport of board is abnormal


� Description:Internal media port of board is abnormal

� Severity:Major


Probable Cause 1. Physical failure of the IC at the internal port on the board.

2. Failure of local board connecting port on the switching IC ofUIM.

3. Backplane wiring failure of local slot to UIM.

4. CPU overloaded on the first level switching board, UIM boardat the shelf, or local board.

5. Service over the rated capability of the board.

Specific Problem 1. Physical failure of the IC at the internal port on the board.

2. Failure of local board connecting port on the switching IC ofUIM.

3. Backplane wiring failure of local slot to UIM.

4. CPU overloaded on the first level switching board, UIM boardat the shelf, or local board.

5. Service over the rated capability of the board.

System Impact Because internal media stream can not be transmitted via thisport, it will select another port for transmission. If all the internalports are abnormal, the internal media stream will be interruptedand all the services provided on this board will be interrupted.

HandlingSuggestion

1. In Alarm Management interface, check the CPU rate, which islocated on L1 switching board, the board or UIM/GUIM boardof the same shelf. Is there a CPU overloaded alarm? If yes,please solve the problem according to the corresponding han-dling suggestions. Related Alarm: 2560 Board CPU Overloaded

2. In the Alarm Management interface, check whether there is analarm, indicating abnormal link at inter-shelf media plane. Ifyes, please solve the problem according to the correspondinghandling suggestions. Related Alarm: 5121 Inter-shelf mediaplane link fault


4. Change a slot to insert the board.

5. Replace the UIM/GUIM of the same shelf.



198005381 Input clock isabnormal


� Description:Input clock is abnormal

� Severity:Critical


Probable Cause 1. The Clock board is abnormal.

2. The clock board is not synchronized with reference clock.

3. The clock reference source is abnormal.

Specific Problem 1. The Clock board is abnormal.

2. The clock board is not synchronized with reference clock.

3. The clock reference source is abnormal.

System Impact The services are interrupted because the system can not get aproper clock.

HandlingSuggestion

1. Reconnect the cable between the board and the clock refer-ence.

2. Replace the cable between the board and the clock reference.

3. Check the signal output from the reference clock source.


198005389 CPU sub card inposition is not configured inthe database


� Description:CPU sub card in position is not configured in thedatabase

� Severity:Warning


Probable Cause 1. Configuration is incorrect.

2. Board is misplaced.

Specific Problem 1. Configuration is incorrect.

2. Board is misplaced.

System Impact Since the board where the unconfigured sub card is located resetsrepeatedly, power resource of the equipment is wasted. However,services won't be affected.



HandlingSuggestion

Is the sub card needed? If no, remove the sub card. If yes, changethe type of board so that it can support the sub card.

198005390 CPU sub cardis missing from slot but isconfigured in database


� Description:CPU sub card is missing from slot but is configuredin database

� Severity:Major


Probable Cause 1. The configuration is wrong.

2. A wrong board is inserted.

Specific Problem 1. The configuration is wrong.

2. A wrong board is inserted.

System Impact The sub-card functions are unavailable, accordingly this boarddoes not support relevant services. The influence on the system isvarious according to different type of sub-card. If the sub-card isan interface board, the transmission link via this board is not con-nectable, then services will be accessed through other sub-card.If the sub-card is a signalling process board, the cell/Node Bconfigured for this board is not available for services. If thesub-card is a user's plane board, user plane process capability willdecline, then services will be accessed through other sub-card.

HandlingSuggestion

Is the sub-card required? If no, modify the type of board so thatthe new type doesn't support such sub-card; if yes, insert the sub-card firmly.

198005395 External portabnormal


� Description:External port abnormal

� Severity:Major


Probable Cause 1. The cable is not properly connected or not connected to theport.

2. The port chip on the board is faulty.



3. The opposite board is faulty.

Specific Problem 1. The cable is not properly connected or not connected to theport.

2. The port chip on the board is faulty.

3. The opposite board is faulty.

System Impact This port is not available for services. If there is a standby port,data can be received or transmitted via the standby port. But inthis case, totally data throughput will decline. Meanwhile, the re-liability and stability of the system declines. If there is no standbyport, all communication links via this port will be broken, and theservices carried via this port will be interrupted.

HandlingSuggestion

1. Reconnect or replace the cable.


3. Contact responsible engineers to check the opposite port andremove possible faults.

198005396 Exceptionalcommunication on UIMboard or back plane


� Description:Exceptional communication on UIM board or backplane

� Severity:Major


Probable Cause 1. The internal port chip on the board has a physical fault.

2. The switch IC on UIM/GUIM provides a port, which is connectedto the board. This port has a fault.

3. Backplane wiring failure, which connects the slot to UIM.

4. A CPU on L1 switching board, the board, or UIM board of thesame shelf, is overloaded.

5. Service exceeds the processing capability of the board.

Specific Problem 1. The internal port chip on the board has a physical fault.

2. The switch IC on UIM/GUIM provides a port, which is connectedto the board. This port has a fault.

3. Backplane wiring failure, which connects the slot to UIM.

4. A CPU on L1 switching board, the board, or UIM board of thesame shelf, is overloaded.

5. Service exceeds the processing capability of the board.

System Impact If the internal media plane stream can not be processed, packetsmay be lost. In this case, services provided by this board become



unstable. If it is port fault or connector fault, the internal mediaplane is completely broken. In this case, services borne on thisboard are interrupted. If either CPU or traffic is overloaded, ser-vices carried on the board will be delayed. In serious situation,services may be interrupted.

HandlingSuggestion

1. In Alarm Management interface, check whether there is an in-ternal media plane port abnormal alarm. If yes, please solvethe problem according to corresponding handling suggestion.Related Alarm: 5376 Internal media plane port abnormal

2. In Alarm Management interface, check the CPU rate, which islocated on L1 switching board, the board or UIM board of theshelf. Is there a CPU overloaded alarm? If yes, please solve theproblem according to the corresponding handling suggestions.Related Alarm: 2560 Board CPU Overloaded

3. In the Alarm Management interface, check whether there is analarm, indicating abnormal link at inter-shelf media plane. Ifyes, please solve the problem according to the correspondinghandling suggestions. Related Alarm: 5121 Inter-shelf mediaplane link fault


5. Change a slot to insert the board.

6. Replace the UIM of the same shelf.

198005399 DSP resource isunavailable


� Description:DSP resource is unavailable

� Severity:Major


Probable Cause 1. This alarm indicates DSP resource is not available. It is mon-itored by higher-level layer. Once DSP is blocked, an alarm isgiven. This includes the following situations: 1. DSP versionfails to be loaded so that the system is unable to operate nor-mally.

2. The HPI port on DSP is abnormal.

3. The DSP media plane communication is disconnected.

4. DSP resets.

Specific Problem 1. This alarm indicates DSP resource is not available. It is mon-itored by higher-level layer. Once DSP is blocked, an alarm isgiven. This includes the following situations: 1. DSP versionfails to be loaded so that the system is unable to operate nor-mally.

2. The HPI port on DSP is abnormal.

3. The DSP media plane communication is disconnected.



4. DSP resets.

System Impact All services processed by this DSP are interrupted, and those ser-vices will be re-created on other normal DSPs. If the DSP is un-available for a long time, system performance will be degraded.

HandlingSuggestion

1. In network management system, check the operation & main-tenance log file. Is there a record, indicating DSP version re-placing? If yes, this operation must cause DSP to reset. Andhaving this alarm is a normal phenomenon. No handling is re-quired. Please wait until DSP reset is complete.

2. Alarm details are displayed in NMS Alarm Management inter-face, where DSP index is given. Click System Rack Architec-ture. Right click the concerned board > Display Attributes >Subunit Configuration. Then select the fault DSP and click Sub-unit Configuration > Status Attribute> Query Status to viewstatus. Is the Status of DSP Blocked? If it is Blocked, it meansDSP is blocked manually. And this alarm is a normal phenom-enon. In this case, click System Rack Architecture. Right clickthe concerned board and choose Subunit. Perform unblockDSP operation. After the operation, DSP restores to normal.

3. In Alarm Management interface, check whether there is one ofthe following alarms. If yes, please solve the problem accord-ing to corresponding handling suggestions. Related Alarms:5701 Version Load Error 5655 DSP auto-detection abnormal5700 DSP abnormally resets

4. Reset the board.


198005403 Board SRAMself-check fails


� Description:Board SRAM self-check fails

� Severity:Major


Probable Cause Hardware fault of board.

Specific Problem Hardware fault of board.

System Impact Board operation might be abnormal.



HandlingSuggestion

Replace the board, and check whether this alarm disappears.

198005404 Board OCXOoven fault


� Description:Board OCXO oven fault

� Severity:Major


Probable Cause Hardware fault of board.

Specific Problem Hardware fault of board.

System Impact Board operation might be abnormal.

HandlingSuggestion

Replace the board, and check whether this alarm disappears.

198005405 Clock boardphase-lock loop work modeabnormal


� Description:Clock board phase-lock loop work mode abnormal

� Severity:Major


Probable Cause 1. There is no available reference source.

2. The clock distribution line is incorrect or there exists self loop.

3. The secondary clock locks the tertiary clock.

Specific Problem 1. There is no available reference source.



System Impact The designated reference clock cannot be phase-locked.

HandlingSuggestion

1. Check if the corresponding clock reference is correctly in-putted.




198005632 Hard disk usagerate exceeds threshold.


� Description:Hard disk usage rate exceeds threshold.

� Severity:Major


Probable Cause 1. The configured usage rate threshold is unreasonable.

2. The usage rate of hard disk is over high.

Specific Problem 1. The configured usage rate threshold is unreasonable.

2. The usage rate of hard disk is over high.

System Impact When hard disk usage rate exceeds its threshold, new data can notbe written. The data may be lost. There is no impact on services.

HandlingSuggestion

1. In NMS Configuration Management interface, click MPX86 orMPX86/2 Alarm Parameters > Hard Disk Full Alarm to checkthe threshold used to report a hard disk usage alarm. If thethreshold value is low, please increase it.

2. Clean the space of hard disk. Delete the files that are no longerused, or move them to external storage devices.

198005633 OMP hard diskis faulty


� Description:OMP hard disk is faulty

� Severity:Major


Probable Cause The ribbon cable is loose or the hard disk fails, usually a hardwarefailure.

Specific Problem The ribbon cable is loose or the hard disk fails, usually a hardwarefailure.

System Impact 1. This is an OMP alarm caused by hard disk breakage, which willaffect the system in three ways: 1. The OMP can not boot andservices can not access the board.

2. If the log server is abnormal, performance data temporarilystored in the hard disk of the OMP will be lost.

3. No peripheral board can be powered on because when a pe-ripheral board boots, it will request for a version from the OMP.

HandlingSuggestion

Replace the fault hard disk or replace the board, where the harddisk is installed.



198005635 The board is notplugged firmly


� Description:The board is not plugged firmly

� Severity:Major


Probable Cause 1. The ENUM switch on the board is open, or in poor contact.

2. The EXCH button on the standby board is pressed twice within3 seconds.

Specific Problem 1. The ENUM switch on the board is open, or in poor contact.

2. The EXCH button on the standby board is pressed twice within3 seconds.

System Impact The active/standby board changeover or the APS changeover willfail. This board can not be switched to the active board.

HandlingSuggestion

1. Check whether the ENUM switch is closed. If not, close it.

2. Open and close the ENUM switch.

3. If the ENUM open status is simulated by pressing the EXCH keyon the standby board twice within 3 seconds, press the EXCHkey on the standby board twice within 3 seconds.

198005636 SMBUS errorAlarm Property � Alarm Code:198005636

� Description:SMBUS error

� Severity:Major


Probable Cause If the board is reset when the read-write time sequences of theSMBUS equipment are not finished, the SMBUS cannot be enabledafter the south bridge is reset. All the SMBUS equipments needbe reset again (the board need be pulled out and plugged).

Specific Problem If the board is reset when the read-write time sequences of theSMBUS equipment are not finished, the SMBUS cannot be enabledafter the south bridge is reset. All the SMBUS equipments needbe reset again (the board need be pulled out and plugged).

System Impact 1. In the case of SMBUS error, MPX86 board can be startup viaconfiguring BIOS. However, normal temperature check is im-possible for the MPX86 board with SMBUS error. Therefore, theboard might be running with high temperature without beingknown.

2. For the board with SMBUS error, memory size is configured bydefault. Therefore, the configured memory size might differfrom the actual memory size.



HandlingSuggestion

1. ull out and plug the board, and check if the alarm is eliminated.Y->The alarm is eliminated. End alarm handling. N->Replacethe board and end alarm handling.

198005637 Back card doesnot match with front board


� Description:Back card does not match with front board

� Severity:Minor


Probable Cause 1. Incorrect rear board is used.

2. Rear board failure.

Specific Problem 1. Incorrect rear board is used.

2. Rear board failure.

System Impact 1. When the rear board interface is used to connect other networkelement, it will cause link interruption at bottom layer, andservices over the corresponding link will be interrupted.

2. When the rear board interface is used to connect internal con-trol plane, it will cause communication error at internal controlplane. As a result, the board can not exchange control planemessages and services borne on the board will be interrupted.

3. When the rear board interface of clock board is used to extractclock, it will cause loss of clock signal. Because without inputclock, the system services will be interrupted.

HandlingSuggestion

1. Check the front board type for the correct rear board type, anduse the correct rear board.

2. Replace the defective rear board with a new rear board.

198005638 LVDS signalunlocked


� Description:LVDS signal unlocked

� Severity:Major


Probable Cause LVDS signal at the bottom layer is unlocked.

Specific Problem LVDS signal at the bottom layer is unlocked.



System Impact CS domain service of the resource shelves connected with the op-tical interface on TFI is down, HW loop back of the board in servicefails. In the case of TSNB board fault, all circuit switch might fail.

HandlingSuggestion

Switch or pull out and plug the board, and then check if the alarmis eliminated. Y->The alarm is eliminated. End alarm handling.N->Please contact ZTE Corporation.

198005639 High Error Rateof Optical Interface


� Description:High Error Rate of Optical Interface

� Severity:Major


Probable Cause 1. The fiber is not completed connected to the port, or is dam-aged, or is not compatible with the optical transceiver modulein T-network switch. There is no light signal input into the op-tics module. This alarm is dedicated to the TDM optical portonly. The possible causes of this alarm include: 1. TDM re-ceiver fiber optics failure, fiber optics module failure. This typeof failures include: damaged fiber on the receiver, unconnectedfiber, contaminated fiber or damaged optics module on the re-ceiver.

2. Fiber optics failure at the transmitting module on the corre-sponding TDM. This type of failures include: damaged fiber onthe transmitter, unconnected fiber, and contaminated fiber.

3. Compatibility between fiber optics and optics module. The fibertransmission rate of TDM signal is incompatible with the wavelength of the optics module.

4. Loss of signal (LOS) alarm operation is performed on the corre-sponding SDH device. This includes the manual diagnosis testalarm operation.

Specific Problem 1. The fiber is not completed connected to the port, or is dam-aged, or is not compatible with the optical transceiver modulein T-network switch. There is no light signal input into the op-tics module. This alarm is dedicated to the TDM optical portonly. The possible causes of this alarm include: 1. TDM re-ceiver fiber optics failure, fiber optics module failure. This typeof failures include: damaged fiber on the receiver, unconnectedfiber, contaminated fiber or damaged optics module on the re-ceiver.

2. Fiber optics failure at the transmitting module on the corre-sponding TDM. This type of failures include: damaged fiber onthe transmitter, unconnected fiber, and contaminated fiber.

3. Compatibility between fiber optics and optics module. The fibertransmission rate of TDM signal is incompatible with the wavelength of the optics module.



4. Loss of signal (LOS) alarm operation is performed on the corre-sponding SDH device. This includes the manual diagnosis testalarm operation.

System Impact There might be error in the data transmitted by the optical portwhich affects the quality of all the services performed on this op-tical port.

HandlingSuggestion

1. Perform loopback test to determine source of this alarm is onthe local devices or the corresponding devices. Perform self-loop test on local device. If the failure persists, the failuresource is on local device; if the failure disappears after self-looptest, then the source of failure is on the corresponding device.Contact the corresponding device for solution.

2. Replace optics module.

3. Replace the fibber optics.


198005640 FPGA exceptionAlarm Property � Alarm Code:198005640

� Description:FPGA exception

� Severity:Major


Probable Cause FPGA runs abnormally, for example, FPGA is lost, or the boardclock is lost.

Specific Problem FPGA runs abnormally, for example, FPGA is lost, or the boardclock is lost.

System Impact The FPGA verification will fail. The FPGA can not provide normalreading and writing functions. The board can not work normallyor provide all of its functions. Services borne on the board will beinterrupted.

HandlingSuggestion

1. Restart the board. In this case, the board downloads FPGAagain.


198005641 Port Link DownAlarm Property � Alarm Code:198005641

� Description:Port Link Down

� Severity:Major


Probable Cause There is something wrong with the lan91 chip or BCM532x chip orM88E6095 chip.



Specific Problem There is something wrong with the lan91 chip or BCM532x chip orM88E6095 chip.

System Impact DSP is abnormal and call loss increases.

HandlingSuggestion

1. Reset the corresponding DSP chip or the board by using MMLcommand on the background and then check the alarm is elim-inated.


198005643 Phase-lock loopwork mode abnormal


� Description:Phase-lock loop work mode abnormal

� Severity:Minor


Probable Cause 1. There is no available reference source.



Specific Problem 1. There is no available reference source.



System Impact The designated reference clock cannot be phase-locked.

HandlingSuggestion

1. Check if the corresponding clock reference is correctly in-putted.

Y->Replace the board and go to "2".

N->Correctly input the clock reference and go to "2".

2. Check if the alarm is eliminated.

Y->End.

N->Please contact ZTE Corporation.

198005644 The channel in asub card is down


� Description:The channel in a sub card is down

� Severity:Major




Probable Cause 1. The sub-card is not inserted in position.

2. The sub-card has hardware faults.

Specific Problem 1. The sub-card is not inserted in position.

2. The sub-card has hardware faults.

System Impact The sub-card channel is not initialized or the initialization fails.As a result, the channel corresponding to the alarm chip cannotbe used normally. This affects the service carried by the boardof the sub-card. After the channel is available and the alarm iseliminated, the service is recovered.

HandlingSuggestion

1. Unplug and plug the sub-card again. Wait for the board to bepowered on.

2. Replace the sub-card.

198005645 Sub cardabnormal


� Description:Sub card abnormal

� Severity:Minor


Probable Cause 1. The GCS, EC or HPS subcard of UIMC/GUIM/CHUB is not in-serted in position.

2. The subcard is faulty.

Specific Problem 1. The GCS, EC or HPS subcard of UIMC/GUIM/CHUB is not in-serted in position.

2. The subcard is faulty.

System Impact 1. UIMC/GUIM/CHUB GCS sub-card functions abnormally. Pack-ets may be lost, and even worse, link disconnection may occuron the control planes of some boards. For active/standby con-figuration, there are two cases: 1. If the active board is abnor-mal while the standby board is normal, the system performsactive/standby switchover. Thus, the standby board takes overthe services of the faulty active board. In this case, the serviceis not affected.

2. If both the active and standby boards are abnormal, ac-tive/standby switchover is forbidden. In this case, the serviceis interrupted because the faulty board cannot restore to thenormal status.

HandlingSuggestion

1. Check the sub-card connection on the board. If the sub-cardis loosely inserted, tightly insert it and wait for the board to bepowered on.

2. Replace the sub-card.



198005646 Phase-lock loopunlocked


� Description:Phase-lock loop unlocked



Probable Cause 1. Clock board faulty.

2. Reference clock has changed to another optical board.

3. Reference clock changed when a board has been removed orplugged in to the shelf.

4. UIMC/GUIM input is disconnected, or UIMC/GUIM clock phaseloop is abnormal.

Specific Problem 1. Clock board faulty.

2. Reference clock has changed to another optical board.

3. Reference clock changed when a board has been removed orplugged in to the shelf.

4. UIMC/GUIM input is disconnected, or UIMC/GUIM clock phaseloop is abnormal.

System Impact The service clock and system clock are inconsistent on the boardwith unlocked phase-lock loop. As a result, the service carried bythe board is interrupted.

HandlingSuggestion

1. Check whether there is the following clock alarm on the NMSAlarm Management interface. If yes, handle it according to thecorresponding suggestions. 5381 Input Clock Abnormal

2. Check whether there is any of the following alarms about theclock extracting optical port on the NMS Alarm Managementinterface. If yes, handle it according to the correspondingsuggestions. 1792 SDH/SONET fault 1824 Abnormal status inSDH/SONET 5639 High Error Rate of Optical Interface 2 SignalLoss of Optical Module

3. Check the operation and maintenance log in the NMS to see ifthere is a record about the change of the loop clock extractionreference. If yes, no handling is required.

4. Conduct an active/standby changeover to the clock board.

5. Conduct an active/standby changeover to the UIM/GUIMboard.




198005647 High BER on E1link


� Description:High BER on E1 link

� Severity:Major


Probable Cause 1. The E1/T1 link is faulty.

2. The device in the uplink direction of the trunk link is faulty.

3. The trunk cable or connector is in poor contact.

Specific Problem 1. The E1/T1 link is faulty.

2. The device in the uplink direction of the trunk link is faulty.

3. The trunk cable or connector is in poor contact.

System Impact The trunk fails to receive trunk signals. If the belonged port hasonly this link, all services on the port are interrupted. Otherwise,only the port bandwidth is affected. The quantity of upper layer ac-cess services associated with the port is decreased. The accessedbandwidth is reduced. The service, however, is not interrupted.

HandlingSuggestion

1. Conduct a meter measurement or loopback test to find outwhether the alarm is rooted in the local end or peer end. Metermeasurement: Connect a trunk test meter to check if the signalreceived by the local end trunk is normal. If yes, the fault isrooted in the local end. If the test shows the problem persists,the fault is rooted in the peer end. In this case, inform the peerend to troubleshoot. Loopback test: Perform self-loop at thetrunk where alarm occurs at local end. If the problem persists,it indicates that the fault is rooted in the local end. If the alarmis eliminated, it indicates that the alarm is rooted in the peerend. In this case, inform the peer end to troubleshoot.

2. Replace the trunk cable.


198005648 Control planeport of backboard joiningswitching chip is exceptional


� Description:Control plane port of backboard joining switchingchip is exceptional

� Severity:Major




Probable Cause The control plane ports of such boards as SPB/SPB_2/SDU aredown or do not send and receive packets for more than 5 min-utes.

Specific Problem The control plane ports of such boards as SPB/SPB_2/SDU aredown or do not send and receive packets for more than 5 min-utes.

System Impact Connection between the switch chip and the backplane's controlnetwork is down.

HandlingSuggestion

1. heck the corresponding port status on UIM after fault diagnosis.Y->Reset or pull out and plug the board and then end alarmhandling. N->Reset UIM and end alarm handling.

198005655 Errors detectedin DSP


� Description:Errors detected in DSP

� Severity:Major


Probable Cause 1. The HPI port fails

2. Hardware failure.

Specific Problem 1. The HPI port fails


System Impact This DSP will be blocked and no longer available. The cell of thisDSP is out of service; the subscriber using this DSP is out of ser-vice; call loss rate might increase when call traffic is high.

HandlingSuggestion

1. Reset the board.

2. Replace DSP sub-card.


198005656 Input clock ofsubcard lost


� Description:Input clock of subcard lost

� Severity:Major


Probable Cause 1. The subcard is loose.



2. The clock circuit of the subcard is damaged.

3. The clock circuit of the mother board is damaged.

Specific Problem 1. The subcard is loose.

2. The clock circuit of the subcard is damaged.

3. The clock circuit of the mother board is damaged.

System Impact The unavailable sub-card clock affects the normal operation of theboard. This may cause clock jittering, and the service that imple-ments media stream exchange through this board becomes un-stable. In the most serious case, the system clock is lost and theservice carried by the board is interrupted.

HandlingSuggestion

1. Check the subcard connection status. If the subcard is loose,tightly connect it and power it on again.

2. Replace the subcard


198005657 Error of LVDSpath frame detection


� Description:Error of LVDS path frame detection

� Severity:Major


Probable Cause Error occurs in LVDS path frame detection

Specific Problem Error occurs in LVDS path frame detection

System Impact The board might not work normally.

HandlingSuggestion

1. Check if the TFI optical fiber corresponding to this path is con-nected in position or is damaged.

2. Connect the fiber in place or replace it with anther one, andcheck if the alarm is eliminated.

3. Check if the fiber matches the optical transceiver module.

4. Replace the fiber, and check if the alarm is eliminated.

5. Switch T network board.



198005658 Failure indiagnosing link loop back oflarge T network


� Description:Failure in diagnosing link loop back of large T net-work

� Severity:Major


Probable Cause The 129th time slot loop back of LVDS has a failure.

Specific Problem The 129th time slot loop back of LVDS has a failure.

System Impact The board does not work normally.

HandlingSuggestion

1. Check if the TFI optical fiber corresponding to this path is con-nected in position or is damaged.

2. Connect the fiber in place or replace it with anther one, andcheck if the alarm is eliminated.

3. Check if the fiber matches the optical transceiver module.

4. Replace the fiber, and check if the alarm is eliminated.

5. Switch T network board.

198005660 Physical linkdown between master portand slave port


� Description:Physical link down between master port and slaveport



Probable Cause The running physical link between the master and the slave portis broken.

Specific Problem The running physical link between the master and the slave portis broken.

System Impact APS function disabled

HandlingSuggestion

1. Change another slot and check whether the alarm disappears.

Y->End.

N->Go to Step



2. Change the board and check whether the alarm disappears.

Y->End.

N->Contact ZTE Corporation.

198005661 Physical linkdown between mediainterface ports


� Description:Physical link down between media interface ports



Probable Cause The network port or board is faulty.

Specific Problem The network port or board is faulty.

System Impact The APS optical port data on the standby board cannot reach theactive board. When the active optical port is normal, the serviceis not affected. When the active optical port is faulty, APS fails toprotect optical port and thus all services carried by the optical portare interrupted.

HandlingSuggestion


2. Replace the other board, that is, the board rather than thefaulty board in active/standby configuration.

3. Replace the slot. Use the slot that supports GE channel be-tween boards. .

198005662 IDE runningovertime


� Description:IDE running overtime



Probable Cause IDE is operated for longer time.

Specific Problem IDE is operated for longer time.

System Impact When hard disk work for long time without sleep, engine will be inhigh speed spin state for long, this will influence the life of disk,and data will lose when disk be abnormal. Disk of some model



will lock the engine when it keep work for long time to protect thedisk. But this is out of the software controled, and may result indata lose when disk cannot be accessed transitorily.

HandlingSuggestion

No handling is necessary.

198005663 Component faultAlarm Property � Alarm Code:198005663

� Description:Component fault

� Severity:Major


Probable Cause Devices or sub-cards on the board operate abnormally.

Specific Problem Devices or sub-cards on the board operate abnormally.

System Impact This alarm only occurs to the IMAB. When it occurs, the IMAB cannot operate normally and the trunk borne on the board will be bro-ken. As a result, users can not access the board and the existingservices will be interrupted.

HandlingSuggestion

Replace the board.

198005665 Fault on board(GPS)


� Description:Fault on board (GPS)



Probable Cause 1. According to alarm details, alarm status falls into two types:Type A fault on board (GPS) phase-lock equipment Phase-lockequipment of this board (GPS) is in power on status The causesfor the two alarm types are described below. 1. Type A faulton board (GPS) phase-lock equipment Probable alarm causesinclude 16chip loss/out of lock, 1

2. M loss/out of lock, PP2S output loss, 8K output loss, 10M outputloss, and 1PPS loss. 2. Phase-lock equipment of this board(GPS) is in power on status The alarm cause is that the GPSmodule of ICM board is in power on status, and power on hasnot been completed.

Specific Problem 1. According to alarm details, alarm status falls into two types:Type A fault on board (GPS) phase-lock equipment Phase-lockequipment of this board (GPS) is in power on status The causesfor the two alarm types are described below. 1. Type A fault



on board (GPS) phase-lock equipment Probable alarm causesinclude 16chip loss/out of lock, 1

2. M loss/out of lock, PP2S output loss, 8K output loss, 10M outputloss, and 1PPS loss. 2. Phase-lock equipment of this board(GPS) is in power on status The alarm cause is that the GPSmodule of ICM board is in power on status, and power on hasnot been completed.

System Impact 1. Be usually determined as hardware fault, which affects systemclock. It might lead to the system clock loss and system syn-chronization failure. When system clock loss/offset occurs, itssubsequent impact on service is described below. 1.For TDMtransmission, all links based on the TDM transmission medium(including the transmission link currently in service for UE andcell transmission link) are affected. Packet loss might occur onthese links, leading to degradation of service quality. In thecase of serious packet loss, service interruption and handoverfailure will occur. Even worse, the cell might be out of service.

2. For non-TDM transmission (for example, IP transmission), Iubinterface service is affected, while Iur interface and Iu interfaceservices are not affected. The clock that Node B derives fromRNC via IEEE1588 is inaccurate. When RNC clock frequencyoffset is no more than 0.05 ppm, Node B synchronization willnot fail, but success rate of inter-RNC inter-Node B soft han-dover might fall. When RNC clock frequency offset exceeds 0.5ppm, Node B will fail to lock the clock. In this case, Node B willoscillate freely and success rate of inter-Node B soft handovermight fall.

HandlingSuggestion

1. On NMS fault management interface, view alarm Details whereError type information is given. Locate the correspondingalarm handling suggestion according to the error type. Thealarm handling suggestions that correspond to the errortypes are described below. 1.Type A Fault on Board (GPS)Phase-lock Equipment 1) On NMS test management interface,perform diagnostic test on ICM board. Check the workingstatus of the GPS module. If Class A fault persists in theGPS module, replace the board. 2) Check if output clock lossoccurs. If yes, replace the board.

2. Phase-lock Equipment of This Board (GPS) Is in Power-on Sta-tus If the alarm persists, hardware fault might exist. Replacethe board.

198005667 E1 is loopedback


� Description:E1 is looped back

� Severity:Minor


Probable Cause 1. User has set loop back.



2. Transmission is looped back by provider.

3. Local board is faulty.

4. Remote board is faulty.

5. Loop back applied on DDF.

Specific Problem 1. User has set loop back.

2. Transmission is looped back by provider.

3. Local board is faulty.

4. Remote board is faulty.

5. Loop back applied on DDF.

System Impact 1. ata can not be sent out because of the loopback E1.

HandlingSuggestion

1. Disconnect the loopback E1.

2. Restart the board.



198005668 Cross-linked E1alarm


� Description:Cross-linked E1 alarm

� Severity:Minor


Probable Cause 1. elf board has cross-linked E1.

Specific Problem 1. elf board has cross-linked E1.

System Impact 1. ata can not be sent out because of cross-linked E1.

HandlingSuggestion

1. Disconnect the cross-linked E1, Wait for 1 minute and checkwhether the alarm disappears.

2. Restart the board and check whether the alarm disappears.

3. Replace the board by another one and check whether the alarmdisappears.

4. Replace the board connected with this board, check whetherthe alarm disappears.



198005669 Synchronizationstatus check of FPGA failed


� Description:Synchronization status check of FPGA failed



Probable Cause Synchronization status check of FPGA and SPI4/VSC872/VSC874failed. It's usually caused by hardware exceptions. For example,the clock chip works abnormally.

Specific Problem Synchronization status check of FPGA and SPI4/VSC872/VSC874failed. It's usually caused by hardware exceptions. For example,the clock chip works abnormally.

System Impact If synchronization status check of FPGA fail, Media can not receiveor send data normally. And the board will reset for the exceptionof the media check frame.

HandlingSuggestion

Replace the board.

198005671 Sending orreceiving packets using thecascade ports inner boardfailed


� Description:Sending or receiving packets using the cascadeports inner board failed



Probable Cause 1. The subcard GCS of UIM2 is not inserted in position.

2. The subcard GCS of UIM2 has hardware faults.

3. The UIM2/CHUB/GUIM board has hardware faults.

Specific Problem 1. The subcard GCS of UIM2 is not inserted in position.

2. The subcard GCS of UIM2 has hardware faults.

3. The UIM2/CHUB/GUIM board has hardware faults.

System Impact 1. Cascade ports inner UIMC/GUIM/CHUB functions abnormally.Packets may be lost, and even worse, link disconnection mayoccur on the control planes of some boards. For active/standbyconfiguration, there are two cases: 1. If the active board is ab-normal while the standby board is normal, the system performs



active/standby switchover. Thus, the standby board takes overthe services of the faulty active board. In this case, the serviceis not affected.

2. If both the active and standby boards are abnormal, ac-tive/standby switchover is forbidden. In this case, the serviceis interrupted because the faulty board cannot restore to thenormal status.

HandlingSuggestion

1. Check the GCS subcard connection on the board. If the subcardis loosely inserted, tightly insert it and wait for the board to bepowered on.

2. Replace the GCS subcard.

3. Replace the UIM2/GUIM/CHUB board.

198005893 Memory checkfailed


� Description:Memory check failed



Probable Cause Memory check failed.

Specific Problem Memory check failed.

System Impact The operation related to the memory maybe failed.

HandlingSuggestion

1. Make records of the alarm information.

2. Replace the board or subcard.

198006400 Cx29704 runsabnormally


� Description:Cx29704 runs abnormally

� Severity:Minor


Probable Cause It is the chip fault. If it can be recovered immediately, it is a falsealarm. If it can not be recovered, it must result from some chipbugs. In that case, it needs to reset the board.

Specific Problem It is the chip fault. If it can be recovered immediately, it is a falsealarm. If it can not be recovered, it must result from some chipbugs. In that case, it needs to reset the board.



System Impact The board does not work normally.

HandlingSuggestion

It is the chip fault. Please contact ZTE Corporation to replace theboard.

198015874 Data traffic toPSN board is congested


� Description:Data traffic to PSN board is congested

� Severity:Major


Probable Cause 1. The traffic flow to the board is excessive.

2. The PSN board in the same shelf is abnormal.

3. The board has hardware faults.

Specific Problem 1. The traffic flow to the board is excessive.

2. The PSN board in the same shelf is abnormal.

3. The board has hardware faults.

System Impact The services carried by the board are unstable. In most seriouscase, all services carried by the board are interrupted.

HandlingSuggestion

1. On NMS fault management interface, check if the PSN in thesame shelf has generated related alarms. If yes, follow thesuggestions on handling the related alarms. The related alarmis as follows: 19456 All high-speed links between line card andpackage switching board are out of synchronism

2. Unplug and plug the board.


198015875 GLI table lookupfailed


� Description:GLI table lookup failed

� Severity:Minor


Probable Cause 1. L1 table or L2 table error.

2. Destination IP of packets or hardware is error.



Specific Problem 1. L1 table or L2 table error.

2. Destination IP of packets or hardware is error.

System Impact Packets would be dropped which would cause poor voice qualityand other problems.

HandlingSuggestion

Switch the master port to the partner board.

198015876 GLI exceptionpackets statistic overthreshold


� Description:GLI exception packets statistic over threshold

� Severity:Minor


Probable Cause 1. Connection between fiber and optic modules is not perfect.

2. Something wrong with fiber optic module.

3. Board hardware error.

Specific Problem 1. Connection between fiber and optic modules is not perfect.

2. Something wrong with fiber optic module.

3. Board hardware error.


HandlingSuggestion

1. Check the connection between fiber and optic modules.

2. Reboot the board.

198015877 GLIQVSRAM/DRAM error


� Description:GLIQV SRAM/DRAM error

� Severity:Minor


Probable Cause 1. SRAM of GLIQV is error.

2. DRAM of GLIQV is error.

3. Micro engine of GLIQV is error.



Specific Problem 1. SRAM of GLIQV is error.

2. DRAM of GLIQV is error.

3. Micro engine of GLIQV is error.


HandlingSuggestion


2. Change the master port to slave port.

3. Replace the board with a new board.

198019456 All high-speedlinks between line card andswitching boards are out ofsynchronization


� Description:All high-speed links between line card and switch-ing boards are out of synchronization



Probable Cause 1. Switching board hardware is abnormal.

2. Line card hardware is faulty.

Specific Problem 1. Switching board hardware is abnormal.

2. Line card hardware is faulty.

System Impact 1. All services on the equipment are down if the alarm is causedby Cause 1 or Cause

2. All services on the line card are affected if the alarm is causedby Cause

3. If the service is not configured in master/slave or load sharingmode, all services on the line card will be down. If the serviceis configured in master/slave or load sharing mode, all serviceson the line card will soon be restored after being down tem-porarily.

HandlingSuggestion

1. Check whether PSN board reboots repeatedly. If yes, Checkwhether the PSN board type configured is consistent with thePSN board type actually in use. If inconsistent (for example,the configured board type is PSN4V and the board type actuallyin use is PSN8V), modify board type configuration or replacethe board actually in use to keep consistency between boardconfiguration and the board in use. If consistent, PSN boardhardware might be faulty. In this case, replace PSN board.



2. If the alarm occurs in line card, check if the same alarm occursin other line card(s) located in the same shelf with the faultyline card. If the same alarm occurs in all other line cards,PSN board might be faulty. Reboot PSN board and check ifthe line card alarms are restored. If alarms are not restored,replace PSN board. If merely the line card where this alarmoccurs reboots repeatedly, replace the board where the alarmis generated.

198019465 CSIX RX and TXpackets is abnormal


� Description:CSIX RX and TX packets is abnormal



Probable Cause 1. Signal is unstable when rack or board is powering on.

2. Switch chip is abnormal.

Specific Problem 1. Signal is unstable when rack or board is powering on.

2. Switch chip is abnormal.

System Impact The transceiver of the media plane is exceptional.

HandlingSuggestion

1. Reset the board.


198019712 APS channelmismatched


� Description:APS channel mismatched

� Severity:Major


Probable Cause 1. Fiber connection is wrong.

2. APS backup mode is configured differently between local endand opposite end.

3. APS protection mode is configured differently between localend and opposite end.

4. The opposite equipment is faulty.

Specific Problem 1. Fiber connection is wrong.





4. The opposite equipment is faulty.

System Impact APS automatic protection switching function is paralyzed. Whenthe working optical port is abnormal, the protection optical portwill not work, leading to service interruption on this optical port.

HandlingSuggestion

1. Check fibber connection. Check fibber connection at both ends.Ensure that the work optical ports at both ends are intercon-nected, and the protection optical ports at both ends are in-terconnected. On NMS configuration management interface,locate the relevant board in the rack. Right-Click the boardand open board properties page. Click Optical port APS pro-tection to view the "Work optical port" and "Protection opticalport" configured at local end.

2. Check APS backup mode configuration at both ends. CheckAPS backup mode (1 1 or 1:1) at local end to ensure con-figuration consistency at both ends. On NMS configurationmanagement interface, locate the relevant board in the rack.Right-Click the board and open board properties page. ClickOptical port APS protection in the shortcut menu to view the"Protection Type" (1+1 or 1:1).

3. Check APS protection direction at both ends. Check APS pro-tection direction (unidirectional or bidirectional) configured atlocal end. Ensure configuration consistency at both ends. OnNMS configuration management interface, locate the relevantboard in the rack. Right-Click the board and open board prop-erties page. Click Optical port APS protection to view the "Pro-tection Direct" (unidirectional or bidirectional).

4. Check whether APS is supported by the opposite equipment.Check whether APS configuration is correct and has taken ef-fect.

198019713 APS modemismatched


� Description:APS mode mismatched

� Severity:Major


Probable Cause 1. Fiber connection is wrong.



Specific Problem 1. Fiber connection is wrong.





System Impact 1. When fibber connection is correct and the working optical portcan work normally, services won't be affected.

2. When the working optical port is faulty, APS automatic protec-tion switching function doesn't work, and services carried viathis optical port will be interrupted due to lack of protection.

HandlingSuggestion

1. Check fibber connection. Check fibber connection at both ends.Ensure that the work optical ports at both ends are intercon-nected, and the protection optical ports at both ends are in-terconnected. On NMS configuration management interface,locate the relevant board in the rack. Right-Click the boardand open board properties page. Click Optical port APS pro-tection to view the "Work optical port" and "Protection opticalport" configured at local end.

2. Check APS backup mode configuration at both ends. CheckAPS backup mode (1+1 or 1:1) at local end to ensure con-figuration consistency at both ends. On NMS configurationmanagement interface, locate the relevant board in the rack.Right-Click the board and open board properties page. ClickOptical port APS protection to view the "Protection Type" (1+1or 1:1).

3. Check APS protection direction at both ends. Check APS pro-tection direction (unidirectional or bidirectional) configured atlocal end. Ensure configuration consistency at both ends. OnNMS configuration management interface, locate the relevantboard in the rack. Right-Click the board and open board prop-erties page. Click Optical port APS protection to view the "Pro-tection Direct" (unidirectional or bidirectional).

198019714 APSconfiguration alarm


� Description:APS configuration alarm

� Severity:Major


Probable Cause Optical interface are not configured for APS in 1:1 mode.

Specific Problem Optical interface are not configured for APS in 1:1 mode.

System Impact The board can not enter into normal working status. All boardservices fail to be established.

HandlingSuggestion

1. If board backup mode is configured as 1:1 or 1+1 and SDHoptical interface is needed, at least one set of APS protectionneeds to be configured. To configure APS protection: On NMSconfiguration management interface, locate the relevant board



in the rack. Right-Click the board and open board propertiespage. Click Optical port APS protection.

2. If board master/slave mode is not needed, modify boardbackup mode into. To configure board backup mode: Deletethe relevant board on NMS configuration management inter-face. Then recreate the board. Select board backup mode as"None" during board creation.

3. If board backup mode is configured as 1:1 and no SDH opticalinterface is required, modify the board backup mode into 1+1.To configure board backup mode: Delete the relevant boardon NMS configuration management interface. Then recreatethe board. Select board backup mode as "1+1" during boardcreation.

198019715 MS APS channelgets errors


� Description:MS APS channel gets errors

� Severity:Major


Probable Cause 1. APS Channel between Master and Slave Board gets hardwarefault.

2. The connection on the backplane between the slot and theneighboring slot gets errors.

Specific Problem 1. APS Channel between Master and Slave Board gets hardwarefault.

2. The connection on the backplane between the slot and theneighboring slot gets errors.

System Impact 1. ASP function is affected.

2. The board master/slave function is affected.

HandlingSuggestion



3. Replace the neighboring board.

4. Replace the slots .



198019968 No response torequest L2 Forwarding Tableinformation from DBS.


� Description:No response to request L2 Forwarding Table infor-mation from DBS.

� Severity:Major


Probable Cause 1. Omp is not powered on normally.

2. Control plane messages are delayed.

Specific Problem 1. Omp is not powered on normally.

2. Control plane messages are delayed.

System Impact 1. If the alarm is reported by UIM, the media stream of the shelfwhere UIM is located is blocked.

2. If the alarm is reported by GSC, the media stream betweenshelves is blocked.

HandlingSuggestion

1. Restart OMP board to see if it works normally.

Y->If so, go to "2".

N->If not, go to "4".

2. Restart UIM/GSC board to see if it works normally.



3. check if the alarm disappears.

Y->If not, go to "4".

N->If so, go to "5".

4. Record detailed information and contact ZTE Corporation.

5. Finish the alarm handling.

198019969 No response torequest L2 Forwarding Tableport information from SCS.


� Description:No response to request L2 Forwarding Table portinformation from SCS.



� Severity:Major


Probable Cause 1. System control process on UIM/GSC board is not powered onnormally.

2. The number of IP addresses configured for sub-units in oneshelf is more than 200.

Specific Problem 1. System control process on UIM/GSC board is not powered onnormally.

2. The number of IP addresses configured for sub-units in oneshelf is more than 200.

System Impact 1. If the alarm is reported by UIM, the media stream of the shelfwhere UIM is located is blocked.

2. If the alarm is reported by GSC, the media stream betweenshelves is blocked.

HandlingSuggestion

1. If the alarm is reported by UIM: 1.Restart UIM board to see ifit works normally.



2. Log in OAM background and enter into protocol mode to viewIP configuration of the port by using “show ip interface brief”command. Check if the number of IP addresses configured forsub-units in one shelf is more than 200.



3. Delete some IP addresses to make the number less than 200.Check if the alarm is still existing.




5. Finish the alarm handling. If the alarm is reported by GSC:1.Check if the GSC board is in working state

Y->If the GSC board is in working state,go to "2"

N->If not,go to "5" 2.Check if the optical fiber is connectedcorrectly Y->If not,go to "3" N->If so,go to "4" 3.Check if thealarm still exists after connecting the optical fiber correctlyY->If so,go to "4" N->If not,go to "6" 4.Restart GSC boardto see if the alarm still exists Y->If so,go to "5" N->If not,goto "6" 5.Record detailed information and contact ZTE Corpora-tion.




198019970 Resource boardcan't get L2 ForwardingTable.


� Description:Resource board can't get L2 Forwarding Table.

� Severity:Major


Probable Cause 1. The type of the shelf is not BUSN/BGSN.

2. UIM board on the shelf is not powered on normally.

3. Control plane messages are blocked.

Specific Problem 1. The type of the shelf is not BUSN/BGSN.

2. UIM board on the shelf is not powered on normally.

3. Control plane messages are blocked.

System Impact The resource board which has reported the alarm will be unable toforward media data.

HandlingSuggestion

1. Check if the resource shelf is BUSN/BGSN shelf and UIM boardon the shelf is powered on normally.

Y->If the shelf is not BUSN/BGSN shelf or UIM board is notpowered on normally, go to "2".

N->If the alarm disappears when the shelf is BUSN/BGSN shelfand UIM board is powered on normally, go to "4", otherwise,go to "3".

2. Replace resource shelf with BUSN/BGSN shelf and configurethe rack again, make sure that the UIM board is powered onnormally. Check if the alarm disappears.

Y->If not, go to "3".

N->If so, go to "4".



198025601 TSNB internalconnection chip fault


� Description:TSNB internal connection chip fault

� Severity:Major




Probable Cause Connection chip (73273/73260) faults on TDM Switch NetworkBoard cause some 129 time slots of HW having connection faults.

Specific Problem Connection chip (73273/73260) faults on TDM Switch NetworkBoard cause some 129 time slots of HW having connection faults.

System Impact If the fault occurs on master board, board state will be changed toslave; slave board will be reset immediately.

HandlingSuggestion

1. Try to replace the board and check if the alarm is eliminated.

2. Please contact ZTE Corporation.

198025602 TDM switchabnormal


� Description:TDM switch abnormal

� Severity:Minor


Probable Cause 1. Check for any clock alarms.

2. TDM Switch chip is faulty

3. Wrong board in configured slot.

Specific Problem 1. Check for any clock alarms.

2. TDM Switch chip is faulty

3. Wrong board in configured slot.

System Impact The link with abnormal connection is interrupted. Accordingly, ser-vices are affected.

HandlingSuggestion

1. In NMS Configuration Management interface, view the config-uration of IMA links. Do the values of HW and TS fields config-ured for IMA links conflict (for example, two A ends are config-ured with the same B end). If yes, modify the configuration.

2. Replace the faulty board.

198026116 PP2S outputclock lost


� Description:PP2S output clock lost

� Severity:Major


Probable Cause Hardware is faulty.



Specific Problem Hardware is faulty.

System Impact 1. If it is caused by the master clock board, the system will failto get clock. Because of this, all clock-related boards can notwork normally and services will be interrupted. The relevantboards include IMA protocol processing board and interfaceboard with HW process capability.

2. If it is caused by the slave clock board, services will not beaffected.

HandlingSuggestion

1. If the alarm is reported by master board rather than slaveboard, perform master/slave switching.

2. Replace the board where the alarm is reported.

198026117 PP2S clockreference lost


� Description:PP2S clock reference lost

� Severity:Major




System Impact The system can not get wanted clock, therefore all clock-relatedprocesses are abnormal.

HandlingSuggestion

1. If the board where the alarm is declared is ICM, please replacethe board.

2. If the board where the alarm is declared is CLKG: Check theconnection between CLKG and GCM. Replace the CLKG. Re-place the GCM.

198026118 16CHIP clockreference lost


� Description:16CHIP clock reference lost

� Severity:Major






System Impact The system can not get wanted clock, therefore all clock-relatedprocesses are abnormal.

HandlingSuggestion

Replace the board.

198026127 Loss of Level 3reference source clock


� Description: Loss of Level 3 reference source clock

� Severity:Minor


Probable Cause 1. Input clock reference is in unavailable status for no more than10 minutes. Probable causes include: 1. Clock reference inputis abnormal.

2. The configured clock reference does not exist.

Specific Problem 1. Input clock reference is in unavailable status for no more than10 minutes. Probable causes include: 1. Clock reference inputis abnormal.


System Impact When all configured clock reference sources are lost, the clockboard comes to free running or hold-over state. Accuracy of out-put clock is determined by the crystal oscillator of clock board. Noimpact on service.

HandlingSuggestion

1. Re-connect the input clock reference.

2. For the clock reference not in use, delete the corresponding“Circuitry Clock Reference” configuration on NMS configurationmanagement interface (board property).

198026128 Loss of Level2reference source clock


� Description: Loss of Level2 reference source clock

� Severity:Major


Probable Cause 1. Input clock reference is in unavailable status for more than 10minutes and less than 24 hours. Probable causes include: 1.Clock reference input is abnormal.




Specific Problem 1. Input clock reference is in unavailable status for more than 10minutes and less than 24 hours. Probable causes include: 1.Clock reference input is abnormal.


System Impact When all configured clock reference sources are lost, the clockboard comes to free running or hold-over state. Accuracy of out-put clock is determined by the crystal oscillator of clock board. Theclock loss leads to synchronization failure between system clockand clock reference source. Service interruption might occur. Thesystem will not be affected if the following two events happen to-gether. Input clock reference source is lost. The phase-lockedloop locks other clock reference source.

HandlingSuggestion



198026129 Loss of Level1reference source clock


� Description:Loss of Level1 reference source clock



Probable Cause 1. Input clock reference is in unavailable status for more than 24hours. Probable causes include: 1. Clock reference input isabnormal.


Specific Problem 1. Input clock reference is in unavailable status for more than 24hours. Probable causes include: 1. Clock reference input isabnormal.


System Impact When all configured clock reference sources are lost, the clockboard comes to free running or hold-over state. Accuracy of out-put clock is determined by the crystal oscillator of clock board. Theclock loss leads to synchronization failure between system clockand clock reference source. Service interruption will occur. Thesystem will not be affected if the following two events happen to-gether. Input clock reference source is lost. The phase-lockedloop locks other clock reference source.

HandlingSuggestion





198026131 CLKG boardPLL is unlocked. Clock willdrift


� Description:CLKG board PLL is unlocked. Clock will drift

� Severity:Minor


Probable Cause Hardware fault of board

Specific Problem Hardware fault of board

System Impact System could not get the needed clock, which will cause processingabnormity related to the clock.

HandlingSuggestion

1. If the alarm is reported by the master board, and the slaveboard is good, perform master/slave changeover operation.

2. Replace the fault board.

198026133 Output clock lostAlarm Property � Alarm Code:198026133

� Description:Output clock lost

� Severity:Major




System Impact 1. If this alarm occurs on the master board, system clock syn-chronization will fail and services will be interrupted.

2. If this alarm occurs on the slave board, services will not beaffected.

HandlingSuggestion

1. If the alarm is declared by master board rather than slaveboard, perform master/slave switching.

2. Replace board.



198028672 80g chipabnormal


� Description:80g chip abnormal



Probable Cause 80g detects that the GLIQP board restarts, or the 80g chip is ab-normal.

Specific Problem 80g detects that the GLIQP board restarts, or the 80g chip is ab-normal.

System Impact Media plane messages are partially lost or unavailable.

HandlingSuggestion

Restart the board for which the alarm is reported. Replace theboard with a good one if the alarm still exists. Contact ZTE. ifreplacing the board does not work.

198029952 802.3ah link faultAlarm Property � Alarm Code:198029952

� Description:802.3ah link fault

� Severity:Major


Probable Cause Link Fault: The physical layer has determined a fault that occurredin the receive direction of the local DTE Dying Gasp: An unrecov-erable local failure condition has occurred Critical Event: An un-specified critical event has occurred

Specific Problem Link Fault: The physical layer has determined a fault that occurredin the receive direction of the local DTE Dying Gasp: An unrecov-erable local failure condition has occurred Critical Event: An un-specified critical event has occurred

System Impact Link Fault: The port can't receive data, the operations will inter-rupt. Dying Gasp: The port can't receive data, the operations willinterrupt. Critical Event: The 802.3ah is failed, can't detect thefault of link.

HandlingSuggestion

1. Link Fault: 1. Check the peer is or not right.

2. If right, change the optical fiber and check the alarm.

3. If the alarm is alive, change the and check the alarm.

4. If the alarm is alive, change the board. Dying Gasp: Checkthe peer is or not down. Critical Event: 1. Check the 802.3ahis or not enable, if it is disable, it can't receive PDU. 2. If the802.3ah is enable, if the port is optical, check the alarm of LinkFault is or not alive, if the alarm is alive, the port can't receive



the PDU 3. Or not, change the good network cable. 4. If thealarm is alive, change the peer board.

198030208 Fault alarm ofCFM


� Description:Fault alarm of CFM

� Severity:Minor


Probable Cause 1. xconCCMdef: The MAID of the received CCM dose not exactlymatch the MAID configured in the receiving MEP. errorCCMdef:1. The MEPID in the received CCM is not configured in thereceiving MEP.

2. The MEPID in the received CCM matches the MEPID of the re-ceiving MEP.

3. The CCM interval filed in the received CCM dose not matchthe configured for the receiving MEP. someREMPCCMdef: TheMEP is not receiving CCM in timeout. someRDIdef: The MEPis receiving CCM that have the RDI. someAISdef: The MEP isreceiving AIS.

Specific Problem 1. xconCCMdef: The MAID of the received CCM dose not exactlymatch the MAID configured in the receiving MEP. errorCCMdef:1. The MEPID in the received CCM is not configured in thereceiving MEP.

2. The MEPID in the received CCM matches the MEPID of the re-ceiving MEP.

3. The CCM interval filed in the received CCM dose not matchthe configured for the receiving MEP. someREMPCCMdef: TheMEP is not receiving CCM in timeout. someRDIdef: The MEPis receiving CCM that have the RDI. someAISdef: The MEP isreceiving AIS.

System Impact 1. xconCCMdef: The configure of MD is error. errorCCMdef: Theconfigure of MEP in MA is error. someREMPCCMdef: 1. theother mep is not enable.

2. the link is fault, mep can't receive PUD. someRDIdef: The re-ceive of the last MEP is error. someAISdef: The receive of theformer MEP is error.

HandlingSuggestion

1. xconCCMdef: Check the configure of the peer MD. errorC-CMdef: Check the configure of all MEP in MA. someREMPC-CMdef: 1. Check the fault of the link

2. Check the other MEP in MA is enabled or not. someRDIdef:Check the alarm of the last MEP. someAISdef: Check the alarmof the former MEP.



198066033 T-net center isfault


� Description:T-net center is fault

� Severity:Major


Probable Cause The big T-net center board has a fault.

Specific Problem The big T-net center board has a fault.

System Impact T-net related resource is unavailable.

HandlingSuggestion

1. Replace the slot.


198066038 The version ofthe EPU does not accordwith that of the RPU


� Description:The version of the EPU does not accord with thatof the RPU

� Severity:Major


Probable Cause The version of the EPU does not accord with that of the RPU.

Specific Problem The version of the EPU does not accord with that of the RPU.

System Impact EPU is not powered on normally.

HandlingSuggestion

Replace the version of EPU consistent with the version of RPU. Ifthe alarm still exists, please contact ZTE Corporation.



198066070 Board offline orCPU in reset status for along period


� Description:Board offline or CPU in reset status for a long pe-riod

� Severity:Major


Probable Cause 1. The board is not in position.


Specific Problem 1. The board is not in position.


System Impact If the board is normal, but its in-position indicator has a fault, thenthis alarm does not affect services. The board is in blocked status,no services can be accessed. If the board acts as a resource board,its resources can not be used.

HandlingSuggestion

1. Check whether the board is in position. If not, insert the board.

2. Plug/unplug the board.


4. Replace the slot


198087000 Dry contactalarm 1


� Description:Dry contact alarm 1

� Severity:


Probable Cause The device connected with dry contact 1 had alarm.

Specific Problem The device connected with dry contact 1 had alarm.

System Impact User defined



HandlingSuggestion

None




� Severity:





HandlingSuggestion

None




� Severity:





HandlingSuggestion

None




� Severity:







HandlingSuggestion

None




� Severity:





HandlingSuggestion

None




� Severity:







HandlingSuggestion

None




� Severity:





HandlingSuggestion

None




� Severity:





HandlingSuggestion

None




� Severity:







HandlingSuggestion

None




� Severity:





HandlingSuggestion

None




� Severity:







HandlingSuggestion

None




� Severity:





HandlingSuggestion

None

198087012 EAM dry contact1 alarm


� Description:EAM dry contact 1 alarm



Probable Cause The device connected with EAM dry contact 1 had alarm.

Specific Problem The device connected with EAM dry contact 1 had alarm.


HandlingSuggestion

None











HandlingSuggestion

None









HandlingSuggestion

None











HandlingSuggestion

None









HandlingSuggestion

None









HandlingSuggestion

None











HandlingSuggestion

None









HandlingSuggestion

None

198087100 CMM/CMBFLASH programming failure


� Description:CMM/CMB FLASH programming failure

� Severity:Minor


Probable Cause There are too many FLASH programming times and read/write er-ror.

Specific Problem There are too many FLASH programming times and read/write er-ror.

System Impact No version can be downloaded or read.

HandlingSuggestion

User cannot solve this problem which generally due to FLASH chipmalfunction. Please replace CMM/CMB board in time.



198087101 HW link brokenAlarm Property � Alarm Code:198087101

� Description:HW link broken

� Severity:Minor


Probable Cause BTS internal communication breaks

Specific Problem BTS internal communication breaks

System Impact Site can't work normally.

HandlingSuggestion

1. Start HW self-loop test to check whether the cable connectiongoes wrong.

2. If all of DTRU fail to build link, re-plug CMB board.

3. If the software has problem, upgrade it.

198087102 Powerovervoltage/undervoltagealarm


� Description:Power overvoltage/undervoltage alarm

� Severity:Minor


Probable Cause CMM/CMB power voltage is out of adjustment range

Specific Problem CMM/CMB power voltage is out of adjustment range

System Impact CMM/CMB can't work normally.

HandlingSuggestion

Power LED displays alarm; please replace CMM/CMB board as soonas possible.

198087103 13M input clockfailure


� Description:13M input clock failure

� Severity:Minor




Probable Cause CMM/CMB clock unit works abnormally

Specific Problem CMM/CMB clock unit works abnormally

System Impact BTS inner transmission links broken, frame number error and fre-quency synthesizer abnormal.

HandlingSuggestion

1Test transmission index. If the transmission continuously hasover-2Hz frequency offset in 4 seconds or the single frequencyadjustment is more than 4 Hz for 15 times in 6 minutes, it is nec-essary to notify the engineer to adjust transmission. 2Reset CMBboard and check whether the alarm disappears. 3If the alarm doesnot disappear, replace CMB board.

198087104 Frame No.inconsistent betweensoftware and hardware


� Description:Frame No. inconsistent between software andhardware

� Severity:Minor


Probable Cause Frame number accumulation is interrupted due to interferencelevel on the circuit.

Specific Problem Frame number accumulation is interrupted due to interferencelevel on the circuit.

System Impact Frame number accumulation is interrupted due to interferencelevel on the circuit.

HandlingSuggestion

If the fault cannot restore, the problem may result from CMM/CMBclock error, please replace the board in time.

198087105 FCLK clockfailure


� Description:FCLK clock failure

� Severity:Minor






System Impact It induces BTS inner transmission links broken, frame number er-ror and abnormal frequency synthesizer.

HandlingSuggestion


198087106 SYNCLK clockfailure


� Description:SYNCLK clock failure

� Severity:Minor




System Impact It induces BTS inner transmission links broken, frame number er-ror and abnormal frequency synthesizer.

HandlingSuggestion


198087107 Master and slavecommunication link failure


� Description:Master and slave communication link failure



Probable Cause Standby CMM/CMB board is not powered on, or the communicationbetween active-standby CMM/CMB board has error.

Specific Problem Standby CMM/CMB board is not powered on, or the communicationbetween active-standby CMM/CMB board has error.

System Impact Master and slave CMM/CMB board cannot switch with each other.



HandlingSuggestion

1. Re-plug CMB board.

2. If the software has problem, upgrade it.

198087108 StandbyCMM/CMB board is notin position.


� Description:Standby CMM/CMB board is not in position.



Probable Cause Standby CMM/CMB board is not inserted

Specific Problem Standby CMM/CMB board is not inserted

System Impact Master CMB board cannot swith into the slave when it is abnoraml,and the system reliability reduces.

HandlingSuggestion

Check whether standby board is present in the rack.If so, resetor re-insert the board ; Check if standby board state is normal(normal state: power LED lights; RUN LED keeps lighting); if not,insert a new CMM/CMB board accordingly.

198087109 StandbyCMM/CMB board abnormal


� Description:Standby CMM/CMB board abnormal



Probable Cause Standby CMM/CMB board is started abnormally or not insertedproperly.

Specific Problem Standby CMM/CMB board is started abnormally or not insertedproperly.

System Impact Master and slave board cannot switch with each other.

HandlingSuggestion

Check whether standby board is present in the rack.If so,pleasereset or re-insert the board (normal state: power LED lights; RUNLED keeps lighting); if not, insert a new CMB board accordingly.



198087110 CMM/CMBboard has powered off.


� Description:CMM/CMB board has powered off.

� Severity:Minor


Probable Cause CMM/CMB board has powered off.

Specific Problem CMM/CMB board has powered off.

System Impact CMM/CMB can't work normally.

HandlingSuggestion

E1 interface will bridge-connect automatically. Replace the CMBcircuit board as quickly as possible.

198087111 Master rackcommunication link alarm


� Description:Master rack communication link alarm



Probable Cause Communication link failed between slave rack and master rack.

Specific Problem Communication link failed between slave rack and master rack.

System Impact Site cannot process data and software downloading as well as op-eration maintaince, thus working abnormally.

HandlingSuggestion

(1) Check whether the cable between racks is connected or workswell. If not, let it works well. (2) Start self-check of master-slave rack communication to confirm the problem lies in CMM/CMBhardware or software process, and solve corresponding problemthen.



198087112 Communicationlink alarm between masterand slave rack (left)


� Description:Communication link alarm between master andslave rack (left)



Probable Cause Communication link from master rack to slave rack failed.

Specific Problem Communication link from master rack to slave rack failed.


HandlingSuggestion

(1) Check whether the cable between racks is connected or workswell. If not, timely connect or replace it. (2) Start self-check ofmaster-slave rack communication to confirm the problem lies inCMM/CMB hardware or software process, and solve correspondingproblem then.

198087113 Communicationlink alarm between masterand slave rack (right)


� Description:Communication link alarm between master andslave rack (right)



Probable Cause Communication link from master rack to slave rack failed.

Specific Problem Communication link from master rack to slave rack failed.


HandlingSuggestion

(1) Check whether the cable between racks is connected or workswell. If not, timely connect or replace it. (2) Start self-check ofmaster-slave rack communication to confirm the problem lies inCMM/CMB hardware or software process, and solve correspondingproblem then.



198087114 A interface E1recieves TRX alarm


� Description:A interface E1 recieves TRX alarm

� Severity:Minor


Probable Cause Situation like chip fault, clock abnormal, difference from BSC clockand poor E1 connection, etc. will induce the alarm.

Specific Problem Situation like chip fault, clock abnormal, difference from BSC clockand poor E1 connection, etc. will induce the alarm.

System Impact If it occurs once in a while, it has small impact on callings. How-ever, if it occurs frequently (once in a few minutes time), it wouldinduce abnormal callings or broken links between TRM/DTRU andBSC.

HandlingSuggestion

(1) Loop-back check whether E1 cable has malfunction. If so, redothe cable to remove cable faults. If not, turn to step 2. (2) In-sert CMM/CMB board tightly and power-on again, watch if alarmrestores. (3) Start E1 interface self-loop test process and checkwhether the result is ok. If so, the problem turns to be trans-mission fault which need to be solved. If not , turn to step 4. (4)Replace CMM/CMB board, and watch if alarm restores. (5) Replacethe rear board.

198087115 A interface E1reciever out of frame alarm


� Description:A interface E1 reciever out of frame alarm

� Severity:Minor


Probable Cause Situation like chip fault, clock abnormal, difference from BSC orbad E1 connection and CMM board not support C/F interface con-figurations (only limited in V2 series BTS) etc.will induce the alarm

Specific Problem Situation like chip fault, clock abnormal, difference from BSC orbad E1 connection and CMM board not support C/F interface con-figurations (only limited in V2 series BTS) etc.will induce the alarm

System Impact it has little influence on callings if it occurs once in a while.However,if it occurs frequently (once in a few minutes time), it would resultin abnormal callings or broken links between TRM/DTRU and BSC.

HandlingSuggestion

1. Check whether E1 cable electrical connection performs well. Ifnot, redo the cable to remove cable faults. If so, turn to step



2. Insert CMM/CMB board tightly and reset, watch if alarm re-stores.

3. If C/F interface alarm occurs, check whether CMM board hard-ware version is 030900 or 030903. If yes, only need to changeto the version 030508 CMM board (only limited to V2 seriesBTS).

4. Check if E1 interface chip could pass self test and determinewhether it is normal.

5. Start E1 interface self-loop test process and check the result.If the result is ok, the problem turns to be transmission faultwhich need to be solved. If not, turn to step

6. Replace CMM/CMB board, and watch if alarm restores.


198087116 A interfaceE1 sender forward-bit-slipindication


� Description:A interface E1 sender forward-bit-slip indication

� Severity:Minor




System Impact it has a little influence on callings if it occurs once in a while.How-ever, if it occurs frequently (once in a few minutes time), it wouldresult in abnormal callings or broken links between TRM/DTRU andBSC.

HandlingSuggestion

(1) Loop-back check whether E1 cable is malfunction. If so, redothe cable to remove cable faults. If not, turn to step 2. (2) InsertCMM/CMB board tightly and power-on again, watch if alarm re-stores. (3) Start E1 interface self-loop test process and check theresult is ok or not. If so, then it's transmission fault which needto be solved. If not, turn to step 4. (4) Replace CMM/CMB board,and watch if alarm restores. (5) Replace backboard.



198087117 A interface E1sender backward-bit-slipindication


� Description:A interface E1 sender backward-bit-slip indication

� Severity:Minor





HandlingSuggestion

(1) Loop-back check whether E1 cable has malfunction. If so, redothe cable to remove cable faults. If not, turn to step 2. (2) In-sert CMM/CMB board tightly and power-on again, watch if alarmrestores. (3) Start E1 interface self-loop test process and checkthe result. If the result is ok, the problem turns to be transmissionfault which need to be solved. If not, turn to step 4. (4) ReplaceCMM/CMB board, and watch if alarm restores. (5) Replace the rearboard.

198087118 A interface E1reciever forward-bit-slipindication


� Description:A interface E1 reciever forward-bit-slip indication

� Severity:Minor







HandlingSuggestion


198087119 A interface E1reciever backward-bit-slipindication


� Description:A interface E1 reciever backward-bit-slip indication

� Severity:Minor





HandlingSuggestion


198087120 A interface E1remote alarm


� Description:A interface E1 remote alarm

� Severity:Minor




Probable Cause The remote end possibly cannot receive data from the local due tobroken send line.

Specific Problem The remote end possibly cannot receive data from the local due tobroken send line.

System Impact BTS cannot provide service.

HandlingSuggestion


198087121 B interface E1recieves TRX alarm


� Description:B interface E1 recieves TRX alarm

� Severity:Minor





HandlingSuggestion

(1) Loop-back check whether E1 cable has malfunction. If yes,redo the cable to remove cable faults. If not, turn to step 2. (2)Insert CMM/CMB board tightly and power-on again, watch if alarmrestores. (3) Start E1 interface self-loop test process and checkthe result. If the result is ok, the problem turns to be transmissionfault which need to be solved. If not ok, turn to step 4. (4) ReplaceCMM/CMB board, and watch if alarm restores. (5) Replace the rearboard.



198087122 B interface E1reciever out of frame alarm


� Description:B interface E1 reciever out of frame alarm

� Severity:Minor





HandlingSuggestion

1. Check whether E1 cable electrical connection performs well. Ifnot, redo the cable to remove cable faults. If yes, turn to step




5. Start E1 interface self-loop test process and check the result.If the result is ok, the problem turns to be transmission faultwhich need to be solved. If not ok, turn to step 5.



198087123 B interfaceE1 sender forward-bit-slipindication


� Description:B interface E1 sender forward-bit-slip indication

� Severity:Minor







HandlingSuggestion

(1) Loop-back check whether E1 cable is malfunction. If yes, redothe cable to remove cable faults. If not, turn to step 2. (2) In-sert CMM/CMB board tightly and power-on again, watch if alarmrestores. (3) Start E1 interface self-loop test process and checkthe result is ok or not. If yes, then it's transmission fault whichneed to be solved. If not, turn to step 4. (4) Replace CMM/CMBboard, and watch if alarm restores. (5) Replace backboard.

198087124 B interface E1sender backward-bit-slipindication


� Description:B interface E1 sender backward-bit-slip indication

� Severity:Minor





HandlingSuggestion




198087125 B interface E1reciever forward-bit-slipindication


� Description:B interface E1 reciever forward-bit-slip indication

� Severity:Minor





HandlingSuggestion


198087126 B interface E1reciever backward-bit-slipindication


� Description:B interface E1 reciever backward-bit-slip indication

� Severity:Minor







HandlingSuggestion


198087127 B interface E1remote alarm


� Description:B interface E1 remote alarm

� Severity:Minor





HandlingSuggestion


198087128 C interface E1recieves TRX alarm


� Description:C interface E1 recieves TRX alarm

� Severity:Minor







HandlingSuggestion


198087129 C interface E1reciever out of frame alarm


� Description:C interface E1 reciever out of frame alarm

� Severity:Minor





HandlingSuggestion










198087130 C interfaceE1 sender forward-bit-slipindication


� Description:C interface E1 sender forward-bit-slip indication

� Severity:Minor





HandlingSuggestion


198087131 C interface E1sender backward-bit-slipindication


� Description:C interface E1 sender backward-bit-slip indication

� Severity:Minor







HandlingSuggestion


198087132 C interface E1reciever forward-bit-slipindication


� Description:C interface E1 reciever forward-bit-slip indication

� Severity:Minor





HandlingSuggestion


198087133 C interface E1reciever backward-bit-slipindication


� Description:C interface E1 reciever backward-bit-slip indication



� Severity:Minor





HandlingSuggestion


198087134 C interface E1remote alarm


� Description:C interface E1 remote alarm

� Severity:Minor





HandlingSuggestion




198087135 D interface E1recieves TRX alarm


� Description:D interface E1 recieves TRX alarm

� Severity:Minor





HandlingSuggestion


198087136 D interface E1reciever out of frame alarm


� Description:D interface E1 reciever out of frame alarm

� Severity:Minor





HandlingSuggestion










198087137 D interfaceE1 sender forward-bit-slipindication


� Description:D interface E1 sender forward-bit-slip indication

� Severity:Minor





HandlingSuggestion




198087138 D interface E1sender backward-bit-slipindication


� Description:D interface E1 sender backward-bit-slip indication

� Severity:Minor





HandlingSuggestion


198087139 D interface E1reciever forward-bit-slipindication


� Description:D interface E1 reciever forward-bit-slip indication

� Severity:Minor







HandlingSuggestion


198087140 D interface E1reciever backward-bit-slipindication


� Description:D interface E1 reciever backward-bit-slip indica-tion

� Severity:Minor





HandlingSuggestion


198087141 D interface E1remote alarm


� Description:D interface E1 remote alarm

� Severity:Minor







HandlingSuggestion


198087142 E interface E1recieves TRX alarm


� Description:E interface E1 recieves TRX alarm

� Severity:Minor





HandlingSuggestion




198087143 E interface E1reciever out of frame alarm


� Description:E interface E1 reciever out of frame alarm

� Severity:Minor





HandlingSuggestion








198087144 E interfaceE1 sender forward-bit-slipindication


� Description:E interface E1 sender forward-bit-slip indication

� Severity:Minor







HandlingSuggestion


198087145 E interface E1sender backward-bit-slipindication


� Description:E interface E1 sender backward-bit-slip indication

� Severity:Minor





HandlingSuggestion




198087146 E interface E1reciever forward-bit-slipindication


� Description:E interface E1 reciever forward-bit-slip indication

� Severity:Minor





HandlingSuggestion


198087147 E interface E1reciever backward-bit-slipindication


� Description:E interface E1 reciever backward-bit-slip indication

� Severity:Minor







HandlingSuggestion


198087148 E interface E1remote alarm


� Description:E interface E1 remote alarm

� Severity:Minor





HandlingSuggestion


198087149 F interface E1recieves TRX alarm


� Description:F interface E1 recieves TRX alarm

� Severity:Minor







HandlingSuggestion


198087150 F interface E1reciever out of frame alarm


� Description:F interface E1 reciever out of frame alarm

� Severity:Minor





HandlingSuggestion










198087151 F interfaceE1 sender forward-bit-slipindication


� Description:F interface E1 sender forward-bit-slip indication

� Severity:Minor





HandlingSuggestion


198087152 F interface E1sender backward-bit-slipindication


� Description:F interface E1 sender backward-bit-slip indication

� Severity:Minor







HandlingSuggestion


198087153 F interface E1reciever forward-bit-slipindication


� Description:F interface E1 reciever forward-bit-slip indication

� Severity:Minor





HandlingSuggestion


198087154 F interface E1reciever backward-bit-slipindication


� Description:F interface E1 reciever backward-bit-slip indication



� Severity:Minor





HandlingSuggestion


198087155 F interface E1remote alarm


� Description:F interface E1 remote alarm

� Severity:Minor





HandlingSuggestion




198087156 G interface E1recieves TRX alarm


� Description:G interface E1 recieves TRX alarm

� Severity:Minor





HandlingSuggestion


198087157 G interface E1reciever out of frame alarm


� Description:G interface E1 reciever out of frame alarm

� Severity:Minor





HandlingSuggestion










198087158 G interfaceE1 sender forward-bit-slipindication


� Description:G interface E1 sender forward-bit-slip indication

� Severity:Minor





HandlingSuggestion




198087159 G interface E1sender backward-bit-slipindication


� Description:G interface E1 sender backward-bit-slip indication

� Severity:Minor





HandlingSuggestion


198087160 G interface E1reciever forward-bit-slipindication


� Description:G interface E1 reciever forward-bit-slip indication

� Severity:Minor







HandlingSuggestion


198087161 G interface E1reciever backward-bit-slipindication


� Description:G interface E1 reciever backward-bit-slip indica-tion

� Severity:Minor





HandlingSuggestion


198087162 G interface E1remote alarm


� Description:G interface E1 remote alarm

� Severity:Minor







HandlingSuggestion


198087163 H interface E1recieves TRX alarm


� Description:H interface E1 recieves TRX alarm

� Severity:Minor





HandlingSuggestion




198087164 H interface E1reciever out of frame alarm


� Description:H interface E1 reciever out of frame alarm

� Severity:Minor





HandlingSuggestion








198087165 H interfaceE1 sender forward-bit-slipindication


� Description:H interface E1 sender forward-bit-slip indication

� Severity:Minor







HandlingSuggestion


198087166 H interface E1sender backward-bit-slipindication


� Description:H interface E1 sender backward-bit-slip indication

� Severity:Minor





HandlingSuggestion




198087167 H interface E1reciever forward-bit-slipindication


� Description:H interface E1 reciever forward-bit-slip indication

� Severity:Minor





HandlingSuggestion


198087168 H interface E1reciever backward-bit-slipindication


� Description:H interface E1 reciever backward-bit-slip indica-tion

� Severity:Minor




System Impact If it occurs once in a while, it has small impact on callings. How-ever, if it occurs frequently (once in a few minutes time), it would



induce abnormal callings or broken links between TRM/DTRU andBSC.

HandlingSuggestion


198087169 H interface E1remote alarm


� Description:H interface E1 remote alarm

� Severity:Minor





HandlingSuggestion


198087170 Temperaturealarm


� Description:Temperature alarm



Probable Cause The alarm is due to fan fault or module over high temperature.

Specific Problem The alarm is due to fan fault or module over high temperature.




HandlingSuggestion

Check whether environment temperature meets requirment. If so,continue observing and keep normal work status in the pemise ofno faults lying in other modules; If not, please improve equipmentworking environment, and replace FCM module if it is faulty.

198087171 Fannot-in-position alarm


� Description:Fan not-in-position alarm



Probable Cause Fan is not inserted or inserted in right position.

Specific Problem Fan is not inserted or inserted in right position.


HandlingSuggestion

Insert the fan or re-plug the fan and make it in right position.

198087172 Fan controlboard CPU alarm


� Description:Fan control board CPU alarm



Probable Cause CPU has faults.

Specific Problem CPU has faults.


HandlingSuggestion

1. Check error-detection circuit fault and remove it.

2. Check FCM board fault and replace FCM control board.

198087173 Fan alarmAlarm Property � Alarm Code:198087173

� Description:Fan alarm





Probable Cause Fan stops rotating due to fault

Specific Problem Fan stops rotating due to fault


HandlingSuggestion

1. Check error-detection circuit fault and remove it.

2. Check fan engine fault and replace FCM.

3. Check whether TPU alarm acquisition circuit is correct, if not,replace corresponding TRM module.

198087174 Fan environmenttemperature alarm


� Description:Fan environment temperature alarm



Probable Cause The error is caused by fan engine fault or too high temperature ofmodule .

Specific Problem The error is caused by fan engine fault or too high temperature ofmodule .

System Impact it will lead to high temperature of TRM/DTRU, and affect the wholenetwork performance.

HandlingSuggestion


198087175 Fan 1 alarmAlarm Property � Alarm Code:198087175

� Description:Fan 1 alarm





System Impact Lead to over high temperature of same layer TRX frame.

HandlingSuggestion

1. Check whether corresponding fan engine has stopped rotating.If so, replace the fan engine plug-in box; if not, turn to step



2. Check whether the lines of fan engine and fan controller hasfault. If so, turn to step 3; if not, turn to step 4.

3. Check whether fan engine cable or board-port connector hasfault. If fan engine cable has malfunction, replace the fanplug-in box. If board-port connector has error, replace fan con-troller board DFCM/FNCB.

4. Check whether error-detection circuit exists fault. If yes, re-move the alarm circuit fault; if not, turn to step

5. Check whether alarm collection of fan controller board is ab-normal. If so, replace fan controller board DFCM/FNCB; if not,turn to step

6. Check whether TRM/DTRU alarm collection circuit is abnormal.If so replace corresponding TRM/DTRU.

198087176 Fan 2 alarmAlarm Property � Alarm Code:198087176

� Description:Fan 2 alarm





System Impact Lead to over high temperature of same layer TRX frame.

HandlingSuggestion

1. Check whether corresponding fan engine stops rotating. If yes,replace the fan engine plug-in box; if not, turn to step

2. Check whether the lines of fan engine and fan controller existfault. If so, turn to step 3; if not, turn to step 4.

3. Check whether fan engine cable or board-port connector ex-ists fault. If fan engine cable has malfunction, replace the fanplug-in box. If board-port connector has error, replace fan con-troller board DFCM/FNCB.

4. Check whether error-detection circuit exists fault. If so, re-move the alarm circuit fault; if not, turn to step

5. Check whether alarm collection of fan controller board is ab-normal. If so, replace fan controller board DFCM/FNCB; if not,turn to step

6. Check whether TRM/DTRU alarm collection circuit is abnormal.If so, replace corresponding TRM/DTRU.



198087177 Fan controllermodule alarm


� Description:Fan controller module alarm



Probable Cause The alarm is due to fan engine fault or module over high temper-ature.

Specific Problem The alarm is due to fan engine fault or module over high temper-ature.

System Impact Lead to over high temperature of TRM/DTRU, and affect the wholenetwork performance.

HandlingSuggestion


198087178 Low NoiseAmplifier (LNA) alarm


� Description:Low Noise Amplifier (LNA) alarm

� Severity:Minor


Probable Cause LNA current exceeds by 30%

Specific Problem LNA current exceeds by 30%


HandlingSuggestion

Please replace AEM module as soon as possible.

198087179 Tower amplifierpower alarm


� Description:Tower amplifier power alarm





Probable Cause AEM tower amplifier power triggers alarm.

Specific Problem AEM tower amplifier power triggers alarm.


HandlingSuggestion

Please replace tower amplifier module or AEM module in time.

198087180 SWR of AEMHYCOM minor alarm


� Description:SWR of AEM HYCOM minor alarm

� Severity:Minor


Probable Cause 1. ombiner SWR exceeds 1.5 and triggers alarm.

Specific Problem 1. ombiner SWR exceeds 1.5 and triggers alarm.


HandlingSuggestion

Keep on observing and don’t replace AEM module if normal workisn's affected.

198087181 SWR of AEMHYCOM major alarm


� Description:SWR of AEM HYCOM major alarm

� Severity:Major


Probable Cause Combiner SWR exceeds 3.0 and triggers alarm.

Specific Problem Combiner SWR exceeds 3.0 and triggers alarm.




HandlingSuggestion

Please replace AEM and reset the TRM which connects to this AEM.

198087182 AEM poweralarm(BTS V2)


� Description:AEM power alarm(BTS V2)

� Severity:Major


Probable Cause AEM power triggers alarm.

Specific Problem AEM power triggers alarm.


HandlingSuggestion

Please replace AEM module as soon as possible.

198087183 AEM typealarm(BTS V2)


� Description:AEM type alarm(BTS V2)

� Severity:Major


Probable Cause the configuration of AEM type is wrong.

Specific Problem the configuration of AEM type is wrong.


HandlingSuggestion

Check whether AEM config type conforms to the actual type andwhether is inserted well and powered on. If not conforms, replaceAEM; if the type is correct, check whether the problem is backpanel transportation fault or TPU collection circuits error, and re-place corresponding cables or modules.



198087184 AEMnot-in-posion alarm (BTSV2)


� Description:AEM not-in-posion alarm (BTS V2)

� Severity:Major


Probable Cause AEM is not in position and triggers alarm.

Specific Problem AEM is not in position and triggers alarm.


HandlingSuggestion

Please replace AEM and reset the TRM which connects to this AEM.

198087185 AEM poweralarm


� Description:AEM power alarm

� Severity:Major


Probable Cause There is something wrong with AEM power.

Specific Problem There is something wrong with AEM power.

System Impact Radio transmission is affected.

HandlingSuggestion

(1) Check whether there is PA temperature alarm or fan environ-ment temperature alarm in the background. If so, address fanalarm first, and insert virtual module if there is no TRX on the rightside of TRM board. (2) Check whether the fuse of CDU is damaged.If so, replace the fuse of corresponding type. Please note: FU1 2A,FU2, 1A. (3) Pull out CDU and the same-layer DTRU module, andcheck whether the pins on the rear board are bent. If so, changethe slot or replace the rear board, and power on the board againto see if alarm restores. (If changes the slot, the background needre-configured) (4) Replace CDU.



198087186 LNA0overcurrent alarm


� Description:LNA0 overcurrent alarm

� Severity:Minor


Probable Cause LNA0 current exceeds by 30%

Specific Problem LNA0 current exceeds by 30%

System Impact The DTRU connected to this ATEM cannot work (if main sub-setLNA are all damaged) or cannot work normally (if only one LNA isdamaged).

HandlingSuggestion

(1) Check whether there is PA temperature alarm or fan environ-ment temperature alarm in the background. If so, address fanalarm first, and insert virtual module if there is no TRX on theright side of TRM board. (2) Pull out CDU and the same-layerDTRU module, and check whether the pins on the rear board arebent. If so, change the slot or replace the rear board, and poweron the board again to see if alarm restores. (If changes the slot,the background need re-configuring) (3) Replace CDU.

198087187 LNA0overcurrent alarm


� Description:LNA0 overcurrent alarm

� Severity:Minor


Probable Cause LNA1 current exceeds by 30%

Specific Problem LNA1 current exceeds by 30%

System Impact The DTRU connected to this ATEM cannot work (if main sub-setLNA are all damaged) or cannot work normally (if only one LNA isdamaged).

HandlingSuggestion

(1) Check whether there is PA temperature alarm or fan environ-ment temperature alarm in the background. If yes, address fanalarm first, and insert virtual module if there is no TRX on theright side of TRM board. (2) Pull out CDU and the same-layerDTRU module, and check whether the pins on the rear board arebent. If yes, change the slot or replace the rear board, and poweron the board again to see if alarm restores. (If changes the slot,the background need re-configuring) (3) Replace CDU.



198087188 Tower amplifier0 overcurrent alarm


� Description:Tower amplifier 0 overcurrent alarm



Probable Cause AEM tower amplifier power 0 triggers alarm.

Specific Problem AEM tower amplifier power 0 triggers alarm.

System Impact The sensitivity of corresponding DTRU UL receiver is affected.

HandlingSuggestion

(1) Check whether there is PA temperature alarm or fan environ-ment temperature alarm in the background. If yes, address fanalarm first, and insert virtual module if there is no TRX on theright side of TRM board. (2) Pull of tower amplifier power cable,and its poisition is: open BTS rear cover and pull off the socketwhich labelled X31 TA_PWR (X31 PA_PWR for the old type rack),the tower amplifier power cable connets all the way to set topPWRTA_Ln. Check whether the alarm disappears, and the powercable is useless if no tower amplifier exists.While if the alarm dis-appears when tower amplifier exists, please check whether thereis short between power cable and tower amplifier or whether PAgoes wrong. (3) Pull out CDU and the same-layer DTRU module,and check whether the pins on the rear board are bent. If yes,change the slot or replace the rear board, and power on the boardagain to see if alarm restores. (If changes the slot, the backgroundneed re-configuring). (4) Replace CDU, and reset the TRX whichconnects to it.

198087189 Tower amplifier1 overcurrent alarm


� Description:Tower amplifier 1 overcurrent alarm



Probable Cause AEM tower amplifier power 1 triggers alarm.

Specific Problem AEM tower amplifier power 1 triggers alarm.

System Impact The sensitivity of corresponding DTRU UL receiver is affected.

HandlingSuggestion

(1) Check whether there is PA temperature alarm or fan environ-ment temperature alarm in the background. If yes, address fanalarm first, and insert virtual module if there is no TRX on theright side of TRM board. (2) Pull of tower amplifier power cable,and its poisition is: open BTS rear cover and pull off the socket



which labelled X31 TA_PWR (X31 PA_PWR for the old type rack),the tower amplifier power cable connets all the way to set topPWRTA_Ln. Check whether the alarm disappears, and the powercable is useless if no tower amplifier exists.While if the alarm dis-appears when tower amplifier exists, please check whether thereis short between power cable and tower amplifier or whether PAgoes wrong. (3) Pull out CDU and the same-layer DTRU module,and check whether the pins on the rear board are bent. If yes,change the slot or replace the rear board, and power on the boardagain to see if alarm restores. (If changes the slot, the backgroundneed re-configuring). (4) Replace CDU, and reset the TRX whichconnects to it.

198087190 SWR of AEMHYCOM minor alarm


� Description:SWR of AEM HYCOM minor alarm

� Severity:Minor


Probable Cause Combiner SWR exceeds limit minorly and triggers alarm.

Specific Problem Combiner SWR exceeds limit minorly and triggers alarm.


HandlingSuggestion

(1) Check whether the connection between the CDU antennamouth and the RF jumper which connects all DTRU and CDUis tight or not, if not, fasten the connection with tool. Afterthat, reset the TRX connecting with it and check whether thealarm disappears. (2) Measure SWR of the jumper between CDUand antenna with SITEMASTER. Check whether the SWR valueexceeds standard. If yes, the antenna has fault, and then checkthe antenna system part by part upon the test result. Once thefault is found, fasten the antenna, make waterproof treatment onthe antenna and replace the antenna. Reset the TRX connectingwith it and check whether the alarm disappears. 3Replace the RFcable which connects DTRU with CDU. Reset the TRX connectingwith it and check whether the alarm disappears. 4Pull out CDUand the same-layer DTRU module, and check whether the pins onthe rear board are bent. If yes, change the slot or replace the rearboard, and power on the board again to see if alarm restores. (Ifchanges the slot, the background need re-configuring). 5ReplaceCDU, and reset the TRX which connects to it.



198087191 SWR of AEMHYCOM major alarm


� Description:SWR of AEM HYCOM major alarm

� Severity:Major


Probable Cause Combiner SWR exceeds limit severely and triggers alarm.

Specific Problem Combiner SWR exceeds limit severely and triggers alarm.


HandlingSuggestion

(1) Check whether the connection between the CDU antennamouth and the RF jumper which connects all DTRU and CDUis tight or not, if not, fasten the connection with tool. Afterthat, reset the TRX connecting with it and check whether thealarm disappears. (2) Measure SWR of the jumper between CDUand antenna with SITEMASTER. Check whether the SWR valueexceeds standard. If yes, the antenna has fault, and then checkthe antenna system part by part upon the test result. Once thefault is found, fasten the antenna, make waterproof treatment onthe antenna and replace the antenna. Reset the TRX connectingwith it and check whether the alarm disappears. 3Replace the RFcable which connects DTRU with CDU. Reset the TRX connectingwith it and check whether the alarm disappears. 4Pull out CDUand the same-layer DTRU module, and check whether the pins onthe rear board are bent. If yes, change the slot or replace the rearboard, and power on the board again to see if alarm restores. (Ifchanges the slot, the background need re-configuring). 5ReplaceCDU, and reset the TRX which connects to it.

198087192 AEM type alarmAlarm Property � Alarm Code:198087192

� Description:AEM type alarm

� Severity:Major


Probable Cause AEM type triggers alarm.

Specific Problem AEM type triggers alarm.


HandlingSuggestion

(1) Check whether there is PA temperature alarm or fan environ-ment temperature alarm in the background. If yes, address fanalarm first, and insert virtual module if there is no TRX on the rightside of TRM board. (2) Check whether AEM configuration type isconsistent with the actual type, and whether DTRU is associatedwith the background. If not, change or modify the backgroundconfiguration. (3) Check whether AEM is powered on or plugged



properly. Shut down AEM module, pull off the module and re-in-sert, turn on the power again and check whether the alarm re-stores. (4) Check whether the board DIP switch of AEM is correct.If not, adjust the DIP switch till it is correct. Power on the equip-ment again and check whether the alarm restores. (5) Pull off theAEM and same-layer DTRU module, check whether the pins on therear board are bent. If yes, replace the rear board, and power onthe board again to see if alarm restores. (6) Plug in site id, andreset CMB. About five minutes later, check whether the alarm isrecovered. (7) Replace AEM module.

198087193 AEMnot-in-posion alarm


� Description:AEM not-in-posion alarm

� Severity:Major


Probable Cause AEM is not in position and triggers alarm.

Specific Problem AEM is not in position and triggers alarm.


HandlingSuggestion

(1) Check whether there is PA temperature alarm or fan environ-ment temperature alarm in the background. If yes, address fanalarm first, and insert virtual module if there is no TRX on the rightside of TRM board. (2) Check whether AEM configuration type isconsistent with the actual type, and whether DTRU is associatedwith the background. If not, change or modify the backgroundconfiguration. (3) Check whether AEM is powered on or pluggedproperly. Shut down AEM module, pull off the module and re-in-sert, turn on the power again and check whether the alarm re-stores. (4) Check whether the board DIP switch of AEM is correct.If not, adjust the DIP switch till it is correct. Check whether thefuse on CDU is broken, if so, change the fuse of the same type.Note: FU1 2A, FU2 1A. Power on the equipment again and checkwhether the alarm restores. (5) Pull off the AEM and same-layerDTRU module, check whether the pins on the rear board are bent.If yes, replace the rear board, and power on the board again tosee if alarm restores. (6) Plug in site id, and reset CMB. About fiveminutes later, check whether the alarm is recovered. (7) ReplaceAEM module.



198087194 CHP DSP0 ofTPU initialization failure(BTSV2)


� Description:CHP DSP0 of TPU initialization failure(BTS V2)

� Severity:Minor


Probable Cause DSP software or hardware has error.

Specific Problem DSP software or hardware has error.


HandlingSuggestion

1. Download software of this DSP again.

2. Reset TRM shelf, restart DSP unit and check whether the alarmrestores. If yes, the DSP initialization error is gennerally in-duced by exterior strong disturbance, and the TRM unit canstill work normally; if the alarm doesn't restore, replace TRMmodule then.

198087195 CHP DSP1 ofTPU initialization failure


� Description:CHP DSP1 of TPU initialization failure



Probable Cause The software or hardware of DSP works abnormally.

Specific Problem The software or hardware of DSP works abnormally.


HandlingSuggestion










Probable Cause The software or hardware of DSP works abnormally.

Specific Problem The software or hardware of DSP works abnormally.


HandlingSuggestion

1. Re-Download software of this DSP.

2. Reset TRM shelf, restart DSP unit and check whether the alarmrestores. If so, the DSP initialization error is gennerally causedby exterior strong disturbance, and the TRM unit can still workswell; if the alarm doesn't restore, replace TRM module then.









HandlingSuggestion





198087198 Uplink ADC chipinitialization failure


� Description:Uplink ADC chip initialization failure

� Severity:Minor


Probable Cause Uplink ADC chip initialization failed.

Specific Problem Uplink ADC chip initialization failed.


HandlingSuggestion

1. Reset this module in order to work normally.

2. if reset is of no effect , please replace this module at once.

198087199 Uplink ADCresource unavailable


� Description:Uplink ADC resource unavailable

� Severity:Minor


Probable Cause Uplink ADC resource is not available.

Specific Problem Uplink ADC resource is not available.


HandlingSuggestion

1. Reset this module in order to work normally.

2. if reset is of no effect , please replace this module at once.

198087200 CIP resourceunavailable


� Description:CIP resource unavailable

� Severity:Minor


Probable Cause Uplink/downlink loop data demodulation failed.



Specific Problem Uplink/downlink loop data demodulation failed.


HandlingSuggestion

If this alarm occurs, and meantime there is traffic on this TRM,it indicates that the TRM is normal; if no traffic on this TRM orthe RF_LOOP test launched by OMCR failed, it means this TRM isdamaged and please replace it immediately.

198087201 Uplink failureAlarm Property � Alarm Code:198087201

� Description: Uplink failure

� Severity:Minor


Probable Cause Uplink data receiving is error.

Specific Problem Uplink data receiving is error.


HandlingSuggestion

1. Reset the module,then it maybe work properly.

2. If it is not effective after Reset, please replace this module.

198087202 TPU FLASHMemory failure(BTS V2)


� Description:TPU FLASH Memory failure(BTS V2)

� Severity:Minor


Probable Cause Beacuse too many times of FLASH programming ,read/wirte Flasherror or software calibration error.

Specific Problem Beacuse too many times of FLASH programming ,read/wirte Flasherror or software calibration error.


HandlingSuggestion

Reset this CU first, and check whether the alarm restores. Ifyes, the alarm is induced by CPU reading FLASH MEMORY datawhich caused by exterior disturbances, and the CU could work nor-mally after resetting resumes. If resetting can't restore the alarm,please replace TRM module .



198087203 Watchdogof TPU CHP DSP0overflow(BTS V2)


� Description:Watchdog of TPU CHP DSP0 overflow(BTS V2)

� Severity:Minor


Probable Cause DSP0 of channel processing unit has no response temporarily

Specific Problem DSP0 of channel processing unit has no response temporarily


HandlingSuggestion

Reset this CU first, and check whether the alarm restores. If so,the alarm is caused by DSP interior abnormal condition, and the CUcould work normally after resetting . If resetting can't restore thealarm, make BSC to start BCCH changeover strategy and replaceTRM module at the meantime.

198087204 Watchdog ofTPU CHP DSP1 overflow


� Description:Watchdog of TPU CHP DSP1 overflow






HandlingSuggestion

Reset this CU first, and check whether the alarm restores. If yest,the alarm is induced by DSP interior abnormal condition, and theCU could work normally after resetting resumes. If resetting can'trestore the alarm, replace TRM module then.











HandlingSuggestion

Reset this CU first, and check whether the alarm restores. If yest,the alarm is induced by DSP interior abnormal condition, and theCU could work normally after resetting resumes. If resetting can'trestore the alarm, replace TRM module then.









HandlingSuggestion

Reset this CU first, and check whether the alarm restores. Ifyest, the alarm is induced by DSP interior abnormal condition, andthe CU could work normally after resetting resumes. If resettingdoesn’t help on the alarm, replace TRM module then.

198087207 Watchdog ofFUC overflow


� Description:Watchdog of FUC overflow

� Severity:Minor




Probable Cause FUC program has no response temporarily

Specific Problem FUC program has no response temporarily


HandlingSuggestion

User can reset TPU to solve this prolbem. If it isn't solved, pleasereplace TRM module.

198087208 Wrongconfiguration of TPUChannel 0


� Description:Wrong configuration of TPU Channel 0



Probable Cause Parameter configuration has error or confilcts each other occur.

Specific Problem Parameter configuration has error or confilcts each other occur.


HandlingSuggestion

Wait ten minutes. If the alarm still exists,configure parametersagain from background,and synchronize them to base station.Otherwise replace TRM module.






Probable Cause Parameter configuration has error or confilcts occur.

Specific Problem Parameter configuration has error or confilcts occur.




HandlingSuggestion










HandlingSuggestion










HandlingSuggestion












HandlingSuggestion










HandlingSuggestion












HandlingSuggestion







Probable Cause Wrong configuration or configuration confilcts each other.

Specific Problem Wrong configuration or configuration confilcts each other.


HandlingSuggestion




198087216 Cell parameterconfiguration mismatch(processing error) (BTS V2)


� Description:Cell parameter configuration mismatch (process-ing error) (BTS V2)

� Severity:Minor


Probable Cause The alarm occurs when cell parameter configuration is incorrector conflicts with channel parameters and CU parameter configura-tion; or TRX actual type is not consistent to the physical board.

Specific Problem The alarm occurs when cell parameter configuration is incorrector conflicts with channel parameters and CU parameter configura-tion; or TRX actual type is not consistent to the physical board.


HandlingSuggestion

1. Wait for ten minutes. If the alarm still exists,configure param-eters again from background,and synchronize them to basestation. Otherwise check the hardware and replace TRM/DTRMmodule in time.

2. Please check whether the TRX configuration in OMCR is con-sistent with the physical board or not.

198087217 Software versionof FUC mismatch(BTS V2)


� Description:Software version of FUC mismatch(BTS V2)

� Severity:Minor


Probable Cause FUC software version load error. If one of the carriers is configuredas BCCH, then the whole cell can not work normally.

Specific Problem FUC software version load error. If one of the carriers is configuredas BCCH, then the whole cell can not work normally.




HandlingSuggestion

If it is not effective after resetting the TRM , please replace TRM .

198087218 Software versionof CHP mismatch(BTS V2)


� Description:Software version of CHP mismatch(BTS V2)

� Severity:Minor


Probable Cause CHP software version loading failed.

Specific Problem CHP software version loading failed.


HandlingSuggestion

If it is not effective after resetting the TRM , please replace TRM .

198087219 FUC has notresponsed with CMM in time(BTS V2)


� Description:FUC has not responsed with CMM in time (BTS V2)



Probable Cause MO software (has/has no) response temporarily (set by CMM)

Specific Problem MO software (has/has no) response temporarily (set by CMM)


HandlingSuggestion

1. Waiting for ten minutes and observe if the alarm restores.

2. If the alarm doesn’t restore for a long time, please re-plug andreset FUC when traffic is not busy.

3. If alarm still exists after resetting, reset CMM when traffic isnot busy.

4. If alarm still exists, replace TRM module.

5. If it is software problem, correct it and upgrade the version.



198087220 LAPDcommunication link betweenFUC and BSC broken


� Description:LAPD communication link between FUC and BSCbroken

� Severity:Major


Probable Cause L2 layer software of FUC does not communicate with BSC for acertain period

Specific Problem L2 layer software of FUC does not communicate with BSC for acertain period


HandlingSuggestion

1. Check whether other FUCs of this BTS exist this alarm, if so,check E1 line connection and whether BSC's boards such asTIC, LAPD and DSN etc. has fault . If so, identify the fault andsolve it.

2. Check the data of BSC, especially T network connection andSMB time slot relay data etc.

3. If LAPD of only one layer TRM breaks, check the line connec-tiong of back panel then.

4. If LAPD of only one TRM breaks, reset FUC then.

5. If the problem still exists, please replace TRM module.

198087221 Communicationbetween CMM and FUCbreaks (communication)(BTS V2)


� Description:Communication between CMM and FUC breaks(communication) (BTS V2)

� Severity:Minor


Probable Cause HDLC link between CMM and TPU breaks, or CMM hardware haserror, etc.



Specific Problem HDLC link between CMM and TPU breaks, or CMM hardware haserror, etc.


HandlingSuggestion

1. System keeps running, but no data configuration could be pro-cessed. If only TPU link long-time breaks, user can excludethe problem through following method: 1. Check whether TPUboard is tightly inserted.

2. Reset TPU board and check alarm status.

3. Check whether CMM board works properly.

4. Check address switch on the panel board.

5. Check whether the transimission line on the panel board is con-nected properly.

6. Judge whether it is software problem or harware problemthrough HW self-loop test, if it's hardware error, replacecorresponding modules and if it is software problem, correctand upgrade software version.

198087222 CIP of TPUinitialization failure


� Description:CIP of TPU initialization failure

� Severity:Minor





HandlingSuggestion





198087223 Wrongparameter configurationfor CIP


� Description:Wrong parameter configuration for CIP

� Severity:Minor





HandlingSuggestion

1. Check software configured parameters (frenquncy, mode,static power level), configure parmeters again from back-ground and synchronize them to BTS.

2. If above method doesn’t work, replace TRM module in time.

198087224 Watchdog ofTPU CIP overflow


� Description:Watchdog of TPU CIP overflow

� Severity:Minor


Probable Cause DSP program of demodulation module has no response temporar-ily

Specific Problem DSP program of demodulation module has no response temporar-ily


HandlingSuggestion

Reset this CU first, and check whether the alarm restores. Ifyest, the alarm is induced by DSP interior abnormal condition, andthe CU could work normally after resetting resumes. If resettingdoesn’t help on the alarm, replace TRM module.



198087225 Software versionof CIP mismatch


� Description:Software version of CIP mismatch

� Severity:Minor


Probable Cause CIP software version load error. If one of the carriers is configuredas BCCH, then the whole cell can not work normally.

Specific Problem CIP software version load error. If one of the carriers is configuredas BCCH, then the whole cell can not work normally.


HandlingSuggestion

Reset TRM, if it is of no effect, please replace TRM module.

198087226 Clock alarm forTPU and CMM


� Description:Clock alarm for TPU and CMM

� Severity:Major


Probable Cause Clock between TPU and CMM is disconnected

Specific Problem Clock between TPU and CMM is disconnected


HandlingSuggestion

1. If only this TPU alarms in the BTS, check whether rear boardline is connected properly, if yes, replace TRM.

2. If other TPUs also have such alarm, check whether CMM boardof the BTS has clock alarm, if yes, replace CMM.

198087227 TPU poweralarm(BTS V2)


� Description:TPU power alarm(BTS V2)

� Severity:Major




Probable Cause The power module on TPU board has alarm

Specific Problem The power module on TPU board has alarm


HandlingSuggestion

Please replace TRM.

198087228 TPU frame No.alarm


� Description:TPU frame No. alarm

� Severity:Minor


Probable Cause Frame clock FCLK has fault, or the frame numbers of CMM hasproblem.

Specific Problem Frame clock FCLK has fault, or the frame numbers of CMM hasproblem.


HandlingSuggestion

1. Check whether FCLK of each frame number generating point isnormal (if it is directly transported, check if the wave shape ofclock frequency distorts; if it is produced by phase lock, checkwhether there is lock lost alarm), if not, replace TRM modulethen.

2. Check transmission link (transmission clock, interface chip andbit error ratio size).

3. Check whether the synchronization source of upper-level framenumber exists alarm.

198087229 TPU CHP DSP0initialization failure


� Description:TPU CHP DSP0 initialization failure

� Severity:Minor






System Impact The 16 channeds which affect dual-carrier doesn't work properly.If this DTRU is configured as BCCH, the whole cell service is af-fected.

HandlingSuggestion

1. Re-download the software of this DSP.

2. Reset DTRU shelf and restart DSP, watch if alarm recovers.

3. Check whether environment temperature exceeds the allow-able operating enviroment temperature of equipment. If so,adjust the environment; if not, re-plug the board and checkwhether alarm restores.

4. If the alarm doesn't restore, replace corresponding DTRU then.

198087230 ADC resourceunavailable


� Description:ADC resource unavailable

� Severity:Minor


Probable Cause AD6650 resource is not available.

Specific Problem AD6650 resource is not available.

System Impact The TRM/DTRU with fault is not available. If this TRM/DTRU isconfigured as BCCH, the whole cell performance is affected.

HandlingSuggestion

1. Reset this module and make it work properly.

2. Check whether environment temperature exceeds the allow-able operating enviroment temperature of equipment. If yes,adjust the environment; if not, re-plug the board and checkwhether alarm restores.


198087231 CHP framenumbers has fault.


� Description:CHP frame numbers has fault.

� Severity:Minor


Probable Cause Frame clock FCLK has fault, and the frame numbers of FUC hasfault.



Specific Problem Frame clock FCLK has fault, and the frame numbers of FUC hasfault.

System Impact This DTRU cannot work. If this DTRU is configured as BCCH, thewhole cell service is affected.

HandlingSuggestion

1. Reset this module and make it work well.



198087232 BURSTinterruption error


� Description:BURST interruption error

� Severity:Minor


Probable Cause BURST interruption has problem, and the synchronization sourceof upper-level BURST has problem

Specific Problem BURST interruption has problem, and the synchronization sourceof upper-level BURST has problem

System Impact This DTRU cannot work. If this DTRU is configured as BCCH, thewhole cell service is affected.

HandlingSuggestion

Check whether the clock of BURST interruption generateing pointis normal. If not, replace DTRU in time.

198087233 TPU FLASHmemory failure


� Description:TPU FLASH memory failure

� Severity:Minor


Probable Cause There are two many times of FLASH programming, read/wirte er-rors or software calibration errors.

Specific Problem There are two many times of FLASH programming, read/wirte er-rors or software calibration errors.



System Impact The Baseband Processing Unit (BPU) cannot get correct softwareversion from FLASH MEMORY, the whole DTRU doesn't work prop-erly.

HandlingSuggestion

Reset this CU first, and check whether the alarm restores. If so,the alarm is iresult from CPU reading FLASH MEMORY data whichcaused by exterior disturbances, and the CU could work normallyafter resetting . If resetting doesn’t restore the alarm, replaceTRM module then.

198087234 TPU CHP DSP0watchdog overflow


� Description:TPU CHP DSP0 watchdog overflow

� Severity:Minor


Probable Cause Channel processing unit DSP0 has no response temporarily

Specific Problem Channel processing unit DSP0 has no response temporarily

System Impact DSP0 of Channel Processing Unit (CPU) has no response temporar-ily, and the control unit reload software and reinitialize the DSP.If the alarm doesn’t restore, it indicates that the software loadingon DSP fails all the time. And the problem causes two channelsof one CU not working properly. If it is configured as BCCH, thewhole cell service is affected.

HandlingSuggestion




198087235 Wrongconfiguration for TRXChannel 0


� Description:Wrong configuration for TRX Channel 0







System Impact Affect channel allocation and normal work.

HandlingSuggestion

1. Reset TRX and wait for ten minutes and if alarm still exists,reconfigure parameter .

2. Reset TRX, and then wait for 10 minutes to check if alarm re-stores.

3. Re-plug TRX module, and wait for 10 minutes to check if alarmdisappears.

4. Replace corresponding TRX module.

198087236 Wrongconfiguration of TRXChannel 1


� Description:Wrong configuration of TRX Channel 1






HandlingSuggestion















HandlingSuggestion













HandlingSuggestion







198087243 Cellconfiguration parametermismatch


� Description:Cell configuration parameter mismatch

� Severity:Minor


Probable Cause Cell parameter configuration is incorrect or conflicts with channelparameters and CIP parameter configuration

Specific Problem Cell parameter configuration is incorrect or conflicts with channelparameters and CIP parameter configuration

System Impact The BTS may not work well.

HandlingSuggestion





198087244 FUC softwareversion mismatch


� Description:FUC software version mismatch

� Severity:Minor


Probable Cause FUC software version load error. If one of the carriers is configuredas BCCH, then the whole cell can not work normally.

Specific Problem FUC software version load error. If one of the carriers is configuredas BCCH, then the whole cell can not work normally.

System Impact FUC software version load error. If one of the carriers is configuredas BCCH, then the whole cell can not work normally.

HandlingSuggestion

1. Reset the TRX, check whether the alarm is recovered.

2. Re-plug the TRX module, check whether the alarm is recov-ered.

3. Change the corresponding TRX module.



198087245 CHP softwareversion mismatch


� Description:CHP software version mismatch

� Severity:Minor




System Impact CHP DSP cannot work well. If one of carriers is configured asBCCH, the whole cell cannot work normally.

HandlingSuggestion




198087246 CU softwareversion mismatch


� Description:CU software version mismatch

� Severity:Minor




System Impact CHP DSP cannot work well. If one of carriers is configured asBCCH, the whole cell cannot work normally.

HandlingSuggestion






198087247 HDLCcommunication link betweenCMB and FUC broken


� Description:HDLC communication link between CMB and FUCbroken

� Severity:Minor


Probable Cause HDLC link between CMB and TPU breaks, or CMB hardware haserror, etc.

Specific Problem HDLC link between CMB and TPU breaks, or CMB hardware haserror, etc.

System Impact TPU communication has error,and no data can be transmissed be-tween TPU and CMB. Data configuration for FUC, CHP and CIP can-not be finished and their states can not be reported.

HandlingSuggestion

1. Check whether DTRU is plugged tightly and properly. Re-plugDTRU module, add DTRU in corresponding position accordingto the configuration, and check whether the alarm is recovered.

2. Reset DTRU board to check whether the alarm is recovered.

3. If alarms occur in all the cells, check whether CMB board worksnormally. Re-plug CMB to check whether the alarm is recov-ered.

4. Check whether the address switch on the backboard is correct.If not, adjust the switch to correct position, and check whetherthe alarm is recovered.

5. Check whether the transmission line of the rear board is con-nected correctly. Otherwise connect the line to correct positionand check whether the alarm is recovered.

198087248 LAPDcommunication link betweenFUC and BSC broken


� Description:LAPD communication link between FUC and BSCbroken

� Severity:Minor




Probable Cause L2 layer software of FUC does not communicate with BSC for acertain period

Specific Problem L2 layer software of FUC does not communicate with BSC for acertain period

System Impact The FUC doesn’t work porperly. And if the FUC is configured asBCCH-TPU, the whole cell service is affected.

HandlingSuggestion

1. Check whether other FUCs have alarm in the BTS, if all FUCsinside the base station have alarm, check whether E1 line isconnected correctly and whether TIC board, LAPD board andDSN board etc.in the BSC have alarms. if yes, dig out theproblem and resolve it.

2. Check whether BSC data configuration is correct or not, espe-cially the T net link and the time slot link of SMB data etc.

3. If only one layer of TRM LAPD breaks, then check whether rearboard line is connected correctly.

4. If only one TRM/DTRU LAPD breaks, reset the FUC and checkwhether alarm restores.

5. If the problem still exists, replace TRM/DTRU module then.

198087249 CU initializationfailure


� Description:CU initialization failure

� Severity:Minor




System Impact Modulator doesn’t work at all. And if the DTRU is configured asBCCH, the whole cell cannot work normally.

HandlingSuggestion






198087250 CU parameterconfiguration error


� Description:CU parameter configuration error

� Severity:Minor




System Impact DTRU can't work normally.

HandlingSuggestion

1. Check software configured parameters (frenquncy, mode,static power level), configure parmeters again from back-ground and synchronize them to BTS.

2. If above method doesn’t work, replace TRM module in time.

198087252 TPU poweralarm


� Description:TPU power alarm

� Severity:Major


Probable Cause The power module on TPU board has alarm

Specific Problem The power module on TPU board has alarm

System Impact This DTRU doesn’t work at all. If this DTRU is configured as BCCH,the whole cell service is affected.

HandlingSuggestion






198087253 FU framenumber error alarm


� Description:FU frame number error alarm

� Severity:Minor


Probable Cause Frame clock FCLK has problem, upper-level frame number syn-chronization source CMB has problem

Specific Problem Frame clock FCLK has problem, upper-level frame number syn-chronization source CMB has problem

System Impact This DTRU doesn’t work at all. If this DTRU is configured as BCCH,the whole cell service is affected.

HandlingSuggestion

1. Check whether FCLK of each frame number generateing pointis normal. If it is directly transported, check if the frequencyand wave shape of the clock distorts; if it is produced by phaselock, check whether there is lock lost alarm. If FCLK has mal-function, replace TRM module then.

2. Check transportation link. That is to check whether transporta-tion clock is normal, interface chip alarms or bit error ratio sizesuits.

3. Check whether the synchronization source of upper-level framenumber exists alarm.

198087254 Rx LocalOscillator (LO) PLL1 lostlock alarm


� Description:Rx Local Oscillator (LO) PLL1 lost lock alarm

� Severity:Minor


Probable Cause Clock signal is unstable or TRM Phase-Locked Loop (PLL) has fault.

Specific Problem Clock signal is unstable or TRM Phase-Locked Loop (PLL) has fault.


HandlingSuggestion

1. Check whether there is clock alarm through LMT and replacecorresponding module if alarm exists. If not exists, checkwhether TP interface 13M clock of the front panel outputs data,if no output, the problem turns to be clock error from TPU toRCU and replace TRM/DTRM module then.



2. If problem still exists, it may be credited with LO error, replaceTRM/DTRM in time then.

198087255 Rx LocalOscillator (LO) PLL2 loselock alarm


� Description:Rx Local Oscillator (LO) PLL2 lose lock alarm

� Severity:Minor





HandlingSuggestion

1. Observe whether there is clock alarm through LMT and re-place corresponding module if alarm exists. If not exists, checkwhether TP interface 13M clock of the front panel outputs data,if no output, the problem turns to be clock error from TPU toRCU and replace TRM/DTRM module then.


198087256 Tx LocalOscillator (LO) PLL1 loselock alarm


� Description:Tx Local Oscillator (LO) PLL1 lose lock alarm

� Severity:Minor





HandlingSuggestion

1. Observe whether there is clock alarm through LMT and re-place corresponding module if alarm exists. If not exists, checkwhether TP interface 13M clock of the front panel outputs data,



if no output, the problem turns to be clock error from TPU toRCU and replace TRM/DTRM module then.


198087257 Tx LocalOscillator (LO) PLL2 loselock alarm


� Description:Tx Local Oscillator (LO) PLL2 lose lock alarm

� Severity:Minor





HandlingSuggestion



198087258 52M referenceclock PLL lose lock alarm


� Description:52M reference clock PLL lose lock alarm

� Severity:Minor





HandlingSuggestion

1. Check whether there is clock alarm through LMT and replacecorresponding module if alarm exists. If not exists, checkwhether TP interface 13M clock of the front panel outputs data,



if no output, the problem turns to be clock error from TPU toRCU and replace TRM/DTRM module then.


198087259 Tx IF LocalOscillator (LO) PLL lose lockalarm


� Description:Tx IF Local Oscillator (LO) PLL lose lock alarm

� Severity:Minor





HandlingSuggestion



198087260 EEPROMresource unavailable alarm


� Description:EEPROM resource unavailable alarm

� Severity:Minor


Probable Cause EEPROM has fault.

Specific Problem EEPROM has fault.




HandlingSuggestion

Please replace TRM/DTRM module in time.

198087261 FPGA interfacefailure


� Description:FPGA interface failure

� Severity:Minor


Probable Cause Communication between DSP and FPGA interface breaks

Specific Problem Communication between DSP and FPGA interface breaks


HandlingSuggestion

Please replace TRM/DTRM module in time.

198087262 PA VSWRalarm(BTS V2)


� Description:PA VSWR alarm(BTS V2)

� Severity:Minor


Probable Cause Direct reason: reverse power is too high. Possible reason: opencircuit or high resistance exists in output end of PA

Specific Problem Direct reason: reverse power is too high. Possible reason: opencircuit or high resistance exists in output end of PA


HandlingSuggestion

1. Check the connection between PA output and the cable, tightenthe connection.

2. If alarm still exists, please replace TRM/DTRM module in time.



198087263 PAovertemperature minoralarm(BTS V2)


� Description:PA overtemperature minor alarm(BTS V2)



Probable Cause PA temperature is over high, which is possibly induced by PA long-time full power operation, fan long-time shutdown, environmentaltemperature over high and detecting circuit fault, etc.

Specific Problem PA temperature is over high, which is possibly induced by PA long-time full power operation, fan long-time shutdown, environmentaltemperature over high and detecting circuit fault, etc.


HandlingSuggestion

1. Check whether fan works porperly and environmental temper-ature is over high.

2. If fan works properly and environmental temperature is nor-mal, while PA temperature alarm still exists, the problem turnsto be detecting circuit error and keep oberserving.

198087264 PAovertemperature majoralarm(BTS V2)


� Description:PA overtemperature major alarm(BTS V2)

� Severity:Minor





HandlingSuggestion




2. If fan works properly and environmental temperature is nor-mal, while PA temperature alarm still exists, the problem turnsto be detecting circuit error and replace TRM/DTRM block intime.

198087265 PA output poweralarm


� Description:PA output power alarm

� Severity:Minor


Probable Cause Direct reason: Difference between PA output power and CIP con-trol power is more than 3 db; Possible reason: PA aging, powerdetecting circuit fault, or detecting threshold too narrow

Specific Problem Direct reason: Difference between PA output power and CIP con-trol power is more than 3 db; Possible reason: PA aging, powerdetecting circuit fault, or detecting threshold too narrow


HandlingSuggestion

1. Reset TRM/DTRM and observe.

2. If alarm still exists, replace TRM/DTRM module in time.

198087266 PA powerovervoltage


� Description:PA power overvoltage

� Severity:Minor


Probable Cause PA power is overvoltage.

Specific Problem PA power is overvoltage.


HandlingSuggestion

Check whether PA detecting circuit has problem, if yes, replaceTRM/DTRM module in time.



198087267 PA power isundervoltage .


� Description:PA power is undervoltage .

� Severity:Minor


Probable Cause PA power is undervoltage.

Specific Problem PA power is undervoltage.


HandlingSuggestion

Check whether PA detecting circuit has problem, if so, replaceTRM/DTRM module in time.

198087268 Downlinkchecksum error ofDLRC_AL1


� Description:Downlink checksum error of DLRC_AL1

� Severity:Minor


Probable Cause There occurs interference in the link between CHP and modulationmodule.

Specific Problem There occurs interference in the link between CHP and modulationmodule.


HandlingSuggestion

1. Check the signal and time sequence between CHP and modu-lation module.

2. If problem still exists, please replace TRM/DTRM in time.

198087269 DUC chipinitialization failure


� Description: DUC chip initialization failure



� Severity:Minor


Probable Cause DUC chip is not available.

Specific Problem DUC chip is not available.


HandlingSuggestion

The TRM/DTRM has error, please replace it in time.

198087270 80w PA VSWRalarm


� Description:80w PA VSWR alarm

� Severity:Minor


Probable Cause Direct reason: reverse power is too high; possible reason: opencircuit or high resistance exists at the output end of PA.

Specific Problem Direct reason: reverse power is too high; possible reason: opencircuit or high resistance exists at the output end of PA.


HandlingSuggestion

1. Check the connection of PA output with cable.

2. If alarm still exists,please replace TRM module as soon as pos-sible.

198087271 80w PA 'stemperature is a litter high.


� Description:80w PA 's temperature is a litter high.








HandlingSuggestion


2. If fan works properly and environmental temperature is nor-mal, while PA temperature alarm still exists, the problem turnsto be detecting circuit error and keep oberserving.

198087272 80w PAovertemperature majoralarm


� Description:80w PA overtemperature major alarm

� Severity:Minor





HandlingSuggestion


2. If fan works properly and environmental temperature is nor-mal, while PA temperature alarm still exists, the problem turnsto be detecting circuit error and replace TRM/DTRM block intime.

198087273 80w PA outputpower alarm


� Description:80w PA output power alarm

� Severity:Minor


Probable Cause Direct reason: Difference between PA output power and CIP con-trol power is more than 3 db; Possible reason: PA aging, powerdetecting circuit fault, or detecting threshold too narrow



Specific Problem Direct reason: Difference between PA output power and CIP con-trol power is more than 3 db; Possible reason: PA aging, powerdetecting circuit fault, or detecting threshold too narrow


HandlingSuggestion

1. Reset TRM/DTRM and observe.

2. If alarm still exists, replace TRM/DTRM module in time.

198087274 80w PA powerovervoltage


� Description:80w PA power overvoltage

� Severity:Minor





HandlingSuggestion


198087275 80w PA 's poweris undervoltage .


� Description:80w PA 's power is undervoltage .

� Severity:Minor


Probable Cause PA power is undervoltage

Specific Problem PA power is undervoltage


HandlingSuggestion




198087276 80w PAnot-in-position alarm


� Description:80w PA not-in-position alarm

� Severity:Minor


Probable Cause PA is not in position.

Specific Problem PA is not in position.


HandlingSuggestion


198087277 TXIF lock is lost.Alarm Property � Alarm Code:198087277

� Description:TXIF lock is lost.

� Severity:Minor




System Impact The DTRU possibly does not allow callings.

HandlingSuggestion

1. Restart TRX, and if the fault disappears, it indicates there is nofault in DTRU.

2. Check whether there is signal between pinout 2 and 15 of HWline; if not, replace the HW line and continue testing; if thereis still no signal, the problem is possibly caused by CMB fault.Test set-top 13M clock port, and if there is signal, re-plug CMBboard, if no signal, it is possibly CMB fault.

3. If the signal test is normal, re-plug this TRX. If fault still exists,replace the faulty TRX slot. And further replace DTRU if theproblem continues.

198087278 TPF clock isunlocked.


� Description:TPF clock is unlocked.



� Severity:Minor




System Impact The DTRU possibly does not accept callings.

HandlingSuggestion




198087279 TXRF lost lockalarm


� Description:TXRF lost lock alarm

� Severity:Minor





HandlingSuggestion






198087280 RXRF clock isunlocked .


� Description:RXRF clock is unlocked .

� Severity:Minor




System Impact The DTRU possibly does not accept callings

HandlingSuggestion

1. Check whether this alarm restores after resetting the DTRU

2. If this problem still exists, replace DTRU then.

198087281 13 MHz clock islost.


� Description:13 MHz clock is lost.

� Severity:Minor


Probable Cause 13 MHz clock's receiving is abnormal, 13 MHz clock unit worksabnormally.

Specific Problem 13 MHz clock's receiving is abnormal, 13 MHz clock unit worksabnormally.


HandlingSuggestion






198087282 60mssynchronous clock lostalarm


� Description:60ms synchronous clock lost alarm

� Severity:Minor


Probable Cause 60ms synchronous clock receiving is abnormal, or 60ms syn-chronous clock unit work abnormally.

Specific Problem 60ms synchronous clock receiving is abnormal, or 60ms syn-chronous clock unit work abnormally.


HandlingSuggestion

1. Check the configuration, and if there are excessive standbyracks configured, ignore this alarm.

2. Check whether 60ms cable is connected properly or damaged.Reconnect or replace the 60ms cable to check if the alarm re-stores.

3. Check wheather the CMB of standby rack works properly. Ifnot, recover CMB working status and check whether the alarmrestores.

198087283 8M clock of HWis lost.


� Description:8M clock of HW is lost.

� Severity:Minor


Probable Cause HW 8M clock receiving is abnormal, or HW 8M clock unit worksabnormally.

Specific Problem HW 8M clock receiving is abnormal, or HW 8M clock unit worksabnormally.


HandlingSuggestion

1. Check whether HW cable is connected abnormally. If so, adjustthe cable to check whether the alarm is recovered.

2. If the alarm occurs in all cells, re-plug CMB and power on again,and check whether the alarm is recovered. If the alarm onlyoccurs in certain cells, please take following steps for thesecells.



3. Re-power on the TRX to check whether the alarm is recovered.

4. Re-plug the TRX to check whether the alarm is recovered.

5. Check whether the backboard socket which corresponds to theTRX is abnormal. If so, replace the backboard.

198087284 HW 8Ksynchronous signal islost .


� Description:HW 8K synchronous signal is lost .

� Severity:Minor


Probable Cause HW 8K synchronous signal receiving is abnormal, or synchronoussignal unit works abnormally.

Specific Problem HW 8K synchronous signal receiving is abnormal, or synchronoussignal unit works abnormally.

System Impact HW 8K synchronous signal receiving is abnormal, or synchronoussignal unit works abnormally.

HandlingSuggestion

1. Check whether HW cable is connected abnormally. If so, adjustthe cable to check whether the alarm is recovered.

2. If the alarm occurs in all cells, re-plug CMB and power on again,and check whether the alarm is recovered. If the alarm onlyoccurs in certain cells, please take following steps for thesecells.

3. Re-power on the TRX to check whether the alarm is recovered.

4. Re-plug the TRX to check whether the alarm is recovered.

5. Check whether the backboard socket which corresponds to theTRX is abnormal. If so, replace the backboard.

198087285 RF board 52MHzclock lost alarm


� Description:RF board 52MHz clock lost alarm

� Severity:Minor




Probable Cause RF board 52MHz clock receiving is abnormal, or RF board 52MHzclock unit works abnormally.

Specific Problem RF board 52MHz clock receiving is abnormal, or RF board 52MHzclock unit works abnormally.


HandlingSuggestion




198087286 First ADC clockis lost.


� Description:First ADC clock is lost.

� Severity:Minor


Probable Cause AD6650 clock receiving is anormal, or AD6650 clock unit worksabnormally.

Specific Problem AD6650 clock receiving is anormal, or AD6650 clock unit worksabnormally.


HandlingSuggestion






198087287 Second ADCclock is lost.


� Description:Second ADC clock is lost.

� Severity:Minor


Probable Cause AD6650 clock receiving is anormal, or AD6650 clock unit worksabnormally.

Specific Problem AD6650 clock receiving is anormal, or AD6650 clock unit worksabnormally.


HandlingSuggestion




198087288 PA power isovervoltage.


� Description:PA power is overvoltage.

� Severity:Minor




System Impact PA is possibly damaged, and modulation module protectively turnsoff power output.

HandlingSuggestion

Check whether PA detection circuit breaks down. If yes, replaceDTRU in time.



198087289 PA power isundervoltage.


� Description:PA power is undervoltage.

� Severity:Minor


Probable Cause PA power is undervoltage.

Specific Problem PA power is undervoltage.

System Impact Output power is abnormal.

HandlingSuggestion

Check whether PA detection circuit breaks down. If so, replaceDTRU in time.

198087290 PA VSWR alarmAlarm Property � Alarm Code:198087290

� Description:PA VSWR alarm

� Severity:Minor


Probable Cause Direct reason: reverse power is too high. Possible reason: opencircuit or high resistance exists in output end of PA

Specific Problem Direct reason: reverse power is too high. Possible reason: opencircuit or high resistance exists in output end of PA

System Impact This DTRU does not allow callings at all, PA is damaged.

HandlingSuggestion

1. Reset DTRU and check whether alarm restores.

2. Replace RF cable from DTRU to AEM and check whether thisalram restores.


198087291 PA temperatureis a little high. (TRX levelalarm, exceeds 80℃)


� Description:PA temperature is a little high. (TRX level alarm,exceeds 80℃)





Probable Cause PA temperature is over high, which is possibly result from PA long-time full power operation, fan long-time shutdown, environmentaltemperature over high and detecting circuit fault, etc.

Specific Problem PA temperature is over high, which is possibly result from PA long-time full power operation, fan long-time shutdown, environmentaltemperature over high and detecting circuit fault, etc.

System Impact The DTRU still works, but PA aging speed accelerates.

HandlingSuggestion

1. heck whether fan works well. If so, turn to step 2; if not,correct the error and check whether alarm restores. 2, Checkwhether environmental temperature is over high. If not, turnto step 3; if so, improve equipment room environment andcheck whether alarm restores. 3. Reset TRX and check alarmstatus. 4. May be it is result from Detection circuit failure, inthis case ,replace the TRX then.

198087292 PA temperatureis much more higher. (TRXlevel alarm, exceeds 95 ℃)


� Description:PA temperature is much more higher. (TRX levelalarm, exceeds 95 ℃)

� Severity:Minor


Probable Cause PA temperature is over high, which is possibly result from PA long-time full power operation, fan long-time shutdown, environmentaltemperature over high and detecting circuit fault, etc.

Specific Problem PA temperature is over high, which is possibly result from PA long-time full power operation, fan long-time shutdown, environmentaltemperature over high and detecting circuit fault, etc.

System Impact Power output of this DTRU is terminated for protection, and PAaging speed accelerates.

HandlingSuggestion

1. heck whether fan works well. If so, turn to step 2; if not,correct the error and check whether alarm restores. 2, Checkwhether environmental temperature is over high. If not, turnto step 3; if so, improve equipment room environment andcheck whether alarm is recovered. 3. Reset TRX and checkalarm status. 4. May be it is result from Detection circuitfailure, in this case ,replace the TRX then.



198087293 PA forwardpower(3db) alarm


� Description:PA forward power(3db) alarm

� Severity:Minor


Probable Cause Direct reason: Difference between PA output power and CHP con-trol power is more than 3 db; Possible reason: PA aging, powerdetecting circuit fault, detecting threshold too narrow

Specific Problem Direct reason: Difference between PA output power and CHP con-trol power is more than 3 db; Possible reason: PA aging, powerdetecting circuit fault, detecting threshold too narrow

System Impact The DTRU possibly does not allow callings, and power control isout of control, etc.

HandlingSuggestion

1. Reset DTRU and check whether alarm restores.

2. Replace RF cable from DTRU to AEM and check whether thisalram restores.


198087294 RTU power isabnormal.


� Description:RTU power is abnormal.

� Severity:Major


Probable Cause Power module on the RTU board has alarm.

Specific Problem Power module on the RTU board has alarm.

System Impact The DRM/DTRM cannot work, if it is configured as BCCH, wholecell service is affected.



HandlingSuggestion

Replace the RTU circuit board as quickly as possible

198087295 The temperatureof RTU power is too high.


� Description:The temperature of RTU power is too high.

� Severity:Minor


Probable Cause RTU temperature is over high, which is possibly result from RTUlong-time full power operation, fan long-time shutdown, environ-mental temperature over high and detecting circuit fault, etc.

Specific Problem RTU temperature is over high, which is possibly result from RTUlong-time full power operation, fan long-time shutdown, environ-mental temperature over high and detecting circuit fault, etc.

System Impact Power output of this TRM/DTRU is terminated for protection, andRTU aging speed accelerates.

HandlingSuggestion

1. Check whether fan works well and environmental temperatureis over high.

2. If fan works well and environmental temperature is normal butRTU temperature alarm still exists, the problem may be resultfrom detecting circuit error.

198087296 The output ofRTU power is overvoltage.


� Description:The output of RTU power is overvoltage.

� Severity:Major


Probable Cause RTU power output is overvoltage.

Specific Problem RTU power output is overvoltage.

System Impact RTU can't work well.



HandlingSuggestion

Replace the RTU board.

198087297 RTU power inputabnormal alarm


� Description:RTU power input abnormal alarm

� Severity:Major


Probable Cause RTU power input exceeds adjustment range.

Specific Problem RTU power input exceeds adjustment range.

System Impact RTU can't work well.

HandlingSuggestion


198087298 IQ calibrationparameters are abnormal.


� Description:IQ calibration parameters are abnormal.

� Severity:Major


Probable Cause IQ calibration parameter is abnormal.

Specific Problem IQ calibration parameter is abnormal.

System Impact The whole board of RTU are paralyzed.

HandlingSuggestion


198087299 EAM heatexchanger alarm.


� Description:EAM heat exchanger alarm.





Probable Cause Heat exchanger triggers alarm, which is reported by node of heatexchanger.

Specific Problem Heat exchanger triggers alarm, which is reported by node of heatexchanger.

System Impact Device's safety is affected.

HandlingSuggestion

1. Check the connection between EAM and heat exchanger, if con-nect right, to step2 .

2. Check whether heat exchanger provide power normally, ifpower right, to step

3. Replace the heat exchanger.

198087300 CMB0 heatingfilm alarm.


� Description: CMB0 heating film alarm.



Probable Cause CMB0 heating film has error.

Specific Problem CMB0 heating film has error.

System Impact Device low-temperature start up is affected.

HandlingSuggestion

1. Check whether CMB0 heating film is powered properly.

2. Check if heating film is damaged. If yes, replace CMB0 heatingfilm.

198087301 CMB1 heatingfilm alarm


� Description: CMB1 heating film alarm



Probable Cause CMB1 heating film has error.

Specific Problem CMB1 heating film has error.

System Impact Device starting up with low-temperature is affected.



HandlingSuggestion

1. Check whether CMB1 heating film is powered properly.

2. Check if heating film is damaged. If yes, replace CMB1 heatingfilm.

198087302 EAM has hadsmoke .


� Description:EAM has had smoke .

� Severity:Minor


Probable Cause Device smoke results in alarm.

Specific Problem Device smoke results in alarm.

System Impact Device's operation safety is affected.

HandlingSuggestion

Perform onsite check immdiately to find the root cause and checkwhether there occurs fire. After addressing the problem, resetEAM board and clear smoke alarm.

198087303 EAM has hadwater.


� Description:EAM has had water.

� Severity:Minor


Probable Cause Water intrusion of device results in alarm.

Specific Problem Water intrusion of device results in alarm.




HandlingSuggestion

Check immediately to find reason and handle the fault.

198087304 EAM lightningprotection alarm.


� Description:EAM lightning protection alarm.

� Severity:Minor


Probable Cause Lightning protector fails and results in alarm.

Specific Problem Lightning protector fails and results in alarm.


HandlingSuggestion

1. Check whether lightening protector connection interface is con-nected well.

2. Check whether lightening protector is damaged itself. If so,replace lightening protector.

198087305 EAM backdooraccess is intruded.


� Description:EAM backdoor access is intruded.



Probable Cause Back door is opened and results in alarm.

Specific Problem Back door is opened and results in alarm.

System Impact Affect device safety.

HandlingSuggestion

Perform onsite check immdiately to check whether backdoor isopened. If so, close the backdoor; if not, check if it is door mag-netic problem.



198087306 EAM frontdooraccess is intruded.


� Description:EAM frontdoor access is intruded.



Probable Cause Front door is opened and results in alarm.

Specific Problem Front door is opened and results in alarm.


HandlingSuggestion

Perform onsite check immdiately to check whether frontdoor isopened. If so, close the frontdoor; if not, check if it is door mag-netic problem.

198087307 EAM PWRmonitoring unit has fault.


� Description:EAM PWR monitoring unit has fault.



Probable Cause PWR monitoring unit results in alarm.

Specific Problem PWR monitoring unit results in alarm.


HandlingSuggestion

1. Check connection line between PWR and EAM.

2. Check whether power monitoring unit is normal.

3. Check if any other alarms exist in the power.

198087308 FIB heating filmalarm


� Description: FIB heating film alarm

� Severity:Minor




Probable Cause FIB heating film has error.

Specific Problem FIB heating film has error.

System Impact Affect device low-temperature start up.

HandlingSuggestion

1. Check whether FIB heating film is powered properly.

2. Check if heating film is damaged. If yes, replace FIB heatingfilm.

198087309 EAM heatexchanger control board hasfault.


� Description:EAM heat exchanger control board has fault.

� Severity:Minor


Probable Cause Heat exchanger control board triggers alarm.

Specific Problem Heat exchanger control board triggers alarm.

System Impact Affect device operation safety.

HandlingSuggestion

1. Check connection line between EAM and heat exchanger.

2. Check whether heat exchanger is powered normally.

3. Replace heat exchanger control board.

198087310 EAM heatexchanger externalcirculation fan 2 alarm.


� Description:EAM heat exchanger external circulation fan 2alarm.

� Severity:Minor


Probable Cause Heat exchanger external circulation fan engine 2 results in alarm.

Specific Problem Heat exchanger external circulation fan engine 2 results in alarm.




HandlingSuggestion

1. Check connection line between heat exchanger control boardand fan.

2. Replace the fan.

198087311 EAM heatexchanger externalcirculation fan 1 alarm.


� Description:EAM heat exchanger external circulation fan 1alarm.

� Severity:Minor


Probable Cause Heat exchanger external circulation fan engine 1 results in alarm.

Specific Problem Heat exchanger external circulation fan engine 1 results in alarm.


HandlingSuggestion


2. Replace the fan.

198087312 EAM heatexchanger internalcirculation fan 2 alarm


� Description:EAM heat exchanger internal circulation fan 2alarm

� Severity:Major


Probable Cause Heat exchanger internal circulation fan engine 2 triggers alarm.

Specific Problem Heat exchanger internal circulation fan engine 2 triggers alarm.


HandlingSuggestion


2. Replace the fan.



198087313 EAM heatexchanger internalcirculation fan 1 alarm.


� Description:EAM heat exchanger internal circulation fan 1alarm.

� Severity:Major


Probable Cause Heat exchanger internal circulation fan engine 1 triggers alarm.

Specific Problem Heat exchanger internal circulation fan engine 1 triggers alarm.


HandlingSuggestion


2. Replace the fan.

198087314 EAM heatexchanger 's 485communication has fault.


� Description:EAM heat exchanger 's 485 communication hasfault.

� Severity:Minor


Probable Cause Communication between EAM and heat exchanger breaks.

Specific Problem Communication between EAM and heat exchanger breaks.

System Impact Affect heat exchanger alarm report.

HandlingSuggestion

1. Check connection line between EAM and heat exchanger.

2. Check whether heat exchanger is powered normally.

3. Replace heat exchanger control board.



198087315 EAMtemperature is abnormal.


� Description:EAM temperature is abnormal.

� Severity:Minor


Probable Cause Device internal environmental temperature is too high.

Specific Problem Device internal environmental temperature is too high.


HandlingSuggestion

1. Check whether TRX layer fan processes normally.

2. Check whether heat exchanger works properly.

198087316 EAM TRX layermixed-flow fan 1 has fault.


� Description:EAM TRX layer mixed-flow fan 1 has fault.

� Severity:Minor


Probable Cause Mixed-flow fan engine 1 is damaged.

Specific Problem Mixed-flow fan engine 1 is damaged.

System Impact Affect RTU normal work.

HandlingSuggestion

1. Check wheter the connection line between FNIB and fan engineis good. If not, replace the line.

2. Check whether fan engine itself is damaged, if so, replace thefan engine.




� Severity:Minor







HandlingSuggestion

1. Check connection line between FNIB and fan engine. And re-place the line if it breaks down.

2. Check whether fan engine itself is damaged, if yes, replace thefan engine.




� Severity:Minor





HandlingSuggestion

1. Check connection line between FNIB and fan engine. And re-place the line if it breaks down.

2. Check whether fan engine itself is damaged, if yes, replace thefan engine.

198087319 Communicationis broken between EAM andCMB.


� Description:Communication is broken between EAM and CMB.

� Severity:Minor


Probable Cause Communication between EAM and CMB breaks.

Specific Problem Communication between EAM and CMB breaks.

System Impact Affect device alarm report.

HandlingSuggestion

1. Check whether EAM is powered on.

2. Check whether CMB works properly.



3. Replace EAM board or backborad.

198087320 Powerundervoltage alarm


� Description:Power undervoltage alarm

� Severity:Major


Probable Cause Power voltage is lower than normal

Specific Problem Power voltage is lower than normal


HandlingSuggestion

Restore external power supply as soon as possible

198087321 Inner fan engine2 alarm (for M8202)


� Description:Inner fan engine 2 alarm (for M8202)



Probable Cause Fan stops rotating because of some bugs.

Specific Problem Fan stops rotating because of some bugs.

System Impact Cabinet temperature rises.

HandlingSuggestion


2. Check whether the lines of fan engine and fan controller existfault. If yes, turn to step 3; if not, turn to step 4.

3. Check whether fan engine cable exists fault, and whetherboard-port connector exists fault. If fan engine cable hasmalfunction, replace it then. If board-port connector malfunc-tions, replance fan controller board DFCM/FNCB.


5. Check whether alarm collection of fan controller board is ab-normal. If yes, replace fan controller board DFCM/FNCB; if not,turn to step



6. Check whether TRM/DTRU alarm collection circuit is abnormal.If yes replace corresponding TRM/DTRU.

198087322 Inner fan engine1 alarm (for M8202)


� Description:Inner fan engine 1 alarm (for M8202)






HandlingSuggestion


2. Check whether the lines of fan engine and fan controller existfault. If yes, turn to step 3; if not, turn to step 4.

3. Check whether fan engine cable exists fault, and whetherboard-port connector exists fault. If fan engine cable hasmalfunction, replace it then. If board-port connector malfunc-tions, replance fan controller board DFCM/FNCB.


5. Check whether alarm collection of fan controller board is ab-normal. If yes, replace fan controller board DFCM/FNCB; if not,turn to step

6. Check whether TRM/DTRU alarm collection circuit is abnormal.If yes replace corresponding TRM/DTRU.

198087323 Outer fan engine2 and 4 alarm (for M8202)


� Description:Outer fan engine 2 and 4 alarm (for M8202)








HandlingSuggestion

1. Check whether error-detection circuit has malfunction, if yes,eliminate it.

2. Check whether fan engine has problem, and repair it.

3. Check whether dTPB alarm collection circuit works well or not,if not, replace dTPB board.

198087324 Outer fan engine1 and 3 alarm (for M8202)


� Description:Outer fan engine 1 and 3 alarm (for M8202)





System Impact the temperature of rack to arise

HandlingSuggestion

1. Check the alarm connection and eliminate the malfunction;

2. Check the fan and maintain the fault;

3. Check the collection system of the dTPB board and replace thewrong one.

198087325 Racktemperature minor alarm


� Description:Rack temperature minor alarm



Probable Cause Fan fault or module temperature too high

Specific Problem Fan fault or module temperature too high

System Impact lead to the temperaturn of TRM/DTRU was too high, affect theperformance index

HandlingSuggestion

Check the environment temperature, if the temperature is normal,keep on observing while other modules works normally, otherwise,improve the equipment working conditions.



198087326 Racktemperature major alarm


� Description:Rack temperature major alarm

� Severity:Minor


Probable Cause Fan fault or module temperature too high

Specific Problem Fan fault or module temperature too high

System Impact to make the device broken and affect the performance index

HandlingSuggestion

Check the environment temperature, if the temperature is normal,keep on observing while other modules works normally, otherwise,improve the equipment working conditions.

198087327 Layer 3 fan 1alarm (for M8206)


� Description:Layer 3 fan 1 alarm (for M8206)



Probable Cause The failure of fans

Specific Problem The failure of fans

System Impact the temperature of rack to arise,affect the performance of workand the working life

HandlingSuggestion

1. Examin the error-detection circuit;

2. Examin the fans;

3. Examin the RTU Alarm Collection Circuit, if any fault in it, re-place the relevant unit.











HandlingSuggestion


2. Examin the fans;










HandlingSuggestion


2. Examin the fans;












HandlingSuggestion


2. Examin the fans;










HandlingSuggestion


2. Examin the fans;










HandlingSuggestion


2. Examin the fans;












HandlingSuggestion


2. Examin the fans;










HandlingSuggestion


2. Examin the fans;












HandlingSuggestion


2. Examin the fans;


198087340 FR device failureAlarm Property � Alarm Code:198087340

� Description:FR device failure

� Severity:Minor


Probable Cause N392 errors are detected in the latest N393 STATUS ENQUIRYevents.

Specific Problem N392 errors are detected in the latest N393 STATUS ENQUIRYevents.

System Impact BRCH of Gb interface is not accessible.

HandlingSuggestion

1. Check whether the alarm of E1 port corresponding to this BRCHis persistent. If so, check transmission devices and solve theproblem.

2. Do self-loop check to local terminal device and ensure E1 worksproperly. If the local terminal is abnormal, replace E1 line thenand watch whether the alarm disappears; If the local deviceworks normally, then contact SGSN maintenance personnel todo self-loop to ensure that SGSN works properly. If SGSNworks normally, go to step

3. Check the configuration of both BSC and SGSN to ensure thatE1 frames have the same format.

4. Check the E1 LED indicator on GIPB board. If it is in normalstatus, go to step 5; if not, replace the rear board and observewhether the alarm disappears.



5. Check whether configured parameters on BRCH interface areconsistent with the corresponding ones in SGSN. If not, modifyconfigured parameters until they are the same. If consistent,go to step

6. , Replace GIPB board and observe whether the alarm disap-pears.

198087342 Cell interruptionalarm


� Description:Cell interruption alarm

� Severity:Minor


Probable Cause 1. The site to which the cell belongs is lost.

2. The cell BCCH frequency is faulty.

Specific Problem 1. The site to which the cell belongs is lost.

2. The cell BCCH frequency is faulty.

System Impact The cell cannot provide any voice or data services.

HandlingSuggestion

1. On NMS fault management interface, check if related alarm ex-ists. If yes, follow the instructions of handling related alarms.Related alarm: 198087337 Site Abis control link broken

2. On NMS dynamic data management interface, check if cellstate is normal. On Radio Resource Management tab page inthis interface, check BTS management, TRX management andTS management. (1) BTS management If manually blockedBTS exists, unblock it. If global reset blocked of the cell, checkand rectify A interface faults. (2) TRX management If BCCHof the alarmed cell is manually blocked, unblock TRX. If blockinduced by Abis control link broken exists, restore the site'sAbis control link. If CU or FU operation state of TRX is blocked,check and restore the BTS TRX faults. (3) TS management IfBCCH of the alarmed cell is manually blocked, unblock timeslot.



198087361 The CRCcalibration of PA parameterturns to be error .


� Description:The CRC calibration of PA parameter turns to beerror .



Probable Cause PA parameter calibration has error.

Specific Problem PA parameter calibration has error.

System Impact PA does not have calibration curve, and affect RX indicators.

HandlingSuggestion

(1) Reset the corresponding TRX and check whether alarm is re-covered. (2) Power on the corresponding TRX and check alarmstatus. (3) Replace TRX.

198087379 OMP rebootalarm


� Description:OMP reboot alarm

� Severity:Major


Probable Cause This alarm is triggered after OMP board rebooted and recovers im-mediately. Generally, these alarms could only be queried in historyalarm list after they are triggered.

Specific Problem This alarm is triggered after OMP board rebooted and recovers im-mediately. Generally, these alarms could only be queried in historyalarm list after they are triggered.

System Impact This alarm affects the operation and maintenance during OMP mal-function. It has no effect on the services.

HandlingSuggestion

OMP reports this alarm after rebooting and restores automatically,no handling operations are needed.



198087386 SYNCLK losinglock alarm


� Description:SYNCLK losing lock alarm



Probable Cause SYNCLK cannot be locked for a long time.

Specific Problem SYNCLK cannot be locked for a long time.

System Impact Master and slave CMM/CMB board cannot switch with each other.

HandlingSuggestion

Check whether SYNCLK board on BSC works well. If it works welland slave board exists, switch the master to slave board; if theslave board does not exist, reset the master board then.

198087387 Status of TX1filter alarm


� Description:Status of TX1 filter alarm

� Severity:Major


Probable Cause TX1 channed is not well adjusted or the loss exceeds 5dB.

Specific Problem TX1 channed is not well adjusted or the loss exceeds 5dB.


HandlingSuggestion

(1) Reset the corresponding TRX and check whether the alarmrestores. (2) Replace FCU and check whether the alarm restores.




� Severity:Major







HandlingSuggestion





� Severity:Major





HandlingSuggestion





� Severity:Major





HandlingSuggestion




198087391 FCU powerundervoltage alarm


� Description:FCU power undervoltage alarm

� Severity:Major


Probable Cause +12V power is undervoltage and triggers alarm.

Specific Problem +12V power is undervoltage and triggers alarm.

System Impact FCU works abnormally.

HandlingSuggestion

1. Check whether FCU power LED displays alarm. If yes, turn tostep 2; if not, turn to step 3.

2. Check whether FCU corresponding slots' 12V power is normal.If not, replace FCU; otherwise, turn to step

3. Replace FCU, and watch whether the alarm restores.

198087392 FCUminor alarmAlarm Property � Alarm Code:198087392

� Description:FCU minor alarm

� Severity:Minor


Probable Cause FCU digital board assistant circuit triggers alarm.

Specific Problem FCU digital board assistant circuit triggers alarm.

System Impact FCU works abnormally.

HandlingSuggestion

Keep on observing and don't replace FCU board if normal serviceis not affected.

198087403 ABIS-E1transmission related clockalarm of CCI board


� Description:ABIS-E1 transmission related clock alarm of CCIboard



� Severity:Minor


Probable Cause Reference source is missed or ABIS-E1 transmission clockPLL(Phase Locked Loop) lost.

Specific Problem Reference source is missed or ABIS-E1 transmission clockPLL(Phase Locked Loop) lost.


HandlingSuggestion

Examine the Abis-E1 interface.

198087404 Local workingclock alarm of CCI board


� Description:Local working clock alarm of CCI board

� Severity:Minor


Probable Cause Local working clock failed.

Specific Problem Local working clock failed.


HandlingSuggestion

Switch into slave baord as soon as possible, and replace CCI circuitboard if necessary.

198087405 13M clock alarmof CCI board .


� Description:13M clock alarm of CCI board .

� Severity:Minor


Probable Cause Reference source is missed or concerned clock PLL(Phase LockedLoop) lost.

Specific Problem Reference source is missed or concerned clock PLL(Phase LockedLoop) lost.




HandlingSuggestion

Check reference source or replace CCI.

198087406 CCI oppositeboard alarm


� Description:CCI opposite board alarm



Probable Cause CCI opposite board is not in position or clock has error.

Specific Problem CCI opposite board is not in position or clock has error.


HandlingSuggestion

Replace the CCI circuit board.

198087407 IQ FPGA internalclock alarm


� Description:IQ FPGA internal clock alarm

� Severity:Minor


Probable Cause IQ FPGA internal source clock is lost.

Specific Problem IQ FPGA internal source clock is lost.


HandlingSuggestion

Detect whether the CLK FPGA is running.

198087408 IQ FPGA lightinterface alarm


� Description:IQ FPGA light interface alarm

� Severity:Minor




Probable Cause IQ FPGA light interface link connection is abnormal.

Specific Problem IQ FPGA light interface link connection is abnormal.


HandlingSuggestion

Replace the optical module or optical fiber.

198087409 IQ FPGA LVDSinterface alarm


� Description:IQ FPGA LVDS interface alarm

� Severity:Minor


Probable Cause LVDS interface is abnormal.

Specific Problem LVDS interface is abnormal.


HandlingSuggestion

Check the rear board and SERDES chip condition on the corre-sponding GBP board.

198087410 IQ FPGA internaldata alarm


� Description:IQ FPGA internal data alarm

� Severity:Minor


Probable Cause The format of detected internal data is abnormal

Specific Problem The format of detected internal data is abnormal


HandlingSuggestion

Check the reason for abnornal data format with whole systemalarms.



198087411 13M and 61.44Mclock lost alarm


� Description:13M and 61.44M clock lost alarm

� Severity:Minor


Probable Cause Clock is lost.

Specific Problem Clock is lost.


HandlingSuggestion

f there is 13M or 61.44M clock lost alarm in CCI board and thealarm still exists after resetting CCI, please check the clock source;if there is no 13M or 61.44M clock lost alarm while alarm still existsafter resetting GBP, please check LVDS access malfunction.

198087412 FR or FN haserror.


� Description:FR or FN has error.

� Severity:Minor


Probable Cause FR or FN has error.

Specific Problem FR or FN has error.


HandlingSuggestion

If there is FR or FN error in CCI and the error still exists afterresetting CCI, please check hardware malfunction; if there is noFR or FN error while 60ms clock lost alarm still exists after resettingGBP, please check LVDS access malfunction.



198087413 26MHz and52MHz Phase Locked Loop(PLL) lose lock alarm


� Description:26MHz and 52MHz Phase Locked Loop (PLL) loselock alarm

� Severity:Minor


Probable Cause PLL is unlocked.

Specific Problem PLL is unlocked.


HandlingSuggestion

If there is 13M clock lost alarm and still exists after resetting CCI,please check the clock source; if there is no 13M clock lost alarmand lock-lost alarm still exists after resetting GBP, then checkwhether 13M LVDS access has malfunction. If not, problem turnsto be FPGA PLL failure and replace FPGA then.

198087414 Detect failurealarm of uplink 60mshyperframe synchronizationhead


� Description:Detect failure alarm of uplink 60ms hyperframesynchronization head

� Severity:Minor


Probable Cause No 60ms hyperframe head is detected in uplink.

Specific Problem No 60ms hyperframe head is detected in uplink.


HandlingSuggestion

If there is detect failure alarm of uplink 60ms hyperframe synchro-nization head in CCI board, and the alarm still exists after resettingCCI, please check corresponding hardware error; If no such alarmin uplink while alarm still exists after resetting GBP, please checkthe LVDS access malfunction then.



198087415 Checking blockdata error alarm


� Description:Checking block data error alarm



Probable Cause Frame data has error.

Specific Problem Frame data has error.


HandlingSuggestion

None

198087416 Uplink LVDSSERDES lost lock alarm


� Description:Uplink LVDS SERDES lost lock alarm

� Severity:Minor


Probable Cause Frame number from CCI has error.

Specific Problem Frame number from CCI has error.


HandlingSuggestion

If there is FN error in CCI and the error still exists after resettingCCI, please check hardware error; if there is no FN error while thealarm still exists after resetting GBP, please check LVDS accessmalfunction.

198087417 FN error alarmAlarm Property � Alarm Code:198087417

� Description:FN error alarm



Probable Cause Frame number from CCI has error.

Specific Problem Frame number from CCI has error.




HandlingSuggestion

If there is FN error in CCI and the error still exists after resettingCCI, please check hardware error; if there is no FN error while thealarm still exists after resetting GBP, please check LVDS accessmalfunction.

198087432 Diversityantenna lost.


� Description:Diversity antenna lost.

� Severity:Major


Probable Cause Two diversity antennae receive signal and one of which is abnor-mal.

Specific Problem Two diversity antennae receive signal and one of which is abnor-mal.

System Impact One of the diversity antennae breaks down and doesn’t play therole of diversity reception, thus impacting sensitivity and cover-age.

HandlingSuggestion

Reset the TRX and if error still exists, replace the slot. And replaceDTRU if alarm still exists.

198087433 Diversityantenna identical.


� Description:Diversity antenna identical.

� Severity:Major


Probable Cause Connection of two diversity antennae is wrong.

Specific Problem Connection of two diversity antennae is wrong.

System Impact Antenna are connected identically and cannot work properly.



HandlingSuggestion

Check the connection of antenna as quickly as possible.

198087443 Diversityantenna lost alarm


� Description:Diversity antenna lost alarm



Probable Cause Two diversity antennae receive signal and one of which is abnor-mal.

Specific Problem Two diversity antennae receive signal and one of which is abnor-mal.


HandlingSuggestion

Check the receive channel of RF as quickly as possible.

198087444 Diversityantenna identical alarm


� Description:Diversity antenna identical alarm



Probable Cause The connection between two diversity antennae is wrong.

Specific Problem The connection between two diversity antennae is wrong.


HandlingSuggestion

Check the connection of ant line as quickly as possible.

198087451 Board does notsupport 16MHW.


� Description:Board does not support 16MHW.





Probable Cause Current board doesn’t support 16MHW.

Specific Problem Current board doesn’t support 16MHW.

System Impact It partially supports IP ABIS function and some TRX cannot workproperly.

HandlingSuggestion

Replace with the board that supports 16MHW.

198087452 CMB CPUoverload alarm


� Description:CMB CPU overload alarm



Probable Cause CPU usage rate exceeds 85%.

Specific Problem CPU usage rate exceeds 85%.

System Impact Some service cannot be processed.

HandlingSuggestion

Wait for a while until alarm restores, and process service then.

198087453 Signalling HDLCis broken .


� Description:Signalling HDLC is broken .

� Severity:Major


Probable Cause HDLC communication between TRX and FIB breaks or hardwarehas error, etc.

Specific Problem HDLC communication between TRX and FIB breaks or hardwarehas error, etc.

System Impact No callings can through this DTRU.

HandlingSuggestion

1. Check whether DTRU board is inserted, plugged tightly or pow-ered on, watch if alarm restores.

2. Reset DTRU board to check whether the alarm is recovered.

3. Check FIB board work status.

4. Check whether the DIP address switch on the rear board iscorrect.



5. Check whether the transmission line of the rear board is con-nected correctly.

198087454 Maindimensional HDLC brokenalarm


� Description:Main dimensional HDLC broken alarm

� Severity:Major


Probable Cause HDLC link between CMB and FIB breaks, or CMB or FIB hardwarehas error.

Specific Problem HDLC link between CMB and FIB breaks, or CMB or FIB hardwarehas error.

System Impact No data can be transmissed between CMB and FIB.

HandlingSuggestion

1. Check whether CMB or FIB processes properly. If CMB is ab-normal, reset CMB and check alarm status. If FIB is abnormal.Reset FIB and check alarm status.

2. If alarm doesn’t recover for a long time, please replace CMB orFIB and check whether it restores.

198087455 FIB configurationexception alarm


� Description:FIB configuration exception alarm



Probable Cause Parameter configuration is timeout or occurs error.

Specific Problem Parameter configuration is timeout or occurs error.

System Impact In general, BSC background checks data legality before synchro-nizing data, and only after the data passed legality check can it besynchronized, therefore, this alarm rarely occurs.

HandlingSuggestion

1. Wait for ten minutes and observe if the alarm restores.

2. If alarm doesn’t restore, reconfigure parameter from back-ground and synchronize to BTS.



3. If alarm still exists, replace FIB module.

198087456 FIB softwarelayer 3 no response


� Description:FIB software layer 3 no response



Probable Cause FIB software (has/has not) reponse temporarily (set by CMB).

Specific Problem FIB software (has/has not) reponse temporarily (set by CMB).

System Impact FIB running state cannot be detected from background.

HandlingSuggestion

1. Wait for ten minutes and observe if alarm restores.

2. If the alarm doesn’t restore for a long time, please re-plug andreset FUC when traffic is not busy.

3. Reset CMB when traffic is not busy and check if alarm recovers.

4. Replace FIB module and check if alarm recovers.

5. Correct software and upgrade the version.

198087457 FIB CPUoverload alarm


� Description:FIB CPU overload alarm





System Impact Some service cannot be processed.



HandlingSuggestion

Wait for a while unitl alarm restores, and process service then.

198087458 BVC block alarmAlarm Property � Alarm Code:198087458

� Description:BVC block alarm

� Severity:Minor


Probable Cause The DSP on UPPB/UPBB2 board is abnormal.

Specific Problem The DSP on UPPB/UPBB2 board is abnormal.

System Impact The cell fails to provide data service.

HandlingSuggestion

1. On NMS Dynamic Data Management interface, select Radio Re-source Management under BTS Dynamic Data Management.Click the BVC Management tab and check if the cell state isblocked. If yes, unblock the cell.

2. On NMS Configuration Management interface, find the faultycell through Configuration Resource tree. In the GPRS BasicParams tab page of Cell Parameters interface, check if the con-figurations of SGSN ID, NSEI, BVCI, UPPB Unit, and DSP No.are correct. If not, correct them and synchronize the data onBSC and NMS.

3. Log in UPPB/UPPB2 board through telnet. Input "SCSShowD-SPStatus" command to check if the corresponding DSP statusis running. If not, it indicates that the DSP is damaged. In thiscase, replace the board.

198087460 +12V voltagealarm


� Description:+12V voltage alarm

� Severity:Major


Probable Cause The +12V power module on DPB board of DTRU module has alarm.

Specific Problem The +12V power module on DPB board of DTRU module has alarm.

System Impact The cell LNA cannot work properly and affect normal service.



HandlingSuggestion

Replace DTRU module or BBTR backboard.

198087461 -12V voltagealarm


� Description:-12V voltage alarm

� Severity:Major


Probable Cause The -12V power module on DPB board of DTRU module has alarm.

Specific Problem The -12V power module on DPB board of DTRU module has alarm.

System Impact The cell LNA cannot work properly and affect normal service.

HandlingSuggestion

Replace DTRU module or BBTR backboard.

198087462 DSP 1.2Vvoltage alarm


� Description:DSP 1.2V voltage alarm

� Severity:Major


Probable Cause The 1.2V power module on DPB board of DTRU module has alarm.

Specific Problem The 1.2V power module on DPB board of DTRU module has alarm.

System Impact The DTRU cannot work and affect whole cell servvice if it is con-figured as BCCH.

HandlingSuggestion

Repace DTRU module.

198087463 6.4V voltagealarm


� Description:6.4V voltage alarm

� Severity:Major




Probable Cause The 6.4V power module on DPB board of DTRU module has alarm.

Specific Problem The 6.4V power module on DPB board of DTRU module has alarm.


HandlingSuggestion

Repace DTRU module.

198087464 5V voltage alarmAlarm Property � Alarm Code:198087464

� Description:5V voltage alarm

� Severity:Major


Probable Cause The 5V power module on DPB board of DTRU module has alarm.

Specific Problem The 5V power module on DPB board of DTRU module has alarm.


HandlingSuggestion

Repace DTRU module.

198087470 Fan enginenot-in-position alarm


� Description:Fan engine not-in-position alarm



Probable Cause The alarm is due to fan engine fault or module over high temper-ature.

Specific Problem The alarm is due to fan engine fault or module over high temper-ature.


HandlingSuggestion




198087471 Fan enginerotation speed alarm


� Description:Fan engine rotation speed alarm



Probable Cause Fan is not in position.

Specific Problem Fan is not in position.


HandlingSuggestion

Let Fan in position or reinsert the fan and let it works well .

198087472 CMB and FNCBRS485 link broken alarm


� Description:CMB and FNCB RS485 link broken alarm



Probable Cause CPU is abnormal

Specific Problem CPU is abnormal

System Impact Fan engine is out of control, but doesn't affect cooling.

HandlingSuggestion

(1) Check whether alarm circuit has fault. If so, solve this problem;if not, turn to step 2. (2) Replace fan controller board DFCM/FNCB.

198087473 DTPU CPU isoverloaded.


� Description:DTPU CPU is overloaded.

� Severity:Major






System Impact Service on this DTRU cannot be processed.

HandlingSuggestion

Wait for about 10 minutes and process service after alarm restores.




� Severity:Major





HandlingSuggestion





� Severity:Major





HandlingSuggestion


198087483 GPS signalsynchronization exception


� Description:GPS signal synchronization exception



� Severity:Minor


Probable Cause GPS synchronization is not supported, GPS clock synchronizationfails or GPS has fault.

Specific Problem GPS synchronization is not supported, GPS clock synchronizationfails or GPS has fault.

System Impact Cannot process GPS clock synchronization, and switch to internalsynchronization mode.

HandlingSuggestion

1. Check current CMB board type, and if it doesn’t supports GPSsynchronization, replace it with one that supports.

2. Check whether EIB/FIB supports GPs, if not replace with onethat supports.

198087484 Second pulselost alarm


� Description:Second pulse lost alarm

� Severity:Minor


Probable Cause GPS 1PPS signal is lost.

Specific Problem GPS 1PPS signal is lost.

System Impact It cannot process GPS clock synchronization.

HandlingSuggestion

1. Check GPS antennae installation out of the cabinet, and re-move fault if there is any.

2. Check adapter cable from EIB/FIB module to set-top GPS, andremove fault if there is any.

3. Check EIB/FIB module, and replace it if there is malufunction.

4. Check GPS second pulse alarm collection circuit of CMB mod-ule, and replace it if it is abnormal.

198087485 Antennaopen-circuit alarm


� Description:Antenna open-circuit alarm

� Severity:Minor




Probable Cause GPS antennae appear open-circuit exception.

Specific Problem GPS antennae appear open-circuit exception.


HandlingSuggestion

1. Check whether GPS antennae installation out of the cabinethas open circuit, if so, remove it.

2. Check whether adapter cable from EIB/FIB module to set-topGPS has open circuit, if so, remove it.


198087486 Antennashort-circuit alarm


� Description:Antenna short-circuit alarm

� Severity:Minor


Probable Cause GPS antennae appeared short-circuit exception.

Specific Problem GPS antennae appeared short-circuit exception.


HandlingSuggestion




198087487 Lost satellitealarm


� Description:Lost satellite alarm

� Severity:Minor


Probable Cause GPS does not recognize the satellite

Specific Problem GPS does not recognize the satellite


HandlingSuggestion






198087505 GUP boardconnection failure


� Description:GUP board connection failure

� Severity:Major


Probable Cause 1. The board could not be allocated with connection resources.

2. If the board type is AIPB, it may caused by UDP port or nexthop error.

Specific Problem 1. The board could not be allocated with connection resources.

2. If the board type is AIPB, it may caused by UDP port or nexthop error.

System Impact Part of CS and PS service is unavailable, and no service could beprovided if situation worsens.

HandlingSuggestion


2. If the board type is AIPB, check UDP port and next hop config-uration.

198088000 DTPU doesnot support basebandfreqency-hopping alarm.


� Description:DTPU does not support baseband freqency-hop-ping alarm.

� Severity:Major


Probable Cause DTPU does not support baseband freqency-hopping.

Specific Problem DTPU does not support baseband freqency-hopping.

System Impact 1. No DTRU supports baseband frequency-hopping except875DTRU.



2. If the DTPB is not the latest version, the whole layer TRX cannotsupport baseband frequency-hopping.

HandlingSuggestion

1. Check if the DTRU is DTPB080300 module, if not, change toDTPB080300 module.

2. If alarm still exists, please check whether rear board isBBTR070401 type, if not, change to BBTR070401 backpanel.

198088001 PA voltageadjusting path has broken.


� Description:PA voltage adjusting path has broken.



Probable Cause I2C path disconnects.

Specific Problem I2C path disconnects.

System Impact Energy-saving is not achieved.

HandlingSuggestion

1. Plug out DTRU and check whether 6-pin to 6-pin data cableexists in current DTRU. If not, this DTRU doesn’t support PAvoltage adjustment function.

2. Check whether 6-pin to 6-pin data cable is inserted well. Ifnot, insert it properly and try again.

3. Replace the cable and try again.If alarm still exists, turn to 3.

4. This function doesn't affect the general use of DTRU, Whilethis DTRU could still be used until new DTRU which supportsPA power adjustment function arrives, and then replace it.

198088002 PA voltageadjusting read/write error.


� Description:PA voltage adjusting read/write error.



Probable Cause I2C data read/write has error.

Specific Problem I2C data read/write has error.




HandlingSuggestion

1. Please redownload PA voltage adjustment configuration andwait for 1 minute. If problem still exists,turn to

2. check and reconnect 6-pin to 6-pin data cable and redownloadconfiguration.If problem still exists,turn to

3. This function doesn't affect the general use of DTRU, Whilethis DTRU could still be used until new DTRU which supportsPA power adjustment function arrives, and then replace it.

198088003 PA voltageadjusting parameter turns tobe error.


� Description:PA voltage adjusting parameter turns to be error.



Probable Cause Static power setting data exceeds the range.

Specific Problem Static power setting data exceeds the range.


HandlingSuggestion

1. Static power data exceeds the level defined by GSM relatedprotocal, please correct the data.If alarm still exists, turn to

2. Reconfigure data and issue afterwards.

198088004 Access iBSCfailure


� Description:Access iBSC failure

� Severity:Major


Probable Cause Authentication failed or unconnected response

Specific Problem Authentication failed or unconnected response


HandlingSuggestion

1. Authentication again

2. Check physical link



198088005 Control linkbroken


� Description:Control link broken

� Severity:Major


Probable Cause Communication broken between BTS and BSC

Specific Problem Communication broken between BTS and BSC


HandlingSuggestion

1. First of all, decide the problem is HomeBTS failure or transmis-sion line problem.

2. Check whether it is software process problem by signaling an-alyzer if all device work well, and determine it is BSC or BTSprolbem.

3. Correct relevant software problem and announce to upgradethe software version.

198088006 Operation linkbroken(CS)


� Description:Operation link broken(CS)

� Severity:Minor


Probable Cause The transmission line disconnects.

Specific Problem The transmission line disconnects.


HandlingSuggestion

Check the transmission line.

198088007 Operation linkbroken(PS)


� Description:Operation link broken(PS)



� Severity:Minor


Probable Cause The transmission line disconnects.

Specific Problem The transmission line disconnects.


HandlingSuggestion


198088008 Parameterconfiguration mismatch


� Description:Parameter configuration mismatch

� Severity:Minor


Probable Cause iBSC parameter configuration failed, time out or process is inter-rupted (timeout or link breaks).

Specific Problem iBSC parameter configuration failed, time out or process is inter-rupted (timeout or link breaks).


HandlingSuggestion

Reconfigure parameters.

198088009 DSP initializationfailure


� Description:DSP initialization failure

� Severity:Minor





HandlingSuggestion


2. Reset DSP and check whether the alarm restores. If not, re-place corresponding HBTS.



198088010 Parameterconfiguration failure ofAD6537


� Description:Parameter configuration failure of AD6537

� Severity:Minor


Probable Cause AD6537 register read/write has error.

Specific Problem AD6537 register read/write has error.


HandlingSuggestion

Power-down restart and reconfigure AD6537 register to send cor-responding alarm message.

198088011 Tx PLL lost lockalarm


� Description:Tx PLL lost lock alarm

� Severity:Minor


Probable Cause Clock signal is unstable or TRM PLL has fault.

Specific Problem Clock signal is unstable or TRM PLL has fault.


HandlingSuggestion

1. Check HW between CMM and DTRU and reset DTRU .

2. If this alarm still exsits, replace DTRU as soon as possible.

198088012 Wrongparameter configurationfor EEPROM


� Description:Wrong parameter configuration for EEPROM



� Severity:Minor


Probable Cause EEPROM hardware error or invalid parameter which is written intoEEPROM previously, and result in the problem that EEPROM RFparameter cannot be read normally.

Specific Problem EEPROM hardware error or invalid parameter which is written intoEEPROM previously, and result in the problem that EEPROM RFparameter cannot be read normally.


HandlingSuggestion

Replace the DTRU.

198088013 FLASH memoryfault


� Description:FLASH memory fault

� Severity:Major


Probable Cause There are too many FLASH programming times, read/write erroror software calibration error.

Specific Problem There are too many FLASH programming times, read/write erroror software calibration error.


HandlingSuggestion

Reset HBTS and check alarm status; reload software version andcheck whether alarm restores, otherwise replace HBTS.

198088014 DSP worksabnormally.


� Description:DSP works abnormally.

� Severity:Major


Probable Cause DSP program has error.

Specific Problem DSP program has error.


HandlingSuggestion

Reset DSP, reload DSP software version and reconfigure CHP pa-rameters.



198088015 FPGA interfacefault


� Description:FPGA interface fault

� Severity:Major


Probable Cause DSP and FPGA interface disconnected.

Specific Problem DSP and FPGA interface disconnected.


HandlingSuggestion

Reload FPGA version and reset HBTS, if problem still exists, replaceHBTS.

198088016 CHP frameporcessing error alarm


� Description:CHP frame porcessing error alarm

� Severity:Minor


Probable Cause Because of interferen level on the circuit, frame number cumula-tion is interrupted.

Specific Problem Because of interferen level on the circuit, frame number cumula-tion is interrupted.


HandlingSuggestion

Reset HBTS

198088017 Wrong receivechannel of RF


� Description:Wrong receive channel of RF

� Severity:Minor




Probable Cause Reveiving channel has error, and cannot receive uplink signal prop-erly.

Specific Problem Reveiving channel has error, and cannot receive uplink signal prop-erly.


HandlingSuggestion

Redownload FPGA and DSP version, and reconfigure system pa-rameters.

198088018 Acquiring DNSfailure under dynamicconfigured IP mode


� Description:Acquiring DNS failure under dynamic configured IPmode

� Severity:Major


Probable Cause HBTS cannot acquire IP address from DNS server.

Specific Problem HBTS cannot acquire IP address from DNS server.


HandlingSuggestion

Manually configure DNS IP address by means of LMT tool.

198088019 Analysis failureof DNS domain name


� Description:Analysis failure of DNS domain name

� Severity:Major


Probable Cause HBTS cannot acquire IP adress which analysis iBSC domain namecorrectly from DNS server.

Specific Problem HBTS cannot acquire IP adress which analysis iBSC domain namecorrectly from DNS server.


HandlingSuggestion

Manually configure the information such as accessed iBSC IP ad-dress, interface number and so on by means of LMT tool.



198088020 IPSec startfailure


� Description:IPSec start failure

� Severity:Major


Probable Cause It cannot access properly.

Specific Problem It cannot access properly.


HandlingSuggestion

Reconfigure IPSec parameters.

198088021 Frequency pointand HTRG mismatch alarm


� Description:Frequency point and HTRG mismatch alarm

� Severity:Minor


Probable Cause Hardward board type doesn’t support configured frequency pointinformation.

Specific Problem Hardward board type doesn’t support configured frequency pointinformation.


HandlingSuggestion

1. Reconfigure the frequency point to match HTRG.

2. Replace HTRG that supports frequency point configurationrange.

198088022 DHCPautomatically acquiringIP address failure


� Description:DHCP automatically acquiring IP address failure

� Severity:Major




Probable Cause HBTS cannot acquire IP address automatically from DHCP server.

Specific Problem HBTS cannot acquire IP address automatically from DHCP server.


HandlingSuggestion

Use LMT tool to manually configure HBTS IP address, submask,gateway and interface number, as well as accessed iBSC IP ad-dress, gateway and interface number, etc.

198088023 Overhightemperature alarm


� Description:Overhigh temperature alarm

� Severity:Minor


Probable Cause BTS temperature is overhigh.

Specific Problem BTS temperature is overhigh.


HandlingSuggestion

Turn off power and check.

198088024 Voltageabnormity


� Description:Voltage abnormity

� Severity:Minor


Probable Cause BTS voltage is abnormal

Specific Problem BTS voltage is abnormal




HandlingSuggestion

Check the power.

198088025 Abis link switchalarm


� Description:Abis link switch alarm



Probable Cause Satellite backup BTS: if Abis link on the earth surface is broken,service will be switched to satellite backup link.

Specific Problem Satellite backup BTS: if Abis link on the earth surface is broken,service will be switched to satellite backup link.

System Impact If switched successfully, there is no impact on service.

HandlingSuggestion

Check Abis link on the earth surface and restore it as soon aspossible.

198088027 DIP E1 rack,rack type error


� Description:DIP E1 rack, rack type error



Probable Cause E1 rack DIP bit 15 to 12 indicates rack type error.

Specific Problem E1 rack DIP bit 15 to 12 indicates rack type error.

System Impact E1 rack reboot possibly cannot setup link.

HandlingSuggestion

Check E1 rack DIP switch bit 15 to 12.

198088028 DIP E1 rack,rack number error


� Description:DIP E1 rack, rack number error





Probable Cause E1 rack DIP bit 11 to 10 indicates rack number error.

Specific Problem E1 rack DIP bit 11 to 10 indicates rack number error.


HandlingSuggestion


198088029 DIP E1 rack,slave rack port 1 error


� Description:DIP E1 rack, slave rack port 1 error



Probable Cause E1 rack DIP bit 9 to 8 indicates slave rack port 1 error.

Specific Problem E1 rack DIP bit 9 to 8 indicates slave rack port 1 error.

System Impact E1 site slave rack 1 possibly doesn’t work properly.

HandlingSuggestion


198088030 DIP E1 rack,slave rack port 2 error


� Description:DIP E1 rack, slave rack port 2 error



Probable Cause E1 rack DIP bit 7 to 6 indicates slave rack port 2 error.

Specific Problem E1 rack DIP bit 7 to 6 indicates slave rack port 2 error.

System Impact E1 site slave rack 2 possibly doesn’t work properly.



HandlingSuggestion


198088031 DIP E1rack,satellite back up flagerror


� Description:DIP E1 rack,satellite back up flag error



Probable Cause E1 rack DIP bit 5 indicates satellite backup flag error.

Specific Problem E1 rack DIP bit 5 indicates satellite backup flag error.

System Impact Satellite backup link of E1 site possibly doesn’t work properly.

HandlingSuggestion

Check E1 rack DIP switch bit 5.

198088032 DIP E1 rack,OAM time slot error.


� Description: DIP E1 rack, OAM time slot error.



Probable Cause E1 rack DIP bit 4 to 0 indicates OAM time slot error.

Specific Problem E1 rack DIP bit 4 to 0 indicates OAM time slot error.




HandlingSuggestion


198088033 DIP IPrack,access mode error(IPor IPOE)


� Description:DIP IP rack,access mode error(IP or IPOE)



Probable Cause IP rack DIP bit 15 to 14 indicates access mode error (IP or IPOE).

Specific Problem IP rack DIP bit 15 to 14 indicates access mode error (IP or IPOE).

System Impact IP rack reboot possibly cannot setup link.

HandlingSuggestion

Check IP rack DIP switch bit 15 to 14.

198088034 DIP IP rack,racknumber error


� Description:DIP IP rack,rack number error



Probable Cause IP rack DIP bit 13 to 12 indicates rack number error.

Specific Problem IP rack DIP bit 13 to 12 indicates rack number error.


HandlingSuggestion


198088035 DIP IP rack,sitenumber error


� Description:DIP IP rack,site number error





Probable Cause IP rack DIP bit 11 to 0 indicates site number error.

Specific Problem IP rack DIP bit 11 to 0 indicates site number error.


HandlingSuggestion


198088036 DIP IPrack,sequence numbererror


� Description:DIP IP rack,sequence number error



Probable Cause IP rack: sequence number configured on NMS is wrong.

Specific Problem IP rack: sequence number configured on NMS is wrong.


HandlingSuggestion

Check the sequence number of corresponding IP site on NMS.

198088037 Mains powerfailure alarm


� Description:Mains power failure alarm

� Severity:Major


Probable Cause AC mains failure

Specific Problem AC mains failure

System Impact user define

HandlingSuggestion

check AC


C h a p t e r 3

Communication Alarm

Table of Contents198000519 Trunk error .................................................... 240198000520 Trunk abnormal .............................................. 241198001824 Abnormal status in SDH/SONET ........................ 242198001825 High BER on SDH / Sonet link........................... 246198003841 The control plane retransfer ratio over the thresh-old ................................................................................ 247198005122 Loss of Active/standby communication link ......... 247198005126 Incorrect FE Routing Connection ....................... 248198005127 FE Link Error Alarm......................................... 249198005128 Duplicate rack and shelf................................... 249198005378 Board HW Error .............................................. 250198005382 Communication between power board and OMP isabnormal ....................................................................... 251198005397 Communication of RAWMACIP channel is abnor-mal ............................................................................... 251198005401 Test packet check abnormal ............................. 252198005651 IP / MAC address conflict ................................. 253198005664 The rate of error code in a mate link is high atGUIM............................................................................. 253198005666 The number of the error packets from MAC portexceeds the threshold ...................................................... 254198015617 Some frames Received by FE/GE/ATM/MP/POS/E1 Port are faulty ............................................................ 255198015618 Faulty frames received by port over thresh-old ................................................................................ 256198015873 PSN board is sending out incorrect frames.......... 257198018689 UID unavailable .............................................. 257198019208 Timing of Near-End IMA Group Failure ............... 258198019212 Near-End Sending Link Broken ......................... 258198019213 LIF Alarm of Near-End Receiving Link ................ 259198019214 LODS Alarm of Near-End Receiving Link............. 259198019215 RDI Alarm of Far End Receiving Link.................. 260198019216 Near-End Receiving Link Faults ......................... 261198019218 Near-End Receiving Link Broken ....................... 261198019223 Ne Group is in fault state. ................................ 262198022784 BFD Session Interrupted .................................. 262198029953 The Ethernet port state is OAM loop back .......... 264198066000 Abis link broken.............................................. 264198066003 Control plane communication is abnormal be-tween board and its home module ..................................... 265198066004 Control plane communication is abnormal be-tween MP and OMP .......................................................... 266198066005 SCCP subsystem unavailable ............................ 266198066007 Broadband link overload .................................. 267198066008 MTP2 link sending overload ............................. 268198066009 MTP2 link reception overload ........................... 269



198066010 MTP3 Signalling Point Inaccessible .................... 269198066011 MTP3 link unavailable ...................................... 270198066012 MTP3 cluster inaccessible ................................. 271198066014 M3UA Signalling Point Inaccessible .................... 271198066015 SUA subsystem unavailable.............................. 272198066016 SUA office inaccessible .................................... 273198066019 Association link broken .................................... 274198066020 STC Signalling Point Inaccessible ...................... 275198066026 Association path broken................................... 275198066029 PPP link broken............................................... 276198066030 BSCIP configuration error in database................ 277198066066 AAL2 Path locally blocked................................. 278198066067 AAL2 Path remotely blocked ............................. 278198066068 AAL2 Path blocked by broken PVC ..................... 279198066071 Link broken for board fault ............................... 279198087336 Rack Abis control link broken............................ 279198087337 Site Abis control link broken............................. 280198087343 Front PC communication link broken alarm......... 281198087352 NSVC failure alarm.......................................... 282198087775 super site exchanged to the satellitic ABISlink................................................................................ 282198088026 IPOE uplink and downlink congestion alarm......... 283

198000519 Trunk errorAlarm Property � Alarm Code:198000519

� Description:Trunk error

� Severity:Major

� Alarm Type:Communications Alarm

Probable Cause 1. The receiving cable of local trunk equipment is faulty. The cableis disconnected, or cable connector is broken.

2. The transmitting cable of opposite trunk equipment is faulty.The cable is disconnected, or cable connector is broken.

3. Trunk transmission line is faulty. The local DDF and equipmentare not properly connected.

4. Operation of LOS insertion is operated at opposite trunk equip-ment. Manual inset alarm operation is performed in diagnostictest.

Specific Problem 1. The receiving cable of local trunk equipment is faulty. The cableis disconnected, or cable connector is broken.

2. The transmitting cable of opposite trunk equipment is faulty.The cable is disconnected, or cable connector is broken.

3. Trunk transmission line is faulty. The local DDF and equipmentare not properly connected.

4. Operation of LOS insertion is operated at opposite trunk equip-ment. Manual inset alarm operation is performed in diagnostictest.

System Impact The trunk equipment fails to work normally. All services based onthe trunk are interrupted.


Chapter 3 Communication Alarm

HandlingSuggestion

1. Check whether the alarm is caused by local end or opposite endvia meter measurement or loop test. Meter Measurement Usea trunk test meter to test whether the trunk receiving signals atlocal end are normal. If yes, fault might lie in local equipment.If no, troubleshoot at opposite end. Loop test Perform trunkself-loop at local end. If the alarm persists, fault might liein local equipment. If the alarm disappears, troubleshoot atopposite end.



198000520 Trunk abnormalAlarm Property � Alarm Code:198000520

� Description:Trunk abnormal

� Severity:Major


Probable Cause 1. Trunk frame formats at local end and at opposite end are in-consistent.

2. The transmitting end of opposite trunk equipment is faulty.

3. Local trunk equipment is faulty.

4. Equipment grounding at both ends is bad.

5. Impedance mismatch occurs.

Specific Problem 1. Trunk frame formats at local end and at opposite end are in-consistent.

2. The transmitting end of opposite trunk equipment is faulty.

3. Local trunk equipment is faulty.

4. Equipment grounding at both ends is bad.

5. Impedance mismatch occurs.

System Impact All services based on the trunk are interrupted.

HandlingSuggestion

1. Alarm details are displayed in NMS Alarm Management inter-face, where fault type is given. You can easily find handlingsuggestions according to the fault type. The handling sug-gestions for each fault type are described as below: 1.Loss ofE1 trunk frame, loss of E1 trunk multi-frame, E1 trunk alarmindication i. In NMS Configuration Management interface,right click the board and select Subunit Configuration to checkwhether frame format at both ends is the same. ii. In NMSConfiguration Management interface, right click the board andselect Subunit Configuration to check whether impedance iscorrect. iii. Check whether the grounding at both ends isproper. iv. If possible, locate alarm position, either at localend or at opposite end, by means of measurement instrument,loopback test, or board/cable replacement.

2. E1 trunk receives an alarm indication from opposite end. Checkthe alarm status of opposite end. Because the alarm indica-



tion is sent from opposite end, please solve the opposite-endproblem first.

198001824 Abnormal statusin SDH/SONET


� Description:Abnormal status in SDH/SONET

� Severity:Minor


Probable Cause 1. The upriver SDH equipment has faults.

2. The optical fiber on the optical distribution frame is wronglyconnected during optic fiber cutover and scheduling, or the ex-pected value is wrongly set in the network management sys-tem.

3. The upriver equipment has faults, such as LOS,LOF,RS TIM etc.

4. The up direction of the downstream equipment has faults.

5. As for all NEs in the multiplexing section where the board islocated, the fiber pigtail connectors in the down direction arecontaminated and the transmission line attenuation enhances,or optical transmission mode changes, which result in errorcodes; It may also be caused by ADM transmitting device fail-ure.

6. The upriver AU pointer processing unit has faults.

7. The upriver VC channel control unit has faults.

8. The optical fiber on the optical distribution frame is wronglyconnected, or the expected value is wrongly set in the networkmanagement system during optic fiber cutover and scheduling.

9. During project installation, the internal cross connection ofSDH network is not complete, or the SDT Board or Subcard re-mote device isn't equipped with the channel where SDT Boardor Subcard locates.

10.During project installation, the internal cross connection ofSDH network is not complete.

11.Network Node Failure in VC Channel Where Board Locates

12. Failure of the upstream VC channel control unit.

13. Failure of the upstream TU pointer processing unit.

14. Failure of the upstream TU tributary pointer processing unit,which may includes TU AIS\TU LOM\TU LOP\TU UNEQ.

15. )Fault of local TU tributary function. 2)The equipment of othernodes on TU tributary may has tributary function faults."

16. Failure of the upstream VC tributary control unit.



17. The cable on the optical distribution frame (DDF) is wronglyconnected, or the expected value is wrongly set in the networkmanagement system during cable cutover and scheduling.

18.During project installation, the internal cross connection ofSDH network is not complete, or the remote device isn'tequipped with the tributary.

19. The upstream and downstream circuit configuration of eachDXC during the corresponding timeslot is incomplete. The in-formation of V5 signal label is inconsistent with that at the peerend.

20.As for all NEs in the multiplexing section where the board islocated, the fiber pigtail connectors in the down direction arecontaminated and the transmission line attenuation enhances,or optical transmission mode changes, which result in errorcodes; It may also be caused by ADM transmitting device fail-ure.

21. )Signal reception attenuation excessive. 2)Failure of transmit-ting part of directly connected transmission equipment. 3)Un-clean optical fiber connectors or incorrect connection of them.4)Local-end receiving part failure."


Specific Problem 1. The upriver SDH equipment has faults.

2. The optical fiber on the optical distribution frame is wronglyconnected during optic fiber cutover and scheduling, or the ex-pected value is wrongly set in the network management sys-tem.

3. The upriver equipment has faults, such as LOS,LOF,RS TIM etc.

4. The up direction of the downstream equipment has faults.

5. As for all NEs in the multiplexing section where the board islocated, the fiber pigtail connectors in the down direction arecontaminated and the transmission line attenuation enhances,or optical transmission mode changes, which result in errorcodes; It may also be caused by ADM transmitting device fail-ure.

6. The upriver AU pointer processing unit has faults.

7. The upriver VC channel control unit has faults.

8. The optical fiber on the optical distribution frame is wronglyconnected, or the expected value is wrongly set in the networkmanagement system during optic fiber cutover and scheduling.

9. During project installation, the internal cross connection ofSDH network is not complete, or the SDT Board or Subcard re-mote device isn't equipped with the channel where SDT Boardor Subcard locates.

10.During project installation, the internal cross connection ofSDH network is not complete.

11.Network Node Failure in VC Channel Where Board Locates

12. Failure of the upstream VC channel control unit.



13. Failure of the upstream TU pointer processing unit.

14. Failure of the upstream TU tributary pointer processing unit,which may includes TU AIS\TU LOM\TU LOP\TU UNEQ.

15. )Fault of local TU tributary function. 2)The equipment of othernodes on TU tributary may has tributary function faults."

16. Failure of the upstream VC tributary control unit.

17. The cable on the optical distribution frame (DDF) is wronglyconnected, or the expected value is wrongly set in the networkmanagement system during cable cutover and scheduling.

18.During project installation, the internal cross connection ofSDH network is not complete, or the remote device isn'tequipped with the tributary.

19. The upstream and downstream circuit configuration of eachDXC during the corresponding timeslot is incomplete. The in-formation of V5 signal label is inconsistent with that at the peerend.

20.As for all NEs in the multiplexing section where the board islocated, the fiber pigtail connectors in the down direction arecontaminated and the transmission line attenuation enhances,or optical transmission mode changes, which result in errorcodes; It may also be caused by ADM transmitting device fail-ure.



System Impact 1. If alarm occurs on optical path, all trunk signals and serviceson this path are interrupted.

2. If alarm occurs on tributary, all trunk signals on this path areinterrupted, and all services on this trunk are interrupted.

HandlingSuggestion

1. Alarm details are displayed in NMS Alarm Management inter-face, where fault type is given. You can easily find handlingsuggestions according to the fault type. The handling sug-gestions for each fault type are described as below: 1.Regen-erator section trace identifier mismatch In NMS ConfigurationManagement interface, click SDH parameter configuration andselect SDH Optical Channel Parameter to check whether theconfiguration of "J0 configuration mode" and "regenerator sec-tion trace" at local end is consistent with those at opposite end.If no, modify the configuration to keep consistency.

2. Multiplex section remote defect indication Check alarm statusin the multiplex section of opposite end. Because the alarmorigin is from the opposite end, please solve the problem atopposite end first.

3. Multiplex section remote error indication Check alarm status inthe multiplex section of opposite end. Because the alarm originis from opposite end (B2 bit error), please solve the problemat opposite end first.



4. High order path trace identifier mismatch In NMS ConfigurationManagement interface, click SDH parameter configuration andselect SDH Optical Channel Parameter to check whether theconfiguration of "J1 Mode 0" and "high order path trace 0" atlocal end is consistent with those at opposite end. If no, modifythe configuration to keep consistency.

5. High order path unequipped In NMS Configuration Manage-ment interface, click SDH parameter configuration and selectSDH Optical Channel Parameter to check the configuration ofoptical channel payload type. If the configured value is 0, mod-ify the configuration.

6. High order path signal label mismatch In NMS ConfigurationManagement interface, click SDH parameter configuration andselect SDH Optical Channel Parameter to check the configura-tion of optical channel payload type. Ensure that the parameterconfiguration at both sides is the same.

7. High order path remote defect indication Check alarm status inthe high order path of opposite end. Because the alarm originis from opposite end, please solve the problem at at oppositeend first.

8. High order path remote error indication Check alarm status inthe high order path of opposite end. Because the alarm originis from opposite end (B3 bit error), please solve the problemat opposite end first.

9. Tributary unit remote defect indication/Tributary remote de-fect indication (VC-11) Check alarm status in the correspond-ing tributary unit at opposite end. Because the alarm origin isfrom opposite end, please solve the problem at opposite endfirst.

10. Tributary unit trace identifier mismatch In NMS ConfigurationManagement interface, click SDH parameter configuration andselect SDH Optical Channel Parameter to check whether theconfiguration of "J2 mode" and "low order path trace" at localend is consistent with those at opposite end. If no, modifyconfiguration to keep consistency.

11. Tributary unit unequipped In NMS Configuration Managementinterface, click SDH parameter configuration and select SDHOptical Channel Parameter to check the configuration of tribu-tary unit payload type. If the configured value is 0, modify theconfiguration.

12. Tributary unit signal label identifier mismatch In NMS Config-uration Management interface, click SDH parameter configu-ration and select SDH Optical Channel Parameter to check theconfiguration of tributary unit payload type. Ensure that theparameter configuration at both sides is the same.

13.Others i. Use measurement instrument or loopback test tojudge whether the alarm is caused by local end or oppositeend. a. Measurement instrument Use a SDH test instrumentto test whether the received optical signals at local end arenormal. If normal, it means opposite end has a fault. Pleasesolve the relevant problem. b. Loop Test Carry out a self-looptest at local SDH equipment. If the alarm still occurs, it meanslocal end has a fault. If the alarm disappears, it means oppositeend has a fault. P...



198001825 High BER onSDH / Sonet link


� Description:High BER on SDH / Sonet link



Probable Cause 1. Attenuation of receiving signals of local SDH equipment islarge.

2. The transmitting part of opposite SDH equipment is faulty.

3. Fiber connector is polluted or misconnected.

4. The receiving part of local SDH equipment is faulty.

5. Operation of bit error insertion is performed at opposite end.

Specific Problem 1. Attenuation of receiving signals of local SDH equipment islarge.

2. The transmitting part of opposite SDH equipment is faulty.

3. Fiber connector is polluted or misconnected.

4. The receiving part of local SDH equipment is faulty.

5. Operation of bit error insertion is performed at opposite end.

System Impact SDH/SONET equipment can work. However, call loss or noise oc-curs to all voice services on this optical path, and bit error occurson the data service channel.

HandlingSuggestion

1. Use meter measurement or loop test to judge whether thealarm is caused by local end or opposite end. Meter Measure-ment Use a SDH test meter or optical power meter to testwhether the receiving optical signals at local end are normal.If normal, fault might lie in local equipment. If abnormal, faultlies in opposite end or on transmission side. Inform the op-posite end or transmission side to troubleshoot. Loop TestPerform fiber self-loop at local SDH equipment. If the alarmpersists, fault might lie in local equipment. If the alarm disap-pears, inform the opposite end to troubleshoot.

2. Replace optical module.

3. Replace optical fiber.

4. Replace board.



198003841 The controlplane retransfer ratio overthe threshold


� Description:The control plane retransfer ratio over the thresh-old

� Severity:Major


Probable Cause There are some badly-touched boards in the system environmentand the retransfer-ratio of RUDP packets increases.

Specific Problem There are some badly-touched boards in the system environmentand the retransfer-ratio of RUDP packets increases.

System Impact The master board will change when slave is exist.

HandlingSuggestion

Make records of the alarm information and contact ZTE Corpora-tion.

198005122 Lossof Active/standbycommunication link


� Description:Loss of Active/standby communication link

� Severity:Minor


Probable Cause 1. The board is configured to be in active/standby mode, but theopposite board is not in position.

2. Hardware Problem.

Specific Problem 1. The board is configured to be in active/standby mode, but theopposite board is not in position.

2. Hardware Problem.

System Impact The active board can not communicate with the standby board.As a result, active/standby changeover operation fails. There isno impact on services.

HandlingSuggestion

1. Make sure the board is configured in active/standby mode, andboth active/standby boards are in position.

2. Check whether the opposite board has the following alarm. Ifyes, please solve the problem according to recommended han-



dling suggestions. Description: 8393987 Board offline or CPUin reset status for a long period


4. Change the slots of the active board and the slave board.

198005126 Incorrect FERouting Connection


� Description:Incorrect FE Routing Connection



Probable Cause 1. FE-C3/4 is used for FE routing port when RUIM1 rear board isused.

2. When CHUB is connected to UIM/GUIM, CHUB rear card(RCHUB1/RCHUB2) uses discrete ports (e.g. port1/port3) toconnect UIM rear card.

3. When UIM/GUIM is connected to UIM/GUIM CHUB, connectionsused for FE routing connection are not in pairs (e.g.FE-C2/4).

4. When UIM is connected to UIM/CHUB, only one cable is usedfor FE inter-connection.

Specific Problem 1. FE-C3/4 is used for FE routing port when RUIM1 rear board isused.

2. When CHUB is connected to UIM/GUIM, CHUB rear card(RCHUB1/RCHUB2) uses discrete ports (e.g. port1/port3) toconnect UIM rear card.

3. When UIM/GUIM is connected to UIM/GUIM CHUB, connectionsused for FE routing connection are not in pairs (e.g.FE-C2/4).

4. When UIM is connected to UIM/CHUB, only one cable is usedfor FE inter-connection.

System Impact Control plane routing is disconnected; ports are switched over incycle; all services on this shelf are interrupted.

HandlingSuggestion

1. Reconnect the FE wire. 1. If the UIM board on the BUSNshelf uses RUIM1 backcard, make sure FE-C1/2 port is usedfor routing port.

2. If the GUIM board is on BGSN shelf, make sure FE1 and FE2ports are used as routing ports.

3. If TRUNK mode is used, numerous FE ports make up of aTRUNK port for cascaded connection. In this case, makesure the both ends are paired ports. If the boards of thelocal board or the opposite board are not paired port, pleasereconnect the FE wire and make sure the both ends are usedpaired ports. Here is an example of connection method: i.When CHUB is connected with UIM/GUIM, the connectingwire on RCHUB1/RCHUB2 of CHUB backcard must be used



continuous ports ( such as port1/port2 pair, port3/port4 pair,port5/port6 pair, port7/port8 pair ) to connect with the pairson the UIM/GUIM backcard. ii. When UIM is connected withUIM/GUIM/CHUB, the ports on UIM backcard must be usedas paired .If RUIM1 backcard is used, then two FE-C1/2 portsmust be used for FE routing ports; if RUIM2/RUIM3 backcardis used, then use FE1/FE2 pair, FE3/FE4 pair or FE5/FE6 pairfor the FE routing ports. iii. When GUIM is connected withUIM/GUIM/CHUB, the ports on GUIM backcard must be usedas pair, i. e. , FE1 and FE2 must be used for FE routing ports.

198005127 FE Link ErrorAlarm


� Description:FE Link Error Alarm

� Severity:Minor


Probable Cause 1. In a pair of FE ports, one has normal link but the other has linkerror.

2. The hardware is faulty.

Specific Problem 1. In a pair of FE ports, one has normal link but the other has linkerror.


System Impact Because one FE port has normal control plane link, services arenot affected. However if this port is faulty, services can not beswitched to the other port, leading to service interruption.

HandlingSuggestion

1. Check if only one cable is used to connect the port pair of therear board to the peer-end FE port. Ensure that both cablesare connected to the peer end.

2. Reconnect the cables or replace the cables.



198005128 Duplicate rackand shelf


� Description:Duplicate rack and shelf

� Severity:Minor




Probable Cause Shelf connect to the system with duplicate physical ID

Specific Problem Shelf connect to the system with duplicate physical ID

System Impact Boards in the shelf which power-on later power-on failure.

HandlingSuggestion

1. Check whether two shelf with same physical ID exists. Modifythe switch of one of the two shelfs and reset the shelf andboard if such connection exists.

2. Check if the board link to the same board by different link type.Remove one of link type and reset the board if such connectionexists.

198005378 Board HW ErrorAlarm Property � Alarm Code:198005378

� Description:Board HW Error

� Severity:Major


Probable Cause 1. Clock is not synchronous.

2. Either the board or the slot has a hardware fault.

Specific Problem 1. Clock is not synchronous.

2. Either the board or the slot has a hardware fault.

System Impact HW connection is affected and services carried over this HW areinterrupted.

HandlingSuggestion

1. Check whether the board has one of the following alarms. Ifyes, please solve the problem according to corresponding han-dling suggestions. Related Alarms 1286 Loss of input clock5646 Phase-locked Loop Unlocked

2. Check whether the clock board has one of the following alarms.If yes, please solve the problem according to correspondinghandling suggestions. Related Alarms 26133 Output clock lost26129 Clock reference source lost (Level 1 alarm) 26128 Clockreference source lost (Level 2 alarm) 26127 Clock referencesource lost (Level 3 alarm)

3. In Configuration Management interface, check whether APSprotection is configured when the SDTB/SDTB2 works in mas-ter/slave mode. How to check APS protection configuration: Inthe Configuration Management interface, click Rack, select theconcerned board (SDTB/SDTB2). Then right click it. A shortcutmenu appears. Then select Optical Port APS Protection.


5. Replace the slot




198005382 Communicationbetween power board andOMP is abnormal


� Description:Communication between power board and OMP isabnormal

� Severity:Major


Probable Cause 1. The power board is not connected to the OMP or the connectionis wrong.

2. The power board locates in a rack. The configured rack numberis different from that where DIP switch of the power boardlocates.

Specific Problem 1. The power board is not connected to the OMP or the connectionis wrong.

2. The power board locates in a rack. The configured rack numberis different from that where DIP switch of the power boardlocates.

System Impact The system can not monitor the status of power supply and envi-ronmental situation. However, there is no impact on services.

HandlingSuggestion

1. Reconnect the RS485 cable between the power board and OMP.

2. Make sure the rack number configured for the rack in whichthis power board locates is consistent with the rack numberswitch set for the power board.

198005397 Communicationof RAWMACIP channel isabnormal


� Description:Communication of RAWMACIP channel is abnormal

� Severity:Major


Probable Cause 1. The CPU usage of the UIM/GUIM in the shelf is too high.

2. The service media stream exceeds the threshold.


Specific Problem 1. The CPU usage of the UIM/GUIM in the shelf is too high.



2. The service media stream exceeds the threshold.


System Impact The channel between user plane processing board and signalingprocessing board is abnormal. This causes degradation of QoS. Inserious situation, services will be interrupted.

HandlingSuggestion

1. In NMS Alarm Management interface, check whether theUIM/GUIM board of the same shelf has a relevant alarm. Ifyes, please solve the problem according to correspondinghandling suggestions. Related alarm: 2560 Board CPU over-loaded



4. Replace the slot.

198005401 Test packetcheck abnormal


� Description:Test packet check abnormal

� Severity:Major


Probable Cause 1. The board is faulty.

2. The line from UIM/GUIM to GLI is abnormal.

Specific Problem 1. The board is faulty.

2. The line from UIM/GUIM to GLI is abnormal.

System Impact 1. Service transfer at medial plane is affected. The alarm detailsinclude fault type. Each fault type has different impacts on thesystem. 1. If fault type is "ATM abnormal", the ATM board cannot provide normal ATM services. Thus, services carried by theboard is interrupted.

2. If fault type is "L1 switch abnormal", it indicates that mediaplane communication is abnormal. This causes all services car-ried on the shelf to be interrupted.

HandlingSuggestion

1. Alarm details are displayed in NMS Alarm Management inter-face, where fault type is given. You can easily find handlingsuggestions according to the fault type. The handling sugges-tions for each type are described as below. 1. Fault type:ATM abnormal The link between C5 and APC of ATM processingboard is abnormal. In this case, replace the board.

2. Fault type: L1 switch abnormal The L1 media plane switchingfrom UIM/GUIM to GLI is abnormal. This is usually causedby abnormal link between UIM/GUIM and GLI. In this case,reconnect the cable between UIM/GUIM and GLI, or replacethe cable. If optical fiber is used, replace the optical module.



198005651 IP / MACaddress conflict


� Description:IP / MAC address conflict

� Severity:Major


Probable Cause 1. Board has rebooted and MAC address is incorrect.

2. Board has recalculated the MAC address, which is incorrect.

3. Addition of new shelf on the rack that has the same DIP settingsas the other shelf.

Specific Problem 1. Board has rebooted and MAC address is incorrect.

2. Board has recalculated the MAC address, which is incorrect.

3. Addition of new shelf on the rack that has the same DIP settingsas the other shelf.

System Impact If IPMAC conflicts, control plane communication may become ab-normal. For the board that has been powered on, packets maybe lost and services are unstable. In serious situation, link in-terruption may occur and all services borne on the board will beinterrupted. For the board that is being powered on, the boardmay reset repeatedly, and services can not be accessed.

HandlingSuggestion

1. Unplug and plug the board.

2. Compare 2 DIP switches on 2 backplane boards, one is relatedto the board, the other is related to OMP board. If the 2 DIPswitches have different settings, please correct the settings tokeep consistency. Reset the relevant boards after setting.

3. Reset the board.

198005664 The rate of errorcode in a mate link is high atGUIM


� Description:The rate of error code in a mate link is high at GUIM

� Severity:Minor


Probable Cause The rate of error code in a mate link is high.

Specific Problem The rate of error code in a mate link is high.

System Impact The data transferred via mate link are incorrect.



HandlingSuggestion

1. heck if the board is inserted tightly. Y->Please contact ZTECorporation. N->Insert the board tightly,and then check if thealarm is eliminated: Y->end, N->contact ZTE Corporation.

198005666 The number ofthe error packets from MACport exceeds the threshold


� Description:The number of the error packets from MAC portexceeds the threshold

� Severity:Minor


Probable Cause The number of the error packets from MAC port exceeds thethreshold.

Specific Problem The number of the error packets from MAC port exceeds thethreshold.

System Impact The MAC port is unavailable or the flow is limited.

HandlingSuggestion

1. Check whether the connection between this port and the peerport is correct.

Y->Go to "2"

N->Check whether the cable connecting two ports is damaged.It is recommended to replace a new cable. If the alarm disap-pears: Y-> End, N-> Go to "2".

2. Try to replace the network interface on the peer end and thencheck if the alarm disappears.

Y->End.

N->Go to "3"

3. Try to replace the board or the network interface on the localend and then check if the alarm disappears.

Y->End.

N->Please contact ZTE Corporation.



198015617 Someframes Received byFE/GE/ATM/MP/POS/E1Port are faulty


� Description:Some frames Received by FE/GE/ATM/MP/POS/E1Port are faulty

� Severity:Minor


Probable Cause 1. The network connected with FE/GE/ATM/MP/POS/E1 port is ab-normal.

2. The board is in abnormal status.

3. Board hardware is faulty. For example, the network processorsub card is not tightly inserted.

4. Other board hardware faults.

Specific Problem 1. The network connected with FE/GE/ATM/MP/POS/E1 port is ab-normal.

2. The board is in abnormal status.

3. Board hardware is faulty. For example, the network processorsub card is not tightly inserted.

4. Other board hardware faults.

System Impact Datagram reception of the board is affected. The service on thisport might be unstable. Worst of all, all services on the boardmight be interrupted.

HandlingSuggestion

1. Unplug and plug port fibber/network cable.

2. Replace port fibber/network cable.

3. Reset the board.

4. Unplug and plug board.




198015618 Faulty framesreceived by port overthreshold


� Description:Faulty frames received by port over threshold

� Severity:Minor


Probable Cause 1. Network status of FE/GE/ATM/MP/POS/E1 port is abnormal.

2. Board hardware faults.

3. Other faults of the board cause faulty FE/GE/ATM/MP/POS/E1reception.

4. Network processor sub-card which has worked normally isloose.

Specific Problem 1. Network status of FE/GE/ATM/MP/POS/E1 port is abnormal.

2. Board hardware faults.

3. Other faults of the board cause faulty FE/GE/ATM/MP/POS/E1reception.

4. Network processor sub-card which has worked normally isloose.

System Impact Datagram reception of the board is affected. The service on theboard might be unstable.

HandlingSuggestion

1. Pull out/insert in the fiber/network cables to check if the faultis eliminated.

Y-> Finish the alarm handling.

N-> go to "2".

2. Replace fiber/network cables to check if the fault is eliminated.


N-> go to "3".

3. Restart the board to check if the fault is eliminated.


N-> go to "4".

4. Pull out/insert the board to check if the fault is eliminated.


N-> go to "5".

5. Replace the board to check if the fault is eliminated.


N-> For other reasons, please contact ZTE Corporation.



198015873 PSN board issending out incorrect frames


� Description:PSN board is sending out incorrect frames

� Severity:Major


Probable Cause 1. PSN board in the same shelf is abnormal.

2. PSN board is faulty

Specific Problem 1. PSN board in the same shelf is abnormal.

2. PSN board is faulty

System Impact If the fault lies in PSN board, service of the entire RNC NE willbecome unstable. If the alarm persists, all services will be inter-rupted. If the fault lies in the board where the alarm is declared,only the services on this board are affected.

HandlingSuggestion

1. Check if the following alarm exists in PSN board at the sameshelf. If yes, refer to the corresponding alarm handling sugges-tion. Related alarm: 19456 All high-speed links between linecard and package (packet) switching board are out of synch

2. Unplug and plug board.

3. Replace board.

198018689 UID unavailableAlarm Property � Alarm Code:198018689

� Description:UID unavailable

� Severity:Major


Probable Cause 1. This alarm occurs when a UID is created, and disappears whenthe link gets through.

2. The link is broken.

Specific Problem 1. This alarm occurs when a UID is created, and disappears whenthe link gets through.

2. The link is broken.

System Impact The service on the UID will be interrupted.

HandlingSuggestion

The UID becomes available one at least one HDCL under this UIDbecomes available, and this alarm disappears automatically in thiscase. To make the HDLC available, perform according to the alarmfor HDLC unavailable.



198019208 Timing ofNear-End IMA Group Failure


� Description:Timing of Near-End IMA Group Failure

� Severity:Major


Probable Cause Far end IMA group clock template sent by the remote end throughICP cells does not match with the near-end one. For example, ITC(Independence Transmit Clock) on the remote end does not matchwith CTC (Common Transmit Clock) on the near end.

Specific Problem Far end IMA group clock template sent by the remote end throughICP cells does not match with the near-end one. For example, ITC(Independence Transmit Clock) on the remote end does not matchwith CTC (Common Transmit Clock) on the near end.

System Impact IMA link may fail to be established.

HandlingSuggestion

1. heck if the clock mode on the near end is matched with thaton the far end. Y->If it is matched, contact ZTE Corporation.N->If not, modify the configuration. If the alarm is eliminated,finish the alarm handling. If not, please contact ZTE Corpora-tion.

198019212 Near-EndSending Link Broken


� Description:Near-End Sending Link Broken

� Severity:Major


Probable Cause When some sending link could not connect to the far end IMA grouplike other links, this alarm appears.

Specific Problem When some sending link could not connect to the far end IMA grouplike other links, this alarm appears.

System Impact IMA link fails to be established.

HandlingSuggestion

1. heck if IMA chip works normally and each link can connect tothe far end IMA group normally. Y->If the chip works normallyand each link connects to the far end IMA group successfully,contact ZTE Corporation for help. N->If not, configure themagain. If the alarm is eliminated, finish the alarm handling. Ifnot, please contact ZTE Corporation.



198019213 LIF Alarm ofNear-End Receiving Link


� Description:LIF Alarm of Near-End Receiving Link

� Severity:Major


Probable Cause Physical fault or connection error occurs to E1 link.

Specific Problem Physical fault or connection error occurs to E1 link.

System Impact IMA link is down. If several links are available in the IMA group,bandwidth of the IMA group will be affected, and the number ofsuccessful upper-layer service access will decrease. However, ser-vice interruption will not occur. If merely one link is available inthe IMA group, all services on the IMA group are interrupted.

HandlingSuggestion

1. On NMS fault management interface, view alarm Details whereinformation of IMA chip ID, IMA group ID, IMA link ID, and E1index is given. Locate the faulty IMA link according to thegiven information. 1. Refer to user's networking plan to see ifconnection error exists.

2. On NMS fault management interface, check if E1-related alarmexists in the board. If yes, refer to the corresponding alarmhandling suggestion. Related alarms: 519 Trunk error 519Trunk abnormal 1026 Cell delineation do not synchronizationabout cell on E1 link

198019214 LODS Alarm ofNear-End Receiving Link


� Description:LODS Alarm of Near-End Receiving Link

� Severity:Major


Probable Cause 1. Operation of the input clock is abnormal.

2. Transmission quality of the link is poor.

3. Self-loop occurs to some cable connection in IMA group

4. Cable connection is incorrect in IMA group.

5. Hardware is faulty.

Specific Problem 1. Operation of the input clock is abnormal.

2. Transmission quality of the link is poor.

3. Self-loop occurs to some cable connection in IMA group



4. Cable connection is incorrect in IMA group.

5. Hardware is faulty.

System Impact IMA link is down. If several links are available in the IMA group,bandwidth of the IMA group will be affected, and the number ofsuccessful upper-layer service access will decrease. However, ser-vice interruption will not occur. If merely one link is available inthe IMA group, all services on the IMA group are interrupted.

HandlingSuggestion

1. Check alarm details on the NMS Alarm Management interfaceto find the IMA chip ID, IMA group ID, IMA link ID, and E1 ID,and locate the faulty IMA link. 1. Check the RUN indicator onthe clock board. If the indicator is green and flashes slowly, itmeans the clock board is normal; otherwise, reboot or replacethe clock board.

2. Check whether there is any of the following clock-relatedalarms on UIM/GUIM on the NMS Alarm Management inter-face. If yes, the input clock source must be wrong. Handleit according to the corresponding suggestions. 1286 Loss ofinput clock 5646 Phase-locked Loop Unlocked

3. Check whether there is any of the following E1-related alarmson the NMS Alarm Management interface. If yes, handle it ac-cording to the corresponding suggestions. 519 Trunk error 520Trunk abnormal 1026 Cell delineation do not synchronizationabout cell on E1 link

4. Check whether there is any self-loop in the IMA group at re-mote end. If yes, correct the connection according to the net-working plan.

5. Check cable connections according to the networking plan tomake sure that each cable is correctly connected.

6. Reboot the faulty board.

7. Replace the faulty board.

198019215 RDI Alarm of FarEnd Receiving Link


� Description:RDI Alarm of Far End Receiving Link

� Severity:Major


Probable Cause 1. Remote IMA link is not in activated status.

2. Remote receiving direction is faulty.

Specific Problem 1. Remote IMA link is not in activated status.

2. Remote receiving direction is faulty.

System Impact IMA link is down. If several links are available in the IMA group,bandwidth of the IMA group will be affected, and the number ofsuccessful upper-layer service access will decrease. However, ser-



vice interruption will not occur. If merely one link is available inthe IMA group, all services on the IMA group are interrupted.

HandlingSuggestion

On NMS fault management interface, view alarm Details where in-formation of IMA chip ID, IMA group ID, IMA link ID, and E1 indexis given. Locate the faulty IMA link according to the given infor-mation. Check the working status of the relevant remote receivinglink by referring to the opposite equipment operation guide. If re-mote receiving link is not in activated status, activate the link.

198019216 Near-EndReceiving Link Faults


� Description:Near-End Receiving Link Faults

� Severity:Major


Probable Cause If a receiving link on near end has faults, this alarm appears onthe near end.

Specific Problem If a receiving link on near end has faults, this alarm appears onthe near end.

System Impact IMA link fails to be established.

HandlingSuggestion

1. heck if IMA chip works normally and each link can connect tothe near IMA group normally. Y->If the chip works normallyand each link connects to the near IMA group successfully, con-tact ZTE Corporation for help. N->If IMA chip works abnor-mally or there is a link which does not access to near end IMAgroup, handle this problem. If the alarm is eliminated, finishthe alarm handling. If not, please contact ZTE Corporation forhelp.

198019218 Near-EndReceiving Link Broken


� Description:Near-End Receiving Link Broken

� Severity:Major


Probable Cause When some receiving links can not connect to the remote IMAgroup like other links, this alarm appears.

Specific Problem When some receiving links can not connect to the remote IMAgroup like other links, this alarm appears.



System Impact The physical link on Iu interface fails to be established.

HandlingSuggestion

1. heck receiving link connections on the two ends to see if eachreceiving link is connected to the remote IMA group normallyand if the proper local E1 link is connected to the correspondingE1 link on far end. Y->If so, contact ZTE Corporation for help.N->If not, find the fault causes and handle the problem. If thealarm is eliminated, finish the alarm handling. If not, pleasecontact ZTE Corporation for help.

198019223 Ne Group is infault state.


� Description:Ne Group is in fault state.

� Severity:Major


Probable Cause 1. All IMA links of this IMA group are broken.

2. The peer-end IMA group is broken.

Specific Problem 1. All IMA links of this IMA group are broken.

2. The peer-end IMA group is broken.

System Impact The IMA Group does not work

HandlingSuggestion

Fix the broken IMA links in the IMA group.

198022784 BFD SessionInterrupted


� Description:BFD Session Interrupted

� Severity:Minor


Probable Cause 1. The network cable connection on relevant equipment (includ-ing local/intermediate/opposite equipment) is loose or discon-nected.

2. Intermediate equipment is faulty.

3. Opposite equipment is faulty.

4. Local equipment is faulty.

5. Configuration related to the BFD session is incorrect.



Specific Problem 1. The network cable connection on relevant equipment (includ-ing local/intermediate/opposite equipment) is loose or discon-nected.

2. Intermediate equipment is faulty.


4. Local equipment is faulty.

5. Configuration related to the BFD session is incorrect.

System Impact All services on the path relating to the BFD session will be switchedto the standby path. Service interruption will occur if no standbypath exists.

HandlingSuggestion

1. Check alarm details on the NMS Alarm Management interfaceto find the source address and the destination address of theBFD session. The source address refers to the address of localequipment. The destination address refers to the address ofthe opposite BFD session equipment. 1. Check the status ofthe line card at the local end. If the line card restarts repeat-edly, replace it and power on.

2. Check the physical connection between the BFD session-re-lated port and the local line card. If the connection is loose orbroken, tighten or replace the cable. If the port indicator is on,it means the physical connection is normal.

3. Ping intermediate and termination equipment in turn with cor-rect IP address. i. Telnet to the interface board to check thelink by making a ping test. For example, if the destinationaddress is 2.2.2.10, enter the following command in the tel-net interface. brs_ping_b "2.2.2.10" ii. Wait for 5 seconds,and then enter the next command. BrsShowLog "ICMP" a. If"PING===>destine 2.2.2.10 timeout" displays on the screen,it means the response times out. b. If "ping_receive:Replyfrom 2.2.2.10: bytes=60 time<1ms" displays on the screen,it means the link is normal. iii. In case of timeout, check ifthe related route and address are configured correctly. If not,correct the reconfiguration and do a ping test again. iv. Ifthe route/address is configured correctly but the repsonse stilltimes out, it means a link is broken or the intermediate equip-ment is faulty. In this case, check to see if there is any brokennetwork cable, loose connection or abnormal equipment alongthe BFD session path. If yes, take necessary actions, such asreplacing the broken cable, tightening the connection, or re-pairing or replacing the fault equipment, to solve the problem.

4. If the ping test indicates that packets can be received and sentnormally at both ends, check to see if the BFD session at bothends is configured correctly by performing the following steps:i. Check the configuration of BFD session on the NMS Configu-ration Management interface to ensure the BFD switch is in "en-abled" status. ii. Make sure that the BFD session is configuredwith the same working mode at both sides. iii. Make sure thatat least one device plays an "active" role for the BFD session.iv. Make sure that the BFD session exists at both ends, andthat the source and the destination IP addresses are matched.v. Make sure that the hop mode (single hop/multi-hop) is con-sistent at both ends. vi. Make sure that the authenticationinformation is consistent at both ends.

5. Reboot the board where the interface is located.



198029953 The Ethernetport state is OAM loop back


� Description:The Ethernet port state is OAM loop back

� Severity:Minor


Probable Cause The local port state is loop back because the peer port starts Eth-ernet OAM loop back request of 802.3ah.

Specific Problem The local port state is loop back because the peer port starts Eth-ernet OAM loop back request of 802.3ah.

System Impact The Ethernet link which is in loop back test can't bear service data.

HandlingSuggestion

Check if the peer port has started Ethernet OAM loop back test. Ifyes, stop it, if no, disable local port Ethernet OAM.

198066000 Abis link brokenAlarm Property � Alarm Code:198066000

� Description:Abis link broken

� Severity:Major


Probable Cause 1. A newly configured link is initially broken.

2. The link status changes to broken.

3. The link may break frequently during active/standbyswitchover.

Specific Problem 1. A newly configured link is initially broken.

2. The link status changes to broken.

3. The link may break frequently during active/standbyswitchover.

System Impact BTS break-down

HandlingSuggestion

If the new Abis link. Please synchronize and wait with no otheroperation, the alarm will resume after 1 minute. If master/slavechange happened before, the alarm will resume after 1 minute, noneed any operation. Check the board has alarm "2560 Board cpuoverload", please deal with first.



198066003 Control planecommunication is abnormalbetween board and its homemodule


� Description:Control plane communication is abnormal betweenboard and its home module

� Severity:Major



2. The board is blocked.

3. The inserted board is different from board configuration.

4. The board is faulty.

5. The control plane communication is abnormal.

6. The board is reset.


2. The board is blocked.

3. The inserted board is different from board configuration.



6. The board is reset.

System Impact The services carried by the board are interrupted.

HandlingSuggestion

1. Check whether the board is in position. If not, insert the board.

2. Check whether the board is in blocked status. If yes, unblockthe board.

3. Check whether the inserted board is the same as the configuredboard. If not, insert a correct board.

4. Reset the board. Wait for the board to be powered on.


6. Replace the board slot.

7. Replace the UIM/GUIM board of the same shelf.



198066004 Control planecommunication is abnormalbetween MP and OMP


� Description:Control plane communication is abnormal betweenMP and OMP

� Severity:Major





4. The board resets.




4. The board resets.

System Impact The board is blocked so that it can not provide functions. Further-more, all services under the relevant module become unavailable.

HandlingSuggestion

1. Check if the board is in position. If not, insert the board.

2. Reset the board. Wait for the board to be powered on.


4. Replace the board slot.

5. Replace the UIM/GUIM board in the same shelf.

198066005 SCCPsubsystem unavailable


� Description:SCCP subsystem unavailable

� Severity:Minor


Probable Cause 1. From the perspective of A, remote signaling point subsystemis out of service.

2. From the perspective of A, remote signaling point is inaccessi-ble.



3. Remote subsystem (for B) is configured at A end, but the cor-responding local subsystem (for B) is not configured at B end.

4. Local subsystem (for B) is blocked at B end.

5. From the perspective of A, SCCP user is not configured in re-mote MTP3 or M3UA user configuration.

Specific Problem 1. From the perspective of A, remote signaling point subsystemis out of service.

2. From the perspective of A, remote signaling point is inaccessi-ble.



5. From the perspective of A, SCCP user is not configured in re-mote MTP3 or M3UA user configuration.

System Impact Signaling data can not be sent to/received from the relevant sub-system. New service can not access to the corresponding office.And existing services are interrupted abnormally.

HandlingSuggestion

1. Check whether there exists office (the office that correspondsto the subsystem) inaccessible alarm. If yes, refer to thecorresponding alarm handling suggestion. Related alarms: i.8400128 MTP3 office inaccessible ii. 8400384 M3UA office in-accessible

2. Unblock the subsystem in dynamic data management.

3. On NMS configuration management interface, check the con-figuration of signaling point code (for A) at A end. See if SCCPuser is included in user type configuration. If no, add the con-figuration. Meanwhile, check the corresponding configurationat B end.

4. Check whether the status of signaling point subsystem (for B)is available at B end. If no, the signaling point subsystem at Bend must be out of service. Locate the cause for the abnormalstatus.

5. Check whether the signaling point subsystem (for B) is config-ured at B end. If no, add the configuration at B end.

198066007 Broadband linkoverload


� Description:Broadband link overload

� Severity:Minor


Probable Cause 1. There are too many messages from upper layer service.

2. The number of links is insufficient.



3. Link load is uneven.

Specific Problem 1. There are too many messages from upper layer service.

2. The number of links is insufficient.

3. Link load is uneven.

System Impact Link overload leads to the loss of all upper-layer service messages.Call loss will occur and access success rate of PS services will fall.

HandlingSuggestion

1. Check the counter of "Peak Traffic of Signaling Link" in MTP3Bsignaling link performance statistics. If the load (nearly)reached 6000 during alarm occurrence, upper layer trafficmust be heavy. Add links to share load.

2. On NMS configuration management interface, check the sig-naling link configuration of NE. Add or delete links to ensurethat the number of links in a link set is two to the power of N.If there are two link sets in the current route, ensure that twolink sets have the same number of links.

198066008 MTP2 linksending overload


� Description:MTP2 link sending overload

� Severity:Major


Probable Cause The traffic flow carried by the MTP2 is excessive under the con-dition of current link bandwidth. It exceeds the alarm thresholdof link transmission load. The alarm threshold is related to MITP2link type. For 64K link, the alarm threshold is: bandwidth occupa-tion ratio reaches 0.8. For N*64k or 2M link, the alarm thresholdis: bandwidth occupation ratio reaches 0.6.

Specific Problem The traffic flow carried by the MTP2 is excessive under the con-dition of current link bandwidth. It exceeds the alarm thresholdof link transmission load. The alarm threshold is related to MITP2link type. For 64K link, the alarm threshold is: bandwidth occupa-tion ratio reaches 0.8. For N*64k or 2M link, the alarm thresholdis: bandwidth occupation ratio reaches 0.6.

System Impact If MTP2 link is overloaded for quite a long time, the signalling linkwill be congested. As a result, service messages will be lost byMTP2 and the service will be interrupted.

HandlingSuggestion

1. Add links to the office that is in service for the congested link.

2. Take the following measures to improve transmission qualityof physical links. Replace bottom layer lines. Ensure thatconnector contact and cable connection are normal.



198066009 MTP2 linkreception overload


� Description:MTP2 link reception overload

� Severity:Major


Probable Cause The traffic flow carried by the MTP2 is excessive under the con-dition of current link bandwidth. It exceeds the alarm thresholdof link transmission load. The alarm threshold is related to MITP2link type. For 64K link, the alarm threshold is: bandwidth occupa-tion ratio reaches 0.8. For N*64k or 2M link, the alarm thresholdis: bandwidth occupation ratio reaches 0.6.

Specific Problem The traffic flow carried by the MTP2 is excessive under the con-dition of current link bandwidth. It exceeds the alarm thresholdof link transmission load. The alarm threshold is related to MITP2link type. For 64K link, the alarm threshold is: bandwidth occupa-tion ratio reaches 0.8. For N*64k or 2M link, the alarm thresholdis: bandwidth occupation ratio reaches 0.6.

System Impact This alarm has little impact on the local. If MTP2 link reception isoverloaded for quite a long time, the signalling reception will becongested. This may trigger the signalling flow control of MTP2layer. In most serious case, package loss may occur, which leadsto call loss or decrease of PS access success rate.

HandlingSuggestion

1. Add links to the office that is in service for the congested link.

2. Take the following measures to improve transmission qualityof physical links. Replace bottom layer lines. Ensure thatconnector contact and cable connection are normal.

198066010 MTP3 SignallingPoint Inaccessible


� Description:MTP3 Signalling Point Inaccessible

� Severity:Major


Probable Cause 1. No service link exists in the office route.

2. TFP is received.

Specific Problem 1. No service link exists in the office route.

2. TFP is received.



System Impact UE fails to receive/transmit messages from/to the relevant office.New services can not be accessed to this office, and existing ser-vices are interrupted abnormally.

HandlingSuggestion

1. Check whether there is an unavailable link alarm. If yes, pleasesolve the problem according to corresponding handling sugges-tions. Related alarm: 8400129 MTP3 link unavailable

2. Check whether the configuration of office and link at oppositeend is correct.

198066011 MTP3 linkunavailable


� Description:MTP3 link unavailable

� Severity:Minor


Probable Cause 1. Physical link at bottom layer is broken or link quality is poor.

2. Link test fails.

3. This link is deactivated in dynamic data management.

4. The opposite end has released this link.

5. SMP or SPB/SPB2/APBE/APBE2 board resets

Specific Problem 1. Physical link at bottom layer is broken or link quality is poor.

2. Link test fails.

3. This link is deactivated in dynamic data management.

4. The opposite end has released this link.

5. SMP or SPB/SPB2/APBE/APBE2 board resets

System Impact If several MTP3 links are available for the office, services will notbe affected. In the case of heavy traffic, link congestion may occur,leading to loss of packets/calls and decreased PS call access rate.If merely one link is available to the destination signalling point,the office may become inaccessible. UE fails to receive/transmitmessages from/to the relevant office. New services can not beaccessed to this office, and existing services are interrupted ab-normally.

HandlingSuggestion

1. IN NMS Configuration Management interface, click SignallingLink Configuration to check PVC configuration. Make sure thatthe configuration of CVPI and CVCI should be the same at bothends.

2. In Dynamic Data Management, check link status. If it is in-terrupted and connected now and then, it means the link un-availability is caused by MTP3 link test failure. 1) In NMS Con-figuration Management interface, check the configuration ofsignalling point code at both ends. Ensure that the configura-tion is consistent at both ends. 2) In NMS Configuration Man-



agement interface, check the configuration of signalling link atboth ends. Ensure that the configuration of SLC (SignallingLink Code) is consistent at both ends.

3. Re-activate the link in Dynamic Data Management.

4. Check board status. If it is abnormal, reset or replace theboard.

5. The opposite end has released the relevant link. Ask the op-posite end to deal with the alarm as link unavailable.

198066012 MTP3 clusterinaccessible


� Description:MTP3 cluster inaccessible

� Severity:Major


Probable Cause 1. No service link exists in the cluster route.

2. TCP is received.

Specific Problem 1. No service link exists in the cluster route.

2. TCP is received.

System Impact Reception and sending of messages from/to the relevant clusterfail. Access of new service under this cluster fails, and abnormalrelease of the ongoing service occurs.

HandlingSuggestion

1. Check if there exists unavailable link alarm. If yes, refer tothe corresponding alarm handling suggestion. Related alarms:8400129 MTP3 link unavailable

2. Check if cluster and link configuration at opposite end is cor-rect.

198066014 M3UA SignallingPoint Inaccessible


� Description:M3UA Signalling Point Inaccessible

� Severity:Major


Probable Cause 1. Association link is broken or application server (AS) is not inserving status.



2. M3UA office is inaccessible because the remote office gives aDUNS (destination signalling point unavailable) report.

Specific Problem 1. Association link is broken or application server (AS) is not inserving status.

2. M3UA office is inaccessible because the remote office gives aDUNS (destination signalling point unavailable) report.

System Impact UE fails to receive/transmit messages from/to the relevant office.New services can not be accessed to this office, and existing ser-vices are interrupted abnormally.

HandlingSuggestion

1. Check whether there is an association link broken alarm. Ifyes, please solve the problem according to corresponding han-dling suggestions. Related alarm: 8402690 Association linkbroken

2. In NMS Configuration Management interface, view AS StaticInformation to check whether a routing context exists. If yes,view the relevant configuration such as routing context ID, ASID and AS service mode. The correct configuration is describedbelow. i. The routing context ID and AS service mode mustbe the same at both ends. ii. AS ID must meet the followingrequirements: if ASP is configured for local end, SGP shouldbe configured for opposite end; if IPSP client is configured forlocal end, IPSP server should be configured for opposite end.

3. Re-activate the ASP in Dynamic Data Management.

4. Check whether the configuration of relevant office is correct atopposite end.

198066015 SUA subsystemunavailable


� Description:SUA subsystem unavailable

� Severity:Minor


Probable Cause 1. Remote signaling point is inaccessible.



4. Remote signaling point subsystem is out of service.

Specific Problem 1. Remote signaling point is inaccessible.



4. Remote signaling point subsystem is out of service.



System Impact Signaling data cannot be sent to and received from the relevantsubsystem. Access of new service under the corresponding officefails, and release of the ongoing service occurs.

HandlingSuggestion

1. Check whether there exists office (the office that correspondsto the subsystem) inaccessible alarm. If yes, refer to thecorresponding alarm handling suggestion. Related alarms:8401153 SUA office inaccessible

2. Check whether the signaling point subsystem (for A) is config-ured at A end. If no, add the configuration at A end.

3. Check whether the status of signaling point subsystem (for B)is available at B end. If no, the signaling point subsystem at Bend must be out of service. Locate the cause for the abnormalstatus.

4. Check whether the signaling point subsystem (for B) is config-ured at B end. If no, add the configuration at B end.

198066016 SUA officeinaccessible


� Description:SUA office inaccessible

� Severity:Major


Probable Cause 1. Association link is broken or application server (AS) is not inserving status.

2. DUNA (destination signaling point unavailable) is reported byremote office of the association.

Specific Problem 1. Association link is broken or application server (AS) is not inserving status.

2. DUNA (destination signaling point unavailable) is reported byremote office of the association.

System Impact Reception and sending of messages from/to the relevant office fail.Access of new service under this office fails, and abnormal releaseof the ongoing service occurs.

HandlingSuggestion

1. Check if there exists broken association link alarm. If yes,refer to the corresponding alarm handling suggestion. Relatedalarm: Association link broken

2. Check AS configuration on NMS configuration management in-terface. Main checking items include the existence of routingcontext, routing context ID, APP server AS ID, and traffic mode.Correct configuration is described below. i. The routing con-text ID and traffic mode at both ends must be the same. ii.APP server AS ID configuration must meet the following re-quirements. If ASP is configured for local end, SGP should beconfigured for Opposite end. If IPSP client is configured forlocal end, IPSP server should be configured for opposite end.



3. Reactivate the ASP in dynamic data management.

4. Check whether the configuration of the relevant office is correctat opposite end.

198066019 Association linkbroken


� Description:Association link broken

� Severity:Major


Probable Cause 1. The association is released in dynamic data management.

2. Association configuration is modified at local end.

3. Association is released at opposite end.

4. Bottom layer link is faulty.

Specific Problem 1. The association is released in dynamic data management.

2. Association configuration is modified at local end.

3. Association is released at opposite end.

4. Bottom layer link is faulty.

System Impact If several association links are available to the destination office,service will not be affected. In the case of heavy traffic, conges-tion of available association(s) might occur, leading to upper layercall loss or increasing PS call access failures. If merely one asso-ciation link is available to the destination office, the office mightbecome inaccessible. Reception and sending of messages from/tothe relevant office fail. Access of new services under this officefails, and abnormal release of ongoing services occurs.

HandlingSuggestion

1. Establish the association in dynamic data management.

2. On NMS configuration management interface, check ASP con-figuration at local end and opposite end. Checking items in-clude protocol type of SCTP association, SMP module No, localIP address, local port No., remote IP address, remote port No.,the number of in/out streams. If the configuration at both endsis inconsistent, modify configuration to keep consistency.

3. Ping the opposite board address to see if the network cable orother intermediate link is faulty. Replace the cable if ping fails.

4. Check if the association is released at opposite end. If yes,troubleshoot according to the corresponding cause.



198066020 STC SignallingPoint Inaccessible


� Description:STC Signalling Point Inaccessible

� Severity:Major


Probable Cause No association is in the servicing state.

Specific Problem No association is in the servicing state.

System Impact The corresponding office cannot receive or send messages.

HandlingSuggestion

1. Check whether no association to the adjacent office is avail-able.

Y->Perform further handling according to the alarm reason forassociation broken.

N->Go to Step

2. Note down detailed information. 2.1 Back up related local of-fice configuration data and peer-end office configuration data.2.2 Back up related local office and peer-end office historyalarms and notifications, as well as current alarms. 2.3 Con-tact ZTE Corporation and end the alarm handling procedure.

198066026 Association pathbroken


� Description:Association path broken

� Severity:Major


Probable Cause 1. SCTP link is broken

2. Control plane path in NE is interrupted.


4. The route to remote address is lost.

Specific Problem 1. SCTP link is broken

2. Control plane path in NE is interrupted.


4. The route to remote address is lost.

System Impact If multiple paths are available for the association and there existsnormal path, relevant services will not be affected. If merely one



path is available for the association, all services on the associationis down.

HandlingSuggestion

1. On NMS fault management interface, view alarm Details,where information of association ID, local address, and remoteaddress is given. 1. On NMS configuration managementinterface (static route), query the route information of theremote address. Locate the out port according to the routeinformation. Check if network cable of the out port is discon-nected or loose. If yes, unplug and plug the cable or replacethe cable.

2. On NMS configuration management interface (ASP configura-tion), query the ID of the module where the association islocated. Check if the following alarm occurs in the relevantboard. If yes, refer to the corresponding alarm handling sug-gestion. Related alarm: 8393985 Control plane communica-tion abnormal between board and its home module

3. On NMS configuration management interface (static route),query if the route to the remote address of the association isconfigured. If not, add the configuration.

4. Check the intermediate equipment on association path. If theroutes to local address and remote address of the associationare not configured, add the configuration according to equip-ment operation manual.

5. Check at opposite end if the route to the local address of theassociation is configured. If not, add the configuration.

6. Check if the opposite equipment is faulty. If yes, troubleshootat opposite end.

198066029 PPP link brokenAlarm Property � Alarm Code:198066029

� Description:PPP link broken

� Severity:Major


Probable Cause 1. The alarm occurs in PPP port creating, modifying, deletingwhen PPP port is created by command.

2. The alarm occurs once in PPP port during board power-on, andrecovers after successful PPP negotiation.

3. Physical link is down, or link transmission quality is poor.

4. Adjustment of PPP link parameter leads to link re-negotiation,causing the alarm.

Specific Problem 1. The alarm occurs in PPP port creating, modifying, deletingwhen PPP port is created by command.

2. The alarm occurs once in PPP port during board power-on, andrecovers after successful PPP negotiation.

3. Physical link is down, or link transmission quality is poor.



4. Adjustment of PPP link parameter leads to link re-negotiation,causing the alarm.

System Impact This will cause disconnection of user plane data and services.

HandlingSuggestion

1. Check alarm details on the NMS Alarm Management interfaceto find the faulty PPP port ID. 1. Check the cable connectionsat both ends to see if they are loose or broken. If yes, tightenthe connection or replace the broken cable.

2. Refer to the networking plan to check if the E1 cable is correctlyconnected.

3. Click IPOverE1 Configuration on the NMS Configuration Man-agement interface to check E1 ID and time slot. Make surethat the time slot configuration is consistent at both ends.

4. Check PPP parameters on the NMS Configuration Managementinterface to ensure that the configuration is consistent at bothends.

5. Check the connection relation of DT and EIPI on the NMS Con-figuration Management interface to ensure that the PPP portconfiguration is consistent at both ends.

198066030 BSCIPconfiguration error indatabase


� Description:BSCIP configuration error in database



Probable Cause 1. BSCIP is not configured.

2. Illegal BSCIP configuration, for example, all 0s or 1s.

Specific Problem 1. BSCIP is not configured.

2. Illegal BSCIP configuration, for example, all 0s or 1s.

System Impact ABPM cannot locate other problems with the self-loop method.

HandlingSuggestion

1. Check whether the BSCIP configuration is correct.

Y->Go to "2".

N->Modify the configuration, and go to "2" if this alarm stillexists.

2. Check whether the internal link between OMP and ABPM is nor-mal.

Y->Go to "3".

N->Check alarms for related internal communication, and per-form further handling according to the alarm information, andgo to "3" if this alarm still exists.



3. Check whether the configuration data of the last configurationor modification have been uploaded to the foreground.

Y->Go to "4".

N->Wait a moment and try again, and go to "4" if this alarmstill exists.

4. Note down the current BSCIP configuration and contact ZTE.

198066066 AAL2 Pathlocally blocked


� Description:AAL2 Path locally blocked

� Severity:Minor


Probable Cause The Path is manually blocked from this AAL2 Node.

Specific Problem The Path is manually blocked from this AAL2 Node.

System Impact No AAL2 connection can be established on the blocked path.

HandlingSuggestion

You can unblock the Path which is generated manually from theoperating interface.

198066067 AAL2 Pathremotely blocked


� Description:AAL2 Path remotely blocked

� Severity:Minor


Probable Cause The adjacent AAL2 node initiates blocking process and then thepath of this node is remotely blocked when receiving the blockingmessage from the adjacent node.

Specific Problem The adjacent AAL2 node initiates blocking process and then thepath of this node is remotely blocked when receiving the blockingmessage from the adjacent node.


HandlingSuggestion

You can unblock the Path which is generated by adjacent nodefrom the operating interface of the adjacent node.



198066068 AAL2 Pathblocked by broken PVC


� Description:AAL2 Path blocked by broken PVC

� Severity:Minor


Probable Cause The Path is blocked because of the broken PVC.

Specific Problem The Path is blocked because of the broken PVC.


HandlingSuggestion

The path can be available when PVC becomes available.

198066071 Link broken forboard fault


� Description:Link broken for board fault

� Severity:Minor


Probable Cause Board internal fault.

Specific Problem Board internal fault.

System Impact This alarm may render some offices inaccessible, or may result inthe congestion of other links.

HandlingSuggestion

1. ote down detailed information. 1.1 Back up related local officeconfiguration data and peer-end office configuration data. 1.2Back up related local office and peer-end office history alarmsand notifications, as well as current alarms. 1.3 Contact ZTECorporation and end the alarm handling procedure.

198087336 Rack Abiscontrol link broken


� Description:Rack Abis control link broken





Probable Cause 1. The rack configured on NMS client does not actually exist.

2. In IP site, IP configuration on NMS client is not correct.

3. In E1 site, Abis time slot of slave rack configuration on NMSclient is not correct.

4. Cable connection is abnormal.

Specific Problem 1. The rack configured on NMS client does not actually exist.




System Impact Alarmed rack cannot provide service.

HandlingSuggestion

1. Check BTS configuration in Resource Tree Configuration onNMS configuration management interface if configured slaverack actually exists. If not, delete the virtual one and syn-chronize the data to BSC on NMS.

2. In IP site, on NMS configuration interface, check Configura-tion Resource/IP related configuration/Interface configuration.Among which, IPBB item is configured with the IP address ofthe gateway from BTS to BSC; RPU item is configured with vir-tual IP address of the SCTP link from BTS to BSC. If the con-figuration is not consistent with the NMS at BTS side, correctit and synchronize the data on BSC and BTS.

3. In E1 site, check Abis time slot of slave rack configurationin Configuration Resource tree on NMS configuration manage-ment interface.

4. Check cable connection between BTS and BSC to ensure itworks properly.

198087337 Site Abis controllink broken


� Description:Site Abis control link broken



Probable Cause 1. The rack configured on NMS client does not actually exist.




Specific Problem 1. The rack configured on NMS client does not actually exist.






System Impact The cells under this site cannot provide any voice or data services.

HandlingSuggestion

1. Check BTS configuration in Configuration Resource tree on NMSconfiguration management interface if configured slave rackactually exists. If not, delete the virtual one and synchronizethe data on BSC and NMS.

2. In IP site, on NMS configuration interface, check Configura-tion Resource/IP related configuration/Interface configuration.Among which, IPBB item is configured with the IP address ofthe gateway from BTS to BSC; RPU item is configured with vir-tual IP address of the SCTP link from BTS to BSC. If the con-figuration is not consistent with the NMS at BTS side, correctit and synchronize the data on BSC and BTS.

3. In E1 site, check Abis time slot of slave rack configurationin Configuration Resource tree on NMS configuration manage-ment interface.

4. Check cable connection between BTS and BSC to ensure itworks properly.

198087343 Front PCcommunication link brokenalarm


� Description:Front PC communication link broken alarm

� Severity:Minor


Probable Cause 1. NFS service of Linux system on NMS server is abnormal.

2. The link communication between NMS server and OMP boardis abnormal.

Specific Problem 1. NFS service of Linux system on NMS server is abnormal.

2. The link communication between NMS server and OMP boardis abnormal.

System Impact During the alarm period, performance data cannot be reported toNMS.

HandlingSuggestion

1. Log in OMP board through telnet and input "NfsShowState"command. If NFS device is abnormal, the command resultshows corresponding indications in English. And then, checkNFS service of Linux system on NMS server, if it is abnormal,NFS service need to be restarted immediately, for example,use Linux command "service nfs restart".



2. Check the network cables between SBCX and OMP and ensurethe connections are correct.

198087352 NSVC failurealarm


� Description:NSVC failure alarm

� Severity:Minor


Probable Cause The physical link between BSC and SGSN is broken.

Specific Problem The physical link between BSC and SGSN is broken.

System Impact For signal NSVC link configuration, the PS service is interrupted.For multi-NSVC link configuration, the bandwidth is decreased.

HandlingSuggestion

1. On NMS fault management interface, check if alarm which is re-lated to FR device malfunction exists. If so, follow the instruc-tions of handling related alarms. Related alarm: 198087340FR device Failure

2. On NMS dynamic data management interface, check if NSVCconfiguration parameters are consistent with those on SGSN.

3. Check if the E1 and the network cables between BSC and SGSNare intact and inserted correctly.

198087775 super siteexchanged to the satelliticABIS link


� Description:super site exchanged to the satellitic ABIS link

� Severity:Major


Probable Cause the subaerial ABIS link is broken, site exchanged to satellitic ABISlink

Specific Problem the subaerial ABIS link is broken, site exchanged to satellitic ABISlink

System Impact None



HandlingSuggestion

restore the subaerial ABIS link

198088026 IPOE uplink anddownlink congestion alarm


� Description:IPOE uplink and downlink congestion alarm



Probable Cause IPOE site detects uplink and downlink congestion.

Specific Problem IPOE site detects uplink and downlink congestion.

System Impact Service quality degrades or even interrupts.

HandlingSuggestion



C h a p t e r 4

Handling Alarm

Table of Contents198005120 T Network Connection Not Conform to Configura-tion ............................................................................... 286198005123 Incorrect configuration for inserted board or de-vice ............................................................................... 286198005387 Alarm due to inconsistent MP type..................... 287198005388 Startup file does not exist ................................ 287198005398 Office ID is not set correctly with controlshelf .............................................................................. 288198005402 Database config is different from file namedbootcfg.ini ...................................................................... 288198005649 Port configuration is incorrect ........................... 289198005659 Formats of audio resource inconsistent .............. 290198005889 Version Switches While Board Doesn't Re-set ................................................................................ 290198005890 Function EPLD Update Failure ........................... 291198005891 Inconsistent BOOT/EPLD Version No. with Data-base Configurations ......................................................... 291198005892 Boot Version Fails to Write to Backup Region ......... 292198007936 Memory file buffer overflow.............................. 292198015360 Microcode Is Abnormal .................................... 293198018944 PVC link is down ............................................. 293198019207 Near-End IMA Group Configuration Failure.......... 294198020225 Protocol stack requested system configuration in-formation timeout............................................................ 295198023040 Number of alarms exceeds threshold. ................ 296198025600 Connection Check be Disabled in board.............. 296198066006 Broadband link congestion .............................. 297198066013 MTP3 link congestion....................................... 298198066018 Association congestion .................................... 298198066021 STC office congestion ...................................... 299198066027 SNTP failure ................................................... 299198066031 OMP alarm pool is full, unable to store any morealarms. .......................................................................... 300198066032 Loss of NTP time synchronisation ...................... 300198066063 MTP3 link sending flow control alarm................. 301198087251 FUC L3 software no response temporarily........... 301198087380 TRX manual block alarm .................................. 302198087482 Data loading exception alarm ........................... 302198087513 Board Ethernet port overload alarm................... 303198087768 Resource Availability Alarm of UPPB DSP............ 303



198005120 T NetworkConnection Not Conform toConfiguration


� Description:T Network Connection Not Conform to Configura-tion


� Alarm Type:Handling Alarm

Probable Cause T network fiber connection does not conform to optical interfaceconnection relation configured on the background.

Specific Problem T network fiber connection does not conform to optical interfaceconnection relation configured on the background.

System Impact T Net switch of the shelf is in disorder.

HandlingSuggestion

Modify the fiber connection or the connection configuration to keepthe configuration consistent with the physical connection.

198005123 Incorrectconfiguration for insertedboard or device


� Description:Incorrect configuration for inserted board or device

� Severity:Minor


Probable Cause 1. Incorrect board in slot

2. Board hardware does not match the OMC-R configuration.

Specific Problem 1. Incorrect board in slot

2. Board hardware does not match the OMC-R configuration.

System Impact The board fails to be normally powered on. The services carriedby the board are interrupted.

HandlingSuggestion

1. The NMS configuration management interface gives the rackdiagram. Select the board and check if the Basic Informationand CPU Information of the rack are correct. If the settingsare incorrect, delete the board and create a new one.

2. Check if a correct board is inserted in the slot on the rack. Ifnot, insert the correct one.


Chapter 4 Handling Alarm

198005387 Alarm due toinconsistent MP type


� Description:Alarm due to inconsistent MP type

� Severity:Major


Probable Cause 1. The MP type is changed on NMS and the board is not restarted.

2. The active MP type on the local board is not consistent withthat configured on NMS.

Specific Problem 1. The MP type is changed on NMS and the board is not restarted.

2. The active MP type on the local board is not consistent withthat configured on NMS.

System Impact There is no impact on services

HandlingSuggestion

1. For CMP and SMP, reset the board.

2. For OMP, set the start mode as "foreground start" on NMSand then reset the board. Do as follows: On NMS softwareversion management interface, select the menu for queryingforeground (that is, RNC NE) board start mode. In the pop-updialog box, set the start mode to "foreground start".

198005388 Startup file doesnot exist


� Description:Startup file does not exist

� Severity:Major


Probable Cause The startup configuration file is deleted.

Specific Problem The startup configuration file is deleted.

System Impact This alarm may cause OMP work abnormally, and the entire net-work element services are affected.

HandlingSuggestion

1. Reset the active and standby OMPs.




198005398 Office ID is notset correctly with controlshelf


� Description:Office ID is not set correctly with control shelf

� Severity:Major


Probable Cause The office ID of a shelf where DIP switch locates is different fromthat of a shelf where OMP locates.

Specific Problem The office ID of a shelf where DIP switch locates is different fromthat of a shelf where OMP locates.

System Impact The MAC address conflicts. The MAC and IP address verificationfails. All boards on the shelf can not be powered on. All servicescarried by the shelf are interrupted.

HandlingSuggestion

Set the office ID of the shelf where DIP switch locates to be thesame as that of OMP belonged shelf.

198005402 Database configis different from file namedbootcfg.ini


� Description:Database config is different from file namedbootcfg.ini

� Severity:Major


Probable Cause After the start information of OMP is modified, the active andstandby OMP boards are not restarted.

Specific Problem After the start information of OMP is modified, the active andstandby OMP boards are not restarted.

System Impact System startup is abnormal, MP may not work normally.



HandlingSuggestion

Restart the active and the standby OMP boards at the same time.

198005649 Portconfiguration is incorrect


� Description:Port configuration is incorrect

� Severity:Major


Probable Cause 1. Port Configuration is incorrect.

2. Incorrect configuration for this board.

Specific Problem 1. Port Configuration is incorrect.

2. Incorrect configuration for this board.

System Impact 1. The port fails to work in the preset mode. This causes the portto be unavailable and all services of the port are interrupted.

2. For Auto mode, the bandwidth of the external port becomesinsufficient. As a result, some services of the port are inter-rupted.

HandlingSuggestion

On NMS fault management interface, view the alarm details, whichgive the reason of mode error. You can quickly locate the handlingmethod according to the reason of mode error. The handling sug-gestion for each reason of mode error is as follows: Speed modeerror i. Determine the speed to be configured. Replace the ex-isting board with the one supporting the configured speed mode.ii. For Force mode, configure the port with the speed supportedby the bottom layer in actual working status. Do as follows: OnNMS configuration management interface, in Basic Information tabof board property, set the speed in outer port information to thespeed supported by the bottom layer in actual working status. iii.For Auto mode, re-configure the expected speed and ensure thatit is consistent with the actual port speed. Do as follows: On NMSconfiguration management interface, in Basic Information tab ofboard property, set the speed in outer port information to the ex-pected one. Duplex mode error i. Determine the required mode.Replace the existing board with the one supporting the mode con-figured on BSC. ii. For Force mode, configure the port with theduplex mode supported by the bottom layer in actual working sta-tus. Do as follows: On NMS configuration management interface,in Basic Information tab of board property, set the work mode inouter port information to the work mode supported by the bottomlayer in actual working status. iii. For Auto mode, re-configure theexpected duplex and ensure that it is consistent with the actualport duplex. Do as follows: On NMS configuration managementinterface, in Basic Information tab of board property, set the workmode in outer port information to the expected one.



198005659 Formats of audioresource inconsistent


� Description:Formats of audio resource inconsistent

� Severity:Major


Probable Cause Different formats of tones can't coexist in the board.

Specific Problem Different formats of tones can't coexist in the board.

System Impact The current service cannot be used by DSP.

HandlingSuggestion

By using the formatting button of OMC background tools, set theaudio format to the same audio format.

198005889 VersionSwitches While BoardDoesn't Reset


� Description:Version Switches While Board Doesn't Reset



Probable Cause 1. Appoint the version for OMP and select the option of restartafter switch,but the version file have existed on OMP's DOC0.

2. Swtich the BOOT version.

Specific Problem 1. Appoint the version for OMP and select the option of restartafter switch,but the version file have existed on OMP's DOC0.

2. Swtich the BOOT version.

System Impact The board version will not take effect if the board does not reset.



HandlingSuggestion

Restart the board manually.

198005890 Function EPLDUpdate Failure


� Description:Function EPLD Update Failure



Probable Cause Function EPLD update failure,or the version file of Function EPLDis bigger than 64K

Specific Problem Function EPLD update failure,or the version file of Function EPLDis bigger than 64K

System Impact If the board is reset before the alarm is eliminated, the board mayfail to boot.

HandlingSuggestion

1. Use the version management tool to switch to a correct func-tional EPLD version.


198005891 InconsistentBOOT/EPLD VersionNo. with DatabaseConfigurations


� Description:Inconsistent BOOT/EPLD Version No. with Data-base Configurations



Probable Cause Inconsistent BOOT/EPLD version No. with database configura-tions.

Specific Problem Inconsistent BOOT/EPLD version No. with database configura-tions.

System Impact If the running EPLD version does not match database, the boardmay not function properly; if the running BOOT version does notmatched database, the slave CPU of the multi-CPU board may failto boot.



HandlingSuggestion

Switch BOOT/EPLD again and restart the board manually.

198005892 Boot VersionFails to Write to BackupRegion


� Description:Boot Version Fails to Write to Backup Region



Probable Cause Boot version fails to be written to backup region.

Specific Problem Boot version fails to be written to backup region.

System Impact BOOT backup version is unavailable.

HandlingSuggestion

Switch BOOT again and restart the board manually.

198007936 Memory filebuffer overflow


� Description:Memory file buffer overflow

� Severity:Major


Probable Cause The transferred data records exceed the maximum capacity of thetable, and the capacity of the receiver memory file buffer is insuf-ficient.

Specific Problem The transferred data records exceed the maximum capacity of thetable, and the capacity of the receiver memory file buffer is insuf-ficient.

System Impact If the board is powering on, the excessive data records (beyondtable capacity) are discarded, otherwise the synchronization willbe aborted.

HandlingSuggestion

1. Lookup if the capacity of the table is correct, please makerecords of the alarm information and contact ZTE Corporation.

2. Synchronize the capacity tables, then synchronize all tables tothe foreground and reboot the board. If the alarm still has notrestored, please make records of the alarm information andcontact ZTE Corporation.



198015360 Microcode IsAbnormal


� Description:Microcode Is Abnormal

� Severity:Major


Probable Cause Network Processor hardware is faulty.

Specific Problem Network Processor hardware is faulty.

System Impact The board will reboot. If the alarm can be restored after boardrebooting, all board services during rebooting will be down, butaccess of new services to the board after rebooting will be suc-cessful. If the alarm cannot be restored after board rebooting, allboard services during and after rebooting will be down.

HandlingSuggestion

Wait for the board to reboot. If the alarm cannot be restored afterboard rebooting, unplug and then plug the board. If the alarm stillcannot be restored, replace the board.

198018944 PVC link is downAlarm Property � Alarm Code:198018944

� Description:PVC link is down

� Severity:Minor


Probable Cause 1. PVC connection for the equipment is loose or disconnected.PVC connection falls into the following three types. Fibber con-nection, carried by optical interface. E1/T1 connection, carriedby IMA port. Fibber connection, carried by IMA port.

2. Continuity Check (CC) test is started at local end, but notstarted at opposite end.

Specific Problem 1. PVC connection for the equipment is loose or disconnected.PVC connection falls into the following three types. Fibber con-nection, carried by optical interface. E1/T1 connection, carriedby IMA port. Fibber connection, carried by IMA port.

2. Continuity Check (CC) test is started at local end, but notstarted at opposite end.

System Impact PVC is in faulty status. All services on the PVC are interrupted.

HandlingSuggestion

1. Check alarm details on the NMS fault management interfaceto find the PVC ID and locate the faulty port. For example, thePVC ID is 1. Select PVC Configuration on the NMS ConfigurationManagement interface to find a record with a PVC ID of 1.Check the record for the Subsystem NO, Unit NO, and ATMPort No. By using the information, you can find the location ofthe corresponding interface board and port.



2. Check the relevant equipment according to the physical bearertype of the port. 1) If the faulty PVC port is carried by an opticalinterface, check the optical port and make sure that the fibberis well connected. Replace the fibber if necessary. 2) If thefaulty PVC port is carried by an IMA port, check whether thecorresponding IMA group/link has one of the following alarms.If yes, handle it according to the corresponding suggestions.a. 19207 Near-end IMA group configuration failure b. 19213LIF alarm of near-end receiving link c. 19214 LODS alarm ofnear-end receiving link d. 19215 RDI alarm of far end receivingLink

3. Check if the peer-end equipment is powered on successfully. Ifnot, refer to the corresponding equipment maintenance man-ual to solve the problem.

4. Check whether the peer-end equipment has normal PVC status.If not, please refer to corresponding equipment maintenancemanual to solve the problem.

5. Deactivate the CC test at the local end, or activate the CCtest at the peer end. For IMAB/APBE board: To deactivatethe CC test at the local end, start the test on the NMS TestManagement interface, and then select "0: Deactivate CC" foractivation type and "1: B-A" for test type (A stands for localend and B stands for peer end). To activate the CC test at thepeer end, start the test on the NMS Test Management interface,and then select "1: Activate CC" for activation type and "1:B-A" for test type. For APBE2/DTA board: Modify PVC CCINFOparameter of configuration to active or deactivate CC test. CCtest parameter is same to APBE/IMAB.

198019207 Near-End IMAGroup Configuration Failure


� Description:Near-End IMA Group Configuration Failure

� Severity:Major


Probable Cause IMA group configuration at local end and at opposite end is incon-sistent.

Specific Problem IMA group configuration at local end and at opposite end is incon-sistent.

System Impact All services on the IMA port are interrupted.

HandlingSuggestion

On NMS fault management interface , view alarm Details where in-formation of the faulty IMA group is given. On NMS configurationmanagement interface (IMA group configuration), locate the cor-responding IMA group according to the information given in alarmDetails. Compare the configuration of the following parametersat both ends. If the configuration at both ends is inconsistent,modify configuration at either end to keep consistency. "Near-End



OMA Label" "Rx Frame Length (cells)" "Tx Frame Length (cells)""Near-End Symmetry"

198020225 Protocolstack requested systemconfiguration informationtimeout


� Description:Protocol stack requested system configuration in-formation timeout

� Severity:Major


Probable Cause 1. The EPU or RPU requests configuration from the database, butthe database makes no response.

2. Or the database has made a response but the content is incor-rect.

3. The message that the EPU or RPU sends to the database is lost.

4. The control-plane communication is broken.

Specific Problem 1. The EPU or RPU requests configuration from the database, butthe database makes no response.

2. Or the database has made a response but the content is incor-rect.

3. The message that the EPU or RPU sends to the database is lost.

4. The control-plane communication is broken.

System Impact The protocol process could not enter working state.

HandlingSuggestion

1. RPU is rebooting when EPU registers to RPU.

Y->No need to handle.

N->Go to "2".

2. Check whether the home module MP and the local board sys-tem control are normal and whether their communication isnormal.

Y->Go to "5".

N->Go to "3".

3. Unplug and plug the board. Reset the hardware. Checkwhether the alarm disappears.

Y->End.

N->Maybe the board hardware is abnormal, go to "4".



4. Replace with a new board and check whether the alarm disap-pears.

Y->End.

N->Go to "5".

5. Contact ZTE Corporation.

198023040 Number ofalarms exceeds threshold.


� Description:Number of alarms exceeds threshold.

� Severity:Major


Probable Cause This board has too many alarms so that the relevant alarm pool isfull.

Specific Problem This board has too many alarms so that the relevant alarm pool isfull.

System Impact Alarms may be lost, but there is no impact on user services.

HandlingSuggestion

Check and remove the current alarms in the system.

198025600 ConnectionCheck be Disabled in board


� Description:Connection Check be Disabled in board



Probable Cause The connection check switch is off, causing PP service process un-able to execute connection check.

Specific Problem The connection check switch is off, causing PP service process un-able to execute connection check.

System Impact Board connection check disabled, automatic check of connectionerror cannot be performed. Thus the connection error might notbe self-cured.



HandlingSuggestion

Please contact ZTE Corporation.

198066006 Broadband linkcongestion


� Description:Broadband link congestion

� Severity:Minor


Probable Cause 1. The configured signaling PVC bandwidth is low.

2. The quality of physical transmission at bottom layer is poor.

Specific Problem 1. The configured signaling PVC bandwidth is low.

2. The quality of physical transmission at bottom layer is poor.

System Impact Link congestion leads to transmission delay. If congestion is notserious, service will not be affected. Otherwise, packet loss or callloss might occur, and access success rate of PS service might fall.

HandlingSuggestion

1. Check the value of "Peak traffic of Signaling Link" in MTP3Bsignaling performance statistic information. If the load nearlyreaches 6000 when the congestion alarm occurs, upper layertraffic must be heavy. In this case, you need to increase PVCbandwidth or add links to share load.

2. Check alarms/notifications in NMS to see whether there is aphysical transmission alarm/notification that occurs simulta-neously with this alarm. If yes, please solve the problem ac-cording to corresponding handling suggestions. The relevantphysical transmission alarms/notifications are listed below byaccess mode. 1) Fiber Access Mode 1792 SDH/SONET fault1824 Abnormal status in SDH/SONET 1825 SDH/SONET: Ex-cessive Error Code 5639 High Error Rate of Optical Interface2)E1 Access Mode 5647 High Error Rate at E1 Bottom Layer519 Trunk error 520 Trunk abnormal 576 Trunk Slide

3. View the statistic performance data of SSCOP link. Checkwhether "Number of PDU Retransmitted" is retransmittedwhen the congestion alarm occurs. If yes, packets must belost during transmission. Since packet loss may occur atopposite end, please try to solve the problem at opposite end.



198066013 MTP3 linkcongestion


� Description:MTP3 link congestion

� Severity:Major


Probable Cause 1. There are too many messages at upper layer.

2. The quality of bottom layer link is so poor that many messagesare retransmitted.

Specific Problem 1. There are too many messages at upper layer.

2. The quality of bottom layer link is so poor that many messagesare retransmitted.

System Impact Link congestion will cause transmission delay. If congestion is notserious, services will not be affected. However, if it is serious,packet loss or call loss may occur, and access success rate of PSservices may fall.

HandlingSuggestion

1. Add links to the office, which provides support for the con-gested link.

2. Take the following measures to improve transmission quality ofphysical links. Replace physical links. Ensure that connectorsare in well contact and cables are correctly connected.

198066018 Associationcongestion


� Description:Association congestion

� Severity:Minor


Probable Cause 1. Transmission quality of bottom layer link is poor.

2. Upper layer traffic in sending service data is heavy.

Specific Problem 1. Transmission quality of bottom layer link is poor.

2. Upper layer traffic in sending service data is heavy.

System Impact Link congestion will cause transmission delay. If congestion is notserious, services will not be affected. However, if it is serious,packet loss or call loss may occur, and access success rate of PSservices may fall.

HandlingSuggestion

1. Check network cable connection. Ensure that the network ca-ble is tightly inserted.



2. Add association links to the office that is in service for the con-gested association.

3. If intermediate equipment exists between local end and oppo-site end, check the transmission quality of intermediate equip-ment.

198066021 STC officecongestion


� Description:STC office congestion

� Severity:Minor


Probable Cause At least one association connected to the office is congested.

Specific Problem At least one association connected to the office is congested.

System Impact Association congestion leads to transmission delay. If congestionis not serious, service is not affected.

HandlingSuggestion

Association congestion exists in this office,refer to the correspond-ing alarm handling suggestion. Related alarm: 8402688 Associa-tion congestion.

198066027 SNTP failureAlarm Property � Alarm Code:198066027

� Description:SNTP failure

� Severity:Minor


Probable Cause 1. SNTP server does not exist or it works abnormally.

2. The configured SNTP IP address in database is different fromits real IP address.

3. The communication between RNC and SNTP server is broken.

4. The time synchronization period configured in the databasemight be 0.

Specific Problem 1. SNTP server does not exist or it works abnormally.

2. The configured SNTP IP address in database is different fromits real IP address.

3. The communication between RNC and SNTP server is broken.

4. The time synchronization period configured in the databasemight be 0.



System Impact SNTP synchronization failure may cause time difference betweensystem time and real time. For example, the real time is 1:00 am,but the system time is 2:00 am. Since the system clock frequencyis correct, services will not be affected.

HandlingSuggestion

1. Alarm details are displayed in NMS Alarm Management inter-face, where fault type is given. You can easily find handlingsuggestions according to the fault type. The handling sug-gestions for each type are described as below. 1. Invaliddatabase configuration. In NMS Configuration Managementinterface, click RNC Ground Resource Management to checkwhether the IP address of SNTP server is invalid, or SNTP syn-chronization period is wrong. If the IP address of SNTP serveris 255.255.255.255 or SNTP synchronization period is 0, pleasecorrect the configuration.

2. Failure in getting time from SNTP server 1) Ensure that SNTPserver exists and it works normally. 2) Ensure that the config-ured IP address of SNTP server in database is the same as itsreal IP address.

198066031 OMP alarm poolis full, unable to store anymore alarms.


� Description:OMP alarm pool is full, unable to store any morealarms.

� Severity:Major


Probable Cause There are too many system alarms. The alarm pool is full of sys-tem alarms.

Specific Problem There are too many system alarms. The alarm pool is full of sys-tem alarms.

System Impact Alarms may be lost, but there is no impact on user services.

HandlingSuggestion

Delete the trivial alarms on NMS fault management interface.

198066032 Loss of NTPtime synchronisation


� Description:Loss of NTP time synchronisation

� Severity:Minor




Probable Cause 1. Link between OMP and RPU is down.

2. NTP time and local time differs greatly.

Specific Problem 1. Link between OMP and RPU is down.

2. NTP time and local time differs greatly.

System Impact NTP time synchronization terminates, leading to interruption ofongoing services.

HandlingSuggestion

On NMS fault management interface, check if the alarm related toRPU board exists. If yes, refer to the corresponding alarm han-dling suggestion. Related alarm: 8393988 Control plane commu-nication abnormal between MP and OMP

198066063 MTP3 linksending flow control alarm


� Description:MTP3 link sending flow control alarm

� Severity:Major


Probable Cause The sending payload of MTP3 link exceeds the threshold set bysending flow control.

Specific Problem The sending payload of MTP3 link exceeds the threshold set bysending flow control.

System Impact WCS network element, for call setup request message, the linkload exceeds a certain percentage threshold will be rejected inorder to achieve out of the link load does not exceed the purposeof setting threshold; non-WCS network element, does not affect.

HandlingSuggestion

1. Reduce traffic or add links.

2. Increase flow control threshold.

198087251 FUC L3 softwareno response temporarily


� Description:FUC L3 software no response temporarily



Probable Cause MO software (has/has no) response temporarily (set by CMB)



Specific Problem MO software (has/has no) response temporarily (set by CMB)

System Impact FUC operation status cannot be detected from background, butcallings are not affected.

HandlingSuggestion



3. If the alarm doesn't restore, reset CMB when service is idle.

4. If it is software problem, upgrade the version then.

5. If the alarm still exists, replace corresponding DTRU.

198087380 TRX manualblock alarm


� Description:TRX manual block alarm

� Severity:Minor


Probable Cause The TRX indicated in the alarm is manually blocked.

Specific Problem The TRX indicated in the alarm is manually blocked.

System Impact The TRX is out of service.

HandlingSuggestion

On NMS Dynamic Data Management interface, check TRX state inTRX Management tab, and manually unblock the blocked TRX.

198087482 Data loadingexception alarm


� Description:Data loading exception alarm

� Severity:Major


Probable Cause Data exception is detected when database is loading or data is syn-chronizing. Please refer to R_DATAERRLOG table of alarm relatedmodule, and modify or delete abnormal data. Notice the followinginformation in the table: NAME: the error table KEYINDEXINFO:the main index of the error data storage information DATAERRSTR:error info string



Specific Problem Data exception is detected when database is loading or data is syn-chronizing. Please refer to R_DATAERRLOG table of alarm relatedmodule, and modify or delete abnormal data. Notice the followinginformation in the table: NAME: the error table KEYINDEXINFO:the main index of the error data storage information DATAERRSTR:error info string

System Impact Database is abnormal, service has exception, etc.

HandlingSuggestion

1. Refer to R_DATERRLOG table to modify the error data, andafter that, please synchronize all data to confirm the error iseliminated.

2. Before master to slave exchange, if this alarm exists in the oldmaster board.Please synchronize all data to confirm whetherthe exception exists in the new master board after the ex-change.

198087513 Board Ethernetport overload alarm


� Description:Board Ethernet port overload alarm

� Severity:Major


Probable Cause Ethernet port resource allocation is unbalanced and overloaded.

Specific Problem Ethernet port resource allocation is unbalanced and overloaded.

System Impact Impact service quality

HandlingSuggestion

Redistribute resources and balance them.

198087768 ResourceAvailability Alarm of UPPBDSP


� Description:Resource Availability Alarm of UPPB DSP

� Severity:Major


Probable Cause 1. Failure ratio for allocating memory exceeds setting threshold.

2. Use ratio of mac instance exceeds setting threshold.

3. Use ratio of bssgp instance exceeds setting threshold.



4. Use ratio of mac-tlli index exceeds setting threshold.

5. Use ratio of bssgp-tlli index exceeds setting threshold.

6. Use ratio of radio channel instance exceeds setting threshold.

7. Use ratio of TS instance exceeds setting threshold.

Specific Problem 1. Failure ratio for allocating memory exceeds setting threshold.

2. Use ratio of mac instance exceeds setting threshold.

3. Use ratio of bssgp instance exceeds setting threshold.

4. Use ratio of mac-tlli index exceeds setting threshold.

5. Use ratio of bssgp-tlli index exceeds setting threshold.

6. Use ratio of radio channel instance exceeds setting threshold.

7. Use ratio of TS instance exceeds setting threshold.

System Impact Congestion or exception may occur in the DSP, new PS service ofthe DSP is affected.

HandlingSuggestion

1. Checking whether alram thresholds of all resources are lower,if alarm threshold of failure ratio for allocating memory is lessthan five percent or alarm threshold of other resources is lessthan seventy percent, increasing alarm thresold and keepingon observation.

2. If failure ratio of allocating memory exceeds alarm threshold,checking RLC throughput and TBF establishing success rateof correlative cells which are handled by this DSP. While RLCthroughput is changeless or decreasing, and TBF establishingsuccess rate drops largeish percent, consider resetting the DSP.Keeping on observation in other situations.

3. If use ratio of mac instance exceeds alarm threshold, or useratio of bssgp instance exceeds alram threshold, or use ra-tio of mac-tlli index exceeds alram threshold, or use ratio ofbssgp-tlli index exceeds alarm threshold, or use ratio of radiochannel instance exceeds alarm threshold, or use ratio of TSinstance exceeds alarm threshold, checking RLC throughputand TBF establishing success rate of correlative cells which arehandled by this DSP. While RLC throughput is changeless ordecreasing, and TBF establishing success rate drops largeishpercent, consider resetting the DSP. In other situations, con-sider moving some cells of this DSP to other idle DSP.


C h a p t e r 5

Environment Alarm

Table of Contents198025856 Rack temperature is high ................................. 305198025857 Low temperature in Rack ................................ 306198025858 Room temperature is higher than high threshold.................................................................................... 307198025859 Room temperature is lower than low threshold.................................................................................... 307198025860 Rack voltage is high ....................................... 308198025861 rack voltage is low .......................................... 309198025862 Humidity is high ............................................. 309198025863 Humidity is low............................................... 310198025864 Fault in fan plug-in box ................................... 310198025865 Rack door alarm ............................................. 311198025866 Smoke detected ............................................. 311198025867 Infrared alarm................................................ 312198025868 Lightning alarm .............................................. 313198025869 Loss of DC power supply to rack ....................... 313198029184 SNTP server is unavailable ............................... 314

198025856 Racktemperature is high


� Description:Rack temperature is high

� Severity:Minor

� Alarm Type:Environment Alarm

Probable Cause 1. Fan is not working.

2. Fan has failed.

3. No fan connected.

4. Temperature sensor is faulty or setting is incorrect.

Specific Problem 1. Fan is not working.

2. Fan has failed.

3. No fan connected.

4. Temperature sensor is faulty or setting is incorrect.



System Impact 1. If an unreasonable threshold is configured, services will not beaffected.

2. If the alarm is caused by high rack temperature, board maywork abnormally and board services may be interrupted.

HandlingSuggestion

1. In NMS Configuration Management interface, click Power BoardAlarm Parameters to view the upper threshold of rack temper-ature. If the configuration is unreasonable, please modify it.The recommended value of upper threshold is 70 degrees inCelsius.

2. Check the thermometer in equipment room to see if the actualtemperature is too high. If yes, take necessary cooling mea-sures.

3. Remove dust from air intake and outlet of the rack. Removeany obstacle nearby which may affect ventilation.

4. Ensure that the rack fan works normally.

198025857 Low temperaturein Rack


� Description:Low temperature in Rack

� Severity:Minor


Probable Cause 1. Threshold is incorrect.

2. Temperature sensor is not working

3. External room heating control not working.

Specific Problem 1. Threshold is incorrect.

2. Temperature sensor is not working

3. External room heating control not working.


2. If the alarm is caused by low rack temperature, board maywork abnormally and board services may be interrupted.

HandlingSuggestion

1. In NMS Configuration Management interface, click Power BoardAlarm Parameters to view the lower threshold of rack temper-ature. If the configuration is unreasonable, please modify it.The recommended value of lower threshold is 0 degrees Cel-sius.

2. Check the thermometer in equipment room to see if the actualtemperature is too low. If yes, take necessary warming mea-sures.

3. Setting the sensor correctly.


Chapter 5 Environment Alarm

198025858 Roomtemperature is higher thanhigh threshold


� Description:Room temperature is higher than high threshold

� Severity:Minor


Probable Cause 1. Threshold configuration is unreasonable.

2. Actual temperature in equipment room is too high.

Specific Problem 1. Threshold configuration is unreasonable.

2. Actual temperature in equipment room is too high.


2. If the alarm is caused by high room temperature, board maywork abnormally and board services may be interrupted.

HandlingSuggestion

1. On NMS configuration management interface (power boardalarm parameters), check the upper limit of equipment roomtemperature. Modify the threshold value if the previous con-figuration is unreasonable. The recommended high thresholdvalue is 40.

2. Check the thermometer in equipment room to see if the actualtemperature is too high. If yes, take necessary cooling andventilation measures.

198025859 Roomtemperature is lower thanlow threshold


� Description:Room temperature is lower than low threshold

� Severity:Minor


Probable Cause 1. The configured threshold is unreasonable.

2. Actual temperature in equipment room is too low.

3. Setting of the sensor is incorrect.

Specific Problem 1. The configured threshold is unreasonable.



2. Actual temperature in equipment room is too low.



2. If the alarm is caused by low room temperature, board maywork abnormally and board services may be interrupted.

HandlingSuggestion

1. In NMS Configuration Management interface, click Power BoardAlarm Parameters to view the lower threshold of room temper-ature. If the configuration is unreasonable, please modify it.The recommended value of lower threshold is 0 degrees Cel-sius.

2. Check the thermometer in equipment room to see if the actualtemperature is too low. If yes, take necessary warming mea-sures.


198025860 Rack voltage ishigh


� Description:Rack voltage is high

� Severity:Minor



2. Actual voltage is too high.


2. Actual voltage is too high.


2. If the alarm is caused by high voltage, board may work abnor-mally and board services may be interrupted.

HandlingSuggestion

1. In NMS Configuration Management interface, click Power BoardAlarm Parameters to view the upper threshold of rack voltage.If the configuration is unreasonable, please modify it. For 48Vpower supply, the recommended value of upper threshold is57V; for 60V power supply, the recommended value is 7

2. Find out which line voltage exceeds upper threshold by usingthe voltage index given in alarm details. Lower down the inputvoltage of this line.



198025861 rack voltage islow


� Description:rack voltage is low

� Severity:Minor


Probable Cause 1. Voltage value is under the low threshold.

2. The setting of the votage detector is error.

3. Power input of a road may have been disconnected.

Specific Problem 1. Voltage value is under the low threshold.

2. The setting of the votage detector is error.

3. Power input of a road may have been disconnected.


2. If the alarm is caused by low voltage, board may work abnor-mally and board services may be interrupted.

HandlingSuggestion

1. In NMS Configuration Management interface, click Power BoardAlarm Parameters to view the lower threshold of rack voltage.If the configuration is unreasonable, please modify it. For 48Vpower supply, the recommended value of lower threshold is40V; for 60V power supply, the recommended value is 50.

2. Find out which line voltage is below lower threshold by usingthe voltage index given in alarm details. Increase the inputvoltage of this line.

198025862 Humidity is highAlarm Property � Alarm Code:198025862

� Description:Humidity is high

� Severity:Minor



2. Actual humidity in equipment room is too high.


2. Actual humidity in equipment room is too high.


2. If the alarm is caused by high room humidity, board may workabnormally and board services may be interrupted.



HandlingSuggestion

1. In NMS Configuration Management interface, click Power BoardAlarm Parameters to view the upper threshold of room humid-ity. If the configuration is unreasonable, please modify it. Therecommended value of upper threshold is 90.

2. Check the hygrometer in equipment room to see if the actualhumidity is too high. If yes, take necessary dehumidifyingmeasures.

198025863 Humidity is lowAlarm Property � Alarm Code:198025863

� Description:Humidity is low

� Severity:Minor



2. Actual humidity in equipment room is too low.



2. Actual humidity in equipment room is too low.



2. If the alarm is caused by low room humidity, board may workabnormally and board services may be interrupted.

HandlingSuggestion

1. In NMS Configuration Management interface, click Power BoardAlarm Parameters to view the lower threshold of room humid-ity. If the configuration is unreasonable, please modify it. Therecommended value of upper threshold is 90.

2. Check the hygrometer in equipment room to see if the actualhumidity is too low. If yes, take necessary humidifying mea-sures.


198025864 Fault in fanplug-in box


� Description:Fault in fan plug-in box

� Severity:Minor




Probable Cause 1. The fan subrack is not tightly inserted into the rack.

2. The fan subrack has a hardware fault.


Specific Problem 1. The fan subrack is not tightly inserted into the rack.

2. The fan subrack has a hardware fault.


System Impact This alarm may cause very high rack temperature. As a result, therelevant board may work abnormally and board services may beinterrupted.

HandlingSuggestion

1. Check whether the FAN subrack is tightly inserted into the rack.If no, unplug and plug it.

2. Replace the fan subrack.


198025865 Rack door alarmAlarm Property � Alarm Code:198025865

� Description:Rack door alarm

� Severity:Minor


Probable Cause 1. The rack door is not closed.

2. The connection for door access control device is incorrect.


Specific Problem 1. The rack door is not closed.

2. The connection for door access control device is incorrect.


System Impact Services won't be affected, but there is a potential safety problem.

HandlingSuggestion

1. Open and close the rack door so that it is tightly closed.

2. Open the rack door to check the door access control device.Ensure that it is correctly installed and connected. After that,close the rack door.


198025866 Smoke detectedAlarm Property � Alarm Code:198025866

� Description:Smoke detected

� Severity:Minor




Probable Cause 1. The alarm device is faulty.

2. The smoke density in equipment room is too high.


Specific Problem 1. The alarm device is faulty.

2. The smoke density in equipment room is too high.


System Impact Services won't be affected, but there is a potential safety problem.

HandlingSuggestion

1. Quick find the origin of smog.

2. If there is no smog in the equipment room, replace the smogdetector.


198025867 Infrared alarmAlarm Property � Alarm Code:198025867

� Description:Infrared alarm

� Severity:Minor


Probable Cause 1. Heat source (e.g. animal/human being) approaches near.

2. The configuration of infra-red sensor is wrong.

3. The infrared sensor is faulty.


Specific Problem 1. Heat source (e.g. animal/human being) approaches near.

2. The configuration of infra-red sensor is wrong.

3. The infrared sensor is faulty.


System Impact 1. If the configuration of infra-red sensor is wrong, the systemwon't be affected.

2. If the infra-red light in the equipment room is over threshold,there is a potential safety problem.

HandlingSuggestion

1. Does an animal or a person approach near the infrared sensor?If yes, remove the heat source. If no, please check the con-figuration of infra-red sensor. If the configuration is correct,sensor sensitivity may be reduced to some extent.

2. The infra-red sensor is faulty. Replace the sensor.




198025868 Lightning alarmAlarm Property � Alarm Code:198025868

� Description:Lightning alarm

� Severity:Minor


Probable Cause 1. Outdoor unit or equipment damaged by lightening


Specific Problem 1. Outdoor unit or equipment damaged by lightening


System Impact The board may work abnormally due to lightning stroke. Accord-ingly, board services will be interrupted.

HandlingSuggestion

1. Check earthing connection.

2. Check lightning protection antenna.


198025869 Loss of DCpower supply to rack


� Description:Loss of DC power supply to rack

� Severity:Minor


Probable Cause 1. Circuit breaker has tripped.

2. No incoming DC supply from rectifier

Specific Problem 1. Circuit breaker has tripped.

2. No incoming DC supply from rectifier

System Impact This shelf can not be supplied with power. All boards on the shelfcan not work and board services are interrupted.

HandlingSuggestion

1. Is this shelf needed? 1. If yes, ensure that the atmosphereswitch is closed and ALM indicator is normal.

2. If no, screen the function of monitoring atmosphere switch. InNMS Configuration Management interface, click Power BoardAlarm Parameters; then set the status of atmosphere switchto be screened.




198029184 SNTP server isunavailable


� Description:SNTP server is unavailable

� Severity:Minor


Probable Cause SNTP server is faulty or communication broken.

Specific Problem SNTP server is faulty or communication broken.

System Impact NO impact to traffic only loss of Time synchronisation data for timestamp of events and reporting.

HandlingSuggestion

1. Check whether the physical link is normal by using Ping com-mand.

Y->Solve the physical link problem.

N->go to "2".

2. Check whether the server IP is correct.

Y->Configure the IP address.

N->Contact ZTE.


C h a p t e r 6

QoS Alarm

Table of Contents198015361 Ring and queue overload alarm......................... 315198023296 Inter-board message communication flow rateexceeds the alarm threshold ............................................. 316198066069 The number of times of signaling data transferexceeds the allowed threshold of the license ....................... 316198087341 FR congestion ................................................ 317198087344 MSC overload control alarm at FUC mode........... 317198087345 CPU overload control alarm at FUC mode ........... 318198087346 Signaling point congestion control alarm at FUCmode............................................................................. 318198087347 MSC overload control alarm at SYS mode........... 319198087348 CPU overload control alarm at SYS mode ........... 319198087349 Signaling point congestion control alarm at SYSmode............................................................................. 320198087350 CS CCCH overload .......................................... 320198087351 PS CCCH overload........................................... 321198087435 A interface resource statistic alarm.................... 321198087436 NSVC resource statistics alarm ......................... 322198087437 TCH resources statistics alarm.......................... 322198087438 Assignment failure alarm ................................. 323198087468 LAPD congestion alarm.................................... 323198087506 NSE block alarm ............................................. 324198087507 SGSN is blocked. ............................................ 324198087758 Manual User Access control alarm ..................... 325198087759 CPU overload control alarm at Paging mode......... 325

198015361 Ring and queueoverload alarm


� Description:Ring and queue overload alarm

� Severity:Major

� Alarm Type:Qos Alarm

Probable Cause Service overload in the board.

Specific Problem Service overload in the board.

System Impact Service quality will get bad, even make service lost.



HandlingSuggestion

You should readjust board's resource to reduce service load in thisboard.

198023296 Inter-boardmessage communicationflow rate exceeds the alarmthreshold


� Description:Inter-board message communication flow rate ex-ceeds the alarm threshold

� Severity:Minor


Probable Cause The configured alarm threshold is less than the usual inter-boardcommunication traffic in input and output directions of the boardcontrol plane.

Specific Problem The configured alarm threshold is less than the usual inter-boardcommunication traffic in input and output directions of the boardcontrol plane.

System Impact Packet of the control plane loss might occur. No impact on userservice.

HandlingSuggestion

On NMS configuration management interface, check if the config-ured alarm threshold of communication traffic in input and outputdirections of the board control plane is too low. Recommendedvalue: 0xffffffff(4096M).

198066069 The numberof times of signaling datatransfer exceeds the allowedthreshold of the license


� Description:The number of times of signaling data transfer ex-ceeds the allowed threshold of the license

� Severity:Major



Chapter 6 QoS Alarm

Probable Cause The number of transfer that passes MTP3/M3UA/SCCP/SUA exceedthe permission of license.

Specific Problem The number of transfer that passes MTP3/M3UA/SCCP/SUA exceedthe permission of license.

System Impact The data transferred may be discarded when The number of trans-fer exceed the permission of license.

HandlingSuggestion

Contact the related personnel and get proper license again.

198087341 FR congestionAlarm Property � Alarm Code:198087341

� Description:FR congestion

� Severity:Minor


Probable Cause When Gb interface connects through FR, if the number of frameswith BECN set to 1 is more than or equal to the ones with BECNset to 0 for a certain NS-VC in a unit time, then it is considered asbackward congestion.

Specific Problem When Gb interface connects through FR, if the number of frameswith BECN set to 1 is more than or equal to the ones with BECNset to 0 for a certain NS-VC in a unit time, then it is considered asbackward congestion.

System Impact Quality of PS service for some users degrades.

HandlingSuggestion

Increase BRCH links or BRCH time slots.

198087344 MSC overloadcontrol alarm at FUC mode


� Description:MSC overload control alarm at FUC mode

� Severity:Minor


Probable Cause MSC sends overload message, and BSC starts FUC flow control.

Specific Problem MSC sends overload message, and BSC starts FUC flow control.

System Impact Some users fail to gain access.

HandlingSuggestion

BSC can implement flow control automatically. Observe the alarmwithout taking any handling measures.



198087345 CPU overloadcontrol alarm at FUC mode


� Description:CPU overload control alarm at FUC mode

� Severity:Minor


Probable Cause The CPU load exceeds the flow control threshold in system config-uration parameter setting.

Specific Problem The CPU load exceeds the flow control threshold in system config-uration parameter setting.


HandlingSuggestion

1. On NMS Fault Management interface, check alarm details,which indicate the flow control level. If the flow control levelis 3 or lower than 3, observe 3 minutes and wait for alarmrestoring.

2. Block some cells in Dynamic Data Management interface toprevent CPU load from further increasing. After the alarm iseliminated, unblock related cells.

198087346 Signaling pointcongestion control alarm atFUC mode


� Description:Signaling point congestion control alarm at FUCmode

� Severity:Minor


Probable Cause MSC sends the signaling congestion message. BSC starts FUC flowcontrol.

Specific Problem MSC sends the signaling congestion message. BSC starts FUC flowcontrol.


HandlingSuggestion



Chapter 6 QoS Alarm

198087347 MSC overloadcontrol alarm at SYS mode


� Description:MSC overload control alarm at SYS mode

� Severity:Minor


Probable Cause MSC sends the overload message. BSC starts system messageflow control.

Specific Problem MSC sends the overload message. BSC starts system messageflow control.


HandlingSuggestion


198087348 CPU overloadcontrol alarm at SYS mode


� Description:CPU overload control alarm at SYS mode

� Severity:Minor


Probable Cause The excessive traffic causes the CPU load to exceed the flow controlthreshold in module parameter setting.

Specific Problem The excessive traffic causes the CPU load to exceed the flow controlthreshold in module parameter setting.

System Impact The system automatically initiates flow control management andinduce unavailable access for some users. If the traffic is still ex-cessive after flow control, CPU load will further increase.

HandlingSuggestion

1. On NMS Fault Management interface, check alarm details,which indicate the flow control level. If the flow control levelis 3 or lower than 3, observe 3 minutes and wait for alarmrestoring.




198087349 Signaling pointcongestion control alarm atSYS mode


� Description:Signaling point congestion control alarm at SYSmode

� Severity:Minor


Probable Cause The excessive traffic causes the MSC to send signaling congestionmessage. BSC starts system message flow control.

Specific Problem The excessive traffic causes the MSC to send signaling congestionmessage. BSC starts system message flow control.

System Impact The system automatically initiates flow control management andcause unavailable access for some users. If the traffic is still ex-cessive after flow control, it will induce A interface signaling tointerrupt and service interruption.

HandlingSuggestion

1. On NMS fault management interface, check alarm details,which indicate the flow control level. If the flow control levelis 3 or lower than 3, observe 3 minutes and wait for alarmrestoring.


198087350 CS CCCHoverload


� Description:CS CCCH overload

� Severity:Minor


Probable Cause Too many MSs request to gain access on CS CCH.

Specific Problem Too many MSs request to gain access on CS CCH.

System Impact The system automatically initiates flow control management,causing some MSs under this cell to fail to access CS services.

HandlingSuggestion



Chapter 6 QoS Alarm

2. If the alarm occurs frequently, add CS CCCH to the channel in-formation under BTS configuration on Configuration Manage-ment Interface, or expand the capacity of overload site or sharetraffic.

198087351 PS CCCHoverload


� Description:PS CCCH overload

� Severity:Minor


Probable Cause Too many MSs request to gain access on PS CCH.

Specific Problem Too many MSs request to gain access on PS CCH.

System Impact The system automatically initiates flow control management,causing some MSs under this cell to fail to access PS services.

HandlingSuggestion


2. If the alarm occurs frequently, add CS CCCH to the channel in-formation under BTS configuration on Configuration Manage-ment Interface, or expand the capacity of overload site or sharetraffic.

198087435 A interfaceresource statistic alarm


� Description:A interface resource statistic alarm

� Severity:Major


Probable Cause Alarm is triggered when A interface resource block rate in OMP/IMPis higher than the threshold.

Specific Problem Alarm is triggered when A interface resource block rate in OMP/IMPis higher than the threshold.

System Impact If the alarm is not addressed, long-time CS service access will beaffected, and telephone is hard or event not able to get through,thus affecting traffic.



HandlingSuggestion

1. On NMS Dynamic Data Management interface, check if A inter-face circuit state is normal. 1. Check DTB board of A interfaceor the physical connection of E1 on SPB/SPB2, and ensure theyare ok.

2. Check whether MSC is blocked or uninstalled. If yes, contactMSC maintenance personnel to check MSC.

3. Check whether PCM is blocked. If yes, unblock PCM.

4. Check whether DRTB/DRTB2 board works properly. If not, re-set, re-insert or replace the board.

5. Check whether PCM number in BSC side is the same as theone in MSC side. If not, modify BSC side PCM number to beconsistent with MSC one, and observe whether the alarm isrestored.

198087436 NSVC resourcestatistics alarm


� Description:NSVC resource statistics alarm

� Severity:Major


Probable Cause Alarm is triggered whenNSVC resource block rate in OMP/IMP ishigher than the threshold.

Specific Problem Alarm is triggered whenNSVC resource block rate in OMP/IMP ishigher than the threshold.

System Impact PS service of some cells is unavailable.

HandlingSuggestion

1. Check whether FR device failure alarm exists persistently. Ifyes, please refer to the addressing method of "

2. FR device failure" alarm. After eliminating FR device failurealarm, observe whether this alarm disappears. 2. Checkwhether NSVC data configuration is the same as SGSN side.If not, modify NSVC data configuration to be consistent withSGSN side, and observe whetheralarm disappears.

3. Check whether manually blocked NSVC exists, if so, manuallyunblock it.

198087437 TCH resourcesstatistics alarm


� Description:TCH resources statistics alarm


Chapter 6 QoS Alarm

� Severity:Major


Probable Cause Alarm is triggered when CMP/IMP TCH resource block rate is higherthan the threshold.

Specific Problem Alarm is triggered when CMP/IMP TCH resource block rate is higherthan the threshold.

System Impact If the alarm were not handled, it might induce call failure.

HandlingSuggestion

1. Check whether channels are manually blocked, if yes, unblockthem.

2. Check whether TRX state is normal, if not, reset, re-insert orreplace TRX.

3. Check cells' work state and disturbance situation. If cells workabnormal or disturbance happens severely, the network needto be optimized.

198087438 Assignmentfailure alarm


� Description:Assignment failure alarm

� Severity:Major


Probable Cause TCH assignment fails in large scale and exceeds threshold.

Specific Problem TCH assignment fails in large scale and exceeds threshold.

System Impact Service quality will remain low for a long time if alarm is not han-dled.

HandlingSuggestion

1. Check whether channels are manually blocked, if yes, unblockthem.

2. Check whether TRX state is normal, if not, reset, re-insert orreplace TRX.

3. Check cells' work state and disturbance situation. If cells workabnormally or disturbance happens severely, the network needto be optimized.

198087468 LAPDcongestion alarm


� Description:LAPD congestion alarm





Probable Cause LAPD link is congested.

Specific Problem LAPD link is congested.

System Impact Abnormal communication or even link break might be induced be-cause of serious LAPD frame discarding

HandlingSuggestion

1. Check whether configured LAPD channels are enough accord-ing to site-configured carriers, and add more LAPD channels ifnot.

2. Check whether there are trunk circuits alarm and trunk slipnotification on E1, and solve E1 transmission problem first if itappears.

3. Check whether site voltage is unstable or too low.

198087506 NSE block alarmAlarm Property � Alarm Code:198087506

� Description:NSE block alarm

� Severity:Major


Probable Cause All NSVCs of the NSE are blocked

Specific Problem All NSVCs of the NSE are blocked

System Impact The NSE can not run PS

HandlingSuggestion

1. If NSVC is manually blocked, please unblock it in Dynamic DataManagement interface of NMS.

2. Otherwise, please check Gb link.

198087507 SGSN isblocked.


� Description:SGSN is blocked.



Probable Cause All NSEs of the SGSN are blocked

Specific Problem All NSEs of the SGSN are blocked

System Impact All NSEs of the SGSN can not run PS


Chapter 6 QoS Alarm

HandlingSuggestion

1. If NSVC is manually blocked, please unblock it in Dynamic DataManagement interface of NMS.

2. Otherwise, please check Gb link.

198087758 Manual UserAccess control alarm


� Description:Manual User Access control alarm

� Severity:Minor


Probable Cause Start manual user access control

Specific Problem Start manual user access control


HandlingSuggestion


198087759 CPU overloadcontrol alarm at Pagingmode


� Description:CPU overload control alarm at Paging mode

� Severity:Minor


Probable Cause The excessive traffic causes the CPU load to exceed the flow controlthreshold in module parameter setting.

Specific Problem The excessive traffic causes the CPU load to exceed the flow controlthreshold in module parameter setting.

System Impact The system automatically initiates flow control management andthus some users cannot gain access. If the traffic is still excessiveafter flow control, the CPU load will grow further.

HandlingSuggestion

Block some cells through dynamic data management to prohibitsome users to access. After the alarm is eliminated, restore theconfiguration or unblock the related cells.


Glossary

OAM- Operation, Administration and Maintenance


V2,V3 Alarms

Documents

Transcript of V2,V3 Alarms