56783249 zxg10 bss v6 20 base station subsystem alarm handling manual 1

ZXG10 BSSBase 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: [email protected]

http://support.zte.com.cn/

mailto:[email protected]

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 Name ZXG10 BSS (V6.20) Base Station Subsystem Alarm Handling Manual

Product Version V6.20 Document Revision Number R1.0

Serial No. sjzl20083213 Equipment Installation Date

Presentation: (Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization, Appearance)

Good Fair Average Poor Bad N/A

Accessibility: (Contents, Index, Headings, Numbering, Glossary)


Your evaluation of this documentation

Intelligibility: (Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content)


Your suggestions for improvement of this documentation

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

Add more examples Add more/better quick reference aids

Add more detail Improve the index

Other suggestions

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

# 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 Pointer15 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 B2 Error Code ........................................20 SDH/SONET:Severe B3 Error Code ........................................21 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 2............................................................ 68 Dry Contact Alarm 3............................................................ 68 Dry Contact Alarm 4............................................................ 68 Dry Contact Alarm 5............................................................ 69 Dry Contact Alarm 6............................................................ 69 Dry Contact Alarm 7............................................................ 69 Dry Contact Alarm 8............................................................ 69 Dry Contact Alarm 9............................................................ 70 Dry Contact Alarm 10 .......................................................... 70 Dry Contact Alarm 11 .......................................................... 70 Dry Contact Alarm 12 .......................................................... 70

EAM Dry Contact Alarm 1 .....................................................71 EAM Dry Contact Alarm 2 .....................................................71 EAM Dry Contact Alarm 3 .....................................................71 EAM Dry Contact Alarm 4 .....................................................71 EAM Dry Contact Alarm 5 .....................................................72 EAM Dry Contact Alarm 6 .....................................................72 EAM Dry Contact Alarm 7 .....................................................72 EAM Dry Contact Alarm 8 .....................................................72 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 CHP DSP2 of TPU initialization failure ................................... 115 CHP DSP3 of TPU initialization failure ................................... 116 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 TPU CHP DSP2 overflow ................................... 119 Watchdog of TPU CHP DSP3 overflow ................................... 119 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 EAM TRX layer mixed-flow fan 2 alarm ................................. 145 EAM TRX layer mixed-flow fan 3 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 3 fan 2 alarm (for M8206).......................................... 149 Layer 3 fan 3 alarm (for M8206).......................................... 150 Layer 2 fan 1 alarm (for M8206).......................................... 150 Layer 2 fan 2 alarm (for M8206).......................................... 150

Layer 2 fan 3 alarm (for M8206) ......................................... 151 Layer 1 fan 1 alarm (for M8206) ......................................... 151 Layer 1 fan 2 alarm (for M8206) ......................................... 151 Layer 1 fan 3 alarm (for M8206) ......................................... 152 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 Status of TX2 filter alarm ................................................... 161 Status of TX3 filter alarm ................................................... 161 Status of TX4 filter alarm ................................................... 161 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 the lost of signal of the light port 2 alarm ............................. 169 light port 2 error,Loss of Frame alarm .................................. 169 the lost of signal of the light port 1 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 Fe IMA Group is in config-aborted state (because of unmatched symmertry mode) ............................................................. 222 Fe IMA Group is in config-aborted state (because of unmatched 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 Wrong Parameter configuration for TPU Ch1.......................... 229 Wrong Parameter configuration for TPU Ch2.......................... 230 Wrong Parameter configuration for TPU Ch3.......................... 230 Wrong Parameter configuration for TPU Ch4.......................... 231 Wrong Parameter configuration for TPU Ch5.......................... 231 Wrong Parameter configuration for TPU Ch6.......................... 231 Wrong Parameter configuration for TPU Ch7.......................... 232 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 Wrong parameter configuration for TRM Channel 1................. 235 Wrong parameter configuration for TRM Channel 2................. 235 Wrong parameter configuration for TRM Channel 3................. 236 Wrong parameter configuration for TRM Channel 4................. 236 Wrong parameter configuration for TRM Channel 5................. 236 Wrong parameter configuration for TRM Channel 6................. 237 Wrong parameter configuration for TRM Channel 7................. 237 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 Inter-board Message Communication DSP overload (Level 2 alarm)...................................................................................... 247 Inter-board Message Communication DSP overload (Level 3 alarm)...................................................................................... 247 MTP2 link reception overload .............................................. 248 Association congested ....................................................... 248 STC office congested ......................................................... 249

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

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

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

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

Confidential and Proprietary Information of ZTE CORPORATION i

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:

T AB L E 1 C H A P T E R S U M M AR Y

Chapter Summary

Chapter 1, Alarm Messages

Introduces the basic concepts of BSS (V6.20) alarms, including alarm definition, severity, handling suggestions, and classification

Chapter 2, Alarm Message Description

Describes the BSS (V6.20) alarms in terms of alarm cause, influence on the system,

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

ii Confidential and Proprietary Information of ZTE CORPORATION

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)

ZXG10 iBSC (V6.20) Base Station Controller Maintenance Manual (Troubleshooting)

ZXG10 iBSC (V6.20) Base Station Controller Maintenance 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)

About This Manual

Confidential and Proprietary Information of ZTE CORPORATION iii

ZXG10 iBSC (V6.20) Base Station Controller Performance Counter Manual - Volume II

ZXG10 iBSC (V6.20) Base Station Controller Performance 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

ZTE documents employ the following typographical conventions.

T AB L E 2 TY P O G R AP H I C AL C O N V E N T I O N S

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.

T AB L E 3 M O U S E OP E R AT I O N C O N V E N T I O N S

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

Typographical Conventions

Mouse Operation

Conventions


iv Confidential and Proprietary Information of ZTE CORPORATION

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.

If you have problems, questions, comments, or suggestions regarding your product, contact us by e-mail at [email protected]. You can also call our customer support center at (86) 755 26771900 and (86) 800-9830-9830.

ZTE welcomes your comments and suggestions on the quality and usefulness of this document. For further questions, comments, or suggestions on the documentation, you can contact us by e-mail at [email protected]; 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.

Customer Support

Documentation Support

Confidential and Proprietary Information of ZTE CORPORATION v

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.

T AB L E 4 – U S AG E E X P L A N A T I O N O F T H E H AZ AR D O U S S U B S T AN C E S I N 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.


vi Confidential and Proprietary Information of ZTE CORPORATION

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.

Confidential and Proprietary Information of ZTE CORPORATION 1

C h a p t e r 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.


2 Confidential and Proprietary Information of ZTE CORPORATION

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.

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


C h a p t e r 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 code: 198000002

Alarm level: 2

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.

The link connected to the fiber circuit is broken and the service is interrupted.

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.

Alarm Property

Alarm Cause

Influence

Handling Flow



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

4. Replace the peer-end optical transceiver module and check if the alarm is eliminated.

5. Check if the peer-end device forcibly inhabits output and if the alarm is eliminated.

UIM consists of UIMC, UIMU, and UIMT.

Ethernet Controller's Physical Link Off


Alarm level: 3

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.

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.

1. Check if network interface OMC2 is connected with network cables and if they are loose.

If the cables loose, go to step 2.

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

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

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Chapter 2 Alarm Messages


starts. If this trunk link is not used for CSU loopback test, this alarm won't be triggered.

The configured trunk link is congested.

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

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.

The ATM communication becomes worse.

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

LCD is triggered after OCD lasts for 4 ms.

The ATM communication is broken.



8K input clock lose


Alarm level: 3

The clock input of the shelf is abnormal.

The system communication fails.

Check whether the clock input line is correctly connected.

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



16M Input Clock Lose


Alarm level: 3



Check whether the clock input line is correctly connected.

PP2S Clock Input Lose


Alarm level: 3



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

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.

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.

Check if the clock input lines are correctly connected.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Clock Phase Does not Match When Inputting 8k,16M Clock to Backboard


Alarm level: 3

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

The board experiences reset. The SETS chip and the constant-temperature crystal oscillator needs to be fully preheated.

The output clock is unstable.

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

The upstream optical transmission device is faulty.

The optical fiber transmission line is faulty.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause



The fiber pigtail and flange between the local-end ODF (optical distribution frame) and equipment are faulty.

The local-end optical receiver is faulty.

All the trunk receiving signals that are transmitted through the SDH/SONET line are interrupted.

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).

If yes, go to step 3

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.

If yes, go to step 5.

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

The upstream SDH devices are faulty.


Ask SDH transmission equipment maintenance personnel to rectify the faults.

SDH/SONET: Regenerator Section Trace Mismatch/Section Trace Mismatch


Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property



Alarm level: 2

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.

The matching relations of the trunks and trunk signals are wrong.

1. Check if the fibers are correctly connected to the ODFs at local end and peer end.


If no, correctly connect the fibers, and then check if the alarm is eliminated.

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

The upriver equipment has faults, such as LOS, LOF, and RS TIM.


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

Errors occur on the uplink direction of the downstream equipment.

All the trunk sending signals that are transmitted through the SDH/SONET line are interrupted.

Clear the “primary alarm” according to the alarm generated from the network node equipment in the corresponding multiplexing section.

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



SDH/SONET:Signal Failure


Alarm level: 2

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.

All the trunk receiving signals that are transmitted through the SDH/SONET line generate large numbers of alarms.

1. Check if the fiber pigtail heads are contaminated.

If yes, clean the connectors, and then check if the alarm is eliminated.

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.

If yes, adjust the attenuation, and then check if the alarm is eliminated.


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

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.

Some trunk receiving signals generate various alarms.

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.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



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

The upstream AU-4 pointer processing unit is faulty.


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

The upstream VC-4 channel control unit is faulty.

All the trunk receiving signals that are transmitted through the SDH line are interrupted.

Ask maintenance personnel for transmission network to check if the VC-4 channel control unit of the upstream device is faulty.

SDH/SONET:HP-Trace Mismatch/ Patch Trace Mismatch


Alarm level: 2

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.

The matching relations of all the trunk signals are wrong.



Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow




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

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.


Ask maintenance personnel for transmission network to check if the VC-4 channel control unit (C2) of the upstream device is faulty.

DH/SONET:HP Label Mismatch/Path Label Mismatch


Alarm level: 2

During project installation, the internal cross connection of SDH network is not complete.


Ask maintenance personnel for transmission network to check if 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 Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause



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


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

The upstream VC-4 channel control unit is faulty.


Ask maintenance personnel for transmission network to check if 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

The upstream TU pointer processing unit is faulty.

The trunks that the tributary bears stop receiving trunk signals.

Ask maintenance personnel for transmission network to check if 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

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause



The upstream TU-12 pointer processing unit is faulty. The fault may be TU AIS, TU LOM, TU LOP, or TU UNEQ.

All the E1 lines that the tributary bears stop receiving trunk signals.

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

The local end TU-12 tributary malfunctions.

The devices on other nodes on the TU-12 tributary have tributary function faults.

The trunks that the tributary bears stop receiving send trunk signals.

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.

If the connection is correct and there is no fault, go to step 3.

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

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property



The upstream TU-12 tributary control unit is faulty.


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.

If the connection is correct and there is no fault, go to step 3.

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.


SDH/SONET:LP-Trace Mismatch/ Virtual Tributary Trace Mismatch


Alarm level: 4

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.

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.

If no, set the same value. Check whether the alarm is eliminated.



Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



SDH/SONET:LP-Unloaded/Virtual Tributary Unloaded


Alarm level: 4

During project installation, the internal cross connection of SDH network is not complete, or the remote device isn't equipped with the tributary.


1. 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 modules are not loose. Check if the alarm is eliminated.

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

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

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



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


SDH:VC-4 Signal Failure


Alarm level: 2



The link connected to the optical path is broken.





SDH:VC-4 Signal Deterioration


Alarm level: 3


The link connected to the optical path is broken.

1. Eliminate SF for VC-4, if it occurs. Check if the alarm is eliminated.



Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow





SDH/SONET:Severe B1 Error Code


Alarm level: 2

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.

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







Alarm level: 2



The peer-end transmitting part in multiplexing section is faulty.

The local-end receiving part in multiplexing section is faulty.

B2 error code

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause



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







Alarm level: 2



The peer-end transmitting part based on higher order path is faulty.

The local-end receiving part is faulty.

B1 and B2 error codes

The voice services that the corresponding high order path bears have noises or call losses. The data service channel has error codes.





Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



SDH/SONET:Severe BIP-2 Error Code


Alarm level: 4

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.

The voice services that the tributary bears have noises or call losses. The data service channel has error codes.





SDH/SONET:MS-Remote Error Indication


Alarm level: 2





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


Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow






SDH/SONET:HP-Remote Error Indication


