SJ-20130408113951-012-ZXG10 IBSC (V6.30.103) Alarm and Notification Handling Reference

ZXG10 iBSC
Base Station Controller

Alarm and Notification Handling Reference
Version: V6.30.103
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2013 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 ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R1.0 20130604 First edition
Serial Number: SJ-20130408113951-012
Publishing Date: 20130604 (R1.0)
SJ-20130408113951-012|20130604 (R1.0) ZTE Proprietary and Confidential

Contents
About This Manual ......................................................................................... I
Chapter 1 Overview .................................................................................... 1-1
Chapter 2 Alarm.......................................................................................... 2-1
2.1 Equipment Alarm................................................................................................ 2-1
2.1.1 198001284 The phase of 8K, 16K clock, input to backplane board, is not
matched ................................................................................................. 2-1
2.1.2 198001286 Input clock of board lost .......................................................... 2-2
2.1.3 198001792 Loss of SDH transmission link ................................................. 2-2
2.1.4 198001825 High BER on SDH / Sonet link ................................................. 2-4
2.1.5 198002560 Board CPU overload ............................................................... 2-4
2.1.6 198002561 High temperature on CPU board.............................................. 2-5
2.1.7 198002563 FPGA clock speed abnormal alarm.......................................... 2-6
2.1.8 198002564 Auxiliary clock speed abnormal alarm ...................................... 2-7
2.1.9 198005121 Inter-shelf media plane links abnormal ..................................... 2-7
2.1.10 198005124 Capacity of TRUNK communication is insufficient ................... 2-8
2.1.11 198005125 GE optical connection is cross connected ............................... 2-9
2.1.12 198005130 The fiber port failed to change over ...................................... 2-10
2.1.13 198005131 The fiber's quality abnormal................................................. 2-10
2.1.14 198005132 Mate board RUN signal invalid..............................................2-11
2.1.15 198005376 Internal media port of board is abnormal................................2-11
2.1.16 198005381 Input clock is abnormal........................................................ 2-12
2.1.17 198005389 CPU sub card in position is not configured in the database ..... 2-13
2.1.18 198005390 CPU sub card is missing from slot but is configured in
database .............................................................................................. 2-14
2.1.19 198005395 External port abnormal ........................................................ 2-14
2.1.20 198005396 Exceptional communication on UIM board or back plane ...... 2-15
2.1.21 198005399 DSP resource is unavailable................................................ 2-16
2.1.22 198005403 Board SRAM self-check fails ............................................... 2-17
2.1.23 198005404 Board OCXO oven fault....................................................... 2-17
2.1.24 198005405 Clock board phase-lock loop work mode abnormal................ 2-18
2.1.25 198005632 Hard disk usage rate exceeds threshold. ............................. 2-18
2.1.26 198005633 Hard disk is faulty ............................................................... 2-19
2.1.27 198005635 The board is not plugged firmly ............................................ 2-20
2.1.28 198005637 Back card does not match with front board ........................... 2-20

2.1.29 198005639 High Error Rate of Optical Interface ..................................... 2-21
2.1.30 198005640 FPGA exception ................................................................. 2-22
2.1.31 198005641 Port Link Down ................................................................... 2-22
2.1.32 198005644 The channel in a sub card is down ....................................... 2-23
2.1.33 198005645 Sub card abnormal ............................................................. 2-23
2.1.34 198005646 Phase-lock loop unlocked ................................................... 2-24
2.1.35 198005647 High BER on E1 link ........................................................... 2-25
2.1.36 198005650 Conflicted MAC addresses of boards on the same shelf ........ 2-26
2.1.37 198005653 Type B fault on board (GPS) phase-lock equipment .............. 2-27
2.1.38 198005655 Errors detected in DSP........................................................ 2-28
2.1.39 198005656 Input clock of subcard lost ................................................... 2-28
2.1.40 198005657 Error of LVDS path frame detection ..................................... 2-29
2.1.41 198005658 Failure in diagnosing link loop back of large T network .......... 2-29
2.1.42 198005660 Physical link down between master port and slave port ......... 2-30
2.1.43 198005661 Physical link down between media interface ports ................. 2-31
2.1.44 198005662 IDE running overtime .......................................................... 2-31
2.1.45 198005663 Component fault ................................................................. 2-32
2.1.46 198005665 Fault on board (GPS) ......................................................... 2-32
2.1.47 198005667 E1 is looped back ............................................................... 2-33
2.1.48 198005668 Cross-linked E1 alarm ......................................................... 2-34
2.1.49 198005669 Synchronization status check of FPGA failed ........................ 2-35
2.1.50 198005670 Oscillator status abnormal ................................................... 2-35
2.1.51 198005671 Sending or receiving packets using the cascade ports inner
board failed .......................................................................................... 2-36
2.1.52 198005672 Synchronization Ethernet clock source is unusable ............... 2-36
2.1.53 198005673 Backboard switch set is changed. ........................................ 2-37
2.1.54 198005674 Sending or receiving packets between management port
and CPU control port failed.................................................................... 2-38
2.1.55 198005675 The input electrical source is error ....................................... 2-38
2.1.56 198005676 Connect port flow over threshold.......................................... 2-39
2.1.57 198005791 TX output power exceeds the high threshold ........................ 2-40
2.1.58 198005792 TX output power exceeds the low threshold.......................... 2-40
2.1.59 198005793 RX output power exceeds the high threshold ........................ 2-41
2.1.60 198005794 RX output power exceeds the low threshold ......................... 2-42
2.1.61 198005795 The optical transceiver transmitter fault ................................ 2-42
2.1.62 198005893 Memory check failed ........................................................... 2-43
2.1.63 198015874 Data traffic to PSN board is congested ................................. 2-43
2.1.64 198015875 GLI table lookup failed ........................................................ 2-44
II

2.1.65 198015876 GLI exception packets statistic over threshold....................... 2-44
2.1.66 198015877 GLIQV SRAM/DRAM error .................................................. 2-45
2.1.67 198015878 GLI internal fabric port receive error ..................................... 2-45
2.1.68 198015879 GLI Port receive error.......................................................... 2-46
2.1.69 198015880 GLI board control and media plane communication error ....... 2-47
2.1.70 198015881 GLI port transmit error ......................................................... 2-47
2.1.71 198015882 GLI buffer error or allocate fail ............................................. 2-48
2.1.72 198016641 Device's LRU algorithm invalid............................................. 2-48
2.1.73 198016896 APP driver memory operation abnormal ............................... 2-49
2.1.74 198018436 Board loop back detection is abnormal ................................. 2-49
2.1.75 198019456 All high-speed links between line card and switching boards
are out of synchronization...................................................................... 2-50
2.1.76 198019465 CSIX RX and TX packets is abnormal .................................. 2-51
2.1.77 198019712 APS channel mismatched ................................................... 2-51
2.1.78 198019713 APS mode mismatched....................................................... 2-52
2.1.79 198019714 APS configuration alarm...................................................... 2-53
2.1.80 198019715 MS APS channel gets errors................................................ 2-54
2.1.81 198025601 TSNB internal connection chip fault...................................... 2-55
2.1.82 198025602 TDM switch abnormal ......................................................... 2-55
2.1.83 198026116 PP2S output clock lost......................................................... 2-56
2.1.84 198026117 PP2S clock reference lost.................................................... 2-57
2.1.85 198026118 16CHIP clock reference lost................................................. 2-57
2.1.86 198026127 Loss of Level 3 reference source clock................................. 2-58
2.1.87 198026128 Loss of Level2 reference source clock ................................. 2-58
2.1.88 198026129 Loss of Level1 reference source clock.................................. 2-59
2.1.89 198026131 CLKG board PLL is unlocked. Clock will drift ....................... 2-60
2.1.90 198026133 Output clock lost ................................................................. 2-60
2.1.91 198028672 80g chip abnormal .............................................................. 2-61
2.1.92 198029952 802.3ah link fault ................................................................ 2-61
2.1.93 198030208 Fault alarm of CFM ............................................................. 2-62
2.1.94 198066033 T-net center is fault ............................................................. 2-64
2.1.95 198066070 Board offline or CPU in reset status for a long period ............ 2-64
2.1.96 198087000 Dry contact alarm 1............................................................. 2-65
2.1.100 198087004 Dry contact alarm 5 ........................................................... 2-67
III

2.1.105 198087009 Dry contact alarm 10 ......................................................... 2-69
2.1.108 198087012 EAM dry contact 1 alarm .................................................. 2-71
2.1.109 198087013 EAM dry contact 2 alarm ................................................... 2-71
2.1.110 198087014 EAM dry contact 3 alarm.................................................... 2-72
2.1.116 198087102 Power overvoltage/undervoltage alarm ............................... 2-75
2.1.117 198087103 13M input clock failure ....................................................... 2-75
2.1.118 198087106 SYNCLK clock failure ........................................................ 2-76
2.1.119 198087107 Master and slave communication link failure ....................... 2-76
2.1.120 198087108 Standby CMM/CMB board not present ............................... 2-77
2.1.121 198087109 Standby CMM/CMB board abnormal .................................. 2-77
2.1.122 198087110 CMM/CMB power failure alarm .......................................... 2-78
2.1.123 198087112 Communication link alarm between master and slave rack
(left) .................................................................................................... 2-78
2.1.124 198087113 Communication link alarm between master and slave rack
(right) .................................................................................................. 2-79
2.1.125 198087114 A interface E1 Rx carrier alarm .......................................... 2-79
2.1.126 198087115 A interface E1 Rx frame not synchronized........................... 2-80
2.1.127 198087120 A interface E1 remote alarm .............................................. 2-81
2.1.128 198087121 B interface E1 Rx carrier alarm .......................................... 2-81
2.1.129 198087122 B interface E1 Rx frame not synchronized .......................... 2-82
2.1.130 198087127 B interface E1 remote alarm .............................................. 2-82
2.1.131 198087128 C interface E1 Rx carrier alarm .......................................... 2-83
2.1.132 198087129 C interface E1 Rx frame not synchronized .......................... 2-83
2.1.133 198087134 C interface E1 remote alarm .............................................. 2-84
2.1.134 198087135 D interface E1 Rx carrier alarm .......................................... 2-84
2.1.135 198087136 D interface E1 Rx frame not synchronized .......................... 2-85
2.1.136 198087141 D interface E1 remote alarm .............................................. 2-85
2.1.137 198087142 E interface E1 Rx carrier alarm .......................................... 2-86
IV

2.1.138 198087143 E interface E1 Rx frame not synchronized .......................... 2-87
2.1.139 198087148 E interface E1 remote alarm .............................................. 2-87
2.1.140 198087149 F interface E1 Rx carrier alarm .......................................... 2-88
2.1.141 198087150 F interface E1 Rx frame not synchronized .......................... 2-88
2.1.142 198087153 F interface E1 Rx forward sliding indication......................... 2-89
2.1.143 198087155 F interface E1 remote alarm .............................................. 2-89
2.1.144 198087156 G interface E1 Rx carrier alarm .......................................... 2-90
2.1.145 198087157 G interface E2 Rx frame not synchronized .......................... 2-90
2.1.146 198087162 G interface E1 remote alarm .............................................. 2-91
2.1.147 198087163 H interface E1 Rx carrier alarm .......................................... 2-91
2.1.148 198087164 H interface E3 Rx frame not synchronized .......................... 2-92
2.1.149 198087169 H interface E1 remote alarm .............................................. 2-93
2.1.150 198087170 Temperature alarm............................................................ 2-93
2.1.151 198087171 Fan absent ....................................................................... 2-94
2.1.152 198087172 Fan control board CPU alarm ............................................ 2-94
2.1.153 198087173 Fan alarm ........................................................................ 2-95
2.1.154 198087174 Fan temperature alarm ...................................................... 2-95
2.1.155 198087175 Fan 1 alarm ...................................................................... 2-96
2.1.156 198087176 Fan 2 alarm ...................................................................... 2-96
2.1.157 198087177 Fan control board alarm .................................................... 2-97
2.1.158 198087178 LNA alarm ....................................................................... 2-98
2.1.159 198087179 Tower amplifier power alarm .............................................. 2-98
2.1.160 198087180 SWR of AEM HYCOM minor alarm .................................... 2-99
2.1.161 198087181 SWR of AEM HYCOM major alarm .................................... 2-99
2.1.162 198087182 AEM power alarm(BTS V2)...............................................2-100
2.1.163 198087183 AEM type alarm(BTS V2) .................................................2-100
2.1.164 198087184 AEM absent(BTS V2) .......................................................2-101
2.1.165 198087185 AEM power alarm ............................................................2-101
2.1.166 198087186 LNA0 alarm ....................................................................2-102
2.1.167 198087187 LNA1 alarm ....................................................................2-102
2.1.168 198087188 Tower Amplifier0 power alarm ..........................................2-103
2.1.169 198087189 Tower Amplifier1 power alarm ...........................................2-104
2.1.170 198087190 SWR of AEM HYCOM minor alarm ..................................2-105
2.1.171 198087191 SWR of AEM HYCOM major alarm ..................................2-106
2.1.172 198087192 AEM type alarm ...............................................................2-106
2.1.173 198087193 AEM Not-in-position alarm ................................................2-107
2.1.174 198087198 Uplink of ADC chip initialization failure...............................2-108

2.1.175 198087200 CIP resource can't be used...............................................2-108
2.1.176 198087201 Uplink failure....................................................................2-109
2.1.177 198087207 Watchdog of FUC overflow ...............................................2-109
2.1.178 198087216 Cell configuration parameter mismatch(BTS V2) ................ 2-110
2.1.179 198087221 Communication link between CMM and FUC break(BTS
V2)...................................................................................................... 2-111
2.1.180 198087224 Watchdog of TPU CIP overflow......................................... 2-111
2.1.181 198087225 Software version of CIP mismatch..................................... 2-112
2.1.182 198087226 Clock alarm for TPU and CMM ......................................... 2-112
2.1.183 198087228 TPU frame No. alarm ....................................................... 2-113
2.1.184 198087229 TPU CHP DSP0 initialization failure .................................. 2-113
2.1.185 198087243 Cell configuration parameter mismatch.............................. 2-114
2.1.186 198087247 HDLC communication link between CMB and FUC
broken................................................................................................. 2-115
2.1.187 198087253 FU fram No error alarm ................................................... 2-115
2.1.188 198087254 Rx PLL1 unlock ............................................................... 2-116
2.1.189 198087255 Rx PLL2 unlock ............................................................... 2-116
2.1.190 198087256 Tx PLL1 unlock ............................................................... 2-117
2.1.191 198087257 Tx PLL2 unlock ............................................................... 2-118
2.1.192 198087258 52M referenced clock PLL unlock ..................................... 2-118
2.1.193 198087259 Tx IF PLL unlock ............................................................. 2-119
2.1.194 198087260 EEPROM resource can't be used...................................... 2-119
2.1.195 198087261 FPGA interface failure ......................................................2-120
2.1.196 198087262 PA VSWR alarm(BTS V2).................................................2-120
2.1.197 198087263 PA overtemperature minor alarm(BTS V2) ........................2-121
2.1.198 198087264 PA overtemperature major alarm(BTS V2) .........................2-121
2.1.199 198087265 PA output power alarm .....................................................2-122
2.1.200 198087266 PA power overvoltage ......................................................2-122
2.1.201 198087267 PA power lower voltage ....................................................2-123
2.1.202 198087268 Downlink checksum error of DLRC_AL1 ............................2-123
2.1.203 198087269 DUC chip initialization failure ............................................2-124
2.1.204 198087270 80w PA VSWR alarm .......................................................2-124
2.1.205 198087271 80w PA overtemperature ..................................................2-125
2.1.206 198087272 80w PA overtemperature major alarm................................2-125
2.1.207 198087273 80w PA output power alarm ..............................................2-126
2.1.208 198087274 80w PA power overvoltage ...............................................2-127
2.1.209 198087275 80w PA power lower voltage .............................................2-127
2.1.210 198087276 80w PA absent.................................................................2-128
VI

2.1.211 198087277 TXIF unlock .....................................................................2-128
2.1.212 198087278 TPF unlock ......................................................................2-129
2.1.213 198087279 TXRF unlock....................................................................2-129
2.1.214 198087280 RXRF unlock ...................................................................2-130
2.1.215 198087281 13 MHz clock lost.............................................................2-131
2.1.216 198087282 60 ms clock lost ...............................................................2-131
2.1.217 198087285 52 MHz clock lost.............................................................2-132
2.1.218 198087288 PA power overvoltage alarm .............................................2-132
2.1.219 198087289 PA power undervoltage alarm ...........................................2-133
2.1.220 198087290 PA VSWR alarm ..............................................................2-133
2.1.221 198087291 PA temperature minor alarm .............................................2-134
2.1.222 198087292 PA temperature major alarm .............................................2-134
2.1.223 198087293 PA forward power(3db) alarm............................................2-135
2.1.224 198087294 RTU power alarm.............................................................2-136
2.1.225 198087295 RTU power temperature alarm ..........................................2-136
2.1.226 198087296 RTU power output overvoltage alarm ................................2-137
2.1.227 198087297 RTU power input failure alarm...........................................2-137
2.1.228 198087298 IQ calibration parameters abnormal alarm .........................2-138
2.1.229 198087299 EAM heat exchanger alarm ..............................................2-138
2.1.230 198087300 EAM TRX layer fan-4 alarm ..............................................2-139
2.1.231 198087301 EAM AEM layer axis-flow fan alarm...................................2-139
2.1.232 198087302 EAM smoke alarm............................................................2-140
2.1.233 198087303 EAM waterproof alarm......................................................2-140
2.1.234 198087304 EAM lightning protection alarm .........................................2-141
2.1.235 198087305 EAM backdoor access control alarm .................................2-141
2.1.236 198087306 EAM frontdoor access control alarm..................................2-142
2.1.237 198087307 EAM PWR monitoring unit alarm.......................................2-142
2.1.238 198087308 EAM heat exchanger electric heater alarm.........................2-143
2.1.239 198087309 EAM heat exchanger control board alarm ..........................2-143
2.1.240 198087310 EAM heat exchanger external circulation fan 2 alarm .........2-144
2.1.241 198087311 EAM heat exchanger external circulation fan 1 alarm..........2-144
2.1.242 198087312 EAM heat exchanger internal circulation fan 2 alarm ..........2-145
2.1.243 198087313 EAM heat exchanger internal circulation fan 1 alarm ..........2-145
2.1.244 198087314 EAM heat exchanger 485 communication alarm.................2-146
2.1.245 198087315 EAM temperature alarm ...................................................2-146
2.1.246 198087316 EAM TRX layer mixed-flow fan 1 alarm .............................2-147
VII

2.1.249 198087319 Communication broken between EAM and CMB ................2-148
2.1.250 198087320 Power undervoltage alarm ................................................2-149
2.1.251 198087321 Inner fan 2 alarm (for M8202) ...........................................2-149
2.1.252 198087322 Inner fan 1 alarm (for M8202) ...........................................2-150
2.1.253 198087323 Outer fan 2 and fan 4 alarm (for M8202) ............................2-150
2.1.254 198087324 Outer fan 1 and fan 3 alarm (for M8202) ............................2-151
2.1.255 198087325 Rack temperature minor alarm..........................................2-151
2.1.256 198087326 Rack temperature major alarm..........................................2-152
2.1.257 198087327 Layer 3 fan 1 alarm (for M8206) ........................................2-152
2.1.266 198087340 FR device failure..............................................................2-157
2.1.267 198087341 FR congestion .................................................................2-158
2.1.268 198087344 MSC overload control alarm at FUC mode.........................2-158
2.1.269 198087345 CPU overload control alarm at FUC mode .........................2-159
2.1.270 198087346 Signaling point congestion control alarm at FUC mode .......2-160
2.1.271 198087347 MSC overload control alarm at SYS mode .........................2-160
2.1.272 198087348 CPU overload control alarm at SYS mode .........................2-161
2.1.273 198087349 Signaling point congestion control alarm at SYS mode .......2-161
2.1.274 198087350 CCCH overload control.....................................................2-162
2.1.275 198087351 PCCCH overload control ..................................................2-162
2.1.276 198087352 NSVC's E1 failure alarm ...................................................2-163
2.1.277 198087391 FCU power undervoltage alarm ........................................2-164
2.1.278 198087403 The clock alarm about transmission of CCI board Abis-E1
...........................................................................................................2-164
2.1.279 198087404 The local working clock alarm of CCI board .......................2-165
2.1.280 198087405 The clock alarm about transmission of CCI board 13M ......2-165
2.1.281 198087406 CCI opposite board alarm.................................................2-166
2.1.282 198087407 IQ FPGA internal clock alarm............................................2-166
2.1.283 198087408 IQ FPGA light interface alarm ..........................................2-167
2.1.284 198087409 IQ FPGA LVDS interface alarm .........................................2-167
VIII

2.1.285 198087410 IQ FPGA internal data alarm.............................................2-168
2.1.286 198087411 13M,61.44M clock lost alarm.............................................2-168
2.1.287 198087412 60ms clock lost alarm.......................................................2-169
2.1.288 198087413 26MHz and 52MHz lost of clock alarm...............................2-169
2.1.289 198087414 the failure examination alarm of the 60ms uplink frame.......2-170
2.1.290 198087415 checking block data error alarm ........................................2-170
2.1.291 198087416 up link LVDS SERDES lost lock alarm ...............................2-171
2.1.292 198087417 FN error alarm .................................................................2-171
2.1.293 198087432 Diversity antenna lost .......................................................2-172
2.1.294 198087433 Diversity antenna identical ................................................2-172
2.1.295 198087443 Diversity antenna lost .......................................................2-173
2.1.296 198087444 Diversity antenna identical ................................................2-173
2.1.297 198087451 board not support 16MHW................................................2-174
2.1.298 198087452 cmb or cpu overload.........................................................2-174
2.1.299 198087453 signal HDLC break off ......................................................2-175
2.1.300 198087454 main HDLC break off........................................................2-175
2.1.301 198087455 FIB configure wrong .........................................................2-176
2.1.302 198087456 lay3 of FIB software has no response................................2-176
2.1.303 198087458 PS cell block caused by slave ...........................................2-177
2.1.304 198087460 positive 12 voltage alarm ..................................................2-177
2.1.305 198087461 negative 12 voltage alarm.................................................2-178
2.1.306 198087462 DSP 1.2v voltage alarm....................................................2-178
2.1.307 198087463 6.4v voltage alarm............................................................2-179
2.1.308 198087464 5v voltage alarm ..............................................................2-179
2.1.309 198087465 NSVC's IP failure alarm ....................................................2-180
2.1.310 198087470 Fan absence alarm ..........................................................2-180
2.1.311 198087471 Fan rotate alarm...............................................................2-181
2.1.312 198087472 CMB and FNCB RS485 link break alarm ...........................2-181
2.1.313 198087473 DTPU CPU overload ........................................................2-182
2.1.314 198087480 Status of TX5 filter alarm ..................................................2-182
2.1.315 198087481 Status of TX6 filter alarm ..................................................2-183
2.1.316 198087482 dbsapp data error alarm ...................................................2-183
2.1.317 198087483 GPS signal synchronization exception ...............................2-184
2.1.318 198087484 Second pulse loss............................................................2-185
2.1.319 198087485 Antenna open-circuit alarm ...............................................2-185
2.1.320 198087486 Antenna short-circuit alarm ...............................................2-186
2.1.321 198087487 Lost satellite alarm ...........................................................2-186
IX

2.1.322 198087505 Board Connect Fail ..........................................................2-187
2.1.323 198087510 CPU of FIB overload ........................................................2-187
2.1.324 198087517 Shelf overload control alarm at FUC mode.........................2-188
2.1.325 198087518 Shelf overload control alarm at SYS mode.........................2-188
2.1.326 198087768 Resource Availability Alarm of SLAVE ...............................2-189
2.1.327 198087778 Dry contact alarm - Waterlog.............................................2-190
2.1.328 198087779 Dry contact alarm - Power loss .........................................2-190
2.1.329 198087780 Dry contact alarm - No.1 air conditioner fault......................2-191
2.1.330 198087781 Dry contact alarm - No.2 air conditioner fault......................2-191
2.1.331 198087782 Dry contact alarm - AC power abnormal ............................2-192
2.1.332 198087783 Dry contact alarm - Battery under-voltage .........................2-192
2.1.333 198087784 Dry contact alarm - SMR abnormal ...................................2-193
2.1.334 198087785 Dry contact alarm - Under-voltage insulate drop.................2-193
2.1.335 198087786 Dry contact alarm - Device suspended ..............................2-194
2.1.336 198087787 User-defined Dry contact alarm 1 ......................................2-194
2.1.345 198087796 User-defined Dry contact alarm 10 ....................................2-199
2.1.346 198087797 User-defined Dry contact alarm 11 ....................................2-199
2.1.347 198088000 DTPU not support Baseband-Hop alarm............................2-200
2.1.348 198088001 PA Power Voltage Adjusting Path Disconnected.................2-200
2.1.349 198088002 PA Power Voltage Adjusting Data Error .............................2-201
2.1.350 198088003 PA Power Voltage Adjusting Data Illegal ............................2-201
2.1.351 198088004 Access iBSC failure..........................................................2-202
2.1.352 198088005 Control link broken ...........................................................2-202
2.1.353 198088006 Operation link broken(CS) ................................................2-203
2.1.354 198088007 Operation link broken(PS) ................................................2-203
2.1.355 198088008 Parameter configuration mismatch ....................................2-204
2.1.356 198088009 DSP initialization failure....................................................2-204
2.1.357 198088010 Parameter configuration failure of AD6537.........................2-205
2.1.358 198088011 Tx PLL unlock ..................................................................2-205

2.1.359 198088012 Wrong parameter configuration for EEPROM.....................2-206
2.1.360 198088013 FLASH memory fault ........................................................2-206
2.1.361 198088014 Run abnormity of DSP......................................................2-207
2.1.362 198088015 FPGA interface fault.........................................................2-207
2.1.363 198088016 CHP frame fault ...............................................................2-208
2.1.364 198088017 Wrong receive channel of RF............................................2-208
2.1.365 198088018 Get DNS failure when configuration IP of active .................2-209
2.1.366 198088019 Analyse failure of DNS domain name ................................2-209
2.1.367 198088020 IPSec failure ....................................................................2-210
2.1.368 198088021 RF channel and HTRG board unconformity .......................2-210
2.1.369 198088022 Get HBTS'S IP address failure from DHCP Sever .............. 2-211
2.1.370 198088023 Over temperature............................................................. 2-211
2.1.371 198088024 Voltage abnormity ............................................................2-212
2.1.372 198088025 Abis link change alarm .....................................................2-212
2.1.373 198088026 IPOE uplink and downlink jam alarm .................................2-213
2.1.374 198088027 DIP E1 rack, rack type error..............................................2-213
2.1.375 198088028 DIP E1 rack, rack number error.........................................2-214
2.1.376 198088029 DIP E1 rack,slave rack 1 port error....................................2-214
2.1.377 198088030 DIP E1 rack,slave rack 2 port error....................................2-215
2.1.378 198088031 DIP E1 rack,satellite back up flag error ..............................2-215
2.1.379 198088032 DIP E1 rack,oam time slot error ........................................2-216
2.1.380 198088033 DIP IP rack,access mode error(IP or IPOE) .......................2-216
2.1.381 198088034 DIP IP rack,rack number error...........................................2-217
2.1.382 198088035 DIP IP rack,site number error............................................2-217
2.1.383 198088036 DIP IP rack,sequence number error ..................................2-218
2.1.384 198088037 Mains power failure alarm.................................................2-218
2.1.385 198088038 Alarm of the trx's down link LRC failed...............................2-219
2.1.386 198105025 the rate of abnormal service on SLAVE is high ...................2-219
2.1.387 198105026 Media Ip address modified................................................2-220
2.1.388 198105029 OMP reboot alarm............................................................2-220
2.1.389 198105034 Back card of LogService board is offline ............................2-221
2.1.390 198105036 The hard disk of LogService error .....................................2-221
2.1.391 198105037 Too high hard disk partition usage rate ..............................2-222
2.1.392 198105039 Bursty flow rate of the control plane for shelf connection
overload ..............................................................................................2-222
2.1.393 198000002 Loss of optical signal ........................................................2-223
2.1.394 198000256 Ethernet link to OMC is broken. ........................................2-224
2.2 Communication Alarm .....................................................................................2-225
XI

2.2.1 198005378 Board HW Error...................................................................2-225
2.2.2 198005382 Communication between power board and OMP is
abnormal .............................................................................................2-226
2.2.3 198005397 Communication of RAWMACIP channel is abnormal..............2-226
2.2.4 198005401 Test packet check abnormal .................................................2-227
2.2.5 198005651 IP / MAC address conflict .....................................................2-228
2.2.6 198005664 The rate of error code in a mate link is high at
GUIM/GUIM2.......................................................................................2-229
2.2.7 198005666 The number of the error packets from MAC port exceeds the
threshold .............................................................................................2-229
2.2.8 198015617 Some frames Received by FE/GE/ATM/MP/POS/E1 Port are
faulty ...................................................................................................2-230
2.2.9 198015618 Faulty frames received by port over threshold........................2-231
2.2.10 198015873 PSN board is sending out incorrect frames ..........................2-231
2.2.11 198022784 BFD Session Interrupted ....................................................2-232
2.2.12 198029953 The Ethernet port state is OAM loop back ...........................2-233
2.2.13 198031744 IPD session interrupted ......................................................2-234
2.2.14 198066000 Abis link broken .................................................................2-235
2.2.15 198066003 Control plane communication is abnormal between board
and its home module ............................................................................2-236
2.2.16 198066004 Control plane communication is abnormal between MP and
OMP ...................................................................................................2-237
2.2.17 198066005 SCCP subsystem unavailable.............................................2-238
2.2.18 198066008 MTP2 link sending overload ...............................................2-239
2.2.19 198066009 MTP2 link reception overload .............................................2-239
2.2.20 198066010 MTP3 Signalling Point Inaccessible.....................................2-240
2.2.21 198066011 MTP3 link unavailable ........................................................2-240
2.2.22 198066012 MTP3 cluster inaccessible ..................................................2-241
2.2.23 198066014 M3UA Signalling Point Inaccessible ....................................2-242
2.2.24 198066019 Association link broken.......................................................2-243
2.2.25 198066026 Association path broken .....................................................2-244
2.2.26 198066029 PPP link broken .................................................................2-245
2.2.27 198087101 HW link broken ..................................................................2-246
2.2.28 198087336 Rack Abis control link broken..............................................2-246
2.2.29 198087337 Site Abis control link broken................................................2-247
2.2.30 198087342 Cell interruption alarm ........................................................2-248
2.2.31 198087343 Front PC communication link broken alarm..........................2-249
2.2.32 198087380 TRX Manual Block .............................................................2-250
XII

