SJ-20121227135800-023-ZXUR 9000 GSM (V6.50.102) Alarm Handling Reference

ZXUR 9000 GSM
Base Station Controller

Alarm Handling Reference
Version:V6.50.102
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 2013–01–14 First edition
Serial Number: SJ-20121227135800-023
Publishing Date: 2013-01-14（R1.0）
SJ-20121227135800-023|2013-01-14（R1.0） ZTE Proprietary and Confidential

Contents
About This Manual ......................................................................................... I
Chapter 1 Overview .................................................................................... 1-1
1.1 Overview of Fault Management........................................................................... 1-1
1.2 Alarm Code........................................................................................................ 1-1
1.3 Alarm Type ........................................................................................................ 1-1
1.4 Alarm Classification ............................................................................................ 1-2
1.4.1 Alarm ...................................................................................................... 1-2
1.4.2 Notification............................................................................................... 1-2
1.5 Severity ............................................................................................................. 1-2
1.6 Probable Cause ................................................................................................. 1-3
1.7 Handling Suggestion .......................................................................................... 1-3
1.8 Alarm Impact ..................................................................................................... 1-3
Chapter 2 Alarm.......................................................................................... 2-1

2.1 Equipment Alarm................................................................................................ 2-1
2.1.1 198087000 Dry contact alarm 1................................................................. 2-1
2.1.10 198087009 Dry contact alarm 10 ............................................................. 2-5
2.1.13 198087012 EAM dry contact 1 alarm ...................................................... 2-7
2.1.14 198087013 EAM dry contact 2 alarm ....................................................... 2-7
2.1.19 198087018 EAM dry contact 7 alarm ..................................................... 2-10

2.1.20 198087019 EAM dry contact 8 alarm ..................................................... 2-10
2.1.21 198087102 Power overvoltage/undervoltage alarm..................................2-11
2.1.22 198087103 13M input clock failure .........................................................2-11
2.1.23 198087106 SYNCLK clock failure.......................................................... 2-12
2.1.24 198087107 Master and slave communication link failure ......................... 2-12
2.1.25 198087108 Standby CMM/CMB board not present ................................. 2-13
2.1.26 198087109 Standby CMM/CMB board abnormal .................................... 2-13
2.1.27 198087110 CMM/CMB power failure alarm ........................................... 2-14
2.1.28 198087112 Communication link alarm between master and slave rack
(left) .................................................................................................... 2-14
2.1.29 198087113 Communication link alarm between master and slave rack
(right) .................................................................................................. 2-15
2.1.30 198087114 A interface E1 Rx carrier alarm ........................................... 2-15
2.1.31 198087115 A interface E1 Rx frame not synchronized ............................ 2-16
2.1.32 198087120 A interface E1 remote alarm ................................................ 2-16
2.1.33 198087121 B interface E1 Rx carrier alarm ............................................ 2-17
2.1.34 198087122 B interface E1 Rx frame not synchronized ............................ 2-17
2.1.35 198087127 B interface E1 remote alarm ................................................ 2-18
2.1.36 198087128 C interface E1 Rx carrier alarm ............................................ 2-19
2.1.37 198087129 C interface E1 Rx frame not synchronized ............................ 2-19
2.1.38 198087134 C interface E1 remote alarm ................................................ 2-20
2.1.39 198087135 D interface E1 Rx carrier alarm ............................................ 2-20
2.1.40 198087136 D interface E1 Rx frame not synchronized ............................ 2-21
2.1.41 198087141 D interface E1 remote alarm ................................................ 2-21
2.1.42 198087142 E interface E1 Rx carrier alarm ............................................ 2-22
2.1.43 198087143 E interface E1 Rx frame not synchronized ............................ 2-22
2.1.44 198087148 E interface E1 remote alarm ................................................ 2-23
2.1.45 198087149 F interface E1 Rx carrier alarm ............................................ 2-24
2.1.46 198087150 F interface E1 Rx frame not synchronized ............................ 2-24
2.1.47 198087153 F interface E1 Rx forward sliding indication .......................... 2-25
2.1.48 198087155 F interface E1 remote alarm ................................................ 2-25
2.1.49 198087156 G interface E1 Rx carrier alarm............................................ 2-26
2.1.50 198087157 G interface E2 Rx frame not synchronized............................ 2-26
2.1.51 198087162 G interface E1 remote alarm................................................ 2-27
2.1.52 198087163 H interface E1 Rx carrier alarm ............................................ 2-27
2.1.53 198087164 H interface E3 Rx frame not synchronized ............................ 2-28
2.1.54 198087169 H interface E1 remote alarm ................................................ 2-28
2.1.55 198087170 Temperature alarm.............................................................. 2-29
II

2.1.56 198087171 Fan absent ......................................................................... 2-30
2.1.57 198087172 Fan control board CPU alarm ............................................. 2-30
2.1.58 198087173 Fan alarm .......................................................................... 2-31
2.1.59 198087174 Fan temperature alarm........................................................ 2-31
2.1.60 198087175 Fan 1 alarm ........................................................................ 2-32
2.1.61 198087176 Fan 2 alarm ........................................................................ 2-32
2.1.62 198087177 Fan control board alarm ...................................................... 2-33
2.1.63 198087178 LNA alarm ......................................................................... 2-33
2.1.64 198087179 Tower amplifier power alarm ................................................ 2-34
2.1.65 198087180 SWR of AEM HYCOM minor alarm ...................................... 2-34
2.1.66 198087181 SWR of AEM HYCOM major alarm ...................................... 2-35
2.1.67 198087182 AEM power alarm(BTS V2) ................................................. 2-35
2.1.68 198087183 AEM type alarm(BTS V2) .................................................... 2-36
2.1.69 198087184 AEM absent(BTS V2).......................................................... 2-36
2.1.70 198087185 AEM power alarm ............................................................... 2-37
2.1.71 198087186 LNA0 alarm ....................................................................... 2-37
2.1.72 198087187 LNA1 alarm ....................................................................... 2-38
2.1.73 198087188 Tower Amplifier0 power alarm ............................................. 2-38
2.1.74 198087189 Tower Amplifier1 power alarm.............................................. 2-39
2.1.75 198087190 SWR of AEM HYCOM minor alarm ..................................... 2-40
2.1.76 198087191 SWR of AEM HYCOM major alarm ..................................... 2-41
2.1.77 198087192 AEM type alarm .................................................................. 2-42
2.1.78 198087193 AEM Not-in-position alarm................................................... 2-42
2.1.79 198087198 Uplink of ADC chip initialization failure.................................. 2-43
2.1.80 198087200 CIP resource can not be used.............................................. 2-44
2.1.81 198087201 Uplink failure ...................................................................... 2-44
2.1.82 198087207 Watchdog of FUC overflow .................................................. 2-45
2.1.83 198087216 Cell configuration parameter mismatch(BTS V2) ................... 2-45
2.1.84 198087221 Communication link between CMM and FUC break(BTS
V2)....................................................................................................... 2-46
2.1.85 198087224 Watchdog of TPU CIP overflow............................................ 2-46
2.1.86 198087225 Software version of CIP mismatch ....................................... 2-47
2.1.87 198087226 Clock alarm for TPU and CMM ............................................ 2-47
2.1.88 198087228 TPU frame No. alarm .......................................................... 2-48
2.1.89 198087229 TPU CHP DSP0 initialization failure ..................................... 2-48
2.1.90 198087243 Cell configuration parameter mismatch................................. 2-49
2.1.91 198087247 HDLC communication link between CMB and FUC broken ..... 2-50
2.1.92 198087253 FU fram No error alarm ...................................................... 2-50
III

2.1.93 198087254 Rx PLL1 unlock ................................................................. 2-51
2.1.94 198087255 Rx PLL2 unlock ................................................................. 2-51
2.1.95 198087256 Tx PLL1 unlock .................................................................. 2-52
2.1.96 198087257 Tx PLL2 unlock .................................................................. 2-53
2.1.97 198087258 52M referenced clock PLL unlock ....................................... 2-53
2.1.98 198087259 Tx IF PLL unlock ................................................................ 2-54
2.1.99 198087260 EEPROM resource can not be used..................................... 2-54
2.1.100 198087261 FPGA interface failure ....................................................... 2-55
2.1.101 198087262 PA VSWR alarm(BTS V2).................................................. 2-55
2.1.102 198087263 PA overtemperature minor alarm(BTS V2) ......................... 2-56
2.1.103 198087264 PA overtemperature major alarm(BTS V2) .......................... 2-56
2.1.104 198087265 PA output power alarm ...................................................... 2-57
2.1.105 198087266 PA power overvoltage ....................................................... 2-57
2.1.106 198087267 PA power lower voltage ..................................................... 2-58
2.1.107 198087268 Downlink checksum error of DLRC_AL1 ............................. 2-58
2.1.108 198087269 DUC chip initialization failure ............................................. 2-59
2.1.109 198087270 80w PA VSWR alarm ........................................................ 2-59
2.1.110 198087271 80w PA overtemperature ................................................... 2-60
2.1.111 198087272 80w PA overtemperature major alarm ................................. 2-60
2.1.112 198087273 80w PA output power alarm ............................................... 2-61
2.1.113 198087274 80w PA power overvoltage................................................. 2-62
2.1.114 198087275 80w PA power lower voltage .............................................. 2-62
2.1.115 198087276 80w PA absent .................................................................. 2-63
2.1.116 198087277 TXIF unlock ...................................................................... 2-63
2.1.117 198087278 TPF unlock ....................................................................... 2-64
2.1.118 198087279 TXRF unlock..................................................................... 2-64
2.1.119 198087280 RXRF unlock .................................................................... 2-65
2.1.120 198087281 13 MHz clock lost.............................................................. 2-66
2.1.121 198087282 60 ms clock lost ................................................................ 2-66
2.1.122 198087285 52 MHz clock lost.............................................................. 2-67
2.1.123 198087288 PA power overvoltage alarm .............................................. 2-67
2.1.124 198087289 PA power undervoltage alarm ............................................ 2-68
2.1.125 198087290 PA VSWR alarm ............................................................... 2-68
2.1.126 198087291 PA temperature minor alarm .............................................. 2-69
2.1.127 198087292 PA temperature major alarm .............................................. 2-69
2.1.128 198087293 PA forward power(3db) alarm............................................. 2-70
2.1.129 198087294 RTU power alarm.............................................................. 2-71
IV

2.1.130 198087295 RTU power temperature alarm ........................................... 2-71
2.1.131 198087296 RTU power output overvoltage alarm ................................. 2-72
2.1.132 198087297 RTU power input failure alarm............................................ 2-72
2.1.133 198087298 IQ calibration parameters abnormal alarm .......................... 2-73
2.1.134 198087299 EAM heat exchanger alarm ............................................... 2-73
2.1.135 198087300 EAM TRX layer fan-4 alarm ............................................... 2-74
2.1.136 198087301 EAM AEM layer axis-flow fan alarm.................................... 2-74
2.1.137 198087302 EAM smoke alarm............................................................. 2-75
2.1.138 198087303 EAM waterproof alarm....................................................... 2-75
2.1.139 198087304 EAM lightning protection alarm .......................................... 2-76
2.1.140 198087305 EAM backdoor access control alarm .................................. 2-76
2.1.141 198087306 EAM frontdoor access control alarm................................... 2-77
2.1.142 198087307 EAM PWR monitoring unit alarm........................................ 2-77
2.1.143 198087308 EAM heat exchanger electric heater alarm.......................... 2-78
2.1.144 198087309 EAM heat exchanger control board alarm ........................... 2-78
2.1.145 198087310 EAM heat exchanger external circulation fan 2 alarm .......... 2-79
2.1.146 198087311 EAM heat exchanger external circulation fan 1 alarm........... 2-79
2.1.147 198087312 EAM heat exchanger internal circulation fan 2 alarm ........... 2-80
2.1.148 198087313 EAM heat exchanger internal circulation fan 1 alarm ........... 2-80
2.1.149 198087314 EAM heat exchanger 485 communication alarm.................. 2-81
2.1.150 198087315 EAM temperature alarm .................................................... 2-81
2.1.151 198087316 EAM TRX layer mixed-flow fan 1 alarm .............................. 2-82
2.1.154 198087319 Communication broken between EAM and CMB ................. 2-83
2.1.155 198087320 Power undervoltage alarm ................................................. 2-84
2.1.156 198087321 Inner fan 2 alarm (for M8202) ............................................ 2-84
2.1.157 198087322 Inner fan 1 alarm (for M8202) ............................................ 2-85
2.1.158 198087323 Outer fan 2 and fan 4 alarm (for M8202) ............................. 2-85
2.1.159 198087324 Outer fan 1 and fan 3 alarm (for M8202) ............................. 2-86
2.1.160 198087325 Rack temperature minor alarm........................................... 2-86
2.1.161 198087326 Rack temperature major alarm........................................... 2-87
2.1.162 198087327 Layer 3 fan 1 alarm (for M8206) ......................................... 2-87

2.1.171 198087391 FCU power undervoltage alarm ......................................... 2-92
2.1.172 198087403 The clock alarm about transmission of CCI board Abis-E1
............................................................................................................ 2-92
2.1.173 198087404 The local working clock alarm of CCI board ........................ 2-93
2.1.174 198087405 The clock alarm about transmission of CCI board 13M ....... 2-93
2.1.175 198087406 CCI opposite board alarm.................................................. 2-94
2.1.176 198087407 IQ FPGA internal clock alarm............................................. 2-94
2.1.177 198087408 IQ FPGA light interface alarm ........................................... 2-95
2.1.178 198087409 IQ FPGA LVDS interface alarm .......................................... 2-95
2.1.179 198087410 IQ FPGA internal data alarm.............................................. 2-96
2.1.180 198087411 13M,61.44M clock lost alarm.............................................. 2-96
2.1.181 198087412 60ms clock lost alarm........................................................ 2-97
2.1.182 198087413 26MHz and 52MHz lost of clock alarm................................ 2-97
2.1.183 198087414 the failure examination alarm of the 60ms uplink frame........ 2-98
2.1.184 198087415 checking block data error alarm ......................................... 2-98
2.1.185 198087416 up link LVDS SERDES lost lock alarm ................................ 2-99
2.1.186 198087417 FN error alarm .................................................................. 2-99
2.1.187 198087432 Diversity antenna lost .......................................................2-100
2.1.188 198087433 Diversity antenna identical ................................................2-100
2.1.189 198087443 Diversity antenna lost .......................................................2-101
2.1.190 198087444 Diversity antenna identical ................................................2-101
2.1.191 198087451 board not support 16MHW................................................2-102
2.1.192 198087452 cmb or cpu overload.........................................................2-102
2.1.193 198087453 signal HDLC break off ......................................................2-103
2.1.194 198087454 main HDLC break off........................................................2-103
2.1.195 198087455 FIB configure wrong .........................................................2-104
2.1.196 198087456 lay3 of FIB software has no response................................2-104
2.1.197 198087460 positive 12 voltage alarm ..................................................2-105
2.1.198 198087461 negative 12 voltage alarm.................................................2-105
2.1.199 198087462 DSP 1.2v voltage alarm....................................................2-106
2.1.200 198087463 6.4v voltage alarm............................................................2-106
2.1.201 198087464 5v voltage alarm ..............................................................2-107
2.1.202 198087470 Fan absence alarm ..........................................................2-107
2.1.203 198087471 Fan rotate alarm ..............................................................2-108
VI

2.1.204 198087472 CMB and FNCB RS485 link break alarm ...........................2-108
2.1.205 198087473 DTPU CPU overload ........................................................2-109
2.1.206 198087480 Status of TX5 filter alarm ..................................................2-109
2.1.207 198087481 Status of TX6 filter alarm .................................................. 2-110
2.1.208 198087483 GPS signal synchronization exception ............................... 2-110
2.1.209 198087484 Second pulse loss............................................................ 2-111
2.1.210 198087485 Antenna open-circuit alarm ............................................... 2-111
2.1.211 198087486 Antenna short-circuit alarm ............................................... 2-112
2.1.212 198087487 Lost satellite alarm ........................................................... 2-112
2.1.213 198087510 CPU of FIB overload ........................................................ 2-113
2.1.214 198088000 DTPU not support Baseband-Hop alarm............................ 2-113
2.1.215 198088001 PA Power Voltage Adjusting Path Disconnected................. 2-114
2.1.216 198088002 PA Power Voltage Adjusting Data Error ............................. 2-114
2.1.217 198088003 PA Power Voltage Adjusting Data Illegal ............................ 2-115
2.1.218 198088004 Access iBSC failure.......................................................... 2-115
2.1.219 198088005 Control link broken ........................................................... 2-116
2.1.220 198088006 Operation link broken(CS) ................................................ 2-116
2.1.221 198088007 Operation link broken(PS) ................................................ 2-117
2.1.222 198088008 Parameter configuration mismatch .................................... 2-117
2.1.223 198088009 DSP initialization failure.................................................... 2-118
2.1.224 198088010 Parameter configuration failure of AD6537......................... 2-118
2.1.225 198088011 Tx PLL unlock .................................................................. 2-119
2.1.226 198088012 Wrong parameter configuration for EEPROM..................... 2-119
2.1.227 198088013 FLASH memory fault ........................................................2-120
2.1.228 198088014 Run abnormity of DSP......................................................2-120
2.1.229 198088015 FPGA interface fault.........................................................2-121
2.1.230 198088016 CHP frame fault ...............................................................2-121
2.1.231 198088017 Wrong receive channel of RF............................................2-122
2.1.232 198088018 Get DNS failure when configuration IP of active .................2-122
2.1.233 198088019 Analyse failure of DNS domain name ................................2-123
2.1.234 198088020 IPSec failure ....................................................................2-123
2.1.235 198088021 RF channel and HTRG board unconformity .......................2-124
2.1.236 198088022 Get HBTS is IP address failure from DHCP Sever..............2-124
2.1.237 198088023 Over temperature.............................................................2-125
2.1.238 198088024 Voltage abnormity ............................................................2-125
2.1.239 198088025 Abis link change alarm .....................................................2-126
2.1.240 198088026 IPOE uplink and downlink jam alarm .................................2-126
VII

2.1.241 198088027 DIP E1 rack, rack type error..............................................2-127
2.1.242 198088028 DIP E1 rack, rack number error.........................................2-127
2.1.243 198088029 DIP E1 rack,slave rack 1 port error....................................2-128
2.1.244 198088030 DIP E1 rack,slave rack 2 port error....................................2-128
2.1.245 198088031 DIP E1 rack,satellite back up flag error ..............................2-129
2.1.246 198088032 DIP E1 rack,oam time slot error ........................................2-129
2.1.247 198088033 DIP IP rack,access mode error(IP or IPOE) .......................2-130
2.1.248 198088034 DIP IP rack,rack number error...........................................2-130
2.1.249 198088035 DIP IP rack,site number error............................................2-131
2.1.250 198088036 DIP IP rack,sequence number error ..................................2-131
2.1.251 198088037 Mains power failure alarm.................................................2-132
2.1.252 198088038 Alarm of the trx is down link LRC failed..............................2-132
2.1.253 198105025 the rate of abnormal service on SLAVE is high ...................2-133
2.1.254 199000256 OMC port is link is down ...................................................2-133
2.1.255 199000512 Trunk loss of frame .........................................................2-134
2.1.256 199000513 Trunk loss of signal ..........................................................2-135
2.1.257 199000514 Trunk alarm indication signal.............................................2-135
2.1.258 199000515 Trunk loss of CRC multi-frame .........................................2-136
2.1.259 199000517 Trunk remote alarm indication ...........................................2-136
2.1.260 199000518 Trunk link is used for CSU loopback test............................2-137
2.1.261 199001024 Cell Delineation Not Synchronized ....................................2-137
2.1.262 199001025 Loss of Cell Delineation ...................................................2-138
2.1.263 199001026 Cell delineation do not synchronization about cell on E1
link......................................................................................................2-139
2.1.264 199001285 Clock chip is in preheat status...........................................2-140
2.1.265 199001286 Input clock of the board is lost...........................................2-140
2.1.266 199001792 SDH SONET Loss of signal ..............................................2-141
2.1.267 199001793 SDH SONET Loss of frame ..............................................2-142
2.1.268 199001794 SDH SONET Regenerator section trace mismatch/Section
trace mismatch ....................................................................................2-142
2.1.269 199001795 SDH SONET MS alarm indication signal/Line alarm
indication signal ...................................................................................2-143
2.1.270 199001796 SDH SONET MS far-end reception failure/Line far-end
reception failure ...................................................................................2-144
2.1.271 199001797 SDH SONET Signal failure ...............................................2-144
2.1.272 199001798 SDH SONET Signal deterioration......................................2-145
2.1.273 199001799 SDH SONET Loss of AU pointer/Loss of path pointer.........2-146
VIII

2.1.274 199001800 SDH SONET AU alarm indication signal/Path alarm
indication signal ...................................................................................2-147
2.1.275 199001801 SDH SONET HP trace mismatch/ Path trace mismatch ......2-147
2.1.276 199001802 SDH SONET HP unequipped/Path unequipped .................2-148
2.1.277 199001803 SDH SONET HP Label mismatch/Path label mismatch.......2-149
2.1.278 199001804 SDH SONET HP remote reception failure/Path remote
reception failure ...................................................................................2-149
2.1.279 199001805 SDH SONET Loss of multi-frame ......................................2-150
2.1.280 199001806 SDH SONET Loss of TU pointer/Loss of virtual tributary
pointer ................................................................................................2-150
2.1.281 199001807 SDH SONET Tributary unit alarm indication signal/Virtual
tributary alarm indication signal .............................................................2-151
2.1.282 199001808 SDH SONET LP remote defect indication/Virtual tributary
remote defect indication .......................................................................2-151
2.1.283 199001809 SDH SONET LP remote failure indication/Virtual tributary
remote failure indication .......................................................................2-152
2.1.284 199001810 SDH SONET LP trace mismatch/Virtual tributary trace
mismatch.............................................................................................2-153
2.1.285 199001811 SDH SONET LP unequipped/Virtual tributary
unequipped .........................................................................................2-154
2.1.286 199001812 SDH SONET LP label mismatch/Virtual tributary label
mismatch.............................................................................................2-155
2.1.287 199001816 SDH SONET Severe B1 error code...................................2-156
2.1.290 199001819 SDH SONET Severe BIP-2 error code ..............................2-158
2.1.291 199001820 SDH SONET MS remote error indication ..........................2-159
2.1.292 199001821 SDH SONET HP remote error indication ...........................2-160
2.1.293 199001826 SDH SONET LP remote error indication ...........................2-161
2.1.294 199005123 The configuration is not supported ....................................2-162
2.1.295 199005405 Clock board phase-lock loop work mode is abnormal .........2-163
2.1.296 199005632 The hard disk used-rate is over threshold ..........................2-163
2.1.297 199005633 File system is abnormal....................................................2-164
2.1.298 199005634 The hard disk on board gets IO error. ................................2-164
2.1.299 199005646 Phase-lock loop of the board is unlocked...........................2-165
2.1.300 199005666 Error packets of MAC is higher than the specified
threshold .............................................................................................2-166
2.1.301 199005670 Oscillator status is abnormal .............................................2-167
2.1.302 199005672 Clock source is not available.............................................2-167
IX