Alarm level: 2





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





SDH/SONET:HP Signal Failure


Alarm level: 2



Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause



All the trunk receiving signals that are transmitted through the SDH/SONET line generate large numbers of alarms.





SDH/SONET:HP Signal Deterioration


Alarm level: 2


Some trunk receiving signals generate various alarms.

1. Eliminate SF, if it occurs. Check if the alarm is eliminated.





E3S subcar transmitter direction loss of signal


Alarm level: 3

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property



Transmitter loss of signal is asserted when no transitions are observed on transmit data for at least 32 consecutive clock cycles.

The E3S subcard cannot work normally.

Reset the board.

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

The cable connection is broken.

The E3S subcard cannot work normally.

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

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.

E3 transmission is exceptional.

1. Check if the protocols used by the matching parties match each other, that is, both use E3 (E1) or T3 (T1).

If they mismatch, configure the same protocol.

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.

If they mismatch, reconfigure the board DIP switch or jumper cap on the rear insertion card. Check if the alarm is eliminated.

If they match, go to step 3.

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



3. Use a multimeter to check if the grounding signals of the equipment at both ends are reliable.

If they are unreliable, make them reliable. If the alarm is eliminated, end the alarm handling.

If they are reliable, go to step 4.

4. Check if the CLKG/ICM board locks clock (that is, TRACE is permanently green).

If the clock is not locked, lock it.

If the clock is locked, go to step 5.

5. Check if the clock references of two matching NEs or nodes are consistent.

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

The peer-end equipment is faulty.


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

The cable link is faulty.


Replace the cable and then check if the high error rate is resulted from link fault.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Board CPU overloaded


Alarm level: 2

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.

The message processing delay is prolonged. Packets are lost.

1. Query the threshold of CPU overload alarm through background and see if the value is too small.

If the threshold is small, modify the threshold. Wait for 30 seconds. Then, check if the alarm is eliminated.

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.

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 alarm is eliminated.

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

The fans do not work properly or are insufficient.

The temperature in the equipment room is too high.

High temperature in equipment room causes the CPU to automatically reset.

1. Check if the fans work normally and if the fans are insufficient.

If the fans are insufficient, add fans and power on all the fans. Wait for ten minutes. Check if the alarm is eliminated.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



If the fans are not powered on, power them on and wait for ten minutes. Check if the alarm is eliminated.

If the fans are sufficient and work normally, go to step 2.

2. Check if the temperature in the equipment room is too high.

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 the alarm is eliminated.

If the temperature is normal, go to step 3.


Board FLASH faults


Alarm level: 2

The FLASH is damaged.

All operations related to the FLASH fails.

1. Confirm if there is any standby board that can be used for replacement.

If yes, replace the board and check if the alarm is eliminated.



Inter-shelf media plane links abnormal


Alarm level: 2

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.

The media plane is interrupted.

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.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



If they are inconsistent, adjust the connection in line with the configuration requirements. Check if the alarm is eliminated.

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

The physical line or port configuration is incorrect.

The network communication capacity is insufficient.

1. Check the port connection relation of TRUNK to see if there is any incorrect connection.

If incorrect connections exist, change the port connection based on the configuration. Check if the alarm is eliminated.

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

The GE optical transceiver module is incorrectly connected with the left and right board slot on the peer-end

The media plane flow is broken.

Connect the optical fibers in cross mode. Check if the alarm is eliminated.

Internal Port of Board Is Down


Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property



Alarm level: 2

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.

The media flow cannot be transmitted through this port. If all internal ports generate alarms, the internal media flow is interrupted.

1. Check if the number of internal ports configured for this board and the neighboring slots exceeds the number of physical slots.

If yes, modify the configuration and synchronize the data. Check if the alarm is eliminated.


2. Check if the board has clock input alarms.

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. Check if the alarm is eliminated.


Board Doesn't Exist/ CPU is Long in Reset Status


Alarm level: 2

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.

The board or board CPU of this slot work exceptionally and fail to provide normal services.

1. Check if the board is correctly inserted.

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 the alarm is eliminated.

3. Replace the slot. Check if the alarm is eliminated.

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Input Clock Abnormal


Alarm level: 1

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.

The system cannot obtain the clock.

1. Check if the configured clock reference is correctly inputted.

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

The (CPU) sub-card is physically inserted in position, but it is not configured in the database.

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.

Confirm if this sub-card is required.

If yes, configure the CPU in the database. Check if the alarm is eliminated.

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

The (CPU) sub-card is configured in the database, but it is not physically inserted in position.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause



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.

1. Confirm if this sub-card is inserted in position.

If yes, pull out the board and insert the sub-card in position. Then, power on the board again. Check if the alarm is eliminated.


2. Confirm if this sub-card is required.

If yes, insert the sub-card. Check if the alarm is eliminated.

If no, delete the configuration from the database. Check if the alarm is eliminated.

External Port of Board Is Down


Alarm level: 2

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

Data fails to be transmitted through the network interface. The service may be disrupted.

1. Check if the connection between the port on this board and the peer-end one is correct.

If correct, go to step 2.

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, check if the alarm is eliminated.

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Exceptional Internal Media Plane Communication


Alarm level: 2

The packet loss rate of the internal media plane of the board exceeds the preset threshold (25% by default).

The media flow cannot transmit normally.

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 alarm is eliminated.

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. Check if the alarm is eliminated.

iii. Replace the slot. Check if the alarm is eliminated.

This problem seldom occurs.

DSP Resource Unavailable


Alarm level: 2

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.

Some DSP related services cannot work normally.

1. Query the related alarm information to locate the fault causes. Confirm if the fault can be rectified.

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow





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 alarm is eliminated.

Usage Rate of Board Hard Disk above Threshold


Alarm level: 2

The hard disk usage exceeds the threshold at a certain level.

Data may be lost if the hard disk of the board continues using.

1. Check if the threshold value configured on the background is too small.

If the value is too small, go to step 2.

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.

The hard disk usage has three levels of threshold.

Hard Disk Broken


Alarm level: 2

The hard disk of the board is faulty.

Data is lost.

1. Switch the board and use the hard disk of the new mainboard.

2. Replace the hard disk.

TRUNK port down


Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property



Alarm level: 3

The TRUNK port is not totally connected through network cables.

The network cables or BCM5615 port is faulty.

Data cannot be transmitted on the control plane.

Check if the network cables are correctly inserted and if the BCM5615 port is normal.

This alarm seldom occurs.

Broad Not Tightly Inserted


Alarm level: 2

The ENUM switch of the broad is opened.

The EXCH key on the standby board is pressed down twice within 3 seconds.

The standby board is in the cold standby state.

Other board faults occur.

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

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).

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.

1. Pull out and plug in the board. Check if alarm is eliminated.

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow




Error in Rear Board That Mismatches With Front Board


Alarm level: 3

The rear board mismatches the front board.

The resources on the rear board are unavailable.

Replace the rear board with one matching with the front board, and then check if the alarm is eliminated.

The boards of some old versions do not provide the function of version detection for rear board.

LVDS Signal Unlocked


Alarm level: 2

LVDS signal at the bottom layer is unlocked.

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.

Switch or pull out and plug in the board. Check if the alarm is eliminated.


High Error Rate of Optical Interface


Alarm level: 2

The optical fiber is not connected in position or is damaged.

The optical fiber does not match the optical transceiver module.

The data transmitted through the optical interface is incorrect.

1. Check if the optical fiber is connected in position and if it is damaged.


Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow



If the fiber is not connected in position, correctly connect it. Check if the alarm is eliminated.

If the fiber is damaged, replace with another one. Check if the alarm is eliminated.

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

FPGA runs exceptionally. For example, FPGA is lost and the mother board clock is lost.

The board cannot work normally.

Restart the board and then the board downloads EPGA again.


Port Link Down


Alarm level: 2

There is something wrong with the lan91 chip or bcm5328 chip.

The DSP works abnormally. Call drops are increased.

1. Reset the DSP chip by using MML commands on the background. Check if the alarm is eliminated.


Hardware Reliability Down


Alarm level: 2

The hardware of the hard disk has faults.

Data is lost.

The system is collapsed.

1. Use a new hard disk and configure it. Then, check if the alarm is eliminated.

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



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

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.

The specified reference clock cannot lock phase.

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

The hardware of the sub-card channel has faults or it is not inserted in position.

A single channel cannot work normally.

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

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.

The sub-card malfunctions.

1. Check the sub-card connection to see if it looses.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



If it looses, insert the card in position and then check if the alarm is eliminated.

If it does not loose, go to step 2.

2. Replace the sub-card.

Phase-lock Loop Unlock


Alarm level: 1

The phase-lock loop cannot be locked due to the hardware fault.

The clock is exceptional.

It may result from the hardware fault. Replace the board.

High Error Rate at E1 Bottom Layer


Alarm level: 2

The E1/T1 link is faulty or there is any other equipment fault in the uplink direction of the trunk link.

The trunk cannot receive trunk signals.

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 if the alarm is eliminated.

Control Plane Ports of Backplane Joining Switching Chip Is Exceptional


Alarm level: 2

The control plane ports of such boards as SPB/SPB2 are faulty or do not transceive packets for more than 3 minutes.

The path to the control plane of the backplane is blocked.

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.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



If the port is not normal, reset the UIM board. Check if the alarm is eliminated.

Type A Fault on Board (GPS) Phase-lock Equipment


Alarm level: 1

The board hardware has faults.

The SETS chip works abnormally.

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 Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property



DSP reports the port or other exceptions after detection.

The DSP works abnormally. The call loss is increased.

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

The sub-card is not in position or the hardware is faulty.

The sub-card clock cannot work normally.

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

Errors occur in LVDS path frame detection

The board may fail to work.

1. Check if the TFI optical fiber corresponding to this path is connected in place or if it is damaged.

If the fiber is connected in place and not damaged, go to step 2.

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 the alarm is eliminated.

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.

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Tier1 Network Link Loopback Diagnosis Failure


Alarm level: 2

129 Time slot loopback of LVDS has a failure.

The board may fail to work normally.

1. Check if the TFI optical fiber corresponding to this path is connected in place or if it is damaged.

If the fiber is connected in place and not damaged, go to step 2.

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 the alarm is eliminated.

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

The physical link between master port and slave port is broken.

The APS function does not take effect.



Media interactive GE port link down


Alarm level: 4

The APS is configured. The physical link between media interactive GE ports is broken.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause



The APS time is prolonged.



Board device is abnormal


Alarm level: 2

The board devices or sub-cards do not work properly.


Replace the board. Check if the alarm is eliminated.

Cx29704 Runs Abnormally


Alarm level: 3

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.

The Cx29704 chip cannot work normally.

1. Reset the board. Check if the alarm is eliminated.


Physical Channel for Data Transmission Blocked


Alarm level: 2

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.

The data packet processing may be affected, which may cause the services that the board bears to be unstable.

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence



1. Restart the board where the alarm happens (board of Release version can restart automatically). Check if the alarm is eliminated.

2. Check if PSN in the same shelf has fault.

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

The alarm is generated when BIPI/GIPI/EIPI board receive a certain number of hardware-error frames in a period.

The data packet processing may be affected, which may cause the services that the board bears to be unstable.

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

The near-end IMA receives the report that the far-end IMA is in the “configuration failure state” in the ICP cell.

The IMA link is broken.

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.

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



All High-Speed Links Between Line Card and Package Switching Board Are out of Synchronism


Alarm level: 1

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.

The media plane of a board cannot work. If the problem is due to PSN, the whole service is broken.

1. Check if PSN boards are set to load sharing working mode.

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.

If no, check which board is not powered on successfully through process.


3. Check if the PSN work normally.

If yes, restart the board where there is a fault and check if the alarm is eliminated.


4. Replace the board where there is a alarm reported. Check if the alarm is eliminated.

APS Channels Mismatched


Alarm level: 2

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.

The switchover fails when the configuration is 1:1.

1. Check if configurations on the two ends are both 1+1 or 1:1(1:N).

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



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

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.

The switchover result may be different from the expectation. Channels may be blocked.

1. Check if configurations on the two ends are both 1+1 or 1:1(1:N).

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

The boards are set as 1+1 mode and do not configure APS.

FE or HW fails to be opened.

The service is broken.

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.

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.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks



No Response to Requesting Database for Secondary Forwarding Table Information


Alarm level: 2

The OMP is not normally powered on.

Control plane messages are delayed.

The media flow in the shelf of the UIM is broken.

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

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.

The media flow in the shelf of the UIM is broken.

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.


Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Resource board Unable to Get Secondary Forwarding Table from UIM


Alarm level: 2

The shelf is not BUSN/BGSN.