2.2.33 198087381 The time-slot of air interface blocked manually.....................2-250
2.2.34 198087468 lapd jam alarm...................................................................2-251
2.2.35 198087775 super site exchanged to the satellitic ABIS link or slave
link......................................................................................................2-251
2.2.36 198105035 The communication link between LogService board and
OMP is broken ....................................................................................2-252
2.2.37 198000519 Trunk error ........................................................................2-252
2.2.38 198000520 Trunk abnormal .................................................................2-253
2.2.39 198003841 The control plane retransmission ratio over the threshold ......2-254
2.2.40 198005122 Loss of Active/standby communication link ..........................2-255
2.2.41 198005126 Incorrect FE Routing Connection ........................................2-255
2.2.42 198005127 FE Link Error Alarm ...........................................................2-256
2.2.43 198005128 Duplicate rack and shelf .....................................................2-257
2.2.44 198005129 Ethernet port loop back error ..............................................2-258
2.3 Processing alarm ............................................................................................2-258
2.3.1 198005120 T Network Connection Not Conform to Configuration .............2-258
2.3.2 198005123 Incorrect configuration for inserted board or device ................2-259
2.3.3 198005387 Alarm due to inconsistent MP type ........................................2-259
2.3.4 198005388 Startup file does not exist .....................................................2-260
2.3.5 198005398 Office ID is not set correctly with control shelf ........................2-261
2.3.6 198005402 Database config is different from file named bootcfg.ini ..........2-261
2.3.7 198005649 Port configuration is incorrect ...............................................2-262
2.3.8 198005889 Version Switches While Board Doesn't Reset ........................2-263
2.3.9 198005892 Boot Version Fails to Write to Backup Region ........................2-264
2.3.10 198007936 Memory file buffer overflow.................................................2-264
2.3.11 198015360 Microcode Is Abnormal.......................................................2-265
2.3.12 198023040 Number of alarms exceeds threshold. .................................2-265
2.3.13 198066013 MTP3 link congestion.........................................................2-266
2.3.14 198066018 Association congestion.......................................................2-267
2.3.15 198066027 SNTP failure......................................................................2-267
2.3.16 198066031 OMP alarm pool is full, unable to store any more alarms. ......2-268
2.3.17 198066032 Loss of NTP time synchronisation .......................................2-269
2.3.18 198087513 Board Ethernet port overload alarm.....................................2-269
2.3.19 198087773 CIC manual blocked alarm .................................................2-270
2.3.20 198087774 BVC manual blocked alarm ................................................2-270
2.4 Environment Alarm..........................................................................................2-271
2.4.1 198025856 Rack temperature is high .....................................................2-271
2.4.2 198025857 Low temperature in Rack .....................................................2-271
XIII

2.4.3 198025858 Room temperature is higher than high threshold ...................2-272
2.4.4 198025859 Room temperature is lower than low threshold ......................2-273
2.4.5 198025860 Rack voltage is high ............................................................2-273
2.4.6 198025861 rack voltage is low ...............................................................2-274
2.4.7 198025862 Humidity is high ...................................................................2-275
2.4.8 198025863 Humidity is low ....................................................................2-275
2.4.9 198025864 Fault in fan plug-in box ........................................................2-276
2.4.10 198025865 Rack door alarm ................................................................2-277
2.4.11 198025866 Smoke detected.................................................................2-277
2.4.12 198025867 Infrared alarm ....................................................................2-278
2.4.13 198025868 Lightning alarm ..................................................................2-279
2.4.14 198025869 Loss of DC power supply to rack.........................................2-279
2.4.15 198029184 SNTP server is unavailable ................................................2-280
2.5 QoS Alarm......................................................................................................2-280
2.5.1 198023296 Inter-board message communication flow rate exceeds the
alarm threshold ....................................................................................2-280
2.5.2 198066069 The number of times of signaling data transfer exceeds the
allowed threshold of the license ............................................................2-281
2.5.3 198087438 Assignment failure alarm......................................................2-282
2.5.4 198087506 NSE block alarm..................................................................2-282
2.5.5 198087507 SGSN is blocked .................................................................2-283
2.5.6 198087758 Manual User Access control alarm........................................2-283
2.5.7 198087759 CPU overload control alarm at Paging mode .........................2-284
Chapter 3 Notification ................................................................................ 3-1

3.1 198003649 Shortage of swap block resource ....................................................... 3-4
3.2 198005188 UIM CS Changeover......................................................................... 3-4
3.3 198005189 Notification of Active/Standby Changeover ........................................ 3-5
3.4 198005192 Board's Work Mode Unsupported ...................................................... 3-6
3.5 198005193 Notification of the power on status of the basic process....................... 3-6
3.6 198005194 Changeover of CS Optical Interfaces ................................................. 3-7
3.7 198005195 Board mix plug occurred ................................................................... 3-8
3.8 198005441 Port status on internal media plane changed ...................................... 3-8
3.9 198005448 485 seriel bus link between CLKG/PWRD and OMP is broken............. 3-9
3.10 198005700 DSP resets for abnormities ............................................................ 3-10
3.11 198005701 Version Load Error ........................................................................ 3-10
3.12 198005702 Trunk configuration is inconsistent with function of board..................3-11
3.13 198005705 MCU resets abnormally ................................................................. 3-12
XIV

3.14 198005708 The active/standby modules of PSN clock have changed over
successfully ................................................................................................... 3-12
3.15 198005710 The result of manual reference selection for SETS chip................... 3-13
3.16 198005711 Clock reference selection is being executed.................................... 3-13
3.17 198005712 The manual select base will be run, please wait for the result .......... 3-14
3.18 198005713 APC chip's peripheral RAM has hardware fault ............................... 3-14
3.19 198005714 No external clock for DSP.............................................................. 3-15
3.20 198005715 PP2S source switched .................................................................. 3-15
3.21 198005718 Two master clock ports is directly connected .................................. 3-16
3.22 198005956 Board Version Error ...................................................................... 3-16
3.23 198005958 IDE Version Files Synchronization Information ................................ 3-17
3.24 198005960 Version Fails to Be Switched ......................................................... 3-18
3.25 198005961 OMP Version Check Information .................................................... 3-18
3.26 198005962 Patch version operate fail .............................................................. 3-19
3.27 198008005 Memory file buffer overflow............................................................ 3-19
3.28 198011840 M3UA user office status change..................................................... 3-20
3.29 198013888 ASP status changed ..................................................................... 3-20
3.30 198013889 AS status changed........................................................................ 3-21
3.31 198013890 Sigtran error message received ..................................................... 3-22
3.32 198013891 Sigtran notification message received ............................................ 3-23
3.33 198013892 Allocate memory fail...................................................................... 3-23
3.34 198014144 Association establishment failed .................................................... 3-24
3.35 198014145 Association restart ........................................................................ 3-25
3.36 198016193 SIG_IPI Forwards Service Messages Abnormally ........................... 3-25
3.37 198017216 Error in MCS Multi-Core processor receiving configuration data
from DBS ....................................................................................................... 3-26
3.38 198018241 TCP Connection Aborted............................................................... 3-26
3.39 198018242 MD5 Verification Failure ................................................................ 3-27
3.40 198018243 Wrong MD5 Message Abstract ...................................................... 3-27
3.41 198018755 HDLC status changed ................................................................... 3-28
3.42 198019777 APS switch over occurred.............................................................. 3-29
3.43 198020291 Protocol stack process failed to initialize during power on ................ 3-29
3.44 198020802 Conflicting IP address in subnet..................................................... 3-30
3.45 198020803 Conflicting MAC address in subnet................................................. 3-31
3.46 198020804 Failed to generate static ARP from IP address ................................ 3-31
3.47 198020805 ARP detect failed .......................................................................... 3-32
3.48 198020806 ARP detect that the static ARP is not match ................................... 3-33
3.49 198021059 RIP Neighbor Configuration Errors ................................................. 3-33
XV

3.50 198021060 RIP Interface Authentication Errors ................................................ 3-34
3.51 198021065 Incompatible RIP Version Number ................................................. 3-34
3.52 198021329 LSDB Overflow ............................................................................. 3-35
3.53 198021330 Configuration of OSPF mismatched ............................................... 3-35
3.54 198021331 Failed to add the ospf route to the courier routing table ................... 3-36
3.55 198021584 Neighbor Hold Timer Expired......................................................... 3-37
3.56 198021585 BGP Interface Down and Neighbor Link Broken.............................. 3-37
3.57 198021837 Failure in adding dynamic routings ................................................. 3-38
3.58 198022598 Routers with Conflicting System Id Exist in Network ........................ 3-39
3.59 198022599 ISIS Message Authentication Failure.............................................. 3-39
3.60 198023106 Board self-check fails .................................................................... 3-40
3.61 198023107 The board initialization failure ........................................................ 3-40
3.62 198023617 Configuration file is unusable ......................................................... 3-41
3.63 198025664 Abnormal Half-Fixed Connection Changes ..................................... 3-42
3.64 198026176 Clock reference changed............................................................... 3-42
3.65 198026177 CLKG reference quality changed ................................................... 3-43
3.66 198026178 Clock work mode changed ............................................................ 3-43
3.67 198026179 Clock source invalidation reason changed ...................................... 3-44
3.68 198028231 Router ID not configured for OSPFv3 ............................................. 3-44
3.69 198028233 Configuration of OSPFv3 Mismatched............................................ 3-45
3.70 198028993 SCTP Primary Path Set Failed....................................................... 3-45
3.71 198029760 DNS server inaccessible ............................................................... 3-46
3.72 198030016 Ethernet link OAM event................................................................ 3-46
3.73 198031040 ACL config failed .......................................................................... 3-47
3.74 198087338 TRX No Traffic.............................................................................. 3-47
3.75 198087339 BTS self maintenance inform ......................................................... 3-48
3.76 198087353 NSVC deletion notification ............................................................. 3-48
3.77 198087355 Timeout notification for a database to return value .......................... 3-49
3.78 198087356 NSVC's reception of incorrect NSVCI notification ............................ 3-49
3.79 198087357 NSVC's reception of incorrect NSEI notification .............................. 3-50
3.80 198087358 NSVC's reception of NS_STATUS_PDU from SGSN notification ...... 3-50
3.81 198087359 No access of BSC to MSC SPC..................................................... 3-51
3.82 198087360 BCCH Exchange Fail .................................................................... 3-51
3.83 198087393 Ring state notification ................................................................... 3-52
3.84 198087394 Intelligent power up/down preparation notification ........................... 3-52
3.85 198087395 SNS Size process failure notification .............................................. 3-53
3.86 198087396 SNS Config process failure notification........................................... 3-53
XVI

3.87 198087397 SNS Add process failure notification .............................................. 3-54
3.88 198087398 SNS Delete process failure notification .......................................... 3-54
3.89 198087399 SNS ChangeWeight process failure notification .............................. 3-55
3.90 198087434 Cannot detect up or down TRAU notification................................... 3-55
3.91 198087459 cell no gprs traffic inform ............................................................... 3-56
3.92 198087466 NSVC's IP deletion notification....................................................... 3-56
3.93 198087469 abis route change inform ............................................................... 3-57
3.94 198087477 site board cpu overload ................................................................. 3-57
3.95 198087478 uplink user layer jam inform ........................................................... 3-57
3.96 198087479 downlink user layer jam inform....................................................... 3-58
3.97 198087488 chp cycle adjust trau information .................................................... 3-58
3.98 198087500 Radio Interface Synchronization ARF emendate Successfully.......... 3-59
3.99 198087501 Radio Interface Synchronization ARF emendate Failed ................... 3-59
3.100 198087502 Site IP Address conflicted............................................................ 3-60
3.101 198087503 Baseband frequency hopping exchange for trx fail ........................ 3-60
3.102 198087504 Baseband frequency hopping exchange for trx restore .................. 3-61
3.103 198087508 Block Successfully After Service released .................................... 3-62
3.104 198087512 IDS Attack detecting.................................................................... 3-62
3.105 198087514 TRAU frame syn loss notification ................................................. 3-63
3.106 198087515 BCCH Exchange Success ........................................................... 3-63
3.107 198087516 Mute call detect .......................................................................... 3-63
3.108 198087751 dbsapp no avilable PCU resource inform ...................................... 3-64
3.109 198087754 Board back up ........................................................................... 3-64
3.110 198087760 BTS master power recover notification.......................................... 3-65
3.111 198087761 BTS master power interruption notification .................................... 3-65
3.112 198087762 BTS mains power failure, TRX is terminated ................................. 3-66
3.113 198087772 Super Site Connect in.................................................................. 3-66
3.114 198087776 Data error report ......................................................................... 3-67
3.115 198087798 Codec Fail .................................................................................. 3-67
3.116 198087799 Cell intelligent power-on or power-down........................................ 3-68
3.117 198105001 Failed to get the table of configuration .......................................... 3-68
3.118 198105002 The route table is overloaded ....................................................... 3-69
3.119 198105003 Failed to handle DHCP message from other network..................... 3-70
3.120 198105004 Failed to operate multicast group ................................................ 3-71
3.121 198105005 Clock difference of slave is large .................................................. 3-71
3.122 198105006 Slave losted external clock .......................................................... 3-72
3.123 198105008 Bandwidth automatic adjustment is useless .................................. 3-72
XVII

3.124 198105009 No acknowledge of SLA query request ......................................... 3-73
3.125 198105011 SBCX Application Exception ........................................................ 3-73
3.126 198105012 SBCX back card offline................................................................ 3-74
3.127 198105018 Unable to save Performance File ................................................. 3-74
3.128 198105019 SLAVE memory check fail notification........................................... 3-75
3.129 198105030 OMP received data is not complete .............................................. 3-76
3.130 198105032 Transport Path Occupied BandWidth Overload ............................. 3-76
3.131 198105033 Transport Path group Occupied Bandwidth Overload .................... 3-77
3.132 198000576 Loss of Frame on Trunk............................................................... 3-77
3.133 198000834 MCC is faulty .............................................................................. 3-78
3.134 198001600 CPU resets on a board ................................................................ 3-79
3.135 198003138 Board FLASH faults .................................................................... 3-79
3.136 198003394 Start daylight saving time............................................................. 3-80
3.137 198003395 End daylight saving time.............................................................. 3-80
Glossary .......................................................................................................... I
XVIII

About This Manual
Purpose
This manual describes how to handle ZXG10 iBSC alarms and notifications.
Intended Audience
This manual is intended for:
l Maintenance engineers
l 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, Alarms Describes the alarms in terms of alarm properties, probable causes,

effect on the system, and handling procedure.
3, Notifications Describes the notifications in terms of notification properties, probable

causes, effect on the system, and handling procedure.

II

Chapter 1
Overview
Functions of Fault Management
The fault management system collects fault information from all the NEs in the managed
network in near real-time, such as boards, links, databases, and servers, and then
displays the collected fault information in the format of alarm or notification. The fault
management system helps the system administrator quickly locate and resolve faults
in the managed network. It also provides telecom operators, network management
departments, and equipment vendors with correct and timely alarm data to ensure stable
network operations.
Fault Indication
The fault management system indicates a fault or event occurring in the network in the
form of alarm or notification.
l A fault is indicated in the form of alarm when it persists and affects the reliability
and 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 the
system, for example, board reset and signaling overload. Such a fault or event is
normally caused by a sudden environment change or other accidental factors. No
special handling is required because the fault or event causing a notification can be
automatically handled by the system. However, a frequently-reported notification
requires troubleshooting.
Alarm Format
The alarms defined for the ZXG10 iBSCare provided with the information such as property
and possible causes. For details, refer to Table 1-1.
Table 1-1 Alarm Format Description
Item Description
Alarm Code Uniquely identifies an alarm.
Alarm Information Summarizes the fault information, such as the fault cause and phenomenon.
1-1

ZXG10 iBSC Alarm and Notification Handling Reference
Item Description
Alarm 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.
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.
Alarm 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 Environmental 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.
Possible Causes Provides probable alarm causes to help users troubleshoot, find preventive
measures, and restore the system to normal state in a timely manner.
Effect on the Provides the consequence of each alarm and the impact on the system and
System services.
Handling Procedure 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-2

Chapter 1 Overview
Notification Format
The notifications defined for the NR8250 are provided with the information such as property
and possible causes. For details, refer to Table 1-2.
Table 1-2 Notification Format Description
Item Description
Notification Code Uniquely identifies a notification.
Notification Summarizes the event information, such as the cause and phenomenon.
Information
Notification Severity No notification severity is available.
Notification Type The notification types are the same as the alarm types.
Possible Causes Provides probable notification causes to help users troubleshoot, find
preventive measures, and restore the system to normal state in a timely
manner.
Effect on the Provides the consequence of each notification and the impact on the system
System and services.
Handling Procedure 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-3

This page intentionally left blank.
1-4

Chapter 2
Alarm
Table of Contents
Equipment Alarm........................................................................................................2-1
Communication Alarm ............................................................................................2-225
Processing alarm ...................................................................................................2-258
Environment Alarm.................................................................................................2-271
QoS Alarm .............................................................................................................2-280
2.1 Equipment Alarm

2.1.1 198001284 The phase of 8K, 16K clock, input to backplane
board, is not matched
Alarm Property
l Alarm Code: 198001284
l Description: The phase of 8K, 16K clock, input to backplane board, is not matched
l Severity: Minor
l Alarm Type: Equipment Alarm
Probable Cause
1. Clock cable is not properly connected.

2. Clock board is faulty.
System 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.
Handling Suggestion
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.
2-1

2.1.2 198001286 Input clock of board lost

Alarm Property
l Description: Input clock of board lost
l Severity: Minor
Probable Cause
1. The board is not in place (not properly inserted) in the slot.

2. Clock cable is disconnected.
3. Clock cable is faulty.
4. Board is faulty.
System 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.
Handling Suggestion
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.
2.1.3 198001792 Loss of SDH transmission link

Alarm Property
l Description: Loss of SDH transmission link
l Severity: Major
2-2

Chapter 2 Alarm
Probable 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.
Optical connector is polluted.
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.
System Impact
SDH/SONET fails to work normally, leading to UE access failure on SDH/SONET and interruption
of ongoing services.
Handling Suggestion
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.
2-3

2.1.4 198001825 High BER on SDH / Sonet link

Alarm Property
l Description: High BER on SDH / Sonet link
l Severity:
Warning
Probable 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.
System 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.
Handling Suggestion
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.
2.1.5 198002560 Board CPU overload

Alarm Property
l Description: Board CPUoverload
2-4

Chapter 2 Alarm
l Severity: Major
Probable Cause
1. Excessive data traffic at higher layer.

2. System is performing data synchronization or saving.
3. CPU alarm threshold setting is under configured.
System 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.
Handling Suggestion
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.
2.1.6 198002561 High temperature on CPU board

Alarm Property
l Description: High temperature on CPU board
l Severity: Major
2-5

Probable Cause
1. Fan faulty.
2. High temperature in rack.
3. CPU overload.
System Impact
Automatic CPU reset might occur.
Handling Suggestion
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.
2.1.7 198002563 FPGA clock speed abnormal alarm

Alarm Property
l Description: FPGAclock speed abnormal alarm
l Severity: Major
Probable Cause
The FPGA clock speed is abnormal.
System Impact
The system time is inaccurate.
2-6

Chapter 2 Alarm
Handling Suggestion
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.
2.1.8 198002564 Auxiliary clock speed abnormal alarm

Alarm Property
l Description: Auxiliary clock speed abnormal alarm
l Severity: Major
Probable Cause
The auxiliary clock speed is abnormal.
System Impact
1. The system time is inaccurate.

2. The Timer is disabled.
Handling Suggestion
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.
2.1.9 198005121 Inter-shelf media plane links abnormal

Alarm Property
l Description: Inter-shelf media plane links abnormal
l Severity: Minor
Probable 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.
2-7

System Impact
The inter-shelf service bandwidth is reduced. The inter-shelf services may be interrupted if no
backup is configured.
Handling Suggestion
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.
5. Replace the opposite board.
2.1.10 198005124 Capacity of TRUNK communication is insufficient

Alarm Property
l Description: Capacity of TRUNK communication is insufficient
l Severity: Minor
Probable Cause
1. Connection failure.
2. Line failure.
3. Board failure.
4. Rear board failure.
System Impact
There is no impact on services when TRUNK connection is 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.
2-8

Chapter 2 Alarm
Handling Suggestion
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.
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.
2.1.11 198005125 GE optical connection is cross connected

Alarm Property
l Description: GE optical connection is cross connected
l Severity: Minor
Probable Cause
1. Fibre connected to wrong module.

2. GE optical transceiver module in wrong slot.
3. Transmit and receive fibres crossed.
System Impact
Cause interruption to all services performed on this shelf.
2-9

Handling Suggestion
1. Check the fiber optics for its proper cross connection

2. Replace the optical fiber or the optical transceiver module
2.1.12 198005130 The fiber port failed to change over

Alarm Property
l Description: The fiber port failed to change over
l Severity: Major
Probable Cause
The fiber port failed to change over
System Impact
The fiber can not work abnormally.
Handling Suggestion
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.
2.1.13 198005131 The fiber's quality abnormal

Alarm Property
l Description: The fiber's quality abnormal
l Severity:
Warning
Probable 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.
2-10

Chapter 2 Alarm
System 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.
Handling Suggestion
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.
5. Replace the board.
2.1.14 198005132 Mate board RUN signal invalid

Alarm Property
l Description: Mate board RUN signal invalid
l Severity: Minor
Probable Cause
The mate board exist POWERON signal but RUN signal is inexistent.
System Impact
Board can not change over.
Handling Suggestion
1. Reboot slave board.

2. Reboot master board.
2.1.15 198005376 Internal media port of board is abnormal

Alarm Property
l Description: Internal media port of board is abnormal
l Severity: Major
2-11

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

2. Failure of local board connecting port on the switching IC 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.
System 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.
Handling Suggestion
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.
2.1.16 198005381 Input clock is abnormal

Alarm Property
l Description: Input clock is abnormal
l Severity: Critical
Probable Cause
1. The Clock board is abnormal.

2. The clock board is not synchronized with reference clock.
3. The clock reference source is abnormal.
2-12

Chapter 2 Alarm
System Impact
The services are interrupted because the system can not get a proper clock.
Handling Suggestion
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.
2.1.17 198005389 CPU sub card in position is not configured in

the database
Alarm Property
l Description: CPU sub card in position is not configured in the database
l Severity:
Warning
Probable Cause
1. Configuration is incorrect.
2. Board is misplaced.
System 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.
Handling Suggestion
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.
2-13

2.1.18 198005390 CPU sub card is missing from slot but is

configured in database
Alarm Property
l Description: CPU sub card is missing from slot but is configured in database
l Severity: Major
Probable Cause
1. The configuration is wrong.

2. A wrong board is inserted.
System 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.
Handling Suggestion
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.
2.1.19 198005395 External port abnormal

Alarm Property
l Description: External port abnormal
l Severity: Major
Probable 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.
2-14

Chapter 2 Alarm
System Impact
This port is not available for services. If there is a standby port, data can be received or transmitted
via the standby port. But 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.
Handling Suggestion
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.
2.1.20 198005396 Exceptional communication on UIM board or

back plane
Alarm Property
l Description: Exceptional communication on UIM board or back plane
l Severity: Major
Probable 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.
System 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.
2-15

Handling Suggestion
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.
6. Replace the UIM in the same shelf.
2.1.21 198005399 DSP resource is unavailable

Alarm Property
l Description: DSPresource is unavailable
l Severity: Major
Probable 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.
System 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.
2-16

Chapter 2 Alarm
Handling Suggestion
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.
2.1.22 198005403 Board SRAM self-check fails

Alarm Property
l Description: Board SRAM self-check fails
l Severity: Major
Probable Cause
Hardware fault of board.
System Impact
Board operation might be abnormal.
Handling Suggestion
Replace the board, and check whether this alarm disappears.
2.1.23 198005404 Board OCXO oven fault

Alarm Property
l Description: Board OCXO oven fault
l Severity: Major
2-17

Probable Cause
Hardware fault of board.
System Impact
Board operation might be abnormal.
Handling Suggestion
Replace the board, and check whether this alarm disappears.
2.1.24 198005405 Clock board phase-lock loop work mode

abnormal
Alarm Property
l Description: Clock board phase-lock loop work mode abnormal
l Severity: Major
Probable Cause
1. There is no available reference source.

2. The clock distribution line is incorrect or there exists self loop.
3. The secondary clock locks the tertiary clock.
System Impact
The designated reference clock cannot be phase-locked.
Handling Suggestion
1. Check if the corresponding clock reference is correctly inputted.

2.1.25 198005632 Hard disk usage rate exceeds threshold.

Alarm Property
l Description: Hard disk usage rate exceeds threshold.
l Severity: Major
2-18

Chapter 2 Alarm
Probable Cause
1. The configured usage rate threshold is unreasonable.

2. The usage rate of hard disk is over high.
System Impact
When hard disk usage rate exceeds its threshold, new data can not be written. The data may be
lost. There is no impact on services.
Handling Suggestion
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.
2.1.26 198005633 Hard disk is faulty

Alarm Property
l Description: Hard disk is faulty
l Severity: Major
Probable Cause
The ribbon cable is loose or the hard disk fails, usually a hardware failure.
System 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.
Handling Suggestion
Replace the fault hard disk or replace the board, where the hard disk is installed.
2-19

2.1.27 198005635 The board is not plugged firmly

Alarm Property
l Description: The board is not plugged firmly
l Severity: Major
Probable Cause
1. The ENUM switch on the board is open, or in poor contact.

2. The EXCH button on the standby board is pressed twice within 3 seconds.
System Impact
The active/standby board changeover or the APS changeover will fail. This board can not be
switched to the active board.
Handling Suggestion
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.
2.1.28 198005637 Back card does not match with front board
Alarm Property
l Description: Back card does not match with front board
l Severity: Minor
Probable Cause
1. Incorrect rear board is used.

2. Rear board failure.
2-20

Chapter 2 Alarm
System 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.
Handling Suggestion
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.
2.1.29 198005639 High Error Rate of Optical Interface

Alarm Property
l Description: High Error Rate of Optical Interface
l Severity: Major
Probable 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.
System 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.
2-21

Handling Suggestion
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.
2.1.30 198005640 FPGA exception

Alarm Property
l Description: FPGA exception
l Severity: Major
Probable Cause
FPGA runs abnormally, for example, FPGA is lost, or the board clock is lost.
System 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.
Handling Suggestion
1. Restart the board. In this case, the board downloads FPGA again.
2.1.31 198005641 Port Link Down

Alarm Property
l Description: Port Link Down
l Severity: Major
2-22

Chapter 2 Alarm
Probable Cause
There is something wrong with the internal chip.
System Impact
DSP is abnormal and call loss increases.
Handling Suggestion
1. Reset the corresponding DSP chip or the board by using MML command on the background and
then check the alarm is eliminated.
2.1.32 198005644 The channel in a sub card is down

Alarm Property
l Description: The channel in a sub card is down
l Severity: Major
Probable Cause
1. The sub-card is not inserted in position.

2. The sub-card has hardware faults.
System Impact
The sub-card channel is not initialized or the initialization fails. As a result, the channel corresponding
to the alarm chip 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.
Handling Suggestion
1. Unplug and plug the sub-card again. Wait for the board to be powered on.
2. Replace the sub-card.
2.1.33 198005645 Sub card abnormal

Alarm Property
l Description: Sub card abnormal
2-23

l Severity: Minor
Probable Cause
1. The GCS, EC or HPS subcard of UIMC/GUIM/CHUB is not inserted in position.

2. The subcard is faulty.
System 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.
Handling Suggestion
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.
2.1.34 198005646 Phase-lock loop unlocked

Alarm Property
l Description: Phase-lock loop unlocked
Probable Cause
1. Clock board faulty.

2. Reference clock has changed to another optical board.
3. Reference clock changed when a board has been removed or plugged in to the shelf.
4. UIMC/GUIM input is disconnected, or UIMC/GUIM clock phase loop is abnormal.
System 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.
2-24

Chapter 2 Alarm
Handling Suggestion
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.
2.1.35 198005647 High BER on E1 link

Alarm Property
l Description: High BER on E1 link
l Severity: Major
Probable Cause
1. The E1/T1 link is faulty.

2. The device in the uplink direction of the trunk link is faulty.
3. The trunk cable or connector is in poor contact.
System 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.
2-25

Handling Suggestion
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.
2.1.36 198005650 Conflicted MAC addresses of boards on the

same shelf
Alarm Property
l Description: Conflicted MAC addresses of boards on the same shelf
Probable 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.
System 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.
Handling Suggestion
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.
2-26

Chapter 2 Alarm
2.1.37 198005653 Type B fault on board (GPS) phase-lock

equipment
Alarm Property
l Description: Type B fault on board (GPS) phase-lock equipment
l Severity: Major
Probable 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.
System 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.
Handling Suggestion
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.
2-27

2.1.38 198005655 Errors detected in DSP

Alarm Property
l Description: Errors detected in DSP
l Severity: Major
Probable Cause
1. The HPI port fails

2. Hardware failure.
System 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.
Handling Suggestion
1. Reset the board.

2. Replace DSP sub-card.
2.1.39 198005656 Input clock of subcard lost

Alarm Property
l Description: Input clock of subcard lost
l Severity: Major
Probable Cause
1. The subcard is loose.

2. The clock circuit of the subcard is damaged.
3. The clock circuit of the mother board is damaged.
System 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.
2-28

Chapter 2 Alarm
Handling Suggestion
1. Check the subcard connection status. If the subcard is loose, tightly connect it and power it
on again.
2. Replace the subcard
2.1.40 198005657 Error of LVDS path frame detection

Alarm Property
l Description: Error of LVDS path frame detection
l Severity: Major
Probable Cause
Error occurs in LVDS path frame detection
System Impact
The board might not work normally.
Handling Suggestion
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.
2.1.41 198005658 Failure in diagnosing link loop back of large T

network
Alarm Property
l Description: Failure in diagnosing link loop back of large T network
l Severity: Major
2-29

Probable Cause
The 129th time slot loop back of LVDS has a failure.
System Impact
The board does not work normally.
Handling Suggestion
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.
2.1.42 198005660 Physical link down between master port and

slave port
Alarm Property
l Description: Physical link down between master port and slave port
l Severity:
Warning
Probable Cause
The running physical link between the master and the slave port is broken.
System Impact
APS function disabled
Handling Suggestion
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.
2-30

Chapter 2 Alarm
2.1.43 198005661 Physical link down between media interface ports

Alarm Property
l Description: Physical link down between media interface ports
l Severity:
Warning
Probable Cause
The network port or board is faulty.
System 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.
Handling Suggestion

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.
.
2.1.44 198005662 IDE running overtime

Alarm Property
l Description: IDE running overtime
l Severity:
Warning
Probable Cause
IDE is operated for longer time.
2-31

System 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.
Handling Suggestion
No handling is necessary.
2.1.45 198005663 Component fault

Alarm Property
l Description: Component fault
l Severity: Major
Probable Cause
Devices or sub-cards on the board operate abnormally.
System 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.
Handling Suggestion
1. Check whether the 'Board input clock lose' or 'PLL unlock' alarm exists. If so, handle the alarm first.
2.1.46 198005665 Fault on board (GPS)