2.1.303 199005673 The setting of the dial switch is changed............................2-168
2.1.304 199005760 Ethernet port is link is down ..............................................2-168
2.1.305 199005761 The speed mode of Ethernet port does not match with
settings ...............................................................................................2-169
2.1.306 199005768 All of the board input clocks which have the same
frequency are lost. ..............................................................................2-170
2.1.307 199005769 The master and slave mode of Ethernet port does not
match with settings ..............................................................................2-170
2.1.308 199005770 The OMP board does not have any OMC port....................2-171
2.1.309 199005771 The duplex mode of Ethernet port does not match with
settings ...............................................................................................2-171
2.1.310 199005772 Board device fault ............................................................2-172
2.1.311 199005773 High CRC error rate at E1/T1 bottom layer ........................2-172
2.1.312 199005774 High FAS error rate at E1/T1 bottom layer ........................2-173
2.1.313 199005775 High EBIT error rate at E1 bottom layer ............................2-174
2.1.314 199005785 GPS module is abnormal..................................................2-174
2.1.315 199005797 The hard disk is abnormal ................................................2-175
2.1.316 199005798 The RAID of hard disks is abnormal ..................................2-176
2.1.317 199005799 Hard disk online ...............................................................2-177
2.1.318 199005800 Hard disk offline ...............................................................2-178
2.1.319 199005890 Functional EPLD update failed..........................................2-178
2.1.320 199005930 NCPU version load failed..................................................2-179
2.1.321 199007168 Port trunk fail ...................................................................2-180
2.1.322 199007169 Inner port error.................................................................2-180
2.1.323 199007170 Trunk connect asymmetry.................................................2-181
2.1.324 199007171 Outer media trunk failed ...................................................2-181
2.1.325 199015360 Media status abnormal .....................................................2-182
2.1.326 199015618 Too many bad frames received .........................................2-182
2.1.327 199019712 APS channel mismatch ....................................................2-183
2.1.328 199019713 APS mode mismatch........................................................2-184
2.1.329 199019715 MS APS channel gets errors.............................................2-184
2.1.330 199023050 Fan Device Absent...........................................................2-185
2.1.331 199023051 Power Unit Absent ...........................................................2-185
2.1.332 199023106 Board initialized test failed ................................................2-186
2.1.333 199025602 Half-Fixed Connection abnormal .......................................2-187
2.1.334 199025856 Rack temperature is higher than high threshold..................2-187
2.1.335 199025857 Rack temperature is lower than low threshold ....................2-188
2.1.336 199025858 Room temperature is higher than high threshold ...............2-189

2.1.337 199025859 Room temperature is lower than low threshold ..................2-189
2.1.338 199025860 Voltage is higher than high threshold ................................2-190
2.1.339 199025861 Voltage is lower than low threshold ...................................2-190
2.1.340 199025862 Humidity is higher than high threshold ..............................2-191
2.1.341 199025863 Humidity is lower than low threshold .................................2-192
2.1.342 199025864 Fault in fan plug-in box ....................................................2-192
2.1.343 199025865 Rack door access control alarm ........................................2-193
2.1.344 199025866 Smoke alarm ...................................................................2-194
2.1.345 199025867 Infrared alarm ..................................................................2-194
2.1.346 199025868 Lightning alarm ................................................................2-195
2.1.347 199025869 Power switch alarm .........................................................2-196
2.1.348 199025870 Power type configured does not accord with physical .........2-196
2.1.349 199026127 Clock reference source lost (Level 3 alarm) ......................2-197
2.1.352 199026133 Output clock of the board is lost ........................................2-200
2.1.353 199029184 SNTP time-synchronization failed......................................2-200
2.1.354 199030721 Temperature is lower than lower-non-critical threshold........2-201
2.1.355 199030722 Temperature is lower than lower-critical threshold. .............2-202
2.1.356 199030723 Temperature is lower than lower-non-recoverable
threshold. ............................................................................................2-202
2.1.357 199030724 Temperature is higher than upper-non-critical threshold. ......2-203
2.1.358 199030725 Temperature is higher than upper-critical threshold.............2-203
2.1.359 199030726 Temperature is higher than upper-non-recoverable
threshold. ............................................................................................2-204
2.1.360 199030727 Voltage is lower than lower-non-critical threshold. ..............2-204
2.1.361 199030728 Voltage is lower than lower-critical threshold. .....................2-205
2.1.362 199030729 Voltage is lower than lower-non-recoverable threshold. ......2-205
2.1.363 199030730 Voltage is higher than upper-non-critical threshold..............2-206
2.1.364 199030731 Voltage is higher than upper-critical threshold. ...................2-206
2.1.365 199030732 Voltage is higher than upper-non-recoverable
threshold. ............................................................................................2-207
2.1.366 199030734 Velocity of fan is lower than lower-critical threshold. ...........2-207
2.1.367 199030739 Current is lower than lower-non-critical threshold. ..............2-208
2.1.368 199030740 Current is lower than lower-critical threshold. .....................2-208
2.1.369 199030741 Current is lower than lower-non-recoverable threshold. ......2-209
2.1.370 199030742 Current is higher than upper-non-critical threshold..............2-209
2.1.371 199030743 Current is higher than upper-critical threshold. ...................2-210
XI

2.1.372 199030744 Current is higher than upper-non-recoverable
threshold. ............................................................................................2-210
2.1.373 199030745 Velocity of fan is lower than lower-non-critical threshold. ...... 2-211
2.1.374 199030746 Velocity of fan is lower than lower-non-recoverable
threshold. ............................................................................................ 2-211
2.1.375 199030747 Module/Board Device Absent............................................2-212
2.1.376 199030748 Power On Failed due to S5...............................................2-212
2.1.377 199030808 Processor Internal Error ...................................................2-213
2.1.378 199030809 Processor Thermal Trip ....................................................2-213
2.1.379 199087340 FR device failure..............................................................2-214
2.1.380 199087341 FR congestion .................................................................2-214
2.1.381 199087344 MSC overload control alarm at FUC mode.........................2-215
2.1.382 199087345 CPU overload control alarm at FUC mode .........................2-215
2.1.383 199087346 Signaling point congestion control alarm at FUC mode .......2-216
2.1.384 199087347 MSC overload control alarm at SYS mode .........................2-216
2.1.385 199087348 CPU overload control alarm at SYS mode .........................2-217
2.1.386 199087349 Signaling point congestion control alarm at SYS mode .......2-217
2.1.387 199087350 CCCH overload control.....................................................2-218
2.1.388 199087351 PCCCH overload control ..................................................2-219
2.1.389 199087352 NSVC is E1 failure alarm ..................................................2-219
2.1.390 199087458 PS cell block caused by slave ...........................................2-220
2.1.391 199087465 NSVC is IP failure alarm ...................................................2-220
2.1.392 199087482 dbsapp data error alarm ...................................................2-221
2.1.393 199087505 Board Connect Fail ..........................................................2-222
2.1.394 199087517 Shelf overload control alarm at FUC mode.........................2-222
2.1.395 199087518 Shelf overload control alarm at SYS mode.........................2-223
2.1.396 199087768 Resource Availability Alarm of SLAVE ...............................2-223
2.1.397 199087778 Dry contact alarm - Waterlog.............................................2-224
2.1.398 199087779 Dry contact alarm - Power loss .........................................2-225
2.1.399 199087780 Dry contact alarm - No.1 air conditioner fault......................2-225
2.1.400 199087781 Dry contact alarm - No.2 air conditioner fault......................2-226
2.1.401 199087782 Dry contact alarm - AC power abnormal ............................2-226
2.1.402 199087783 Dry contact alarm - Battery under-voltage .........................2-227
2.1.403 199087784 Dry contact alarm - SMR abnormal ...................................2-227
2.1.404 199087785 Dry contact alarm - Under-voltage insulate drop.................2-228
2.1.405 199087786 Dry contact alarm - Device suspended ..............................2-228
2.1.406 199087787 User-defined Dry contact alarm 1 ......................................2-229
XII

2.1.415 199087796 User-defined Dry contact alarm 10 ....................................2-233
2.1.416 199087797 User-defined Dry contact alarm 11 ....................................2-234
2.1.417 199105029 OMP reboot alarm............................................................2-234
2.1.418 199393987 Board off line ...................................................................2-235
2.1.419 199419840 PTP failed to get clock attribute.........................................2-235
2.2 Processing alarm ............................................................................................2-236
2.2.1 199002560 CPU utilization over alarm limit .............................................2-236
2.2.2 199004357 The system bureau changed ................................................2-237
2.2.3 199005400 Configuration conflicts between OMP and CMM ....................2-237
2.2.4 199005908 Lack of version ....................................................................2-238
2.2.5 199005909 Download version failed .......................................................2-238
2.2.6 199005910 Process execute failed .........................................................2-239
2.2.7 199015362 Fail to process MCS APP Dlib .............................................2-239
2.2.8 199020225 Protocol stack requests for configuration information
timeout ................................................................................................2-240
2.2.9 199023042 The number of board physical alarms exceeds the
threshold .............................................................................................2-241
2.2.10 199025600 Connection check be disabled in board ...............................2-242
2.2.11 199029953 Port is in ethernet OAM loopback state ................................2-242
2.2.12 199066013 MTP3 link congestion.........................................................2-243
2.2.13 199066027 Request time from SNTP server failed.................................2-244
2.2.14 199066031 The number of OMP alarms exceeds the threshold ..............2-244
2.2.15 199066032 Time synchronization over alarm limit..................................2-245
2.2.16 199066063 MTP3 link sending flow control alarm ..................................2-245
2.2.17 199087773 CIC manual blocked alarm .................................................2-246
2.2.18 199087774 BVC manual blocked alarm ................................................2-247
2.2.19 199392708 Time synchronization over alarm limit in RPU accesstype ......2-247
2.2.20 199411651 The number of board logical alarms exceeds the
threshold .............................................................................................2-248
2.3 Communications Alarm....................................................................................2-248
2.3.1 198087101 HW link broken ....................................................................2-248
XIII

2.3.2 199003841 The control plane retransfer ratio over the threshold...............2-249
2.3.3 199005382 Environment monitor board communication is abnormal ........2-250
2.3.4 199005396 Packet test of internal media plane is abnormal .....................2-250
2.3.5 199005397 Communication of RAW MAC channel is abnormal ................2-251
2.3.6 199005406 Sub-unit state is abnormal....................................................2-252
2.3.7 199019971 Request gate info timeout.....................................................2-252
2.3.8 199025631 LVDS link error ....................................................................2-253
2.3.9 199025871 Communication abnormal between the shelf management
board and switch board in the same shelf ..............................................2-254
2.3.10 199029952 Ethernet link fault alarm......................................................2-254
2.3.11 199030208 Connectivity fault alarm ......................................................2-255
2.3.12 199066003 Control plane communication abnormal between board and
its home module ..................................................................................2-257
2.3.13 199066005 SCCP subsystem unavailable.............................................2-257
2.3.14 199066008 MTP2 link sending overload ...............................................2-258
2.3.15 199066009 MTP2 link reception overload .............................................2-259
2.3.16 199066010 MTP3 office inaccessible ....................................................2-260
2.3.17 199066011 MTP3 link unavailable ........................................................2-261
2.3.18 199066012 MTP3 cluster inaccessible ..................................................2-262
2.3.19 199066014 M3UA office inaccessible ...................................................2-263
2.3.20 199066019 Broken Association ............................................................2-264
2.3.21 199066026 Association Channel Broken...............................................2-265
2.3.22 199087336 Rack Abis control link broken..............................................2-266
2.3.23 199087337 Site Abis control link broken................................................2-267
2.3.24 199087342 Cell interruption alarm ........................................................2-268
2.3.25 199087380 TRX Manual Block .............................................................2-269
2.3.26 199087381 The time-slot of air interface blocked manually.....................2-270
2.3.27 199087468 lapd jam alarm...................................................................2-270
2.3.28 199087775 super site exchanged to the satellitic ABIS link or slave
link......................................................................................................2-271
2.3.29 199105035 The communication link between LogService board and
OMP is broken ....................................................................................2-271
2.3.30 199393986 Control plane communication is abnormal between this
board and the active independent board ................................................2-272
2.3.31 199393988 Control plane communication abnormal between MP and
OMP ...................................................................................................2-272
2.3.32 199407043 PPP Link Broken ...............................................................2-273
2.3.33 199407298 BSCIP configuration error in database.................................2-275
XIV

2.3.34 199411392 BFD Session Interruption....................................................2-275
2.3.35 199411393 BFD Session Negotiation Failure.........................................2-277
2.3.36 199419073 Bearer network is unavailable .............................................2-278
2.3.37 199419074 Bearer network get worse...................................................2-279
2.3.38 199420352 IPD Session Interruption.....................................................2-280
2.4 Environment Alarm..........................................................................................2-281
2.4.1 199030749 Difference between ambient and outlet sensor exceeded limit
. ..........................................................................................................2-281
2.5 Qos Alarm ......................................................................................................2-282
2.5.1 199066018 Association congested .........................................................2-282
2.5.2 199087506 NSE block alarm..................................................................2-283
2.5.3 199087507 SGSN is blocked .................................................................2-283
2.5.4 199087758 Manual User Access control alarm........................................2-284
2.5.5 199087759 CPU overload control alarm at Paging mode .........................2-284
XV

XVI

About This Manual
Manual Description
This manual is a handling reference for the ZXUR 9000alarms and notifications, it helps
users to analyze and handle the alarms and notifications reported on the NMS during the
operation of ZXUR 9000.
Target Group
l EMS Engineer
l Network Optimization Engineer
l Testing Engineer
What Is in This Manual
Chapter Summary
Chapter 1, Overview Introduces the concepts and terms used in this manual.
Chapter 2, Alarm Introduces the ZXUR 9000alarms.

II

Chapter 1
Overview
Table of Contents
Overview of Fault Management ..................................................................................1-1
Alarm Code ................................................................................................................1-1
Alarm Type.................................................................................................................1-1
Alarm Classification....................................................................................................1-2
Severity ......................................................................................................................1-2
Probable Cause .........................................................................................................1-3
Handling Suggestion ..................................................................................................1-3
Alarm Impact ..............................................................................................................1-3
1.1 Overview of Fault Management

Fault management is responsible for collecting information of failures and events that occur
during system operation or service processing.
The information, in the form of alarm or notification, is stored in database or displayed
on realtime basis via a user-oriented fault monitoring platform. Means such as
visual-interface monitor or history information query can be used to view current or
historical system operation and service processing status. Fault management enables
maintenance personnel to troubleshoot and take preventive measures to remove potential
fault and restore system and services as early as possible.
1.2 Alarm Code

Alarm code is the identifier which differentiates alarms.
Alarm code is defined by a 32-bit field indicating the specific code value.
1.3 Alarm Type

Alarm is classified into six types according to alarm trigger condition and its system impact.
l Equipment alarm: related with device hardware.
l Communication alarm: related with information transmission (ITU-T Recommendation
X.733).
l Processing alarm: related with software or process fault (ITU-T Recommendation
X.733).
l Environment alarm: related with the environment where the equipment is located
(ITU-T Recommendation X.733).
1-1

ZXUR 9000 GSM Alarm Handling Reference
l QoS alarm: related with degradation of service quality (ITU-T Recommendation

X.733).
l OMS alarm: related with the network management system.
1.4 Alarm Classification

1.4.1 Alarm
The fault that persists during system operation and affects system reliability and normal
services is referred to as an alarm. Alarm usually lasts until fault removal.
Due to its possible impact on normal system operation, alarm requires timely
troubleshooting in which alarm cause is identified, and the fault is located and handled.
1.4.2 Notification
Notification refers to the non-repeated/instantaneous fault or event that occurs during
system operation. Examples include board reset, signaling overload, etc.
Notification is mostly caused by sudden environment change or other accidental factors.
No special handling is required for the notification, which can be automatically removed by
the system. Only the notification that occurs persistently requires troubleshooting.
1.5 Severity
There are four alarm severity levels, which are indicated in descending order of severity
as Critical, Major, Minor and Warning.
l Critical alarm causes system breakdown and service interruption. It requires
immediate troubleshooting.
l Major alarm significantly affects system operation or weakens network service
capability. It requires troubleshooting as soon as possible.
l Minor alarm affects system operation and network service capability in a nonsignificant
way. A timely troubleshooting is required to avoid severity escalation.
l Warning alarm poses a potential hazard to system operation and network service
capability. It requires troubleshooting at an appropriate time so as to avoid severity
escalation.
The degree of impact as described in the definition of alarm severity refers to the impact of
a single index, such as reliability and security. Once the impact on any of the index reaches
the specified threshold, the severity level of the alarm can be roughly determined. If an
alarm has an impact on multiple indices, alarm severity should be escalated accordingly.
1-2

Chapter 1 Overview
Note:
Alarm severity can be modified in NetNumen M31 NMS (network management system) if
necessary.
Generally speaking, the default alarm severity is reasonably set. Users should think twice
before making any modification.
In addition, the severity of few alarms is Undefined. It is up to users to define the severity
of such alarms.
1.6 Probable Cause

Probable alarm causes are enumerated to help users troubleshoot, find preventive
measures, and restore the system to normal state in a timely manner.
1.7 Handling Suggestion

Troubleshooting measures and suggestions are provided.
Pay attention to the following tips when handling alarms.

l After recording the fault phenomenon, O&M personnel may handle the fault step by
step as described in the Handling Suggestion Section of this manual. If the fault is
removed (alarm restored) at any handling step, terminate the handling process. If the
fault is not removed, go ahead to the next handling step.
l If the fault cannot be removed, contact the local ZTE office as soon as possible.
1.8 Alarm Impact

Alarm impact refers to the impact that the alarm incurs on system or services.
1-3

This page intentionally left blank.
1-4

Chapter 2
Alarm
Table of Contents
Equipment Alarm........................................................................................................2-1
Processing alarm ...................................................................................................2-236
Communications Alarm ..........................................................................................2-248
Environment Alarm.................................................................................................2-281
Qos Alarm ..............................................................................................................2-282
2.1 Equipment Alarm

2.1.1 198087000 Dry contact alarm 1
Alarm Property
l Alarm Code: 198087000
l Description: Dry contact alarm 1
l Severity: Not defined
l Alarm Type: Equipment Alarm
Probable Cause
None
System Impact
None
Handling Suggestion
None

Alarm Property
2-1

Probable Cause
None
System Impact
None
Handling Suggestion
None

Alarm Property
Probable Cause
None
System Impact
None
Handling Suggestion
None

Alarm Property
2-2

Chapter 2 Alarm
Probable Cause
None
System Impact
None
Handling Suggestion
None

Alarm Property
Probable Cause
None
System Impact
None
Handling Suggestion
None

Alarm Property
Probable Cause
None
2-3

System Impact
None
Handling Suggestion
None

Alarm Property
Probable Cause
None
System Impact
None
Handling Suggestion
None

Alarm Property
Probable Cause
None
System Impact
None
2-4

Chapter 2 Alarm
Handling Suggestion
None

Alarm Property
Probable Cause
None
System Impact
None
Handling Suggestion
None

Alarm Property
Probable Cause
None
System Impact
None
Handling Suggestion
None
2-5


Alarm Property
Probable Cause
None
System Impact
None
Handling Suggestion
None

Alarm Property
Probable Cause
None
System Impact
None
Handling Suggestion
None
2-6

Chapter 2 Alarm
2.1.13 198087012 EAM dry contact 1 alarm

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

Alarm Property
Probable Cause
None
System Impact
None
Handling Suggestion
None
2-7


Alarm Property
Probable Cause
None
System Impact
None
Handling Suggestion
None

Alarm Property
Probable Cause
None
System Impact
None
Handling Suggestion
None
2-8

Chapter 2 Alarm

Alarm Property
Probable Cause
None
System Impact
None
Handling Suggestion
None

Alarm Property
Probable Cause
None
System Impact
None
Handling Suggestion
None
2-9


Alarm Property
Probable Cause
None
System Impact
None
Handling Suggestion
None

Alarm Property
Probable Cause
None
System Impact
None
Handling Suggestion
None
2-10

Chapter 2 Alarm
2.1.21 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.22 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-11

2.1.23 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.24 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-12

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

2. If the software has problem, upgrade it.
2.1.25 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.26 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
System Impact
None
2-13

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.27 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.28 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
Probable Cause
Communication link fault between master rack and slave rack
System Impact
None
2-14

Chapter 2 Alarm
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.29 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.30 198087114 A interface E1 Rx carrier alarm

Alarm Property
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
2-15

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.31 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.1.32 198087120 A interface E1 remote alarm

Alarm Property
l Description: A interface E1 remote alarm
l Severity: Minor
2-16

Chapter 2 Alarm
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.33 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.1.34 198087122 B interface E1 Rx frame not synchronized

Alarm Property
l Description: B interface E1 Rx frame not synchronized
l Severity: Minor
2-17

Probable Cause
System Impact
None
Handling Suggestion
2.1.35 198087127 B interface E1 remote alarm

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

Chapter 2 Alarm
2.1.36 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.37 198087129 C interface E1 Rx frame not synchronized

Alarm Property
l Description: C interface E1 Rx frame not synchronized
l Severity: Minor
Probable Cause
System Impact
None
2-19

Handling Suggestion
2.1.38 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.39 198087135 D interface E1 Rx carrier alarm

