ZXG10 IBSC (V6.30.103) Alarm and Notification Handling Reference_579008

ZXG10 iBSCBase Station Controller

Alarm and Notification Handling Reference

Version: V6.30.103

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

LEGAL INFORMATIONCopyright © 2014 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or

distribution of this document or any portion of this document, in any form by any means, without the prior written

consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by

contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE

CORPORATION or of their respective owners.

This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions

are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,

title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the

use of or reliance on the information contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications

covering the subject matter of this document. Except as expressly provided in any written license between ZTE

CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter

herein.

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

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

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

Revision History

Revision No. Revision Date Revision Reason

R1.1 2014–04–11 Update all text

R1.0 2013–06–04 First edition

Serial Number: SJ-20130408113951-012

Publishing Date: 2014-04-11 (R1.1)

SJ-20130408113951-012|2014-04-11 (R1.1) ZTE Proprietary and Confidential

ContentsAbout This Manual ......................................................................................... I

Chapter 1 Overview.................................................................................... 1-1

Chapter 2 General Operations................................................................... 2-12.1 Finding the Managed Objects Through an Alarm Object ....................................... 2-1

2.1.1 Querying the Configuration Object............................................................. 2-1

2.1.2 Querying the Parent Object of a Configuration Object ................................. 2-4

2.1.3 Querying the Referring Object of a Configuration Object ............................. 2-6

2.2 Filtering Controller Alarms................................................................................. 2-10

2.2.1 Checking Board Alarms Through the Rack Diagram ................................. 2-10

2.2.2 Filtering Alarms Based on Alarm Location.................................................2-11

2.2.3 Querying Alarms by Office Information..................................................... 2-13

Chapter 3 Alarms........................................................................................ 3-13.1 Equipment Alarm................................................................................................ 3-1

3.1.1 198019456 All high-speed links between line card and switching boardsare out of synchronization........................................................................ 3-1

3.1.2 198019465 CSIX RX and TX packets is abnormal ...................................... 3-2

3.1.3 198029952 802.3ah link fault .................................................................... 3-3

3.1.4 198030208 Fault alarm of CFM................................................................. 3-4

3.1.5 198005633 Hard disk is faulty ................................................................... 3-5

3.1.6 198005635 The board is not plugged firmly................................................ 3-6

3.1.7 198005639 High Error Rate of Optical Interface ......................................... 3-7

3.1.8 198005640 FPGA exception ..................................................................... 3-8

3.1.9 198005644 The channel in a sub card is down........................................... 3-9

3.1.10 198005645 Sub card abnormal ............................................................... 3-9

3.1.11 198005646 Phase-lock loop unlocked ................................................... 3-10

3.1.12 198005647 High BER on E1 link ............................................................3-11

3.1.13 198005656 Input clock of subcard lost ................................................... 3-12

3.1.14 198005663 Component fault ................................................................. 3-13

3.1.15 198005665 Fault on board (GPS) ......................................................... 3-14

3.1.16 198000256 Ethernet link to OMC is broken. ........................................... 3-15

3.1.17 198001284 The phase of 8K, 16K clock, input to backplane board, isnot matched ......................................................................................... 3-16

3.1.18 198001286 Input clock of board lost ...................................................... 3-16

I


3.1.19 198000002 Loss of optical signal........................................................... 3-17

3.1.20 198001792 Loss of SDH transmission link ............................................. 3-18

3.1.21 198001825 High BER on SDH / Sonet link ............................................. 3-20

3.1.22 198015874 Data traffic to PSN board is congested ................................. 3-21

3.1.23 198015875 GLI table lookup failed ........................................................ 3-21

3.1.24 198015876 GLI exception packets statistic over threshold....................... 3-22

3.1.25 198015877 GLIQV SRAM/DRAM error .................................................. 3-23

3.1.26 198002560 Board CPU overload ........................................................... 3-23

3.1.27 198002561 High temperature on CPU board.......................................... 3-24

3.1.28 198025602 TDM switch abnormal ......................................................... 3-25

3.1.29 198005376 Internal media port of board is abnormal............................... 3-26

3.1.30 198066070 Board offline or CPU in reset status for a long period ............ 3-27

3.1.31 198005381 Input clock is abnormal........................................................ 3-28

3.1.32 198005389 CPU sub card in position is not configured in the database ..... 3-28

3.1.33 198005390 CPU sub card is missing from slot but is configured indatabase .............................................................................................. 3-29

3.1.34 198005395 External port abnormal ........................................................ 3-30

3.1.35 198005396 Exceptional communication on UIM board or back plane ...... 3-31

3.1.36 198005399 DSP resource is unavailable................................................ 3-32

3.1.37 198005403 Board SRAM self-check fails ............................................... 3-33

3.1.38 198005404 Board OCXO oven fault....................................................... 3-33

3.1.39 198005405 Clock board phase-lock loop work mode abnormal................ 3-34

3.1.40 198026116 PP2S output clock lost......................................................... 3-34

3.1.41 198026117 PP2S clock reference lost.................................................... 3-35

3.1.42 198026118 16CHIP clock reference lost................................................. 3-36

3.1.43 198026127 Loss of Level 3 reference source clock................................. 3-36

3.1.44 198026128 Loss of Level2 reference source clock ................................. 3-37

3.1.45 198026129 Loss of Level1 reference source clock.................................. 3-38

3.1.46 198026131 CLKG board PLL is unlocked. Clock will drift ....................... 3-39

3.1.47 198026133 Output clock lost ................................................................. 3-40

3.1.48 198005632 Hard disk usage rate exceeds threshold. ............................. 3-40

3.1.49 198005637 Back card does not match with front board ........................... 3-41

3.1.50 198005661 Physical link down between media interface ports................. 3-42

3.1.51 198005662 IDE running overtime .......................................................... 3-42

3.1.52 198005667 E1 is looped back ............................................................... 3-43

3.1.53 198005668 Cross-linked E1 alarm......................................................... 3-44

3.1.54 198005669 Synchronization status check of FPGA failed ........................ 3-44

II


3.1.55 198005671 Sending or receiving packets using the cascade ports innerboard failed .......................................................................................... 3-45

3.1.56 198005655 Errors detected in DSP........................................................ 3-46

3.1.57 198019712 APS channel mismatched ................................................... 3-47

3.1.58 198019713 APS mode mismatched....................................................... 3-48

3.1.59 198019714 APS configuration alarm...................................................... 3-49

3.1.60 198005121 Inter-shelf media plane links abnormal ................................. 3-50

3.1.61 198005124 Capacity of TRUNK communication is insufficient ................. 3-51

3.1.62 198005125 GE optical connection is cross connected............................. 3-52

3.1.63 198005893 Memory check failed ........................................................... 3-52

3.1.64 198005650 Conflicted MAC addresses of boards on the same shelf ........ 3-53

3.1.65 198005672 Synchronization Ethernet clock source is unusable ............... 3-54

3.1.66 198015878 GLI internal fabric port receive error ..................................... 3-55

3.1.67 198015879 GLI Port receive error.......................................................... 3-55

3.1.68 198015880 GLI board control and media plane communication error ....... 3-56

3.1.69 198015881 GLI port transmit error ......................................................... 3-57

3.1.70 198015882 GLI buffer error or allocate fail ............................................. 3-57

3.1.71 198005670 Oscillator status abnormal ................................................... 3-58

3.1.72 198005673 Backboard switch set is changed. ........................................ 3-59

3.1.73 198005653 Type B fault on board (GPS) phase-lock equipment .............. 3-59

3.1.74 198005674 Sending or receiving packets between management portand CPU control port failed.................................................................... 3-61

3.1.75 198005130 The fiber port failed to change over ...................................... 3-61

3.1.76 198005131 The fiber's quality abnormal................................................. 3-62

3.1.77 198005675 The input electrical source is error ....................................... 3-63

3.1.78 198016641 Device's LRU algorithm invalid............................................. 3-64

3.1.79 198002563 FPGA clock speed abnormal alarm ...................................... 3-64

3.1.80 198002564 Auxiliary clock speed abnormal alarm .................................. 3-65

3.1.81 198005132 Mate board RUN signal invalid............................................. 3-66

3.1.82 198005676 Connect port flow over threshold.......................................... 3-66

3.1.83 198005791 TX output power exceeds the high threshold ........................ 3-67

3.1.84 198005792 TX output power exceeds the low threshold.......................... 3-68

3.1.85 198005793 RX output power exceeds the high threshold ........................ 3-68

3.1.86 198005794 RX output power exceeds the low threshold ......................... 3-69

3.1.87 198005795 The optical transceiver transmitter fault ................................ 3-70

3.1.88 198018436 Board loop back detection is abnormal ................................. 3-70

3.1.89 198016896 APP driver memory operation abnormal ............................... 3-71

3.1.90 198105013 user plane resource pool overload ....................................... 3-71

III


3.1.91 198105026 Media Ip address modified................................................... 3-72

3.1.92 198105029 OMP reboot alarm .............................................................. 3-73

3.1.93 198105034 Back card of LogService board is offline ............................... 3-74

3.1.94 198105036 The hard disk of LogService error ........................................ 3-75

3.1.95 198105037 Too high hard disk partition usage rate ................................. 3-75

3.1.96 198105039 Bursty flow rate of the control plane for shelf connectionoverload ............................................................................................... 3-76

3.1.97 198028672 80g chip abnormal .............................................................. 3-77

3.1.98 198005657 Error of LVDS path frame detection ..................................... 3-78

3.1.99 198005658 Failure in diagnosing link loop back of large T network .......... 3-78

3.1.100 198025601 TSNB internal connection chip fault.................................... 3-79

3.1.101 198066033 T-net center is fault ........................................................... 3-80

3.1.102 198005660 Physical link down between master port and slave port ....... 3-80

3.1.103 198005641 Port Link Down ................................................................. 3-81

3.1.104 198019715 MS APS channel gets errors.............................................. 3-82

3.1.105 198087340 FR device failure............................................................... 3-82

3.1.106 198087341 FR congestion .................................................................. 3-84

3.1.107 198087352 NSVC's E1 failure alarm .................................................... 3-85

3.1.108 198087465 NSVC's IP failure alarm..................................................... 3-86

3.1.109 198087458 PS cell block caused by slave............................................ 3-87

3.1.110 198087000 Dry contact alarm 1 ........................................................... 3-87









3.1.119 198087009 Dry contact alarm 10 ......................................................... 3-92



3.1.122 198087012 EAM dry contact 1 alarm .................................................. 3-94

3.1.123 198087013 EAM dry contact 2 alarm ................................................... 3-95





IV




3.1.130 198087102 Power overvoltage/undervoltage alarm............................... 3-98

3.1.131 198087103 13M input clock failure....................................................... 3-99

3.1.132 198087106 SYNCLK clock failure .......................................................3-100

3.1.133 198087107 Master and slave communication link failure ......................3-100

3.1.134 198087108 Standby CMM/CMB board not present ..............................3-101

3.1.135 198087109 Standby CMM/CMB board abnormal .................................3-102

3.1.136 198087110 CMM/CMB power failure alarm .........................................3-102

3.1.137 198087112 Communication link alarm between master and slave rack(left) ...................................................................................................3-103

3.1.138 198087113 Communication link alarm between master and slave rack(right) .................................................................................................3-103

3.1.139 198087114 A interface E1 Rx carrier alarm .........................................3-104

3.1.140 198087115 A interface E1 Rx frame not synchronized..........................3-105

3.1.141 198087120 A interface E1 remote alarm .............................................3-106

3.1.142 198087121 B interface E1 Rx carrier alarm .........................................3-106

3.1.143 198087122 B interface E1 Rx frame not synchronized .........................3-107

3.1.144 198087127 B interface E1 remote alarm .............................................3-108

3.1.145 198087128 C interface E1 Rx carrier alarm .........................................3-108

3.1.146 198087129 C interface E1 Rx frame not synchronized .........................3-109

3.1.147 198087134 C interface E1 remote alarm .............................................3-110

3.1.148 198087135 D interface E1 Rx carrier alarm ......................................... 3-111

3.1.149 198087136 D interface E1 Rx frame not synchronized ......................... 3-111

3.1.150 198087141 D interface E1 remote alarm .............................................3-112

3.1.151 198087142 E interface E1 Rx carrier alarm .........................................3-113

3.1.152 198087143 E interface E1 Rx frame not synchronized .........................3-113

3.1.153 198087148 E interface E1 remote alarm .............................................3-114

3.1.154 198087149 F interface E1 Rx carrier alarm .........................................3-115

3.1.155 198087150 F interface E1 Rx frame not synchronized .........................3-116

3.1.156 198087153 F interface E1 Rx forward sliding indication........................3-116

3.1.157 198087155 F interface E1 remote alarm .............................................3-117

3.1.158 198087156 G interface E1 Rx carrier alarm.........................................3-118

3.1.159 198087157 G interface E2 Rx frame not synchronized .........................3-118

3.1.160 198087162 G interface E1 remote alarm.............................................3-119

3.1.161 198087163 H interface E1 Rx carrier alarm .........................................3-119

3.1.162 198087164 H interface E3 Rx frame not synchronized .........................3-120

3.1.163 198087169 H interface E1 remote alarm .............................................3-121

V


3.1.164 198087170 Temperature alarm...........................................................3-121

3.1.165 198087171 Fan absent ......................................................................3-122

3.1.166 198087172 Fan control board CPU alarm ...........................................3-123

3.1.167 198087173 Fan alarm .......................................................................3-123

3.1.168 198087174 Fan temperature alarm.....................................................3-124

3.1.169 198087175 Fan 1 alarm .....................................................................3-124

3.1.170 198087176 Fan 2 alarm .....................................................................3-125

3.1.171 198087177 Fan control board alarm ...................................................3-126

3.1.172 198087178 LNA alarm ......................................................................3-126

3.1.173 198087179 Tower amplifier power alarm .............................................3-127

3.1.174 198087180 SWR of AEM HYCOM minor alarm ...................................3-127

3.1.175 198087181 SWR of AEM HYCOM major alarm ...................................3-128

3.1.176 198087182 AEM power alarm(BTS V2)...............................................3-128

3.1.177 198087183 AEM type alarm(BTS V2) .................................................3-129

3.1.178 198087184 AEM absent(BTS V2) .......................................................3-130

3.1.179 198087185 AEM power alarm ............................................................3-130

3.1.180 198087186 LNA0 alarm ....................................................................3-131

3.1.181 198087187 LNA1 alarm ....................................................................3-132

3.1.182 198087188 Tower Amplifier0 power alarm ..........................................3-132

3.1.183 198087189 Tower Amplifier1 power alarm...........................................3-133

3.1.184 198087190 SWR of AEM HYCOM minor alarm ..................................3-134

3.1.185 198087191 SWR of AEM HYCOM major alarm ..................................3-135

3.1.186 198087192 AEM type alarm ...............................................................3-136

3.1.187 198087193 AEM Not-in-position alarm................................................3-137

3.1.188 198087198 Uplink of ADC chip initialization failure...............................3-138

3.1.189 198087200 CIP resource can't be used...............................................3-139

3.1.190 198087201 Uplink failure....................................................................3-139

3.1.191 198087207 Watchdog of FUC overflow ...............................................3-140

3.1.192 198087216 Cell configuration parameter mismatch(BTS V2) ................3-140

3.1.193 198087221 Communication link between CMM and FUC break(BTSV2)......................................................................................................3-141

3.1.194 198087224 Watchdog of TPU CIP overflow.........................................3-142

3.1.195 198087225 Software version of CIP mismatch.....................................3-142

3.1.196 198087226 Clock alarm for TPU and CMM .........................................3-143

3.1.197 198087228 TPU frame No. alarm .......................................................3-144

3.1.198 198087229 TPU CHP DSP0 initialization failure ..................................3-144

3.1.199 198087243 Cell configuration parameter mismatch..............................3-145

VI


3.1.200 198087247 HDLC communication link between CMB and FUCbroken.................................................................................................3-146

3.1.201 198087453 signal HDLC break off ......................................................3-146

3.1.202 198087253 FU fram No error alarm ...................................................3-147

3.1.203 198087254 Rx PLL1 unlock ...............................................................3-148

3.1.204 198087255 Rx PLL2 unlock ...............................................................3-148

3.1.205 198087256 Tx PLL1 unlock ...............................................................3-149

3.1.206 198087257 Tx PLL2 unlock ...............................................................3-150

3.1.207 198087258 52M referenced clock PLL unlock .....................................3-150

3.1.208 198087259 Tx IF PLL unlock .............................................................3-151

3.1.209 198087260 EEPROM resource can't be used......................................3-152

3.1.210 198087261 FPGA interface failure ......................................................3-152

3.1.211 198087262 PA VSWR alarm(BTS V2) .................................................3-153

3.1.212 198087263 PA overtemperature minor alarm(BTS V2) ........................3-153

3.1.213 198087264 PA overtemperature major alarm(BTS V2) .........................3-154

3.1.214 198087265 PA output power alarm .....................................................3-155

3.1.215 198087266 PA power overvoltage ......................................................3-155

3.1.216 198087267 PA power lower voltage ....................................................3-156

3.1.217 198087268 Downlink checksum error of DLRC_AL1............................3-156

3.1.218 198087269 DUC chip initialization failure ............................................3-157

3.1.219 198087270 80w PA VSWR alarm .......................................................3-157

3.1.220 198087271 80w PA overtemperature ..................................................3-158

3.1.221 198087272 80w PA overtemperature major alarm................................3-159

3.1.222 198087273 80w PA output power alarm ..............................................3-159

3.1.223 198087274 80w PA power overvoltage ...............................................3-160

3.1.224 198087275 80w PA power lower voltage .............................................3-160

3.1.225 198087276 80w PA absent.................................................................3-161

3.1.226 198087277 TXIF unlock .....................................................................3-161

3.1.227 198087278 TPF unlock ......................................................................3-162

3.1.228 198087279 TXRF unlock....................................................................3-163

3.1.229 198087280 RXRF unlock ...................................................................3-164

3.1.230 198087281 13 MHz clock lost.............................................................3-164

3.1.231 198087282 60 ms clock lost ...............................................................3-165

3.1.232 198087285 52 MHz clock lost.............................................................3-166

3.1.233 198087288 PA power overvoltage alarm .............................................3-166

3.1.234 198087289 PA power undervoltage alarm ...........................................3-167

3.1.235 198087290 PA VSWR alarm ..............................................................3-167

3.1.236 198087291 PA temperature minor alarm .............................................3-168

VII


3.1.237 198087292 PA temperature major alarm .............................................3-169

3.1.238 198087293 PA forward power(3db) alarm............................................3-169

3.1.239 198087294 RTU power alarm.............................................................3-170

3.1.240 198087295 RTU power temperature alarm..........................................3-171

3.1.241 198087296 RTU power output overvoltage alarm ................................3-171

3.1.242 198087297 RTU power input failure alarm...........................................3-172

3.1.243 198087298 IQ calibration parameters abnormal alarm .........................3-172

3.1.244 198087299 EAM heat exchanger alarm ..............................................3-173

3.1.245 198087300 EAM TRX layer fan-4 alarm ..............................................3-173

3.1.246 198087301 EAM AEM layer axis-flow fan alarm...................................3-174

3.1.247 198087302 EAM smoke alarm............................................................3-174

3.1.248 198087303 EAM waterproof alarm......................................................3-175

3.1.249 198087304 EAM lightning protection alarm .........................................3-176

3.1.250 198087305 EAM backdoor access control alarm .................................3-176

3.1.251 198087306 EAM frontdoor access control alarm..................................3-177

3.1.252 198087307 EAM PWR monitoring unit alarm.......................................3-177

3.1.253 198087308 EAM heat exchanger electric heater alarm.........................3-178

3.1.254 198087309 EAM heat exchanger control board alarm ..........................3-178

3.1.255 198087310 EAM heat exchanger external circulation fan 2 alarm .........3-179

3.1.256 198087311 EAM heat exchanger external circulation fan 1 alarm..........3-179

3.1.257 198087312 EAM heat exchanger internal circulation fan 2 alarm ..........3-180

3.1.258 198087313 EAM heat exchanger internal circulation fan 1 alarm ..........3-181

3.1.259 198087314 EAM heat exchanger 485 communication alarm.................3-181

3.1.260 198087315 EAM temperature alarm ...................................................3-182

3.1.261 198087316 EAM TRX layer mixed-flow fan 1 alarm .............................3-182



3.1.264 198087319 Communication broken between EAM and CMB ................3-184

3.1.265 198087320 Power undervoltage alarm................................................3-184

3.1.266 198087321 Inner fan 2 alarm (for M8202) ...........................................3-185

3.1.267 198087322 Inner fan 1 alarm (for M8202) ...........................................3-186

3.1.268 198087323 Outer fan 2 and fan 4 alarm (for M8202) ............................3-186

3.1.269 198087324 Outer fan 1 and fan 3 alarm (for M8202) ............................3-187

3.1.270 198087325 Rack temperature minor alarm..........................................3-187

3.1.271 198087326 Rack temperature major alarm..........................................3-188

3.1.272 198087327 Layer 3 fan 1 alarm (for M8206) ........................................3-188


VIII









3.1.281 198087391 FCU power undervoltage alarm ........................................3-194

3.1.282 198087403 The clock alarm about transmission of CCI board Abis-E1...........................................................................................................3-195

3.1.283 198087404 The local working clock alarm of CCI board .......................3-195

3.1.284 198087405 The clock alarm about transmission of CCI board 13M ......3-196

3.1.285 198087406 CCI opposite board alarm.................................................3-196

3.1.286 198087407 IQ FPGA internal clock alarm............................................3-197

3.1.287 198087408 IQ FPGA light interface alarm ..........................................3-197

3.1.288 198087409 IQ FPGA LVDS interface alarm.........................................3-198

3.1.289 198087410 IQ FPGA internal data alarm.............................................3-198

3.1.290 198087470 Fan absence alarm ..........................................................3-199

3.1.291 198087471 Fan rotate alarm ..............................................................3-200

3.1.292 198087472 CMB and FNCB RS485 link break alarm ...........................3-200

3.1.293 198087480 Status of TX5 filter alarm ..................................................3-201

3.1.294 198087481 Status of TX6 filter alarm ..................................................3-201

3.1.295 198087443 Diversity antenna lost .......................................................3-202

3.1.296 198087444 Diversity antenna identical ................................................3-202

3.1.297 198087411 13M,61.44M clock lost alarm.............................................3-203

3.1.298 198087412 60ms clock lost alarm.......................................................3-204

3.1.299 198087413 26MHz and 52MHz lost of clock alarm...............................3-204

3.1.300 198087414 the failure examination alarm of the 60ms uplink frame.......3-205

3.1.301 198087415 checking block data error alarm ........................................3-205

3.1.302 198087416 up link LVDS SERDES lost lock alarm...............................3-206

3.1.303 198087417 FN error alarm .................................................................3-207

3.1.304 198087432 Diversity antenna lost .......................................................3-207

3.1.305 198087433 Diversity antenna identical ................................................3-208

3.1.306 198087451 board not support 16MHW................................................3-208

3.1.307 198087452 cmb or cpu overload.........................................................3-209

3.1.308 198087454 main HDLC break off........................................................3-209

3.1.309 198087455 FIB configure wrong .........................................................3-210

3.1.310 198087456 lay3 of FIB software has no response................................3-210

IX


3.1.311 198087460 positive 12 voltage alarm ..................................................3-211

3.1.312 198087461 negative 12 voltage alarm.................................................3-212

3.1.313 198087462 DSP 1.2v voltage alarm....................................................3-212

3.1.314 198087463 6.4v voltage alarm............................................................3-213

3.1.315 198087464 5v voltage alarm ..............................................................3-213

3.1.316 198087473 DTPU CPU overload ........................................................3-214

3.1.317 198087483 GPS signal synchronization exception...............................3-215

3.1.318 198087484 Second pulse loss............................................................3-215

3.1.319 198087485 Antenna open-circuit alarm ...............................................3-216

3.1.320 198087486 Antenna short-circuit alarm ...............................................3-216

3.1.321 198087487 Lost satellite alarm ...........................................................3-217

3.1.322 198087510 CPU of FIB overload ........................................................3-218

3.1.323 198088000 DTPU not support Baseband-Hop alarm............................3-218

3.1.324 198088001 PA Power Voltage Adjusting Path Disconnected.................3-219

3.1.325 198088002 PA Power Voltage Adjusting Data Error .............................3-219

3.1.326 198088003 PA Power Voltage Adjusting Data Illegal ............................3-220

3.1.327 198088004 Access iBSC failure..........................................................3-221

3.1.328 198088005 Control link broken ...........................................................3-221

3.1.329 198088006 Operation link broken(CS) ................................................3-222

3.1.330 198088007 Operation link broken(PS) ................................................3-222

3.1.331 198088008 Parameter configuration mismatch ....................................3-223

3.1.332 198088009 DSP initialization failure....................................................3-223

3.1.333 198088010 Parameter configuration failure of AD6537.........................3-224

3.1.334 198088011 Tx PLL unlock ..................................................................3-225

3.1.335 198088012 Wrong parameter configuration for EEPROM.....................3-225

3.1.336 198088013 FLASH memory fault ........................................................3-226

3.1.337 198088014 Run abnormity of DSP......................................................3-226

3.1.338 198088015 FPGA interface fault.........................................................3-227

3.1.339 198088016 CHP frame fault ...............................................................3-227

3.1.340 198088017 Wrong receive channel of RF............................................3-228

3.1.341 198088018 Get DNS failure when configuration IP of active .................3-229

3.1.342 198088019 Analyse failure of DNS domain name ................................3-229

3.1.343 198088020 IPSec failure ....................................................................3-230

3.1.344 198088021 RF channel and HTRG board unconformity .......................3-230

3.1.345 198088022 Get HBTS'S IP address failure from DHCP Sever ..............3-231

3.1.346 198088023 Over temperature.............................................................3-231

3.1.347 198088024 Voltage abnormity ............................................................3-232

X


3.1.348 198088025 Abis link change alarm .....................................................3-232

3.1.349 198088026 IPOE uplink and downlink jam alarm .................................3-233

3.1.350 198088027 DIP E1 rack, rack type error..............................................3-234

3.1.351 198088028 DIP E1 rack, rack number error.........................................3-234

3.1.352 198088029 DIP E1 rack,slave rack 1 port error....................................3-235

3.1.353 198088030 DIP E1 rack,slave rack 2 port error....................................3-235

3.1.354 198088031 DIP E1 rack,satellite back up flag error ..............................3-236

3.1.355 198088032 DIP E1 rack,oam time slot error ........................................3-236

3.1.356 198088033 DIP IP rack,access mode error(IP or IPOE) .......................3-237

3.1.357 198088034 DIP IP rack,rack number error...........................................3-237

3.1.358 198088035 DIP IP rack,site number error............................................3-238

3.1.359 198088036 DIP IP rack,sequence number error ..................................3-238

3.1.360 198088037 Mains power failure alarm.................................................3-239

3.1.361 198088038 Alarm of the trx's down link LRC failed...............................3-240

3.2 Communication Alarm .....................................................................................3-240

3.2.1 198022784 BFD Session Interrupted ......................................................3-240

3.2.2 198066029 PPP link broken...................................................................3-242

3.2.3 198066026 Association path broken .......................................................3-243

3.2.4 198029953 The Ethernet port state is OAM loop back ............................3-244

3.2.5 198005666 The number of the error packets from MAC port exceeds thethreshold .............................................................................................3-244

3.2.6 198000519 Trunk error ..........................................................................3-245

3.2.7 198000520 Trunk abnormal ...................................................................3-246

3.2.8 198015617 Some frames Received by FE/GE/ATM/MP/POS/E1 Port arefaulty ...................................................................................................3-247

3.2.9 198015618 Faulty frames received by port over threshold........................3-248

3.2.10 198015873 PSN board is sending out incorrect frames ..........................3-249

3.2.11 198003841 The control plane retransmission ratio over the threshold ......3-250

3.2.12 198005651 IP / MAC address conflict ...................................................3-250

3.2.13 198066003 Control plane communication is abnormal between boardand its home module ............................................................................3-251

3.2.14 198005378 Board HW Error .................................................................3-252

3.2.15 198066004 Control plane communication is abnormal between MP andOMP ...................................................................................................3-253

3.2.16 198005382 Communication between power board and OMP isabnormal .............................................................................................3-254

3.2.17 198005397 Communication of RAWMACIP channel is abnormal ............3-255

3.2.18 198005401 Test packet check abnormal ...............................................3-255

XI


3.2.19 198005122 Loss of Active/standby communication link ..........................3-256

3.2.20 198005126 Incorrect FE Routing Connection ........................................3-257

3.2.21 198005127 FE Link Error Alarm ...........................................................3-258

3.2.22 198005128 Duplicate rack and shelf .....................................................3-259

3.2.23 198066005 SCCP subsystem unavailable.............................................3-260

3.2.24 198066010 MTP3 Signalling Point Inaccessible.....................................3-261

3.2.25 198066011 MTP3 link unavailable ........................................................3-261

3.2.26 198066014 M3UA Signalling Point Inaccessible ....................................3-262

3.2.27 198066019 Association link broken.......................................................3-263

3.2.28 198005129 Ethernet port loop back error ..............................................3-264

3.2.29 198031744 IPD session interrupted ......................................................3-265

3.2.30 198105021 IP channel of Iub interface breaks down ..............................3-266

3.2.31 198105035 The communication link between LogService board andOMP is broken ....................................................................................3-268

3.2.32 198066000 Abis link broken .................................................................3-269

3.2.33 198005664 The rate of error code in a mate link is high atGUIM/GUIM2.......................................................................................3-270

3.2.34 198066008 MTP2 link sending overload ...............................................3-271

3.2.35 198066009 MTP2 link reception overload .............................................3-271

3.2.36 198066012 MTP3 cluster inaccessible ..................................................3-272

3.2.37 198087775 Super site exchanged to the satellitic Abis link or slavelink......................................................................................................3-273

3.2.38 198087342 Cell interruption alarm ........................................................3-274

3.2.39 198087380 TRX Manual Block .............................................................3-275

3.2.40 198087336 Rack Abis control link broken..............................................3-275

3.2.41 198087468 lapd jam alarm...................................................................3-276

3.2.42 198087337 Site Abis control link broken................................................3-278

3.2.43 198087101 HW link broken ..................................................................3-279

3.3 Processing error Alarm ....................................................................................3-279

3.3.1 198015360 Microcode Is Abnormal ........................................................3-279

3.3.2 198023040 Number of alarms exceeds threshold. ...................................3-280

3.3.3 198066031 OMP alarm pool is full, unable to store any more alarms. .......3-281

3.3.4 198066032 Loss of NTP time synchronisation.........................................3-281

3.3.5 198066027 SNTP failure........................................................................3-282

3.3.6 198005387 Alarm due to inconsistent MP type ........................................3-283

3.3.7 198005388 Startup file does not exist .....................................................3-284

3.3.8 198005398 Office ID is not set correctly with control shelf ........................3-284

3.3.9 198005402 Database config is different from file named bootcfg.ini ..........3-285

XII


3.3.10 198005649 Port configuration is incorrect .............................................3-285

3.3.11 198005123 Incorrect configuration for inserted board or device ..............3-287

3.3.12 198066013 MTP3 link congestion.........................................................3-288

3.3.13 198066018 Association congestion.......................................................3-289

3.3.14 198105027 The RUB board is overload ................................................3-289

3.3.15 198007936 Memory file buffer overflow.................................................3-290

3.3.16 198005120 T Network Connection Not Conform to Configuration ...........3-291

3.3.17 198005889 Version Switches While Board Doesn't Reset ......................3-292

3.3.18 198005892 Boot Version Fails to Write to Backup Region ......................3-292

3.3.19 198087482 dbsapp data error alarm .....................................................3-293

3.3.20 198087505 Board Connect Fail ............................................................3-294

3.4 QoS Alarm......................................................................................................3-295

3.4.1 198023296 Inter-board message communication flow rate exceeds thealarm threshold....................................................................................3-295

3.4.2 198066069 The number of times of signaling data transfer exceeds theallowed threshold of the license ............................................................3-295

3.4.3 198087344 MSC overload control alarm at FUC mode ............................3-296

3.4.4 198087345 CPU overload control alarm at FUC mode.............................3-297

3.4.5 198087346 Signaling point congestion control alarm at FUC mode...........3-298

3.4.6 198087347 MSC overload control alarm at SYS mode.............................3-299

3.4.7 198087348 CPU overload control alarm at SYS mode .............................3-299

3.4.8 198087349 Signaling point congestion control alarm at SYS mode...........3-300

3.4.9 198087350 CCCH overload control ........................................................3-301

3.4.10 198087506 NSE block alarm................................................................3-302

3.4.11 198087507 SGSN is blocked................................................................3-303

3.4.12 198087513 Board Ethernet port overload alarm.....................................3-304

3.4.13 198087758 Manual User Access control alarm......................................3-304

3.4.14 198087759 CPU overload control alarm at Paging mode .......................3-305

3.4.15 198087773 CIC manual blocked alarm .................................................3-306

3.4.16 198087774 BVC manual blocked alarm ................................................3-307

3.4.17 198087517 Shelf overload control alarm at FUC mode ..........................3-307

3.4.18 198087518 Shelf overload control alarm at SYS mode...........................3-308

3.4.19 198087381 The time-slot of air interface blocked manually.....................3-309

3.5 Environment Alarm..........................................................................................3-310

3.5.1 198025856 Rack temperature is high .....................................................3-310

3.5.2 198025857 Low temperature in Rack .....................................................3-311

3.5.3 198025858 Room temperature is higher than high threshold ...................3-312

3.5.4 198025859 Room temperature is lower than low threshold ......................3-312

XIII


3.5.5 198025860 Rack voltage is high ............................................................3-313

3.5.6 198025861 rack voltage is low ...............................................................3-314

3.5.7 198025862 Humidity is high ...................................................................3-315

3.5.8 198025863 Humidity is low ....................................................................3-315

3.5.9 198025864 Fault in fan plug-in box ........................................................3-316

3.5.10 198025865 Rack door alarm ................................................................3-317

3.5.11 198025866 Smoke detected.................................................................3-317

3.5.12 198025867 Infrared alarm....................................................................3-318

3.5.13 198025868 Lightning alarm..................................................................3-319

3.5.14 198025869 Loss of DC power supply to rack.........................................3-320

3.5.15 198029184 SNTP server is unavailable ................................................3-320

Chapter 4 Notifications .............................................................................. 4-14.1 198020291 Protocol stack process failed to initialize during power on.................... 4-4

4.2 198020802 Conflicting IP address in subnet......................................................... 4-4

4.3 198020803 Conflicting MAC address in subnet .................................................... 4-5

4.4 198020804 Failed to generate static ARP from IP address.................................... 4-6

4.5 198020805 ARP detect failed.............................................................................. 4-7

4.6 198020806 ARP detect that the static ARP is not match ....................................... 4-8

4.7 198018241 TCP Connection Aborted .................................................................. 4-8

4.8 198018242 MD5 Verification Failure .................................................................... 4-9

4.9 198018243 Wrong MD5 Message Abstract ........................................................ 4-10

4.10 198028993 SCTP Primary Path Set Failed....................................................... 4-10

4.11 198030016 Ethernet link OAM event.................................................................4-11

4.12 198000576 Loss of Frame on Trunk .................................................................4-11

4.13 198000834 MCC is faulty ................................................................................ 4-12

4.14 198001600 CPU resets on a board.................................................................. 4-13

4.15 198008005 Memory file buffer overflow............................................................ 4-14

4.16 198017216 Error in MCS Multi-Core processor receiving configuration datafrom DBS ....................................................................................................... 4-14

4.17 198023106 Board self-check fails .................................................................... 4-15

4.18 198023107 The board initialization failure ........................................................ 4-16

4.19 198023617 Configuration file is unusable......................................................... 4-16

4.20 198003138 Board FLASH faults ...................................................................... 4-17

4.21 198003394 Start daylight saving time .............................................................. 4-18

4.22 198003395 End daylight saving time................................................................ 4-18

4.23 198025664 Abnormal Half-Fixed Connection Changes ..................................... 4-19

4.24 198005441 Port status on internal media plane changed .................................. 4-20

XIV


4.25 198005448 485 seriel bus link between CLKG/PWRD and OMP is broken......... 4-21

4.26 198026176 Clock reference changed............................................................... 4-22

4.27 198026177 CLKG reference quality changed ................................................... 4-22

4.28 198026178 Clock work mode changed ............................................................ 4-23

4.29 198026179 Clock source invalidation reason changed ...................................... 4-23

4.30 198005705 MCU resets abnormally ................................................................. 4-24

4.31 198005710 The result of manual reference selection for SETS chip................... 4-25

4.32 198005711 Clock reference selection is being executed.................................... 4-25

4.33 198005712 The manual select base will be run, please wait for the result .......... 4-26

4.34 198005713 APC chip's peripheral RAM has hardware fault ............................... 4-27

4.35 198005715 PP2S source switched .................................................................. 4-27

4.36 198005718 Two master clock ports is directly connected .................................. 4-28

4.37 198005700 DSP resets for abnormities............................................................ 4-28

4.38 198005701 Version Load Error ........................................................................ 4-29

4.39 198019777 APS switch over occurred.............................................................. 4-30

4.40 198005188 UIM CS Changeover ..................................................................... 4-31

4.41 198005189 Notification of Active/Standby Changeover .................................... 4-32

4.42 198005192 Board's Work Mode Unsupported................................................... 4-33

4.43 198005193 Notification of the power on status of the basic process................... 4-34

4.44 198005956 Board Version Error ...................................................................... 4-35

4.45 198005958 IDE Version Files Synchronization Information................................ 4-35

4.46 198005961 OMP Version Check Information .................................................... 4-36

4.47 198005962 Patch version operate fail .............................................................. 4-37

4.48 198011840 M3UA user office status change..................................................... 4-38

4.49 198013888 ASP status changed ..................................................................... 4-38

4.50 198013889 AS status changed........................................................................ 4-39

4.51 198013890 Sigtran error message received ..................................................... 4-40

4.52 198013891 Sigtran notification message received ............................................ 4-41

4.53 198013892 Allocate memory fail...................................................................... 4-42

4.54 198014144 Association establishment failed .................................................... 4-42

4.55 198014145 Association restart ........................................................................ 4-43

4.56 198005195 Board mix plug occurred................................................................ 4-44

4.57 198031040 ACL config failed .......................................................................... 4-45

4.58 198105001 Failed to get the table of configuration ............................................ 4-46

4.59 198105002 The route table is overloaded ........................................................ 4-48

4.60 198105003 Failed to handle DHCP message from other network ...................... 4-49

4.61 198105004 Failed to operate multicast group .................................................. 4-50

XV


4.62 198105005 Clock difference of slave is large.................................................... 4-51

4.63 198105006 Slave losted external clock ............................................................ 4-52

4.64 198105008 Bandwidth automatic adjustment is useless .................................... 4-53

4.65 198105018 Unable to save Performance File ................................................... 4-54

4.66 198105019 SLAVE memory check fail notification............................................. 4-55

4.67 198105030 OMP received data is not complete................................................ 4-56

4.68 198105032 Transport Path Occupied BandWidth Overload ............................... 4-57

4.69 198105033 Transport Path group Occupied Bandwidth Overload ...................... 4-58

4.70 198018755 HDLC status changed ................................................................... 4-59

4.71 198021329 LSDB Overflow............................................................................. 4-60

4.72 198021330 Configuration of OSPF mismatched ............................................... 4-61

4.73 198021331 Failed to add the ospf route to the courier routing table ................... 4-61

4.74 198028231 Router ID not configured for OSPFv3 ............................................. 4-62

4.75 198028233 Configuration of OSPFv3 Mismatched............................................ 4-63

4.76 198021837 Failure in adding dynamic routings ................................................. 4-63

4.77 198021059 RIP Neighbor Configuration Errors ................................................. 4-64

4.78 198021060 RIP Interface Authentication Errors ................................................ 4-65

4.79 198021065 Incompatible RIP Version Number ................................................. 4-66

4.80 198022598 Routers with Conflicting System Id Exist in Network ........................ 4-66

4.81 198022599 ISIS Message Authentication Failure.............................................. 4-67

4.82 198021584 Neighbor Hold Timer Expired......................................................... 4-68

4.83 198021585 BGP Interface Down and Neighbor Link Broken.............................. 4-69

4.84 198029760 DNS server inaccessible ............................................................... 4-70

4.85 198016193 SIG_IPI Forwards Service Messages Abnormally ........................... 4-70

4.86 198005702 Trunk configuration is inconsistent with function of board................. 4-71

4.87 198005708 The active/standby modules of PSN clock have changed oversuccessfully ................................................................................................... 4-72

4.88 198005714 No external clock for DSP.............................................................. 4-72

4.89 198005194 Changeover of CS Optical Interfaces ............................................. 4-73

4.90 198005960 Version Fails to Be Switched ......................................................... 4-74

4.91 198087360 BCCH Exchange Fail .................................................................... 4-74

4.92 198087393 Ring state notification ................................................................... 4-76

4.93 198087394 Intelligent power up/down preparation notification ........................... 4-76

4.94 198087459 cell no gprs traffic inform ............................................................... 4-77

4.95 198087469 abis route change inform ............................................................... 4-77

4.96 198087353 NSVC deletion notification ............................................................. 4-78

4.97 198087395 SNS Size process failure notification .............................................. 4-79

4.98 198087396 SNS Config process failure notification........................................... 4-79

XVI


4.99 198087466 NSVC's IP deletion notification....................................................... 4-80

4.100 198087359 No access of BSC to MSC SPC................................................... 4-81

4.101 198087503 Baseband frequency hopping exchange for trx fail ........................ 4-81

4.102 198087504 Baseband frequency hopping exchange for trx restore .................. 4-82

4.103 198087508 Block Successfully After Service released .................................... 4-83

4.104 198087751 dbsapp no avilable PCU resource inform ...................................... 4-84

4.105 198087754 Board back up ........................................................................... 4-84

4.106 198087760 BTS master power recover notification ......................................... 4-85

4.107 198087761 BTS master power interruption notification.................................... 4-86

4.108 198087762 After BTS mains power failure TRX terminated notification ............ 4-86

4.109 198087772 Super Site Connect in ................................................................. 4-87

4.110 198087799 Cell intelligent power-on or power-down........................................ 4-88

4.111 198087514 TRAU frame sync loss notification ................................................ 4-88

4.112 198087515 BCCH Exchange Success ........................................................... 4-89

4.113 198087516 Mute call detect........................................................................... 4-89

4.114 198087519 Release dynamic association by force .......................................... 4-90

4.115 198087520 Gb interface throughput exceed permissible value......................... 4-91

4.116 198087338 TRX No Traffic ............................................................................ 4-92

4.117 198087434 Cannot detect up or down TRAU notification ................................. 4-92

4.118 198087339 BTS self maintenance inform ....................................................... 4-93

4.119 198087477 site board cpu overload ............................................................... 4-93

4.120 198087478 uplink user layer jam inform ......................................................... 4-94

4.121 198087479 downlink user layer jam inform..................................................... 4-95

4.122 198087488 chp cycle adjust trau information .................................................. 4-95

4.123 198087500 Radio Interface Synchronization ARF emendate Successfully........ 4-96

4.124 198087501 Radio Interface Synchronization ARF emendate Failed ................. 4-96

4.125 198087502 Site IP Address conflicted............................................................ 4-97

4.126 198087512 IDS Attack detecting.................................................................... 4-98

Appendix A Link Information ................................................................... A-1A.1 A2051 ...............................................................................................................A-1

Glossary .......................................................................................................... I

XVII


This page intentionally left blank.

XVIII


About This ManualPurpose

This manual describes how to handle ZXG10 iBSC alarms and notifications.

Intended Audience

This manual is intended for:

l Maintenance engineersl On-duty staff in equipment room

What Is in This Manual

This manual has the following chapters:

Chapter Description

1, Overview Gives an overview of ZXG10 iBSC alarms and notifications.

2, General Operations Describes the common operations for alarm handling.

3, Alarms Describes the alarms in terms of alarm properties, causes, impact,

and Action.

4, Notifications Describes the notifications in terms of notification properties, causes,

impact, and Action.

Appendix A Link Information Describes the complex operations for alarm handling.

I



II


Chapter 1OverviewFunctions of Fault Management

The fault management system collects fault information from all the NEs in the managednetwork in near real-time, such as boards, links, databases, and servers, and thendisplays the collected fault information in the format of alarm or notification. The faultmanagement system helps the system administrator quickly locate and resolve faultsin the managed network. It also provides telecom operators, network managementdepartments, and equipment vendors with correct and timely alarm data to ensure stablenetwork operations.

Fault Indication

The fault management system indicates a fault or event occurring in the network in theform of alarm or notification.

l A fault is indicated in the form of alarm when it persists and affects the reliabilityand services of the system. An alarm will be cleared only after the fault is resolved.Immediate troubleshooting is required when alarms occur.

l A notification indicates a non-repeatable or instantaneous fault or event in thesystem, for example, board reset and signaling overload. Such a fault or event isnormally caused by a sudden environment change or other accidental factors. Nospecial handling is required because the fault or event causing a notification can beautomatically handled by the system. However, a frequently-reported notificationrequires troubleshooting.

Alarm Format

The alarms defined for the ZXG10 iBSCare provided with the information such as propertyand possible causes. For details, refer to Table 1-1.

Table 1-1 Alarm Format Description

Item Description

Code Uniquely identifies an alarm.

Name Summarizes the fault information, such as the fault cause and phenomenon.

1-1


ZXG10 iBSC Alarm and Notification Handling Reference

Item Description

Severity There are four alarm severity levels, which are indicated in descending order

of severity as Critical, Major, Minor, and Warning.

l Critical: indicates a fault that causes failures of system operations or

service capabilities. Immediate troubleshooting is required when a critical

alarm is reported.

l Major: indicates a fault that seriously impacts proper system operations or

reduces service capabilities. Clearing the fault to restore the system as

soon as possible is required when a major alarm occurs.

l Minor: indicates a fault that slightly influences proper system operations or

reduces service capabilities. Proper measures should be taken to clear

the fault in a timely manner and prevent the occurrence of more severe

alarms when a major alarm occurs.

l Warning: indicates a fault that has a potential or gradual impact on proper

system operations or service capabilities. Warning messages need to

be analyzed and proper measures should be taken to clear the fault in a

timely manner and avoid more severe alarms.

l Unknown: indicates a fault that severity is defined by users.

The impact degree described in the definition of alarm severity refers to the

impact on a single index, for example, reliability or security. Once the impact

on any index reaches the specified threshold, the severity level of the alarm

can be roughly determined. If an alarm has an impact on multiple indices, its

severity level should be escalated accordingly.

Type Based on the triggering condition and system impact, alarms can be classified

into the following five types:

l Equipment alarm: related with equipment hardware faults.

l Communication alarm: related with information transmission faults (ITU-T

Recommendation X.733).

l Processing error alarm: related with software or processing faults (defined

in ITU-T Recommendation X.733).

l Environment alarm: related with the environment where the equipment is

located (defined in ITU-T Recommendation X.733).

l QoS alarm: related with equipment operation performance or indexes.

Alarm Description Describes how the alarm is triggered.

Alarm Cause Provides probable alarm causes to help users troubleshoot, find preventive

measures, and restore the system to normal state in a timely manner.

Impact Provides the consequence of each alarm and the impact on the system and

services.

1-2


Chapter 1 Overview

Item Description

Action Provides the troubleshooting steps and suggestions.

During the alarm handling process, the following tips needs your attention:

l After recording the fault information, O&M personnel needs to handle the

fault step by step as suggested. If there is no otherwise specified and the

fault is solved (that is, alarm is cleared), the alarm handling process ends.

If the fault persists, go to the next step.

l If fault cannot be removed, contact the local ZTE office.

Notification Format

The notifications defined for the ZXG10 iBSC are provided with the information such asproperty and possible causes. For details, refer to Table 1-2.

Table 1-2 Notification Format Description

Item Description

Code Uniquely identifies a notification.

Name Summarizes the event information, such as the cause and phenomenon.

Severity There are two alarm severity levels, which are indicated in descending order of

severity as Major, and Minor.

l Major: indicates a fault that seriously impacts proper system operations or

reduces service capabilities. Clearing the fault to restore the system as

soon as possible is required when a major alarm occurs.

l Minor: indicates a fault that slightly influences proper system operations or

reduces service capabilities. Proper measures should be taken to clear

the fault in a timely manner and prevent the occurrence of more severe

alarms when a major alarm occurs.

The impact degree described in the definition of notification severity refers

to the impact on a single index, for example, reliability or security. Once the

impact on any index reaches the specified threshold, the severity level of the

notification can be roughly determined. If a notification has an impact on

multiple indices, its severity level should be escalated accordingly.

Type The notification types are the same as the alarm types.

Notification

Description

Describes how the notification is triggered.

Notification Cause Provides probable notification causes to help users troubleshoot, find

preventive measures, and restore the system to normal state in a timely

manner.

Impact Provides the consequence of each notification and the impact on the system

and services.

1-3



Item Description

Action Provides the troubleshooting steps and suggestions.

During the alarm handling process, the following tips needs your attention:

l After recording the fault information, O&M personnel needs to handle the

fault step by step as suggested. If there is no otherwise specified and the

fault is solved (that is, alarm is cleared), the alarm handling process ends.

If the fault persists, go to the next step.

l If fault cannot be removed, contact the local ZTE office.

1-4


Chapter 2General OperationsTable of Contents

Finding the Managed Objects Through an Alarm Object.............................................2-1Filtering Controller Alarms ........................................................................................2-10

2.1 Finding the Managed Objects Through an AlarmObject

On the EMS, based on the key information of an alarm object, you can find the managedelements and check their attributes (configuration parameters).

Key information of an alarm object:

l Subnet and NE informationl Alarm MO information (contained in the alarm details), including:

à Alarm object MOC

à Alarm object DN

à Alarm object name, which is user-defined

Related managed objects:

l Configuration objectl Parent objectl Sub-objectl Referring objectl Referred object

2.1.1 Querying the Configuration ObjectThis procedure takes the configuration object “Adjacent Office Information (RemoteSp)”as an example to describe how to query related configuration objects of an alarm object.

Key information of the alarm object is as follows:

l Alarm object MOC=REMOTESPl Alarm object DN=TransportNetwork=1,Ss7=1,LocalSp=1,RemoteSp=1l Subnet and NE information: SubNetwork=1333,MEID=1333

The complete DN information that can be used for checking or modifying the configurationdata is as follows:

2-1



SubNetwork=1333,MEID=1333,ConfigSet=n,TransportNetwork=1,Ss7=1,LocalSp=1,RemoteSp=1

Where:

l ConfigSet=0 indicates that the data is in the modification area (used for modifying NEconfiguration data).

l ConfigSet=1 indicates that the data is in the snapshot area (used for checking NEconfiguration).

Steps

l Querying configuration objects through the GUI

1. From the navigation tree in the Configuration Management window, selectSnapshot Area under the NE node, see Figure 2-1.

Figure 2-1 Selecting the Snapshot Area

2. In the search box, enter the object type name Adjacent Office Information, andclick . See Figure 2-2.

Figure 2-2 Querying the Object Type

2-2


Chapter 2 General Operations

The Adjacent Office Information-List tab is displayed in the right pane.

3. Find the configuration object in the list.

You can set conditions to quickly find the object, for example, select DN as thematching condition, like as the matching algorithm, and TransportNetwork=1 asthe matching value, see Figure 2-3.

Figure 2-3 Querying the Configuration Object

4. Double-click a configuration object and view its attributes in the displayed tab, seeFigure 2-4.

Figure 2-4 Attributes of a Configuration Object

l Querying configuration objects through the MML

1. In the navigation tree of the MML Terminal, select Configuration Management> Query Managed Object, see Figure 2-5.

Figure 2-5 Selecting the Command Type

2. Enter the command QUERY:MOC="RemoteSp",MOI="SubNetwork=1333,MEID=1333,ConfigSet=1,TransportNetwork=1,Ss7=1,LocalSp=1,RemoteSp=1"; toquery the managed object.

2-3



Note:

The configuration object MOC is case sensitive.

The command result is as follows:

– End of Steps –

2.1.2 Querying the Parent Object of a Configuration ObjectThis procedure takes the “No.7 Signalling Configuration(Ss7)” parent object as an exampleto describe how to query the configured parent object through the alarm object information.


l Alarm object MOC=REMOTESPl Alarm object DN=TransportNetwork=1,Ss7=1,LocalSp=1,RemoteSp=1l Subnet and NE information SubNetwork=1333,MEID=1333

Therefore, the DN information of “No.7 Signalling Configuration(Ss7)” is DN=TransportNetwork=1,Ss7=1.


SubNetwork=1333,MEID=1333,ConfigSet=1,TransportNetwork=1,Ss7=1.

Steps

l Querying the parent object through the GUI


2-4



Figure 2-6 Selecting the Snapshot Area Node

2. In the search box, enter the object type name 7 Signalling Configuration, andclick . See Figure 2-7.


The No.7 Signalling Configuration-List tab is displayed in the right pane


You can set conditions to quickly find the object, for example, select DN as thematching condition, like as the matching algorithm, and TransportNetwork=1 asthe matching value, see Figure 2-8.


2-5



4. Double-click the configuration object. Its attributes are shown the displayed tab,see Figure 2-9.

Figure 2-9 Attributes of the Configuration Object

l Querying the parent object through MML



2. Enter the command QUERY:MOC="Ss7",MOI="SubNetwork=1333,MEID=1333,ConfigSet=1,TransportNetwork=1,Ss7=1"; to query the managed object.



2.1.3 Querying the Referring Object of a Configuration ObjectThis procedure takes the referring object “Signalling Linkset (Sls)” of the configurationobject “Mtp3 Route (Mtp3Route) as an example to describe how to query the referringobject through the alarm object information.

2-6



Key information of the alarm object:

l MOC=M3UAROUTEl Alarm object DN=TransportNetwork=1,Ss7=1,M3uaRoute=1l Subnet and NE information: SubNetwork=1333,MEID=1333


SubNetwork=1333,MEID=1333,ConfigSet=1,TransportNetwork=1,Ss7=1,Mtp3Route=1

Steps

l Querying the referring object through the GUI


Figure 2-11 Selecting the Snapshot Area Node

2. In the search box, enter the object type name Mtp3 Route, and click , SeeFigure 2-12.

2-7




The Mtp3 Route-List tab is displayed in the right pane.


You can set conditions to quickly find the object, for example, select DN as thematching condition, like as the matching algorithm, and Mtp3Route=1 as thematching value, see Figure 2-13.


4. Double-click the configuration object. Its attributes are shown the displayed tab,see Figure 2-14.

Figure 2-14 Attributes of the Configuration Object

2-8



5. Click Used signalling linkset 1. The linked Signalling Linkset-List tab isdisplayed, see Figure 2-15.

Figure 2-15 Locating the Signaling Link Set

Check the information of the signaling link set (Sls).

l Querying the referring object through the MML



2. Enter the command QUERY:MOC="Mtp3Route",MOI="SubNetwork=1333,MEID=1333,ConfigSet=1,TransportNetwork=1,Ss7=1,Mtp3Route=1"; to query themanaged object.


3. Drag the horizontal scroll bar to the right and view the Used signalling linkset 1information.

4. According to the signaling link group information, enter the commandQUERY:MOC="Sls",MOI="SubNetwork=1333,MEID=1333,ConfigSet=1,TransportNetwork=1,Ss7=1,LocalSp=1,RemoteSp=1,Sls=1"; to query the referring object.



2-9



2.2 Filtering Controller AlarmsIn the network management system, specific conditions can be set to filter alarms duringa query of active or historical alarms.

You can query the required alarms by:

l Selecting the corresponding board where the alarms are raised directly on the rackdiagram.

l Entering the location information of the board where the alarms are raised, includingthe rack, shelf, and slot information of the board.

l Entering the office information in the alarms.

2.2.1 Checking Board Alarms Through the Rack DiagramThe rack diagram displays the board configuration and the alarms at each severity levelon each slot.

This section describes how to check the board alarms through the rack diagram.

Steps

1. Right-click the faulty NE, and select Open Diagram from the shortcut menu.

The board where the alarm is generated blinks in the color corresponding to the alarmseverity. For details, refer to the following table.

Alarm Color Severity

Critical

Major

Minor

Warning

2. In the Rank Chart, right-click the faulty board, and select Show Active Alarm fromthe shortcut menu, see Figure 2-17.

2-10



Figure 2-17 Selecting the Show Active Alarm Command Item

The Show Active Alarm dialog box is displayed.

3. Double-click an alarm, and view the alarm details and handling suggestions.


2.2.2 Filtering Alarms Based on Alarm LocationThis procedure takes the “Port trunk failed(199007168)” alarm as an example to describehow to filter controller alarms based on the alarm location.


Location: EQRNCID=1,RACKNO=1,SHELFNO=2,SLOTNO=18,CPUNO=1.

Steps

l Querying alarms through the GUI

1. On the Location tab, select the NE Type of the controller, see Figure 2-18.

Figure 2-18 Selecting the NE Type

2-11



2. Select the board where the alarm is generated, see Figure 2-19.

Figure 2-19 Selecting the Board

3. Switch to the Alarm Code tab, and select Port trunk failed(199007168), seeFigure 2-20.

Figure 2-20 Selecting the Alarm Code

4. Click OK. The query result is displayed, see Figure 2-21.

Figure 2-21 Alarm Query Result

l Querying alarms through MML

2-12



1. In the navigation tree of the MML Terminal, select Fault Management > ShowActive Alarm, see Figure 2-22.


2. Enter the command SHOW CURRENT ALARM:POSITION="urop:OMMOID=hnfwvxgt-1@sbn=4@me=4",ALARMCODE="199007168",ISVISIBLE=TRUE,SYSTEMTYPE=20421,SUBPOSITION1="EQRNCID=1,RACKNO=1,SHELFNO=2,SLOTNO=18,CPUNO=1"; to query the current alarms.



2.2.3 Querying Alarms by Office InformationThe information of an office includes “Site Name (Office)” and “Site ID (Office)”.

This procedure describes how to query alarms in accordance with the information of anoffice, for example, “Site ID (Office): 3005”.

Context

If the office information is available in the alarm details, you can view the office informationby either of the following two methods:

l Alarm list

The office information is available in the corresponding columns in the alarm list, seethe following figure:

2-13



l Additional information

The office information is available in the Additional Information area on the Detailtab, see the following figure:

Steps

l Fuzzy query

1. On the Others tab, select Remark(Fuzzy Match), and enter 3005 in the text box,see Figure 2-23.

2-14



Figure 2-23 Entering the Office Information for Alarm Query

2. Click OK. The queried alarm is displayed on the query result tab, see Figure 2-24.

Figure 2-24 Query Result

l Advanced query

1. On the Others tab, click Advanced. The Advanced dialog box is displayed.

2. On the Additional Information tab, enter 3005 in the Site ID(Office) text box,see Figure 2-25.

Figure 2-25 Entering the Site ID

3. Click OK. The queried alarm is displayed on the query result tab, see Figure 2-24.


2-15




2-16


Chapter 3AlarmsTable of Contents

Equipment Alarm........................................................................................................3-1Communication Alarm ............................................................................................3-240Processing error Alarm...........................................................................................3-279QoS Alarm .............................................................................................................3-295Environment Alarm.................................................................................................3-310

3.1 Equipment Alarm

3.1.1 198019456 All high-speed links between line card andswitching boards are out of synchronization

Alarm Information

Code: 198019456

Name: All high-speed links between line card and switching boards are out of

synchronization

Severity: Critical

Type: Equipment alarm

Alarm Description

All HSSLS between line card and switching boards are out of synchronization

Alarm Cause

1. The configuration of the PSN type is inconsistent with the actual used of PSN type

2. PSN hardware is abnormal.

3. GLI/TLIV hardware is faulty.

3-1



Impact

1. All services on the equipment are down if the alarm is caused by Cause 1 or Cause 2.

2. All services on the line card are affected if the alarm is caused by Cause 3. If the service is not

configured in master/slave or load sharing mode, all services on the line card will be down. If the

service is configured in master/slave or load sharing mode, all services on the line card will soon be

restored after being down temporarily.

Action

1. Check whether PSN board reboots repeatedly. If yes, Check whether the PSN board type

configured is consistent with the PSN board type actually in use.

If inconsistent (for example, the configured board type is PSN4V and the board type actually in use is

PSN8V), modify board type configuration or replace the board actually in use to keep consistency

between board configuration and the board in use.

If consistent, PSN board hardware might be faulty. In this case, replace PSN board.

2. If the alarm occurs in line card, check if the same alarm occurs in other line card(s) located in the

same shelf with the faulty line card.

If the same alarm occurs in all other line cards, PSN board might be faulty. Reboot PSN board and

check if the line card alarms are restored. If alarms are not restored, replace PSN board.

If merely the line card where this alarm occurs reboots repeatedly, replace the board where the

alarm is generated.

3.1.2 198019465 CSIX RX and TX packets is abnormal

Alarm Information

Code: 198019465

Name: CSIX RX and TX packets is abnormal

Severity: Warning


Alarm Description

CSIX RX and TX packets is abnormal, the number of error packets exceeds the threshold

Alarm Cause

1. Signal is unstable when rack or board is powering on.

2. Switch chip is abnormal.

Impact

The transceiver of the media plane is exceptional.

3-2


Chapter 3 Alarms

Action

1. Reset the board.

2. Replace the board.

3.1.3 198029952 802.3ah link fault

Alarm Information

Code: 198029952

Name: 802.3ah link fault

Severity: Major


Alarm Description

Link Fault: The physical layer has determined a fault that occurred in the receive direction of the

local DTE

Dying Gasp: An unrecoverable local failure condition has occurred

Critical Event: An unspecified critical event has occurred

Alarm Cause

Link Fault: The physical layer has determined a fault that occurred in the receive direction of the

local DTE

Dying Gasp: An unrecoverable local failure condition has occurred

Critical Event: An unspecified critical event has occurred

Impact

Link Fault:

The port can't receive data, the operations will interrupt.

Dying Gasp:

The port can't receive data, the operations will interrupt.

Critical Event:

The 802.3ah is failed, can't detect the fault of link.

3-3



Action

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:

Check the peer is or not down.

Critical Event:

1. Check the 802.3ah is or not enable, if it is disable, it can't receive PDU.

2. If the 802.3ah is enable, if the port is optical, check the alarm of Link Fault 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 the alarm is alive, change the peer board.

3.1.4 198030208 Fault alarm of CFM

Alarm Information

Code: 198030208

Name: Fault alarm of CFM

Severity: Minor


Alarm Description

Fault alarm of CFM

Alarm Cause

DefXconCCM:

The MAID of the received CCM dose not exactly match the MAID configured in the receiving MEP.

DefErrorCCM:

1. The MEPID in the received CCM is not configured in the receiving MEP.

2. The MEPID in the received CCM matches the MEPID of the receiving MEP.

3. The CCM interval filed in the received CCM dose not match the configured for the receiving MEP.

4. The source mac of CCM is not match the mac of rmep's configured .

DefRemoteCCM:

The MEP is not receiving CCM in timeout.

DefRDICCM:

The MEP is receiving CCM that have the RDI.

AIS:

The MEP is receiving AIS.

3-4


Chapter 3 Alarms

LCK:

The MEP is receiving LCK.

Impact

DefXconCCM:

The configure of MD is error.

DefErrorCCM:

The configure of MEP in MA is error.

DefRemoteCCM:

1. the other mep is not enable.

2. the link is fault, mep can't receive PUD.

DefRDICCM:

The receive of the last MEP is error.

AIS:

The receive of the former MEP is error.

LCK:

The receive of the former MEP is error.

Action

DefXconCCM:

Check the configure of the peer MD.

DefErrorCCM:

Check the configure of all MEP in MA.

DefRemoteCCM:

1. Check the fault of the link

2. Check the other MEP in MA is enabled or not.

DefRDICCM:

Check the alarm of the last MEP.

AIS:

Check the alarm of the former MEP.

LCK:

Check the alarm of the former MEP.

3.1.5 198005633 Hard disk is faulty

Alarm Information

Code: 198005633

Name: Hard disk is faulty

Severity: Major


3-5



Alarm Description

Hard disk is faulty

Alarm Cause

The ribbon cable is loose or the hard disk fails, usually a hardware failure.

Impact

This is an OMP alarm caused by hard disk breakage, which will affect the system in three ways:

1. The OMP can not boot and services can not access the board.

2. If the log server is abnormal, performance data temporarily stored in the hard disk of the OMP

will be lost.

3. No peripheral board can be powered on because when a peripheral board boots, it will request

for a version from the OMP.

Action

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

3.1.6 198005635 The board is not plugged firmly

Alarm Information

Code: 198005635

Name: The board is not plugged firmly

Severity: Major


Alarm Description

ENUM is open

Alarm 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 within 3 seconds.

Impact

The active/standby board changeover or the APS changeover will fail. This board can not be

switched to the active board.

3-6


Chapter 3 Alarms

Action

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 key on the standby board twice within

3 seconds, press the EXCH key on the standby board twice within 3 seconds.

3.1.7 198005639 High Error Rate of Optical Interface

Alarm Information

Code: 198005639

Name: High Error Rate of Optical Interface

Severity: Major


Alarm Description

The rate of error code in a fiber is high.It is adventive

Alarm Cause

The fiber is not completed connected to the port, or is damaged, or is not compatible with the optical

transceiver module in T-network switch. There is no light signal input into the optics module.

This alarm is dedicated to the TDM optical port only. The possible causes of this alarm include:

1. TDM receiver fiber optics failure, fiber optics module failure.

This type of failures include: damaged fiber on the receiver, unconnected fiber, contaminated fiber or

damaged optics module on the receiver.

2. Fiber optics failure at the transmitting module on the corresponding TDM.

This type of failures include: damaged fiber on the transmitter, unconnected fiber, and contaminated

fiber.

3. Compatibility between fiber optics and optics module.

The fiber transmission rate of TDM signal is incompatible with the wave length of the optics module.

4. Loss of signal (LOS) alarm operation is performed on the corresponding SDH device.

This includes the manual diagnosis test alarm operation.

Impact

There might be error in the data transmitted by the optical port which affects the quality of all the

services performed on this optical port.

3-7



Action

1. Perform loopback test to determine source of this alarm is on the local devices or the corresponding

devices. Perform self-loop test on local device. If the failure persists, the failure source is on local

device; if the failure disappears after self-loop test, 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.


3.1.8 198005640 FPGA exception

Alarm Information

Code: 198005640

Name: FPGA exception

Severity: Major


Alarm Description

FPGA is abnormal, it happens only once

Alarm Cause

FPGA runs abnormally, for example, FPGA is lost, or the board clock is lost.

Impact

The FPGA verification will fail.

The FPGA can not provide normal reading and writing functions.

The board can not work normally or provide all of its functions.

Services borne on the board will be interrupted.

Action

1. Restart the board. In this case, the board downloads FPGA again.


3-8


Chapter 3 Alarms

3.1.9 198005644 The channel in a sub card is down

Alarm Information

Code: 198005644

Name: The channel in a sub card is down

Severity: Major


Alarm Description

The channel in a subcard is down

Alarm Cause

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

2. The sub-card has hardware faults.

Impact

The sub-card channel is not initialized or the initialization fails. As a result, the channel corresponding

to the alarm chip cannot be used normally. This affects the service carried by the board of the

sub-card. After the channel is available and the alarm is eliminated, the service is recovered.

Action

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

2. Replace the sub-card.

3.1.10 198005645 Sub card abnormal

Alarm Information

Code: 198005645

Name: Sub card abnormal

Severity: Minor


Alarm Description

Subcard abnormal

3-9



Alarm Cause

1. The GCS, EC or HPS subcard of UIMC/GUIM/CHUB is not inserted in position.

2. The subcard is faulty.

Impact

UIMC/GUIM/CHUB GCS sub-card functions abnormally. Packets may be lost, and even worse, link

disconnection may occur on the control planes of some boards. For active/standby configuration,

there are two cases:

1. If the active board is abnormal while the standby board is normal, the system performs

active/standby switchover. Thus, the standby board takes over the services of the faulty active

board. In this case, the service is not affected.

2. If both the active and standby boards are abnormal, active/standby switchover is forbidden. In this

case, the service is interrupted because the faulty board cannot restore to the normal status.

Action

1. Check the sub-card connection on the board. If the sub-card is loosely inserted, tightly insert it and

wait for the board to be powered on.

2. Replace the sub-card.

3.1.11 198005646 Phase-lock loop unlocked

Alarm Information

Code: 198005646

Name: Phase-lock loop unlocked

Severity: Critical


Alarm Description

Phase-lock loop unlocked

Alarm Cause

1. Clock board faulty.

2. Reference clock has changed to another optical board.

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

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

3-10


Chapter 3 Alarms

Impact

The service clock and system clock are inconsistent on the board with unlocked phase-lock loop. As

a result, the service carried by the board is interrupted.

Action

1. On NMS fault management interface, check if the related clock alarm occur. If yes, handle the

alarm by referring to the corresponding suggestions.

The related alarm is as follows:

198005381 Input Clock Abnormal

2. On NMS fault management interface, check if related alarms occur on the optical port for clock

extraction. If yes, handle the alarm by referring to the corresponding suggestions.

The related alarms are as follows:

198001792 SDH/SONET fault

198005639 High Error Rate of Optical Interface

198000002 Loss of Optical Transceiver Module Signal

3. Check the operation and maintenance logs. If the operation of changing the clock extraction

reference for the loop is recorded, report the alarm as a normal phenomenon. In this case, no

handling operation is required.

4. Switch to the standby clock board.

5. Switch to the standby UIM/GUIM board.


3.1.12 198005647 High BER on E1 link

Alarm Information

Code: 198005647

Name: High BER on E1 link

Severity: Major


Alarm Description

High error code happens in the trunk link

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

3-11



Impact

The trunk fails to receive trunk signals. If the belonged port has only this link, all services on the port

are interrupted. Otherwise, only the port bandwidth is affected. The quantity of upper layer access

services associated with the port is decreased. The accessed bandwidth is reduced. The service,

however, is not interrupted.

Action

1. Conduct a meter measurement or loopback test to find out whether the alarm is rooted in the

local end or peer end.

Meter measurement: Connect a trunk test meter to check if the signal received by the local end trunk

is normal. If yes, the fault is rooted in the local end. If the test shows the problem persists, the fault is

rooted in the peer end. In this case, inform the peer end to troubleshoot.

Loopback test: Perform self-loop at the trunk where alarm occurs at local end. If the problem persists,

it indicates that the fault is rooted in the local end. If the alarm is eliminated, it indicates that the alarm

is rooted in the peer end. In this case, inform the peer end to troubleshoot.

2. Replace the trunk cable.


3.1.13 198005656 Input clock of subcard lost

Alarm Information

Code: 198005656

Name: Input clock of subcard lost

Severity: Major


Alarm Description

Input clock of subcard is lost

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

3-12


Chapter 3 Alarms

Impact

The unavailable sub-card clock affects the normal operation of the board. This may cause clock

jittering, and the service that implements media stream exchange through this board becomes

unstable. In the most serious case, the system clock is lost and the service carried by the board is

interrupted.

Action

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

on again.

2. Replace the subcard


3.1.14 198005663 Component fault

Alarm Information

Code: 198005663

Name: Component fault

Severity: Major


Alarm Description

Board device or subcard is abnormal

Alarm Cause

Devices or sub-cards on the board operate abnormally.

Impact

This alarm only occurs to the IMAB. When it occurs, the IMAB can not operate normally and the trunk

borne on the board will be broken. As a result, users can not access the board and the existing

services will be interrupted.

Action

1. Check whether the 'Board input clock lose' or 'PLL unlock' alarm exists. If so, handle the alarm first.


3-13



3.1.15 198005665 Fault on board (GPS)

Alarm Information

Code: 198005665

Name: Fault on board (GPS)

Severity: Critical


Alarm Description

Clock board or GPS module report hardware error

Alarm Cause

According to alarm details, alarm status falls into two types:

Type A fault on board (GPS) phase-lock equipment (Probable alarm causes include 16chip loss/out

of lock, 12.8M loss/out of lock, PP2S output loss, 8K output loss, 10M output loss, and 1PPS loss).

Phase-lock equipment of this board (GPS) is in power on status (alarm cause is that the GPS module

of ICM board is in power on status, and power on has not been completed).

Impact

Be usually determined as hardware fault, which affects system clock. It might lead to the system

clock loss and system synchronization failure.

When system clock loss/offset occurs, its subsequent impact on service is described below.

1.For TDM transmission, all links based on the TDM transmission medium (including the transmission

link currently in service for UE and cell transmission link) are affected. Packet loss might occur on

these links, leading to degradation of service quality. In the case of serious packet loss, service

interruption and handover failure will occur. Even worse, the cell might be out of service.

2.For non-TDM transmission (for example, IP transmission), Iub interface service is affected, while

Iur interface and Iu interface services are not affected. The clock that Node B derives from RNC

via IEEE1588 is inaccurate.

When RNC clock frequency offset is no more than 0.05 ppm, Node B synchronization will not fail, but

success rate of inter-RNC inter-Node B soft handover might fall.

When RNC clock frequency offset exceeds 0.5 ppm, Node B will fail to lock the clock. In this case,

Node B will oscillate freely and success rate of inter-Node B soft handover might fall.

3-14


Chapter 3 Alarms

Action

On NMS fault management interface, view alarm Details where Error type information is given.

Locate the corresponding alarm handling suggestion according to the error type.

The alarm handling suggestions that correspond to the error types 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 working

status of the GPS module. If Class A fault persists in the GPS module, replace the board.

2) Check if output clock loss occurs. If yes, replace the board.

2.Phase-lock Equipment of This Board (GPS) Is in Power-on Status

If the alarm persists, hardware fault might exist. Replace the board.

3.1.16 198000256 Ethernet link to OMC is broken.

Alarm Information

Code: 198000256

Name: Ethernet link to OMC is broken.

Severity: Minor


Alarm Description

Ethernet link down,only use for OMC and OMC2 now

Alarm Cause

1. No network cable is connected with Network Port OMC or OMC2 on rear board of OMP.

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

3. Network port on the board is faulty.

Impact

Master/slave switching will occur if OMP is configured in master/slave mode.

If master/slave switching is normal, system will not be affected.

If master/slave switching is abnormal, OMP board will fail to obtain version package from NMS,

leading to board power-on failure, UE access failure, and interruption of ongoing services.

Action

1. Ensure that the network cable connected to Network Port OMC or OMC2 is connected firmly

and correctly on the both end.

2. Unplug and plug the network cable on Network Port OMC or OMC2 of OMP board

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

3-15



3.1.17 198001284 The phase of 8K, 16K clock, input to backplaneboard, is not matched

Alarm Information

Code: 198001284

Name: The phase of 8K, 16K clock, input to backplane board, is not matched

Severity: Minor


Alarm Description

The phase of 8K, 16M clock, input to backplane board, is not matched

Alarm Cause

1. Clock cable is not properly connected.

2. Clock board is faulty.

Impact

The system fails to achieve synchronization so that the board can not work normally. As a result, UE

can not be accessed and services borne on the board are interrupted.

Action

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

2. Clock board changeover.

3. UIM/GUIM board changeover.

4. Replace the board which reported alarm.

3.1.18 198001286 Input clock of board lost

Alarm Information

Code: 198001286

Name: Input clock of board lost

Severity: Minor


Alarm Description

Input clock of board is lost

3-16


Chapter 3 Alarms

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

Impact

The board fails to synchronize with system clock so that it can not work normally. As a result, UE can

not be accessed and services borne on the board are interrupted.

Action

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

2. Check if the following alarm occurs in the board. If yes, refer to the corresponding alarm handling

suggestion.

Related alarm: 198005635 The board is not plugged firmly

3. Replace board.

3.1.19 198000002 Loss of optical signal

Alarm Information

Code: 198000002

Name: Loss of optical signal

Severity: Minor


Alarm Description

The optical module receives no optical signal

Alarm Cause

1. The receiving optical fiber/module of local equipment is faulty.

Receiving optical fiber is faulty or disconnected.

Optical connector is polluted.

Receiving optical module is faulty.

2. The transmitting optical fiber of opposite equipment is faulty.

Transmitting optical fiber is faulty or disconnected.


3. The receiving optical power at local end is excessively low.

Optical power attenuation on the receiving fiber transmission line at local end is too much.

Transmitting optical power at opposite end is too low.

3-17



4. Operation of LOS insertion is performed at opposite end.

Manual 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 fiber transmission rate and the optical module wavelength are incompatible.

Impact

The optical interface fails to work normally. If the optical interface is configured with APS protection,

service will be switched to protection optical interface. Otherwise, all services on the optical interface

will be down.

Action

1. Carry out loop test to determine whether the alarm is caused by local end or opposite end. Perform

fiber self-loop at local equipment. If the alarm persists, fault might lie in local equipment. If the alarm

disappears, inform the opposite end to troubleshoot.

2. Replace the optical module.

3. Replace fiber.

4. Replace board.

3.1.20 198001792 Loss of SDH transmission link

Alarm Information

Code: 198001792

Name: Loss of SDH transmission link

Severity: Major


Alarm Description

When the power of the receiving-optical signaling is lower than the sensitivity of the optical receiver,

the LOS alarm occurs. When the LOS alarm occurs, the board inserts "110" between bit 6 and bit 8

of the multiplexing section overhead (MSOH) K2 on the sending side, via, send the MS RDI to

each other.

3-18


Chapter 3 Alarms

Alarm Cause

The alarm occurs when the receiving optical power is below optical receiver sensitivity. Generally

speaking, normal receiving optical power range for optical modules is between -28 dBm and -8 dBm.

Optical signals within this range can be detected.

Probable causes for the alarm include:

1. The receiving optical fiber/module of local SDH equipment is faulty.

Receiving optical fiber is faulty or disconnected.


Receiving optical module is faulty.

2. The transmitting optical fiber of opposite SDH equipment is faulty.

Transmitting optical fiber is faulty or disconnected.


3. The optical transmission line of SDH equipment is faulty.

Tail fiber and flange between fiber distribution frame and the equipment at local end are faulty

or disconnected.

The related connector is in poor contact.

4. The receiving optical power at local end is excessively low.

Optical power attenuation on the fiber transmission line at receiving end is too much.

Opposite-end transmitting optical power is too low.

5. Operation of LOS insertion is performed at opposite end.

Manual operation of LOS insertion is performed in diagnostic test, and optical module is shutdown by

force.

6. Optical fiber and optical module is incompatible.

The fiber transmission rate of STM signals and the optical module wavelength are incompatible.

Impact

SDH/SONET fails to work normally, leading to UE access failure on SDH/SONET and interruption

of ongoing services.

Action

1. Use meter measurement or loop test to judge whether the alarm is caused by local end or

opposite end.

Meter Measurement

Use a SDH test meter or optical power meter to test whether the receiving optical signals at local end

are normal. If normal, fault might lie in local equipment. If abnormal, fault lies in opposite end or on

transmission side. Inform the opposite end or transmission side to troubleshoot.

Loop Test

Perform fiber self-loop at local SDH equipment. If the alarm persists, fault might lie in local equipment.

If the alarm disappears, inform the opposite end to troubleshoot.

If it is a local fault, go on with the following steps.

2. Replace optical module.

3. Replace optical fiber.

4. Replace board.

3-19



3.1.21 198001825 High BER on SDH / Sonet link

Alarm Information

Code: 198001825

Name: High BER on SDH / Sonet link

Severity: Warning


Alarm Description

SDH/SONET: SD(signal degrade)

Alarm Cause

1. Attenuation of receiving signals of local SDH equipment is large.

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.

Impact

SDH/SONET equipment can work. However, call loss or noise occurs to all voice services on this

optical path, and bit error occurs on the data service channel.

Action

1. Use meter measurement or loop test to judge whether the alarm is caused by local end or

opposite end.

Meter Measurement

Use a SDH test meter or optical power meter to test whether the receiving optical signals at local end

are normal. If normal, fault might lie in local equipment. If abnormal, fault lies in opposite end or on

transmission side. Inform the opposite end or transmission side to troubleshoot.

Loop Test

Perform fiber self-loop at local SDH equipment. If the alarm persists, fault might lie in local equipment.

If the alarm disappears, inform the opposite end to troubleshoot.

If it is a local fault, go on with the following steps.

2. Replace optical module.

3. Replace optical fiber.

4. Replace board.

3-20


Chapter 3 Alarms

3.1.22 198015874 Data traffic to PSN board is congested

Alarm Information

Code: 198015874

Name: Data traffic to PSN board is congested

Severity: Major


Alarm Description

A link level flow control occurred in 2400 during specified time and could not be recovered.

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

Impact

The services carried by the board are unstable. In most serious case, all services carried by the

board are interrupted.

Action

1. On NMS fault management interface, check if the PSN in the same shelf has generated related

alarms. If yes, follow the suggestions on handling the related alarms.

The related alarm is as follows:

198019456 All high-speed links between line card and package switching board are out of

synchronism

2. Unplug and plug the board.


3.1.23 198015875 GLI table lookup failed

Alarm Information

Code: 198015875

Name: GLI table lookup failed

Severity: Minor


3-21



Alarm Description

The number of dropped packets is over the threshold due to lookup critical table failure

Alarm Cause

1. L1 table or L2 table error.

2. Destination IP of packets or hardware is error.

Impact

Packets would be dropped which would cause poor voice quality and other problems.

Action

Switch the master port of the GLI board (where table lookup failed) to the partner board

3.1.24 198015876 GLI exception packets statistic over threshold

Alarm Information

Code: 198015876

Name: GLI exception packets statistic over threshold

Severity: Minor


Alarm Description

GLI exception packets statistic over threshold

Alarm Cause

1. Connection between fiber and optic modules is not perfect.

2. Something wrong with fiber optic module.

3. Board hardware error.

Impact


Action

1. Check the connection between fiber and optic modules.

2. Reboot the board.

3-22


Chapter 3 Alarms

3.1.25 198015877 GLIQV SRAM/DRAM error

Alarm Information

Code: 198015877

Name: GLIQV SRAM/DRAM error

Severity: Minor


Alarm Description

GLIQV SRAM/DRAM error

Alarm Cause

1. SRAM of GLIQV is error.

2. DRAM of GLIQV is error.

3. Micro engine of GLIQV is error.

Impact


Action


2. Change the master port to slave port.

3. Replace the board with a new board.

3.1.26 198002560 Board CPU overload

Alarm Information

Code: 198002560

Name: Board CPU overload

Severity: Major


Alarm Description

The usage of CPU is over the threshold

3-23



Alarm Cause

1. Excessive data traffic at higher layer.

2. System is performing data synchronization or saving.

3. CPU alarm threshold setting is under configured.

Impact

CPU occupancy indicates the current status of system operation. CPU overloaded, or over high

occupancy, is usually caused by service or operation that consume much time.

It has the following impact on the system:

Services with low priority level have little or no access to the processing of CPU, which reduces

processing speed of the services or even halts the processing.

System board could reset under excessively overloading conditions, causing interruption to the

service it performs.

Action

1. Open the rack map on the Configuration Management window, select Board, right click and select

Board Property. Check the CPU overload threshold setting on the CPU Information tab. Please reset

CPU overload threshold if the CPU overload threshold value is too low. It will take 30 seconds for

the new setting to take effect.

Recommended threshold value: 80% for low level load threshold, 90% for high level load threshold.

2. Check for the record of data synchronization, data saving or other file operations in the network

manager log files. Those operations might increase the CPU utilization rate radically, and it might

take 2 minutes.

3. Check for the record of new board added or version upgrade operation in the network manager

log files. Version upgrading operation might increase CPU utilization rate radically, and it might

take 2 minutes.

3.1.27 198002561 High temperature on CPU board

Alarm Information

Code: 198002561

Name: High temperature on CPU board

Severity: Major


Alarm Description

High temperature on CPU board

3-24


Chapter 3 Alarms

Alarm Cause

1. Fan faulty.

2. High temperature in rack.

3. CPU overload.

Impact

Automatic CPU reset might occur.

Action

1. In NMS Configuration Management interface, click Rack. Right click the concerned board >

Show Board Properties Page > CPU1 or CPU2. Check 2 parameters: Low/High threshold of alarm

temperature, Reset temperature. If the settings are low, please adjust the High threshold of alarm

temperature and the Reset temperature. The new settings will be valid after 30 seconds.

Recommended Thresholds: High threshold of alarm temperature: 90 degrees Celsius, Reset

temperature: 95 degrees Celsius.

2. Observe the thermometer in machine room to know room temperature. If it is high, please take

effective measures to cool down.

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

4. Check the air intake and air outlet of the rack. Does it have much 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.

3.1.28 198025602 TDM switch abnormal

Alarm Information

Code: 198025602

Name: TDM switch abnormal

Severity: Minor


Alarm Description

The board has an abnormal half-fixed connection

Alarm Cause

1. Check for any clock alarms.

2. TDM Switch chip is faulty

3. Wrong board in configured slot.

3-25



Impact

The link with abnormal connection is interrupted. Accordingly, services are affected.

Action

1. In NMS Configuration Management interface, view the configuration of IMA links. Do the values of

HW and TS fields configured for IMA links conflict (for example, two A ends are configured with the

same B end). If yes, modify the configuration.

2. Replace the faulty board.

3.1.29 198005376 Internal media port of board is abnormal

Alarm Information

Code: 198005376

Name: Internal media port of board is abnormal

Severity: Major


Alarm Description

Inner media port link down

Alarm 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 of UIM.

3. Backplane wiring failure of local slot to UIM.

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

5. Service over the rated capability of the board.

Impact

Because internal media stream can not be transmitted via this port, it will select another port for

transmission. If all the internal ports are abnormal, the internal media stream will be interrupted and

all the services provided on this board will be interrupted.

3-26


Chapter 3 Alarms

Action

1. Check the Alarm Management window for the CUP overloaded on the first level switching board,

UIM board at the shelf, or local board. Perform recommended solution to process the alarm(s) if any.

Related Alarm: 198002560 Board CPU Overloaded

2. Check the Alarm Management window for the alarms of Inter-shelf media plane links abnormal.

Perform the recommended solution to process the alarm(s) if any.

Related Alarm: 198005121 Inter-shelf Media Plane Link Error


4. Change the slot of the board.

5. Replace the UIM in the same shelf.

3.1.30 198066070 Board offline or CPU in reset status for a longperiod

Alarm Information

Code: 198066070

Name: Board offline or CPU in reset status for a long period

Severity: Major


Alarm Description

Board offline or CPU in reset status for a long period

Alarm Cause

1. The board is not in position.

2. Hardware failure.

Impact

If the board is normal, but its in-position indicator has a fault, then this 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.

Action

1. Check whether the board is in position. If not, insert the board.

2. Plug/unplug the board.


4. Replace the slot

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

3-27



3.1.31 198005381 Input clock is abnormal

Alarm Information

Code: 198005381

Name: Input clock is abnormal

Severity: Critical


Alarm Description

Input clock is abnormal

Alarm Cause

1. The Clock board is abnormal.

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

3. The clock reference source is abnormal.

Impact

The services are interrupted because the system can not get a proper clock.

Action

1. Reconnect the cable between the board and the clock reference (the previous level).

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

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


3.1.32 198005389 CPU sub card in position is not configured inthe database

Alarm Information

Code: 198005389

Name: CPU sub card in position is not configured in the database

Severity: Warning


Alarm Description

A (CPU) subcard is online, but is not configured by database

3-28


Chapter 3 Alarms

Alarm Cause

1. Configuration is incorrect.

2. Board is misplaced.

Impact

Since the board where the unconfigured sub card is located resets repeatedly, power resource of

the equipment is wasted. However, services won't be affected.

Action

Is the sub card needed?

If no, remove the sub card.

If yes, change the type of board so that it can support the sub card.

3.1.33 198005390 CPU sub card is missing from slot but isconfigured in database

Alarm Information

Code: 198005390

Name: CPU sub card is missing from slot but is configured in database

Severity: Major


Alarm Description

A (CPU) subcard is not online, but has been configured by database

Alarm Cause

1. The configuration is wrong.

2. A wrong board is inserted.

Impact

The sub-card functions are unavailable, accordingly this board does not support relevant services.

The influence on the system is various according to different type of sub-card.

If the sub-card is an interface board, the transmission link via this board is not connectable, then

services will be accessed through other sub-card. If the sub-card is a signalling process board,

the cell/Node B configured for this board is not available for services. If the sub-card is a user's

plane board, user plane process capability will decline, then services will be accessed through

other sub-card.

3-29



Action

Is the sub-card required? If no, modify the type of board so that the new type doesn't support such

sub-card; if yes, insert the sub-card firmly.

3.1.34 198005395 External port abnormal

Alarm Information

Code: 198005395

Name: External port abnormal

Severity: Major


Alarm Description

The physical link of the external port is down

Alarm Cause

1. The cable is not properly connected or not connected to the port.

2. The port chip on the board is faulty.

3. The opposite board is faulty.

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 in this case, totally data throughput will decline. Meanwhile, the reliability

and stability of the system declines. If there is no standby port, all communication links via this port

will be broken, and the services carried via this port will be interrupted.

Action

1. Reconnect or replace the cable.


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

Check, including but not limited to: such as port attributes 10M/100M/1000M, is adaptive or

mandatory, full-duplex, half duplex.

3-30


Chapter 3 Alarms

3.1.35 198005396 Exceptional communication on UIM board orback plane

Alarm Information

Code: 198005396

Name: Exceptional communication on UIM board or back plane

Severity: Major


Alarm Description

Board internal media plane packet test abnormal

Alarm Cause

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

2. The switch IC on UIM/GUIM/GUIM2 provides a port, which is connected to 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 the same shelf, is overloaded.

5. Service exceeds the processing capability of the board.

Impact

If the internal media plane stream can not be processed, packets may be lost. In this case, services

provided by this board become unstable.

If it is port fault or connector fault, the internal media plane is completely broken. In this case, services

borne on this board are interrupted.

If either CPU or traffic is overloaded, services carried on the board will be delayed. In serious

situation, services may be interrupted.

Action



Related Alarm: 198005376 internal media plane port failure.

2. Check the Alarm Management window for the CUP overloaded on the first level switching board,

UIM board at the shelf, or local board. Perform recommended solution to process the alarm(s) if any.

Related Alarm: 198002560 Board CPU Overloaded



Related Alarm: 198005121 Inter-shelf Media Plane Link Error


5. Change the slot of the board.

3-31



6. Replace the UIM in the same shelf.

3.1.36 198005399 DSP resource is unavailable

Alarm Information

Code: 198005399

Name: DSP resource is unavailable

Severity: Major


Alarm Description

The state should be reported to the DBS and blocked in the DBS when Dsp resources is not

available.(such as broken)

Alarm Cause

This alarm indicates DSP resource is not available. It is monitored by higher-level layer. Once DSP is

blocked, an alarm is given. This includes the following situations:

1. DSP version fails to be loaded so that the system is unable to operate normally.

2. The HPI port on DSP is abnormal.

3. The DSP media plane communication is disconnected.

4. DSP resets.

Impact

All services processed by this DSP are interrupted, and those services will be re-created on other

normal DSPs. If the DSP is unavailable for a long time, system performance will be degraded.

Action

1. In network management system, check the operation & maintenance log file. Is there a record,

indicating DSP version replacing? If yes, this operation must cause DSP to reset. And having this

alarm is a normal phenomenon. No handling is required. Please wait until DSP reset is complete.

2. In Alarm Management interface, check whether there is one of the following alarms. If yes, please

solve the problem according to corresponding handling suggestions.

Related Alarms:

198005701 Version Load Error

198005655 DSP auto-detection abnormal

198005700 DSP abnormally resets

3. Reset the board.


3-32


Chapter 3 Alarms

3.1.37 198005403 Board SRAM self-check fails

Alarm Information

Code: 198005403

Name: Board SRAM self-check fails

Severity: Major


Alarm Description

Board's hardware faults occur in SRAM self-check during the process of system power on

Alarm Cause

Hardware fault of board.

Impact

Board operation might be abnormal.

Action

Replace the board, and check whether this alarm disappears.

3.1.38 198005404 Board OCXO oven fault

Alarm Information

Code: 198005404

Name: Board OCXO oven fault

Severity: Major


Alarm Description

Board OCXO oven fault occur

Alarm Cause

Hardware fault of board.

3-33



Impact

Board operation might be abnormal.

Action

Replace the board, and check whether this alarm disappears.

3.1.39 198005405 Clock board phase-lock loop work modeabnormal

Alarm Information

Code: 198005405

Name: Clock board phase-lock loop work mode abnormal

Severity: Major


Alarm Description

Phase-lock loop is not in TRACE state

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

Impact

The designated reference clock cannot be phase-locked.

Action

1. Check if the corresponding clock reference is correctly inputted.


3.1.40 198026116 PP2S output clock lost

Alarm Information

Code: 198026116

Name: PP2S output clock lost

3-34


Chapter 3 Alarms

Severity: Major


Alarm Description

PP2S output clock lost

Alarm Cause

Hardware is faulty.

Impact

1. If it is caused by the master clock board, the system will fail to get clock. Because of this, all

clock-related boards can not work normally and services will be interrupted. The relevant boards

include IMA protocol processing board and interface board with HW process capability.

2. If it is caused by the slave clock board, services will not be affected.

Action

1. If the alarm is reported by master board rather than slave board, perform master/slave switching.

2. Replace the board where the alarm is reported.

3.1.41 198026117 PP2S clock reference lost

Alarm Information

Code: 198026117

Name: PP2S clock reference lost

Severity: Major


Alarm Description

CLKG PP2S clock base lost

Alarm Cause

Hardware is faulty.

Impact

The system can not get wanted clock, therefore all clock-related processes are abnormal.

3-35



Action

1. If the board where the alarm is declared is ICM, please replace the board.

2. If the board where the alarm is declared is CLKG:

Check the connection between CLKG and GCM.

Replace the CLKG.

Replace the GCM.

3.1.42 198026118 16CHIP clock reference lost

Alarm Information

Code: 198026118

Name: 16CHIP clock reference lost

Severity: Major


Alarm Description

CLKG clock 16CHIP base lost

Alarm Cause

Hardware is faulty.

Impact

The system can not get wanted clock, therefore all clock-related processes are abnormal.

Action

Replace the board.

3.1.43 198026127 Loss of Level 3 reference source clock

Alarm Information

Code: 198026127

Name: Loss of Level 3 reference source clock

Severity: Minor


3-36


Chapter 3 Alarms

Alarm Description

Loss of Level 3 reference source clock

Alarm Cause

Input clock reference is in unavailable status for no more than 10 minutes.

Probable causes include:

1. Clock reference input is abnormal.

2. The configured clock reference does not exist.

Impact

When all configured clock reference sources are lost, the clock board comes to free running or

hold-over state. Accuracy of output clock is determined by the crystal oscillator of clock board.

No impact on service.

Action

1. Re-connect the input clock reference.

2. For the clock reference not in use, delete the corresponding “Circuitry Clock Reference”

configuration on NMS configuration management interface (board property).

3. If the clock reference is from interface board, check if the backcard of the interface board is

supported clock output.

3.1.44 198026128 Loss of Level2 reference source clock

Alarm Information

Code: 198026128

Name: Loss of Level2 reference source clock

Severity: Major


Alarm Description


Alarm Cause

Input clock reference is in unavailable status for more than 10 minutes and less than 24 hours.




3-37



Impact



The clock loss leads to synchronization failure between system clock and clock reference source.

Service interruption might occur.

The system will not be affected if the following two events happen together.

Input clock reference source is lost.

The phase-locked loop locks other clock reference source.

Action






3.1.45 198026129 Loss of Level1 reference source clock

Alarm Information

Code: 198026129

Name: Loss of Level1 reference source clock

Severity: Critical


Alarm Description


Alarm Cause

Input clock reference is in unavailable status for more than 24 hours.




3-38


Chapter 3 Alarms

Impact



The clock loss leads to synchronization failure between system clock and clock reference source.

Service interruption will occur.

The system will not be affected if the following two events happen together.

Input clock reference source is lost.

The phase-locked loop locks other clock reference source.

Action






3.1.46 198026131 CLKG board PLL is unlocked. Clock will drift

Alarm Information

Code: 198026131

Name: CLKG board PLL is unlocked. Clock will drift

Severity: Minor


Alarm Description

CLKG board PLL is unlocked

Alarm Cause

Hardware fault of board

Impact

System could not get the needed clock, which will cause processing abnormity related to the clock.

Action

1. If the alarm is reported by the master board, and the slave board is good, perform master/slave

changeover operation.

2. Replace the fault board.

3-39



3.1.47 198026133 Output clock lost

Alarm Information

Code: 198026133

Name: Output clock lost

Severity: Major


Alarm Description

Output clock lost

Alarm Cause

Hardware is faulty.

Impact

1. If this alarm occurs on the master board, system clock synchronization will fail and services will

be interrupted.

2. If this alarm occurs on the slave board, services will not be affected.

Action

1. If the alarm is declared by master board rather than slave board, perform master/slave switching.

2. Replace board.

3.1.48 198005632 Hard disk usage rate exceeds threshold.

Alarm Information

Code: 198005632

Name: Hard disk usage rate exceeds threshold.

Severity: Major


Alarm Description

Hard disk usage rate exceeds one of the thresholds. There are three kinds of threshold about this

alarm.

3-40


Chapter 3 Alarms

Alarm Cause

1. The configured usage rate threshold is unreasonable.

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

Impact

When hard disk usage rate exceeds its threshold, new data can not be written. The data may be

lost. There is no impact on services.

Action

1. In NMS configuration management interface, click MPX86 or MPX86/2 alarm parameters > hard

disk full alarm to check the threshold used to report a hard disk usage alarm. If the threshold value is

low, please increase it.

2. Clean the space of hard disk. Delete the files that are no longer used, or move them to external

storage devices.

3.1.49 198005637 Back card does not match with front board

Alarm Information

Code: 198005637

Name: Back card does not match with front board

Severity: Minor


Alarm Description

Back card error. Back card and frontal board do not match

Alarm Cause

1. Incorrect rear board is used.

2. Rear board failure.

Impact

1. When the rear board interface is used to connect other network element, it will cause link

interruption at bottom layer, and services over the corresponding link will be interrupted.

2. When the rear board interface is used to connect internal control plane, it will cause communication

error at internal control plane. As a result, the board can not exchange control plane messages and

services borne on the board will be interrupted.

3. When the rear board interface of clock board is used to extract clock, it will cause loss of clock

signal. Because without input clock, the system services will be interrupted.

3-41



Action

1. Check the front board type for the correct rear board type, and use the correct rear board.

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

3.1.50 198005661 Physical link down between media interface ports

Alarm Information

Code: 198005661

Name: Physical link down between media interface ports

Severity: Warning


Alarm Description

Media interactive GE port link down

Alarm Cause

The network port or board is faulty.

Impact

The APS optical port data on the standby board cannot reach the active board. When the active

optical port is normal, the service is not affected. When the active optical port is faulty, APS fails to

protect optical port and thus all services carried by the optical port are interrupted.

Action


2. Replace the other board, that is, the board rather than the faulty board in active/standby

configuration.

3. Replace the slot. Use the slot that supports GE channel between boards.

.

3.1.51 198005662 IDE running overtime

Alarm Information

Code: 198005662

Name: IDE running overtime

3-42


Chapter 3 Alarms

Severity: Warning


Alarm Description

The hard disk working time exceeds the allowed duration

Alarm Cause

IDE is operated for longer time.

Impact

When hard disk work for long time without sleep, engine will be in high 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 the disk. But this is

out of the software controled, and may result in data lose when disk cannot be accessed transitorily.

Action

No handling is necessary.

3.1.52 198005667 E1 is looped back

Alarm Information

Code: 198005667

Name: E1 is looped back

Severity: Minor


Alarm Description

Loop E1 alarm

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

3-43



Impact

Data can not be sent out because of the loopback E1.

Action

1. Disconnect the loopback E1.

2. Restart the board.


4. Replace the opposite board.

3.1.53 198005668 Cross-linked E1 alarm

Alarm Information

Code: 198005668

Name: Cross-linked E1 alarm

Severity: Minor


Alarm Description

Cross-linked E1 alarm

Alarm Cause

Self board has cross-linked E1.

Impact

Data can not be sent out because of cross-linked E1.

Action

1. Disconnect the cross-linked E1, Wait for 1 minute and check whether the alarm disappears.

2. Restart the board and check whether the alarm disappears.

3. Replace the board by another one and check whether the alarm disappears.

4. Replace the board connected with this board, check whether the alarm disappears.

3.1.54 198005669 Synchronization status check of FPGA failed

Alarm Information

Code: 198005669

3-44


Chapter 3 Alarms

Name: Synchronization status check of FPGA failed

Severity: Critical


Alarm Description

Synchronization status check of FPGA failed

Alarm Cause

Synchronization status check of FPGA and SPI4/VSC872/VSC874 failed. It's usually caused by

hardware exceptions. For example, the clock chip works abnormally.

Impact

If synchronization status check of FPGA fail, Media can not receive or send data normally. And the

board will reset for the exception of the media check frame.

Action

Replace the board.

3.1.55 198005671 Sending or receiving packets using the cascadeports inner board failed

Alarm Information

Code: 198005671

Name: Sending or receiving packets using the cascade ports inner board failed

Severity: Critical


Alarm Description

Sending or receiving packets using the cascade ports inner board failed

Alarm 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/GUIM2 board has hardware faults.

3-45



Impact

Cascade ports inner UIMC/GUIM/GUIM2/CHUB functions abnormally. Packets may be lost, and even

worse, link disconnection may occur on the control planes of some boards. For active/standby

configuration, there are two cases:






Action

1. Check the GCS subcard connection on the board. If the subcard is loosely inserted, tightly insert it

and wait for the board to be powered on.

2. Replace the GCS subcard.

3. Replace the UIM2/GUIM/GUIM2/CHUB board.

3.1.56 198005655 Errors detected in DSP

Alarm Information

Code: 198005655

Name: Errors detected in DSP

Severity: Major


Alarm Description

Inform UP layer to block after DSP has automatically detected abnormity

Alarm Cause

1. The HPI port fails

2. Hardware failure.

Impact

This DSP will be blocked and no longer available. The cell of this DSP is out of service; the subscriber

using this DSP is out of service; call loss rate might increase when call traffic is high.

3-46


Chapter 3 Alarms

Action

1. Reset the board.

2. Replace DSP sub-card.


3.1.57 198019712 APS channel mismatched

Alarm Information

Code: 198019712

Name: APS channel mismatched

Severity: Major


Alarm Description

APS channel mismatch

Alarm Cause

1. Fiber connection is wrong.

2. APS backup mode is configured differently between local end and opposite end.

3. APS protection mode is configured differently between local end and opposite end.

4. The opposite equipment is faulty.

Impact

APS automatic protection switching function is paralyzed. When the working optical port is abnormal,

the protection optical port will not work, leading to service interruption on this optical port.

Action

1. Check fibber connection.

Check fibber connection at both ends. Ensure that the work optical ports at both ends are

interconnected, and the protection optical ports at both ends are interconnected.

On NMS configuration management interface, locate the relevant board in the rack. Right-Click the

board and open board properties page. Click Optical port APS protection to view the "Work optical

port" and "Protection optical port" configured at local end.

2. Check APS backup mode configuration at both ends.

Check APS backup mode (1+1 or 1:1) at local end to ensure configuration consistency at both ends.


board and open board properties page. Click Optical 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.

3-47



Check APS protection direction (unidirectional or bidirectional) configured at local end. Ensure

configuration consistency at both ends.


board and open board properties page. Click Optical port APS protection to view the "Protection

Direct" (unidirectional or bidirectional).

4. Check whether APS is supported by the opposite equipment. Check whether APS configuration is

correct and has taken effect.

3.1.58 198019713 APS mode mismatched

Alarm Information

Code: 198019713

Name: APS mode mismatched

Severity: Major


Alarm Description

APS protection mode mismatch

Alarm Cause

1. Fiber connection is wrong.

2. APS backup mode is configured differently between local end and opposite end.

3. APS protection mode is configured differently between local end and opposite end.

Impact

1. When fibber connection is correct and the working optical port can work normally, services won't

be affected.

2. When the working optical port is faulty, APS automatic protection switching function doesn't work,

and services carried via this optical port will be interrupted due to lack of protection.

Action

1. Check fibber connection.

Check fibber connection at both ends. Ensure that the work optical ports at both ends are

interconnected, and the protection optical ports at both ends are interconnected.


board and open board properties page. Click Optical port APS protection to view the "Work optical

port" and "Protection optical port" configured at local end.

2. Check APS backup mode configuration at both ends.

Check APS backup mode (1+1 or 1:1) at local end to ensure configuration consistency at both ends.

3-48


Chapter 3 Alarms



Type" (1+1 or 1:1).

3. Check APS protection direction at both ends.

Check APS protection direction (unidirectional or bidirectional) configured at local end. Ensure

configuration consistency at both ends.



Direct" (unidirectional or bidirectional).

3.1.59 198019714 APS configuration alarm

Alarm Information

Code: 198019714

Name: APS configuration alarm

Severity: Major


Alarm Description

APS reset board

Alarm Cause

Optical interface are not configured for APS in 1:1 mode.

Impact

The board can not enter into normal working status. All board services fail to be established.

Action

1. If board backup mode is configured as 1:1 or 1+1 and SDH optical interface is needed, at least one

set of APS protection needs to be configured.

To configure APS protection:


board and open board properties page. Click Optical port APS protection.

2. If board master/slave mode is not needed, modify board backup mode into.

To configure board backup mode:

Delete the relevant board on NMS configuration management interface. 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 optical interface is required, modify the

board backup mode into 1+1.

3-49



To configure board backup mode:

Delete the relevant board on NMS configuration management interface. Then recreate the board.

Select board backup mode as "1+1" during board creation.

3.1.60 198005121 Inter-shelf media plane links abnormal

Alarm Information

Code: 198005121

Name: Inter-shelf media plane links abnormal

Severity: Minor


Alarm Description

Ge routing is abnormal

Alarm Cause

1. The fiber connection is error between shelves, or the fiber is not physically plugged.

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

3. The transceiver of the board link detection packet is exceptional.

Impact

The inter-shelf service bandwidth is reduced. The inter-shelf services may be interrupted if no

backup is configured.

Action

1. In the NMS Configuration Management interface, select Unit Connection Relation, then compare

the configuration with actual physical connection. If it is different, adjust connection cables according

to the configuration.

2. Check the connection of optical fiber and make sure it is in cross connection. Is there any relevant

alarm? If yes, please solve the problem according to recommended handling suggestions.

Relevant Alarm: 198005125 GE optical transceiver module is wrongly connected to left/right board

slots at opposite end

3. Replace the optical fiber or the optical transceiver module so that the SD indicator for the

corresponding port is on.

4. Replace the local board.


3-50


Chapter 3 Alarms

3.1.61 198005124 Capacity of TRUNK communication is insufficient

Alarm Information

Code: 198005124

Name: Capacity of TRUNK communication is insufficient

Severity: Minor


Alarm Description

Capacity of TRUNK communication is insufficient

Alarm Cause

1. Connection failure.

2. Line failure.

3. Board failure.

4. Rear board failure.

Impact

There is no impact on services when TRUNK connection is not adopted for inter-shelf control plane

communication. However if TRUNK connection is adopted, this alarm indicates insufficient network

communication capability. This may cause congestion at control plane. During heavy traffic period,

this may cause much delay or services interruption in extreme condition.

Action

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

is required.

2. Check the number of connections, i.e. 4 FEs and 2 GEs are required. Complete the connections if

there is any missing.

3. Check whether the connection is correct.

The correct connection is described as below:

For FE port trunk, if UIM board is installed on BUSN shelf, then TRUNK connection is not supported.

In this case, this alarm won't occur. If UIM is installed on other shelf, FE7, FE8, FE9 and FE10

work together to form a TRUNK port. However if it is GUIM/GUIM2 board, FE3, FE4, FE5 and FE6

form a TRUNK port.

For CHUB board, every 4 adjacent FE ports form a TRUNK port, such as FE1~FE4, FE5~FE8 etc.

For each trunk port, All the 4 RE ports must be connected, and direct connection is recommended.

For GE port trunk, 2 GE interfaces (CHUB board inter-connection) are connected in cross-connection

mode. The #1 GE port on the left board on the local shelf corresponds to the #1 GE port on the left

board on the opposite shelf; the #2 GE port on the left board on the local shelf corresponds to the #2

GE port on the right board of opposite shelf.

3-51



The #1 GE port on the right board on the local shelf corresponds to the #2 GE port on the left board

on the opposite shelf, and the #2 GE port on the left board on the local shelf corresponds to the #2

GE port on the right board on the opposite shelf.

4. Replace the cable.

5. Replace the rear board.

6. Replace the connected board.

3.1.62 198005125 GE optical connection is cross connected

Alarm Information

Code: 198005125

Name: GE optical connection is cross connected

Severity: Minor


Alarm Description

Module of GE connect to aside left or right board Error.

Alarm Cause

1. Fibre connected to wrong module.

2. GE optical transceiver module in wrong slot.

3. Transmit and receive fibres crossed.

Impact

Cause interruption to all services performed on this shelf.

Action

1. Check the fiber optics for its proper cross connection

2. Replace the optical fiber or the optical transceiver module

3.1.63 198005893 Memory check failed

Alarm Information

Code: 198005893

Name: Memory check failed

Severity: Critical

3-52


Chapter 3 Alarms


Alarm Description

Memory check failed

Alarm Cause

Memory check failed.

Impact

The operation related to the memory maybe failed.

Action

1. Make records of the alarm information.

2. Replace the board or subcard.

3.1.64 198005650 Conflicted MAC addresses of boards on thesame shelf

Alarm Information

Code: 198005650

Name: Conflicted MAC addresses of boards on the same shelf

Severity: Critical


Alarm Description

The physical address information of the board is incorrect

Alarm Cause

1. The board is not inserted in position.

2. The board is not consistent with the backboard information.

3. UIM may have the loop back phenomena.

Impact

The board fails to start up, or control plane communication is abnormal. As a result, users cannot

gain access and existing services are interrupted.

3-53



Action

1. Check whether the DIP switch setting is changed or the board is not restarted after the change.

2. Plug and unplug the board and then check if the alarm is eliminated.

3.1.65 198005672 Synchronization Ethernet clock source isunusable

Alarm Information

Code: 198005672

Name: Synchronization Ethernet clock source is unusable

Severity: Major


Alarm Description

Synchronization Ethernet clock source is unusable, the slave clock port can not synchronize with the

connected port.

Alarm Cause

1. The slave clock port does not receive ESMC PDU for 5 seconds.

2. The SSM value that the slave clock port received is DNU.

3. The port speed is 10M.

4. Physical link of the port is broken.

Impact

The slave clock port can not synchronize with the connected port, which will cause processing

abnormity related to the clock.

Action

1. Check the synchronization Ethernet's master/slave clock configuration of the connected port,

the configuration should be master;

2. Check local and connected port speed, port speed should not be 10M;

3. Check if the physical connection is correct.

3-54


Chapter 3 Alarms

3.1.66 198015878 GLI internal fabric port receive error

Alarm Information

Code: 198015878

Name: GLI internal fabric port receive error

Severity: Major


Alarm Description

The number of dropped frames is over threshold due to internal fabric port receive error

Alarm Cause

1. Network Processor or Switch Chip error.

2. PSN Board Hardware error.

Impact


Action

1. If only ONE GLI triggered this alarm, switch all master port of this board to its partner board,

and reboot the board.

2. If the alarm being triggered again after the board rebooted, replace the board.

3. If the alarm being triggered again after the board replaced, contact the next level of maintenance

support.

4. If the more than one GLI triggered this alarm, contact the next level of maintenance support.

3.1.67 198015879 GLI Port receive error

Alarm Information

Code: 198015879

Name: GLI Port receive error

Severity: Minor


Alarm Description

GLI Port receive error

3-55



Alarm Cause

1. Connection between fiber and optic modules is not perfect.

2. Something wrong with fiber optic modules.


Impact


Action

1.Check the connection between fiber and optic modules.

2. Replace optic modules.


4. Contact the next level of maintenance support.

3.1.68 198015880 GLI board control and media planecommunication error

Alarm Information

Code: 198015880

Name: GLI board control and media plane communication error

Severity: Minor


Alarm Description

The number of dropped packets is over threshold due to control and media plane communication error

Alarm Cause

1. SRAM or DRAM error.


Impact


Action



3-56


Chapter 3 Alarms

3.1.69 198015881 GLI port transmit error

Alarm Information

Code: 198015881

Name: GLI port transmit error

Severity: Minor


Alarm Description

GLI port transmit error

Alarm Cause

1. Packets error.


Impact


Action

1. Check all the GLI board in the same shelf to confirm whether there were any other alarms, if this

is the ONLY alarmed board, switch all master port of this board to its partner board, and replace

this board.

2. If this alarm being triggered again after the board replaced, contact the next level of maintenance

support.

3. If more than one GLI triggered this alarm, contact the next level of maintenance support.

3.1.70 198015882 GLI buffer error or allocate fail

Alarm Information

Code: 198015882

Name: GLI buffer error or allocate fail

Severity: Minor


Alarm Description

GLI buffer error or allocate fail

3-57



Alarm Cause

1. The traffic is over the capability of the board.

2. SRAM or DRAM error.


Impact


Action

1. Check the state of all ports of the alarmed board, if more than 2 ports of this board is in master

state, switch 1 or 2 ports to its partner port.

2. If the alarm is still active, reboot the board.

3. If the alarm being triggered again after the board rebooted, replace the board.

3.1.71 198005670 Oscillator status abnormal

Alarm Information

Code: 198005670

Name: Oscillator status abnormal

Severity: Critical


Alarm Description

Oscillator status abnormal

Alarm Cause

Oscillator may stop oscillating or meet frequency deviation.

Impact

Board cannot work normally with this crucial device error.

Action

Replace the board.

3-58


Chapter 3 Alarms

3.1.72 198005673 Backboard switch set is changed.

Alarm Information

Code: 198005673

Name: Backboard switch set is changed.

Severity: Major


Alarm Description

Backboard switch set is changed.

Alarm Cause

The setting of the DIP switch on the backboard has been changed.

Impact

Other board faults

Action

1. Plug the uim/UIM_2/GUIM/GUIM2/GUIM/GUIM2_2 board tightly to the slot again and then observe

if the alarm is given.

Y->Go to "2"

N->End.

2. Replace the backplane of the shelf, and check if this alarm is given.

Y->Please contact the next level of maintenance support.

N->End.

3.1.73 198005653 Type B fault on board (GPS) phase-lockequipment

Alarm Information

Code: 198005653

Name: Type B fault on board (GPS) phase-lock equipment

Severity: Major


3-59



Alarm Description

Type B fault on board (GPS) phase-lock equipment

Alarm Cause

Class B faults of GPS module of ICM board are generated by singlechip processor checking,

including antenna feed short circuit or open circuit, poor quality of received satellite signals or difficulty

in receiving satellite signals, and large phase difference of 10M OCXO assistant phase control.

Impact

There is no impact on system clock or services if the type B fault lasts for less than 48 hours. After 48

hours, the system clock is deviated and system synchronization fails. When GPS signal is poor, the

alarm will be repeatedly reported/restored. As long as the alarm lasts for no more than 48 hours, both

system clock and services will not be affected.

When the system clock is lost or clock frequency deviation happens, services may be affected

differently according to transmission mode.

1. For TDM transmission, all links based on TDM transmission medium (including UE transmission

link and cell transmission link) will be affected. Packets may be lost, which leads to degradation

of service quality. In serious situation, services may be interrupted, handover may fail and cell

out-of-service may happen.

2. For non-TDM transmission (e.g. IP transmission), services via Iub interface will be affected. This

fault will not affect services via Iur interface or Iu interface. In this case, Node B will fetch clock signal

from RNC by using IEEE1588 function, but the clock is inaccurate.

When RNC's clock frequency offset is no more than 0.05 ppm, Node B synchronization can be

achieved. But inter-RNC soft handover success rate will fall.

When RNC's clock frequency offset exceeds 0.5 ppm, Node B cannot lock the clock. Then Node B

will work in free oscillation mode. In this case, inter-Node B soft handover success rate will drop.

Action

Check the input circuit of antenna feeder of ICM board so that it can receive good GPS signals.

The checking items include:

1) The position of the receiving antenna.

The antenna should be installed in an open area, far away from high buildings and clear from shades.

The effective visibility angle of the antenna should be greater than 150 degrees.

2) The connection between power splitter and front panel.

The connector used to connect the power splitter and the front panel should be in good contact and

properly connected.

3-60


Chapter 3 Alarms

3.1.74 198005674 Sending or receiving packets betweenmanagement port and CPU control port failed

Alarm Information

Code: 198005674

Name: Sending or receiving packets between management port and CPU control port

failed

Severity: Critical


Alarm Description

Sending or receiving packets between management port and CPU control port failed

Alarm Cause

Management port or CPU control port has faults.

Impact

Isolate island, checking packets being abnormal or messages between shelves being abnormal may

occur. For active/standby configuration, there are two cases:






Action

Replace the board. CPU control port, management port or switch chip is error when this alarm

happens. By resetting the board, this fault will be self-cured with very few possibility, and the fault

may remain.

3.1.75 198005130 The fiber port failed to change over

Alarm Information

Code: 198005130

Name: The fiber port failed to change over

Severity: Major


3-61



Alarm Description

The fiber port failed to change over

Alarm Cause

The fiber port failed to change over

Impact

The fiber can not work abnormally.

Action

Try to change over the special fiber port by network manage system. If failed to change over for three

continuous times, the fiber port has fault, please replace the fiber port or board.

3.1.76 198005131 The fiber's quality abnormal

Alarm Information

Code: 198005131

Name: The fiber's quality abnormal

Severity: Warning


Alarm Description

Soft check failed for the fiber

Alarm Cause

The fiber is not completed connected to the port, or is damaged, or is not compatible with the optical

transceiver module in T-net switch.

Impact

There might be error in the data transmitted by the optical port which affects the quality of all the

services performed on this optical port.

3-62


Chapter 3 Alarms

Action

1. Check whether the fiber optics is connected to the port completely.

2. Perform loop back test to determine source of this alarm is on the local devices or the

corresponding devices. Perform self-loop test on local device. If the failure persists, the failure source

is on local device; if the failure disappears after self-loop test, then the source of failure is on the

corresponding device. Contact the corresponding device for solution.

3. Replace optics module.

4. Replace the fiber optics.


3.1.77 198005675 The input electrical source is error

Alarm Information

Code: 198005675

Name: The input electrical source is error

Severity: Warning


Alarm Description

One of the input electrical sources is error

Alarm Cause

One of the electrical sources inputted from PDU is abnormal.

Impact

The input power of the shelf has may have fault. There will be no power if all two electrical sources

input are abnormal.

Action

1. Please check the cable connection between the PDU and the back board.

Y->If the cable connection is OK, go to 2;

N->If the cable connection is error, please connect the cable again. Check whether the alarm

disappears. Y->The troubleshooting completes. N->Go to 2.

2. Please check the switch.

Y->If the switch is OK, go to 3;

N->If the switch is abnormal, please switch on the switch. Check whether the alarm disappears.

Y->The troubleshooting completes. N->Go to 3.

3. Please replace the cable.

Y->If the alarm disappears, the troubleshooting completes.

3-63



N->Please contact the next level of maintenance support.

3.1.78 198016641 Device's LRU algorithm invalid

Alarm Information

Code: 198016641

Name: Device's LRU algorithm invalid

Severity: Major


Alarm Description

Device's LRU algorithm is invalid, which may cause failure of queue scheduling

Alarm Cause

Device's LRU algorithm is invalid.

Impact

It may cause failure of queue scheduling, and then services won't work normally.

Action

Make records of the alarm information and contact the next level of maintenance support.

3.1.79 198002563 FPGA clock speed abnormal alarm

Alarm Information

Code: 198002563

Name: FPGA clock speed abnormal alarm

Severity: Major


Alarm Description

The FPGA clock speed is abnormal because it exceeds the threshold

3-64


Chapter 3 Alarms

Alarm Cause

The FPGA clock speed is abnormal.

Impact

The system time is inaccurate.

Action

1. Synchronize the system time with the external clock source.

2. If the alarm still exists or there is an alarm report after restarting the board, please replace the

board.

3.1.80 198002564 Auxiliary clock speed abnormal alarm

Alarm Information

Code: 198002564

Name: Auxiliary clock speed abnormal alarm

Severity: Major


Alarm Description

Auxiliary clock speed is abnormal because it exceeds the threshold

Alarm Cause

The auxiliary clock speed is abnormal.

Impact

1. The system time is inaccurate.

2. The Timer is disabled.

Action

1. Wait for about 20 minutes. If the alarm is not restored, please restart the board.

2. If the alarm still exists after restarting the board, please replace the board.

3-65



3.1.81 198005132 Mate board RUN signal invalid

Alarm Information

Code: 198005132

Name: Mate board RUN signal invalid

Severity: Minor


Alarm Description

The mate board exist POWERON signal but RUN signal is inexistent

Alarm Cause

The mate board exist POWERON signal but RUN signal is inexistent.

Impact

Board can not change over.

Action

1. Reboot slave board.

2. Reboot master board.

3.1.82 198005676 Connect port flow over threshold

Alarm Information

Code: 198005676

Name: Connect port flow over threshold

Severity: Major


Alarm Description

The connect port flow is too high, that is over the value of flow threshold configuration.

Alarm Cause

The connect port flow is too high, that is over the value of flow threshold configuration.

3-66


Chapter 3 Alarms

Impact

Maybe this port lost lots of packets.

Action

1. Check the value of flow threshold, if it is too low.

Y->Please increase value of the flow threshold to be the max one which one you wish, and then

check if this alarm is disappeared. If no, go to 2.

N->Go to 2.

2. Check this port's flow, if it is too high.

Y->Please decrease this port flow.

N->If this port's flow is not over the value of flow threshold, go to 3.

3. Make records of the alarm information and contact the next level of maintenance support

Cooperation.

3.1.83 198005791 TX output power exceeds the high threshold

Alarm Information

Code: 198005791

Name: TX output power exceeds the high threshold

Severity: Minor


Alarm Description

TX output power exceeds the high threshold

Alarm Cause

TX output power exceeds the high threshold

Impact

It affects the data transfer of the remote SFP. If it is serious, which will make bad the SFF on the

other side.

Action

1. Replace local SFP.

2. There may be something wrong with the transmission equipment. It needs to ask the maintenance

personnel special for maintaining transmission equipment to do troubleshooting or contact the next

level of maintenance support.

3. Please contact the next level of maintenance support.

3-67



3.1.84 198005792 TX output power exceeds the low threshold

Alarm Information

Code: 198005792

Name: TX output power exceeds the low threshold

Severity: Minor


Alarm Description

TX output power exceeds the low threshold

Alarm Cause

TX output power exceeds the low threshold

Impact

It affects the data transfer of the SFP.

Action

1. Replace the local SFP.





3.1.85 198005793 RX output power exceeds the high threshold

Alarm Information

Code: 198005793

Name: RX output power exceeds the high threshold

Severity: Minor


Alarm Description

RX output power exceeds the high threshold

3-68


Chapter 3 Alarms

Alarm Cause

RX output power exceeds the high threshold

Impact

It affects the data transfer of the local SFP. If it is serious, which will make bad the SFF on the

other side.

Action

1. Check the configuration of the TX module on the remote side is too long transmission.

2. Replace the SFP on the remote side.

3. Check the configuration of the fiber type (You should use single mode fiber, but OM1 or OM2 or

OM3 fiber).

4. Replace the SFP on the local side.

3.1.86 198005794 RX output power exceeds the low threshold

Alarm Information

Code: 198005794

Name: RX output power exceeds the low threshold

Severity: Minor


Alarm Description

RX output power exceeds the low threshold

Alarm Cause

RX output power exceeds the low threshold

Impact


Action

1. Check the configuration of the TX module on the remote side is too long transmission.

2. Replace the SFP on the remote side.

3. Check the configuration of the fiber type (You should use single mode fiber, but OM1 or OM2 or

OM3 fiber).

4. Replace the SFP on the local side.

3-69



3.1.87 198005795 The optical transceiver transmitter fault

Alarm Information

Code: 198005795

Name: The optical transceiver transmitter fault

Severity: Minor


Alarm Description

The optical transceiver transmitter fault

Alarm Cause

The optical transceiver transmitter fault

Impact


Action

1. If the connection is loose or broken, tighten or replace the local SFP.





3.1.88 198018436 Board loop back detection is abnormal

Alarm Information

Code: 198018436

Name: Board loop back detection is abnormal

Severity: Major


Alarm Description

Some test packets were discarded in board loop back detection

3-70


Chapter 3 Alarms

Alarm Cause

Board hardware fault.

Impact

When the slave board change to master, the service through this board will be interrupt.

Action

Replace the board.

3.1.89 198016896 APP driver memory operation abnormal

Alarm Information

Code: 198016896

Name: APP driver memory operation abnormal

Severity: Minor


Alarm Description

APP driver memory operation abnormal, such as static memory is not enough or pointer is rewrited.

Alarm Cause

1. Static memory is not enough.

2. Pointer was rewrited.

Impact

The board may reboot when the static memory is not enough.

Action

When the memory exception influences the services, reboot the board.

3.1.90 198105013 user plane resource pool overload

Alarm Information

Code: 198105013

Name: user plane resource pool overload

3-71



Severity: Minor


Alarm Description

The RNC detects that the user-plane resource pool cannot assign new resources.

Alarm Cause

The user-plane resource pool is overloaded.

Impact

The system is heavy loaded, and capacity expansion should be considered.

Action

1. [A2051] Run the START DTM command to perform a board diagnostic test to diagnose the

operational statuses of all RUB resource boards, and check whether the resource board is

operating properly.

Yes -> Step 2.

No -> Step 3.

2. Contact the next level of maintenance support (it is recommended to expand the capacity

of the RUB board).

3. 3. Contact the next level of maintenance support.

3.1.91 198105026 Media Ip address modified

Alarm Information

Code: 198105026

Name: Media Ip address modified

Severity: Critical


Alarm Description

The user-plane board detects a change of the media-plane IP address.

Alarm Cause

The media-plane IP address of the board is modified.

3-72


Chapter 3 Alarms

Impact

All of the services operating on the faulty board are interrupted.

Action

1. Run the SET NORMALRESET command to reset the board in accordance with "Rack number",

"Shelf number", "Slot number", and "CPU number" in the alarm information. Wait for five minutes,

and check whether the alarm is cleared.

Yes -> End.

No -> Step 2.


3.1.92 198105029 OMP reboot alarm

Alarm Information

Code: 198105029

Name: OMP reboot alarm

Severity: Major


Alarm Description

The OMP board reboots.

Alarm Cause

The OMP board reboots.

Impact

When the OMP is reset, the operation and maintenance tasks are affected, but services are not

affected.

Action

1. After the alarm arises, wait for five minutes, and check whether the alarm is cleared.

Yes -> End.

No -> Step 2.


3-73



3.1.93 198105034 Back card of LogService board is offline

Alarm Information

Code: 198105034

Name: Back card of LogService board is offline

Severity: Minor


Alarm Description

The log server board detects that the corresponding rear card is offline.

Alarm Cause

l The rear card corresponding to the log server board is not present.

l The rear card has a poor contact with the log server board.

l The hardware of the rear card corresponding to the log server board is faulty.

Impact

The link between the log server and OMM server is interrupted, and the OMM fails to obtain the

signaling tracing data or performance statistics data.

Action

1. Check whether the rear card is installed in the physical location where the alarm arises.

Yes -> Step 3.

No -> Step 2.

2. Install the rear card into the corresponding slot, and check whether the alarm is cleared.

Yes -> End.

No -> Step 3.

3. Remove and reinstall the rear card, and check whether the alarm is cleared.

Yes -> End.

No -> Step 4.

4. Replace the rear card with an operational one, and check whether the alarm is cleared.

Yes -> End.

No -> Step 5.


3-74


Chapter 3 Alarms

3.1.94 198105036 The hard disk of LogService error

Alarm Information

Code: 198105036

Name: The hard disk of LogService error

Severity: Minor


Alarm Description

The log server board detects a disk failure.

Alarm Cause

l The SMART parameter of the hard disk on the log server is not correctly set.

l The RAID1 level of the hard disk on the log server is degraded.

Impact

A faulty hard disk has no effect on the system. If the backup hard disk also fails, the log server

cannot operate properly.

Action

1. Determine the location of the abnormal hard disk in accordance with "Error hardware disk

location" in the alarm information.[[Replace the hard disk with an operational one]], and check

whether the alarm is cleared.

Yes -> End.

No -> Step 2.


3.1.95 198105037 Too high hard disk partition usage rate

Alarm Information

Code: 198105037

Name: Too high hard disk partition usage rate

Severity: Minor


Alarm Description

The log server board detects that the disk partition usage is too high.

3-75



Alarm Cause

The usage of the hard disk partition on the log server exceeds the threshold (95 percent).

Impact

The disk partition space is insufficient, causing the log server not to operate properly.

Action

Contact the next level of maintenance support.

3.1.96 198105039 Bursty flow rate of the control plane for shelfconnection overload

Alarm Information

Code: 198105039

Name: Bursty flow rate of the control plane for shelf connection overload

Severity: Major


Alarm Description

The base station controller detects that a burst of the control-plane inter-shelf flow

exceeds the overload threshold (Bglobal(Bglobal).Stream Overload threshold of Trunk

Port(trunkPortOverLoadThr)) .

Alarm Cause

l The overload threshold is too small.

l A large amount of traffic is processed at the same time.

l The inter-shelf physical connections are not operating properly.

Impact

A burst of control-plane inter-shelf flow triggers the overload control in the system, causing new users

not to be connected to the system.

3-76


Chapter 3 Alarms

Action

1. Check whether the setting ("BGlobal(Bglobal)". "Stream Overload threshold of Trunk

Port(trunkPortOverLoadThr)") is below the default (90).

Yes -> Step 2.

No -> Step 3.

2. Modify the configuration, and check whether the alarm is cleared.

Yes -> End.

No -> Step 3.

3. Check whether the physical cable for interconnecting the inter-shelf control plan is damaged

or the corresponding port is loose.

Yes -> Step 5.

No -> Step 4.

4. Secure the cable or replace the cable with an operational one, and check whether the alarm

is cleared.

Yes -> End.

No -> Step 5.

5. Check whether the CHUB board is used as the inter-shelf interconnection board.

Yes -> Step 6.

No -> Step 7.

6. Replace the CHUB board with the THUB board (the CHUB board supports lower bandwidth, and

therefore the THUB board is recommended in capacity expansion). Check whether the alarm

is cleared.

Yes -> End.

No -> Step 7.


3.1.97 198028672 80g chip abnormal

Alarm Information

l Alarm code: 198028672l Name: 80g chip abnormall Alarm severity: Criticall Alarm type: Equipment alarm

Alarm Description

Alarm Cause

80g detects that the GLIQP board restarts, or the 80g chip is abnormal.

3-77



Impact

Media plane messages are partially lost or unavailable.

Action

Restart the board for which the alarm is reported. Replace the board with a good one if the alarm still

exists. Contact the next level of maintenance support. if replacing the board does not work.

3.1.98 198005657 Error of LVDS path frame detection

Alarm Information

l Alarm code: 198005657l Name: Error of LVDS path frame detectionl Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

There are no frame heads on the LVDS channel, or the 257th and the 258th time slot are not 0xf1 or

0xba with frame heads on the LVDS channel

Alarm Cause

Error occurs in LVDS path frame detection

Impact

The board might not work normally.

Action

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

2. Connect the fiber in place or replace it with anther one, and check 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.

3.1.99 198005658 Failure in diagnosing link loop back of large Tnetwork

Alarm Information

l Alarm code: 198005658

3-78


Chapter 3 Alarms

l Name: Failure in diagnosing link loop back of large T networkl Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

It is wrong about the 129th time slot loop of LVDS between logic TSNB and TFI

Alarm Cause

The 129th time slot loop back of LVDS has a failure.

Impact

The board does not work normally.

Action

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

2. Connect the fiber in place or replace it with anther one, and check 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.

3.1.100 198025601 TSNB internal connection chip fault

Alarm Information

l Alarm code: 198025601l Name: TSNB internal connection chip faultl Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

error connection on 129ts of TSNB board

Alarm Cause

Connection chip (73273/73260) faults on TDM Switch Network Board cause some 129 time slots of

HW having connection faults.

Impact

If the fault occurs on master board, board state will be changed to slave; slave board will be reset

immediately.

3-79



Action

1. Try to replace the board and check if the alarm is eliminated.


3.1.101 198066033 T-net center is fault

Alarm Information

l Alarm code: 198066033l Name: T-net center is faultl Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

T-net center is fault

Alarm Cause

The big T-net center board has a fault.

Impact

T-net related resource is unavailable.

Action

1. Replace the slot.


3.1.102 198005660 Physical link down between master port andslave port

Alarm Information

l Alarm code: 198005660l Name: Physical link down between master port and slave portl Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

Physical link down between master port and slave port

3-80


Chapter 3 Alarms

Alarm Cause

The running physical link between the master and the slave port is broken.

Impact

APS function disabled

Action

1. Change another slot and check whether the alarm disappears.

Y->End.

N->Go to Step 2.

2. Change the board and check whether the alarm disappears.

Y->End.

N->Contact the next level of maintenance support.

3.1.103 198005641 Port Link Down

Alarm Information

l Alarm code: 198005641l Name: Port Link Downl Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

port link down

Alarm Cause

There is something wrong with the internal chip.

Impact

DSP is abnormal and call loss increases.

Action

1. Reset the corresponding DSP chip or the board by using MML command on the background and

then check the alarm is eliminated.


3-81



3.1.104 198019715 MS APS channel gets errors

Alarm Information

l Alarm code: 198019715l Name: MS APS channel gets errorsl Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

APS channel between master and slave board gets errors

Alarm Cause

1. APS Channel between Master and Slave Board gets hardware fault.

2. The connection on the backplane between the slot and the neighboring slot gets errors.

Impact

1. ASP function is affected.

2. The board master/slave function is affected.

Action



3. Replace the neighboring board.

4. Replace the slots .

3.1.105 198087340 FR device failure

Alarm Information

l Alarm code: 198087340l Name: FR device failurel Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

This alarm is reported if a board detects that the FR link is faulty.

3-82


Chapter 3 Alarms

Alarm Cause

N392 ("Brch(GFrGbBrch)"."N392(N392)") errors are detected in the last N393

("Brch(GFrGbBrch)"."N393(N393)") STATUS ENQUIRY events.

Impact

The Gb bear channel corresponding to this alarm is blocked and the Gb bandwidth is decreased.

In this case, PS traffic congestion may occur.

Action

1. According to the board's physical position and PCM number ("Port") in the alarm details,

check whether the configuration of "E1 Port(E1Port)"."E1 Frame Type(Crc4Mode)" of the PCM

link ("Brch(GFrGbBrch)"."Used Gb Interface Pcm(refGGbPcm)") on the Gb interface board is

consistent with that of the SGSN.

Yes -> Step 3.

No -> Step 2.

2. Modify the configuration of "E1 Frame Type" for the PCM link on the Gb interface board to ensure

the consistency with that of the SGSN, and then check whether this alarm is cleared.

Yes -> End.

No -> Step 3.

3. Check whether the configurations of "PCM TS(StartTs)" and "Access rate"(GFrGbBrch.AR)" in the

"Brch(GFrGbBrch)" configuration parameter of the BSC are consistent with those of the SGSN.

Yes -> Step 5.

No -> Step 4.

4. Modify the two parameters for consistency between the BSC and the SGSN, and check whether

the alarm is cleared.

Yes -> End.

No -> Step 5.

5. Check whether the E1 port corresponding to the bear channel reports an alarm.

Yes -> Step 6.

No -> Step 7.

6. Handle the transmission device alarm, and check whether this alarm is cleared.

Yes -> End.

No -> Step 7.

7. Perform a physical self-loop check on the local E1 terminal device, and check whether the E1 line

operates properly (the green light flashes slowly).

Yes -> Step 9.

No -> Step 8.

8. Replace the E1 line, and check whether the alarm is cleared.

Yes -> End.

No -> Step 9.

9. Contact SGSN maintenance personnel to check whether the peer E1 line operates properly.

Yes -> Step 11.

No -> Step 10.

3-83



10. Contact SGSN maintenance personnel to troubleshoot the SGSN equipment, and check whether


Yes -> End.

No -> Step 11.

11. Replace the faulty board, and check whether the alarm is cleared.

Yes -> End.

No -> Step 12.


3.1.106 198087341 FR congestion

Alarm Information

l Alarm code: 198087341l Name: FR congestionl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

This alarm is reported if a board detects that the FR link is congested.

Alarm Cause

In case of intermediate Frame Relay networking, for a specific NSVC, the number of frames with the

BECN bit of "1" is more than or equal to the number of frames with the BECN bit of "0" in a 10-second

interval. (The peer end may be overloaded or be configured improperly.)

Impact

Quality of PS services for some of users may be degraded, or new users fail to access the services.

Action

1. According to network planning, add a new "Brch(GFrGbBrch)", or increase the existing

"Brch(GFrGbBrch)"."Access rate(AR)", and check whether the alarm is cleared.

Yes -> End.

No -> Step 2.


3-84


Chapter 3 Alarms

3.1.107 198087352 NSVC's E1 failure alarm

Alarm Information

l Alarm code: 198087352l Name: NSVC's E1 failure alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

This alarm is reported if a board detects that the NSVC link in E1 is faulty.

Alarm Cause

NS Alive Ack cannot be received several consecutive times (GBssFunction.NSAliveMax) during the

NS Alive procedure.

Impact

For single NSVC link configuration, the PS service is interrupted.

For multi-NSVC link configuration, the bandwidth is decreased. In this case, PS traffic congestion

may occur.

Action

1. Check whether the configuration of "NSEI" and "NSVCI" in the alarm details is consistent with

that of the SGSN.

Yes -> Step 3.

No -> Step 2.

2. Search the parent object "Frame relay Nse(GFrGbNse)" and modify "Nse ID(GFrGbNseSeq)".

Modify the configuration of "NSVCI(GFrGbNsvcSeq)" according to the alarm object "Frame relay

Nsvc(GFrGbNsvc)" for consistency with that of the SGSN, and check whether the alarm is cleared.

Yes -> End.

No -> Step 3.

3. Check whether the following alarm arises:

198087340 FR device failure

Yes -> Step 4.

No -> Step 5.

4. Handle the above alarm, and check whether this alarm is cleared.

Yes -> End.

No -> Step 5.


3-85



3.1.108 198087465 NSVC's IP failure alarm

Alarm Information

l Alarm code: 198087465l Name: NSVC's IP failure alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

This alarm is reported if a board detects that the NSVC link in IP is faulty.

Alarm Cause

NS Alive Ack cannot be received several consecutive times (GBssFunction.NSAliveMax) during the

NS Alive procedure.

Impact

For single NSVC link configuration, the PS service is interrupted. For multi-NSVC link configuration,

the bandwidth is decreased. In this case, PS traffic congestion may occur.

Action

1. Check whether the configuration of "NSEI" in the alarm details is consistent with that of the SGSN.

Yes -> Step 3.

No -> Step 2.

2. Modify the configuration of the parameter "Nse ID(GIpGbNseSeq)" of the object "IP

Nse(GIpGbNse)" for consistency with that of the SGSN, and check whether the alarm is cleared.

Yes -> End.

No -> Step 3.

3. Check whether alarms arise on the Gb interface board.

Yes -> Step 4.

No -> Step 5.

4. Handle the related alarms, and check whether this alarm is cleared.

Yes -> End.

No -> Step 5.

5. Contact the maintenance personnel of the transmission or peer device to check whether the

transmission or peer device is faulty.

Yes -> Step 6.

No -> Step 7.

6. Remove the faults, and check whether the alarm is cleared.

Yes -> End.

No -> Step 7.


3-86


Chapter 3 Alarms

3.1.109 198087458 PS cell block caused by slave

Alarm Information

l Alarm code: 198087458l Name: PS cell block caused by slavel Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

This alarm is reported if the BSC detects the PS process unit failure.

Alarm Cause

A PS process unit failure occurs.

Impact

Data services are not available in the cell.

Action

1. Wait for five minutes, and check whether the alarm is cleared automatically.

Yes -> End.

No -> Step 2.

2. Execute the QRY PSCELLDSPcommand based on "Site ID" and "Bts ID" in the alarm details to

query the corresponding SLAVE of the cell. Execute the QRY SUNITSTATUScommand based

on "Sub System number", "RUP board number", and "SLAVE number" in the returned results

to query the status of the sub-unit.

"Manual block" status -> Step 3.

Other status -> Step 4.

3. Unblock the PS processing sub-unit. Check whether the alarm is cleared.

Yes -> End.

No -> Step 4.

4. Reset the PS processing sub-unit, wait for two minutes, and then check whether the alarm

is cleared.

Yes -> End.

No -> Step 5.


3.1.110 198087000 Dry contact alarm 1

Alarm Information


3-87



l Name: Dry contact alarm 1l Alarm severity: Unknownl Alarm type: Equipment alarm

Alarm Description

Dry contact alarm 1

Alarm Cause

None

Impact

User-defined.

Action

None


Alarm Information

l Alarm code: 198087001l Name: Dry contact alarm 2l Alarm severity: Unknownl Alarm type: Equipment alarm

Alarm Description

Dry contact alarm 2

Alarm Cause

None

Impact

User-defined.

Action

None

3-88


Chapter 3 Alarms


Alarm Information


Alarm Description

Dry contact alarm 3

Alarm Cause

None

Impact

User-defined.

Action

None


Alarm Information


Alarm Description

Dry contact alarm 4

Alarm Cause

None

Impact

User-defined.

3-89



Action

None


Alarm Information


Alarm Description

Dry contact alarm 5

Alarm Cause

None

Impact

User-defined.

Action

None


Alarm Information


Alarm Description

Dry contact alarm 6

Alarm Cause

None

3-90


Chapter 3 Alarms

Impact

User-defined.

Action

None


Alarm Information


Alarm Description

Dry contact alarm 7

Alarm Cause

None

Impact

User-defined.

Action

None


Alarm Information


Alarm Description

Dry contact alarm 8

3-91



Alarm Cause

None

Impact

User-defined.

Action

None


Alarm Information


Alarm Description

Dry contact alarm 9

Alarm Cause

None

Impact

User-defined.

Action

None


Alarm Information


3-92


Chapter 3 Alarms

Alarm Description

Dry contact alarm 10

Alarm Cause

None

Impact

User-defined.

Action

None


Alarm Information


Alarm Description


Alarm Cause

None

Impact

User-defined.

Action

None


Alarm Information


3-93



l Name: Dry contact alarm 12l Alarm severity: Unknownl Alarm type: Equipment alarm

Alarm Description


Alarm Cause

None

Impact

User-defined.

Action

None

3.1.122 198087012 EAM dry contact 1 alarm

Alarm Information

l Alarm code: 198087012l Name: EAM dry contact 1 alarml Alarm severity: Unknownl Alarm type: Equipment alarm

Alarm Description

EAM dry contact 1 alarm

Alarm Cause

None

Impact

User-defined.

Action

None

3-94


Chapter 3 Alarms


Alarm Information


Alarm Description


Alarm Cause

None

Impact

User-defined.

Action

None


Alarm Information


Alarm Description


Alarm Cause

None

Impact

User-defined.

3-95



Action

None


Alarm Information


Alarm Description


Alarm Cause

None

Impact

User-defined.

Action

None


Alarm Information


Alarm Description


Alarm Cause

None

3-96


Chapter 3 Alarms

Impact

User-defined.

Action

None


Alarm Information


Alarm Description


Alarm Cause

None

Impact

User-defined.

Action

None


Alarm Information


Alarm Description


3-97



Alarm Cause

None

Impact

User-defined.

Action

None


Alarm Information


Alarm Description


Alarm Cause

None

Impact

User-defined.

Action

None

3.1.130 198087102 Power overvoltage/undervoltage alarm

Alarm Information

l Alarm code: 198087102l Name: Power overvoltage/undervoltage alarml Alarm severity: Minorl Alarm type: Equipment alarm

3-98


Chapter 3 Alarms

Alarm Description

Power overvoltage/undervoltage alarm

Alarm Cause

CMM/CMB power voltage is out of adjustment range

Impact

The CMM/CMB boards do not operate properly.

Action

please replace CMM/CMB board as soon as possible

3.1.131 198087103 13M input clock failure

Alarm Information

l Alarm code: 198087103l Name: 13M input clock failurel Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

13M input clock failure

Alarm Cause

CMM/CMB clock unit works abnormally

Impact

A transmission link inside the BTS is disconnected, frame numbers are confused, and the frequency

synthesizer does not operate properly.

Action

1)Test transmission index. If the transmission continuously has over-2Hz frequency offset in

4 seconds or the single frequency adjustment is more than 4 Hz for 15 times in 6 minutes, it is

necessary to notify the engineer to adjust transmission.

2)Reset CMB board and check whether the alarm disappears.

3)If the alarm does not disappear, replace CMB board.

3-99



3.1.132 198087106 SYNCLK clock failure

Alarm Information

l Alarm code: 198087106l Name: SYNCLK clock failurel Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

SYNCLK clock failure

Alarm Cause

CMM/CMB clock unit works abnormally

Impact

A transmission link inside the BTS is disconnected, frame numbers are confused, and the frequency

synthesizer does not operate properly.

Action

1)Test transmission index. If the transmission continuously has over-2Hz frequency offset in

4 seconds or the single frequency adjustment is more than 4 Hz for 15 times in 6 minutes, it is

necessary to notify the engineer to adjust transmission.

2)Reset CMB board and check whether the alarm disappears.

3)If the alarm does not disappear, replace CMB board.

3.1.133 198087107 Master and slave communication link failure

Alarm Information

l Alarm code: 198087107l Name: Master and slave communication link failurel Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

Master and slave communication link failure

3-100


Chapter 3 Alarms

Alarm Cause

Standby CMM/CMB board is not powered on, or active-standby CMM/CMB board communication

error

Impact

The master and slave CMM/CMB boards fail to be switched over.

Action

1. Re-plug CMB board.

2. If the software has problem, upgrade it.

3.1.134 198087108 Standby CMM/CMB board not present

Alarm Information

l Alarm code: 198087108l Name: Standby CMM/CMB board not presentl Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

Standby CMM/CMB board not present

Alarm Cause

Standby CMM/CMB board is not inserted

Impact

The system is less reliable because the faulty master board fails to be switched over to the slave

board.

Action

check if standby board is present in the rack. If it is , reset or insert standby board again( normal

state of standby board is that power lamp always lights and running lamp always lights);if it isn't,

insert a new CMM/CMB board

3-101



3.1.135 198087109 Standby CMM/CMB board abnormal

Alarm Information

l Alarm code: 198087109l Name: Standby CMM/CMB board abnormall Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

Standby CMM/CMB board abnormal

Alarm Cause

Standby CMM/CMB board starts abnormally or not inserted properly

Impact

The master and slave boards fail to be switched over.

Action

Check whether the spare board is on the rack. If yes, reset or re-plug the board ( it is in the normal

condition if the power LED indicator and RUN LED indicator are both on). If no, plug in the new

CMB board if necessary.

3.1.136 198087110 CMM/CMB power failure alarm

Alarm Information

l Alarm code: 198087110l Name: CMM/CMB power failure alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

CMM/CMB power failure alarm

Alarm Cause

CMM/CMB board is power off

Impact

The CMM/CMB boards fail to operate.

3-102


Chapter 3 Alarms

Action

E1 interface will bridge-connect automatically. Replace the CMB circuit board as quickly as possible.

3.1.137 198087112 Communication link alarm between master andslave rack (left)

Alarm Information

l Alarm code: 198087112l Name: Communication link alarm between master and slave rack (left)l Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

Communication link alarm between master and slave rack (left)

Alarm Cause

Communication link fault between master rack and slave rack

Impact

The site fails to load, operate or maintain data and software.

Action

1. Check if line between racks is connected. if it has problems, connect or replace it. 2. start

self-check of master-slave rack communication to confirm the problem of CMM/CMB hardware

or software. then replace it

3.1.138 198087113 Communication link alarm between master andslave rack (right)

Alarm Information

l Alarm code: 198087113l Name: Communication link alarm between master and slave rack (right)l Alarm severity: Warningl Alarm type: Equipment alarm

3-103



Alarm Description

Communication link alarm between master and slave rack (right)

Alarm Cause

Communication link fault between master rack and slave rack

Impact

The site fails to load, operate or maintain data and software.

Action

1. Check if line between racks is connected. if it has problems, connect or replace it. 2. start

self-check of master-slave rack communication to confirm the problem of CMM/CMB hardware

or software. then replace it

3.1.139 198087114 A interface E1 Rx carrier alarm

Alarm Information

l Alarm code: 198087114l Name: A interface E1 Rx carrier alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

A interface E1 Rx carrier alarm

Alarm Cause

Chip fault, clock abnormal, difference from BSC clock, or bad E1 connections, etc

Impact

This fault has a little impact on calls if it does not occur frequently. However, errors may occur during

a call or the link establishment between the TRM/DTRU and the BSC if this alarm occurs frequently

(for example, at intervals of several minutes).

3-104


Chapter 3 Alarms

Action

1. Check the electric-connection performance of E1 line.

2. if E1 line has no problem, insert the board tightly and reset.

3. if alarm still exists, maybe E1 interface chip is abnormal.

4. if chip's self-check is passed, start loop test of E1 interface.

5. if loop test of E1 is correct, the transport has problems

3.1.140 198087115 A interface E1 Rx frame not synchronized

Alarm Information

l Alarm code: 198087115l Name: A interface E1 Rx frame not synchronizedl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

A interface E1 Rx frame not synchronized

Alarm Cause

Chip fault, clock abnormal, difference from BSC clock, bad E1 connections, or CMM board not

support C/F configuration, etc

Impact




Action



3.if C/F Trunk alarm happens, please check Whether CMM board hardware version is 030903 or

030900, and if so, it need be changed to 030508 version.( this situation only suitable for Site V2

serials).


5. if chip's self-check is passed, start loop test of E1 interface. 6. if loop test of E1 is correct, the

transport has problems.

3-105



3.1.141 198087120 A interface E1 remote alarm

Alarm Information

l Alarm code: 198087120l Name: A interface E1 remote alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

A interface E1 remote alarm

Alarm Cause

Sending line is shorted, the remote end might not receive data sent from local end

Impact

The BTS fails to provide services.

Action

1.Check the electrical connection property of the E1 cable.2. If the cable of E1 did not have problems,

insert the board tightly and resetting.3.If the warning continue to exist, the E1 interface chip maybe is

in abnormal.4. If can pass the chip selftest, can start the selfloop test procedure for E1 interface.5.If

the selfloop test result is correct, can think that the transmission equipment have problems.

3.1.142 198087121 B interface E1 Rx carrier alarm

Alarm Information

l Alarm code: 198087121l Name: B interface E1 Rx carrier alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

B interface E1 Rx carrier alarm

Alarm Cause


3-106


Chapter 3 Alarms

Impact




Action






3.1.143 198087122 B interface E1 Rx frame not synchronized

Alarm Information

l Alarm code: 198087122l Name: B interface E1 Rx frame not synchronizedl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

B interface E1 Rx frame not synchronized

Alarm Cause



Impact




3-107



Action



3. if C/F Trunk alarm happens, please check Whether CMM board hardware version is 030903

or 030900, and if so, it need be changed to 030508 version.( this situation only suitable for Site

V2 serials).




3.1.144 198087127 B interface E1 remote alarm

Alarm Information

l Alarm code: 198087127l Name: B interface E1 remote alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

B interface E1 remote alarm

Alarm Cause


Impact


Action





3.1.145 198087128 C interface E1 Rx carrier alarm

Alarm Information

l Alarm code: 198087128l Name: C interface E1 Rx carrier alarm

3-108


Chapter 3 Alarms

l Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

C interface E1 Rx carrier alarm

Alarm Cause


Impact




Action






3.1.146 198087129 C interface E1 Rx frame not synchronized

Alarm Information

l Alarm code: 198087129l Name: C interface E1 Rx frame not synchronizedl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

C interface E1 Rx frame not synchronized

Alarm Cause



3-109



Impact




Action





serials).




3.1.147 198087134 C interface E1 remote alarm

Alarm Information

l Alarm code: 198087134l Name: C interface E1 remote alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

C interface E1 remote alarm

Alarm Cause


Impact


Action





3-110


Chapter 3 Alarms

3.1.148 198087135 D interface E1 Rx carrier alarm

Alarm Information

l Alarm code: 198087135l Name: D interface E1 Rx carrier alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

D interface E1 Rx carrier alarm

Alarm Cause


Impact




Action






3.1.149 198087136 D interface E1 Rx frame not synchronized

Alarm Information

l Alarm code: 198087136l Name: D interface E1 Rx frame not synchronizedl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

D interface E1 Rx frame not synchronized

3-111



Alarm Cause



Impact




Action





serials).



6. if loop test of E1 is correct, the transport has problems.

3.1.150 198087141 D interface E1 remote alarm

Alarm Information

l Alarm code: 198087141l Name: D interface E1 remote alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

D interface E1 remote alarm

Alarm Cause


Impact


3-112


Chapter 3 Alarms

Action





3.1.151 198087142 E interface E1 Rx carrier alarm

Alarm Information

l Alarm code: 198087142l Name: E interface E1 Rx carrier alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

E interface E1 Rx carrier alarm

Alarm Cause


Impact




Action






3.1.152 198087143 E interface E1 Rx frame not synchronized

Alarm Information

l Alarm code: 198087143l Name: E interface E1 Rx frame not synchronizedl Alarm severity: Minor

3-113



l Alarm type: Equipment alarm

Alarm Description

E interface E1 Rx frame not synchronized

Alarm Cause



Impact




Action





serials).




3.1.153 198087148 E interface E1 remote alarm

Alarm Information

l Alarm code: 198087148l Name: E interface E1 remote alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

E interface E1 remote alarm

Alarm Cause


3-114


Chapter 3 Alarms

Impact


Action





3.1.154 198087149 F interface E1 Rx carrier alarm

Alarm Information

l Alarm code: 198087149l Name: F interface E1 Rx carrier alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

F interface E1 Rx carrier alarm

Alarm Cause


Impact




Action






3-115



3.1.155 198087150 F interface E1 Rx frame not synchronized

Alarm Information

l Alarm code: 198087150l Name: F interface E1 Rx frame not synchronizedl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

F interface E1 Rx frame not synchronized

Alarm Cause



Impact




Action

1. Check the electric-connection performance of E1 line. 2. if E1 line has no problem, insert the board

tightly and reset. 3.if C/F Trunk alarm happens, please check Whether CMM board hardware version

is 030903 or 030900, and if so, it need be changed to 030508 version.( this situation only suitable for

Site V2 serials). 4. if alarm still exists, maybe E1 interface chip is abnormal. 5. if chip's self-check is

passed, start loop test of E1 interface. 6. if loop test of E1 is correct, the transport has problems.

3.1.156 198087153 F interface E1 Rx forward sliding indication

Alarm Information

l Alarm code: 198087153l Name: F interface E1 Rx forward sliding indicationl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

F interface E1 Rx forward sliding indication

3-116


Chapter 3 Alarms

Alarm Cause


Impact




Action


tightly and reset. 3. if alarm still exists, maybe E1 interface chip is abnormal. 4. if chip's self-check is

passed, start loop test of E1 interface. 5. if loop test of E1 is correct, the transport has problems

3.1.157 198087155 F interface E1 remote alarm

Alarm Information

l Alarm code: 198087155l Name: F interface E1 remote alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

F interface E1 remote alarm

Alarm Cause


Impact


Action





3-117



3.1.158 198087156 G interface E1 Rx carrier alarm

Alarm Information

l Alarm code: 198087156l Name: G interface E1 Rx carrier alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

G interface E1 Rx carrier alarm

Alarm Cause


Impact




Action




3.1.159 198087157 G interface E2 Rx frame not synchronized

Alarm Information

l Alarm code: 198087157l Name: G interface E2 Rx frame not synchronizedl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

G interface E2 Rx frame not synchronized

Alarm Cause


3-118


Chapter 3 Alarms

Impact




Action




3.1.160 198087162 G interface E1 remote alarm

Alarm Information

l Alarm code: 198087162l Name: G interface E1 remote alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

G interface E1 remote alarm

Alarm Cause


Impact


Action





3.1.161 198087163 H interface E1 Rx carrier alarm

Alarm Information


3-119



l Name: H interface E1 Rx carrier alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

H interface E1 Rx carrier alarm

Alarm Cause


Impact




Action




3.1.162 198087164 H interface E3 Rx frame not synchronized

Alarm Information

l Alarm code: 198087164l Name: H interface E3 Rx frame not synchronizedl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

H interface E3 Rx frame not synchronized

Alarm Cause


Impact




3-120


Chapter 3 Alarms

Action




3.1.163 198087169 H interface E1 remote alarm

Alarm Information

l Alarm code: 198087169l Name: H interface E1 remote alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

H interface E1 remote alarm

Alarm Cause


Impact


Action





3.1.164 198087170 Temperature alarm

Alarm Information

l Alarm code: 198087170l Name: Temperature alarml Alarm severity: Warningl Alarm type: Equipment alarm

3-121



Alarm Description

Temperature alarm

Alarm Cause

Fan fault or module temperature too high

Impact

User-defined.

Action

check the envirnment temperature.if it conforms to the demand, keep on observing and keep normal

status in the case of other modules no fault. If not , please change it.if there are some other problems,

please replace FCM module

3.1.165 198087171 Fan absent

Alarm Information

l Alarm code: 198087171l Name: Fan absentl Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

Fan absent

Alarm Cause

Fan not inserted or not in position

Impact

User-defined.

Action

check the fan

3-122


Chapter 3 Alarms

3.1.166 198087172 Fan control board CPU alarm

Alarm Information

l Alarm code: 198087172l Name: Fan control board CPU alarml Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

Fan control board CPU alarm

Alarm Cause

CPU fault

Impact

User-defined.

Action

1. check the line and correct it. 2. check the fan and replace FCM.

3.1.167 198087173 Fan alarm

Alarm Information

l Alarm code: 198087173l Name: Fan alarml Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

Fan alarm

Alarm Cause

Fan stops rotating due to fault

Impact

User-defined.

3-123



Action

1. check the line and correct it.

2. check the fan and replace FCM.

3. check if collecting-alarm circuit of TPU is correct. Otherwise replace TRM module.

3.1.168 198087174 Fan temperature alarm

Alarm Information

l Alarm code: 198087174l Name: Fan temperature alarml Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

Fan temperature alarm

Alarm Cause


Impact

Performance is reduced due to too high temperature of the TRM/DTRU boards.

Action

Check the environment temperature meets the requirement or not.If meet the requirement, under the

premise that other modules have not fault, can continue to observe, and keep the normal work. If not

meet the requirement, then improving the equipments working environment is needed. If break down,

then should replace the FCM module immediately.

3.1.169 198087175 Fan 1 alarm

Alarm Information

l Alarm code: 198087175l Name: Fan 1 alarml Alarm severity: Warningl Alarm type: Equipment alarm

3-124


Chapter 3 Alarms

Alarm Description

Fan 1 alarm

Alarm Cause


Impact

Too high temperature is generated on the TRX shelf in the same layer.

Action

Check the alarm circuit have fault or not, if have problem, then resolve it.

2. Check the fan has fault or not. If have problem, then replace the FCM.

3. Check the alarm sampling electric circuit of TPU is good or not, otherwise replacing the

corresponding DTRM module

3.1.170 198087176 Fan 2 alarm

Alarm Information

l Alarm code: 198087176l Name: Fan 2 alarml Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

Fan 2 alarm

Alarm Cause


Impact

Too high temperature is generated on the TRX shelf in the same layer.

Action

Check the alarm circuit have fault or not, if have problem, then resolve it.2. Check the fan has fault or

not. If have problem, then replace the FCM.3. Check the alarm sampling electric circuit of TPU is

good or not, otherwise replacing the corresponding DTRM module

3-125



3.1.171 198087177 Fan control board alarm

Alarm Information

l Alarm code: 198087177l Name: Fan control board alarml Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

Fan control board alarm

Alarm Cause


Impact


Action

Check the environment temperature meets the request or not.If meet the request, under the premise

that other modules have not fault, can continue to observe, and keep the normal work. If not meet

the request, then improving the equipments working environment is needed. If break down, then

should replace the FCM module immediately.

3.1.172 198087178 LNA alarm

Alarm Information

l Alarm code: 198087178l Name: LNA alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

LNA alarm

Alarm Cause

LNA current exceeds by 30%

3-126


Chapter 3 Alarms

Impact

User-defined.

Action

please replace AEM module as soon as possible.

3.1.173 198087179 Tower amplifier power alarm

Alarm Information

l Alarm code: 198087179l Name: Tower amplifier power alarml Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

Tower amplifier power alarm

Alarm Cause

AEM tower amplifier power alarm

Impact

User-defined.

Action

please replace Tower Amplifier module or AEM module as soon as possible.

3.1.174 198087180 SWR of AEM HYCOM minor alarm

Alarm Information

l Alarm code: 198087180l Name: SWR of AEM HYCOM minor alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

SWR of AEM HYCOM minor alarm

3-127



Alarm Cause

Combiner SWR 1.5 alarm

Impact

User-defined.

Action

keep on observing.if normal work isn't influenced, don't replace AEM module.

3.1.175 198087181 SWR of AEM HYCOM major alarm

Alarm Information

l Alarm code: 198087181l Name: SWR of AEM HYCOM major alarml Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

SWR of AEM HYCOM major alarm

Alarm Cause

Combiner SWR 3.0 alarm

Impact

User-defined.

Action

please replace AEM and reset TRM which connects with this AEM.

3.1.176 198087182 AEM power alarm(BTS V2)

Alarm Information

l Alarm code: 198087182l Name: AEM power alarm(BTS V2)l Alarm severity: Majorl Alarm type: Equipment alarm

3-128


Chapter 3 Alarms

Alarm Description

AEM power alarm(BTS V2)

Alarm Cause

AEM power alarm

Impact

User-defined.

Action

please replace AEM module as soon as possible.

3.1.177 198087183 AEM type alarm(BTS V2)

Alarm Information

l Alarm code: 198087183l Name: AEM type alarm(BTS V2)l Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

AEM type alarm(BTS V2)

Alarm Cause

AEM type alarm

Impact

User-defined.

Action

check whether config type of AEM doesn't conform to actual type, whether insert tightly and poweron.

If not, please replace it.if type is correct, problem maybe is the fault of back panel transport or the

fault of TPU collecting circuit, please replace the cable or the module.

3-129



3.1.178 198087184 AEM absent(BTS V2)

Alarm Information

l Alarm code: 198087184l Name: AEM absent(BTS V2)l Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

AEM absent(BTS V2)

Alarm Cause

AEM not-in-position alarm

Impact

User-defined.

Action

please replace AEM and reset TRM which connects with this AEM.

3.1.179 198087185 AEM power alarm

Alarm Information

l Alarm code: 198087185l Name: AEM power alarml Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

AEM power alarm

Alarm Cause

AEM power alarm

Impact

This fault has an impact on transmission.

3-130


Chapter 3 Alarms

Action

( 1)Check whether there is PA temperature alarm or fan environment temperature alarm on the

background. If yes, deal with the fan alarm first. It is necessary to plug in the blank module if there is

no TRX on the right side of TRM board.

( 2)Check whether the fuse of CDU is damaged. If yes, replace it. ( Note: FU1 2A, FU2 1A)

( 3)Pull out of CDU and DTRU modules in the same layer. Check whether the pins on the rear board

are bent. If yes, change the slot or replace the rear board. After that, re-power on and check whether

the alarm is recovered. ( If changing the slot, it is necessary to re-configure on the background.)

( 4)Replace CDU.

3.1.180 198087186 LNA0 alarm

Alarm Information

l Alarm code: 198087186l Name: LNA0 alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

LNA0 alarm

Alarm Cause

LNA0 current exceeds by 30%

Impact

The connected DTRU board fails to operate (both master and diversity LNAs are faulty) or does not

operate fully (only one LNA is faulty).

Action







( 3)Replace CDU.

3-131



3.1.181 198087187 LNA1 alarm

Alarm Information

l Alarm code: 198087187l Name: LNA1 alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

LNA1 alarm

Alarm Cause

LNA1 current exceeds by 30%

Impact

The connected DTRU board fails to operate (both master and diversity LNAs are faulty) or does not

operate fully (only one LNA is faulty).

Action







( 3)Replace CDU.

3.1.182 198087188 Tower Amplifier0 power alarm

Alarm Information

l Alarm code: 198087188l Name: Tower Amplifier0 power alarml Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

Tower Amplifier0 power alarm

3-132


Chapter 3 Alarms

Alarm Cause

AEM tower amplifier 0 power alarm

Impact

This fault has an impact on the uplink receive sensitivity of the related DTRU board.

Action




( 2)Pull off PA power cable. The position of PA power cable: open the BTS rear cover and pull off the

socket with the label of TA_PWR X31 ( X31 PA_PWR for the old rack). The PA power cable connects

to PWRTA_Ln on the top of cabinet. Check whether the alarm disappears. The power cable is useless

in the place where no PA exists. In the place where PA exists, the alarm disappears. It is necessary

to check whether the short circuit exists between the power cable and PA or whether PA goes wrong.




( 4)Replace CDU and reset TRX connecting with it.

3.1.183 198087189 Tower Amplifier1 power alarm

Alarm Information

l Alarm code: 198087189l Name: Tower Amplifier1 power alarml Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

Tower Amplifier1 power alarm

Alarm Cause

AEM tower amplifier 1 power alarm

Impact

This fault has an impact on the uplink receive sensitivity of the related DTRU board.

3-133



Action




( 2)Pull off PA power cable. The position of PA power cable: open the BTS rear cover and pull off the

socket with the label of TA_PWR X31 ( X31 PA_PWR for the old rack). The PA power cable connects

to PWRTA_Ln on the top of cabinet. Check whether the alarm disappears. The power cable is useless

in the place where no PA exists. In the place where PA exists, the alarm disappears. It is necessary

to check whether the short circuit exists between the power cable and PA or whether PA goes wrong.





3.1.184 198087190 SWR of AEM HYCOM minor alarm

Alarm Information

l Alarm code: 198087190l Name: SWR of AEM HYCOM minor alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

SWR of AEM HYCOM minor alarm

Alarm Cause

Combiner SWR minor alarm

Impact


3-134


Chapter 3 Alarms

Action

( 1) Check whether the connection between RF jumper which connects DTRU with CDU and CDU

antenna mouth is tight. If the connection is loose, fasten it with tool. After that, reset the TRX and

check whether the alarm disappears.

( 2)Measure SWR of the jumper between CDU and antenna with SITEMASTER. Check whether the

SWR value exceeds standard. If yes, the antenna has fault. Check the antenna system part by part

upon the test result. Once the fault is found, fasten the antenna, make waterproof treatment on the

antenna and replace the antenna. Reset the TRX and check whether the alarm disappears.

( 3)Replace the RF cable which connects DTRU with CDU. Reset the TRX connecting with it and


( 4)Pull out of CDU and DTRU modules in the same layer. Check whether the pins on the rear

board are bent. If yes, replace the rear board. Check whether the alarm cable connector of CDU

is loose or off. If yes, fasten it and re-power it on. Three minutes after the TRX is running, check

whether the alarm disappears.


3.1.185 198087191 SWR of AEM HYCOM major alarm

Alarm Information

l Alarm code: 198087191l Name: SWR of AEM HYCOM major alarml Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

SWR of AEM HYCOM major alarm

Alarm Cause

Combiner SWR major alarm

Impact


3-135



Action

( 1) Check whether the connection between RF jumper which connects DTRU with CDU and CDU

antenna mouth is tight. If the connection is loose, fasten it with tool. After that, reset the TRX. Three

minutes after the TRX is running, check whether the alarm disappears.

( 2)Measure SWR of the jumper between CDU and antenna with SITEMASTER. Check whether the

SWR value exceeds standard. If yes, the antenna has fault. Check the antenna system part by

part upon the test result. Once the fault is found, fasten the antenna, make waterproof treatment

on the antenna and replace the antenna. Reset the TRX. Three minutes after the TRX is running,


( 3)Replace the RF cable which connects DTRU with CDU. Reset the TRX connecting with it. Three

minutes after the TRX is running, check whether the alarm disappears.

( 4)Pull out of CDU and DTRU modules in the same layer. Check whether the pins on the rear

board are bent. If yes, replace the rear board. Check whether the alarm cable connector is loose

or off. If yes, fasten it and re-power it on. Three minutes after the TRX is running, check whether

the alarm disappears.


3.1.186 198087192 AEM type alarm

Alarm Information

l Alarm code: 198087192l Name: AEM type alarml Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

AEM type alarm

Alarm Cause

AEM type alarm

Impact


3-136


Chapter 3 Alarms

Action




( 2)Check whether AEM configuration type is consistent with the actual type, and whether DTRU is

associated with the background, otherwise change or modify the background configuration.

( 3)Check whether AEM powers on, and plugged properly. Shut down AEM module power, plug off

and then plug in the module, turn on the power to check whether the alarm has been recovered.

( 4)Check whether the board DIP switch of AEM is correct. Otherwise, adjust the DIP switch till it is

correct. Check whether the fuse on CDU is broken, if so, change the fuse of the same model. Note:

FU1 2A, FU2 1A; power on the equipment to check whether the alarm is recovered.

( 5)Plug off the AEM and DTRU module of the same layer, check whether there backplane pin is

curved, if so, change the backplane and re-power on to check whether the alarm is recovered.

( 6)Plug in site id, and reset CMB. About five minutes later, check whether the alarm is recovered.

( 7)Replace AEM module.

3.1.187 198087193 AEM Not-in-position alarm

Alarm Information

l Alarm code: 198087193l Name: AEM Not-in-position alarml Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

AEM Not-in-position alarm

Alarm Cause

AEM not-in-position alarm

Impact


3-137



Action

( 1) Check whether there is PA temperature alarm or fan environmental temperature alarm, if so,

process with the fan alarm first. If there is no another TRX or blank module on the right side of the

TRX, plug in a blank module;

( 2) Check whether AEM configuration type is consistent with the actual type, and whether DTRU is

associated with the background, otherwise change or modify the background configuration.

( 3) Check whether AEM powers on, and plugged properly. Shut down AEM module power, plug off

and then plug in the module, turn on the power to check whether the alarm has been recovered.

( 4) Check whether the board DIP switch of AEM is correct. Otherwise, adjust the DIP switch till it is

correct. Check whether the fuse on CDU is broken, if so, change the fuse of the same model. Note:

FU1 2A, FU2 1A; power on the equipment to check whether the alarm is recovered.

( 5) Plug off the AEM and DTRU module of the same layer, check whether there backplane pin is

curved, if so, change the backplane and re-power on to check whether the alarm is recovered.

( 6) Plug in site id, and reset CMB. About five minutes later, check whether the alarm is recovered.

( 7) Change AEM module.

3.1.188 198087198 Uplink of ADC chip initialization failure

Alarm Information

l Alarm code: 198087198l Name: Uplink of ADC chip initialization failurel Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

Uplink of ADC chip initialization failure

Alarm Cause

Uplink ADC chip initialization failure

Impact

User-defined.

Action

1. Reset this module in order to work normally.

2. if reset is of no effect , please replace this module at once.

3-138


Chapter 3 Alarms

3.1.189 198087200 CIP resource can't be used

Alarm Information

l Alarm code: 198087200l Name: CIP resource can't be usedl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

CIP resource can't be used

Alarm Cause

Uplink/downlink loop data demodulation failure

Impact

User-defined.

Action

if alarm exists, at the same time some traffics exist on this TRM, it indicates this TRM is normal; if

there aren't some traffics on this TRM, or RF_LOOP test failure which arose by OMCR, this TRM is

damaged and please replace it at once.

3.1.190 198087201 Uplink failure

Alarm Information

l Alarm code: 198087201l Name: Uplink failurel Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

Uplink failure

Alarm Cause

Error in uplink data receiving

Impact

User-defined.

3-139



Action

1.Reset this module in order to work normally.

2. if reset is of no effect, please replace this module at once.

3.1.191 198087207 Watchdog of FUC overflow

Alarm Information

l Alarm code: 198087207l Name: Watchdog of FUC overflowl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

Watchdog of FUC overflow

Alarm Cause

FUC program has no response temporarily

Impact

User-defined.

Action

user can reset TPU to solve this problem. If it isn't solved, please replace TRM module.

3.1.192 198087216 Cell configuration parameter mismatch(BTS V2)

Alarm Information

l Alarm code: 198087216l Name: Cell configuration parameter mismatch(BTS V2)l Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

Cell configuration parameter mismatch(BTS V2)

3-140


Chapter 3 Alarms

Alarm Cause

Cell parameter configuration is incorrect or conflicts with channel parameters and CU parameter

configuration, carrier frequency configuration in omcr is unconform with the physical board

Impact

User-defined.

Action

1.Wait ten minutes. If the alarm still exists, configure parameters again from background, and

synchronize them to base station. Otherwise check the hardware and replace TRM/DTRM module in

time.

2.Please check whether the carrier frequency configuration in omcr is conform with the physical

board or not.

3.1.193 198087221 Communication link between CMM and FUCbreak(BTS V2)

Alarm Information

l Alarm code: 198087221l Name: Communication link between CMM and FUC break(BTS V2)l Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

Communication link between CMM and FUC break(BTS V2)

Alarm Cause

HDLC link between CMM and TPU breaks, CMM hardware error, etc

Impact

User-defined.

3-141



Action

system can run, but any data doesn't be configured.if only TPU link longtime break, User can use

the methods as follows to remove the problem:

1.Check whether TPU plugin tightly.

2.Reset TPU board.

3.Check whether CMM work normally.

4.Check address switch's right.

5.Transport line''s connection on back panel.

6.Use HW loop test to confirm software problem or hardware problem.if hardware has problems,

please replace it, if software has problems please upgrade software version.

3.1.194 198087224 Watchdog of TPU CIP overflow

Alarm Information

l Alarm code: 198087224l Name: Watchdog of TPU CIP overflowl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

Watchdog of TPU CIP overflow

Alarm Cause

DSP program of demodulation module has no response temporarily

Impact

User-defined.

Action

Reset this CU firstly.If the alarm resume, it could be confirmed that the alarm is arisen by interior

status of DSP abnormal.After resetting resumes, the CU could work normally.if not, BSC should start

BCCH changeover strategy and replace TRM module.

3.1.195 198087225 Software version of CIP mismatch

Alarm Information

l Alarm code: 198087225l Name: Software version of CIP mismatch

3-142


Chapter 3 Alarms


Alarm Description

Software version of CIP mismatch

Alarm Cause

CIP software version load error. If one of the carriers is configured as BCCH, then the whole cell

can not work normally.

Impact

User-defined.

Action

reset TRM, if it is of no effect, please replace TRM module.

3.1.196 198087226 Clock alarm for TPU and CMM

Alarm Information

l Alarm code: 198087226l Name: Clock alarm for TPU and CMMl Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

Clock alarm for TPU and CMM

Alarm Cause

Clock between TPU and CMM is disconnected

Impact

User-defined.

Action

1. If this TPU alarm is the only one alarm in the base station, check the line connection on back

panel.if the connection is correct , please replace TRM.

2. if other TPUs have the same alarm as this TPU, check whether clock alarm exists on CMM

board. If it is , please replace CMM.

3-143



3.1.197 198087228 TPU frame No. alarm

Alarm Information

l Alarm code: 198087228l Name: TPU frame No. alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

TPU frame No. alarm

Alarm Cause

Frame clock FCLK has problem, upper-level frame number synchronization source CMM has problem

Impact

User-defined.

Action

1.check if FCLK of frame no producing point is normal( if it is directly transported, check the clock

frequency, wave shape; if it is produced by phase locked, check whether the alarm of loose lock

exists.if there are some problems, please replace TRM module.

2. Transport link( transport clock, interface chip, the size of error code rate)3. check superior

synchro source of frame no

3.1.198 198087229 TPU CHP DSP0 initialization failure

Alarm Information

l Alarm code: 198087229l Name: TPU CHP DSP0 initialization failurel Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

TPU CHP DSP0 initialization failure

Alarm Cause

DSP software or hardware error

3-144


Chapter 3 Alarms

Impact

All the sixteen physical channels of the dual-carrier fail to operate properly. Cell services may also be

affected if the DTRU board is configured as BCCH.

Action

1. Re- download the software of that DSP.

2. Reset that DTRM frame( restart DSP), check whether that warning can recover or not.

3. Check whether the environmental temperature exceeds temperature permit for equipment running,

if there is overtemperature alarm, please adjust the environment; if the temperature is within the

permit, re-plug in the board to check whether the alarm is recovered.

4. If the alarm has not been recovered, replace the corresponding DTRU.

3.1.199 198087243 Cell configuration parameter mismatch

Alarm Information

l Alarm code: 198087243l Name: Cell configuration parameter mismatchl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

Cell configuration parameter mismatch

Alarm Cause

Cell parameter configuration is incorrect or conflicts with channel parameters and CIP parameter

configuration

Impact

The BTS may not operate properly.

Action

1. If the alarm is not recovered within 10 minutes, re-configure the parameter in the background,

and synchronize to the base station.

2. Reset the TRX, after 10 minutes, check whether the alarm is recovered.

3. Re-plug the TRX module, after 10 minutes, check whether the alarm is recovered.

4. Change the corresponding TRX module.

3-145



3.1.200 198087247 HDLC communication link between CMB andFUC broken

Alarm Information

l Alarm code: 198087247l Name: HDLC communication link between CMB and FUC brokenl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

HDLC communication link between CMB and FUC broken

Alarm Cause

HDLC link between CMB and TPU breaks, CMB hardware error, etc

Impact

TPU polling is faulty and data fails to be transmitted between the TPU and CMB. Data fails to be

configured for the FUC, CHP, and CIP and their states fail to be reported.

Action

1. Check whether DTRU is plugged tightly and properly. Re-plug DTRU module, and add DTRU in

corresponding position according to the configuration, so as to 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 works normally. Re-plug CMB to check

whether the alarm is recovered.

4. Check whether the DIP switch on the backplane is correct. Otherwise, adjust the switch to correct

position, to check whether the alarm is recovered.

5. Check whether the transmission line of the backplane is connected correctly. Otherwise connect

the line to correct position to check whether the alarm is recovered.

3.1.201 198087453 signal HDLC break off

Alarm Information

l Alarm code: 198087453l Name: signal HDLC break offl Alarm severity: Majorl Alarm type: Equipment alarm

3-146


Chapter 3 Alarms

Alarm Description

signal HDLC break off

Alarm Cause

Communication break of between TRX and FIB's HDLC or hardware error

Impact

The DTRU board fails to operate.

Action

1.DTRU board insert close or not? Insert or power on

2.Reset DTRU board , and watch whether it work or not

3.check whether FIB work or not

4.check whether address switch of rear board right or not

5.check whether line connect right or not

3.1.202 198087253 FU fram No error alarm

Alarm Information

l Alarm code: 198087253l Name: FU fram No error alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

FU fram No error alarm

Alarm Cause

Frame clock FCLK has problem, upper-level frame number synchronization source CMB has problem

Impact

The DTRU board fails to operate. Cell services may also be affected if the DTRU board is configured

with BCCH.

3-147



Action

1. Measure every Frame clock FCLK that produce frame number to ensure it is normal( if deliver

directly, then see the frequency of the clock, whether waveform have or not distortion. if it is

phaselock to produce, then check whether have the warning of lose lock or not). if have fault then

replace the DTRM module in time.

2. Check transmission link( whether clock of transmission is normal or not, whether the interface chip

have or not warning, whether the size of the error code rate is small or not)

3.Whether the upper source of synchronization exists the warning or not.

3.1.203 198087254 Rx PLL1 unlock

Alarm Information

l Alarm code: 198087254l Name: Rx PLL1 unlockl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

Rx PLL1 unlock

Alarm Cause

Clock signal is unstable or TRM Phase-Locked Loop ( PLL) fault

Impact

User-defined.

Action

1. Check whether clock alarm exists with LMT.if it exists, please replace relevant module.if it doesn't

exist, check the 13M output of TP on front panel. If it doesn't exist, there is clock problem from TPU to

RCU.please replace TRM.

2. if the problem still exists, maybe the LO fail, please replace TRM.

3.1.204 198087255 Rx PLL2 unlock

Alarm Information

l Alarm code: 198087255l Name: Rx PLL2 unlockl Alarm severity: Minor

3-148


Chapter 3 Alarms


Alarm Description

Rx PLL2 unlock

Alarm Cause


Impact

User-defined.

Action





3.1.205 198087256 Tx PLL1 unlock

Alarm Information

l Alarm code: 198087256l Name: Tx PLL1 unlockl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

Tx PLL1 unlock

Alarm Cause


Impact

User-defined.

3-149



Action





3.1.206 198087257 Tx PLL2 unlock

Alarm Information

l Alarm code: 198087257l Name: Tx PLL2 unlockl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

Tx PLL2 unlock

Alarm Cause


Impact

User-defined.

Action





3.1.207 198087258 52M referenced clock PLL unlock

Alarm Information

l Alarm code: 198087258l Name: 52M referenced clock PLL unlockl Alarm severity: Minorl Alarm type: Equipment alarm

3-150


Chapter 3 Alarms

Alarm Description

52M referenced clock PLL unlock

Alarm Cause


Impact

User-defined.

Action





3.1.208 198087259 Tx IF PLL unlock

Alarm Information

l Alarm code: 198087259l Name: Tx IF PLL unlockl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

Tx IF PLL unlock

Alarm Cause


Impact

User-defined.

Action





3-151



3.1.209 198087260 EEPROM resource can't be used

Alarm Information

l Alarm code: 198087260l Name: EEPROM resource can't be usedl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

EEPROM resource can't be used

Alarm Cause

EEPROM fault

Impact

User-defined.

Action

please replace TRM module.

3.1.210 198087261 FPGA interface failure

Alarm Information

l Alarm code: 198087261l Name: FPGA interface failurel Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

FPGA interface failure

Alarm Cause

Communication between DSP and FPGA interface breaks

Impact

User-defined.

3-152


Chapter 3 Alarms

Action

please replace TRM module.

3.1.211 198087262 PA VSWR alarm(BTS V2)

Alarm Information

l Alarm code: 198087262l Name: PA VSWR alarm(BTS V2)l Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

PA VSWR alarm(BTS V2)

Alarm Cause

Direct reason: reverse power is too high. Possible reason: open circuit or high resistance exists in

output end of PA

Impact

User-defined.

Action

1.Check the connection of PA output with cable.

2.If alarm still exists, please replace TRM module as soon as possible.

3.1.212 198087263 PA overtemperature minor alarm(BTS V2)

Alarm Information

l Alarm code: 198087263l Name: PA overtemperature minor alarm(BTS V2)l Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

PA overtemperature minor alarm(BTS V2)

3-153



Alarm Cause

PA temperature is too high, which is possibly due to PA working with rated power for a long time, fan

not working for a long time, environment temperature too high, and detecting circuit fault, etc

Impact

User-defined.

Action

1.Check whether fan works normally or not and whether the environment temperature is high or not.

2.If the fan works normally and the environment temperature is normal, the PA temperature warning

still exist then may be the detection electric circuit breakdown, continue to observe.

3.1.213 198087264 PA overtemperature major alarm(BTS V2)

Alarm Information

l Alarm code: 198087264l Name: PA overtemperature major alarm(BTS V2)l Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

PA overtemperature major alarm(BTS V2)

Alarm Cause



Impact

User-defined.

Action



still exist then may be the detection electric circuit breakdown, should replace the TRM/DTRM

module in time.

3-154


Chapter 3 Alarms

3.1.214 198087265 PA output power alarm

Alarm Information

l Alarm code: 198087265l Name: PA output power alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

PA output power alarm

Alarm Cause

Direct reason: Difference between PA output power and CIP control power is more than 3 db;

Possible reason: PA aging, power detecting circuit fault, or detecting threshold too narrow

Impact

User-defined.

Action

1.Reset TRM and observe.

2. if alarm exists, replace TRM module as soon as possible.

3.1.215 198087266 PA power overvoltage

Alarm Information

l Alarm code: 198087266l Name: PA power overvoltagel Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

PA power overvoltage

Alarm Cause


Impact

User-defined.

3-155



Action

check the check circuit of PA.if it has problem, please replace TRM.

3.1.216 198087267 PA power lower voltage

Alarm Information

l Alarm code: 198087267l Name: PA power lower voltagel Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

PA power lower voltage

Alarm Cause

PA power undervoltage

Impact

User-defined.

Action


3.1.217 198087268 Downlink checksum error of DLRC_AL1

Alarm Information

l Alarm code: 198087268l Name: Downlink checksum error of DLRC_AL1l Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

Downlink checksum error of DLRC_AL1

Alarm Cause

Interference exists on link between CHP and modulation module

3-156


Chapter 3 Alarms

Impact

User-defined.

Action

1. Check the signal and time-sequence between CHP and modulation module.

2. if the problem still exists, please replace TRM in time.

3.1.218 198087269 DUC chip initialization failure

Alarm Information

l Alarm code: 198087269l Name: DUC chip initialization failurel Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

DUC chip initialization failure

Alarm Cause

DUC chip unavailable

Impact

User-defined.

Action

please replace this TRM module.

3.1.219 198087270 80w PA VSWR alarm

Alarm Information

l Alarm code: 198087270l Name: 80w PA VSWR alarml Alarm severity: Minorl Alarm type: Equipment alarm

3-157



Alarm Description

80w PA VSWR alarm

Alarm Cause

Direct reason: Reverse power is too high; Possible reason: Open circuit or high resistance exists at

the output end of PA

Impact

User-defined.

Action

1.Check the connection of PA output with cable.

2.If alarm still exists, please replace TRM module as soon as possible.

3.1.220 198087271 80w PA overtemperature

Alarm Information

l Alarm code: 198087271l Name: 80w PA overtemperaturel Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

80w PA overtemperature

Alarm Cause



Impact

User-defined.

Action




3-158


Chapter 3 Alarms

3.1.221 198087272 80w PA overtemperature major alarm

Alarm Information

l Alarm code: 198087272l Name: 80w PA overtemperature major alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

80w PA overtemperature major alarm

Alarm Cause



Impact

User-defined.

Action



still exist then may be the detection electric circuit breakdown, should replace the TRM/DTRM

module in time.

3.1.222 198087273 80w PA output power alarm

Alarm Information

l Alarm code: 198087273l Name: 80w PA output power alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

80w PA output power alarm

Alarm Cause

Direct reason: Difference between PA output power and CIP control power is more than 3 db;

Possible reason: PA aging, power detecting circuit fault, or detecting threshold too narrow

3-159



Impact

User-defined.

Action

1.Reset TRM and observe.

2. if alarm exists, replace TRM module as soon as possible.

3.1.223 198087274 80w PA power overvoltage

Alarm Information

l Alarm code: 198087274l Name: 80w PA power overvoltagel Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

80w PA power overvoltage

Alarm Cause


Impact

User-defined.

Action


3.1.224 198087275 80w PA power lower voltage

Alarm Information

l Alarm code: 198087275l Name: 80w PA power lower voltagel Alarm severity: Minorl Alarm type: Equipment alarm

3-160


Chapter 3 Alarms

Alarm Description

80w PA power lower voltage

Alarm Cause


Impact

User-defined.

Action

check the check circuit of PA.if it has problem, please replace TRM

3.1.225 198087276 80w PA absent

Alarm Information

l Alarm code: 198087276l Name: 80w PA absentl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

80w PA absent

Alarm Cause

PA not in position

Impact

User-defined.

Action


3.1.226 198087277 TXIF unlock

Alarm Information


3-161



l Name: TXIF unlockl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

TXIF unlock

Alarm Cause

Clock signal is unstable or DTRU Phase-Locked Loop ( PLL) fault

Impact

The DTRU board may fail to operate.

Action

1. Restart the TRX, if the fault disappears, it indicates there is no fault in DTRU.

2. Check whether there is signal between Pinout 2 and 15 of HW line; if there is no signal, change

the HW line and continue with the test; if there is still no signal, it may be caused by CMB fault.

Test the 13M clock port on the equipment top, if there is signal, re-plug CMB board, if there is no

signal, it may be caused by CMB fault.

3. If the signal test is normal, re-plug this TRX. If there is still faults, change the fault TRX slot. If the

problem continues, change DTRU.

3.1.227 198087278 TPF unlock

Alarm Information

l Alarm code: 198087278l Name: TPF unlockl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

TPF unlock

Alarm Cause


Impact


3-162


Chapter 3 Alarms

Action








3.1.228 198087279 TXRF unlock

Alarm Information

l Alarm code: 198087279l Name: TXRF unlockl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

TXRF unlock

Alarm Cause


Impact


Action








3-163



3.1.229 198087280 RXRF unlock

Alarm Information

l Alarm code: 198087280l Name: RXRF unlockl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

RXRF unlock

Alarm Cause


Impact


Action

1. See through LMT whether have the clock warning, if have, then replace the corresponding

module.If have not clock warning, then check whether have output or not from 13M clock of TP

front panel. If have not output, then can be thought that the clock fault between TPU and RCU and

should replace the DTRM module.

2.If still have fault and can't recover, then it is possible that local oscillator have fault, and should

replace the DTRM in time.

3.1.230 198087281 13 MHz clock lost

Alarm Information

l Alarm code: 198087281l Name: 13 MHz clock lostl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

13 MHz clock lost

Alarm Cause

13 MHz clock receiving is abnormal, 13 MHz clock unit works abnormally

3-164


Chapter 3 Alarms

Impact


Action








3.1.231 198087282 60 ms clock lost

Alarm Information

l Alarm code: 198087282l Name: 60 ms clock lostl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

60 ms clock lost

Alarm Cause

60 ms synchronization clock receiving is abnormal, 60 ms synchronization clock unit works abnormally

Impact


Action

1. Check the configuration, if there are excessive standby racks configured, ignore this alarm.

2. Check whether the 60ms cables are connected properly, or whether the cables are broken.

Reconnect or change the 60ms cables to check whether the alarm is recovered.

3. Check whether the CMB of standby racks work normally. If it is not normal, recover CMB working

status to check whether the alarm is recovered.

3-165



3.1.232 198087285 52 MHz clock lost

Alarm Information

l Alarm code: 198087285l Name: 52 MHz clock lostl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

52 MHz clock lost

Alarm Cause

RF board 52 MHz clock receiving is abnormal, RF board 52 MHz clock unit works abnormally

Impact


Action








3.1.233 198087288 PA power overvoltage alarm

Alarm Information

l Alarm code: 198087288l Name: PA power overvoltage alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

PA power overvoltage alarm

3-166


Chapter 3 Alarms

Alarm Cause


Impact

The PA may be broken and the modulation module may switch off the power output for protection.

Action

Check whether the PA examination electric circuit break down or not, if have the fault, should replace

the DTRM in time

3.1.234 198087289 PA power undervoltage alarm

Alarm Information

l Alarm code: 198087289l Name: PA power undervoltage alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

PA power undervoltage alarm

Alarm Cause


Impact

The output power is faulty.

Action

Check whether the PA examination electric circuit break down or not, if have the fault, should replace

the DTRM in time

3.1.235 198087290 PA VSWR alarm

Alarm Information

l Alarm code: 198087290l Name: PA VSWR alarml Alarm severity: Minor

3-167




Alarm Description

PA VSWR alarm

Alarm Cause

Direct reason: reverse power is too high. Possible reason: open circuit or high resistance exists in

output end of PA

Impact

The DTRU board fails to operate and the PA is broken.

Action

1. Check whether the PA output connects the electric cable tightly, if not, connects the PA output

and the electric cable tightly.

2. If still break down then should replace the DTRM module in time.

3.1.236 198087291 PA temperature minor alarm

Alarm Information

l Alarm code: 198087291l Name: PA temperature minor alarml Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

PA temperature minor alarm

Alarm Cause



Impact

The DTRU still operates properly but the performance of the PA is deteriorated drastically.

3-168


Chapter 3 Alarms

Action




3.1.237 198087292 PA temperature major alarm

Alarm Information

l Alarm code: 198087292l Name: PA temperature major alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

PA temperature major alarm

Alarm Cause



Impact

The power output of the DTRU is switched off for protection and the performance of the PA is

deteriorated drastically.

Action



still exist then may be the detection electric circuit breakdown, should replace the DTRM module in

time.

3.1.238 198087293 PA forward power(3db) alarm

Alarm Information

l Alarm code: 198087293l Name: PA forward power(3db) alarml Alarm severity: Minorl Alarm type: Equipment alarm

3-169



Alarm Description

PA forward power(3db) alarm

Alarm Cause

Direct reason: Difference between PA output power and CHP control power is more than 3 db;

Possible reason: PA aging, power detecting circuit fault, detecting threshold too narrow

Impact

The DTRU board may fail to operate and the power is out of control.

Action

1. Reset the DTRM to observe whether warning can recover or not.

2. If still have the breakdown, should replace the DTRM module in time

3.1.239 198087294 RTU power alarm

Alarm Information

l Alarm code: 198087294l Name: RTU power alarml Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

RTU power alarm

Alarm Cause

RTU power module failure

Impact

The TRM/DTRU boards fail to operate. Cell services may also be affected if the TRM/DTRU is

configured as BCCH.

Action

Replace the RTU circuit board as quickly as possible

3-170


Chapter 3 Alarms

3.1.240 198087295 RTU power temperature alarm

Alarm Information

l Alarm code: 198087295l Name: RTU power temperature alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

RTU power temperature alarm

Alarm Cause

RTU power module overheated

Impact

The power output of the TRM/DTRU is switched off for protection and the performance of the RTU is

deteriorated drastically.

Action

1.To detect the whether the fans are running and the electric power source is overheat.

2.If the fans are running and the electric power source isn't overheat, maybe there is something wrong

in the error-detector circuit.

3.1.241 198087296 RTU power output overvoltage alarm

Alarm Information

l Alarm code: 198087296l Name: RTU power output overvoltage alarml Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

RTU power output overvoltage alarm

Alarm Cause

RTU power output overvoltage

3-171



Impact

The RTU fails to operate properly.

Action


3.1.242 198087297 RTU power input failure alarm

Alarm Information

l Alarm code: 198087297l Name: RTU power input failure alarml Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

RTU power input failure alarm

Alarm Cause

RTU power input failure

Impact

The RTU fails to operate properly.

Action


3.1.243 198087298 IQ calibration parameters abnormal alarm

Alarm Information

l Alarm code: 198087298l Name: IQ calibration parameters abnormal alarml Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

IQ calibration parameters abnormal alarm

3-172


Chapter 3 Alarms

Alarm Cause

IQ calibration parameter abnormal

Impact

The RTU board is completely broken.

Action

Replace the RTU circuit board as quickly as possible.

3.1.244 198087299 EAM heat exchanger alarm

Alarm Information

l Alarm code: 198087299l Name: EAM heat exchanger alarml Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

EAM heat exchanger alarm

Alarm Cause

Heat exchanger alarm, reported by dry contact of heat exchanger

Impact

This fault may decrease the equipment safety.

Action

Perform on-site check immediately to find fault cause and replace the heat exchanger.

3.1.245 198087300 EAM TRX layer fan-4 alarm

Alarm Information

l Alarm code: 198087300l Name: EAM TRX layer fan-4 alarml Alarm severity: Warningl Alarm type: Equipment alarm

3-173



Alarm Description

EAM TRX layer fan-4 alarm

Alarm Cause

CMB0 heater wrong

Impact

This fault has an impact on start-up at a low temperature.

Action

replace CMB0 heater in time

3.1.246 198087301 EAM AEM layer axis-flow fan alarm

Alarm Information

l Alarm code: 198087301l Name: EAM AEM layer axis-flow fan alarml Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

EAM AEM layer axis-flow fan alarm

Alarm Cause

CMB1 heater wrong

Impact


Action

replace CMB1 heater in time

3.1.247 198087302 EAM smoke alarm

Alarm Information


3-174


Chapter 3 Alarms

l Name: EAM smoke alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

EAM smoke alarm

Alarm Cause

Equipment smoke alarm

Impact

This fault may decrease the safety of equipment operation.

Action

Perform on-site check immediately to find fault cause and handle the fault.

3.1.248 198087303 EAM waterproof alarm

Alarm Information

l Alarm code: 198087303l Name: EAM waterproof alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

EAM waterproof alarm

Alarm Cause

Equipment water alarm

Impact


Action


3-175



3.1.249 198087304 EAM lightning protection alarm

Alarm Information

l Alarm code: 198087304l Name: EAM lightning protection alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

EAM lightning protection alarm

Alarm Cause

Lightning protector failure alarm

Impact


Action

Perform on-site check immediately to find fault cause and replace the lightning protector.

3.1.250 198087305 EAM backdoor access control alarm

Alarm Information

l Alarm code: 198087305l Name: EAM backdoor access control alarml Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

EAM backdoor access control alarm

Alarm Cause

Alarm of back door being opened

Impact


3-176


Chapter 3 Alarms

Action

Perform on-site check immediately to find fault cause and close the back door.

3.1.251 198087306 EAM frontdoor access control alarm

Alarm Information

l Alarm code: 198087306l Name: EAM frontdoor access control alarml Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

EAM frontdoor access control alarm

Alarm Cause

Alarm of front door being opened

Impact


Action

Perform on-site check immediately to find fault cause and close the front door.

3.1.252 198087307 EAM PWR monitoring unit alarm

Alarm Information

l Alarm code: 198087307l Name: EAM PWR monitoring unit alarml Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

EAM PWR monitoring unit alarm

Alarm Cause

PWR monitoring unit alarm

3-177



Impact


Action

Perform on-site check immediately to find fault cause.

3.1.253 198087308 EAM heat exchanger electric heater alarm

Alarm Information

l Alarm code: 198087308l Name: EAM heat exchanger electric heater alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

EAM heat exchanger electric heater alarm

Alarm Cause

FIB heater alarm

Impact


Action

replace FIB heater in time

3.1.254 198087309 EAM heat exchanger control board alarm

Alarm Information

l Alarm code: 198087309l Name: EAM heat exchanger control board alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

EAM heat exchanger control board alarm

3-178


Chapter 3 Alarms

Alarm Cause

Heat exchanger control board alarm

Impact

This fault has an impact on operation of the equipment.

Action


3.1.255 198087310 EAM heat exchanger external circulation fan 2alarm

Alarm Information

l Alarm code: 198087310l Name: EAM heat exchanger external circulation fan 2 alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

EAM heat exchanger external circulation fan 2 alarm

Alarm Cause

Heat exchanger external circulation fan 2 alarm

Impact


Action


3.1.256 198087311 EAM heat exchanger external circulation fan 1alarm

Alarm Information

l Alarm code: 198087311l Name: EAM heat exchanger external circulation fan 1 alarm

3-179




Alarm Description

EAM heat exchanger external circulation fan 1 alarm

Alarm Cause

Heat exchanger external circulation fan 1 alarm

Impact


Action


3.1.257 198087312 EAM heat exchanger internal circulation fan 2alarm

Alarm Information

l Alarm code: 198087312l Name: EAM heat exchanger internal circulation fan 2 alarml Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

EAM heat exchanger internal circulation fan 2 alarm

Alarm Cause

Heat exchanger internal circulation fan 2 alarm

Impact


Action


3-180


Chapter 3 Alarms

3.1.258 198087313 EAM heat exchanger internal circulation fan 1alarm

Alarm Information

l Alarm code: 198087313l Name: EAM heat exchanger internal circulation fan 1 alarml Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

EAM heat exchanger internal circulation fan 1 alarm

Alarm Cause

Heat exchanger internal circulation fan 1 alarm

Impact


Action


3.1.259 198087314 EAM heat exchanger 485 communication alarm

Alarm Information

l Alarm code: 198087314l Name: EAM heat exchanger 485 communication alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

EAM heat exchanger 485 communication alarm

Alarm Cause

Communication break between EAM and heat exchanger

Impact

This fault has an impact on the reporting of heat exchanger alarms.

3-181



Action


3.1.260 198087315 EAM temperature alarm

Alarm Information

l Alarm code: 198087315l Name: EAM temperature alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

EAM temperature alarm

Alarm Cause

Equipment internal environment temperature too high

Impact


Action


3.1.261 198087316 EAM TRX layer mixed-flow fan 1 alarm

Alarm Information

l Alarm code: 198087316l Name: EAM TRX layer mixed-flow fan 1 alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

EAM TRX layer mixed-flow fan 1 alarm

Alarm Cause

Mixed-flow fan 1 damage alarm

3-182


Chapter 3 Alarms

Impact

This fault has an impact on the operation of the TRX module.

Action

Perform on-site check immediately to find fault cause and replace the fan.


Alarm Information


Alarm Description


Alarm Cause


Impact


Action



Alarm Information


Alarm Description


3-183



Alarm Cause


Impact


Action


3.1.264 198087319 Communication broken between EAM and CMB

Alarm Information

l Alarm code: 198087319l Name: Communication broken between EAM and CMBl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

Communication broken between EAM and CMB

Alarm Cause

Communication break between EAM and CMB

Impact

This fault has an impact on the reporting of equipment alarms.

Action


3.1.265 198087320 Power undervoltage alarm

Alarm Information

l Alarm code: 198087320l Name: Power undervoltage alarml Alarm severity: Majorl Alarm type: Equipment alarm

3-184


Chapter 3 Alarms

Alarm Description

Power undervoltage alarm

Alarm Cause

Power voltage is lower than normal

Impact

User-defined.

Action

Restore external power supply as soon as possible

3.1.266 198087321 Inner fan 2 alarm (for M8202)

Alarm Information

l Alarm code: 198087321l Name: Inner fan 2 alarm (for M8202)l Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

Inner fan 2 alarm (for M8202)

Alarm Cause


Impact

The temperature in the cabinet is too high.

Action

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 the wrong one.

3-185



3.1.267 198087322 Inner fan 1 alarm (for M8202)

Alarm Information

l Alarm code: 198087322l Name: Inner fan 1 alarm (for M8202)l Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

Inner fan 1 alarm (for M8202)

Alarm Cause


Impact


Action


2. Check the fan and maintain the fault; 3. Check the collection system of the dTPB board and

replace the wrong one.

3.1.268 198087323 Outer fan 2 and fan 4 alarm (for M8202)

Alarm Information

l Alarm code: 198087323l Name: Outer fan 2 and fan 4 alarm (for M8202)l Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

Outer fan 2 and fan 4 alarm (for M8202)

Alarm Cause


Impact


3-186


Chapter 3 Alarms

Action


2. Check the fan and maintain the fault;

3. Check the collection system of the dTPB board and replace the wrong one.

3.1.269 198087324 Outer fan 1 and fan 3 alarm (for M8202)

Alarm Information

l Alarm code: 198087324l Name: Outer fan 1 and fan 3 alarm (for M8202)l Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

Outer fan 1 and fan 3 alarm (for M8202)

Alarm Cause


Impact


Action


2. Check the fan and maintain the fault;

3. Check the collection system of the dTPB board and replace the wrong one.

3.1.270 198087325 Rack temperature minor alarm

Alarm Information

l Alarm code: 198087325l Name: Rack temperature minor alarml Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

Rack temperature minor alarm

3-187



Alarm Cause


Impact


Action

Check the environment temperature, if the temperature is normal, keep on observing while other

modules works normally, otherwise, improve the equipment working conditions.

3.1.271 198087326 Rack temperature major alarm

Alarm Information

l Alarm code: 198087326l Name: Rack temperature major alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

Rack temperature major alarm

Alarm Cause


Impact

Performance is reduced because the equipment is damaged.

Action

Check the environment temperature, if the temperature is normal, keep on observing while other

modules works normally, otherwise, improve the equipment working conditions.

3.1.272 198087327 Layer 3 fan 1 alarm (for M8206)

Alarm Information

l Alarm code: 198087327l Name: Layer 3 fan 1 alarm (for M8206)l Alarm severity: Warning

3-188


Chapter 3 Alarms


Alarm Description

Layer 3 fan 1 alarm (for M8206)

Alarm Cause

The failure of fans

Impact

Too high temperature in the cabinet may result in deteriorated performance and shorter service life

of the devices.

Action

1.Examin the error-detection circuit;

2. Examin the fans;

3. Examin the RTU Alarm Collection Circuit, if any fault in it, replace the relevant unit.


Alarm Information

l Alarm code: 198087328l Name: Layer 3 fan 2 alarm (for M8206)l Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description


Alarm Cause

The failure of fans

Impact


of the devices.

3-189



Action


2. Examin the fans;



Alarm Information


Alarm Description


Alarm Cause

The failure of fans

Impact


of the devices.

Action


2. Examin the fans;



Alarm Information


3-190


Chapter 3 Alarms

Alarm Description


Alarm Cause

The failure of fans

Impact


of the devices.

Action


2. Examin the fans;



Alarm Information


Alarm Description


Alarm Cause

The failure of fans

Impact


of the devices.

Action


2. Examin the fans;


3-191




Alarm Information


Alarm Description


Alarm Cause

The failure of fans

Impact


of the devices.

Action


2. Examin the fans;



Alarm Information


Alarm Description


Alarm Cause

The failure of fans

3-192


Chapter 3 Alarms

Impact


of the devices.

Action


2. Examin the fans;



Alarm Information


Alarm Description


Alarm Cause

The failure of fans

Impact


of the devices.

Action


2. Examin the fans;



Alarm Information

l Alarm code: 198087335l Name: Layer 1 fan 3 alarm (for M8206)

3-193



l Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description


Alarm Cause

The failure of fans

Impact


of the devices.

Action

1. Examin the error-detection circuit;

2. Examin the fans;


3.1.281 198087391 FCU power undervoltage alarm

Alarm Information

l Alarm code: 198087391l Name: FCU power undervoltage alarml Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

FCU power undervoltage alarm

Alarm Cause

+12V power undervoltage

Impact

The FCU fails to operate properly.

Action

Replace the FCU as soon as possible

3-194


Chapter 3 Alarms

3.1.282 198087403 The clock alarm about transmission of CCIboard Abis-E1

Alarm Information

l Alarm code: 198087403l Name: The clock alarm about transmission of CCI board Abis-E1l Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

The clock alarm about transmission of CCI board Abis-E1

Alarm Cause

The clock alarm about transmission of CCI board Abis-E1 is lost

Impact

User-defined.

Action

Exam the Abis E1 interface.

3.1.283 198087404 The local working clock alarm of CCI board

Alarm Information

l Alarm code: 198087404l Name: The local working clock alarm of CCI boardl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

The local working clock alarm of CCI board

Alarm Cause

The local working clock error

Impact

User-defined.

3-195



Action

Switch to the slave circuit board as quickly as possible. If Necessarily, to replace the CCI circuit board.

3.1.284 198087405 The clock alarm about transmission of CCIboard 13M

Alarm Information

l Alarm code: 198087405l Name: The clock alarm about transmission of CCI board 13Ml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

The clock alarm about transmission of CCI board 13M

Alarm Cause

The clock alarm about transmission of CCI board is lost

Impact

User-defined.

Action

Exam the contrast source, or replace the CCI circuit board.

3.1.285 198087406 CCI opposite board alarm

Alarm Information

l Alarm code: 198087406l Name: CCI opposite board alarml Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

CCI opposite board alarm

3-196


Chapter 3 Alarms

Alarm Cause

there is no CCI opposite board or clock failure

Impact

User-defined.

Action

Replace the CCI circuit board.

3.1.286 198087407 IQ FPGA internal clock alarm

Alarm Information

l Alarm code: 198087407l Name: IQ FPGA internal clock alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

IQ FPGA internal clock alarm

Alarm Cause

IQ FPGA internal source lost of clock

Impact

User-defined.

Action

Detect whether the CLK FPGA is running.

3.1.287 198087408 IQ FPGA light interface alarm

Alarm Information

l Alarm code: 198087408l Name: IQ FPGA light interface alarml Alarm severity: Minorl Alarm type: Equipment alarm

3-197



Alarm Description

IQ FPGA light interface alarm

Alarm Cause

IQ FPGA light interface abnormal

Impact

User-defined.

Action

Replace the optical module or optical fiber.

3.1.288 198087409 IQ FPGA LVDS interface alarm

Alarm Information

l Alarm code: 198087409l Name: IQ FPGA LVDS interface alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

IQ FPGA LVDS interface alarm

Alarm Cause

LVDS interface abnormal

Impact

User-defined.

Action

Exam the backboard and SERDES chip in the relevant GBP board.

3.1.289 198087410 IQ FPGA internal data alarm

Alarm Information


3-198


Chapter 3 Alarms

l Name: IQ FPGA internal data alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

IQ FPGA internal data alarm

Alarm Cause

the format of internal data is abnormal

Impact

User-defined.

Action

Find out the cause of the data format mistake.

3.1.290 198087470 Fan absence alarm

Alarm Information

l Alarm code: 198087470l Name: Fan absence alarml Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

Fan absence alarm

Alarm Cause

Fan error or absence

Impact


Action

1. Check if fan work or not.

2. If work, check up the connection between fan and fan controller good or not.3. If connection is

good, exchange new fan frame.

3-199



3.1.291 198087471 Fan rotate alarm

Alarm Information

l Alarm code: 198087471l Name: Fan rotate alarml Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

Fan rotate alarm

Alarm Cause

Fan rotate too slowly

Impact


Action

1. Check if much dust result in the slow rotate speed of the fan or not.

2. If not, exchange new fan frame.

3.1.292 198087472 CMB and FNCB RS485 link break alarm

Alarm Information

l Alarm code: 198087472l Name: CMB and FNCB RS485 link break alarml Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

CMB and FNCB RS485 link break alarm

Alarm Cause

interrupt RS485 communication between fan controller and CMB

Impact

This fault has no impact on heat dissipation, but the fan fails to be controlled.

3-200


Chapter 3 Alarms

Action

1. Check if the fan frame tightened or not.

2. Check if the RS485 and CMB backboard or DTRU backboard tightened or not.

3. Exchange fan frame.

3.1.293 198087480 Status of TX5 filter alarm

Alarm Information

l Alarm code: 198087480l Name: Status of TX5 filter alarml Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

Status of TX5 filter alarm

Alarm Cause

TX5 is adjusting or loss over 5dB

Impact


Action

Replace the FCU, or reset the TRM that connected with it

3.1.294 198087481 Status of TX6 filter alarm

Alarm Information

l Alarm code: 198087481l Name: Status of TX6 filter alarml Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

Status of TX6 filter alarm

3-201



Alarm Cause

TX6 is adjusting or loss over 5dB

Impact


Action

Replace the FCU, or reset the TRM that connected with it

3.1.295 198087443 Diversity antenna lost

Alarm Information

l Alarm code: 198087443l Name: Diversity antenna lostl Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

Diversity antenna lost

Alarm Cause

Two diversity antenna receive signal, one of diversity antenna is abnormal

Impact

User-defined.

Action

Check the receive channel of RF as quickly as possible.

3.1.296 198087444 Diversity antenna identical

Alarm Information

l Alarm code: 198087444l Name: Diversity antenna identicall Alarm severity: Warningl Alarm type: Equipment alarm

3-202


Chapter 3 Alarms

Alarm Description

Diversity antenna identical

Alarm Cause

Wrong connection of diversity antenna

Impact

User-defined.

Action

Check the connection of ant line as quickly as possible.

3.1.297 198087411 13M,61.44M clock lost alarm

Alarm Information

l Alarm code: 198087411l Name: 13M,61.44M clock lost alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

13M,61.44M clock lost alarm

Alarm Cause

clock lost

Impact

User-defined.

Action

If there is 13M or 61.44M clock lost alarm in CCI board, and there is alarm all the same after reset the

board, please exam the clock source; If no 13M or 61.44M clock lost alarm, and there is alarm after

reset GBP all the same, please exam the LVDS access.

3-203



3.1.298 198087412 60ms clock lost alarm

Alarm Information

l Alarm code: 198087412l Name: 60ms clock lost alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

60ms clock lost alarm

Alarm Cause

FR or FN error

Impact

User-defined.

Action

If there is FR or FN error in the CCI, and there is error all the same after reset the CCI, please

exam the hardware; If there is not FR or FN error in the CCI, and there is 60ms clock lost alarm

all the same, please exam the LVDS access.

3.1.299 198087413 26MHz and 52MHz lost of clock alarm

Alarm Information

l Alarm code: 198087413l Name: 26MHz and 52MHz lost of clock alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

26MHz and 52MHz lost of clock alarm

Alarm Cause

the loop of clock is unlock

Impact

User-defined.

3-204


Chapter 3 Alarms

Action

If there is 13M clock lost alarm in the CCI, and there is alarm all the same after reset CCI, please

exam the clock source; if there is not 13M clock lost alarm in the CCI, and there is clock lost alarm all

the same after reset GBP, please exam 13M clock LVDS access. If there is no problem with the LVDS

access, please replace the FPGA PLL that is invalid.

3.1.300 198087414 the failure examination alarm of the 60ms uplinkframe

Alarm Information

l Alarm code: 198087414l Name: the failure examination alarm of the 60ms uplink framel Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

the failure examination alarm of the 60ms uplink frame

Alarm Cause

the uplink is not detected the 60ms frame

Impact

User-defined.

Action

If there is up 60ms super frame synchronization head exam failing alarm in the CCI, and there

is alarm all the same after reset CCI, please exam its hardware. If no up 60ms super frame

synchronization head exam failing alarm, and there is alarm all the same after reset GBP, please

exam the LVDS access.

3.1.301 198087415 checking block data error alarm

Alarm Information

l Alarm code: 198087415l Name: checking block data error alarml Alarm severity: Warningl Alarm type: Equipment alarm

3-205



Alarm Description

checking block data error alarm

Alarm Cause

the frame data error

Impact

User-defined.

Action

None

3.1.302 198087416 up link LVDS SERDES lost lock alarm

Alarm Information

l Alarm code: 198087416l Name: up link LVDS SERDES lost lock alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

up link LVDS SERDES lost lock alarm

Alarm Cause

SERDES lose clock

Impact

User-defined.

Action

If it is of no effect to reset GBP and CCI, please exam the LVDS data format from CCI, else to

replace the LVDS.

3-206


Chapter 3 Alarms

3.1.303 198087417 FN error alarm

Alarm Information

l Alarm code: 198087417l Name: FN error alarml Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

FN error alarm

Alarm Cause

the error of frame no error from CCI

Impact

User-defined.

Action

If there is FN error the CCI, and there is error all the same after reset CCI, please exam the hardware.

If no FN error, but there is FN error after reset GBP, exam the LVDS access.

3.1.304 198087432 Diversity antenna lost

Alarm Information

l Alarm code: 198087432l Name: Diversity antenna lostl Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

Diversity antenna lost

Alarm Cause

Two diversity antenna receive signal, one of diversity antenna is abnormal

Impact

The sensitivity and coverage of the receiver antenna decreases because one of the diversities is faulty.

3-207



Action

Reset the TRX; if there is a fault, change the slot; if problem remains, change DTRU.

3.1.305 198087433 Diversity antenna identical

Alarm Information

l Alarm code: 198087433l Name: Diversity antenna identicall Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

Diversity antenna identical

Alarm Cause

Wrong connection of diversity antenna

Impact

The antenna fails to operate because there is a crossed pair of wires.

Action

Check the connection of ant line as quickly as possible.

3.1.306 198087451 board not support 16MHW

Alarm Information

l Alarm code: 198087451l Name: board not support 16MHWl Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

board not support 16MHW

Alarm Cause

board not support 16MHW

3-208


Chapter 3 Alarms

Impact

The IP ABIS function is partially supported and some carrier frequencies are not available.

Action

change the board support 16MHW

3.1.307 198087452 cmb or cpu overload

Alarm Information

l Alarm code: 198087452l Name: cmb or cpu overloadl Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

cmb or cpu overload

Alarm Cause

cpu usage rate exceed 85%

Impact

Some services may fail to be processed.

Action

wait for a while , and operate service after alarm restored

3.1.308 198087454 main HDLC break off

Alarm Information

l Alarm code: 198087454l Name: main HDLC break offl Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

main HDLC break off

3-209



Alarm Cause

HDLC break off between CMB and FIB;CMB or FIB hardware error

Impact

Data fails to be transmitted between the CMB and FIB.

Action

1.watch cmb or fib work or not

2.if cmb or fib doesn't work, reset it

3.if alarm does not restore for a long time, please change a new cmb or fib

3.1.309 198087455 FIB configure wrong

Alarm Information

l Alarm code: 198087455l Name: FIB configure wrongl Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

FIB configure wrong

Alarm Cause

parameter Configuration over time or wrong

Impact

This alarm seldom occurs because the back end of the BSC generally checks data validity before

data synchronization.

Action

wait for ten minutes, if alarm still does not restore, ismg configure parameter again, and synchronize

to the site. If problem remain, just change a new fib

3.1.310 198087456 lay3 of FIB software has no response

Alarm Information


3-210


Chapter 3 Alarms

l Name: lay3 of FIB software has no responsel Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

lay3 of FIB software has no response

Alarm Cause

FIB software has no respond temporary( set by CMB)

Impact

The back end fails to detect the operation of the FIB.

Action

1.wait for ten minute, and watch whether alarm restore or not

2.ifalarm does not restore for a long time, please pull out the fib board and put it in to slot again

when service not too busy

3.if alarm remain after reset fib, please reset cmb when service not too busy

4.if alarm remain please change a new fib

5.if software has bug, please update to the latest

3.1.311 198087460 positive 12 voltage alarm

Alarm Information

l Alarm code: 198087460l Name: positive 12 voltage alarml Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

positive 12 voltage alarm

Alarm Cause

DPB board of DTRU module, +12V power module has alarm

Impact

Services are affected because the LNA of the cell fails to operate properly.

3-211



Action

change DTRU module or BBTR board

3.1.312 198087461 negative 12 voltage alarm

Alarm Information

l Alarm code: 198087461l Name: negative 12 voltage alarml Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

negative 12 voltage alarm

Alarm Cause

DPB board of DTRU module, -12V power module has alarm

Impact

Services are affected because the LNA of the cell fails to operate properly.

Action

change DTRU module or BBTR board

3.1.313 198087462 DSP 1.2v voltage alarm

Alarm Information

l Alarm code: 198087462l Name: DSP 1.2v voltage alarml Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

DSP 1.2v voltage alarm

Alarm Cause

DPB board of DTRU module, 1.2V power module has alarm

3-212


Chapter 3 Alarms

Impact

The DTRU board fails to operate. Cell services may also be affected if the DTRU is configured

as BCCH.

Action

change DTRU module

3.1.314 198087463 6.4v voltage alarm

Alarm Information

l Alarm code: 198087463l Name: 6.4v voltage alarml Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

6.4v voltage alarm

Alarm Cause

DPB board of DTRU module, 6.4V power module has alarm

Impact


as BCCH.

Action

change DTRU module

3.1.315 198087464 5v voltage alarm

Alarm Information

l Alarm code: 198087464l Name: 5v voltage alarml Alarm severity: Majorl Alarm type: Equipment alarm

3-213



Alarm Description

5v voltage alarm

Alarm Cause

DPB board of DTRU module, 5V power module has alarm

Impact


as BCCH.

Action

change DTRU module

3.1.316 198087473 DTPU CPU overload

Alarm Information

l Alarm code: 198087473l Name: DTPU CPU overloadl Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

DTPU CPU overload

Alarm Cause


Impact

The services on the DTRU may fail to be processed.

Action


3-214


Chapter 3 Alarms

3.1.317 198087483 GPS signal synchronization exception

Alarm Information

l Alarm code: 198087483l Name: GPS signal synchronization exceptionl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

GPS signal synchronization exception

Alarm Cause

Not support GPS synchronization, GPS clock synchronization failed or GPS fault

Impact

Clock synchronization is switched to internal synchronization because GPS synchronization fails.

Action

1. Check whether the current CMB board supports GPS synchronization. If not, replace it with the

new one supporting GPS. 2.To check EIB/FIB if support GPS or not 3.Change EIB/FIB

3.1.318 198087484 Second pulse loss

Alarm Information

l Alarm code: 198087484l Name: Second pulse lossl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

Second pulse loss

Alarm Cause

GPS 1PPS signal loss

Impact

GPS clock synchronization fails.

3-215



Action

1. Check the antennas.

2. Check the cable between EIB/FIB and the top of equipment.

3. Check EIB/FIB.

4. Check the CMB Alarm Collect Circuit, if something is wrong in it, replace the relevant unit.

3.1.319 198087485 Antenna open-circuit alarm

Alarm Information

l Alarm code: 198087485l Name: Antenna open-circuit alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

Antenna open-circuit alarm

Alarm Cause

GPS Antenna appeared open-circuit exception

Impact


Action

1. Check cable connection from antennas to EIB or FIB, include GPSSP.


3. Check EIB/FIB, if something is wrong in it, replace the relevant unit.

3.1.320 198087486 Antenna short-circuit alarm

Alarm Information

l Alarm code: 198087486l Name: Antenna short-circuit alarml Alarm severity: Minorl Alarm type: Equipment alarm

3-216


Chapter 3 Alarms

Alarm Description

Antenna short-circuit alarm

Alarm Cause

GPS Antenna appeared short-circuit exception

Impact


Action

1. Check cable connection from antennas to EIB or FIB, include GPSSP if short or not.



3.1.321 198087487 Lost satellite alarm

Alarm Information

l Alarm code: 198087487l Name: Lost satellite alarml Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

Lost satellite alarm

Alarm Cause

GPS does not recognize the satellite

Impact


Action

1.Check connecting of the antennas, and the antennas is hid or not.

2.TCheck the cable between EIB/FIB and the top of equipment.


3-217



3.1.322 198087510 CPU of FIB overload

Alarm Information

l Alarm code: 198087510l Name: CPU of FIB overloadl Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

CPU of FIB overload

Alarm Cause


Impact

Some services may fail to be processed.

Action


3.1.323 198088000 DTPU not support Baseband-Hop alarm

Alarm Information

l Alarm code: 198088000l Name: DTPU not support Baseband-Hop alarml Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

DTPU not support Baseband-Hop alarm

Alarm Cause

DTPU not support Baseband-Hop alarm

Impact

1. The TRXs other than 875DTRU fail to be involved in baseband-hop.

2. The TRXs other than the DTPB fail to be involved in baseband-hop.

3-218


Chapter 3 Alarms

Action

1, Check DTRU if DTPB080300 or not, if not , please change to DTPB080300 module

2, If alarm is still exist, please check backplane if BBTR070401 or not , if not, please change to

BBTR070401.

3.1.324 198088001 PA Power Voltage Adjusting Path Disconnected

Alarm Information

l Alarm code: 198088001l Name: PA Power Voltage Adjusting Path Disconnectedl Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

PA Power Voltage Adjusting Path Disconnected

Alarm Cause

I2C Path Disconnected

Impact

This fault is adverse to energy saving.

Action

1.Check DTRU supports the function

2.Check 6 Pins Cable

3.Reconnected Cable, if cannot recovery then

4.The DTRU Can Work , Replace the DTRU till New DTRU Coming for PA Power voltage adjusting

function

3.1.325 198088002 PA Power Voltage Adjusting Data Error

Alarm Information

l Alarm code: 198088002l Name: PA Power Voltage Adjusting Data Errorl Alarm severity: Warningl Alarm type: Equipment alarm

3-219



Alarm Description

PA Power Voltage Adjusting Data Error

Alarm Cause

I2C Data Read or Write Error

Impact


Action

1.Retry Data Setting

2.Check 6 Pins Cable , if cannot recovery then

3.The DTRU Can Work , Replace the DTRU till New DTRU Coming for PA Power voltage adjusting

function

3.1.326 198088003 PA Power Voltage Adjusting Data Illegal

Alarm Information

l Alarm code: 198088003l Name: PA Power Voltage Adjusting Data Illegall Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

PA Power Voltage Adjusting Data Illegal

Alarm Cause

Set Data out of Range

Impact


Action

1.Change Static Power data

2.Update setting

3-220


Chapter 3 Alarms

3.1.327 198088004 Access iBSC failure

Alarm Information

l Alarm code: 198088004l Name: Access iBSC failurel Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

Access iBSC failure

Alarm Cause

Authentication failed or unconnected response

Impact

User-defined.

Action

1.Authentication again

2.Check physical link

3.1.328 198088005 Control link broken

Alarm Information

l Alarm code: 198088005l Name: Control link brokenl Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

Control link broken

Alarm Cause

Communication broken between

BTS and BSC

Impact

User-defined.

3-221



Action

1.First, determinate HBTS fault or transmission line problem.

2.Check the process of software By signaling analyzer, determine the problem of BSC or BTS.

3.Amend the relevant software, and upgrade version of the software.

3.1.329 198088006 Operation link broken(CS)

Alarm Information

l Alarm code: 198088006l Name: Operation link broken(CS)l Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

Operation link broken(CS)

Alarm Cause

the transmission line is broken

Impact

User-defined.

Action

check the transmission line

3.1.330 198088007 Operation link broken(PS)

Alarm Information

l Alarm code: 198088007l Name: Operation link broken(PS)l Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

Operation link broken(PS)

3-222


Chapter 3 Alarms

Alarm Cause

the transmission line is broken

Impact

User-defined.

Action


3.1.331 198088008 Parameter configuration mismatch

Alarm Information

l Alarm code: 198088008l Name: Parameter configuration mismatchl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

Parameter configuration mismatch

Alarm Cause

iBSC parameters configuration

failed, time-out or broken links

Impact

User-defined.

Action

configuration

parameter again.

3.1.332 198088009 DSP initialization failure

Alarm Information

l Alarm code: 198088009l Name: DSP initialization failurel Alarm severity: Minor

3-223




Alarm Description

DSP initialization failure

Alarm Cause

DSP software or hardware

error

Impact

User-defined.

Action

1.Download DSP software version again.

2.Reset DSP, if the alarm is not restored alarm, replace HBTS

3.1.333 198088010 Parameter configuration failure of AD6537

Alarm Information

l Alarm code: 198088010l Name: Parameter configuration failure of AD6537l Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

Parameter configuration failure of AD6537

Alarm Cause

AD6537 register to read

and write error

Impact

User-defined.

Action

Power-down Re-starting and re-configuration AD6537, send the

appropriate warning information

3-224


Chapter 3 Alarms

3.1.334 198088011 Tx PLL unlock

Alarm Information

l Alarm code: 198088011l Name: Tx PLL unlockl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

Tx PLL unlock

Alarm Cause

Clock signal instability or PLL failed

Impact

User-defined.

Action

Forbid TRM, send

warning information

3.1.335 198088012 Wrong parameter configuration for EEPROM

Alarm Information

l Alarm code: 198088012l Name: Wrong parameter configuration for EEPROMl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

Wrong parameter configuration for EEPROM

Alarm Cause

EEPROM hardware failed or previously written into the EEPROM invalid parameters, resulting in

EEPROM RF parameters can not read.

Impact

User-defined.

3-225



Action

send warning information

3.1.336 198088013 FLASH memory fault

Alarm Information

l Alarm code: 198088013l Name: FLASH memory faultl Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

FLASH memory fault

Alarm Cause

FLASH programming over the number,

read and write error Or check the software error

Impact

User-defined.

Action

Reset HBTS, Download DSP software version again.if the alarm is not restored alarm, replace HBTS

3.1.337 198088014 Run abnormity of DSP

Alarm Information

l Alarm code: 198088014l Name: Run abnormity of DSPl Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

Run abnormity of DSP

3-226


Chapter 3 Alarms

Alarm Cause

DSP programming error

Impact

User-defined.

Action

Reset DSP, load DSP software version, configuration CHP parameters.

3.1.338 198088015 FPGA interface fault

Alarm Information

l Alarm code: 198088015l Name: FPGA interface faultl Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

FPGA interface fault

Alarm Cause

DSP and FPGA interface interruption

Impact

User-defined.

Action

load FPGA version again, reset HBTS,

replace HBTS

3.1.339 198088016 CHP frame fault

Alarm Information

l Alarm code: 198088016l Name: CHP frame faultl Alarm severity: Minorl Alarm type: Equipment alarm

3-227



Alarm Description

CHP frame fault

Alarm Cause

As the circuit interference so that the frame misoperation

Impact

User-defined.

Action

Reset HBTS

3.1.340 198088017 Wrong receive channel of RF

Alarm Information

l Alarm code: 198088017l Name: Wrong receive channel of RFl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

Wrong receive channel of RF

Alarm Cause

Failure to receive channel, the

normal of signals up

Impact

User-defined.

Action

Download FPGA, DSP version again, configuration system parameters.

3-228


Chapter 3 Alarms

3.1.341 198088018 Get DNS failure when configuration IP of active

Alarm Information

l Alarm code: 198088018l Name: Get DNS failure when configuration IP of activel Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

Get DNS failure when configuration IP of active

Alarm Cause

HBTS can not get to the IP address from the DNS server

Impact

User-defined.

Action

Configuration the IP address of DNS by LMT.

3.1.342 198088019 Analyse failure of DNS domain name

Alarm Information

l Alarm code: 198088019l Name: Analyse failure of DNS domain namel Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

Analyse failure of DNS domain name

Alarm Cause

HBTS can not get to the IP address from the DHCP server

Impact

User-defined.

3-229



Action

Configuration the IP address, port of iBSC by LMT.

3.1.343 198088020 IPSec failure

Alarm Information

l Alarm code: 198088020l Name: IPSec failurel Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

IPSec failure

Alarm Cause

Can not access

Impact

User-defined.

Action

Configuration IPSec parameter again

3.1.344 198088021 RF channel and HTRG board unconformity

Alarm Information

l Alarm code: 198088021l Name: RF channel and HTRG board unconformityl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

RF channel and HTRG board unconformity

Alarm Cause

Hardware does not support requencies information

3-230


Chapter 3 Alarms

Impact

User-defined.

Action

1.reset the frequency point with HTRG

2.Replace supporting the rang of frequency HTRG

3.1.345 198088022 Get HBTS'S IP address failure from DHCP Sever

Alarm Information

l Alarm code: 198088022l Name: Get HBTS'S IP address failure from DHCP Severl Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

Get HBTS'S IP address failure from DHCP Sever

Alarm Cause

HBTS can not automatically get

to the IP address from the DHCP server

Impact

User-defined.

Action

Configuration the IP address, subnet mask, gateway, port of iBSC and HBTS by LMT.

3.1.346 198088023 Over temperature

Alarm Information

l Alarm code: 198088023l Name: Over temperaturel Alarm severity: Minorl Alarm type: Equipment alarm

3-231



Alarm Description

Over temperature

Alarm Cause

Over temperature

Impact

User-defined.

Action

Switch off power, check

3.1.347 198088024 Voltage abnormity

Alarm Information

l Alarm code: 198088024l Name: Voltage abnormityl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

Voltage abnormity

Alarm Cause

Voltage abnormity

Impact

User-defined.

Action

Check power

3.1.348 198088025 Abis link change alarm

Alarm Information


3-232


Chapter 3 Alarms

l Name: Abis link change alarml Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

Abis link change alarm

Alarm Cause

Abis link on the earth surface is broken, then the service of satellite-backup site changes to the

satellite abis link

Impact

This fault has no impact on a service if the service is successfully switched over.

Action

check the abis link on the earth surface, and restore it as soon as possible

3.1.349 198088026 IPOE uplink and downlink jam alarm

Alarm Information

l Alarm code: 198088026l Name: IPOE uplink and downlink jam alarml Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

IPOE uplink and downlink jam alarm

Alarm Cause

IPOE site detect the jam of uplink and downlin

Impact

Service quality degrades or even the service is interrupted.

Action


3-233



3.1.350 198088027 DIP E1 rack, rack type error

Alarm Information

l Alarm code: 198088027l Name: DIP E1 rack, rack type errorl Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

DIP E1 rack, rack type error

Alarm Cause

No. 15 to 12 bits of E1 rack DIP, rack type error

Impact

A link may fail to be established after the E1 rack is rebooted.

Action

check E1 rack No. 15 to 12 bits of the DIP

3.1.351 198088028 DIP E1 rack, rack number error

Alarm Information

l Alarm code: 198088028l Name: DIP E1 rack, rack number errorl Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

DIP E1 rack, rack number error

Alarm Cause

No. 11 to 10 bits of E1 rack, rack number error

Impact


3-234


Chapter 3 Alarms

Action


3.1.352 198088029 DIP E1 rack,slave rack 1 port error

Alarm Information

l Alarm code: 198088029l Name: DIP E1 rack,slave rack 1 port errorl Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

DIP E1 rack,slave rack 1 port error

Alarm Cause

No. 9 to 8 bits of E1 rack, slave rack 1 port error

Impact

Slave rack 1 of the E1 BTS may fail to operate properly.

Action


3.1.353 198088030 DIP E1 rack,slave rack 2 port error

Alarm Information

l Alarm code: 198088030l Name: DIP E1 rack,slave rack 2 port errorl Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

DIP E1 rack,slave rack 2 port error

Alarm Cause

No. 7 to 6 bits of E1 rack, slave rack 2 port error

3-235



Impact

Slave rack 2 of the E1 BTS may fail to operate properly.

Action


3.1.354 198088031 DIP E1 rack,satellite back up flag error

Alarm Information

l Alarm code: 198088031l Name: DIP E1 rack,satellite back up flag errorl Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

DIP E1 rack,satellite back up flag error

Alarm Cause

No. 5 bit of E1 rack, satellite back up flag error

Impact

The backup satellite link of the E1 BTS may fail to operate properly.

Action

check E1 rack No. 5 bit of the DIP

3.1.355 198088032 DIP E1 rack,oam time slot error

Alarm Information

l Alarm code: 198088032l Name: DIP E1 rack,oam time slot errorl Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

DIP E1 rack,oam time slot error

3-236


Chapter 3 Alarms

Alarm Cause

No. 4 to 0 bits of E1 rack, oam time slot error

Impact


Action


3.1.356 198088033 DIP IP rack,access mode error(IP or IPOE)

Alarm Information

l Alarm code: 198088033l Name: DIP IP rack,access mode error(IP or IPOE)l Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

DIP IP rack,access mode error(IP or IPOE)

Alarm Cause

No. 15 to 14 bits of IP rack, access mode error( IP or IPOE)

Impact

A link may fail to be established after the IP rack is rebooted.

Action

check IP rack No. 15 to 14 bits of the DIP

3.1.357 198088034 DIP IP rack,rack number error

Alarm Information

l Alarm code: 198088034l Name: DIP IP rack,rack number errorl Alarm severity: Warningl Alarm type: Equipment alarm

3-237



Alarm Description

DIP IP rack,rack number error

Alarm Cause

No. 13 to 12 bits of IP rack, rack number error

Impact


Action


3.1.358 198088035 DIP IP rack,site number error

Alarm Information

l Alarm code: 198088035l Name: DIP IP rack,site number errorl Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

DIP IP rack,site number error

Alarm Cause

No. 11to 0 bits of IP rack, site number error

Impact


Action


3.1.359 198088036 DIP IP rack,sequence number error

Alarm Information


3-238


Chapter 3 Alarms

l Name: DIP IP rack,sequence number errorl Alarm severity: Warningl Alarm type: Equipment alarm

Alarm Description

DIP IP rack,sequence number error

Alarm Cause

IP rack, sequence number configured on NMS is error

Impact


Action

ON NMS, check the sequence number of the IP site

3.1.360 198088037 Mains power failure alarm

Alarm Information

l Alarm code: 198088037l Name: Mains power failure alarml Alarm severity: Majorl Alarm type: Equipment alarm

Alarm Description

Mains power failure alarm

Alarm Cause

AC mains failure

Impact

User-defined.

Action

check AC

3-239



3.1.361 198088038 Alarm of the trx's down link LRC failed

Alarm Information

l Alarm code: 198088038l Name: Alarm of the trx's down link LRC failedl Alarm severity: Minorl Alarm type: Equipment alarm

Alarm Description

the LRC of the PLL parameter failed

Alarm Cause

the parameter FPGA received is abnormal, or the channel of McBSP is abnormal.

Impact

The RF phase-lock loop is unlocked.

Action

Change another DTRU

3.2 Communication Alarm

3.2.1 198022784 BFD Session Interrupted

Alarm Information

Code: 198022784

Name: BFD Session Interrupted

Severity: Minor

Type: Communication alarm

Alarm Description

BFD session is down

3-240


Chapter 3 Alarms

Alarm Cause

1. The network cable connection on relevant equipment (including local/intermediate/opposite

equipment) is loose or disconnected.

2. Intermediate equipment is faulty.

3. Opposite equipment is faulty.

4. Local equipment is faulty.

5. Configuration related to the BFD session is incorrect.

Impact

All services on the path relating to the BFD session will be switched to the standby path. Service

interruption will occur if no standby path exists.

Action

Check alarm details on the NMS Alarm Management interface to find the source address and the

destination address of the BFD session. The source address refers to the address of local equipment.

The destination address refers to the address of the opposite BFD session equipment.

1. Check the status of the line card at the local end. If the line card restarts repeatedly, replace it

and power on.

2. Check the physical connection between the BFD session-related port and the local line card. If the

connection is loose or broken, 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 correct IP address.

i. Telnet to the interface board to check the link by making a ping test. For example, if the destination

address is 2.2.2.10, enter the following command in the telnet 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:Reply from 2.2.2.10: bytes=60 time<1ms" displays on the screen, it means the link

is normal.

iii. In case of timeout, check if the related route and address are configured correctly. If not, correct

the reconfiguration and do a ping test again.

iv. If the route/address is configured correctly but the repsonse still times out, it means a link is broken

or the intermediate equipment is faulty. In this case, check to see if there is any broken network

cable, loose connection or abnormal equipment along the BFD session path. If yes, take necessary

actions, such as replacing the broken cable, tightening the connection, or repairing or replacing the

fault equipment, to solve the problem.

4. If the ping test indicates that packets can be received and sent normally at both ends, check to see

if the BFD session at both ends is configured correctly by performing the following steps:

i. Check the configuration of BFD session on the NMS Configuration Management interface to

ensure the BFD switch is in "enabled" status.

ii. Make sure that the BFD session is configured with the same working mode at both sides.

iii. Make sure that at least one device plays an "active" role for the BFD session.

3-241



iv. Make sure that the BFD session exists at both ends, and that the source and the destination

IP addresses are matched.

v. Make sure that the hop mode (single hop/multi-hop) is consistent at both ends.

vi. Make sure that the authentication information is consistent at both ends.

5. Reboot the board where the interface is located.

3.2.2 198066029 PPP link broken

Alarm Information

Code: 198066029

Name: PPP link broken

Severity: Major


Alarm Description

PPP_UID Link Down

Alarm Cause

1. The alarm occurs in PPP port creating, modifying, deleting when PPP port is created by command.

2. The alarm occurs once in PPP port during board power-on, and recovers 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.

Impact

This will cause disconnection of user plane data and services.

Action

Check alarm details on the NMS Alarm Management interface to find the faulty PPP port ID.

1. Check the cable connections at both ends to see if they are loose or broken. If yes, tighten the

connection or replace the broken cable.

2. Refer to the networking plan to check if the E1 cable is correctly connected.

3. Click IPOverE1 Configuration on the NMS Configuration Management interface to check E1 ID and

time slot. Make sure that the time slot configuration is consistent at both ends.

4. Check PPP parameters on the NMS Configuration Management interface to ensure that the

configuration is consistent at both ends.

5. Check the connection relation of DT and EIPI on the NMS Configuration Management interface to

ensure that the PPP port configuration is consistent at both ends.

3-242


Chapter 3 Alarms

3.2.3 198066026 Association path broken

Alarm Information

Code: 198066026

Name: Association path broken

Severity: Major


Alarm Description

Association path broken

Alarm Cause

1. SCTP link is broken

2. Control plane path in NE is interrupted.


4. The route to remote address is lost.

Impact

If multiple paths are available for the association and there exists normal path, relevant services will

not be affected.

If merely one path is available for the association, all services on the association is down.

Action

On NMS fault management interface, view alarm Details, where information of association ID, local

address, and remote address is given.

1. On NMS configuration management interface (static route), query the route information of the

remote address. Locate the out port according to the route information. Check if network cable of the

out port is disconnected or loose. If yes, unplug and plug the cable or replace the cable.

2. On NMS configuration management interface (SCTP association configuration), query the ID of

the module where the association is located. Check if the following alarm occurs in the relevant

board. If yes, refer to the corresponding alarm handling suggestion.

Related alarm: 198066003 Control plane communication 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 is configured. If not, add the configuration.

4. Check the intermediate equipment on association path. If the routes to local address and remote

address of the association are not configured, add the configuration according to equipment

operation manual.

5. Check at opposite end if the route to the local address of the association is configured. If not,

add the configuration.

3-243



6. Check if the opposite equipment is faulty. If yes, troubleshoot at opposite end.

3.2.4 198029953 The Ethernet port state is OAM loop back

Alarm Information

Code: 198029953

Name: The Ethernet port state is OAM loop back

Severity: Minor


Alarm Description

The Ethernet port state is OAM loop back

Alarm Cause

The local port state is loop back because the peer port starts Ethernet OAM loop back request

of 802.3ah.

Impact

The Ethernet link which is in loop back test can't bear service data.

Action

Check if the peer port has started Ethernet OAM loop back test. If yes, stop it, if no, disable local port

Ethernet OAM.

3.2.5 198005666 The number of the error packets from MAC portexceeds the threshold

Alarm Information

Code: 198005666

Name: The number of the error packets from MAC port exceeds the threshold

Severity: Minor


Alarm Description

The number of the error packets from MAC port exceeds the threshold

3-244


Chapter 3 Alarms

Alarm Cause

The number of the error packets from MAC port exceeds the threshold.

Impact

The MAC port is unavailable or the flow is limited.

Action

1.Check whether the connection between this port and the peer port 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 disappears: Y-> End, N-> Go to "2".

2.Try to replace the network interface on the peer end and then check if the alarm disappears.

Y->End.

N->Go to "3"

3.Try to replace the board or the network interface on the local end and then check if the alarm

disappears.

Y->End.


3.2.6 198000519 Trunk error

Alarm Information

Code: 198000519

Name: Trunk error

Severity: Major


Alarm Description

Trunk error

3-245



Alarm Cause

1. The receiving cable of local trunk equipment is faulty.

The cable is 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 equipment are not properly connected.

4. Operation of LOS insertion is operated at opposite trunk equipment.

Manual inset alarm operation is performed in diagnostic test.

Impact

The trunk equipment fails to work normally. All services based on the trunk are interrupted.

Action

1. Check whether the alarm is caused by local end or opposite end via meter measurement or

loop test.

Meter Measurement

Use a trunk test meter to test whether the trunk receiving signals at local end are normal. If yes, fault

might lie in local equipment. If no, troubleshoot at opposite end.

Loop test

Perform trunk self-loop at local end. If the alarm persists, fault might lie in local equipment. If the

alarm disappears, troubleshoot at opposite end.

2. Replace trunk cable.


3.2.7 198000520 Trunk abnormal

Alarm Information

Code: 198000520

Name: Trunk abnormal

Severity: Major


Alarm Description

Trunk abnormal

3-246


Chapter 3 Alarms

Alarm Cause

1. Trunk frame formats at local end and at opposite end are inconsistent.

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.

Impact

All services based on the trunk are interrupted.

Action

Alarm details are displayed in NMS Alarm Management interface, where fault type is given. You can

easily find handling suggestions according to the fault type.

The handling suggestions for each fault type are described as below:

1.Loss of E1 trunk frame, loss of E1 trunk multi-frame, E1 trunk alarm indication

i. In NMS Configuration Management interface, right click the board and select Subunit Configuration

to check whether frame format at both ends is the same.

ii. In NMS Configuration Management interface, right click the board and select Subunit Configuration

to check whether impedance is correct.

iii. Check whether the grounding at both ends is proper.

iv. If possible, locate alarm position, either at local end 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.

Check the alarm status of opposite end. Because the alarm indication is sent from opposite end,

please solve the opposite-end problem first.

3.2.8 198015617 Some frames Received by FE/GE/ATM/MP/POS/E1Port are faulty

Alarm Information

Code: 198015617

Name: Some frames Received by FE/GE/ATM/MP/POS/E1 Port are faulty

Severity: Minor


Alarm Description

The number of hardware error frames that the port received during specified time exceeds the

threshold

3-247



Alarm Cause

1. The network connected with FE/GE/ATM/MP/POS/E1 port is abnormal.

2. The board is in abnormal status.

3. Board hardware is faulty. For example, the network processor sub card is not tightly inserted.

4. Other board hardware faults.

Impact

Datagram reception of the board is affected. The service on this port might be unstable. Worst of all,

all services on the board might be interrupted.

Action

1. Unplug and plug port fibber/network cable.

2. Replace port fibber/network cable.

3. Reset the board.

4. Unplug and plug board.


3.2.9 198015618 Faulty frames received by port over threshold

Alarm Information

Code: 198015618

Name: Faulty frames received by port over threshold

Severity: Minor


Alarm Description

The number of hardware error frames that the port received during specified time exceeds the

threshold

Alarm 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/E1 reception.

4. Network processor sub-card which has worked normally is loose.

Impact

Datagram reception of the board is affected. The service on the board might be unstable.

3-248


Chapter 3 Alarms

Action

1. Pull out and insert the fiber/network cables to check if the fault is 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 the next level of maintenance support.

3.2.10 198015873 PSN board is sending out incorrect frames

Alarm Information

Code: 198015873

Name: PSN board is sending out incorrect frames

Severity: Major


Alarm Description

The number of frames of CSIX horizontal parity check error received during specified time exceeds

the threshold.

Alarm Cause

1. PSN board in the same shelf is abnormal.

2. PSN board is faulty

Impact

If the fault lies in PSN board, service of the entire RNC NE will become unstable. If the alarm persists,

all services will be interrupted.

If the fault lies in the board where the alarm is declared, only the services on this board are affected.

3-249



Action

1. Check if the following alarm exists in PSN board at the same shelf. If yes, refer to the

corresponding alarm handling suggestion.

Related alarm: 198019456 All high-speed links between line card and package switching board

are out of synchronism

2. Unplug and plug board.

3. Replace board.

3.2.11 198003841 The control plane retransmission ratio over thethreshold

Alarm Information

Code: 198003841

Name: The control plane retransmission ratio over the threshold

Severity: Major


Alarm Description

The RUDP of the control plane retransmission ratio over the threshold

Alarm Cause

There are some badly-touched boards in the system environment and the retransfer-ratio of RUDP

packets increases.

Impact

The master board will change when slave is exist.

Action

Make records of the alarm information and contact the next level of maintenance support.

3.2.12 198005651 IP / MAC address conflict

Alarm Information

Code: 198005651

Name: IP / MAC address conflict

3-250


Chapter 3 Alarms

Severity: Major


Alarm Description

IP/MAC address conflict when OSS detects control plane

Alarm 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 settings as the other shelf.

Impact

If IPMAC conflicts, control plane communication may become abnormal.

For the board that has been powered on, packets may be lost and services are unstable. In serious

situation, link interruption may occur and all services borne on the board will be interrupted.

For the board that is being powered on, the board may reset repeatedly, and services can not be

accessed.

Action

1. Unplug and plug the board.

2. Compare 2 DIP switches on 2 backplane boards, one is related to the board, the other is related

to OMP board. If the 2 DIP switches have different settings, please correct the settings to keep

consistency. Reset the relevant boards after setting.

3. Reset the board.

3.2.13 198066003 Control plane communication is abnormalbetween board and its home module

Alarm Information

Code: 198066003

Name: Control plane communication is abnormal between board and its home module

Severity: Minor


Alarm Description

OSS communication link off between pp and its mp

3-251



Alarm Cause


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.

Impact

The services carried by the board are interrupted.

Action

1. Check whether the board is in position. If not, insert the board.

2. Check whether the board is in blocked status. If yes, unblock the board.

3. Check whether the inserted board is the same as the configured board. 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/GUIM2 board of the same shelf.

3.2.14 198005378 Board HW Error

Alarm Information

Code: 198005378

Name: Board HW Error

Severity: Major


Alarm Description

Board HW loop back test fails

Alarm Cause

1. Clock is not synchronous.

2. Either the board or the slot has a hardware fault.

Impact

HW connection is affected and services carried over this HW are interrupted.

3-252


Chapter 3 Alarms

Action

1. Check the local board for the Related Alarms. Perform the recommended solution to process

the possible alarms.

Related Alarms:

198001286 Loss of clock when input to board

198005646 Phase-lock loop unlock

2. Check the clock board for the Related Alarms. Perform the recommended solution to process

the possible alarms.

Related Alarms:

198026133 Output clock lost

198026129 Clock reference source lost (Level 1 alarm)



3. Open the Configuration Management window and check whether the SDTB/SDTB2 has configured

APS while the active/standby board is configure.

How to check APS protection configuration: open the rack map on the Configuration Management

window, find the SDTB/SDTB2 board, right click to pop up shortcut menu, and select Optical port

APS Protection.



6. Replace the UIM/GUIM in the same shelf.

3.2.15 198066004 Control plane communication is abnormalbetween MP and OMP

Alarm Information

Code: 198066004

Name: Control plane communication is abnormal between MP and OMP

Severity: Major


Alarm Description

communication link off between mp and omp

Alarm Cause



3. The control plane communication is abnormal.

4. The board resets.

3-253



Impact

The board is blocked so that it can not provide functions. Furthermore, all services under the relevant

module become unavailable.

Action

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/GUIM2 board in the same shelf.

3.2.16 198005382 Communication between power board and OMPis abnormal

Alarm Information

Code: 198005382

Name: Communication between power board and OMP is abnormal

Severity: Major


Alarm Description

The RS485 of power board communicate link break

Alarm Cause

1. The power board is not connected to the OMP or the connection is wrong.

2. The power board locates in a rack. The configured rack number is different from that where DIP

switch of the power board locates.

Impact

The system can not monitor the status of power supply and environmental situation. However,

there is no impact on services.

Action

1. Reconnect the serial cable between the power board and OMP.

2. Make sure the rack number configured for the rack in which this power board locates is consistent

with the rack number switch set for the power board.

3-254


Chapter 3 Alarms

3.2.17 198005397 Communication of RAWMACIP channel isabnormal

Alarm Information

Code: 198005397

Name: Communication of RAWMACIP channel is abnormal

Severity: Major


Alarm Description

Board RAWMACIP communication abnormal

Alarm Cause

1. The CPU usage of the UIM/GUIM/GUIM2 in the shelf is too high.

2. The service media stream exceeds the threshold.

3. The hardware is faulty.

Impact

The channel between user plane processing board and signaling processing board is abnormal. This

causes degradation of QoS. In serious situation, services will be interrupted.

Action

1. In NMS Alarm Management interface, check whether the UIM/GUIM board of the same shelf has a

relevant alarm. If yes, please solve the problem according to corresponding handling suggestions.

Related alarm: 198002560 Board CPU overloaded


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


3.2.18 198005401 Test packet check abnormal

Alarm Information

Code: 198005401

Name: Test packet check abnormal

Severity: Major


3-255



Alarm Description

Test packet check abnormal,test type is decided by additional info

Alarm Cause


2. The line from UIM/GUIM/GUIM2 to GLI is abnormal.

Impact

Service transfer at medial plane is affected.

The alarm details include fault type. Each fault type has different impacts on the system.

1. If fault type is "ATM abnormal", the ATM board can not provide normal ATM services. Thus,

services carried by the board is interrupted.

2. If fault type is "L1 switch abnormal", it indicates that media plane communication is abnormal. This

causes all services carried on the shelf to be interrupted.

Action



The handling suggestions for each type are described as below.

1. Fault type: ATM abnormal

The internal related chip link of ATM processing board is abnormal. In this case, replace the board.

2. Fault type: L1 switch abnormal

The L1 media plane switching from UIM/GUIM/GUIM2 to GLI is abnormal. This is usually caused

by abnormal link between UIM/GUIM/GUIM2 and GLI. In this case, reconnect the cable between

UIM/GUIM/GUIM2 and GLI, or replace the cable. If optical fiber is used, replace the optical module.

3.2.19 198005122 Loss of Active/standby communication link

Alarm Information

Code: 198005122

Name: Loss of Active/standby communication link

Severity: Minor


Alarm Description

The control plane communication link between Master and Slave Boards is broken

3-256


Chapter 3 Alarms

Alarm Cause

1. The board is configured to be in active/standby mode, but the mate board is not in position.

2. Hardware Problem.

Impact

The active board can not communicate with the standby board. As a result, active/standby

changeover operation fails. There is no impact on services.

Action

1. Make sure the board is configured backup mode, and the master and slave boards are firmly in

place.

2. Check the opposite board for the related alarms. If there are related alarms,Perform the

recommended solution to process the possible alarms.

Description: 198066070, The board is offline or the CPU is in reset status for a long time


4. Change the slots of both the master and slave boards.

3.2.20 198005126 Incorrect FE Routing Connection

Alarm Information

Code: 198005126

Name: Incorrect FE Routing Connection

Severity: Critical


Alarm Description

The ports on the opposite board connected with a couple of ports on the local board are not paired

ports, or FE-C3/4 on RUIM1 backcard receives link detecting packets.

Alarm Cause

1. FE-C3/4 is used for FE routing port when RUIM1 rear board is used.

2. When CHUB is connected to UIM/GUIM/GUIM2, CHUB rear card (RCHUB1/RCHUB2) uses

discrete ports (e.g. port1/port3) to connect UIM rear card.

3. When UIM/GUIM/GUIM2 is connected to UIM/GUIM/GUIM2 CHUB, connections used 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 used for FE inter-connection.

3-257



Impact

Control plane routing is disconnected; ports are switched over in cycle; all services on this shelf

are interrupted.

Action

Reconnect the FE wire.

1. If the UIM board on the BUSN shelf uses RUIM1 backcard, make sure FE-C1/2 port is used

for routing port.

2. If the GUIM/GUIM2 board is on BGSN shelf, make sure FE1 and FE2 ports are used as routing

ports.

3. If TRUNK mode is used, numerous FE ports make up of a TRUNK port for cascaded connection.

In this case, make sure the both ends are paired ports.

If the boards of the local board or the opposite board are not paired port, please reconnect the FE

wire and make sure the both ends are used paired ports.

Here is an example of connection method:

i. When CHUB is connected with UIM/GUIM/GUIM2, the connecting wire 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 pairs on the UIM/GUIM/GUIM2 backcard.

ii. When UIM is connected with UIM/GUIM/GUIM2/CHUB, the ports on UIM backcard must be used

as paired .If RUIM1 backcard is used, then two FE-C1/2 ports must be used for FE routing ports;

if RUIM2/RUIM3 backcard is used, then use FE1/FE2 pair, FE3/FE4 pair or FE5/FE6 pair for the

FE routing ports.

iii. When GUIM/GUIM2 is connected with UIM/GUIM/GUIM2/CHUB, the ports on GUIM/GUIM2

backcard must be used as pair, i. e. , FE1 and FE2 must be used for FE routing ports.

3.2.21 198005127 FE Link Error Alarm

Alarm Information

Code: 198005127

Name: FE Link Error Alarm

Severity: Minor


Alarm Description

In a pair of FE port,one is link ok but another is link error, then the link error port need to be reported

alarm .

3-258


Chapter 3 Alarms

Alarm Cause

1. In a pair of FE ports, one has normal link but the other has link error.

2. The hardware is faulty.

Impact

Because one FE port has normal control plane link, services are not affected. However if this port is

faulty, services can not be switched to the other port, leading to service interruption.

Action

1. Check if only one cable is used to connect the port pair of the rear board to the peer-end FE port.

Ensure that both cables are connected to the peer end.

2. Reconnect the cables or replace the cables.

3. Replace the rear board.


3.2.22 198005128 Duplicate rack and shelf

Alarm Information

Code: 198005128

Name: Duplicate rack and shelf

Severity: Minor


Alarm Description

Duplicate rack and shelf

Alarm Cause

Shelf connect to the system with duplicate physical ID

Impact

Boards in the shelf which power-on later power-on failure.

Action

1. Check whether two shelf with same physical ID exists. Modify the switch of one of the two shelfs

and reset the shelf and board 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 connection exists.

3-259



3.2.23 198066005 SCCP subsystem unavailable

Alarm Information

Code: 198066005

Name: SCCP subsystem unavailable

Severity: Minor


Alarm Description

SCCP subsystem unavailable

Alarm Cause

1. From the perspective of A, remote signaling point subsystem is out of service.

2. From the perspective of A, remote signaling point is inaccessible.

3. Remote subsystem (for B) is configured at A end, but the corresponding 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 remote MTP3 or M3UA user

configuration.

Impact

Signaling data can not be sent to/received from the relevant subsystem. New service can not access

to the corresponding office. And existing services are interrupted abnormally.

Action

1. Check whether there is an office (the office that corresponds to the subsystem) inaccessible alarm.

If yes, solve the problem according to corresponding handling suggestion.

Related alarms:

i. 198066010 MTP3 office inaccessible

ii. 198066014 M3UA office inaccessible

2. Unblock the subsystem in dynamic data management.

3. In NMS Configuration Management interface, check the configuration of signaling point code

(for A) at A end. Is SCCP user included in user type configuration. If no, add the configuration.

Meanwhile, check the corresponding configuration at 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 B end must be out of service. Try to find the reason for this abnormal

status.

5. Check whether the signaling point subsystem (for B) is configured at B end. If no, add the

configuration at B end.

3-260


Chapter 3 Alarms

3.2.24 198066010 MTP3 Signalling Point Inaccessible

Alarm Information

Code: 198066010

Name: MTP3 Signalling Point Inaccessible

Severity: Major


Alarm Description

Alarm of office inaccessible from MTP3

Alarm Cause

1. No service link exists in the office route.

2. The MTP3 signaling network management message TransFer Prohibit(TFP) is received.

Impact

UE fails to receive/transmit messages from/to the relevant office. New services can not be accessed

to this office, and existing services are interrupted abnormally.

Action

1. Check whether there is an unavailable link alarm. If yes, please solve the problem according to

corresponding handling suggestions.

Related alarm: 198066011 MTP3 link unavailable

2. Check whether the configuration of office and link at opposite end is correct.

3.2.25 198066011 MTP3 link unavailable

Alarm Information

Code: 198066011

Name: MTP3 link unavailable

Severity: Minor


Alarm Description

Alarm of link unavailability

3-261



Alarm 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

Impact

If several MTP3 links are available for the office, services will not be 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.



Action

1. IN NMS Configuration Management interface, click Signalling Link Configuration to check PVC

configuration. Make sure that the configuration of CVPI and CVCI should be the same at both ends.

2. In Dynamic Data Management, check link status. If it is interrupted and connected now and then, it

means the link unavailability is caused by MTP3 link test failure.

1) In NMS Configuration Management interface, check the configuration of signalling point code at

both ends. Ensure that the configuration is consistent at both ends.

2) In NMS Configuration Management interface, check the configuration of signalling link at both

ends. Ensure that the configuration of SLC (Signalling Link 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 the board.

5. The opposite end has released the relevant link. Ask the opposite end to deal with the alarm as

link unavailable.

3.2.26 198066014 M3UA Signalling Point Inaccessible

Alarm Information

Code: 198066014

Name: M3UA Signalling Point Inaccessible

Severity: Major


Alarm Description

Alarm of office inaccessible from M3UA

3-262


Chapter 3 Alarms

Alarm Cause

1. Association link is broken or application server (AS) is not in serving status.

2. M3UA office is inaccessible because the remote office gives a DUNS (destination signalling

point unavailable) report.

Impact



Action

1. Check whether there is an association link broken alarm. If yes, please solve the problem

according to corresponding handling suggestions.

Related alarm: 198066019 Association link broken

2. In NMS Configuration Management interface, view AS Static Information to check whether a

routing context exists. If yes, view the relevant configuration such as routing context ID, AS ID

and AS service mode.

The correct configuration is described below.

i. The routing context ID and AS service mode must be the same at both ends.

ii. AS ID must meet the following requirements: if ASP is configured for local end, SGP should

be configured for opposite end; if IPSP client is configured for local 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 at opposite end.

3.2.27 198066019 Association link broken

Alarm Information

Code: 198066019

Name: Association link broken

Severity: Major


Alarm Description

Association link broken

3-263



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

Impact

If several association links are available to the destination office, service will not be affected. In the

case of heavy traffic, congestion of available association(s) might occur, leading to upper layer

call loss or increasing PS call access failures.

If merely one association link is available to the destination office, the office might become

inaccessible. Reception and sending of messages from/to the relevant office fail. Access of new

services under this office fails, and abnormal release of ongoing services occurs.

Action

1. Establish the association in dynamic data management.

2. On NMS configuration management interface, check ASP configuration at local end and opposite

end. Checking items include protocol type of SCTP association, SMP module No, local IP address,

local port No., remote IP address, remote port No., the number of in/out streams. If the configuration

at both ends is inconsistent, modify configuration to keep consistency.

3. Ping the opposite board address to see if the network cable or other 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.

3.2.28 198005129 Ethernet port loop back error

Alarm Information

Code: 198005129

Name: Ethernet port loop back error

Severity: Minor


Alarm Description

Ethernet port loop back error

Alarm Cause

Ethernet port loop back occurs.

3-264


Chapter 3 Alarms

Impact

There is a fault of the network in the system.

Action

1. Check alarm info of the board.

1) Check if the debug port loops back.

Y->Check the HUB or other device linked to the debug port. If there is loop back, destroy the loop

back and check if the alarm restored. Y-> The troubleshooting completes. N-> go to "2)".

N->No fault of the debug port, go to "2)".

2) Check if the port which linked to shelves loops back.

Y->Check if the connection between shelves is incorrect. Y->Correct the connection and check if the

alarm restored. Y->The troubleshooting completes. N-> go to "2".

N->No fault of the port linked to shelves, go to "2".

2. Make records of the alarm

information and contact the next level of maintenance support.

3.2.29 198031744 IPD session interrupted

Alarm Information

Code: 198031744

Name: IPD session interrupted

Severity: Minor


Alarm Description

IPD session is down

Alarm Cause

1. The network cable connection on relevant equipment (including local/intermediate/opposite

equipment) is loose or disconnected.

2. Intermediate equipment is faulty.


4. Local equipment is faulty.

5. Configuration related to the IPD session is incorrect.

Impact

All services on the path relating to the BFD session will be switched to the standby path. Service

interruption will occur if no standby path exists.

3-265



Action

Check alarm details on the NMS Alarm Management interface to find the source address and the

destination address of the BFD session. The source address refers to the address of local equipment.

The destination address refers to the address of the opposite IPD session equipment.

1. Check the status of the line card at the local end. If the line card restarts repeatedly, replace it

and power on.

2. Check the physical connection between the IPD session-related port and the local line card. If the

connection is loose or broken, 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 correct IP address.

i. Telnet to the interface board to check the link by making a ping test. For example, if the destination

address is 2.2.2.10, enter the following command in the telnet 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:Reply from 2.2.2.10: bytes=60 time<1ms" displays on the screen, it means the link

is normal.

iii. In case of timeout, check if the related route and address are configured correctly. If not, correct

the reconfiguration and do a ping test again.

iv. If the route/address is configured correctly but the response still times out, it means a link is broken

or the intermediate equipment is faulty. In this case, check to see if there is any broken network

cable, loose connection or abnormal equipment along the IPD session path. If yes, take necessary

actions, such as replacing the broken cable, tightening the connection, or repairing or replacing the

fault equipment, to solve the problem.

4. If the ping test indicates that packets can be received and sent normally at both ends, make sure

that the IPD session exists at the local end, and that the source and the destination IP addresses are

matched.

5. Reboot the board where the interface is located.

3.2.30 198105021 IP channel of Iub interface breaks down

Alarm Information

Code: 198105021

Name: IP channel of Iub interface breaks down

Severity: Minor


3-266


Chapter 3 Alarms

Alarm Description

The base station controller that has the "MultiPath Protection on Iub Interface" function enabled

detects that the IP service channel on the Iub interface is unavailable or the operation and

maintenance channel on the Iub interface is unavailable.

Alarm Cause

l The bottom-layer transmission is faulty, for example, the physical connection is broken.

l The configuration is not correct.

l The transport quality is degraded (for IP over Ethernet-based channels, the base station

controller detects that the packet loss rate is larger than 25 percent or receives less than three

keepalive packets consecutively. For IP over PPP-based channels, the base station controller

detects that the packet loss rate is larger than 70 percent or receives less than seven keepalive

packets consecutively).

l The hardware of the interface board on the local or peer end is faulty.

Impact

Related services and the operation and maintenance system may select another available IP channel

to transport data. If no available channel exists, services may be interrupted, or the connection

between the base station and network management system is broken.

Action

1. Check whether the following parameters are set in accordance with actual requirements:

l "Operation Maintenance Configuration(OmCon)". "OMCB Inner IP Address(InnerOm-

cbIpv4Addr)"

l "Operation Maintenance Configuration(OmCon)". "OMCB Inner IP Mask

Length(InnerIpv4MaskLen)"

l "Operation Maintenance Configuration(OmCon)". "OMCB Agent IPv4 Address to

NODEB(OmcbAgIpv4Addr)" (note:to IPv4 NODEB)

l "Operation Maintenance Configuration(OmCon)". "OMCB Agent IPv6 Address to

NODEB(OmcbAgIpv6Addr)" (note:to IPv6 NODEB)

Yes -> Step 3.

No -> Step 2.

2. Modify the above parameters as required or contact the maintenance personnel of the base

station to modify parameters. Wait for two minutes, and check whether the alarm is cleared.

Yes -> End.

No -> Step 3.

3. Check whether "Ip channel attribute" in the alarm information is "Service Channel".

Yes -> Step 4.

No -> Step 6.

4. Check whether the following parameters of the "Iub Transmission Path(UIubTrPath)" object are

set as required in accordance with "ANE id" and "Ip domain id or OMCB path id" in the alarm

information:

3-267



l Length of Destination IP address(DestIpVersion)

l Destination IP address(DestIpAddr)

l net mask length for Destination IP(DestIpMaskLen)

Yes -> Step 8.

No -> Step 5.



Yes -> End.

No -> Step 8.

6. Check whether the following parameters of the "Omcb Path(UOmcbPath)" object are set as

required in accordance with "ANE id" and "Ip domain id or OMCB path id" in the alarm information:

l OMCB Path IP Address Length(OmcbIpAddrVer)

l OMCB Path IP Address(OmcbIpAddr)

Yes -> Step 8.

No -> Step 7.



Yes -> End.

No -> Step 8.

8. Compare the network planning data to find the interface board location and physical port in

accordance with "NodeB ID"+ "The peer-side IP address" (IP transport) or "NodeB ID" + "The

peer-side IP address" + "cVpi" + "cVci" (IPoA transport) in the alarm information. Check whether

the related alarm arises on the board.

Yes -> Step 9.

No -> Step 10.

9. Handle the related alarm on the interface board. Wait for two minutes, and check whether the

alarm is cleared.

Yes -> End.

No -> Step 10.

10. Secure the cable connected to the interface board or replace the cable with an operational one.

Wait for two minutes, and check whether the alarm is cleared.

Yes -> End.

No -> Step 11.


3.2.31 198105035 The communication link between LogServiceboard and OMP is broken

Alarm Information

Code: 198105035

Name: The communication link between LogService board and OMP is broken

3-268


Chapter 3 Alarms

Severity: Minor


Alarm Description

The OMP detects an interruption of the link with the log server board.

Alarm Cause

l The log server board is not present.

l The software of the log server is not operating properly.

l The hardware of the log server board is faulty.

Impact

The OMM fails to obtain the signaling tracing data, and the NDS server fails to obtain the network

optimization data.

Action

1. Check whether the log server board is present.

Yes -> Step 3.

No -> Step 2.

2. Install the log server board into the corresponding slot. Wait for 10 minutes, and check whether


Yes -> End.

No -> Step 3.


3.2.32 198066000 Abis link broken

Alarm Information

l Alarm code: 198066000l Name: Abis link brokenl Alarm severity: Majorl Alarm type: Communication alarm

Alarm Description

Abis link down

3-269



Alarm Cause

1. A newly configured link is initially broken.

2. The link status changes to broken.

3. The link may break frequently during active/standby switchover.

Impact

BTS break-down

Action

If the new Abis link. Please synchronize and wait with no other operation, the alarm will resume

after 1 minute.

If master/slave change happened before, the alarm will resume after 1 minute, no need any operation.

Check the board has alarm "2560 Board cpu overload", please deal with first.

3.2.33 198005664 The rate of error code in a mate link is high atGUIM/GUIM2

Alarm Information

l Alarm code: 198005664l Name: The rate of error code in a mate link is high at GUIM/GUIM2l Alarm severity: Minorl Alarm type: Communication alarm

Alarm Description

The rate of error code in a mate link is high

Alarm Cause

The rate of error code in a mate link is high.

Impact

The data transferred via mate link are incorrect.

Action

1.Check if the board is inserted tightly.


N->Insert the board tightly,and then check if the alarm is eliminated: Y->end, N->contact the next


3-270


Chapter 3 Alarms

3.2.34 198066008 MTP2 link sending overload

Alarm Information

l Alarm code: 198066008l Name: MTP2 link sending overloadl Alarm severity: Majorl Alarm type: Communication alarm

Alarm Description

MTP2 link sending overload

Alarm Cause

The traffic flow carried by the MTP2 is excessive under the condition of current link bandwidth. It

exceeds the alarm threshold of link transmission load. The alarm threshold is related to MITP2 link

type. For 64K link, the alarm threshold is: bandwidth occupation ratio reaches 0.8. For N*64k or 2M

link, the alarm threshold is: bandwidth occupation ratio reaches 0.6.

Impact

If MTP2 link is overloaded for quite a long time, the signalling link will be congested. As a result,

service messages will be lost by MTP2 and the service will be interrupted.

Action

1. Add links to the office that is in service for the congested link.

2. Take the following measures to improve transmission quality of physical links.

Replace bottom layer lines.

Ensure that connector contact and cable connection are normal.

3.2.35 198066009 MTP2 link reception overload

Alarm Information

l Alarm code: 198066009l Name: MTP2 link reception overloadl Alarm severity: Majorl Alarm type: Communication alarm

Alarm Description

MTP2 link reception overload

3-271



Alarm Cause

The traffic flow carried by the MTP2 is excessive under the condition of current link bandwidth. It

exceeds the alarm threshold of link transmission load. The alarm threshold is related to MITP2 link

type. For 64K link, the alarm threshold is: bandwidth occupation ratio reaches 0.8. For N*64k or 2M

link, the alarm threshold is: bandwidth occupation ratio reaches 0.6.

Impact

This alarm has little impact on the local. If MTP2 link reception is overloaded for quite a long time,

the signalling reception will be congested. This may trigger the signalling flow control of MTP2

layer. In most serious case, package loss may occur, which leads to call loss or decrease of PS

access success rate.

Action

1. Add links to the office that is in service for the congested link.

2. Take the following measures to improve transmission quality of physical links.

Replace bottom layer lines.

Ensure that connector contact and cable connection are normal.

3.2.36 198066012 MTP3 cluster inaccessible

Alarm Information

l Alarm code: 198066012l Name: MTP3 cluster inaccessiblel Alarm severity: Majorl Alarm type: Communication alarm

Alarm Description

MTP3 cluster inaccessible

Alarm Cause

1. No service link exists in the cluster route.

2. TCP is received.

Impact

Reception and sending of messages from/to the relevant cluster fail. Access of new service under

this cluster fails, and abnormal release of the ongoing service occurs.

3-272


Chapter 3 Alarms

Action

1. Check if there exists unavailable link alarm. If yes, refer to the corresponding alarm handling

suggestion.

Related alarms: 8400129 MTP3 link unavailable

2. Check if cluster and link configuration at opposite end is correct.

3.2.37 198087775 Super site exchanged to the satellitic Abis linkor slave link

Alarm Information

l Alarm code: 198087775l Name: Super site exchanged to the satellitic Abis link or slave linkl Alarm severity: Majorl Alarm type: Communication alarm

Alarm Description

This alarm is reported if the BSC detects that the Abis link of the super station is exchanged to

the satellite link or the standby link.

Alarm Cause

The subaerial Abis link of the super station is broken.

Impact

This alarm has no impact on the current operation of the system. However, the system reliability

will be decreased.

Action

1. Locate the alarm object, and check whether the object reports the following alarms:

198066026 Association path broken

198066019 Association link broken

198066029 PPP link broken

Yes -> Step 2.

No -> Step 3.

2. Handle the alarm, and check whether the alarm is cleared.

Yes -> End.

No -> Step 3.


3-273



3.2.38 198087342 Cell interruption alarm

Alarm Information

l Alarm code: 198087342l Name: Cell interruption alarml Alarm severity: Minorl Alarm type: Communication alarm

Alarm Description

This alarm is reported if the BSC detects that the state of a cell is abnormal.

Alarm Cause

l The link between the BSC and the site that the cell belongs to is broken.

l The BCCH TRX of the cell is faulty.

l The cell is manually blocked.

l The configuration of related cell parameters is incorrect.

Impact

The cell fails to provide any voice or data service.

Action

1. Locate the site in accordance with "Site ID" in the alarm details, and check whether the following

alarms exist in the site:

198087336 Rack Abis control link broken

198087337 Site Abis control link broken

Yes -> Step 2.

No -> Step 3.


Yes -> End.

No -> Step 3.

3. Query the "GSM Cell Configuration(GGsmCell)" object of the cell, check the following parameters

of the object, perform necessary operations as required, and check whether the alarm is cleared.

l "Cell management"

Execute the QRY CELL command to query the cell state in accordance with "Site ID" and

"Bts ID". If the cell is manually blocked, execute the UNB CELL command to unblock the cell.

l "TRX management"

If the BCCH TRX corresponding to the cell is manually blocked, execute the UNB FUTRX or

UNB CUTRX command to unblock the TRX.

If the CU or FU operation state of the TRX is blocked, which indicates a TRX fault, query and

clear related alarms in the base station. If the alarm persists, proceed to Step 4.

l "Channel Management"

3-274


Chapter 3 Alarms

If the BCCH timeslot corresponding to the cell is manually blocked, execute the UNB TS

command to unblock the timeslot.

Yes -> End.

No -> Step 4.


3.2.39 198087380 TRX Manual Block

Alarm Information

l Alarm code: 198087380l Name: TRX Manual Blockl Alarm severity: Minorl Alarm type: Communication alarm

Alarm Description

This alarm is reported if the BSC detects that a TRX is manually blocked.

Alarm Cause

The TRX is manually blocked.

Impact

The blocked TRX fails to provide any service.

Action

1. Locate the blocked TRX in accordance with "Site ID", "Bts ID", and "Trx ID" in the alarm details,

and execute the UNB FUTRX or UNB CUTRX command to unblock the TRX. Check whether


Yes -> End.

No -> Step 2.


3.2.40 198087336 Rack Abis control link broken

Alarm Information

l Alarm code: 198087336l Name: Rack Abis control link brokenl Alarm severity: Criticall Alarm type: Communication alarm

3-275



Alarm Description

This alarm is reported if the BSC detects that the control link between the controller and a rack

is broken.

Alarm Cause

l The configured rack does not exist.

l In case of an IP site, the IP-related configuration is incorrect.

l In case of an E1 site, the Abis timeslot configuration is incorrect.

l The Abis transmission is abnormal.

Impact

The rack fails to provide any service.

Action

1. 1. Locate "Site ID" in the alarm details, and check whether the corresponding site is required in

the network planning.

Yes -> Step 2.

No -> Delete the site configuration, or suppress the alarm. End alarm handling.

2. 2. Check whether the following association and PPP related alarms exist in accordance with "Site

ID" or "office information" in the alarm details.


198000519 Trunk error

198000520 Trunk abnormal

Yes -> Step 3.

No -> Step 4.

3. 3. Handle the related alarms, and check whether this alarm is cleared.

Yes -> End.

No -> Step 4.


3.2.41 198087468 lapd jam alarm

Alarm Information

l Alarm code: 198087468l Name: lapd jam alarml Alarm severity: Majorl Alarm type: Communication alarm

3-276


Chapter 3 Alarms

Alarm Description

This alarm is reported if the BSC detects LAPD link congestion between the rack and the BSC.

Alarm Cause

l Too few LAPD links are configured.

l The traffic is too high.

Impact

A severe loss of frames occurs on LAPD channels, which results in abnormal or even interrupted

communication. The quality of service degrades.

Action

1. Check whether enough LAPD channels are configured in accordance with the number of TRXs

configured on the site.

The recommended configuration is as follows:

- When 6 TRXs are configured, at least one LAPD channel must be configured.

- When 7 to 16 TRXs are configured, at least two LAPD channels must be configured.

- When 17 to 26 TRXs are configured, at least three LAPD channels must be configured.

- When 27 to 36 TRXs are configured, at least four LAPD channels must be configured.

Yes -> Step 3.

No -> Step 2.

2. Add one or more LADP channels as follows: In Configuration Management, view the attributes

of the CMB board on the rack diagram of the base station, and then add an "OMU slot number".

Check whether the alarm is cleared.

Yes -> End.

No -> Step 3.

3. Check whether the following alarm and notification exist in accordance with "Site ID" in the

alarm details or the object reporting the alarm:

198087102 Power overvoltage/undervoltage alarm

198000576 Loss of Frame on Trunk

Yes -> Step 4.

No -> Step 5.


Yes -> End.

No -> Step 5.


3-277



3.2.42 198087337 Site Abis control link broken

Alarm Information

l Alarm code: 198087337l Name: Site Abis control link brokenl Alarm severity: Criticall Alarm type: Communication alarm

Alarm Description

This alarm is reported if the BSC detects that the LAPD communication link of a base station is broken.

Alarm Cause

l The configured site does not exist.

l In case of an IP site, the IP-related configuration is incorrect.

l In case of an E1 site, the Abis timeslot configuration is incorrect.

l The Abis transmission is abnormal.

Impact

All cells of the site fail to provide any voice or data service.

Action

1. Locate "Site ID" in the alarm details, and check whether the corresponding site is required in

the network planning.

Yes -> Step 2.

No -> Delete the site configuration, or suppress the alarm. End alarm handling.

2. Check whether the following association and PPP related alarms exist in accordance with "Site

ID" or "office information" in the alarm details.

198066026 Association path broken



Yes -> Step 3.

No -> Step 4.


Yes -> End.

No -> Step 4.


3-278


Chapter 3 Alarms

3.2.43 198087101 HW link broken

Alarm Information

l Alarm code: 198087101l Name: HW link brokenl Alarm severity: Minorl Alarm type: Communication alarm

Alarm Description

HW link broken

Alarm Cause

BTS internal communication breaks

Impact

The site fails to operate properly.

Action

1. Start HW self-loop test to check whether the cable connection goes wrong.

2. If all of DTRU fail to build link, re-plug CMB board.

3. If the software has problem, upgrade it.

3.3 Processing error Alarm

3.3.1 198015360 Microcode Is Abnormal

Alarm Information

Code: 198015360

Name: Microcode Is Abnormal

Severity: Major

Type: Processing error alarm

Alarm Description

Microcode is abnormal

3-279



Alarm Cause

The Network Processor hardware in the board (whose microcode is abnormal) is faulty.

Impact

The board will reboot.

If the alarm can be restored after board rebooting, all board services during rebooting will be down,

but access of new services to the board after rebooting will be successful.

If the alarm cannot be restored after board rebooting, all board services during and after rebooting will

be down.

Action

1. Wait for the board to reboot. If the alarm cannot be restored after board rebooting, unplug and

then plug the board.

2. If the alarm still cannot be restored, replace the board.

3.3.2 198023040 Number of alarms exceeds threshold.

Alarm Information

Code: 198023040

Name: Number of alarms exceeds threshold.

Severity: Major


Alarm Description

Number of board alarms exceeds threshold

Alarm Cause

The current alarm board has too many alarms so that the relevant alarm pool is full.

Impact

Alarms may be lost, but there is no impact on user services.

Action

1. Delete any temporarily useless virtual configuration resources of this board.

2. On NMS fault management interface, delete some alarms which have small system impact.

3-280


Chapter 3 Alarms

3.3.3 198066031 OMP alarm pool is full, unable to store any morealarms.

Alarm Information

Code: 198066031

Name: OMP alarm pool is full, unable to store any more alarms.

Severity: Major


Alarm Description

Number of OMP alarms exceeds threshold

Alarm Cause

There are too many system alarms. The alarm pool is full of system alarms.

Impact

Alarms may be lost, but there is no impact on user services.

Action

1. Delete any temporarily useless virtual configuration resources.

2. On NMS fault management interface, delete some alarms which have small system impact.

3.3.4 198066032 Loss of NTP time synchronisation

Alarm Information

Code: 198066032

Name: Loss of NTP time synchronisation

Severity: Minor


Alarm Description

NTP time exceeds the threshold

Alarm Cause

1. Control-panel link between OMP and RPU board is down.

2. NTP time and local time differs greatly.

3-281



Impact

NTP time synchronization terminates, bringing in time deviation between the foreground and the

background，effecting some services，such as charges, and leading to interruption of ongoing

services.

Action

On NMS fault management interface, check if the alarm related to RPU board exists. If yes, refer to

the corresponding alarm handling suggestion.

Related alarm: 198066004 Control plane communication abnormal between MP and OMP

3.3.5 198066027 SNTP failure

Alarm Information

Code: 198066027

Name: SNTP failure

Severity: Minor


Alarm Description

The client of the SNTP fail to gain the net time.

Alarm Cause

1. SNTP server does not exist or it works abnormally.

2. The configured SNTP IP address in database is different from its real IP address.

3. The communication between Network Element and SNTP server is broken.

4. The time synchronization period configured in the database might be 0.

Impact

SNTP synchronization failure may cause time difference between system 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 frequency

is correct, services will not be affected.

3-282


Chapter 3 Alarms

Action



The handling suggestions for each type are described as below.

1. Invalid database configuration.

In NMS Configuration Management interface, click Network Element Ground Resource Management

to check whether the IP address of SNTP server is invalid, or SNTP synchronization period is wrong.

If the IP address of SNTP server is 255.255.255.255 or SNTP synchronization period is 0, please

correct the configuration.

2. Failure in getting time from SNTP server

1) Ensure that SNTP server exists and it works normally.

2) Ensure that the configured IP address of SNTP server in database is the same as its real IP

address.

3.3.6 198005387 Alarm due to inconsistent MP type

Alarm Information

Code: 198005387

Name: Alarm due to inconsistent MP type

Severity: Major


Alarm Description

MP type in database does not agree with the one in bootcfg.ini

Alarm 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 with that configured on NMS.

Impact

There is no impact on services

Action

1. For CMP and SMP, reset the board through NMS man-machine command interface.

2. For OMP, set the start mode as "foreground start" on NMS and then reset the board.

Do as follows:

On NMS software version management interface, select the menu for querying foreground (that is,

RNC NE) board start mode. In the pop-up dialog box, set the start mode to "foreground start".

3-283



3.3.7 198005388 Startup file does not exist

Alarm Information

Code: 198005388

Name: Startup file does not exist

Severity: Major


Alarm Description

Failed to read the Bootcfg.ini file from OMP Flash

Alarm Cause

The startup configuration file is deleted.

Impact

This alarm may cause OMP work abnormally, and the entire network element services are affected.

Action

1. Reset the active and standby OMPs through NMS man-machine command interface.


3.3.8 198005398 Office ID is not set correctly with control shelf

Alarm Information

Code: 198005398

Name: Office ID is not set correctly with control shelf

Severity: Major


Alarm Description

The office No of dial switch is different.

Alarm Cause

The office ID of a shelf where DIP switch locates is different from that of a shelf where OMP locates.

3-284


Chapter 3 Alarms

Impact

The MAC address conflicts. The MAC and IP address verification fails. All boards on the shelf can

not be powered on. All services carried by the shelf are interrupted.

Action

By operating the hardware dial code key on the shelf, Set the office ID of the shelf where DIP switch

locates to be the same as that of OMP belonged shelf.

3.3.9 198005402 Database config is different from file namedbootcfg.ini

Alarm Information

Code: 198005402

Name: Database config is different from file named bootcfg.ini

Severity: Major


Alarm Description

The Data from the OMP database is inconsistent with that previously saved on the OMP

Alarm Cause

After the start information of OMP is modified, the active and standby OMP boards are not restarted.

Impact

System startup is abnormal, MP may not work normally.

Action

Restart the active and the standby OMP boards at the same time through NMS man-machine

interface command .

3.3.10 198005649 Port configuration is incorrect

Alarm Information

Code: 198005649

Name: Port configuration is incorrect

3-285



Severity: Major


Alarm Description

Port work mode doesn't match the settings

Alarm Cause

1. The speed mode configuration of the port does not take effect.

2. The duplex mode configuration of the port does not take effect.

3. The master or slave mode configuration of the port does not take effect.

4. The auto negotiation mode configuration of the port does not take effect.

Above four points, the set work mode of the external port does not take effect due to faulty

performance of the chip on the local end or unsuccessful settings on the peer end.

Impact

1. The port fails to work in the preset mode. This causes the port to be unavailable and all services

of the port are interrupted.

2. For Auto mode, the bandwidth of the external port becomes insufficient. As a result, some services

of the port are interrupted.

Action

On NMS fault management interface, check the alarm details, which give the reasons of mode error.

You can quickly locate the handling method according to it.

The handling suggestions for each reason of mode error are as follows:

Speed mode error

1.Check the speed settings on the both end ports if they are correct and consistent.

Y->Go to "2".

N->Modify the speed settings, which the hardware supports on the both end, to make them be

consistent with each other, and then check the alarm if it is eliminated.

Y->End.

N->Go to "2".

2.Please contact the next level of maintenance support.

Duplex mode error

1.Check the duplex mode settings on the both ports end if they are correct and consistent.

Y->Go to "2".

N->Modify the duplex mode settings, which the hardware supports on the both end, to make them be


Y->End.

N->Go to "2".


GE port master or slave mode error

1.Check the master and slave mode settings on the both end ports if they are correct and consistent.

3-286


Chapter 3 Alarms

Y->Go to "2".

N->Modify the master or slave mode settings, which the hardware supports on the both end, to make

them match with each other, and then check the alarm if it is eliminated.

Y->End.

N->Go to "2".


Auto negotiation failed

1.Check the work mode settings on the both end ports if they are correct and consistent, if one of

them is auto negotiation, the other one can not be force mode.

Y->Go to "2".

N->Modify the work mode settings, which the hardware supports on the both end, to make them be


Y->End.

N->Go to "2".


3.3.11 198005123 Incorrect configuration for inserted board ordevice

Alarm Information

Code: 198005123

Name: Incorrect configuration for inserted board or device

Severity: Minor


Alarm Description

The equipment type configured in the DB is inconsistent with the hardware device

Alarm Cause

1. Incorrect board in slot.

2. Board hardware does not match the OMC-R configuration.

Impact

The board fails to be normally powered on. The services carried by the board are interrupted.

3-287



Action

1. The NMS configuration management interface gives the rack diagram. Select the board and check

if the Basic Information and CPU Information of the rack are correct. If the settings are incorrect,

delete the board and create a new one.

2. Check if a correct board is inserted in the slot on the rack. If not, insert the correct one.

3.3.12 198066013 MTP3 link congestion

Alarm Information

Code: 198066013

Name: MTP3 link congestion

Severity: Major


Alarm Description

MTP3 link congest. The messages that MTP3 sent to MTP2 have reached a particular percentage in

MTP2 buffers and queues.

Alarm Cause

1. There are too many messages at upper layer.

2. The quality of bottom layer link is so poor that many messages are retransmitted.

Impact

Link congestion will cause transmission delay. If congestion is not serious, services will not be

affected. However, if it is serious, packet loss or call loss may occur, and access success rate of

PS services may fall.

Action

1. Check the peak traffic of MTP3(B) signaling link performance statistics. If the payload reach to

6000, it's necessary to add links or increase the PVC bandwidth.

2. Check the physical connection, and check the following alarm. If there are some alarms as follows,

solve related alarms firstly.

(1) Fiber access:

1792 SDH/SONET faulty

1824 SDH/SONET exception

(2) E1 access:

519 trunk faulty

1026 E1 ATM cell synchronization failed

3-288


Chapter 3 Alarms

3.3.13 198066018 Association congestion

Alarm Information

Code: 198066018

Name: Association congestion

Severity: Minor


Alarm Description

Association congestion

Alarm Cause

1. Transmission quality of bottom layer link(include the physical links between interface board and

signal processing board inside network element and the physical links between interface board and

opposite network element) is poor.

2. Upper layer traffic in sending service data is heavy, confirming it by the traffic networking model.

Impact

Link congestion will cause transmission delay. If congestion is not serious, services will not be

affected. However, if it is serious, packet loss or call loss may occur, and access success rate of

PS services may fall.

Action

1. Check network cable connection. Ensure that the network cable is tightly inserted.

2. Add association links to the office that is in service for the congested association.

3. If intermediate equipment exists between local end and opposite end, check the transmission

quality of intermediate equipment.

3.3.14 198105027 The RUB board is overload

Alarm Information

Code: 198105027

Name: The RUB board is overload

Severity: Minor


3-289



Alarm Description

The user-plane processing board detects that the CPU is overloaded ("BGlobal(Bglobal)"."RUP

Congestion Threshold(RupCongestThr)").

Alarm Cause

l The threshold is not properly set.

l The amount of the traffic on the user plane is too high.

Impact

Some users who are connected through the RUB may be rejected.

Action

1. Check whether the threshold configuration ("BGlobal(Bglobal)". "RUP Congestion

Threshold(RupCongestThr)") is in accordance with actual requirements (the recommended

setting is 95).

Yes -> Step 3.

No -> Step 2.

2. Modify the threshold as required. Wait for five minutes, and check whether the alarm is cleared.

Yes -> End.

No -> Step 3.

3. Wait for 30 minutes, and check whether the alarm is cleared.

Yes -> End.

No -> Step 4.

4. Contact the next level of maintenance support (it is recommended to optimize the configuration or

expand the capacity).

3.3.15 198007936 Memory file buffer overflow

Alarm Information

l Alarm code: 198007936l Name: Memory file buffer overflowl Alarm severity: Majorl Alarm type: Processing error alarm

Alarm Description

Memory file buffer overflow

3-290


Chapter 3 Alarms

Alarm Cause

The transferred data records exceed the maximum capacity of the table, and the capacity of the

receiver memory file buffer is insufficient.

Impact

If the board is powering on, the excessive data records (beyond table capacity) are discarded.

Action

1. Lookup if the capacity of the table is correct, please make records of the alarm information and

contact the next level of maintenance support.

2. Synchronize the capacity tables, then synchronize all tables to the foreground and reboot the

board. If the alarm still has not restored, please make records of the alarm information and contact

the next level of maintenance support.

3.3.16 198005120 T Network Connection Not Conform toConfiguration

Alarm Information

l Alarm code: 198005120l Name: T Network Connection Not Conform to Configurationl Alarm severity: Criticall Alarm type: Processing error alarm

Alarm Description

The fiber connection is error

Alarm Cause

T network fiber connection does not conform to optical interface connection relation configured on

the background.

Impact

T Net switch of the shelf is in disorder.

Action

Modify the fiber connection or the connection configuration to keep the configuration consistent

with the physical connection.

3-291



3.3.17 198005889 Version Switches While Board Doesn't Reset

Alarm Information

l Alarm code: 198005889l Name: Version Switches While Board Doesn't Resetl Alarm severity: Warningl Alarm type: Processing error alarm

Alarm Description

Version switch information

Alarm Cause

1. Appoint the version for OMP and select the option of restart after switch,but the version file have

existed on OMP's DOC0.2.Swtich the BOOT version.

Impact

The board version will not take effect if the board does not reset.

Action

Restart the board manually.

3.3.18 198005892 Boot Version Fails to Write to Backup Region

Alarm Information

l Alarm code: 198005892l Name: Boot Version Fails to Write to Backup Regionl Alarm severity: Warningl Alarm type: Processing error alarm

Alarm Description

BOOT version synchronization information

Alarm Cause

Boot version fails to be written to backup region.

Impact

BOOT backup version is unavailable.

3-292


Chapter 3 Alarms

Action

Switch BOOT again and restart the board manually.

3.3.19 198087482 dbsapp data error alarm

Alarm Information

l Alarm code: 198087482l Name: dbsapp data error alarml Alarm severity: Majorl Alarm type: Processing error alarm

Alarm Description

This alarm is reported if the BSC detects data errors in the following two processes:

- Power-on loading

- Data synchronization

Alarm Cause

Configuration data errors occur.

Impact

Some or all services may operate improperly.

Action

1. In Configuration Management, perform the "Synchronize All Data" operation on the

configuration data. Wait for five minutes, and check whether the alarm is cleared.

Note: The "Synchronize All Data" operation may cause a system restart. Perform the operation

with care.

Yes -> End.

No -> Step 2.

2. Execute the SET NORMALCHANGE command for active/standby switchover based on "Rack

number", "Shelf number", "Slot number", and "CPU number" in the alarm details. Wait for two

minutes, and check whether the alarm is cleared.

Yes -> End.

No -> Step 3.


3-293



3.3.20 198087505 Board Connect Fail

Alarm Information

l Alarm code: 198087505l Name: Board Connect Faill Alarm severity: Majorl Alarm type: Processing error alarm

Alarm Description

This alarm is reported if the BSC detects that the service connection failure count of one board

exceeds the threshold.

Alarm Cause

l The card version is not correct.

l The board is configured improperly.

l The versions of the base station and the base station controller are not compatible with each

other.

Impact

Some services are not available.

Action

l If the alarm is reported that the cause of AIPB board alarm is 1 or the cause of DRTB/TIPB

board alarm is 2, the port number is allocated unsuccessfully. You need to query the network

management system and check whether the IPUDP resources assigned to the board is sufficient.

If the IPUDP resources are insufficient, you need increase the resources. Otherwise, contact the

next level of maintenance support.

l If the alarm is reported that the cause of AIPB board alarm is 3 or the cause of DRTB/TIPB board

alarm is 7, the next hop is obtained unsuccessfully. You need to check whether the version of the

base station is not compatible with the version of the BSC. If the version of the base station is not

compatible with the version of the BSC, you need to load the proper version for the base station.

If the version of the base station is compatible with the version of the BSC, you need to check the

route configuration of CN user plane. If the route configuration of CN user plane is incorrect, you

need to modify the configuration. Otherwise, contact the next level of maintenance support.

l If the alarm is reported that the cause of AIPB/BIPB board alarm is 4 or the cause of DRTB/TIPB

board alarm is 8, you need to check whether all VTCD boards and GLI boards are configured

properly and check whether the version is powered on properly. If there is anything wrong, you

need to make a modification. Otherwise, contact the next level of maintenance support.

3-294


Chapter 3 Alarms

3.4 QoS Alarm

3.4.1 198023296 Inter-board message communication flow rateexceeds the alarm threshold

Alarm Information

Code: 198023296

Name: Inter-board message communication flow rate exceeds the alarm threshold

Severity: Minor

Type: QoS alarm

Alarm Description

The communication flow rate in input and output directions of the control plane exceeds the alarm

threshold

Alarm Cause

The configured alarm threshold is less than the usual inter-board communication traffic in input

and output directions of the board control plane.

Impact

Packet of the control plane loss might occur. No impact on user service.

Action

On NMS configuration management interface, check if the configured alarm threshold of

communication traffic in input and output directions of the board control plane is too low.

Recommended value: 0xffffffff(4096M).

3.4.2 198066069 The number of times of signaling data transferexceeds the allowed threshold of the license

Alarm Information

Code: 198066069

Name: The number of times of signaling data transfer exceeds the allowed threshold

of the license

Severity: Major

Type: QoS alarm

3-295



Alarm Description

The number of times of signaling data transfer over threshold

Alarm Cause

The number of transfer that passes MTP3/M3UA/SCCP/SUA exceed the permission of license.

Impact

The data may be discarded in all MP boards.

Action

Contact the related personnel and get proper license again.

3.4.3 198087344 MSC overload control alarm at FUC mode

Alarm Information

l Alarm code: 198087344l Name: MSC overload control alarm at FUC model Alarm severity: Minorl Alarm type: QoS alarm

Alarm Description

This alarm is reported if the BSC initiates flow control in "FUC control mode" upon receiving

"OVERLOAD" from the MSC through the A-interface.

The "FUC control mode" allows the base station to discard the access messages of some MSs as

required by the BSC.

Alarm Cause

The BSC receives "OVERLOAD" from the MSC.

Impact

Some new users fail to gain access to the system.

Action

No action is required.

3-296


Chapter 3 Alarms

3.4.4 198087345 CPU overload control alarm at FUC mode

Alarm Information

l Alarm code: 198087345l Name: CPU overload control alarm at FUC model Alarm severity: Minorl Alarm type: QoS alarm

Alarm Description

This alarm is reported if the BSC initiates flow control in "FUC control mode" upon detecting that the

CPU load is above "GSM Logical Configuration(GBssFunction)"."Start limit of FUC flow control

for CPU overload(CpuFucCtlCpu)".



Alarm Cause

The system traffic becomes too high transiently.

Impact

Some users fail to gain access to the system due to the flow control automatically initiated by the

BSC. If the traffic is still excessive after flow control, the CPU load may grow further. In this case,

the system may break down.

Action

1. 1. Query "Flow Control Level" in the alarm details. If the flow control level is five or lower, wait for

three minutes, and check whether the alarm is cleared.

Yes -> End.

No -> Step 2.

2. 2. Execute the BLK FUTR or BLK CUTR command based on "Site ID", "Bts ID", and "Trx

ID" to block some cells. In this way, the access of some users can be limited to avoid system

breakdown caused by further increase of the CPU load. Check whether the alarm is cleared.

Yes -> Step 3.

No -> Step 2.

3. 3. Execute the UNB FUTRX or UNB CUTRX command to unblock some cells one batch at a

time based on "Site ID", "Bts ID", and "Trx ID". The alarm handling is completed.

3-297



3.4.5 198087346 Signaling point congestion control alarm at FUCmode

Alarm Information

l Alarm code: 198087346l Name: Signaling point congestion control alarm at FUC model Alarm severity: Minorl Alarm type: QoS alarm

Alarm Description

This alarm is reported if the BSC initiates flow control in "FUC control mode" upon detecting No.7

signaling point congestion on the A-interface.



Alarm Cause

The A-interface is congested with excessive No.7 signaling messages.

Impact


BSC. If the traffic is still excessive after flow control, the signaling on the A-interface may be blocked

and services may be interrupted.

Action

1. Query "Flow Control Level" in the alarm details. If the flow control level is five or lower, wait for


Yes -> End.

No -> Step 2.

2. Execute the BLK FUTR or BLK CUTR command based on "Site ID", "Bts ID", and "Trx ID" to

block some cells. In this way, the access of some users can be limited to avoid A-interface

disconnection caused by further increase of the No.7 signaling load. Check whether the alarm

is cleared.

Yes -> Step 3.

No -> Step 2.

3. Execute the UNB FUTRX or UNB CUTRX command to unblock some cells one batch at a time

based on "Site ID", "Bts ID", and "Trx ID". The alarm handling is completed.

3-298


Chapter 3 Alarms

3.4.6 198087347 MSC overload control alarm at SYS mode

Alarm Information

l Alarm code: 198087347l Name: MSC overload control alarm at SYS model Alarm severity: Minorl Alarm type: QoS alarm

Alarm Description

This alarm is reported if the BSC initiates flow control in "system message control mode" upon

receiving "OVERLOAD" from the MSC through the A-interface.

The "system message control mode" allows the base station to deny the access of some MSs through

the system information broadcasted over the air interface.

Alarm Cause

The BSC receives "OVERLOAD" from the MSC.

Impact


Action


3.4.7 198087348 CPU overload control alarm at SYS mode

Alarm Information

l Alarm code: 198087348l Name: CPU overload control alarm at SYS model Alarm severity: Minorl Alarm type: QoS alarm

Alarm Description


detecting that the CPU load is above "GSM Logical Configuration(GBssFunction)"."Start limit of

system message method for CPU overload(CpuSysInfoCtlCpu)".



3-299



Alarm Cause


Impact




Action

1. 1. Query "Flow Control Level" in the alarm details. If the flow control level is eight or lower, wait

for three minutes, and check whether the alarm is cleared.

Yes -> End.

No -> Step 2.

2. 2. Execute the BLK CELL command to block some cells based on "Site ID" and "Bts ID" in the

alarm details. In this case, the access of some users can be limited to avoid system breakdown

caused by excessive CPU load. Check whether the alarm is cleared.

Yes -> Step 3.

No -> Step 2.

3. 3. Execute the UNB CELL command to unblock some cells based on "Site ID" and "Bts ID" in the

alarm details. The alarm handling is completed.

3.4.8 198087349 Signaling point congestion control alarm at SYSmode

Alarm Information

l Alarm code: 198087349l Name: Signaling point congestion control alarm at SYS model Alarm severity: Minorl Alarm type: QoS alarm

Alarm Description


detecting No.7 signaling point congestion on the A-interface.



Alarm Cause

The A-interface is congested with excessive No.7 signaling messages.

3-300


Chapter 3 Alarms

Impact


BSC. If the traffic is still excessive after flow control, the signaling on the A-interface may be blocked

and services may be interrupted.

Action

1. Query "Flow Control Level" in the alarm details. If the flow control level is eight or lower, wait for


Yes -> End.

No -> Step 2.

2. Execute the BLK CELL command to block some cells in accordance with "Site ID" and "Bts ID"

in the alarm details. In this case, the access of some users can be limited to avoid system

breakdown caused by excessive CPU load. Check whether the alarm is cleared.

Yes -> Step 3.

No -> Step 2.

3. Execute the UNB CELL command to unblock some cells in accordance with "Site ID" and "Bts

ID" in the alarm details. The alarm handling is completed.

3.4.9 198087350 CCCH overload control

Alarm Information

l Alarm code: 198087350l Name: CCCH overload controll Alarm severity: Minorl Alarm type: QoS alarm

Alarm Description

This alarm is reported if the BSC detects the RACH load of a cell exceeds the threshold ("GSM

Cell Configuration(GGsmCell)"."CCCH load indication (RACH)(CcchLoadINDThs_0)"), or the PCH

load of a cell exceeds the threshold ("GSM Cell Configuration(GGsmCell)"."CCCH load indication

(PCH)(CcchLoadINDThs_1)").

Alarm Cause

Too many MSs request to gain access to the CCCH.

Impact

Some MS CS services under this cell fail to gain access to the system due to the flow control

automatically initiated by the BSC.

3-301



Action


ten minutes, and check whether the alarm is cleared.

Yes -> End.

No -> Step 2.

2. If the alarm occurs frequently, contact network optimization engineers to:

- add CCCHs to the cell, or

- expand the capacity of the overloaded cell, or

- share the traffic.

3.4.10 198087506 NSE block alarm

Alarm Information

l Alarm code: 198087506l Name: NSE block alarml Alarm severity: Majorl Alarm type: QoS alarm

Alarm Description

This alarm is reported if the BSC detects that all NSVCs of an NSE are in the "block" state.

Alarm Cause

1. All NSVCs of the NSE are manually blocked.

2. Gb interface link is broken.

Impact

The PS service of this NSE is unavailable.

Action

1. 1. Locate the alarm object in State Management, and query the state of NSCV link. Verify that

the state is "manual block".

Yes -> Step 2.

No -> Step 3.

2. 2. Execute the UNB NSVC command to unblock all NSVC links which are in the "manual

block" state and check whether the alarm is cleared in accordance with "SGSN ID", "NSE ID",

and "NSVC ID" in the alarm details.

Yes -> End.

No -> Step 3.

3. 3. Check whether the following alarms exist:

198087352 NSVC's E1 failure alarm

3-302


Chapter 3 Alarms

198087465 NSVC's IP failure alarm

Yes -> Step 4.

No -> Step 5.

4. 4. Handle the alarm, and check whether the alarm is cleared.

Yes -> End.

No -> Step 5.


3.4.11 198087507 SGSN is blocked

Alarm Information

l Alarm code: 198087507l Name: SGSN is blockedl Alarm severity: Majorl Alarm type: QoS alarm

Alarm Description

This alarm is reported if the BSC detects that all NSVCs of an SGSN are in the "block" state.

Alarm Cause

l All NSVCs of the SGSN are manually blocked.

l Gb interface link is broken.

Impact

The PS service of this SGSN is unavailable.

Action

1. Execute the QRY NSV command to query the state of this NSVC link and check whether the state

is "manual block" in accordance with "SGSN ID", "NSE ID", and "NSVC ID" in the alarm details.

Yes -> Step 2.

No -> Step 3.

2. Execute the UNB NSVC command to unblock all NSVC links which are in the "manual block"

state and check whether the alarm is cleared in accordance with "SGSN ID", "NSE ID", and

"NSVC ID" in the alarm details.

Yes -> End.

No -> Step 3.

3. Check whether the following alarms exist:

198087352 NSVC's E1 failure alarm

198087465 NSVC's IP failure alarm

Yes -> Step 4.

3-303



No -> Step 5.

4. Handle the alarm, and check whether the alarm is cleared.

Yes -> End.

No -> Step 5.


3.4.12 198087513 Board Ethernet port overload alarm

Alarm Information

l Alarm code: 198087513l Name: Board Ethernet port overload alarml Alarm severity: Majorl Alarm type: QoS alarm

Alarm Description

This alarm is reported if the BSC detects that the connection count of an Ethernet port on the BIPB

board exceeds the threshold (2500 routes).

Alarm Cause


Impact

Packet loss may occur on the Ethernet port and the service quality is degraded.

Action

1. Wait for 2 hours, and check whether the alarm is cleared.

Yes -> End.

No -> Step 2.

2. Contact the next level of maintenance support. (It is recommended to add more BIPB boards for

capacity expansion.)

3.4.13 198087758 Manual User Access control alarm

Alarm Information

l Alarm code: 198087758l Name: Manual User Access control alarml Alarm severity: Minorl Alarm type: QoS alarm

3-304


Chapter 3 Alarms

Alarm Description

This alarm is reported if the BSC initiates flow control in "manual user access control mode".

"manual user access control mode" indicates that the network management system delivers flow

control parameters to the BSC and the BSC executes flow control unconditionally.

Alarm Cause

The "manual user access control" function is initiated.

Impact


Action


3.4.14 198087759 CPU overload control alarm at Paging mode

Alarm Information

l Alarm code: 198087759l Name: CPU overload control alarm at Paging model Alarm severity: Minorl Alarm type: QoS alarm

Alarm Description

This alarm is reported if the BSC initiates flow control in "paging control mode" upon detecting that

the CPU load exceeds the threshold ("GSM Logical Configuration(GBssFunction).CPU threshold of

paging flow control(CpuPagingCtlCpu)").

"paging control mode" indicates that the BSC discards some paging messages.

Alarm Cause


Impact




3-305



Action


in the alarm details. Limit the access of some users to avoid system breakdown caused by

excessive CPU load. Check whether the alarm is cleared.

Yes -> Step 2.

No -> Step 1.



3.4.15 198087773 CIC manual blocked alarm

Alarm Information

l Alarm code: 198087773l Name: CIC manual blocked alarml Alarm severity: Minorl Alarm type: QoS alarm

Alarm Description

This alarm is reported if the BSC detects that the state of A-interface trunk circuit is manually blocked.

Alarm Cause

Trunk circuit of A-interface is manually blocked.

Impact

The blocked circuit cannot provide services.

Action

1. Check whether the object is manually blocked by maintenance personnel.

Yes -> End.

No -> Step 2.

2. Locate the alarm object, and search the parent object "Trx(GTrx)". Check the parameter "TRX

Sequence(GTrxSeq)".

Locate the carrier object, and search the parent object of this carrier "GSM Cell

Configuration(GGsmCell)". Check the parameter "GSM Cell Configuration ID(GGsmCellId)".

Locate the GSM cell configuration object, and search the parent object of the

GSM cell configuration object "Site(GBtsSiteManager)". Check the parameter "Site

ID(GBtsSiteManagerId)".

Execute the UNB TS command to unblock this time slot in accordance with "Ts ID" in the above

three parameters and the alarm details. Check whether the alarm is cleared.

Yes -> End.

3-306


Chapter 3 Alarms

No -> Step 3.


3.4.16 198087774 BVC manual blocked alarm

Alarm Information

l Alarm code: 198087774l Name: BVC manual blocked alarml Alarm severity: Minorl Alarm type: QoS alarm

Alarm Description

This alarm is reported if the BSC detects that the state of BVC is manually blocked.

Alarm Cause

BVC is manually blocked.

Impact

The blocked BVC cannot provide services.

Action

1. 1. Check whether the object is manually blocked by maintenance personnel.

Yes -> End.

No -> Step 2.

2. 2. Execute the UNB BVC command to unblock this BVC in accordance with "SGSN ID", "NSEI",

and "BVC ID" in the alarm details. Check whether the alarm is cleared.

Yes -> End.

No -> Step 3.


3.4.17 198087517 Shelf overload control alarm at FUC mode

Alarm Information

l Alarm code: 198087517l Name: Shelf overload control alarm at FUC model Alarm severity: Minorl Alarm type: QoS alarm

3-307



Alarm Description

This alarm is reported if the BSC initiates flow control in "FUC control mode" upon detecting inter-shelf

traffic overload in the system.

The "FUC control mode" allows the base station to discard the access messages of some mobile

phones as required by the BSC.

Alarm Cause


Impact


Action

1. 1. Query "Flow Control Level" in the alarm details. If the flow control level is five or lower, wait for


Yes -> End.

No -> Step 2.

2. 2. Execute the BLK CELL command to block some cells in accordance with "Site ID" and "Bts

ID" in the alarm details. Limit the access of some users to avoid system breakdown caused by

further increase of the inter-shelf traffic. Check whether the alarm is cleared.

Yes -> Step 3.

No -> Step 2.

3. 3. Execute the UNB CELL command to unblock some cells one batch at a time in accordance

with "Site ID" and "Bts ID" in the alarm details. The alarm handling is completed.

3.4.18 198087518 Shelf overload control alarm at SYS mode

Alarm Information

l Alarm code: 198087518l Name: Shelf overload control alarm at SYS model Alarm severity: Minorl Alarm type: QoS alarm

Alarm Description


detecting inter-shelf traffic overload in the system.



3-308


Chapter 3 Alarms

Alarm Cause


Impact


Action



Yes -> End.

No -> Step 2.


in the alarm details. In this case, the access of some users can be limited to avoid system

breakdown caused by further increase of the inter-shelf traffic. Check whether the alarm is

cleared.

Yes -> Step 3.

No -> Step 2.



3.4.19 198087381 The time-slot of air interface blocked manually

Alarm Information

l Alarm code: 198087381l Name: The time-slot of air interface blocked manuallyl Alarm severity: Minorl Alarm type: QoS alarm

Alarm Description

This alarm is reported if the BSC detects that a timeslot of the air interface is manually blocked.

Alarm Cause

The timeslot is manually blocked.

Impact

The blocked timeslot fails to provide any service.

3-309



Action

1. Check whether the object is manually blocked by maintenance personnel.

Yes -> End.

No -> Step 2.

2. Locate the blocked timeslot in accordance with "Site ID", "Bts ID", "Trx ID", and "Ts ID" in the

alarm details, and execute the UNB TS command to unblock the timeslot. Check whether the

alarm is cleared.

Yes -> End.

No -> Step 3.


3.5 Environment Alarm

3.5.1 198025856 Rack temperature is high

Alarm Information

Code: 198025856

Name: Rack temperature is high

Severity: Minor

Type: Environment alarm

Alarm Description

Rack temperature is high

Alarm Cause

1. Fan is not working.

2. Fan has failed.

3. No fan connected.

4. Temperature sensor is faulty or setting is incorrect.

Impact

1. If an unreasonable threshold is configured, services will not be affected.

2. If the alarm is caused by high rack temperature, board may work abnormally and board services

may be interrupted.

3-310


Chapter 3 Alarms

Action

1. In NMS Configuration Management interface, click Power Board Alarm Parameters to view the

upper threshold of rack temperature. If the configuration is unreasonable, please modify it. The

recommended value of upper threshold is 70 degrees in Celsius.

2. Check the thermometer in equipment room to see if the actual temperature is too high. If yes, take

necessary cooling measures.

3. Remove dust from air intake and outlet of the rack. Remove any obstacle nearby which may

affect ventilation.

4. Ensure that the rack fan works normally.

3.5.2 198025857 Low temperature in Rack

Alarm Information

Code: 198025857

Name: Low temperature in Rack

Severity: Minor


Alarm Description

Rack temperature is low

Alarm Cause

1. Threshold is incorrect.

2. Temperature sensor is not working

3. External room heating control not working.

Impact


2. If the alarm is caused by low rack temperature, board may work abnormally and board services

may be interrupted.

Action


lower threshold of rack temperature. If the configuration is unreasonable, please modify it. The

recommended value of lower threshold is 0 degrees Celsius.

2. Check the thermometer in equipment room to see if the actual temperature is too low. If yes,

take necessary warming measures.

3. Setting the sensor correctly.

3-311



3.5.3 198025858 Room temperature is higher than high threshold

Alarm Information

Code: 198025858

Name: Room temperature is higher than high threshold

Severity: Minor


Alarm Description

Room temperature is higher than high threshold

Alarm Cause

1. Threshold configuration is unreasonable.

2. Actual temperature in equipment room is too high.

Impact


2. If the alarm is caused by high room temperature, board may work abnormally and board services

may be interrupted.

Action

1. On NMS configuration management interface (power board alarm parameters), check the upper

limit of equipment room temperature. Modify the threshold value if the previous configuration is

unreasonable. The recommended high threshold value is 40.

2. Check the thermometer in equipment room to see if the actual temperature is too high. If yes, take

necessary cooling and ventilation measures.

3.5.4 198025859 Room temperature is lower than low threshold

Alarm Information

Code: 198025859

Name: Room temperature is lower than low threshold

Severity: Minor


Alarm Description

Room temperature is lower than low threshold

3-312


Chapter 3 Alarms

Alarm Cause

1. The configured threshold is unreasonable.

2. Actual temperature in equipment room is too low.

3. Setting of the sensor is incorrect.

Impact


2. If the alarm is caused by low room temperature, board may work abnormally and board services

may be interrupted.

Action


lower threshold of room temperature. If the configuration is unreasonable, please modify it. The

recommended value of lower threshold is 0 degrees Celsius.

2. Check the thermometer in equipment room to see if the actual temperature is too low. If yes,

take necessary warming measures.


3.5.5 198025860 Rack voltage is high

Alarm Information

Code: 198025860

Name: Rack voltage is high

Severity: Minor


Alarm Description

Rack voltage is high

Alarm Cause


2. Actual voltage is too high.

Impact


2. If the alarm is caused by high voltage, board may work abnormally and board services may

be interrupted.

3-313



Action


upper threshold of rack voltage. If the configuration is unreasonable, please modify it. For 48V power

supply, the recommended value of upper threshold is 57V; for 60V power supply, the recommended

value is 72.

2. Find out which line voltage exceeds upper threshold by using the voltage index given in alarm

details. Regulator through the power supply equipment to lower down the input voltage of this line.

3.5.6 198025861 rack voltage is low

Alarm Information

Code: 198025861

Name: rack voltage is low

Severity: Minor


Alarm Description

Rack voltage is low

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

Impact


2. If the alarm is caused by low voltage, board may work abnormally and board services may be

interrupted.

Action


lower threshold of rack voltage. If the configuration is unreasonable, please modify it. For 48V power

supply, the recommended value of lower threshold is 40V; for 60V power supply, the recommended

value is 50.

2. Find out which line voltage is below lower threshold by using the voltage index given in alarm

details. Regulator through the power supply equipment to increase the input voltage of this line.

3-314


Chapter 3 Alarms

3.5.7 198025862 Humidity is high

Alarm Information

Code: 198025862

Name: Humidity is high

Severity: Minor


Alarm Description

Humidity is high

Alarm Cause


2. Actual humidity in equipment room is too high.

Impact


2. If the alarm is caused by high room humidity, board may work abnormally and board services may

be interrupted.

Action

1. In NMS Configuration Management interface, click Power Board Alarm Parameters to view

the upper threshold of room humidity. If the configuration is unreasonable, please modify it. The

recommended value of upper threshold is 90.

2. Check the hygrometer in equipment room to see if the actual humidity is too high. If yes, take

necessary dehumidifying measures.

3.5.8 198025863 Humidity is low

Alarm Information

Code: 198025863

Name: Humidity is low

Severity: Minor


Alarm Description

Humidity is low

3-315



Alarm Cause


2. Actual humidity in equipment room is too low.


Impact


2. If the alarm is caused by low room humidity, board may work abnormally and board services may

be interrupted.

Action

1. In NMS Configuration Management interface, click Power Board Alarm Parameters to view

the lower threshold of room humidity. If the configuration is unreasonable, please modify it. The

recommended value of upper threshold is 90.

2. Check the hygrometer in equipment room to see if the actual humidity is too low. If yes, take

necessary humidifying measures.


3.5.9 198025864 Fault in fan plug-in box

Alarm Information

Code: 198025864

Name: Fault in fan plug-in box

Severity: Minor


Alarm Description

Fan works in error

Alarm Cause

1. The fan subrack is not tightly inserted into the rack.

2. The fan subrack has a hardware fault.


Impact

This alarm may cause very high rack temperature. As a result, the relevant board may work

abnormally and board services may be interrupted.

3-316


Chapter 3 Alarms

Action

1. Check whether the FAN subrack is tightly inserted into the rack. If no, unplug and plug it.

2. Replace the fan subrack.


3.5.10 198025865 Rack door alarm

Alarm Information

Code: 198025865

Name: Rack door alarm

Severity: Minor


Alarm Description

Alarm because of rack door open

Alarm Cause

1. The rack door is not closed.

2. The connection for door access control device is incorrect.


Impact

Services won't be affected, but there is a potential safety problem.

Action

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.


3.5.11 198025866 Smoke detected

Alarm Information

Code: 198025866

Name: Smoke detected

3-317



Severity: Minor


Alarm Description

Smoke detected

Alarm Cause

1. The alarm device is faulty.

2. The smoke density in equipment room is too high.


Impact

Services won't be affected, but there is a potential safety problem. Need to be handled immediately.

Action

1. Quick find the origin of smog.

2. If there is no smog in the equipment room, replace the smog detector.


3.5.12 198025867 Infrared alarm

Alarm Information

Code: 198025867

Name: Infrared alarm

Severity: Minor


Alarm Description

Infrared alarm

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


3-318


Chapter 3 Alarms

Impact

1. If the configuration of infra-red sensor is wrong, the system won't be affected.

2. If the infra-red light in the equipment room is over threshold, there is a potential safety problem.

Action

1. Does an animal or a person approach near the infrared sensor? If yes, remove the heat source. If

no, please check the configuration 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.


3.5.13 198025868 Lightning alarm

Alarm Information

Code: 198025868

Name: Lightning alarm

Severity: Minor


Alarm Description

Lightning alarm

Alarm Cause

1. Outdoor unit or equipment damaged by lightening


Impact

The board may work abnormally due to lightning stroke. Accordingly, board services will be

interrupted.

Action

1. Provide a reference manual and standard.

2. Provide a reference manual and standard and check grounding connection.

3. Provide a reference manual and standard and check lightning protection antenna.


3-319



3.5.14 198025869 Loss of DC power supply to rack

Alarm Information

Code: 198025869

Name: Loss of DC power supply to rack

Severity: Minor


Alarm Description

Atmosphere switch alarm

Alarm Cause

1. Circuit breaker has tripped.

2. No incoming DC supply from rectifier

Impact

This shelf can not be supplied with power. All boards on the shelf can not work and board services

are interrupted.

Action

Is this shelf needed?

1. If yes, ensure that the atmosphere switch is closed and ALM indicator is normal.

2. If no, screen the function of monitoring atmosphere switch. In NMS Configuration Management

interface, click Power Board Alarm Parameters; then set the status of atmosphere switch to be

screened.


3.5.15 198029184 SNTP server is unavailable

Alarm Information

l Alarm code: 198029184l Name: SNTP server is unavailablel Alarm severity: Minorl Alarm type: Environment alarm

Alarm Description

SNTP server is unavailable

3-320


Chapter 3 Alarms

Alarm Cause

SNTP server is faulty or communication broken.

Impact

NO impact to traffic only loss of Time synchronisation data for time stamp of events and reporting.

Action

1.Check whether the physical link is normal by using Ping command.

Y->Solve the physical link problem.

N->go to "2".

2.Check whether the server IP is correct.

Y->Configure the IP address.


3-321




3-322


Chapter 4NotificationsTable of Contents

198020291 Protocol stack process failed to initialize during power on ........................4-4198020802 Conflicting IP address in subnet...............................................................4-4198020803 Conflicting MAC address in subnet ..........................................................4-5198020804 Failed to generate static ARP from IP address.........................................4-6198020805 ARP detect failed .....................................................................................4-7198020806 ARP detect that the static ARP is not match.............................................4-8198018241 TCP Connection Aborted .........................................................................4-8198018242 MD5 Verification Failure...........................................................................4-9198018243 Wrong MD5 Message Abstract ..............................................................4-10198028993 SCTP Primary Path Set Failed...............................................................4-10198030016 Ethernet link OAM event ........................................................................4-11198000576 Loss of Frame on Trunk .........................................................................4-11198000834 MCC is faulty .........................................................................................4-12198001600 CPU resets on a board ..........................................................................4-13198008005 Memory file buffer overflow ....................................................................4-14198017216 Error in MCS Multi-Core processor receiving configuration data fromDBS .........................................................................................................................4-14198023106 Board self-check fails.............................................................................4-15198023107 The board initialization failure ................................................................4-16198023617 Configuration file is unusable .................................................................4-16198003138 Board FLASH faults ...............................................................................4-17198003394 Start daylight saving time.......................................................................4-18198003395 End daylight saving time ........................................................................4-18198025664 Abnormal Half-Fixed Connection Changes ............................................4-19198005441 Port status on internal media plane changed..........................................4-20198005448 485 seriel bus link between CLKG/PWRD and OMP is broken...............4-21198026176 Clock reference changed .......................................................................4-22198026177 CLKG reference quality changed ...........................................................4-22198026178 Clock work mode changed.....................................................................4-23198026179 Clock source invalidation reason changed .............................................4-23198005705 MCU resets abnormally .........................................................................4-24198005710 The result of manual reference selection for SETS chip .........................4-25198005711 Clock reference selection is being executed...........................................4-25198005712 The manual select base will be run, please wait for the result ................4-26198005713 APC chip's peripheral RAM has hardware fault ......................................4-27198005715 PP2S source switched ...........................................................................4-27198005718 Two master clock ports is directly connected..........................................4-28

4-1



198005700 DSP resets for abnormities ....................................................................4-28198005701 Version Load Error.................................................................................4-29198019777 APS switch over occurred ......................................................................4-30198005188 UIM CS Changeover..............................................................................4-31198005189 Notification of Active/Standby Changeover ...........................................4-32198005192 Board's Work Mode Unsupported ..........................................................4-33198005193 Notification of the power on status of the basic process .........................4-34198005956 Board Version Error ...............................................................................4-35198005958 IDE Version Files Synchronization Information.......................................4-35198005961 OMP Version Check Information ............................................................4-36198005962 Patch version operate fail.......................................................................4-37198011840 M3UA user office status change.............................................................4-38198013888 ASP status changed ..............................................................................4-38198013889 AS status changed.................................................................................4-39198013890 Sigtran error message received .............................................................4-40198013891 Sigtran notification message received....................................................4-41198013892 Allocate memory fail...............................................................................4-42198014144 Association establishment failed ............................................................4-42198014145 Association restart .................................................................................4-43198005195 Board mix plug occurred ........................................................................4-44198031040 ACL config failed....................................................................................4-45198105001 Failed to get the table of configuration ...................................................4-46198105002 The route table is overloaded.................................................................4-48198105003 Failed to handle DHCP message from other network .............................4-49198105004 Failed to operate multicast group ..........................................................4-50198105005 Clock difference of slave is large............................................................4-51198105006 Slave losted external clock.....................................................................4-52198105008 Bandwidth automatic adjustment is useless ...........................................4-53198105018 Unable to save Performance File ...........................................................4-54198105019 SLAVE memory check fail notification ....................................................4-55198105030 OMP received data is not complete........................................................4-56198105032 Transport Path Occupied BandWidth Overload ......................................4-57198105033 Transport Path group Occupied Bandwidth Overload.............................4-58198018755 HDLC status changed............................................................................4-59198021329 LSDB Overflow ......................................................................................4-60198021330 Configuration of OSPF mismatched .......................................................4-61198021331 Failed to add the ospf route to the courier routing table..........................4-61198028231 Router ID not configured for OSPFv3.....................................................4-62198028233 Configuration of OSPFv3 Mismatched ...................................................4-63198021837 Failure in adding dynamic routings.........................................................4-63198021059 RIP Neighbor Configuration Errors.........................................................4-64198021060 RIP Interface Authentication Errors ........................................................4-65198021065 Incompatible RIP Version Number .........................................................4-66198022598 Routers with Conflicting System Id Exist in Network...............................4-66198022599 ISIS Message Authentication Failure .....................................................4-67

4-2


Chapter 4 Notifications

198021584 Neighbor Hold Timer Expired .................................................................4-68198021585 BGP Interface Down and Neighbor Link Broken.....................................4-69198029760 DNS server inaccessible ........................................................................4-70198016193 SIG_IPI Forwards Service Messages Abnormally ..................................4-70198005702 Trunk configuration is inconsistent with function of board .......................4-71198005708 The active/standby modules of PSN clock have changed oversuccessfully..............................................................................................................4-72198005714 No external clock for DSP......................................................................4-72198005194 Changeover of CS Optical Interfaces .....................................................4-73198005960 Version Fails to Be Switched..................................................................4-74198087360 BCCH Exchange Fail .............................................................................4-74198087393 Ring state notification ............................................................................4-76198087394 Intelligent power up/down preparation notification ..................................4-76198087459 cell no gprs traffic inform........................................................................4-77198087469 abis route change inform .......................................................................4-77198087353 NSVC deletion notification .....................................................................4-78198087395 SNS Size process failure notification......................................................4-79198087396 SNS Config process failure notification ..................................................4-79198087466 NSVC's IP deletion notification...............................................................4-80198087359 No access of BSC to MSC SPC.............................................................4-81198087503 Baseband frequency hopping exchange for trx fail .................................4-81198087504 Baseband frequency hopping exchange for trx restore...........................4-82198087508 Block Successfully After Service released..............................................4-83198087751 dbsapp no avilable PCU resource inform ...............................................4-84198087754 Board back up ......................................................................................4-84198087760 BTS master power recover notification...................................................4-85198087761 BTS master power interruption notification.............................................4-86198087762 After BTS mains power failure TRX terminated notification ....................4-86198087772 Super Site Connect in ............................................................................4-87198087799 Cell intelligent power-on or power-down.................................................4-88198087514 TRAU frame sync loss notification .........................................................4-88198087515 BCCH Exchange Success .....................................................................4-89198087516 Mute call detect......................................................................................4-89198087519 Release dynamic association by force ...................................................4-90198087520 Gb interface throughput exceed permissible value .................................4-91198087338 TRX No Traffic .......................................................................................4-92198087434 Cannot detect up or down TRAU notification..........................................4-92198087339 BTS self maintenance inform .................................................................4-93198087477 site board cpu overload..........................................................................4-93198087478 uplink user layer jam inform ...................................................................4-94198087479 downlink user layer jam inform...............................................................4-95198087488 chp cycle adjust trau information............................................................4-95198087500 Radio Interface Synchronization ARF emendate Successfully ...............4-96198087501 Radio Interface Synchronization ARF emendate Failed .........................4-96198087502 Site IP Address conflicted ......................................................................4-97

4-3



198087512 IDS Attack detecting ..............................................................................4-98

4.1 198020291 Protocol stack process failed to initializeduring power on

Notification Information

Code: 198020291

Name: Protocol stack process failed to initialize during power on

Severity: Major


Notification Description

Protocol stack process failed to initialize during power on.

Notification Cause

Physical memory is insufficient.

Impact

RPU board will reboot automatically after 10 seconds.

Action

Ensure that the actual capacity of the physical memory is more than 1GB.

4.2 198020802 Conflicting IP address in subnetNotification Information

Code: 198020802

Name: Conflicting IP address in subnet

Severity: Minor



The Source IP in ARP packet is same with local IP address (include virtual address by ARP Proxy

4-4



Notification Cause

1. This network port is configured with the same IP address (including the virtual address in the same

network segment) as another host in the local network.

2. The peer-end switch that connects with this network port has a loop.

Impact

Board operation is normal. Communication network is faulty. All services on this port are down.

Action

When an IP address conflict occur, the NMS will display the conflicted IP address. Meanwhile, the

5-tuple information of the conflicted local port, as well as the conflicted MAC address of the external

device, can be detected.

1. Click Interface Configuration on the NMS Configuration interface to check the local interface

address. Modify the local interface address or the IP address of the conflicted external device.

Refer to the corresponding equipment maintenance manual to learn how to query the IP address of

external device.

2. The switch connected with the local port must have a loop if the following two conditions are

satisfied:

1) "20802 Conflicting IP Address" and "20803 Conflicting MAC Address in Subnet" concur;

2) Even though the local port IP address is changed, the two alarms still exist.

In this case, check whether there is a cable that connects both ports of the peer-end switch. If

yes, remove the cable.

4.3 198020803 Conflicting MAC address in subnetNotification Information

Code: 198020803

Name: Conflicting MAC address in subnet

Severity: Minor



The Source MAC in ARP packet is same with local MAC address.

Notification Cause

1. The MAC address of this port is the same with another MAC address in the direct connect network.

2. Loop exists in the remote switch connected with this port.

4-5



Impact

Board operation is normal. The notification leads to packet lookup failure in Layer 2 forwarding table.

Then packet loss occurs and all services related to this port will be down.

Action

When an MAC address conflict occurs, the NMS will display the conflicted MAC address. Meanwhile,

the 5-tuple information of the conflicted local port, as well as the conflicted MAC address of the

external device, can be detected.

1. Modify the MAC address of the local port or the conflicted MAC address of the external device.

Find the conflicted local port according to the displayed 5-tuple information. Click Interface

Configuration on the NMS Configuration interface and select "MAC Address" to check and modify

the MAC address of the local port.

Refer to the corresponding equipment maintenance manual to learn how to query the MAC address

of the external device.

2. The switch connected with the local port must have a loop if the following two conditions are

satisfied:

1) "20802 Conflicting IP Address" and "20803 Conflicting MAC Address in Subnet" concur;

2) Even though the local port IP is changed, the two alarms still exist.

In this case, check whether there is a cable that connects both ports of the peer-end switch. If

yes, remove the cable.

4.4 198020804 Failed to generate static ARP from IPaddress


Code: 198020804

Name: Failed to generate static ARP from IP address

Severity: Minor



Failed to generate static ARP from the newly added IP address,because the number of static ARPs

which generated by IP has reached the maximum.

Notification Cause

Failed to generate static ARP from the newly added IP address, because the number of static ARPs

which generated by IP has reached the maximum (each port up to 100).

4-6



Impact

The external device failed to communicate with the IP address from which no static ARP is generated.

Action

Delete some proxy addresses configured for virtual ports and re-configure IP address within the limit

of static ARPs.

4.5 198020805 ARP detect failedNotification Information

Code: 198020805

Name: ARP detect failed

Severity: Minor



ARP detect failed

Notification Cause

When the switch of the ARP detecting enabled, NE can send ARP request packet with the ARP's

IP periodically, if NE can not receive the ARP respond packet during the set time, NE will report

this alarm information.

Impact

The communication will be interrupted possibly.

Action

1. Please check the device's IP address configuration of the peer end, Please check the destination

IP address of the ARP request packet whether exist.

2. Please check physical link.

3. Please check the exchanger's VLAN configuration. The local port and the destination port must be

configured with the same VLAN ID.

4-7



4.6 198020806 ARP detect that the static ARP is notmatch


Code: 198020806

Name: ARP detect that the static ARP is not match

Severity: Minor



ARP detect that the static ARP is not match

Notification Cause

When the switch of the ARP detecting enabled, NE can send static ARP request packet with the static

ARP's IP periodically, if NE receives the ARP respond packet whose MAC or dot1q encapsulation is

not the same as static ARP's during the set time, NE will report this alarm information.

Impact

The communication will be interrupted possibly.

Action

1. Please check remote device's MAC address.

2. Please check the switch VLAN configuration. The local port and the destination port must be

configured with the same VLAN ID.

4.7 198018241 TCP Connection AbortedNotification Information

Code: 198018241

Name: TCP Connection Aborted

Severity: Major



TCP connection breaks down

4-8



Notification Cause

1. Network communication faults

2. The peer end shut down this TCP connection normally or abnormally.

3. Peer-end device faults.

Impact

The corresponding connection aborts.

Action

Check if there is severe packet loss in physical link (It can be checked by ping command), and

handle physical link faults.

4.8 198018242 MD5 Verification FailureNotification Information

Code: 198018242

Name: MD5 Verification Failure

Severity: Minor



No MD5 option in TCP packet head

Notification Cause

MD5 verification is not set for packets in application layer.

Impact

Application layer communication failure

Action

Check MD5 encrypted option of the two ends of application layer. If an end does not set with MD5

encrypted option, then set MD5 encrypted option for this end. The application layer protocol includes

BGP and LDP.

4-9



4.9 198018243 Wrong MD5 Message AbstractNotification Information

Code: 198018243

Name: Wrong MD5 Message Abstract

Severity: Minor



TCP packet have MD5 option, but wrong MD5 message abstract

Notification Cause

When application layer is receiving messages, MD5 cryptographic keys set on both ends are

inconsistent.

Impact

Application layer communication failure

Action

Set the same MD5 cryptographic keys for both ends of application layer. The application layer

protocol includes BGP and LDP.

4.10 198028993 SCTP Primary Path Set FailedNotification Information

Code: 198028993

Name: SCTP Primary Path Set Failed

Severity: Minor



Set Sctp primary path failed

Notification Cause

The remote IP of the SCTP primary path configured at application layer is not included in the local

address list of SCTP at opposite end

4-10



Impact

This notification informs user of the update failure of SCTP primary path. The primary path currently

in use is not affected. No impact on service.

Action

Check notification details on the NMS Alarm Management interface to find the SCTP ID and the

primary remote IP address.

To use the primary remote IP address as the primary SCTP path, perform the following steps:

1. Add the IP address as an interface address at the peer-end equipment.

2. Add the "primary remote IP address" to the "local SCTP IP address" list.

4.11 198030016 Ethernet link OAM eventNotification Information

Code: 198030016

Name: Ethernet link OAM event

Severity: Major



The number of wrong frames or wrong symbols exceeds the threshold

Notification Cause

The number of wrong frames or wrong symbols exceeds the threshold.

Impact

Ethernet links can not transmit data credibly.

Action

Check Ethernet link, receiver and transmitter of link.

4.12 198000576 Loss of Frame on TrunkNotification Information

Code: 198000576

4-11



Name: Loss of Frame on Trunk

Severity: Minor



Loss of frame on trunk

Notification Cause

Since frequency difference might exist between trunk line clock and local receive clock, the trunk

receive clock is not synchronous with the transmit clock.

Impact

Momentary fault occurs to trunk data service or signalling channel. If fault occurs repeatedly, CS/PS

service might become unstable. Otherwise, service is not affected.

Action

Check the clock synchronization status at both sides. If the status is unsynchronized, check if

LOL-related (loss of lock) alarm occurs in clock board. If yes, refer to the corresponding alarm

handling suggestion.

Related alarms:




4.13 198000834 MCC is faultyNotification Information

Code: 198000834

Name: MCC is faulty

Severity: Major



MCC is faulty

Notification Cause

MCC Hardware is faulty.

4-12



Impact

All MCC channels cannot transmit or receive data.

Action

1. Unplug the board for 5 seconds, and plug it again after a full discharge.


4.14 198001600 CPU resets on a boardNotification Information

Code: 198001600

Name: CPU resets on a board

Severity: Major



CPU resets on a board

Notification Cause

A CPU on a board at the shelf abnormally resets. The possible causes are:

1. User request CPU reset.

2. Board has reset itself due to fault.

Impact

The relevant services or communication links will be interrupted or disconnected. This alarm will be

recovered after the board is powered on normally.

Action

1. Check the NMS operation log to see whether there is a manual reset record. If yes, no handling is

necessary.


4-13



4.15 198008005 Memory file buffer overflowNotification Information

Code: 198008005

Name: Memory file buffer overflow

Severity: Minor



Memory file buffer overflow

Notification Cause

The transferred data records exceed the maximum capacity of the table, and the capacity of the

receiver memory file buffer is insufficient.

Impact

If the board is powering on, the excessive data records (beyond table capacity) are discarded.

Action

Delete the excessive data records of the false table.

4.16 198017216 Error in MCS Multi-Core processorreceiving configuration data from DBS


Code: 198017216

Name: Error in MCS Multi-Core processor receiving configuration data from DBS

Severity: Major



1. The configuration data from OAM to RNC is abnormal (the configuration data from DBS are

abnormal).

2. Failure in adding a vital data table.

4-14



Notification Cause

1. The configuration data from DBS are exceptional.

2. Failure in adding a vital data table.

Impact

It may cause packet forwarding problem since some vital data table is absent.

Action

Check the data configuration, if there is a configuring error, correct it and reboot the board.

4.17 198023106 Board self-check failsNotification Information

Code: 198023106

Name: Board self-check fails

Severity: Minor



Board self-check fails

Notification Cause

Board hardware is faulty.

Impact

The board fails to power on possibly, and the service or communication link related to this board is

down.

Action

Replace the board.

4-15



4.18 198023107 The board initialization failureNotification Information

Code: 198023107

Name: The board initialization failure

Severity: Minor



The board initialization failure

Notification Cause


Impact

The board fails to be powered on. As a result, UE can not be accessed and existing services are

interrupted.

Action

Replace the board.

4.19 198023617 Configuration file is unusableNotification Information

Code: 198023617

Name: Configuration file is unusable

Severity: Major



The file which is used for restoring protocol configuration data is unusable.

Notification Cause

During the process of system power on, the DAT file obtained from VMM is unusable or the TXT

file which saves configuration data is unusable.

4-16



Impact

1. DAT file is unusable

This error will make the saved data unrestorable and unconfigurable if the configured data was

saved in TXT file.

2. TXT file is unusable

This error will make the saved data unrestorable.

Action

On NMS fault management interface, view the alarm details, which give the Additional Reason.

1. If it's the DAT file error, then we need to reload the file from VMM and switch to the new file.

2. If it's the TXT file error, then take the following step:

1)Get the TXT file from ""/DOC0/DATA1"" directory at RPU with File Manager method.

2)Open the TXT file and delete line ""[CRC_DATFILE]="" and ""[CRC_TXTFILE]="".

3)Transmit the modified TXT file.

4)Reboot RPU.

4.20 198003138 Board FLASH faultsNotification Information

Code: 198003138

Name: Board FLASH faults

Severity: Major



FLASH device initialization failed

Notification Cause

The flash on the board is damaged.

Impact

1. If the fault flash is on OMP board, the OMP board will fail to be powered on. If both master/slave

OMP boards have the flash fault, the entire system can not start up.

2. If the fault flash is on other board, the board can be powered on normally and there is no impact

on services.

4-17



Action

Replace the board.

4.21 198003394 Start daylight saving timeNotification Information

Code: 198003394

Name: Start daylight saving time

Severity: Minor



System start daylight saving time

Notification Cause

Daylight saving time activated, clock changed accordingly.

Impact

No impact

Action


4.22 198003395 End daylight saving timeNotification Information

Code: 198003395

Name: End daylight saving time

Severity: Minor



System end daylight saving time

4-18



Notification Cause

Daylight saving time is de-activated and the system is back to normal country clock.

Impact

No impact

Action


4.23 198025664 Abnormal Half-Fixed ConnectionChanges


Code: 198025664

Name: Abnormal Half-Fixed Connection Changes

Severity: Major



Half-fixed connection is changed abnormally

Notification Cause

1. Abnormal jitter occurs to the line clock of the shelf where the board is located.


Impact

TMD channel is interrupted momentarily, which may have a slight impact on services.

4-19



Action

1.Check alarms and notifications to see if the alarm(s)/notification(s) related to input clock

exist(s).Related alarm(s) and notification(s) are listed below.

198026116 CLKG PP2S Output Clock Lost




198026133 Clock Output Loss

2.Replace the faulty board.

4.24 198005441 Port status on internal media planechanged


Code: 198005441

Name: Port status on internal media plane changed

Severity: Minor



The status of the cascading port of the inter-media plane changed

Notification Cause

1. The connection between UIM/GUIM/GUIM2 and GLI is faulty.


Impact

The impact varies according to port status.

1. If the port status is "Master port invalid status" or "Master port abnormal", the master port fails to

forward inner media stream, and the services carried via the master port will be switched to the slave

port. If the slave port is also unavailable, services carried over the port will be interrupted.

2. If the port status is "Slave port invalid status" or "Slave port abnormal", services will not be affected.

However, the potential risk exists during master/slave changeover.

3. If the port status is others, services will not be affected.

4-20



Action

Alarm details are displayed in NMS Alarm Management interface, where port status is given.

1. If the port status is "Master port invalid status" or "Master port abnormal", please solve the problem

according to the following handling suggestions.

i. Reconnect the cable between UIM/GUIM/GUIM2 and GLI.

ii. Replace the optical module or cable used for the connection between UIM/GUIM/GUIM2 and GLI.

iii. Replace the UIM/GUIM/GUIM2 board.

iv. Replace the GLI board.

2. If the port status is others, no handling is necessary.

4.25 198005448 485 seriel bus link betweenCLKG/PWRD and OMP is broken


Code: 198005448

Name: 485 seriel bus link between CLKG/PWRD and OMP is broken

Severity: Minor



485 offline set fail

Notification Cause

1. 485 communication is interrupted.

2. The board is abnormal.

Impact

The configured clock reference/environment threshold fails to take into effect. There is no impact

on services.

Action

1. Unplug and plug the 485 cable.

2. Replace the 485 cable.

3. Replace clock CLKG or environmental monitoring PWRD /fiber access TFI board

4-21



4.26 198026176 Clock reference changedNotification Information

Code: 198026176

Name: Clock reference changed

Severity: Minor



Clock base changed

Notification Cause

The currently locked clock reference has changed.

Impact


Action

No need to handle.

4.27 198026177 CLKG reference quality changedNotification Information

Code: 198026177

Name: CLKG reference quality changed

Severity: Minor



CLKG frequence base quality changed

Notification Cause

Clock quality of the CLKG board has changed.

4-22



Impact

The system may not get the needed clock.

Action

Check the quality of external clock source.

4.28 198026178 Clock work mode changedNotification Information

Code: 198026178

Name: Clock work mode changed

Severity: Minor



CLKG work mode changed

Notification Cause

The clock work mode of the CLKG board has changed.

Impact

The system may not get the needed clock.

Action

No need to handle.

4.29 198026179 Clock source invalidation reasonchanged


Code: 198026179

Name: Clock source invalidation reason changed

Severity: Minor

4-23





Base invalid reason changed

Notification Cause

The clock reference becomes invalid.

Impact


Action

No need to handle.

4.30 198005705 MCU resets abnormallyNotification Information

Code: 198005705

Name: MCU resets abnormally

Severity: Major



Error occurs during MCU running

Notification Cause

MCU Hardware is faulty.

Impact

CLKG_2 board is faulty.

Action

Replace the alarm board.

4-24



4.31 198005710 The result of manual referenceselection for SETS chip


Code: 198005710

Name: The result of manual reference selection for SETS chip

Severity: Minor



Prompts the subscriber to select the result of the benchmark manually

Notification Cause

After manual base switchover, man-machine command, or pressing panel button, clock board

performs base locking operation (at most for 2 minutes). This notification is to inform the user of

the operation result of manual base selection.

Impact


Action


4.32 198005711 Clock reference selection is beingexecuted


Code: 198005711

Name: Clock reference selection is being executed

Severity: Minor



If the last benchmark selection operation is being done and the corresponding result is not given, this

current benchmark selection operation will be cancelled and the corresponding notice will be reported

4-25



Notification Cause

If previous operation about clock reference selection doesn't finish and relevant result is not given

yet, the system will screen any new attempt to manually select clock reference. And in this case,

this notification is declared.

Impact


Action


4.33 198005712 The manual select base will be run,please wait for the result


Code: 198005712

Name: The manual select base will be run, please wait for the result

Severity: Minor



When the reference is selected with panel keys, the background sends this message to notify the

user that the command is being executed and ask the user to wait for the execution result

Notification Cause

The notification is declared after selecting base via panel button, to remind user that the base

selection is in process and to request user to wait for the operation result.

Impact


Action


4-26



4.34 198005713 APC chip's peripheral RAM hashardware fault


Code: 198005713

Name: APC chip's peripheral RAM has hardware fault

Severity: Major



The chip MTAPC64013E's RAM occur hardware error

Notification Cause


Impact

The alarm board can not be used. ATM cell fails to be forwarded, and all board services are

interrupted.

Action

Replace the alarm board.

4.35 198005715 PP2S source switchedNotification Information

Code: 198005715

Name: PP2S source switched

Severity: Minor



PP2S source switched

Notification Cause

PP2S (Pulse Per 2 Seconds) source is switched at both system clock and GPS receiver sides.

4-27



Impact


Action

GPS side PP2S has a higher priority. If PP2S is switched over from GPS-side to system-side, check

the GPS receiver and antenna feed status.

4.36 198005718 Two master clock ports is directlyconnected


Code: 198005718

Name: Two master clock ports is directly connected

Severity: Minor



The network port connected with a master clock port in this board is a master clock port too

Notification Cause

Two ports which are configured as synchronous Ethernet master clock port are directly connected.

Impact

If network connecting is normal, then there is no impact; if it is network connecting mistake, then the

port can not synchronize to the connected master clock port.

Action

If network connecting is normal, there is no need to handle; if it is network connecting mistake, there

is need to reconfigure the clock port or reconnect the port.

4.37 198005700 DSP resets for abnormitiesNotification Information

Code: 198005700

4-28



Name: DSP resets for abnormities

Severity: Major



DSP error

Notification Cause

1. DSP chip on the board that has alarm is faulty.

2. Board is faulty.

Impact

DSP is unavailable during reset, but will be restored to normal state after reset. During reset, cells on

the DSP are out of service, services on the DSP are interrupted, and call loss increases.

Action

DSP resets automatically and abnormally.

1. If power-on is normal(the board has no alarm code 5399) after DSP reset, the board can be

restored to normal state.

2. If DSP resets repeatedly, replace the board or sub-card.

4.38 198005701 Version Load ErrorNotification Information

Code: 198005701

Name: Version Load Error

Severity: Major



Version Load Error

Notification Cause

The equipment is abnormal in the process of version loading, which falls into three cases.

1. The equipment fails to fetch the needed version.

2. Version loading to chip fails.

3. Chip hardware is faulty.

4-29



Impact

1. Microcode version loading fails, leading to repeated board reset and interruption of board services.

2. Firmware/single-chip computer version loading fails, leading to abnormal board operation and

interruption of board services.

3. DSP version loading fails. Cells on the DSP will be out of service. Services on the DSP are

interrupted, and the number of call loss increases.

Action

On NMS fault management interface, view notification Details where "Loading corresponding alarm

information" is given. Locate the corresponding handling suggestion based on the given information.

1. Any of the following items displayed by "Loading corresponding alarm information" indicates that

the chip fails to obtain the needed version. On NMS software management interface, check the

configured version for the chip and version status. Ensure that the needed version is configured for

the chip and the version is actived. If the version is not actived, please active the version by the OMC

i. DSP6416 No.d : No Version Information

ii.DSP5402 No.d : No Version Information

iii. MC fail to get version information

iv. OCT6100 fail to get version information

v. M82620 : Index = d fail to get version information

2. If information other than the items listed above appears, refer to the following handling suggestion.

i. Reset board.

ii. Replace DSP sub-card.

iii. Replace board.

4.39 198019777 APS switch over occurredNotification Information

Code: 198019777

Name: APS switch over occurred

Severity: Minor



APS switch over occurred

4-30



Notification Cause

1. Optical interface is faulty.

2. In inter-board backup mode, the board gets fault.

3. Changeover operation is initiated by the opposite end.

4. In recovery mode, fault recovery time at optical interface exceeds 5 minutes.

5. APS changeover request/clearance is initiated by NMS.

Impact

During APS changeover process, the link is interrupted for 10 ~ 50 ms. Few packets may be lost, but

services won't be affected.

Action

View operation & maintenance log to see whether there is a record, indicating an operator manually

initiates APS changeover request/clearance. If yes, no handling is necessary. If no, check whether

there is one of the following alarms. If yes, please solve the problem according to corresponding

handling suggestions.

Related alarms:

198001792 SDH/SONET fault

198005396 Exceptional Internal Media Plane Communication

198005378 Board HW Error

198005635 The board is not plugged firmly.

4.40 198005188 UIM CS ChangeoverNotification Information

Code: 198005188

Name: UIM CS Changeover

Severity: Minor



UIM CS domain switchover

4-31



Notification Cause

1. Optical module signal loss occurs.

2. Board input clock loss occurs.

3. Bit error rate at the optical interface is high.

4. Lock loss occurs to the phase-locked loop.

5. Bit error rate on the master/slave interconnecting link of GUIM/GUIM2 board is high.

Impact

There is no impact on services.

Action

Check if the following alarm occurs in local/opposite board. If yes, refer to the corresponding alarm


Related alarms:

198001286 Loss of input clock

198005639 High Error Rate of Optical Interface

198005646 Phase-locked Loop Unlocked

4.41 198005189 Notification of Active/StandbyChangeover


Code: 198005189

Name: Notification of Active/Standby Changeover

Severity: Minor



M/S switchover occurs on the board

Notification Cause

It is hardware system fault. The CS domain of the UIM switches over due to artificial operation.

Impact

The board whose changeover fails will reset automatically.

4-32



Action

1. Analyze the switchover reason according to the additional information about the alarm .If it is not

because of the system fault but due to control of MML command at the background or caused

by non-active/standby changeover, or the standby board does not exist physically, nothing would

be done for this alarm.

2. If it is because of the system fault, eliminate those alarms firstly.

4.42 198005192 Board's Work Mode UnsupportedNotification Information

Code: 198005192

Name: Board's Work Mode Unsupported

Severity: Minor



The board working mode is not supported

Notification Cause

1. The work mode that the board does not support is configured on the background.

2. Such reasons as FPGA not loading cause that there are errors in setting the working mode for

the board.

Impact

Board master/slave backup function is disabled.

Action

1. Check the configuration of board backup mode. If the configured backup mode is not supported by

the board, modify configuration or replace the board with one that supports such configuration.

2. Unplug and plug board. Reload FPGA version.

4-33



4.43 198005193 Notification of the power on status ofthe basic process


Code: 198005193

Name: Notification of the power on status of the basic process

Severity: Minor



The basic process power on notification

Notification Cause

1. Board power-on is successful.

2. Board power-on fails or expires.

Impact

If it indicates successful powered-on operation, services will not be affected.

If it indicates failure powered-on operation, the services on the board will be unavailable.

Action

Alarm details are displayed in NMS Alarm Management interface, where powered-on status (“Board

poweron successful/failed/timeout”) is given. You can easily find handling suggestions according to

the powered-on status.

The handling suggestions for each status are described as below.

1. Powered on successful


2. Powered-on timeout

Ensure that the board loads a proper version. The boards on a network element must use the

same version.

3. Powered-on failed

Ensure that the board loads a proper version. The boards on a network element must use the

same version.

4-34



4.44 198005956 Board Version ErrorNotification Information

Code: 198005956

Name: Board Version Error

Severity: Minor



Periphery board request version info error or download / load version file error

Notification Cause

1. A board is in the slot which is not configured with any board.

2. Board version is unconfigured.

3. Board version has been configured, but version file does not exist or is damaged.

Impact

The board fails to obtain version, leading to abnormal board operation and access failure of board

services.

Action

1. On NMS configuration management interface (rack), view rack layout. Make sure that the board

configured is the same with the board plugged in the slot.

2. According to board type information in detailed notification, add and reload the right version.

4.45 198005958 IDE Version Files SynchronizationInformation


Code: 198005958

Name: IDE Version Files Synchronization Information

Severity: Minor


4-35




IDE files synchronization information

Notification Cause

Synchronization of master/slave OMP version files occurs.

Impact

1. IDE version file synchronization occurs between master and slave OMP (ROMB board). Service

will not be affected by synchronization result.

2. In the case of synchronization failure, partial loss of version file will occur to slave OMP

Action

On NMS fault management interface, view notification Details where "Synchronization information" is

given.

1. If synchronization information is "Failed to obtain file record during synchronization" or

"Synchronization failed", find the name of the version file in notification Details. According to the given

file name, locate on NMS software management interface the corresponding version configuration in

the version file database. Reload the version file to RNC NE. Delete the version file if it is not in use.

2. If synchronization information is others, no handling is necessary.

4.46 198005961 OMP Version Check InformationNotification Information

Code: 198005961

Name: OMP Version Check Information

Severity: Minor



The version file recorded in DB is not exist or ompcfg.inf is lost.

Notification Cause

The version file in software version configuration does not exist in RNC NE.

4-36



Impact

1. If the non-existent version file is not in use, service will not be affected.

2. If the non-existent version file is the activated version, the corresponding board will fail to fetch

version during powering-on, leading to service access failure.

Action

On NMS fault management interface, view notification Details where "Version file name" is given.

According to the given file name, locate on NMS software management interface the corresponding

version configuration in the version file database. Reload the version file to RNC NE.

4.47 198005962 Patch version operate failNotification Information

Code: 198005962

Name: Patch version operate fail

Severity: Minor



Patch version operate fail

Notification Cause

1. Patch version file and CPU version file do not match.

2. Patch version file does not exist in RNC NE.

3. The patch version file related to the patch does not exist in RNC NE.

Impact

Patch version activation fails. New functions of the patch version are unavailable. No impact on

service.

Action

1. If the patch version is not needed, delete the corresponding version configuration on NMS software

management interface.

2. If the patch version is needed, locate on NMS software management interface the version

configuration of patch version file and related patch version file in the version file database. Reload

the version files to RNC NE.

4-37



4.48 198011840 M3UA user office status changeNotification Information

Code: 198011840

Name: M3UA user office status change

Severity: Major



M3UA user office status change

Notification Cause

1. User configuration of this office is changed.

2. Bottom-layer links are unavailable.

3. The signaling network management message from opposite end is received.

Impact

If M3UA user office status changes from accessible to inaccessible, reception and sending of

messages from/to the office fail. Access of new services under the office fails, and abnormal release

of the ongoing service occurs.

If M3UA user office status changes from inaccessible to accessible, the system will return to normal

state.

Action

1. Check whether link interruption alarm occurs to the link/association. If yes, refer to the

corresponding alarm handling suggestion.

Related alarms:

198066011 MTP3 link unavailable


2. On NMS configuration management interface, check if the M3UA user is configured in the relevant

office. If no, add the configuration.

3. Locate the cause for office status change at opposite end.

4.49 198013888 ASP status changedNotification Information

Code: 198013888

4-38



Name: ASP status changed

Severity: Minor



Inform of the change of ASP status

Notification Cause

1. Association status is changed.

2. ASP operation is performed at opposite end.

3. ASP operation is performed in dynamic data management at local end.

Impact

If both "ASP status changed" notification and "8400384 M3UA office inaccessible" alarm occur at the

same time, new services can not be accessed to the office and existing services will be interrupted

abnormally.

If merely this notification is reported, services will not be affected.

Action

1. Check whether association interruption alarm occurs. If yes, refer to the corresponding alarm



2. Activate the ASP in dynamic data management.

3. Check whether ASP operation is performed at the opposite end.

4.50 198013889 AS status changedNotification Information

Code: 198013889

Name: AS status changed

Severity: Minor



Inform of the change of AS status

4-39



Notification Cause

1. Association status is changed.

2. ASP operation is performed at opposite end.

3. ASP operation is performed in dynamic data management at local end.

Impact

If both "AS status changed" notification and "8400384 M3UA office inaccessible" alarm occur at the

same time, new services can not be accessed to the office and existing services will be interrupted

abnormally.

If merely this notification is reported, services will not be affected.

Action

1. Check whether association interruption alarm occurs. If yes, refer to the corresponding alarm



2. Activate ASP under the AS in dynamic data management.


4.51 198013890 Sigtran error message receivedNotification Information

Code: 198013890

Name: Sigtran error message received

Severity: Minor



Sigtran error message received

Notification Cause

1. AS configuration is wrong.

2. Protocol versions used at both sides are different.

Impact

The corresponding AS fails to be activated, causing M3UA office inaccessible. UE fails to

receive/transmit messages from/to the relevant office. New services can not be accessed to this office.

4-40



Action

1. Check AS configuration to see whether the configured traffic mode at both sides are consistent. If

no, modify configuration to keep consistency.

2. APP server AS ID configuration must meet the following requirements. If ASP is configured for

local end, SGP should be configured for Opposite end. Vice versa. If IPSP client is configured for

local end, IPSP server should be configured for opposite end. Vice Versa.

3. Activate the ASP in dynamic data management.

4. On NMS configuration management interface (AS configuration), check if routing context and

routing context ID are configured. Ensure that the routing contexts configured at both ends are

the same.

5. On NMS configuration management interface, check whether the local ASP in service for AS is

configured. If no, add the configuration.

6. Check the protocol versions used at both sides. Ensure that the protocol versions are the same.

4.52 198013891 Sigtran notification message receivedNotification Information

Code: 198013891

Name: Sigtran notification message received

Severity: Minor



Sigtran notification message received

Notification Cause

1. Because association links are interrupted, the number of activated ASPs, associated to the serving

AS, is insufficient.

2. ASP is released in Dynamic Data Management so that the number of ASPs, associated to the

serving AS, is insufficient.

Impact

The number of ASPs associated to the serving AS is insufficient. If traffic is heavy, congestion or

packet loss may occur, leading to loss of calls and decreased PS call access rate. However, if

traffic is not heavy, services will not be affected.

4-41



Action

1. On NMS configuration management interface (AS configuration), query ASP-related associations.

Check whether interruption alarm occurs in the association(s). If yes, refer to the corresponding

alarm handling suggestion.


2. Reactivate ASP in dynamic data management.


4.53 198013892 Allocate memory failNotification Information

Code: 198013892

Name: Allocate memory fail

Severity: Minor



Allocate memory fail

Notification Cause

Memory is insufficient, that result in dynamic memory allocation failure when the processor is

powered on.

Impact

If Application Server/Application Server Process is not configured on this board, system will not

be affected. Or else process will be unstable.

Action

1. Need to enlarge memory capacity of the alarming board and then restart the board.

2. If Application Server/Application Server Process is not configured on this board, then the alarm

should be ignored.

4.54 198014144 Association establishment failedNotification Information

Code: 198014144

4-42



Name: Association establishment failed

Severity: Major



Association establishment failed

Notification Cause

1. Association configuration at both ends is inconsistent.

2. The same local address and port are configured for more than one association, but they adopt

different protocol types.

3. The IP address of interface board is faulty or the physical link is broken.

Impact

If several association links are available to the destination office, services will not be affected. In

the case of heavy traffic, link congestion may occur, leading to loss of calls and decreased PS

call access rate.

If merely one association link is available to the destination office, the office may become inaccessible.


to this office.

Action

1. On NMS configuration management interface, check association configuration at local end and

opposite end. Checking items include local IP address, local port No., remote IP address, remote port

No., and application property of SCTP association. If the association at local end is configured as

client, the association at opposite end should be configured as server. Vice Versa.

2. At local end, check whether the associations configured with different protocol types have the

same local IP address and local port No.. If yes, perform configuration modification to differentiate the

local IP address and local port No. of these associations.

3. Check protocol stack configuration at both ends to see if interface board addresses are in the same

network segment. If no, modify configuration to put two addresses in the same network segment.

4. Ping the opposite-end interface board address to see if the network cable or other intermediate link

is faulty. Replace the cable if ping fails.

4.55 198014145 Association restartNotification Information

Code: 198014145

4-43



Name: Association restart

Severity: Minor



The peer end originated link reestablishment, and the association restarted.

Notification Cause

The local end receives a link setup request but actually it doesn't detect a broken link. This causes

association restarts. Probable reasons are:

1. Relevant board at opposite end resets.

2. An association link is re-established at opposite end.

Impact

No impact.

Action

No handling is necessary,wait association to restart

4.56 198005195 Board mix plug occurredNotification Information

Code: 198005195

Name: Board mix plug occurred

Severity: Minor



The PCB ID, BOM ID or physical board type is inconsistent between master board and slave board.

Notification Cause

1. The PCB ID is inconsistent between master board and slave board.

2. The BOM ID is inconsistent between master board and slave board.

3. The physical board type is inconsistent between master board and slave board.

4-44



Impact

Not support to mix plug into shelf, the board can't work normally.

Action

Depend on PCB ID, BOM ID and physical board type of the self board and the mate board according

to the additional information about the inform, inquire "Board mix plug test conclusion.xls" and check

the two boards can mix plug into shelf? If yes ignore it, if not use the same PCB ID, BOM ID and

physical boar type please.

4.57 198031040 ACL config failedNotification Information

Code: 198031040

Name: ACL config failed

Severity: Minor



ACL config failed

Notification Cause

BRS protocol processes ACL configuration data which synchronized by DBS from ACL offline

configuration failed.

Impact

The ACL configuration data will not take effect.

Action

1. Check the ACL configuration type and error information from alarm inform.

2. Correct the ACL offline configuration data base on alarm inform.

3. Synchronize the ACL offline configuration data.

4-45



4.58 198105001 Failed to get the table of configurationNotification Information

Code: 198105001

Name: Failed to get the table of configuration

Severity: Minor



The board fails to obtain the database configuration from itself or the OMP.

Notification Cause

l The database table configuration is incomplete or wrong.

l The channel over which the control-plane data is transmitted is not operating properly.

Impact

The effect on the system varies with the alarm cause. Detailed information is as follows:

l Failing to obtain the IP segment reassemble board information.

This information is used to process the external fragmented IP packets arriving at the device.

If the information is missing, the processing of fragmented IP packets may fail, causing the

interruption of services or a decline of the service processing rate.

l Failing to obtain the OMCB server configuration.

If the configuration is missing, the OMCB function may fail to be used.

l Failing to obtain the signaling distribution table.

If the information is missing, the SCTP data may fail to be transmitted on the interface board,

and related services operating on the board are interrupted.

l Failing to obtain the IP/UDP distribution table.

If the information is missing, the processing of the IUPS service or the IP transport-based data

may fail.

l Failing to obtain the layer-2 forwarding table.

If the information is missing, the internal communication of the device is not operating properly,

causing the interruption of all services operating on the board.

l Failing to obtain the path configuration table.

For the ATM interface board, if the information is missing, the processing of the AAL2-based data

may fail, causing the interruption of the IUB, IUCS, and IUR services belonging to the office.

For the IP interface board, the traffic control on IP packets may fail, causing the interruption of

all services belonging to the office.

l Failing to obtain the path group configuration table.

For the ATM interface board, if the information is missing, the processing of the AAL2-based data

may fail, causing the interruption of IUB, IUCS, and IUR services belonging to the office. For the

IP interface board, there is no impact on services.

4-46



Action

1. Re-execute synchronize all data, and check whether the notification persists.

Yes -> Step 2.

No -> End.

2. Check whether the following parameters are set as required in accordance with "Table name" in

the notification information.

IpUdpTbl: "Slave Sunit(UpSlaveSunit)"

PathGrpTbl: "Transmission Path Group(TrPathGroup)"

PathTbl:

l UMTS: "Iub Transmission Path(UIubTrPath)", "MGW Transmission Path(UMgwTrPath)",

"Iups Transmission Path(UIupsTrPath)", "Iur Transmission Path(UIurTrPath)", and "Iurg

Transmission Path(UIurgTrPath)"

l TD: "Iub Transmission Path(TIubTrPath)", "MGW Transmission Path(TMgwTrPath)",

"Iups Transmission Path(TIupsTrPath)", "Iur Transmission Path(TIurTrPath)", and "Iurg

Transmission Path(TIurgTrPath)"

l GSM: "Abis Transmission Path(GAbisTrPath)", "A Transmission Path(GATrPath)", "Gb

Transmission Path(GGbTrPath)", "Ater Transmission Path(GAterTrPath)", and "Iurg

Transmission Path(GIurgTrPath)"

PathCirTbl:

l UMTS: "CIR of Iub Transmission Path(UIubTrPathCir)", "CIR of MGW Transmission

Path(UMgwTrPathCir)", "CIR of Iups Transmission Path(UIupsTrPathCir)", "CIR of Iur

Transmission Path(UIurTrPathCir)", and "CIR of Iurg Transmission Path(UIurgTrPathCir)"

l GSM: "CIR of Abis Transmission Path(GAbisTrPathCir)", "CIR of A Transmission

Path(GATrPathCir)", "CIR of Gb Transmission Path(GGbTrPathCir)", "CIR of Ater

Transmission Path(GAterTrPathCir)", and "CIR of Iurg Transmission Path(GIurgTrPathCir)"

l TD: "CIR of Iub Transmission Path(TIubTrPathCir)", "CIR of MGW Transmission

Path(TMgwTrPathCir)", "CIR of Iups Transmission Path(TIupsTrPathCir)", "CIR of Iur

Transmission Path(TIurTrPathCir)", and "CIR of Iurg Transmission Path(TIurgTrPathCir)"

IntfIpAddrTbl: check "Ethernet IP Interface(EthIpIntf)", "Ethernet IP Sub Interface(EthIpSubIntf)",

"Ethernet Channel IP Sub Interface(EthChIpSubIntf)", "Ethernet Channel IP

Interface(EthChIpIntf)", "IP Interface of ML-PPP Group(MlpppTpIpIntf)", "IP Interface of PPP

Link(PppIpIntf)", "Super Vlan IP Interface(EthSuperIpIntf)", "IPOA IP Configuration(IpoaTp)",

"Loopback IP Interface(LbIpIntf)", and "Virtual IP Interface(VIpIntf)".

ReassBrdTbl: Check "IP Configuration(Ip)". "IP Segment ReAssemble Default Unit(ref1Unit)" and

"IP Configuration(Ip)". "IP Segment ReAssemble Units(ref2Unit[])".

DhcpRoleTbl: check "DHCP Server(DhcpServer)" and "DHCP Relay(DhcpRelay)".

DataMuxTbl: check "IP Configuration(Ip)". "DeMux Port of RTP MUX (IuDeMuxUdpPort)" and "IP

Configuration(Ip)". "DeMux Port of UDP/RTP MUX (IubDeMuxUdpPort)".

SctpCfgTbl: check "Association(SctpAssociation)".

OmcbCfgTbl: check "Operation Maintenance Configuration(OmCon)".

InnerOmcbCliIp:

l UMTS: "Iub Link(UIubLink)". "OMCB Inner Service IPv4 Address(InnerOmcbCliIPv4)".

l TD: "Iub Link(TIubLink)". "OMCB Inner Service IPv4 Address(InnerOmcbCliIPv4)".

l GSM: "Abis Office(GAbisLink)". "OMCB Inner Service IPv4 Address(InnerOmcbCliIPv4)"

4-47



OmcbMultiPath:

l UMTS: "Omcb Path(UOmcbPath)"

l TD: "Omcb Path(TOmcbPath)"

l GSM: "Omcb Path(GOmcbPath)"

UdpUnitTbl: "UDP Port Configuration(UDPPORTNUM)"

PtpTbl: "PTP Interface Configuration(PtpPort)"

DhcpRelayTbl: "DHCP Relay(DhcpRelay)".

Yes -> Step 4.

No -> Step 3.

3. Modify the configuration as required, and check whether the notification persists.

Yes -> Step 4.

No -> End.


4.59 198105002 The route table is overloadedNotification Information

Code: 198105002

Name: The route table is overloaded

Severity: Minor



The total number of routing entries that the user-plane board detects exceeds 90 percent of the

maximum number of routing entries that the board supports.

Notification Cause

Too many route entries are configured, reaching 90 percent of the upperlimit of the routing table (the

maximum number of routing entries that the VTCD board supports is 360, and the maximum number

of routing entries that the VTCD-2 board supports is 4096).

4-48



Impact

l If the total number of routing entries does not exceed the maximum capacity of the routing table

on the user-plane processing board, services are not affected.

l If the total number of routing entries exceeds the maximum capacity of the routing table on the

user-plane processing board, some routing entries are lost.

à If the lost route is the route from the RNC/BSC to Node B/BTS or to the CN, user services

may fail to be connected to the board.

à If the lost route is destined to the peer RNC NE, the cross-RNC user services cannot be

connected to the board.

à The SLA diagnostic test between the RNC and other NEs fails to be executed.

Action

1. Check whether the following configuration is in accordance with actual requirements:

Routing table: "Static Route(StaticRoute)"

Interface table:

l "Ethernet IP Interface(EthIpIntf)"

l "Ethernet IP Sub Interface(EthIpSubIntf)"

l "Ethernet Channel IP Sub Interface(EthChIpSubIntf)"

l "Ethernet Channel IP Interface(EthChIpIntf)"

l "IP Interface of ML-PPP Group(MlpppTpIpIntf)"

l "IP Interface of PPP Link(PppIpIntf)"

l "Super Vlan IP Interface(EthSuperIpIntf)"

l "IPOA IP Configuration(IpoaTp)"

l "Loopback IP Interface(LbIpIntf)"

l "Virtual IP Interface(VIpIntf)"

Yes -> Step 3.

No -> Step 2.

2. Modify the configuration as required. Wait for five minutes, and check whether the notification

is cleared.

Yes -> End.

No -> Step 3.

3. Contact the next level of maintenance support (it is recommended to re-plan routes and the

network topology).

4.60 198105003 Failed to handle DHCP message fromother network


Code: 198105003

4-49



Name: Failed to handle DHCP message from other network

Severity: Minor



The DHCP server board fails to process a DHCP message.

Notification Cause

l The peer IP address of the PPP link is not configured.

l The operation and maintenance IP address of the RNC for the Node B is not configured.

l The DHCP client configuration fails to be obtained.

l An error DHCP message is received.

Impact

The DHCP client fails to obtain the IP address.

Action

1. Open the rack diagram, and identify the board type (interface board or non-interface board) in

accordance with the physical address in the notification information. Check whether the following

configuration is in accordance with actual requirements.

l non-interface board parameters

"DHCP Client(DhcpClient)"

l interface board parameters

à "IP Interface of ML-PPP Group(MlpppTpIpIntf)". "Peer IP Address(PeerIpAddress)"

à "IP Interface of PPP Link(PppIpIntf)". "Peer IP Address(PeerIpAddress)"

Yes -> Step 3.

No -> Step 2.

2. Modify the configuration as required, and check whether a new notification is reported.

Yes -> Step 3.

No -> End.


4.61 198105004 Failed to operate multicast groupNotification Information

Code: 198105004

Name: Failed to operate multicast group

4-50



Severity: Minor



The interface board fails to be added to the User Trace Multicast Group.

Notification Cause

The interface board fails to be added to the User Trace Multicast Group, which may be caused

by the abnormal communication with the control-plane channel of other control-plane boards or

the abnormal operation of the board.

Impact

The user tracing function of the interface board may fail to operate properly. There is no impact

on services.

Action

Contact the next level of maintenance support.

4.62 198105005 Clock difference of slave is largeNotification Information

Code: 198105005

Name: Clock difference of slave is large

Severity: Minor



The user-plane board detects that the clock difference between the slave subunit and host exceeds

the threshold.

Notification Cause

l The clock deviation between the slave subunit and host exceeds the threshold (default: 36

seconds).

l The crystal oscillator of the slave subunit or host is not accurate.

l The board is writing the black box.

4-51



Impact

The services operating on the slave subunit may be interrupted.

Action

1. Run the SET BLOCKSUNIT:MEID=,SUBSYSTEM=,UNIT=,SUNIT=; command in accordance

with "Slave Sunit" and the physical address in the notification information to block the slave

subunit, and then run the SET UNBLOCKSUNIT:MEID=,SUBSYSTEM=,UNIT=,SUNIT=;

command to unblock the slave subunit. Wait for five hours, and check whether the notification

persists.

Yes -> Step 2.

No -> End.


"Shelf number", "Slot number", and "CPU number" in the notification information. Wait for 5

minutes, and check whether the notification is cleared.

Yes -> End.

No -> Step 3.

3. [[Replace the board with an operational one]], wait for five minutes, and check whether the

notification is cleared.

Yes -> End.

No -> Step 4.


4.63 198105006 Slave losted external clockNotification Information

Code: 198105006

Name: Slave losted external clock

Severity: Minor



The user-plane board detects the loss of the external clock of the slave subunit.

Notification Cause

l The clock channel between the clock board and user-plane board is not operating properly.

l The clock board is not operating properly.

l The hardware of the user-plane board is faulty.

4-52



Impact


Action

1. 1. Run the SET BLOCKSUNIT:MEID=,SUBSYSTEM=,UNIT=,SUNIT=;command in accordance



command to unblock the slave subunit. Wait for five minutes, and check whether the notification

is cleared.

Yes -> End.

No -> Step 2.

2. Check whether an alarm arises on the clock board.

Yes -> Step 3.

No -> Step 4.

3. Handle the related alarm, and check whether the notification is cleared.

Yes -> End.

No -> Step 4.

4. Check whether other alarms arise on the board.

Yes -> Step 5.

No -> Step 6.

5. Handle the related alarms, and check whether the notification is cleared.

Yes -> End.

No -> Step 6.


"Shelf number", "Slot number", and "CPU number" in the notification information. Wait for 5

minutes, and check whether the notification is cleared.

Yes -> End.

No -> Step 7.

7. [[Replace the board with an operational one]], wait for five minutes, and check whether the


Yes -> End.

No -> Step 8.


4.64 198105008 Bandwidth automatic adjustment isuseless


Code: 198105008

Name: Bandwidth automatic adjustment is useless

4-53



Severity: Minor

Type: QoS alarm


The base station controller that has the "Transmission CAC based on SLA-PM" function enabled

detects that bandwidth automatic adjustment is invalid.

Notification Cause

The base station controller cannot completely solve the loss of packets over the path after setting the

transmission path bandwidth to the smallest value.

Impact

The packet loss ratio of the path is larger than the reference value, which causes a decline of the

PS/CS service quality, the access failure, and service interruption.

Action

1. Find the interface location in accordance with the network planning data and "ANE ID" in the

notification information, and check whether the physical cable connected to the interface is loose.

Yes -> Step 2.

No -> Step 3.

2. Secure the physical cable.

3. Wait for half an hour, and check whether the notification persists.

Yes -> Step 4.

No -> End.

4. Record the packet loss ratio in additional information of the newly reported notification, and

contact the next level of maintenance support.

4.65 198105018 Unable to save Performance FileNotification Information

Code: 198105018

Name: Unable to save Performance File

Severity: Minor



The OMP fails to store performance files.

4-54



Notification Cause

l The log server is not operating properly, for example, the link between the log server board and

OMP is broken, the rear card corresponding to the log server board is offline, or the disk of the

log server has insufficient space.

l The OMP is not operating properly, for example, the link with the OMM is broken. If the link

between the OMM and OMP is broken for more than eight performance statistics periods, the

OMP does not write performance files.

Impact

There is no impact on services. The performance statistics data may be lost, causing the performance

statistics results to be incorrect.

Action


198099803 Link Broken Between OMM and NE

Yes -> Step 2.

No -> Step 3.

2. Handle the related alarm, and check whether the notification persists.

Yes -> Step 3.

No -> End.

3. Check whether the following alarms or notifications arise:

198105037 Too high hard disk partition usage rate

199105045 The communication link between LogService board for FST and OMP is broken

Yes -> Step 4.

No -> Step 5.

4. Handle the related alarms or notifications. Wait for a performance statistics period, and check

whether the notification persists.

Yes -> Step 5.

No -> End.


4.66 198105019 SLAVE memory check fail notificationNotification Information

Code: 198105019

Name: SLAVE memory check fail notification

Severity: Minor


4-55




The user-plane board detects a memory soft check failure in the slave subunit.

Notification Cause

The software or hardware of the slave subunit is not operating properly.

Impact


Action

1. Run the SET BLOCKSUNIT:MEID=,SUBSYSTEM=,UNIT=,SUNIT=; command in accordance



command to unblock the slave subunit. Wait for five minutes, and check whether the notification

persists.

Yes -> Step 2.

No -> End.

2. Replace the board with an operational one, wait for five minutes, and check whether the


Yes -> End.

No -> Step 3.


4.67 198105030 OMP received data is not completeNotification Information

Code: 198105030

Name: OMP received data is not complete

Severity: Minor



The non-OMP board detects that not all of the performance data on the board is reported to the OMP.

4-56



Notification Cause

l Too many measurement statistics task are executed at the same time, resulting in a large

amount of performance data on the non-OMP board. The data cannot be sent to the OMP

during the specified time.

l The communication between the OMP and non-OMP board is faulty.

Impact

There is no impact on services. The performance statistics data may be lost, causing the performance

statistics results to be incorrect.

Action


198066004 Control plane communication is abnormal between MP and OMP

Yes -> Step 2.

No -> Step 3.

2. Resolve the related alarm.

3. Terminate part of performance statistics tasks that are not related to the KPI.

4. Wait for 15 minutes, and check whether the notification persists.

Yes -> Step 5.

Yes -> End.


4.68 198105032 Transport Path Occupied BandWidthOverload


Code: 198105032

Name: Transport Path Occupied BandWidth Overload

Severity: Minor

Type: QoS alarm


The base station controller detects that the bandwidth that is already allocated in the transmission

path exceeds the bandwidth upperlimit.

4-57



Notification Cause

l The E1/T1 link is broken.

l The transport quality of the transmission link is deteriorated.

l The intermediate device is faulty.

l The higher-priority service is forcedly accessed.

Impact

The available bandwidth to the destination address is smaller than the allocated bandwidth, the base

station controller selectively releases services over the transmission path to avoid congestions on

the transmission path.

Action

1. Query the transmission path object in the corresponding office in accordance with "ANE ID" and

"Transmission path ID" in the alarm information. Check whether the "Transport BandWidth

Adjustment Switch based on IP SLA(IpBandAdjSwitch)" parameter of the object is set to

"1:(Open)".

Yes-> It means that the "Transmission CAC based on SLA-PM" function is enabled, and the

transport quality of the transmission channel to the office is deteriorated or the intermediate

device is faulty. In this case, contact the maintenance personnel of the intermediate device to

resolve the fault. End alarm handling.

No -> Step 2.

2. It means a higher-priority service is forcedly accessed, causing the exceeding of the bandwidth

limit. In this case, no action is required, and end alarm handling.

4.69 198105033 Transport Path group OccupiedBandwidth Overload


Code: 198105033

Name: Transport Path group Occupied Bandwidth Overload

Severity: Minor

Type: QoS alarm


The base station controller detects that the bandwidth that is already allocated in the transmission

path group exceeds the bandwidth upperlimit.

4-58



Notification Cause

l The E1/T1 link is broken.

l The transport quality of the transmission link is deteriorated.

l The intermediate device is faulty.

l The higher-priority service is forcedly accessed.

Impact

The available bandwidth to the destination address is smaller than the allocated bandwidth, and

therefore the rate at which services operate over the path group decreases.

Action

1. Query the "Transmission Path Group(TrPathGroup)" object in accordance with "Path group ID" in

the alarm information. If "E1/T1 Transport BandWidth Adjustment Switch(E1T1BandAdjSwit)" is

set to "1:(Open)", check whether the following alarms arise:

198000518 Trunk link is used for CSU loopback test

198000519 Trunk error

198000520 Trunk abnormal

198001792 Loss of SDH transmission link

198001825 High BER on SDH / Sonet link


Yes -> Step 2.

No -> Step 3.

2. Resolve the related alarms, and end alarm handling.

3. It means a higher-priority service is forcedly accessed, causing the exceeding of the bandwidth

limit. In this case, no action is required, and end alarm handling.

4.70 198018755 HDLC status changedNotification Information

l Notification code: 198018755l Name: HDLC status changedl Notification severity: Majorl Notification type: Communication alarm


HDLC status changed

4-59



Notification Cause

1. This notification occurs when an HDLC is created.

2. The link is broken or recovered.

Impact

If the HDLC is the last available one in the UID,the service on the UID will be interrupted. If the HDLC

is not the last available one in the UID, the traffic on the UID will be reduced.

Action

1.Check the settings of HDLC channel to see whether the E1/TI of this HDLC and its time slots are

accordant with the peer end.

2.Check whether the physical connection is correct.

3.Check whether the E1/T1 line is damaged.

4.Note down the statistic data of messages received and sent from the HDLC, and contact the

next level of maintenance support.

4.71 198021329 LSDB OverflowNotification Information

l Notification code: 198021329l Name: LSDB Overflowl Notification severity: Majorl Notification type: Processing error alarm


LSDB Overflow

Notification Cause

The LSDB (Link Status Database) overflows.

Impact

LSA addition failure and LSDB synchronization failure

Action

1.Configure route aggregation to reduce the number of LSAs. Check if the alarm is eliminated.

Y->If so, finish the alarm handling.


4-60



4.72 198021330 Configuration of OSPF mismatchedNotification Information

l Notification code: 198021330l Name: Configuration of OSPF mismatchedl Notification severity: Minorl Notification type: Processing error alarm


Configuration of OSPF mismatched

Notification Cause

Configuration mismatched, OSPF cannot run in normal.

Impact

Route learning and calculation failure

Action

1.To modify the relevant configuration of OSPF and make them are coordinated. Check if the alarm is

eliminated.



4.73 198021331 Failed to add the ospf route to thecourier routing table


l Notification code: 198021331l Name: Failed to add the ospf route to the courier routing tablel Notification severity: Majorl Notification type: Equipment alarm


Failed to add the ospf routes to the dynamic protocol routing table for overflowing

Notification Cause

Failed to add the ospf routes to the dynamic protocol routing table for overflowing

4-61



Impact

OSPF route lost

Action

1.Check routes on RPU through the background to see whether there are any needless interface

addresses and static routes.

Y->If the unwanted IP addresses or static routes exist, delete the unwanted IP interface addresses

or static routes. If so, go to step "2".

N->If IP address is not configured on the interface, go to step "3".

2.Check whether the alarm is eliminated.


N->If not, go to step "3".

3.Reduce the quantity of its distributed route information through route aggregation on the peer router

and then check whether the local alarm is eliminated.


N->If not, go to step "4".

4.Record the detailed information.

1) Record IP address and static route configuration on the interface.

2) Record the dynamic route information. Contact the next level of maintenance support.

4.74 198028231 Router ID not configured for OSPFv3Notification Information

l Notification code: 198028231l Name: Router ID not configured for OSPFv3l Notification severity: Minorl Notification type: Equipment alarm


OSPF3: not config router ID

Notification Cause

Router ID not configured for OSPFv3.

Impact

OSPFv3 Instance creation failure

4-62



Action

1.Configure an IPv4 address for an interface (It is recommended to configured an IPv4 address for a

Loopback interface) , make it a Router ID, and then re-create an OSPF process. Check whether

the alarm disappears.

Y->End.


4.75 198028233 Configuration of OSPFv3 MismatchedNotification Information

l Notification code: 198028233l Name: Configuration of OSPFv3 Mismatchedl Notification severity: Minorl Notification type: Equipment alarm


Configuration of OSPFv3 Mismatched

Notification Cause

Cannot learn and calculate route.

Impact

Route learning and calculation failure

Action

1.To modify the relevant configuration of OSPF and make them are coordinated. Check if the alarm is

eliminated.



4.76 198021837 Failure in adding dynamic routingsNotification Information

l Notification code: 198021837l Name: Failure in adding dynamic routingsl Notification severity: Majorl Notification type: Processing error alarm

4-63




Failed to add routes to IP forwarding table for overflowing of the table

Notification Cause

Forwarding table overflow causes the failure in adding routes.

Impact

Dynamic route loss occurs.

Action

1.Check routes on RPU to see if there are any needless interface addresses and static routes.

Y->If there are, delete the unwanted IP interface addresses or static routes, go to "2".

N->If IP address is not configured on the interface, go to "3".

2.Check if the alarm is eliminated.


N->If not, go to "3".

3.Reduce the quantity of its distributed route information through route aggregation on the peer router.

And check if the alarm is eliminated on the local.



4.Record the detailed information.

1)Record IP address and static route information on the interface.

2)Record the dynamic route information. Contact the next level of maintenance support.

4.77 198021059 RIP Neighbor Configuration ErrorsNotification Information

l Notification code: 198021059l Name: RIP Neighbor Configuration Errorsl Notification severity: Minorl Notification type: Equipment alarm


RIP neighbor configuration errors

Notification Cause

When adding a neighbor, the address of the neighbor mismatches with that of the interface.

4-64



Impact

The dynamic route expected to be obtained from this neighbor fails to be established.

Action

1.Check the address of interface to see whether it is in the same network segment with that of rip

neighbor.

Y->If so, go to "3".


2.Check if the configured neighbor address is the network number or broadcast address.

Y->If so, go to "3".

N->go to "4".

3.Reconfigure the neighbor address to finish the alarm handling.

4.Contact the next level of maintenance support.

4.78 198021060 RIP Interface Authentication ErrorsNotification Information

l Notification code: 198021060l Name: RIP Interface Authentication Errorsl Notification severity: Minorl Notification type: Processing error alarm


RIP interface authentication fail

Notification Cause

When the interface needs to be authenticated, the authentication code is wrong.

Impact

RIP messages cannot be properly received.

Action

1.Check if the authentication types on the two ends are consistent. If not, go to "2". Y-> If so, go to "3".

2.Modify verification types on two ends as consistent ones. And Finish the alarm handling.

3.If the verification types are consistent, check if the verification keys are consistent, if so, go to "4". If

not, modify them as consistent ones. Finish the alarm handling.


4-65



4.79 198021065 Incompatible RIP Version NumberNotification Information

l Notification code: 198021065l Name: Incompatible RIP Version Numberl Notification severity: Minorl Notification type: Processing error alarm


Refused to receive because of version incompatibility between interface and route update message

Notification Cause

The version number of the interface on remote device is inconsistent with that on local device.

Impact

RIP messages cannot be properly received.

Action

1.Check if the version number of the interface on remote device is inconsistent with that on local

device. Y-> Go to "3". N-> Go to "2".

2.Reconfigure it and finish the alarm handling.


4.80 198022598 Routers with Conflicting System IdExist in Network


l Notification code: 198022598l Name: Routers with Conflicting System Id Exist in Networkl Notification severity: Minorl Notification type: Processing error alarm


Discover a router with conflicting system id with local

4-66



Notification Cause

In ISIS instance configuration under protocol stack configuration mode, System-id has wrong

configuration.

Impact

ISIS neighbor status fails to be established between the neighboring routers whose system IDs

conflict.

Action

1.Check system id configuration in ISIS instance on the router by show running config command

for conflict.

Y->Modify system id configuration in the instance, go to "2".


2.Check if the alarm is eliminated.

Y->Finish the alarm handling.


4.81 198022599 ISIS Message Authentication FailureNotification Information

l Notification code: 198022599l Name: ISIS Message Authentication Failurel Notification severity: Minorl Notification type: Processing error alarm


ISIS Message Authentication Failure

Notification Cause

Message authentication modes or keys configured on the routers of the two ends are inconsistent.

Impact

The message that fails to be authenticated is omitted. The local router can not synchronize the

LSDB with the corresponding router.

4-67



Action

1.Find out the peer-end router according to system id in the alarm message.

2.Execute the show running config command locally and remotely. Check the routers on the two ends

in the displayed device running configuration to see if the protocol authentication modes in ISIS

protocol stack instance configuration are consistent (MD5/TEXT).

Y->Go to "3".

N->Modify the protocol authentication modes on the routers of the two ends as the consistent ones

and perform the interconnection operations again. Finish the alarm handling.

3.Execute the show running config command locally and remotely. Check the routers on the two ends

in the displayed device running configuration to see if the protocol message authentication keys in

ISIS protocol instance configuration are consistent (MD5/TEXT).


N->Modify the protocol authentication modes on the routers of the two ends as the consistent ones

and perform the interconnection operations again. Finish the alarm handling.

4.82 198021584 Neighbor Hold Timer ExpiredNotification Information

l Notification code: 198021584l Name: Neighbor Hold Timer Expiredl Notification severity: Minorl Notification type: Communication alarm


Neighbor hold timer expired.

Notification Cause

1. The physical link is interrupted.

2. TCP connection is interrupted.

Impact

BGP session is disconnected.

4-68



Action

1.Check if the network configuration is correct.

Y->Go to "2".

N->Configure correctly and finish the alarm handling.

2.Check if the interface network connection and network topology are correct.


N->Connect the port to the network correctly and finish the alarm handling.

4.83 198021585 BGP Interface Down and Neighbor LinkBroken


l Notification code: 198021585l Name: BGP Interface Down and Neighbor Link Brokenl Notification severity: Majorl Notification type: Equipment alarm


BGP interface is down and neighbor link is broken.

Notification Cause

Message 'local interface is down' is received.

Impact

The session of the BGP neighbor on this interface is unavailable.

Action

1.Check if the interface is activated (using show ip interface brief command).


N-> Go to "2".

2.Check if the port is connected to the network correctly.


N-> Connect the port to the network correctly. And check if the alarm disappears, if so, finish the

alarm handling.

4-69



4.84 198029760 DNS server inaccessibleNotification Information

l Notification code: 198029760l Name: DNS server inaccessiblel Notification severity: Minorl Notification type: Communication alarm


DNS server can't be accessed.

Notification Cause

DNS server makes no response, so the link may be broken or the DNS server is down.

Impact

DNS client does not work.

Action

1.Use command Ping to check whether the link between the network element which the DNS client

belongs to and the DNS server is available.

Y->go to "2".

N->Solve the physical link problem.

2.Check the status of DNS server to see whether it is listening at port 53.

Y->Contact the next level of maintenance support.

N->Solve equipment problem.

4.85 198016193 SIG_IPI Forwards Service MessagesAbnormally


l Notification code: 198016193l Name: SIG_IPI Forwards Service Messages Abnormallyl Notification severity: Majorl Notification type: Processing error alarm


SIG_IPI forwards service messages abnormally

4-70



Notification Cause

1. Association is not configured on the SIPI board.

2. The hardware of the SIPI board is faulty.

3. Transmission network is faulty.

Impact

The SIPI board will restart, which may affect the normal data packet processing of the board, and

causes the services on the board unstable.

Action

1. On the background, close the message exception detection of SIG_IPI forwarding service. In

this way, the board will not restart.

2. If an alarm appears when this function is enabled, check whether the signaling is configured

to pass through this board.

3. Check whether the transmission configuration and network are faulty.

4. If the problem still exists, replace the board.

4.86 198005702 Trunk configuration is inconsistentwith function of board


l Notification code: 198005702l Name: Trunk configuration is inconsistent with function of boardl Notification severity: Majorl Notification type: Processing error alarm


Work mode difference with DB trunk configuration

Notification Cause

The board does not support the trunk configuration in the database.

Impact

The board resets automatically.

4-71



Action

1.Check if this board configuration is correct.

Y->Go to "2"

N->Modify the board configuration and then restart the board to see if the alarm is still given: Y->

end,N->go to "2".

2.Replace the board with one that matches the configuration, and check if this alarm is still given.


Y->End.

4.87 198005708 The active/standby modules of PSNclock have changed over successfully


l Notification code: 198005708l Name: The active/standby modules of PSN clock have changed over successfullyl Notification severity: Minorl Notification type: Processing error alarm


The active/standby modules of PSN clock have changed over successfully

Notification Cause

It is triggered from the background.

Impact

None

Action

No need to handle.

4.88 198005714 No external clock for DSPNotification Information

l Notification code: 198005714l Name: No external clock for DSPl Notification severity: Minorl Notification type: Equipment alarm

4-72




No external clock for DSP

Notification Cause

The board does not provide external 16M or 8K clock for MCBSP interface of DSP, so DSP can only

use its clock which is not very steady, resulting in unsteadiness of DSP ping operation.

Impact

None

Action

Check the clock.

4.89 198005194 Changeover of CS Optical InterfacesNotification Information

l Notification code: 198005194l Name: Changeover of CS Optical Interfacesl Notification severity: Minorl Notification type: Equipment alarm


CS domain optical port has switched over

Notification Cause

1. The CS optical interface changeover is initiated on the background through MML command

operation.

2. The CS optical interface has faults and automatically switches over.

(GE interfaces are located on the upper half of the GUIM/GUIM2 board while the CS domain optical

interfaces are located on the lower half of it.

Impact

Data communication error of T Net occurs.

4-73



Action

1. If it is because of artificial operations, this alarm occurrence belongs to normal situation and

there is no need to handle it.

2. Confirm if the indication light of the CS optical interface on the board which gives the alarm is off.If

the light is off, check if the fiber or light module has problems.

3. Check if the following alarm occurs in local/opposite board. If yes, refer to the corresponding

alarm handling suggestion.

1286 Loss of clock when input to board

5639 High error rate of optical interface

5646 Phase-lock loop unlock

4.90 198005960 Version Fails to Be SwitchedNotification Information

l Notification code: 198005960l Name: Version Fails to Be Switchedl Notification severity: Minorl Notification type: Processing error alarm


Switch version fail

Notification Cause

The slave board have some master processes when update the EPLD.

Impact

EPLD upgrade fails.

Action

Switch some active functions (such as optical interfaces) to standby ones on the standby board

through MML command operation.Switch again after the operation.

4.91 198087360 BCCH Exchange FailNotification Information

l Notification code: 198087360l Name: BCCH Exchange Fail

4-74



l Notification severity: Minorl Notification type: Processing error alarm


This notification is reported if the BSC detects a BCCH switchover failure.

Notification Cause

l BCCH switchover is disabled.

l Operations on the destination carrier frequency fails during BCCH switchover.

l The destination carrier frequency is not available.

Impact

Voice and data services are not available in the cell.

Action

1. According to the object reporting this notification, query the object "GSM Cell

Configuration(GGsmCell)", and check whether the parameter "BCCH switch

allowed(CanBcchExch)" is "Yes".

Query the global object "GSM Logical Configuration(GBssFunction)", and check whether the

parameter "BCCH switch allowed(CanBcchExch)" is "Yes".

Yes -> Step 3.

No -> Step 2.

2. Modify these two parameters to "Yes". Wait for eight minutes, and check whether the notification

is still reported.

Yes -> Step 3.

No -> End.

3. Execute the QRY TRX command based on "Site ID" and "Bts ID" in the alarm details to query

the state of all the carrier frequencies in the cell. Execute the UNB FUTRX or UNB CUTRX

command to unblock the carrier frequencies in "manual block" state based on "Trx ID". Wait for

eight minutes, and check whether the notification is still reported.

Yes -> Step 4.

No -> End.

4. Contact BS maintenance personnel to check whether carrier frequency-related faults occurred.

Yes -> Step 5.

No -> Step 6.

5. Ask BS maintenance personnel to remove the faults. Check whether the notification persists.

Yes -> Step 6.

No -> End.


4-75



4.92 198087393 Ring state notificationNotification Information

l Notification code: 198087393l Name: Ring state notificationl Notification severity: Minorl Notification type: Equipment alarm


This notification is reported if the BSC detects the ring network status has changed. There are

three ring network statuses:

l Switchover status

l Normal connection status

l Disconnection status

Notification Cause

The BS link is broken.

Impact

Services cannot operate properly.

Action


4.93 198087394 Intelligent power up/down preparationnotification


l Notification code: 198087394l Name: Intelligent power up/down preparation notificationl Notification severity: Minorl Notification type: Equipment alarm


This notification is reported if the BSC detects the intelligent power-on/power-off state of the carrier

has been changed.

4-76



Notification Cause

The BSC has changed the power-on/power-off state of the carrier.

Impact

None.

Action


4.94 198087459 cell no gprs traffic informNotification Information

l Notification code: 198087459l Name: cell no gprs traffic informl Notification severity: Minorl Notification type: Communication alarm


This notification is reported if the BSC detects there is no GPRS traffic in a cell for one hour.

Notification Cause

Data service is not available for one hour in the cell.

Impact

None.

Action


4.95 198087469 abis route change informNotification Information

l Notification code: 198087469l Name: abis route change informl Notification severity: Minorl Notification type: Equipment alarm

4-77




This notification is reported if the BSC detects that the Abis interface link changes from the satellite

link to the ground link or from the ground link to the satellite link.

Notification Cause

l The Abis ground link of the satellite-backup site is broken.

l The Abis ground link of the satellite-backup site is restored.

Impact

None.

Action


4.96 198087353 NSVC deletion notificationNotification Information

l Notification code: 198087353l Name: NSVC deletion notificationl Notification severity: Minorl Notification type: Equipment alarm


This notification is reported if a board detects that an NSVC link is deleted manually.

Notification Cause

An NSVC link is deleted manually.

Impact

None.

Action

1. Check whether the NSVC link is the one that should be deleted.

Yes -> End.

No -> Step 2.


4-78



4.97 198087395 SNS Size process failure notificationNotification Information

l Notification code: 198087395l Name: SNS Size process failure notificationl Notification severity: Minorl Notification type: Communication alarm


This notification is reported if a board detects an SNS Size process failure.

Notification Cause

There is no response from the SGSN, or a failure response is received.

Impact

The NSVC link fails to be established.

Action

1. Check whether the configuration of the following parameters of the object "IP Nse(GIpGbNse)" is

consistent with that of the SGSN.

- "Nse ID(GIpGbNseSeq)"

- "SGSN IP Address(SGSNIPAddress)"

- "SGSN UDP Port(SGSNUDPPort)"

Yes -> Step 3.

No -> Step 2.

2. Modify the parameter configuration for consistency with that of the SGSN, and check whether

the notification is cleared.

Yes -> End.

No -> Step 3.


4.98 198087396 SNS Config process failure notificationNotification Information

l Notification code: 198087396l Name: SNS Config process failure notificationl Notification severity: Minorl Notification type: Communication alarm

4-79




This notification is reported if a board detects an SNS Config process failure.

Notification Cause

There is no response from the SGSN, or a failure response is received.

Impact

The NSVC link fails to be established.

Action

1. Check whether the value of the parameter "Signaling Weights(SigWeight)" or "Data

Weights(DataWeight)" of the object "Local End Point(GIpGbLocalEP)" is not equal to 0.

Yes -> Step 3.

No -> Step 2.

2. Modify the signalling or data weight of the IP endpoint to a nonzero value, and check whether

the notification is cleared.

Yes -> End.

No -> Step 3.


4.99 198087466 NSVC's IP deletion notificationNotification Information

l Notification code: 198087466l Name: NSVC's IP deletion notificationl Notification severity: Minorl Notification type: Equipment alarm


This notification is reported if a board detects that an NSVC link in IP is deleted.

Notification Cause

An NSVC link in IP is deleted.

Impact

None.

4-80



Action

1. Based on "NSVCI" together with "SGSN ID" and "NSEI" in the alarm details, check whether the

NSVC link is the one that should be deleted.

Yes -> End.

No -> Step 2.


4.100 198087359 No access of BSC to MSC SPCNotification Information

l Notification code: 198087359l Name: No access of BSC to MSC SPCl Notification severity: Minorl Notification type: Processing error alarm


This notification is reported if the BSC fails to obtain the MSC SPC.

Notification Cause

The BSC is not configured with the MSC office type.

Impact

All the services are interrupted.

Action

1. Configure the object "Adjacent Office Information(RemoteSp)" with "Type of adjacent

office(OfficeType)" of 512(MSCSERVER) or 576(MGW+MSCSERVER). whether the notification

persists.

Yes -> Step 2.

No -> End.


4.101 198087503 Baseband frequency hoppingexchange for trx fail


l Notification code: 198087503

4-81



l Name: Baseband frequency hopping exchange for trx faill Notification severity: Minorl Notification type: Equipment alarm


This notification is reported if the BSC detects a carrier failure in a baseband frequency-hopping

group and automatically performs active/standby switchover.

Notification Cause

A carrier failure occurs in a baseband frequency-hopping group.

Impact

None.

Action

1. Execute the QRY TRX command based on "Site ID", "Bts ID", and "Trx ID" in the alarm details,

and check whether the status of this carrier is "manual block".

Yes -> Step 2.

No -> Step 3.

2. Execute the UNB FUTRX or UNB CUTRX command based on "Site ID", "Bts ID", and "Trx ID" in

the alarm details to unblock the blocked carrier Check whether the following notifications arise:

198087504 Baseband frequency hopping exchange for trx restore

Yes -> End.

No -> Step 5.

3. Contact BS maintenance personnel to check whether carrier related faults occurred.

Yes -> Step 4.

No -> Step 5.

4. Ask BS maintenance personnel to remove the faults. The alarm handling is completed.


4.102 198087504 Baseband frequency hoppingexchange for trx restore


l Notification code: 198087504l Name: Baseband frequency hopping exchange for trx restorel Notification severity: Minorl Notification type: Equipment alarm

4-82




This notification is reported if the BSC detects a carrier recovery in a baseband frequency-hopping

group and automatically performs active/standby switchover.

Notification Cause

A carrier in a baseband frequency-hopping group recovers.

Impact

None.

Action


4.103 198087508 Block Successfully After Servicereleased


l Notification code: 198087508l Name: Block Successfully After Service releasedl Notification severity: Minorl Notification type: Processing error alarm


This notification is generated if the network management system initiates cell/carrier/timeslot "Block

after service released" and the BSC performs one of the following operations.

- The object is blocked after the current services are released.

- The system initiates BCCH switchover when the BSC is waiting for resources to be released. The

object is blocked mandatorily.

- The object is blocked mandatorily when the longest timer expires and the resources are not

released yet.

Notification Cause

The BSC performs the "Block after service released" function.

Impact

The blocked resources cannot be used. The system capacity is decreased.

4-83



Action


4.104 198087751 dbsapp no avilable PCU resourceinform


l Notification code: 198087751l Name: dbsapp no avilable PCU resource informl Notification severity: Minorl Notification type: QoS alarm


This notification is generated if the BSC detects that PCU resources are insufficient when the cell

is selecting PCU resource.

Notification Cause

l PCU resources are insufficient.

l PCU resources are faulty.

Impact

Some cells cannot provide data service.

Action

1. On the rack diagram of [Alarm management], check whether an alarm exists on the UPPB board.

Yes -> Step 2.

No -> Step 3.

2. Handle the alarm. The alarm handling is completed.


4.105 198087754 Board back upNotification Information

l Notification code: 198087754l Name: Board back upl Notification severity: Majorl Notification type: Processing error alarm

4-84




This notification is generated if the BSC detects that switchover occurs on the BIPB board or the

LAPD board.

Notification Cause

l The system performs switchover automatically due to a sub-unit fault.

l The system performs switchover back automatically after the faulty sub-unit resumes normal.

l Switchover is initiated manually.

Impact

None.

Action

1. Execute the QRY SUNITSTATU command to query the state of the corresponding sub-unit

and check whether the state is "fault" in accordance with "Sub system No", "Source Unit No",

and "Source sub unit No" in the alarm details.

Yes -> Step 2.

No -> Step 3.

2. Execute the SET DSPRESE command to reset this sub-unit upon the relevant RACK, SHELF,

SLOT configuration information in accordance with "Sub system No", "Source Unit No", and

"Source sub unit No" in the alarm details. Then, execute the QRY SUNITSTATU command to

query the state of the corresponding sub-unit and check whether the state is "fault".

Yes -> Step 3.

No -> End.


4.106 198087760 BTSmaster power recover notificationNotification Information

l Notification code: 198087760l Name: BTS master power recover notificationl Notification severity: Minorl Notification type: QoS alarm


This notification is generated if the BSC detects that the master power of the base station is recovered.

Notification Cause

The master power of the base station is recovered.

4-85



Impact

None.

Action


4.107 198087761 BTS master power interruptionnotification


l Notification code: 198087761l Name: BTS master power interruption notificationl Notification severity: Minorl Notification type: QoS alarm


If the BSC receives the "BTS master power interruption" message reported by the base station and

it waits for a moment (by configuring "Site(GBtsSiteManager)"."the delay time of master power

Off(MasterPwrOffTime)", and confirms that some carriers are powered off after the master power is

off, the BSC generates this notification.

Notification Cause

The master power of the base station is off.

Impact

None.

Action


4.108 198087762 After BTS mains power failure TRXterminated notification


l Notification code: 198087762

4-86



l Name: After BTS mains power failure TRX terminated notificationl Notification severity: Minorl Notification type: QoS alarm


If the BSC detects that the master power of the base station is off and it waits for a moment (by

configuring "Site(GBtsSiteManager)"."the delay time of master power Off(MasterPwrOffTime)", and

confirms that some carriers are powered off after the master power is off and then waits for another

moment (by configuring ""Site(GBtsSiteManager)"."the delay time of Transceivers Off(TrxOffTime)"

before terminating all carriers except BCCH carrier, the BSC generates this notification.

Notification Cause

The master power of the base station is off.

Impact

None.

Action


4.109 198087772 Super Site Connect inNotification Information

l Notification code: 198087772l Name: Super Site Connect inl Notification severity: Majorl Notification type: QoS alarm


This notification is generated if the BSC detects that the Abis link of the super station is exchanged

(among the subaerial link, the satellite link or the standby link).

Notification Cause

The Abis link of the super station is exchanged.

Impact

None.

4-87



Action


4.110 198087799 Cell intelligent power-on orpower-down


l Notification code: 198087799l Name: Cell intelligent power-on or power-downl Notification severity: Minorl Notification type: Processing error alarm


This notification is generated if the BSC detects the power-on/power-off state of the cell's BCCH

carrier has been changed.

Notification Cause

The BSC has changed the power-on/power-off state of the cell's BCCH carrier.

Impact

None.

Action


4.111 198087514 TRAU frame sync loss notificationNotification Information

l Notification code: 198087514l Name: TRAU frame sync loss notificationl Notification severity: Minorl Notification type: Communication alarm


This notification is generated if the BSC detects that TRAU frame alignment loss occurs on a voice

channel for a long time.

4-88



Notification Cause

The transmission quality of this channel is poor.

Impact

None.

Action


4.112 198087515 BCCH Exchange SuccessNotification Information

l Notification code: 198087515l Name: BCCH Exchange Successl Notification severity: Minorl Notification type: Processing error alarm


This notification is generated if the BSC detects BCCH switchover success.

Notification Cause

BCCH switchover is successful.

Impact

None.

Action


4.113 198087516 Mute call detectNotification Information

l Notification code: 198087516l Name: Mute call detectl Notification severity: Minorl Notification type: Communication alarm

4-89




This notification is generated if the BSC detects that packet loss occurs on a voice channel for a

long time.

Notification Cause

For a long time, voice data cannot be detected on this channel.

Impact

None.

Action


4.114 198087519 Release dynamic association by forceNotification Information

l Notification code: 198087519l Name: Release dynamic association by forcel Notification severity: Minorl Notification type: Communication alarm


This notification is reported if the BSC automatically releases a detected illegal dynamic association.

Notification Cause

l More than two dynamic associations are established between the BSC and a base station.

l A conflict of local port number occurs between the new dynamic association and an existing

association (master or slave) due to incorrect association configuration at the base station side.

Impact

The association establishment on the Abis interface of the base station may be influenced.

4-90



Action

1. Locate the base station and its site ID in accordance with "peer IP address" and "peer port

ID" in the alarm details, and check whether more than two associations are configured at the

base station side.

Yes -> Step 2.

No -> Step 3.

2. Delete the extra associations. Check whether the notification persists.

Yes -> Step 3.

No -> End.

3. View the association configuration at the base station side, and check whether the local port

number of the association is configured to the site ID of the base station.

Yes -> Step 5.

No -> Step 4.

4. Modify the configuration at the base station side, and configure the local port number to that of

the base station. Check whether the notification persists.

Yes -> Step 5.

No -> End.


4.115 198087520 Gb interface throughput exceedpermissible value


l Notification code: 198087520l Name: Gb interface throughput exceed permissible valuel Notification severity: Minorl Notification type: QoS alarm


This alarm is reported if a board detects that the throughput of a Gb interface exceeds the permissible

value.

Notification Cause

The throughput of the Gb interface exceeds the configured permissible value continuously for several

times due to high PS traffic.

Impact

Some users fail to gain access to the system due to the automatically initiated flow control.

4-91



Action

The BSC will implement flow control automatically. Observing notifications is required without the

need of further operation. The capacity can be expanded if an increase of the upper limit of Gb

interface throughput is required.

4.116 198087338 TRX No TrafficNotification Information

l Notification code: 198087338l Name: TRX No Trafficl Notification severity: Minorl Notification type: Communication alarm


None

Notification Cause

Cell No Traffic

Impact

None.

Action

None

4.117 198087434 Cannot detect up or down TRAUnotification


l Notification code: 198087434l Name: Cannot detect up or down TRAU notificationl Notification severity: Minorl Notification type: Communication alarm


None

4-92



Notification Cause

Cannot detect up or down TRAU

Impact

None.

Action

None

4.118 198087339 BTS self maintenance informNotification Information

l Notification code: 198087339l Name: BTS self maintenance informl Notification severity: Minorl Notification type: Equipment alarm


None

Notification Cause

BTS Board Reboot

Impact

None.

Action

None

4.119 198087477 site board cpu overloadNotification Information

l Notification code: 198087477l Name: site board cpu overloadl Notification severity: Majorl Notification type: Equipment alarm

4-93




None

Notification Cause

CMB/DTPU/FIB CPU usage rate over 80%

Impact

None.

Action

None

4.120 198087478 uplink user layer jam informNotification Information

l Notification code: 198087478l Name: uplink user layer jam informl Notification severity: Minorl Notification type: Communication alarm


None

Notification Cause

Uplink data in user layer is jaming

Impact

None.

Action

1) Modify to static channel, reserve not more than 4 channels for PS.

2) If 16 channels of 2 TRX all for PS, modify to static coding mode, and coding mode should Less

than MCS6. If EDGE not work, this restrict is not exist.

4-94



4.121 198087479 downlink user layer jam informNotification Information

l Notification code: 198087479l Name: downlink user layer jam informl Notification severity: Minorl Notification type: Communication alarm


None

Notification Cause

Downlink data in user layer is jaming

Impact

None.

Action

1) Modify to static channel, reserve not more than 4 channels for PS.

2)If 16 channels of 2 TRX all for PS, modify to static coding mode, and coding mode should Less than

MCS6. If EDGE not work, this restrict is not exist.

4.122 198087488 chp cycle adjust trau informationNotification Information

l Notification code: 198087488l Name: chp cycle adjust trau informationl Notification severity: Minorl Notification type: Communication alarm


None

Notification Cause

13MHz clock of Um is unsynchronized with HW 8K clock on DTRU.

4-95



Impact

CS and PS performance may be degraded.

Action

In E1 Abis mode, be sure 'clock synchronization' is network synchronization.

4.123 198087500 Radio Interface Synchronization ARFemendate Successfully


l Notification code: 198087500l Name: Radio Interface Synchronization ARF emendate Successfullyl Notification severity: Minorl Notification type: Communication alarm


None

Notification Cause

Search Radio Interface Synchronization Successfully.

Impact

None.

Action

Check the display of the value of ARFCN at OMM.

4.124 198087501 Radio Interface Synchronization ARFemendate Failed


l Notification code: 198087501l Name: Radio Interface Synchronization ARF emendate Failedl Notification severity: Minorl Notification type: Communication alarm

4-96




None

Notification Cause

Search Radio Interface Synchronization Failed.

Impact

26 M frequency deviation correction fails to be executed.

Action

Check the reason of failure at iOMCR:

0x01 No suitable Arfcn；0x02 Radio Synchronization failed；0x03 Other.

4.125 198087502 Site IP Address conflictedNotification Information

l Notification code: 198087502l Name: Site IP Address conflictedl Notification severity: Minorl Notification type: Equipment alarm


None

Notification Cause

Site IP Conflict

Impact

The site fails to operate properly.

Action

Remodify the IP of site

4-97



4.126 198087512 IDS Attack detectingNotification Information

l Notification code: 198087512l Name: IDS Attack detectingl Notification severity: Minorl Notification type: Communication alarm


None

Notification Cause

IDS detecting the network attacking

Impact

User-defined.

Action

None

4-98


Appendix ALink InformationTable of Contents

� A2051..................................................................................................................... A-1

A.1 A2051Run the START DTM command to perform a diagnosis test to the board and checkthe status of all the RUB resource boards.

Command example

START DTM:TESTTYPE=DIAG_BOARD_TEST, OBJTYPE="Board", MOC="PhysCpu",MOI="SubNetwork=35, MEID=35, Equipment=1,Rack=1, Shelf=2, Board=7, PhysCpu=1", ATTRIBUTES="RackNo=1, ShelfNo=2, SlotNo=7, CpuNo=1", TESTSEQ="1";

Parameter description

"TESTTYPE" Select "DIAG_BOARD_TEST".

"OBJTYPE" Enter the test object type "Board".

"MOC" Enter the MOC "PhysCpu".

"MOI" Enter the test object DN.

Enter specific parameters.

RackNo　　 Rack number of the tested board.

ShelfNo　　 Shelf number of the tested board.

SlotNo 　　 Slot number of the tested board.

"ATTRIBUTES"

CpuNo 　　 Number of the first physical CPU of the tested board.

"TESTSEQ" Enter any integer from 1 to 200.

Run the above board diagnosis command on each configured RUB board.

A-1




A-2


GlossaryAAL2- ATM Adaptation Layer type 2

ATM- Asynchronous Transfer Mode

BSC- Base Station Controller

BTS- Base Transceiver Station

BVC- BSSGP Virtual Connection

CHUB- Control plane HUB

CMB- Call Me Back

CN- Core Network

CPU- Central Processing Unit

CS- Circuit Switched

DHCP- Dynamic Host Configuration Protocol

GSM- Global System for Mobile Communications

LAPD- Link Access Procedure for D-channel

MO- Managed Object

MOC- Managed Object Class

NE- Network Element

NSE- Network Service Entity

I



NSVC- Network Service Virtual Connection

OMCB- Operation & Maintenance Center for Node B

OMM- Operation & Maintenance Module

OMP- Operation & Maintenance Processor

PCU- Packet Control Unit

PPP- Point-to-Point Protocol

PS- Packet Switched

RNC- Radio Network Controller

RUB- RNC User Plane Board

SCTP- Stream Control Transmission Protocol

SGSN- Serving GPRS Support Node

SLA- Service Level Agreement

SPC- Signaling Point Code

TD- Time Division

THUB- Trunk HUB

TRAU- Transcoder Rate Adaptor Unit

UDP- User Datagram Protocol

UMTS- Universal Mobile Telecommunication System

VTCD- Voice Transcoder Card based on DSP

II


ZXG10 IBSC (V6.30.103) Alarm and Notification Handling Reference_579008

Documents

Transcript of ZXG10 IBSC (V6.30.103) Alarm and Notification Handling Reference_579008