Alarm Property
l Description: Fault on board (GPS)
2-32

Chapter 2 Alarm
Probable 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).
System 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.
Handling Suggestion
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.
2.1.47 198005667 E1 is looped back

Alarm Property
l Description: E1 is looped back
l Severity: Minor
2-33

Probable Cause
1. User has set loop back.

2. Transmission is looped back by provider.
3. Local board is faulty.
4. Remote board is faulty.
5. Loop back applied on DDF.
System Impact
Data can not be sent out because of the loopback E1.
Handling Suggestion
1. Disconnect the loopback E1.

2. Restart the board.
2.1.48 198005668 Cross-linked E1 alarm

Alarm Property
l Description: Cross-linked E1 alarm
l Severity: Minor
Probable Cause
Self board has cross-linked E1.
System Impact
Data can not be sent out because of cross-linked E1.
Handling Suggestion
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.
2-34

Chapter 2 Alarm
2.1.49 198005669 Synchronization status check of FPGA failed

Alarm Property
l Description: Synchronization status check of FPGA failed
Probable 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.
System 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.
Handling Suggestion
Replace the board.
2.1.50 198005670 Oscillator status abnormal

Alarm Property
l Description: Oscillator status abnormal
Probable Cause
Oscillator may stop oscillating or meet frequency deviation.
System Impact
Board cannot work normally with this crucial device error.
Handling Suggestion
Replace the board.
2-35

2.1.51 198005671 Sending or receiving packets using the cascade

ports inner board failed
Alarm Property
l Description: Sending or receiving packets using the cascade ports inner board failed
Probable Cause
1. The subcard GCS of UIM2 is not inserted in position.

2. The subcard GCS of UIM2 has hardware faults.
3. The UIM2/CHUB/GUIM/GUIM2 board has hardware faults.
System 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:
Handling Suggestion
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.
2.1.52 198005672 Synchronization Ethernet clock source is

unusable
Alarm Property
l Description: Synchronization Ethernet clock source is unusable
l Severity: Major
2-36

Chapter 2 Alarm
Probable 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.
System Impact
The slave clock port can not synchronize with the connected port, which will cause processing
abnormity related to the clock.
Handling Suggestion
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.
2.1.53 198005673 Backboard switch set is changed.

Alarm Property
l Description: Backboard switch set is changed.
l Severity: Major
Probable Cause
The setting of the DIP switch on the backboard has been changed.
System Impact
Other board faults
Handling Suggestion
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.
2-37

2.1.54 198005674 Sending or receiving packets between

management port and CPU control port failed
Alarm Property
l Description: Sending or receiving packets between management port and CPU
control port failed
Probable Cause
Management port or CPU control port has faults.
System Impact
Isolate island, checking packets being abnormal or messages between shelves being abnormal may
occur. For active/standby configuration, there are two cases:
Handling Suggestion
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.
2.1.55 198005675 The input electrical source is error

Alarm Property
l Description: The input electrical source is error
l Severity:
Warning
Probable Cause
One of the electrical sources inputted from PDU is abnormal.
2-38

Chapter 2 Alarm
System Impact
The input power of the shelf has may have fault. There will be no power if all two electrical sources
input are abnormal.
Handling Suggestion
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.
N->Please contact the next level of maintenance support.
2.1.56 198005676 Connect port flow over threshold

Alarm Property
l Description: Connect port flow over threshold
l Severity: Major
Probable Cause
The connect port flow is too high, that is over the value of flow threshold configuration.
System Impact
Maybe this port lost lots of packets.
2-39

Handling Suggestion
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.
2.1.57 198005791 TX output power exceeds the high threshold

Alarm Property
l Description: TX output power exceeds the high threshold
l Severity: Minor
Probable Cause
TX output power exceeds the high threshold
System Impact
It affects the data transfer of the remote SFP. If it is serious, which will make bad the SFF on the
other side.
Handling Suggestion
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.
2.1.58 198005792 TX output power exceeds the low threshold

Alarm Property
l Description: TX output power exceeds the low threshold
2-40

Chapter 2 Alarm
l Severity: Minor
Probable Cause
TX output power exceeds the low threshold
System Impact
It affects the data transfer of the SFP.
Handling Suggestion
1. Replace the local SFP.

2.1.59 198005793 RX output power exceeds the high threshold

Alarm Property
l Description: RX output power exceeds the high threshold
l Severity: Minor
Probable Cause
RX output power exceeds the high threshold
System Impact
It affects the data transfer of the local SFP. If it is serious, which will make bad the SFF on the
other side.
Handling Suggestion
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.
2-41

2.1.60 198005794 RX output power exceeds the low threshold

Alarm Property
l Description: RX output power exceeds the low threshold
l Severity: Minor
Probable Cause
RX output power exceeds the low threshold
System Impact
Handling Suggestion
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.
2.1.61 198005795 The optical transceiver transmitter fault

Alarm Property
l Description: The optical transceiver transmitter fault
l Severity: Minor
Probable Cause
The optical transceiver transmitter fault
System Impact
2-42

Chapter 2 Alarm
Handling Suggestion
1. If the connection is loose or broken, tighten or replace the local SFP.

2.1.62 198005893 Memory check failed

Alarm Property
l Description: Memory check failed
Probable Cause
Memory check failed.
System Impact
The operation related to the memory maybe failed.
Handling Suggestion
1. Make records of the alarm information.

2. Replace the board or subcard.
2.1.63 198015874 Data traffic to PSN board is congested

Alarm Property
l Description: Data traffic to PSN board is congested
l Severity: Major
Probable Cause
1. The traffic flow to the board is excessive.

2. The PSN board in the same shelf is abnormal.
3. The board has hardware faults.
2-43

System Impact
The services carried by the board are unstable. In most serious case, all services carried by the
board are interrupted.
Handling Suggestion
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.
198019456 All high-speed links between line card and package switching board are out of
synchronism
2. Unplug and plug the board.
2.1.64 198015875 GLI table lookup failed

Alarm Property
l Description: GLI table lookup failed
l Severity: Minor
Probable Cause
1. L1 table or L2 table error.

2. Destination IP of packets or hardware is error.
System Impact
Packets would be dropped which would cause poor voice quality and other problems.
Handling Suggestion
Switch the master port of the GLI board (where table lookup failed) to the partner board
2.1.65 198015876 GLI exception packets statistic over threshold

Alarm Property
l Description: GLI exception packets statistic over threshold
l Severity: Minor
2-44

Chapter 2 Alarm
Probable Cause
1. Connection between fiber and optic modules is not perfect.

2. Something wrong with fiber optic module.
3. Board hardware error.
System Impact
Handling Suggestion
1. Check the connection between fiber and optic modules.

2. Reboot the board.
2.1.66 198015877 GLIQV SRAM/DRAM error

Alarm Property
l Description: GLIQV SRAM/DRAM error
l Severity: Minor
Probable Cause
1. SRAM of GLIQV is error.

2. DRAM of GLIQV is error.
3. Micro engine of GLIQV is error.
System Impact
Handling Suggestion

2. Change the master port to slave port.
3. Replace the board with a new board.
2.1.67 198015878 GLI internal fabric port receive error

Alarm Property
2-45

l Description: GLI internal fabric port receive error

l Severity: Major
Probable Cause
1. Network Processor or Switch Chip error.

2. PSN Board Hardware error.
System Impact
Handling Suggestion
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.
2.1.68 198015879 GLI Port receive error

Alarm Property
l Description: GLI Port receive error
l Severity: Minor
Probable Cause
1. Connection between fiber and optic modules is not perfect.

2. Something wrong with fiber optic modules.
System Impact
2-46

Chapter 2 Alarm
Handling Suggestion
1.Check the connection between fiber and optic modules.

2. Replace optic modules.
4. Contact the next level of maintenance support.
2.1.69 198015880 GLI board control and media plane

communication error
Alarm Property
l Description: GLI board control and media plane communication error
l Severity: Minor
Probable Cause
1. SRAM or DRAM error.

System Impact
Handling Suggestion

2.1.70 198015881 GLI port transmit error

Alarm Property
l Description: GLI port transmit error
l Severity: Minor
Probable Cause
1. Packets error.
2-47

System Impact
Handling Suggestion
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.
2.1.71 198015882 GLI buffer error or allocate fail

Alarm Property
l Description: GLI buffer error or allocate fail
l Severity: Minor
Probable Cause
1. The traffic is over the capability of the board.

2. SRAM or DRAM error.
System Impact
Handling Suggestion
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.
2.1.72 198016641 Device's LRU algorithm invalid

Alarm Property
l Description: Device's LRU algorithm invalid
2-48

Chapter 2 Alarm
l Severity: Major
Probable Cause
Device's LRU algorithm is invalid.
System Impact
It may cause failure of queue scheduling, and then services won't work normally.
Handling Suggestion
Make records of the alarm information and contact the next level of maintenance support.
2.1.73 198016896 APP driver memory operation abnormal

Alarm Property
l Description: APP driver memory operation abnormal
l Severity: Minor
Probable Cause
1. Static memory is not enough.

2. Pointer was rewrited.
System Impact
The board may reboot when the static memory is not enough.
Handling Suggestion
When the memory exception influences the services, reboot the board.
2.1.74 198018436 Board loop back detection is abnormal

Alarm Property
l Description: Board loop back detection is abnormal
l Severity: Major
2-49

Probable Cause
Board hardware fault.
System Impact
When the slave board change to master, the service through this board will be interrupt.
Handling Suggestion
Replace the board.
2.1.75 198019456 All high-speed links between line card and

switching boards are out of synchronization
Alarm Property
l Description: All high-speed links between line card and switching boards are out of
synchronization
Probable 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.
System 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.
2-50

Chapter 2 Alarm
Handling Suggestion
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.
2.1.76 198019465 CSIX RX and TX packets is abnormal

Alarm Property
l Description: CSIX RX and TX packets is abnormal
l Severity:
Warning
Probable Cause
1. Signal is unstable when rack or board is powering on.

2. Switch chip is abnormal.
System Impact
The transceiver of the media plane is exceptional.
Handling Suggestion
1. Reset the board.

2.1.77 198019712 APS channel mismatched

Alarm Property
2-51

l Description: APS channel mismatched

l Severity: Major
Probable 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.
System 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.
Handling Suggestion
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.
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.
2.1.78 198019713 APS mode mismatched

Alarm Property
l Description: APS mode mismatched
l Severity: Major
2-52

Chapter 2 Alarm
Probable 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.
System 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.
Handling Suggestion
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.
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).
2.1.79 198019714 APS configuration alarm

Alarm Property
l Description: APS configuration alarm
l Severity: Major
2-53

Probable Cause
Optical interface are not configured for APS in 1:1 mode.
System Impact
The board can not enter into normal working status. All board services fail to be established.
Handling Suggestion
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.
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.
2.1.80 198019715 MS APS channel gets errors

Alarm Property
l Description: MS APS channel gets errors
l Severity: Major
Probable 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.
System Impact
1. ASP function is affected.

2. The board master/slave function is affected.
2-54

Chapter 2 Alarm
Handling Suggestion

3. Replace the neighboring board.
4. Replace the slots .
2.1.81 198025601 TSNB internal connection chip fault

Alarm Property
l Description: TSNB internal connection chip fault
l Severity: Major
Probable Cause
Connection chip (73273/73260) faults on TDM Switch Network Board cause some 129 time slots of
HW having connection faults.
System Impact
If the fault occurs on master board, board state will be changed to slave; slave board will be reset
immediately.
Handling Suggestion
1. Try to replace the board and check if the alarm is eliminated.

2.1.82 198025602 TDM switch abnormal

Alarm Property
l Description: TDM switch abnormal
l Severity: Minor
2-55

Probable Cause
1. Check for any clock alarms.

2. TDM Switch chip is faulty
3. Wrong board in configured slot.
System Impact
The link with abnormal connection is interrupted. Accordingly, services are affected.
Handling Suggestion
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.
2.1.83 198026116 PP2S output clock lost

Alarm Property
l Description: PP2S output clock lost
l Severity: Major
Probable Cause
Hardware is faulty.
System 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.
Handling Suggestion
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.
2-56

Chapter 2 Alarm
2.1.84 198026117 PP2S clock reference lost

Alarm Property
l Description: PP2S clock reference lost
l Severity: Major
Probable Cause
Hardware is faulty.
System Impact
The system can not get wanted clock, therefore all clock-related processes are abnormal.
Handling Suggestion
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.
2.1.85 198026118 16CHIP clock reference lost

Alarm Property
l Description: 16CHIP clock reference lost
l Severity: Major
Probable Cause
Hardware is faulty.
System Impact
The system can not get wanted clock, therefore all clock-related processes are abnormal.
Handling Suggestion
Replace the board.
2-57

2.1.86 198026127 Loss of Level 3 reference source clock

Alarm Property
l Description: Loss of Level 3 reference source clock
l Severity: Minor
Probable 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.
System 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.
Handling Suggestion
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.
2.1.87 198026128 Loss of Level2 reference source clock

Alarm Property
l Description: Loss of Level2 reference source clock
l Severity: Major
Probable Cause
Input clock reference is in unavailable status for more than 10 minutes and less than 24 hours.
2-58

Chapter 2 Alarm
System 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.
Handling Suggestion

2.1.88 198026129 Loss of Level1 reference source clock

Alarm Property
l Description: Loss of Level1 reference source clock
Probable Cause
Input clock reference is in unavailable status for more than 24 hours.

System 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.
2-59

Handling Suggestion

2.1.89 198026131 CLKG board PLL is unlocked. Clock will drift

Alarm Property
l Description: CLKG board PLL is unlocked. Clock will drift
l Severity: Minor
Probable Cause
Hardware fault of board
System Impact
System could not get the needed clock, which will cause processing abnormity related to the clock.
Handling Suggestion
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.
2.1.90 198026133 Output clock lost

Alarm Property
l Description: Output clock lost
l Severity: Major
Probable Cause
Hardware is faulty.
2-60

Chapter 2 Alarm
System 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.
Handling Suggestion
1. If the alarm is declared by master board rather than slave board, perform master/slave switching.
2. Replace board.
2.1.91 198028672 80g chip abnormal

Alarm Property
l Description: 80g chip abnormal
Probable Cause
80g detects that the GLIQP board restarts, or the 80g chip is abnormal.
System Impact
Media plane messages are partially lost or unavailable.
Handling Suggestion
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.
2.1.92 198029952 802.3ah link fault

Alarm Property
l Description: 802.3ah link fault
l Severity: Major
2-61

Probable 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
System 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.
Handling Suggestion
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.
2.1.93 198030208 Fault alarm of CFM

Alarm Property
l Description: Fault alarm of CFM
l Severity: Minor
2-62

Chapter 2 Alarm
Probable 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.
LCK:
The MEP is receiving LCK.
System 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.
Handling Suggestion
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:
2-63

Check the alarm of the former MEP.

LCK:
Check the alarm of the former MEP.
2.1.94 198066033 T-net center is fault

Alarm Property
l Description: T-net center is fault
l Severity: Major
Probable Cause
The big T-net center board has a fault.
System Impact
T-net related resource is unavailable.
Handling Suggestion
1. Replace the slot.

2.1.95 198066070 Board offline or CPU in reset status for a long

period
Alarm Property
l Description: Board offline or CPU in reset status for a long period
l Severity: Major
Probable Cause
1. The board is not in position.

2. Hardware failure.
2-64

Chapter 2 Alarm
System 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.
Handling Suggestion
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.
2.1.96 198087000 Dry contact alarm 1

Alarm Property
l Description: Dry contact alarm 1
l Severity: Unknown
Probable Cause
None
System Impact
None
Handling Suggestion
None

Alarm Property
l Severity: Unknown
2-65

Probable Cause
None
System Impact
None
Handling Suggestion
None

Alarm Property
l Severity: Unknown
Probable Cause
None
System Impact
None
Handling Suggestion
None

Alarm Property
l Severity: Unknown
Probable Cause
None
2-66

Chapter 2 Alarm
System Impact
None
Handling Suggestion
None

Alarm Property
l Severity: Unknown
Probable Cause
None
System Impact
None
Handling Suggestion
None

Alarm Property
l Severity: Unknown
Probable Cause
None
System Impact
None
2-67

Handling Suggestion
None

Alarm Property
l Severity: Unknown
Probable Cause
None
System Impact
None
Handling Suggestion
None

Alarm Property
l Severity: Unknown
Probable Cause
None
System Impact
None
Handling Suggestion
None
2-68

Chapter 2 Alarm

Alarm Property
l Severity: Unknown
Probable Cause
None
System Impact
None
Handling Suggestion
None

Alarm Property
l Severity: Unknown
Probable Cause
None
System Impact
None
Handling Suggestion
None
2-69


Alarm Property
l Severity: Unknown
Probable Cause
None
System Impact
None
Handling Suggestion
None

Alarm Property
l Severity: Unknown
Probable Cause
None
System Impact
None
Handling Suggestion
None
2-70

Chapter 2 Alarm
2.1.108 198087012 EAM dry contact 1 alarm

Alarm Property
l Description: EAM dry contact 1 alarm
l Severity: Unknown
Probable Cause
None
System Impact
None
Handling Suggestion
None

Alarm Property
l Severity: Unknown
Probable Cause
None
System Impact
None
Handling Suggestion
None
2-71


Alarm Property
l Severity: Unknown
Probable Cause
None
System Impact
None
Handling Suggestion
None

Alarm Property
l Severity: Unknown
Probable Cause
None
System Impact
None
Handling Suggestion
None
2-72

Chapter 2 Alarm

Alarm Property
l Severity: Unknown
Probable Cause
None
System Impact
None
Handling Suggestion
None

Alarm Property
l Severity: Unknown
Probable Cause
None
System Impact
None
Handling Suggestion
None
2-73


Alarm Property
l Severity: Unknown
Probable Cause
None
System Impact
None
Handling Suggestion
None

Alarm Property
l Severity: Unknown
Probable Cause
None
System Impact
None
Handling Suggestion
None
2-74

Chapter 2 Alarm
2.1.116 198087102 Power overvoltage/undervoltage alarm

Alarm Property
l Description: Power overvoltage/undervoltage alarm
l Severity: Minor
Probable Cause
CMM/CMB power voltage is out of adjustment range
System Impact
None
Handling Suggestion
please replace CMM/CMB board as soon as possible
2.1.117 198087103 13M input clock failure

Alarm Property
l Description: 13M input clock failure
l Severity: Minor
Probable Cause
CMM/CMB clock unit works abnormally
System Impact
None
Handling Suggestion
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.
2-75

2.1.118 198087106 SYNCLK clock failure

Alarm Property
l Description: SYNCLK clock failure
l Severity: Minor
Probable Cause
CMM/CMB clock unit works abnormally
System Impact
None
Handling Suggestion
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.
2.1.119 198087107 Master and slave communication link failure

Alarm Property
l Description: Master and slave communication link failure
l Severity:
Warning
Probable Cause
Standby CMM/CMB board is not powered on, or active-standby CMM/CMB board communication
error
System Impact
None
2-76

Chapter 2 Alarm
Handling Suggestion
1. Re-plug CMB board.

2. If the software has problem, upgrade it.
2.1.120 198087108 Standby CMM/CMB board not present

Alarm Property
l Description: Standby CMM/CMB board not present
l Severity:
Warning
Probable Cause
Standby CMM/CMB board is not inserted
System Impact
None
Handling Suggestion
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
2.1.121 198087109 Standby CMM/CMB board abnormal

Alarm Property
l Description: Standby CMM/CMB board abnormal
l Severity:
Warning
Probable Cause
Standby CMM/CMB board starts abnormally or not inserted properly
2-77

System Impact
None
Handling Suggestion
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.
2.1.122 198087110 CMM/CMB power failure alarm

Alarm Property
l Description: CMM/CMB power failure alarm
l Severity: Minor
Probable Cause
CMM/CMB board is power off
System Impact
None
Handling Suggestion
E1 interface will bridge-connect automatically. Replace the CMB circuit board as quickly as possible.
2.1.123 198087112 Communication link alarm between master and

slave rack (left)
Alarm Property
l Description: Communication link alarm between master and slave rack (left)
l Severity:
Warning
2-78

Chapter 2 Alarm
Probable Cause
Communication link fault between master rack and slave rack
System Impact
None
Handling Suggestion
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
2.1.124 198087113 Communication link alarm between master and

slave rack (right)
Alarm Property
l Description: Communication link alarm between master and slave rack (right)
l Severity:
Warning
Probable Cause
Communication link fault between master rack and slave rack
System Impact
None
Handling Suggestion
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
2.1.125 198087114 A interface E1 Rx carrier alarm

Alarm Property
2-79

l Description: A interface E1 Rx carrier alarm

l Severity: Minor
Probable Cause
Chip fault, clock abnormal, difference from BSC clock, or bad E1 connections, etc
System Impact
None
Handling Suggestion
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
2.1.126 198087115 A interface E1 Rx frame not synchronized

Alarm Property
l Description: A interface E1 Rx frame not synchronized
l Severity: Minor
Probable Cause
Chip fault, clock abnormal, difference from BSC clock, bad E1 connections, or CMM board not
support C/F configuration, etc
System Impact
None
Handling Suggestion
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.
2-80

Chapter 2 Alarm
2.1.127 198087120 A interface E1 remote alarm

Alarm Property
l Description: A interface E1 remote alarm
l Severity: Minor
Probable Cause
Sending line is shorted, the remote end might not receive data sent from local end
System Impact
None
Handling Suggestion
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.
2.1.128 198087121 B interface E1 Rx carrier alarm

Alarm Property
l Description: B interface E1 Rx carrier alarm
l Severity: Minor
Probable Cause
System Impact
None
Handling Suggestion
2-81

2.1.129 198087122 B interface E1 Rx frame not synchronized

Alarm Property
l Description: B interface E1 Rx frame not synchronized
l Severity: Minor
Probable Cause
System Impact
None
Handling Suggestion
2.1.130 198087127 B interface E1 remote alarm

Alarm Property
l Description: B interface E1 remote alarm
l Severity: Minor
Probable Cause
System Impact
None
2-82

Chapter 2 Alarm
Handling Suggestion
2.1.131 198087128 C interface E1 Rx carrier alarm

Alarm Property
l Description: C interface E1 Rx carrier alarm
l Severity: Minor
Probable Cause
System Impact
None
Handling Suggestion
2.1.132 198087129 C interface E1 Rx frame not synchronized

Alarm Property
l Description: C interface E1 Rx frame not synchronized
l Severity: Minor
Probable Cause
2-83

System Impact
None
Handling Suggestion
2.1.133 198087134 C interface E1 remote alarm

Alarm Property
l Description: C interface E1 remote alarm
l Severity: Minor
Probable Cause
System Impact
None
Handling Suggestion
2.1.134 198087135 D interface E1 Rx carrier alarm

Alarm Property
l Description: D interface E1 Rx carrier alarm
l Severity: Minor
2-84

Chapter 2 Alarm
Probable Cause
System Impact
None
Handling Suggestion
2.1.135 198087136 D interface E1 Rx frame not synchronized

Alarm Property
l Description: D interface E1 Rx frame not synchronized
l Severity: Minor
Probable Cause
System Impact
None
Handling Suggestion
2.1.136 198087141 D interface E1 remote alarm

Alarm Property
2-85

l Description: D interface E1 remote alarm

l Severity: Minor
Probable Cause
System Impact
None
Handling Suggestion
2.1.137 198087142 E interface E1 Rx carrier alarm

Alarm Property
l Description: E interface E1 Rx carrier alarm
l Severity: Minor
Probable Cause
System Impact
None
Handling Suggestion
2-86

Chapter 2 Alarm
2.1.138 198087143 E interface E1 Rx frame not synchronized

Alarm Property
l Description: E interface E1 Rx frame not synchronized
l Severity: Minor
Probable Cause
System Impact
None
Handling Suggestion
2.1.139 198087148 E interface E1 remote alarm

Alarm Property
l Description: E interface E1 remote alarm
l Severity: Minor
Probable Cause
System Impact
None
2-87

Handling Suggestion
2.1.140 198087149 F interface E1 Rx carrier alarm

Alarm Property
l Description: F interface E1 Rx carrier alarm
l Severity: Minor
Probable Cause
System Impact
None
Handling Suggestion
2.1.141 198087150 F interface E1 Rx frame not synchronized

Alarm Property
l Description: F interface E1 Rx frame not synchronized
l Severity: Minor
Probable Cause
2-88

Chapter 2 Alarm
System Impact
None
Handling Suggestion
2.1.142 198087153 F interface E1 Rx forward sliding indication

Alarm Property
l Description: F interface E1 Rx forward sliding indication
l Severity: Minor
Probable Cause
System Impact
None
Handling Suggestion
2.1.143 198087155 F interface E1 remote alarm

Alarm Property
l Description: F interface E1 remote alarm
l Severity: Minor
2-89

Probable Cause
System Impact
None
Handling Suggestion
2.1.144 198087156 G interface E1 Rx carrier alarm

Alarm Property
l Description: G interface E1 Rx carrier alarm
l Severity: Minor
Probable Cause
System Impact
None
Handling Suggestion
2.1.145 198087157 G interface E2 Rx frame not synchronized

Alarm Property
l Description: G interface E2 Rx frame not synchronized
l Severity: Minor
2-90

Chapter 2 Alarm
Probable Cause
System Impact
None
Handling Suggestion
2.1.146 198087162 G interface E1 remote alarm

Alarm Property
l Description: G interface E1 remote alarm
l Severity: Minor
Probable Cause
System Impact
None
Handling Suggestion
2.1.147 198087163 H interface E1 Rx carrier alarm

Alarm Property
2-91

l Description: H interface E1 Rx carrier alarm

l Severity: Minor
Probable Cause
System Impact
None
Handling Suggestion
2.1.148 198087164 H interface E3 Rx frame not synchronized

Alarm Property
l Description: H interface E3 Rx frame not synchronized
l Severity: Minor
Probable Cause
System Impact
None
Handling Suggestion
2-92

Chapter 2 Alarm
2.1.149 198087169 H interface E1 remote alarm

Alarm Property
l Description: H interface E1 remote alarm
l Severity: Minor
Probable Cause
System Impact
None
Handling Suggestion
2.1.150 198087170 Temperature alarm

Alarm Property
l Description: Temperature alarm
l Severity:
Warning
Probable Cause
Fan fault or module temperature too high
System Impact
None
2-93

Handling Suggestion
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
2.1.151 198087171 Fan absent

Alarm Property
l Description: Fan absent
l Severity:
Warning
Probable Cause
Fan not inserted or not in position
System Impact
None
Handling Suggestion
check the fan
2.1.152 198087172 Fan control board CPU alarm

Alarm Property
l Description: Fan control board CPU alarm
l Severity:
Warning
Probable Cause
CPU fault
2-94

Chapter 2 Alarm
System Impact
None
Handling Suggestion
1. check the line and correct it. 2. check the fan and replace FCM.
2.1.153 198087173 Fan alarm

Alarm Property
l Description: Fan alarm
l Severity:
Warning
Probable Cause
Fan stops rotating due to fault
System Impact
None
Handling Suggestion
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.
2.1.154 198087174 Fan temperature alarm

Alarm Property
l Description: Fan temperature alarm
l Severity:
Warning
2-95

Probable Cause
System Impact
None
Handling Suggestion
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.
2.1.155 198087175 Fan 1 alarm

Alarm Property
l Description: Fan 1 alarm
l Severity:
Warning
Probable Cause
System Impact
None
Handling Suggestion
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
2.1.156 198087176 Fan 2 alarm

Alarm Property
2-96

Chapter 2 Alarm
l Description: Fan 2 alarm

l Severity:
Warning
Probable Cause
System Impact
None
Handling Suggestion
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
2.1.157 198087177 Fan control board alarm

Alarm Property
l Description: Fan control board alarm
l Severity:
Warning
Probable Cause
System Impact
None
Handling Suggestion
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.
2-97

2.1.158 198087178 LNA alarm

Alarm Property
l Description: LNA alarm
l Severity: Minor
Probable Cause
LNA current exceeds by 30%
System Impact
None
Handling Suggestion
please replace AEM module as soon as possible.
2.1.159 198087179 Tower amplifier power alarm

Alarm Property
l Description: Tower amplifier power alarm
l Severity:
Warning
Probable Cause
AEM tower amplifier power alarm
System Impact
None
Handling Suggestion
please replace Tower Amplifier module or AEM module as soon as possible.
2-98

Chapter 2 Alarm
2.1.160 198087180 SWR of AEM HYCOM minor alarm

Alarm Property
l Description: SWR of AEM HYCOM minor alarm
l Severity: Minor
Probable Cause
Combiner SWR 1.5 alarm
System Impact
None
Handling Suggestion
keep on observing.if normal work isn't influenced, don't replace AEM module.
2.1.161 198087181 SWR of AEM HYCOM major alarm

Alarm Property
l Description: SWR of AEM HYCOM major alarm
l Severity: Major
Probable Cause
Combiner SWR 3.0 alarm
System Impact
None
Handling Suggestion
please replace AEM and reset TRM which connects with this AEM.
2-99

2.1.162 198087182 AEM power alarm(BTS V2)

Alarm Property
l Description: AEM power alarm(BTS V2)
l Severity: Major
Probable Cause
AEM power alarm
System Impact
None
Handling Suggestion
please replace AEM module as soon as possible.
2.1.163 198087183 AEM type alarm(BTS V2)

Alarm Property
l Description: AEM type alarm(BTS V2)
l Severity: Major
Probable Cause
AEM type alarm
System Impact
None
Handling Suggestion
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.
2-100

Chapter 2 Alarm
2.1.164 198087184 AEM absent(BTS V2)

Alarm Property
l Description: AEM absent(BTS V2)
l Severity: Major
Probable Cause
AEM not-in-position alarm
System Impact
None
Handling Suggestion
please replace AEM and reset TRM which connects with this AEM.
2.1.165 198087185 AEM power alarm

Alarm Property
l Description: AEM power alarm
l Severity: Major
Probable Cause
AEM power alarm
System Impact
None
2-101