Alarm Property
l Description: D interface E1 Rx carrier alarm
l Severity: Minor
Probable Cause
2-20

Chapter 2 Alarm
System Impact
None
Handling Suggestion
2.1.40 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.41 198087141 D interface E1 remote alarm

Alarm Property
l Description: D interface E1 remote alarm
l Severity: Minor
2-21

Probable Cause
System Impact
None
Handling Suggestion
2.1.42 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.1.43 198087143 E interface E1 Rx frame not synchronized

Alarm Property
l Description: E interface E1 Rx frame not synchronized
l Severity: Minor
2-22

Chapter 2 Alarm
Probable Cause
System Impact
None
Handling Suggestion
2.1.44 198087148 E interface E1 remote alarm

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

2.1.45 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.46 198087150 F interface E1 Rx frame not synchronized

Alarm Property
l Description: F interface E1 Rx frame not synchronized
l Severity: Minor
Probable Cause
System Impact
None
2-24

Chapter 2 Alarm
Handling Suggestion
2.1.47 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.48 198087155 F interface E1 remote alarm

Alarm Property
l Description: F interface E1 remote alarm
l Severity: Minor
Probable Cause
2-25

System Impact
None
Handling Suggestion
2.1.49 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.50 198087157 G interface E2 Rx frame not synchronized

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

Chapter 2 Alarm
Probable Cause
System Impact
None
Handling Suggestion
2.1.51 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.52 198087163 H interface E1 Rx carrier alarm

Alarm Property
l Description: H interface E1 Rx carrier alarm
l Severity: Minor
2-27

Probable Cause
System Impact
None
Handling Suggestion
2.1.53 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.1.54 198087169 H interface E1 remote alarm

Alarm Property
l Description: H interface E1 remote alarm
2-28

Chapter 2 Alarm
l Severity: Minor
Probable Cause
System Impact
None
Handling Suggestion
2.1.55 198087170 Temperature alarm

Alarm Property
l Description: Temperature alarm
l Severity: Warning
Probable Cause
Fan fault or module temperature too high
System Impact
None
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-29

2.1.56 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.57 198087172 Fan control board CPU alarm

Alarm Property
l Description: Fan control board CPU alarm
l Severity: Warning
Probable Cause
CPU fault
System Impact
None
Handling Suggestion
1. check the line and correct it.

2. check the fan and replace FCM.
2-30

Chapter 2 Alarm
2.1.58 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.59 198087174 Fan temperature alarm

Alarm Property
l Description: Fan temperature alarm
l Severity: Warning
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-31

2.1.60 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.61 198087176 Fan 2 alarm

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

Chapter 2 Alarm
2.1.62 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.1.63 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-33

2.1.64 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.1.65 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-34

Chapter 2 Alarm
2.1.66 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.1.67 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-35

2.1.68 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.1.69 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-36

Chapter 2 Alarm
2.1.70 198087185 AEM power alarm

Alarm Property
l Description: AEM power alarm
l Severity: Major
Probable Cause
AEM power alarm
System Impact
None
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.71 198087186 LNA0 alarm

Alarm Property
l Description: LNA0 alarm
l Severity: Minor
Probable Cause
LNA0 current exceeds by 30%
System Impact
None
2-37

Handling Suggestion
（3）Replace CDU.
2.1.72 198087187 LNA1 alarm

Alarm Property
l Description: LNA1 alarm
l Severity: Minor
Probable Cause
LNA1 current exceeds by 30%
System Impact
None
Handling Suggestion
（3）Replace CDU.
2.1.73 198087188 Tower Amplifier0 power alarm

Alarm Property
l Description: Tower Amplifier0 power alarm
l Severity: Warning
2-38

Chapter 2 Alarm
Probable Cause
AEM tower amplifier 0 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.
（4）Replace CDU and reset TRX connecting with it.
2.1.74 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
2-39

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.1.75 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
2-40

Chapter 2 Alarm
（4）Pull out of CDU and DTRU modules in the same layer. Check whether the pins on the rear
board are bent. If yes, replace the rear board. Check whether the alarm cable connector of CDU
is loose or off. If yes, fastern it and re-power it on. Three minutes after the TRX is running, check
whether the alarm disappears.
2.1.76 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
the alarm disappears.
2-41

2.1.77 198087192 AEM type alarm

Alarm Property
l Description: AEM type alarm
l Severity: Major
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 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 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.78 198087193 AEM Not-in-position alarm

Alarm Property
l Description: AEM Not-in-position alarm
l Severity: Major
2-42

Chapter 2 Alarm
Probable Cause
AEM not-in-position alarm
System Impact
None
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.79 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-43

2.1.80 198087200 CIP resource can not be used

Alarm Property
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.81 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-44

Chapter 2 Alarm
2.1.82 198087207 Watchdog of FUC overflow

Alarm Property
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.83 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-45

2.1.84 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
1.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.85 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
System Impact
None
2-46

Chapter 2 Alarm
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.86 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.87 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
System Impact
None
2-47

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.88 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.89 198087229 TPU CHP DSP0 initialization failure

Alarm Property
l Description: TPU CHP DSP0 initialization failure
l Severity: Minor
Probable Cause
DSP software or hardware error
2-48

Chapter 2 Alarm
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.90 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-49

2.1.91 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.92 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-50

Chapter 2 Alarm
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.93 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.94 198087255 Rx PLL2 unlock

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

Probable Cause
System Impact
None
Handling Suggestion
2.1.95 198087256 Tx PLL1 unlock

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

Chapter 2 Alarm
2.1.96 198087257 Tx PLL2 unlock

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

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

Handling Suggestion
2.1.98 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.99 198087260 EEPROM resource can not be used

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

Chapter 2 Alarm
System Impact
None
Handling Suggestion
please replace TRM module.
2.1.100 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.101 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-55

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.102 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.103 198087264 PA overtemperature major alarm(BTS V2)

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

Chapter 2 Alarm
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.104 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.105 198087266 PA power overvoltage

Alarm Property
l Description: PA power overvoltage
2-57

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.106 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.107 198087268 Downlink checksum error of DLRC_AL1

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

Chapter 2 Alarm
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.108 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.109 198087270 80w PA VSWR alarm

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

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.110 198087271 80w PA overtemperature

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

Alarm Property
l Description: 80w PA overtemperature major alarm
l Severity: Minor
2-60

Chapter 2 Alarm
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.112 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-61

2.1.113 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.114 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-62

Chapter 2 Alarm
2.1.115 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.116 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-63

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.117 198087278 TPF unlock

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

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

Chapter 2 Alarm
Probable Cause
System Impact
None
Handling Suggestion
2.1.119 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-65

2.1.120 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.121 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-66

Chapter 2 Alarm
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.122 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.123 198087288 PA power overvoltage alarm

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

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.124 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.125 198087290 PA VSWR alarm

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

Chapter 2 Alarm
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.126 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.127 198087292 PA temperature major alarm

Alarm Property
l Description: PA temperature major alarm
2-69

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.128 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-70

Chapter 2 Alarm
2.1.129 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.130 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-71

2.1.131 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.132 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-72

Chapter 2 Alarm
2.1.133 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.134 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-73

2.1.135 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.136 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-74

Chapter 2 Alarm
2.1.137 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.138 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-75

2.1.139 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.140 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-76

Chapter 2 Alarm
2.1.141 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.142 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-77

2.1.143 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.144 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-78

Chapter 2 Alarm
2.1.145 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.146 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-79

2.1.147 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.148 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-80

Chapter 2 Alarm
2.1.149 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.150 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-81

2.1.151 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-82

Chapter 2 Alarm

Alarm Property
l Severity: Minor
Probable Cause
System Impact
None
Handling Suggestion
2.1.154 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-83

2.1.155 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.156 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-84

Chapter 2 Alarm
2.1.157 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.158 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
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-85

2.1.159 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.160 198087325 Rack temperature minor alarm

Alarm Property
l Description: Rack temperature minor alarm
l Severity: Warning
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-86

Chapter 2 Alarm
2.1.161 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.162 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
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.
2-87


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
Handling Suggestion

2. Examin the fans;
2-88

Chapter 2 Alarm

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
Handling Suggestion

2. Examin the fans;
2-89


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
Handling Suggestion

2. Examin the fans;
2-90

Chapter 2 Alarm

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
Handling Suggestion
1. Examin the error-detection circuit;

2. Examin the fans;
2-91

2.1.171 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.172 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-92

Chapter 2 Alarm
2.1.173 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.174 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-93

2.1.175 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.176 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-94

Chapter 2 Alarm
2.1.177 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.178 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-95

2.1.179 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.180 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-96

Chapter 2 Alarm
2.1.181 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.182 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-97

2.1.183 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.184 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
Handling Suggestion
None
2-98

Chapter 2 Alarm
2.1.185 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.186 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
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-99

2.1.187 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.188 198087433 Diversity antenna identical

Alarm Property
l Description: Diversity antenna identical
l Severity: Major
Probable Cause
Wrong connection of diversity antenna
System Impact
None
Handling Suggestion
Check the connection of ant line as quickly as possible.
2-100

Chapter 2 Alarm
2.1.189 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.190 198087444 Diversity antenna identical

Alarm Property
l Description: Diversity antenna identical
l Severity: Warning
Probable Cause
Wrong connection of diversity antenna
System Impact
None
Handling Suggestion
Check the connection of ant line as quickly as possible.
2-101

2.1.191 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.192 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
Handling Suggestion
wait for a while ,and operate service after alarm restored
2-102

Chapter 2 Alarm
2.1.193 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.194 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-103

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.195 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.196 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)
System Impact
None
2-104

Chapter 2 Alarm
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.197 198087460 positive 12 voltage alarm

Alarm Property
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.198 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
2-105

System Impact
None
Handling Suggestion
change DTRU module or BBTR board
2.1.199 198087462 DSP 1.2v voltage alarm

Alarm Property
l Description: DSP 1.2v voltage alarm
l Severity: Major
Probable Cause
DPB board of DTRU module,1.2V power module has alarm
System Impact
None
Handling Suggestion
change DTRU module
2.1.200 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
2-106

Chapter 2 Alarm
Handling Suggestion
change DTRU module
2.1.201 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
System Impact
None
Handling Suggestion
change DTRU module
2.1.202 198087470 Fan absence alarm

Alarm Property
l Description: Fan absence alarm
l Severity: Warning
Probable Cause
Fan error or absence
System Impact
None
2-107

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.203 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.204 198087472 CMB and FNCB RS485 link break alarm

Alarm Property
l Description: CMB and FNCB RS485 link break alarm
l Severity: Warning
Probable Cause
interrupt RS485 communication between fan controller and CMB
System Impact
None
2-108

Chapter 2 Alarm
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.205 198087473 DTPU CPU overload

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

Alarm Property
l Description: Status of TX5 filter alarm
l Severity: Major
Probable Cause
TX5 is adjusting or loss over 5dB
System Impact
None
2-109

Handling Suggestion
Replace the FCU, or reset the TRM that connected with it
2.1.207 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.208 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
2-110

Chapter 2 Alarm
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.1.209 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.210 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
2-111

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.1.211 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.212 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
2-112

Chapter 2 Alarm
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.1.213 198087510 CPU of FIB overload

Alarm Property
l Description: CPU of FIB overload
l Severity: Warning
Probable Cause
System Impact
None
Handling Suggestion
2.1.214 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
2-113

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.215 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
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.216 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
2-114

Chapter 2 Alarm
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.217 198088003 PA Power Voltage Adjusting Data Illegal

Alarm Property
l Description: PA Power Voltage Adjusting Data Illegal
l Severity: Warning
Probable Cause
Set Data out of Range
System Impact
None
Handling Suggestion
1.Change Static Power data

2.Update setting
2.1.218 198088004 Access iBSC failure

Alarm Property
l Description: Access iBSC failure
l Severity: Major
Probable Cause
Authentication failed or unconnected response
2-115

System Impact
None
Handling Suggestion
1.Authentication again
2.Check physical link
2.1.219 198088005 Control link broken

Alarm Property
l Description: Control link broken
l Severity: Major
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.220 198088006 Operation link broken(CS)

Alarm Property
l Description: Operation link broken(CS)
l Severity: Minor
Probable Cause
the transmission line is broken
2-116

Chapter 2 Alarm
System Impact
None
Handling Suggestion
check the transmission line
2.1.221 198088007 Operation link broken(PS)

Alarm Property
l Description: Operation link broken(PS)
l Severity: Minor
Probable Cause
the transmission line is broken
System Impact
None
Handling Suggestion
2.1.222 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
2-117

System Impact
None
Handling Suggestion
configuration
parameter again.
2.1.223 198088009 DSP initialization failure

Alarm Property
l Description: DSP initialization failure
l Severity: Minor
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.224 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
2-118

Chapter 2 Alarm
System Impact
None
Handling Suggestion
Power-down Re-starting and re-configuration AD6537,send the

appropriate warning information
2.1.225 198088011 Tx PLL unlock

Alarm Property
l Description: Tx PLL unlock
l Severity: Minor
Probable Cause
Clock signal instability or PLL failed
System Impact
None
Handling Suggestion
Forbid TRM,send
warning information
2.1.226 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.
2-119

System Impact
None
Handling Suggestion
send warning information
2.1.227 198088013 FLASH memory fault

Alarm Property
l Description: FLASH memory fault
l Severity: Major
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.228 198088014 Run abnormity of DSP

Alarm Property
l Description: Run abnormity of DSP
l Severity: Major
Probable Cause
DSP programming error
2-120

Chapter 2 Alarm
System Impact
None
Handling Suggestion
Reset DSP,load DSP software version,configuration CHP parameters.
2.1.229 198088015 FPGA interface fault

Alarm Property
l Description: FPGA interface fault
l Severity: Major
Probable Cause
DSP and FPGA interface interruption
System Impact
None
Handling Suggestion
load FPGA version again,reset HBTS,

replace HBTS
2.1.230 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
2-121

System Impact
None
Handling Suggestion
Reset HBTS
2.1.231 198088017 Wrong receive channel of RF

Alarm Property
l Description: Wrong receive channel of RF
l Severity: Minor
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.232 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
2-122

Chapter 2 Alarm
System Impact
None
Handling Suggestion
Configuration the IP address of DNS by LMT.
2.1.233 198088019 Analyse failure of DNS domain name

Alarm Property
l Description: Analyse failure of DNS domain name
l Severity: Major
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.234 198088020 IPSec failure

Alarm Property
l Description: IPSec failure
l Severity: Major
Probable Cause
Can not access
System Impact
None
2-123

Handling Suggestion
Configuration IPSec parameter again
2.1.235 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
System Impact
None
Handling Suggestion
1.reset the frequency point with HTRG

2.Replace supporting the rang of frequency HTRG
2.1.236 198088022 Get HBTS is 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
2-124

Chapter 2 Alarm
Handling Suggestion
Configuration the IP address、subnet mask、gateway、port of iBSC and HBTS by LMT.
2.1.237 198088023 Over temperature

Alarm Property
l Description: Over temperature
l Severity: Minor
Probable Cause
Over temperature
System Impact
None
Handling Suggestion
Switch off power,check
2.1.238 198088024 Voltage abnormity

Alarm Property
l Description: Voltage abnormity
l Severity: Minor
Probable Cause
Voltage abnormity
System Impact
None
Handling Suggestion
Check power
2-125

2.1.239 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
System Impact
if change successful，no impact to the service
Handling Suggestion
check the abis link on the earth surface, and restore it as soon as possible
2.1.240 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-126

Chapter 2 Alarm
2.1.241 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
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.242 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-127

2.1.243 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
System Impact
The E1 site slave rack 1 may not work correctly
Handling Suggestion
2.1.244 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-128

Chapter 2 Alarm
2.1.245 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
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.246 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-129

2.1.247 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)
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.248 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-130

Chapter 2 Alarm
2.1.249 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
System Impact
Handling Suggestion
2.1.250 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-131

2.1.251 198088037 Mains power failure alarm

Alarm Property
l Description: Mains power failure alarm
l Severity: Major
Probable Cause
AC mains failure
System Impact
user define
Handling Suggestion
check AC
2.1.252 198088038 Alarm of the trx is 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-132

Chapter 2 Alarm
2.1.253 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.
Handling Suggestion
Reset the Slave reported in the alarm
2.1.254 199000256 OMC port is link is down

Alarm Property
l Description: OMC port's link is down
l Severity: Warning
Probable Cause
OMC port's link is down.
System Impact
OMC port can't transfer data.
Handling Suggestion
1. If OMM is outside, please check OMC port's link if it is up.

2. If OMM is inside, OMC over fabric, please check if there is inner media fault. OMC over base,
please check if there is control fault. Yes, deal with them first. No, Please contact ZTE Corporation.
2-133

2.1.255 199000512 Trunk loss of frame

Alarm Property
l Description: Trunk loss of frame
l Severity: Major
Probable Cause
Two ends have no common ground; the clocks are not synchronous; transmission equipment has a
failure.
System Impact
Trunk signal is broken
Handling Suggestion
Check if the equipment cable impedance of our company matches, if the board's DIP switch matches
the cable and if the rear board's jumper cap matches the cable.
Y-> Go to "2"
Re-set the board's DIP switch or rear board's jumper cap and then check if the alarm is eliminated. If
the alarm is eliminated, end alarm handling, otherwise, go to "2".
2. Use the multimeter to detect if the grounding signal of the equipment from both ends is reliable.
Y-> Go to "3"
Use the multimeter to detect if the grounding signal of the equipment from both ends is reliable and
then check if the alarm is eliminated. If the alarm is eliminated, end alarm handling, otherwise,
go to "3".
3. Check if the CLKG board locks the clock (TRACE evergreen)
Y-> Go to "4"
N-> Lock the clock.
4. Check if the clock references of two matching NEs or nodes are consistent.
Y-> Go to "5"
4. Modify the clock benchmark, ensuring the clock references of two matching NEs or nodes are
consistent.
5. Ask for assistant of the transmission equipment maintaining personnel to check if the transmission
equipment is exceptional. If there is any exception, locate the fault through step-by-step physical
diagnosis and circulating test. Please contact ZTE Corporation if the problem can not be solved.
2-134

Chapter 2 Alarm
2.1.256 199000513 Trunk loss of signal

Alarm Property
l Description: Trunk loss of signal
l Severity: Major
Probable Cause
The wire E1 is not connected or wrongly connected on DDF ; E1 breaks; the upstream equipment is
exceptional.
System Impact
Trunk signal is broken.
Handling Suggestion
1. Check if E1 on DDF is connected and then check if the alarm is eliminated.

Y-> The alarm is eliminated. End alarm handling.
N-> Go to "2"
2. Make a self-loop E1 on the local end and then check if the alarm is eliminated.
Y->Detect the upstream equipment, referring to suggestions on upstream equipment troubleshooting.
N-> Go to "3"
3. Replace the board and end alarm handling.
2.1.257 199000514 Trunk alarm indication signal

Alarm Property
l Description: Trunk alarm indication signal
l Severity: Major
Probable Cause
There is something wrong with upstream equipment.
System Impact
2-135

Handling Suggestion
Check and remove alarms relating to E1 of upstream equipment. If the alarm can not be eliminated,
please contact ZTE Corporation.
2.1.258 199000515 Trunk loss of CRC multi-frame

Alarm Property
l Description: Trunk loss of CRC multi-frame
l Severity: Major
Probable Cause
Multi-frame format is inconsistent.
System Impact
Handling Suggestion
Check if the frame format for the two matching ends is consistent. If it is not consistent, configure the
same one for the two ends. If the alarm can not be eliminated, please contact ZTE Corporation.
2.1.259 199000517 Trunk remote alarm indication

Alarm Property
l Description: Trunk remote alarm indication
l Severity: Major
Probable Cause
There is something wrong with the signals sent by the local end or with the intermediate transmission
equipment. All kinds of faults that may result in LOS, AIS, LOF on the peer end would probably
cause this alarm.
System Impact
2-136

Chapter 2 Alarm
Handling Suggestion
1.At this time, at least one alarm among LOS, AIS LOF occurs on the peer end. Check and record the
peer-end alarm. Check the intermediate transmission equipment for this trunk link to see if there
is any failure. If there is , eliminate the failure.
2. Please contact ZTE Corporation if the problem can not be solved.
2.1.260 199000518 Trunk link is used for CSU loopback test

Alarm Property
l Description: Trunk link is used for CSU loopback test
l Severity: Minor
Probable Cause
The equipment at end A sends CSU link building code to end B, and this trunk link is set to loopback
at end B. And CSU test starts. If this trunk link is not used for CSU loopback test, this alarm won't be
triggered.
System Impact
Trunk will be blocked when it is configed.
Handling Suggestion
After diagnosis and test, do some settings, where end A sends the command of canceling CSU
loopback to end B.
2.1.261 199001024 Cell Delineation Not Synchronized

Alarm Property
l Description: Cell Delineation Not Synchronized
l Severity: Minor
2-137

Probable Cause
HEC is damaged. The cell can not be located from the physical layer's frame.Usually it is triggered
by bottom faults or it is because the local-end equipment and the peer-end equipment process
HEC in different ways.
System Impact
Possibly communication cannot work well
Handling Suggestion
1. Check if there are other alarms accompanying it's occurrence. If there are, eliminate other alarms
firstly and then check if this alarm is eliminated.
N-> Go to "2"
2. Check if both two ends are configured to SDH mode or SONET mode. If the mode is not same,
configure a correct signal mode for them and then check if the alarm is eliminated.
N->Please contact ZTE Corporation.
2.1.262 199001025 Loss of Cell Delineation

Alarm Property
l Description: Loss of Cell Delineation
l Severity: Minor
Probable Cause
LCD is triggered after OCD lasting for 4ms.
System Impact
Possibly communication cannot work.
2-138

Chapter 2 Alarm
Handling Suggestion
1. Check if there are other alarms accompanying it's occurrence. If there are, eliminate other alarms
N-> Go to "2"
2. Check if both two ends are configured to SDH mode or SONET mode. If the mode is not same,
configure a correct signal mode for them and then check if the alarm is eliminated.
2.1.263 199001026 Cell delineation do not synchronization about