The UIM board on the shelf is not powered on normally.

Control plane messages are blocked.

The resource board cannot get the secondary forwarding table.

1. Check if the resource shelf is BUSN/BGSN shelf.

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. Check if the alarm is eliminated.


Only the UIM in the BUSN/BGSN shelf has secondary forwarding table.

Internal Connection Chip Faults of TSNB


Alarm level: 2

Connection chip (73273/73260) faults on T network board cause some 129 time slots of HW having connection faults.

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 Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property



Bugs exist in configuration or chip.

The link may be broken.

Check the configuration. Replace the board. Check if the alarm is eliminated.

CLKG 32M output clock lost


Alarm level: 2

The CLKG/ICM 32M output clock is lost.

The system cannot obtain the required clock, which leads to exceptions in clock related processing.

Check if the CLKG/ICM output clock is normal. If no, replace the CLKG/ICM board.

CLKG 32M8K output clock lost


Alarm level: 2

The CLKG/ICM 32M8K output clock is lost.



CLKG 16M output clock lost


Alarm level: 2

The CLKG 16M output clock is lost.


Check the CLKG/ICM board and software. Replace the board. Check if the alarm is eliminated.

CLKG 16M8K output clock lost


Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property



Alarm level: 2

The CLKG/ICM 16M8K output clock is lost.



CLKG PP2S Output Clock Lost


Alarm level: 2




PP2S clock reference lost


Alarm level: 2



1. Check the type of the alarm board.

If the board is CLKG, go to step 2.

If the board is ICM, go to step 3.

2. Check if PP2S clock is correctly led to CLKG from the control rack.


If no, correctly lead PP2S clock to CLKG. Check if the alarm is eliminated.


16CHIP clock reference lost


Alarm level: 2


Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause





All clock bases had lost


Alarm level: 2

Clock base lost is detected for the first time.

The clock related processing is exceptional.

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

The I2MB0 clock base is lost.


1. Check if the 2MB0 input of RCKG1/RCKG2 is normal.


CLKG I2MB1 clock base lost


Alarm level: 3

The I2MB1 clock base is lost.


1. Check if the 2MB1 input of RCKG1/RCKG2 is normal.


CLKG I2MHZ0 clock base lost


Alarm level: 3

The I2MHZ0 clock base is lost.

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause




1. Check if the 2MHZ0 input of RCKG1/RCKG2 is normal.


CLKG I2MHZ1 clock base lost


Alarm level: 3

The I2MHZ1 clock base is lost.


1. Check if the 2MHZ1 input of RCKG1/RCKG2 is normal.


CLKG I8KBASE clock base lost


Alarm level: 3

The I8KBASE clock base is lost.


1. Check if the 8KBASE input of RCKG1/RCKG2 is normal.


CLKG I8KGPS clock base lost


Alarm level: 3

The I8KGPS clock base is lost.


1. Check if the 8KGPS input of RCKG1/RCKG2 is normal.


CLKG I8KUIM clock base lost


Alarm level: 3

The I8KUIM clock base is lost.

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause




For CLKG/ICM, the base does not serve as the base source.

Clock reference source lost (Level 3 alarm)


Alarm level: 3

Clock base lost is detected for the first time.


Check if the corresponding clock reference is correctly led in.


If no, correctly lead in this clock reference. Check if the alarm is eliminated.



Alarm level: 2

Clock reference lost has been detected for more than 10 minutes.







Alarm level: 1

Clock reference lost has been detected for more than 24 hours.


Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence






Clock Base Lost


Alarm level: 3

The clock base configured on the background is lost.


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

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property



DSP's load has reached a dangerous degree.

The voice quality is poor and call loss may occur.

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

80g detects that the gliqp board restarts, or the 80g chip is abnormal.

Media plane partially loses messages or is interrupted.

1. Restart the board for which the alarm is reported. Check if the alarm is eliminated.


SCCP SSN is invalid


Alarm level: 3

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.

User fails to transceive messages on the subsystem.

1. Check through Alarm Management whether there is any alarm prompting this adjacent office inaccessible.

If MTP3 office inaccessible alarms or M3UA office inaccessible alarms exist, perform further handling according to the office inaccessible alarms.

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.


If no, configure the subsystem. Then, check if the alarm is eliminated.

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



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.


If no, contact the personnel of the peer-end office to configure the data. After the configuration is complete, check if the alarm is eliminated.


Back up related local office configuration data and peer-end office configuration data.

Back up related local office and peer-end office history alarms and notifications, as well as current alarms.

Broadband link congestion


Alarm level: 3

The traffic is heavy.

The loads among links are unbalanced.

The link resource is insufficient.

The link is congested, which may cause package losses and call drops.

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.

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.

If insufficient, add new links and check whether this alarm is eliminated. If no, use the above method for sufficient link resources.




Alarm Property

Alarm Cause

Influence

Handling Flow



Broadband link overload


Alarm level: 3




When the link is overloaded, it discards received packages. This causes call drops.











MTP2 link transmission overload


Alarm level: 2




Messages fail to be transceived.




Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow










MTP3 office inaccessible


Alarm level: 2

Office and route configuration has error.

The link is broken

Corresponding office fails to be transceive messages.

1. Check whether the static route settings of the destination office are correct.


If no, configure or modify the corresponding static route. Check if the alarm is eliminated.

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.

If yes, perform further handling as described in “MTP3 link unavailable”.





Alarm Property

Alarm Cause

Influence

Handling Flow



MTP3 link unavailable


Alarm level: 3

The link is physically blocked.

Link test failed.

CMP board is restarted or SPB/SPB2 board is restarted.

Corresponding office fails to be transceive messages.

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.


If no, modify the configuration. Check if the alarm is eliminated.

2. Check whether there is any alarm for bottom layer transmission.

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.

If yes, ask a transmission engineer to handle the problem.





MTP3 cluster inaccessible


Alarm level: 2

The cluster and route configuration are incorrect.

The link is broken.

The corresponding office fails to transceive messages.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



1. Check whether the static route settings of the destination cluter are correct.


If no, configure or modify the corresponding static route. Check if the alarm is eliminated.

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.

If yes, perform further handling as described in “MTP3 link unavailable”.





MTP3 link congestion


Alarm level: 2




The corresponding office fails to transceive messages.








Alarm Property

Alarm Cause

Influence

Handling Flow






M3UA office inaccessible


Alarm level: 2

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.


User fails to transceive messages to the corresponding office.

1. Check the configuration data to see whether SIO location of this office is configured.


If no, configure the SIO location data. Then, check if the alarm is eliminated.

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.

If there are ASPs activated under this AS and the number of them exceeds the necessary number N, go to step 6.

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.

If the association is activated but the ASP is not, go to step 5.

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.


Alarm Property

Alarm Cause

Influence

Handling Flow






SUA SSN is invalid


Alarm level: 3

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.


1. Check through Alarm Management whether there is any alarm prompting this adjacent office inaccessible.

If SCCP User Adaptation (SUA) office inaccessible alarms exist, perform further handling as described in “SUA office inaccessible.”

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.


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.


If no, contact the personnel of the peer-end office to configure the data. After the configuration is complete, check if the alarm is eliminated.





Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks



SUA office inaccessible


Alarm level: 2

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.


1. Check configuration data to see whether SSN location of this office is configured.

If yes, go o step 2.

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.

If there are ASPs activated under this AS and the number of them exceeds the necessary number N, go to step 6.

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.

If the association is activated but the ASP is not, go to step 5.

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 Property

Alarm Cause

Influence

Handling Flow

Alarm Property



Alarm level: 3

The association is broken.

Upper layer services are stopped.

The peer end originates a release.

The messages are discarded.

1. Check whether the association for M2PA link is available by checking for alarms for related association broken in Alarm Management.


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.


If no, change protocols to be consistent. Check if the alarm is eliminated.

3. Check whether the associations used at the two end of the M2PA link are consistent.

If the associations are consistent and available, go to step 4.

If the associations are inconsistent, change the associations to be consistent. Check if the alarm is eliminated.




BSC IP configuration error


Alarm level: 2

The BSC IP configured in the database is incorrect.

The protocol stack fails to be powered on. The board cannot work normally.

1. Check whether BSC IP is configured.


If no, configure BSC IP. Check if the alarm is eliminated.

2. Check whether the BSC IP is all 0s or all 1s.

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow




If yes, change the BSC IPs. Check if the alarm is eliminated.

3. Check whether the communication between BIPI/GIPI and OMP is normal.


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

The T-net center board has a fault.

T-net resources are unavailable.



EPU and RPU Version Not Match


Alarm level: 2

The versions of EPU and RPU do not match.

The EPU cannot be powered on normally.

Change the EPU version to the one matching the RPU version. Check if the alarm is eliminated.

Abnormal Status in SDH/SONET


Alarm level: 3

The upstream optical transmission device is faulty.

All the trunk receiving signals that are transmitted through the 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.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

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.

If no fault exists, go to step 3

If there is fault, go to step 2.

2. Correctly connect the optical fibers. Check if the alarm is 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. Check if the alarm is eliminated.


5. Ask maintenance personnel special for transmission equipment to do troubleshooting.

SDH/SONET:Excessive Error Code


Alarm level: 2


All the trunk receiving signals that are transmitted through the 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.





Alarm Property

Alarm Cause

Influence

Handling Flow



ATM Communication Abnormally


Alarm level: 3

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.

The ATM communication is interrupted.



MCC Abnormal


Alarm level: 2

The MCC hardware is faulty.

All MCC channels cannot transceive data.

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

The APS channel between master and slave boards is faulty.

The connection on the backplane between the slot and the neighboring slot gets errors.

The APS function is affected.

The active/standby function of the board is affected.

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.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Dry Contact Alarm 1


Alarm level: not defined

Dry contact alarm 1.

None.

None.

User-defined

Dry Contact Alarm 2




None.

None.

User-defined

Dry Contact Alarm 3




None.

None.

User-defined

Dry Contact Alarm 4




None.

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence



None.

User-defined

Dry Contact Alarm 5




None.

None.

User-defined

Dry Contact Alarm 6




None.

None.

User-defined

Dry Contact Alarm 7




None.

None.

User-defined

Dry Contact Alarm 8




None.

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence



None.

User-defined

Dry Contact Alarm 9




None.

None.

User-defined

Dry Contact Alarm 10




None.

None.

User-defined





None.

None.

User-defined





None.

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence



None.

User-defined

EAM Dry Contact Alarm 1




None.

None.

User-defined




Dry contact alarm 2

None.

None.

User-defined





None.

None.

User-defined





None.

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence



None.

User-defined





None.

None.

User-defined





None.

None.

User-defined





None.

None.

User-defined





None.

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence



None.

User-defined

CMM/CMB FLASH programming failure


Alarm level: 3

Too many times of FLASH programming leads to read/write error.

Any version fails to be loaded and read/write.

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

CMM/CMB power voltage is out of adjustment range.

CMB works exceptionally.

Replace CMM/CMB board as soon as possible.

13M input clock failure


Alarm level: 3

CMM/CMB clock unit works exceptionally.

BTS internal transmission link is interrupted. Frame numbers are out of order. The frequency synthesizer is exceptional.

Replace CMM/CMB board as soon as possible.

Frame No. inconsistent between software and hardware


Alarm level: 3

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property



Interference level on the circuit causes frame number accumulation to interrupt.

TPU frame No. is out of order. All DTRUs of the CMB works abnormally.

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

CMM/CMB clock unit works abnormally.


Clock alarm is shown on front panel. Replace CMM/CMB board as soon as possible.

SYNCLK clock failure


Alarm level: 3

CMM/CMB clock unit works abnormally.


Clock alarm is shown on front panel. Replace CMM/CMB board as soon as possible.

Master and slave communication link failure


Alarm level: 4

Standby CMM/CMB board is not powered on, or communication between active and standby CMM/CMB boards has error.

Active and standby CMBs cannot be switched mutually.

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.

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Standby CMM/CMB board not present


Alarm level: 4

The standby CMM/CMB board is not inserted.

The active board cannot be switched to the standby board when errors occur. The system reliability is reduced.

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

Standby CMM/CMB board starts abnormally or is not inserted properly.

The active and standby boards cannot be switched normally.

1. Check if standby board is powered on.


If no, power on the standby 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

CMM/CMB board is power off.

CMM fails to work.

E1 interface will bridge-connect automatically. Replace the CMM/CMB board as soon as possible

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



A interface E1 Rx carrier alarm


Alarm level: 3

The alarm is due to chip fault, abnormal clock, difference from BSC clock, bad E1 connections, or others.

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.

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

If fault exists, make cables again to rectify the faults.

If no fault exists, go to step 2.