Handling Suggestion
(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.
2.1.166 198087186 LNA0 alarm

Alarm Property
l Description: LNA0 alarm
l Severity: Minor
Probable Cause
LNA0 current exceeds by 30%
System Impact
None
Handling Suggestion
(3)Replace CDU.
2.1.167 198087187 LNA1 alarm

Alarm Property
l Description: LNA1 alarm
2-102

Chapter 2 Alarm
l Severity: Minor
Probable Cause
LNA1 current exceeds by 30%
System Impact
None
Handling Suggestion
(3)Replace CDU.
2.1.168 198087188 Tower Amplifier0 power alarm

Alarm Property
l Description: Tower Amplifier0 power alarm
l Severity:
Warning
Probable Cause
AEM tower amplifier 0 power alarm
System Impact
None
2-103

Handling Suggestion
(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 whcther PA goes wrong.
(4)Replace CDU and reset TRX connecting with it.
2.1.169 198087189 Tower Amplifier1 power alarm

Alarm Property
l Description: Tower Amplifier1 power alarm
l Severity:
Warning
Probable Cause
AEM tower amplifier 1 power alarm
System Impact
None
Handling Suggestion
(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 whcther PA goes wrong.
2-104

Chapter 2 Alarm
2.1.170 198087190 SWR of AEM HYCOM minor alarm

Alarm Property
l Description: SWR of AEM HYCOM minor alarm
l Severity: Minor
Probable Cause
Combiner SWR minor alarm
System Impact
None
Handling Suggestion
(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
are bent. If yes, replace the rear board. Check whether the alarm cable connector of CDU is loose
or off. If yes, fastern it and re-power it on. Three minutes after the TRX is running, check whether
the alarm disappears.
2-105

2.1.171 198087191 SWR of AEM HYCOM major alarm

Alarm Property
l Description: SWR of AEM HYCOM major alarm
l Severity: Major
Probable Cause
Combiner SWR major alarm
System Impact
None
Handling Suggestion
(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, fastern it and re-power it on. Three minutes after the TRX is running, check whether
2.1.172 198087192 AEM type alarm

Alarm Property
l Description: AEM type alarm
l Severity: Major
2-106

Chapter 2 Alarm
Probable Cause
AEM type alarm
System Impact
None
Handling Suggestion
(1)Check whether there is PA temperature alarm or fan environment termperature alarm on the
(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.
2.1.173 198087193 AEM Not-in-position alarm

Alarm Property
l Description: AEM Not-in-position alarm
l Severity: Major
Probable Cause
AEM not-in-position alarm
System Impact
None
2-107

Handling Suggestion
(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.
2.1.174 198087198 Uplink of ADC chip initialization failure

Alarm Property
l Description: Uplink of ADC chip initialization failure
l Severity: Minor
Probable Cause
Uplink ADC chip initialization failure
System Impact
None
Handling Suggestion
1. Reset this module in order to work normally.

2. if reset is of no effect , please replace this module at once.
2.1.175 198087200 CIP resource can't be used

Alarm Property
2-108

Chapter 2 Alarm
l Description: CIP resource can't be used

l Severity: Minor
Probable Cause
Uplink/downlink loop data demodulation failure
System Impact
None
Handling Suggestion
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.
2.1.176 198087201 Uplink failure

Alarm Property
l Description: Uplink failure
l Severity: Minor
Probable Cause
Error in uplink data receiving
System Impact
None
Handling Suggestion
1.Reset this module in order to work normally.

2. if reset is of no effect, please replace this module at once.
2.1.177 198087207 Watchdog of FUC overflow

Alarm Property
2-109

l Description: Watchdog of FUC overflow

l Severity: Minor
Probable Cause
FUC program has no response temporarily
System Impact
None
Handling Suggestion
user can reset TPU to solve this problem. If it isn't solved, please replace TRM module.
2.1.178 198087216 Cell configuration parameter mismatch(BTS V2)

Alarm Property
l Description: Cell configuration parameter mismatch(BTS V2)
l Severity: Minor
Probable 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
System Impact
None
Handling Suggestion
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.
2-110

Chapter 2 Alarm
2.1.179 198087221 Communication link between CMM and FUC

break(BTS V2)
Alarm Property
l Description: Communication link between CMM and FUC break(BTS V2)
l Severity: Minor
Probable Cause
HDLC link between CMM and TPU breaks, CMM hardware error, etc
System Impact
None
Handling Suggestion
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 replact it, if software has problems please upgrade software version.
2.1.180 198087224 Watchdog of TPU CIP overflow

Alarm Property
l Description: Watchdog of TPU CIP overflow
l Severity: Minor
Probable Cause
DSP program of demodulation module has no response temporarily
2-111

System Impact
None
Handling Suggestion
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.
2.1.181 198087225 Software version of CIP mismatch

Alarm Property
l Description: Software version of CIP mismatch
l Severity: Minor
Probable Cause
CIP software version load error. If one of the carriers is configured as BCCH, then the whole cell
can not work normally.
System Impact
None
Handling Suggestion
reset TRM, if it is of no effect, please replace TRM module.
2.1.182 198087226 Clock alarm for TPU and CMM

Alarm Property
l Description: Clock alarm for TPU and CMM
l Severity: Major
Probable Cause
Clock between TPU and CMM is disconnected
2-112

Chapter 2 Alarm
System Impact
None
Handling Suggestion
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.
2.1.183 198087228 TPU frame No. alarm

Alarm Property
l Description: TPU frame No. alarm
l Severity: Minor
Probable Cause
Frame clock FCLK has problem, upper-level frame number synchronization source CMM has problem
System Impact
None
Handling Suggestion
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
2.1.184 198087229 TPU CHP DSP0 initialization failure

Alarm Property
l Description: TPU CHP DSP0 initialization failure
l Severity: Minor
2-113

Probable Cause
DSP software or hardware error
System Impact
None
Handling Suggestion
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.
2.1.185 198087243 Cell configuration parameter mismatch

Alarm Property
l Description: Cell configuration parameter mismatch
l Severity: Minor
Probable Cause
Cell parameter configuration is incorrect or conflicts with channel parameters and CIP parameter
configuration
System Impact
None
Handling Suggestion
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.
2-114

Chapter 2 Alarm
2.1.186 198087247 HDLC communication link between CMB and

FUC broken
Alarm Property
l Description: HDLC communication link between CMB and FUC broken
l Severity: Minor
Probable Cause
HDLC link between CMB and TPU breaks, CMB hardware error, etc
System Impact
None
Handling Suggestion
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 currect. 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.
2.1.187 198087253 FU fram No error alarm

Alarm Property
l Description: FU fram No error alarm
l Severity: Minor
Probable Cause
Frame clock FCLK has problem, upper-level frame number synchronization source CMB has problem
2-115

System Impact
None
Handling Suggestion
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.
2.1.188 198087254 Rx PLL1 unlock

Alarm Property
l Description: Rx PLL1 unlock
l Severity: Minor
Probable Cause
Clock signal is unstable or TRM Phase-Locked Loop (PLL) fault
System Impact
None
Handling Suggestion
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.
2.1.189 198087255 Rx PLL2 unlock

Alarm Property
l Description: Rx PLL2 unlock
l Severity: Minor
2-116

Chapter 2 Alarm
Probable Cause
System Impact
None
Handling Suggestion
2.1.190 198087256 Tx PLL1 unlock

Alarm Property
l Description: Tx PLL1 unlock
l Severity: Minor
Probable Cause
System Impact
None
Handling Suggestion
2-117

2.1.191 198087257 Tx PLL2 unlock

Alarm Property
l Description: Tx PLL2 unlock
l Severity: Minor
Probable Cause
System Impact
None
Handling Suggestion
2.1.192 198087258 52M referenced clock PLL unlock

Alarm Property
l Description: 52M referenced clock PLL unlock
l Severity: Minor
Probable Cause
System Impact
None
2-118

Chapter 2 Alarm
Handling Suggestion
2.1.193 198087259 Tx IF PLL unlock

Alarm Property
l Description: Tx IF PLL unlock
l Severity: Minor
Probable Cause
System Impact
None
Handling Suggestion
2.1.194 198087260 EEPROM resource can't be used

Alarm Property
l Description: EEPROM resource can't be used
l Severity: Minor
Probable Cause
EEPROM fault
2-119

System Impact
None
Handling Suggestion
please replace TRM module.
2.1.195 198087261 FPGA interface failure

Alarm Property
l Description: FPGA interface failure
l Severity: Minor
Probable Cause
Communication between DSP and FPGA interface breaks
System Impact
None
Handling Suggestion
please replace TRM module.
2.1.196 198087262 PA VSWR alarm(BTS V2)

Alarm Property
l Description: PA VSWR alarm(BTS V2)
l Severity: Minor
Probable Cause
Direct reason: reverse power is too high. Possible reason: open circuit or high resistance exists in
output end of PA
2-120

Chapter 2 Alarm
System Impact
None
Handling Suggestion
1.Check the connection of PA output with cable.

2.If alarm still exists, please replace TRM module as soon as possible.
2.1.197 198087263 PA overtemperature minor alarm(BTS V2)

Alarm Property
l Description: PA overtemperature minor alarm(BTS V2)
l Severity:
Warning
Probable 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
System Impact
None
Handling Suggestion
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.
2.1.198 198087264 PA overtemperature major alarm(BTS V2)

Alarm Property
l Description: PA overtemperature major alarm(BTS V2)
l Severity: Minor
2-121

Probable Cause
System Impact
None
Handling Suggestion
still exist then may be the detection electric circuit breakdown, should replace the TRM/DTRM
module in time.
2.1.199 198087265 PA output power alarm

Alarm Property
l Description: PA output power alarm
l Severity: Minor
Probable 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
System Impact
None
Handling Suggestion
1.Reset TRM and observe.

2. if alarm exists, replace TRM module as soon as possible.
2.1.200 198087266 PA power overvoltage

Alarm Property
l Description: PA power overvoltage
2-122

Chapter 2 Alarm
l Severity: Minor
Probable Cause
PA power overvoltage
System Impact
None
Handling Suggestion
check the check circuit of PA.if it has problem, please replace TRM.
2.1.201 198087267 PA power lower voltage

Alarm Property
l Description: PA power lower voltage
l Severity: Minor
Probable Cause
PA power undervoltage
System Impact
None
Handling Suggestion
2.1.202 198087268 Downlink checksum error of DLRC_AL1

Alarm Property
l Description: Downlink checksum error of DLRC_AL1
l Severity: Minor
2-123

Probable Cause
Interference exists on link between CHP and modulation module
System Impact
None
Handling Suggestion
1. Check the signal and time-sequence between CHP and modulation module.
2. if the problem still exists, please replace TRM in time.
2.1.203 198087269 DUC chip initialization failure

Alarm Property
l Description: DUC chip initialization failure
l Severity: Minor
Probable Cause
DUC chip unavailable
System Impact
None
Handling Suggestion
please replace this TRM module.
2.1.204 198087270 80w PA VSWR alarm

Alarm Property
l Description: 80w PA VSWR alarm
l Severity: Minor
2-124

Chapter 2 Alarm
Probable Cause
Direct reason: Reverse power is too high; Possible reason: Open circuit or high resistance exists at
the output end of PA
System Impact
None
Handling Suggestion
1.Check the connection of PA output with cable.
2.If alarm still exists, please replace TRM module as soon as possible.
2.1.205 198087271 80w PA overtemperature

Alarm Property
l Description: 80w PA overtemperature
l Severity:
Warning
Probable Cause
System Impact
None
Handling Suggestion
2.1.206 198087272 80w PA overtemperature major alarm

Alarm Property
l Description: 80w PA overtemperature major alarm
2-125

l Severity: Minor
Probable Cause
System Impact
None
Handling Suggestion
still exist then may be the detection electric circuit breakdown, should replace the TRM/DTRM
module in time.
2.1.207 198087273 80w PA output power alarm

Alarm Property
l Description: 80w PA output power alarm
l Severity: Minor
Probable 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
System Impact
None
Handling Suggestion
1.Reset TRM and observe.

2. if alarm exists, replace TRM module as soon as possible.
2-126

Chapter 2 Alarm
2.1.208 198087274 80w PA power overvoltage

Alarm Property
l Description: 80w PA power overvoltage
l Severity: Minor
Probable Cause
System Impact
None
Handling Suggestion
2.1.209 198087275 80w PA power lower voltage

Alarm Property
l Description: 80w PA power lower voltage
l Severity: Minor
Probable Cause
System Impact
None
Handling Suggestion
check the check circuit of PA.if it has problem, please replace TRM
2-127

2.1.210 198087276 80w PA absent

Alarm Property
l Description: 80w PA absent
l Severity: Minor
Probable Cause
PA not in position
System Impact
None
Handling Suggestion
2.1.211 198087277 TXIF unlock

Alarm Property
l Description: TXIF unlock
l Severity: Minor
Probable Cause
Clock signal is unstable or DTRU Phase-Locked Loop (PLL) fault
System Impact
None
2-128

Chapter 2 Alarm
Handling Suggestion
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 bnard, 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.
2.1.212 198087278 TPF unlock

Alarm Property
l Description: TPF unlock
l Severity: Minor
Probable Cause
System Impact
None
Handling Suggestion
2.1.213 198087279 TXRF unlock

Alarm Property
l Description: TXRF unlock
l Severity: Minor
2-129

Probable Cause
System Impact
None
Handling Suggestion
2.1.214 198087280 RXRF unlock

Alarm Property
l Description: RXRF unlock
l Severity: Minor
Probable Cause
System Impact
None
Handling Suggestion
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 possibile that local oscillator have fault, and should
replace the DTRM in time.
2-130

Chapter 2 Alarm
2.1.215 198087281 13 MHz clock lost

Alarm Property
l Description: 13 MHz clock lost
l Severity: Minor
Probable Cause
13 MHz clock receiving is abnormal, 13 MHz clock unit works abnormally
System Impact
None
Handling Suggestion
2.1.216 198087282 60 ms clock lost

Alarm Property
l Description: 60 ms clock lost
l Severity: Minor
Probable Cause
60 ms synchronization clock receiving is abnormal, 60 ms synchronization clock unit works abnormally
System Impact
None
2-131

Handling Suggestion
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 wheather the CMB of standby racks work normally. If it is not normal, recover CMB working
status to check whether the alarm is recovered.
2.1.217 198087285 52 MHz clock lost

Alarm Property
l Description: 52 MHz clock lost
l Severity: Minor
Probable Cause
RF board 52 MHz clock receiving is abnormal, RF board 52 MHz clock unit works abnormally
System Impact
None
Handling Suggestion
2.1.218 198087288 PA power overvoltage alarm

Alarm Property
l Description: PA power overvoltage alarm
l Severity: Minor
2-132

Chapter 2 Alarm
Probable Cause
System Impact
None
Handling Suggestion
Check whether the PA examination electric circuit break down or not, if have the fault, should replace
the DTRM in time
2.1.219 198087289 PA power undervoltage alarm

Alarm Property
l Description: PA power undervoltage alarm
l Severity: Minor
Probable Cause
System Impact
None
Handling Suggestion
Check whether the PA examination electric circuit break down or not, if have the fault, should replace
the DTRM in time
2.1.220 198087290 PA VSWR alarm

Alarm Property
l Description: PA VSWR alarm
l Severity: Minor
2-133

Probable Cause
Direct reason: reverse power is too high. Possible reason: open circuit or high resistance exists in
output end of PA
System Impact
None
Handling Suggestion
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.
2.1.221 198087291 PA temperature minor alarm

Alarm Property
l Description: PA temperature minor alarm
l Severity:
Warning
Probable Cause
System Impact
None
Handling Suggestion
2.1.222 198087292 PA temperature major alarm

Alarm Property
2-134

Chapter 2 Alarm
l Description: PA temperature major alarm

l Severity: Minor
Probable Cause
System Impact
None
Handling Suggestion
still exist then may be the detection electric circuit breakdown, should replace the DTRM module in
time.
2.1.223 198087293 PA forward power(3db) alarm

Alarm Property
l Description: PA forward power(3db) alarm
l Severity: Minor
Probable 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
System Impact
None
Handling Suggestion
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
2-135

2.1.224 198087294 RTU power alarm

Alarm Property
l Description: RTU power alarm
l Severity: Major
Probable Cause
RTU power module failure
System Impact
None
Handling Suggestion
Replace the RTU circuit board as quickly as possible
2.1.225 198087295 RTU power temperature alarm

Alarm Property
l Description: RTU power temperature alarm
l Severity: Minor
Probable Cause
RTU power module overheated
System Impact
None
Handling Suggestion
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.
2-136

Chapter 2 Alarm
2.1.226 198087296 RTU power output overvoltage alarm

Alarm Property
l Description: RTU power output overvoltage alarm
l Severity: Major
Probable Cause
RTU power output overvoltage
System Impact
None
Handling Suggestion
2.1.227 198087297 RTU power input failure alarm

Alarm Property
l Description: RTU power input failure alarm
l Severity: Major
Probable Cause
RTU power input failure
System Impact
None
Handling Suggestion
2-137

2.1.228 198087298 IQ calibration parameters abnormal alarm

Alarm Property
l Description: IQ calibration parameters abnormal alarm
l Severity: Major
Probable Cause
IQ calibration parameter abnormal
System Impact
None
Handling Suggestion
Replace the RTU circuit board as quickly as possible.
2.1.229 198087299 EAM heat exchanger alarm

Alarm Property
l Description: EAM heat exchanger alarm
l Severity:
Warning
Probable Cause
Heat exchanger alarm, reported by dry contact of heat exchanger
System Impact
None
Handling Suggestion
Perform on-site check immediately to find fault cause and replace the heat exchanger.
2-138

Chapter 2 Alarm
2.1.230 198087300 EAM TRX layer fan-4 alarm

Alarm Property
l Description: EAM TRX layer fan-4 alarm
l Severity:
Warning
Probable Cause
CMB0 heater wrong
System Impact
None
Handling Suggestion
replace CMB0 heater in time
2.1.231 198087301 EAM AEM layer axis-flow fan alarm

Alarm Property
l Description: EAM AEM layer axis-flow fan alarm
l Severity:
Warning
Probable Cause
CMB1 heater wrong
System Impact
None
Handling Suggestion
replace CMB1 heater in time
2-139

2.1.232 198087302 EAM smoke alarm

Alarm Property
l Description: EAM smoke alarm
l Severity: Minor
Probable Cause
Equipment smoke alarm
System Impact
None
Handling Suggestion
Perform on-site check immediately to find fault cause and handle the fault.
2.1.233 198087303 EAM waterproof alarm

Alarm Property
l Description: EAM waterproof alarm
l Severity: Minor
Probable Cause
Equipment water alarm
System Impact
None
Handling Suggestion
2-140

Chapter 2 Alarm
2.1.234 198087304 EAM lightning protection alarm

Alarm Property
l Description: EAM lightning protection alarm
l Severity: Minor
Probable Cause
Lightning protector failure alarm
System Impact
None
Handling Suggestion
Perform on-site check immediately to find fault cause and replace the lightning protector.
2.1.235 198087305 EAM backdoor access control alarm

Alarm Property
l Description: EAM backdoor access control alarm
l Severity:
Warning
Probable Cause
Alarm of back door being opened
System Impact
None
Handling Suggestion
Perform on-site check immediately to find fault cause and close the back door.
2-141

2.1.236 198087306 EAM frontdoor access control alarm

Alarm Property
l Description: EAM frontdoor access control alarm
l Severity:
Warning
Probable Cause
Alarm of front door being opened
System Impact
None
Handling Suggestion
Perform on-site check immediately to find fault cause and close the front door.
2.1.237 198087307 EAM PWR monitoring unit alarm

Alarm Property
l Description: EAM PWR monitoring unit alarm
l Severity:
Warning
Probable Cause
PWR monitoring unit alarm
System Impact
None
Handling Suggestion
Perform on-site check immediately to find fault cause.
2-142

Chapter 2 Alarm
2.1.238 198087308 EAM heat exchanger electric heater alarm

Alarm Property
l Description: EAM heat exchanger electric heater alarm
l Severity: Minor
Probable Cause
FIB heater alarm
System Impact
None
Handling Suggestion
replace FIB heater in time
2.1.239 198087309 EAM heat exchanger control board alarm

Alarm Property
l Description: EAM heat exchanger control board alarm
l Severity: Minor
Probable Cause
Heat exchanger control board alarm
System Impact
None
Handling Suggestion
2-143

2.1.240 198087310 EAM heat exchanger external circulation fan 2

alarm
Alarm Property
l Description: EAM heat exchanger external circulation fan 2 alarm
l Severity: Minor
Probable Cause
Heat exchanger external circulation fan 2 alarm
System Impact
None
Handling Suggestion
2.1.241 198087311 EAM heat exchanger external circulation fan 1

alarm
Alarm Property
l Description: EAM heat exchanger external circulation fan 1 alarm
l Severity: Minor
Probable Cause
Heat exchanger external circulation fan 1 alarm
System Impact
None
Handling Suggestion
2-144

Chapter 2 Alarm
2.1.242 198087312 EAM heat exchanger internal circulation fan 2

alarm
Alarm Property
l Description: EAM heat exchanger internal circulation fan 2 alarm
l Severity: Major
Probable Cause
Heat exchanger internal circulation fan 2 alarm
System Impact
None
Handling Suggestion
2.1.243 198087313 EAM heat exchanger internal circulation fan 1

alarm
Alarm Property
l Description: EAM heat exchanger internal circulation fan 1 alarm
l Severity: Major
Probable Cause
Heat exchanger internal circulation fan 1 alarm
System Impact
None
Handling Suggestion
2-145

2.1.244 198087314 EAM heat exchanger 485 communication alarm

Alarm Property
l Description: EAM heat exchanger 485 communication alarm
l Severity: Minor
Probable Cause
Communication break between EAM and heat exchanger
System Impact
None
Handling Suggestion
2.1.245 198087315 EAM temperature alarm

Alarm Property
l Description: EAM temperature alarm
l Severity: Minor
Probable Cause
Equipment internal environment temperature too high
System Impact
None
Handling Suggestion
2-146

Chapter 2 Alarm
2.1.246 198087316 EAM TRX layer mixed-flow fan 1 alarm

Alarm Property
l Description: EAM TRX layer mixed-flow fan 1 alarm
l Severity: Minor
Probable Cause
Mixed-flow fan 1 damage alarm
System Impact
None
Handling Suggestion
Perform on-site check immediately to find fault cause and replace the fan.

Alarm Property
l Severity: Minor
Probable Cause
System Impact
None
Handling Suggestion
2-147


Alarm Property
l Severity: Minor
Probable Cause
System Impact
None
Handling Suggestion
2.1.249 198087319 Communication broken between EAM and CMB

Alarm Property
l Description: Communication broken between EAM and CMB
l Severity: Minor
Probable Cause
Communication break between EAM and CMB
System Impact
None
Handling Suggestion
2-148

Chapter 2 Alarm
2.1.250 198087320 Power undervoltage alarm

Alarm Property
l Description: Power undervoltage alarm
l Severity: Major
Probable Cause
Power voltage is lower than normal
System Impact
None
Handling Suggestion
Restore external power supply as soon as possible
2.1.251 198087321 Inner fan 2 alarm (for M8202)

Alarm Property
l Description: Inner fan 2 alarm (for M8202)
l Severity:
Warning
Probable Cause
System Impact
None
Handling Suggestion
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.
2-149

2.1.252 198087322 Inner fan 1 alarm (for M8202)

Alarm Property
l Description: Inner fan 1 alarm (for M8202)
l Severity:
Warning
Probable Cause
System Impact
None
Handling Suggestion

2. Check the fan and maintain the fault; 3. Check the collection system of the dTPB board and
replace the wrong one.
2.1.253 198087323 Outer fan 2 and fan 4 alarm (for M8202)

Alarm Property
l Description: Outer fan 2 and fan 4 alarm (for M8202)
l Severity:
Warning
Probable Cause
System Impact
None
2-150

Chapter 2 Alarm
Handling Suggestion

2. Check the fan and maintain the fault;
3. Check the collection system of the dTPB board and replace the wrong one.
2.1.254 198087324 Outer fan 1 and fan 3 alarm (for M8202)

Alarm Property
l Description: Outer fan 1 and fan 3 alarm (for M8202)
l Severity:
Warning
Probable Cause
System Impact
None
Handling Suggestion

2. Check the fan and maintain the fault;
3. Check the collection system of the dTPB board and replace the wrong one.
2.1.255 198087325 Rack temperature minor alarm

Alarm Property
l Description: Rack temperature minor alarm
l Severity:
Warning
Probable Cause
2-151

System Impact
None
Handling Suggestion
Check the environment temperature, if the temperature is normal, keep on observing while other
modules works normally, otherwise, improve the equipment working conditions.
2.1.256 198087326 Rack temperature major alarm

Alarm Property
l Description: Rack temperature major alarm
l Severity: Minor
Probable Cause
System Impact
None
Handling Suggestion
Check the environment temperature, if the temperature is normal, keep on observing while other
modules works normally, otherwise, improve the equipment working conditions.
2.1.257 198087327 Layer 3 fan 1 alarm (for M8206)

Alarm Property
l Description: Layer 3 fan 1 alarm (for M8206)
l Severity:
Warning
Probable Cause
The failure of fans
2-152

Chapter 2 Alarm
System Impact
None
Handling Suggestion
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 Property
l Severity:
Warning
Probable Cause
The failure of fans
System Impact
None
Handling Suggestion

2. Examin the fans;

Alarm Property
l Severity:
Warning
2-153

Probable Cause
The failure of fans
System Impact
None
Handling Suggestion
2. Examin the fans;

Alarm Property
l Severity:
Warning
Probable Cause
The failure of fans
System Impact
None
Handling Suggestion
2. Examin the fans;

Alarm Property
l Severity:
2-154

Chapter 2 Alarm
Warning
Probable Cause
The failure of fans
System Impact
None
Handling Suggestion

2. Examin the fans;

Alarm Property
l Severity:
Warning
Probable Cause
The failure of fans
System Impact
None
Handling Suggestion

2. Examin the fans;
2-155


Alarm Property
l Severity:
Warning
Probable Cause
The failure of fans
System Impact
None
Handling Suggestion

2. Examin the fans;

Alarm Property
l Severity:
Warning
Probable Cause
The failure of fans
System Impact
None
2-156

Chapter 2 Alarm
Handling Suggestion

2. Examin the fans;

Alarm Property
l Severity:
Warning
Probable Cause
The failure of fans
System Impact
None
Handling Suggestion
1. Examin the error-detection circuit;

2. Examin the fans;
2.1.266 198087340 FR device failure

Alarm Property
l Description: FR device failure
l Severity: Minor
Probable Cause
Detected N392 errors in the last N393 STATUS ENQUIRY events
2-157

System Impact
BRCH of Gb port is not expedite
Handling Suggestion
1.Check whether the alarm of E1 port corresponding to BRCH persistent.If so, check the transmit
device and deal with the transmit alarm.
2.Do self-loop checking to the local terminal device and ensure it work correct.if not, replace E1 line,
and watch whether the alarm restored;if the local terminal device work well, then contact SGSN
surfaceman to self-loop the mate terminal device, also should ensure mate terminal device works
well.if mate terminal device has no fault, turn to step No.3
3.Check the configuration both BSC and SGSN, and ensure the E1 fram of them have the same
format.
4.Check the parameters configures could be agreed with SGSN.if not, change the configurations
untill they are same.
5.Replace the GIPB board, then watch whether the alarm could be restored.
2.1.267 198087341 FR congestion

Alarm Property
l Description: FR congestion
l Severity: Minor
Probable Cause
In case of an intermediate Frame Relay network, the number of a frame with a BECN bit set to 1 is
more than or equal to the number of a frame with a BECN bit set to 0 in T interval.
System Impact
Quality of PS service for Part of user will decline
Handling Suggestion
Increase the BRCH line or BRCH time-slot
2.1.268 198087344 MSC overload control alarm at FUC mode

Alarm Property
2-158

Chapter 2 Alarm
l Description: MSC overload control alarm at FUC mode

l Severity: Minor
Probable Cause
MSC overload control at FUC mode
System Impact
Some users fail to gain access.
Handling Suggestion
BSC can implement flow control automatically. Observe the alarm without further operation.
2.1.269 198087345 CPU overload control alarm at FUC mode

Alarm Property
l Description: CPU overload control alarm at FUC mode
l Severity: Minor
Probable Cause
The CPU load exceeds the flow control threshold in module parameter setting.
System Impact
Handling Suggestion
1. On NMS fault management interface, check the alarm details, which give the flow control level. If
the flow control level is 3 or lower than 3, observe three minutes. Wait for the alarm to be eliminated.
2. Block some cells through dynamic data management to prevent CPU load from increasing. After
the alarm is eliminated, unblock the related cells.
2-159

2.1.270 198087346 Signaling point congestion control alarm at FUC

mode
Alarm Property
l Description: Signaling point congestion control alarm at FUC mode
l Severity: Minor
Probable Cause
MSC sends the signaling congestion message. BSC starts FUC flow control.
System Impact
Handling Suggestion
2.1.271 198087347 MSC overload control alarm at SYS mode

Alarm Property
l Description: MSC overload control alarm at SYS mode
l Severity: Minor
Probable Cause
MSC sends the overload message. BSC starts system message flow control.
System Impact
Handling Suggestion
2-160

Chapter 2 Alarm
2.1.272 198087348 CPU overload control alarm at SYS mode

Alarm Property
l Description: CPU overload control alarm at SYS mode
l Severity: Minor
Probable Cause
The excessive traffic causes the CPU load to exceed the flow control threshold in module parameter
setting.
System Impact
The system automatically initiates flow control management and thus some users cannot gain access.
If the traffic is still excessive after flow control, the CPU load will grow further.
Handling Suggestion
2. Block some cells through dynamic data management to prohibit some users to access. After the
alarm is eliminated, restore the configuration or unblock the related cells.
2.1.273 198087349 Signaling point congestion control alarm at SYS

mode
Alarm Property
l Description: Signaling point congestion control alarm at SYS mode
l Severity: Minor
Probable Cause
The excessive traffic causes the MSC to send signaling congestion message. BSC starts system
message flow control.
2-161

System Impact
The system automatically initiates flow control management and thus some users cannot gain
access. If the traffic is still excessive after flow control, signaling at A interface are blocked and the
service is interrupted.
Handling Suggestion
2. Block some cells through dynamic data management to prohibit some users to access. After the
2.1.274 198087350 CCCH overload control

Alarm Property
l Description: CCCH overload control
l Severity: Minor
Probable Cause
Too many MSs request to gain access on CS CCH.
System Impact
The system automatically initiates flow control management, causing some MSs under this cell to
fail to access CS services.
Handling Suggestion
the flow control level is 8 or lower than 8, observe ten minutes. Wait for the alarm to be eliminated.
2. If the alarm occurs frequently, add CS CCCH to the channel information under BTS configuration
or expand the capacity of the overloaded site or share the traffic.
2.1.275 198087351 PCCCH overload control

Alarm Property
l Description: PCCCH overload control
l Severity: Minor
2-162

Chapter 2 Alarm
Probable Cause
Too many MSs request to gain access on PS CCH.
System Impact
The system automatically initiates flow control management, causing some MSs under this cell to
fail to access PS services.
Handling Suggestion
the flow control level is 8 or lower than 8, observe ten minutes. Wait for the alarm to be eliminated.
2. If the alarm occurs frequently, add PS CCCH to the channel information under BTS configuration
or expand the capacity of the overloaded site or share the traffic.
2.1.276 198087352 NSVC's E1 failure alarm

Alarm Property
l Description: NSVC's E1 failure alarm
l Severity: Minor
Probable Cause
Continously no NS Alive Ack for NSAliveMax times during NS Alive procedure
System Impact
For single NSVC link configuration, the PS service is interrupted. For multi-NSVC link configuration,
the bandwidth is decreased.
Handling Suggestion
1. On NMS fault management interface, check if alarms related to FR device failure exist. If yes,
follow the suggestions for handling the related alarms.
198087340 FR Device Failure
2. On NMS configuration management interface, check if NSVC configuration parameters are
consistent with those on SGSN.
2-163

2.1.277 198087391 FCU power undervoltage alarm

Alarm Property
l Description: FCU power undervoltage alarm
l Severity: Major
Probable Cause
+12V power undervoltage
System Impact
None
Handling Suggestion
Replace the FCU as soon as possible
2.1.278 198087403 The clock alarm about transmission of CCI

board Abis-E1
Alarm Property
l Description: The clock alarm about transmission of CCI board Abis-E1
l Severity: Minor
Probable Cause
The clock alarm about transmission of CCI board Abis-E1 is lost
System Impact
None
Handling Suggestion
Exam the Abis E1 interface.
2-164

Chapter 2 Alarm
2.1.279 198087404 The local working clock alarm of CCI board

Alarm Property
l Description: The local working clock alarm of CCI board
l Severity: Minor
Probable Cause
The local working clock error
System Impact
None
Handling Suggestion
Switch to the slave circuit board as quickly as possible. If Necessarily, to replace the CCI circuit board.
2.1.280 198087405 The clock alarm about transmission of CCI

board 13M
Alarm Property
l Description: The clock alarm about transmission of CCI board 13M
l Severity: Minor
Probable Cause
The clock alarm about transmission of CCI board is lost
System Impact
None
Handling Suggestion
Exam the contrast source, or replace the CCI circuit board.
2-165

2.1.281 198087406 CCI opposite board alarm

Alarm Property
l Description: CCI opposite board alarm
l Severity:
Warning
Probable Cause
there is no CCI opposite board or clock failure
System Impact
None
Handling Suggestion
Replace the CCI circuit board.
2.1.282 198087407 IQ FPGA internal clock alarm

Alarm Property
l Description: IQ FPGA internal clock alarm
l Severity: Minor
Probable Cause
IQ FPGA internal source lost of clock
System Impact
None
Handling Suggestion
Detect whether the CLK FPGA is running.
2-166

Chapter 2 Alarm
2.1.283 198087408 IQ FPGA light interface alarm

Alarm Property
l Description: IQ FPGA light interface alarm
l Severity: Minor
Probable Cause
IQ FPGA light interface abnormal
System Impact
None
Handling Suggestion
Replace the optical module or optical fiber.
2.1.284 198087409 IQ FPGA LVDS interface alarm

Alarm Property
l Description: IQ FPGA LVDS interface alarm
l Severity: Minor
Probable Cause
LVDS interface abnormal
System Impact
None
Handling Suggestion
Exam the backboard and SERDES chip in the relevant GBP board.
2-167

2.1.285 198087410 IQ FPGA internal data alarm

Alarm Property
l Description: IQ FPGA internal data alarm
l Severity: Minor
Probable Cause
the format of internal data is abnormal
System Impact
None
Handling Suggestion
Find out the cause of the data format mistake.
2.1.286 198087411 13M,61.44M clock lost alarm

Alarm Property
l Description: 13M,61.44M clock lost alarm
l Severity: Minor
Probable Cause
clock lost
System Impact
None
Handling Suggestion
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.
2-168

Chapter 2 Alarm
2.1.287 198087412 60ms clock lost alarm

Alarm Property
l Description: 60ms clock lost alarm
l Severity: Minor
Probable Cause
FR or FN error
System Impact
None
Handling Suggestion
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.
2.1.288 198087413 26MHz and 52MHz lost of clock alarm

Alarm Property
l Description: 26MHz and 52MHz lost of clock alarm
l Severity: Minor
Probable Cause
the loop of clock is unlock
System Impact
None
Handling Suggestion
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.
2-169

2.1.289 198087414 the failure examination alarm of the 60ms uplink

frame
Alarm Property
l Description: the failure examination alarm of the 60ms uplink frame
l Severity: Minor
Probable Cause
the uplink is not detected the 60ms frame
System Impact
None
Handling Suggestion
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.
2.1.290 198087415 checking block data error alarm

Alarm Property
l Description: checking block data error alarm
l Severity:
Warning
Probable Cause
the frame data error
System Impact
None
2-170

Chapter 2 Alarm
Handling Suggestion
None
2.1.291 198087416 up link LVDS SERDES lost lock alarm

Alarm Property
l Description: up link LVDS SERDES lost lock alarm
l Severity: Minor
Probable Cause
SERDES lose clock
System Impact
None
Handling Suggestion
If it is of no effect to reset GBP and CCI, please exam the LVDS data format from CCI, else to
replace the LVDS.
2.1.292 198087417 FN error alarm

Alarm Property
l Description: FN error alarm
l Severity:
Warning
Probable Cause
the error of frame no error from CCI
System Impact
None
2-171

Handling Suggestion
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.
2.1.293 198087432 Diversity antenna lost

Alarm Property
l Description: Diversity antenna lost
l Severity: Major
Probable Cause
Two diversity antenna receive signal, one of diversity antenna is abnormal
System Impact
None
Handling Suggestion
Reset the TRX; if there is a fault, change the slot; if problem remains, change DTRU.
2.1.294 198087433 Diversity antenna identical

Alarm Property
l Description: Diversity antenna identical
l Severity: Major
Probable Cause
Wrong connection of diversity antenna
System Impact
None
2-172

Chapter 2 Alarm
Handling Suggestion
Check the connection of ant line as quickly as possible.
2.1.295 198087443 Diversity antenna lost

Alarm Property
l Description: Diversity antenna lost
l Severity:
Warning
Probable Cause
Two diversity antenna receive signal, one of diversity antenna is abnormal
System Impact
None
Handling Suggestion
Check the receive channel of RF as quickly as possible.
2.1.296 198087444 Diversity antenna identical

Alarm Property
l Description: Diversity antenna identical
l Severity:
Warning
Probable Cause
Wrong connection of diversity antenna
System Impact
None
2-173

Handling Suggestion
Check the connection of ant line as quickly as possible.
2.1.297 198087451 board not support 16MHW

Alarm Property
l Description: board not support 16MHW
l Severity:
Warning
Probable Cause
board not support 16MHW
System Impact
None
Handling Suggestion
change the board support 16MHW
2.1.298 198087452 cmb or cpu overload

Alarm Property
l Description: cmb or cpu overload
l Severity:
Warning
Probable Cause
cpu usage rate exceed 85%
System Impact
None
2-174

Chapter 2 Alarm
Handling Suggestion
wait for a while , and operate service after alarm restored
2.1.299 198087453 signal HDLC break off

Alarm Property
l Description: signal HDLC break off
l Severity: Major
Probable Cause
Communication break of between TRX and FIB's HDLC or hardware error
System Impact
None
Handling Suggestion
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
2.1.300 198087454 main HDLC break off

Alarm Property
l Description: main HDLC break off
l Severity: Major
Probable Cause
HDLC break off between CMB and FIB;CMB or FIB hardware error
System Impact
None
2-175

Handling Suggestion
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 chang a new cmb or fib
2.1.301 198087455 FIB configure wrong

Alarm Property
l Description: FIB configure wrong
l Severity:
Warning
Probable Cause
parameter Configuration over time or wrong
System Impact
None
Handling Suggestion
wait for ten minutes, if alarm still does not restore, ismg configure parameter again, and synchronize
to the site. If problem remain, just chang a new fib
2.1.302 198087456 lay3 of FIB software has no response

Alarm Property
l Description: lay3 of FIB software has no response
l Severity:
Warning
Probable Cause
FIB software has no respond temporary(set by CMB)
2-176

Chapter 2 Alarm
System Impact
None
Handling Suggestion
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 chang a new fib
5.if software has bug, please update to the latest
2.1.303 198087458 PS cell block caused by slave

Alarm Property
l Description: PS cell block caused by slave
l Severity: Minor
Probable Cause
The DSP on UPPB board is abnormal.
System Impact
The cell fails to provide data service.
Handling Suggestion
1. 2. Check the dynamic data management about the BTS resource in dynamic data management.
Confirm whether the cell is blocked or not. If the cell blocked, unblock the cell.
2. Find the cell which has faulty on NMS configuration management system. Check whether the
configurations of SGSN ID, NSEI and BVCI are correct or not. Correct the wrong configuration.
3. Log in to UPPB board through telnet. Input the SCSShowDevStatus() command to check if the
corresponding DSP status is running. If not, it indicates that the DSP is damaged. In this case,
replace the board.
2.1.304 198087460 positive 12 voltage alarm

Alarm Property
2-177

l Description: positive 12 voltage alarm

l Severity: Major
Probable Cause
DPB board of DTRU module, +12V power module has alarm
System Impact
None
Handling Suggestion
change DTRU module or BBTR board
2.1.305 198087461 negative 12 voltage alarm

Alarm Property
l Description: negative 12 voltage alarm
l Severity: Major
Probable Cause
DPB board of DTRU module, -12V power module has alarm
System Impact
None
Handling Suggestion
change DTRU module or BBTR board
2.1.306 198087462 DSP 1.2v voltage alarm

Alarm Property
l Description: DSP 1.2v voltage alarm
l Severity: Major
2-178

Chapter 2 Alarm
Probable Cause
DPB board of DTRU module, 1.2V power module has alarm
System Impact
None
Handling Suggestion
change DTRU module
2.1.307 198087463 6.4v voltage alarm

Alarm Property
l Description: 6.4v voltage alarm
l Severity: Major
Probable Cause
DPB board of DTRU module, 6.4V power module has alarm
System Impact
None
Handling Suggestion
change DTRU module
2.1.308 198087464 5v voltage alarm

Alarm Property
l Description: 5v voltage alarm
l Severity: Major
Probable Cause
DPB board of DTRU module, 5V power module has alarm
2-179

System Impact
None
Handling Suggestion
change DTRU module
2.1.309 198087465 NSVC's IP failure alarm

Alarm Property
l Description: NSVC's IP failure alarm
l Severity: Minor
Probable Cause
Continously no NS Alive Ack for NSAliveMax times during NS Alive procedure
System Impact
For single NSVC link configuration, the PS service is interrupted. For multi-NSVC link configuration,
the bandwidth is decreased.
Handling Suggestion
1. On NMS fault management interface, check if alarms related to exist. If yes, follow the suggestions
for handling the related alarms.
2. On NMS configuration management interface, check if NSVC configuration parameters are
consistent with those on SGSN.
3. Check if the network cables between BSC and SGSN are intact and inserted in position.
2.1.310 198087470 Fan absence alarm

Alarm Property
l Description: Fan absence alarm
l Severity:
Warning
2-180

Chapter 2 Alarm
Probable Cause
Fan error or absence
System Impact
None
Handling Suggestion
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.
2.1.311 198087471 Fan rotate alarm

Alarm Property
l Description: Fan rotate alarm
l Severity:
Warning
Probable Cause
Fan rotate too slowly
System Impact
None
Handling Suggestion
1. Check if much dust result in the slow rotate speed of the fan or not.
2. If not, exchang new fan frame.
2.1.312 198087472 CMB and FNCB RS485 link break alarm

Alarm Property
l Description: CMB and FNCB RS485 link break alarm
l Severity:
2-181

Warning
Probable Cause
interrupt RS485 communication between fan controller and CMB
System Impact
None
Handling Suggestion
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.
2.1.313 198087473 DTPU CPU overload

Alarm Property
l Description: DTPU CPU overload
l Severity: Major
Probable Cause
System Impact
None
Handling Suggestion
2.1.314 198087480 Status of TX5 filter alarm

Alarm Property
l Description: Status of TX5 filter alarm
l Severity: Major
2-182

Chapter 2 Alarm
Probable Cause
TX5 is adjusting or loss over 5dB
System Impact
None
Handling Suggestion
Replace the FCU, or reset the TRM that connected with it
2.1.315 198087481 Status of TX6 filter alarm

Alarm Property
l Description: Status of TX6 filter alarm
l Severity: Major
Probable Cause
TX6 is adjusting or loss over 5dB
System Impact
None
Handling Suggestion
Replace the FCU, or reset the TRM that connected with it
2.1.316 198087482 dbsapp data error alarm

Alarm Property
l Description: dbsapp data error alarm
l Severity: Major
2-183

Probable Cause
Database detect error when database poweron loading or data synchronizing.Please refer
R_DATERRLOG to modify the error data.
You need to observe the following info of this Table:
NAME(the error table), KEYINDEXINFO(the key index info of the error data), LINE(error line),
DATAERRSTR(error info string)
System Impact
Database service Exception and so on.
Handling Suggestion
1.Refer to R_DATERRLOG modify the error data, Modify the error data then synchronize all data
to affirm whether error is eliminated.
2.Before master to slave exchange, if the old master board exsit this alarm, after exchanged please
synchronize all data to affirm whether the exception exist in the new master board.
2.1.317 198087483 GPS signal synchronization exception

Alarm Property
l Description: GPS signal synchronization exception
l Severity: Minor
Probable Cause
Not support GPS synchronization, GPS clock synchronization failed or GPS fault
System Impact
None
Handling Suggestion
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
2-184

Chapter 2 Alarm
2.1.318 198087484 Second pulse loss

Alarm Property
l Description: Second pulse loss
l Severity: Minor
Probable Cause
GPS 1PPS signal loss
System Impact
None
Handling Suggestion
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.
2.1.319 198087485 Antenna open-circuit alarm

Alarm Property
l Description: Antenna open-circuit alarm
l Severity: Minor
Probable Cause
GPS Antenna appeared open-circuit exception
System Impact
None
Handling Suggestion
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.
2-185

2.1.320 198087486 Antenna short-circuit alarm

Alarm Property
l Description: Antenna short-circuit alarm
l Severity: Minor
Probable Cause
GPS Antenna appeared short-circuit exception
System Impact
None
Handling Suggestion
1. Check cable connection from antennas to EIB or FIB, include GPSSP if short or not.
2.1.321 198087487 Lost satellite alarm

Alarm Property
l Description: Lost satellite alarm
l Severity: Minor
Probable Cause
GPS does not recognize the satellite
System Impact
None
Handling Suggestion
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.
2-186

Chapter 2 Alarm
2.1.322 198087505 Board Connect Fail

Alarm Property
l Description: Board Connect Fail
l Severity: Major
Probable Cause
1. No connect ACK times exceeds setting threshold.

2.No disconnect ACK times exceeds setting threshold.
3.Disconnect ACK times exceeds setting threshold.
4.Apply port fail times exceeds setting threshold.
5.Send connect MSG fail times exceeds setting threshold.
6. Apply connect table fail times exceeds setting threshold.
7.Connect/Disconnect MSG error times exceeds setting threshold.
8.Other reason fail times exceeds setting threshold
System Impact
The service may abnormal when the alarm comes up
Handling Suggestion
check releative performance statistic, mapping to relative board, check the relative board is normal
or not
2.1.323 198087510 CPU of FIB overload

Alarm Property
l Description: CPU of FIB overload
l Severity:
Warning
Probable Cause
2-187

System Impact
None
Handling Suggestion
2.1.324 198087517 Shelf overload control alarm at FUC mode

Alarm Property
l Description: Shelf overload control alarm at FUC mode
l Severity: Minor
Probable Cause
The shelf load exceeds the flow control threshold.
System Impact
Handling Suggestion
2.1.325 198087518 Shelf overload control alarm at SYS mode

Alarm Property
l Description: Shelf overload control alarm at SYS mode
l Severity: Minor
Probable Cause
The shelf load exceeds the flow control threshold.
System Impact
2-188

Chapter 2 Alarm
Handling Suggestion
2.1.326 198087768 Resource Availability Alarm of SLAVE

Alarm Property
l Description: Resource Availability Alarm of SLAVE
l Severity: Minor
Probable Cause
1.Failure ratio for allocating memory exceeds setting threshold.

2.Use ratio of mac instance exceeds setting threshold.
3.Use ratio of bssgp instance exceeds setting threshold.
4.Use ratio of mac-tlli index exceeds setting threshold.
5.Use ratio of bssgp-tlli index exceeds setting threshold.
6.Use ratio of radio channel instance exceeds setting threshold.
7.Use ratio of TS instance exceeds setting threshold.
System Impact
Congestion
or exception may occur in the SLAVE, new PS service of the SLAVE is affected.
Handling Suggestion
1. Checking whether alram thresholds of all resources are lower, if alarm threshold of failure ratio for
allocating memory is less than five percent or alarm threshold of other resources is less than seventy
percent, increasing alarm thresold and keeping on observation.
2. If failure ratio of allocating memory exceeds alarm threshold, checking RLC throughput and TBF
establishing success rate of correlative cells which are handled by this DSP. While RLC throughput
is changeless or decreasing, and TBF establishing success rate drops largeish percent, consider
resetting the SLAVE. Keeping on observation in other situations.
3. If use ratio of mac instance exceeds alarm threshold, or use ratio of bssgp instance exceeds alram
threshold, or use ratio of mac-tlli index exceeds alram threshold, or use ratio of bssgp-tlli index
exceeds alarm threshold, or use ratio of radio channel instance exceeds alarm threshold, or use ratio
of TS instance exceeds alarm threshold, checking RLC throughput and TBF establishing success
rate of correlative cells which are handled by this SLAVE. While RLC throughput is changeless or
decreasing, and TBF establishing success rate drops largeish percent, consider resetting the SLAVE.
In other situations, consider moving some cells of this SLAVE to other idle SLAVE.
2-189

2.1.327 198087778 Dry contact alarm - Waterlog

Alarm Property
l Description: Dry contact alarm - Waterlog
l Severity: Major
Probable Cause
Waterlog alarm
System Impact
None
Handling Suggestion
Perform different process methods according to the type of the exterior device. User can define the
treatment measures according to the actual situation.
2.1.328 198087779 Dry contact alarm - Power loss

Alarm Property
l Description: Dry contact alarm - Power loss
l Severity: Major
Probable Cause
Power loss
System Impact
None
Handling Suggestion
2-190

Chapter 2 Alarm
2.1.329 198087780 Dry contact alarm - No.1 air conditioner fault

Alarm Property
l Description: Dry contact alarm - No.1 air conditioner fault
l Severity: Major
Probable Cause
No.1 air conditioner fault
System Impact
None
Handling Suggestion
2.1.330 198087781 Dry contact alarm - No.2 air conditioner fault

Alarm Property
l Description: Dry contact alarm - No.2 air conditioner fault
l Severity: Major
Probable Cause
No.2 air conditioner fault
System Impact
None
Handling Suggestion
2-191

2.1.331 198087782 Dry contact alarm - AC power abnormal

Alarm Property
l Description: Dry contact alarm - AC power abnormal
l Severity: Major
Probable Cause
AC power abnormal
System Impact
None
Handling Suggestion
2.1.332 198087783 Dry contact alarm - Battery under-voltage

Alarm Property
l Description: Dry contact alarm - Battery under-voltage
l Severity: Major
Probable Cause
Battery under-voltage
System Impact
None
Handling Suggestion
2-192

Chapter 2 Alarm
2.1.333 198087784 Dry contact alarm - SMR abnormal

Alarm Property
l Description: Dry contact alarm - SMR abnormal
l Severity: Major
Probable Cause
SMR(selenium module rectifier) abnormal
System Impact
None
Handling Suggestion
2.1.334 198087785 Dry contact alarm - Under-voltage insulate drop

Alarm Property
l Description: Dry contact alarm - Under-voltage insulate drop
l Severity: Major
Probable Cause
Under-voltage insulate drop
System Impact
None
Handling Suggestion
2-193

2.1.335 198087786 Dry contact alarm - Device suspended

Alarm Property
l Description: Dry contact alarm - Device suspended
l Severity: Major
Probable Cause
Device suspended
System Impact
None
Handling Suggestion
2.1.336 198087787 User-defined Dry contact alarm 1

Alarm Property
l Description: User-defined Dry contact alarm 1
l Severity: Major
Probable Cause
There is a fault on the User-defined dry contact.
System Impact
None
Handling Suggestion
2-194

Chapter 2 Alarm

Alarm Property
l Severity: Major
Probable Cause
System Impact
None
Handling Suggestion

Alarm Property
l Severity: Major
Probable Cause
System Impact
None
Handling Suggestion
2-195


Alarm Property
l Severity: Major
Probable Cause
System Impact
None
Handling Suggestion

Alarm Property
l Severity: Major
Probable Cause
System Impact
None
Handling Suggestion
2-196

Chapter 2 Alarm

Alarm Property
l Severity: Major
Probable Cause
System Impact
None
Handling Suggestion

Alarm Property
l Severity: Major
Probable Cause
System Impact
None
Handling Suggestion
2-197


Alarm Property
l Severity: Major
Probable Cause
System Impact
None
Handling Suggestion

Alarm Property
l Severity: Major
Probable Cause
System Impact
None
Handling Suggestion
2-198

Chapter 2 Alarm

Alarm Property
l Severity: Major
Probable Cause
System Impact
None
Handling Suggestion

Alarm Property
l Severity: Major
Probable Cause
System Impact
None
Handling Suggestion
2-199

2.1.347 198088000 DTPU not support Baseband-Hop alarm

Alarm Property
l Description: DTPU not support Baseband-Hop alarm
l Severity: Major
Probable Cause
DTPU not support Baseband-Hop alarm
System Impact
None
Handling Suggestion
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.
2.1.348 198088001 PA Power Voltage Adjusting Path Disconnected

Alarm Property
l Description: PA Power Voltage Adjusting Path Disconnected
l Severity:
Warning
Probable Cause
I2C Path Disconnected
System Impact
None
2-200

Chapter 2 Alarm
Handling Suggestion
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
2.1.349 198088002 PA Power Voltage Adjusting Data Error

Alarm Property
l Description: PA Power Voltage Adjusting Data Error
l Severity:
Warning
Probable Cause
I2C Data Read or Write Error
System Impact
None
Handling Suggestion
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
2.1.350 198088003 PA Power Voltage Adjusting Data Illegal

Alarm Property
l Description: PA Power Voltage Adjusting Data Illegal
l Severity:
Warning
2-201

Probable Cause
Set Data out of Range
System Impact
None
Handling Suggestion
1.Change Static Power data

2.Update setting
2.1.351 198088004 Access iBSC failure

Alarm Property
l Description: Access iBSC failure
l Severity: Major
Probable Cause
Authentication failed or unconnected response
System Impact
None
Handling Suggestion
1.Authentication again
2.Check physical link
2.1.352 198088005 Control link broken

Alarm Property
l Description: Control link broken
l Severity: Major
2-202

Chapter 2 Alarm
Probable Cause
Communication broken between

BTS and BSC
System Impact
None
Handling Suggestion
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.
2.1.353 198088006 Operation link broken(CS)

Alarm Property
l Description: Operation link broken(CS)
l Severity: Minor
Probable Cause
the transmission line is broken
System Impact
None
Handling Suggestion
check the transmission line
2.1.354 198088007 Operation link broken(PS)

Alarm Property
l Description: Operation link broken(PS)
l Severity: Minor
2-203

Probable Cause
the transmission line is broken
System Impact
None
Handling Suggestion
2.1.355 198088008 Parameter configuration mismatch

Alarm Property
l Description: Parameter configuration mismatch
l Severity: Minor
Probable Cause
iBSC parameters configuration

failed, time-out or broken links
System Impact
None
Handling Suggestion
configuration
parameter again.
2.1.356 198088009 DSP initialization failure

Alarm Property
l Description: DSP initialization failure
l Severity: Minor
2-204

Chapter 2 Alarm
Probable Cause
DSP software or hardware

error
System Impact
None
Handling Suggestion
1.Download DSP software version again.

2.Reset DSP, if the alarm is not restored alarm, replace HBTS
2.1.357 198088010 Parameter configuration failure of AD6537

Alarm Property
l Description: Parameter configuration failure of AD6537
l Severity: Minor
Probable Cause
AD6537 register to read

and write error
System Impact
None
Handling Suggestion
Power-down Re-starting and re-configuration AD6537, send the

appropriate warning information
2.1.358 198088011 Tx PLL unlock

Alarm Property
l Description: Tx PLL unlock
l Severity: Minor
2-205

Probable Cause
Clock signal instability or PLL failed
System Impact
None
Handling Suggestion
Forbid TRM, send

warning information
2.1.359 198088012 Wrong parameter configuration for EEPROM

Alarm Property
l Description: Wrong parameter configuration for EEPROM
l Severity: Minor
Probable Cause
EEPROM hardware failed or previously written into the EEPROM invalid parameters, resulting in
EEPROM RF parameters can not read.
System Impact
None
Handling Suggestion
send warning information
2.1.360 198088013 FLASH memory fault

Alarm Property
l Description: FLASH memory fault
l Severity: Major
2-206

Chapter 2 Alarm
Probable Cause
FLASH programming over the number,

read and write error Or check the software error
System Impact
None
Handling Suggestion
Reset HBTS, Download DSP software version again.if the alarm is not restored alarm, replace HBTS
2.1.361 198088014 Run abnormity of DSP

Alarm Property
l Description: Run abnormity of DSP
l Severity: Major
Probable Cause
DSP programming error
System Impact
None
Handling Suggestion
Reset DSP, load DSP software version, configuration CHP parameters.
2.1.362 198088015 FPGA interface fault

Alarm Property
l Description: FPGA interface fault
l Severity: Major
2-207

Probable Cause
DSP and FPGA interface interruption
System Impact
None
Handling Suggestion
load FPGA version again, reset HBTS,

replace HBTS
2.1.363 198088016 CHP frame fault

Alarm Property
l Description: CHP frame fault
l Severity: Minor
Probable Cause
As the circuit interference so that the frame misoperation
System Impact
None
Handling Suggestion
Reset HBTS
2.1.364 198088017 Wrong receive channel of RF

Alarm Property
l Description: Wrong receive channel of RF
l Severity: Minor
2-208

Chapter 2 Alarm
Probable Cause
Failure to receive channel, the

normal of signals up
System Impact
None
Handling Suggestion
Download FPGA, DSP version again, configuration system parameters.
2.1.365 198088018 Get DNS failure when configuration IP of active

Alarm Property
l Description: Get DNS failure when configuration IP of active
l Severity: Major
Probable Cause
HBTS can not get to the IP address from the DNS server
System Impact
None
Handling Suggestion
Configuration the IP address of DNS by LMT.
2.1.366 198088019 Analyse failure of DNS domain name

Alarm Property
l Description: Analyse failure of DNS domain name
l Severity: Major
2-209

Probable Cause
HBTS can not get to the IP address from the DHCP server
System Impact
None
Handling Suggestion
Configuration the IP address, port of iBSC by LMT.
2.1.367 198088020 IPSec failure

Alarm Property
l Description: IPSec failure
l Severity: Major
Probable Cause
Can not access
System Impact
None
Handling Suggestion
Configuration IPSec parameter again
2.1.368 198088021 RF channel and HTRG board unconformity

Alarm Property
l Description: RF channel and HTRG board unconformity
l Severity: Minor
Probable Cause
Hardware does not support requencies information
2-210

Chapter 2 Alarm
System Impact
None
Handling Suggestion
1.reset the frequency point with HTRG

2.Replace supporting the rang of frequency HTRG
2.1.369 198088022 Get HBTS'S IP address failure from DHCP Sever

Alarm Property
l Description: Get HBTS'S IP address failure from DHCP Sever
l Severity: Major
Probable Cause
HBTS can not automatically get

to the IP address from the DHCP server
System Impact
None
Handling Suggestion
Configuration the IP address, subnet mask, gateway, port of iBSC and HBTS by LMT.
2.1.370 198088023 Over temperature

Alarm Property
l Description: Over temperature
l Severity: Minor
Probable Cause
Over temperature
2-211

System Impact
None
Handling Suggestion
Switch off power, check
2.1.371 198088024 Voltage abnormity

Alarm Property
l Description: Voltage abnormity
l Severity: Minor
Probable Cause
Voltage abnormity
System Impact
None
Handling Suggestion
Check power
2.1.372 198088025 Abis link change alarm

Alarm Property
l Description: Abis link change alarm
l Severity:
Warning
Probable Cause
Abis link on the earth surface is broken, then the service of satellite-backup site changes to the
satellite abis link
2-212

Chapter 2 Alarm
System Impact
if change successfulno impact to the service
Handling Suggestion
check the abis link on the earth surface, and restore it as soon as possible
2.1.373 198088026 IPOE uplink and downlink jam alarm

Alarm Property
l Description: IPOE uplink and downlink jam alarm
l Severity:
Warning
Probable Cause
IPOE site detect the jam of uplink and downlin
System Impact
quality of service decline ,or even not work at all
Handling Suggestion
2.1.374 198088027 DIP E1 rack, rack type error

Alarm Property
l Description: DIP E1 rack, rack type error
l Severity:
Warning
Probable Cause
No. 15 to 12 bits of E1 rack DIP, rack type error
2-213

System Impact
The E1 rack may could not set up link after reboot
Handling Suggestion
check E1 rack No. 15 to 12 bits of the DIP
2.1.375 198088028 DIP E1 rack, rack number error

Alarm Property
l Description: DIP E1 rack, rack number error
l Severity:
Warning
Probable Cause
No. 11 to 10 bits of E1 rack, rack number error
System Impact
Handling Suggestion
2.1.376 198088029 DIP E1 rack,slave rack 1 port error

Alarm Property
l Description: DIP E1 rack,slave rack 1 port error
l Severity:
Warning
Probable Cause
No. 9 to 8 bits of E1 rack, slave rack 1 port error
2-214

Chapter 2 Alarm
System Impact
The E1 site slave rack 1 may not work correctly
Handling Suggestion
2.1.377 198088030 DIP E1 rack,slave rack 2 port error

Alarm Property
l Description: DIP E1 rack,slave rack 2 port error
l Severity:
Warning
Probable Cause
No. 7 to 6 bits of E1 rack, slave rack 2 port error
System Impact
The E1 site slave rack 2 may not work correctly
Handling Suggestion
2.1.378 198088031 DIP E1 rack,satellite back up flag error

Alarm Property
l Description: DIP E1 rack,satellite back up flag error
l Severity:
Warning
Probable Cause
No. 5 bit of E1 rack, satellite back up falg error
2-215

System Impact
Satellite back up link ofE1 site may not work correctly
Handling Suggestion
check E1 rack No. 5 bit of the DIP
2.1.379 198088032 DIP E1 rack,oam time slot error

Alarm Property
l Description: DIP E1 rack,oam time slot error
l Severity:
Warning
Probable Cause
No. 4 to 0 bits of E1 rack, oam time slot error
System Impact
Handling Suggestion
2.1.380 198088033 DIP IP rack,access mode error(IP or IPOE)

Alarm Property
l Description: DIP IP rack,access mode error(IP or IPOE)
l Severity:
Warning
Probable Cause
No. 15 to 14 bits of IP rack, access mode error(IP or IPOE)
2-216

Chapter 2 Alarm
System Impact
The IP rack may could not set up link after reboot
Handling Suggestion
check IP rack No. 15 to 14 bits of the DIP
2.1.381 198088034 DIP IP rack,rack number error

Alarm Property
l Description: DIP IP rack,rack number error
l Severity:
Warning
Probable Cause
No. 13 to 12 bits of IP rack, rack number error
System Impact
Handling Suggestion
2.1.382 198088035 DIP IP rack,site number error

Alarm Property
l Description: DIP IP rack,site number error
l Severity:
Warning
Probable Cause
No. 11to 0 bits of IP rack, site number error
2-217

System Impact
Handling Suggestion
2.1.383 198088036 DIP IP rack,sequence number error

Alarm Property
l Description: DIP IP rack,sequence number error
l Severity:
Warning
Probable Cause
IP rack, sequence number configured on NMS is error
System Impact
Handling Suggestion
ON NMS, check the sequence number of the IP site
2.1.384 198088037 Mains power failure alarm

Alarm Property
l Description: Mains power failure alarm
l Severity: Major
Probable Cause
AC mains failure
2-218

Chapter 2 Alarm
System Impact
user define
Handling Suggestion
check AC
2.1.385 198088038 Alarm of the trx's down link LRC failed

Alarm Property
l Description: Alarm of the trx's down link LRC failed
l Severity: Minor
Probable Cause
the parameter FPGA received is abnormal, or the channel of McBSP is abnormal.
System Impact
RF PLL unlock
Handling Suggestion
Change another DTRU
2.1.386 198105025 the rate of abnormal service on SLAVE is high

Alarm Property
l Description: the rate of abnormal service on SLAVE is high
l Severity: Minor
Probable Cause
The abnormal rate of service on the SLAVE is high
System Impact
KPI Index of Service in RNC will be low.
2-219

Handling Suggestion
Reset the Slave reported in the alarm
2.1.387 198105026 Media Ip address modified

Alarm Property
l Description: Media Ip address modified
Probable Cause
Media Ip address be modified
System Impact
Handling Suggestion
Reset all media plane board
2.1.388 198105029 OMP reboot alarm

Alarm Property
l Description: OMP reboot alarm
l Severity: Major
Probable Cause
After OMP board is restarted, it reports this alarm and then the alarm is restored immediately.
Generally, after this alarm is generated, it can only be queried in history alarms.
System Impact
This alarm affects the operation and maintenance during OMP malfunction. It has no effect on
the services.
2-220

Chapter 2 Alarm
Handling Suggestion
OMP reports this alarm when being reset and then restores the alarm. No handling operations
are required.
2.1.389 198105034 Back card of LogService board is offline

Alarm Property
l Description: Back card of LogService board is offline
l Severity: Minor
Probable Cause
Back card of LogService board is offline, probable causes include:

1. Back card is not on shelf;
2. Back card connection is bad;
3. Back card does not work.
System Impact
The network communication link between Logservice and OMM is broken
Handling Suggestion
1.Check the back card is on the shelf.

2.Inset the back card again.
3.Replace the bad back card.
2.1.390 198105036 The hard disk of LogService error

Alarm Property
l Description: The hard disk of LogService error
l Severity: Minor
Probable Cause
Disk hardware of logservice is fault
2-221

System Impact
one disck has defaultthe other can not work as image diskif the other has default too
LogService maybe can not work
Handling Suggestion
Please Check the alarm additional information to make sure the abnormal hard disk location, and
replace a new hard disk on the location.
2.1.391 198105037 Too high hard disk partition usage rate

Alarm Property
l Description: Too high hard disk partition usage rate
l Severity: Minor
Probable Cause
Disk hardware partition is not enough
System Impact
The hard disk partition usage of LogService is high, LogService maybe can not work.
Handling Suggestion
1.Clean redundancy data
2.1.392 198105039 Bursty flow rate of the control plane for shelf
connection overload
Alarm Property
l Description: Bursty flow rate of the control plane for shelf connection overload
l Severity: Major
Probable Cause
Bursty flow rate of the ctrl plane for shelf connection exceed the threshold.
2-222

Chapter 2 Alarm
System Impact
Bursty flow rate of the control plane for shelf connection is overload. New user access will be refused
for the reason of overload control.
Handling Suggestion
1. Check if the shelf connection is correct.

2. Check if the calbe for shelf connection is intact.
3. Check if board for connection shelf is THUB. If not, change the board to THUB.
2.1.393 198000002 Loss of optical signal

Alarm Property
l Description: Loss of optical signal
l Severity: Minor
Probable Cause
1. The receiving optical fiber/module of local equipment is faulty.

Receiving optical fiber is faulty or disconnected.
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.
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.
System 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.
2-223

Handling Suggestion
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.
2.1.394 198000256 Ethernet link to OMC is broken.

Alarm Property
l Description: Ethernet link to OMC is broken.
l Severity: Minor
Probable 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.
System 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.
Handling Suggestion
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.
2-224

Chapter 2 Alarm
2.2 Communication Alarm

2.2.1 198005378 Board HW Error
Alarm Property
l Description: Board HW Error
l Severity: Major
l Alarm Type: Communications Alarm
Probable Cause
1. Clock is not synchronous.

2. Either the board or the slot has a hardware fault.
System Impact
HW connection is affected and services carried over this HW are interrupted.
Handling Suggestion
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.
2-225

2.2.2 198005382 Communication between power board and OMP is

abnormal
Alarm Property
l Description: Communication between power board and OMP is abnormal
l Severity: Major
Probable 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.
System Impact
The system can not monitor the status of power supply and environmental situation. However,
there is no impact on services.
Handling Suggestion
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.
2.2.3 198005397 Communication of RAWMACIP channel is

abnormal
Alarm Property
l Description: Communication of RAWMACIP channel is abnormal
l Severity: Major
Probable 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.
2-226

Chapter 2 Alarm
System 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.
Handling Suggestion
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.
2.2.4 198005401 Test packet check abnormal

Alarm Property
l Description: Test packet check abnormal
l Severity: Major
Probable Cause
1. The board is faulty.

2. The line from UIM/GUIM/GUIM2 to GLI is abnormal.
System 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.
2-227

Handling Suggestion
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 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.
2.2.5 198005651 IP / MAC address conflict

Alarm Property
l Description: IP / MAC address conflict
l Severity: Major
Probable Cause
1. Board has rebooted and MAC address is incorrect.

2. Board has recalculated the MAC address, which is incorrect.
3. Addition of new shelf on the rack that has the same DIP settings as the other shelf.
System 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.
Handling Suggestion
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.
2-228

Chapter 2 Alarm
2.2.6 198005664 The rate of error code in a mate link is high at

GUIM/GUIM2
Alarm Property
l Description: The rate of error code in a mate link is high at GUIM/GUIM2
l Severity: Minor
Probable Cause
The rate of error code in a mate link is high.
System Impact
The data transferred via mate link are incorrect.
Handling Suggestion
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
2.2.7 198005666 The number of the error packets from MAC port
exceeds the threshold
Alarm Property
l Description: The number of the error packets from MAC port exceeds the threshold
l Severity: Minor
Probable Cause
The number of the error packets from MAC port exceeds the threshold.
System Impact
The MAC port is unavailable or the flow is limited.
2-229

Handling Suggestion
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.
2.2.8 198015617 Some frames Received by FE/GE/ATM/MP/POS/E1

Port are faulty
Alarm Property
l Description: Some frames Received by FE/GE/ATM/MP/POS/E1 Port are faulty
l Severity: Minor
Probable 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.
System 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.
Handling Suggestion
1. Unplug and plug port fibber/network cable.

2. Replace port fibber/network cable.
3. Reset the board.
4. Unplug and plug board.
2-230

Chapter 2 Alarm
2.2.9 198015618 Faulty frames received by port over threshold

Alarm Property
l Description: Faulty frames received by port over threshold
l Severity: Minor
Probable Cause
1. Network status of FE/GE/ATM/MP/POS/E1 port is abnormal.

2. Board hardware faults.
3. Other faults of the board cause faulty FE/GE/ATM/MP/POS/E1 reception.
4. Network processor sub-card which has worked normally is loose.
System Impact
Datagram reception of the board is affected. The service on the board might be unstable.
Handling Suggestion
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.
2.2.10 198015873 PSN board is sending out incorrect frames

Alarm Property
l Description: PSN board is sending out incorrect frames
l Severity: Major
2-231

Probable Cause
1. PSN board in the same shelf is abnormal.

2. PSN board is faulty
System Impact
If the fault lies in PSN board, service of the entire RNC NE 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.
Handling Suggestion
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.
2.2.11 198022784 BFD Session Interrupted

Alarm Property
l Description: BFD Session Interrupted
l Severity: Minor
Probable 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.
System 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.
2-232

Chapter 2 Alarm
Handling Suggestion
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.
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.
2.2.12 198029953 The Ethernet port state is OAM loop back

Alarm Property
l Description: The Ethernet port state is OAM loop back
2-233

l Severity: Minor
Probable Cause
The local port state is loop back because the peer port starts Ethernet OAM loop back request
of 802.3ah.
System Impact
The Ethernet link which is in loop back test can't bear service data.
Handling Suggestion
Check if the peer port has started Ethernet OAM loop back test. If yes, stop it, if no, disable local port
Ethernet OAM.
2.2.13 198031744 IPD session interrupted

Alarm Property
l Description: IPD session interrupted
l Severity: Minor
Probable 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.
System 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.
2-234

Chapter 2 Alarm
Handling Suggestion
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.
2.2.14 198066000 Abis link broken

Alarm Property
l Description: Abis link broken
l Severity: Major
2-235

Probable Cause
1. A newly configured link is initially broken.

2. The link status changes to broken.
3. The link may break frequently during active/standby switchover.
System Impact
BTS break-down
Handling Suggestion
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.
2.2.15 198066003 Control plane communication is abnormal

between board and its home module
Alarm Property
l Description: Control plane communication is abnormal between board and its home
module
l Severity: Minor
Probable Cause

2. The board is blocked.
3. The inserted board is different from board configuration.
5. The control plane communication is abnormal.
6. The board is reset.
System Impact
The services carried by the board are interrupted.
2-236

Chapter 2 Alarm
Handling Suggestion
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.
2.2.16 198066004 Control plane communication is abnormal

between MP and OMP
Alarm Property
l Description: Control plane communication is abnormal between MP and OMP
l Severity: Major
Probable Cause

3. The control plane communication is abnormal.
4. The board resets.
System Impact
The board is blocked so that it can not provide functions. Furthermore, all services under the relevant
module become unavailable.
Handling Suggestion
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.
2-237

2.2.17 198066005 SCCP subsystem unavailable

Alarm Property
l Description: SCCP subsystem unavailable
l Severity: Minor
Probable 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.
System 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.
Handling Suggestion
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.
2-238

Chapter 2 Alarm
2.2.18 198066008 MTP2 link sending overload

Alarm Property
l Description: MTP2 link sending overload
l Severity: Major
Probable 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.
System 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.
Handling Suggestion
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.
2.2.19 198066009 MTP2 link reception overload

Alarm Property
l Description: MTP2 link reception overload
l Severity: Major
Probable 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.
2-239

System 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.
Handling Suggestion
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.
2.2.20 198066010 MTP3 Signalling Point Inaccessible

Alarm Property
l Description: MTP3 Signalling Point Inaccessible
l Severity: Major
Probable Cause
1. No service link exists in the office route.

2. The MTP3 signaling network management message TransFer Prohibit(TFP) is received.
System Impact
UE fails to receive/transmit messages from/to the relevant office. New services can not be accessed
to this office, and existing services are interrupted abnormally.
Handling Suggestion
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.
2.2.21 198066011 MTP3 link unavailable

Alarm Property
2-240

Chapter 2 Alarm
l Description: MTP3 link unavailable

l Severity: Minor
Probable Cause
1. Physical link at bottom layer is broken or link quality is poor.

2. Link test fails.
3. This link is deactivated in dynamic data management.
4. The opposite end has released this link.
5. SMP or SPB/SPB2/APBE/APBE2 board resets
System 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.
Handling Suggestion
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.
2.2.22 198066012 MTP3 cluster inaccessible

Alarm Property
l Description: MTP3 cluster inaccessible
l Severity: Major
2-241

Probable Cause
1. No service link exists in the cluster route.

2. TCP is received.
System 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.
Handling Suggestion
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.
2.2.23 198066014 M3UA Signalling Point Inaccessible

Alarm Property
l Description: M3UA Signalling Point Inaccessible
l Severity: Major
Probable 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.
System Impact
2-242

Chapter 2 Alarm
Handling Suggestion
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.
2.2.24 198066019 Association link broken

Alarm Property
l Description: Association link broken
l Severity: Major
Probable Cause
1. The association is released in dynamic data management.

2. Association configuration is modified at local end.
3. Association is released at opposite end.
4. Bottom layer link is faulty.
System 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.
2-243

Handling Suggestion
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.
2.2.25 198066026 Association path broken

Alarm Property
l Description: Association path broken
l Severity: Major
Probable Cause
1. SCTP link is broken

2. Control plane path in NE is interrupted.
4. The route to remote address is lost.
System 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.
Handling Suggestion
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.
2-244

Chapter 2 Alarm
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.
6. Check if the opposite equipment is faulty. If yes, troubleshoot at opposite end.
2.2.26 198066029 PPP link broken

Alarm Property
l Description: PPP link broken
l Severity: Major
Probable 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.
System Impact
This will cause disconnection of user plane data and services.
Handling Suggestion
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.
2-245

2.2.27 198087101 HW link broken

Alarm Property
l Description: HW link broken
l Severity: Minor
Probable Cause
BTS internal communication breaks
System Impact
None
Handling Suggestion
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.
2.2.28 198087336 Rack Abis control link broken

Alarm Property
l Description: Rack Abis control link broken
Probable Cause
1. The rack configured on NMS client does not actually exist.

2. IP site, The IP configuration on NMS client is not correct.
3. E1 site, Abis time slot of the slave rack configuration on NMS client is not correct.
4. The cable connections are abnormal.
System Impact
None
2-246

Chapter 2 Alarm
Handling Suggestion
1. Check the site configuration in the Configuration Resource Tree. If the configured slave rack does
not actually exist, delete it and synchronize to BSC.
2. On NMS configuration management interface, check the correctness of configuration.
2.1 For IP access site:
a) Check the interface configuration, ensure the RPU and RUIB/EUIP interfaces are both configured
and correct.
b) Check the association configuration in the "2G Office Configuration" interface, if exists. The local
port, remote port, local IP address pair, remote IP address pair must be exactly the same with site
configuration. All IP addresses appeared in the "local IP address pair" must be configured in step a).
The association property must be Server, service type must be "IPABIS".
c) In the "Site Configuration" interface, make sure the referenced association id is same with which
configured in step b)
2.2 For E1 access site, check the Abis time slot of slave rack of the site.
If any of the configurations mentioned above is found wrong or inconsistent, correct it and synchronize
to BSC.
3. Check the cables between BTS and BSC to ensure they are correct.
2.2.29 198087337 Site Abis control link broken

Alarm Property
l Description: Site Abis control link broken
Probable Cause
1. The site configured on NMS client does not actually exist.

2. IP site, The IP configuration on NMS client is not correct.
3. E1 site, Abis time slot of the master rack configuration on NMS client is not correct.
4. The cable connections are abnormal.
System Impact
The cells under this site cannot provide any voice or data services.
2-247

Handling Suggestion
1. On NMS configuration management interface, check the site configuration. If the configured site
does not actually exist, delete it and synchronize to BSC.
2. Check the correctness of configuration in the Confguration Resource Tree.
2.1 For IP access site:
a) Check the interface configuration, ensure the RPU and RUIB/EUIP interfaces are both configured
and correct.
b) Check the association configuration, if exists. The local port, remote port, local IP address pair,
remote IP address pair must be exactly the same with site configuration. All IP addresses appeared
in the "local IP address pair" must be configured in step a). The association property must be Server,
service type must be "IPABIS".
c) In the "Site Configuration" interface, make sure the referenced association id is same with which
configured in step b)
2.2 For E1 access site, check the Abis time slot of slave rack of the site.
If any of the configurations mentioned above is found wrong or inconsistent, correct it and synchronize
to BSC.
3. Check the cables between BTS and BSC to ensure they are correct.
2.2.30 198087342 Cell interruption alarm

