Huawei Alarms

Horizon RAN controller
BSS Alarm Reference
Issue 01
Date 2008-06-24
BSS Alarm Reference Contents
Contents
1 BSC Alarm Reference................................................................................................................1-1

1.1 BSC Alarm List.............................................................................................................................................1-17
1.2 101 MSC Overload........................................................................................................................................1-43
1.3 102 Disrupted Connection with the CBC......................................................................................................1-44
1.4 103 All SS7 Links Faulty..............................................................................................................................1-45
1.5 124 No A Interface Circuit Configured in the BSC......................................................................................1-46
1.6 126 No Circuit Configured in the MSC........................................................................................................1-48
1.7 128 No Circuit Configured in the PCU.........................................................................................................1-49
1.8 129 MSC Resetting.......................................................................................................................................1-50
1.9 130 BSC Resetting Failure............................................................................................................................1-51
1.10 131 BSC Unable to Reset a Circuit.............................................................................................................1-52
1.11 132 BSC Unable to Block a Circuit............................................................................................................1-53
1.12 133 BSC Unable to Unblock a Circuit........................................................................................................1-54
1.13 134 BSC Unable to Block a Packet Circuit.................................................................................................1-55
1.14 135 BSC Unable to Unblock a Packet Circuit............................................................................................1-56
1.15 136 BSC Unable to Reset a Packet Circuit.................................................................................................1-57
1.16 137 BSC Unable to Unblock Group Circuits..............................................................................................1-58
1.17 138 BSC Unable to Block Group Circuits..................................................................................................1-59
1.18 139 No Group Circuits Configured on the BSC side..................................................................................1-61
1.19 140 BSC Unable to Read License File........................................................................................................1-62
1.20 141 BSC Unable to Obtain License File.....................................................................................................1-63
1.21 142 Resource Overused...............................................................................................................................1-64
1.22 143 Resource Overused Event Alarm.........................................................................................................1-66
1.23 144 Simpermanent Link Configuration Validation Failure........................................................................1-67
1.24 145 No Group Circuits Configured on the MSC Side................................................................................1-68
1.25 146 Satellite Transmission Supported Sites Blocked Due to License........................................................1-69
1.26 147 Extended Cells Blocked Due to License..............................................................................................1-71
1.27 148 PBT-Supported DTRU Blocked Due to License.................................................................................1-72
1.28 149 Transmit-Diversity DTRU Blocked Due to License............................................................................1-73
1.29 150 DTRU Blocked Due to License...........................................................................................................1-74
1.30 151 4-Way Diversity DTRU Blocked Due to License................................................................................1-75
1.31 152 High-Output-Power TRU Blocked Due to License.............................................................................1-76
1.32 153 Cell Broadcast Short Message Service Stopped Due to License.........................................................1-77
(2008-06-24) i
Contents BSS Alarm Reference
1.33 154 Resource Usage Threshold Exceeded for Over 60 Times....................................................................1-79

1.34 155 All Ater LapdLink Faulty.....................................................................................................................1-80
1.35 156 DSP Resource Lack..............................................................................................................................1-81
1.36 157 License Inferior Limit..........................................................................................................................1-82
1.37 158 License File Expired.............................................................................................................................1-82
1.38 159 Lack TC Resource................................................................................................................................1-83
1.39 160 HDLC Link Fault.................................................................................................................................1-84
1.40 161 HDLC Link Congestion.......................................................................................................................1-85
1.41 201 Internal Flow Control Level Changed..................................................................................................1-86
1.42 202 Internal Flow Control Released............................................................................................................1-88
1.43 203 PDCH Configured on Overlayer with an old version PCU.................................................................1-89
1.44 205 TC Fault Alarm....................................................................................................................................1-90
1.45 291 Cell Transmission Delay Abnormal.....................................................................................................1-92
1.46 293 GB BC Faulty.......................................................................................................................................1-93
1.47 294 TRX Config Error................................................................................................................................1-94
1.48 331 NSVC Faulty........................................................................................................................................1-95
1.49 332 NSVL Faulty........................................................................................................................................1-97
1.50 333 NSE Faulty...........................................................................................................................................1-98
1.51 340 Cell PS Service Faulty..........................................................................................................................1-99
1.52 341 DSP Resource Overload.....................................................................................................................1-101
1.53 342 PTP BVC Faulty.................................................................................................................................1-102
1.54 343 NSVL Dynamic Configuration Process Failure.................................................................................1-103
1.55 344 FAULTY DSP OVER LIMIT............................................................................................................1-104
1.56 401 BCCH Mutual Aid in a Cell...............................................................................................................1-106
1.57 402 Switchback after BCCH Mutual Aid in a Cell...................................................................................1-107
1.58 403 Baseband FH Mutual Aid in a Cell....................................................................................................1-109
1.59 404 Switchback after Baseband FH Mutual Aid in a Cell........................................................................1-110
1.60 405 Cell Out of Service.............................................................................................................................1-111
1.61 407 BTS Initialization...............................................................................................................................1-113
1.62 408 Automatic Activation of BTS TMU Version.....................................................................................1-114
1.63 409 Cell BCCH Aiding to IUO_INN TRX...............................................................................................1-115
1.64 410 BTS's capabilty doesn't account with the config data........................................................................1-117
1.65 411 Site Reset for DynCfg........................................................................................................................1-118
1.66 412 Manually Obturate Cell......................................................................................................................1-118
1.67 413 Manually Obturate Trx.......................................................................................................................1-119
1.68 414 Manually Obturate Channel...............................................................................................................1-120
1.69 416 SitePowerOff......................................................................................................................................1-121
1.70 417 BTS Loop Rotate................................................................................................................................1-122
1.71 418 BTS Loop Rotateback........................................................................................................................1-123
1.72 419 Query IP of PTU by Its electric label failed because of configration error........................................1-124
1.73 420 BTS doesn't support config the card and the logic object separately.................................................1-125
1.74 421 PTU Initialization...............................................................................................................................1-126
ii (2008-06-24)
1.75 422 BTS doesn't support abis optimize.....................................................................................................1-128

1.76 423 Extension Signaling Link Failure.......................................................................................................1-128
1.77 701 M3UA Link Fault...............................................................................................................................1-130
1.78 702 M3UA Link Congestion.....................................................................................................................1-132
1.79 703 M3UA Route Unvailable...................................................................................................................1-133
1.80 704 M3UA Destination Entity Unvailably................................................................................................1-134
1.81 705 FG2/GOU Route Status Unavailable.................................................................................................1-135
1.82 801 Data Out of Synchronization..............................................................................................................1-136
1.83 802 Error of Transaction Logging File.....................................................................................................1-137
1.84 951 TDM slot link error............................................................................................................................1-138
1.85 1000 LAPD OML Fault............................................................................................................................1-139
1.86 20002 Incorrect Board Slot Information...................................................................................................1-141
1.87 20003 Board Fault - Faulty Inner Clock...................................................................................................1-143
1.88 20004 Board Fault-Abnormal Voltage......................................................................................................1-144
1.89 20005 Faulty Clock Source 0 from the Front Interface Board to the Backplane of the GSCU................1-145
1.90 20006 Faulty Clock Source 1 from the Front Interface Board to the Backplane of the GSCU................1-147
1.91 20007 Faulty Clock Source 0 from the Rear Interface Board to the Backplane of the GSCU.................1-149
1.92 20008 Faulty Clock Source 1 from the Rear Interface Board to the Backplane of the GSCU.................1-151
1.93 20009 Faulty 8 kHz Clock Source from the Active GGCU to the Backplane of the GSCU....................1-153
1.94 20010 Faulty 8 kHz Clock Source from the Standby GGCU to the Backplane of the GSCU..................1-155
1.95 20013 Faulty GGCU 8 kHz Clock Source for the Front Panel of the GSCU...........................................1-157
1.96 20016 Faulty 32 MHz Clock from the Backplane....................................................................................1-158
1.97 20025 BIOS Check Failure.......................................................................................................................1-161
1.98 20026 Faulty Phase-Locked Loop of the Board Clock.............................................................................1-162
1.99 20027 Abnormal Subrack Information.....................................................................................................1-164
1.100 20028 Faulty Packet Switching Unit.......................................................................................................1-165
1.101 20029 Board Fault - Faulty Logical Unit................................................................................................1-167
1.102 20030 Faulty Sub-Board.........................................................................................................................1-168
1.103 20038 Faulty Board Chip........................................................................................................................1-170
1.104 20039 Faulty Output Clock Signals........................................................................................................1-172
1.105 20040 High Board Temperature - Minor Alarm.....................................................................................1-173
1.106 20041 High Board Temperature - Major Alarm.....................................................................................1-175
1.107 20042 High Board Temperature - Critical Alarm...................................................................................1-177
1.108 20044 Unavailable Clock Source............................................................................................................1-179
1.109 20045 Failed to Get Temperature............................................................................................................1-181
1.110 20052 Flash erase/write fail alarm..........................................................................................................1-182
1.111 20081 Loss of E1 Signals (LOS).............................................................................................................1-183
1.112 20082 Loss of E1 Frames (LOF).............................................................................................................1-185
1.113 20083 Remote E1 Alarm (RAI)..............................................................................................................1-186
1.114 20084 E1 Alarm Indication Signal (AIS)................................................................................................1-188
1.115 20085 Loss of E1 Multiframes (LOM)...................................................................................................1-189
1.116 20086 E1 Link Loopback........................................................................................................................1-190
(2008-06-24) iii
1.117 20087 High BER over the E1 Link.........................................................................................................1-192

1.118 20089 Excessive Loss of E1 Signals in an Hour.....................................................................................1-194
1.119 20090 Excessive E1 Synchronization Failures in an Hour.....................................................................1-195
1.120 20091 E1 Excessive Peer End Alarms Per Hour.....................................................................................1-197
1.121 20092 E1 Excessive Bit Error Rate Per Hour.........................................................................................1-198
1.122 20093 E1 Excessive Slip Frames Per Hour.............................................................................................1-200
1.123 20113 Faulty GE Link on the Sub-board of GXPUx..............................................................................1-201
1.124 20114 Inter-Board HIG Link Faulty.......................................................................................................1-203
1.125 20115 Intra-Board HIG Link Faulty.......................................................................................................1-205
1.126 20116 Inter-Board HIG Trunk Communication Failure.........................................................................1-206
1.127 20117 Board Fault-GE Switch Unit Failure............................................................................................1-208
1.128 20118 Inter-Board HIG Communication Failure....................................................................................1-209
1.129 20120 Broadcast packet overflow alarm.................................................................................................1-211
1.130 20121 GESW BAM GE Communication Failure...................................................................................1-212
1.131 20122 GESW BAM Trunk Communication Failure...............................................................................1-213
1.132 20123 Faulty GE Link on the Panel of GSCU board..............................................................................1-215
1.133 20124 Faulty GE Link on the Panel of XPU board.................................................................................1-216
1.134 20125 GESW Back Trunk Group Link Failure......................................................................................1-218
1.135 20126 GE Trunk Group Link Fault of transaction board........................................................................1-220
1.136 20127 GESW Panel Trunk Group Link Failure......................................................................................1-222
1.137 20128 Faulty GE Link on the Backplane of GSCU board......................................................................1-224
1.138 20129 Faulty GE Link on the Backplane of transaction board...............................................................1-226
1.139 20164 Quality of GE Link on Service Board Backplane Decrease........................................................1-228
1.140 20191 Board Faulty-Link Disconnection on the Service Port................................................................1-230
1.141 20194 Disconnected Link Between the Ports on the Active and Standby GSCU..................................1-231
1.142 20221 Loss of Clock on the Optical Port (RLOC)..................................................................................1-233
1.143 20222 Loss of Signals on the Optical Port (RLOS)................................................................................1-234
1.144 20223 Loss of Received Signal Frames on the Optical Port (RLOF).....................................................1-236
1.145 20224 Out-of-Synchronization of Received Signal Frames on the Optical Port (ROOF)......................1-238
1.146 20225 Mismatch of Trace Byte of the Regenerator Section on the Optical Port (RTIM)......................1-239
1.147 20226 Regenerator Section Signal Failure (RSF)...................................................................................1-240
1.148 20227 Regenerator Section Signal Deteriorated (RSD)..........................................................................1-242
1.149 20228 Multiplex Section Alarm Indication Signal (MAIS)....................................................................1-243
1.150 20229 Multiplex Section Remote Defect Indication (MRDI).................................................................1-244
1.151 20230 Loopback on the Optical Port.......................................................................................................1-246
1.152 20231 Administration Unit Alarm Indication Signal (AUAIS)..............................................................1-247
1.153 20232 Loss of Administration Unit Pointer (AULOP)...........................................................................1-248
1.154 20233 Service Unequipped on the High-Order Path of the Optical Port (HPUNEQ)............................1-249
1.155 20234 Trace Flag Mismatch on the High-Order Path of the Optical Port (HPTIM)..............................1-250
1.156 20235 High-Order Path Signal Label Byte Mismatch (HPSLM)...........................................................1-252
1.157 20236 High-Order Path Signal Failure (HPSF)......................................................................................1-253
1.158 20237 High-Order Path Signal Deteriorated (HPSD).............................................................................1-254
iv (2008-06-24)
1.159 20238 Remote Defect Indication on the High-Order Path of the Optical Port (HPRDI)........................1-255
1.160 20239 Loss of Tributary Unit Multi-frames (TULOM)..........................................................................1-257
1.161 20240 Tributary Unit Alarm Indication Signal (TUAIS)........................................................................1-258
1.162 20241 Loss of Tributary Unit Pointer (TULOP).....................................................................................1-259
1.163 20242 Service Unequipped on the Lower-Order Path of the Optical Port (LPUNEQ)..........................1-260
1.164 20243 Trace Flag Mismatch on the Lower-Order Path of the Optical Port (LPTIM)............................1-262
1.165 20244 Signal Flag Mismatch on the Low-Order Path of the Optical Port (LPSLM).............................1-263
1.166 20245 Low-Order Path Remote Failure Indicaton (LPRFI)...................................................................1-264
1.167 20246 Low-Order Path Remote Defect Indication (LPRDI)..................................................................1-265
1.168 20247 Tributary Unit Type Mismatch (TUSIZEERR)...........................................................................1-266
1.169 20248 Loss of Tributary Signals (LOS)..................................................................................................1-267
1.170 20249 Tributary Alarm Indication Signal (AIS).....................................................................................1-269
1.171 20250 Loss of Tributary Frames (LOF)..................................................................................................1-270
1.172 20251 Remote Alarm Indication over the Tributary (RAI)....................................................................1-271
1.173 20252 Loss of Tributary Multi-Frames (LOM)......................................................................................1-273
1.174 20253 Slip Frame over the Tributary......................................................................................................1-275
1.175 20254 Tributary Loopback Alarm...........................................................................................................1-276
1.176 20255 Optical Module Fault...................................................................................................................1-277
1.177 20271 Serial Port Fault............................................................................................................................1-278
1.178 20272 Monitor Board Out of Position.....................................................................................................1-279
1.179 20321 Unavailable Clock Reference for GGCU.....................................................................................1-281
1.180 20322 Unavailable Current Clock Reference for GGCU........................................................................1-283
1.181 20323 GGCU Failure-Abnormal Frequency Doubler.............................................................................1-285
1.182 20324 GGCU Failure-Abnormal Local Oscillation Signal.....................................................................1-286
1.183 20325 Clock Reference Failure of GGCU over 24 Hours......................................................................1-287
1.184 20329 Unavailable Input Clock Source for GGCU................................................................................1-289
1.185 20352 Clock Failure of the TDM Interface Unit.....................................................................................1-291
1.186 20353 TDM Interface Unit Failure Alarm..............................................................................................1-292
1.187 20357 GEIUx/GOIUxTime slot loopback alarm....................................................................................1-294
1.188 20359 TDM backplane Link Failure of TSU..........................................................................................1-295
1.189 20360 TDM backplane Link Failure of transaction board......................................................................1-297
1.190 20361 TDM panel Link Failure of TSU..................................................................................................1-299
1.191 20362 Master TDM link of TSU backplane fault alarm.........................................................................1-301
1.192 20363 Master TDM link of transaction board backplane fault alarm.....................................................1-303
1.193 20364 Master TDM link of TSU panel fault alarm.................................................................................1-304
1.194 20371 GE/FE Conversion Unit Fault......................................................................................................1-306
1.195 20372 GE Interface Unit Fault................................................................................................................1-308
1.196 20401 Board Fault-ME Fault..................................................................................................................1-310
1.197 20409 Quality of GE Link on GSCU Backplane Decrease.....................................................................1-311
1.198 20410 Quality of GE Link on GSCU Panel Decrease............................................................................1-312
1.199 20411 Quality of GE Link on Sub-Board Decrease................................................................................1-314
1.200 20412 Quality of GE Link on GXPUx Panel Decrease..........................................................................1-315
(2008-06-24) v
1.201 20421 Abnormal Temperature................................................................................................................1-317

1.202 20422 Abnormal Voltage........................................................................................................................1-319
1.203 20423 Communication Failure................................................................................................................1-320
1.204 20424 Abnormal Humidity.....................................................................................................................1-322
1.205 20425 Abnormal External Analog Sensor..............................................................................................1-323
1.206 20426 Abnormal External Digital Sensor...............................................................................................1-324
1.207 20427 Abnormal PDB Output Switch Sensor.........................................................................................1-325
1.208 20428 Abnormal PDB Power Sensor......................................................................................................1-327
1.209 20429 Abnormal PDB Lightning Protection Sensor...............................................................................1-328
1.210 20430 Fan Box Temperature Sensor Invalidation...................................................................................1-329
1.211 20431 Fan Block Alarm..........................................................................................................................1-330
1.212 20433 Fan Board Hardware Failure Alarm.............................................................................................1-331
1.213 20434 Board Register Successfully Alarm.............................................................................................1-332
1.214 20435 Failure in One Power Supply for the Fan Box.............................................................................1-333
1.215 20436 Abnormal PDB Monitoring Board Component...........................................................................1-334
1.216 20951 Status Change Event Alarm.........................................................................................................1-335
1.217 20954 8k Clock reference source 0 from mainboard to BackPlane fault alarm......................................1-336
1.218 20955 8k Clock reference source 1 from mainboard to BackPlane fault alarm......................................1-338
1.219 20956 19M SDH Clock reference source from BackPlane fault alarm..................................................1-339
1.220 20957 8k SDH Clock reference source from BackPlane fault alarm......................................................1-340
1.221 20958 32M TDM Clock reference source from BackPlane fault alarm.................................................1-342
1.222 20959 8k TDM Clock reference source from BackPlane fault alarm.....................................................1-343
1.223 20960 2M Clock reference source 0 from up subboard fault alarm........................................................1-344
1.224 20961 2M Clock reference source 1 from up subboard fault alarm........................................................1-345
1.225 20962 2M Clock reference source from down subboard fault alarm......................................................1-347
1.226 20963 Number of E1 Frame Slips Within 24 Hours Over Threshold.....................................................1-348
1.227 20964 Number of E1 Frame Slips Within 24 Hours Over Max Threshold............................................1-349
1.228 20965 Board Fault-Abnormal Voltage....................................................................................................1-351
1.229 20966 SubBoard not exist.......................................................................................................................1-352
1.230 20967 OPT Module electrical current exceed high Threshold................................................................1-353
1.231 20968 OPT Module electrical current exceed low Threshold.................................................................1-354
1.232 20969 Ethernet Link failure....................................................................................................................1-355
1.233 20970 Ethernet Link Receive Defect Indication.....................................................................................1-356
1.234 20971 Ethernet Link Send Defect Indication..........................................................................................1-357
1.235 20972 Ethernet Link Loop......................................................................................................................1-358
1.236 20973 OPT Module Temprature exceed high Threshold........................................................................1-359
1.237 20974 OPT Module Temprature exceed low Threshold.........................................................................1-360
1.238 20975 OPT Module Voltage exceed high Threshold..............................................................................1-360
1.239 20976 OPT Module Voltage exceed low Threshold...............................................................................1-361
1.240 20977 Failure of High-Speed Communication Link on the Backplane of Service Boards....................1-362
1.241 20978 COMM Channel Abnormal..........................................................................................................1-363
1.242 20979 Faulty Board Chip........................................................................................................................1-364
vi (2008-06-24)
1.243 20980 Ethernet Port Band Width Change...............................................................................................1-366

1.244 20981 Ethernet Port Duplex Mode Change............................................................................................1-367
1.245 20982 OPT Module rx power exceed high Threshold............................................................................1-368
1.246 20983 OPT Module rx power exceed low Threshold.............................................................................1-369
1.247 20984 OPT Module tx power exceed high Threshold............................................................................1-370
1.248 20985 OPT Module tx power exceed low Threshold.............................................................................1-370
1.249 20988 Microcode Thread Abort..............................................................................................................1-371
1.250 21001 LAPD Link Congestion................................................................................................................1-372
1.251 21002 Broken LAPD Link......................................................................................................................1-374
1.252 21019 Failed Loading of Board Software...............................................................................................1-375
1.253 21020 Software Version Inconsistency...................................................................................................1-377
1.254 21022 Faulty Remote Load Agent..........................................................................................................1-378
1.255 21023 Inconsistent Sub-Board Alarm.....................................................................................................1-380
1.256 21024 GBAM File Check Failure...........................................................................................................1-381
1.257 21025 Patch not confirm.........................................................................................................................1-382
1.258 21026 GBAM/GOMU License Check Fail Alarm.................................................................................1-383
1.259 21027 Remote EIU/OIU Board Connection Error..................................................................................1-384
1.260 21028 Board Physical Type inconsistent................................................................................................1-385
1.261 21030 Load License to SMU failed........................................................................................................1-387
1.262 21201 DSP Heartbeat Lost......................................................................................................................1-388
1.263 21202 DSP Overload...............................................................................................................................1-389
1.264 21203 DSP Fault.....................................................................................................................................1-390
1.265 21204 Unavailable Subrack....................................................................................................................1-391
1.266 21205 Board Fault...................................................................................................................................1-392
1.267 21206 CPU Fault.....................................................................................................................................1-393
1.268 21207 Board Hardware Self-Test Failure of Warning Level..................................................................1-394
1.269 21208 Board Hardware Self-Test Failure of Minor Level......................................................................1-395
1.270 21209 Board Hardware Self-Test Failure of Major Level......................................................................1-396
1.271 21210 CPU Overload..............................................................................................................................1-397
1.272 21211 Board Switchover.........................................................................................................................1-398
1.273 21212 DSP TDM Timeslot Link Unavailable.........................................................................................1-399
1.274 21213 HA Status Line Fault....................................................................................................................1-400
1.275 21214 OMU Harddisk Overload Alarm..................................................................................................1-401
1.276 21215 XPU Port IP Conflict....................................................................................................................1-402
1.277 21216 PowerBox Types Inconsistent......................................................................................................1-403
1.278 21250 Daemon Heartbeat Lost Alarm....................................................................................................1-404
1.279 21251 Daemon Version Not Match Alarm.............................................................................................1-405
1.280 21252 Backup Channel Between Daemons Break Alarm.......................................................................1-406
1.281 21253 Interior Channel Between Daemons Break Alarm.......................................................................1-407
1.282 21254 OMU Mode Switch Event Alarm.................................................................................................1-408
1.283 21255 Swap Result Event Alarm............................................................................................................1-409
1.284 21501 MTP3 DSP Unreachable..............................................................................................................1-410
(2008-06-24) vii
1.285 21502 MTP3 Layer 3 Congestion...........................................................................................................1-411

1.286 21503 MTP3 Link Unavailable...............................................................................................................1-413
1.287 21504 MTP3 Signaling Link2 Congestion..............................................................................................1-417
1.288 21511 MTP3 Link Test Success..............................................................................................................1-418
1.289 21512 MTP3 Link Test Failure...............................................................................................................1-419
1.290 21513 MTP2 Link Location Failure........................................................................................................1-421
1.291 21514 MTP2 Link Service Disrupted.....................................................................................................1-424
1.292 21516 Route Transmission on the MTP3 Prohibited..............................................................................1-428
1.293 21518 MTP3 Link Layer 3 Congestion Released...................................................................................1-429
1.294 21525 SCCP DSP Unreachable...............................................................................................................1-430
1.295 21526 SCCP Subsystem Prohibited........................................................................................................1-432
1.296 21528 Remote SCCP Fault.....................................................................................................................1-433
1.297 21531 Lack of SCCP Connection Resources..........................................................................................1-435
1.298 21551 Ater OML Broken Alarm.............................................................................................................1-435
1.299 21581 APS Started Alarm.......................................................................................................................1-437
1.300 21582 Deactivate APS Alarm.................................................................................................................1-438
1.301 21583 APS Protocol Swap Alarm...........................................................................................................1-439
1.302 21584 APS K1/K2 Mismatch Alarm......................................................................................................1-440
1.303 21585 APS K2 Mismatch Alarm............................................................................................................1-441
1.304 21586 APS Uni-Bid Mode Mismatch Alarm..........................................................................................1-442
1.305 21601 NTP Server unconfigured.............................................................................................................1-444
1.306 21602 Adjust time failure with the NTP server......................................................................................1-444
1.307 22001 Extern Water Sensor Alarm.........................................................................................................1-445
1.308 22002 Extern Smoke Sensor Alarm........................................................................................................1-446
1.309 22003 Extern InfraRed Sensor Alarm.....................................................................................................1-447
1.310 22004 Extern DoorEngine Sensor Alarm................................................................................................1-448
1.311 22005 Extern Figure Sensor1 Alarm.......................................................................................................1-450
1.320 22014 Extern Figure Sensor10 Alarm.....................................................................................................1-459
viii (2008-06-24)

1.343 22051 Extern Simulate Sensor1 Alarm...................................................................................................1-482
1.347 65234 BTS Custom Environment Alarm1..............................................................................................1-486
1.356 65243 BTS Custom Environment Alarm10............................................................................................1-498
(2008-06-24) ix

x (2008-06-24)

1.446 65333 BTS Custom Environment Alarm100..........................................................................................1-624
1.447 65334 BSC Custom Environment Alarm1..............................................................................................1-626
(2008-06-24) xi

1.456 65343 BSC Custom Environment Alarm10............................................................................................1-635
xii (2008-06-24)

2 BTS Alarm Reference................................................................................................................2-1

2.1 BTS Alarm List.............................................................................................................................................2-15
2.2 30000 BTP Software Failure.........................................................................................................................2-38
2.3 30001 BTP Site Reset Occurred Due To Front Panel Reset.........................................................................2-39
2.4 30002 BTP Active Link Connection Failure.................................................................................................2-41
2.5 30003 BTP Standby Link Connection Failure..............................................................................................2-42
2.6 30004 BTP Process Safe Test Audit Failure.................................................................................................2-44
2.7 30005 CSFP Code objects unavailable.........................................................................................................2-45
2.8 30006 CSFP PCMCIA Card Removed.........................................................................................................2-47
2.9 30007 GCLK Clock Reference Failure.........................................................................................................2-48
2.10 30008 GCLK Phase Lock Lost...................................................................................................................2-50
2.11 30009 GCLK Phase Lock Failure...............................................................................................................2-51
2.12 30010 GCLK Watchdog Timer Expired.....................................................................................................2-53
2.13 30011 GCLK Clock Output Failure............................................................................................................2-54
2.14 30012 GCLK SYNC Shutdown Request....................................................................................................2-55
2.15 30013 GCLK Not Operational....................................................................................................................2-57
2.16 30014 GCLK Warmup Failure....................................................................................................................2-58
2.17 30015 GCLK Invalid Mode........................................................................................................................2-60
2.18 30016 GCLK Calibration In Progress.........................................................................................................2-61
2.19 30017 GCLK Calibration via Firmware Initiated.......................................................................................2-63
2.20 30018 GCLK Bad Clock Source, or OCXO(oscillator) Replacement Required........................................2-64
2.21 30019 GCLK Calibration Request..............................................................................................................2-66
2.22 30020 Port 0 Synchronization Loss Daily Threshold Exceeded.................................................................2-67
2.23 30021 Port 0 Synchronization Loss Hourly Threshold Exceeded..............................................................2-69
2.24 30022 Port 0 Synchronization Loss OOS Threshold Exceeded..................................................................2-70
2.25 30023 Port 0 Remote Alarm Daily Threshold Exceeded............................................................................2-72
2.26 30024 Port 0 Remote Alarm Hourly Threshold Exceeded..........................................................................2-73
2.27 30025 Port 0 Remote Alarm OOS Threshold Exceeded.............................................................................2-74
2.28 30026 Port 0 Frame Slip Daily Threshold Exceeded..................................................................................2-76
2.29 30027 Port 0 Frame Slip Hourly Threshold Exceeded...............................................................................2-77
2.30 30028 Port 0 Frame Slip OOS Threshold Exceeded...................................................................................2-79
2.31 30029 Port 0 Bit Error Daily Threshold Exceeded.....................................................................................2-80
2.32 30030 Port 0 Bit Error Hourly Threshold Exceeded...................................................................................2-82
2.33 30031 Port 0 Bit Error OOS Threshold Exceeded......................................................................................2-83
2.34 30032 Port 0 Synchronization Loss OOS Timer Expired...........................................................................2-85
2.35 30033 Port 0 Remote Alarm OOS Timer Expired......................................................................................2-86
2.36 30034 Port 0 CRC4 Error Hourly Threshold Exceeded..............................................................................2-88
2.37 30035 Port 0 CRC4 Error Daily Threshold Exceeded................................................................................2-89
2.38 30036 Port 0 Critical Alarm Threshold Exceeded......................................................................................2-91
2.39 30037 Port 1 Synchronization Loss Daily Threshold Exceeded.................................................................2-92
(2008-06-24) xiii
2.40 30038 Port 1 Synchronization Loss Hourly Threshold Exceeded.............................................................. 2-94

2.41 30039 Port 1 Synchronization Loss OOS Threshold Exceeded..................................................................2-95
2.42 30040 Port 1 Remote Alarm Daily Threshold Exceeded............................................................................2-97
2.43 30041 Port 1 Remote Alarm Hourly Threshold Exceeded..........................................................................2-98
2.44 30042 Port 1 Remote Alarm OOS Threshold Exceeded...........................................................................2-100
2.45 30043 Port 1 Frame Slip Daily Threshold Exceeded................................................................................2-101
2.46 30044 Port 1 Frame Slip Hourly Threshold Exceeded.............................................................................2-103
2.47 30045 Port 1 Frame Slip OOS Threshold Exceeded.................................................................................2-104
2.48 30046 Port 1 Bit Error Daily Threshold Exceeded...................................................................................2-106
2.49 30047 Port 1 Bit Error Hourly Threshold Exceededc...............................................................................2-107
2.50 30048 Port 1 Bit Error OOS Threshold Exceeded....................................................................................2-108
2.51 30049 Port 1 Synchronization Loss OOS Timer Expired.........................................................................2-110
2.52 30050 Port 1 Remote Alarm OOS Timer Expired....................................................................................2-112
2.53 30051 Port 1 CRC4 Error Hourly Threshold Exceeded............................................................................2-113
2.54 30052 Port 1 CRC4 Error Daily Threshold Exceeded..............................................................................2-115
2.55 30053 Port 1 Critical Alarm Threshold Exceeded....................................................................................2-116
2.56 30054 Port 2 Synchronization Loss Daily Threshold Exceeded...............................................................2-118
2.57 30055 Port 2 Synchronization Loss Hourly Threshold Exceeded............................................................2-119
2.58 30056 Port 2 Synchronization Loss OOS Threshold Exceeded................................................................2-121
2.59 30057 Port 2 Remote Alarm Daily Threshold Exceeded..........................................................................2-122
2.60 30058 Port 2 Remote Alarm Hourly Threshold Exceeded........................................................................2-124
2.66 30064 Port 2 Bit Error Hourly Threshold Exceeded.................................................................................2-132
xiv (2008-06-24)

2.83 30081 Port 3 Bit Error Hourly Threshold Exceeded.................................................................................2-158
2.100 30098 Port 4 Bit Error Hourly Threshold Exceeded...............................................................................2-183
2.101 30099 Port 4 Bit Error OOS Threshold Exceeded..................................................................................2-184
2.102 30100 Port 4 Synchronization Loss OOS Timer Expired.......................................................................2-186
2.103 30101 Port 4 Remote Alarm OOS Timer Expired..................................................................................2-187
2.104 30102 Port 4 CRC4 Error Hourly Threshold Exceeded..........................................................................2-189
2.105 30103 Port 4 CRC4 Error Daily Threshold Exceeded............................................................................2-190
2.106 30104 Port 4 Critical Alarm Threshold Exceeded..................................................................................2-192
2.107 30105 Port 5 Synchronization Loss Daily Threshold Exceeded.............................................................2-193
2.108 30106 Port 5 Synchronization Loss Hourly Threshold Exceeded..........................................................2-195
2.109 30107 Port 5 Synchronization Loss OOS Threshold Exceeded..............................................................2-196
2.110 30108 Port 5 Remote Alarm Daily Threshold Exceeded........................................................................2-198
2.111 30109 Port 5 Remote Alarm Hourly Threshold Exceeded......................................................................2-199
2.112 30110 Port 5 Remote Alarm OOS Threshold Exceeded.........................................................................2-201
2.113 30111 Port 5 Frame Slip Daily Threshold Exceeded..............................................................................2-202
2.114 30112 Port 5 Frame Slip Hourly Threshold Exceeded...........................................................................2-204
2.115 30113 Port 5 Frame Slip OOS Threshold Exceeded...............................................................................2-205
2.116 30114 Port 5 Bit Error Daily Threshold Exceeded.................................................................................2-207
(2008-06-24) xv
2.124 30122 Site No Clock References Available............................................................................................2-219

2.125 30123 Site Active Alarm List Full..........................................................................................................2-220
2.126 30124 Site Reset Request........................................................................................................................2-221
2.127 30125 Site Database corruption detected................................................................................................2-223
2.128 30131 MSI Re-Initialized Unexpectedly.................................................................................................2-224
2.129 30132 MSI Safe Test Audit Failure........................................................................................................2-226
2.130 30133 MSI Active Link Connection Failure...........................................................................................2-228
2.131 30134 MSI Device Failure......................................................................................................................2-229
2.132 30135 Site No Software Failure - No intact software load on BTS without CSFP................................2-231
2.133 30136 Site No Software Failure - No intact Abis software load on BTS with CSFP.............................2-232
2.134 30137 SWFM Indication.........................................................................................................................2-234
2.135 30256 DRI SWFM Indication - BSS Internal Alarm Only.....................................................................2-235
2.136 30257 Internal Message Error - Pointer Misalignment...........................................................................2-236
2.137 30258 Internal Message Error - Dual-Port RAM Segment Full.............................................................2-238
2.138 30259 Superframe Counter Error............................................................................................................2-240
2.140 30261 Channel Coder Internal Message Error........................................................................................2-243
2.141 30262 Dual-Port RAM Error...................................................................................................................2-245
2.144 30265 Initial Synchronization of Radio and GPRS channel failed.........................................................2-249
2.147 30268 Primary Message or Hardware Interrupt Error.............................................................................2-254
2.150 30271 Calibration in progress.................................................................................................................2-259
2.151 30272 Radio Subsystem Software to DRI Communication Error..........................................................2-260
2.152 30273 Radio Subsystem Software to DRI Communication Failure.......................................................2-262
2.153 30274 TDM Interface Failure - TDM Parity Error.................................................................................2-263
2.154 30275 TDM Interface Failure - Assigned Timeslot Counter Overflow..................................................2-265
2.155 30276 TDM Interface Failure - Assigned Timeslot Counter Underflow................................................2-267
2.156 30277 Clock A Signal Loss.....................................................................................................................2-268
2.157 30278 Clock A Signal Loss.....................................................................................................................2-270
2.158 30279 Processor Failure..........................................................................................................................2-271
2.159 30280 Transceiver Re-Initialized Unexpectedly.....................................................................................2-273
2.160 30281 Critical Resource Exhausted........................................................................................................2-274
2.161 30282 RF Unit Primary Sync Signal Lost...............................................................................................2-276
2.162 30283 RF Unit HDSL Link Quality Error..............................................................................................2-277
2.163 30284 RF Unit Reset...............................................................................................................................2-279
2.164 30285 Reset Due To Recurring Fault......................................................................................................2-280
2.165 30286 Front End Processor to Radio Subsystem Software Communication Failure..............................2-282
xvi (2008-06-24)
2.166 30287 Hard Reset....................................................................................................................................2-284

2.167 30288 Synchronization Loss With MCU................................................................................................2-285
2.168 30289 Channel Coder Timeslot 0 Failure...............................................................................................2-287
2.176 30297 Baseband Hopping Timeslot Counter Mismatch.........................................................................2-299
2.177 30298 GSM Timeslot Counter Mismatch...............................................................................................2-300
2.178 30299 Spurious GSM Timeslot Interrupt................................................................................................2-302
2.179 30300 Baseband Hopping TDM Link Error...........................................................................................2-304
2.180 30301 Baseband Hopping GSM Timeslot Misalignment.......................................................................2-305
2.181 30302 Channel Coder 0 Failure - Demodulation Processor 0 Failure....................................................2-307
2.185 30306 Transceiver to DRI Communication Error...................................................................................2-313
2.187 30308 Transceiver to DRI Burst Error....................................................................................................2-316
2.188 30309 Transceiver to DRI Burst Error....................................................................................................2-318
2.192 30313 Unrecoverable Error.....................................................................................................................2-324
2.193 30314 Radio Subsystem Software to DRI Communication Error - Checksum Error.............................2-325
2.195 30316 Radio Subsystem Software to DRI Communication Error - DRI Not Responding.....................2-329
2.196 30317 Equalizer Control Processor Failure - Watchdog Timer Expired................................................2-330
2.197 30318 Unexpected Communications Bus Interrupt................................................................................2-332
2.198 30319 Receiver Failure...........................................................................................................................2-334
2.199 30320 Power Amplifier Error.................................................................................................................2-335
2.200 30321 Cell Transmit Power Unachievable..............................................................................................2-337
2.201 30322 Radio Subsystem Software to DRI Communication Error - Detected No Transceiver Uplink Data
...........................................................................................................................................................................2-338
2.202 30323 Tx VSWR Antenna Fault.............................................................................................................2-340
2.203 30324 Transmitter Synthesizer Failure...................................................................................................2-341
(2008-06-24) xvii
2.208 30329 Transmitter Failure - Output Power.............................................................................................2-349

2.211 30332 Power Amplifier Temperature High............................................................................................2-354
2.212 30333 Power Amplifier Communication Failure....................................................................................2-355
2.214 30335 Power Amplifier Power Low But Functioning............................................................................2-358
2.215 30336 Power Amplifier Temperature High But Functioning.................................................................2-360
2.217 30338 Timeslot 0 Configuration Failure.................................................................................................2-363
2.225 30346 Receiver Synthesizer Failure........................................................................................................2-375
2.242 30363 Transceiver to DRI Communication Failure................................................................................2-402
2.247 30368 Receive Matrix Failure.................................................................................................................2-409
2.248 30369 Transceiver to Combiner Communication Failure.......................................................................2-411
2.249 30370 Control Processor to Power Amplifier Communication Failure..................................................2-412
xviii (2008-06-24)
2.250 30371 Control Processor to Equalizer Communication Failure..............................................................2-414

2.251 30372 Power Supply Failure...................................................................................................................2-415
2.253 30374 Control Processor Message Queue Overflowed...........................................................................2-418
2.254 30375 Receiver Input Overflowed..........................................................................................................2-420
2.255 30376 Receiver Input Overflowed..........................................................................................................2-421
2.256 30377 Equalizer Output Overflowed......................................................................................................2-423
2.257 30378 Equalizer Output Overflowed......................................................................................................2-424
2.258 30379 Transmitter Out of Synchronization.............................................................................................2-425
2.259 30380 Receive Matrix Branch 2 Control Link Failure...........................................................................2-427
2.263 30384 Control Processor Firmware Failure............................................................................................2-433
2.264 30385 Control Processor Configuration Mismatch.................................................................................2-434
2.265 30386 Equalizer Configuration Mismatch..............................................................................................2-436
2.267 30388 Invalid Calibration Data...............................................................................................................2-439
2.268 30389 Equalizer Failure..........................................................................................................................2-440
2.269 30390 Equalizer Firmware Failure..........................................................................................................2-442
2.270 30391 Baseband Hopping TDM Link Error...........................................................................................2-443
2.271 30392 Baseband Hopping GSM Timeslot Misalignment.......................................................................2-445
2.272 30393 RF Unit Power Supply Unit - Input Failure.................................................................................2-446
2.273 30394 RF Unit Over Temperature..........................................................................................................2-448
2.274 30395 RF Unit Low Voltage Disconnect Imminent...............................................................................2-449
2.275 30396 RF Unit External Alarm Input......................................................................................................2-451
2.276 30397 Internal Communication Error.....................................................................................................2-452
2.277 30398 Power Amplifier Temperature.....................................................................................................2-454
2.278 30399 Hopping DRI Failure....................................................................................................................2-455
2.279 30400 Front End Processor Failure.........................................................................................................2-457
2.280 30401 Channel Coder Failure.................................................................................................................2-458
2.281 30402 Transceiver Processor Failure......................................................................................................2-460
2.282 30403 Equalizer Failure..........................................................................................................................2-461
2.283 30404 Power Amplifier Failure...............................................................................................................2-463
2.284 30405 Transceiver Recovery Failure......................................................................................................2-464
2.285 30406 Transmission Suspended to Conserve Battery Power..................................................................2-465
2.286 30407 Invalid Transceiver Calibration Data...........................................................................................2-467
2.287 30408 GPRS Not Supported by Radio....................................................................................................2-468
2.288 30409 Invalid in-call modification of destination channel type..............................................................2-470
2.289 30410 Safe Test Audit Failure................................................................................................................2-472
2.290 30412 Active Link Connection Failure...................................................................................................2-473
2.291 30413 Standby Link Connection Failure................................................................................................2-475
(2008-06-24) xix
2.292 30414 Slow Flash Failure........................................................................................................................2-476

2.293 30415 Non-Volatile Memory Failure......................................................................................................2-478
2.294 30416 Process Safe Test Audit Failure...................................................................................................2-479
2.295 30417 Standby Link Connected to Wrong Device..................................................................................2-481
2.296 30418 Unlocked Device Not In Service..................................................................................................2-482
2.297 30419 Device Failure..............................................................................................................................2-484
2.298 30420 DRI hardware type mismatch with software configuration.........................................................2-485
2.301 30423 RSL Link Disconnected...............................................................................................................2-490
2.302 30424 LAPD Protocol Error...................................................................................................................2-491
2.303 30426 LAPD Protocol Error Threshold Exceeded..................................................................................2-493
2.304 30427 Too Many LAPD Protocol Errors................................................................................................2-494
2.305 30511 Cavity 0 Tuning Error..................................................................................................................2-496
2.310 30516 Link A Sanity Failure...................................................................................................................2-503
2.311 30517 Link B Sanity Failure...................................................................................................................2-504
2.312 30518 Power Feed A Failure...................................................................................................................2-506
2.313 30519 Power Feed B Failure...................................................................................................................2-507
2.314 30520 Full Reset......................................................................................................................................2-509
2.315 30521 Partial Reset..................................................................................................................................2-510
2.317 30523 Cavity Combining Block 0 Failure..............................................................................................2-513
2.318 30524 Cavity Combining Block 1 Failure..............................................................................................2-514
2.319 30525 Processor A Failure......................................................................................................................2-516
2.320 30526 Processor B Failure......................................................................................................................2-517
2.321 30527 Device Failure..............................................................................................................................2-519
2.322 30551 MSI Re-Initialized Unexpectedly.................................................................................................2-520
2.323 30552 MSI Safe Test Audit Failure........................................................................................................2-522
2.324 30553 MSI Active Link Connection Failure...........................................................................................2-523
2.325 30554 MSI Device Failure......................................................................................................................2-525
xx (2008-06-24)

2.360 30671 Cabinet Fan Failure......................................................................................................................2-576
2.361 30672 Fan Tray 0 Failure........................................................................................................................2-577
2.362 30673 Fan Tray 1 Failure........................................................................................................................2-579
2.363 30674 Fan Tray 2 Failure........................................................................................................................2-580
2.364 30711 EAS has detected Main Power Failure.........................................................................................2-582
2.365 30712 External Alarm 01........................................................................................................................2-583
2.366 30713 External Alarm 02........................................................................................................................2-584
2.367 30714 External Alarm 03........................................................................................................................2-586
2.368 30715 External Alarm 04........................................................................................................................2-587
2.369 30716 External Alarm 05........................................................................................................................2-589
2.370 30717 External Alarm 06........................................................................................................................2-590
2.371 30718 External Alarm 07........................................................................................................................2-592
2.372 30719 External Alarm 08........................................................................................................................2-593
2.373 30720 External Alarm 09........................................................................................................................2-594
2.374 30721 External Alarm 10........................................................................................................................2-596
2.375 30722 External Alarm 11........................................................................................................................2-597
(2008-06-24) xxi
2.376 30723 External Alarm 12........................................................................................................................2-599

2.377 30724 External Alarm 13........................................................................................................................2-600
2.378 30725 External Alarm 14........................................................................................................................2-602
2.379 30726 External Alarm 15........................................................................................................................2-603
2.380 30727 External Alarm 16........................................................................................................................2-604
2.381 30728 Database Configuration and Hardware Mismatch.......................................................................2-606
2.382 30729 Duplexer Voltage Error................................................................................................................2-608
2.383 30730 BTS Cabinet Over Temperature...................................................................................................2-609
2.384 30731 Low Voltage Disconnect Imminent.............................................................................................2-611
2.385 30732 Air Conditioning Unit Failure......................................................................................................2-612
2.386 30733 Heat Management System Unit Failure.......................................................................................2-614
2.387 30735 Ancillary Cabinet Over Temperature...........................................................................................2-615
2.388 30736 Voltage Standing Wave Ratio Sector 1 Failure...........................................................................2-617
2.391 30739 Voltage Standing Wave Ratio Performance Low........................................................................2-622
2.392 30740 Smoke Alarm................................................................................................................................2-623
2.393 30741 Door Open....................................................................................................................................2-625
2.394 30742 No Connection to Alarms Board - connection broken.................................................................2-627
2.395 30743 Low Noise Amplifier Fuse Failure...............................................................................................2-628
2.396 30744 No Redundant Connection to Alarms Board - connection broken...............................................2-630
2.397 30745 No Connection to Alarm Board - Radio OOS..............................................................................2-631
2.398 30746 No Redundant Connection to Alarms Board - Radio OOS..........................................................2-633
2.399 30747 No connection to alarm board - Alarm Board Removed..............................................................2-634
2.400 30748 Rectifier Failure............................................................................................................................2-636
2.401 30749 Battery Box Temperature High....................................................................................................2-637
2.402 30750 Alarm Board Failed......................................................................................................................2-639
2.403 30751 Auxiliary Alarm 1........................................................................................................................2-640
2.404 30752 Urgent Critical Alarm...................................................................................................................2-642
2.405 30753 Heat Management System Unit Failure 1....................................................................................2-643
2.406 30754 Heat Management System Unit Failure 2....................................................................................2-645
2.407 30755 Mains A.C. Supply Failure 1........................................................................................................2-646
2.408 30756 Mains A.C. Supply Failure 2........................................................................................................2-648
2.409 30757 Rectifier Failure 1.........................................................................................................................2-649
2.410 30758 Rectifier Failure 2.........................................................................................................................2-651
2.411 30831 Power Supply Unit 0 Failure........................................................................................................2-652
2.415 30835 Power Supply Unit - Input Failure...............................................................................................2-659
2.416 30836 Power Supply Unit - Output Failure............................................................................................2-661
2.417 30837 Low Voltage Disconnect Imminent.............................................................................................2-662
xxii (2008-06-24)
2.418 30838 Power Supply Temperature High.................................................................................................2-664

2.419 30839 Mains A.C. Supply Failure...........................................................................................................2-665
2.420 30881 Active Multiplexer 0 Loopback Failure.......................................................................................2-667
2.421 30882 Standby Multiplexer 0 Loopback Failure.....................................................................................2-668
3 Changes in BSS Alarm Reference...........................................................................................3-1

Index.................................................................................................................................................i-1
(2008-06-24) xxiii
xxiv (2008-06-24)
BSS Alarm Reference 1 BSC Alarm Reference
1 BSC Alarm Reference
About This Chapter
This section describes the BSC alarms and the alarm lists.
1.1 BSC Alarm List

1.2 101 MSC Overload
1.3 102 Disrupted Connection with the CBC
1.4 103 All SS7 Links Faulty
1.5 124 No A Interface Circuit Configured in the BSC
1.6 126 No Circuit Configured in the MSC
1.7 128 No Circuit Configured in the PCU
1.8 129 MSC Resetting
1.9 130 BSC Resetting Failure
1.10 131 BSC Unable to Reset a Circuit
1.11 132 BSC Unable to Block a Circuit
1.12 133 BSC Unable to Unblock a Circuit
1.13 134 BSC Unable to Block a Packet Circuit
1.14 135 BSC Unable to Unblock a Packet Circuit
1.15 136 BSC Unable to Reset a Packet Circuit
1.16 137 BSC Unable to Unblock Group Circuits
1.17 138 BSC Unable to Block Group Circuits
1.18 139 No Group Circuits Configured on the BSC side
1.19 140 BSC Unable to Read License File
1.20 141 BSC Unable to Obtain License File
(2008-06-24) 1-1
1 BSC Alarm Reference BSS Alarm Reference
1.21 142 Resource Overused

1.22 143 Resource Overused Event Alarm
1.23 144 Simpermanent Link Configuration Validation Failure
1.24 145 No Group Circuits Configured on the MSC Side
1.25 146 Satellite Transmission Supported Sites Blocked Due to License
1.26 147 Extended Cells Blocked Due to License
1.27 148 PBT-Supported DTRU Blocked Due to License
1.28 149 Transmit-Diversity DTRU Blocked Due to License
1.29 150 DTRU Blocked Due to License
1.30 151 4-Way Diversity DTRU Blocked Due to License
1.31 152 High-Output-Power TRU Blocked Due to License
1.32 153 Cell Broadcast Short Message Service Stopped Due to License
1.33 154 Resource Usage Threshold Exceeded for Over 60 Times
1.34 155 All Ater LapdLink Faulty
1.35 156 DSP Resource Lack
1.36 157 License Inferior Limit
1.37 158 License File Expired
1.38 159 Lack TC Resource
1.39 160 HDLC Link Fault
1.40 161 HDLC Link Congestion
1.41 201 Internal Flow Control Level Changed
1.42 202 Internal Flow Control Released
1.43 203 PDCH Configured on Overlayer with an old version PCU
1.44 205 TC Fault Alarm
1.45 291 Cell Transmission Delay Abnormal
1.46 293 GB BC Faulty
1.47 294 TRX Config Error
1.48 331 NSVC Faulty
1.49 332 NSVL Faulty
1.50 333 NSE Faulty
1.51 340 Cell PS Service Faulty
1.52 341 DSP Resource Overload
1.53 342 PTP BVC Faulty
1-2 (2008-06-24)
1.54 343 NSVL Dynamic Configuration Process Failure

1.55 344 FAULTY DSP OVER LIMIT
1.56 401 BCCH Mutual Aid in a Cell
1.57 402 Switchback after BCCH Mutual Aid in a Cell
1.58 403 Baseband FH Mutual Aid in a Cell
1.59 404 Switchback after Baseband FH Mutual Aid in a Cell
1.60 405 Cell Out of Service
1.61 407 BTS Initialization
1.62 408 Automatic Activation of BTS TMU Version
1.63 409 Cell BCCH Aiding to IUO_INN TRX
1.64 410 BTS's capabilty doesn't account with the config data
1.65 411 Site Reset for DynCfg
1.66 412 Manually Obturate Cell
1.67 413 Manually Obturate Trx
1.68 414 Manually Obturate Channel
1.69 416 SitePowerOff
1.70 417 BTS Loop Rotate
1.71 418 BTS Loop Rotateback
1.72 419 Query IP of PTU by Its electric label failed because of configration error
1.73 420 BTS doesn't support config the card and the logic object separately
1.74 421 PTU Initialization
1.75 422 BTS doesn't support abis optimize
1.76 423 Extension Signaling Link Failure
1.77 701 M3UA Link Fault
1.78 702 M3UA Link Congestion
1.79 703 M3UA Route Unvailable
1.80 704 M3UA Destination Entity Unvailably
1.81 705 FG2/GOU Route Status Unavailable
1.82 801 Data Out of Synchronization
1.83 802 Error of Transaction Logging File
1.84 951 TDM slot link error
1.85 1000 LAPD OML Fault
1.86 20002 Incorrect Board Slot Information
(2008-06-24) 1-3
1.87 20003 Board Fault - Faulty Inner Clock

1.88 20004 Board Fault-Abnormal Voltage
1.89 20005 Faulty Clock Source 0 from the Front Interface Board to the Backplane of the GSCU
1.90 20006 Faulty Clock Source 1 from the Front Interface Board to the Backplane of the GSCU
1.91 20007 Faulty Clock Source 0 from the Rear Interface Board to the Backplane of the GSCU
1.92 20008 Faulty Clock Source 1 from the Rear Interface Board to the Backplane of the GSCU
1.93 20009 Faulty 8 kHz Clock Source from the Active GGCU to the Backplane of the GSCU
1.94 20010 Faulty 8 kHz Clock Source from the Standby GGCU to the Backplane of the GSCU
1.95 20013 Faulty GGCU 8 kHz Clock Source for the Front Panel of the GSCU
1.96 20016 Faulty 32 MHz Clock from the Backplane
1.97 20025 BIOS Check Failure
1.98 20026 Faulty Phase-Locked Loop of the Board Clock
1.99 20027 Abnormal Subrack Information
1.100 20028 Faulty Packet Switching Unit
1.101 20029 Board Fault - Faulty Logical Unit
1.102 20030 Faulty Sub-Board
1.103 20038 Faulty Board Chip
1.104 20039 Faulty Output Clock Signals
1.105 20040 High Board Temperature - Minor Alarm
1.106 20041 High Board Temperature - Major Alarm
1.107 20042 High Board Temperature - Critical Alarm
1.108 20044 Unavailable Clock Source
1.109 20045 Failed to Get Temperature
1.110 20052 Flash erase/write fail alarm
1.111 20081 Loss of E1 Signals (LOS)
1.112 20082 Loss of E1 Frames (LOF)
1.113 20083 Remote E1 Alarm (RAI)
1.114 20084 E1 Alarm Indication Signal (AIS)
1.115 20085 Loss of E1 Multiframes (LOM)
1.116 20086 E1 Link Loopback
1.117 20087 High BER over the E1 Link
1.118 20089 Excessive Loss of E1 Signals in an Hour
1.119 20090 Excessive E1 Synchronization Failures in an Hour
1-4 (2008-06-24)
1.120 20091 E1 Excessive Peer End Alarms Per Hour

1.121 20092 E1 Excessive Bit Error Rate Per Hour
1.122 20093 E1 Excessive Slip Frames Per Hour
1.123 20113 Faulty GE Link on the Sub-board of GXPUx
1.124 20114 Inter-Board HIG Link Faulty
1.125 20115 Intra-Board HIG Link Faulty
1.126 20116 Inter-Board HIG Trunk Communication Failure
1.127 20117 Board Fault-GE Switch Unit Failure
1.128 20118 Inter-Board HIG Communication Failure
1.129 20120 Broadcast packet overflow alarm
1.130 20121 GESW BAM GE Communication Failure
1.131 20122 GESW BAM Trunk Communication Failure
1.132 20123 Faulty GE Link on the Panel of GSCU board
1.133 20124 Faulty GE Link on the Panel of XPU board
1.134 20125 GESW Back Trunk Group Link Failure
1.135 20126 GE Trunk Group Link Fault of transaction board
1.136 20127 GESW Panel Trunk Group Link Failure
1.137 20128 Faulty GE Link on the Backplane of GSCU board
1.138 20129 Faulty GE Link on the Backplane of transaction board
1.139 20164 Quality of GE Link on Service Board Backplane Decrease
1.140 20191 Board Faulty-Link Disconnection on the Service Port
1.141 20194 Disconnected Link Between the Ports on the Active and Standby GSCU
1.142 20221 Loss of Clock on the Optical Port (RLOC)
1.143 20222 Loss of Signals on the Optical Port (RLOS)
1.144 20223 Loss of Received Signal Frames on the Optical Port (RLOF)
1.145 20224 Out-of-Synchronization of Received Signal Frames on the Optical Port (ROOF)
1.146 20225 Mismatch of Trace Byte of the Regenerator Section on the Optical Port (RTIM)
1.147 20226 Regenerator Section Signal Failure (RSF)
1.148 20227 Regenerator Section Signal Deteriorated (RSD)
1.149 20228 Multiplex Section Alarm Indication Signal (MAIS)
1.150 20229 Multiplex Section Remote Defect Indication (MRDI)
1.151 20230 Loopback on the Optical Port
1.152 20231 Administration Unit Alarm Indication Signal (AUAIS)
(2008-06-24) 1-5
1.153 20232 Loss of Administration Unit Pointer (AULOP)

1.154 20233 Service Unequipped on the High-Order Path of the Optical Port (HPUNEQ)
1.155 20234 Trace Flag Mismatch on the High-Order Path of the Optical Port (HPTIM)
1.156 20235 High-Order Path Signal Label Byte Mismatch (HPSLM)
1.157 20236 High-Order Path Signal Failure (HPSF)
1.158 20237 High-Order Path Signal Deteriorated (HPSD)
1.159 20238 Remote Defect Indication on the High-Order Path of the Optical Port (HPRDI)
1.160 20239 Loss of Tributary Unit Multi-frames (TULOM)
1.161 20240 Tributary Unit Alarm Indication Signal (TUAIS)
1.162 20241 Loss of Tributary Unit Pointer (TULOP)
1.163 20242 Service Unequipped on the Lower-Order Path of the Optical Port (LPUNEQ)
1.164 20243 Trace Flag Mismatch on the Lower-Order Path of the Optical Port (LPTIM)
1.165 20244 Signal Flag Mismatch on the Low-Order Path of the Optical Port (LPSLM)
1.166 20245 Low-Order Path Remote Failure Indicaton (LPRFI)
1.167 20246 Low-Order Path Remote Defect Indication (LPRDI)
1.168 20247 Tributary Unit Type Mismatch (TUSIZEERR)
1.169 20248 Loss of Tributary Signals (LOS)
1.170 20249 Tributary Alarm Indication Signal (AIS)
1.171 20250 Loss of Tributary Frames (LOF)
1.172 20251 Remote Alarm Indication over the Tributary (RAI)
1.173 20252 Loss of Tributary Multi-Frames (LOM)
1.174 20253 Slip Frame over the Tributary
1.175 20254 Tributary Loopback Alarm
1.176 20255 Optical Module Fault
1.177 20271 Serial Port Fault
1.178 20272 Monitor Board Out of Position
1.179 20321 Unavailable Clock Reference for GGCU
1.180 20322 Unavailable Current Clock Reference for GGCU
1.181 20323 GGCU Failure-Abnormal Frequency Doubler
1.182 20324 GGCU Failure-Abnormal Local Oscillation Signal
1.183 20325 Clock Reference Failure of GGCU over 24 Hours
1.184 20329 Unavailable Input Clock Source for GGCU
1.185 20352 Clock Failure of the TDM Interface Unit
1-6 (2008-06-24)
1.186 20353 TDM Interface Unit Failure Alarm

1.187 20357 GEIUx/GOIUxTime slot loopback alarm
1.188 20359 TDM backplane Link Failure of TSU
1.189 20360 TDM backplane Link Failure of transaction board
1.190 20361 TDM panel Link Failure of TSU
1.191 20362 Master TDM link of TSU backplane fault alarm
1.192 20363 Master TDM link of transaction board backplane fault alarm
1.193 20364 Master TDM link of TSU panel fault alarm
1.194 20371 GE/FE Conversion Unit Fault
1.195 20372 GE Interface Unit Fault
1.196 20401 Board Fault-ME Fault
1.197 20409 Quality of GE Link on GSCU Backplane Decrease
1.198 20410 Quality of GE Link on GSCU Panel Decrease
1.199 20411 Quality of GE Link on Sub-Board Decrease
1.200 20412 Quality of GE Link on GXPUx Panel Decrease
1.201 20421 Abnormal Temperature
1.202 20422 Abnormal Voltage
1.203 20423 Communication Failure
1.204 20424 Abnormal Humidity
1.205 20425 Abnormal External Analog Sensor
1.206 20426 Abnormal External Digital Sensor
1.207 20427 Abnormal PDB Output Switch Sensor
1.208 20428 Abnormal PDB Power Sensor
1.209 20429 Abnormal PDB Lightning Protection Sensor
1.210 20430 Fan Box Temperature Sensor Invalidation
1.211 20431 Fan Block Alarm
1.212 20433 Fan Board Hardware Failure Alarm
1.213 20434 Board Register Successfully Alarm
1.214 20435 Failure in One Power Supply for the Fan Box
1.215 20436 Abnormal PDB Monitoring Board Component
1.216 20951 Status Change Event Alarm
1.217 20954 8k Clock reference source 0 from mainboard to BackPlane fault alarm
1.218 20955 8k Clock reference source 1 from mainboard to BackPlane fault alarm
(2008-06-24) 1-7
1.219 20956 19M SDH Clock reference source from BackPlane fault alarm
1.220 20957 8k SDH Clock reference source from BackPlane fault alarm
1.221 20958 32M TDM Clock reference source from BackPlane fault alarm
1.222 20959 8k TDM Clock reference source from BackPlane fault alarm
1.223 20960 2M Clock reference source 0 from up subboard fault alarm
1.224 20961 2M Clock reference source 1 from up subboard fault alarm
1.225 20962 2M Clock reference source from down subboard fault alarm
1.226 20963 Number of E1 Frame Slips Within 24 Hours Over Threshold
1.227 20964 Number of E1 Frame Slips Within 24 Hours Over Max Threshold
1.229 20966 SubBoard not exist
1.230 20967 OPT Module electrical current exceed high Threshold
1.231 20968 OPT Module electrical current exceed low Threshold
1.232 20969 Ethernet Link failure
1.233 20970 Ethernet Link Receive Defect Indication
1.234 20971 Ethernet Link Send Defect Indication
1.235 20972 Ethernet Link Loop
1.236 20973 OPT Module Temprature exceed high Threshold
1.237 20974 OPT Module Temprature exceed low Threshold
1.238 20975 OPT Module Voltage exceed high Threshold
1.239 20976 OPT Module Voltage exceed low Threshold
1.240 20977 Failure of High-Speed Communication Link on the Backplane of Service Boards
1.241 20978 COMM Channel Abnormal
1.243 20980 Ethernet Port Band Width Change
1.244 20981 Ethernet Port Duplex Mode Change
1.245 20982 OPT Module rx power exceed high Threshold
1.246 20983 OPT Module rx power exceed low Threshold
1.247 20984 OPT Module tx power exceed high Threshold
1.248 20985 OPT Module tx power exceed low Threshold
1.249 20988 Microcode Thread Abort
1.250 21001 LAPD Link Congestion
1.251 21002 Broken LAPD Link
1-8 (2008-06-24)
1.252 21019 Failed Loading of Board Software

1.253 21020 Software Version Inconsistency
1.254 21022 Faulty Remote Load Agent
1.255 21023 Inconsistent Sub-Board Alarm
1.256 21024 GBAM File Check Failure
1.257 21025 Patch not confirm
1.258 21026 GBAM/GOMU License Check Fail Alarm
1.259 21027 Remote EIU/OIU Board Connection Error
1.260 21028 Board Physical Type inconsistent
1.261 21030 Load License to SMU failed
1.262 21201 DSP Heartbeat Lost
1.263 21202 DSP Overload
1.264 21203 DSP Fault
1.265 21204 Unavailable Subrack
1.266 21205 Board Fault
1.267 21206 CPU Fault
1.268 21207 Board Hardware Self-Test Failure of Warning Level
1.269 21208 Board Hardware Self-Test Failure of Minor Level
1.270 21209 Board Hardware Self-Test Failure of Major Level
1.271 21210 CPU Overload
1.272 21211 Board Switchover
1.273 21212 DSP TDM Timeslot Link Unavailable
1.274 21213 HA Status Line Fault
1.275 21214 OMU Harddisk Overload Alarm
1.276 21215 XPU Port IP Conflict
1.277 21216 PowerBox Types Inconsistent
1.278 21250 Daemon Heartbeat Lost Alarm
1.279 21251 Daemon Version Not Match Alarm
1.280 21252 Backup Channel Between Daemons Break Alarm
1.281 21253 Interior Channel Between Daemons Break Alarm
1.282 21254 OMU Mode Switch Event Alarm
1.283 21255 Swap Result Event Alarm
1.284 21501 MTP3 DSP Unreachable
(2008-06-24) 1-9
1.285 21502 MTP3 Layer 3 Congestion

1.286 21503 MTP3 Link Unavailable
1.287 21504 MTP3 Signaling Link2 Congestion
1.288 21511 MTP3 Link Test Success
1.289 21512 MTP3 Link Test Failure
1.290 21513 MTP2 Link Location Failure
1.291 21514 MTP2 Link Service Disrupted
1.292 21516 Route Transmission on the MTP3 Prohibited
1.293 21518 MTP3 Link Layer 3 Congestion Released
1.294 21525 SCCP DSP Unreachable
1.295 21526 SCCP Subsystem Prohibited
1.296 21528 Remote SCCP Fault
1.297 21531 Lack of SCCP Connection Resources
1.298 21551 Ater OML Broken Alarm
1.299 21581 APS Started Alarm
1.300 21582 Deactivate APS Alarm
1.301 21583 APS Protocol Swap Alarm
1.302 21584 APS K1/K2 Mismatch Alarm
1.303 21585 APS K2 Mismatch Alarm
1.304 21586 APS Uni-Bid Mode Mismatch Alarm
1.305 21601 NTP Server unconfigured
1.306 21602 Adjust time failure with the NTP server
1.307 22001 Extern Water Sensor Alarm
1.308 22002 Extern Smoke Sensor Alarm
1.309 22003 Extern InfraRed Sensor Alarm
1.310 22004 Extern DoorEngine Sensor Alarm
1.311 22005 Extern Figure Sensor1 Alarm
1-10 (2008-06-24)

1.343 22051 Extern Simulate Sensor1 Alarm
1.347 65234 BTS Custom Environment Alarm1
(2008-06-24) 1-11

1-12 (2008-06-24)

(2008-06-24) 1-13

1.447 65334 BSC Custom Environment Alarm1
1-14 (2008-06-24)

(2008-06-24) 1-15

1-16 (2008-06-24)
1.1 BSC Alarm List

Alarm ID Alarm name Alarm Alarm type
type severit
y
ALM-101 MSC Overload Fault Minor Running
ALM-102 Disrupted Connection with the Fault Major Communica

CBC tion system
ALM-103 All SS7 Links Faulty Fault Critical Communica

tion system
ALM-124 No A Interface Circuit Configured Event Minor Software

in the BSC system
ALM-126 No Circuit Configured in the MSC Event Event Software

system
ALM-128 No Circuit Configured in the PCU Event Minor Software

system
ALM-129 MSC Resetting Event Minor Software

system
ALM-130 BSC Resetting Failure Event Minor Software

system
ALM-131 BSC Unable to Reset a Circuit Event Minor Software

system
ALM-132 BSC Unable to Block a Circuit Event Minor Software

system
ALM-133 BSC Unable to Unblock a Circuit Event Minor Software

system
ALM-134 BSC Unable to Block a Packet Event Minor Software

Circuit system
ALM-135 BSC Unable to Unblock a Packet Event Minor Software

Circuit system
ALM-136 BSC Unable to Reset a Packet Event Minor Software

Circuit system
ALM-137 BSC Unable to Unblock Group Event Minor Software

Circuits system
ALM-138 BSC Unable to Block Group Event Minor Software

Circuits system
ALM-139 No Group Circuits Configured on Event Minor Software

the BSC side system
(2008-06-24) 1-17

type severit
y
ALM-140 BSC Unable to Read License File Fault Critical Software

system
ALM-141 BSC Unable to Obtain License File Event Critical Software

system
ALM-142 Resource Overused Fault Minor Software

system
ALM-143 Resource Overused Event Alarm Event Minor Software

system
ALM-144 Simpermanent Link Event Major Software

Configuration Validation Failure system
ALM-145 No Group Circuits Configured on Event Minor Software

the MSC Side system
ALM-146 Satellite Transmission Supported Event Minor Software

Sites Blocked Due to License system
ALM-147 Extended Cells Blocked Due to Event Minor Software

License system
ALM-148 PBT-Supported DTRU Blocked Event Minor Software

Due to License system
ALM-149 Transmit-Diversity DTRU Event Minor Software

Blocked Due to License system
ALM-150 DTRU Blocked Due to License Event Minor Software

system
ALM-151 4-Way Diversity DTRU Blocked Event Minor Software

ALM-152 High-Output-Power TRU Blocked Event Minor Software

ALM-153 Cell Broadcast Short Message Fault Minor Software

Service Stopped Due to License system
ALM-154 Resource Usage Threshold Event Minor Software

Exceeded for Over 60 Times system
ALM-155 All Ater LapdLink Faulty Fault Critical Communica

tion system
ALM-156 DSP Resource Lack Fault Critical Software

system
ALM-157 License Inferior Limit Fault Major Software
ALM-158 License File Expired Event Major Software
1-18 (2008-06-24)

type severit
y
ALM-159 Lack TC Resource Event Minor Software

system
ALM-160 HDLC Link Fault Fault Minor Software

system
ALM-161 HDLC Link Congestion Fault Minor Software

system
ALM-201 Internal Flow Control Level Event Warnin Running

Changed g
ALM-202 Internal Flow Control Released Event Warnin Running

g
ALM-203 PDCH Configured on Overlayer Event Minor Running

with an old version PCU
ALM-205 TC Fault Alarm Event Warnin Running

g
ALM-291 Cell Transmission Delay Event Major Communica

Abnormal tion
ALM-293 GB BC Faulty Fault Critical Communica

tion
ALM-294 TRX Config Error Event Major Software
ALM-331 NSVC Faulty Fault Major Communica

tion
ALM-332 NSVL Faulty Fault Major Communica

tion
ALM-333 NSE Faulty Fault Critical Signaling
ALM-340 Cell PS Service Faulty Fault Critical Signaling
ALM-341 DSP Resource Overload Fault Critical Signaling
ALM-342 PTP BVC Faulty Fault Major Communica

tion
ALM-343 NSVL Dynamic Configuration Fault Critical Communica

Process Failure tion
ALM-344 FAULTY DSP OVER LIMIT Fault Critical Software
ALM-401 BCCH Mutual Aid in a Cell Event Major Software
ALM-402 Switchback after BCCH Mutual Event Major Software

Aid in a Cell
ALM-403 Baseband FH Mutual Aid in a Cell Event Major Software
(2008-06-24) 1-19

type severit
y
ALM-404 Switchback after Baseband FH Event Major Software

Mutual Aid in a Cell
ALM-405 Cell Out of Service Fault Major Software
ALM-407 BTS Initialization Event Minor Software
ALM-408 Automatic Activation of BTS Event Minor Software

TMU Version
ALM-409 Cell BCCH Aiding to IUO_INN Event Major Software

TRX
ALM-410 BTS's capabilty doesn't account Fault Major Software

with the config data
ALM-411 Site Reset for DynCfg Event Minor Software
ALM-412 Manually Obturate Cell Event Minor Software
ALM-413 Manually Obturate Trx Event Minor Software
ALM-414 Manually Obturate Channel Event Minor Software
ALM-416 SitePowerOff Event Major Power
ALM-417 BTS Loop Rotate Event Major Communica

tion
ALM-418 BTS Loop Rotateback Event Major Communica

tion
ALM-419 Query IP of PTU by Its electric Event Critical Software

label failed because of configration
error
ALM-420 BTS doesn't support config the Event Major Software

card and the logic object
separately
ALM-421 PTU Initialization Event Major Software
ALM-422 BTS doesn't support abis optimize Event Major Software
ALM-423 Extension Signaling Link Failure Fault Critical Communica

tion
ALM-701 M3UA Link Fault Fault Warnin Signaling

g
ALM-702 M3UA Link Congestion Fault Warnin Signaling

g
ALM-703 M3UA Route Unvailable Fault Warnin Signaling

g
1-20 (2008-06-24)

type severit
y
ALM-704 M3UA Destination Entity Fault Warnin Signaling

Unvailably g
ALM-705 FG2/GOU Route Status Fault Warnin Signaling

Unavailable g
ALM-801 Data Out of Synchronization Fault Critical Running
ALM-802 Error of Transaction Logging File Event Critical Running
ALM-951 TDM slot link error Event Minor Running
ALM-1000 LAPD OML Fault Fault Critical Communica

tion
ALM-20002 Incorrect Board Slot Information Fault Major Hardware
ALM-20003 Board Fault - Faulty Inner Clock Fault Major Hardware
ALM-20004 Board Fault-Abnormal Voltage Fault Major Hardware
ALM-20005 Faulty Clock Source 0 from the Fault Major Hardware

Front Interface Board to the
Backplane of the GSCU

Front Interface Board to the

Rear Interface Board to the

Rear Interface Board to the
ALM-20009 Faulty 8 kHz Clock Source from Fault Major Hardware

the Active GGCU to the Backplane
of the GSCU
ALM-20010 Faulty 8 kHz Clock Source from Fault Minor Hardware

the Standby GGCU to the
ALM-20013 Faulty GGCU 8 kHz Clock Source Fault Major Hardware

for the Front Panel of the GSCU
ALM-20016 Faulty 32 MHz Clock from the Fault Major Hardware

Backplane
ALM-20025 BIOS Check Failure Fault Major Hardware
(2008-06-24) 1-21

type severit
y
ALM-20026 Faulty Phase-Locked Loop of the Fault Major Hardware

Board Clock
ALM-20027 Abnormal Subrack Information Fault Major Hardware
ALM-20028 Faulty Packet Switching Unit Fault Major Hardware
ALM-20029 Board Fault - Faulty Logical Unit Fault Major Hardware
ALM-20030 Faulty Sub-Board Fault Major Hardware
ALM-20038 Faulty Board Chip Fault Major Hardware
ALM-20039 Faulty Output Clock Signals Fault Major Hardware
ALM-20040 High Board Temperature - Minor Fault Minor Hardware

Alarm
ALM-20041 High Board Temperature - Major Fault Major Hardware

Alarm
ALM-20042 High Board Temperature - Fault Critical Hardware

Critical Alarm
ALM-20044 Unavailable Clock Source Fault Major Hardware
ALM-20045 Failed to Get Temperature Fault Major Hardware
ALM-20052 Flash erase/write fail alarm Fault Minor Hardware
ALM-20081 Loss of E1 Signals (LOS) Fault Major Trunk
ALM-20082 Loss of E1 Frames (LOF) Fault Major Trunk
ALM-20083 Remote E1 Alarm (RAI) Fault Major Trunk
ALM-20084 E1 Alarm Indication Signal (AIS) Fault Major Trunk
ALM-20085 Loss of E1 Multiframes (LOM) Fault Major Trunk
ALM-20086 E1 Link Loopback Fault Warnin Trunk

g
ALM-20087 High BER over the E1 Link Fault Major Trunk
ALM-20089 Excessive Loss of E1 Signals in an Fault Major Trunk

Hour
ALM-20090 Excessive E1 Synchronization Fault Major Trunk

Failures in an Hour
ALM-20091 E1 Excessive Peer End Alarms Per Fault Major Trunk

Hour
1-22 (2008-06-24)

type severit
y
ALM-20092 E1 Excessive Bit Error Rate Per Fault Warnin Trunk

Hour g
ALM-20093 E1 Excessive Slip Frames Per Fault Warnin Trunk

Hour g
ALM-20113 Faulty GE Link on the Sub-board Fault Major Trunk

of GXPUx
ALM-20114 Inter-Board HIG Link Faulty Fault Major Hardware
ALM-20115 Intra-Board HIG Link Faulty Fault Critical Hardware
ALM-20116 Inter-Board HIG Trunk Fault Major Hardware

Communication Failure
ALM-20117 Board Fault-GE Switch Unit Fault Major Hardware

Failure
ALM-20118 Inter-Board HIG Communication Fault Major Hardware

Failure
ALM-20120 Broadcast packet overflow alarm Fault Major Communica

tion
ALM-20121 GESW BAM GE Communication Fault Warnin Trunk

Failure g
ALM-20122 GESW BAM Trunk Fault Warnin Trunk

Communication Failure g
ALM-20123 Faulty GE Link on the Panel of Fault Major Trunk

SCU board
ALM-20124 Faulty GE Link on the Panel of Fault Major Trunk

XPU board
ALM-20125 GESW Back Trunk Group Link Fault Major Trunk

Failure
ALM-20126 GE Trunk Group Link Fault of Fault Major Trunk

transaction board
ALM-20127 GESW Panel Trunk Group Link Fault Major Trunk

Failure
ALM-20128 Faulty GE Link on the Backplane Fault Minor Trunk

of SCU board
ALM-20129 Faulty GE Link on the Backplane Fault Minor Trunk

of transaction board
ALM-20164 Quality of GE Link on Service Fault Minor Trunk

Board Backplane Decrease
(2008-06-24) 1-23

type severit
y
ALM-20191 Board Faulty-Link Disconnection Fault Major Hardware

on the Service Port
ALM-20194 Disconnected Link Between the Fault Minor Hardware

Ports on the Active and Standby
GSCU
ALM-20221 Loss of Clock on the Optical Port Fault Major Trunk

(RLOC)
ALM-20222 Loss of Signals on the Optical Port Fault Major Trunk

(RLOS)
ALM-20223 Loss of Received Signal Frames on Fault Major Trunk

the Optical Port (RLOF)
ALM-20224 Out-of-Synchronization of Fault Major Trunk

Received Signal Frames on the
Optical Port (ROOF)
ALM-20225 Mismatch of Trace Byte of the Fault Major Trunk

Regenerator Section on the
Optical Port (RTIM)
ALM-20226 Regenerator Section Signal Fault Major Trunk

Failure (RSF)
ALM-20227 Regenerator Section Signal Fault Major Trunk

Deteriorated (RSD)
ALM-20228 Multiplex Section Alarm Fault Major Trunk

Indication Signal (MAIS)
ALM-20229 Multiplex Section Remote Defect Fault Major Trunk

Indication (MRDI)
ALM-20230 Loopback on the Optical Port Fault Minor Trunk
ALM-20231 Administration Unit Alarm Fault Major Trunk

Indication Signal (AUAIS)
ALM-20232 Loss of Administration Unit Fault Major Trunk

Pointer (AULOP)
ALM-20233 Service Unequipped on the High- Fault Major Trunk

Order Path of the Optical Port
(HPUNEQ)
ALM-20234 Trace Flag Mismatch on the High- Fault Major Trunk

(HPTIM)
1-24 (2008-06-24)

type severit
y
ALM-20235 High-Order Path Signal Label Fault Major Trunk

Byte Mismatch (HPSLM)
ALM-20236 High-Order Path Signal Failure Fault Major Trunk

(HPSF)
ALM-20237 High-Order Path Signal Fault Major Trunk

Deteriorated (HPSD)
ALM-20238 Remote Defect Indication on the Fault Major Trunk

High-Order Path of the Optical
Port (HPRDI)
ALM-20239 Loss of Tributary Unit Multi- Fault Major Trunk

frames (TULOM)
ALM-20240 Tributary Unit Alarm Indication Fault Major Trunk

Signal (TUAIS)
ALM-20241 Loss of Tributary Unit Pointer Fault Major Trunk

(TULOP)
ALM-20242 Service Unequipped on the Lower- Fault Major Trunk

(LPUNEQ)
ALM-20243 Trace Flag Mismatch on the Fault Major Trunk

Lower-Order Path of the Optical
Port (LPTIM)
ALM-20244 Signal Flag Mismatch on the Low- Fault Major Trunk

(LPSLM)
ALM-20245 Low-Order Path Remote Failure Fault Major Trunk

Indicaton (LPRFI)
ALM-20246 Low-Order Path Remote Defect Fault Major Trunk

Indication (LPRDI)
ALM-20247 Tributary Unit Type Mismatch Fault Major Trunk

(TUSIZEERR)
ALM-20248 Loss of Tributary Signals (LOS) Fault Major Trunk
ALM-20249 Tributary Alarm Indication Fault Major Trunk

Signal (AIS)
ALM-20250 Loss of Tributary Frames (LOF) Fault Major Trunk
ALM-20251 Remote Alarm Indication over the Fault Major Trunk

Tributary (RAI)
(2008-06-24) 1-25

type severit
y
ALM-20252 Loss of Tributary Multi-Frames Fault Minor Trunk

(LOM)
ALM-20253 Slip Frame over the Tributary Fault Minor Trunk
ALM-20254 Tributary Loopback Alarm Fault Minor Trunk
ALM-20255 Optical Module Fault Fault Major Hardware
ALM-20271 Serial Port Fault Fault Minor Hardware
ALM-20272 Monitor Board Out of Position Fault Minor Hardware
ALM-20321 Unavailable Clock Reference for Fault Minor Hardware

GGCU
ALM-20322 Unavailable Current Clock Fault Minor Hardware

Reference for GGCU
ALM-20323 GGCU Failure-Abnormal Fault Major Hardware

Frequency Doubler
ALM-20324 GGCU Failure-Abnormal Local Fault Major Hardware

Oscillation Signal
ALM-20325 Clock Reference Failure of GGCU Fault Major Hardware

over 24 Hours
ALM-20329 Unavailable Input Clock Source Fault Major Hardware

for GGCU
ALM-20352 Clock Failure of the TDM Fault Major Hardware

Interface Unit
ALM-20353 TDM Interface Unit Failure Fault Major Hardware

Alarm
ALM-20357 GEIUx/GOIUxTime slot loopback Fault Warnin Hardware

alarm g
ALM-20359 TDM backplane Link Failure of Fault Minor Hardware

TSU
ALM-20360 TDM backplane Link Failure of Fault Minor Hardware

transaction board
ALM-20361 TDM panel Link Failure of TSU Fault Minor Hardware
ALM-20362 Master TDM link of TSU Fault Major Hardware

backplane fault alarm
ALM-20363 Master TDM link of transaction Fault Major Hardware

board backplane fault alarm
1-26 (2008-06-24)

type severit
y
ALM-20364 Master TDM link of TSU panel Fault Major Hardware

fault alarm
ALM-20371 GE/FE Conversion Unit Fault Fault Major Hardware
ALM-20372 GE Interface Unit Fault Fault Minor Trunk
ALM-20401 Board Fault-ME Fault Fault Major Hardware
ALM-20409 Quality of GE Link on GSCU Fault Minor Trunk

Backplane Decrease
ALM-20410 Quality of GE Link on GSCU Fault Minor Trunk

Panel Decrease
ALM-20411 Quality of GE Link on Sub-Board Fault Major Hardware

Decrease
ALM-20412 Quality of GE Link on GXPUx Fault Minor Trunk

Panel Decrease
ALM-20421 Abnormal Temperature Fault Major Hardware
ALM-20422 Abnormal Voltage Fault Major Hardware
ALM-20423 Communication Failure Fault Major Hardware
ALM-20424 Abnormal Humidity Fault Major Hardware
ALM-20425 Abnormal External Analog Sensor Fault Major Hardware
ALM-20426 Abnormal External Digital Sensor Fault Major Hardware
ALM-20427 Abnormal PDB Output Switch Fault Major Hardware

Sensor
ALM-20428 Abnormal PDB Power Sensor Fault Major Hardware
ALM-20429 Abnormal PDB Lightning Fault Major Hardware

Protection Sensor
ALM-20430 Fan Box Temperature Sensor Fault Major Hardware

Invalidation
ALM-20431 Fan Block Alarm Fault Major Hardware
ALM-20433 Fan Board Hardware Failure Fault Major Hardware

Alarm
ALM-20434 Board Register Successfully Event Major Hardware

Alarm
ALM-20435 Failure in One Power Supply for Fault Major Hardware

the Fan Box
(2008-06-24) 1-27

type severit
y
ALM-20436 Abnormal PDB Monitoring Board Fault Major Hardware

Component
ALM-20951 Status Change Event Alarm Fault Minor Running
ALM-20954 8k Clock reference source 0 from Fault Major Hardware

mainboard to BackPlane fault
alarm
ALM-20955 8k Clock reference source 1 from Fault Major Hardware

mainboard to BackPlane fault
alarm
ALM-20956 19M SDH Clock reference source Fault Major Hardware

from BackPlane fault alarm
ALM-20957 8k SDH Clock reference source Fault Major Hardware

ALM-20958 32M TDM Clock reference source Fault Major Hardware

ALM-20959 8k TDM Clock reference source Fault Major Hardware

ALM-20960 2M Clock reference source 0 from Fault Major Hardware

up subboard fault alarm
ALM-20961 2M Clock reference source 1 from Fault Major Hardware

up subboard fault alarm
ALM-20962 2M Clock reference source from Fault Major Hardware

down subboard fault alarm
ALM-20963 Number of E1 Frame Slips Within Fault Warnin Trunk

24 Hours Over Threshold g
ALM-20964 Number of E1 Frame Slips Within Fault Warnin Trunk

24 Hours Over Max Threshold g
ALM-20965 Board Fault-Abnormal Voltage Fault Major Hardware
ALM-20966 SubBoard not exist Fault Major Hardware
ALM-20967 OPT Module electrical current Fault Major Hardware

exceed high Threshold
ALM-20968 OPT Module electrical current Fault Major Hardware

exceed low Threshold
ALM-20969 Ethernet Link failure Fault Major Trunk
ALM-20970 Ethernet Link Receive Defect Fault Minor Trunk

Indication
1-28 (2008-06-24)

type severit
y
ALM-20971 Ethernet Link Send Defect Fault Minor Trunk

Indication
ALM-20972 Ethernet Link Loop Fault Warnin Trunk

g
ALM-20973 OPT Module Temprature exceed Fault Major Hardware

high Threshold
ALM-20974 OPT Module Temprature exceed Fault Major Hardware

low Threshold
ALM-20975 OPT Module Voltage exceed high Fault Major Hardware

Threshold
ALM-20976 OPT Module Voltage exceed low Fault Major Hardware

Threshold
ALM-20977 Failure of High-Speed Fault Major Hardware

Communication Link on the
Backplane of Service Boards
ALM-20978 COMM Channel Abnormal Fault Critical Software
ALM-20979 Faulty Board Chip Fault Major Hardware
ALM-20980 Ethernet Port Band Width Event Major Trunk

Change
ALM-20981 Ethernet Port Duplex Mode Event Major Trunk

Change
ALM-20982 OPT Module rx power exceed high Fault Major Hardware

Threshold
ALM-20983 OPT Module rx power exceed low Fault Major Hardware

Threshold
ALM-20984 OPT Module tx power exceed high Fault Major Hardware

Threshold
ALM-20985 OPT Module tx power exceed low Fault Major Hardware

Threshold
ALM-20988 Microcode Thread Abort Fault Major Software
ALM-21001 LAPD Link Congestion Fault Major Communica

tion
ALM-21002 Broken LAPD Link Fault Critical Communica

tion
ALM-21019 Failed Loading of Board Software Fault Critical Software
(2008-06-24) 1-29

type severit
y
ALM-21020 Software Version Inconsistency Event Minor Software
ALM-21022 Faulty Remote Load Agent Fault Minor Software
ALM-21023 Inconsistent Sub-Board Alarm Fault Minor Software
ALM-21024 GBAM File Check Failure Event Major Software
ALM-21025 Patch not comfirm Event Major Software
ALM-21026 GBAM/GOMU License Check Event Major Software

Fail Alarm
ALM-21027 Remote EIU/OIU Board Fault Major Software

Connection Error
ALM-21028 Board Physical Type inconsistent Event Critical Software
ALM-21030 Load License to SMU failed Event Minor Software
ALM-21201 DSP Heartbeat Lost Fault Minor Software
ALM-21202 DSP Overload Fault Minor Software
ALM-21203 DSP Fault Fault Minor Software
ALM-21204 Unavailable Subrack Fault Critical Software
ALM-21205 Board Fault Fault Critical Software
ALM-21206 CPU Fault Fault Critical Software
ALM-21207 Board Hardware Self-Test Failure Fault Warnin Hardware

of Warning Level g
ALM-21208 Board Hardware Self-Test Failure Fault Minor Hardware

of Minor Level
ALM-21209 Board Hardware Self-Test Failure Fault Major Hardware

of Major Level
ALM-21210 CPU Overload Fault Major Software
ALM-21211 Board Switchover Event Warnin Software

g
ALM-21212 DSP TDM Timeslot Link Fault Minor Software

Unavailable
ALM-21213 HA Status Line Fault Fault Critical Hardware
ALM-21214 OMU Harddisk Overload Alarm Fault Minor Hardware
ALM-21215 XPU Port IP Conflict Fault Minor Software
ALM-21216 PowerBox Types Inconsistent Fault Major Software
1-30 (2008-06-24)

type severit
y
ALM-21250 Daemon Heartbeat Lost Alarm Fault Major Software
ALM-21251 Daemon Version Not Match Fault Major Software

Alarm
ALM-21252 Backup Channel Between Fault Major Software

Daemons Break Alarm
ALM-21253 Interior Channel Between Fault Major Software

Daemons Break Alarm
ALM-21254 OMU Mode Switch Event Alarm Event Major Software
ALM-21255 Swap Result Event Alarm Event Major Software
ALM-21501 MTP3 DSP Unreachable Fault Major Signaling
ALM-21502 MTP3 Layer 3 Congestion Event Major Signaling
ALM-21503 MTP3 Link Unavailable Fault Minor Signaling
ALM-21504 MTP3 Signaling Link2 Congestion Fault Warnin Signaling

g
ALM-21511 MTP3 Link Test Success Event Warnin Signaling

g
ALM-21512 MTP3 Link Test Failure Event Warnin Signaling

g
ALM-21513 MTP2 Link Location Failure Event Warnin Signaling

g
ALM-21514 MTP2 Link Service Disrupted Event Minor Signaling
ALM-21516 Route Transmission on the MTP3 Fault Major Signaling

Prohibited
ALM-21518 MTP3 Link Layer 3 Congestion Event Minor Signaling

Released
ALM-21525 SCCP DSP Unreachable Fault Critical Signaling
ALM-21526 SCCP Subsystem Prohibited Fault Critical Signaling
ALM-21528 Remote SCCP Fault Fault Major Signaling
ALM-21531 Lack of SCCP Connection Event Warnin Signaling

Resources g
ALM-21551 Ater OML Broken Alarm Fault Critical Communica

tion
ALM-21581 APS Started Alarm Event Warnin Communica

g tion
(2008-06-24) 1-31

type severit
y
ALM-21582 Deactivate APS Alarm Event Warnin Communica

g tion
ALM-21583 APS Protocol Swap Alarm Event Warnin Communica

g tion
ALM-21584 APS K1/K2 Mismatch Alarm Fault Major Communica

tion
ALM-21585 APS K2 Mismatch Alarm Fault Major Communica

tion
ALM-21586 APS Uni-Bid Mode Mismatch Fault Major Communica

Alarm tion
ALM-21601 NTP Server unconfigured Fault Major Software
ALM-21602 Adjust time failure with the NTP Fault Major Software
server
ALM-22001 Extern Water Sensor Alarm Fault Major Environme

nt
ALM-22002 Extern Smoke Sensor Alarm Fault Major Environme

nt
ALM-22003 Extern InfraRed Sensor Alarm Fault Major Environme

nt
ALM-22004 Extern DoorEngine Sensor Alarm Fault Major Environme

nt
ALM-22005 Extern Figure Sensor1 Alarm Fault Major Environme

nt

nt

nt

nt

nt

nt

nt
1-32 (2008-06-24)

type severit
y

nt

nt

nt

nt

nt

nt

nt

nt

nt

nt

nt

nt

nt

nt

nt

nt

nt

nt
(2008-06-24) 1-33

type severit
y

nt

nt

nt

nt

nt

nt

nt
ALM-22051 Extern Simulate Sensor1 Alarm Fault Major Environme

nt

nt

nt

nt
ALM-65234 BTS Custom Environment Fault Major Environme

Alarm1 nt

Alarm2 nt

Alarm3 nt

Alarm4 nt

Alarm5 nt

Alarm6 nt

Alarm7 nt
1-34 (2008-06-24)

type severit
y

Alarm8 nt

Alarm9 nt

Alarm10 nt

Alarm11 nt

Alarm12 nt

Alarm13 nt

Alarm14 nt

Alarm15 nt

Alarm16 nt

Alarm17 nt

Alarm18 nt

Alarm19 nt

Alarm20 nt

Alarm21 nt

Alarm22 nt

Alarm23 nt

Alarm24 nt

Alarm25 nt
(2008-06-24) 1-35

type severit
y

Alarm26 nt

Alarm27 nt

Alarm28 nt

Alarm29 nt

Alarm30 nt

Alarm31 nt

Alarm32 nt

Alarm33 nt

Alarm34 nt

Alarm35 nt

Alarm36 nt

Alarm37 nt

Alarm38 nt

Alarm39 nt

Alarm40 nt

Alarm41 nt

Alarm42 nt

Alarm43 nt
1-36 (2008-06-24)

type severit
y

Alarm44 nt

Alarm45 nt

Alarm46 nt

Alarm47 nt

Alarm48 nt

Alarm49 nt

Alarm50 nt

Alarm51 nt

Alarm52 nt

Alarm53 nt

Alarm54 nt

Alarm55 nt

Alarm56 nt

Alarm57 nt

Alarm58 nt

Alarm59 nt

Alarm60 nt

Alarm61 nt
(2008-06-24) 1-37

type severit
y

Alarm62 nt

Alarm63 nt

Alarm64 nt

Alarm65 nt

Alarm66 nt

Alarm67 nt

Alarm68 nt

Alarm69 nt

Alarm70 nt

Alarm71 nt

Alarm72 nt

Alarm73 nt

Alarm74 nt

Alarm75 nt

Alarm76 nt

Alarm77 nt

Alarm78 nt

Alarm79 nt
1-38 (2008-06-24)

type severit
y

Alarm80 nt

Alarm81 nt

Alarm82 nt

Alarm83 nt

Alarm84 nt

Alarm85 nt

Alarm86 nt

Alarm87 nt

Alarm88 nt

Alarm89 nt

Alarm90 nt

Alarm91 nt

Alarm92 nt

Alarm93 nt

Alarm94 nt

Alarm95 nt

Alarm96 nt

Alarm97 nt
(2008-06-24) 1-39

type severit
y

Alarm98 nt

Alarm99 nt

Alarm100 nt
ALM-65334 BSC Custom Environment Fault Major Environme

Alarm1 nt

Alarm2 nt

Alarm3 nt

Alarm4 nt

Alarm5 nt

Alarm6 nt

Alarm7 nt

Alarm8 nt

Alarm9 nt

Alarm10 nt

Alarm11 nt

Alarm12 nt

Alarm13 nt

Alarm14 nt

Alarm15 nt
1-40 (2008-06-24)

type severit
y

Alarm16 nt

Alarm17 nt

Alarm18 nt

Alarm19 nt

Alarm20 nt

Alarm21 nt

Alarm22 nt
ALM-65356 BSC Custom Environment Fault Environme

Alarm23 nt

Alarm24 nt

Alarm25 nt

Alarm26 nt

Alarm27 nt

Alarm28 nt

Alarm29 nt

Alarm30 nt

Alarm31 nt

Alarm32 nt

Alarm33 nt
(2008-06-24) 1-41

type severit
y

Alarm34 nt

Alarm35 nt

Alarm36 nt

Alarm37 nt

Alarm38 nt

Alarm39 nt

Alarm40 nt

Alarm41 nt

Alarm42 nt

Alarm43 nt

Alarm44 nt

Alarm45 nt

Alarm46 nt

Alarm47 nt

Alarm48 nt

Alarm49 nt

Alarm50 nt
1-42 (2008-06-24)
1.2 101 MSC Overload

Description
This alarm is reported when the MSC sends the BSC an Overload message, indicating that MSC
is congested.
Attribute
Alarm ID Alarm Severity Alarm Type

101 Minor Fault
Parameters
ID Name Meaning
1 NI l 0 = International
l 1 = Spare international
l 2 = National
l 3 = Spare national
2 OPC This parameter indicates the original signaling point code of the BSC.
3 DPC This parameter indicates the destination signaling point code of the overloaded
MSC.
4 Cause l 7=OM interference

l 35=CCCH overload
l 36=CPU overload
Impact on System
If the MSC is congested, the MSC starts flow control. Some services may be disrupted.
System Actions
The MSC starts flow control to adjust the traffic volume.
Possible Causes
l 7=OM interference
l 35=CCCH overload
l 36=CPU overload
(2008-06-24) 1-43
Handling Procedure
Contact MSC maintenance engineers to check the MSC.

No processing is required on the BSC side.
----End
1.3 102 Disrupted Connection with the CBC

Description
This alarm is reported when the connection with the CBC is interrupted.
Attribute
102 Major Fault
Parameters
ID Name Meaning
1 Subrack No. This parameter indicates the number of the subrack where the XPUC
board is located.
2 Logical Slot No. This parameter indicates the number of the slot where the XPUC board
is located.
Impact on System
The broadcast command from the new cell cannot be received.
System Actions
The BSC sends connection setup requests to the CBC every 0.5 seconds, attempting to recover
the connection.
Possible Causes
l The network communication between the BSC and the CBC is interrupted.
l The CBC software fails, or the CBC is not running.
Handling Procedure
Step 1 Check whether the network communication between the BSC and the CBC is normal.
Y => Go to step 2.
1-44 (2008-06-24)
N => The network communication fails. Check that the network connection between the CBC
and the BSC is normal.
Step 2 Check whether the CBC software is functional.

Y => Refer to the section "Routine Maintenance and Troubleshooting" in the User Guide in the
cell broadcast database.
N => Run the files Cell Broadcast Server.exe and Huawei.exe. For details about the running
method, refer to the CBC user manual.
----End
1.4 103 All SS7 Links Faulty

Description
This alarm is reported when all the signaling links that connect the MSC are faulty.
Attribute
103 Critical Fault
Parameters
ID Name Meaning
l 2 = National
2 OPC This parameter indicates the original signaling point code of the BSC.
3 DPC This parameter indicates the destination signaling point code of the MSC.
Impact on System
The circuit service of the MSC cannot be carried out.
System Actions
All the call resources are released.
Possible Causes
l The E1 links on the A interface or the ATER interface are faulty.
l The interface units (GEIUA/GOIUA and GEIUT/GOIUT) are abnormal.
(2008-06-24) 1-45
l The configuration of the SS7 is modified.

l The signaling links at the MSC are broken manually.
l The MSC equipment is Fault.
Handling Procedure
Step 1 Check whether any E1 alarm is reported ( 1.111 20081 Loss of E1 Signals (LOS),1.112 20082
Loss of E1 Frames (LOF),1.113 20083 Remote E1 Alarm (RAI),1.114 20084 E1 Alarm
Indication Signal (AIS)).
Y=>Refer to the related alarm handling suggestions
N=>Go to step 2.
Step 2 Check if the interface board of local end and remote end is functional.
Y=> The interface unit of the local office and the MSC are normal. Go to step 4.
N=> The interface unit of the local office and the MSC are abnormal. Go to step 3.
Step 3 Reset the board. Check whether the alarm is cleared.

Y=>The alarm is cleared. The alarm handling is complete.
N=>The alarm persists. Please contact Motorola for technical support.
Step 4 Check whether the data configured at local office and the MSC are consistent.
Y=> Go to step 5.
N=> Modify data on the MSC or the BSC to keep the data on the two sides consistent.
Step 5 Check whether the signaling links at the MSC are broken manually.
N=> Go to step 6.
Step 6 Please contact the maintenance technicians to check whether the MSC equipment is faulty.
Y=> The alarm is cleared. The alarm handling is complete.
N=> Please contact Motorola for technical support.
----End
1.5 124 No A Interface Circuit Configured in the BSC

Description
This alarm is reported in the following conditions:
l The MSC sends a circuit maintenance (such as resetting a circuit) message to the BSC, but
the corresponding circuit is not configured in the BSC. Then BSC sends the "Unequipped
Circuit" message to the MSC.
l The MSC sends an assignment request or a switchover request to the BSC, if the circuit
identification code (CIC) in the assignment request or in the switchover requests is not
configured in the BSC. Then BSC sends the "Unequipped Circuit" message to the MSC
and reports the alarm.
1-46 (2008-06-24)
Attribute
124 Minor Event
Parameters
ID Name Meaning
1 DPCGROUP This parameter indicates the DPCGROUP of the circuit that is not
configured.
2 CIC This parameter indicates the circuit identification code (CIC) of the circuit
that is not configured.
3 OSP This parameter indicates that original signaling point (OSP) of the subrack
where the circuit is located.
Impact on System
If the CIC in an assignment request that the MSC sends to the BSC is not configured in the BSC,
the call fails. If the CIC in a switchover request that the MSC sends to the BSC is not configured
in the BSC, the switchover fails.
System Actions
The BSC sends the "Unequipped Circuit" message to the MSC.
Possible Causes
l The CIC configuration in the BSC is inconsistent with that in the MSC. For example, the
number of configured CICs or CIC range is different.
l The circuit state configured in the BSC is inconsistent with that configured in the MSC.
Handling Procedure
Step 1 Check whether the CIC configuration (for example, the number of configured CICs or the CIC
scope) in the BSC is consistent with that in the MSC.
Y => Go to step 2.
N => Delete redundant CIC data from the MSC, or add required CIC data into the BSC.
Step 2 Check whether the circuit state configured in the BSC is consistent with that configured in the
MSC.
Y => Please contact Motorola for technical support.
N => Modify the circuit state configuration in the BSC or in the MSC and ensure that the BSC
and the MSC are consistent in the circuit state configuration.
----End
(2008-06-24) 1-47
1.6 126 No Circuit Configured in the MSC

Description
This alarm is reported when the BSC sends a circuit maintenance (such as resetting a circuit)
message to the MSC, but the MSC is not configured with the corresponding circuit, the MSC
sends the "The circuit is not configured" message to the BSC.
Attribute
126 Event Event
Parameters
ID Name Meaning
1 DPCGROUP This parameter indicates the DPCGROUP of the circuit that is not
configured.
2 CIC This parameter indicates the circuit identification code (CIC) of the circuit
that is not configured.
3 OSP This parameter indicates that original signaling point (OSP) of the subrack
where the circuit is located.
Impact on System
The MSC does not assign a circuit that is not configured in the MSC, no impact is caused on the
system.
System Actions
The BSC does nothing but receives the "The circuit is not configured" message from the MSC.
Possible Causes
l The CIC configuration in the BSC is inconsistent with that in the MSC. For example, the
number of configured CICs or the CIC range is different.
l The circuit state configured in the BSC is inconsistent with that configured in the MSC.
Handling Procedure
scope) in the MSC is consistent with that in the BSC.
Y => Go to step 2.
1-48 (2008-06-24)
N => Delete redundant CIC data from the BSC, or add required CIC data into the MSC.
Step 2 Check whether the circuit state configured in the MSC is consistent with that configured in the
BSC.
----End
1.7 128 No Circuit Configured in the PCU

Description
This alarm is reported when the circuit specified by a PCIC is not configured in the PCU, but it
is configured in the BSC.
Attribute

128 Minor Event
Parameters
ID Name Meaning
1 Subrack No. This parameter indicates the number of the subrack where the Alarm
port is located.
2 Logical Slot No. This parameter indicates the number of the slot where the Alarm port
is located.
3 Port No. This parameter indicates the number of the slot where the Alarm port
is located.
4 PCU No. This parameter indicates the number of the PCU on one end of the
packet circuit entity.
Impact on System
None.
System Actions
None.
(2008-06-24) 1-49
Possible Causes
l The PCIC (number of PCICs or PCIC range) in the BSC is inconsistent with that in the
PCU.
l The circuit state in the BSC is inconsistent with that in the.
Handling Procedure
Step 1 Check whether the PCIC in the BSC is consistent with that in the PCU.
Y=> The PCIC in the BSC is consistent with that in the PCU. Go to step 2.
N=> The PCIC in the BSC is inconsistent with that in the PCU. Delete the redundant PCICs
from the BSC or add a PCIC to the PCU.
Step 2 Check whether the circuit state in the BSC is consistent with that in the PCU.
Y=> The circuit states are consistent. Please contact Motorola for technical support.
N=> The circuit states are inconsistent. Modify the state in the BSC or PCU to make them
consistent.
----End
1.8 129 MSC Resetting

Description
The alarm is generated when the BSC receives a Reset message from the MSC.
Attribute
129 Minor Event
Parameters
ID Name Meaning
1 OSP This parameter indicates OSP of the subrack where the BSC receives a Reset
message from the MSC.
l 2 = National
Impact on System
All ongoing calls will be released.
1-50 (2008-06-24)
System Actions
The BSC releases all ongoing calls.
Possible Causes
l The MSC is reset manually.
l The equipment is not operational.
Handling Procedure
Contact MSC maintenance engineers to locate the cause of the MSC resetting.
----End
1.9 130 BSC Resetting Failure

Description
This alarm is reported when the attempts that the BSC sends Reset messages to the MSC expire
N times. The alarm indicates that the BSC fails to reset. The parameter N indicates "bsc reset
message max retrans in A-interface". The value of N can be set on the LMT. To set the value of
N on the LMT, log in to the LMT. Select "BSC Root Node", right-click, and click Configure
BSC Attributes. In the Configure BSC Attributes interface, select the Software Parameters tab.
Then you can set the value.
Attribute
130 Minor Event
Parameters
ID Name Meaning
1 OSP This parameter indicates the OSP of the subrack where the BSC receives a Reset
message from the MSC but the resetting fails.
l 2 = National
Impact on System
Perhaps the call resources fail to be released from the MSC in due time.
(2008-06-24) 1-51
System Actions
None.
Possible Causes
l The SS7 link has intermittent bit errors.
Handling Procedure
Check whether the fault alarms (1.111 20081 Loss of E1 Signals (LOS),1.112 20082 Loss of
E1 Frames (LOF)).
Y => Refer to the handling suggestions for clearing E1 alarms.
No => Please contact Motorola for technical support.
----End
1.10 131 BSC Unable to Reset a Circuit

Description
This alarm is reported when the BSC fails to send a reset message to the MSC for N times. The
alarm indicates that the circuit fails to be reset. The parameter N indicates "Max Retrans Reset
Circuit Message on A-Interface". The value of N can be set on the LMT. To set the value of N,
log in to LMT. Select "BSC Root Node", right-click, and click Configure BSC Attributes. In the
Configure BSC Attributes interface, select the Software Parameters tab. Then you can set the
value.
Attribute
131 Minor Event
Parameters
ID Name Meaning
1 DPCGROUP This parameter indicates the DPCGROUP of the reset circuit that is not
configured.
2 CIC This parameter indicates the circuit identification code (CIC) of the reset
circuit that is not configured.
3 OSP This parameter indicates the original signaling point (OSP) of the subrack
where the reset circuit is located.
Impact on System
The BSC circuit state and MSC circuit state are inconsistent.
1-52 (2008-06-24)
System Actions
None.
Possible Causes
The SS7 link has intermittent bit errors.
Handling Procedure
E1 Frames (LOF)).
----End
1.11 132 BSC Unable to Block a Circuit

Description
This alarm is reported when the BSC sends Block messages twice to the MSC but has no replies
from the MSC.
Attribute

132 Minor Event
Parameters
ID Name Meaning
1 DPCGROUP This parameter indicates the DPCGROUP of the block circuit that is not
configured.
2 CIC This parameter indicates the circuit identification code (CIC) of the block
circuit that is not configured.
where the block circuit is located.
Impact on System
The state of the circuit in the BSC is inconsistent with that in the MSC. If the MSC assigns the
circuit for a call, the call fails.
(2008-06-24) 1-53
System Actions
None.
Possible Causes
Handling Procedure
E1 Frames (LOF)).
----End
1.12 133 BSC Unable to Unblock a Circuit

Description
This alarm is reported when the BSC sends Unblock messages twice to the MSC but has no
replies from the MSC.
Attribute

133 Minor Event
Parameters
ID Name Meaning
1 DPCGROUP This parameter indicates the DPCGROUP of the unblock circuit that is not
configured.
2 CIC This parameter indicates the circuit identification code (CIC) of the
unblock circuit that is not configured.
where the unblock circuit is located.
Impact on System
The state of the circuit in the BSC is inconsistent with that in the MSC, causing a decrease in
available circuit resources.
1-54 (2008-06-24)
System Actions
None.
Possible Causes
Handling Procedure
E1 Frames (LOF)).
----End
1.13 134 BSC Unable to Block a Packet Circuit

Description
This alarm is reported when the BSC sends Block messages to the PCU but has not received any
response from the PCU.
Attribute
134 Minor Event
Parameters
ID Name Meaning
1 CIC This parameter indicates the identification code of the circuit that is
unsuccessfully blocked.
Impact on System
The state of the circuit in the BSC is inconsistent with that in the PCU. If the PCU assigns the
circuit for a packet service, the packet service fails.
System Actions
None.
Possible Causes
The LPAD signalling link between the BSC and the PCU is faulty.
(2008-06-24) 1-55
Handling Procedure
N=>Go to step 2.
Step 2 Check whether the GDPUP board is manually blocked.
Y => The alarm handling is complete.
N => Go to step 3.
Step 3 Check whether the GDPUP board is faulty.
Y => Go to step.4
N => Please contact Motorola for technical support.
Step 4 Reset the GDPUP board. Check whether the alarm is restored.
----End
1.14 135 BSC Unable to Unblock a Packet Circuit

Description
This alarm is reported when the BSC sends Unblock messages to the PCU but has not received
any response from the PCU.
Attribute
135 Minor Event
Parameters
ID Name Meaning
unsuccessfully unblocked.
Impact on System
The circuit state in the BSC is inconsistent with that in the PCU. If the PCU assigns the circuit
for a packet service, the packet service fails.
System Actions
None.
1-56 (2008-06-24)
Possible Causes
The LPAD signalling link between the BSC and the PCU is faulty.
Handling Procedure
N=>Go to step 2.
N => Go to step 3.
Y => Go to step.4
----End
1.15 136 BSC Unable to Reset a Packet Circuit

Description
This alarm is reported when the BSC sends Reset messages to the PCU but has not received any
response from the PCU.
Attribute
136 Minor Event
Parameters
ID Name Meaning
unsuccessfully reset.
Impact on System
The state of the circuit in the BSC is inconsistent with that in the PCU. The PCU cannot release
circuits in time.
(2008-06-24) 1-57
System Actions
None.
Possible Causes
The LPAD signaling link between the BSC and the PCU is faulty.
Handling Procedure
N=>Go to step 2.

N => Go to step 3.

Y => Go to step.4
----End
1.16 137 BSC Unable to Unblock Group Circuits

Description
This alarm is reported when the BSC sends Group Unblock messages twice to the MSC but has
no replies from the MSC.
Attribute
137 Minor Event
Parameters
ID Name Meaning
1 OSP This parameter indicates the original signaling point (OSP) of the subrack where
the circuit is located.
1-58 (2008-06-24)
ID Name Meaning
2 CIC This parameter indicates the identification code of the circuit through which the
BSC sends Group Unblock messages.
3 Para1 This parameter indicates the circuit bitmap that requires to send the alarm.
Impact on System
The state of the circuit in the BSC is inconsistent with that in the MSC, causing a decrease in
available circuit resources
System Actions
None.
Possible Causes
Handling Procedure
E1 Frames (LOF)).
----End
1.17 138 BSC Unable to Block Group Circuits

Description
This alarm is reported when the BSC sends Group Block messages twice to the MSC but has no
replies from the MSC.
(2008-06-24) 1-59
Attribute
138 Minor Event
Parameters
ID Name Meaning
1 OSP This parameter indicates the original signaling point (OSP) of the subrack where
the circuit is located.
2 CIC This parameter indicates the identification code of the circuits through which the
BSC sends Group Block messages.
3 Para1 This parameter indicates the bitmap that shows circuit alarms.
Impact on System
The state of the circuit in the BSC is inconsistent with that in the MSC. If the MSC assigns the
circuit for a call, the call fails.
System Actions
None.
Possible Causes
Handling Procedure
E1 Frames (LOF)).
1-60 (2008-06-24)

----End
1.18 139 No Group Circuits Configured on the BSC side

Description
This alarm is reported in the following conditions :
l The MSC sends a circuit maintenance (such as blocking a circuit) message to the BSC, but
the BSC is not configured with the corresponding circuit, the BSC sends the "Unequipped
Circuit" message to the MSC.
l The MSC sends an assignment request or a switchover request to the BSC, if the circuit
identification code (CIC) of the circuit bitmap in the assignment request or in the switchover
requests is not configured on the BSC side, the BSC sends the "Unequipped Circuit"
message to the MSC .
Attribute
139 Minor Event
Parameters
ID Name Meaning
1 OSP This parameter indicates the signaling point of the subrack where the circuit is
located.
2 CIC This parameter indicates the identification code of the circuit through which the
BSC sends Group Unequipped Circuit messages.
(2008-06-24) 1-61
ID Name Meaning
Impact on System
If the MSC assigns a circuit number which is not configured in the BSC , the paging or the intra-
BSC handover fails.
System Actions
None.
Possible Causes
The circuit configuration on the BSC side is inconsistent with that on the MSC side.
Handling Procedure
Y => Go to step 2.
MSC.
----End
1.19 140 BSC Unable to Read License File

Description
This alarm is reported when the BSC fails to read the License file.
Attribute

140 Critical Fault
Impact on System
The functions and resources of the BSC system are restricted.
1-62 (2008-06-24)
System Actions
The system uses the default values for the License control items. The functions controlled by
the License are unavailable and as a result the resources cannot be used.
Possible Causes
l The License file is not available.
l The License file expires.
l The License file is not activated.
Handling Procedure
Step 1 Check whether the License file is available.
Y => Go to step 2.
N => Download and activate the License file.
Step 2 Confirm the application date and validity period of the License file with the maintenance
personnel of the customer. Check whether the License file expires.
Y => Apply a new License file.
N => Go to step 3.
Step 3 Check whether the License file is activated.

N => Activate the License file.
----End
1.20 141 BSC Unable to Obtain License File

Description
This alarm is reported when the BSC fails to obtain the License file.
Attribute

141 Critical Event
Impact on System
None.
System Actions
None.
(2008-06-24) 1-63
Possible Causes
Handling Procedure
Y => Go to step 2.
N => Go to step 3.
----End
1.21 142 Resource Overused

Description
This alarm is reported when the BSC resource is utilized more than what the License allows.
Attribute
142 Minor Fault
1-64 (2008-06-24)
Parameters
ID Name Meaning
1 Resource Name l 0 = Channel resource that uses EDGE function
l 1 = HR channel resource
l 2 = AMR channel resource
l 3 = Number of TRXs
l 4=Number of the site supporting satellite transmission
l 5=Number of the extended cell
l 6=Number of DTRU which Transmitter is PBT
l 7=Number of DTRU which Transmitter is Diversity Transmitter
l 8=Number of DTRU which works as Dual Transceiver
l 9=Number of DTRU which Receiver is Four Diversity Receiver
l 10= Number of high output power TRU
l 11= channel resource of the extended cell
l 12= Number of TRX supporting BTS local switching
l 13= Number of TRX supporting BSC Local Switching
l 14= Number of TRX supporting Flex Abis
l 15= Number of NACC cell
l 16=Number of NC2 cell
l 17 = Maximum number of 64 kbit/s Gb links supported by GB OVER
FR
IP
l 19 = Maximum number of PDCHs that can be activated
Impact on System
l If the resource utilization does not exceed "License Forbid Threshold", the system is
allowed to continue to assign resource. If the resource utilization exceeds "License Forbid
Threshold", the system is prohibited to assign resource.
l How to check whether the resource utilization exceeds the threshold.
System Actions
None.
Possible Causes
The alarm ID resource is overused.
Handling Procedure
(2008-06-24) 1-65
Please contact Motorola for technical support to apply for more License files.
----End
1.22 143 Resource Overused Event Alarm

Description
This alarm is reported when the BSC resource is utilized more than what the License allows.
Attribute

143 Minor Event
Parameters
ID Name Meaning
1 Resource Name l 0 = Channel resource that uses EDGE function
l 1 = HR channel resource
l 2 = AMR channel resource
l 3 = Number of TRXs
l 4=Number of the site supporting satellite transmission
l 5=Number of the extended cell
l 6=Number of DTRU which Transmitter is PBT
l 7=Number of DTRU which Transmitter is Diversity Transmitter
l 8=Number of DTRU which works as Dual Transceiver
l 9=Number of DTRU which Receiver is Four Diversity Receiver
l 10= Number of high output power TRU
l 11= channel resource of the extended cell
l 12= Number of TRX supporting BTS local switching
l 13= Number of TRX supporting BSC Local Switching
l 14= Number of TRX supporting Flex Abis
l 15= Number of NACC cell
l 16=Number of NC2 cell
FR
IP
l 19 = Maximum number of PDCHs that can be activated
1-66 (2008-06-24)
Impact on System
None.
System Actions
None.
Possible Causes
The resource is overused.
Handling Procedure
Please contact Motorola for technical support to apply for more License files.
----End
1.23 144 Simpermanent Link Configuration Validation

Failure
Description
This alarm is reported when the configured semipermanent link fails to take effect.
Attribute

144 Major Event
Impact on System
The currently-configured semipermanent connection fails to take effect.
System Actions
None.
Possible Causes
l The License file does not allow the semipermanent connection function.
(2008-06-24) 1-67
Handling Procedure
Y => Go to step 2.
N => Go to step 3.

Step 4 Check whether the License file prohibits the semipermanent connection function.
Y => Download and activate a License file that allows the semipermanent connection function.
----End
1.24 145 No Group Circuits Configured on the MSC Side

Description
This alarm is reported when the BSC sends a circuit maintenance (such as blocking a circuit)
message to the MSC, but the MSC is not configured with the corresponding circuit, the MSC
sends the "Unequipped Circuit" message to the BSC.
Attribute
145 Minor Event
Parameters
ID Name Meaning
1 OSP This parameter indicates the signaling point of the subrack where the circuit is
located.
2 CIC This parameter indicates the circuit identification code (CIC) that the MSC sends
Group Unequipped messages.
1-68 (2008-06-24)
ID Name Meaning
Impact on System
The MSC does not assign a circuit that is not configured on the MSC side, so no impact is caused
on the system.
System Actions
The BSC does nothing but receives the "Unequipped Circuit" message from the MSC.
Possible Causes
The circuit configuration in the BSC is inconsistent with that in the MSC .
Handling Procedure
Y => Go to step 2.
MSC.
----End
1.25 146 Satellite Transmission Supported Sites Blocked

Due to License
Description
This alarm is reported when the GPS-supported sites are blocked due to License.
(2008-06-24) 1-69
Attribute
146 Minor Event
Parameters
ID Name Meaning
1 Site index This parameter indicates the number of the site to be blocked.
Impact on System
The redundant GPS-supported sites which are restricted by the License are blocked.
System Actions
None.
Possible Causes
l A License file does not exist.
l The number of serving GPS-supported sites exceed that allowed by the License.
Handling Procedure
Step 1 Check whether the License file exists.
Y=> Go to step 2.
N=> Download a License file and then activate it.
Y=> Re-apply a License file.
N=> Go to step 3.

Y=> Go to step 4.
N=> Activate the License file.
Step 4 Check whether the serving GPS-supported sites exceed the number allowed by the License.
Y=> The serving GPS-supported sites exceed the number allowed by the License. Download
additional License files to those GPS-supported sites, and then activate them.
N => The serving GPS-supported sites do not exceed the number allowed by the License. Please
contact Motorola for technical support.
----End
1-70 (2008-06-24)
1.26 147 Extended Cells Blocked Due to License

Description
This alarm is reported when the extension cells are blocked due to License.
Attribute
147 Minor Event
Parameters
ID Name Meaning
1 Cell index This parameter indicates the number of the cell to be blocked.
Impact on System
The redundant extension cells which are restricted by the License are blocked.
System Actions
None.
Possible Causes
l The number of serving extension cells exceed the number allowed by the License.
Handling Procedure
Y=> Go to step 2.
N=> Go to step 3.
Y=> Go to step 4.
(2008-06-24) 1-71
Step 4 Check whether the serving extension cells exceed the number allowed by the License.
Y=> Download additional License files to those extension cells, and then activate them.
----End
1.27 148 PBT-Supported DTRU Blocked Due to License

Description
This alarm is reported when the PBT DTRUs are blocked due to License.
Attribute
148 Minor Event
Parameters
ID Name Meaning
1 DTRU index This parameter indicates the number of the DTRU to be blocked.
Impact on System
The redundant PBT DTRUs which are restricted by the License are blocked.
System Actions
None.
Possible Causes
l The number of serving PBT DTRUs exceed that allowed by the License.
Handling Procedure
Y=> Go to step 2.
1-72 (2008-06-24)
N=> Go to step 3.
Y=> Go to step 4.
Step 4 Check whether the serving extension cells exceed the number allowed by the License.
Y=> Download additional License files to those extension cells, and then activate them.
----End
1.28 149 Transmit-Diversity DTRU Blocked Due to License

Description
This alarm is reported when the transmit-diversity DTRUs are blocked due to License.
Attribute
149 Minor Event
Parameters
ID Name Meaning
Impact on System
The redundant transmit-diversity DTRUs which are restricted by the License are blocked.
System Actions
None.
Possible Causes
l The number of serving transmit-diversity DTRUs exceed that allowed by the License.
Handling Procedure
Y=> Go to step 2.
(2008-06-24) 1-73

N=> Go to step 3.
Y=> Go to step 4.
Step 4 Check whether the serving transmit-diversity DTRUs exceed the number allowed by the License.
Y=> Download additional License files to those transmit-diversity DTRUs, and then activate
them.
----End
1.29 150 DTRU Blocked Due to License

Description
This alarm is reported when the double-TRX DTRUs are blocked due to License.
Attribute
150 Minor Event
Parameters
ID Name Meaning
Impact on System
The redundant double-TRX DTRUs which are restricted by the License are blocked.
System Actions
None.
Possible Causes
1-74 (2008-06-24)
l The number of serving double-TRX DTRUs exceed that allowed by the License.
Handling Procedure
Y=> Go to step 2.
N=> Go to step 3.

Y=> Go to step 4.
Step 4 Check whether the serving double-TRX DTRUs exceed the number allowed by the License.
Y=> Download additional License files to those double-TRX DTRUs, and then activate them.
----End
1.30 151 4-Way Diversity DTRU Blocked Due to License

Description
This alarm is reported when the 4-way diversity DTRUs are blocked due to License.
Attribute
151 Minor Event
Parameters
ID Name Meaning
Impact on System
The redundant 4-way diversity DTRUs which are restricted by the License are blocked.
System Actions
None.
(2008-06-24) 1-75
Possible Causes
l The number of serving 4-way diversity DTRUs exceed that allowed by the License.
Handling Procedure
Y=> Go to step 2.
N=> Go to step 3.
Y=> Go to step 4.
Step 4 Check whether the serving 4-Way Diversity DTRU exceed the number allowed by the License.
Y=> Download additional License files to those 4-way diversity DTRUs, and then activate them.
----End
1.31 152 High-Output-Power TRU Blocked Due to License

Description
This alarm is reported when the high output power TRUs are blocked due to License.
Attribute
152 Minor Event
Parameters
ID Name Meaning
1 DTRU index This parameter indicates the number of the TRU to be blocked.
Impact on System
The redundant high output power TRUs which are restricted by the License are blocked.
1-76 (2008-06-24)
System Actions
None.
Possible Causes
l The number of serving high output power TRUs exceed that allowed by the License.
Handling Procedure
Y=> Go to step 2.
N=> Go to step 3.

Y=> Go to step 4.
Step 4 Check whether the serving high output power TRUs exceed the number allowed by the License.
Y=> Download additional License files to those high output power TRUs, and then activate
them.
----End
1.32 153 Cell Broadcast Short Message Service Stopped Due

to License
Description
This alarm is reported when the short message broadcasting service of a cell is disabled by the
CBIP. CBIP disables the short message broadcasting service of the cells once the number of the
serving cells which support short message broadcasting exceed that allowed by the License.
Attribute

153 Minor Fault
(2008-06-24) 1-77
Parameters
ID Name Meaning
1 License permit cell No. This parameter indicates the number of the cell which is
permitted in license.
2 Config cell No. This parameter indicates the number of the cell whose CBCH
channel is enabled.
Impact on System
The short message broadcasting service of the redundant cells which are restricted by the License
are disabled.
System Actions
None.
Possible Causes
l The number of the serving cells which support short message broadcasting exceed that
allowed by the License.
Handling Procedure
Y=> Go to step 2.
N=> Go to step 3.

Y=> Go to step 4.
Step 4 Check whether the cells which use short message broadcasting service exceed the number
allowed by the License.
Y=> Download additional License files to those cells, and then activate them.
----End
1-78 (2008-06-24)
1.33 154 Resource Usage Threshold Exceeded for Over 60

Times
Description
This alarm is reported when the quantity of one resource being used exceeds the threshold defined
by the License in more than 60 times.
Attribute
154 Minor Event
Parameters
ID Name Meaning
1 Resource name l 4 = Number of sites that use satellite transmission mechanism
l 5 = Number of extension cells
l 6 = Number of TRXs that use PBT transmitting mechanism
l 7 = Number of TRXs that use transmitting diversity mechanism
l 8 = Number of double-TRX DTRUs
l 9 = Number of TRXs that use 4-way receiving diversity mechanism
l 10 = Number of high output power TRUs
Impact on System
The fluctuation of the quantity of this resource is forbidden by the License.
System Actions
The fluctuation of the quantity of this resource is forbidden by the License.
Possible Causes
The quantity of one resource being used exceeds the threshold defined by the License in more
than 60 times.
Handling Procedure
Check whether the quantity of the resource exceeds the quantity allowed by the License.
Y=> Download additional License files and activate them.
----End
(2008-06-24) 1-79
1.34 155 All Ater LapdLink Faulty

Description
This alarm is reported when all of the Ater Lapdlink are disrupted.
Attribute
155 Critical Fault
Impact on System
The BSC can not apply the resource for the services.
System Actions
None.
Possible Causes
l The E1 links on the Ater interface are fault
l The interface boards are running abnormally.
l The configuration of the internal signaling links are modified.
Handling Procedure
Check whether a correlated parent alarm is reported.
Y => Clear the parent alarm according to the corresponding handling suggestions. Check
whether the alarm is cleared.
N =>Please contact Motorola for technical support.
Correlated parent alarm
This alarm is reported when the parent alarm occurs on the ports for all the internal signaling
links.
links.
links.
links.
1-80 (2008-06-24)
links.
links.
links.
links.
----End
1.35 156 DSP Resource Lack

Description
This alarm is reported when the DSP resource is lack.
Attribute
156 Critical Fault
Parameters
ID Name Meaning
1 Subrack No. This parameter indicates the number of the subrack where the DPU
board is located.
2 Logical Slot No. This parameter indicates the number of the slot where the DPU board
is located.
Impact on System
The number of speech service subscribers supported by the BSC decreases.
System Actions
None.
Possible Causes
l The DPU board is fault.
l A few DSPs in the DPU board are fault.
(2008-06-24) 1-81
Handling Procedure
Please contact Motorola for technical support.
----End
1.36 157 License Inferior Limit

Description
This alarm is reported when the License file and the probational time are all expired.
Attribute

157 Major Fault
Impact on System
License Resourse reduced to minimization . The functions and resources of the BSC system are
restricted.
System Actions
The system uses the default values for the License control items. The functions controlled by
the License are unavailable and as a result the resources cannot be used.
Possible Causes
The License file expires.
Handling Procedure
N => Go to step 2.
Step 2 Please contact Motorola for technical support.
----End
1.37 158 License File Expired

Description
This alarm is reported when the License file is expired but the probational time is not expired.
1-82 (2008-06-24)
Attribute

158 Major Event
Impact on System
None.
System Actions
None.
Possible Causes
The License file expires.
Handling Procedure
N => Go to step 2.
----End
1.38 159 Lack TC Resource

Description
This alarm is generated when the TC resources are insufficient.
Attribute

159 Minor Event
Parameters
ID Name Meaning
1 Subrack No. This parameter indicates the number of the subrack where the GDPUC
\GDPUX board is located.
(2008-06-24) 1-83
Impact on System
No TC resources can be assigned; thus calls cannot be put through.
System Actions
None.
Possible Causes
l The GDPUC\GDPUX is not configured.
l The DSP usage of the GDPUC\GDPUX whose CPU usage is the lowest exceeds 95%.
Handling Procedure
Check whether the GDPUC\GDPUX is configured.
Y => Add a GDPUC\GDPUX.
N => Configure the GDPUC\GDPUX.
----End
1.39 160 HDLC Link Fault

Description
This alarm is reported in the following conditions:
l The state of the PEU changes, and the alarm is generated on all the HDLC links configured
on the PEU.
l The E1 port is faulty.
l The BTS reports the status change in the HDLC link.
Attribute

160 Minor Fault
Parameters
ID Name Meaning
1 HDLC No. This parameter indicates the HDLC No.
Impact on System
The channel resources on the HDLC link are unavailable.
1-84 (2008-06-24)
System Actions
None.
Possible Causes
l The interface board where the HDLC link is configured is faulty.
l The E1 port where the HDLC link is configured is faulty.
l The BTS reports that the HDLC link is faulty.
Handling Procedure
Step 1 Confirm the slot for the board where the HDLC link is configured.
Step 2 Check whether the board where the HDLC link is configured is faulty.
Y => Make the board run normally.
N => Go to step 3.
Step 3 Confirm the E1 port where the HDLC link is configured.
Step 4 Check whether the E1 port where the HDLC link is configured is faulty.
Y => Make the E1 port operational.
N => Go to step 5.
Step 5 Check whether the BTS reports that the HDLC link is faulty.
Y => Check whether the BTS reports the PTU-related alarm.
N => Go to step 6.
Step 6 Run the MML command to check whether the operating status of the HDLC link is faulty.
Y => Replace the E1 cable.
----End
1.40 161 HDLC Link Congestion

Description
This alarm is reported when the HDLC link is congested.
Attribute

161 Minor Fault
(2008-06-24) 1-85
Parameters
ID Name Meaning
1 HDLC No. The HDLC number identifies an HDLC link uniquely in a BSC.
2 Congestion Level The division of HDLC congestion levels is used to prevent the physical
links from being congested.Six congestion levels are defined:level 0
means non-congestion,and level 1 through level 5 mean
congested.The congestion severity increases from level 1 to level 5
while the remaining bandwidth of the HDLC link decreases from level
1 to level 5. That is, level 5 is the severest congestion of the HDLC
link. If the physical link is not congested, the congestion level can be
calculated from the parameter obtained from the following way: BSC
Attributes > IP Transfers > XLevel RemainWidthRatio (X can be one
through five). For example, if OneLevel RemainWidthRatio is set to
20, TwoLevel RemainWidthRatio is set to 30, and if the ratio of the
remaining bandwidth of one HDLC link to the configured bandwidth
is 21%, then the congestion level of the HDLC link is level 1. If the
physical link is congested, then the congestion level of the HDLC link
is level 5.
Impact on System
None.
System Actions
None.
Possible Causes
The consumed bandwidth of the HDLC link exceeds the upper threshold of the HDLC congestion
level.
Handling Procedure
Step 1 Increase the configured bandwidth of the HDLC link (the bandwidth cannot be adjusted
manually).
Step 2 The congestion alarm will be cleared automatically.
----End
1.41 201 Internal Flow Control Level Changed

Description
This alarm is reported when the system load is too heavy and then the system starts the flow
control.
1-86 (2008-06-24)
Attribute
201 Warning Event
Parameters
ID Name Meaning
1 Flow control level This parameter indicates the flow control level of the system currently
when an alarm is generated. There are 12 flow control levels, with 0
indicating the lowest level and 11 indicating the highest level.
2 Subrack No. This parameter indicates the number of the subrack where the
GXPUM board is faulty.
3 Logical slot No. This parameter indicates the number of the logical slot where the
GXPUM board is faulty The active GXPUM board and standby
GXPUM board are located in adjacent physical slots but share the
same logical slot number.
4 CPU No. This parameter indicates the number of the CPU where the GXPUM
board is faulty.
Impact on System
l When the alarm is generated, the services of some users may be temporarily interrupted.
At the same time, the BSC prohibits some functions.
l Flow control level 2 and above: The cell frequency scanning, common information printing,
common log recording, and call resource check functions are unavailable.
l Flow control level 4 and above: The forced handover function is unavailable.
l Flow control level 6 and above: The handover candidate query function is unavailable.
l Flow control level 8 and above: The channel assignment queuing, radio resource indication
handling (interference band), and call preemption functions are unavailable.
l Flow control level 10 and above: The conversion between traffic channels and the
conversion between traffic channel and signaling channel functions are unavailable.
System Actions
When the alarm is generated, the BSC discards the paging messages and the random access
request messages based on the corresponding probabilities of the flow control levels. If the flow
control level is high, the probability for discarding the messages is high. At the same time,
according to the different flow control levels, the BSC prohibits certain functions to decrease
the system load.
Possible Causes
l Multiple service requests are accessed at the same time.
(2008-06-24) 1-87
l The MSC or the SGSN sends multiple paging messages in a short time.
l Too many message services consume much CPU resource.
Handling Procedure
Step 1 Check whether there are multiple location updates.
Y => There are multiple location updates, go to step [3].
N => Go to step 2.
Step 2 Check whether the MSC or the SGSN sends multiple abnormal paging messages.
Y => Go to step 4.
N => Go to step 5.
Step 3 Block the cells where multiple location updates happen and check whether the alarm is cleared.
N => The alarm persists. Go to step 2.
Step 4 Process the MSC and SGSN problems.

Y => The alarm is cleared, the alarm handling is complete.
Step 5 Check the traffic measurement and alarms for other errors and solve them. If there is no
abnormity and the alarm persists, please contact Motorola for technical support.
----End
1.42 202 Internal Flow Control Released

Description
This alarm is reported when the system flow control ends, and system runs normally.
Attribute
202 Warning Event
Parameters
ID Name Meaning
1 Flow control level This parameter indicates that the flow control level of the system is 0
currently. There are 12 internal flow control levels, with 0 indicating
the lowest level and 11 indicating the highest level.
2 Subrack No This parameter indicates the number of the subrack where the
GXPUM board is faulty.
1-88 (2008-06-24)
ID Name Meaning
3 Logical slot No. This parameter indicates the number of the logical slot where the
GXPUM board is faulty. The active GXPUM board and standby
GXPUM board are located in adjacent physical slots but share the
same logical slot number.
board is faulty.
Impact on System
The system is recovered.
System Actions
The system is operational and the services are functional.
Possible Causes
l The BSC does not report many channel request messages any longer.
l The MSC or the SGSN does not send multiple paging messages at the same time.
l The system is recovered and the system load is within the normal range.
Handling Procedure
The system is recovered.
----End
1.43 203 PDCH Configured on Overlayer with an old version

PCU
Description
PCU is old version, and does not support the configuration of PDCH on Overlayer in a concentric
cell. Such configuration will effect the performance result of BSC and PCU
Attribute

203 Minor Event
(2008-06-24) 1-89
Parameters
ID Name Meaning
1 Cell ID The Global index value of a cell in a BSC
Impact on System
Such configuration will effect the performance result of BSC and PCU
System Actions
The system is operational, but the PDCH on Overlayer can not be used.
Possible Causes
PCU is old version, and PDCH is onfigured on Overlayer in a concentric cell.
Handling Procedure
Config the PDCH on Underlayer or update the PCU to a new version which supports v1.30 or
newer version PB interface protocol
----End
1.44 205 TC Fault Alarm

Description
This alarm is reported when the TC fault message is received. The cause is one-way audio, no
audio, uplink noise, or downlink noise or unlink and downlink noise.
Attribute

205 Warning Event
Parameters
ID Name Meaning
1 Cause This parameter indicates the cause of the TC fault.
2 Subrack No. This parameter indicates the number of the subrack where the DPU
board that reports the alarm is located.
1-90 (2008-06-24)
ID Name Meaning
3 Slot No. This parameter indicates the number of the slot where the DPU incurring
the alarm is located.
4 DSP No. This parameter indicates the number of the DSP that is occupied by the
call.
5 DSP Slot No. This parameter indicates the number of the DSP slot that is occupied by
the call.
6 Channel No. This parameter indicates the number of the channel that carries the call.
7 Cell ID This parameter indicates the ID of the cell that carries the call.
8 TRX Index This parameter indicates the index of the TRX that carries the call.
9 DPC Group No. DPC group number of the call
10 A Interface CIC This parameter indicates A interface CIC that is occupied by the call.
Impact on System
The one-way audio or no audio of TC (cause value 12/13/14) leads to no voice for a single user
during conversation.
System Actions
When the TC incurs one-way audio or no audio (cause value 12/13/14), the call persists after
the system reports an alarm.
Possible Causes
The reason why the TC incurs one-way audio or no audio (cause value 12/13/14) is that the links
on the downlink of the A interface or on the uplink of the Abis or Ater interface may be blocked.
Handling Procedure
If the TC one-way audio or no audio (cause value 12/13/14) occurs on the downlink, check the
connection of cables on the A interface and the configuration on the MSC. Then, implement a
loopback test on the A interface towards the BTS to check whether the links of the equipment
on the B side are normal. Sometimes, no voice can be heard through the outgoing premium rate
call. This type of downlink one way audio alarm must be shielded. If the TC one-way audio or
no audio (cause value 12/13/14) occurs on the uplink, check the connection of cables on the Ater
or Abis interface and query the single user resources. Then, implement the timeslot loopback
test on each EIU/OIU interface board towards the BTS based on the result so that you can confirm
the section where the fault occurs.
----End
(2008-06-24) 1-91
1.45 291 Cell Transmission Delay Abnormal

Description
This alarm is reported when the transmission delay between the BTS and the BSC is lower than
the lower limit or higher than the upper limit.
Attribute
291 Major Event
Parameters
ID Name Meaning
1 Cell Id This parameter indicates the cells with abnormal transmission delay.
2 Cause l Cause 0: The cell is a common cell, and the transmission delay is higher than
240ms;
l Cause 1: The cell is a satellite cell, and the transmission delay is lower than
240ms;
l Cause 2: The cell is a satellite cell, and the transmission delay is higher than
800ms;
l Cause 3: The cell is a satellite cell, and the transmission delay is higher than
1000ms.
Impact on System
l Cause 0: The cell is a common cell, and the transmission delay is higher than 240ms;
l Cause 1: The cell is a satellite cell, and the transmission delay is lower than 240ms;
l Cause 2: The cell is a satellite cell, and the transmission delay is higher than 800ms;
l Cause 3: The cell is a satellite cell, and the transmission delay is higher than 1000ms.
System Actions
None
Possible Causes
l Cause 0: The cell is a common cell, and the transmission delay is higher than the soft
parameter Delay Threshold of Common Cell;
l Cause 1: The cell is a satellite cell, and the transmission delay is lower than the soft
parameter Delay Threshold of Common Cell;
l Cause 2: The cell is a satellite cell, and the transmission delay is higher than the soft
parameter Delay Threshold 1 of Satellite Cell;
1-92 (2008-06-24)
l Cause 3: The cell is a satellite cell, and the transmission delay is higher than the soft
parameter Delay Threshold 2 of Satellite Cell.
Handling Procedure
Step 1 Cause 0: On the local maintenance terminal, check whether the type of the cell is common cell;
Y => Configure the cell type to satellite cell;
N=> Contact Motorola for technical support.
Step 2 Cause 2: On the local maintenance terminal, check whether the type of the cell is satellite cell;
Y => Configure the cell type to common cell;
N=> Contact Motorola for technical support.
Step 3 Cause 2: No operation needed. This alarm indicates that the current environment is bad and this
has impact on services;
Step 4 Cause 3: No operation needed. This alarm indicates that the current environment is very bad and
this has a great impact on services.
----End
1.46 293 GB BC Faulty

Description
This alarm is reported when the Gb interface is broken, the configuration of Gb interface is
faulty, or the BC is blocked. BC is a binding of E1's some slots for transferring service data and
signaling data
Attribute
293 Critical Fault
Parameters
ID Name Meaning
1 Subrack No. This parameter indicates the subrack No. of the GEPUG where the alarm
is generated.
2 Slot No. This parameter indicates the slot No. of the GEPUG where the alarm is
generated.
3 Port No. This parameter indicates the port No. of the GEPUG where the alarm is
generated.
4 BC No. This parameter indicates the ID of the BC where the alarm is generated.
(2008-06-24) 1-93
Impact on System
l If no backup BC is configured, then the data service in the related cells will be interrupted;
l If a backup BC is configured, then the data service in the related cells can be performed,
but the service capacity goes down.
System Actions
None
Possible Causes
l The Gb interface is broken;
l The configuration of the Gb interface is incorrect;
l The BC is blocked.
Handling Procedure
Step 1 Check whether the E1 cable between the BSC and the SGSN is correct;
Y => Go to step 2;
N => Connect BSC and SGSN again.
Step 2 On the local maintenance terminal of BSC and SGSN, separately run the MML command DSP
BC. Check whether the configurations include subrack No., slot No., port No., and BC ID of
BSC and SGSN are the same;
Y => Same, go to step [3];
N => Different, go to step [4];
Step 3 On the local maintenance terminal of BSC, run the MML command DSP BC. Check whether
the BC is blocked;
Y => Blocked, run the UBL BC to unblock the BC;
N => Unblocked, contact Motorola for technical support.
Step 4 On the local maintenance terminal of BSC, right-click the GEPUG that incurs an alarm and then
choose Configure BC. Reconfigure the BC of Gb interface, make sure that the timeslot of BSC
and SGSN is identical.
----End
1.47 294 TRX Config Error

Description
This alarm is reported when BSC has set BTS TRX to support EGPRS, but the BTS TRX does
not support EGPRS actually; or when BSC has set BTS TRX to support GPRS, but BTS TRX
does not support GPRS actually.
1-94 (2008-06-24)
Attribute

294 Major Event
Parameters
ID Name Meaning
1 TrxNo. This parameter indicates the number of the TRX where the alarm is generated.
Impact on System
The TRX cannot provide PS service.
System Actions
None
Possible Causes
l BSC has configured BTS TRX to support EGPRS, but exactly, BTS TRX does not support
EGPRS;
l BSC has configured BTS TRX to support GPRS, but exactly, BTS TRX does not support
GPRS.
Handling Procedure
Step 1 Check whether the Types of TRXs Supported by the BSC and the Software Version of BTS
TRX are consistent;
Y =>Please contact Motorola for technical support.
N => Go to step 2;
Step 2 Configure the Types of TRXs Supported by the BSC again or change the Software Version of
BTS TRX, make sure they are consistent.
----End
1.48 331 NSVC Faulty

Description
This alarm is reported when the GEPUG is faulty, NSVC is blocked, BC is faulty, or the
configuration data between BSC and SGSN is incorrect. The NSVC stands for the virtual
connection on the NS layer of Gb interface.
(2008-06-24) 1-95
Attribute
331 Major Fault
Parameters
ID Name Meaning
1 NSEI This parameter indicates the ID of the NSE where the alarm is generated.
2 NSVCI This parameter indicates the ID of the NSVC where the alarm is generated.
Impact on System
l If no backup NSVC is configured, then the data service in the related cells will be
interrupted;
l If a backup NSVC is configured, then the data service in the related cells can be performed,
System Actions
None
Possible Causes
l GEPUG is faulty;
l NSVC is blocked;
l The BC is blocked;
l The configuration of the BSC and SGSN is faulty.
Handling Procedure
Step 1 On the local maintenance terminal, check whether the GEPUG runs normally.
Y => Go to step 2;
N => Commission the GEPUG board.
Step 2 Run the MML command DSP NSVC, check whether the NSVC is blocked;
Y => Run the MML command UBL BC to unblock the NSVC.
N => Go to step 3;
Step 3 Run the MML command DSP BC, check whether the BC service state is available;
Y => Go to step 4;
N => Commission the BC service state.
NSVC. Check whether the NSE and NSVC configuration of BSC and SGSN are consistent;
Y => Go to step 5;
1-96 (2008-06-24)
N => Configure the NSE of BSC and the NSVC of BSC again, make sure that they are consistent
with that of SGSN.
Step 5 Run the MML command DSP BC and DSP PVC. Check whether the statistics data of BC and
PVC is normal;
Y => The alarm handling is complete, and the alarm is cleared.
----End
1.49 332 NSVL Faulty

Description
This alarm is reported when the GFGUG is faulty, the communication between BSC and SGSN
is interrupted, or the configuration data of BSC and SGSN is incorrect. The NSVL stands for
the virtual link on the IP NS layer of Gb interface.
Attribute
332 Major Fault
Parameters
ID Name Meaning
2 NSVLI This parameter indicates the ID of the NSVL where the alarm is generated.
Impact on System
l If no backup NSVL is configured, then the data service in the related cells will be
interrupted;
l If a backup NSVL is configured, then the data service in the related cells can be performed,
System Actions
None
Possible Causes
l GFGUG is faulty;
l The communication between BSC and SGSN is interrupted;
l The configuration of the BSC and SGSN is faulty.
(2008-06-24) 1-97
Handling Procedure
Step 1 On the local maintenance terminal, check whether the GFGUG runs normally;
Y => Go to step 2;
N => Commission the GFGUG board.
Step 2 Check whether the IP connection between the IP-Interface-Boards of BSC and the SGSN is
normal;
Y => Go to step 3;
NSVL. Check whether the NSE and NSVL configuration of BSC and SGSN are consistent;
Y => The alarm is cleared.
N => Configure the NSE and NSVL of the BSC again, make sure that they are consistent with
that of SGSN.
----End
1.50 333 NSE Faulty

Description
The alarm is reported when the Gb interface is abnormal.NSE is the management entity on the
NS layer.
Attribute

333 Critical Fault
Parameters
ID Name Meaning
Impact on System
l If the Gb Flex feature is not enabled, all cells of this NSE cannot support packet service;
l If the Gb Flex feature is enabled, the cells of the PTP BVC cannot access the corresponding
SGSN of the NSE.
System Actions
None
1-98 (2008-06-24)
Possible Causes
The Gb interface is abnormal.
Handling Procedure
Step 1 Run the MML command DSP BC, check whether the BC service state is available;
Y => Go to step 2;
N => Reconfigure the BC service state to be available.
Step 2 Run the MML command DSP NSVC, check whether the NSVC is in the activation unblocked
state;
Y => Go to step 3;
N => Reconfigure the NSVC service state to be available.
BC. Check whether the BC ID of BSC and SGSN are consistent;
Y => Go to step 4;
N => On the local maintenance terminal of BSC, reconfigure the BC to be the same with the
BC ID of SGSN.
NSVC. Check whether the NSE and NSVC of the BSC and SGSN are consistent;
N => On the local maintenance terminal of BSC, reconfigure the NSVC to be the same with the
NSE and NSVC of SGSN.
----End
1.51 340 Cell PS Service Faulty

Description
This alarm is reported when cell distribution is failure, the cell is forbidden due to no license,
the Um interface is blocked, or the Gb interface is blocked.
Attribute

340 Critical Fault
Parameters
ID Name Meaning
1 Cell ID This parameter indicates the ID of the cell where the alarm is generated.
(2008-06-24) 1-99
ID Name Meaning
2 Cause l 0-Cell distribution failure
l 1-The cell is forbidden due to no license
l 2-The Um interface is blocked
l 3-The Gb interface is blocked
Impact on System
The cell cannot provide PS service.
System Actions
None
Possible Causes
l Cause 0: Cell distribution failure;
l Cause 1: The cell is forbidden due to no license;
l Cause 2: The Um interface is blocked;
l Cause 3: The Gb interface is blocked.
Handling Procedure
Step 1 Cause 0: Adds GDPUP to add the number of packet DSP available;
Step 2 Cause 1: Please contact Motorola for technical support for a License supports this feature.
Step 3 Cause 2: Run the MML command DSP PSCELL, check whether the cell Um administration
state is blocked;
Y => Adjust the BTS to unblock the Um interface;
N => The alarm is cleared.
Step 4 Cause 3: When the Gb interface board is the GEPUG, check whether the 1.48 331 NSVC
Faulty is generated;
Y => Refer to the handling suggestion to the 1.48 331 NSVC Faulty.
N => Go to step 5;
Step 5 When the Gb interface board is the GFGUG, check whether the 1.49 332 NSVL Faulty is
generated;
Y => Refer to the handling suggestion to the 1.49 332 NSVL Faulty.
N => Go to step 6;
Step 6 Check whether the 1.50 333 NSE Faulty is generated;
Y => Refer to the handling suggestion to the 1.50 333 NSE Faulty.
N => Go to step 7;
Step 7 Check whether the 1.53 342 PTP BVC Faulty alarm is generated;
Y => Refer to the handling suggestion to the 1.53 342 PTP BVC Faulty.
1-100 (2008-06-24)
N => Go to step 8;
Step 8 Run the MML command DSP PSCELL, check whether the cell Gb administration state is
blocked;
Y => Go to step 9;
Step 9 Check the connection of the E1 cables;
N => Replace the E1 cable.
----End
1.52 341 DSP Resource Overload

Description
This alarm is reported when the number of distributed cells on a DSP exceeds the upper limit.
Attribute
341 Critical Fault
Parameters
ID Name Meaning
1 Subrack No. This parameter indicates the number of the subrack where the alarm is
generated.
2 Slot No. This parameter indicates the number of the slot where the alarm is
generated.
3 Dsp No. This parameter indicates the number of the DSP where the alarm is
generated.
Impact on System
The packet service performance of the cells on the DSP deteriorates.
System Actions
None
Possible Causes
The number of distributed cells on a DSP exceeds the upper limit.
(2008-06-24) 1-101
Handling Procedure
Step 1 Check whether the 1.262 21201 DSP Heartbeat Lost alarm is generated, and check whether
there is any DSP fault;
Y => Refer to the handling suggestion to the 1.262 21201 DSP Heartbeat Lost.
N => Go to step 2;
Step 2 Run the MML command DSP PSRES, and obtain the resource status of each DSP;
Step 3 Run the MML command SET PSCELLTODSP, and make the cells distributed on the idle DSP
manually;
Step 4 Please consider system capacity expansion.
----End
1.53 342 PTP BVC Faulty

Description
This alarm is reported when the PTP BVC protocol procedure is abnormal, or the PTP BVC is
blocked.
Attribute
342 Major Fault
Parameters
ID Name Meaning
2 BVCI This parameter indicates the ID of the BVC where the alarm is generated.
Impact on System
This PTP BVC cannot carry services.
System Actions
S
Possible Causes
l The PTP BVC protocol procedure is abnormal;
l PTP BVC is blocked.
1-102 (2008-06-24)
Handling Procedure
Step 1 Check whether the 1.46 293 GB BC Faulty is generated;
Y => Refer to the handling suggestion to the 1.46 293 GB BC Faulty.
N => Go to step 2;
Step 2 When the Gb interface board is the GEPUG, check whether the 1.48 331 NSVC Faulty is
generated;
Y => Refer to the handling suggestion to the 1.48 331 NSVC Faulty.
N => Go to step 3;
Step 3 When the Gb interface board is the GFGUG, check whether the 1.49 332 NSVL Faulty is
generated;
Y => Refer to the handling suggestion to the 1.49 332 NSVL Faulty.
N => Go to step 4;
Step 4 Check whether the 1.50 333 NSE Faulty is generated;
Y => Refer to the handling suggestion to the 1.50 333 NSE Faulty.
N => Go to step 5;
Step 5 Run the MML command DSP PTPBVC, check whether the PTPBVC is blocked;
Y => Go to step 6;
N => Go to step 7;
Step 6 Run the MML command UBL PTPBVC, unblock the PTPBVC, then the alarm is cleared.
Step 7 On the LMT, trace the SIG BVC on the Gb Interface;
Step 8 Run the MML command RST PTPBVC to reset the PTP BVC, and locate the fault by the traced
message of the Gb interface.
----End
1.54 343 NSVL Dynamic Configuration Process Failure

Description
This alarm is reported when the communication link between the BSC and SGSN is faulty, or
the configuration of SERVER IP/UDP interface between the BSC and SGSN is incorrect.
Attribute
343 Critical Fault
(2008-06-24) 1-103
Parameters
ID Name Meaning
1 NSEI This parameter indicates the ID of the NSE where the alarm is generated
2 Cause l 0 - Local
l 1 - Remote
Impact on System
All the PTP BVC in this NSE cannot carry services.
System Actions
None
Possible Causes
l The communication link between the BSC and SGSN is faulty;
l The configuration of SERVER IP/UDP interface between the BSC and SGSN is incorrect.
Handling Procedure
Step 1 Check whether the IP connection between the IP-Interface-Boards of BSC and the SGSN is
normal;
Y => Go to step 2;
Step 2 Check whether the server IP address of BSC and SGSN are consistent;
Y => Go to step 3;
N => Reconfigure the server IP address of BSC.
Step 3 Check whether the server IP address of BSC and SGSN are consistent;
N => Reconfigure the server UDP port number of BSC.
----End
1.55 344 FAULTY DSP OVER LIMIT

Description
This alarm is reported when 16 or more DSP units in the GDPUP are faulty.
1-104 (2008-06-24)
Attribute

344 Critical Fault
Parameters
ID Name Meaning
1 Subrack No. This parameter indicates the subrack No. of the GDPUP where the alarm is
generated.
2 Slot No. This parameter indicates the slot No. of the GDPUP where the alarm is
generated.
3 DSP No. This parameter indicates the number of faulty DPS units on one GDPUP.
Impact on System
l The faulty DSP cannot process services.
l The system performance deteriorates.
System Actions
If the GDPUP is not faulty, the DSPs are automatically reset.
Possible Causes
l Loading of DSP software fails;
l Configuration of the DSP unit fails;
l The DSP unit fails to process services;
l The DSP unit examined is faulty.
Handling Procedure
Step 1 Check whether the DSP units are faulty. Calculate the number of faulty DSP units and check
whether the number exceeds the upper limit.
Y => Go to step 2.
Step 2 Wait for at least three minutes. Then, check whether the DSP units are faulty.
Y => Restart the GDPUP. The alarm is cleared.
----End
(2008-06-24) 1-105
1.56 401 BCCH Mutual Aid in a Cell

Description
This alarm is reported when the primary BCCH is switched to another TRX because the TRX
carrying the primary BCCH is faulty. The BCCH mutual aid ensures that the disrupted services
in a cell are restored within a short period of time.
Attribute
401 Major Event
Parameters
ID Name Meaning
1 Cell Index. This parameter indicates the index of the cell where BCCH mutual aid occurs.
Impact on System
When the cell is re-initialized, the traffic over the cell resume normal operation after being
disrupted for no more than 10 seconds.
System Actions
l When this alarm is reported, the system detects available TRXs in this cell and selects one
as the new primary BCCH TRX. The system assigns the primary BCCH to this TRX and
reinitializes the cell. A switchback occurs under the following situations:
l The former TRX carrying the primary BCCH is restored.
l The management status of the primary BCCH is Unblocked.
l TRX Aiding Function Control is set to Allowed Recover Immediately.
Possible Causes
l The TRX carrying the primary BCCH is unblocked manually.
l The primary BCCH is unblocked manually.
l The TRX carrying the primary BCCH is faulty because of a hardware failure of the primary
BCCH TRX.
Handling Procedure
Step 1 Check whether the primary BCCH is idle after the BCCH mutual aid.
Y=> The primary BCCH is idle. The BCCH mutual aid is successful. Go to step 2;
N=> The Primary BCCH is not idle. The BCCH mutual aid fails. Another BCCH mutual aid
occurs. If no other available TRX exists, contact Motorola to replace the faulty TRX.
1-106 (2008-06-24)
Step 2 Check whether the original primary BCCH is idle.

Y=> The primary BCCH is idle. Go to step 3;
N=> The primary BCCH is not idle. Go to step 4.
Step 3 Check the original primary BCCH TRX for alarms.

Y=> The alarm is generated. Go to step 5;
N=> The alarm is not generated. Go to step 4.
Step 4 View the status of the TRXs or channels, and check whether the BCCH mutual aid is caused by
the manual blocking of the BCCH TRX.
Y=> The BCCH mutual aid is caused by the manual blocking of the BCCH TRX. The alarm
handling is complete;
N=> The BCCH mutual aid is not caused by the manual blocking of the BCCH TRX. Contact
Motorola for technical support.
Step 5 Analysis of the alarm handling.

If the BCCH mutual aid occurs because of hardware failure, replace the faulty TRX;
If the TRX board is not securely inserted or the connection between the power cables of the TRX
and the cabinet is improper, the communication between the TMU and TRX is abnormal. Power
on the TRX again.
----End
1.57 402 Switchback after BCCH Mutual Aid in a Cell

Description
This alarm is reported in following conditions:
l The BCCH is switched back to the initial TRX under the following conditions: the BSC
detects that the initial TRX that carries the BCCH resumes to normal operation, and the
management status of the main BCCH is Unlocked, and the switchback is allowed in the
cell
l A forced switchback occurs due to data configuration.
Attribute

402 Major Event
Parameters
ID Name Meaning
1 Cell Index. This parameter indicates the index of the cell where the main BCCH is
switched between two TRXs.
(2008-06-24) 1-107
ID Name Meaning
2 Cause value l 0=A BTS is level-4 reset
l 1=A cell is level-4 reset
l 2=Current TRX that carries the main BCCH is deleted
l 3=Initial TRX that carries the main BCCH resumes to normal operation
l 4=Current TRX does not meet the requirement from the cavity
l 5=Checking of the resources are inconsistent
l 6=Location of the main BCCH is modified
l 7=Priority of the current main BCCH is modified
Impact on System
The cell is re-initialized. The BCCH is switched back to the initial TRX. The services provided
by this cell are interrupted and then restored within 10 seconds.
System Actions
l When the initial TRX that carries the main BCCH resumes to normal operation and the
management status of the main BCCH is Unblocked, a switchback occurs if the cell allows
switchback. The alarm is then reported and the cell is re-initialized.
l If the switchback occurs due to data configuration, the alarm is reported and the cell is re-
initialized.
Possible Causes
l The faults of the former TRX which carries the BCCH are rectified.
l The BCCH TRX is manually unblocked. The BCCH is switched back to the initial TRX.
l The BCCH is manually unblocked. The BCCH is switched back to the initial TRX.
l The switchback occurs due to data configuration.
Handling Procedure
Step 1 Check whether the forced switchback is caused by data configuration.
Y=> No handling is required.
N=> Go to step 2.
Step 2 Check whether the switchback is caused by manual troubleshooting.
Y=> Go to step 4.
N=> This indicates that the initial TRX is unstable or has transient faults. Go to step 3.
Step 3 Check whether the primary BCCH is idle after the BCCH mutual aid.
Y=> The primary BCCH is idle. Go to step 4.
N=> The primary BCCH is not idle. The switchover of the main BCCH fails. Please contact
Motorola to replace the faulty TRX.
Step 4 Wait for 15 minutes and then launch the LMT. Check whether the alarm 1.56 401 BCCH Mutual
Aid in a Cell occurs.
1-108 (2008-06-24)
Y=> The alarm 1.56 401 BCCH Mutual Aid in a Cell occurs. Clear alarm 1.56 401 BCCH
Mutual Aid in a Cell according to its relevant handling suggestions. In addition, the occurrence
of the mutual aid and switchback shows that the BCCH-carried TRX is unstable. Please contact
Motorola for technical support and replace the faulty TRX.
N=> The alarm 1.56 401 BCCH Mutual Aid in a Cell does not occur. Go to step5.
Step 5 Check whether the switchback of the BCCH is caused by manual operation.
Y=> The BCCH is switched back to the initial TRX intentionally. The alarm handling is
complete.
N=> Please contact Motorola for technical support and replace the faulty TRX.
----End
1.58 403 Baseband FH Mutual Aid in a Cell

Description
This alarm is reported when the baseband frequency hopping (FH) function of a cell is disabled
because the TRX that participates in baseband FH is faulty.
Attribute
403 Major Event
Parameters
ID Name Meaning
1 Cell Index. This parameter indicates the index of the cell where baseband FH mutual aid
occurs.
Impact on System
The services provided by the cell are disrupted temporarily. After the mutual aid, FH is not
allowed in the cell and the services are restored.
System Actions
After the alarm is reported, FH is not allowed in the cell and the cell is initialized.
Possible Causes
l The baseband FH function of the cell is disabled because the TRX that participates in
baseband FH is faulty.
l The TRX carrying the primary BCCH is faulty. The BCCH mutual aid occurs.
l The TRX that participates in baseband FH is blocked manually.
(2008-06-24) 1-109
Handling Procedure
Step 1 In the alarm system of BSC6000 LMT, check whether the alarm 1.56 401 BCCH Mutual Aid
in a Cell in a Cell is reported a few seconds before this alarm is reported.
Y => The baseband FH mutual aid is caused by the BCCH TRX mutual aid, that is, the BCCH
is aided to the TRX that participates in baseband FH. Refer to the handling suggestions of 1.56
401 BCCH Mutual Aid in a Cell. The alarm handling is complete.
N => The TRX that participates in baseband FH is faulty. Go to step2.
Step 2 Check whether all the TRXs listed in Parameters after the mutual aid are normal.
Y => Go to step 3.
N => Please contact Motorola for technical support to Replace the faulty TRX.
Step 3 Check whether the mutual aid is caused by the manual blocking of the TRXs participating in
baseband FH.
----End
1.59 404 Switchback after Baseband FH Mutual Aid in a Cell

Description
This alarm is reported when all the faulty TRXs that participate in baseband frequency hopping
(FH) are restored in a cell. The baseband FH function of this cell is also restored.
Attribute
404 Major Event
Parameters
ID Name Meaning
1 Cell Index. This parameter indicates the index of the cell where the switchback occurs.
Impact on System
The services provided by the cell are disrupted. After the switchover, the baseband FH function
and the services are restored.
System Actions
After the alarm is reported, the baseband FH function of the cell is restored and the cell is
initialized.
1-110 (2008-06-24)
Possible Causes
l The faults of the TRXs that participate in baseband FH are rectified. The baseband FH
function of the cell is restored.
l The faults of the TRX carrying the BCCH are rectified. A switchover after the BCCH
mutual aid occurs.
l The TRXs that participate in baseband FH are manually unblocked.
Handling Procedure
Step 1 In the alarm system of BSC6000 LMT, check whether the alarm 402 Switchback after BCCH
Mutual Aid in a Cell is reported before this alarm is reported.
Y => The alarm is caused by the switchover after the BCCH mutual aid. Refer to the handling
suggestions of 1.57 402 Switchback after BCCH Mutual Aid in a Cell.
N => The faults of the TRXs that participate in baseband FH are rectified. All the TRXs that
participate in baseband FH are functional. Go to 2.
Step 2 On the BSC6000 LMT, check whether the FH attribute of the cell is baseband FH and the status
of each TRX is normal.
Y => The switchback succeeds. The alarm handling is complete.
N => The switchback fails. Go to 3.
Step 3 Wait for 15 minutes. In the alarm system of the BSC6000 LMT, check whether the alarm 1.58
403 Baseband FH Mutual Aid in a Cell is reported.
Y => Refer to the handling suggestions of1.58 403 Baseband FH Mutual Aid in a Cell. The
mutual aid and the switchback show that the performance of TRXs are unstable. Please contact
Motorola for technical support to Replace the faulty TRX.
N => Please contact Motorola for technical support to Replace the faulty TRX.
----End
1.60 405 Cell Out of Service

Description
This alarm is reported when a cell is out of service because the TRX carrying the primary BCCH
is faulty.
Attribute
405 Major Fault
Parameters
ID Name Meaning
1 Site No. This parameter indicates the number of the site that is out of service.
(2008-06-24) 1-111
ID Name Meaning
2 Cell Index. This parameter indicates the index of the cell that is out of service.
3 Site type This parameter indicates the HorizenMacro, HorizenMacro2, Horizen2Mini,

or Horizen2Micro.
4 Site name This parameter indicates the name of site in that out of service happened.
5 Cell name This parameter indicates the name of cell in that out of service happened.
Impact on System
The services provided by the cell are disrupted.
System Actions
When the alarm is reported, the BCCH mutual aid is initiated to restore the services if the cell
allows the BCCH mutual aid. If the cell does not allow the BCCH mutual aid, the disruption
persists.
Possible Causes
The TRX carrying the BCCH is faulty.
Handling Procedure
Step 1 Check whether the primary BCCH is faulty.
Y => The alarm is caused by the primary BCCH failure. Wait for three minutes, and then go to
step 2.
N => The primary BCCH is blocked. Unblock it on the LMT. The alarm handling is complete.
Step 2 Check whether the TRX mutual aid occurs.

Y => Go to step 3.
N => Go to step 4.
Step 3 Check whether the primary BCCH is normal after the mutual aid.
Y => Replace the former TRX carrying the primary BCCH. The alarm handling is complete.
N => Please contact Motorola to Replace the faulty TRX.
Step 4 Check whether the TMU is normal.

Y => Go to step 5.
N => Please contact Motorola for technical support toReplace the faulty TMU.
Step 5 Check whether the communication between the BTS and the BSC is normal.
Y => Please contact Motorola to Replace the faulty TRX.
N => Handle the communication fault.
----End
1-112 (2008-06-24)
1.61 407 BTS Initialization

Description
This alarm is reported when a BTS is reset and re-initialized.
Attribute
407 Minor Event
Parameters
ID Name Meaning
1 Site No. This parameter indicates the number of the initialized site.
2 Cause value l 0=BTS is reset manually

l 1=BSC resets the BTS
l 2=BTS is reset automatically
l 3=BTS is reset due to other causes
Impact on System
All the services related to a BTS are disrupted when the BTS is reset.
System Actions
None.
Possible Causes
l The BTS is reset manually. Cause value: 0.
l The BTS is reset by the BSC. Cause value: 1.
l The BTS is reset automatically. Cause value: 2.
l The BTS is reset due to other causes. Cause value: 3.
Handling Procedure
Step 1 No handling is required if the BTS is reset manually.
Step 2 If the BTS is reset by the BSC, check whether the data associated with the BTS is correct on the
BSC.
N => On the BSC6000 LMT, modify the data.
(2008-06-24) 1-113
Step 3 If the BTS is reset automatically, check whether the power supply for the BTS is stable.
N => Replace the board related to the power supply.
----End
1.62 408 Automatic Activation of BTS TMU Version

Description
This alarm is reported when the BSC activates the TMU version of a BTS automatically.
Attribute
408 Minor Event
Parameters
ID Name Meaning
1 Site No. This parameter indicates the number of the site where the TMU version is
activated automatically.
2 Cause l 0=TMU version number saved during data configuration is null

l 1=Querying the current version number of the BTS failed
l 2=Querying all the version numbers in the BTS flash failed
l 3=There is no TMU version number saved during data configuration in
the BTS flash
l 4=Activating the TMU version failed
l 5=Activating the TMU version succeeded
3 NACK cause l 14= Parameter value limit exceeded

l 38= Target file does not exist
l 39= File cannot be activated
l 145= No management rights
Impact on System
l Succeeded: The configured TMU version is activated and the BTS is initialized. The
services associated with the BTS are disrupted temporarily.
l Failed: The configured TMU version is not activated.
System Actions
None.
1-114 (2008-06-24)
Possible Causes
l The TMU version number saved during data configuration is null. Cause value: 0
l Querying the current version number of the BTS failed. Cause value: 1
l Querying all the version numbers in the flash failed. Cause value: 2
l There is no TMU version number saved during data configuration in the flash. Cause value:
3
l Activating the TMU version failed. Cause value: 4
l Activating the TMU version succeeded. Cause value: 5
Handling Procedure
Step 1 If the cause value is 0, check whether the configuration of the TMU version is correct.
N => Reconfigure the data.
Step 2 If the cause value is 1, Check whether the OML is normal.

N => Reconnect the E1 on the Abis interface. If the alarm is cleared, the alarm handling is
complete. If the alarm persists, Please contact Motorola for technical support.
Step 3 If the cause value is 2,Check whether the OML is normal.

Step 4 If the cause value is 3, Check whether the correct TMU version is loaded into the BTS flash.
N => Load the correct TMU version.
Step 5 If the cause value is 4,Check whether the OML is normal.

Step 6 If the cause value is 5, activating the TMU version succeeded. No alarm handling is required.
----End
1.63 409 Cell BCCH Aiding to IUO_INN TRX

Description
The alarm is reported when the TRX where the active BCCH is located is abnormal.The TRX
of BCCH is faulty. The BCCH on this TRX is switched to IUO_INN TRX.
(2008-06-24) 1-115
Attribute
409 Major Event
Parameters
ID Name Meaning
1 Cell Index. This parameter indicates the cell index that aids to the IUO_INN TRX.
Impact on System
The coverage range of the cell signals may be reduced.
System Actions
The system automatically detects the cell for other available TRX, allocates the active BCCH
to the IUO_INN TRX and initialize the cell again. If the original active BCCH is recovered, the
active BCCH is in unblocked state, and TRX Aiding Function Control is set to Allowed Recover
Immediately, the cell BCCH aiding to IUO_INN TRX happen.
Possible Causes
l The active BCCH frequency is blocked manually.
l The active BCCH channel is blocked manually.
l The hardware fault of the active BCCH frequency destroys the frequency where the active
BCCH is located.
Handling Procedure
Step 1 Check whether the primary BCCH is idle .
Y => The BCCH mutual aid succeeds. Go to step 2.
N => The BCCH mutual aid fails. The BCCH TRX mutual aid occurs again. If there are no
TRXs available, Replace the faulty TRX.
Step 2 Check whether the primary BCCH is idle before the BCCH mutual aid occurs.
Y => Go to step 3.
N => Go to step 4.
Step 3 Check whether the former TRX carrying the primary BCCH has alarms.
Y => Go to step 5.
N => Go to step 4.
Step 4 Check whether the BCCH mutual aid is initiated by the manual blocking of the primary BCCH
TRX.
1-116 (2008-06-24)
Step 5 Analyze the alarm.

(1) The primary BCCH mutual aid is caused by the hardware failure of TRXs. Replace the
faulty TRX.
(2) The communication between the TMU and the TRX is disrupted because the TRX board
or the TRX power plug is loosely inserted. Power on the TRX again.
----End
1.64 410 BTS's capabilty doesn't account with the config data
Description
This alarm is reported when BTS doesn't support FlexAbis actually, but the config data show
the BTS has the capability of FlexAbis.
Attribute
410 Major Fault
Parameters
ID Name Meaning
1 Site No. This parameter indicates the site No. that capability doesn't account with the
config data.
Impact on System
BTS's initialization fail
System Actions
BTS will stop the initialization when alarm occurred
Possible Causes
BTS doesn't support FlexAbis actually, but the config data show the BTS has the capability of
FlexAbis.
Handling Procedure
Fix the config data, make it account with the BTS capability; Or update the BTS software, make
it support FlexAbis.
----End
(2008-06-24) 1-117
1.65 411 Site Reset for DynCfg

Description
This alarm is reported when the site which reset because of dynamic config goes back to normal
in the time of site reset delay time.
Attribute

411 Minor Event
Parameters
ID Name Meaning
1 Site No. This parameter indicates the number of the site delayed alarm.
Impact on System
The link disconnection alarm is shielded.
System Actions
None.
Possible Causes
The site is reset because of dynamic configurations and the site is restored to normal within the
delay time of the recovery alarm.
Handling Procedure
None.
----End
1.66 412 Manually Obturate Cell

Description
This alarm is reported when a cell is manually obturated.
1-118 (2008-06-24)
Attribute

412 Minor Event
Parameters
ID Name Meaning
1 Site No. This parameter indicates the number of the site whose cell is obturated.
2 Cell Index. This parameter indicates the number of the cell which is obturated.
3 Block type l 0 = LOCK

l 2 = SHUTDOWN
Impact on System
The cell is unavailable.
System Actions
None.
Possible Causes
The cell is manually blocked.
Handling Procedure
None.
----End
1.67 413 Manually Obturate Trx

Description
This alarm is reported when a trx is manually obturated.
Attribute

413 Minor Event
(2008-06-24) 1-119
Parameters
ID Name Meaning
1 Site No. This parameter indicates the number of the site whose trx is obturated.
2 Cell Index. This parameter indicates the number of the cell whose trx is obturated.
3 TRX No. This parameter indicates the number of the trx which is obturated.
4 Object type l 0 = Site

l 1 = Cell
l 3 = Channel
l 4 = Trx

l 2 = SHUTDOWN
Impact on System
The TRX is unavailable.
System Actions
None.
Possible Causes
The TRX is manually blocked.
Handling Procedure
None.
----End
1.68 414 Manually Obturate Channel

Description
This alarm is reported when a channel is manually obturated.
Attribute
414 Minor Event
1-120 (2008-06-24)
Parameters
ID Name Meaning
1 Site No. This parameter indicates the number of the site whose channel is
obturated.
2 Cell Index. This parameter indicates the number of the cell whose channel is
obturated.
3 TRX number This parameter indicates the number of the trx whose channel is
obturated.
4 Channel number This parameter indicates the number of the channel which is obturated.

l 2 = SHUTDOWN
Impact on System
The channel is unavailable.
System Actions
None.
Possible Causes
The channel is manually blocked.
Handling Procedure
None.
----End
1.69 416 SitePowerOff

Description
This alarm is reported when BTS lose it's power.
Attribute
416 Major Event
(2008-06-24) 1-121
Parameters
ID Name Meaning
1 Site No. This parameter indicates the number of the site which has lost power.
Impact on System
The services of the current site are disrupted.
System Actions
None.
Possible Causes
The BTS lose it's power.
Handling Procedure
None.
----End
1.70 417 BTS Loop Rotate

Description
This alarm is reported when BTS has rotated.
Attribute
417 Major Event
Parameters
ID Name Meaning
1 Site No. This parameter indicates the number of the site which has rotated.
Impact on System
l For ring network I, the BTS is reset and all services of the BTS are interrupted; for ring
network II, the BTS reestablishes a link, which takes a maximum of eight seconds.
l After the BTS is reset, some TCHs may become unavailable because they are not assigned
the anticlockwise time slots.
1-122 (2008-06-24)
System Actions
When the alarm is generated, the BTS is switched over to the reverse direction.
Possible Causes
l The link on the forward ring port connecting the BTS in ring topology mode (including the
upper-level BTSs) is faulty.
l Manually rotate the ring network on the maintenance system.
Handling Procedure
Step 1 Check whether the switchover of the BTS ring topology is caused by manual operation.
Y => The BTS ring topology is switched over intentionally. The switchover of BTS ring topology
succeeds. The alarm handling is complete;
N => Go to step 2.
Step 2 Check whether the forward ring port residing link of the BTS (including the upper-level BTSs)
is faulty.
Y => Handle and eliminate line failure, and then manually switch over the BTS on the
maintenance system (menu: BTS Maintenance > Maintain Site > Maintain Ring Network). The
BTS is switched over to the forward direction;
----End
1.71 418 BTS Loop Rotateback

Description
This alarm is reported when BTS has rotated back.
Attribute
418 Major Event
Parameters
ID Name Meaning
1 Site No. This parameter indicates the number of the site which has rotated back.
Impact on System
For ring network I, the BTS is reset and all services of the BTS are interrupted; for ring network
II, the BTS reestablishes a link, which takes a maximum of eight seconds.
(2008-06-24) 1-123
System Actions
When the alarm is generated, the BTS is switched over to the forward direction.
Possible Causes
l The link on the reverse ring port connecting the BTS in ring topology mode (including the
BTSs of the upper-level in the reverse direction) is faulty.
l Manually rotate the ring network on the maintenance system.
Handling Procedure
Step 1 Check whether the switchover of the BTS ring topology is caused by manual operation.
Y => The BTS ring topology is switched over intentionally. The switchover of the BTS ring
topology succeeds. The alarm handling is complete;
N => Go to step 2.
Step 2 Check whether the reverse ring port residing line of the BTS (including the BTSs of the upper-
level in the reverse direction) is faulty.
Y => Rectify the fault in the transmission line;
----End
1.72 419 Query IP of PTU by Its electric label failed because

of configration error
Description
This alarm is reported when the querying of the IP address of the configured active and standby
PTUs based on the electronic label of PTU reported by the BTS fails.
Attribute
419 Critical Event
Parameters
ID Name Meaning
1 Electric Label This parameter indicates the electric label or the PTU.
Impact on System
The BTS that supports IP transmission cannot obtain the IP address. Therefore, the BTS does
not work, and all the services of the BTS are disrupted.
1-124 (2008-06-24)
System Actions
None
Possible Causes
The electronic label of the active and standby PTUs configured on the LMT is different from
the electronic label of the active and standby PTUs in the BTS.
Handling Procedure
Step 1 Check whether the electronic label of the PTU indicated by the alarm is consistent with the
electronic label of the PTU before delivery.
Y => Go to step 2;
N => Go to step 4.
Step 2 Check whether the electronic label of the PTU in the BTS is consistent with the electronic label
of the PTU before delivery.
Y => Go to step 5;
N => Go to step 3.
Step 3 Reconfigure the electronic label of the PTU in the BTS on the basis of the electronic label of
the PTU before delivery. Then, check whether the BTS is operational.
Y => If the alarm is caused by the incorrect configuration of the electronic label, the alarm
handling is complete;
N => Go to step 5.
Step 4 If the electronic label of PTU is faulty, please contact Motorola for technical support.
Step 5 If the PTU is faulty, Please contact Motorola for technical support.
----End
1.73 420 BTS doesn't support config the card and the logic
object separately
Description
This alarm is reported when the BTS data is configured on the basis of the physical board
independent of the logical object. The BTS actually, however, does not support the physical
board independent of the logical object.
Attribute

420 Major Event
(2008-06-24) 1-125
Parameters
ID Name Meaning
1 Site No. This parameter indicates the site No. that doesn't support config the card and
the logic object separately.
Impact on System
The initialization of the BTS fails. All the services of the BTS are disrupted.
System Actions
None
Possible Causes
In the configuration data, the BTS is set to support the physical board independent of the logical
object. The BTS actually, however, does not support the physical board independent of the
logical object.
Handling Procedure
Modify the BTS data on the basis of the physical board dependent of the logical object, and
make the configuration data account with the capability of the BTS, or upgrade the BTS software
to make it support the physical board independent of the logical object.
----End
1.74 421 PTU Initialization

Description
This alarm is reported when the PTU is initialized.
Attribute

421 Major Event
Parameters
ID Name Meaning
1 Site No. This parameter indicates the number of the initialized site.
1-126 (2008-06-24)
ID Name Meaning
2 Cause value l 0=The PTU is reset manually
l 1=The BSC resets the PTU
l 2=The PTU is reset automatically
l 3=Reset for other causes
Impact on System
When the PTU is reset, all the services related to the board are disrupted temporarily.
System Actions
None
Possible Causes
l 0= The PTU is reset manually
l 1= The BSC resets the PTU
l 2= The PTU is reset automatically
l 3= Reset for other causes
Handling Procedure
Step 1 The manual reset of the PTU does not require handling.
Step 2 If the BSC resets the BTS, check whether the BTS data configuration is correct on the BSC (for
example, check whether the cell attributes or the TRX attributes are configured correctly). The
BTS is not reset by the BSC. Go to step 3.
Y => The data configuration is correct. Go to step 4.
N => If the data configuration is incorrect, reconfigure all the data.
Step 3 If the PTU is reset automatically, check whether the BTS power supply is stable.
Y => The power supply is stable. Go to step 5;
N => If the power supply is unstable, replace the board related to power supply.
Step 4 View the BSC operation logs, and analyze whether the PTU reset is caused by dynamic
configuration.
Y => If the IP address of the PTU is changed, or the BTS is activated or deactivated, or the BTS
is reset on a four-level basis, no exception exists. The alarm handling is complete.
Step 5 View the BSC operation logs, and analyze, and analyze whether the IP address of the FG2/GOU
is changed.
Y => If the links are disconnected, the BTS reinitializes. No exception exists. The alarm handling
is complete.
----End
(2008-06-24) 1-127
1.75 422 BTS doesn't support abis optimize

Description
This alarm is reported when the TRX carrying the primary BCCH is abnormal, and then mutual
aid takes place between the primary BCCH TRX and other TRXs in this cell. This process
disrupts the services in the cell for a short period.
Attribute
422 Major Event
Parameters
ID Name Meaning
1 Site No. This parameter indicates the number of the site.
Impact on System
The initialization of the BTS fails. All the services of the BTS are disrupted.
System Actions
None
Possible Causes
In configuration data, the BTS is set to support Abis transmission optimization. The BTS
actually, however, does not support Abis transmission optimization.
Handling Procedure
Reconfigure the entire BTS data. Change the BTS service bearing mode to TDM transmission,
or upgrade the BTS software to make it support Abis transmission optimization.
----End
1.76 423 Extension Signaling Link Failure

Description
This alarm is reported when the extension signaling link between the BSC and the BTS is
disconnected.
1-128 (2008-06-24)
Attribute
423 Critical Fault
Parameters
ID Name Meaning
1 Site No. This parameter indicates the number of the BTS where the faulty extension
signaling link is configured.
Impact on System
The communication services are affected. If the period of link disconnection exceeds 10 minutes,
the PTU is automatically reset.
System Actions
After the alarm is generated, the BTS attempts to connect to the BSC periodically.
Possible Causes
l The transmission link is faulty.
l The GEHUB/GFGUB/GOGUB is not properly installed.
l The BTS is powered off.
l The PTU board in the BTS is faulty.
l The format of the E1 frame on the GEHUB/GFGUB/GOGUB does not match.
Handling Procedure
Step 1 Check whether the number of the E1 port connected to the BTS is consistent with the configured
data.
Y => Go to step 3.
Step 2 Check whether the GEHUB/GFGUB/GOGUB is loosely inserted.

Y => Insert the GEHUB/GFGUB/GOGUB tightly.
N => Go to step 3.
Step 3 Check whether the Abis transmission line is faulty.

Y => Repair the Abis transmission cable.
N => Go to step 4.
Step 4 Check whether the BTS is powered off.

Y => Power on the BTS.
N => Go to step 5.
(2008-06-24) 1-129
Step 5 Check whether the PTU is faulty.

Y => Replace the PTU board.
N => Go to step 6.
Step 6 Check whether the frame format configured on the GEHUB/GFGUB/GOGUB is consistent
between the local and peer ends.
Y=> Please contact Motorola for technical support.
N=> Set the frame format correctly and ensure that the frame format of the GEHUB/GFGUB/
GOGUB is consistent with that of the BTS.
----End
1.77 701 M3UA Link Fault

Description
This alarm is reported when the M3UA link is faulty.
Attribute
701 Warning Fault
Parameters
ID Name Meaning
1 Subrack No. This parameter indicates the number of the subrack for the M3UA link.
2 Slot No. This parameter indicates the slot No.
3 Cpu No. This parameter indicates the CPU No.
4 M3UA Link No. This parameter indicates the M3UA Link No.
1-130 (2008-06-24)
ID Name Meaning
5 Cause l 0=The ASP ACTIVE or ASP ACTIVE ACK message is received.
l 1=The signaling link is deactivated at the local end.
l 2=The signaling link is deactivated at the peer end.
l 17=The ASP DOWN ACK message is received.
l 65=The ASP DOWN message is received.
l 32=The signaling link is released at the local end.
l 49=The establishment of the signaling link fails.
l 50=The signaling link restart is initiated at the peer end.
l 52=There is no valid IP address,64= that the signaling link release
is initiated at the peer end.
l 254=The initial user configuration
l 255=Other reasons
Impact on System
l If there is not any other available links in the link set, the route of the link set is unavailable.
l If the DSP of some route does not have other available routes, the DSP cannot be visited.
An alarm is generated indicating that the destination point is inaccessible.
System Actions
The M3UA link will be reestablished periodically. If the alarm is cleared, the signaling link
resumes normal operation.
Possible Causes
l The signaling link is deactivated at the local or peer end.
l The signaling link is released at the local or peer end.
l The interfaced board is faulty.
l The transmission is faulty.
Handling Procedure
Step 1 Check whether the link is unavailable for more than six seconds.
Y => Go to step 3.
N => The signaling link is restored in six seconds. Go to step 2.
Step 2 Check whether a GFUGA/GOGUA switchover occurs.

Y => Add a signaling link.
N => Go to step 3.
Step 3 Through the LMT, check whether the 21205 Board Fault alarm is generated.
Y => Clear the alarm by referring to the relative handling suggestion.
N => If the alarm is cleared or does not exist, but the alarm cannot be cleared, go to step 4.
(2008-06-24) 1-131
Step 4 Check whether the link is deactivated.

Y => Activate the corresponding link. The alarm handling is complete.
----End
1.78 702 M3UA Link Congestion

Description
This alarm is reported when the M3UA link is congested.
Attribute
702 Warning Fault
Parameters
ID Name Meaning
1 Subrack No. This parameter indicates the number of the subrack for the M3UA link.
2 Slot No. This parameter indicates the slot No.
3 Cpu No. This parameter indicates the CPU No.
4 M3UA Link No. This parameter indicates the M3UA Link No.
Impact on System
The congestion of the M3UA signaling link causes the M3UA to discard user messages.
System Actions
The M3UA reports the congestion primitive to the SCCP, requiring that the SCCP and the SCCP
users lessen the MSUs to eliminate the congestion.
Possible Causes
Too many messages are sent to the M3UA link, so the link is congested.
Handling Procedure
Step 1 In the Brows Alarm window on the LMT, check whether the alarm is cleared within 10 seconds.
N => Go to step 2.
1-132 (2008-06-24)
Step 2 Add M3UA signaling links to share load and then check whether the alarm is cleared.
Y => The alarm is cleared. The alarm handling is complete.
----End
1.79 703 M3UA Route Unvailable

Description
This alarm is reported when the M3UA route is invalid.
Attribute
703 Warning Fault
Parameters
ID Name Meaning
1 M3UA De No. This parameter indicates the M3UA Destination Entity Number.
2 LinkSet No. This parameter indicates the LinkSet No.
3 Cause l 0=The corresponding link set is faulty.

l 1=The route is forbidden.
Impact on System
If the corresponding DSP has only one route, the signaling point is unreachable. Then, the 1.80
704 M3UA Destination Entity Unvailably alarm is generated.
System Actions
If one signaling link in the link set is restored to normal, the alarm is cleared automatically.
Possible Causes
The corresponding link set is faulty.
Handling Procedure
Step 1 Check whether signaling links are configured in the corresponding link set.
Y => Go to step 2.
N => Configure signaling links. The alarm handling is complete.
(2008-06-24) 1-133
Step 2 Check whether the 1.77 701 M3UA Link Fault alarm is generated before this alarm.
Y => Clear the alarm by referring to the handling suggestion for the 1.77 701 M3UA Link
Fault alarm. The alarm handling is complete.
N => The 1.77 701 M3UA Link Fault alarm is not generated and this alarm is not cleared.
----End
1.80 704 M3UA Destination Entity Unvailably

Description
This alarm is reported when the M3UA destination entity is unreachable.
Attribute
704 Warning Fault
Parameters
ID Name Meaning
1 M3UA De No. This parameter indicates the M3UA Destination Entity Number.
2 M3UA Le No. This parameter indicates the M3UA Le No.
3 OPC This parameter indicates the OPC.
4 DPC This parameter indicates the DPC.
5 NI l 0=International,
l 1=International Standby
l 2=National
l 3=National Standby
6 Cause l 0=All the routes are unreachable

Impact on System
The local signaling point cannot transmit the MSU to the specified DSP, so the services are
disrupted.
1-134 (2008-06-24)
System Actions
The M3UA reports the SCCP the suspension primitive, informing that the destination signaling
point is unreachable. The SCCP reports the message to the user layer and then the user layer
disrupts the services related to the specified DSP.
Possible Causes
All the routes reaching this DSP are unreachable.
Handling Procedure
Step 1 Check whether the signaling links reaching this DSP are configured.
Y => Go to step 2.
N => Configure signaling links. The alarm handling is complete.
Step 2 Check whether the 1.77 701 M3UA Link Fault alarm is generated before this alarm.
Y => Clear the alarm by referring to the handling suggestion for the 1.77 701 M3UA Link
Fault alarm. The alarm handling is complete.
N => The 1.77 701 M3UA Link Fault alarm is not generated and this alarm is not cleared.
----End
1.81 705 FG2/GOU Route Status Unavailable

Description
This alarm is reported when the route of the FG2/GOU is unreachable.
Attribute
705 Warning Fault
Parameters
ID Name Meaning
1 Subrack No. This parameter indicates the number of the subrack of the FG2/GOU.
2 Slot No. This parameter indicates the number of the slot of the FG2/GOU.
3 Port No. This parameter indicates the number of the port of the FG2/GOU.
Impact on System
The services are disrupted.
(2008-06-24) 1-135
System Actions
The system detects that the route is unreachable. Then, the system stops assigning user resources.
Possible Causes
The ARP detects that the peer route is unreachable.
Handling Procedure
Step 1 Check whether the DSP ETHPORT is faulty.
Y => Use other ports available.
N => Go to step 2.
Step 2 Check whether the physical connection of the Ethernet cable between the FG2/GOU and the
router is proper.
Y => Reconnect the Ethernet cable.
----End
1.82 801 Data Out of Synchronization

Description
This alarm is reported when the data consistency check shows that the GBAM core program and
the GBAM local program or service board data are inconsistent.
Attribute
801 Critical Fault
Parameters
ID Name Meaning
1 Subrack No. This parameter indicates the number of the subrack where the board with
inconsistent data is located.
2 Slot No. This parameter indicates the number of the slot where the board with
3 Subslot No. This parameter indicates the number of the subslot where the board with
4 CPU No. This parameter indicates the number of the CPU where the board with
1-136 (2008-06-24)
Impact on System
The data cannot be synchronized with the GBAM local program or service board data, causing
some services are not functional.
System Actions
None.
Possible Causes
l Data configuration is performed after configuration fails to take effect.
l In the data upload recovery, the used data file is inconsistent with the service board data.
Handling Procedure
Step 1 On the LMT, choose Configuration > Load and Restore. Check whether the GBAM local
program and all service boards fail to reset after the data upload recovery on the LMT.
Y => When the traffic is not heavy (early in the morning), Reset the GBAM local program and
corresponding service board.
N => Go to step 2.
Step 2 Check whether the data fails to take effect in the dynamic configuration.
Y => Go to step 3.
N => The data is successful to take effect. When the traffic is not heavy (early in the morning),
reset the GBAM local program and corresponding service board.
Step 3 On the LMT, perform the forced check and synchronization and check whether the
synchronization is successful.
N => When the traffic is not heavy (early in the morning), reset the GBAM local program and
corresponding service board.
----End
1.83 802 Error of Transaction Logging File

Description
This alarm is reported when there is error in transaction logging file.
Attribute

802 Critical Event
(2008-06-24) 1-137
Parameters
ID Name Meaning
1 The cause l 1=The transaction logging file was not consistent with the baseline
l 2=There was invalid transaction logging
l 3=The Transaction logging file did not exist
Impact on System
The data used for restoration is invalid.
System Actions
None
Possible Causes
l The transaction logging file was not consistent with the baseline.
l There was invalid transaction logging.
l The Transaction logging file did not exist.
Handling Procedure
None
----End
1.84 951 TDM slot link error

Description
This alarm is reported when the sent DSP timeslot data loopback and the received DSP timeslot
data loopback are inconsistent.
Attribute
951 Minor Event
Parameters
ID Name Meaning
1 Subrack No This parameter indicates the number of the subrack where the GDPU board
incurring the DSP alarm is located.
1-138 (2008-06-24)
ID Name Meaning
2 slot No This parameter indicates the slot number of the subrack where the GDPU
board incurring the DSP alarm is located.
3 Dsp No This parameter indicates the number of the DSP where the alarm is
generated.
Impact on System
The Call of DSP is abnormal.
System Actions
After the DSP is reset, if the timeslot is normal, then the DSP runs normally. Otherwise, the DSP
is reset all the time.
Possible Causes
l The TSU board is not inserted.
l The TC version does not match the platform version.
l The TDM switching chip on the DPU board is faulty.
l The DSP MCBSP data line is faulty.
l The DSP chip is faulty.
Handling Procedure
Step 1 Check whether the TSU board is inserted.
Step 2 Ensure that the TC version matches the platform version.
Step 3 Check whether the TDM switching chip is normal through hardware.
Step 4 Locate the fault of the DSP MCBSP data line through hardware.
Step 5 Locate the fault of the DSP chip on the DPU board through hardware.
----End
1.85 1000 LAPD OML Fault

Description
This alarm is reported when the LAPD OML between the BSC and BTS is disconnected.
(2008-06-24) 1-139
Attribute
1000 Critical Fault
Parameters
ID Name Meaning
1 Site No. This parameter indicates the number of the site where the OML link is
disconnected.
Impact on System
The call services are affected. The BTS is reset automatically if the OML is disconnected for
more than 15 minutes.
System Actions
After the alarm is generated, the BSC regularly keeps on making handshake link setup attempts.
Possible Causes
l The transmission line is faulty.
l The GEIUB/GOIUB on the Abis interface is loosely inserted.
l The BTS has a power failure.
l The TMU of the BTS is faulty.
l The format of the E1 frame on the corresponding GEIUB/GOIUB interface board is wrong.
Handling Procedure
Step 1 Check whether the number of the E1 port connected to the BTS is consistent with the configured
data.
Y => Go to step 3.
Step 2 Check whether the GEIUB is loosely inserted.

Y => Insert the GEIUB tightly.
N => Go to step 3.
Step 3 Check whether the Abis transmission line is faulty.

Y => Repair the Abis transmission cable.
N => Go to step 4.
Step 4 Check whether the BTS is powered off.

Y => Power on the BTS.
N => Go to step 5.
1-140 (2008-06-24)
Step 5 Check whether the TMU is faulty.

Y => Replace the TMU board.
N => Go to step 6.
Step 6 Check whether the frame format configured on the GEIUB is consistent between the local and
peer ends.
Y=> Please contact Motorola for technical support.
N=> Set the frame format correctly and ensure that the frame format of the GEIUB is consistent
with that of the BTS.
----End
1.86 20002 Incorrect Board Slot Information

Description
This alarm is reported when the slot information is different from the slot information recorded
upon board power-on.
Attribute

20002 Major Fault
Parameters
ID Name Meaning
board is located.
2 Slot No. This parameter indicates the number of the slot where the board
is located.
3 CPU No. This parameter indicates the number of the CPU that reports the
alarm.
4 Current slot information This parameter indicates the current information obtained on
the slot.
5 Initial slot information This parameter indicates the slot information recorded when the
board is initialized.
Impact on System
l If the board is not reset, the service will not be affected.
(2008-06-24) 1-141
l If the board is reset, it might not be normally started or the service over the board might
not be normally proceeded after normal startup.
System Actions
l Handling of the active board in the active/standby operation mode: Perform the switchover
if the standby is ready for the operation.
l
l Handling of the standby board in the active/standby operation mode: None.

l Handling of the board in the Independent operation mode: None.
Possible Causes
l The board is not securely inserted.
l The pin of the board is damaged.
l The connector of the board is damaged.
Handling Procedure
Step 1 Insert securely the board and check whether the alarm is cleared.
Step 2 Check whether the alarm is reported by two or more boards in the same subrack.
Y => Two or more boards report this alarm in the same subrack. Please contact Motorola for
technical support.
N => Only one board reports this alarm. Go to step 3.
Step 3 Check whether the board is in independent operation mode.
Y => The board is in Independent operation mode. Go to step 7.
N => The board is in active/standby operation mode. Go to step 4.
Step 4 Check whether the active board reports this alarm.
Y => The active board reports this alarm. Go to step 5.
N => The standby board reports this alarm. Go to step 6.
Step 5 If the alarm is reported by the active board, a switchover between the active and standby boards
will be automatically performed. If the standby board has a same- or higher-level alarm, the
switchover fails, resulting in the persistence of the alarm within the active board. Clear the alarm
of the standby board by adhering to relevant alarm-handling procedures, and then check whether
the switchover between the active and standby boards is performed.
Y => The switchover is performed. Go to step 6.
N => The switchover is not performed. Please contact Motorola for technical support.
Step 6 Replace the standby board and wait until the board is successfully restarted. Check whether the
alarm is cleared.
N => The alarm persists. Please contact Motorola for technical support.
Step 7 Replace the board and wait until the board is successfully restarted. Check whether the alarm is
cleared.
1-142 (2008-06-24)

----End
1.87 20003 Board Fault - Faulty Inner Clock

Description
This alarm is reported only when the inner clock is faulty.
Attribute
20003 Major Fault
Parameters
ID Name Meaning
1 Subrack No. This parameter indicates the number of the subrack where the board is
located.
2 Slot No. This parameter indicates the number of the slot where the board is located.
3 CPU No. This parameter indicates the number of the CPU that reports the alarm.
4 Clock type l 1=25M clock (GXPUx/GSCU)

l 2=32M clock (GDPUC/GEIUx/GOIUx/GTNU)
l 3=33M clock (GXPUx/GDPUC/GSCU)
l 4=50M clock (GDPUC)
l 5=66M clock (GDPUC)
l 6=100M clock (TSU)
l 7=127M clock (GSCU)
l 8=157M clock (GSCU)
Impact on System
The service provided by this board might be affected or interrupted.
System Actions
Reset the board.
Possible Causes
Hardware fault on the board
(2008-06-24) 1-143
Handling Procedure
Step 1 After the board is automatically reset, wait until the new board is successfully restarted. Check
Step 2 Replace the board that reports the alarm and check whether the alarm is cleared.
----End

Description
This alarm is reported when the voltage of the board is abnormal.
Attribute
20004 Major Fault
Parameters
ID Name Meaning
1 Subrack No. This parameter indicates the number of the subrack where the board
is located.
2 Slot No. This parameter indicates the number of the slot where the board is
located.
alarm.
4 Voltage Type This parameter indicates the type of the voltage that triggers an alarm.
5 Voltage This parameter indicates the value of the voltage when the alarm
occurs.
6 The low threshold This parameter indicates the lower threshold of the Abnormal
Voltage alarm (unit: mV).
7 The high threshold This parameter indicates the upper threshold of the Abnormal
Voltage alarm (unit: mV).
1-144 (2008-06-24)
Impact on System
The service provided by this board might be affected or interrupted.
System Actions
Possible Causes
The board is faulty.
Handling Procedure
Replace the faulty board and wait until the new board is successfully loaded and reset. Check
----End
1.89 20005 Faulty Clock Source 0 from the Front Interface

Board to the Backplane of the GSCU
Description
This alarm is reported when clock source 0 from the front interface board to the backplane of
the GSCU is faulty.
Attribute
20005 Major Fault
Parameters
ID Name Meaning
located.
(2008-06-24) 1-145
Impact on System
If this alarm is reported from all the clock references being configured on the interface boards,
the voice quality and the reliable transmission of the data service might be affected.
System Actions
l If the current clock source is faulty, the clock source will be switched to other normal clock
sources which are available at the time being.
l No action is taken in other cases.
Possible Causes
l The clock is incorrectly configured.
l The clock source is abnormal.
l A hardware fault occurs.
Handling Procedure
Step 1 Check whether the alarm occurs to both the active and the standby GSCUs.
Y => The alarm occurs to both GSCUs. Go to step 2.
N => The alarm occurs to only one board. Go to step 8.
Step 2 Check whether the clock is incorrectly configured.
Y => The clock is incorrectly configured. Go to step 3.
N => The clock is correctly configured. Go to step 4.
Step 3 Configure the clock correctly, and check whether the alarm is cleared.
Step 4 Check whether an alarm related to the E1 or optical interface occurs to the interface board.
Y => An alarms occurs. Go to step 5.
N => No alarm occurs. Please contact Motorola for technical support.
Step 5 Clear the alarm on the interface board according to its relevant handling suggestions, and then
check whether the alarm on the GSCU is cleared.
Step 6 Insert securely the interface board and the GSCU, and check whether the alarm is cleared.
Step 7 Switch over the interface boards and check whether the alarm is cleared.
Y => The alarm is cleared. Replace the standby interface board. The alarm handling is complete.
Step 8 Check whether the alarm occurs to the active GSCU.
Y => The alarm occurs to the active GSCU. Go to step 9.
N => The alarm occurs to the standby GSCU. Go to step 10.
1-146 (2008-06-24)
Step 9 Switch over the GSCUs, and check whether the fault alarm is cleared.
Step 10 Replace the standby GSCU and wait until the board is successfully restarted. Check whether the
alarm is cleared.
----End
1.90 20006 Faulty Clock Source 1 from the Front Interface

Description
This alarm is reported when clock source 1 from the front interface board to the backplane of
the GSCU is faulty.
Attribute

20006 Major Fault
Parameters
ID Name Meaning
located.
Impact on System
System Actions
rsources which are available at the time being.
l No actions are taken for other cases.
(2008-06-24) 1-147
Possible Causes
Handling Procedure
Step 1 Check whether the alarm occurs to both the active and the standby GSCU boards.
Y => The alarm occurs to both boards. Go to step 2.
Y => An alarm occurs to the interface board. Go to step 5.
Step 6 Insert securely the interface board and the GSCU board, and check whether the alarm is cleared.
N =>The alarm persists. Go to step 7.
alarm is cleared.
----End
1-148 (2008-06-24)
1.91 20007 Faulty Clock Source 0 from the Rear Interface

Description
This alarm is reported when clock source 0 from the rear interface board to the backplane of the
GSCU is faulty.
Attribute
20007 Major Fault
Parameters
ID Name Meaning
located.
Impact on System
System Actions
resources which are available at the time being.
Possible Causes
l A hardware fault occurs
Handling Procedure
Step 1 Check whether a correlated parent alarm occurs.
Y=> Clear the parent alarm according to the corresponding handling suggestions. Check whether
the alarm is cleared.
(2008-06-24) 1-149
N=> Go to step 2.
The parent alarm and the child alarm must have the same Subrack No. in the alarm location
information.
The LINE0 clock of the subrack reporting the alarm must be configured with the line clock, and
extracted at the port specified in the alarm location information of the parent alarm.
The parent alarm must be generated at the active board.
information.
extracted at the port in the alarm location information of the parent alarm.
information.
information. The PPL No. in the alarm location information of the parent alarm must be 1.
N => The alarm occurs to only one GSCU. Go to step 9.
Y => An alarm occurs. Go to step 6.
1-150 (2008-06-24)


alarm is cleared.
----End
1.92 20008 Faulty Clock Source 1 from the Rear Interface

Description
This alarm is reported when clock source 1 from the rear interface board to the backplane of the
GSCU is faulty.
Attribute

20008 Major Fault
Parameters
ID Name Meaning
located.
(2008-06-24) 1-151
Impact on System
System Actions
resources which are available at the time being.
Possible Causes
Handling Procedure
N=> Go to step 2.
information.
information.
information.
information. The PPL No. in the alarm location information of the parent alarm must be 1.
1-152 (2008-06-24)
N => The alarm occurs to only one GSCU. Go to step 9.
Y => An alarm occurs. Go to step 6.
alarm is cleared.
----End
1.93 20009 Faulty 8 kHz Clock Source from the Active GGCU
to the Backplane of the GSCU
Description
This alarm is reported when the 8 kHz clock source from the active GGCU to the backplane of
the GSCU is faulty.
(2008-06-24) 1-153
Attribute
20009 Major Fault
Parameters
ID Name Meaning
located.
Impact on System
The voice quality and data transmission are affected.
System Actions
None
Possible Causes
l The upper-level clock source on the active GGCU is not locked, and no clock source is
provided for the GSCU.
l The active GGCU is faulty.
l The GSCU is faulty.
l The backplane is faulty.
Handling Procedure
Step 1 Check whether the alarm is generated on both the active and the standby GSCUs.
Y => The alarm is generated on both GSCUs. Go to step 2.
N => The alarm is generated on only one GSCU. Go to step 4.
Step 2 Insert securely the active GGCU and then check whether the alarm is cleared.
N => The alarm is not cleared. Go to step 3.
Step 3 Switch over the GGCUs and check whether the alarm is cleared.
N => The alarm is not cleared. Please contact Motorola for technical support.
Step 4 Insert securely the GSCU and then check whether the alarm is cleared.
1-154 (2008-06-24)
Step 5 Check whether the active board reports the alarm.

Y => The active board reports the alarm. Go to step 6.
N => The standby board reports the alarm. Go to step 7.
will be automatically performed.If the standby board has a same- or higher-level alarm, the
switchover fails, resulting in the persistence of the alarm within the active board.Clear the alarm
Y => The switchover is successful. Go to step 7.
N => The switchover fails. Please contact Motorola for technical support.
Step 7 Replace the faulty standby GSCU and wait until the new board is successfully loaded and reset.
Check whether the alarm is cleared.
----End
1.94 20010 Faulty 8 kHz Clock Source from the Standby

GGCU to the Backplane of the GSCU
Description
This alarm is reported when the 8 kHz clock source from the standby GGCU to the backplane
of the GSCU is faulty.
Attribute

20010 Minor Fault
Parameters
ID Name Meaning
located.
(2008-06-24) 1-155
Impact on System
l If the switchover between the active and standby boards is not performed, the service will
not be affected.
l If the switchover between the active and standby boards is performed, the voice quality
and the transmission of data service will be affected.
System Actions
None.
Possible Causes
l The standby GGCU is not locked to the upper-level clock source. No clock source is input
to the GSCU.
l The standby GGCU is faulty.
l The active GSCU is faulty.
Handling Procedure
Step 1 Check whether the alarm is generated on both the active and standby GSCUs.
Step 2 Insert securely the standby GGCU and then check whether the alarm is cleared.
Step 3 Replace the standby GGCU, wait until the new GGCU is successfully loaded, and then check
Step 4 Insert securely the GSCU and then check whether the alarm is cleared.

Step 6 Perform switchover between the active and standby GSCUs. Wait until the standby GSCU is
successfully restarted, and then check whether the alarm is cleared.
1-156 (2008-06-24)
----End
1.95 20013 Faulty GGCU 8 kHz Clock Source for the Front
Panel of the GSCU
Description
This alarm is reported when the GGCU 8 kHz clock source for the front panel of the GSCU is
faulty.
Attribute

20013 Major Fault
Parameters
ID Name Meaning
located.
Impact on System
System Actions
None.
Possible Causes
l The clock line between the GSCU and GGCU is not connected, or wrongly connected. The
clock line might be loose or faulty.
l The active GGCU is not locked to the upper-level clock source. No clock source is available
in the GSCU.
l The active GGCU is faulty.
l The active GSCU is faulty.
(2008-06-24) 1-157
Handling Procedure
Step 1 Check whether the clock line between the GSCU and the GGCU is securely connected. For
example, check whether the line is inserted, whether it is loose, or whether it is faulty.
Y => The clock line is not securely connected. Go to step 2.
N => The clock line is securely connected. Go to step 3.
Step 2 Connect the clock line securely and check whether the alarm is cleared.
Step 3 Replace the clock line between the GSCU and the GGCU, and then check whether the alarm is
cleared.
Step 4 Check whether the alarm is generated on both the active and standby GSCUs.
Step 5 Switch over the GGCUs and check whether the alarm is cleared.
Y => This alarm is cleared. The services are not affected temporarily. You are advised to replace
the faulty GGCU in time. The alarm handling is complete.

Step 7 Perform switchover between the active and standby GSCUs. Wait until the standby GSCU is
successfully restarted, and then check whether the alarm is cleared.
----End

Description
This alarm is reported when the 32 MHz TDM clock from the backplane is faulty.
1-158 (2008-06-24)
Attribute
20016 Major Fault
Parameters
ID Name Meaning
located.
Impact on System
System Actions
Possible Causes
l The GSCU rejects clock reference from the backplane.
l The GSCU is not securely inserted.
l The service board is not securely inserted.
l The service board is faulty.
Handling Procedure
N=> Go to step 2.
The parent alarm and the child alarm have the same Subrack No. in the alarm location
information.
(2008-06-24) 1-159

The parent alarm and the child alarm have the same Subrack No. in the alarm location
information.
Step 2 Check whether two or more boards report this alarm in the same subrack.
Y => Two or more boards report this alarm. Go to step 3.
N => Only one board reports this alarm. Go to step 7.
Step 3 Check whether there is an alarm with the clock source chosen by the active GSCU.
Y => There is an alarm with the clock source. Go to step 4.
N => There is no alarm with the clock source. Go to step 5.
Step 4 Clear the clock alarm of the active GSCU according to its relevant handling suggestions, and
then check whether the alarm of the board is cleared.
Step 5 Secure the active GSCU and check whether the alarm is cleared.
Step 6 Perform the switchover between the active GSCU and standby GSCU, and then check whether
Y => The alarm is cleared. The service might not be affected for the time being, but we suggest
changing the standby GSCU in time. The alarm handling is complete.
Step 7 Secure the service board which reports the alarm, and then check whether the alarm is cleared.

Y => The switchover succeeds. Go to step 10.
alarm is cleared.
----End
1-160 (2008-06-24)
1.97 20025 BIOS Check Failure

Description
This alarm is report when the BIOS check detects BIOS file error.
Attribute
20025 Major Fault
Parameters
ID Name Meaning
1 Subrack No. This parameter indicates the number of the
subrack where the board is located.
2 Slot No. This parameter indicates the number of the

slot where the board is located.
3 CPU No. This parameter indicates the number of the

CPU that reports the alarm.
4 Number of the BIOS that triggers the l 0=BIOS0

alarm
l 1= BIOS1
Impact on System
l If the board is reset, the board might fail to be restarted.
System Actions
None.
Possible Causes
l The BIOS file is modified.
l The board FLASH for storing the BIOS file is damaged.
Handling Procedure
Step 1 Check whether BIOS 0 is faulty.
Y => BIOS 0 is faulty. Go to step 3.
N => BIOS 1 is faulty. Go to step 2.
(2008-06-24) 1-161
Step 2 Load BIOS through the LMT and wait for three hours. Check whether the alarm is cleared.
Step 3 Replace the board and wait until the new board is successfully restarted. Check whether the
alarm is cleared.
----End

Description
This alarm is report when the board clock phase-lock loop is faulty.
Attribute

20026 Major Fault
Parameters
ID Name Meaning
located.
4 PPL No. This parameter indicates the number of the phase-lock loop.
Impact on System
System Actions
1-162 (2008-06-24)
Possible Causes
As the probable causes vary for different types of boards, please specify the type of the board
in advance by the subrack number and slot number where the board is located.
l If the GEIUx or GOIUx is faulty:

The active GSCU stops the clock output from the backplane.
The transmission equipment or the transmission link is faulty.
The hardware of the board is faulty.
l If the GTNU,GDPUC, or GSCU is faulty: the hardware of the board is faulty.
Handling Procedure
Step 1 As the handling procedures vary for different types of boards, please specify the type of the
board in advance by the subrack number and slot number where the board is located. If the
GEIUx/GOIUx is faulty:
(1) Check whether a correlated parent alarm occurs.
Y=> Clear the parent alarm according to the corresponding handling suggestions. Check
N=> Go to step b.
The parent alarm and the child alarm have the same Subrack No. and Slot No. in the alarm
location information.
(2) Check whether the PPL number of the faulty board is 1.
Y => The PPL number is 1. Go to step c.
N => The PPL number is not 1. Go to step e.
(3) Check whether there is optical port alarm.
Y => There is optical port alarm. Go to step d.
N => There is no optical port alarm. Go to step g.
(4) Clear the optical port alarm according to its relevant handling suggestions, and then check
whether the phase-locked alarm of the board clock is cleared.
N => The alarm persists. Go to step g.
(5) Check whether there is clock alarm with the active GSCU.
Y => There is clock alarm. Go to step f.
N => There is no clock alarm. Go to step g.
(6) Clear the GSCU alarm by adhering to the its clock handling procedures, and then check
whether the GEIUx/GOIUx alarm is cleared.
N => The alarm persists. Go to step g.
(7) Replace the board and wait until the board is successfully restarted. Check whether the
alarm is cleared.
(2008-06-24) 1-163
board in advance by the subrack number and slot number where the board is located. If the
GDPUC, GTNU, or GSCU is faulty:
N=> Go to step b.
(2) Replace the board and wait until the board is successfully restarted. Check whether the
alarm is cleared.
----End
1.99 20027 Abnormal Subrack Information

Description
The current subrack information is inconsistent with the initial subrack information
Attribute

20027 Major Fault
Parameters
ID Name Meaning
1 Subrack No. This parameter indicates the number of the subrack where
the board is located.
2 Slot No. This parameter indicates the number of the slot where the
board is located.
3 CPU No. This parameter indicates the number of the CPU that reports
the alarm.
4 Current subrack information This parameter indicates the subrack information read from
board currently.
1-164 (2008-06-24)
ID Name Meaning
5 Initial subrack information This parameter indicates the subrack information read from
board when board boots up.
Impact on System
l If the board is reset, it might not be normally started or the service over the board might
not be normally proceeded after normal startup.
System Actions
None.
Possible Causes
l The DIP switch is manually changed when the board is functioning.
l The pin of the backplane is damaged.
l The subrack DIP is damaged.
Handling Procedure
Step 1 Check whether the alarm occurs to the boards in the concerned subrack.
Y => The alarm occurs to more than one board. Go to step 2.
Step 2 Check whether the subrack DIP switch is manually changed.
Y => The subrack DIP switch is manually changed. Resume the correct setting and the alarm
handling is complete.
N => The subrack number is not changed. Please contact Motorola for technical support.
Step 3 Securely insert the board and check whether the alarm is cleared.
cleared.
----End
1.100 20028 Faulty Packet Switching Unit

Description
This alarm is reported when the packet switch unit is faulty.
(2008-06-24) 1-165
Attribute
20028 Major Fault
Parameters
ID Name Meaning
board is located.
is located.
alarm.
4 Logical chip No. 0=Packet switch unit
5 First 32-bit information This parameter indicates the first 32 bit status information of
packet switch unit.
6 Last 32-bit information This parameter indicates the second 32 bit status information of
packet switch unit.
Impact on System
The service carried on this board might be interrupted.
System Actions
Reset the board.
Possible Causes
Faulty packet switching unit.
Handling Procedure
Step 1 After the board is automatically reset, wait until the board is successfully restarted. Check
Step 2 Replace the board that reports the alarm and wait until the board is successfully restarted. Check
1-166 (2008-06-24)
----End
1.101 20029 Board Fault - Faulty Logical Unit

Description
This alarm is reported when the board logic is faulty.
Attribute
20029 Major Fault
Parameters
ID Name Meaning
located.
located.
4 Logical chip No. This parameter indicates the number of the logic chip.
Impact on System
The services may be interrupted.
System Actions
Reset the board.
Possible Causes
The logical chip of a board is faulty.
Handling Procedure
Step 1 After the board is automatically reset, wait until the board is successfully restarted. Check
(2008-06-24) 1-167
Step 2 Replace the board that reports the alarm and wait until the board is successfully restarted. Check
----End

Description
This alarm is reported when the pinch board in-position state is faulty.
Attribute
20030 Major Fault
Parameters
ID Name Meaning
is located.
located.
alarm.
4 Sub-board slot No. This parameter indicates the pinch board slot No.
1-168 (2008-06-24)
ID Name Meaning
5 Initial sub-board l 0=E1 pinch board
l 1=STM-1 optical pinch board
l 2=STM-1 electric pinch board
l 3=E3T3 pinch board
l 4=EAS pinch board
l 10=DSP pinch board type 0
l 14=EC256 pinch board
l 15=IEC512 pinch board
l 20=CPU pinch board
6 Current sub-board l 0=E1 pinch board

l 1=STM-1 optical pinch board
l 2=STM-1 electric pinch board
l 3=E3T3 pinch board
l 4=EAS pinch board
l 14=EC256 pinch board
l 15=IEC512 pinch board
l 20=CPU pinch board
Impact on System
l If the alarm is reported from GEIUx/GOIUx, all the services carried might be interrupted.
l If the alarm is reported from GDPUC, the service processing capability might decrease and
the call-drop might happen.
l If the alarm is reported from GXPUx, the signaling processing capability might decrease
and the services might interrupt.
(2008-06-24) 1-169
System Actions
The handling procedures of the system vary for different types of boards.
l If the GEIUx or GOIUx is faulty: Reset the board.

l If the GDPUC or GXPUx is faulty: No action is taken.
Possible Causes
l The sub-board is not inserted.
l The sub-board is not securely inserted.
l The sub-board is damaged.
l The bottom plate is damaged.
Handling Procedure
Step 1 Remove the specific board, insert securely the sub-board, reinsert the board, wait until the new
board is successfully restarted. Check whether the alarm is cleared.
Step 2 Replace the board that reports the alarm and wait until the new board is successfully restarted.
----End

Description
This alarm is reported when the board chip is faulty.
Attribute
20038 Major Fault
Parameters
ID Name Meaning
located.
1-170 (2008-06-24)
ID Name Meaning
4 Chip type l 8=GE interface chip

l 9=TDM switch chip
l 14=E1 interface chip
l 17=Optical interface chip
l 51=bridge chip
l 128=PIU_SDRAM
l 129=PIU_SRAM
l 130=PIU_FLASH
l 131=PIU_CPLD
l 132=PIU_FPGA
l 133=PIU_VXWORKS
l 134= PIU_GE interface chip
l 135=PIU_FE/GE interface chip
l 136=PIU_E1 interface chip
l 137=PIU_IMA process chip
l 139=PIU_E1 map chip
l 140=PIU_SDH/SONET interface chip
l 141=PIU_PPP/MP link layer process chip
l 143=PIU_SUBFPGA
l 144=PIU_SUBCPLD
l 145=PIU_SUBSRAM
l 146=PIU_EEPROM
l 147=PIU_SUB_BOARD_UP
l 148=PIU_SUB_BOARD_DOWN
l 149=PIU_NPMAC
5 Chip No. Chip index
Impact on System
System Actions
Reset the board.
(2008-06-24) 1-171
Possible Causes
l The chip clock is not working steadily.
l The chip is faulty.
Handling Procedure
Step 1 After the board is automatically reset, wait until the new board is successfully restarted. Check
Step 2 Replace the board that reports the alarm and check whether the alarm is cleared.
----End
1.104 20039 Faulty Output Clock Signals

Description
This alarm is reported when the board detects errors when polling the clock output.
Attribute

20039 Major Fault
Parameters
ID Name Meaning
located.
4 Clock type This parameter indicates the Clock type.
Impact on System
The voice quality and the reliable transmission of the data service might be affected.
1-172 (2008-06-24)
System Actions
Possible Causes
Handling Procedure
Step 1 Check whether the board is in Independent operation mode.
Y => The board is in independent operation mode. Go to step 5.

alarm is cleared.
cleared.
----End
1.105 20040 High Board Temperature - Minor Alarm

Description
This alarm is reported when the temperature of the test point of the board is over the minor high
threshold.
(2008-06-24) 1-173
Attribute
20040 Minor Fault
Parameters
ID Name Meaning
1 Subrack No. This parameter indicates the number of the subrack
where the board is located.
2 Slot No. This parameter indicates the number of the slot where
3 CPU No. This parameter indicates the number of the CPU that
reports the alarm.
4 Temperature of test point 0 This parameter indicates the temperature value (unit:
degree centigrade) of test point No.0, 65535 indicates
that the test point is not exist.
7 The threshold of test point No.0 This parameter indicates the temperature threshold of
test point 0. 65535 indicates that the test point does not
exist.
exist.
exist.
Impact on System
If the board with high temperature works for a long time, a fault may arise.
1-174 (2008-06-24)
System Actions
The fan is adjusted to work in full speed.
Possible Causes
l The ambient temperature is high.
l The fan box is faulty.
l The empty slot is not installed with a dummy panel.
Handling Procedure
Step 1 Check whether the fan box is faulty .
Y => The fan box is faulty. Replace the fan box. Go to step 2.
N => The fan box is normal. Go to step 2.
Step 2 Check whether there are empty slots which have not installed dummy panels.
Y => There are empty slots which have not installed dummy panels. Go to step 3.
N => All the slots have installed boards or dummy panels. Go to step 3.
Step 3 Check whether the temperature exceeds the normal operation range for the equipment.
Y => The temperature exceeds the normal operation range for the equipment. Adjust the
temperature to the normal operation range. Go to step 4.
N => The temperature does not exceed the normal operation range. Please contact Motorola for
technical support.
Step 4 Wait for 30 minutes and check whether the alarm is cleared.
----End
1.106 20041 High Board Temperature - Major Alarm

Description
This alarm is reported when the temperature of the test point of the board is over the major high
threshold.
Attribute
20041 Major Fault
(2008-06-24) 1-175
Parameters
ID Name Meaning
reports the alarm.
exist.
exist.
exist.
Impact on System
If the board with high temperature works for a long time, a fault may arise.
System Actions
Possible Causes
1-176 (2008-06-24)
Handling Procedure
technical support.
----End
1.107 20042 High Board Temperature - Critical Alarm

Description
This alarm is reported when the temperature of the test point of the board is over the critical high
threshold.
Attribute
20042 Critical Fault
Parameters
ID Name Meaning
reports the alarm.
(2008-06-24) 1-177
ID Name Meaning
that the test point is not exist
exist.
exist.
exist.
Impact on System
The board is damaged soon.
System Actions
Possible Causes
Handling Procedure
1-178 (2008-06-24)
technical support.
----End

Description
This alarm is reported when the selected clock reference source status is abnormal.
Attribute

20044 Major Fault
Parameters
ID Name Meaning
located.
Impact on System
System Actions
l Handling of the board in the Independent operation mode:None .
(2008-06-24) 1-179
Possible Causes
l No clock signal is exported by the selected clock source.
l The clock signal imported from the selected clock source is bad.
Handling Procedure
N=> Go to step 2.
1.91 20007 Faulty Clock Source 0 from the Rear Interface Board to the Backplane of the
GSCU
The reference clock of the subrack is configured with the line clock, which is only the LINE0
clock, not the LINE1 clock.
1.92 20008 Faulty Clock Source 1 from the Rear Interface Board to the Backplane of the
GSCU
The reference clock of the subrack is configured with the line clock, which is only the LINE1
clock, not the LINE0 clock.
NOTE
When 20007 Faulty Clock Source 0 from the Rear Interface Board to the Backplane of the GSCU, 20008 Faulty
Clock Source 1 from the Rear Interface Board to the Backplane of the GSCU, and this alarm have the same
Subrack No. and Slot No. in the alarm location information, and when the reference clock of the subrack is
configured with both LINE0 and LINE1, this alarm occurs in the case that two parent alarms occur at the same
time.
1.93 20009 Faulty 8 kHz Clock Source from the Active GGCU to the Backplane of the
GSCU
The reference clock of the subrack is configured with the backplane clock.
1.95 20013 Faulty GGCU 8 kHz Clock Source for the Front Panel of the GSCU
The reference clock of the subrack is configured with the panel clock.
Step 2 Check whether the alarm occurs to other clock sources.

Y => Alarm occurs to other clock sources. Remove the alarm by referring to other clock sources.
----End
1-180 (2008-06-24)
1.109 20045 Failed to Get Temperature

Description
This alarm is generated when the reading of board temperature from test point fails.
Attribute
20045 Major Fault
Parameters
ID Name Meaning
located.
Impact on System
Temperature cannot be monitored. Thus, some devices may be burned in the case of too high
temperature.
System Actions
l Adjust the fan to work at full speed.
l For the board that works as the active board in active/standby mode, a switchover is
performed if allowed.
l For the standby board in active/standby mode: No system action is taken.
l For the board in independent mode: No system action is taken.
Possible Causes
The temperature monitoring device is faulty.
Handling Procedure
Step 1 Check whether the board works in independent mode.
Y => The board works in independent mode. Go to step 5.
N => The board works in active/standby mode. Go to step 2.
(2008-06-24) 1-181

Y => The switchover is successful. Go to step 4.
cleared.
cleared.
----End
1.110 20052 Flash erase/write fail alarm

Description
This alarm is reported when the Flash is failed to erase or failed to write to.
Attribute
20052 Minor Fault
Parameters
ID Name Meaning
located.
Impact on System
l The system configuration cannot be saved to the Flash of the board.
1-182 (2008-06-24)
l The host software cannot be saved to the Flash of the board.
System Actions
None
Possible Causes
The Flash is faulty.
Handling Procedure
Step 1 Reset the board, and then check whether the alarm is cleared.
Y=> The alarm handling is complete.
N => Go to step2.
Step 2 Replace the faulty board, and then check whether the alarm is cleared.
Y => The alarm is not cleared. Please contact Motorola for technical support.
N => The alarm is cleared. The alarm handling is complete.
----End

Description
This alarm is reported when E1 signal is not detected in the port.
Attribute

20081 Major Fault
Parameters
ID Name Meaning
located.
4 Port No. This parameter indicates the number of the port.
(2008-06-24) 1-183
Impact on System
The services over this port are interrupted.
System Actions
Possible Causes
l The DB44 connector of the E1 cable, which is connected to the panel of the interface board,
is not securely inserted.
l The connection of the transmitting cables are wrong.
l The receiving circuit of the local equipment is faulty.
l The transmitting circuit of the peer equipment is faulty.
l The transmitting port is faulty.
Handling Procedure
Step 1 Secure the DB44 connector of the E1 cable at the local and peer ends, and then check whether
Step 2 Check whether the cables between the local and peer equipment are disconnected, such as the
reverse connection of TX/RX cable, cross-connected cable.
Y => The cables are disconnected. Go to step 3.
N => All the cables are correctly connected. Go to step 4.
Step 3 Correctly connect the cables between the local and peer equipment, and then check whether the
alarm is cleared.
Step 4 Reset the local board and wait until the board is successfully restarted. Check whether the alarm
is cleared.
Step 5 Contact the maintenance personnel at the peer end to perform the loop back of the E1 toward
the local equipment. Check whether the alarm is cleared.
Y => The alarm is cleared. This indicates that the peer board is faulty. Ask the maintenance
personnel at the peer end to solve the problem. The alarm handling is complete.
Step 6 Contact the maintenance personnel of the transmission network to check whether the
transmission network is faulty.
1-184 (2008-06-24)
Y => The transmission network is faulty. Ask the transmission maintenance personnel to solve
the problem. The alarm handling is complete.
N => The transmission network is in good condition. Go to step 7.
Step 7 Replace the local board and wait until the board is successfully restarted. Check whether the
alarm is cleared.
----End

Description
This alarm is reported when the port is in out-of-frame state.
Attribute
20082 Major Fault
Parameters
ID Name Meaning
located.
Impact on System
The services on the port are disrupted.
System Actions
None.
Possible Causes
l The frame format between the local and peer ends is inconsistent over this link.
l The transmission link is poor in quality or the transmission equipment is faulty.
(2008-06-24) 1-185
Handling Procedure
N=> Go to step 2.
Step 2 Check whether the frame format between the local and peer ends is inconsistent over this link.
Y => The frame format is inconsistent. Go to step 3.
N => The frame format is consistent. Go to step 4.
Step 3 Keep the frame format between the local and peer equipment in consistency over this link.
Step 4 Ask the transmission engineer to check whether the transmission network is abnormal.
Y => The transmission network is abnormal. Ask the transmission engineer to solve the problem.
The alarm handling is complete.
N => The transmission network is in good condition. Please contact Motorola for technical
support.
----End

Description
This alarm is reported when the peer end is in out-of-frame state or signal loss state.
Attribute

20083 Major Fault
Parameters
ID Name Meaning
located.
1-186 (2008-06-24)
ID Name Meaning
Impact on System
The services over the port are interrupted.
System Actions
None.
Possible Causes
l The DB44 connector connecting the E1 cable line to the interface board is not securely
inserted.
l The frame format at two ends of the link is inconsistent.
l The local equipment fails to send the E1 signals.
l The peer equipment fails to receive the E1 signals.
l The transmission link is unidirectional.
Handling Procedure
N=> Go to step 2.
The parent alarm and the child alarm are respectively reported from the interface board of two
subracks configured over the Ater interface.
Step 2 Insert securely the DB44 connector (the connector connecting the E1 cable with the panel of the
interface board) of the E1 at the local and peer ends, and then check whether the alarm is cleared.
Step 3 Check whether the frame formats on both ends of the link are consistent.
Y => The formats are consistent. Go to step 5.
N => The formats are inconsistent. Go to step 4.
Step 4 Adjust the local frame format to the peer one and check whether the alarm is cleared.
(2008-06-24) 1-187
Step 5 Reset the local board and wait until the new board is successfully restarted. Check whether the
alarm is cleared.
Step 6 Ask the peer maintenance engineers to connect together the two ends of the E1 link and to
perform a loopback to the local equipment, and then check whether the alarm is cleared.
Y => The alarm is cleared. The peer board is faulty. Ask the peer maintenance engineers to
rectify the fault. The alarm handling is complete.
Step 7 Ask maintenance engineers to check whether the transmission link fails.
Y => The transmission link fails. Ask maintenance engineers to rectify the fault. The alarm
N => The transmission link is functional. Go to step 8.
Step 8 Replace the local board and check whether the alarm is cleared.
----End

Description
This alarm is reported when the local end receives an AIS indication that in the port are all 1
signals.
Attribute
20084 Major Fault
Parameters
ID Name Meaning
located.
3 CPU No. This parameter indicates the Number of the CPU that reports the alarm.
1-188 (2008-06-24)
Impact on System
The services over the port are interrupted.
System Actions
None.
Possible Causes
l The tributary at the peer end is in inter-board loop mode.
l The transmission equipment is in well communication with the local equipment, but it
obtains no signal input from the peer equipment.
Handling Procedure
Step 1 Check whether the link on the peer board is operating under inter-board loopback mode.
Y => The link on the peer board is operating under inter-board loopback mode. Go to step 2.
N => The link on the peer board is not operating under inter-board loopback mode. Go to step
3.
Step 2 Stop the inter-board loopback mode of the link on the peer board to have the link operated
normally. Check whether the alarm is cleared.
Step 3 Check whether the peer board is correctly connected with the transmission equipment.
Y => The connection is correct. Please contact Motorola for technical support.
N => The connection is wrong. Go to step 4.
Step 4 Correctly connect the peer board with the transmission equipment, and then check whether the
alarm is cleared.
----End
1.115 20085 Loss of E1 Multiframes (LOM)

Description
This alarm is reported when the port is in out-of-multi-frame state.
Attribute

20085 Major Fault
(2008-06-24) 1-189
Parameters
ID Name Meaning
located.
Impact on System
The service quality drops.
System Actions
None.
Possible Causes
l The local link may be configured to CRC4 multiframe format but the peer link may be
configured to dual-frame format.
Handling Procedure
Step 1 Check whether peer link is configured to dual-frame format.
Y => Go to step 2.
N => Go to step 3.
Step 2 Configure the frame format of peer equipment to CRC4 multiframe format. Check whether the
alarm is cleared.
Step 3 Contact the transmission engineer to check whether the transmission network is abnormal.
Y => The transmission network is abnormal. Ask the transmission engineer to solve the problem.
N => The transmission network is in good condition. Please contact Motorola for technical
support.
----End
1.116 20086 E1 Link Loopback

Description
This alarm is reported when a port of the local equipment is in loopback mode.
1-190 (2008-06-24)
Attribute
20086 Warning Fault
Parameters
ID Name Meaning
located.
5 l 1=No loop
l 2=Payload loop
l 3=Remote loop
l 5=Local loop
l 7=Single channel loop
Impact on System
l If the local equipment is in loopback mode, the AIS alarm occurs in the remote equipment.
l The services on the port are disrupted.
System Actions
None.
Possible Causes
The E1 link of the local equipment is manually set to one loopback mode at will.
Handling Procedure
Step 1 [#1515] Check whether a loopback test is performed on the link[/#1515].
Y => This is a normal symptom. The alarm handling is complete.
N => Go to step 2.
Step 2 [#1516] Stop the loopback of the alarm link through the LMT [/#1516] to make the alarm link
operate in normal state, and then check whether the alarm is cleared.
(2008-06-24) 1-191
----End
1.117 20087 High BER over the E1 Link

Description
l The bit error rate exceeds 5E-4 for one minute.

l The bit error rate is less than 1E-6 for one minute.
Attribute

20087 Major Fault
Parameters
ID Name Meaning
located.
5 l 0=NO ERR
l 1=CRC
l 2 =FAS
l 3 =CRC and FAS
l 4=Code Violation
l 5 =Code Violation and CRC
l 6=Code Violation and FAS
l 7=Code Violation and CRC and FAS
Impact on System
The quality of associated services degrades.
1-192 (2008-06-24)
System Actions
None.
Possible Causes
l The line coding schemes on the two sides are different.
l The subrack is not properly grounded.
l The shielding layer of the cable between the BSC and the transmission equipment is
damaged.
l The transmission network is faulty.
Handling Procedure
Step 1 If the Code Violation is faulty, check whether the line coding schemes on the two sides are the
same.
Y => Go to step 3.
N => Go to step 2.
Step 2 Set the line coding schemes to be the same, then check whether the alarm is cleared.
Step 3 Check whether the subrack fails to be securely grounded.

Y => Go to step 4.
N => Go to step 5.
Step 4 Connect securely the grounding cable and check whether the alarm is cleared.
Step 5 Check whether the shielding layer of the cable connecting the BSC to the transmission equipment
is damaged.
Y => Go to step 6.
N => Go to step 7.
Step 6 Replace the damaged cable and check whether the alarm is cleared.
Step 7 Ask the maintenance engineers to check whether the transmission network fails.
Y => The transmission network fails. Ask the maintenance engineers to rectify the fault. The
alarm handling is complete.
N => The transmission network is functional. Please contact Motorola for technical support.
----End
(2008-06-24) 1-193
1.118 20089 Excessive Loss of E1 Signals in an Hour

Description
This alarm is reported in following condition:
l The LOS exceeds 40 times within one hour

l No LOS is detected within ten minutes
Attribute

20089 Major Fault
Parameters
ID Name Meaning
located.
5 This parameter indicates the LOS intermittent times.
Impact on System
System Actions
None.
Possible Causes
l The subrack fails to be securely grounded.
l The shielding layer of the cable connecting the BSC to the transmission equipment is
damaged.
l The transmission fails.
1-194 (2008-06-24)
Handling Procedure
Y => It fails to be securely grounded. Go to step 2.
N => It is securely grounded. Go to step 3.
is damaged.
Y => The shielding layer is damaged. Go to step 4.
N => The shielding layer is not damaged. Go to step 5.
Step 5 Ask maintenance engineers to check whether the transmission network fails.
Y => The transmission network fails. Ask maintenance engineers to rectify the fault. The alarm
----End
1.119 20090 Excessive E1 Synchronization Failures in an

Hour
Description
l The LOF exceeds 40 times within one hour.

l No LOF is detected within ten minutes.
Attribute
20090 Major Fault
Parameters
ID Name Meaning
located.
(2008-06-24) 1-195
ID Name Meaning
3 CPU No. This parameter indicates the umber of the CPU that reports the alarm.
5 This parameter indicates the frame out-of-sync intermittent times.
Impact on System
System Actions
None.
Possible Causes
l The subrack fails to be securely grounded.
l The shielding layer of the cable connecting the BSC to the transmission equipment is
damaged.
l The transmission fails.
Handling Procedure
Y => It fails to be securely grounded. Go to step 2.
N => It is securely grounded. Go to step 3.
is damaged.
Y => The shielding layer is damaged. Go to step 4.
N => The shielding layer is not damaged. Go to step 5.
Step 5 Ask maintenance engineers to check whether the transmission network fails.
Y => The transmission network fails. Ask maintenance engineers to rectify the fault. The alarm
----End
1-196 (2008-06-24)
1.120 20091 E1 Excessive Peer End Alarms Per Hour

Description
l The RAI exceeds 40 times within one hour.

l No RAI is detected within ten minutes.
Attribute

20091 Major Fault
Parameters
ID Name Meaning
located.
5 This parameter indicates the remote alarm intermittent times.
Impact on System
System Actions
None.
Possible Causes
l The grounding of the subrack is incorrect.
damaged.
l The transport network is faulty.
(2008-06-24) 1-197
Handling Procedure
Step 1 Check whether the grounding of the subrack is correct.
Y => The grounding is incorrect. Go to step 2.
N => The grounding is correct. Go to step 3.
Step 2 Connect the grounding cable correctly, and then check whether the alarm is cleared.
N => The alarm persists. Go to 3.
Step 3 Check whether the shielding layer of the cable between the BSC and the transmission equipment
is damaged.
Y => The shielding layer of the cable is damaged. Go to step 4.
N => The shielding layer of the cable is intact. Go to step 5.
Step 5 Ask the transport network maintenance personnel to check whether the transport network is
faulty.
Y => The transport network is faulty. Ask the transport network maintenance personnel to handle
the fault. The alarm handling is complete.
N => The transport network is normal. Please contact Motorola for technical support.
----End
1.121 20092 E1 Excessive Bit Error Rate Per Hour

Description
l The bit error rate exceeds 1E-5 for one hour.

l The bit error rate is less than 1E-5 for fifteen minutes.
Attribute
20092 Warning Fault
Parameters
ID Name Meaning
located.
1-198 (2008-06-24)
ID Name Meaning
5 l 0=NO ERR
l 1=CRC
l 2=FAS
l 3=CRC and FAS
l 4=Code Violation
l 5=Code Violation and CRC
l 6=Code Violation and FAS
l 7=Code Violation and CRC and FAS
Impact on System
System Actions
None.
Possible Causes
l The line coding is different.
l The subrack is not properly grounded.
damaged.
l The transmission network is faulty.
Handling Procedure
Step 1 If the Code Violation is faulty, check whether the line coding schemes on the two sides are the
same.
Y => Go to step 3.
N => Go to step 2.
Step 2 Set the line coding schemes to be the same, then check whether the alarm is cleared.

Y => Go to step 4.
(2008-06-24) 1-199
N => Go to step 5.
is damaged.
Y => Go to step 6.
N => Go to step 7.
Step 7 Ask the maintenance engineers to check whether the transmission network fails.
Y => The transmission network fails. Ask the maintenance engineers to rectify the fault. The
----End
1.122 20093 E1 Excessive Slip Frames Per Hour

Description
l The number of slip frames exceeds 288 within one hour.
l No slip frames are detected within 10 minutes.
Attribute
20093 Warning Fault
Parameters
ID Name Meaning
located.
1-200 (2008-06-24)
ID Name Meaning
5 This parameter indicates the number of slip frames.
Impact on System
System Actions
None.
Possible Causes
l The clocks at the two ends of the transport cable are inconsistent.
l The transport cable is in poor conditions.
Handling Procedure
Step 1 Check whether the clock-specific configuration on the BSC is correct.
Y => The configuration is incorrect. Go to step 2.
N => The configuration is correct. Go to step 3.
Step 2 Correct the configuration, and then check whether the alarm is cleared.
Step 3 Ask the transport network maintenance personnel to check whether the transport equipment or
cable is faulty.
Y => The transmission link is normal. Please contact Motorola for technical support.
N => The transmission link is abnormal. Ask the transmission engineer to solve the problem.
----End
1.123 20113 Faulty GE Link on the Sub-board of GXPUx

Description
This alarm is reported when the GE link of the pinch board is disconnected.
Attribute

20113 Major Fault
(2008-06-24) 1-201
Parameters
ID Name Meaning
2 Slot No. This parameter indicates the number of the slot


4 CPU No. that corresponds to the GE port This parameter indicates the CPU No.
corresponding GE port.
Impact on System
The service on the faulty link CPU is interrupted.
System Actions
Possible Causes
l The CPU which corresponds to the faulty link is reset.
l The sub-board where the faulty link CPU resides is not securely inserted.
l The sub-boar where the faulty link CPU resides is out-of-position.
Handling Procedure
N=> Go to step 2.
Step 2 Check whether the alarm is cleared within 10 minutes.

Y => The alarm is cleared. The alarm is caused by the restoration of the CPU. The alarm handling
is complete.
1-202 (2008-06-24)
Step 3 Remove the GXPUx and insert tightly the sub-board where the faulty link CPU resides. Then
reinstall the GXPUx and wait until the new board is successfully restarted. Check whether the
alarm is cleared.
Step 4 Remove the GXPUx and replace the sub-board where the faulty link CPU resides. Then reinstall
the GXPUx and wait until the new board is successfully restarted. Check whether the alarm is
cleared.
Step 5 Replace the GXPUx and wait until the new board is successfully restarted. Check whether the
alarm is cleared.
----End

Description
This alarm is reported when HiGig link between boards is disconnected.
Attribute

20114 Major Fault
Parameters
ID Name Meaning
located.
4 HIG Link No. This parameter indicates the disconnected inter-board HiGig link No.
Impact on System
l If only one or two HIGs fail, the service between the active and standby GSCUs decreases.
(2008-06-24) 1-203
l If three HIGs fail, the standby GSCU is unavailable for service, and the switch capability
of the system decreases.
System Actions
The service carried by the faulty HIG is passed to other normal HIGs.
Possible Causes
l The peer board is reset.
l The local or peer board is not securely installed.
l The local board is faulty.
l The backplane (including slots and circuit is faulty.
Handling Procedure
Step 1 Check whether the peer board is reset.
Y => The peer board is reset. This alarm is caused by the restoration of the peer board. The alarm
N => The peer board is not reset. Go to step 2.
Step 2 Secure the installation of the two GSCUs, and then check whether the alarm is cleared.
Step 3 Reset the standby board and wait until the board is successfully restarted. Check whether the
alarm is cleared after the standby board restarts.
Step 4 Replace the local board and wait until the new board is successfully restarted. Check whether
Step 5 Switch the active board into standby state and wait until the standby board is successfully
restarted. Check whether the alarm is cleared.
Step 6 Replace the new standby board and wait until the new board is successfully restarted. Check
----End
1-204 (2008-06-24)
1.125 20115 Intra-Board HIG Link Faulty

Description
This alarm is reported when HiGig link in the board is disconnected.
Attribute
Parameters
ID Name Meaning
located.
4 HIG Link No. This parameter indicates the disconnected intra-board HiGig link No.
Impact on System
Partial services may stop.
System Actions
l Handling of the active board in the active/standby operation mode: Reset the board.
l Handling of the standby board in the active/standby operation mode: Close all GE port,
and can not switchover forever.
Possible Causes
Handling Procedure
Step 1 The system automatically reset the board. Wait until the board is successfully restarted, and then
check whether the alarm is cleared.
alarm is cleared.
(2008-06-24) 1-205

----End
1.126 20116 Inter-Board HIG Trunk Communication Failure

Description
This alarm is reported when the CPU communication with the peer GSCU board fails.
Attribute
20116 Major Fault
Parameters
ID Name Meaning
located.
2 Subrack No. This parameter indicates the number of the slot where the board is located.
3 Slot No. This parameter indicates the number of the CPU that reports the alarm.
Impact on System
The standby GSCU becomes unavailable. The performance of the system degrades.
System Actions
Inhabit all external GE ports on the standby board.
Possible Causes
l The heartbeat packets between active and standby switching network boards cannot be
processed due to CPU busy.
l The peer board is faulty.
l The backplane (including slots and circuit) is faulty.
Handling Procedure
1-206 (2008-06-24)
N=> Go to step 2.
The three alarms have the same Subrack No. and Slot No. in the alarm location information.
This alarm occurs when 20114 Inter-Board HIG Link Faulty occurs on HIG link 6, HIG link 7,
and HIG link 8 at the same time.
The four alarms have the same Subrack No. and Slot No. in the alarm location information.

Y => The peer board is reset. The alarm is caused by the restoration of the peer board. The alarm
Step 3 Secure the installation of the local board and the peer board, and then check whether the alarm
is cleared.
Step 4 Reset the standby board and wait until the board is successfully restarted. Check whether the
alarm is cleared.
alarm is cleared.
Step 6 Switch the active board into standby state on the LMT, and then check whether the switchover
succeeds.
N => The switchover fails. Go to step 8.
Step 7 Wait until the standby board is successfully started, and then check whether the alarm is cleared.
Step 8 Reset the active board and wait until the standby board is successfully started. Check whether
Step 9 Replace the current standby board and wait until the board is successfully restarted. Check
----End
(2008-06-24) 1-207
1.127 20117 Board Fault-GE Switch Unit Failure

Description
This alarm is reported when GE switch unit is faulty.
Attribute
20117 Major Fault
Parameters
ID Name Meaning
located.
4 This parameter indicates the Chip No. which is faulty.
Impact on System
System Actions
l Handling of the active board in the active/standby operation mode: Reset the board.
l Handling of the standby board in the active/standby operation mode: Close all GE port,
and can not switchover forever.
Possible Causes
Handling Procedure
Step 1 After the board is automatically reset. Wait until the board is successfully restarted, and then
alarm is cleared.
1-208 (2008-06-24)

----End
1.128 20118 Inter-Board HIG Communication Failure

Description
This alarm is reported when no heartbeat packet is received on the HiGig link.
Attribute

20118 Major Fault
Parameters
ID Name Meaning


4 Backplane HIG Link No. (HIG Link No. This parameter indicates the disconnected
between boards) backplane HiGig link No.
Impact on System
l If only one or two HIGs fail, the service between the active and standby GSCUs decreases.
l If three HIGs fail, the standby GSCU is unavailable for service, and the switch capability
of the system decreases.
System Actions
l The service carried by the faulty HIG is passed to other normal HIGs.
l If all HIGs are fail,Inhabit all external GE ports on the standby board.
Possible Causes
(2008-06-24) 1-209
l The heartbeat packets between the active and standby switching network boards cannot be
processed when the CPU is busy.
l The backplane (including slots and circuit) is faulty.
Handling Procedure
Y => The peer board is reset. This alarm is caused by the restoration of the peer board. The alarm
Step 2 Secure the installation of the local board and the peer board, and then check whether the alarm
is cleared.
Step 3 Reset the standby board, and check whether the alarm is cleared after the standby board restarts.
alarm is cleared.
Step 5 Switch the active board into standby state on the LMT, and then check whether the switch over
succeeds.
N => The switchover fails. Go to step 7.
Step 6 Wait until the standby board is successfully started. Check whether the alarm is cleared.
Step 7 Reset the active board and wait until the standby board is successfully started. Check whether
Step 8 Replace the current standby board and wait until the board is successfully restarted. Check
----End
1-210 (2008-06-24)
1.129 20120 Broadcast packet overflow alarm

Description
This alarm is reported when the system generates broadcast storm.
Attribute
20120 Major Fault
Parameters
ID Name Meaning


4 GE link No. This parameter indicates the number of the

faulty GE link.
5 Number of the link mapping to the faulty This parameter indicates the number of the
link slot on the backplane mapping to the faulty
link, if the faulty port is a panel port, the Slot
No. is 255.
Impact on System
The loop occurs on the existing switching network.
System Actions
None
Possible Causes
Broadcast storm
Handling Procedure
Check whether the cables are securely connected.
(2008-06-24) 1-211
Y => Connect the cables according to the specifications.

----End
1.130 20121 GESW BAM GE Communication Failure

Description
The GSCU sends a heartbeat package to the BAM to determine whether the links can be used.
This alarm is reported when the heartbeat of any link is timed out.
Attribute
20121 Warning Fault
Parameters
ID Name Meaning
located.
4 BAM No. This parameter indicates the number of the faulty BAM.
Impact on System
The bandwidth between the GSCU and the BAM is reduced.
System Actions
None.
Possible Causes
External BAM:
l The Ethernet cable connect to wrong port.

l The Network adapter in BAM is disabled.
l The Ethernet cable on the panel is disconnected or in loose contact.
Internal BAM
1-212 (2008-06-24)
l The BAM or SCU is not securely inserted.

l The Network adapter in BAM is disabled.
Handling Procedure
Step 1 The troubleshooting of external BAM fault differs from the troubleshooting of built-in BAM
fault. The procedure for troubleshooting external BAM fault is as follows:
(1) Check whether the Ethernet cables that connect the BAM are connected to ports on the
panel of the GSCU.
Y => Go to step b. The alarm is cleared. The alarm handling is complete.
N => Connect the Ethernet cables properly.
(2) Check whether the Ethernet adapter on the BAM that connects to the GSCU is disabled.
Y => The Ethernet adapter is disabled. Enable the Ethernet adapter. The alarm is cleared.
N => The Ethernet adapter is not disabled. Please contact Motorola for technical support.
fault. The procedure for troubleshooting built-in BAM fault is as follows:
(1) Insert securely the GSCU and BAM, and then check whether the alarm is cleared.
N => The alarm is not cleared. Go to step b.
----End
1.131 20122 GESW BAM Trunk Communication Failure

Description
The GSCU sends a heartbeat package to the BAM to determine whether the links can be used.
This alarm is reported when the heartbeats of two links are timed out.
Attribute
20122 Warning Fault
Parameters
ID Name Meaning
located.
(2008-06-24) 1-213
ID Name Meaning
4 BAM No. This parameter indicates the number of the faulty BAM.
Impact on System
The communications between the GSCU and the BAM is disrupted.
System Actions
None.
Possible Causes
External BAM:
l The two Ethernet cables connect to wrong ports.

l The two Network adapters in BAM are disabled.
l The two Ethernet cables on the panel are disconnected or in loose contact.
Internal BAM:
l The BAM or SCU is not securely inserted.

l The two Network adapters in BAM are disabled.
Handling Procedure
fault. The procedure for troubleshooting external BAM fault is as follows:
(1) Check whether the Ethernet cables that connect the BAM are connected to ports on the
panel of the GSCU.
N => Connect the Ethernet cables properly. The alarm is cleared. The alarm handling is
complete.
Y => Go to step b.
fault. The procedure for troubleshooting built-in BAM fault is as follows:
(1) Insert securely the GSCU and BAM, and then check whether the alarm is cleared.
N => The alarm is not cleared. Go to step b.
1-214 (2008-06-24)
----End

Description
This alarm is reported when the GE link for the GSCU panel is disconnected.
Attribute

20123 Major Fault
Parameters
ID Name Meaning
is located.
located.
alarm.
4 Panel GE Link No. This parameter indicates the number of the disconnected link for the
panel. The twelve ports on the panel are numbered from 0 to 11, from
the top down. The link number maps with the number of the port on
the panel.
5 Panel GE Link No. The parameter value indicates the number of the disconnected link
for the panel. The twelve ports on the panel are numbered from 0 to
11, from the top down. The link number maps with the number of
the port on the panel.
Impact on System
l If at least one link in the trunk group is faulty, the service performance between the subracks
decreases.
l If all the links in the trunk group are faulty, the services between the subracks are disrupted.
(2008-06-24) 1-215
System Actions
None.
Possible Causes
l The Ethernet cable is faulty.
l The hardware of the local board is faulty.
Handling Procedure
Y => The peer board is reset. It is a normal symptom. The alarm is cleared after the boards are
restarted. The alarm handling is complete.
Step 2 Secure the Ethernet cables on the panel of the local and peer boards, and then check whether the
alarm is cleared.
Step 3 Replace the damaged Ethernet cable and check whether the alarm is cleared.
Step 5 Replace the peer board and wait until the board is successfully restarted. Check whether the
alarm is cleared.
----End
1.133 20124 Faulty GE Link on the Panel of XPU board

Description
This alarm is reported when the GE link for the XPU panel is disconnected.
1-216 (2008-06-24)
Attribute

20124 Major Fault
Parameters
ID Name Meaning
is located.
located.
alarm.
4 Panel GE Link No. This parameter indicates the the number of the disconnected link for
the panel. The four ports on the panel are numbered from 0 to 3, from
the panel.
5 Panel GE Link No. This parameter indicates the number of the disconnected link for the
panel. The four ports on the panel are numbered from 0 to 3, from
the panel.
Impact on System
The services that the link bears are disrupted.
System Actions
l Handling of the active board in active/standby mode: Perform switchover if the standby
board is ready for the operation.
l Handling of the standby board in active/standby mode: None.
Possible Causes
(2008-06-24) 1-217
Handling Procedure
Y => The peer board is reset. It is a normal symptom. The alarm is cleared after the boards are
restarted. The alarm handling is complete.
Step 2 Secure the Ethernet cables on the panel of the local and peer boards, and then check whether the
alarm is cleared.
alarm is cleared.
----End
1.134 20125 GESW Back Trunk Group Link Failure

Description
This alarm is reported when all the backplane links in one trunk group between the GSCU and
the service boards are disconnected.
Attribute

20125 Major Fault
Parameters
ID Name Meaning
1-218 (2008-06-24)
ID Name Meaning

4 Trunk Group No. This parameter indicates the number of the

trunk group.
5 The slot No. of transaction board in this This parameter indicates the slot No. of the
group peer service board.
Impact on System
The services between the GSCU and the service boards may be disrupted.
System Actions
None.
Possible Causes
l The local GSCU or the service board that corresponds to the trunk group is not securely
inserted.
l The service board corresponding to the trunk group is removed.
l The hardware of the board is faulty.
Handling Procedure
Step 1 Check whether a correlated parent alarm is reported.
N => Go to step 2.
This alarm is generated only when the 20128 Faulty GE Link on the Backplane alarm is reported
from both slot 6 and slot 7.
The three alarms have the same Subrack No. and Slot No. on the peer board in the alarm location
information.
Step 2 Check whether the service board which corresponds to the faulty trunk group is in position.
Y => The service board is in position. Go to step 3.
N => The service board is out of position. Insert the service board into its corresponding slot.
The alarm is cleared after its normal startup. The alarm handling is complete.
(2008-06-24) 1-219
Step 3 Check whether the service board that corresponds to the faulty trunk group is reset but is not
started.
Y => The service board is reset. It is a normal symptom. The alarm is cleared after the boards
are restarted. The alarm handling is complete.
N => The service board is not reset. Go to step 4.
Step 4 Secure the service board which corresponds to the switching board and the faulty link. Check
Step 5 Replace the service board which corresponds to the faulty trunk group and wait until the board
is successfully loaded and restarted. Check whether the alarm is cleared.
Step 6 Replace the faulty GSCU and wait until the board is successfully loaded and restarted. Check
----End
1.135 20126 GE Trunk Group Link Fault of transaction board

Description
This alarm is reported when the two links between the service board and the GSCU switching
network are disconnected.
Attribute
20126 Major Fault
Parameters
ID Name Meaning
board is located.
board is located.
the alarm.
1-220 (2008-06-24)
ID Name Meaning
4 Slot No. of one SCU This parameter indicates the slot No. of one peer SCU.
5 Slot No. of the other SCU This parameter indicates the slot No. of the other peer SCU.
Impact on System
The service between the GSCU and the faulty service board is disrupted.
System Actions
None.
Possible Causes
l Two GSCUs are out-of-position or not secured.
l Two GSCUs are reset.
l The local board is not securely inserted.
l The port for the local board is faulty.
Handling Procedure
N => Go to step 2.
This alarm is reported only when both link 0 and link 1 incur the 20129 Faulty GE Link on the
Backplane of transaction board alarm.
Step 2 Check whether at least one GSCU is in position.
Y => At least one GSCU is in position. Go to step 3.
N => Two GSCUs are out of position. This alarm is caused by the out-of-position of the peer
board. Insert the GSCU into the subrack correctly. The alarm handling is complete.
Step 3 Check whether all the GSCUs in position are reset but are not started.
Y => All the GSCUs in position are reset. The alarm is caused by the reset of the peer boards.
N => At least one GSCU is not reset. Go to step 4.
Step 4 Secure all the GSCUs in position and check whether the alarm is cleared.
(2008-06-24) 1-221
Step 5 Secure the local board and check whether the alarm is cleared.
is cleared.
alarm is cleared.
----End
1.136 20127 GESW Panel Trunk Group Link Failure

Description
This alarm is reported when all the backplane links in one trunk group between the active GSCU
and the standby GSCU are disconnected.
Attribute

20127 Major Fault
Parameters
ID Name Meaning


4 Trunk Group No. This parameter indicates the number of the

trunk group.
5 The first Panel port No. of SCU in slot 6 This parameter indicates the first panel port
No. of SCU in slot 6.
1-222 (2008-06-24)
ID Name Meaning
6 The first Panel port No. of SCU in slot 7 This parameter indicates the first panel port
No. of SCU in slot 7.
7 The second Panel port No. of SCU in slot This parameter indicates the second Panel
6 port No. of SCU in slot 6.
8 The second Panel port No. of SCU in slot This parameter indicates the second panel
7 port No. of SCU in slot 7.
Impact on System
The services between the subracks that are connected by the trunk group links may be disrupted.
System Actions
None.
Possible Causes
l The active and standby boards at the peer end are reset.
l The Ethernet cables connecting the GE ports of the GSCU panel are not inserted, are not
securely inserted, or are faulty.
l The peer active and standby boards are faulty.
l The local active and standby boards are faulty.
Handling Procedure
N => Go to step 2.
This alarm is generated only when the 20123 Faulty GE Link on the Panel of GSCU board
is reported from both slot 6 and slot 7.
The three alarms have the same Subrack No. and Slot No. on the peer board in the alarm location
information.
Step 2 Check whether all the peer GSCUs that corresponds to the faulty trunk group are out of position.
Y => All the peer GSCUs are out of position. Insert all the peer GSCUs into their corresponding
slots. The alarm is cleared after their normal startup. The alarm handling is complete.
N => At least one peer GSCU is in position. Go to step 3.
Step 3 Check whether all the peer boards that correspond to the faulty trunk group are reset but are not
started successfully.
Y => All the peer boards are reset. It is a normal symptom. The alarm is cleared after the boards
are restarted. The alarm handling is complete.
(2008-06-24) 1-223
N => At least one peer board is not reset. Go to step 4.
Step 4 Secure all the Ethernet cables on the panel of the local and peer boards, and then check whether
Step 5 Replace all the Ethernet cables, and then check whether the alarm is cleared.
Step 6 Replace the standby GSCU of the standby subrack and wait until the board is successfully
restarted. Check whether the alarm is cleared.
Step 7 Replace the standby GSCU of the active subrack and wait until the board is successfully restarted.
----End

Description
This alarm is reported when the GE link of the GSCU backplane is disconnected.
Attribute

20128 Minor Fault
Parameters
ID Name Meaning


1-224 (2008-06-24)
ID Name Meaning
4 Backplane GE link No. This parameter indicates the number of the
disconnected GE link of the GSCU
backplane.
5 The Slot No. of transaction board This parameter indicates the number of the
corresponding this link slot on the backplane corresponding to the
faulty link.
Impact on System
l If only one link in the trunk group is faulty, the service performance between the GSCU
and service boards decreases.
l If all the links in the trunk group are faulty, the services between the GSCU and the service
boards are disrupted.
System Actions
Disable the port in the trunk group until it returns to normal. During the disabled period, the
service carried by the faulty port is passed to other ports in the trunk group.
Possible Causes
l The peer board is not in position or is not secured.
l The hardware of the peer board is faulty.
l The local board is not in position or is not securely inserted.
l The hardware of the backplane is faulty.
Handling Procedure
Step 1 Check whether the peer service board is in position.
Y => The peer board is in position. Go to step 2.
N => The peer board is not in position. You can infer that the alarm is caused by the out-of-
position of the peer service board. The alarm handling is complete.
Step 2 Check whether the peer service board is reset.
Y => The peer service board is reset. You can infer that the alarm is caused by the reset of the
peer service board. The alarm handling is complete.
N => The peer service board is not reset. Go to step 3.
Step 3 Secure the peer service board and check whether the alarm is cleared.
Y => Go to step 4.
Y => Go to step 5.
(2008-06-24) 1-225

Step 5 Reset the peer service board and wait until the board is successfully restarted. Check whether
is cleared.
Step 7 Replace the peer service board and wait until the board is successfully restarted. Check whether
cleared.
----End
1.138 20129 Faulty GE Link on the Backplane of transaction

board
Description
This alarm is reported when the GE link for the backplane of the service board is disconnected.
Attribute
20129 Minor Fault
Parameters
ID Name Meaning


1-226 (2008-06-24)
ID Name Meaning
4 Backplane GE link No. This parameter indicates the number of the
disconnected GE link of the GSCU
backplane.
5 The Slot No. of GSCU corresponding this This parameter indicates the number of the
link slot for the GSCU backplane corresponding
to the faulty link.
Impact on System
l If only one link in the trunk group is faulty, the service performance between the GSCU
and service boards decreases.
l If all the links in the trunk group are faulty, the services between the GSCU and the service
boards are disrupted.
System Actions
Disable the port in the trunk group until it returns to normal. During the disabled period, the
service carried by the faulty port is passed to other ports in the trunk group.
Possible Causes
l The peer board is not in position or is not secured.
l The local board is not in position or is not securely inserted.
Handling Procedure
Step 1 Check whether the peer service board is in position.
Y => The peer board is in position. Go to step 2.
N => The peer board is not in position. You can infer that the alarm is caused by the out-of-
position of the peer service board. The alarm handling is complete.
Step 2 Check whether the peer service board is reset.
Y => The peer service board is reset. You can infer that the alarm is caused by the reset of the
peer service board. The alarm handling is complete.
N => The peer service board is not reset. Go to step 3.
Y => Go to step 4.
Y => Go to step 5.
(2008-06-24) 1-227
Step 5 Reset the peer service board and wait until the board is successfully restarted. Check whether
is cleared.
Step 7 Replace the peer service board and wait until the board is successfully restarted. Check whether
cleared.
----End
1.139 20164 Quality of GE Link on Service Board Backplane

Decrease
Description
This alarm is reported when the quality of the GE link on the backplane of the service board
decreases.
Attribute

20164 Minor Fault
Parameters
ID Name Meaning

1-228 (2008-06-24)
ID Name Meaning
4 Number of the GE link on the backplane This parameter indicates the number of the
GE link on the backplane.
5 Slot number of the GSCU mapping to this This parameter indicates the number of the
link slot for the GSCU mapping to the faulty link
on the backplane.
6 Alarm parameter This parameter indicates the alarm

parameter.
Impact on System
The service performance between the GSCU and the service board decreases.
System Actions
None
Possible Causes
l The peer board is not securely inserted.
Handling Procedure
Y => An alarm is generated. Go to step2.
Step 3 Reset the peer board. After the board is restarted successfully, check whether the alarm is cleared.
N =>The alarm is not cleared. Go to step4.
Step 4 Reset the local board. After the board is restarted successfully, check whether the alarm is
cleared.
(2008-06-24) 1-229
N => The alarm is not cleared. Go to step5.
Step 5 Replace the peer board. After the board is restarted successfully, check whether the alarm is
cleared.
Step 6 Replace the board. After the board is restarted successfully, check whether the alarm is cleared.
----End
1.140 20191 Board Faulty-Link Disconnection on the Service

Port
Description
This alarm is reported when the link of traffic network port is disconnected.
Attribute

20191 Major Fault
Parameters
ID Name Meaning
is located.
located.
4 Ethernet Port No. 0=traffic network port.
5 l 0=LINK UP
l 1=LINK DOWN
Impact on System
The services associated with the fault CPU stop.
1-230 (2008-06-24)
System Actions
l The handling procedures for different types of boards vary.
l If the GSCU is faulty, reset the GSCU.
l If the GXPUx is faulty, reset the CPU.
Possible Causes
l The sub-board of the GXPUx is not secured.
Handling Procedure
board in advance by the subrack number and slot number where the board is located.
If the GXPUx is faulty:
(1) Remove the board and secure the sub-board (No.0 and No.1 CPUs are on upper side of the
board, No.2 and No.3 CPUs are on the lower side of the board) where the faulty CPU is
located. Check whether the alarm is cleared.
N => The alarm persists. Go to step b.
(2) Replace the board and wait until the new board is successfully restarted. Check whether
N => The alarm persists. Please contact Motorola for technical.
Step 2 If the GSCU is faulty:

(1) Replace the board and wait until the new board is successfully restarted. Check whether
----End
1.141 20194 Disconnected Link Between the Ports on the

Active and Standby GSCU
Description
This alarm is reported when the link of MS network port is disconnected.
Attribute

20194 Minor Fault
(2008-06-24) 1-231
Parameters
ID Name Meaning
is located.
located.
4 Network port No. 1 indicates MS network port
5 PHY fault type 0 indicates LINK UP,1 indicates LINK DOWN
Impact on System
The communication between the active and the standby GSCUs is interrupted.
System Actions
None.
Possible Causes
l The peer GSCU is reset.
l The peer GSCU slot is empty.
l One or both GSCUs are not securely inserted.
l A GSCU is faulty.
Handling Procedure
Step 1 Check whether the peer GSCU is in position.
Y => The peer GSCU is in position. Go to step 2.
N => The peer GSCU is not in position. The fault is caused by the empty slot and the alarm
Step 2 Check whether the peer GSCU is reset.
Y => The peer GSCU is reset. The fault is caused by the resetting, and the alarm handling is
complete.
N => The peer GSCU is not reset. Go to step 3.
Step 3 Insert securely the peer GSCU and check whether the alarm is cleared.
Step 4 Insert securely the local GSCU and check whether the alarm is cleared.
1-232 (2008-06-24)
Step 5 Reset the standby GSCU and wait until the board is successfully restarted. Check whether the
alarm is cleared.
Step 6 Reset the active GSCU and wait until the new board is successfully restarted. Check whether
Step 7 Replace the standby GSCU and wait until the new board is successfully restarted. Check whether
Step 8 Replace the active GSCU and wait until the new board is successfully restarted. Check whether
----End

Description
This alarm is reported when the clock at the optical interface is lost.
Attribute

20221 Major Fault
Parameters
ID Name Meaning
board is located.
located.
alarm.
(2008-06-24) 1-233
ID Name Meaning
4 Optical Interface No. This parameter indicates the optical interface No.
Impact on System
The services on this optical faulty are interrupted.
System Actions
l Handling of the board in the Independent operation mode:None.
Possible Causes
Handling Procedure
Step 1 Reset the board, and then check whether the alarm is cleared after the board restarts.
Step 2 Replace the board and wait for the startup of the board, and then check whether the alarm is
cleared.
----End

Description
This alarm is reported when the signal at the optical interface is lost.
Attribute
20222 Major Fault
1-234 (2008-06-24)
Parameters
ID Name Meaning
board is located.
located.
alarm.
Impact on System
The services carried on the affected optical cable stop.
System Actions
Possible Causes
l The optical cable is not connected correctly.
l The Rx and Tx ends of the optical cable are disconnected.
l The optical interface on the peer board is faulty.
l The optical interface on the local board is faulty.
l The transport link is faulty.
Handling Procedure
Step 1 Connect correctly the optical cable between the local board and the peer board, and then check
Step 2 Check whether the cables between the local and peer equipment are disconnected, such as the
reverse connection of TX/RX cable, cross-connected cable.
Y => The local and peer equipment are disconnected. Go to step 3.
N => All the links are faulty. Go to step 4.
Step 3 Connect the local equipment and peer equipment correctly, and then check whether the alarm
is cleared.
(2008-06-24) 1-235
Step 4 Reset the local board, and check whether the alarm is cleared after the local board restarts.
Step 5 Ask the peer-site maintenance personnel to perform the loop back of the peer equipment to the
local end, and then check whether the alarm is cleared.
Y => The alarm is cleared. The peer board is faulty. The alarm handling is complete.
Step 6 Check whether the transport link is faulty.

Y => The transport link is faulty. Ask associated maintenance personnel to resolve the fault.
N => The transport link is normal. Go to step 7.
Step 7 Replace the local board and wait for the startup of the board, and then check whether the alarm
is cleared.
----End
1.144 20223 Loss of Received Signal Frames on the Optical

Port (RLOF)
Description
This alarm is reported when the frame of the received signal at optical interface is lost.
Attribute
20223 Major Fault
Parameters
ID Name Meaning
board is located.
located.
alarm.
1-236 (2008-06-24)
ID Name Meaning
Impact on System
System Actions
Possible Causes
Handling Procedure
N=> Go to step 2.
Step 3 Ask the peer-site maintenance personnel to perform the loop back of the peer equipment to local
end, and then check whether the alarm is cleared.
Step 4 Ask the transport link maintenance personnel to check whether the transport link is faulty.
Y => The transport link is faulty. Ask the transport link maintenance personnel to handle the
fault. The alarm handling is complete.
is cleared.
(2008-06-24) 1-237
----End
1.145 20224 Out-of-Synchronization of Received Signal

Frames on the Optical Port (ROOF)
Description
This alarm is reported when the frame of the received signal at optical interface is out of sync.
Attribute
20224 Major Fault
Parameters
ID Name Meaning
board is located.
located.
alarm.
Impact on System
System Actions
Possible Causes
1-238 (2008-06-24)
Handling Procedure
Step 2 Ask the peer-site maintenance personnel to perform the loop back of the peer equipment to the
local end, and then check whether the alarm is cleared.
Y => The transport link is faulty. Ask the transport link maintenance personnel to handle the
fault. The alarm handling is complete.
is cleared.
----End
1.146 20225 Mismatch of Trace Byte of the Regenerator

Section on the Optical Port (RTIM)
Description
This alarm is reported when the trace byte J0 of regenerator section is mismatched. J0 byte is
used to repeatedly send the identifier of section access point, so the receiving end can confirm
the continuous connection to the transmitting end.
Attribute
20225 Major Fault
Parameters
ID Name Meaning
board is located.
located.
(2008-06-24) 1-239
ID Name Meaning
alarm.
Impact on System
None.
System Actions
None.
Possible Causes
The J0 byte received at the local end is inconsistent with what is expected.
Handling Procedure
Set the J0 byte at the local end to the same value with that transmitted from the peer board. Check
----End

Description
This alarm is reported when the bit error rate of the regenerator section of optical interface
exceeds the threshold. This threshold is higher than that of the signal of regenerator section at
optical interface worsened alarm.
Attribute
20226 Major Fault
Parameters
ID Name Meaning
board is located.
1-240 (2008-06-24)
ID Name Meaning
located.
alarm.
Impact on System
The quality of the services carried on the affected optical cable degrades, or the services stop.
System Actions
l

l
Possible Causes
Handling Procedure
Step 1 Contact the maintenance engineers who are responsible for maintaining the transmission
network and confirm with them whether the transmission network has problems.
Y => The transmission network has problem. Ask the maintenance engineers to solve the
problems. The alarm handling is complete.
N => The transmission network is working normally. Go to step 2.
Step 2 Replace the faulty board on the BSC side. Wait until the new board starts up and loads data
successfully, check whether the alarm is cleared.
----End
(2008-06-24) 1-241
1.148 20227 Regenerator Section Signal Deteriorated (RSD)

Description
This alarm is reported when the bit error rate of the regenerator section at optical interface
exceeds the threshold. This threshold is lower than that of the signal of regenerator section at
optical interface failed alarm.
Attribute
20227 Major Fault
Parameters
ID Name Meaning
board is located.
located.
alarm.
Impact on System
The service quality of the optical fiber that generates an alarm becomes poorer or even
interrupted.
System Actions
None.
Possible Causes
l The transmission quality is poor.
l The optical port is faulty.
Handling Procedure
1-242 (2008-06-24)
N=> Go to step 2.
Step 2 Contact the maintenance engineers who are responsible for maintaining the transmission
network and confirm with them whether the transmission network has problems.
Y => The transmission network has problem. Ask the maintenance engineers to solve the
problems. The alarm handling is complete.
N => The transmission network is working normally. Go to step 3.
Step 3 Replace the faulty board on the BSC side. Wait until the new board starts up and loads data
----End
1.149 20228 Multiplex Section Alarm Indication Signal

(MAIS)
Description
This alarm is reported when the multiplex section at optical interface receives the alarm
indication signal.
Attribute
20228 Major Fault
Parameters
ID Name Meaning
board is located.
located.
alarm.
(2008-06-24) 1-243
Impact on System
System Actions
Possible Causes
No signal is detected between the peer equipment (BTS or BSC) and the transmission equipment,
whereas the transmission equipment is normally connected with the local equipment.
Handling Procedure
Refer to the maintenance manual for the peer equipment to handle the fault, and then check
----End
1.150 20229 Multiplex Section Remote Defect Indication

(MRDI)
Description
Multiplex section remote defect indication at optical interface
Attribute
20229 Major Fault
Parameters
ID Name Meaning
1 Subrack No. Number of the subrack where the board is located
2 Slot No. Number of the slot where the board is located.
3 CPU No. Number of the CPU that reports the alarm
1-244 (2008-06-24)
ID Name Meaning
4 Optical Interface No. Optical interface No.
Impact on System
System Actions
l Handling of the active board in the active/standby operation mode
l Perform the switchover if the standby is ready for the operation.
l Handling of the standby board in the active/standby operation mode
l None.
l Handling of the board in the Independent operation mode.
l None.
Possible Causes
l The Rx end of the peer equipment is faulty.
l The transport link is operational in only one direction.
Handling Procedure
N=> Go to step 2.
Step 2 Check whether an alarm such as loss of signals, loss of frames, and alarm indication signal is
associated with the peer equipment.
Y => The alarm exists. Go to step 3.
N => The alarm does not exist.Please contact Motorola for technical support.
Step 3 Ask the peer-site maintenance personnel to clear the alarm on the peer equipment, and then
check whether the alarm on the local equipment is cleared.
----End
(2008-06-24) 1-245
1.151 20230 Loopback on the Optical Port

Description
This alarm is reported when the local equipment is in loopback mode, which means the services
at this optical interface are disabled.
Attribute
20230 Minor Fault
Parameters
ID Name Meaning
board is located.
located.
alarm.
5 l 0=No loop
l 1=regenerator section line loop
l 2= regenerator section system loop
Impact on System
System Actions
None.
Possible Causes
Manually set the local link to any optical port loopback mode.
Handling Procedure
Step 1 Check whether the optical port loopback test is being performed.
1-246 (2008-06-24)
Y => The optical port is normal.No handling is required.

N => Go to step 2.
Step 2 Stop the loopback of the alarm port to have the port operated in normal state. Check whether
----End
1.152 20231 Administration Unit Alarm Indication Signal

(AUAIS)
Description
This alarm is reported when the administration unit receives alarm indication.
Attribute
20231 Major Fault
Parameters
ID Name Meaning
board is located.
located.
alarm.
5 High Order Path No. This parameter indicates the High Order Path No.
Impact on System
System Actions
(2008-06-24) 1-247

l
Possible Causes
Handling Procedure
----End
1.153 20232 Loss of Administration Unit Pointer (AULOP)

Description
The optical interface cannot identity the pointer in SDH frame.
Attribute
20232 Major Fault
Parameters
ID Name Meaning
board is located.
located.
alarm.
1-248 (2008-06-24)
Impact on System
System Actions
Possible Causes
l The traffic-specific parameters are incorrectly configured on the transport equipment.
Handling Procedure
Step 1 Ask the transport equipment maintenance personnel to check whether the traffic-specific
parameters are correctly configured.
Y => Go to step 2.
N => Ask the transport equipment maintenance personnel to reconfigure the parameters. The
Step 3 Replace the peer board and wait until the new board is successfully restarted. Check whether
----End
1.154 20233 Service Unequipped on the High-Order Path of

the Optical Port (HPUNEQ)
Description
This parameter indicates the higher order path is unequipped with service.
Attribute
20233 Major Fault
(2008-06-24) 1-249
Parameters
ID Name Meaning
board is located.
located.
alarm.
Impact on System
System Actions
Possible Causes
The higher order path signal flag (byte C2) configured on the peer board is set to 0.
Handling Procedure
Set the RX C2 byte on the peer board to 0x02, and then check whether the alarm is cleared.
----End
1.155 20234 Trace Flag Mismatch on the High-Order Path of

the Optical Port (HPTIM)
Description
This alarm is reported when the higher order path trace byte J1 is mismatched. Byte J1 is used
to repeatedly send the identifier of higher order path access point, so the receiving end can
confirm the continuous connection to the transmitting end.
1-250 (2008-06-24)
Attribute
20234 Major Fault
Parameters
ID Name Meaning
board is located.
located.
alarm.
Impact on System
None.
System Actions
None.
Possible Causes
Handling Procedure
----End
(2008-06-24) 1-251
1.156 20235 High-Order Path Signal Label Byte Mismatch

(HPSLM)
Description
This alarm is reported when the higher order path signal label byte C2 is mismatched.
Attribute

20235 Major Fault
Parameters
ID Name Meaning
board is located.
located.
alarm.
Impact on System
System Actions
Possible Causes
The higher order path signal label byte (C2) configured on the peer board is inconsistent with
that configured on the local board.
1-252 (2008-06-24)
Handling Procedure
On the peer board, set byte C2 to 0x02, and then check whether the alarm is cleared.
----End

Description
The bit error rate of the higher order path signal exceeds the threshold. This threshold is higher
than that of the higher order path signal worsened alarm.
Attribute
20236 Major Fault
Parameters
ID Name Meaning
5 High Order Path No. High Order Path No.
Impact on System
The quality of the services carried on the affected optical cable degrade, or the services stop.
System Actions
l None.
l None.
(2008-06-24) 1-253
Possible Causes
Handling Procedure
Step 1 Check whether the transport link is faulty.
Y => The transport link is faulty. Ask associated maintenance personnel to resolve the fault.
alarm is cleared.
----End
1.158 20237 High-Order Path Signal Deteriorated (HPSD)

Description
The bit error rate of the higher order path signal exceeds the threshold. This threshold is lower
than that of the higher order path signal failed alarm.
Attribute
20237 Major Fault
Parameters
ID Name Meaning
Impact on System
The quality of the services carried on the affected optical cable degrade, or the services stop.
1-254 (2008-06-24)
System Actions
None.
Possible Causes
Handling Procedure
N=> Go to step 2.
Y => Ask the transport link maintenance personnel to handle the fault. The alarm handling is
complete.
N => Go to step 3.
alarm is cleared.
----End
1.159 20238 Remote Defect Indication on the High-Order

Path of the Optical Port (HPRDI)
Description
Higher order path remote defect indication at the receiver side of optical interface
Attribute
20238 Major Fault
(2008-06-24) 1-255
Parameters
ID Name Meaning
Impact on System
The service carried on the faulty optical fiber is interrupted.
System Actions
l None.
l None.
Possible Causes
Any of the following alarms exist on the peer equipment: 20232 Loss of Administration Unit
Pointer (AULOP),20231 Administration Unit Alarm Indication Signal (AUAIS), 20235 High-
Order Path Signal Label Byte Mismatch (HPSLM), or 20234 Trace Flag Mismatch on the High-
Order Path of the Optical Port (HPTIM).
Handling Procedure
Step 1 Check whether any of the following alarms exist on the peer equipment: 1.153 20232 Loss of
Administration Unit Pointer (AULOP),1.152 20231 Administration Unit Alarm Indication
Signal (AUAIS), 1.156 20235 High-Order Path Signal Label Byte Mismatch (HPSLM), or
1.155 20234 Trace Flag Mismatch on the High-Order Path of the Optical Port (HPTIM).
Y => Go to step 2.
Step 2 Ask the maintenance personnel at the peer end to clear the alarms there, and then check whether
the alarm on the local equipment is cleared.
----End
1-256 (2008-06-24)
1.160 20239 Loss of Tributary Unit Multi-frames (TULOM)

Description
This alarm is reported when the tributary unit generates loss of Multiframe.
Attribute
20239 Major Fault
Parameters
ID Name Meaning
board is located.
located.
alarm.
Impact on System
The service carried on the faulty optical fiber is interrupted.
System Actions
None.
Possible Causes
l The transmission link is in poor condition.
Handling Procedure
Step 1 Check whether there is any alarm associated with the Optical Port, for example, 1.147 20226
Regenerator Section Signal Failure (RSF), 1.148 20227 Regenerator Section Signal
(2008-06-24) 1-257
Deteriorated (RSD), 1.157 20236 High-Order Path Signal Failure (HPSF), and 1.158 20237
High-Order Path Signal Deteriorated (HPSD).
Y => An alarm exists. Go to step 2.
N => No alarm exists. Go to step 3.
Step 2 Clear the BER alarm according to its relevant handling suggestions, and then check whether the
multi-frame loss alarm is cleared.
Step 4 Replace the peer board and wait until the new board is successfully restarted. Check whether
----End
1.161 20240 Tributary Unit Alarm Indication Signal (TUAIS)

Description
This alarm is reported when the tributary unit generates alarm indication signal.
Attribute
20240 Major Fault
Parameters
ID Name Meaning
is located.
located.
alarm.
4 Tributary Unit No. This parameter indicates the tributary unit No.of the optical port.
1-258 (2008-06-24)
Impact on System
Services carried on the affected tributary unit stop.
System Actions
Possible Causes
Handling Procedure
----End
1.162 20241 Loss of Tributary Unit Pointer (TULOP)

Description
This alarm is reported when the pointer of the tributary unit at optical port is not identified by
BSC.
Attribute

20241 Major Fault
Parameters
ID Name Meaning
1 Subrack No. This parameter is indicates the number of the subrack where the board
is located.
2 Slot No. This parameter is indicates the number of the slot where the board is
located.
(2008-06-24) 1-259
ID Name Meaning
3 CPU No. This parameter is indicates the number of the CPU that reports the
alarm.
Impact on System
Services carried on the affected tributary unit stop.
System Actions
Possible Causes
l The service configuration for the transmission device is wrong.
l The the Optical Port on the local board is faulty.
l The the Optical Port on the peer board is faulty.
Handling Procedure
Step 1 Ask the transmission engineer to check whether the service configuration for the transmission
service is correct.
N => Ask the engineer to modify the service configuration. The alarm handling is complete.
Y => Go to step 2.
alarm is cleared.
alarm is cleared.
----End
1.163 20242 Service Unequipped on the Lower-Order Path

of the Optical Port (LPUNEQ)
Description
This alarm is reported when the lower order path is unequipped with service.
1-260 (2008-06-24)
Attribute
20242 Major Fault
Parameters
ID Name Meaning
is located.
located.
alarm.
Impact on System
The service over this path might be interrupted.
System Actions
Possible Causes
The indication flag V5 byte on this lower-order path of the peer board is set to 0.
Handling Procedure
Set the V5 byte on the peer board to 0x04, and then check whether the alarm is cleared.
----End
(2008-06-24) 1-261
1.164 20243 Trace Flag Mismatch on the Lower-Order Path

of the Optical Port (LPTIM)
Description
This alarm is reported when the lower order path trace byte J2 is mismatched. Byte J2 is used
to repeatedly send the identifier of lower order path access point, so the receiving end can confirm
the continuous connection to the transmitting end.
Attribute
20243 Major Fault
Parameters
ID Name Meaning
is located.
located.
alarm.
Impact on System
None.
System Actions
None.
Possible Causes
Handling Procedure
1-262 (2008-06-24)
----End
1.165 20244 Signal Flag Mismatch on the Low-Order Path of

the Optical Port (LPSLM)
Description
Lower order path signal label byte mismatched alarm
Attribute
20244 Major Fault
Parameters
ID Name Meaning
4 Tributary Unit No. 062
Impact on System
The service over this path might be interrupted.
System Actions
Possible Causes
The signal identifier field of the V5 byte over this low-order path is inconsistent between the
local and peer boards.
Handling Procedure
Set the V5 byte on the peer board to 0x04, and then check whether the alarm is cleared.
(2008-06-24) 1-263

----End
1.166 20245 Low-Order Path Remote Failure Indicaton

(LPRFI)
Description
Lower order path remote failure indication
Attribute

20245 Major Fault
Parameters
ID Name Meaning
Impact on System
The service quality of the lower-order path in this board is decreased, which might lead to the
interruption of the service.
System Actions
Possible Causes
An alarm is detected over the tributary of the peer equipment.
1-264 (2008-06-24)
Handling Procedure
Step 1 Check whether there is the unloaded, signal label mismatch, or tracing label mismatch alarm
over the lower-order path of the peer equipment.
Y => Go to step 2.
Step 2 Ask the maintenance personnel of the peer equipment to clear the alarms of the peer equipment,
and then check whether the local alarm is cleared.
----End
1.167 20246 Low-Order Path Remote Defect Indication

(LPRDI)
Description
Lower order path remote defect indication
Attribute
20246 Major Fault
Parameters
ID Name Meaning
Impact on System
The service over the lower-order path in this board is affected, which might lead to the
interruption of the service.
System Actions
(2008-06-24) 1-265

Possible Causes
An alarm is detected over the tributary of the peer equipment.
Handling Procedure
Step 1 Check whether there is the unloaded, signal label mismatch, or tracing flag mismatch alarm over
the lower-order path of the peer equipment.
Y => Go to Step 2.
Step 2 Ask the maintenance personnel of the peer equipment to clear the alarms of the peer equipment,
and then check whether the local alarm is cleared.
N => The alarm persists.Please contact Motorola for technical support.
----End
1.168 20247 Tributary Unit Type Mismatch (TUSIZEERR)

Description
This alarm is reported when the tributary unit type is mismatched. Tributary unit type mismatch
means the settings of the SS bit of V1 byte at two ends are inconsistent.
Attribute
20247 Major Fault
Parameters
ID Name Meaning
is located.
located.
alarm.
4 Tributary Unit No. This parameter indicates the tributary unit No. of the optical port.
1-266 (2008-06-24)
Impact on System
The service over this lower-order path is interrupted.
System Actions
Possible Causes
The SS bit configuration of the V1 byte in the peer equipment is not the same with that of the
local equipment.
Handling Procedure
Set the SS bit of the V1 byte in the peer equipment as the same with that of the local equipment,
and then check whether the alarm is cleared.
----End

Description
This alarm is reported when there is no signal input on this tributary.
Attribute
20248 Major Fault
Parameters
ID Name Meaning
is located.
located.
alarm.
(2008-06-24) 1-267
ID Name Meaning
Impact on System
The service over this tributary might be interrupted.
System Actions
Possible Causes
l The optical fiber of this link is not securely installed.
l The receiving mechanism over this link of the local equipment is faulty.
l The transmitting mechanism over this link of the peer equipment is faulty.
l The transmission link is faulty.
Handling Procedure
Step 1 Secure the optical fiber at the local and peer ends, and then check whether the alarm is cleared.
Step 2 Reset the local board and wait for the startup of the board, and then check whether the alarm is
cleared.
Step 3 Contact the maintenance personnel at the peer end to loop back the peer end toward the local
end. Check whether the alarm is cleared.
Y => The alarm is cleared. It indicates that the board at the peer end is faulty. Ask the personnel
at the peer end to clear the fault. The alarm handling is complete.
Step 4 Contact the transmission personnel and check whether the transmission is normal.
Y => Go to step 5.
N => The alarm handling is complete.
is cleared.
N => The alarm persists. Please contact Motorola for technical.
----End
1-268 (2008-06-24)
1.170 20249 Tributary Alarm Indication Signal (AIS)

Description
This alarm is reported when the tributary unit receives alarm indication signal from the peer
port.
Attribute

20249 Major Fault
Parameters
ID Name Meaning
is located.
located.
alarm.
4 Tributary Unit No. This parameter indicates the tributary unit of the optical port.
Impact on System
System Actions
Possible Causes
l The tributary at the peer end is in inter-board loop mode.
l The transmission equipment is in well communication with the local equipment, but it
obtains no signal input from the peer equipment.
(2008-06-24) 1-269
Handling Procedure
Step 1 Check whether the link on the peer board is operating under inter-board loopback mode.
Y => The link on the peer board is operating under inter-board loopback mode. Go to step 2.
N => The link on the peer board is not operating under inter-board loopback mode. Go to step
3.
Step 2 Stop the inter-board loopback mode of the link on the peer board to have the link operated
normally. Check whether the alarm is cleared.
Step 3 Check whether the peer board is correctly connected with the transmission equipment.
Y => The connection is correct. Please contact Motorola for technical support.
N => The connection is wrong. Go to step 4.
Step 4 Correctly connect the peer board with the transmission equipment, and then check whether the
alarm is cleared.
----End

Description
This alarm is reported when the tributary cannot locate the initial position of frame.
Attribute
20250 Major Fault
Parameters
ID Name Meaning
is located.
located.
alarm.
1-270 (2008-06-24)
Impact on System
System Actions
Possible Causes
The configuration of the frame format in the local equipment is not the same with that of the
peer board.
Handling Procedure
N=> Go to step 2.
The parent alarm and the child alarm have the same Subrack No., Slot No., and Tributary No.
in the alarm location information.
Step 2 Keep consistent with the configuration of the frame format between the local and peer equipment
over this tributary, and then check whether the alarm is cleared.
----End
1.172 20251 Remote Alarm Indication over the Tributary

(RAI)
Description
This alarm is reported when the peer end is in out-of-frame state or signal loss state.
Attribute

20251 Major Fault
(2008-06-24) 1-271
Parameters
ID Name Meaning
is located.
located.
alarm.
Impact on System
System Actions
Possible Causes
l The optical fiber of this link is not securely installed.
l The configuration of the frame format between two ends of this link is not the same.
l The receiving mechanism over this link of the local equipment is faulty.
l The transmitting mechanism over this link of the peer equipment is faulty.
l The transmission is one-way operational.
Handling Procedure
N=> Go to step 2.
The parent alarm and the child alarm have the same Tributary No. in the alarm location
information.
1-272 (2008-06-24)
The parent alarm and the child alarm have the same Tributary No. in the alarm location
information.
Step 2 Secure the optical fiber at the local and peer ends, and then check whether the alarm is cleared.
Step 3 Check whether the configuration of the frame format between two ends of this link is the same.
Y => Go to step 5.
N => Go to step 4.
Step 4 Configure the link of the local end the same with that of the peer end, and then check whether
Step 5 Reset the local board and wait for the startup of the board, and then check whether the alarm is
cleared.
Step 6 Contact the maintenance personnel at the peer end to loop back the peer link toward the local
end. Check whether the alarm is cleared.
Y => The alarm is cleared. It indicates that the board at the peer end is faulty. Ask the personnel
at the peer end to clear the fault. The alarm handling is complete.
Step 7 Contact the transmission personnel and check whether the transmission is faulty.
Y => The transmission is faulty. Ask the maintenance personnel to solve the transmission
problem. The alarm handling is complete.
N => The transmission is normal. Go to step 8.
Step 8 Replace the local board, and then check whether the alarm is cleared.
----End
1.173 20252 Loss of Tributary Multi-Frames (LOM)

Description
This alarm is reported when the tributary cannot locate the initial position of frame.
Attribute
20252 Minor Fault
(2008-06-24) 1-273
Parameters
ID Name Meaning
is located.
located.
alarm.
Impact on System
The service over this tributary might be affected.
System Actions
None.
Possible Causes
l The peer frame format over this tributary is not the same with that of the local end, which
is E1 CRC4 multi-frame format.
l The bit error rate over this link exceeds the normal value.
Handling Procedure
Step 1 Check whether the local frame format is of E1 CRC4 multi-frame format.
Y => Go to step 2.
N => Go to step 4.
Step 2 Check whether the configuration of the frame format in the peer end is the same with that of the
local end.
N => Go to step 3.
Step 3 Configure the peer frame format over this tributary the same with that of the local end, and then
Step 4 Check whether there exists bit error-related alarm.
Y => Go to step 5.
Step 5 Clear the bit error alarm according to its relevant handling suggestions, and then check whether
the multi-frame loss alarm is cleared.
1-274 (2008-06-24)

----End
1.174 20253 Slip Frame over the Tributary

Description
This alarm is reported when the number of slip frames within five minutes exceeds the alarm
threshold.
Attribute

20253 Minor Fault
Parameters
ID Name Meaning
is located.
located.
alarm.
5 Slip Frame No. This parameter indicates the number of slip frame.
Impact on System
The service over this tributary might be affected.
System Actions
None.
Possible Causes
The clock between two ends of this tributary is not synchronized.
(2008-06-24) 1-275
Handling Procedure
Synchronize the clock between two ends of this tributary through the local maintenance terminal
(LMT), and then check whether the alarm is cleared.
----End
1.175 20254 Tributary Loopback Alarm

Description
This alarm is report when the local equipment is in loopback mode. The services on it are
disabled.
Attribute
20254 Minor Fault
Parameters
ID Name Meaning
is located.
located.
alarm.
5 l 0=No loop
l 3=Lower order path line loop
l 4=tributary line loop
l ,5=tributary system loop
Impact on System
The service over this tributary is interrupted.
System Actions
None.
1-276 (2008-06-24)
Possible Causes
The local tributary is randomly set as one of the loopback mode of the the Optical Port.
Handling Procedure
Step 1 Check whether this tributary is performing the loopback test on the optical tributary.
Y => No handling is required.
N => Go to step 2.
Step 2 Stop the loopback of the optical tributary through the LMT to have it operated in normal state.
----End
1.176 20255 Optical Module Fault

Description
This alarm is reported when the performance of optical component such as power or temperature
is faulty.
Attribute

20255 Major Fault
Parameters
ID Name Meaning
located.
located.
4 Optical port No. This parameter indicates the optical interface No.
Impact on System
The service performance decreases, which might lead to the interruption of the service.
(2008-06-24) 1-277
System Actions
Possible Causes
The optical module is abnormal.
Handling Procedure
Step 1 Replace the faulty optical module, and then check whether the alarm is cleared.
Step 2 Reset the board and wait until the board is successfully restarted. Check whether the alarm is
cleared.
cleared.
----End

Description
This alarm is reported when serial ports are faulty. Local boards cannot communicate with
monitoring boards (power distribution box, fan box, and EAC) through the serial ports.
Attribute
20271 Minor Fault
Parameters
ID Name Meaning
located.
1-278 (2008-06-24)
ID Name Meaning
Impact on System
The monitoring of fan, power box, and environment device is unavailable.
System Actions
None.
Possible Causes
l There is an over-inflow of data transmitted from the CPU.
Handling Procedure
Step 1 Reset the board and wait for its startup, and then check whether the alarm is cleared.
cleared.
----End
1.178 20272 Monitor Board Out of Position

Description
This alarm is reported when monitoring boards (power distribution box, fan box, and EAC) are
not connected to the BSC.
Attribute

20272 Minor Fault
(2008-06-24) 1-279
Parameters
ID Name Meaning
2 Slot No. of the monitor board l 0=Distribution Monitor and Communication board
l 1=Fan Control Unit
l 2=Environment Monitoring Device
Impact on System
l If one port is faulty, the service quality between the GSCU and the service boards decreases.
l If two ports are faulty, the service between the GSCU and the service boards is interrupted.
System Actions
None.
Possible Causes
l The monitor board being examined is not connected to the subrack with the serial port
cable.
l The serial cable that connects the board and the subrack is faulty.
l The board being checked is faulty.
Handling Procedure
N=> Go to step 2.
Step 2 Check whether the monitor board is connected to the subrack with the serial port cable.
Y => Go to step 4.
N => Go to step 3.
Step 3 Connect the monitor board and the subrack with the serial port, and then check whether the alarm
is cleared.
1-280 (2008-06-24)
Step 4 Reconnect the serial port cable that connects the monitor board and the subrack, and then check
Step 5 Replace the serial port cable that connects the monitor board and the subrack, and then check
Step 6 Replace the monitor equipment, and then check whether the alarm is cleared.
Step 7 Switch the GSCU, and then check whether the alarm is cleared.
N => The alarm persists. Please contact Motorola for technical support..
----End

Description
This alarm is reported when the clock reference of GGCU board is in unusable state.
Attribute
20321 Minor Fault
Parameters
ID Name Meaning
located.
located.
4 Source index No. This parameter indicates the Index in Source table of lost source.
Impact on System
None.
(2008-06-24) 1-281
System Actions
l If the GGCU is in automatic switch mode and there are other available clock sources when
the current clock source is unavailable, then the GGCU switches to other available clock
source.
l If the GGCU is in automatic switch mode and there are no available clock sources when
the current clock source is unavailable, then the phase-lock loop of the GGCU enters self-
oscillation state or remains unchanged.
l If the GGCU is in manual switch mode and the current clock source is unavailable, then
the phase-lock loop of the GGCU enters self-oscillation state or remains unchanged.
l No alarm handling for other cases.
Possible Causes
l The input signal for the clock reference is lost.
l The frequency offset for the input signal of the reference source is abnormal, that is, the
frequency offset is greater than that being introduced.
l The board is faulty.
Handling Procedure
Step 1 As the handling procedures vary for different clock reference, please specify the type of the
clock reference in advance by the values of parameter 4.
If the type of the faulty clock reference is 2 MHz or 2 MBPS:
(1) Secure the clock cable of the GGCU that connects the clock source, and then check whether
(2) Replace the clock cable, and then check whether the alarm is cleared.
N => The alarm persists. Go to step c.
(3) Check whether the frequency offset output from the clock source is normal by using relevant
equipment.
Y => The frequency offset is normal. Go to step d.
N => The frequency offset is abnormal. Go to step e.
(4) Replace the board, and then check whether the alarm is cleared.
(5) Check whether the clock source is of BITS clock.
Y => Contact the maintenance engineer concerning the BITS clock to solve the problem.
N => The clock source is from the interface board of the BSC. Go to step f.
(6) The interface board that output the clock source is faulty. Clear the relevant fault, and then
1-282 (2008-06-24)
Step 2 If the type of the faulty clock reference is 8K:

(1) Secure the GGCU and the interface board that output the clock source, and then check
(2) Check whether there are clock-related alarms with the interface board that output the clock
source.
Y => There are clock-related alarms. Go to step c.
N => There is no clock-related alarm. Go to step d.
(3) Clear the clock alarm of the interface board according to its relevant handling suggestions,
and then check whether the alarm of the board is cleared.
N => The alarm persists. Go to step d.
(4) Replace the faulty GGCU board, and then check whether the alarm is cleared.
----End
1.180 20322 Unavailable Current Clock Reference for GGCU

Description
This alarm is reported when the current clock reference of GGCU board is in unusable state.
Attribute
20322 Minor Fault
Parameters
ID Name Meaning
located.
Impact on System
None.
(2008-06-24) 1-283
System Actions
The phase-lock loop of the GGCU enters self-oscillation state or remains unchanged.
Possible Causes
Handling Procedure
clock reference in advance by the values of parameter 4. If the type of the faulty clock reference
is 2 MHz or 2 MBPS:
N=> Go to step b.
The clock source corresponding to Source index No. in the alarm location information of
the parent alarm must be the current clock source of the GGCU.
(2) Secure the clock cable of the GGCU that connects the clock reference, and then check
equipment.
Y => The frequency offset is normal. Go to step e.
N => The frequency offset is abnormal. Go to step f.
Y => Contact the the maintenance engineer concerning the BITS clock to solve the problem.
N => The clock source is from the interface board of the BSC. Go to step g.
(7) The interface board that output the clock source is faulty. Clear the relevant fault ,and then
1-284 (2008-06-24)
clock reference in advance by the values of parameter 4. If the type of the faulty clock reference
is 8K:
N=> Go to step b.
The clock source corresponding to Source index No. in the alarm location information of
the parent alarm must be the current clock source of the GGCU.
source.
Y => There are clock-related alarms. Go to step d.
N => There is no clock-related alarm. Go to step e.
N => The alarm persists. Go to step e.
(5) Replace the faulty GGCU, and then check whether the alarm is cleared.
----End
1.181 20323 GGCU Failure-Abnormal Frequency Doubler

Description
This alarm is reported when clock frequency doubler of GGCU board is abnormal.
Attribute

20323 Major Fault
(2008-06-24) 1-285
Parameters
ID Name Meaning
located.
4 Chip No. l 0=Clock frequency doubler A

l 1=Clock frequency doubler B
Impact on System
None.
System Actions
Reset the board.
Possible Causes
The board hardware is faulty.
Handling Procedure
Step 1 Wait until the board is successfully loaded and restarted. Check whether the alarm is cleared.
cleared.
----End
1.182 20324 GGCU Failure-Abnormal Local Oscillation

Signal
Description
This parameter indicates the local oscillator signal (crystal oscillator chip) of GGCU board is
faulty.
1-286 (2008-06-24)
Attribute
20324 Major Fault
Parameters
ID Name Meaning
located.
Impact on System
None.
System Actions
Reset the board.
Possible Causes
The constant-temperature crystal oscillator in the GGCU is faulty, resulting the abnormal output
of the clock signal.
Handling Procedure
Step 2 Replace the board and wait until the board is successfully loaded and restarted. Check whether
----End
1.183 20325 Clock Reference Failure of GGCU over 24 Hours

Description
This alarm is reported when the current clock reference of the GGCU board is in unusable state
for 24 hours.
(2008-06-24) 1-287
Attribute
20325 Major Fault
Parameters
ID Name Meaning
located.
Impact on System
l If the alarm is reported by the active board, the service will not be affected once the
switchover between the active and standby boards succeeds.
l If the alarm is reported by the active board, the service will not be affected once the alarm
is cleared within 24 hours when the switchover between the active and standby boards fails.
l If the alarm is reported by the active board, the service will be affected once the alarm is
not cleared within 24 hours when the switchover between the active and standby board
fails.
l If the alarm is reported by the standby board, the service will not be affected.
System Actions
Possible Causes
Handling Procedure
clock reference in the clock reference table.
If the type of the faulty clock reference is 2 MHz or 2 MBPS:
(1) Secure the clock cable of the GGCU that connects the clock source, and then check whether
1-288 (2008-06-24)

equipment.
Y => The frequency offset is normal. Go to step d.
N => The frequency offset is abnormal. Go to step e.
Y => Contact the the maintenance engineer concerning the BITS clock to solve the problem.
N => The clock source is from the interface board of the BSC. Go to step f.
(6) The interface board that output the clock source is faulty. Clear the relevant fault, and then
Step 2 If the type of the faulty clock reference is 8K:

source.
Y => There are clock-related alarms. Go to step c.
N => There is no clock-related alarm. Go to step d.
(4) Replace the faulty GGCU , and then check whether the alarm is cleared.
----End
1.184 20329 Unavailable Input Clock Source for GGCU

Description
This alarm is reported when all the clock module input resources of the GGCU board are
unusable. The phase-lock loop is in non-tracing non-hold status.
(2008-06-24) 1-289
Attribute
20329 Major Fault
Parameters
ID Name Meaning
located.
Impact on System
l If the alarm is reported by the active board, the service will not be affected once the
switchover between the active and standby boards succeeds.
l If the alarm is reported by the active board, the service might be affected once the switchover
between the active and standby boards fails.
l If the alarm is reported by the standby board, the service will not be affected.
System Actions
Possible Causes
l The clock reference is not configured.
l The clock reference chosen in manual mode is unavailable.
l All the clock references chosen in automatic mode are unavailable.
l The clock reference with highest priority is in frequent switching between availability and
unavailability in the automatic mode.
Handling Procedure
Step 1 Check whether the clock reference is not configured.
Y => The clock reference is not configured. Go to step 2.
N => The clock reference is configured. Go to step 3.
Step 2 Configure the clock reference and access to the available clock reference. Wait for 10 minutes,
and then check whether the alarm is cleared.
1-290 (2008-06-24)
Step 3 Check whether the work mode is of manual mode.
Y => The work mode is of manual mode. Go to step 4.
N => The work mode is of automatic mode. Go to step 5.
Step 4 Check whether the current clock reference which is of manual mode is unavailable.
Y => The current clock reference is unavailable. Go to step 6.
N => The current clock reference is available. Please contact Motorola for technical support.
Step 5 Check whether all the clock references being configured are unavailable.
Y => All the clock references being configured are unavailable. Go to step 6.
N => Some clock references are available. Please contact Motorola for technical support.
Step 6 Clear the fault by adhering to the handling of 1.180 20322 Unavailable Current Clock
Reference for GGCU and wait for 10 minutes, and then check whether the alarm is cleared.
----End
1.185 20352 Clock Failure of the TDM Interface Unit

Description
This alarm is reported when TDM interface unit clock is abnormal.
Attribute
20352 Major Fault
Parameters
ID Name Meaning
located.
4 Fault Type This parameter indicates the fault type.
Impact on System
The service on this board is interrupted.
(2008-06-24) 1-291
System Actions
Reset the board.
Possible Causes
The hardware chip is faulty.
Handling Procedure
cleared.
----End
1.186 20353 TDM Interface Unit Failure Alarm

Description
This alarm is reported when the TDM interface unit logic chip is abnormal.
Attribute
20353 Major Fault
Parameters
ID Name Meaning
board is located.
reports the alarm.
4 HW and CORE Interface State This parameter indicates the HW and CORE interface
status.
1-292 (2008-06-24)
ID Name Meaning
5 POS Interface State This parameter indicates the POS interface status.
6 MII Interface State This parameter indicates the MII interface status.
7 SSRAM Verify Status This parameter indicates the SSRAM Verify Fail.
8 Logic Chip Number This parameter indicates the Index of the alarmed logic
chip.
Impact on System
The service on this board might be interrupted.
System Actions
l Handling of the active board in the active/standby operation modePerform the switchover
l Handling of the standby board in the active/standby operation modeNone.
l Handling of the board in the Independent operation modeNone.
Possible Causes
The hardware chip is faulty.
Handling Procedure

alarm is cleared.
(2008-06-24) 1-293
cleared.
----End
1.187 20357 GEIUx/GOIUxTime slot loopback alarm

Description
This alarm is reported when the GEIUx/GOIUx timeslot is in the Loopback state.
Attribute
20357 Warning Fault
Parameters
ID Name Meaning
located.
4 Link No. This parameter indicates the number of the E1 link on which the timeslot
loop alarm is generated.
Impact on System
The communication on the timeslot is interrupted.
System Actions
None
Possible Causes
The timeslot is in the Loopback state.
Handling Procedure
Step 1 Check which ports are set in the TDM timeslot loopback mode.
Y => The loopback is set. Go to step2.
1-294 (2008-06-24)
N => The loopback is not set. Go to step3.

Step 2 Disable the setting of TDM timeslot loopback setting on the port, and check whether the alarm
is cleared.
Step 3 Reset the faulty board. After the board is restarted, check whether the alarm is cleared.
Step 4 Replace the faulty board. After the new board is restarted, check whether the alarm is cleared.
----End
1.188 20359 TDM backplane Link Failure of TSU

Description
This alarm is reported when the TDM link on the TSU Backplane is faulty.
Attribute
20359 Minor Fault
Parameters
ID Name Meaning


4 Backplane link No. This parameter indicates the backplane link

No.
6 Slot No. of transaction board crossing this This parameter indicates the slot No. of
link transaction board crossing this link.
(2008-06-24) 1-295
Impact on System
The services may be disrupted.
System Actions
None.
Possible Causes
l The peer board that carries the faulty link is reset.
l The clock signals transmitted to the service board from the GSCU are faulty.
l The peer board that carries the faulty link is not in position or not securely inserted.
l The peer board that carries the faulty link is faulty.
Handling Procedure
N => Go to step 2.
Correlated parent alarm:
Y => The peer board is reset. This indicates that the alarm is caused by the reset of the peer
board. The alarm handling is complete.
Step 3 Check whether an alarm related to the clock is generated on the active GSCU.
Y => Go to step 4.
N => Go to step 5.
Step 4 Clear the clock alarm on the GSCU according to the handling suggestions, and then check
Step 5 Secure the local board and the peer board that carries the faulty link, and then check whether
Step 6 Replace the faulty board and wait until the new board is successfully loaded and reset. Then,
1-296 (2008-06-24)

Step 7 Replace the peer board that carries the faulty link and wait until the new board is successfully
loaded and reset. Then, check whether the alarm is cleared.
----End
1.189 20360 TDM backplane Link Failure of transaction

board
Description
This alarm is reported when the TDM link on the Service Board Backplane is faulty.
Attribute

20360 Minor Fault
Parameters
ID Name Meaning
reports the alarm.
4 Backplane link No. This parameter indicates the backplane link No.
5 Fault Type This parameter indicates the Fault type.
6 Slot No. of TSU crossing this link This parameter indicates the slot No. of the peer TSU.
Impact on System
(2008-06-24) 1-297
System Actions
None.
Possible Causes
Handling Procedure
Y=> Clear the parent alarm according to the handling suggestions. Check whether the alarm is
cleared.
N => Go to step 2.

Y => Go to step 4.
N => Go to step 5.
1-298 (2008-06-24)
----End
1.190 20361 TDM panel Link Failure of TSU

Description
This alarm is reported when the TDM link on the TSU Panel is faulty.
Attribute
20361 Minor Fault
Parameters
ID Name Meaning
reports the alarm.
4 Panel Port No. This parameter indicates the Panel Port No.
6 Panel port No. crossing this link This parameter indicates the number of the panel port
that carries the link (A GTNU panel has six ports and
each port has two port numbers. The six ports are
numbered 0-11.)
Impact on System
Some inter-subrack calls may fail.
System Actions
None.
(2008-06-24) 1-299
Possible Causes
l The cable between the GTNU panels are not securely inserted.
l The cable between the GTNU panels is faulty.
Handling Procedure
Y=> Clear the parent alarm according to the handling suggestions. Check whether the alarm is
cleared.
N => Go to step 2.
Y => Go to step 4.
N => Go to step 5.
Step 5 Secure the cable between the local board and the peer board, and check whether the alarm is
cleared.
Step 6 Replace the cable between the local board and the peer board, and check whether the alarm is
cleared.
1-300 (2008-06-24)

----End
1.191 20362 Master TDM link of TSU backplane fault alarm

Description
This alarm is reported when the master TDM Link is faulty.
Attribute
20362 Major Fault
Parameters
ID Name Meaning

3 CPU No. This parameter indicates the number of the CPU

that reports the alarm.
4 TDM link group No. 0-23: Group number of TDM links on the
backplane
5 LVDS slot 1 No. of transaction board This parameter indicates the LVDS slot 1 No. of
transaction board.
6 LVDS slot 2 No. of transaction board This parameter indicates the LVDS slot 2 No. of
transaction board.
Impact on System
System Actions
(2008-06-24) 1-301
l For the board that works in independent mode, no action is taken.
Possible Causes
Handling Procedure
Step 2 Check whether an alarm related to the clock is generated on the GSCU.
Y => Go to step 3.
N => Go to step 4.
Correlated alarm related to the clock:
Step 3 Clear the clock alarm on the GSCU according to its relevant handling suggestions, and then
Step 5 Replace the faulty board. Check whether this alarm is cleared.
Step 6 Replace the peer board that carries the faulty link. Check whether this alarm is cleared.
----End
1-302 (2008-06-24)
1.192 20363 Master TDM link of transaction board

backplane fault alarm
Description
This alarm is reported when the master TDM Link is faulty.
Attribute

20363 Major Fault
Parameters
ID Name Meaning
board is located.
is located.
the alarm.
4 TDM link group No. This parameter indicates the group number of TDM links on
the service board backplane.
5 LVDS slot 1 No. of TSU This parameter indicates the LVDS slot 1 No. of TSU.
6 LVDS slot 2 No. of TSU This parameter indicates the LVDS slot 2 No. of TSU.
Impact on System
System Actions
(2008-06-24) 1-303
Possible Causes
Handling Procedure
Y => Go to step 3.
N => Go to step 4.
Correlated alarm related to the clock:
----End
1.193 20364 Master TDM link of TSU panel fault alarm

Description
This alarm is reported when the master TDM Link if faulty.
1-304 (2008-06-24)
Attribute

20364 Major Fault
Parameters
ID Name Meaning
is located.
located.
alarm.
4 TDM link group No. 0-11: group number of TDM links on the panel
5 Panel port 1 No. This parameter indicates the panel port 1 No.
6 Panel port 2 No. This parameter indicates the panel port 2 No.
Impact on System
Some inter-subrack calls may fail.
System Actions
Possible Causes
l The cable between the GTNU panels are not securely inserted.
l The cable between the GTNU panels is faulty.
(2008-06-24) 1-305
Handling Procedure
Y => Go to step 3.
N => Go to step 4.
Step 4 Secure the cable between the local board and the peer board, and check whether the alarm is
cleared.
Step 5 Replace the cable between the local board and the peer board, and check whether the alarm is
cleared.
----End
1.194 20371 GE/FE Conversion Unit Fault

Description
This alarm is reported when the GE/FE conversion unit logic chip is abnormal.
Attribute

20371 Major Fault
1-306 (2008-06-24)
Parameters
ID Name Meaning
board is located.
reports the alarm.
4 HW and CORE Interface State This parameter indicates the HW and CORE interface
status.
5 POS Interface State This parameter indicates the POS interface status.
6 MII Interface State This parameter indicates the MII interface status.
Impact on System
The service on this board might be interrupted.
System Actions
Possible Causes
Handling Procedure
(2008-06-24) 1-307

alarm is cleared.
cleared.
----End
1.195 20372 GE Interface Unit Fault

Description
This alarm is reported when the GE interface unit is faulty.
Attribute
20372 Minor Fault
Parameters
ID Name Meaning
located.
4 POS3 port No. l 0=POS3 port connected with the 7th slot GSCU
l 1=POS3 port connected with the 6th slot GSCU
Impact on System
l If one port is faulty, the service performance between the GSCU and the service board
decreases.
l If two ports are faulty, the service between the GSCU and the service board is interrupted.
1-308 (2008-06-24)
System Actions
If the other link is normal, an automatic handover is performed to a normal link.
Possible Causes
l The GSCU is reset.
l The GSCU corresponded to the faulty port is not securely inserted.
l The hardware of the GSCU is faulty.
Handling Procedure
N=> Go to step 2.
The Link No. in the alarm location information of the parent alarm is the same as the POS3 No.
in the alarm location information of the child alarm.
Step 2 Check whether the GSCU is reset.

Y => The GSCU is reset. The alarm is cleared once the board is reset and started. The alarm
N => The GSCU is not reset. Go to step 3.
Step 3 Secure the board and check whether the alarm is cleared.
Step 4 Secure the GSCU which corresponds to the faulty port of the board and check whether the alarm
is cleared.
Step 5 Replace the faulty board and wait until the board is successfully restarted. Check whether the
alarm is cleared.
Step 6 Replace the GSCU which corresponds to the faulty P0S3 port and wait until the board is
successfully restarted. Check whether the alarm is cleared.
(2008-06-24) 1-309
----End
1.196 20401 Board Fault-ME Fault

Description
ME fault alarm
Attribute
20401 Major Fault
Parameters
ID Name Meaning
4 Fault Type "1" indicates the ME thread is faulty.
5 Thread states of the former four Mes The thread status of 03 ME
6 Thread states of the latter four Mes The thread status of 47 ME
Impact on System
The service on this board is interrupted.
System Actions
Reset the board.
Possible Causes
Handling Procedure
Step 1 The system automatically resets the board. Wait until the board is successfully loaded and
restarted, and check whether the alarm is cleared.
1-310 (2008-06-24)
Step 2 Change the board, and check whether the alarm is cleared.
Y =>The alarm is cleared. The alarm handling is complete.
N =>The alarm persists. Please contact Motorola for technical support.
----End
1.197 20409 Quality of GE Link on GSCU Backplane

Decrease
Description
This alarm is reported when the quality of the GE link on the backplane of the GSCU decreases.
Attribute

20409 Minor Fault
Parameters
ID Name Meaning


4 Number of the GE link on the backplane This parameter indicates the number of the GE
link on the backplane.
5 Slot number of the service board mapping This parameter indicates the number of the slot
to the faulty link on the backplane corresponding to the faulty
link.
6 Alarm parameter This parameter indicates the Alarm parameter.
Impact on System
The service performance between the GSCU and the service board decreases.
(2008-06-24) 1-311
System Actions
None
Possible Causes
l The peer board is not securely inserted.
Handling Procedure
Step 3 Reset the peer service board. After the board is restarted successfully, check whether the alarm
is cleared.
N =>The alarm is not cleared. Go to step4.
Step 4 Reset the local board. After the board is restarted successfully, check whether the alarm is
cleared.
Step 5 Replace the peer service board. After the board is restarted successfully, check whether the alarm
is cleared.
Step 6 Replace the board. After the board is restarted successfully, check whether the alarm is cleared.
----End
1.198 20410 Quality of GE Link on GSCU Panel Decrease

Description
This alarm is reported when the quality of the GE link on the panel of the GSCU decreases.
1-312 (2008-06-24)
Attribute

20410 Minor Fault
Parameters
ID Name Meaning


4 Number of the GE link on the panel This parameter indicates the number of the GE link
on the panel. The twelve ports on the panel are
numbered from 0 to 11, from the top down. The link
number maps the number of the port on the panel.
5 Number of the port on the panel The parameter value indicates the number of the
disconnected link for the panel. The twelve ports on
the panel are numbered from 0 to 11, from the top
down. The link number maps the number of the port
on the panel.
6 Alarm parameter This parameter indicates the alarm parameter.
Impact on System
The service performance between subracks decreases.
System Actions
None
Possible Causes
l The Ethernet cable on the panel is in loose contact.
(2008-06-24) 1-313
Handling Procedure
Step 1 Secure the Ethernet cables on the panels of the local and peer boards, and then check whether
N => The alarm is not cleared. 4.
cleared.
----End
1.199 20411 Quality of GE Link on Sub-Board Decrease

Description
This alarm is reported when the quality of the GE link on the sub-board of the GXPUx decreases.
Attribute

20411 Major Fault
Parameters
ID Name Meaning


1-314 (2008-06-24)
ID Name Meaning
4 Number of the CPU that is connected to the This parameter indicates the number of the
GE port CPU that is connected to the GE port.
5 Alarm parameter This parameter indicates the alarm

parameter.
Impact on System
The service quality of the standby CPU mapping to the faulty link decreases.
System Actions
l For the active board in active/standby mode: The system performs switchover if the standby
l For the standby board in active/standby mode: No handling.
Possible Causes
l The sub-board where the CPU mapping to the faulty link resides is not securely inserted.
l The hardware of the peer board mapping to the faulty link fails.
Handling Procedure
Step 1 Remove the GXPUx and tightly insert the sub-board where the CPU mapping to the faulty link
CPU resides. Then, reinstall the GXPUx. After the new board is successfully restarted, check
Step 2 Remove the GXPUx and replace the sub-board where the faulty link CPU resides. Then, reinstall
the GXPUx. After the new board is successfully restarted, check whether the alarm is cleared.
Step 3 Replace the GXPUx. After the new board is successfully restarted, check whether the alarm is
cleared.
----End
1.200 20412 Quality of GE Link on GXPUx Panel Decrease

Description
This alarm is reported when the quality of the GE link on the panel of the GXPUx decreases.
(2008-06-24) 1-315
Attribute

20412 Minor Fault
Parameters
ID Name Meaning


4 Number of the GE link on the panel This parameter value indicates the number of the
disconnected link for the panel. The four ports on
on the panel.
5 Number of the port on the panel The parameter value indicates the number of the
disconnected link for the panel. The four ports on
on the panel.
6 Alarm parameter This parameter indicates the alarm parameter.
Impact on System
The quality of the service that the link bears decreases.
System Actions
None
Possible Causes
l The Ethernet cable on the panel is in loose contact.
1-316 (2008-06-24)
Handling Procedure
Step 1 Secure the Ethernet cables on the panels of the local and peer boards, and then check whether
cleared.
----End
1.201 20421 Abnormal Temperature

Description
An overtemperature alarm is reported when the fan box detects that the temperature exceeds the
upper temperature threshold. An undertemperature alarm is reported when the temperature of
the power distribution box or the environment monitor device exceeds the lower temperature
threshold. In reverse, an overtemperature alarm is reported.
Attribute

20421 Major Fault
Parameters
ID Name Meaning
1 Subrack No. This parameter indicates the number of the subrack.
2 Logical Slot No. l 0=0Powerbox Monitor

l 1=1Fanbox Monitor
l 2=2Environment Monitor
(2008-06-24) 1-317
ID Name Meaning
3 Sensor No. This parameter indicates the number of the sensor that resides in the
board.
4 Temperature State l 0=Normal

l 1=High
l 2=Low
Impact on System
The overtemperature or the undertemperature of the cabinet has an impact on normal running
of the system.
System Actions
l If the fan box detects that the temperature exceeds the upper temperature threshold, the fan
box runs in full speed to ensure the dissipation and safe running of the system. The LMT
can detects that the rotational speed of the fan is about 4000 RPM.
l If the power distribution box or the environment monitoring device detects that the
temperature of the cabinet exceeds the upper temperature threshold (70) or exceeds the
lower temperature threshold (5), a temperature alarm is reported. The system does not
automatically process the alarm.
Possible Causes
l The environment temperature exceeds or below normal value.
l The temperature of the board exceeds or below normal value.
Handling Procedure
Step 1 according to the alarm information, you can make sure that the alarm is caused by
overtemperature or undertemperature.
Y> An overtemperature alarm is reported. Go to step 2.
N> An undertemperature alarm is reported. Go to step 3.
Step 2 If an overtemperature alarm is reported, you can power on the air conditioner or the ventilating
fan to lower the environment temperature.
Step 3 If an undertemperature alarm is reported, you can power on the air conditioner to increase the
environment temperature.
----End
1-318 (2008-06-24)
1.202 20422 Abnormal Voltage

Description
This alarm is reported when one supply voltage of the input power in the power distribution box
or one supply voltage of the environment monitoring device exceeds the upper or lower voltage
limitation.
Attribute
20422 Major Fault
Parameters
ID Name Meaning

l 2=2Enviroment Monitor
3 Sensor No. This parameter indicates the number of the sensor in the board.
4 Voltage Status l 0=Normal

l 1=High
l 2=Low
Impact on System
The power distribution box supplies power abnormally. This may has an impact on normal
running of the system. If the voltage exceeds the upper or lower limitation, the power module
on the board might stop supplying power and the service is interrupted.
System Actions
Generally, if an alarm is reported within 10 seconds, the system can go back to normal
automatically.
Possible Causes
Any supply voltage of the two input power in the power distribution box or the environment
monitoring device exceeds the upper or lower voltage limitation.
Handling Procedure
Step 1 Check the duration of the alarm. If the duration is less than 10 seconds, the alarm is reported
because of the voltage pulsation and is unnecessary to be handled.
(2008-06-24) 1-319
Step 2 If the duration is long, Check whether the power supply is normal.
Y=> This indicates that the board is faulty. Go to step 3.
N=> The power supply is over voltage or under voltage. Inform the network operator to take
certain measures, such as power transfer or battery maintenance. The alarm handling is complete.
NOTE
The evaluation standard of 48 V power supply system: Undervoltage alarm ranges from -40 V to -42 V;
overvoltage alarm ranges from -57 V to 60 V.
The evaluation standard of 60 V power supply system: Undervoltage alarm ranges from -71 V to -75 V;
overvoltage alarm ranges from -42 V to -50 V.
Step 3 Reset the power distribution box on the LMT. After the power distribution box is registered
----End
1.203 20423 Communication Failure

Description
This alarm is reported when the communication of the fan box, the power distribution box, or
the environment monitoring device is interrupted.
Attribute

20423 Major Fault
Parameters
ID Name Meaning

l 1=1Fanbox Monitor
l 2=2Environment Monitor
3 Sensor No This parameter indicates the number of the sensor that resides in the
board.
4 Link Status l 0=normal

l 1=connect fail
1-320 (2008-06-24)
Impact on System
The fan box, the power distribution box, or the environment monitoring device cannot report
the alarm information. The LMT cannot send the command of the fan box, the power distribution
box, or the environment monitoring device.
System Actions
l If the communication of the power distribution box fails, an automatic handover of the
power distribution box is performed to a standby serial port. If the standby serial port cannot
be registered , the board is reset automatically after 30 seconds. Before the reset is registered
successfully, repeat the previous process until the communication link is established again.
l If the communication of the fan box fails, after 60 seconds, the fan box runs at full speed.
After the link is normal, the alarm is cleared.
l If the communication of the environment monitoring device fails, reset the environment
monitoring device and establish the communication link again.
Possible Causes
l The node address of the power distribution box, the fan box, or the environment monitoring
device is incorrectly set. The correct setting is:
0 = power distribution box
1 = fan box
2 = environment monitoring device
l If the hardware of the fan box, the power distribution box, or the environment monitoring
device is faulty, the communication fails.
l If the cable that connects the power distribution box, the fan box, or the environment
monitoring device is faulty, the communication of the power distribution box, the fan box,
or the environment monitoring device fails.
Handling Procedure
Step 1 If the communication of the power distribution box fails, remove the power distribution monitor
and control board and reinsert it. Then check whether the DIP switch used to set the address on
the power distribution box is correctly configured. If the configuration is incorrect, set the node
address again according to the BSC Hardware Description. Then power on the board to check
whether the board is connected normally.
Step 2 Check whether the automatic reset of the power distribution box can be connected again.
Step 3 Check whether the connected cable is normal. If the connected cable is abnormal, securely
connect the cable again. If the condition permits, change the cable.
Step 4 If the communication of the fan box fails, remove the fan box and reinsert it. Then check whether
the DIP switch used to set the address on the fan box is correctly configured. If the configuration
is incorrect, set the node address again according to the BSC Hardware Description. Then power
on the board to check whether the board is connected normally.
(2008-06-24) 1-321

Step 5 If the communication of the environment monitoring device fails, check whether the DIP switch
used to set the address on the environment monitoring device is correctly configured. If the
configuration is incorrect, set the node address again according to the BSC Hardware
Description. Then power on the board to check whether the board is connected normally.
----End
1.204 20424 Abnormal Humidity

Description
This alarm is reported when the environment humidity of the power distribution box or the
environment monitoring device exceeds the upper or lower limitation.
Attribute
20424 Major Fault
Parameters
ID Name Meaning

board.
4 Humidity Status l 0=Normal

l 1=High
l 2=Low
Impact on System
The humidity that exceeds the upper or lower limitation has an impact on the normal running of
the system.
System Actions
None.
1-322 (2008-06-24)
Possible Causes
The humidity of the system work environment exceeds the upper or lower limitation.
Handling Procedure
Step 1 If the humidity exceeds the lower limitation, use a moistener.
Step 2 If the humidity exceeds the upper limitation, use a dehumidifier.
----End
1.205 20425 Abnormal External Analog Sensor

Description
This alarm is reported when the measurement value of the external analog sensor on the power
distribution box or the environment monitoring device exceeds the setting range.
Attribute
20425 Major Fault
Parameters
ID Name Meaning

board.
4 Simu Status l 0=Normal

l 1=High
l 2=Low
(2008-06-24) 1-323
Impact on System
The environment of the equipment room is abnormal, such as the temperature or the humidity
exceeds the upper or lower limitation (A specific alarm is determined according to the accessed
sensor type.).
System Actions
Whether the alarm persists or the alarm is cleared depends on the actual detection value of the
external analog sensor.
Possible Causes
The detection value of the external analog sensor exceeds the upper or lower limitation.
Handling Procedure
Check whether the cabinet or the temperature and the state of the equipment room that reports
the alarm is normal. If an abnormality exists, related measures used for improvement are taken
to check whether the alarm is cleared.
----End
1.206 20426 Abnormal External Digital Sensor

Description
This alarm is reported when the switch signals of the external digital sensor on the power
distribution box or the environment monitoring device are abnormal.
Attribute

20426 Major Fault
Parameters
ID Name Meaning

1-324 (2008-06-24)
ID Name Meaning
board.
4 Num Status l 0=Restore

l 1=Alarm
Impact on System
The environment of the equipment room is abnormal, such as the door of the cabinet is open
illegally, water penetrates the equipment room, the equipment room catches fire, or the smoke
is thick. The abnormal environment of the equipment room has an impact on the normal running
of the system.
System Actions
Whether the alarm persists or the alarm is cleared depends on the actual detection value of the
external digital sensor.
Possible Causes
The door status switch of the cabinet, the water sensor, or the smoke sensor is triggered.
Handling Procedure
Check whether the cabinet where the alarmed sensor is located is normal. Check whether the
environment and state of the equipment room are normal. If there are any abnormalities, take
corresponding measures. Then check whether the alarm is cleared.
----End
1.207 20427 Abnormal PDB Output Switch Sensor

Description
This alarm is reported when a tripping operation or a manual power-off operation occurs on the
input switch of the power distribution box.
Attribute

20427 Major Fault
(2008-06-24) 1-325
Parameters
ID Name Meaning
2 Logical Slot No. 0=0Powerbox Monitor
3 Sensor No. l 0=Powerbox Output Switch One

l 1=Powerbox Output Switch Two
l 2=Powerbox Output Switch Three
l 3=Powerbox Output Switch Four
l 4=Powerbox Output Switch Five
l 5=Powerbox Output Switch Six
l 6=Powerbox Output Switch Seven
l 7=Powerbox Output Switch Eight
l 8=Powerbox Output Switch Nine
l 9=Powerbox Output Switch Ten
l 10=Powerbox Output Switch Eleven
l 11=Powerbox Output Switch Twelve
l 12=Powerbox Output Switch Thirteen
l 13=Powerbox Output Switch Fourteen
l 14=Powerbox Output Switch Fifteen
l 15=Powerbox Output Switch Sixteen
l 16=Powerbox Output Switch Seventeen
l 17=Powerbox Output Switch Eighteen
l 18=Powerbox Output Switch Nineteen
l 19=Powerbox Output Switch Twenty
4 Switch Status l 0=On

l 1=Off
Impact on System
l The load connected to the output control switch is overcurrent or short-circuit.
l Manual power-off operation.
System Actions
None.
Possible Causes
The system is overcurrent and the board is protected.
1-326 (2008-06-24)
Handling Procedure
Make sure that the electric connection of the corresponding load is normal(check whether the
load of power supply is short-circuited). Rectify the fault, and check whether the alarm is cleared.
Y> The alarm is cleared. The alarm handling is complete.
N> The alarm persists. Please contact Motorola for technical support.
----End
1.208 20428 Abnormal PDB Power Sensor

Description
This alarm is reported when the working power supply of the WDMB in the power distribution
box is faulty.
Attribute
20428 Major Fault
Parameters
ID Name Meaning
board.
4 Power Info l 0=Normal

l 1=Abnormal
Impact on System
l If the working power module (voltage: 5 V) on the MDMC is faulty, the communication
of the MDMC is invalid. The alarm 1.178 20272 Monitor Board Out of Positionon the
LMT.
l If the power supply module of the sensor on the MDMC is faulty, the external sensors (such
as water immersion sensor and smoke sensor), the power distribution output switch, and
the lightning protection cannot be detected. Thus other alarms are generated.
System Actions
None.
(2008-06-24) 1-327
Possible Causes
The power module has no output.
Handling Procedure
Change the power distribution monitor and control board, and check whether the alarm is cleared.
----End
1.209 20429 Abnormal PDB Lightning Protection Sensor

Description
This alarm is reported when the lightning protection board in the power distribution box is
damaged by a lightning strike.
Attribute

20429 Major Fault
Parameters
ID Name Meaning
board.
4 Thunder Status l 0=Normal

l 1=Abnormal
Impact on System
When the alarm is reported, if the lightning protection board in the power distribution box is
invalid, another lightning strike has an impact on the normal running of the system.
System Actions
None.
1-328 (2008-06-24)
Possible Causes
The lightning protection board is damaged by a lightning strike.
Handling Procedure
Change the lightning protection board (remove and reinsert it with power), and then check
----End
1.210 20430 Fan Box Temperature Sensor Invalidation

Description
This alarm is reported when the temperature sensor of the fan box is faulty.
Attribute

20430 Major Fault
Parameters
ID Name Meaning
2 Logical Slot No. 1=1Fanbox Monitor
board.
4 Sensor Work Status l 0=Normal

l 1=Abnormal
Impact on System
The temperature control and speed adjustment mode of the Fan Control Unit (PFCU) in the fan
box may be affected. The temperature control and speed adjustment mode cannot work normally.
System Actions
The invalidation of the temperature sensor cannot be recovered.
(2008-06-24) 1-329
Possible Causes
The fan temperature sensor is invalid.
Handling Procedure
Step 1 Check the speed adjustment mode of the fan through the LMTIf the hardware auto mode is used,
the temperature control mode is not reliable.
On the LMT,Set the speed adjustment mode of the fan to software or manual speed adjustment
mode to control the fan speed.
Step 2 If the spare parts are available, change the fan box.
----End
1.211 20431 Fan Block Alarm

Description
The alarm is reported in case of fan block.
Attribute
20431 Major Fault
Parameters
ID Name Meaning
1 Subrack No. The number of the subrack
3 Sensor No. The number of the sensor that resides in the board
4 Fan Rate Status 0=Normal,1=Block
Impact on System
Fan block affects system running environment, such as temperature and humidity.
System Actions
Due to mechanical invalidation, such as fan axes fault, the fan block cannot be rectified.
1-330 (2008-06-24)
Possible Causes
,1000RPM.
Handling Procedure
Step 1 Check whether the air filter is functional.
Y => Go to step 3.
N => Clean the air filter and then install it. For the method of installing the air filter, refer to the
BSC6000 Parts Replacement Guide. Go to step 2.
Step 2 Check whether the fan rev is nomal. The full rev is 4000 RPM.
Step 3 Replace the fan subrack and check whether the alarm is cleared.
NOTE
Remove the faulty fan subrack and insert a new fan subrack soon. The interval should be less than five minutes.
----End
1.212 20433 Fan Board Hardware Failure Alarm

Description
This alarm is reported when a hardware failure occurs to the fan monitoring board.
Attribute
20433 Major Fault
Parameters
ID Name Meaning
board.
4 HW Work Status l 0=Normal

l 1=Abnormal
(2008-06-24) 1-331
Impact on System
l If the power connector is invalid, there is no system action.
l If the fan power module is faulty, the fan rev remains the same but the reliability is low.
System Actions
l The power connector is invalid or the connection is poor, possibly causing the fan is
powered off.
l The fan power module is faulty, possibly causing the fan box is not operational.
Possible Causes
l A hardware failure occurs to the fan monitoring board.
l The power connector is invalid or the connection is poor.
l The fan power module is faulty.
Handling Procedure
Replace the fan subrack and check whether the alarm is cleared.
NOTE
Remove the faulty fan subrack and insert a new fan subrack soon. The interval should be less than five minutes.
----End
1.213 20434 Board Register Successfully Alarm

Description
Indicate the monitor board having regisered to host.
Attribute
20434 Major Event
Parameters
ID Name Meaning
2 Logical Slot No. 0=0Powerbox Monitor,1=1Fanbox Monitor,2=2Environment

Monitor
1-332 (2008-06-24)
ID Name Meaning
3 Board Instance No. The number of the board
4 Status Value 0=Registered,1=Unregistered
Impact on System
System Actions
None.
Possible Causes
Handling Procedure
None.
----End
1.214 20435 Failure in One Power Supply for the Fan Box
Description
The fan subrack has two powers. This alarm is reported when either of the two power supplies
in the fan subrack is off.
Attribute

20435 Major Fault
Parameters
ID Name Meaning
3 Sensor No. This parameter indicates the number of the sensor that resides
in the board.
(2008-06-24) 1-333
ID Name Meaning
4 FAN Power Down Status l 0=Power Up
l 1=Power Down
Impact on System
l The power connector is invalid.
l The power supply system is faulty.
System Actions
None.
Possible Causes
Either of the two power supplies in the fan subrack is off.
Handling Procedure
Check the working status of the power supply system and cable connection. If the power supply
system is not operational or the cable is faulty, perform the troubleshooting methods. Check
----End
1.215 20436 Abnormal PDB Monitoring Board Component

Description
This alarm is reported when a component on the monitoring board in the power distribution box
is faulty.
Attribute
20436 Major Fault
Parameters
ID Name Meaning
1-334 (2008-06-24)
ID Name Meaning
board.
4 HW Work Status l 0=Normal

l 1=Faulty
Impact on System
The monitoring function of the power distribution box is affected.
System Actions
None.
Possible Causes
The fault may lie in AD7828 or EEPROM on the monitoring board in the power distribution
box.
Handling Procedure
Replace the monitoring board with a new one and check whether the alarm is cleared.
----End
1.216 20951 Status Change Event Alarm

Description
This alarm is reported when the board status changes from active status to standby status or from
standby status to active status.
Attribute
20951 Minor Fault
(2008-06-24) 1-335
Parameters
ID Name Meaning


4 Active/standby state after the change l 0=Active

l 1=Standby
5 Active/standby state before the change l 0=Active

l 1=Standby
Impact on System
The switchover between the active and standby boards is performed. There is no impact on the
service.
System Actions
The board that is switched over from the active state to the standby state is reset.
Possible Causes
l The board is manually switched over through the LMT.
l The active board before the switchover is reset or pulled out.
l The active board before the switchover is faulty.
Handling Procedure
None.
----End
1.217 20954 8k Clock reference source 0 from mainboard to

BackPlane fault alarm
Description
This alarm is reported when there is abnormality in BackPlane 8k Clock Signal(No.0).
1-336 (2008-06-24)
Attribute
20954 Major Fault
Parameters
ID Name Meaning
2 Slot No. This parameter indicates the number of the slot.
3 CPU No. This parameter indicates the number of the CPU.
Impact on System
This will interrupt services.
System Actions
None.
Possible Causes
l The input signal for clock reference is lost.
l The frequency offset of input signal for clock reference goes beyond the pull-in range.
Handling Procedure
Step 1 Check whether this alarm is generated by all the service boards in the subrack.
Y => Go to Step 2.
N => Go to Step 3.
Step 2 If the GSCU is not inserted tightly, insert the GSCU tightly, and then Check whether the alarm
is cleared.
N => Go to Step 3.
Step 3 If the service board is not inserted tightly, insert the service board tightly, and check whether
N => Go to Step 4.
Step 4 If the service board may be damaged, replace the service board, and then check whether the
alarm is cleared.
N => Go to Step 5.
(2008-06-24) 1-337
Step 5 If the mux board is damaged, replace the mux board, and check whether the alarm is cleared.
N => Go to Step 6.
Step 6 The backplane may be damaged physically. Please contact Motorola for technical support.
----End
1.218 20955 8k Clock reference source 1 from mainboard to

Description
This alarm is reported when there is abnormality in BackPlane 8k Signal (No.1).
Attribute
20955 Major Fault
Parameters
ID Name Meaning
Impact on System
System Actions
None.
Possible Causes
Handling Procedure
Y => Go to Step 2.
1-338 (2008-06-24)
N => Go to Step 3.
Step 2 If the GSCU is not inserted tightly, insert the GSCU tightly, and check whether the alarm is
cleared.
N => Go to Step 3.
Step 3 If the service board is not inserted tightly, insert the service board tightly, and then check whether
N => Go to Step 4.
alarm is cleared.
N => Go to Step 5.
Step 5 If the mux board is damaged, replace the mux board, and then check whether the alarm is cleared.
N => Go to Step 6.
----End
1.219 20956 19M SDH Clock reference source from

Description
This alarm is reported when there is abnormality in BackPlane 19M SDH Signal.
Attribute
20956 Major Fault
Parameters
ID Name Meaning
Impact on System
(2008-06-24) 1-339
System Actions
None.
Possible Causes
Handling Procedure
Y => Go to Step 2.
N => Go to Step 3.
Step 2 If the GSCU is not inserted tightly, insert the GSCU tightly, and then check whether the alarm
is cleared.
N => Go to Step 3.
Step 3 If the service board is not inserted tightly, insert the service board tightly, and then check whether
N => Go to Step 4.
alarm is cleared.
N => Go to Step 5.
N => Go to Step 6.
----End
1.220 20957 8k SDH Clock reference source from BackPlane

fault alarm
Description
This alarm is reported when there is abnormality in BackPlane 8k SDH Signal.
Attribute
20957 Major Fault
1-340 (2008-06-24)
Parameters
ID Name Meaning
Impact on System
System Actions
None.
Possible Causes
Handling Procedure
Y => Go to Step 2.
N => Go to Step 3.
is cleared.
N => Go to Step 3.
N => Go to Step 4.
alarm is cleared.
N => Go to Step 5.
N => Go to Step 6.
----End
(2008-06-24) 1-341
1.221 20958 32M TDM Clock reference source from

Description
This alarm is reported when there is abnormality in BackPlane 32M TDM Signal.
Attribute
20958 Major Fault
Parameters
ID Name Meaning
Impact on System
System Actions
None.
Possible Causes
Handling Procedure
Y => Go to Step 2.
N => Go to Step 3.
is cleared.
N => Go to Step 3.
1-342 (2008-06-24)
N => Go to Step 4.
alarm is cleared.
N => Go to Step 5.
N => Go to Step 6.
----End
1.222 20959 8k TDM Clock reference source from BackPlane

fault alarm
Description
This alarm is reported when there is abnormality in BackPlane 8k TDM Signal.
Attribute
20959 Major Fault
Parameters
ID Name Meaning
Impact on System
System Actions
None.
(2008-06-24) 1-343
Possible Causes
Handling Procedure
Y => Go to Step 2.
N => Go to Step 3.
is cleared.
N => Go to Step 3.
N => Go to Step 4.
alarm is cleared.
N => Go to Step 5.
N => Go to Step 6.
----End
1.223 20960 2M Clock reference source 0 from up subboard

fault alarm
Description
This alarm is reported when there is abnormality in 2M Signal(No.0) From SubBoardUp.
Attribute

20960 Major Fault
1-344 (2008-06-24)
Parameters
ID Name Meaning
Impact on System
The recovered receive data clock can't be offered
System Actions
None.
Possible Causes
l The input signal from up subboard is lost.
l The frequency offset of input signal from up subboard goes beyond the pull-in range.
Handling Procedure
Step 1 Check whether the physical connection of the lines is proper.
Y => Go to Step 2.
N => Go to Step 3.
Step 2 If the service board is damaged, replace the service board, and then check whether the alarm is
cleared.
N => Go to Step3.
----End
1.224 20961 2M Clock reference source 1 from up subboard

fault alarm
Description
This alarm is reported when there is abnormality in 2M Signal(No.1) From SubBoardUp.
(2008-06-24) 1-345
Attribute
20961 Major Fault
Parameters
ID Name Meaning
Impact on System
System Actions
None.
Possible Causes
l The input signal from up subboard is lost.
l The frequency offset of input signal from up subboard goes beyond the pull-in range.
Handling Procedure
Y => Go to Step 2.
N => Go to Step 3.
alarm is cleared.
N => Go to Step3.
----End
1-346 (2008-06-24)
1.225 20962 2M Clock reference source from down subboard

fault alarm
Description
This alarm is reported when there is abnormality in 2M Signal From SubBoardDown.
Attribute
20962 Major Fault
Parameters
ID Name Meaning
Impact on System
System Actions
None.
Possible Causes
l The input signal from down subboard is lost.
l The frequency offset of input signal from down subboard goes beyond the pull-in range.
Handling Procedure
Y => Go to Step 2.
N => Go to Step 3.
Step 2 The service board may be damaged, replace the service board, and the check whether the alarm
is cleared.
N => Go to Step3.
(2008-06-24) 1-347
----End
1.226 20963 Number of E1 Frame Slips Within 24 Hours Over

Threshold
Description
This alarm is reported when the number of frame slips within 24 hours exceeds the alarm
threshold (default: 4), which will result in a drop in QoS.
Attribute
20963 Warning Fault
Parameters
ID Name Meaning
1 Subrack No. This parameter indicated the number of the subrack.
2 Slot No. This parameter indicated the number of the slot.
3 CPU No. This parameter indicated the number of the CPU.
4 Link No. This parameter indicated the number of the Link.
5 Frame Slips Number This parameter indicated the number of slip frames.
Impact on System
The relay services distributed on this E1 will be affected while common calls will not. However,
data services with a high demand on BER will be affected.
System Actions
None.
Possible Causes
Loss of system clock synchronization. The system clock is asynchronous.
Handling Procedure
Step 1 Check whether the E1 cables are well grounded and whether the shielding layers of the cables
are in good condition.
1-348 (2008-06-24)
Y => Go to 2.
N => Make the cables well grounded or replace the faulty cables. If the fault is cleared, end the
handling. Otherwise go to step2.
Step 2 Check whether the transmission devices or cables are in good condition.
Y => Go to 3.
N => Replace the faulty cables and devices. If the fault is cleared, end the handling. Otherwise
go to 3.
Step 3 Use the command LST CLKSRC to check whether the clock resource of this board is correctly
configured.
Y => Go to 4.
N => Modify the clock configuration. If the fault is cleared, end the handling. Otherwise go to
4.
Step 4 Check whether the clock resource of the peer equipment is correctly configured.
Y => Go to 5.
N => Modify the clock resource of the peer equipment. If the fault is cleared, end the handling.
Otherwise go to 5.
Step 5 Contact the technical support engineers of the RNC or CBSC.
----End
1.227 20964 Number of E1 Frame Slips Within 24 Hours Over

Max Threshold
Description
This alarm is reported when the number of frame slips within 24 hours exceeds the maximum
alarm threshold (default: 255), which will result in a drop in QoS.
Attribute

20964 Warning Fault
Parameters
ID Name Meaning
(2008-06-24) 1-349
ID Name Meaning
4 Link No. This parameter indicates the number of the Link.
5 Frame Slips Number This parameter indicates the number of slip frames.
Impact on System
The relay services distributed on this E1 will be affected while common calls will not. However,
data services with a high demand on BER will be affected.
System Actions
None.
Possible Causes
Loss of system clock synchronization.
Handling Procedure
Step 1 Check whether the E1 cables are well grounded and whether the shielding layers of the cables
are in good condition.
Y => Go to 2.
N => Make the cables well grounded or replace the faulty cables. If the fault is cleared, end the
handling. Otherwise go to 2.
Step 2 Check whether the transmission devices or cables are in good condition.
Y => Go to 3.
N => Replace the faulty cables and devices. If the fault is cleared, end the handling. Otherwise
go to 3.
Step 3 Use the command LST CLKSRC to check whether the clock resource of this board is correctly
configured.
Y => Go to 4.
N => Modify the clock configuration. If the fault is cleared, end the handling. Otherwise go to
4.
Step 4 Check whether the clock resource of the peer equipment is correctly configured.
Y => Go to 5.
N => Modify the clock resource of the peer equipment. If the fault is cleared, end the handling.
Otherwise go to 5.
----End
1-350 (2008-06-24)

Description
This alarm is reported when the voltage of the board is abnormal.
Attribute
20965 Major Fault
Parameters
ID Name Meaning
4 Voltage Type This parameter indicates the type of the voltage that triggers an alarm.
5 Voltage Value This parameter indicates the Voltage when this alarm is generated.
Impact on System
The quality of the service that the board bears may be decreased or the service is interrupted.
System Actions
Possible Causes
The board hardware fails.
Handling Procedure
(2008-06-24) 1-351
----End
1.229 20966 SubBoard not exist

Description
This alarm is reported when the subBoard is abnormal.
Attribute

20966 Major Fault
Parameters
ID Name Meaning
4 Sub-board slot No. This parameter indicates the number of SubBoard.
Impact on System
The related services will be interrupted .
System Actions
None.
Possible Causes
PIU SubBoard Abnormal
Handling Procedure
Check the subboard and the in and out parts of the bottom plate. Insert the subboard tightly.
----End
1-352 (2008-06-24)
1.230 20967 OPT Module electrical current exceed high

Threshold
Description
This alarm is reported when the OPT Module electrical current exceed high Threshold
Attribute

20967 Major Fault
Parameters
ID Name Meaning
Impact on System
The OPT Module may be abnormal and affect the traffic.
System Actions
None.
Possible Causes
The environment is abnormal.
Handling Procedure
Contact the technical support engineers of the RNC or CBSC.
----End
(2008-06-24) 1-353
1.231 20968 OPT Module electrical current exceed low

Threshold
Description
This alarm is reported when the OPT Module electrical current exceed low threshold.
Attribute

20968 Major Fault
Parameters
ID Name Meaning
Impact on System
The OPT Module may be abnormal and affect the traffic.
System Actions
None.
Possible Causes
Handling Procedure
----End
1-354 (2008-06-24)
1.232 20969 Ethernet Link failure

Description
This alarm is reported when the FE port which on the board has configured with an IP address,
but there's no packets send or receive in this port.
Attribute
20969 Major Fault
Parameters
ID Name Meaning
4 Link No. This parameter indicates the Number of the Link.
Impact on System
The performance of system may be affected and the related services may be interrupted .
System Actions
None.
Possible Causes
Handling Procedure
Step 1 Check whether the Ethernet cable or optical fiber is correctly connected.
Step 2 Perform loopback test on the FE port of the board. If the alarm is cleared, the fault lies in the
transmission. In this case, clear the transmission fault.
----End
(2008-06-24) 1-355
1.233 20970 Ethernet Link Receive Defect Indication

Description
This alarm is reported when the FE port which on the board has configured with an IP address,
and we can send packets normally but can't receive packets correctly in this port.
Attribute
20970 Minor Fault
Parameters
ID Name Meaning
Impact on System
The performance of system may be affected
System Actions
None.
Possible Causes
Handling Procedure
Step 2 Perform loopback test on the FE port of the board. If the alarm is not cleared, the fault lies in
the hardware of FE subboard. In this case, reset the board. If the fault persists, replace the FE
subboard or go to step 3.
1-356 (2008-06-24)
----End
1.234 20971 Ethernet Link Send Defect Indication

Description
This alarm is reported when the FE port which on the WFGI/WGOI has configured with an IP
address, and we can receive packets normally but can't send packets correctly in this port.
Attribute
20971 Minor Fault
Parameters
ID Name Meaning
Impact on System
The performance of system may be affected
System Actions
None.
Possible Causes
Handling Procedure
Step 2 Perform loopback test on the FE port of the board. If the alarm is not cleared, the fault lies in
the hardware of FE subboard. In this case, reset the board. If the fault persists, replace the FE
subboard or contact Motorola for technical support.
(2008-06-24) 1-357
----End
1.235 20972 Ethernet Link Loop

Description
This alarm is reported when the FE port which on the WFGI/WGOI has configured with an IP
address, and it's line looped by user.
Attribute
20972 Warning Fault
Parameters
ID Name Meaning
5 Loop Type l 0=no Loop

l 1=Line Loop Mode
l 2=System Loop Mode
Impact on System
The performance of system may be affected and the related services may be interrupted .
System Actions
None.
Possible Causes
l Use the command SET ETHPORT,set Loop Mode "Line_Loop".
l The connection of the FE port is faulty.
Handling Procedure
Step 1 Use the command SET ETHPORT,set Loop Mode "No_Loop".
1-358 (2008-06-24)
Step 2 Check whether the connection of the WFIE/WFEE FE port is correct, or go to 3.
----End
1.236 20973 OPT Module Temprature exceed high

Threshold
Description
This alarm is reported when the OPT module temprature exceeds high threshold.
Attribute
20973 Major Fault
Parameters
ID Name Meaning
Impact on System
The OPT module may be abnormal and affect the traffic.
System Actions
None.
Possible Causes
Handling Procedure

----End
(2008-06-24) 1-359
1.237 20974 OPT Module Temprature exceed low Threshold

Description
This alarm is reported when the OPT module temprature exceeds low threshold.
Attribute
20974 Major Fault
Parameters
ID Name Meaning
Impact on System
System Actions
None.
Possible Causes
Handling Procedure

----End
1.238 20975 OPT Module Voltage exceed high Threshold

Description
This alarm is reported when the OPT module voltage exceeds high threshold.
1-360 (2008-06-24)
Attribute
20975 Major Fault
Parameters
ID Name Meaning
Impact on System
System Actions
None.
Possible Causes
Handling Procedure
----End
1.239 20976 OPT Module Voltage exceed low Threshold

Description
This alarm is reported when the OPT module voltage exceeds low threshold.
Attribute
20976 Major Fault
(2008-06-24) 1-361
Parameters
ID Name Meaning
Impact on System
System Actions
None.
Possible Causes
Handling Procedure

----End
1.240 20977 Failure of High-Speed Communication Link on

the Backplane of Service Boards
Description
Back Broad GE Link Down of Interface Broad
Attribute
20977 Major Fault
1-362 (2008-06-24)
Parameters
ID Name Meaning
2 Slot No. The number of the slot
3 CPU No. The number of the CPU
4 Link No. 0=link connected with the 7th slot GSCU,1=link connected with the 6th slot
GSCU
Impact on System
System Actions
If the other GE link is normal, the service is switched to the normal GE link.
Possible Causes
Handling Procedure
Check whether the SCU board is in position.

----End
1.241 20978 COMM Channel Abnormal

Description
This alarm is reported when the CORE and ME communication is not exist.
Attribute
(2008-06-24) 1-363
Parameters
ID Name Meaning
4 Comm. Channel No. This parameter indicates the number of Communication Channel.
Impact on System
System Actions
None.
Possible Causes
AEU/PEU/AOU/UOI/FG2/GOU core and ME communication is abnormal.
Handling Procedure
This alarm is an indication and can be paid less attention to.

----End

Description
This alarm is reported when the board chip is faulty.
Attribute
20979 Major Fault
Parameters
ID Name Meaning
1-364 (2008-06-24)
ID Name Meaning
4 Chip Type l 8=GE interface chip

l 9=TDM switch chip
l 14=E1 interface chip
l 17=Optical interface chip
l 51=bridge chip
l 128=PIU_SDRAM,129=PIU_SRAM
l 130=PIU_FLASH,131=PIU_CPLD
l 132=PIU_FPGA,133=PIU_VXWORKS
l 134=PIU_GE interface chip
l 135=PIU_FE/GE interface chip
l 136=PIU_E1 interface chip
l 139=PIU_E1 map chip
l 141=PIU_PPP/MP link layer process chip
l 143=PIU_SUBFPGA
l 144=PIU_SUBCPLD
l 145=PIU_SUBSRAM
l 146=PIU_EEPROM
l 147=PIU_SUB_BOARD_UP
l 148=PIU_SUB_BOARD_DOWN
l 149=PIU_NPMAC
5 Chip No. This parameter indicates the number of chip index.
Impact on System
The quality of the service that the board bears may be decreased or the service is interrupted.
System Actions
if the standby is ready for the operation, after switchover reset the board.
l Handling of the standby board in the active/standby operation mode: Reset board.
(2008-06-24) 1-365
l Handling of the board in the Independent operation mode: Reset board..
Possible Causes
The board hardware is failure.
Handling Procedure
----End
1.243 20980 Ethernet Port Band Width Change

Description
This alarm is reported when the FE port band width is changed.
Attribute
20980 Major Event
Parameters
ID Name Meaning
5 Speed Mode l 0=10M

l 1=100M
l 2=1000M
Impact on System
The services may be interrupted .
1-366 (2008-06-24)
System Actions
None.
Possible Causes
The speed of Ethernet link changes.
Handling Procedure
Ensure that the peer end supports self-negotiation of 100M&1000M line rate, and then set the
Ethernet property as self-negotiation.
----End
1.244 20981 Ethernet Port Duplex Mode Change

Description
This alarm is reported when the FE port Duplex Mode changes .
Attribute
20981 Major Event
Parameters
ID Name Meaning
2 Slot No. The number of the slot
3 CPU No. The number of the CPU
4 Link No. The Number of the Link
5 Duplex Mode 0=FE Link Duplex Half,1=FE Link Duplex Full
Impact on System
Link Duplex Mode changed to Half may affact the transmision
System Actions
None.
(2008-06-24) 1-367
Possible Causes
l config to Half Duplex
l port AutoNeg only support Half Duplex
l one port manual config and one is AutoNeg
Handling Procedure
Step 1 reconfig the 2 port AutoNeg
----End
1.245 20982 OPT Module rx power exceed high Threshold

Description
This alarm is reported when the OPT module rx power exceeds high threshold.
Attribute
20982 Major Fault
Parameters
ID Name Meaning
Impact on System
System Actions
None.
Possible Causes
1-368 (2008-06-24)
Handling Procedure

----End
1.246 20983 OPT Module rx power exceed low Threshold

Description
This alarm is reported when the OPT module rx power exceeds low threshold.
Attribute
20983 Major Fault
Parameters
ID Name Meaning
Impact on System
System Actions
None.
Possible Causes
Handling Procedure

----End
(2008-06-24) 1-369
1.247 20984 OPT Module tx power exceed high Threshold

Description
This alarm is reported when the OPT module tx power exceeds high threshold.
Attribute
20984 Major Fault
Parameters
ID Name Meaning
4 Link No. This parameter indicates the number of the link.
Impact on System
System Actions
None.
Possible Causes
Handling Procedure

----End
1.248 20985 OPT Module tx power exceed low Threshold

Description
This alarm is reported when the OPT module tx power exceeds low threshold.
1-370 (2008-06-24)
Attribute
20985 Major Fault
Parameters
ID Name Meaning
Impact on System
System Actions
None.
Possible Causes
Handling Procedure
----End
1.249 20988 Microcode Thread Abort

Description
This alarm is reported when the IXP2400 is abnormal.
Attribute
20988 Major Fault
(2008-06-24) 1-371
Parameters
ID Name Meaning
4 ME No. This parameter indicates the number of MicroEngine.
Impact on System
System Actions
if the standby is ready for the operation, after switchover reset the board.
l Handling of the standby board in the active/standby operation mode: reset board.
l Handling of the board in the Independent operation mode: Reset board.
Possible Causes
The AEU/PEU/AOU/UOI/FG2/GOU microcode thread is abnormal.
Handling Procedure
Perform switchover or reset the board.
----End
1.250 21001 LAPD Link Congestion

Description
This alarm is reported when the length of the LAPD send queue is greater than the upper limit
of the set congestion threshold. After the LAPD link congestion alarm is reported, the LAPD
link congestion recovery alarm is generated if the length of the LAPD send queue is smaller than
the lower limit of the set congestion threshold.
Attribute
21001 Major Fault
1-372 (2008-06-24)
Parameters
ID Name Meaning
1 Link No. This parameter indicates the number of the congested link.
carrying the congested link is located.
3 Slot No. This parameter indicates the number of the slot where the board carrying
the congested link is located.
4 E1 No. This parameter indicates the number of the E1 port corresponding to the
congested link.
Impact on System
l The improper threshold settings or the overgreat traffic volume will slow down the service
processing speed.
l The faulty E1 cable or the faulty peer end will disrupt the services.
System Actions
l When the system reports the alarm, it also reports the LAPD link status to the MTLS (upper-
layer module corresponding to LAPD). Then the MTLS automatically performs flow
control according to the link status and sets the congestion attribute of the LAPD link to
the congested state.
l At the same time, the messages are sent to the peer end (BTS or PCU). If the length of the
message queue is smaller than the lower congestion limit, a recovery alarm is automatically
reported and the link status is reported to the MTLS. Set the congestion attribute of the
LAPD link to the decongested state. The MTLS can delivers messages.
Possible Causes
l The setting of the congestion threshold is unreasonable. The recommended values of the
upper and lower limits are 80 and 60 separately.
l The singling traffic is overgreat and temporary congestion is caused.
l The E1 cable that connects the BSC and the BTS or the BSC and the PCU is faulty. (The
cable is loose or damaged).
l The BTS or the PCU at the peer end is faulty.
Handling Procedure
Step 1 After the congestion alarm is reported for one minute, Check whether the alarm can be cleared
automatically.
N => Go to step 2.
Step 2 Check whether the threshold setting is reasonable. The recommended values of the upper and
lower limits are 80 and 60 separately.
(2008-06-24) 1-373
Y => Go to step 3.
N => Change the threshold.
Step 3 Check whether the connection of the E1 cable is loose or faulty.

Y => Go to 4.
N => Go to step 5.
Step 4 Tighten or change the E1 cable.

N=>The alarm persists. Go to step 5.
Step 5 Check whether the BTS or the PCU at the peer end is abnormal.
Y => Notify the maintenance personnel at the peer end to handle the alarm. The alarm handling
is complete.
----End
1.251 21002 Broken LAPD Link

Description
This alarm is reported when the LAPD link cannot receive any message from the BTS, PCU or
TC at the peer end.
Attribute
Parameters
ID Name Meaning
1 Link No. This parameter indicates the number of the broken link.
2 Subrack No. This parameter indicates the number of the subrack where the broken link
is located.
3 Slot No. This parameter indicates the number of the slot where the board carrying
the broken link is located.
4 E1 No. This parameter indicates the number of the E1 port carrying the broken link.
Impact on System
l The faulty E1 cable or the faulty peer end will disrupt the services.
1-374 (2008-06-24)
l If the network is not stable, the system will automatically restore to the normal state.
System Actions
The system reports the alarm and the LAPD link is switched over to the state ready for link setup.
A request for link setup is sent to the PCU or the BTS at the peer end every five seconds. After
the E1 cable is normal or the network is stable, the system sends a recovery alarm within five
seconds. The LAPD link restores to the normal state.
Possible Causes
l The network is unstable and the intermittent link is caused.
l The E1 cable is faulty.
l The BTS or the PCU at the peer end is faulty.
Handling Procedure
Step 1 Wait for about one minute, and then observe whether the alarm is cleared automatically in the
Browse Alarm window on the LMT.
Step 2 Tighten the E1 cables, and then check whether the alarm is cleared.
Step 3 Change the E1 cables, and then check whether the alarm is cleared.
Step 4 Notify the maintenance personnel at the peer end to check whether the BTS or the PCU at the
peer end is faulty.
Y => Rectify the fault. The alarm handling is complete.
----End
1.252 21019 Failed Loading of Board Software

Description
This alarm is reported when the loading of software files fails and the board cannot work
normally during the board startup.
Attribute
(2008-06-24) 1-375
Parameters
ID Name Meaning
1 Subrack No. This parameter indicates the number of the subrack where the board on
which the loading fails is located.
2 Slot No. This parameter indicates the number of the slot where the board on which
the loading fails is located.
3 CPU No. This parameter indicates the number of the CPU on which the loading fails
(GXPUx has four CPUs numbered from 0 to 3; other boards have only one
CPU numbered 0).
Impact on System
The corresponding board or CPU is not available. The board cannot work normally.
System Actions
The board is reset automatically. Make an attempt to load software from the GBAM/GOMU. If
the loading fails again, the board will be reset repeatedly with an internal of about 10-30 seconds.
Possible Causes
l The GSCU in the GMPS or where the GBAM/GOMU is located is faulty.
l The communication among the GBAM/GOMU, the GSCU, and the faulty board is
abnormal.
l The files under the directory of the version area on the GBAM/GOMU are damaged.
l The board hardware (such as flash device) is faulty.
Handling Procedure
Step 1 Wait one minute, and then check whether the alarm is cleared.
Y=> The alarm handling is complete.
N=> Go to 2.
Step 2 Observe the RUN indicators on the board panels. If they blink slowly, the boards are operating
at normal levels. Check whether the GBAM/GOMU or the GSCU is faulty.
N => Go to step 3.
Step 3 Check whether there are alarms 1.271 21210 CPU Overloadand1.266 21205 Board Faultin
the Alarm Browse window on the LMT.
Y=> Handle the alarm according to the handling suggestions of alarms 1.271 21210 CPU
Overload and 1.266 21205 Board Fault.
N=> Go to step 4.
Step 4 Check whether the network connection between the GBAM/GOMU and the board is normal.
Check whether the network connection between the GSCU and the board is normal.
1-376 (2008-06-24)
Reinsert or change the Ethernet cable. Then check whether the alarm is cleared.
Step 5 Check whether there is the alarm1.256 21024 GBAM File Check Failurein the Alarm Browse
window on the LMT.
Y => Download the software version again. The alarm handling is complete.
N => Go to step 6.
Step 6 Change the board, and then check whether the alarm is cleared.
----End
1.253 21020 Software Version Inconsistency

Description
The GBAM/GOMU compares the current version matching table and periodically checks the
software files (comprising host program, patch, license file, and extended BIOS) stored on the
flash of the working board in the system. This alarm is reported when the files of inconsistent
versions are detected.
Attribute
21020 Minor Event
Parameters
ID Name Meaning
1 Subrack No. This parameter indicates the number of the subrack where the board on
which the inconsistent versions are detected is located.
2 Slot No. This parameter indicates the number of the slot where the board on which
the inconsistent versions are detected is located.
3 CPU No. This parameter indicates the number of the CPU on which the inconsistent
versions are detected (GXPUx has four CPUs numbered from 0 to 3; other
boards have only one CPU numbered 0).
Impact on System
If the file version is inconsistent with the GBAM/GOMU version, the activation of the file fails
(such as patch License) or after the activation, the file cannot run normally (such as the version
software and the extended BIOS). The normal service might be affected.
(2008-06-24) 1-377
System Actions
None.
Possible Causes
l The board is not correctly upgraded.
l The GBAM/GOMU is not correctly upgraded.
l The file on the GBAM/GOMU is damaged.
Handling Procedure
Step 1 On the LMT, Check whether the version of the software on the faulty board is the latest version.
Y => Go to step 2.
N => Run the online load command (to load the version software, patch, license file or extended
BIOS). The alarm handling is complete.
Step 2 Check whether the alarm1.256 21024 GBAM File Check Failure appears in the Alarm Browse
window on the LMT.
Y => Run the load command (version software, version software, patch, license file or extended
BIOS), load the correct file version again. The alarm handling is complete.
----End
1.254 21022 Faulty Remote Load Agent

Description
This alarm is reported when the relay agent module that is loaded to the remote subrack is faulty.
A board in the remote subrack acts as the remote load agent. The function is to download the
software files required for the board in the remote subrack in advance and buffer the files to
local. Therefore, when other boards in the remote subrack are started or upgraded, the software
is downloaded from the agent instead of from the GBAM/GOMU through the remote
maintenance link. Thus the bandwidth of the link is saved and the startup of the board in the
remote subrack is quickened.
Attribute
21022 Minor Fault
Parameters
ID Name Meaning
1 Subrack No. This parameter indicates the number of the subrack where the remote load
agent is located.
1-378 (2008-06-24)
ID Name Meaning
2 Slot No. This parameter indicates the number of the slot where the remote load agent
is located.
3 CPU No. This parameter indicates the number of the CPU on which the inconsistent
versions are detected (GXPUx has four CPUs numbered from 0 to 3; other
boards have only one CPU numbered 0).
Impact on System
When the boards in the remote subrack are loaded or upgraded, load the software from the
GBAM/GOMU through the remote maintenance link. Because the bandwidth of the remote link
is limited, it takes long to load software on the board in the remote subrack if a great number of
boards in the remote subrack require loading.
System Actions
All the boards load software files from the GBAM/GOMU.
Possible Causes
l The remote load agent board is faulty.
l The remote maintenance link is congested or intermittent.
Handling Procedure
Step 1 Check whether the physical connection between the local board and the remote board is normal.
Check whether the connector is securely inserted or the cable is in good condition. If any trouble
exists, shoot the trouble. Check whether the alarm is cleared.
Step 2 Check whether the remote load agent board runs abnormally. (On the LMT, check whether the
equipment status is normal and whether the agent board has the alarm 1.271 21210 CPU
Overload and1.266 21205 Board Fault in the Alarm Browse window on the LMT).
Y => Abnormal. Go to step 3.
N => Normal. Please contact Motorola for technical support.
Step 3 Switch over or reset the remote load agent board. Then check whether the alarm is cleared.
----End
(2008-06-24) 1-379
1.255 21023 Inconsistent Sub-Board Alarm

Description
This alarm is reported when the installed subrack is not consistent with that configured with the
service board, that is, GDPUx, interface boards, or GXPUx.
Attribute
21023 Minor Fault
Parameters
ID Name Meaning
1 Subrack No. This parameter indicates the number of the subrack where the sub-board
is inconsistent with its configuration.
2 Slot No. This parameter indicates the number of the slot where the sub-board is
inconsistent with its configuration.
3 CPU No. This parameter indicates the number of the CPU on which the
inconsistent versions are detected (GXPUx has four CPUs numbered
from 0 to 3; other boards have only one CPU numbered 0).
4 Checking result l 1=Loading allowed

l 3=Loading not allowed
Impact on System
The relevant board or CPU is unavailable, that is, the service board cannot perform properly.
System Actions
The sub-board keeps resetting with an interval of 10 to 30 seconds.
Possible Causes
The sub-board is configured while it is not physically installed or the sub-board is installed
without configuration in the system.
Handling Procedure
Check whether the configuration of the sub-board in the system is consistent with that being
installed in the subrack.
Y => Replace the sub-board in the subrack or clear the configuration of the board and then
reconfigure with the correct board in the LMT. The alarm handling is complete.
1-380 (2008-06-24)
----End
1.256 21024 GBAM File Check Failure

Description
This alarm is reported when the GBAM/GOMU files check fails.
Attribute
21024 Major Event
Parameters
ID Name Meaning
1 File name This parameter indicates the file name of the file of which the
verification fails.
2 Incorrect reason l 0=File not found

l 1=File inconsistent
3 Version area l 0=active version area

l 1=standby version area
4 File type l 0=patch file

l 1=version software
l 2=secondary BIOS file
l 3=license file
l 4=configuration file
l 5=other files that support loading
5 Patch area l 0=active patch area

l 1=standby patch area
Impact on System
When the board is started or the software is upgraded, if the software is required to be loaded
from the GBAM/GOMU, the start or the upgrade of the board fails.
System Actions
None.
(2008-06-24) 1-381
Possible Causes
l The version software stored on the GBAM/GOMU, the secondary BIOS file, the patch file,
and the license file are manually damaged.
l The file transfer is faulty during the download of the file from the file server.
l The hard disk is damaged.
Handling Procedure
Step 1 Use a file comparison tool such as the BeyondCompare to compare the files in the server with
the released files. Check whether the version software on the file server is consistent with the
formally issued version.
Y => Go to step 2.
N => Download the version software again. The alarm handling is complete.
Step 2 Log in to the GBAM. Check whether the files in the version area are consistent with those on
the file server or in the version release directory.
Y => Go to step 3.
N => Download the version software again. The alarm handling is complete.
Step 3 Check whether the hardware is faulty (check the indicators on the GBAM hardware to confirm
whether the hardware is abnormal).
Y => Change the hardware or switch over the GBAM. The alarm handling is complete.
N => The hardware is normal. Please contact Motorola for technical support.
----End
1.257 21025 Patch not confirm

Description
This alarm is reported when the GBAM/GOMU patch is not confirmed
Attribute
21025 Major Event
Parameters
ID Name Meaning
1 Alarm Reason This parameter indicates the alarm reason.
Impact on System
The unconfirmed patch might cause the abnormality of the system.
1-382 (2008-06-24)
System Actions
None.
Possible Causes
The current patch of the OMU is not confirmed.
Handling Procedure

----End
1.258 21026 GBAM/GOMU License Check Fail Alarm

Description
This alarm is reported when the GBAM license check fails.
Attribute
21026 Major Event
Parameters
ID Name Meaning
1 Reason of check failure l 0=Parsing license error
l 1=License expired,2=No activated license
l 3=License will expire
Impact on System
BSC turns to the minimum configuration after the license invalidates over 7 days.
System Actions
None.
Possible Causes
l Parsing license error.
l License expired.
l No activated license.
l License will expire.
(2008-06-24) 1-383
Handling Procedure
Step 1 Check whether there is valid license on OMU board.
Y =>Go to step 2.
N =>Apply new license from Motorola, and activate the license.
Step 2 Check whether the license is mature.

Y=>Buy new license from Motorola, the inactive the license.
N =>Go to step 3.
Step 3 Check whether the license matches with the configured signal point.
N =>Configure the signal point as the license or apply new license as the signal point.
----End
1.259 21027 Remote EIU/OIU Board Connection Error

Description
This alarm is reported when the EIU/OIU Subrack No. or Slot No. in the remote GTCS is
inconsistent with the configuration. In this case, do not load the EIU/OIU subrack in the remote
GTCS. (If the remote EIU/OIU board is started successfully but the alarm still exists, please
clear the alarm manually.)
Attribute

21027 Major Fault
Parameters
ID Name Meaning
1 Subrack No. Configured remote EIU/OIU This parameter indicates the configured
board's subrack No. remote EIU/OIU board's subrack No.
2 Slot No. Configured remote EIU/OIU This parameter indicates the configured
board's physical slot1 No. remote EIU/OIU board's physical slot1 No.
3 Slot No.2 Configured remote EIU/OIU This parameter indicates the configured
board's physical slot2 No(0xffffffff means remote EIU/OIU board's physical slot2 No.
no backup). (0xffffffff means no backup.)
4 Subrack No. of the remote GTCS Actual This parameter indicates the actual remote
remote EIU/OIU Board's subrack No. EIU/OIU Board's subrack No.
1-384 (2008-06-24)
ID Name Meaning
5 Slot No. of the remote EIU/OIU Actual This parameter indicates the actual remote
remote EIU/OIU Board's slot No. EIU/OIU Board's slot No.
Impact on System
The remote GTCS can not startup.
System Actions
None.
Possible Causes
The wire connection of the remote EIU/OIU board does not match with the configuration.
Handling Procedure
Step 1 Check whether the EIU/OIU board is in position.
Y =>Go to step 2;
N =>Insert the EIU/OIU board into the configured slot, go to step 2.
Step 2 Connect the interface wire to the configured EIU/OIU board. Check whether the alarm is cleared.
Y =>The alarm handling is complete.
Step 3
----End
1.260 21028 Board Physical Type inconsistent

Description
This alarm is reported when the board physical type is inconsistent with the configuration. In
this case, the board is not allowed to start up.
Attribute
21028 Critical Event
(2008-06-24) 1-385
Parameters
ID Name Meaning
1 Subrack No. This parameter indicates the number of the subrack where the physical
board type is inconsistent with its configuration.
2 Slot No. This parameter indicates the number of the slot where the physical
3 CPU No. This parameter indicates the number of the CPU where the physical
4 Physical Type l 1=GSCU

l 2=GCK
l 3=OIU/EIU
l 4=TSU
l 5=XPU
l 6=DPU
l 7=GF2/GOU/PEU
5 Configured Type l 1=GSCU

l 2=GCK
l 3=OIU/EIU
l 4=TSU
l 5=XPU
l 6=DPU
l 7=GF2/GOU/PEU
Impact on System
The board will be forbidded start up.
System Actions
None.
Possible Causes
Board physical type is inconsistent with its configuration.
Handling Procedure
Step 1 Check whether the board 's physical type is consistent with the configuration.
Y =>Please contact Motorola for technical support;
N =>Go to step 2;
1-386 (2008-06-24)
Step 2 Reconfigure the board, and check whether the alarm reporting is keeping on.
N =>The alarm handling is complete.
----End
1.261 21030 Load License to SMU failed

Description
This alarm is reported when load license to SMU failed.
Attribute

21030 Minor Event
Parameters
ID Name Meaning
1 Alarm Reason This parameter indicates the alarm reason.
Impact on System
The license state of NE can not be changed.
System Actions
None.
Possible Causes
Load and active the license file failed.
Handling Procedure
Step 1 Check if there are some boards running abnormally .
Y =>Reconfigure the board and make sure it running normally, Go to step 2;
N => Please contact Motorola for technical support;
Step 2 Check whether the alarm reporting is keeping on.

N =>The alarm handling is complete.
----End
(2008-06-24) 1-387
1.262 21201 DSP Heartbeat Lost

Description
This alarm is reported when the Network Processor (NP) can not receive the heartbeat message
from the DSP in succession.
Attribute

21201 Minor Fault
Parameters
ID Name Meaning
1 Subrack No. This parameter indicated the number of the subrack where the DSP reports
the alarm.
2 Slot No. DSP
3 DSP No. DSP
Impact on System
The DSP is unavailable.
System Actions
The NP resets the DSP.
Possible Causes
No heartbeat message is sent from the DSP or the communication between the NP and DSP is
abnormal.
Handling Procedure
Reset the DSP in the LMT and check whether the alarm is cleared.
N=> The alarm persists. Please contact Motorola for technical support.
----End
1-388 (2008-06-24)
1.263 21202 DSP Overload

Description
This alarm is reported when the load of the DSP exceeds its own processing capability.
Attribute
21202 Minor Fault
Parameters
ID Name Meaning
1 Subrack No. This parameter indicates the number of the subrack where the DSP reports
the alarm.
2 Slot No. DSP
3 DSP No. DSP
Impact on System
The alarm has an impact on the quality of the speech services. The serious overload causes the
DSP fault.
System Actions
None.
Possible Causes
The DSP is overloaded.
Handling Procedure
Step 1 Wait for one minute and check whether the alarm is cleared.
N=> The alarm persists. Go to step 2.
Step 2 Reset the DSP on the LMT, and then check whether the alarm is cleared.
N=> The alarm persists. Please contact Motorola for technical support.
----End
(2008-06-24) 1-389
1.264 21203 DSP Fault

Description
This alarm is reported when the DSP chip is faulty and unavailable.
Attribute
21203 Minor Fault
Parameters
ID Name Meaning
1 Subrack No. This parameter indicates the number of the subrack where the DSP reports
the alarm.
2 Slot No. DSP
3 DSP No. DSP
Impact on System
System Actions
None.
Possible Causes
The DSP chip is abnormal.
Handling Procedure
Step 1 Reset the DSP on the LMT, and then check whether the alarm is cleared.
Step 2 Replace the GDPUx.

----End
1-390 (2008-06-24)
1.265 21204 Unavailable Subrack

Description
This alarm is reported when both active GSCU and standby GSCU are unavailable. Services
related to the subrack are unavailable.
Attribute
Parameters
ID Name Meaning
1 Subrack No. This parameter indicates the number of the faulty subrack.
Impact on System
Both active GSCU and standby GSCU are unavailable. Services related to the subrack are
unavailable.
System Actions
None.
Possible Causes
l The inter-subrack communication is faulty and the inter-subrack heartbeat is lost.
l The logical object of the GSCU in the subrack is reset or abnormal.
Handling Procedure
Step 1 If the main subrack reports the alarm, tighten the Ethernet cable between the main subrack and
the extension subrack. Then check whether the alarm is cleared.
Step 2 Change the Ethernet cable between the main subrack and the extension subrack. Then check
Step 3 If the remote subrack reports the alarm, ensure the E1 cable that connects the local subrack and
the remote subrack tightly. Then check whether the alarm is cleared.
(2008-06-24) 1-391
Step 4 Replace the E1 cable. Then check whether the alarm is cleared.
Step 5 Notify the maintenance personnel to check whether the logical objects in the SCU are available.
Y => The boards are available. Please contact Motorola for technical support.
N => The boards are unavailable. Find out the cause for the unavailability and reset the GSCU.
----End
1.266 21205 Board Fault

Description
This alarm is reported when the operation state of the board is unavailable.
Attribute
Parameters
ID Name Meaning
located.
2 Slot No. This parameter indicates the number of the slot where the faulty board is
inserted.
3 Board Type l 0=GOMU

l 1=GSCU
l 2=GGCU
l 3=GEIUx/GOIUx
l 4=GTNU
l 5=GXPUx
l 6=GDPUx
l 7=GF2/GOU/PEU
Impact on System
The board is unavailable.
1-392 (2008-06-24)
System Actions
None.
Possible Causes
Handling Procedure
Step 1 Reset the board on the LMT, and then check whether the alarm is cleared.
Step 2 Reinsert the board when the traffic is small. Then check whether the alarm is cleared.
Step 3 Repalce the board, and check whether the alarm is cleared.
----End
1.267 21206 CPU Fault

Description
This alarm is reported when the object operation of the CPU is unavailable.
Attribute
Parameters
ID Name Meaning
1 Subrack No. This parameter indicates the number of the subrack where the faulty CPU
is located.
2 Slot No. This parameter indicates the number of the slot where the faulty CPU is
located.
3 CPU No. This parameter indicates the number of the faulty CPU in a board.
(2008-06-24) 1-393
Impact on System
The CPU that reports the alarm is unavailable.
System Actions
None.
Possible Causes
The operation status of the CPU is unavailable.
Handling Procedure
Step 2 Reinsert the board when the traffic is low, and then check whether the alarm is cleared.
Step 3 Replace the board and check whether the alarm is cleared.
----End
1.268 21207 Board Hardware Self-Test Failure of Warning

Level
Description
This alarm is reported when the chip on the board is faulty.
Attribute
21207 Warning Fault
Parameters
ID Name Meaning
1 Subrack No. This parameter indicates the number of the subrack that reports the alarm.
2 Slot No. This parameter indicates the number of the slot that reports the alarm.
1-394 (2008-06-24)
ID Name Meaning
Impact on System
The abnormal board may have a bad impact on the service.
System Actions
None.
Possible Causes
The hardware is abnormal.
Handling Procedure
Step 2 Remove and reinsert the board (You are required to do this when the traffic volume is small).
Then check whether the alarm is cleared.
Step 3 Replace the board, and then check whether the alarm is cleared.
----End
1.269 21208 Board Hardware Self-Test Failure of Minor

Level
Description
Attribute

21208 Minor Fault
(2008-06-24) 1-395
Parameters
ID Name Meaning
Impact on System
System Actions
None.
Possible Causes
Handling Procedure
----End
1.270 21209 Board Hardware Self-Test Failure of Major

Level
Description
1-396 (2008-06-24)
Attribute
21209 Major Fault
Parameters
ID Name Meaning
1 Subrack No. This parameter indicates the number of the subrack that reports the alarm
Impact on System
System Actions
None.
Possible Causes
Handling Procedure
----End
1.271 21210 CPU Overload

Description
This alarm is reported when the CPU is overloaded.
(2008-06-24) 1-397
Attribute
21210 Major Fault
Parameters
ID Name Meaning
4 CPU Usage This parameter indicates the actual utilization of the CPU.
Impact on System
If the CPU is overloaded, the process speed of the PCU is so slow that the board is reset.
System Actions
None.
Possible Causes
The CPU is overloaded.
Handling Procedure
----End
1.272 21211 Board Switchover

Description
The alarm is reported when the board is swapped.
Attribute
21211 Warning Event
1-398 (2008-06-24)
Parameters
ID Name Meaning
1 Subrack No. Number of the subrack where the board is switched over
2 Slot No. Number of the slot where the active board is inserted
3 Swap Result 0=successful swap, 1=failed swap
4 Swap Reason 0=manual swap,1=fault swap
Impact on System
The services may be interrupted for a short time.
System Actions
None.
Possible Causes
l The switchover is performed between the active and standby boards when the active board
receives a major alarm while the standby board is in good condition.
l A manual switchover is performed, such as removing and (or) inserting the board, resetting
the active board, or switching with commands.
Handling Procedure
None.
----End
1.273 21212 DSP TDM Timeslot Link Unavailable

Description
This alarm is reported when the DSP TDM timeslot link is unavailable.
Attribute

21212 Minor Fault
(2008-06-24) 1-399
Parameters
ID Name Meaning
1 Subrack No. Number of the subrack that reports the alarm
2 Slot No. Number of the slot that reports the alarm
3 DSP No. Number of the DSP that reports the alarm
Impact on System
System Actions
None.
Possible Causes
l The reasons for the DSP chip fault are as follows:
l The failure of communication within the board caused by dry joint or aging.
l The timeslots on the DSP port is displaced.
l You can consult the TC log.
Handling Procedure
Step 1 Reset the GDPUC through the LMT and check whether the alarm is cleared.
N => Go to 2.
Step 2 Remove the GDPUC when the traffic volumn is small and check whether the alarm is cleared.
Y => The alarm is cleared. The alarm handling is cleared.
N => Go to step3.
Step 3 Change the GDPUC and check whether the alarm is cleared.
----End
1.274 21213 HA Status Line Fault

Description
This alarm is reported when the HA status lines are fault.
1-400 (2008-06-24)
Attribute

Parameters
ID Name Meaning
generated.
generated.
Impact on System
A potential risk for the normal operation of the system exists.
System Actions
None.
Possible Causes
Handling Procedure
Change the board or subrack.
----End
1.275 21214 OMU Harddisk Overload Alarm

Description
This alarm is reported when the space of OMU hard disk is insufficient.
Attribute

21214 Minor Fault
(2008-06-24) 1-401
Parameters
ID Name Meaning
1 Hard Disk Partition ID l 0=System partition
l 1=Software partition
l 2=Data partition
alarm is generated.
3 Slot No. This parameter indicates the number of the slot where the alarm
is generated.
4 Used Space This parameter indicates the used space of the hard disk.
5 Remaining Space Remaining Space of the Hard Disk
Impact on System
System Actions
None.
Possible Causes
l The space of the system hard disk is small.
l Lots of files are generated and are not deleted in the system.
l There are useless files in the system.
Handling Procedure
Delete all the useless files in the system.
----End
1.276 21215 XPU Port IP Conflict

Description
This alarm is reported when the IP address on the XPU port conflicts with others in the net.
1-402 (2008-06-24)
Attribute
21215 Minor Fault
Parameters
ID Name Meaning
generated.
generated.
3 IP Addr. This parameter indicates the IP address conflict with others in the net.
Impact on System
System Actions
None.
Possible Causes
The IP address on the XPU port conflicts with other XPU ports in the net.
Handling Procedure
Reset IP.
----End
1.277 21216 PowerBox Types Inconsistent

Description
This alarm is reported when the types of the powerbox are inconsistent between the configured
and the inserted.
Attribute
21216 Major Fault
(2008-06-24) 1-403
Parameters
ID Name Meaning
generated.
2 PowerBox Type This parameter indicates the type of powerbox inserted.
Impact on System
The monitoring board in the power distribution box can not work.
System Actions
None.
Possible Causes
The type of the monitoring board in the power distribution box is inconsistent with the data
configuration.
Handling Procedure
Insert the monitoring board in the power distribution box consistent with the data configuration.
----End
1.278 21250 Daemon Heartbeat Lost Alarm

Description
This alarm is reported when the daemon heartbeat is lost.
Attribute

21250 Major Fault
Parameters
ID Name Meaning
generated.
1-404 (2008-06-24)
ID Name Meaning
generated.
Impact on System
The backup and switchover functions are not available.
System Actions
None.
Possible Causes
The standby board is removed or powered off.
Handling Procedure
Step 1 Insert the standby board.
Step 2 Start the Daemon on the standby board.
Step 3 Replace the standby board if it has the fault.
----End
1.279 21251 Daemon Version Not Match Alarm

Description
This alarm is reported when the Daemon version is inconsistent.
Attribute
21251 Major Fault
Parameters
ID Name Meaning
generated.
generated.
(2008-06-24) 1-405
Impact on System
The backup function is not available.
System Actions
None.
Possible Causes
l The Daemon is being upgraded.
l The versions of Daemon running on the two boards are not consistent.
Handling Procedure
Step 1 Upgrade the Daemon with an early version.
Step 2 Replace the boards with those with the same version.
----End
1.280 21252 Backup Channel Between Daemons Break

Alarm
Description
This alarm is reported when the backup channel between Daemons is faulty.
Attribute
21252 Major Fault
Parameters
ID Name Meaning
generated.
generated.
Impact on System
The backup function is not available.
1-406 (2008-06-24)
System Actions
None.
Possible Causes
l The board is removed or powered off.
l The backup is reset.
l The Daemon on the standby board is stopped.
l The backup channel is faulty.
Handling Procedure
Step 3 Replace the standby board if it has the fault.
----End
1.281 21253 Interior Channel Between Daemons Break

Alarm
Description
This alarm is reported when the interior network channel between Daemons is faulty.
Attribute
21253 Major Fault
Parameters
ID Name Meaning
generated.
generated.
Impact on System
(2008-06-24) 1-407
System Actions
None.
Possible Causes
l The board is removed or powered off.
l The board is reset.
l The Daemon on the standby board is stopped.
l The SCU is out of the position or the startup of the SCU fails.
Handling Procedure
Step 3 Replace the SCU if it has the fault.
----End
1.282 21254 OMU Mode Switch Event Alarm

Description
This alarm is reported when the OMU mode is switch.
Attribute
21254 Major Event
Parameters
ID Name Meaning
generated.
generated.
Impact on System
The backup function is provided, when OMU mode is double, this function is forbidden, when
OMU mode is single.
1-408 (2008-06-24)
System Actions
None.
Possible Causes
Switch OMU mode from double to single, or contrarily.
Handling Procedure
None.
----End
1.283 21255 Swap Result Event Alarm

Description
This alarm is reported when the swap result event occurs.
Attribute

21255 Major Event
Parameters
ID Name Meaning
1 Swap Type l 0=Mannually Swap
l 1=DEV Defect Swap
l 2=Force Swap
l 3=Interior Swap
l 4=Daemon Defect Swap
2 Swap Result l 0=Swap success

l 1=Swap fail
Impact on System
The switchover occurs.
System Actions
None.
(2008-06-24) 1-409
Possible Causes
The switchover occurs.
Handling Procedure
None.
----End
1.284 21501 MTP3 DSP Unreachable

Description
l There is no response to the MSC or the message cannot be returned

l There is no available route to the DSP.
Attribute
21501 Major Fault
Parameters
ID Name Meaning
1 Dest Signaling Point Index This parameter indicates a DSP record, which is specified
when configuring the DSP.
2 Network Indicator l 0=International

l 1=International standby
l 2=National
l 3=National standby
3 Dest Signaling Point Code This parameter indicates the code of the DSP in the
signaling network, which is specified when configuring
data of the signaling point.
4 Source Signaling Point Code This parameter indicates the code of the signaling point in
the signaling network, which is specified when configuring
the GXPUM is located.
1-410 (2008-06-24)
ID Name Meaning
GXPUM is located.
7 CPU No. This parameter indicates the number of the CPU where the
GXPUM is located.
Impact on System
The signaling unit cannot be sent by the local signaling point to the DSP. The service is disrupted.
System Actions
MTP3 reports "PAUSE" to notify the SCCP of the destination signaling point unavailable
message. Then the SCCP reports the message to the user plane to stop the DSP services.
Possible Causes
l The signaling links are not configured.
l All the signaling links to the DSP are unavailable.
Handling Procedure
Step 1 Check whether the signaling links to the DSP is configured.
Y => Go to step 2.
N => Configure the signaling links.
For details about how to configure the signaling links, refer to the BSC Initial Configuration
Guide. The alarm handling is complete.
Step 2 Check whether there is a 1.286 21503 MTP3 Link Unavailable before the alarm.
Y=> Refer to the handling suggestions in the Signaling Link Unavailable. The alarm handling
is complete.
N=> The alarm is not cleared. Please contact Motorola for technical support.
----End
1.285 21502 MTP3 Layer 3 Congestion

Description
This alarm is reported when the usage of the cache memory of the layer 3 message exceeds that
of the start threshold in the buffer area of the layer 3 message.
Attribute
21502 Major Event
(2008-06-24) 1-411
Parameters
ID Name Meaning
1 PHY Link No. This parameter indicates the each link has only one number
on the CPU of GXPUM.

l 2=National
5 Signaling Link Code This parameter indicates the only code of the signaling link
in the link set that is a set of links.
6 Buffer Usage This parameter indicates the usage of the cache memory
occupied by the Layer 3 message over this signaling link.
7 Subrack No. This parameter indicates the logical subrack number of the
XPUM CPU to which the signaling link belongs.
8 Slot No. This parameter indicates the logical slot number of the
GPUM CPU to which the signaling link belongs.
GXPUM is located.
Impact on System
When the layer 3 congestion alarm over the signaling link is reported, the user information will
be discarded on the MTP3 layer.
System Actions
The MTP3 reports the congestion primitive to the SCCP, requiring that the SCCP and the SCCP
users lessen the MSUs to eliminate the congestion.
Possible Causes
Too many messages are sent to layer 3.
1-412 (2008-06-24)
Handling Procedure
Step 1 In the Brows Alarm window on the LMT, check whether the alarm is cleared within 10 seconds.
N => Go to step 2.
Step 2 Add a signaling link.

For details about how to add a signaling link, refer to the BSC Initial Configuration Guide.
----End
1.286 21503 MTP3 Link Unavailable

Description
This alarm is reported when the physical layer of the signaling links are faulty, or the links are
deactivated or management inhibited, the available signaling links turn to unavailable.
Attribute

21503 Minor Fault
Parameters
ID Name Meaning
1 PHY Link No. This parameter indicates the number of the link. Each link
has only one number on the CPU of GXPUM.

l 2=National
(2008-06-24) 1-413
ID Name Meaning
GXPUM is located.
GXPUM is located.
1-414 (2008-06-24)
ID Name Meaning
9 Cause This parameter indicates the values of alarm causes are as
follows:
l 0x02: MTP3 sends the stop command.
l 0x08: The MTP2 reports that the location is impossible
during the IAC.
l 0x09: MTP2 receives the abnormal BSN.
l 0x0A: MTP2 receives the abnormal FIB.
l 0x0C: MTP2 receives SIO from the destination point
l 0x0D: MTP2 receives SIN from the destination point.
l 0x0E: MTP2 receives the critical SIE from the
destination point.
l 0x0F: MTP2 receives SIOS from the destination point.
l 0x12: The error rate of the signal rate is high.
l 0x13: T1 (45 seconds) expires.
l 0x14: T6 (5 seconds) expires. The signaling links are
congested for a long time.
l 0x15: T7 (1.5 seconds) expires. The messages are
delayed for a long time.
l 0x17: T3 (1.3 seconds) expires.
l 0x19: The error rate is high.
l 0x1B: MTP3 sends a stop message during the LSC.
l 0x30: Receive the COO signal from the destination
point.
l 0x31: The test of the signaling links fails.
l 0x32: The signaling links are deactivated.
l 0x33: Software on layer 2 is unavailable.
l 0x34: The communication with the management
module stops.
l 0x35: Commands on layer 2 and layer 3 have no
responses.
l 0x36: The physical links are faulty for a long time.
l 0x37: The link switchover expires.
l 0x38: Software data on layer2 are reconfigured.
l 0x40: The local management is prohibited, and the links
are unavailable.
l 0x41: The remote management is prohibited, and the
links are unavailable
l 0x42: The remote processor is faulty.
(2008-06-24) 1-415
ID Name Meaning
l 0x44: Set data in the table again. The system restarts and
reports alarms.
l 0xFF: Other reasons.
Impact on System
l If there is not any other available links in the link set, the route of the link set is unavailable.
l If the DSP of some route has not any other available routes, the DSP cannot be visited. An
alarm is generated indicating that the destination point is inaccessible.
System Actions
The MTP3 will periodically initiates signaling link reestablishment. The link resumes normal
operation once the cause of the link unavailability is cleared.
Possible Causes
l The physical links are faulty.
l The signaling links are deactivated.
l The signaling links are prohibited by the local or remote management.
l The MTP3 links receive the changeover message.
Handling Procedure
Step 1 Check whether the signaling links are unavailable for more than six seconds.
Y => Go to step 3.
N => Go to step 2.
Step 2 On the M2000 traffic management console, check whether the traffic volume is too high.
Y => Add a signaling link.
N => Go to step 3.
Step 3 Through the LMT, check whether there is a 1.266 21205 Board Fault alarm.
Y => Refer to the relative handling suggestion.
N => If the 1.266 21205 Board Fault alarm is cleared or does not exist, but the alarm cannot
be cleared, go to step 4.
Step 4 Check whether the link is deactivated.
Y => Activate the corresponding link. The alarm handling is complete.
----End
1-416 (2008-06-24)
1.287 21504 MTP3 Signaling Link2 Congestion

Description
This alarm is reported when the congestion begin threshold value exceeds the congestion
threshold value.
Attribute
21504 Warning Fault
Parameters
ID Name Meaning
1 PHY Link No. Number of the link
Each link has only one number on the GXPUM CPU
2 Network Indicator 0=0international,1=1internationalstandby,2=2national,

3=3nationalstandby
3 Dest Signaling Point Code Code of the DSP in the signaling network, which is
specified when configuring data of the signaling point
4 Source Signaling Point Code Code of the signaling point in the signaling network, which
is specified when configuring data of the signaling point
5 Signaling Link Code Only code of the signaling link in the link set that is a set
of links
7 Slot No. Number of the slot where the GXPUM is located
8 CPU No. Number of the CPU where the GXPUM is located
Impact on System
When the alarm is reported, the congestion on signaling link 2 will decrease the number of the
MSUs and the transmission quality. In addition, part of the information will be discarded.
System Actions
21502 MTP3 Layer 3 Congestion[/alm].
(2008-06-24) 1-417
Possible Causes
The number of the MSUs saved in the MTP2 send buffer exceeds the congestion start threshold.
Handling Procedure
Step 1 Analyze the load on the signaling link. Check whether the alarm can be cleared by load sharing.
N => Go to step 2.
Step 2 Check the transmission quality. Check whether the error rate is less than 10-6.
Y => Go to step 4.
N => If the error rate is too high, go to step [3].
Step 3 Check whether there exists any clock alarm or hardware alarm concerning the E1.
Y => Clear the clock or the hardware alarm. The alarm handling is complete.
Step 4 Check whether the transmission is delayed.

----End
1.288 21511 MTP3 Link Test Success

Description
This alarm is reported when there is a response after sending the signaling link test message.
Attribute

21511 Warning Event
Parameters
ID Name Meaning

l 2=National
1-418 (2008-06-24)
ID Name Meaning
GXPUM is located.
GXPUM is located.
Impact on System
The link is available.
System Actions
None.
Possible Causes
The link is available.
Handling Procedure
None.
----End
1.289 21512 MTP3 Link Test Failure

Description
This alarm is reported when no acknowledgement message is returned or the acknowledgement
message is returned after long time upon the sending of the signaling link testing message on
the local end.
(2008-06-24) 1-419
Attribute
21512 Warning Event
Parameters
ID Name Meaning

l 2=National
GXPUM is located.
GXPUM is located.
Impact on System
The link is not available.
System Actions
MTP3 sends a stop message to MTP2 to reestablish the link.
1-420 (2008-06-24)
Possible Causes
l The configuration data for connecting two ends is inconsistent, such as SLC, coding scheme
of the source/destination signaling point, coding format, or network indication.
l Layer MTP2 is performing self-loop caused by E1 self-loop or port self-loop.
Handling Procedure
Step 1 Check whether the parameters, such as SLC, coding scheme of the source/destination signaling
point, coding format, or network indication is consistent between the local and peer ends.
Y => Go to step 2.
N => Modify data in the local office. The alarm handling is complete.
Step 2 Check whether the E1 self-loop or the self-loop on the E1 port is performed.
Y => Stop the E1 self-loop or the self-loop of the E1 port. The alarm handling is complete.
----End
1.290 21513 MTP2 Link Location Failure

Description
This alarm is reported when the signaling location fails during the start or recovery of links.
Attribute

21513 Warning Event
Parameters
ID Name Meaning

l 2=National
(2008-06-24) 1-421
ID Name Meaning
GXPUM is located.
GXPUM is located.
1-422 (2008-06-24)
ID Name Meaning
follows:
during the IAC.
l 0x0C: MTP2 receives SIO from the destination point.
destination point.
point.
module stops.
responses.
are unavailable.
links are unavailable.
(2008-06-24) 1-423
ID Name Meaning
reports alarms.
Impact on System
The location fails, and the link is not available.
System Actions
MTP3 sends the location messages to MTP2 until the location succeeds.
Possible Causes
l The data is configured incorrectly.
l The physical links are not well connected.
l The MSC is faulty.
Handling Procedure
Step 1 Check whether the data in the data tables at the local office are configured correctly according
to the BSC Initial Configuration Guide.
Y => Go to step 2.
N => Modify the configuration at the local office. The alarm handling is complete.
Step 2 Check the Physical links. Check whether the connectors of the E1 links are loose or scrap.
Y => Adjust the physical links, and then check whether the alarm is cleared. If yes, the alarm
N => Go to step 3.
Step 3 Check the alarm Cause value, and handle the alarm according to the cause value.
----End
1.291 21514 MTP2 Link Service Disrupted

Description
This alarm is reported when the signaling link MTP2 reports the indication message of quitting
the services.
1-424 (2008-06-24)
Attribute
21514 Minor Event
Parameters
ID Name Meaning
1 PHY Link No. This parameter indicates the Number of the link. Each link
has only one number on the CPU of GXPUM .

l 1=international standby
l 2=National
GXPUM is located.
GXPUM is located.
(2008-06-24) 1-425
ID Name Meaning
follows:
during the IAC.
l 0x0C: MTP2 receives SIO from the destination point.
destination point.
point.
module stops.
responses.
are unavailable.
links are unavailable.
1-426 (2008-06-24)
ID Name Meaning
reports alarms
Impact on System
l The links do not transfer the service. If no other links in the link set are available, the route
of the links is unavailable.
l If the DSP of a route does not have other routes, the DSP cannot be visited. The "21501
MTP3 DSP Inaccessible" alarm is reported.
System Actions
l MTP2 stops sending the SLTM messages on the links. The switchover procedure of the
link is initiated.
l If no other links in the link set are available, the route of the links is unavailable.
l If the DSP of a route does not have other routes, the DSP cannot be visited. The "destination
point inaccessible" alarm is reported and received by the SCCP on the user plane. The user
plane stops the services to the DSP. The MTP3 will periodically initiates signaling link
reestablishment.
Possible Causes
l The interruption of link is detected on the bottom MTP2.
l The signaling links are deactivated.
l The MSC is faulty.
l The physical link over the channel is faulty. For example, the E1 cable is removed or the
board is faulty.
Handling Procedure
Step 1 In the Brow Alarm window on the LMT, check whether the1.286 21503 MTP3 Link
Unavailable alarm is reported.
Y => Handle the alarms according to the suggestions in the1.286 21503 MTP3 Link
Unavailable. The alarm handling is complete.
N => Go to step 2.
Step 2 Check whether the signaling links are deactivated.

Y => Activate the signaling links manually on the LMT.
N => Go to step 3.
Step 3 Handle the alarm according to the returned cause value, and check whether the alarm is cleared.
----End
(2008-06-24) 1-427
1.292 21516 Route Transmission on the MTP3 Prohibited

Description
This alarm is reported when the route transmission on the prohibited link are forbidden.
Attribute
21516 Major Fault
Parameters
ID Name Meaning
1 Signaling Route Index This parameter indicates the record of a signaling route,
which is automatically generated during the
configuration.
2 Net Indication l 0=International

l 2=National
4 Adjacent Signaling Point Code This parameter indicates the code of a reachable DSP in
the signaling network.
5 Source Signaling Point Code This parameter indicates the code of the signaling point
in the signaling network, which is specified when
configuring data of the signaling point.
6 Subrack No. This parameter indicates the logical subrack number of

the CPU of XPUM to which the signaling link belongs.
CPU of GPUM to which the signaling link belongs.
8 CPU No. This parameter indicates the logical CPU number of the
CPU of XPUM to which the signaling link belongs.
1-428 (2008-06-24)
Impact on System
The adjacent signaling points cannot send the signaling information element to the DSP. If the
local signaling point do not have other reachable DSPs, an alarm is generated indicating that the
DSP is inaccessible.
System Actions
l The STP at the local office sends the TFP message to other DSPs, except the signaling point
that generates the message.
l If the signaling point at the office is not of STP, the system initiates the status testing of
the route where the destination signaling point passes the STP.
Possible Causes
The adjacent STP sends the TFP message. The related signaling route are prohibited and there
is no other available signaling route between the local office and the DSP.
Handling Procedure
The alarm is generated because of a logical error in the signaling network. The error cannot be
modified manually at the local office. Notify the adjacent STP (MSC) to rectify the error.
----End
1.293 21518 MTP3 Link Layer 3 Congestion Released

Description
This alarm is reported when the congestion of the signaling link on the MTP3 is cleared.
Attribute
21518 Minor Event
Parameters
ID Name Meaning

l 2=National
(2008-06-24) 1-429
ID Name Meaning
5 Signaling Link Code This parameter indicates the unique code of signaling ling.
6 Subrack No. This parameter indicates the logical subrack number of the
GPUM CPU to which the signaling link belongs.
8 CPU No. This parameter indicates the logical CPU number of the
Impact on System
The link can bear services normally.
System Actions
The system restores the link status from congestion to non-congestion and change back the
services in the link.
Possible Causes
l The message cache memory occupied by the MTP3 is released when the signaling service
inflow of the MTP3 user decreases, resulting in the congestion release.
l The services are shared between the newly added SS7 signaling links, resulting in the
congestion release.
Handling Procedure
None.
----End
1.294 21525 SCCP DSP Unreachable

Description
This alarm is reported when the DSP is inaccessible on the SCCP layer.
1-430 (2008-06-24)
Attribute
Parameters
ID Name Meaning
l 2=National
2 SCCP Dest Signaling Point Code This parameter indicates the code of the signaling
point in the signaling network, which is specified
when configuring data of the signaling point.
3 Local Signaling Point Code This parameter indicates the signaling point in the
signaling network, which is specified when
configuring data of the signaling point.
4 SubrackNo. This parameter indicates the logical subrack number

of the GXPUM CPU where the alarm is reported.
GXPUM CPU where the alarm is reported.
6 CPU No. This parameter indicates the logical CPU number of

the GXPUM CPU where the alarm is reported.
Impact on System
Messages related to the signaling point cannot be sent.
System Actions
Stop the services related to the DSP.
Possible Causes
l SCCP DSP is prohibited.
l MTP3 DSP is unreachable.
Handling Procedure
Step 1 Check whether AlM_ 21501 is reported, that is, the destination signaling point of the MTP3 is
unreachable.
(2008-06-24) 1-431
Y => Handle the alarm according to the suggestions in AlM_ 21501. The alarm handling is
complete.
N => Go to step 2.
Step 2 Check whether the DSP operation is prohibited.
Y => Operation prohibited. If the alarm is cleared, the alarm handling is complete.
N => If the alarm persists. Please contact Motorola for technical support.
----End
1.295 21526 SCCP Subsystem Prohibited

Description
This alarm is reported when the SCCP subsystem is prohibited.
Attribute
Parameters
ID Name Meaning
l 2=National
2 DSP Code of the SCCP Subsystem This parameter indicates the local signaling point or
the DSP.
3 SCCP Subystem No. This parameter indicates the SCCP user.
4 Local Signaling Point Code This parameter indicates the code of the signaling
point in the signaling network, which is specified
during data configuration of the signaling point.
5 Subrack No. This parameter indicates the logical subrack number

of the GXPUM CPU where the alarm is reported.
6 Slot No. This parameter indicates the logical slot number of

7 CPU No. This parameter indicates the logical CPU number of

1-432 (2008-06-24)
Impact on System
The services of the SCCP subsystem are stopped.
System Actions
The services of the SCCP subsystem are stopped.
Possible Causes
l The DSP is inaccessible or the SCCP users prohibit the subsystem.
l The SSP message is received from the remote end.
l The state of the SCCP subsystem is disabled.
Handling Procedure
Step 1 In the Brow Alarm window on the LMT, check whether 1.294 21525 SCCP DSP
Unreachable is reported.
Y => The SCCP DSP is inaccessible. Handle the alarm according to the suggestions in 1.294
21525 SCCP DSP Unreachable.
N => Go to step 2.
Step 2 Check the state of the SCCP subsystem.. Check whether the alarm is cleared.
If the SCCP subsystem is in the OPERATION ALLOW state, the prohibit message of the
destination point is received. You have to wait for the allow message of the destination point
without any handling.
If the SCCP subsystem is in the OPERATION PROHIBIT state, allow the subsystem operation.
----End
1.296 21528 Remote SCCP Fault

Description
This alarm is reported when the SCCP management subsystem of the destination point is faulty
and the SCCP layer cannot handle the services.
Attribute
21528 Major Fault
(2008-06-24) 1-433
Parameters
ID Name Meaning
l 2=National
2 SCCP DSP Code This parameter indicates the code of the signaling point in the signaling
network, which is specified during data configuration of the signaling
point.
3 LOCAL SPC This parameter indicates the code of the signaling point in the network,
which is specified during data configuration of the signaling point.
located.
located.
is located.
Impact on System
The services of the local signaling point and the remote SCCP cannot be carried out.
System Actions
All the messages sent to the signaling points are prohibited.
Possible Causes
l The SCCP management subsystem of the destination point are prohibited.
l The UPU message of the destination point is received.
Handling Procedure
Notify the maintenance personnel of the remote office to handle the alarm in time.
----End
1-434 (2008-06-24)
1.297 21531 Lack of SCCP Connection Resources

Description
This alarm is reported when the SCCP connection request fails for no DSP.
Attribute
21531 Warning Event
Parameters
ID Name Meaning
located.
3 CPU No. This parameter indicates the number of the CPU where the GXPUM is
located.
Impact on System
New connections cannot be established until some connections are released.
System Actions
The system refuses new connections until some connections are released.
Possible Causes
There are no resources in the connection control table.
Handling Procedure
None.
----End
1.298 21551 Ater OML Broken Alarm

Description
This alarm is reported when the Ater OML is broken.
(2008-06-24) 1-435
Attribute
Parameters
ID Name Meaning
1 Index No. This parameter indicates the number of the Ater OML.
board is located.
is located.
4 Number of the E1 port This parameter indicates the number of the E1 port.
Impact on System
The remote subrack is unavailable or unable to receive the configuration messages.
System Actions
The Ater OMLs are in 1+1 backup mode. When the Ater OML is broken, the system
automatically check whether it is the active link. If the active Ater OML breaks, the system tries
to backup the Ater OML automatically according to the availability of the backup Ater OML.
If the standby Ater OML is broken, no handling.
Possible Causes
l The remote Ater board is reset or fault.
l The physical link is faulty.
Handling Procedure
Step 1 Check whether connectors of the local physical link are loose.
Y => Tighten the connectors. The alarm handling ends.
N => The connectors are normal. Go to step 2.
Step 2 Check whether the local physical link is faulty.
Y => Change the physical link. The alarm handling ends.
N => The physical link are normal. Go to step 3.
Step 3 Check whether connectors of the remote physical link are loose.
Y => Tighten the connectors. The alarm handling ends.
N => The connectors are normal. Go to step 4.
1-436 (2008-06-24)
Step 4 Check whether the remote board is normal.

N => Replace the board.
----End
1.299 21581 APS Started Alarm

Description
This alarm is reported when the APS protocol is started.
Attribute

21581 Warning Event
Parameters
ID Name Meaning
generated.
generated.
3 Sub slot No. This parameter indicates the number of the sub slot where the alarm is
generated.
4 Optical Port No. This parameter indicates the number of the optical port where the alarm
is generated.
Impact on System
None.
System Actions
None.
Possible Causes
l The APS backup function is created.
l The user modifies the APS protocol attribute.
(2008-06-24) 1-437
Handling Procedure
None.
----End
1.300 21582 Deactivate APS Alarm

Description
This alarm is reported when the APS protocol is stopped.
Attribute

21582 Warning Event
Parameters
ID Name Meaning
generated.
generated.
generated.
is generated.
Impact on System
None.
System Actions
None.
Possible Causes
l The APS backup function is deleted.
l The user modifies the APS protocol attribute.
1-438 (2008-06-24)
Handling Procedure
None.
----End
1.301 21583 APS Protocol Swap Alarm

Description
This alarm is reported when the status of the APS protocol changes from idle to swap.
Attribute
21583 Warning Event
Parameters
ID Name Meaning
generated.
generated.
generated.
is generated.
5 Switch Request l 15=Lock of Protection

l 14=Forced Switch
l 13=SF-High Priority
l 12=SF-Low Priority
l 11=SD-High Priority
l 10=SD-Low Priority
l 8=Manual Switch
l 6=Wait-to-Restore
l 4=Exercise Switch
l 1=Do Not Revert
l 0=No Request
(2008-06-24) 1-439
ID Name Meaning
6 Switch Type l 0=Local Request
l 1=Remote Request
l 2=Local Request
Impact on System
None.
System Actions
If the switch request is forced switch, signal fail, or manual switch, the traffic is switched over
to the protection section.
Possible Causes
l The signals of the working section or protection section on the link fail or are degraded.
l The peer end of the link starts the K byte request.
l The user starts the switch through the BAM.
Handling Procedure
None.
----End
1.302 21584 APS K1/K2 Mismatch Alarm

Description
This alarm is reported when the ASP protection section uses different channels to send the K1
byte and to receive the K2 byte.
Attribute
21584 Major Fault
Parameters
ID Name Meaning
generated.
1-440 (2008-06-24)
ID Name Meaning
generated.
generated.
is generated.
Impact on System
The switchover may not be complete, and the traffic carried by the optical port may be disrupted.
System Actions
None.
Possible Causes
This alarm is reported when the duration that ASP protection section uses different channels to
send the K1 byte and to receive the K2 byte exceeds the five seconds.
Handling Procedure
Step 1 Check whether the physical links on the both ends of the APS protection section are normal.
Y => Go to step 2.
N => Contact Motorola for technical support.
Step 2 Initiate the switchover command on the MML to make the switch status on the both ends to be
the same. Then check whether the alarm is cleared.
Y => The alarm handling ends.
----End
1.303 21585 APS K2 Mismatch Alarm

Description
This alarm is reported when the protection modes at two ends of the APS protection section are
different.
Attribute
21585 Major Fault
(2008-06-24) 1-441
Parameters
ID Name Meaning
generated.
generated.
3 Sub Slot No. This parameter indicates the number of the sub slot where the alarm is
generated.
is generated.
Impact on System
The traffic carried by the optical port may be disrupted.
System Actions
None.
Possible Causes
The protection modes at two ends of the APS protection section are different: one end is 1:1
protection mode and the other end is 1+1 protection mode.
Handling Procedure
Step 1 Check whether the protection modes at two ends of the APS protection section are the same.
Y => Configure the APS protection mode at two ends to be the same. Interconnect the two ends,
and then go to step [2].
Step 2 Check whether this alarm is cleared.

----End
1.304 21586 APS Uni-Bid Mode Mismatch Alarm

Description
This alarm is reported when the unidirectional/bidirectional switch modes at two ends of the
APS protection section are different.
1-442 (2008-06-24)
Attribute
21586 Major Fault
Parameters
ID Name Meaning
generated.
generated.
3 Sub Slot No. This parameter indicates the number of the sub slot where the alarm is
generated.
is generated.
Impact on System
The traffic carried by the optical port may be disrupted.
System Actions
If the local end adopts the 1+1 bidirectional switch mode, the system automatically adjust the
local end to be the 1+1 unidirectional switch mode.
Possible Causes
The unidirectional/bidirectional switch modes at two ends of the APS protection section are
different: one end is 1+1 unidirectional switch mode and the other end is 1+1 bidirectional switch
mode.
Handling Procedure
Step 1 Check whether the unidirectional/bidirectional switch modes at two ends of the APS protection
domain are the same.
Y => Configure the APS switch mode at two ends to be the same. Interconnect the two ends,
and then go to step 2.
Step 2 Check whether this alarm is cleared.
----End
(2008-06-24) 1-443
1.305 21601 NTP Server unconfigured

Description
This alarm is reported when NTP server is not configured.
Attribute
21601 Major Fault
Parameters
ID Name Meaning
1 Subrack No. This parameter indicates the subRack number.
2 Physical slot No. This parameter indicates the physical slot number.
3 CPU No. This parameter indicates the CPU number.
4 Process No. This parameter indicates the process number.
Impact on System
If not adjust time in a long time, the system time will be not accurate.
System Actions
None.
Possible Causes
NTP Server is not configured.
Handling Procedure
Please configure NTP server.

----End
1.306 21602 Adjust time failure with the NTP server

Description
This alarm is reported when adjust time failure with the server over 15 minutes
1-444 (2008-06-24)
Attribute
21602 Major Fault
Parameters
ID Name Meaning
1 Subrack No. This parameter indicates the subrack number.
2 Physical slot No. This parameter indicates the physical slot Number.
3 CPU No. This parameter indicates the CPU number.
4 Process No. This parameter indicates the process number.
Impact on System
If not adjust time in a long time, the system time will be not accurate.
System Actions
None.
Possible Causes
Adjust time failure with the NTP server.
Handling Procedure
Please check the network between OMU and NTP server.

----End
1.307 22001 Extern Water Sensor Alarm

Description
This alarm is reported when the water sensor of the environment monitor detects the abnormality
of the switch signals.
Attribute
22001 Major Fault
(2008-06-24) 1-445
Parameters
ID Name Meaning
environment monitor is configured.
2 Logical slot No. 2=2 Environment Monitor
4 Digital state l 0=Normal

l 1=Alarm
Impact on System
System Actions
None.
Possible Causes
The alarm is triggered when water is detected around the equipment.
Handling Procedure
Locate the cause that triggers the water sensor alarm and clean the water immediately. Check
----End
1.308 22002 Extern Smoke Sensor Alarm

Description
This alarm is reported when the smoke sensor of the environment monitor detects the
abnormality of the switch signals.
Attribute

22002 Major Fault
1-446 (2008-06-24)
Parameters
ID Name Meaning

l 1=Alarm
Impact on System
System Actions
None.
Possible Causes
The smoke sensor is triggered.
Handling Procedure
Locate the cause that triggers the smoke sensor alarm and clear the smoke accordingly. Check
----End
1.309 22003 Extern InfraRed Sensor Alarm

Description
This alarm is reported when the infrared sensor of the environment monitor detects the
Attribute

22003 Major Fault
(2008-06-24) 1-447
Parameters
ID Name Meaning

l 1=Alarm
Impact on System
System Actions
None.
Possible Causes
The infrared sensor is triggered.
Handling Procedure
Step 1 Recover the infrared sensor alarm manually at alarm maintenance on LMT if the infrared sensor
is not connected.
Step 2 Check the infrared sensor alarm's state of the cabinet or the room environment. Take right
measure when it is not normal.
(1) Check whether the alarm is cleared by clearing environment monitor's infrared sensor alarm
on LMT.
(2) Check whether the alarm is restored after the environment monitor registering successfully
by resetting the environment monitor.
----End
1.310 22004 Extern DoorEngine Sensor Alarm

Description
This alarm is reported when the access control sensor of the environment monitor detects the
1-448 (2008-06-24)
Attribute
22004 Major Fault
Parameters
ID Name Meaning

l 1=Alarm
Impact on System
System Actions
None.
Possible Causes
The access control switch of the cabinet door is triggered.
Handling Procedure
Step 1 Recover the Door Engine sensor alarm manually at alarm maintenance on LMT if the Door
Engine sensor is not connected.
Step 2 Check the Door Engine sensor alarm's state of the cabinet or the room environment. Take right
measure when it is not normal.
(1) Check whether the alarm is cleared by clearing environment monitor's Door Engine sensor
alarm and close the Door Engine switch on LMT.
(2) Check whether the alarm is restored after the environment monitor registering successfully
by resetting the environment monitor.
----End
(2008-06-24) 1-449

Description
Attribute
22005 Major Fault
Parameters
ID Name Meaning
3 Port No. of the sensor This parameter indicates the number of the sensor in the board.

l 1=Alarm
Impact on System
System Actions
The alarm persists or can be cleared by comparing the detection value (factory value) of the
digital sensor with the actual environment.
Possible Causes
The digital sensor that is connected to the BSC is triggered.
Handling Procedure
Check whether the BSC or the equipment room is in good condition. If no, solve the relevant
problems. Check whether the alarm is cleared.
----End
1-450 (2008-06-24)

Description
Attribute
22006 Major Fault
Parameters
ID Name Meaning
3 Port No. of the sensor This parameter indicates the port number of the sensor in the
board.

l 1=Alarm
Impact on System
System Actions
Possible Causes
Handling Procedure
----End
(2008-06-24) 1-451

Description
Attribute
22007 Major Fault
Parameters
ID Name Meaning
board.

l 1=Alarm
Impact on System
System Actions
Possible Causes
Handling Procedure
----End
1-452 (2008-06-24)

Description
Attribute
22008 Major Fault
Parameters
ID Name Meaning
board.

l 1=Alarm
Impact on System
System Actions
Possible Causes
Handling Procedure
----End
(2008-06-24) 1-453

Description
Attribute
22009 Major Fault
Parameters
ID Name Meaning
board.

l 1=Alarm
Impact on System
System Actions
Possible Causes
Handling Procedure
----End
1-454 (2008-06-24)

Description
Attribute
22010 Major Fault
Parameters
ID Name Meaning
board.

l 1=Alarm
Impact on System
System Actions
Possible Causes
Handling Procedure
----End
(2008-06-24) 1-455

Description
Attribute
22011 Major Fault
Parameters
ID Name Meaning
board.

l 1=Alarm
Impact on System
System Actions
Possible Causes
Handling Procedure
----End
1-456 (2008-06-24)

Description
Attribute
22012 Major Fault
Parameters
ID Name Meaning
board.

l 1=Alarm
Impact on System
System Actions
Possible Causes
Handling Procedure
----End
(2008-06-24) 1-457

Description
Attribute
22013 Major Fault
Parameters
ID Name Meaning
board.

l 1=Alarm
Impact on System
System Actions
Possible Causes
Handling Procedure
----End
1-458 (2008-06-24)

Description
Attribute
22014 Major Fault
Parameters
ID Name Meaning
board.

l 1=Alarm
Impact on System
System Actions
Possible Causes
Handling Procedure
----End
(2008-06-24) 1-459

Description
Attribute
22015 Major Fault
Parameters
ID Name Meaning
board.

l 1=Alarm
Impact on System
System Actions
Possible Causes
Handling Procedure
----End
1-460 (2008-06-24)

Description
Attribute
22016 Major Fault
Parameters
ID Name Meaning
board.

l 1=Alarm
Impact on System
System Actions
Possible Causes
Handling Procedure
----End
(2008-06-24) 1-461

Description
Attribute
22017 Major Fault
Parameters
ID Name Meaning
board.

l 1=Alarm
Impact on System
System Actions
Possible Causes
Handling Procedure
----End
1-462 (2008-06-24)

Description
Attribute
22018 Major Fault
Parameters
ID Name Meaning
board.

l 1=Alarm
Impact on System
System Actions
Possible Causes
Handling Procedure
----End
(2008-06-24) 1-463

Description
Attribute
22019 Major Fault
Parameters
ID Name Meaning
board.

l 1=Alarm
Impact on System
System Actions
Possible Causes
Handling Procedure
----End
1-464 (2008-06-24)

Description
Attribute
22020 Major Fault
Parameters
ID Name Meaning
board.

l 1=Alarm
Impact on System
System Actions
Possible Causes
Handling Procedure
----End
(2008-06-24) 1-465

Description
Attribute
22021 Major Fault
Parameters
ID Name Meaning
board.

l 1=Alarm
Impact on System
System Actions
Possible Causes
Handling Procedure
----End
1-466 (2008-06-24)

Description
Attribute
22022 Major Fault
Parameters
ID Name Meaning
board.

l 1=Alarm
Impact on System
System Actions
Possible Causes
Handling Procedure
----End
(2008-06-24) 1-467

Description
Attribute
22023 Major Fault
Parameters
ID Name Meaning
board.

l 1=Alarm
Impact on System
System Actions
Possible Causes
Handling Procedure
----End
1-468 (2008-06-24)

Description
Attribute
22024 Major Fault
Parameters
ID Name Meaning
board.

l 1=Alarm
Impact on System
System Actions
Possible Causes
Handling Procedure
----End
(2008-06-24) 1-469

Description
Attribute
22025 Major Fault
Parameters
ID Name Meaning
board.

l 1=Alarm
Impact on System
System Actions
Possible Causes
Handling Procedure
----End
1-470 (2008-06-24)

Description
Attribute
22026 Major Fault
Parameters
ID Name Meaning
board.

l 1=Alarm
Impact on System
System Actions
Possible Causes
Handling Procedure
----End
(2008-06-24) 1-471

Description
Attribute
22027 Major Fault
Parameters
ID Name Meaning
board.

l 1=Alarm
Impact on System
System Actions
Possible Causes
Handling Procedure
----End
1-472 (2008-06-24)

Description
Attribute
22028 Major Fault
Parameters
ID Name Meaning
board.

l 1=Alarm
Impact on System
System Actions
Possible Causes
Handling Procedure
----End
(2008-06-24) 1-473

Description
Attribute
22029 Major Fault
Parameters
ID Name Meaning
board.

l 1=Alarm
Impact on System
System Actions
Possible Causes
Handling Procedure
----End
1-474 (2008-06-24)

Description
Attribute
22030 Major Fault
Parameters
ID Name Meaning
board.

l 1=Alarm
Impact on System
System Actions
Possible Causes
Handling Procedure
----End
(2008-06-24) 1-475

Description
Attribute
22031 Major Fault
Parameters
ID Name Meaning
board.

l 1=Alarm
Impact on System
System Actions
Possible Causes
Handling Procedure
----End
1-476 (2008-06-24)

Description
Attribute
22032 Major Fault
Parameters
ID Name Meaning
board.

l 1=Alarm
Impact on System
System Actions
Possible Causes
Handling Procedure
----End
(2008-06-24) 1-477

Description
Attribute
22033 Major Fault
Parameters
ID Name Meaning
board.

l 1=Alarm
Impact on System
System Actions
Possible Causes
Handling Procedure
----End
1-478 (2008-06-24)

Description
Attribute
22034 Major Fault
Parameters
ID Name Meaning
board.

l 1=Alarm
Impact on System
System Actions
Possible Causes
Handling Procedure
----End
(2008-06-24) 1-479

Description
Attribute
22035 Major Fault
Parameters
ID Name Meaning
board.

l 1=Alarm
Impact on System
System Actions
Possible Causes
Handling Procedure
----End
1-480 (2008-06-24)

Description
Attribute
22036 Major Fault
Parameters
ID Name Meaning
board.

l 1=Alarm
Impact on System
System Actions
Possible Causes
Handling Procedure
----End
(2008-06-24) 1-481

Description
Attribute
22051 Major Fault
Parameters
ID Name Meaning
the environment monitor is configured.
3 Port No. of the external sensor This parameter indicates the port number of the external
analog sensor.
4 Analog state l 0=Normal

l 1=Above the upper threshold
l 2=Below the lower threshold
Impact on System
System Actions
Possible Causes
The value measured by the analog sensor of the environment monitor exceeds the threshold.
Handling Procedure
1-482 (2008-06-24)
----End

Description
Attribute
22052 Major Fault
Parameters
ID Name Meaning
1 Subrack No. Number of the subrack where the environment monitor
is configured
2 Logical slot No. 2=2Enviroment Monitor
3 Port No. of the external sensor Port number of the external analog sensor
4 Analog state 0=Normal,1=Above the upper threshold,2=Below the

lower threshold
Impact on System
System Actions
Possible Causes
Handling Procedure
(2008-06-24) 1-483
----End

Description
Attribute
22053 Major Fault
Parameters
ID Name Meaning
analog sensor.

Impact on System
System Actions
Possible Causes
Handling Procedure
1-484 (2008-06-24)

----End

Description
Attribute

22054 Major Fault
Parameters
ID Name Meaning
analog sensor.

Impact on System
System Actions
Possible Causes
(2008-06-24) 1-485
Handling Procedure
----End

Description
Attribute

65234 Major Fault
Parameters
ID Name Meaning
1 Site No. This parameter indicates the number of the site where the faulty
board is located.
2 Board ID. This parameter indicates the number of the type which the faulty
board belongs to.
3 Board No. This parameter indicates the number of the fault board.
4 The number of passage

5 TRX No. This parameter indicates the number of the alarm Trx No.
6 Cell Id. This parameter indicates the number of the cell where the faulty
board is located.
7 Site Type. This parameter indicates the type of the site where the faulty
board is located.
8 Transaction ID This parameter indicates the ID used to identify the transaction

triggered by system.
1-486 (2008-06-24)
ID Name Meaning
9 Alarm Description1 This parameter indicates the alarm additional description, only
used by developer for debugging.
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65235 Major Fault
(2008-06-24) 1-487
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
1-488 (2008-06-24)

----End

Description
Attribute
65236 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

(2008-06-24) 1-489
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65237 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.
1-490 (2008-06-24)
ID Name Meaning
board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
(2008-06-24) 1-491
Attribute
65238 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
1-492 (2008-06-24)
Handling Procedure
----End

Description
Attribute

65239 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

(2008-06-24) 1-493
ID Name Meaning
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65240 Major Fault
1-494 (2008-06-24)
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
(2008-06-24) 1-495

----End

Description
Attribute
65241 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

1-496 (2008-06-24)
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65242 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.
(2008-06-24) 1-497
ID Name Meaning
board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
1-498 (2008-06-24)
Attribute
65243 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
(2008-06-24) 1-499
Handling Procedure
----End

Description
Attribute

65244 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

1-500 (2008-06-24)
ID Name Meaning
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65245 Major Fault
(2008-06-24) 1-501
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
1-502 (2008-06-24)

----End

Description
Attribute
65246 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

(2008-06-24) 1-503
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65247 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.
1-504 (2008-06-24)
ID Name Meaning
board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
(2008-06-24) 1-505
Attribute
65248 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
1-506 (2008-06-24)
Handling Procedure
----End

Description
Attribute

65249 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

(2008-06-24) 1-507
ID Name Meaning
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65250 Major Fault
1-508 (2008-06-24)
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
(2008-06-24) 1-509

----End

Description
Attribute
65251 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

1-510 (2008-06-24)
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65252 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.
(2008-06-24) 1-511
ID Name Meaning
board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
1-512 (2008-06-24)
Attribute
65253 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
(2008-06-24) 1-513
Handling Procedure
----End

Description
Attribute

65254 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

1-514 (2008-06-24)
ID Name Meaning
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65255 Major Fault
(2008-06-24) 1-515
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
1-516 (2008-06-24)

----End

Description
Attribute
65256 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

(2008-06-24) 1-517
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65257 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.
1-518 (2008-06-24)
ID Name Meaning
board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
(2008-06-24) 1-519
Attribute
65258 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
1-520 (2008-06-24)
Handling Procedure
----End

Description
Attribute

65259 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

(2008-06-24) 1-521
ID Name Meaning
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65260 Major Fault
1-522 (2008-06-24)
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
(2008-06-24) 1-523

----End

Description
Attribute
65261 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

1-524 (2008-06-24)
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65262 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.
(2008-06-24) 1-525
ID Name Meaning
board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
1-526 (2008-06-24)
Attribute
65263 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
(2008-06-24) 1-527
Handling Procedure
----End

Description
Attribute

65264 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

1-528 (2008-06-24)
ID Name Meaning
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65265 Major Fault
(2008-06-24) 1-529
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
1-530 (2008-06-24)

----End

Description
Attribute
65266 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

(2008-06-24) 1-531
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65267 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.
1-532 (2008-06-24)
ID Name Meaning
board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
(2008-06-24) 1-533
Attribute
65268 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
1-534 (2008-06-24)
Handling Procedure
----End

Description
Attribute

65269 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

(2008-06-24) 1-535
ID Name Meaning
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65270 Major Fault
1-536 (2008-06-24)
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
(2008-06-24) 1-537

----End

Description
Attribute
65271 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

1-538 (2008-06-24)
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65272 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.
(2008-06-24) 1-539
ID Name Meaning
board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
1-540 (2008-06-24)
Attribute
65273 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
(2008-06-24) 1-541
Handling Procedure
----End

Description
Attribute

65274 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

1-542 (2008-06-24)
ID Name Meaning
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65275 Major Fault
(2008-06-24) 1-543
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
1-544 (2008-06-24)

----End

Description
Attribute
65276 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

(2008-06-24) 1-545
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65277 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.
1-546 (2008-06-24)
ID Name Meaning
board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
(2008-06-24) 1-547
Attribute
65278 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
1-548 (2008-06-24)
Handling Procedure
----End

Description
Attribute

65279 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

(2008-06-24) 1-549
ID Name Meaning
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65280 Major Fault
1-550 (2008-06-24)
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
(2008-06-24) 1-551

----End

Description
Attribute
65281 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

1-552 (2008-06-24)
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65282 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.
(2008-06-24) 1-553
ID Name Meaning
board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
1-554 (2008-06-24)
Attribute
65283 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
(2008-06-24) 1-555
Handling Procedure
----End

Description
Attribute

65284 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

1-556 (2008-06-24)
ID Name Meaning
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65285 Major Fault
(2008-06-24) 1-557
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
1-558 (2008-06-24)

----End

Description
Attribute
65286 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

(2008-06-24) 1-559
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65287 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.
1-560 (2008-06-24)
ID Name Meaning
board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
(2008-06-24) 1-561
Attribute
65288 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
1-562 (2008-06-24)
Handling Procedure
----End

Description
Attribute

65289 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

(2008-06-24) 1-563
ID Name Meaning
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65290 Major Fault
1-564 (2008-06-24)
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
(2008-06-24) 1-565

----End

Description
Attribute
65291 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

1-566 (2008-06-24)
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65292 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.
(2008-06-24) 1-567
ID Name Meaning
board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
1-568 (2008-06-24)
Attribute
65293 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
(2008-06-24) 1-569
Handling Procedure
----End

Description
Attribute

65294 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

1-570 (2008-06-24)
ID Name Meaning
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65295 Major Fault
(2008-06-24) 1-571
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
1-572 (2008-06-24)

----End

Description
Attribute
65296 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

(2008-06-24) 1-573
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65297 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.
1-574 (2008-06-24)
ID Name Meaning
board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
(2008-06-24) 1-575
Attribute
65298 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
1-576 (2008-06-24)
Handling Procedure
----End

Description
Attribute

65299 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

(2008-06-24) 1-577
ID Name Meaning
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65300 Major Fault
1-578 (2008-06-24)
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
(2008-06-24) 1-579

----End

Description
Attribute
65301 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

1-580 (2008-06-24)
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65302 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.
(2008-06-24) 1-581
ID Name Meaning
board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
1-582 (2008-06-24)
Attribute
65303 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
(2008-06-24) 1-583
Handling Procedure
----End

Description
Attribute

65304 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

1-584 (2008-06-24)
ID Name Meaning
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65305 Major Fault
(2008-06-24) 1-585
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
1-586 (2008-06-24)

----End

Description
Attribute
65306 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

(2008-06-24) 1-587
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65307 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.
1-588 (2008-06-24)
ID Name Meaning
board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
(2008-06-24) 1-589
Attribute
65308 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
1-590 (2008-06-24)
Handling Procedure
----End

Description
Attribute

65309 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

(2008-06-24) 1-591
ID Name Meaning
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65310 Major Fault
1-592 (2008-06-24)
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
(2008-06-24) 1-593

----End

Description
Attribute
65311 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

1-594 (2008-06-24)
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65312 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.
(2008-06-24) 1-595
ID Name Meaning
board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
1-596 (2008-06-24)
Attribute
65313 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
(2008-06-24) 1-597
Handling Procedure
----End

Description
Attribute

65314 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

1-598 (2008-06-24)
ID Name Meaning
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65315 Major Fault
(2008-06-24) 1-599
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
1-600 (2008-06-24)

----End

Description
Attribute
65316 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

(2008-06-24) 1-601
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65317 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.
1-602 (2008-06-24)
ID Name Meaning
board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
(2008-06-24) 1-603
Attribute
65318 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
1-604 (2008-06-24)
Handling Procedure
----End

Description
Attribute

65319 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

(2008-06-24) 1-605
ID Name Meaning
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65320 Major Fault
1-606 (2008-06-24)
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
(2008-06-24) 1-607

----End

Description
Attribute
65321 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

1-608 (2008-06-24)
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65322 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.
(2008-06-24) 1-609
ID Name Meaning
board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
1-610 (2008-06-24)
Attribute
65323 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
(2008-06-24) 1-611
Handling Procedure
----End

Description
Attribute

65324 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

1-612 (2008-06-24)
ID Name Meaning
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65325 Major Fault
(2008-06-24) 1-613
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
1-614 (2008-06-24)

----End

Description
Attribute
65326 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

(2008-06-24) 1-615
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65327 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.
1-616 (2008-06-24)
ID Name Meaning
board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
(2008-06-24) 1-617
Attribute
65328 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
1-618 (2008-06-24)
Handling Procedure
----End

Description
Attribute

65329 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

(2008-06-24) 1-619
ID Name Meaning
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65330 Major Fault
1-620 (2008-06-24)
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
(2008-06-24) 1-621

----End

Description
Attribute
65331 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

1-622 (2008-06-24)
Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
65332 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.
(2008-06-24) 1-623
ID Name Meaning
board is located.
board is located.

Impact on System
System Actions
Possible Causes
Handling Procedure
----End

Description
1-624 (2008-06-24)
Attribute
65333 Major Fault
Parameters
ID Name Meaning
board is located.
board belongs to.

board is located.
board is located.

Impact on System
System Actions
Possible Causes
(2008-06-24) 1-625
Handling Procedure
----End

Description
Attribute
65334 Major Fault
Parameters
ID Name Meaning
2 Logical slot No. 2=Environment Monitor
3 Port No. This parameter indicates number of the port that resides in the board.
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
sensor with the actual environment.
Possible Causes
The sensor connected to the BSC is triggered.
1-626 (2008-06-24)
Handling Procedure
----End

Description
Attribute
65335 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
(2008-06-24) 1-627
Handling Procedure
----End

Description
Attribute
65336 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
1-628 (2008-06-24)
Handling Procedure
----End

Description
Attribute
65337 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
(2008-06-24) 1-629
Handling Procedure
----End

Description
Attribute
65338 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
1-630 (2008-06-24)
Handling Procedure
----End

Description
Attribute
65339 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
(2008-06-24) 1-631
Handling Procedure
----End

Description
Attribute
65340 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
1-632 (2008-06-24)
Handling Procedure
----End

Description
Attribute
65341 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
(2008-06-24) 1-633
Handling Procedure
----End

Description
Attribute
65342 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
1-634 (2008-06-24)
Handling Procedure
----End

Description
Attribute
65343 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
(2008-06-24) 1-635
Handling Procedure
----End

Description
Attribute
65344 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
1-636 (2008-06-24)
Handling Procedure
----End

Description
Attribute
65345 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
(2008-06-24) 1-637
Handling Procedure
----End

Description
Attribute
65346 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
1-638 (2008-06-24)
Handling Procedure
----End

Description
Attribute
65347 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
(2008-06-24) 1-639
Handling Procedure
----End

Description
Attribute
65348 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
1-640 (2008-06-24)
Handling Procedure
----End

Description
Attribute
65349 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
(2008-06-24) 1-641
Handling Procedure
----End

Description
Attribute
65350 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
1-642 (2008-06-24)
Handling Procedure
----End

Description
Attribute
65351 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
(2008-06-24) 1-643
Handling Procedure
----End

Description
Attribute
65352 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
1-644 (2008-06-24)
Handling Procedure
----End

Description
Attribute
65353 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
(2008-06-24) 1-645
Handling Procedure
----End

Description
Attribute
65354 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
1-646 (2008-06-24)
Handling Procedure
----End

Description
Attribute
65355 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
(2008-06-24) 1-647
Handling Procedure
----End

Description
Attribute
65356 Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
1-648 (2008-06-24)
Handling Procedure
----End

Description
Attribute
65357 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
(2008-06-24) 1-649
Handling Procedure
----End

Description
Attribute
65358 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
1-650 (2008-06-24)
Handling Procedure
----End

Description
Attribute
65359 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
(2008-06-24) 1-651
Handling Procedure
----End

Description
Attribute
65360 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
1-652 (2008-06-24)
Handling Procedure
----End

Description
Attribute
65361 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
(2008-06-24) 1-653
Handling Procedure
----End

Description
Attribute
65362 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
1-654 (2008-06-24)
Handling Procedure
----End

Description
Attribute
65363 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
(2008-06-24) 1-655
Handling Procedure
----End

Description
Attribute
65364 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
1-656 (2008-06-24)
Handling Procedure
----End

Description
Attribute
65365 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
(2008-06-24) 1-657
Handling Procedure
----End

Description
Attribute
65366 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
1-658 (2008-06-24)
Handling Procedure
----End

Description
Attribute
65367 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
(2008-06-24) 1-659
Handling Procedure
----End

Description
Attribute
65368 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
1-660 (2008-06-24)
Handling Procedure
----End

Description
Attribute
65369 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
(2008-06-24) 1-661
Handling Procedure
----End

Description
Attribute
65370 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
1-662 (2008-06-24)
Handling Procedure
----End

Description
Attribute
65371 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
(2008-06-24) 1-663
Handling Procedure
----End

Description
Attribute
65372 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
1-664 (2008-06-24)
Handling Procedure
----End

Description
Attribute
65373 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
(2008-06-24) 1-665
Handling Procedure
----End

Description
Attribute
65374 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
1-666 (2008-06-24)
Handling Procedure
----End

Description
Attribute
65375 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
(2008-06-24) 1-667
Handling Procedure
----End

Description
Attribute
65376 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
1-668 (2008-06-24)
Handling Procedure
----End

Description
Attribute
65377 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
(2008-06-24) 1-669
Handling Procedure
----End

Description
Attribute
65378 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
1-670 (2008-06-24)
Handling Procedure
----End

Description
Attribute
65379 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
(2008-06-24) 1-671
Handling Procedure
----End

Description
Attribute
65380 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
1-672 (2008-06-24)
Handling Procedure
----End

Description
Attribute
65381 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
(2008-06-24) 1-673
Handling Procedure
----End

Description
Attribute
65382 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
1-674 (2008-06-24)
Handling Procedure
----End

Description
Attribute
65383 Major Fault
Parameters
ID Name Meaning
4 State l 0=Restore
l 1=Alarm
Impact on System
System Actions
Possible Causes
(2008-06-24) 1-675
Handling Procedure
----End
1-676 (2008-06-24)
BSS Alarm Reference 2 BTS Alarm Reference
2 BTS Alarm Reference
About This Chapter
This section describes the BTS alarm reference.
2.1 BTS Alarm List

2.2 30000 BTP Software Failure
2.3 30001 BTP Site Reset Occurred Due To Front Panel Reset
2.4 30002 BTP Active Link Connection Failure
2.5 30003 BTP Standby Link Connection Failure
2.6 30004 BTP Process Safe Test Audit Failure
2.7 30005 CSFP Code objects unavailable
2.8 30006 CSFP PCMCIA Card Removed
2.9 30007 GCLK Clock Reference Failure
2.10 30008 GCLK Phase Lock Lost
2.11 30009 GCLK Phase Lock Failure
2.12 30010 GCLK Watchdog Timer Expired
2.13 30011 GCLK Clock Output Failure
2.14 30012 GCLK SYNC Shutdown Request
2.15 30013 GCLK Not Operational
2.16 30014 GCLK Warmup Failure
2.17 30015 GCLK Invalid Mode
2.18 30016 GCLK Calibration In Progress
2.19 30017 GCLK Calibration via Firmware Initiated
2.20 30018 GCLK Bad Clock Source, or OCXO(oscillator) Replacement Required
(2008-06-24) 2-1
2 BTS Alarm Reference BSS Alarm Reference
2.21 30019 GCLK Calibration Request

2.22 30020 Port 0 Synchronization Loss Daily Threshold Exceeded
2.23 30021 Port 0 Synchronization Loss Hourly Threshold Exceeded
2.24 30022 Port 0 Synchronization Loss OOS Threshold Exceeded
2.25 30023 Port 0 Remote Alarm Daily Threshold Exceeded
2.26 30024 Port 0 Remote Alarm Hourly Threshold Exceeded
2.27 30025 Port 0 Remote Alarm OOS Threshold Exceeded
2.28 30026 Port 0 Frame Slip Daily Threshold Exceeded
2.29 30027 Port 0 Frame Slip Hourly Threshold Exceeded
2.30 30028 Port 0 Frame Slip OOS Threshold Exceeded
2.31 30029 Port 0 Bit Error Daily Threshold Exceeded
2.32 30030 Port 0 Bit Error Hourly Threshold Exceeded
2.33 30031 Port 0 Bit Error OOS Threshold Exceeded
2.34 30032 Port 0 Synchronization Loss OOS Timer Expired
2.35 30033 Port 0 Remote Alarm OOS Timer Expired
2.36 30034 Port 0 CRC4 Error Hourly Threshold Exceeded
2.37 30035 Port 0 CRC4 Error Daily Threshold Exceeded
2.38 30036 Port 0 Critical Alarm Threshold Exceeded
2.49 30047 Port 1 Bit Error Hourly Threshold Exceededc
2-2 (2008-06-24)

(2008-06-24) 2-3

2-4 (2008-06-24)

2.124 30122 Site No Clock References Available
2.125 30123 Site Active Alarm List Full
2.126 30124 Site Reset Request
2.127 30125 Site Database corruption detected
2.128 30131 MSI Re-Initialized Unexpectedly
2.129 30132 MSI Safe Test Audit Failure
2.130 30133 MSI Active Link Connection Failure
2.131 30134 MSI Device Failure
2.132 30135 Site No Software Failure - No intact software load on BTS without CSFP
2.133 30136 Site No Software Failure - No intact Abis software load on BTS with CSFP
2.134 30137 SWFM Indication
2.135 30256 DRI SWFM Indication - BSS Internal Alarm Only
2.136 30257 Internal Message Error - Pointer Misalignment
2.137 30258 Internal Message Error - Dual-Port RAM Segment Full
2.138 30259 Superframe Counter Error
2.140 30261 Channel Coder Internal Message Error
2.141 30262 Dual-Port RAM Error
2.144 30265 Initial Synchronization of Radio and GPRS channel failed
2.147 30268 Primary Message or Hardware Interrupt Error
2.150 30271 Calibration in progress
2.151 30272 Radio Subsystem Software to DRI Communication Error
2.152 30273 Radio Subsystem Software to DRI Communication Failure
(2008-06-24) 2-5
2.153 30274 TDM Interface Failure - TDM Parity Error

2.154 30275 TDM Interface Failure - Assigned Timeslot Counter Overflow
2.155 30276 TDM Interface Failure - Assigned Timeslot Counter Underflow
2.156 30277 Clock A Signal Loss
2.158 30279 Processor Failure
2.159 30280 Transceiver Re-Initialized Unexpectedly
2.160 30281 Critical Resource Exhausted
2.161 30282 RF Unit Primary Sync Signal Lost
2.162 30283 RF Unit HDSL Link Quality Error
2.163 30284 RF Unit Reset
2.164 30285 Reset Due To Recurring Fault
2.165 30286 Front End Processor to Radio Subsystem Software Communication Failure
2.166 30287 Hard Reset
2.167 30288 Synchronization Loss With MCU
2.168 30289 Channel Coder Timeslot 0 Failure
2.176 30297 Baseband Hopping Timeslot Counter Mismatch
2.177 30298 GSM Timeslot Counter Mismatch
2.178 30299 Spurious GSM Timeslot Interrupt
2.179 30300 Baseband Hopping TDM Link Error
2.180 30301 Baseband Hopping GSM Timeslot Misalignment
2.181 30302 Channel Coder 0 Failure - Demodulation Processor 0 Failure
2.185 30306 Transceiver to DRI Communication Error
2-6 (2008-06-24)

2.187 30308 Transceiver to DRI Burst Error
2.192 30313 Unrecoverable Error
2.193 30314 Radio Subsystem Software to DRI Communication Error - Checksum Error
2.195 30316 Radio Subsystem Software to DRI Communication Error - DRI Not Responding
2.196 30317 Equalizer Control Processor Failure - Watchdog Timer Expired
2.197 30318 Unexpected Communications Bus Interrupt
2.198 30319 Receiver Failure
2.199 30320 Power Amplifier Error
2.200 30321 Cell Transmit Power Unachievable
2.201 30322 Radio Subsystem Software to DRI Communication Error - Detected No Transceiver
Uplink Data
2.202 30323 Tx VSWR Antenna Fault
2.203 30324 Transmitter Synthesizer Failure
2.208 30329 Transmitter Failure - Output Power
2.211 30332 Power Amplifier Temperature High
2.212 30333 Power Amplifier Communication Failure
2.214 30335 Power Amplifier Power Low But Functioning
2.215 30336 Power Amplifier Temperature High But Functioning
2.217 30338 Timeslot 0 Configuration Failure
(2008-06-24) 2-7

2.225 30346 Receiver Synthesizer Failure
2.242 30363 Transceiver to DRI Communication Failure
2.247 30368 Receive Matrix Failure
2.248 30369 Transceiver to Combiner Communication Failure
2.249 30370 Control Processor to Power Amplifier Communication Failure
2.250 30371 Control Processor to Equalizer Communication Failure
2-8 (2008-06-24)
2.251 30372 Power Supply Failure

2.253 30374 Control Processor Message Queue Overflowed
2.254 30375 Receiver Input Overflowed
2.256 30377 Equalizer Output Overflowed
2.258 30379 Transmitter Out of Synchronization
2.259 30380 Receive Matrix Branch 2 Control Link Failure
2.263 30384 Control Processor Firmware Failure
2.264 30385 Control Processor Configuration Mismatch
2.265 30386 Equalizer Configuration Mismatch
2.267 30388 Invalid Calibration Data
2.268 30389 Equalizer Failure
2.269 30390 Equalizer Firmware Failure
2.271 30392 Baseband Hopping GSM Timeslot Misalignment
2.272 30393 RF Unit Power Supply Unit - Input Failure
2.273 30394 RF Unit Over Temperature
2.274 30395 RF Unit Low Voltage Disconnect Imminent
2.275 30396 RF Unit External Alarm Input
2.276 30397 Internal Communication Error
2.277 30398 Power Amplifier Temperature
2.278 30399 Hopping DRI Failure
2.279 30400 Front End Processor Failure
2.280 30401 Channel Coder Failure
2.281 30402 Transceiver Processor Failure
2.283 30404 Power Amplifier Failure
(2008-06-24) 2-9
2.284 30405 Transceiver Recovery Failure

2.285 30406 Transmission Suspended to Conserve Battery Power
2.286 30407 Invalid Transceiver Calibration Data
2.287 30408 GPRS Not Supported by Radio
2.288 30409 Invalid in-call modification of destination channel type
2.289 30410 Safe Test Audit Failure
2.290 30412 Active Link Connection Failure
2.291 30413 Standby Link Connection Failure
2.292 30414 Slow Flash Failure
2.293 30415 Non-Volatile Memory Failure
2.294 30416 Process Safe Test Audit Failure
2.295 30417 Standby Link Connected to Wrong Device
2.296 30418 Unlocked Device Not In Service
2.297 30419 Device Failure
2.298 30420 DRI hardware type mismatch with software configuration
2.301 30423 RSL Link Disconnected
2.302 30424 LAPD Protocol Error
2.303 30426 LAPD Protocol Error Threshold Exceeded
2.304 30427 Too Many LAPD Protocol Errors
2.305 30511 Cavity 0 Tuning Error
2.310 30516 Link A Sanity Failure
2.311 30517 Link B Sanity Failure
2.312 30518 Power Feed A Failure
2.313 30519 Power Feed B Failure
2.314 30520 Full Reset
2.315 30521 Partial Reset
2-10 (2008-06-24)
2.317 30523 Cavity Combining Block 0 Failure

2.319 30525 Processor A Failure
2.320 30526 Processor B Failure
(2008-06-24) 2-11

2.360 30671 Cabinet Fan Failure
2.361 30672 Fan Tray 0 Failure
2.364 30711 EAS has detected Main Power Failure
2.365 30712 External Alarm 01
2.381 30728 Database Configuration and Hardware Mismatch
2.382 30729 Duplexer Voltage Error
2-12 (2008-06-24)
2.383 30730 BTS Cabinet Over Temperature

2.384 30731 Low Voltage Disconnect Imminent
2.385 30732 Air Conditioning Unit Failure
2.386 30733 Heat Management System Unit Failure
2.387 30735 Ancillary Cabinet Over Temperature
2.388 30736 Voltage Standing Wave Ratio Sector 1 Failure
2.391 30739 Voltage Standing Wave Ratio Performance Low
2.392 30740 Smoke Alarm
2.393 30741 Door Open
2.394 30742 No Connection to Alarms Board - connection broken
2.395 30743 Low Noise Amplifier Fuse Failure
2.396 30744 No Redundant Connection to Alarms Board - connection broken
2.397 30745 No Connection to Alarm Board - Radio OOS
2.398 30746 No Redundant Connection to Alarms Board - Radio OOS
2.399 30747 No connection to alarm board - Alarm Board Removed
2.400 30748 Rectifier Failure
2.401 30749 Battery Box Temperature High
2.402 30750 Alarm Board Failed
2.403 30751 Auxiliary Alarm 1
2.404 30752 Urgent Critical Alarm
2.405 30753 Heat Management System Unit Failure 1
2.407 30755 Mains A.C. Supply Failure 1
2.409 30757 Rectifier Failure 1
2.411 30831 Power Supply Unit 0 Failure
2.415 30835 Power Supply Unit - Input Failure
(2008-06-24) 2-13
2.416 30836 Power Supply Unit - Output Failure

2.418 30838 Power Supply Temperature High
2.419 30839 Mains A.C. Supply Failure
2.420 30881 Active Multiplexer 0 Loopback Failure
2.421 30882 Standby Multiplexer 0 Loopback Failure
2-14 (2008-06-24)
2.1 BTS Alarm List

type severit
y
ALM-30000 BTP Software Failure Fault Critial Running
ALM-30001 BTP Site Reset Occurred Due To Event Warnin Running

Front Panel Reset g
ALM-30002 BTP Active Link Connection Fault Critial Hardware

Failure
ALM-30003 BTP Standby Link Connection Fault Minor Hardware

Failure
ALM-30004 BTP Process Safe Test Audit Fault Warnin Software

Failure g
ALM-30005 CSFP Code objects unavailable Fault Major Software
ALM-30006 CSFP PCMCIA Card Removed Fault Major Running
ALM-30007 GCLK Clock Reference Failure Fault Major Hardware
ALM-30008 GCLK Phase Lock Lost Fault Major Hardware
ALM-30009 GCLK Phase Lock Failure Fault Major Hardware
ALM-30010 GCLK Watchdog Timer Expired Fault Critial Hardware
ALM-30011 GCLK Clock Output Failure Fault Critial Hardware
ALM-30012 GCLK SYNC Shutdown Request Fault Critial Hardware
ALM-30013 GCLK Not Operational Fault Critial Hardware
ALM-30014 GCLK Warmup Failure Fault Critial Hardware
ALM-30015 GCLK Invalid Mode Fault Critial Hardware
ALM-30016 GCLK Calibration In Progress Fault Warnin Hardware

g
ALM-30017 GCLK Calibration via Firmware Fault Warnin Hardware

Initiated g
ALM-30018 GCLK Bad Clock Source, or Fault Warnin Hardware

OCXO(oscillator) Replacement g
Required
ALM-30019 GCLK Calibration Request Fault Warnin Hardware

g
ALM-30020 Port 0 Synchronization Loss Daily Event Warnin Communica

Threshold Exceeded g tion
(2008-06-24) 2-15

type severit
y
ALM-30021 Port 0 Synchronization Loss Event Warnin Communica

Hourly Threshold Exceeded g tion
ALM-30022 Port 0 Synchronization Loss OOS Fault Major Communica

Threshold Exceeded tion
ALM-30023 Port 0 Remote Alarm Daily Event Warnin Communica

ALM-30024 Port 0 Remote Alarm Hourly Event Warnin Communica

ALM-30025 Port 0 Remote Alarm OOS Fault Major Communica

ALM-30026 Port 0 Frame Slip Daily Threshold Event Warnin Communica

Exceeded g tion
ALM-30027 Port 0 Frame Slip Hourly Event Warnin Communica

ALM-30028 Port 0 Frame Slip OOS Threshold Fault Major Communica

Exceeded tion
ALM-30029 Port 0 Bit Error Daily Threshold Event Warnin Communica

Exceeded g tion
ALM-30030 Port 0 Bit Error Hourly Threshold Event Warnin Communica

Exceeded g tion
ALM-30031 Port 0 Bit Error OOS Threshold Fault Major Communica

Exceeded tion

Timer Expired tion
ALM-30033 Port 0 Remote Alarm OOS Timer Fault Major Communica

Expired tion
ALM-30034 Port 0 CRC4 Error Hourly Event Warnin Communica

ALM-30035 Port 0 CRC4 Error Daily Event Warnin Communica

ALM-30036 Port 0 Critical Alarm Threshold Fault Major Communica

Exceeded tion


2-16 (2008-06-24)

type severit
y





Exceeded g tion


Exceeded tion

Exceeded g tion

Exceededc g tion

Exceeded tion

Timer Expired tion

Expired tion



Exceeded tion



(2008-06-24) 2-17

type severit
y




Exceeded g tion


Exceeded tion

Exceeded g tion

Exceeded g tion

Exceeded tion

Timer Expired tion

Expired tion



Exceeded tion




2-18 (2008-06-24)

type severit
y



Exceeded g tion


Exceeded tion

Exceeded g tion

Exceeded g tion

Exceeded tion

Timer Expired tion

Expired tion



Exceeded tion





(2008-06-24) 2-19

type severit
y


Exceeded g tion


Exceeded tion

Exceeded g tion

Exceeded g tion

Exceeded tion

Timer Expired tion

Expired tion



Exceeded tion






2-20 (2008-06-24)

type severit
y

Exceeded g tion


Exceeded tion

Exceeded g tion

Exceeded g tion

Exceeded tion

Timer Expired tion

Expired tion



Exceeded tion
ALM-30122 Site No Clock References Fault Warnin Running

Available g
ALM-30123 Site Active Alarm List Full Fault Warnin Software

g
ALM-30124 Site Reset Request Fault Critial Running
ALM-30125 Site Database corruption detected Fault Major Software
ALM-30131 MSI Re-Initialized Unexpectedly Fault Critial Running
ALM-30132 MSI Safe Test Audit Failure Fault Critial Software
ALM-30133 MSI Active Link Connection Fault Critial Communica

Failure tion
ALM-30134 MSI Device Failure Fault Critial Running
(2008-06-24) 2-21

type severit
y
ALM-30135 Site No Software Failure - No Fault Critial Software

intact software load on BTS
without CSFP
ALM-30136 Site No Software Failure - No Fault Critial Software

intact Abis software load on BTS
with CSFP
ALM-30137 SWFM Indication Event Warnin Processing

g
ALM-30256 DRI SWFM Indication - BSS Event Warnin Processing

Internal Alarm Only g error
ALM-30257 Internal Message Error - Pointer Event Warnin Processing

Misalignment g error
ALM-30258 Internal Message Error - Dual- Event Major Processing

Port RAM Segment Full error
ALM-30259 Superframe Counter Error Event Warnin QoS

g
ALM-30260 Superframe Counter Error Event Warnin QoS

g
ALM-30261 Channel Coder Internal Message Event Warnin QoS

Error g
ALM-30262 Dual-Port RAM Error Event Warnin Processing

g error
ALM-30263 Channel Coder Internal Message Event Warnin Processing

Error g error

Error g error
ALM-30265 Initial Synchronization of Radio Event Warnin Communica

and GPRS channel failed g tion

Error g error

Error g error
ALM-30268 Primary Message or Hardware Event Warnin Hardware

Interrupt Error g

Error g error
2-22 (2008-06-24)

type severit
y

Error g error
ALM-30271 Calibration in progress Fault Warnin Processing

g error
ALM-30272 Radio Subsystem Software to DRI Fault Warnin Communica

Communication Error g tion
ALM-30273 Radio Subsystem Software to DRI Fault Critial Communica

Communication Failure tion
ALM-30274 TDM Interface Failure - TDM Fault Major Communica

Parity Error tion
ALM-30275 TDM Interface Failure - Assigned Fault Critial Processing

Timeslot Counter Overflow error
ALM-30276 TDM Interface Failure - Assigned Fault Critial Processing

Timeslot Counter Underflow error
ALM-30277 Clock A Signal Loss Fault Major Environme

nt
ALM-30278 Clock A Signal Loss Fault Major Environme

nt
ALM-30279 Processor Failure Fault Critial Environme

nt
ALM-30280 Transceiver Re-Initialized Fault Critial Environme

Unexpectedly nt
ALM-30281 Critical Resource Exhausted Fault Major Processing

error
ALM-30282 RF Unit Primary Sync Signal Lost Fault Warnin Environme

g nt
ALM-30283 RF Unit HDSL Link Quality Error Event Warnin Communica

g tion
ALM-30284 RF Unit Reset Fault Critial Environme

nt
ALM-30285 Reset Due To Recurring Fault Fault Critial Environme

nt
ALM-30286 Front End Processor to Radio Event Major Environme

Subsystem Software nt
ALM-30287 Hard Reset Fault Critial Environme

nt
(2008-06-24) 2-23

type severit
y
ALM-30288 Synchronization Loss With MCU Event Warnin Processing

g error
ALM-30289 Channel Coder Timeslot 0 Failure Fault Major Processing

error

error

error

error

error

error

error

error
ALM-30297 Baseband Hopping Timeslot Event Warnin Environme

Counter Mismatch g nt
ALM-30298 GSM Timeslot Counter Mismatch Event Warnin Environme

g nt
ALM-30299 Spurious GSM Timeslot Interrupt Event Warnin Environme

g nt
ALM-30300 Baseband Hopping TDM Link Fault Critial Environme

Error nt
ALM-30301 Baseband Hopping GSM Timeslot Fault Critial Environme

Misalignment nt
ALM-30302 Channel Coder 0 Failure - Fault Critial Environme

Demodulation Processor 0 Failure nt



2-24 (2008-06-24)

type severit
y
ALM-30306 Transceiver to DRI Event Warnin Processing

Communication Error g error

ALM-30308 Transceiver to DRI Burst Error Event Warnin Processing

g error
ALM-30309 Transceiver to DRI Burst Error Event Warnin Processing

g error



ALM-30313 Unrecoverable Error Fault Major Environme

nt
ALM-30314 Radio Subsystem Software to DRI Event Warnin Processing

Communication Error - g error
Checksum Error
ALM-30315 Superframe Counter Error Event Warnin Processing

g error
ALM-30316 Radio Subsystem Software to DRI Fault Critial Environme

Communication Error - DRI Not nt
Responding
ALM-30317 Equalizer Control Processor Fault Critial Environme

Failure - Watchdog Timer nt
Expired
ALM-30318 Unexpected Communications Bus Event Warnin Environme

Interrupt g nt
ALM-30319 Receiver Failure Fault Major Environme

nt
ALM-30320 Power Amplifier Error Fault Major Environme

nt
ALM-30321 Cell Transmit Power Fault Major Environme

Unachievable nt
(2008-06-24) 2-25

type severit
y
ALM-30322 Radio Subsystem Software to DRI Fault Critial Environme

Communication Error - Detected nt
No Transceiver Uplink Data
ALM-30323 Tx VSWR Antenna Fault Fault Major Environme

nt
ALM-30324 Transmitter Synthesizer Failure Fault Critial Environme

nt

nt

nt

nt

nt
ALM-30329 Transmitter Failure - Output Fault Critial Environme

Power nt

Power nt

Power nt
ALM-30332 Power Amplifier Temperature Fault Critial Environme

High nt
ALM-30333 Power Amplifier Communication Fault Critial Processing

Failure error

Power nt
ALM-30335 Power Amplifier Power Low But Fault Major Environme

Functioning nt
ALM-30336 Power Amplifier Temperature Fault Major Environme

High But Functioning nt

Power nt
ALM-30338 Timeslot 0 Configuration Failure Fault Critial Processing

error

error
2-26 (2008-06-24)

type severit
y

error

error

error

error

error

error
ALM-30346 Receiver Synthesizer Failure Fault Critial Environme

nt

nt

nt

nt

nt

nt

nt
ALM-30353 Receiver Failure Fault Critial Environme

nt

nt

nt

nt

nt
(2008-06-24) 2-27

type severit
y

nt

nt

nt

nt

nt
ALM-30363 Transceiver to DRI Fault Critial Environme

Communication Failure nt
ALM-30364 Transceiver to DRI Fault Major Environme




ALM-30368 Receive Matrix Failure Fault Major Environme

nt
ALM-30369 Transceiver to Combiner Fault Critial Environme

ALM-30370 Control Processor to Power Fault Critial Environme

Amplifier Communication Failure nt
ALM-30371 Control Processor to Equalizer Fault Critial Environme

ALM-30372 Power Supply Failure Fault Critial Environme

nt
ALM-30373 Transceiver to DRI Fault Major Communica

Communication Error tion
ALM-30374 Control Processor Message Queue Fault Major Communica

Overflowed tion
ALM-30375 Receiver Input Overflowed Fault Critial Environme

nt
2-28 (2008-06-24)

type severit
y
ALM-30376 Receiver Input Overflowed Fault Critial Environme

nt
ALM-30377 Equalizer Output Overflowed Fault Critial Environme

nt
ALM-30378 Equalizer Output Overflowed Fault Critial Environme

nt
ALM-30379 Transmitter Out of Fault Major Environme

Synchronization nt
ALM-30380 Receive Matrix Branch 2 Control Fault Major Environme

Link Failure nt
ALM-30381 Transceiver to DRI Fault Critial Communica



ALM-30384 Control Processor Firmware Fault Critial Processing

Failure error
ALM-30385 Control Processor Configuration Fault Major Processing

Mismatch error
ALM-30386 Equalizer Configuration Fault Major Processing

Mismatch error

ALM-30388 Invalid Calibration Data Fault Critial Environme

nt
ALM-30389 Equalizer Failure Fault Major Processing

error
ALM-30390 Equalizer Firmware Failure Fault Critial Processing

error
ALM-30391 Baseband Hopping TDM Link Fault Critial Environme

Error nt
ALM-30392 Baseband Hopping GSM Timeslot Fault Critial Environme

Misalignment nt
ALM-30393 RF Unit Power Supply Unit - Input Fault Warnin Environme

Failure g nt
(2008-06-24) 2-29

type severit
y
ALM-30394 RF Unit Over Temperature Fault Critial Environme

nt
ALM-30395 RF Unit Low Voltage Disconnect Fault Critial Environme

Imminent nt
ALM-30396 RF Unit External Alarm Input Fault Warnin Environme

g nt
ALM-30397 Internal Communication Error Fault Major Processing

error
ALM-30398 Power Amplifier Temperature Fault Major Environme

nt
ALM-30399 Hopping DRI Failure Event Warnin Environme

g nt
ALM-30400 Front End Processor Failure Fault Critial Environme

nt
ALM-30401 Channel Coder Failure Fault Critial Environme

nt
ALM-30402 Transceiver Processor Failure Fault Critial Environme

nt
ALM-30403 Equalizer Failure Fault Critial Environme

nt
ALM-30404 Power Amplifier Failure Fault Critial Environme

nt
ALM-30405 Transceiver Recovery Failure Fault Critial Environme

nt
ALM-30406 Transmission Suspended to Fault Major Environme

Conserve Battery Power nt
ALM-30407 Invalid Transceiver Calibration Fault Warnin Environme

Data g nt
ALM-30408 GPRS Not Supported by Radio Fault Major Communica

tion
ALM-30409 Invalid in-call modification of Fault Warnin Processing

destination channel type g error
ALM-30410 Safe Test Audit Failure Fault Critial Communica

tion
ALM-30412 Active Link Connection Failure Fault Critial Environme

nt
2-30 (2008-06-24)

type severit
y
ALM-30413 Standby Link Connection Failure Fault Minor Environme

nt
ALM-30414 Slow Flash Failure Fault Warnin Environme

g nt
ALM-30415 Non-Volatile Memory Failure Fault Warnin Environme

g nt
ALM-30416 Process Safe Test Audit Failure Fault Warnin Software

g
ALM-30417 Standby Link Connected to Fault Warnin Environme

Wrong Device g nt
ALM-30418 Unlocked Device Not In Service Fault Warnin Environme

g nt
ALM-30419 Device Failure Fault Critial Environme

nt
ALM-30420 DRI hardware type mismatch with Fault Warnin Environme

software configuration g nt
ALM-30421 DRI hardware type mismatch with Fault Major Environme

software configuration nt
ALM-30422 DRI hardware type mismatch with Fault Critial Environme

software configuration nt
ALM-30423 RSL Link Disconnected Fault Major Communica

tion
ALM-30424 LAPD Protocol Error Event Warnin Communica

g tion
ALM-30426 LAPD Protocol Error Threshold Fault Major Communica

Exceeded tion
ALM-30427 Too Many LAPD Protocol Errors Fault Major Communica

tion
ALM-30511 Cavity 0 Tuning Error Fault Critial Hardware
ALM-30516 Link A Sanity Failure Fault Critial Hardware
ALM-30517 Link B Sanity Failure Fault Critial Hardware
(2008-06-24) 2-31

type severit
y
ALM-30518 Power Feed A Failure Fault Minor Power
ALM-30519 Power Feed B Failure Fault Minor Power
ALM-30520 Full Reset Fault Critial Running
ALM-30521 Partial Reset Event Warnin Hardware

g
ALM-30523 Cavity Combining Block 0 Failure Fault Critial Hardware
ALM-30524 Cavity Combining Block 1 Failure Fault Critial Hardware
ALM-30525 Processor A Failure Fault Major Hardware
ALM-30526 Processor B Failure Fault Major Hardware
ALM-30527 Device Failure Fault Critial Running
ALM-30551 MSI Re-Initialized Unexpectedly Fault Critial Running
ALM-30552 MSI Safe Test Audit Failure Fault Critial Software
ALM-30553 MSI Active Link Connection Fault Critial Communica

Failure tion
ALM-30554 MSI Device Failure Fault Critial Running







Exceeded g tion

2-32 (2008-06-24)

type severit
y

Exceeded tion

Exceeded g tion

Exceeded g tion

Exceeded tion

Timer Expired tion

Expired tion



Exceeded tion







Exceeded g tion


Exceeded tion
(2008-06-24) 2-33

type severit
y

Exceeded g tion

Exceeded g tion

Exceeded tion

Timer Expired tion

Expired tion



Exceeded tion
ALM-30671 Cabinet Fan Failure Fault Warnin Hardware

g
ALM-30672 Fan Tray 0 Failure Fault Critial Hardware
ALM-30711 EAS has detected Main Power Fault Major Environme

Failure nt
ALM-30712 External Alarm 01 Fault Warnin Environme

g nt

g nt

g nt

g nt

g nt

g nt
2-34 (2008-06-24)

type severit
y

g nt

g nt

g nt

g nt

g nt

g nt

g nt

g nt

g nt

g nt
ALM-30728 Database Configuration and Fault Major Running

Hardware Mismatch
ALM-30729 Duplexer Voltage Error Fault Warnin Hardware

g
ALM-30730 BTS Cabinet Over Temperature Fault Warnin Environme

g nt
ALM-30731 Low Voltage Disconnect Imminent Fault Major Hardware
ALM-30732 Air Conditioning Unit Failure Fault Critial Environme

nt
ALM-30733 Heat Management System Unit Fault Warnin Environme

Failure g nt
ALM-30735 Ancillary Cabinet Over Fault Warnin Environme

Temperature g nt
ALM-30736 Voltage Standing Wave Ratio Fault Warnin Environme

Sector 1 Failure g nt
(2008-06-24) 2-35

type severit
y



Performance Low g nt
ALM-30740 Smoke Alarm Fault Critial Environme

nt
ALM-30741 Door Open Fault Warnin Running

g
ALM-30742 No Connection to Alarms Board - Fault Warnin Running

connection broken g
ALM-30743 Low Noise Amplifier Fuse Failure Fault Warnin Running

g
ALM-30744 No Redundant Connection to Fault Warnin Running

Alarms Board - connection broken g
ALM-30745 No Connection to Alarm Board - Fault Warnin Running

Radio OOS g
ALM-30746 No Redundant Connection to Fault Warnin Running

Alarms Board - Radio OOS g
ALM-30747 No connection to alarm board - Fault Warnin Running

Alarm Board Removed g
ALM-30748 Rectifier Failure Fault Warnin Hardware

g
ALM-30749 Battery Box Temperature High Fault Warnin Environme

g nt
ALM-30750 Alarm Board Failed Fault Warnin Hardware

g
ALM-30751 Auxiliary Alarm 1 Fault Warnin Environme

g nt
ALM-30752 Urgent Critical Alarm Fault Warnin Environme

g nt

Failure 1 g nt

Failure 2 g nt
2-36 (2008-06-24)

type severit
y
ALM-30755 Mains A.C. Supply Failure 1 Fault Major Hardware
ALM-30756 Mains A.C. Supply Failure 2 Fault Major Hardware
ALM-30757 Rectifier Failure 1 Fault Major Hardware
ALM-30758 Rectifier Failure 2 Fault Major Hardware
ALM-30831 Power Supply Unit 0 Failure Fault Critial Power
ALM-30835 Power Supply Unit - Input Failure Fault Major Power
ALM-30836 Power Supply Unit - Output Fault Minor Power

Failure
ALM-30837 Low Voltage Disconnect Imminent Fault Major Power
ALM-30838 Power Supply Temperature High Fault Minor Power
ALM-30839 Mains A.C. Supply Failure Fault Minor Power
ALM-30881 Active Multiplexer 0 Loopback Fault Critial Hardware

Failure
ALM-30882 Standby Multiplexer 0 Loopback Fault Critial Hardware

Failure

Failure

Failure

Failure

Failure

Failure

Failure

Failure
(2008-06-24) 2-37

type severit
y

Failure

Failure

Failure
2.2 30000 BTP Software Failure

Description
GPROC or M-Cell Main Control Unit has experienced an unrecoverable software fault.
Attribute
Parameters
ID Name Meaning
1 Site No. This parameter indicates the global ID of the BTS that reports an
alarm.
2 Board Type This parameter indicates the type of the board that reports an alarm.
3 Board No. This parameter indicates the physical number of the board that
reports an alarm.
4 Pass No. This parameter indicates the path No. of the TRX board that reports
an alarm. This parameter is 0xFF for a non-TRX board, which
indicates invalid.
5 TRX No. This parameter indicates the logical No. of the TRX board that
reports an alarm. This parameter is 0xFF for a non-TRX board,
which indicates invalid.
6 Cell No. This parameter indicates the global cell No. of the TRX board that
2-38 (2008-06-24)
ID Name Meaning
7 Site Type. Site Type., indicating the type of the BTS that reports an alarm. This
parameter can be HorizonMacro, HorizonMacro2, Horizon2Mini,
or Horizon2Micro.
8 Transcation ID Used to identify the transcation triggered by system
9 Alarm Description1 Alarm additional description,only used by developer for debugging
Impact on System
None
System Actions
The site may reset as a result of this fault if there is only one processor in the site. Otherwise the
control is transferred to the redundant processor.
Possible Causes
MCU software may have been faulty; MCU hardware may have been faulty.
Handling Procedure
Determine the site where this alarm is occuring and initiate the appropriate data collection
processes (e.g Performance Management). Review the log files and determine what caused the
SWFM. If the error has recurred for this BTP it may indicate a hardware problem. Otherwise it
was probably due to software faults. If the problem is hardware related replace the faulty BTP.
If the problem is software related, determine the cause of the problem based on the alarm info.
----End
2.3 30001 BTP Site Reset Occurred Due To Front Panel Reset
Description
The site was reset due to front panel reset switch.
Attribute

30001 Warning Event
(2008-06-24) 2-39
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
No action is required. The site has already reset.
Possible Causes
The front panel soft reset switch was pressed, which initiated a site reset.
Handling Procedure
2-40 (2008-06-24)
Investigate front panel reset of BTP MCU.
----End
2.4 30002 BTP Active Link Connection Failure

Description
DRI active link connection to the active BTP has failed.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-41
ID Name Meaning
Impact on System
None
System Actions
If the DRI link fails the DRI will be placed OOS.
Possible Causes
DRI and/or BTP device may have failed; DRI and/or BTP portion that supports the active BTP
link connection may have failed; A port on the active FOX and/or FMUX/XMUX board may
have failed;Communication fiber link may have failed; Backplane connection may have failed.
Handling Procedure
If the alarm is received with a DRI or BTP failure (254) then the corresponding DRI or BTP has
failed. Replace the DRI or BTP device. Check the state of the DRI or BTP. If it is B-U or E-U,
alarm condition has ceased and fault isolation is not required. If alarm recurs replace the the
faulty device. If the device is D-U attempt to bring the device back to service and if it remains
OOS, replace the device.
----End
2.5 30003 BTP Standby Link Connection Failure

Description
DRI standby link connection to the standby BTP has failed.
Attribute
30003 Minor Fault
Parameters
ID Name Meaning
alarm.
2-42 (2008-06-24)
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
None. Alarm is reported. DRI is not placed OOS.
Possible Causes
DRI and/or BTP device may have failed; DRI and/or BTP portion that supports the active BTP
link connection may have failed; A port on the active FOX and/or FMUX/XMUX board may
have failed;Communication fiber link may have failed; Backplane connection may have failed.
Handling Procedure
If the alarm is received with a BTP failure (254) then the corresponding BTP has failed. Replace
the BTP device. Check the state of the BTP. If it is E-U alarm condition has ceased and fault
isolation is not required. If alarm recurs replace the the faulty device. If the device is D-U attempt
to bring the device back to service and if it remains OOS, replace the device.
----End
(2008-06-24) 2-43
2.6 30004 BTP Process Safe Test Audit Failure

Description
This alarm is generated when one or more processes that the System Audit Process is auditing,
fails its audit. This could occur during a BTP audit.
Attribute

30004 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-44 (2008-06-24)
Impact on System
None
System Actions
None
Possible Causes
A process executing on the BTP failed to respond to the System Audit Process.
Handling Procedure
For a reason code of 0, 1 or 3, the BTP requires a reset to correct the problem. If the reason code
is 2, the operator should try running the audit again while continuing to check the CPU utilization
statistics for the process. If this failure persists,the operator should contact MCSC or their local
field office.
----End
2.7 30005 CSFP Code objects unavailable

Description
The alarm indicates that one (or more) devices have failed to codeload due to the code objects
for the device(s) not being available.
Attribute

30005 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
(2008-06-24) 2-45
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Alarm is reported
Possible Causes
Removable flash media device is not present or removable flash media device was inserted into
BTS after the code download.
Handling Procedure
Insert a removable flash media device into the BTS, reset the BTS to download the required
objects.
----End
2-46 (2008-06-24)
2.8 30006 CSFP PCMCIA Card Removed

Description
The PCMCIA (Personal Computer Memory Card International Association) card has been
improperly removed from the slot on an MCU. The PCMCIA card contains the software and
firmware objects required to properly initialize the MCU. The PCMCIA card facilitates a quick,
on-site code download. Otherwise, the software and firmware (objects) will be downloaded from
the BSC which is a substantially slower method.
Attribute
30006 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-47
ID Name Meaning
Impact on System
None
System Actions
None.
Possible Causes
The PCMCIA card was removed before the associated CSFP was locked.
Handling Procedure
Review the alarm report/event logs to determine the Site where this alarm is occurring.
Determine whether on-site maintenance is occurring at the location reporting the alarm. If yes,
monitor the situation at the site. If possible, contact a field representative at the site to verify the
PCMCIA card has been properly reinserted. If no, send a field representative to the site to
investigate.
----End
2.9 30007 GCLK Clock Reference Failure

Description
This alarm indicates that a GCLK cannot detect a valid clock reference signal from the incoming
span line.
Attribute
30007 Major Fault
Parameters
ID Name Meaning
alarm.
2-48 (2008-06-24)
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
A new span line will be selected as a reference source provided one is available, and phase
locking process will be reinitiated.
Possible Causes
Faulty span lines, or a GCLK reference clock detection circuit may be malfunctioning.
Handling Procedure
Investigate the faulty E1/T1 links. Select an alternative span line for the extracted clock using
modify_value or replace BTP board if the clock detection circuit is malfunctioning.
----End
(2008-06-24) 2-49
2.10 30008 GCLK Phase Lock Lost

Description
This alarm indicates that the Phase Lock Loop circuit has lost phase lock to the incoming clock
reference signal.
Attribute

30008 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-50 (2008-06-24)
Impact on System
None
System Actions
A new span line will be selected as a reference source provided one is available, and phase
locking process will be reinitiated.
Possible Causes
The CEPT reference signal has failed; The GCLK may not be in closed loop mode; The GCLK
has lost its phase lock with the source clock; The GCLK hardware has failed; The GCLK may
have aged significantly and can no longer follow the source clock.
Handling Procedure
Check for upstream E1/T1 links; Check for reference failure alarms; Calibrate GCLK.
----End
2.11 30009 GCLK Phase Lock Failure

Description
This alarm indicates that fault management has detected that a GCLK has lost phase lock; and
continued attempts to get phase locked with the clock source have failed.
Attribute

30009 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
(2008-06-24) 2-51
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Report alarm and the GCLK remains in the set frequency mode.
Possible Causes
The GCLK related to the uplink site may be wandering; The span line providing clock source
may not be stable.
Handling Procedure
Investigate the need for GCLK calibration; Check for E1/T1 link alarms to determine whether
the clock source has experienced failure at that level; Attempt to re-establish the phase lock by
reattempt_pl command;If the above actions do not correct the problem, replace the faulty GCLK.
----End
2-52 (2008-06-24)
2.12 30010 GCLK Watchdog Timer Expired

Description
This alarm indicates that the SYNC process on MCU board watchdog timer unexpectedly timed
out.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-53
Impact on System
None
System Actions
The GCLK is taken OOS.
Possible Causes
Sync firmware may have failed; The processor may have failed.
Handling Procedure
If the alarm recurs and standby MCU is now active replace the master MCU board.
----End
2.13 30011 GCLK Clock Output Failure

Description
This alarm indicates that the GCLK synchronization (SYNC) is not generating the 16.384 MHZ
clock signal in the system.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-54 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
The SYNC firmware may have failed; The processor may have failed.
Handling Procedure
----End
2.14 30012 GCLK SYNC Shutdown Request

Description
This alarm indicates that a GCLK SYNC function has experienced a catastrophic failure causing
a shutdown request to be issued.
(2008-06-24) 2-55
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
2-56 (2008-06-24)
Possible Causes
The SYNC firmware may have failed; The processor may have failed.
Handling Procedure
----End
2.15 30013 GCLK Not Operational

Description
This alarm indicates that the Micro Control Unit (MCU) Synchronization (SYNC) function
would not complete the required initialization.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-57
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Report alarm.
Possible Causes
The operational SYNC firmware may have been corrupted; The SYNC hardware may have been
faulty.
Handling Procedure
----End
2.16 30014 GCLK Warmup Failure

Description
This alarm indicates that the MCU SYNC function completed the MCU GCLK initialization,
but, the SYNC function did not indicate that the warm up was completed so that it could begin
normal operation.
Attribute

2-58 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Report the alarm.
Possible Causes
faulty.
(2008-06-24) 2-59
Handling Procedure
----End
2.17 30015 GCLK Invalid Mode

Description
This alarm indicates that the MCU SYNC function has completed hardware/firmware
initialization, and the warm up of the MCU GCLK. However, the SYNC function is reporting
that the MCU GCLK is in an operational mode that is invalid. As a result, the MCU GCLK may
not be able to continue normal operation.The operational SYNC firmware may have been
corrupted; The SYNC processor may have failed.
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-60 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Report the alarm.
Possible Causes
faulty.
Handling Procedure
----End
2.18 30016 GCLK Calibration In Progress

Description
This alarm indicates that a calibration of the GCLK SYNC hardware has been requested by the
OMC operator. The calibration is being performed on the MCU SYNC circuit.
Attribute
30016 Warning Fault
(2008-06-24) 2-61
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Report the alarm.
Possible Causes
The OMC operator has initiated a GCLK calibration.
Handling Procedure
2-62 (2008-06-24)
Verify the GCLK is operational after the GCLK SYNC is brought INS.
----End
2.19 30017 GCLK Calibration via Firmware Initiated

Description
This alarm indicates that a firmware-directed calibration of the GCLK SYNC hardware has been
requested by the OMC operator. The calibration will be performed on the MCU SYNC circuit
using the SYNC TTY firmware interface.
Attribute

30017 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-63
ID Name Meaning
Impact on System
None
System Actions
Report the alarm.
Possible Causes
The OMC operator has initiated a GCLK calibration.
Handling Procedure
Verify the GCLK is operational after the GCLK SYNC is brought INS.
----End
2.20 30018 GCLK Bad Clock Source, or OCXO(oscillator)

Replacement Required
Description
This alarm indicates that the GCLK SYNC oscillator (OCXO) will soon require replacement.
The SYNC firmware detects this need based on the age of the oscillator.
Attribute
30018 Warning Fault
Parameters
ID Name Meaning
alarm.
2-64 (2008-06-24)
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Report the alarm.
Possible Causes
The OXCO board may have aged to the point where system functions may be affected. The
SYNC firmware may have failed;The processor may have failed. There could be a problem with
incoming clock source.
Handling Procedure
Check incoming clock source. If the alarm recurs and standby MCU is now active replace the
master MCU board.
----End
(2008-06-24) 2-65
2.21 30019 GCLK Calibration Request

Description
This alarm is generated when the GCLK ageing has caused the GCLK Long Term Average
(LTA) calibration limits to exceed. The software detects the calibration problem via the GCLK
frequency register which collects the calibration data.
Attribute

30019 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-66 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
Report the alarm.
Possible Causes
The GCLK is reaching a point where it needs to be calibrated.
Handling Procedure
Check the current LTA levels by disp_gclk_avgs command.Recalibrate the MCU GCLK.
----End
2.22 30020 Port 0 Synchronization Loss Daily Threshold

Exceeded
Description
Number of Synchronisation Loss alarm hits over a 24 hour period exceeded threshold (default :
16).
Attribute
30020 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
(2008-06-24) 2-67
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
The alarm is just reported.
Possible Causes
Receive megastream signal fading in and out.
Handling Procedure
Monitor the situation to see if this alarm is a precursor to serious fault conditions.
----End
2-68 (2008-06-24)
2.23 30021 Port 0 Synchronization Loss Hourly Threshold

Exceeded
Description
20).
Attribute

30021 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-69
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End
2.24 30022 Port 0 Synchronization Loss OOS Threshold

Exceeded
Description
511).
Attribute
30022 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
2-70 (2008-06-24)
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
For an alarm condition, the MMS is taken out of service.If it is an alarm clear and the MMS
critical alarm threshold exceeded alarm processing enable flag(mms_cat_enable flag) is on, the
MMS fault history is checked to test stability of the MMS. If the stability test is passed the MMS
will be enabled and an alarm clear will be reported, else the MMS will be left disabled and a
clear for this alarm along with a critical alarm threshold exceeded alarm will be reported.
Possible Causes
Handling Procedure
If the MMS is D-U, check whether the MMS or MSI is faulty.If MMS/MSI is faulty, replace
board else check cabling, connections and the the link interface board. Verify as necessary, that
the MTL, OML or RSL links have been re-established and all SITEs have returned to service.In
the case where the faulty device resides in a Horizon2 cabinet, the MMS is part of the NIU2
(2008-06-24) 2-71
which is onboard the Horizon2 Site Controller (H2SC). In this case the FRU t be replaced should
be the H2SC.
----End

Description
Number of Remote alarm hits over 24 hour period exceeded threshold (default : 16).
Attribute
30023 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-72 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Transmit megastream path fading in and out.This condition is detected by the remote site.
Handling Procedure
----End

Description
Number of Remote alarm hits over a 1 hour period exceeded threshold (default : 20).
Attribute

30024 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
(2008-06-24) 2-73
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
2-74 (2008-06-24)
Attribute
30025 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
MMS fault history is checked to test stability of the MMS. If the stability test is passed, the MMS
(2008-06-24) 2-75
Possible Causes
Handling Procedure
be the H2SC.
----End

Description
Number of Frame Slip alarm hits over 24 hour period exceeded threshold (default : 4).
Attribute

30026 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-76 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
None. The alarm is just reported.
Possible Causes
GCLK is not synchronised with this inbound megastream.
Handling Procedure
Monitor the situation to see if this alarm is a precursor to serious fault conditions. If both MMS
8 and MMS 9 alarms are present, perform a recalibration of the GCLK, if necessary.
----End

Description
Number of Frame Slip alarm hits over a 1 hour period exceeded threshold (default : 10).
(2008-06-24) 2-77
Attribute

30027 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
2-78 (2008-06-24)
Possible Causes
Handling Procedure
----End

Description
Attribute

30028 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-79
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
be the H2SC.
----End

Description
The daily bit error rate threshold has been exceeded.
Attribute

30029 Warning Event
2-80 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Received bit error rate exceeded threshold.
Handling Procedure
(2008-06-24) 2-81
----End

Description
The hourly bit error rate threshold has been exceeded.
Attribute

30030 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-82 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
The OOS Bit Error Rate threshold has been exceeded.
Attribute

30031 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
(2008-06-24) 2-83
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
MMS fault history is checked to test stability of the MMS. If the stability test is passed,the MMS
Possible Causes
Handling Procedure
board else check cabling, connections and the link interface board. Verify as necessary, that the
MTL, OML or RSL links have been re-established and all SITEs have returned to service.In the
case where the faulty device resides in a Horizon2 cabinet, the MMS is part of the NIU2 which
2-84 (2008-06-24)
is onboard the Horizon2 Site Controller (H2SC). In this case the FRU t be replaced should be
the H2SC.
----End

Description
Synchronisation Loss alarm active continuously over the timer period.
Attribute
30032 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-85
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Receive megastream signal lost, receive framing words corrupted, in compatible remote
megastream interface.
Handling Procedure
the MTL, OML or RSL links have been re-established and all SITEs have returned to service.
In the case where the faulty device resides in a Horizon2 cabinet, the MMS is part of the NIU2
be the H2SC.
----End

Description
Remote Alarm active continuously over the timer period.
Attribute
30033 Major Fault
2-86 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Transmit megastream signal lost at remote end, transmit framing words corrupted at the remote
end. This condition is detected at the remote site.
(2008-06-24) 2-87
Handling Procedure
be the H2SC.
----End

Description
Number of CRC4 error hits over a 1 hour period exceeded threshold
Attribute

30034 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-88 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
l The intermediate equipment may not support CRC4
l The noise present on the receiver signal cause bit error to make the CRC4 error to exceed
threshold
Handling Procedure
----End

Description
Attribute
30035 Warning Event
(2008-06-24) 2-89
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
threshold
2-90 (2008-06-24)
Handling Procedure
----End

Description
Indicates that the MMS device has been in and out of service repeatedly so many times that the
system will no longer try to recover from the faults.
Attribute

30036 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-91
ID Name Meaning
Impact on System
None
System Actions
This alarm is based on tracking the frequency of OOS alarms and clears for the MMS. When
the MMS has reported OOS alarms and clears 10 times within the last 10 minutes(the MMS is
unstable), the last clear is reported but the MMS is kept OOS and this alarm is reported.This
alarm can be cleared by an INS of the MMS which will put the MMS back into service(if no
OOS alarms are active). Also, there is a periodic audit of how frequently the OOS alarms and
clears are occurring. Anytime the occurrences fall below the threshold, this alarm is cleared and
the MMS enabled.
Possible Causes
Ten MMS critical alarms were generated in less than ten minutes. This condition may be caused
by link problems (e.g. bad cable or microwave link), environment factors (e.g. weather), or a
bad MSI/XCDR board.
Handling Procedure
be the H2SC.
----End

Exceeded
Description
16).
2-92 (2008-06-24)
Attribute

30037 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
(2008-06-24) 2-93
Possible Causes
Handling Procedure
----End

Exceeded
Description
20).
Attribute
30038 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-94 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Exceeded
Description
511).
Attribute

30039 Major Fault
(2008-06-24) 2-95
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
2-96 (2008-06-24)
Handling Procedure
be the H2SC.
----End

Description
Attribute

30040 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-97
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
30041 Warning Event
2-98 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
(2008-06-24) 2-99
----End

Description
Attribute

30042 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-100 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Handling Procedure
be the H2SC.
----End

Description
Attribute
30043 Warning Event
(2008-06-24) 2-101
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
2-102 (2008-06-24)
----End

Description
Attribute
30044 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-103
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
30045 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
2-104 (2008-06-24)
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
be the H2SC.
----End
(2008-06-24) 2-105

Description
Attribute

30046 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-106 (2008-06-24)
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End
2.49 30047 Port 1 Bit Error Hourly Threshold Exceededc

Description
Attribute

30047 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-107
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
2-108 (2008-06-24)
Attribute
30048 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
(2008-06-24) 2-109
Possible Causes
Handling Procedure
the H2SC.
----End

Description
Attribute

30049 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-110 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
be the H2SC.
----End
(2008-06-24) 2-111

Description
Attribute

30050 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-112 (2008-06-24)
Impact on System
None
System Actions
Possible Causes
Handling Procedure
be the H2SC.
----End

Description
Attribute
30051 Warning Event
Parameters
ID Name Meaning
alarm.
(2008-06-24) 2-113
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
threshold
Handling Procedure
----End
2-114 (2008-06-24)

Description
Attribute

30052 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-115
Impact on System
None
System Actions
Possible Causes
threshold
Handling Procedure
----End

Description
Attribute
30053 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-116 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
the MMS enabled.
Possible Causes
bad MSI/XCDR board.
Handling Procedure
be the H2SC.
----End
(2008-06-24) 2-117

Exceeded
Description
16).
Attribute

30054 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-118 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Exceeded
Description
20).
Attribute
30055 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
(2008-06-24) 2-119
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End
2-120 (2008-06-24)

Exceeded
Description
511).
Attribute

30056 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-121
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Handling Procedure
be the H2SC.
----End

Description
Attribute
30057 Warning Event
2-122 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
(2008-06-24) 2-123
----End

Description
Attribute

30058 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-124 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute

30059 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
(2008-06-24) 2-125
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
2-126 (2008-06-24)
be the H2SC.
----End

Description
Attribute
30060 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-127
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
30061 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
2-128 (2008-06-24)
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
(2008-06-24) 2-129
Attribute

30062 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
2-130 (2008-06-24)
Possible Causes
Handling Procedure
be the H2SC.
----End

Description
Attribute

30063 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-131
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute

30064 Warning Event
2-132 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
(2008-06-24) 2-133
----End

Description
Attribute

30065 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-134 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Handling Procedure
the H2SC.
----End

Description
Attribute
30066 Major Fault
(2008-06-24) 2-135
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
2-136 (2008-06-24)
Handling Procedure
be the H2SC.
----End

Description
Attribute

30067 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-137
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
be the H2SC.
----End

Description
2-138 (2008-06-24)
Attribute

30068 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
(2008-06-24) 2-139
Possible Causes
threshold
Handling Procedure
----End

Description
Attribute
30069 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-140 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
threshold
Handling Procedure
----End

Description
Attribute

30070 Major Fault
(2008-06-24) 2-141
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
the MMS enabled.
2-142 (2008-06-24)
Possible Causes
bad MSI/XCDR board.
Handling Procedure
be the H2SC.
----End

Exceeded
Description
16).
Attribute

30071 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-143
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Exceeded
Description
20).
2-144 (2008-06-24)
Attribute

30072 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
(2008-06-24) 2-145
Possible Causes
Handling Procedure
----End

Exceeded
Description
511).
Attribute
30073 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-146 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
be the H2SC.
----End

Description
(2008-06-24) 2-147
Attribute

30074 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
2-148 (2008-06-24)
Possible Causes
Handling Procedure
----End

Description
Attribute

30075 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-149
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
30076 Major Fault
2-150 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
(2008-06-24) 2-151
Handling Procedure
be the H2SC.
----End

Description
Attribute

30077 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-152 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
30078 Warning Event
(2008-06-24) 2-153
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
2-154 (2008-06-24)
----End

Description
Attribute
30079 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-155
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Handling Procedure
be the H2SC.
----End

Description
Attribute
30080 Warning Event
Parameters
ID Name Meaning
alarm.
2-156 (2008-06-24)
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End
(2008-06-24) 2-157

Description
Attribute

30081 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-158 (2008-06-24)
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute

30082 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-159
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
the H2SC.
----End
2-160 (2008-06-24)

Description
Attribute

30083 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-161
Impact on System
None
System Actions
Possible Causes
Handling Procedure
be the H2SC.
----End

Description
Attribute
30084 Major Fault
Parameters
ID Name Meaning
alarm.
2-162 (2008-06-24)
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
(2008-06-24) 2-163
be the H2SC.
----End

Description
Attribute
30085 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-164 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
threshold
Handling Procedure
----End

Description
Attribute
30086 Warning Event
Parameters
ID Name Meaning
alarm.
(2008-06-24) 2-165
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
threshold
Handling Procedure
----End
2-166 (2008-06-24)

Description
Attribute

30087 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-167
Impact on System
None
System Actions
the MMS enabled.
Possible Causes
bad MSI/XCDR board.
Handling Procedure
be the H2SC.
----End

Exceeded
Description
16).
Attribute
30088 Warning Event
2-168 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
(2008-06-24) 2-169
----End

Exceeded
Description
20).
Attribute

30089 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-170 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Exceeded
Description
511).
Attribute
30090 Major Fault
Parameters
ID Name Meaning
alarm.
(2008-06-24) 2-171
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
2-172 (2008-06-24)
be the H2SC.
----End

Description
Attribute

30091 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-173
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
30092 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
2-174 (2008-06-24)
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
(2008-06-24) 2-175
Attribute
30093 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
2-176 (2008-06-24)
Possible Causes
Handling Procedure
be the H2SC.
----End

Description
Attribute

30094 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-177
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
2-178 (2008-06-24)
Attribute

30095 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
(2008-06-24) 2-179
Possible Causes
Handling Procedure
----End

Description
Attribute

30096 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-180 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
be the H2SC.
----End

Description
Attribute

30097 Warning Event
(2008-06-24) 2-181
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
2-182 (2008-06-24)
----End

Description
Attribute

30098 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-183
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute

30099 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
2-184 (2008-06-24)
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
(2008-06-24) 2-185
the H2SC.
----End

Description
Attribute
30100 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-186 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Handling Procedure
be the H2SC.
----End

Description
Attribute
30101 Major Fault
(2008-06-24) 2-187
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
2-188 (2008-06-24)
Handling Procedure
be the H2SC.
----End

Description
Attribute

30102 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-189
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
threshold
Handling Procedure
----End

Description
Attribute
30103 Warning Event
2-190 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
threshold
(2008-06-24) 2-191
Handling Procedure
----End

Description
Attribute

30104 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-192 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
the MMS enabled.
Possible Causes
bad MSI/XCDR board.
Handling Procedure
be the H2SC.
----End

Exceeded
Description
16).
(2008-06-24) 2-193
Attribute

30105 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
2-194 (2008-06-24)
Possible Causes
Handling Procedure
----End

Exceeded
Description
20).
Attribute
30106 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-195
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Exceeded
Description
511).
Attribute

30107 Major Fault
2-196 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
(2008-06-24) 2-197
Handling Procedure
be the H2SC.
----End

Description
Attribute

30108 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-198 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End
2.111 30109 Port 5 Remote Alarm Hourly Threshold

Exceeded
Description
Attribute
30109 Warning Event
(2008-06-24) 2-199
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
2-200 (2008-06-24)
----End

Description
Attribute

30110 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-201
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Handling Procedure
be the H2SC.
----End

Description
Attribute
30111 Warning Event
2-202 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
(2008-06-24) 2-203
----End

Description
Attribute
30112 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-204 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
30113 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
(2008-06-24) 2-205
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
be the H2SC.
----End
2-206 (2008-06-24)

Description
Attribute

30114 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-207
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute

30115 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-208 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
(2008-06-24) 2-209
Attribute
30116 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
2-210 (2008-06-24)
Possible Causes
Handling Procedure
the H2SC.
----End

Description
Attribute

30117 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-211
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
be the H2SC.
----End
2-212 (2008-06-24)

Description
Attribute

30118 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-213
Impact on System
None
System Actions
Possible Causes
Handling Procedure
be the H2SC.
----End

Description
Attribute
30119 Warning Event
Parameters
ID Name Meaning
alarm.
2-214 (2008-06-24)
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
threshold
Handling Procedure
----End
(2008-06-24) 2-215

Description
Attribute

30120 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-216 (2008-06-24)
Impact on System
None
System Actions
Possible Causes
threshold
Handling Procedure
----End

Description
Attribute
30121 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-217
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
the MMS enabled.
Possible Causes
bad MSI/XCDR board.
Handling Procedure
be the H2SC.
----End
2-218 (2008-06-24)
2.124 30122 Site No Clock References Available

Description
The clock reference for the site is lost.
Attribute

30122 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-219
Impact on System
None
System Actions
None.
Possible Causes
) No MMS available for GCLK phase clock reference.2.) No Reference or operator did n't set
the right reference.
Handling Procedure
Get the GCLK into the phase lock mode.
----End
2.125 30123 Site Active Alarm List Full

Description
The active alarm list buffer maintained by the system reached its limit.
Attribute

30123 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-220 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
None.
Possible Causes
The active alarms on the system has increased due to too many fault conditions.
Handling Procedure
(1) ) Some of the fault conditions have to be cleared.

(2) ) If possible, site reset will clear all alarms and clear this alarm also.
----End
2.126 30124 Site Reset Request

Description
The software has received a request to reset the site.
(2008-06-24) 2-221
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
No action is required. The site will be reset.
2-222 (2008-06-24)
Possible Causes
An operator has requested a site reset or the system software has determined that a site reset is
required.
Handling Procedure
No action is required. The site will be reset.
----End
2.127 30125 Site Database corruption detected

Description
The database object at the site is invalid or corrupt.
Attribute

30125 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-223
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
alarm reported.
Possible Causes
Memory corruption or software error has rendered the database invalid at the site.Currently we
only validate the 64k RCI pointers in the Switch Connection Manager (SM) portion of the
database.
Handling Procedure
Operator should reload a valid database object to the site.

----End

Description
The MSI board was unexpectedly re-initialized or reset.
Attribute
2-224 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Reset the MSI device and attempt to bring it back into service.
Possible Causes
Via the front panel switch, software reset, failure of the processor or failure of a peripheral board
related to the MMS.
(2008-06-24) 2-225
Handling Procedure
Wait for the re-initialization sequence to complete.If the MSI device fails to become B-U, ins
the device and attempt to bring it back into service.If the MSI still does not become B-U, replace
the H2SC.
----End

Description
These audits involve the use of inter-process messages to interrogate the target hardware device
while not taking the device Out-Of-Service or interrupting its primary functionality. These tests
will determine the sanity of the processor in each of the intelligent boards and the communication
link which carries the audit messaging protocol (basic ACK handshake). These tests are not
Service Affecting.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-226 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Reset the MSI board.
Possible Causes
l MSI software is hung up, MCAP interface software is not functioning correctly, MCAP
bus is bad, hardware problem on board causing no response, loss of power to board.
l Return code is as follows:
l Code Reason
l ------------------------------------------
l 0x0000 NIB_RC_SUCCESS
l 0x0001 NIB_RC_INV_LOC
l 0x0002 NIB_RC_INV_DEVICE
l 0x0003 NIB_RC_CODELOAD_NOT_REQD
l 0x0004 NIB_RC_CODELOAD_FAIL
l 0x0005 NIB_RC_PING_FAIL
l 0x0006 NIB_RC_CODELOAD_STARTED
l 0x0007 NIB_RC_CODELOAD_COMPLETE
l 0x0008 NIB_RC_PING_FAIL_EXCEPTION
l 0x0009 NIB_RC_PING_FAIL_KERNEL_FAIL
l 0x000A NIB_RC_PING_FAIL_UNKNOWN_ERROR
l 0x000B NIB_RC_PING_FAIL_COUNTER_FAIL
Handling Procedure
(2008-06-24) 2-227
If the MSI does not become B-U or there is an excessive recurrence of this alarm, replace the
H2SC.
----End

Description
The MSI(NIU) has lost connection to the active BTP(MCU).
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-228 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
Based on the additional data, reset the device or bring it back into service.
Possible Causes
Failure of the MSI(NIU) device, the active BTP(MCU), the MSI(NIU) backplane connection ,
the BTP(MCU) backplane connection or the portion of the MSI(NIU) and/or the active BTP
(MCU) board that supports the BTP(MCU) link connection.
Handling Procedure
If the MSI(NIU) does not become B-U within a short period of time,then investigate the MSI
(NIU)-BTP(MCU) communications path. If this alarm is raised and cannot be cleared then
replace the H2SC.
----End

Description
Indicates that the MSI has been requested to be taken out of service by the GPROC Fault
Management software.
Attribute
Parameters
ID Name Meaning
alarm.
(2008-06-24) 2-229
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
The device is taken OOS.
Possible Causes
The result of fault translation.
Handling Procedure
Ins the device and attempt to bring it back into service.If the device still fails to become B-U,
replace the H2SC.
----End
2-230 (2008-06-24)
2.132 30135 Site No Software Failure - No intact software

load on BTS without CSFP
Description
This alarm occurs when the Initialization Process detects that there no intact Abis software load
in running table at bootup
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-231
ID Name Meaning
Impact on System
None
System Actions
None. Alarm is reported.
Possible Causes
The BTS without CSFP suffer a power recycle. The BTS just migrate to Abis BSC from MOT
BSC with preload software.
Handling Procedure
If alarm occurs, download the Abis software load to the BTS and then activate the Abis load on
the BTS.
----End
2.133 30136 Site No Software Failure - No intact Abis

software load on BTS with CSFP
Description
This alarm occurs when the Initialization Process detects that there no intact Abis software load
in running/current table at bootup
Attribute
Parameters
ID Name Meaning
alarm.
2-232 (2008-06-24)
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
None. Alarm is reported.
Possible Causes
The Abis code objects in current table is corrupted at the site.
Handling Procedure
If alarm occurs, download the Abis software load to the BTS and then activate the Abis load on
the BTS.
----End
(2008-06-24) 2-233
2.134 30137 SWFM Indication

Description
System has detected a software processing error (SWFM) for a BTP.
Attribute

30137 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-234 (2008-06-24)
Impact on System
None
System Actions
l The alarm is reported only if SWFM indication is ON at
l the MMI.
Possible Causes
Software fault in a BTP.
Handling Procedure
From the message report determine the site number and the device
identifiers for which the SWFM is being generated. Determine the
root cause of the SWFM by looking at the code.
----End
2.135 30256 DRI SWFM Indication - BSS Internal Alarm

Only
Description
This alarm indicates a SWFM indication affecting the TCU
Attribute

30256 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
(2008-06-24) 2-235
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
None
Possible Causes
An error condition was detected by the RSS
Handling Procedure
None
----End
2.136 30257 Internal Message Error - Pointer Misalignment

Description
The FEP identified that the offset address contained in the previous "Message Ready Indication"
did not match that which the FEP was expecting.
2-236 (2008-06-24)
Attribute
30257 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
l Alarm is not reported. If several of these alarms occur within a certain time frame such that
a pre-set threshold is reached,
(2008-06-24) 2-237
l then the "Reset Due to Recurring Fault" alarm is generated. If the condition
l to generate the reset alarm occurs a third time within ten minutes, the DRI
l will be taken OOS and the "Device Failure" alarm reported.
Possible Causes
l The RSS and FEP software pointers got out of alignment
l possibly due to : 1) a lost message 2) high call traffic causing DPRAM
l access rates to be different for the FEP and RSS.
Handling Procedure
Monitor the DRI. The BSS will reset the DRI if these alarms continue at an unacceptable rate.If
the BSS takes the DRI OOS, then INS the DRI and monitor again. If the BSS takes the DRI
OOS because of
the same alarm then replace the DRI.
----End
2.137 30258 Internal Message Error - Dual-Port RAM

Segment Full
Description
The FEP has no more room in the specified DPRAM segment to place another RSS-destined
message.
Attribute

30258 Major Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
2-238 (2008-06-24)
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Reset the DPRAM segment.
Possible Causes
large number of alarms are being reported thereby causing overflow of DPRAM by messages
from either the CCDSPs or the RCU. Also,the RSS software may have simply fallen too far
behind the FEP, thus causing a backlog in DPRAM. High volume of call messages can also lead
to this alarm.
Handling Procedure
Monitor other DRI devices in the cage for this particular

alarm. If this alarm is reported by other DRI devices as well, analyze the
call traffic of the site (the site may be overloaded).
----End
(2008-06-24) 2-239

Description
CCDSP determined that there was a mismatch in the uplink superframe counter value.
Attribute

30259 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-240 (2008-06-24)
Impact on System
None
System Actions
l Alarm is reported. If several of these alarms occur
l within a certain time frame such that a pre-set threshold is reached,
Possible Causes
l Lack of Superframe Synchronization message being sent
l to the FEP, loss of uplink equalizer data, or a problem with the DRI
l baseband hopping interrupt.
Handling Procedure
Monitor the DRI. The BSS will reset the DRI if these
alarms continue at an unacceptable rate. If the BSS takes the DRI OOS, then
INS the DRI and monitor again. If the BSS takes the DRI OOS again because
of the same alarm then replace the DRI.
----End

Description
CCDSP determined that there was a mismatch in the downlink superframe counter value.
Attribute

30260 Warning Event
Parameters
ID Name Meaning
alarm.
(2008-06-24) 2-241
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
l Lack of Superframe Synchronization message being sent
l to the FEP, loss of downlink equalizer data, or a problem with the DRI
l baseband hopping interrupt.
2-242 (2008-06-24)
Handling Procedure
alarms continue at an unacceptable rate. If the BSS takes the DRI OOS, then
INS the DRI and monitor again. If the BSS takes the DRI OOS because of
the same alarm then replace the DRI.
----End

Description
A control channel message (e.g. SDCCH, PCH) for the specified subchannel or paging group
(if applicable) to be encoded and destined for the mobile station already has a message pending
for transmission.
Attribute

30261 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-243
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
l Alarm is not reported. If several of these alarms occur
Possible Causes
l Most likely the previous control channel message came
l to the CCDSP a little late and missed its opportunity for encoding and
l transmission to the mobile station. The second or current message was received
l by the CCDSP before the first was completely sent out. The site may be
l overloaded.
Handling Procedure
Monitor the DRI. The BSS will reset the DRI if these alarms
continue at an unacceptable rate. If the BSS takes the DRI OOS, then
INS the DRI and monitor again. If the BSS takes the DRI OOS because of the
same alarm then replace the DRI.
----End
2-244 (2008-06-24)
2.141 30262 Dual-Port RAM Error

Description
This alarm indicates that the Radio SubSystem (RSS) has identified that a message from the
Dual-Port Random Access Memory (DPRAM) contained an invalid number of bytes or an
invalid checksum.
Attribute

30262 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-245
ID Name Meaning
Impact on System
None
System Actions
l The number of the corrupted DPRAM segment will be
l retrieved from the alarm message, then the DPRAM segment is reset.
Possible Causes
l The DPRAM data may have been corrupted, or DRI hardware
l may have been defective, or the FEP may have been malfunctioning, or the
l DHP may be overloaded.
Handling Procedure
Monitor this DRI. If this alarm continues to be reported,

replace the DRI device.
----End

Description
The message was received with a valid checksum but the CCDSP does NOT support the
requested change of processing states.
Attribute
30263 Warning Event
Parameters
ID Name Meaning
alarm.
2-246 (2008-06-24)
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
A message was lost on its way to the CCDSP.
Handling Procedure
(2008-06-24) 2-247
----End

Description
The message was received with a valid checksum but the CCDSP determined that the message
cannot be processed given the current state of the CCDSP.
Attribute

30264 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-248 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Bad state change message received by the CCDSP.
Handling Procedure
----End
2.144 30265 Initial Synchronization of Radio and GPRS

channel failed
Description
The initial synchronization of the Radio channel and GPRS channel failed.
Attribute

30265 Warning Event
(2008-06-24) 2-249
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
None
Possible Causes
There is a fault in the path from the radio to the PCU.
Handling Procedure
2-250 (2008-06-24)
1 Take appropriate corrective action to rectify any faults.

2 Check the communication links and the devices in the path from the
radio to the PCU.
----End

Description
The byte count was in error. It was 0,1, or larger than the longest message defined in the GSM
BSS RSS-DRI Interface Specification.
Attribute
30266 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-251
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
l A message pointer or the message itself got corrupted
l somewhere between the RSS and DRI.
Handling Procedure
----End

Description
The checksum of the host message was invalid causing th e host port to be corrupted.
Attribute

30267 Warning Event
2-252 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
l will be taken OOS and the "Device Failure" alarm reported
(2008-06-24) 2-253
Possible Causes
l A message pointer or the message itself got corrupted
l somewhere between the RSS and DRI.
Handling Procedure
----End
2.147 30268 Primary Message or Hardware Interrupt Error

Description
The radio has either (1) an interrupt failure or (2) a primary message error.
Attribute

30268 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-254 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
l Persistent fault alarm: if several of these alarms occur
l within a certain time frame they are classed as a persistent fault. In this case
l , "Reset Due to Recurring Fault", will be generated and the faulty
l DRI soft reset.
l If the condition to generate the reset alarm occurs a third time within ten
l , "Device Failure",
l reported.
l If the radio is operating in Dual Carrier Mode, the associated DRI will
l subsequently undergo the same reset-reset-OOS procedure. DRI state changes for
l both DRIs will be tagged to the initial alarm.
Possible Causes
l (1) There is a hardware problem with one of the firmware's
l critical interrupts or (2) a firmware application failed to receive a critical
l message correctly.
Handling Procedure
continue at an unacceptable rate. If the BSS takes the DRI OOS then INS the DRI
and monitor it again. If the BSS takes the DRI OOS because of the same alarm,
(2008-06-24) 2-255
replace the DRI.
----End

Description
A subchannel deactivate request message was expected. The current message expected the
subchannel to be deactivated.
Attribute
30269 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-256 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
l An MPH-Deactivate Request message was lost on its way
l to the CCDSP.
Handling Procedure
continue at an unallowable rate. If the BSS takes the DRI OOS, then
----End

Description
A subchannel activate request message was expected. The current message expected the
subchannel to be activated.
Attribute

30270 Warning Event
(2008-06-24) 2-257
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
2-258 (2008-06-24)
Possible Causes
l An MPH-Activate Request message was lost on its way to
l the CCDSP.
Handling Procedure
----End
2.150 30271 Calibration in progress

Description
DRI firmware has been put into a test mode in order to calibrate the radio.
Attribute

30271 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-259
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
l DRI will transition to E-U. Subsequent alarms on the DRI
l will be reported but not acted upon.
Possible Causes
Site engineer has requested the firmware enter cal test mode
Handling Procedure
Do not lock, unlock, ins or reset the DRI while calibration is

in progress. MMI commands on the DRI should be performed by the site engineer
only.
----End
2.151 30272 Radio Subsystem Software to DRI

Communication Error
Description
This alarm indicates that the host interface port was initially busy when an attempt to write to
that port was made.
2-260 (2008-06-24)
Attribute
30272 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
l A firmware fault management report (FWFM) is generated,
l which indicates the affected DRI and the alarm code.
(2008-06-24) 2-261
Possible Causes
l The DRI hardware may have been malfunctioning or the RSS
l may be writing to a busy port.
Handling Procedure
Monitor the DRI. If this SWFM is recurring alongwith the

DRI alarm 23, then replace the DRI hardware.
----End

Description
his alarm indicates that the write to the host interface port was not successfully completed before
the maximum retry count of 16 was reached.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-262 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
l Soft reset the DRI for the first two instances when this
l alarm indication is received. If the alarm occurs three times within a
l ten minute period, then the DRI is taken OOS.
Possible Causes
The DRI hardware may have been malfunctioning.
Handling Procedure
Monitor the DRI. If the BSS takes the DRI OOS, then INS
the DRI and monitor again. If the BSS takes the DRI OOS because of the same
alarm again, then replace the DRI.
----End
2.153 30274 TDM Interface Failure - TDM Parity Error

Description
Incorrect parity detected on the inbound (to DRI) TDM highway.
(2008-06-24) 2-263
Attribute
30274 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
l If a failure is detected on the KSW or TBUS, the device
l will be taken OOS. If no failure is detected on the KSW and TBUS for the
2-264 (2008-06-24)
l active TDM bus, then the DRI will be tested, and taken OOS if the tests fail.
Possible Causes
l Failure of TDM bus interface on KSW/KSWX/DSWX or failure of
l one or more signals of TDM bus on backplane or failure of TDM interface
l circuitry on DRI.
Handling Procedure
If the BSS takes the DRI OOS because of this alarm, then
INS the DRI. If the alarm recurs, then replace the DRI board. If the alarm
leads to switching to the redundant KSW, and the alarm recurs, then replace
the primary KSW.
----End
2.154 30275 TDM Interface Failure - Assigned Timeslot

Counter Overflow
Description
More switch bound timeslots were driven onto the TDM bus than allocated in ATC register.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-265
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
l active TDM bus, then the DRI will be tested, and taken OOS if the tests fail.
Possible Causes
l Failure of TSA RAM or ATC register or MCAP interface or
l failure of one or more MCAP data/address lines on backplane.
Handling Procedure
Monitor the DRI. If the DRI is taken OOS by FM action, then

INS the DRI. If the DRI continues to be taken out of service, then replace
the DRI.
----End
2-266 (2008-06-24)
2.155 30276 TDM Interface Failure - Assigned Timeslot

Counter Underflow
Description
Fewer switch bound timeslots were driven onto the TDM bus than allocated in ATC register.
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-267
Impact on System
None
System Actions
l active TDM bus, then the DRI will be tested, and taken OOS if the test fail.
Possible Causes
l Failure of TSA RAM or ATC register or MCAP interface or
l of one or more MCAP data/address lines on backplane.
Handling Procedure

the DRI.
----End

Description
This alarm indicates that the GCLK (Clock A) associated with the TDM highway has
malfunctioned or failed.
Attribute
30277 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
2-268 (2008-06-24)
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
l Determine if TDM Clock A Failure alarm is present on
l any of the other MCAP slave boards. If so then GCLK/KSWX/DSWX A has failed,
l either force DRI to use GCLK/KSWX/DSWX B (if switch has not already been performed
l by the hardware) or replace GCLK/KSWX/DSWX A. If alarm not present on other boards
l fault is with TDM clock A detection circuitry on DRI. Take DRI out of service
Possible Causes
l The GCLK/KSWX/DSWX A device may have failed or the part of
l the Clock A that it receiving circuitry on the DRI has failed.
Handling Procedure

the DRI. If the DRI has been switched to use GCLK/KSWX/DSWX B, replace
(2008-06-24) 2-269
GCLK/KSWX/DSWX A.
----End

Description
This alarm indicates that the GCLK (Clock B) associated with the TDM highway has
malfunctioned or failed.
Attribute
30278 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-270 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
l Determine if TDM Clock B Failure alarm is present on
l any of the other MCAP slave boards. If so then GCLK/KSWX/DSWX B has failed,
l either force DRI to use GCLK/KSWX/DSWX A (if switch has not already been performed
l by the hardware) or replace GCLK/KSWX/DSWX B. If alarm not present on other boards
l fault is with TDM clock B detection circuitry on DRI, take DRI out of service.
Possible Causes
l The GCLK/KSWX/DSWX B device may have failed or the part of
l the Clock B that it receiving circuitry on the DRI has failed.
Handling Procedure

the DRI. If the DRI has been switched to use GCLK/KSWX/DSWX A, replace
GCLK/KSWX/DSWX B.
----End
2.158 30279 Processor Failure

Description
Dependent on DRI type the alarm definition is: CTU2 or CTU2D: A Digital Signal Processor
on the radio has reset. Other DRI types: The DRI has gone OOS due to the failure of the FEP
as shown by the expiration of the watchdog timer. If a watchdog timer residing on a board or
processor fails, the associated board has failed.
Attribute

(2008-06-24) 2-271
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
l Hard reset the DRI for the first two instances when this
l alarm indication is received. If the alarm occurs three times within a
Possible Causes
Failure of processor or processor peripheral or firmware.
2-272 (2008-06-24)
Handling Procedure
If fault condition still exists and the DRI is taken out

of service, then INS the DRI. If the DRI continues to be taken OOS due to
this alarm, then replace the DRI hardware.
----End
2.159 30280 Transceiver Re-Initialized Unexpectedly

Description
This alarm indicates that the Radio Channel Unit (RCU) is reset.
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-273
ID Name Meaning
Impact on System
None
System Actions
The DRI device is soft reset.
Possible Causes
l The RCU/TCU firmware has submitted a RESET request to
l RSS software. The front-panel RESET button on the Radio may have been pressed.
Handling Procedure
Replace the Radio if it the DRI device does not come bac
k into service.
----End
2.160 30281 Critical Resource Exhausted

Description
Critical firmware resource is unavailable, one of: (1) The target processor is out of available
memory (2) A firmware application has run out of time to complete a time-critical task (3) An
outgoing PCI queue is full (4) The Shared Memory Unit is unable to find a free Data Buffer
Descriptor
Attribute
30281 Major Fault
2-274 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
l DRI will undergo soft reset. If the alarm indication is
l received a second time the DRI will be hard reset and DSP code load will occur.
l If a third indication is received within ten minutes the DRI will be taken OOS,
l resulting in a loss of capacity.
(2008-06-24) 2-275
Possible Causes
l (1) All buffers are full or there is a memory leak
l (2) A timing problem has occurred
l (3) More transactions were requested than the PCI driver can handle
l (4) An off-chip process is not consuming messages quickly enough to free Data
l Buffer Descriptors, or the Shared Memory Unit is lacking memory space.
Handling Procedure
Monitor other DRIs in the cabinet for this alarm.

If the alarm is restricted to one radio, it is likely to be a hardware fault:
if the BSS takes the DRI OOS, INS the DRI and monitor it.
If the alarm is reported by neighbouring DRIs it is likely to be due to a
software or firmware problem: reduce the call load and monitor the DRIs again.
----End
2.161 30282 RF Unit Primary Sync Signal Lost

Description
RF Unit in the Slave Mode has lost the primary synchronization signal from the fiber link. The
RF Unit will switch to sync off of the HDSL link when this alarm is generated.
Attribute
30282 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-276 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
None
Possible Causes
RF Unit has lost the primary synchronization signal from the fiber link and started to sync off
of the HDSL link. Only sync slave RF Units report this alarm. Sync master RF Unit always uses
sync signal from the HDSL link.
Handling Procedure
Check the following: 1. Fiber Links and 2. The state of the

upstream RF Units.
----End
2.162 30283 RF Unit HDSL Link Quality Error

Description
The HDSL modem in the RF Unit has detected one of below errors 1. SNR (Signal to Noise
Ratio) of the HDSL modem has dropped below the SNR hourly threshold for longer than the
SNR hourly threshold period during a one hour period. 2. SNR of the HDSL modem has dropped
(2008-06-24) 2-277
below the SNR daily threshold longer than the SNR daily threshold period during a 24 hour
period.
Attribute

30283 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
2-278 (2008-06-24)
System Actions
None
Possible Causes
The quality of the HDSL link is being intermittently affected.
Handling Procedure
Note the early warning condition.
----End
2.163 30284 RF Unit Reset

Description
F Unit has been reset without resetting the RF Unit Modem.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-279
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
DRI will be re-initialized.
Possible Causes
l TDM Clock Failure, 2.TDM Sync Failure,
l RSS Communication Failure, 4.CCCP Watchdog Timeout or
l EQCP Watchdog Timeout.
Handling Procedure
Replace the DRI if it does not come back into service.

----End
2.164 30285 Reset Due To Recurring Fault

Description
This alarm is reported when the Fault Translation Process resets the DRI board due to recurring
fault conditions. When reported, the alarm will indicate the DRI that was reset and the alarm
code that caused the reset.
2-280 (2008-06-24)
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
l For the first two times that the leaky bucket for a
l persistent fault overflows, this alarm is reported and the DRI device is reset.
(2008-06-24) 2-281
l If the leaky bucket overflows a third time, the "Device Failure" alarm
l (Alarm 254) is reported against the DRI and the DRI is taken OOS.
l If this alarm was raised on a CTU2 or CTU2D radio type and the DRI is in Dual Carrier
l Mode, the associated DRI will subsequently undergo the same reset-reset-OOS
l procedure. Associated DRI state transitions will be tagged to the orignal alarm.
Possible Causes
l This alarm is reported against a class of DRI alarms that
l are classified as persistent faults. Fault translation for persistent
l alarms is handled by a leaky bucket mechanism. By this mechanism, a separate
l leaky bucket is maintained for each alarm and each incoming alarm
l indication adds a drop to this bucket. This alarm is reported when the leaky
l bucket for certain alarms overflows. The following lists the DRI persistent
l alarms for which this alarm is reported and the number of alarm indications
l that cause the leaky bucket for that alarm to overflow. The additional
l info on the alarm should indicate one of the following. DRI Alarm Code:
l 2, 5, 6, 9, 13, 14, 16, 17, 19, 20, 39, 48, 49, 50, 57, 58, 59, 60, 61, 62,
l 63, 65, 66, 221. Number of Alarm Indications: 12 (DRI alarm 50) and 6 (All
l other alarms).
Handling Procedure
Monitor the DRI. If the BSS takes the DRI OOS with the
"Device Failure" alarm, then INS the DRI and monitor again. If the BSS takes
the DRI OOS because of this same alarm then replace the DRI.
----End
2.165 30286 Front End Processor to Radio Subsystem

Software Communication Failure
Description
This alarm indicates that the FEP has not received the `Superframe Synchronization Message'
for the last five superframes. This failure can be a result of either a software or a hardware (link)
problem.
Attribute
30286 Major Event
2-282 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
l Test RSS Layer 1 and DRI/RCU processors in order to
l isolate a DRI/RCU fault. If RSS L1 has a problem, the DHP that the RSS L1
l belongs to will be disabled and a 'Device Failure' alarm will be generated
l against the DHP. If a DRI/RCU processor fails, the DRI will be disabled and
l a FM alarm will be reported indicating the failure of the DRI/RCU processor.
l All the DRI/RCU processors are tested.
(2008-06-24) 2-283
Possible Causes
l RSS may have failed to transmit the Sync message or the
l physical link between the DRI and RSS (MCAP) might have failed.
Handling Procedure
Check the physical link between the DRI and RSS and between
the DRI and RCU.
----End
2.166 30287 Hard Reset

Description
The DRI device has undergone a hard reset.
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-284 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
The DRI device undergoes a reset process.
Possible Causes
l Operator initiated reset or DRI hardware initiated res
l et.
Handling Procedure
f alarm keeps re-occuring and is not initiated by the

operator, the replace the DRI device.
----End
2.167 30288 Synchronization Loss With MCU

Description
The DRI (TCU) active communication link is no longer synchronized with the BTP (MCU).
Attribute

30288 Warning Event
(2008-06-24) 2-285
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
2-286 (2008-06-24)
Possible Causes
l 1) faulty fibre optic cable, 2 )faulty connections or link,
l 3) faulty MCU or DRI.
Handling Procedure
alarms continue at an unallowable rate. If the BSS takes the DRI OOS,
then INS the DRI and monitor again. If the BSS takes the DRI OOS because
----End

Description
The FEP related Channel Coding Digital Signal Processor is not responding.
Attribute

30289 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-287
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
l Alarm processing will determine if PCHN's RTF is a BCCH
l and using a CCCH timeslot and if so it will reset the DRI. If the alarm
l happens a 3rd time within 10 minutes the DRI will be taken OOS. If the
l PCHN's RTF is not a BCCH using CCCH then the PCHN will be taken OOS.
Possible Causes
l The interface hardware between the FEP and the CCDSP may
l be defective or the code checksum routine, which is included as part of the
l CCDSP initialization process, may have failed.
Handling Procedure
The DRI may need to be replaced. Consult the Customer

Manual for Alarm Handling to see a detailed procedure.
----End

Description
2-288 (2008-06-24)
Attribute
30290 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
(2008-06-24) 2-289
Possible Causes
Handling Procedure
The DRI may need to be replaced. Consult the Customer Manual

for Alarm Handling to see a detailed procedure.
----End

Description
Attribute
30291 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-290 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure

----End

Description
(2008-06-24) 2-291
Attribute
30292 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
2-292 (2008-06-24)
Possible Causes
Handling Procedure

----End

Description
Attribute
30293 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-293
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure

----End

Description
2-294 (2008-06-24)
Attribute
30294 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
(2008-06-24) 2-295
Possible Causes
Handling Procedure

----End

Description
Attribute
30295 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-296 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure

----End

Description
(2008-06-24) 2-297
Attribute
30296 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
2-298 (2008-06-24)
Possible Causes
Handling Procedure

----End
2.176 30297 Baseband Hopping Timeslot Counter Mismatch

Description
The FEP BBH counter is not back to zero on the superframe boundary.
Attribute
30297 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-299
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
The DRI radio that generates the interrupt may be defective.
Handling Procedure
----End
2.177 30298 GSM Timeslot Counter Mismatch

Description
The FEP DRI counter was not set back to zero on the superframe boundary.
2-300 (2008-06-24)
Attribute
30298 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
(2008-06-24) 2-301
Possible Causes
The DRI radio that generates the interrupt may be defective.
Handling Procedure
----End
2.178 30299 Spurious GSM Timeslot Interrupt

Description
Two consecutive timeslot interrupts processed with equalized data bursts from the RCU.
Attribute

30299 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-302 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
l 1) The RCU may have been placed OOS. 2) The DRI baseband
l hopping interrupt feature may not have been functioning properly. 3) The
l uplink portion of the RCU-DRI fibre link may be defective. 4) The DRI
l hardware that generates the GSM timeslot interrupt may be defective.
Handling Procedure
----End
(2008-06-24) 2-303

Description
The TDM bus and the KSW failed to properly transfer channel-encoded modulator data to the
RCU.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-304 (2008-06-24)
Impact on System
None
System Actions
l Alarm processing tries to isolate a fault on the TDM bus.
l If fault not found then reset the DRI. If fault happens again and not
l isolated to the TDM bus then reset DRI. If same happens within 10 minutes
l of the first fault, then take DRI OOS.
Possible Causes
l 1) The TDM timeslot path connects may not have been properly configured at the KSW or
the DRI. 2) The DRI, KSW, or TDM hardware may have
l been defective.
Handling Procedure
If this alarm has occured and the DRI is left OOS, then INS the DRI. If the DRI fails to come
into service, then replace it.
If the DRI comes into service but goes OOS because of another occurrence
of this alarm then replace the DRI.
----End
2.180 30301 Baseband Hopping GSM Timeslot

Misalignment
Description
The CCDSPs are activated in the wrong GSM timeslots.
Attribute
Parameters
ID Name Meaning
alarm.
(2008-06-24) 2-305
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Alarm processing Hard resets the DRI. If the same fault happens again within 10 minutes then
the DRI is Hard reset again. If the same happens a 3rd time within 10 minutes then the DRI is
taken OOS.
Possible Causes
1) Defective DRI. 2) Incorrectly configured TDM timeslot path connections at the CCDSP. 3)
Defective CCDSP or TDM link cables.
Handling Procedure
into service, then replace it.
If the DRI comes into service but goes OOS because of another occurrence of
2-306 (2008-06-24)
this alarm then replace the DRI.
----End
2.181 30302 Channel Coder 0 Failure - Demodulation

Processor 0 Failure
Description
The channel coder 0 detected that the associated Viterbi Engine processor 0 has failed.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-307
ID Name Meaning
Impact on System
None
System Actions
l The system Soft resets the DRI. If the same fault
l happens again within 10 minutes then the DRI is Soft reset again. If the same
l happens a 3rd time within 10 minutes then the DRI is taken OOS.
Possible Causes
Faulty Viterbi Engine hardware (demodulation processor).
Handling Procedure
into service, then replace the
Radio unit. If the DRI comes into service but goes OOS because of another
occurrence of this alarm then replace the Radio unit.
----End

Processor 1 Failure
Description
Attribute
2-308 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
(2008-06-24) 2-309
Handling Procedure
----End

Processor 0 Failure
Description
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-310 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Processor 1 Failure
Description
Attribute
(2008-06-24) 2-311
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
2-312 (2008-06-24)
Handling Procedure
----End

Description
The RSS-destined message from the RCU contains an invalid header/message code.
Attribute
30306 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-313
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
l 1) Defective fibre link to the DRI. 2) RCU firmware may
l have sent an erroneous message.
Handling Procedure
----End

Description
The message sent to the RCU has a bad message byte count.
2-314 (2008-06-24)
Attribute
30307 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
(2008-06-24) 2-315
Possible Causes
l 1) Defective fibre link to the DRI. 2) RCU firmware may
l have sent an erroneous message.
Handling Procedure
----End

Description
The first message from the RCU was not the Equalized Data message.
Attribute

30308 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-316 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
l within a certain time frame such that a pre-set threshold is reached,then the "Reset Due to
Recurring Fault" alarm is generated. If the condition
l to generate the reset alarm occurs a third time within ten minutes, the DRI will be taken
OOS and the "Device Failure" alarm reported.
Possible Causes
l 1) Defective fibre link to the DRI. 2) Faulty DRIX.
l 3) RCU firmware may have sent an erroneous message.
Handling Procedure
Monitor the DRI. The BSS will reset the DRI if these alarms continue at an unallowable rate. If
the BSS takes the DRI OOS,
then INS the DRI and monitor again.If the BSS takes the DRI OOS because of the same alarm
then replace the DRI.
----End
(2008-06-24) 2-317

Description
A second Equalized Data message from the RCU was detected within the same timeslot.
Attribute

30309 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-318 (2008-06-24)
Impact on System
None
System Actions
Possible Causes
l 3) RCU firmware may have sent an erroneous message. 4) Faulty downlink
l baseband hopping interrupt hardware.
Handling Procedure
the BSS takes the DRI OOS,
then INS the DRI and monitor again.If the BSS takes the DRI OOS because of the same alarm
then replace the DRI.
----End

Description
No data was sent when the FEP was expecting an Equalized Data message.
Attribute
30310 Warning Event
Parameters
ID Name Meaning
alarm.
(2008-06-24) 2-319
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
1) Defective fibre link to the DRI. 2) Faulty DRIX.
Handling Procedure
2-320 (2008-06-24)
the BSS takes the DRI OOS,then INS the DRI and monitor again. If the BSS takes the DRI OOS
because of the same alarm then replace the DRI.
----End

Description
Data sent was incomplete when the FEP was expecting three bytes.
Attribute

30311 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-321
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
Data sent was incomplete when the FEP was expecting three bytes.
Attribute
30312 Warning Event
2-322 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
(2008-06-24) 2-323
Possible Causes
Handling Procedure
----End
2.192 30313 Unrecoverable Error

Description
An unrecoverable error has occurred, one of: (1) DRI initialisation failed (2) PCI bus error (3)
Digital Signal Processor failure.
Attribute

30313 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-324 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
l DRI will undergo hard reset and DSP code load will occur.If a third indication is received
within ten minutes the DRI will be taken OOS,resulting in a loss of capacity.If the radio is
operating in Dual Carrier Mode, the associated DRI will
l subsequently undergo the same reset-reset-OOS procedure. DRI state changes for both
DRIs will be tagged to the initial alarm.
Possible Causes
Memory allocation error or hardware failure.
Handling Procedure
Monitor the DRI. If the BSS takes the DRI OOS, INS the DRI and
monitor again. If the BSS takes the DRI OOS because of the same alarm then
replace the DRI.
----End

Communication Error - Checksum Error
Description
The FEP identified a Dual Port Ram (DPRAM) message from RSS that contains an invalid
checksum, hence FEP discarded the message. Alternatively if this alarm was raised on a CTU2
or CTU2D radio type, a message was received by firmware with invalid checksum.
(2008-06-24) 2-325
Attribute
30314 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
2-326 (2008-06-24)
OOS and the "Device Failure" alarm reported.If this alarm was raised on a CTU2 or CTU2D
radio type and the DRI is in Dual Carrier Mode, the associated DRI will subsequently
undergo the same reset-reset-OOS
l procedure. Associated DRI state transitions will be tagged to the orignal alarm.
Possible Causes
The message may have been corrupted by RSS software or the DRI-resident DPRAM hardware
is defective.
Handling Procedure
Monitor the DRI. The BSS will reset the DRI if these alarm
----End

Description
This alarm indicates that the superframe software counter maintained by the Front End Processor
(FEP) does not match the superframe value most recently received in the "Superframe
Synchronization Message" from the Radio Subsystem (RSS).
Attribute
30315 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
(2008-06-24) 2-327
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
l Alarm is reported. If several of these alarms occur within a certain time frame such that a
pre-set threshold is reached,then the "Reset Due to Recurring Fault" alarm is generated. If
the condition
Possible Causes
The RSS may not have sent an updated "Superframe Synchronization Message", or the message
may have arrived too late at the FEP,or the GSM timeslot interrupt on the DRI may be defective.
Handling Procedure
----End
2-328 (2008-06-24)

Communication Error - DRI Not Responding
Description
DRI is not responding to higher layer messages. RSS is unable to communicate with the DRI
due to the problem.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-329
ID Name Meaning
Impact on System
None
System Actions
l For Horizonoffice the affected DRI is reset.
l For Non-Horizonoffice case the DRI is disabled.
Possible Causes
l The following are the possible causes for this alarm:
l ? The DRI hardware was unequipped in the system.
l ? The DRI hardware is faulty.
Handling Procedure
If the BSS takes the DRI OOS (DRI

goes disabled-unlocked) then Return the DRI to service (INS)
and monitor the DRI. And If the DRI fails to go
busy-unlocked after
return to service or the BSS takes the DRI
OOS again as a result of the
same alarm after the DRI
becomes busy-unlocked, then Send a field representative to the
site to replace one of the following:
? DRIM board for an InCell
BTS.
? Transceiver unit for a
non-InCell BTS.
----End
2.196 30317 Equalizer Control Processor Failure - Watchdog

Timer Expired
Description
This alarm indicates that the DRI has gone OOS due to the failure of the Equalizer Control
Processor (EQCP) as shown by the expiration of the watchdog timer.
2-330 (2008-06-24)
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
l Soft reset the DRI for the first two instances when
l this alarm indication is received. If the alarm occurs three times within a
(2008-06-24) 2-331
Possible Causes
The DRI radio (RCU/TCU), may be faulty, or the EQCP firmware on the DRI radio may be
defective.
Handling Procedure
If fault condition still exists and the DRI is taken out

of service, then INS the DRI. If the DRI is successively taken OOS again
due to this alarm, then replace the DRI hardware.
----End
2.197 30318 Unexpected Communications Bus Interrupt

Description
An intermittent hardware or message transport (PCI) error has occurred. The master DSP has
received more interrupts than messages delivered via the PCI bus.
Attribute
30318 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-332 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
l Persistent fault alarm: if several of these alarms occur within a certain time frame they are
classed as a persistent fault. In this case
l , "Reset Due to Recurring Fault", will be generated and the faulty
l DRI soft reset.
l , "Device Failure",reported.
Possible Causes
Either the PCI driver is malfunctioning or there is a PCI bus hardware fault.
Handling Procedure
continue at an unacceptable rate. If the BSS takes the DRI OOS then INS the DRI
and monitor it again. If the BSS takes the DRI OOS because of the same alarm,
replace the DRI.
----End
(2008-06-24) 2-333

Description
Radio receiver (equalizer) detected a problem with the order of the in-phase and quadrature (IQ)
data stream.
Attribute

30319 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-334 (2008-06-24)
Impact on System
None
System Actions
l The DRI will be soft reset the first and second time this alarm indication is received. If the
alarm occurs three times within a ten minute period the
l DRI is taken OOS.
Possible Causes
IQ data was corrupted before it reached radio firmware.
Handling Procedure
Monitor the DRI. If the BSS takes the DRI OOS, reset the DRI
(reset_device) and monitor again. If the BSS takes the DRI OOS because of the same alarm then
replace the DRI.
----End
2.199 30320 Power Amplifier Error

Description
A Power Amplifier (PA) phase detect or reverse power error has occurred, either of: (1) Phase
detect: PA's branches are no longer in phase; or (2) Reverse power: radio has too much power
entering the primary output connector.
Attribute
30320 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
(2008-06-24) 2-335
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
l DRI will undergo soft reset. If the alarm indication is
l received a second time the DRI will be hard reset and DSP code load will occur.If a third
indication is received within ten minutes the DRI will be taken OOS,
l resulting in a loss of capacity.If the radio is operating in Dual Carrier Mode, the ssociated
DRI will subsequently undergo the same reset-reset-OOS procedure. DRI state changes for
Possible Causes
l (1) Temporary phase error may arise due to PA compression;
l (2) Radio operating at full output power whilst no load is connected, or faulty
l combiner setup such that output power from one radio is fed to the output connector
l of another.
Handling Procedure
Monitor the DRI. If the BSS takes the DRI OOS, reset the DRI
2-336 (2008-06-24)
(reset_device) and monitor again. If the BSS takes the DRI OOS because of the same alarm then
replace the DRI.
----End
2.200 30321 Cell Transmit Power Unachievable

Description
A radio cannot be brought into service because it cannot achieve the cell transmit power level.
This can be due to various factors which include bad database settings and DRI Tx calibration
offsets.
Attribute
30321 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-337
ID Name Meaning
Impact on System
None
System Actions
Alarm is reported. If the DRI is operating in Dual Carrier Mode, the associated DRI will
subsequently be taken OS.Associated DRI state transitions will be tagged to the alarm. All
affected DRI devices will remain out of service at this Cell, resulting in a loss of capacity.
Possible Causes
Radio devices can have different power levels depending on the cabinet they are located in and
the carrier mode (single/double) in use. Due to the power level differences there may be some
scenarios where the radio is not able to achieve the cell transmit power level. When this is
detected the DRI is taken OOS and an alarm raised.
Handling Procedure
Cell transmit power level may be reduced.

----End

Communication Error - Detected No Transceiver Uplink
Data
Description
The RSS has detected loss of uplink SACCH messages from the RCU.
Attribute
2-338 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
l FM checks whether 10 indications of this alarm have
l been received in 24 hours. If so, hard reset the DRI device. If not, then
l alarm reporting is suppressed.
Possible Causes
Radio link, firmware on the radio, RSS software or BTP/DHP may be faulty.
(2008-06-24) 2-339
Handling Procedure
Monitor the DRI. If the DRI device is being reset due to this alarm multiple times within a period
of 24 hours, then replace the Radio.
----End
2.202 30323 Tx VSWR Antenna Fault

Description
One of the duplexer blocks has reported a transmit VSWR fault. This alarm indicates high
reflected power level from TX antenna N (0-5).The additional data enumerates which duplexer
block detected the failure.
Attribute
30323 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-340 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
Alarm is reported.
Possible Causes
Broken or missing antenna/cable or poor connection to the antenna.
Handling Procedure
Send a service technician to troubleshoot the antenna connection.
----End

Description
This alarm indicates that the Radio Channel Unit (RCU) Transmit (TX) Synthesizer 1 is
identified as "not locked".If this alarm was raised on a CTU2 or CTU2D radio type, a failure of
one of the radio's synthesizers occurred.
Attribute
Parameters
ID Name Meaning
alarm.
(2008-06-24) 2-341
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
l For newgen, if the alarm occurrence has reached the threshold within the specified time
period, then take the board OOS, else reset the board, otherwise retrieve current event-
control state from dri device record; for an IN-Cell, DRI is taken to a DU wait state.If this
alarm was raised on a CTU2 or CTU2D radio type and the DRI is in Dual Carrier Mode,
the associated DRI will subsequently undergo the same alarm translation procedure.
Associated DRI state transitions will be tagged to the orignal alarm.
Possible Causes
Handling Procedure
In the TTY window, enter the state command to check the operational and the administrative
status of the DRI; check the state if
2-342 (2008-06-24)
OOS then try to INS it, if INSing doesn't bring the DRI back into service after couple of attempts,
then send the field representative to the site to replace the DRI generating the alarm.
----End

Description
This alarm indicates that the Radio Channel Unit (RCU) Transmit(TX) Synthesizer 2 is identified
as "not locked". If this alarm was raised on a CTU2 or CTU2D radio type, a failure of one of
the radio's synthesizers occurred.
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-343
ID Name Meaning
Impact on System
None
System Actions
l For newgen, if the alarm occurrence has reached the threshold within the specified time
period, then take the board OOS, else reset the board, otherwise retrieve current event-
control state from dri device record; for an IN-Cell, DRI is taken to a DU wait state.
Mode, the associated DRI will subsequently undergo the same alarm translation procedure.
Possible Causes
l dc power to TX synthesizer 2 may be been lost, input reference frequency may have been
lost, synthesizer may have failed,
l interconnect jumper might be blocked, Control Equalizer Board(CEB) might
l have failed, RF cable might be defective.
Handling Procedure
----End

Description
This alarm indicates that the output power if the Radio Channel Unit(RCU) Transmit(TX)
Synthesizer 1 was detected at a level below the normal power range required for RF transmission.
Attribute
2-344 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
l For newgen, if the alarm occurrence has reached
l the threshold within the specified time period, then take the board OOS, else
l reset the board, otherwise retrieve current event-control state from dri device record; for
an IN-Cell, DRI is taken to a DU wait state.
Possible Causes
l The TX synthesizer 1 byitself, or its switch or switch
(2008-06-24) 2-345
l control circuit may have been failed; the interconnect jumper ot the
l synthesizer might have been blocked; the control equalizer board may have
l failed.
Handling Procedure
----End

Description
This alarm indicates that the output power if the Radio Channel Unit(RCU) Transmit(TX)
Synthesizer 2 was detected at a level below the normal power range required for RF transmission.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-346 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
l The TX synthesizer 2 byitself, or its switch or switch control circuit may have been failed;
the interconnect jumper or the synthesizer might have been blocked; the control equalizer
board may have
l failed.
Handling Procedure
----End
(2008-06-24) 2-347

Description
This alarm indicates that the Radio Channel Unit(RCU) Transmit(TX) Synthesizer switch has
failed.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-348 (2008-06-24)
Impact on System
None
System Actions
Possible Causes
The TX synthesizer switch or switch control circuit may have failed; the interconnect jumper
might have been blocked; the simultaneous failure of TX synthesizer 1 and TX synthesizer 2.
Handling Procedure
----End

Description
This alarm indicates that the output power of the Radio Channel Unit(RCU) transmit(TX) exciter
has been detected to a level below the power range required for RF transmission.
Attribute

Parameters
ID Name Meaning
alarm.
(2008-06-24) 2-349
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
l If the alarm occurrence has reached the threshold
l within the specified time period, then take the board OOS, else reset the
l board.
Possible Causes
The TX synthesizer or its switch may have failed; the dc power to exciter may have failed; exciter
may have failed; exciter control circuit may have failed; interconnect jumper to exciter board
may have been blocked; RF stage on exciter board may have failed; RF cable may have been
defective; the modulator may have failed.
Handling Procedure
Monitor the DRI by checking its state, if state
2-350 (2008-06-24)
indicates OOS then go to the TTY window, enter the state command to check the operational
and the administrative status of the DRI; check the state
if OOS then try to INS it, if INSing doesn't bring the DRI back into
service after couple of attempts, then send the field representative to
the site to replace the DRI generating the alarm.
----End

Description
This alarm indicates that the output power of the Radio Channel Unit(RCU) transmit(TX) exciter
has been detected to a level below the power range required for RF transmission.
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-351
ID Name Meaning
Impact on System
None
System Actions
l If the alarm occurrence has reached the threshold
l within the specified time period, then take the board OOS, else reset the
l board.
Possible Causes
dc power to the PA may have been lost; exciter power output may have been lost; PA control
circuit may have been lost; PA components may have failed; the failed components may have
resulted in spurious emissions.
Handling Procedure
Monitor the DRI by checking its state, if state

indicates OOS then go to the TTY window, enter the state command to check the operational
and the administrative status of the DRI; check the state
if OOS then try to INS it, if INSing doesn't bring the DRI back into
service after couple of attempts, then send the field representative to
the site to replace the DRI generating the alarm.
----End

Description
This alarm indicates that the output of the DRI Transmit(TX) Power Amplifier(PA) has been
detected at a level in excess of the power required to sustain RF transmission.
Attribute
2-352 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
If the alarm occurrence has reached the threshold within the specified time period, then take the
board OOS, else reset the board.
Possible Causes
PA control circuit may have failed; temperature variations may have caused a power increase;
firmware control algorithm may be in error.
(2008-06-24) 2-353
Handling Procedure
Monitor the DRI by checking its state, if state indicates OOS then go to the TTY window, enter
the state command to check the operational and the administrative status of the DRI; check the
state
if OOS then try to INS it, if INSing doesn't bring the DRI back into service after couple of
attempts, then send the field representative to the site to replace the DRI generating the alarm.
----End
2.211 30332 Power Amplifier Temperature High

Description
This alarm indicates that the DRI Transmit(TX) Power Amplifier(PA) has been detected at a
level in excess of a state operating temperature for the equipment.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-354 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
l For newgen platforms, if the alarm occurrence has reached the threshold within the
specified time period, then take the board OOS, else reset the board, otherwise retrieve
current event-control state from dri device record; for an IN-Cell, DRI is taken to a DU
wait state.
Possible Causes
Air flow may have been blocked; cooling fans may have failed; cabinet temperature may have
been excessive; PA control circuit may have failed; PA voltage regulation circuit may have
failed; RF output connection may have failed; DRI hardware components may have been
defective.
Handling Procedure
status of the DRI; check the state if OOS then try to INS it, if INSing doesn't bring the DRI back
into service
after couple of attempts, then send the field representative to the site to replace the DRI
generating the alarm.
----End
2.212 30333 Power Amplifier Communication Failure

Description
This alarm indicates that the Radio ChannelUnit(RCU) Transmit(TX) Power Amplifier(PA)
"Watchdog Timer" has timed out in the system. Either the PA or the PA processor has failed.
(2008-06-24) 2-355
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
If 3 of these alarms occur within 10 minutes, the DRI is taken OOS. Otherwise the DRI is Hard
Reset.
2-356 (2008-06-24)
Possible Causes
Due to corrupted software the PA control process may have failed; the PA control curcuit may
have lost dc power.
Handling Procedure
state
----End

Description
This alarm indicates that the Radio Channel Unit(RCU) Transmit(TX) Radio Frequency(RF)
modulator has failed.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-357
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
For an M-Cell, if the alarm occurrence has reached the threshold within the specified time period,
then take the board OOS, else reset the board, otherwise retrieve current event-control state from
dri device record; for an IN-Cell, DRI is taken to a DU wait state.
Possible Causes
The modulator may have failed or may have lost dc power or its output power may have been
too low, or may have been out of lock from the Receive(Rx) synthesizer 3.
Handling Procedure
into service
----End
2.214 30335 Power Amplifier Power Low But Functioning

Description
This alarm indicates that the DRI Transmit(TX) Power Amplifier(PA) output power is
marginally below specified limits, but calls may continue.
2-358 (2008-06-24)
Attribute

30335 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
None. Alarm is just reported.
(2008-06-24) 2-359
Possible Causes
PA control circuits may have lost dc power; exciter power output may have been low; PA
component may have failed.
Handling Procedure
status of the DRI; send a field representative to the site to replace the DRI generating the alarm;
Use the
performance management system to generate a call traffic report to be used to verify that the
traffic has been handled correctly by the BSS (cell) in which the DRI resides; Enter the
unlock_device command to bring the DRI (radio) back into service.
----End
2.215 30336 Power Amplifier Temperature High But

Functioning
Description
This alarm indicates that the temperature of the DRI Transmit(TX) Power AMplifier(PA) has
been detected at a level in excess of a normal operating temperature for the equipment.
Attribute

30336 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-360 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Air flow may have been blocked; cooling fans may have failed; ambient temperature may have
been excessive; Transmit(TX) combiner may have failed; RF element following the PA in the
transmit path PA may be faulty; RF output connection may have failed.
Handling Procedure
Send a field representative to the site to verify that the building air conditioning equipment is
cooling the building properly; field should verify the RF cable/connectors to the next RF element
in the transmit RF path are properly connected, where the next RF element in the transmit
RF path may be Tx Bandpass Filter, Tx combiner, Duplexer/Quadraplexer, or an Antenna(s); if
the malfunctioning component is still isolated,the field service representative should verify that
the
Duplexer/Quadraplexer, and Antenna(s) are functioning properly; after the malfuntioning
component is isolated, replace the suspect RF component or DRI.
----End
(2008-06-24) 2-361

Description
This alarm indicates that the Radio ChannelUnit(RCU) transmitter board has failed.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-362 (2008-06-24)
Impact on System
None
System Actions
Possible Causes
l The TX synthesizer may have failed; the TX board may have failed; The TX control circuit
may have failed; the dc power to the TX board may have been failed; the interconnection
to the TX board may have been blocked; RF cables may have been defective; power level
reference (13 Mhz) may have been
l lost.
Handling Procedure
state
----End

Description
This alarm indicates that the Cell Resource Manager(CRM) has failed to configure a DRI
timeslot 0 for RF channel resource allocation for call processing.
Attribute
Parameters
ID Name Meaning
alarm.
(2008-06-24) 2-363
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
If the Fatal fault flag on 5th byte is NO then device goes OOS else the physical connectivity
(PCHN) is disabled.
Possible Causes
The cell resource manager (CRM) may have been faulty; the middle man funnel(MMF) process
may have been faulty; RSS may have been faulty; Front End Process(FEP) may have been faulty;
Radio Channel Unit(RCU)
Handling Procedure
Review the DRI device alarm message for the device failed alarm; in a TTY window, enter the
state command to check the operational and administrative status of the DRI; Send a field
representative to the site to replace the DRI generating the alarm.
----End
2-364 (2008-06-24)

Description
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-365
Impact on System
None
System Actions
(PCHN) is disabled.
Possible Causes
Radio Channel Unit(RCU) may have been faulty.
Handling Procedure
----End

Description
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
2-366 (2008-06-24)
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
(PCHN) is disabled.
Possible Causes
Handling Procedure
----End
(2008-06-24) 2-367

Description
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-368 (2008-06-24)
Impact on System
None
System Actions
(PCHN) is disabled.
Possible Causes
Handling Procedure
----End

Description
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
(2008-06-24) 2-369
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
(PCHN) is disabled.
Possible Causes
Handling Procedure
----End
2-370 (2008-06-24)

Description
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-371
Impact on System
None
System Actions
(PCHN) is disabled.
Possible Causes
Handling Procedure
----End

Description
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
2-372 (2008-06-24)
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
(PCHN) is disabled.
Possible Causes
Handling Procedure
----End
(2008-06-24) 2-373

Description
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-374 (2008-06-24)
Impact on System
None
System Actions
(PCHN) is disabled.
Possible Causes
Handling Procedure
----End

Description
This alarm indicates that the Radio Channel Unit(RCU) Receive(RX) Synthesizer 1 has been
indentified as "not locked". If this alarm was raised on a CTU2 or CTU2D radio type, a failure
of one of the radio's synthesizers occurred.
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
(2008-06-24) 2-375
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
dri device record; for an IN-Cell, DRI is taken to a DU wait state.If this alarm was raised on a
CTU2 or CTU2D radio type and the DRI is in Dual Carrier Mode, the associated DRI will
subsequently undergo the same alarm translation procedure. Associated DRI state transitions
will be tagged to the orignal alarm.
Possible Causes
dc power to the RX synthesizer 1 may have been lost; input reference frequency may have been
lost; RX synthesizer 1 may have failed; interconnect jumper to the RX synthesizer 2 board may
have been blocked.
Handling Procedure
into service
2-376 (2008-06-24)
----End

Description
indentified as "not locked".If this alarm was raised on a CTU2 or CTU2D radio type, a failure
of one of the radio's synthesizers occurred.
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-377
ID Name Meaning
Impact on System
None
System Actions
dri device record; for an IN-Cell, DRI is taken to a DU wait state.If this alarm was raised on a
CTU2 or CTU2D radio type and the DRI is in Dual Carrier Mode, the associated DRI will
subsequently undergo the same alarm translation procedure. Associated DRI state transitions
will be tagged to the orignal alarm.
Possible Causes
have been blocked.
Handling Procedure
into service
----End

Description
indentified as "not locked".
Attribute

2-378 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
have been blocked.
(2008-06-24) 2-379
Handling Procedure
into service
----End

Description
This alarm indicates that the output power of the Radio Channel Unit(RCU) Receive(RX)
Synthesizer 1 has been detected at a level below the normal power range required for RF signal
reception.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-380 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
RX synthesizer 1 may have been failed; RX synthesizer switch may have been failed; RX
synthesizer switch control circuits may have been failed; interconnect jumper to the synthesizer
board may have been blocked; Control Equalizer Board(CEB) may have failed.
Handling Procedure
into service
----End

Description
reception.
(2008-06-24) 2-381
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
2-382 (2008-06-24)
Possible Causes
Handling Procedure
into service
----End

Description
reception.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-383
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
into service
----End
2-384 (2008-06-24)

Description
This alarm indicates that the Radio Channel Unit(RCU) Receive Synthesizer switch has failed.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-385
Impact on System
None
System Actions
Possible Causes
RX synthesizer switch may have been failed; RX synthesizer switch control circuits may have
been failed; interconnect jumper to the synthesizer board may have been blocked; simultaneqou
failure of RX synthesizer 1 and RX sythensizer 2; Control Equalizer Board(CEB) may have
failed.
Handling Procedure
into service
----End

Description
This alarm indicates that the Radio Channel Unit(RCU) Main Receive Intermediate Frequency
(IF) has failed.
Attribute
Parameters
ID Name Meaning
alarm.
2-386 (2008-06-24)
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
dc power voltage to IF may have been out of the required range; the dc power drain of the Mail
IF may have been out of the required range; the IF components may have failed.
Handling Procedure
into service
(2008-06-24) 2-387
----End

Description
This alarm indicates that the Radio Channel Unit(RCU) Receive Signal Strength Indicator(RSSI)
branch has failed.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-388 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
dc power voltage to RSSI branch may have been out of the required range; the dc power current
drain of the RSSI branch may have been out of the required range; RSSI branch components
may have failed; interconnect jumper to the RSSI broad may have been blocked; 10.7 MHz
oscillator on the RSSI board may have been mistuned.
Handling Procedure
into service
----End

Description
This alarm indicates that the Radio Channel Unit(RCU) Receiver front-end has failed.
Attribute

(2008-06-24) 2-389
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
dc power voltage to the front-end may have been out of the required range; dc power current
drain of the front-end may have been out of the required range; intermediate frequency(IF)
components may have failed; interconnect jumper to the receiver front-end broad may have been
blocked.
2-390 (2008-06-24)
Handling Procedure
state
----End

Description
This alarm indicates that the Radio Channel Unit(RCU) Receiver I-Channel Analog to Digital
(A/D) power has consistently underflowed.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-391
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
A/D converter may have failed; AGC system may have failed; RSSI branch may have failed;
Main Intermediate Frequency may have failed; Control Equalizer Board(CEB) interface to the
I-Channel A/D convertor may have been defective.
Handling Procedure
into service
----End

Description
This alarm indicates that the Radio Channel Unit(RCU) Receiver Q-Channel Analog to Digital
(A/D) power has consistently underflowed.
2-392 (2008-06-24)
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
(2008-06-24) 2-393
Possible Causes
Q-Channel A/D convertor may have been defective.
Handling Procedure
into service
----End

Description
This alarm indicates that either the Radio Channel Unit(RCU) Receiver I-Channel Analog to
Digital (A/D) power has consistently underflowed OR if a Diversity RCU (DRCU) is involved,
Branch 2 power is either underflowed or overflowed.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-394 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
A/D converter may have failed; AGC system may have failed;RSSI branch may have failed;
Main Intermediate Frequency may have failed;Control Equalizer Board(CEB) interface to the
Handling Procedure
into service
----End
(2008-06-24) 2-395

Description
This alarm indicates that the Radio Channel Unit(RCU) Receiver Q-Channel Analog to Digital
(A/D) power consistently underflowed.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-396 (2008-06-24)
Impact on System
None
System Actions
Possible Causes
Handling Procedure
into service
----End

Description
This alarm indicates that the Radio Channel Unit(RCU) Receiver branch 1 has failed.
Attribute

Parameters
ID Name Meaning
alarm.
(2008-06-24) 2-397
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Receiver board may have failed; dc power to the receiver board may have filed; receiver board
control circuit may have failed; interconnect jumper to the receiver board may have been
blocked.
Handling Procedure
into service
2-398 (2008-06-24)
----End

Description
This alarm indicates that the Radio Channel Unit(RCU) Receiver branch 2 has failed.
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-399
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Receiver board may have failed; dc power to the receiver board may have filed; receiver board
control circuit may have failed; interconnect jumper to the receiver board may have been
blocked.
Handling Procedure
into service
----End

Description
This alarm indicates that the Digital Radio Interface(DRI) has detected that the Radio Frequency
Module(RFM) receiver board at an M-Cell micro site has failed.
Attribute
2-400 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Receiver board may have failed; dc power to the receiver board may have bene lost.
(2008-06-24) 2-401
Handling Procedure
into service
----End

Description
This alarm indicates that there is an error related to the PLL for GSM timing.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-402 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
l The DRI is Reset. If the alarm occurs a 2nd time within 10 minutes of the first alarm, then
the DRI is taken OOS.If this alarm was raised on a CTU2 or CTU2D radio type and the
DRI is in Dual Carrier
l Mode, the associated DRI will subsequently undergo the same reset-OOS procedure.
Possible Causes
l For all DRIs except CTU2 and CTU2D, the possible cause of the alarm is given in the
second byte of the additional info. RCU fault code: 0 (byte 2) -- The PLL synthesizer may
have failed; or dc power
l to the 13 MHz synthesizer may have been lost; or faulty fibre optic downlink path from the
DRI; or input frequency reference to the 13MHz PLL synthesizer may have been lost. RCU
Fault code: 1 (byte 2) -- Same as fault code 0; or GSM timing chain may have failed.For
CTU2 or CTU2D: this alarm indicates a hardware failure.
Handling Procedure
Monitor the system. If the DRI is taken OOS by the BSS then INS the DRI. If the DRI is taken
OOS again by this alarm then the Radio may need to be replaced.
----End

Description
GSM timing chain is out of synch with the higher software layers.
(2008-06-24) 2-403
Attribute
30364 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
l If 3 of these alarms occur within 10 minutes, the DRI is taken OOS. Otherwise the DRI is
Soft Reset.
2-404 (2008-06-24)
Mode, the associated DRI will subsequently undergo the same reset-reset-OOS procedure.
Possible Causes
1) The failure of GSM timing chain 2) Failure of timing 3) Momentary loss of synchronization
because of a burst in communications link.
Handling Procedure
----End

Description
The number of CRC errors on the data link exceeded the allowable limits.
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-405
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
MCU Based Site: If 3 of these alarms occur within 10 minutes of the first alarm, then the DRI
is taken OOS. Incell: DRI is put into Disabled-Wait state, then gets reset when the alarm is
cleared.
Possible Causes
1) Faulty DRI/RCU data link 2) DRI/RCU data link noise 3) The DRI/RCU data link may have
been intermittent causing it to fail 4)Faulty fibre optic interface circuit 5) Faulty data recovery
circuit.
Handling Procedure
----End

Description
HDLC transmit FIFO to fibre links consistently underflows.
2-406 (2008-06-24)
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
If 3 of these alarms occur within 10 minutes, the DRI is taken OOS. Otherwise the DRI is Soft
Reset.
(2008-06-24) 2-407
Possible Causes
1) Defective RCU timing chain 2) Defective communications interface between the HDLC link
and control processor 3) Faulty control circuits.
Handling Procedure
----End

Description
HDLC receive FIFO to fibre links consistently overflows.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-408 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Reset.
Possible Causes
1) Defective RCU timing chain 2) Defective communications interface between the HDLC link
and control processor 3) Faulty control circuits.
Handling Procedure
----End
2.247 30368 Receive Matrix Failure

Description
The receive matrix control link failed.
Attribute

30368 Major Fault
(2008-06-24) 2-409
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
None
Possible Causes
1) Faulty RX matrix 2) Defective open circuit coaxial cable between the RCU and the matrix 3)
Defective short circuit coaxial cable between the RCU and the matrix 4) Defective Control
Equalizer Board (CEB) control circuits 5) Defective open circuit on the front-end board matrix
interface 6) Defective short circuit on the front-end board matrix interface;incorrect SURF type
located in cabinet; incorrect SURF2 positioning in H2 dual band adapter unit; mismatched
antenna_select / SURF port.
2-410 (2008-06-24)
Handling Procedure
Review the device alarm messages and monitor the DRI. If more than 1 DRI is reporting an
alarm, verify that the matrix module had dc input power otherwise check for faulty hardware
(radio (D)RCU, PAB, RF cable/connectors to the matrix module (IDU)etc) and replace it if
needed.
Replace the Rx connector if it's removed.If the cabinet is dual band Horizon2macro ensure the
position of SURF2s relevant to CTU2s or CTU2Ds is correct.
----End
2.248 30369 Transceiver to Combiner Communication

Failure
Description
The communication link with the transmit combiner via the specified RCU has failed.
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-411
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
The failing Combiner device is placed to OOS and the switchover is made to standby Combiner
device. If both combiner devices fail,all radios connected to this Combiner are placed OOS.
Possible Causes
1) Faulty TX combiner (COMB) 2) The dc power to the COMB may have been lost. 3) Defective
open circuit coaxial cable between the RCU and COMB 4) Defective shorted circuit coaxial
cable between the RCU and the COMB 5) Defective COMB circuit interface in the RCU.
Handling Procedure
Check the status of both the combiners. If any one of them is in-service and other is in active
standby state, then further fault isolation is not needed. If only one of them is inservice and the
other is not, then suspect a link failure and replace necessary hardware. If both of them are not
in-service, replace the combiner.
----End
2.249 30370 Control Processor to Power Amplifier

Description
The communication link to the RCU power amplifier failed.
Attribute
2-412 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Reset.
Possible Causes
1) Defective CEB/PA control code 2) The noise present on the CEB to PA link 3) Defective
hardware link on either side of CEB/PA control processors.
(2008-06-24) 2-413
Handling Procedure
----End
2.250 30371 Control Processor to Equalizer Communication

Failure
Description
The communication link between the Control Equalizer Board (CEB) host processor and the
Equalizer Board (EQB) processor is lost.
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-414 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Reset.
Possible Causes
1) Faulty communication link between CEB and EQB 2) The communication link may have
been seized by one of the EQB processors causing the link to fail. 3) The seizure of
communication link by the CEB processor.
Handling Procedure
----End
2.251 30372 Power Supply Failure

Description
An RCU (DRI) power supply failed.
Attribute

(2008-06-24) 2-415
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
l If 3 of these alarms occur within 10 minutes, the DRI is taken OOS. Otherwise the DRI is
Soft Reset.
2-416 (2008-06-24)
Possible Causes
l 1) The dc supply voltage(s) within the RCU may have been out of the acceptable range. 2)
Faulty dc supply voltage(s) within the RCU 3) The external power source voltage is out of
the acceptable range
l causing the power supply to fail.
Handling Procedure
----End

Description
An excessive number of byte count errors were encountered.
Attribute

30373 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-417
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Reset.
Possible Causes
1) The corrupted DRI software 2) The corrupted CEB software 3) The HDLC link to the DRI
may be intermittent 4) The HDLC link to the RCU may be intermittent.
Handling Procedure
----End
2.253 30374 Control Processor Message Queue Overflowed

Description
The CEB message queue was overflowed.
Attribute
30374 Major Fault
2-418 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Reset.
Possible Causes
1) The higher layer process may have been sending an excessive number of messages too quickly.
2) The CEB may not have been processing messages. 3) The corrupted CEB software/DRI
software/Fault Management (to BSS) software or defective CEB hardware.
(2008-06-24) 2-419
Handling Procedure
----End

Description
The receiver I channel FIFO has consistently overflowed.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-420 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
Reset.
Possible Causes
1) The failure of control circuits 2) The failure of timing circuits.
Handling Procedure
----End

Description
The receiver Q channel FIFO has consistently overflowed.
Attribute
Parameters
ID Name Meaning
alarm.
(2008-06-24) 2-421
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Reset.
Possible Causes
1) The failure of control circuits 2) The failure of timing circuits.
Handling Procedure
----End
2-422 (2008-06-24)

Description
The equalizer output data has consistently overflowed.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-423
Impact on System
None
System Actions
Reset.
Possible Causes
1) Expired watchdog timer of CEB 2) The failure of control circuits 3) The failure of timing
circuits.
Handling Procedure
----End

Description
The equalizer output control FIFO has consistently overflowed.
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-424 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Reset.
Possible Causes
1) Expired watchdog timer of CEB 2) The failure of control circuits 3) The failure of timing
circuits.
Handling Procedure
----End
2.258 30379 Transmitter Out of Synchronization

Description
The modulator interface has lost synchronization with the RCU timing chain.
(2008-06-24) 2-425
Attribute
30379 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Reset.
2-426 (2008-06-24)
Possible Causes
l 1) Defective CEB timing chain 2) The disruption of synchronization because of the noise
present on the fibre link 3) The 5-Volt supply voltage may have "low-switched" causing
the synchronization to be
l disrupted. 4) Failure of 13 MHz clock from Slave PLL 5) Failure of the recovered clock
on the fibre link to the RCU 6) Failure of the timing circuits.
Handling Procedure
Monitor the DRI. If the DRI is in a D-U/OOS state, attempt to return the device to service. If it
changes to "clear", cease fault resolution, otherwise replace the suspect DRI (D)RCU. Verify
that the traffic is being handled correctly at BSS (cell) in which this DRI resides. The DRI can
be INSed one last time, before actually replacing the radio.
----End
2.259 30380 Receive Matrix Branch 2 Control Link Failure

Description
The receive matrix control link has failed.
Attribute
30380 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-427
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
None
Possible Causes
l 1) Faulty RX matrix 2) Defective open circuit coaxial cable between the RCU and the
matrix 3) Defective short circuit coaxial cable between the RCU and the matrix 4) Defective
CEB control circuits 5)Defective open circuits on the front-end board matrix interface 6)
Defective
l short circuit on the front-end board matrix interface.
Handling Procedure
Review the device alarm messages and monitor the DRI. If more than 1 DRI is reporting an
alarm, verify that the matrix module had dc input power otherwise check for faulty hardware
(radio (D)RCU, PAB, RF cable/connectors to the matrix module (IDU)etc) and replace it if
needed.Replace the Rx connector if it's removed.
----End

Description
HDLC downlink communication between the higher level devices and the radio has failed.
2-428 (2008-06-24)
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Reset.
(2008-06-24) 2-429
Possible Causes
The lost communications between RSS and DRI.
Handling Procedure
----End

Description
The Destination Point Code (DPC) 40.96 MHz Phase Lock Loop (PLL) is Out of Lock.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-430 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Reset.
Possible Causes
1) The loss of dc power to the PLL 2) The loss of input reference to the PLL.
Handling Procedure
----End

Description
The output power from the Destination Point Code 40.96 MHz PLL is out of limits.
Attribute
(2008-06-24) 2-431
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
MCU Based Site: If 3 of these alarms occur within 10 minutes of the first alarm, then the DRI
is taken OOS. Incell: DRI is put into Disabled-Wait state, then gets reset when the alarm is
cleared.
Possible Causes
1) The loss of dc power to the 40.96 MHz PLL 2) The failure of DPC PLL synthesizer
components.
2-432 (2008-06-24)
Handling Procedure
----End
2.263 30384 Control Processor Firmware Failure

Description
The OSCAR processor has experienced an unrecoverable software error.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-433
ID Name Meaning
Impact on System
None
System Actions
l The affected DRI is hard reset when this alarm occurs. If this alarm occurs three times
within a
l 10 minute period, the DRI is hard reset on the first two occurrences and then placed OOS
on
l the third occurrence.
Possible Causes
l The following are the possible causes for this alarm:
l ? An internal exception generated by a DSP.
l ? An internal hardware or software exception generated on an M-Cell micro.
Handling Procedure
----End
2.264 30385 Control Processor Configuration Mismatch

Description
The control processor in the MCU is in an improper operational state.
Attribute

30385 Major Fault
2-434 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Reset.
Possible Causes
1) The corrupted BSS (or specific BTS) software load 2)Momentary fault experienced by the
BSS software/firmware.
(2008-06-24) 2-435
Handling Procedure
----End
2.265 30386 Equalizer Configuration Mismatch

Description
One of the M-Cellmicro equalizer processors is currently in an improper operational state.
Attribute

30386 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-436 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
Reset.
Possible Causes
1) The BSS (or specific BTS) software download may have failed.
Handling Procedure
----End

Description
Either the GSM timing chain is Out Of Lock, or output power from the 13 MHz PLL for the
GSM timing chain is out of limits.
Attribute
Parameters
ID Name Meaning
alarm.
(2008-06-24) 2-437
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Reset.
Possible Causes
l 1) The loss of dc power to the 13 MHz synthesizer 2) The failure of PLL synthesizer
components 3) The faulty fibre optic downlink path from the DRI 4) The failure of the
GSM timing chain 5) The loss of
l input frequency reference to 13 MHz PLL synthesizer.
Handling Procedure
2-438 (2008-06-24)
----End
2.267 30388 Invalid Calibration Data

Description
The calibration data cannot be used because it has been corrupted.
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-439
ID Name Meaning
Impact on System
None
System Actions
Reset.
Possible Causes
1) Corrupted (RX, TX, or cabinet) calibration data 2)Corruption of the calibration data by the
OMC operator
Handling Procedure
----End

Description
A watchdog timer for an equalizer DSP (0 to 7) board on RCU has expired. This alarm will be
genarted for DRI alarm codes 176 to 183 corresponding to DSPs 0 to 7. Each alarm will indicate
the corresponding DSP.
Attribute
30389 Major Fault
Parameters
ID Name Meaning
alarm.
2-440 (2008-06-24)
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
The DRI is Soft Reset.
Possible Causes
) The hardware of the equalizer DSP block (0-7) may be defective. 2.) The hardware of the CEB
may be defective. 3.) The EQ DSP software may be faulty.
Handling Procedure
If the DRI is OOS after receiving this alarm then INS the DRI to see if it comes back into service.
If the DRI remains OOS then the Radio may need to be replaced.
----End
(2008-06-24) 2-441
2.269 30390 Equalizer Firmware Failure

Description
The M-Cellmicro equalizer processor has experienced an unrecoverable firmware
error.processor has malfunctioned. When this processor has stopped normal execution of the
operational code, this alarm is generated.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-442 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
If 3 of these alarms occur within 10 minutes, the DRI is taken OOS. Otherwise the DRI is Hard
Reset.
Possible Causes
) The DSP may have generated an internal exception message. 2.) The equalizer H/W may have
experienced a stack overflow or underflow. 3.) The DRI S/W may have experienced a stack
overflow or underflow.4.) The DRI S/W may have experienced illegal instruction from (internal)
S/W protocol.
Handling Procedure
----End

Description
The received BBH data had incorrect checksums. For CTU2 or CTU2D radio it could also be
message loss/corruption or invalid data.
Attribute
Parameters
ID Name Meaning
alarm.
(2008-06-24) 2-443
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Upon receiving the first alarm, use gathering method to gather the alarm data within two minutes
delay period. After the delay, if the alarm count is larger than the alarm clear count or the alarm
count is larger than five, then generate the alarm and apply reset retry mechanism (i.e.,Reset the
DRI device at least 2 times. If the alarm reoccurs after the second reset within twenty minutes,
then the DRI will be taken out of service).
Possible Causes
Handling Procedure
If the alarm occurs, perform the following:1. Review the alarm report/event logs to determine
the Site where this alarm is occurring.2. Enter the state command to check the operational and
administrative state of the DRI devices on the site where this alarm is occurring.3. Send a field
2-444 (2008-06-24)
representative to the site to replace the faulty radio if the radio is taken out of service by the
system due to this alarm.
----End
2.271 30392 Baseband Hopping GSM Timeslot

Misalignment
Description
The radio is unable to perform the base band hopping properly since the time slot provided in
the base band hopping data misaligns with what the radio is expecting.
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-445
ID Name Meaning
Impact on System
None
System Actions
Upon receiving the first alarm, use gathering method to gather the alarm data within two minutes
delay period. After the delay, if the alarm count is larger than the alarm clear count or the alarm
count is larger than five, then generate the alarm and apply reset retry mechanism (i.e.,Reset the
DRI device at least 2 times. If the alarm reoccurs after the second reset within twenty minutes,
then the DRI will be taken out of service).
Possible Causes
The TDM timeslot path connects may not be properly configured at the MCU, or the TDM
hardware may be defective.
Handling Procedure
If the alarm occurs, perform the following:1. Review the alarm report/event logs to determine
the Site where this alarm is occurring.2. Enter the state command to check the operational and
administrative state of the DRI devices on the site where this alarm is occurring.4. Send a field
representative to the site to replace the faulty radio if the radio is taken out of service by the
system due to this alarm.
----End
2.272 30393 RF Unit Power Supply Unit - Input Failure

Description
Main Power Supply to RF Unit has been lost and the RF Unit is operating on the backup power
supply.
Attribute

30393 Warning Fault
2-446 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
None
Possible Causes
l Failure of the main AC supply into external AC/DC converter.
l Failure of supply fuse/opening of protective device.
l Failure of +25V DC feed into the RF Unit.
l Connector/ lead from the external AC/DC converter
(2008-06-24) 2-447
l broken or removed from RF Unit input.
Handling Procedure
Investigate the loss of the main supply input.
----End
2.273 30394 RF Unit Over Temperature

Description
AC/DC converter within the RF Head Unit has detected an "Over Temperature" condition.
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-448 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
The affected DRI is disabled.
Possible Causes
l Failure of the building air conditioning system and subsequent increase of unit's ambient
temperature (i.e greater than 45 degree centigrade)
l Incorrect positioning of RF Unit above/too close to external heat source.
l Blockage of air vent holes around RF Unit.
Handling Procedure
Investigate the cause of the over temperature condition and then INS the DRI.
----End
2.274 30395 RF Unit Low Voltage Disconnect Imminent

Description
Battery back-up voltage is nearing the point of initiating a disconnect of the load, i.e the RF
Unit.
Attribute
(2008-06-24) 2-449
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Alarm is reported and no translation action is taken.
Possible Causes
l Failure of the main AC supply into external AC/DC converter.
l Failure of supply fuse/opening of protective device.
l Failure of +25V DC feed into the RF Unit.
l Connector/ lead from the external AC/DC converter broken or removed from RF Unit input.
2-450 (2008-06-24)
Handling Procedure
Investigate the cause of the loss of the +25V DC supply and after the power is restored INS the
DRI.
----End
2.275 30396 RF Unit External Alarm Input

Description
External Input has a 'short circuit' across its inputs.
Attribute

30396 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-451
ID Name Meaning
Impact on System
None
System Actions
None
Possible Causes
Input Circuit Failure.
Handling Procedure
Investigate and clear the cause of the Input Short Circuit.

----End
2.276 30397 Internal Communication Error

Description
The CTU2's or CTU2D's cascaded integral combiner (CIC) has lost synch with the direct digital
synthesiser (DDS).
Attribute
30397 Major Fault
Parameters
ID Name Meaning
alarm.
2-452 (2008-06-24)
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
l DRI will undergo soft reset. If the alarm indication is received a second time the DRI will
be hard reset and DSP code load will occur.If a third indication is received within ten
minutes the DRI will be taken OOS,resulting in a loss of capacity.
l If the radio is operating in Dual Carrier Mode, the associated DRI will subsequently undergo
the same reset-reset-OOS procedure. DRI state changes for both DRIs will be tagged to the
initial alarm.
Possible Causes
Miscommunication between CIC and DDS.
Handling Procedure
(2008-06-24) 2-453
Monitor the DRI. If the BSS takes the DRI OOS, reset the DRI (reset_device) and monitor again.
If the BSS takes the DRI OOS because of the same alarm then replace the DRI.
----End
2.277 30398 Power Amplifier Temperature

Description
This alarm indicates that the Radio Channel Unit(RCU) Power Amplifier(PA) temperature has
registered above the accceptable temperature range for PA equipment.
Attribute

30398 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-454 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
Check the sanity of the processor and if it is faulty after doing a query or checks, the device is
taken OOS, else if the test doesn't fail then report this alarm.
Possible Causes
"PA temperature high" alarm must have been generated.
Handling Procedure
Check the link between DRI and RCU; send a field representative to the site to verify that the
building air conditioning equipment is cooling the building property; the field representative
should be prepared to check and/or replace the following items, if necessary: the fans, the RF
cable/connectors(used to connect the (d)RCU transmitter output) to the next RF element in the
transmit RF path, a Tx Bandpass Filter, a Tx Combiner, the Duplexer/Quadraplexer, the antenna
(s),
the RF component or (d)RCU.
----End
2.278 30399 Hopping DRI Failure

Description
This alarm indicates that a Digital Radio Interface(DRI) involved in an attempt to Base Band
Hop(BBH) has failed.
Attribute
30399 Warning Event
(2008-06-24) 2-455
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
The DRI is OOS; when the DRI is a hopping DRI.
Handling Procedure
2-456 (2008-06-24)
Review the alarm/event reports and determine the following: SITE, device identifiers Cage, and
slot number; In the TTY window, enter the state command to check the operational and the
administrative
status of the DRI; Try INSing the DRI and if it doesn't come up then replace the DRI.
----End
2.279 30400 Front End Processor Failure

Description
This Alarm indicates that a Digital Radio Interface(DRI) Front End Processor (FEP) has failed.
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-457
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
The DRI may have been defective; the DRI software may have been faulty.
Handling Procedure
status of the DRI; send a field representative to the site to replace the DRI generating the alarm;
Use the
performance management system to generate a call traffic report to be used to verify that the
traffic has been handled correctly by the BSS (cell) in which the DRI resides; Enter the
unlock_devie command to bring the DRI (radio) back into service.
----End
2.280 30401 Channel Coder Failure

Description
This alarm indicates that the DRI channel coding digital signal processor(CCDSP) has failed.
Attribute
Parameters
ID Name Meaning
alarm.
2-458 (2008-06-24)
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
The DRI may have been defective.
Handling Procedure
Monitor the state of the DRI, if DRI is still OOS then try INSing it. After INSing it, if it is still
OOS then replace the device.
----End
(2008-06-24) 2-459
2.281 30402 Transceiver Processor Failure

Description
On a CTU2 or CTU2D this alarm indicates the radio firmware has failed to respond to payload
alive or fault audit queries. For all other platforms this alarm indicates that the Digital Radio
Interface(DRI) Radio Channel Unit (RCU) Control Equalizer Board (CEB) has failed.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-460 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
DRI will undergo soft reset. If the alarm indication is received a second time the DRI will be
hard reset and DSP code load will occur.If a third indication is received within ten minutes the
DRI will be taken OOS,resulting in a loss of capacity.If the radio is a CTU2 or CTU2D operating
in Dual Carrier Mode, the associated DRI will subsequently undergo the same reset-reset-OOS
procedure. DRI state changes for both DRIs will be tagged to the initial alarm.
Possible Causes
CTU2 or CTU2D: DSP on which firmware resides is unresponsive.Other platforms: RCU may
be defective; DRI extender(DRIX) board may be defective.
Handling Procedure
----End

Description
This alarm indicates that the Digital Radio Interface(DRI) Radio Channel Unit(RCU) Equalizer
Digitized Signal Processor(EQ DSP) has failed.
Attribute
Parameters
ID Name Meaning
alarm.
(2008-06-24) 2-461
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
RCU may have been defective; DRI software may have been faulty; RSS software may have
been faulty; RCU software may have been fualty.
Handling Procedure
----End
2-462 (2008-06-24)
2.283 30404 Power Amplifier Failure

Description
This alarm indicates that the Digital Radio Interface(DRI) Radio Channel Unit(RCU) Power
Amplifier(PA) has failed.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-463
Impact on System
None
System Actions
Possible Causes
PA may have been defective, FM software may have been faulty; DRI software mayhave been
faulty; RSS software may have been faulty; RCU software may have been faulty.
Handling Procedure
----End
2.284 30405 Transceiver Recovery Failure

Description
This alarm indicates that the Radio Channel Unit(RCU) has failed.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-464 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
RCU may have been failed
Handling Procedure
----End
2.285 30406 Transmission Suspended to Conserve Battery

Power
Description
The RCU stopped transmitting because the EAS Main Power Failure alarm has occurred and
according to the Battery Conservation feature database element - carrier_ins_on_power_fail, it
is necessary to disable this carrier.
(2008-06-24) 2-465
Attribute

30406 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
2-466 (2008-06-24)
Possible Causes
The state of the alarm sensor for the Main Power has changed since the last time the EAS was
polled by the GPROC FM software. Alarm caused by customer defined environmental sensor
activation.
Handling Procedure
Review that alarm/event report to determine where the fault condition(s) are occuring: SITE,
device identifiers, Cage, and slot number(s).
----End
2.286 30407 Invalid Transceiver Calibration Data

Description
This alarm indicates that the DRI currently being used at a site cannot access any form of
calibration data.
Attribute

30407 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-467
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
A DRI may have been installed at a site without being calibrated; An uncalibrated DRI may
have been replaced; The calibration data may have been cleared (after entering the clear_cal_data
command) and the DRI unlocked,before being calibrated.
Handling Procedure
Send a field representative to the site to calibrate the

DRI. This problem cannot be received from the OMC.
----End
2.287 30408 GPRS Not Supported by Radio

Description
The radio unit is not equipped to support GPRS service, but the radio function assigned to the
radio requires GPRS support.
2-468 (2008-06-24)
Attribute

30408 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
(2008-06-24) 2-469
Possible Causes
l No radio available to support GPRS and a GPRS radio function exists
l which is assigned to the radio unit.
Handling Procedure
Insert a radio which supports GPRS. Assign the

GPRS function to the radio which can support GPRS.
----End
2.288 30409 Invalid in-call modification of destination

channel type
Description
From the firmware viewpoint, higher layers have lost track of the configuration state of the
channel coder. Whilst a call is activated as TCH/AHS, a 'modify active channel request' is sent
to the channel coder requesting the call be switched to TCH/FS, TCH/EFS or TCH/F(data). This
is not allowed as TRAU backhaul for the two call types are incompatible. The message 'modify
active channel request' is only valid when TRAU rate remains the same.
Attribute

30409 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-470 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
l Alarm is not reported. If several of these alarms occur within a certain time frame such that
a pre-set threshold is reached,then the "Reset Due to Recurring Fault" alarm is generated.
If the condition
Possible Causes
Either the channel coder has received an invalid request or its internal channel type data stores
have been corrupted.
Handling Procedure
Monitor the DRI. The BSS will reset the DRI if these alarms continue at an unacceptable rate.
If the BSS takes the DRI OOS, then INS the DRI and monitor again. If the BSS takes the DRI
OOS because of the same alarm then replace the DRI.
----End
(2008-06-24) 2-471
2.289 30410 Safe Test Audit Failure

Description
while not taking the device out of service or interrupting its primary functionality. These tests
link which carries the audit messaging protocol (basic Acknowledge handshake).
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-472 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
Reset retry the device. If the DRI is a CTU2 or CTU2D in Dual Carrier Mode then both DRI
devices will be reset / taken OOS.
Possible Causes
Peripheral boards: Software is hung-up, MCAP interface software is not functioning correctly,
hardware problem on board causing no response,loss of power to board.DRI/RCU/PA:
peripheral board causes, problem with the RSS-DRI interface,bad DRIX, bad RCU data in/out
cabling.
Handling Procedure
Try resetting the DRI 3 times in 10 minutes. If the alarm still keeps coming then take the DRI
OOS.
----End
2.290 30412 Active Link Connection Failure

Description
This alarm indicates that the Digital Radio Interface(DRI)/Transceiver Carrier Unit(TCU) active
link connection to the active Base Transceiver Processor (BTP) has failed.
Attribute
Parameters
ID Name Meaning
alarm.
(2008-06-24) 2-473
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Based on the additional data, reset the device or bring it back into service. For CTU2 or CTU2D
radios operating in Dual Carrier Mode both DRIs will be taken OOS by this fault. In this case
one alarm will be raised and state transitions for both DRIs will be tagged to this alarm.
Possible Causes
l DRI may have failed; the BTP device may have failed; portion of the DRI and/or the active
BTP board that supports the active BTP link connection may have failed; A port on the
active Fibre Optic Extender(FOX) board may have failed; a port on the FMUX/XMUX
may have failed; communication fibre
l link may have failed; backplane connection may have failed.
Handling Procedure
Refer to the alarm message report; determine the site number, device identifier, slot number,
and cage of the faulty DRI or BTP device. In a TTY window, enter the state command to check
2-474 (2008-06-24)
the operational and administrative status of DRI or BTP; Determine whether DRI is
BUSY_UNLOCKED, or the BTP(MCU/H2SC) is ENABLED-UNLOCKED; Send a field
representative to the site to replace the faulty device: the DRI or the BTP device. In addition the
representative should be prepared to check all boards and active FOX/FMUX/XMUX fibre
connection that connects the Radio to the BTP and replace if necessary.
----End
2.291 30413 Standby Link Connection Failure

Description
The Digital Radio Interface (DRI)/Transceiver Carrier Unit standby link connection to the
standby BTP has failed.
Attribute

30413 Minor Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-475
ID Name Meaning
Impact on System
None
System Actions
Clear any FOX/FMUX/XMUX alarms associated with DRI.
Possible Causes
l DRI device may have failed; BTP device may have failed; portion of DRI and/or the active
BTP board that supports the standby BTP link connection may have failed; port on the
standby FOX/FMUX/XMUX
l board may have failed; communication fibre link may have failed; backplane connection
may have failed.
Handling Procedure
Refer to the alarm message report; determine the site number,device identifiers, slot number,
and cage of the faulty DRI or BTP device; In a TTY window, enter the state command to check
the operational and administrative the status of the standby BTP; Determine whether the BTP
is ENABLED-UNLOCKED; Try INSing the standby BTP, if INSing a couple of times doesn't
work then check the standby FOX/FMUX/XMUX fibre connections that connect the Radio to
the BTP.
----End
2.292 30414 Slow Flash Failure

Description
This alarm indicates that the failure to "read" or "write" to a slow flash EEPROM was detected
for a Digital Radio Interface (DRI)/Transceiver Control Unit(TCU) within an M-Cell micro site.
Attribute

30414 Warning Fault
2-476 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
flash EEPROM on the TCU is defective.
Handling Procedure
(2008-06-24) 2-477
Review the alarm report/event logs to determine the site where this alarm is occuring; in the
TTY window, enter the state command to check the operational and administrative state of the
DRI device; Enter the lock command to disable the DRI(TCU)with the faculty slow flash
EEPROM; send a field representative to the site to replace eiether a TCU in a M-Cell2/6 cabinet
or the M-Cellmicro containing the faculty TCU.
----End
2.293 30415 Non-Volatile Memory Failure

Description
This alarm indicates that the failure to "read" or "write" to the Non-Volatile(NV) flash EEPROM
was detected for a Digital Radio Interface (DRI)/Transceiver Control Unit(TCU) within an M-
Cell micro site.
Attribute
30415 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-478 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
NV flash EEPROM on the TCU is defective.
Handling Procedure
Review the alarm report/event logs to determine the site where this alarm is occuring; in the
TTY window, enter the state command to check the operational and administrative state of the
DRI device; Enter the lock command to disable the DRI(TCU)with the faculty slow flash
EEPROM; send a field representative to the site to replace either a TCU in a M-Cell2/6 cabinet
or the M-Cellmicro
containing the faculty TCU.
----End
2.294 30416 Process Safe Test Audit Failure

Description
This alarm indicates that the Digital Radio Interface(DRI) Transceiver Control Unit(TCU)
device process safe test audit has failed.
Attribute
30416 Warning Fault
(2008-06-24) 2-479
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
A process executing on the DRI failed to respond to the System Audit Process.
Handling Procedure
2-480 (2008-06-24)
For a reason code of 0, 1 or 3, the DRI requires a reset to correct the problem. If the reason code
is 2, the operator should try running the audit again while continuing to check the CPU utilization
statistics for the process. If this failure persists,the operator should contact MCSC or their local
field office.
----End
2.295 30417 Standby Link Connected to Wrong Device

Description
This alarm will be generated for each incorrect standby link connection in a BTS or in an
extended cabinet.
Attribute

30417 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-481
ID Name Meaning
Impact on System
None
System Actions
Clear any FOX/FMUX/XMUX alarms associated with TCU.
Possible Causes
FOX may have been connected to the wrong TCU port; BTP may have been connected to wrong
TCU; FMUX/XMUX may have been placed in the wrong slot; FMUX/XMUX may have been
connected to the wrong standby FMUX/XMUX in another extended cabinet.
Handling Procedure
Review the alarm report/event logs to determine the site where this alarm is occuring; Initiate
the data collection process for troubleshooting purposes; determine whether more than two
separate DRI
devices in a cabinet at a site are generatind this alarm; send field representative to the site to
check/verify the configuration of all M-Cell2, M-Cell6, HorizonMacro1/2 cage and cabinet
connections.
----End
2.296 30418 Unlocked Device Not In Service

Description
Device not in service due to some fault.
Attribute

30418 Warning Fault
2-482 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
l If there is no primary alarm active on the device,
l an alarm is generated indicating device not in service. The alarm
l is cleared when the device comes back in service. Locking a disabled
l device will clear this alarm.
Possible Causes
The system failed to bring the device in service.
(2008-06-24) 2-483
Handling Procedure
Investigate why the device is not in service, and try to

bring it back into service.
----End

Description
Indicates that the DRI has been requested to be taken out of service by the GPROC Fault
Management software.If this alarm was raised on a CTU2 or CTU2D radio type by the leaky
bucket method and the DRI is in Dual Carrier Mode, the associated DRI will also be taken OOS.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-484 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
Refer to the message report; determine the site number, device identifiers, slot number, and cage
of the faulty DRI device; initiate the apppropriate data collection processes for troubleshooting
purposes; in the TTY window, enter the state command to check the operational and
administrative the
status of the DRI; Determine whether the DRI is Busy-Unlocked; Enter the swap command to
switch the redundant DRI to active status; send a field representative to the site to replace the
DRI generating the alarm.
----End
2.298 30420 DRI hardware type mismatch with software

configuration
Description
The physically installed DRI in BTS is not compatible with TRX card configured by BSC.
(2008-06-24) 2-485
Attribute

30420 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Alarm is raised but no action is taken; service is unaffected.
2-486 (2008-06-24)
Possible Causes
Configure Hardware Type CTU2/CTU2D As CTU
Handling Procedure
Pls make the physical TRX's capability fitted with the radio carrier configuration in database.
----End

configuration
Description
Attribute

30421 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-487
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Alarm is raised.
Possible Causes
Configure Hardware Type CTU as SCTU2;Configure Hardware Type CTU2 as CCTU2;
Handling Procedure
----End

configuration
Description
Attribute
2-488 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Alarm is raised and impacted TRXs are taken OOS
Possible Causes
Configure Hardware Type CTU As CTU2/CTU2D
Handling Procedure
(2008-06-24) 2-489
----End
2.301 30423 RSL Link Disconnected

Description
Provides an indication of an RSL link disconnection. This is currently defined by the entity
requesting disconnection.
Attribute
30423 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-490 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
Alarm is reported.
Possible Causes
l Link on an E1 disconnects due to a normal disconnect process or because of a problem
l with the protocol/medium which is causing an unexpected disconnect to occur.
Handling Procedure
Wait atleast 10 minutes before taking any action. If the alarm is not cleared and the connection
is not established by then,the system will go into a "Continuous Retry" mode. Check if the RSL
has reported this RSL repeatedly. If so this may be a quality of service problem on one of the
E1/T1 links that carries this RSL. If this alarm has occurred repeatedly over a short period of
time then
RSL might not be functioning and may be faulty. Determine whether the E1 and/or SITE devices
specified for the PATH device are OOS. Check if the BSC-related E1 are in BU state.
----End
2.302 30424 LAPD Protocol Error

Description
This alarm is reported when the RSL detects an error.
Attribute
30424 Warning Event
Parameters
ID Name Meaning
alarm.
(2008-06-24) 2-491
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
The alarm is intermittent.
Possible Causes
l The possible cause of the alarm is given in the second byte of the
l additional info (fault code).
l Fault Codes: 0, 4 -- The timeslot assignments may not be correct;
l The connection to the physical link may have a different protocol;
l The physical media may have been faulty (for example, a noisy communication link).
l Fault code: 1 -- The external equipment may have experienced outages;
l The physical frame may have dropped;
2-492 (2008-06-24)
l The out-of-sequence frames to be received may have caused the failure.

l Fault codes: 2, 3 -- The connection may have been invalid;
l The DACS link may have been physically connected to the wrong line.
l Fault codes: 5, 8 -- The nailed connection may be missing
l (The connection may be correct for one direction, but incorrect for the other.);
l The physical media in one direction of the link may be faulty.
l Fault code: 6 -- The remote side of the link connection may be sending I-frames
l before the link was established.
l Fault codes: 7, 9 -- Physical link outage affecting the local to remote direction.
Handling Procedure
Check report logs for repeated occurrence of this alarm. If alarm occurs more than expected,
monitor the state of E1 related to the RSL and INS the RSL device. A field representative may
need to visit the site to determine the quality of the link and adjust/correct/replace it as
necessary. Consult Alarm Handling at the OMC customer documentation.
----End
2.303 30426 LAPD Protocol Error Threshold Exceeded

Description
Disables RSL due to LAPD Protocol Error Threshold being exceeded
Attribute

30426 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
(2008-06-24) 2-493
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Take the RSL OOS
Possible Causes
The number of RSL Intermittent alarms has exceeded threshold.
Handling Procedure
Investigate further the RSL if this keeps happening
----End
2.304 30427 Too Many LAPD Protocol Errors

Description
Too many LAPD Protocol errors have been received indicating poor link quality.
2-494 (2008-06-24)
Attribute

30427 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Reset the RSL.
(2008-06-24) 2-495
Possible Causes
4 or more LAPD Protocol errors were received within 1 second indicating major problems with
the RSL link.
Handling Procedure
Check report logs for repeated occurrence of this alarm.If alarm occurs more than expected,
monitor the state of E1 related to the RSL and INS the RSL device. A field representative may
need to visit the site to determine the quality of the link and adjust/correct/replace it as necessary.
Consult Alarm Handling at the OMC customer documentation.Investigate the RSL further if
this keeps happening
----End

Description
The COMB cavity 0 has failed to tune correctly.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-496 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Perform partial reset on the Combiner, 2. Reset the DRI/RCU attached to the faulty cavity.
Possible Causes
(1) The cavity tuning circuits may have been faulty.(2) The combiner cavity may be faulty. (3)
The antenna may be faulty.
Handling Procedure
If alarm has not cleared the radio or the combiner must be replaced.
----End

Description
Attribute

(2008-06-24) 2-497
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
2-498 (2008-06-24)
Handling Procedure
----End

Description
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-499
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute

Parameters
ID Name Meaning
alarm.
2-500 (2008-06-24)
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End
(2008-06-24) 2-501

Description
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-502 (2008-06-24)
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End
2.310 30516 Link A Sanity Failure

Description
The Watchdog timer in the master Combiner device Processor A has expired causing the link
from the (DRI) radio to the Remotely Tunable Combiner (RTC) to stop functioning.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-503
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
The Processor A on the RTC processor board has failed.
Handling Procedure
Check the states of the COMB, if one or both COMBs are DU, replace the COMBs. If one
COMB is BU and the other COMB is EU,check the COMB links.
----End
2.311 30517 Link B Sanity Failure

Description
The Watchdog timer in the master Combiner device Processor B has expired causing the link
from the (DRI) radio to the Remotely Tunable Combiner (RTC) to stop functioning.
2-504 (2008-06-24)
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
(2008-06-24) 2-505
Possible Causes
The Processor B on the RTC processor board has failed.
Handling Procedure
Check the states of the COMB, if one or both COMBs are DU, replace the COMBs. If one
COMB is BU and the other COMB is EU,check the COMB links.
----End
2.312 30518 Power Feed A Failure

Description
The main power feed A to the Combiner has failed. This alarm applies to the Remotely Tunable
Combiner (RTC) as well as the Transmit Antenna-Transceiver Interface (TATI) Combiner.
Attribute

30518 Minor Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-506 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Disables the Combiner if both Combiner power feeds have failed.
Possible Causes
(1) The dc power feed may have failed. (2) The RTC processor board may have failed. (3) The
TATI Control Board may have failed. (4) The external combiner fuse may be defective. (4) A
CCB/TCB fuse may be defective.
Handling Procedure
Check alarm output to determine whether there are any IAS fuse alarms being displayed for the
site. If the alarm severity is critical, send a field representative to the site to check the dc input
power path.
----End
2.313 30519 Power Feed B Failure

Description
The main power feed B to the Combiner has failed. This alarm applies to the Remotely Tunable
Combiner (RTC) as well as the Transmit Antenna-Transceiver Interface (TATI) Combiner.
Attribute

30519 Minor Fault
(2008-06-24) 2-507
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Disables the Combiner if both Combiner power feeds have failed.
Possible Causes
(1) The dc power feed may have failed. (2) The RTC processor board may have failed. (3) The
TATI Control Board may have failed. (4) The external combiner fuse may be defective. (4) A
CCB/TCB fuse may be defective.
2-508 (2008-06-24)
Handling Procedure
Check alarm output to determine whether there are any IAS fuse alarms being displayed for the
site. If the alarm severity is critical, send a field representative to the site to check the dc input
power path.
----End
2.314 30520 Full Reset

Description
The COMB has undergone a full reset. This alarm applies to the RTC as well as the TATI
Combiner.
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-509
ID Name Meaning
Impact on System
None
System Actions
Combiner will be reset(disabled-enabled).
Possible Causes
(1) The COMB forced a full reset. (2) The reset switches on the COMB may have been placed
into a "full reset" position. (3) A momentary power outage may have occurred.
Handling Procedure
After the fault condition has been resolved, verify that the COMBs and the DRIs that are
connected to the COMBs have been returned to an INS device state.
----End
2.315 30521 Partial Reset

Description
The COMB has undergone a partial reset in the system. This alarm applies to the RTC only.
Attribute
30521 Warning Event
Parameters
ID Name Meaning
alarm.
2-510 (2008-06-24)
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
No
Possible Causes
(1) The COMB may have forced a partial reset. (2) The reset switches on the COMB may have
been placed into a "full reset" position.
Handling Procedure
After the fault condition has been resolved, verify that the COMBs and the DRIs that are
connected to the COMBs have been returned to an INS device state.
----End
(2008-06-24) 2-511

Description
The TATI Combiner cavity 5 has failed to tune correctly.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-512 (2008-06-24)
Impact on System
None
System Actions
Possible Causes
(1) The cavity tuning circuits may have been faulty. (2) The combiner cavity may have been
faulty. (3) The antenna may have been faulty.
Handling Procedure
----End

Description
The TATI combiner Cavity Combining Block 0 (CCB 0) has failed. The CCB 0 controls
combiner cavities 0-2. This alarm applies to the TATI combiner only.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-513
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
The controlling DRIs for the failed combiner cavities are taken OOS.
Possible Causes
The TATI COMB CCB 0 hardware has failed.
Handling Procedure
Reset the Combiner and if the alarm does not clear replace the CCB 0.
----End

Description
The TATI combiner Cavity Combing Block 1 (CCB 1) has failed. The CCB 1 controls combiner
cavities 3-5. This alarm applies to the TATI Combiner only.
2-514 (2008-06-24)
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
The controlling DRIs for the failed combiner cavities are taken OOS.
(2008-06-24) 2-515
Possible Causes
The TATI COMB CCB 1 hardware has failed.
Handling Procedure
Reset the Combiner and if the alarm does not clear Replace the CCB 1.
----End
2.319 30525 Processor A Failure

Description
The TATI Processor A has failed due to the failure of the TATI Control Board 0.
Attribute

30525 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-516 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
None
Possible Causes
The TCB 0 board may have failed. The TCB 0 board may have been removed.
Handling Procedure
Check if the TCB board is properly inserted. If the TCB board is faulty replace it.
----End
2.320 30526 Processor B Failure

Description
The TATI Processor B has failed due to the failure of the TATI Control Board 0.
Attribute
30526 Major Fault
(2008-06-24) 2-517
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
None
Possible Causes
The TCB 0 board may have failed. The TCB 0 board may have been removed.
Handling Procedure
2-518 (2008-06-24)
Check if the TCB board is properly inserted. If the TCB board is faulty replace it.
----End

Description
Indicates that the COMB has been taken out of service by the Fault Management software.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-519
ID Name Meaning
Impact on System
None
System Actions
The combiner is taken OOS.
Possible Causes
Handling Procedure
Check the recent alarm output. If the alarm has not cleared, the radio and/or the COMB probably
need to be replaced. Send a field representative to the site to investigate and replace the radio,or
antenna connection etc..
----End

Description
The MSI board was unexpectedly re-initialized or reset.
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
2-520 (2008-06-24)
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Reset the MSI device and attempt to bring it back into service.
Possible Causes
Via the front panel switch, software reset, failure of the processor or failure of a peripheral board
related to the MSI.
Handling Procedure
Wait for the re-initialization sequence to complete.If the MSI device fails to become B-U, ins
the device and attempt to bring it back into service.If the MSI still does not become B-U, replace
the MSI board.
----End
(2008-06-24) 2-521

Description
while not taking the device Out-Of-Service or interrupting its primary functionality. These tests
link which carries the audit messaging protocol (basic ACK handshake). These tests are not
Service Affecting.
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-522 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
Reset the MSI board.
Possible Causes
l MSI software is hung up, MCAP interface software is not functioning correctly, MCAP
bus is bad, hardware problem on board causing no response, loss of power to board.
l Return code is as follows:
l Code Reason
l ------------------------------------------
l 0x0000 NIB_RC_SUCCESS
l 0x0001 NIB_RC_INV_LOC
l 0x0002 NIB_RC_INV_DEVICE
l 0x0003 NIB_RC_CODELOAD_NOT_REQD
l 0x0004 NIB_RC_CODELOAD_FAIL
l 0x0005 NIB_RC_PING_FAIL
l 0x0006 NIB_RC_CODELOAD_STARTED
l 0x0007 NIB_RC_CODELOAD_COMPLETE
l 0x0008 NIB_RC_PING_FAIL_EXCEPTION
l 0x0009 NIB_RC_PING_FAIL_KERNEL_FAIL
l 0x000A NIB_RC_PING_FAIL_UNKNOWN_ERROR
l 0x000B NIB_RC_PING_FAIL_COUNTER_FAIL
Handling Procedure
If the MSI does not become B-U or there is an excessive recurrence of this alarm, replace the
MSI board
----End

Description
The MSI(NIU) has lost connection to the active BTP(MCU).
(2008-06-24) 2-523
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Based on the additional data, reset the device or bring it back into service.
2-524 (2008-06-24)
Possible Causes
Failure of the MSI(NIU) device, the active BTP(MCU), the MSI(NIU) backplane connection ,
the BTP(MCU) backplane connection or the portion of the MSI(NIU) and/or the active BTP
(MCU) board that supports the BTP(MCU) link connection.
Handling Procedure
If the MSI(NIU) does not become B-U within a short period of time,then investigate the MSI
(NIU)-BTP(MCU) communications path. If the MSI(NIU) board is faulty, replace the MSI(NIU)
board.
----End

Description
Indicates that the MSI has been requested to be taken out of service by the GPROC Fault
Management software.
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-525
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
The device is taken OOS.
Possible Causes
Handling Procedure
Ins the device and attempt to bring it back into service.If the device still fails to become B-U,
replace the MSI board;
----End

Exceeded
Description
16).
2-526 (2008-06-24)
Attribute

30555 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
(2008-06-24) 2-527
Possible Causes
Handling Procedure
----End

Exceeded
Description
20).
Attribute
30556 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-528 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Exceeded
Description
511).
Attribute

30557 Major Fault
(2008-06-24) 2-529
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
For an alarm condition, this E1 is taken out of service.If it is an alarm clear and this E1 critical
alarm threshold exceeded alarm processing enable flag(mms_cat_enable flag) is on, this E1 fault
history is checked to test stability of this E1 If the stability test is passed this E1 will be enabled
and an alarm clear will be reported, else this E1 will be left disabled and a clear for this alarm
along with a critical alarm threshold exceeded alarm will be reported.
Possible Causes
2-530 (2008-06-24)
Handling Procedure
If the E1 is D-U, check whether the E1 or MSI is faulty.If E1/MSI is faulty, replace board else
check cabling, connections and the the link interface board. Verify as necessary, that the MTL,
OML or RSL links have been re-established and all SITEs have returned to service.
----End

Description
Attribute

30558 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-531
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Exceeded
Description
Attribute
30559 Warning Event
Parameters
ID Name Meaning
alarm.
2-532 (2008-06-24)
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End
(2008-06-24) 2-533

Description
Attribute

30560 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-534 (2008-06-24)
Impact on System
None
System Actions
For an alarm condition, this E1 is taken out of service.If it is an alarm clear and the E1 critical
history is checked to test stability of this E1. If the stability test is passed, this E1 will be enabled
Possible Causes
Handling Procedure
If this E1 is D-U, check whether the E1 or MSI is faulty.If E1/MSI is faulty, replace MSI board
else check cabling, connections and the the link interface board. Verify as necessary, that the
MTL, OML or RSL links have been re-established and all SITEs have returned to service.
----End

Description
Attribute

30561 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
(2008-06-24) 2-535
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
Monitor the situation to see if this alarm is a precursor to serious fault conditions. If both MSI
10 and MSI 11 alarms are present, perform a recalibration of the GCLK, if necessary.
----End

Description
2-536 (2008-06-24)
Attribute

30562 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
(2008-06-24) 2-537
Possible Causes
Handling Procedure
----End

Description
Attribute

30563 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-538 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
30564 Warning Event
(2008-06-24) 2-539
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
2-540 (2008-06-24)
----End

Description
Attribute

30565 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-541
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute

30566 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
2-542 (2008-06-24)
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End
(2008-06-24) 2-543

Description
Attribute

30567 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-544 (2008-06-24)
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
30568 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
(2008-06-24) 2-545
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End
2-546 (2008-06-24)

Description
Attribute

30569 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-547
Impact on System
None
System Actions
Possible Causes
threshold
Handling Procedure
----End

Description
Attribute
30570 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-548 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
threshold
Handling Procedure
----End

Description
Indicates that the E1 has been in and out of service repeatedly so many times that the system
will no longer try to recover from the faults.
(2008-06-24) 2-549
Attribute
30571 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
This alarm is based on tracking the frequency of OOS generating and clears for the E1. When
the E1 has reported OOS generating and clears 10 times within the last 10 minutes(the E1 is
unstable), the last clear is reported but the E1 is kept OOS and this alarm is reported.This alarm
2-550 (2008-06-24)
can be cleared by an INS of the E1 which will put the E1 back into service(if no OOS alarms
are active). Also, there is a periodic audit of how frequently the OOS alarms and clears are
occurring. Anytime the occurrences fall below the threshold, this alarm is cleared and the E1
enabled.
Possible Causes
Ten E1 critical alarms were generated in less than ten minutes. This condition may be caused
bad MSI board.
Handling Procedure
----End

Exceeded
Description
16).
Attribute
30572 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-551
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Exceeded
Description
20).
2-552 (2008-06-24)
Attribute

30573 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
(2008-06-24) 2-553
Possible Causes
Handling Procedure
----End

Exceeded
Description
511).
Attribute
30574 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-554 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
For an alarm condition, this E1 is taken out of service.If it is an alarm clear and this E1 critical
history is checked to test stability of this E1 If the stability test is passed this E1 will be enabled
Possible Causes
Handling Procedure
If the E1 is D-U, check whether the E1 or MSI is faulty.If E1/MSI is faulty, replace board else
check cabling, connections and the the link interface board. Verify as necessary, that the MTL,
OML or RSL links have been re-established and all SITEs have returned to service.
----End

Description
Attribute
30575 Warning Event
(2008-06-24) 2-555
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
2-556 (2008-06-24)
----End

Exceeded
Description
Attribute

30576 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-557
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
30577 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
2-558 (2008-06-24)
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
For an alarm condition, this E1 is taken out of service.If it is an alarm clear and the E1 critical
history is checked to test stability of this E1. If the stability test is passed, this E1 will be enabled
Possible Causes
Handling Procedure
----End
(2008-06-24) 2-559

Description
Attribute

30578 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-560 (2008-06-24)
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute

30579 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-561
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
2-562 (2008-06-24)
Attribute

30580 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
(2008-06-24) 2-563
Possible Causes
Handling Procedure
----End

Description
Attribute

30581 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-564 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
30582 Warning Event
(2008-06-24) 2-565
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
2-566 (2008-06-24)
----End

Description
Attribute

30583 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-567
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
30584 Major Fault
Parameters
ID Name Meaning
alarm.
2-568 (2008-06-24)
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
(2008-06-24) 2-569
----End

Description
Attribute

30585 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-570 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
30586 Warning Event
(2008-06-24) 2-571
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
threshold
2-572 (2008-06-24)
Handling Procedure
----End

Description
Attribute
30587 Warning Event
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-573
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
threshold
Handling Procedure
----End

Description
Attribute
30588 Major Fault
Parameters
ID Name Meaning
alarm.
2-574 (2008-06-24)
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
This alarm is based on tracking the frequency of OOS generating and clears for the E1. When
the E1 has reported OOS generating and clears 10 times within the last 10 minutes(the E1 is
unstable), the last clear is reported but the E1 is kept OOS and this alarm is reported.This alarm
can be cleared by an INS of the E1 which will put the E1 back into service(if no OOS alarms
are active). Also, there is a periodic audit of how frequently the OOS alarms and clears are
occurring. Anytime the occurrences fall below the threshold, this alarm is cleared and the E1
enabled.
Possible Causes
Ten E1 critical alarms were generated in less than ten minutes. This condition may be caused
bad MSI board.
Handling Procedure
(2008-06-24) 2-575
----End
2.360 30671 Cabinet Fan Failure

Description
This alarm indicates that a BTS or "Ancillary" cabinet fan (or fans) has failed. It is generated
when a fan has stopped functioning due to a power loss or an (air flow) obstruction causing the
equipment to stop. The obstruction may have damaged the unit. This alarm may be received in
conjunction with another IAS alarm (which will aid in fault diagnosis) including "80. IAS: Power
Supply Unit - Input Failure.", "81. IAS: Power Supply Unit - Output Failure.", or "82. IAS: BTS
Cabinet Over Temperature."
Attribute
30671 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-576 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
The alarm is reported.
Possible Causes
The air inlet vent to the fan unit may have been blocked causing the unit to fail, the air outlet
vent from the fan unit may have been blocked causing the unit to fail, the airways may be
obstructed causing the fan unit to fail, or the PSU may have been malfunctioning causing the
fan unit to stop.
Handling Procedure
If the alarm has not ceased, perform the following procedures: 1. Review the alarm report/event
logs to determine the cause of this alarm. 2. Send a field representative to the site to
locate the failed unit and determine if the inlet or outlet vents are blocked.
----End

Description
This alarm indicates that BSS software has detected a fan within fan tray 0 has either failed or
has not been properly installed.
Attribute
(2008-06-24) 2-577
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
A fan may be faulty. The fan fuses may be faulty. The fan tray may not be properly installed.
Handling Procedure
2-578 (2008-06-24)
Check the alarm board LEDs to verify that fan tray 0 has failed.
Check fuses or replace fan tray 0 (Quad Fan type).
----End

Description
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-579
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Handling Procedure
Check fuses or replace fan tray 1 .
----End

Description
Attribute
Parameters
ID Name Meaning
alarm.
2-580 (2008-06-24)
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
Check fuses or replace fan tray 2 (Quad Fan type).
----End
(2008-06-24) 2-581
2.364 30711 EAS has detected Main Power Failure

Description
Indicates a change in the state of the EAS Main Power Failure alarm since the last time it was
polled.
Attribute

30711 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-582 (2008-06-24)
Impact on System
None
System Actions
If the MPF feature is active, the system will disable a user defined number of DRIs one at a time
over a user defined time interval.
Possible Causes
The state of the alarm sensor has changed since the last time the EAS was polled. Alarm caused
by Main Power Failure environmental sensor activation.
Handling Procedure
Check the integrity of the physical cabling for the power on the site itself.
----End

Description
Indicates a change in the state of the Customer defined alarm since the last time it was polled.
Attribute

30712 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-583
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
None.
Possible Causes
The state of the alarm sensor has changed state since the last time the EAS was polled. Alarm
caused by customer defined environmental sensor activation.
Handling Procedure
If alarm persists, check to see whether the software is at fault by checking the specific fault and
its parameters. If the software is at fault, resolve the problem at the OMC. If not, check the
hardware problems at the site itself.
----End

Description
2-584 (2008-06-24)
Attribute

30713 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
None.
(2008-06-24) 2-585
Possible Causes
Handling Procedure
----End

Description
Attribute
30714 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-586 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
None.
Possible Causes
Handling Procedure
----End

Description
Attribute

30715 Warning Fault
(2008-06-24) 2-587
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
None.
Possible Causes
2-588 (2008-06-24)
Handling Procedure
----End

Description
Attribute

30716 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-589
ID Name Meaning
Impact on System
None
System Actions
None.
Possible Causes
Handling Procedure
----End

Description
Attribute
30717 Warning Fault
Parameters
ID Name Meaning
alarm.
2-590 (2008-06-24)
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
None.
Possible Causes
Handling Procedure
----End
(2008-06-24) 2-591

Description
Attribute

30718 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-592 (2008-06-24)
Impact on System
None
System Actions
None.
Possible Causes
Handling Procedure
----End

Description
Attribute
30719 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-593
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
None.
Possible Causes
Handling Procedure
----End

Description
2-594 (2008-06-24)
Attribute

30720 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
None.
(2008-06-24) 2-595
Possible Causes
Handling Procedure
----End

Description
Attribute
30721 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-596 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
None.
Possible Causes
Handling Procedure
----End

Description
Attribute

30722 Warning Fault
(2008-06-24) 2-597
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
None.
Possible Causes
2-598 (2008-06-24)
Handling Procedure
----End

Description
Attribute

30723 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-599
ID Name Meaning
Impact on System
None
System Actions
None.
Possible Causes
Handling Procedure
----End

Description
Attribute
30724 Warning Fault
Parameters
ID Name Meaning
alarm.
2-600 (2008-06-24)
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
None.
Possible Causes
Handling Procedure
----End
(2008-06-24) 2-601

Description
Attribute

30725 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-602 (2008-06-24)
Impact on System
None
System Actions
None.
Possible Causes
Handling Procedure
----End

Description
Attribute
30726 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-603
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
None.
Possible Causes
Handling Procedure
----End

Description
2-604 (2008-06-24)
Attribute

30727 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
None.
(2008-06-24) 2-605
Possible Causes
Handling Procedure
----End
2.381 30728 Database Configuration and Hardware

Mismatch
Description
This alarm indicates one of the following scenarios: 1.Micro platforms: 1a.The
Horizoncompact2 hardware is present but the database configuration is for the Horizonmicro2/
MCellarena/MCellcity/MCellmicro hardware. 1b.The Horizonmicro2 hardware is present but
the database configuration is for the Horizoncompact2/MCellarenamacro/MCellcity/
MCellmicro hardware. 1c.The MCellarena/MCellarenamacro hardware is present but the
database configuration is for the Horizonmicro2/Horizoncompact2 hardware. 2.Macro
platforms: A macro site with extension cabinet of type MCell6/HorizonMacro/HorizonMacro2/
Horizon2mini/Horizon2micro has been inconsistently equipped in the database such that a
mismatch of cabinet types has been detected.
Attribute

30728 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
2-606 (2008-06-24)
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
When considering scenario 1: the system continues to function and report valid External Power
Booster Failure alarms, if detected. When considering scenario 2: The system will continue to
function, specific restrictions applied to the management of CTU2 devices (Transmit power
levels etc) can be applied incorrectly, due to the mismatch. This could result in reduced
performance or devices being out of service.The alarm is cleared when system detects that the
database configuration matches the hardware.
Possible Causes
The database configuration does not match the hardware present.
Handling Procedure
Update the database to match the Hardware present, or replace Hardware to match the Database
value. Note that IAS and EAS alarms may be incorrectly reported/cleared while this alarm is
active.
----End
(2008-06-24) 2-607
2.382 30729 Duplexer Voltage Error

Description
One of the duplexer blocks has a Duplexer Voltage Detect alarm. This alarm indicates that the
VSWR circuitry in the duplexer has no power.The additional data indicates which duplexer
block detected the failure.
Attribute

30729 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-608 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Input voltage may be out of range; environmental temperature may be too high; input voltage
may been lost; output supply cable may be faulty; a power supply fan may have failed; an
overvoltage condition may have been detected on the PSU.
Handling Procedure
Send a service technician to reset the circuit breaker or replace the duplexer.
----End
2.383 30730 BTS Cabinet Over Temperature

Description
This alarm indicates that a Base Transceiver Station (BTS) cabinet ambient temperature has
overheated to a level of 70 degrees C which is beyond the (safe) temperature range allowed for
proper operation of BTS equipment. This internal cabinet condition has been detected by either
the BTS Over Temperature Thermostat or by the Power Supply Unit (PSU) which has
overheated.
Attribute
30730 Warning Fault
Parameters
ID Name Meaning
alarm.
(2008-06-24) 2-609
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
This alarm may have been caused by one or more of the following possible reasons: the air
passage ways (inlet, outlet and air ways) may have been obstructed, the BTS Over Temperature
thermostat may have been faulty, the PSU may have been malfunctioning (this does not apply
to Thor cabinets), or the BTS Heat Management System Over Temperature may have been faulty
(this applies to outdoor cabinets only).Note that if a BTS cabinet over temperature condition has
occurred and the cabinet temperature has risen to 80 degrees C, the power to the BTS cabinet
will be shut off (On-site, a red LED will light on the ASPM or the NSPM to indicate the fault
condition) and the system will generate the "10. RSL: Link Disconnected" alarm because an
RSL link will be disconnected when the power is shut off.
Handling Procedure
2-610 (2008-06-24)
logs to determine the cause of this alarm. 2. Send a field representative to the site to determine
if the air passage ways are obstructed or if the PSU, thermostat, or BTS Heat Management System
(outdoor cabinet) equipment is faulty.
----End

Description
This alarm indicates that there has been a loss of mains power or the PSU has failed causing a
loss of input power from the backup battery. This alarm is generated when the battery backup
power (voltage) is nearing the point where it will start initiating a disconnection of the BTS
cabinets. This alarm applies to outdoor cabinets only. This +27V battery backup input power
supply has helped to sustain power to the BSU/RXU for the purpose of maintaining system
operation until power can be restored.
Attribute

30731 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-611
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
The input feed (voltage) may have been lost causing the output failure or the PSU may have
been malfunctioning.
Handling Procedure
The BSS will clear the alarm automatically after the fault condition has been resolved. If the
alarm has not ceased, perform the following procedures: 1. Review the alarm report/event logs
to determine the cause of this alarm. 2. Investigate the mains power failure. 3. Send a field
representative to the site to determine if the PSU and/or the input power source (equipment/
cables) are faulty.
----End
2.385 30732 Air Conditioning Unit Failure

Description
A BTS or ancillary cabinet Air Conditioning Unit has failed.This alarm is generated when an
air conditioning (air) inlet or outlet is blocked causing the equipment to fail. This alarm applies
to outdoor cabinets only.
Attribute
2-612 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
The air inlet or outlet vent to the air conditioning unit may have been blocked causing the unit
to fail or the air conditioning unit may have been faulty.
(2008-06-24) 2-613
Handling Procedure
locate the failed unit and determine if the inlet or outlet vents are blocked.
----End
2.386 30733 Heat Management System Unit Failure

Description
This alarm indicates that Ancillary Heat Management Unit at a BTS has failed. This alarm is
generated when a heat management (air) inlet or outlet is blocked causing the equipment to fail.
The alarm may be received in conjunction with alarm 82. IAS: BTS Cabinet Over Temperature.
Attribute

30733 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-614 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
The following are possible reasons for this alarm: the air inlet or outlet vent to/from the heat
management unit may have been blocked causing the unit to fail or the heat management unit
may have been faulty.
Handling Procedure
to determine the cause of this alarm. 2. Send a field representative to the site to locate the failed
unit and determine if the inlet or outlet vents are blocked.
----End
2.387 30735 Ancillary Cabinet Over Temperature

Description
This alarm indicates that an "Ancillary" cabinet ambient temperature has overheated to a level
which is beyond the (safe) temperature range allowed for proper operation of equipment. This
internal cabinet condition has been detected by either the "Ancillary Over Temperature
Thermostat" or by the Power Supply Unit (PSU) which has overheated.
(2008-06-24) 2-615
Attribute

30735 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
2-616 (2008-06-24)
Possible Causes
The air passage ways (inlet, outlet and air ways) unit may have been obstructed,the "Ancillary
Over Temperature Thermostat" may have been faulty, the PSU may have been malfunctioning,
or the "Ancillary Heat Management System Over Temperature" may have been faulty (this
applies to outdoor cabinets only).
Handling Procedure
If the alarm has not ceased, perform the following procedure:1. Review the alarm report/event
logs to determine the cause(s) of this alarm.2. Send a field representative to the site to locate the
failed unit and determine if the inlet/outlet vents or air passage ways are blocked. The PSU
should be checked as well.
----End

Description
This alarm indicates that the Voltage Standing Wave Radio (VSWR) unit has failed in sector 1.
This failure may affect the signal quality transmitted in this sector. If the ratio of forward-to-
reflected power is not maintained and there is an excessive reflected signal, the quality of the
signal transmitted will be compromised.
Attribute

30736 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-617
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
l The VSWR unit may have been faulty, the antenna may have been faulty, the
l Alarms (or the EAS or PIX) board may have been improperly connected to the
l VSWR Bridge, the Alarms board (or connectors on the board) may be faulty
l (See Notes), or the antenna may have been improperly connected to the
l VSWR Bridge.
Handling Procedure
determine if the air passage ways are obstructed or if the PSU, thermostat or "Ancillary Heat
Management System" (outdoor cabinet) equipment is faulty.
----End
2-618 (2008-06-24)

Description
Attribute

30737 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-619
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
The VSWR unit may have been faulty, the antenna may have been faulty, the Alarms (or the
EAS or PIX) board may have been improperly connected to the VSWR Bridge, the Alarms board
(or connectors on the board) may be faulty (See Notes), or the antenna may have been improperly
connected to the VSWR Bridge.
Handling Procedure
----End

Description
Attribute
30738 Warning Fault
2-620 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
l The following include possible reasons for this error:the VSWR unit may have been faulty,
the antenna may have been faulty, the Alarms (or the EAS or PIX) board may have been
improperly connected to the
l VSWR Bridge, the Alarms board (or connectors on the board) may be faulty (See Notes)
or the antenna may have been improperly connected to the VSWR Bridge.
(2008-06-24) 2-621
Handling Procedure
----End
2.391 30739 Voltage Standing Wave Ratio Performance Low

Description
This alarm indicates that the Voltage Standing Wave Radio (VSWR) unit transmitted signal
quality has degraded in a sector (1-3). This alarm is generated when a problem has been detected
with a connection to the VSWR unit.The ratio of forward-to-reflected power has been
compromised. As a result,there is an excessive reflected signal affecting the quality of the signal
being transmitted.
Attribute
30739 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-622 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
l The VSWR unit may be faulty; the antenna may be faulty due to weather conditions,
external damage,
l errors in the installation, etc; the alarms (or the EAS or PIX) board (or connectors on the
board may be faulty (see Note 1. below); or the antenna may have been improperly
connected to the VSWR Bridge.
Handling Procedure
If the alarm occurs, perform the following procedure: send a field representative to the site to
determine whether the equipment is fault. The field representative must be prepared to check,
repair or replace the following equipment,if necessary: the VSWR unit (1-3), the connection
between the antenna and the VSWR Bridge, the connection between the VSWR Bridge and the
Alarms board (or the
EAS or PIX) board, and the antenna.
----End
2.392 30740 Smoke Alarm

Description
This alarm indicates that smoke has been detected in a BTS or an "Ancillary" cabinet indicating
that the equipment may have overheated to a level which may damage equipment. This internal
cabinet condition may also have been detected by either the BTS (or Ancillary) "Over
Temperature Thermostat" or by a PSU which has overheated. This alarm may be received in
conjunction with other IAS alarms which will aid in fault diagnosis. These alarms include: "80.
IAS: Power Supply Unit - Input Failure.", "81. IAS: Power Supply Unit - Output Failure.", "84.
(2008-06-24) 2-623
IAS: Air Conditioning Unit Failure.", "85. IAS: Heat Management System Unit Failure." or "86.
IAS: Cabinet Fan Failure.".
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
2-624 (2008-06-24)
System Actions
Possible Causes
l The cause for the smoke alarm is fire which may have been caused by one of the following:
the air passage ways (inlet, outlet and air ways) may have been obstructed causing the
equipment to overhead, the fan may have been malfunctioning causing the equipment to
overhead, the PSU may have been
l malfunctioning/overheating, the air conditioning unit may have been faulty causing the
equipment to overheat, or the "Ancillary Heat Management System Over Temperature"
may have been faulty causing the equipment to overheat (applies to outdoor cabinets only.).
Handling Procedure
If the alarm has occurred, send a field representative to the site to determine whether the hardware
if faulty. The representative must check all connections and be prepared to repair or replace the
following hardware if necessary:the VSWF unit (1-3), the antenna, the Alarms board or EAS
(or PIX) board, the link between the antenna and the VSWR Bridge, and/or the link between the
VSWR Bridge and the Alarms board (or EAS or PIX board).
----End
2.393 30741 Door Open

Description
This alarm indicates that a cabinet door is open at a site which should not be. If one of the
following doors is open,this alarm will be generated: BTS - door or hood, Ancillary cabinet -
door or hood, or side cabinet door.
Attribute
30741 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
(2008-06-24) 2-625
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Trigger all MSI boards to write the E1 MMS monitor historical data and MSI local board test
result into nv-ram, and then report this alarm.
Possible Causes
The cabinet door may not have been secured properly or the door latches may have been
defective.
Handling Procedure
If the alarm has not ceased, perform the following procedure: 1. Review the alarm/event logs to
determine the cause of this alarm if possible. 2. Send a field representative to the site to close
the door(s). While there, the representative should check the cabinet door latches. Any defective
latches must be replaced.
----End
2-626 (2008-06-24)
2.394 30742 No Connection to Alarms Board - connection

broken
Description
This alarm indicates that the connection between the radio (Transceiver Control Unit(s) TCUSs)
and the Alarms board has been interrupted. This alarm is generated when the BSS software has
detected that none of the TCUs in a cabinet are connected to the Alarms board.
Attribute
30742 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-627
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
The Alarms board link to a DRI (TCU) may not have been established, the Alarms board fibre
link to a DRI (TCU) may be faulty,the Alarms board link may be connect to an OOS DRI
(TCU),the Alarms board link may be connected to an E-U DRI (TCU) that does not have an
RTF equipped, or the Alarms board may be faulty.
Handling Procedure
None
----End
2.395 30743 Low Noise Amplifier Fuse Failure

Description
This alarm indicates that the low noise amplifier fuse in an M-Cell cabinet has failed. The fuses
are located in different places within each type of M-Cell cabinet: M-Cell2 and M-Cell6. In the
M-Cell2 cabinet, the fuse is located near a panel of switches in the lower right side of the cabinet.
There are three fuses: the low noise amplifier fuse is the bottom fuse and is unlabeled. In the M-
Cell6 cabinet, the fuse is located on the panel between the two card cages that are situated below
the radios in the bottom half of the cabinet.
Attribute
30743 Warning Fault
Parameters
ID Name Meaning
alarm.
2-628 (2008-06-24)
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
The following are possible reasons for this error: the amplifier fuse may have been faulty, the
cabling connecting the fuse panel and IADU board may be faulty, the IADU board (above the
radios) may be faulty, and/or the Alarms board may be faulty.
Handling Procedure
(2008-06-24) 2-629
If this alarm occurs, review the alarm report/event logs to check for other alarms at the same
site. Then send a field representative to the site to check and replace the fuse, the Alarms board,
the IADU board, and/or the cabling if necessary.
----End
2.396 30744 No Redundant Connection to Alarms Board -

connection broken
Description
This alarm indicates that BSS software has detected that the redundant (back up) radio
connection to the Alarms board is not functioning.The redundant connection may not be
functioning due to either a faulty cable or an on-site disconnection.
Attribute
30744 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-630 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
l The redundant cable between the radio and Alarms board
l may have been disconnected or may be faulty.
Handling Procedure
If this alarm occurs:1. Review the alarm/event logs to check for other alarms at the same
site. 2. Send a field representative to the site to check the cabling from the Alarms board to the
DRI. The representative should be prepared to reconnect or replace the cabling to the Alarms
board if necessary.
----End
2.397 30745 No Connection to Alarm Board - Radio OOS

Description
This alarm indicates that BSS software has detected that all radio (Transceiver Control Unit
(TCU) connections to the Alarms board are OOS. This alarm is generated when the last (final)
radio connection goes OOS. In this case,there is no connection because the radio(s) are faulty.
Attribute
30745 Warning Fault
(2008-06-24) 2-631
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
The last (or only) radio DRI (TCU) is faulty.
Handling Procedure
2-632 (2008-06-24)
If this alarm occurs, review the alarm/report event logs to check for other alarms at the same
site. Then send a field representative to the site to check the radios (DRI (TCUs)) connected to
the Alarms board. The representative should be prepared to replace either or both DRI (TCUs)
if necessary.
----End
2.398 30746 No Redundant Connection to Alarms Board -

Radio OOS
Description
This alarm indicates that BSS software has detected that the redundant radio (Transceiver
Control Unit (TCU)) connections to the Alarms board are OOS. Note that two radios (DRI
(TCUs) are connected to the Alarms board.
Attribute
30746 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-633
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
One radio DRI (TCU) is faulty.
Handling Procedure
site. Then send a field representative to the site to check both radios (DRI (TCUs)) connected
to the Alarms board and thus identify the faulty DRI (TCU). The representative should attempt
to restore the faulty (redundant) DRI (TCU) to service and be prepared to replace it if necessary.
----End
2.399 30747 No connection to alarm board - Alarm Board

Removed
Description
This alarm indicates that BSS software has detected that the Alarms board has been physically
removed or has not been properly connected.
Attribute

30747 Warning Fault
2-634 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
The Alarms board may not have been properly connected or the board may have been removed.
Handling Procedure
(2008-06-24) 2-635
site. Then send a field representative to the site to determine whether the Alarms board has been
physically removed or is not properly connected. The representative should check the
connections, attempt to reconnect the Alarms board and be prepared to replace it if necessary.
----End
2.400 30748 Rectifier Failure

Description
This alarm indicates that BSS software has detected that the rectifier output from a backup battery
box has failed. This alarm is generated when the rectifier has failed or the cable from the battery
box (rectifier)-to-Thor alarm connector is faulty; or when the cable is not properly connected.
Attribute

30748 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-636 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
The rectifier may be damaged. The cable from rectifiers in the battery box to the external Thor
alarm connector is loose or not properly connected, or is faulty.
Handling Procedure
Check the output LEDs on the rectifier front panel, and then replace the rectifiers that are
defective from the power cage. If no rectifiers are defective, check the cable from the rectifiers
in the battery box to the external Thor alarm connector. It may be loose, not properly connected,
or faulty.If so, connect it properly or replace it if it is faulty.
----End
2.401 30749 Battery Box Temperature High

Description
This alarm indicates that BSS software has detected that the temperature in the backup battery
box has exceeded the established limits for safe operation of the equipment.
Attribute
30749 Warning Fault
(2008-06-24) 2-637
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
l The following are the possible reasons for this error:
l * The air passage way (inlet, outlet, and airways) may have been obstructed causing the
equipment to overheat.
l * The thermostat may be faulty.
2-638 (2008-06-24)
l * The environmental temperature may be too high.

l * The Heat Management System (HMS) in an outdoor cabinet may be faulty.
l * The cable from battery box to cabinet may not be properly connected.
l * The cable (or cable connectors) from battery box to cabinet may be faulty.
Handling Procedure
Check that all air inlet, outlet and airways are clear of obstructions.
----End
2.402 30750 Alarm Board Failed

Description
This alarm indicates that BSS software has detected that the Alarms board in a Thor cabinet has
failed due to faulty board circuitry or board damaged due to conditions in the field.
Attribute
30750 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-639
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
GPS power failure. Site alarms circuitry failure. Bad Alarms Board.
Handling Procedure
Replace the alarms board.
----End
2.403 30751 Auxiliary Alarm 1

Description
Spare external alarm.
Attribute

30751 Warning Fault
2-640 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Spare - To be defined.
Possible Causes
Handling Procedure
(2008-06-24) 2-641
----End
2.404 30752 Urgent Critical Alarm

Description
Urgent Critical Alarm.
Attribute

30752 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-642 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
Attribute
30753 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
(2008-06-24) 2-643
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End
2-644 (2008-06-24)

Description
Attribute

30754 Warning Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-645
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
This alarm applies to HorizonMacro and HorizonMacro2 cabinets only. The BSS will clear the
alarm automatically through the Fault Management Initiated Clear (FMIC) after the fault
condition has been resolved.
Attribute
30755 Major Fault
Parameters
ID Name Meaning
alarm.
2-646 (2008-06-24)
ID Name Meaning
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
l * The A.C. circuit breaker may be in the "OFF" position due to a power surge.
l * The cable from the rectifier to the external alarm connector may not be properly
connected.
l * The cable (or connector on the cable) from the rectifier to the external alarm connector
may be faulty.
l * A rectifier within the battery box may be faulty.
(2008-06-24) 2-647
Handling Procedure
Check to see if the Mains A.C. input supply circuit breaker is OFF. Isolate Mains supply to the
cabinet and check the integrity of the A.C. wiring. If faulty, remove rectifiers from the power
cage and check A.C. wiring again. A pass may indicate that one or more rectifiers are faulty.
----End

Description
This alarm applies to HorizonMacro and HorizonMacro2 cabinets only. The BSS will clear the
alarm automatically through the Fault Management Initiated Clear (FMIC) after the fault
condition has been resolved.
Attribute
30756 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-648 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
connected.
may be faulty.
Handling Procedure
----End

Description
box (rectifier) alarm connector is faulty; or when the cable is not properly connected.
(2008-06-24) 2-649
Attribute

30757 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
2-650 (2008-06-24)
Possible Causes
The rectifier may be damaged. The cable from rectifiers in the battery box to the external alarm
connector is loose or not properly connected or is faulty.
Handling Procedure
in the battery box to the external alarm connector. It may be loose, not properly connected, or
faulty. If so, connect it properly or replace it if it is faulty.
----End

Description
box (rectifier) alarm connector is faulty; or when the cable is not properly connected.
Attribute

30758 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-651
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
The rectifier may be damaged. The cable from rectifiers in the battery box to the external alarm
connector is loose or not properly connected or is faulty.
Handling Procedure
in the battery box to the external alarm connector. It may be loose, not properly connected, or
faulty. If so, connect it properly or replace it if it is faulty.
----End

Description
A failure has been detected with Power Supply Unit (PSU) 0,one of: (1) PSU input failure; (2)
PSU output failure; (3) PSU overtemperature; (4) PSU fan failure; (5) PSU overvoltage. The
additional data indicates which failure has occurred.
2-652 (2008-06-24)
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
(2008-06-24) 2-653
Possible Causes
Handling Procedure
If the alarm remains active, perform the following procedure:

(1) Review the alarm report/event logs to determine the cause of this alarm.
(2) Determine whether the PSU failure is related to other more serious fault conditions. Check
the Alarm window for other failures at the site with the PSU power failure. If other failures
exist for the site, prioritise the faults and consult the "Maintenance Information: Alarm
Handling at the OMC" guide for the alarm descriptions and fault resolution procedures.
(3) Send a field representative to the site to determine if the input power source (equipment
and/or cables) are faulty, or the PSU equipment is faulty. Any faulty equipment should be
replaced.
----End

Description
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
2-654 (2008-06-24)
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure

(2008-06-24) 2-655
replaced.
----End

Description
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
2-656 (2008-06-24)
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
Handling Procedure

replaced.
----End

Description
(2008-06-24) 2-657
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
2-658 (2008-06-24)
Possible Causes
Handling Procedure

replaced.
----End
2.415 30835 Power Supply Unit - Input Failure

Description
This alarm indicates that there has been a loss of mains power. Because of the power loss, the
cabinet has switched to the emergency battery backup input power supply. This +27V battery
backup input power supply will help sustain power to the Base Station Unit shelf (BSU)/Remote
Transcoder Unit (RXU).
Attribute

30835 Major Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
(2008-06-24) 2-659
ID Name Meaning
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
For an indoor system, the input voltage may have been out of specification causing the failure.
In this case, the power supply units would operate for a small duration until the input voltage
was completely out of range. For an outdoor system, the ac mains may have been faulty.
Handling Procedure
logs to determine the cause of this alarm. 2. Send a field representative to the site to determine
if the air passage ways are obstructed or if the PSU, thermostat, or BTS Heat Management System
(outdoor cabinet) equipment is faulty.
----End
2-660 (2008-06-24)
2.416 30836 Power Supply Unit - Output Failure

Description
This alarm indicates that there has been a loss of output power due to the failure of the Power
Supply Unit (PSU). It is also possible that the output power failure is due to the input feed
(voltage) which may have been interrupted (or discontinued) due to faulty equipment.
Attribute

30836 Minor Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
(2008-06-24) 2-661
ID Name Meaning
Impact on System
None
System Actions
Possible Causes
The input feed (voltage) may have been lost causing the output failure or the output power supply
cable may have been faulty.
Handling Procedure
logs to determine the cause of this alarm. 2. Determine whether the PSU failure is related to
other more serious fault conditions. Check the Alarm window for other failures at the site with
the PSU power failure. If other failures exist for the site, prioritize the faults and consult the
Maintenance Information: Alarm Handling at the OMC Guide for the Alarm descriptions and
fault resolution procedures. 3. Send a field representative to the site to determine if the input
power source (equipment and/or cables) are faulty, or the PSU equipment is faulty. Any faulty
equipment should be replaced.
----End

Description
This alarm indicates that there has been a loss of mains power or the PSU has failed causing a
loss of input power from the backup battery. This alarm is generated when the battery backup
power (voltage) is nearing the point where it will start initiating a disconnection of the BTS
cabinets. This alarm applies to outdoor cabinets only. This +27V battery backup input power
supply has helped to sustain power to the BSU/RXU for the purpose of maintaining system
operation until power can be restored.
Attribute

30837 Major Fault
2-662 (2008-06-24)
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
The input feed (voltage) may have been lost causing the output failure or the PSU may have
been malfunctioning.
(2008-06-24) 2-663
Handling Procedure
to determine the cause of this alarm. 2. Investigate the mains power failure. 3. Send a field
representative to the site to determine if the PSU and/or the input power source (equipment/
cables) are faulty.
----End
2.418 30838 Power Supply Temperature High

Description
This alarm indicates that BSS software has detected that one or more Power Supply Unit (PSUs)
in Thor cabinet has exceeded the established (safe) temperature range.
Attribute

30838 Minor Fault
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-664 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
The PSU may be faulty. The environmental temperature may be too high. The Heat Management
System (HMS) in an outdoor cabinet may be faulty.
Handling Procedure
Replace Power Supply Unit.
----End
2.419 30839 Mains A.C. Supply Failure

Description
This alarm indicates that BSS software has detected that Mains A.C. input power to the backup
battery box is no longer available.As a result, A.C. input power is not being sent through to the
BTS.
Attribute

30839 Minor Fault
(2008-06-24) 2-665
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
connected.
2-666 (2008-06-24)
may be faulty.
Handling Procedure
----End

Description
The alarm will be generated when an integrated multiplexer on the master BTP or its
corresponding remote multiplexer is disconnected. In both cases the alarm will only be generated
if at least one in-service DRI is connected to the multiplexer(s).
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-667
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
All DRIs connected to FMUX will be taken out of service.The DRIs are no longer able to
communicate with an MCU/BTP.
Possible Causes
l ) Fibre cable connecting the two multiplexers is damaged or broken.
l ) Bad multiplexer at either end of the fibre.
Handling Procedure
A field representative must investigate a potential hardware fault with the multiplexer or its link.
The associated DRIs must be INS'ed once before replacing the faulty multiplexer or the link.
----End

Description
The alarm will be generated when an integrated multiplexer on the standby BTP or its
2-668 (2008-06-24)
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
(2008-06-24) 2-669
Possible Causes
Handling Procedure
----End

Description
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-670 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
(2008-06-24) 2-671
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
2-672 (2008-06-24)
Possible Causes
Handling Procedure
----End

Description
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-673
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
2-674 (2008-06-24)
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
(2008-06-24) 2-675
Possible Causes
Handling Procedure
----End

Description
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-676 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
All DRIs connected to XMUX will be taken out of service.The DRIs are no longer able to
Possible Causes
Handling Procedure
----End

Description
(2008-06-24) 2-677
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
2-678 (2008-06-24)
Possible Causes
Handling Procedure
----End

Description
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
(2008-06-24) 2-679
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
2-680 (2008-06-24)
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
(2008-06-24) 2-681
Possible Causes
Handling Procedure
----End

Description
Attribute

Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
2-682 (2008-06-24)
ID Name Meaning
or Horizon2Micro.
Impact on System
None
System Actions
Possible Causes
Handling Procedure
----End

Description
(2008-06-24) 2-683
Attribute
Parameters
ID Name Meaning
alarm.
reports an alarm.
indicates invalid.
or Horizon2Micro.
Impact on System
None
System Actions
2-684 (2008-06-24)
Possible Causes
Handling Procedure
----End
(2008-06-24) 2-685
2-686 (2008-06-24)
BSS Alarm Reference 3 Changes in BSS Alarm Reference
3 Changes in BSS Alarm Reference
This section describes the changes in the BSS Alarm Reference.
01 (2008-06-24)
(2008-06-24) 3-1
3 Changes in BSS Alarm Reference BSS Alarm Reference
3-2 (2008-06-24)

Huawei Alarms

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Huawei Alarms

Uploaded by

Copyright:

Available Formats

Horizon RAN controller

BSS Alarm Reference

1 BSC Alarm Reference................................................................................................................1-1

1.33 154 Resource Usage Threshold Exceeded for Over 60 Times....................................................................1-79

1.75 422 BTS doesn't support abis optimize.....................................................................................................1-128

1.117 20087 High BER over the E1 Link.........................................................................................................1-192

1.201 20421 Abnormal Temperature................................................................................................................1-317

1.243 20980 Ethernet Port Band Width Change...............................................................................................1-366

1.285 21502 MTP3 Layer 3 Congestion...........................................................................................................1-411

1.327 22021 Extern Figure Sensor17 Alarm.....................................................................................................1-466

1.369 65256 BTS Custom Environment Alarm23............................................................................................1-517

1.411 65298 BTS Custom Environment Alarm65............................................................................................1-575

1.453 65340 BSC Custom Environment Alarm7..............................................................................................1-632

1.495 65382 BSC Custom Environment Alarm49............................................................................................1-674

2 BTS Alarm Reference................................................................................................................2-1

2.40 30038 Port 1 Synchronization Loss Hourly Threshold Exceeded.............................................................. 2-94

2.82 30080 Port 3 Bit Error Daily Threshold Exceeded...................................................................................2-156

2.124 30122 Site No Clock References Available............................................................................................2-219

2.166 30287 Hard Reset....................................................................................................................................2-284

2.208 30329 Transmitter Failure - Output Power.............................................................................................2-349

2.250 30371 Control Processor to Equalizer Communication Failure..............................................................2-414

2.292 30414 Slow Flash Failure........................................................................................................................2-476

2.334 30563 Port 0 Frame Slip OOS Threshold Exceeded...............................................................................2-538

2.376 30723 External Alarm 12........................................................................................................................2-599

2.418 30838 Power Supply Temperature High.................................................................................................2-664

3 Changes in BSS Alarm Reference...........................................................................................3-1

1 BSC Alarm Reference

About This Chapter

1.1 BSC Alarm List

1.21 142 Resource Overused

1.54 343 NSVL Dynamic Configuration Process Failure

1.87 20003 Board Fault - Faulty Inner Clock

1.120 20091 E1 Excessive Peer End Alarms Per Hour

1.153 20232 Loss of Administration Unit Pointer (AULOP)

1.186 20353 TDM Interface Unit Failure Alarm

1.252 21019 Failed Loading of Board Software

1.285 21502 MTP3 Layer 3 Congestion

1.318 22012 Extern Figure Sensor8 Alarm

1.351 65238 BTS Custom Environment Alarm5

1.384 65271 BTS Custom Environment Alarm38

1.417 65304 BTS Custom Environment Alarm71

1.450 65337 BSC Custom Environment Alarm4

1.483 65370 BSC Custom Environment Alarm37

1.1 BSC Alarm List

ALM-101 MSC Overload Fault Minor Running

ALM-102 Disrupted Connection with the Fault Major Communica

ALM-103 All SS7 Links Faulty Fault Critical Communica

ALM-124 No A Interface Circuit Configured Event Minor Software

ALM-126 No Circuit Configured in the MSC Event Event Software

ALM-128 No Circuit Configured in the PCU Event Minor Software

ALM-129 MSC Resetting Event Minor Software

ALM-130 BSC Resetting Failure Event Minor Software

ALM-131 BSC Unable to Reset a Circuit Event Minor Software

ALM-132 BSC Unable to Block a Circuit Event Minor Software

ALM-133 BSC Unable to Unblock a Circuit Event Minor Software

ALM-134 BSC Unable to Block a Packet Event Minor Software

ALM-135 BSC Unable to Unblock a Packet Event Minor Software

ALM-136 BSC Unable to Reset a Packet Event Minor Software

ALM-137 BSC Unable to Unblock Group Event Minor Software

ALM-138 BSC Unable to Block Group Event Minor Software

ALM-139 No Group Circuits Configured on Event Minor Software

Alarm ID Alarm name Alarm Alarm type

ALM-140 BSC Unable to Read License File Fault Critical Software

ALM-141 BSC Unable to Obtain License File Event Critical Software