ZXG10 BSS (V6.20) Base Station Subsystem Alarm Handling Manual

ZXG10 BSS
Base Station Subsystem

Alarm Handling Manual
Version 6.20
ZTE CORPORATION
ZTE Plaza, Keji Road South,
Hi-Tech Industrial Park,
Nanshan District, Shenzhen,
P. R. China
518057
Tel: (86) 755 26771900 800-9830-9830
Fax: (86) 755 26772236
URL: http://support.zte.com.cn
E-mail: doc@zte.com.cn
LEGAL INFORMATION
Copyright © 2006 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Date Revision No. Serial No. Reason for Issue

Aug. 29, 2008 R1.0 sjzl20083213 First edition
ZTE CORPORATION
Values Your Comments & Suggestions!
Your opinion is of great value and will help us improve the quality of our product
documentation and offer better services to our customers.
Please fax to: (86) 755-26772236; or mail to Technical Delivery Department, ZTE
University, Dameisha, Yantian District, Shenzhen, Guangdong, P.R. China 518083.
Thank you for your cooperation!
Document
ZXG10 BSS (V6.20) Base Station Subsystem Alarm Handling Manual
Name
Document Revision
Product Version V6.20 R1.0
Number
Equipment
Serial No. sjzl20083213
Installation Date
Presentation:
(Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization,
Appearance)
Good Fair Average Poor Bad N/A
Your evaluation Accessibility:

of this
(Contents, Index, Headings, Numbering, Glossary)
documentation
Intelligibility:
(Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content)
Please check the suggestions which you feel can improve this documentation:
Improve the overview/introduction Make it more concise/brief
Improve the Contents Add more step-by-step procedures/tutorials
Improve the organization Add more troubleshooting information
Include more figures Make it less technical
Your Add more examples Add more/better quick reference aids
suggestions for Add more detail Improve the index
improvement of
this Other suggestions
documentation __________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
# Please feel free to write any comments on an attached sheet.
If you wish to be contacted regarding your comments, please complete the following:
Name Company
Postcode Address
Telephone E-mail
This page is intentionally blank.
Contents
About This Manual ............................................................ i

Purpose ................................................................................ i
Intended Audience ................................................................. i
Prerequisite Skill and Knowledge .............................................. i
What Is in This Manual ........................................................... i
Related Documentation.......................................................... ii
Conventions ........................................................................ iii
How to Get in Touch............................................................. iv
Declaration of RoHS Compliance..................................... v
Chapter 1.......................................................................... 1
Alarm Message Summary................................................ 1

Alarm Code Definition ......................................................1
Alarm Severity Level ............................................................. 1
Alarm Handling ...............................................................2
Alarm Classification ............................................................... 3
Chapter 2.......................................................................... 5
Alarm Messages ............................................................... 5

Equipment Alarms ...........................................................5
Loss of Optical Transceiver Module Signal ................................. 5
Ethernet Controller's Physical Link Off ...................................... 6
Trunk Link Is Used for CSU Loopback Test ................................ 6
Cell Delineation Not Synchronized ........................................... 7
Loss of Cell Delineation .......................................................... 7
8K input clock lose ................................................................ 7
16M Input Clock Lose ............................................................ 8
PP2S Clock Input Lose ........................................................... 8
32M Clock lost in TSNB .......................................................... 8
Clock Phase Does not Match When Inputting 8k,16M Clock to
Backboard ........................................................................... 9
Clock Chip of This Board Is in Preheat Status............................ 9
Loss of Clock When Input to Board.......................................... 9
SDH/SONET fault ................................................................. 9
SDH/SONET:Loss of Frame ...................................................10
SDH/SONET: Regenerator Section Trace Mismatch/Section Trace
Mismatch ...........................................................................10
SDH/SONET:MS-AIS,Line Alarm Indication Signal ....................11
SDH/SONET:Multiplexing Section Far-end Reception Failure/Line
Far-end Reception Failure .....................................................11
SDH/SONET:Signal Failure....................................................12
SDH/SONET:Signal Deterioration ...........................................12
SDH/SONET:Loss of AU-4 Pointer/Loss of Channel Pointer.........13
SDH/SONET:AU-AIS/Channel-AIS..........................................13
SDH/SONET:HP-Trace Mismatch/ Patch Trace Mismatch............13
SDH/SONET:HP Unassembled/Path Unassembled.....................14
DH/SONET:HP Label Mismatch/Path Label Mismatch .................14
SDH/SONET:HP Remote Reception Failure ..............................14
SDH/SONET:LOM ................................................................15
SDH/SONET: Loss of TU Pointer/Loss of Virtual Tributary Pointer 15
SDH/SONET:Tributary Unit Alarm Indication Signal/Virtual
Tributary Alarm Indication Signal...........................................15
SDH/SONET:LP Remote Defect Indication/Virtual Tributary Remote
Defect Indication .................................................................16
SDH/SONET:LP-RFI/Virtual Tributary-RFI................................16
SDH/SONET:LP-Trace Mismatch/ Virtual Tributary Trace Mismatch
........................................................................................17
SDH/SONET:LP-Unloaded/Virtual Tributary Unloaded................18
SDH/SONET:LP Label Mismatch/Virtual Tributary Label Mismatch18
SDH:VC-4 Signal Failure.......................................................19
SDH:VC-4 Signal Deterioration ..............................................19
SDH/SONET:Severe B1 Error Code ........................................20
SDH/SONET:Severe BIP-2 Error Code ....................................22
SDH/SONET:MS-Remote Error Indication ................................22
SDH/SONET:HP-Remote Error Indication ................................23
SDH/SONET:HP Signal Failure ...............................................23
SDH/SONET:HP Signal Deterioration ......................................24
E3S subcar transmitter direction loss of signal .........................24
Signal of Receiving End of E3S Daughter Card is Lost ...............25
OFF Alarm ..........................................................................25
E3S Daughter Card Receives Alarm Signal Indication ............... 26
Remote Failure Indication..................................................... 26
Board CPU overloaded ......................................................... 27
Excess Temperature of CPU on Board..................................... 27
Board FLASH faults ............................................................. 28
Inter-shelf media plane links abnormal .................................. 28
Capacity of intra-shelf control plane TRUNK communication is
insufficient ......................................................................... 29
Incorrect Connection of GE Optical Transceiver Module with Board
Slots on Peer-end ............................................................... 29
Internal Port of Board Is Down.............................................. 29
Board Doesn't Exist/ CPU is Long in Reset Status..................... 30
Input Clock Abnormal .......................................................... 31
A (CPU) Subcard Is Online, but Is not Configured in Database ... 31
A (CPU) Subcard Is not Online, but Has Been Configured by
Database ........................................................................... 31
External Port of Board Is Down ............................................. 32
Exceptional Internal Media Plane Communication..................... 33
DSP Resource Unavailable .................................................... 33
Usage Rate of Board Hard Disk above Threshold...................... 34
Hard Disk Broken................................................................ 34
TRUNK port down ............................................................... 34
Broad Not Tightly Inserted ................................................... 35
SMBUS Error ...................................................................... 35
Error in Rear Board That Mismatches With Front Board ............. 36
LVDS Signal Unlocked.......................................................... 36
High Error Rate of Optical Interface ....................................... 36
FPGA Exception .................................................................. 37
Port Link Down ................................................................... 37
Hardware Reliability Down.................................................... 37
PLL Work Mode Abnormal..................................................... 38
The Channel in a Subcard Is Down ........................................ 38
Subcard Abnormal .............................................................. 38
Phase-lock Loop Unlock ....................................................... 39
High Error Rate at E1 Bottom Layer ....................................... 39
Control Plane Ports of Backplane Joining Switching Chip Is
Exceptional ........................................................................ 39
Type A Fault on Board (GPS) Phase-lock Equipment ................. 40
Type B Fault on Board (GPS) Phase-lock Equipment ................. 40
Phase-lock Equipment of This Board (GPS) Is in Power-on Status
........................................................................................ 40
DSP Reports Exceptions After Detection..................................40
Loss of Clock When Input to Sub-card ....................................41
Error of LVDS Path Frame Detection.......................................41
Tier1 Network Link Loopback Diagnosis Failure ........................42
Physical link down between master port and slave port .............42
Media interactive GE port link down .......................................42
Board device is abnormal .....................................................43
Cx29704 Runs Abnormally....................................................43
Physical Channel for Data Transmission Blocked ......................43
2350 receive hardware error .................................................44
Fe IMA Group is in config-aborted state (because of unmatched
Frame length).....................................................................44
All High-Speed Links Between Line Card and Package Switching
Board Are out of Synchronism ...............................................45
APS Channels Mismatched ....................................................45
APS Modes Mismatched ........................................................46
Board Resets for APS Configuration Changes ...........................46
No Response to Requesting Database for Secondary Forwarding
Table Information................................................................47
No Response to Requesting the System for Secondary Forwarding
Table Port Information .........................................................47
Resource board Unable to Get Secondary Forwarding Table from
UIM...................................................................................48
Internal Connection Chip Faults of TSNB .................................48
Semi-Fixed Connection Error.................................................48
CLKG 32M output clock lost ..................................................49
CLKG 32M8K output clock lost...............................................49
CLKG 16M output clock lost ..................................................49
CLKG 16M8K output clock lost...............................................49
CLKG PP2S Output Clock Lost................................................50
PP2S clock reference lost......................................................50
16CHIP clock reference lost ..................................................50
All clock bases had lost ........................................................51
CLKG I2MB0 clock base lost ..................................................51
CLKG I2MB1 clock base lost ..................................................51
CLKG I2MHZ0 clock base lost ................................................51
CLKG I2MHZ1 clock base lost ................................................52
CLKG I8KBASE clock base lost...............................................52
CLKG I8KGPS clock base lost ................................................52
CLKG I8KUIM clock base lost.................................................52
Clock reference source lost (Level 3 alarm) .............................53
Clock reference source lost (Level 2 alarm)............................. 53
Clock reference source lost (Level 1 alarm)............................. 53
Clock Base Lost .................................................................. 54
CLKG board PLL out-of-lock .................................................. 54
Output clock lost................................................................. 54
DSP over load .................................................................... 54
80g chip abnormal .............................................................. 55
SCCP SSN is invalid............................................................. 55
Broadband link congestion ................................................... 56
Broadband link overload ...................................................... 57
MTP2 link transmission overload............................................ 57
MTP3 office inaccessible ....................................................... 58
MTP3 link unavailable .......................................................... 59
MTP3 cluster inaccessible ..................................................... 59
MTP3 link congestion ........................................................... 60
M3UA office inaccessible ...................................................... 61
SUA SSN is invalid .............................................................. 62
SUA office inaccessible......................................................... 63
M2PA Link Broken ............................................................... 63
BSC IP configuration error.................................................... 64
T-net center fault................................................................ 65
EPU and RPU Version Not Match ............................................ 65
Abnormal Status in SDH/SONET............................................ 65
SDH/SONET:Excessive Error Code ......................................... 66
ATM Communication Abnormally ........................................... 67
MCC Abnormal.................................................................... 67
MS APS Channel gets errors ................................................. 67
Dry Contact Alarm 1............................................................ 68
Dry Contact Alarm 10 .......................................................... 70
EAM Dry Contact Alarm 1 .....................................................71
CMM/CMB FLASH programming failure ...................................73
Power overvoltage/undervoltage alarm...................................73
13M input clock failure .........................................................73
Frame No. inconsistent between software and hardware ...........73
FCLK clock failure ................................................................74
SYNCLK clock failure ............................................................74
Master and slave communication link failure............................74
Standby CMM/CMB board not present.....................................75
Standby CMM/CMB board abnormal .......................................75
CMM/CMB power failure alarm...............................................75
A interface E1 Rx carrier alarm..............................................76
A interface E1 Rx frame not synchronized ...............................76
A interface E1 Tx forward sliding indication .............................77
A interface E1 Tx backward sliding indication...........................77
A interface E1 Rx forward sliding indication .............................78
A interface E1 Rx backward sliding indication...........................79
B interface E1 Rx carrier alarm..............................................79
B interface E1 Rx frame not synchronized ...............................80
B interface E1 Tx forward sliding indication .............................81
B interface E1 Tx backward sliding indication...........................81
B interface E1 Rx forward sliding indication .............................82
B interface E1 Rx backward sliding indication...........................82
C interface E1 Rx carrier alarm..............................................83
C interface E1 Rx frame not synchronized ...............................84
C interface E1 Tx forward sliding indication .............................84
C interface E1 Tx backward sliding indication...........................85
C interface E1 Rx forward sliding indication .............................86
C interface E1 Rx backward sliding indication ..........................86
D interface E1 Rx carrier alarm..............................................87
D interface E1 Rx frame not synchronized ...............................87
D interface E1 Tx forward sliding indication .............................88
D interface E1 Tx backward sliding indication .......................... 89
D interface E1 Rx forward sliding indication ............................ 89
D interface E1 Rx backward sliding indication .......................... 90
E interface E1 Rx carrier alarm.............................................. 91
E interface E1 Rx frame not synchronized ............................... 91
E interface E1 Tx forward sliding indication ............................. 92
E interface E1 Tx backward sliding indication .......................... 92
E interface E1 Rx forward sliding indication ............................. 93
E interface E1 Rx backward sliding indication .......................... 94
F interface E1 Rx carrier alarm.............................................. 94
F interface E1 Rx frame not synchronized ............................... 95
F interface E1 Tx forward sliding indication ............................. 96
F interface E1 Tx backward sliding indication........................... 96
F interface E1 Rx forward sliding indication ............................. 97
F interface E1 Rx backward sliding indication .......................... 97
G interface E1 Rx carrier alarm ............................................. 98
G interface E2 Rx frame not synchronized .............................. 99
G interface E1 Tx forward sliding indication............................. 99
G interface E1 Tx backward sliding indication ........................ 100
G interface E1 Rx forward sliding indication .......................... 101
G interface E1 Rx backward sliding indication ........................ 101
H interface E1 Rx carrier alarm ........................................... 102
H interface E3 Rx frame not synchronized............................. 102
H interface E1 Tx forward sliding indication........................... 103
H interface E1 Tx backward sliding indication ........................ 104
H interface E1 Rx forward sliding indication........................... 104
H interface E1 Rx backward sliding indication ........................ 105
Temperature alarm ........................................................... 106
Fan absent....................................................................... 106
Fan control board CPU alarm .............................................. 106
Fan control board CPU alarm .............................................. 106
Fan temperature alarm ...................................................... 107
Fan 1 alarm ..................................................................... 108
Fan 2 alarm ..................................................................... 108
Fan control board alarm ..................................................... 109
LNA alarm........................................................................ 109
Tower amplifier power alarm .............................................. 110
SWR of AEM HYCOM minor alarm ........................................ 110
SWR of AEM HYCOM major alarm ........................................ 110
AEM power alarm(BTS V2).................................................. 111
AEM type alarm(BTS V2) .................................................... 111
AEM absent(BTS V2).......................................................... 111
AEM power alarm .............................................................. 112
LNA0 alarm ...................................................................... 112
LNA1 alarm ...................................................................... 112
Tower Amplifier0 power alarm............................................. 112
Tower Amplifier1 power alarm............................................. 113
SWR of AEM HYCOM minor alarm......................................... 113
SWR of AEM HYCOM major alarm ........................................ 113
AEM type alarm ................................................................ 114
AEM Not-in-position alarm .................................................. 114
CHP DSP0 of TPU initialization failure(BTS V2) ....................... 114
CHP DSP1 of TPU initialization failure ................................... 115
Uplink of ADC chip initialization failure.................................. 116
Uplink of ADC resource can't be used ................................... 117
CIP resource can't be used ................................................. 117
Uplink failure .................................................................... 117
TPU FLASH Memory failure(BTS V2) ..................................... 118
Watchdog of TPU CHP DSP0 overflow(BTS V2)....................... 118
Watchdog of TPU CHP DSP1 overflow ................................... 118
Watchdog of FUC overflow .................................................. 120
CIP of TPU initialization failure............................................. 120
Watchdog of TPU CIP overflow ............................................ 120
Clock alarm for TPU and CMM.............................................. 121
TPU power alarm(BTS V2) .................................................. 121
TPU frame No. alarm ......................................................... 121
TPU CHP DSP0 initialization failure ....................................... 122
ADC resource unavailable ................................................... 122
CHP frame error ................................................................ 123
BURST interrupt error ........................................................ 123
TPU FLASH memory failure ................................................. 123
TPU CHP DSP0 watchdog overflow ....................................... 124
CU intialization failure ........................................................ 124
TPU power alarm............................................................... 124
TPU's FN alarm ................................................................. 125
Rx PLL1 unlock ................................................................. 125
Rx PLL2 unlock ................................................................. 125
Tx PLL1 unlock ................................................................. 126
Tx PLL2 unlock ................................................................. 126
52M referenced clock PLL unlock ......................................... 126
Tx IF PLL unlock ............................................................... 127
EEPROM resource can't be used .......................................... 127
FPGA interface failure ........................................................ 127
PA VSWR alarm(BTS V2).................................................... 127
PA overtemperature minor alarm(BTS V2) ............................ 128
PA overtemperature major alarm(BTS V2) ............................ 128
PA output power alarm ...................................................... 129
PA power overvoltage ........................................................ 129
PA power lower voltage...................................................... 129
Downlink checksum error of DLRC_AL1 ................................ 130
DUC chip initialization failure .............................................. 130
80w PA VSWR alarm.......................................................... 130
80w PA overtemperature.................................................... 130
80w PA overtemperature major alarm.................................. 131
80w PA output power alarm................................................ 131
80w PA power overvoltage ................................................. 132
80w PA power lower voltage ............................................... 132
80w PA absent ................................................................. 132
TXIF unlock...................................................................... 133
TPF unlock ....................................................................... 133
TXRF unlock ..................................................................... 133
RXRF unlock..................................................................... 133
13 MHz clock lost .............................................................. 134
60 ms clock lost................................................................ 134
8M clock of HW lost........................................................... 135
8K clock of HW lost ........................................................... 135
52 MHz clock lost .............................................................. 135
First ADC clock lost ........................................................... 136
Second ADC clock lost ....................................................... 136
PA power overvoltage alarm ............................................... 136
PA power undervoltage alarm ............................................. 137
PA VSWR alarm ................................................................ 137
PA temperature minor alarm............................................... 137
PA temperature major alarm ............................................... 138
PA forward power(3db) alarm ............................................. 138
RTU power alarm .............................................................. 138
RTU power temperature alarm ............................................ 139
RTU power output overvoltage alarm ................................... 139
RTU power input failure alarm ............................................. 139
IQ calibration parameters abnormal alarm ............................ 140
EAM heat exchanger alarm ................................................. 140
EAM TRX layer fan-4 alarm ................................................. 140
EAM AEM layer axis-flow fan alarm ...................................... 140
EAM smoke alarm.............................................................. 141
EAM waterproof alarm........................................................ 141
EAM lightning protection alarm ............................................ 141
EAM backdoor access control alarm...................................... 141
EAM frontdoor access control alarm ..................................... 142
EAM PWR monitoring unit alarm .......................................... 142
EAM heat exchanger electric heater alarm............................. 142
EAM heat exchanger control board alarm .............................. 143
EAM heat exchanger external circulation fan 2 alarm .............. 143
EAM heat exchanger external circulation fan 1 alarm .............. 143
EAM heat exchanger internal circulation fan 2 alarm ............... 144
EAM heat exchanger internal circulation fan 1 alarm ............... 144
EAM heat exchanger 485 communication alarm ..................... 144
EAM temperature alarm ..................................................... 145
EAM TRX layer mixed-flow fan 1 alarm ................................. 145
Power undervoltage alarm .................................................. 146
Inner fan 2 alarm (for M8202)............................................. 146
Inner fan 1 alarm (for M8202)............................................. 147
Outer fan 2 and fan 4 alarm (for M8202) .............................. 148
Outer fan 1 and fan 3 alarm (for M8202) .............................. 148
Rack temperature minor alarm ............................................ 148
Rack temperature major alarm............................................ 149
Layer 3 fan 1 alarm (for M8206).......................................... 149
Layer 2 fan 3 alarm (for M8206) ......................................... 151
FR device failure ............................................................... 152
FR congestion................................................................... 153
MSC overload control alarm at FUC mode ............................. 153
CPU overload control alarm at FUC mode.............................. 153
Signaling point congestion control alarm at FUC mode............ 154
MSC overload control alarm at SYS mode ............................. 154
CPU overload control alarm at SYS mode.............................. 154
Signaling point congestion control alarm at SYS mode............ 155
CCCH overload control ....................................................... 155
PCCCH overload control ..................................................... 155
NSVC failure alarm............................................................ 156
alarm of CRC verifying of power amplifier parameters error..... 156
DSP initialization failure ..................................................... 156
Tx PLL unlock ................................................................... 157
FLASH memory fault ......................................................... 157
Run abnormity of DSP ....................................................... 157
FPGA interface fault........................................................... 158
CHP frame fault ................................................................ 158
Wrong receive channel of RF .............................................. 158
Wrong parameter configuration for EEPROM.......................... 159
RF channel and HTRG board unconformity ............................ 159
OMP reboot alarm ............................................................. 159
TRX Man Block ................................................................. 159
Resource cannot be used of RF Channel ............................... 160
SYNCLK locked fail alarm ................................................... 160
Status of TX1 filter alarm ................................................... 160
FCU power undervoltage alarm ........................................... 161
FCU minor alarm............................................................... 162
Hard disk initialization failure.............................................. 162
The clock alarm about transmission of CCI board Abis-E1 ....... 162
The local working clock alarm of CCI board ........................... 163
The clock alarm about transmission of CCI board 13M ............ 163
CCI opposite board alarm ................................................... 163
IQ FPGA internal clock alarm............................................... 164
IQ FPGA light interface alarm .............................................. 164
IQ FPGA LVDS interface alarm............................................. 164
IQ FPGA internal data alarm ............................................... 164
13M,61.44M clock lost alarm............................................... 164
60ms clock lost alarm ........................................................ 165
26MHz and 52MHz lost of clock alarm................................... 165
the failure examination alarm of the 60ms uplink frame .......... 166
checking block data error alarm........................................... 166
up link LVDS SERDES lost lock alarm ................................... 166
FN error alarm .................................................................. 167
receiving channel frequent alarm ......................................... 167
transmiting channel frequent alarm...................................... 167
the lost alarm of 60ms ....................................................... 167
output power less than 6DB ................................................ 168
HYCOM major alarm .......................................................... 168
the input power is abnormal ............................................... 168
out of power alarm ............................................................ 168
the lost of signal of the light port 4 alarm ............................. 169
light port 2 error,Loss of Frame alarm .................................. 169
light port 1 error,Loss of Frame alarm .................................. 170
FR device failure ............................................................... 170
the version checking CRC error alarm................................... 170
Diversity antenna lost ........................................................ 170
Diversity antenna identical.................................................. 171
A Interface Resource Statistics Alarm ................................... 171
NSVC Resource Statistics Alarm........................................... 172
TCH Resource Statistics Alarm............................................. 172
Assignment Failure ............................................................ 172
Communication Alarms ................................................ 173
Exceptional Connection Setup ............................................. 173
Trunk Frame Loss.............................................................. 173
Trunk Signal Loss .............................................................. 174
Trunk Alarm Indication....................................................... 174
Trunk Multi-frame Loss ...................................................... 175
Far-End CRC Multi-frame Alarm Indication ............................ 175
Far End Alarm .................................................................. 175
Communication Link between Active and Standby Boards Off .. 176
Incorrect FE Routing Connection ......................................... 176
Board HW Error ................................................................ 177
Communication between environment monitoring board and OMP
board abnormal ................................................................ 178
RAWMACIP Channel Communication Exception ...................... 178
test pack check abnormal................................................... 179
MAC Address Conflict Exists in Boards of Same Shelf............. 179
IPMAC Conflict When OSS Detects Control Plane.................... 179
dualhome office block ........................................................ 180
dualhome link block .......................................................... 180
dualhome association block ................................................ 181
Recive bad packet ............................................................. 181
Faulty Frames Received by FE/GE/ATM/MP/POS/E1 Port ......... 182
Faulty Frames Received by Internal Switching Interface Faulty 183
HDLC unavailable.............................................................. 183
UID unavailable ................................................................ 184
UID unavailable ................................................................ 184
Far End IMA Group is in Startup state .................................. 185
FE is in blocked state......................................................... 185
Timing of Near-End IMA Group Failure ................................. 185
FE RXLSM is in Unusable State............................................ 186
Implementation specific TX fault declared at the NE ............... 186
Near-End Sending Link Broken............................................ 186
Near-End Sending Link Broken............................................ 187
LODS Alarm of Near-End Receiving Link ............................... 187
RDI Alarm of Near-End Receiving Link.................................. 187
Near-End Receiving Link Faults ........................................... 188
Implementation specific Rx failed declared at the NE .............. 188
Near-End Receiving Link Broken.......................................... 188
Far end TXLSM is in Unusable State ..................................... 189
Fe IMA Group's part of links are possibly arp looped back ....... 189
Remote Receiving Link ID Mismatched ................................. 189
BFD Session Interrupted .................................................... 190
Abis link broken ................................................................ 190
Control plane communication abnormal between board and its
home module ................................................................... 191
Control plane communication abnormal between MP and OMP . 192
Association link broken ...................................................... 192
STC office inaccessible ....................................................... 193
PPP_UID Link Down ........................................................... 194
PPP Link Down .................................................................. 194
HDLC unavailable .............................................................. 195
UID unavailable ................................................................ 195
Association path broken ..................................................... 196
PPP link broken ................................................................. 196
BSCIP configuration error in database .................................. 197
MGW not registered ........................................................... 198
Dual Homing Office Blocked ................................................ 198
Dual Homing Link Blocked .................................................. 199
Dual Homing Association Blocked......................................... 199
Trunk error....................................................................... 200
Trunk abnormal ................................................................ 200
The rate of error code in a matelink is high at GUIM ............... 201
FE Link Error Alarm ........................................................... 201
Link Broken Between Server and Alarmbox ........................... 201
HW link broken ................................................................. 202
Master rack communication link alarm.................................. 203
Communication link alarm between master and slave rack (left)
...................................................................................... 203
Communication link alarm between master and slave rack (right)
...................................................................................... 203
A interface E1 remote alarm ............................................... 204
B interface E1 remote alarm ............................................... 204
C interface E1 remote alarm ............................................... 205
D interface E1 remote alarm ............................................... 205
E interface E1 remote alarm................................................ 206
F interface E1 remote alarm................................................ 206
G interface E1 remote alarm ............................................... 207
H interface E1 remote alarm ............................................... 207
LAPD communication link between FUC and BSC break ........... 208
Communication link between CMM and FUC break(BTS V2) ..... 208
HDLC communication link between CMB and FUC broken ........ 209
LAPD communication link between FUC and BSC broken ......... 210
CU parameter configuration error ........................................ 210
Communication broken between EAM and CMB ...................... 211
BSC LAPD communication link broken .................................. 211
Site LAPD communication link broken................................... 211
Cell interruption alarm ....................................................... 212
Front-end communication link broken alarm ......................... 212
Control link broken............................................................ 213
Operation link broken(CS) .................................................. 213
Operation link broken(PS) .................................................. 213
Handling Alarms ......................................................... 214
Process Instance Configuration Error ................................... 214
T Network Connection Not Conform to Configuration .............. 214
DB Config Doesn't Fit for Device.......................................... 215
OMC Gateway Mask Different from DBs ................................ 215
Alarm Due to Inconsistent Area Code................................... 215
Alarm Due to Inconsistent Mac Address of Background OMP(OMC)
...................................................................................... 216
Alarm Due to Inconsistent Mac Address of Background OMP(OMC)
...................................................................................... 216
Alarm Due to Inconsistent MP Type ..................................... 216
Startup File Does Not Exist ................................................. 217
OMP GateWay IP Different from DBs .................................... 217
OMC Server IP Different from Dbs ....................................... 217
OMC Gateway Mask Different from DBs ................................ 217
OMP Config Changes ......................................................... 218
Inconsistent Office ID Settings of DIP Switch ........................ 218
Port Work Mode Doesn't Match Settings ............................... 218
Formats of audio resource inconsistent................................. 219
Version Switches While Board Doesn't Reset ......................... 219
Function EPLD Update Failure ............................................. 220
Inconsistent BOOT/EPLD Version No. with Database Configurations
...................................................................................... 220
Boot Version Fails to Be Written to Backup Region ................. 220
Microcode Is Abnormal ...................................................... 221
PVC Fault......................................................................... 221
FE reports unacceptable configuration parameters(M size) ...... 222
symmertry mode) ............................................................. 222
OAM lable)....................................................................... 222
Fe IMA Group is in config-aborted state (because of other reseans)
...................................................................................... 223
FE is in Insufficient links State ............................................ 223
Near-End IMA Group Configuration Failure............................ 223
NE Group is in Insufficient links State .................................. 224
Number of Alarms Over Threshold ....................................... 224
Board Connection Check is Off............................................. 224
Access DSP's HPI memory error ......................................... 225
The config data of sntp in DBS is wrong................................ 225
The Client Of Sntp Failed In Fetching Net Time ...................... 225
SNTP failure ..................................................................... 226
Number of management module alarms exceeds the threshold 227
NTP time exceeds threshold ................................................ 227
brs main config request timeout .......................................... 228
brs main epu register timeout ............................................. 228
Database config is different from file named bootcfg ini. ......... 229
Wrong Parameter configuration for TPU Ch0.......................... 229
Cell configuration parameter mismatch(BTS V2) .................... 232
Software version of FUC mismatch(BTS V2) .......................... 233
Software version of CHP mismatch(BTS V2) .......................... 233
L3 Software of FUC No Response(BTS V2)............................. 233
Wrong Parameter configuration for CIP................................. 234
Software version of CIP mismatch........................................ 234
Wrong parameter configuration for TRM Channel 0................. 234
Cell configuration parameter mismatch................................. 238
FUC Software version mismatch .......................................... 238
CHP Software version mismatch .......................................... 238
CU Software version mismatch ............................................ 239
FUC L3 Software no response.............................................. 239
Parameter configuration mismatch....................................... 239
Parameter configuration failure of AD6537 ............................ 240
Environment Alarms .................................................... 240
Cell delineation do not synchronization about cell on E1 link ... 240
RACK Temperature Over Alarm Threshold............................. 240
RACK Temperature Lower Than Alarm Threshold ................... 241
House temperature is higher than high threshold................... 241
House temperature is lower than high threshold .................... 242
Any one of rack voltage inputs above threshold ..................... 242
Any one of rack voltage inputs below threshold ..................... 242
Temperature in equipment room above threshold .................. 243
Temperature in equipment room below threshold .................. 243
Rack fans faults ................................................................ 244
Rack door access control alarm ........................................... 244
Smoke alarm.................................................................... 244
Infrared alarm .................................................................. 245
Lightning alarm ................................................................ 245
SNTP server invalid ........................................................... 245
Fault on Board (GPS)......................................................... 246
QoS Alarms ................................................................ 246
Inter-board Message Communication Flow Rate Over Alarm
Threshold ........................................................................ 246
Inter-board Message Communication DSP overload (Level 1 alarm)
...................................................................................... 247
...................................................................................... 247
...................................................................................... 247
MTP2 link reception overload .............................................. 248
Association congested ....................................................... 248
STC office congested ......................................................... 249
Appendix A ................................................................... 251
Abbreviations ............................................................... 251
Tables ........................................................................... 259
Index ............................................................................ 261

