SJ-20140527134643-015-ZXUR 9000 GSM (V6.50.202) Alarm and Notification Handling Reference

ZXUR 9000 GSM
Base Station Controller
Alarm and Notification Handling Reference

Version: V6.50.202
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://support.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2014 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited.
Additionally, the contents of this document are protected by
contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit the ZTE technical support website http://support.zte.com.cn to inquire for related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No.
Revision Date
Revision Reason
R1.1
20150331
Updated to V6.50.202f. For details, refer to the relevant release

notes.
R1.0
20140731
First edition
Serial Number: SJ-20140527134643-015

Publishing Date: 2015-03-31 (R1.1)
SJ-20140527134643-015|2015-03-31 (R1.1)
ZTE Proprietary and Confidential
Contents
About This Manual ......................................................................................... I
Chapter 1 Overview .................................................................................... 1-1
Chapter 2 General Operations................................................................... 2-1
2.1 Finding the Managed Objects Through an Alarm Object ....................................... 2-1
2.1.1 Querying the Configuration Object............................................................. 2-1
2.1.2 Querying the Parent Object of a Configuration Object ................................. 2-4
2.1.3 Querying the Referring Object of a Configuration Object ............................. 2-6
2.2 Filtering Controller Alarms................................................................................. 2-10
2.2.1 Checking Board Alarms Through the Rack Diagram ................................. 2-10
2.2.2 Filtering Alarms Based on Alarm Location.................................................2-11
2.2.3 Querying Alarms by Office Information..................................................... 2-13
Chapter 3 Alarms........................................................................................ 3-1

3.1 Equipment Alarm................................................................................................ 3-1
3.1.1 199026127 Clock reference source lost (Level 3 alarm) .............................. 3-1
3.1.4 199026133 Output clock of the board is lost............................................... 3-9
3.1.5 199000170 The switch board occurred loopback port ................................. 3-9
3.1.6 199000256 OMC port's link is down..........................................................3-11
3.1.7 199000512 Trunk loss of frame ............................................................... 3-12
3.1.8 199000513 Trunk loss of signal ............................................................... 3-14
3.1.9 199000514 Trunk alarm indication signal ................................................. 3-15
3.1.10 199000515 Trunk loss of CRC multi-frame ............................................. 3-16
3.1.11 199000517 Trunk remote alarm indication .............................................. 3-19
3.1.12 199000518 Trunk link is used for CSU loopback test .............................. 3-20
3.1.13 199001024 ATM cell delineation not synchronized.................................. 3-20
3.1.14 199001025 Loss of ATM cell delineation ................................................ 3-22
3.1.15 199001026 ATM cell delineation do not synchronization about cell on
E1/T1 link ............................................................................................. 3-24
3.1.16 199001286 Input clock of the board is lost.............................................. 3-25
3.1.17 199001792 SDH/SONET:Loss of signal ................................................. 3-27
3.1.18 199001793 SDH/SONET:Loss of frame ................................................. 3-29
I
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.19 199001794 SDH/SONET:Regenerator section trace mismatch/Section

trace mismatch ..................................................................................... 3-31
3.1.20 199001795 SDH/SONET:MS alarm indication signal/Line alarm
indication signal .................................................................................... 3-32
3.1.21 199001796 SDH/SONET:MS far-end reception failure/Line far-end
reception failure .................................................................................... 3-34
3.1.22 199001797 SDH/SONET:Signal failure .................................................. 3-35
3.1.23 199001798 SDH/SONET:Signal deterioration ......................................... 3-37
3.1.24 199001799 SDH/SONET:Loss of AU pointer/Loss of path pointer ............ 3-39
3.1.25 199001800 SDH/SONET:AU alarm indication signal/Path alarm
indication signal .................................................................................... 3-40
3.1.26 199001801 SDH/SONET:HP trace mismatch/ Path trace mismatch ......... 3-42
3.1.27 199001802 SDH/SONET:HP unequipped/Path unequipped..................... 3-43
3.1.28 199001803 SDH/SONET:HP label mismatch/Path label mismatch ........... 3-45
3.1.29 199001804 SDH/SONET:HP remote reception failure/Path remote
reception failure .................................................................................... 3-46
3.1.30 199001805 SDH/SONET:Loss of multi-frame ......................................... 3-47
3.1.31 199001806 SDH/SONET:Loss of TU pointer/Loss of virtual tributary
pointer.................................................................................................. 3-49
3.1.32 199001807 SDH/SONET:Tributary unit alarm indication signal/Virtual
tributary alarm indication signal .............................................................. 3-50
3.1.33 199001808 SDH/SONET:LP remote defect indication/Virtual tributary
remote defect indication ........................................................................ 3-51
3.1.34 199001809 SDH/SONET:LP remote failure indication/Virtual tributary
remote failure indication ........................................................................ 3-52
3.1.35 199001810 SDH/SONET:LP trace mismatch/Virtual tributary trace
mismatch.............................................................................................. 3-54
3.1.36 199001811 SDH/SONET:LP unequipped/Virtual tributary unequipped ...... 3-56
3.1.37 199001812 SDH/SONET:LP label mismatch/Virtual tributary label
mismatch.............................................................................................. 3-57
3.1.38 199001816 SDH/SONET:Severely B1 error code.................................... 3-58
3.1.41 199001819 SDH/SONET:Severely BIP-2 error code ............................... 3-64
3.1.42 199001820 SDH/SONET:MS remote error indication .............................. 3-65
3.1.43 199001821 SDH/SONET:HP remote error indication............................... 3-67
3.1.44 199001826 SDH/SONET:LP remote error indication ............................... 3-69
3.1.45 199005123 The configuration is not supported ....................................... 3-71
3.1.46 199005128 Rack or shelf conflict ........................................................... 3-71
II
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.47 199005200 Board configuration information is not compatible ................. 3-72

3.1.48 199005405 Clock board phase-lock loop work mode is abnormal ............ 3-73
3.1.49 199005407 The board is power off......................................................... 3-74
3.1.50 199005632 The hard disk used-rate is over threshold ............................. 3-75
3.1.51 199005633 File system is abnormal....................................................... 3-76
3.1.52 199005634 The hard disk on board gets IO error.................................... 3-77
3.1.53 199005666 Error packets of MAC is higher than the specified
threshold .............................................................................................. 3-78
3.1.54 199005672 Clock source for SyncE is not available ................................ 3-79
3.1.55 199005673 The setting of the dial switch is changed............................... 3-81
3.1.56 199005674 Switch chip inner loop check abnormal................................. 3-82
3.1.57 199005760 Ethernet port's link is down .................................................. 3-83
3.1.58 199005761 The speed mode of Ethernet port doesn't match with
settings ................................................................................................ 3-84
3.1.59 199005768 All of the board input clocks which have the same frequency
are lost ................................................................................................. 3-85
3.1.60 199005770 The OMP board doesn't have any OMC port......................... 3-87
3.1.61 199005771 The duplex mode of Ethernet port doesn't match with
settings ................................................................................................ 3-88
3.1.62 199005772 Board device fault ............................................................... 3-89
3.1.63 199005773 High CRC error rate at E1/T1 bottom layer ........................... 3-90
3.1.64 199005774 High FAS error rate at E1/T1 bottom layer ............................ 3-92
3.1.65 199005775 High EBIT error rate at E1 bottom layer ................................ 3-94
3.1.66 199005785 GPS module is abnormal..................................................... 3-95
3.1.67 199005790 The configuration of clock shelf function is error.................... 3-96
3.1.68 199005795 The optical transceiver transmitter has detected a fault ......... 3-97
3.1.69 199005796 Clock of this board is abnormal ............................................ 3-98
3.1.70 199005797 The hard disk is abnormal ................................................... 3-99
3.1.71 199005798 The RAID of hard disks is abnormal ....................................3-100
3.1.72 199005799 Hard disk online.................................................................3-101
3.1.73 199005800 Hard disk offline.................................................................3-102
3.1.74 199005801 Memory size is abnormal....................................................3-102
3.1.75 199005802 The board lacks fabric port in the shelf ................................3-103
3.1.76 199005930 Version load failed .............................................................3-104
3.1.77 199005931 Incorrect subunit configuration for inserted board or
device .................................................................................................3-105
3.1.78 199005932 The third party firmware version load failed..........................3-105
3.1.79 199005933 Shutdown board to validate the third party firmware .............3-106
III
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.80 199007168 Port trunk failed .................................................................3-107

3.1.81 199007169 Inner port error ..................................................................3-108
3.1.82 199007170 Trunk connect asymmetry ..................................................3-109
3.1.83 199007171 Outer media trunk failed ..................................................... 3-110
3.1.84 199007172 Port physical state restore .................................................. 3-111
3.1.85 199007174 Connect port loopback ....................................................... 3-112
3.1.86 199007425 Board self loop check abnormal .......................................... 3-113
3.1.87 199015360 Mediaplane ran abnormal ................................................... 3-114
3.1.88 199015618 Too many error frames received.......................................... 3-115
3.1.89 199019712 APS channel mismatch ...................................................... 3-117
3.1.90 199019713 APS mode mismatch.......................................................... 3-118
3.1.91 199019715 APS channel between master and slave board gets
errors .................................................................................................. 3-119
3.1.92 199023050 Fan device absent .............................................................3-120
3.1.93 199023051 Power unit absent ..............................................................3-122
3.1.94 199023106 Board self-check failed when power on ...............................3-123
3.1.95 199025602 Abnormal half-fixed connection changes .............................3-124
3.1.96 199025603 Trunk is looped back ..........................................................3-125
3.1.97 199025604 Cross-linked trunk alarm.....................................................3-127
3.1.98 199025856 Rack temperature is higher than high threshold ...................3-128
3.1.99 199025857 Rack temperature is lower than low threshold ......................3-129
3.1.100 199025858 Room temperature is higher than high threshold ................3-130
3.1.101 199025859 Room temperature is lower than low threshold...................3-131
3.1.102 199025860 Voltage is higher than high threshold .................................3-132
3.1.103 199025861 Voltage is lower than low threshold ...................................3-133
3.1.104 199025862 Humidity is higher than high threshold ...............................3-134
3.1.105 199025863 Humidity is lower than low threshold..................................3-135
3.1.106 199025865 Rack door access control alarm or other monitor alarm ......3-136
3.1.107 199025866 Smoke alarm ...................................................................3-137
3.1.108 199025867 Infrared alarm ..................................................................3-138
3.1.109 199025868 Lightning alarm ................................................................3-139
3.1.110 199025869 Power switch alarm ..........................................................3-140
3.1.111 199025870 Electrical source configuration does not according with
physical...............................................................................................3-141
3.1.112 199029184 SNTP failed to synchronize time........................................3-142
3.1.113 199030722 Temperature is lower than lower-critical threshold...............3-143
3.1.114 199030723 Temperature is lower than lower-non-recoverable
threshold .............................................................................................3-144
IV
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.115 199030725 Temperature is higher than upper-critical threshold.............3-145

3.1.116 199030726 Temperature is higher than upper-non-recoverable
threshold .............................................................................................3-146
3.1.117 199030728 Voltage is lower than lower-critical threshold ......................3-148
3.1.118 199030729 Voltage is lower than lower-non-recoverable threshold........3-150
3.1.119 199030731 Voltage is higher than upper-critical threshold ....................3-153
3.1.120 199030732 Voltage is higher than upper-non-recoverable threshold ......3-155
3.1.121 199030733 Voltage is abnormal..........................................................3-158
3.1.122 199030734 Velocity of fan is lower than lower-critical threshold ............3-160
3.1.123 199030747 Module/Board device absent.............................................3-161
3.1.124 199030748 Power on failed due to S5.................................................3-162
3.1.125 199030759 Fault memory isolation .....................................................3-163
3.1.126 199030808 Processor internal error ....................................................3-164
3.1.127 199030809 Processor thermal trip ......................................................3-165
3.1.128 199393987 Board offline ....................................................................3-167
3.1.129 199419840 PTP failed to get clock attribute.........................................3-168
3.1.130 199030756 Major shelf power fault .....................................................3-169
3.1.131 199030758 Minor shelf power fault .....................................................3-171
3.1.132 199030760 CDM information is wrong ................................................3-172
3.1.133 199030761 Board extractor open........................................................3-173
3.1.134 199030762 Board power-on failure .....................................................3-174
3.1.135 199030765 Board CPU hardware error ...............................................3-175
3.1.136 199030767 Board SAS system error ...................................................3-176
3.1.137 199030768 Board PCIE error .............................................................3-177
3.1.138 199030769 Board overheat ................................................................3-178
3.1.139 199030772 Number of correctable memory errors over threshold .........3-179
3.1.140 199030773 Uncorrectable memory error .............................................3-180
3.1.141 199105029 OMP reboot alarm............................................................3-181
3.1.142 199087778 Dry contact alarm - Waterlog.............................................3-182
3.1.143 199087779 Dry contact alarm - Power loss .........................................3-182
3.1.144 199087780 Dry contact alarm - No.1 air conditioner fault......................3-183
3.1.146 199087782 Dry contact alarm - AC power abnormal ............................3-184
3.1.147 199087783 Dry contact alarm - Battery under-voltage ..........................3-185
3.1.148 199087784 Dry contact alarm - SMR abnormal ...................................3-186
3.1.149 199087785 Dry contact alarm - Under-voltage insulate drop.................3-186
3.1.150 199087786 Dry contact alarm - Device suspended ..............................3-187
3.1.151 199087787 User-defined Dry contact alarm 1 ......................................3-188
V
SJ-20140527134643-015|2015-03-31 (R1.1)

3.1.160 199087796 User-defined Dry contact alarm 10 ....................................3-194
3.1.186 199080855 Dry contact alarm - AC power abnormal ............................ 3-211
VI
SJ-20140527134643-015|2015-03-31 (R1.1)

3.1.222 199087340 FR device failure..............................................................3-235
3.1.223 199087341 FR congestion .................................................................3-237
3.1.224 199087352 NSVC's E1 failure alarm ...................................................3-237
3.1.225 199087465 NSVC's IP failure alarm ....................................................3-238
VII
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.226 199087458 PS cell block caused by slave ...........................................3-239

3.1.227 198087000 Dry contact alarm 1 ..........................................................3-240
3.1.236 198087009 Dry contact alarm 10 ........................................................3-246
3.1.239 198087012 EAM dry contact 1 alarm ..................................................3-248
3.1.247 198087102 Power overvoltage/undervoltage alarm..............................3-252
3.1.248 198087103 13M input clock failure......................................................3-253
3.1.249 198087106 SYNCLK clock failure .......................................................3-254
3.1.250 198087107 Master and slave communication link failure ......................3-255
3.1.251 198087108 Standby CMM/CMB board not present ..............................3-255
3.1.252 198087109 Standby CMM/CMB board abnormal .................................3-256
3.1.253 198087110 CMM/CMB power failure alarm .........................................3-257
3.1.254 198087112 Communication link alarm between master and slave rack
(left) ....................................................................................................3-257
3.1.255 198087113 Communication link alarm between master and slave rack
(right) ..................................................................................................3-258
3.1.256 198087114 A interface E1 Rx carrier alarm .........................................3-259
3.1.257 198087115 A interface E1 Rx frame not synchronized..........................3-259
3.1.258 198087120 A interface E1 remote alarm .............................................3-260
3.1.259 198087121 B interface E1 Rx carrier alarm .........................................3-261
3.1.260 198087122 B interface E1 Rx frame not synchronized .........................3-261
3.1.261 198087127 B interface E1 remote alarm .............................................3-262
VIII
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.262 198087128 C interface E1 Rx carrier alarm .........................................3-263

3.1.263 198087129 C interface E1 Rx frame not synchronized .........................3-264
3.1.264 198087134 C interface E1 remote alarm .............................................3-264
3.1.265 198087135 D interface E1 Rx carrier alarm .........................................3-265
3.1.266 198087136 D interface E1 Rx frame not synchronized .........................3-266
3.1.267 198087141 D interface E1 remote alarm .............................................3-267
3.1.268 198087142 E interface E1 Rx carrier alarm .........................................3-267
3.1.269 198087143 E interface E1 Rx frame not synchronized .........................3-268
3.1.270 198087148 E interface E1 remote alarm .............................................3-269
3.1.271 198087149 F interface E1 Rx carrier alarm .........................................3-269
3.1.272 198087150 F interface E1 Rx frame not synchronized .........................3-270
3.1.273 198087153 F interface E1 Rx forward sliding indication........................3-271
3.1.274 198087155 F interface E1 remote alarm .............................................3-272
3.1.275 198087156 G interface E1 Rx carrier alarm .........................................3-272
3.1.276 198087157 G interface E2 Rx frame not synchronized .........................3-273
3.1.277 198087162 G interface E1 remote alarm .............................................3-274
3.1.278 198087163 H interface E1 Rx carrier alarm .........................................3-274
3.1.279 198087164 H interface E3 Rx frame not synchronized .........................3-275
3.1.280 198087169 H interface E1 remote alarm .............................................3-276
3.1.281 198087170 Temperature alarm...........................................................3-276
3.1.282 198087171 Fan absent ......................................................................3-277
3.1.283 198087172 Fan control board CPU alarm ...........................................3-278
3.1.284 198087173 Fan alarm........................................................................3-278
3.1.285 198087174 Fan temperature alarm .....................................................3-279
3.1.286 198087175 Fan 1 alarm .....................................................................3-280
3.1.287 198087176 Fan 2 alarm .....................................................................3-280
3.1.288 198087177 Fan control board alarm ...................................................3-281
3.1.289 198087178 LNA alarm .......................................................................3-282
3.1.290 198087179 Tower amplifier power alarm .............................................3-282
3.1.291 198087180 SWR of AEM HYCOM minor alarm ...................................3-283
3.1.292 198087181 SWR of AEM HYCOM major alarm ...................................3-283
3.1.293 198087182 AEM power alarm(BTS V2)...............................................3-284
3.1.294 198087183 AEM type alarm(BTS V2) .................................................3-285
3.1.295 198087184 AEM absent(BTS V2) .......................................................3-285
3.1.296 198087185 AEM power alarm ............................................................3-286
3.1.297 198087186 LNA0 alarm .....................................................................3-287
3.1.298 198087187 LNA1 alarm .....................................................................3-287
IX
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.299 198087188 Tower Amplifier0 power alarm ...........................................3-288

3.1.300 198087189 Tower Amplifier1 power alarm ...........................................3-289
3.1.301 198087190 SWR of AEM HYCOM minor alarm ...................................3-290
3.1.302 198087191 SWR of AEM HYCOM major alarm ...................................3-291
3.1.303 198087192 AEM type alarm ...............................................................3-292
3.1.304 198087193 AEM Not-in-position alarm ................................................3-293
3.1.305 198087198 Uplink of ADC chip initialization failure...............................3-294
3.1.306 198087200 CIP resource can't be used...............................................3-295
3.1.307 198087201 Uplink failure....................................................................3-295
3.1.308 198087207 Watchdog of FUC overflow ...............................................3-296
3.1.309 198087216 Cell configuration parameter mismatch(BTS V2) ................3-297
3.1.310 198087221 Communication link between CMM and FUC break(BTS
V2)......................................................................................................3-297
3.1.311 198087224 Watchdog of TPU CIP overflow .........................................3-298
3.1.312 198087225 Software version of CIP mismatch.....................................3-299
3.1.313 198087226 Clock alarm for TPU and CMM .........................................3-299
3.1.314 198087228 TPU frame No. alarm .......................................................3-300
3.1.315 198087229 TPU CHP DSP0 initialization failure ..................................3-301
3.1.316 198087243 Cell configuration parameter mismatch..............................3-302
3.1.317 198087247 HDLC communication link between CMB and FUC
broken.................................................................................................3-302
3.1.318 198087453 signal HDLC break off ......................................................3-303
3.1.319 198087253 FU fram No error alarm ....................................................3-304
3.1.320 198087254 Rx PLL1 unlock ...............................................................3-305
3.1.321 198087255 Rx PLL2 unlock ...............................................................3-305
3.1.322 198087256 Tx PLL1 unlock................................................................3-306
3.1.323 198087257 Tx PLL2 unlock................................................................3-307
3.1.324 198087258 52M referenced clock PLL unlock......................................3-307
3.1.325 198087259 Tx IF PLL unlock..............................................................3-308
3.1.326 198087260 EEPROM resource can't be used......................................3-309
3.1.327 198087261 FPGA interface failure ......................................................3-309
3.1.328 198087262 PA VSWR alarm(BTS V2).................................................3-310
3.1.329 198087263 PA overtemperature minor alarm(BTS V2) .........................3-310
3.1.330 198087264 PA overtemperature major alarm(BTS V2) ......................... 3-311
3.1.331 198087265 PA output power alarm .....................................................3-312
3.1.332 198087266 PA power overvoltage ......................................................3-312
3.1.333 198087267 PA power lower voltage ....................................................3-313
3.1.334 198087268 Downlink checksum error of DLRC_AL1 ............................3-314
X
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.335 198087269 DUC chip initialization failure ............................................3-314

3.1.336 198087270 80w PA VSWR alarm .......................................................3-315
3.1.337 198087271 80w PA overtemperature ..................................................3-316
3.1.338 198087272 80w PA overtemperature major alarm................................3-316
3.1.339 198087273 80w PA output power alarm ..............................................3-317
3.1.340 198087274 80w PA power overvoltage ...............................................3-318
3.1.341 198087275 80w PA power lower voltage .............................................3-318
3.1.342 198087276 80w PA absent.................................................................3-319
3.1.343 198087277 TXIF unlock .....................................................................3-319
3.1.344 198087278 TPF unlock ......................................................................3-320
3.1.345 198087279 TXRF unlock....................................................................3-321
3.1.346 198087280 RXRF unlock ...................................................................3-322
3.1.347 198087281 13 MHz clock lost.............................................................3-322
3.1.348 198087282 60 ms clock lost ...............................................................3-323
3.1.349 198087285 52 MHz clock lost.............................................................3-324
3.1.350 198087288 PA power overvoltage alarm .............................................3-325
3.1.351 198087289 PA power undervoltage alarm ...........................................3-325
3.1.352 198087290 PA VSWR alarm ..............................................................3-326
3.1.353 198087291 PA temperature minor alarm .............................................3-327
3.1.354 198087292 PA temperature major alarm .............................................3-327
3.1.355 198087293 PA forward power(3db) alarm............................................3-328
3.1.356 198087294 RTU power alarm.............................................................3-329
3.1.357 198087295 RTU power temperature alarm ..........................................3-329
3.1.358 198087296 RTU power output overvoltage alarm ................................3-330
3.1.359 198087297 RTU power input failure alarm...........................................3-331
3.1.360 198087298 IQ calibration parameters abnormal alarm .........................3-331
3.1.361 198087299 EAM heat exchanger alarm ..............................................3-332
3.1.362 198087300 EAM TRX layer fan-4 alarm ..............................................3-332
3.1.363 198087301 EAM AEM layer axis-flow fan alarm...................................3-333
3.1.364 198087302 EAM smoke alarm............................................................3-334
3.1.365 198087303 EAM waterproof alarm......................................................3-334
3.1.366 198087304 EAM lightning protection alarm .........................................3-335
3.1.367 198087305 EAM backdoor access control alarm .................................3-335
3.1.368 198087306 EAM frontdoor access control alarm..................................3-336
3.1.369 198087307 EAM PWR monitoring unit alarm.......................................3-337
3.1.370 198087308 EAM heat exchanger electric heater alarm.........................3-337
3.1.371 198087309 EAM heat exchanger control board alarm ..........................3-338
XI
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.372 198087310 EAM heat exchanger external circulation fan 2 alarm .........3-338
3.1.373 198087311 EAM heat exchanger external circulation fan 1 alarm..........3-339
3.1.374 198087312 EAM heat exchanger internal circulation fan 2 alarm ..........3-340
3.1.375 198087313 EAM heat exchanger internal circulation fan 1 alarm ..........3-340
3.1.376 198087314 EAM heat exchanger 485 communication alarm.................3-341
3.1.377 198087315 EAM temperature alarm ...................................................3-342
3.1.378 198087316 EAM TRX layer mixed-flow fan 1 alarm .............................3-342
3.1.381 198087319 Communication broken between EAM and CMB ................3-344
3.1.382 198087320 Power undervoltage alarm ................................................3-345
3.1.383 198087321 Inner fan 2 alarm (for M8202) ...........................................3-345
3.1.384 198087322 Inner fan 1 alarm (for M8202) ...........................................3-346
3.1.385 198087323 Outer fan 2 and fan 4 alarm (for M8202) ............................3-346
3.1.386 198087324 Outer fan 1 and fan 3 alarm (for M8202) ............................3-347
3.1.387 198087325 Rack temperature minor alarm..........................................3-348
3.1.388 198087326 Rack temperature major alarm..........................................3-348
3.1.389 198087327 Layer 3 fan 1 alarm (for M8206) ........................................3-349
3.1.398 198087391 FCU power undervoltage alarm ........................................3-355
3.1.399 198087403 The clock alarm about transmission of CCI board
Abis-E1 ...............................................................................................3-356
3.1.400 198087404 The local working clock alarm of CCI board .......................3-356
3.1.401 198087405 The clock alarm about transmission of CCI board 13M .......3-357
3.1.402 198087406 CCI opposite board alarm.................................................3-358
3.1.403 198087407 IQ FPGA internal clock alarm............................................3-358
3.1.404 198087408 IQ FPGA light interface alarm ...........................................3-359
3.1.405 198087409 IQ FPGA LVDS interface alarm .........................................3-359
3.1.406 198087410 IQ FPGA internal data alarm.............................................3-360
3.1.407 198087470 Fan absence alarm ..........................................................3-361
3.1.408 198087471 Fan rotate alarm ..............................................................3-361
XII
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.409 198087472 CMB and FNCB RS485 link break alarm ...........................3-362
3.1.410 198087480 Status of TX5 filter alarm ..................................................3-363
3.1.411 198087481 Status of TX6 filter alarm ..................................................3-363
3.1.412 198087443 Diversity antenna lost .......................................................3-364
3.1.413 198087444 Diversity antenna identical ................................................3-364
3.1.414 198087411 13M,61.44M clock lost alarm.............................................3-365
3.1.415 198087412 60ms clock lost alarm.......................................................3-366
3.1.416 198087413 26MHz and 52MHz lost of clock alarm...............................3-366
3.1.417 198087414 the failure examination alarm of the 60ms uplink frame.......3-367
3.1.418 198087415 checking block data error alarm ........................................3-368
3.1.419 198087416 up link LVDS SERDES lost lock alarm ...............................3-368
3.1.420 198087417 FN error alarm .................................................................3-369
3.1.421 198087432 Diversity antenna lost .......................................................3-369
3.1.422 198087433 Diversity antenna identical ................................................3-370
3.1.423 198087451 board not support 16MHW................................................3-371
3.1.424 198087452 cmb or cpu overload.........................................................3-371
3.1.425 198087454 main HDLC break off........................................................3-372
3.1.426 198087455 FIB configure wrong .........................................................3-372
3.1.427 198087456 lay3 of FIB software has no response................................3-373
3.1.428 198087460 positive 12 voltage alarm ..................................................3-374
3.1.429 198087461 negative 12 voltage alarm.................................................3-374
3.1.430 198087462 DSP 1.2v voltage alarm....................................................3-375
3.1.431 198087463 6.4v voltage alarm............................................................3-376
3.1.432 198087464 5v voltage alarm ..............................................................3-376
3.1.433 198087473 DTPU CPU overload ........................................................3-377
3.1.434 198087483 GPS signal synchronization exception ...............................3-378
3.1.435 198087484 Second pulse loss............................................................3-378
3.1.436 198087485 Antenna open-circuit alarm ...............................................3-379
3.1.437 198087486 Antenna short-circuit alarm ...............................................3-380
3.1.438 198087487 Lost satellite alarm ...........................................................3-380
3.1.439 198087510 CPU of FIB overload ........................................................3-381
3.1.440 198088000 DTPU not support Baseband-Hop alarm............................3-382
3.1.441 198088001 PA Power Voltage Adjusting Path Disconnected.................3-382
3.1.442 198088002 PA Power Voltage Adjusting Data Error .............................3-383
3.1.443 198088003 PA Power Voltage Adjusting Data Illegal ............................3-384
3.1.444 198088004 Access iBSC failure..........................................................3-384
3.1.445 198088005 Control link broken ...........................................................3-385
XIII
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.446 198088006 Operation link broken(CS) ................................................3-386

3.1.447 198088007 Operation link broken(PS) ................................................3-386
3.1.448 198088008 Parameter configuration mismatch ....................................3-387
3.1.449 198088009 DSP initialization failure....................................................3-387
3.1.450 198088010 Parameter configuration failure of AD6537.........................3-388
3.1.451 198088011 Tx PLL unlock ..................................................................3-389
3.1.452 198088012 Wrong parameter configuration for EEPROM.....................3-389
3.1.453 198088013 FLASH memory fault ........................................................3-390
3.1.454 198088014 Run abnormity of DSP......................................................3-391
3.1.455 198088015 FPGA interface fault.........................................................3-391
3.1.456 198088016 CHP frame fault ...............................................................3-392
3.1.457 198088017 Wrong receive channel of RF............................................3-392
3.1.458 198088018 Get DNS failure when configuration IP of active .................3-393
3.1.459 198088019 Analyse failure of DNS domain name ................................3-394
3.1.460 198088020 IPSec failure ....................................................................3-394
3.1.461 198088021 RF channel and HTRG board unconformity .......................3-395
3.1.462 198088022 Get HBTS'S IP address failure from DHCP Sever ..............3-395
3.1.463 198088023 Over temperature.............................................................3-396
3.1.464 198088024 Voltage abnormity ............................................................3-397
3.1.465 198088025 Abis link change alarm .....................................................3-397
3.1.466 198088026 IPOE uplink and downlink jam alarm .................................3-398
3.1.467 198088027 DIP E1 rack, rack type error..............................................3-399
3.1.468 198088028 DIP E1 rack, rack number error.........................................3-399
3.1.469 198088029 DIP E1 rack,slave rack 1 port error....................................3-400
3.1.470 198088030 DIP E1 rack,slave rack 2 port error....................................3-400
3.1.471 198088031 DIP E1 rack,satellite back up flag error ..............................3-401
3.1.472 198088032 DIP E1 rack,oam time slot error ........................................3-402
3.1.473 198088033 DIP IP rack,access mode error(IP or IPOE) .......................3-402
3.1.474 198088034 DIP IP rack,rack number error...........................................3-403
3.1.475 198088035 DIP IP rack,site number error............................................3-403
3.1.476 198088036 DIP IP rack,sequence number error ..................................3-404
3.1.477 198088037 Mains power failure alarm.................................................3-405
3.1.478 198088038 Alarm of the trx's down link LRC failed...............................3-405
3.1.479 199005784 Please reboot the board after you have saved the new
configuration to make it effective ...........................................................3-406
3.2 Processing error Alarm ....................................................................................3-407
3.2.1 199002560 CPU utilization over alarm limit .............................................3-407
3.2.2 199003584 Memory insufficient alarm.....................................................3-408
XIV
SJ-20140527134643-015|2015-03-31 (R1.1)
3.2.3 199004357 The system bureau changed ................................................3-409

3.2.4 199005908 Lack of version ....................................................................3-410
3.2.5 199005909 Download version failed .......................................................3-410
3.2.6 199005910 Process execute failed ......................................................... 3-411
3.2.7 199025600 Connection check be disabled in board .................................3-412
3.2.8 199066032 SNTP time synchronization exceeded the threhold ................3-412
3.2.9 199066027 SNTP time synchronization failed .........................................3-414
3.2.10 199392708 Time synchronization over alarm limit in RPU accesstype ......3-415
3.2.11 199399616 LAPD link broken ...............................................................3-416
3.2.12 199066013 MTP3 link congestion.........................................................3-417
3.2.13 199005202 Configuration conflicts between DBS and CMM ...................3-418
3.2.14 199005912 BOOTROM version update failed........................................3-419
3.2.15 199409857 Routing table utilization exceeds the second threshold .........3-420
3.2.16 199087482 dbsapp data error alarm .....................................................3-421
3.2.17 199087505 Board Connect Fail ............................................................3-422
3.2.18 199105051 The configuration of master and slave logservice is
inconsistent .........................................................................................3-423
3.2.19 199101000 Fail to load DPI Signature library.........................................3-424
3.2.20 199101001 Fail to initialize DPI regular engine ......................................3-425
3.2.21 199101002 DPI regular engine run check failed.....................................3-426
3.3 Communications Alarm....................................................................................3-427
3.3.1 199003841 The control plane retransfer ratio over the threshold...............3-427
3.3.2 199005122 Loss of Active/standby communication link ............................3-428
3.3.3 199005382 Environment monitor board communication is abnormal.........3-429
3.3.4 199005396 Packet loopback test of internal media plane abnormal ..........3-430
3.3.5 199005397 Communication of RAW MAC channel is abnormal ................3-431
3.3.6 199005406 Sub-unit state is abnormal....................................................3-432
3.3.7 199025631 LVDS link error ....................................................................3-432
3.3.8 199029952 802.3ah ethernet link fault event ...........................................3-434
3.3.9 199030208 CFM fault ............................................................................3-435
3.3.10 199066003 Control plane communication abnormal between board and
its home module ..................................................................................3-438
3.3.11 199393986 Control plane communication is abnormal between this
board and the active independent board ................................................3-439
3.3.12 199393988 Control plane communication abnormal between module
and OMP.............................................................................................3-440
3.3.13 199066008 MTP2 link sending is overloaded ........................................3-441
3.3.14 199066009 MTP2 link reception is overloaded ......................................3-442
XV
SJ-20140527134643-015|2015-03-31 (R1.1)
3.3.15 199066010 MTP3 office inaccessible ....................................................3-443

3.3.16 199066011 MTP3 link unavailable ........................................................3-445
3.3.17 199066014 M3UA office inaccessible ...................................................3-447
3.3.18 199066019 Association broken ............................................................3-450
3.3.19 199406528 The protocol state of port-channel interface is down .............3-452
3.3.20 199406529 The protocol state of SUPERVLAN interface is down ...........3-453
3.3.21 199406530 The protocol state of tunnel port is down .............................3-454
3.3.22 199407043 PPP link is down ................................................................3-456
3.3.23 199411392 BFD session interruption ....................................................3-458
3.3.24 199411393 BFD session negotiation failure...........................................3-460
3.3.25 199066026 Association path broken .....................................................3-462
3.3.26 199420352 IPD session interruption .....................................................3-463
3.3.27 199007426 Switch chip buffer overflow .................................................3-465
3.3.28 199105035 The communication link between LogService board and
OMP is broken.....................................................................................3-466
3.3.29 199105041 ECMM/EGBS/EGFS Board Offline ......................................3-466
3.3.30 199105042 The configuration of ECMM/EGBS/EGFS Board doesn't
match with OMM..................................................................................3-468
3.3.31 199105045 The communication link between LogService board for FST
and OMP is broken ..............................................................................3-469
3.3.32 199105047 The FTP link for full signal tracing is exceptional ..................3-470
3.3.33 199087775 Super site exchanged to the satellitic Abis link or slave
link......................................................................................................3-471
3.3.34 199087342 Cell interruption alarm ........................................................3-471
3.3.35 199087380 TRX Manual Block .............................................................3-473
3.3.36 199087336 Rack Abis control link broken..............................................3-473
3.3.37 199087468 lapd jam alarm...................................................................3-474
3.3.38 199087337 Site Abis control link broken................................................3-476
3.3.39 198087101 HW link broken ..................................................................3-477
3.4 Qos Alarm ......................................................................................................3-477
3.4.1 199066018 Association congested .........................................................3-477
3.4.2 199105044 The internal KPI of the logic board is abnormal ......................3-478
3.4.3 199087344 MSC overload control alarm at FUC mode ............................3-480
3.4.4 199087345 CPU overload control alarm at FUC mode.............................3-481
3.4.5 199087346 Signaling point congestion control alarm at FUC mode...........3-482
3.4.6 199087347 MSC overload control alarm at SYS mode.............................3-483
3.4.7 199087348 CPU overload control alarm at SYS mode .............................3-483
3.4.8 199087349 Signaling point congestion control alarm at SYS mode ...........3-484
XVI
SJ-20140527134643-015|2015-03-31 (R1.1)
3.4.9 199087350 CCCH overload control ........................................................3-485

3.4.10 199087506 NSE block alarm ................................................................3-486
3.4.11 199087507 SGSN is blocked................................................................3-487
3.4.12 199087758 Manual User Access control alarm ......................................3-488
3.4.13 199087759 CPU overload control alarm at Paging mode .......................3-489
3.4.14 199087773 CIC manual blocked alarm .................................................3-490
3.4.15 199087774 BVC manual blocked alarm ................................................3-491
3.4.16 199087517 Shelf overload control alarm at FUC mode ..........................3-492
3.4.17 199087518 Shelf overload control alarm at SYS mode...........................3-493
3.4.18 199087381 The time-slot of air interface blocked manually.....................3-494
3.4.19 199101003 The usage of DPI DBS table space exceeds the limit
value ...................................................................................................3-494
Chapter 4 Notifications .............................................................................. 4-1

4.1 199026176 The currently locked reference of the clock board has been
changed........................................................................................................... 4-3
4.2 199000576 Trunk slip ......................................................................................... 4-4
4.3 199000834 HDLC is abnormal ............................................................................ 4-5
4.4 199001600 CPU resets on a board in the same shelf ........................................... 4-6
4.5 199004418 Logic CPU is power on successfully................................................... 4-7
4.6 199004419 Logic CPU is power on failed............................................................. 4-7
4.7 199005189 Board change over ........................................................................... 4-9
4.8 199005448 Environment parameters set fail ........................................................ 4-9
4.9 199005718 Two master clock ports is directly connected .................................... 4-10
4.10 199005720 The CDM data was covered ...........................................................4-11
4.11 199005977 Running version not match with database configuration................... 4-12
4.12 199005982 Patch operation failed ................................................................... 4-13
4.13 199005983 Write back version information ....................................................... 4-13
4.14 199005984 Check version information ............................................................. 4-14
4.15 199005985 Synchronize version information .................................................... 4-14
4.16 199006720 Environment monitoring board is powered on or reset ..................... 4-15
4.17 199007232 Poor board recover ....................................................................... 4-16
4.18 199008000 Failed to load data after the node is powered on ............................. 4-17
4.19 199008007 Database failed to save data ......................................................... 4-18
4.20 199008769 Failed to synchronize data between nodes ..................................... 4-20
4.21 199008770 Failed to update node data ............................................................ 4-21
4.22 199010048 Insufficient memory of database .................................................... 4-22
4.23 199011073 LAPD failed to initialize HDLC........................................................ 4-23
4.24 199011333 MTP2 failed to initialize HDLC........................................................ 4-24
XVII
SJ-20140527134643-015|2015-03-31 (R1.1)
4.25 199013890 Sigtran error message received ..................................................... 4-25

4.26 199014145 Restart the association.................................................................. 4-26
4.27 199014150 Association config error ................................................................. 4-27
4.28 199014152 Dynamic association config error ................................................... 4-28
4.29 199017992 Protocol state of aggregation port member interface is down ........... 4-29
4.30 199017993 Failed to add IPv6 dynamic route ................................................... 4-30
4.31 199018241 TCP connection closed ................................................................. 4-32
4.32 199018500 The peer IP address is the same as the local IP address of the
PPP link ......................................................................................................... 4-34
4.33 199018501 Fail to create the HDLC channel .................................................... 4-35
4.34 199018502 Fail to initialize the HDLC chip ....................................................... 4-36
4.35 199018504 Succeed to create the HDLC channel............................................. 4-37
4.36 199018753 The configuration of UID/HDLC/IPE1 in database is wrong .............. 4-38
4.37 199019777 APS switchover happens............................................................... 4-39
4.38 199020554 Failed to add PPP route ................................................................ 4-40
4.39 199020571 Failed to perform offline configuration............................................. 4-42
4.40 199020802 An IP address conflicts with another system on the subnet .............. 4-42
4.41 199020803 A MAC address conflicts with another system on the subnet............ 4-43
4.42 199020805 ARP detecting failed ..................................................................... 4-44
4.43 199020806 ARP detecting reply is different from static ARP .............................. 4-46
4.44 199021330 Failed to establish OSPFv2 neighbors............................................ 4-47
4.45 199021837 Fail to add dynamic route .............................................................. 4-50
4.46 199028233 Failed to establish OSPFv3 neighbors............................................ 4-51
4.47 199030528 The result of starting PD task......................................................... 4-54
4.48 199030820 Memory inform reported by BIOS................................................... 4-56
4.49 199031041 ACL query table is unavailable....................................................... 4-57
4.50 199032064 IPv6 addresses conflicted.............................................................. 4-58
4.51 199032065 Peer-end IPv6 addresses of SuperVLAN member interfaces
conflict ........................................................................................................... 4-60
4.52 199032066 Static neighbor cache entry detecting not matched.......................... 4-61
4.53 199032067 Neighbor cache entry detecting failed............................................. 4-62
4.54 199031297 PTP slave port link broken............................................................. 4-64
4.55 199031298 PTP slave port change .................................................................. 4-65
4.56 199105001 Failed to get the table of configuration ............................................ 4-66
4.57 199105002 The route table is overloaded ........................................................ 4-69
4.58 199105003 Failed to handle DHCP message from other network ...................... 4-70
4.59 199105004 Failed to operate multicast group ................................................... 4-71
4.60 199105005 Clock difference of slave is large.................................................... 4-72
XVIII
SJ-20140527134643-015|2015-03-31 (R1.1)
4.61 199105006 Slave losted external clock ............................................................ 4-73

4.62 199105008 Bandwidth automatic adjustment is useless .................................... 4-74
4.63 199105018 Unable to save Performance File ................................................... 4-75
4.64 199105019 SLAVE memory check fail notification............................................. 4-76
4.65 199105030 OMP received data is not complete................................................ 4-77
4.66 199105032 Transport Path Occupied BandWidth Overload ............................... 4-78
4.67 199105033 Transport Path group Occupied Bandwidth Overload ...................... 4-79
4.68 199105043 The slave's IPUDP configuration is modified ................................... 4-80
4.69 199105046 The log files on LogService board are unavailable .......................... 4-81
4.70 199105048 OMP disk reserved for performance files is insufficient .................... 4-82
4.71 199087360 BCCH Exchange Fail .................................................................... 4-82
4.72 199087393 Ring state notification.................................................................... 4-84
4.73 199087394 Intelligent power up/down preparation notification ........................... 4-84
4.74 199087459 cell no gprs traffic inform ............................................................... 4-85
4.75 199087469 abis route change inform ............................................................... 4-86
4.76 199087353 NSVC deletion notification ............................................................. 4-86
4.77 199087395 SNS Size process failure notification .............................................. 4-87
4.78 199087396 SNS Config process failure notification........................................... 4-88
4.79 199087466 NSVC's IP deletion notification....................................................... 4-89
4.80 199087359 No access of BSC to MSC SPC..................................................... 4-90
4.81 199087503 Baseband frequency hopping exchange for trx fail .......................... 4-90
4.82 199087504 Baseband frequency hopping exchange for trx restore .................... 4-91
4.83 199087508 Block Successfully After Service released ...................................... 4-92
4.84 199087751 dbsapp no avilable PCU resource inform........................................ 4-93
4.85 199087760 BTS master power recover notification ........................................... 4-93
4.86 199087761 BTS master power interruption notification...................................... 4-94
4.87 199087762 After BTS mains power failure TRX terminated notification .............. 4-95
4.88 199087772 Super Site Connect in ................................................................... 4-96
4.89 199087799 Cell intelligent power-on or power-down ......................................... 4-96
4.90 199087514 TRAU frame sync loss notification.................................................. 4-97
4.91 199087515 BCCH Exchange Success ............................................................. 4-97
4.92 199087516 Mute call detect ............................................................................ 4-98
4.93 199087519 Release dynamic association by force............................................ 4-99
4.94 199087520 Gb interface throughput exceed permissible value .........................4-100
4.95 199087521 Cell's home-processor transformed ...............................................4-101
4.96 198087338 TRX No Traffic.............................................................................4-102
4.97 198087434 Cannot detect up or down TRAU notification..................................4-102
XIX
SJ-20140527134643-015|2015-03-31 (R1.1)
4.98 198087339 BTS self maintenance inform ........................................................4-103

4.99 198087477 site board cpu overload ................................................................4-103
4.100 198087478 uplink user layer jam inform ........................................................4-104
4.101 198087479 downlink user layer jam inform....................................................4-105
4.102 198087488 chp cycle adjust trau information .................................................4-105
4.103 198087500 Radio Interface Synchronization ARF emendate Successfully.......4-106
4.104 198087501 Radio Interface Synchronization ARF emendate Failed ................4-107
4.105 198087502 Site IP Address conflicted...........................................................4-107
4.106 198087512 IDS Attack detecting...................................................................4-108
Appendix A Link Information ................................................................... A-1

A.1 A1001 ............................................................................................................... A-2
A.2 A1010 ............................................................................................................... A-2
A.3 A1011 ............................................................................................................... A-2
A.4 A1012 ............................................................................................................... A-2
A.5 A1013 ............................................................................................................... A-3
A.6 A1014 ............................................................................................................... A-3
A.7 A1015 ............................................................................................................... A-4
A.8 A1016 ............................................................................................................... A-4
A.9 A1021 ............................................................................................................... A-4
A.10 A1022 ............................................................................................................. A-6
A.11 A1023.............................................................................................................. A-6
A.12 A1024 ............................................................................................................. A-8
A.13 A2001 ............................................................................................................. A-8
A.14 A2002 ............................................................................................................. A-9
A.15 A2003 ........................................................................................................... A-11
A.16 A2005 ........................................................................................................... A-12
A.17 A2007 ........................................................................................................... A-13
A.18 A2009 ........................................................................................................... A-14
A.19 A2010 ........................................................................................................... A-15
A.20 A2011............................................................................................................ A-16
A.21 A2012 ........................................................................................................... A-18
A.22 A2013 ........................................................................................................... A-19
A.23 A2014 ........................................................................................................... A-20
A.24 A2015 ........................................................................................................... A-21
A.25 A2016 ........................................................................................................... A-22
A.26 A2017 ........................................................................................................... A-23
A.27 A2018 ........................................................................................................... A-25
XX
SJ-20140527134643-015|2015-03-31 (R1.1)
A.28 A2019 ........................................................................................................... A-26

A.29 A2051 ........................................................................................................... A-27
Glossary .......................................................................................................... I
XXI
SJ-20140527134643-015|2015-03-31 (R1.1)
This page intentionally left blank.
XXII
SJ-20140527134643-015|2015-03-31 (R1.1)
About This Manual

Purpose
This manual describes how to handle ZXUR 9000 GSM alarms and notifications.
Intended Audience
This manual is intended for:
l
l
Maintenance engineers
On-duty staff in equipment room
What Is in This Manual

This manual has the following chapters:
Chapter
Description
1, Overview
Gives an overview of ZXUR 9000 GSM alarms and notifications.
2, General Operations
Describes the common operations for alarm handling.
3, Alarms
Describes the alarms in terms of alarm properties, causes, impact,

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

impact, and Action.
Appendix A Link Information
Describes the complex operations for alarm handling.
I
SJ-20140527134643-015|2015-03-31 (R1.1)
II
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 1
Overview
Functions of Fault Management
The fault management system collects fault information from all the NEs in the managed
network in near real-time, such as boards, links, databases, and servers, and then
displays the collected fault information in the format of alarm or notification. The fault
management system helps the system administrator quickly locate and resolve faults
in the managed network. It also provides telecom operators, network management
departments, and equipment vendors with correct and timely alarm data to ensure stable
network operations.
Fault Indication
The fault management system indicates a fault or event occurring in the network in the
form of alarm or notification.
l
A fault is indicated in the form of alarm when it persists and affects the reliability
and services of the system. An alarm will be cleared only after the fault is resolved.
Immediate troubleshooting is required when alarms occur.
A notification indicates a non-repeatable or instantaneous fault or event in the
system, for example, board reset and signaling overload. Such a fault or event is
normally caused by a sudden environment change or other accidental factors. No
special handling is required because the fault or event causing a notification can be
automatically handled by the system. However, a frequently-reported notification
requires troubleshooting.
Alarm Format
The alarms defined for the ZXUR 9000 GSMare provided with the information such as
property and possible causes. For details, refer to Table 1-1.
Table 1-1 Alarm Format Description
Item
Description
Alarm Code
Uniquely identifies an alarm.
Name
Summarizes the fault information, such as the fault cause and phenomenon.
1-1
SJ-20140527134643-015|2015-03-31 (R1.1)
ZXUR 9000 GSM Alarm and Notification Handling Reference
Item
Description
Alarm severity
There are four alarm severity levels, which are indicated in descending order
of severity as Critical, Major, Minor, and Warning.
l
Critical: indicates a fault that causes failures of system operations or

service capabilities. Immediate troubleshooting is required when a critical
alarm is reported.
Major: indicates a fault that seriously impacts proper system operations or

reduces service capabilities. Clearing the fault to restore the system as
soon as possible is required when a major alarm occurs.
Minor: indicates a fault that slightly influences proper system operations or

reduces service capabilities. Proper measures should be taken to clear
the fault in a timely manner and prevent the occurrence of more severe
alarms when a major alarm occurs.
Warning: indicates a fault that has a potential or gradual impact on proper

system operations or service capabilities. Warning messages need to
be analyzed and proper measures should be taken to clear the fault in a
timely manner and avoid more severe alarms.
Unknown: indicates a fault that severity is defined by users.
The impact degree described in the definition of alarm severity refers to the
impact on a single index, for example, reliability or security. Once the impact
on any index reaches the specified threshold, the severity level of the alarm
can be roughly determined. If an alarm has an impact on multiple indices, its
severity level should be escalated accordingly.
Alarm Type
Based on the triggering condition and system impact, alarms can be classified
into the following five types:
l
Equipment alarm: related with equipment hardware faults.
Communication alarm: related with information transmission faults (ITU-T

Recommendation X.733).
Processing error alarm: related with software or processing faults (defined

in ITU-T Recommendation X.733).
Environment alarm: related with the environment where the equipment is

located (defined in ITU-T Recommendation X.733).
QoS alarm: related with equipment operation performance or indexes.
Alarm Description
Provides the fault information in detail.
Alarm Cause
Provides probable alarm causes to help users troubleshoot, find preventive

measures, and restore the system to normal state in a timely manner.
Impact
Provides the consequence of each alarm and the impact on the system and
services.
1-2
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 1 Overview
Item
Description
Action
Provides the troubleshooting steps and suggestions.

During the alarm handling process, the following tips needs your attention:
l
After recording the fault information, O&M personnel needs to handle the
fault step by step as suggested. If there is no otherwise specified and the
fault is solved (that is, alarm is cleared), the alarm handling process ends.
If the fault persists, go to the next step.
If fault cannot be removed, contact the local ZTE office.
Notification Format
The notifications defined for the ZXUR 9000 GSM are provided with the information such
as property and possible causes. For details, refer to Table 1-2.
Table 1-2 Notification Format Description
Item
Description
Notification Code
Uniquely identifies a notification.
Name
Summarizes the event information, such as the cause and phenomenon.
Notification severity
There are two alarm severity levels, which are indicated in descending order of
severity as Major, and Minor.
l
Major: indicates a fault that seriously impacts proper system operations or

reduces service capabilities. Clearing the fault to restore the system as
soon as possible is required when a major alarm occurs.
Minor: indicates a fault that slightly influences proper system operations or

reduces service capabilities. Proper measures should be taken to clear
the fault in a timely manner and prevent the occurrence of more severe
alarms when a major alarm occurs.
The impact degree described in the definition of notification severity refers

to the impact on a single index, for example, reliability or security. Once the
impact on any index reaches the specified threshold, the severity level of the
notification can be roughly determined. If a notification has an impact on
multiple indices, its severity level should be escalated accordingly.
Notification Type
The notification types are the same as the alarm types.
Notification
Provides the fault information in detail.
Description
Notification Causes
Provides probable notification causes to help users troubleshoot, find

preventive measures, and restore the system to normal state in a timely
manner.
Impact
Provides the consequence of each notification and the impact on the system
and services.
1-3
SJ-20140527134643-015|2015-03-31 (R1.1)
Item
Description
Action
Provides the troubleshooting steps and suggestions.

During the alarm handling process, the following tips needs your attention:
l
After recording the fault information, O&M personnel needs to handle the
fault step by step as suggested. If there is no otherwise specified and the
fault is solved (that is, alarm is cleared), the alarm handling process ends.
If the fault persists, go to the next step.
If fault cannot be removed, contact the local ZTE office.
1-4
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 2
General Operations
Table of Contents
Finding the Managed Objects Through an Alarm Object.............................................2-1
Filtering Controller Alarms ........................................................................................2-10
2.1 Finding the Managed Objects Through an Alarm

Object
On the EMS, based on the key information of an alarm object, you can find the managed
elements and check their attributes (configuration parameters).
Key information of an alarm object:
l
l
Subnet and NE information

Alarm MO information (contained in the alarm details), including:
Alarm object MOC
Alarm object DN
Alarm object name, which is user-defined
Related managed objects:

l
l
l
l
l
Configuration object
Parent object
Sub-object
Referring object
Referred object
2.1.1 Querying the Configuration Object

This procedure takes the configuration object Adjacent Office Information (RemoteSp)
as an example to describe how to query related configuration objects of an alarm object.
Key information of the alarm object is as follows:
l
l
l
Alarm object MOC=REMOTESP

Alarm object DN=TransportNetwork=1,Ss7=1,LocalSp=1,RemoteSp=1
Subnet and NE information: SubNetwork=1333,MEID=1333
The complete DN information that can be used for checking or modifying the configuration
data is as follows:
2-1
SJ-20140527134643-015|2015-03-31 (R1.1)
SubNetwork=1333,MEID=1333,ConfigSet=n,TransportNetwork=1,Ss7=1,LocalSp=1,Re
moteSp=1
Where:
l
l
ConfigSet=0 indicates that the data is in the modification area (used for modifying NE
configuration data).
ConfigSet=1 indicates that the data is in the snapshot area (used for checking NE
configuration).
Steps
l
Querying configuration objects through the GUI

1. From the navigation tree in the Configuration Management window, select
Snapshot Area under the NE node, see Figure 2-1.
Figure 2-1 Selecting the Snapshot Area
2. In the search box, enter the object type name Adjacent Office Information, and
click
. See Figure 2-2.
Figure 2-2 Querying the Object Type
2-2
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 2 General Operations
The Adjacent Office Information-List tab is displayed in the right pane.

3. Find the configuration object in the list.
You can set conditions to quickly find the object, for example, select DN as the
matching condition, like as the matching algorithm, and TransportNetwork=1 as
the matching value, see Figure 2-3.
Figure 2-3 Querying the Configuration Object
4. Double-click a configuration object and view its attributes in the displayed tab, see
Figure 2-4.
Figure 2-4 Attributes of a Configuration Object
Querying configuration objects through the MML

1. In the navigation tree of the MML Terminal, select Configuration Management
> Query Managed Object, see Figure 2-5.
Figure 2-5 Selecting the Command Type
2. Enter the command QUERY:MOC="RemoteSp",MOI="SubNetwork=1333,MEI

D=1333,ConfigSet=1,TransportNetwork=1,Ss7=1,LocalSp=1,RemoteSp=1"; to
query the managed object.
2-3
SJ-20140527134643-015|2015-03-31 (R1.1)
Note:
The configuration object MOC is case sensitive.
The command result is as follows:
End of Steps
2.1.2 Querying the Parent Object of a Configuration Object

This procedure takes the No.7 Signalling Configuration(Ss7) parent object as an example
to describe how to query the configured parent object through the alarm object information.
l
l
l
Alarm object MOC=REMOTESP

Alarm object DN=TransportNetwork=1,Ss7=1,LocalSp=1,RemoteSp=1
Subnet and NE information SubNetwork=1333,MEID=1333
Therefore, the DN information of No.7 Signalling Configuration(Ss7) is DN=TransportNe

twork=1,Ss7=1.
data is as follows:
SubNetwork=1333,MEID=1333,ConfigSet=1,TransportNetwork=1,Ss7=1.
Steps
l
Querying the parent object through the GUI

2-4
SJ-20140527134643-015|2015-03-31 (R1.1)
Figure 2-6 Selecting the Snapshot Area Node
2. In the search box, enter the object type name 7 Signalling Configuration, and
click
. See Figure 2-7.
The No.7 Signalling Configuration-List tab is displayed in the right pane

matching condition, like as the matching algorithm, and TransportNetwork=1 as
the matching value, see Figure 2-8.
2-5
SJ-20140527134643-015|2015-03-31 (R1.1)
4. Double-click the configuration object. Its attributes are shown the displayed tab,
see Figure 2-9.
Figure 2-9 Attributes of the Configuration Object
Querying the parent object through MML

2. Enter the command QUERY:MOC="Ss7",MOI="SubNetwork=1333,MEID=133

3,ConfigSet=1,TransportNetwork=1,Ss7=1"; to query the managed object.
End of Steps
2.1.3 Querying the Referring Object of a Configuration Object

This procedure takes the referring object Signalling Linkset (Sls) of the configuration
object Mtp3 Route (Mtp3Route) as an example to describe how to query the referring
object through the alarm object information.
2-6
SJ-20140527134643-015|2015-03-31 (R1.1)
Key information of the alarm object:

l
l
l
MOC=M3UAROUTE
Alarm object DN=TransportNetwork=1,Ss7=1,M3uaRoute=1
Subnet and NE information: SubNetwork=1333,MEID=1333
data is as follows:
SubNetwork=1333,MEID=1333,ConfigSet=1,TransportNetwork=1,Ss7=1,Mtp3Route=1
Steps
l
Querying the referring object through the GUI

Figure 2-11 Selecting the Snapshot Area Node
2. In the search box, enter the object type name Mtp3 Route, and click
Figure 2-12.
, See
2-7
SJ-20140527134643-015|2015-03-31 (R1.1)
The Mtp3 Route-List tab is displayed in the right pane.

matching condition, like as the matching algorithm, and Mtp3Route=1 as the
matching value, see Figure 2-13.
4. Double-click the configuration object. Its attributes are shown the displayed tab,
see Figure 2-14.
Figure 2-14 Attributes of the Configuration Object
2-8
SJ-20140527134643-015|2015-03-31 (R1.1)
5. Click Used signalling linkset 1.

displayed, see Figure 2-15.
The linked Signalling Linkset-List tab is
Figure 2-15 Locating the Signaling Link Set
Check the information of the signaling link set (Sls).

l
Querying the referring object through the MML

2. Enter the command QUERY:MOC="Mtp3Route",MOI="SubNetwork=1333,ME

ID=1333,ConfigSet=1,TransportNetwork=1,Ss7=1,Mtp3Route=1"; to query the
managed object.
3. Drag the horizontal scroll bar to the right and view the Used signalling linkset 1
information.
4. According to the signaling link group information, enter the command

QUERY:MOC="Sls",MOI="SubNetwork=1333,MEID=1333,ConfigSet=1,Transpo
rtNetwork=1,Ss7=1,LocalSp=1,RemoteSp=1,Sls=1"; to query the referring object.
End of Steps
2-9
SJ-20140527134643-015|2015-03-31 (R1.1)
2.2 Filtering Controller Alarms

In the network management system, specific conditions can be set to filter alarms during
a query of active or historical alarms.
You can query the required alarms by:
l
l
l
Selecting the corresponding board where the alarms are raised directly on the rack
diagram.
Entering the location information of the board where the alarms are raised, including
the rack, shelf, and slot information of the board.
Entering the office information in the alarms.
2.2.1 Checking Board Alarms Through the Rack Diagram

The rack diagram displays the board configuration and the alarms at each severity level
on each slot.
This section describes how to check the board alarms through the rack diagram.
Steps
1. Right-click the faulty NE, and select Open Diagram from the shortcut menu.
The board where the alarm is generated blinks in the color corresponding to the alarm
severity. For details, refer to the following table.
Alarm Color
Severity
Critical
Major
Minor
Warning
2. In the Rank Chart, right-click the faulty board, and select Show Active Alarm from
the shortcut menu, see Figure 2-17.
2-10
SJ-20140527134643-015|2015-03-31 (R1.1)
Figure 2-17 Selecting the Show Active Alarm Command Item
The Show Active Alarm dialog box is displayed.

3. Double-click an alarm, and view the alarm details and handling suggestions.
End of Steps
2.2.2 Filtering Alarms Based on Alarm Location

This procedure takes the Port trunk failed(199007168) alarm as an example to describe
how to filter controller alarms based on the alarm location.
Location: EQRNCID=1,RACKNO=1,SHELFNO=2,SLOTNO=18,CPUNO=1.
Steps
l
Querying alarms through the GUI

1. On the Location tab, select the NE Type of the controller, see Figure 2-18.
Figure 2-18 Selecting the NE Type
2-11
SJ-20140527134643-015|2015-03-31 (R1.1)
2. Select the board where the alarm is generated, see Figure 2-19.
Figure 2-19 Selecting the Board
3. Switch to the Alarm Code tab, and select Port trunk failed(199007168), see
Figure 2-20.
Figure 2-20 Selecting the Alarm Code
4. Click OK. The query result is displayed, see Figure 2-21.

Figure 2-21 Alarm Query Result
Querying alarms through MML
2-12
SJ-20140527134643-015|2015-03-31 (R1.1)
1. In the navigation tree of the MML Terminal, select Fault Management > Show
Active Alarm, see Figure 2-22.
2. Enter the command SHOW CURRENT ALARM:POSITION="urop:OMMOID=hn

fwvxgt-1@sbn=4@me=4",ALARMCODE="199007168",ISVISIBLE=TRUE,SYST
EMTYPE=20421,SUBPOSITION1="EQRNCID=1,RACKNO=1,SHELFNO=2,SL
OTNO=18,CPUNO=1"; to query the current alarms.
End of Steps
2.2.3 Querying Alarms by Office Information

The information of an office includes Site Name (Office) and Site ID (Office).
This procedure describes how to query alarms in accordance with the information of an
office, for example, Site ID (Office): 3005.
Context
If the office information is available in the alarm details, you can view the office information
by either of the following two methods:
l
Alarm list
The office information is available in the corresponding columns in the alarm list, see
the following figure:
2-13
SJ-20140527134643-015|2015-03-31 (R1.1)
Additional information
The office information is available in the Additional Information area on the Detail
tab, see the following figure:
Steps
l
Fuzzy query
1. On the Others tab, select Remark(Fuzzy Match), and enter 3005 in the text box,
see Figure 2-23.
2-14
SJ-20140527134643-015|2015-03-31 (R1.1)
Figure 2-23 Entering the Office Information for Alarm Query
2. Click OK. The queried alarm is displayed on the query result tab, see Figure 2-24.
Figure 2-24 Query Result
Advanced query
1. On the Others tab, click Advanced. The Advanced dialog box is displayed.
2. On the Additional Information tab, enter 3005 in the Site ID(Office) text box,
see Figure 2-25.
Figure 2-25 Entering the Site ID
3. Click OK. The queried alarm is displayed on the query result tab, see Figure 2-24.
End of Steps
2-15
SJ-20140527134643-015|2015-03-31 (R1.1)
2-16
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3
Alarms
Table of Contents
Equipment Alarm........................................................................................................3-1
Processing error Alarm...........................................................................................3-407
Communications Alarm ..........................................................................................3-427
Qos Alarm ..............................................................................................................3-477
3.1 Equipment Alarm

3.1.1 199026127 Clock reference source lost (Level 3 alarm)
Alarm Information
l
l
l
l
Alarm code: 199026127

Name: Clock reference source lost (Level 3 alarm)
Alarm severity: Minor
Alarm type: Equipment Alarm
Alarm Description
This alarm is raised if the clock reference source is lost for less than 10 minutes
Alarm Cause
l
The input clock information is abnormal.
The clock reference is not configured correctly.
Impact
When all configured references are lost, the clock board enters free operating status or Hold status,
and the output clock accuracy is determined by the clock board crystal oscillator. This fault has
no impact on services.
Action
3-1
SJ-20140527134643-015|2015-03-31 (R1.1)
1. Check whether "Type of the lost reference" in the alarm information is consistent with the
requirement.
Yes -> Step 3.
No -> Step 2.
2. In accordance with the physical position of the board, check the "Master Shelf Flag (IsMastFlag)"
parameter of the "Shelf (Shelf)" object. If the board is in a main shelf, modify the clock reference
configuration as required in "Independent Board Configuration Online". Check whether the
alarm is cleared.
Yes -> End.
No -> Step 3.
3. Check whether the clock reference is extracted by the line in accordance with the clock
networking requirement.
Yes -> Step 4.
No -> Step 19.
4. Check whether the connection line from the clock extraction board to the clock board is correct.
Yes -> Step 6.
No -> Step 5.
5. Connect the clock extraction board to the clock board with a good cable. Check whether the
alarm is cleared.
Yes -> End.
No -> Step 6.
6. Verify the type of the interface that extracts the clock according to the clock networking
requirement.
Trunk -> Step 7.
SDH port -> Step 11.
Ethernet port -> Step 15.
Not determined -> Step 23.
7. Check whether the trunk parameter "E1 timer fetch" or "T1 timer fetch flag" is "Timer fetch".
Yes -> Step 8.
No -> Step 23.
8. Configure the clock extraction function for the trunk, and then check whether the alarm is cleared.
Yes -> End.
No -> Step 9.
9. Check whether the trunk that extracts clock has the following alarms:
199000512 Trunk loss of frame
199000513 Trunk loss of signal
Yes -> Step 10.
No -> Step 23.
10. Handle the above alarm, and check whether the alarm is cleared.
Yes -> End.
No -> Step 23.
11. Check whether the SDH port parameter "Whether distill clock from working port" is "Distill clock".
Yes -> Step 12.
No -> Step 23.
3-2
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
12. Configure the clock extraction function for the SDH port, and then check whether the alarm
is cleared.
Yes -> End.
No -> Step 12.
13. Check whether the SDH port has the following alarms:
199001792 SDH/SONET:Loss of signal
199001793 SDH/SONET:Loss of frame
Yes -> Step 14.
No -> Step 23.
Yes -> End.
No -> Step 23.
15. Check whether the "Distill Clock Flag(ClockSource)" parameter of the Ethernet port is "Distill
clock".
Yes -> Step 16.
No -> Step 23.
16. Configure the clock extraction function for the Ethernet port, and then check whether the alarm
is cleared.
Yes -> End.
No -> Step 17.
17. Check whether the Ethernet port has the following alarms:
199005672 Clock source for SyncE is not available
199005760 Ethernet port's link is down
199005718 Two master clock ports is directly connected
Yes -> Step 18.
No -> Step 23.
Yes -> End.
No -> Step 23.
19. If an external independent clock reference provides the clock, check whether the connecting
line is correct.
Yes -> Step 21.
No -> Step 20.
20. Correct the connecting line, and check whether the alarm is cleared.
Yes -> End.
No -> Step 21.
21. Contact the maintenance personnel to check whether the clock source operates properly.
Yes -> Step 22.
No -> Step 23.
22. Eliminate the external clock source fault, and check whether the alarm is cleared.
Yes -> End.
No -> Step 23.
23. Contact the next level of maintenance support.
3-3
SJ-20140527134643-015|2015-03-31 (R1.1)

Alarm Information
l
l
l
l

Alarm severity: Major
Alarm Description
This alarm is raised if the clock reference source is lost for more than 10 minutes and less than
24 hours.
Alarm Cause
l
Impact
and the output clock accuracy is determined by the clock board crystal oscillator. This fault may
have no impact on services.
Action
requirement.
Yes -> Step 3.
No -> Step 2.
alarm is cleared.
Yes -> End.
No -> Step 3.
Yes -> Step 4.
No -> Step 19.
Yes -> Step 6.
No -> Step 5.
alarm is cleared.
Yes -> End.
3-4
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
No -> Step 6.
requirement.
If the interface is a trunk -> Step 7.
If the interface is an SDH port -> Step 11.
If the interface is an Ethernet port -> Step 15.
If the interface type cannot be determined -> Step 23.
7. Check whether the "E1 timer fetch(TimeFetchFlag)" or "T1 timer fetch flag(TimeFetchFlag)"
parameter of the related trunk is "Timer fetch".
Yes -> Step 8.
No -> Step 23.
Yes -> End.
No -> Step 9.
Yes -> Step 10.
No -> Step 23.
10. Handle the above alarms, and check whether the alarm is cleared.
Yes -> End.
No -> Step 23.
11. Check whether the "Whether distill clock from working port(WPortDistillClock)" parameter of the
SDH port is "Distill clock".
Yes -> Step 12.
No -> Step 23.
is cleared.
Yes -> End.
No -> Step 12.
Yes -> Step 14.
No -> Step 23.
Yes -> End.
No -> Step 23.
15. Check whether the "Distill Clock Flag(ClockSource)" parameter of the Ethernet port.
Yes -> Step 16.
No -> Step 23.
is cleared.
Yes -> End.
3-5
SJ-20140527134643-015|2015-03-31 (R1.1)
No -> Step 17.

17. Check whether the following alarms exist on the Ethernet port:
Yes -> Step 18.
No -> Step 23.
Yes -> End.
No -> Step 23.
line is correct.
Yes -> Step 21.
No -> Step 20.
Yes -> End.
No -> Step 21.
Yes -> Step 22.
No -> Step 23.
22. Resolve the external clock source fault, and check whether the alarm is cleared.
Yes -> End.
No -> Step 23.

Alarm Information
l
l
l
l

Alarm severity: Critical
Alarm Description
This alarm is raised if the clock reference source is lost for more than 24 hours.
Alarm Cause
l
3-6
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Impact
and the output clock accuracy is determined by the clock board crystal oscillator. This fault may
have no impact on services.
Action
requirement.
Yes -> Step 3.
No -> Step 2.
alarm is cleared.
Yes -> End.
No -> Step 3.
Yes -> Step 4.
No -> Step 19.
Yes -> Step 6.
No -> Step 5.
alarm is cleared.
Yes -> End.
No -> Step 6.
requirement.
If the interface is a trunk -> Step 7.
If the interface is an SDH port -> Step 11.
If the interface is an Ethernet port -> Step 15.
If the interface type cannot be determined -> Step 23.
7. Check whether the "E1 timer fetch(TimeFetchFlag)" or "T1 timer fetch flag(TimeFetchFlag)"
parameter of the related trunk is "Timer fetch".
Yes -> Step 8.
No -> Step 23.
Yes -> End.
No -> Step 9.
Yes -> Step 10.
3-7
SJ-20140527134643-015|2015-03-31 (R1.1)
No -> Step 23.

Yes -> End.
No -> Step 23.
11. Check whether the "Whether distill clock from working port(WPortDistillClock)" parameter of the
SDH port is "Distill clock".
Yes -> Step 12.
No -> Step 23.
is cleared.
Yes -> End.
No -> Step 12.
Yes -> Step 14.
No -> Step 23.
Yes -> End.
No -> Step 23.
15. Check whether the "Distill Clock Flag (ClockSource)" parameter of the Ethernet port is "Distill
clock".
Yes -> Step 16.
No -> Step 23.
is cleared.
Yes -> End.
No -> Step 17.
17. Check whether the Ethernet port has the following alarms:
Yes -> Step 18.
No -> Step 23.
Yes -> End.
No -> Step 23.
line is correct.
Yes -> Step 21.
No -> Step 20.
Yes -> End.
No -> Step 21.
3-8
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Yes -> Step 22.

No -> Step 23.
22. Resolve the external clock source fault, and check whether the alarm is cleared.
Yes -> End.
No -> Step 23.
3.1.4 199026133 Output clock of the board is lost

Alarm Information
l
l
l
l

Name: Output clock of the board is lost
Alarm Description
This alarm is raised if the board detects that the output clock is unavailable.
Alarm Cause
The hardware is faulty.
Impact
The system clock cannot be synchronized and services may be interrupted.
Action
1. Replace the faulty board with an operational one(refer to Front Boards and Rear Boards
Replacement), and check whether the alarm is cleared.
Yes -> End.
No -> Step 2.
3.1.5 199000170 The switch board occurred loopback port

Alarm Information
Code:
199000170
Name:
The switch board occurred loopback port
3-9
SJ-20140527134643-015|2015-03-31 (R1.1)
Severity:
Major
Type:
Equipment Alarm
Alarm Description
This alarm is raised if the local port receives a loop message sent from itself.
Probable Cause
l
The cascading network in the shelf has a loop.
The switch that is connected to the debugging interface of this board has a loop.
The internal switching network of the shelf corresponding to the board has a loop.
System Impact
This port will be blocked by the system automatically, messages on the port will be discarded, and
services may be interrupted.
Handling Suggestion
1. Check whether the "Use Type" parameter in the alarm information is set to "In shelf".
Yes -> Step 8.
No -> Step 2.
2. Check whether the debug port on the switching board is plugged with a network cable.
The EGBS/EGBS_2 board uses the ETH-M port as the debug port.
Yes -> Step 3.
No -> Step 6.
3. Remove the network cable, wait for two minutes, and then check whether the alarm is cleared.
Yes -> Step 4.
No -> Step 6.
4. Replug the network cable to the debug port on the switching board. Contact the maintenance
personnel of the peer device to check whether the peer device has related loop alarms.
Yes -> Step 5.
No -> Step 8.
5. Contact the maintenance personnel of the peer device to resolve the fault, and check whether
the alarm is cleared.
Yes -> End.
No -> Step 8.
6. Replug the network cable to the debug port on the switching board. Check whether the switching
boards between shelves are connected as required.
Yes -> Step 8.
No -> Step 7.
7. Connect the cables as required, wait for two minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 8.
3-10
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.6 199000256 OMC port's link is down

Alarm Information
l
l
l
l

Name: OMC port's link is down
Alarm severity: Warning
Alarm Description
This alarm is raised if the board detects that the link of the OMC port is disconnected.
Alarm Cause
l
The OMC network interface is not connected or the cable connection of the OMC network
interface is incorrect.
The OMC network interface of the board is faulty.
The peer port is faulty.
The switching boards in the same shelf of the board are faulty.
Impact
l
If the board is in active status, the network management system cannot manage NEs.
If the board is in standby status, this alarm does not affect the system, but the reliability of the
system is reduced.
Action
1. Query the OMM mode configured for the CMM board in the same shelf as the board, and
determine whether the OMM mode is external OMM (for the controller, it is fixed to built-in OMM).
Yes -> Step 2.
No -> Step 3.
2. Check whether the OMC port of the faulty board has a problem with the cable connection.
Yes -> Step 4.
No -> Step 6.
3. Check whether the control-plane switching board in the same shelf in the rack diagram operates
improperly.
Yes -> Step 5.
No -> Step 8.
4. Replace the cable, and check whether the alarm is cleared.
Yes -> End.
No -> Step 6.
5. Handle the fault related to the switching board, and check whether the alarm is cleared.
Yes -> End.
No -> Step 6.
3-11
SJ-20140527134643-015|2015-03-31 (R1.1)
6. Check whether the peer device connected to the port is normal.

Yes -> Step 8.
No -> Step 7.
7. Resolve the fault of the peer device, and check whether the alarm is cleared.
Yes -> End.
No -> Step 8.
3.1.7 199000512 Trunk loss of frame

Alarm Information
l
l
l
l

Name: Trunk loss of frame
Alarm Description
This alarm is raised if the trunk (E1/T1) frame is lost due to unsynchronized signals.
Alarm Cause
l
The local end or the peer end is not properly grounded.
A transmission device is faulty.
The receiving impedance does not match the cable type.
The E1/T1 chip hardware is faulty.
The frame format of the local end is different from that of the peer end.
Impact
All services on this trunk are interrupted.
Action
1. Check whether the board has any of the following alarms in accordance with "Rack number",
"Shelf number", "Slot number", and "CPU number" in the alarm information.
199001286 Input clock of the board is lost
199005796 Clock of this board is abnormal
Yes -> Step 2.
No -> Step 3.
2. Handle the related alarms, and check whether this alarm is cleared.
Yes -> End.
No -> Step 3.
3-12
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3. Query the trunk E1/T1 object in accordance with the alarm object and query the E1/T1 port
configuration. Contact the maintenance personnel of the peer end to check whether the format
of the E1 frame on the local end is the same as that on the peer end, or whether the format of
the T1 frame and the encoding format of the T1 link on the local end are the same as those
on the peer end.
Yes -> Step 5.
No -> Step 4.
4. Modify the local E1/T1 port configuration or request the maintenance personnel of the peer end
to modify the peer-end configuration so that E1/T1 port attributes are the same on both ends.
Wait for three minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 5.
5. Search for the specific port of the board in accordance with "Rack number", "Shelf number", "Slot
number", "Primary device index" (the primary device index is the optical port number if the board
uses the optical port trunk), and "Secondary device index" (the secondary device index is the
trunk number if the board uses the electrical interface trunk) in the alarm information, and then
check whether the cable connection of the faulty E1/T1 port is correct.
Yes -> Step 7.
No -> Step 6.
6. Adjust the cable connection as required and then check whether the alarm is cleared.
Yes -> End.
No -> Step 7.
7. Check whether the cable or connector is damaged.
Yes -> Step 8.
No -> Step 9.
Yes -> End.
No -> Step 9.
9. Check whether the protective grounding wires of the interconnected devices are connected
properly. Properly connect the protective grounding wires for both ends if the grounding is poor or
wrong, and then check whether the alarm is cleared.
Yes -> End.
No -> Step 10.
10. Check whether the board is an ASPB board in accordance with "Board type" in the alarm
information.
Yes -> Step 11.
No -> Step 13.
11. Remove the board (refer to Removing a Board) and check whether the DIP switch of the board
and the jumper of the rear board are consistent with the cable type.
Yes -> Step 15.
No -> Step 14.
12. Adjust the DIP switch of the board and the jumper of the rear board to be consistent with the
cable type, and then check whether the alarm is cleared.
Yes -> End.
No -> Step 15.
3-13
SJ-20140527134643-015|2015-03-31 (R1.1)
13. Query "E1 Impedance" or "T1 Impedance". Remove the board (refer to Removing a Board)
and check whether the DIP switch of the board and the trunk impedance are consistent with
the cable type.
Yes -> Step 15.
No -> Step 14.
14. Adjust the DIP switch and the impedance of the trunk to ensure that they are consistent with the
Yes -> End.
No -> Step 15.
15. [A2003] Run the START DTM command to perform a local loopback test on the trunk in
accordance with the alarm object and "Rack number", "Shelf number", "Slot number", "CPU
number", "Primary device index", and "Secondary device index" in the alarm information, wait for
about one minute, and then check whether the alarm is cleared and cancel the loopback test.
Yes -> Step 17.
No -> Step 16.
16. Replace the board(refer to Front Boards and Rear Boards Replacement), wait for a maximum
of 10 minutes, and then check whether the alarm is cleared.
Yes -> End.
No -> Step 17.
3.1.8 199000513 Trunk loss of signal

Alarm Information
l
l
l
l

Name: Trunk loss of signal
Alarm Description
This alarm is raised when the board cannot detect signals input from the trunk port.
Alarm Cause
l
The E1 line is not connected or connected incorrectly to the DDF.
The E1 line is damaged or the connector of the E1 line is in poor contact.
The peer transmission device is faulty.
Impact
3-14
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Action
1. Search for the faulty port in accordance with the rack number, shelf number, slot number, primary
device index (optical port index), and the secondary device index (E1/T1 port index) in the alarm
information, and then check whether the cable connection of the faulty E1/T1 port is correct.
Yes -> Step 3.
No -> Step 2.
Yes -> End.
No -> Step 3.
Yes -> Step 4.
No -> Step 5.
Yes -> End.
No -> Step 5.
Yes -> Step 7.
No -> Step 6.
6. Replace the faulty board(refer to Front Boards and Rear Boards Replacement), or replace the
rear board on the faulty board, wait for a maximum of 10 minutes, and then check whether
Yes -> End.
No -> Step 7.
3.1.9 199000514 Trunk alarm indication signal

Alarm Information
l
l
l
l

Name: Trunk alarm indication signal
Alarm Description
This alarm is raised if the board detects that the signals received by the trunk port are all 1.
3-15
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Cause
l
The peer device is faulty.
The E1/T1 chip hardware of this board is faulty.
Impact
Action
1. Contact the maintenance personnel of the peer end to check whether the peer device has
related alarms.
Yes -> Step 2.
No -> Step 3.
2. After the maintenance personnel of the peer end handles the alarms, check whether the alarm
is cleared.
Yes -> End.
No -> Step 3.
Yes -> Step 5.
No -> Step 4.
4. Replace the faulty board(refer to Front Boards and Rear Boards Replacement). Wait for ten
minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 5.
3.1.10 199000515 Trunk loss of CRC multi-frame

Alarm Information
l
l
l
l

Name: Trunk loss of CRC multi-frame
Alarm Description
This alarm is raised if the trunk (E1/T1) multiframe is lost due to unsynchronized CRC multiframe
signals.
3-16
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
l
The local E1/T1 chip hardware is faulty.
The frame format of the local end is different from that of the peer end.
Impact
Action
on the peer end.
Yes -> Step 3.
No -> Step 2.
Check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3. Contact the maintenance personnel for the transmission network to check whether the
transmission network is faulty.
Yes -> Step 4.
No -> Step 5.
4. Ask the maintenance personnel for the transmission network to resolve the fault of the
transmission network, and check whether the alarm is cleared.
Yes -> End.
No -> Step 5.
5. Check whether the cable connection of the faulty E1/T1 port is correct in accordance with "Rack
number", "Shelf number", "Primary device index" (optical port number), and "Secondary device
index" (E1/T1 port number) in the alarm information.
Yes -> Step 7.
No -> Step 6.
Yes -> End.
No -> Step 7.
Yes -> Step 8.
No -> Step 9.
3-17
SJ-20140527134643-015|2015-03-31 (R1.1)
Yes -> End.

No -> Step 9.
Yes -> End.
No -> Step 10.
information.
Yes -> Step 11.
No -> Step 13.
11. Remove the board (refer to Removing a Board) and check whether the DIP switch of the board
and the jumper of the rear board are consistent with the cable type.
Yes -> Step 15.
No -> Step 12.
Yes -> End.
No -> Step 15.
13. Query "E1 Impedance" or "T1 Impedance". Remove the board (refer to Removing a Board)
and check whether the DIP switch of the board and the trunk impedance are consistent with
the cable type.
Yes -> Step 15.
No -> Step 14.
Yes -> End.
No -> Step 15.
Yes -> Step 17.
No -> Step 16.
16. Replace the faulty board(refer to Front Boards and Rear Boards Replacement), wait for 10
Yes -> End.
No -> Step 17.
3-18
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.11 199000517 Trunk remote alarm indication

Alarm Information
l
l
l
l

Name: Trunk remote alarm indication
Alarm Description
This alarm is raised if the board detects that the trunk port receives "Remote Alarm Indication"
from the peer end.
Alarm Cause
l
An error occurs when the local end sends a signal.
An intermediate transmission device is faulty.
Impact
Action
1. Contact the peer maintenance personnel to check whether the peer device has related fault.
Yes -> Step 2.
No -> Step 3.
2. Ask the maintenance personnel of the peer end to resolve the fault, and check whether the
alarm is cleared.
Yes -> End.
No -> Step 3.
Yes -> Step 5.
No -> Step 4.
Yes -> End.
No -> Step 5.
3-19
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.12 199000518 Trunk link is used for CSU loopback test

Alarm Information
l
l
l
l

Name: Trunk link is used for CSU loopback test
Alarm Description
This alarm is raised if the board detects that the trunk link performs the CSU loopback test.
Alarm Cause
The CSU loopback test is set for the trunk link manually.
Impact
The trunk link is blocked, so services cannot be carried on this link.
Action
1. [A2014]Run the START DTM command to cancel the CSU loopback in accordance with the
alarm object and "Rack number", "Shelf number", "Slot number", "CPU number", "Primary
device index", and "Secondary device index" in the alarm information, and then check whether
Yes -> End.
No -> Step 2.
3.1.13 199001024 ATM cell delineation not synchronized

Alarm Information
l
l
l
l

Name: ATM cell delineation not synchronized
Alarm Description
This alarm is raised if the ATM cell delineation is not synchronized.
3-20
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
l
l
The optical transmission device of the peer end is faulty.

The optical fiber transmission link is faulty, so the header HEC of the cell is damaged. As a result,
the cell cannot be located from the frame in the physical layer.
The local optical receiver is faulty.
The header HEC of the cell is processed differently by the local and peer devices.
Impact
The ATM communication may be abnormal.
Action
1. [A2001] Run the START DTM command to perform a system loopback test on the SDH optical
port in accordance with the alarm object and the "Rack number", "Shelf number", "Slot number",
"CPU number", and "Optical port index" in the alarm information, wait for one minute, and then
check whether the alarm is cleared.
Yes -> [A2002] Run the START DTM command to cancel the loopback test on the SDH optical
"CPU number", and "Optical port index" in the alarm information, and go to Step 2.
No -> Step 12.
2. Check whether the faulty port has any of the following alarms in accordance with the "Rack
number", "Shelf number", Slot number", "CPU number", and "Optical port index" in the alarm
information.
199001795 SDH/SONET:MS alarm indication signal/Line alarm indication signal
199001800 SDH/SONET:AU alarm indication signal/Path alarm indication signal
199001802 SDH/SONET:HP unequipped/Path unequipped
Yes -> Step 3.
No -> Step 4.
Yes -> End.
No -> Step 4.
4. Check whether the board has any of following alarms in accordance with the "Rack number",
199005768 All of the board input clocks which have the same frequency are lost
Yes -> Step 5.
No -> Step 6.
Yes -> End.
No -> Step 6.
3-21
SJ-20140527134643-015|2015-03-31 (R1.1)
6. Query the "Board (Board)" parent object in accordance with the alarm object, and check whether
the "Port Type(ExtPortType)" and "SDH speed mode(SdhPortMuxMode)" parameters are
consistent with those of the peer end.
Yes -> Step 8.
No -> Step 7.
7. Modify the configuration of the local end as required, or ask the maintenance personnel of the
peer device to modify the configuration to ensure the configuration of the local end is consistent
with that of the peer end. Wait for one minute, and check whether the alarm is cleared.
Yes -> End.
No -> Step 8.
8. Perform the self-loop operation on the faulty port through the optical fibers (on the ODF frame),
and then check whether the alarm is cleared.
Yes -> Step 10.
No -> Step 9.
9. Replace the old optical fiber with a new one, and then check whether the alarm is cleared.
Yes -> End.
No -> Step 10.
10. Contact the maintenance personnel of the peer device to check whether the peer device has
related alarms of the interconnected port.
Yes -> Step 11.
No -> Step 13.
11. Check whether the alarm is cleared after the fault on the peer device is resolved.
Yes -> End.
No -> Step 13.
12. Replace the board(refer to Front Boards and Rear Boards Replacement), and check whether
Yes -> End.
No -> Step 2.
3.1.14 199001025 Loss of ATM cell delineation

Alarm Information
l
l
l
l

Name: Loss of ATM cell delineation
Alarm Description
This alarm is raised if the ATM cell delineation fails to be synchronized for a certain period.
3-22
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
l
l

Impact
The ATM communication may be disconnected.
Action
No -> Step 12.
information.
199001025 Loss of ATM cell delineation
Yes -> Step 3.
No -> Step 4.
Yes -> End.
No -> Step 4.
Yes -> Step 5.
No -> Step 6.
Yes -> End.
No -> Step 6.
3-23
SJ-20140527134643-015|2015-03-31 (R1.1)
6. Query the "Board (Board)" parent object in accordance with the alarm object, and check whether
the "Port Type(ExtPortType)" and "SDH speed mode(SdhPortMuxMode)" parameters are
consistent with those of the peer end.
Yes -> Step 8.
No -> Step 7.
7. Modify the configuration of the local end as required, or ask the maintenance personnel of the
peer device to modify the configuration to ensure the configuration of the local end is consistent
with that of the peer end. Wait for one minute, and check whether the alarm is cleared.
Yes -> End.
No -> Step 8.
Yes -> Step 10.
No -> Step 9.
Yes -> End.
No -> Step 10.
Yes -> Step 11.
No -> Step 13.
Yes -> End.
No -> Step 13.
Yes -> End.
No -> Step 2.
3.1.15 199001026 ATM cell delineation do not synchronization

about cell on E1/T1 link
Alarm Information
l
l
l
l

Name: ATM cell delineation do not synchronization about cell on E1/T1 link
Alarm Description
Cell delineation do not synchronization about cell on E1/T1 link.
3-24
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
l
l

Impact
Data reception is failure and signaling link is down.
Action
1. [A2013]Query the trunk E1/T1 object in accordance with "Subsystem ID", "Unit Number", "TC
Index", and "CPU Index" in the alarm information, and run the START DTM command to perform
a local loopback test on the trunk. Wait for one minute, and check whether the alarm is cleared.
Yes -> Cancel the local loopback and go to Step 2.
No -> Step 5.
2. Query the ATM port object in accordance with "Subsystem ID", "Unit Number", "TC Index",
and "CPU Index" in the alarm information, and check whether the scrambling modes are the
same on both ends.
Yes -> Step 4.
No -> Step 3.
3. If required, modify the scrambling mode of the local end, or ask the maintenance personnel of
the peer end to modify the scrambling mode on the peer end, wait for one minute, and then
Yes -> End.
No -> Step 4.
4. Run the SET NORMALRESET command to reset the board in accordance with "Rack number",
"Shelf number", "Slot number", and "CPU number" in the alarm information. Wait for five minutes,
and check whether the alarm is cleared.
Yes -> End.
No -> Step 5.
5. Replace the board(refer to Front Boards and Rear Boards Replacement), wait for five minutes,
Yes -> End.
No -> Step 6.
3.1.16 199001286 Input clock of the board is lost

Alarm Information
l

3-25
SJ-20140527134643-015|2015-03-31 (R1.1)
l
l
l
Name: Input clock of the board is lost

Alarm Description
This alarm is raised if the board detects that the input clock is lost.
Alarm Cause
l
The clock line is not connected.
The clock output source operates improperly.
The hardware of the clock module of the board is faulty.
Impact
Services on the board may be affected.
Action
1. Check whether the boards in Slots 21 and 22 of the shelf are clock boards in accordance with the
"Rack number" and "Shelf number" in the alarm information.
Yes -> Step 2.
No -> Step 10.
2. Check whether an alarm is raised on the upper-level clock board.
Yes -> Step 3.
No -> Step 4.
3. Handle the alarm raised on the upper-level clock board, and check whether the alarm is cleared.
Yes -> End.
No -> Step 4.
4.
In the Independent Board Configuration Online window, check whether the upper-level
clock shelf is configured as the master shelf.
Yes -> Step 8.
No -> Step 5.
5. Modify the configuration of the upper-level clock shelf in accordance with the actual clock
networking requirements. If it is configured as the master shelf, the clock reference configuration
should be added. Check whether the alarm is cleared.
Yes -> End.
No -> Step 6.
6. Check whether the following alarms are raised on the upper-level clock board:
199001285 Clock chip is in preheat status
199005405 Clock board phase-lock loop work mode is abnormal
199026133 Output clock of the board is lost
Yes -> Step 7.
3-26
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
No -> Step 8.
Yes -> End.
No -> Step 8.
8. Check whether the cables for the clock network are connected as required. (Refer to Installing
Clock Cables.)
Yes -> Step 16.
No -> Step 9.
9. Connect the cables in accordance with the inter-shelf clock networking requirements, and check
whether the alarm is cleared.
Yes -> End.
No -> Step 16.
10. Check whether the clock board in the shelf is powered on successfully. (Refer to EGFS Rear
Board
Yes -> Step 12.
No -> Step 11.
11. Power on the clock board, and check whether the alarm is cleared.
Yes -> End.
No -> Step 12.
12. Check whether the clock shelf configuration is correct.
Yes -> Step 14.
No -> Step 13.
13. In the Independent Board Configuration Online window, check whether the clock reference is
configured for the master shelf. If not, configure it, and check whether the alarm is cleared.
Yes -> End.
No -> Step 14.
14. Check whether the following alarms are raised on the clock board of the shelf:
Yes -> Step 15.
No -> Step 16.
Yes -> End.
No -> Step 16.
3.1.17 199001792 SDH/SONET:Loss of signal

Alarm Information
l

3-27
SJ-20140527134643-015|2015-03-31 (R1.1)
l
l
l
Name: SDH/SONET:Loss of signal

Alarm Description
This alarm is raised if the system fails to detect that the optical port receives a signal.
Alarm Cause
l
The optical transmission line is faulty.
The optical power exceeds the range supported by the optical module.
Impact
l
All the trunk receiving signals transmitted through the SDH/SONET channel are interrupted, and
the corresponding services are also interrupted.
When a LOS alarm is raised, the board sends MS-RDI to the peer end.
Action
No -> Step 11.
information.
199005793 RX Power High Alarm
199005794 RX Power Low Alarm
Yes -> Step 3.
No -> Step 4.
Yes -> End.
No -> Step 4.
4. 4. [A2009] Run the START DTM command to perform a diagnostic test on the board in
accordance with the "Rack number", "Shelf number", "Slot number" and "CPU number" in the
alarm information, and then check whether the rate, wavelength, multimode, and single-mode of
the optical module of the local end are consistent with those of the peer end.
Yes -> Step 6.
3-28
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
No -> Step 5.
5. Replace the optical module (refer to Replacing an Optical Module) as required, or ask the
maintenance personnel of the peer device to replace the optical module, and then check whether
Yes -> End.
No -> Step 6.
6. Clean the optical fiber connector of the port, and then unplug and plug the optical fiber. Ensure
the optical fiber connection is normal (avoid mistaking the sending port for receiving port, and
vice versa). Check whether the alarm is cleared.
Yes -> End.
No -> Step 7.
Yes -> Step 9.
No -> Step 8.
Yes -> End.
No -> Step 9.
Yes -> Step 10.
No -> Step 12.
Yes -> End.
No -> Step 12.
Yes -> End.
No -> Step 2.
3.1.18 199001793 SDH/SONET:Loss of frame

Alarm Information
l
l
l
l

Name: SDH/SONET:Loss of frame
Alarm Description
This alarm is raised if the port cannot correctly receive A1A2 frame locating signals continuously.
3-29
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Cause
l
The optical transmission device of the peer end is faulty, and therefore the signal does not
have a frame structure.
The signal is attenuated greatly because of the optical transmission line.
The local clock is abnormal.
Impact
l
When this alarm is raised, the board transmits MS-RDI to the peer end.
Action
1. 1. [A2001] Run the START DTM command to perform a system loopback test on the SDH
optical port in accordance with the alarm object and the "Rack number", "Shelf number", "Slot
number", "CPU number", and "Optical port index" in the alarm information, wait for one minute,
No -> Step 10.
information.
Yes -> Step 3.
No -> Step 4.
Yes -> End.
No -> Step 4.
Yes -> Step 5.
No -> Step 6.
Yes -> End.
No -> Step 6.
Yes -> Step 8.
3-30
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
No -> Step 7.
Yes -> End.
No -> Step 8.
Yes -> Step 9.
No -> Step 11.
Yes -> End.
No -> Step 11.
Yes -> End.
No -> Step 2.
3.1.19 199001794 SDH/SONET:Regenerator section trace

mismatch/Section trace mismatch
Alarm Information
l
l
l
l

Name: SDH/SONET:Regenerator section trace mismatch/Section trace mismatch
Alarm Description
This alarm is raised if "Section Access Point Identifier" received by the board is not the same as
expected.
Alarm Cause
l
The optical fibers on the optical distribution frame are connected incorrectly during the cutover
and scheduling of the optical fibers.
The expected value is not configured correctly.
Optical signals are lost.
Impact
l
The corresponding relationships of all trunk signals are incorrect, which does not affect services.
3-31
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
1. [A2012] Run the START DTM command, read SDH values of the SDH optical port, and query
the J0 receiving value, expected value, and sending value of the faulty optical port in accordance
with the alarm object and the "Rack number", "Shelf number", "Slot number", "CPU number",
and "Optical port index" in the alarm information, and check whether the receiving value is
consistent with the expected value.
Yes -> Step 3.
No -> Step 2.
2. Query the "STM-1 Physical Port (S155Port)" object in accordance with the alarm object, and
change the value of the "J0 Trail Identifier Message(J0)" parameter to the receiving value in Step
1, or ask the maintenance personnel of the peer device to modify the configuration. Wait for one
minute, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
information.
Yes -> Step 4.
No -> Step 5.
Yes -> End.
No -> Step 5.
5. Check whether there is a problem with the optical fiber connection of the ODFs at the local
and peer ends.
Yes -> Step 6.
No -> Step 7.
6. Correct the optical fiber connection, and check whether the alarm is cleared.
Yes -> End.
No -> Step 7.
3.1.20 199001795 SDH/SONET:MS alarm indication signal/Line

alarm indication signal
Alarm Information
l
l
l
l

Name: SDH/SONET:MS alarm indication signal/Line alarm indication signal
3-32
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Description
This alarm is raised if the board detects that an upstream device is faulty when it operates as a
network node (for example, a generator) in a multiplex section.
Alarm Cause
l
The peer end transmits an MS-AIS signal.
The local line is faulty.
The local clock is abnormal.
Impact
l
The signal consisting of only 1 is transmitted to the downlink direction of the SDH multiplex
section.
Action
No -> Step 10.
number", "Shelf number", "Slot number", "CPU number", and "Optical port index" in the alarm
information.
199001794 SDH/SONET:Regenerator section trace mismatch/Section trace mismatch
Yes -> Step 3.
No -> Step 4.
Yes -> End.
No -> Step 4.
3-33
SJ-20140527134643-015|2015-03-31 (R1.1)

Yes -> Step 5.
No -> Step 6.
Yes -> End.
No -> Step 6.
Yes -> Step 8.
No -> Step 7.
Yes -> End.
No -> Step 8.
Yes -> Step 9.
No -> Step 11.
Yes -> End.
No -> Step 11.
Yes -> End.
No -> Step 2.
3.1.21 199001796 SDH/SONET:MS far-end reception failure/Line

far-end reception failure
Alarm Information
l
l
l
l

Name: SDH/SONET:MS far-end reception failure/Line far-end reception failure
Alarm Description
If the peer end detects a fault, for example, MS-AIS, it transmits MS-RDI to the local end. This alarm
is raised if the local end detects MS-RDI in the multiplex section.
3-34
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
l
The peer optical receiver is faulty.
If the peer end detects that signals cannot be received normally, it transmits MS-RDI to the
local end.
Impact
l
If there are no serious faults when this alarm is raised, this alarm does not affect the local end.
All the trunk receiving signals transmitted through the SDH/SONET channel, and the
corresponding services are interrupted if serious faults, for example, MS-AIS, occurred on the
local end.
Action
Yes -> Step 2.
No -> Step 3.
Yes -> End.
No -> Step 3.
information.
Yes -> Step 4.
No -> Step 5.
Yes -> End.
No -> Step 5.
3.1.22 199001797 SDH/SONET:Signal failure

Alarm Information
l
l
l
l

Name: SDH/SONET:Signal failure
3-35
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Description
This alarm is raised if the board detects that the B2 bit error rate in the receiving signals multiplex
section exceeds the preset threshold (default threshold: 1e-3).
Alarm Cause
l
The faulty optical transmission line or the changed transmission mode causes bit error.
The local end hardware is faulty.
The clock of the local end or the peer end is not stable.
Impact
l
When this alarm is raised, the corresponding board inserts an AIS signal in the downlink direction
of the SDH multiplex section, which interrupts all services.
All the trunk receiving signals transmitted through the SDH/SONET channel generate various
alarms.
Action
No -> Step 10.
number", "Shelf number", "Slot number", "CPU number", and "Optical port index" in the alarm
information.
Yes -> Step 3.
No -> Step 4.
Yes -> End.
No -> Step 4.
Yes -> Step 5.
No -> Step 6.
3-36
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Yes -> End.
No -> Step 6.
Yes -> Step 8.
No -> Step 7.
Yes -> End.
No -> Step 8.
Yes -> Step 9.
No -> Step 11.
Yes -> End.
No -> Step 11.
Yes -> End.
No -> Step 2.
3.1.23 199001798 SDH/SONET:Signal deterioration

Alarm Information
l
l
l
l

Name: SDH/SONET:Signal deterioration
Alarm Description
This alarm is raised if the board detects that the B2 bit error rate in the receiving signals multiplex
section exceeds the preset threshold (default threshold: 1e-6).
Alarm Cause
l
The faulty optical transmission line or the changed transmission mode causes bit error.
The local end hardware is faulty.
3-37
SJ-20140527134643-015|2015-03-31 (R1.1)
Impact
l
Some trunk receiving signals generate various alarms.
Some data is lost or bit error exists, which reduces service quality.
Action
No -> Step 8.
information.
199001797 SDH/SONET:Signal failure
Yes -> Step 3.
No -> Step 4.
Yes -> End.
No -> Step 4.
Yes -> Step 6.
No -> Step 5.
Yes -> End.
No -> Step 6.
Yes -> Step 7.
No -> Step 9.
Yes -> End.
No -> Step 9.
Yes -> End.
No -> Step 2.
3-38
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.24 199001799 SDH/SONET:Loss of AU pointer/Loss of path

pointer
Alarm Information
l
l
l
l

Name: SDH/SONET:Loss of AU pointer/Loss of path pointer
Alarm Description
This alarm is raised if the board continuously receives eight invalid AU pointers or eight NDF pointers.
Alarm Cause
l
The clock configuration or network configuration on the local device is different from that on
the peer device.
Other alarms are raised on the local device.
The peer clock or peer device is faulty.
The local clock or local device is faulty.
Impact
l
All the trunk receiving signals transmitted through the SDH/SONET channel are interrupted,
which may affect corresponding services.
When an AU-4 LOP alarm is raised, the board transmits VC-4 RDI to the peer end.
Action
1. Check whether the board has any of the following alarms in accordance with "Rack number",
"Shelf number", and "Slot number" displayed in the alarm information:
Yes -> Step 2.
No -> Step 3.
2. Handle the related alarms, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3. Check whether the local faulty port has any of the following alarm in accordance with "Rack
number", "Shelf number", "Slot number", and "Optical port index" in the alarm information:
Yes -> Step 4.
No -> Step 5.
3-39
SJ-20140527134643-015|2015-03-31 (R1.1)
Yes -> End.

No -> Step 5.
5. [A2017]Run the START DTM command to perform a system loopback test on the SDH optical
port in accordance with the "Rack number", "Shelf number", "Slot number", "CPU number", and
"Optical port index" in the alarm information, and then check whether the alarm is cleared.
Yes -> Step 6.
No -> Step 8.
6. [A2018]Run the START DTM command to cancel the loopback test on the SDH optical port in
accordance with the "Rack number", "Shelf number", "Slot number", "CPU number", and "Optical
port index" in the alarm information. Contact the maintenance personnel of the peer device to
check whether the peer device has related alarms.
Yes -> Step 7.
No -> Step 10.
Yes -> End.
No -> Step 10.
"Shelf number", "Slot number", and "CPU number" in the alarm information, and then check
whether the alarm persists three minutes after the board is powered on successfully.
Yes -> Step 9.
No -> End.
9. Replace the board(refer to Front Boards and Rear Boards Replacement). After the board
operates properly for three minutes, check whether the alarm is cleared.
Yes -> Step 10.
No -> End.
3.1.25 199001800 SDH/SONET:AU alarm indication signal/Path

alarm indication signal
Alarm Information
l
l
l
l

Name: SDH/SONET:AU alarm indication signal/Path alarm indication signal
Alarm Description
This alarm is raised if the board detects that both the VC-4 payload and AU-4 pointers are all 1.
3-40
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
l
The peer device transmits the signal.
The receiving device of the local board is faulty.
Impact
l
When an AU-4 AIS alarm is raised, the board transmits VC-4 RDI to the peer end.
Action
1. Check whether this board has any of the following alarms in accordance with the "Rack number",
"Shelf number", and "Slot number" in the alarm information.
Yes -> Step 2.
No -> Step 3.
2. Handle the alarms, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
port in accordance with the "Rack number", "Shelf number", "Slot number", "CPU number", and
Yes -> Cancel the system loopback test and go to Step 6.
No -> Step 4.
4. Run the SET NORMALRESET command to reset the board in accordance with the "Rack
number", "Shelf number", "Slot number", and "CPU number" in the alarm information, and then
check whether the alarm persists three minutes after the board is powered on successfully.
Yes -> Step 5.
No -> End.
Yes -> Step 6.
No -> End.
6. Contact the maintenance personnel of the peer device to check whether the peer device is faulty.
Yes -> Step 7.
No -> Step 8.
Yes -> End.
No -> Step 8.
8. Contact the maintenance personnel to check whether the transmission device is in good condition.
Yes -> Step 10.
3-41
SJ-20140527134643-015|2015-03-31 (R1.1)
No -> Step 9.
Yes -> End.
No -> Step 10.
3.1.26 199001801 SDH/SONET:HP trace mismatch/ Path trace

mismatch
Alarm Information
l
l
l
l

Name: SDH/SONET:HP trace mismatch/ Path trace mismatch
Alarm Description
This alarm is raised if the VC-4 path entry point ID (J1) received by the board is not consistent with
the expected parameter "High path trail identifier message(J1)" configuration.
Alarm Cause
l
The optical fibers on the optical distribution frame are connected incorrectly during the cutover
and scheduling of the optical fibers.
The J1 configuration on the local end is not consistent with that on the peer end.
The local clock system is faulty.
Impact
l
The correspondences of all trunk signals transmitting through the high-order path are incorrect.
When a VC-4 TIM alarm is raised, the board transmits VC-4 RDI to the peer end.
Action
1. Check whether the board has any of following alarms in accordance with "Rack number", "Shelf
number", "Slot number", and "CPU number" in the alarm information.
Yes -> Step 2.
No -> Step 3.
Yes -> End.
No -> Step 3.
3-42
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3. Query the SDH path object in accordance with the alarm object, and check whether the
configuration of the "High path trail identifier message (J1)" is the same as that of the peer end.
Yes -> Step 7.
No -> Step 4.
4. Check whether the local configuration is wrong.
Yes -> Step 5.
No -> Step 6.
5. Modify the "High path trail identifier message (J1)" parameter. Ensure that the configurations of
this parameter on both ends are the same, and then check whether the alarm is cleared.
Yes -> End.
No -> Step 7.
6. Contact the maintenance personnel of the peer device to modify the J1 configuration to ensure
that the peer J1 configuration is the same with the local J1 configuration, and then check whether
Yes -> End.
No -> Step 7.
7. Check whether the optical fibers of the faulty port are connected as required in accordance
with "Rack number", "Shelf number", "Slot number", "CPU number", and "Optical port index" in
the alarm information.
Yes -> Step 9.
No -> Step 8.
8. Connect the local optical fibers correctly, and then check whether the alarm is cleared.
Yes -> End.
No -> Step 9.
9. Contact the maintenance personnel of the peer device to check whether the peer optical fiber is
connected properly.
Yes -> Step 11.
No -> Step 10.
10. Contact the maintenance personnel of the peer device to connect the optical fibers properly,
Yes -> End.
No -> Step 11.
3.1.27 199001802 SDH/SONET:HP unequipped/Path unequipped

Alarm Information
l
l
l
l

Name: SDH/SONET:HP unequipped/Path unequipped
3-43
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Description
This alarm is raised if the "VC-4 path signal label" of five continuously received frames are all '0'.
Alarm Cause
l
The high-order path configured on the local end is not consistent with that on the peer end.
Impact
l
When a VC-4 UNEQ alarm is raised, the board transmits VC-4 RDI to the peer end.
Action
1. Query the SDH channel in accordance with the alarm object, and check whether the
configurations of the "High path label (C2)", "High path trail identifier byte mode (J1Mode)", and
"High path trail identifier message (J1)" parameters are the same as those of the peer end.
Yes -> Step 5.
No -> Step 2.
Yes -> Step 3.
No -> Step 4.
3. Modify the configurations of the "High path label (C2)", "High path trail identifier byte mode
(J1Mode)", and "High path trail identifier message (J1)" parameters, and then check whether
Yes -> End.
No -> Step 5.
4. Contact the maintenance personnel of the peer end to modify the configuration, ensure that the
peer configuration is consistent with the local configuration, and then check whether the alarm
is cleared.
Yes -> End.
No -> Step 5.
5. Contact the maintenance personnel of the peer end to check whether the peer device is faulty.
Yes -> Step 6.
No -> Step 7.
Yes -> End.
No -> Step 7.
3-44
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.28 199001803 SDH/SONET:HP label mismatch/Path label

mismatch
Alarm Information
l
l
l
l

Name: SDH/SONET:HP label mismatch/Path label mismatch
Alarm Description
This alarm is raised if the "VC-4 path signal label" received by the board is not consistent with the
parameter "High path label(C2)".
Alarm Cause
l
The high-order path flag of the local end is not consistent with that of the peer end.
Impact
l
the corresponding services may be affected.
If the VC-4 PLM alarm is raised, the board transmits VC-4 RDI to the peer end.
Action
1. Query the SDH channel in accordance with the alarm object, and check whether the configuration
of the "High path label (C2)" parameter is the same as that of the peer end.
Yes -> Step 5.
No -> Step 2.
Yes -> Step 3.
No -> Step 4.
3. Modify the configuration of the "High path label (C2)" parameter, and then check whether the
alarm is cleared.
Yes -> End.
No -> Step 5.
is cleared.
Yes -> End.
No -> Step 5.
Yes -> Step 6.
3-45
SJ-20140527134643-015|2015-03-31 (R1.1)
No -> Step 7.
Yes -> End.
No -> Step 7.
3.1.29 199001804 SDH/SONET:HP remote reception failure/Path

remote reception failure
Alarm Information
l
l
l
l

Name: SDH/SONET:HP remote reception failure/Path remote reception failure
Alarm Description
The VC-4 "far-end reception failure" (FERE) alarm is raised if the board detects VC-4 RDI on the
receiving side.
Alarm Cause
l
The hardware of the local transmission device is faulty.
Impact
the corresponding services may be affected.
Action
"CPU number", and "Optical port index" in the alarm information, and then check whether the
alarm is cleared.
No -> Step 2.
Yes -> Step 3.
No -> End.
3-46
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Yes -> Step 4.
No -> End.
Yes -> Step 5.
No -> Step 6.
Yes -> End.
No -> Step 6.
3.1.30 199001805 SDH/SONET:Loss of multi-frame

Alarm Information
l
l
l
l

Name: SDH/SONET:Loss of multi-frame
Alarm Description
When the board cannot receive a correct multi-frame indication code, the board enters tributary
multi-frame un-synchronization status. This alarm is raised if eight continuous frames fail to be
synchronized.
Alarm Cause
l
The frame format of the local trunk is not consistent with that of the peer end.
Local board hardware is faulty.
Impact
l
All the trunk receiving signals transmitted through the SDH/SONET channel may be interrupted,
and the corresponding services may be affected.
When a TU LOM alarm is raised, the board inserts the TU-AIS signal and transmits the TU
RDI alarm message to the peer end.
3-47
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
1. Query the SDH tributary in accordance with the alarm object, and check whether "E1 Frame
Type" or "T1 Frame Format" is the same as that on the peer end.
Yes -> Step 5.
No -> Step 2.
2. Check whether the frame format of the local trunk is wrong.
Yes -> Step 3.
No -> Step 4.
3. Modify the local frame format configuration, and check whether the alarm is cleared.
Yes -> End.
No -> Step 5.
4. Contact the maintenance personnel of the peer end to modify the peer-end frame format and
then check whether the alarm is cleared.
Yes -> End.
No -> Step 5.
port in accordance with the alarm object and "Rack number", "Shelf number", "Slot number",
alarm is cleared.
Yes -> Cancel the loopback and go to Step 8.
No -> Step 6.
"Shelf number", "Slot number", and "CPU number" in the alarm information. After the board
operates properly for three minutes, check whether the alarm persists.
Yes -> Step 7.
No -> End.
operates properly for three minutes, check whether the alarm persists.
Yes -> Step 8.
No -> End.
related alarms.
Yes -> Step 9.
No -> Step 10.
9. Contact the maintenance personnel of the peer end to remove the fault, and check whether
Yes -> End.
No -> Step 10.
3-48
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.31 199001806 SDH/SONET:Loss of TU pointer/Loss of virtual

tributary pointer
Alarm Information
l
l
l
l

Name: SDH/SONET:Loss of TU pointer/Loss of virtual tributary pointer
Alarm Description
This alarm is raised if the board continuously receives eight invalid pointers or eight NDF pointers.
Alarm Cause
l
The local board has a receiving-related fault.
Impact
l
All signals received by the trunk carried on this tributary are interrupted. Related services may
be affected.
When a TU LOP alarm is raised, the board transmits TU RDI to the peer end.
Action
1. [A2005] Run the START DTM command to perform a local loopback test on the faulty trunk of
the optical port in accordance with the alarm object and the "Rack number", "Shelf number",
"Slot number", "CPU number", "Optical port index", and "Secondary device index" in the alarm
information, and then check whether the alarm is cleared.
Yes -> Cancel the loopback test and go to Step 4.
No -> Step 2.
Yes -> Step 3.
No -> End.
Yes -> Step 4.
No -> End.
related alarms.
Yes -> Step 5.
No -> Step 6.
3-49
SJ-20140527134643-015|2015-03-31 (R1.1)
5. Contact the maintenance personnel of the peer device to remove the fault, and check whether
Yes -> End.
No -> Step 6.
3.1.32 199001807 SDH/SONET:Tributary unit alarm indication

signal/Virtual tributary alarm indication signal
Alarm Information
l
l
l
l

Name: SDH/SONET:Tributary unit alarm indication signal/Virtual tributary alarm indication signal
Alarm Description
This alarm is raised if the board detects that the codes of this tributary are all 1.
Alarm Cause
l
The hardware of the transmission device on this board is faulty.
Impact
l
All signals received by the trunk carried on this tributary are interrupted. Related services may
be affected.
When a TU AIS alarm is raised, the board transmits TU RDI to the peer end.
Action
the optical port in accordance with the alarm object and the "Rack number", "Shelf number",
"Slot number", "CPU number", "Optical port index", and "Secondary device index" in the alarm
information, and then check whether the alarm is cleared.
No -> Step 2.
Yes -> Step 3.
No -> End.
3-50
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Yes -> Step 4.
No -> End.
related alarms.
Yes -> Step 5.
No -> Step 6.
Yes -> End.
No -> Step 6.
3.1.33 199001808 SDH/SONET:LP remote defect indication/Virtual

tributary remote defect indication
Alarm Information
l
l
l
l

Name: SDH/SONET:LP remote defect indication/Virtual tributary remote defect indication
Alarm Description
This alarm is raised if the board detects that bit8 of the V5 of five continuously received frames
on the tributary is 1.
Alarm Cause
l
The hardware of the local board is faulty.
Impact
All signals transmitted by the trunk carried on this tributary are interrupted, and related services
may be affected.
3-51
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
1. Check whether the local faulty port has any of the following alarms in accordance with the "Rack
199001806 SDH/SONET:Loss of TU pointer/Loss of virtual tributary pointer
199001807 SDH/SONET:Tributary unit alarm indication signal/Virtual tributary alarm indication
signal
Yes -> Step 2.
No -> Step 3.
Yes -> End.
No -> Step 3.
alarm is cleared.
No -> Step 4.
Yes -> Step 5.
No -> End.
Yes -> Step 6.
No -> End.
Yes -> Step 7.
No -> Step 8.
Yes -> End.
No -> Step 8.
3.1.34 199001809 SDH/SONET:LP remote failure indication/Virtual

tributary remote failure indication
Alarm Information
l
l

Name: SDH/SONET:LP remote failure indication/Virtual tributary remote failure indication
3-52
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
l
l

Alarm Description
This alarm is raised if the board detects that bit4 of the V5 of five continuously received frames
on the tributary is 1.
Alarm Cause
l
The hardware of the local board is faulty.
Impact
All signals transmitted by the trunk carried on this tributary are interrupted, and related services
may be affected.
Action
signal
199001808 SDH/SONET:LP remote defect indication/Virtual tributary remote defect indication
Yes -> Step 2.
No -> Step 3.
2. 2. Handle the alarms, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
alarm is cleared.
No -> Step 4.
Yes -> Step 5.
No -> End.
Yes -> Step 6.
No -> End.
3-53
SJ-20140527134643-015|2015-03-31 (R1.1)
Yes -> Step 7.
No -> Step 8.
Yes -> End.
No -> Step 8.
3.1.35 199001810 SDH/SONET:LP trace mismatch/Virtual tributary

trace mismatch
Alarm Information
l
l
l
l

Name: SDH/SONET:LP trace mismatch/Virtual tributary trace mismatch
Alarm Description
This alarm is raised if the J2 configuration received by the board is not consistent with the expected
parameter "Low path trail identifier message(J2)" configuration.
Alarm Cause
l
The cable of the peer end is not connected correctly.
The J2 configuration on the local end is not consistent with that on the peer end.
The local clock system is faulty.
Impact
The correspondences of trunk signals carried on this tributary are incorrect, and the related services
may be affected.
3-54
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Action
"Shelf number", and "Slot number", and "CPU number" in the alarm information.
Yes -> Step 2.
No -> Step 3.
Yes -> End.
No -> Step 3.
3. Query the SDH tributary in accordance with the alarm object, and check whether the configuration
of the "Low path trail identifier message (J2)" is the same as that of the peer end.
Yes -> Step 7.
No -> Step 4.
Yes -> Step 5.
No -> Step 6.
5. Modify the configuration of the "Low path trail identifier message (J2)" parameter. Ensure
that the configurations of this parameter on both ends are the same, and then check whether
Yes -> End.
No -> Step 7.
6. Contact the maintenance personnel of the peer end to modify the J2 configuration, ensure that
the peer J2 configuration is consistent with the local J2 configuration, and then check whether
Yes -> End.
No -> Step 7.
7. Check whether the local optical fibers are connected correctly.
Yes -> Step 9.
No -> Step 8.
8. Connect the local optical fibers correctly and then check whether the alarm is cleared.
Yes -> End.
No -> Step 9.
9. Contact the maintenance personnel of the peer end to check whether the optical fiber connection
of the peer end is correct.
Yes -> Step 11.
No -> Step 10.
Yes -> End.
No -> Step 11.
3-55
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.36 199001811 SDH/SONET:LP unequipped/Virtual tributary

unequipped
Alarm Information
l
l
l
l

Name: SDH/SONET:LP unequipped/Virtual tributary unequipped
Alarm Description
This alarm is raised if the "VC-12 path signal label" received by the board is all '0'.
Alarm Cause
l
The configuration on the local end is not consistent with that on the peer end.
During installation, the internal cross-connection in the SDH network is not complete.
The peer device of this tributary is not installed.
Impact
l
All signals received by the trunk carried on this tributary may be interrupted, and the related
services may be affected.
When a TU UNEQ alarm is raised, the board transmits TU RDI to the peer end.
Action
199001812 SDH/SONET:LP label mismatch/Virtual tributary label mismatch
Yes -> Step 2.
No -> Step 3.
Yes -> End.
No -> Step 3.
3. Query the SDH tributary in accordance with the alarm, and check whether the configuration of the
"Low path label (V5)" parameter is the same to that of the peer end.
Yes -> Step 7.
No -> Step 4.
Yes -> Step 5.
No -> Step 6.
5. Modify the configuration of the "Low path label (V5)" parameter, and then check whether the
alarm is cleared.
Yes -> End.
3-56
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
No -> Step 7.
is cleared.
Yes -> End.
No -> Step 7.
7. Check the optical fibers and optical modules of the local end to make sure that optical fibers are
well connected and optical modules are inserted tightly.
Yes -> Step 9.
No -> Step 8.
8. Connect the optical fibers as required and insert the optical modules tightly, and then check
Yes -> End.
No -> Step 9.
Yes -> Step 10.
No -> Step 11.
Yes -> End.
No -> Step 11.
3.1.37 199001812 SDH/SONET:LP label mismatch/Virtual tributary

label mismatch
Alarm Information
l
l
l
l

Name: SDH/SONET:LP label mismatch/Virtual tributary label mismatch
Alarm Description
This alarm is raised if the "VC-12 path signal flag" V5(bit5-bit7) received by the board is not equal to
the parameter "Low path label(V5)" configuration, and there is no returned alarm.
Alarm Cause
l
The V5 signal flag of the local end is not consistent with that of the peer end.
3-57
SJ-20140527134643-015|2015-03-31 (R1.1)
Impact
All signals received by the trunk carried on this tributary may be interrupted, and the related services
may be affected.
Action
1. Query the SDH tributary in accordance with the alarm, and check the configuration of the "Low
path label (V5)" parameter is the same to that of the peer end.
Yes -> Step 5.
No -> Step 2.
Yes -> Step 3.
No -> Step 4.
3. Modify the configuration of the "Low path label (V5)" parameter, and then check whether the
alarm is cleared.
Yes -> End.
No -> Step 5.
is cleared.
Yes -> End.
No -> Step 5.
Yes -> Step 7.
No -> Step 6.
6. Connect the optical fibers as required and insert the optical modules tightly, and then check
Yes -> End.
No -> Step 7.
Yes -> Step 8.
No -> Step 9.
Yes -> End.
No -> Step 9.
3.1.38 199001816 SDH/SONET:Severely B1 error code

Alarm Information
l

3-58
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
l
l
l
Name: SDH/SONET:Severely B1 error code

Alarm Description
The number of error blocks in the multiplexing section is more than 30% of the total blocks.
Alarm Cause
l
The transmission part of the directly connected peer transmission device is faulty.
The connectors of the optical fibers are not clean.
The hardware of the local receiving part is faulty.
Impact
Noises or call loss occurs to all tone services carried by this optical channel, and error codes occur
to the data service channel.
Action
Yes -> Step 2.
No -> Step 3.
Yes -> End.
No -> Step 3.
alarm is cleared.
No -> Step 4.
Yes -> Step 5.
No -> End.
Yes -> Step 6.
No -> End.
6. Check whether the local optical fibers and the optical modules are inserted tightly.
Yes -> Step 8.
3-59
SJ-20140527134643-015|2015-03-31 (R1.1)
No -> Step 7.
7. Insert the local optical fibers and optical modules tightly as required. Check whether the alarm
is cleared.
Yes -> End.
No -> Step 8.
8. Perform the self-loop operation on the faulty port through the optical fibers in accordance with the
"Rack number", "Shelf number", "Slot number", and "Optical port index" in the alarm information,
Yes -> Step 10.
No -> Step 9.
9. Clean the connectors of the optical fibers, replace the optical module (refer to Replacing an
Optical Module), and then check whether the alarm is cleared.
Yes -> End.
No -> Step 10.
10. Cancel the self-loop on the optical fibers and connect the interconnected devices properly.
Contact the maintenance personnel of the peer end to check whether the peer device is faulty.
Yes -> Step 11.
No -> Step 12.
Yes -> End.
No -> Step 12.

Alarm Information
l
l
l
l

Alarm Description
The number of error blocks in the multiplexing section is more than 30% of the total blocks.
Alarm Cause
l
B1 error code causes this alarm.
3-60
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Impact
Action
199001816 SDH/SONET:Severely B1 error code
Yes -> Step 2.
No -> Step 3.
Yes -> End.
No -> Step 3.
alarm is cleared.
No -> Step 4.
Yes -> Step 5.
No -> End.
Yes -> Step 6.
No -> End.
Yes -> Step 8.
No -> Step 7.
7. Insert the local optical fibers and optical modules properly as required, and then check whether
Yes -> End.
No -> Step 8.
Yes -> Step 10.
No -> Step 9.
Yes -> End.
No -> Step 10.
3-61
SJ-20140527134643-015|2015-03-31 (R1.1)
Yes -> Step 11.
No -> Step 12.
Yes -> End.
No -> Step 12.

Alarm Information
l
l
l
l

Alarm Description
The number of error blocks in the high-order path is more than 30% of the total blocks.
Alarm Cause
l
B1 and B2 error codes cause this alarm.
Impact
Noises and call loss occur to all voice services carried by the high order channel, and error codes
occur to the data service channel.
Action
3-62
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Yes -> Step 2.
No -> Step 3.
Yes -> End.
No -> Step 3.
alarm is cleared.
No -> Step 4.
Yes -> Step 5.
No -> End.
Yes -> Step 6.
No -> End.
Yes -> Step 8.
No -> Step 7.
7. Insert the local optical fibers and optical modules properly as required, and then check whether
Yes -> End.
No -> Step 8.
Yes -> Step 10.
No -> Step 9.
Yes -> End.
No -> Step 10.
Yes -> Step 11.
No -> Step 12.
3-63
SJ-20140527134643-015|2015-03-31 (R1.1)
Yes -> End.
No -> Step 12.
3.1.41 199001819 SDH/SONET:Severely BIP-2 error code

Alarm Information
l
l
l
l

Name: SDH/SONET:Severely BIP-2 error code
Alarm Description
The number of error blocks in the low-order path is more than 30% of the total blocks.
Alarm Cause
l
The peer device of the low-order path is faulty.
The receiving part of the local board is faulty.
Impact
Noises or call loss occurs to all tone services carried on this tributary, and error codes occur to the
data service channel.
Action
Yes -> Step 2.
No -> Step 3.
Yes -> End.
No -> Step 3.
3. [A2007] Run the START DTM command to perform the local loopback test on the faulty trunk
of the optical port in accordance with the alarm object and the "Rack number", "Shelf number",
3-64
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
"Slot number", "CPU number", "Optical port index", and "Trunk ID" in the alarm information,
No -> Step 4.
4. 4. Run the SET NORMALRESET command to reset the board in accordance with "Rack
Yes -> Step 5.
No -> End.
Yes -> Step 6.
No -> End.
Yes -> Step 8.
No -> Step 7.
7. Install the local optical fibers and optical modules properly as required, and check whether the
alarm is cleared.
Yes -> End.
No -> Step 8.
8. Perform the self-loop test on the faulty port through the optical fibers in accordance with the
Yes -> Step 10.
No -> Step 9.
Yes -> End.
No -> Step 10.
10. Cancel the self-loop test on the optical fibers, and connect the interconnected devices properly.
Contact the maintenance personnel of the peer device to check whether the peer device has
related alarms.
Yes -> Step 11.
No -> Step 12.
Yes -> End.
No -> Step 12.
3.1.42 199001820 SDH/SONET:MS remote error indication

Alarm Information
l

3-65
SJ-20140527134643-015|2015-03-31 (R1.1)
l
l
l
Name: SDH/SONET:MS remote error indication

Alarm Description
This alarm is the returned error code alarm if the peer end receives a B2 error code.
Alarm Cause
l
The local optical module is faulty.
Impact
Action
199005795 The optical transceiver transmitter has detected a fault
Yes -> Step 2.
No -> Step 3.
Yes -> End.
No -> Step 3.
the SDH optical port in accordance with the alarm object and the "Rack number", "Shelf number",
Yes -> Cancel the local loopback test and go to Step 6.
No -> Step 4.
Yes -> Step 5.
No -> End.
Yes -> Step 6.
No -> End.
3-66
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Yes -> Step 8.
No -> Step 7.
7. Insert the local optical fibers and optical modules properly as required. Check whether the alarm
is cleared.
Yes -> End.
No -> Step 8.
Yes -> Step 10.
No -> Step 9.
9. replace the optical module (refer to Replacing an Optical Module), and then check whether
Yes -> End.
No -> Step 10.
10. Cancel the self-loop on the optical fibers, contact the maintenance personnel of the peer end to
check whether the peer device is faulty.
Yes -> Step 11.
No -> Step 12.
Yes -> End.
No -> Step 12.
3.1.43 199001821 SDH/SONET:HP remote error indication

Alarm Information
l
l
l
l

Name: SDH/SONET:HP remote error indication
Alarm Description
This alarm is the returned error code alarm if the peer end receives a B3 error code.
3-67
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Cause
l
Impact
Noises and call loss occur to all voice services carried on the high order channel, and error codes
occur to the data service channel.
Action
Yes -> Step 2.
No -> Step 3.
Yes -> End.
No -> Step 3.
"Slot number", "CPU number", and "Optical port index", and "Trunk ID" in the alarm information,
No -> Step 4.
Yes -> Step 5.
No -> End.
Yes -> Step 6.
No -> End.
Yes -> Step 8.
No -> Step 7.
is cleared.
Yes -> End.
No -> Step 8.
3-68
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Yes -> Step 10.
No -> Step 9.
9. Replace the optical module (refer to Replacing an Optical Module), and then check whether
Yes -> End.
No -> Step 10.
Yes -> Step 11.
No -> Step 12.
Yes -> End.
No -> Step 12.
3.1.44 199001826 SDH/SONET:LP remote error indication

Alarm Information
l
l
l
l

Name: SDH/SONET:LP remote error indication
Alarm Description
This alarm is the returned error code alarm if the peer end receives a BIP-2 error code.
Alarm Cause
l
Impact
Noises or call loss occurs to all tone services carried on this tributary, and error codes occur to the
data service channel.
Action
3-69
SJ-20140527134643-015|2015-03-31 (R1.1)
Yes -> Step 2.
No -> Step 3.
Yes -> End.
No -> Step 3.
No -> Step 4.
Yes -> Step 5.
No -> End.
Yes -> Step 6.
No -> End.
Yes -> Step 8.
No -> Step 7.
is cleared.
Yes -> End.
No -> Step 8.
Yes -> Step 10.
No -> Step 9.
9. Replace the optical module (refer to Replacing an Optical Module), and then check whether
Yes -> End.
No -> Step 10.
Yes -> Step 11.
No -> Step 12.
3-70
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Yes -> End.
No -> Step 12.
3.1.45 199005123 The configuration is not supported

Alarm Information
l
l
l
l

Name: The configuration is not supported
Alarm Description
This alarm is raised if the board detects that the configured parameters are not supported by the
hardware.
Alarm Cause
l
The configuration is incorrect.
Hardware type error.
Impact
Some functions of the board are abnormal.
Action
Contact the next level of maintenance support.
3.1.46 199005128 Rack or shelf conflict

Alarm Information
Code:
199005128
Name:
Rack or shelf conflict
Severity:
Minor
Type:
Equipment Alarm
3-71
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Description
This alarm is raised if the switching board detects a shelf and rack information conflict.
Probable Cause
The shelf DIP is set incorrectly.
System Impact
The conflicting shelves cannot operate properly.
Handling Suggestion
1. Check whether the DIP on the CDM of the peer-end shelf (that the port of the board is connected
to) is configured in accordance with the actual requirements by using "Physical address", "Port
number", and "Port Type" in the alarm information.
Yes -> Step 3.
No -> Step 2.
2. Modify the DIP setting as required, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3.1.47 199005200 Board configuration information is not compatible

Alarm Information
Code:
199005200
Name:
Board configuration information is not compatible
Severity:
Major
Type:
Equipment Alarm
Alarm Description
This alarm is raised if the system detects that the physical board type configured in the database is
different from the real board type, and they are not compatible with each other.
Probable Cause
l
The physical board type is configured incorrectly.
The slot is not installed with a correct board.
3-72
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
System Impact
The board fails to operate properly.
Handling Suggestion
1. Check whether the board type is configured as required through the rack diagram.
Yes -> Step 3.
No -> Step 2.
2. Configure the "Board(Board)" object as required, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3. Replace the board with an operational one(refer to Front Boards and Rear Boards Replacement)
as required, and check whether the alarm is cleared.
Yes -> End.
No -> Step 4.
3.1.48 199005405 Clock board phase-lock loop work mode is

abnormal
Alarm Information
l
l
l
l

Name: Clock board phase-lock loop work mode is abnormal
Alarm Description
This alarm is raised if the board detects that the phase-locked loop is in the non-tracing status (not
synchronized with the external clock reference card).
Alarm Cause
l
There is no clock reference source.
The clock distribution line is not correct, or a loopback exists.
The precision of the clock reference used is lower than the one required by this board.
Impact
The specific clock reference cannot be locked, and thus services may be affected.
3-73
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
parameter of the "Shelf (Shelf)" object. If the board is in a main shelf, in the Independent Board
Configuration Online window, check whether the clock reference is configured (any clock
reference with a priority in the range from level 1 through level 4).
Yes -> Step 3.
No -> Step 2.
2. Configure the clock reference as required, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3. Check whether the board has an alarm about the loss of the clock reference.
199026127 Clock reference source lost (Level 3 alarm)
Yes -> Step 4.
No -> Step 5.
Yes -> End.
No -> Step 5.
3.1.49 199005407 The board is power off

Alarm Information
Code:
199005407
Name:
The board is power off
Severity:
Major
Type:
Equipment Alarm
Alarm Description
This alarm is raised if the CMM detects that an OMM, OMP, EGBS, EGFS, EXFS, or USCC board
is powered off.
Probable Cause
l
A board's ejector lever is unlocked.
A board is powered off manually.
The board hardware is faulty.
3-74
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
System Impact
The corresponding board cannot provide services.
Handling Suggestion
1. Check whether the board is manually powered off by any maintenance personnel by checking
EMS operation logs.
Yes -> End.
No -> Step 2.
2. Check whether any extractor of the board is open.
Yes -> Step 3.
No -> Step 4.
3. Close the board extractors, and check whether the alarm is cleared.
Yes -> End.
No -> Step 4.
4. Power on the board, and check whether the alarm is cleared.
Yes -> End.
No -> Step 5.
5. Remove and reinstall the board, wait for 2 minutes, and check whether the alarm is cleared,refer
to Removing a Board.
Yes -> End.
No -> Step 6.
3.1.50 199005632 The hard disk used-rate is over threshold

Alarm Information
l
l
l
l

Name: The hard disk used-rate is over threshold
Alarm Description
This alarm is raised if the board detects that the hard disk usage exceeds the threshold.
Alarm Cause
l
The hard disk usage is too high.
The hard disk usage threshold is too low (in normal cases, it should not be less than 90%).
3-75
SJ-20140527134643-015|2015-03-31 (R1.1)
Impact
Data cannot be saved.
Action
1. Check whether "Hard disk usage" in the alarm information exceeds 90 percent.
Yes -> Step 3.
No -> Step 2.
2. Modify the hard disk threshold of the "IDE Alarm(IDEAlarm)" object, and check whether the
alarm is cleared.
Yes -> End.
No -> Step 3.
3.1.51 199005633 File system is abnormal

Alarm Information
l
l
l
l

Name: File system is abnormal
Alarm Description
This alarm is raised if the board detects a file system fault.
Alarm Cause
l
The hard disk does not exist.
The hard disk is not formatted.
The file system is abnormal.
Impact
Data cannot be saved or read.
3-76
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Action
"Shelf number", "Slot number" and "CPU number" in the alarm information. Check whether
Yes -> End.
No -> Step 2.
2. Replace the faulty board(refer to Front Boards and Rear Boards Replacement), and check
Yes -> End.
No -> Step 3.
3.1.52 199005634 The hard disk on board gets IO error

Alarm Information
l
l
l
l

Name: The hard disk on board gets IO error
Alarm Description
This alarm is raised if the number of times that an error occurs during hard disk read and write
exceeds the threshold (20/hour).
Alarm Cause
The number of times that an error occurs during hard disk read and write exceeds the threshold.
Impact
Action
1. Check whether the following alarms are raised on the faulty board:
199005797 The hard disk is abnormal
199005798 The RAID of hard disks is abnormal
Yes -> Step 2.
No -> Step 3.
2. Handle the above alarms, wait for one hour, and check whether the alarms are cleared.
Yes -> End.
No -> Step 3.
3-77
SJ-20140527134643-015|2015-03-31 (R1.1)
3. Replace the hard disk (refer to Replacing a Hard Disk) with an operational one. Check whether
Caution!
Backup important data before the replacement.
Yes -> End.

No -> Step 4.
3.1.53 199005666 Error packets of MAC is higher than the specified

threshold
Alarm Information
l
l
l
l

Name: Error packets of MAC is higher than the specified threshold
Alarm Description
This alarm is raised if the board detects that the error packet rate of the MAC exceeds the threshold
(1/1024) continuously.
Alarm Cause
l
The devices on both ends are faulty.
The intermediate line is faulty.
Impact
Services transmitted by the port are affected.
3-78
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Action
1. Check whether "Physical location " in the alarm information is "Front panel port", "Rear port",
"Switch panel port" or "Switch back card port".
Yes -> Step 2.
No -> Step 8.
2. Check whether the cable connected to the corresponding port is damaged in accordance with
"Physical location" and "Port number" in the alarm information.
Yes -> Step 3.
No -> Step 4.
3. Replace the cable with an operational one, and check whether the alarm is cleared.
Yes -> End.
No -> Step 4.
199005791 TX Power High Alarm
199005792 TX Power Low Alarm
Yes -> Step 5.
No -> Step 6.
Yes -> End.
No -> Step 6.
Yes -> Step 7.
No -> Step 8.
7. Resolve the peer device fault, and check whether the alarm is cleared.
Yes -> End.
No -> Step 8.
Yes -> End.
No -> Step 9.
3.1.54 199005672 Clock source for SyncE is not available

Alarm Information
l
l
l
l

Name: Clock source for SyncE is not available
3-79
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Description
This alarm is raised if the board cannot obtain clock information from the peer end.
Alarm Cause
l
No clock synchronization packet is received from the peer end within five seconds.
The clock resource advertised by the peer end is unavailable.
The port rate is 10 Mbps.
The physical link of the port is disconnected.
Impact
The clock of the NE may fail to be synchronized, and thus services may be affected.
Action
1. Check whether "Reason of unavailable clock source" in the alarm information is "Physical link
is down".
Yes -> Step 2.
No -> Step 4.
2. Check whether the following alarm is raised on the board:
Yes -> Step 3.
No -> Step 11.
Yes -> End.
No -> Step 11.
4. Check whether "Reason of unavailable clock source" in the alarm information is "Not received
ESMC PDU message for 5 seconds".
Yes -> Step 5.
No -> Step 7.
5. Contact the maintenance personnel of the peer device, and check whether the interconnected
port is in master mode.
Yes -> Step 11.
No -> Step 6.
6. Modify the peer-end configuration, and check whether the alarm is cleared.
Yes -> End.
No -> Step 11.
7. Check whether "Reason of unavailable clock source" in the alarm information is "Received
SSM code is DNU".
Yes -> Step 8.
No -> Step 9.
8. After the maintenance personnel of the peer device resolve the fault, check whether the alarm
is cleared.
Yes -> End.
3-80
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
No -> Step 11.

9. Check whether "Reason of unavailable clock source" in the alarm information is "Port speed
mode is 10M".
Yes -> Step 10.
No -> Step 11.
10. Modify the "Negotiate Mode(NegotiateMode)" and "Port Speed(Speed)" parameters of the
"Ethernet Port(EthernetPort)" object (the "Port Speed(Speed)" parameter must not be set to 10
Mbps). Check whether the alarm is cleared.
Yes -> End.
No -> Step 11.
3.1.55 199005673 The setting of the dial switch is changed

Alarm Information
l
l
l
l

Name: The setting of the dial switch is changed
Alarm Description
This alarm is raised if the CMM board detects that the DIP of the shelf is changed.
Alarm Cause
The CDM jumper setting on the CMM board is changed.
Impact
Other boards in the shelf cannot be powered on successfully after the CMM board is restarted.
Action
1. Check whether "Office ID in left CDM", "Office ID in right CDM", "Rack number in left CDM", "Rack
number in right CDM", "Shelf number in left CDM", "Shelf number in right CDM", "Diagnostic
mode in left CDM", and "Diagnostic mode in right CDM" in the alarm information are the newest
values and the left and right settings correspond to each other.
Yes -> Step 2.
No -> Step 4.
2. Reset the CMM board. After the board is powered on, forcedly reset other boards in the shelf,
and whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3-81
SJ-20140527134643-015|2015-03-31 (R1.1)
3. Determine whether the left CDM settings are the newest ones in accordance with alarm
information.
Yes -> Step 5.
No -> Step 4.
4. Replace the left CDM (refer to ECDM Replacement) with an operational one (before the
replacement, configure the DIP on the left CDM in accordance with the value range), and check
Yes -> End.
No -> Step 5.
5. Determine whether the right CDM settings are the newest ones in accordance with alarm
information.
Yes -> End.
No -> Step 6.
6. Replace the right CDM (refer to ECDM Replacement) with an operational one (before the
replacement, configure the DIP on the right CDM in accordance with the value range), and
Yes -> End.
No -> Step 7.
3.1.56 199005674 Switch chip inner loop check abnormal

Alarm Information
Code:
199005674
Name:
Switch chip inner loop check abnormal
Severity:
Critical
Type:
Equipment Alarm
Alarm Description
This alarm is raised if the board detect that the switching chip has an internal loopback.
Probable Cause
l
The switching chip of the board is faulty.
The switching chip of the board is not connected properly with the CPU.
System Impact
The control plane communication between the faulty board and other boards may be disconnected,
the board checking packets in a shelf or the cascading messages between different shelves are
abnormal. Services are thus interrupted.
3-82
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Handling Suggestion
1. Wait for five minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 2.
2. Replace the board with an operational one(refer to Front Boards and Rear Boards Replacement),
Yes -> End.
No -> Step 3.
3.1.57 199005760 Ethernet port's link is down

Alarm Information
l
l
l
l

Name: Ethernet port's link is down
Alarm Description
This alarm is raised if the board detects that the link of the Ethernet port is disconnected.
Alarm Cause
l
The local or the peer network port is faulty.
The local end is not properly connected to the peer end.
The network port configuration on the local end is not consistent with that on the peer end.
Impact
Data cannot be transmitted through the port.
Action
1. Check whether the "Negotiate Mode(NegotiateMode)","Port Speed(Speed)","Duplex
Mode(Duplex)","Master or Slave mode(Master)", and "Cable Type(WireType)" parameters of the
"Ethernet Port(EthernetPort)" object are set as required in accordance with the alarm object.
Yes -> Step 3.
No -> Step 2.
2. Modify the parameters as required, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3. Contact the maintenance personnel of the peer device to check whether the working parameters
of the interconnected port are set as required.
3-83
SJ-20140527134643-015|2015-03-31 (R1.1)
Yes -> End.

No -> Step 4.
4. Modify the working parameters of the interconnected port, and check whether the alarm is cleared.
Yes -> End.
No -> Step 5.
199005791 TX Power High Alarm
199005792 TX Power Low Alarm
Yes -> Step 6.
No -> Step 7.
Yes -> End.
No -> Step 7.
7. Contact the maintenance personnel of the peer device to check whether the interconnected
port is faulty.
Yes -> Step 8.
No -> Step 9.
8. Resolve the interconnected port fault, and check whether the alarm is cleared.
Yes -> End.
No -> Step 9.
3.1.58 199005761 The speed mode of Ethernet port doesn't match

with settings
Alarm Information
l
l
l
l

Name: The speed mode of Ethernet port doesn't match with settings
Alarm Description
This alarm is raised if the board detects that the port's auto-negotiated rate is different from the
expected rate.
Alarm Cause
The auto-negotiated rate of the Ethernet port is different from the configured expected rate.
3-84
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Impact
The transmission capability of the Ethernet port may be reduced.
Action
1. Query the "Negotiate Mode(NegotiateMode)" and "Port Speed(Speed)" parameters of the
"Ethernet Port(EthernetPort)" object in accordance with the alarm object, and check whether the
setting of the "Port Speed(Speed)" parameter in auto negotiation mode is in accordance with the
actual requirements.
Yes -> Step 3.
No -> Step 2.
2. Modify the "Port Speed(Speed)" parameter, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
Yes -> End.
No -> Step 4.
3.1.59 199005768 All of the board input clocks which have the same
frequency are lost
Alarm Information
l
l
l
l

Name: All of the board input clocks which have the same frequency are lost
Alarm Description
This alarm is raised if the board detects that all board input clocks with the same frequency are lost.
Alarm Cause
l
The clock line is not connected.
The clock output source operates improperly.
The hardware of the clock module of the board is faulty.
Impact
Action
3-85
SJ-20140527134643-015|2015-03-31 (R1.1)
1. Check whether the boards in slots 21 and 22 of the shelf are clock boards in accordance with
Yes -> Step 2.
No -> Step 10.
2. Check whether an alarm is raised on the upper-level clock board.
Yes -> Step 4.
No -> Step 3.
Yes -> End.
No -> Step 4.
4. In the "Independent Board Configuration Online" window, check whether the upper-level clock
board is configured to be in the master shelf.
Yes -> Step 6.
No -> Step 5.
5. Modify the shelf configuration of the upper-level clock board in accordance with the actual clock
networking requirements. If the board is configured to be in the master shelf, the clock reference
configuration should be added. Check whether the alarm is cleared.
Yes -> End.
No -> Step 6.
6. Check whether the following alarms are raised on the upper-level clock board:
Yes -> Step 7.
No -> Step 8.
7. Handle the above alarms, and whether the alarm is cleared.
Yes -> End.
No -> Step 8.
8. Check whether the cables for the clock network are connected as required (refer to Installing
Clock Cables).
Yes -> Step 16.
No -> Step 9.
9. Connect the cables in accordance with the inter-shelf clock networking requirements, and
Yes -> End.
No -> Step 16.
10. Check whether the clock board in the shelf is operating properly.
Yes -> Step 12.
No -> Step 11.
11. Power on the clock board, and check whether the alarm is cleared.
Yes -> End.
No -> Step 12.
3-86
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
12. Check whether the shelf configuration of the clock board is correct.
Yes -> Step 14.
No -> Step 13.
13. In the "Independent Board Configuration Online" window, check whether the clock reference is
configured for the master shelf. If the clock reference is not configured, configure it, and check
Yes -> End.
No -> Step 14.
14. Check whether the following alarms are raised on the clock board of the shelf:
Yes -> Step 15.
No -> Step 16.
Yes -> End.
No -> Step 16.
3.1.60 199005770 The OMP board doesn't have any OMC port
Alarm Information
l
l
l
l

Name: The OMP board doesn't have any OMC port
Alarm Description
This alarm is raised if the OMP board fails to detect the OMC port.
Alarm Cause
The rear board is not present or faulty.
Impact
l
If the board is in active status, the network management system cannot manage NEs.
If the board is in standby status, this alarm does not affect the system, but the reliability of the
system is reduced.
3-87
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
1. Check whether the rear card corresponding to the board in the rack diagram is present.
Yes -> Step 3.
No -> Step 2.
2. Install the matched rear card (refer to Installing a Board) and check whether the alarm is
cleared.
Yes -> End.
No -> Step 4.
3. Replace the rear card with the same type of card(refer to Front Boards and Rear Boards
Yes -> End.
No -> Step 4.
3.1.61 199005771 The duplex mode of Ethernet port doesn't match

with settings
Alarm Information
l
l
l
l

Name: The duplex mode of Ethernet port doesn't match with settings
Alarm Description
This alarm is raised if the board detects that the port's auto-negotiated rate is different from the
expected rate.
Alarm Cause
The duplex mode of port auto-negotiation is different from the configured mode.
Impact
The transmission capability of the Ethernet port may be reduced.
3-88
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Action
1. Query the "Negotiate Mode(NegotiateMode)" and "Duplex Mode(Duplex)" parameters of the
"Ethernet Port(EthernetPort)" object in accordance with the alarm object, and check whether the
setting of the "Duplex Mode(Duplex)" parameter in auto negotiation mode is in accordance
with the actual requirements.
Yes -> Step 3.
No -> Step 2.
2. Modify the "Duplex Mode(Duplex)" parameter, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
Yes -> End.
No -> Step 4.
3.1.62 199005772 Board device fault

Alarm Information
l
l
l
l

Name: Board device fault
Alarm Description
This alarm is raised if the board detects a device hardware fault.
Alarm Cause
Impact
The board does not operate properly, which may affect the corresponding services.
Action
Yes -> End.
No -> Step 2.
3-89
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.63 199005773 High CRC error rate at E1/T1 bottom layer

Alarm Information
l
l
l
l

Name: High CRC error rate at E1/T1 bottom layer
Alarm Description
This alarm is raised if the board detects that the CRC bit error rate of trunk port E1/T1 is high (30% of
the error codes are generated within one second).
Alarm Cause
l
The frame format of the interconnected E1/T1 port is inconsistent.
Impact
Action
on the peer end.
Yes -> Step 3.
No -> Step 2.
Yes -> End.
No -> Step 3.
Yes -> Step 4.
No -> Step 5.
Yes -> End.
3-90
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
No -> Step 5.
number", "Shelf number", "Slot number", "Primary device index" (optical port number), and
"Secondary device index" (E1/T1 port number) in the alarm information.
Yes -> Step 7.
No -> Step 6.
Yes -> End.
No -> Step 7.
Yes -> Step 8.
No -> Step 9.
Yes -> End.
No -> Step 9.
Yes -> End.
No -> Step 10.
information.
Yes -> Step 11.
No -> Step 13.
11. Removing a Board and check whether the DIP switch of the board and the jumper of the rear
board are consistent with the cable type.
Yes -> Step 15.
No -> Step 12.
Yes -> End.
No -> Step 15.
13. Query "E1 Impedance" or "T1 Impedance". Removing a Board and check whether the DIP switch
of the board and the trunk impedance are consistent with the cable type.
Yes -> Step 15.
No -> Step 14.
Yes -> End.
No -> Step 15.
3-91
SJ-20140527134643-015|2015-03-31 (R1.1)
Yes -> Step 17.

No -> Step 16.
Yes -> End.
No -> Step 17.
3.1.64 199005774 High FAS error rate at E1/T1 bottom layer

Alarm Information
l
l
l
l

Name: High FAS error rate at E1/T1 bottom layer
Alarm Description
This alarm is raised if the board detects that the FAS bit error rate of trunk port E1/T1 is high (30% of
the error codes are generated within one second).
Alarm Cause
l
The transmission device is faulty.
Impact
Action
Yes -> Step 2.
No -> Step 3.
Yes -> End.
No -> Step 3.
3-92
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
number", "Shelf number", "Slot number", "Primary device index" (optical port number), and
"Secondary device index" (E1/T1 port number) in the alarm information.
Yes -> Step 5.
No -> Step 4.
Yes -> End.
No -> Step 5.
Yes -> Step 6.
No -> Step 7.
Yes -> End.
No -> Step 7.
Yes -> End.
No -> Step 8.
information.
Yes -> Step 9.
No -> Step 11.
9. Removing a Board and check whether the DIP switch of the board and the jumper of the rear
board are consistent with the cable type.
Yes -> Step 13.
No -> Step 10.
Yes -> End.
No -> Step 13.
11. Query "E1 Impedance" or "T1 Impedance". Removing a Board and check whether the DIP switch
of the board and the trunk impedance are consistent with the cable type.
Yes -> Step 13.
No -> Step 12.
Yes -> End.
No -> Step 13.
Yes -> Step 15.
No -> Step 14.
3-93
SJ-20140527134643-015|2015-03-31 (R1.1)
Yes -> End.
No -> Step 15.
3.1.65 199005775 High EBIT error rate at E1 bottom layer

Alarm Information
l
l
l
l

Name: High EBIT error rate at E1 bottom layer
Alarm Description
This alarm is raised if the board detects that the E bit error rate of trunk port E1 is high (30% of the
error codes are generated within one second).
Alarm Cause
l
The frame formats of the interconnected E1/T1 ports are inconsistent.
The peer end transmits "E-Bit error" to this end.
Impact
Action
on the peer end.
Yes -> Step 3.
No -> Step 2.
Yes -> End.
No -> Step 3.
3-94
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3. Contact the maintenance personnel of the peer end to check whether the peer device reports
alarms relating to CRC errors and whether the peer device sends "E-bit error" messages to the
local end.
Yes -> Step 4.
No -> Step 5.
4. After the maintenance personnel of the peer end solves related faults, check whether the alarm
is cleared.
Yes -> End.
No -> Step 5.
Yes -> Step 6.
No -> Step 7.
Yes -> End.
No -> Step 7.
Yes -> Step 9.
No -> Step 8.
Yes -> End.
No -> Step 9.
3.1.66 199005785 GPS module is abnormal

Alarm Information
l
l
l
l

Name: GPS module is abnormal
Alarm Description
This alarm is raised if the board detects that the GPS is in abnormal status.
3-95
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Cause
l
The receiving signal is poor. The number of satellites that can receive signals is less than four.
The GPS PP1S output jitter exceeds the allowed range.
Impact
System clock synchronization may be affected, and services may be affected.
Action
1. Check whether the GPS antenna is connected correctly.
Yes -> Step 2.
No -> Step 3.
2. Connect the GPS antenna correctly, and then check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3.1.67 199005790 The configuration of clock shelf function is error

Alarm Information
Code:
199005790
Name:
The configuration of clock shelf function is error
Severity:
Warning
Type:
Equipment Alarm
Alarm Description
This alarm is raised if the clock's master and slave shelves are not configured correctly.
Probable Cause
l
More than one clock shelf is configured as the master shelf.
No slave shelf is configured.
System Impact
The system clock may fail to be synchronized, so services may be affected.
3-96
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Handling Suggestion
1. Check whether "Reason of configuration error" in the alarm information is "More than one clock
shelf is configured as the master."
Yes -> Step 2.
No -> Step 3.
2. In accordance with the clock networking requirement, query "Independent Board Configuration
Online", and check the master and slave clock shelf configuration. Verify that only one shelf that
contains a clock board in the system is configured as the master clock shelf. Check whether
Yes -> End.
No -> Step 3.
3. Check whether "Reason of configuration error" in the alarm information is "The configuration
for clock shelf function is needed."
Yes -> Step 4.
No -> Step 5.
4. In accordance with the clock networking requirement, query "Independent Board Configuration
Online", and check the master and slave clock shelf configuration of the clock board in the shelf.
Verify that only one shelf that contains a clock board in the system is configured as the master
clock shelf. Check whether the alarm is cleared.
Yes -> End.
No -> Step 5.
3.1.68 199005795 The optical transceiver transmitter has detected

a fault
Alarm Information
Code:
199005795
Name:
The optical transceiver transmitter has detected a fault
Severity:
Minor
Type:
Equipment Alarm
Alarm Description
This alarm is raised when the board detects that the optical module cannot transmit signals properly.
Probable Cause
The optical module hardware is faulty.
3-97
SJ-20140527134643-015|2015-03-31 (R1.1)
System Impact
Data transmission on the optical module is affected, and services are interrupted.
Handling Suggestion
1. Remove and reinstall the optical module in accordance with "Optical transceiver index" and
"Physical location" in the alarm information, wait for three minutes, and then check whether
Yes -> End.
No -> Step 2.
2. Replace the optical module(refer to Replacing an Optical Module) in accordance with "Optical
transceiver index" and "Physical location" in the alarm information, wait for three minutes, and
then check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3.1.69 199005796 Clock of this board is abnormal

Alarm Information
Code:
199005796
Name:
Clock of this board is abnormal
Severity:
Critical
Type:
Equipment Alarm
Alarm Description
This alarm is raised if the board detects that the crystal oscillator or the phase-locked loop is abnormal.
Probable Cause
l
The clock board fault results in the output clock change.
The phase-locked loop hardware is faulty.
The crystal oscillator stops oscillating or the frequency is deviated.
System Impact
3-98
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Handling Suggestion
Yes -> Step 3.
No -> Step 2.
Yes -> End.
No -> Step 3.
3. Replace the board with an operational one(refer to Replacing an Optical Module), and check
Yes -> End.
No -> Step 4.
3.1.70 199005797 The hard disk is abnormal

Alarm Information
l
l
l
l

Name: The hard disk is abnormal
Alarm Description
This alarm is raised if the board fails to detect the hard disk or the hard disk SMART parameter is
not correct.
Alarm Cause
l
The hard disk does not exist or cannot be identified.
The hard disk SMART is abnormal.
Impact
3-99
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
1. Replacing a Hard Disk in accordance with "Hard disk location" in the alarm information, and
Yes -> End.
No -> Step 2.
Note:
If the hard disk of the board is hot swappable, the status indicator mark of the hard disk is the same
as the location mark of the hard disk in the alarm information. If the hard disk is not hot swappable,
the two marks are opposite to each other.
3.1.71 199005798 The RAID of hard disks is abnormal

Alarm Information
l
l
l
l

Name: The RAID of hard disks is abnormal
Alarm Description
This alarm is raised if the board detects that the hard disk RAID is in abnormal status.
Alarm Cause
l
Two hard disks of the board do not form the RAID.
In RAID, one hard disk is unavailable or does not operate properly.
Before the RAID is synchronized, the active hard disk becomes faulty or is removed.
The RAID information of the SAS controller is abnormal or the RAID information on the two
hard disks is different.
Impact
The hard disk may fail to operate properly.
3-100
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Action
1. Check whether the following alarm is raised on the hard disk in accordance with the "Hard disk
location" in the alarm information:
Yes -> Step 2.
No -> Step 3.
Yes -> End.
No -> Step 3.
Note:
If the hard disk of the board is hot swappable, the status indicator mark of the hard disk is the same
as the location mark of the hard disk in the alarm information. If the hard disk is not hot swappable,
the two marks are opposite to each other.
3.1.72 199005799 Hard disk online

Alarm Information
l
l
l
l

Name: Hard disk online
Alarm Description
This alarm is raised if the board detects that a hard disk is installed.
Alarm Cause
l
A hard disk is installed.
The SAS controller is abnormal.
Impact
After a hard disk is installed, the board is restarted. In this period, services on the board may
be affected instantaneously.
3-101
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
Yes -> End.
No -> Step 2.
3.1.73 199005800 Hard disk offline

Alarm Information
l
l
l
l

Name: Hard disk offline
Alarm Description
This alarm is raised if the board detects that a hard disk becomes unavailable.
Alarm Cause
l
A hard disk is removed.
The SAS controller is abnormal.
Impact
After a hard disk is removed, the board is restarted. In this period, services on the board may be
affected instantaneously.
Action
Yes -> End.
No -> Step 2.
3.1.74 199005801 Memory size is abnormal

Alarm Information
Code:
199005801
Name:
Memory size is abnormal
3-102
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Severity:
Major
Type:
Equipment Alarm
Alarm Description
This alarm is raised if the board detects that the SPD memory capacity is different from the available
memory in the system.
Probable Cause
The memory is faulty or loose.
System Impact
If the available memory is insufficient, the board may fail to operate properly.
Handling Suggestion
1. Remove and reinstall the board memory or replace the board memory with an operational
one(refer to Replacing a Memory Bar), and power on the board. Wait for three minutes, and
Yes -> End
No -> 2
Replacement), and power on the board. Wait for three minutes, and check whether the alarm
is cleared.
Yes -> End .
No -> 3 .
3.1.75 199005802 The board lacks fabric port in the shelf

Alarm Information
Code:
199005802
Name:
The board lacks fabric port in the shelf
Severity:
Warning
Type:
Equipment Alarm
Alarm Description
This alarm is raised if the board detects that the intra-shelf Fabric port is unavailable.
3-103
SJ-20140527134643-015|2015-03-31 (R1.1)
Probable Cause
The board does not have any intra-shelf Fabric port.
System Impact
Handling Suggestion
Yes -> End.
No -> Step 2.
3.1.76 199005930 Version load failed

Alarm Information
l
l
l
l

Name: Version load failed
Alarm Description
This alarm is raised if any resource processing chip (for example, DSP and EC) version fails to be
loaded on the board.
Alarm Cause
l
The DSP or EC device is configured, but the corresponding hardware version is not configured.
The DSP or EC hardware version fails to be burnt.
Impact
The DSP and EC resources cannot be used and the corresponding services may be interrupted.
Action
1. Reset the faulty board, and check whether the alarm is cleared.
Yes -> End.
No -> Step 2.
3-104
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.77 199005931 Incorrect subunit configuration for inserted

board or device
Alarm Information
Code:
199005931
Name:
Incorrect subunit configuration for inserted board or device
Severity:
Warning
Type:
Equipment Alarm
Alarm Description
This alarm is raised if the board detects that the configuration of the database subunit does not
match the board hardware.
Probable Cause
l
The subunit is configured incorrectly.
Incorrect hardware.
System Impact
The corresponding services cannot use the DSP and EC resources.
Handling Suggestion
3.1.78 199005932 The third party firmware version load failed

Alarm Information
Code:
199005932
Name:
The third party firmware version load failed
Severity:
Major
Type:
Equipment Alarm
Alarm Description
This alarm is raised if a third-party firmware version fails to be updated because the required version
fails to be downloaded or verified.
3-105
SJ-20140527134643-015|2015-03-31 (R1.1)
Probable Cause
l
A third-party firmware version fails to be downloaded.
The third-party firmware version fails to be burnt or verified.
System Impact
The third-party firmware device may fail to operate properly.
Handling Suggestion
3.1.79 199005933 Shutdown board to validate the third party

firmware
Alarm Information
Code:
199005933
Name:
Shutdown board to validate the third party firmware
Severity:
Major
Type:
Equipment Alarm
Alarm Description
This alarm is raised if the third-party firmware is updated and the device needs to be powered off.
Probable Cause
The updated firmware version is effective after it is powered on again.
System Impact
If the board is not powered off and then powered on, the third-party firmware version is not effective.
Handling Suggestion
Run the SET NON_OMP BOARD POWER OFFcommand to power off the board in accordance
with the alarm position information, and run the SET NON_OMP BOARD POWER ONcommand to
power on the board.
3-106
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.80 199007168 Port trunk failed

Alarm Information
l
l
l
l

Name: Port trunk failed
Alarm Description
This alarm is raised if the board detects that the internal Ethernet port connection is not in normal
status.
Alarm Cause
l
The Ethernet port hardware is faulty.
The switching board of the NE is faulty or unavailable.
The pin of the slot in which the board is installed is damaged.
Impact
If the ports of the same type on this board are all faulty, the services on this board are interrupted.
Action
1. Check whether the alarm is raised on more than two boards in the same shelf in accordance with
Yes -> Step 2.
No -> Step 5.
2. In the rack diagram, check whether the switching board that is in the same shelf as the faulty
board is operating properly.
Yes -> Step 3.
No -> Step 4.
3. Wait for one minute, and check whether the alarm is cleared.
Yes -> End.
No -> Step 5.
4. Resolve the switching board fault, wait for five minutes, and then check whether the alarm
is cleared.
Yes -> End.
No -> Step 5.
199005666 Error packets of MAC is higher than the specified threshold
199007169 Inner port error
Yes -> Step 6.
No -> Step 7.
3-107
SJ-20140527134643-015|2015-03-31 (R1.1)
Yes -> End.

No -> Step 7.
3.1.81 199007169 Inner port error

Alarm Information
l
l
l
l

Name: Inner port error
Alarm Description
This alarm is raised if the board detects that the internal Ethernet port (used for internal
communication) is not operating in full duplex mode or in correct rate (for example, a 1Gbps optical
port operates at 100 Mbps).
Alarm Cause
The Ethernet port hardware is faulty.
Impact
This fault may result in internal communication faults and triggers alarm "199007168 Port trunk failed".
Action
"Shelf number", "Slot number", and "CPU number" in the alarm information. Wait for five minutes,
Yes -> End.
No -> Step 2.
wait for five minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3-108
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.82 199007170 Trunk connect asymmetry

Alarm Information
l
l
l
l

Name: Trunk connect asymmetry
Alarm Description
This alarm is raised if the switching board detects that the connections between shelves are not
symmetrical. For example, Ethernet port 1 in the left slot is connected to a shelf, but Ethernet port 1 in
the right slot is not connected to a shelf or the connection fails.
Alarm Cause
l
The inter-shelf port connections between the left and right switching boards are not symmetrical.
The connection between inter-shelf ports is faulty.
Impact
If the service traffic is heavy, the communication between shelves may fail, and thus some services
may be affected.
Action
199005666 Error packets of MAC is higher than the specified threshold
Yes -> Step 2.
No -> Step 3.
Yes -> End.
No -> Step 3.
3. Check whether the fiber or network cable is not connected to the faulty port of the board in
accordance with "Physical address" and "Port number" in the alarm information.
Yes -> Step 4.
No -> Step 5.
4. Connect the fibers and network cables between shelves as required, and check whether the
alarm is cleared.
Yes -> End.
No -> Step 5.
5. Check whether the fibers and network cables connected to the faulty port and the peer device's
port are loose (if so, the green indicators of the ports are not lighted).
Yes -> Step 6.
No -> Step 7.
3-109
SJ-20140527134643-015|2015-03-31 (R1.1)
6. Secure the fibers and network cables, and check whether the alarm is cleared.
Yes -> End.
No -> Step 7.
7. Clean the both ends of the fibers by using the absorbent cotton soaked with absolute alcohol, and
Yes -> End.
No -> Step 8.
8. Replace the fibers and network cables with operational ones, and check whether the alarm
is cleared.
Yes -> End.
No -> Step 9.
9. Replacing an Optical Module, and check whether the alarm is cleared.
Yes -> End.
No -> Step 10.
3.1.83 199007171 Outer media trunk failed

Alarm Information
l
l
l
l

Name: Outer media trunk failed
Alarm Description
This alarm is raised if there is no media plane optical connection between NEs in multiple shelves, or
between a non-gateway shelf and a gateway shelf, or all optical ports are faulty. This alarm is not
raised if there is one optical port that operates properly.
Alarm Cause
l
The optical ports on media planes are not connected between a non-gateway shelf and a
gateway shelf.
The optical port connection on media planes between a non-gateway shelf and a gateway
shelf are faulty.
Impact
Media plane services on the non-gateway shelf are interrupted.
3-110
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Action
1. Check whether the following alarm is raised on the optical ports (of the faulty board) that all
fibers are connected to:
Yes -> Step 2.
No -> Step 3.
Yes -> End.
No -> Step 3.
3. Check whether fibers are connected to the faulty board or are connected as required.
Yes -> Step 5.
No -> Step 4.
4. Connect fibers between shelves as required, and check whether the alarm is cleared.
Yes -> End.
No -> Step 5.
5. Check whether the fibers connected to the faulty port and the peer device's port are loose (if so,
the green indicators of the ports are not lighted).
Yes -> Step 6.
No -> Step 7.
6. Secure the fibers, and check whether the alarm is cleared.
Yes -> End.
No -> Step 7.
7. Clean the both ends of the fibers by using the absorbent cotton soaked with absolute alcohol, and
Yes -> End.
No -> Step 8.
8. Replace the fibers with operational ones, and check whether the alarm is cleared.
Yes -> End.
No -> Step 9.
9. Replacing an Optical Module, and check whether the alarm is cleared.
Yes -> End.
No -> Step 10.
3.1.84 199007172 Port physical state restore

Alarm Information
Code:
199007172
Name:
Port physical state restore
Severity:
Warning
3-111
SJ-20140527134643-015|2015-03-31 (R1.1)
Type:
Equipment Alarm
Alarm Description
The board checks the STP, VLAN, and TRUNK status of the Ethernet port. This alarm is raised if
any of the status is abnormal.
The board executes self-healing operations automatically. If the port status recovers, this alarm
is cleared.
Probable Cause
l
The Ethernet port STP status is abnormal.
The Ethernet port's PVLAN or VLAN property is incorrect.
The Ethernet port's TRUNK property is incorrect.
System Impact
If the port cannot operate properly, the links on the control plane or the media plane are not stable or
even disconnected. Packets therefore get lost and NE services are affected.
Handling Suggestion
1. Wait for 30 seconds, and check whether the alarm is cleared.
Yes -> End.
No -> Step 2.
2. Run the SET NORMALRESETcommand to reset the board in accordance with "Rack number",
"Shelf number", "Slot number", and "CPU number" in the alarm information. Wait for 20 minutes,
Yes -> End.
No -> Step 3.
wait for 20 minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 4.
3.1.85 199007174 Connect port loopback

Alarm Information
Code:
199007174
Name:
Connect port loopback
Severity:
Minor
3-112
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Type:
Equipment Alarm
Alarm Description
This alarm is raised if the switching board detects that an interconnected port between two shelves
cannot operate properly because of a loopback on the port.
Probable Cause
l
Two cascading ports in two shelves of this board are interconnected.
Two cascade ports in two shelves between the left and right switching boards are interconnected.
A loopback is set on the port.
System Impact
The system can shield the storm caused by the loopback. However, if the ports are connected
incorrectly, the communication between different shelves is disconnected, which results in insufficient
bandwidth and service interruption.
Handling Suggestion
1. Remove the fiber or network cable in accordance with "Physical location" and "Port number" in
the alarm information, and check whether the alarm is cleared.
Yes -> Step 2.
No -> Step 3.
2. Connect the fiber or network cable as required, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3.1.86 199007425 Board self loop check abnormal

Alarm Information
Code:
199007425
Name:
Board self loop check abnormal
Severity:
Critical
Type:
Equipment Alarm
Alarm Description
After the board detects the fault, it performs the self-loop test. This alarm is raised if the self-loop test
fails.
3-113
SJ-20140527134643-015|2015-03-31 (R1.1)
Probable Cause
The board software or hardware is faulty.
System Impact
Services may be affected.
Handling Suggestion
1. Check whether the following alarm is raised on the board and its partner board:
199025631 LVDS link error
Yes -> Step 2.
No -> Step 3.
Yes -> End.
No -> Step 3.
Yes -> End.
No -> Step 4.
3.1.87 199015360 Mediaplane ran abnormal

Alarm Information
l
l
l
l

Name: Mediaplane ran abnormal
Alarm Description
This alarm is raised if packets get lost or error packets are detected within five periods after the CPU
transfers the loopback detection message received by the engine from the media plane.
Alarm Cause
Impact
The board cannot operate properly, and the service quality may be affected.
3-114
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Action
1. Replace the board(refer to Front Boards and Rear Boards Replacement) in accordance with
"Rack number", "Shelf number", and "Slot number" in the alarm information. When the board
operates properly for five minutes, check whether the alarm persists.
Yes -> Step 2.
No -> End.
3.1.88 199015618 Too many error frames received

Alarm Information
l
l
l
l

Name: Too many error frames received
Alarm Description
This alarm is raised if the number of damaged frames received by the port within four detection
periods exceeds threshold parameter "Threshold for the rate of bad frames(BadFramesThr)" of
"System Function(SystemFunction)" object.
This alarm is cleared if the number of damaged frames received by the port within a detection periods
is less than threshold parameter "Threshold for the rate of bad frames(BadFramesThr)" of "System
Function(SystemFunction)" object.
Alarm Cause
l
The port operating modes on both ends do not match each other.
The network cable or optical fiber on both ends is loose.
The specifications of the network cable/optical fiber of the port or the optical module do not
match each other.
The network cable/optical fiber or the optical module connected with the port is faulty.
The peer end transmits a message with CRC error or other packets that fail to be verified.
Impact
Service packets may be lost and thus the service quality is affected.
Action
3-115
SJ-20140527134643-015|2015-03-31 (R1.1)
1. Check whether the port type in the alarm information is set to "External Port".
Yes -> Step 2.
No -> Step 12.
2. Query "EthernetPort" of this object based on "subsystem ID", "Module", "Unit", and "Port number",
and check whether the "Duplex mode of the port (Duplex)", "Speed of the port (Speed)" and "Neg
mode of the port (NegotiateMode)" parameters are the same as those on the peer end.
Yes -> Step 4.
No -> Step 3.
3. Modify the "EthernetPort" parameter in accordance with actual requirements, or contact the peer
end for modification, and check whether the alarm is cleared.
Yes -> End.
No -> Step 4.
4. Remove/Install the optical fiber/network cable in accordance with "Port number" in the alarm
information, wait for five minutes, and then check whether the alarm is cleared.
Yes -> End.
No -> Step 5.
5. Check whether the network cable is connected tightly to the network interface, and whether the
optical fiber matches the optical module in accordance with the "Port number" in the alarm
information.
Yes -> Step 7.
No -> Step 6.
6. Connect the network cable tightly, or replace the unmatched optical fiber or optical module, and
Yes -> End.
No -> Step 7.
7. Check whether the network cable/optical fiber or optical module of this port is damaged in
accordance with "Port number" in the alarm information.
Yes -> Step 8.
No -> Step 9.
8. Replace the damaged network cable/optical fiber or refer to Replacing an Optical Module, and
Yes -> End.
No -> Step 9.
"Rack number", "Shelf number", and "Slot number" in the alarm information. After the board
Yes -> End.
No -> Step 10.
related alarms, for example sending an error frame.
Yes -> Step 11.
No -> Step 13.
11. Contact the maintenance personnel of the peer device to resolve the faults, and check whether
3-116
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Yes -> End.

No -> Step 13.
"Rack number", "Shelf number", and "Slot number" in the alarm information. After the board
Yes -> End.
No -> Step 13.
3.1.89 199019712 APS channel mismatch

Alarm Information
l
l
l
l

Name: APS channel mismatch
Alarm Description
This alarm is raised if the board detects that a response message is not received after an ASP
transmits a handover request to the peer end.
Alarm Cause
l
Optical fiber connection fault.
Incorrect APS parameter configuration.
Impact
The APS automatic switchover cannot be performed. If the operating optical port fails to operate
properly, the protecting optical port cannot protect the operation, and thus services carried on the
port may be interrupted.
Action
1. Query the APS parameters ("Protection Type(BackupMode)" and "Protection
direction(SwitchDirection)") of the "APS Group (ApsGroup)" object in accordance with the alarm
object, and check whether the parameters are set as required.
Yes -> Step 3.
No -> Step 2.
2. Change the APS configuration as required, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3-117
SJ-20140527134643-015|2015-03-31 (R1.1)
3. Contact the maintenance personnel of the peer end to check whether the APS configuration is
in accordance with the actual requirements.
Yes -> End.
No -> Step 4.
4. Inform the maintenance personnel of the peer device to change the APS configuration, and
Yes -> End.
No -> Step 5.
5. Check whether the cables are correctly connected (the protection ports and working ports of the
local and peer devices must be interconnected separately).
Yes -> Step 7.
No -> Step 6.
6. Connect the cables as required, and check whether the alarm is cleared.
Yes -> End.
No -> Step 7.
3.1.90 199019713 APS mode mismatch

Alarm Information
l
l
l
l

Name: APS mode mismatch
Alarm Description
This alarm is raised if the board detects that the operation mode of the local APS is different from
that of the peer APS.
Alarm Cause
l
Optical fiber connection fault.
Incorrect APS parameter configuration.
Impact
l
If the optical fiber is connected correctly, and the optical port operates properly, services are
not affected.
If the operating optical interface is faulty, the APS may cause the optical fiber interface not to
work, and thus the involved services are interrupted on this interface.
3-118
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Action
1. Query the APS parameters ("Protection Type(BackupMode)" and "Protection
direction(SwitchDirection)") of the "APS Group (ApsGroup)" object in accordance with the alarm
object, and check whether the parameters are set as required.
Yes -> Step 3.
No -> Step 2.
2. Change the APS configuration as required, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3. Contact the maintenance personnel of the peer end to check whether the APS configuration is
in accordance with the actual requirements.
Yes -> End.
No -> Step 4.
4. Inform the maintenance personnel of the peer device to change the APS configuration, and
Yes -> End.
No -> Step 5.
5. Check whether cables are correctly connected (the protection ports and working ports of the local
and peer devices must be interconnected separately).
Yes -> Step 7.
No -> Step 6.
6. Connect the cables as required, and check whether the alarm is cleared.
Yes -> End.
No -> Step 7.
3.1.91 199019715 APS channel between master and slave board

gets errors
Alarm Information
l
l
l
l

Name: APS channel between master and slave board gets errors
Alarm Description
This alarm is raised if the board detects a fault on the APS channel between the active and standby
boards.
3-119
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Cause
l
The APS channel between the active and standby boards has hardware faults.
The rear board has a fault.
Impact
The APS switchover function is affected, and thus system reliability is reduced.
Action
1. Reset the faulty board. After the board is powered on, wait for three minutes, and check whether
Yes -> End.
No -> Step 2.
2. Reset the partner board. After the board is powered on, wait for three minutes, and check
Yes -> End.
No -> Step 3.
Replacement). After the board is powered on, wait for three minutes, and check whether the
alarm is cleared.
Yes -> End.
No -> Step 4.
4. Replace the partner board with an operational one. After the board is powered on, wait for three
Yes -> End.
No -> Step 5.
3.1.92 199023050 Fan device absent

Alarm Information
l
l
l
l

Name: Fan device absent
Alarm Description
This alarm is raised if the fan subrack is unavailable, or the communication of the fan or the shelf
management board is lost.
3-120
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
l
The fan subrack is unavailable.
The connection between the fan subrack and the rear board is poor.
The communication between the fan and the shelf management board is abnormal.
Impact
l
The subrack of the fan is unavailable, so the temperature of the board is increased, and then the
temperature of the board is increased. The hardware of the board is affected, the lifespan of
the components of the board are reduced, so the system cannot operate properly or stably, and
The communication between the fan subrack and the shelf management module is abnormal, so
the fan management function is invalid, the speed of the fan is set to the maximum, the system
noise is increased, and the lifespan of the fan is reduced.
Action
1. Check whether the fan unit is properly installed in accordance with the "Rack number", "Shelf
number", and "Slot number" in the alarm information.
Yes -> Step 2.
No -> Step 3.
2. Remove and install the fan unit in accordance with the "Rack number", "Shelf number", and
"Slot number" in the alarm information, and then check whether the alarm is cleared, refer to
Fan Subrack Replacement.
Yes -> End.
No -> Step 3.
3. Replace the fan unit in accordance with the "Rack number", "Shelf number", and "Slot number"
in the alarm information, and then check whether the alarm is cleared, refer to Fan Subrack
Replacement.
Yes -> End.
No -> Step 5.
4. Install the fan unit in accordance with the "Rack number", "Shelf number", and "Slot number"
in the alarm information, and then check whether the alarm is cleared, refer to Fan Subrack
Replacement.
Yes -> End.
No -> Step 5.
5. Run the SET NORMALCHANGE command to switch over the boards in accordance with the
"Rack number", "Shelf number", "Slot number", and "CPU number" in the alarm information, and
Yes -> End.
No -> Step 6.
6. Run the SET NORMALCHANGE command to reset the active and standby CMM boards in
accordance with the "Rack number", "Shelf number", "Slot number", and "CPU number" in the
alarm information, and check whether the alarm is cleared.
Yes -> End.
3-121
SJ-20140527134643-015|2015-03-31 (R1.1)
No -> Step 7.
3.1.93 199023051 Power unit absent

Alarm Information
l
l
l
l

Name: Power unit absent
Alarm Description
This alarm is raised if the power module is unavailable, or the communication between the power
supply module and the shelf management board is abnormal.
Alarm Cause
l
The power module is unavailable.
The connection between the power module and the rear board is poor.
The communication between the power supply module and the shelf management board is
abnormal.
Impact
l
If one power supply module is unavailable, the power supply of the shelf is not affected.
However, the power supply redundancy is lost. If two power supply modules are unavailable, the
entire shelf is powered off.
The communication between the power supply module and the shelf management module is
abnormal, so the power supply management function is invalid, and the system cannot detect the
power supply fault.
3-122
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Action
1. Check whether the power module is properly installed in accordance with the "Rack number",
"Shelf number", and "Slot number" in the alarm information.
Yes -> Step 2.
No -> Step 3.
2. Remove and install the power module in accordance with the "Rack number", "Shelf number",
and "Slot number" in the alarm information, and then check whether the alarm is cleared, refer to
Power Box Replacement.
Yes -> End.
No -> Step 3.
3. Replace the power module in accordance with the "Rack number", "Shelf number", and "Slot
number" in the alarm information, and then check whether the alarm is cleared, refer to Power
Box Replacement.
Yes -> End.
No -> Step 5.
4. Install the power module in accordance with the "Rack number", "Shelf number", and "Slot
number" in the alarm information, and then check whether the alarm is cleared, refer to Power
Box Replacement.
Yes -> End.
No -> Step 5.
5. Run the SET NORMALCHANGE command to switch over the boards in accordance with the
Yes -> End.
No -> Step 6.
6. Run the SET NORMALCHANGE command to reset the active and standby CMM boards in
accordance with the "Rack number", "Shelf number", "Slot number", and "CPU number" in the
alarm information, and check whether the alarm is cleared.
Yes -> End.
No -> Step 7.
3.1.94 199023106 Board self-check failed when power on

Alarm Information
l
l
l
l

Name: Board self-check failed when power on
3-123
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Description
This alarm is raised if the self-test of a device fails when the board is powered on.
Alarm Cause
The board is faulty.
Impact
Action
1. Check whether the ejector levers of the board are closed.
Yes -> Step 3.
No -> Step 2.
2. Remove and reinstall the board,and close the ejector levers,refer to Removing a Board. Wait for
five minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3.1.95 199025602 Abnormal half-fixed connection changes

Alarm Information
l
l
l
l

Name: Abnormal half-fixed connection changes
Alarm Description
This alarm is raised if the CS has an incorrect connection.
Alarm Cause
l
The board input clock or the phase-lock loop is abnormal.
The switching chip on the board is faulty.
Impact
Services using CS are affected, for example, voice calls and signaling links.
3-124
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Action
Yes -> Step 2.
No -> Step 3.
2. Handle the above alarms. Wait for ten minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
"Shelf number", "Slot number", and "CPU number" in the alarm information. After the board starts
to operate properly, wait for ten minutes, and check whether the alarm is still reported.
Yes -> Step 4.
No -> End.
4. Replace the board with an operational one(refer to Front Boards and Rear Boards Replacement).
After the board starts to operate properly, wait for ten minutes, and check whether the alarm
is still reported.
Yes -> Step 5.
No -> End.
3.1.96 199025603 Trunk is looped back

Alarm Information
Code:
199025603
Name:
Trunk is looped back
Severity:
Minor
Type:
Equipment Alarm
Alarm Description
Selfloop is detected on the cables connected to trunks on the board.
Probable Cause
l
The user performs a local loopback test command for the trunk.
A remote loopback is set for the trunk by the peer end.
A physical loopback exists on the transmission line.
Peer board hardware is faulty.
3-125
SJ-20140527134643-015|2015-03-31 (R1.1)
System Impact
Services on the trunk on which a loopback exists are interrupted. For the voice call service, the
peer user cannot hear the local user.
Handling Suggestion
1. [A2015]Run the START DTM command to check whether the trunk has local loopback in
number", "Primary device index", and "Secondary device index" in the alarm information.
Yes -> Step 2.
No -> Step 3.
2. [A2016]Cancel the loopback on the trunk, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3. Contact the maintenance personnel of the peer device, and check whether a remote loopback is
configured for the corresponding trunk.
Yes -> Step 4.
No -> Step 5.
4. Inform the maintenance personnel of the peer device to cancel the remote loopback for the
trunk, and check whether the alarm is cleared.
Yes -> End.
No -> Step 5.
5. Contact the maintenance personnel of the transmission device to resolve the loopback in
transmission lines, and check whether the alarm is cleared.
Yes -> End.
No -> Step 6.
to operate properly, wait for ten minutes, and check whether the alarm persists.
Yes -> Step 7.
No -> End.
7. Replace the board(refer to Front Boards and Rear Boards Replacement). After the board starts
to operate properly, wait for ten minutes, and check whether the alarm persists.
Yes -> Step 8.
No -> End.
8. Contact the maintenance personnel of the peer device to resolve the hardware fault of the trunk
board, and check whether the alarm is cleared.
Yes -> End.
No -> Step 9.
3-126
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.97 199025604 Cross-linked trunk alarm

Alarm Information
Code:
199025604
Name:
Cross-linked trunk alarm
Severity:
Minor
Type:
Equipment Alarm
Alarm Description
This alarm is raised if the cable of the trunk has mismatched wires. Mismatched wires refer to that
multiple trunk cables are crossly and incorrectly connected. In normal cases, a receiving and a
sending is a pair of cable, and b receiving and b sending is another pair of cable. If a receiving and b
sending are connected, this pair of cable is called mismatched wires.
Probable Cause
l
Mismatched wires exist on the transmission line.
Peer board hardware is faulty.
System Impact
Services on the trunk on which mismatched wires exist are affected. For the voice call service,
one-way communication may occur.
Handling Suggestion
1. Contact the maintenance personnel of the transmission device to resolve the situation where
the sending and receiving ends of the transmission cable are inversely connected, and check
Yes -> End.
No -> Step 2.
to operate properly, wait for ten minutes, and check whether the alarm is still reported.
Yes -> Step 3.
No -> End.
3. Replace the board with an operational one(refer to Front Boards and Rear Boards Replacement).
After the board starts to operate properly, wait for ten minutes, and check whether the alarm
is still reported.
Yes -> Step 4.
No -> End.
3-127
SJ-20140527134643-015|2015-03-31 (R1.1)
4. Contact the maintenance personnel of the peer device to resolve the hardware fault of the trunk
board, and check whether the alarm is cleared.
Yes -> End.
No -> Step 5.
3.1.98 199025856 Rack temperature is higher than high threshold

Alarm Information
l
l
l
l

Name: Rack temperature is higher than high threshold
Alarm Description
This alarm is raised if the temperature of the rack exceeds the upper threshold.
For the PDU whose voltage type is 48V, the voltage range is 36V-72V, and the recommended value is
57V.For the PDU whose voltage type is 60V, the voltage range is 45V-72V, and the recommended
value is 69V.
Alarm Cause
l
The alarm threshold is not properly set.
The fan is faulty.
The ventilation of both the air intake and air outlet is not adequate.
The temperature in the equipment room is too high.
Impact
The environmental temperature is too high, so the board may operate abnormally, the components of
the board may be damaged, and services may be affected.
Action
1. Query the "The maximal value of the rack temperature (RackTempHigh)" parameter of the "Rack
(Rack)" object in accordance with "Rack number" in the alarm information, and check whether the
"The maximal value of the rack temperature" parameter is properly configured (it is recommend
to set the value to 70).
Yes -> Step 3.
No -> Step 2.
2. Modify the value of the "The maximal value of the rack temperature (RackTempHigh)" parameter,
Yes -> End.
3-128
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
No -> Step 3.
3. Check whether the shelf fan in the rack has any of the following alarms in accordance with
the "Rack number" in the alarm information.
199030734 Velocity of fan is lower than lower-critical threshold
199023050 Fan device absent
Yes -> Step 4.
No -> Step 5.
4. Handle the above alarms, wait for 1015 minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 5.
5. Check whether the shelf in the rack is an ATCA shelf in accordance with the "Rack number" in
Yes -> Step 7.
No -> Step 9.
6. Pull out the dust filter of the shelf, and check whether it is blocked, refer to Controller Rack.
Yes -> Step 8.
No -> Step 9.
7. Clean the dust filter, and insert it into the shelf after it becomes dry. Wait for 1015 minutes, and
Yes -> End.
No -> Step 7.
8. Check the environment temperature of the shelf, ensure that the temperature is in the range from
0C to 40C, wait for 510 minutes, and then check whether the alarm is cleared.
Yes -> End.
No -> Step 10.
3.1.99 199025857 Rack temperature is lower than low threshold

Alarm Information
l
l
l
l

Name: Rack temperature is lower than low threshold
Alarm Description
This alarm is raised if the temperature of the rack is lower than the lower threshold.
Alarm Cause
l
The temperature of the equipment room is too low.

3-129
SJ-20140527134643-015|2015-03-31 (R1.1)
Impact
The environmental temperature is too low, so the board may operate abnormally, the components of
Action
1. Check the "The maximal value of the rack temperature (RackTempHigh)" parameter in
accordance with "Rack number" in the alarm information, query the "Rack (Rack)" object, and
check whether the "The minimal value of the rack temperature" parameter is properly configured
(it is recommend to set the value to 0).
Yes -> Step 3.
No -> Step 2.
2. Modify the value of the "The minimal value of the rack temperature (RackTempLow)" parameter,
Yes -> End.
No -> Step 3.
3. Check the environment temperature of the rack, ensure that the temperature is in the range of
0 to 40, wait for five to ten minutes, and then check whether the alarm is cleared.
Yes -> End.
No -> Step 4.
3.1.100 199025858 Room temperature is higher than high threshold

Alarm Information
l
l
l
l

Name: Room temperature is higher than high threshold
Alarm Description
This alarm is raised if the temperature of the equipment room exceeds the upper threshold.
Alarm Cause
l
The temperature of the equipment room is too high.
Impact
The environmental temperature is too high, so the board may operate abnormally, the components of
3-130
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Action
1. Query the "Rack (Rack)" object in accordance with "Rack number" in the alarm information,
and check the "The maximal value of the rack temperature (RackTempHigh)" parameter, and
check whether the "The maximal check value of the room temperature" parameter is properly
configured (it is recommend to set the value to 40).
Yes -> Step 3.
No -> Step 2.
2. Modify the value of the "The maximal check value of the room temperature (RoomTempHigh)"
parameter, and then check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3. Check the environment temperature in the equipment room, ensure that the temperature is in the
range of 0 to 40, wait for five to ten minutes, and then check whether the alarm is cleared.
Yes -> End.
No -> Step 4.
3.1.101 199025859 Room temperature is lower than low threshold

Alarm Information
l
l
l
l

Name: Room temperature is lower than low threshold
Alarm Description
This alarm is raised if the temperature of the equipment room is lower than the lower threshold.
Alarm Cause
l
The temperature of the equipment room is too low.
The temperature sensor is not connected.
Impact
The environmental temperature is too low, so the board may operate abnormally, the components of
3-131
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
1. Check whether the room temperature sensor on the rack needs to be connected in accordance
with the actual situation and the "Rack number" in the alarm information.
Yes -> Step 3.
No -> Step 2.
2. Query the object "Rack (Rack)" in accordance with the "Rack number" in the alarm information,
cancel the configuration of the parameter "The room temperature and humidity sensors'
configuration (RoomTempSet)", and then check whether the alarm is cleared.
Yes -> End.
No -> Step 6.
3. Query the "Rack (Rack)" object in accordance with "Rack number" in the alarm information, check
the "The maximal value of the rack temperature (RackTempHigh)" parameter, and check whether
the "The maximal check value of the room temperature" parameter is properly configured (it is
recommend to set the value to 0).
Yes -> Step 5.
No -> Step 4.
4. Modify the value of the "The minimal check value of the room temperature (RoomTempHigh)"
Yes -> End.
No -> Step 5.
5. Check the environment temperature in the equipment room, ensure that the temperature is in the
range of 0 to 40, wait for five to ten minutes, and then check whether the alarm is cleared.
Yes -> End.
No -> Step 6.
6.
3.1.102 199025860 Voltage is higher than high threshold

Alarm Information
l
l
l
l

Name: Voltage is higher than high threshold
Alarm Description
This alarm is raised if any voltage exceeds the upper threshold.
For the PDU whose voltage type is 48V, the voltage range is 36V-72V, and the recommended value
is 42V.
For the PDU whose voltage type is 60V, the voltage range is 45V-72V, and the recommended value
is 54V.
3-132
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
l
The real input voltage is too high.
Impact
The input voltage is too high, so the components of the board may be damaged, the board cannot
operate properly, and services are interrupted.
Action
check whether the "The maximal value of the voltage" parameter is properly configured (the
recommended threshold for 48 V power supply is 57, and the recommended threshold for 60 V
power supply is 72).
Yes -> Step 3.
No -> Step 2.
2. Modify the value of the "The maximal value of the voltage (VolHigh)" parameter, and then check
Yes -> End.
No -> Step 3.
3. Contact the power induction department in accordance with the voltage in the alarm information
to examine and repair the corresponding power supply. Wait for three minutes after the voltage is
steady, and then check whether the alarm is cleared.
Yes -> End.
No -> Step 4.
3.1.103 199025861 Voltage is lower than low threshold

Alarm Information
l
l
l
l

Name: Voltage is lower than low threshold
3-133
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Description
This alarm is raised if any voltage is less than the lower threshold.
For the PDU whose voltage type is 48V, the low voltage range is from 36V to 72V, and the
recommended value is 42V.
For the PDU whose voltage type is 60V, the low voltage range is from 45V to 75V, and the
recommended value is 54V.
Alarm Cause
l
The input voltage is too low.
Impact
The board may be power off and services are interrupted.
Action
check whether the "The minimal value of the voltage" parameter is properly configured (the
recommended threshold for 48 V power supply is 40, and the recommended threshold for 60 V
power supply is 50).
Yes -> Step 3.
No -> Step 2.
2. Modify the value of the "The minimal value of the voltage (VolLow)" parameter, and then check
Yes -> End.
No -> Step 3.
3. Contact the power induction department in accordance with the voltage in the alarm information
to examine and repair the corresponding power supply. Wait for three minutes after the voltage is
steady, and then check whether the alarm is cleared.
Yes -> End.
No -> Step 4.
3.1.104 199025862 Humidity is higher than high threshold

Alarm Information
l
l
l
l

Name: Humidity is higher than high threshold
3-134
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Description
This alarm is raised if the humidity of the equipment room exceeds the upper threshold.
Alarm Cause
l
The humidity of the equipment room is too high.
Impact
The equipment room is humid. If a device operates in such an environment for a long time, the board
may operate improperly, and all service running on the board will be interrupted.
Action
check the "The maximal value of the rack temperature (RackTempHigh)" parameter, and check
whether the "The maximal check value of the room humidity" parameter is properly configured (it
is recommend to set the value to 90).
Yes -> Step 3.
No -> Step 2.
2. Modify the value of the "The maximal check value of the room humidity (RoomHumHigh)"
Yes -> End.
No -> Step 3.
3. Check the actual room humidity, take effective actions if the humidity is too high, and then check
Yes -> End.
No -> Step 4.
3.1.105 199025863 Humidity is lower than low threshold

Alarm Information
l
l
l
l

Name: Humidity is lower than low threshold
Alarm Description
This alarm is raised if the humidity of the equipment room is lower than the lower threshold.
3-135
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Cause
l
The threshold is not properly set.
The humidity of the equipment room is too low.
The equipment humidity sensor is not connected.
Impact
The environment of the equipment room is dry, so static electricity is easy to occur. If the device or the
antistatic measure is not ready during the operation and maintenance, the board may be damaged.
Action
1. Check whether the room humidity sensor on the rack needs to be connected in accordance with
the actual situation and the "Rack number" in the alarm information.
Yes -> Step 3.
No -> Step 2.
cancel the configuration of the parameter "The room temperature and humidity sensors'
configuration (RoomTempSet)", and then check whether the alarm is cleared.
Yes -> End.
No -> Step 6.
3. query the "Rack (Rack)" object in accordance with "Rack number" in the alarm information,
check the "The maximal value of the rack temperature (RackTempHigh)" parameter, and check
whether the "The minimal check value of the room humidity" parameter is properly configured (it
is recommend to set the value to 20).
Yes -> Step 5.
No -> Step 4.
4. Modify the value of the "The minimal check value of the room humidity (RoomHumLow)"
Yes -> End.
No -> Step 5.
5. Check the actual room humidity, take effective actions if the humidity is too high, and then check
Yes -> End.
No -> Step 6.
3.1.106 199025865 Rack door access control alarm or other monitor

alarm
Alarm Information
l
l

Name: Rack door access control alarm or other monitor alarm
3-136
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
l
l

Alarm Description
1. This alarm is raised if the door of the rack is opened.
2. If this device is connected to the third-party device, the third-party monitoring alarm is raised.
Alarm Cause
l
The door of the rack is open.
The third-party device is faulty.
Impact
Safety risks may exist.
Action
1. Check whether the door control or a third-party device needs to be connected in accordance with
the actual situation and the "Rack number" in the alarm information.
Yes -> Step 3.
No -> Step 2.
2. Query the "Rack (Rack)" object in accordance with the "Rack number" and "Door index", cancel
the configurations of the parameters "Gate control's configuration 1 (Gate1AlarmSet)" to "Gate
control's configuration 6 (Gate6AlarmSet)", and then check whether the alarm is cleared.
Yes -> End.
No -> Step 5.
3. Check whether the rack is properly closed in accordance with the "Rack number" and "Door
index" in the alarm information.
Yes -> Step 5.
No -> Step 4.
4. Close the door of the rack, and then check whether this alarm is cleared.
Yes -> End.
No -> Step 5.
3.1.107 199025866 Smoke alarm

Alarm Information
l
l
l
l

Name: Smoke alarm
3-137
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Description
This alarm is raised if the equipment room has smoke.
Alarm Cause
l
The smoke in the equipment room exceeds the standard value.
The smoke sensor is faulty.
Impact
Safety risks may exist, and the equipment room is easy to catch fire.
Action
1. Check whether the smoke sensor on the rack needs to be connected in accordance with the
actual situation and the "Rack number" in the alarm information.
Yes -> Step 3.
No -> Step 2.
cancel the configuration of the parameter "Smoke sensor's configuration (SmokeSensorSet)",
Yes -> End.
No -> Step 6.
3. Check whether the equipment room has smoke.
Yes -> Step 4.
No -> Step 5.
4. Clean the smoke from the equipment room, and check whether the alarm is cleared.
Yes -> End.
No -> Step 5.
3.1.108 199025867 Infrared alarm

Alarm Information
l
l
l
l

Name: Infrared alarm
Alarm Description
This alarm is raised if heat is detected.
3-138
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
l
A heat source, for example, animals or persons, is near the sensor.
The sensor is faulty.
Impact
Safety risks may exist.
Action
1. Check whether the infrared sensor on the rack needs to be connected in accordance with the
actual situation and the "Rack number" in the alarm information.
Yes -> Step 3.
No -> Step 2.
cancel the configuration of the parameter "Infrared sensor's configuration (InfaredSet)", and then
Yes -> End.
No -> Step 6.
3. Check whether there is any heat source around the infrared sensor.
Yes -> Step 4.
No -> Step 4.
4. Remove the heat source, and then check whether the alarm is cleared.
Yes -> End.
No -> Step 5.
3.1.109 199025868 Lightning alarm

Alarm Information
l
l
l
l

Name: Lightning alarm
Alarm Description
This alarm is raised if the lightning protection module is faulty.
Alarm Cause
The lightning protection device is faulty.
3-139
SJ-20140527134643-015|2015-03-31 (R1.1)
Impact
The lightning protection system is faulty. The board may be damaged by the lightning.
Action
1. Replace the lightning protection device (PDUM board)(refer to Replacing the PDUM) and check
Yes -> End.
No -> Step 2.
3.1.110 199025869 Power switch alarm

Alarm Information
l
l
l
l

Name: Power switch alarm
Alarm Description
This alarm is raised if the air circuit breaker is off.
Alarm Cause
l
The air circuit breaker is triggered and the back-end system requires to detect this breaker.
The air circuit breaker is faulty.
Impact
The power supply of the shelf corresponding to the switch may be affected.
Action
1. Check whether the corresponding air switch corresponding to the rack is connected in accordance
with actual situations and "Rack number", "Air switch group number", and "Air switch index" in
Yes -> Step 3.
No -> Step 2.
2. Query the "Rack (Rack)" object in accordance with the "Rack number" and "Air switch group
number", cancel the configurations of the parameters "Air switch configuration 1 (AirSwitch1Set)"
to "Air switch configuration 20 (AirSwitch20Set)", and then check whether the alarm is cleared.
Yes -> End.
No -> Step 6.
3-140
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3. Check whether the corresponding air switch is disconnected.

Yes -> Step 4.
No -> Step 5.
4. Close the air switch, and then check whether the alarm is cleared.
Yes -> End.
No -> Step 5.
3.1.111 199025870 Electrical source configuration does not

according with physical
Alarm Information
l
l
l
l

Name: Electrical source configuration does not according with physical
Alarm Description
This alarm is raised through the CMM board if the PDU detects that the configuration of the power
type is not consistent with the real type.
Alarm Cause
The power type configured in the database is not consistent with the real power type.
Impact
The NE may fail to operate properly.
Action
1. Query the "Voltage type" parameter of the "Rack" object in accordance with "Rack number" in the
alarm information, and check whether the parameter is correct.
Yes -> Step 3.
No -> Step 2.
2. Modify the "Voltage type" parameter as required. Check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3. Check whether the power supply for the rack is applicable (-48 V in normal areas and -60 V in
special areas).
Yes -> Step 5.
No -> Step 4.
4. Replace the power supply for the rack as required. Check whether the alarm is cleared.
3-141
SJ-20140527134643-015|2015-03-31 (R1.1)
Yes -> End.

No -> Step 5.
3.1.112 199029184 SNTP failed to synchronize time

Alarm Information
l
l
l
l

Name: SNTP failed to synchronize time
Alarm Description
This alarm is raised if the time of the NE and that of the NTP server cannot be synchronized.
Alarm Cause
l
The source address of the SNTP client or the address of the NTP server is incorrect.
The NTP server is faulty.
Network communication fault.
Impact
The system time of the NE cannot be synchronized with that of the NTP server, so the time accuracy
of the NE cannot be guaranteed.
Action
1. Wait for three minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 2.
2. Check whether "IP address of SNTP server (SntpServer)" of the "Operation Maintenance
Configuration" object meets the actual requirements.
Yes -> Step 4.
No -> Step 3.
3. Modify "IP address of SNTP server (SntpServer)" of the "Operation Maintenance Configuration"
object, and check whether the alarm is cleared.
Yes -> End.
No -> Step 4.
4. Run the protocol stack command to check whether the active and standby addresses of the
NTP server can be pinged.
Yes -> Step 5.
No -> Step 7.
3-142
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
5. Check whether all devices, such as the firewall, between this device and the NTP server, screen
the messages from port 123.
Yes -> Step 6.
No -> Step 7.
6. Cancel the screen function on messages from port 123 for related devices, such as the firewall,
Yes -> End.
No -> Step 7.
7. Contact the maintenance personnel of the peer device to check whether the active/standby
NTP servers are faulty.
Yes -> Step 8.
No -> Step 9.
8. Contact the maintenance personnel of the peer device to resolve the faults of the active/standby
NTP server, and check whether the alarm is cleared.
Yes -> End.
No -> Step 9.
9. Check whether any other available NTP servers that can be used to synchronize the network
time of the NE exist.
Yes -> Step 10.
No -> Step 11.
10. Modify "IP address of SNTP server (SntpServer)" of the "Operation Maintenance Configuration"
Yes -> End.
No -> Step 11.
3.1.113 199030722 Temperature is lower than lower-critical

threshold
Alarm Information
l
l
l
l

Name: Temperature is lower than lower-critical threshold
Alarm Description
This alarm is raised if the temperature of the components (such as CPU and memory) of a board is
lower than the lower-critical threshold.
3-143
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Cause
This alarm is raised if the environmental temperature of the system is lower than the normal range
(less than 10 below zero).
Impact
When the temperature is lower than the lower-critical threshold, this fault has negative influence on
the hardware performance of the system. The system cannot operate properly or stably, and services
may be affected.
Action
1. Check the environment temperature of the shelf, ensure that the temperature is in the range of
0 to 40, wait for 5-10 minutes, and then check whether the alarm is cleared.
Yes -> End.
No -> Step 2.
3.1.114 199030723 Temperature is lower than lower-non-recoverable

threshold
Alarm Information
l
l
l
l

Name: Temperature is lower than lower-non-recoverable threshold
Alarm Description
lower than the lower-non-recoverable threshold. Handle it immediately.
Alarm Cause
This alarm is raised if the environmental temperature of the system is lower than the normal range
(less than 10 below zero).
Impact
When the temperature is lower than the lower-non-recoverable threshold, the system hardware may
be damaged. The hardware may not be recovered, and services are affected.
3-144
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Action
1. Check the environment temperature of the shelf, ensure that the temperature is in the range of
0 to 40, wait for 5-10 minutes, and then check whether the alarm is cleared.
Yes -> End.
No -> Step 2.
3.1.115 199030725 Temperature is higher than upper-critical

threshold
Alarm Information
l
l
l
l

Name: Temperature is higher than upper-critical threshold
Alarm Description
higher than the critical upper threshold. Handle it as soon as possible.
Alarm Cause
l
The environmental temperature of the system is higher than the normal range (higher than 40).
The fan of the shelf does not operate properly.
The filter is not cleaned for a long time.
The free slots of the shelf are not installed with blank panels.
Impact
If the temperature is higher than the critical high threshold, the temperature has negative influence on
the hardware performance of the system. The system cannot operate properly or stably, and services
may be affected. If the alarm persists for a long time, components may be damaged.
3-145
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
1. Locate the shelf where the board with abnormal temperature is located in accordance with the
"Rack number" and Shelf number" in the alarm information, and check whether the fan of the
shelf has any of the following alarms:
Yes -> Step 2.
No -> Step 3.
2. Handle the above fan alarm. Wait for 510 minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
Yes -> End.
No -> Step 4.
4. Check whether the free slot of the shelf is installed with a blank panel. If not, install a blank panel,
Yes -> End.
No -> Step 5.
5. Query the "Shelf Type(ShelfType)" parameter of the "Shelf(Shelf)" object in accordance with the
"Rack number" in the alarm information, and check whether the shelf type is ATCA.
Yes -> Step 6.
No -> Step 8.
6. Air Filter Replacement, and check whether it is blocked.
Yes -> Step 7.
No -> Step 8.
7. Clean the dust filter, and insert it into the shelf after it becomes dry. Wait for 5-10 minutes, and
Yes -> End.
No -> Step 8.
3.1.116 199030726 Temperature is higher than upper-non-recov

erable threshold
Alarm Information
l
l
l
l

Name: Temperature is higher than upper-non-recoverable threshold
3-146
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Description
higher than the upper-non-recoverable threshold. Handle it immediately.
Alarm Cause
l
The environmental temperature of the system is higher than the normal range (higher than 40).
The fan of the shelf does not operate properly.
The filter is not cleaned for a long time.
The free slots of the shelf are not installed with blank panels.
Impact
If the temperature is higher than the upper-non-recoverable threshold, the hardware of the board
may be damaged. The board may be powered off automatically (it must be configured through
Configuration for High Temperature).The system cannot operate properly and services are affected.
Action
Yes -> Step 2.
No -> Step 3.
Yes -> End.
No -> Step 3.
Yes -> End.
No -> Step 4.
Yes -> End.
No -> Step 5.
"Rack number" in the alarm information and check whether the shelf type is ATCA.
Yes -> Step 6.
No -> Step 8.
Yes -> Step 7.
No -> Step 8.
3-147
SJ-20140527134643-015|2015-03-31 (R1.1)
Yes -> End.
No -> Step 8.
3.1.117 199030728 Voltage is lower than lower-critical threshold

Alarm Information
l
l
l
l

Name: Voltage is lower than lower-critical threshold
Alarm Description
This alarm is raised if the voltage is lower than the critical low threshold. Handle the fault as soon
as possible.
Alarm Cause
l
The output voltage of the shelf power module is abnormal.
The power module of a board is faulty.
The fan power is faulty.
A rear board is faulty.
The rack power is faulty.
Impact
This alarm is raised because the voltage is not stable. If the voltage is lower than the lower-critical
threshold, the board may be powered off, the fan speed is reduced, and the system cannot operate
properly.
Action
3-148
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
1. Check whether the following alarm exists in accordance with "Rack number" in the alarm
information.
199025861 Voltage is lower than low threshold
Yes -> Step 2.
No -> Step 3.
Yes -> End.
No -> Step 3.
3. Query the "Shelf Type (ShelfType)" parameter of the "Shelf (Shelf)" object to check whether the
shelf type is ETCA in accordance with "Rack number" and "Shelf number" in the alarm information.
Yes -> Step 4.
No -> Step 8.
4. Check whether the rack and shelf where the alarm source is located have the following alarms.
In accordance with "Rack number" and "Shelf number" in the alarm information, check whether
"Slot number" in these alarms is "36 (shelf)".
199030728 Voltage is lower than lower-critical threshold
199030729 Voltage is lower than lower-non-recoverable threshold
Yes -> Step 5.
No -> Step 12.
5. Power-on Procedures. Check whether the voltage is in the range of error tolerance (For -48 V
rated voltage, the error tolerance ranges from -40 V through -57 V. For -60 V rated voltage, the
error tolerance ranges from -50 V through -72 V.)
Yes -> Step 6.
No -> Step 7.
6. Replace the CDM module in the shelfrefer to ECDM Replacementin accordance with "Rack
number", "Shelf number", and "Slot number" in the alarm information. Check whether the alarm
is cleared.
Yes -> End.
No -> Step 12.
7. Contact the power supply department to check external circuits, and then check whether the
alarm is cleared after the voltage is steady.
Yes -> End.
No -> Step 12.
8. Check whether slots 34 and 35 (power supply) have the following alarms in accordance with
"Rack number" and "Shelf number" in the alarm information:
Yes -> Step 9.
No -> Step 12.
9. Measure the input voltage of the shelf with a multimeter. Check whether the voltage is in the
range of error tolerance (For -48 V rated voltage, the error tolerance ranges from -40 V through
-57 V. For -60 V rated voltage, the error tolerance ranges from -50 V through -72 V.)
Yes -> Step 10.
No -> Step 11.
3-149
SJ-20140527134643-015|2015-03-31 (R1.1)
10. Replace the power module in the shelf (refer toPower Box Replacement) in accordance with
"Rack number" and "Shelf number" in the alarm information. After two minutes, check whether
Yes -> End.
No -> Step 12.
11. Contact the electric power department to repair the external circuits. After the voltage is steady,
Yes -> End.
No -> Step 12.
12. Check whether "Slot number" in the alarm information is "31", "32", and "33" (fan).
Yes -> Step 13.
No -> Step 14.
13. Replace the fan subrack in the rack(refer to Fan Subrack Replacement) in accordance with "Rack
number", "Shelf number", and "Slot number" in the alarm information. Wait for two minutes.
After the fan subrack operates properly (the RUN indicator flashes at 1 Hz), check whether
Yes -> End.
No -> Step 18.
14. Check whether "Slot number" in the alarm information is in the range of 1 through 28 (board).
Yes -> Step 15.
No -> Step 16.
"Rack number", "Shelf number", and "Slot number" in the alarm information. Wait for two
minutes. After the board operates properly (the OK indicator flashes at 1 Hz), check whether
Yes -> End.
No -> Step 16.
16. Check whether "Slot number" in the alarm information is either "29" or "30" (CMM board).
Yes -> Step 17.
No -> Step 18.
17. Replace the CMM board in accordance with "Rack number", "Shelf number", and "Slot number"
in the alarm information. Wait for three minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 18.
3.1.118 199030729 Voltage is lower than lower-non-recoverable

threshold
Alarm Information
l
l

Name: Voltage is lower than lower-non-recoverable threshold
3-150
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
l
l

Alarm Description
This alarm is raised if the voltage is lower than the lower-non-recoverable threshold. Handle the fault
as soon as possible.
Alarm Cause
l
Impact
This alarm is raised because the voltage is not stable. If the voltage is lower than the
lower-non-recoverable threshold, the board may be powered off, the fan speed is reduced, and
the system cannot operate properly.
Action
information.
Yes -> Step 2.
No -> Step 3.
Yes -> End.
No -> Step 3.
Yes -> Step 4.
No -> Step 8.
Yes -> Step 5.
No -> Step 12.
Yes -> Step 6.
3-151
SJ-20140527134643-015|2015-03-31 (R1.1)
No -> Step 7.
6. Replace the CDM module in the shelf (refer toECDM Replacement) in accordance with "Rack
is cleared.
Yes -> End.
No -> Step 12.
Yes -> End.
No -> Step 12.
Yes -> Step 9.
No -> Step 12.
Yes -> Step 10.
No -> Step 11.
Yes -> End.
No -> Step 12.
Yes -> End.
No -> Step 12.
Yes -> Step 13.
No -> Step 14.
13. Replace the fan subrack in the rack (refer to Fan Subrack Replacement) in accordance with
"Rack number", "Shelf number", and "Slot number" in the alarm information. Wait for two minutes.
Yes -> End.
No -> Step 18.
14. Check whether "Slot number" in the alarm information is in the range of 1 through 28 (board).
Yes -> Step 15.
No -> Step 16.
3-152
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Yes -> End.
No -> Step 16.
16. Check whether "Slot number" in the alarm information is either "29" or "30" (CMM board).
Yes -> Step 17.
No -> Step 18.
Yes -> End.
No -> Step 18.
3.1.119 199030731 Voltage is higher than upper-critical threshold

Alarm Information
l
l
l
l

Name: Voltage is higher than upper-critical threshold
Alarm Description
This alarm is raised if the voltage is higher than the upper-critical threshold. Handle the fault as
soon as possible.
Alarm Cause
l
Impact
This alarm is raised because the voltage is not stable. If the voltage is higher than the upper-critical
threshold, the component mat be damaged, and the system cannot operate properly.
Action
3-153
SJ-20140527134643-015|2015-03-31 (R1.1)
information.
199025860 Voltage is higher than high threshold
Yes -> Step 2.
No -> Step 3.
Yes -> End.
No -> Step 3.
Yes -> Step 4.
No -> Step 8.
199030731 Voltage is higher than upper-critical threshold
199030732 Voltage is higher than upper-non-recoverable threshold
Yes -> Step 5.
No -> Step 12.
Yes -> Step 6.
No -> Step 7.
is cleared.
Yes -> End.
No -> Step 12.
Yes -> End.
No -> Step 12.
Yes -> Step 9.
No -> Step 12.
Yes -> Step 10.
No -> Step 11.
3-154
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Yes -> End.
No -> Step 12.
Yes -> End.
No -> Step 12.
Yes -> Step 13.
No -> Step 14.
Yes -> End.
No -> Step 18.
14. Check whether the "Slot number" in the alarm information is in the range of 1 through 28 (board).
Yes -> Step 15.
No -> Step 16.
Yes -> End.
No -> Step 16.
16. Check whether the "Slot number" in the alarm information is either "29" or "30" (CMM board).
Yes -> Step 17.
No -> Step 18.
Yes -> End.
No -> Step 18.
3.1.120 199030732 Voltage is higher than upper-non-recoverable

threshold
Alarm Information
l
l

Name: Voltage is higher than upper-non-recoverable threshold
3-155
SJ-20140527134643-015|2015-03-31 (R1.1)
l
l

Alarm Description
This alarm is raised if the voltage is higher than the emergency upper-critical threshold. Handle
the fault as soon as possible.
Alarm Cause
l
Impact
This alarm is raised because the voltage is not stable. If the voltage is higher than the emergency
upper-critical threshold, the component mat be damaged, and the system cannot operate properly.
Action
1. Check whether the following alarm exists in accordance with the "Rack number" in the alarm
information.
Yes -> Step 2.
No -> Step 3.
Yes -> End.
No -> Step 3.
Yes -> Step 4.
No -> Step 8.
Yes -> Step 5.
No -> Step 12.
Yes -> Step 6.
No -> Step 7.
3-156
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
is cleared.
Yes -> End.
No -> Step 12.
Yes -> End.
No -> Step 12.
Yes -> Step 9.
No -> Step 12.
Yes -> Step 10.
No -> Step 11.
Yes -> End.
No -> Step 12.
Yes -> End.
No -> Step 12.
Yes -> Step 13.
No -> Step 14.
Yes -> End.
No -> Step 18.
14. Check whether the "Slot number" in the alarm information is in the range of 1 through 28 (board).
Yes -> Step 15.
No -> Step 16.
3-157
SJ-20140527134643-015|2015-03-31 (R1.1)
Yes -> End.

No -> Step 16.
16. Check whether the "Slot number" in the alarm information is either "29" or "30" (CMM board).
Yes -> Step 17.
No -> Step 18.
Yes -> End.
No -> Step 18.
3.1.121 199030733 Voltage is abnormal

Alarm Information
Code:
199030733
Name:
Voltage is abnormal
Severity:
Major
Type:
Equipment Alarm
Alarm Description
This alarm is raised if the voltage of a fan or a board exceeds the normal range.
Probable Cause
l
The input power of the fan or board is powered off.
The detection circuit of the fan or board is abnormal.
System Impact
1. The voltage of the fan is abnormal, so the temperature of the system is too high, and hardware
may be damaged or become invalid.
2. The power supply of the board is abnormal, so the board may be powered off and services
are interrupted.
Handling Suggestion
3-158
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
"Rack number" in the alarm information, and check whether the shelf type is ETCA.
Yes -> Step 2.
No -> Step 4.
2. Check whether the shelf whose "Slot number" is "36" has the following alarms in accordance with
the "Rack number" and "Shelf number" in the alarm information.
Yes -> Step 3.
No -> Step 4.
Yes -> End.
No -> Step 6.
4. Check whether Slot "34" or "35" of the shelf has the following power alarms in accordance with
Yes -> Step 5.
No -> Step 6.
Yes -> End.
No -> Step 6.
6. Check whether the "Slot number" in the alarm information is "31", "32", and "33" (fan).
Yes -> Step 7.
No -> Step 9.
7. Unplug and plug the corresponding fan shelf(refer to Fan Subrack Replacement) in accordance
with the "Rack number", "Shelf number", and "Slot number" in the alarm information. Wait for two
Yes -> End.
No -> Step 8.
8. Replace the corresponding fan shelf(refer to Fan Subrack Replacement) in accordance with
the "Rack number", "Shelf number", and "Slot number" in the alarm information. Wait for two
Yes -> End.
No -> Step 12
9. Check whether the "Slot number" in the alarm information is within the range from 1 to 28 (board).
Yes -> Step 10.
No -> Step 12.
3-159
SJ-20140527134643-015|2015-03-31 (R1.1)
10. Unplug and plug the corresponding board(refer to Front Boards and Rear Boards Replacement) in
accordance with the "Rack number", "Shelf number", and "Slot number" in the alarm information.
Wait for two minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 11.
11. Replace the corresponding board(refer to Front Boards and Rear Boards Replacement) in
Yes -> End.
No -> Step 12.
3.1.122 199030734 Velocity of fan is lower than lower-critical

threshold
Alarm Information
l
l
l
l

Name: Velocity of fan is lower than lower-critical threshold
Alarm Description
This alarm is raised if the speed of the fan is less than the lower-critical threshold.
Alarm Cause
l
The voltage of the fan is insufficient because the rear board of the shelf is faulty.
The voltage of the fan is insufficient or unstable because the external power is abnormal.
The internal components in the fan are faulty, for example, the fan is damaged or the circuit
contact is poor.
Impact
1. If the speed of multiple fans is too slow, heat dissipation of the system is affected. Some boards
may be powered off because of the high temperature and the system fails to operate properly.
2. The speed of other fans may be accelerated, and thus the system noise is increased, and the
lifespan of the fan is reduced.
3-160
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Action
1. Check whether the slots 31, 32,and 33 in the shelf have the following alarms in accordance with
199030733 Voltage is abnormal
Yes -> Step 2.
No -> Step 3.
2. Handle the alarm, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3. Fan Subrack Replacement in accordance with the "Rack number", "Shelf number", and "Slot
number" in the alarm information. Wait for two minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 4.
4. Replace the corresponding fan unit (refer to Fan Subrack Replacement) in accordance with
the "Rack number", "Shelf number", and "Slot number" in the alarm information. Wait for two
Yes -> End.
No -> Step 5.
3.1.123 199030747 Module/Board device absent

Alarm Information
l
l
l
l

Name: Module/Board device absent
Alarm Description
This alarm is raised if the CDM is unavailable.
Alarm Cause
l
The CDM module is unavailable.
The connection between the CDM module and the rear board is poor.
3-161
SJ-20140527134643-015|2015-03-31 (R1.1)
Impact
If only one CDM module is unavailable, the system is not affected. If both CDM modules are
unavailable, the entire shelf cannot be started. The configuration information of the shelf is in the
CDM modules. This information is required when the shelf is started.
Action
1. Check whether the CDM module is absent in the shelf.
Yes -> Step 2.
No -> Step 3.
2. ECDM Replacement, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3. In accordance with "Rack number", "Shelf number", and "CDM number" in the alarm information,
replace the CDM module (refer to ECDM Replacement), and then check whether the alarm
is cleared.
Yes -> End.
No -> Step 4.
3.1.124 199030748 Power on failed due to S5

Alarm Information
l
l
l
l

Name: Power on failed due to S5
Alarm Description
This alarm is raised if the board cannot be powered on because it is in S5 status.
Alarm Cause
l
The board firmware properly.
Impact
The board cannot be powered on and services cannot operate.
3-162
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Action
1. Removing a Board and Installing a Board in accordance with "Rack number", "Shelf number",
and "Slot number" in the alarm information. Wait for two minutes, and check whether the alarm
is cleared.
Yes -> End.
No -> Step 2.
"Rack number", "Shelf number", and "Slot number" in the alarm information. Wait for two minutes,
Yes -> End.
No -> Step 3.
3.1.125 199030759 Fault memory isolation

Alarm Information
Code:
199030759
Name:
Fault memory isolation
Severity:
Major
Type:
Equipment Alarm
Alarm Description
This alarm is raised if the BIOS detects a memory fault and separates the faulty memory automatically
when the board starts.
Probable Cause
The memory of the board is faulty.
System Impact
The available memory of the system is reduced, and thus the board may not operate properly.
3-163
SJ-20140527134643-015|2015-03-31 (R1.1)
Handling Suggestion
1. Run the SET FORCERESETcommand to reset the board in accordance with the "Rack number",
"Shelf number", "Slot number", and "CPU number" in the alarm information. Wait for five to ten
Yes -> End.
No -> Step 2.
2. Replace the memory of the board(refer to Replacing a Memory Bar) in accordance with the
"Rack number", "Shelf number", "Slot number", and "Memory location", and then check whether
Yes -> End.
No -> Step 3.
3. Replace the board(refer to Front Boards and Rear Boards Replacement) in accordance with the
"Rack number", "Shelf number", and "Slot number" in the alarm information. Wait for five to ten
Yes -> End.
No -> Step 4.
3.1.126 199030808 Processor internal error

Alarm Information
l
l
l
l

Name: Processor internal error
Alarm Description
This alarm is raised if the internal processor of the board is faulty.
Alarm Cause
The processor has an internal error.
Impact
If the internal processor is faulty, the system may be down and services cannot operate properly.
3-164
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Action
1. Run the SET FORCERESET command to reset the board in accordance with the "Rack number",
Yes -> End.
No -> Step 2.
"Rack number", "Shelf number", and "Slot number" in the alarm information. Wait for five to ten
Yes -> End.
No -> Step 3.
3.1.127 199030809 Processor thermal trip

Alarm Information
l
l
l
l

Name: Processor thermal trip
Alarm Description
This alarm is raised if the processor temperature of the board is too high.
Alarm Cause
The processor temperature is too high.
Impact
If the processor is overheated, the CPU may be damaged and the system may be down. As a
result, services cannot operate properly.
Action
3-165
SJ-20140527134643-015|2015-03-31 (R1.1)
Yes -> Step 2.
No -> Step 3.
Yes -> End.
No -> Step 3.
3. Check whether the overheated board has any of the following alarms in accordance with the
199030725 Temperature is higher than upper-critical threshold
199030726 Temperature is higher than upper-non-recoverable threshold
Yes -> Step 4.
No -> Step 5.
4. Handle the above temperature alarm. Wait for 510 minutes, and check whether the alarm
is cleared.
Yes -> End.
No -> Step 5.
Yes -> End.
No -> Step 6.
Yes -> End.
No -> Step 7.
"Rack number" in the alarm information, and check whether the shelf type is ATCA.
Yes -> Step 8.
No -> Step 9.
Yes -> Step 9.
No -> Step 10.
Yes -> End.
No -> Step 10.
10. Removing a Board and Installing a Board in accordance with the "Rack number", "Shelf number",
and "Slot number" in the alarm information. Wait for 510 minutes, and check whether the
alarm is cleared.
Yes -> End.
No -> Step 10.
3-166
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
11. Replace the corresponding board(refer to Front Boards and Rear Boards Replacement) in
Wait for five to ten minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 12.
3.1.128 199393987 Board offline

Alarm Information
l
l
l
l

Name: Board offline
Alarm Description
This alarm is raised if the OMP or the CMM detects that the board is offline.
Alarm Cause
l
The configured board is unavailable.
The IPMC communication link between the CMM and the board is faulty.
Impact
This board cannot provide any services.
Action
1. Check whether the board where the alarm is raised is configured as required in accordance
with the physical location of the faulty board.
Yes -> Step 3.
No -> Step 2.
2. In the Independent Board Configuration Online window, check the information about the boards in
the same shelf as the ECMM is. Set the OMM board type to OMM_BOARD, OMP board type to
OMP_BOARD, EGBS board type and EGFS board type to INDEPEND_BOARD, and the types of
other boards to PP_BOARD). Check whether the alarm is cleared.
Yes -> End.
No -> Step 7.
3. Check whether the board is present.
Yes -> Step 5.
No -> Step 4.
4. Installing a Board as required. Wait for two minutes, and check whether the alarm is cleared.
3-167
SJ-20140527134643-015|2015-03-31 (R1.1)
Yes -> End.

No -> Step 7.
5. Removing a Board and Installing a Board, wait for 2 minutes, and check whether the alarm
is cleared.
Yes -> End.
No -> Step 6.
6. Replace the board(refer to Front Boards and Rear Boards Replacement), wait for 2 minutes, and
Yes -> End.
No -> Step 7.
3.1.129 199419840 PTP failed to get clock attribute

Alarm Information
l
l
l
l

Name: PTP failed to get clock attribute
Alarm Description
This alarm is raised if the board fails to obtain the local clock attribute from the clock board in the
same shelf.
Alarm Cause
l
The communication between the board and the clock board in the same shelf is abnormal.
The clock board in the same shelf is faulty.
Impact
The PTP function of this board is disabled, so the clock of this board cannot be synchronized with
other clocks in the network.
3-168
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Action
Yes -> End.
No -> Step 2.
2. Check the rack to see whether the clock board in the same shelf operates properly.
Yes -> Step 3.
No -> Step 5.
3. Check whether the following alarm exists:
199066003 Control plane communication abnormal between board and its home module
Yes -> Step 4.
No -> Step 5.
Yes -> End.
No -> Step 7.
5. Run the SET NORMALRESET command to reset the clock board in the same shelf, and check
Yes -> End.
No -> Step 6.
6. Replace the clock board in the same shelf (refer to EGFS/EXFS1a Board Replacement), wait for
three minutes after the board is started, and then check whether the alarm is cleared.
Yes -> End.
No -> Step 8.
7. Check whether other boards in the same shelf have this alarm.
Yes -> Step 5.
No -> Step 8.
3.1.130 199030756 Major shelf power fault

Alarm Information
l
l
l
l

Name: Major shelf power fault
Alarm type: Equipment alarm
Alarm Description
This alarm is reported when the power supply has a major fault, including incorrect input, incorrect
output, and internal faults.
3-169
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Cause
l
The input voltage of the power supply is abnormal.
The input current of the power supply is abnormal.
The input power of the power supply is abnormal.
The output voltage of the power supply is abnormal.
The output current of the power supply is abnormal.
The output power of the power supply is abnormal.
The temperature of the power supply is abnormal.
The fan of the power supply is abnormal.
The firmware of the power supply is abnormal.
The fuse of the power supply is abnormal.
The circuit breaker of the power supply is open.
Impact
l
If only one power supply is faulty, the power supply for the shelf is not affected, but the shelf
power supply redundancy cannot be implemented.
If two power supplies are faulty, the shelf may be powered down.
Action
1. Handle the alarm in accordance with the actual alarm cause in detailed alarm information:
If the input voltage of the power supply is abnormal, go to step 2.
If the input current of the power supply is abnormal, go to step 2.
If the input power of the power supply is abnormal, go to step 2.
If the temperature of the power supply is abnormal, go to step 5.
If the circuit breaker of the power supply is open, go to step 6.
For other causes, go to step 7.
2. Check whether the rack has the following alarms in accordance with the actual rack number in
detailed alarm information:
Yes -> Step 3.
No -> Step 6.
3. Use a multimeter to measure the input voltage of the rack, and judge whether the voltage is within
the tolerance range in accordance with the actual rack number and shelf number in detailed alarm
information. If the rated voltage is -48 V, the voltage tolerance range is from -40 V to -57 V. If
the rated voltage is -60 V, the voltage tolerance range is from -50 V to -72 V. If the rated voltage
is -110 V, the voltage tolerance range is from -90 V to -127 V. If the rated voltage is -220 V, the
voltage tolerance range is from -200 V to -240 V.
Yes -> Step 7.
No -> Step 4.
4. Contact the electric power department to repair external circuits. After the voltage is stable,
Yes -> End.
3-170
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
No -> Step 7.
5. Wait for 5 to 10 minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 7.
6. Close the circuit breaker of the corresponding power supply in accordance with the rack number
and shelf number in detailed alarm information, and check whether the alarm is cleared.
Yes -> No further action is required.
No -> Step 7.
7. Replace the power module in accordance with the rack number and shelf number in detailed
alarm information, wait for two minutes, and check whether the alarm is cleared.
Yes -> No further action is required.
No -> Step 8.
3.1.131 199030758 Minor shelf power fault

Alarm Information
l
l
l
l

Name: Minor shelf power fault
Alarm Description
This alarm is reported when the power supply has a minor fault, including incorrect input, incorrect
output, and internal faults.
Alarm Cause
l
The input voltage of the power supply is abnormal.
The input current of the power supply is abnormal.
The input power of the power supply is abnormal.
The output voltage of the power supply is abnormal.
The output current of the power supply is abnormal.
The output power of the power supply is abnormal.
The temperature of the power supply is abnormal.
The fan of the power supply is abnormal.
The firmware of the power supply is abnormal.
Impact
The system is not affected. However, if the fault persists for a long time, it may worsen to become a
major fault.
3-171
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
1. Handle the alarm in accordance with the actual alarm cause in detailed alarm information:
If the input voltage of the power supply is abnormal, go to step 2.
If the input current of the power supply is abnormal, go to step 2.
If the input power of the power supply is abnormal, go to step 2.
If the temperature of the power supply is abnormal, go to step 5.
2. Judge whether the rack has the following alarms in accordance with the actual rack number in
detailed alarm information:
Yes -> Step 3.
No -> Step 6.
3. Use a multimeter to measure the input voltage of the rack, and judge whether the voltage is within
the tolerance range in accordance with the actual rack number and shelf number in detailed alarm
information. If the rated voltage is -48 V, the voltage tolerance range is from -40 V to -57 V. If
the rated voltage is -60 V, the voltage tolerance range is from -50 V to -72 V. If the rated voltage
is -110 V, the voltage tolerance range is from -90 V to -127 V. If the rated voltage is -220 V, the
voltage tolerance range is from -200 V to -240 V.
Yes -> Step 7.
No -> Step 4.
4. Contact the electric power department to repair external circuits. After the voltage is stable,
Yes -> End.
No -> Step 6.
5. Wait for 5 to 10 minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 6.
6. Replace the power module in accordance with the rack number and shelf number in detailed
alarm information, wait for two minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 7.
3.1.132 199030760 CDM information is wrong

Alarm Information
l
l
l
l

Name: CDM information is wrong
3-172
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Description
This alarm is reported when the information stored in the CDM is incorrect or does not match the
shelf type.
Alarm Cause
The information stored in the CDM does not match the shelf type.
Impact
The shelf configuration information is stored on the CDM. Incorrect CDM information may cause the
CMM unable to get and configure rack and shelf information when the CMM is started, which then
affects the shelf operations.
Action
1. Replace all CDMs (refer to ECDM Replacement) in accordance with the rack number and shelf
number in detailed alarm information, and check whether the alarm is cleared.
Yes -> End.
No -> Step 2.
3.1.133 199030761 Board extractor open

Alarm Information
l
l
l
l

Name: Board extractor open
Alarm Description
This alarm is reported when the IPMC detects that the ejector lever of a board or a rear board is
unlocked.
Alarm Cause
l
The ejector lever of the board or rear board is unlocked manually.
The ejector lever of the board or rear board is loosened or damaged.
Impact
The board or the rear board may be powered off.
3-173
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
1. Lock the ejector lever of the board or the rear board in accordance with the rack number, shelf
number, and slot number in detailed alarm information. Wait for two minutes, and check whether
Yes -> End.
No -> Step 2.
2. Replace the board or the rear board in accordance with the rack number (refer to Front Boards
and Rear Boards Replacement), shelf number, and slot number in detailed alarm information.
Yes -> End.
No -> Step 3.
3.1.134 199030762 Board power-on failure

Alarm Information
l
l
l
l

Name: Board power-on failure
Alarm Description
This alarm is reported when the IPMC detects that a board fails to be powered on due to hardware
or firmware problems.
Alarm Cause
l
The board firmware is faulty.
Impact
3-174
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Action
1. Removing and installing the board (refer to Removing a Board and Installing a Board in
accordance with the rack number, shelf number, and slot number in detailed alarm information.
Yes -> End.
No -> Step 2.
2. Replace the board (refer to Front Boards and Rear Boards Replacement) in accordance with
the rack number, shelf number, and slot number in detailed alarm information. Wait for two
Yes -> End.
No -> Step 3.
3.1.135 199030765 Board CPU hardware error

Alarm Information
l
l
l
l

Name: Board CPU hardware error
Alarm Description
This alarm is reported when the hardware of the board CPU becomes faulty.
Alarm Cause
l
The board CPU has a catastrophic failure.
The board CPU has a correctable error.
The board CPU has a non-fatal error, which can be repaired by the operating system or firmware.
The board CPU has a fatal error, and must be restarted for recovery.
Impact
The board CPU fault may cause the board unable to operate properly.
3-175
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
1. Wait for 10 minutes, and check whether the alarm is cleared automatically.
Yes -> End.
No -> Step 2.
2. Removing and installing the board (refer to Removing a Board and Installing a Board) in
Wait for 5 minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3. Replace the board (refer to Front Boards and Rear Boards Replacement) in accordance with the
rack number, shelf number, and slot number in detailed alarm information. Wait for 5 minutes,
Yes -> End.
No -> Step 4.
3.1.136 199030767 Board SAS system error

Alarm Information
l
l
l
l

Name: Board SAS system error
Alarm Description
This alarm is reported when the board SAS becomes faulty.
Alarm Cause
The board SAS is faulty.
Impact
The board SAS fault may cause the board unable to operate properly.
3-176
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Action
1. Reset the board forcedly in accordance with the rack number, shelf number, and slot number in
detailed alarm information. Wait for 5 to 10 minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 2.
2. Replace the board in accordance with the rack number, shelf number, and slot number in detailed
alarm information. Wait for 5 to 10 minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3.1.137 199030768 Board PCIE error

Alarm Information
l
l
l
l

Name: Board PCIE error
Alarm Description
This alarm is reported when the board PCIE bus becomes faulty. It is recommended that the alarm
should be handled immediately.
Alarm Cause
The board PCIE bus is faulty.
Impact
The board PCIE bus fault may cause the board unable to operate properly.
Action
1. Reset the board forcedly in accordance with the rack number, shelf number, and slot number in
detailed alarm information. Wait for 5 to 10 minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 2.
2. Replace the corresponding board in accordance with the rack number, shelf number, and slot
number in detailed alarm information. Wait for 5 to 10 minutes, and check whether the alarm
is cleared.
Yes -> End.
No -> Step 3.
3-177
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.138 199030769 Board overheat

Alarm Information
l
l
l
l

Name: Board overheat
Alarm Description
This alarm is reported when the board CPU and memory system are overheated.
Alarm Cause
l
The board CPU is overheated.
The board memory is overheated.
Impact
If the board is overheated, it may cause device damage, system crash, and service failure.
Action
1. Locate the shelf where the board with abnormal temperature is in accordance with the rack
number and shelf number in detailed alarm information, and check whether the following alarms
are reported for the shelf fan.
Yes -> Step 2.
No -> Step 3.
2. Handle the fan-related alarm. Wait for 5 to 10 minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3. Check whether the following alarms are reported for the overheated board in accordance with the
rack number and shelf number in detailed alarm information:
199030724 Temperature is higher than upper-non-critical threshold
199030725 Temperature is higher than upper-critical threshold
199030726 Temperature is higher than upper-non-recoverable threshold
Yes -> Step 4.
No -> Step 5.
4. Handle the temperature-related alarm. Wait for 5 to 10 minutes, and check whether the alarm
is cleared.
3-178
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Yes -> End.

No -> Step 5.
5. Check the temperature where the shelf is located, and control the temperature to be within the
range of 0 to 40. Wait for 5 to 10 minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 6.
6. Check whether the empty slots of the shelf are installed with dummy panels. If not, install dummy
panels on the empty slots. Wait for 5 to 10 minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 7.
7. Check the parameter Shelf.ShelfType in accordance with the rack number and shelf number in
detailed alarm information to see whether the shelf type is an ATCA shelf.
Yes -> Step 8.
No -> Step 9.
8. Unplug the dustproof net of the shelf, and check whether the dustproof net is blocked.
Yes -> Step 9.
No -> Step 10.
9. Clean the dustproof net, dry it, and insert it into the shelf. Wait for 5 to 10 minutes, and check
Yes -> End.
No -> Step 10.
10. Unplug and plug in the board in accordance with the rack number, shelf number, and slot number
in detailed alarm information. Wait for 5 to 10 minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 11.
11. Replace the board in accordance with the rack number, shelf number, and slot number in detailed
alarm information. Wait for 5 to 10 minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 12.
3.1.139 199030772 Number of correctable memory errors over

threshold
Alarm Information
l
l
l
l

Name: Number of correctable memory errors over threshold
3-179
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Description
This alarm is reported when the number of times that the board memory has a correctable error
exceeds the threshold (the number of times of error occurrence is larger than ten times per minute).
Alarm Cause
The number of times that the board memory has a correctable error exceeds the threshold.
Impact
The services may be affected.
Action
1. Check whether there are historical alarms reported from the same location in the past 24 hours in
Yes -> Step 2.
No -> Step 3.
2. Replace the board in accordance with the rack number, shelf number, and slot number in
detailed alarm information.
Yes -> End.
No -> Step 4.
3. Replace the memory module of the board in accordance with the rack number, shelf number, slot
number, and memory position in detailed alarm information. Check whether the alarm is cleared.
Yes -> End.
No -> Step 4.
3.1.140 199030773 Uncorrectable memory error

Alarm Information
l
l
l
l

Name: Uncorrectable memory error
Alarm Description
This alarm is reported when the board memory has an uncorrectable error.
Alarm Cause
The memory has an uncorrectable error.
3-180
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Impact
The faulty board may be reset.
Action
1. Check whether there are historical alarms reported from the same location in the past 24 hours in
Yes -> Step 2.
No -> Step 3.
2. Replace the board (refer to Front Boards and Rear Boards Replacement) in accordance with the
rack number, shelf number, and slot number in detailed alarm information.
Yes -> End.
No -> Step 4.
3. Replace the memory module of the board in accordance with the rack number (refer to Replacing
a Memory Bar), shelf number, slot number, and memory position in detailed alarm information.
Yes -> End.
No -> Step 4.
3.1.141 199105029 OMP reboot alarm

Alarm Information
Alarm code:
199105029
Name:
OMP reboot alarm
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
The OMP board reboots.
Alarm Cause
The OMP board reboots.
Impact
When the OMP is reset, the operation and maintenance tasks are affected, but services are not
affected.
3-181
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
1. After the alarm arises, wait for five minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 2.
3.1.142 199087778 Dry contact alarm - Waterlog

Alarm Information
Alarm code:
199087778
Name:
Dry contact alarm - Waterlog
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Waterlog alarm
Impact
N/A
Action
Perform different process methods according to the type of the exterior device. User can define the
treatment measures according to the actual situation.
3.1.143 199087779 Dry contact alarm - Power loss

Alarm Information
Alarm code:
199087779
Name:
Dry contact alarm - Power loss
Alarm severity:
Major
3-182
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Power loss
Impact
N/A
Action
3.1.144 199087780 Dry contact alarm - No.1 air conditioner fault

Alarm Information
Alarm code:
199087780
Name:
Dry contact alarm - No.1 air conditioner fault
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
No.1 air conditioner fault
Impact
N/A
Action
3-183
SJ-20140527134643-015|2015-03-31 (R1.1)

Alarm Information
Alarm code:
199087781
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action
3.1.146 199087782 Dry contact alarm - AC power abnormal

Alarm Information
Alarm code:
199087782
Name:
Dry contact alarm - AC power abnormal
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
3-184
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
AC power abnormal
Impact
N/A
Action
3.1.147 199087783 Dry contact alarm - Battery under-voltage

Alarm Information
Alarm code:
199087783
Name:
Dry contact alarm - Battery under-voltage
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Battery under-voltage
Impact
N/A
Action
3-185
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.148 199087784 Dry contact alarm - SMR abnormal

Alarm Information
Alarm code:
199087784
Name:
Dry contact alarm - SMR abnormal
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
SMR(selenium module rectifier) abnormal
Impact
N/A
Action
3.1.149 199087785 Dry contact alarm - Under-voltage insulate drop

Alarm Information
Alarm code:
199087785
Name:
Dry contact alarm - Under-voltage insulate drop
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
3-186
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Under-voltage insulate drop
Impact
N/A
Action
3.1.150 199087786 Dry contact alarm - Device suspended

Alarm Information
Alarm code:
199087786
Name:
Dry contact alarm - Device suspended
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Device suspended
Impact
N/A
Action
3-187
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.151 199087787 User-defined Dry contact alarm 1

Alarm Information
Alarm code:
199087787
Name:
User-defined Dry contact alarm 1
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
There is a fault on the User-defined dry contact.
Impact
N/A
Action

Alarm Information
Alarm code:
199087788
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
3-188
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199087789
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action
3-189
SJ-20140527134643-015|2015-03-31 (R1.1)

Alarm Information
Alarm code:
199087790
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199087791
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
3-190
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199087792
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action
3-191
SJ-20140527134643-015|2015-03-31 (R1.1)

Alarm Information
Alarm code:
199087793
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199087794
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
3-192
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199087795
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action
3-193
SJ-20140527134643-015|2015-03-31 (R1.1)

Alarm Information
Alarm code:
199087796
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199087797
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
3-194
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199083851
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Waterlog alarm
Impact
N/A
Action
3-195
SJ-20140527134643-015|2015-03-31 (R1.1)

Alarm Information
Alarm code:
199083852
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Power loss
Impact
N/A
Action

Alarm Information
Alarm code:
199083853
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
3-196
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199083854
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action
3-197
SJ-20140527134643-015|2015-03-31 (R1.1)

Alarm Information
Alarm code:
199083855
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
AC power abnormal
Impact
N/A
Action

Alarm Information
Alarm code:
199083856
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
3-198
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199083857
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action
3-199
SJ-20140527134643-015|2015-03-31 (R1.1)

Alarm Information
Alarm code:
199083858
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199083859
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
3-200
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Device suspended
Impact
N/A
Action

Alarm Information
Alarm code:
199083860
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action
3-201
SJ-20140527134643-015|2015-03-31 (R1.1)

Alarm Information
Alarm code:
199083861
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199083862
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
3-202
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199083863
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action
3-203
SJ-20140527134643-015|2015-03-31 (R1.1)

Alarm Information
Alarm code:
199083864
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199083865
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
3-204
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199083866
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action
3-205
SJ-20140527134643-015|2015-03-31 (R1.1)

Alarm Information
Alarm code:
199083867
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199083868
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
3-206
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199083869
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action
3-207
SJ-20140527134643-015|2015-03-31 (R1.1)

Alarm Information
Alarm code:
199083870
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199080851
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
3-208
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Waterlog alarm
Impact
N/A
Action

Alarm Information
Alarm code:
199080852
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Power loss
Impact
N/A
Action
3-209
SJ-20140527134643-015|2015-03-31 (R1.1)

Alarm Information
Alarm code:
199080853
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199080854
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
3-210
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199080855
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
AC power abnormal
Impact
N/A
Action
3-211
SJ-20140527134643-015|2015-03-31 (R1.1)

Alarm Information
Alarm code:
199080856
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199080857
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
3-212
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199080858
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action
3-213
SJ-20140527134643-015|2015-03-31 (R1.1)

Alarm Information
Alarm code:
199080859
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Device suspended
Impact
N/A
Action

Alarm Information
Alarm code:
199080860
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
3-214
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199080861
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action
3-215
SJ-20140527134643-015|2015-03-31 (R1.1)

Alarm Information
Alarm code:
199080862
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199080863
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
3-216
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199080864
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action
3-217
SJ-20140527134643-015|2015-03-31 (R1.1)

Alarm Information
Alarm code:
199080865
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199080866
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
3-218
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199080867
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action
3-219
SJ-20140527134643-015|2015-03-31 (R1.1)

Alarm Information
Alarm code:
199080868
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199080869
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
3-220
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199080870
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action
3-221
SJ-20140527134643-015|2015-03-31 (R1.1)

Alarm Information
Alarm code:
199104851
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Waterlog alarm
Impact
N/A
Action

Alarm Information
Alarm code:
199104852
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
3-222
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Power loss
Impact
N/A
Action

Alarm Information
Alarm code:
199104853
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action
3-223
SJ-20140527134643-015|2015-03-31 (R1.1)

Alarm Information
Alarm code:
199104854
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199104855
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
3-224
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
AC power abnormal
Impact
N/A
Action

Alarm Information
Alarm code:
199104856
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action
3-225
SJ-20140527134643-015|2015-03-31 (R1.1)

Alarm Information
Alarm code:
199104857
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199104858
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
3-226
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199104859
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Device suspended
Impact
N/A
Action
3-227
SJ-20140527134643-015|2015-03-31 (R1.1)

Alarm Information
Alarm code:
199104860
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199104861
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
3-228
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199104862
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action
3-229
SJ-20140527134643-015|2015-03-31 (R1.1)

Alarm Information
Alarm code:
199104863
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199104864
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
3-230
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199104865
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action
3-231
SJ-20140527134643-015|2015-03-31 (R1.1)

Alarm Information
Alarm code:
199104866
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199104867
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
3-232
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199104868
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action
3-233
SJ-20140527134643-015|2015-03-31 (R1.1)

Alarm Information
Alarm code:
199104869
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
N/A
Action

Alarm Information
Alarm code:
199104870
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
3-234
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Impact
N/A
Action
3.1.222 199087340 FR device failure

Alarm Information
Alarm code:
199087340
Name:
FR device failure
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
This alarm is reported if a board detects that the FR link is faulty.
Alarm Cause
N392 ("Brch(GFrGbBrch)"."N392(N392)") errors are detected in the last N393
("Brch(GFrGbBrch)"."N393(N393)") STATUS ENQUIRY events.
Impact
The Gb bear channel corresponding to this alarm is blocked and the Gb bandwidth is decreased.
In this case, PS traffic congestion may occur.
3-235
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
1. According to the board's physical position and PCM number ("Port") in the alarm details,
check whether the configuration of "E1 Port(E1Port)"."E1 Frame Type(Crc4Mode)" of the PCM
link ("Brch(GFrGbBrch)"."Used Gb Interface Pcm(refGGbPcm)") on the Gb interface board is
consistent with that of the SGSN.
Yes -> Step 3.
No -> Step 2.
2. Modify the configuration of "E1 Frame Type" for the PCM link on the Gb interface board to ensure
the consistency with that of the SGSN, and then check whether this alarm is cleared.
Yes -> End.
No -> Step 3.
3. Check whether the configurations of "PCM TS(StartTs)" and "Access rate"(GFrGbBrch.AR)" in the
"Brch(GFrGbBrch)" configuration parameter of the BSC are consistent with those of the SGSN.
Yes -> Step 5.
No -> Step 4.
4. Modify the two parameters for consistency between the BSC and the SGSN, and check whether
Yes -> End.
No -> Step 5.
5. Check whether the E1 port corresponding to the bear channel reports an alarm.
Yes -> Step 6.
No -> Step 7.
6. Handle the transmission device alarm, and check whether this alarm is cleared.
Yes -> End.
No -> Step 7.
7. Perform a physical self-loop check on the local E1 terminal device, and check whether the E1 line
operates properly (the green light flashes slowly).
Yes -> Step 9.
No -> Step 8.
8. Replace the E1 line, and check whether the alarm is cleared.
Yes -> End.
No -> Step 9.
9. Contact SGSN maintenance personnel to check whether the peer E1 line operates properly.
Yes -> Step 11.
No -> Step 10.
10. Contact SGSN maintenance personnel to troubleshoot the SGSN equipment, and check whether
Yes -> End.
No -> Step 11.
11. Replace the faulty board, and check whether the alarm is cleared.
Yes -> End.
No -> Step 12.
3-236
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.223 199087341 FR congestion

Alarm Information
Alarm code:
199087341
Name:
FR congestion
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
This alarm is reported if a board detects that the FR link is congested.
Alarm Cause
In case of intermediate Frame Relay networking, for a specific NSVC, the number of frames with the
BECN bit of "1" is more than or equal to the number of frames with the BECN bit of "0" in a 10-second
interval. (The peer end may be overloaded or be configured improperly.)
Impact
Quality of PS services for some of users may be degraded, or new users fail to access the services.
Action
1. According to network planning, add a new "Brch(GFrGbBrch)", or increase the existing
"Brch(GFrGbBrch)"."Access rate(AR)", and check whether the alarm is cleared.
Yes -> End.
No -> Step 2.
3.1.224 199087352 NSVC's E1 failure alarm

Alarm Information
Alarm code:
199087352
Name:
NSVC's E1 failure alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
3-237
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Description
This alarm is reported if a board detects that the NSVC link in E1 is faulty.
Alarm Cause
NS Alive Ack cannot be received several consecutive times (GBssFunction.NSAliveMax) during the
NS Alive procedure.
Impact
For single NSVC link configuration, the PS service is interrupted.
For multi-NSVC link configuration, the bandwidth is decreased. In this case, PS traffic congestion
may occur.
Action
1. Check whether the configuration of "NSEI" and "NSVCI" in the alarm details is consistent with
that of the SGSN.
Yes -> Step 3.
No -> Step 2.
2. Search the parent object "Frame relay Nse(GFrGbNse)" and modify "Nse ID(GFrGbNseSeq)".
Modify the configuration of "NSVCI(GFrGbNsvcSeq)" according to the alarm object "Frame relay
Nsvc(GFrGbNsvc)" for consistency with that of the SGSN, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3. Check whether the following alarm arises:
199087340 FR device failure
Yes -> Step 4.
No -> Step 5.
4. Handle the above alarm, and check whether this alarm is cleared.
Yes -> End.
No -> Step 5.
3.1.225 199087465 NSVC's IP failure alarm

Alarm Information
Alarm code:
199087465
Name:
NSVC's IP failure alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
3-238
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Description
This alarm is reported if a board detects that the NSVC link in IP is faulty.
Alarm Cause
NS Alive Ack cannot be received several consecutive times during the NS Alive procedure.
Impact
For single NSVC link configuration, the PS service is interrupted. For multi-NSVC link configuration,
the bandwidth is decreased. In this case, PS traffic congestion may occur.
Action
1. Check whether the configuration of "NSEI" in the alarm details is consistent with that of the SGSN.
Yes -> Step 3.
No -> Step 2.
2. Modify the configuration of the parameter "Nse ID(GIpGbNseSeq)" of the object "IP
Nse(GIpGbNse)" for consistency with that of the SGSN, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3. Check whether alarms arise on the Gb interface board.
Yes -> Step 4.
No -> Step 5.
Yes -> End.
No -> Step 5.
5. Contact the maintenance personnel of the transmission or peer device to check whether the
transmission or peer device is faulty.
Yes -> Step 6.
No -> Step 7.
6. Remove the faults, and check whether the alarm is cleared.
Yes -> End.
No -> Step 7.
3.1.226 199087458 PS cell block caused by slave

Alarm Information
Alarm code:
199087458
Name:
PS cell block caused by slave
3-239
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
This alarm is reported if the BSC detects the PS process unit failure.
Alarm Cause
A PS process unit failure occurs.
Impact
Data services are not available in the cell.
Action
1. Wait for five minutes, and check whether the alarm is cleared automatically.
Yes -> End.
No -> Step 2.
2. Execute the QRY PSCELLDSP command based on "Site ID" and "Bts ID" in the alarm details to
query the corresponding SLAVE of the cell. Execute the QRY SUNITSTATUS command based
on "Sub System number", "RUP board number", and "SLAVE number" in the returned results
to query the status of the sub-unit.
"Manual block" status -> Step 3.
Other status -> Step 4.
3. Execute the SET UNBLOCKSUNIT command to unblock the PS processing sub-unit. Check
Yes -> End.
No -> Step 4.
4. Reset the PS processing sub-unit, wait for two minutes, and then check whether the alarm
is cleared.
Yes -> End.
No -> Step 5.
3.1.227 198087000 Dry contact alarm 1

Alarm Information
Alarm code:
198087000
Name:
Dry contact alarm 1
3-240
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm severity:
Unknown
Alarm type:
Equipment Alarm
Alarm Description
Dry contact alarm 1
Alarm Cause
None
Impact
User-defined.
Action
None

Alarm Information
Alarm code:
198087001
Name:
Dry contact alarm 2
Alarm severity:
Unknown
Alarm type:
Equipment Alarm
Alarm Description
Dry contact alarm 2
Alarm Cause
None
Impact
User-defined.
Action
None
3-241
SJ-20140527134643-015|2015-03-31 (R1.1)

Alarm Information
Alarm code:
198087002
Name:
Dry contact alarm 3
Alarm severity:
Unknown
Alarm type:
Equipment Alarm
Alarm Description
Dry contact alarm 3
Alarm Cause
None
Impact
User-defined.
Action
None

Alarm Information
Alarm code:
198087003
Name:
Dry contact alarm 4
Alarm severity:
Unknown
Alarm type:
Equipment Alarm
Alarm Description
Dry contact alarm 4
Alarm Cause
None
3-242
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Impact
User-defined.
Action
None

Alarm Information
Alarm code:
198087004
Name:
Dry contact alarm 5
Alarm severity:
Unknown
Alarm type:
Equipment Alarm
Alarm Description
Dry contact alarm 5
Alarm Cause
None
Impact
User-defined.
Action
None

Alarm Information
Alarm code:
198087005
Name:
Dry contact alarm 6
Alarm severity:
Unknown
3-243
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm type:
Equipment Alarm
Alarm Description
Dry contact alarm 6
Alarm Cause
None
Impact
User-defined.
Action
None

Alarm Information
Alarm code:
198087006
Name:
Dry contact alarm 7
Alarm severity:
Unknown
Alarm type:
Equipment Alarm
Alarm Description
Dry contact alarm 7
Alarm Cause
None
Impact
User-defined.
Action
None
3-244
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms

Alarm Information
Alarm code:
198087007
Name:
Dry contact alarm 8
Alarm severity:
Unknown
Alarm type:
Equipment Alarm
Alarm Description
Dry contact alarm 8
Alarm Cause
None
Impact
User-defined.
Action
None

Alarm Information
Alarm code:
198087008
Name:
Dry contact alarm 9
Alarm severity:
Unknown
Alarm type:
Equipment Alarm
Alarm Description
Dry contact alarm 9
Alarm Cause
None
3-245
SJ-20140527134643-015|2015-03-31 (R1.1)
Impact
User-defined.
Action
None

Alarm Information
Alarm code:
198087009
Name:
Dry contact alarm 10
Alarm severity:
Unknown
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
None
Impact
User-defined.
Action
None

Alarm Information
Alarm code:
198087010
Name:
Alarm severity:
Unknown
3-246
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
None
Impact
User-defined.
Action
None

Alarm Information
Alarm code:
198087011
Name:
Alarm severity:
Unknown
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
None
Impact
User-defined.
Action
None
3-247
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.239 198087012 EAM dry contact 1 alarm

Alarm Information
Alarm code:
198087012
Name:
EAM dry contact 1 alarm
Alarm severity:
Unknown
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
None
Impact
User-defined.
Action
None

Alarm Information
Alarm code:
198087013
Name:
Alarm severity:
Unknown
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
None
3-248
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Impact
User-defined.
Action
None

Alarm Information
Alarm code:
198087014
Name:
Alarm severity:
Unknown
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
None
Impact
User-defined.
Action
None

Alarm Information
Alarm code:
198087015
Name:
Alarm severity:
Unknown
3-249
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
None
Impact
User-defined.
Action
None

Alarm Information
Alarm code:
198087016
Name:
Alarm severity:
Unknown
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
None
Impact
User-defined.
Action
None
3-250
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms

Alarm Information
Alarm code:
198087017
Name:
Alarm severity:
Unknown
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
None
Impact
User-defined.
Action
None

Alarm Information
Alarm code:
198087018
Name:
Alarm severity:
Unknown
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
None
3-251
SJ-20140527134643-015|2015-03-31 (R1.1)
Impact
User-defined.
Action
None

Alarm Information
Alarm code:
198087019
Name:
Alarm severity:
Unknown
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
None
Impact
User-defined.
Action
None
3.1.247 198087102 Power overvoltage/undervoltage alarm

Alarm Information
Alarm code:
198087102
Name:
Power overvoltage/undervoltage alarm
Alarm severity:
Minor
3-252
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm type:
Equipment Alarm
Alarm Description
Power overvoltage/undervoltage alarm
Alarm Cause
CMM/CMB power voltage is out of adjustment range
Impact
The CMM/CMB boards do not operate properly.
Action
please replace CMM/CMB board as soon as possible
3.1.248 198087103 13M input clock failure

Alarm Information
Alarm code:
198087103
Name:
13M input clock failure
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
13M input clock failure
Alarm Cause
CMM/CMB clock unit works abnormally
Impact
A transmission link inside the BTS is disconnected, frame numbers are confused, and the frequency
synthesizer does not operate properly.
3-253
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
1)Test transmission index. If the transmission continuously has over-2Hz frequency offset in
4 seconds or the single frequency adjustment is more than 4 Hz for 15 times in 6 minutes, it is
necessary to notify the engineer to adjust transmission.
2)Reset CMB board and check whether the alarm disappears.
3)If the alarm does not disappear, replace CMB board.
3.1.249 198087106 SYNCLK clock failure

Alarm Information
Alarm code:
198087106
Name:
SYNCLK clock failure
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
SYNCLK clock failure
Alarm Cause
CMM/CMB clock unit works abnormally
Impact
A transmission link inside the BTS is disconnected, frame numbers are confused, and the frequency
synthesizer does not operate properly.
Action
1)Test transmission index. If the transmission continuously has over-2Hz frequency offset in
4 seconds or the single frequency adjustment is more than 4 Hz for 15 times in 6 minutes, it is
necessary to notify the engineer to adjust transmission.
2)Reset CMB board and check whether the alarm disappears.
3)If the alarm does not disappear, replace CMB board.
3-254
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.250 198087107 Master and slave communication link failure

Alarm Information
Alarm code:
198087107
Name:
Master and slave communication link failure
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Master and slave communication link failure
Alarm Cause
Standby CMM/CMB board is not powered on, or active-standby CMM/CMB board communication
error
Impact
The master and slave CMM/CMB boards fail to be switched over.
Action
1. Re-plug CMB board.
2. If the software has problem, upgrade it.
3.1.251 198087108 Standby CMM/CMB board not present

Alarm Information
Alarm code:
198087108
Name:
Standby CMM/CMB board not present
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Standby CMM/CMB board not present
3-255
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Cause
Standby CMM/CMB board is not inserted
Impact
The system is less reliable because the faulty master board fails to be switched over to the slave
board.
Action
check if standby board is present in the rack. If it is , reset or insert standby board again( normal
state of standby board is that power lamp always lights and running lamp always lights);if it isn't,
insert a new CMM/CMB board
3.1.252 198087109 Standby CMM/CMB board abnormal

Alarm Information
Alarm code:
198087109
Name:
Standby CMM/CMB board abnormal
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Standby CMM/CMB board abnormal
Alarm Cause
Standby CMM/CMB board starts abnormally or not inserted properly
Impact
The master and slave boards fail to be switched over.
Action
Check whether the spare board is on the rack. If yes, reset or re-plug the board ( it is in the normal
condition if the power LED indicator and RUN LED indicator are both on). If no, plug in the new
CMB board if necessary.
3-256
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.253 198087110 CMM/CMB power failure alarm

Alarm Information
Alarm code:
198087110
Name:
CMM/CMB power failure alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
CMM/CMB power failure alarm
Alarm Cause
CMM/CMB board is power off
Impact
The CMM/CMB boards fail to operate.
Action
E1 interface will bridge-connect automatically. Replace the CMB circuit board as quickly as possible.
3.1.254 198087112 Communication link alarm between master and

slave rack (left)
Alarm Information
Alarm code:
198087112
Name:
Communication link alarm between master and slave rack (left)
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Communication link alarm between master and slave rack (left)
3-257
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Cause
Communication link fault between master rack and slave rack
Impact
The site fails to load, operate or maintain data and software.
Action
1. Check if line between racks is connected. if it has problems, connect or replace it. 2. start
self-check of master-slave rack communication to confirm the problem of CMM/CMB hardware
or software. then replace it
3.1.255 198087113 Communication link alarm between master and

slave rack (right)
Alarm Information
Alarm code:
198087113
Name:
Communication link alarm between master and slave rack (right)
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Communication link alarm between master and slave rack (right)
Alarm Cause
Communication link fault between master rack and slave rack
Impact
The site fails to load, operate or maintain data and software.
Action
1. Check if line between racks is connected. if it has problems, connect or replace it. 2. start
self-check of master-slave rack communication to confirm the problem of CMM/CMB hardware
or software. then replace it
3-258
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.256 198087114 A interface E1 Rx carrier alarm

Alarm Information
Alarm code:
198087114
Name:
A interface E1 Rx carrier alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
A interface E1 Rx carrier alarm
Alarm Cause
Chip fault, clock abnormal, difference from BSC clock, or bad E1 connections, etc
Impact
This fault has a little impact on calls if it does not occur frequently. However, errors may occur during
a call or the link establishment between the TRM/DTRU and the BSC if this alarm occurs frequently
(for example, at intervals of several minutes).
Action
1. Check the electric-connection performance of E1 line. 2. if E1 line has no problem, insert the board
tightly and reset. 3. if alarm still exists, maybe E1 interface chip is abnormal. 4. if chip's self-check is
passed, start loop test of E1 interface. 5. if loop test of E1 is correct, the transport has problems
3.1.257 198087115 A interface E1 Rx frame not synchronized

Alarm Information
Alarm code:
198087115
Name:
A interface E1 Rx frame not synchronized
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
A interface E1 Rx frame not synchronized
3-259
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Cause
Chip fault, clock abnormal, difference from BSC clock, bad E1 connections, or CMM board not
support C/F configuration, etc
Impact
Action
tightly and reset. 3.if C/F Trunk alarm happens, please check Whether CMM board hardware version
is 030903 or 030900, and if so, it need be changed to 030508 version.( this situation only suitable for
Site V2 serials). 4. if alarm still exists, maybe E1 interface chip is abnormal. 5. if chip's self-check is
passed, start loop test of E1 interface. 6. if loop test of E1 is correct, the transport has problems.
3.1.258 198087120 A interface E1 remote alarm

Alarm Information
Alarm code:
198087120
Name:
A interface E1 remote alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
A interface E1 remote alarm
Alarm Cause
Sending line is shorted, the remote end might not receive data sent from local end
Impact
The BTS fails to provide services.
3-260
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Action
1.Check the electrical connection property of the E1 cable.2. If the cable of E1 did not have problems,
insert the board tightly and resetting.3.If the warning continue to exist, the E1 interface chip maybe is
in abnormal.4. If can pass the chip selftest, can start the selfloop test procedure for E1 interface.5.If
the selfloop test result is correct, can think that the transmission equipment have problems.
3.1.259 198087121 B interface E1 Rx carrier alarm

Alarm Information
Alarm code:
198087121
Name:
B interface E1 Rx carrier alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
B interface E1 Rx carrier alarm
Alarm Cause
Impact
Action
3.1.260 198087122 B interface E1 Rx frame not synchronized

Alarm Information
Alarm code:
198087122
3-261
SJ-20140527134643-015|2015-03-31 (R1.1)
Name:
B interface E1 Rx frame not synchronized
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
B interface E1 Rx frame not synchronized
Alarm Cause
Impact
Action
3.1.261 198087127 B interface E1 remote alarm

Alarm Information
Alarm code:
198087127
Name:
B interface E1 remote alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
B interface E1 remote alarm
3-262
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Impact
Action
3.1.262 198087128 C interface E1 Rx carrier alarm

Alarm Information
Alarm code:
198087128
Name:
C interface E1 Rx carrier alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
C interface E1 Rx carrier alarm
Alarm Cause
Impact
Action
3-263
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.263 198087129 C interface E1 Rx frame not synchronized

Alarm Information
Alarm code:
198087129
Name:
C interface E1 Rx frame not synchronized
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
C interface E1 Rx frame not synchronized
Alarm Cause
Impact
Action
3.1.264 198087134 C interface E1 remote alarm

Alarm Information
Alarm code:
198087134
Name:
C interface E1 remote alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
3-264
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Description
C interface E1 remote alarm
Alarm Cause
Impact
Action
3.1.265 198087135 D interface E1 Rx carrier alarm

Alarm Information
Alarm code:
198087135
Name:
D interface E1 Rx carrier alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
D interface E1 Rx carrier alarm
Alarm Cause
Impact
3-265
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
3.1.266 198087136 D interface E1 Rx frame not synchronized

Alarm Information
Alarm code:
198087136
Name:
D interface E1 Rx frame not synchronized
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
D interface E1 Rx frame not synchronized
Alarm Cause
Impact
Action
3-266
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.267 198087141 D interface E1 remote alarm

Alarm Information
Alarm code:
198087141
Name:
D interface E1 remote alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
D interface E1 remote alarm
Alarm Cause
Impact
Action
3.1.268 198087142 E interface E1 Rx carrier alarm

Alarm Information
Alarm code:
198087142
Name:
E interface E1 Rx carrier alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
E interface E1 Rx carrier alarm
3-267
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Cause
Impact
Action
3.1.269 198087143 E interface E1 Rx frame not synchronized

Alarm Information
Alarm code:
198087143
Name:
E interface E1 Rx frame not synchronized
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
E interface E1 Rx frame not synchronized
Alarm Cause
Impact
3-268
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Action
3.1.270 198087148 E interface E1 remote alarm

Alarm Information
Alarm code:
198087148
Name:
E interface E1 remote alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
E interface E1 remote alarm
Alarm Cause
Impact
Action
3.1.271 198087149 F interface E1 Rx carrier alarm

Alarm Information
Alarm code:
198087149
3-269
SJ-20140527134643-015|2015-03-31 (R1.1)
Name:
F interface E1 Rx carrier alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
F interface E1 Rx carrier alarm
Alarm Cause
Impact
Action
3.1.272 198087150 F interface E1 Rx frame not synchronized

Alarm Information
Alarm code:
198087150
Name:
F interface E1 Rx frame not synchronized
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
F interface E1 Rx frame not synchronized
Alarm Cause
3-270
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Impact
Action
3.1.273 198087153 F interface E1 Rx forward sliding indication

Alarm Information
Alarm code:
198087153
Name:
F interface E1 Rx forward sliding indication
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
F interface E1 Rx forward sliding indication
Alarm Cause
Impact
Action
3-271
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.274 198087155 F interface E1 remote alarm

Alarm Information
Alarm code:
198087155
Name:
F interface E1 remote alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
F interface E1 remote alarm
Alarm Cause
Impact
Action
3.1.275 198087156 G interface E1 Rx carrier alarm

Alarm Information
Alarm code:
198087156
Name:
G interface E1 Rx carrier alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
G interface E1 Rx carrier alarm
3-272
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Impact
Action
3.1.276 198087157 G interface E2 Rx frame not synchronized

Alarm Information
Alarm code:
198087157
Name:
G interface E2 Rx frame not synchronized
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
G interface E2 Rx frame not synchronized
Alarm Cause
Impact
Action
3-273
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.277 198087162 G interface E1 remote alarm

Alarm Information
Alarm code:
198087162
Name:
G interface E1 remote alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
G interface E1 remote alarm
Alarm Cause
Impact
Action
3.1.278 198087163 H interface E1 Rx carrier alarm

Alarm Information
Alarm code:
198087163
Name:
H interface E1 Rx carrier alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
H interface E1 Rx carrier alarm
3-274
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Impact
Action
3.1.279 198087164 H interface E3 Rx frame not synchronized

Alarm Information
Alarm code:
198087164
Name:
H interface E3 Rx frame not synchronized
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
H interface E3 Rx frame not synchronized
Alarm Cause
Impact
Action
3-275
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.280 198087169 H interface E1 remote alarm

Alarm Information
Alarm code:
198087169
Name:
H interface E1 remote alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
H interface E1 remote alarm
Alarm Cause
Impact
Action
3.1.281 198087170 Temperature alarm

Alarm Information
Alarm code:
198087170
Name:
Temperature alarm
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Temperature alarm
3-276
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Fan fault or module temperature too high
Impact
User-defined.
Action
check the envirnment temperature.if it conforms to the demand, keep on observing and keep normal
status in the case of other modules no fault. If not , please change it.if there are some other problems,
please replace FCM module
3.1.282 198087171 Fan absent

Alarm Information
Alarm code:
198087171
Name:
Fan absent
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Fan absent
Alarm Cause
Fan not inserted or not in position
Impact
User-defined.
Action
check the fan
3-277
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.283 198087172 Fan control board CPU alarm

Alarm Information
Alarm code:
198087172
Name:
Fan control board CPU alarm
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Fan control board CPU alarm
Alarm Cause
CPU fault
Impact
User-defined.
Action
1. check the line and correct it.
2. check the fan and replace FCM.
3.1.284 198087173 Fan alarm

Alarm Information
Alarm code:
198087173
Name:
Fan alarm
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Fan alarm
3-278
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Fan stops rotating due to fault
Impact
User-defined.
Action
1. check the line and correct it.
2. check the fan and replace FCM.
3. check if collecting-alarm circuit of TPU is correct. Otherwise replace TRM module.
3.1.285 198087174 Fan temperature alarm

Alarm Information
Alarm code:
198087174
Name:
Fan temperature alarm
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Fan temperature alarm
Alarm Cause
Impact
Performance is reduced due to too high temperature of the TRM/DTRU boards.
Action
Check the environment temperature meets the requirement or not.If meet the requirement, under the
premise that other modules have not fault, can continue to observe, and keep the normal work. If not
meet the requirement, then improving the equipments working environment is needed. If break down,
then should replace the FCM module immediately.
3-279
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.286 198087175 Fan 1 alarm

Alarm Information
Alarm code:
198087175
Name:
Fan 1 alarm
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Fan 1 alarm
Alarm Cause
Impact
Too high temperature is generated on the TRX shelf in the same layer.
Action
Check the alarm circuit have fault or not, if have problem, then resolve it.
2. Check the fan has fault or not. If have problem, then replace the FCM.
3. Check the alarm sampling electric circuit of TPU is good or not, otherwise replacing the
corresponding DTRM module
3.1.287 198087176 Fan 2 alarm

Alarm Information
Alarm code:
198087176
Name:
Fan 2 alarm
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Fan 2 alarm
3-280
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Impact
Too high temperature is generated on the TRX shelf in the same layer.
Action
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
3.1.288 198087177 Fan control board alarm

Alarm Information
Alarm code:
198087177
Name:
Fan control board alarm
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Fan control board alarm
Alarm Cause
Impact
Action
Check the environment temperature meets the request or not.If meet the request, under the premise
that other modules have not fault, can continue to observe, and keep the normal work. If not meet
the request, then improving the equipments working environment is needed. If break down, then
should replace the FCM module immediately.
3-281
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.289 198087178 LNA alarm

Alarm Information
Alarm code:
198087178
Name:
LNA alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
LNA alarm
Alarm Cause
LNA current exceeds by 30%
Impact
User-defined.
Action
please replace AEM module as soon as possible.
3.1.290 198087179 Tower amplifier power alarm

Alarm Information
Alarm code:
198087179
Name:
Tower amplifier power alarm
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Tower amplifier power alarm
Alarm Cause
AEM tower amplifier power alarm
3-282
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Impact
User-defined.
Action
please replace Tower Amplifier module or AEM module as soon as possible.
3.1.291 198087180 SWR of AEM HYCOM minor alarm

Alarm Information
Alarm code:
198087180
Name:
SWR of AEM HYCOM minor alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Combiner SWR 1.5 alarm
Impact
User-defined.
Action
keep on observing.if normal work isn't influenced, don't replace AEM module.
3.1.292 198087181 SWR of AEM HYCOM major alarm

Alarm Information
Alarm code:
198087181
Name:
SWR of AEM HYCOM major alarm
Alarm severity:
Major
3-283
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Combiner SWR 3.0 alarm
Impact
User-defined.
Action
please replace AEM and reset TRM which connects with this AEM.
3.1.293 198087182 AEM power alarm(BTS V2)

Alarm Information
Alarm code:
198087182
Name:
AEM power alarm(BTS V2)
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
AEM power alarm(BTS V2)
Alarm Cause
AEM power alarm
Impact
User-defined.
Action
please replace AEM module as soon as possible.
3-284
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.294 198087183 AEM type alarm(BTS V2)

Alarm Information
Alarm code:
198087183
Name:
AEM type alarm(BTS V2)
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
AEM type alarm(BTS V2)
Alarm Cause
AEM type alarm
Impact
User-defined.
Action
check whether config type of AEM doesn't conform to actual type, whether insert tightly and poweron.
If not, please replace it.if type is correct, problem maybe is the fault of back panel transport or the
fault of TPU collecting circuit, please replace the cable or the module.
3.1.295 198087184 AEM absent(BTS V2)

Alarm Information
Alarm code:
198087184
Name:
AEM absent(BTS V2)
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
AEM absent(BTS V2)
3-285
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Cause
AEM not-in-position alarm
Impact
User-defined.
Action
please replace AEM and reset TRM which connects with this AEM.
3.1.296 198087185 AEM power alarm

Alarm Information
Alarm code:
198087185
Name:
AEM power alarm
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
AEM power alarm
Alarm Cause
AEM power alarm
Impact
This fault has an impact on transmission.
Action
( 1)Check whether there is PA temperature alarm or fan environment temperature alarm on the
background. If yes, deal with the fan alarm first. It is necessary to plug in the blank module if there is
no TRX on the right side of TRM board.
( 2)Check whether the fuse of CDU is damaged. If yes, replace it. ( Note: FU1 2A, FU2 1A)
( 3)Pull out of CDU and DTRU modules in the same layer. Check whether the pins on the rear board
are bent. If yes, change the slot or replace the rear board. After that, re-power on and check whether
the alarm is recovered. ( If changing the slot, it is necessary to re-configure on the background.)
( 4)Replace CDU.
3-286
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.297 198087186 LNA0 alarm

Alarm Information
Alarm code:
198087186
Name:
LNA0 alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
LNA0 alarm
Alarm Cause
LNA0 current exceeds by 30%
Impact
The connected DTRU board fails to operate (both master and diversity LNAs are faulty) or does not
operate fully (only one LNA is faulty).
Action
( 3)Replace CDU.
3.1.298 198087187 LNA1 alarm

Alarm Information
Alarm code:
198087187
Name:
LNA1 alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
3-287
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Description
LNA1 alarm
Alarm Cause
LNA1 current exceeds by 30%
Impact
The connected DTRU board fails to operate (both master and diversity LNAs are faulty) or does not
operate fully (only one LNA is faulty).
Action
( 3)Replace CDU.
3.1.299 198087188 Tower Amplifier0 power alarm

Alarm Information
Alarm code:
198087188
Name:
Tower Amplifier0 power alarm
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
AEM tower amplifier 0 power alarm
Impact
This fault has an impact on the uplink receive sensitivity of the related DTRU board.
3-288
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Action
( 2)Pull off PA power cable. The position of PA power cable: open the BTS rear cover and pull off the
socket with the label of TA_PWR X31 ( X31 PA_PWR for the old rack). The PA power cable connects
to PWRTA_Ln on the top of cabinet. Check whether the alarm disappears. The power cable is useless
in the place where no PA exists. In the place where PA exists, the alarm disappears. It is necessary
to check whether the short circuit exists between the power cable and PA or whether PA goes wrong.
( 4)Replace CDU and reset TRX connecting with it.
3.1.300 198087189 Tower Amplifier1 power alarm

Alarm Information
Alarm code:
198087189
Name:
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
AEM tower amplifier 1 power alarm
Impact
This fault has an impact on the uplink receive sensitivity of the related DTRU board.
3-289
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
( 2)Pull off PA power cable. The position of PA power cable: open the BTS rear cover and pull off the
socket with the label of TA_PWR X31 ( X31 PA_PWR for the old rack). The PA power cable connects
to PWRTA_Ln on the top of cabinet. Check whether the alarm disappears. The power cable is useless
in the place where no PA exists. In the place where PA exists, the alarm disappears. It is necessary
to check whether the short circuit exists between the power cable and PA or whether PA goes wrong.
3.1.301 198087190 SWR of AEM HYCOM minor alarm

Alarm Information
Alarm code:
198087190
Name:
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Combiner SWR minor alarm
Impact
3-290
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Action
( 1) Check whether the connection between RF jumper which connects DTRU with CDU and CDU
antenna mouth is tight. If the connection is loose, fasten it with tool. After that, reset the TRX and
check whether the alarm disappears.
( 2)Measure SWR of the jumper between CDU and antenna with SITEMASTER. Check whether the
SWR value exceeds standard. If yes, the antenna has fault. Check the antenna system part by part
upon the test result. Once the fault is found, fasten the antenna, make waterproof treatment on the
antenna and replace the antenna. Reset the TRX and check whether the alarm disappears.
( 3)Replace the RF cable which connects DTRU with CDU. Reset the TRX connecting with it and
( 4)Pull out of CDU and DTRU modules in the same layer. Check whether the pins on the rear
board are bent. If yes, replace the rear board. Check whether the alarm cable connector of CDU
is loose or off. If yes, fasten it and re-power it on. Three minutes after the TRX is running, check
whether the alarm disappears.
3.1.302 198087191 SWR of AEM HYCOM major alarm

Alarm Information
Alarm code:
198087191
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Combiner SWR major alarm
Impact
3-291
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
( 1) Check whether the connection between RF jumper which connects DTRU with CDU and CDU
antenna mouth is tight. If the connection is loose, fasten it with tool. After that, reset the TRX. Three
minutes after the TRX is running, check whether the alarm disappears.
( 2)Measure SWR of the jumper between CDU and antenna with SITEMASTER. Check whether the
SWR value exceeds standard. If yes, the antenna has fault. Check the antenna system part by
part upon the test result. Once the fault is found, fasten the antenna, make waterproof treatment
on the antenna and replace the antenna. Reset the TRX. Three minutes after the TRX is running,
( 3)Replace the RF cable which connects DTRU with CDU. Reset the TRX connecting with it. Three
minutes after the TRX is running, check whether the alarm disappears.
( 4)Pull out of CDU and DTRU modules in the same layer. Check whether the pins on the rear
board are bent. If yes, replace the rear board. Check whether the alarm cable connector is loose
or off. If yes, fasten it and re-power it on. Three minutes after the TRX is running, check whether
the alarm disappears.
3.1.303 198087192 AEM type alarm

Alarm Information
Alarm code:
198087192
Name:
AEM type alarm
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
AEM type alarm
Alarm Cause
AEM type alarm
Impact
3-292
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Action
( 2)Check whether AEM configuration type is consistent with the actual type, and whether DTRU is
associated with the background, otherwise change or modify the background configuration.
( 3)Check whether AEM powers on, and plugged properly. Shut down AEM module power, plug off
and then plug in the module, turn on the power to check whether the alarm has been recovered.
( 4)Check whether the board DIP switch of AEM is correct. Otherwise, adjust the DIP switch till it is
correct. Check whether the fuse on CDU is broken, if so, change the fuse of the same model. Note:
FU1 2A, FU2 1A; power on the equipment to check whether the alarm is recovered.
( 5)Plug off the AEM and DTRU module of the same layer, check whether there backplane pin is
curved, if so, change the backplane and re-power on to check whether the alarm is recovered.
( 6)Plug in site id, and reset CMB. About five minutes later, check whether the alarm is recovered.
( 7)Replace AEM module.
3.1.304 198087193 AEM Not-in-position alarm

Alarm Information
Alarm code:
198087193
Name:
AEM Not-in-position alarm
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
AEM Not-in-position alarm
Alarm Cause
AEM not-in-position alarm
Impact
3-293
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
( 1) Check whether there is PA temperature alarm or fan environmental temperature alarm, if so,
process with the fan alarm first. If there is no another TRX or blank module on the right side of the
TRX, plug in a blank module;
( 2) Check whether AEM configuration type is consistent with the actual type, and whether DTRU is
associated with the background, otherwise change or modify the background configuration.
( 3) Check whether AEM powers on, and plugged properly. Shut down AEM module power, plug off
and then plug in the module, turn on the power to check whether the alarm has been recovered.
( 4) Check whether the board DIP switch of AEM is correct. Otherwise, adjust the DIP switch till it is
correct. Check whether the fuse on CDU is broken, if so, change the fuse of the same model. Note:
FU1 2A, FU2 1A; power on the equipment to check whether the alarm is recovered.
( 5) Plug off the AEM and DTRU module of the same layer, check whether there backplane pin is
curved, if so, change the backplane and re-power on to check whether the alarm is recovered.
( 6) Plug in site id, and reset CMB. About five minutes later, check whether the alarm is recovered.
( 7) Change AEM module.
3.1.305 198087198 Uplink of ADC chip initialization failure

Alarm Information
Alarm code:
198087198
Name:
Uplink of ADC chip initialization failure
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Uplink of ADC chip initialization failure
Alarm Cause
Uplink ADC chip initialization failure
Impact
User-defined.
Action
1. Reset this module in order to work normally.
2. if reset is of no effect , please replace this module at once.
3-294
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.306 198087200 CIP resource can't be used

Alarm Information
Alarm code:
198087200
Name:
CIP resource can't be used
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
CIP resource can't be used
Alarm Cause
Uplink/downlink loop data demodulation failure
Impact
User-defined.
Action
if alarm exists, at the same time some traffics exist on this TRM, it indicates this TRM is normal; if
there aren't some traffics on this TRM, or RF_LOOP test failure which arose by OMCR, this TRM is
damaged and please replace it at once.
3.1.307 198087201 Uplink failure

Alarm Information
Alarm code:
198087201
Name:
Uplink failure
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Uplink failure
3-295
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Cause
Error in uplink data receiving
Impact
User-defined.
Action
1.Reset this module in order to work normally.
2. if reset is of no effect, please replace this module at once.
3.1.308 198087207 Watchdog of FUC overflow

Alarm Information
Alarm code:
198087207
Name:
Watchdog of FUC overflow
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Watchdog of FUC overflow
Alarm Cause
FUC program has no response temporarily
Impact
User-defined.
Action
user can reset TPU to solve this problem. If it isn't solved, please replace TRM module.
3-296
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.309 198087216 Cell configuration parameter mismatch(BTS V2)

Alarm Information
Alarm code:
198087216
Name:
Cell configuration parameter mismatch(BTS V2)
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Cell configuration parameter mismatch(BTS V2)
Alarm Cause
Cell parameter configuration is incorrect or conflicts with channel parameters and CU parameter
configuration, carrier frequency configuration in omcr is unconform with the physical board
Impact
User-defined.
Action
1.Wait ten minutes. If the alarm still exists, configure parameters again from background, and
synchronize them to base station. Otherwise check the hardware and replace TRM/DTRM module in
time.
2.Please check whether the carrier frequency configuration in omcr is conform with the physical
board or not.
3.1.310 198087221 Communication link between CMM and FUC

break(BTS V2)
Alarm Information
Alarm code:
198087221
Name:
Communication link between CMM and FUC break(BTS V2)
Alarm severity:
Minor
Alarm type:
Equipment Alarm
3-297
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Description
Communication link between CMM and FUC break(BTS V2)
Alarm Cause
HDLC link between CMM and TPU breaks, CMM hardware error, etc
Impact
User-defined.
Action
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 replace it, if software has problems please upgrade software version.
3.1.311 198087224 Watchdog of TPU CIP overflow

Alarm Information
Alarm code:
198087224
Name:
Watchdog of TPU CIP overflow
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Watchdog of TPU CIP overflow
Alarm Cause
DSP program of demodulation module has no response temporarily
Impact
User-defined.
3-298
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Action
Reset this CU firstly.If the alarm resume, it could be confirmed that the alarm is arisen by interior
status of DSP abnormal.After resetting resumes, the CU could work normally.if not, BSC should start
BCCH changeover strategy and replace TRM module.
3.1.312 198087225 Software version of CIP mismatch

Alarm Information
Alarm code:
198087225
Name:
Software version of CIP mismatch
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Software version of CIP mismatch
Alarm Cause
CIP software version load error. If one of the carriers is configured as BCCH, then the whole cell
can not work normally.
Impact
User-defined.
Action
reset TRM, if it is of no effect, please replace TRM module.
3.1.313 198087226 Clock alarm for TPU and CMM

Alarm Information
Alarm code:
198087226
Name:
Clock alarm for TPU and CMM
Alarm severity:
Major
Alarm type:
Equipment Alarm
3-299
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Description
Clock alarm for TPU and CMM
Alarm Cause
Clock between TPU and CMM is disconnected
Impact
User-defined.
Action
1. If this TPU alarm is the only one alarm in the base station, check the line connection on back
panel.if the connection is correct , please replace TRM.
2. if other TPUs have the same alarm as this TPU, check whether clock alarm exists on CMM
board. If it is , please replace CMM.
3.1.314 198087228 TPU frame No. alarm

Alarm Information
Alarm code:
198087228
Name:
TPU frame No. alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
TPU frame No. alarm
Alarm Cause
Frame clock FCLK has problem, upper-level frame number synchronization source CMM has problem
Impact
User-defined.
3-300
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Action
1.check if FCLK of frame no producing point is normal( if it is directly transported, check the clock
frequency, wave shape; if it is produced by phase locked, check whether the alarm of loose lock
exists.if there are some problems, please replace TRM module.
2. Transport link( transport clock, interface chip, the size of error code rate)3. check superior
synchro source of frame no
3.1.315 198087229 TPU CHP DSP0 initialization failure

Alarm Information
Alarm code:
198087229
Name:
TPU CHP DSP0 initialization failure
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
TPU CHP DSP0 initialization failure
Alarm Cause
DSP software or hardware error
Impact
All the sixteen physical channels of the dual-carrier fail to operate properly. Cell services may also be
affected if the DTRU board is configured as BCCH.
Action
1. Re- download the software of that DSP.
2. Reset that DTRM frame( restart DSP), check whether that warning can recover or not.
3. Check whether the environmental temperature exceeds temperature permit for equipment running,
if there is overtemperature alarm, please adjust the environment; if the temperature is within the
permit, re-plug in the board to check whether the alarm is recovered.
4. If the alarm has not been recovered, replace the corresponding DTRU.
3-301
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.316 198087243 Cell configuration parameter mismatch

Alarm Information
Alarm code:
198087243
Name:
Cell configuration parameter mismatch
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Cell configuration parameter mismatch
Alarm Cause
Cell parameter configuration is incorrect or conflicts with channel parameters and CIP parameter
configuration
Impact
The BTS may not operate properly.
Action
1. If the alarm is not recovered within 10 minutes, re-configure the parameter in the background,
and synchronize to the base station.
2. Reset the TRX, after 10 minutes, check whether the alarm is recovered.
3. Re-plug the TRX module, after 10 minutes, check whether the alarm is recovered.
4. Change the corresponding TRX module.
3.1.317 198087247 HDLC communication link between CMB and

FUC broken
Alarm Information
Alarm code:
198087247
Name:
HDLC communication link between CMB and FUC broken
Alarm severity:
Minor
Alarm type:
Equipment Alarm
3-302
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Description
HDLC communication link between CMB and FUC broken
Alarm Cause
HDLC link between CMB and TPU breaks, CMB hardware error, etc
Impact
TPU polling is faulty and data fails to be transmitted between the TPU and CMB. Data fails to be
configured for the FUC, CHP, and CIP and their states fail to be reported.
Action
1. Check whether DTRU is plugged tightly and properly. Re-plug DTRU module, and add DTRU in
corresponding position according to the configuration, so as to check whether the alarm is recovered.
2. Reset DTRU board to check whether the alarm is recovered.
3. If alarms occur in all the cells, check whether CMB board works normally. Re-plug CMB to check
whether the alarm is recovered.
4. Check whether the DIP switch on the backplane is correct. Otherwise, adjust the switch to correct
position, to check whether the alarm is recovered.
5. Check whether the transmission line of the backplane is connected correctly. Otherwise connect
the line to correct position to check whether the alarm is recovered.
3.1.318 198087453 signal HDLC break off

Alarm Information
Alarm code:
198087453
Name:
signal HDLC break off
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
signal HDLC break off
Alarm Cause
Communication break of between TRX and FIB's HDLC or hardware error
3-303
SJ-20140527134643-015|2015-03-31 (R1.1)
Impact
The DTRU board fails to operate.
Action
1.DTRU board insert close or not? Insert or power on
2.Reset DTRU board , and watch whether it work or not
3.check whether FIB work or not
4.check whether address switch of rear board right or not
5.check whether line connect right or not
3.1.319 198087253 FU fram No error alarm

Alarm Information
Alarm code:
198087253
Name:
FU fram No error alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
FU fram No error alarm
Alarm Cause
Frame clock FCLK has problem, upper-level frame number synchronization source CMB has problem
Impact
The DTRU board fails to operate. Cell services may also be affected if the DTRU board is configured
with BCCH.
Action
1. Measure every Frame clock FCLK that produce frame number to ensure it is normal( if deliver
directly, then see the frequency of the clock, whether waveform have or not distortion. if it is
phaselock to produce, then check whether have the warning of lose lock or not). if have fault then
replace the DTRM module in time.
2. Check transmission link( whether clock of transmission is normal or not, whether the interface chip
have or not warning, whether the size of the error code rate is small or not)
3.Whether the upper source of synchronization exists the warning or not.
3-304
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.320 198087254 Rx PLL1 unlock

Alarm Information
Alarm code:
198087254
Name:
Rx PLL1 unlock
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Rx PLL1 unlock
Alarm Cause
Clock signal is unstable or TRM Phase-Locked Loop ( PLL) fault
Impact
User-defined.
Action
1. Check whether clock alarm exists with LMT.if it exists, please replace relevant module.if it doesn't
exist, check the 13M output of TP on front panel. If it doesn't exist, there is clock problem from TPU to
RCU.please replace TRM.
2. if the problem still exists, maybe the LO fail, please replace TRM.
3.1.321 198087255 Rx PLL2 unlock

Alarm Information
Alarm code:
198087255
Name:
Rx PLL2 unlock
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Rx PLL2 unlock
3-305
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Cause
Impact
User-defined.
Action
3.1.322 198087256 Tx PLL1 unlock

Alarm Information
Alarm code:
198087256
Name:
Tx PLL1 unlock
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Tx PLL1 unlock
Alarm Cause
Impact
User-defined.
Action
3-306
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.323 198087257 Tx PLL2 unlock

Alarm Information
Alarm code:
198087257
Name:
Tx PLL2 unlock
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Tx PLL2 unlock
Alarm Cause
Impact
User-defined.
Action
3.1.324 198087258 52M referenced clock PLL unlock

Alarm Information
Alarm code:
198087258
Name:
52M referenced clock PLL unlock
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
52M referenced clock PLL unlock
3-307
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Cause
Impact
User-defined.
Action
3.1.325 198087259 Tx IF PLL unlock

Alarm Information
Alarm code:
198087259
Name:
Tx IF PLL unlock
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Tx IF PLL unlock
Alarm Cause
Impact
User-defined.
Action
3-308
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.326 198087260 EEPROM resource can't be used

Alarm Information
Alarm code:
198087260
Name:
EEPROM resource can't be used
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
EEPROM resource can't be used
Alarm Cause
EEPROM fault
Impact
User-defined.
Action
please replace TRM module.
3.1.327 198087261 FPGA interface failure

Alarm Information
Alarm code:
198087261
Name:
FPGA interface failure
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
FPGA interface failure
Alarm Cause
Communication between DSP and FPGA interface breaks
3-309
SJ-20140527134643-015|2015-03-31 (R1.1)
Impact
User-defined.
Action
please replace TRM module.
3.1.328 198087262 PA VSWR alarm(BTS V2)

Alarm Information
Alarm code:
198087262
Name:
PA VSWR alarm(BTS V2)
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
PA VSWR alarm(BTS V2)
Alarm Cause
Direct reason: reverse power is too high. Possible reason: open circuit or high resistance exists in
output end of PA
Impact
User-defined.
Action
1.Check the connection of PA output with cable.
2.If alarm still exists, please replace TRM module as soon as possible.
3.1.329 198087263 PA overtemperature minor alarm(BTS V2)

Alarm Information
Alarm code:
198087263
Name:
PA overtemperature minor alarm(BTS V2)
3-310
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
PA overtemperature minor alarm(BTS V2)
Alarm Cause
PA temperature is too high, which is possibly due to PA working with rated power for a long time, fan
not working for a long time, environment temperature too high, and detecting circuit fault, etc
Impact
User-defined.
Action
1.Check whether fan works normally or not and whether the environment temperature is high or not.
2.If the fan works normally and the environment temperature is normal, the PA temperature warning
still exist then may be the detection electric circuit breakdown, continue to observe.
3.1.330 198087264 PA overtemperature major alarm(BTS V2)

Alarm Information
Alarm code:
198087264
Name:
PA overtemperature major alarm(BTS V2)
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
PA overtemperature major alarm(BTS V2)
Alarm Cause
Impact
User-defined.
3-311
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
still exist then may be the detection electric circuit breakdown, should replace the TRM/DTRM
module in time.
3.1.331 198087265 PA output power alarm

Alarm Information
Alarm code:
198087265
Name:
PA output power alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
PA output power alarm
Alarm Cause
Direct reason: Difference between PA output power and CIP control power is more than 3 db;
Possible reason: PA aging, power detecting circuit fault, or detecting threshold too narrow
Impact
User-defined.
Action
1.Reset TRM and observe.
2. if alarm exists, replace TRM module as soon as possible.
3.1.332 198087266 PA power overvoltage

Alarm Information
Alarm code:
198087266
Name:
PA power overvoltage
3-312
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
User-defined.
Action
check the check circuit of PA.if it has problem, please replace TRM.
3.1.333 198087267 PA power lower voltage

Alarm Information
Alarm code:
198087267
Name:
PA power lower voltage
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
PA power lower voltage
Alarm Cause
PA power undervoltage
Impact
User-defined.
Action
3-313
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.334 198087268 Downlink checksum error of DLRC_AL1

Alarm Information
Alarm code:
198087268
Name:
Downlink checksum error of DLRC_AL1
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Downlink checksum error of DLRC_AL1
Alarm Cause
Interference exists on link between CHP and modulation module
Impact
User-defined.
Action
1. Check the signal and time-sequence between CHP and modulation module.
2. if the problem still exists, please replace TRM in time.
3.1.335 198087269 DUC chip initialization failure

Alarm Information
Alarm code:
198087269
Name:
DUC chip initialization failure
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
DUC chip initialization failure
3-314
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
DUC chip unavailable
Impact
User-defined.
Action
please replace this TRM module.
3.1.336 198087270 80w PA VSWR alarm

Alarm Information
Alarm code:
198087270
Name:
80w PA VSWR alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
80w PA VSWR alarm
Alarm Cause
Direct reason: Reverse power is too high; Possible reason: Open circuit or high resistance exists at
the output end of PA
Impact
User-defined.
Action
1.Check the connection of PA output with cable.
2.If alarm still exists, please replace TRM module as soon as possible.
3-315
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.337 198087271 80w PA overtemperature

Alarm Information
Alarm code:
198087271
Name:
80w PA overtemperature
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
80w PA overtemperature
Alarm Cause
Impact
User-defined.
Action
3.1.338 198087272 80w PA overtemperature major alarm

Alarm Information
Alarm code:
198087272
Name:
80w PA overtemperature major alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
80w PA overtemperature major alarm
3-316
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Impact
User-defined.
Action
still exist then may be the detection electric circuit breakdown, should replace the TRM/DTRM
module in time.
3.1.339 198087273 80w PA output power alarm

Alarm Information
Alarm code:
198087273
Name:
80w PA output power alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
80w PA output power alarm
Alarm Cause
Direct reason: Difference between PA output power and CIP control power is more than 3 db;
Possible reason: PA aging, power detecting circuit fault, or detecting threshold too narrow
Impact
User-defined.
Action
1.Reset TRM and observe.
2. if alarm exists, replace TRM module as soon as possible.
3-317
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.340 198087274 80w PA power overvoltage

Alarm Information
Alarm code:
198087274
Name:
80w PA power overvoltage
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
80w PA power overvoltage
Alarm Cause
Impact
User-defined.
Action
3.1.341 198087275 80w PA power lower voltage

Alarm Information
Alarm code:
198087275
Name:
80w PA power lower voltage
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
80w PA power lower voltage
Alarm Cause
3-318
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Impact
User-defined.
Action
check the check circuit of PA.if it has problem, please replace TRM
3.1.342 198087276 80w PA absent

Alarm Information
Alarm code:
198087276
Name:
80w PA absent
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
80w PA absent
Alarm Cause
PA not in position
Impact
User-defined.
Action
3.1.343 198087277 TXIF unlock

Alarm Information
Alarm code:
198087277
Name:
TXIF unlock
Alarm severity:
Minor
3-319
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm type:
Equipment Alarm
Alarm Description
TXIF unlock
Alarm Cause
Clock signal is unstable or DTRU Phase-Locked Loop ( PLL) fault
Impact
The DTRU board may fail to operate.
Action
1. Restart the TRX, if the fault disappears, it indicates there is no fault in DTRU.
2. Check whether there is signal between Pinout 2 and 15 of HW line; if there is no signal, change
the HW line and continue with the test; if there is still no signal, it may be caused by CMB fault.
Test the 13M clock port on the equipment top, if there is signal, re-plug CMB board, if there is no
signal, it may be caused by CMB fault.
3. If the signal test is normal, re-plug this TRX. If there is still faults, change the fault TRX slot. If the
problem continues, change DTRU.
3.1.344 198087278 TPF unlock

Alarm Information
Alarm code:
198087278
Name:
TPF unlock
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
TPF unlock
Alarm Cause
Impact
3-320
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Action
3.1.345 198087279 TXRF unlock

Alarm Information
Alarm code:
198087279
Name:
TXRF unlock
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
TXRF unlock
Alarm Cause
Impact
Action
3-321
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.346 198087280 RXRF unlock

Alarm Information
Alarm code:
198087280
Name:
RXRF unlock
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
RXRF unlock
Alarm Cause
Impact
Action
1. See through LMT whether have the clock warning, if have, then replace the corresponding
module.If have not clock warning, then check whether have output or not from 13M clock of TP
front panel. If have not output, then can be thought that the clock fault between TPU and RCU and
should replace the DTRM module.
2.If still have fault and can't recover, then it is possible that local oscillator have fault, and should
replace the DTRM in time.
3.1.347 198087281 13 MHz clock lost

Alarm Information
Alarm code:
198087281
Name:
13 MHz clock lost
Alarm severity:
Minor
Alarm type:
Equipment Alarm
3-322
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Description
13 MHz clock lost
Alarm Cause
13 MHz clock receiving is abnormal, 13 MHz clock unit works abnormally
Impact
Action
3.1.348 198087282 60 ms clock lost

Alarm Information
Alarm code:
198087282
Name:
60 ms clock lost
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
60 ms clock lost
Alarm Cause
60 ms synchronization clock receiving is abnormal, 60 ms synchronization clock unit works abnormally
Impact
3-323
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
1. Check the configuration, if there are excessive standby racks configured, ignore this alarm.
2. Check whether the 60ms cables are connected properly, or whether the cables are broken.
Reconnect or change the 60ms cables to check whether the alarm is recovered.
3. Check whether the CMB of standby racks work normally. If it is not normal, recover CMB working
status to check whether the alarm is recovered.
3.1.349 198087285 52 MHz clock lost

Alarm Information
Alarm code:
198087285
Name:
52 MHz clock lost
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
52 MHz clock lost
Alarm Cause
RF board 52 MHz clock receiving is abnormal, RF board 52 MHz clock unit works abnormally
Impact
Action
3-324
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.350 198087288 PA power overvoltage alarm

Alarm Information
Alarm code:
198087288
Name:
PA power overvoltage alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
PA power overvoltage alarm
Alarm Cause
Impact
The PA may be broken and the modulation module may switch off the power output for protection.
Action
Check whether the PA examination electric circuit break down or not, if have the fault, should replace
the DTRM in time
3.1.351 198087289 PA power undervoltage alarm

Alarm Information
Alarm code:
198087289
Name:
PA power undervoltage alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
PA power undervoltage alarm
3-325
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Cause
Impact
The output power is faulty.
Action
Check whether the PA examination electric circuit break down or not, if have the fault, should replace
the DTRM in time
3.1.352 198087290 PA VSWR alarm

Alarm Information
Alarm code:
198087290
Name:
PA VSWR alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
PA VSWR alarm
Alarm Cause
Direct reason: reverse power is too high. Possible reason: open circuit or high resistance exists in
output end of PA
Impact
The DTRU board fails to operate and the PA is broken.
Action
1. Check whether the PA output connects the electric cable tightly, if not, connects the PA output
and the electric cable tightly.
2. If still break down then should replace the DTRM module in time.
3-326
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.353 198087291 PA temperature minor alarm

Alarm Information
Alarm code:
198087291
Name:
PA temperature minor alarm
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
PA temperature minor alarm
Alarm Cause
Impact
The DTRU still operates properly but the performance of the PA is deteriorated drastically.
Action
3.1.354 198087292 PA temperature major alarm

Alarm Information
Alarm code:
198087292
Name:
PA temperature major alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
PA temperature major alarm
3-327
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Cause
Impact
The power output of the DTRU is switched off for protection and the performance of the PA is
deteriorated drastically.
Action
still exist then may be the detection electric circuit breakdown, should replace the DTRM module in
time.
3.1.355 198087293 PA forward power(3db) alarm

Alarm Information
Alarm code:
198087293
Name:
PA forward power(3db) alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
PA forward power(3db) alarm
Alarm Cause
Direct reason: Difference between PA output power and CHP control power is more than 3 db;
Possible reason: PA aging, power detecting circuit fault, detecting threshold too narrow
Impact
The DTRU board may fail to operate and the power is out of control.
Action
1. Reset the DTRM to observe whether warning can recover or not.
2. If still have the breakdown, should replace the DTRM module in time
3-328
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.356 198087294 RTU power alarm

Alarm Information
Alarm code:
198087294
Name:
RTU power alarm
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
RTU power alarm
Alarm Cause
RTU power module failure
Impact
The TRM/DTRU boards fail to operate. Cell services may also be affected if the TRM/DTRU is
configured as BCCH.
Action
Replace the RTU circuit board as quickly as possible
3.1.357 198087295 RTU power temperature alarm

Alarm Information
Alarm code:
198087295
Name:
RTU power temperature alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
RTU power temperature alarm
3-329
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Cause
RTU power module overheated
Impact
The power output of the TRM/DTRU is switched off for protection and the performance of the RTU is
deteriorated drastically.
Action
1.To detect the whether the fans are running and the electric power source is overheat.
2.If the fans are running and the electric power source isn't overheat, maybe there is something wrong
in the error-detector circuit.
3.1.358 198087296 RTU power output overvoltage alarm

Alarm Information
Alarm code:
198087296
Name:
RTU power output overvoltage alarm
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
RTU power output overvoltage alarm
Alarm Cause
RTU power output overvoltage
Impact
The RTU fails to operate properly.
Action
3-330
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.359 198087297 RTU power input failure alarm

Alarm Information
Alarm code:
198087297
Name:
RTU power input failure alarm
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
RTU power input failure alarm
Alarm Cause
RTU power input failure
Impact
The RTU fails to operate properly.
Action
3.1.360 198087298 IQ calibration parameters abnormal alarm

Alarm Information
Alarm code:
198087298
Name:
IQ calibration parameters abnormal alarm
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
IQ calibration parameters abnormal alarm
Alarm Cause
IQ calibration parameter abnormal
3-331
SJ-20140527134643-015|2015-03-31 (R1.1)
Impact
The RTU board is completely broken.
Action
Replace the RTU circuit board as quickly as possible.
3.1.361 198087299 EAM heat exchanger alarm

Alarm Information
Alarm code:
198087299
Name:
EAM heat exchanger alarm
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
EAM heat exchanger alarm
Alarm Cause
Heat exchanger alarm, reported by dry contact of heat exchanger
Impact
This fault may decrease the equipment safety.
Action
Perform on-site check immediately to find fault cause and replace the heat exchanger.
3.1.362 198087300 EAM TRX layer fan-4 alarm

Alarm Information
Alarm code:
198087300
Name:
EAM TRX layer fan-4 alarm
Alarm severity:
Warning
3-332
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm type:
Equipment Alarm
Alarm Description
EAM TRX layer fan-4 alarm
Alarm Cause
CMB0 heater wrong
Impact
This fault has an impact on start-up at a low temperature.
Action
replace CMB0 heater in time
3.1.363 198087301 EAM AEM layer axis-flow fan alarm

Alarm Information
Alarm code:
198087301
Name:
EAM AEM layer axis-flow fan alarm
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
EAM AEM layer axis-flow fan alarm
Alarm Cause
CMB1 heater wrong
Impact
Action
replace CMB1 heater in time
3-333
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.364 198087302 EAM smoke alarm

Alarm Information
Alarm code:
198087302
Name:
EAM smoke alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
EAM smoke alarm
Alarm Cause
Equipment smoke alarm
Impact
This fault may decrease the safety of equipment operation.
Action
Perform on-site check immediately to find fault cause and handle the fault.
3.1.365 198087303 EAM waterproof alarm

Alarm Information
Alarm code:
198087303
Name:
EAM waterproof alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
EAM waterproof alarm
Alarm Cause
Equipment water alarm
3-334
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Impact
Action
3.1.366 198087304 EAM lightning protection alarm

Alarm Information
Alarm code:
198087304
Name:
EAM lightning protection alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
EAM lightning protection alarm
Alarm Cause
Lightning protector failure alarm
Impact
Action
Perform on-site check immediately to find fault cause and replace the lightning protector.
3.1.367 198087305 EAM backdoor access control alarm

Alarm Information
Alarm code:
198087305
Name:
EAM backdoor access control alarm
Alarm severity:
Warning
3-335
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm type:
Equipment Alarm
Alarm Description
EAM backdoor access control alarm
Alarm Cause
Alarm of back door being opened
Impact
Action
Perform on-site check immediately to find fault cause and close the back door.
3.1.368 198087306 EAM frontdoor access control alarm

Alarm Information
Alarm code:
198087306
Name:
EAM frontdoor access control alarm
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
EAM frontdoor access control alarm
Alarm Cause
Alarm of front door being opened
Impact
Action
Perform on-site check immediately to find fault cause and close the front door.
3-336
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.369 198087307 EAM PWR monitoring unit alarm

Alarm Information
Alarm code:
198087307
Name:
EAM PWR monitoring unit alarm
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
EAM PWR monitoring unit alarm
Alarm Cause
PWR monitoring unit alarm
Impact
Action
Perform on-site check immediately to find fault cause.
3.1.370 198087308 EAM heat exchanger electric heater alarm

Alarm Information
Alarm code:
198087308
Name:
EAM heat exchanger electric heater alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
EAM heat exchanger electric heater alarm
Alarm Cause
FIB heater alarm
3-337
SJ-20140527134643-015|2015-03-31 (R1.1)
Impact
Action
replace FIB heater in time
3.1.371 198087309 EAM heat exchanger control board alarm

Alarm Information
Alarm code:
198087309
Name:
EAM heat exchanger control board alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
EAM heat exchanger control board alarm
Alarm Cause
Heat exchanger control board alarm
Impact
This fault has an impact on operation of the equipment.
Action
3.1.372 198087310 EAM heat exchanger external circulation fan 2

alarm
Alarm Information
Alarm code:
198087310
Name:
EAM heat exchanger external circulation fan 2 alarm
3-338
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Heat exchanger external circulation fan 2 alarm
Impact
Action
3.1.373 198087311 EAM heat exchanger external circulation fan 1

alarm
Alarm Information
Alarm code:
198087311
Name:
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Heat exchanger external circulation fan 1 alarm
Impact
3-339
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
3.1.374 198087312 EAM heat exchanger internal circulation fan 2

alarm
Alarm Information
Alarm code:
198087312
Name:
EAM heat exchanger internal circulation fan 2 alarm
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Heat exchanger internal circulation fan 2 alarm
Impact
Action
3.1.375 198087313 EAM heat exchanger internal circulation fan 1

alarm
Alarm Information
Alarm code:
198087313
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
3-340
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Description
Alarm Cause
Heat exchanger internal circulation fan 1 alarm
Impact
Action
3.1.376 198087314 EAM heat exchanger 485 communication alarm

Alarm Information
Alarm code:
198087314
Name:
EAM heat exchanger 485 communication alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
EAM heat exchanger 485 communication alarm
Alarm Cause
Communication break between EAM and heat exchanger
Impact
This fault has an impact on the reporting of heat exchanger alarms.
Action
3-341
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.377 198087315 EAM temperature alarm

Alarm Information
Alarm code:
198087315
Name:
EAM temperature alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
EAM temperature alarm
Alarm Cause
Equipment internal environment temperature too high
Impact
Action
3.1.378 198087316 EAM TRX layer mixed-flow fan 1 alarm

Alarm Information
Alarm code:
198087316
Name:
EAM TRX layer mixed-flow fan 1 alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Mixed-flow fan 1 damage alarm
3-342
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Impact
This fault has an impact on the operation of the TRX module.
Action
Perform on-site check immediately to find fault cause and replace the fan.

Alarm Information
Alarm code:
198087317
Name:
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
Action

Alarm Information
Alarm code:
198087318
Name:
Alarm severity:
Minor
3-343
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
Action
3.1.381 198087319 Communication broken between EAM and CMB

Alarm Information
Alarm code:
198087319
Name:
Communication broken between EAM and CMB
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Communication broken between EAM and CMB
Alarm Cause
Communication break between EAM and CMB
Impact
This fault has an impact on the reporting of equipment alarms.
Action
3-344
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.382 198087320 Power undervoltage alarm

Alarm Information
Alarm code:
198087320
Name:
Power undervoltage alarm
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Power undervoltage alarm
Alarm Cause
Power voltage is lower than normal
Impact
User-defined.
Action
Restore external power supply as soon as possible
3.1.383 198087321 Inner fan 2 alarm (for M8202)

Alarm Information
Alarm code:
198087321
Name:
Inner fan 2 alarm (for M8202)
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
3-345
SJ-20140527134643-015|2015-03-31 (R1.1)
Impact
The temperature in the cabinet is too high.
Action
1. Check the alarm connection and eliminate the malfunction;
2. Check the fan and maintain the fault; 3. Check the collection system of the dTPB board and
replace the wrong one.
3.1.384 198087322 Inner fan 1 alarm (for M8202)

Alarm Information
Alarm code:
198087322
Name:
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
Action
2. Check the fan and maintain the fault; 3. Check the collection system of the dTPB board and
replace the wrong one.
3.1.385 198087323 Outer fan 2 and fan 4 alarm (for M8202)

Alarm Information
Alarm code:
198087323
3-346
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Name:
Outer fan 2 and fan 4 alarm (for M8202)
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
Action
2. Check the fan and maintain the fault;
3. Check the collection system of the dTPB board and replace the wrong one.
3.1.386 198087324 Outer fan 1 and fan 3 alarm (for M8202)

Alarm Information
Alarm code:
198087324
Name:
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
3-347
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
2. Check the fan and maintain the fault;
3. Check the collection system of the dTPB board and replace the wrong one.
3.1.387 198087325 Rack temperature minor alarm

Alarm Information
Alarm code:
198087325
Name:
Rack temperature minor alarm
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Rack temperature minor alarm
Alarm Cause
Impact
Action
Check the environment temperature, if the temperature is normal, keep on observing while other
modules works normally, otherwise, improve the equipment working conditions.
3.1.388 198087326 Rack temperature major alarm

Alarm Information
Alarm code:
198087326
Name:
Rack temperature major alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
3-348
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Description
Rack temperature major alarm
Alarm Cause
Impact
Performance is reduced because the equipment is damaged.
Action
Check the environment temperature, if the temperature is normal, keep on observing while other
modules works normally, otherwise, improve the equipment working conditions.
3.1.389 198087327 Layer 3 fan 1 alarm (for M8206)

Alarm Information
Alarm code:
198087327
Name:
Layer 3 fan 1 alarm (for M8206)
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
The failure of fans
Impact
Too high temperature in the cabinet may result in deteriorated performance and shorter service life
of the devices.
Action
1.Examin the error-detection circuit;
2. Examin the fans;
3. Examin the RTU Alarm Collection Circuit, if any fault in it, replace the relevant unit.
3-349
SJ-20140527134643-015|2015-03-31 (R1.1)

Alarm Information
Alarm code:
198087328
Name:
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
The failure of fans
Impact
of the devices.
Action
2. Examin the fans;

Alarm Information
Alarm code:
198087329
Name:
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
3-350
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
The failure of fans
Impact
of the devices.
Action
2. Examin the fans;

Alarm Information
Alarm code:
198087330
Name:
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
The failure of fans
Impact
of the devices.
Action
2. Examin the fans;
3-351
SJ-20140527134643-015|2015-03-31 (R1.1)

Alarm Information
Alarm code:
198087331
Name:
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
The failure of fans
Impact
of the devices.
Action
2. Examin the fans;

Alarm Information
Alarm code:
198087332
Name:
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
3-352
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
The failure of fans
Impact
of the devices.
Action
2. Examin the fans;

Alarm Information
Alarm code:
198087333
Name:
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
The failure of fans
Impact
of the devices.
Action
2. Examin the fans;
3-353
SJ-20140527134643-015|2015-03-31 (R1.1)

Alarm Information
Alarm code:
198087334
Name:
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
The failure of fans
Impact
of the devices.
Action
2. Examin the fans;

Alarm Information
Alarm code:
198087335
Name:
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
3-354
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
The failure of fans
Impact
of the devices.
Action
1. Examin the error-detection circuit;
2. Examin the fans;
3.1.398 198087391 FCU power undervoltage alarm

Alarm Information
Alarm code:
198087391
Name:
FCU power undervoltage alarm
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
FCU power undervoltage alarm
Alarm Cause
+12V power undervoltage
Impact
The FCU fails to operate properly.
Action
Replace the FCU as soon as possible
3-355
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.399 198087403 The clock alarm about transmission of CCI

board Abis-E1
Alarm Information
Alarm code:
198087403
Name:
The clock alarm about transmission of CCI board Abis-E1
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
The clock alarm about transmission of CCI board Abis-E1
Alarm Cause
The clock alarm about transmission of CCI board Abis-E1 is lost
Impact
User-defined.
Action
Exam the Abis E1 interface.
3.1.400 198087404 The local working clock alarm of CCI board

Alarm Information
Alarm code:
198087404
Name:
The local working clock alarm of CCI board
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
The local working clock alarm of CCI board
3-356
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
The local working clock error
Impact
User-defined.
Action
Switch to the slave circuit board as quickly as possible. If Necessarily, to replace the CCI circuit board.
3.1.401 198087405 The clock alarm about transmission of CCI

board 13M
Alarm Information
Alarm code:
198087405
Name:
The clock alarm about transmission of CCI board 13M
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
The clock alarm about transmission of CCI board 13M
Alarm Cause
The clock alarm about transmission of CCI board is lost
Impact
User-defined.
Action
Exam the contrast source, or replace the CCI circuit board.
3-357
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.402 198087406 CCI opposite board alarm

Alarm Information
Alarm code:
198087406
Name:
CCI opposite board alarm
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
CCI opposite board alarm
Alarm Cause
there is no CCI opposite board or clock failure
Impact
User-defined.
Action
Replace the CCI circuit board.
3.1.403 198087407 IQ FPGA internal clock alarm

Alarm Information
Alarm code:
198087407
Name:
IQ FPGA internal clock alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
IQ FPGA internal clock alarm
Alarm Cause
IQ FPGA internal source lost of clock
3-358
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Impact
User-defined.
Action
Detect whether the CLK FPGA is running.
3.1.404 198087408 IQ FPGA light interface alarm

Alarm Information
Alarm code:
198087408
Name:
IQ FPGA light interface alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
IQ FPGA light interface alarm
Alarm Cause
IQ FPGA light interface abnormal
Impact
User-defined.
Action
Replace the optical module or optical fiber.
3.1.405 198087409 IQ FPGA LVDS interface alarm

Alarm Information
Alarm code:
198087409
Name:
IQ FPGA LVDS interface alarm
Alarm severity:
Minor
3-359
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm type:
Equipment Alarm
Alarm Description
IQ FPGA LVDS interface alarm
Alarm Cause
LVDS interface abnormal
Impact
User-defined.
Action
Exam the backboard and SERDES chip in the relevant GBP board.
3.1.406 198087410 IQ FPGA internal data alarm

Alarm Information
Alarm code:
198087410
Name:
IQ FPGA internal data alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
IQ FPGA internal data alarm
Alarm Cause
the format of internal data is abnormal
Impact
User-defined.
Action
Find out the cause of the data format mistake.
3-360
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.407 198087470 Fan absence alarm

Alarm Information
Alarm code:
198087470
Name:
Fan absence alarm
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Fan absence alarm
Alarm Cause
Fan error or absence
Impact
Action
1. Check if fan work or not.
2. If work, check up the connection between fan and fan controller good or not.3. If connection is
good, exchange new fan frame.
3.1.408 198087471 Fan rotate alarm

Alarm Information
Alarm code:
198087471
Name:
Fan rotate alarm
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Fan rotate alarm
3-361
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Cause
Fan rotate too slowly
Impact
Action
1. Check if much dust result in the slow rotate speed of the fan or not.
2. If not, exchange new fan frame.
3.1.409 198087472 CMB and FNCB RS485 link break alarm

Alarm Information
Alarm code:
198087472
Name:
CMB and FNCB RS485 link break alarm
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
CMB and FNCB RS485 link break alarm
Alarm Cause
interrupt RS485 communication between fan controller and CMB
Impact
This fault has no impact on heat dissipation, but the fan fails to be controlled.
Action
1. Check if the fan frame tightened or not.
2. Check if the RS485 and CMB backboard or DTRU backboard tightened or not.
3. Exchange fan frame.
3-362
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.410 198087480 Status of TX5 filter alarm

Alarm Information
Alarm code:
198087480
Name:
Status of TX5 filter alarm
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
TX5 is adjusting or loss over 5dB
Impact
Action
Replace the FCU, or reset the TRM that connected with it
3.1.411 198087481 Status of TX6 filter alarm

Alarm Information
Alarm code:
198087481
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
TX6 is adjusting or loss over 5dB
3-363
SJ-20140527134643-015|2015-03-31 (R1.1)
Impact
Action
Replace the FCU, or reset the TRM that connected with it
3.1.412 198087443 Diversity antenna lost

Alarm Information
Alarm code:
198087443
Name:
Diversity antenna lost
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Two diversity antenna receive signal, one of diversity antenna is abnormal
Impact
User-defined.
Action
Check the receive channel of RF as quickly as possible.
3.1.413 198087444 Diversity antenna identical

Alarm Information
Alarm code:
198087444
Name:
Diversity antenna identical
Alarm severity:
Warning
3-364
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Wrong connection of diversity antenna
Impact
User-defined.
Action
Check the connection of ant line as quickly as possible.
3.1.414 198087411 13M,61.44M clock lost alarm

Alarm Information
Alarm code:
198087411
Name:
13M,61.44M clock lost alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
13M,61.44M clock lost alarm
Alarm Cause
clock lost
Impact
User-defined.
Action
If there is 13M or 61.44M clock lost alarm in CCI board, and there is alarm all the same after reset the
board, please exam the clock source; If no 13M or 61.44M clock lost alarm, and there is alarm after
reset GBP all the same, please exam the LVDS access.
3-365
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.415 198087412 60ms clock lost alarm

Alarm Information
Alarm code:
198087412
Name:
60ms clock lost alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
60ms clock lost alarm
Alarm Cause
FR or FN error
Impact
User-defined.
Action
If there is FR or FN error in the CCI, and there is error all the same after reset the CCI, please
exam the hardware; If there is not FR or FN error in the CCI, and there is 60ms clock lost alarm
all the same, please exam the LVDS access.
3.1.416 198087413 26MHz and 52MHz lost of clock alarm

Alarm Information
Alarm code:
198087413
Name:
26MHz and 52MHz lost of clock alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
26MHz and 52MHz lost of clock alarm
3-366
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
the loop of clock is unlock
Impact
User-defined.
Action
If there is 13M clock lost alarm in the CCI, and there is alarm all the same after reset CCI, please
exam the clock source; if there is not 13M clock lost alarm in the CCI, and there is clock lost alarm all
the same after reset GBP, please exam 13M clock LVDS access. If there is no problem with the LVDS
access, please replace the FPGA PLL that is invalid.
3.1.417 198087414 the failure examination alarm of the 60ms uplink

frame
Alarm Information
Alarm code:
198087414
Name:
the failure examination alarm of the 60ms uplink frame
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
the failure examination alarm of the 60ms uplink frame
Alarm Cause
the uplink is not detected the 60ms frame
Impact
User-defined.
Action
If there is up 60ms super frame synchronization head exam failing alarm in the CCI, and there
is alarm all the same after reset CCI, please exam its hardware. If no up 60ms super frame
synchronization head exam failing alarm, and there is alarm all the same after reset GBP, please
exam the LVDS access.
3-367
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.418 198087415 checking block data error alarm

Alarm Information
Alarm code:
198087415
Name:
checking block data error alarm
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
checking block data error alarm
Alarm Cause
the frame data error
Impact
User-defined.
Action
None
3.1.419 198087416 up link LVDS SERDES lost lock alarm

Alarm Information
Alarm code:
198087416
Name:
up link LVDS SERDES lost lock alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
up link LVDS SERDES lost lock alarm
Alarm Cause
SERDES lose clock
3-368
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Impact
User-defined.
Action
If it is of no effect to reset GBP and CCI, please exam the LVDS data format from CCI, else to
replace the LVDS.
3.1.420 198087417 FN error alarm

Alarm Information
Alarm code:
198087417
Name:
FN error alarm
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
FN error alarm
Alarm Cause
the error of frame no error from CCI
Impact
User-defined.
Action
If there is FN error the CCI, and there is error all the same after reset CCI, please exam the hardware.
If no FN error, but there is FN error after reset GBP, exam the LVDS access.
3.1.421 198087432 Diversity antenna lost

Alarm Information
Alarm code:
198087432
Name:
3-369
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Two diversity antenna receive signal, one of diversity antenna is abnormal
Impact
The sensitivity and coverage of the receiver antenna decreases because one of the diversities is faulty.
Action
Reset the TRX; if there is a fault, change the slot; if problem remains, change DTRU.
3.1.422 198087433 Diversity antenna identical

Alarm Information
Alarm code:
198087433
Name:
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Wrong connection of diversity antenna
Impact
The antenna fails to operate because there is a crossed pair of wires.
Action
Check the connection of ant line as quickly as possible.
3-370
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.423 198087451 board not support 16MHW

Alarm Information
Alarm code:
198087451
Name:
board not support 16MHW
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
The IP ABIS function is partially supported and some carrier frequencies are not available.
Action
change the board support 16MHW
3.1.424 198087452 cmb or cpu overload

Alarm Information
Alarm code:
198087452
Name:
cmb or cpu overload
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
cmb or cpu overload
Alarm Cause
cpu usage rate exceed 85%
3-371
SJ-20140527134643-015|2015-03-31 (R1.1)
Impact
Some services may fail to be processed.
Action
wait for a while , and operate service after alarm restored
3.1.425 198087454 main HDLC break off

Alarm Information
Alarm code:
198087454
Name:
main HDLC break off
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
main HDLC break off
Alarm Cause
HDLC break off between CMB and FIB;CMB or FIB hardware error
Impact
Data fails to be transmitted between the CMB and FIB.
Action
1.watch cmb or fib work or not
2.if cmb or fib doesn't work, reset it
3.if alarm does not restore for a long time, please change a new cmb or fib
3.1.426 198087455 FIB configure wrong

Alarm Information
Alarm code:
198087455
Name:
FIB configure wrong
3-372
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
FIB configure wrong
Alarm Cause
parameter Configuration over time or wrong
Impact
This alarm seldom occurs because the back end of the BSC generally checks data validity before
data synchronization.
Action
wait for ten minutes, if alarm still does not restore, ismg configure parameter again, and synchronize
to the site. If problem remain, just change a new fib
3.1.427 198087456 lay3 of FIB software has no response

Alarm Information
Alarm code:
198087456
Name:
lay3 of FIB software has no response
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
lay3 of FIB software has no response
Alarm Cause
FIB software has no respond temporary( set by CMB)
Impact
The back end fails to detect the operation of the FIB.
3-373
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
1.wait for ten minute, and watch whether alarm restore or not
2.ifalarm does not restore for a long time, please pull out the fib board and put it in to slot again
when service not too busy
3.if alarm remain after reset fib, please reset cmb when service not too busy
4.if alarm remain please change a new fib
5.if software has bug, please update to the latest
3.1.428 198087460 positive 12 voltage alarm

Alarm Information
Alarm code:
198087460
Name:
positive 12 voltage alarm
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
positive 12 voltage alarm
Alarm Cause
DPB board of DTRU module, +12V power module has alarm
Impact
Services are affected because the LNA of the cell fails to operate properly.
Action
change DTRU module or BBTR board
3.1.429 198087461 negative 12 voltage alarm

Alarm Information
Alarm code:
198087461
Name:
negative 12 voltage alarm
3-374
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
negative 12 voltage alarm
Alarm Cause
DPB board of DTRU module, -12V power module has alarm
Impact
Services are affected because the LNA of the cell fails to operate properly.
Action
change DTRU module or BBTR board
3.1.430 198087462 DSP 1.2v voltage alarm

Alarm Information
Alarm code:
198087462
Name:
DSP 1.2v voltage alarm
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
DSP 1.2v voltage alarm
Alarm Cause
DPB board of DTRU module, 1.2V power module has alarm
Impact
The DTRU board fails to operate. Cell services may also be affected if the DTRU is configured
as BCCH.
Action
change DTRU module
3-375
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.431 198087463 6.4v voltage alarm

Alarm Information
Alarm code:
198087463
Name:
6.4v voltage alarm
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
6.4v voltage alarm
Alarm Cause
DPB board of DTRU module, 6.4V power module has alarm
Impact
as BCCH.
Action
change DTRU module
3.1.432 198087464 5v voltage alarm

Alarm Information
Alarm code:
198087464
Name:
5v voltage alarm
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
5v voltage alarm
3-376
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
DPB board of DTRU module, 5V power module has alarm
Impact
as BCCH.
Action
change DTRU module
3.1.433 198087473 DTPU CPU overload

Alarm Information
Alarm code:
198087473
Name:
DTPU CPU overload
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
DTPU CPU overload
Alarm Cause
Impact
The services on the DTRU may fail to be processed.
Action
3-377
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.434 198087483 GPS signal synchronization exception

Alarm Information
Alarm code:
198087483
Name:
GPS signal synchronization exception
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
GPS signal synchronization exception
Alarm Cause
Not support GPS synchronization, GPS clock synchronization failed or GPS fault
Impact
Clock synchronization is switched to internal synchronization because GPS synchronization fails.
Action
1. Check whether the current CMB board supports GPS synchronization. If not, replace it with the
new one supporting GPS. 2.To check EIB/FIB if support GPS or not 3.Change EIB/FIB
3.1.435 198087484 Second pulse loss

Alarm Information
Alarm code:
198087484
Name:
Second pulse loss
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Second pulse loss
3-378
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
GPS 1PPS signal loss
Impact
GPS clock synchronization fails.
Action
1. Check the antennas.
2. Check the cable between EIB/FIB and the top of equipment.
3. Check EIB/FIB.
4. Check the CMB Alarm Collect Circuit, if something is wrong in it, replace the relevant unit.
3.1.436 198087485 Antenna open-circuit alarm

Alarm Information
Alarm code:
198087485
Name:
Antenna open-circuit alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Antenna open-circuit alarm
Alarm Cause
GPS Antenna appeared open-circuit exception
Impact
Action
1. Check cable connection from antennas to EIB or FIB, include GPSSP.
3. Check EIB/FIB, if something is wrong in it, replace the relevant unit.
3-379
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.437 198087486 Antenna short-circuit alarm

Alarm Information
Alarm code:
198087486
Name:
Antenna short-circuit alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Antenna short-circuit alarm
Alarm Cause
GPS Antenna appeared short-circuit exception
Impact
Action
1. Check cable connection from antennas to EIB or FIB, include GPSSP if short or not.
3.1.438 198087487 Lost satellite alarm

Alarm Information
Alarm code:
198087487
Name:
Lost satellite alarm
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Lost satellite alarm
3-380
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
GPS does not recognize the satellite
Impact
Action
1.Check connecting of the antennas, and the antennas is hid or not.
2.TCheck the cable between EIB/FIB and the top of equipment.
3.1.439 198087510 CPU of FIB overload

Alarm Information
Alarm code:
198087510
Name:
CPU of FIB overload
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
CPU of FIB overload
Alarm Cause
Impact
Some services may fail to be processed.
Action
3-381
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.440 198088000 DTPU not support Baseband-Hop alarm

Alarm Information
Alarm code:
198088000
Name:
DTPU not support Baseband-Hop alarm
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
Impact
1. The TRXs other than 875DTRU fail to be involved in baseband-hop.
2. The TRXs other than the DTPB fail to be involved in baseband-hop.
Action
1, Check DTRU if DTPB080300 or not, if not , please change to DTPB080300 module
2, If alarm is still exist, please check backplane if BBTR070401 or not , if not, please change to
BBTR070401.
3.1.441 198088001 PA Power Voltage Adjusting Path Disconnected

Alarm Information
Alarm code:
198088001
Name:
PA Power Voltage Adjusting Path Disconnected
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
PA Power Voltage Adjusting Path Disconnected
3-382
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
I2C Path Disconnected
Impact
This fault is adverse to energy saving.
Action
1.Check DTRU supports the function
2.Check 6 Pins Cable
3.Reconnected Cable, if cannot recovery then
4.The DTRU Can Work , Replace the DTRU till New DTRU Coming for PA Power voltage adjusting
function
3.1.442 198088002 PA Power Voltage Adjusting Data Error

Alarm Information
Alarm code:
198088002
Name:
PA Power Voltage Adjusting Data Error
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
PA Power Voltage Adjusting Data Error
Alarm Cause
I2C Data Read or Write Error
Impact
Action
1.Retry Data Setting
2.Check 6 Pins Cable , if cannot recovery then
3.The DTRU Can Work , Replace the DTRU till New DTRU Coming for PA Power voltage adjusting
function
3-383
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.443 198088003 PA Power Voltage Adjusting Data Illegal

Alarm Information
Alarm code:
198088003
Name:
PA Power Voltage Adjusting Data Illegal
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
PA Power Voltage Adjusting Data Illegal
Alarm Cause
Set Data out of Range
Impact
Action
1.Change Static Power data
2.Update setting
3.1.444 198088004 Access iBSC failure

Alarm Information
Alarm code:
198088004
Name:
Access iBSC failure
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Access iBSC failure
3-384
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
Authentication failed or unconnected response
Impact
User-defined.
Action
1.Authentication again
2.Check physical link
3.1.445 198088005 Control link broken

Alarm Information
Alarm code:
198088005
Name:
Control link broken
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Control link broken
Alarm Cause
Communication broken between
BTS and BSC
Impact
User-defined.
Action
1.First, determinate HBTS fault or transmission line problem.
2.Check the process of software By signaling analyzer, determine the problem of BSC or BTS.
3.Amend the relevant software, and upgrade version of the software.
3-385
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.446 198088006 Operation link broken(CS)

Alarm Information
Alarm code:
198088006
Name:
Operation link broken(CS)
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Operation link broken(CS)
Alarm Cause
the transmission line is broken
Impact
User-defined.
Action
check the transmission line
3.1.447 198088007 Operation link broken(PS)

Alarm Information
Alarm code:
198088007
Name:
Operation link broken(PS)
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Operation link broken(PS)
Alarm Cause
the transmission line is broken
3-386
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Impact
User-defined.
Action
3.1.448 198088008 Parameter configuration mismatch

Alarm Information
Alarm code:
198088008
Name:
Parameter configuration mismatch
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Parameter configuration mismatch
Alarm Cause
iBSC parameters configuration
failed, time-out or broken links
Impact
User-defined.
Action
configuration
parameter again.
3.1.449 198088009 DSP initialization failure

Alarm Information
Alarm code:
198088009
Name:
DSP initialization failure
3-387
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
DSP initialization failure
Alarm Cause
DSP software or hardware
error
Impact
User-defined.
Action
1.Download DSP software version again.
2.Reset DSP, if the alarm is not restored alarm, replace HBTS
3.1.450 198088010 Parameter configuration failure of AD6537

Alarm Information
Alarm code:
198088010
Name:
Parameter configuration failure of AD6537
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Parameter configuration failure of AD6537
Alarm Cause
AD6537 register to read
and write error
Impact
User-defined.
3-388
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Action
Power-down Re-starting and re-configuration AD6537, send the
appropriate warning information
3.1.451 198088011 Tx PLL unlock

Alarm Information
Alarm code:
198088011
Name:
Tx PLL unlock
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Tx PLL unlock
Alarm Cause
Clock signal instability or PLL failed
Impact
User-defined.
Action
Forbid TRM, send
warning information
3.1.452 198088012 Wrong parameter configuration for EEPROM

Alarm Information
Alarm code:
198088012
Name:
Wrong parameter configuration for EEPROM
Alarm severity:
Minor
Alarm type:
Equipment Alarm
3-389
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Description
Wrong parameter configuration for EEPROM
Alarm Cause
EEPROM hardware failed or previously written into the EEPROM invalid parameters, resulting in
EEPROM RF parameters can not read.
Impact
User-defined.
Action
send warning information
3.1.453 198088013 FLASH memory fault

Alarm Information
Alarm code:
198088013
Name:
FLASH memory fault
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
FLASH memory fault
Alarm Cause
FLASH programming over the number,
read and write error Or check the software error
Impact
User-defined.
Action
Reset HBTS, Download DSP software version again.if the alarm is not restored alarm, replace HBTS
3-390
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.454 198088014 Run abnormity of DSP

Alarm Information
Alarm code:
198088014
Name:
Run abnormity of DSP
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Run abnormity of DSP
Alarm Cause
DSP programming error
Impact
User-defined.
Action
Reset DSP, load DSP software version, configuration CHP parameters.
3.1.455 198088015 FPGA interface fault

Alarm Information
Alarm code:
198088015
Name:
FPGA interface fault
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
FPGA interface fault
Alarm Cause
DSP and FPGA interface interruption
3-391
SJ-20140527134643-015|2015-03-31 (R1.1)
Impact
User-defined.
Action
load FPGA version again, reset HBTS,
replace HBTS
3.1.456 198088016 CHP frame fault

Alarm Information
Alarm code:
198088016
Name:
CHP frame fault
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
CHP frame fault
Alarm Cause
As the circuit interference so that the frame misoperation
Impact
User-defined.
Action
Reset HBTS
3.1.457 198088017 Wrong receive channel of RF

Alarm Information
Alarm code:
198088017
Name:
Wrong receive channel of RF
3-392
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Wrong receive channel of RF
Alarm Cause
Failure to receive channel, the
normal of signals up
Impact
User-defined.
Action
Download FPGA, DSP version again, configuration system parameters.
3.1.458 198088018 Get DNS failure when configuration IP of active

Alarm Information
Alarm code:
198088018
Name:
Get DNS failure when configuration IP of active
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Get DNS failure when configuration IP of active
Alarm Cause
HBTS can not get to the IP address from the DNS server
Impact
User-defined.
Action
Configuration the IP address of DNS by LMT.
3-393
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.459 198088019 Analyse failure of DNS domain name

Alarm Information
Alarm code:
198088019
Name:
Analyse failure of DNS domain name
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Analyse failure of DNS domain name
Alarm Cause
HBTS can not get to the IP address from the DHCP server
Impact
User-defined.
Action
Configuration the IP address, port of iBSC by LMT.
3.1.460 198088020 IPSec failure

Alarm Information
Alarm code:
198088020
Name:
IPSec failure
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
IPSec failure
Alarm Cause
Can not access
3-394
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Impact
User-defined.
Action
Configuration IPSec parameter again
3.1.461 198088021 RF channel and HTRG board unconformity

Alarm Information
Alarm code:
198088021
Name:
RF channel and HTRG board unconformity
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
RF channel and HTRG board unconformity
Alarm Cause
Hardware does not support requencies information
Impact
User-defined.
Action
1.reset the frequency point with HTRG
2.Replace supporting the rang of frequency HTRG
3.1.462 198088022 Get HBTS'S IP address failure from DHCP Sever

Alarm Information
Alarm code:
198088022
Name:
Get HBTS'S IP address failure from DHCP Sever
3-395
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Get HBTS'S IP address failure from DHCP Sever
Alarm Cause
HBTS can not automatically get
to the IP address from the DHCP server
Impact
User-defined.
Action
Configuration the IP address, subnet mask, gateway, port of iBSC and HBTS by LMT.
3.1.463 198088023 Over temperature

Alarm Information
Alarm code:
198088023
Name:
Over temperature
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Over temperature
Alarm Cause
Over temperature
Impact
User-defined.
Action
Switch off power, check
3-396
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.464 198088024 Voltage abnormity

Alarm Information
Alarm code:
198088024
Name:
Voltage abnormity
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
Voltage abnormity
Alarm Cause
Voltage abnormity
Impact
User-defined.
Action
Check power
3.1.465 198088025 Abis link change alarm

Alarm Information
Alarm code:
198088025
Name:
Abis link change alarm
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Abis link change alarm
3-397
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Cause
Abis link on the earth surface is broken, then the service of satellite-backup site changes to the
satellite abis link
Impact
This fault has no impact on a service if the service is successfully switched over.
Action
check the abis link on the earth surface, and restore it as soon as possible
3.1.466 198088026 IPOE uplink and downlink jam alarm

Alarm Information
Alarm code:
198088026
Name:
IPOE uplink and downlink jam alarm
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
IPOE uplink and downlink jam alarm
Alarm Cause
IPOE site detect the jam of uplink and downlin
Impact
Service quality degrades or even the service is interrupted.
Action
3-398
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.467 198088027 DIP E1 rack, rack type error

Alarm Information
Alarm code:
198088027
Name:
DIP E1 rack, rack type error
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
DIP E1 rack, rack type error
Alarm Cause
No. 15 to 12 bits of E1 rack DIP, rack type error
Impact
A link may fail to be established after the E1 rack is rebooted.
Action
check E1 rack No. 15 to 12 bits of the DIP
3.1.468 198088028 DIP E1 rack, rack number error

Alarm Information
Alarm code:
198088028
Name:
DIP E1 rack, rack number error
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
DIP E1 rack, rack number error
Alarm Cause
No. 11 to 10 bits of E1 rack, rack number error
3-399
SJ-20140527134643-015|2015-03-31 (R1.1)
Impact
Action
3.1.469 198088029 DIP E1 rack,slave rack 1 port error

Alarm Information
Alarm code:
198088029
Name:
DIP E1 rack,slave rack 1 port error
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
No. 9 to 8 bits of E1 rack, slave rack 1 port error
Impact
Slave rack 1 of the E1 BTS may fail to operate properly.
Action
3.1.470 198088030 DIP E1 rack,slave rack 2 port error

Alarm Information
Alarm code:
198088030
Name:
Alarm severity:
Warning
3-400
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm type:
Equipment Alarm
Alarm Description
Alarm Cause
No. 7 to 6 bits of E1 rack, slave rack 2 port error
Impact
Slave rack 2 of the E1 BTS may fail to operate properly.
Action
3.1.471 198088031 DIP E1 rack,satellite back up flag error

Alarm Information
Alarm code:
198088031
Name:
DIP E1 rack,satellite back up flag error
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
DIP E1 rack,satellite back up flag error
Alarm Cause
No. 5 bit of E1 rack, satellite back up flag error
Impact
The backup satellite link of the E1 BTS may fail to operate properly.
Action
check E1 rack No. 5 bit of the DIP
3-401
SJ-20140527134643-015|2015-03-31 (R1.1)
3.1.472 198088032 DIP E1 rack,oam time slot error

Alarm Information
Alarm code:
198088032
Name:
DIP E1 rack,oam time slot error
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
DIP E1 rack,oam time slot error
Alarm Cause
No. 4 to 0 bits of E1 rack, oam time slot error
Impact
Action
3.1.473 198088033 DIP IP rack,access mode error(IP or IPOE)

Alarm Information
Alarm code:
198088033
Name:
DIP IP rack,access mode error(IP or IPOE)
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
DIP IP rack,access mode error(IP or IPOE)
Alarm Cause
No. 15 to 14 bits of IP rack, access mode error( IP or IPOE)
3-402
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Impact
A link may fail to be established after the IP rack is rebooted.
Action
check IP rack No. 15 to 14 bits of the DIP
3.1.474 198088034 DIP IP rack,rack number error

Alarm Information
Alarm code:
198088034
Name:
DIP IP rack,rack number error
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
DIP IP rack,rack number error
Alarm Cause
No. 13 to 12 bits of IP rack, rack number error
Impact
Action
3.1.475 198088035 DIP IP rack,site number error

Alarm Information
Alarm code:
198088035
Name:
DIP IP rack,site number error
Alarm severity:
Warning
3-403
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm type:
Equipment Alarm
Alarm Description
DIP IP rack,site number error
Alarm Cause
No. 11to 0 bits of IP rack, site number error
Impact
Action
3.1.476 198088036 DIP IP rack,sequence number error

Alarm Information
Alarm code:
198088036
Name:
DIP IP rack,sequence number error
Alarm severity:
Warning
Alarm type:
Equipment Alarm
Alarm Description
DIP IP rack,sequence number error
Alarm Cause
IP rack, sequence number configured on NMS is error
Impact
Action
ON NMS, check the sequence number of the IP site
3-404
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.1.477 198088037 Mains power failure alarm

Alarm Information
Alarm code:
198088037
Name:
Mains power failure alarm
Alarm severity:
Major
Alarm type:
Equipment Alarm
Alarm Description
Mains power failure alarm
Alarm Cause
AC mains failure
Impact
User-defined.
Action
check AC
3.1.478 198088038 Alarm of the trx's down link LRC failed

Alarm Information
Alarm code:
198088038
Name:
Alarm of the trx's down link LRC failed
Alarm severity:
Minor
Alarm type:
Equipment Alarm
Alarm Description
the LRC of the PLL parameter failed
Alarm Cause
the parameter FPGA received is abnormal, or the channel of McBSP is abnormal.
3-405
SJ-20140527134643-015|2015-03-31 (R1.1)
Impact
The RF phase-lock loop is unlocked.
Action
Change another DTRU
3.1.479 199005784 Please reboot the board after you have saved
the new configuration to make it effective
Alarm Information
l
l
l
l

Name: Please reboot the board after you have saved the new configuration to make
it effective
Alarm Description
Please reboot the board after you have saved the new configuration to make it effective.
Alarm Cause
The configuration is changed.
Impact
The new configure can't be effective.
Action
1. Check the current configuration is to be expectation one.
Y->Go to "2".
N->Go to "3".
2. Check the board has been reboot after saving the configuration.
Y->Go to "5".
N->Go to "4".
3. Modify the configuration to be the pre-configuration, then check the alarm if it is eliminated.
Y->If it is eliminated, end alarm handling.
N->If it still exists, go to "5".
4. Please reboot the board by yourself after saving the configuration. After this board power on,
check the alarm if it is eliminated.
Y->If it is eliminated, end alarm handling.
N->If it still exists, go to "5".
3-406
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
5. Note down the alarm information and contact the next level of maintenance support.
3.2 Processing error Alarm

3.2.1 199002560 CPU utilization over alarm limit
Alarm Information
l
l
l
l

Name: CPU utilization over alarm limit
Alarm type: Processing error Alarm
Alarm Description
This alarm is raised if the board detects that the CPU usage exceeds the alarm threshold
(parameter "Threshold of CPU low level overload(RateLowThr)" and "Threshold of CPU high level
overload(RateHighThr)" of "Physical CPU(PhysCpu)" object).
Alarm Cause
l
The alarm threshold is too low.
Multiple time-consuming operations are performed concurrently.
A periodical task that involves large traffic is triggered.
Impact
The system performance is affected and thus the system operates slowly.
Action
1. Check whether "CPU high threshold" and "CPU low threshold" in the alarm information of the
faulty board meet the actual requirements.
Yes -> Step 3.
No -> Step 2.
Yes -> End.
No -> Step 3.
3. Check whether there are many current access subscribers.
Yes -> Step 6.
No -> Step 4.
3-407
SJ-20140527134643-015|2015-03-31 (R1.1)
4. Check whether files are transmitted between the network management system and the NE or
other manual operations are done on the network management system.
Yes -> Step 5.
No -> Step 6.
5. Stop the file transmission or manual operations, and check whether the alarm is cleared.
Yes -> End.
No -> Step 6.
3.2.2 199003584 Memory insufficient alarm

Alarm Information
Code:
199003584
Name:
Memory insufficient alarm
Severity:
Major
Type:
Processing error Alarm
Alarm Description
This alarm is raised if the board detects that the memory usage exceeds the set threshold (Physical
CPU(PhysCpu) object).
Probable Cause
l
Services are busy, so the memory usage is high.
The board cannot operate properly.
The memory is damaged.
System Impact
The system performance is affected and thus the system operates slowly.
3-408
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Handling Suggestion
1. Check whether the "Memory alarm threshold" in the alarm information of the faulty board meets
the actual requirements.
Yes -> Step 3.
No -> Step 2.
2. Query the "Physical CPU(PhysCpu)" child object of the "Board(Board)" object in accordance
with the physical position of the faulty board, and modify the "Threshold of Memory lack
alarm(MEMAlmThr)" parameter as required. Check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3. Check whether the traffic reaches the threshold of the network performance planning.
Yes -> Contact the network optimization department to determine whether it is necessary to
perform network optimization.
No -> Step 4.
3.2.3 199004357 The system bureau changed

Alarm Information
l
l
l
l

Name: The system bureau changed
Alarm Description
This alarm is raised if the system's office number changes.
Alarm Cause
The configuration of the system office number changes.
Impact
If some boards are not restarted, the services on these boards may be affected.
Action
Run the SET ALLNE RESET command to reset the entire NE.
3-409
SJ-20140527134643-015|2015-03-31 (R1.1)
3.2.4 199005908 Lack of version

Alarm Information
l
l
l
l

Name: Lack of version
Alarm Description
This alarm is raised if the version information of the board is not complete.
Alarm Cause
l
The service set is not configured correctly.
The corresponding version package is not activated.
The version package lacks a version file.
Impact
The board cannot be powered on, and thus corresponding functions cannot be provided.
Action
3.2.5 199005909 Download version failed

Alarm Information
l
l
l
l

Name: Download version failed
Alarm Description
This alarm is raised if the board fails to download the version file from the OMP.
Alarm Cause
l
The control plane communication of the NE is abnormal.
The version file is damaged.
3-410
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Impact
Action
1. 1. Check whether the following alarms are raised:.
199393988 Control plane communication abnormal between module and OMP
199393986 Control plane communication is abnormal between this board and the active
independent board
Yes -> Step 2.
No -> Step 3.
2. Handle the above alarms, wait for five minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3.2.6 199005910 Process execute failed

Alarm Information
l
l
l
l

Name: Process execute failed
Alarm Description
This alarm is raised if the board process fails to be started.
Alarm Cause
l
The published version file is unavailable.
The version property is not correct.
Impact
The version file fails to be executed, and therefore the board may fail to be powered on.
Action
3-411
SJ-20140527134643-015|2015-03-31 (R1.1)
3.2.7 199025600 Connection check be disabled in board

Alarm Information
l
l
l
l

Name: Connection check be disabled in board
Alarm Description
This alarm is raised if the function for checking CS connection error is disabled for more than two
minutes.
Alarm Cause
Specifying a subunit loopback, specifying a subunit time slot loopback, specifying an HW loopback,
and specifying an HWtime slot loopback The corresponding loopback operation is not canceled
within two minutes.
Impact
If the CS connection is abnormal, this fault cannot be recovered automatically. Services using CS
may be affected, for example, voice calls and signaling links.
Action
1. Run the SET DISLOOP ALLUNITcommand to disconnect all loopback links in accordance with
Yes -> End.
No -> Step 2.
3.2.8 199066032 SNTP time synchronization exceeded the threhold

Alarm Information
l
l
l
l

Name: SNTP time synchronization exceeded the threhold
3-412
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Description
This alarm is raised if the difference between the NE time and the time of the SNTP server exceeds
the threshold (parameter "SNTP networking mode(SntpSynChannel)" of "Operation Maintenance
Configuration(OmCon)" object) during the time synchronization in OMP networking mode (parameter
"SNTP error limit(SntpGapThr)" of "Operation Maintenance Configuration(OmCon)" object).
The OMP networking mode means that the NE uses the OMP as the SNTP client to send a time
request to the SNTP server, and each board obtains the time from the OMP board.
Alarm Cause
l
SNTP server time jumps forward.
NE time jumps forward.
Impact
The system time may be incorrect, so all functions relating to the time are affected (for example, the
performance statistics result is incorrect, and the alarm reporting time is incorrect).
Action
1. Check whether the "Alarm threshold (ms)" in the alarm information meets the actual requirements.
Yes -> Step 3.
No -> Step 2.
2. Modify the "SNTP error limit(SntpGapThr)" parameter of the "Operation Maintenance
Configuration(OmCon)" object as required, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3. Check the "OMP time (GMT)" and "Time (GMT) from the SNTP server" in the alarm information.
Run the QRY TIME command to query the board time in accordance with the "Rack number",
"Shelf number", and "Slot number" in the alarm information to determine which time is more
accurate.
The "Time (GMT) from the SNTP server" is more accurate -> Step 4.
The "OMP time (GMT)" is more accurate -> Step 5.
There is no method for determining which time is more accurate -> Step 7.
4. Run the SET NTPSYN command to originate NTP time synchronization. Wait for one minute, and
Yes -> End.
No -> Step 7.
5. Contact the maintenance personnel of SNTP server to check whether related alarms exist.
Yes -> Step 6.
No -> Step 7.
6. Wait for the maintenance personnel of SNTP server to resolve related faults. Go to Step 4.
3-413
SJ-20140527134643-015|2015-03-31 (R1.1)
3.2.9 199066027 SNTP time synchronization failed

Alarm Information
l
l
l
l

Name: SNTP time synchronization failed
Alarm Description
This alarm is raised if the NE receives no response or an incorrect response from the SNTP server
after it transmits a time synchronization request to the SNTP server during time synchronization.
Alarm Cause
l
The IP address of the configured SNTP server does not exist, or the device with the
corresponding IP address is not enabled with the SNTP service.
The SNTP server does not operate properly, or the time of the SNTP server is not synchronized
with its upper-level server.
The configured time synchronization period of the NE is less than 16 seconds.
Impact
The time cannot be synchronized from the SNTP server. The system time may be incorrect, so all
functions relating to the time are affected (for example, the performance statistics result is incorrect,
and the alarm reporting time is incorrect).
Action
1. Check whether the "IP address of SNTP server(SntpServer)" and "SNTP synchronization
cycle(SntpSyncPer)" parameters of the "Operation Maintenance Configuration(OmCon)" object
are set as required.
Yes -> Step 3.
No -> Step 2.
2. Modify the "IP address of SNTP server(SntpServer)" parameter of the "Operation Maintenance
Yes -> End.
No -> Step 3.
Yes -> Step 4.
No -> Step 5.
4. Wait for the maintenance personnel of SNTP server to resolve related faults. Run the SET
NTPSYN command to originate NTP time synchronization. Wait for one minute, and check
Yes -> End.
No -> Step 5.
3-414
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.2.10 199392708 Time synchronization over alarm limit in RPU

accesstype
Alarm Information
l
l
l
l

Name: Time synchronization over alarm limit in RPU accesstype
Alarm Description
This alarm is raised if the difference between the NE time and the time of the SNTP server exceeds
the threshold (parameter "SNTP networking mode(SntpSynChannel)" of "Operation Maintenance
Configuration(OmCon)" object) during time synchronization in RPU networking mode (parameter
"SNTP error limit(SntpGapThr)" of "Operation Maintenance Configuration(OmCon)" object).
The RPU networking mode means that the NE uses the RPU as the SNTP client to transmit a time
request to the SNTP server, and transmits the time to the OMP board, and each board obtains the
time from the OMP board.
Alarm Cause
l
SNTP server time jumps forward.
NE time jumps forward.
Impact
The system time may be incorrect, so all functions relating to the time are affected (for example, the
performance statistics result is incorrect, and the alarm reporting time is incorrect).
Action
1. Check whether the "Alarm threshold (ms)" in the alarm information meets the actual requirements.
Yes -> Step 3.
No -> Step 2.
2. Modify the "SNTP error limit(SntpGapThr)" parameter of the "Operation Maintenance
Yes -> End.
No -> Step 3.
3. Check the "OMP time (GMT)" and "Time (GMT) from the SNTP server" in the alarm information.
Run the QRY TIME command to query the board time in accordance with the "Rack number",
3-415
SJ-20140527134643-015|2015-03-31 (R1.1)
"Shelf number", and "Slot number" in the alarm information to determine which time is more
accurate.
The "Time (GMT) from the SNTP server" is more accurate -> Step 4.
The "OMP time (GMT)" is more accurate -> Step 5.
There is no method for determining which time is more accurate -> Step 7.
4. Run the SET NTPSYN command to originate NTP time synchronization. Wait for one minute, and
Yes -> End.
No -> Step 7.
Yes -> Step 6.
No -> Step 7.
6. Wait for the maintenance personnel of SNTP server to resolve related faults. Go to Step 4.
3.2.11 199399616 LAPD link broken

Alarm Information
Code:
199399616
Name:
LAPD link broken
Severity:
Minor
Type:
Alarm Description
This alarm is raised if the LAPD link is disconnected.
Probable Cause
l
The local end deactivates the layer-3 links.
The configuration is not correct.
The bottom layer link is faulty, for example, transmission fault.
The peer end is faulty, for example, the peer link is deactivated.
The hardware of the local port is faulty.
System Impact
The service fails.
3-416
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Handling Suggestion
1. Query the "Mtp2 Link" object that references "Signalling Link" of the alarm object, and check
whether "Beginning slot number of E1" and "Slot number of signalling link" are consistent with
those on the peer end.
Yes -> Step 3.
No -> Step 2.
2. Modify the local configuration or request the peer end to modify the peer-end configuration as
required so that "Beginning slot number of E1" and "Slot number of signalling link" are the same
on both ends, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3. Query the referenced object "Logical E1" or "Logical T1" in accordance with the "Mtp2 Link"
object,A1015[]and determine the E1/T1 frame format in accordance with "Logical E1" or "Logical
T1".
Check whether the E1/T1 frame format is the same as that on the peer end.
Yes -> End.
No -> Step 5.
4. Modify the local configuration or request the peer end to modify the peer-end configuration as
required so that the E1/T1 frame formats are the same on both ends, and check whether the
alarm is cleared.
Yes -> End.
No -> Step 5.
3.2.12 199066013 MTP3 link congestion

Alarm Information
l
l
l
l

Name: MTP3 link congestion
Alarm Description
This alarm is raised if the MTP3 link detects that the usage of the signaling sending buffer area
reaches 85%.
Alarm Cause
l
The load of the links in the link group is not balanced.
Too many services are carried, which results in insufficient link configuration.
3-417
SJ-20140527134643-015|2015-03-31 (R1.1)
Impact
This link congestion may result in package loss, call loss, and even link disconnection.
Action
1. Wait for five minutes if the traffic is heavy, and check whether the alarm is cleared.
Yes -> End.
No -> Step 2.
2. Run the QRY MTP3LINKSETSTATUS command in accordance with the "Link set ID" in the
alarm information, and check whether other MTP2 links in the link set are in normal status.
Yes -> Step 5.
No -> Step 3.
3. Check whether unavailable links in the same link set have the following alarm:
199066011 MTP3 link unavailable
Yes -> Step 4.
No -> Step 5.
Yes -> End.
No -> Step 5.
5. Contact the planning personnel for new signaling links or contact the next level of maintenance
support.
3.2.13 199005202 Configuration conflicts between DBS and CMM

Alarm Information
Code:
199005202
Name:
Configuration conflicts between DBS and CMM
Severity:
Major
Type:
Alarm Description
This alarm is raised if the board property configured in the CMM is inconsistent with that configured
on the OMP.
Probable Cause
l
The board type configured on the CMM is OMP, but the board is not configured as an OMP
board on the OMP.
The board type configured on the CMM is not OMP, but the board is configured as an OMP
board on the OMP.
3-418
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
System Impact
Board operation is affected.
Handling Suggestion
1. Check whether "Whether the board is configed as OMP on CMM" in the alarm information is "NO".
Yes -> Step 2.
No -> Step 5.
2. Check whether the board should be configured as an OMP board.
Yes -> Step 3.
No -> Step 4.
3. In "ECMM shelf board info" of "Independent Board Configuration Online", set the board type to
"OMP board". Restart the board, and check whether the alarm is cleared.
Yes -> End.
No -> Step 8.
4. Configure the board as a non-OMP board. Reset the board, and check whether the alarm
is cleared.
Yes -> End.
No -> Step 8.
5. Check whether the board should be configured as an OMP board.
Yes -> Step 6.
No -> Step 7.
6. Configure the board as an OMP board. Reset the board, and check whether the alarm is cleared.
Yes -> End.
No -> Step 8.
7. In "ECMM shelf board info" of "Independent Board Configuration Online", set the board type to
"Non OMP board". Restart the board, and check whether the alarm is cleared.
Yes -> End.
No -> Step 8.
3.2.14 199005912 BOOTROM version update failed

Alarm Information
Code:
199005912
Name:
BOOTROM version update failed
Severity:
Warning
Type:
3-419
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Description
This alarm is raised if the BOOT version fails to be updated.
Probable Cause
l
The version package is activated but the corresponding version file is deleted.
The BOOT version fails to be burnt.
System Impact
The BOOT version fails to be updated, and thus board functions may be affected.
Handling Suggestion
3.2.15 199409857 Routing table utilization exceeds the second

threshold
Alarm Information
Code:
199409857
Name:
Routing table utilization exceeds the second threshold
Severity:
Minor
Type:
Alarm Description
This alarm is generated when the IPv4 routing tables or the number of LSAs in the OSPF link status
database reaches the second threshold set in advance "Alarm threshold 2".
Probable Cause
This alarm is raised if the usage rate of the routing table reaches the second threshold. The possible
causes are as follows:
l
Too many IP addresses are configured, so the usage of the routing table exceeds the second
threshold.
Too many static routes are configured in this NE, so the usage of the routing table exceeds
the second threshold.
The OSPF instance of this NE learns too many routes from other neighbors, so the usage of the
routing table exceeds the second threshold.
The OSPF instance of this NE learns too many LSAs from other neighbors, so the usage of the
routing table exceeds the second threshold.
3-420
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
System Impact
This alarm does not affect system operation. If the routing table of the system is full, new routes
cannot be added, and related services are interrupted.
Handling Suggestion
1. Run the QRY RPU INTERFACEcommand to check whether the IP addresses configured for all
UP interfaces meet the actual requirements.
Yes -> Step 3.
No -> Step 2.
2. Add, delete or modify the interface object as required. Wait for five minutes, and check whether
Yes -> End.
No -> Step 3.
3. Check whether the configuration of the "Static Route(IPV4)(StaticRoute)" object meets the
Yes -> Step 5.
No -> Step 4.
4. Add, delete or modify the "Static Route(IPV4)(StaticRoute)" object as required. Wait for five
Yes -> End.
No -> Step 5.
5. Contact the maintenance personnel of the peer device to check whether the configuration related
to the dynamic route meets the actual requirement.
Yes -> Step 7.
No -> Step 6.
6. After the maintenance personnel of the peer device modifies the configuration as required, wait
for five minutes, and check whether the alarm is cleared.
Yes -> End.
3.2.16 199087482 dbsapp data error alarm

Alarm Information
Alarm code:
199087482
Name:
dbsapp data error alarm
Alarm severity:
Major
Alarm type:
3-421
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Description
This alarm is reported if the BSC detects data errors in the following two processes:
l
Power-on loading
Data synchronization
Alarm Cause
Configuration data errors occur.
Impact
Some or all services may operate improperly.
Action
1. In Configuration Management, perform the "Synchronize All Data" operation on the
configuration data. Wait for five minutes, and check whether the alarm is cleared.
Caution!
The "Synchronize All Data" operation may cause a system restart. Perform the operation with care.
Yes -> End.

No -> Step 2.
2. Execute the SET NORMALCHANGE command for active/standby switchover based on "Rack
number", "Shelf number", "Slot number", and "CPU number" in the alarm details. Wait for two
Yes -> End.
No -> Step 3.
3.2.17 199087505 Board Connect Fail

Alarm Information
Alarm code:
199087505
Name:
Board Connect Fail
Alarm severity:
Major
Alarm type:
3-422
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Description
This alarm is reported if the BSC detects that the service connection failure count of one board
exceeds the threshold.
Alarm Cause
l
The card version is not correct.
The board is configured improperly.
The versions of the base station and the base station controller are not compatible with each
other.
Impact
Some services are not available.
Action
If the alarm is reported that the cause of ETCB board alarm is 7, or the cause of EDTB board alarm is
4, or the cause of RUP alarm is 7 or 9, the port number is allocated unsuccessfully. You need to query
the network management system and check whether the IPUDP resources assigned to the board
is sufficient. If the IPUDP resources are insufficient, you need increase the resources. Otherwise,
contact the next level of maintenance support.
If the alarm is reported that the cause of ETCB board alarm is 11 or the cause of EDTB board alarm is
8, the next hop is obtained unsuccessfully. You need to check whether the version of the base station
is not compatible with the version of the BSC. If the version of the base station is not compatible with
the version of the BSC, you need to load the proper version for the base station. If the version of the
base station is compatible with the version of the BSC, you need to check the route configuration
of CN user plane. If the route configuration of CN user plane is incorrect, you need to modify the
configuration. Otherwise, contact the next level of maintenance support.
If the alarm is reported that the cause of EDBB/EDAB board alarm is 11, or the cause of ETCB board
alarm is 24, or the cause of EDTB board alarm is 21, you need to check whether the gateway shelf is
configured. If the gateway shelf is not configured, you need to configure it. Otherwise, contact the
next level of maintenance support.
3.2.18 199105051 The configuration of master and slave logservice

is inconsistent
Alarm Information
l
l
l
l

Name: The configuration of master and slave logservice is inconsistent
Alarm type: Processing error alarm
3-423
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Description
When the active log server detects that its configuration data is not the same as that of the standby
log server, this alarm is raised.
Alarm Cause
The differences in the configuration data include:
l
The versions of the active and standby log servers are different.
The network interface channels of the active and standby log servers are differently configured.
The processes of the active and standby log servers are differently configured.
Impact
If the active and standby log servers are switched over, the new active log server after switchover
may fail to operate properly.
Action
3.2.19 199101000 Fail to load DPI Signature library

Alarm Information
l
l
l
l

Name: Fail to load DPI Signature library
Alarm Description
Fail to load DPI Signature library.
Alarm Cause
The reasons for failing to load DPI Signature library may include:
l
Signature library decryption failed (10000);
Signature library MD5 check error (10001);
Signature library version error (10002);
Signature library decoding failed (10003);
LSI chip loading Signature library failed (10005);
Signature library file size exceeds the upper limit (10006) ;
Signature library loads incomplete file (10007);
Signature library file opening failed (10008);
Signature library file reading failed (10009);

3-424
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Signature library private data area, block information type error (10010);
Signature library private data area, block information size error (10011);
Signature library private data area, memory insufficient (10012);
Signature library shared data area, block information type error (10013);
Signature library shared data area, block information size error (10014);
Signature library shared data area, memory insufficient (10015);
Signature library shared data area, data configuration block information type error (10016);
Signature library shared data area, data configuration node number error (10017);
Signature library shared data area, data configuration block size check error (10018);
Signature library shared data area, data configuration memory insufficient (10019);
Signature library load and read software parameter out of range (10020);
Signature library function mapping error (10021)
Impact
DPI function error.
Action
1. Check whether the Signature library version is correct; choose the Signature library version
corresponding to the DPI foreground engine to reactivate.
2. Contact DPI platform engineer to locate the problem according to the error code in the alarm
information.
3.2.20 199101001 Fail to initialize DPI regular engine

Alarm Information
l
l
l
l

Name: Fail to initialize DPI regular engine
Alarm Description
Fail to initialize DPI regular engine.
Alarm Cause
The reasons for failing to initialize DPI regular engine may include:
l
DPI(LSI) subcard is absent
DPI(LSI) subcard has hardware failure
DPI(LSI) subcard has software failure
3-425
SJ-20140527134643-015|2015-03-31 (R1.1)
Impact
DPI function error.
Action
1. Check whether there is DPI (LSI) subcard; if there is not, replace the hardware.
2. For DPI (LSI) subcard failure, first restart the system to check whether the problem is solved; if
not, contact the hardware engineer to check whether the DPI (LSI) subcard is normal.
3. Contact LSI support engineer to locate the problem according to the error code (1-1024) in
3.2.21 199101002 DPI regular engine run check failed

Alarm Information
l
l
l
l

Name: DPI regular engine run check failed
Alarm Description
DPI regular engine run check failed.
Alarm Cause
The reasons why DPI regular engine run check failed may include:
l
DPI (LSI) subcard has a sudden hardware failure or software error (11024).
Self-test string rule matching error (1025).
Impact
DPI function error.
Action
1. Contact LSI support engineer to locate the problem according to the error code (1-1024) in
2. Restart the system to check whether the problem is solved; if not, contact the hardware engineer
to check whether the DPI (LSI) subcard is normal.
3. Check whether the feature library version corresponds to the DPI foreground engine version
(1025).
3-426
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.3 Communications Alarm

3.3.1 199003841 The control plane retransfer ratio over the
threshold
Alarm Information
l
l
l
l

Name: The control plane retransfer ratio over the threshold
Alarm type: Communications Alarm
Alarm Description
This alarm is raised if the board detects that the control-plane communication between this board
and other boards is abnormal.
Alarm Cause
l
Some boards of the system are in poor contact, which results in an increase of the retransmission
of control-plane messages.
The Ethernet communication device on the board or the switching board is faulty.
Impact
Messages transmitted among control planes of different boards are delayed or lost, and thus services
may be affected.
Action
1. Check whether an alarm is raised on the control-plane switching board in the shelf where the
alarm board is located in accordance with the rack diagram in the network management system.
Yes -> Step 2.
No -> Step 3.
2. Clear the alarm on the switching board, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3. Unplug and plug the faulty board (refer to Installing a Board and Removing a Board), wait for
the board to be powered on (the HOST indicator flashes at 1 Hz), and check whether the alarm
is cleared.
Yes -> End.
No -> Step 4.
3-427
SJ-20140527134643-015|2015-03-31 (R1.1)
3.3.2 199005122 Loss of Active/standby communication link

Alarm Information
Code:
199005122
Name:
Loss of Active/standby communication link
Severity:
Minor
Type:
Communications Alarm
Alarm Description
This alarm is raised on both the active and the standby boards respectively if the communication
between them is abnormal.
Probable Cause
l
The board is in active and standby configuration, but only the active board is installed. The
standby board is unavailable or fails to be powered on.
The switching board on the control plane in the shelf is unavailable or faulty.
System Impact
The communication between the active board and the standby board fails, and therefore, data cannot
be synchronized between them. The system reliability is affected.
Handling Suggestion
1. Query the slot number of the partner board in accordance with "Rack number", "Shelf number",
and "Slot number" in the alarm information and the "Backup Slot No. (StandbySlot)" parameter of
the "Board(Board)" object. Check whether the following alarms are raised on the partner board:
199066003 Control plane communication link off between PP and its home module
199393988 Control plane communication link off between the module and OMP
Yes -> Step 2.
No -> Step 3.
Yes -> End.
No -> Step 3.
Replacement), wait for five to ten minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 4.
3-428
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.3.3 199005382 Environment monitor board communication is

abnormal
Alarm Information
l
l
l
l

Name: Environment monitor board communication is abnormal
Alarm Description
This alarm is raised if the CMM detects that the communication between it and the environment
monitoring board is abnormal.
Alarm Cause
l
The environment monitoring board is not connected correctly or the DIP is not set correctly.
The environment monitoring board hardware is faulty.
Impact
The power module of the rack and the environment statuses cannot be monitored.
Action
1. Check whether "Rack number" in the alarm information is correct.
Yes -> Step 3.
No -> Step 2.
2. Query the "Rack" object in accordance with "Rack number" in the alarm information, and delete
the environment monitoring configuration. Check whether the alarm is cleared.
Yes -> End.
No -> Step 8.
3. Check whether the cabling of the environment monitoring board is correct.
Yes -> Step 5.
No -> Step 4.
4. Connect cables to the environment monitoring board properly, and check whether the alarm
is cleared.
Yes -> End.
No -> Step 5.
5. Check whether the DIP setting of the environment monitoring board is consistent with "Rack
number" in the alarm information.
Yes -> Step 7.
No -> Step 6.
6. Modify the DIP setting as required, and check whether the alarm is cleared.
Yes -> End.
3-429
SJ-20140527134643-015|2015-03-31 (R1.1)
No -> Step 7.
7. Replace the environment monitoring cable, and check whether the alarm is cleared.
Yes -> End.
No -> Step 8.
3.3.4 199005396 Packet loopback test of internal media plane

abnormal
Alarm Information
l
l
l
l

Name: Packet loopback test of internal media plane abnormal
Alarm Description
The board detects that the packet loopback on the internal media plane is abnormal (packet loopback
refers to that this board transmits a detection packet to the switching board on the media plane in
the same shelf, and then the packet is forwarded to this board).
Alarm Cause
l
The internal port's physical chip of this board is faulty.
The switching board on the media plane in this shelf is faulty.
The pins of this board are damaged.
The communication of the media plane exceeds the processing capability of the board.
Impact
Media streams cannot be transmitted properly, and thus services may be affected.
Action
1. 1 Check whether the following alarm is raised on the faulty board:
199007168 Port trunk failed
Yes -> Step 2.
No -> Step 3.
Yes -> End.
No -> Step 3.
3. Check whether the media-plane switching board in the same shelf is operating properly through
the rack diagram (refer to Controller Rack).
Yes -> Step 5.
3-430
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
No -> Step 4.
4. Resolve the switching board fault, and check whether the alarm is cleared.
Yes -> End.
No -> Step 5.
5. Reset all media-plane switching boards in the shelf. Wait for ten minutes, and check whether
Yes -> End.
No -> Step 6.
6. Replace the faulty board and media-plane switching boards in the same shelf in sequence, and
Yes -> End.
No -> Step 7.
3.3.5 199005397 Communication of RAW MAC channel is abnormal

Alarm Information
l
l
l
l

Name: Communication of RAW MAC channel is abnormal
Alarm Description
This alarm is raised if the board detects that the communication of the RAW MAC channel (through
this internal channel, packets are forwarded from the media plane to the control plane) is abnormal.
Alarm Cause
Impact
Service quality may be reduced. In serious cases, services are interrupted.
Action
Yes -> End.
No -> Step 2.
3-431
SJ-20140527134643-015|2015-03-31 (R1.1)
3.3.6 199005406 Sub-unit state is abnormal

Alarm Information
l
l
l
l

Name: Sub-unit state is abnormal
Alarm Description
This alarm is raised if the board detects that the SLAVE sub-unit is in abnormal status.
Alarm Cause
Software fault.
Impact
Services on the SLAVE sub-unit may be interrupted.
Action
"Shelf number", "Slot number", and "CPU number" in the alarm information, and check whether
Yes -> End.
No -> Step 2.
3.3.7 199025631 LVDS link error

Alarm Information
l
l
l
l

Name: LVDS link error
Alarm Description
This alarm is raised if the circuit connection channel between the active and standby boards is
abnormal.
3-432
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
l
The board input clock or the phase-lock loop is abnormal.
The circuit switching chip of the board or other hardware is faulty.
The rear board has a fault.
Impact
The services carried by the trunk on the standby board need to be transmitted to the active board
for processing through the CSconnection channel between the active and the standby board. If this
channel is faulty, the services carried by the trunk on the standby board are affected, for example,
caller and callee cannot be heard in voice calls and signaling links are disconnected.
Action
1. Check whether the following alarms are raised on the board:
199005796Clock of this board is abnormal
Yes -> Step 2.
No -> Step 3.
2. Handle the above alarms. Wait for ten minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
"Shelf number", "Slot number", and "CPU number" in the alarm information. After the board starts to
operate properly, wait for ten minutes, and check whether the alarm is still reported.
No -> End.
Yes -> Step 4.
4. Perform an active/standby switchover forcedly, and reset the standby board. After the board starts
to operate properly, wait for ten minutes, and check whether the alarm is raised on the standby board.
No -> End.
Yes -> Step 5.
5. Replace the standby board with an operational one(refer to Front Boards and Rear Boards
Replacement). After the standby board starts to operate properly, wait for ten minutes, and check
whether the alarm is still reported on the standby board.
No -> End.
Yes -> Step 6.
6. Perform an active/standby switchover forcedly, and replace the standby board with an operational
one(refer to Front Boards and Rear Boards Replacement). After the standby board starts to operate
properly, wait for ten minutes, and check whether the alarm is still reported on the standby board.
No -> End.
Yes -> Step 7.
3-433
SJ-20140527134643-015|2015-03-31 (R1.1)
3.3.8 199029952 802.3ah ethernet link fault event

Alarm Information
l
l
l
l

Name: 802.3ah ethernet link fault event
Alarm Description
This alarm is raised if the NE detects a link fault defined in Ethernet IEEE802.3ah standard on the
port of an interface board.
Alarm Cause
l
The IEEE_802.3ah negotiation fails.
The receiving link of the peer end is faulty (one-way communication).
Impact
Services carried on the port may be interrupted.
Action
1. Handle the fault accordingly in accordance with "Link fault type" in the alarm information.
"Link fault occurs in the receiving direction of the remote DTE." -> Step 2.
"Dying gasp event happened." -> Step 6.
"Critical event happened." -> Step 2.
Check whether a local end device is configured incorrectly or a physical link is faulty.
2. Run the QRY RPU INTERFACE command to check whether the related port is in "UP" status.
Yes -> Step 3.
No -> Step 5.
3. Run the QRY ETHOAM DISC command in accordance with "subsystem ID", "module ID", "unit
ID", "sub-unit ID", and "Port number" in the alarm information, and check whether "OAMPDU
Sending Period" of the port is consistent with the requirement.
Yes -> Step 6.
No -> End.
4. Query the "Ethernet Interface (EthernetTp)" object that uses the "Logical Ethernet Port
(LogicalEthPort)" object, and then query the "OAM Configuration (LinkOam)" that uses the
"Ethernet Interface (EthernetTp)" object. Modify the "OAMPDU Sending Period(Period)"
parameter as required. Wait for one minute, and check whether the alarm is cleared.
Yes -> End.
No -> Step 6.
5. Check the physical connection of the corresponding board port in accordance with the physical
address in the alarm information and the port information in "Port Quintuplet". Verify that the
3-434
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
optical fiber is not in good contact or the electrical port is fixed in place. Remove and install, or
replace the optical fiber or network cable. Wait for one minute, and then check whether the
alarm is cleared.
Yes -> End.
No -> Step 6.
Verify that the link fault is caused by the peer device.
related alarms.
Yes -> Step 7.
No -> Step 8.
Yes -> End.
No -> Step 8.
3.3.9 199030208 CFM fault

Alarm Information
l
l
l
l

Name: CFM fault
Alarm Description
This alarm is raised if the connection fault is detected because the IEEE802.1ag protocol is enabled
on a port of the NE.
3-435
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Cause
One of the following connection faults occurs between the local MEP and a peer MEP under the
same MD and MA:
l
A fault occurs in the receiving direction on the layer-2 Ethernet path of the peer MEP.
A connection fault occurs on the service layer between the local MEP and the peer MEP. The
local MEP receives an AIS (alarm indication signal) from the MA service layer.
A fault occurs in the receiving direction on the layer-2 Ethernet path of the local MEP.
The local MEP receives an incorrect CCM frame.
The local MEP receives a CCM frame that is transmitted incorrectly from other MD or MA.
The local MEP receives a lock signal transmitted from the service layer.
Impact
Services may be interrupted.
Action
1. Handle the fault in accordance with "Alarm type" in the alarm information.
"The remote RX fault indication is received." -> Step 10.
"Receive server layer alarm indication signal" -> Step 6.
"Lost continuity of remote MEP" -> Step 2.
"Receive incorrect CCM frame" -> Step 9.
"Receive a CCM frame from other MA or MD" -> Step 7.
"Receive server layer lock signal" -> Step 8.
Check whether the fault is caused by any local configuration error.
2. Check whether the local end is configured as required.
a. Query the "CFM Local MEP" object in accordance with the alarm object, and query the local
MEP parameters including "Used Ethernet Interface", "Switch of CCM Send", "Switch of CCM
receive", and "Mep Object ID".
b. Run the QRY ETHCFM MA command in accordance with "MD index" and "MA index" in the
alarm information to query "NAME", "PERIOD", and "VLAN ID".
Yes -> Step 4.
No -> Step 3.
3. Modify the local configuration as required, wait for one minute, and check whether the alarm
is cleared.
a. Modify the "Switch of CCM Send", "Switch of CCM receive", and "Mep Object ID" parameters
of the "CFM Local MEP" object as required in accordance with the alarm object.
b. Modify the "Vlan ID of Maintenance Association" and "Name of Maintenance Association" parameters of its parent object "CFM Maintenance Association" as required in accordance with
the alarm object.
Yes -> End.
No -> Step 4.
Check whether the alarm is caused by any physical fault on the local end.
3-436
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
4. Run the QRY RPU INTERFACE command to check whether the related port is in "UP" status.
Yes -> Step 6.
No -> Step 5.
5. Check the physical connection of the corresponding board port in accordance with "Port
Quintuplet" information queried in Step 2.1. Verify that the optical fiber has a good contact or the
electrical port is properly connected. Remove and install, or replace the optical fiber or network
cable. Wait for one minute, and then check whether the alarm is cleared.
Yes -> End.
No -> Step 7.
Contact the intermediate device manufacturer to troubleshoot the intermediate device.
6. Inform the manufacturer of the intermediate device between the local MEP and the remote MEP
to check the links between the service-layer MEP and the MA domain that borders on the MEP
that sends AIS signals in accordance with the local and remote MEP configurations queried in
Step 2.1. Check whether any link to the intermediate device is broken. Inform the intermediate
device manufacturer to troubleshoot the faulty link. Wait for a while, and check whether the
alarm is cleared.
Yes -> End.
No -> Step 7.
7. Inform MIP/MEP maintenance personnel to check whether the intermediate device is configured
as required. Ensure that the MD and MA are properly configured, and check whether the alarm
is cleared.
Yes -> End.
No -> Step 11.
8. Inform the manufacturer of the intermediate device between the local MEP and the remote MEP
to check whether a network locking operation is performed. Cancel the service-layer locking
operation in accordance with the local and remote MEP configurations queried in Step 2.1, and
Yes -> End.
No -> Step 11.
Contact the remote device manufacturer to troubleshoot the remote faults.
9. Inform the remote MEP device manufacturer to check whether the remote MEP is configured as
required in accordance with the local and remote MEP configurations queried in Step 2.1. Ensure
that the configurations on both ends are the same, and check whether the alarm is cleared.
Yes -> End.
No -> Step 11.
10. Inform the remote device manufacturer in accordance with "RMEP ID" in the alarm information to
troubleshoot receiving links. Check whether the alarm is cleared.
Yes -> End.
No -> Step 11.
3-437
SJ-20140527134643-015|2015-03-31 (R1.1)
3.3.10 199066003 Control plane communication abnormal between

board and its home module
Alarm Information
l
l
l
l

Name: Control plane communication abnormal between board and its home module
Alarm Description
This alarm is raised if the home module of the board detects that the communication between the
control plane of the board and the module is abnormal.
Alarm Cause
l
The board is offline.
The board fails to be powered on after reset.
The channel between the control plane of the board and its home module is abnormal, for
example, the switching board is removed.
Impact
The board is blocked, and all services running on the board are interrupted.
Action
1. Check whether the following alarm is raised on the faulty board:
199393987 Board offline
Yes -> Step 2.
No -> Step 3.
Yes -> End.
No -> Step 3.
3. Check whether the control-plane switching board in the shelf is operating properly through the
rack diagram (refer to Controller Rack).
Yes -> Step 5.
No -> Step 4.
Yes -> End.
No -> Step 5.
5. Check whether the following notification is raised after the alarm (determined in accordance
with the occurrence time)
199004419 Logic CPU is power on failed
3-438
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Yes -> Step 6.

No -> Step 7.
6. Handle the notification, and check whether the alarm is cleared.
Yes -> End.
No -> Step 7.
Yes -> End.
No -> Step 8.
3.3.11 199393986 Control plane communication is abnormal

between this board and the active independent board
Alarm Information
l
l
l
l

Name: Control plane communication is abnormal between this board and the active
independent board
Alarm Description
This alarm is raised if the active board detects that the communication between it and the standby
board is disconnected.
Alarm Cause
l
The communication link between the active and standby boards is abnormal.
Impact
Because the active and standby boards cannot communicate with each other, active/standby
switchover cannot be implemented if the active board is faulty. This alarm does not affect services,
but the system availability may be reduced.
3-439
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
with the occurrence time).
Yes -> Step 2.
No -> Step 3.
2. Clear the notification, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3. Press the EXCH key on the board to reset the board. Wait until the board is powered on (the
HOST indicator is flashing in green slowly at 1 Hz). Check whether the alarm is cleared.
Yes -> End.
No -> End.
3.3.12 199393988 Control plane communication abnormal between

module and OMP
Alarm Information
l
l
l
l

Name: Control plane communication abnormal between module and OMP
Alarm Description
This alarm is raised if the OMP detects that the communication between it and any other control
plane of other modules is abnormal.
Alarm Cause
l
The channel between the control plane of the board and the OMP is abnormal, for example, the
switching board is removed.
Impact
The board is blocked and the corresponding functions are unavailable, so all services of the board
are unavailable.
3-440
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Action
199393987 Board offline
Yes -> Step 2.
No -> Step 3.
Yes -> End.
No -> Step 3.
3. Check whether the control-plane switching board in the shelf is operating properly through the
rack diagram (refer to Controller Rack).
Yes -> Step 5.
No -> Step 4.
Yes -> End.
No -> Step 5.
with the occurrence time).
Yes -> Step 6.
No -> Step 7.
6. Handle the notification, and check whether the alarm is cleared.
Yes -> End.
No -> Step 7.
Yes -> End.
No -> Step 8.
3.3.13 199066008 MTP2 link sending is overloaded

Alarm Information
Alarm code:
199066008
Name:
MTP2 link sending is overloaded
Alarm severity:
Major
Alarm type:
3-441
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Description
This alarm is raised if the transmission load of the MTP2 link exceeds the threshold. The threshold for
a 64 kbps link is 8 Erl, and that for a 2 Mbps link is 6 Erl.
Alarm Cause
l
The load of the links in the MTP2 link group is not balanced.
Traffic carried on the MTP2 link is heavy.
Impact
This alarm may result in MTP2 link congestion, packet loss, and even a broken link. The services
carried on the link are interrupted.
Action
Yes -> End.
No -> Step 2.
2. Query the R_N7LINK table in accordance with the "Link number" in the alarm information to
obtain the belonging "Link set ID (LinkSet)". Run the QRY MTP3LINKSETSTATUS command
in accordance with the "Link set ID" in the alarm information, and check whether other MTP2
links in the link group are in normal status.
Yes -> Step 5.
No -> Step 3.
3. Check whether unavailable links have the following alarm:
Yes -> Step 4.
No -> Step 5.
Yes -> End.
No -> Step 5.
5. Contact the planning personnel for new MTP2 links or contact the next level of maintenance
support.
3.3.14 199066009 MTP2 link reception is overloaded

Alarm Information
Alarm code:
199066009
Name:
MTP2 link reception is overloaded
Alarm severity:
Major
3-442
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm type:
Alarm Description
This alarm is raised if the receiving load of the MTP2 link exceeds the threshold. The threshold for a
64 kbps link is 8 Erl, and that for a 2 Mbps link is 6 Erl.
Alarm Cause
l
The load of the links in the MTP2 link group is not balanced.
Traffic carried on the MTP2 link is heavy.
Impact
This alarm may result in MTP2 link congestion, packet loss, and even a broken link. The services
carried on the link are interrupted.
Action
Yes -> End.
No -> Step 2.
2. Query the R_N7LINK table in accordance with the "Link number" in the alarm information to
obtain the belonging "Link set ID (LinkSet)". Run the QRY MTP3LINKSETSTATUS command
in accordance with the "Link set ID" in the alarm information, and check whether other MTP2
links in the link group are in normal status.
Yes -> Step 5.
No -> Step 3.
3. Check whether unavailable links have the following alarm:
Yes -> Step 4.
No -> Step 5.
Yes -> End.
No -> Step 5.
5. Contact the planning personnel for new MTP2 links or contact the next level of maintenance
support.
3.3.15 199066010 MTP3 office inaccessible

Alarm Information
l
l
l

Name: MTP3 office inaccessible
3-443
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Description
This alarm is raised if the MTP3 office is inaccessible.
Alarm Cause
l
The office routing is not configured.
All MTP links among offices are faulty.
The destination office that receives the signaling transfer point notification is inaccessible.
Impact
l
The upper level service cannot send or receive messages from a specific office.
New services cannot access an office.
A service of the office is released abnormally.
Action
1. Check whether the "Mtp3 RouteSet (Mtp3RouteSet)" object that uses the "Adjacent Office
Information (RemoteSp)" object is configured with an MTP3 route in accordance with the alarm
object.
Yes -> Step 3.
No -> Step 2.
2. Add an MTP3 route for the "Mtp3 RouteSet (Mtp3RouteSet)" object, wait for three minutes, and
Yes -> End.
No -> Step 3.
3. Check whether the "Mtp3 RouteSet (Mtp3RouteSet)" object that uses the "Adjacent Office
Information (RemoteSp)" object in accordance with the first configured MTP3 route for the "Mtp3
RouteSet (Mtp3RouteSet)" object.
Yes -> Step 5.
No -> Step 4.
4. Configure the first MTP3 route for the "Mtp3 RouteSet (Mtp3RouteSet)" object, wait for three
Yes -> End.
No -> Step 5.
5. Check whether the links 1 through 16 in the R_N7ROUTE configuration has the following alarms:
Yes -> Step 6.
No -> Step 7.
Yes -> End.
No -> Step 7.
3-444
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
7. Repeat steps 3 through 6 to check whether the alarm is cleared in accordance with routes 2
through 4.
Yes -> End.
No -> Step 8.
8. Query the "Adjacent Office Information (RemoteSp)" object in accordance with the alarm
object. Check whether the "Connection relationship with local signaling point" parameter is
set to "Associated".
Yes -> Step 10.
No -> Step 9.
9. Contact the maintenance personnel of the peer device to transfer the signaling to the destination
office, and then check whether the alarm is cleared.
Yes -> End.
No -> Step 10.
3.3.16 199066011 MTP3 link unavailable

Alarm Information
l
l
l
l

Name: MTP3 link unavailable
Alarm Description
This alarm is raised if the signaling processing module of the NE detects that the MTP3 link is
unavailable.
Alarm Cause
l
The local MTP3 link is deactivated or the management is interrupted.
The configuration is not correct.
The bottom layer link is faulty, for example, the MTP2 link is faulty.
The peer end is faulty, for example, the peer link is deactivated.
The hardware of the local port is faulty.
Impact
l
Multiple MTP3 links to the same office operate in load sharing mode. If some MTP3 links to one
office are faulty, the load of MTP3 links in operating status is increased.
If all MTP3 links to the same office are faulty, signaling services to this office cannot be
transferred properly.
Action
3-445
SJ-20140527134643-015|2015-03-31 (R1.1)
Yes -> End.
No -> Step 2.
2. Check whether the "Reason for exiting service" parameter is set to "Link is deactivated by OMC".
Yes -> Step 3.
No -> Step 4.
3. Run the SET MTP3LINK ACTIVE command in accordance with the "Link number" in the alarm
information to activate the link, wait for two minutes, and then check whether the alarm is cleared.
Yes -> End.
No -> Step 4.
4. Check whether the "Signalling link code " (Slc) in the alarm information is consistent with that
of the peer end.
Yes -> Step 6.
No -> Step 5.
5. Modify the "Signalling link" configuration on the local end in accordance with the alarm object,
or contact the peer end to modify the corresponding configuration, ensure that the "Signalling
link code (Slc)" parameter is consistently configured on both ends. Wait for two minutes, and
Yes -> End.
No -> Step 6.
6. Query its Parent DN "Adjacent Office Information (RemoteSp)" in accordance with the alarm
object, and check whether the configuration of the "Destination point code (Dpc)" parameter is
the same as that of the "Signalling Point Code" parameter of the peer end.
Yes -> Step 8.
No -> Step 7.
7. Modify the parent DN "Adjacent Office Information (RemoteSp)" on the local end, or contact
the peer end to modify the corresponding configuration, ensure that the configuration of the
"Destination point code (Dpc)" parameter of the local end is the same as that of the "Signalling
Point Code" parameter of the peer end. Wait for two minutes, and check whether the alarm
is cleared.
Yes -> End.
No -> Step 8.
8. Query the parent DN "Used signalling linkset (Sls)" in accordance with the alarm object, and
check whether the "Physical link type (PhyLinkType)" parameter is set to "TDM Signaling link".
Yes -> Step 9.
No -> Step 11.
9. Query the "Mtp2 Link (Mtp2Link)" object associated to the "Signalling link code (Slc)" object in
accordance with the alarm object, and then query the "Logical E1 (LogicalE1)" object associated
by the "Mtp2 Link (Mtp2Link)" object. [A1013]Obtain the trunk in accordance with the "Logical E1
(LogicalE1)" object, check whether the trunk has the following alarms:
3-446
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Yes -> Step 10.

No -> Step 17.
Yes -> End.
No -> Step 17.
11. Check whether the "Physical link type (PhyLinkType)" parameter of the parent DN "Used
signalling linkset (Sls)" is set to "TDM SIGNALLING LINK".
Yes -> Step 12.
No -> Step 14.
12. Query the "NNI Link (NniSaalTp)" object associated to the "Signalling link code (Slc)" object
in accordance with the alarm object, and then query the "Termination PVC (PvcTp)" object
associated by the "NNI Link (NniSaalTp)" object. Obtain the "PVC No. (PvcSeq)" parameter
to check whether the following alarm exists:
199018944 The state of PVC link is faulty
Yes -> Step 13.
No -> Step 17.
13. Handle the PVC alarm, and check whether the alarm is cleared.
Yes -> End.
No -> Step 17.
14. Check whether the "Physical link type (PhyLinkType)" parameter of the parent DN "Used
signalling linkset (Sls)" is set to "IP signaling bearer".
Yes -> Step 15.
No -> Step 18.
15. Query the association in accordance with the "Link number" in the alarm information, and check
whether the following alarm exists on the association:
199066019 Association broken
Yes -> Step 16.
No -> Step 17.
16. Handle the association alarm, and check whether the alarm is cleared.
Yes -> End.
No -> Step 17.
17. Contact the maintenance personnel of the peer end to resolve the fault, and then check whether
Yes -> End.
No -> Step 18.
3.3.17 199066014 M3UA office inaccessible

Alarm Information
l
l

Name: M3UA office inaccessible
3-447
SJ-20140527134643-015|2015-03-31 (R1.1)
l
l

Alarm Description
This alarm is raised if the board detects that the M3UA office is inaccessible.
Alarm Cause
l
The association is disconnected or the AS does not enter service status.
The destination signaling point that receives the signaling transfer point notification is
inaccessible.
Impact
l
The upper level service cannot send or receive messages from a specific office.
New services cannot access an office.
A service of the office is released abnormally.
Action
1. Check whether the "M3ua RouteSet (M3uaRouteSet)" object that uses the "Adjacent Office
Information (RemoteSp)" object is configured in accordance with the alarm object.
Yes -> Step 3.
No -> Step 2.
2. Add the "M3ua RouteSet (M3uaRouteSet)" object. Wait for three minutes, and check whether
Yes -> End.
No -> Step 3.
3. Query the "AS Configuration (M3uaAs)" object associated with the "M3ua Route (M3uaRoute)"
object, and query the "Association (SctpAssociation)" object associated with the "AS
Configuration (M3uaAs)" object in accordance with the "M3ua RouteSet (M3uaRouteSet)" object
in Step 1 or 2. Check whether the following alarm is raised on the association:
Yes -> Step 4.
No -> Step 5.
Yes -> End.
No -> Step 5.
5. Query the "M3ua Route(M3uaRoute)" object associated with the "M3ua RouteSet(M3uaRouteSet)"
object in Step 1 or 2, and query the "AS Configuration(M3uaAs)" object associated with the
"M3ua Route(M3uaRoute)" object. Run the QRY ASSTATUS command to query the AS status
in accordance with the "AS Number(AsId)" parameter. Check whether the AS serving for the
office is activated.
Yes -> Step 6.
No -> Step 8.
3-448
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
6. Query the "Adjacent Office Information (RemoteSp)" object in accordance with the alarm
object. Check whether the "Connection relationship with local signalling point" parameter is
set to "Associated".
Yes -> Step 13.
No -> Step 7.
7. Contact the maintenance personnel of the peer device to check the connection between the
adjacent SP and destination SP. Ensure that the destination SP is reachable from the point of the
adjacent SP, and check whether the alarm is cleared.
Yes -> End.
No -> Step 13.
8. Obtain the setting of the "Association ID(AssociationSeq)" parameter and module number in the
alarm information in accordance with the "Association(SctpAssociation)" object in Step 3. Run
the QRY SCTP BY ASSOCIATION command to query the association status (activated or not).
Yes -> Step 9.
No -> Step 10.
9. Query the "M3ua Route (M3uaRoute)" object associated with the "M3ua RouteSet
(M3uaRouteSet)" object in Step 1 or 2, query the "AS Configuration (M3uaAs)" object associated
with the "M3ua Route (M3uaRoute)" object, and query the "ASP Configuration (M3uaAsp)" object
associated with the "AS Configuration (M3uaAs)" object. Check whether the "ASP Configuration
(M3uaAs)" object configuration is the same as that in the peer end office.
Yes -> Step 13.
No -> Step 11.
10. Run the SET SCTP SHUTDOWN command to block the association in accordance with the
association ID, and run the SET SCTP ESTABLISH command to unblock the association to
check whether the association is activated.
Yes -> Step 12.
No -> Step 13.
11. Query the "M3ua Route (M3uaRoute)" object associated with the "M3ua RouteSet
(M3uaRouteSet)" object in Step 1 or 2, query the "AS Configuration (M3uaAs)" object associated
with the "M3ua Route (M3uaRoute)" object, and query the "ASP Configuration (M3uaAsp)"
object associated with the "AS Configuration (M3uaAs)" object. Modify the "ASP Configuration
(M3uaAsp)" object locally or contact the maintenance personnel of the peer device to modify the
object (ensure that the "ASP Configuration (M3uaAsp)" object in the local end and peer end are
the same). Wait for three minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 13.
Yes -> End.
No -> Step 13.
3-449
SJ-20140527134643-015|2015-03-31 (R1.1)
3.3.18 199066019 Association broken

Alarm Information
l
l
l
l

Name: Association broken
Alarm Description
This alarm is raised if the association is disconnected.
Alarm Cause
l
The association is released manually.
The association channels on both ends are faulty.
The association configurations on the local end and the peer end are not consistent.
Impact
If the association is disconnected, and upper-layer services of the association may be affected
(signaling link). For example, the signaling office is inaccessible, or the load on other available
associations is increased.
Action
1. Check the parameters of the "Association (SctpAssociation)" object, including "peer end IP
address 1 (RemoteIp1Addr)", "peer end IP address 2 (RemoteIp2Addr)", "peer end IP address 3
(RemoteIp3Addr)", "peer end IP address 4 (RemoteIp4Addr)", and "Remote Port (RemotePort)"
meet the actual requirements in accordance with the alarm object.
Yes -> Step 3.
No -> Step 2.
2. Modify the association configuration as required, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3. Contact the maintenance personnel of the peer device to check whether the related configuration
of the peer end is the same with the real requirement.
Yes -> Step 5.
No -> Step 4.
4. After the peer maintenance personnel modifies the configuration as required, check whether
Yes -> End.
No -> Step 5.
5. Run the QRY RPU ROUTE command in accordance with the "Association peer IP Address" in
the alarm information to check whether the corresponding route configuration is configured as
required.
3-450
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Yes -> Step 7.

No -> Step 6.
6. Modify the "Static Route Object ID(IPV4) (StaticRoute)" object as required to ensure that the
associated peer IP address and the static route object ID are in the same network segment,
Yes -> End.
No -> Step 7.
7. Check whether the "ucReason" parameter in the alarm information is "Establishment timer timed
out".
Yes -> Step 10.
No -> Step 8.
8. Check whether the "ucReason" parameter in the alarm information is "All paths are inactive".
Yes -> Step 10.
No -> Step 9.
9. Check whether the "ucReason" parameter in the alarm information is "Abort request from remote
peer received and Shutdown completeness received".
Yes -> Step 13.
No -> Step 15.
10. Run the QRY RPU ROUTE command to query routing configuration in accordance with the
"Association peer IP Address" in the alarm information, determine logical information (Port
Quintuplet) and physical information (rack-shelf-slot) of the corresponding egress interface
board. Determine logical information and physical information of the ingress interface board in
accordance with the "Association local IP Address" in the alarm and actual routing requirements
of the peer end, and check whether the board and related ingress and egress interface boards
have any of the following alarms:
199005397 Communication of RAW MAC channel is abnormal
199411392 BFD session interruption
199407043 PPP link is down
Yes -> Step 11.
No -> Step 12.
Yes -> End.
No -> Step 12.
12. Ping 1200 packets in accordance with "Association peer IP Address" in the alarm information,
and check whether packet loss occurs.
Yes -> Step 13.
No -> Step 15.
Yes -> Step 14.
No -> Step 15.
Yes -> End.
3-451
SJ-20140527134643-015|2015-03-31 (R1.1)
No -> Step 10.

3.3.19 199406528 The protocol state of port-channel interface is

down
Alarm Information
Code:
199406528
Name:
The protocol state of port-channel interface is down
Severity:
Minor
Type:
Alarm Description
This alarm is raised if the initialization negotiation of the aggregation port fails, or the status changes
from UP to DOWN.
Probable Cause
l
The aggregation port configurations on both ends are not consistent.
The channel of the aggregation port is abnormal.
System Impact
Services carried on the aggregation port may be interrupted.
Handling Suggestion
1. Run the QRY LACP COUNTERS command in accordance with "channel-group number" in the
alarm information to check whether the aggregation port configuration is the same with the
Yes -> Step 3.
No -> Step 2.
2. Modify the "Bounding mode of member port (BoundMode)" parameter of the "Ethernet Channel
Sub Interface Object ID (EthChannel)" object in accordance with the alarm object, or add/delete
the "Channel Member Port Object ID(EthChMember)" object. Wait for one minute, and check
Yes -> End.
No -> Step 3.
3. Check whether the following alarm exists in the "Ethernet Port Object ID (EthernetPort)" of
"Logical Ethernet Port (LogicalEthPort)" of "Ethernet Interface (EthernetTp)" used by the "Ethernet
Channel Member Port (EthChMember)" object.
3-452
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms

Yes -> Step 4.
No -> Step 5.
Yes -> End.
No -> Step 5.
related alarms.
Yes -> Step 6.
No -> Step 7.
Yes -> End.
No -> Step 7.
3.3.20 199406529 The protocol state of SUPERVLAN interface is

down
Alarm Information
Code:
199406529
Name:
The protocol state of SUPERVLAN interface is down
Severity:
Minor
Type:
Alarm Description
This alarm is raised if the SuperVLAN port does not change to UP status from the initialization status
within 30 seconds, or the status of the SuperVLAN port changes from UP to DOWN.
Probable Cause
l
The SUPERVLAN configuration is wrong.
The physical port to which the member port of SUPERVLAN belongs is faulty.
System Impact
Services carried on the SUPERVLAN interface are interrupted.
3-453
SJ-20140527134643-015|2015-03-31 (R1.1)
Handling Suggestion
1. Run the QRY SUPERVLAN MEMBER command to query the SUPERVLAN member interface
information based on "supervlan number" in the alarm information, and check whether "supervlan
number" is the same with actual one.
Yes -> Step 3.
No -> Step 2.
2. Query the "Super Vlan Interface (SuperVlan)" object based on the alarm objects. Add the "Super
Vlan Member Port (SubVlan)" child object, or delete the "Super Vlan Interface (SuperVlan)"
Yes -> End.
No -> Step 3.
3. Check whether the following alarm exists in the "Ethernet Port Object ID (EthernetPort)" of
"Logical Ethernet Port (LogicalEthPort)" of "Ethernet Interface (EthernetTp)" parent object
used by the "Ethernet Vlan Sub Interface(EthernetVlanTp)" object of the "Super Vlan Member
(SubVlan)" child object.
Yes -> Step 4.
No -> Step 5.
Yes -> End.
No -> Step 5.
3.3.21 199406530 The protocol state of tunnel port is down

Alarm Information
Code:
199406530
Name:
The protocol state of tunnel port is down
Severity:
Minor
Type:
Alarm Description
This alarm is raised if the status of the tunnel port changes from UP to DOWN.
Probable Cause
l
The route to the destination address of the channel is unavailable.
The tunnel is nested incorrectly.
The GRE tunnel has more than three layers nested.
3-454
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
System Impact
The tunnel cannot carry upper layer services.
Handling Suggestion
1. Query the "Tunnel Mode", "IPV4 Destination IP Address", and "IPV6 Destination IP Address"
parameters of the "Tunnel Interface" object in accordance with "Tunnel ID" in the alarm
information, and check "Alarm cause" in the alarm information.
"No route to reach the tunnel destination." -> Step 2.
"The tunnel is nested wrong" or "GRE tunnel is nested over 3 layers" -> Step 13.
"The tunnel is set down while modifying" -> Step 14.
2. Check whether the "Tunnel Mode" parameter of the "Tunnel Interface" object is GRE, V6inV4
or V6toV4.
Yes -> Step 3.
No -> Step 8.
3. Query the "Static Route(IPV4)" object and check whether there is a route to the "IPV4 Destination
IP Address".
Yes -> Step 4.
No -> Step 5.
4. Obtain the port number in accordance with the "Tunnel Interface" object, and check whether
the "Priority" filed is 1.
Yes -> Step 6.
No -> Step 15.
5. Add a "Static Route(IPV4)" object as required, and check whether the alarm is cleared.
Yes -> End.
No -> Step 15.
6. Check whether the port queried in Step 3 has any of the following alarms:
199406528 The protocol state of port-channel interface is down
199406529 The protocol state of SUPERVLAN interface is down
Yes -> Step 7.
No -> Step 15.
Yes -> End.
No -> Step 15.
8. Query the "Static Route(IPV6)" object and check whether there is a route to the "IPV6 Destination
IP Address".
Yes -> Step 9.
No -> Step 10.
9. Obtain the port number in accordance with the "Tunnel Interface" object, and check whether
the "Priority" filed is 1.
Yes -> Step 11.
No -> Step 15.
10. Add a "Static Route(IPV4)" object as required, and check whether the alarm is cleared.
Yes -> End.
3-455
SJ-20140527134643-015|2015-03-31 (R1.1)
No -> Step 15.

11. Check whether the port queried in Step 8 has any of the following alarms:
199406528 The protocol state of port-channel interface is down
199406529 The protocol state of SUPERVLAN interface is down
Yes -> Step 12.
No -> Step 15.
Yes -> End.
No -> Step 15.
13. Add a "Static Route(IPV4)" object as required, wait for three minutes, and check whether the
alarm is cleared.
Yes -> End.
No -> Step 15.
Yes -> End.
No -> Step 15.
3.3.22 199407043 PPP link is down

Alarm Information
l
l
l
l

Name: PPP link is down
Alarm Description
This alarm is generated when the PPP link is broken.
Alarm Cause
l
The HDLC link fails to be created.
The physical link is disconnected or the link transmission quality is poor.
The active board is powered on or a standby board switches over to an active board successfully.
PPP port configurations on both ends of a link are different.
The parameters of the PPP port are modified.
3-456
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Impact
l
If multiple PPP links are configured for service data transmission, the load on other links may be
increased.
If only one PPP link is configured, related services may be interrupted.
Action
1. Check whether the following alarm exists in accordance with "Rack number", "Shelf number",
"Slot number" in the alarm information:
199018501 Fail to create the HDLC channel
Yes -> Step 2.
No -> Step 3.
2. Resolve the faults in accordance with the suggestions of this notification, wait for one minute,
Yes -> End.
No -> Step 3.
3. Query "Logical E1 (LogicalE1)" or "Logical T1 (LogicalT1)" used by the "PPP Link of ML-PPP
Group (MpLink)" or "PPP Link (PppTp)" object. [A1011]Query the trunk ID of the corresponding
port, "Begin Time Slot (BeginSlot)", and "End Time Slot (EndSlot)", and check whether these
parameters are the same as those on the peer end.
Yes -> Step 4.
No -> Step 9.
4. Check whether the local configuration is incorrect as required.
Yes -> Step 5.
No -> Step 6.
5. Modify the local configuration as required, wait for one minute, and check whether the alarm
is cleared.
Yes -> End.
No -> Step 6.
6. Contact the maintenance personnel of the peer device to check whether the peer configuration
is correct.
Yes -> Step 8.
No -> Step 7.
7. Contact the maintenance personnel of the peer device to modify the configuration, and then
Yes -> End.
No -> Step 8.
8. Check whether the E1 range meet the actual requirements.
Yes -> Step 10.
No -> Step 9.
9. Query "PPP Link of ML-PPP Group (MpLink)" or "PPP Link (PppTp)" in accordance with the alarm
object. [A1011]Check the trunk ID of the corresponding port to see whether the trunk ID on the
local end and peer end is the same. Wait for one minute, and check whether the alarm is cleared.
Yes -> End.
No -> Step 10.
3-457
SJ-20140527134643-015|2015-03-31 (R1.1)
10. Modify the local configuration based on actual requirements, and check whether the cable
connected to the local device is loose.
Yes -> Step 11.
No -> Step 12.
11. Remove and install the cable again, wait for one minute, and check whether the alarm is cleared.
Yes -> End.
No -> Step 12.
12. Check whether the appearance of the local cable is damaged.
Yes -> Step 13.
No -> Step 14.
13. Replace another cable of the same type, wait for one minute, and check whether the alarm
is cleared.
Yes -> End.
No -> Step 14.
14. Check whether the connection order of the cable meets the actual requirements.
Yes -> Step 16.
No -> Step 15.
15. Adjust the connection order of the cable as required, wait for one minute, and check whether
Yes -> End.
No -> Step 16.
Yes -> Step 17.
No -> Step 18.
Yes -> End.
No -> Step 18.
3.3.23 199411392 BFD session interruption

Alarm Information
l
l
l
l

Name: BFD session interruption
Alarm Description
This alarm is raised if the BFD session is interrupted because the status of the session changes
from UP to DOWN.
3-458
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
l
The BFD session configurations on both ends are inconsistent.
The channel of the BFD session is abnormal.
Impact
The BFD is used to detect the accessibility and the quality of the link between the NE and the peer
device. When the BFD is interrupted, it means that the link to the peer end is interrupted. If there is
no backup path, services may be interrupted.
Action
1. Search for the "Statistics of BFD protocol performance measurement" of the "BFD Session"
object, and query the number of BFD sessions received by the counter "C380680002 Number of
BFD packets received", and whether the counter value is larger than 0.
Yes -> Step 7.
No -> Step 2.
2. Set the source address of the BFD session to the source address of the PING command, specify
the destination address of the BFD session to the destination address of the PING command,
and then check whether you can successfully run the PING command.
Yes -> Step 5.
No -> Step 3.
3. [A1014]Query the IP port in accordance with Bfdsession, and check whether the following alarm
exists:
Yes -> Step 4.
No -> Step 12.
Yes -> End.
No -> Step 12.
5. Contact the maintenance personnel of the peer device to check whether BFD session exists.
Yes -> Step 12.
No -> Step 6.
6. Contact the maintenance personnel of the peer device to add a BFD session, and check whether
Yes -> End.
No -> Step 12.
object, and query the number of BFD sessions failed to be authenticated and received by the
counter "C380680005 Number of BFD packets received with invalid authentication key", and
whether the counter value is larger than 0.
Yes -> Step 8.
No -> Step 12.
8. Query "Authorization Type (AuthType)", "Authorization Key Id (AuthKeyId)", "Authorization Key
Type (AuthKeyType)", and "Authorization Key (AuthKey)" of the "BFD Authorization (BfdAuth)"
3-459
SJ-20140527134643-015|2015-03-31 (R1.1)
used by "BFD IPv4 Session (BfdSession)" object, and ensure that the configurations on both
ends are the same.
Yes -> Step 12.
No -> Step 9.
9. Check whether the session configuration needs to be modified as required.
Yes -> Step 10.
No -> Step 11.
10. Re-configure "Authorization Type (AuthType)", "Authorization Key Id (AuthKeyId)", "Authorization
Key Type (AuthKeyType)", and "Authorization Key (AuthKey)" of the "BFD Authorization
(BfdAuth)" used by "BFD IPv4 Session (BfdSession)" object, and ensure that the configurations
on both ends are the same, and check whether the alarm is cleared.
Yes -> End.
No -> Step 12.
11. Contact the maintenance personnel of the peer device to modify the BFD session, and check
Yes -> End.
No -> Step 12.
3.3.24 199411393 BFD session negotiation failure

Alarm Information
l
l
l
l

Name: BFD session negotiation failure
Alarm Description
This alarm is raised if the status of the BFD session fails to change to the UP status and the initial
negotiation of the session fails.
Alarm Cause
l
The BFD session configurations on both ends are inconsistent.
The channel of the BFD session is abnormal.
Impact
The BFD is used to detect the accessibility and the quality of the link between the NE and the peer
device. When the BFD negotiation fails, it means that the link to the peer end is interrupted. If there is
Action
3-460
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
object, and query the number of BFD sessions received by the counter "C380680002 Number of
BFD packets received", and whether the counter value is larger than 0.
Yes -> Step 7.
No -> Step 2.
2. Set the source address of the BFD session to the source address of the PING command, specify
the destination address of the BFD session to the destination address of the PING command,
and then check whether you can successfully run the PING command.
Yes -> Step 5.
No -> Step 3.
3. [A1014]Query the IP port in accordance with Bfdsession, and check whether the following alarm
exists:
Yes -> Step 4.
No -> Step 12.
Yes -> End.
No -> Step 12.
5. Contact the maintenance personnel of the peer device to check whether BFD session exists.
Yes -> Step 12.
No -> Step 6.
6. Contact the maintenance personnel of the peer device to add a BFD session, and check whether
Yes -> End.
No -> Step 12.
object, and query the number of BFD sessions failed to be authenticated and received by the
counter "C380680005 Number of BFD packets received with invalid authentication key", and
whether the counter value is larger than 0.
Yes -> Step 8.
No -> Step 12.
8. Query "Authorization Type (AuthType)", "Authorization Key Id (AuthKeyId)", "Authorization Key
Type (AuthKeyType)", and "Authorization Key (AuthKey)" of the "BFD Authorization (BfdAuth)"
used by "BFD IPv4 Session (BfdSession)" object, and ensure that the configurations on both
ends are the same.
Yes -> Step 12.
No -> Step 9.
9. Check whether the session configuration needs to be modified as required.
Yes -> Step 10.
No -> Step 11.
10. Re-configure "Authorization Type (AuthType)", "Authorization Key Id (AuthKeyId)", "Authorization
Key Type (AuthKeyType)", and "Authorization Key (AuthKey)" of the "BFD Authorization
(BfdAuth)" used by "BFD IPv4 Session (BfdSession)" object, and ensure that the configurations
on both ends are the same, and check whether the alarm is cleared.
3-461
SJ-20140527134643-015|2015-03-31 (R1.1)
Yes -> End.

No -> Step 12.
11. Contact the maintenance personnel of the peer device to modify the BFD session, and check
Yes -> End.
No -> Step 12.
3.3.25 199066026 Association path broken

Alarm Information
l
l
l
l

Name: Association path broken
Alarm Description
This alarm is raised if the association is disconnected.
Alarm Cause
l
The hardware of the board is faulty.
The SCTP channels on both ends are faulty.
The configurations of both ends are inconsistent.
Impact
This channel is unavailable, but services are not affected.
Action
1. Run the QRY RPU ROUTE command in accordance with the "Association peer IP Address" in
the alarm information to check whether the corresponding route configuration is configured as
required.
Yes -> Step 3.
No -> Step 2.
2. Modify the "Static Route (IPV4)" object as required to ensure that the associated peer IP address
and the static route object ID are in the same destination network segment, and then check
Yes -> Step 5.
No -> End.
of the peer end is the same with the actual requirement.
3-462
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Yes -> Step 4.

No -> Step 5.
4. After the peer maintenance personnel modifies the configuration as required, check whether
Yes -> End.
No -> Step 5.
"Association peer IP Address" in the alarm information, determine logical information (Port
Quintuplet) and physical information (rack-shelf-slot) of the corresponding egress interface
board. Determine logical information and physical information of the ingress interface board in
accordance with the "Association local IP Address" in the alarm and actual routing requirements
of the peer end, and check whether the board and related ingress and egress interface boards
have any of the following alarms:
Yes -> Step 6.
No -> Step 7.
Yes -> End.
No -> Step 7.
7. Ping 1200 packets in accordance with "Association peer IP Address" in the alarm information,
and check whether packet loss occurs.
Yes -> Step 8.
No -> Step 10.
Yes -> Step 9.
No -> Step 10.
Yes -> End.
No -> Step 10.
3.3.26 199420352 IPD session interruption

Alarm Information
l
l
l
l

Name: IPD session interruption
3-463
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Description
This alarm is raised if the status of the IPD session is changed from UP to DOWN and the session is
interrupted.
Alarm Cause
l
The IPD configuration is incorrect.
The channel of the IPD session is abnormal.
Impact
The IPD is used to detect the accessibility and the quality of the link between the NE and the peer
device. When the IPD is interrupted, it means that the link to the peer end is interrupted. If there is
Action
1. Search for the measurement type "Statistics of IPS protocol performance measurement" of the
object type "IPD Session", and query the counter "C380690002 Number of IPD packets received"
of the performance object corresponding to the alarm object. Check whether the counter value
is larger than 0.
Yes -> Step 5.
No -> Step 2.
2. Run the PING command, set the source address of the IPD session to the source address of the
PING command, specify the destination address of the IPD session to the destination address of
the PING command, and then check whether you can successfully run the PING command.
Yes -> Step 7.
No -> Step 3.
3. Run the QRY RPU INTERFACE command, find the interface corresponding to the source
address of the IPD session, search for the physical address of the interface board in accordance
with the "Subsystem ID", "Module number", "Unit number", and "Subunit number" of the logical
address, and then check whether the following alarm exists:
Yes -> Step 4.
No -> Step 7.
Yes -> End.
No -> Step 7.
5. Query the "IPD Session(IpdSession)" object in accordance with the "Source IP Address" and
"Destination IP Address" parameters in the alarm information, and check the "The sending
interval (TxInterval)" and "The detection time (DetectTime)" parameters. Check whether "The
detection time (DetectTime)" is at least three times longer than "The sending interval (TxInterval)".
Yes -> Step 7.
No -> Step 6.
3-464
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
6. Modify the "The sending interval (TxInterval)" and "The detection time (DetectTime)" parameters,
and ensure that "The detection time (DetectTime)" is at least three times longer than "The
sending interval (TxInterval)". Check whether the alarm is cleared.
Yes -> End.
No -> Step 7.
3.3.27 199007426 Switch chip buffer overflow

Alarm Information
Alarm code:
199007426
Name:
Switch chip buffer overflow
Alarm severity:
Minor
Alarm type:
Alarm Description
This alarm is raised if the board detects that the cache of the switching chip overflows.
Alarm Cause
The traffic on the board is heavy.
Impact
Packets may be lost and services are affected.
Action
Yes -> End.
No -> Step 2.
3-465
SJ-20140527134643-015|2015-03-31 (R1.1)
3.3.28 199105035 The communication link between LogService

board and OMP is broken
Alarm Information
Alarm code:
199105035
Name:
The communication link between LogService board and OMP is broken
Alarm severity:
Minor
Alarm type:
Alarm Description
The OMP detects an interruption of the link with the log server board.
Alarm Cause
l
The log server board is not present.
The software of the log server is not operating properly.
The hardware of the log server board is faulty.
Impact
The OMM fails to obtain the signaling tracing data, and the NDS server fails to obtain the network
optimization data.
Action
1. Check whether the log server board is present.
Yes -> Step 3.
No -> Step 2.
2. Install the log server board into the corresponding slot. Wait for 10 minutes, and check whether
Yes -> End.
No -> Step 3.
3.3.29 199105041 ECMM/EGBS/EGFS Board Offline

Alarm Information
Alarm code:
199105041
3-466
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Name:
ECMM/EGBS/EGFS Board Offline
Alarm severity:
Major
Alarm type:
Alarm Description
The OMM detects that the ECMM/EGBS/EGFS board is offline.
Alarm Cause
The link between the ECMM/EGBS/EGFS board and OMM server is broken.
Impact
The link between the ECMM/EGBS/EGFS board and OMM server is broken, and the OMM fails
to obtain the performance alarm data of NEs.
Action
1. Open the rack diagram in the Status Management window, and check whether the board in the
corresponding shelf is operating properly in accordance with "Rack number", "Shelf number", and
"Board type" in the alarm information.
Yes -> Step 11.
No -> Step 2.
2. Check whether the type of the board where the alarm arises is EGBS.
Yes -> Step 3.
No -> Step 4.
3. Check whether the shelf where the board is located is the master shelf (the OMM board is also
located in the master shelf).
Yes -> Step 8.
No -> Step 6.
4. Check whether the following alarm arises on the EGBS board that is on the same shelf as the
board where the alarm arises:
199105041 ECMM/EGBS/EGFS Board Offline
Yes -> Step 5.
No -> Step 8.
5. Handle the related alarm, and check whether the alarm is cleared.
Yes -> End.
No -> Step 8.
6. Open the rack diagram in the Alarm Management window, and check whether the following alarm
arises on the EGBS board in the master shelf (the OMM board is also located in the master shelf):
199105041 ECMM/EGBS/EGFS Board Offline
Yes -> Step 7.
No -> Step 8.
7. Handle the related alarm, and check whether the alarm is cleared.
3-467
SJ-20140527134643-015|2015-03-31 (R1.1)
Yes -> End.

No -> Step 8.
8. Check whether the type of the board where the alarm arises is "ECMM".
Yes -> Step 9.
No -> Step 10.
9. Locate the EGBS board in accordance with "Rack number" and "Shelf number" in the alarm
information. Press the "RST-C" key on the EGBS board to reset the board. Wait for two minutes,
Yes -> End.
No -> Step 11.
10. Locate the board in accordance with "Rack number" , "Shelf number", and "Board type" in the
alarm information. Press the "RST-C" key on the board to reset the board. Wait for two minutes,
Yes -> End.
No -> Step 11.
3.3.30 199105042 The configuration of ECMM/EGBS/EGFS Board

doesn't match with OMM
Alarm Information
Alarm code:
199105042
Name:
The configuration of ECMM/EGBS/EGFS Board doesn't match with OMM
Alarm severity:
Major
Alarm type:
Alarm Description
The OMM detects that the ECMM/EGBS/EGFS configuration is not consistent with that on the OMM.
Alarm Cause
The configuration on the board is not the same as that on the OMM.
Impact
l
The system clock may not operate properly.
The media-plane inter-shelf communication is broken.
The environment monitoring function becomes invalid.
3-468
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Action
1. Synchronize the configuration through the online configuration of the independent board in
the Configuration Management window in accordance with "Rack number", "Shelf number",
and "Board type" in the alarm information. Wait for two minutes, and check whether the alarm
is cleared.
Yes -> End.
No -> Step 2.
3.3.31 199105045 The communication link between LogService

board for FST and OMP is broken
Alarm Information
l
l
l
l

Name: The communication link between LogService board for FST and OMP is broken
Alarm type: Communication alarm
Alarm Description
The OMP detects an interruption of the link with the full signaling log server board.
Alarm Cause
l
The full signaling log server board is not present.
The software of the full signaling log server is not operating properly.
The hardware of the full signaling log server board is faulty.
Impact
The signaling tracing log data related to the whole network cannot be stored on the log server.
Action
1. Check whether the full signaling log server board is present.
Yes -> Step 3.
No -> Step 2.
2. Install the full signaling log server board into the corresponding slot. Wait for 10 minutes, and
Yes -> End.
No -> Step 3.
3-469
SJ-20140527134643-015|2015-03-31 (R1.1)
3.3.32 199105047 The FTP link for full signal tracing is exceptional
Alarm Information
l
l
l
l

Name: The FTP link for full signal tracing is exceptional
Alarm type: Communication alarm
Alarm Description
Logservice detect that the FTP link for full signal tracing is exceptional or the transmission rate is too
low. That cause the files can not transfer to the FTP server immediately.
Alarm Cause
l
FTP configuration has error, that mainly include user name, password, IP Address, port.
The FTP link to FTP server is abnormal.
Impact
l
If the FTP configuration is error, the log files will be saved on disk. It maybe reduce the life
of disk and the files losing.
The log files will be accumulated on the service, and maybe cause the disk wrong and files losing.
Action
1. Check whether the "Full Signal Trace Configuration" is correct.
Yes -> Step 3.
No -> Step 2.
2. Please contact the FTP provider and modify the FTP configuration for full signal tracing, then
check whether the alarm is recovered.
Yes -> end.
No -> Step 3.
3. Contact the maintainer of transmission equipment and eliminate the fault, the check whether
Yes -> end.
No -> Step 4.
4. Please contact the next level of maintenance support.
3-470
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.3.33 199087775 Super site exchanged to the satellitic Abis link

or slave link
Alarm Information
Alarm code:
199087775
Name:
Super site exchanged to the satellitic Abis link or slave link
Alarm severity:
Major
Alarm type:
Alarm Description
This alarm is reported if the BSC detects that the Abis link of the super station is exchanged to
the satellite link or the standby link.
Alarm Cause
The subaerial Abis link of the super station is broken.
Impact
This alarm has no impact on the current operation of the system. However, the system reliability
will be decreased.
Action
1. Locate the alarm object, and check whether the object reports the following alarm:
199066026 Association path broken
Yes -> Step 2.
No -> Step 3.
Yes -> End.
No -> Step 3.
3.3.34 199087342 Cell interruption alarm

Alarm Information
Alarm code:
199087342
3-471
SJ-20140527134643-015|2015-03-31 (R1.1)
Name:
Cell interruption alarm
Alarm severity:
Minor
Alarm type:
Alarm Description
This alarm is reported if the BSC detects that the state of a cell is abnormal.
Alarm Cause
l
The link between the BSC and the site that the cell belongs to is broken.
The BCCH TRX of the cell is faulty.
The cell is manually blocked.
The configuration of related cell parameters is incorrect.
Impact
The cell fails to provide any voice or data service.
Action
1. Locate the site in accordance with "Site ID" in the alarm details, and check whether the following
alarms exist in the site:
199087336 Rack Abis control link broken
199087337 Site Abis control link broken
Yes -> Step 2.
No -> Step 3.
Yes -> End.
No -> Step 3.
3. Query the "GSM Cell Configuration(GGsmCell)" object of the cell, check the following parameters
of the object, perform necessary operations as required, and check whether the alarm is cleared.
l
"Cell management"
Execute the QRY CELL command to query the cell state in accordance with "Site ID" and
"Bts ID". If the cell is manually blocked, execute the UNB CELL command to unblock the cell.
"TRX management"
If the BCCH TRX corresponding to the cell is manually blocked, execute the UNB FUTRX or
UNB CUTRX command to unblock the TRX.
If the CU or FU operation state of the TRX is blocked, which indicates a TRX fault, query and
clear related alarms in the base station. If the alarm persists, proceed to Step 4.
"Channel Management"
If the BCCH timeslot corresponding to the cell is manually blocked, execute the UNB TS
command to unblock the timeslot.
Yes -> End.

No -> Step 4.
3-472
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.3.35 199087380 TRX Manual Block

Alarm Information
Alarm code:
199087380
Name:
TRX Manual Block
Alarm severity:
Minor
Alarm type:
Alarm Description
This alarm is reported if the BSC detects that a TRX is manually blocked.
Alarm Cause
The TRX is manually blocked.
Impact
The blocked TRX fails to provide any service.
Action
1. Locate the blocked TRX in accordance with "Site ID", "Bts ID", and "Trx ID" in the alarm details,
and execute the UNB FUTRX or UNB CUTRX command to unblock the TRX. Check whether
Yes -> End.
No -> Step 2.
3.3.36 199087336 Rack Abis control link broken

Alarm Information
Alarm code:
199087336
Name:
Rack Abis control link broken
Alarm severity:
Critical
3-473
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm type:
Alarm Description
This alarm is reported if the BSC detects that the control link between the controller and a rack
is broken.
Alarm Cause
l
The configured rack does not exist.
In case of an IP site, the IP-related configuration is incorrect.
In case of an E1 site, the Abis timeslot configuration is incorrect.
The Abis transmission is abnormal.
Impact
The rack fails to provide any service.
Action
1. Locate "Site ID" in the alarm details, and check whether the corresponding site is required in
the network planning.
Yes -> Step 2.
No -> Delete the site configuration, or suppress the alarm. End alarm handling.
2. Check whether the following association and PPP related alarms exist in accordance with "Site
ID" or "office information" in the alarm details.
199000514 Trunk alarm indication signal
199000515 Trunk loss of CRC multi-frame
199000517 Trunk remote alarm indication
Yes -> Step 3.
No -> Step 4.
Yes -> End.
No -> Step 4.
3.3.37 199087468 lapd jam alarm

Alarm Information
Alarm code:
199087468
3-474
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Name:
lapd jam alarm
Alarm severity:
Major
Alarm type:
Alarm Description
This alarm is reported if the BSC detects LAPD link congestion between the rack and the BSC.
Alarm Cause
l
Too few LAPD links are configured.
The traffic is too high.
Impact
A severe loss of frames occurs on LAPD channels, which results in abnormal or even interrupted
communication. The quality of service degrades.
Action
1. Check whether enough LAPD channels are configured in accordance with the number of TRXs
configured on the site.
The recommended configuration is as follows:
l
When 6 TRXs are configured, at least one LAPD channel must be configured.
When 7 to 16 TRXs are configured, at least two LAPD channels must be configured.
When 17 to 26 TRXs are configured, at least three LAPD channels must be configured.
When 27 to 36 TRXs are configured, at least four LAPD channels must be configured.
Yes -> Step 3.

No -> Step 2.
2. Add one or more LAPD channels as follows: In Configuration Management, view the attributes
of the CMB board on the rack diagram of the base station, and then add an "OMU slot number".
Yes -> End.
No -> Step 3.
3. Check whether the following alarm and notification exist in accordance with "Site ID" in the
alarm details or the object reporting the alarm:
198087102 Power overvoltage/undervoltage alarm
199000576 Trunk slip
Yes -> Step 4.
No -> Step 5.
Yes -> End.
No -> Step 5.
3-475
SJ-20140527134643-015|2015-03-31 (R1.1)
3.3.38 199087337 Site Abis control link broken

Alarm Information
Alarm code:
199087337
Name:
Site Abis control link broken
Alarm severity:
Critical
Alarm type:
Alarm Description
This alarm is reported if the BSC detects that the LAPD communication link of a base station is broken.
Alarm Cause
l
The configured site does not exist.
In case of an IP site, the IP-related configuration is incorrect.
In case of an E1 site, the Abis timeslot configuration is incorrect.
The Abis transmission is abnormal.
Impact
All cells of the site fail to provide any voice or data service.
Action
1. Locate "Site ID" in the alarm details, and check whether the corresponding site is required in
the network planning.
Yes -> Step 2.
No -> Delete the site configuration, or suppress the alarm. End alarm handling.
2. Check whether the following association and PPP related alarms exist in accordance with "Site
ID" or "office information" in the alarm details.
Yes -> Step 3.
No -> Step 4.
Yes -> End.
No -> Step 4.
3-476
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.3.39 198087101 HW link broken

Alarm Information
Alarm code:
198087101
Name:
HW link broken
Alarm severity:
Minor
Alarm type:
Alarm Description
HW link broken
Alarm Cause
BTS internal communication breaks
Impact
The site fails to operate properly.
Action
1. Start HW self-loop test to check whether the cable connection goes wrong.
2. If all of DTRU fail to build link, re-plug CMB board.
3. If the software has problem, upgrade it.
3.4 Qos Alarm

3.4.1 199066018 Association congested
Alarm Information
l
l
l
l

Name: Association congested
Alarm type: Qos Alarm
Alarm Description
This alarm is raised if the messages transmitted by the association exceed 7/8 of the cache capacity.
3-477
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Cause
l
l
Too many services need to be processed, which causes the SCTP association to be overloaded.
The SCTP associations are overloaded because some SCTP associations are faulty or the
routing is not well balanced.
Some networks are disconnected or the network bandwidth is insufficient.
Impact
Congestion may result in transmission delay. In normal cases, services are not affected. In serious
cases, congestion may result in call loss and reduced access rate.
Action
1. Check whether there is any fault on other associations that results in congestion of the
association. Check whether other associations have any of the following alarms:
Yes -> Step 2.
No -> Step 3.
2. Handle the above alarms, wait for three minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3. Query the measurement type "Statistics of SCTP Link performance" of the "SCTP ASSOCIATION"
object, query the corresponding counters "C380170007 Packets sent to SCTP in bytes in the
unbroken period" and "C380170009 The flow of SCTP sent", and check whether the counter
values increase significantly.
Yes -> Step 4.
No -> Step 6.
4. Contact the network optimization personnel to check whether it is required to add the carrier
network bandwidth (by adding associations or send buffer).
Yes -> Step 5.
No -> Step 6.
5. Add associations. Wait for three minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 6.
3.4.2 199105044 The internal KPI of the logic board is abnormal

Alarm Information
Code:
199105044
Name:
The internal KPI of the logic board is abnormal

3-478
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Severity:
Minor
Type:
Qos Alarm
Alarm Description
The base station controller detects an abnormal internal KPI index in a logical board.
Probable Cause
l
The program on the logical board is not operating properly.
The hardware of the physical board is faulty.
System Impact
The internal key index of the logical board is abnormal, indicating that an abnormality occurs inside the
board. This means that the board cannot operate properly and services cannot be properly connected.
Handling Suggestion
1. Check whether "The alarm reason" in alarm information is "the memory bank of the board which
the logic unit located is abnormal".
Yes -> Step 2.
No -> Step 6.
2. Check "Module number of the abnormal logic board", "Subsystem number of the abnormal
logic board", and "Subsystem number of the abnormal logic board" in alarm information. If the
setting of "Subsystem number of the abnormal logic board" is 65535, and if the setting of "Unit
of the abnormal logic board" is 255, query the module backup mode in the Configuration
Management window in accordance with the setting of "Module number of the abnormal logic
board". Otherwise, query the physical address in the Configuration Management window in
accordance with the settings of "Subsystem number of the abnormal logic board" and "Unit of the
abnormal logic board". Based on the physical address, Remove and reinstall the board memory
or replace the board memory with an operational one (refer to Replacing a Memory Bar), and
power on the board. Wait for three minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 6.
3. Check "Module number of the abnormal logic board", "Subsystem number of the abnormal
logic board", and "Subsystem number of the abnormal logic board" in alarm information. If the
setting of "Subsystem number of the abnormal logic board" is 65535, and if the setting of "Unit
of the abnormal logic board" is 255, query the module backup mode in the Configuration
Management window in accordance with the setting of "Module number of the abnormal logic
board". Otherwise, query the unit backup mode in the Configuration Management window in
accordance with the settings of "Subsystem number of the abnormal logic board" and "Unit of
the abnormal logic board".
1+1 backup mode -> Step 4
No backup -> Step 5
3-479
SJ-20140527134643-015|2015-03-31 (R1.1)
4. Open the rack diagram in the [Status Management] window, perform the "Normal switch" or
"Forcible switch" operation for the faulty logical board. Wait for 15 minutes, and check whether
Yes -> End.
No -> Step 6.
"Shelf number", "Slot number", and "CPU number" in the alarm information. Wait for 15 minutes,
and check whether the alarm persists.
Yes -> Step 6.
No -> End.
3.4.3 199087344 MSC overload control alarm at FUC mode

Alarm Information
Alarm code:
199087344
Name:
MSC overload control alarm at FUC mode
Alarm severity:
Minor
Alarm type:
Qos Alarm
Alarm Description
This alarm is reported if the BSC initiates flow control in "FUC control mode" upon receiving
"OVERLOAD" from the MSC through the A-interface.
The "FUC control mode" allows the base station to discard the access messages of some MSs as
required by the BSC.
Alarm Cause
The BSC receives "OVERLOAD" from the MSC.
Impact
Some new users fail to gain access to the system.
Action
No action is required.
3-480
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.4.4 199087345 CPU overload control alarm at FUC mode

Alarm Information
Alarm code:
199087345
Name:
CPU overload control alarm at FUC mode
Alarm severity:
Minor
Alarm type:
Qos Alarm
Alarm Description
This alarm is reported if the BSC initiates flow control in "FUC control mode" upon detecting that the
CPU load is above "GSM Logical Configuration(GBssFunction)"."Start limit of FUC flow control
for CPU overload(CpuFucCtlCpu)".
Alarm Cause
The system traffic becomes too high transiently.
Impact
Some users fail to gain access to the system due to the flow control automatically initiated by the
BSC. If the traffic is still excessive after flow control, the CPU load may grow further. In this case,
the system may break down.
Action
1. Query "Flow Control Level" in the alarm details. If the flow control level is five or lower, wait for
three minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 2.
2. Execute the BLK FUTRX or BLK CUTRX command based on "Site ID", "Bts ID", and "Trx
ID" to block some cells. In this way, the access of some users can be limited to avoid system
breakdown caused by further increase of the CPU load. Check whether the alarm is cleared.
Yes -> Step 3.
No -> Step 2.
3. Execute the UNB FUTRX or UNB CUTRX command to unblock some cells one batch at a time
based on "Site ID", "Bts ID", and "Trx ID". The alarm handling is completed.
3-481
SJ-20140527134643-015|2015-03-31 (R1.1)
3.4.5 199087346 Signaling point congestion control alarm at FUC

mode
Alarm Information
Alarm code:
199087346
Name:
Signaling point congestion control alarm at FUC mode
Alarm severity:
Minor
Alarm type:
Qos Alarm
Alarm Description
This alarm is reported if the BSC initiates flow control in "FUC control mode" upon detecting No.7
signaling point congestion on the A-interface.
Alarm Cause
The A-interface is congested with excessive No.7 signaling messages.
Impact
BSC. If the traffic is still excessive after flow control, the signaling on the A-interface may be blocked
and services may be interrupted.
Action
Yes -> End.
No -> Step 2.
2. Execute the BLK FUTRX or BLK CUTRX command based on "Site ID", "Bts ID", and "Trx ID"
to block some cells. In this way, the access of some users can be limited to avoid A-interface
disconnection caused by further increase of the No.7 signaling load. Check whether the alarm
is cleared.
Yes -> Step 3.
No -> Step 2.
3. Execute the UNB FUTRX or UNB CUTRX command to unblock some cells one batch at a time
based on "Site ID", "Bts ID", and "Trx ID". The alarm handling is completed.
3-482
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.4.6 199087347 MSC overload control alarm at SYS mode

Alarm Information
Alarm code:
199087347
Name:
MSC overload control alarm at SYS mode
Alarm severity:
Minor
Alarm type:
Qos Alarm
Alarm Description
This alarm is reported if the BSC initiates flow control in "system message control mode" upon
receiving "OVERLOAD" from the MSC through the A-interface.
The "system message control mode" allows the base station to deny the access of some MSs through
the system information broadcasted over the air interface.
Alarm Cause
The BSC receives "OVERLOAD" from the MSC.
Impact
Action
3.4.7 199087348 CPU overload control alarm at SYS mode

Alarm Information
Alarm code:
199087348
Name:
CPU overload control alarm at SYS mode
Alarm severity:
Minor
Alarm type:
Qos Alarm
3-483
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Description
detecting that the CPU load is above "GSM Logical Configuration(GBssFunction)"."Start limit of
system message method for CPU overload(CpuSysInfoCtlCpu)".
Alarm Cause
Impact
Action
1. Query "Flow Control Level" in the alarm details. If the flow control level is eight or lower, wait for
Yes -> End.
No -> Step 2.
2. Execute the BLK CELL command to block some cells based on "Site ID" and "Bts ID" in the
alarm details. In this case, the access of some users can be limited to avoid system breakdown
caused by excessive CPU load. Check whether the alarm is cleared.
Yes -> Step 3.
No -> Step 2.
3. Execute the UNB CELL command to unblock some cells based on "Site ID" and "Bts ID" in the
alarm details. The alarm handling is completed.
3.4.8 199087349 Signaling point congestion control alarm at SYS

mode
Alarm Information
Alarm code:
199087349
Name:
Signaling point congestion control alarm at SYS mode
Alarm severity:
Minor
Alarm type:
Qos Alarm
3-484
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Description
detecting No.7 signaling point congestion on the A-interface.
Alarm Cause
The A-interface is congested with excessive No.7 signaling messages.
Impact
BSC. If the traffic is still excessive after flow control, the signaling on the A-interface may be blocked
and services may be interrupted.
Action
Yes -> End.
No -> Step 2.
2. Execute the BLK CELL command to block some cells in accordance with "Site ID" and "Bts ID"
in the alarm details. In this case, the access of some users can be limited to avoid system
breakdown caused by excessive CPU load. Check whether the alarm is cleared.
Yes -> Step 3.
No -> Step 2.
3. Execute the UNB CELL command to unblock some cells in accordance with "Site ID" and "Bts
ID" in the alarm details. The alarm handling is completed.
3.4.9 199087350 CCCH overload control

Alarm Information
Alarm code:
199087350
Name:
CCCH overload control
Alarm severity:
Minor
Alarm type:
Qos Alarm
3-485
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Description
This alarm is reported if the BSC detects the RACH load of a cell exceeds the threshold ("GSM
Cell Configuration(GGsmCell)"."CCCH load indication (RACH)(CcchLoadINDThs_0)"), or the PCH
load of a cell exceeds the threshold ("GSM Cell Configuration(GGsmCell)"."CCCH load indication
(PCH)(CcchLoadINDThs_1)").
Alarm Cause
Too many MSs request to gain access to the CCCH.
Impact
Some MS CS services under this cell fail to gain access to the system due to the flow control
automatically initiated by the BSC.
Action
ten minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 2.
2. If the alarm occurs frequently, contact network optimization engineers to:
l
add CCCHs to the cell, or
expand the capacity of the overloaded cell, or
share the traffic.
3.4.10 199087506 NSE block alarm

Alarm Information
Alarm code:
199087506
Name:
NSE block alarm
Alarm severity:
Major
Alarm type:
Qos Alarm
Alarm Description
This alarm is reported if the BSC detects that all NSVCs of an NSE are in the "block" state.
3-486
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Cause
l
All NSVCs of the NSE are manually blocked.
Gb interface link is broken.
Impact
The PS service of this NSE is unavailable.
Action
1. Locate the alarm object in Status Management, and query the state of NSVC link. Verify that
the state is "manual block".
Yes -> Step 2.
No -> Step 3.
2. Execute the UNB NSVC command to unblock all NSVC links which are in the "manual block"
state and check whether the alarm is cleared in accordance with "SGSN ID", "NSE ID", and
"NSVC ID" in the alarm details.
Yes -> End.
No -> Step 3.
3. Check whether the following alarms exist:
199087352 NSVC's E1 failure alarm
199087465 NSVC's IP failure alarm
Yes -> Step 4.
No -> Step 5.
Yes -> End.
No -> Step 5.
3.4.11 199087507 SGSN is blocked

Alarm Information
Alarm code:
199087507
Name:
SGSN is blocked
Alarm severity:
Major
Alarm type:
Qos Alarm
Alarm Description
This alarm is reported if the BSC detects that all NSVCs of an SGSN are in the "block" state.
3-487
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Cause
l
All NSVCs of the SGSN are manually blocked.
Gb interface link is broken.
Impact
The PS service of this SGSN is unavailable.
Action
1. Execute the QRY NSVC command to query the state of this NSVC link and check whether the
state is "manual block" in accordance with "SGSN ID", "NSE ID", and "NSVC ID" in the alarm
details.
Yes -> Step 2.
No -> Step 3.
2. Execute the UNB NSVC command to unblock all NSVC links which are in the "manual block"
state and check whether the alarm is cleared in accordance with "SGSN ID", "NSE ID", and
"NSVC ID" in the alarm details.
Yes -> End.
No -> Step 3.
199087352 NSVC's E1 failure alarm
199087465 NSVC's IP failure alarm
Yes -> Step 4.
No -> Step 5.
Yes -> End.
No -> Step 5.
3.4.12 199087758 Manual User Access control alarm

Alarm Information
Alarm code:
199087758
Name:
Manual User Access control alarm
Alarm severity:
Minor
Alarm type:
Qos Alarm
3-488
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Description
This alarm is reported if the BSC initiates flow control in "manual user access control mode".
"manual user access control mode" indicates that the network management system delivers flow
control parameters to the BSC and the BSC executes flow control unconditionally.
Alarm Cause
The "manual user access control" function is initiated.
Impact
Action
3.4.13 199087759 CPU overload control alarm at Paging mode

Alarm Information
Alarm code:
199087759
Name:
CPU overload control alarm at Paging mode
Alarm severity:
Minor
Alarm type:
Qos Alarm
Alarm Description
This alarm is reported if the BSC initiates flow control in "paging control mode" upon detecting that
the CPU load exceeds the threshold ("GSM Logical Configuration(GBssFunction).CPU threshold of
paging flow control(CpuPagingCtlCpu)").
"paging control mode" indicates that the BSC discards some paging messages.
Alarm Cause
Impact
3-489
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
in the alarm details. Limit the access of some users to avoid system breakdown caused by
excessive CPU load. Check whether the alarm is cleared.
Yes -> Step 2.
No -> Step 1.
3.4.14 199087773 CIC manual blocked alarm

Alarm Information
Alarm code:
199087773
Name:
CIC manual blocked alarm
Alarm severity:
Minor
Alarm type:
Qos Alarm
Alarm Description
This alarm is reported if the BSC detects that the state of A-interface trunk circuit is manually blocked.
Alarm Cause
Trunk circuit of A-interface is manually blocked.
Impact
The blocked circuit cannot provide services.
Action
1. Check whether the object is manually blocked by maintenance personnel.
Yes -> End.
No -> Step 2.
2. Locate the alarm object, and search the parent object "Trx(GTrx)". Check the parameter "TRX
Sequence(GTrxSeq)".
Locate the carrier object, and search the parent object of this carrier "GSM Cell
Configuration(GGsmCell)". Check the parameter "GSM Cell Configuration ID(GGsmCellId)".
Locate the GSM cell configuration object, and search the parent object of the
GSM cell configuration object "Site(GBtsSiteManager)". Check the parameter "Site
ID(GBtsSiteManagerId)".
3-490
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Execute the UNB TS command to unblock this time slot in accordance with "Ts ID" in the above
three parameters and the alarm details. Check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3.4.15 199087774 BVC manual blocked alarm

Alarm Information
Alarm code:
199087774
Name:
BVC manual blocked alarm
Alarm severity:
Minor
Alarm type:
Qos Alarm
Alarm Description
This alarm is reported if the BSC detects that the state of BVC is manually blocked.
Alarm Cause
BVC is manually blocked.
Impact
The blocked BVC cannot provide services.
Action
Yes -> End.
No -> Step 2.
2. Execute the UNB BVC command to unblock this BVC in accordance with "SGSN ID", "NSEI",
and "BVC ID" in the alarm details. Check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3-491
SJ-20140527134643-015|2015-03-31 (R1.1)
3.4.16 199087517 Shelf overload control alarm at FUC mode

Alarm Information
Alarm code:
199087517
Name:
Shelf overload control alarm at FUC mode
Alarm severity:
Minor
Alarm type:
Qos Alarm
Alarm Description
This alarm is reported if the BSC initiates flow control in "FUC control mode" upon detecting inter-shelf
traffic overload in the system.
The "FUC control mode" allows the base station to discard the access messages of some mobile
phones as required by the BSC.
Alarm Cause
Impact
Action
Yes -> End.
No -> Step 2.
in the alarm details. Limit the access of some users to avoid system breakdown caused by further
increase of the inter-shelf traffic. Check whether the alarm is cleared.
Yes -> Step 3.
No -> Step 2.
3. Execute the UNB CELL command to unblock some cells one batch at a time in accordance with
"Site ID" and "Bts ID" in the alarm details. The alarm handling is completed.
3-492
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
3.4.17 199087518 Shelf overload control alarm at SYS mode

Alarm Information
Alarm code:
199087518
Name:
Shelf overload control alarm at SYS mode
Alarm severity:
Minor
Alarm type:
Qos Alarm
Alarm Description
detecting inter-shelf traffic overload in the system.
Alarm Cause
Impact
Action
Yes -> End.
No -> Step 2.
in the alarm details. In this case, the access of some users can be limited to avoid system
breakdown caused by further increase of the inter-shelf traffic. Check whether the alarm is
cleared.
Yes -> Step 3.
No -> Step 2.
3-493
SJ-20140527134643-015|2015-03-31 (R1.1)
3.4.18 199087381 The time-slot of air interface blocked manually

Alarm Information
Alarm code:
199087381
Name:
The time-slot of air interface blocked manually
Alarm severity:
Minor
Alarm type:
Qos Alarm
Alarm Description
This alarm is reported if the BSC detects that a timeslot of the air interface is manually blocked.
Alarm Cause
The timeslot is manually blocked.
Impact
The blocked timeslot fails to provide any service.
Action
Yes -> End.
No -> Step 2.
2. Locate the blocked timeslot in accordance with "Site ID", "Bts ID", "Trx ID", and "Ts ID" in the
alarm details, and execute the UNB TS command to unblock the timeslot. Check whether the
alarm is cleared.
Yes -> End.
No -> Step 3.
3.4.19 199101003 The usage of DPI DBS table space exceeds the
limit value
Alarm Information
l
l
l
l

Name: The usage of DPI DBS table space exceeds the limit value
Alarm type: QoS alarm
3-494
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 3 Alarms
Alarm Description
The usage of DPI DBS table space exceeds the limit value.
Alarm Cause
The usage of user table space exceeds the limit value.
Impact
DPI recognition accuracy rate will go down.
Action
1. Modify the capacity configuration according to the resource (memory) state, and restart the
system.
2. Add DPI equipment, control and reduce the user amount accessing the DPI equipment.
3-495
SJ-20140527134643-015|2015-03-31 (R1.1)
3-496
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 4
Notifications
Table of Contents
199026176 The currently locked reference of the clock board has been changed ......4-3
199000576 Trunk slip .................................................................................................4-4
199000834 HDLC is abnormal ...................................................................................4-5
199001600 CPU resets on a board in the same shelf .................................................4-6
199004418 Logic CPU is power on successfully.........................................................4-7
199004419 Logic CPU is power on failed ...................................................................4-7
199005189 Board change over ..................................................................................4-9
199005448 Environment parameters set fail...............................................................4-9
199005718 Two master clock ports is directly connected..........................................4-10
199005720 The CDM data was covered...................................................................4-11
199005977 Running version not match with database configuration.........................4-12
199005982 Patch operation failed ............................................................................4-13
199005983 Write back version information ...............................................................4-13
199005984 Check version information......................................................................4-14
199005985 Synchronize version information ............................................................4-14
199006720 Environment monitoring board is powered on or reset............................4-15
199007232 Poor board recover ................................................................................4-16
199008000 Failed to load data after the node is powered on ....................................4-17
199008007 Database failed to save data..................................................................4-18
199008769 Failed to synchronize data between nodes ............................................4-20
199008770 Failed to update node data ....................................................................4-21
199010048 Insufficient memory of database ............................................................4-22
199011073 LAPD failed to initialize HDLC ................................................................4-23
199011333 MTP2 failed to initialize HDLC................................................................4-24
199013890 Sigtran error message received .............................................................4-25
199014145 Restart the association ..........................................................................4-26
199014150 Association config error .........................................................................4-27
199014152 Dynamic association config error ...........................................................4-28
199017992 Protocol state of aggregation port member interface is down .................4-29
199017993 Failed to add IPv6 dynamic route ...........................................................4-30
199018241 TCP connection closed ..........................................................................4-32
199018500 The peer IP address is the same as the local IP address of the PPP
link ...........................................................................................................................4-34
199018501 Fail to create the HDLC channel ............................................................4-35
199018502 Fail to initialize the HDLC chip ...............................................................4-36
199018504 Succeed to create the HDLC channel ....................................................4-37
199018753 The configuration of UID/HDLC/IPE1 in database is wrong ....................4-38
4-1
SJ-20140527134643-015|2015-03-31 (R1.1)
199019777 APS switchover happens .......................................................................4-39

199020554 Failed to add PPP route .........................................................................4-40
199020571 Failed to perform offline configuration ....................................................4-42
199020802 An IP address conflicts with another system on the subnet ....................4-42
199020803 A MAC address conflicts with another system on the subnet..................4-43
199020805 ARP detecting failed ..............................................................................4-44
199020806 ARP detecting reply is different from static ARP.....................................4-46
199021330 Failed to establish OSPFv2 neighbors ...................................................4-47
199021837 Fail to add dynamic route.......................................................................4-50
199028233 Failed to establish OSPFv3 neighbors ...................................................4-51
199030528 The result of starting PD task .................................................................4-54
199030820 Memory inform reported by BIOS...........................................................4-56
199031041 ACL query table is unavailable...............................................................4-57
199032064 IPv6 addresses conflicted ......................................................................4-58
199032065 Peer-end IPv6 addresses of SuperVLAN member interfaces conflict .....4-60
199032066 Static neighbor cache entry detecting not matched ................................4-61
199032067 Neighbor cache entry detecting failed ....................................................4-62
199031297 PTP slave port link broken .....................................................................4-64
199031298 PTP slave port change...........................................................................4-65
199105001 Failed to get the table of configuration ...................................................4-66
199105002 The route table is overloaded.................................................................4-69
199105003 Failed to handle DHCP message from other network .............................4-70
199105004 Failed to operate multicast group ...........................................................4-71
199105005 Clock difference of slave is large............................................................4-72
199105006 Slave losted external clock.....................................................................4-73
199105008 Bandwidth automatic adjustment is useless ...........................................4-74
199105018 Unable to save Performance File ...........................................................4-75
199105019 SLAVE memory check fail notification ....................................................4-76
199105030 OMP received data is not complete........................................................4-77
199105032 Transport Path Occupied BandWidth Overload ......................................4-78
199105033 Transport Path group Occupied Bandwidth Overload.............................4-79
199105043 The slave's IPUDP configuration is modified ..........................................4-80
199105046 The log files on LogService board are unavailable .................................4-81
199105048 OMP disk reserved for performance files is insufficient ..........................4-82
199087360 BCCH Exchange Fail .............................................................................4-82
199087393 Ring state notification.............................................................................4-84
199087394 Intelligent power up/down preparation notification ..................................4-84
199087459 cell no gprs traffic inform ........................................................................4-85
199087469 abis route change inform .......................................................................4-86
199087353 NSVC deletion notification .....................................................................4-86
199087395 SNS Size process failure notification......................................................4-87
199087396 SNS Config process failure notification ..................................................4-88
199087466 NSVC's IP deletion notification...............................................................4-89
199087359 No access of BSC to MSC SPC.............................................................4-90
199087503 Baseband frequency hopping exchange for trx fail .................................4-90
4-2
SJ-20140527134643-015|2015-03-31 (R1.1)
Chapter 4 Notifications
199087504 Baseband frequency hopping exchange for trx restore...........................4-91

199087508 Block Successfully After Service released..............................................4-92
199087751 dbsapp no avilable PCU resource inform ...............................................4-93
199087760 BTS master power recover notification...................................................4-93
199087761 BTS master power interruption notification .............................................4-94
199087762 After BTS mains power failure TRX terminated notification ....................4-95
199087772 Super Site Connect in ............................................................................4-96
199087799 Cell intelligent power-on or power-down.................................................4-96
199087514 TRAU frame sync loss notification .........................................................4-97
199087515 BCCH Exchange Success .....................................................................4-97
199087516 Mute call detect......................................................................................4-98
199087519 Release dynamic association by force ...................................................4-99
199087520 Gb interface throughput exceed permissible value ...............................4-100
199087521 Cell's home-processor transformed......................................................4-101
198087338 TRX No Traffic .....................................................................................4-102
198087434 Cannot detect up or down TRAU notification........................................4-102
198087339 BTS self maintenance inform ...............................................................4-103
198087477 site board cpu overload........................................................................4-103
198087478 uplink user layer jam inform .................................................................4-104
198087479 downlink user layer jam inform.............................................................4-105
198087488 chp cycle adjust trau information..........................................................4-105
198087500 Radio Interface Synchronization ARF emendate Successfully .............4-106
198087501 Radio Interface Synchronization ARF emendate Failed .......................4-107
198087502 Site IP Address conflicted ....................................................................4-107
198087512 IDS Attack detecting ............................................................................4-108
4.1 199026176 The currently locked reference of the

clock board has been changed
Notification Information
l
l
l
l
Notification code: 199026176

Name: The currently locked reference of the clock board has been changed
Notification severity: Minor
Notification type: Equipment Alarm
Notification Description
This notification is raised if the clock board detects that the locked clock reference is switched over
to another reference.
Notification Cause
The locked clock reference changes.
4-3
SJ-20140527134643-015|2015-03-31 (R1.1)
Impact
The system clock may fail to be synchronized, so services may be affected.
Action
4.2 199000576 Trunk slip

l
l
l
l

Name: Trunk slip
This notification is raised if the board detects that code slip on the trunk.
Notification Cause
The clocks on both ends of the trunk are not synchronized.
Impact
Momentary faults occur to a data service or on a signaling channel in the trunk link. In normal cases,
this does not affect services. If the alarm occurs frequently, services may be affected.
Action
1. Determine whether the shelf type is ETCA (for the controller, it is fixed to ETCA) in accordance
with the "Rack number" and "Shelf number" in the alarm information.
Yes -> Step 2.
No -> Step 4.
2.
In the Independent Board Configuration Online window, check whether the clock reference
(any clock reference with a priority in the range from level 1 through level 4) is configured for
the clock board in the master shelf of the NE.
Yes -> Step 6.
No -> Step 3.
3. Add the clock reference configuration as required. Wait for 15 minutes, and check whether the
notification persists.
Yes -> End.
No -> Step 6.
4. Check whether the clock reference is configured for the clock board in the master shelf of the NE.
4-4
SJ-20140527134643-015|2015-03-31 (R1.1)
Yes -> Step 6.

No -> Step 5.
5. Add the clock reference configuration as required. Wait for 15 minutes, and check whether the
Yes -> End.
No -> Step 6.
6. Contact the maintenance personnel of the peer device to check whether the peer device and
transmission device are added to the clock synchronization network.
Yes -> Step 8.
No -> Step 7.
7. Add the peer device and transmission device to the clock synchronization network. Wait for 15
minutes, and check whether the notification persists.
Yes -> End.
No -> Step 8.
Yes -> Step 9.
No -> Step 10.
9. Clear the above alarms, wait for 15 minutes and then check whether the notification persists.
Yes -> End.
No -> Step 10.
10. Check whether the following alarms are raised on the clock boards in Slots 21 and 22:
Yes -> Step 11.
No -> Step 12.
11. Clear the above alarms, wait for 15 minutes and then check whether the notification persists.
Yes -> End.
No -> Step 12.
4.3 199000834 HDLC is abnormal

l
l
l
l

Name: HDLC is abnormal
Notification severity: Major
4-5
SJ-20140527134643-015|2015-03-31 (R1.1)
This notification is raised if the board detects that the HDLC hardware is abnormal.
Notification Cause
The HDLC hardware is faulty.
Impact
All HDLC channels cannot transmit or receive data.
Action
1. Run the SET FORCERESETcommand to reset the board in accordance with the "Rack number",
"Shelf number", "Slot number" and "CPU number" in the alarm information. Check whether
Yes -> End.
No -> Step 2.
2. Replace the faulty board(refer to Front Boards and Rear Boards Replacement), and then check
whether the notification persists.
Yes -> End.
No -> Step 3.
4.4 199001600 CPU resets on a board in the same shelf

l
l
l
l

Name: CPU resets on a board in the same shelf
This notification is raised if the CMM board detects that a board in another slot of the same shelf is
reset.
Notification Cause
l
The board is reset abnormally.
The board is reset manually.
4-6
SJ-20140527134643-015|2015-03-31 (R1.1)
Impact
Services cannot be carried on the board when the board is reset.
Action
1. View the operation log, and check whether the board is reset by the network management system.
Yes -> End.
No -> Step 2.
4.5 199004418 Logic CPU is power on successfully

l
l
l
l

Name: Logic CPU is power on successfully
Notification type: Processing alarm
This notification is raised if the board detects that all processes under the logical CPU are powered
on successfully. This notification indicates that the logical entity is powered on successfully, and
is in operating status.
Notification Cause
All processes under the logical CPU are powered on successfully.
Impact
None.
Action
4.6 199004419 Logic CPU is power on failed

l
l
l

Name: Logic CPU is power on failed
4-7
SJ-20140527134643-015|2015-03-31 (R1.1)
This notification is raised if the board detects that one or more processes under the logical CPU
fail to be powered on or the power-on expires.
Notification Cause
l
One or more processes under the logical CPU fail to be powered on.
The power-on of one or more processes under the logical CPU expires.
Impact
The logical board fails to operate properly.
Action
1. Determine whether the board is OMP ("Module number" is 1, and "Unit number" is 65535) in
accordance with the "Module number" and "Unit number" in the alarm information.
Yes -> Step 2.
No -> Step 4.
2. Check whether the master OMP operates properly through the rack diagram. (Refer to Controller
Rack)
Yes -> Step 10.
No -> Step 3.
3. Wait for the master OMP to operate properly, and check whether the alarm is cleared.
Yes -> End.
No -> Step 10.
4. Query the slot number of the partner board in accordance with "Rack number", "Shelf number",
and "Slot number" in the alarm information and the "Backup Slot No. (StandbySlot)" parameter of
the "Board(Board)" object. Check whether the partner board operates properly through the rack
diagram. (Refer to Controller Rack)
Yes -> Step 6.
No -> Step 5.
5. Wait for the partner board to operate properly, and check whether the alarm is cleared.
Yes -> End.
No -> Step 6.
6. Check whether the master OMP operates properly through the rack diagram. (Refer to Controller
Rack)
Yes -> Step 8.
No -> Step 7.
7. Wait for the OMP to operate properly, and check whether the alarm is cleared.
Yes -> End.
No -> Step 8.
4-8
SJ-20140527134643-015|2015-03-31 (R1.1)
Yes -> Step 9.
No -> Step 10.
Yes -> End.
No -> Step 10.
4.7 199005189 Board change over

l
l
l
l

Name: Board change over
This notification is raised after the board active/standby switchover completes.
Notification Cause
The board switchover operation is performed automatically or manually.
Impact
None.
Action
4.8 199005448 Environment parameters set fail

l
l
l
l

Name: Environment parameters set fail
Notification type: Communications Alarm
4-9
SJ-20140527134643-015|2015-03-31 (R1.1)
This notification is raised if the CMM fails to set environment monitoring parameters on the monitoring
board.
Notification Cause
l
The communication between the CMM and the environment monitoring board is abnormal.
The environment monitoring board is faulty.
Impact
The configured environment parameters are not effective, and the monitoring result may differ from
the real circumstance. There is no impact on services.
Action
1. Check whether the following alarm exists:
199005382 Environment monitor board communication is abnormal
Yes -> Step 2.
No -> Step 3.
Yes -> End.
No -> Step 3.
"Shelf number", "Slot number", and "CPU number" in the alarm information. Check whether the
notification is still reported.
Yes -> Step 4.
No -> End.
4.9 199005718 Two master clock ports is directly

connected
l
l
l
l

Name: Two master clock ports is directly connected
This notification is raised if the local port that operates as a master clock port detects that the
interconnected port is also a master clock port.
4-10
SJ-20140527134643-015|2015-03-31 (R1.1)
Notification Cause
l
The local port is incorrectly set as the master clock port.
The peer port is incorrectly set as the master clock port.
Impact
The clock of the NE may fail to be synchronized, and thus services may be affected.
Action
1. Check whether the "Synchronization Enable Flag(SyncE)" parameter of the local-end "Ethernet
Port(EthernetPort)" object is set as required.
Yes -> Step 3.
No -> Step 2.
2. Modify the "Synchronization Enable Flag(SyncE)" parameter as required, and check whether
Yes -> End.
No -> Step 3.
3. Contact the maintenance personnel of the peer end, and check whether the master configuration
of the peer-end clock is in accordance with the actual requirements.
Yes -> Step 6.
No -> Step 4.
4. Modify the peer-end clock configuration (cancel the master mode or change it to slave mode),
Yes -> End.
No -> Step 6.
5. Check whether the cable is connected as required.
Yes -> Step 8.
No -> Step 7.
6. Reconnect the cable, and check whether the alarm is cleared.
Yes -> End.
No -> Step 8.
4.10 199005720 The CDM data was covered

l
l
l
l

Name: The CDM data was covered
4-11
SJ-20140527134643-015|2015-03-31 (R1.1)
This notification is raised if a board detects that the information stored in the right and left CDMs is
different, and then it synchronizes the information.
Notification Cause
The information stored in the right and left CDMs is different.
Impact
None.
Action
4.11 199005977 Running version not match with

database configuration
l
l
l
l

Name: Running version not match with database configuration
When a board is powered on, or the configurations of a module or a unit change, the information of
the operating version and the version information configured in the version library are compared. If
the information is different, this notification is raised.
Notification Cause
l
The version file is not configured correctly.
The expected version is not activated.
Impact
The operating version of the board is not consistent with the version information configured in the
database, so some functions may be unavailable or abnormal.
Action
4-12
SJ-20140527134643-015|2015-03-31 (R1.1)
4.12 199005982 Patch operation failed

l
l
l
l

Name: Patch operation failed
This notification is raised if an operation on the hotfix fails.
Notification Cause
Operations on the hotfix fail.
Impact
The hot patch fails to operate properly.
Action
4.13 199005983 Write back version information

l
l
l
l

Name: Write back version information
This notification is raised if the operating version is saved to a storage device in file format from the
peer end or the memory after the board is powered on for five minutes.
Notification Cause
l
The version write-back starts.
The version write-back ends successfully.
The version write-back ends but failed.
4-13
SJ-20140527134643-015|2015-03-31 (R1.1)
Impact
If the version write-back fails, the device may fail to be started after it is shut down.
Action
4.14 199005984 Check version information

l
l
l
l

Name: Check version information
This notification is raised if the version file information of the board is consistent with that configured
in the database.
Notification Cause
l
The version check starts.
The version is checked successfully.
The version check failed.
Impact
None.
Action
4.15 199005985 Synchronize version information

l
l
l
l

Name: Synchronize version information
4-14
SJ-20140527134643-015|2015-03-31 (R1.1)
This notification is raised when the version files on the active and standby boards are synchronized.
Notification Cause
l
The version synchronization begins.
The version synchronization ends successfully.
The version is being synchronizing.
The version synchronization ends, but the peer board may be offline.
The version synchronization ends, but the database fails to be queried.
The version synchronization ends but failed.
Impact
When the active/standby board fails to synchronize version files, the version files of the active/standby
board may be inconsistent with each other or incomplete. In this case, the system has potential risks.
Action
4.16 199006720 Environment monitoring board is

powered on or reset
l
l
l
l

Name: Environment monitoring board is powered on or reset
This notification is raised if the environment monitoring board is powered on successfully, or it
is reset successfully.
Notification Cause
The environment monitoring board is powered on successfully, or it is reset successfully.
Impact
None.
4-15
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
4.17 199007232 Poor board recover

l
l
l
l

Name: Poor board recover
Notificationm type: Equipment alarm
This notification is reported by a switching board. The NE periodically compares the communication
capability of the left and the right switching boards. If the two boards differ greatly in that, the board
with poorer communication capability will be restarted for recovery and the notification will be reported.
Notification Cause
l
1The switching board has two or more faulty slots than its partner board.
The stack port of the switching board is faulty, including the following two cases:
When the switching board is a media plane board with poorer communication capability.
When the switching board is a control plane board (not distinguished as active or standby)
with poorer communication capability.
Impact
The shelf where the faulty switching board is located has only one normal switching board. Thus
redundancy cannot be implemented, the intra-shelf and inter-shelf communication capabilities and
the system reliability are reduced, and services may be affected.
Action
1. After the board is powered on successfully, check whether the following alarms are reported:
199007168 Port trunk failed
199007174 Connect port loopback
Yes -> Step 2.
No -> Step 3.
2. Handle relevant alarms, and check whether the alarms are reported again.
Yes -> Step 3.
No -> End.
4-16
SJ-20140527134643-015|2015-03-31 (R1.1)
4.18 199008000 Failed to load data after the node is

powered on
l
l
l
l

Name: Failed to load data after the node is powered on
When the board is powered on, the data on the disk needs to be loaded to the real-time memory
database. If the data fails to be loaded, this alarm is raised.
Notification Cause
l
The data on the local disk or the FLASH memory is lost.
The data on the local disk or the FLASH memory is damaged.
Impact
l
The board may fail to be powered on.
Some configurations may be lost, and thus services may be affected.
Action
1. Check whether there are alarms about file system failure or disk exception on the faulty board.
199005633 File system is abnormal
199005800 Hard disk offline
199005632 The hard disk used-rate is over threshold
Yes -> Step 2.
No -> Step 3.
2. After the related alarms are cleared, run the SET NORMALRESET command to reset the board
in accordance with "Rack number", "Shelf number", "Slot number", and "CPU number" in the
alarm information. Check whether the alarm is reported again.
Yes -> Step 3.
No -> End.
4-17
SJ-20140527134643-015|2015-03-31 (R1.1)
4.19 199008007 Database failed to save data

l
l
l
l

Name: Database failed to save data
When the real-time memory database saves all data to the disk, the following operations are involved:
l
Memory operation.
Writing operations for the active and standby saving paths on the active board (this board).
Writing operations for the active and standby saving paths on the standby board.
If an error occurs during the above operations, this alarm is raised. In the additional alarm information,
the saving results are provided.
Notification Cause
l
The board's database is processing a saving task.
The version of the board is being updated, and thus data cannot be saved.
The storage space on the hard disk or the FLASH memory is insufficient.
The hard disk or FLASH memory is not formatted or is damaged.
Insufficient database space.
Impact
l
If the failure reason is "Saving Forbidden", it does not affect system operation. It is only a prompt
during version updating.
If the failure reason is "Active Saving Directory Operation Failure", or "Standby Saving Directory
Operation Failure", it does not affect system operation. However, the backup data is only saved
on the board, which cannot guarantee high availability.
If the failure reason is "Active and Standby Saving Directory Operation Failure", the backup fails.
If the board is reset, there is no backup data, and therefore the configurations may be lost and
the board may fail to be powered on.
For other reasons that cause saving failure, the data that was backed up to the local disk is not
affected. However, the memory data and the backup data may be different. If the board is
reset, when it reads the backup data, some configurations performed after the data was backed
up may be lost.
Action
4-18
SJ-20140527134643-015|2015-03-31 (R1.1)
Handle the fault in accordance with "Active board saving result" and "Standby board saving result" in
the alarm information and detailed failure cause.
1. If the failure cause is "IO is busy", it indicates that there is a data-saving task running on the
board, so that the data-saving request is not accepted.
a. Check whether the network management system is initiating a data-saving operation.
Yes -> Step 1.2.
No -> Step 1.3.
b. Wait for a period of time, and then try to save data in the disk again. Check whether this alarm
still persists.
Yes -> Perform step 1.2 again. If the alarm still exists, go to step 7.
No -> Step 1.4.
c.
Wait for a while, and check whether the alarm is reported again.
Yes -> Step 7.
No -> Step 1.4.
d. If the latest data-saving operation is successful, end alarm handling.

2. If the failure cause is "IO forbid saving", it indicates that the board version is being upgraded, and
processing data-saving requests are disabled.
a. Check whether board version upgrade is in progress.
Yes -> Step 2.2.
No -> Step 7.
b. Check whether an operator initiates data-saving operation from the network management system.
Yes -> Step 2.3.
No -> The board triggers data saving, which has no impact on the system. It is a prompt for
the front end status. End alarm handling.
c.
After version upgrade is completed, save data in the disk again, and then check whether the
alarm is reported.
Yes -> Step 7.
No -> End.
3. If the failure cause is "save database failed in both master and slave path", it indicates that
some files may be damaged, the storage media are not formatted or damaged, or the space is
insufficient.
a. Check whether the faulty board reports alarms about file system failure, insufficient disk space,
or disk damage. The related alarms are as follows:
Yes -> Step 3.2.
No -> Step 7.
b. After the related alarms are cleared, save data to the disk again, and check whether the alarm
is reported again.
4-19
SJ-20140527134643-015|2015-03-31 (R1.1)
Yes -> Step 7.

No -> End.
4. If the failure cause is "save database failed in master path" or "save database failed in slave
path", it indicates that a failure occurs when files are written to the master path or slave path of
the storage media on the board, because some files are damaged, storage media are damaged,
or disk space is insufficient.
a. Check whether the faulty board reports alarms about file system failure, insufficient disk space,
or disk damage. The related alarm is as follows:
Yes -> Step 4.2.
No -> Step 7.
is reported again.
Yes -> Step 7.
No -> End.
5. If the failure cause is "fail to malloc lpmssaveinfo" or "fail to malloc memory for saving delay-save
req info", it indicates that the database space is insufficient.
a. Check whether the alarm-corresponding board reports alarms about insufficient memory. The
related alarms are as follows:
199003584 Memory insufficient alarm
199010048 Insufficient memory of database
Yes -> Step 5.2.
No -> Step 7.
is reported again.
Yes -> Step 7.
No -> End.
6. For other failure causes, go to step 7.
4.20 199008769 Failed to synchronize data between

nodes
l
l
l

Name: Failed to synchronize data between nodes
4-20
SJ-20140527134643-015|2015-03-31 (R1.1)
If the configuration in the memory of the main control node (the OMP in the NE) changes, data
synchronization between the main control node and downstream nodes (modules and units managed
by the OMP) is triggered. If the synchronization fails, this alarm is raised.
Notification Cause
l
Versions of different nodes are different.
The communication between nodes is abnormal.
Impact
If the data in memory of different nodes is different, the upper level services may be affected.
Action
1. Check whether the following alarm exists.
Yes -> Step 2.
No -> Step 3.
2. After the related alarm is cleared, check whether this alarm persists.
Yes -> Step 3.
No -> End.
3. Check whether the software version of the board is correct.
Yes -> Step 5.
No -> Step 4.
4. Reset the faulty board. Wait for five to ten minutes, and check whether the alarm persists.
Yes -> Step 5.
No -> End.
4.21 199008770 Failed to update node data

l
l
l
l

Name: Failed to update node data
4-21
SJ-20140527134643-015|2015-03-31 (R1.1)
If the configuration in the memory of the main control node (the OMP in the NE) changes, data
synchronization between the main control node and downstream nodes (modules and units managed
by the OMP) is triggered. After the synchronization completes, the downstream node that receives
data needs to update the local data. If data synchronization fails, this alarm is raised.
Notification Cause
l
Versions of different nodes are different.
Insufficient database space.
Impact
If the data in memory of different nodes is different, the upper level services may be affected.
Action
1. Check whether any of the following alarm exists.
199010048 Insufficient memory of database
Yes -> Step 2.
No -> Step 3.
2. After the related alarm is cleared, check whether this alarm persists.
Yes -> Step 3.
No -> End.
3. Check whether the software version of the board is correct.
Yes -> Step 5.
No -> Step 4.
4. Reset the faulty board. Wait for five to ten minutes, and check whether the alarm persists.
Yes -> Step 5.
No -> End.
4.22 199010048 Insufficient memory of database

l
l
l
l

Name: Insufficient memory of database
4-22
SJ-20140527134643-015|2015-03-31 (R1.1)
During the operation of the board's real-time database, it requests for dynamic memory with the
increase of the user number. During this process, if the memory usage reaches the threshold, this
alarm is raised.
Notification Cause
l
The physical memory of the board is insufficient.
The database space is not enough.
Impact
Action
1. Check whether the following alarm exists.
Yes -> Step 2.
No -> Step 3.
2. After the related alarm is cleared, check whether this alarm is reported again.
Yes -> Step 3.
No -> End.
4.23 199011073 LAPD failed to initialize HDLC

Alarm Information
Code:
199011073
Name:
LAPD failed to initialize HDLC
Severity:
Minor
Type:
Equipment Alarm
Alarm Description
This alarm is raised if the LAPD fails to initialize the HDLC chip.
Probable Cause
l
The HDLC chip is faulty.
The port of the board is not set to E1 or T1.

4-23
SJ-20140527134643-015|2015-03-31 (R1.1)
System Impact
The LAPD fails to be powered on.
Handling Suggestion
1. Query the reference object "Board" of the object "Unit" in accordance with the "Subsystem ID"
and "Unit number" in the alarm information, and check whether the "Port Type (ExtPortType)"
parameter is configured to T1 or E1.
Yes -> Step 2.
No -> Step 3.
2. Replace the board(refer to Front Boards and Rear Boards Replacement), and then check
Yes -> Step 4.
No -> End.
3. Configure the "Port Type (ExtPortType)" parameter of the "Board" to E1 or T1 as required,
wait for five minutes after the board is automatically rebooted, and then check whether the
Yes -> Step 4.
No -> End.
4.24 199011333 MTP2 failed to initialize HDLC

Alarm Information
Code:
199011333
Name:
MTP2 failed to initialize HDLC
Severity:
Minor
Type:
Equipment Alarm
Alarm Description
This alarm is raised if the MTP2 fails to initialize the HDLC chip.
Probable Cause
l
The port of the board is not set to E1 or T1.
System Impact
The MTP2 link fails to be powered on.
4-24
SJ-20140527134643-015|2015-03-31 (R1.1)
Handling Suggestion
1. Query the reference object "Board" of the object "Unit" in accordance with the "Subsystem ID"
and "Unit number" in the alarm information, and check whether the "Port Type (ExtPortType)"
parameter is configured to T1 or E1.
Yes -> Step 2.
No -> Step 3.
2. Replace the board(refer to Front Boards and Rear Boards Replacement), and then check
Yes -> Step 4.
No -> End.
3. Configure the "Port Type (ExtPortType)" parameter of the "Board" to E1 or T1 as required,
wait for five minutes after the board is automatically rebooted, and then check whether the
Yes -> Step 4.
No -> End.
4.25 199013890 Sigtran error message received

l
l
l
l

Name: Sigtran error message received
This notification is raised if the local end receives a Sigtran error message transmitted by the peer end.
Notification Cause
The local end receives a Sigtran error message transmitted by the peer end.
Impact
Action
4-25
SJ-20140527134643-015|2015-03-31 (R1.1)
4.26 199014145 Restart the association

l
l
l
l

Name: Restart the association
This notification is raised if the peer end sends a request to establish a link for the association and
the local association restarts.
Notification Cause
The peer end (SCTP client) sends a link reestablishment request after it detects that the association
is broken.
Impact
In normal cases, this alarm has no influence on the system. In the worst case, the association is
disconnected transiently. It can be recovered immediately.
Action
1. Query the object "Association (SctpAssociation)", and check whether the "Delayack interval
(DelayACk)" parameter is configured as required.
Yes -> Step 3.
No -> Step 2.
2. Modify the configuration of the "Delayack interval (DelayACk)" parameter as required. Wait for 10
minute, and check whether the notification persists.
Yes -> Step 3.
No -> End.
3. Contact the maintenance personnel of the peer end, and check whether the SCTP configuration
is consistent with the real requirement.
Yes -> Step 5.
No -> End.
4. Ask the maintenance personnel of the peer end to modify the configuration, wait for 10 minutes,
and then check whether the notification persists.
Yes -> Step 5.
No -> End.
Yes -> Step 6.
No -> Step 7.
6. Ask the maintenance personnel of the peer end to resolve the fault, wait for 10 minutes, and
then check whether the notification persists.
4-26
SJ-20140527134643-015|2015-03-31 (R1.1)
Yes -> Step 7.

No -> End.
4.27 199014150 Association config error

l
l
l
l

Name: Association config error
This notification is raised if the stream configuration of an association is incorrect or the configuration
of an association is not complete.
Notification Cause
l
The number of streams of an association is not configured correctly.
The configuration of an association is not complete (the association is not configured on the
SCTP layer).
Impact
Associations cannot be established and services cannot be carried.
Action
1. Query the "Association" object in accordance with the alarm object, and check whether the
object is configured.
Yes -> Step 3.
No -> Step 2.
2. Configure the "Association" object. Wait for one minute, and check whether the notification
persists.
Yes -> Step 3.
No -> End.
3. Check whether the "The number of inbound stream" and "The number of outbound stream"
parameters of the "Association" object are valid (based on "SCTP association bearer protocol
type", the valid value for an M2PA association is 2, 2-17 for an M2UA/SUA/M3UA/IUA
association, and 1-17 for other associations).
Yes -> Step 5.
No -> Step 4.
4-27
SJ-20140527134643-015|2015-03-31 (R1.1)
4. Modify the "The number of inbound stream" and "The number of outbound stream" parameters.
Wait for one minute, and check whether the notification persists.
Yes -> Step 5.
No -> End.
4.28 199014152 Dynamic association config error

l
l
l
l

Name: Dynamic association config error
This notification is raised if the local end detects that a dynamic association is not configured correctly.
Notification Cause
The configuration of a dynamic association is not complete (the association is not configured on the
SCTP layer) or a dynamic association is configured incorrectly.
Impact
The dynamic association cannot be established and services cannot be carried.
Action
1. Query the "Dynamic Association" object in accordance with the alarm object, and check whether
the object is configured.
Yes -> Step 3.
No -> Step 2.
2. Configure the "Dynamic Association" object. Wait for one minute, and check whether the
Yes -> Step 3.
No -> End.
3. Query the "Dynamic Association" configuration, and check whether the local IP and port are
wrong.
Yes -> Step 4.
No -> Step 5.
4. Modify the local IP address and port configuration. Wait for one minute, and check whether the
Yes -> Step 5.
4-28
SJ-20140527134643-015|2015-03-31 (R1.1)
No -> End.
5. Query the "Dynamic Association" object in accordance with the alarm object, and check whether
the "SCTP association bearer protocol type" parameter is valid.
Yes -> Step 7.
No -> Step 6.
6. Modify the "SCTP association bearer protocol type" parameter as required. Wait for one minute,
and check whether the notification persists.
Yes -> Step 7.
No -> End.
4.29 199017992 Protocol state of aggregation port

member interface is down
Alarm Information
Code:
199017992
Name:
Protocol state of aggregation port member interface is down
Severity:
Minor
Type:
Alarm Description
This notification is raised if the protocol status of a member port under the aggregation port in
802.3AD mode changes from UP to DOWN.
Probable Cause
l
The configurations on both ends of the aggregation port are not consistent.
The channel of the aggregation port or a member port is abnormal.
System Impact
The load on other member ports of the aggregation port may be increased. If the aggregation port
has only one member port, the corresponding upper-layer services may be interrupted.
4-29
SJ-20140527134643-015|2015-03-31 (R1.1)
Handling Suggestion
1. Check whether "Channel-group ID" and "Port Quintuplet" are the same with the actual
requirements ("Port Quintuplet" belongs to "Channel-group ID").
Yes -> Step 3.
No -> Step 2.
2. Modify the "Bounding mode of member port (BoundMode)" parameter of the "Channel Member
Port Object ID(EthChMember)" object based on actual requirements.
Sub Interface Object ID (EthChannel)" parent object in accordance with alarm object.
Yes -> Step 6.
No -> Step 4.
Sub Interface Object ID (EthChannel)" parent object or the "Bounding mode of member port
(BoundMode)" parameter of the "Channel Member Port Object ID(EthChMember)" object in
accordance with actual requirements and alarm object. Run the QRY LACP INTERNAL
command to check whether "Is Active" is "Active member port" in accordance with "Channel-group
ID" in the alarm information.
Yes -> End.
No -> Step 5.
5. Contact the maintenance personnel of the peer device to check whether related alarms exist and
the aggregation port of the peer device is configured correctly.
Yes -> Step 6.
No -> Step 7.
6. After the fault is removed by peer maintenance personnel, run the QRY LACP INTERNAL
command to check whether "Is Active" is "Active member port".
Yes -> End.
No -> Step 7.
4.30 199017993 Failed to add IPv6 dynamic route

Alarm Information
Code:
199017993
Name:
Failed to add IPv6 route
Severity:
Minor
Type:
Processing alarm
4-30
SJ-20140527134643-015|2015-03-31 (R1.1)
Alarm Description
This notification is raised if IPv6 routes received through the dynamic route protocol notification fail
to be added to the NE, routes reallocated by the IPv6 static route fail to be added, or routes in the
OSPFV3 domain fail to be added to the IPv6 interface.
Probable Cause
l
The number of routes exceeds the maximum number.

SBC 1000
iBSC 1000
HLR 1000
IMS 1000
MSC_CS 1000
RNC 1000
uMAC 2048
MGW 1000
BSC 1000
PDS 1000
SIU 1000
AG 1000
CEMC 1000
The local NE is not configured correctly.
System Impact
Services using the IPv6 address prefix may be interrupted.
Handling Suggestion
1. Check whether "IPv6 route prefix" in the notification information is the required route prefix.
Yes -> Step 2.
No -> End.
2. Query the "Static Route(IPV6)", "IPV6 Route Redistribute", and "OSPFv3 Interface Configuration"
objects to obtain IPv6 routing information, and check whether IPv6 routing information is
configured as required.
Yes -> Step 4.
No -> Step 3.
3. Modify the IPv6 routing information of the "Static Route(IPV6)", "IPV6 Route Redistribute",
and "OSPFv3 Interface Configuration" objects as required, and check whether the following
notification exists:
199017993 Failed to add IPv6 dynamic route
Yes -> Step 4.
No -> End.
4. Contact the maintenance personnel of the peer end to check whether the IPv6 route configuration
of the peer end meets the real requirements.
4-31
SJ-20140527134643-015|2015-03-31 (R1.1)
Yes -> Step 6.

No -> Step 5.
5. Wait for the maintenance personnel of the peer end to modify the configuration, and then check
whether the following notification exists:
199017993 Failed to add IPv6 dynamic route
Yes -> Step 6.
No -> End.
4.31 199018241 TCP connection closed

l
l
l
l

Name: TCP connection closed
This notification is raised if the status of the TCP link changes from establish to close or the local end
that operates as the TCP client fails to establish a link for a long time.
Notification Cause
l
The hardware of the board is faulty.
The TCP channels on both ends are faulty.
The configurations of both ends are inconsistent.
Impact
The TCP connection is disconnected, and services may be affected.
Action
1. Query the "Static Route(IPV4) (StaticRoute)" object in accordance with the "Peer IP Address" in
notification information, and check the "Route nexthop address (NextHopIpAddr)" parameter.
And you can also run the QRY RPU ROUTE command to query the routing configuration, and
check whether routing information is configured as required.
Yes -> Step 3.
No -> Step 2.
2. 2. Modify the settings of the "Static Route(IPV4) (StaticRoute)" object as required, and then
Yes -> Step 3.
No -> End.
4-32
SJ-20140527134643-015|2015-03-31 (R1.1)
3. Contact the maintenance personnel of the peer end, and check whether the related configuration
of the peer end is consistent with the real requirement.
Yes -> Step 4.
No -> Step 5.
4. After the maintenance personnel of the peer end modifies the configuration as required, check
Yes -> Step 5.
No -> End.
"Peer IP Address" in the notification, determine logical information (Port Quintuplet) and physical
information (rack-shelf-slot) of the corresponding egress interface board. Determine logical
information and physical information of the ingress interface board in accordance with the local IP
address in the notification and actual routing requirements of the peer end, and check whether
the board and related ingress and egress interface boards have any of the following alarms:
Yes -> Step 6.
No -> Step 7.
6. Handles the alarms and check whether the notification persists.
Yes -> Step 7.
No -> End.
7. Check whether the Reason parameter in the notification is "SYN waiting timeout".
Yes -> Step 10.
No -> Step 8.
8. Check whether the Reason parameter in the alarm information is "retransmission timeout".
Yes -> Step 10.
No -> Step 9.
9. Check whether the Reason parameter in the alarm information is "received RST".
Yes -> Step 11.
No -> Step 13.
10. Ping 1200 packets in accordance with the "Destination address" in notification information, and
check whether packet loss occurs.
Yes -> Step 11.
No -> Step 13.
Yes -> Step 12.
No -> Step 13.
Yes -> Step 13.
No -> End.
4-33
SJ-20140527134643-015|2015-03-31 (R1.1)
4.32 199018500 The peer IP address is the same as the

local IP address of the PPP link
l
l
l
l

Name: The peer IP address is the same as the local IP address of the PPP link
This alarm is raised if the IP address carried in the PPP negotiation message received by the local
end is the same as the local IP address.
Notification Cause
l
The local IP address of the PPPlink is the same as that of the peer end.
A loopback is set for the local port.
Impact
This link cannot communicate with the peer end properly, and the link cannot be used for the
transmission of the service data.
Action
1. Query "IP Interface Object ID of ML-PPP (MlpppTpIpIntf)" and "IP Interface Object ID of PPP
(PppIpIntf)"in accordance with the alarm object, and check whether "Local IP Address (IPv4)
(IpAddress)" meet actual requirements.
Yes -> Step 3.
No -> Step 2.
2. Modify "Local IP Address (IPv4) (IpAddress)" in accordance with actual requirements, wait for
one minute, and check whether this notification persists.
Yes -> Step 5.
No -> End.
3. Contact the maintenance personnel of the peer device to check whether the peer configuration is
the same with the actual requirement.
Yes -> Step 5.
No -> Step 4.
4. Contact the maintenance personnel of the peer device to modify the configuration as required,
wait for one minute, and then check whether the notification persists.
Yes -> Step 5.
No -> End.
5. Query "Logical E1 (LogicalE1)" or "Logical T1 (LogicalT1)" used by the "PPP Link of ML-PPP
Group (MpLink)" object, A1010and query the corresponding trunk E1/T1 object.
4-34
SJ-20140527134643-015|2015-03-31 (R1.1)
6. A2010 Run the START DTMcommand in accordance with the trunk E1/T1 object obtained in Step
5 to check whether the local loopback test is configured on the trunk.
Yes -> Step 7.
No -> Step 8.
7. A2011Run the START DTM command to cancel the loopback test in accordance with the trunk
E1/T1 object obtained in Step 5. Wait for one minute, and then check whether the notification
persists.
Yes -> Step 8.
No -> End.
8. Check whether the cable on the corresponding port is looped back in accordance with the trunk
number obtained in Step 5.
Yes -> Step 9.
No -> Step 10.
9. Cancel the loopback test function, wait for one minute, and check whether the notification persists.
Yes -> Step 10.
No -> End.
4.33 199018501 Fail to create the HDLC channel

l
l
l
l

Name: Fail to create the HDLC channel
This notification is raised if the HDLCchip of the board is faulty when the HDLC channel is configured.
Notification Cause
Impact
This link cannot be used for the transmission of the service data.
4-35
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
1. Wait for three minutes, and check whether the following notification exists:
199018504 Succeed to create the HDLC channel
Yes -> End.
No -> Step 2.
2. Run the SET NORMALRESETcommand to reset the board in accordance with the "Rack
number", "Shelf number", "Slot number", and "CPU number" in the alarm information. When the
board operates properly for three minutes, check whether the notification persists.
Yes -> Step 3.
No -> End.
"Rack number", "Shelf number", "Slot number", and "CPU number" in the alarm information.
When the board operates properly for three minutes, check whether the notification persists.
Yes -> Step 9.
No -> End.
4.34 199018502 Fail to initialize the HDLC chip

Alarm Information
Code:
199018502
Name:
Fail to initialize the HDLC chip
Severity:
Minor
Type:
Processing alarm
Alarm Description
This notification is generated when the PPP fails to initialize the HDLC chip.
Probable Cause
The hardware of the HDLC chip is faulty.
System Impact
The PPP link fails to be created, so it cannot be used for service transmission.
4-36
SJ-20140527134643-015|2015-03-31 (R1.1)
Handling Suggestion
1. Run the SET NORMALRESETcommand to reset the board in accordance with the "Rack
number", "Shelf number", "Slot number", and "CPU number" in the alarm information. When the
board operates properly for three minutes, check whether the notification persists.
Yes -> Step 2.
No -> End.
"Rack number", "Shelf number", and "Slot number" in the alarm information. When the board
operates properly for three minutes, check whether the notification persists.
Yes -> Step 3.
No -> End.
4.35 199018504 Succeed to create the HDLC channel

l
l
l
l

Name: Succeed to create the HDLC channel
This notification is raised if the system tries to create an HDLC channel after a "fails to create a
HDLC channel" message is received.
Notification Cause
The system successfully creates an HDLC channel after a "fails to create a HDLC channel" message
is received.
Impact
None.
Action
4-37
SJ-20140527134643-015|2015-03-31 (R1.1)
4.36 199018753 The configuration of UID/HDLC/IPE1 in

database is wrong
Notification code:
199018753
Notification name:
The configuration of UID/HDLC/IPE1 in database is wrong
Notification severity:
Major
Notification type:
Processing alarm
This notification is generated when the IPoverE1 configuration is incorrect.
Notification Cause
The local IPoverE1 configuration is incorrect.
Impact
This configured link cannot be used for service data transmission.
Action
1. Check whether the Error reason of UID HDLC configuration parameter is set to IPOverE1 port
number error.
Yes -> Step 4.
No -> Step 2.
2. Check whether the Error reason of UID HDLC configuration parameter is set to Sub-unit does
not belong to UID or protocol stack.
Yes -> Step 6.
No -> Step 3.
3. Check whether the Error reason of UID HDLC configuration parameter is set to Error timeslots or
E1 number of HDLC.
Yes -> Step 7.
No -> Step 9.
4. Check whether the port number in notification information meets the real requirements.
Yes -> Step 9.
No -> Step 5.
5. Add the "PPP Link of ML-PPP Group" object or the "PPP Link" object as required. Wait for one
minute, and check whether the notification persists ("Port number" in the notification information
is the reconfigured port number).
Yes -> Step 2.
No -> End.
4-38
SJ-20140527134643-015|2015-03-31 (R1.1)
6. Check whether the "PPP Link of ML-PPP Group"/"PPP Link" object is configured as required
in accordance with the logical address (subsystem ID, module ID, unit ID, and sub-unit ID)
in the notification information and port number. Wait for one minute, and check whether the
Yes -> Step 3.
No -> End.
7. Query the "Logical E1" or "Logical T1" object that the "PPP Link of ML-PPP Group" object or the
"PPP Link" object references in accordance with the logical address (subsystem ID, module ID,
unit ID, and sub-unit ID) in the notification information and port number, and check whether the
trunk information is correct.
Yes -> Step 9.
No -> Step 8.
8. Modify the "Logical E1"/"Logical T1" object that the "PPP Link of ML-PPP Group" object or
the "PPP Link" object references as required. Wait for one minute, and check whether the
Yes -> Step 9.
No -> End.
4.37 199019777 APS switchover happens

l
l
l
l

Name: APS switchover happens
This notification is raised if the board detects APS switchover.
Notification Cause
1. The board is faulty or the APS port is faulty.
2. The peed end initiates a switchover operation.
3. The operating optical port is faulty and cannot recover within five minutes, which triggers APS
switchover.
4. APS switchover is initiated manually.
Impact
During APS switchover, the port is disconnected for 10 to 50 ms, and thus some packets are lost.
Services are affected slightly.
4-39
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
1. Check the operation and maintenance log, and check whether the network management system
has initiated an APS switchover command,refer to Obtaining Log-Service Data Files.
Yes -> End.
No -> Step 2.
2. Check whether the notification is frequently reported.
Yes -> Step 3.
No -> End.
4.38 199020554 Failed to add PPP route

l
l
l
l

Name: Failed to add PPP route
After the PPP link successfully negotiates the peer IP address, the NE adds a route automatically.
This alarm is raised if the route fails to be added.
Notification Cause
l
1. The number of routes exceeds the maximum number
For an RNC, there are eight next hops
For an MSC_CS, there are eight next hops
For an HLR, there are eight next hops
For an IMS, there are 5000 routes and four next hops
For a uMAC and a CEMC, there are 2048 routes and 32 next hops
For an iBSC, there are 2048 routes and eight next hops
For a BSC, there are 5120 routes and eight next hops
For an SIU, there are 5000 routes and eight next hops
The new route conflict with the routes injected reversely by the NE through IPsec.
The new route conflicts with an address route.
4-40
SJ-20140527134643-015|2015-03-31 (R1.1)
Impact
Services carried on this route may be affected.
Action
1. A1016 Query "IP Interface Object ID of ML-PPP (MlpppTpIpIntf)" and "IP Interface Object ID of
PPP (PppIpIntf)" of the object in accordance with "Port Quintuplet" in the alarm information, and
check "Local IP Address (IPv4) (IpAddress)" and "Peer IP Address(IPv4)(PeerIpAddress)" of the
"IP Interface Object ID of ML-PPP (MlpppTpIpIntf)" object or the "IP Interface Object ID of PPP
(PppIpIntf)" object to see whether "IP Address" in the notification message can be found.
Yes -> Step 2.
No -> Step 4.
2. Check whether the IP address of the local port meet the actual requirements.
Yes -> Step 4.
No -> Step 3.
3. Modify the local IP address in accordance with actual requirements, including "Local IP Address
(IPv4) (IpAddress)" and "Peer IP Address(IPv4)(PeerIpAddress)" of the "IP Interface Object ID of
ML-PPP (MlpppTpIpIntf)" object and the "IP Interface Object ID of PPP (PppIpIntf)" object. Wait
for one minute, and check whether this notification persists.
Yes -> Step 4.
No -> End.
4. Run the QRY RPU ROUTE command to check whether the IP address in the notification
message exists in the route information of the IPsec type.
Yes -> Step 9.
No -> Step 5.
5. Run the QRY RPU ROUTE command to check whether the route information is the same with
actual route information.
Yes -> Step 7.
No -> Step 6.
6. Modify "IP Interface Object ID of ML-PPP (MlpppTpIpIntf)" object and the "IP Interface Object
ID of PPP (PppIpIntf)" object, or "Static Route (IPV4) (StaticRoute)", wait for one minute, and
check whether the notification persists.
Yes -> Step 7.
No -> End.
meets the actual requirements.
Yes -> Step 9.
No -> Step 8.
8. After the peer maintenance personnel modifies the configuration as required, wait for one minute,
and then check whether the notification persists.
Yes -> Step 9.
No -> End.
4-41
SJ-20140527134643-015|2015-03-31 (R1.1)
4.39 199020571 Failed to perform offline configuration

Alarm Information
Code:
199020571
Name:
Failed to perform offline configuration
Severity:
Minor
Type:
Equipment Alarm
Alarm Description
This notification is raised if the board detects an incorrect IP configuration parameter.
Probable Cause
The IP configuration is incorrect.
System Impact
Handling Suggestion
4.40 199020802 An IP address conflicts with another

system on the subnet
l
l
l
l

Name: An IP address conflicts with another system on the subnet
This notification is raised if this board detects that IPv4 addresses in the IP subnet conflict with
each other.
4-42
SJ-20140527134643-015|2015-03-31 (R1.1)
Notification Cause
l
The IP address of the network interface of this board is incorrect.
IPv4 addresses in the IP subnet conflict with each other.
The Ethernet that is connected with the network interface of this board has a loopback.
Impact
Services corresponding to the conflicted IP address of this port are interrupted
Action
1. A1012 Query the "Ethernet Interface" object in accordance with "Port Quintuplet" in the
notification information#}, check "IP Address 1(IpAddr1)" of the child object "Ethernet IP Interface
(IPv4)(EthIpIntf)", and verify that the configured IPv4 address meet the actual requirements.
Yes -> Step 3.
No -> Step 2.
2. Modify the local IP address in accordance with actual requirements.
3. Contact the maintenance personnel of the peer device to check whether the configuration is the
same with the actual requirements.
Yes -> Step 5.
No -> Step 4.
4. Contact the maintenance personnel of the peer device to modify the IPv4 configuration as
required.
5. Contact the maintenance personnel of the peer device to check whether there is a loopback
in the network.
Yes -> Step 6.
No -> Step 7.
6. Contact the maintenance personnel of the peer device to resolve the faults, and end the handling.
4.41 199020803 A MAC address conflicts with another

system on the subnet
l
l
l
l

Name: A MAC address conflicts with another system on the subnet
4-43
SJ-20140527134643-015|2015-03-31 (R1.1)
This notification is raised if this board detects that the MAC addresses in the IP subnet conflict
with each other.
Notification Cause
l
The MAC address of the network interface of this board is incorrect.
The MAC addresses in the IP subnet conflict with each other.
Impact
Services corresponding to the port are interrupted
Action
1. A1012 Query the physical Ethernet interface object in the notification information in accordance
with "Port Quintuplet", check "Mac Address", and verify that the configured MAC address meet
the actual requirements.
Yes -> Step 3.
No -> Step 2.
2. Modify the local MAC address in accordance with actual requirements.
3. Contact the maintenance personnel of the peer device to check whether the MAC address is the
same with the actual requirements.
Yes -> Step 5.
No -> Step 4.
4. Contact the maintenance personnel of the peer device to modify the MAC configuration as
required.
5. Contact the maintenance personnel of the peer device to check whether there is a loopback
in the network.
Yes -> Step 6.
No -> Step 7.
6. Contact the maintenance personnel of the peer device to resolve the faults, and end the handling.
4.42 199020805 ARP detecting failed

Alarm Information
Code:
199020805
Name:
ARP detecting failed
Severity:
Minor
4-44
SJ-20140527134643-015|2015-03-31 (R1.1)
Type:
Alarm Description
When the ARP detection function "EthIpIntf.ArpDetectFlag" of the port is enabled, the port
sends ARP requests periodically. This notification is raised if no reply is received from the
peer end within the set period (the set period = parameter "Timeout Interval of one ARP
Detect procedure(ArpDetectTimeOut)" * parameter "Threshold of ARP-Detect-Fail times
reaching(ArpDetectFailTimes)" of "Ethernet IP Interface (IPv4)(EthIpIntf)" object).
Probable Cause
l
The Ethernet port is faulty.
The peer device gives no response to the ARP request.
The ARP detects that the channel corresponding to the IP address is faulty.
System Impact
Services carried on the channel corresponding to the IP address that fails in the ARP detection may
be interrupted.
Handling Suggestion
1. Check whether the local faulty port has any of the following alarms in accordance with "Rack
number", "Shelf number", "Slot number", and the port number contained in "Port Quintuplet" in
the alarm information:
Yes -> Step 2.
No -> Step 3.
2. Handle the alarms, and wait for a while (at least for a period as long as "Timeout Interval of
one ARP Detect procedure" * "Threshold of ARP-Detect-Fail times reaching", both of which
are parameters of the "Ethernet IP Interface (IPv4)" object). Query the "Ethernet IP Interface
(IPv4)" object in accordance with its parent object "Ethernet Interface", and check whether the
alarm persists.
Yes -> Step 3.
No -> End.
related alarms.
Yes -> Step 4.
No -> Step 5.
4. Ask the maintenance personnel of the peer end to handle the faults. Wait for a while (at
least for a period as long as "Timeout Interval of one ARP Detect procedure" * "Threshold of
ARP-Detect-Fail times reaching", both of which are parameters of the "Ethernet IP Interface
(IPv4)" object). Query the "Ethernet IP Interface (IPv4)" object in accordance with its parent
object "Ethernet Interface", and check whether the alarm persists.
Yes -> Step 5.
4-45
SJ-20140527134643-015|2015-03-31 (R1.1)
No -> End.
4.43 199020806 ARP detecting reply is different from

static ARP
Alarm Information
Code:
199020806
Name:
ARP detecting reply is different from static ARP
Severity:
Minor
Type:
Alarm Description
This notification is generated when the source MAC address in the ARP reply received from the
peer end is not consistent with the MAC in the local static ARP after the ARP detection function
"EthIpIntf.ArpDetectFlag" of the port is enabled,
Probable Cause
The MAC address of the peer end is not consistent with that in the local static ARP configuration.
System Impact
Services carried on the channel corresponding to the IP address that fails in the ARP detection may
be interrupted.
Handling Suggestion
1. Check whether the "Port Quintuplet" and "Request MAC address" in the notification meet the
Yes -> Step 3.
No -> Step 2.
2. Modify the "MAC address(MacAddress)" parameter of the "Static Arp(StaticArp)" object
as required. Wait for a period of time (the "Timeout Interval of one ARP Detect procedure
(ArpDetectTimeOut)" parameter * the "Threshold of ARP-Detect-Fail times reaching
(ArpDetectFailTimes)" parameter of the "Ethernet IP Interface (IPv4)(EthIpIntf)" object, the
"Ethernet IP Interface (IPv4)(EthIpIntf)" object can be obtained by [A1012] querying the Ethernet
interface object in accordance with the "Port Quintuplet" in the notification), and check whether
the notification persists.
Yes -> Step 3.
No -> End.
4-46
SJ-20140527134643-015|2015-03-31 (R1.1)
3. Contact the maintenance personnel of the peer device to check whether the configuration is
consistent with the actual requirements.
Yes -> Step 5.
No -> Step 4.
4. Ask the maintenance personnel of the peer device to modify the configuration as required.
Wait for a period of time (more than the value of the "Timeout Interval of one ARP Detect
procedure (ArpDetectTimeOut)" parameter * the "Threshold of ARP-Detect-Fail times reaching
(ArpDetectFailTimes)" parameter of the "Ethernet IP Interface (IPv4)(EthIpIntf)" object), and
Yes -> Step 5.
No -> End.
4.44 199021330 Failed to establish OSPFv2 neighbors

l
l
l
l

Name: Failed to establish OSPFv2 neighbors
This notification is raised if the OSPF neighbor fails to be established.
Notification Cause
The local OSPF configuration is inconsistent with that of the peer end.
Impact
The NE fails to learn the OSPF route normally, and services may be interrupted.
Action
4-47
SJ-20140527134643-015|2015-03-31 (R1.1)
1. Check whether the alarm type in notification information and the OSPF configuration meet the
real requirement.
Yes -> Step 6.
No -> Step 2.
If...
Then...
The Hello interval on the
Configuration query: A1021 Query the interface object in accordance
interface is not matched.
with "Interface IP address" in the alarm information, query the "OSPFv2

Interface Configuration" object that references the interface object, and
query the "Hello interval" parameter.
Dead-interval mismatch
on interface

query the "Dead interval" parameter.
E-bit of Hello packet
mismatch on interface

Network" object that has the same IP address and subnet mask, query
its parent object "OSPFv2 Area", and query its NSSA area parameters
(including "Whether to config default type-7 LSA for the nssa area",
"Metric type for the default type-7 LSA", "Whether to config Parameter
metric of the nssa command", "Metric for the default type-7 LSA",
"Whether to config Don't send summary LSA into the NSSA area",
and "Whether to config Don't redistribute EX-LSA to the NSSA area")
or STUB area parameters (including "Whether to config No-summary
option of the Stub command" and "Default-cost option value of the stub
command").
P-bit of Hello packet

its parent object "OSPFv2 Area", and query its NSSA area parameters
(including "Whether to config default type-7 LSA for the nssa area",
"Metric type for the default type-7 LSA", "Whether to config Parameter
metric of the nssa command", "Metric for the default type-7 LSA",
"Whether to config Don't send summary LSA into the NSSA area", and
"Whether to config Don't redistribute EX-LSA to the NSSA area").
Network mask of Hello
packet mismatch on
with "Interface IP address" in the alarm information, and obtain the first
interface
IP address and subnet mask of the interface.
OSPF version number
with "Interface IP address" in the alarm information, check whether the

"OSPFv2 Network" object that has the same IP address and subnet
mask exists.
4-48
SJ-20140527134643-015|2015-03-31 (R1.1)
Area mismatch number
on interface

the "OSPF instance Sequence" parameter of its parent object "OSPFv2
Instance" and the "OSPF area ID in IP address format" parameter of
its parent object "OSPFv2 Area".
Authentication type

query the "Enable authentication" parameter.
Simple plaintext
password mismatch
on interface

query the "Authentication key" parameter.
MD5 configuration
Configuration query: A1021Query the interface object in accordance

query the "MD5 key ID" and "MD5 key" parameters.
Router ID conflict
Configuration query: A1021Query the interface object in accordance

Network" object that has the same IP address and subnet mask,
query the "OSPF instance Sequence(InstanceId)" and "Router-id for
this OSPF process(RouteId)" parameter of its parent object "OSPFv2
Instance(Ospfv2Inst)".
2. Modify the configuration as required.

[The Hello interval on the interface is not matched.]
Configuration modification: Modify the "Hello interval" parameter of the "OSPFv2 Interface
Configuration" object as required.
[Dead-interval mismatch on interface]
Configuration modification: Modify the "Dead interval" parameter of the "OSPFv2 Interface
[E-bit of Hello packet mismatch on interface]
Configuration modification: Modify the "Whether to config stub command" or "Whether to config
nssa command" parameter of the "OSPFv2 Area" object as required.
[P-bit of Hello packet mismatch on interface]
Configuration modification: Modify the "Whether to config nssa command" parameter of the
"OSPFv2 Area" object as required.
[Network mask of Hello packet mismatch on interface]
Configuration modification: Query the "Ethernet IP Interface (IPv4)" object referenced by the
"OSPFv2 Interface Configuration" object, and modify the "IP Address 1" and "Subnet Mask
Length 1" parameters as required.
[OSPF version number mismatch on interface]
4-49
SJ-20140527134643-015|2015-03-31 (R1.1)
Configuration modification: Modify the "OSPF instance Sequence" parameter of the "OSPFv2
Instance" object as required.
[Area mismatch number on interface]
Configuration modification: Modify the "OSPF area ID in IP address format" parameter of the
"OSPFv2 Area" object as required.
[Authentication type mismatch on interface]
Configuration modification: Modify the "Enable authentication" parameter of the "OSPFv2
Interface Configuration" object as required.
[Simple plaintext password mismatch on interface]
Configuration modification: Modify the "Authentication key" parameter of the "OSPFv2 Interface
[MD5 configuration mismatch on interface]
Configuration modification: Modify the "MD5 key ID" and "MD5 key(Md5Key)" parameters of the
"OSPFv2 Interface Configuration" object as required.
[Router ID conflict]
Configuration modification: Modify the "Router-id for this OSPF process" parameter of the
"OSPFv2 Instance" object as required.
3. Modify the "MD5 key ID" and "MD5 key(Md5Key)" parameters of the "OSPFv2 Interface
Configuration" object, and check whether the status of all the neighbors is "FULL".
Yes -> End.
No -> Step 4.
4. Contact the maintenance personnel of the peer end for the OSPF neighbors which are not in
"FULL" status to check whether the OSPF configuration meets the actual requirements.
Yes -> Step 6.
No -> Step 5.
5. Ask the maintenance personnel of the peer end to modify the OSPF configuration. Modify the
"Router-id for this OSPF process" parameter of the "OSPFv2 Instance" object as required, and
check whether the status of all the neighbors is "FULL".
Yes -> End.
No -> Step 6.
4.45 199021837 Fail to add dynamic route

l
l
l
l

Name: Fail to add dynamic route
4-50
SJ-20140527134643-015|2015-03-31 (R1.1)
This notification is raised if items fail to be added to the routing tables of the NE.
Notification Cause
The number of IPv4 routes exceeds the maximum number supported by the NE.
iBSC 5000
RNC 5000
uMAC 2048
PDS 2048
AG 5000
Impact
New dynamic routes are unavailable.
Action
1. Run the QRY RPU ROUTE command to check whether the routing entries reach the threshold.
Yes -> Step 2.
No -> Step 3.
2. Confirm whether any routes in the IPv4 routing table can be deleted in accordance with the actual
networking requirements.
Yes -> Step 3.
No -> Step 5.
3. Delete unwanted routing entries as required (delete records of the "Static
Route(IPV4)(StaticRoute)" object), add new routes (add records of the "Static
Route(IPV4)(StaticRoute)" object), and check whether the alarm is cleared.
Yes -> End.
No -> Step 4.
4. Modify the "IP address (SummaryIpNet)" and "Subnetwork mask length (SummaryNetMaskLen)"
parameters of the "OSPFv2 Instance Summary Information(Ospfv2Summary)" object, summarize
the routes of other routing protocols that are being re-allocated to the OSPF to reduce the number
of LSAs, and check whether the alarm is cleared.
Yes -> End.
No -> Step 5.
4.46 199028233 Failed to establish OSPFv3 neighbors

l
l

Name: Failed to establish OSPFv3 neighbors
4-51
SJ-20140527134643-015|2015-03-31 (R1.1)
l
l

This notification is raised if the OSPF neighbor fails to be established.
Notification Cause
The local OSPFv3 configuration is inconsistent with that of the peer end.
Impact
The NE fails to learn the OSPFv3 route, and services may be interrupted.
Action
1. Check whether the alarm type in notification information and the OSPFv3 configuration meet
the real requirement.
Yes -> Step 6.
No -> Step 2.
If...
Then...
The Hello interval on the interface
Configuration query: [A1021]Query the interface object
is not matched.
in accordance with "Interface IP address" in the alarm

information, query the "OSPFv3 Interface Configuration"
object that references the interface object, and query the
"Hello interval" parameter.
Dead-interval mismatch on
interface

"Dead interval" parameter.
E-bit of Hello packet mismatch on interface
information, and then query the "OSPFv3 Interface
Configuration" object that references the interface object.
Query the "OSPF area ID in IP address format" and "OSPF
instance Sequence on the interface" parameters, and
query the "OSPFv3 Area" object in accordance with these
parameters. Query the STUB area parameters "Whether
to config No-summary option of the Stub command." And
"Default-cost option value of the stub command".
Version numbers do not match on interfaces
4-52
SJ-20140527134643-015|2015-03-31 (R1.1)

"OSPF instance Sequence on the interface" parameter.
Check whether the corresponding "OSPFv3 Instance"
object exists.
Interface Area IDs do not match
"OSPF area ID in IP address format" parameter.
Interface instance IDs do not match on interfaces
"OSPF instance Sequence on the interface" parameter.
Router ID conflict

information query the "OSPFv3 Interface Configuration"
"Router ID" parameter.
2. Modify the configuration as required.

If...
Then...
The Hello interval on the interface
Configuration modification: Modify the "Hello interval"
is not matched.
parameter of the "OSPFv3 Interface Configuration" object

as required.
Dead-interval mismatch on
Configuration modification: Modify the "Dead interval"
interface

as required.
E-bit of Hello packet mismatch on interface
Configuration modification: Modify the "Whether to config
stub command" parameter of the "OSPFv3 Area" object
as required.
Version numbers do not match on interfaces
Configuration modification: Modify the "OSPF3 process
Sequence" parameter of the "OSPFv3 Interface
Interface Area IDs do not match
4-53
SJ-20140527134643-015|2015-03-31 (R1.1)
Configuration modification: Modify the "OSPF area ID

in IP address format" parameter of the "OSPFv3 Area"
object as required.
Interface instance IDs do not match on interfaces
Configuration modification: Modify the "OSPF instance
Sequence on the interface" parameter of the "OSPFv3
Interface Configuration" object as required.
Router ID conflict
Configuration modification: Modify the "Router ID"

as required.
3. Check whether the status of all the neighbors is "FULL" in accordance with the "OSPFv3 Interface
Configuration" object.
Yes -> End.
No -> Step 4.
4. Contact the maintenance personnel of the peer end corresponding to the OSPFv3 neighbors who
are not in FULL status to check whether the OSPFv3 configuration meets the real requirements.
Yes -> Step 6.
No -> Step 5.
5. Ask the maintenance personnel of the peer end to modify the OSPFv3 configuration. Check
whether the status of all the neighbors is "FULL" in accordance with the "OSPFv3 Interface
Configuration" object.
Yes -> End.
No -> Step 6.
4.47 199030528 The result of starting PD task

l
l
l
l

Name: The result of starting PD task
This notification is raised if the path detection function fails to be enabled.
Notification Cause
l
Parameters are configured incorrectly.
The number of path detection tasks has reached the maximum number.
4-54
SJ-20140527134643-015|2015-03-31 (R1.1)
Impact
The PD task fails to be started, but services are not affected.
Action
1. Check whether "Start Result" in the notification information is "start success".
Yes -> End.
No -> Step 2.
2. Check whether "Start Result" in the notification information shows any of the following:
"task exist"
"nexthop error"
"pkt length error"
"send pkt num error"
"time error"
"TTL set error"
"PD request type error"
"packet type error"
"timeout error"
"packet length larger than mtu"
"source ip invalid"
"DSCP parameter error"
"destination cannot be source board"
"IP family not same"
"direct route can't assign nexthop"
Yes -> Step 7.
No -> Step 3.
3. Check whether "Start Result" in the notification information is "route look up error".
Yes -> Step 4.
No -> Step 5.
4. Modify the "Static Route(IPV4) (StaticRoute)" object configuration as required, and then check
Yes -> Step 8.
No -> End.
5. Check whether "Start Result" in the notification information is "out port error".
Yes -> Step 6.
No -> Step 8.
6. Query the IP path detection parameters "Subsystem NO. of out interface", "Module NO. of out
interface", "Unit NO. of out interface", "Sunit NO. of out interface", and "Local port of out interface"
in accordance with "Task number" in the alarm information, query the interface configurations,
and check whether the egress interface information in the PD task is correct.
Yes -> Step 8.
No -> Step 7.
7. Modify the IP path detection parameters as required in accordance with "Task number" in the
alarm information, and check whether the notification persists.
Yes -> Step 8.
4-55
SJ-20140527134643-015|2015-03-31 (R1.1)
No -> End.
4.48 199030820 Memory inform reported by BIOS

l
l
l
l

Name: Memory inform reported by BIOS
This alarm is raised if the BIOS detects a memory check error.
Notification Cause
l
The memory has a correctable error.
The memory has multiple incorrectable errors.
Impact
l
If a correctable error occurs frequently and it evolves to multiple incorrectable errors, services
of the board are affected.
If a correctable error occurs frequently, the memory access efficiency may be reduced, and
services are affected.
Action
1. Check whether the same notification occurs twice or more in the same location within 24 hours.
Yes -> Step 2.
No -> End.
2. Removing a Board and Installing a Board in accordance with "Rack number", "Shelf number", and
"Slot number" in the alarm information. Check whether this notification appears within 24 hours.
Yes -> Step 3.
No -> End.
3. Replacing a Memory Bar in accordance with "Rack number", "Shelf number", "Slot number", and
"Memory location" in the alarm information, and then check whether this notification appears
within 24 hours.
Yes -> Step 4.
No -> End.
"Rack number", "Shelf number", and "Slot number" in the alarm information, and then check
whether this notification appears within 24 hours.
4-56
SJ-20140527134643-015|2015-03-31 (R1.1)
Yes -> Step 5.

No -> End.
4.49 199031041 ACL query table is unavailable

Alarm Information
Code:
199031041
Name:
ACL query table is unavailable
Severity:
Minor
Type:
Processing alarm
Alarm Description
This alarm is raised if the ACL query table fails to be calculated because of an internal cause, and the
board uses the ACL rule calculated at the last time.
In the following cases, the board processes the latest ACL to generate the query table and improve
the ACL processing efficiency. After the ACL is processed successfully, the corresponding ACL
rule becomes effective:
l
The ACL is bound with a port of the board.
The ACL is associated with an IPSec policy or a policy route.
The associated ACL table changes, for example, it is modified or deleted.
Probable Cause
l
The physical memory of the board is insufficient.
In the configured ACL, the source addresses or the destination addresses are too dispersed.
There are too many rules in the ACL table.
The configured ACL is used by multiple IPSec policies or by multiple sub-interfaces of a board.
System Impact
If this alarm is raised, some configured ACLs are not effective, and thus the real data stream matching
rule is different from the one configured by the user.
l
If the ACL applied to packet filtering is not effective, packets may be dropped or maintained
incorrectly.
If the ACL applied to IPSec is not effective, data streams that should not be encrypted may be
encrypted and those that should be encrypted may not be encrypted.
If the ACL applied to policy routing is not effective, data streams may fail to be forwarded or
modified.
4-57
SJ-20140527134643-015|2015-03-31 (R1.1)
Handling Suggestion
1. Delete the "IPV4 ACL Rule (Ipv4AclRule)" object as required. Wait for three minutes, and then
check whether the notification is reported again.
Yes -> Step 2.
No -> End.
Yes -> Step 3.
No -> End.
3. Clear the above alarm, and then check whether the notification is still reported.
Yes -> Step 4.
No -> End.
4.50 199032064 IPv6 addresses conflicted

Alarm Information
Code:
199032064
Name:
IPv6 addresses conflicted
Severity:
Minor
Type:
Alarm Description
This notification is raised if this board detects that IPv6 addresses conflict with each other.
Probable Cause
l
The IPv6 address configuration for the network interface of this board is incorrect.
The network to which the network port of this board is connected has conflicted IPv6 addresses.
The MAC addresses of the network port of this board conflict with each other.
The VLAN is not configured correctly.
System Impact
Services carried by the port may be interrupted.
4-58
SJ-20140527134643-015|2015-03-31 (R1.1)
Handling Suggestion
1. Check whether the following notification exists in accordance with "Information of the logical out
port" in the notification information:
199020803 A MAC address conflicts with another system on the subnet
Yes -> Step 2.
No -> Step 3.
2. Handles the above notifications and check whether the notification persists.
Yes -> Step 3.
No -> End.
3. [A1022]Query the "Ethernet Vlan Sub Interface(EthernetVlanTp)" object in accordance with
"Information of the logical member port" in the notification information, and check whether "VLAN
ID(VlanId)" is set as required.
Yes -> Step 5.
No -> Step 4.
4. [A1022]Query the "Ethernet Vlan Sub Interface(EthernetVlanTp)" object in accordance with
"Information of the logical member port" in the notification information, and modify the "VLAN
ID(VlanId)" parameter as required. Wait for one minute, and check whether the notification
persists.
Yes -> Step 5.
No -> End.
5. [A1012]Query the "Ethernet Interface" object in accordance with "Information of the logical out
port" in the notification information, query the "IP Address 1", "IP Address 2", "IP Address 3", "IP
Address 4", and "Local Address of Link" parameters of the child object "Ethernet IP Interface
(IPv6)" in accordance with "Duplicate Address" in the notification information, and check whether
these parameters are set as required.
Yes -> Step 7.
No -> Step 6.
6. Modify the "IP Address 1", "IP Address 2", "IP Address 3", and "IP Address 4" parameters of the
"Ethernet IP Interface (IPv6)" object as required. End alarm handling.
7. Contact the maintenance personnel of the peer end, and check whether the IPv6 and the VLAN
ID are consistent with the real requirement.
Yes -> Step 9.
No -> Step 8.
8. Ask the maintenance personnel of the peer end to modify the IPv6 and the VLAN ID as required.
End alarm handling.
9. Contact the maintenance personnel of the peer end to check whether there is a loopback
in the network.
Yes -> Step 10.
No -> Step 11.
10. Ask the maintenance personnel of the peer end to handle the faults. End alarm handling.
4-59
SJ-20140527134643-015|2015-03-31 (R1.1)
4.51 199032065 Peer-end IPv6 addresses of SuperVLAN

member interfaces conflict
Alarm Information
Code:
199032065
Name:
Peer-end IPv6 addresses of SuperVLAN member interfaces conflict
Severity:
Minor
Type:
Alarm Description
This notification is generated when the peer IPv6 addresses of the member port corresponding to the
SuperVLAN interface are conflicted.
Probable Cause
l
The IPv6 address (including virtual addresses in the same segment) of the peer device is not
correct.
The VLAN is not configured correctly.
System Impact
Services carried on the member port and the path of the conflicted IPv6 may be interrupted.
Handling Suggestion
1. [A1022]Query the "Ethernet Vlan Sub Interface(EthernetVlanTp)" or "Vlan Sub Interface of
Channel Group" object in accordance with "Information of the logical member port" in the
notification information, and check whether the "VLAN ID" parameter of the "Ethernet Vlan Sub
Interface(EthernetVlanTp)" object or the "VLAN ID" parameter of the "Vlan Sub Interface of
Channel Group" object is set as required in accordance with "Information of the duplicate port" in
the notification information.
Yes -> Step 3.
No -> Step 2.
2. Query the "Ethernet Vlan Sub Interface(EthernetVlanTp)" object or the "Vlan Sub Interface
of Channel Group" object that the "Super Vlan Member" object references in accordance
with "Information of the logical member port" and "Information of the duplicate port" in the
notification information, and modify the "VLAN ID" parameter of the "Ethernet Vlan Sub
Interface(EthernetVlanTp)" object or the "VLAN ID" parameter of the "Vlan Sub Interface of
Channel Group" object as required. Wait for one minute, and check whether the notification
persists.
Yes -> Step 3.
No -> End.
4-60
SJ-20140527134643-015|2015-03-31 (R1.1)
3. Contact the maintenance personnel of the peer end, and check whether the related configuration
items (IPv6 address, MAC address, and VLAN ID) are consistent with the real requirement.
Yes -> Step 5.
No -> Step 4.
4. Ask the maintenance personnel of the peer end to modify the related configurations (IPv6
address, MAC address, and VLAN ID) as required. End alarm handling.
4.52 199032066 Static neighbor cache entry detecting

not matched
Alarm Information
Code:
199032066
Name:
Static neighbor cache entry detecting not matched
Severity:
Minor
Type:
Alarm Description
This notification is raised if the source MAC address in the ND reply received from the peer end is
not consistent with the MAC in the local static ND after the ND detection function parameter "Switch
of ND entry detection(NdDetectSwitch)" of "Ethernet IP Interface (IPv6)(EthIpv6Intf)" object of the
port is enabled.
Probable Cause
The MAC address of the peer end is not consistent with the MAC address in the local static ND
configuration.
System Impact
Services carried on the channel corresponding to the IPv6 address that fails in the ND detection
are interrupted.
4-61
SJ-20140527134643-015|2015-03-31 (R1.1)
Handling Suggestion
1. Check whether the "Port Quintuplet" and "Request MAC address" in the notification meet the
Yes -> Step 3.
No -> Step 2.
2. Modify the "Mac address (MacAddress)" parameter of the "Static ND Entry(StaticNd)" object
as required. Wait for a period of time (more than the value of the "ND entry detection timeout
(NdDetectTimeout)" parameter * the "Times of ND entry detection timeout (NdDetectFailTimes)"
parameter of the "Ethernet IP Interface (IPv6)(EthIpv6Intf)" object, the "Ethernet IP Interface
(IPv6)(EthIpv6Intf)" object can be queried in accordance with the "Static ND Entry(StaticNd)"
object), and check whether the notification persists.
Yes -> Step 3.
No -> End.
3. Contact the maintenance personnel of the peer device to check whether the configuration is
consistent with the real requirement.
Yes -> Step 5.
No -> Step 4.
4. Ask the maintenance personnel of the peer device to modify the configuration as required. Wait
for a period of time (more than the value of the "ND entry detection timeout (NdDetectTimeout)"
parameter * the "Times of ND entry detection timeout (NdDetectFailTimes)" parameter of the
"Ethernet IP Interface (IPv6)(EthIpv6Intf)" object), and check whether the notification persists.
Yes -> Step 5.
No -> End.
4.53 199032067 Neighbor cache entry detecting failed

Alarm Information
Code:
199032067
Name:
Neighbor cache entry detecting failed
Severity:
Minor
Type:
Alarm Description
When the ND detection function is enabled (functional switch: parameter "Switch of ND entry
detection(NdDetectSwitch)" of "Ethernet IP Interface (IPv6)(EthIpv6Intf)" object), the port transmits
ND requests periodically. This notification is raised if a response is not received within the set period
(set period = parameter "ND entry detection timeout(NdDetectTimeout)" * parameter "Times of ND
entry detection timeout(NdDetectFailTimes)" of "Ethernet IP Interface (IPv6)(EthIpv6Intf)" object)
4-62
SJ-20140527134643-015|2015-03-31 (R1.1)
Probable Cause
l
The Ethernet port is faulty.
The peer device gives no response to the ND request.
The ND detects that the channel of the IPv6 address is faulty.
The VLAN to which the local Ethernet port belongs is configured incorrectly.
System Impact
Services carried on the channel corresponding to the IPv6 address that fails in the ND detection
are interrupted.
Handling Suggestion
1. Check whether the faulty port has the following alarm in accordance with the "Rack number",
"Shelf number", "Slot number", and the port number in the "Port Quintuplet".
Yes -> Step 2.
No -> Step 3.
2. Handle the above alarm, wait for a period of time (more than the value of the "ND entry
detection timeout (NdDetectTimeout)" parameter * the "Times of ND entry detection timeout
(NdDetectFailTimes)" parameter of the "Ethernet IP Interface (IPv6)(EthIpv6Intf)" object), and
Yes -> Step 3.
No -> End.
3. Check whether the "Rack number", "Shelf number", "Slot number", "Port Quintuplet", and
"Request 802.1Q" (VLAN ID) meet the actual requirements.
Yes -> Step 5.
No -> Step 4.
4. [A1012] Query the Ethernet interface object in accordance with the "Port Quintuplet"
in the notification. Modify the "VLAN ID (VlanId)" parameter of the "Ethernet Vlan Sub
Interface(EthernetVlanTp)" object as required. Wait for a period of time (more than the value of
the "ND entry detection timeout (NdDetectTimeout)" parameter * the "Times of ND entry detection
timeout (NdDetectFailTimes)" parameter of the "Ethernet IP Interface (IPv6)(EthIpv6Intf)" object),
and check whether the notification persists.
Yes -> Step 5.
No -> End.
related alarms.
Yes -> Step 6.
No -> Step 7.
6. Ask the maintenance personnel of the peer device to handle the faults. Wait for a period of
time (more than the value of the "ND entry detection timeout (NdDetectTimeout)" parameter *
the "Times of ND entry detection timeout (NdDetectFailTimes)" parameter of the "Ethernet IP
Interface (IPv6)(EthIpv6Intf)" object), and check whether the notification persists.
Yes -> Step 7.
4-63
SJ-20140527134643-015|2015-03-31 (R1.1)
No -> End.
4.54 199031297 PTP slave port link broken

Alarm Information
Code:
199031297
Name:
PTP slave port link broken
Severity:
Minor
Type:
Alarm Description
This notification is raised if the communication between the PTP port in slave status and the PTP
active clock is interrupted.
Probable Cause
l
The communication between the PTP slave port and the PTP main clock is abnormal.
The PTP main clock is abnormal.
The destination IP address of the PTP unicast-negotiation is incorrect.
System Impact
The synchronization with the main clock fails, and the 1588 clock lock of this NE is lost. Corresponding
Handling Suggestion
1. Run the QRY PTP ONE INTF CFG command to check whether "Destination address_1 for
unicast negotiation" or "Destination address_2 for unicast negotiation" of the PTP port is set as
required in accordance with "subsystem ID", "module ID", "unit ID", "sub-unit ID", and "port
number" in the alarm information.
Yes -> Step 3.
No -> Step 2.
2. [A1023]Query the "PTP Interface Configuration" object in accordance with "Slave port information
of interrupted PTP" in the alarm information, and modify the "First Destination IP Address" or
"Second Destination IP Address" parameter as required. End alarm handling.
3. Ping the "Destination address for unicast negotiation" queried in Step 1 and check whether the
ping operation is successful.
Yes -> Step 6.
No -> Step 4.
4-64
SJ-20140527134643-015|2015-03-31 (R1.1)
4. [A1024]Query the physical address of the interface board in accordance with "Slave port
information of interrupted PTP" in the alarm information, and check whether the following alarm
exists:
Yes -> Step 5.
No -> Step 11.
5. Handle the above alarms. Run the QRY PTP ONE PORT STATE command to check whether the
PTP port is in "SLAVE" status in accordance with "subsystem ID", "module ID", "unit ID", "sub-unit
ID", and "port number" in the alarm information.
Yes -> Step 6.
No -> Step 11.
6. Run the QRY PTP UNICAST NEGO NORMAL PORT command to check whether the PTP port
has any unicast negotiation record in accordance with "Subsystem ID", "Module ID", "unit ID",
"sub-unit ID", and "port number" in the alarm information.
Yes -> Step 9.
No -> Step 7.
7. Run the QRY PTP ONE INTF CFG command to check whether the "The flag if multicast is
enabled" parameter of the PTP port is set to "On" in accordance with "subsystem ID", "module
ID", "unit ID", "sub-unit ID", and "port number" in the alarm information.
Yes -> Step 8.
No -> Step 11.
8. Wait for five minutes, and check whether the notification persists.
Yes -> Step 11.
No -> End.
9. Contact the maintenance personnel of the peer end to check whether the main clock has related
alarms.
Yes -> Step 10.
No -> Step 11.
10. Ask the maintenance personnel of the peer end to handle the faults, wait for five minutes, and
then check whether the notification persists.
Yes -> Step 11.
No -> End.
4.55 199031298 PTP slave port change

Alarm Information
Code:
199031298
Name:
PTP slave port change
Severity:
Minor
4-65
SJ-20140527134643-015|2015-03-31 (R1.1)
Type:
Alarm Description
This notification is raised if the change of the external active clock results in the change of the slave
port that is used for the 1588 clock synchronization, This notification is also generated for the port
vibration even if the slave port is not changed.
Probable Cause
l
The external main clock changes, for example, a new main clock is added or a main clock is
interrupted.
The old slave port is unavailable, and a new slave port in the NE is generated.
System Impact
The slave port changes.
Handling Suggestion
4.56 199105001 Failed to get the table of configuration

Notification code:
199105001
Notification name:
Failed to get the table of configuration
Minor
Notification type:
Equipment Alarm
The board fails to obtain the database configuration from itself or the OMP.
Notification Cause
l
The database table configuration is incomplete or wrong.
The channel over which the control-plane data is transmitted is not operating properly.
4-66
SJ-20140527134643-015|2015-03-31 (R1.1)
Impact
The effect on the system varies with the alarm cause. Detailed information is as follows:
l
Failing to obtain the IP segment reassemble board information.

This information is used to process the external fragmented IP packets arriving at the device.
If the information is missing, the processing of fragmented IP packets may fail, causing the
interruption of services or a decline of the service processing rate.
Failing to obtain the OMCB server configuration.

If the configuration is missing, the OMCB function may fail to be used.
Failing to obtain the signaling distribution table.

If the information is missing, the SCTP data may fail to be transmitted on the interface board,
and related services operating on the board are interrupted.
Failing to obtain the IP/UDP distribution table.

If the information is missing, the processing of the IUPS service or the IP transport-based data
may fail.
Failing to obtain the layer-2 forwarding table.

If the information is missing, the internal communication of the device is not operating properly,
causing the interruption of all services operating on the board.
Failing to obtain the path configuration table.

For the ATM interface board, if the information is missing, the processing of the AAL2-based data
may fail, causing the interruption of the IUB, IUCS, and IUR services belonging to the office.
For the IP interface board, the traffic control on IP packets may fail, causing the interruption of
all services belonging to the office.
Failing to obtain the path group configuration table.

For the ATM interface board, if the information is missing, the processing of the AAL2-based data
may fail, causing the interruption of IUB, IUCS, and IUR services belonging to the office. For the
IP interface board, there is no impact on services.
Action
1. Re-execute [synchronize all data], and check whether the notification persists.
Yes -> Step 2.
No -> End.
2. Check whether the following parameters are set as required in accordance with "Table name" in
the notification information.
IpUdpTbl: "Slave Sunit(UpSlaveSunit)"
PathGrpTbl: "Transmission Path Group(TrPathGroup)"
PathTbl:
l
UMTS: "Iub Transmission Path(UIubTrPath)", "MGW Transmission Path(UMgwTrPath)",

"Iups Transmission Path(UIupsTrPath)", "Iur Transmission Path(UIurTrPath)", and "Iurg
Transmission Path(UIurgTrPath)"
TD: "Iub Transmission Path(TIubTrPath)", "MGW Transmission Path(TMgwTrPath)",

"Iups Transmission Path(TIupsTrPath)", "Iur Transmission Path(TIurTrPath)", and "Iurg
Transmission Path(TIurgTrPath)"
4-67
SJ-20140527134643-015|2015-03-31 (R1.1)
GSM: "Abis Transmission Path(GAbisTrPath)", "A Transmission Path(GATrPath)", "Gb

Transmission Path(GGbTrPath)", "Ater Transmission Path(GAterTrPath)", and "Iurg
Transmission Path(GIurgTrPath)"
PathCirTbl:
l
UMTS: "CIR of Iub Transmission Path(UIubTrPathCir)", "CIR of MGW Transmission

Path(UMgwTrPathCir)", "CIR of Iups Transmission Path(UIupsTrPathCir)", "CIR of Iur
Transmission Path(UIurTrPathCir)", and "CIR of Iurg Transmission Path(UIurgTrPathCir)"
GSM: "CIR of Abis Transmission Path(GAbisTrPathCir)", "CIR of A Transmission

Path(GATrPathCir)", "CIR of Gb Transmission Path(GGbTrPathCir)", "CIR of Ater
Transmission Path(GAterTrPathCir)", and "CIR of Iurg Transmission Path(GIurgTrPathCir)"
TD: "CIR of Iub Transmission Path(TIubTrPathCir)", "CIR of MGW Transmission

Path(TMgwTrPathCir)", "CIR of Iups Transmission Path(TIupsTrPathCir)", "CIR of Iur
Transmission Path(TIurTrPathCir)", and "CIR of Iurg Transmission Path(TIurgTrPathCir)"
IntfIpAddrTbl: "Ethernet IP Interface (IPv4)(EthIpIntf)", "Ethernet IP Sub Interface(IPV4)(EthIpSubIntf)", "Ethernet Channel IP Sub Interface(IPV4)(EthChIpSubIntf)", "Ethernet Channel
IP Interface (IPV4)(EthChIpIntf)", "IP Interface of ML-PPP Group(MlpppTpIpIntf)", "IP
Interface of PPP Link(PppIpIntf)", "Super Vlan IP Interface(IPV4)(EthSuperIpIntf)", "IPOA
IP Configuration(IpoaTp)", "Loopback IP Interface(LbIpIntf)", "Virtual IP Interface(VIpIntf)",
"Ethernet IP Interface(IPV6)(EthIpv6Intf)", "Ethernet IP Sub Interface(IPV6)(EthIpv6SubIntf)",
"Ethernet Channel IP Sub Interface(IPV6)(EthChIpv6SubIntf)", "Ethernet Channel IP
Interface(IPV6)(EthChIpv6Intf)", and "Super Vlan IP Interface(IPV6)(EthSuperIpv6Intf)".
ReassBrdTbl: Check "IP Configuration(Ip)". "IP Segment ReAssemble Default Unit(ref1Unit)" and
"IP Configuration(Ip)". "IP Segment ReAssemble Units(ref2Unit[])".
DhcpRoleTbl: check "DHCP Server(DhcpServer)" and "DHCP Relay(DhcpRelay)".
DataMuxTbl: check "IP Configuration(Ip)". "DeMux Port of RTP MUX (IuDeMuxUdpPort)" and "IP
Configuration(Ip)". "DeMux Port of UDP/RTP MUX (IubDeMuxUdpPort)".
SctpCfgTbl: check "Association(SctpAssociation)".
OmcbCfgTbl: check "Operation Maintenance Configuration(OmCon)".
InnerOmcbCliIp:
l
UMTS: "Iub Link(UIubLink)". "OMCB Inner Service IPv4 Address(InnerOmcbCliIPv4)".
TD: "Iub Link(TIubLink)". "OMCB Inner Service IPv4 Address(InnerOmcbCliIPv4)".
GSM: "Abis Office(GAbisLink)". "OMCB Inner Service IPv4 Address(InnerOmcbCliIPv4)"
OmcbMultiPath:
l
UMTS: "Omcb Path(UOmcbPath)"
TD: "Omcb Path(TOmcbPath)"
GSM: "Omcb Path(GOmcbPath)"
UdpUnitTbl: "UDP Port Configuration(UDPPORTNUM)"

DhcpRelayTbl: "DHCP Relay(DhcpRelay)".
Yes -> Step 4.
No -> Step 3.
3. Modify the configuration as required, and check whether the notification persists.
Yes -> Step 4.
No -> End.
4-68
SJ-20140527134643-015|2015-03-31 (R1.1)
4.57 199105002 The route table is overloaded

Notification code:
199105002
Notification name:
The route table is overloaded
Minor
Notification type:
Equipment Alarm
The total number of routing entries that the user-plane board detects exceeds 90 percent of the
maximum number of routing entries that the board supports.
Notification Cause
Too many routing entries are configured, reaching 90 percent of the capacity of the routing table (the
maximum number of routing entries that a board supports is 4096).
Impact
l
If the total number of routing entries does not exceed the maximum capacity of the routing table
on the user-plane processing board, services are not affected.
If the total number of routing entries exceeds the maximum capacity of the routing table on the
user-plane processing board, some routing entries are lost.
If the lost route is the route from the RNC/BSC to NodeB/BTS or to the CN, user services may
fail to be connected to the board.
If the lost route is destined to the peer RNC NE, the cross-RNC user services cannot be
connected to the board.
The SLA diagnostic test between the RNC and other NEs fails to be executed.
Action
1. Check whether the following configuration is in accordance with actual requirements:
Routing table:"Static Route(StaticRoute)"
Interface table:
l
"Ethernet IP Interface (IPv4)(EthIpIntf)"
"Ethernet IP Sub Interface (IPv4)(EthIpSubIntf)"
"Ethernet Channel IP Sub Interface (IPv4)(EthChIpSubIntf)"
"Ethernet Channel IP Interface (IPv4)(EthChIpIntf)"
"IP Interface of ML-PPP Group(MlpppTpIpIntf)"
"IP Interface of PPP Link(PppIpIntf)"
"Super Vlan IP Interface (IPv4)(EthSuperIpIntf)"
"IPOA IP Configuration(IpoaTp)"
4-69
SJ-20140527134643-015|2015-03-31 (R1.1)
"Loopback IP Interface(LbIpIntf)"
"Virtual IP Interface(VIpIntf)"
"Ethernet IP Interface (IPv6)(EthIpv6Intf)"
"Ethernet Sub Interface (IPv6)(EthIpv6SubIntf)"
"Ethernet Channel Sub Interface (IPv6)(EthChIpv6SubIntf)"
"Ethernet Channel IP Interface (IPv6)(EthChIpv6Intf)"
"Super Vlan IP Interface (IPv6)(EthSuperIpv6Intf)"
Yes -> Step 3.

No -> Step 2.
2. Modify the configuration as required. Wait for five minutes, and check whether the notification
is cleared.
Yes -> End.
No -> Step 3.
3. Contact the next level of maintenance support (it is recommended to re-plan routes and the
networking topology).
4.58 199105003 Failed to handle DHCP message from

other network
Notification code:
199105003
Notification name:
Failed to handle DHCP message from other network
Minor
Notification type:
Equipment Alarm
The DHCP server board fails to process a DHCP message.
Notification Cause
l
The peer IP address of the PPP link is not configured.
The operation and maintenance IP address of the RNC for the NODEB is not configured.
The DHCP client configuration fails to be obtained.
An error DHCP message is received.
Impact
The DHCP client fails to obtain the IP address.
4-70
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
1. Open the rack diagram, and identify the board type (interface board or non-interface board) in
accordance with the physical address in the notification information. Check whether the following
configuration is in accordance with actual requirements.
[non-interface board parameters]
l
"DHCP Client(DhcpClient)"
[interface board parameters]

l
"IP Interface of ML-PPP Group(MlpppTpIpIntf)". "Peer IP Address(PeerIpAddress)"
"IP Interface of PPP Link(PppIpIntf)". "Peer IP Address(PeerIpAddress)"
Yes -> Step 3.

No -> Step 2.
2. Modify the configuration as required, and check whether a new notification is reported.
Yes -> Step 3.
No -> End.
4.59 199105004 Failed to operate multicast group

Notification code:
199105004
Notification name:
Failed to operate multicast group
Minor
Notification type:
Equipment Alarm
The interface board fails to be added to the User Trace Multicast Group.
Notification Cause
The interface board fails to be added to the User Trace Multicast Group, which may be caused
by the abnormal communication with the control-plane channel of other control-plane boards or
the abnormal operation of the board.
Impact
The user tracing function of the interface board may fail to operate properly. There is no impact
on services.
4-71
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
4.60 199105005 Clock difference of slave is large

Notification code:
199105005
Notification name:
Clock difference of slave is large
Minor
Notification type:
Equipment Alarm
The user-plane board detects that the clock difference between the slave subunit and host exceeds
the threshold.
Notification Cause
l
The clock deviation between the slave subunit and host exceeds the threshold (default: 36
seconds).
The crystal oscillator of the slave subunit or host is not accurate.
The board is writing the black box.
Impact
The services operating on the slave subunit may be interrupted.
Action
1. Run the SET BLOCKSUNIT:MEID=,SUBSYSTEM=,UNIT=,SUNIT=; command in accordance
with "Slave Sunit" and the physical address in the notification information to block the slave
subunit, and then run the SET UNBLOCKSUNIT:MEID=,SUBSYSTEM=,UNIT=,SUNIT=;
command to unblock the slave subunit. Wait for five hours, and check whether the notification
persists.
Yes -> Step 2.
No -> End.
"Shelf number", "Slot number", and "CPU number" in the notification information. Wait for 5
minutes, and check whether the notification is cleared.
Yes -> End.
No -> Step 3.
4-72
SJ-20140527134643-015|2015-03-31 (R1.1)
3. [Replace the board with an operational one], wait for five minutes, and check whether the
notification is cleared.
Yes -> End.
No -> Step 4.
4.61 199105006 Slave losted external clock

Notification code:
199105006
Notification name:
Slave losted external clock
Minor
Notification type:
Equipment Alarm
The user-plane board detects the loss of the external clock of the slave subunit.
Notification Cause
l
The clock channel between the clock board and user panel is not operating properly.
The clock board is not operating properly.
The hardware of the user panel is faulty.
Impact
Action
command to unblock the slave subunit. Wait for five minutes, and check whether the notification
is cleared.
Yes -> End.
No -> Step 2.
2. Check whether an alarm arises on the clock board.
Yes -> Step 3.
No -> Step 4.
3. Handle the related alarm, and check whether the notification is cleared.
Yes -> End.
4-73
SJ-20140527134643-015|2015-03-31 (R1.1)
No -> Step 4.
4. Check whether other alarms arise on the board.
Yes -> Step 5.
No -> Step 6.
5. Handle the related alarms, and check whether the notification is cleared.
Yes -> End.
No -> Step 6.
"Shelf number", "Slot number", and "CPU number" in the notification information. Wait for 5
minutes, and check whether the notification is cleared.
Yes -> End.
No -> Step 7.
wait for five minutes, and check whether the notification is cleared.
Yes -> End.
No -> Step 8.
4.62 199105008 Bandwidth automatic adjustment is

useless
Notification code:
199105008
Notification name:
Bandwidth automatic adjustment is useless
Minor
Notification type:
Qos Alarm
The base station controller that has the "Transmission CAC based on SLA-PM" function enabled
detects that bandwidth automatic adjustment is invalid.
Notification Cause
The base station controller cannot completely solve the loss of packets over the path after setting the
transmission path bandwidth to the smallest value.
Impact
The packet loss ratio of the path is larger than the reference value, which causes a decline of the
PS/CS service quality, the access failure, and service interruption.
4-74
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
1. Find the interface location in accordance with the network planning data and "ANE ID" in the
notification information, and check whether the physical cable connected to the interface is loose.
Yes -> Step 2.
No -> Step 3.
2. Secure the physical cable.
3. Wait for half an hour, and check whether the notification persists.
Yes -> Step 4.
No -> End.
4. Record the packet loss ratio in additional information of the newly reported notification, and
contact the next level of maintenance support.
4.63 199105018 Unable to save Performance File

Notification code:
199105018
Notification name:
Unable to save Performance File
Minor
Notification type:
Processing alarm
The OMP fails to store performance files.
Notification Cause
1. The space of the disk on the OMP is less than 500 MB.
2. If the link between the OMM and OMP is broken for more than 24 hours, the OMP does not
record performance files.
Impact
There is no impact on services. The performance statistics data may be lost, causing the performance
statistics results to be incorrect.
4-75
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
198099803 Link Broken Between OMM and NE
Yes -> Step 2.
No -> Step 3.
2. Handle the related alarm. Wait for a performance statistics period, and check whether the
Yes -> Step 3.
No -> End.
4.64 199105019 SLAVE memory check fail notification

Notification code:
199105019
Notification name:
SLAVE memory check fail notification
Minor
Notification type:
Equipment Alarm
The user-plane board detects a memory soft check failure in the slave subunit.
Notification Cause
The software or hardware of the slave subunit is not operating properly.
Impact
Action
command to unblock the slave subunit. Wait for five minutes, and check whether the notification
persists.
Yes -> Step 2.
No -> End.
2. Replace the board with an operational one, wait for five minutes, and check whether the
notification is cleared.
4-76
SJ-20140527134643-015|2015-03-31 (R1.1)
Yes -> End.

No -> Step 3.
4.65 199105030 OMP received data is not complete

Notification code:
199105030
Notification name:
OMP received data is not complete
Minor
Notification type:
The non-OMP board detects that not all of the performance data on the board is reported to the OMP.
Notification Cause
l
Too many measurement statistics task are executed at the same time, resulting in a large
amount of performance data on the non-OMP board. The data cannot be sent to the OMP
during the specified time.
The communication between the OMP and non-OMP board is faulty.
Impact
There is no impact on services. The performance statistics data may be lost, causing the performance
statistics results to be incorrect.
Action
Yes -> Step 2.
No -> Step 3.
2. Handle the related alarm.
3. Terminate some performance statistics tasks that are not related to the KPI.
4. Wait for 15 minutes, and check whether the notification persists.
Yes -> Step 5.
No -> End.
4-77
SJ-20140527134643-015|2015-03-31 (R1.1)
4.66 199105032 Transport Path Occupied BandWidth

Overload
Notification code:
199105032
Notification name:
Transport Path Occupied BandWidth Overload
Minor
Notification type:
Qos Alarm
The base station controller detects that the bandwidth that is already allocated in the transmission
path exceeds the bandwidth upperlimit.
Notification Cause
l
The E1/T1 link is broken.
The transport quality of the transmission link is deteriorated.
The intermediate device is faulty.
The higher-priority service is forcedly accessed.
Impact
The available bandwidth to the destination address is smaller than the allocated bandwidth, the base
station controller selectively releases services over the transmission path to avoid congestions on
the transmission path.
Action
1. Query the transmission path object in the corresponding office in accordance with "ANE ID" and
"Transmission path ID" in the alarm information. Check whether the "Transport BandWidth
Adjustment Switch based on IP SLA(IpBandAdjSwitch)" parameter of the object is set to
"1:(Open)".
Yes-> It means that the "Transmission CAC based on SLA-PM" function is enabled, and the
transport quality of the transmission channel to the office is deteriorated or the intermediate
device is faulty. In this case, contact the maintenance personnel of the intermediate device to
resolve the fault. End alarm handling.
No -> Step 2.
2. It means a higher-priority service is forcedly accessed, causing the exceeding of the bandwidth
limit. In this case, no action is required, and end alarm handling.
4-78
SJ-20140527134643-015|2015-03-31 (R1.1)
4.67 199105033 Transport Path group Occupied

Bandwidth Overload
Notification code:
199105033
Notification name:
Transport Path group Occupied Bandwidth Overload
Minor
Notification type:
Qos Alarm
The base station controller detects that the bandwidth that is already allocated in the transmission
path group exceeds the bandwidth upperlimit.
Notification Cause
l
The E1/T1 link is broken.
The transport quality of the transmission link is deteriorated.
The intermediate device is faulty.
The higher-priority service is forcedly accessed.
Impact
The available bandwidth to the destination address is smaller than the allocated bandwidth, and
therefore the rate at which services operate over the path group decreases.
Action
1. Query the "Transmission Path Group(TrPathGroup)" object in accordance with "Path group ID" in
the alarm information. If "E1/T1 Transport BandWidth Adjustment Switch(E1T1BandAdjSwit)" is
set to "1:(Open)", check whether the following alarms arise:
199000514 Trunk alarm indication signal
199000515 Trunk loss of CRC multi-frame
199000517 Trunk remote alarm indication
199000518 Trunk link is used for CSU loopback test
199005773 High CRC error rate at E1/T1 bottom layer
199005774 High FAS error rate at E1/T1 bottom layer
199005775 High EBIT error rate at E1 bottom layer
4-79
SJ-20140527134643-015|2015-03-31 (R1.1)

199001796 SDH/SONET:MS far-end reception failure/Line far-end reception failure
199001797 SDH/SONET:Signal failure
199001798 SDH/SONET:Signal deterioration
199001799 SDH/SONET:Loss of AU pointer/Loss of path pointer
199001801 SDH/SONET:HP trace mismatch/ Path trace mismatch
199001803 SDH/SONET:HP label mismatch/Path label mismatch
199001804 SDH/SONET:HP remote reception failure/Path remote reception failure
199001805 SDH/SONET:Loss of multi-frame
signal
199001808 SDH/SONET:LP remote defect indication/Virtual tributary remote defect indication
199001809 SDH/SONET:LP remote failure indication/Virtual tributary remote failure indication
199001810 SDH/SONET:LP trace mismatch/Virtual tributary trace mismatch
199001811 SDH/SONET:LP unequipped/Virtual tributary unequipped
199001812 SDH/SONET:LP label mismatch/Virtual tributary label mismatch
199001819 SDH/SONET:Severely BIP-2 error code
199001820 SDH/SONET:MS remote error indication
199001821 SDH/SONET:HP remote error indication
199001826 SDH/SONET:LP remote error indication
Yes -> Step 2.
No -> Step 3.
2. Handle the related alarm, and end alarm handling.
3. It means a higher-priority service is forcedly connected, causing the exceeding of the bandwidth
limit. In this case, no action is required, and end alarm handling.
4.68 199105043 The slave's IPUDP configuration is

modified
Notification code:
199105043
Notification name:
The slave's IPUDP configuration is modified
Minor
4-80
SJ-20140527134643-015|2015-03-31 (R1.1)
Notification type:
Equipment Alarm
The user-plane board detects a change of the IPUDP resource configuration in the slave subunit.
Notification Cause
The following IPUDP resource configuration is modified:
l
"UDP Port Configuration(UDPPORTNUM)"
"Slave Sunit(UpSlaveSunit)"
Impact
Services operating on the slave subunit are released.
Action
4.69 199105046 The log files on LogService board are

unavailable
Notification code:
199105046
Notification name:
The log files on LogService board are unavailable
Minor
Notification type:
Processing alarm
OMP detect the data on LogService are abnormal.
The causes include:
l
The log files on LogService board are abnormal.
The log data are lost seriously.
Notification Cause
l
The software on LogService has error.
The communication between the LogService and processing board is abnormal.
4-81
SJ-20140527134643-015|2015-03-31 (R1.1)
Impact
It does not have impact on the services, but the files can not be used by trouble shooting and
network optimization.
Action
Please contact the next level of maintenance support.
4.70 199105048 OMP disk reserved for performance

files is insufficient
Notification code:
199105048
Notification name:
OMP disk reserved for performance files is insufficient
Minor
Notification type:
Equipment Alarm
This notification is raised when the OMP detects that the remaining disk space is smaller than 7G
in a performance data report period.
Notification Cause
Too many files (for example: historical version files) are saved on the OMP.
Impact
Performance data may be lost because insufficient space is available after the OMM and OMP
are disconnected.
Action
4.71 199087360 BCCH Exchange Fail

Notification code:
199087360
4-82
SJ-20140527134643-015|2015-03-31 (R1.1)
Notification name:
BCCH Exchange Fail
Minor
Notification type:
Processing alarm
This notification is reported if the BSC detects a BCCH switchover failure.
Notification Cause
l
BCCH switchover is disabled.
The destination carrier does not respond or operations on the destination TRX fails during
BCCH switchover.
The destination carrier does not exist.
Impact
Voice and data services are not available in the cell.
Action
1. According to the object reporting this notification, query the object "GSM Cell
Configuration(GGsmCell)", and check whether the parameter "BCCH switch
allowed(CanBcchExch)" is "Yes".
Query the global object "GSM Logical Configuration(GBssFunction)", and check whether the
parameter "BCCH switch allowed(CanBcchExch)" is "Yes".
Yes -> Step 3.
No -> Step 2.
2. Modify these two parameters to "Yes". Wait for eight minutes, and check whether the notification
is still reported.
Yes -> Step 3.
No -> End.
3. Execute the QRY TRX command based on "Site ID" and "Bts ID" in the alarm details to query
the state of all the carrier frequencies in the cell. Execute the UNB FUTRX or UNB CUTRX
command to unblock the carrier frequencies in "manual block" state based on "Trx ID". Wait for
eight minutes, and check whether the notification is still reported.
Yes -> Step 4.
No -> End.
4. Contact BS maintenance personnel to check whether carrier frequency-related faults occurred.
Yes -> Step 5.
No -> Step 6.
5. Ask BS maintenance personnel to remove the faults. Check whether the notification persists.
Yes -> Step 6.
No -> End.
4-83
SJ-20140527134643-015|2015-03-31 (R1.1)
4.72 199087393 Ring state notification

Notification code:
199087393
Notification name:
Ring state notification
Minor
Notification type:
Equipment Alarm
This notification is reported if the BSC detects the ring network status has changed. There are
three ring network statuses:
l
Switchover status
Normal connection status
Disconnection status
Notification Cause
The BS link is broken.
Impact
Services cannot operate properly.
Action
4.73 199087394 Intelligent power up/down preparation

notification
Notification code:
199087394
Notification name:
Intelligent power up/down preparation notification
Minor
Notification type:
Equipment Alarm
4-84
SJ-20140527134643-015|2015-03-31 (R1.1)
This notification is reported if the BSC detects the intelligent power-on/power-off state of the carrier
has been changed.
Notification Cause
The system has changed the power-on/power-off state of the carrier.
Impact
None.
Action
4.74 199087459 cell no gprs traffic inform

Notification code:
199087459
Notification name:
cell no gprs traffic inform
Minor
Notification type:
This notification is reported if the BSC detects there is no GPRS traffic in a cell for one hour.
Notification Cause
Data service is not available for one hour in the cell.
Impact
None.
Action
4-85
SJ-20140527134643-015|2015-03-31 (R1.1)
4.75 199087469 abis route change inform

Notification code:
199087469
Notification name:
abis route change inform
Minor
Notification type:
Equipment Alarm
This notification is reported if the BSC detects that the Abis interface link changes from the satellite
link to the ground link or from the ground link to the satellite link.
Notification Cause
l
The Abis ground link of the satellite-backup site is broken.
The Abis ground link of the satellite-backup site is restored.
Impact
None.
Action
4.76 199087353 NSVC deletion notification

Notification code:
199087353
Notification name:
NSVC deletion notification
Minor
Notification type:
Equipment Alarm
This notification is reported if a board detects that an NSVC link is deleted manually.
4-86
SJ-20140527134643-015|2015-03-31 (R1.1)
Notification Cause
An NSVC link is deleted manually.
Impact
None.
Action
1. Check whether the NSVC link is the one that should be deleted.
Yes -> End.
No -> Step 2.
4.77 199087395 SNS Size process failure notification

Notification code:
199087395
Notification name:
SNS Size process failure notification
Minor
Notification type:
This notification is reported if a board detects an SNS Size process failure.
Notification Cause
There is no response from the SGSN, or a failure response is received.
Impact
The NSVC link fails to be established.
4-87
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
1. Check whether the configuration of the following parameters of the object "IP Nse(GIpGbNse)" is
consistent with that of the SGSN.
l
"Nse ID(GIpGbNseSeq)"
"SGSN IP Address(SGSNIPAddress)"
"SGSN UDP Port(SGSNUDPPort)"
Yes -> Step 3.

No -> Step 2.
2. Modify the parameter configuration for consistency with that of the SGSN, and check whether
the notification is cleared.
Yes -> End.
No -> Step 3.
4.78 199087396 SNS Config process failure notification

Notification code:
199087396
Notification name:
SNS Config process failure notification
Minor
Notification type:
This notification is reported if a board detects an SNS Config process failure.
Notification Cause
There is no response from the SGSN, or a failure response is received.
Impact
The NSVC link fails to be established.
4-88
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
1. Check whether the value of the parameter "Signaling Weights(SigWeight)" or "Data
Weights(DataWeight)" of the object "Local End Point(GIpGbLocalEP)" is not equal to 0.
Yes -> Step 3.
No -> Step 2.
2. Modify the signalling or data weight of the IP endpoint to a nonzero value, and check whether
the notification is cleared.
Yes -> End.
No -> Step 3.
4.79 199087466 NSVC's IP deletion notification

Notification code:
199087466
Notification name:
NSVC's IP deletion notification
Minor
Notification type:
Equipment Alarm
This notification is reported if a board detects that an NSVC link in IP is deleted.
Notification Cause
An NSVC link in IP is deleted.
Impact
None.
Action
1. Based on "NSVCI" together with "SGSN ID" and "NSEI" in the alarm details, check whether the
NSVC link is the one that should be deleted.
Yes -> End.
No -> Step 2.
4-89
SJ-20140527134643-015|2015-03-31 (R1.1)
4.80 199087359 No access of BSC to MSC SPC

Notification code:
199087359
Notification name:
No access of BSC to MSC SPC
Minor
Notification type:
Processing alarm
This notification is reported if the BSC fails to obtain the MSC SPC.
Notification Cause
The BSC is not configured with the MSC office type.
Impact
All the services are interrupted.
Action
1. Configure the object "Adjacent Office Information(RemoteSp)" with "Type of adjacent
office(OfficeType)" of 512(MSCSERVER) or 576(MGW+MSCSERVER). whether the notification
persists.
Yes -> Step 2.
No -> End.
4.81 199087503 Baseband frequency hopping

exchange for trx fail
Notification code:
199087503
Notification name:
Baseband frequency hopping exchange for trx fail
Minor
Notification type:
Equipment Alarm
4-90
SJ-20140527134643-015|2015-03-31 (R1.1)
This notification is reported if the BSC detects a carrier failure in a baseband frequency-hopping
group and automatically performs active/standby switchover.
Notification Cause
A carrier failure occurs in a baseband frequency-hopping group.
Impact
None.
Action
1. Execute the QRY TRX command based on "Site ID", "Bts ID", and "Trx ID" in the alarm details,
and check whether the status of this carrier is "manual block".
Yes -> Step 2.
No -> Step 3.
2. Execute the UNB FUTRX or UNB CUTRX command based on "Site ID", "Bts ID", and "Trx ID" in
the alarm details to unblock the blocked carrier Check whether the following notifications arise:
199087504 Baseband frequency hopping exchange for trx restore
Yes -> End.
No -> Step 5.
3. Contact BS maintenance personnel to check whether carrier related faults occurred.
Yes -> Step 4.
No -> Step 5.
4. Ask BS maintenance personnel to remove the faults. The alarm handling is completed.
4.82 199087504 Baseband frequency hopping

exchange for trx restore
Notification code:
199087504
Notification name:
Baseband frequency hopping exchange for trx restore
Minor
Notification type:
Equipment Alarm
4-91
SJ-20140527134643-015|2015-03-31 (R1.1)
This notification is reported if the BSC detects a carrier recovery in a baseband frequency-hopping
group and automatically performs active/standby switchover.
Notification Cause
A carrier in a baseband frequency-hopping group recovers.
Impact
None.
Action
4.83 199087508 Block Successfully After Service

released
Notification code:
199087508
Notification name:
Block Successfully After Service released
Minor
Notification type:
Processing alarm
This notification is generated if the network management system initiates cell/carrier/timeslot "Block
after service released" and the BSC performs one of the following operations.
l
The object is blocked after the current services are released.
The system initiates BCCH switchover when the BSC is waiting for resources to be released.
The object is blocked mandatorily.
The object is blocked mandatorily when the longest timer expires and the resources are not
released yet.
Notification Cause
The BSC performs the "Block after service released" function.
Impact
The blocked resources cannot be used. The system capacity is decreased.
4-92
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
4.84 199087751 dbsapp no avilable PCU resource

inform
Notification code:
199087751
Notification name:
dbsapp no avilable PCU resource inform
Minor
Notification type:
Qos Alarm
This notification is generated if the BSC detects that PCU resources are insufficient when the cell
is selecting PCU resource.
Notification Cause
l
PCU resources are insufficient.
PCU resources are faulty.
Impact
Some cells cannot provide data service.
Action
1. On the rack diagram of Alarm management, check whether an alarm exists on the RUP board.
Yes -> Step 2.
No -> Step 3.
2. Handle the alarm. The alarm handling is completed.
4.85 199087760 BTS master power recover notification

Notification code:
199087760
4-93
SJ-20140527134643-015|2015-03-31 (R1.1)
Notification name:
BTS master power recover notification
Minor
Notification type:
Qos Alarm
This notification is generated if the BSC detects that the master power of the base station is recovered.
Notification Cause
The master power of the base station is recovered.
Impact
None.
Action
4.86 199087761 BTS master power interruption

notification
Notification code:
199087761
Notification name:
BTS master power interruption notification
Minor
Notification type:
Qos Alarm
If the BSC receives the "BTS master power interruption" message reported by the base station and
it waits for a moment (by configuring "Site(GBtsSiteManager)"."the delay time of master power
Off(MasterPwrOffTime)", and confirms that some carriers are powered off after the master power is
off, the BSC generates this notification.
Notification Cause
The master power of the base station is off.
4-94
SJ-20140527134643-015|2015-03-31 (R1.1)
Impact
None.
Action
4.87 199087762 After BTS mains power failure TRX

terminated notification
Notification code:
199087762
Notification name:
After BTS mains power failure TRX terminated notification
Minor
Notification type:
Qos Alarm
If the BSC detects that the master power of the base station is off and it waits for a moment (by
configuring "Site(GBtsSiteManager)"."the delay time of master power Off(MasterPwrOffTime)", and
confirms that some carriers are powered off after the master power is off and then waits for another
moment (by configuring ""Site(GBtsSiteManager)"."the delay time of Transceivers Off(TrxOffTime)"
before terminating all carriers except BCCH carrier, the BSC generates this notification.
Notification Cause
The master power of the base station is off.
Impact
None.
Action
4-95
SJ-20140527134643-015|2015-03-31 (R1.1)
4.88 199087772 Super Site Connect in

Notification code:
199087772
Notification name:
Super Site Connect in
Major
Notification type:
Qos Alarm
This notification is generated if the BSC detects that the Abis link of the super station is exchanged
(among the subaerial link, the satellite link or the standby link).
Notification Cause
The Abis link of the super station is exchanged.
Impact
None.
Action
4.89 199087799 Cell intelligent power-on or

power-down
Notification code:
199087799
Notification name:
Cell intelligent power-on or power-down
Minor
Notification type:
Processing alarm
This notification is generated if the BSC detects the power-on/power-off state of the cell's BCCH
carrier has been changed.
4-96
SJ-20140527134643-015|2015-03-31 (R1.1)
Notification Cause
The BSC has changed the power-on/power-off state of the cell's BCCH carrier.
Impact
None.
Action
4.90 199087514 TRAU frame sync loss notification

Notification code:
199087514
Notification name:
TRAU frame sync loss notification
Minor
Notification type:
This notification is generated if the BSC detects that TRAU frame alignment loss occurs on a voice
channel for a long time.
Notification Cause
The transmission quality of this channel is poor.
Impact
None.
Action
4.91 199087515 BCCH Exchange Success

Notification code:
199087515
4-97
SJ-20140527134643-015|2015-03-31 (R1.1)
Notification name:
BCCH Exchange Success
Minor
Notification type:
Processing alarm
This notification is generated if the BSC detects BCCH switchover success.
Notification Cause
BCCH switchover is successful.
Impact
None.
Action
4.92 199087516 Mute call detect

Notification code:
199087516
Notification name:
Mute call detect
Minor
Notification type:
This notification is generated if the BSC detects that packet loss occurs on a voice channel for a
long time.
Notification Cause
For a long time, voice data cannot be detected on this channel.
Impact
None.
4-98
SJ-20140527134643-015|2015-03-31 (R1.1)
Action
4.93 199087519 Release dynamic association by force

Notification code:
199087519
Notification name:
Release dynamic association by force
Minor
Notification type:
This notification is reported if the BSC automatically releases a detected illegal dynamic association.
Notification Cause
l
More than two dynamic associations are established between the BSC and a base station.
A conflict of local port number occurs between the new dynamic association and an existing
association (master or slave) due to incorrect association configuration at the base station side.
The BSC configures static associations for the base station, but the corresponding association
parameters configured at the base station side are inconsistent with those in the BSC.
Impact
The association establishment on the Abis interface of the base station may be influenced.
Action
1. Locate the base station and its site ID in accordance with "peer IP address" and "peer port
ID" in the alarm details, and check whether more than two associations are configured at the
base station side.
Yes -> Step 2.
No -> Step 3.
2. Delete the extra associations. Check whether the notification persists.
Yes -> Step 3.
No -> End.
3. View the association configuration at the base station side, and check whether the local port
number of the association is configured to the site ID of the base station.
Yes -> Step 5.
No -> Step 4.
4-99
SJ-20140527134643-015|2015-03-31 (R1.1)
4. Modify the configuration at the base station side, and configure the local port number to that of
the base station. Check whether the notification persists.
Yes -> Step 5.
No -> End.
5. View the association configuration at the base station side, and check whether the peer port
number of each association is 14592 or 14656 and is not repeatedly used by another associations.
Yes -> Step 7.
No -> Step 6.
6. Change the peer port number to 14592 or 14656 at the base station side, and ensure that the port
number is not repeatedly used by different associations. Check whether the notification persists.
Yes -> Step 7.
No -> End.
7. View the base station configuration at the BSC side, and check whether static associations
are configured for the base station.
Yes -> Step 8.
No -> Step 9.
8. Modify the association configuration at the base station side, ensure that the associations
configured at the base station side are consistent with the static associations at the BSC side,
and then delete the extra associations. Check whether the notification persists.
Yes -> Step 9.
No -> End.
4.94 199087520 Gb interface throughput exceed

permissible value
Notification code:
199087520
Notification name:
Gb interface throughput exceed permissible value
Minor
Notification type:
Qos Alarm
This alarm is reported if a board detects that the throughput of a Gb interface exceeds the permissible
value.
4-100
SJ-20140527134643-015|2015-03-31 (R1.1)
Notification Cause
The throughput of the Gb interface exceeds the configured permissible value continuously for several
times due to high PS traffic.
Impact
Some users fail to gain access to the system due to the automatically initiated flow control.
Action
The BSC will implement flow control automatically. Observing notifications is required without the
need of further operation. The capacity can be expanded if an increase of the upper limit of Gb
interface throughput is required.
4.95 199087521 Cell's home-processor transformed

Notification code:
199087521
Notification name:
Cell's home-processor transformed
Minor
Notification type:
Qos Alarm
This notification is reported if the BSC detects that the cell's home processor change.
Notification Cause
l
The type of the cell's home board changes.
The cell or TRX configuration in the CMP module changes.
Impact
A transient traffic interruption for several seconds occurs. CS and PS performance may be degraded.
Action
4-101
SJ-20140527134643-015|2015-03-31 (R1.1)
4.96 198087338 TRX No Traffic

Notification code:
198087338
Notification name:
TRX No Traffic
Minor
Notification type:
None
Notification Cause
Cell No Traffic
Impact
None.
Action
None
4.97 198087434 Cannot detect up or down TRAU

notification
Notification code:
198087434
Notification name:
Cannot detect up or down TRAU notification
Minor
Notification type:
None
Notification Cause
Cannot detect up or down TRAU
4-102
SJ-20140527134643-015|2015-03-31 (R1.1)
Impact
None.
Action
None
4.98 198087339 BTS self maintenance inform

Notification code:
198087339
Notification name:
BTS self maintenance inform
Minor
Notification type:
Equipment Alarm
None
Notification Cause
BTS Board Reboot
Impact
None.
Action
None
4.99 198087477 site board cpu overload

Notification code:
198087477
Notification name:
site board cpu overload
Major
Notification type:
Equipment Alarm
4-103
SJ-20140527134643-015|2015-03-31 (R1.1)
None
Notification Cause
CMB/DTPU/FIB CPU usage rate over 80%
Impact
None.
Action
None
4.100 198087478 uplink user layer jam inform

Notification code:
198087478
Notification name:
uplink user layer jam inform
Minor
Notification type:
None
Notification Cause
Uplink data in user layer is jaming
Impact
None.
Action
1) Modify to static channel, reserve not more than 4 channels for PS.
2) If 16 channels of 2 TRX all for PS, modify to static coding mode, and coding mode should Less
than MCS6. If EDGE not work, this restrict is not exist.
4-104
SJ-20140527134643-015|2015-03-31 (R1.1)
4.101 198087479 downlink user layer jam inform

Notification code:
198087479
Notification name:
downlink user layer jam inform
Minor
Notification type:
None
Notification Cause
Downlink data in user layer is jaming
Impact
None.
Action
1) Modify to static channel, reserve not more than 4 channels for PS.
2)If 16 channels of 2 TRX all for PS, modify to static coding mode, and coding mode should Less than
MCS6. If EDGE not work, this restrict is not exist.
4.102 198087488 chp cycle adjust trau information

Notification code:
198087488
Notification name:
chp cycle adjust trau information
Minor
Notification type:
None
4-105
SJ-20140527134643-015|2015-03-31 (R1.1)
Notification Cause
13MHz clock of Um is unsynchronized with HW 8K clock on DTRU.
Impact
CS and PS performance may be degraded.
Action
In E1 Abis mode, be sure 'clock synchronization' is network synchronization.
4.103 198087500 Radio Interface Synchronization ARF

emendate Successfully
Notification code:
198087500
Notification name:
Radio Interface Synchronization ARF emendate Successfully
Minor
Notification type:
None
Notification Cause
Search Radio Interface Synchronization Successfully.
Impact
None.
Action
Check the display of the value of ARFCN at OMM.
4-106
SJ-20140527134643-015|2015-03-31 (R1.1)
4.104 198087501 Radio Interface Synchronization ARF

emendate Failed
Notification code:
198087501
Notification name:
Radio Interface Synchronization ARF emendate Failed
Minor
Notification type:
None
Notification Cause
Search Radio Interface Synchronization Failed.
Impact
26 M frequency deviation correction fails to be executed.
Action
Check the reason of failure at iOMCR:
0x01 No suitable Arfcn
0x02 Radio Synchronization failed
0x03 Other.
4.105 198087502 Site IP Address conflicted

Notification code:
198087502
Notification name:
Site IP Address conflicted
Minor
Notification type:
Equipment Alarm
None
4-107
SJ-20140527134643-015|2015-03-31 (R1.1)
Notification Cause
Site IP Conflict
Impact
The site fails to operate properly.
Action
Remodify the IP of site
4.106 198087512 IDS Attack detecting

Notification code:
198087512
Notification name:
IDS Attack detecting
Minor
Notification type:
None
Notification Cause
IDS detecting the network attacking
Impact
User-defined.
Action
None
4-108
SJ-20140527134643-015|2015-03-31 (R1.1)
Appendix A
Link Information
Table of Contents
A1001..................................................................................................................... A-2
A1010..................................................................................................................... A-2
A1011 ..................................................................................................................... A-2
A1012..................................................................................................................... A-2
A1013..................................................................................................................... A-3
A1014..................................................................................................................... A-3
A1015..................................................................................................................... A-4
A1016..................................................................................................................... A-4
A1021..................................................................................................................... A-4
A1022..................................................................................................................... A-6
A1023..................................................................................................................... A-6
A1024..................................................................................................................... A-8
A2001..................................................................................................................... A-8
A2002..................................................................................................................... A-9
A2003................................................................................................................... A-11
A2005................................................................................................................... A-12
A2007................................................................................................................... A-13
A2009................................................................................................................... A-14
A2010................................................................................................................... A-15
A2011 ................................................................................................................... A-16
A2012................................................................................................................... A-18
A2013................................................................................................................... A-19
A2014................................................................................................................... A-20
A2015................................................................................................................... A-21
A2016................................................................................................................... A-22
A2017................................................................................................................... A-23
A2018................................................................................................................... A-25
A2019................................................................................................................... A-26
A2051................................................................................................................... A-27
A-1
SJ-20140527134643-015|2015-03-31 (R1.1)
A.1 A1001
Query the "Trunk" object in accordance with the "Mtp2 Link" object.
1. Query the "Logical E1(LogicalE1)" object that the "Mtp2 Link(Mtp2Link)" object
references.
2. Query
the
trunk
object
"E1
Port(E1Port)"/"VC12
Trail
in
VC3
Channel(Vc3Vc12Trail)"/"VC12
Trail
in
VC4
Channel(Vc12Trail)"/"VT-2
Trail(Vt2Trail)" that the "Logical E1(LogicalE1)" object references.
A.2 A1010
Query the corresponding trunk E1/T1 object.
1. For a "Logical E1(LogicalE1)" port, query the trunk object "E1 Port(E1Port)"/"VC12
Trail in VC3 Channel(Vc3Vc12Trail)"/"VC12 Trail in VC4 Channel(Vc12Trail)"/"VT-2
Trail(Vt2Trail)" that the "Logical E1(LogicalE1)" object references.
2. For a "Logical T1(LogicalT1)" port, query the trunk object "T1 Port(T1Port)"/"VC11
Trail in VC4 Channel(Vc4Vc11Trail)"/"VC11 Trail in VC3 Channel(Vc11Trail)"/"VT-1.5
Trail(Vt15Trail)" that the "Logical T1(LogicalT1)" object references.
A.3 A1011
Query the trunk ID corresponding to a port.
1. For a "Logical E1(LogicalE1)" port, query the trunk object "E1 Port(E1Port)"/"VC12
Trail in VC3 Channel(Vc3Vc12Trail)"/"VC12 Trail in VC4 Channel(Vc12Trail)"/"VT-2
Trail(Vt2Trail)" that the "Logical E1(LogicalE1)" object references, and obtain the
trunk ID "E1 Port No(E1PortSeq)"/"VC12 Trail No.(Vc3Vc12TrailSeq)"/"VC12 Trail
No.(Vc12TrailSeq)"/"VT-2 Trail No.(Vt2TrailSeq)".
2. For a "Logical T1(LogicalT1)" port, query the trunk object "T1 Port(T1Port)"/"VC11
Trail in VC4 Channel(Vc4Vc11Trail)"/"VC11 Trail in VC3 Channel(Vc11Trail)"/"VT-1.5
Trail(Vt15Trail)" that the "Logical T1(LogicalT1)" object references, and obtain the
trunk ID "T1 Port No(T1PortSeq)"/"VC11 Trail No.(Vc4Vc11TrailSeq)"/"VC11 Trail
No.(Vc11Seq)"/"VT-1.5 Trail No.(Vt15Seq)".
A.4 A1012
Query the "Ethernet Interface(EthernetTp)" object in accordance with "Port
Quintuplet" in the notification information.
Find the "Logical Ethernet Port(LogicalEthPort)" object in accordance with Port
Quintuplet (subsystem ID, unit ID, and port number) in the notification information, and
A-2
SJ-20140527134643-015|2015-03-31 (R1.1)
query the "Ethernet Interface(EthernetTp)" object that references the "Logical Ethernet
Port(LogicalEthPort)" object.
Note:
Note: Both Port Quintuplet and Information of the logical out port refer to Port
Quintuplet.
A.5 A1013
Obtain the trunk in accordance with the "Logical E1(LogicalE1)" object.
Query
the
trunk
object
"E1
Port(E1Port)"/"VC12
Trail
in
VC3
Channel(Vc3Vc12Trail)"/"VC12 Trail in VC4 Channel(Vc12Trail)"/"VT-2 Trail(Vt2Trail)"
that the "Logical E1(LogicalE1)" object references.
A.6 A1014
Query the IP Port object in accordance with Bfdsession.
In accordance with Source IP Address in the alarm information:
1. Query the "Ethernet IP Interface (IPv4)(EthIpIntf)" object, and check whether any of
the "IP Address 1(IpAddr1)", "IP Address 2(IpAddr2)", "IP Address 3(IpAddr3)", and
"IP Address 4(IpAddr4)" parameters matches the source IP address. If yes, obtain the
parent object "Ethernet Interface(EthernetTp)", and then obtain the referenced objects
"Logical Ethernet Port(LogicalEthPort)" and "Ethernet Port(EthernetPort)" in order.
2. If no result is obtained in Step 1, query the "Ethernet Sub Interface
(IPv4)(EthIpSubIntf)" object, and check whether any of the "IP address 1(IpAddr1)",
"IP address 2(IpAddr2)", "IP address 3(IpAddr3)", and "IP address 4(IpAddr4)"
parameters matches the source IP address. If yes, obtain the parent object "Ethernet
Interface(EthernetTp)", and then obtain the referenced objects "Logical Ethernet
Port(LogicalEthPort)" and "Ethernet Port(EthernetPort)" in order.
3. If no result is obtained in Step 2, query the "Ethernet Channel IP Interface
(IPv4)(EthChIpIntf)" object, and check whether any of the "IP Address 1(IpAddr1)",
"IP Address 2(IpAddr2)", "IP Address 3(IpAddr3)", and "IP Address 4(IpAddr4)"
parameters matches the source IP address. If yes, obtain the parent object
"Ethernet Channel Group(EthChannel)", obtain its child object "Ethernet Channel
Member Port(EthChMember)", and then obtain the referenced objects "Ethernet
Interface(EthernetTp)", "Logical Ethernet Port(LogicalEthPort)", and "Ethernet
Port(EthernetPort)" in order.
4. If no result is obtained in Step 3, query the "Ethernet Channel Sub Interface
(IPv4)(EthChIpSubIntf)" object, and check whether any of the "IP address 1(IpAddr1)",
A-3
SJ-20140527134643-015|2015-03-31 (R1.1)
parameters matches the source IP address. If yes, obtain the parent object
"Ethernet Channel Group(EthChannel)", obtain its child object "Ethernet Channel
Member Port(EthChMember)", and then obtain the referenced objects "Ethernet
Interface(EthernetTp)", "Logical Ethernet Port(LogicalEthPort)", and "Ethernet
Port(EthernetPort)" in order.
A.7 A1015
Obtain the E1/T1 frame format in accordance with the "Logical E1(LogicalE1)" or
"Logical T1(LogicalT1)" object.
Query the "E1 Port(E1Port)"/"VC12 Trail in VC3 Channel(Vc3Vc12Trail)"/"VC12 Trail in
VC4 Channel(Vc12Trail)"/"VT-2 Trail(Vt2Trail)" object that the "Logical E1(LogicalE1)"
object references, and obtain the "E1 Frame Type(Crc4Mode)" parameter. Or query
the "T1 Port(T1Port)"/"VC11 Trail in VC4 Channel(Vc4Vc11Trail)"/"VC11 Trail in VC3
Channel(Vc11Trail)"/"VT-1.5 Trail(Vt15Trail)" object that the "Logical T1(LogicalT1)"
object references, and obtain the "T1 Frame Format(FrameFormat)" parameter.
A.8 A1016
Query the IP Interface of ML-PPP Group (MlpppTpIpIntf) object or the IP Interface
of PPP Link (PppIpIntf) object in accordance with the Port Quintuplet parameter
in the alarm information.
Query the "CPU Sunit(CpuSunit)" object in accordance with the Port Quintuplet
(Subsystem ID, Unit number, and Port number) parameter in the alarm information,
locate the "ML-PPP Group(MlpppTp)" object associated with the "CPU Sunit(CpuSunit)"
object, and then locate the sub-object "IP Interface of ML-PPP Group(MlpppTpIpIntf)".
Alternatively, query the "PPP Link(PppTp)" object associated with the "CPU
Sunit(CpuSunit)" object, and locate the sub-object "IP Interface of PPP Link(PppIpIntf)"
of the "PPP Link(PppTp)" object.
A.9 A1021
Query the interface object in accordance with Interface IP address in the alarm
information.
If the interface IP address is an IPv4 address, perform the following steps to query the
interface object in accordance with Interface IP address in the alarm information.
1. Query the "Ethernet IP Interface (IPv4)(EthIpIntf)" object, and check whether any of
"IP Address 4(IpAddr4)" parameters matches the interface IP address. If yes, obtain
the interface object.
A-4
SJ-20140527134643-015|2015-03-31 (R1.1)

(IPv4)(EthIpSubIntf)" object, and check whether any of the "IP address 1(IpAddr1)",
parameters matches the interface IP address. If yes, obtain the interface object.
(IPv4)(EthChIpIntf)" object, and check whether any of the "IP Address 1(IpAddr1)",
(IPv4)(EthChIpSubIntf)" object, and check whether any of the "IP address 1(IpAddr1)",
5. If no result is obtained in Step 4, query the "Virtual IP Interface(VIpIntf)" object, and
check whether any of the "IP address 1(IpAddr1)", "IP Address 2(IpAddr2)", "IP
Address 3(IpAddr3)", and "IP Address 4(IpAddr4)" parameters matches the interface
IP address. If yes, obtain the interface object.
6. If no result is obtained in Step 5, query the "Loopback IP Interface(LbIpIntf)" object,
and check whether any of the "IP address 1(IpAddr1)", "IP Address 2(IpAddr2)", "IP
If the interface IP address is an IPv6 address, perform the following steps to query the
interface object in accordance with Interface IP address in the alarm information.
1. Query the "Ethernet IP Interface (IPv6)(EthIpv6Intf)" object, and check whether any of
"IP Address 4(IpAddr4)" parameters matches the interface IP address. If yes, obtain
the interface object.
(IPv6)(EthIpv6SubIntf)" object, and check whether any of the "IP Address 1(IpAddr1)",
(IPv6)(EthChIpv6Intf)" object, and check whether any of the "IP Address 1(IpAddr1)",
(IPv6)(EthChIpv6SubIntf)" object, and check whether any of the "IP Address
1(IpAddr1)", "IP Address 2(IpAddr2)", "IP Address 3(IpAddr3)", and "IP Address
4(IpAddr4)" parameters matches the interface IP address. If yes, obtain the interface
object.
5. If no result is obtained in Step 4, query the "Virtual IP Interface(VIpIntf)" object, and
check whether any of the "IP address 1(IpAddr1)", "IP Address 2(IpAddr2)", "IP
A-5
SJ-20140527134643-015|2015-03-31 (R1.1)
6. If no result is obtained in Step 5, query the "Loopback IP Interface(LbIpIntf)" object,

and check whether any of the "IP address 1(IpAddr1)", "IP Address 2(IpAddr2)", "IP
A.10 A1022
Query the "Ethernet Vlan Sub Interface(EthernetVlanTp)" or "Vlan Sub Interface of
Channel Group(EthChVlanTp)" object in accordance with Information of the logical
member port in the notification information.
Obtain the subsystem number, unit number, and port number in accordance with
"Information of the logical member port" in the notification information, and resolve the
port number.
1. If bit 12 of the port number is 0, obtain the physical interface number corresponding
to the subinterface in accordance with bits 1623 of the port number, and
obtain the subinterface number in accordance with bits 011 of the port number.
Query the "Logical Ethernet Port(LogicalEthPort)" object in accordance with
the subsystem number, unit number, and physical interface number, query the
"Ethernet Interface(EthernetTp)" object that references the "Logical Ethernet
Port(LogicalEthPort)" object, and then query the child object "Ethernet Vlan
Sub Interface(EthernetVlanTp)" of the "Ethernet Interface(EthernetTp)" object in
accordance with the subinterface number.
2. If bit 12 of the port number is 1, obtain the aggregate port number corresponding
to the subinterface in accordance with bits 1623 of the port number, and obtain
the subinterface number in accordance with bits 011. Query the "Logical Ethernet
Port(LogicalEthPort)" object in accordance with the subsystem number, unit number,
and physical interface number, query the "Ethernet Interface(EthernetTp)" object that
references the "Logical Ethernet Port(LogicalEthPort)" object, and then query the
child object "Vlan Sub Interface of Channel Group(EthChVlanTp)" of the "Ethernet
Channel Group(EthChannel)" object in accordance with the subinterface number.
A.11 A1023
Query the "PTP Interface Configuration(PtpPort)" object in accordance with Slave
port information of interrupted PTP in the alarm information.
Obtain "subsystem ID", "module ID", "unit ID", "sub-unit ID", and "Port number" of the
interface in accordance with "Slave port information of interrupted PTP" in the alarm
information. Resolve the port number, and obtain the port type in accordance with bits
1215 of the port number.
1. If the port type is 0 and bits 1623 of the port number is 0, it indicates that it is a
physical interface. Obtain the physical interface number in accordance with bits
07 of the port number. Query the "Logical Ethernet Port(LogicalEthPort)" object
A-6
SJ-20140527134643-015|2015-03-31 (R1.1)
in accordance with the subsystem number, unit number, and physical interface
number, query the "Ethernet Interface(EthernetTp)" object that references the
"Logical Ethernet Port(LogicalEthPort)" object, query the child object "Ethernet
IP Interface (IPv4)(EthIpIntf)" of the "Ethernet Interface(EthernetTp)" object, and
then query the "PTP Interface Configuration(PtpPort)" object that references
the "Ethernet IP Interface (IPv4)(EthIpIntf)" object.
If the "PTP Interface
Configuration(PtpPort)" object cannot be found, query the child object "Ethernet
IP Interface (IPv6)(EthIpv6Intf)" of the "Ethernet Interface(EthernetTp)" object, and
query the "PTP Interface Configuration(PtpPort)" object that references the "Ethernet
IP Interface (IPv6)(EthIpv6Intf)" object.
2. If the port type is 0 and bits 1623 of the port number is not 0, it indicates that
it is a subinterface of a physical interface. Obtain the physical interface number
corresponding to the subinterface in accordance with bits 1623 of the port number,
and the subinterface number in accordance with bits 011. Query the "Logical
Ethernet Port(LogicalEthPort)" object in accordance with the subsystem number, unit
number, and physical interface number. Query the "Ethernet Interface(EthernetTp)"
object that references the "Logical Ethernet Port(LogicalEthPort)" object, query
the child object "Ethernet Vlan Sub Interface(EthernetVlanTp)" of the "Ethernet
Interface(EthernetTp)" object in accordance with the subinterface number, query
the child object "Ethernet Sub Interface (IPv4)(EthIpSubIntf)" of the "Ethernet
Vlan Sub Interface(EthernetVlanTp)" object, and then query the "PTP Interface
Configuration(PtpPort)" object that references the "Ethernet Sub Interface
(IPv4)(EthIpSubIntf)" object. If the "PTP Interface Configuration(PtpPort)" object
cannot be found, query the child object "Ethernet Sub Interface (IPv6)(EthIpv6SubIntf)"
of the "Ethernet Vlan Sub Interface(EthernetVlanTp)" object, and then query the "PTP
Interface Configuration(PtpPort)" object that references the "Ethernet Sub Interface
(IPv6)(EthIpv6SubIntf)" object.
3. If the port type is 1 and bits 1623 of the port number is 0, it indicates that it is
an aggregate port. Obtain the aggregate port number in accordance with bits
07 of the port number, and query the "Ethernet Channel Group(EthChannel)"
object in accordance with the aggregate port number. Query the child object
"Ethernet Channel IP Interface (IPv4)(EthChIpIntf)" of the "Ethernet Channel
Group(EthChannel)" object, and query the "PTP Interface Configuration(PtpPort)"
object that references the "Ethernet Channel IP Interface (IPv4)(EthChIpIntf)"
object. If the "PTP Interface Configuration(PtpPort)" object cannot be found,
query the child object "Ethernet Channel IP Interface (IPv6)(EthChIpv6Intf)" of the
"Ethernet Channel Group(EthChannel)" object, and then query the "PTP Interface
Configuration(PtpPort)" object that references the "Ethernet Channel IP Interface
(IPv6)(EthChIpv6Intf)" object.
4. If the port type is 1 and bits 1623 of the port number is not 0, it indicates that it is a
subinterface of an aggregate port. Obtain the aggregate port number in accordance
with bits 07 of the port number and the subinterface number in accordance with bits
011. Query the "Ethernet Channel Group(EthChannel)" object in accordance with
the aggregate port number, and query the child object "Vlan Sub Interface of Channel
Group(EthChVlanTp)" of the "Ethernet Interface(EthernetTp)" object in accordance
A-7
SJ-20140527134643-015|2015-03-31 (R1.1)
with the subinterface number. Query the child object "Ethernet Channel Sub Interface
(IPv4)(EthChIpSubIntf)" of the "Vlan Sub Interface of Channel Group(EthChVlanTp)"
object, and then query the "PTP Interface Configuration(PtpPort)" object that
references the "Ethernet Channel Sub Interface (IPv4)(EthChIpSubIntf)" object. If
the "PTP Interface Configuration(PtpPort)" object cannot be found, query the child
object "Ethernet Channel Sub Interface (IPv6)(EthChIpv6SubIntf)" of the "Vlan Sub
Interface of Channel Group(EthChVlanTp)" object, and then query the "PTP Interface
Configuration(PtpPort)" object that references the "Ethernet Channel Sub Interface
(IPv6)(EthChIpv6SubIntf)" object.
5. If the port type is 12, it indicates that it is a SuperVlan port. Obtain the SuperVlan port
number in accordance with bits 07 of the port number, and query the "Super Vlan
Interface(SuperVlan)" object in accordance with the SuperVlan port number. Query
the child object "Super Vlan IP Interface (IPv4)(EthSuperIpIntf)" of the "Super Vlan
Interface(SuperVlan)" object, and query the "PTP Interface Configuration(PtpPort)"
object that references the "Super Vlan IP Interface (IPv4)(EthSuperIpIntf)"
object. If the "PTP Interface Configuration(PtpPort)" object cannot be found,
query the child object "Super Vlan IP Interface (IPv6)(EthSuperIpv6Intf)" of the
"Super Vlan Interface(SuperVlan)" object, and then query the "PTP Interface
Configuration(PtpPort)" object that references the "Super Vlan IP Interface
(IPv6)(EthSuperIpv6Intf)" object.
A.12 A1024
Query the physical location of the interface board in accordance with Slave port
information of interrupted PTP in the alarm information.
Obtain the "subsystem ID" and "unit ID" of the interface in accordance with "Slave port
information of interrupted PTP" in the notification information. Query the "Unit(Unit)"
object in accordance with "subsystem ID" and "unit ID", query the first referenced object
"Board(Board)" of the "Unit(Unit)" object, and obtain the physical address of the interface
board in accordance with the "Description(description)" parameter of the "Board(Board)"
object.
A.13 A2001
Run the START DTM command to perform a system loopback test on the SDH
optical port in accordance with the alarm object and "Rack number", "Shelf number",
"Slot number", "CPU number", and "Optical port index" in the alarm information.
Command example
START DTM:TESTTYPE=DTM_V4_LOOPSET_TEST, OBJTYPE="SDH Optical Port",
MOC="S155Port", MOI="SubNetwork=35, MEID=35, Equipment=1, Rack=1, Shelf=3,
Board=1, S155Port=1", ATTRIBUTES="RackNo=1, ShelfNo=3, SlotNo=1, CpuNo=1,
LoopType=1, LoopMode=2, LogicPort=1, PortFlag=0", TESTSEQ="1";
A-8
SJ-20140527134643-015|2015-03-31 (R1.1)
Parameter descriptions
"TESTTYPE"
Select "DTM_V4_LOOPSET_TEST".
"OBJTYPE"
Enter the test object type "SDH Optical Port".
"MOC"
Enter the MOC "S155Port" or "S622Port", depending on the alarm object DN

field. If the DN field is "Equipment=1, Rack=1, Shelf=3, Board=1, S155Port=1",
set this parameter to "S155Port". If the DN field is "Equipment=1, Rack=1,
Shelf=3, Board=1, S622Port=1", set this parameter to "S622Port" (last MOC in
the DN field).
"MOI"
Enter the test object DN, which is obtained from the alarm object DN in
the alarm information. Alarm object DN example: "Equipment=1, Rack=1,
Shelf=3, Board=1, S155Port=1". Add the "SubNetwork=XXX" and "MEID=XXX"
parameters before the alarm object DN.
"ATTRIBUTES"
Enter specific parameters.

RackNo
Rack number of the test object.
ShelfNo
Shelf number of the test object.
SlotNo
Slot number of the test object.
CpuNo
CPU number of the test object.
LoopType
Enter "1", indicating SDH optical interface loopback.
LoopMode
Loopback mode, options:

l
"0" :Loopback cancellation.
"1" :Line loopback.
"2":System loopback.
"3":Cell loopback. In this example, LoopMode is set to

"2". To cancel loopback, set it to "0".
"TESTSEQ"
LogicPort
Optical interface number.
PortFlag
Port protection attribute. Options:

l
"0":Operational port.
"1":Protection port. Normally, PortFlag is set to "0".
Enter any integer from 1 to 200.
A.14 A2002
Run the START DTM command to cancel the loopback test on the SDH optical
port in accordance with the alarm object and "Rack number", "Shelf number", "Slot
number", "CPU number", and "Optical port index" in the alarm information.
Command example
A-9
SJ-20140527134643-015|2015-03-31 (R1.1)

Parameter description
"TESTTYPE"
"OBJTYPE"
"MOC"
Enter the MOC "S155Port" or "S622Port", depending on the alarm object DN

field. If the DN field is "Equipment=1, Rack=1, Shelf=3, Board=1, S155Port=1",
set this parameter to "S155Port". If the DN field is "Equipment=1, Rack=1,
Shelf=3, Board=1, S622Port=1", set this parameter to "S622Port" (last MOC in
the DN field).
"MOI"
Enter the test object DN, which is obtained from the alarm object DN in the alarm
information. Alarm object DN example: "Equipment=1, Rack=1, Shelf=3, Board=1,
S155Port=1". Add the "SubNetwork=XXX" and "MEID=XXX" parameters before
the alarm object DN.
"ATTRIBUTES"
"TESTSEQ"

RackNo
ShelfNo
SlotNo
CpuNo
LoopType
LoopMode

l
"0":Loopback cancellation.
"1":Line loopback.
"3":Cell loopback. In this example, LoopMode is set to "0".
LogicPort
PortFlag

l
A-10
SJ-20140527134643-015|2015-03-31 (R1.1)
A.15 A2003
Run the START DTM command to perform a local loopback test on the trunk
in accordance with the alarm object and "Rack number", "Shelf number", "Slot
number", "CPU number", "Primary device index", and "Secondary device index" in
Command example
START DTM:TESTTYPE=DTM_V4_LOOPSET_TEST, OBJTYPE="E1 Optical Trunk",
MOC="Vc12Trail", MOI="SubNetwork=35, MEID=35, Equipment=1,Rack=1, Shelf=3,
Board=1, S155Port=1, Vc4Trail=1, Vc12Trail=2", ATTRIBUTES="RackNo=1,
ShelfNo=3, SlotNo=1, CpuNo=1, LoopType=8, LoopMode=0, Unit=1, PortE1T1=2",
TESTSEQ="1";
"TESTTYPE"
"OBJTYPE"
Enter the test object type "E1 Electric Trunk", "T1 Electric Trunk", "E1 Optical
Trunk", or "T1 Optical Trunk" in accordance with the MOC description.
"MOC"
Enter the MOC "E1Port", "T1Port", "Vt15Trail", "Vt2Trail", "Vc11Trail",

"Vc3Vc12Trail", "Vc12Trail", or "Vc4Vc11Trail", depending on the alarm object DN
field in the alarm information. Alarm object DN example: "Equipment=1, Rack=1,
Shelf=3, Board=1, S155Port=1, Vc4Trail=1, Vc12Trail=2". Enter the last MOC in
the DN field. If MOC is "E1Port", set "OBJTYPE" to "E1 Electric Trunk". If MOC
is "T1Port", set "OBJTYPE" to "T1 Electric Trunk". If MOC is "Vc3Vc12Trail",
"Vc12Trail", or "Vt2Trail", set "OBJTYPE" to "E1 Optical Trunk". If MOC is
"Vc11Trail", "Vc4Vc11Trail", or "Vt15Trail", set "OBJTYPE" to "T1 Optical Trunk".
"MOI"
Enter the test object DN, which is obtained from the alarm object DN in the
alarm information. Alarm object DN example: "Equipment=1, Rack=1, Shelf=3,
Board=1, S155Port=1, Vc4Trail=1, Vc12Trail=2". Add the "SubNetwork=XXX" and
"MEID=XXX" parameters before the alarm object DN.
"ATTRIBUTES"

RackNo
ShelfNo
SlotNo
CpuNo
LoopType
Enter "8", indicating trunk loopback.
LoopMode

l
"0":Local loopback.
"1":Load loopback.
"2":Remote loopback.
A-11
SJ-20140527134643-015|2015-03-31 (R1.1)
"3":Channel loopback.
"4":Loopback cancellation. In this example, LoopMode is

set to "0". To cancel the local loopback test, set it to "4".
Unit
Enter "Primary device index" in the alarm information.
PortE1T1
Secondary device index, which means "Secondary device

"TESTSEQ"
A.16 A2005
Run the START DTM command to perform a local loopback test on the SDH
optical port in accordance with the alarmed object and the "Rack number", "Shelf
number", "Slot number", "CPU number", "Optical port index", and Secondary
device index in the alarm information.
Command example
TESTSEQ="1";
"TESTTYPE"
"OBJTYPE"
Trunk", or "T1 Optical Trunk", depending on the MOC description.
"MOC"

"MOI"
A-12
SJ-20140527134643-015|2015-03-31 (R1.1)
"ATTRIBUTES"

RackNo
ShelfNo
SlotNo
CpuNo
LoopType
LoopMode

l
"0":Local loopback.
"1":Load loopback.

Unit
Primary device index, which means "Optical port index" in the

alarm information.
PortE1T1

"TESTSEQ"
A.17 A2007
Run the START DTM command to perform a local loopback test on the SDH
optical port in accordance with the alarmed object and the "Rack number", "Shelf
number", "Slot number", "CPU number", "Optical port index", and Trunk ID in
Command example
TESTSEQ="1";
"TESTTYPE"
"OBJTYPE"
A-13
SJ-20140527134643-015|2015-03-31 (R1.1)
"MOC"

"MOI"
"ATTRIBUTES"

RackNo
ShelfNo
SlotNo
CpuNo
LoopType
LoopMode

l
"0":Local loopback.
"1":Load loopback.

Unit
Enter the primary device index, which means "Optical port

PortE1T1
Enter the secondary device index, which means "Trunk ID" in

"TESTSEQ"
A.18 A2009
Run the START DTM command to perform a diagnosis test to the board in
accordance with Rack number, Shelf number, Slot number, and CPU number
Command example
A-14
SJ-20140527134643-015|2015-03-31 (R1.1)
START DTM:TESTTYPE=DIAG_BOARD_TEST, OBJTYPE="Board", MOC="PhysCpu",

MOI="SubNetwork=35, MEID=35, Equipment=1,Rack=1, Shelf=2, Board=7, PhysCpu
=1", ATTRIBUTES="RackNo=1, ShelfNo=2, SlotNo=7, CpuNo=1", TESTSEQ="1";
"TESTTYPE"
Select "DIAG_BOARD_TEST".
"OBJTYPE"
Enter the test object type "Board".
"MOC"
Enter the MOC "PhysCpu".
"MOI"
Enter the test object DN.
"ATTRIBUTES"
"TESTSEQ"
RackNo
Rack number of the tested board.
ShelfNo
Shelf number of the tested board.
SlotNo
Slot number of the tested board.
CpuNo
Number of the first physical CPU of the tested board.
A.19 A2010
Run the START DTM command in accordance with the trunk E1/T1 object
obtained in Step 5 to check whether local loopback is configured on the trunk.
Command example
START DTM:TESTTYPE=DTM_V4_LOOPQRY_TEST, OBJTYPE="Board", MOC="Phy
sCpu", MOI="SubNetwork=35, MEID=35, Equipment=1,Rack=1, Shelf=3, Board=1, Phy
sCpu=1", ATTRIBUTES="RackNo=1, ShelfNo=3, SlotNo=1, CpuNo=1", TESTSEQ="1";
"TESTTYPE"
Select "DTM_V4_LOOPQRY_TEST".
"OBJTYPE"
"MOC"
"MOI"
Enter the test object DN. The rack number, shelf number, and board number
are obtained from the trunk E1/T1 object DN. Trunk E1/T1 object DN example,
"SubNetwork=35, MEID=35, Rack=1, Shelf=3, Board=1, S155Port=1, Vc4Trail=1,
Vc12Trail=2", where the rack number, shelf number, and board number can be
obtained from the "Rack=XX, Shelf=YY, Board=ZZ" fields. PhysCpu is fixed to 1.
A-15
SJ-20140527134643-015|2015-03-31 (R1.1)
"ATTRIBUTES"

RackNo
Rack number of the object, which means the Rack parameter

in "MOI".
ShelfNo
Shelf number of the object, which means the Shelf parameter

in "MOI".
SlotNo
Slot number of the object, which means the Board parameter

in "MOI".
CpuNo
Number of the first physical CPU of the tested board, which

means the PhysCpu parameter in "MOI".
"TESTSEQ"
A.20 A2011
Run the START DTM command to cancel the loopback in accordance with the
trunk E1/T1 object obtained in Step 5.
Command example
TESTSEQ="1";
"TESTTYPE"
"OBJTYPE"
"MOC"

"Vc3Vc12Trail", "Vc12Trail", or "Vc4Vc11Trail", depending on the trunk E1/T1
object DN field. Trunk E1/T1 object DN example: "Equipment=1, Rack=1,
"MOI"
Enter the test object DN, which is obtained from the trunk E1/T1 object DN field.
A-16
SJ-20140527134643-015|2015-03-31 (R1.1)
"ATTRIBUTES"

RackNo

in "MOI".
ShelfNo

in "MOI".
SlotNo

in "MOI".
CpuNo
CPU number of the test object, which is fixed to 1.
LoopType
LoopMode

l
"0":Local loopback.
"1":Load loopback.
"4":Loopback cancellation. In this example, LoopMode
is set to "4".
Unit
Primary device index, obtained in accordance with the

"Description" field of the trunk E1/T1 object. If "OBJTYPE"
is "E1 Electric Trunk", the "Description" field may be
"E1PortSeq=12,Slot=27,ShelfSeq=2,RackSeq=1", where
E1PortSeq indicates the secondary device index, so
the primary device index is 0. If "OBJTYPE" is "E1
Optical Trunk" or "T1 Optical Trunk", the "Description"
field may be "Vc12TrailSeq=12,Vc4TrailSeq=1,S155PortSeq=1,Slot=27,ShelfSeq=2,RackSeq=1", where the first
XXXSeq parameter (in this example, Vc12TrailSeq, depending
on the MOC) indicates the secondary device index, and the
S155PortSeq parameter (which is included in all the MOCs)
indicates the primary device index.
PortE1T1
Secondary device index, which is obtained from the

"Description" field of the trunk E1/T1 object. For details, refer
to the "Unit" parameter description.
"TESTSEQ"
A-17
SJ-20140527134643-015|2015-03-31 (R1.1)
A.21 A2012
Run the START DTM command to read SDH values of the SDH optical port, and
query the J0 receiving value, expected value, and sending value of the faulty optical
port in accordance with the alarm object and Rack number, Shelf number, Slot
number, CPU number, and Optical port index in the alarm information.
Command example
START DTM:TESTTYPE=DTM_V4_SDHCFGGET_TEST, OBJTYPE="Segment Port",
MOC="S155Port", MOI="SubNetwork=35, MEID=35, Equipment=1,Rack=1, Shelf=3,
LogicPort=1, PortFlag=0, CfgType=11", TESTSEQ="1";
"TESTTYPE"
Select "DTM_V4_SDHCFGGET_TEST".
"OBJTYPE"
Enter the test object type "Segment Por".
"MOC"
Enter the MOC "S155Port" or "S622Port", depending on the alarm object DN field
in the alarm information. Alarm object DN example: "Equipment=1, Rack=1,
Shelf=3, Board=1, S155Port=1". Enter the last MOC in the DN field.
"MOI"
S155Port=1". Add the "SubNetwork=XXX" and "MEID=XXX" parameters before
the alarm object DN.
"ATTRIBUTES"

RackNo
Rack number of the test object, which means "Rack number"

ShelfNo
Shelf number of the test object, which means "Shelf number"

SlotNo
Slot number of the test object, which means "Slot number" in

CpuNo
CPU number of the test object, which means "CPU number" in

LogicPort
Logical port number, which means "Optical port index" in the

alarm information.
PortFlag

l
l
l
A-18
SJ-20140527134643-015|2015-03-31 (R1.1)
CfgType
Configuration type, options:

l
"11":J0 Trail Identifier Message (J0)
"16":Synchronization Status (S1)
"17":Signal Fail Threshold (SF)
"18":Signal Degradation Threshold (SD). In this example,

"CfgType" is set to "11".
"TESTSEQ"
A.22 A2013
Query the trunk E1/T1 object in accordance with "Subsystem ID", "Unit Number",
"TC Index", and "CPU Index" in the alarm information, and run the START DTM
command to perform a local loopback test on the trunk.
Command example
TESTSEQ="1";
"TESTTYPE"
"OBJTYPE"
"MOC"

"Vc3Vc12Trail", "Vc12Trail", or "Vc4Vc11Trail", depending on the trunk E1/T1
object DN field. Trunk E1/T1 object DN example: "Equipment=1, Rack=1,
"MOI"
Enter the test object DN, which is obtained from the trunk E1/T1 object DN field.
"ATTRIBUTES"

RackNo

in "MOI".
ShelfNo

in "MOI".
A-19
SJ-20140527134643-015|2015-03-31 (R1.1)
SlotNo

in "MOI".
CpuNo
CPU number of the test object, which is fixed to 1.
LoopType
LoopMode

l
"0":Local loopback.
"1":Load loopback.

is set to "0".
Unit
Primary device index, obtained in accordance with the

"Description" field of the trunk E1/T1 object. If "OBJTYPE"
is "E1 Electric Trunk", the "Description" field may be
"E1PortSeq=12,Slot=27,ShelfSeq=2,RackSeq=1", where
E1PortSeq indicates the secondary device index, so
the primary device index is 0. If "OBJTYPE" is "E1
Optical Trunk" or "T1 Optical Trunk", the "Description"
field may be "Vc12TrailSeq=12,Vc4TrailSeq=1,S155PortSeq=1,Slot=27,ShelfSeq=2,RackSeq=1", where the first
XXXSeq parameter (in this example, Vc12TrailSeq, depending
on the MOC) indicates the secondary device index, and the
S155PortSeq parameter (which is included in all the MOCs)
indicates the primary device index.
PortE1T1
Secondary device index, which is obtained from the

"Description" field of the trunk E1/T1 object. For details, refer
to the "Unit" parameter description.
"TESTSEQ"
A.23 A2014
Run the START DTM command to cancel the CSU loopback in accordance with
the alarm object and "Rack number", "Shelf number", "Slot number", "CPU number",
"Primary device index", and "Secondary device index" in the alarm information.
Command example
START DTM:TESTTYPE=DTM_V4_LOOPSET_TEST, OBJTYPE="T1 CSU Trunk", MO
C="T1Port", MOI="SubNetwork=35, MEID=35, Equipment=1,Rack=1, Shelf=3, Board
=1, T1Port=1", ATTRIBUTES="RackNo=1, ShelfNo=3, SlotNo=1, CpuNo=1, LoopTyp
e=5, LoopMode=1, Unit=0, PortE1T1=5", TESTSEQ="1";
A-20
SJ-20140527134643-015|2015-03-31 (R1.1)
"TESTTYPE"
"OBJTYPE"
Enter the test object type "T1 CSU Trunk".
"MOC"
Enter the MOC "T1Port".
"MOI"
Board=1, T1Port=1". Add the "SubNetwork=XXX" and "MEID=XXX" parameters
before the alarm object DN.
"ATTRIBUTES"

RackNo

ShelfNo

SlotNo

CpuNo
CPU number of the test object, which means "CPU number" in

LoopType
Enter "5", indicating T1 CSU loopback.
LoopMode

l
"1":Enables loopback.
"2":Disables loopback.
"3":Disables local loopback. In this example, LoopMode

is set to "2".
Unit
Primary device number, which means "Primary device index"

PortE1T1
Secondary device number, which means "Secondary device

"TESTSEQ"
A.24 A2015
Run the START DTM command to check whether the trunk has local loopback
in accordance with the alarm object and "Rack number", "Shelf number", "Slot
number", "CPU number", "Primary device index", and "Secondary device index" in
Command example
A-21
SJ-20140527134643-015|2015-03-31 (R1.1)
START DTM:TESTTYPE=DTM_V4_LOOPQRY_TEST, OBJTYPE="Board", MOC

="PhysCpu", MOI="SubNetwork=35, MEID=35, Equipment=1,Rack=1, Shelf=3,
Board=1, PhysCpu=1", ATTRIBUTES="RackNo=1, ShelfNo=3, SlotNo=1, CpuNo=1",
TESTSEQ="1";
"TESTTYPE"
Select "DTM_V4_LOOPQRY_TEST".
"OBJTYPE"
"MOC"
"MOI"
Enter the test object DN, where the Rack, Shelf, Board, and PhysCpu parameters
correspond to RackNo, ShelfNo, SlotNo, and CpuNo respectively in the
"ATTRIBUTES" parameter.
"ATTRIBUTES"

RackNo

ShelfNo

SlotNo

CpuNo
Number of the first physical CPU of the tested board, which

means "CPU number" in the alarm information.
"TESTSEQ"
A.25 A2016
Cancel the loopback test on the trunk.
Command example
TESTSEQ="1";
"TESTTYPE"
"OBJTYPE"
A-22
SJ-20140527134643-015|2015-03-31 (R1.1)
"MOC"

"MOI"
"ATTRIBUTES"

RackNo
ShelfNo
SlotNo
CpuNo
LoopType
LoopMode

l
"0":Local loopback.
"1":Load loopback.

is set to "4".
Unit
Enter "Primary device index" in the alarm information.
PortE1T1

"TESTSEQ"
A.26 A2017
Command example
A-23
SJ-20140527134643-015|2015-03-31 (R1.1)

"TESTTYPE"
"OBJTYPE"
"MOC"
Enter the MOC "S155Port" or "S622Port", depending on the alarm object DN field.
If the DN field is like "Equipment=1, Rack=1, Shelf=3, Board=1, S155Port=1,
Vc4Trail=1", set this parameter to "S155Port". If the DN field is like "Equipment=1,
Rack=1, Shelf=3, Board=1, S622Port=1,Vc44cTrail=1", set this parameter to
"S622Port".
"MOI"
Board=1, S155Port=1, Vc4Trail=1". Extract the DN of S155Port or S622Port,
and add the "SubNetwork=XXX" and "MEID=XXX" parameters before the
S155Port/S622Port DN.
"ATTRIBUTES"

RackNo
ShelfNo
SlotNo
CpuNo
LoopType
LoopMode

l
"1":Line loopback.

"TESTSEQ"
LogicPort
PortFlag

l
A-24
SJ-20140527134643-015|2015-03-31 (R1.1)
A.27 A2018
Run the START DTM command to cancel the loopback test on the SDH optical
port in accordance with the alarm object and "Rack number", "Shelf number", "Slot
number", "CPU number", and "Optical port index" in the alarm information.
Command example
"TESTTYPE"
"OBJTYPE"
"MOC"
Enter the MOC "S155Port" or "S622Port", depending on the alarm object DN field.
If the DN field is like "Equipment=1, Rack=1, Shelf=3, Board=1, S155Port=1,
Vc4Trail=1", set this parameter to "S155Port". If the DN field is like "Equipment=1,
Rack=1, Shelf=3, Board=1, S622Port=1,Vc44cTrail=1", set this parameter to
"S622Port".
"MOI"
Board=1, S155Port=1, Vc4Trail=1". Extract the DN of S155Port or S622Port,
and add the "SubNetwork=XXX" and "MEID=XXX" parameters before the
S155Port/S622Port DN.
"ATTRIBUTES"

RackNo
ShelfNo
SlotNo
CpuNo
LoopType
LoopMode

l
"1":Line loopback.
"3":Cell loopback. In this example, LoopMode is set to "0".
LogicPort
PortFlag

l
A-25
SJ-20140527134643-015|2015-03-31 (R1.1)
l
"TESTSEQ"
A.28 A2019
Command example
"TESTTYPE"
"OBJTYPE"
"MOC"
Enter the MOC "S155Port".
"MOI"
S155Port=1, Vc4Trail=1, Vc12Trail=2". Extract the S155Port DN, and add the
"SubNetwork=XXX" and "MEID=XXX" parameters before the S155Port DN.
"ATTRIBUTES"

RackNo
ShelfNo
SlotNo
CpuNo
LoopType
LoopMode

l
"1":Line loopback.

LogicPort
PortFlag

l
A-26
SJ-20140527134643-015|2015-03-31 (R1.1)
l
"TESTSEQ"
A.29 A2051
Run the START DTM command to perform a diagnosis test to the board and check
the status of all the RUB resource boards.
Command example
START DTM:TESTTYPE=DIAG_BOARD_TEST, OBJTYPE="Board", MOC="PhysCpu",
MOI="SubNetwork=35, MEID=35, Equipment=1,Rack=1, Shelf=2, Board=7, PhysCpu
=1", ATTRIBUTES="RackNo=1, ShelfNo=2, SlotNo=7, CpuNo=1", TESTSEQ="1";
"TESTTYPE"
Select "DIAG_BOARD_TEST".
"OBJTYPE"
"MOC"
"MOI"
Enter the test object DN.
"ATTRIBUTES"
"TESTSEQ"
RackNo
Rack number of the tested board.
ShelfNo
Shelf number of the tested board.
SlotNo
Slot number of the tested board.
CpuNo
Number of the first physical CPU of the tested board.
Run the above board diagnosis command on each configured RUB board.
A-27
SJ-20140527134643-015|2015-03-31 (R1.1)
A-28
SJ-20140527134643-015|2015-03-31 (R1.1)
Glossary
ACL
- Access Control List
AIS
- Alarm Indication Signal
ARP
- Address Resolution Protocol
ASPB
- ACTA Signaling Processing Board
ATCA
- Advanced Telecommunications Computing Architecture
ATM
- Asynchronous Transfer Mode
BCCH
- Broadcast Control Channel
BECN
- Backward Explicit Congestion Notification
BFD
- Bidirectional Forwarding Detection
BIOS
- Basic Input/Output System
BS
- Base Station
BSC
- Base Station Controller
BTS
- Base Transceiver Station
BVC
- BSSGP Virtual Connection
CCCH
- Common Control Channel
CCM
- Communication Control Module
CDM
- Chassis Data Module
I
SJ-20140527134643-015|2015-03-31 (R1.1)
CFM
- Connectivity Fault Management
CMB
- Call Me Back
CMM
- Chassis Management Module
CMP
- Control Main Processor
CN
- Core Network
CPU
- Central Processing Unit
CRC
- Cyclic Redundancy Check
CS
- Circuit Switched
CS
- Circuit Service
CSU
- Control and Storage Unit
DDF
- Digital Distribution Frame
DHCP
- Dynamic Host Configuration Protocol
DIP
- Dependency-Inversion Principle
DSCP
- Differentiated Services Code Point
DSP
- Digital Signal Processing
DTE
- Data Terminal Equipment
DTM
- Dual Transfer Mode
EC
- Echo Canceller
ECDM
- ETCA Chassis Data Module
II
SJ-20140527134643-015|2015-03-31 (R1.1)
Glossary
ECMM
- ETCA Chassis Management Module
EGBS
- Enhanced GE BASE Switch Board
EGBS
- ETCA GE Base Switch
EGFS
- ETCA GE Fabric Switch
EGFS
- Enhanced GE FABRIC Switch Board
ESMC
- Ethernet Synchronization Message Channel
ETCA
- Enhanced ATCA
EXCH
- Exchange
FAS
- Frame Alignment Signal
FR
- Frame Relay
GMT
- Greenwich Mean Time
GPRS
- General Packet Radio Service
GPS
- Global Positioning System
GSM
- Global System for Mobile Communications
HDLC
- High-level Data Link Control
HEC
- Header Error Control
HW
- High speed data Way
IO
- Input & Output
IP
- Internet Protocol
III
SJ-20140527134643-015|2015-03-31 (R1.1)
IPD
- ICMP Path Detection
IPMC
- Intelligent Platform Management Controller
KPI
- Key Performance Index
LAPD
- Link Access Procedure for D-channel
LOM
- Loss of Multiframe
LOP
- Loss of Pointer
LOS
- Loss of Signal
M3UA
- MTP3-User Adaptation layer protocol
MA
- Maintenance Association
MAC
- Media Access Control
MO
- Managed Object
MOC
- Managed Object Class
MS
- Mobile Station
MS-AIS
- Multiplex Section - Alarm Indication Signal
MS-RDI
- Multiplex Section - Remote Defect Indication
MSC
- Mobile Switching Center
MTP
- Message Transfer Part
MTP2
- Message Transfer Part layer 2
MTP3
- Message Transfer Part layer 3
IV
SJ-20140527134643-015|2015-03-31 (R1.1)
Glossary
NDS
- Network Data Service
NE
- Network Element
NSE
- Network Service Entity
NSVC
- Network Service Virtual Connection
NTP
- Network Time Protocol
OAM
- Operation, Administration and Maintenance
OAMPDU
- OAM Protocol Data Unit
ODF
- Optical Distribution Frame
OMC
- Operation & Maintenance Center
OMCB
- Operation & Maintenance Center for Node B
OMM
- Operation & Maintenance Module
OMP
- Operation Main Processor
OMP
- Operation & maintenance Main Processor
OMP
- Operation & Maintenance Processor
OSPF
- Open Shortest Path First
OSPFv3
- Open Shortest Path First Protocol for IPv6
PCH
- Paging Channel
PCM
- Pulse Code Modulation
PCU
- Packet Control Unit
V
SJ-20140527134643-015|2015-03-31 (R1.1)
PDU
- Protocol Data Unit
PDU
- Power Distribution Unit
PDUM
- PDU Monitor board
PPP
- Point to Point Protocol
PS
- Packet Switched
PS
- Packet Service
PTP
- Precision Time Protocol
PVC
- Permanent Virtual Channel
RACH
- Random Access Channel
RAID
- Redundant Array of Independent Disks
RDI
- Remote Defect Indication
RMEP
- Remote Maintenance association End Point
RNC
- Radio Network Controller
RPU
- Route Process Unit
RPU
- Router Process Unit
RUP
- Rnc User plane Processor
RX
- Receiver
SAS
- Serial Attached SCSI
SCTP
- Stream Control Transmission Protocol
VI
SJ-20140527134643-015|2015-03-31 (R1.1)
Glossary
SDH
- Synchronous Digital Hierarchy
SGSN
- Serving GPRS Support Node
SLA
- Service Level Agreement
SNS
- Subnetwork Service
SNTP
- Simple Network Time Protocol
SONET
- Synchronous Optical Network
SP
- Signaling Point
SPC
- Signaling Point Code
TD
- Time Division
TRAU
- Transcoder Rate Adaptor Unit
TRX
- Transceiver
TU
- Tributary Unit
TU-AIS
- Tributary Unit Alarm Indication Signal
UDP
- User Datagram Protocol
UMTS
- Universal Mobile Telecommunication System
UNEQ
- UN-Equipped
VLAN
- Virtual Local Area Network
VII
SJ-20140527134643-015|2015-03-31 (R1.1)

SJ-20140527134643-015-ZXUR 9000 GSM (V6.50.202) Alarm and Notification Handling Reference

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

SJ-20140527134643-015-ZXUR 9000 GSM (V6.50.202) Alarm and Notification Handling Reference

Transféré par

Droits d'auteur :

Formats disponibles

ZXUR 9000 GSM

Base Station Controller

Alarm and Notification Handling Reference

Additionally, the contents of this document are protected by

contractual confidentiality obligations.

Updated to V6.50.202f. For details, refer to the relevant release

Serial Number: SJ-20140527134643-015

ZTE Proprietary and Confidential

Chapter 3 Alarms........................................................................................ 3-1

ZTE Proprietary and Confidential

3.1.19 199001794 SDH/SONET:Regenerator section trace mismatch/Section

ZTE Proprietary and Confidential

3.1.47 199005200 Board configuration information is not compatible ................. 3-72

ZTE Proprietary and Confidential

3.1.80 199007168 Port trunk failed .................................................................3-107

ZTE Proprietary and Confidential

3.1.115 199030725 Temperature is higher than upper-critical threshold.............3-145

ZTE Proprietary and Confidential

3.1.152 199087788 User-defined Dry contact alarm 2 ......................................3-188

ZTE Proprietary and Confidential

3.1.189 199080858 Dry contact alarm - Under-voltage insulate drop.................3-213

ZTE Proprietary and Confidential

3.1.226 199087458 PS cell block caused by slave ...........................................3-239

ZTE Proprietary and Confidential

3.1.262 198087128 C interface E1 Rx carrier alarm .........................................3-263

ZTE Proprietary and Confidential

3.1.299 198087188 Tower Amplifier0 power alarm ...........................................3-288

ZTE Proprietary and Confidential

3.1.335 198087269 DUC chip initialization failure ............................................3-314

ZTE Proprietary and Confidential

ZTE Proprietary and Confidential

ZTE Proprietary and Confidential

3.1.446 198088006 Operation link broken(CS) ................................................3-386

ZTE Proprietary and Confidential

3.2.3 199004357 The system bureau changed ................................................3-409

ZTE Proprietary and Confidential

3.3.15 199066010 MTP3 office inaccessible ....................................................3-443

ZTE Proprietary and Confidential

3.4.9 199087350 CCCH overload control ........................................................3-485

Chapter 4 Notifications .............................................................................. 4-1

ZTE Proprietary and Confidential

4.25 199013890 Sigtran error message received ..................................................... 4-25

ZTE Proprietary and Confidential

4.61 199105006 Slave losted external clock ............................................................ 4-73

ZTE Proprietary and Confidential

4.98 198087339 BTS self maintenance inform ........................................................4-103

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

ZTE Proprietary and Confidential

A.28 A2019 ........................................................................................................... A-26

ZTE Proprietary and Confidential

This page intentionally left blank.

ZTE Proprietary and Confidential

About This Manual

What Is in This Manual

Gives an overview of ZXUR 9000 GSM alarms and notifications.

Describes the common operations for alarm handling.

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

Describes the notifications in terms of notification properties, causes,

Appendix A Link Information

Describes the complex operations for alarm handling.

ZTE Proprietary and Confidential

This page intentionally left blank.

ZTE Proprietary and Confidential

Uniquely identifies an alarm.