Alarm Property
l Description: Cell interruption alarm
l Severity: Minor
Probable Cause
1. The site to which the cell belongs is lost.

2. The cell BCCH frequency is faulty.
3. The cell is manually blocked.
System Impact
The cell cannot provide any voice or data services.
2-248

Chapter 2 Alarm
Handling Suggestion
1. On NMS fault management interface, check if related alarms exist. If yes, follow the suggestions
for handling the related alarms.
198087337 Site Abis control link broken
2. On NMS dynamic data management interface, check if the cell state is abnormal.
On Radio Resource Management tab page, check BTS management, TRX management, and TS
management.
i. BTS management:
If manually blocked BTSs exist, unblock them.
If global reset cell blockage exists, rectify A interface faults.
ii. TRX management:
If the BCCH of the cell concerned is manually blocked, unblock the TRX.
If Abis control link break cause TRX to block exists, restore the Abis control link.
If CU or FU operation state of the TRX is blocked, rectify the TRX fault.
iii. TS management:
If the BCCH TS of the cell concerned is manually blocked, unblock the TS.
2.2.31 198087343 Front PC communication link broken alarm

Alarm Property
l Description: Front PC communication link broken alarm
l Severity: Minor
Probable Cause
1. NFS service of Linux system on NMS server is abnormal.