About This Manual
Purpose
This manual describes BSS (V6.20) related alarm messages in
terms of alarm cause, influence, and handling suggestions. You
can analyze, locate, and handle faults by referring to this
document.
Intended Audience
This manual is intended for engineers and technicians who
perform operation activities on the ZXG BSS.
Prerequisite Skill and Knowledge

To use this manual effectively, users should have a general
understanding of wireless telecommunications technology.
Familiarity with the following is helpful:
ZXG system and its various components
User interfaces on the Mobile Switching Center (MSC)
Local operating procedures
What Is in This Manual

This manual contains the following chapters:
TABLE 1 CHAPTER SUMM ARY
Chapter Summary
Chapter 1, Alarm Introduces the basic concepts of BSS
Messages (V6.20) alarms, including alarm definition,
severity, handling suggestions, and
classification
Chapter 2, Alarm Describes the BSS (V6.20) alarms in terms
Message Description of alarm cause, influence on the system,
Confidential and Proprietary Information of ZTE CORPORATION i

Chapter Summary
and handing flow.
Related Documentation
The following documentation is related to this manual:
ZXG10 iBSC (V6.20) Base Station Controller Documentation
Guide
ZXG10 iBSC (V6.20) Base Station Controller Technical
Manual
ZXG10 iBSC (V6.20) Base Station Controller Hardware
Manual
ZXG10 iBSC (V6.20) Base Station Controller Installation
Manual
ZXG10 iBSC (V6.20) Base Station Controller Performance
Counters Manual – Volume I
ZXG10 iBSC (V6.20) Base Station Controller KPI Reference
Manual
ZXG10 iBSC (V6.20) Base Station Controller Maintenance
Manual (Routine Maintenance)
Manual (Troubleshooting)
Manual (Emergency Maintenance)
ZXG10 BSS (V6.20) Base Station Subsystem Notification
Handling Manual
ZXG10 BSS (V6.20) Base Station Subsystem OMM Sofrware
Installation Manual
ZXG10 BSS (V6.20) Base Station Subsystem Configuration
Manual (Initial Configuration Guide)
ZXG10 BSS (V6.20) Base Station Subsystem Configuration
Manual (Feature Configuration Guide)
ZXG10 BSS (V6.20) Base Station Subsystem MML Command
Manual
ZXG10 BSS (V6.20) Base Station Subsystem Radio
Parameters Manual
ZXG10 BSS (V6.20) Base Station Subsystem Operation
Manual (Diagnosis and Test)
ZXG10 BSS (V6.20) Base Station Subsystem Operation
Manual (Signaling Tracing)
ii Confidential and Proprietary Information of ZTE CORPORATION

About This Manual

Counter Manual - Volume II
Counter Manual - Volume III
In this manual, ZXG10 iBSC (V6.20) and ZXG10 BSC (V2) are
referred to as BSC, and iBSC refers to only ZXG10 iBSC.
Conventions
Typographical ZTE documents employ the following typographical conventions.
Conventions
TABLE 2 TYPOGRAPHICAL CONVENTIONS
Typeface Meaning
Italics References to other Manuals and documents.
“Quotes” Links on screens.
Bold Menus, menu options, function names, input
fields, radio button names, check boxes, drop-
down lists, dialog box names, window names.
CAPS Keys on the keyshelf and buttons on screens and
company name.
Constant width Text that you type, program code, files and
directory names, and function names.
[] Optional parameters.
{} Mandatory parameters.
| Select one of the parameters that are delimited
by it.
Note: Provides additional information about a
certain topic.
Checkpoint: Indicates that a particular step needs
to be checked before proceeding further.
Tip: Indicates a suggestion or hint to make things
easier or more productive for the reader.
Mouse TABLE 3 MOUSE OPERATION CONVENTIONS

Operation
Conventions Typeface Meaning
Click Refers to clicking the primary mouse button (usually
the left mouse button) once.
Double-click Refers to quickly clicking the primary mouse button
(usually the left mouse button) twice.
Right-click Refers to clicking the secondary mouse button
(usually the right mouse button) once.
Drag Refers to pressing and holding a mouse button and
Confidential and Proprietary Information of ZTE CORPORATION iii

Typeface Meaning
moving the mouse.
How to Get in Touch

The following sections provide information on how to obtain
support for the documentation and the software.
Customer If you have problems, questions, comments, or suggestions
Support regarding your product, contact us by e-mail at
support@zte.com.cn. You can also call our customer support
center at (86) 755 26771900 and (86) 800-9830-9830.
Documentation ZTE welcomes your comments and suggestions on the quality
Support and usefulness of this document. For further questions,
comments, or suggestions on the documentation, you can
contact us by e-mail at doc@zte.com.cn; or you can fax your
comments and suggestions to (86) 755 26772236. You can also
browse our website at http://support.zte.com.cn, which contains
various interesting subjects like documentation, knowledge base,
forum and service request.
iv Confidential and Proprietary Information of ZTE CORPORATION

Declaration of RoHS
Compliance
To minimize the environmental impact and take more

responsibility to the earth we live, this document shall serve as
formal declaration that the ZXG10 BSS (V6.20) Base Station
Subsystem manufactured by ZTE CORPORATION is in
compliance with the Directive 2002/95/EC of the European
Parliament - RoHS (Restriction of Hazardous Substances) with
respect to the following substances:
Lead (Pb)
Mercury (Hg)
Cadmium (Cd)
Hexavalent Chromium (Cr(VI))
PolyBrominated Biphenyls (PBB’s)
PolyBrominated Diphenyl Ethers (PBDE’s)
The usage of the above substances in ZXG10 BSS (V6.20) is
explained in Table 4.
TABLE 4 – USAGE EXPLANATION OF THE HAZ ARDOUS SUBSTANCES IN ZXG10

BSS (V6.20)
Hazardous substances
Names of Parts
Pb Hg Cd Cr(VI) PBB’s PBDE’s
System × 0 0 0 0 0
Cables and Assembly 0 0 0 0 0 0
Auxiliary Equipment × × × × × ×
Table Explanation:
0: The usage of the substance in all of the components is less
than the allowed values given by 2002/95/EC standard.
×: The usage of the substance in at least one of the components
is beyond the allowed values given by 2002/95/EC standard.
Confidential and Proprietary Information of ZTE CORPORATION v

The ZXG10 BSS (V6.20) Base Station Subsystem manufactured

by ZTE CORPORATION meet the requirements of EU
2002/95/EC; however, some assemblies are customized to client
specifications. Addition of specialized, customer-specified
materials or processes which do not meet the requirements of
EU 2002/95/EC may negate RoHS compliance of the assembly.
To guarantee compliance of the assembly, the need for
compliant product must be communicated to ZTE CORPORATION
in written form.
This declaration is issued based on our current level of
knowledge. Since conditions of use are outside our control, ZTE
CORPORATION makes no warranties, express or implied, and
assumes no liability in connection with the use of this
information.
vi Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1
Alarm Message Summary
This chapter introduces the basic concepts of alarm messages,

such as alarm code definition, alarm severity level, alarm
handling suggestions, and alarm classification.
Alarm Code Definition

An alarm code is defined by a string of 32 bits, which indicates
the code values of a specified alarm message.
The range of GSM BSS alarm codes is as follows:
1 ~ 100000
198000000 ~ 198065535
198066000 ~ 198079999
198087000 ~ 198089999
198099800 ~ 198099801
Alarm Severity Level

Whenever there is a problem or fault during BSC operation, an
alarm message appears. Usually, the alarm may last till the
problems or faults are rectified.
According to severity, alarms are divided into four levels:
Critical (level 1)
Critical alarms cause the whole system to fail to operate or
provide services. Measures must be taken to recover or
eliminate the alarms immediately.
Major (level 2)
Severe alarms greatly affect the system operation or result
in severe degradation in performance of service provision.
Confidential and Proprietary Information of ZTE CORPORATION 1

Measures must be taken to recover or eliminate the alarms

as soon as possible.
Minor (level 3)
Major alarms do not greatly affect normal system operation
and performance of service provision. Measures should be
taken to recover or eliminate the alarms in time to avoid
more severe alarms.
Warning (level 4)
Minor alarms have potential effects on normal system
operation and performance of service provision. Diagnosis
and measures should be taken to avoid more severe alarms.
In alarm level definition, the affected range only refers to the
influence on a single item, that is, alarm level can be determined
if a certain index, such as reliability and safety, reaches the
specified range. If an alarm affects several indices, the alarm
level should be upgraded.
Note:
Alarm levels can be modified in the Netnumen M31 EMS
system based on the actual situations.
Generally, the default settings are comparatively reasonable.
Be cautious when re-defining levels. It is not allowed to
modify the settings at will.
In addition, some alarm levels are not defined. For these alarms,
users can define their levels in actual situations.
Alarm Handling
Pay attention to the following points when handling alarms:
After noting down the problem and symptom, system
maintenance personnel should handle the alarms step by
step by referring to the solutions described in this manual.
Unless otherwise specified, end the alarm handling once the
fault is rectified (that is, the alarm is recovered), or go to the
next step if the problem persists.
If the alarm fails to be handled or recovered, contact the
local ZTE office.
2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Alarm Message Summary
Alarm Classification
The BSS related alarm messages on Netnumen M31 can be
classified into the following six types:
Equipment alarms
Communication alarms
Handling alarms
Environment alarms
QoS alarms


Chapter 2
Alarm Messages
This chapter gives a comprehensive and systematic description

of the BSS (V6.20) related alarm messages, which helps system
maintenance personnel to have a clear idea about every alarm
generated at the BSS side. This chapter explains:
Alarm cause
Influence on the system
Handling method
Equipment Alarms
Loss of Optical Transceiver Module
Signal
Alarm Property Alarm code: 198000002
Alarm level: 2
Alarm Cause The local-end RX fiber or peer-end TX fiber is not properly
connected.
The local or peer-end optical transceiver module is faulty.
The peer end does not export optical signals forcibly.
The UIM has no TFS subcard or the board does not provide
TDM optical interface function.
Influence The link connected to the fiber circuit is broken and the service
is interrupted.
Handling Flow 1. Correctly insert the local and the peer-end fibers and check if
the alarm is eliminated.
2. Replace the fiber and check if the alarm is eliminated.

3. Replace the local-end optical transceiver module and check if

4. Replace the peer-end optical transceiver module and check if
5. Check if the peer-end device forcibly inhabits output and if
Remarks UIM consists of UIMC, UIMU, and UIMT.
Ethernet Controller's Physical Link

Off
Alarm level: 3
Alarm Cause The network cables are not connected to the OMC1 and
OMC2 interfaces on the rear shelf.
The network cable fails or looses.
The network interfaces on the shelf are faulty.
Influence A link connected to the Ethernet is broken. The symptom is
that the OMC interface is disconnected, that is, the
communication between the NE and the EMS server is
broken.
Handling Flow 1. Check if network interface OMC2 is connected with network
cables and if they are loose.
f If the cables loose, go to step 2.
f If the cables are not loose, go to step 3.
2. Insert cables to OMC2 on both ends again and check if the
alarm is eliminated.
3. Replace the cables for OMC2 and check if the alarm is
eliminated.
4. Use crossover cables and straight cables for OMC2 and check
if the alarm is eliminated.
Trunk Link Is Used for CSU

Loopback Test
Alarm level: 3
Alarm Cause The equipment at end A sends CSU link building code to end B,
and this trunk link is set to loopback at end B. Then, CSU test

Chapter 2 Alarm Messages
starts. If this trunk link is not used for CSU loopback test, this
alarm won't be triggered.
Influence The configured trunk link is congested.
Handling Flow After diagnosis and test, do some settings, where end A sends
the command of canceling CSU loopback to end B.
Cell Delineation Not Synchronized

Alarm level: 3
Alarm Cause The HEC is damaged. The cell cannot be located from the
physical layer frame. This problem is usually triggered from
bottom layer fault. It may also because the local and peer-end
devices use different methods to process HEC.
Influence The ATM communication becomes worse.
Handling Flow 1. Check if other alarms are generated accompanying its
occurrence. If yes, clear these alarms. If no, go to step 2.
2. Check if both ends are configured to SDH mode or SONET
mode. If the modes are different, configure a correct signal
mode.
Loss of Cell Delineation

Alarm level: 2
Alarm Cause LCD is triggered after OCD lasts for 4 ms.
Influence The ATM communication is broken.
mode.
8K input clock lose

Alarm level: 3
Alarm Cause The clock input of the shelf is abnormal.
Influence The system communication fails.
Handling Flow Check whether the clock input line is correctly connected.

16M Input Clock Lose

Alarm level: 3
Handling Flow Check whether the clock input line is correctly connected.
PP2S Clock Input Lose

Alarm level: 3
Handling Flow 1. Check if the clock input lines are correctly connected.
2. Check if the subrack of output clock locks the GPS signals.
32M Clock lost in TSNB

Alarm level: 3
Alarm Cause As the clock consists of 32M and 8K, the 32M clock alarm is
generated when the clock (32M or 8K) jitters out of the
specified range and affects the links.
The clock is unavailable.
Influence The whole link is blocked if the alarm is generated. Therefore,
the clock cannot be lost. Two boards for reporting alarms are
used in a system, with one active and the other one standby.
When a clock alarm is generated, the system switches over
between the active and standby TSNBs.
For Tier 1 network, clock loss means loss of the whole link
data. The link is recovered only after the clock becomes
normal.
Handling Flow Check if the clock input lines are correctly connected.

Clock Phase Does not Match When

Inputting 8k,16M Clock to Backboard
Alarm level: 3
Alarm Cause The clock input of the shelf is abnormal. The clock line is not
reliably connected or faulty.
Clock Chip of This Board Is in

Preheat Status
Alarm level: 3
Alarm Cause The board experiences reset. The SETS chip and the constant-
temperature crystal oscillator needs to be fully preheated.
Influence The output clock is unstable.
Handling Flow Perform normal operations after the board is powered on. Wait
until the clock board is completely preheated. Conduct the clock
performance test only after the preheat ends.
Loss of Clock When Input to Board

Alarm level: 3
SDH/SONET fault
Alarm level: 2
Alarm Cause The upstream optical transmission device is faulty.
The optical fiber transmission line is faulty.

The fiber pigtail and flange between the local-end ODF

(optical distribution frame) and equipment are faulty.
The local-end optical receiver is faulty.
Influence All the trunk receiving signals that are transmitted through the
SDH/SONET line are interrupted.
Handling Flow 1. Use an optical power meter to check if the power for
receiving optical signals is within the specified range (that is,
-28 dBm ~ -8 dBm).
f If yes, go to step 3
f If no, it can be inferred that the optical module is faulty,
and then go to step 2.
2. Replace the optical module or board. Check if the alarm is
eliminated.
3. Use the transmitting end at the peer-end office to detect the
transmitting optical signal. Check if the signal is within the
specified range.
f If yes, go to step 5.
f If no, it can be inferred that the peer end is faulty, and
then go to step 4.
4. Ask maintenance personnel to check the peer-end office.
After the fault is rectified, check if the alarm is eliminated.
5. Something may be wrong with the transmission equipment.
Ask maintenance personnel special for transmission
equipment to do troubleshooting.
SDH/SONET:Loss of Frame
Alarm level: 2
Alarm Cause The upstream SDH devices are faulty.
Handling Flow Ask SDH transmission equipment maintenance personnel to
rectify the faults.
SDH/SONET: Regenerator Section

Trace Mismatch/Section Trace
Mismatch

Alarm level: 2
Alarm Cause The optical fiber on the optical distribution frame is incorrectly
connected during optical fiber cutover and scheduling, or the
expected value is incorrectly set on the network management
system.
Influence The matching relations of the trunks and trunk signals are wrong.
Handling Flow 1. Check if the fibers are correctly connected to the ODFs at
local end and peer end.
f If no, correctly connect the fibers, and then check if the
2. Check if the predefined values of “section access point
identifier” at both ends are consistent. If not, set the same
value. Check whether the alarm is eliminated.
SDH/SONET:MS-AIS,Line Alarm
Indication Signal
Alarm level: 2
Alarm Cause The upriver equipment has faults, such as LOS, LOF, and RS TIM.
Handling Flow Clear the “primary alarm” according to the alarm generated from
the network node equipment in the corresponding multiplexing
section.
SDH/SONET:Multiplexing Section
Far-end Reception Failure/Line Far-
end Reception Failure
Alarm level: 3
Alarm Cause Errors occur on the uplink direction of the downstream
equipment.
Influence All the trunk sending signals that are transmitted through the
Handling Flow Clear the “primary alarm” according to the alarm generated from
the network node equipment in the corresponding multiplexing
section.

SDH/SONET:Signal Failure
Alarm level: 2
Alarm Cause For all the NEs in the multiplexing section where the board
resides, the fiber pigtail connectors in the down direction are
contaminated. The increase of transmission line attenuation
or change in optical transmission mode leads to error code.
The ADM transmit device is faulty.
SDH/SONET line generate large numbers of alarms.
Handling Flow 1. Check if the fiber pigtail heads are contaminated.
f If yes, clean the connectors, and then check if the alarm
is eliminated.
f If no, go to step 2.
2. Use an optical power meter to detect the optical power
attenuation of each connection point in the down direction in
the multiplexing section and find if the value is excessive.
f If yes, adjust the attenuation, and then check if the
3. Ask maintenance personnel for transmission network to
check if the ADM transmit device is faulty, end the alarm
handing.
SDH/SONET:Signal Deterioration
Alarm level: 3
Alarm Cause When signal degrade (SD) and signal fail (SF) occur at the same
time, eliminate SF first. When SD occurs individually, it can be
inferred that the ADM transmit device is faulty.
Influence Some trunk receiving signals generate various alarms.
Handling Flow 1. Eliminate SF, if it occurs. Check if the alarm is eliminated.
2. Check the optical fibers and fiber transceiver modules at the
local and peer ends. Ensure that the optical fibers are well
connected and that the optical transceiver module is not
loose. Check if the alarm is eliminated.
3. Replace the fiber module or board. Check if the alarm is
eliminated.

4. Ask maintenance personnel to check the peer-end office and

rectify the faults. Check if the alarm is eliminated.
SDH/SONET:Loss of AU-4
Pointer/Loss of Channel Pointer
Alarm level: 2
Alarm Cause The upstream AU-4 pointer processing unit is faulty.
Handling Flow Ask maintenance personnel for transmission network to check if
the AU-4 pointer processing unit of the upstream device is faulty.
SDH/SONET:AU-AIS/Channel-AIS
Alarm level: 2
Alarm Cause The upstream VC-4 channel control unit is faulty.
SDH line are interrupted.
the VC-4 channel control unit of the upstream device is faulty.
SDH/SONET:HP-Trace Mismatch/
Patch Trace Mismatch
Alarm level: 2
Alarm Cause The optical fiber on the ODF is incorrectly connected during
optical fiber cutover and scheduling, or the expected value is
incorrectly set on the network management system.
Influence The matching relations of all the trunk signals are wrong.


2. Check if the predefined values of “VC-4 channel access point
identifier (J1)” at both ends are consistent. If not, set the
same expected value. Check if the alarm is eliminated.
SDH/SONET:HP Unassembled/Path
Unassembled
Alarm level: 2
Alarm Cause During project installation, the internal cross connection of SDH
network is not complete, or the SDTB/SDTB2 remote device is
not equipped with the channel where SDTB/SDTB2 locates.
the VC-4 channel control unit (C2) of the upstream device is
faulty.
DH/SONET:HP Label Mismatch/Path

Label Mismatch
Alarm level: 2
network is not complete.
the upstream and downstream circuit configuration (C2) of the
DXC devices in each station during the corresponding timeslot is
correct.
SDH/SONET:HP Remote Reception

Failure
Alarm level: 3
Alarm Cause

The network node in VC-4 channel where the board locates is

faulty.
Handling Flow Rectify the “source fault” according to the alarm generated on
the network node equipment in the VC-4 channel where the
board locates.
SDH/SONET:LOM
Alarm level: 2
Alarm Cause The upstream VC-4 channel control unit is faulty.
the VC-4 channel control unit (H4) of the upstream device is
faulty.
SDH/SONET: Loss of TU
Pointer/Loss of Virtual Tributary
Pointer
Alarm level: 4
Alarm Cause The upstream TU pointer processing unit is faulty.
Influence The trunks that the tributary bears stop receiving trunk signals.
the upstream TU-12 tributary pointer processing unit is faulty.
SDH/SONET:Tributary Unit Alarm

Indication Signal/Virtual Tributary
Alarm Indication Signal
Alarm level: 4
Alarm Cause

The upstream TU-12 pointer processing unit is faulty. The fault

may be TU AIS, TU LOM, TU LOP, or TU UNEQ.
Influence All the E1 lines that the tributary bears stop receiving trunk
signals.
Handling Flow Ask the maintenance personnel of transmission network to check
if the upstream TU-12 tributary pointer processing unit is faulty.
SDH/SONET:LP Remote Defect

Indication/Virtual Tributary Remote
Defect Indication
Alarm level: 4
Alarm Cause The local end TU-12 tributary malfunctions.
The devices on other nodes on the TU-12 tributary have
tributary function faults.
Influence The trunks that the tributary bears stop receiving send trunk
signals.
Handling Flow 1. Check if the optical fibers are correctly connected to the
ODFs at the local end and peer end and if the processing of
the TU-12 tributary pointer of the upstream equipment is
faulty.
f If the connection is correct and there is no fault, go to
step 3.
f If the connection is wrong or there is a fault, go to step 2.
2. Correctly connect the optical fibers. Check if the alarm is
eliminated. This is upstream troubleshooting.
3. Check the alarms at both ends. Check the alarms at the peer
end before checking those at the local end. A loopback
operation can also be performed to locate the problem step
by step from the local end equipment, transmission
equipment, and peer end equipment. Two methods can be
used, software loop and hardware loop. Check if the alarm is
eliminated.
4. Replace the board. Check if the alarm is eliminated.
SDH/SONET:LP-RFI/Virtual
Tributary-RFI
Alarm level: 4

Alarm Cause The upstream TU-12 tributary control unit is faulty.

Handling Flow 1. Check if the optical fibers are correctly connected to the
ODFs at the local end and peer end and if the processing of
the TU-12 tributary pointer of the upstream equipment is
faulty.
f If the connection is correct and there is no fault, go to
step 3.
f If the connection is wrong or there is a fault, go to step 2.
eliminated. This is upstream troubleshooting.
3. Check the alarms at both ends. Check the alarms at the peer
end before checking those at the local end. A loopback
operation can also be performed to locate the problem step
by step from the local end equipment, transmission
equipment, and peer end equipment. Two methods can be
used, software loop and hardware loop. Check if the alarm is
eliminated.
SDH/SONET:LP-Trace Mismatch/
Virtual Tributary Trace Mismatch
Alarm level: 4
Alarm Cause The optical fiber on the digital distribution frame (DDF) is
incorrectly connected during optical fiber cutover and scheduling,
or the expected value is incorrectly set on the network
management system.
Influence The matching relations of the trunks and trunk signals that the
tributary bears are wrong.
2. Check if the predefined values of “VC-12 channel access
point identifier (J2)” at both ends are consistent.
f If no, set the same value. Check whether the alarm is
eliminated.

SDH/SONET:LP-Unloaded/Virtual
Tributary Unloaded
Alarm level: 4
network is not complete, or the remote device isn't equipped
with the tributary.
Handling Flow 1. Check the optical fibers and fiber transceiver modules at the
connected and that the optical transceiver modules are not
2. Ask maintenance personnel to check the connections at both
ends. Ensure that the signal label received by the tributary is
consistent with that at the local end. Check if the alarm is
eliminated.
3. Ask the maintenance personnel for transmission equipment
to use an SDH tester to check if the upstream and
downstream circuit configurations of each DXC node device
on the transmission line during the corresponding timeslot
are correct, and check if V5 byte configuration is consistent
with that at peer-end. (The default configuration at local end
is asynchronous mapping.)
SDH/SONET:LP Label
Mismatch/Virtual Tributary Label
Mismatch
Alarm level: 4
Alarm Cause The upstream and downstream circuits of DXCs of each station
are not complete. The V5 signal label is inconsistent with that at
the peer end.
2. Ask maintenance personnel to check the configuration
connections at both ends. Ensure that the information on V5

signal label is consistent with that at the peer end. Check if

SDH:VC-4 Signal Failure

Alarm level: 2
Influence The link connected to the optical path is broken.
eliminated.
SDH:VC-4 Signal Deterioration

Alarm level: 3
Influence The link connected to the optical path is broken.
Handling Flow 1. Eliminate SF for VC-4, if it occurs. Check if the alarm is
eliminated.
eliminated.


SDH/SONET:Severe B1 Error Code

Alarm level: 2
Alarm Cause The receiving signal attenuation is excessive.
The transmitting part of the directly connected transmission
equipment is faulty.
The optical fiber head is contaminated or the connector is
wrong.
The receiving part at the local end is faulty.
Influence All the voice services that the optical path bears have noises or
call losses. The data service channel has error codes.
eliminated.

Alarm level: 2
wrong.
The peer-end transmitting part in multiplexing section is
faulty.
The local-end receiving part in multiplexing section is faulty.
B2 error code

Influence All the voice services that the optical path bears have noises or
call losses. The data service channel has error codes.
eliminated.

Alarm level: 2
wrong.
The peer-end transmitting part based on higher order path is
faulty.
The local-end receiving part is faulty.
B1 and B2 error codes
Influence The voice services that the corresponding high order path bears
have noises or call losses. The data service channel has error
codes.
eliminated.

SDH/SONET:Severe BIP-2 Error

Code
Alarm level: 4
Alarm Cause The low order path is interfered.
The peer-end transmitting part based on lower order path is
faulty.
The local-end receiving part is faulty.
Influence The voice services that the tributary bears have noises or call
losses. The data service channel has error codes.
eliminated.
SDH/SONET:MS-Remote Error
Indication
Alarm level: 2
wrong.
Influence The voice services that the optical path bears have noises or call


eliminated.
SDH/SONET:HP-Remote Error
Indication
Alarm level: 2
wrong.
Influence The voice services that the optical path bears have noises or call
eliminated.
SDH/SONET:HP Signal Failure

Alarm level: 2

SDH/SONET line generate large numbers of alarms.
eliminated.
SDH/SONET:HP Signal
Deterioration
Alarm level: 2
Influence Some trunk receiving signals generate various alarms.
Handling Flow 1. Eliminate SF, if it occurs. Check if the alarm is eliminated.
eliminated.
E3S subcar transmitter direction loss

of signal
Alarm level: 3

Alarm Cause Transmitter loss of signal is asserted when no transitions are

observed on transmit data for at least 32 consecutive clock
cycles.
Influence The E3S subcard cannot work normally.
Handling Flow Reset the board.
Remarks Transmitter loss of signal is deasserted as soon as transition on
transmit data are observed.
Signal of Receiving End of E3S

Daughter Card is Lost
Alarm level: 3
Alarm Cause The cable connection is broken.
Influence The E3S subcard cannot work normally.
Handling Flow Check if the cable connection is normal. If the cable is
disconnected, correctly connect the cables. Check if the alarm is
eliminated.
OFF Alarm
Alarm level: 3
Alarm Cause The protocols used by the two matching parties mismatch.
They must use the E3 (E1) or T3 (T1) protocols at the same
time. E3 (E1) cannot match T3 (T1)
Cable transmission incurs error.
Influence E3 transmission is exceptional.
Handling Flow 1. Check if the protocols used by the matching parties match
each other, that is, both use E3 (E1) or T3 (T1).
f If they mismatch, configure the same protocol.
f If they match, go to step 2.
2. Check if the equipment cable impedance matches, if the
board’s DIP switch matches the cable, and if the jumper cap
of the rear board matches the cable.
f If they mismatch, reconfigure the board DIP switch or
jumper cap on the rear insertion card. Check if the alarm
is eliminated.
f If they match, go to step 3.

3. Use a multimeter to check if the grounding signals of the