cell on E1 link
Alarm Property
l Description: Cell delineation do not synchronization about cell on E1 link
l Severity: Minor
Probable Cause
The HEC field of cell header is corrupted which result in loss of delineation. This may happen when
physical layer problem occurs or different HEC processes by two ends are taken.
System Impact
Data reception is failure and signaling link is down.
Handling Suggestion
1.Check if there are other alarms accompanying it's occurrence. If there are, eliminate other alarms
Y->The alarm is eliminated. End alarm handling.
N->Go to "2"
2. Pull out and insert the board. Reset the board to check if the alarm is eliminated.
Y->End.
2-139

2.1.264 199001285 Clock chip is in preheat status

Alarm Property
l Description: Clock chip is in preheat status
l Severity: Minor
Probable Cause
The board experiences reset. The SETS chip and the crystal oscillator needs to be fully preheated.
System Impact
Output clock is unstable.
Handling Suggestion
Normal procedure after board reset, please wait for the end of warm-up procedure. Clock tests can
be taken unless this alarm is cleared.
2.1.265 199001286 Input clock of the board is lost

Alarm Property
l Description: Input clock of the board is 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. One clock board in the same shelf is faulty or not exist.
4. Board is faulty.
System Impact
Board operaton might be abnormal.
2-140

Chapter 2 Alarm
Handling Suggestion
1. Check if the two clock boards in the same shelf are normal, if one of them is normal, then no
need to handle.
2. Replace the board.
2.1.266 199001792 SDH SONET Loss of signal

Alarm Property
l Description: SDH SONET Loss of signal
l Severity: Major
Probable Cause
Upstream optical transmit device has faults; Optical fiber transmission line has faults; Fiber pigtail
and flange between local-end optical distribution frame and equipment have faults; Local-end
fiber-optical receiver has faults.
System Impact
All received trunk signals are broken.
Handling Suggestion
The normal receiving optical power should be less than -8dBm and more than -28dBm.
1. It needs to check if the fiber modules of both ends are matching,including data rate、optical
wavelength、multi mode、single mode and so on.
If they are not matching,please replace the correct fiber module.
N-> Go to "2"
2. Use optical power meter to detect the power for receiving optical signal at local end to see if
the power is within the above-mentioned range.
Y-> If it is within this range, go to step 4.
Y-> If it is not within this range, it can be concluded that the optical transceiver module has faults. In
this case, go to step 3.
3. Replace this fiber module or board, and then check if the alarm is eliminated.
N-> Go to "4"
4. Detect the transmitting optical signal by use of the transmitting end at the peer end office to
see if it is within the prescribed range.
Y-> If it is within this range, go to step 6.
2-141

Y-> If it is not within this range, it can be concluded that some faults have occurred at the peer
end. In this case, go to step 5.
5. It needs to ask maintenance personnel to check the peer-end office. After troubleshooting at
the peer end, check if the alarm is eliminated.
N-> Go to "6"
6. There may be something wrong with the transmission equipment. It needs to ask the maintenance
personnel to do troubleshooting of maintaining transmission equipment or contact ZTE Corporation.
2.1.267 199001793 SDH SONET Loss of frame

Alarm Property
l Description: SDH SONET Loss of frame
l Severity: Major
Probable Cause
The upriver SDH equipment has faults.
System Impact
All received trunk signals are broken.
Handling Suggestion
Ask relating maintenance personnel to do troubleshooting of SDH transmission equipment. Please

contact ZTE Corporation if the problem can not be solved.
2.1.268 199001794 SDH SONET Regenerator section trace

mismatch/Section trace mismatch
Alarm Property
l Description: SDH SONET Regenerator section trace mismatch/Section trace
mismatch
l Severity: Major
2-142

Chapter 2 Alarm
Probable Cause
The optical fiber on the optical distribution frame is wrongly connected during optical fiber cutover and
scheduling, or the expected value is wrongly set in the network management system.
System Impact
The connection of all trunks is incorrect.
Handling Suggestion
1. Check if there is something wrong with the optical fiber connections on ODFs at the local end
and the peer end.
Y-> If there is, go to step 2.
Y-> If there isn't , go to step 3.
2. Have the optical fiber well connected, and check if the alarm is eliminated.
N-> Go to "3"
3. Check if the expected values of the "section access point identifier" at both ends are consistent.
Y-> If they are consistent, go to step 5.
Y-> If they aren't consistent, go to step 4.
4. Configure the same expected value for the "section access point identifier" at both ends, and
then check if the alarm is eliminated.
N-> Go to "5"
5. Please contact ZTE Corporation if the problem can not be solved.
2.1.269 199001795 SDH SONET MS alarm indication signal/Line

alarm indication signal
Alarm Property
l Description: SDH SONET MS alarm indication signal/Line alarm indication signal
l Severity: Major
Probable Cause
The upriver equipment has faults, such as LOS,LOF etc.
System Impact
All received trunk signals transmitted by this SDH/SONET line are broken.
2-143

Handling Suggestion
Eliminate the "primary fault" according to the alarm generated from the network node equipment in
the corresponding multiplexing section. If the alarm can not be eliminated, please contact ZTE
Corporation.
2.1.270 199001796 SDH SONET MS far-end reception failure/Line

far-end reception failure
Alarm Property
l Description: SDH SONET MS far-end reception failure/Line far-end reception failure
l Severity: Minor
Probable Cause
The up direction of the downstream equipment has faults.
System Impact
All sended trunk signals transmitted by this SDH/SONET line are broken.
Handling Suggestion
Eliminate the "primary fault" according to the alarm generated from the network node equipment in
the corresponding multiplexing section. If the alarm can not be eliminated, please contact ZTE
Corporation.
2.1.271 199001797 SDH SONET Signal failure

Alarm Property
l Description: SDH SONET Signal failure
l Severity: Major
2-144

Chapter 2 Alarm
Probable Cause
As for all NEs in the multiplexing section where the board is located, the fiber pigtail connectors in
the down direction are contaminated and the transmission line attenuation enhances, or optical
transmission mode changes, which result in error codes; It may also be caused by ADM transmitting
device failure.
System Impact
All recevied trunk signals transmitted by this SDH/SONET line generate kinds of alarms.
Handling Suggestion
1. Check if the fiber pigtail heads are contaminated.

Y-> If they are contaminated, go to step 2.
N-> Go to "3".
2. Clean the fiber connectors, and check if the alarm is eliminated.
N-> Go to "3"
3. Use optical power meter to detect the optical power attenuation of each connection point in the
down direction in the corresponding multiplexing section to see if it is excessive.
Y-> If it is, go to step 4.
N-> Go to "5"
4. Adjust the attenuation to normal value, and check if the alarm is eliminated.
N-> Go to "5"
5. Ask the transmission equipment maintaining personnel to check ADM transmitting device to
see if there is any fault. End alarm handling.
2.1.272 199001798 SDH SONET Signal deterioration

Alarm Property
l Description: SDH SONET Signal deterioration
l Severity: Minor
Probable Cause
Eliminate SF first when SD and SF occur at the same time; If SD occurs alone, it can be concluded
that the ADM transmission device has faults.
2-145

System Impact
Alarms indicated for partial Trunks.
Handling Suggestion
1. If SF occurs, eliminate SF first. If the problem can still not be eliminated after SF is eliminated, go
to step 2.
2. Check the optical fibers and fiber optical transceivers at the local end and the peer end, and make
sure the fibers are well connected and the optical transceiver modules are not loose.
N-> Go to "3"
N-> Go to "4"
N-> Go to "5"
personnel to do troubleshooting of transmission equipment, or contact ZTE Corporation.
2.1.273 199001799 SDH SONET Loss of AU pointer/Loss of path

pointer
Alarm Property
l Description: SDH SONET Loss of AU pointer/Loss of path pointer
l Severity: Major
Probable Cause
The upriver AU-4 pointer processing unit has faults.
System Impact
All received trunk signals transmitted by this SDH/SONET line are broken.
Handling Suggestion
Ask the maintenance personnel of transmission network to check if the upstream VC-4 channel
control unit has faults. If the transmission is found no problem, please contact ZTE Corporation.
2-146

Chapter 2 Alarm
2.1.274 199001800 SDH SONET AU alarm indication signal/Path

alarm indication signal
Alarm Property
l Description: SDH SONET AU alarm indication signal/Path alarm indication signal
l Severity: Major
Probable Cause
The upriver VC-4 channel control unit has faults.
System Impact
All received trunk signals transmitted by this SDH line are broken.
Handling Suggestion
Ask the maintenance personnel of transmission network to check if the upstream VC-4 channel
control unit has faults. If the transmission is found no problem, please contact ZTE Corporation.
2.1.275 199001801 SDH SONET HP trace mismatch/ Path trace

mismatch
Alarm Property
l Description: SDH SONET HP trace mismatch/ Path trace mismatch
l Severity: Major
Probable Cause
The optical fiber on the optical distribution frame is wrongly connected, or the expected value is
wrongly set in the network management system during optical fiber cutover and scheduling.
System Impact
The connection of all trunks is incorrect.
2-147

Handling Suggestion
and the peer end.
Y-> Go to "3"
N-> Go to "2"
2. Correctly connect the optical fibers on ODFs at the local end and the peer end and then check if
the alarm is eliminated.
N-> Go to "3"
3. Check if the expected values of the "VC-4 channel access point identifier (J1B)" at both ends
are consistent.
Y-> Go to "5"
N-> Go to "4"
4. Configure the same expected values for the "VC-4 channel access point identifier (J1B)" at both
ends, and then check if the alarm is eliminated.
N-> Go to "5"
5. Please contact ZTE Corporation.
2.1.276 199001802 SDH SONET HP unequipped/Path unequipped

Alarm Property
l Description: SDH SONET HP unequipped/Path unequipped
l Severity: Major
Probable Cause
During project installation, the internal cross connection of SDH network is not complete, or the SDTB
remote device isn't equipped with the channel where SDTB locates.
System Impact
All received trunk signals transmitted by this SDH line are broken.
Handling Suggestion
Ask the maintenance personnel for transmission network to check if the upstream VC-4 channel
control unit has faults(C2B).
2-148

Chapter 2 Alarm
2.1.277 199001803 SDH SONET HP Label mismatch/Path label

mismatch
Alarm Property
l Description: SDH SONET HP Label mismatch/Path label mismatch
l Severity: Major
Probable Cause
During project installation, the internal cross connection of SDH network is not complete.
System Impact
All received trunk signals transmitted by this SDH line may be broken.
Handling Suggestion
Ask the maintenance personnel for transmission network to check if the upstream and downstream
circuit configuration (C2B) of the DXC devices in each station during the corresponding timeslot
is correct.
2.1.278 199001804 SDH SONET HP remote reception failure/Path

remote reception failure
Alarm Property
l Description: SDH SONET HP remote reception failure/Path remote reception failure
l Severity: Minor
Probable Cause
There is network node failure in VC-4 channel where board locates.
System Impact
All sended trunk signals transmitted by this SDH/SONET line are broken.
2-149

Handling Suggestion
Eliminate the "source fault" according to the alarm generated from the network node equipment in
VC-4 channel where the board locates. If the alarm can not be eliminated, please contact ZTE
Corporation.
2.1.279 199001805 SDH SONET Loss of multi-frame

Alarm Property
l Description: SDH SONET Loss of multi-frame
l Severity: Major
Probable Cause
There is failure of the upstream VC-4 channel control unit.
System Impact
All received trunk signals transmitted by this SDH line may be broken.
Handling Suggestion
Ask the maintenance personnel for transmission network to check if the upstream VC-4 channel
control unit (H4) has faults.
2.1.280 199001806 SDH SONET Loss of TU pointer/Loss of virtual

tributary pointer
Alarm Property
l Description: SDH SONET Loss of TU pointer/Loss of virtual tributary pointer
l Severity: Warning
Probable Cause
The upstream TU pointer processing unit is failure.
2-150

Chapter 2 Alarm
System Impact
The received trunk signal transmitted by this tributary unit is broken.
Handling Suggestion
Ask the maintenance personnel of transmission network to check if the upstream TU-12 tributary
pointer has faults. If the problem can still not be solved, please contact ZTE Corporation.
2.1.281 199001807 SDH SONET Tributary unit alarm indication

signal/Virtual tributary alarm indication signal
Alarm Property
l Description: SDH SONET Tributary unit alarm indication signal/Virtual tributary alarm
indication signal
l Severity: Warning
Probable Cause
There is failure of the upstream TU-12 tributary pointer processing unit, which may includes TU
AIS\TU LOM\TU LOP\TU UNEQ.
System Impact
Handling Suggestion
Ask the maintenance personnel of transmission network to check if the upstream TU-12 tributary
pointer has faults. If the problem can still not be solved, please contact ZTE Corporation.
2.1.282 199001808 SDH SONET LP remote defect indication/Virtual

tributary remote defect indication
Alarm Property
l Description: SDH SONET LP remote defect indication/Virtual tributary remote defect
indication
l Severity: Warning
2-151

Probable Cause
1. Local TU-12 tributary function is fault. 2. The equipment of other nodes on TU-12 tributary may
has tributary function faults.
System Impact
The sended trunk signal transmitted by this tributary unit is broken.
Handling Suggestion
1. Check if there is something wrong with the optical fiber connections on ODFs at the local end and
the peer end and check if the processing of TU-12 tributary pointer of the upstream equipment
has faults.
Y-> If there isn't, go to step 3.
2. Have the optic fiber well connected, and check if the alarm is eliminated. This is upstream
troubleshooting.
N-> Go to "3"
3. Check the alarm forms at both ends. Firstly detect the peer-end alarm forms. The peer-end
alarms should be firstly eliminated.Trough loopback operation, perform troubleshooting for local-end
equipment, transmission equipment and peer-end equipment step by step. Software loopback and
hardware loopback can be applied.
Please contact ZTE Corporation or replace the board if the problem can not be solved.
2.1.283 199001809 SDH SONET LP remote failure indication/Virtual

tributary remote failure indication
Alarm Property
l Description: SDH SONET LP remote failure indication/Virtual tributary remote failure
indication
l Severity: Warning
Probable Cause
The upstream VC-12 tributary control unit is failure.
System Impact
2-152

Chapter 2 Alarm
Handling Suggestion
1. Check if there is something wrong with the optical fiber connections on ODFs at the local end and
the peer end and check if the processing of TU-12 tributary pointer of the upstream equipment
has faults.
Y-> If there isn't, go to step 3.
2. Have the optic fiber well connected, and check if the alarm is eliminated. This is the upstream
troubleshooting.
N-> Go to "3"
3. Check the alarm forms at both ends. Firstly detect the peer-end alarm forms. The peer-end
alarms should be firstly eliminated.Trough loopback operation, perform troubleshooting for local-end
equipment, transmission equipment and peer-end equipment step by step. Software loopback and
hardware loopback can be applied.
Please contact ZTE Corporation or replace the board if the problem can not be solved.
2.1.284 199001810 SDH SONET LP trace mismatch/Virtual tributary

trace mismatch
Alarm Property
l Description: SDH SONET LP trace mismatch/Virtual tributary trace mismatch
l Severity: Warning
Probable Cause
The cable on the optical distribution frame (DDF) is wrongly connected, or the expected value is
wrongly set in the network management system during cable cutover and scheduling.
System Impact
The connection of the trunk signal on this tributary unit is incorrect.
2-153

Handling Suggestion
and the peer end.
Y-> Go to "3"
N-> Go to "2"
2. Correctly connect the optic fibers on ODFs at the local end and the peer end and then check if
N-> Go to "3"
3. Check if the expected values of the "VC-12 channel access point identifier (J2B)" at both ends
are consistent.
Y-> Go to "5"
N-> Go to "4"
4. Configure the same expected values for the "VC-12 channel access point identifier (J2B)" at both
ends, and then check if the alarm is eliminated.
N-> Go to "5"
5. Please contact ZTE Corporation or replace the board.
2.1.285 199001811 SDH SONET LP unequipped/Virtual tributary

unequipped
Alarm Property
l Description: SDH SONET LP unequipped/Virtual tributary unequipped
l Severity: Warning
Probable Cause
During project installation, the internal cross connection of SDH network is not complete, or the
remote device isn't equipped with the tributary.
System Impact
The received trunk signal transmitted by this tributary unit may be broken.
2-154

Chapter 2 Alarm
Handling Suggestion
1. Check the optical fibers and fiber transceiver modules at the local end and the peer end, and make
sure the fibers are well connected and the fiber modules are not loose.
N-> Go to "2"
2. The configuration connection at both ends needs to be checked by the maintenance personnel.
Check if the signal label received by this tributary is consistent with that configured at local end. After
confirmation, check if the alarm has been eliminated.
N-> Go to "3"
Ask the maintenance personnel for transmission equipment to use SDH tester to check if the
upstream and downstream circuit configuration of each DXC node device on the transmission line
during the corresponding timeslot is correct, and check if V5 byte configuration is consistent with that
at peer-end. (The default configuration at local end is asynchronous mapping.)
4.Replace the board, view alarm information, or contact ZTE Corporation.
2.1.286 199001812 SDH SONET LP label mismatch/Virtual tributary

label mismatch
Alarm Property
l Description: SDH SONET LP label mismatch/Virtual tributary label mismatch
l Severity: Warning
Probable Cause
The upstream and downstream circuit configuration of each DXC during the corresponding timeslot is
incomplete. The information of V5 signal label is inconsistent with that at the peer end.
System Impact
The received trunk signal transmitted by this tributary unit may be broken.
2-155

Handling Suggestion
N-> Go to "2"
2. The configuration connection at both ends needs to be checked by the maintenance personnel.
Check if the information of V5 signal label is consistent with that at the peer end. After confirmation,
check if the alarm has been eliminated.
N-> Go to "3"
3. Replace the board, view alarm information, or contact ZTE Corporation.
2.1.287 199001816 SDH SONET Severe B1 error code

Alarm Property
l Description: SDH SONET Severe B1 error code
l Severity: Major
Probable Cause
(1) Signal reception attenuation is excessive. (2) There is failure of transmitting part of directly
connected transmission equipment. (3)Optical fiber connectors is unclean or connection of them is
incorrect.(4) Local-end receiving part is failure.
System Impact
Noise or call lose appears in the tone service on this SDH line. Error code appears in the data
service path.
Handling Suggestion
N-> Go to "2"
N-> Go to "3"
2-156

Chapter 2 Alarm
N-> Go to "4"
personnel special for maintaining transmission equipment to do troubleshooting or contact ZTE
Corporation.

Alarm Property
l Severity: Major
Probable Cause
(1) Signal reception attenuation is excessive. (2) Optical fiber connectors are unclean or connection
of them are incorrect. (3)Peer-end transmitting part failed in multiplexing section.(4) Local-end
receiving part failure in multiplexing section. (5) B1 error code.
System Impact
service path.
Handling Suggestion
N-> Go to "2"
N-> Go to "3"
N-> Go to "4"
Corporation.
2-157


Alarm Property
l Severity: Major
Probable Cause
(1) Signal reception attenuation is excessive. (2) Optical fiber connectors are unclean or connection
of them is incorrect. (3)There is failure of the peer-end transmitting part based on higher order path
(4) Local-end receiving part is failure. (5) B1, B2 error codes.
System Impact
Noise or call lose appears in the tone service on this HP. Error code appears in the data service path.
Handling Suggestion
N-> Go to "2"
N-> Go to "3"
N-> Go to "4"
Corporation.
2.1.290 199001819 SDH SONET Severe BIP-2 error code

Alarm Property
l Description: SDH SONET Severe BIP-2 error code
l Severity: Warning
2-158

Chapter 2 Alarm
Probable Cause
(1) Low order path is interfered. (2) There is failure of the peer-end transmitting part based on lower
order path. (3) Local-end receiving part is failure.
System Impact
Noise or call lose appears in the tone service on this tributary unit. Error code appears in the data
service path.
Handling Suggestion
N-> Go to "2"
N-> Go to "3"
N-> Go to "4"
Corporation.
2.1.291 199001820 SDH SONET MS remote error indication

Alarm Property
l Description: SDH SONET MS remote error indication
l Severity: Major
Probable Cause
connected transmission equipment. (3) Optical fiber connectors are unclean or connection of them is
incorrect. (4) Local-end receiving part is failure.
2-159

System Impact
service path.
Handling Suggestion
N-> Go to "2"
N-> Go to "3"
N-> Go to "4"
Corporation.
2.1.292 199001821 SDH SONET HP remote error indication

Alarm Property
l Description: SDH SONET HP remote error indication
l Severity: Major
Probable Cause
connected transmission equipment. (3) Optical fiber connectors are unclean or connection of them is
incorrect.(4) Local-end receiving part is failure.
System Impact
service path.
2-160

Chapter 2 Alarm
Handling Suggestion
N-> Go to "2"
N-> Go to "3"
N-> Go to "4"
Corporation.
2.1.293 199001826 SDH SONET LP remote error indication

Alarm Property
l Description: SDH SONET LP remote error indication
l Severity: Warning
Probable Cause
(1) Signal reception attenuation is excessive. (2)There is failure of transmitting part of directly
connected transmission equipment. (3)Optical fiber connectors are unclean or connection of them is
incorrect. (4) Local-end receiving part is failure.
System Impact
Noise or call lose appears in the tone service on this tributary unit. Error code appears in the data
service path.
2-161

Handling Suggestion
N-> Go to "2"
N-> Go to "3"
N-> Go to "4"
Corporation.
2.1.294 199005123 The configuration is not supported

Alarm Property
l Description: The configuration is not supported
l Severity: Warning
Probable Cause
Configure is error.
System Impact
The board do not work on the configuration .
Handling Suggestion
1. Check the additional information for this alarm, and look for the configuration error.
2.If this configuration-item is supported in the configure-dialog?
Y->Goto 3
N->Contact ZTE
3. If setting is incorrect, re-configure this item to correct value.
4. If setting is correct, replace the board with witch surpport the setting.
5. If the alarm is still existing?
Y->Goto 4
N->Contact ZTE
2-162

Chapter 2 Alarm
2.1.295 199005405 Clock board phase-lock loop work mode is

abnormal
Alarm Property
l Description: Clock board phase-lock loop work mode is abnormal
l Severity: Minor
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.

Y->Replace the board and go to "2".
N->Correctly input the clock reference and go to "2".
2.Check if the alarm is eliminated.
Y->End.
2.1.296 199005632 The hard disk used-rate is over threshold