2. The link communication between NMS server and OMP board is abnormal.
System Impact
During the alarm period, performance data cannot be reported to NMS.
Handling Suggestion
1. Log in OMP board through telnet and input "NfsShowState" command. If NFS device is abnormal,
the command result shows corresponding indications in English. And then, check NFS service of
Linux system on NMS server, if it is abnormal, NFS service need to be restarted immediately, for
example, use Linux command "service nfs restart".
2. Check the network cables between SBCX and OMP and ensure the connections are correct.
2-249

2.2.32 198087380 TRX Manual Block

Alarm Property
l Description: TRX Manual Block
l Severity: Minor
Probable Cause
The TRX indicated in the alarm is manually blocked.
System Impact
The TRX is out of service.
Handling Suggestion
On NMS dynamic data management interface, check the TRX state in TRX Management tab.
Manually unblock the blocked TRXs.
2.2.33 198087381 The time-slot of air interface blocked manually

Alarm Property
l Description: The time-slot of air interface blocked manually
l Severity: Minor
Probable Cause
The TS indicated in the alarm is manually blocked.
System Impact
The TS that blocked manually can not provide any service.
Handling Suggestion
On NMS dynamic data management interface, check the TS state in TS Management tab. Manually
unblock the blocked TSs.
2-250

Chapter 2 Alarm
2.2.34 198087468 lapd jam alarm

Alarm Property
l Description: lapd jam alarm
l Severity: Major
Probable Cause
Rack Lapd jam alarm
System Impact
LAPD frame lose serious and communication may break off
Handling Suggestion
1.Add more Lapd channel if not enough

2.if E1 Trunk alarm appear, solve it firstly.
3.check site voltage whether it is correct or not
2.2.35 198087775 super site exchanged to the satellitic ABIS link

or slave link
Alarm Property
l Description: super site exchanged to the satellitic ABIS link or slave link
l Severity: Major
Probable Cause
The subaerial ABIS link is broken, site exchanged to satellitic ABIS link or slave link
System Impact
None
Handling Suggestion
restore the subaerial ABIS link
2-251

2.2.36 198105035 The communication link between LogService

board and OMP is broken
Alarm Property
l Description: The communication link between LogService board and OMP is broken
l Severity: Minor
Probable Cause
The communication link between LogService board and OMP is broken, Probable causes for the
alarm include:
1.LogService board is not on the shelf.
2.LogService programme does not work.
3.LogService board does not work.
System Impact
The network communication link between Logservice and OMP is brokenLog data can not been
sent to LogService
Handling Suggestion
1.Check the LogService board is on the shelf.

2.Check the LogService programme run status.
3.Replace the LogService board;
2.2.37 198000519 Trunk error

Alarm Property
l Description: Trunk error
l Severity: Major
2-252

Chapter 2 Alarm
Probable 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.
System Impact
The trunk equipment fails to work normally. All services based on the trunk are interrupted.
Handling Suggestion
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.
2.2.38 198000520 Trunk abnormal

Alarm Property
l Description: Trunk abnormal
l Severity: Major
Probable 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.
2-253

System Impact
All services based on the trunk are interrupted.
Handling Suggestion
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.
2.2.39 198003841 The control plane retransmission ratio over the

threshold
Alarm Property
l Description: The control plane retransmission ratio over the threshold
l Severity: Major
Probable Cause
There are some badly-touched boards in the system environment and the retransfer-ratio of RUDP
packets increases.
System Impact
The master board will change when slave is exist.
Handling Suggestion
Make records of the alarm information and contact the next level of maintenance support.
2-254

Chapter 2 Alarm
2.2.40 198005122 Loss of Active/standby communication link

Alarm Property
l Description: Loss of Active/standby communication link
l Severity: Minor
Probable Cause
1. The board is configured to be in active/standby mode, but the mate board is not in position.
2. Hardware Problem.
System Impact
The active board can not communicate with the standby board. As a result, active/standby
changeover operation fails. There is no impact on services.
Handling Suggestion
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.
2.2.41 198005126 Incorrect FE Routing Connection

Alarm Property
l Description: Incorrect FE Routing Connection
2-255

Probable 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.
System Impact
Control plane routing is disconnected; ports are switched over in cycle; all services on this shelf
are interrupted.
Handling Suggestion
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.
2.2.42 198005127 FE Link Error Alarm

Alarm Property
l Description: FE Link Error Alarm
l Severity: Minor
2-256

Chapter 2 Alarm
Probable Cause
1. In a pair of FE ports, one has normal link but the other has link error.
2. The hardware is faulty.
System 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.
Handling Suggestion
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.
2.2.43 198005128 Duplicate rack and shelf

Alarm Property
l Description: Duplicate rack and shelf
l Severity: Minor
Probable Cause
Shelf connect to the system with duplicate physical ID
System Impact
Boards in the shelf which power-on later power-on failure.
Handling Suggestion
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.
2-257

2.2.44 198005129 Ethernet port loop back error

Alarm Property
l Description: Ethernet port loop back error
l Severity: Minor
Probable Cause
Ethernet port loop back occurs.
System Impact
There is a fault of the network in the system.
Handling Suggestion
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.
2.3 Processing alarm

2.3.1 198005120 T Network Connection Not Conform to
Configuration
Alarm Property
l Description: T Network Connection Not Conform to Configuration
l Alarm Type: Processing alarm
2-258

Chapter 2 Alarm
Probable Cause
T network fiber connection does not conform to optical interface connection relation configured on
the background.
System Impact
T Net switch of the shelf is in disorder.
Handling Suggestion
Modify the fiber connection or the connection configuration to keep the configuration consistent
with the physical connection.
2.3.2 198005123 Incorrect configuration for inserted board or

device
Alarm Property
l Description: Incorrect configuration for inserted board or device
l Severity: Minor
Probable Cause
1. Incorrect board in slot.

2. Board hardware does not match the OMC-R configuration.
System Impact
The board fails to be normally powered on. The services carried by the board are interrupted.
Handling Suggestion
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.
2.3.3 198005387 Alarm due to inconsistent MP type

Alarm Property
2-259

l Description: Alarm due to inconsistent MP type

l Severity: Major
Probable Cause
1. The MP type is changed on NMS and the board is not restarted.

2. The active MP type on the local board is not consistent with that configured on NMS.
System Impact
There is no impact on services
Handling Suggestion
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".
2.3.4 198005388 Startup file does not exist

Alarm Property
l Description: Startup file does not exist
l Severity: Major
Probable Cause
The startup configuration file is deleted.
System Impact
This alarm may cause OMP work abnormally, and the entire network element services are affected.
Handling Suggestion
1. Reset the active and standby OMPs through NMS man-machine command interface.
2-260

Chapter 2 Alarm
2.3.5 198005398 Office ID is not set correctly with control shelf

Alarm Property
l Description: Office ID is not set correctly with control shelf
l Severity: Major
Probable Cause
The office ID of a shelf where DIP switch locates is different from that of a shelf where OMP locates.
System 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.
Handling Suggestion
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.
2.3.6 198005402 Database config is different from file named

bootcfg.ini
Alarm Property
l Description: Database config is different from file named bootcfg.ini
l Severity: Major
Probable Cause
After the start information of OMP is modified, the active and standby OMP boards are not restarted.
System Impact
System startup is abnormal, MP may not work normally.
Handling Suggestion
Restart the active and the standby OMP boards at the same time through NMS man-machine
interface command .
2-261

2.3.7 198005649 Port configuration is incorrect

Alarm Property
l Description: Port configuration is incorrect
l Severity: Major
Probable 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.
System 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.
Handling Suggestion
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".
2-262

Chapter 2 Alarm
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.
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".
2.3.8 198005889 Version Switches While Board Doesn't Reset

Alarm Property
l Description: Version Switches While Board Doesn't Reset
l Severity:
Warning
Probable 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.
System Impact
The board version will not take effect if the board does not reset.
Handling Suggestion
Restart the board manually.
2-263

2.3.9 198005892 Boot Version Fails to Write to Backup Region

Alarm Property
l Description: Boot Version Fails to Write to Backup Region
l Severity:
Warning
Probable Cause
Boot version fails to be written to backup region.
System Impact
BOOT backup version is unavailable.
Handling Suggestion
Switch BOOT again and restart the board manually.
2.3.10 198007936 Memory file buffer overflow

Alarm Property
l Description: Memory file buffer overflow
l Severity: Major
Probable Cause
The transferred data records exceed the maximum capacity of the table, and the capacity of the
receiver memory file buffer is insufficient.
System Impact
If the board is powering on, the excessive data records (beyond table capacity) are discarded.
2-264

Chapter 2 Alarm
Handling Suggestion
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.
2.3.11 198015360 Microcode Is Abnormal

Alarm Property
l Description: Microcode Is Abnormal
l Severity: Major
Probable Cause
The Network Processor hardware in the board (whose microcode is abnormal) is faulty.
System 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.
Handling Suggestion
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.
2.3.12 198023040 Number of alarms exceeds threshold.

Alarm Property
l Description: Number of alarms exceeds threshold.
l Severity: Major
2-265

Probable Cause
The current alarm board has too many alarms so that the relevant alarm pool is full.
System Impact
Alarms may be lost, but there is no impact on user services.
Handling Suggestion
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.
2.3.13 198066013 MTP3 link congestion

Alarm Property
l Description: MTP3 link congestion
l Severity: Major
Probable Cause
1. There are too many messages at upper layer.

2. The quality of bottom layer link is so poor that many messages are retransmitted.
System 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.
Handling Suggestion
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
2-266

Chapter 2 Alarm
2.3.14 198066018 Association congestion

Alarm Property
l Description: Association congestion
l Severity: Minor
Probable 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.
System 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.
Handling Suggestion
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.
2.3.15 198066027 SNTP failure

Alarm Property
l Description: SNTP failure
l Severity: Minor
Probable 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.
2-267

System 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.
Handling Suggestion
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.
2.3.16 198066031 OMP alarm pool is full, unable to store any more
alarms.
Alarm Property
l Description: OMP alarm pool is full, unable to store any more alarms.
l Severity: Major
Probable Cause
There are too many system alarms. The alarm pool is full of system alarms.
System Impact
Alarms may be lost, but there is no impact on user services.
Handling Suggestion
1. Delete any temporarily useless virtual configuration resources.

2. On NMS fault management interface, delete some alarms which have small system impact.
2-268

Chapter 2 Alarm
2.3.17 198066032 Loss of NTP time synchronisation

Alarm Property
l Description: Loss of NTP time synchronisation
l Severity: Minor
Probable Cause
1. Control-panel link between OMP and RPU board is down.

2. NTP time and local time differs greatly.
System Impact
NTP time synchronization terminates, bringing in time deviation between the foreground and the
backgroundeffecting some servicessuch as charges, and leading to interruption of ongoing
services.
Handling Suggestion
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
2.3.18 198087513 Board Ethernet port overload alarm

Alarm Property
l Description: Board Ethernet port overload alarm
l Severity: Major
Probable Cause
Ethernet port resource allocation is unbalanced and overloaded.
System Impact
Impact service quality
Handling Suggestion
Redistribute resources and balance them.
2-269

2.3.19 198087773 CIC manual blocked alarm

Alarm Property
l Description: CIC manual blocked alarm
l Severity: Minor
Probable Cause
Atrunk is manual blocked
System Impact
the CIC is out of service
Handling Suggestion
On NMS Dynamic Data Management interface, select A interface Management under BSC Dynamic
Data Management. Click the Atrunk Management tab, unblock the blocked ts.
2.3.20 198087774 BVC manual blocked alarm

Alarm Property
l Description: BVC manual blocked alarm
l Severity: Minor
Probable Cause
BVC is manual blocked
System Impact
the BVC is out of service
Handling Suggestion
On NMS Dynamic Data Management interface, select Radio Resource Management under BTS
Dynamic Data Management. Click the BVC Management tab, unblock the blocked BVC
2-270

Chapter 2 Alarm
2.4 Environment Alarm

2.4.1 198025856 Rack temperature is high
Alarm Property
l Description: Rack temperature is high
l Severity: Minor
l Alarm Type: Environment Alarm
Probable Cause
1. Fan is not working.

2. Fan has failed.
3. No fan connected.
4. Temperature sensor is faulty or setting is incorrect.
System 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.
Handling Suggestion
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.
2.4.2 198025857 Low temperature in Rack

Alarm Property
l Description: Low temperature in Rack
l Severity: Minor
2-271

Probable Cause
1. Threshold is incorrect.
2. Temperature sensor is not working
3. External room heating control not working.
System Impact

2. If the alarm is caused by low rack temperature, board may work abnormally and board services
may be interrupted.
Handling Suggestion
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.
2.4.3 198025858 Room temperature is higher than high threshold

Alarm Property
l Description: Room temperature is higher than high threshold
l Severity: Minor
Probable Cause
1. Threshold configuration is unreasonable.

2. Actual temperature in equipment room is too high.
System Impact

2. If the alarm is caused by high room temperature, board may work abnormally and board services
may be interrupted.
2-272

Chapter 2 Alarm
Handling Suggestion
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.
2.4.4 198025859 Room temperature is lower than low threshold

Alarm Property
l Description: Room temperature is lower than low threshold
l Severity: Minor
Probable Cause
1. The configured threshold is unreasonable.

2. Actual temperature in equipment room is too low.
3. Setting of the sensor is incorrect.
System Impact

2. If the alarm is caused by low room temperature, board may work abnormally and board services
may be interrupted.
Handling Suggestion
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.
2.4.5 198025860 Rack voltage is high

Alarm Property
l Description: Rack voltage is high
2-273

l Severity: Minor
Probable Cause

2. Actual voltage is too high.
System Impact