equipment at both ends are reliable.
f If they are unreliable, make them reliable. If the alarm is
eliminated, end the alarm handling.
f If they are reliable, go to step 4.
4. Check if the CLKG/ICM board locks clock (that is, TRACE is
permanently green).
f If the clock is not locked, lock it.
f If the clock is locked, go to step 5.
5. Check if the clock references of two matching NEs or nodes
are consistent.
f If no, modify the clock benchmarks to make them
consistent.
6. Check if the protocols configurations of the two matching
parties are consistent. Ask for assistant of the maintenance
personnel special for transmission equipment to check if the
transmission equipment is exceptional. Locate the fault step
by step through physical diagnosis and loopback test.
E3S Daughter Card Receives Alarm

Signal Indication
Alarm level: 3
Alarm Cause The peer-end equipment is faulty.
Handling Flow Check if the peer-end equipment has generated alarms related
to E3 subcard. Clear them if they are available.
Remote Failure Indication

Alarm level: 3
Alarm Cause The cable link is faulty.
Handling Flow Replace the cable and then check if the high error rate is
resulted from link fault.

Board CPU overloaded

Alarm level: 2
Alarm Cause When the upper-layer service traffic is huge, the CPU usage
is too high and may exceed the threshold of CPU occupancy.
The set threshold value of the CPU overload alarm is small,
which may result in CPU overload alarm.
Influence The message processing delay is prolonged. Packets are lost.
Handling Flow 1. Query the threshold of CPU overload alarm through
background and see if the value is too small.
f If the threshold is small, modify the threshold. Wait for
30 seconds. Then, check if the alarm is eliminated.
f If the threshold is reasonable, go to step 2.
2. Wait for the system to recover itself without performing any
operations. After 30 seconds, check if the alarm is recovered.
3. Check if the service in process is busy or there is any
software being downloaded.
f If the current service is busy, or there is any software
being downloaded, wait until the current service
processing or software downloading ends, check if the
f If the current service isn't busy, or there isn't any
software being downloaded, go to step 4.
4. Note down the alarm information.
Excess Temperature of CPU on

Board
Alarm level: 2
Alarm Cause The fans do not work properly or are insufficient.
The temperature in the equipment room is too high.
Influence High temperature in equipment room causes the CPU to
automatically reset.
Handling Flow 1. Check if the fans work normally and if the fans are
insufficient.
f If the fans are insufficient, add fans and power on all the
fans. Wait for ten minutes. Check if the alarm is
eliminated.

f If the fans are not powered on, power them on and wait
for ten minutes. Check if the alarm is eliminated.
f If the fans are sufficient and work normally, go to step 2.
2. Check if the temperature in the equipment room is too high.
f If the temperature is high, improve the ventilation
situation or take measures to reduce the temperature.
After the temperature returns to normal range, check if
f If the temperature is normal, go to step 3.
Board FLASH faults

Alarm level: 2
Alarm Cause The FLASH is damaged.
Influence All operations related to the FLASH fails.
Handling Flow 1. Confirm if there is any standby board that can be used for
replacement.
f If yes, replace the board and check if the alarm is
eliminated.
Inter-shelf media plane links

abnormal
Alarm level: 2
Alarm Cause The optical fibers between UIM/GLI and UIM/GLI are not
correctly connected, or the optical fibers are not inserted.
The background configuration of UIM is inconsistent with its
foreground physical configuration.
The transceiver of UIM link detection packet is exceptional.
Influence The media plane is interrupted.
Handling Flow 1. Configure BUSN-BUSN (or BGSN-BGSN) double-shelf
interconnection or BUSN-BPSN (or BGSN-BPSN) multi-shelf
cascade connection for UIM. Then, check if the background
configuration is consistent with the foreground physical
connection.

f If they are inconsistent, adjust the connection in line with

the configuration requirements. Check if the alarm is
eliminated.
f If they are consistent, go to step 2.
2. Check the fiber connection to see if cross connection is
adopted. If cross connection is not adopted, change the
physical connections of optical fibers. Check if the alarm is
eliminated.
Capacity of intra-shelf control plane

TRUNK communication is insufficient
Alarm level: 3
Alarm Cause The physical line or port configuration is incorrect.
Influence The network communication capacity is insufficient.
Handling Flow 1. Check the port connection relation of TRUNK to see if there is
any incorrect connection.
f If incorrect connections exist, change the port connection
based on the configuration. Check if the alarm is
eliminated.
f If no incorrect connection exists, go to step 2.
Incorrect Connection of GE Optical

Transceiver Module with Board Slots
on Peer-end
Alarm level: 3
Alarm Cause The GE optical transceiver module is incorrectly connected with
the left and right board slot on the peer-end
Influence The media plane flow is broken.
Handling Flow Connect the optical fibers in cross mode. Check if the alarm is
eliminated.
Internal Port of Board Is Down


Alarm level: 2
Alarm Cause The number of internal ports configured for this board and
the neighboring slots exceeds the number of physical slots.
Pin Healthy of this slot on the backplane is damaged.
Influence The media flow cannot be transmitted through this port. If all
internal ports generate alarms, the internal media flow is
interrupted.
Handling Flow 1. Check if the number of internal ports configured for this
board and the neighboring slots exceeds the number of
physical slots.
f If yes, modify the configuration and synchronize the data.
Check if the alarm is eliminated.
2. Check if the board has clock input alarms.
f If yes, follow the suggestions on handling of related
alarms to do troubleshooting.
3. Replace the backplane or change the configured slot. Then
check if the alarm is eliminated.
4. Switch the active and standby UIM boards in the same shelf.
Board Doesn't Exist/ CPU is Long in

Reset Status
Alarm level: 2
Alarm Cause The board configured in the database is not in position.
The board incurs fault when being reset.
The Pin Healthy of this slot in the backplane is damaged.
Influence The board or board CPU of this slot work exceptionally and fail to
provide normal services.
Handling Flow 1. Check if the board is correctly inserted.
f If no, insert the board. Check if the alarm is eliminated.
2. Pull out and then plug in the board again in position. Check if
3. Replace the slot. Check if the alarm is eliminated.

Input Clock Abnormal

Alarm level: 1
Alarm Cause The clock plate runs exceptionally, and is not in the normal
working status.
No clock reference is input to the clock board.
The clock reference is exceptional.
Influence The system cannot obtain the clock.
Handling Flow 1. Check if the configured clock reference is correctly inputted.
f If no, input the clock reference. Check if the alarm is
eliminated.
A (CPU) Subcard Is Online, but Is

not Configured in Database
Alarm level: 4
Alarm Cause The (CPU) sub-card is physically inserted in position, but it is not
configured in the database.
Influence The CPU that is not configured constantly reset. Therefore, the
alarm that the CPU reset abnormally is generated constantly on
the background. This problem does not affect the function.
Handling Flow Confirm if this sub-card is required.
f If yes, configure the CPU in the database. Check if the
f If no, pull out the CPU subcard. Check if the alarm is
eliminated.
A (CPU) Subcard Is not Online, but

Has Been Configured by Database
Alarm level: 2
Alarm Cause The (CPU) sub-card is configured in the database, but it is not
physically inserted in position.

Influence The CPU that is not configured constantly reset. Therefore, the
alarm that the CPU reset abnormally is generated constantly on
the background. This problem does not affect the function.
Handling Flow 1. Confirm if this sub-card is inserted in position.
f If yes, pull out the board and insert the sub-card in
position. Then, power on the board again. Check if the
2. Confirm if this sub-card is required.
f If yes, insert the sub-card. Check if the alarm is
eliminated.
f If no, delete the configuration from the database. Check
External Port of Board Is Down

Alarm level: 2
Alarm Cause The network interface at the local end or the peer end is
faulty.
The work modes of network interfaces at both ends do not
match.
The physical connection has faults
Influence Data fails to be transmitted through the network interface. The
service may be disrupted.
Handling Flow 1. Check if the connection between the port on this board and
the peer-end one is correct.
f If correct, go to step 2.
f If incorrect, correctly connect the port on this board with
the peer-end one. Check if the alarm is eliminated.
2. Configure the work mode of the port on the local end to
make it consistent with that of the port on the peer end. Or
configure the work mode of the port on the peer end to make
it consistent with that of the port on the local end. Then
check if the alarm is eliminated
3. Replace the board or the network interface in used at the
local end. Then, check if the alarm is eliminated.
4. Replace the network interface used at the peer end. Then,

Exceptional Internal Media Plane

Communication
Alarm level: 2
Alarm Cause The packet loss rate of the internal media plane of the board
exceeds the preset threshold (25% by default).
Influence The media flow cannot transmit normally.
Handling Flow If the alarm board is a first level switching unit, do as follows:
i. Restart the board. Check if the alarm is eliminated.
ii. Reset the PSN associated with the board. Check if the
iii. Replace the slot. Check if the alarm is eliminated.
If the alarm board is not a first level switching unit, do as
follows:
i. Restart the board. Check if the alarm is eliminated.
ii. Switch the active/standby UIM board in the same shelf.
iii. Replace the slot. Check if the alarm is eliminated.
Remarks This problem seldom occurs.
DSP Resource Unavailable

Alarm level: 2
Alarm Cause The DSP does not succeed in loading the version and cannot
work normally.
The DSP has HPI interface exception.
The media plane loopback fails.
Lan91 link is broken.
The link of 5328 port is broken.
The DSP running halts.
The system initialization of the Tone resource DSP fails.
Different formats of tone resources or even no tone resource
exists on the board.
Influence Some DSP related services cannot work normally.
Handling Flow 1. Query the related alarm information to locate the fault
causes. Confirm if the fault can be rectified.

2. Wait for 24 hours and DSP will reset. Then, re-load the
version. If the time is insufficient, go to step 3.
3. Manually stop up the DSP or replace the board. Check if the
Usage Rate of Board Hard Disk

above Threshold
Alarm level: 2
Alarm Cause The hard disk usage exceeds the threshold at a certain level.
Influence Data may be lost if the hard disk of the board continues using.
Handling Flow 1. Check if the threshold value configured on the background is
too small.
f If the value is too small, go to step 2.
f If the value is reasonable, go to step 3.
2. Modify the small threshold value to a normal one and
synchronize data. Then, check the alarm is
3. Delete those useless data unless they are being used. If all
the data is in use, switch the board and use the hard disk of
the new mainboard.
Remarks The hard disk usage has three levels of threshold.
Hard Disk Broken

Alarm level: 2
Alarm Cause The hard disk of the board is faulty.
Influence Data is lost.
Handling Flow 1. Switch the board and use the hard disk of the new
mainboard.
2. Replace the hard disk.
TRUNK port down


Alarm level: 3
Alarm Cause The TRUNK port is not totally connected through network
cables.
The network cables or BCM5615 port is faulty.
Influence Data cannot be transmitted on the control plane.
Handling Flow Check if the network cables are correctly inserted and if the
BCM5615 port is normal.
Remarks This alarm seldom occurs.
Broad Not Tightly Inserted

Alarm level: 2
Alarm Cause The ENUM switch of the broad is opened.
The EXCH key on the standby board is pressed down twice
within 3 seconds.
Influence The standby board is in the cold standby state.
Other board faults occur.
Handling Flow 1. Check the ENUM switch. If is turned on, turn it of. Then,
check if alarm is eliminated.
2. If the alarm is caused by pressing ENUM, switch on/off ENUM
again. Check if the alarm is eliminated.
SMBUS Error
Alarm level: 2
Alarm Cause If the board is reset when the read-write time sequences of the
SMBUS equipment are not finished, the SMBUS cannot be
enabled after the south bridge is reset. All the SMBUS
equipments need be reset again (the board need be pulled out
and plugged).
Influence When the SMBUS incurs error, the board can be restarted
through BIOS settings. However, after the version is run, the
temperature cannot be detected for the board with SMBUS
error. Therefore, the board may be running in high
temperature without being noticed.
If the board has SMBUS error, the configuration of the
memory size follows the default setting. In this case, the
memory size may be inconsistent with the actual one.
Handling Flow 1. Pull out and plug in the board. Check if alarm is eliminated.

Error in Rear Board That

Mismatches With Front Board
Alarm level: 3
Alarm Cause The rear board mismatches the front board.
Influence The resources on the rear board are unavailable.
Handling Flow Replace the rear board with one matching with the front board,
and then check if the alarm is eliminated.
Remarks The boards of some old versions do not provide the function of
version detection for rear board.
LVDS Signal Unlocked

Alarm level: 2
Alarm Cause LVDS signal at the bottom layer is unlocked.
Influence All the circuit domains of the resource frames connected to
the FTI optical interface may be interrupted. The HW
loopback of the service board fail.
If the switch board is faulty, all the circuit switching fail.
Handling Flow Switch or pull out and plug in the board. Check if the alarm is
eliminated.
High Error Rate of Optical Interface

Alarm level: 2
Alarm Cause The optical fiber is not connected in position or is damaged.
The optical fiber does not match the optical transceiver
module.
Influence The data transmitted through the optical interface is incorrect.
Handling Flow 1. Check if the optical fiber is connected in position and if it is
damaged.

f If the fiber is not connected in position, correctly connect

it. Check if the alarm is eliminated.
f If the fiber is damaged, replace with another one. Check
2. Check if the fiber matches the optical transceiver matches. If
no, replace with a matching optical fiber. Check if the alarm
is eliminated.
FPGA Exception
Alarm level: 2
Alarm Cause FPGA runs exceptionally. For example, FPGA is lost and the
mother board clock is lost.
Influence The board cannot work normally.
Handling Flow Restart the board and then the board downloads EPGA again.
Port Link Down

Alarm level: 2
Alarm Cause There is something wrong with the lan91 chip or bcm5328 chip.
Influence The DSP works abnormally. Call drops are increased.
Handling Flow 1. Reset the DSP chip by using MML commands on the
background. Check if the alarm is eliminated.
Hardware Reliability Down

Alarm level: 2
Alarm Cause The hardware of the hard disk has faults.
Influence Data is lost.
The system is collapsed.
Handling Flow 1. Use a new hard disk and configure it. Then, check if the

2. Switch the active/standby board and use the hard disk on

the new mainboard. Then, check if the alarm is eliminated.
PLL Work Mode Abnormal

Alarm level: 3
Alarm Cause No benchmark source is available.
The clock distribution path is incorrect, or self loop exists.
The second level clock may lock the third level clock.
Influence The specified reference clock cannot lock phase.
Handling Flow Check if clock reference available.
If yes, replace the board. Check if the alarm is eliminated.
If no, correctly access the clock reference. Check if the alarm
is eliminated.
The Channel in a Subcard Is Down

Alarm level: 2
Alarm Cause The hardware of the sub-card channel has faults or it is not
inserted in position.
Influence A single channel cannot work normally.
Handling Flow 1. Plug the sub-card tightly, and check if the alarm is eliminated.
2. Reset the board, and check if the alarm is eliminated.
Subcard Abnormal
Alarm level: 3
Alarm Cause The UIM/CHUB GCS sub-card is exceptional. The probable
reasons are:
The sub-card is not inserted in position.
Packet loss occurs during large data flow.
Other causes.
Influence The sub-card malfunctions.
Handling Flow 1. Check the sub-card connection to see if it looses.

f If it looses, insert the card in position and then check if

f If it does not loose, go to step 2.
2. Replace the sub-card.
Phase-lock Loop Unlock

Alarm level: 1
Alarm Cause The phase-lock loop cannot be locked due to the hardware fault.
Influence The clock is exceptional.
Handling Flow It may result from the hardware fault. Replace the board.
High Error Rate at E1 Bottom Layer

Alarm level: 2
Alarm Cause The E1/T1 link is faulty or there is any other equipment fault in
the uplink direction of the trunk link.
Influence The trunk cannot receive trunk signals.
Handling Flow 1. Check if the trunk link at the local end is faulty and eliminate
the primary fault. Check if the alarm is eliminated.
2. Check if there is any other equipment fault in the uplink
direction of the trunk link. Eliminate the fault and then check
Control Plane Ports of Backplane

Joining Switching Chip Is
Exceptional
Alarm level: 2
Alarm Cause The control plane ports of such boards as SPB/SPB2 are faulty or
do not transceive packets for more than 3 minutes.
Influence The path to the control plane of the backplane is blocked.
Handling Flow Check the corresponding port status on UIM after fault diagnosis.
If the port is normal, reset the board or pull and plug the
board. Check if the alarm is eliminated.

If the port is not normal, reset the UIM board. Check if the
Type A Fault on Board (GPS)

Phase-lock Equipment
Alarm level: 1
Alarm Cause The board hardware has faults.
Influence The SETS chip works abnormally.
Handling Flow Replace the faulty board.
Type B Fault on Board (GPS)

Phase-lock Equipment
Alarm level: 2
Phase-lock Equipment of This Board

(GPS) Is in Power-on Status
Alarm level: 1
DSP Reports Exceptions After

Detection
Alarm level: 2

Alarm Cause DSP reports the port or other exceptions after detection.
Influence The DSP works abnormally. The call loss is increased.
Handling Flow 1. Reset the corresponding DSP chip by using MML command
on the background. Then, check if the alarm is eliminated.
Loss of Clock When Input to Sub-

card
Alarm level: 2
Alarm Cause The sub-card is not in position or the hardware is faulty.
Influence The sub-card clock cannot work normally.
Handling Flow 1. Insert the sub-card again. Check if the alarm is eliminated.
2. Replace the sub-card or board. Check if the alarm is
eliminated.
Error of LVDS Path Frame Detection

Alarm level: 2
Alarm Cause Errors occur in LVDS path frame detection
Influence The board may fail to work.
Handling Flow 1. Check if the TFI optical fiber corresponding to this path is
connected in place or if it is damaged.
f If the fiber is connected in place and not damaged, go to
step 2.
f If the fiber is damaged or not connected in place, go to
step 3.
2. Insert the optical fiber in place or replace the fiber. Check if
3. Check if the fiber matches the optical transceiver module.
4. Replace the optical fiber. Check if the alarm is eliminated.
5. Switch T network board. Check if the alarm is eliminated.

Tier1 Network Link Loopback

Diagnosis Failure
Alarm level: 2
Alarm Cause 129 Time slot loopback of LVDS has a failure.
Influence The board may fail to work normally.
Handling Flow 1. Check if the TFI optical fiber corresponding to this path is
connected in place or if it is damaged.
f If the fiber is connected in place and not damaged, go to
step 2.
f If the fiber is damaged or not connected in place, go to
step 3.
2. Insert the optical fiber in place or replace the fiber. Check if
3. Check if the fiber matches the optical transceiver module.
4. Replace the optical fiber. Check if the alarm is eliminated.
5. Switch T network board. Check if the alarm is eliminated.
Physical link down between master

port and slave port
Alarm level: 4
Alarm Cause The physical link between master port and slave port is broken.
Influence The APS function does not take effect.
Handling Flow 1. Replace the slot. Check if the alarm is eliminated.
Media interactive GE port link down

Alarm level: 4
Alarm Cause The APS is configured. The physical link between media
interactive GE ports is broken.

Influence The APS time is prolonged.

Board device is abnormal

Alarm level: 2
Alarm Cause The board devices or sub-cards do not work properly.
Handling Flow Replace the board. Check if the alarm is eliminated.
Cx29704 Runs Abnormally

Alarm level: 3
Alarm Cause The problem is due to chip fault. If the alarm can be recovered
immediately, it is a false alarm. If it can not be recovered, it
must result from some chip bugs. In that case, it needs to reset
the board.
Influence The Cx29704 chip cannot work normally.
Handling Flow 1. Reset the board. Check if the alarm is eliminated.
Physical Channel for Data

Transmission Blocked
Alarm level: 2
Alarm Cause The board hardware is faulty.
Traffic flow to this board is excessive.
When any board is in processing, a board is resetting.
PSN board in the same shelf is exceptional.
Network processor sub-card which has worked normally is
loose.
Influence The data packet processing may be affected, which may cause
the services that the board bears to be unstable.

Handling Flow 1. Restart the board where the alarm happens (board of
Release version can restart automatically). Check if the
2. Check if PSN in the same shelf has fault.
f If yes, follow the suggestions on the related alarm.
3. Pull out and plug in the board. Check if the alarm is
eliminated.
2350 receive hardware error

Alarm level: 2
Alarm Cause The alarm is generated when BIPI/GIPI/EIPI board receive a
certain number of hardware-error frames in a period.
Influence The data packet processing may be affected, which may cause
the services that the board bears to be unstable.
Handling Flow Check the board. Replace another board if alarm occurs
continually.
Fe IMA Group is in config-aborted

state (because of unmatched Frame
length)
Alarm level: 2
Alarm Cause The near-end IMA receives the report that the far-end IMA is in
the “configuration failure state” in the ICP cell.
Influence The IMA link is broken.
Handling Flow 1. Check if the configurations of frame length (M) on both near
end and far end match. If they mismatch, set the matching
values. Check if the alarm is eliminated.
2. Check if the configurations of symmetric parameters on both
near end and far end match. If they mismatch, set the
matching values. Check if the alarm is eliminated.
3. Check if the configurations of IMA protocol version on both
near end and far end match. If they mismatch, set the
matching values. Check if the alarm is eliminated.

All High-Speed Links Between Line

Card and Package Switching Board
Are out of Synchronism
Alarm level: 1
Alarm Cause All High-Speed Serial Links connected to PSN are out of
synchronism. The 872 chip may have fault.
The 882 chip on PSN has faults.
The PSN board has faults.
Influence The media plane of a board cannot work. If the problem is due
to PSN, the whole service is broken.
Handling Flow 1. Check if PSN boards are set to load sharing working mode.
f If no, set PSN boards to loading sharing working mode.
Restart PSN boards and the board where the alarm
happens. Check if the alarm is eliminated.
2. Check if PSN boards are in running status.
f If no, check which board is not powered on successfully
through process.
3. Check if the PSN work normally.
f If yes, restart the board where there is a fault and check
4. Replace the board where there is a alarm reported. Check if
APS Channels Mismatched

Alarm level: 2
Alarm Cause The peer end has faults. That is, the configuration has faults or
the devices do not support. The symptom is the bridging channel
that the remote end indicates through K2 is not the one required
by the local.
Influence The switchover fails when the configuration is 1:1.
Handling Flow 1. Check if configurations on the two ends are both 1+1 or
1:1(1:N).

f If no, modify them as consistent ones. Check if the alarm

is eliminated.
2. Check if PSN boards are in running status. Check if the
optical fiber connections are correct. If no, correctly connect
the optical fibers and check if the alarm is eliminated.
APS Modes Mismatched

Alarm level: 2
Alarm Cause Protection types on the two ends are inconsistent, one end
adopts 1+1 mode, the other end adopts 1: n mode,(one-way or
two-way). For SDTB/SDTB2, SONET mode also determines if
both are unidirectional or bidirectional.
Influence The switchover result may be different from the expectation.
Channels may be blocked.
Handling Flow 1. Check if configurations on the two ends are both 1+1 or
1:1(1:N).
f If no, modify them as consistent ones. Check if the alarm
is eliminated.
2. Check if optical fiber connections are correct. If no, correctly
connect the optical fibers and check if the alarm is eliminated.
Board Resets for APS Configuration

Changes
Alarm level: 2
Alarm Cause The boards are set as 1+1 mode and do not configure APS.
FE or HW fails to be opened.
Influence The service is broken.
Handling Flow Check if the backup mode configured on board is consistent with
that on APS optical port. If no, modify the configurations as
consistent ones. Check if the alarm is eliminated.
Remarks 1:1 backup mode on board corresponds to inter-board backup
mode on APS optical port, no backup mode on the board
corresponds to inner-board backup or no backup on APS optical
port.

No Response to Requesting
Database for Secondary Forwarding
Table Information
Alarm level: 2
Alarm Cause The OMP is not normally powered on.
Control plane messages are delayed.
Influence The media flow in the shelf of the UIM is broken.
Handling Flow 1. Restart the OMP board to see if it works normally.
2. Restart the UIM board to see if it works normally.
3. Record the details.
No Response to Requesting the

System for Secondary Forwarding
Table Port Information
Alarm level: 2
Alarm Cause The system control process on the UIM is not normally
powered on.
The number of IP addresses configured for sub-units in one
shelf exceeds 200.
Influence The media flow in the shelf of the UIM is broken.
Handling Flow 1. Restart the UIM board to enable it to work normally.
2. Log in to OAM background and switch tot the protocol mode.
View the IP configuration of the port by using the show ip
interface brief command. Check if the number of IP
addresses configured for sub-units in one shelf is more than
200. If yes, delete some IP addresses to make the number
less than 200. Check if the alarm is eliminated.

Resource board Unable to Get

Secondary Forwarding Table from
UIM
Alarm level: 2
Alarm Cause The shelf is not BUSN/BGSN.
The UIM board on the shelf is not powered on normally.
Control plane messages are blocked.
Influence The resource board cannot get the secondary forwarding table.
Handling Flow 1. Check if the resource shelf is BUSN/BGSN shelf.
f If no, change it to BUSN/BGSN shelf and configure the
rack again. Check if the alarm is eliminated.
2. Check if the UIM board on the shelf is powered on normally.
If no, make sure that the UIM board is powered on normally.
Remarks Only the UIM in the BUSN/BGSN shelf has secondary forwarding
table.
Internal Connection Chip Faults of

TSNB
Alarm level: 2
Alarm Cause Connection chip (73273/73260) faults on T network board cause
some 129 time slots of HW having connection faults.
Influence For TSNB, if the faults occur on the active board, the system
switches to the standby board; if the faults occur on the standby
board, the standby board reset.
Semi-Fixed Connection Error

Alarm level: 3

Alarm Cause Bugs exist in configuration or chip.

Influence The link may be broken.
Handling Flow Check the configuration. Replace the board. Check if the alarm is
eliminated.
CLKG 32M output clock lost

Alarm level: 2
Alarm Cause The CLKG/ICM 32M output clock is lost.
Influence The system cannot obtain the required clock, which leads to
exceptions in clock related processing.
Handling Flow Check if the CLKG/ICM output clock is normal. If no, replace the
CLKG/ICM board.
CLKG 32M8K output clock lost

Alarm level: 2
Alarm Cause The CLKG/ICM 32M8K output clock is lost.
CLKG/ICM board.
CLKG 16M output clock lost

Alarm level: 2
Alarm Cause The CLKG 16M output clock is lost.
Handling Flow Check the CLKG/ICM board and software. Replace the board.
CLKG 16M8K output clock lost


Alarm level: 2
Alarm Cause The CLKG/ICM 16M8K output clock is lost.
CLKG/ICM board.
CLKG PP2S Output Clock Lost

Alarm level: 2
PP2S clock reference lost

Alarm level: 2
Handling Flow 1. Check the type of the alarm board.
f If the board is CLKG, go to step 2.
f If the board is ICM, go to step 3.
2. Check if PP2S clock is correctly led to CLKG from the control
rack.
f If no, correctly lead PP2S clock to CLKG. Check if the
16CHIP clock reference lost

Alarm level: 2

All clock bases had lost

Alarm level: 2
Alarm Cause Clock base lost is detected for the first time.
Influence The clock related processing is exceptional.
Handling Flow 1. Check if the input reference base of ICM is normal (through
the CLKG/ICM rear board).
2. Check if the background configuration is correct.
CLKG I2MB0 clock base lost

Alarm level: 3
Alarm Cause The I2MB0 clock base is lost.
Handling Flow 1. Check if the 2MB0 input of RCKG1/RCKG2 is normal.
CLKG I2MB1 clock base lost

Alarm level: 3
Alarm Cause The I2MB1 clock base is lost.
Handling Flow 1. Check if the 2MB1 input of RCKG1/RCKG2 is normal.
CLKG I2MHZ0 clock base lost

Alarm level: 3
Alarm Cause The I2MHZ0 clock base is lost.


Handling Flow 1. Check if the 2MHZ0 input of RCKG1/RCKG2 is normal.
CLKG I2MHZ1 clock base lost

Alarm level: 3
Alarm Cause The I2MHZ1 clock base is lost.
Handling Flow 1. Check if the 2MHZ1 input of RCKG1/RCKG2 is normal.
CLKG I8KBASE clock base lost

Alarm level: 3
Alarm Cause The I8KBASE clock base is lost.
Handling Flow 1. Check if the 8KBASE input of RCKG1/RCKG2 is normal.
CLKG I8KGPS clock base lost

Alarm level: 3
Alarm Cause The I8KGPS clock base is lost.
Handling Flow 1. Check if the 8KGPS input of RCKG1/RCKG2 is normal.
CLKG I8KUIM clock base lost

Alarm level: 3
Alarm Cause The I8KUIM clock base is lost.


Handling Flow For CLKG/ICM, the base does not serve as the base source.
Clock reference source lost (Level 3

alarm)
Alarm level: 3
Alarm Cause Clock base lost is detected for the first time.
Handling Flow Check if the corresponding clock reference is correctly led in.
If no, correctly lead in this clock reference. Check if the

alarm)
Alarm level: 2
Alarm Cause Clock reference lost has been detected for more than 10 minutes.

alarm)
Alarm level: 1
Alarm Cause Clock reference lost has been detected for more than 24 hours.

Clock Base Lost

Alarm level: 3
Alarm Cause The clock base configured on the background is lost.
Handling Flow 1. Check if the input reference base of ICM is normal (through
the CLKG/ICM rear board)
2. Check if the backcard is loose.
CLKG board PLL out-of-lock

Alarm level: 3
Output clock lost

Alarm level: 2
DSP over load

Alarm level: 2

Alarm Cause DSP's load has reached a dangerous degree.

Influence The voice quality is poor and call loss may occur.
Handling Flow Check if the preset threshold is reasonable. If reasonable,
reduce the DSP traffic. If not reasonable, change the threshold
setting.
80g chip abnormal