Alarm Property
l Description: The hard disk used-rate is over threshold
l Severity: Minor
Probable Cause
The hard disk capacity of used has been over the alarm threshold which configured by user.
System Impact
The hard disk can not work normaly.
2-163

Handling Suggestion
1. Please make sure the hard disk usage settings are appropriate. If inappropriate please modify
as appropriate value.
2: Remove non-used data on the hard disk.
2.1.297 199005633 File system is abnormal

Alarm Property
l Description: File system is abnormal
l Severity: Major
Probable Cause
1. The hard disk doesn't exist.

2. The hard disk isn't formatted.
3. File system is abnormal.
System Impact
It's effect on the ability of store. Maybe the system is error, or some process can't run, even some
data is lost. When the alarm occurs, the board maybe change over from master to slave or reboot.
Handling Suggestion
1. Check the hard disk exists or not.

Y->Go to "3".
N->Please insert a hard disk, if this alarm is eliminated, end alarm handling. Otherwise, go to "3".
2. Check the hard disk is formatted or not.
Y->Go to "3".
N->Please format the hard disk, if this alarm is eliminated, end alarm handling, otherwise, go to "3".
3. Note down the alarm information and contact ZTE Corporation.
2.1.298 199005634 The hard disk on board gets IO error.

Alarm Property
l Description: The hard disk on board gets IO error.
l Severity: Minor
2-164

Chapter 2 Alarm
Probable Cause
The hard disk file system gets error when reading or writing.
System Impact
The hard disk can not work normaly.
Handling Suggestion
1. Check the hard disk is damaged or not;

Y: Repair the hard disk. If it's still gets IO error, go to "2";
N: Go to "2";
2. Change another good hard disk, Check the hard disk has IO error or not;
Y: Contact the ZTE;
N: End
2.1.299 199005646 Phase-lock loop of the board is unlocked

Alarm Property
l Description: Phase-lock loop of the board is unlocked
l Severity: Critical
Probable Cause
1. The clock extraction reference is changed, including the case that the clock output is closed by
the interface board when optical port is faulty. This leads to the change of clock board input. Or,
configuration is modified at NMS and a new optical port is used to extract the clock.
2. The change in input of clock board results in the change in output.
3. The board lock phase loop has hardware faults.
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-165

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.
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.
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.
2.1.300 199005666 Error packets of MAC is higher than the

specified threshold
Alarm Property
l Description: Error packets of MAC is higher than the specified threshold
l Severity: Minor
Probable Cause
Error packets of MAC is higher than specified threshold.
System Impact
The MAC port cannot be used or packets flow is limited.
Handling Suggestion
1.Check the connection between the port on this board and the peer end one if it is correct.
Y->Go to "2"
N->Check physical cable ,if it is not good, please replace a good cable, and check the alarm if
it is eliminated.
Y-> End.
N-> Go to "2".
2.Replace the board on the local end or the interface on the remote peer end and then check the
alarm if it is eliminated.
Y->End.
N->Go to "3"
3.Replace the remote peer board or the interface on the local end and then check the alarm if it is
eliminated.
Y->End.
2-166

Chapter 2 Alarm
2.1.301 199005670 Oscillator status is abnormal

Alarm Property
l Description: Oscillator status is 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.1.302 199005672 Clock source is not available

Alarm Property
l Description: Clock source is not available
Probable Cause
There are four reasons:

1. The slave clock port does not receive ESMC PDU for 5 seconds.
2. The SSM code that the slave clock port received is DNU.
3. The speed mode of the port is 10M.
4. Physical link of the port is broken.
System Impact
The slave clock port can not synchronize to the connected port.
2-167

Handling Suggestion
Check the physical connection, reconfigure the clock port or reconnect the port.
2.1.303 199005673 The setting of the dial switch is changed

Alarm Property
l Description: The setting of the dial switch is changed
l Severity: Major
Probable Cause
The setting of the dial switch on the CMM board has been changed.
System Impact
The board can not power on nomally.
Handling Suggestion
1) Checking the setting of dial switch is changed or not .

Y-> Go to 2)
N-> Go to 3)
2) Whether the user has modified the rack and shelf configuration and wants to update dial switch
setting to the configuration value.
Y-> Reset CMM board, then reset all the boards in the same shelf. If the boards power on normally,
to the end; otherwise, go to 3)
N-> Modify the setting to the correct value. If the alarm is recovered, to the end; otherwise go to 3)
3) Replace the CMM board and make the correct dial switch setting. Checking the alarm is recovered
or not.
Y-> To the end;
N-> Contact to ZTE.
2.1.304 199005760 Ethernet port is link is down

Alarm Property
l Description: Ethernet port's link is down
l Severity: Warning
2-168

Chapter 2 Alarm
Probable Cause
Ethernet port's link is down.
System Impact
MAC port can't transfer data.
Handling Suggestion
1. Reconnect or replace the cable.

3. Check the opposite port to make sure if it is falut.
4. Please modify the settings of the port to be correct. Please make work mode, speed mode, duplex
mode of both ends to be same. Please make master and slave mode to be match with each other.
2.1.305 199005761 The speed mode of Ethernet port does not

match with settings
Alarm Property
l Description: The speed mode of Ethernet port doesn't match with settings
l Severity: Major
Probable Cause
The speed mode settings of Ethernet port does not take effect.
System Impact
Ethernet port does not work on the speed mode which is set.
Handling Suggestion
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 on the both end to make it correct and consistent with each other, and
then check the alarm if it is eliminated.
Y->End.
N->Go to "2".
2.Please contact ZTE Corporation.
2-169

2.1.306 199005768 All of the board input clocks which have the
same frequency are lost.
Alarm Property
l Description: All of the board input clocks which have the same frequency are lost.
l Severity: Major
Probable Cause
1. The board is not in place (not properly inserted) in the slot.

2. The output clock of the clock board in the same shelf is error.
3. Clock board is faulty.
4. Clock cable is faulty.
5. Board is faulty.
System Impact
The board fails to synchronize with system clock and fails to work normally, leading to UE access
failure and interruption of board services.
Handling Suggestion
1. Check if the clock board in the same shelf is normal and the clock input cable is properly connected.
2.1.307 199005769 The master and slave mode of Ethernet port

does not match with settings
Alarm Property
l Description: The master and slave mode of Ethernet port doesn't match with settings
l Severity: Major
Probable Cause
The master and slave mode settings of Ethernet port does not take effect.
System Impact
The Ethernet port does not work on the master and slave mode which is set.
2-170

Chapter 2 Alarm
Handling Suggestion
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 and slave mode settings on the both end ports to make them correct and
consistent with each other, and then check the alarm if it is eliminated.
Y->End.
N->Go to "2".
2.1.308 199005770 The OMP board does not have any OMC port
Alarm Property
l Description: The OMP board doesn't have any OMC port
l Severity: Warning
Probable Cause
The OMP board doesn't have any OMC port.
System Impact
The OMP board could not communicate by OMC port.
Handling Suggestion
1.Check the backcard to make sure it is correct and inserted well.

2.Check the hardware of the board to make sure it supports OMC port.
2.1.309 199005771 The duplex mode of Ethernet port does not

match with settings
Alarm Property
l Description: The duplex mode of Ethernet port doesn't match with settings
l Severity: Major
2-171

Probable Cause
The duplex mode settings of Ethernet port does not take effect.
System Impact
Ethernet port does not work on the duplex mode which is set.
Handling Suggestion
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 on the both end ports to make them correct and consistent with
each other, and then check the alarm if it is eliminated.
Y->End.
N->Go to "2".
2.1.310 199005772 Board device fault

Alarm Property
l Description: Board device fault
l Severity: Minor
Probable Cause
Fault occur when read or write the register on the board, this is may be the hardware fault.
System Impact
Board operation might be abnormal.
Handling Suggestion
Replace the board.
2.1.311 199005773 High CRC error rate at E1/T1 bottom layer

Alarm Property
l Description: High CRC error rate at E1/T1 bottom layer
2-172

Chapter 2 Alarm
l Severity: Major
Probable Cause
The E1/T1 link is faulty or there is any other equipment fault in the uplink direction of the trunk link.
System Impact
Handling Suggestion
1. Check whether the trunk link at the local end is faulty and eliminate the primary fault. After that,
check if the alarm is eliminated.
N-> Go to "2"
2. Check whether there is any other equipment fault in the uplink direction of the trunk link. After
that, check if the alarm is eliminated.
2.1.312 199005774 High FAS error rate at E1/T1 bottom layer

Alarm Property
l Description: High FAS error rate at E1/T1 bottom layer
l Severity: Major
Probable Cause
The E1/T1 link is faulty or there is any other equipment fault in the uplink direction of the trunk link.
System Impact
2-173

Handling Suggestion
N-> Go to "2"
2.1.313 199005775 High EBIT error rate at E1 bottom layer

Alarm Property
l Description: High EBIT error rate at E1 bottom layer
l Severity: Major
Probable Cause
The E1 link is faulty or there is any other equipment fault in the downlink direction of the trunk link.
System Impact
Handling Suggestion
N-> Go to "2"
2.1.314 199005785 GPS module is abnormal

Alarm Property
2-174

Chapter 2 Alarm
l Description: GPS module is abnormal

l Severity: Major
Probable Cause
1.GPS is in searching state.

2.Satellite number that the GPS device searched is less than 4.
3.GPS PP1S output dither is very bad.
4.GPS antenna is abnormal.
System Impact
The board fails to synchronize with system clock and fails to work normally, leading to UE access
failure and interruption of board services.
Handling Suggestion
Check the GPS receiver and antenna feed status.
2.1.315 199005797 The hard disk is abnormal

Alarm Property
l Description: The hard disk is abnormal
l Severity: Major
Probable Cause
1. The hard disk doesn't exist.

2. The hard disk has serious fault cause the system not to find it.
3. The SMART of the hard disk is abnormal.
4. The SMART of the hard disk can't be gotten.
System Impact
The hard disk can not work normally.
2-175

Handling Suggestion
1.Check if the hard disk abnormal reason of the alarm information is that the hard disk doesn't exist.
Y-> Check if the hard disk doesn't exist. Yes, insert one. No, remove and insert the hard disk
or exchange one. Go to "3".
N-> Go to "2".
2. Check if the hard disk abnormal reason of the alarm information is that the smart is abnormal or
can't be gotten.
Y-> Exchange the hard disk. Go to "3".
N-> Go to "4".
3. Check the alarm if it is eliminated.
Y-> End alarm handling.
N-> Go to "4".
4. Contact ZTE Corporation.
Note.
If the hard disk can be hot plug in the board ,The flag of hard disk light is coincident with the flag
of hard disk location of alarm information. Otherwise, The flag of hard disk light is opposite to the
flag of hard disk location of alarm information.
2.1.316 199005798 The RAID of hard disks is abnormal

Alarm Property
l Description: The RAID of hard disks is abnormal
l Severity: Major
Probable Cause
1. The hard disks are not in RAID mode. Two hard disks are inserted in the board which don't
work in RAID mode.
2. Degraded but not sync.There is a hard disk of the RAID which doesn't exist or may be abnormal.
3. Failed.The master hard disk may be abnormal or removed when RAID doesn't sync completely.
4. Missing.Hard disk of RAID is abnormal.
5. Inactive.The RAID information of SAS controller is abnormal or the RAID information of the hard
disk on the board is not same as another.
System Impact
The hard disk can not work normally.
2-176

Chapter 2 Alarm
Handling Suggestion
1.Check if the RAID abnormal reason of the alarm information is that hard disks are not in RAID mode.
Y-> Set RAID mode.End alarm handling.
N-> Go to "2".
2.Check if the hard disk location of the alarm information is HD1(upper or left) or HD2(nether or right).
Y-> Check if the hard disk doesn't exist. Yes, insert one. Go to "4".
N-> Go to "3".
3. Check if there is an alarm exists which named "the hard disk is abnormal".
Y-> Reference to suggestion to handle the alarm. Go to "4".
N-> Go to "6".
4. Check the alarm if it is eliminated.
N-> Go to "5".
5. Check if the RAID status is degraded and sync by the diagnosis query.
Y-> When RAID syncs completely ,the alarm can be eliminated. End alarm handling.
N-> Go to "6".
Note.
If the hard disk can be hot plug in the board ,The flag of hard disk light is coincident with the flag
of hard disk location of alarm information. Otherwise, The flag of hard disk light is opposite to the
flag of hard disk location of alarm information.
2.1.317 199005799 Hard disk online

Alarm Property
l Description: Hard disk online
l Severity: Major
Probable Cause
1. Hard disk is inserted.

2. SAS controller is abnormal.
System Impact
The hard disk can not work normally. The board reboots.
2-177

Handling Suggestion
1. Check whether a hard disk is inserted.

Y->This alarm is normal phenomenon, end alarm handling.
N->Go to "2".
2.1.318 199005800 Hard disk offline

Alarm Property
l Description: Hard disk offline
l Severity: Major
Probable Cause
1. Hard disk is removed.

2. SAS controller is abnormal.
System Impact
The hard disk can not work normally. The board reboots.
Handling Suggestion
1. Check whether the hard disk is removed.

Y->This alarm is normal phenomenon, end alarm handling.
N->Go to "2".
2.1.319 199005890 Functional EPLD update failed

Alarm Property
l Description: Functional EPLD update failed
l Severity: Warning
Probable Cause
Function EPLD update failed.
2-178

Chapter 2 Alarm
System Impact
EPLD version is not update.
Handling Suggestion
1.Check whether the switch board is in the same shelf as this board, or the switch board in the shelf
where the OMP is located and the switch board (if there is any) are working normally.
Y-> Go to Step 2
N-> Restore the boards above to normal state, and check whether this alarm disappears: Y-> Go
to Step 2, N-> Contact ZTE.
2.Update the EPLD version again, and chek the board EPLD version is the new version number.
Y-> End.
N-> Contact ZTE.
2.1.320 199005930 NCPU version load failed

Alarm Property
l Description: NCPU version load failed
l Severity: Major
Probable Cause
NCPU version load failed.
System Impact
NCPU RUNNING ERR
Handling Suggestion
1.Check the Version exist.

Y.Turn 2.
N.Load the version and reload.
2.reboot the Ncpu device, and chek the alarm also existed.
Y.Alarm restore;
N.Turn 3.
3.change the board ,and reload.
Y.Load success ,hardware problem,turn 4.
N.Turn 4.
4.contact ZTE Corporation .
2-179

2.1.321 199007168 Port trunk fail

Alarm Property
l Description: Port trunk fail
l Severity: Minor
Probable Cause
PP board port aggregation failure:

1.Switch Board is not in place.
2.Port transceiver package exception.
switch board stack port aggregation failure：
1.Mate Board is not in place.
2.stack port transceiver package exception.
System Impact
as for PP board,the link connected with switch board does not work. As for switch board,if all of the
stack ports trunk failed, all ports of the poor board do not work.
Handling Suggestion
PP board port aggregation failure:

1.Check the both Switch Boards are in place.
Y->turn to 2.
N.if one is not in place,the port connected to tht switch board is at down state, the PP baord will
report warning information.
2.record the warning inforation,and contact with ZTE.
switch board stack port aggregation failure：
1.Check the mate Board is in place.
Y->turn to 2.
N.if it is not in place,the switch board will report warning information.
2.record the warning inforation,and contact with ZTE.
2.1.322 199007169 Inner port error

Alarm Property
l Description: Inner port error
l Severity: Minor
2-180

Chapter 2 Alarm
Probable Cause
1. The duplex mode of the switch port is abnormal and can't heal self.
2. The speed of the switch port is abnormal and can't heal self.
3. The duplex mode of the mac port is abnormal and can't heal self.
4. The speed of the mac port is abnormal and can't heal self.
System Impact
1. PP board: link broken

2. switch board: can't link to the pp board
Handling Suggestion
1. Reboot the board and check whether the alarm is restored.

N-> Make record of the related information and contact ZTE.
2.1.323 199007170 Trunk connect asymmetry

Alarm Property
l Description: Trunk connect asymmetry
l Severity: Minor
Probable Cause
Ports of the trunk are not symmetry
System Impact
System work abnormally
Handling Suggestion
check ports connect
2.1.324 199007171 Outer media trunk failed

Alarm Property
l Description: Outer media trunk failed
2-181

l Severity: Minor
Probable Cause
1.Media ports between the shelf are not linked or trunk failed
System Impact
adjunct shelf's media work abnormally
Handling Suggestion
check ports connect
2.1.325 199015360 Media status abnormal

Alarm Property
l Description: Media status abnormal
l Severity: Major
Probable Cause
the network process part such as the media cores, microengines or APP650/APP100 are abnormal
System Impact
The media process doesn't work
Handling Suggestion
Most probably because of the hardware error. If occurs repeatly, replace the board.
2.1.326 199015618 Too many bad frames received

Alarm Property
l Description: Too many bad frames received
l Severity: Minor
2-182

Chapter 2 Alarm
Probable Cause
the number of bad frames that the media interfaces have received at a certain period of time exceeds
the threshold
System Impact
May reduce the quality of communication
Handling Suggestion
Check the connection of fibre/wire.If occurs repeatly, replace the board.
2.1.327 199019712 APS channel mismatch

Alarm Property
l Description: APS channel mismatch
l Severity: Major
Probable Cause
Peer-end faults (configuration faults or devices which do not support exist, the symptom is the
bridging channel that the remote end indicates through K2 is not the one required by the local).
System Impact
APS automatic protection switching function is paralyzed. When the work optical port is abnormal,
protection optical port will not work, leading to service interruption on this optical interface.
Handling Suggestion
1. Check fiber connection.

Check fiber 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.
2. Check APS backup mode configuration at both ends.
Check APS backup mode (1+1 or 1:1) at local end to ensure configuration consistency at both ends.
3. Check APS protection direction at both ends.
Check APS protection direction (unidirectional or bidirectional) configured at local end. Ensure
configuration consistency at both ends.
4. Check whether APS is supported by the opposite equipment. Check whether APS configuration is
correct and has taken effect.
2-183

2.1.328 199019713 APS mode mismatch

Alarm Property
l Description: APS mode mismatch
l Severity: Major
Probable Cause
1. Fiber connection is wrong.

2. Configuration of APS backup mode at local end and opposite end is inconsistent.
3. Configuration of APS protection direction at local end and opposite end is inconsistent.
4. The equipment of the peer end is abnormal.
System Impact
When fiber connection is correct and work optical port works, service is not affected.
When work optical port is faulty, APS automatic protection switching might fail, and service on this
optical interface might be interrupted due to lack of protection.
Handling Suggestion
1. Check fiber connection.

Check fiber 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.
2. Check APS backup mode configuration at both ends.
Check APS backup mode (1+1 or 1:1) at local end to ensure configuration consistency at both ends.
3. Check APS protection direction at both ends.
Check APS protection direction (unidirectional or bidirectional) configured at local end. Ensure
configuration consistency at both ends.
2.1.329 199019715 MS APS channel gets errors

Alarm Property
l Description: MS APS channel gets errors
l Severity: Major
2-184

Chapter 2 Alarm
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. APS function is affected.

2. The board master/slave function is affected.
Handling Suggestion
Please try the following steps:

1. Reboot the board.
3. Replace the neighboring board.
4. Replace the slots .
2.1.330 199023050 Fan Device Absent

Alarm Property
l Description: Fan Device Absent
l Severity: Major
Probable Cause
Fan Device Removed /Fan Device Absent
System Impact
Device damaged
Handling Suggestion
Check fantray module
2.1.331 199023051 Power Unit Absent

Alarm Property
l Description: Power Unit Absent
2-185

l Severity: Major
Probable Cause
Power Unit Removed /Power Unit Absent
System Impact
Power Supply may be not enough
Handling Suggestion
Check power unit
2.1.332 199023106 Board initialized test failed

Alarm Property
l Description: Board initialized test failed
Probable Cause
There are devices failure on the board.
System Impact
The devices of the board is not available.
Handling Suggestion
1. Check Alarm information of the board.

1) Whether there is memory's fault.
Y-> Remove and plug the memory card again, power on the board to check if the alarm restored. Y->
The troubleshooting completes. N-> go to "2)".
N-> no memory’s fault,go to "2".
2) Replace the memory card by a new one and power on the board,then check if the alarm restored.
Y-> The troubleshooting completes. N-> go to "2".
2. Replace the faulty board by a new one
and power one the board to check if the alarm restored. Y-> The troubleshooting completes. N->
go to "3".
3. Make records of the alarm
information and contact ZTE Cooperation.
2-186

Chapter 2 Alarm
2.1.333 199025602 Half-Fixed Connection abnormal

Alarm Property
l Description: Half-Fixed Connection abnormal
l Severity: Major
Probable Cause
Reason A: The line clock of the frame where this board is located in has jitters.
Reason B: There is a hardware fault in the switching chip of this board.
System Impact
The bear link maybe not work
Handling Suggestion
1.Check connect chip clock is working order. Check whether the problem is repaired when the
worked out clock error.
Y->Done N->Go to step2
2.Change the board, Check whether the problem is repaired when changed the board.
Y->Done N->contact ZTE
2.1.334 199025856 Rack temperature is higher than high threshold

Alarm Property
l Description: Rack temperature is higher than high threshold
l Severity: Minor
Probable Cause
The temperature of the rack exceeds the pre-set upper limit of the alarm threshold.
System Impact
2-187

Handling Suggestion
1.Check if the pre-set high limit of the alarm threshold configured in the background for rack
temperature is reasonable.
Y->Go to "2".
N->Modify the alarm threshold and synchronize it to the foreground. Check if the alarm is eliminated:
if so, end. If not, go to "2".
2.Increase the temperature of the rack and check if the alarm is eliminated.
Y->End.
N->Contact ZTE Corporation.
2.1.335 199025857 Rack temperature is lower than low threshold

Alarm Property
l Description: Rack temperature is lower than low threshold
l Severity: Minor
Probable Cause
1.Rack temperature value reported now is under the low threshold.

2.The setting of the rack temperature detector is error.
System Impact
Handling Suggestion
1.Check if the pre-set lower limit of the alarm threshold configured in the background for rack
temperature is reasonable.
Y->Go to "2".
N->Modify the alarm threshold and synchronize it to the foreground. Check if the alarm is eliminated:
if so, end. If not, go to "2".
2.Increase the temperature of the rack and check if the alarm is eliminated.
Y->End.
N->Contact ZTE Corporation.
2-188