2. Tightly insert CMM/CMB and power it on again. Check if the alarm is eliminated.

3. Start the self-loop detection and check if the E1 interface self-loop detection is normal.

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






Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow









A interface E1 Tx forward sliding indication


Alarm level: 3












A interface E1 Tx backward sliding indication


Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property



Alarm level: 3












A interface E1 Rx forward sliding indication


Alarm level: 3








Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow







A interface E1 Rx backward sliding indication


Alarm level: 3












B interface E1 Rx carrier alarm


Alarm level: 3


If the problem seldom occurs, the conversation is slightly affected. If the problem frequently occurs, for example, once

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence



every several minutes, the conversation is abnormal or the link between TRM/DTRU and BSC is abnormal.










B interface E1 Rx frame not synchronized


Alarm level: 3












Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



B interface E1 Tx forward sliding indication


Alarm level: 3












B interface E1 Tx backward sliding indication


Alarm level: 3






Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow









B interface E1 Rx forward sliding indication


Alarm level: 3












B interface E1 Rx backward sliding indication


Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property



Alarm level: 3












C interface E1 Rx carrier alarm


Alarm level: 3










Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow





C interface E1 Rx frame not synchronized


Alarm level: 3












C interface E1 Tx forward sliding indication


Alarm level: 3



Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow












C interface E1 Tx backward sliding indication


Alarm level: 3












Alarm Property

Alarm Cause

Influence

Handling Flow



C interface E1 Rx forward sliding indication


Alarm level: 3












C interface E1 Rx backward sliding indication


Alarm level: 3






Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow









D interface E1 Rx carrier alarm


Alarm level: 3












D interface E1 Rx frame not synchronized


Alarm level: 3

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause














D interface E1 Tx forward sliding indication


Alarm level: 3









Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow






D interface E1 Tx backward sliding indication


Alarm level: 3












D interface E1 Rx forward sliding indication


Alarm level: 3



Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence












D interface E1 Rx backward sliding indication


Alarm level: 3












Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



E interface E1 Rx carrier alarm


Alarm level: 3












E interface E1 Rx frame not synchronized


Alarm level: 3






Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow









E interface E1 Tx forward sliding indication


Alarm level: 3












E interface E1 Tx backward sliding indication


Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property



Alarm level: 3












E interface E1 Rx forward sliding indication


Alarm level: 3








Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow







E interface E1 Rx backward sliding indication


Alarm level: 3












F interface E1 Rx carrier alarm


Alarm level: 3


If the problem seldom occurs, the conversation is slightly affected. If the problem frequently occurs, for example, once

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence



every several minutes, the conversation is abnormal or the link between TRM/DTRU and BSC is abnormal.










F interface E1 Rx frame not synchronized


Alarm level: 3












Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



F interface E1 Tx forward sliding indication


Alarm level: 3












F interface E1 Tx backward sliding indication


Alarm level: 3






Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow









F interface E1 Rx forward sliding indication


Alarm level: 3












F interface E1 Rx backward sliding indication


Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property



Alarm level: 3












G interface E1 Rx carrier alarm


Alarm level: 3










Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow





G interface E2 Rx frame not synchronized


Alarm level: 3












G interface E1 Tx forward sliding indication


Alarm level: 3



Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow












G interface E1 Tx backward sliding indication


Alarm level: 3












Alarm Property

Alarm Cause

Influence

Handling Flow



G interface E1 Rx forward sliding indication


Alarm level: 3












G interface E1 Rx backward sliding indication


Alarm level: 3






Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow









H interface E1 Rx carrier alarm


Alarm level: 3












H interface E3 Rx frame not synchronized


Alarm level: 3

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause














H interface E1 Tx forward sliding indication


Alarm level: 3









Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow






H interface E1 Tx backward sliding indication


Alarm level: 3












H interface E1 Rx forward sliding indication


Alarm level: 3



Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence












H interface E1 Rx backward sliding indication


Alarm level: 3












Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Temperature alarm


Alarm level: 4

The alarm is due to fan fault or too high module temperature.


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

The fan is not inserted or not in position.

TRM/DTRU temperature is too high and the performance indices are affected.

Insert the fan, or pull out and plug in the fan again.

Fan control board CPU alarm


Alarm level: 4

The CPU is faulty.

The fan is out of control but heat elimination is not affected.

1. Check if the line has faults.

If yes, rectify the faults.


2. Change the fan control pane DFCM/FNCB.

Fan control board CPU alarm


Alarm level: 4

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property



The fan stops rotating due to fault.

The frequency shelf on the same layer has high temperature.

1. Check if the fan stops rotating.

If it stops, change the fan subrack.


2. Check if the link between the fan and the fan control board is faulty.

If faults exist, go to step 3.


3. Check if the fan cables have faults and if the board-to-board connectors have faults.

If the fan cables have faults, change the fan subrack.

If the board-to-board connectors have faults, change the fan control board DFCM/FNCB.

4. Check if the alarm line is faulty.

If yes, troubleshoot the alarm line.


5. Check if alarm collection on the fan control board is exceptional.

If exceptions occur, change the fan control board DFCM/FNCB.

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




Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Fan 1 alarm


Alarm level: 4



















Fan 2 alarm


Alarm level: 4






Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow
















Fan control board alarm


Alarm level: 4




LNA alarm


Alarm level: 3

LNA current exceeds by 30%.

The connected TRM/DTRU cannot work completely (if both active and density LNAs are faulty) or cannot work normally (only one LNA is faulty).

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence



Replace AEM module as soon as possible.

Tower amplifier power alarm


Alarm level: 4

The problem is caused by AEM tower amplifier alarm.

The uplink receiver sensitivity of the related TRM/DTRU is affected.

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

The problem is caused by combiner SWR 1.5 alarm.

The emission is affected.

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




Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow






AEM power alarm(BTS V2)


Alarm level: 2

The problem is caused by AEM power alarm.


Replace AEM as soon as possible.

AEM type alarm(BTS V2)


Alarm level: 2



1. Check if the board DIP switch on the AEM is correct.

If yes, power it on again and reset the connected frequency. Check if the alarm is eliminated.

If no, adjust the board DIP switch.

2. Change AEM. Reset the connected frequency.

AEM absent(BTS V2)


Alarm level: 2

The problem is caused by AEM not-in-position alarm.






Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



AEM power alarm


Alarm level: 2



Replace AEM as soon as possible.

LNA0 alarm


Alarm level: 3

LNA0 current exceeds by 30%.

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

LNA1 current exceeds by 30%.

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

The problem is caused by AEM tower amplifier0 alarm.

The uplink receiver sensitivity of the related DTRU is affected.



Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow




Tower Amplifier1 power alarm


Alarm level: 4

The problem is caused by AEM tower amplifier1 alarm.

The uplink receiver sensitivity of the related DTRU is affected.




SWR of AEM HYCOM minor alarm


Alarm level: 3

The problem is caused by combiner SWR minor alarm.






SWR of AEM HYCOM major alarm


Alarm level: 2

The problem is caused by combiner SWR major alarm.



Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow






AEM type alarm


Alarm level: 2

The problem is caused by AEM type alarm.






AEM Not-in-position alarm


Alarm level: 2

The problem is caused by AEM not-in-position alarm.






CHP DSP0 of TPU initialization failure(BTS V2)


Alarm level: 3

The problem is caused by DSP software or hardware error.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause



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.

1. Download software of DSP again.

2. Reset TRM/DTRU shelf and restart DSP. Check if the alarm is eliminated.

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.

If the alarm cannot be eliminated, replace the TRM/DTRU module.

CHP DSP1 of TPU initialization failure


Alarm level: 4


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.







Alarm level: 4




Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow








Alarm level: 4







Uplink of ADC chip initialization failure


Alarm level: 3

The problem is caused by uplink ADC chip initialization failure.

The TRM/DTRU is unavailable. If it is BCCH carrier, the normal operation of the whole cell is affected.

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.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Uplink of ADC resource can't be used


Alarm level: 3

The problem is caused by unavailability of uplink ADC resource (uplink data lost suddenly).


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

The alarm is caused by uplink/downlink loop data demodulation failure.


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

Errors occur during the receipt of uplink data.


1. Reset the module.

2. Replace the module if the reset does not solve the problem.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



TPU FLASH Memory failure(BTS V2)


Alarm level: 3

Too many times of FLASH programming leads to read/write error or software checksum error.

The baseband processing unit fails to obtain the correct software version from FLASH MEMORY. The whole carrier unit (CU) cannot work normally.

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

DSP0 of channel processing unit has no response temporarily.

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.


If the alarm is eliminated, it is inferred that the alarm is 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.

Watchdog of TPU CHP DSP1 overflow


Alarm level: 4


Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause









Alarm level: 4








Alarm level: 4




Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow





Watchdog of FUC overflow


Alarm level: 3

FUC program has no response temporarily.

The eight channels of the TRM/DTRU are not applicable. If this fault occurs during a conversation, calls may be dropped.

Reset TPU to solve this problem. If the alarm is not eliminated, change TRM/DTRU.

CIP of TPU initialization failure


Alarm level: 3

This alarm is caused by DSP software or hardware error.

The modulation module cannot work. The carrier or cell (when the carrier is assigned BCCH) cannot work normally.

1. Download the DSP software again.

2. Reset TRM/DTRU and restart DSP. Check if the alarm is eliminated.

If the alarm is eliminated, the DSP initialization failure is due to strong exterior interference. The TRM/DTRU can work normally.

If the alarm is not eliminated, change the TRM/DTRU.

Watchdog of TPU CIP overflow


Alarm level: 4

DSP program of demodulation module has no response temporarily.

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

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence



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

The clock between TPU and CMM is disconnected.

The FUN fails to work. If the FUN is BCCH-TPU, the cell service is affected.

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

The power module on the TPU board has alarms.

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

Replace the corresponding carrier.

TPU frame No. alarm


Alarm level: 3

Frame clock FCLK has problem and upper-level frame number synchronization source CMM has problem.

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence



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

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

This problem is caused by DSP software or hardware error.

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.

If the alarm is eliminated, the DSP initialization failure is due to strong exterior interference. The DTRU can work normally.

If the alarm is not eliminated, change the DTRU.

ADC resource unavailable


Alarm level: 3

The AD6650 resource is unavailable (uplink data is lost suddenly and AD6650 initialization fails).

The TRM/DTRU cannot to work normally. If the TRM/DTRU is BCCH carrier, the cell service is affected.

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.

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



CHP frame error


Alarm level: 3

Frame clock FCLK has problem and upper-level frame number synchronization source FUC has problem.

The DTRU fails to work. If the DTRU has BCCH carrier, the cell service is affected.




BURST interrupt error


Alarm level: 3



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

Too many times of FLASH programming leads to read/write error or software checksum error.

The baseband processing unit fails to obtain the correct software version from FLASH MEMORY. The whole carrier unit (CU) cannot work normally.


Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



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 DTRU module.

TPU CHP DSP0 watchdog overflow


Alarm level: 3

Channel processing unit DSP0 has no response temporarily.

If channel processing unit DSP0 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.



If the alarm is not eliminated, start the BCCH switchover policy on the BSC and replace DTRU.

CU intialization failure


Alarm level: 3

This problem is caused by DSP software or hardware error.

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.

If the alarm is eliminated, the DSP initialization failure is due to strong exterior interference. The module can work normally.

If the alarm is not eliminated, change the module.

TPU power alarm


Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property



Alarm level: 2

The power module on TPU board has alarm.

The DTRU cannot work. If the STRU is BCCH, the cell service is affected.

Replace the module.

TPU's FN alarm


Alarm level: 3

Frame clock FCLK has problem and upper-level frame number synchronization source FUC has problem.





Rx PLL1 unlock


Alarm level: 3

Clock signal is unstable or TRM Phase-Locked Loop (PLL) fault.

Conversation may fail on the TRM/DTRU.




Rx PLL2 unlock


Alarm level: 3


Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause







Tx PLL1 unlock


Alarm level: 3






Tx PLL2 unlock


Alarm level: 3






52M referenced clock PLL unlock


Alarm level: 3






Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Tx IF PLL unlock


Alarm level: 3






EEPROM resource can't be used


Alarm level: 3

This alarm is caused by EEPROM fault.

The TRM/DTRU is unavailable.

Replace the TRM/DTRU as soon as possible.

FPGA interface failure


Alarm level: 3

The communication between DSP and FPGA interface is broken.

The TRM/DTRU is unavailable.

Replace the TRM/DTRU as soon as possible.

PA VSWR alarm(BTS V2)


Alarm level: 3

The reverse power is too high. It may be caused by the existence of open circuit or high resistance in output end of PA.

Conversation fails on the TRM/DTRU. The PA is damaged.