Alarm level: 1
Alarm Cause 80g detects that the gliqp board restarts, or the 80g chip is
abnormal.
Influence Media plane partially loses messages or is interrupted.
Handling Flow 1. Restart the board for which the alarm is reported. Check if
SCCP SSN is invalid

Alarm level: 3
Alarm Cause The remote signaling point sub-system exits services.
The remote signaling point is inaccessible.
The remote office has deleted the SubSystem Number (SSN).
This SSN is not configured in the remote office, but the SSN
of the remote office is configured at the local end. This
causes SST test failure.
Influence User fails to transceive messages on the subsystem.
Handling Flow 1. Check through Alarm Management whether there is any
alarm prompting this adjacent office inaccessible.
f If MTP3 office inaccessible alarms or M3UA office
inaccessible alarms exist, perform further handling
according to the office inaccessible alarms.
f If no office inaccessible alarms exist, go to step 2.
2. Check the local data configuration to see whether the
subsystem is correctly configured in local office configuration
and adjacent office configuration.
f If no, configure the subsystem. Then, check if the alarm
is eliminated.

3. Check configuration data of the peer adjacent office to see

whether the corresponding sub-system is configured in local
office configuration and adjacent office configuration as well.
f If no, contact the personnel of the peer-end office to
configure the data. After the configuration is complete,
f Back up related local office configuration data and peer-
end office configuration data.
f Back up related local office and peer-end office history
alarms and notifications, as well as current alarms.
Broadband link congestion

Alarm level: 3
Alarm Cause The traffic is heavy.
The loads among links are unbalanced.
The link resource is insufficient.
Influence The link is congested, which may cause package losses and call
drops.
Handling Flow 1. Make no manual intervention and just wait the system to
recover. 30 seconds later, check if the alarm is eliminated.
2. Check if the service in process is busy.
3. Check whether there are sufficient link resources.
f If sufficient, query performance statistic data to check
whether load are evenly shared among links. If yes, go to
step 1. If no, go to step 4.
f If insufficient, add new links and check whether this
alarm is eliminated. If no, use the above method for
sufficient link resources.

Broadband link overload

Alarm level: 3
Influence When the link is overloaded, it discards received packages. This
causes call drops.
MTP2 link transmission overload

Alarm level: 2
Influence Messages fail to be transceived.

MTP3 office inaccessible

Alarm level: 2
Alarm Cause Office and route configuration has error.
The link is broken
Influence Corresponding office fails to be transceive messages.
Handling Flow 1. Check whether the static route settings of the destination
office are correct.
f If no, configure or modify the corresponding static route.
2. Query link status in the route table through Dynamic
Management on the background to check whether there are
links available.
3. Check alarms on the background to see whether there are
alarms prompting no link available.
f If yes, perform further handling as described in “MTP3
link unavailable”.

MTP3 link unavailable

Alarm level: 3
Alarm Cause The link is physically blocked.
Link test failed.
CMP board is restarted or SPB/SPB2 board is restarted.
Influence Corresponding office fails to be transceive messages.
Handling Flow 1. Check whether there is new data configuration or the
configuration has been changed. Check link configuration
data, especially signaling point code (SPC), SLC and network
type (international or domestic) to see whether they accord
with the peer end of the link.
f If no, modify the configuration. Check if the alarm is
eliminated.
2. Check whether there is any alarm for bottom layer
transmission.
f If yes, ask a transmission engineer to handle the problem.
3. Perform physical link self-loop on the devices at the two ends
of the link on the DDF, and check whether this alarm is
eliminated.
f If yes, ask a transmission engineer to handle the problem.
MTP3 cluster inaccessible

Alarm level: 2
Alarm Cause The cluster and route configuration are incorrect.
The link is broken.
Influence The corresponding office fails to transceive messages.
Handling Flow

1. Check whether the static route settings of the destination

cluter are correct.
f If no, configure or modify the corresponding static route.
2. Query link status in the route table through Dynamic
Management on the background to check whether there are
links available.
3. Check alarms on the background to see whether there are
alarms prompting no link available.
f If yes, perform further handling as described in “MTP3
link unavailable”.
MTP3 link congestion

Alarm level: 2
Influence The corresponding office fails to transceive messages.


M3UA office inaccessible

Alarm level: 2
Alarm Cause The association is released or the Application Server (AS)
has not entered serving state, which causes office
inaccessible.
No SIOLOCAS table data to this office are configured, which
causes AS unable to be bound with the office managed by
M3UA.
Influence User fails to transceive messages to the corresponding office.
Handling Flow 1. Check the configuration data to see whether SIO location of
this office is configured.
f If no, configure the SIO location data. Then, check if the
2. Check the data configuration to see whether the AS
corresponding to the SIO location of this office is activated.
3. Check whether Application Server Process (ASPs) under this
AS are activated.
f If there are ASPs activated under this AS and the number
of them exceeds the necessary number N, go to step 6.
f If there is no ASP activated under this AS or the number
of activated ASPs does not reach the necessary number N,
go to step 4.
4. Check whether the association of ASP is activated.
f If the association is activated but the ASP is not, go to
step 5.
f If the association of the ASP is not activated, perform
further handling according to “Association Link Broken”.
5. De-activate and then activate the associations serving this
office, and check whether this alarm is eliminated.


SUA SSN is invalid

Alarm level: 3
Alarm Cause A signaling point sub-system has services.
The association or AS is not in serving state, which causes a
signaling point inaccessible.
SSN location AS is not configured.
Handling Flow 1. Check through Alarm Management whether there is any
alarm prompting this adjacent office inaccessible.
f If SCCP User Adaptation (SUA) office inaccessible alarms
exist, perform further handling as described in “SUA
office inaccessible.”
f If no SUA office inaccessible alarms exist, go to step 2.
2. Check the local data configuration to see whether the
subsystem is correctly configured in local office configuration
and adjacent office configuration.
f If no, configure the subsystem. Then, check if the alarm
is eliminated.
3. Check configuration data of the peer adjacent office to see
whether the corresponding sub-system is configured in local
office configuration and adjacent office configuration as well.
f If no, contact the personnel of the peer-end office to
configure the data. After the configuration is complete,

SUA office inaccessible

Alarm level: 2
Alarm Cause A signaling point sub-system exists services.
The association or AS is not in serving state, which causes a
signaling point inaccessible.
SSN location AS is not configured.
Handling Flow 1. Check configuration data to see whether SSN location of this
office is configured.
f If yes, go o step 2.
f If no, configure the related data. Then, check if the alarm
is eliminated.
2. Check the data configuration to see whether the AS
corresponding to the SSN location of this office is activated.
3. Check whether ASPs under this AS are activated.
f If there are ASPs activated under this AS and the number
of them exceeds the necessary number N, go to step 6.
f If there is no ASP activated under this AS or the number
of activated ASPs does not reach the necessary number N,
go to step 4.
4. Check whether the association of ASP is activated.
f If the association is activated but the ASP is not, go to
step 5.
f If the association of the ASP is not activated, perform
further handling according to section 2.2.42.
5. De-activate and then activate the associations serving this
office, and check whether this alarm is eliminated.
M2PA Link Broken


Alarm level: 3
Alarm Cause The association is broken.
Upper layer services are stopped.
The peer end originates a release.
Influence The messages are discarded.
Handling Flow 1. Check whether the association for M2PA link is available by
checking for alarms for related association broken in Alarm
Management.
f If no, perform further handling according to section
2.2.42.
2. Check whether the protocols at the two end of the M2PA link
are consistent.
f If no, change protocols to be consistent. Check if the
3. Check whether the associations used at the two end of the
M2PA link are consistent.
f If the associations are consistent and available, go to
step 4.
f If the associations are inconsistent, change the
associations to be consistent. Check if the alarm is
eliminated.
BSC IP configuration error

Alarm level: 2
Alarm Cause The BSC IP configured in the database is incorrect.
Influence The protocol stack fails to be powered on. The board cannot
work normally.
Handling Flow 1. Check whether BSC IP is configured.
f If no, configure BSC IP. Check if the alarm is eliminated.
2. Check whether the BSC IP is all 0s or all 1s.

f If yes, change the BSC IPs. Check if the alarm is
eliminated.
3. Check whether the communication between BIPI/GIPI and
OMP is normal.
f If no, check for OSS communication link alarms on
background and perform handling according to the alarm
information. Check if the alarm is eliminated.
4. Record all UIP IP configurations.
T-net center fault

Alarm level: 2
Alarm Cause The T-net center board has a fault.
Influence T-net resources are unavailable.
EPU and RPU Version Not Match

Alarm level: 2
Alarm Cause The versions of EPU and RPU do not match.
Influence The EPU cannot be powered on normally.
Handling Flow Change the EPU version to the one matching the RPU version.
Abnormal Status in SDH/SONET

Alarm level: 3
Alarm Cause The upstream optical transmission device is faulty.
SDH/SONET line are interrupted. All voice services that the
optical path bears may have noise or call drop. Data service
channel may have error codes.
Handling Flow

1. Check if the optical fibers are correctly connected on the

local-end and peer-end ODFs. Check if upstream equipment
is faulty. Ensure that the optical module is tightly inserted.
f If no fault exists, go to step 3
f If there is fault, go to step 2.
eliminated.
3. Check the alarm modes and related preset values at both
ends. A loopback operation can also be performed to locate
the problem step by step from the local end equipment,
transmission equipment, and peer end equipment. Two
methods can be used, software loop and hardware loop.
eliminated.
5. Ask maintenance personnel special for transmission
SDH/SONET:Excessive Error Code

Alarm level: 2
SDH/SONET line are interrupted. All voice services that the
optical path bears may have noise or call drop. Data service
channel may have error codes.
eliminated.

ATM Communication Abnormally

Alarm level: 3
Alarm Cause The HEC is damaged. The cell cannot be located from the
physical layer frame. This problem is usually triggered from
bottom layer fault. It may also because the local and peer-end
devices use different methods to process HEC.
Influence The ATM communication is interrupted.
mode.
MCC Abnormal
Alarm level: 2
Alarm Cause The MCC hardware is faulty.
Influence All MCC channels cannot transceive data.
Handling Flow Pull out the board for 5 seconds and insert it again after a full
discharge. Check if the alarm is eliminated.
MS APS Channel gets errors

Alarm level: 2
Alarm Cause The APS channel between master and slave boards is faulty.
The connection on the backplane between the slot and the
neighboring slot gets errors.
Influence The APS function is affected.
The active/standby function of the board is affected.
Handling Flow 1. Restart the board. Check if the alarm is eliminated.
3. Replace the neighboring board. Check if the alarm is
eliminated.
4. Replace two neighboring slots. Check if the alarm is
eliminated.

Dry Contact Alarm 1

Alarm level: not defined
Alarm Cause Dry contact alarm 1.
Influence None.
Handling Flow None.
Remarks User-defined
Dry Contact Alarm 2

Influence None.
Handling Flow None.
Dry Contact Alarm 3

Influence None.
Handling Flow None.
Dry Contact Alarm 4

Influence None.

Handling Flow None.

Dry Contact Alarm 5

Influence None.
Handling Flow None.
Dry Contact Alarm 6

Influence None.
Handling Flow None.
Dry Contact Alarm 7

Influence None.
Handling Flow None.
Dry Contact Alarm 8

Influence None.

Handling Flow None.

Dry Contact Alarm 9

Influence None.
Handling Flow None.
Dry Contact Alarm 10

Influence None.
Handling Flow None.

Influence None.
Handling Flow None.

Influence None.

Handling Flow None.

EAM Dry Contact Alarm 1

Influence None.
Handling Flow None.

Alarm Cause Dry contact alarm 2
Influence None.
Handling Flow None.

Influence None.
Handling Flow None.

Influence None.

Handling Flow None.


Influence None.
Handling Flow None.

Influence None.
Handling Flow None.

Influence None.
Handling Flow None.

Influence None.

Handling Flow None.

CMM/CMB FLASH programming

failure
Alarm level: 3
Alarm Cause Too many times of FLASH programming leads to read/write error.
Influence Any version fails to be loaded and read/write.
Handling Flow The fault arises by FLASH chip failure, which cannot be solved by
user. Replace CMM/CMB board in time.
Power overvoltage/undervoltage
alarm
Alarm level: 3
Alarm Cause CMM/CMB power voltage is out of adjustment range.
Influence CMB works exceptionally.
Handling Flow Replace CMM/CMB board as soon as possible.
13M input clock failure

Alarm level: 3
Alarm Cause CMM/CMB clock unit works exceptionally.
Influence BTS internal transmission link is interrupted. Frame numbers are
out of order. The frequency synthesizer is exceptional.
Handling Flow Replace CMM/CMB board as soon as possible.
Frame No. inconsistent between

software and hardware
Alarm level: 3

Alarm Cause Interference level on the circuit causes frame number

accumulation to interrupt.
Influence TPU frame No. is out of order. All DTRUs of the CMB works
abnormally.
Handling Flow If the fault can't restore, clock system of CMM/CMB has
problems. Replace CMM/CMB board as soon as possible.
FCLK clock failure

Alarm level: 3
Alarm Cause CMM/CMB clock unit works abnormally.
Handling Flow Clock alarm is shown on front panel. Replace CMM/CMB board as
soon as possible.
SYNCLK clock failure

Alarm level: 3
Alarm Cause CMM/CMB clock unit works abnormally.
Handling Flow Clock alarm is shown on front panel. Replace CMM/CMB board as
soon as possible.
Master and slave communication link

failure
Alarm level: 4
Alarm Cause Standby CMM/CMB board is not powered on, or communication
between active and standby CMM/CMB boards has error.
Influence Active and standby CMBs cannot be switched mutually.
Handling Flow Check if the standby CMM/CMB board is powered on. If not,
power on the standby CMM/CMB. If it is powered on, replace
CMM/CMB board as soon as possible.

Standby CMM/CMB board not

present
Alarm level: 4
Alarm Cause The standby CMM/CMB board is not inserted.
Influence The active board cannot be switched to the standby board when
errors occur. The system reliability is reduced.
Handling Flow Check if standby board is present in the rack. If it is, reset or
insert standby board again (normal state of standby board is
that power lamp always lights and running lamp always lights).
If it isn’t, insert a new CMM/CMB board.
Standby CMM/CMB board abnormal

Alarm level: 4
Alarm Cause Standby CMM/CMB board starts abnormally or is not inserted
properly.
Influence The active and standby boards cannot be switched normally.
Handling Flow 1. Check if standby board is powered on.
f If no, power on the standby board. Check if the alarm is
eliminated.
2. Reset the board. Check if the alarm is eliminated.
3. Power on the standby board. Check if the alarm is eliminated.
CMM/CMB power failure alarm

Alarm level: 3
Alarm Cause CMM/CMB board is power off.
Influence CMM fails to work.
Handling Flow E1 interface will bridge-connect automatically. Replace the
CMM/CMB board as soon as possible

A interface E1 Rx carrier alarm

Alarm level: 3
Alarm Cause The alarm is due to chip fault, abnormal clock, difference from
BSC clock, bad E1 connections, or others.
Influence If the problem seldom occurs, the conversation is slightly
affected. If the problem frequently occurs, for example, once
every several minutes, the conversation is abnormal or the link
between TRM/DTRU and BSC is abnormal.
Handling Flow 1. Check the electric-connection performance of E1 line through
loopback test.
f If fault exists, make cables again to rectify the faults.
f If no fault exists, go to step 2.
2. Tightly insert CMM/CMB and power it on again. Check if the
3. Start the self-loop detection and check if the E1 interface
self-loop detection is normal.
f If yes, it is inferred that the transmission is faulty.
Troubleshoot the transmission faults.
4. Replace CMM/CMB board. Check if the alarm is eliminated.
5. Replace the backplane.
A interface E1 Rx frame not

synchronized
Alarm level: 3
loopback test.


A interface E1 Tx forward sliding

indication
Alarm level: 3
loopback test.
A interface E1 Tx backward sliding

indication

Alarm level: 3
loopback test.
A interface E1 Rx forward sliding

indication
Alarm level: 3
loopback test.


A interface E1 Rx backward sliding

indication
Alarm level: 3
loopback test.
B interface E1 Rx carrier alarm

Alarm level: 3


loopback test.
B interface E1 Rx frame not

synchronized
Alarm level: 3
loopback test.

B interface E1 Tx forward sliding

indication
Alarm level: 3
loopback test.
B interface E1 Tx backward sliding

indication
Alarm level: 3
loopback test.


B interface E1 Rx forward sliding

indication
Alarm level: 3
loopback test.
B interface E1 Rx backward sliding

indication

Alarm level: 3
loopback test.
C interface E1 Rx carrier alarm

Alarm level: 3
loopback test.


C interface E1 Rx frame not

synchronized
Alarm level: 3
loopback test.
C interface E1 Tx forward sliding

indication
Alarm level: 3
Handling Flow

1. Check the electric-connection performance of E1 line through

loopback test.
C interface E1 Tx backward sliding

indication
Alarm level: 3
loopback test.

C interface E1 Rx forward sliding

indication
Alarm level: 3
loopback test.
C interface E1 Rx backward sliding

indication
Alarm level: 3
loopback test.


D interface E1 Rx carrier alarm

Alarm level: 3
loopback test.
D interface E1 Rx frame not

synchronized
Alarm level: 3
Alarm Cause

The alarm is due to chip fault, abnormal clock, difference from

loopback test.
D interface E1 Tx forward sliding

indication
Alarm level: 3
loopback test.

D interface E1 Tx backward sliding

indication
Alarm level: 3
loopback test.
D interface E1 Rx forward sliding

indication
Alarm level: 3


loopback test.
D interface E1 Rx backward sliding

indication
Alarm level: 3
loopback test.

E interface E1 Rx carrier alarm

Alarm level: 3
loopback test.
E interface E1 Rx frame not

synchronized
Alarm level: 3
loopback test.


E interface E1 Tx forward sliding

indication
Alarm level: 3
loopback test.
E interface E1 Tx backward sliding

indication

Alarm level: 3
loopback test.
E interface E1 Rx forward sliding

indication
Alarm level: 3
loopback test.


E interface E1 Rx backward sliding

indication
Alarm level: 3
loopback test.
F interface E1 Rx carrier alarm

Alarm level: 3


loopback test.
F interface E1 Rx frame not

synchronized
Alarm level: 3
loopback test.

F interface E1 Tx forward sliding

indication
Alarm level: 3
loopback test.
F interface E1 Tx backward sliding

indication
Alarm level: 3
loopback test.


F interface E1 Rx forward sliding

indication
Alarm level: 3
loopback test.
F interface E1 Rx backward sliding

indication

Alarm level: 3
loopback test.
G interface E1 Rx carrier alarm

Alarm level: 3
loopback test.


G interface E2 Rx frame not

synchronized
Alarm level: 3
loopback test.
G interface E1 Tx forward sliding

indication
Alarm level: 3
Handling Flow

1. Check the electric-connection performance of E1 line through

loopback test.
G interface E1 Tx backward sliding

indication
Alarm level: 3
loopback test.

G interface E1 Rx forward sliding

indication
Alarm level: 3
loopback test.
G interface E1 Rx backward sliding

indication
Alarm level: 3
loopback test.


H interface E1 Rx carrier alarm

Alarm level: 3
loopback test.
H interface E3 Rx frame not

synchronized
Alarm level: 3
Alarm Cause

The alarm is due to chip fault, abnormal clock, difference from

loopback test.
H interface E1 Tx forward sliding

indication
Alarm level: 3
loopback test.

H interface E1 Tx backward sliding

indication
Alarm level: 3
loopback test.
H interface E1 Rx forward sliding

indication
Alarm level: 3


loopback test.
H interface E1 Rx backward sliding

indication
Alarm level: 3
loopback test.

Temperature alarm
Alarm level: 4
Alarm Cause The alarm is due to fan fault or too high module temperature.
Handling Flow Check the environment temperature. If it conforms to the
demand, keep on observing and keep normal status on
prerequisite that other modules have no fault. If not improve the
work environment. If fault exists, change the FCM module.
Fan absent
Alarm level: 4
Alarm Cause The fan is not inserted or not in position.
Influence TRM/DTRU temperature is too high and the performance indices
are affected.
Handling Flow Insert the fan, or pull out and plug in the fan again.
Fan control board CPU alarm

Alarm level: 4
Alarm Cause The CPU is faulty.
Influence The fan is out of control but heat elimination is not affected.
Handling Flow 1. Check if the line has faults.
f If yes, rectify the faults.
2. Change the fan control pane DFCM/FNCB.
Fan control board CPU alarm

Alarm level: 4

Alarm Cause The fan stops rotating due to fault.

Influence The frequency shelf on the same layer has high temperature.
Handling Flow 1. Check if the fan stops rotating.
f If it stops, change the fan subrack.
2. Check if the link between the fan and the fan control board is
faulty.
f If faults exist, go to step 3.
3. Check if the fan cables have faults and if the board-to-board
connectors have faults.
f If the fan cables have faults, change the fan subrack.
f If the board-to-board connectors have faults, change the
fan control board DFCM/FNCB.
4. Check if the alarm line is faulty.
f If yes, troubleshoot the alarm line.
5. Check if alarm collection on the fan control board is
exceptional.
f If exceptions occur, change the fan control board
DFCM/FNCB.
f If no exceptions occur, go to step 6.
6. Check if alarm collecting circuit of TRM/DTRU is exceptional.
If yes, change the TRM/DTRU.
Fan temperature alarm

Alarm level: 4
are affected.

Fan 1 alarm
Alarm level: 4
faulty.
exceptional.
DFCM/FNCB.
Fan 2 alarm
Alarm level: 4

faulty.
exceptional.
DFCM/FNCB.
Fan control board alarm

Alarm level: 4
are affected.
LNA alarm
Alarm level: 3
Alarm Cause LNA current exceeds by 30%.
Influence The connected TRM/DTRU cannot work completely (if both active
and density LNAs are faulty) or cannot work normally (only one
LNA is faulty).

Handling Flow Replace AEM module as soon as possible.
Tower amplifier power alarm

Alarm level: 4
Alarm Cause The problem is caused by AEM tower amplifier alarm.
Influence The uplink receiver sensitivity of the related TRM/DTRU is
affected.
Handling Flow 1. Replace the problem AEM. Check if the alarm is eliminated.
2. Replace the frequency modules on the same layer in
sequence. Check if the alarm is eliminated.
3. Replace the tower amplifier as soon as possible.
SWR of AEM HYCOM minor alarm

Alarm level: 3
Alarm Cause The problem is caused by combiner SWR 1.5 alarm.
Influence The emission is affected.
Handling Flow 1. Measure the SWR of AEM output cable to antenna. Check if
the BWR exceeds the threshold. If yes, the replace the cable
with exceeding values.
2. Replace AEM. Reset the connected DTRU. Check if the alarm
is eliminated.
3. Replace other TRM/DTRU modules at the same layer in
sequence. Reset the frequencies. Check if the alarm is
eliminated.
4. Replace the backplane of the frequency shelf.
SWR of AEM HYCOM major alarm

Alarm level: 2


is eliminated.
eliminated.
AEM power alarm(BTS V2)

Alarm level: 2
Alarm Cause The problem is caused by AEM power alarm.
Handling Flow Replace AEM as soon as possible.
AEM type alarm(BTS V2)

Alarm level: 2
Handling Flow 1. Check if the board DIP switch on the AEM is correct.
f If yes, power it on again and reset the connected
frequency. Check if the alarm is eliminated.
f If no, adjust the board DIP switch.
2. Change AEM. Reset the connected frequency.
AEM absent(BTS V2)

Alarm level: 2
Alarm Cause The problem is caused by AEM not-in-position alarm.

AEM power alarm

Alarm level: 2
Handling Flow Replace AEM as soon as possible.
LNA0 alarm
Alarm level: 3
Alarm Cause LNA0 current exceeds by 30%.
Influence The connected DTRU cannot work completely (if both active and
density LNAs are faulty) or cannot work normally (only one LNA
is faulty).
LNA1 alarm
Alarm level: 3
Alarm Cause LNA1 current exceeds by 30%.
Influence The connected DTRU cannot work completely (if both active and
density LNAs are faulty) or cannot work normally (only one LNA
is faulty).
Tower Amplifier0 power alarm

Alarm level: 4
Alarm Cause The problem is caused by AEM tower amplifier0 alarm.
Influence The uplink receiver sensitivity of the related DTRU is affected.

Tower Amplifier1 power alarm

Alarm level: 4
Alarm Cause The problem is caused by AEM tower amplifier1 alarm.
Influence The uplink receiver sensitivity of the related DTRU is affected.
SWR of AEM HYCOM minor alarm

Alarm level: 3
Alarm Cause The problem is caused by combiner SWR minor alarm.
is eliminated.
eliminated.
SWR of AEM HYCOM major alarm

Alarm level: 2
Alarm Cause The problem is caused by combiner SWR major alarm.


is eliminated.
eliminated.
AEM type alarm

Alarm level: 2
Alarm Cause The problem is caused by AEM type alarm.
AEM Not-in-position alarm

Alarm level: 2
Alarm Cause The problem is caused by AEM not-in-position alarm.
CHP DSP0 of TPU initialization

failure(BTS V2)
Alarm level: 3
Alarm Cause The problem is caused by DSP software or hardware error.

Influence If the TRM/DTRU where DSP0 resides is BCCH carrier, the cell
fails to work normally. If it is not BCCH carrier, the two physical
channels of the TRM/DTRU cannot work and other channels are
not affected.
Handling Flow 1. Download software of DSP again.
2. Reset TRM/DTRU shelf and restart DSP. Check if the alarm is
eliminated.
f If the alarm can be eliminated, it indicates that the failure
is commonly arisen by strong exterior interference, and
the TRM/DTRU unit can work normally.
f If the alarm cannot be eliminated, replace the TRM/DTRU
module.

failure
Alarm level: 4
Influence Two timeslots of the TRM/DTRU cannot work normally. That is,
the two physical channels of the TRM/DTRU are not applicable.
The cell traffic volume is affected.
eliminated.
module.

failure
Alarm level: 4


eliminated.
module.

failure
Alarm level: 4
eliminated.
module.
Uplink of ADC chip initialization

failure
Alarm level: 3
Alarm Cause The problem is caused by uplink ADC chip initialization failure.
Influence The TRM/DTRU is unavailable. If it is BCCH carrier, the normal
operation of the whole cell is affected.
Handling Flow 1. Reset the frequency. Check if the alarm is eliminated.
2. Power on the frequency again. Check if the alarm is
eliminated.
3. Replace the frequency.

Uplink of ADC resource can't be

used
Alarm level: 3
Alarm Cause The problem is caused by unavailability of uplink ADC resource
(uplink data lost suddenly).
Handling Flow 1. Reset the frequency. Check if the alarm is eliminated.
2. Power on the frequency again. Check if the alarm is
eliminated.
3. Replace the frequency.
CIP resource can't be used

Alarm level: 3
Alarm Cause The alarm is caused by uplink/downlink loop data demodulation
failure.
Handling Flow If traffic exists on the TRM/DTRU, it indicates that the
TRM/DTRU is normal. If no traffic exists on the TRM/DTRU or
OMCR fails to originate RF_LOOP test, it indicates that the
TRM/DTRU is damaged. In this case, change the TRM/DTRU
immediately.
Uplink failure
Alarm level: 3
Alarm Cause Errors occur during the receipt of uplink data.
Handling Flow 1. Reset the module.
2. Replace the module if the reset does not solve the problem.

TPU FLASH Memory failure(BTS V2)

Alarm level: 3
Alarm Cause Too many times of FLASH programming leads to read/write error
or software checksum error.
Influence The baseband processing unit fails to obtain the correct software
version from FLASH MEMORY. The whole carrier unit (CU)
cannot work normally.
Handling Flow Reset this CU. Check if the alarm is eliminated.
If the alarm is eliminated, it is inferred that the alarm is
arisen by exterior interference, which makes CPU read data
from FLASH MEMORY. After resetting resumes, the CU could
work normally.
If the alarm is not eliminated, replace TRM module.
Watchdog of TPU CHP DSP0

overflow(BTS V2)
Alarm level: 3
Alarm Cause DSP0 of channel processing unit has no response temporarily.
Influence If DSP0 of channel processing unit has no response temporarily,
the control unit loads and initializes the DSP again. If the alarm
cannot be eliminated, it indicates that the DSP loading cannot
succeed. This fault disables two channels of a carrier unit to
work. If the carrier is BCCH, the whole cell cannot work.
arisen by interior DSP exceptions. After resetting resumes,
the CU could work normally.
If the alarm is not eliminated, start the BCCH switchover
policy on the BSC and replace TRM/DTRU.

overflow
Alarm level: 4



overflow
Alarm level: 4

overflow
Alarm level: 4


Watchdog of FUC overflow

Alarm level: 3
Alarm Cause FUC program has no response temporarily.
Influence The eight channels of the TRM/DTRU are not applicable. If this
fault occurs during a conversation, calls may be dropped.
Handling Flow Reset TPU to solve this problem. If the alarm is not eliminated,
change TRM/DTRU.
CIP of TPU initialization failure

Alarm level: 3
Alarm Cause This alarm is caused by DSP software or hardware error.
Influence The modulation module cannot work. The carrier or cell (when
the carrier is assigned BCCH) cannot work normally.
Handling Flow 1. Download the DSP software again.
2. Reset TRM/DTRU and restart DSP. Check if the alarm is
eliminated.
f If the alarm is eliminated, the DSP initialization failure is
due to strong exterior interference. The TRM/DTRU can
work normally.
f If the alarm is not eliminated, change the TRM/DTRU.
Watchdog of TPU CIP overflow

Alarm level: 4
Alarm Cause DSP program of demodulation module has no response
temporarily.
Influence If DSP program of demodulation module has no response
temporarily, the control unit loads and initializes the DSP again.
If the alarm cannot be eliminated, it indicates that the DSP