Chapter 2 Alarm
2.1.336 199025858 Room temperature is higher than high threshold

Alarm Property
l Description: Room temperature is higher than high threshold
l Severity: Minor
Probable Cause
The temperature in the equipment room exceeds the upper limit of the alarm threshold
System Impact
Handling Suggestion
1.Check the high threshold of equipment room temperature on background to see whether it is
rational.
Y->Go to "2".
N->Modify the threshold and upload it to the foreground, and then check whether the alarm
disappears. The handling of this alarm is ended if it disappears, or go to "2" if it does not.
2.Cool the equipment room, and check whether the alarm disappears.
Y->End.
N->Contact ZTE.
2.1.337 199025859 Room temperature is lower than low threshold

Alarm Property
l Description: Room temperature is lower than low threshold
l Severity: Minor
Probable Cause
1.Room temperature value reported now is under the low threshold

2.The setting of the room temperature detector is error.
System Impact
2-189

Handling Suggestion
1.Check the low threshold of equipment room temperature on background to see whether it is rational.
Y->Go to "2".
2.Warm up the equipment room, and check whether the alarm disappears.
Y->End.
N->Contact ZTE.
2.1.338 199025860 Voltage is higher than high threshold

Alarm Property
l Description: Voltage is higher than high threshold
l Severity: Minor
Probable Cause
Voltage of a line exceeds the upper limit of the alarm threshold
System Impact
Handling Suggestion
1.Check the high voltage threshold on background to see whether it is rational.

Y->Go to "2".
2. Lower down the voltage, and check whether the alarm disappears.
Y->End.
N->Contact ZTE.
2.1.339 199025861 Voltage is lower than low threshold

Alarm Property
l Description: Voltage is lower than low threshold
l Severity: Minor
2-190

Chapter 2 Alarm
Probable Cause
1.Voltage value is under the low threshold

2.The setting of the votage detector is error
System Impact
Handling Suggestion
1.Check the low voltage threshold on background to see whether it is rational.

Y->Go to "2".
2.Increase the voltage, and check whether the alarm disappears.
Y->End.
N->Contact ZTE.
2.1.340 199025862 Humidity is higher than high threshold

Alarm Property
l Description: Humidity is higher than high threshold
l Severity: Minor
Probable Cause
The humidity in equipment room exceeds the upper limit of the alarm threshold.
System Impact
2-191

Handling Suggestion
1.Check the high humidity threshold on background to see whether it is rational.

Y->Go to "2".
2.Lower down the humidity, and check whether the alarm disappears.
Y->End.
N->Contact ZTE.
2.1.341 199025863 Humidity is lower than low threshold

Alarm Property
l Description: Humidity is lower than low threshold
l Severity: Minor
Probable Cause
1.Room humidity value is under the low threshold

2.The setting of the room humidity detector is error
System Impact
Handling Suggestion
1.Check the low humidity threshold on background to see whether it is rational.

Y->Go to "2".
2.Increase the humidity, and check whether the alarm disappears.
Y->End.
N->Contact ZTE.
2.1.342 199025864 Fault in fan plug-in box

Alarm Property
l Description: Fault in fan plug-in box
2-192

Chapter 2 Alarm
l Severity: Minor
Probable Cause
1.Fan works in error

2.The setting of the fan detector is error
System Impact
Handling Suggestion
1.Check whether the fan plug-in box and its power line are connected securely (indicators are normal).
Y->go to "2".
N->Secure the fan plug-in box and connect the power line, and then check whether this alarm
2.Replace the fan plug-in box with a good one and check whether the alarm disappears.
Y->End.
N->Contact ZTE.
2.1.343 199025865 Rack door access control alarm

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

2.The setting of the door detector is error
System Impact
2-193

Handling Suggestion
1.Check whether the rack door is closed.

Y->go to "2".
N->Close the rack door, and check whether this alarm disappears. Y->End., N->go to "2".
2.Check whether the rack door access control system is correctly connected.
Y->Contact ZTE.
N->Connect the access control system and close the rack door, and check whether this alarm
disappears. Y->End., N->Contact ZTE.
2.1.344 199025866 Smoke alarm

Alarm Property
l Description: Smoke alarm
l Severity: Minor
Probable Cause
1.Alarm because of fume exceed the high threshold

2.The setting of the fume detector is error
System Impact
Handling Suggestion
1.Check whether there is smoke in the equipment room.

Y->Dispel the smoke, and check whether this alarm disappears. Y->End., N->Contact ZTE.
N->Contact ZTE.
2.1.345 199025867 Infrared alarm

Alarm Property
l Description: Infrared alarm
l Severity: Minor
2-194

Chapter 2 Alarm
Probable Cause
1.The infrared is too strong.

2.The setting of the infrared detector is error.
System Impact
Handling Suggestion
1.Check whether there is any animals or human near the infrared detector.
Y->Make the animal or human away from the detector.
N->go to "2".
2.Check whether the setting of the infrared detector is correct.
Y or do not know how to check ->Contact ZTE.
N->Set the infrared detector, and check whether this alarm disappears. Y->End., N->Contact ZTE.
2.1.346 199025868 Lightning alarm

Alarm Property
l Description: Lightning alarm
l Severity: Minor
Probable Cause
1.Alarm because of thunder

2.The setting of the thunder detector is error
System Impact
Handling Suggestion
1.Check whether there is lightning hazard.

Y->Take protection measures, and check whether this alarm disappears. Y->End., N->Contact ZTE.
N->Contact ZTE.
2-195

2.1.347 199025869 Power switch alarm

Alarm Property
l Description: Power switch alarm
l Severity: Minor
Probable Cause
1.Atmosphere switch is open and configured.

2.The setting of the atmosphere switch detector is error
System Impact
Shelf power supply might be affected.
Handling Suggestion
1.Check if the power switch is closed and check if the ALM indicator light is normal
Y->Go to "2"
N->Close the power switch please Y->The end, N->Go to "2"
2.Check if the power switch signal is shielded by the background
Y->The end
2.1.348 199025870 Power type configured does not accord with

physical
Alarm Property
l Description: Power type configured does not accord with physical
l Severity: Minor
Probable Cause
The power type configured in the database does not accord with the board hardware equipment.
System Impact
The board is faulty.
2-196

Chapter 2 Alarm
Handling Suggestion
1.Check the background configuration according to the additional information of the alarm to see
if the configuration conforms to the board hardware equipment.
Y->If yes, go to "2".
N->If no, modify the configuration according to the hardware equipment and re-power on the board.
The alarm will be eliminated.
2.The database configuration is consistent with the equipment hardware while the alarm still can not
be eliminated. In this case, please contact ZTE Corporation.
2.1.349 199026127 Clock reference source lost (Level 3 alarm)

Alarm Property
l Description: Clock reference source lost (Level 3 alarm)
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. Check the additional information of the alarm, and check if it is needed to input the corresponding
clock reference
Y->If it is needed to input the corresponding clock reference, input the clock reference and check if
the alarm is eliminated. If the alarm is eliminated, end alarm handling. Else, go to "2".
N->If it is not needed to input the corresponding clock reference, delete the clock reference
configuration on NMS configuration management interface, and check if the alarm is eliminated. If the
alarm is eliminated, end alarm handling. Else, go to "5".
2. Check if the clock reference is circuitry distilled clock
Y->If the clock reference is circuitry distilled clock, go to "3".
N->If the clock reference is not circuitry distilled clock, go to "5".
3. Check if the board where the clock reference is distilled has been configured to distill clock
2-197

Y->If the board where the clock reference is distilled has been configured to distill clock, go to "4".
N->If the board where the clock reference is distilled has not been configured to distill clock,
reconfigure and check if the alarm is eliminated. If the alarm is eliminated, end alarm handling.
Else, go to "4".
4. Check if the board where the clock reference is distilled has any alarms
Y->If the board where the clock reference is distilled has alarms, eliminate the alarms according
suggestions, and check if the alarm is eliminated. If the alarm is eliminated, end alarm handling.
Else, go to "5".
N->If the board where the clock reference is distilled has no alarm, go to "5".

Alarm Property
l Severity: Major
Probable Cause
Input clock reference is in unavailable status for more than 10 minutes and less than 24 hours.
System Impact
Handling Suggestion
clock reference
2-198

Chapter 2 Alarm
Else, go to "4".
Else, go to "5".

Alarm Property
Probable Cause
Input clock reference is in unavailable status for more than 24 hours.

System Impact
Handling Suggestion
clock reference
2-199


Else, go to "4".
Else, go to "5".
2.1.352 199026133 Output clock of the board is lost

Alarm Property
l Description: Output clock of the board is lost
l Severity: Major
Probable Cause
Hardware is faulty.
System Impact
The synchronization of system clock will fail and service interruption will occur.
Handling Suggestion
Replace the board.
2.1.353 199029184 SNTP time-synchronization failed

Alarm Property
l Description: SNTP time-synchronization failed
l Severity: Minor
2-200

Chapter 2 Alarm
Probable Cause
1.The source addresses of SNTP client configuration is error.

2.SNTP servers faults.
3.Network communication faults.
System Impact
SNTP doesn't work.
Handling Suggestion
1.Check whether the source addresses of SNTP client configuration is correct.

Y->go to "3".
N->go to "2".
2.Configure the correct source addresses of SNTP client again, then check whether the alarm
is restored.
Y->over.
N->go to "3".
3.Check whether the SNTP server is available.
Y->go to "5".
N->go to "4".
4.Solve SNTP server problem，then check whether the alarm is restored.
Y->over.
N->go to "5".
5.Check whether the link between SNTP servers and client is available.
Y->Contact ZTE.
N->Solve the link problem.
2.1.354 199030721 Temperature is lower than lower-non-critical

threshold.
Alarm Property
l Description: Temperature is lower than lower-non-critical threshold.
l Severity: Warning
Probable Cause
Velocity of fan is larger than normal;Temperature of environment is too low( Not often happen)
2-201

System Impact
Maybe make the velocity of data processing go down
Handling Suggestion
Depressing the velocity of fan;Improving the temperature of environment
2.1.355 199030722 Temperature is lower than lower-critical

threshold.
Alarm Property
l Description: Temperature is lower than lower-critical threshold.
l Severity: Minor
Probable Cause
Velocity of fan is too larger;Temperature of environment is too lower(Not often happen)
System Impact
Maybe make the velocity of processing going down and some data missing
Handling Suggestion
Depressing the velocity of fan;Improving the temperature of environment
2.1.356 199030723 Temperature is lower than lower-non-recoverable

threshold.
Alarm Property
l Description: Temperature is lower than lower-non-recoverable threshold.
l Severity: Major
Probable Cause
Too lower temperature lead to circuit damaged(Not often happen)
2-202

Chapter 2 Alarm
System Impact
Some functions of System maybe lost
Handling Suggestion
Power off right now and repaired it
2.1.357 199030724 Temperature is higher than upper-non-critical

threshold.
Alarm Property
l Description: Temperature is higher than upper-non-critical threshold.
l Severity: Warning
Probable Cause
Velocity of fan is lower than normal;Temperature of environment is too high.(Not often happen)
System Impact
Maybe the velocity of processing will go down
Handling Suggestion
Improving the velocity of fan;Depressing the temperature of

environment
2.1.358 199030725 Temperature is higher than upper-critical

threshold.
Alarm Property
l Description: Temperature is higher than upper-critical threshold.
l Severity: Minor
Probable Cause
Velocity of fan is too low or the temperature of environment is too high(Not often happen)
2-203

System Impact
Maybe the velocity of processing will go down and some data missing.
Handling Suggestion
Improving the velocity of fan;Depressing the temperature of

environment
2.1.359 199030726 Temperature is higher than upper-non-recov

erable threshold.
Alarm Property
l Description: Temperature is higher than upper-non-recoverable threshold.
l Severity: Major
Probable Cause
Too high temperature lead to circuit damaged
System Impact
Handling Suggestion
2.1.360 199030727 Voltage is lower than lower-non-critical

threshold.
Alarm Property
l Description: Voltage is lower than lower-non-critical threshold.
l Severity: Warning
Probable Cause
Power fluctuate
2-204

Chapter 2 Alarm
System Impact
Some system functions maybe lost
Handling Suggestion
Check the power and payload
2.1.361 199030728 Voltage is lower than lower-critical threshold.

Alarm Property
l Description: Voltage is lower than lower-critical threshold.
l Severity: Minor
Probable Cause
Maybe aroused by payload changing
System Impact
Some system functions maybe lost or arouse more serous trouble
Handling Suggestion
Check the payload and power
2.1.362 199030729 Voltage is lower than lower-non-recoverable

threshold.
Alarm Property
l Description: Voltage is lower than lower-non-recoverable threshold.
l Severity: Major
Probable Cause
Resistance invalid;Influenced by environment
2-205

System Impact
Parts of circuit may be damaged
Handling Suggestion
2.1.363 199030730 Voltage is higher than upper-non-critical

threshold.
Alarm Property
l Description: Voltage is higher than upper-non-critical threshold.
l Severity: Warning
Probable Cause
Power fluctuate
System Impact
Handling Suggestion
Check the power and payload situation
2.1.364 199030731 Voltage is higher than upper-critical threshold.

Alarm Property
l Description: Voltage is higher than upper-critical threshold.
l Severity: Minor
Probable Cause
2-206

Chapter 2 Alarm
System Impact
Parts of system functions maybe lost or arouse more serous trouble
Handling Suggestion
Check the payload
2.1.365 199030732 Voltage is higher than upper-non-recoverable

threshold.
Alarm Property
l Description: Voltage is higher than upper-non-recoverable threshold.
l Severity: Major
Probable Cause
System Impact
Handling Suggestion
2.1.366 199030734 Velocity of fan is lower than lower-critical

threshold.
Alarm Property
l Description: Velocity of fan is lower than lower-critical threshold.
l Severity: Major
Probable Cause
Machine malfunction;Voltage abnormal
2-207

System Impact
Will arouse the rising of shelf temperature
Handling Suggestion
Check the fan
2.1.367 199030739 Current is lower than lower-non-critical

threshold.
Alarm Property
l Description: Current is lower than lower-non-critical threshold.
l Severity: Warning
Probable Cause
Power fluctuate
System Impact
Handling Suggestion
Check the power and payload
2.1.368 199030740 Current is lower than lower-critical threshold.

Alarm Property
l Description: Current is lower than lower-critical threshold.
l Severity: Minor
Probable Cause
2-208

Chapter 2 Alarm
System Impact
Some system functions maybe lost or arouse more serous trouble
Handling Suggestion
Check the payload and power
2.1.369 199030741 Current is lower than lower-non-recoverable

threshold.
Alarm Property
l Description: Current is lower than lower-non-recoverable threshold.
l Severity: Major
Probable Cause
System Impact
Handling Suggestion
2.1.370 199030742 Current is higher than upper-non-critical

threshold.
Alarm Property
l Description: Current is higher than upper-non-critical threshold.
l Severity: Warning
Probable Cause
Power fluctuate
2-209

System Impact
Handling Suggestion
Check the power and payload situation
2.1.371 199030743 Current is higher than upper-critical threshold.

Alarm Property
l Description: Current is higher than upper-critical threshold.
l Severity: Minor
Probable Cause
System Impact
Parts of system functions maybe lost or arouse more serous trouble
Handling Suggestion
Check the payload
2.1.372 199030744 Current is higher than upper-non-recoverable

threshold.
Alarm Property
l Description: Current is higher than upper-non-recoverable threshold.
l Severity: Major
Probable Cause
2-210

Chapter 2 Alarm
System Impact
Handling Suggestion
2.1.373 199030745 Velocity of fan is lower than lower-non-critical

threshold.
Alarm Property
l Description: Velocity of fan is lower than lower-non-critical threshold.
l Severity: Minor
Probable Cause
System Impact
Handling Suggestion
Check the fan
2.1.374 199030746 Velocity of fan is lower than lower-non-recov

erable threshold.
Alarm Property
l Description: Velocity of fan is lower than lower-non-recoverable threshold.
l Severity: Major
Probable Cause
2-211

System Impact
Handling Suggestion
Check the fan
2.1.375 199030747 Module/Board Device Absent

Alarm Property
l Description: Module/Board Device Absent
l Severity: Minor
Probable Cause
Module/Board Device Removed / Device Absent
System Impact
Handling Suggestion
Check Module/Board in Add-info
2.1.376 199030748 Power On Failed due to S5

Alarm Property
l Description: Power On Failed due to S5
l Severity: Minor
Probable Cause
Hardware may be abnormal
System Impact
Board can't enter word status.
2-212

Chapter 2 Alarm
Handling Suggestion
Check board
2.1.377 199030808 Processor Internal Error

Alarm Property
l Description: Processor Internal Error
l Severity: Minor
Probable Cause
Processor Internal Error happens.
System Impact
System can not work normally.
Handling Suggestion
Check Board Hardware
2.1.378 199030809 Processor Thermal Trip

Alarm Property
l Description: Processor Thermal Trip
l Severity: Minor
Probable Cause
Processor Thermal Trip。
System Impact
System can not work normally.
Handling Suggestion
Check Board Hardware
2-213

2.1.379 199087340 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
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 EDGB or ESDGB board, then watch whether the alarm could be restored.
2.1.380 199087341 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.
2-214

Chapter 2 Alarm
System Impact
Quality of PS service for Part of user will decline
Handling Suggestion
Increase the BRCH line or BRCH time-slot
2.1.381 199087344 MSC overload control alarm at FUC mode

Alarm Property
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.382 199087345 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
2-215

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.1.383 199087346 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.384 199087347 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.
2-216

Chapter 2 Alarm
System Impact
Handling Suggestion
2.1.385 199087348 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.386 199087349 Signaling point congestion control alarm at SYS

mode
Alarm Property
l Description: Signaling point congestion control alarm at SYS mode
l Severity: Minor
2-217

Probable Cause
The excessive traffic causes the MSC to send signaling congestion message. BSC starts system
message flow control.
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.387 199087350 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-218

Chapter 2 Alarm
2.1.388 199087351 PCCCH overload control

Alarm Property
l Description: PCCCH overload control
l Severity: Minor
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.389 199087352 NSVC is 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.
2-219

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.
The related alarm is as follows:
199087340 FR Device Failure
2. On NMS configuration management interface, check if NSVC configuration parameters are
consistent with those on SGSN.
2.1.390 199087458 PS cell block caused by slave

Alarm Property
l Description: PS cell block caused by slave
l Severity: Minor
Probable Cause
The SLAVE on RUP 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 RUP board through telnet. Input the SCSShowDevStatus() command to check if the
corresponding SLAVE status is running. If not, it indicates that the SLAVE is damaged. In this case,
replace the board.
2.1.391 199087465 NSVC is IP failure alarm

Alarm Property
l Description: NSVC's IP failure alarm
l Severity: Minor
2-220

Chapter 2 Alarm
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.392 199087482 dbsapp data error alarm

Alarm Property
l Description: dbsapp data error alarm
l Severity: Major
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-221

2.1.393 199087505 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.394 199087517 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
2-222

Chapter 2 Alarm
Handling Suggestion
2.1.395 199087518 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
Handling Suggestion
2.1.396 199087768 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.
2-223

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.1.397 199087778 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-224

Chapter 2 Alarm
2.1.398 199087779 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.1.399 199087780 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-225

2.1.400 199087781 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.1.401 199087782 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-226

Chapter 2 Alarm
2.1.402 199087783 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.1.403 199087784 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-227

2.1.404 199087785 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.1.405 199087786 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-228

Chapter 2 Alarm
2.1.406 199087787 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

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


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-230

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-231


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-232

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-233


Alarm Property
l Severity: Major
Probable Cause
System Impact
None
Handling Suggestion
2.1.417 199105029 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.
Handling Suggestion
OMP reports this alarm when being reset and then restores the alarm. No handling operations
are required.
2-234

Chapter 2 Alarm
2.1.418 199393987 Board off line

Alarm Property
l Description: Board off line
l Severity: Major
Probable Cause
1.The board configured in the database is not online.

2. The board lose contact with the CMM of the same shelf.
System Impact
Related services cannot be provided.
Handling Suggestion
1. Check for the proper placing of the board, and insert the board firmly if it is not properly placed.
2. Plug/unplug the board.
4. Change the slot.
5. Replace the CMM of the same shelf.
2.1.419 199419840 PTP failed to get clock attribute

Alarm Property
l Description: PTP failed to get clock attribute
l Severity: Minor
Probable Cause
PTP failed to get clock attribute
System Impact
PTP doesn't work.
2-235

Handling Suggestion
1.Check whether clock board is powered on (indicator RUN is flashing at 1HZ).
Y-> Go to Step "2".
N-> Reset the board to restore the board to normal state, and check whether this alarm disappears:
Y-> End, N-> Go to Step 3.
2.Check the Alarm Management window for the alarm of control plane communication abnormal,
which is 8393985(Control plane communication abnormal between board and its home module).
Y-> Perform the recommended solution to process the alarm, and check whether this alarm
disappears: Y-> End, N-> Go to Step "3".
N-> Go to Step "3".
3.Please contact ZTE.
2.2 Processing alarm

2.2.1 199002560 CPU utilization over alarm limit
Alarm Property
l Description: CPU utilization over alarm limit
l Severity: Major
l Alarm Type: Processing alarm
Probable Cause
CPU utilization over alarm limit
System Impact
System runs slowly so some function may be affected
Handling Suggestion
1. Inquire CPU alarm limit from backstage, judge if CPU alarm limit is too low
Y-> Reset the CPU alarm limit, wait dozens of seconds, check if the alarm is eliminated, if alarm is
restored, end, else go to "2".
N-> Go to "2".
2. Do nothing, wait dozens of seconds for the system recover automatically, check if the alarm is
eliminated
Y-> End.
N-> Go to "3".
3. Check if the business is running busily
Y-> Wait until the business finished, check if the alarm is eliminated, if alarm is restored, end, else
go to "4".
2-236

Chapter 2 Alarm
N-> Go to "4".
4. Please record the alarm information and contact ZTE Corporation
2.2.2 199004357 The system bureau changed