1. Reset TRM/DTRU. Check if the alarm is eliminated.

2. Replace the RF cables from TRM/DTRU to AEM. Check if the alarm is eliminated.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



3. Replace TRM/DTRU.

PA overtemperature minor alarm(BTS V2)


Alarm level: 4

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.

The TRM/DTRU can work, but the PA degradation speeds up.

1. Check if the fan can work normally.


If no, rectify the faults. Check if the alarm is eliminated.

2. Check if the environment temperature is too high.


If no, improve the equipment room environment. 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


The power output of the TRM/DTRU is protectively shutdown. PA degradation speeds up.






Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow






PA output power alarm


Alarm level: 3

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.

Conversations may fail on the TRM/DTRU. The power control fails.

1. Reset the TRM/DTRU. Check if the alarm is eliminated.

2. Replace the RF cables between TRM/DTRU to AEM. Check if the alarm is eliminated.

3. Replace the TRM/DTRU.

PA power overvoltage


Alarm level: 3

The problem is caused by overvoltage of PA power.

The PA may be damaged. The modulation module protectively closes the power output.

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

The problem is caused by undervoltage of PA power.

The output power is abnormal.


Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Downlink checksum error of DLRC_AL1


Alarm level: 3

The link between CHP and modulation module is interfered.

Large numbers of error codes exist between CHP and modulation module. The downlink is faulty. Conversation fails on TRM/DTRU.

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

The DUC chip is unavailable.

The TRM/DTRU cannot converse normally.

Replace TRM/DTRU.

80w PA VSWR alarm


Alarm level: 3

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.

The TRM/DTRU cannot converse normally. The PA is damaged.

1. Reset TRM/DTRU. Check if the alarm is eliminated.

2. Replace the RF cables between TRM/DTRU and AEM. Check if the alarm is eliminated.


80w PA overtemperature


Alarm level: 4

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property




The TRM/DTRU can work but the PA degradation speeds up.









80w PA overtemperature major alarm


Alarm level: 3


The TRM/DTRU can work but the PA degradation speeds up.









80w PA output power alarm


Alarm level: 3

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property



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.

Conversations may fail on the TRM/DTRU. The power control fails.

1. Reset the TRM/DTRU. Check if the alarm is eliminated.

2. Replace the RF cables between TRM/DTRU to AEM. Check if the alarm is eliminated.


80w PA power overvoltage


Alarm level: 3




80w PA power lower voltage


Alarm level: 3




80w PA absent


Alarm level: 3

The PA is not in position.

No output power.


Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



TXIF unlock


Alarm level: 3

Clock signal is unstable or DTRM Phase-Locked Loop (PLL) is faulty.

Conversations may fail on the DTRU.


2. Power on the module again. Check if the alarm is eliminated.


TPF unlock


Alarm level: 3






TXRF unlock


Alarm level: 3






RXRF unlock


Alarm level: 3

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property








13 MHz clock lost


Alarm level: 3

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

60 ms synchronization clock receiving is abnormal and 60 ms synchronization clock unit works abnormally.





4. Replace the CMB.

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



8M clock of HW lost


Alarm level: 3

HW 8 MHz clock receiving is abnormal and HW 8 MHz clock unit works abnormally.





4. Replace the CMB.

8K clock of HW lost


Alarm level: 3

HW 8 kHz clock receiving is abnormal and HW 8 kHz clock unit works abnormally.





4. Replace the CMB.

52 MHz clock lost


Alarm level: 3

RF board 52 MHz clock receiving is abnormal and RF board 52 MHz clock unit works abnormally.


Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence





3. Replace the DTRU.

First ADC clock lost


Alarm level: 3

AD6650 clock receiving is abnormal and AD6650 clock unit works abnormally.





Second ADC clock lost


Alarm level: 3

AD6650 clock receiving is abnormal and AD6650 clock unit works abnormally.





PA power overvoltage alarm


Alarm level: 3



Check if the PA testing circuit is faulty. If yes, replace the DTRU as soon as possible.

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



PA power undervoltage alarm


Alarm level: 3



Check if the PA testing circuit is faulty. If yes, replace the DTRU as soon as possible.

PA VSWR alarm


Alarm level: 3

The reverse power is too high. It may be caused by the existence of open circuit or high resistance in output end of PA.

Conversation fails on the DTRU. The PA is damaged.

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


The DTRU can work but the PA degradation speeds up.








Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow




PA temperature major alarm


Alarm level: 3


The DTRU power output is protectively closed. The PA degradation speeds up.









PA forward power(3db) alarm


Alarm level: 3

Difference between PA output power and CHP control power is more than 3 dB. This may be due to PA aging, power detecting circuit fault, or too narrow detecting threshold.

Conversations may fail on the DTRU. The power control fails.

1. Reset the DTRU. Check if the alarm is eliminated.

2. Replace the RF cables between DTRU to AEM. Check if the alarm is eliminated.


RTU power alarm


Alarm level: 2

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property



The RTU power module has faults.

The TRM/DTRU cannot work. If the TRM/DTRU is configured BCCH, the cell service is affected.

Replace RTU.

RTU power temperature alarm


Alarm level: 3

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.

The TRM/DTRU power output is protectively closed. The RTU degradation speeds up.

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

The problem is caused by overvoltage of RTU power.

The RTU works abnormally.

Replace the RTU board.

RTU power input failure alarm


Alarm level: 2

The RTU power input is beyond the adjustment range.

The RTU works abnormally.


Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



IQ calibration parameters abnormal alarm


Alarm level: 2

This problem is due to wrong IQ calibration parameter.

The RTU collapses.


EAM heat exchanger alarm


Alarm level: 4

This problem is due to heat exchanger problems, which is reported by the dry contact of the heat exchanger.

The system security is affected.

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

This problem is due to faulty CMB0 heater.

The low temperature startup is affected.

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

This problem is due to faulty CMB0 heater.


Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence



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

This problem is due to equipment smoke alarm.

The operation security is affected.

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

This problem is due to equipment water alarm.


Perform on-site check immediately to find fault cause and handle the fault.

EAM lightning protection alarm


Alarm level: 3

This problem is due to lightning protector failure.


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

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property



This problem is due to the alarm of back door being opened.


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

This problem is due to the alarm of front door being opened.


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

This problem is due to PWR monitoring unit alarm.


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

This problem is due to FIB heater alarm.


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.

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



EAM heat exchanger control board alarm


Alarm level: 3

This problem is due to heat exchanger control board alarm.

The normal operation of the equipment is affected.

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

This problem is due to heat exchanger external circulation fan 2 alarm.


1. Check if the lines between the heat exchanger control board and the fan are normal.

2. Replace the fan.

EAM heat exchanger external circulation fan 1 alarm


Alarm level: 3

This problem is due to heat exchanger external circulation fan 1 alarm.



2. Replace the fan.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



EAM heat exchanger internal circulation fan 2 alarm


Alarm level: 2

This problem is due to heat exchanger internal circulation fan 2 alarm.



2. Replace the fan.

EAM heat exchanger internal circulation fan 1 alarm


Alarm level: 2

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

This problem is due to alarm of communication between EAM and heat exchanger.

The alarm reporting of heat exchanger is affected.

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.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



EAM temperature alarm


Alarm level: 3

This problem is due to overtemperature of network internal environment.


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

This problem is due to mixed-flow fan 1 damage alarm.

Normal operation of the frequency module is affected.

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 level: 3







Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property



Alarm level: 3





Power undervoltage alarm


Alarm level: 2

The external power voltage is lower than the lower limit.

The system transmit power is abnormal, and thus the system cannot work normally.

Restore the external power supply as soon as possible.

Inner fan 2 alarm (for M8202)


Alarm level: 4


The temperature in rack is increased.







3. Check if the fan cables have faults and if board-to-board connectors have faults.






Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow







Inner fan 1 alarm (for M8202)


Alarm level: 4









3. Check if the fan cables have faults and if board-to-board connectors have faults.










Alarm Property

Alarm Cause

Influence

Handling Flow



Outer fan 2 and fan 4 alarm (for M8202)


Alarm level: 4



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

The fan is faulty or the module temperature is too high.

The TRM/DTRU is over-temperature and thus the performance indices are affected.

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.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Rack temperature major alarm


Alarm level: 3

The fan is faulty or the module temperature is too high.

The equipment is damaged and thus the performance indices are affected.

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


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 Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow





Alarm level: 4








Alarm level: 4








Alarm level: 4






Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow





Alarm level: 4






FR device failure


Alarm level: 2

The BRCH works abnormally. N392 errors are detected in the last N393 STATUS ENQUIRY events.

The BRCH on Gb interface is broken.

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 if the alarm is eliminated.

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.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



FR congestion


Alarm level: 3

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.

Quality of some users’ PS service is reduced.

Add BRCG links or BRCH timeslots.

MSC overload control alarm at FUC mode


Alarm level: 3

MSC sends overload message. BSC starts FUC flow control.

Some users cannot be accessed.

BSC can automatically control the flow. No operation is required.

CPU overload control alarm at FUC mode


Alarm level: 2

CPU load exceeds the threshold of flow control in the module parameter setting.


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.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Signaling point congestion control alarm at FUC mode


Alarm level: 3

MSC sends signaling congested message. BSC starts FUC flow control.



MSC overload control alarm at SYS mode


Alarm level: 3

MSC sends overload message. BSC starts system message flow control.



CPU overload control alarm at SYS mode


Alarm level: 2

CPU load exceeds the threshold of flow control in the module parameter setting.



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.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Signaling point congestion control alarm at SYS mode


Alarm level: 3

MSC sends signaling point congestion message. BSC starts system message flow control.



CCCH overload control


Alarm level: 3

CS services of some users under the cell cannot be accessed.



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

Users applying for CS service are excessive.

CS services of some users under the cell cannot be accessed.


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.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



NSVC failure alarm


Alarm level: 2

NSVC link is faulty.

For single-NSVC link configuration, the PS service is interrupted. For multiple-NSVC link configuration, the bandwidth is reduced.

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

The verifying of power amplifier parameters has error.

The power amplifier has no calibration curve and the RF index is affected.

1. Reset the corresponding module. Check if the alarm is eliminated.


3. Change the module.

DSP initialization failure


Alarm level: 2

The problem is caused by DSP software or hardware fault.

The system can not operation normally.


2. Reset the DSP. Check if the alarm is eliminated.

3. Change the HBTS.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Tx PLL unlock


Alarm level: 3

The clock signal is unstable, or the TRM/DTRU phase-locked loop is faulty.

S8001 cannot converse.



3. Change the module.

FLASH memory fault


Alarm level: 3

Too many times of FLASH programming leads to read/write error or checksum error.

The software version cannot be downloaded or loaded. Important HBTS logs cannot be recorded. The HBTS cannot work normally.

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

DSP has no response temporally or program runs abnormally.

If DSP is reset, the programs are loaded and initialized again. If this alarm occurs frequently, the HBTS cannot work normally.

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.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



FPGA interface fault


Alarm level: 3

The interface between DSP and FPGA is broken.

S8001 cannot be used normally.

1. Load the EPGA again and reset HBTS. Check if the alarm is eliminated.

2. Replace the HBTS.

CHP frame fault


Alarm level: 3

Frame number processing is interrupted.

The frame numbers are out of order.




Wrong receive channel of RF


Alarm level: 2

The receive channel is faulty and cannot receive uplink signals.

Uplink signal processing cannot be performed.

Download EPGA and DSP versions again. Configure the system parameters again.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Wrong parameter configuration for EEPROM


Alarm level: 3

This problem is caused by EEPROM hardware faults or invalid parameters written to EEPROM. As a result, EEPROM RF parameters cannot be read normally.

The system cannot normally read RF parameters from EEPROM.

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

The board hardware does not support the preset frequency point.

S8001 cannot work normally.

1. Replace the HTRG/HTRU board.

2. Change the frequency point range.

OMP reboot alarm


Alarm level: 3

OMP is reset.

O&M is affected during OMO maintenance. This alarm has no effect on the service.

OMP reports the alarm and restores it when being reset. No handling operation is required.

TRX Man Block


Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property



Alarm level: 3

The TRX is blocked manually.

The TRX exits service.

Unblock the TRX.

Resource cannot be used of RF Channel


Alarm level: 2

Automatic frequency resource search fails.

Research times out.

iBSC cannot provide frequency resource.

The TRX exits service.

Specify the frequency point or change the research range.

SYNCLK locked fail alarm


Alarm level: 4

The synchronization clock cannot be locked after a long time.

CMM/CMB active and standby switchover fails.

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

The TX1 channel does not finish adjustment or the loss is greater than 5 dB.

The transmission is affected.