loading cannot succeed. This fault disables two channels of a

carrier unit to work. If the carrier is BCCH, the whole cell cannot
work.
Clock alarm for TPU and CMM

Alarm level: 2
Alarm Cause The clock between TPU and CMM is disconnected.
Influence The FUN fails to work. If the FUN is BCCH-TPU, the cell service is
affected.
Handling Flow 1. If this TPU alarm is the only one alarm in the base station,
check if the backplane cables are correctly connected. If yes,
replace TRM/DTRU.
2. If other TPUs or TRM/DTRUs have the same alarm as this
TPU in the base station, check if the CMM board has clock
alarms. If yes, replace the CMM.
TPU power alarm(BTS V2)

Alarm level: 2
Alarm Cause The power module on the TPU board has alarms.
Influence The TRM/DTRU fails to work. If the FTRM/DTRU is BCCH, the cell
service is affected.
Handling Flow Replace the corresponding carrier.
TPU frame No. alarm

Alarm level: 3
Alarm Cause Frame clock FCLK has problem and upper-level frame number
synchronization source CMM has problem.
Influence

The TRM/DTRU fails to work. If the FTRM/DTRU is BCCH, the cell

Handling Flow 1. Check if FCLK of frame number producing point is normal. If
it is directly transported, check the clock frequency, wave
shape; if it is produced by phase locked, check whether the
alarm of lost lock exists. If there are some problems, replace
TRM module.
2. Check the transmission link, that is, transmission clock,
interface chip, the size of error code rate.
3. Check if the superior synchronization source of frame no. has
alarms.
TPU CHP DSP0 initialization failure

Alarm level: 3
Alarm Cause This problem is caused by DSP software or hardware error.
Influence The 16 physical channels of the dual carrier cannot to work
normally. If the DTRU is configured BCCH carrier, the cell service
is affected.
2. Reset DTRU and restart DSP. Check if the alarm is eliminated.
due to strong exterior interference. The DTRU can work
normally.
f If the alarm is not eliminated, change the DTRU.
ADC resource unavailable

Alarm level: 3
Alarm Cause The AD6650 resource is unavailable (uplink data is lost suddenly
and AD6650 initialization fails).
Influence The TRM/DTRU cannot to work normally. If the TRM/DTRU is
BCCH carrier, the cell service is affected.
Handling Flow 1. Reset the module. Check if the alarm is eliminated.
2. Power on the module. Check if the alarm is eliminated.
3. Replace the module.

CHP frame error

Alarm level: 3
synchronization source FUC has problem.
Influence The DTRU fails to work. If the DTRU has BCCH carrier, the cell
TRM module.
alarms.
BURST interrupt error

Alarm level: 3
Alarm Cause The DTRU fails to work. If the DTRU has BCCH carrier, the cell
Handling Flow Measure the clock of BURST interruption to check whether it is
normal or not, if it breaks down, then replace the DTRM module
in time.
TPU FLASH memory failure

Alarm level: 3
or software checksum error.
Influence The baseband processing unit fails to obtain the correct software
version from FLASH MEMORY. The whole carrier unit (CU)


arisen by exterior interference, which makes CPU read data
from FLASH MEMORY. After resetting resumes, the CU could
work normally.
If the alarm is not eliminated, replace DTRU module.
TPU CHP DSP0 watchdog overflow

Alarm level: 3
Alarm Cause Channel processing unit DSP0 has no response temporarily.
Influence If channel processing unit DSP0 has no response temporarily,
policy on the BSC and replace DTRU.
CU intialization failure
Alarm level: 3
Alarm Cause This problem is caused by DSP software or hardware error.
Influence The modulation module cannot work. If the carrier is assigned
SCCH, the carrier or cell cannot work normally.
2. Reset the module and restart DSP. Check if the alarm is
eliminated.
due to strong exterior interference. The module can work
normally.
f If the alarm is not eliminated, change the module.
TPU power alarm


Alarm level: 2
Alarm Cause The power module on TPU board has alarm.
Influence The DTRU cannot work. If the STRU is BCCH, the cell service is
affected.
Handling Flow Replace the module.
TPU's FN alarm
Alarm level: 3
synchronization source FUC has problem.
TRM module.
alarms.
Rx PLL1 unlock
Alarm level: 3
Alarm Cause Clock signal is unstable or TRM Phase-Locked Loop (PLL) fault.
Influence Conversation may fail on the TRM/DTRU.
Rx PLL2 unlock
Alarm level: 3


Tx PLL1 unlock
Alarm level: 3
Tx PLL2 unlock
Alarm level: 3
52M referenced clock PLL unlock

Alarm level: 3

Tx IF PLL unlock
Alarm level: 3
EEPROM resource can't be used

Alarm level: 3
Alarm Cause This alarm is caused by EEPROM fault.
Influence The TRM/DTRU is unavailable.
Handling Flow Replace the TRM/DTRU as soon as possible.
FPGA interface failure

Alarm level: 3
Alarm Cause The communication between DSP and FPGA interface is broken.
Influence The TRM/DTRU is unavailable.
Handling Flow Replace the TRM/DTRU as soon as possible.
PA VSWR alarm(BTS V2)

Alarm level: 3
Alarm Cause The reverse power is too high. It may be caused by the
existence of open circuit or high resistance in output end of PA.
Influence Conversation fails on the TRM/DTRU. The PA is damaged.
Handling Flow 1. Reset TRM/DTRU. Check if the alarm is eliminated.
2. Replace the RF cables from TRM/DTRU to AEM. Check if the

3. Replace TRM/DTRU.
PA overtemperature minor
alarm(BTS V2)
Alarm level: 4
Alarm Cause PA temperature is too high, which is possibly due to PA working
with rated power for a long time, fan not working for a long time,
too high environment temperature, detecting circuit fault, and
other reasons.
Influence The TRM/DTRU can work, but the PA degradation speeds up.
Handling Flow 1. Check if the fan can work normally.
f If no, rectify the faults. Check if the alarm is eliminated.
2. Check if the environment temperature is too high.
f If no, improve the equipment room environment. Check if
3. Reset the module. Check if the alarm is eliminated.
4. The testing circuit may be faulty. Replace the module.
PA overtemperature major
alarm(BTS V2)
Alarm level: 3
other reasons.
Influence The power output of the TRM/DTRU is protectively shutdown. PA
degradation speeds up.


PA output power alarm

Alarm level: 3
Alarm Cause Difference between PA output power and CIP control power is
more than 3 dB. This may be due to PA aging, power detecting
circuit fault, or too narrow detecting threshold.
Influence Conversations may fail on the TRM/DTRU. The power control
fails.
Handling Flow 1. Reset the TRM/DTRU. Check if the alarm is eliminated.
2. Replace the RF cables between TRM/DTRU to AEM. Check if
3. Replace the TRM/DTRU.
PA power overvoltage
Alarm level: 3
Alarm Cause The problem is caused by overvoltage of PA power.
Influence The PA may be damaged. The modulation module protectively
closes the power output.
Handling Flow Check if the PA testing circuit is faulty. If yes, replace the
TRM/DTRU as soon as possible.
PA power lower voltage

Alarm level: 3
Alarm Cause The problem is caused by undervoltage of PA power.
Influence The output power is abnormal.

Downlink checksum error of

DLRC_AL1
Alarm level: 3
Alarm Cause The link between CHP and modulation module is interfered.
Influence Large numbers of error codes exist between CHP and modulation
module. The downlink is faulty. Conversation fails on TRM/DTRU.
Handling Flow 1. Check the signals and time-sequence between CHP and
modulation module. Check if the alarm is eliminated.
DUC chip initialization failure

Alarm level: 3
Alarm Cause The DUC chip is unavailable.
Influence The TRM/DTRU cannot converse normally.
Handling Flow Replace TRM/DTRU.
80w PA VSWR alarm

Alarm level: 3
Alarm Cause The reverse power is too high, which may be due to the
existence of open circuit or high resistance at the output end of
PA.
Influence The TRM/DTRU cannot converse normally. The PA is damaged.
Handling Flow 1. Reset TRM/DTRU. Check if the alarm is eliminated.
2. Replace the RF cables between TRM/DTRU and AEM. Check if
80w PA overtemperature
Alarm level: 4


other reasons.
Influence The TRM/DTRU can work but the PA degradation speeds up.
80w PA overtemperature major

alarm
Alarm level: 3
other reasons.
Influence The TRM/DTRU can work but the PA degradation speeds up.
80w PA output power alarm

Alarm level: 3

Alarm Cause Difference between PA output power and CIP control power is
Influence Conversations may fail on the TRM/DTRU. The power control
fails.
Handling Flow 1. Reset the TRM/DTRU. Check if the alarm is eliminated.
2. Replace the RF cables between TRM/DTRU to AEM. Check if
80w PA power overvoltage

Alarm level: 3
80w PA power lower voltage

Alarm level: 3
80w PA absent
Alarm level: 3
Alarm Cause The PA is not in position.
Influence No output power.

TXIF unlock
Alarm level: 3
Alarm Cause Clock signal is unstable or DTRM Phase-Locked Loop (PLL) is
faulty.
Influence Conversations may fail on the DTRU.
2. Power on the module again. Check if the alarm is eliminated.
TPF unlock
Alarm level: 3
faulty.
TXRF unlock
Alarm level: 3
faulty.
RXRF unlock
Alarm level: 3


faulty.
13 MHz clock lost

Alarm level: 3
Alarm Cause 13 MHz clock receiving is abnormal and 13 MHz clock unit works
abnormally.
3. Check if the socket on the backplane of the corresponding
module is normal. If it is normal, replace the module and
then check if the alarm is eliminated. If it is not exceptional,
replace the backplane and then check if the alarm is
eliminated.
4. Replace the CMB.
60 ms clock lost
Alarm level: 3
Alarm Cause 60 ms synchronization clock receiving is abnormal and 60 ms
synchronization clock unit works abnormally.
eliminated.
4. Replace the CMB.

8M clock of HW lost
Alarm level: 3
Alarm Cause HW 8 MHz clock receiving is abnormal and HW 8 MHz clock unit
works abnormally.
eliminated.
4. Replace the CMB.
8K clock of HW lost
Alarm level: 3
Alarm Cause HW 8 kHz clock receiving is abnormal and HW 8 kHz clock unit
works abnormally.
eliminated.
4. Replace the CMB.
52 MHz clock lost

Alarm level: 3
Alarm Cause RF board 52 MHz clock receiving is abnormal and RF board 52
MHz clock unit works abnormally.


3. Replace the DTRU.
First ADC clock lost

Alarm level: 3
Alarm Cause AD6650 clock receiving is abnormal and AD6650 clock unit
works abnormally.
Second ADC clock lost

Alarm level: 3
Alarm Cause AD6650 clock receiving is abnormal and AD6650 clock unit
works abnormally.
PA power overvoltage alarm

Alarm level: 3
Handling Flow Check if the PA testing circuit is faulty. If yes, replace the DTRU

PA power undervoltage alarm

Alarm level: 3
Handling Flow Check if the PA testing circuit is faulty. If yes, replace the DTRU
PA VSWR alarm
Alarm level: 3
Alarm Cause The reverse power is too high. It may be caused by the
existence of open circuit or high resistance in output end of PA.
Influence Conversation fails on the DTRU. The PA is damaged.
Handling Flow 1. Reset DTRU. Check if the alarm is eliminated.
2. Replace the RF cables from DTRU to AEM. Check if the alarm
is eliminated.
3. Replace DTRU.
PA temperature minor alarm

Alarm level: 4
other reasons.
Influence The DTRU can work but the PA degradation speeds up.

PA temperature major alarm

Alarm level: 3
other reasons.
Influence The DTRU power output is protectively closed. The PA
PA forward power(3db) alarm

Alarm level: 3
Alarm Cause Difference between PA output power and CHP control power is
Influence Conversations may fail on the DTRU. The power control fails.
Handling Flow 1. Reset the DTRU. Check if the alarm is eliminated.
2. Replace the RF cables between DTRU to AEM. Check if the
RTU power alarm

Alarm level: 2

Alarm Cause The RTU power module has faults.

Influence The TRM/DTRU cannot work. If the TRM/DTRU is configured
BCCH, the cell service is affected.
Handling Flow Replace RTU.
RTU power temperature alarm

Alarm level: 3
Alarm Cause RTU temperature is too high, which is possibly due to RTU
working with rated power for a long time, fan not working for a
long time, too high environment temperature, detecting circuit
fault, and other reasons.
Influence The TRM/DTRU power output is protectively closed. The RTU
Handling Flow Check if the fan can work normally and if the environment
temperature is too high. If the fan works normally and the
environment temperature is normal, the alarm persists, the
testing circuit may be faulty. Replace the module.
RTU power output overvoltage alarm

Alarm level: 2
Alarm Cause The problem is caused by overvoltage of RTU power.
Influence The RTU works abnormally.
Handling Flow Replace the RTU board.
RTU power input failure alarm

Alarm level: 2
Alarm Cause The RTU power input is beyond the adjustment range.
Influence The RTU works abnormally.

IQ calibration parameters abnormal

alarm
Alarm level: 2
Alarm Cause This problem is due to wrong IQ calibration parameter.
Influence The RTU collapses.
EAM heat exchanger alarm

Alarm level: 4
Alarm Cause This problem is due to heat exchanger problems, which is
reported by the dry contact of the heat exchanger.
Influence The system security is affected.
Handling Flow 1. Check if the line between EAM and heat exchanger is normal.
2. Check if the heat exchanger can normally supply power.
3. Replace the heat exchanger.
EAM TRX layer fan-4 alarm

Alarm level: 4
Alarm Cause This problem is due to faulty CMB0 heater.
Influence The low temperature startup is affected.
Handling Flow 1. Check if the power supply of CMB0 heater is normal.
2. Check if the heater is damaged. If the heater is damaged,
replace it with a new one.
EAM AEM layer axis-flow fan alarm

Alarm level: 4
Alarm Cause This problem is due to faulty CMB0 heater.

Handling Flow 1. Check if the power supply of CMB1 heater is normal.

2. Check if the heater is damaged. If the heater is damaged,
replace it with a new one.
EAM smoke alarm

Alarm level: 3
Alarm Cause This problem is due to equipment smoke alarm.
Influence The operation security is affected.
Handling Flow Perform on-site check immediately to find fault cause and handle
the fault. After the fault is rectified, reset EAM and resume the
alarm.
EAM waterproof alarm

Alarm level: 3
Alarm Cause This problem is due to equipment water alarm.
Handling Flow Perform on-site check immediately to find fault cause and handle
the fault.
EAM lightning protection alarm

Alarm level: 3
Alarm Cause This problem is due to lightning protector failure.
Handling Flow 1. Check if the connectors of the lightning protector are
correctly connected.
2. Check if the lightning protector is damaged itself. If yes,
change a new one.
EAM backdoor access control alarm

Alarm level: 3

Alarm Cause This problem is due to the alarm of back door being opened.
Handling Flow Perform on-site check immediately to check if the back door is
opened. If yes, close it. If it is not opened, check if the door
status switch is damaged.
EAM frontdoor access control alarm

Alarm level: 3
Alarm Cause This problem is due to the alarm of front door being opened.
Handling Flow Perform on-site check immediately to check if the front door is
opened. If yes, close it. If it is not opened, check if the door
status switch is damaged.
EAM PWR monitoring unit alarm

Alarm level: 4
Alarm Cause This problem is due to PWR monitoring unit alarm.
Handling Flow 1. Check if the line between PWR and EAM is normal.
2. Check if the power monitoring module is normal.
3. Check if other power alarms are generated.
EAM heat exchanger electric heater

alarm
Alarm level: 3
Alarm Cause This problem is due to FIB heater alarm.
Handling Flow 1. Check if the power supply of the FIT heater is normal.
2. Check if the heater is damaged. If it is damaged, replace it
with a new one.

EAM heat exchanger control board

alarm
Alarm level: 3
Alarm Cause This problem is due to heat exchanger control board alarm.
Influence The normal operation of the equipment is affected.
Handling Flow 1. Check if the lines between EAM and heat exchanger are
normal.
2. Check if the power supply of the heat exchanger is normal.
3. Replace the heat exchanger control board.
EAM heat exchanger external

circulation fan 2 alarm
Alarm level: 3
Alarm Cause This problem is due to heat exchanger external circulation fan 2
alarm.
Handling Flow 1. Check if the lines between the heat exchanger control board
and the fan are normal.
2. Replace the fan.
EAM heat exchanger external

Alarm level: 3
Alarm Cause This problem is due to heat exchanger external circulation fan 1
alarm.
2. Replace the fan.

EAM heat exchanger internal

Alarm level: 2
Alarm Cause This problem is due to heat exchanger internal circulation fan 2
alarm.
2. Replace the fan.
EAM heat exchanger internal

Alarm level: 2
Alarm Cause This problem is due to heat exchanger internal circulation fan 1
alarm.
2. Replace the fan.
EAM heat exchanger 485

communication alarm
Alarm level: 3
Alarm Cause This problem is due to alarm of communication between EAM
and heat exchanger.
Influence The alarm reporting of heat exchanger is affected.
Handling Flow 1. Check if the lines between the EAM and heat exchanger are
normal.
2. Check if the power supply of the heat exchanger is normal.
3. Replace the heat exchanger control board.

EAM temperature alarm

Alarm level: 3
Alarm Cause This problem is due to overtemperature of network internal
environment.
Handling Flow 1. Check if the fan on the frequency layer is running normally.
2. Check if the heat exchanger is running normally.
EAM TRX layer mixed-flow fan 1

alarm
Alarm level: 3
Alarm Cause This problem is due to mixed-flow fan 1 damage alarm.
Influence Normal operation of the frequency module is affected.
Handling Flow 1. Check if the line between the FNIB and fan is normal. If not,
change the line.
2. Check if the fan is faulty. If yes, change the fan.

alarm
Alarm level: 3
change the line.

alarm

Alarm level: 3
change the line.
Power undervoltage alarm

Alarm level: 2
Alarm Cause The external power voltage is lower than the lower limit.
Influence The system transmit power is abnormal, and thus the system
Handling Flow Restore the external power supply as soon as possible.
Inner fan 2 alarm (for M8202)

Alarm level: 4
Influence The temperature in rack is increased.
faulty.
3. Check if the fan cables have faults and if board-to-board


exceptional.
DFCM/FNCB.
Inner fan 1 alarm (for M8202)

Alarm level: 4
faulty.
3. Check if the fan cables have faults and if board-to-board
exceptional.
DFCM/FNCB.

Outer fan 2 and fan 4 alarm (for

M8202)
Alarm level: 4
Handling Flow 1. Check the alarm line and rectify the fault.
2. Check the fan and rectify the fault.
3. Check if dTPB alarm collection circuit is correct. If it is
incorrect, replace the dTPB board.
Outer fan 1 and fan 3 alarm (for

M8202)
Alarm level: 4
3. Check if dTPB alarm collection circuit is correct. If it is
incorrect, replace the dTPB board.
Rack temperature minor alarm

Alarm level: 4
Alarm Cause The fan is faulty or the module temperature is too high.
Influence The TRM/DTRU is over-temperature and thus the performance
indices are affected.
Handling Flow Check if the environment temperature meets the requirement.
If yes, check the module working status and solve the
problem.
If no, improve the working environment.

Rack temperature major alarm

Alarm level: 3
Alarm Cause The fan is faulty or the module temperature is too high.
Influence The equipment is damaged and thus the performance indices are
affected.
Handling Flow Check if the environment temperature meets the requirement.
If yes, check the module working status and solve the
problem.
If no, improve the working environment.
Layer 3 fan 1 alarm (for M8206)

Alarm level: 4
Influence The rack temperature is increased, which reduces device
performance and service life.
3. Check if RTU alarm collection circuit is correct. If it is
incorrect, replace the TRM/DTRU.

Alarm level: 4


Alarm level: 4

Alarm level: 4

Alarm level: 4


Alarm level: 4

Alarm level: 4

Alarm level: 4


Alarm level: 4
FR device failure
Alarm level: 2
Alarm Cause The BRCH works abnormally. N392 errors are detected in the
last N393 STATUS ENQUIRY events.
Influence The BRCH on Gb interface is broken.
Handling Flow 1. Check if the E1 interface of the BRCH has alarms incessantly.
If yes, check the transmission equipment and rectify
transmission alarms.
2. Check if E1 device is normal through a selfloop test at the
local. If it is abnormal, change the E1 line and check if the
alarm is eliminated. If it is normal, then contact SGSN
maintenance personnel to perform peer-end selfloop. Check
if the peer end is normal. If no, then contact peer-end
equipment maintenance personnel for troubleshooting. If the
peer end is normal, go to step 3.
3. Check if the E1 frame format configurations on BSC and
SGSN are consistent.
4. Check if the E1 indicator on GIPB is normal (blinks). If it is
normal, go to step 5. If not, change the backplane and check
5. Check if the BRCH parameter configuration is the same as
the corresponding parameters on SGSN. If they are
inconsistent, change the parameters to be consistent. If they
are consistent, go to step 6.
6. Change GIPB. Check if the alarm is eliminated.

FR congestion
Alarm level: 3
Alarm Cause In case of an intermediate Frame Relay network, the number of
a frame with a BECN bit set to "1" is more than or equal to the
number of a frame with a BECN bit set to "0" in T interval.
Influence Quality of some users’ PS service is reduced.
Handling Flow Add BRCG links or BRCH timeslots.
MSC overload control alarm at FUC

mode
Alarm level: 3
Alarm Cause MSC sends overload message. BSC starts FUC flow control.
Influence Some users cannot be accessed.
Handling Flow BSC can automatically control the flow. No operation is required.
CPU overload control alarm at FUC

mode
Alarm level: 2
Alarm Cause CPU load exceeds the threshold of flow control in the module
parameter setting.
Handling Flow 1. Check alarm details. If the flow control level is 6 or lower
than 6, observe for three minutes and check if the alarm is
eliminated. If the flow control level is higher than 6, go to
step 2.
2. Block some cells through EMS to prevent the CPU load from
rising. Check if the alarm is eliminated. After the alarm is
eliminated, unblock the cells.

Signaling point congestion control

alarm at FUC mode
Alarm level: 3
Alarm Cause MSC sends signaling congested message. BSC starts FUC flow
control.
MSC overload control alarm at SYS

mode
Alarm level: 3
Alarm Cause MSC sends overload message. BSC starts system message flow
control.
CPU overload control alarm at SYS

mode
Alarm level: 2
Alarm Cause CPU load exceeds the threshold of flow control in the module
parameter setting.
step 2.
2. Block some cells through EMS to prevent the CPU load from
rising. Check if the alarm is eliminated. After the alarm is
eliminated, unblock the cells.

Signaling point congestion control

alarm at SYS mode
Alarm level: 3
Alarm Cause MSC sends signaling point congestion message. BSC starts
system message flow control.
CCCH overload control

Alarm level: 3
Alarm Cause CS services of some users under the cell cannot be accessed.
step 2.
2. Check if the cell parameter RACH overload level threshold is
correct.
3. Check the traffic statistics. Consider expanding overloaded
sites or using traffic sharing.
PCCCH overload control

Alarm level: 3
Alarm Cause Users applying for CS service are excessive.
Influence CS services of some users under the cell cannot be accessed.
step 2.
2. Check if the cell parameter RACH overload level threshold is
correct.
3. Check the traffic statistics. Consider expanding overloaded
sites or using traffic sharing.

NSVC failure alarm

Alarm level: 2
Alarm Cause NSVC link is faulty.
Influence For single-NSVC link configuration, the PS service is interrupted.
For multiple-NSVC link configuration, the bandwidth is reduced.
Handling Flow 1. Check if FR device alarm is generated. If yes, handle the
alarm by referring to “FR device failure”. If no, go to step 2.
2. Check if NSVC configuration parameters are consistent with
the corresponding parameter in SGSN.
alarm of CRC verifying of power

amplifier parameters error
Alarm level: 2
Alarm Cause The verifying of power amplifier parameters has error.
Influence The power amplifier has no calibration curve and the RF index is
affected.
Handling Flow 1. Reset the corresponding module. Check if the alarm is
eliminated.
3. Change the module.
DSP initialization failure

Alarm level: 2
Alarm Cause The problem is caused by DSP software or hardware fault.
Influence The system can not operation normally.
2. Reset the DSP. Check if the alarm is eliminated.
3. Change the HBTS.

Tx PLL unlock
Alarm level: 3
Alarm Cause The clock signal is unstable, or the TRM/DTRU phase-locked loop
is faulty.
Influence S8001 cannot converse.
3. Change the module.
FLASH memory fault

Alarm level: 3
or checksum error.
Influence The software version cannot be downloaded or loaded.
Important HBTS logs cannot be recorded. The HBTS cannot work
normally.
Handling Flow Reset the HBTS and check if the alarm is eliminated. If the alarm
is eliminated, it is inferred that the alarm is arisen by exterior
interference, which makes CPU read data from FLASH MEMORY.
After resetting resumes, the CU could work normally. If the
alarm cannot be eliminated after being reset, replace HBTS
module.
Run abnormity of DSP

Alarm level: 3
Alarm Cause DSP has no response temporally or program runs abnormally.
Influence If DSP is reset, the programs are loaded and initialized again. If
this alarm occurs frequently, the HBTS cannot work normally.
Handling Flow Reset the HBTS and check if the alarm is eliminated. If the alarm
is eliminated, it is inferred that the alarm is arisen by interior
interference, which makes CPU read data from FLASH MEMORY.
After resetting resumes, the CU could work normally. If the
alarm cannot be eliminated after being reset, replace the HBTS
module.

FPGA interface fault

Alarm level: 3
Alarm Cause The interface between DSP and FPGA is broken.
Influence S8001 cannot be used normally.
Handling Flow 1. Load the EPGA again and reset HBTS. Check if the alarm is
eliminated.
2. Replace the HBTS.
CHP frame fault

Alarm level: 3
Alarm Cause Frame number processing is interrupted.
Influence The frame numbers are out of order.
TRM module.
alarms.
Wrong receive channel of RF

Alarm level: 2
Alarm Cause The receive channel is faulty and cannot receive uplink signals.
Influence Uplink signal processing cannot be performed.
Handling Flow Download EPGA and DSP versions again. Configure the system
parameters again.

Wrong parameter configuration for

EEPROM
Alarm level: 3
Alarm Cause This problem is caused by EEPROM hardware faults or invalid
parameters written to EEPROM. As a result, EEPROM RF
parameters cannot be read normally.
Influence The system cannot normally read RF parameters from EEPROM.
Handling Flow Check if RF parameters are written to EEPROM. If yes, it
indicates that decoding incurs error and EEPROM and peripheral
are damaged. In this case, change the hardware device. If no RF
parameter is written, write the parameters to EEPROM through
command interface.
RF channel and HTRG board

unconformity
Alarm level: 2
Alarm Cause The board hardware does not support the preset frequency point.
Influence S8001 cannot work normally.
Handling Flow 1. Replace the HTRG/HTRU board.
2. Change the frequency point range.
OMP reboot alarm

Alarm level: 3
Alarm Cause OMP is reset.
Influence O&M is affected during OMO maintenance. This alarm has no
effect on the service.
Handling Flow OMP reports the alarm and restores it when being reset. No
handling operation is required.
TRX Man Block


Alarm level: 3
Alarm Cause The TRX is blocked manually.
Influence The TRX exits service.
Handling Flow Unblock the TRX.
Resource cannot be used of RF

Channel
Alarm level: 2
Alarm Cause Automatic frequency resource search fails.
Research times out.
iBSC cannot provide frequency resource.
Influence The TRX exits service.
Handling Flow Specify the frequency point or change the research range.
SYNCLK locked fail alarm

Alarm level: 4
Alarm Cause The synchronization clock cannot be locked after a long time.
Influence CMM/CMB active and standby switchover fails.
Handling Flow Check if the BSC SYNCLK runs normally. If the standby board is
available and it works normally, switch to the standby board. If
the standby board is unavailable, reset the board.
Status of TX1 filter alarm

Alarm level: 2
Alarm Cause The TX1 channel does not finish adjustment or the loss is
greater than 5 dB.
Influence The transmission is affected.
2. Replace the FCU. Check if the alarm is eliminated.


Alarm level: 2
greater than 5 dB.

Alarm level: 2
greater than 5 dB.

Alarm level: 2
greater than 5 dB.
FCU power undervoltage alarm

Alarm level: 2
Alarm Cause The +12V power is under voltage.
Influence The PCU works abnormally.
Handling Flow 1. Check if the FCU/FUC power indicator displays alarm.

f If alarm is displayed, go to step 2.

f If no alarm is displayed, go to step 3.
2. Check if the 12V power of the slot corresponding to FCU/FUC
is normal.
f If it is abnormal, replace FCU/FUC.
f If it is normal, go to step 3.
3. Change the frequencies of the corresponding layer one by
one. Check if the alarm is eliminated.
4. Replace the backplane. Check if the alarm is eliminated.
FCU minor alarm

Alarm level: 3
Alarm Cause The problem is caused by FCU digital board assistant circuit
alarm.
Influence The FCU works abnormally.
Handling Flow Keep observation. The FCU need not be replaced unless the
normal service is affected.
Hard disk initialization failure

Alarm level: 3
Alarm Cause The hard disk is physically damaged.
The hard disk is used for a long time and thus it switches to
the read/write protection state.
The hardware is not formatted before delivery.
Influence Operations related to hard disk fail.
Handling Flow Replace the board.
The clock alarm about transmission

of CCI board Abis-E1
Alarm level: 3
Alarm Cause The reference source is lost.

Abis-E1 transmission clock phase-locked loop loses lock.