Alarm Property
l Description: The system bureau changed
l Severity: Major
Probable Cause
The configuration of system bureau changed
System Impact
Need restart system to validate the changed bureau configuration
Handling Suggestion
1. Restart the system, wait 30 seconds, check if the alarm is eliminated

Y-> End.
N-> Please record the alarm information and contact ZTE Corporation
2.2.3 199005400 Configuration conflicts between OMP and CMM

Alarm Property
l Description: Configuration conflicts between OMP and CMM
l Severity: Major
Probable Cause
1. The slot is configured to 'OMP'type in CMM, but is not configured to OMP in the database of OMP.
System Impact
OMP can't run normally, so the services in this net element are affected.
2-237

Handling Suggestion
1.Change OMP address on CMM board or OMP board, and reboot board.
2.2.4 199005908 Lack of version

Alarm Property
l Description: Lack of version
l Severity: Minor
Probable Cause
Several version not found in version server.
System Impact
Board work with exception
Handling Suggestion
Get log file, and find out lacked version. Then add and active it.
2.2.5 199005909 Download version failed

Alarm Property
l Description: Download version failed
l Severity: Minor
Probable Cause
Download version from version server failed.
System Impact
Handling Suggestion
Get log file,and find out download failed version. Then check if file exist in version server.
2-238

Chapter 2 Alarm
2.2.6 199005910 Process execute failed

Alarm Property
l Description: Process execute failed
l Severity: Minor
Probable Cause
Several process execute failed.
System Impact
Handling Suggestion
Get log file, and find error code. Then anylize it.
2.2.7 199015362 Fail to process MCS APP Dlib

Alarm Property
l Description: Fail to process MCS APP Dlib
Probable Cause
1.fail to open App Dll;

2.fail to excute app init;
3.customized-thread changed
System Impact
reason 1. 2: board poweroff or reboot; reason 3: board reset, then be normal
2-239

Handling Suggestion
1. Check whether the reason info is 2

Y-> It is normally restarted for the configuration changed
N-> Go to "2"
2.Check whether the reason is 0
Y-> Check whether the DLL was correctly uploaded, Go to "3"
N-> It may be caused by abnormal upper layer service ,Go to "4"
3. make and upload the correct version
4.Make records of the alarm information and contact ZTE Corporation.
2.2.8 199020225 Protocol stack requests for configuration

information timeout
Alarm Property
l Description: Protocol stack requests for configuration information timeout
l Severity: Major
Probable Cause
1. Failed to register on the TCP/IP protocol stack RPU board.

2. Failed to request for database configuration, such as SNTP configuration, DSCP
configuration and UID PPP configuration. Refer to detailed alarm information.
3. Failed to request for interface configuration information, such as Ethernet interface or
ATM interface. Refer to detailed alarm information.
4. Failed to initialize the TCP/IP protocol stack process resource, such as HDLC IC
initialization failure, or memory loss. Refer to detailed alarm information.
System Impact
Some board functions listed in alarm description are unavailable. When "configuration
request type" in additional alarm information is "media panel IP configuration", the media
panel function will be impacted, other reasons will result in an entire unavailable TCP/IP
protocol stack.
2-240

Chapter 2 Alarm
Handling Suggestion
1. Wait for several mins, and check whether the alarm is eliminated.
Y->End
N->2
2. Check whether an alarm ALM-8393985 Communication Exception of
Control panel Between Board and Affiliated Module occurs.
Y->3
N->4
3. Refer to the handling suggestions of ALM-8393985 Communication Exception
of Control panel Between Board and Affiliated Module occurs, and
check whether the alarm is eliminated.
Y->End
N->6
4. Plug this board and reset hardware, and check whether the alarm is eliminated.
Y->End
N->5
5. Replace the faulty board, and check whether the alarm is eliminated.
Y->End
N->6
6. Contact the ZTE office.
2.2.9 199023042 The number of board physical alarms exceeds

the threshold
Alarm Property
l Description: The number of board physical alarms exceeds the threshold
l Severity: Major
Probable Cause
There are too many alarms for this board, and the alarm pool is full of board alarms.
System Impact
Alarm information might be lost. No impact on user service.
Handling Suggestion
Check and delete some temporarily useless virtual configuration resources.
2-241

2.2.10 199025600 Connection check be disabled in board

Alarm Property
l Description: Connection check be disabled in board
l Severity: Warning
Probable Cause
The connection check switch is off, causing PP service process unable to execute connection check.
System Impact
Board connection check disabled, automatic check of connection error cannot be performed. Thus
the connection error might not be self-cured.
Handling Suggestion
Please input "ppenableconncheck" on the board
2.2.11 199029953 Port is in ethernet OAM loopback state

Alarm Property
l Description: Port is in ethernet OAM loopback state
l Severity: Minor
Probable Cause
Local port goes to oam loopback state because remote enable loopback.
System Impact
System service halt
Handling Suggestion
1.Check remote Oam configuratio ，see if remote enable ethernet oam loopback function,if it is
enable,check loopback test is over. Disable remote’s ethernet oam loopback。Observe if alarm
restore.
Yes->alarm restore
No->phone ZTE corporation
2-242

Chapter 2 Alarm
2.2.12 199066013 MTP3 link congestion

Alarm Property
l Description: MTP3 link congestion
l Severity: Major
Probable Cause
1.Heavy traffic.
2.Uneven load among links.
3.Insufficient link resources.
System Impact
Congestion may cause packet loss, call abortion and even link breakdown.
Handling Suggestion
1.Make no manual intervention and wait for automatic system recovery. Check whether this alarm
disappears after 30 seconds.
Y->End.
N->Go to Step 2.
2.Check whether the system is busy with its current services.
Y->Go to Step 3.
N->Go to Step 4.
3.Check whether there are sufficient link resources.
Y->3.1 Query performance statistic data to check whether the load is evenly shared among links.
Y->Go to Step 1.
N->Go to Step 4.
N->3.2 Add new links and check whether this alarm disappears.
Y->End.
N->Go to Step 3.1.
4.Note down detailed information.
4.1 Back up related local office configuration data and peer-end office configuration data.
4.2 Back up related local office and peer-end office history alarms and notifications, as well as
current alarms.
4.3 Contact ZTE Corporation and end the alarm handling procedure.
2-243

2.2.13 199066027 Request time from SNTP server failed

Alarm Property
l Description: Request time from SNTP server failed
l Severity: Major
Probable Cause
Request time from Sntp server failed
System Impact
Can't synchronize time from SNTP server
Handling Suggestion
1. Check if the configuration of SNTP server is correct

Y-> Go to "2" .
N-> Reset SNTP server's configuration, enforce SNTP time synchronization, check if the alarm is
eliminated, if alarm is restored, end, else go to "2".
2.2.14 199066031 The number of OMP alarms exceeds the threshold

Alarm Property
l Description: The number of OMP alarms exceeds the threshold
l Severity: Major
Probable Cause
There are too many alarms for OMP board, and the alarm pool is full of board alarms.
System Impact
Handling Suggestion
2-244

Chapter 2 Alarm
2.2.15 199066032 Time synchronization over alarm limit

Alarm Property
l Description: Time synchronization over alarm limit
l Severity: Major
Probable Cause
The minus of time on OMP and time from Sntp server over alarm limit
System Impact
System time may not be correct
Handling Suggestion
1. Inquire time difference alarm limit from backstage, judge if time difference alarm limit is too low
Y-> Reset the time difference alarm limit, wait dozens of seconds, check if the alarm is eliminated, if
alarm is restored, end, else go to "2".
N-> Go to "2".
2. check time on SNTP server and the system time, judge which time is more accurater
Time on SNTP server-> Enforce SNTP time synchronization from SNTP server, wait dozens of
seconds, check if the alarm is eliminated, if alarm is restored, end, else go to "3".
System time-> Check SNTP server organization, find out the reason of the inaccurate time, if cannot
solve, go to "3".
2.2.16 199066063 MTP3 link sending flow control alarm

Alarm Property
l Description: MTP3 link sending flow control alarm
l Severity: Major
Probable Cause
The sending payload of MTP3 link exceeds the threshold set by sending flow control.
System Impact
Packet loss and call abortion.
2-245

Handling Suggestion
1.Make no manual intervention and just wait the system to recover. Check whether this alarm
disappears 30 seconds later.
Y->End.
N->Go to "2".
2.Check whether the system has a heavy traffic.
Y->Go to "3".
N->Go to "4".
Y->3.1 Query performance statistic data to check whether load are evenly shared among links.
Y->Go to "1"
N->Go to "4"
Y->End.
N->Go to "3.1"
current alarms.
2.2.17 199087773 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-246

Chapter 2 Alarm
2.2.18 199087774 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.2.19 199392708 Time synchronization over alarm limit in RPU

accesstype
Alarm Property
l Description: Time synchronization over alarm limit in RPU accesstype
l Severity: Major
Probable Cause
The minus of time on OMP and time from SNTP server over alarm limit
System Impact
System time may not be correct
2-247

Handling Suggestion
1. Inquire time difference alarm limit from backstage, judge if time difference alarm limit is too low
Y-> Reset the time difference alarm limit, wait dozens of seconds, check if the alarm is eliminated, if
alarm is restored, end, else go to "2".
N-> Go to "2".
2. check time on SNTP server and the system time, judge which time is more accurater
Time on SNTP server-> Enforce SNTP time synchronization from SNTP server, wait dozens of
seconds, check if the alarm is eliminated, if alarm is restored, end, else go to "3".
System time-> Check SNTP server organization, find out the reason of the inaccurate time, if cannot
solve, go to "3".
2.2.20 199411651 The number of board logical alarms exceeds the

threshold
Alarm Property
l Description: The number of board logical alarms exceeds the threshold
l Severity: Major
Probable Cause
There are too many alarms for this board, and the alarm pool is full of board alarms.
System Impact
Handling Suggestion
2.3 Communications Alarm

2.3.1 198087101 HW link broken
Alarm Property
l Description: HW link broken
2-248

Chapter 2 Alarm
l Severity: Minor
l Alarm Type: Communications Alarm
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.3.2 199003841 The control plane retransfer ratio over the

threshold
Alarm Property
l Description: The control plane retransfer ratio over the threshold
l Severity: Minor
Probable Cause
1.There are some badly-touched boards in the system environment and the retransfer-ratio of control
plane increases.
2.The ethernet communication equipment is abnormal on board or switch board.
3.The node address of TIPC conflicts.
System Impact
The message is delayed on control plane between boards.
2-249

Handling Suggestion
1. Reset the board.

2. Reset the control plane switch board of the same shelf.
4. Change the slot.
5. Check whether other board run abnormally, if it is abnormal, please resolve fault board due to
fault alarm.
2.3.3 199005382 Environment monitor board communication is

abnormal
Alarm Property
l Description: Environment monitor board communication is abnormal
l Severity: Major
Probable Cause
1. The environment board is not connected to the switch board or the connection is wrong.
2. The environment board locates in a rack. The configured rack number is different from that where
DIP switch of the environment board locates.
System Impact
There is no impact on services. However, the system can not monitor the status of power supply
and environment situation.
Handling Suggestion
1. Reconnect the RS485 cable between the environment monitor board and switch board.
2. Modify the rack number configured for the environment monitor board to consistent with the rack
number switch set for the environment monitor board.
2.3.4 199005396 Packet test of internal media plane is abnormal

Alarm Property
l Description: Packet test of internal media plane is abnormal
l Severity: Major
2-250

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

2. The switch chip on media switch board provides a port, which is connected to the board. This
port has a fault.
3. Backplane wiring abnormal, which connects the slot to media switch board.
4. The CPU on the board, or media switch board of the same shelf, is overloaded.
5. Traffic exceeds the processing payload of the board.
System Impact
Media stream can not be transfored normally.
Handling Suggestion
1. Check the alarm management window for the CPU overloaded on the switch board at the shelf, or
local board. Perform recommended solution to process the alarm(s) if any.
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.
4. Change the slot of the board.
5. Replace the switch board in the same shelf.
2.3.5 199005397 Communication of RAW MAC channel is abnormal

Alarm Property
l Description: Communication of RAW MAC channel is abnormal
l Severity: Major
Probable Cause
1. The service media stream exceeds the payload.

2. The board hardware is faulty.
System Impact
The channel between media and control plane is abnormal, and it maybe cause the service quality
decline or the service may be wholly interrupted.
2-251

Handling Suggestion
1. Reset the board.

3. Change the slot.
2.3.6 199005406 Sub-unit state is abnormal

Alarm Property
l Description: Sub-unit state is abnormal
l Severity: Major
Probable Cause
1.The process which reports sub-unit state is abnormal.

2.The device that is associated with sub-unit is abnormal.
System Impact
Some resource in system is blocked and is unavailable, the services carried by the board are affected.
Handling Suggestion
1. Reset the board.

3. Change the slot.
2.3.7 199019971 Request gate info timeout

Alarm Property
l Description: Request gate info timeout
l Severity: Minor
Probable Cause
Request gate info from scs timeout
2-252

Chapter 2 Alarm
System Impact
Can't create L3fwdTbl
Handling Suggestion
Y->End.
N->Contact ZTE Corporation
2.3.8 199025631 LVDS link error

Alarm Property
l Description: LVDS link error
l Severity: Major
Probable Cause
1.The NE clock is abnormal.

2.The TDM connection chip is abnormal.
3.The board hardware has faults.
4.The back board hardware has faults.
System Impact
CS domain service might be down.
Handling Suggestion
1. Check the local board for the Related Alarms. Perform the recommended solution to process
the possible alarms.
Related Alarms:
1286 Loss of clock when input to board
5646 Phase-lock loop unlock
2. Check the clock board for the Related Alarms. Perform the recommended solution to process
the possible alarms.
Related Alarms:
26133 Output clock lost
26129 Clock reference source lost (Level 1 alarm)
2-253

3. Open the Configuration Management window and check whether the EMSI has configured APS
while the active/standby board is configure.
5. Replace the slot.
6. Replace the ETAS in the same shelf.
2.3.9 199025871 Communication abnormal between the shelf

management board and switch board in the same shelf
Alarm Property
l Description: Communication abnormal between the shelf management board and
switch board in the same shelf
l Severity: Major
Probable Cause
1. The connection is wrong between the shelf management board and switch board in the same shelf.
2. The 485 communication is wrong between switch board and the rack configuration of the
environmental monitoring board.
System Impact
Board operaton might be abnormal.It has no impact to the services.
Handling Suggestion
1. Check if switch board is in place.

2. Make sure the RS485 cable between the rack configuration of environmental monitor board
and switch board.
2.3.10 199029952 Ethernet link fault alarm

Alarm Property
l Description: Ethernet link fault alarm
l Severity: Minor
2-254

Chapter 2 Alarm
Probable Cause
A critical event has occurred.An unrecoverable local failure condition has occurred.Local device's
receive pash has detected a fault.
System Impact
Lost of system service
Handling Suggestion
1. Check the fiber Rx if connetivity is good or electric cable is loose。Put out the fiber or cable and
put in it。Observe if the alarm restore.
Yes-> alarm restore
No-> jump“2”\
2. Check peer device’s ethernet OAM function is enable。If it is disable，make peer device enable
ethernet OAM function. Observe if the alarm restore.
Yes->alarm restore
No->jump“3”
3. Replace the cable to peer port on the same device。Insure peer move the other port on the device.
Yes-> alarm restor
No->phone ZTE corporation
2.3.11 199030208 Connectivity fault alarm

Alarm Property
l Description: Connectivity fault alarm
l Severity: Minor
Probable Cause
Connetivty fault management is in fault
System Impact
service may lost partly.
2-255

Handling Suggestion
1. Observe the additional information of the alarm.There are five kinds of additional informations.
(1) receive remote rx fault indication signal,jump to "2"
(2) receive server layer's alarm indication signal,jump to "3"
(3) lost continuity from the remote MEP,jump to "4"
(4) recevie incorrect CCM frame,jump to "5"
(5) receive a CCM frame from other MD,jump to "6"
(6) receive server layer's lock signal,jump to "7"
2. Check if remote Mep's(Maintanence end point)"rx is unidirection. Check rx's link state, for
example,rx's fiber is loose.If rx's fiber is loose,then put in it.Sure the devices between localc and
remote mep if good and their port is up.Observer if alarm restore.
Yes->alarm restore,alarm process end.
No->jump to "8"
3. Check the link work state between the server layer's MEP. Sure the port of intermediate devices
is up. If some links of intermediate server layer's devices if fault.Restore the fault links(replace the
cable or put out and put in the port).Observe if the alarm restore.
Yes->alarm restore, alarm process end.
No->jump to "8"
4. Check network path matter between two MEP. Check if link ports of intermediate devices are up. If
intermediate server layer's network have fault link between MEP. Restore fault links(replace cable
or put up and put in port).Check local and remote MEP's bind port's packet statics can increase.
Observe if alarm can restore.
No->jump to "8"
5. Check the whole network plane of Ethernet OAM(IEEE 802.1ag)administration. You inspect the
device's VLAN,MD,MA configuration. Check the remote MEP configuration belong to local MEP.
Check if it has incorrect configuration, CCM send interval is different from local CCM send interval, or
local MEP's MAC is different from remote MAC.Amend it to same. Observe if the alarm can restore.
No->jump to "8"
6. Check the whole network plane of Ethernet OAM(IEEE 802.1ag)administration. You inspect the
device's VLAN,MD,MA configuration. Check the edge MEPs of the whole MD domain is are full close
in. Check if there are packets from other MD domains. Observe if the alarm can restore.
No->jump to "8"
7. Check the 802.1ag configuration of the server layer's from which our device receive lock
signal.Check if the server layer's MEPs are doing administrator lock. If it is in administrator lock
state,then turn off it.Observe if the alarm restore.
No->jump to "8"
8. We suggest that you adopt expert's advice to eliminate the alarm.
Yes->alarm restore, then phone ZTE to analyse the network.
No->phone ZTE.
2-256

Chapter 2 Alarm
2.3.12 199066003 Control plane communication abnormal between

board and its home module
Alarm Property
l Description: Control plane communication abnormal between board and its home
module
l Severity: Major
Probable Cause
1. The board is offline.

2. The inserted is different from configuration.
3. The board is abnormal.
4. The control plane communication is abnormal.
5. The board is resetting.
System Impact
The board is blocked so that the services carried by the board are interrupted.
Handling Suggestion
1. Check whether the board is online. If not, insert the board.

2. Check whether the inserted board is the same as the configured board. If not, insert a correct
board.
3. Reset the board. Wait for the board to be powered on.
6. Replace the control plane switch board of the same shelf.
2.3.13 199066005 SCCP subsystem unavailable

Alarm Property
l Description: SCCP subsystem unavailable
l Severity: Minor
2-257

Probable Cause
1.The remote signaling point subsystem has exit services.

2.The remote signaling point is inaccessible.
3.The remote office has deleted the SSN configuration, and the local end reports alarms.
4.This SSN is not configured in the remote office, but the SSN of the remote office is configured at the
local end, causing SST test failure.
System Impact
The corresponding subsystem cannot receive or send messages.
Handling Suggestion
1.Check through Alarm Management whether there is any alarm prompting that the adjacent office
is inaccessible.
Y->Perform further handling according to the office inaccessible alarms if there are MTP3 office
inaccessible alarms or M3UA office inaccessible alarms.
N->Go to Step 2.
2.Check the local data configuration to see whether the subsystem is correctly configured in the local
office configuration and adjacent office configuration.
Y->Go to Step 3.
N->Configure the subsystem.
2.1 Check whether this alarm disappears after configuring the subsystem.
Y->End.
N->Go to Step 3.
3.Check the peer-end data configuration to see whether the subsysem is correctly configured in its
local office configuration and adjacent office configuration.
Y->Go to Step 4.
N->Ask the peer end to configure the subsystem.
3.1 Check whether this alarm disappears after the peer end has configured the subsystem.
Y->End.
N->Go to Step 4.
current alarms.
2.3.14 199066008 MTP2 link sending overload

Alarm Property
l Description: MTP2 link sending overload
2-258

Chapter 2 Alarm
l Severity: Major
Probable Cause
1.Heavy traffic on the local end.

System Impact
Overload renders the signaling link is unstable.
Handling Suggestion
Y->End.
N->Go to Step 2.
Y->Go to Step 3.
N->Go to Step 4.
Y->3.1 Query performance statistics data to check whether the load is evenly shared among links.
Y->Go to Step 1.
N->Go to Step 4.
Y->End.
N->Go to Step 3.1.
current alarms.
2.3.15 199066009 MTP2 link reception overload

Alarm Property
l Description: MTP2 link reception overload
l Severity: Major
2-259

Probable Cause
1.Heavy traffic at peer end.

System Impact
Overload renders the signaling link is unstable.
Handling Suggestion
Y->End.
N->Go to Step 2.
Y->Go to Step 3.
N->Go to Step 4.
Y->3.1 Query performance statistics data to check whether the load is evenly shared among links.
Y->Go to Step 1.
N->Go to Step 4.
Y->End.
N->Go to Step 3.1.
current alarms.
2.3.16 199066010 MTP3 office inaccessible

Alarm Property
l Description: MTP3 office inaccessible
l Severity: Major
Probable Cause
1.Office and route configuration error.

2.Link broken.
2-260

Chapter 2 Alarm
System Impact
The corresponding office cannot receive or send messages.
Handling Suggestion
1.Check whether the static route settings of the destination office are correct.
Y->Go to Step 2.
N->Configure or modify the related static route.
1.1 Check whether the office is accessible (this alarm disappears).
Y->End
N->Go to Step 2.
2.Query link status in the route table through Dynamic Management on the background to check
whether there are links available.
Y->Go to Step 4.
N->Go to Step 3.
3.Check alarms on the background to see whether there are alarms prompting that no link is available.
Y->Perform further handling according to the alarms prompting no link available.
N->Go to Step 4.
current alarms.
2.3.17 199066011 MTP3 link unavailable

Alarm Property
l Description: MTP3 link unavailable
l Severity: Minor
Probable Cause
1.The link is physically broken.

2.Link test failed.
3.SMP board or the board where the signalling links are configured restarted.
System Impact
This alarm may render some offices inaccessible, or may result in the congestion of other links.
2-261