2. Replace the FCU. Check if the alarm is eliminated.

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow





Alarm level: 2







Alarm level: 2







Alarm level: 2





FCU power undervoltage alarm


Alarm level: 2

The +12V power is under voltage.

The PCU works abnormally.

1. Check if the FCU/FUC power indicator displays alarm.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



If alarm is displayed, go to step 2.

If no alarm is displayed, go to step 3.

2. Check if the 12V power of the slot corresponding to FCU/FUC is normal.

If it is abnormal, replace FCU/FUC.

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

The problem is caused by FCU digital board assistant circuit alarm.

The FCU works abnormally.

Keep observation. The FCU need not be replaced unless the normal service is affected.

Hard disk initialization failure


Alarm level: 3

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.

Operations related to hard disk fail.

Replace the board.

The clock alarm about transmission of CCI board Abis-E1


Alarm level: 3

The reference source is lost.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause



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

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.

Check the Abis-E1 interface.

The local working clock alarm of CCI board


Alarm level: 3

The local working clock is faulty.

The local board works abnormally.

Switch to the standby board. If necessary, replace the CCI board.

The clock alarm about transmission of CCI board 13M


Alarm level: 3

The reference source is lost.

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

The BTS internal transmission link is broken. The frame numbers are out of order.

Check the reference source or replace the CCI board.

CCI opposite board alarm


Alarm level: 4

The opposite board is not in position or the clock is faulty.

The opposite board cannot work normally. The active and standby switchover fails.

Replace the CCI board.

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



IQ FPGA internal clock alarm


Alarm level: 3

The IQ EPGA internal source clock is lost.

The IQ EPGA cannot work normally.

Check if CLK FPGA is working normally.

IQ FPGA light interface alarm


Alarm level: 3

The IQ EPGA optical interface link is exceptional.

The alarm optical interface cannot transmit data.

Replace the optical module or optical fiber.

IQ FPGA LVDS interface alarm


Alarm level: 3

The LVDS interface is exceptional.

The alarm LVDS interface cannot transmit data.

Check the backplane and the SERDES chip on the corresponding GBP board.

IQ FPGA internal data alarm


Alarm level: 3

The format of internal data is abnormal.

IQ data transmission fails.

Find out the cause of data format error.

13M,61.44M clock lost alarm


Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property



Alarm level: 3

The clock is lost.

The clock cannot work. Conversation fails on the DTRU.

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

The FR or FN has error.

Frames cannot be formed on the downlink. Conversation may fail on the DTRU.





26MHz and 52MHz lost of clock alarm


Alarm level: 3

The phase-locked loop is unlocked.

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.




Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



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

The 60ms super frame header is not detected on the uplink.

The uplink can neither normally decode frames nor send timeslot interval to DSP.





checking block data error alarm


Alarm level: 4

The frame data has error.

Communication message is wrong during transmission.

None.

up link LVDS SERDES lost lock alarm


Alarm level: 3

SERDES loses lock.

The uplink cannot normally receive decoded frames.



Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



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


FN error alarm


Alarm level: 4

Downlink framing is affected.

The frame number from CCI has error.



3. Rectify CCI hardware faults. Check if the alarm is eliminated.


receiving channel frequent alarm


Alarm level: 3

Clock signals are unstable, or RRU phase-locked loop is faulty.

Conversation fails on the RRU.

Replace the RRU as soon as possible.

transmiting channel frequent alarm


Alarm level: 3

The crystalloid is faulty.

The PLL is unstable.

Replace hardware.

the lost alarm of 60ms


Alarm level: 3

The RRU clock unit works abnormally.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause



Normal communication fails.

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

The duplexer output power is less than 6 dB.

The duplexer cannot work normally.

None.

HYCOM major alarm


Alarm level: 2



Change the AEM and reset RRU.

the input power is abnormal


Alarm level: 3

The power input is abnormal.

The RRU cannot work abnormally.

Replace the power module.

out of power alarm


Alarm level: 3

The RRU is out of power.

The RRU cannot work abnormally.

Check the power module. If the power module is faulty, replace it with a new one.

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



the lost of signal of the light port 4 alarm


Alarm level: 3

The optical link between RRU and BBU is broken.

Conversation fails.

Check if the optical fiber between RRU and BBU is normal. If it is abnormal, replace it.



Alarm level: 3


Conversation fails.

Check if the optical fiber between RRU and BBU is normal. If it is abnormal, replace it.

light port 2 error,Loss of Frame alarm


Alarm level: 3

The BER of data transmitted through optical fibers is larger than 10E-6.

The RRU cannot work normally.

None.



Alarm level: 3


Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause



Conversation fails.

Check if the optical fiber between RRU and BBU is normal. If it is not normal, replace it.

light port 1 error,Loss of Frame alarm


Alarm level: 3

The BER of data transmitted through optical fibers is larger than 10E-6.

The RRU cannot work normally.

None.

FR device failure


Alarm level: 3

Too many times of FLASH programming leads to read/write error.

The system fails to load and read any version.

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

The version saved on BBU has error.

Data error occurs during version transmission.

The system fails to load the version.

None.

Diversity antenna lost


Alarm level: 2

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property



Two density antennas receive signals. One of them is abnormal.

The density reception cannot be realized and thus the sensitiviey and coverage are affected.

Check the RF receive channel.

Diversity antenna identical


Alarm level: 2

The two antennas of the two densities are wrongly corrected.

The antennas are identical and thus cannot work.

Check the antenna connection.

A Interface Resource Statistics Alarm


Alarm level: 2

The resource blockage rate on OMP A interface exceeds the threshold.

The CS service access is affected in long term. Calls are difficult to be given or connected. Traffic volume is affected.

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 the alarm is eliminated.

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



NSVC Resource Statistics Alarm


Alarm level: 2

The NSVC resource blockage rate on OMP exceeds the threshold.

The PS services of some cells are unavailable.

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. Check if the alarm is eliminated.

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 the alarm is eliminated.

TCH Resource Statistics Alarm


Alarm level: 2

The number of consecutive assignment failures exceeds the threshold.

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

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

The TCH resource blockage rate on CMP exceeds the threshold.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause



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

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 code: 100000

Alarm level: 1

The communication between the EMS and NE is broken. The NE is disconnected from the OMC server.

Messages related to the device cannot be reported normally.

Check if the link is normal.

Link alarm

Trunk Frame Loss


Alarm level: 2

Two ends have no common ground.

The clocks are not synchronous.

Transmission equipment has a failure.

The trunk signals received by the trunk are interrupted.

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.


If no, reset the board's DIP switch or rear board's jumper cap. Then, check if the alarm is eliminated.

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow



2. Use a multimeter to detect if the grounding signal of the equipment from both ends is reliable.


If no, make the grounding signal of both ends reliable. Check if the alarm is eliminated.

3. Check if the CLKG/ICM board locks the clock (TRACE evergreen)


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.


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

The wire E1 is not connected or wrongly connected on DDF.

E1 line breaks.

The upstream equipment is exceptional.


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.

If the alarm is eliminated, refer to the suggestions on upstream equipment troubleshooting.

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 Property

Alarm Cause

Influence

Handling Flow

Alarm Property



The upstream equipment is exceptional.


Check and clear the E1 alarms corresponding to the upstream equipment.

Trunk Multi-frame Loss


Alarm level: 2

The frame formats at both ends are inconsistent.


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

The base frame and CRC multi-frame are not synchronized.


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

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.


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.

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Communication Link between Active and Standby Boards Off


Alarm level: 3

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.

The active and standby boards cannot communicate.

1. Check if the active and standby boards are configured on OMC. 1

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.

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 alarm is eliminated.

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

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.

The control plane fails to be routed, or the ports are switched cyclically.

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.

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.

If FE-C3/4 is not used as the routing port, the alarm will need no handling. End alarm handling.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



2. Check if the ports on the peer end connected with a couple of ports on the local board are coupling ports.

If they are coupling ports, the alarm will need no handling. End alarm handling.

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 if the alarm is eliminated.

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

NE clock is exceptional.

The TDM connection chip is exceptional.

The board hardware is faulty.

The backplane hardware is faulty.

The CS domain service may be interrupted.

1. Check the HW number configured for this board and neighboring slots to see if the number exceeds the number of physical slots.

If the number is not excessive, modify the configuration and synchronize the data. Reset the board. Check if the alarm is eliminated.

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.

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow



Communication between environment monitoring board and OMP board abnormal


Alarm level: 2

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.

The environment status cannot be monitored.

1. Check if the connection between PWRD and OMP is correct.

If it is not correct, correctly connect OMP and PWRD.

If it is correct, go to step 2.

2. Check if the connection cables between PWRD and OMP have faults.

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

The packet loss rate of the internal RAWMACIP channel of the board exceeds the threshold (25% by default).

The RAWMACIP channel cannot transmit data normally.




Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks



test pack check abnormal


Alarm level: 2

The ATM communication in the board is abnormal.

The media plane communicates abnormally.



MAC Address Conflict Exists in Boards of Same Shelf


Alarm level: 1

The board is not inserted in position.

The DIP switch setting is changed.

Other causes.

The board cannot start normally or conflicts occur on the control plane.

1. Check if the DIP switch setting is changed and if the board is restarted after the change.

If the DIP switch setting is not changed, go to step 2.

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

The board is not inserted in position.

The DIP switch setting is changed.

Other causes.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence



The board cannot start normally or conflicts occur on the control plane.

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.

If the DIP switch setting is not changed, go to step 2.

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 alarm is eliminated.

OSS refers to the operating system.

dualhome office block


Alarm level: 3

The dual-home office is switched to be slave. The DH process blocks the office.

The messages fail to be transceived.

1. Check if the dual-home office is slave.

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

The dual-home office is switched to be slave. The DH process blocks all the links of an office.

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause







2. Perform dynamic management on related links. Unblock the links. Check if the alarm is eliminated.




dualhome association block


Alarm level: 3

The dual-home office is switched to be slave. The DH process blocks all the associations of an office.





2. Perform dynamic management on related associations. Unblock the associations. Check if the alarm is eliminated.




Recive bad packet


Alarm level: 3

The state of the external port is abnormal.

The hardware is bad.

The 2400 card don't plug well.

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause



Other problems result in the GE receipt error.

The board cannot normally receive data packet. This makes the service that the board bears unstable.

1. Connect to the alarm board ingress, input the command McsGliPmShow.

If the printed message contains only “Port *** Pkts with Error RSW” and the corresponding statistic item is not zero, go to step 2.

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 alarm is eliminated.

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

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.


1. Pull out and plug in the optical fibers/cables. Check if the alarm is eliminated.

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



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




Faulty Frames Received by Internal Switching Interface Faulty


Alarm level: 2

The board switching chips are physically faulty.

The PSN board in the same shelf is exceptional.

The network processor subcard is loose.


1. Restart the board (For the Release version, the board restarts automatically). Check if the alarm is eliminated.



HDLC unavailable


Alarm level: 2

This alarm is generated when an HDLC is created. It disappears when the link gets through.

The link is broken.

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.

1. Check the settings of HDLC channel to see whether the E1/TI of this HDLC and its time slots match the peer end.


If no, modify HDLC setting and make it accordant with the peer end HDLC.

2. Check if the physical connection is correct.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow




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.

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

This alarm is generated when a UID is created. It disappears when the link gets through.

The link is broken.

All the services on the UID are interrupted.

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.



Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Far End IMA Group is in Startup state


Alarm level: 2

The alarm is generated when the local end IMA group receives the “group status device is in Startup status” message from the far end.


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

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.


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

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.


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.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



FE RXLSM is in Unusable State


Alarm level: 2

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.


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

The near-end sending link fault is generally due to IMA device failure.


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 Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause



A sending link in the group does not connect to the remote end IMA group link other links.


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

The physical E1 link connection is faulty.


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

The receiving clock is abnormal.


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. Check if the alarm is eliminated.

RDI Alarm of Near-End Receiving Link


Alarm level: 2

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property



The remote IMA link is not in the activated state.


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. Check if the alarm is eliminated.

Near-End Receiving Link Faults


Alarm level: 2

The alarm is generated if the near-end receiving link is faulty.


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

The alarm is generated if the near-end receiving link becomes invalid.


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

A receiving link in the group does not connect to the remote end IMA group link other links.

The Iu physical link is broken.

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

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



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

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.


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

Far-end IMA group's part links are loopback and came to operational state, and part of links are connected to near-end group.


Check if the links of the far-end IMA group connected to the local end are not loopback.

Remote Receiving Link ID Mismatched


Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property



Alarm level: 2

Two groups of interacted links are wrongly connected or link ID is modified on the background.