Influence If the Abis-E1 interface is used for transmission, the
communication with BSC is affected. If FE interface is used, the
communication is not affected.
Handling Flow Check the Abis-E1 interface.
The local working clock alarm of CCI

board
Alarm level: 3
Alarm Cause The local working clock is faulty.
Influence The local board works abnormally.
Handling Flow Switch to the standby board. If necessary, replace the CCI board.
The clock alarm about transmission

of CCI board 13M
Alarm level: 3
Alarm Cause The reference source is lost.
Abis-E1 transmission clock phase-locked loop loses lock.
Influence The BTS internal transmission link is broken. The frame numbers
are out of order.
Handling Flow Check the reference source or replace the CCI board.
CCI opposite board alarm

Alarm level: 4
Alarm Cause The opposite board is not in position or the clock is faulty.
Influence The opposite board cannot work normally. The active and
standby switchover fails.
Handling Flow Replace the CCI board.

IQ FPGA internal clock alarm

Alarm level: 3
Alarm Cause The IQ EPGA internal source clock is lost.
Influence The IQ EPGA cannot work normally.
Handling Flow Check if CLK FPGA is working normally.
IQ FPGA light interface alarm

Alarm level: 3
Alarm Cause The IQ EPGA optical interface link is exceptional.
Influence The alarm optical interface cannot transmit data.
Handling Flow Replace the optical module or optical fiber.
IQ FPGA LVDS interface alarm

Alarm level: 3
Alarm Cause The LVDS interface is exceptional.
Influence The alarm LVDS interface cannot transmit data.
Handling Flow Check the backplane and the SERDES chip on the corresponding
GBP board.
IQ FPGA internal data alarm

Alarm level: 3
Alarm Cause The format of internal data is abnormal.
Influence IQ data transmission fails.
Handling Flow Find out the cause of data format error.
13M,61.44M clock lost alarm


Alarm level: 3
Alarm Cause The clock is lost.
Influence The clock cannot work. Conversation fails on the DTRU.
Handling Flow 1. Reset CCI. Check if the alarm is eliminated.
2. Reset GBP. Check if the alarm is eliminated.
3. Rectify the CCI clock source fault. Check if the alarm is
eliminated.
4. Rectify the LVDS link fault of GBP. Check if the alarm is
eliminated.
60ms clock lost alarm

Alarm level: 3
Alarm Cause The FR or FN has error.
Influence Frames cannot be formed on the downlink. Conversation may
fail on the DTRU.
eliminated.
eliminated.
26MHz and 52MHz lost of clock

alarm
Alarm level: 3
Alarm Cause The phase-locked loop is unlocked.
Influence The 26M clock is unlocked, and then FPGA on the downlink
cannot receive the data from DSP.
The 52M clock is unlocked, and then data from uplink cannot
be received.
eliminated.

4. Rectify the LVDS link fault of GBP 13M clock. Check if the
alarm is eliminated. If no fault exists, it indicates that the
FPGA phase-locked loop is invalid. In this case, replace the
board.
the failure examination alarm of the

60ms uplink frame
Alarm level: 3
Alarm Cause The 60ms super frame header is not detected on the uplink.
Influence The uplink can neither normally decode frames nor send timeslot
interval to DSP.
eliminated.
eliminated.
checking block data error alarm

Alarm level: 4
Alarm Cause The frame data has error.
Influence Communication message is wrong during transmission.
Handling Flow None.
up link LVDS SERDES lost lock

alarm
Alarm level: 3
Alarm Cause SERDES loses lock.
Influence The uplink cannot normally receive decoded frames.

3. Check if the format of data from CCI to LVDS is correct.

FN error alarm
Alarm level: 4
Alarm Cause Downlink framing is affected.
Influence The frame number from CCI has error.
3. Rectify CCI hardware faults. Check if the alarm is eliminated.
eliminated.
receiving channel frequent alarm

Alarm level: 3
Alarm Cause Clock signals are unstable, or RRU phase-locked loop is faulty.
Influence Conversation fails on the RRU.
Handling Flow Replace the RRU as soon as possible.
transmiting channel frequent alarm

Alarm level: 3
Alarm Cause The crystalloid is faulty.
Influence The PLL is unstable.
Handling Flow Replace hardware.
the lost alarm of 60ms

Alarm level: 3
Alarm Cause The RRU clock unit works abnormally.

Influence Normal communication fails.

Handling Flow Check if the optical fiber between RRU and BBU is normal. If no,
change the optical fibers.
output power less than 6DB

Alarm level: 3
Alarm Cause The duplexer output power is less than 6 dB.
Influence The duplexer cannot work normally.
Handling Flow None.
HYCOM major alarm

Alarm level: 2
Handling Flow Change the AEM and reset RRU.
the input power is abnormal

Alarm level: 3
Alarm Cause The power input is abnormal.
Influence The RRU cannot work abnormally.
Handling Flow Replace the power module.
out of power alarm

Alarm level: 3
Alarm Cause The RRU is out of power.
Influence The RRU cannot work abnormally.
Handling Flow Check the power module. If the power module is faulty, replace
it with a new one.

the lost of signal of the light port 4

alarm
Alarm level: 3
Alarm Cause The optical link between RRU and BBU is broken.
Influence Conversation fails.
Handling Flow Check if the optical fiber between RRU and BBU is normal. If it is
abnormal, replace it.

alarm
Alarm level: 3
abnormal, replace it.
light port 2 error,Loss of Frame

alarm
Alarm level: 3
Alarm Cause The BER of data transmitted through optical fibers is larger than
10E-6.
Influence The RRU cannot work normally.
Handling Flow None.

alarm
Alarm level: 3


not normal, replace it.
light port 1 error,Loss of Frame

alarm
Alarm level: 3
Alarm Cause The BER of data transmitted through optical fibers is larger than
10E-6.
Influence The RRU cannot work normally.
Handling Flow None.
FR device failure
Alarm level: 3
Alarm Cause Too many times of FLASH programming leads to read/write error.
Influence The system fails to load and read any version.
Handling Flow This problem cannot be manually solved. It belongs to FLASH
chip fault. To clear the alarm, replace the RRU.
the version checking CRC error

alarm
Alarm level: 3
Alarm Cause The version saved on BBU has error.
Data error occurs during version transmission.
Influence The system fails to load the version.
Handling Flow None.
Diversity antenna lost

Alarm level: 2

Alarm Cause Two density antennas receive signals. One of them is abnormal.
Influence The density reception cannot be realized and thus the sensitiviey
and coverage are affected.
Handling Flow Check the RF receive channel.
Diversity antenna identical

Alarm level: 2
Alarm Cause The two antennas of the two densities are wrongly corrected.
Influence The antennas are identical and thus cannot work.
Handling Flow Check the antenna connection.
A Interface Resource Statistics

Alarm
Alarm level: 2
Alarm Cause The resource blockage rate on OMP A interface exceeds the
threshold.
Influence The CS service access is affected in long term. Calls are difficult
to be given or connected. Traffic volume is affected.
Handling Flow Check if the A interface circuit is normal through the dynamic
data management function of EMS.
1. Check if the E1 cables on DTB or SPB/SPB2 board at A
interface are normally connected.
2. Check the MSC is congested or not configured. If it is
abnormal, ask MSC maintenance engineers for
troubleshooting.
3. Check if PCM is blocked. If yes, unblock it.
4. Check if the DRTB/DRTB2 board works normally. If no, reset,
pull out and plug in, or replace the board.
5. Check if the PCM number at the BSC side is consistent with
that at the MSC side. If no, modify the PCM number at the
BSC side to be consistent with that at the MSC side. Check if

NSVC Resource Statistics Alarm

Alarm level: 2
Alarm Cause The NSVC resource blockage rate on OMP exceeds the threshold.
Influence The PS services of some cells are unavailable.
Handling Flow 1. Check if FR device fault alarms are generated continuously.
If yes, follow the handling suggestion mentioned in “FR
Device Failure”. Then, check if the alarm is eliminated.
2. Check If the NSVC data configuration is consistent with that
at the SGSN side. If no, modify the NSVC data configuration.
3. Check if PCM is blocked. If yes, unblock it.
4. Check if manually blocked NSVC exists. If yes, manually
unblock it.
5. Check if the PCM number at the BSC side is consistent with
that at the MSC side. If no, modify the PCM number at the
BSC side to be consistent with that at the MSC side. Check if
TCH Resource Statistics Alarm

Alarm level: 2
Alarm Cause The number of consecutive assignment failures exceeds the
threshold.
Influence Calls are difficult to be given or connected. Traffic volume is
affected.
Handling Flow 1. Check if the channel is manually blocked. If yes, manually
unblock it.
2. Check if the board is normal. If no, reset, pull out and plug in,
or replace the board.
3. Check if the cell is normal and if the interference is severe. If
yes, optimize the network.
Assignment Failure
Alarm level: 2
Alarm Cause The TCH resource blockage rate on CMP exceeds the threshold.

Influence Calls are difficult to be given or connected. Traffic volume is

affected.
Handling Flow 1. Check if the channel is manually blocked. If yes, manually
unblock it.
2. Check if the board is normal. If no, reset, pull out and plug in,
or replace the board.
3. Check if the cell is normal and if the interference is severe. If
yes, optimize the network.
Communication Alarms
Exceptional Connection Setup
Alarm level: 1
Alarm Cause The communication between the EMS and NE is broken. The NE
is disconnected from the OMC server.
Influence Messages related to the device cannot be reported normally.
Handling Flow Check if the link is normal.
Remarks Link alarm
Trunk Frame Loss

Alarm level: 2
Alarm Cause Two ends have no common ground.
The clocks are not synchronous.
Transmission equipment has a failure.
Influence The trunk signals received by the trunk are interrupted.
Handling Flow 1. Check if the equipment cable impedance matches, if the
board's DIP switch matches the cable, and if the rear board's
jumper cap matches the cable.
f If no, reset the board's DIP switch or rear board's jumper
cap. Then, check if the alarm is eliminated.

2. Use a multimeter to detect if the grounding signal of the

equipment from both ends is reliable.
f If no, make the grounding signal of both ends reliable.
3. Check if the CLKG/ICM board locks the clock (TRACE
evergreen)
f If no, lock the clock. Check if the alarm is eliminated.
4. Check if the clock references of two matching NEs or nodes
are consistent.
f If no, modify the clock benchmark, ensuring the clock
references of two matching NEs or nodes are consistent.
5. Ask maintenance personnel for transmission equipment to
check if the transmission equipment is exceptional. If there is
any exception, locate the fault through step-by-step physical
diagnosis and circulating test.
Trunk Signal Loss

Alarm level: 2
Alarm Cause The wire E1 is not connected or wrongly connected on DDF.
E1 line breaks.
The upstream equipment is exceptional.
Handling Flow 1. Check if E1 on DDF is connected and then check if the alarm
is eliminated.
2. Make a self-loop E1 on the local end. Check if the alarm is
eliminated.
f If the alarm is eliminated, refer to the suggestions on
upstream equipment troubleshooting.
f If the alarm is not eliminated, go to step 3.
3. Replace the board. End the alarm handling.
Trunk Alarm Indication

Alarm level: 2

Alarm Cause The upstream equipment is exceptional.

Handling Flow Check and clear the E1 alarms corresponding to the upstream
equipment.
Trunk Multi-frame Loss

Alarm level: 2
Alarm Cause The frame formats at both ends are inconsistent.
Handling Flow Check if the frame format for the two matching ends is
consistent. If it is not consistent, configure the same one for the
two ends.
Far-End CRC Multi-frame Alarm

Indication
Alarm level: 2
Alarm Cause The base frame and CRC multi-frame are not synchronized.
Handling Flow Check if the frame format for the two matching ends is
consistent. If it is not consistent, configure the same one for the
two ends.
Far End Alarm

Alarm level: 1
Alarm Cause Something is wrong with the signals sent by the local end or
with the intermediate transmission equipment. All kinds of faults
that may result in LOS, AIS, or LOF on the peer end would
probably cause this alarm.
Handling Flow At the peer end, at least one alarm among LOS, AIS, or LOF
may be generated. Check and record the peer-end alarm. Check
if intermediate transmission equipment for this trunk link has
faults. If fault occurs, clear the related fault.

Communication Link between Active

and Standby Boards Off
Alarm level: 3
Alarm Cause Active and standby boards are configured on OMC, but no
standby board is physically plugged.
The standby board exists, but the communication link
between the active and standby boards is broken.
Influence The active and standby boards cannot communicate.
Handling Flow 1. Check if the active and standby boards are configured on
OMC. 1
f If it is active/standby boards configuration, check if there
is a standby board physically plugged. If the standby
board is not in position, insert the standby board and
then power it on. Check if the alarm is eliminated.
f If the standby board is physically plugged, go to step 2.
2. Check if the standby board runs abnormally. If it runs
abnormally, replace it. Power it on and then check if the
3. Check the control-layer communication link and troubleshoot
the fault according to the alarm (relating to control-layer
communication interrupt) handling suggestions.
Incorrect FE Routing Connection

Alarm level: 1
Alarm Cause On RUIM1 rear board, FE-C3/4 is taken as the FE routing
port and receives link detection packet.
The ports on the peer end connected with a couple of ports
on the local board are not coupling ports.
Influence The control plane fails to be routed, or the ports are switched
cyclically.
Handling Flow 1. Check if FE-C3/4 is used as the routing port when UIM in the
BUSN/BGSN shelf adopts the RUIM1 rear board for FE
routing.
f If FE-C3/4 is used as routing port, the system generates
an alarm. Reuse FE-C1/2 as the routing port and then
wait for 1 second to see if the alarm is eliminated.
f If FE-C3/4 is not used as the routing port, the alarm will
need no handling. End alarm handling.

2. Check if the ports on the peer end connected with a couple of

ports on the local board are coupling ports.
f If they are coupling ports, the alarm will need no
handling. End alarm handling.
f If they aren't coupling ports, that couple of ports on the
local end will generate the alarm. Reconnect this pair of
FE lines, pay attention that both ends of their ports
should be in couples. After reconnect the FE lines, check
Remarks The ports at both ends of FE lines must be in couples, for
example:
When connecting CHUB to UIM, the connection line led from
the CHUB rear board RCHUB1/RCHUB2 must be connected
from consecutive couple of ports (port1/port2, port3/port4,
port5/port6, port7/port8) to coupling ports on the UIM rear
board.
When connecting UIM to UIM/CHUB, the ports on UIM rear
board used for connection must be in couples. For example,
if adopting the RUIM1 rear board, two FE-C1/2 ports must be
used as FE routing ports. If adopting the RUIM2/RUIM3 rear
board, the consecutive couple of ports like FE1/FE2, FE3/FE4,
FE5/FE6 must be used as FE routing ports.
Board HW Error
Alarm level: 2
Alarm Cause NE clock is exceptional.
The TDM connection chip is exceptional.
The board hardware is faulty.
The backplane hardware is faulty.
Influence The CS domain service may be interrupted.
Handling Flow 1. Check the HW number configured for this board and
neighboring slots to see if the number exceeds the number
of physical slots.
f If the number is not excessive, modify the configuration
and synchronize the data. Reset the board. Check if the
f If the number is excessive, go to step 2.
2. Check if there are any vacant slots. Replace the configured
slot. Check if the alarm is eliminated.

Communication between
environment monitoring board and
OMP board abnormal
Alarm level: 2
Alarm Cause The RS485 communication link between PWRD and OMP is
broken.
There is no connection between PWRD and OMP, or the
connection has a failure.
The rack number configured for the rack in which this PWRD
locates is not consistent with the rack number set by PWRD
DIP switches.
Influence The environment status cannot be monitored.
Handling Flow 1. Check if the connection between PWRD and OMP is correct.
f If it is not correct, correctly connect OMP and PWRD.
f If it is correct, go to step 2.
2. Check if the connection cables between PWRD and OMP have
faults.
f If yes, replace the cables. Check if the alarm is
eliminated.
3. Check if the configured rack number is consistent with the
value of PWRD DIP switches. If no, adjust the value of PWRD
DIP switches. Check if the alarm is eliminated.
RAWMACIP Channel
Communication Exception
Alarm level: 2
Alarm Cause The packet loss rate of the internal RAWMACIP channel of the
board exceeds the threshold (25% by default).
Influence The RAWMACIP channel cannot transmit data normally.

test pack check abnormal

Alarm level: 2
Alarm Cause The ATM communication in the board is abnormal.
Influence The media plane communicates abnormally.
Handling Flow 1. Restart the board. Check if the alarm is eliminated.
MAC Address Conflict Exists in

Boards of Same Shelf
Alarm level: 1
Alarm Cause The board is not inserted in position.
The DIP switch setting is changed.
Other causes.
Influence The board cannot start normally or conflicts occur on the control
plane.
Handling Flow 1. Check if the DIP switch setting is changed and if the board is
restarted after the change.
f If the DIP switch setting is not changed, go to step 2.
f If the DIP switch setting is changed or the board is not
started after the change, restart the boar and record the
fault details. Check if the alarm is eliminated.
2. Pull out and plug in the board again. Check if the alarm is
eliminated.
IPMAC Conflict When OSS Detects

Control Plane
Alarm level: 2
Alarm Cause The board is not inserted in position.
The DIP switch setting is changed.
Other causes.
Influence

The board cannot start normally or conflicts occur on the control

plane.
Handling Flow 1. Pull out and plug in the board again. Check if the alarm is
eliminated.
2. Check if the DIP switch setting is changed and if the board is
restarted after the change.
f If the DIP switch setting is not changed, go to step 2.
f If the DIP switch setting is changed or the board is not
started after the change, restart the boar and record the
fault details. Check if the alarm is eliminated.
3. Check if the engineering network has potential risks. The
control plane of the NE and other NEs should be on the same
plane. If necessary, modify the networking. Check if the
Remarks OSS refers to the operating system.
dualhome office block

Alarm level: 3
Alarm Cause The dual-home office is switched to be slave. The DH process
blocks the office.
Influence The messages fail to be transceived.
Handling Flow 1. Check if the dual-home office is slave.
f If yes, it is a normal phenomenon. End the alarm
handling.
2. Perform dynamic management on dual home office. Unblock
the office. Check if the alarm is eliminated.
dualhome link block

Alarm level: 3
blocks all the links of an office.


handling.
2. Perform dynamic management on related links. Unblock the
links. Check if the alarm is eliminated.
dualhome association block

Alarm level: 3
blocks all the associations of an office.
handling.
2. Perform dynamic management on related associations.
Unblock the associations. Check if the alarm is eliminated.
Recive bad packet

Alarm level: 3
Alarm Cause The state of the external port is abnormal.
The hardware is bad.
The 2400 card don't plug well.

Other problems result in the GE receipt error.

Influence The board cannot normally receive data packet. This makes the
service that the board bears unstable.
Handling Flow 1. Connect to the alarm board ingress, input the command
McsGliPmShow.
f If the printed message contains only “Port *** Pkts with
Error RSW” and the corresponding statistic item is not
zero, go to step 2.
f If the printed message contains other statistic item not
equal to zero, the problem is caused by software. Ask
R&D engineers to locate.
2. If the problem is determined as a hardware problem,
perform the following steps:
i. Check the physical devices connected to the external port,
for example, optical fibers and optical modules. Ensure
that the network works normally through monitoring
device status or replacing devices.
ii. Reset the board. Check if the alarm is eliminated.
iii. Pull out and plug in the board again.
iv. Pull out and plug in the 2400 card again. Check if the
v. Change the slot of the board. Check if the alarm is
eliminated.
vi. Ask hardware engineers to locate the problem and
replace the board. Check if the alarm is eliminated.
Faulty Frames Received by

FE/GE/ATM/MP/POS/E1 Port
Alarm level: 3
Alarm Cause Network status of FE/GE/ATM/MP/POS/E1 port is abnormal.
Board hardware is faulty.
Other faults of the board cause faulty FE/GE/ATM/MP/POS/E1
exception.
Network processor sub-card which has worked normally is
loose.
Handling Flow 1. Pull out and plug in the optical fibers/cables. Check if the

2. Replace the optical fibers/cables. Check if the alarm is

eliminated.
3. Restart the board. Check if the alarm is eliminated.
eliminated.
Faulty Frames Received by Internal

Switching Interface Faulty
Alarm level: 2
Alarm Cause The board switching chips are physically faulty.
The PSN board in the same shelf is exceptional.
The network processor subcard is loose.
Handling Flow 1. Restart the board (For the Release version, the board
restarts automatically). Check if the alarm is eliminated.
eliminated.
HDLC unavailable
Alarm level: 2
Alarm Cause This alarm is generated when an HDLC is created. It
disappears when the link gets through.
The link is broken.
Influence If the HDLC is the last available HDLC that is bound to the UID,
then all the services of the corresponding UID are interrupted. If
the HDLC is not the last available HDLC that is bound to the UID,
the service traffic on the corresponding UID is reduced.
Handling Flow 1. Check the settings of HDLC channel to see whether the E1/TI
of this HDLC and its time slots match the peer end.
f If no, modify HDLC setting and make it accordant with
the peer end HDLC.
2. Check if the physical connection is correct.

f If no, adjust the physical connection to make it consistent
with the peer end. Check if the alarm is eliminated.
3. Check if the E1/T1 lines have quality problems.
f If yes, change the E1/T1 lines. Check if the alarm is
eliminated.
4. Record the statistic data of messages received by and sent
from the HDLC.
UID unavailable
Alarm level: 2
Alarm Cause This alarm is generated when a UID is created. It disappears
when the link gets through.
The link is broken.
Influence All the services on the UID are interrupted.
Handling Flow When at least one HDCL on UID becomes available, the UID can
be used. In this case, the alarm disappears automatically. To
make the HDLC available, follow the suggestions in “HDLC
unavailable.”
UID unavailable
Alarm level: 2
The link is broken.
unavailable.”

Far End IMA Group is in Startup

state
Alarm level: 2
Alarm Cause The alarm is generated when the local end IMA group receives
the “group status device is in Startup status” message from the
far end.
Handling Flow If the IMA group is normally configured, then after the far-end
group is successfully started, the alarm is automatically
eliminated because the far-end group is not in the Startup state.
FE is in blocked state
Alarm level: 2
Alarm Cause The alarm is generated at the local end when the local end IMA
group receives the “status device is in blocked state” message in
the ICP cell from the far-end IMA group.
Handling Flow Check the status of the far-end IMA group. If the far-end group
is set to inhibited, enter the module No., subsystem No., unit
No., subunit No., and the group name on the DDM and then set
the group on the far end to “uninhibited”.
Timing of Near-End IMA Group

Failure
Alarm level: 2
Alarm Cause Far-end IMA group clock template sent by the remote end
through ICP cells does not match with the near-end one. For
example, ICT (Independent Clock Template) on the remote end
does not match with CTC (Common Transmit Clock) on the near
end.
Handling Flow Check if the clock mode on the near end and that on the far end
match each other. If they do not match, modify the
configuration. Check if the alarm is eliminated.

FE RXLSM is in Unusable State

Alarm level: 2
Alarm Cause Because a receiving link at remote end is faulty, the link
transmits from the ACTIVE state to the Unusable state. Or,
the link just switches to the Unusable state shortly after
being configured.
This alarm is generated when the near end receives the
“receiving link is in available status” message from the
remote end through ICP cells.
Handling Flow 1. If the alarm is generated because the link switches to the
Unusable state shortly after being configured, the alarm
disappears automatically.
2. If the alarm is due to faulty remote receiving link, check the
remote IMA link configuration to see if the scrambling and
direction match the local-end sending link.
3. Check if the RUN indicator on the clock board is normal
(green and slowly flashes), use the debugging function
ppdbgpslot (BYTE ucSlot) to check the connection relation of
UIM and DTB. Check if the E1 cable is loose.
Implementation specific TX fault

declared at the NE
Alarm level: 2
Alarm Cause The near-end sending link fault is generally due to IMA device
failure.
Handling Flow Check if the IMA chip works normally and if the E1 cable is
correctly connected. As this alarm is caused by occasional
unstable operation of chip, it seldom occurs and can disappear
automatically.
Near-End Sending Link Broken

Alarm level: 2
Alarm Cause

A sending link in the group does not connect to the remote end
IMA group link other links.
Handling Flow Check if the IMA chip works normally. Ensure that each link is
correctly connected to the remote end IMA group. If the chip
works abnormally or some links does not properly connect to the
remote-end IMA group, configure them again. Check if the alarm
is eliminated.
Near-End Sending Link Broken

Alarm level: 2
Alarm Cause The physical E1 link connection is faulty.
Handling Flow The loss of IMA frame is generally due to faulty E1 physical
connection. Check if the E1 links are connected to the
corresponding remote links. Ensure that the connection order of
E1 link is correct. If the E1 link connection is incorrect, connect
the E1 links again. Check if the alarm is eliminated.
LODS Alarm of Near-End Receiving

Link
Alarm level: 2
Alarm Cause The receiving clock is abnormal.
Handling Flow Check if the access clock of IMAB works normally. Check RUN
indicator on the clock board of the corresponding NE is in normal
status of green and slowly flashing. If the access clock is
abnormal, handle the problem according to maintenance
suggestions for clock alarm. Set the clock to the normal state.
RDI Alarm of Near-End Receiving

Link
Alarm level: 2

Alarm Cause The remote IMA link is not in the activated state.
Handling Flow Check the remote receiving link status. Ensure that the remote
receiving link is in the active state. If the remote receiving link is
not in the active state, check and set it to the active state.
Near-End Receiving Link Faults

Alarm level: 2
Alarm Cause The alarm is generated if the near-end receiving link is faulty.
Handling Flow Check if the IMA chip works normally and if each link is correctly
connected to the near-end IMA group. If the IMA chip works
abnormally or does not connect to the near-end IMA group, fix
the problem. Check if the alarm is eliminated.
Implementation specific Rx failed

declared at the NE
Alarm level: 2
Alarm Cause The alarm is generated if the near-end receiving link becomes
invalid.
Handling Flow Similar to near-end receiving link faults, this alarm occurs after
a long time of transition. It is due to occasional unstable
operation of chip or link and it can automatically disappear.
Near-End Receiving Link Broken

Alarm level: 2
Alarm Cause A receiving link in the group does not connect to the remote end
IMA group link other links.
Influence The Iu physical link is broken.
Handling Flow Check receiving link connections on the two ends to see if each
receiving link is connected to the near-end IMA group normally
and if the proper local E1 link is connected to the corresponding

E1 link on remote end. If a receiving link is not connected to the

near-end IMA group or the local link does not connect to the
remote link, rectify the fault and check if the alarm is eliminated.
Far end TXLSM is in Unusable State

Alarm level: 2
Alarm Cause Because a sending link at remote end is faulty, the link
transmits from the ACTIVE state to the Unusable state. Or,
the link just switches to the Unusable state shortly after
being configured.
This alarm is generated when the near end receives the “the
sent link is being used” report from the remote end through
ICP cells.
Handling Flow 1. If the alarm is generated because the link switches to the
Unusable state shortly after being configured, the alarm
disappears automatically.
2. If the alarm is due to faulty remote sending link, check the
remote IMA link configuration to see if the scrambling and
direction match the local-end sending link.
3. Check if the E1 cable is loose.
Fe IMA Group's part of links are

possibly arp looped back
Alarm level: 2
Alarm Cause Far-end IMA group's part links are loopback and came to
operational state, and part of links are connected to near-end
group.
Handling Flow Check if the links of the far-end IMA group connected to the
local end are not loopback.
Remote Receiving Link ID

Mismatched

Alarm level: 2
Alarm Cause Two groups of interacted links are wrongly connected or link ID
is modified on the background.
Influence The RX link status machine at the NodeB side cannot normally
flip.
Handling Flow 1. Check if the E1 lines are correctly connected.
If the receiving link ID of near-end IMA link is not consistent
with the sending link ID of the far-end IMA link connected
through E1 link, or the receiving link ID of near-end IMA link
is the same as a sending link ID that is not interconnected,
the E1 line is incorrectly connected.
If E1 line is incorrectly connected, connect the correct E1 link
to the near-end link. Check if the alarm is eliminated.
2. Check if the inconsistency between sending link ID and
receiving link ID results from the modification of sending ID
of far-end IMA link. If yes, modify the sending link ID of far-
end IMA link to the receiving link ID of near-end IMA link.
BFD Session Interrupted

Alarm level: 3
Alarm Cause The UDP-layer link where the BFD session runs is faulty. This
leads the BFD module to the down state.
Influence The service is interrupted.
Handling Flow 1. Check if physical link between the source IP address and
destination IP address is smooth.
f If the link is broken or the cables are of loose connection,
connect the link or replace the cable. Wait for 30 seconds
and check if the alarm is eliminated.
f If the link is good, go to step 2.
2. Check if the intermediate equipment works normally. If no,
contact the manufacturer.
Abis link broken

Alarm level: 2
Alarm Cause A newly configured link is initially broken.
The link state changes to broken.

The link is actively closed during active/standby switchover.

Influence The BTS is inaccessible.
Handling Flow 1. Check if the transmission link between BSC and BTS is
normal.
f If it is not normal, ensure that the link is normal. Wait for
5 minutes and check if the alarm is eliminated.
f If it is normal, go to step 2.
2. Check if any alarm of high CPU usage occurs on the board
concerned during the alarm period.
f If no alarm occurs, go to step 2.
f If such an alarm occurs, reduce services to lower down
the CPU load. Check if the alarm is eliminated one minute
after the alarm of CPU usage is eliminated.
3. Record the alarm details.
Control plane communication