Handling Suggestion
1.Check whether there is new data configuration or the configuration has been changed.
Y->1.1 Check link configuration data, especially signaling point code (SPC), SLC and network type
(international or domestic) to see whether they accord with the peer end of the link.
Y->Go to Step 2.
N->Modify the configuration and go to Step 1.2.
1.2 Check whether this alarm disappears after modifying the configuration.
Y->End
N->Go to Step 2.
N->Go to Step 2.
2.Check whether there is any alarm for bottom layer transmission if the link configuration has not
been changed.
Y->Ask a transmission engineer to handle the problem.
N->Go to Step 3.
3.Perform physical link self-loop on the devices at the both ends of the link, and check whether
this alarm disappears.
Y->Check the bottom layer transmission and ask a transmission engineer to solve the problem.
N->Go to Step 4.
current alarms.
2.3.18 199066012 MTP3 cluster inaccessible

Alarm Property
l Description: MTP3 cluster inaccessible
l Severity: Major
Probable Cause
1.Incorrect cluster and route configuration.

2.Link broken.
System Impact
The corresponding cluster cannot receive or send messages.
2-262

Chapter 2 Alarm
Handling Suggestion
1.Check whether the static route configuration of the destination cluster is correct.
Y->Go to Step 2 if the static route configuration of the destination cluster is correct.
N->Configure or modify related static route.
1.1 Check whether the cluster is accessible.
Y->End
N->Go to Step 2.
2.Query link status in the route table through Dynamic Management on the background to check
whether there are links available.
Y->Go to Step 4.
N->Go to Step 3.
3.Check alarms on the background to see whether there are alarms prompting no link available.
Y->Perform further handling according to the alarms prompting no link available.
N->Go to Step 4.
current alarms.
2.3.19 199066014 M3UA office inaccessible

Alarm Property
l Description: M3UA office inaccessible
l Severity: Major
Probable Cause
1. Association link is broken or application server (AS) is not in serving status.

2. Receive DUNA from peer office.
System Impact
Reception and sending of messages from/to the relevant office fail. Access of new service under this
office fails, and abnormal release of the ongoing service occurs.
2-263

Handling Suggestion
1.Check if there is SIO location records of the corresponding users.

2.After the corresponding SIO location has been configured, check if the corresponding AS is
activated.
3.Deactivate and activate the corresponding association. Check if the alarm is eliminated.
2.3.20 199066019 Broken Association

Alarm Property
l Description: Broken Association
l Severity: Major
Probable Cause
1. The association is manually release.

2. All the channels configured by this association are disconnected, or max. resending
times of this association exceeds Association.Max.Retrans.
3. Other association disconnection causes except for the association deletion (See the
additional alarm information)
System Impact
Association interruption, data cannot be transmited, upper layer services will be impacted,
for example, signaling office is unreachable and other available association of an identical office
is blocked.
Handling Suggestion
1. Query association configuration by SHOW SCTP based on association number in

additional information, check whether local/remote port IDs, destination IP, active local
IP are set properly. You should set local association a to local IP a. a. a. a, local port
to Port A, remote IP to b. b. b. b, remote port to Port B, remote association b to local
IP b. b. b. b, local port to Port B, remote IP to a. a. a. a, and remote port to Port A.
Y->3
N->2
2. Modify association by SET SCTP, and check whether the alarm is eliminated.
Y->End
N->3
3. Check whether alarm cause is "receive shutdown request" based on alarm reasons in
additional information.
Y->4
2-264

Chapter 2 Alarm
N->6
4. The association is blocked manually, check whether required to block the association
manually.
Y->End
N->5
5. Activate corresponding association by dynamic management tool, and check whether
Y->End
N->6
2.3.21 199066026 Association Channel Broken

Alarm Property
l Description: Association Channel Broken
l Severity: Major
Probable Cause
1. Hardware fault, for example, external interfaces of local/remote devices are broken,
the intermediate switch device is broken, or the transmission channel is interrupted.
2. Bear network communication fault, for example, external interfaces of local/remote
devices are broken, the intermediate switch device is broken or the bear link is
interrupted.
3. Configuration fault, for example, routes or interface addresses of local/remote devices
change.
4. Device fault, for example, NE control panel channels of local or remote device are
interrupted.
System Impact
This channel is unavailable, all channel interruption will result in association interruption.SCTP will
shift transmission to another channel without impact on signaling transmission and service.
2-265

Handling Suggestion
1. Enter the protocol mode by IPSTACK, and check whether the physical link lost lots of
packages by PING and exit this mode by EXIT MODE.
Y->2
N->3
2. Troubleshooting the physical links, and check whether the alarm is eliminated.
Y->End
N->3
3. In the NM alarm management window, check whether the ALM-8393985 Abnormal
Control Plane Communication Between Board and Home ModuleALM-8393988
Abnormal Control Plane Communication Between Module and OMP alarms are
reported on the home module.
Y->5
N->4
4. Handle the fault according to related suggestions, and check whether the alarm is
eliminated.
Y->End
N->5
5. Check whether the remote device of the association is faulty, troubleshoot the remote
faults, and check whether the alarm is eliminated.
Y->End
N->6
2.3.22 199087336 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-266

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 OMP and EGPB 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.3.23 199087337 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-267

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 OMP and EGPB 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.3.24 199087342 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-268

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.
The related alarm is as follows:
199087337 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.3.25 199087380 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-269

2.3.26 199087381 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.3.27 199087468 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-270

Chapter 2 Alarm
2.3.28 199087775 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.3.29 199105035 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 self.
2.LogService programme does not work.
3.LogService board does not work.
System Impact
The network communication link between Logservice and OMP is broken，Log data can not been
sent to LogService
2-271

Handling Suggestion
1.Check the LogService board is on the shelf.

2.Check the LogService programme run status.
3.Replace the LogService board;
2.3.30 199393986 Control plane communication is abnormal

between this board and the active independent board
Alarm Property
l Description: Control plane communication is abnormal between this board and the
active independent board
l Severity: Major
Probable Cause
1.Boards are configured backup mode, but the slave board is offline.
2.The slave board is online, but the communication link between master and slave independent
boards is abnormal.
System Impact
The master board and the slave board can't communicate. When the master board works abnormally,
change over won't happen. It has no impact to the services.
Handling Suggestion
1. Make sure the board is configured backup mode, and the master and slave boards are firmly online.
2. Check the opposite board for the related alarms. If there are related alarms, perform the
recommended solution to process the possible alarms.
3. Replace the opposite board.
4. Change the slots of both the master and slave boards.
2.3.31 199393988 Control plane communication abnormal between

MP and OMP
Alarm Property
l Description: Control plane communication abnormal between MP and OMP
l Severity: Major
2-272

Chapter 2 Alarm
Probable Cause
1. The board is not online.

2. The board is blocked.
3. The inserted board is different from the configured.
4. The board is abnormal.
5. The control plane communication is abnormal.
6. The board is resetting.
7. The module has been powered off, and the service on this board will be failed or switch over
other module.
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 whether the board is online. If not, insert the board.

2. Check whether the inserted board is the same as the configured board. If not, insert a correct
board.
3. Reset the board and wait power on.
6. Replace the control plane switch board of the same shelf.
2.3.32 199407043 PPP Link Broken

Alarm Property
l Description: PPP Link Broken
l Severity: Major
2-273

Probable Cause
1. EPU Create HDLC channel failed.

2. Physical link is broken, or the transmission quality of link is poor.
3. PPP port is creating or modifying by user.
4. Master board power on, or slave board became to master.
5. Users modify its' parameter of PPP link or peer's.
6. The other side of link is re-negotiation.
7. Two sides of link is inconsistent
System Impact
This will cause disconnection of user plane data and services.
Handling Suggestion
1Is there a alarminfo called "18501 EPU create HDLC channel failed"
Y->go to "2"
N->go to "7"
2.Observe the alarm information for a few minutes, check whether the alarm will be restored.
Y->alarm can be restored, end(link broken reason may be 2,3,4,5,6)
N->go to "3"
3.Check cable connection at both ends. If the cable is disconnected or connection is loose
Y-> unplug and plug the cable or replace the cable,if the alarm is restored after operation,end(link
broken reason:2) ,otherwise, go to "4".
N->go to "4"
4.Refer to user's networking plan to see if E1 cable connection is correct
Y-> connection refer to user's networking.if the alarm is restored after operation,end(link broken
reason:2) ,otherwise, go to "5".
N->go to "5"
5.On NMS configuration management interface (IPOverE1 configuration), check whether Interface E1
No. and time slot configuration of two sides is accord
Y-> modify congiguration,Ensure that the relevant configuration is consistent at both ends.if the alarm
is restored after operation,end(link broken reason:7) ,otherwise, go to "6".
N->go to "6"
6.On NMS configuration management interface, check whether configuration of relay board and
interface board connection is accord.
Y-> modify congiguration,Ensure the connection continuity of PPP port at both ends.if the alarm is
restored after operation,end(link broken reason:7) ,otherwise, go to "10".
N->go to "10"
7.Check if EPU board property is T1.
Y->go to "8"
N->go to "9"
8.Check if the timeslot of port is excess No.24
Y->modify the configuration,make sure timeslot is not overrun No.24,end(link broken reason:1)
,otherwise, go to "9".
2-274

Chapter 2 Alarm
N->go to "9"
9.Check if the E1 Num is excess max num.
Y->modify the E1 num,,end(link broken reason:1) ,otherwise, go to "10".
N->go to "10"
10.Contact ZTE corporation,use expert advice
2.3.33 199407298 BSCIP configuration error in database

Alarm Property
l Description: BSCIP configuration error in database
l Severity: Warning
Probable Cause
1.BSCIP is not configured.

2.Illegal BSCIP configuration, for example, all 0s or 1s.
System Impact
ABPM cannot locate other problems with the self-loop method.
Handling Suggestion
1.Check whether the BSCIP configuration is correct.

Y->Go to "2".
N->Modify the configuration, and go to "2" if this alarm still exists.
2.Check whether the internal link between OMP and ABPM is normal.
Y->Go to "3".
N->Check alarms for related internal c
2.3.34 199411392 BFD Session Interruption

Alarm Property
l Description: BFD Session Interruption
l Severity: Minor
2-275

Probable Cause
1. The physical link of the BFD link is faulty.

2. The physical link of the BFD link is faulty.
3. The physical link of the BFD link loses packages or is blocked.
4. The opposite BFD session is removed.
5. The software of the BFD session is faulty.
6. Related BFD configuration is modified.
System Impact
BFD is used to test the accessibility to the opposite device and link quality. BFD interruption means
the link to the opposite device is disconnected, and all static routes which treat this opposite device
as the new-hop path will be disconnected or switched. If there is a standby path, then the system
will change over to this path, if not, the services are unavailable.
Handling Suggestion
1. Abundant data caused by the burst traffic or some configurations will result in BFD
disconnection in a flash, observe this alarm information for a while, and check whether
Y->End
N->2
2. Check the indicators of the BFD session source address interface and destination
interface are on normally.
Y->4
N->3
3. Replace the network cables, or re-insert the link cables of the BFD session, wait for
30 secs, re-check the indicators of the BFD session source address interface and
destination interface, and check whether the alarm is eliminated.
Y->End
N->4
4. Through the diagnostic test(other methods of IP path detection, such as PING), check network
connection between BFD source address and destination address.
Y->6
N->5
5. Troubleshoot the network connection and check whether the alarm is eliminated.
Y->End
N->6
2-276

Chapter 2 Alarm
2.3.35 199411393 BFD Session Negotiation Failure

Alarm Property
l Description: BFD Session Negotiation Failure
l Severity: Minor
Probable Cause
1. You have not configured BFD session on the opposite end.

2. Related BFD configurations are inaccurate.
3. The physical link of the BFD session is faulty.
4. The device interface of the BFD is faulty.
5. The physical link of the BFD link loses packages or is blocked.
6. The software of the BFD session is faulty.
System Impact
All services on the path related to the BFD session will be switched to the slave path. Service
interruption will occur if slave path does not exist.
Handling Suggestion
1. Time different of both parties may result in unsuccessful BFD negotiation, observe
alarm information for a while, and check whether the alarm is eliminated.
Y->End
N->2
2. Check the indicators of the BFD session source address interface and destination
interface are on normally.
Y->4
N->3
3. Replace the network cables, or re-insert the link cables of the BFD session, wait for
30 secs, re-check the indicators of the BFD session source address interface and
Y->End
N->4
connection between BFD source address and destination address.
Y->6
N->5
Y->End
N->6
2-277

2.3.36 199419073 Bearer network is unavailable

Alarm Property
l Description: Bearer network is unavailable
l Severity: Major
Probable Cause
1. The intermediate device drop packets which possibly causes the bearer network to be unavailable.
2. Some section of both sides environment's drop packets which also possibly cause the bearer
network to be unavailable.
System Impact
Seriously affect the service on the bearer network
Handling Suggestion
1 Ping the address each other to sure if the link is break or loss packet badly
Y - >Goto 2.1
N - > please contact zte, End the alarm handling.
2 Use the PD trace function to detect through the Web Master:
2.1 Check the every part coording to each nexthop
2.1.1 the link between mp and interface board is broken,Goto 2.2
2.1.2 the link between interface board and intermediate equipment is broken, Goto 2.4
2.1.3 the link between intermediate equipment and other intermediate equipmentis broken, Goto 2.4
2.2 check to see if the routing configuration with wrong
Y - > Check to see if the route configuration is wrong
Y - > Change route configuration ,Goto 2.1.1
N - > Goto 2.3
2.2.1 This part is ok?
Y - > make sure the alarm is eliminated or not,goto 2.2.2
N - > Goto 2.3
2.2.2 Check if the alarm is eliminated
Y - > End the alarm handling.
N - > Goto 2.3
2.3 Check The port of interface board is down or not
Y - > Replace the cable,Goto 2.3.1
2.3.1 Check port of interface board again
Y - > Check if the alarm is eliminated ,goto 2.3.2
2-278

Chapter 2 Alarm

N - > Goto 2.4
2.4 Check intermediate equipment, such as eht configuration of switch to find if it has errors
Y - > Change configuration, Goto 2.4.1
N - > Goto 2.4.2
N - > Goto 2.4.2
2.4.2 Replace the intermediate equipment,goto 2.4.3
N - > Please contact zte
2.3.37 199419074 Bearer network get worse

Alarm Property
l Description: Bearer network get worse
l Severity: Minor
Probable Cause
1. The intermediate device drop packets which possibly causes the bearer network worst.
2. Some section of both sides environment's drop packets which also possibly cause the bearer
network worst.
System Impact
Possible to affect the service on the bearer network.
Handling Suggestion
1 Ping the address each other to sure if the link is break or loss packet badly
Y - >Goto 2.1
2 Use the PD trace function to detect through the Web Master:
2.1 Check the every part coording to each nexthop
2.1.1 the link between mp and interface board is broken,Goto 2.2
2.1.2 the link between interface board and intermediate equipment is broken, Goto 2.4
2.1.3 the link between intermediate equipment and other intermediate equipmentis broken, Goto 2.4
2.2 check to see if the routing configuration with wrong
Y - > Check to see if the route configuration is wrong
Y - > Change route configuration ,Goto 2.1.1
2-279

N - > Goto 2.3

N - > Goto 2.3
N - > Goto 2.3
2.3 Check The port of interface board is down or not
Y - > Replace the cable,Goto 2.3.1
2.3.1 Check port of interface board again
Y - > Check if the alarm is eliminated ,goto 2.3.2
N - > Goto 2.4
2.4 Check intermediate equipment, such as eht configuration of switch to find if it has errors
Y - > Change configuration, Goto 2.4.1
N - > Goto 2.4.2
N - > Goto 2.4.2
2.4.2 Replace the intermediate equipment,goto 2.4.3
N - > Please contact zte
2.3.38 199420352 IPD Session Interruption

Alarm Property
l Description: IPD Session Interruption
l Severity: Minor
Probable Cause
1. The physical link of the IPD link is faulty.

2. The device interface link of the IPD link is faulty.
3. The link of the IPD session is blocked or losing packages.
4. The software of the IPD session is faulty.
5. Related configuration of the IPD session is modified.
2-280

Chapter 2 Alarm
System Impact
IPD is used to test the accessibility to the opposite device and link quality. IPD interruption means
the link to the opposite device is disconnected, and all static routes which treat this opposite device
as the new-hop path will be disconnected or switched. If there is a standby path, then the system
will change over to this path, if not, the services are unavailable.
Handling Suggestion
1. Abundant data caused by the burst traffic or some configurations will result in IPD
disconnection in a flash, observe this alarm information for a period of time, and check whether
Y->End
N->2
2. Check the indicators of the IPD session source address interface and destination
interface are normal.
Y->4
N->3
3. Replace the network cables, or re-insert the link cables of the IPD session, wait for
30 seconds, re-check the indicators of the IPD session source address interface and
Y->End
N->4
connection between IPD source address and destination address.
Y->6
N->5
Y->End
N->6
2.4 Environment Alarm

2.4.1 199030749 Difference between ambient and outlet sensor
exceeded limit .
Alarm Property
l Description: Difference between ambient and outlet sensor exceeded limit .
l Severity: Minor
l Alarm Type: Environment Alarm
2-281

Probable Cause
Shelf envirotment temperature changed;Fantray may be abnormal.
System Impact
A hidden danger occurs.
Handling Suggestion
check shelf condition; check fantrays.
2.5 Qos Alarm

2.5.1 199066018 Association congested
Alarm Property
l Description: Association congested
l Severity: Minor
l Alarm Type: Qos Alarm
Probable Cause
1.Heavy traffic
2.Uneven load among associations
3.Insufficient association resources
System Impact
Transmission delay, or even packet loss will occur. If congestion is not serious, service will not be
affected. Otherwise, call loss might occur, and access success rate of PS service might 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-282

Chapter 2 Alarm
2.5.2 199087506 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.5.3 199087507 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-283

2.5.4 199087758 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.5.5 199087759 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

SJ-20121227135800-023-ZXUR 9000 GSM (V6.50.102) Alarm Handling Reference

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SJ-20121227135800-023-ZXUR 9000 GSM (V6.50.102) Alarm Handling Reference

Uploaded by

Copyright:

Available Formats

ZXUR 9000 GSM

Base Station Controller

Revision No. Revision Date Revision Reason

R1.0 2013–01–14 First edition

Serial Number: SJ-20121227135800-023

Publishing Date: 2013-01-14（R1.0）

SJ-20121227135800-023|2013-01-14（R1.0） ZTE Proprietary and Confidential

Chapter 2 Alarm.......................................................................................... 2-1

SJ-20121227135800-023|2013-01-14（R1.0） ZTE Proprietary and Confidential

SJ-20121227135800-023|2013-01-14（R1.0） ZTE Proprietary and Confidential

SJ-20121227135800-023|2013-01-14（R1.0） ZTE Proprietary and Confidential

SJ-20121227135800-023|2013-01-14（R1.0） ZTE Proprietary and Confidential

SJ-20121227135800-023|2013-01-14（R1.0） ZTE Proprietary and Confidential

SJ-20121227135800-023|2013-01-14（R1.0） ZTE Proprietary and Confidential

SJ-20121227135800-023|2013-01-14（R1.0） ZTE Proprietary and Confidential

SJ-20121227135800-023|2013-01-14（R1.0） ZTE Proprietary and Confidential

SJ-20121227135800-023|2013-01-14（R1.0） ZTE Proprietary and Confidential

SJ-20121227135800-023|2013-01-14（R1.0） ZTE Proprietary and Confidential

SJ-20121227135800-023|2013-01-14（R1.0） ZTE Proprietary and Confidential

SJ-20121227135800-023|2013-01-14（R1.0） ZTE Proprietary and Confidential

SJ-20121227135800-023|2013-01-14（R1.0） ZTE Proprietary and Confidential

SJ-20121227135800-023|2013-01-14（R1.0） ZTE Proprietary and Confidential

SJ-20121227135800-023|2013-01-14（R1.0） ZTE Proprietary and Confidential

SJ-20121227135800-023|2013-01-14（R1.0） ZTE Proprietary and Confidential

What Is in This Manual

Chapter 2, Alarm Introduces the ZXUR 9000alarms.

SJ-20121227135800-023|2013-01-14（R1.0） ZTE Proprietary and Confidential

SJ-20121227135800-023|2013-01-14（R1.0） ZTE Proprietary and Confidential

1.1 Overview of Fault Management

1.2 Alarm Code

1.3 Alarm Type

SJ-20121227135800-023|2013-01-14（R1.0） ZTE Proprietary and Confidential

l QoS alarm: related with degradation of service quality (ITU-T Recommendation

1.4 Alarm Classification

SJ-20121227135800-023|2013-01-14（R1.0） ZTE Proprietary and Confidential

1.6 Probable Cause

1.7 Handling Suggestion

Pay attention to the following tips when handling alarms.

1.8 Alarm Impact

SJ-20121227135800-023|2013-01-14（R1.0） ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20121227135800-023|2013-01-14（R1.0） ZTE Proprietary and Confidential

2.1 Equipment Alarm

2.1.2 198087001 Dry contact alarm 2

SJ-20121227135800-023|2013-01-14（R1.0） ZTE Proprietary and Confidential

l Alarm Type: Equipment Alarm

2.1.3 198087002 Dry contact alarm 3

2.1.4 198087003 Dry contact alarm 4

SJ-20121227135800-023|2013-01-14（R1.0） ZTE Proprietary and Confidential

2.1.5 198087004 Dry contact alarm 5

2.1.6 198087005 Dry contact alarm 6

SJ-20121227135800-023|2013-01-14（R1.0） ZTE Proprietary and Confidential

2.1.7 198087006 Dry contact alarm 7

2.1.8 198087007 Dry contact alarm 8

SJ-20121227135800-023|2013-01-14（R1.0） ZTE Proprietary and Confidential

2.1.9 198087008 Dry contact alarm 9

2.1.10 198087009 Dry contact alarm 10

SJ-20121227135800-023|2013-01-14（R1.0） ZTE Proprietary and Confidential

2.1.11 198087010 Dry contact alarm 11

2.1.12 198087011 Dry contact alarm 12

SJ-20121227135800-023|2013-01-14（R1.0） ZTE Proprietary and Confidential

2.1.13 198087012 EAM dry contact 1 alarm

2.1.14 198087013 EAM dry contact 2 alarm

SJ-20121227135800-023|2013-01-14（R1.0） ZTE Proprietary and Confidential