The RX link status machine at the NodeB side cannot normally flip.

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. Check if the alarm is eliminated.

BFD Session Interrupted


Alarm level: 3

The UDP-layer link where the BFD session runs is faulty. This leads the BFD module to the down state.

The service is interrupted.

1. Check if physical link between the source IP address and destination IP address is smooth.

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.

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

A newly configured link is initially broken.

The link state changes to broken.

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause



The link is actively closed during active/standby switchover.

The BTS is inaccessible.

1. Check if the transmission link between BSC and BTS is normal.

If it is not normal, ensure that the link is normal. Wait for 5 minutes and check if the alarm is eliminated.

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.

If no alarm occurs, go to step 2.

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

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.

The control plane communication between boards is abnormal. This may cause control plane messages to be lost.

1. Check if the ENUM indicator on the alarm board is always lighting.

If yes, switch off the ENUM. Check if the alarm is eliminated.

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.


If no, restore the above mentioned boards to the normal state. Check if the alarm is eliminated.

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



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

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.

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.

1. Check if the ENUM indicator on the alarm board is always lighting.

If yes, switch off the ENUM. Check if the alarm is eliminated.

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.


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

The association link is deleted.

The association link is released manually.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause



Other causes.

The office may be inaccessible and other available association links are congested.

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.


If the configurations are inconsistent or server and client do not match, modify the configuration and then check if the alarm is eliminated.

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.

If yes, ask transmission engineers to solve the problem.





The alarm seldom occurs.

The following is an example of correct configuration:

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.

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

Influence

Handling Flow

Remarks

Alarm Property



No association is in the serving state.

The system fails to transceive messages to the corresponding office.

1. Check if none of the associations to the adjacent office is available.

If yes, refer to section “Association link broken” to handle the alarm.

If the associations are available, go to step 2.




PPP_UID Link Down


Alarm level: 2

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.


Check if the BTS is started. Check if the E1 link to the BTS is normal.

PPP Link Down


Alarm level: 2

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.


Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence



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

This alarm is generated after a HDLC is created. It disappears after the link gets through.

The link is broken.

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.

1. Check the settings of HDLC channel to see whether the E1/TI of this HDLC and its time slots match the peer end.


If no, modify HDLC setting and make it accordant with the peer end HDLC.

2. Check if the physical connection is correct.


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.

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


Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause



The link is broken.



Association path broken


Alarm level: 2

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.

The path is unavailable. If all the paths are broken, the association link is broken.

1. Check if the physical link has serious package loss by using the command Ping.

If yes, troubleshoot the physical link and then check if the alarm is eliminated.


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 check if the alarm is eliminated.

PPP link broken


Alarm level: 2

This alarm is generated when a port is created dynamically. It disappears after the PPP negotiation succeeds.

The PPP link is broken.


1. Check if the peer-end BTS works normally.


Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



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.


If no, modify UID and HDLC settings and make them accordant at the two ends of BSC and BTS. Check if the alarm is eliminated.

3. Check if physical connection is correct and if the physical link connection is consistent with the UID/HDLC configuration.


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.


If yes, replace the cables. Check if the alarm is eliminated.

5. Record the statistic data of messages received by and sent from the PPP port.

BSCIP configuration error in database


Alarm level: 4

The BIPI/GIPI is not configured.

The IP addresses of BSCIP are illegal, that is, all 0s or all 1s.

The ABPM cannot locate other problems by using the selfloop method.

1. Check if the BSCIP configuration is correct.


If no, modify the configuration. Check if the alarm is eliminated.

2. Check if the internal link between OMP and BIPI/GIPI is normal.


If no, check related alarms of internal communication and refer to the handling suggestion.

Alarm Property

Alarm Cause

Influence

Handling Flow



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


If no, wait for a period of time and then configure again. Check if the alarm is eliminated.

4. Record the BSCIP configuration.

MGW not registered


Alarm level: 2

The MGW exits the service.

The MGW fails to be registered for a long time (for example, 210 s) after being powered on.

The MGW that generates the alarm is unavailable.

Ask MGW maintenance personnel to check if the MGW equipment works normally. Record the alarm details.

Dual Homing Office Blocked


Alarm level: 3

The dual homing office switches to the standby domain. The service DH process initiates the message of blocking office.


1. Check if the current dual homing office is in the standby domain.

If the current dual homing office is in the standby domain, it is not necessary to handle the alarm. End the alarm handling.

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.




Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Dual Homing Link Blocked


Alarm level: 3

The dual homing office switches to the standby domain. The service DH process initiates the message of blocking all the links of the office.





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

The dual homing office switches to the standby domain. The service DH process initiates the message of blocking all the associations of the office.





2. Perform dynamic management on the related associations and unblock the blocked associations. Check if the alarm is eliminated.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow






Trunk error


Alarm level: 2

The trunk cables are not correctly connected.

The trunk fails to be accessed. All connections based on the trunk are interrupted.

1. Check if the E1 lines on the DDF are correctly connected. Check if the alarm is eliminated.

2. Set the E1 line to loopback at the local side. Check if the alarm is eliminated.

If the alarm is eliminated, detect the upstream devices and take the corresponding measure.

If the alarm is not eliminated, go to step 3.

3. Replace the board. End the alarm handling.

Trunk abnormal


Alarm level: 2

Trunk LOF，AIS，or RAI is detected.

The trunk fails to be accessed. All connections based on the trunk are interrupted.

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.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



The rate of error code in a matelink is high at GUIM


Alarm level: 3

The rate of error code in a matelink is high at GUIM.

The data transmitted through the matelink is incorrect.

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

In a pair of FE port, one is link correct but the other is link error.

Link error occurs on the control plane.

1. Check if only one cable is used to connect the port pair of the rear board to the peer-end FE port.

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.

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

The link between the server and alarm box fails to be set up.

Users cannot be informed of alarms through the alarm box.

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

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.


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.


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.


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.

NE link alarm

HW link broken


Alarm level: 3

BTS internal link breaks.

The BTS cannot work normally.


2. Power on the board again. Check if the alarm is eliminated.

3. Check if the backplane jacket matching the board is normal.

If it is abnormal, replace the backplane and then check if the alarm is eliminated.

If it is normal, replace the module and then check if the alarm is eliminated.

4. Replace the CMB.

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow



Master rack communication link alarm


Alarm level: 4

The communication link between the slave rack and the master rack is faulty.

The site fails to load and install data and software, and perform operation and maintenance.

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

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

The communication link between the master rack and the slave rack is faulty.


Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence





A interface E1 remote alarm


Alarm level: 3

The sending line is broken. This causes the remote end fail to receive data sent from local end.

The BTS cannot provide services.

1. Check if E1 cables have faults through loopback test.

If yes, make the cables again to remove cable faults.


2. Inset the CMM/CMB board tightly and power it on again. Check if the alarm is eliminated.

3. Start the selfloop test of E1 interface. Check if the result is normal.

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







Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow








C interface E1 remote alarm


Alarm level: 3












D interface E1 remote alarm


Alarm level: 3






Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow









E interface E1 remote alarm


Alarm level: 3












F interface E1 remote alarm


Alarm level: 3





Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow










G interface E1 remote alarm


Alarm level: 3












H interface E1 remote alarm


Alarm level: 3




Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow











LAPD communication link between FUC and BSC break


Alarm level: 2

The L2 layer software of FUC does not communicate wit the BSC for a period of time.

The FUC cannot work. If the FUC is BCCH-TPU, cell services are affected.










Communication link between CMM and FUC break(BTS V2)


Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property



Alarm level: 3

The HDLC link between the CMM and TPU is broken. The CMM hardware is faulty.

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.

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

The HDLC link between the CMM and TPU is broken. The CMM hardware is faulty.

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.

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

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



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

LAPD communication link between FUC and BSC broken


Alarm level: 3

The L2 layer software of FUC does not communicate wit the BSC for a period of time.

The FUC cannot work. If the FUC is BCCH-TPU, cell services are affected.

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

The parameter configuration is incorrect or has conflicts.

The DTUR normal operation is affected.

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.

Generally, the BSC background checks the data legality before synchronizing data. Only legal data can be synchronized. Therefore, this alarm seldom occurs.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks



Communication broken between EAM and CMB


Alarm level: 3

The communication between EAM and CMB is broken.

Alarm reporting is affected.

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

The LAPD communication between rack operation&maintenance unit and BSC is broken.

The rack exits from services.

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. Then, check if the alarm is eliminated.

Site LAPD communication link broken


Alarm level: 2

The LAPD communication between site operation&maintenance unit and BSC is broken.

The site exits from services.

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. Then, check if the alarm is eliminated.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Cell interruption alarm


Alarm level: 2

The cell is interrupted.

The cell exits from services.

View the cell management, transceiver management and channel management on the background.

1. View the cell management.

If some cells are manually blocked, unblock them.

If some cells are blocked due to global resetting, check and rectify A interface fault.

2. View the transceiver management.

If the BCCH carrier of the cell that generates the alarm is manually blocked, unblock the carrier.

If blockage due to broken LAPD exists, restore the LAPD link.

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

The handshake between NFSDETECT process of OMP and SBCX fails.

Performance data is lost.

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.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Control link broken


Alarm level: 2

The communication between HBTS and iBSC is broken.

The HBTS cannot normally communicate with the iBSC.

1. Check the transmission link.

2. Load the software version again.

3. Upgrade the software version.

The HBTS model is S8001.

Operation link broken(CS)


Alarm level: 3

For the CS service, the communication link between HBTS and iBSC is broken or has no response for a long time.

The subscribers of the HOMEBTS fail to use the CS service.

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, Check if the alarm is eliminated.


Operation link broken(PS)


Alarm level: 3

For the PS service, the communication link between HBTS and iBSC is broken or has no response for a long time.

The subscribers of the HOMEBTS fail to use the PS service.

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, Check if the alarm is eliminated.


Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Handling Alarms Process Instance Configuration Error


Alarm level: 2

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.

The board startup fails.

Check the configuration table of process instances. Record the alarm details.

T Network Connection Not Conform to Configuration


Alarm level: 1

The T network fiber connection does not conform to the optical interface connection relation configured on the background.

The T network switching of the shelf where the board is located is out of order.

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. Then, check if the alarm is eliminated.

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.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



DB Config Doesn't Fit for Device


Alarm level: 3

The equipment type configured in the database does not conform to the board hardware equipment.


1. Based on the detailed information on the alarm, check if the background configuration conforms to the board hardware equipment.

If no, modify the configuration according to the hardware equipment. Power on the board again. Then, check if the alarm is eliminated.


2. Record alarm details.

OMC Gateway Mask Different from DBs


Alarm level: 2

The mask of the OMC gateway read from the OMP database is inconsistent with that previously saved on the OMP.

The system cannot start normally. This may disable the communication between foreground and background.

Restart the active and standby OMP boards at the same time. Check if the alarm is eliminated.

Alarm Due to Inconsistent Area Code


Alarm level: 2

The area code exported from the OMP database is inconsistent with that previously saved on the OMP.



Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Alarm Due to Inconsistent Mac Address of Background OMP(OMC)


Alarm level: 2

The OMC MAC address read 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

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

The module type read from the MP database is inconsistent with that previously saved on the MP.

The system cannot start normally. The MP may not provide functions normally.

1. Check if the board module type is OMP.

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

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



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

Startup File Does Not Exist


Alarm level: 2

The Bootcfg.ini file does not exist.

The system cannot start normally. The MP may not provide functions normally.


OMP GateWay IP Different from DBs


Alarm level: 2

The gateway IP address read from the OMP database is inconsistent with that previously saved on the OMP.



OMC Server IP Different from Dbs


Alarm level: 2

The IP address of the OMC server read from the OMP database is inconsistent with that previously saved on the OMP.



OMC Gateway Mask Different from DBs


Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property



Alarm level: 2

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

The key configuration data of OMP is changed.

The OMP needs to be reset. Otherwise, the system cannot work normally.


Inconsistent Office ID Settings of DIP Switch


Alarm level: 2

The office IDs set through DIP switch in different shelves are different.

The MAC addresses conflict. The verification of board MAC and IP address fail. The board cannot be powered on.

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

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property



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.

The network interface does not work as the setting.

1. Check if the work mode on the peer end matches the one set on the local end.


If no, modify the work mode on the peer end to make it consistent with the one on the local end. Check if the alarm is eliminated.

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

Different formats of tones cannot co-exist on the board.

The DSP cannot use the service.

y using the formatting button of OMC background tools, set the audio format to new audio format or old audio format. Check if the alarm is eliminated.

Version Switches While Board Doesn't Reset


Alarm level: 4

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.

The version takes effect only after the board is reset.

1Manually restart the OMP board.

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Function EPLD Update Failure