abnormal between board and its
home module
Alarm level: 2
Alarm Cause The board is configured in the database, but it is not
powered on.
The board is successfully powered on, but the control plane
link with its home MP (CMP and OMP) is broken.
After the board is powered on, the mirco switch (ENUM) is
switched on.
Influence The control plane communication between boards is abnormal.
This may cause control plane messages to be lost.
Handling Flow 1. Check if the ENUM indicator on the alarm board is always
lighting.
f If yes, switch off the ENUM. Check if the alarm is
eliminated.
f If no, go step 2.
2. Check whether the UIM board in the same shelf as this board,
the UIM board in the shelf where the home module is located
and the CHUB (if there is any) are working normally.
f If no, restore the above mentioned boards to the normal
state. Check if the alarm is eliminated.

3. Check if the board is successfully powered on (that is, RUN

indicator flashes at 1 Hz). If the board is not successfully
powered on, power it on. Check if the alarm is eliminated.
Control plane communication

abnormal between MP and OMP
Alarm level: 2
Alarm Cause The MP board is configured in the database, but the board is
not powered on.
The MP board is successfully powered on, but the control
plane link with the OMP is broken.
After the MP board is powered on, the mirco switch (ENUM)
is switched on.
Influence The control plane communication between boards is
abnormal. This may cause control plane messages to be lost.
After the communication between the MP an OMP is broken,
the unit whose home is this MP changes to the unknown
state.
Handling Flow 1. Check if the ENUM indicator on the alarm board is always
lighting.
f If yes, switch off the ENUM. Check if the alarm is
eliminated.
f If no, go step 2.
2. Check whether the UIM board in the same shelf as this board,
the UIM board in the shelf where the home module is located
and the CHUB (if there is any) are working normally.
f If no, restore the above mentioned boards to the normal
state. Check if the alarm is eliminated.
3. Check if the board is successfully powered on (that is, RUN
indicator flashes at 1 Hz). If the board is not successfully
powered on, power it on. Check if the alarm is eliminated.
Association link broken

Alarm level: 2
Alarm Cause The association link is deleted.
The association link is released manually.

Other causes.
Influence The office may be inaccessible and other available association
links are congested.
Handling Flow 1. Check if data configurations, especially port numbers and IP
addresses configured on local and remote offices, are
consistent. Check if the configured association client matches
the configured server.
f If the configurations are inconsistent or server and client
do not match, modify the configuration and then check if
2. Check if the association is blocked manually. View the alarm
details. If the cause is “Sctp BrokenDown: Receive
ShutDownAckfrom SCTP” or it is hinted that the association
is manually blocked, activate the corresponding association
through the dynamic management tool. Check if the alarm is
eliminated.
3. Check if the association is in the standby domain. Check the
msstatus field in the r_office table in probe to see if the
msstatus field on remote end is 2, which indicates that the
office is in the standby domain. In this case, the association
can not be added.
4. Check if there is any alarm of lower layer transmission.
f If yes, ask transmission engineers to solve the problem.
Remarks The alarm seldom occurs.
The following is an example of correct configuration:
f For local association a: local IP address: a.a.a.a. Local
port number: PortA. Remote IP address: b.b.b.b. Remote
port number: PortB. The application attribute is client.
f For remote association B: local IP address: b.b.b.b. Local
port number: PortB. Remote IP address: a.a.a.a. Remote
port number: PortA. The application attribute is server.
STC office inaccessible

Alarm level: 2

Alarm Cause No association is in the serving state.

Influence The system fails to transceive messages to the corresponding
office.
Handling Flow 1. Check if none of the associations to the adjacent office is
available.
f If yes, refer to section “Association link broken” to handle
the alarm.
f If the associations are available, go to step 2.
PPP_UID Link Down

Alarm level: 2
Alarm Cause This alarm is often generated during initial port creation
because ports are generally created dynamically.
The former IPCP state is OPENED. When the link changes to
broken, the link quality is reduced, or lower layer module is
faulty (for example, BSP or microcode fault), the PPP
discards packets for consecutive five times. Moreover, the
PPP state transition leads to another negation.
Handling Flow Check if the BTS is started. Check if the E1 link to the BTS is
normal.
PPP Link Down

Alarm level: 2
Alarm Cause This alarm is often generated during initial port creation
because ports are generally created dynamically.
The former IPCP state is OPENED. When the link changes to
broken, the link quality is reduced, or lower layer module is
faulty (for example, BSP or microcode fault), the PPP
discards packets for consecutive five times. Moreover, the
PPP state transition leads to another negation.

Handling Flow If the link is smooth and IPCP becomes opened after
negotiation, the alarm is restored.
Delete the ports that are not OPENED. The methods for
generating and deleting PPP ports vary depending on the
logical board. BIPI/GIPI are dynamically added or deleted.
PISI is statically added or deleted, that is, it has only one
external port.
HDLC unavailable
Alarm level: 2
Alarm Cause This alarm is generated after a HDLC is created. It
disappears after the link gets through.
The link is broken.
Influence If the HDLC is the last available HDLC that is bound to the UID,
then all the services of the corresponding UID are interrupted. If
the HDLC is not the last available HDLC that is bound to the UID,
the service traffic on the corresponding UID is reduced.
Handling Flow 1. Check the settings of HDLC channel to see whether the E1/TI
of this HDLC and its time slots match the peer end.
f If no, modify HDLC setting and make it accordant with
the peer end HDLC.
2. Check if the physical connection is correct.
f If no, adjust the physical connection to make it consistent
with the peer end. Check if the alarm is eliminated.
3. Check if the E1/T1 lines have quality problems.
f If yes, change the E1/T1 lines. Check if the alarm is
eliminated.
from the HDLC.
UID unavailable
Alarm level: 2

The link is broken.

unavailable.”
Association path broken

Alarm level: 2
Alarm Cause The network communication is faulty.
The intra-NE control plane path is broken.
The peer-end equipment is faulty.
The route to the peer-end address is lost.
Influence The path is unavailable. If all the paths are broken, the
association link is broken.
Handling Flow 1. Check if the physical link has serious package loss by using
the command Ping.
f If yes, troubleshoot the physical link and then check if
2. Check the background EMS for alarms of broken
communication link on control plane in the module that the
association belongs to.
3. Check if the peer end equipment that the association belongs
to is faulty. If yes, troubleshoot the physical link and then
PPP link broken

Alarm level: 2
Alarm Cause This alarm is generated when a port is created dynamically.
It disappears after the PPP negotiation succeeds.
The PPP link is broken.
Handling Flow 1. Check if the peer-end BTS works normally.

f If no, refer to related BTS manuals or contact BTS

engineers to rectify the fault. Check if the alarm is
eliminated
2. Check the UID and HDLC setting of BSC and BTS to see if the
E1/T1 and timeslots are consistent.
f If no, modify UID and HDLC settings and make them
accordant at the two ends of BSC and BTS. Check if the
3. Check if physical connection is correct and if the physical link
connection is consistent with the UID/HDLC configuration.
f If no, adjust the physical connection relation according to
the UID/HDLC configuration. Check if the alarm is
eliminated.
4. Check if the physical cables have quality problems.
f If yes, replace the cables. Check if the alarm is
eliminated.
from the PPP port.
BSCIP configuration error in

database
Alarm level: 4
Alarm Cause The BIPI/GIPI is not configured.
The IP addresses of BSCIP are illegal, that is, all 0s or all 1s.
Influence The ABPM cannot locate other problems by using the selfloop
method.
Handling Flow 1. Check if the BSCIP configuration is correct.
f If no, modify the configuration. Check if the alarm is
eliminated.
2. Check if the internal link between OMP and BIPI/GIPI is
normal.
f If no, check related alarms of internal communication and
refer to the handling suggestion.

3. Check if the data is synchronized after the previous data

finishes configuration.
f If no, wait for a period of time and then configure again.
4. Record the BSCIP configuration.
MGW not registered

Alarm level: 2
Alarm Cause The MGW exits the service.
The MGW fails to be registered for a long time (for example,
210 s) after being powered on.
Influence The MGW that generates the alarm is unavailable.
Handling Flow Ask MGW maintenance personnel to check if the MGW
equipment works normally. Record the alarm details.
Dual Homing Office Blocked

Alarm level: 3
Alarm Cause The dual homing office switches to the standby domain. The
service DH process initiates the message of blocking office.
Handling Flow 1. Check if the current dual homing office is in the standby
domain.
f If the current dual homing office is in the standby domain,
it is not necessary to handle the alarm. End the alarm
handling.
f If the current dual homing office is in the active domain,
go to step 2.
2. Perform dynamic management on the dual homing office and
unblock the office. Check if the alarm is eliminated.

Dual Homing Link Blocked

Alarm level: 3
service DH process initiates the message of blocking all the links
of the office.
domain.
handling.
go to step 2.
2. Perform dynamic management on the related links and
unblock the blocked links. Check if the alarm is eliminated.
Dual Homing Association Blocked

Alarm level: 3
service DH process initiates the message of blocking all the
associations of the office.
domain.
handling.
go to step 2.
2. Perform dynamic management on the related associations
and unblock the blocked associations. Check if the alarm is
eliminated.


Trunk error
Alarm level: 2
Alarm Cause The trunk cables are not correctly connected.
Influence The trunk fails to be accessed. All connections based on the
trunk are interrupted.
Handling Flow 1. Check if the E1 lines on the DDF are correctly connected.
2. Set the E1 line to loopback at the local side. Check if the
f If the alarm is eliminated, detect the upstream devices
and take the corresponding measure.
f If the alarm is not eliminated, go to step 3.
3. Replace the board. End the alarm handling.
Trunk abnormal
Alarm level: 2
Alarm Cause Trunk LOF，AIS，or RAI is detected.
Influence The trunk fails to be accessed. All connections based on the
trunk are interrupted.
Handling Flow 1. Check if the grounding of devices is well at both ends.
2. Check if the frame formats at both ends are consistent.
3. Check if impedances match.
4. Check if peer end or upstream devices have alarms. Take the
related measures.

The rate of error code in a matelink

is high at GUIM
Alarm level: 3
Alarm Cause The rate of error code in a matelink is high at GUIM.
Influence The data transmitted through the matelink is incorrect.
Handling Flow Check if the board is correctly inserted. If no, correctly insert it
and check if the alarm is eliminated.
FE Link Error Alarm

Alarm level: 3
Alarm Cause In a pair of FE port, one is link correct but the other is link error.
Influence Link error occurs on the control plane.
Handling Flow 1. Check if only one cable is used to connect the port pair of the
rear board to the peer-end FE port.
f Connect the other cable to the pair of ports to ensure
both ports are connected to the peer-end FE port. The
handling is complete if the alarm is eliminated.
f If two cables are connected, go to step 2.
2. Check if one cable is connected to the peer-end FE port while
the other is connected to the test computer or SIG-IPI. If yes,
remove the FE channel selection line and check if the alarm
is eliminated. Alternatively, remove the cable connecting the
test computer or SIG-IPI and reconnect it to the normal FE
channel selection port. Check if the alarm is eliminated.
Link Broken Between Server and

Alarmbox
Alarm level: 1
Alarm Cause The link between the server and alarm box fails to be set up.
Influence Users cannot be informed of alarms through the alarm box.
Handling Flow

1. In alarm management module, view the IP address of the

alarm box, which is configured on the background, and check
if it can be pinged through.
2. Check if the alarm box is properly powered on.
f If no, start the alarm box. Then, check if the alarm is
eliminated.
3. Check if the alarm box IP address shown on the screen is
consistent with the one configured on the background.
f If no, modify the IP address configured on the
background. Then, check if the alarm is eliminated.
4. Check if the server IP address shown on the screen is
consistent with the one configured on the background.
f If no, modify the IP address configured in the alarm box.
Then, check if the alarm is eliminated.
5. Check if the port number shown in the alarm box is correct.
If it is wrong, correct it and then check if the alarm is
eliminated.
Remarks NE link alarm
HW link broken
Alarm level: 3
Alarm Cause BTS internal link breaks.
Influence The BTS cannot work normally.
Handling Flow 1. Reset the board. Check if the alarm is eliminated.
2. Power on the board again. Check if the alarm is eliminated.
3. Check if the backplane jacket matching the board is normal.
f If it is abnormal, replace the backplane and then check if
f If it is normal, replace the module and then check if the
4. Replace the CMB.

Master rack communication link

alarm
Alarm level: 4
Alarm Cause The communication link between the slave rack and the master
rack is faulty.
Influence The site fails to load and install data and software, and perform
operation and maintenance.
Handling Flow 1. Check if the cables between racks are correctly inserted or
have faults. If faults exist, replace them as soon as possible.
2. Start the self-check of master/slave rack communication.
Determine whether the problem is caused by CMM/CMB
hardware or software fault. Rectify the faults.
Communication link alarm between

master and slave rack (left)
Alarm level: 4
Alarm Cause The communication link between the slave rack and the master
rack is faulty.
Communication link alarm between

master and slave rack (right)
Alarm level: 4
Alarm Cause The communication link between the master rack and the slave
rack is faulty.

A interface E1 remote alarm

Alarm level: 3
Alarm Cause The sending line is broken. This causes the remote end fail to
receive data sent from local end.
Influence The BTS cannot provide services.
Handling Flow 1. Check if E1 cables have faults through loopback test.
f If yes, make the cables again to remove cable faults.
2. Inset the CMM/CMB board tightly and power it on again.
3. Start the selfloop test of E1 interface. Check if the result is
normal.
f If yes, infer that the fault is rooted in transmission.
Rectify transmission faults.
4. Change the CMM/CMB board. Check if the alarm is eliminated.
B interface E1 remote alarm

Alarm level: 3


normal.
C interface E1 remote alarm

Alarm level: 3
normal.
D interface E1 remote alarm

Alarm level: 3


normal.
E interface E1 remote alarm

Alarm level: 3
normal.
F interface E1 remote alarm

Alarm level: 3

normal.
G interface E1 remote alarm

Alarm level: 3
normal.
H interface E1 remote alarm

Alarm level: 3


normal.
LAPD communication link between

FUC and BSC break
Alarm level: 2
Alarm Cause The L2 layer software of FUC does not communicate wit the BSC
for a period of time.
Influence The FUC cannot work. If the FUC is BCCH-TPU, cell services are
affected.
normal.
Communication link between CMM

and FUC break(BTS V2)

Alarm level: 3
Alarm Cause The HDLC link between the CMM and TPU is broken. The CMM
hardware is faulty.
Influence The FUC polling is faulty. No data can be transmitted between
the TPU and CMM. If the data configuration of FUC, CHP, and
CIP cannot complete, their states cannot be reported.
Handling Flow The system can run but data configuration cannot be performed.
If the problem is only that the TPU link is broken for a long time,
use the following method to solve the problem:
1. Check if the TPU board is inserted tightly.
2. Reset the TPU board. Check if the alarm is eliminated.
3. Check if the CMM board works normally.
4. Check if the address switch on the backplane is correct.
5. Check if the transmission lines on the backplane are correctly
connected.
6. Use a HW selfloop test to check whether the fault is rooted in
software or hardware. If the hardware is faulty, replace the
related board. If the software is faulty, modify and upgrade
the software version.
HDLC communication link between

CMB and FUC broken
Alarm level: 3
Alarm Cause The HDLC link between the CMM and TPU is broken. The CMM
hardware is faulty.
Influence The FUC polling is faulty. No data can be transmitted between
the TPU and CMM. If the data configuration of FUC, CHP, and
CIP cannot complete, their states cannot be reported.
Handling Flow The system can run but data configuration cannot be performed.
If the problem is only that the TPU link is broken for a long time,
use the following method to solve the problem:
1. Check if the TPU board is inserted tightly.
2. Reset the TPU board. Check if the alarm is eliminated.
3. Check if the CMM board works normally.
4. Check if the address switch on the backplane is correct.
5. Check if the transmission lines on the backplane are correctly
connected.
6. Use a HW selfloop test to check whether the fault is rooted in
software or hardware. If the hardware is faulty, replace the

related board. If the software is faulty, modify and upgrade

the software version.
LAPD communication link between

FUC and BSC broken
Alarm level: 3
Alarm Cause The L2 layer software of FUC does not communicate wit the BSC
for a period of time.
Influence The FUC cannot work. If the FUC is BCCH-TPU, cell services are
affected.
Handling Flow 1. Check if other FUCs in the base station have the alarm. If all
FUNCs in the base station have the alarm, check if E1 cables
are correctly connected and if TIC, LAPD, and DSN have
alarms. If alarms are generated, locate the problem and
solve it.
2. Check if BSC data is correct, especially T net link and
timeslot link of SMB data.
3. If the LAPD of only one TRM/DTRU is broken, check if the
backplane cables are correctly connected. Correctly connect
them and then check if the alarm is eliminated.
CU parameter configuration error

Alarm level: 3
Alarm Cause The parameter configuration is incorrect or has conflicts.
Influence The DTUR normal operation is affected.
Handling Flow 1. Check the parameters of software configuration, that is,
frequency point, mode, and static power level. Configure the
parameters again on the background and synchronize them
to the base station.
2. Replace the DTRU if the above method has no effect.
Remarks Generally, the BSC background checks the data legality before
synchronizing data. Only legal data can be synchronized.
Therefore, this alarm seldom occurs.

Communication broken between

EAM and CMB
Alarm level: 3
Alarm Cause The communication between EAM and CMB is broken.
Influence Alarm reporting is affected.
Handling Flow 1. Check if the EAM is powered on.
2. Check if the CMB works normally.
3. Replace the EAM board or backplane.
BSC LAPD communication link

broken
Alarm level: 2
Alarm Cause The LAPD communication between rack operation&maintenance
unit and BSC is broken.
Influence The rack exits from services.
Handling Flow 1. Check if E1 interface on the corresponding BSC has
continuous alarms. If yes, check the transmission equipment
and handle the related faults.
2. Ensure that the site is powered on and the DIP is correct.
Site LAPD communication link

broken
Alarm level: 2
Alarm Cause The LAPD communication between site operation&maintenance
unit and BSC is broken.
Influence The site exits from services.
Handling Flow 1. Check if E1 interface on the corresponding BSC has
continuous alarms. If yes, check the transmission equipment
and handle the related faults.
2. Ensure that the site is powered on and the DIP is correct.

Cell interruption alarm

Alarm level: 2
Alarm Cause The cell is interrupted.
Influence The cell exits from services.
Handling Flow View the cell management, transceiver management and
channel management on the background.
1. View the cell management.
f If some cells are manually blocked, unblock them.
f If some cells are blocked due to global resetting, check
and rectify A interface fault.
2. View the transceiver management.
f If the BCCH carrier of the cell that generates the alarm is
manually blocked, unblock the carrier.
f If blockage due to broken LAPD exists, restore the LAPD
link.
f If blockage of carrier CU or FU operation status, check
and restore the carrier faults.
3. View the channel management. If the BCCH timeslot of the
cell that generates the alarm is manually blocked, unlock the
timeslot.
Front-end communication link broken

alarm
Alarm level: 2
Alarm Cause The handshake between NFSDETECT process of OMP and SBCX
fails.
Influence Performance data is lost.
Handling Flow 1. Check if the network cables between SBCX and OMP are
correctly connected.
2. Check if the front-end process address and the port number
are correct in the OMP configuration file.
3. Check if the NFSDETECT process of SBCX is running normally.

Control link broken

Alarm level: 2
Alarm Cause The communication between HBTS and iBSC is broken.
Influence The HBTS cannot normally communicate with the iBSC.
Handling Flow 1. Check the transmission link.
2. Load the software version again.
3. Upgrade the software version.
Remarks The HBTS model is S8001.
Operation link broken(CS)

Alarm level: 3
Alarm Cause For the CS service, the communication link between HBTS and
iBSC is broken or has no response for a long time.
Influence The subscribers of the HOMEBTS fail to use the CS service.
Handling Flow 1. Check if the transmission link is normal. Check if the alarm is
eliminated.
2. Check if the IP address and the port number are correct,
Operation link broken(PS)

Alarm level: 3
Alarm Cause For the PS service, the communication link between HBTS and
iBSC is broken or has no response for a long time.
Influence The subscribers of the HOMEBTS fail to use the PS service.
Handling Flow 1. Check if the transmission link is normal. Check if the alarm is
eliminated.
2. Check if the IP address and the port number are correct,

Handling Alarms
Process Instance Configuration Error
Alarm level: 2
Alarm Cause The number of instances is modified in the processes whose
instances cannot be configured. For example, the maximum
or minimum instance number of the processes registered as
(1, 1) is modified.
The preset number of process instances is excessive, which
results in insufficient memory.
The configuration of process instances does not observe the
configuration rules, for example, the maximum number of
processes should be greater than or equal to the minimum,
the process instances to be configured should be firstly
registered in the version.
Influence The board startup fails.
Handling Flow Check the configuration table of process instances. Record the
alarm details.
T Network Connection Not Conform

to Configuration
Alarm level: 1
Alarm Cause The T network fiber connection does not conform to the optical
interface connection relation configured on the background.
Influence The T network switching of the shelf where the board is located
is out of order.
Handling Flow 1. Check the connection relation configured for the board and
the fiber connection on the rack in the configuration
management. Ensure that the fiber is connected in position.
2. Check if the physical configuration is consistent with the
actual situation. If no, change the fiber connection or the
configuration to ensure the consistency with the physical
connection. Check if the alarm is eliminated.

DB Config Doesn't Fit for Device

Alarm level: 3
Alarm Cause The equipment type configured in the database does not
conform to the board hardware equipment.
Handling Flow 1. Based on the detailed information on the alarm, check if the
background configuration conforms to the board hardware
equipment.
f If no, modify the configuration according to the hardware
equipment. Power on the board again. Then, check if the
2. Record alarm details.
OMC Gateway Mask Different from

DBs
Alarm level: 2
Alarm Cause The mask of the OMC gateway read from the OMP database is
inconsistent with that previously saved on the OMP.
Influence The system cannot start normally. This may disable the
communication between foreground and background.
Handling Flow Restart the active and standby OMP boards at the same time.
Alarm Due to Inconsistent Area

Code
Alarm level: 2
Alarm Cause The area code exported from the OMP database is inconsistent
with that previously saved on the OMP.

Alarm Due to Inconsistent Mac

Address of Background OMP(OMC)
Alarm level: 2
Alarm Cause The OMC MAC address read from the OMP database is
Alarm Due to Inconsistent Mac

Address of Background OMP(OMC)
Alarm level: 2
Alarm Cause The OMC IP address read from the OMP database is inconsistent
with that previously saved on the OMP.
Alarm Due to Inconsistent MP Type

Alarm level: 2
Alarm Cause The module type read from the MP database is inconsistent with
that previously saved on the MP.
Influence The system cannot start normally. The MP may not provide
functions normally.
Handling Flow 1. Check if the board module type is OMP.
f If no, restart the board and check if the alarm is
eliminated.
2. Change the start mode to foreground start, or modify the
configuration of the startup file on the background to make it
consistent with the database configuration. Then, restart the

active and standby OMP boards at the same time. Check if

Startup File Does Not Exist

Alarm level: 2
Alarm Cause The Bootcfg.ini file does not exist.
Influence The system cannot start normally. The MP may not provide
functions normally.
OMP GateWay IP Different from DBs

Alarm level: 2
Alarm Cause The gateway IP address read from the OMP database is
OMC Server IP Different from Dbs

Alarm level: 2
Alarm Cause The IP address of the OMC server read from the OMP database is
OMC Gateway Mask Different from

DBs

Alarm level: 2
Alarm Cause The subnet mask of OMC gateway read from the OMP database
is inconsistent with that previously saved on the OMP.
OMP Config Changes

Alarm level: 1
Alarm Cause The key configuration data of OMP is changed.
Influence The OMP needs to be reset. Otherwise, the system cannot work
normally.
Inconsistent Office ID Settings of DIP

Switch
Alarm level: 2
Alarm Cause The office IDs set through DIP switch in different shelves are
different.
Influence The MAC addresses conflict. The verification of board MAC and IP
address fail. The board cannot be powered on.
Handling Flow 1. Check if the DIP switch for office ID setting in this shelf is
consistent with that in the shelf where OMP is located. If no,
change the office ID DIP switch. Check if the alarm is
eliminated. If the alarm is eliminated, go to step 2.
2. Restart all the boards in this shelf. Ensure that the newly set
office ID takes effect.
Port Work Mode Doesn't Match

Settings
Alarm level: 2

Alarm Cause The preset work mode of external port does not take effect due
to faulty performance of the chip on the local end or
unsuccessful settings on the peer end.
Influence The network interface does not work as the setting.
Handling Flow 1. Check if the work mode on the peer end matches the one set
on the local end.
f If no, modify the work mode on the peer end to make it
consistent with the one on the local end. Check if the
2. Check if the work mode at the local end is correctly set. If no,
change it to a correct one and then check if the alarm is
eliminated.
Formats of audio resource

inconsistent
Alarm level: 2
Alarm Cause Different formats of tones cannot co-exist on the board.
Influence The DSP cannot use the service.
Handling Flow y using the formatting button of OMC background tools, set the
audio format to new audio format or old audio format. Check if
Version Switches While Board

Doesn't Reset
Alarm level: 4
Alarm Cause The OMP is configured to switch the same version, but the
board does not reset automatically.
The OMP switches to the BOOT version, but the board does
not reset automatically.
Influence The version takes effect only after the board is reset.
Handling Flow 1Manually restart the OMP board.

Function EPLD Update Failure

Alarm level: 4
Alarm Cause The size of the functional EPLD version exceeds the threshold.
The functional EPLD fails to be burnt.
After the functional EPLD is burnt, the verification fails.
Influence If the alarm is eliminated, the board may not be restarted.
Handling Flow 1. Use the version management tool to switch to a correct
functional EPLD version and then check if the alarm is
eliminated.
2. The alarm may be caused by hardware faults. Replace the
board and check if the alarm is eliminated.
Remarks Currently the upper limit of EPLD version size is 64 K.
Inconsistent BOOT/EPLD Version

No. with Database Configurations
Alarm level: 4
Alarm Cause The running BOOT version does not match the database.
The running EPLD version does not match the database.
Influence If the running EPLD version does not match the database,
the board may not function properly.
If the running BOOT version does not match the database,
the board with many CPUs cannot start from CPU.
Handling Flow Switch BOOT/EPLD again and restart the board manually. After
the board begins running normally, the alarm is eliminated.
Boot Version Fails to Be Written to

Backup Region
Alarm level: 4
Alarm Cause The system fails to cover the bootflash backup region.
Influence The BOOT backup version is unavailable.
Handling Flow Switch BOOT again and restart the board manually. After the
board begins running normally, the alarm is eliminated.

Microcode Is Abnormal
Alarm level: 2
Alarm Cause The micro code program is trapped in an endless loop.
Hardware faults of micro engineer leads to exceptional
operation.
Hardware faults of CP or XP leads to exceptional operation.
Influence The board communication link is broken.
The service that the board bears is interrupted.
Handling Flow 1. Restart the board that generates the alarm (board of Release
version starts automatically). After the board is restarted,
2. Pull out and plug in the board. After the board is restarted,
3. The board hardware may have fault. Replace the board.
PVC Fault
Alarm level: 3
Alarm Cause When PVC CC function is enabled, the working status of PVC
becomes non-operating status.
The local end enables CC function, but the peer end does not
enable this function.
Influence The PVC status changes to faulty. The services that the PVC
bears, irrespective of signaling or data, are interrupted.
Handling Flow 1. Check if the optical fibers corresponding to the PVC work
normally.
f If no, correctly connect the fibers and then check if the
f If the fibers work normally, go to step 2.
2. Check if the CC function is enabled on the local end but not
on the peer end
f If yes, activate the CC function on the peer end so that
the local end can receive CC cells. Send user data from
the peer end, and the peer end can receive the user cell.
You can also deactivate CC detection on the local end.

3. Delete the PVC. Check if the alarm is eliminated.
FE reports unacceptable
configuration parameters(M size)
Alarm level: 2
Alarm Cause The near-end IMA group receives unacceptable configuration
message through ICP cells from the far-end IMA group. (M size)
Handling Flow Check if the parameter configuration of frame length (M size) on
the near end and far end match each other.

state (because of unmatched
symmertry mode)
Alarm level: 2
message through ICP cells from the far-end IMA group.
(Unadaptable Symmetry)
Handling Flow Check if the configuration of Symmetry on the near end and far
end match each other.

state (because of unmatched OAM
lable)
Alarm level: 2
message through ICP cells from the far-end IMA group.
(Unmatched OAM label)
Handling Flow

Check if the configuration of IMA version on the near end and far
end match each other.

state (because of other reseans)
Alarm level: 2
message through ICP cells from the far-end IMA group. (other
reasons)
Handling Flow Check if the group parameter configuration on the near end and
far end match each other.
FE is in Insufficient links State

Alarm level: 2
message through ICP cells from the far-end IMA group. (other
reasons)
Handling Flow Use the DDM tool to enter the group, module, subsystem, unit,
and subunit number of the link that generates the alarm. Check
the status of each configuration link in the far-end IMA group
and ensure that the number of Active links is greater than or
equal to the specified minimum number. In this way, the links in
the group can reach the required number of Active links. Then,
the alarm can be eliminated.
Near-End IMA Group Configuration

Failure
Alarm level: 2
Alarm Cause The group parameters configured on near end IMA group do not
match with those configured on the far end. In addition, the IMA
configuration parameters sent by the remote end through ICP
cells are rejected. Therefore, the system comes into
Config_Aborted status.


Handling Flow Check if IMA group parameter configuration are correct and
match mutually on the near end and far end. If no, modify the
parameters and then check if the alarm is eliminated.
NE Group is in Insufficient links State

Alarm level: 2
Alarm Cause The number of active links on the local end is less than the
specified minimum number of sending or receiving links.
Handling Flow The alarm is eliminated automatically when the number of active
links is greater than or equal to the specified number of sending
or receiving links.
Number of Alarms Over Threshold