2. If the alarm is caused by high voltage, board may work abnormally and board services may
be interrupted.
Handling Suggestion
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.
2.4.6 198025861 rack voltage is low

Alarm Property
l Description: rack voltage is low
l Severity: Minor
Probable Cause
1. Voltage value is under the low threshold.

2. The setting of the votage detector is error.
3. Power input of a road may have been disconnected.
System Impact

2. If the alarm is caused by low voltage, board may work abnormally and board services may be
interrupted.
2-274

Chapter 2 Alarm
Handling Suggestion
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.
2.4.7 198025862 Humidity is high

Alarm Property
l Description: Humidity is high
l Severity: Minor
Probable Cause

2. Actual humidity in equipment room is too high.
System Impact

2. If the alarm is caused by high room humidity, board may work abnormally and board services may
be interrupted.
Handling Suggestion
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.
2.4.8 198025863 Humidity is low

Alarm Property
l Description: Humidity is low
l Severity: Minor
2-275

Probable Cause

2. Actual humidity in equipment room is too low.
System Impact

2. If the alarm is caused by low room humidity, board may work abnormally and board services may
be interrupted.
Handling Suggestion
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.
2.4.9 198025864 Fault in fan plug-in box

Alarm Property
l Description: Fault in fan plug-in box
l Severity: Minor
Probable Cause
1. The fan subrack is not tightly inserted into the rack.

2. The fan subrack has a hardware fault.
System Impact
This alarm may cause very high rack temperature. As a result, the relevant board may work
abnormally and board services may be interrupted.
2-276

Chapter 2 Alarm
Handling Suggestion
1. Check whether the FAN subrack is tightly inserted into the rack. If no, unplug and plug it.
2. Replace the fan subrack.
2.4.10 198025865 Rack door alarm

Alarm Property
l Description: Rack door alarm
l Severity: Minor
Probable Cause
1. The rack door is not closed.

2. The connection for door access control device is incorrect.
System Impact
Services won't be affected, but there is a potential safety problem.
Handling Suggestion
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.
2.4.11 198025866 Smoke detected

Alarm Property
l Description: Smoke detected
l Severity: Minor
2-277

Probable Cause
1. The alarm device is faulty.

2. The smoke density in equipment room is too high.
System Impact
Services won't be affected, but there is a potential safety problem. Need to be handled immediately.
Handling Suggestion
1. Quick find the origin of smog.

2. If there is no smog in the equipment room, replace the smog detector.
2.4.12 198025867 Infrared alarm

Alarm Property
l Description: Infrared alarm
l Severity: Minor
Probable Cause
1. Heat source (e.g. animal/human being) approaches near.

2. The configuration of infra-red sensor is wrong.
3. The infrared sensor is faulty.
System 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.
Handling Suggestion
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.
2-278

Chapter 2 Alarm
2.4.13 198025868 Lightning alarm

Alarm Property
l Description: Lightning alarm
l Severity: Minor
Probable Cause
1. Outdoor unit or equipment damaged by lightening

System Impact
The board may work abnormally due to lightning stroke. Accordingly, board services will be
interrupted.
Handling Suggestion
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.
2.4.14 198025869 Loss of DC power supply to rack

Alarm Property
l Description: Loss of DC power supply to rack
l Severity: Minor
Probable Cause
1. Circuit breaker has tripped.

2. No incoming DC supply from rectifier
System Impact
This shelf can not be supplied with power. All boards on the shelf can not work and board services
are interrupted.
2-279

Handling Suggestion
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.
2.4.15 198029184 SNTP server is unavailable

Alarm Property
l Description: SNTP server is unavailable
l Severity: Minor
Probable Cause
SNTP server is faulty or communication broken.
System Impact
NO impact to traffic only loss of Time synchronisation data for time stamp of events and reporting.
Handling Suggestion
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.
2.5 QoS Alarm

2.5.1 198023296 Inter-board message communication flow rate
exceeds the alarm threshold
Alarm Property
2-280

Chapter 2 Alarm
l Description: Inter-board message communication flow rate exceeds the alarm

threshold
l Severity: Minor
l Alarm Type: Qos Alarm
Probable Cause
The configured alarm threshold is less than the usual inter-board communication traffic in input
and output directions of the board control plane.
System Impact
Packet of the control plane loss might occur. No impact on user service.
Handling Suggestion
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).
2.5.2 198066069 The number of times of signaling data transfer

exceeds the allowed threshold of the license
Alarm Property
l Description: The number of times of signaling data transfer exceeds the allowed
threshold of the license
l Severity: Major
Probable Cause
The number of transfer that passes MTP3/M3UA/SCCP/SUA exceed the permission of license.
System Impact
The data may be discarded in all MP boards.
Handling Suggestion
Contact the related personnel and get proper license again.
2-281

2.5.3 198087438 Assignment failure alarm

Alarm Property
l Description: Assignment failure alarm
l Severity: Major
Probable Cause
TCH assignment fails in large scale and exceeds threshold.
System Impact
Service quality will remain low for a long time if alarm is not handled.
Handling Suggestion
1. Check whether channels are manually blocked, if yes, unblock them.

2. Check whether TRX state is normal, if not, reset, re-insert or replace TRX.
3. Check cells' work state and disturbance situation. If cells work abnormally or disturbance happens
severely, the network need to be optimized.
2.5.4 198087506 NSE block alarm

Alarm Property
l Description: NSE block alarm
l Severity: Major
Probable Cause
All NSVCs of the NSE are blocked
System Impact
The NSE can not run PS
Handling Suggestion
1. If NSVC is manually blocked, please unblock it in Dynamic Data Management interface of NMS.
2. Otherwise, please check Gb link.
2-282

Chapter 2 Alarm
2.5.5 198087507 SGSN is blocked

Alarm Property
l Description: SGSN is blocked
l Severity: Major
Probable Cause
All NSEs of the SGSN are blocked
System Impact
All NSEs of the SGSN can not run PS
Handling Suggestion
1. If NSVC is manually blocked, please unblock it in Dynamic Data Management interface of NMS.
2. Otherwise, please check Gb link.
2.5.6 198087758 Manual User Access control alarm

Alarm Property
l Description: Manual User Access control alarm
l Severity: Minor
Probable Cause
Start manual user access control
System Impact
Handling Suggestion
2-283

2.5.7 198087759 CPU overload control alarm at Paging mode

Alarm Property
l Description: CPU overload control alarm at Paging mode
l Severity: Minor
Probable Cause
The excessive traffic causes the CPU load to exceed the flow control threshold in module parameter
setting.
System Impact
The system automatically initiates flow control management and thus some users cannot gain access.
If the traffic is still excessive after flow control, the CPU load will grow further.
Handling Suggestion
Block some cells through dynamic data management to prohibit some users to access. After the
2-284

Chapter 3
Notification
Table of Contents
198003649 Shortage of swap block resource .............................................................3-4
198005188 UIM CS Changeover................................................................................3-4
198005189 Notification of Active/Standby Changeover .............................................3-5
198005192 Board's Work Mode Unsupported ............................................................3-6
198005193 Notification of the power on status of the basic process ...........................3-6
198005194 Changeover of CS Optical Interfaces .......................................................3-7
198005195 Board mix plug occurred ..........................................................................3-8
198005441 Port status on internal media plane changed............................................3-8
198005448 485 seriel bus link between CLKG/PWRD and OMP is broken.................3-9
198005700 DSP resets for abnormities ....................................................................3-10
198005701 Version Load Error.................................................................................3-10
198005702 Trunk configuration is inconsistent with function of board .......................3-11
198005705 MCU resets abnormally .........................................................................3-12
198005708 The active/standby modules of PSN clock have changed over
successfully..............................................................................................................3-12
198005710 The result of manual reference selection for SETS chip .........................3-13
198005711 Clock reference selection is being executed...........................................3-13
198005712 The manual select base will be run, please wait for the result ................3-14
198005713 APC chip's peripheral RAM has hardware fault ......................................3-14
198005714 No external clock for DSP ......................................................................3-15
198005715 PP2S source switched ...........................................................................3-15
198005718 Two master clock ports is directly connected..........................................3-16
198005956 Board Version Error ...............................................................................3-16
198005958 IDE Version Files Synchronization Information.......................................3-17
198005960 Version Fails to Be Switched..................................................................3-18
198005961 OMP Version Check Information ............................................................3-18
198005962 Patch version operate fail.......................................................................3-19
198008005 Memory file buffer overflow ....................................................................3-19
198011840 M3UA user office status change.............................................................3-20
198013888 ASP status changed ..............................................................................3-20
198013889 AS status changed.................................................................................3-21
198013890 Sigtran error message received .............................................................3-22
198013891 Sigtran notification message received....................................................3-23
198013892 Allocate memory fail...............................................................................3-23
198014144 Association establishment failed ............................................................3-24
198014145 Association restart .................................................................................3-25
198016193 SIG_IPI Forwards Service Messages Abnormally ..................................3-25
3-1

198017216 Error in MCS Multi-Core processor receiving configuration data from

DBS .........................................................................................................................3-26
198018241 TCP Connection Aborted .......................................................................3-26
198018242 MD5 Verification Failure .........................................................................3-27
198018243 Wrong MD5 Message Abstract ..............................................................3-27
198018755 HDLC status changed............................................................................3-28
198019777 APS switch over occurred ......................................................................3-29
198020291 Protocol stack process failed to initialize during power on ......................3-29
198020802 Conflicting IP address in subnet.............................................................3-30
198020803 Conflicting MAC address in subnet ........................................................3-31
198020804 Failed to generate static ARP from IP address.......................................3-31
198020805 ARP detect failed ...................................................................................3-32
198020806 ARP detect that the static ARP is not match...........................................3-33
198021059 RIP Neighbor Configuration Errors.........................................................3-33
198021060 RIP Interface Authentication Errors ........................................................3-34
198021065 Incompatible RIP Version Number .........................................................3-34
198021329 LSDB Overflow ......................................................................................3-35
198021330 Configuration of OSPF mismatched .......................................................3-35
198021331 Failed to add the ospf route to the courier routing table..........................3-36
198021584 Neighbor Hold Timer Expired .................................................................3-37
198021585 BGP Interface Down and Neighbor Link Broken.....................................3-37
198021837 Failure in adding dynamic routings.........................................................3-38
198022598 Routers with Conflicting System Id Exist in Network...............................3-39
198022599 ISIS Message Authentication Failure .....................................................3-39
198023106 Board self-check fails.............................................................................3-40
198023107 The board initialization failure ................................................................3-40
198023617 Configuration file is unusable .................................................................3-41
198025664 Abnormal Half-Fixed Connection Changes ............................................3-42
198026176 Clock reference changed .......................................................................3-42
198026177 CLKG reference quality changed ...........................................................3-43
198026178 Clock work mode changed.....................................................................3-43
198026179 Clock source invalidation reason changed .............................................3-44
198028231 Router ID not configured for OSPFv3.....................................................3-44
198028233 Configuration of OSPFv3 Mismatched ...................................................3-45
198028993 SCTP Primary Path Set Failed...............................................................3-45
198029760 DNS server inaccessible ........................................................................3-46
198030016 Ethernet link OAM event ........................................................................3-46
198031040 ACL config failed....................................................................................3-47
198087338 TRX No Traffic .......................................................................................3-47
198087339 BTS self maintenance inform .................................................................3-48
198087353 NSVC deletion notification .....................................................................3-48
198087355 Timeout notification for a database to return value .................................3-49
198087356 NSVC's reception of incorrect NSVCI notification...................................3-49
198087357 NSVC's reception of incorrect NSEI notification .....................................3-50
198087358 NSVC's reception of NS_STATUS_PDU from SGSN notification............3-50
3-2

Chapter 3 Notification
198087359 No access of BSC to MSC SPC.............................................................3-51

198087360 BCCH Exchange Fail .............................................................................3-51
198087393 Ring state notification ............................................................................3-52
198087394 Intelligent power up/down preparation notification ..................................3-52
198087395 SNS Size process failure notification......................................................3-53
198087396 SNS Config process failure notification ..................................................3-53
198087397 SNS Add process failure notification .....................................................3-54
198087398 SNS Delete process failure notification .................................................3-54
198087399 SNS ChangeWeight process failure notification .....................................3-55
198087434 Cannot detect up or down TRAU notification..........................................3-55
198087459 cell no gprs traffic inform ........................................................................3-56
198087466 NSVC's IP deletion notification...............................................................3-56
198087469 abis route change inform .......................................................................3-57
198087477 site board cpu overload..........................................................................3-57
198087478 uplink user layer jam inform ...................................................................3-57
198087479 downlink user layer jam inform...............................................................3-58
198087488 chp cycle adjust trau information............................................................3-58
198087500 Radio Interface Synchronization ARF emendate Successfully ...............3-59
198087501 Radio Interface Synchronization ARF emendate Failed .........................3-59
198087502 Site IP Address conflicted ......................................................................3-60
198087503 Baseband frequency hopping exchange for trx fail .................................3-60
198087504 Baseband frequency hopping exchange for trx restore...........................3-61
198087508 Block Successfully After Service released..............................................3-62
198087512 IDS Attack detecting ..............................................................................3-62
198087514 TRAU frame syn loss notification ...........................................................3-63
198087515 BCCH Exchange Success .....................................................................3-63
198087516 Mute call detect......................................................................................3-63
198087751 dbsapp no avilable PCU resource inform ...............................................3-64
198087754 Board back up ......................................................................................3-64
198087760 BTS master power recover notification...................................................3-65
198087761 BTS master power interruption notification .............................................3-65
198087762 BTS mains power failure, TRX is terminated ..........................................3-66
198087772 Super Site Connect in ............................................................................3-66
198087776 Data error report ....................................................................................3-67
198087798 Codec Fail .............................................................................................3-67
198087799 Cell intelligent power-on or power-down.................................................3-68
198105001 Failed to get the table of configuration ...................................................3-68
198105002 The route table is overloaded.................................................................3-69
198105003 Failed to handle DHCP message from other network .............................3-70
198105004 Failed to operate multicast group ..........................................................3-71
198105005 Clock difference of slave is large............................................................3-71
198105006 Slave losted external clock.....................................................................3-72
198105008 Bandwidth automatic adjustment is useless ...........................................3-72
198105009 No acknowledge of SLA query request ..................................................3-73
198105011 SBCX Application Exception ..................................................................3-73
3-3

198105012 SBCX back card offline ..........................................................................3-74

198105018 Unable to save Performance File ...........................................................3-74
198105019 SLAVE memory check fail notification ....................................................3-75
198105030 OMP received data is not complete........................................................3-76
198105032 Transport Path Occupied BandWidth Overload ......................................3-76
198105033 Transport Path group Occupied Bandwidth Overload.............................3-77
198000576 Loss of Frame on Trunk .........................................................................3-77
198000834 MCC is faulty .........................................................................................3-78
198001600 CPU resets on a board ..........................................................................3-79
198003138 Board FLASH faults ...............................................................................3-79
198003394 Start daylight saving time .......................................................................3-80
198003395 End daylight saving time ........................................................................3-80
3.1 198003649 Shortage of swap block resource

Notification Property
l Notification Code: 198003649
l Description: Shortage of swap block resource
l Severity: Minor
Probable Cause
1. UB configuration is insufficient.
2. For the messages are not processed in time, UBs are occupied for too long time to be released
timely.
System Impact
The link of communnication is broken and all the messages based on the link fail to be send.
Handling Suggestion
Note down the alarm information and contact the next level of maintenance support.
3.2 198005188 UIM CS Changeover

l Description: UIM CS Changeover
l Severity: Minor
3-4

Probable 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.
System Impact
There is no impact on services.
Handling Suggestion
Check if the following alarm occurs in local/opposite board. If yes, refer to the corresponding alarm
handling suggestion.
Related alarms:
198001286 Loss of input clock
198005639 High Error Rate of Optical Interface
198005646 Phase-locked Loop Unlocked
3.3 198005189 Notification of Active/Standby

Changeover
l Description: Notification of Active/Standby Changeover
l Severity: Minor
Probable Cause
It is hardware system fault. The CS domain of the UIM switches over due to artificial operation.
System Impact
The board whose changeover fails will reset automatically.
Handling Suggestion
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.
3-5

3.4 198005192 Board's Work Mode Unsupported

l Description: Board's Work Mode Unsupported
l Severity: Minor
Probable 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.
System Impact
Board master/slave backup function is disabled.
Handling Suggestion
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.
3.5 198005193 Notification of the power on status of

the basic process
l Description: Notification of the power on status of the basic process
l Severity: Minor
Probable Cause
1. Board power-on is successful.

2. Board power-on fails or expires.
System 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.
3-6

Handling Suggestion
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.
3.6 198005194 Changeover of CS Optical Interfaces

l Description: Changeover of CS Optical Interfaces
l Severity: Minor
Probable 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.
System Impact
Data communication error of T Net occurs.
Handling Suggestion
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
3-7

5646 Phase-lock loop unlock
3.7 198005195 Board mix plug occurred

l Description: Board mix plug occurred
l Severity: Minor
Probable 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.
System Impact
Not support to mix plug into shelf, the board can't work normally.
Handling Suggestion
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.
3.8 198005441 Port status on internal media plane

changed
l Description: Port status on internal media plane changed
l Severity: Minor
Probable Cause
1. The connection between UIM/GUIM/GUIM2 and GLI is faulty.

3-8

System 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.
Handling Suggestion
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.
3.9 198005448 485 seriel bus link between CLKG/PWRD

and OMP is broken
l Description: 485 seriel bus link between CLKG/PWRD and OMP is broken
l Severity: Minor
Probable Cause
1. 485 communication is interrupted.
2. The board is abnormal.
System Impact
The configured clock reference/environment threshold fails to take into effect. There is no impact
on services.
Handling Suggestion
1. Unplug and plug the 485 cable.
2. Replace the 485 cable.
3. Replace clock CLKG or environmental monitoring PWRD /fiber access TFI board
3-9

3.10 198005700 DSP resets for abnormities

l Description: DSP resets for abnormities
l Severity: Major
Probable Cause
1. DSP chip on the board that has alarm is faulty.

2. Board is faulty.
System 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.
Handling Suggestion
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.
3.11 198005701 Version Load Error

l Description: Version Load Error
l Severity: Major
Probable 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.
3-10

System 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.
Handling Suggestion
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.
3.12 198005702 Trunk configuration is inconsistent

with function of board
l Description: Trunk configuration is inconsistent with function of board
l Severity: Major
Probable Cause
The board does not support the trunk configuration in the database.
System Impact
The board resets automatically.
3-11

Handling Suggestion
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.
3.13 198005705 MCU resets abnormally

l Description: MCU resets abnormally
l Severity: Major
Probable Cause
MCU Hardware is faulty.
System Impact
CLKG_2 board is faulty.
Handling Suggestion
Replace the alarm board.
3.14 198005708 The active/standby modules of PSN

clock have changed over successfully
l Description: The active/standby modules of PSN clock have changed over
successfully
l Severity: Minor
Probable Cause
It is triggered from the background.
3-12

System Impact
None
Handling Suggestion
No need to handle.
3.15 198005710 The result of manual reference

selection for SETS chip
l Description: The result of manual reference selection for SETS chip
l Severity: Minor
Probable 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.
System Impact
Handling Suggestion
3.16 198005711 Clock reference selection is being

executed
l Description: Clock reference selection is being executed
l Severity: Minor
3-13

Probable 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.
System Impact
Handling Suggestion
3.17 198005712 The manual select base will be run,

please wait for the result
l Description: The manual select base will be run, please wait for the result
l Severity: Minor
Probable 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.
System Impact
Handling Suggestion
3.18 198005713 APC chip's peripheral RAM has

hardware fault
l Description: APC chip's peripheral RAM has hardware fault
3-14

l Severity: Major
Probable Cause
Board hardware is faulty.
System Impact
The alarm board can not be used. ATM cell fails to be forwarded, and all board services are
interrupted.
Handling Suggestion
Replace the alarm board.
3.19 198005714 No external clock for DSP

l Description: No external clock for DSP
l Severity: Minor
Probable 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.
System Impact
None
Handling Suggestion
Check the clock.
3.20 198005715 PP2S source switched

l Description: PP2S source switched
l Severity: Minor
3-15

Probable Cause
PP2S (Pulse Per 2 Seconds) source is switched at both system clock and GPS receiver sides.
System Impact
Handling Suggestion
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.
3.21 198005718 Two master clock ports is directly

connected
l Description: Two master clock ports is directly connected
l Severity: Minor
Probable Cause
Two ports which are configured as synchronous Ethernet master clock port are directly connected.
System 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.
Handling Suggestion
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.
3.22 198005956 Board Version Error

l Description: Board Version Error
l Severity: Minor
3-16

Probable 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.
System Impact
The board fails to obtain version, leading to abnormal board operation and access failure of board
services.
Handling Suggestion
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.
3.23 198005958 IDE Version Files Synchronization

Information
l Description: IDE Version Files Synchronization Information
l Severity: Minor
Probable Cause
Synchronization of master/slave OMP version files occurs.
System 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
Handling Suggestion
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.
3-17

3.24 198005960 Version Fails to Be Switched

l Description: Version Fails to Be Switched
l Severity: Minor
Probable Cause
The slave board have some master processes when update the EPLD.
System Impact
EPLD upgrade fails.
Handling Suggestion
Switch some active functions (such as optical interfaces) to standby ones on the standby board
through MML command operation.Switch again after the operation.
3.25 198005961 OMP Version Check Information

l Description: OMP Version Check Information
l Severity: Minor
Probable Cause
The version file in software version configuration does not exist in RNC NE.
System 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.
Handling Suggestion
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.
3-18

3.26 198005962 Patch version operate fail

l Description: Patch version operate fail
l Severity: Minor
Probable 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.
System Impact
Patch version activation fails. New functions of the patch version are unavailable. No impact on
service.
Handling Suggestion
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.
3.27 198008005 Memory file buffer overflow

l Description: Memory file buffer overflow
l Severity: Minor
Probable Cause
The transferred data records exceed the maximum capacity of the table, and the capacity of the
receiver memory file buffer is insufficient.
System Impact
If the board is powering on, the excessive data records (beyond table capacity) are discarded.
3-19

Handling Suggestion
Delete the excessive data records of the false table.
3.28 198011840 M3UA user office status change

l Description: M3UA user office status change
l Severity: Major
Probable 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.
System 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.
Handling Suggestion
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
198066019 Association link broken
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.
3.29 198013888 ASP status changed

l Description: ASP status changed
l Severity: Minor
3-20

Probable 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.
System 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.
Handling Suggestion
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.
3.30 198013889 AS status changed

l Description: AS status changed
l Severity: Minor
Probable 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.
System 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.
3-21

Handling Suggestion
1. Check whether association interruption alarm occurs. If yes, refer to the corresponding alarm
2. Activate ASP under the AS in dynamic data management.
3.31 198013890 Sigtran error message received

l Description: Sigtran error message received
l Severity: Minor
Probable Cause
1. AS configuration is wrong.
2. Protocol versions used at both sides are different.
System 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.
Handling Suggestion
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.
3-22

3.32 198013891 Sigtran notification message received

l Description: Sigtran notification message received
l Severity: Minor
Probable 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.
System 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.
Handling Suggestion
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.
3.33 198013892 Allocate memory fail

l Description: Allocate memory fail
l Severity: Minor
Probable Cause
Memory is insufficient, that result in dynamic memory allocation failure when the processor is
powered on.
3-23

System Impact
If Application Server/Application Server Process is not configured on this board, system will not
be affected. Or else process will be unstable.
Handling Suggestion
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.
3.34 198014144 Association establishment failed

l Description: Association establishment failed
l Severity: Major
Probable 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.
System 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.
Handling Suggestion
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-24

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.
3.35 198014145 Association restart

l Description: Association restart
l Severity: Minor
Probable 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.
System Impact
No impact.
Handling Suggestion
No handling is necessary,wait association to restart
3.36 198016193 SIG_IPI Forwards Service Messages

Abnormally
l Description: SIG_IPI Forwards Service Messages Abnormally
l Severity: Major
Probable Cause
1. Association is not configured on the SIPI board.

2. The hardware of the SIPI board is faulty.
3. Transmission network is faulty.
3-25

System 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.
Handling Suggestion
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.
3.37 198017216 Error in MCS Multi-Core processor

receiving configuration data from DBS
l Description: Error in MCS Multi-Core processor receiving configuration data from DBS
l Severity: Major
Probable Cause
1. The configuration data from DBS are exceptional.

2. Failure in adding a vital data table.
System Impact
It may cause packet forwarding problem since some vital data table is absent.
Handling Suggestion
Check the data configuration, if there is a configuring error, correct it and reboot the board.
3.38 198018241 TCP Connection Aborted

l Description: TCP Connection Aborted
l Severity: Major
3-26

Probable Cause
1. Network communication faults

2. The peer end shut down this TCP connection normally or abnormally.
3. Peer-end device faults.
System Impact
The corresponding connection aborts.
Handling Suggestion
Check if there is severe packet loss in physical link (It can be checked by ping command), and
handle physical link faults.
3.39 198018242 MD5 Verification Failure

l Description: MD5 Verification Failure
l Severity: Minor
Probable Cause
MD5 verification is not set for packets in application layer.
System Impact
Application layer communication failure
Handling Suggestion
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.
3.40 198018243 Wrong MD5 Message Abstract

l Description: Wrong MD5 Message Abstract
l Severity: Minor
3-27

Probable Cause
When application layer is receiving messages, MD5 cryptographic keys set on both ends are
inconsistent.
System Impact
Application layer communication failure
Handling Suggestion
Set the same MD5 cryptographic keys for both ends of application layer. The application layer
protocol includes BGP and LDP.
3.41 198018755 HDLC status changed

l Description: HDLC status changed
l Severity: Major
Probable Cause
1. This notification occurs when an HDLC is created.

2. The link is broken or recovered.
System 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.
Handling Suggestion
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.
3-28

3.42 198019777 APS switch over occurred

l Description: APS switch over occurred
l Severity: Minor
Probable 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.
System Impact
During APS changeover process, the link is interrupted for 10 ~ 50 ms. Few packets may be lost, but
services won't be affected.
Handling Suggestion
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.
3.43 198020291 Protocol stack process failed to

initialize during power on
l Description: Protocol stack process failed to initialize during power on
l Severity: Major
3-29

Probable Cause
Physical memory is insufficient.
System Impact
RPU board will reboot automatically after 10 seconds.
Handling Suggestion
Ensure that the actual capacity of the physical memory is more than 1GB.
3.44 198020802 Conflicting IP address in subnet

l Description: Conflicting IP address in subnet
l Severity: Minor
Probable 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.
System Impact
Board operation is normal. Communication network is faulty. All services on this port are down.
Handling Suggestion
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.
3-30

3.45 198020803 Conflicting MAC address in subnet

l Description: Conflicting MAC address in subnet
l Severity: Minor
Probable 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.
System 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.
Handling Suggestion
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.
3.46 198020804 Failed to generate static ARP from IP

address
l Description: Failed to generate static ARP from IP address
l Severity: Minor
3-31

Probable 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).
System Impact
The external device failed to communicate with the IP address from which no static ARP is generated.
Handling Suggestion
Delete some proxy addresses configured for virtual ports and re-configure IP address within the limit
of static ARPs.
3.47 198020805 ARP detect failed

l Description: ARP detect failed
l Severity: Minor
Probable 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.
System Impact
The communication will be interrupted possibly.
Handling Suggestion
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.
3-32

3.48 198020806 ARP detect that the static ARP is not

match
l Description: ARP detect that the static ARP is not match
l Severity: Minor
Probable 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.
System Impact
The communication will be interrupted possibly.
Handling Suggestion
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.
3.49 198021059 RIP Neighbor Configuration Errors

l Description: RIP Neighbor Configuration Errors
l Severity: Minor
Probable Cause
When adding a neighbor, the address of the neighbor mismatches with that of the interface.
System Impact
The dynamic route expected to be obtained from this neighbor fails to be established.
3-33

Handling Suggestion
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".
N->If not, go to "2".
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.
3.50 198021060 RIP Interface Authentication Errors

l Description: RIP Interface Authentication Errors
l Severity: Minor
Probable Cause
When the interface needs to be authenticated, the authentication code is wrong.
System Impact
RIP messages cannot be properly received.
Handling Suggestion
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.
3.51 198021065 Incompatible RIP Version Number

l Description: Incompatible RIP Version Number
l Severity: Minor
3-34

Probable Cause
The version number of the interface on remote device is inconsistent with that on local device.
System Impact
RIP messages cannot be properly received.
Handling Suggestion
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.
3.52 198021329 LSDB Overflow

l Description: LSDB Overflow
l Severity: Major
Probable Cause
The LSDB (Link Status Database) overflows.
System Impact
LSA addition failure and LSDB synchronization failure
Handling Suggestion
1.Configure route aggregation to reduce the number of LSAs. Check if the alarm is eliminated.
Y->If so, finish the alarm handling.
3.53 198021330 Configuration of OSPF mismatched

l Description: Configuration of OSPF mismatched
l Severity: Minor
3-35

Probable Cause
Configuration mismatched, OSPF cannot run in normal.
System Impact
Route learning and calculation failure
Handling Suggestion
1.To modify the relevant configuration of OSPF and make them are coordinated. Check if the alarm is
eliminated.
3.54 198021331 Failed to add the ospf route to the

courier routing table
l Description: Failed to add the ospf route to the courier routing table
l Severity: Major
Probable Cause
Failed to add the ospf routes to the dynamic protocol routing table for overflowing
System Impact
OSPF route lost
Handling Suggestion
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.
3-36

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.
3.55 198021584 Neighbor Hold Timer Expired

l Description: Neighbor Hold Timer Expired
l Severity: Minor
Probable Cause
1. The physical link is interrupted.
2. TCP connection is interrupted.
System Impact
BGP session is disconnected.
Handling Suggestion
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.
3.56 198021585 BGP Interface Down and Neighbor Link

Broken
l Description: BGP Interface Down and Neighbor Link Broken
l Severity: Major
Probable Cause
Message 'local interface is down' is received.
3-37

System Impact
The session of the BGP neighbor on this interface is unavailable.
Handling Suggestion
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.
3.57 198021837 Failure in adding dynamic routings

l Description: Failure in adding dynamic routings
l Severity: Major
Probable Cause
Forwarding table overflow causes the failure in adding routes.
System Impact
Dynamic route loss occurs.
Handling Suggestion
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.
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.
3-38

3.58 198022598 Routers with Conflicting System Id

Exist in Network
l Description: Routers with Conflicting System Id Exist in Network
l Severity: Minor
Probable Cause
In ISIS instance configuration under protocol stack configuration mode, System-id has wrong
configuration.
System Impact
ISIS neighbor status fails to be established between the neighboring routers whose system IDs
conflict.
Handling Suggestion
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.
3.59 198022599 ISIS Message Authentication Failure

l Description: ISIS Message Authentication Failure
l Severity: Minor
Probable Cause
Message authentication modes or keys configured on the routers of the two ends are inconsistent.
System Impact
The message that fails to be authenticated is omitted. The local router can not synchronize the
LSDB with the corresponding router.
3-39