Alarm level: 4

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.

If the alarm is eliminated, the board may not be restarted.

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.

Currently the upper limit of EPLD version size is 64 K.

Inconsistent BOOT/EPLD Version No. with Database Configurations


Alarm level: 4

The running BOOT version does not match the database.

The running EPLD version does not match the database.

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.

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

The system fails to cover the bootflash backup region.

The BOOT backup version is unavailable.

Switch BOOT again and restart the board manually. After the board begins running normally, the alarm is eliminated.

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Microcode Is Abnormal


Alarm level: 2

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.

The board communication link is broken.

The service that the board bears is interrupted.

1. Restart the board that generates the alarm (board of Release version starts automatically). After the board is restarted, check if the alarm is eliminated.

2. Pull out and plug in the board. After the board is restarted, check if the alarm is eliminated.

3. The board hardware may have fault. Replace the board. Check if the alarm is eliminated.

PVC Fault


Alarm level: 3

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.

The PVC status changes to faulty. The services that the PVC bears, irrespective of signaling or data, are interrupted.

1. Check if the optical fibers corresponding to the PVC work normally.

If no, correctly connect the fibers and then check if the alarm is eliminated.

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

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. Check if the alarm is eliminated.


Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



3. Delete the PVC. Check if the alarm is eliminated.

FE reports unacceptable configuration parameters(M size)


Alarm level: 2

The near-end IMA group receives unacceptable configuration message through ICP cells from the far-end IMA group. (M size)


Check if the parameter configuration of frame length (M size) on the near end and far end match each other.

Fe IMA Group is in config-aborted state (because of unmatched symmertry mode)


Alarm level: 2

The near-end IMA group receives unacceptable configuration message through ICP cells from the far-end IMA group. (Unadaptable Symmetry)


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

Fe IMA Group is in config-aborted state (because of unmatched OAM lable)


Alarm level: 2

The near-end IMA group receives unacceptable configuration message through ICP cells from the far-end IMA group. (Unmatched OAM label)


Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



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

Fe IMA Group is in config-aborted state (because of other reseans)


Alarm level: 2

The near-end IMA group receives unacceptable configuration message through ICP cells from the far-end IMA group. (other reasons)


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

The near-end IMA group receives unacceptable configuration message through ICP cells from the far-end IMA group. (other reasons)


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

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.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause




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

The number of active links on the local end is less than the specified minimum number of sending or receiving links.


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

The foreground alarm pool is full.

Alarms are lost, and the system may be collapsed.

Check if there are virtual configuration resources that are temporarily useless. If yes, delete them and then check if the alarm is eliminated.

Board Connection Check is Off


Alarm level: 4

The connection check switch is off, causing PP service process unable to perform connection check.

The connection check is prohibited and thus connection error cannot be detected automatically. This causes the connections fail to self heal in some cases.

Restore the connection check.

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Access DSP's HPI memory error


Alarm level: 2

For some reason, HOST cannot access DSP's register through HPI.

This problem causes call losses.

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

The IP address of the NTP server is set to 0 or 0xFFFFFFFF in the database.

The period of synchronization is zero.

The system time may be different.

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

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.


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.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



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

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.


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.

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.

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.

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.



Alarm Property

Alarm Cause

Influence

Handling Flow



Number of management module alarms exceeds the threshold


Alarm level: 2

The foreground alarm pool is full.

Alarms are lost, and the system may be collapsed.

Check if there are virtual configuration resources that are temporarily useless. If yes, delete them and then check if the alarm is eliminated.

NTP time exceeds threshold


Alarm level: 3

The difference between NTP time and local time exceeds the threshold.

NTP clock synchronization terminates.

1. Check if the interval between alarm time and current environment time exceeds 8 periods.


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.

If yes, restore the alarm first and then go to step 4.


4. Check if the link between OMP and RPU is broken.

If yes, restore the link and then go to step 1.


5. Check if the alarm threshold of NTP server is too low.

If the alarm threshold is not 0 and less than 100, increase the threshold or change it to 0. Then, go to step 1.

If the threshold is greater than 100, go to step 6.

6. Manually originates time synchronization on the background. Check if the alarm is eliminated.


Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



brs main config request timeout


Alarm level: 2

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.

The protocol stack cannot work.

1. Check if the home module MP and the local board system control are normal and if their communication is normal..


If yes, end alarm handling.

2. Pull out and plug in the board. Reset the hardware. Check if the alarm is eliminated.


brs main epu register timeout


Alarm level: 2

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.

The protocol stack cannot work.

1. Check if the RPU and communication between EPU and RPU are normal.


If yes, end alarm handling.

2. Pull out and plug in the board. Reset the hardware. Check if the alarm is eliminated.


Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Database config is different from file named bootcfg ini.


Alarm level: 2

The data from the OMP database is inconsistent with that previously saved on the OMP.

System startup is abnormal. MP may not provide functions normally.

Restart the master and slave OMPs at the same time. Check if the alarm is eliminated.

Wrong Parameter configuration for TPU Ch0


Alarm level: 4


The channel assignment and normal operation are affected.

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.





Alarm level: 4




Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow








Alarm level: 4









Alarm level: 4







Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks





Alarm level: 4









Alarm level: 4









Alarm level: 4


Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause










Alarm level: 4







Cell configuration parameter mismatch(BTS V2)


Alarm level: 3

The cell parameter configuration is wrong, or conflicts with the configuration of channel parameter and CIP parameters.

The BTS may work abnormally.



3. Check if the hardware is faulty. If hardware faults exist, replace the related module.

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow




Software version of FUC mismatch(BTS V2)


Alarm level: 3

The FUC software version is incorrectly installed. If one carrier is configured as BCCH, the whole cell cannot work normally.

The TRM/DTRU cannot work normally.

Reset the TRM/DTRU. If the alarm persists, replace the TRM/DTRU.

Software version of CHP mismatch(BTS V2)


Alarm level: 3

The four DSPs of CHP cannot run. If one DSP is configured as BCCH, the whole cell cannot work normally.



L3 Software of FUC No Response(BTS V2)


Alarm level: 4

The MO software has/has no response temporally (which is determined by CMM).

The background cannot detect the running status of FUC. Calls, however, are not affected.

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 and then check if the alarm is eliminated.

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



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.

Wrong Parameter configuration for CIP


Alarm level: 3

The parameter configuration is wrong or has conflicts.


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

The CIP software version is incorrectly installed. If one carrier is configured as BCCH, the whole cell cannot work normally.



Wrong parameter configuration for TRM Channel 0


Alarm level: 4



Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence









Alarm level: 4









Alarm level: 4







Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks





Alarm level: 4









Alarm level: 4









Alarm level: 4


Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause










Alarm level: 4









Alarm level: 4






Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks




Cell configuration parameter mismatch


Alarm level: 3

The cell parameter configuration is wrong, or conflicts with the configuration of channel parameter and CIP parameters.

The BTS may work abnormally.



3. Check if the hardware is faulty. If hardware faults exist, replace the related module.


FUC Software version mismatch


Alarm level: 3

The FUC software version is incorrectly installed. If one carrier is configured as BCCH, the whole cell cannot work normally.

The DTRU cannot work normally.

Reset the DTRU. If the alarm persists, replace the DTRU.

CHP Software version mismatch


Alarm level: 3

The CHP software version is incorrectly installed.

The DSP of CHP cannot run. If one carrier is configured as BCCH, the whole cell cannot work normally.


Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



CU Software version mismatch


Alarm level: 3

The CH software version is incorrectly installed.

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

The MO software has/has no response temporally (which is determined by CMB).

The background cannot detect the running status of FUC. Calls, however, are not affected.

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 and then check if the alarm is eliminated.

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

The iBSC parameter configuration fails.

The parameter configuration times out.

The configuration process is interrupted, such as timeout and link broken.

The S8001 cannot work normally.

Configure the parameters again.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Parameter configuration failure of AD6537


Alarm level: 3

The AD6537 register reads and writes abnormally.

The system cannot normally read and write the AD6537 register.

Configure the AD6537 register again.

Environment Alarms Cell delineation do not synchronization about cell on E1 link


Alarm level: 3

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.

The data receipt fails and the signaling link is broken.

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

The rack temperature exceeds the preset upper limit of alarm threshold.

The boards work abnormally.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



1. Check if the preset upper limit of rack temperature threshold on the background is reasonable.


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

The rack temperature is lower than the preset lower limit of alarm threshold.


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

The temperature in the equipment room is higher than the preset upper limit of alarm threshold.


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.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



House temperature is lower than high threshold


Alarm level: 3

The temperature in the equipment room is lower than the preset lower limit of alarm threshold.


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

The voltage of a line exceeds the upper limit of the alarm threshold.


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

The voltage of a line is lower than the upper limit of the alarm threshold.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause




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

The humidity in the equipment room exceeds the upper limit of the alarm threshold.


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

The humidity in the equipment room is lower than the lower limit of the alarm threshold.


1. Check if the lower limit of humidity threshold on the background is reasonable.



2. Increase the humidity. Check if the alarm is eliminated.

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Rack fans faults


Alarm level: 3

The fans in the rack are faulty.


1. Check if the fan plug-in box and its power line are connected securely (the indicators are normal).


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

The related rack door is not closed.


1. Check if the rack door is closed.


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

The smoke detector detects smoke.


Check if smoke exists in the equipment room. If yes, dispel the smoke and then check if the alarm is eliminated.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Infrared alarm


Alarm level: 3

The infrared of the equipment room is higher than the preset threshold.


1. Check if there is any animal around the infrared sensor.

If yes, keep them away from the sensor. Check if the alarm is eliminated.


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

The equipment room is influenced by thunderstroke in bad weather.


Check if there is lightning hazard. If yes, take protection measures. Check if the alarm is eliminated.

SNTP server invalid


Alarm level: 3

The network communication is faulty.

The server is faulty.

Board clocks cannot be synchronized.

1. Check if the physical link is normal by using the ping command.

If no, rectify physical link faults.


2. Check if the IP address of the server is correct. If no, configure the IP address again.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



Fault on Board (GPS)


Alarm level: 1

A class fault.

ICM/CLKD/CLKG board output clock is lost. The output detects the device.

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.

The SETS chip or GPS module works exceptionally.

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

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.

Packets may be lost.

Check if the threshold is reasonable.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



If no, modify the configuration and synchronize the data. Check if the alarm is eliminated.

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

Inter-board Message Communication DSP overload (Level 1 alarm)


Alarm level: 2

The DSP load exceeds the preset high threshold.

Voice quality is reduced. Call loss may also be caused.

Check if the threshold is reasonable. If yes, reduce the traffic. If no, modify the threshold setting.



Alarm level: 3

The DSP load exceeds the preset medium threshold.

Voice quality is reduced.

Check if the threshold is reasonable. If yes, reduce the traffic. If no, modify the threshold setting.



Alarm level: 3

The DSP load exceeds the preset low threshold.

Voice quality may be reduced.

Check if the threshold is reasonable. If yes, do not add traffic any more. If no, modify the threshold setting.

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow



MTP2 link reception overload


Alarm level: 2

The traffic on the peer end is heavy.














Association congested


Alarm level: 3

The service is busy.

The loads among associations are unbalanced.

The association resource is insufficient.

Messages are lost.




Alarm Property

Alarm Cause

Influence

Handling Flow

Alarm Property

Alarm Cause

Influence

Handling Flow




3. Check if association resources are sufficient.

If sufficient, check if loads are evenly shared among associations. If yes, go to step 1. If no, go to step 4.

If insufficient, add new associations and check if this alarm is eliminated. If no, use the above method for sufficient link resources.




STC office congested


Alarm level: 3

A congested association leads to the office congestion.

Messages may be discarded due to congestion. Thus, calls may be lost and associations may be broken.





3. Check if association resources are sufficient.

If sufficient, check if each association is congested. If yes, handle the problem by referring to “Association congested”. If no, go to step 4.

If insufficient, add new associations and check if this alarm is eliminated. If no, use the above method for sufficient link resources.





Alarm Property

Alarm Cause

Influence

Handling Flow

Remarks


A p p e n d i x 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

UIMC Universal Interface Module for Control plane

（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 Communication Alarms ...... 173 Dry Contact Alarm...............69 Environment Alarms .......... 240 Equipment Alarms.................5 Handling Alarms ............... 213 input clock lose.....................7

interface E1 Rx forward sliding indication....................... 82

QoS Alarms...................... 246 SDH/SONET .........................9 Trunk Link ...........................6 Wrong parameter configuration

.................................. 234 ZXG10 iBSC ..................vii, viii

56783249 zxg10 bss v6 20 base station subsystem alarm handling manual 1

Documents