Alarm level: 2
Alarm Cause The foreground alarm pool is full.
Influence Alarms are lost, and the system may be collapsed.
Handling Flow Check if there are virtual configuration resources that are
temporarily useless. If yes, delete them and then check if the
Board Connection Check is Off

Alarm level: 4
Alarm Cause The connection check switch is off, causing PP service process
unable to perform connection check.
Influence The connection check is prohibited and thus connection error
cannot be detected automatically. This causes the connections
fail to self heal in some cases.
Handling Flow Restore the connection check.

Access DSP's HPI memory error

Alarm level: 2
Alarm Cause For some reason, HOST cannot access DSP's register through
HPI.
Influence This problem causes call losses.
Handling Flow Check if the threshold setting is reasonable. If yes, reduce DSP
traffic. If no, modify the threshold.
The config data of sntp in DBS is

wrong
Alarm level: 3
Alarm Cause The IP address of the NTP server is set to 0 or 0xFFFFFFFF in
the database.
The period of synchronization is zero.
Influence The system time may be different.
Handling Flow 1. Check if the IP address of the NTP server is set to 0 or
0xFFFFFFFF in the database. If yes, change it to the actual IP
address of the NTP server.
2. Check if the synchronization period in the database is zero. If
yes, change it to a non-zero value.
The Client Of Sntp Failed In

Fetching Net Time
Alarm level: 3
Alarm Cause The NTP server does not exist or it works abnormally.
The IP address of the NTP server in the database is different
from the actual one.
Handling Flow 1. Check if NTP server exists or if the NTP server works
normally. If it does not exist or work normally, configure the
NTP server and make it work normally. Issue a command of
NTP time synchronization on the background, and then check
if the alarm is eliminated after 30 seconds.

2. Check if the IP address of the NTP server configured in the

database is consistent with that of the actual NTP server. If
no, modify the IP address of the NTP server on the
foreground to make it consistent with that of the actual
server. Alternatively, modify the IP address of the NTP server
to make it consistent that in the database.
SNTP failure
Alarm level: 3
Alarm Cause The NTP server does not exist or it works abnormally.
The IP address of the NTP server in the database is different
from the actual one.
The NTP ser IP address of the NTP server is set to 0 or
0xFFFFFFFF in the database.
The period of synchronization is zero.
Handling Flow 1. Check if NTP server exists or if the NTP server works
normally.
f If it does not exist or work normally, configure the NTP
server and make it work normally. Issue a command of
NTP time synchronization on the background, and then
check if the alarm is eliminated after 30 seconds.
f If it works normally, go to step 2.
2. Check if the IP address of the NTP server configured in the
database is consistent with that of the actual NTP server.
f If no, modify the IP address of the NTP server on the
foreground to make it consistent with the actual one and
upload the modified data to the foreground. Alternatively,
modify the IP address of the NTP server to make it
consistent that in the database. Issue a command of NTP
time synchronization on the background, and then check
if the alarm is eliminated after 30 seconds.
3. Check if the IP address of the NTP server is set to 0 or
0xFFFFFFFF in the database.
f If yes, change it to the actual IP address of the NTP
server and upload the modified data to the foreground.
Check if the alarm is eliminated after 10 seconds.

Number of management module

alarms exceeds the threshold
Alarm level: 2
Alarm Cause The foreground alarm pool is full.
Influence Alarms are lost, and the system may be collapsed.
Handling Flow Check if there are virtual configuration resources that are
temporarily useless. If yes, delete them and then check if the
NTP time exceeds threshold

Alarm level: 3
Alarm Cause The difference between NTP time and local time exceeds the
threshold.
Influence NTP clock synchronization terminates.
Handling Flow 1. Check if the interval between alarm time and current
environment time exceeds 8 periods.
f If no, check the synchronization period and modify it if it
is too long. Wait for 8 alarm periods and go to Step 2.
2. Check if the overload alarm is restored. If no, go to step 1.
3. Check if the alarm of NTP server invalid alarm exists.
f If yes, restore the alarm first and then go to step 4.
4. Check if the link between OMP and RPU is broken.
f If yes, restore the link and then go to step 1.
5. Check if the alarm threshold of NTP server is too low.
f If the alarm threshold is not 0 and less than 100,
increase the threshold or change it to 0. Then, go to step
1.
f If the threshold is greater than 100, go to step 6.
6. Manually originates time synchronization on the background.

brs main config request timeout

Alarm level: 2
Alarm Cause EPU or RPU requests the database for configuration. The
database has no response.
EPU or RPU requests the database for configuration. The
database gives wrong information.
The messages given by EPU or RPU to the database are lost.
The control plane communication is interrupted.
Influence The protocol stack cannot work.
Handling Flow 1. Check if the home module MP and the local board system
control are normal and if their communication is normal..
f If yes, end alarm handling.
2. Pull out and plug in the board. Reset the hardware. Check if
brs main epu register timeout

Alarm level: 2
Alarm Cause The RPU is not successfully powered on.
EPU or RPU communication is broken.
RPU receives the EPU register request, but the checksum
message is incorrect.
The control plane communication is interrupted.
Influence The protocol stack cannot work.
Handling Flow 1. Check if the RPU and communication between EPU and RPU
are normal.
f If yes, end alarm handling.
2. Pull out and plug in the board. Reset the hardware. Check if

Database config is different from file

named bootcfg ini.
Alarm level: 2
Alarm Cause The data from the OMP database is inconsistent with that
previously saved on the OMP.
Influence System startup is abnormal. MP may not provide functions
normally.
Handling Flow Restart the master and slave OMPs at the same time. Check if
Wrong Parameter configuration for

TPU Ch0
Alarm level: 4
Influence The channel assignment and normal operation are affected.
Handling Flow 1. Wait for 10 minutes. Check if the alarm is eliminated.
2. Configure the parameters again on the background and
synchronize to the base station. Check if the alarm is
eliminated.

TPU Ch1
Alarm level: 4


eliminated.

TPU Ch2
Alarm level: 4
eliminated.

TPU Ch3
Alarm level: 4
eliminated.


TPU Ch4
Alarm level: 4
eliminated.

TPU Ch5
Alarm level: 4
eliminated.

TPU Ch6
Alarm level: 4


eliminated.

TPU Ch7
Alarm level: 4
eliminated.
Cell configuration parameter

mismatch(BTS V2)
Alarm level: 3
Alarm Cause The cell parameter configuration is wrong, or conflicts with the
configuration of channel parameter and CIP parameters.
Influence The BTS may work abnormally.
eliminated.
3. Check if the hardware is faulty. If hardware faults exist,
replace the related module.

Software version of FUC

mismatch(BTS V2)
Alarm level: 3
Alarm Cause The FUC software version is incorrectly installed. If one carrier is
configured as BCCH, the whole cell cannot work normally.
Influence The TRM/DTRU cannot work normally.
Handling Flow Reset the TRM/DTRU. If the alarm persists, replace the
TRM/DTRU.
Software version of CHP

mismatch(BTS V2)
Alarm level: 3
Alarm Cause The four DSPs of CHP cannot run. If one DSP is configured as
BCCH, the whole cell cannot work normally.
TRM/DTRU.
L3 Software of FUC No
Response(BTS V2)
Alarm level: 4
Alarm Cause The MO software has/has no response temporally (which is
determined by CMM).
Influence The background cannot detect the running status of FUC. Calls,
however, are not affected.
Handling Flow 1. Wait for ten minutes. Check if the alarm is eliminated.
2. If the alarm cannot be eliminated for a long time, pull out
and plug in the FUC when the traffic is low. Reset the FUC

3. Reset the CMM when the traffic is low. Check if the alarm is
eliminated.
4. Replace the TRM/DTRU. Check if the alarm is eliminated.
5. If the alarm is due to software faults, modify and upgrade
the version.

CIP
Alarm level: 3
Alarm Cause The parameter configuration is wrong or has conflicts.
Handling Flow 1. Check the software configuration parameters, that is,
frequency point, mode, and static power level. Configure the
parameters again on the background and synchronize them
to the base station.
2. If the alarm persists, replace the TRM/DTRU.
Software version of CIP mismatch

Alarm level: 3
Alarm Cause The CIP software version is incorrectly installed. If one carrier is
TRM/DTRU.

TRM Channel 0
Alarm level: 4


eliminated.

TRM Channel 1
Alarm level: 4
eliminated.

TRM Channel 2
Alarm level: 4
eliminated.


TRM Channel 3
Alarm level: 4
eliminated.

TRM Channel 4
Alarm level: 4
eliminated.

TRM Channel 5
Alarm level: 4


eliminated.

TRM Channel 6
Alarm level: 4
eliminated.

TRM Channel 7
Alarm level: 4
eliminated.
Remarks

Generally, the BSC background checks the data legality before

Cell configuration parameter

mismatch
Alarm level: 3
Alarm Cause The cell parameter configuration is wrong, or conflicts with the
configuration of channel parameter and CIP parameters.
Influence The BTS may work abnormally.
eliminated.
3. Check if the hardware is faulty. If hardware faults exist,
replace the related module.
FUC Software version mismatch

Alarm level: 3
Alarm Cause The FUC software version is incorrectly installed. If one carrier is
Influence The DTRU cannot work normally.
Handling Flow Reset the DTRU. If the alarm persists, replace the DTRU.
CHP Software version mismatch

Alarm level: 3
Alarm Cause The CHP software version is incorrectly installed.
Influence The DSP of CHP cannot run. If one carrier is configured as BCCH,
the whole cell cannot work normally.

CU Software version mismatch

Alarm level: 3
Alarm Cause The CH software version is incorrectly installed.
Influence The DSP of CHP cannot run. If one carrier is configured as BCCH,
the whole cell cannot work normally.
FUC L3 Software no response

Alarm level: 4
Alarm Cause The MO software has/has no response temporally (which is
determined by CMB).
Influence The background cannot detect the running status of FUC. Calls,
however, are not affected.
Handling Flow 1. Wait for ten minutes. Check if the alarm is eliminated.
2. If the alarm cannot be eliminated for a long time, pull out
and plug in the FUC when the traffic is low. Reset the FUC
3. Reset the CMB when the traffic is low. Check if the alarm is
eliminated.
4. Replace the DTRU. Check if the alarm is eliminated.
5. If the alarm is due to software faults, modify and upgrade
the version.
Parameter configuration mismatch

Alarm level: 3
Alarm Cause The iBSC parameter configuration fails.
The parameter configuration times out.
The configuration process is interrupted, such as timeout and
link broken.
Influence The S8001 cannot work normally.
Handling Flow Configure the parameters again.

Parameter configuration failure of

AD6537
Alarm level: 3
Alarm Cause The AD6537 register reads and writes abnormally.
Influence The system cannot normally read and write the AD6537 register.
Handling Flow Configure the AD6537 register again.
Environment Alarms
Cell delineation do not
synchronization about cell on E1 link
Alarm level: 3
Alarm Cause The HEC field of cell header is corrupted, which results in loss of
delineation. This alarm is generally caused by physical layer
faults. It may also be caused by different methods for processing
HECs on local end and peer end devices.
Influence The data receipt fails and the signaling link is broken.
Handling Flow 1. Check if other physical layer alarms exist. If yes, clear the
alarms and then check if this alarm is eliminated.
2. Check if both ends are configured as SDH mode or SONET
mode. If the modes are inconsistent, set them to correct
signaling mode and then check if the alarm is eliminated.
RACK Temperature Over Alarm

Threshold
Alarm level: 3
Alarm Cause The rack temperature exceeds the preset upper limit of alarm
threshold.
Influence The boards work abnormally.
Handling Flow

1. Check if the preset upper limit of rack temperature threshold

on the background is reasonable.
f If no, modify the threshold and synchronize it to the
foreground. Check if the alarm is eliminated
2. Cool the rack temperature. Check if the alarm is eliminated.
RACK Temperature Lower Than

Alarm Threshold
Alarm level: 3
Alarm Cause The rack temperature is lower than the preset lower limit of
alarm threshold.
Handling Flow 1. Check if the preset lower limit of rack temperature threshold
on the background is reasonable.
2. Increase the rack temperature. Check if the alarm is
eliminated.
House temperature is higher than

high threshold
Alarm level: 3
Alarm Cause The temperature in the equipment room is higher than the
preset upper limit of alarm threshold.
Handling Flow 1. Check if the preset upper limit of temperature in equipment
room on the background is reasonable.
2. Cool the equipment room. Check if the alarm is eliminated.

House temperature is lower than

high threshold
Alarm level: 3
Alarm Cause The temperature in the equipment room is lower than the preset
lower limit of alarm threshold.
Handling Flow 1. Check if the preset lower limit of temperature in equipment
room on the background is reasonable.
2. Cool the equipment room. Check if the alarm is eliminated.
Any one of rack voltage inputs above

threshold
Alarm level: 3
Alarm Cause The voltage of a line exceeds the upper limit of the alarm
threshold.
Handling Flow 1. Check if the high voltage threshold on the background is
reasonable.
2. Reduce the voltage. Check if the alarm is eliminated.
Any one of rack voltage inputs below

threshold
Alarm level: 3
Alarm Cause The voltage of a line is lower than the upper limit of the alarm
threshold.


Handling Flow 1. Check if the high voltage threshold on the background is
reasonable.
2. Increase the voltage. Check if the alarm is eliminated.
Temperature in equipment room

above threshold
Alarm level: 3
Alarm Cause The humidity in the equipment room exceeds the upper limit of
the alarm threshold.
Handling Flow 1. Check if the higher limit of humidity threshold on the
background is reasonable.
2. Decrease the humidity. Check if the alarm is eliminated.
Temperature in equipment room

below threshold
Alarm level: 3
Alarm Cause The humidity in the equipment room is lower than the lower
limit of the alarm threshold.
Handling Flow 1. Check if the lower limit of humidity threshold on the
background is reasonable.
2. Increase the humidity. Check if the alarm is eliminated.

Rack fans faults

Alarm level: 3
Alarm Cause The fans in the rack are faulty.
Handling Flow 1. Check if the fan plug-in box and its power line are connected
securely (the indicators are normal).
f If no, secure the fan plug-in box and connect the power
line. Check if the alarm is eliminated
2. Replace the fan plug-in box. Check if the alarm is eliminated.
Rack door access control alarm

Alarm level: 3
Alarm Cause The related rack door is not closed.
Handling Flow 1. Check if the rack door is closed.
f If no, close the door. Check if the alarm is eliminated
2. Check if the door access control system is correctly
connected. If no, correctly connect it, close the door, and
then check if the alarm is eliminated.
Smoke alarm
Alarm level: 3
Alarm Cause The smoke detector detects smoke.
Handling Flow Check if smoke exists in the equipment room. If yes, dispel the
smoke and then check if the alarm is eliminated.

Infrared alarm
Alarm level: 3
Alarm Cause The infrared of the equipment room is higher than the preset
threshold.
Handling Flow 1. Check if there is any animal around the infrared sensor.
f If yes, keep them away from the sensor. Check if the
2. Check if the infrared sensor is correctly configured. If no,
modify the configuration and then check if the alarm is
eliminated.
Lightning alarm
Alarm level: 3
Alarm Cause The equipment room is influenced by thunderstroke in bad
weather.
Handling Flow Check if there is lightning hazard. If yes, take protection
measures. Check if the alarm is eliminated.
SNTP server invalid

Alarm level: 3
Alarm Cause The network communication is faulty.
The server is faulty.
Influence Board clocks cannot be synchronized.
Handling Flow 1. Check if the physical link is normal by using the ping
command.
f If no, rectify physical link faults.
2. Check if the IP address of the server is correct. If no,
configure the IP address again.

Fault on Board (GPS)

Alarm level: 1
Alarm Cause A class fault.
f ICM/CLKD/CLKG board output clock is lost. The output
detects the device.
f For ICMC board, A class fault is due to FPGA detection,
including 16 chip unlock and loss, 12.8M unlock and loss,
PP2S output loss, 8K output loss, and 10M output loss.
B class fault
The GPS module of ICMC board generates B class fault due
to single-chip computer detection, such as feeder short
circuit, circuit break, large 10M OCXO auxiliary phase
difference.
Power on status
The GPS module of the ICMC board is in the power on status.
This alarm is not generated 2 minutes before the board is
powered on, when ENUM board is opened, or when the
single-chip computer is downloaded. In this case, the
background does not generate alarms and the diagnosis and
alarm may be inconsistent.
Influence The SETS chip or GPS module works exceptionally.
Handling Flow For A class faults or continuous power-on status, replace the
faulty board.
QoS Alarms
Inter-board Message Communication
Flow Rate Over Alarm Threshold
Alarm level: 3
Alarm Cause The system calculates the communication flow rate in a period
and determines if the communication flow rate in input/output
direction of the control panel is more than the alarm threshold.
If it exceeds the threshold, the alarm is generated.
Influence Packets may be lost.
Handling Flow Check if the threshold is reasonable.

If no, modify the configuration and synchronize the data.

If yes, check if the configuration module has problems based
on the alarm details.

DSP overload (Level 1 alarm)
Alarm level: 2
Alarm Cause The DSP load exceeds the preset high threshold.
Influence Voice quality is reduced. Call loss may also be caused.
Handling Flow Check if the threshold is reasonable. If yes, reduce the traffic. If
no, modify the threshold setting.

Alarm level: 3
Alarm Cause The DSP load exceeds the preset medium threshold.
Influence Voice quality is reduced.
Handling Flow Check if the threshold is reasonable. If yes, reduce the traffic. If
no, modify the threshold setting.

Alarm level: 3
Alarm Cause The DSP load exceeds the preset low threshold.
Influence Voice quality may be reduced.
Handling Flow Check if the threshold is reasonable. If yes, do not add traffic
any more. If no, modify the threshold setting.

MTP2 link reception overload

Alarm level: 2
Alarm Cause The traffic on the peer end is heavy.
Association congested
Alarm level: 3
Alarm Cause The service is busy.
The loads among associations are unbalanced.
The association resource is insufficient.
Influence Messages are lost.

3. Check if association resources are sufficient.
f If sufficient, check if loads are evenly shared among
associations. If yes, go to step 1. If no, go to step 4.
f If insufficient, add new associations and check if this
STC office congested

Alarm level: 3
Alarm Cause A congested association leads to the office congestion.
Influence Messages may be discarded due to congestion. Thus, calls may
be lost and associations may be broken.
3. Check if association resources are sufficient.
f If sufficient, check if each association is congested. If yes,
handle the problem by referring to “Association
congested”. If no, go to step 4.
f If insufficient, add new associations and check if this


Appendix A
Abbreviations
Abbreviation Full Name
A
AAL2 ATM Adaptation Layer 2
AAL5 ATM Adaptation Layer type 5
AEM Antenna Equipment Module
AIS Alarm Indication Signal
AIU A Interface Unit
AMR Adaptive Multi Rate
APBE ATM Process Board Enhanced version
APS Automatic Protection Switching
AS Application Server
ASP Application Server Process
ATM Asynchronous Transfer Mode
B
BCSN Backplane of Circuit Switch Network
BCTC Backplane of ConTrol Center
BGSN Backplane of Giga Universal Service Network
BHCA Busy-Hour Call Attempts
BIPB Abis Interface Processing board
GIPI BSC IP Interface board
BIU aBis Interface Unit
BPSN Backplane of Packet Switch Network
BSC Base Station Controller
BSS Base Station System
BSSAP Base Station System Application Part
BSSGP Base Station System EDGE/GPRS Protocol
BTS Base Transceiver Station
BUSN Backplane of Universal Switch Network
C
CAS Channel Associated Signaling

CC Calling Control
CCS Common Channel Signaling
CCS7 Common Channel Signaling System NO.7
CDU Combiner Distribution Unit
CEU Combiner Extension Unit
CHP Channel Processor
CHUB Control plane HUB
CIP Carrier Interface Part
CLKG Clock Generator
CM Communication Management
CMB Control & Maintenance Board
CMM Controller & Maintenance Module
CMP Control Main Processor
CN Core Network
CPU Central Processing Unit
CS Circuit Switch
CSU Channel Service Unit
CU Carrier Unit
D
DBS Data Base Subsystem
DC Direct Current
DCE Data Circuit terminating Equipment
DDF Digital Distribution Frame
DDN Digital Data Network
DFCM Dual -carrier Fan Cortrol Module
DRTB Dual Rate Transcoder Board
DSP Digital Signal Processor
DTB Digital Trunk Board
DTE Data Terminal Equipment
DTRU Dual -carrier Transceiver Unit
DTU Digital Trunk Unit
DTX Discontinuous Transmission
DXC Digital CrosS Connection
E
EAM External Alarm Module
EIPI E1 IP Interface
EIR Equipment Identification Register
EMC ElectroMagnetic Compatibility
EMI Electro Magnetic Interference
ETSI European Telecommunications Standards Institute
ETSN Enhanced TDM Switch Network Board

Appendix A Abbreviations
F
FAM Fan Alarm Module
FCLK Frame Clock
FCM Fan Control Module
FCU Fused Combiner Unit
FDM Fan Driver Module
FE Fast Ethernet
FIB Fast-ethernet Interface Board
FN Frame Number
FNCB Fan Control Board
FNIB Fan Interface Board
FR Frame Relay
FRS Full Rate Service
FSMU Far SubMultiplexing Unit
FUC Frame Unit Controller
G
GERAN GSM/EDGE Radio Access Network
GIPB Gb Interface Processing board
GIPI GE IP Interface
GIU Gb Interface Unit
GLI Gigabit Line Interface
GND GrouND
GNDP GrouND Protection
GPRS General Packet Radio Service
GPS Global Position System
GSM Global System for Mobile Communication
GUIM Gigabit universal Interface Module
GUP GSM Universal Processing board
GUP2 GSM Universal Processing board
H
HBTS Home-BTS
HDLC High-level Data Link Control protocol
HLR Home Location Register
HPI Host Port Interface
HSCSD High Speed Circuit Switched Data
HTRU Home-BTS Transceiver Unit
HW High Way line
I
ICM Integrated Clock Module
IMA Inverse Multiplexing for ATM
IMAB IMA Board

IMSI International Mobile Subscriber Identity

IP Internet Protocol
L
LAN Local Area Network
LAPD Link Access Protocol on the D channel
LLC Logical Link Control
LMT Local Management Terminal
LNA Low Noise Amplifier
LOF Lose Of Frame
LOS Lose Of Signal
M
MAC Medium Access Control
MM Mobility Management
MNIC Multi-service Network Interface Card
MS Mobile Station
MSC Mobile services Switching Center
MSS Mobile Switch System
MTP Message Transfer Protocol
N
NEF Network Element Function
NS Network Service
NSE Network Service Entity
NSMU Near SubMultiplexing Unit
O
OAM Operation Administration and Maintenance
ODF Optical Distribution Frame
OMC Operation and Maintenance Center
OMP Operation Main Processor
OMS Operating Maintenance Subsystem
OSI Open System Interconnection
OSS Operating & Support Subsystem
P
PA Power Amplifier
PACCH Packet Associated Control Channel
PAGCH Packet Access granted Channel
PBCCH Packet Broadcast Control Channel
PCH Paging Channel
PCM Pulse Code Modulation
PCU Packet Control Unit
PDP Packet Date Protocol
PDTCH Packet Data Traffic Channel

PE Protective Earthing
PLL Phase Locked Loop
PLMN Public Land Mobile Network
PPCH Packet Paging Channel
PS Packet Switch
PSN Packet Switch Network
PSPDN Packet Switched Public Data Network
PSTN Public Switching Telephone Network
PTP Point To Point
PWRD PoWeR Distributor
PWRDB PoWeR Distributor Backplane
Q
QoS Quality of Service
R
RACH Random Access Channel
RBID Rearboard of ID Interface
RCBU Resources board Configuration Basal Unit
RCHB1 Rear board 1 of CHUB
RCHB2 Rear board 2 of CHUB
RCKG1 Rear board 1 of CLKG
RCKG2 Rear board 2 of CLKG
RDI Remote Defect Indication
RDTB Rear Board of DTB
RGER Rear Card of GE for BUSN and BGSN
RGIM1 Rear General Interface Moudle 1
RGUM1 Rear board 1 of GUIM
RGUM2 Rear board 2 of GUIM
RLC Radio Link Control
RMPB Rear board of OMP
RMNIC Rear board of MNIC
RR Radio Resource
RSPB Rear Board of SPB
RSVB Rear board of Server
RTU Radio Transceiver Unit
RUIM1 Rear board 1 of UIM
S
SACCH Slow Associated Control Channel
SAPI Service Access Point Indicator
SAR Segment And Reassemble

SBCX Single Board Computer of X86

SCCP Signal Connect Control Part
SD Signal Degrade
SDCCH Stand alone dedicated Control Channel
SDH Synchronous Digital Hierarchy
SDTB Sonet Digital Trunk Board
SDTB2 Sonet Digital Trunk Board
SF Signaln Fail
SLC Signaling Link Code
SM SubMultiplexing
SMC Short Message Center
SMLC Serving Mobile Location Centre
SMS Short Message Service
SMU Subchannel Multiplexing Unit
SONET Synchronous Optical NETwork
SPB Signaling Processing Board
SPB2 Signaling Processing Board
SSM Subjoin Service Management
SSN SubSystem Number
STM-1 Synchronous Transfer Mode 1
SUA SCCP User Adaptation
SVR SerVeR board
SYNCLK SYNchronous CLocK
T
TBF Temporary Block Flow
TC TransCoder
TCH Traffic Channel
TCP Transmission Control Protocol
TCU TransCoder Unit
TDM Time Division Multiplex
TEI Terminal Equipment Identification
TFI TDM Fiber Interface board
TFO Tandem Free operation
TRM Transceiver Module
TRX Transmitter & Receiver
TS Time Slot
TTL Transistor-Transistor Logic
U
UDP User Datagram Protocol
Universal Interface Module for Control plane
UIMC
（BCTC or BPSN）

UIMU Universal Interface Module for User plane

UPPB User Plane Processing Board
UPU User Plane Process Unit
Um Um Interface
V
VLR Visitor Location Register


Tables
Table 1 Chapter Summary ....................................................i

Table 2 Typographical Conventions ...................................... iii
Table 3 Mouse Operation Conventions ................................. iii
Table 4 – Usage Explanation of the Hazardous Substances in
ZXG10 BSS (V6.20) ............................................................ v


Index
80w PA ............................ 132 interface E1 Rx forward sliding

Communication Alarms ...... 173 indication ....................... 82
Dry Contact Alarm............... 69 QoS Alarms...................... 246
Environment Alarms .......... 240 SDH/SONET ......................... 9
Equipment Alarms .................5 Trunk Link ........................... 6
Handling Alarms ............... 213 Wrong parameter configuration
input clock lose.....................7 .................................. 234
ZXG10 iBSC ..................vii, viii

ZXG10 BSS (V6.20) Base Station Subsystem Alarm Handling Manual

Uploaded by

Document Information

Original Description:

Original Title

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

ZXG10 BSS (V6.20) Base Station Subsystem Alarm Handling Manual

Uploaded by

Copyright:

Available Formats

ZXG10 BSS

Base Station Subsystem

Copyright © 2006 ZTE CORPORATION.

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

Date Revision No. Serial No. Reason for Issue

Your evaluation Accessibility:

About This Manual ............................................................ i

Declaration of RoHS Compliance..................................... v

Alarm Message Summary................................................ 1

Alarm Messages ............................................................... 5

Appendix A ................................................................... 251

Abbreviations ............................................................... 251

Tables ........................................................................... 259

Index ............................................................................ 261

Prerequisite Skill and Knowledge

What Is in This Manual

TABLE 1 CHAPTER SUMM ARY

Confidential and Proprietary Information of ZTE CORPORATION i

ii Confidential and Proprietary Information of ZTE CORPORATION

 ZXG10 iBSC (V6.20) Base Station Controller Performance

Mouse TABLE 3 MOUSE OPERATION CONVENTIONS

Confidential and Proprietary Information of ZTE CORPORATION iii

How to Get in Touch

iv Confidential and Proprietary Information of ZTE CORPORATION

To minimize the environmental impact and take more

TABLE 4 – USAGE EXPLANATION OF THE HAZ ARDOUS SUBSTANCES IN ZXG10

Confidential and Proprietary Information of ZTE CORPORATION v

The ZXG10 BSS (V6.20) Base Station Subsystem manufactured

vi Confidential and Proprietary Information of ZTE CORPORATION

Alarm Message Summary

This chapter introduces the basic concepts of alarm messages,

Alarm Code Definition

Alarm Severity Level

Confidential and Proprietary Information of ZTE CORPORATION 1

Measures must be taken to recover or eliminate the alarms

2 Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION 3

This page is intentionally blank.

4 Confidential and Proprietary Information of ZTE CORPORATION

This chapter gives a comprehensive and systematic description

Confidential and Proprietary Information of ZTE CORPORATION 5

3. Replace the local-end optical transceiver module and check if

Ethernet Controller's Physical Link

Trunk Link Is Used for CSU

6 Confidential and Proprietary Information of ZTE CORPORATION

Cell Delineation Not Synchronized

Loss of Cell Delineation

8K input clock lose

Confidential and Proprietary Information of ZTE CORPORATION 7

16M Input Clock Lose

PP2S Clock Input Lose

32M Clock lost in TSNB

8 Confidential and Proprietary Information of ZTE CORPORATION

Clock Phase Does not Match When

Clock Chip of This Board Is in

Loss of Clock When Input to Board

Confidential and Proprietary Information of ZTE CORPORATION 9

 The fiber pigtail and flange between the local-end ODF

SDH/SONET: Regenerator Section

10 Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION 11

12 Confidential and Proprietary Information of ZTE CORPORATION

ZXG10 iBSC (V6.20) Base Station Controller Performance

The fiber pigtail and flange between the local-end ODF