Handling Suggestion
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.
3.60 198023106 Board self-check fails

l Description: Board self-check fails
l Severity: Minor
Probable Cause
System Impact
The board fails to power on possibly, and the service or communication link related to this board is
down.
Handling Suggestion
Replace the board.
3.61 198023107 The board initialization failure

l Description: The board initialization failure
l Severity: Minor
3-40

Probable Cause
System Impact
The board fails to be powered on. As a result, UE can not be accessed and existing services are
interrupted.
Handling Suggestion
Replace the board.
3.62 198023617 Configuration file is unusable

l Description: Configuration file is unusable
l Severity: Major
Probable 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.
System 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.
Handling Suggestion
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.
3-41

3.63 198025664 Abnormal Half-Fixed Connection

Changes
l Description: Abnormal Half-Fixed Connection Changes
l Severity: Major
Probable Cause
1. Abnormal jitter occurs to the line clock of the shelf where the board is located.
System Impact
TMD channel is interrupted momentarily, which may have a slight impact on services.
Handling Suggestion
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.
3.64 198026176 Clock reference changed

l Description: Clock reference changed
l Severity: Minor
Probable Cause
The currently locked clock reference has changed.
System Impact
3-42

Handling Suggestion
No need to handle.
3.65 198026177 CLKG reference quality changed

l Description: CLKG reference quality changed
l Severity: Minor
Probable Cause
Clock quality of the CLKG board has changed.
System Impact
The system may not get the needed clock.
Handling Suggestion
Check the quality of external clock source.
3.66 198026178 Clock work mode changed

l Description: Clock work mode changed
l Severity: Minor
Probable Cause
The clock work mode of the CLKG board has changed.
System Impact
The system may not get the needed clock.
Handling Suggestion
No need to handle.
3-43

3.67 198026179 Clock source invalidation reason

changed
l Description: Clock source invalidation reason changed
l Severity: Minor
Probable Cause
The clock reference becomes invalid.
System Impact
Handling Suggestion
No need to handle.
3.68 198028231 Router ID not configured for OSPFv3

l Description: Router ID not configured for OSPFv3
l Severity: Minor
Probable Cause
Router ID not configured for OSPFv3.
System Impact
OSPFv3 Instance creation failure
Handling Suggestion
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
Y->End.
3-44

3.69 198028233 Configuration of OSPFv3 Mismatched

l Description: Configuration of OSPFv3 Mismatched
l Severity: Minor
Probable Cause
Cannot learn and calculate route.
System Impact
Route learning and calculation failure
Handling Suggestion
1.To modify the relevant configuration of OSPF and make them are coordinated. Check if the alarm is
eliminated.
3.70 198028993 SCTP Primary Path Set Failed

l Description: SCTP Primary Path Set Failed
l Severity: Minor
Probable 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
System 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.
3-45

Handling Suggestion
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.
3.71 198029760 DNS server inaccessible

l Description: DNS server inaccessible
l Severity: Minor
Probable Cause
DNS server makes no response, so the link may be broken or the DNS server is down.
System Impact
DNS client does not work.
Handling Suggestion
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.
3.72 198030016 Ethernet link OAM event

l Description: Ethernet link OAM event
l Severity: Major
3-46

Probable Cause
The number of wrong frames or wrong symbols exceeds the threshold.
System Impact
Ethernet links can not transmit data credibly.
Handling Suggestion
Check Ethernet link, receiver and transmitter of link.
3.73 198031040 ACL config failed

l Description: ACL config failed
l Severity: Minor
Probable Cause
BRS protocol processes ACL configuration data which synchronized by DBS from ACL offline
configuration failed.
System Impact
The ACL configuration data will not take effect.
Handling Suggestion
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.
3.74 198087338 TRX No Traffic

l Description: TRX No Traffic
l Severity: Minor
3-47

Probable Cause
Cell No Traffic
System Impact
None
Handling Suggestion
None
3.75 198087339 BTS self maintenance inform

l Description: BTS self maintenance inform
l Severity: Minor
Probable Cause
BTS Board Reboot
System Impact
None
Handling Suggestion
None
3.76 198087353 NSVC deletion notification

l Description: NSVC deletion notification
l Severity: Minor
Probable Cause
A NSVC link is deleted.
3-48

System Impact
None
Handling Suggestion
This notification is generated when a NSVC link is deleted. Check whether the NSVC link is the one
that should be deleted. If it is, no handlings are required.
3.77 198087355 Timeout notification for a database to

return value
l Description: Timeout notification for a database to return value
l Severity: Minor
Probable Cause
The timer is exipired when waiting for the response from database.
System Impact
The user is notified that problem exists during the process of downloading data configuration.
Handling Suggestion
Check whether the OMP board is running normally. If it is, no handlings are required.
3.78 198087356 NSVC's reception of incorrect NSVCI

notification
l Description: NSVC's reception of incorrect NSVCI notification
l Severity: Minor
Probable Cause
The link receives incorrect NSVCI.
3-49

System Impact
The NS_RESET process terminates abnormally
Handling Suggestion
Check whether the NSVC configuration at BSC is consistent with that at SGSN. If they are
inconsistent, modify the two configurations to make them consistent. If they are consistent, notify
SGSN to handle the problem.
3.79 198087357 NSVC's reception of incorrect NSEI

notification
l Description: NSVC's reception of incorrect NSEI notification
l Severity: Minor
Probable Cause
The link receives incorrect NSEI.
System Impact
The NS_RESET process terminates abnormally.
Handling Suggestion
Check whether the NSVC configuration at BSC is consistent with the NSEI configuration at SGSN. If
they are inconsistent, modify the two configurations to make them consistent. If they are consistent,
notify SGSN to handle the problem.
3.80 198087358 NSVC's reception of NS_STATUS_PDU

from SGSN notification
l Description: NSVC's reception of NS_STATUS_PDU from SGSN notification
l Severity: Minor
3-50

Probable Cause
The link receives the NS_STATUS_PDU message from SGSN.
System Impact
The user is notified that a NS_STATUS_PDU message is received.
Handling Suggestion
Check the notification details.

If the cause code is 5 (i.e. incorrect BVCI), check whether the BVC status at BSC is consistent with
that at SGSN. If they are inconsistent, initiate the signaling BVC resetting; otherwise, notify SGSN to
handle the problem.
If the cause code is other value, no handlings are required.
3.81 198087359 No access of BSC to MSC SPC

l Description: No access of BSC to MSC SPC
l Severity: Minor
Probable Cause
BSC is not configured with MSC office type.
System Impact
The logical connection between BSC and MSC is broken, and BSC can not send signaling
information to MSC.
Handling Suggestion
Configure the MSC office type for BSC.
3.82 198087360 BCCH Exchange Fail

l Description: BCCH Exchange Fail
l Severity: Minor
3-51

Probable Cause
1. BCCH switching is configured as not allowed.

2. Operation on destination TRX fails during BCCH switching.
3. Data synchronization between BSC NE and NMS occurs.
4. Can not find the suitable target TRX.
System Impact
Voice and data services are down in the cell.
Handling Suggestion
1. Check the configuration of BCCH switch allowed.

2. Check if the destination TRX of BCCH switching works normally. query the TRX status on TRX
Management tab. Unblock the faulty TRX.
3.83 198087393 Ring state notification

l Description: Ring state notification
l Severity: Minor
Probable Cause
The ring network state has changed.
System Impact
None
Handling Suggestion
None
3.84 198087394 Intelligent power up/down preparation

notification
l Description: Intelligent power up/down preparation notification
3-52

l Severity: Minor
Probable Cause
The carrier's power-up/power-down state has changed.
System Impact
None
Handling Suggestion
None
3.85 198087395 SNS Size process failure notification

l Description: SNS Size process failure notification
l Severity: Minor
Probable Cause
There is no response from SGSN, or the failure response is received.
System Impact
The user is notified that the SNS Size process fails.
Handling Suggestion
Check NSE and end-node data to ensure that they are correct.
3.86 198087396 SNS Config process failure notification

l Description: SNS Config process failure notification
l Severity: Minor
Probable Cause
3-53

System Impact
The user is notified that the SNS Config process fails.
Handling Suggestion
3.87 198087397 SNS Add process failure notification

l Description: SNS Add process failure notification
l Severity: Minor
Probable Cause
System Impact
The user is notified that the SNS Add process fails.
Handling Suggestion
3.88 198087398 SNS Delete process failure notification

l Description: SNS Delete process failure notification
l Severity: Minor
Probable Cause
System Impact
The user is notified that the SNS Delete process fails.
3-54

Handling Suggestion
3.89 198087399 SNS ChangeWeight process failure

notification
l Description: SNS ChangeWeight process failure notification
l Severity: Minor
Probable Cause
System Impact
The user is notified that the SNS ChangeWeight process fails.
Handling Suggestion
3.90 198087434 Cannot detect up or down TRAU

notification
l Description: Cannot detect up or down TRAU notification
l Severity: Minor
Probable Cause
Cannot detect up or down TRAU
System Impact
None
3-55

Handling Suggestion
None
3.91 198087459 cell no gprs traffic inform

l Description: cell no gprs traffic inform
l Severity: Minor
Probable Cause
Data service is down for one hour in the cell.
System Impact
Handling Suggestion
3.92 198087466 NSVC's IP deletion notification

l Description: NSVC's IP deletion notification
l Severity: Minor
Probable Cause
A NSVC's IP link is deleted.
System Impact
None
Handling Suggestion
This notification is generated when a NSVC link is deleted. Check whether the NSVC link is the one
that should be deleted. If it is, no handlings are required.
3-56

3.93 198087469 abis route change inform

l Description: abis route change inform
l Severity: Minor
Probable Cause
Abis route of the site satellite-backuped changed
System Impact
None
Handling Suggestion
None
3.94 198087477 site board cpu overload

l Description: site board cpu overload
l Severity: Major
Probable Cause
CMB/DTPU/FIB CPU usage rate over 80%
System Impact
None
Handling Suggestion
None
3.95 198087478 uplink user layer jam inform

3-57

l Description: uplink user layer jam inform

l Severity: Minor
Probable Cause
Uplink data in user layer is jaming
System Impact
None
Handling Suggestion
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.
3.96 198087479 downlink user layer jam inform

l Description: downlink user layer jam inform
l Severity: Minor
Probable Cause
Downlink data in user layer is jaming
System Impact
None
Handling Suggestion
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.
3.97 198087488 chp cycle adjust trau information

l Description: chp cycle adjust trau information
3-58

l Severity: Minor
Probable Cause
13MHz clock of Um is unsynchronized with HW 8K clock on DTRU.
System Impact
Reduce CS, PS performance.
Handling Suggestion
1) In E1 Abis mode, be sure 'clock synchronization' is network synchronization.

2) In IP Abis mode, check CMM FPGA version.
3.98 198087500 Radio Interface Synchronization ARF

emendate Successfully
l Description: Radio Interface Synchronization ARF emendate Successfully
l Severity: Minor
Probable Cause
Search Radio Interface Synchronization Successfully.
System Impact
None
Handling Suggestion
Check the display of the value of ARFCN at OMM.
3.99 198087501 Radio Interface Synchronization ARF

emendate Failed
l Description: Radio Interface Synchronization ARF emendate Failed
3-59

l Severity: Minor
Probable Cause
Search Radio Interface Synchronization Failed.
System Impact
Cannot execute the 26M CLK adjust
Handling Suggestion
Check the reason of failure at iOMCR:

0x01 No suitable Arfcn
0x02 Radio Synchronization failed
0x03 Other.
3.100 198087502 Site IP Address conflicted

l Description: Site IP Address conflicted
l Severity: Minor
Probable Cause
Site IP Conflict
System Impact
Site cannot work normally
Handling Suggestion
Remodify the IP of site
3.101 198087503 Baseband frequency hopping

exchange for trx fail
l Description: Baseband frequency hopping exchange for trx fail
3-60

l Severity: Minor
Probable Cause
Baseband frequency hopping

trx failed and remove form hoping group by system
System Impact
When Baseband frequency hopping

is used, if one of the TRX is faulty, the system will remove it from the hopping group to keep the rest
of the healthy TRX working properly
Handling Suggestion
When Baseband frequency hopping

is used, if one of the TRX is faulty, you should remove it from the hopping group and synchronize
the configuration.If not do this, iBSC database is not same with OMM database, and will see this
information again, if you synchronize the failure trx.
3.102 198087504 Baseband frequency hopping

exchange for trx restore
l Description: Baseband frequency hopping exchange for trx restore
l Severity: Minor
Probable Cause
Baseband frequency hopping

trx restore and add in hoping group again by system
System Impact
When Baseband frequency hopping is used, if one of the TRX is restore, the system will add the
recovered TRX back to its hopping group.
Handling Suggestion
none
3-61

3.103 198087508 Block Successfully After Service

released
l Description: Block Successfully After Service released
l Severity: Minor
Probable Cause
1.Block successfully after service released

2.Bcch exchange while waiting for release service, and the object is bolcked forced
3.time out, and the object is bolcked forced
System Impact
The last two issue will lead interrupting of service.
Handling Suggestion
none
3.104 198087512 IDS Attack detecting

l Description: IDS Attack detecting
l Severity: Minor
Probable Cause
IDS detecting the network attacking
System Impact
User define
Handling Suggestion
None
3-62

3.105 198087514 TRAU frame syn loss notification

l Description: TRAU frame syn loss notification
l Severity: Minor
Probable Cause
The quality of voice is bad on this voice path
System Impact
None
Handling Suggestion
None
3.106 198087515 BCCH Exchange Success

l Description: BCCH Exchange Success
l Severity: Minor
Probable Cause
BCCH switching is Success.
System Impact
None
Handling Suggestion
None
3.107 198087516 Mute call detect

3-63

l Description: Mute call detect

l Severity: Minor
Probable Cause
No voice data on this voice path.
System Impact
None
Handling Suggestion
None
3.108 198087751 dbsapp no avilable PCU resource

inform
l Description: dbsapp no avilable PCU resource inform
l Severity: Minor
Probable Cause
When Cell selected PCU resource in OMP, There is no aviable resource to use.
System Impact
Some Cells can't provide data service
Handling Suggestion
1.Config more PCU resource on configuration management interface.

2.Recover the fault PCU
3.109 198087754 Board back up

l Description: Board back up
l Severity: Major
3-64

Probable Cause
1.Back up because of Sunit fault.

2.Back up because of Sunit normal.
3.Back up because of OMM operating.
System Impact
None
Handling Suggestion
None
3.110 198087760 BTS master power recover notification

l Description: BTS master power recover notification
l Severity: Minor
Probable Cause
BTS master power recover notification
System Impact
None
Handling Suggestion
3.111 198087761 BTS master power interruption

notification
l Description: BTS master power interruption notification
l Severity: Minor
3-65

Probable Cause
BTS master power interruption notification
System Impact
None
Handling Suggestion
3.112 198087762 BTS mains power failure, TRX is

terminated
l Description: BTS mains power failure, TRX is terminated
l Severity: Minor
Probable Cause
BTS mains power failure, TRX is terminated
System Impact
None
Handling Suggestion
3.113 198087772 Super Site Connect in

l Description: Super Site Connect in
l Severity: Major
Probable Cause
Link of Super Site Changes
3-66

System Impact
None
Handling Suggestion
None
3.114 198087776 Data error report

l Description: Data error report
l Severity: Major
Probable Cause
Check out data error When call the data base interface.
System Impact
None
Handling Suggestion
Find out the source of err data and recover the data base the information
3.115 198087798 Codec Fail

l Description: Codec Fail
l Severity: Major
Probable Cause
Codec Fail
System Impact
None
3-67

Handling Suggestion
Check cell configration, make sure that Number of Neighbour Cells and ARFCNs in BA/CA list is
suitable. If it's too many, delete some of them. Reconfigure the cell.
3.116 198087799 Cell intelligent power-on or

power-down
l Description: Cell intelligent power-on or power-down
l Severity: Minor
Probable Cause
The Cell power-up/power-down state has changed.
System Impact
None
Handling Suggestion
None
3.117 198105001 Failed to get the table of configuration

l Description: Failed to get the table of configuration
l Severity: Minor
Probable Cause
MicroCode subsystem failed to get the table of configuration from database subsystem during the
power on procedure, or failed to update the table of configuration.
3-68

System Impact
The system impacts that correspond to different alarm causes are described below.
1. Failed to get the information of the reassemble board.
The configuration information is used to reassemble the fragments of IP packets inputted into the
equipment. Lacking the configuration information may cause processing failure of fragments of IP
packets. Service interruption might occur or service processing rate might slow down.
2. Failed to get the configuration of OMCB server.
Lacking the configuration information may paralyze OMCB function.
3. Failed to get the configuration of signal dispatch table.
Lacking the configuration information causes SCTP data transmission failure on the interface board.
The service related to SCTP Protocol on this board is down.
4. Failed to get the configuration of IP/UDP.
Lacking the configuration information may cause processing failure of IUPS service, or processing
failure of other data based on IP transmission.
5. Failed to get the configuration of L2 table.
Lacking the configuration information may cause communication failure within the equipment. All
services on the board might be down.
6. Failed to get the configuration of path information.
In the case of ATM interface board, lacking the configuration information may incur processing failure
of the AAL2 data based on ATM Adaptation Layer Protocol, leading to interruption of IUB/IUCS/IUR
services under this office.
In the case of IP interface board, lacking the configuration information may incur processing failure of
IP packet traffic control, leading to interruption of all services under this office.
7. Failed to get the configuration of pathgroup information.
In the case of ATM interface board, lacking the configuration information may incur processing failure
of the AAL2 data based on ATM Adaptation Layer Protocol, leading to interruption of IUB/IUCS/IUR
services under this office.
In the case of IP interface board, service is not affected.
Handling Suggestion
The operator should add the configuration or re-synchronize the configuration according to the
addition information of this report.
3.118 198105002 The route table is overloaded

l Description: The route table is overloaded
l Severity: Minor
3-69

Probable Cause
There are too many configured route entries

For RUB board (VTCD), the table can contain at most 360 route entries. For RUB board (VTCD_2),
the table can contain at most 1024 route entries. The alarm is declared when the number of route
entries reaches 90% of the table capacity threshold.
System Impact
1.If the number of route entries does not exceed the RUB board route table capacity, service will
not be affected.
2.If the number of route entries exceeds the RUB board route table capacity, information of some
route entries will be lost.
1) If the missing route are the route to Node B or CN, UE service access to the board will fail.
2) If the missing route are the route to other RNC NE, access of Inter-RNC UE services to the board
will fail. Meanwhile, tick clock synchronization of the MBMS service between the relevant RNC NEs
will fail, degrading the MBMS service quality
3.If the number of route entries exceeds the RUB board route table capacity, the SLA diagnostic test
function from RNC to related NE will be disabled.
Handling Suggestion
1. On NMS configuration management interface (static route), delete the routes that are not in use.
2. On NMS configuration management interface (interface configuration), delete the port IP that is
no longer in use.
3.119 198105003 Failed to handle DHCP message from

other network
l Description: Failed to handle DHCP message from other network
l Severity: Minor
Probable Cause
Failed to assign DHCP Configuration to Client, may be one of the following causes:
1) OMCB Server Ip Configuration Absent
2) Peer Ip Address of PPP Link Absent
3) RNC Omcb Service Ip of Node Operation and Maintain Absent
4) Failed to Get Client DHCP Configuration from DBS
3-70

System Impact
DHCP Client can not get it's DHCP Configuration Information
Handling Suggestion
1) Check whether configed OMCB Server IP, if not, config it.

2) Check whether configed Peer IP of PPP/MLPPP Link, if not, config it.
3) Check whether configed RNC Omcb Service Ip of Node Operation and Maintain, if not, config it.
4) Check whether DHCP Configuration of Client is correct, if not, correct it.
3.120 198105004 Failed to operate multicast group

l Description: Failed to operate multicast group
l Severity: Minor
Probable Cause
Failed to join to Mulicast group of Link Trace
System Impact
Link Trace Function can not work
Handling Suggestion
contect with engneers of OSS
3.121 198105005 Clock difference of slave is large

l Description: Clock difference of slave is large
l Severity: Minor
Probable Cause
1. Clock Deviation between Slave and Host over threshold(default threshold 36sec/hr)
2. Clock crystal oscillator of Slave or Host is inaccurate
3-71

System Impact
KPI Index of Service in RNC will be low
Handling Suggestion
Block the Slave reported in the notification, and inform hardware manager
3.122 198105006 Slave losted external clock

l Description: Slave losted external clock
l Severity: Minor
Probable Cause
External Clock of Slave Lost
System Impact
KPI Index of Service in RNC will be low
Handling Suggestion
Block the Slave reported in the notification, and inform hardware manager
3.123 198105008 Bandwidth automatic adjustment is

useless
l Description: Bandwidth automatic adjustment is useless
l Severity: Minor
Probable Cause
Adjust the transmission path bandwidth to the low thehold can not radically improve packet loss
rate of this path.
3-72

System Impact
The packet loss rate higher than the reference value will depress the quality of service (QoS), even
lead to the access failure and service disconnection.
Handling Suggestion
Check the intermediate equipment between RNC and peer NE, make sure the intermediate
equipment runs normally .
3.124 198105009 No acknowledge of SLA query request

l Description: No acknowledge of SLA query request
l Severity: Minor
Probable Cause
Not recived the SLA query request.
System Impact
IPBM can not recive the SLA acknowledge,the function of the band width adjust is useless.
Handling Suggestion
Check the state of interface board is normal, the PD query entity is exsit.
3.125 198105011 SBCX Application Exception

l Description: SBCX Application Exception
l Severity: Major
Probable Cause
Log Server Application has exception
System Impact
NONE
3-73

Handling Suggestion
Check the status of Log-Server or whether the Log service is running
3.126 198105012 SBCX back card offline

l Description: SBCX back card offline
l Severity: Minor
Probable Cause
Back card has been take off.
System Impact
SBCX cant link to client.
Handling Suggestion
Check whether the back card is offline
3.127 198105018 Unable to save Performance File

l Description: Unable to save Performance File
l Severity: Minor
Probable Cause
1. The disk space of logservice is less than 500M.

2. The disk space of OMP is less than 500M.
3. The communication link between OMM and OMP is broken more than 2 hours.
4. The communication link between Logservice and OMP is broken more than 3 days.
5. The version of OMP and logservice is incompatible.
6. The time of OMP adjusted.
3-74

System Impact
Either the LogService or the OMP cannot save the performance files. Performance data will be lost.
It has no impact on services.
Handling Suggestion
Check alarm details to find the Failure cause during saving performance file, and handle the alarm
accordingly.
1. If the Failure cause is "Logservice disk space less than 500M", delete unnecessary files from
the Logservice disk to release enough space.
2. If the Failure cause is "Directory on Logservice is different from that on OMP", it means the
Logservice version is incompatible with the OMP version. Use the correct Logservice version.
3. If the Failure cause is "Logservice is unavailable and the space of OMP disk is less than 500M"
1) Delete unnecessary files from the OMP disk to release enough space.
2) Handle it according to the suggestions given for the alarm "198083028 Logservice is unavailable".
4. If the Failure cause is "The session ends abnormally and the performance file can not be saved", it
means the board time has been adjusted. In this case, no handling is required.
5. If the Failure cause is "The Logservice is unavailable, and the PM files have already existed for
over two hours.", the suggestion is given for the alarm "198083028 Logservice is unavailable".
3.128 198105019 SLAVE memory check fail notification

l Description: SLAVE memory check fail notification
l Severity: Minor
Probable Cause
SLAVE memory check fail
System Impact
Handling Suggestion
Reset the Slave reported in the notification.
3-75

3.129 198105030 OMP received data is not complete

l Description: OMP received data is not complete
l Severity: Minor
Probable Cause
MP can not finish transfering data to OMP in five minutes.
System Impact
Performance file is not complete, the counter value is not accurate.
Handling Suggestion
Check communication status between CMP, DMP and OMP.
3.130 198105032 Transport Path Occupied BandWidth

Overload
l Description: Transport Path Occupied BandWidth Overload
l Severity: Minor
Probable Cause
Available bandWidth of transport path is less than occupied bandWidth. Probable causes for the
alarm include:
1.E1 link is broken.
2.Transmission quality of the transmission line is poor.
3.Intermediate equipment is faulty.
System Impact
The available bandwidth to destination is less than occupied bandwidth. Some services would be
released in this transport path selectively to avoid transport path congestion.
3-76

Handling Suggestion
1.Check the E1 link.

2.Check the transmission quality of intermediate equipment.
3.131 198105033 Transport Path group Occupied

Bandwidth Overload
l Description: Transport Path group Occupied Bandwidth Overload
l Severity: Minor
Probable Cause
Available bandwidth of transport path group is less than occupied bandwidth. Probable causes
for the alarm include:
1.E1 link is broken.
2.Transmission quality of the transmission line is poor.
3.Intermediate equipment is faulty.
System Impact
The available bandwidth to destination is less than occupied bandwidth.So service rate on this
path group will be degraded.
Handling Suggestion
1.Check the E1 link.

2.Check the transmission quality of intermediate equipment.
3.132 198000576 Loss of Frame on Trunk

l Description: Loss of Frame on Trunk
l Severity: Minor
3-77

Probable 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.
System 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.
Handling Suggestion
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
Related alarms:
3.133 198000834 MCC is faulty

l Description: MCC is faulty
l Severity: Major
Probable Cause
MCC Hardware is faulty.
System Impact
All MCC channels cannot transmit or receive data.
Handling Suggestion
1. Unplug the board for 5 seconds, and plug it again after a full discharge.
3-78

3.134 198001600 CPU resets on a board

l Description: CPU resets on a board
l Severity: Major
Probable 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.
System Impact
The relevant services or communication links will be interrupted or disconnected. This alarm will be
recovered after the board is powered on normally.
Handling Suggestion
1. Check the NMS operation log to see whether there is a manual reset record. If yes, no handling is
necessary.
3.135 198003138 Board FLASH faults

l Description: Board FLASH faults
l Severity: Major
Probable Cause
The flash on the board is damaged.
System 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.
3-79

Handling Suggestion
Replace the board.
3.136 198003394 Start daylight saving time

l Description: Start daylight saving time
l Severity: Minor
Probable Cause
Daylight saving time activated, clock changed accordingly.
System Impact
No impact
Handling Suggestion
3.137 198003395 End daylight saving time

l Description: End daylight saving time
l Severity: Minor
Probable Cause
Daylight saving time is de-activated and the system is back to normal country clock.
System Impact
No impact
Handling Suggestion
3-80

Glossary
CPU
- Central Processing Unit
DSP
- Digital Signal Processing
FPGA
- Field Programmable Gate Array

SJ-20130408113951-012-ZXG10 IBSC (V6.30.103) Alarm and Notification Handling Reference

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

SJ-20130408113951-012-ZXG10 IBSC (V6.30.103) Alarm and Notification Handling Reference

Transféré par

Droits d'auteur :

Formats disponibles

ZXG10 iBSC

Base Station Controller

Revision No. Revision Date Revision Reason

R1.0 20130604 First edition

Serial Number: SJ-20130408113951-012

Publishing Date: 20130604 (R1.0)

SJ-20130408113951-012|20130604 (R1.0) ZTE Proprietary and Confidential

SJ-20130408113951-012|20130604 (R1.0) ZTE Proprietary and Confidential

SJ-20130408113951-012|20130604 (R1.0) ZTE Proprietary and Confidential

SJ-20130408113951-012|20130604 (R1.0) ZTE Proprietary and Confidential

SJ-20130408113951-012|20130604 (R1.0) ZTE Proprietary and Confidential

SJ-20130408113951-012|20130604 (R1.0) ZTE Proprietary and Confidential

SJ-20130408113951-012|20130604 (R1.0) ZTE Proprietary and Confidential

SJ-20130408113951-012|20130604 (R1.0) ZTE Proprietary and Confidential

SJ-20130408113951-012|20130604 (R1.0) ZTE Proprietary and Confidential

SJ-20130408113951-012|20130604 (R1.0) ZTE Proprietary and Confidential

SJ-20130408113951-012|20130604 (R1.0) ZTE Proprietary and Confidential

SJ-20130408113951-012|20130604 (R1.0) ZTE Proprietary and Confidential

SJ-20130408113951-012|20130604 (R1.0) ZTE Proprietary and Confidential

SJ-20130408113951-012|20130604 (R1.0) ZTE Proprietary and Confidential

Chapter 3 Notification ................................................................................ 3-1

SJ-20130408113951-012|20130604 (R1.0) ZTE Proprietary and Confidential

SJ-20130408113951-012|20130604 (R1.0) ZTE Proprietary and Confidential

SJ-20130408113951-012|20130604 (R1.0) ZTE Proprietary and Confidential

SJ-20130408113951-012|20130604 (R1.0) ZTE Proprietary and Confidential

SJ-20130408113951-012|20130604 (R1.0) ZTE Proprietary and Confidential

What Is in This Manual

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

2, Alarms Describes the alarms in terms of alarm properties, probable causes,

3, Notifications Describes the notifications in terms of notification properties, probable

SJ-20130408113951-012|20130604 (R1.0) ZTE Proprietary and Confidential

SJ-20130408113951-012|20130604 (R1.0) ZTE Proprietary and Confidential

Table 1-1 Alarm Format Description

Alarm Code Uniquely identifies an alarm.

SJ-20130408113951-012|20130604 (R1.0) ZTE Proprietary and Confidential

Handling Procedure Provides the troubleshooting steps and suggestions.

SJ-20130408113951-012|20130604 (R1.0) ZTE Proprietary and Confidential

Table 1-2 Notification Format Description

Notification Code Uniquely identifies a notification.

Notification Severity No notification severity is available.

Handling Procedure Provides the troubleshooting steps and suggestions.

SJ-20130408113951-012|20130604 (R1.0) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20130408113951-012|20130604 (R1.0) ZTE Proprietary and Confidential

2.1 Equipment Alarm

1. Clock cable is not properly connected.

SJ-20130408113951-012|20130604 (R1.0) ZTE Proprietary and Confidential

2.1.2 198001286 Input clock of board lost

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

2.1.3 198001792 Loss of SDH transmission link

SJ-20130408113951-012|20130604 (R1.0) ZTE Proprietary and Confidential

SJ-20130408113951-012|20130604 (R1.0) ZTE Proprietary and Confidential

2.1.4 198001825 High BER on SDH / Sonet link

1. Attenuation of receiving signals of local SDH equipment is large.

2.1.5 198002560 Board CPU overload

SJ-20130408113951-012|20130604 (R1.0) ZTE Proprietary and Confidential

1. Excessive data traffic at higher layer.

2.1.6 198002561 High temperature on CPU board

SJ-20130408113951-012|20130604 (R1.0) ZTE Proprietary and Confidential

Automatic CPU reset might occur.

2.1.7 198002563 FPGA clock speed abnormal alarm

The FPGA clock speed is abnormal.

The system time is inaccurate.