- No category
ZXG10 iBSC Base Station Controller Alarm Handling Reference Guide
advertisement
ZXG10 iBSC Base Station Controller Alarm Handling Reference Version 6.20.61 ZTE CORPORATION NO. 55, Hi-tech Road South, ShenZhen, P.R.China Postcode: 518057 Tel: (86) 755 26771900 Fax: (86) 755 26770801 URL: http://ensupport.zte.com.cn E-mail: support@zte.com.cn LEGAL INFORMATION Copyright © 2010 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 conidentiality 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, itness for a particular purpose, title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on the information contained herein. ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subject matter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter herein. ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice. Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information. The ultimate right to interpret this product resides in ZTE CORPORATION. Revision History Revision No. R1.1 R1.0 Revision Date 20101010 20100720 Author:Mo Shenghua Revision Reason Updated to V6.20.614 First edition Serial Number: SJ-20100524164252-020 Content About This Manual............................................. I Overview ...........................................................1 Overview of Fault Management......................................... 1 Fault View ..................................................................... 1 Alarm ....................................................................... 1 Notiication ................................................................ 2 Alarm ........................................................................... 2 Alarm Property........................................................... 2 Probable Cause .......................................................... 3 System Impact........................................................... 3 Handling Suggestion ................................................... 3 Notiication .................................................................... 4 Notiication Property ................................................... 4 Probable Cause .......................................................... 4 System Impact........................................................... 4 Handling Suggestion ................................................... 4 Equipment Alarm...............................................5 198000002 Loss of optical signal .....................................13 198000256 Ethernet link to OMC is broken. ......................15 198000518 Trunk link is used for CSU loop back test..........15 198001026 Loss of ATM Cell Synchronization over E1 Link ...........................................................................16 198001027 ATM link is down ...........................................17 198001284 The phase of 8K, 16K clock, input to backplane board, is not matched .............................17 198001285 SDH/SONET:Excessive Error Code ..................18 198001286 Input clock of board lost ................................18 198001792 Loss of SDH transmission link .........................19 198002560 Board CPU overload ......................................21 198002561 High temperature on CPU board......................21 198005121 Inter-shelf media plane links abnormal ............22 Conidential and Proprietary Information of ZTE CORPORATION I ZXG10 iBSC Alarm Handling Reference 198005124 Capacity of TRUNK communication is insuficient............................................................23 198005125 GE optical connection is cross connected ..........24 198005376 Internal media port of board is abnormal .........25 198005381 Input clock is abnormal .................................26 198005389 CPU sub card in position is not conigured in the database.........................................................26 198005390 CPU sub card is missing from slot but is conigured in database ...........................................27 198005395 External port abnormal ..................................27 198005396 Exceptional communication on UIM board or back plane ...........................................................28 198005399 DSP resource is unavailable............................29 198005403 Board SRAM self-check fails ...........................30 198005404 Board OCXO oven fault ..................................31 198005405 Clock board phase-lock loop work mode abnormal..............................................................31 198005632 Hard disk usage rate exceeds threshold. .........32 198005633 OMP hard disk is faulty ..................................32 198005635 The board is not plugged irmly ......................33 198005636 SMBUS error ................................................33 198005637 Back card does not match with front board...................................................................34 198005638 LVDS signal unlocked ....................................34 198005639 High Error Rate of Optical Interface ................35 198005640 FPGA exception ............................................36 198005641 Port Link Down .............................................36 198005643 Phase-lock loop work mode abnormal ..............37 198005644 The channel in a sub card is down...................37 198005645 Sub card abnormal .......................................38 198005646 Phase-lock loop unlocked ..............................39 198005647 High BER on E1 link ......................................40 198005648 Control plane port of backboard joining switching chip is exceptional ..................................40 198005655 Errors detected in DSP...................................41 198005656 Input clock of subcard lost .............................41 198005657 Error of LVDS path frame detection ................42 198005658 Failure in diagnosing link loop back of large T network ...............................................................43 II Conidential and Proprietary Information of ZTE CORPORATION 198005660 Physical link down between master port and slave port .............................................................43 198005661 Physical link down between media interface ports....................................................................44 198005662 IDE running overtime ....................................44 198005663 Component fault ...........................................45 198005665 Fault on board (GPS) ....................................45 198005667 E1 is looped back..........................................46 198005668 Cross-linked E1 alarm ...................................47 198005669 Synchronization status check of FPGA failed ...................................................................48 198005671 Sending or receiving packets using the cascade ports inner board failed ..............................48 198005893 Memory check failed .....................................49 198006400 Cx29704 runs abnormally ..............................49 198015874 Data trafic to PSN board is congested .............50 198015875 GLI table lookup failed...................................50 198015876 GLI exception packets statistic over threshold..............................................................51 198015877 GLIQV SRAM/DRAM error...............................51 198019456 All high-speed links between line card and switching boards are out of synchronization ..............52 198019465 CSIX RX and TX packets is abnormal ...............53 198019712 APS channel mismatched ...............................53 198019713 APS mode mismatched ..................................54 198019714 APS coniguration alarm.................................55 198019715 MS APS channel gets errors............................56 198019968 No response to request L2 Forwarding Table information from DBS. ...........................................57 198019969 No response to request L2 Forwarding Table port information from SCS. .....................................57 198019970 Resource board can't get L2 Forwarding Table. ..................................................................59 198025601 TSNB internal connection chip fault .................59 198025602 TDM switch abnormal ....................................60 198026116 PP2S output clock lost ...................................60 198026117 PP2S clock reference lost ...............................61 198026118 16CHIP clock reference lost............................61 198026127 Loss of Level 3 reference source clock .............62 198026128 Loss of Level2 reference source clock .............62 Conidential and Proprietary Information of ZTE CORPORATION III ZXG10 iBSC Alarm Handling Reference 198026129 Loss of Level1 reference source clock ..............63 198026131 CLKG board PLL is unlocked. Clock will drift ...........................................................................64 198026133 Output clock lost...........................................64 198028672 80g chip abnormal ........................................65 198029952 802.3ah link fault .........................................65 198030208 Fault alarm of CFM ........................................66 198066033 T-net center is fault ......................................67 198066038 The version of the EPU does not accord with that of the RPU .....................................................67 198066070 Board ofline or CPU in reset status for a long period ..................................................................68 198087000 Dry contact alarm 1 ......................................68 198087001 Dry contact alarm 2 ......................................69 198087002 Dry contact alarm 3 ......................................69 198087003 Dry contact alarm 4 ......................................69 198087004 Dry contact alarm 5 ......................................70 198087005 Dry contact alarm 6 ......................................70 198087006 Dry contact alarm 7 ......................................71 198087007 Dry contact alarm 8 ......................................71 198087008 Dry contact alarm 9 ......................................71 198087009 Dry contact alarm 10.....................................72 198087010 Dry contact alarm 11.....................................72 198087011 Dry contact alarm 12.....................................73 198087012 EAM dry contact 1 alarm ...............................73 198087013 EAM dry contact 2 alarm ................................73 198087014 EAM dry contact 3 alarm ................................74 198087015 EAM dry contact 4 alarm ................................74 198087016 EAM dry contact 5 alarm ................................75 198087017 EAM dry contact 6 alarm ................................75 198087018 EAM dry contact 7 alarm ................................75 198087019 EAM dry contact 8 alarm ................................76 198087100 CMM/CMB FLASH programming failure .............76 198087101 HW link broken.............................................77 198087102 Power overvoltage/undervoltage alarm ............77 198087103 13M input clock failure...................................77 198087104 Frame No. inconsistent between software and hardware..............................................................78 198087105 FCLK clock failure .........................................78 198087106 SYNCLK clock failure .....................................79 IV Conidential and Proprietary Information of ZTE CORPORATION 198087107 Master and slave communication link failure ..................................................................79 198087108 Standby CMM/CMB board is not in position. ...............................................................80 198087109 Standby CMM/CMB board abnormal.................80 198087110 CMM/CMB board has powered off. ...................81 198087111 Master rack communication link alarm ............81 198087112 Communication link alarm between master and slave rack (left) ..............................................82 198087113 Communication link alarm between master and slave rack (right) ............................................82 198087114 A interface E1 recieves TRX alarm ...................83 198087115 A interface E1 reciever out of frame alarm .........83 198087116 A interface E1 sender forward-bit-slip indication .............................................................84 198087117 A interface E1 sender backward-bit-slip indication .............................................................85 198087118 A interface E1 reciever forward-bit-slip indication .............................................................85 198087119 A interface E1 reciever backward-bit-slip indication .............................................................86 198087120 A interface E1 remote alarm...........................86 198087121 B interface E1 recieves TRX alarm ...................87 198087122 B interface E1 reciever out of frame alarm .........88 198087123 B interface E1 sender forward-bit-slip indication .............................................................88 198087124 B interface E1 sender backward-bit-slip indication .............................................................89 198087125 B interface E1 reciever forward-bit-slip indication .............................................................90 198087126 B interface E1 reciever backward-bit-slip indication .............................................................90 198087127 B interface E1 remote alarm...........................91 198087128 C interface E1 recieves TRX alarm ...................91 198087129 C interface E1 reciever out of frame alarm .........92 198087130 C interface E1 sender forward-bit-slip indication .............................................................93 198087131 C interface E1 sender backward-bit-slip indication .............................................................93 Conidential and Proprietary Information of ZTE CORPORATION V ZXG10 iBSC Alarm Handling Reference 198087132 C interface E1 reciever forward-bit-slip indication .............................................................94 198087133 C interface E1 reciever backward-bit-slip indication .............................................................94 198087134 C interface E1 remote alarm...........................95 198087135 D interface E1 recieves TRX alarm...................96 198087136 D interface E1 reciever out of frame alarm...................................................................96 198087137 D interface E1 sender forward-bit-slip indication .............................................................97 198087138 D interface E1 sender backward-bit-slip indication .............................................................98 198087139 D interface E1 reciever forward-bit-slip indication .............................................................98 198087140 D interface E1 reciever backward-bit-slip indication .............................................................99 198087141 D interface E1 remote alarm...........................99 198087142 E interface E1 recieves TRX alarm ................. 100 198087143 E interface E1 reciever out of frame alarm................................................................. 101 198087144 E interface E1 sender forward-bit-slip indication ........................................................... 101 198087145 E interface E1 sender backward-bit-slip indication ........................................................... 102 198087146 E interface E1 reciever forward-bit-slip indication ........................................................... 103 198087147 E interface E1 reciever backward-bit-slip indication ........................................................... 103 198087148 E interface E1 remote alarm ......................... 104 198087149 F interface E1 recieves TRX alarm ................. 104 198087150 F interface E1 reciever out of frame alarm................................................................. 105 198087151 F interface E1 sender forward-bit-slip indication ........................................................... 106 198087152 F interface E1 sender backward-bit-slip indication ........................................................... 106 198087153 F interface E1 reciever forward-bit-slip indication ........................................................... 107 198087154 F interface E1 reciever backward-bit-slip indication ........................................................... 107 VI Conidential and Proprietary Information of ZTE CORPORATION 198087155 F interface E1 remote alarm ......................... 108 198087156 G interface E1 recieves TRX alarm................. 109 198087157 G interface E1 reciever out of frame alarm................................................................. 109 198087158 G interface E1 sender forward-bit-slip indication ........................................................... 110 198087159 G interface E1 sender backward-bit-slip indication ........................................................... 111 198087160 G interface E1 reciever forward-bit-slip indication ........................................................... 111 198087161 G interface E1 reciever backward-bit-slip indication ........................................................... 112 198087162 G interface E1 remote alarm......................... 112 198087163 H interface E1 recieves TRX alarm................. 113 198087164 H interface E1 reciever out of frame alarm................................................................. 114 198087165 H interface E1 sender forward-bit-slip indication ........................................................... 114 198087166 H interface E1 sender backward-bit-slip indication ........................................................... 115 198087167 H interface E1 reciever forward-bit-slip indication ........................................................... 116 198087168 H interface E1 reciever backward-bit-slip indication ........................................................... 116 198087169 H interface E1 remote alarm......................... 117 198087170 Temperature alarm...................................... 117 198087171 Fan not-in-position alarm ............................. 118 198087172 Fan control board CPU alarm ....................... 118 198087173 Fan alarm ................................................. 118 198087174 Fan environment temperature alarm.............. 119 198087175 Fan 1 alarm ............................................... 119 198087176 Fan 2 alarm ............................................... 120 198087177 Fan controller module alarm ......................... 121 198087178 Low Noise Ampliier (LNA) alarm ................... 121 198087179 Tower ampliier power alarm ........................ 121 198087180 SWR of AEM HYCOM minor alarm .................. 122 198087181 SWR of AEM HYCOM major alarm.................. 122 198087182 AEM power alarm(BTS V2) ........................... 123 198087183 AEM type alarm(BTS V2).............................. 123 198087184 AEM not-in-posion alarm (BTS V2) ................ 124 Conidential and Proprietary Information of ZTE CORPORATION VII ZXG10 iBSC Alarm Handling Reference 198087185 AEM power alarm........................................ 124 198087186 LNA0 overcurrent alarm............................... 125 198087187 LNA0 overcurrent alarm............................... 125 198087188 Tower ampliier 0 overcurrent alarm .............. 126 198087189 Tower ampliier 1 overcurrent alarm .............. 126 198087190 SWR of AEM HYCOM minor alarm ................. 127 198087191 SWR of AEM HYCOM major alarm ................. 128 198087192 AEM type alarm .......................................... 128 198087193 AEM not-in-posion alarm.............................. 129 198087194 CHP DSP0 of TPU initialization failure(BTS V2).................................................................... 130 198087195 CHP DSP1 of TPU initialization failure............. 130 198087196 CHP DSP2 of TPU initialization failure............. 131 198087197 CHP DSP3 of TPU initialization failure............. 131 198087198 Uplink ADC chip initialization failure............... 132 198087199 Uplink ADC resource unavailable ................... 132 198087200 CIP resource unavailable.............................. 132 198087201 Uplink failure.............................................. 133 198087202 TPU FLASH Memory failure(BTS V2) .............. 133 198087203 Watchdog of TPU CHP DSP0 overlow(BTS V2).................................................................... 134 198087204 Watchdog of TPU CHP DSP1 overlow............. 134 198087205 Watchdog of TPU CHP DSP2 overlow............. 135 198087206 Watchdog of TPU CHP DSP3 overlow............. 135 198087207 Watchdog of FUC overlow............................ 135 198087208 Wrong coniguration of TPU Channel 0 ........... 136 198087209 Wrong coniguration of TPU Channel 1 ........... 136 198087210 Wrong coniguration of TPU Channel 2 ........... 137 198087211 Wrong coniguration of TPU Channel 3 ........... 137 198087212 Wrong coniguration of TPU Channel 4 ........... 138 198087213 Wrong coniguration of TPU Channel 5 ........... 138 198087214 Wrong coniguration of TPU Channel 6 ........... 139 198087215 Wrong coniguration of TPU Channel 7 ........... 139 198087216 Cell parameter coniguration mismatch (processing error) (BTS V2) .................................. 140 198087217 Software version of FUC mismatch(BTS V2).................................................................... 140 198087218 Software version of CHP mismatch(BTS V2).................................................................... 141 VIII Conidential and Proprietary Information of ZTE CORPORATION 198087219 FUC has not responsed with CMM in time (BTS V2).................................................................... 141 198087220 LAPD communication link between FUC and BSC broken ........................................................ 142 198087221 Communication between CMM and FUC breaks (communication) (BTS V2) ......................... 142 198087222 CIP of TPU initialization failure ...................... 143 198087223 Wrong parameter coniguration for CIP .......... 144 198087224 Watchdog of TPU CIP overlow ...................... 144 198087225 Software version of CIP mismatch ................. 145 198087226 Clock alarm for TPU and CMM ....................... 145 198087227 TPU power alarm(BTS V2)............................ 145 198087228 TPU frame No. alarm................................... 146 198087229 TPU CHP DSP0 initialization failure ................ 146 198087230 ADC resource unavailable............................. 147 198087231 CHP frame numbers has fault. ...................... 147 198087232 BURST interruption error ............................. 148 198087233 TPU FLASH memory failure........................... 148 198087234 TPU CHP DSP0 watchdog overlow................. 149 198087235 Wrong coniguration for TRX Channel 0 .......... 149 198087236 Wrong coniguration of TRX Channel 1 ........... 150 198087237 Wrong coniguration of TRX Channel 2 ........... 150 198087238 Wrong coniguration of TRX Channel 3 ........... 151 198087239 Wrong coniguration of TRX Channel 4 ........... 152 198087240 Wrong coniguration of TRX Channel 5 ........... 152 198087241 Wrong coniguration of TRX Channel 6 ........... 153 198087242 Wrong coniguration of TRX Channel 7 ........... 153 198087243 Cell coniguration parameter mismatch .......... 154 198087244 FUC software version mismatch .................... 154 198087245 CHP software version mismatch .................... 155 198087246 CU software version mismatch...................... 155 198087247 HDLC communication link between CMB and FUC broken......................................................... 156 198087248 LAPD communication link between FUC and BSC broken ........................................................ 156 198087249 CU initialization failure................................. 157 198087250 CU parameter coniguration error .................. 158 198087252 TPU power alarm ........................................ 158 198087253 FU frame number error alarm ....................... 159 Conidential and Proprietary Information of ZTE CORPORATION IX ZXG10 iBSC Alarm Handling Reference 198087254 Rx Local Oscillator (LO) PLL1 lost lock alarm................................................................. 159 198087255 Rx Local Oscillator (LO) PLL2 lose lock alarm................................................................. 160 198087256 Tx Local Oscillator (LO) PLL1 lose lock alarm................................................................. 160 198087257 Tx Local Oscillator (LO) PLL2 lose lock alarm................................................................. 161 198087258 52M reference clock PLL lose lock alarm ......... 161 198087259 Tx IF Local Oscillator (LO) PLL lose lock alarm................................................................. 162 198087260 EEPROM resource unavailable alarm .............. 162 198087261 FPGA interface failure .................................. 163 198087262 PA VSWR alarm(BTS V2).............................. 163 198087263 PA overtemperature minor alarm(BTS V2) ......................................................................... 164 198087264 PA overtemperature major alarm(BTS V2).................................................................... 164 198087265 PA output power alarm ................................ 165 198087266 PA power overvoltage .................................. 165 198087267 PA power is undervoltage ............................ 166 198087268 Downlink checksum error of DLRC_AL1 .......... 166 198087269 DUC chip initialization failure ........................ 166 198087270 80w PA VSWR alarm ................................... 167 198087271 80w PA 's temperature is a litter high. ........... 167 198087272 80w PA overtemperature major alarm............ 168 198087273 80w PA output power alarm ......................... 168 198087274 80w PA power overvoltage ........................... 169 198087275 80w PA 's power is undervoltage . ................. 169 198087276 80w PA not-in-position alarm........................ 170 198087277 TXIF lock is lost. ......................................... 170 198087278 TPF clock is unlocked................................... 170 198087279 TXRF lost lock alarm.................................... 171 198087280 RXRF clock is unlocked . .............................. 172 198087281 13 MHz clock is lost..................................... 172 198087282 60ms synchronous clock lost alarm ............... 173 198087283 8M clock of HW is lost. ................................ 173 198087284 HW 8K synchronous signal is lost . ................ 174 198087285 RF board 52MHz clock lost alarm................... 174 198087286 First ADC clock is lost. ................................. 175 X Conidential and Proprietary Information of ZTE CORPORATION 198087287 Second ADC clock is lost. ............................. 176 198087288 PA power is overvoltage............................... 176 198087289 PA power is undervoltage............................. 177 198087290 PA VSWR alarm .......................................... 177 198087291 PA temperature is a little high. (TRX level alarm, exceeds 80℃) ........................................... 177 198087292 PA temperature is much more higher. (TRX level alarm, exceeds 95 ℃) ................................... 178 198087293 PA forward power(3db) alarm ....................... 179 198087294 RTU power is abnormal................................ 179 198087295 The temperature of RTU power is too high................................................................... 180 198087296 The output of RTU power is overvoltage. ......... 180 198087297 RTU power input abnormal alarm .................. 181 198087298 IQ calibration parameters are abnormal. ......... 181 198087299 EAM heat exchanger alarm........................... 181 198087300 CMB0 heating ilm alarm.............................. 182 198087301 CMB1 heating ilm alarm.............................. 182 198087302 EAM has had smoke . .................................. 183 198087303 EAM has had water...................................... 183 198087304 EAM lightning protection alarm. .................... 184 198087305 EAM backdoor access is intruded................... 184 198087306 EAM frontdoor access is intruded. ................. 185 198087307 EAM PWR monitoring unit has fault................ 185 198087308 FIB heating ilm alarm ................................. 185 198087309 EAM heat exchanger control board has fault. ................................................................. 186 198087310 EAM heat exchanger external circulation fan 2 alarm................................................................. 186 198087311 EAM heat exchanger external circulation fan 1 alarm................................................................. 187 198087312 EAM heat exchanger internal circulation fan 2 alarm................................................................. 187 198087313 EAM heat exchanger internal circulation fan 1 alarm................................................................. 188 198087314 EAM heat exchanger 's 485 communication has fault............................................................. 188 198087315 EAM temperature is abnormal....................... 189 198087316 EAM TRX layer mixed-low fan 1 has fault. ................................................................. 189 Conidential and Proprietary Information of ZTE CORPORATION XI ZXG10 iBSC Alarm Handling Reference 198087317 EAM TRX layer mixed-low fan 2 has fault. ................................................................. 189 198087318 EAM TRX layer mixed-low fan 3 has fault. ................................................................. 190 198087319 Communication is broken between EAM and CMB. ................................................................. 190 198087320 Power undervoltage alarm............................ 191 198087321 Inner fan engine 2 alarm (for M8202)............ 191 198087322 Inner fan engine 1 alarm (for M8202)............ 192 198087323 Outer fan engine 2 and 4 alarm (for M8202) .............................................................. 192 198087324 Outer fan engine 1 and 3 alarm (for M8202) .............................................................. 193 198087325 Rack temperature minor alarm ..................... 193 198087326 Rack temperature major alarm ..................... 194 198087327 Layer 3 fan 1 alarm (for M8206) ................... 194 198087328 Layer 3 fan 2 alarm (for M8206) ................... 194 198087329 Layer 3 fan 3 alarm (for M8206) ................... 195 198087330 Layer 2 fan 1 alarm (for M8206) ................... 195 198087331 Layer 2 fan 2 alarm (for M8206) ................... 196 198087332 Layer 2 fan 3 alarm (for M8206) ................... 196 198087333 Layer 1 fan 1 alarm (for M8206) ................... 197 198087334 Layer 1 fan 2 alarm (for M8206) ................... 197 198087335 Layer 1 fan 3 alarm (for M8206) ................... 198 198087340 FR device failure ......................................... 198 198087342 Cell interruption alarm................................. 199 198087361 The CRC calibration of PA parameter turns to be error . ........................................................... 200 198087379 OMP reboot alarm ....................................... 200 198087386 SYNCLK losing lock alarm............................. 201 198087387 Status of TX1 ilter alarm ............................. 201 198087388 Status of TX2 ilter alarm ............................. 201 198087389 Status of TX3 ilter alarm ............................. 202 198087390 Status of TX4 ilter alarm ............................. 202 198087391 FCU power undervoltage alarm ..................... 203 198087392 FCU minor alarm ........................................ 203 198087403 ABIS-E1 transmission related clock alarm of CCI board........................................................... 203 198087404 Local working clock alarm of CCI board.......... 204 198087405 13M clock alarm of CCI board . ..................... 204 XII Conidential and Proprietary Information of ZTE CORPORATION 198087406 CCI opposite board alarm ............................ 205 198087407 IQ FPGA internal clock alarm ........................ 205 198087408 IQ FPGA light interface alarm ...................... 205 198087409 IQ FPGA LVDS interface alarm ...................... 206 198087410 IQ FPGA internal data alarm ......................... 206 198087411 13M and 61.44M clock lost alarm .................. 207 198087412 FR or FN has error....................................... 207 198087413 26MHz and 52MHz Phase Locked Loop (PLL) lose lock alarm .................................................... 208 198087414 Detect failure alarm of uplink 60ms hyperframe synchronization head .......................... 208 198087415 Checking block data error alarm ................... 209 198087416 Uplink LVDS SERDES lost lock alarm.............. 209 198087417 FN error alarm............................................ 209 198087432 Diversity antenna lost.................................. 210 198087433 Diversity antenna identical. .......................... 210 198087443 Diversity antenna lost alarm......................... 211 198087444 Diversity antenna identical alarm .................. 211 198087451 Board does not support 16MHW. ................... 211 198087452 CMB CPU overload alarm ............................. 212 198087453 Signalling HDLC is broken . .......................... 212 198087454 Main dimensional HDLC broken alarm ............ 213 198087455 FIB coniguration exception alarm ................. 213 198087456 FIB software layer 3 no response .................. 214 198087457 FIB CPU overload alarm ............................... 214 198087458 BVC block alarm ......................................... 215 198087460 +12V voltage alarm .................................... 215 198087461 -12V voltage alarm ..................................... 216 198087462 DSP 1.2V voltage alarm ............................... 216 198087463 6.4V voltage alarm...................................... 216 198087464 5V voltage alarm ........................................ 217 198087470 Fan engine not-in-position alarm................... 217 198087471 Fan engine rotation speed alarm ................... 218 198087472 CMB and FNCB RS485 link broken alarm ......... 218 198087473 DTPU CPU is overloaded............................... 218 198087480 Status of TX5 ilter alarm ............................. 219 198087481 Status of TX6 ilter alarm ............................. 219 198087483 GPS signal synchronization exception ............ 219 198087484 Second pulse lost alarm............................... 220 198087485 Antenna open-circuit alarm .......................... 220 Conidential and Proprietary Information of ZTE CORPORATION XIII ZXG10 iBSC Alarm Handling Reference 198087486 Antenna short-circuit alarm .......................... 221 198087487 Lost satellite alarm...................................... 221 198087505 GUP board connection failure........................ 222 198088000 DTPU does not support baseband freqency-hopping alarm........................................ 222 198088001 PA voltage adjusting path has broken. ........... 223 198088002 PA voltage adjusting read/write error. ............ 223 198088003 PA voltage adjusting parameter turns to be error. ................................................................. 224 198088004 Access iBSC failure...................................... 224 198088005 Control link broken...................................... 225 198088006 Operation link broken(CS)............................ 225 198088007 Operation link broken(PS) ............................ 225 198088008 Parameter coniguration mismatch ................ 226 198088009 DSP initialization failure ............................... 226 198088010 Parameter coniguration failure of AD6537.............................................................. 227 198088011 Tx PLL lost lock alarm.................................. 227 198088012 Wrong parameter coniguration for EEPROM ............................................................. 227 198088013 FLASH memory fault ................................... 228 198088014 DSP works abnormally. ................................ 228 198088015 FPGA interface fault .................................... 229 198088016 CHP frame porcessing error alarm ................. 229 198088017 Wrong receive channel of RF ........................ 229 198088018 Acquiring DNS failure under dynamic conigured IP mode.............................................. 230 198088019 Analysis failure of DNS domain name ............ 230 198088020 IPSec start failure ....................................... 231 198088021 Frequency point and HTRG mismatch alarm................................................................. 231 198088022 DHCP automatically acquiring IP address failure ................................................................ 231 198088023 Overhigh temperature alarm ........................ 232 198088024 Voltage abnormity....................................... 232 198088025 Abis link switch alarm.................................. 233 198088027 DIP E1 rack, rack type error ......................... 233 198088028 DIP E1 rack, rack number error .................... 233 198088029 DIP E1 rack, slave rack port 1 error............... 234 198088030 DIP E1 rack, slave rack port 2 error............... 234 XIV Conidential and Proprietary Information of ZTE CORPORATION 198088031 DIP E1 rack,satellite back up lag error .......... 235 198088032 DIP E1 rack, OAM time slot error. .................. 235 198088033 DIP IP rack,access mode error(IP or IPOE)................................................................. 236 198088034 DIP IP rack,rack number error ...................... 236 198088035 DIP IP rack,site number error ....................... 236 198088036 DIP IP rack,sequence number error ............... 237 198088037 Mains power failure alarm ............................ 237 Communication Alarm ................................... 239 198000519 Trunk error ................................................ 240 198000520 Trunk abnormal .......................................... 241 198001824 Abnormal status in SDH/SONET .................... 242 198001825 High BER on SDH / Sonet link....................... 246 198003841 The control plane retransfer ratio over the threshold............................................................ 247 198005122 Loss of Active/standby communication link.................................................................... 247 198005126 Incorrect FE Routing Connection ................... 248 198005127 FE Link Error Alarm ..................................... 249 198005128 Duplicate rack and shelf............................... 249 198005378 Board HW Error .......................................... 250 198005382 Communication between power board and OMP is abnormal ................................................. 251 198005397 Communication of RAWMACIP channel is abnormal............................................................ 251 198005401 Test packet check abnormal ......................... 252 198005651 IP / MAC address conlict ............................. 253 198005664 The rate of error code in a mate link is high at GUIM ................................................................. 253 198005666 The number of the error packets from MAC port exceeds the threshold.................................... 254 198015617 Some frames Received by FE/GE/ATM/MP/POS/E1 Port are faulty.................... 255 198015618 Faulty frames received by port over threshold............................................................ 256 198015873 PSN board is sending out incorrect frames ............................................................... 257 198018689 UID unavailable .......................................... 257 198019208 Timing of Near-End IMA Group Failure ........... 258 198019212 Near-End Sending Link Broken ..................... 258 Conidential and Proprietary Information of ZTE CORPORATION XV ZXG10 iBSC Alarm Handling Reference 198019213 LIF Alarm of Near-End Receiving Link ............ 259 198019214 LODS Alarm of Near-End Receiving Link ......... 259 198019215 RDI Alarm of Far End Receiving Link .............. 260 198019216 Near-End Receiving Link Faults ..................... 261 198019218 Near-End Receiving Link Broken.................... 261 198019223 Ne Group is in fault state. ............................ 262 198022784 BFD Session Interrupted .............................. 262 198029953 The Ethernet port state is OAM loop back ......................................................................... 264 198066000 Abis link broken.......................................... 264 198066003 Control plane communication is abnormal between board and its home module ...................... 265 198066004 Control plane communication is abnormal between MP and OMP ........................................... 266 198066005 SCCP subsystem unavailable ........................ 266 198066007 Broadband link overload .............................. 267 198066008 MTP2 link sending overload ......................... 268 198066009 MTP2 link reception overload ....................... 269 198066010 MTP3 Signalling Point Inaccessible ................ 269 198066011 MTP3 link unavailable .................................. 270 198066012 MTP3 cluster inaccessible ............................. 271 198066014 M3UA Signalling Point Inaccessible ................ 271 198066015 SUA subsystem unavailable .......................... 272 198066016 SUA ofice inaccessible ................................ 273 198066019 Association link broken ................................ 274 198066020 STC Signalling Point Inaccessible .................. 275 198066026 Association path broken............................... 275 198066029 PPP link broken........................................... 276 198066030 BSCIP coniguration error in database............ 277 198066066 AAL2 Path locally blocked............................. 278 198066067 AAL2 Path remotely blocked ......................... 278 198066068 AAL2 Path blocked by broken PVC ................. 279 198066071 Link broken for board fault ........................... 279 198087336 Rack Abis control link broken........................ 279 198087337 Site Abis control link broken ......................... 280 198087343 Front PC communication link broken alarm................................................................. 281 198087352 NSVC failure alarm...................................... 282 198087775 super site exchanged to the satellitic ABIS link.................................................................... 282 XVI Conidential and Proprietary Information of ZTE CORPORATION 198088026 IPOE uplink and downlink congestion alarm................................................................. 283 Handling Alarm ............................................. 285 198005120 T Network Connection Not Conform to Coniguration ...................................................... 286 198005123 Incorrect coniguration for inserted board or device ................................................................ 286 198005387 Alarm due to inconsistent MP type................. 287 198005388 Startup ile does not exist ............................ 287 198005398 Ofice ID is not set correctly with control shelf .................................................................. 288 198005402 Database conig is different from ile named bootcfg.ini .......................................................... 288 198005649 Port coniguration is incorrect ....................... 289 198005659 Formats of audio resource inconsistent .......... 290 198005889 Version Switches While Board Doesn't Reset ................................................................. 290 198005890 Function EPLD Update Failure ....................... 291 198005891 Inconsistent BOOT/EPLD Version No. with Database Conigurations....................................... 291 198005892 Boot Version Fails to Write to Backup Region ............................................................... 292 198007936 Memory ile buffer overlow .......................... 292 198015360 Microcode Is Abnormal ................................ 293 198018944 PVC link is down ......................................... 293 198019207 Near-End IMA Group Coniguration Failure ............................................................... 294 198020225 Protocol stack requested system coniguration information timeout ............................................. 295 198023040 Number of alarms exceeds threshold. ............ 296 198025600 Connection Check be Disabled in board.......... 296 198066006 Broadband link congestion .......................... 297 198066013 MTP3 link congestion................................... 298 198066018 Association congestion................................. 298 198066021 STC ofice congestion .................................. 299 198066027 SNTP failure ............................................... 299 198066031 OMP alarm pool is full, unable to store any more alarms. ...................................................... 300 198066032 Loss of NTP time synchronisation .................. 300 198066063 MTP3 link sending low control alarm ............. 301 Conidential and Proprietary Information of ZTE CORPORATION XVII ZXG10 iBSC Alarm Handling Reference 198087251 FUC L3 software no response temporarily......................................................... 301 198087380 TRX manual block alarm .............................. 302 198087482 Data loading exception alarm ....................... 302 198087513 Board Ethernet port overload alarm............... 303 198087768 Resource Availability Alarm of UPPB DSP ......... 303 Environment Alarm ....................................... 305 198025856 Rack temperature is high ............................. 305 198025857 Low temperature in Rack ............................ 306 198025858 Room temperature is higher than high threshold ........................................................... 307 198025859 Room temperature is lower than low threshold ......................................................................... 307 198025860 Rack voltage is high ................................... 308 198025861 rack voltage is low ...................................... 309 198025862 Humidity is high ......................................... 309 198025863 Humidity is low........................................... 310 198025864 Fault in fan plug-in box ............................... 310 198025865 Rack door alarm ......................................... 311 198025866 Smoke detected ......................................... 311 198025867 Infrared alarm ............................................ 312 198025868 Lightning alarm .......................................... 313 198025869 Loss of DC power supply to rack ................... 313 198029184 SNTP server is unavailable ........................... 314 QoS Alarm ..................................................... 315 198015361 Ring and queue overload alarm..................... 315 198023296 Inter-board message communication low rate exceeds the alarm threshold ........................... 316 198066069 The number of times of signaling data transfer exceeds the allowed threshold of the license ........... 316 198087341 FR congestion............................................. 317 198087344 MSC overload control alarm at FUC mode ................................................................. 317 198087345 CPU overload control alarm at FUC mode ......... 318 198087346 Signaling point congestion control alarm at FUC mode .......................................................... 318 198087347 MSC overload control alarm at SYS mode ................................................................. 319 198087348 CPU overload control alarm at SYS mode ......... 319 XVIII Conidential and Proprietary Information of ZTE CORPORATION 198087349 Signaling point congestion control alarm at SYS mode .......................................................... 320 198087350 CS CCCH overload ...................................... 320 198087351 PS CCCH overload....................................... 321 198087435 A interface resource statistic alarm................ 321 198087436 NSVC resource statistics alarm ..................... 322 198087437 TCH resources statistics alarm ...................... 322 198087438 Assignment failure alarm ............................. 323 198087468 LAPD congestion alarm ................................ 323 198087506 NSE block alarm ......................................... 324 198087507 SGSN is blocked. ........................................ 324 198087758 Manual User Access control alarm ................. 325 198087759 CPU overload control alarm at Paging mode ................................................................. 325 Glossary ........................................................ 327 Conidential and Proprietary Information of ZTE CORPORATION XIX ZXG10 iBSC Alarm Handling Reference This page is intentionally blank. XX Conidential and Proprietary Information of ZTE CORPORATION About This Manual Purpose Intended Audience What Is in This Manual This manual introduces the alarms that might occur during the installation, operation and maintenance of ZXG10 BSS product. Alarm code and description displayed by NetNumen M31 centralized NMS, probable cause for the alarm, and the corresponding handling suggestion are covered in this manual. � � System engineers Maintenance engineers This manual contains the following chapters. Chapter Summary Chapter 2, Equipment Alarm Introduces BSS equipment alarms with respect to alarm property, probable cause, system impact, and handling suggestion. Chapter 1, Overview Chapter 3, Communication Alarm Chapter 4, Processing Alarm Chapter 5, Environment Alarm Chapter 6, QoS Alarm Introduces the concept of fault management, as well as the deinition, type, level classiication of alarm and notiication. Introduces BSS communication alarms with respect to alarm property, probable cause, system impact, and handling suggestion. Introduces BSS processing alarms with respect to alarm property, probable cause, system impact, and handling suggestion. Introduces BSS environment alarms with respect to alarm property, probable cause, system impact, and handling suggestion. Introduces BSS QoS alarms with respect to alarm property, probable cause, system impact, and handling suggestion. Conidential and Proprietary Information of ZTE CORPORATION I ZXG10 iBSC Alarm Handling Reference This page is intentionally blank. II Conidential and Proprietary Information of ZTE CORPORATION Chapter 1 Overview This chapter introduces the concept of fault management, as well as the deinition, type, level classiication of alarm. Table of Contents Overview of Fault Management............................................. 1 Fault View ......................................................................... 1 Alarm ............................................................................... 2 Notiication ........................................................................ 4 Overview of Fault Management Fault management is responsible for collecting information of failures and events that occur during system operation or service processing. The information, in the form of alarm or notiication, is stored in database or displayed on realtime basis through a user-oriented fault monitoring platform. Means such as visual-interface monitor or history information query can be used to view current or historical system operation and service processing status. Fault management enables maintenance personnel to troubleshoot and take preventive measures to remove potential fault and restore system and services as early as possible. Fault View Fault is displayed in the form of alarm or notiication. Alarm The fault that persists during system operation and affects system reliability and normal services is referred to as an alarm. Alarm usually lasts until fault removal. Conidential and Proprietary Information of ZTE CORPORATION 1 ZXG10 iBSC Alarm Handling Reference Due to its possible impact on normal system operation, alarm requires timely troubleshooting in which alarm cause is identiied, and the fault is located and handled. Notification Notiication refers to the non-repeated/instantaneous fault or event that occurs during system operation. Examples include board reset, signaling overload, and so on. Notiication is mostly caused by sudden environment change or other accidental factors. No special handling is required for the notiication, which can be automatically removed by the system. Only the notiication that occurs persistently requires troubleshooting. Alarm Alarm Property Alarm Code Alarm code is the identiier which differentiates alarms. Description Alarm description relects such content as fault cause and fault phenomenon in a simple and straightforward way. Severity Alarm code is deined by a 32-bit ield indicating the speciic code value. There are four alarm levels, which are indicated in descending order of severity as Critical, Major, Minor, and Warning. � � � � Critical alarm causes system breakdown and service interruption. It requires immediate troubleshooting. Major alarm signiicantly affects system operation or weakens network service capability. It requires troubleshooting as soon as possible. Minor alarm affects system operation and network service capability in a non-signiicant way. It requires timely troubleshooting so as to avoid severity escalation. Warning poses a potential hazard to system operation and network service capability. It requires troubleshooting at an appropriate time so as to avoid severity escalation. The degree of impact as described in the deinition of alarm severity refers to the impact of a single index, such as reliability and security. Once the impact on any of the index reaches the speciied threshold, the severity level of the alarm can be roughly determined. If an alarm has an impact on multiple indices, alarm severity should be escalated accordingly. 2 Conidential and Proprietary Information of ZTE CORPORATION Chapter 1 Overview � � Alarm Type Note: Alarm severity can be modiied in NetNumen R31 NMS (Network Management System) if necessary. The default alarm severity is reasonably set. think twice before making any modiication. Users should In addition, the severity of a few alarms is undetermined. It is up to users to deine the severity of such alarms. Alarm is classiied into six types according to alarm trigger condition and its system impact: � Equipment alarm: related with device hardware. � Processing alarm: related with software or process fault (ITU-T Recommendation X.733). � � � � Communication alarm: related with information transmission (ITU-T Recommendation X.733). Environment alarm: related with the environment where the equipment is located (ITU-T Recommendation X.733). QoS alarm: related with degradation of service quality (ITU-T Recommendation X.733). OMS alarm: related with the NMS. Probable Cause Probable alarm causes are enumerated to help users troubleshoot, ind preventive measures, and restore the system to normal state in a timely manner. System Impact System impact refers to the impact that the alarm incurs on system or services. Handling Suggestion Troubleshooting measures and suggestions are provided. Pay attention to the following tips when handling alarms. � After recording the fault phenomenon, OAM personnel may handle the fault step by step as described in the Handling Suggestion Section of this manual. If the fault is removed (alarm restored) at any handling step, terminate the handling process. If the fault is not removed, go ahead to the next handling step. Conidential and Proprietary Information of ZTE CORPORATION 3 ZXG10 iBSC Alarm Handling Reference � If the fault cannot be removed, contact the local ZTE ofice as soon as possible. Notification Notification Property Notiication Code Description Importance Notiication Type Notiication code is the identiier to differentiate notiications. Notiication code is deined by a 32-bit ield indicating the speciic code value. Notiication description relects such content as fault cause and fault phenomenon in a simple and straightforward way. There are two levels of notiication importance: Important and Ordinary. No notiication type exists. Probable Cause Probable notiication causes are enumerated to help users troubleshoot, ind preventive measures, and restore the system to normal state in a timely manner. System Impact System impact refers to the impact that the notiication incurs on system or services. Handling Suggestion Troubleshooting measures and suggestions are provided. Pay attention to the following tips when handling notiications. � � 4 After recording the fault phenomenon, OAM personnel may handle the fault step by step as described in the Handling Suggestion Section of this manual. If the fault is removed at any handling step, terminate the handling process. If the fault is not removed, go ahead to the next handling step. If the fault cannot be removed, or the system normal operation cannot be restored, contact the local ZTE ofice as soon as possible. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Table of Contents 198000002 Loss of optical signal .........................................13 198000256 Ethernet link to OMC is broken. ..........................15 198000518 Trunk link is used for CSU loop back test..............15 198001026 Loss of ATM Cell Synchronization over E1 Link ......................................................................................16 198001027 ATM link is down...............................................17 198001284 The phase of 8K, 16K clock, input to backplane board, is not matched ........................................................17 198001285 SDH/SONET:Excessive Error Code ......................18 198001286 Input clock of board lost ....................................18 198001792 Loss of SDH transmission link .............................19 198002560 Board CPU overload ..........................................21 198002561 High temperature on CPU board..........................21 198005121 Inter-shelf media plane links abnormal ................22 198005124 Capacity of TRUNK communication is insuficient ................................................................................23 198005125 GE optical connection is cross connected..............24 198005376 Internal media port of board is abnormal .............25 198005381 Input clock is abnormal .....................................26 198005389 CPU sub card in position is not conigured in the database ..........................................................................26 198005390 CPU sub card is missing from slot but is conigured in database.......................................................................27 198005395 External port abnormal ......................................27 198005396 Exceptional communication on UIM board or back plane ..............................................................................28 198005399 DSP resource is unavailable................................29 198005403 Board SRAM self-check fails ...............................30 198005404 Board OCXO oven fault ......................................31 198005405 Clock board phase-lock loop work mode abnormal .................................................................................31 198005632 Hard disk usage rate exceeds threshold. .............32 198005633 OMP hard disk is faulty ......................................32 198005635 The board is not plugged irmly ..........................33 198005636 SMBUS error ....................................................33 198005637 Back card does not match with front board...........34 198005638 LVDS signal unlocked ........................................34 198005639 High Error Rate of Optical Interface ....................35 198005640 FPGA exception ................................................36 198005641 Port Link Down .................................................36 198005643 Phase-lock loop work mode abnormal ..................37 198005644 The channel in a sub card is down.......................37 198005645 Sub card abnormal ...........................................38 198005646 Phase-lock loop unlocked ..................................39 198005647 High BER on E1 link ..........................................40 Conidential and Proprietary Information of ZTE CORPORATION 5 ZXG10 iBSC Alarm Handling Reference 198005648 Control plane port of backboard joining switching chip is exceptional ............................................................40 198005655 Errors detected in DSP ......................................41 198005656 Input clock of subcard lost .................................41 198005657 Error of LVDS path frame detection ....................42 198005658 Failure in diagnosing link loop back of large T network ................................................................................43 198005660 Physical link down between master port and slave port .................................................................................43 198005661 Physical link down between media interface ports ...............................................................................44 198005662 IDE running overtime ........................................44 198005663 Component fault ...............................................45 198005665 Fault on board (GPS) ........................................45 198005667 E1 is looped back..............................................46 198005668 Cross-linked E1 alarm .......................................47 198005669 Synchronization status check of FPGA failed .........48 198005671 Sending or receiving packets using the cascade ports inner board failed ......................................................48 198005893 Memory check failed .........................................49 198006400 Cx29704 runs abnormally ..................................49 198015874 Data trafic to PSN board is congested .................50 198015875 GLI table lookup failed.......................................50 198015876 GLI exception packets statistic over threshold ..................................................................................51 198015877 GLIQV SRAM/DRAM error...................................51 198019456 All high-speed links between line card and switching boards are out of synchronization ...................................52 198019465 CSIX RX and TX packets is abnormal ...................53 198019712 APS channel mismatched ...................................53 198019713 APS mode mismatched ......................................54 198019714 APS coniguration alarm.....................................55 198019715 MS APS channel gets errors................................56 198019968 No response to request L2 Forwarding Table information from DBS. ..........................................................57 198019969 No response to request L2 Forwarding Table port information from SCS.........................................................57 198019970 Resource board can't get L2 Forwarding Table. .................................................................................59 198025601 TSNB internal connection chip fault .....................59 198025602 TDM switch abnormal ........................................60 198026116 PP2S output clock lost .......................................60 198026117 PP2S clock reference lost ...................................61 198026118 16CHIP clock reference lost................................61 198026127 Loss of Level 3 reference source clock .................62 198026128 Loss of Level2 reference source clock .................62 198026129 Loss of Level1 reference source clock ..................63 198026131 CLKG board PLL is unlocked. Clock will drift .........64 198026133 Output clock lost...............................................64 198028672 80g chip abnormal ............................................65 198029952 802.3ah link fault .............................................65 198030208 Fault alarm of CFM ............................................66 198066033 T-net center is fault ..........................................67 198066038 The version of the EPU does not accord with that of the RPU ........................................................................67 198066070 Board ofline or CPU in reset status for a long period ..............................................................................68 198087000 Dry contact alarm 1 ..........................................68 198087001 Dry contact alarm 2 ..........................................69 198087002 Dry contact alarm 3 ..........................................69 6 Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198087003 Dry contact alarm 4 ..........................................69 198087004 Dry contact alarm 5 ..........................................70 198087005 Dry contact alarm 6 ..........................................70 198087006 Dry contact alarm 7 ..........................................71 198087007 Dry contact alarm 8 ..........................................71 198087008 Dry contact alarm 9 ..........................................71 198087009 Dry contact alarm 10.........................................72 198087010 Dry contact alarm 11.........................................72 198087011 Dry contact alarm 12.........................................73 198087012 EAM dry contact 1 alarm ...................................73 198087013 EAM dry contact 2 alarm....................................73 198087014 EAM dry contact 3 alarm....................................74 198087015 EAM dry contact 4 alarm....................................74 198087016 EAM dry contact 5 alarm....................................75 198087017 EAM dry contact 6 alarm....................................75 198087018 EAM dry contact 7 alarm....................................75 198087019 EAM dry contact 8 alarm....................................76 198087100 CMM/CMB FLASH programming failure .................76 198087101 HW link broken.................................................77 198087102 Power overvoltage/undervoltage alarm ................77 198087103 13M input clock failure ......................................77 198087104 Frame No. inconsistent between software and hardware..........................................................................78 198087105 FCLK clock failure .............................................78 198087106 SYNCLK clock failure .........................................79 198087107 Master and slave communication link failure .........79 198087108 Standby CMM/CMB board is not in position. ..........80 198087109 Standby CMM/CMB board abnormal.....................80 198087110 CMM/CMB board has powered off. .......................81 198087111 Master rack communication link alarm ................81 198087112 Communication link alarm between master and slave rack (left) ................................................................82 198087113 Communication link alarm between master and slave rack (right) ..............................................................82 198087114 A interface E1 recieves TRX alarm .......................83 198087115 A interface E1 reciever out of frame alarm ...........83 198087116 A interface E1 sender forward-bit-slip indication .................................................................................84 198087117 A interface E1 sender backward-bit-slip indication .................................................................................85 198087118 A interface E1 reciever forward-bit-slip indication .................................................................................85 198087119 A interface E1 reciever backward-bit-slip indication .................................................................................86 198087120 A interface E1 remote alarm...............................86 198087121 B interface E1 recieves TRX alarm .......................87 198087122 B interface E1 reciever out of frame alarm ...........88 198087123 B interface E1 sender forward-bit-slip indication .................................................................................88 198087124 B interface E1 sender backward-bit-slip indication .................................................................................89 198087125 B interface E1 reciever forward-bit-slip indication .................................................................................90 198087126 B interface E1 reciever backward-bit-slip indication .................................................................................90 198087127 B interface E1 remote alarm...............................91 198087128 C interface E1 recieves TRX alarm .......................91 198087129 C interface E1 reciever out of frame alarm ...........92 198087130 C interface E1 sender forward-bit-slip indication .................................................................................93 Conidential and Proprietary Information of ZTE CORPORATION 7 ZXG10 iBSC Alarm Handling Reference 198087131 C interface E1 sender backward-bit-slip indication .................................................................................93 198087132 C interface E1 reciever forward-bit-slip indication .................................................................................94 198087133 C interface E1 reciever backward-bit-slip indication .................................................................................94 198087134 C interface E1 remote alarm...............................95 198087135 D interface E1 recieves TRX alarm.......................96 198087136 D interface E1 reciever out of frame alarm ...........96 198087137 D interface E1 sender forward-bit-slip indication .................................................................................97 198087138 D interface E1 sender backward-bit-slip indication .................................................................................98 198087139 D interface E1 reciever forward-bit-slip indication .................................................................................98 198087140 D interface E1 reciever backward-bit-slip indication .................................................................................99 198087141 D interface E1 remote alarm ..............................99 198087142 E interface E1 recieves TRX alarm ..................... 100 198087143 E interface E1 reciever out of frame alarm.......... 101 198087144 E interface E1 sender forward-bit-slip indication ............................................................................... 101 198087145 E interface E1 sender backward-bit-slip indication ............................................................................... 102 198087146 E interface E1 reciever forward-bit-slip indication ............................................................................... 103 198087147 E interface E1 reciever backward-bit-slip indication ............................................................................... 103 198087148 E interface E1 remote alarm ............................. 104 198087149 F interface E1 recieves TRX alarm ..................... 104 198087150 F interface E1 reciever out of frame alarm .......... 105 198087151 F interface E1 sender forward-bit-slip indication ............................................................................... 106 198087152 F interface E1 sender backward-bit-slip indication ............................................................................... 106 198087153 F interface E1 reciever forward-bit-slip indication ............................................................................... 107 198087154 F interface E1 reciever backward-bit-slip indication ............................................................................... 107 198087155 F interface E1 remote alarm ............................. 108 198087156 G interface E1 recieves TRX alarm..................... 109 198087157 G interface E1 reciever out of frame alarm ......... 109 198087158 G interface E1 sender forward-bit-slip indication ............................................................................... 110 198087159 G interface E1 sender backward-bit-slip indication ............................................................................... 111 198087160 G interface E1 reciever forward-bit-slip indication ............................................................................... 111 198087161 G interface E1 reciever backward-bit-slip indication ............................................................................... 112 198087162 G interface E1 remote alarm ............................ 112 198087163 H interface E1 recieves TRX alarm..................... 113 198087164 H interface E1 reciever out of frame alarm ......... 114 198087165 H interface E1 sender forward-bit-slip indication ............................................................................... 114 198087166 H interface E1 sender backward-bit-slip indication ............................................................................... 115 198087167 H interface E1 reciever forward-bit-slip indication ............................................................................... 116 8 Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198087168 H interface E1 reciever backward-bit-slip indication ............................................................................... 116 198087169 H interface E1 remote alarm............................. 117 198087170 Temperature alarm ......................................... 117 198087171 Fan not-in-position alarm ................................. 118 198087172 Fan control board CPU alarm ........................... 118 198087173 Fan alarm ..................................................... 118 198087174 Fan environment temperature alarm.................. 119 198087175 Fan 1 alarm ................................................... 119 198087176 Fan 2 alarm ................................................... 120 198087177 Fan controller module alarm ............................. 121 198087178 Low Noise Ampliier (LNA) alarm ....................... 121 198087179 Tower ampliier power alarm ............................ 121 198087180 SWR of AEM HYCOM minor alarm ...................... 122 198087181 SWR of AEM HYCOM major alarm...................... 122 198087182 AEM power alarm(BTS V2) ............................... 123 198087183 AEM type alarm(BTS V2).................................. 123 198087184 AEM not-in-posion alarm (BTS V2) .................... 124 198087185 AEM power alarm............................................ 124 198087186 LNA0 overcurrent alarm................................... 125 198087187 LNA0 overcurrent alarm................................... 125 198087188 Tower ampliier 0 overcurrent alarm .................. 126 198087189 Tower ampliier 1 overcurrent alarm .................. 126 198087190 SWR of AEM HYCOM minor alarm ..................... 127 198087191 SWR of AEM HYCOM major alarm ..................... 128 198087192 AEM type alarm .............................................. 128 198087193 AEM not-in-posion alarm.................................. 129 198087194 CHP DSP0 of TPU initialization failure(BTS V2)................................................................................ 130 198087195 CHP DSP1 of TPU initialization failure................. 130 198087196 CHP DSP2 of TPU initialization failure................. 131 198087197 CHP DSP3 of TPU initialization failure................. 131 198087198 Uplink ADC chip initialization failure................... 132 198087199 Uplink ADC resource unavailable ....................... 132 198087200 CIP resource unavailable.................................. 132 198087201 Uplink failure.................................................. 133 198087202 TPU FLASH Memory failure(BTS V2) .................. 133 198087203 Watchdog of TPU CHP DSP0 overlow(BTS V2)................................................................................ 134 198087204 Watchdog of TPU CHP DSP1 overlow................. 134 198087205 Watchdog of TPU CHP DSP2 overlow................. 135 198087206 Watchdog of TPU CHP DSP3 overlow................. 135 198087207 Watchdog of FUC overlow ............................... 135 198087208 Wrong coniguration of TPU Channel 0 ............... 136 198087209 Wrong coniguration of TPU Channel 1 ............... 136 198087210 Wrong coniguration of TPU Channel 2 ............... 137 198087211 Wrong coniguration of TPU Channel 3 ............... 137 198087212 Wrong coniguration of TPU Channel 4 ............... 138 198087213 Wrong coniguration of TPU Channel 5 ............... 138 198087214 Wrong coniguration of TPU Channel 6 ............... 139 198087215 Wrong coniguration of TPU Channel 7 ............... 139 198087216 Cell parameter coniguration mismatch (processing error) (BTS V2) .......................................................... 140 198087217 Software version of FUC mismatch(BTS V2) ......... 140 198087218 Software version of CHP mismatch(BTS V2) ......... 141 198087219 FUC has not responsed with CMM in time (BTS V2)................................................................................ 141 198087220 LAPD communication link between FUC and BSC broken ........................................................................... 142 Conidential and Proprietary Information of ZTE CORPORATION 9 ZXG10 iBSC Alarm Handling Reference 198087221 Communication between CMM and FUC breaks (communication) (BTS V2)................................................ 142 198087222 CIP of TPU initialization failure .......................... 143 198087223 Wrong parameter coniguration for CIP .............. 144 198087224 Watchdog of TPU CIP overlow .......................... 144 198087225 Software version of CIP mismatch ..................... 145 198087226 Clock alarm for TPU and CMM ........................... 145 198087227 TPU power alarm(BTS V2)................................ 145 198087228 TPU frame No. alarm....................................... 146 198087229 TPU CHP DSP0 initialization failure .................... 146 198087230 ADC resource unavailable ................................ 147 198087231 CHP frame numbers has fault. .......................... 147 198087232 BURST interruption error ................................. 148 198087233 TPU FLASH memory failure............................... 148 198087234 TPU CHP DSP0 watchdog overlow..................... 149 198087235 Wrong coniguration for TRX Channel 0 .............. 149 198087236 Wrong coniguration of TRX Channel 1 ............... 150 198087237 Wrong coniguration of TRX Channel 2 ............... 150 198087238 Wrong coniguration of TRX Channel 3 ............... 151 198087239 Wrong coniguration of TRX Channel 4 ............... 152 198087240 Wrong coniguration of TRX Channel 5 ............... 152 198087241 Wrong coniguration of TRX Channel 6 ............... 153 198087242 Wrong coniguration of TRX Channel 7 ............... 153 198087243 Cell coniguration parameter mismatch .............. 154 198087244 FUC software version mismatch ........................ 154 198087245 CHP software version mismatch ........................ 155 198087246 CU software version mismatch.......................... 155 198087247 HDLC communication link between CMB and FUC broken ........................................................................... 156 198087248 LAPD communication link between FUC and BSC broken ........................................................................... 156 198087249 CU initialization failure..................................... 157 198087250 CU parameter coniguration error ...................... 158 198087252 TPU power alarm ............................................ 158 198087253 FU frame number error alarm ........................... 159 198087254 Rx Local Oscillator (LO) PLL1 lost lock alarm ......... 159 198087255 Rx Local Oscillator (LO) PLL2 lose lock alarm............................................................................. 160 198087256 Tx Local Oscillator (LO) PLL1 lose lock alarm ......... 160 198087257 Tx Local Oscillator (LO) PLL2 lose lock alarm ......... 161 198087258 52M reference clock PLL lose lock alarm............. 161 198087259 Tx IF Local Oscillator (LO) PLL lose lock alarm............................................................................. 162 198087260 EEPROM resource unavailable alarm .................. 162 198087261 FPGA interface failure ...................................... 163 198087262 PA VSWR alarm(BTS V2).................................. 163 198087263 PA overtemperature minor alarm(BTS V2) ......... 164 198087264 PA overtemperature major alarm(BTS V2).......... 164 198087265 PA output power alarm .................................... 165 198087266 PA power overvoltage ...................................... 165 198087267 PA power is undervoltage ................................ 166 198087268 Downlink checksum error of DLRC_AL1.............. 166 198087269 DUC chip initialization failure ............................ 166 198087270 80w PA VSWR alarm ....................................... 167 198087271 80w PA 's temperature is a litter high. ............... 167 198087272 80w PA overtemperature major alarm ............... 168 198087273 80w PA output power alarm ............................. 168 198087274 80w PA power overvoltage ............................... 169 198087275 80w PA 's power is undervoltage . ..................... 169 198087276 80w PA not-in-position alarm............................ 170 10 Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198087277 TXIF lock is lost. ............................................. 170 198087278 TPF clock is unlocked....................................... 170 198087279 TXRF lost lock alarm........................................ 171 198087280 RXRF clock is unlocked . .................................. 172 198087281 13 MHz clock is lost......................................... 172 198087282 60ms synchronous clock lost alarm ................... 173 198087283 8M clock of HW is lost. .................................... 173 198087284 HW 8K synchronous signal is lost . .................... 174 198087285 RF board 52MHz clock lost alarm....................... 174 198087286 First ADC clock is lost. ..................................... 175 198087287 Second ADC clock is lost. ................................. 176 198087288 PA power is overvoltage................................... 176 198087289 PA power is undervoltage................................. 177 198087290 PA VSWR alarm .............................................. 177 198087291 PA temperature is a little high. (TRX level alarm, exceeds 80℃) ................................................................. 177 198087292 PA temperature is much more higher. (TRX level alarm, exceeds 95 ℃) ...................................................... 178 198087293 PA forward power(3db) alarm ........................... 179 198087294 RTU power is abnormal.................................... 179 198087295 The temperature of RTU power is too high. ......... 180 198087296 The output of RTU power is overvoltage. ............ 180 198087297 RTU power input abnormal alarm ...................... 181 198087298 IQ calibration parameters are abnormal. ............ 181 198087299 EAM heat exchanger alarm............................... 181 198087300 CMB0 heating ilm alarm.................................. 182 198087301 CMB1 heating ilm alarm.................................. 182 198087302 EAM has had smoke . ...................................... 183 198087303 EAM has had water.......................................... 183 198087304 EAM lightning protection alarm. ........................ 184 198087305 EAM backdoor access is intruded....................... 184 198087306 EAM frontdoor access is intruded. ..................... 185 198087307 EAM PWR monitoring unit has fault. .................. 185 198087308 FIB heating ilm alarm ..................................... 185 198087309 EAM heat exchanger control board has fault. ............................................................................. 186 198087310 EAM heat exchanger external circulation fan 2 alarm............................................................................. 186 198087311 EAM heat exchanger external circulation fan 1 alarm............................................................................. 187 198087312 EAM heat exchanger internal circulation fan 2 alarm............................................................................. 187 198087313 EAM heat exchanger internal circulation fan 1 alarm............................................................................. 188 198087314 EAM heat exchanger 's 485 communication has fault. ............................................................................. 188 198087315 EAM temperature is abnormal........................... 189 198087316 EAM TRX layer mixed-low fan 1 has fault. ......... 189 198087317 EAM TRX layer mixed-low fan 2 has fault. ......... 189 198087318 EAM TRX layer mixed-low fan 3 has fault. ......... 190 198087319 Communication is broken between EAM and CMB. ............................................................................. 190 198087320 Power undervoltage alarm................................ 191 198087321 Inner fan engine 2 alarm (for M8202)................ 191 198087322 Inner fan engine 1 alarm (for M8202)................ 192 198087323 Outer fan engine 2 and 4 alarm (for M8202) ......... 192 198087324 Outer fan engine 1 and 3 alarm (for M8202) ......... 193 198087325 Rack temperature minor alarm ......................... 193 198087326 Rack temperature major alarm ......................... 194 198087327 Layer 3 fan 1 alarm (for M8206) ....................... 194 Conidential and Proprietary Information of ZTE CORPORATION 11 ZXG10 iBSC Alarm Handling Reference 198087328 Layer 3 fan 2 alarm (for M8206) ....................... 194 198087329 Layer 3 fan 3 alarm (for M8206) ....................... 195 198087330 Layer 2 fan 1 alarm (for M8206) ....................... 195 198087331 Layer 2 fan 2 alarm (for M8206) ....................... 196 198087332 Layer 2 fan 3 alarm (for M8206) ....................... 196 198087333 Layer 1 fan 1 alarm (for M8206) ....................... 197 198087334 Layer 1 fan 2 alarm (for M8206) ....................... 197 198087335 Layer 1 fan 3 alarm (for M8206) ....................... 198 198087340 FR device failure ............................................. 198 198087342 Cell interruption alarm..................................... 199 198087361 The CRC calibration of PA parameter turns to be error ............................................................................. 200 198087379 OMP reboot alarm ........................................... 200 198087386 SYNCLK losing lock alarm ................................ 201 198087387 Status of TX1 ilter alarm ................................. 201 198087388 Status of TX2 ilter alarm ................................. 201 198087389 Status of TX3 ilter alarm ................................. 202 198087390 Status of TX4 ilter alarm ................................. 202 198087391 FCU power undervoltage alarm ......................... 203 198087392 FCU minor alarm ............................................ 203 198087403 ABIS-E1 transmission related clock alarm of CCI board............................................................................. 203 198087404 Local working clock alarm of CCI board.............. 204 198087405 13M clock alarm of CCI board . ......................... 204 198087406 CCI opposite board alarm ................................ 205 198087407 IQ FPGA internal clock alarm ............................ 205 198087408 IQ FPGA light interface alarm .......................... 205 198087409 IQ FPGA LVDS interface alarm .......................... 206 198087410 IQ FPGA internal data alarm ............................. 206 198087411 13M and 61.44M clock lost alarm ...................... 207 198087412 FR or FN has error........................................... 207 198087413 26MHz and 52MHz Phase Locked Loop (PLL) lose lock alarm ...................................................................... 208 198087414 Detect failure alarm of uplink 60ms hyperframe synchronization head ....................................................... 208 198087415 Checking block data error alarm ....................... 209 198087416 Uplink LVDS SERDES lost lock alarm.................. 209 198087417 FN error alarm................................................ 209 198087432 Diversity antenna lost...................................... 210 198087433 Diversity antenna identical. .............................. 210 198087443 Diversity antenna lost alarm............................. 211 198087444 Diversity antenna identical alarm ...................... 211 198087451 Board does not support 16MHW. ....................... 211 198087452 CMB CPU overload alarm ................................. 212 198087453 Signalling HDLC is broken . .............................. 212 198087454 Main dimensional HDLC broken alarm ................ 213 198087455 FIB coniguration exception alarm ..................... 213 198087456 FIB software layer 3 no response ...................... 214 198087457 FIB CPU overload alarm ................................... 214 198087458 BVC block alarm ............................................. 215 198087460 +12V voltage alarm ........................................ 215 198087461 -12V voltage alarm ......................................... 216 198087462 DSP 1.2V voltage alarm ................................... 216 198087463 6.4V voltage alarm ......................................... 216 198087464 5V voltage alarm ............................................ 217 198087470 Fan engine not-in-position alarm....................... 217 198087471 Fan engine rotation speed alarm ....................... 218 198087472 CMB and FNCB RS485 link broken alarm ............ 218 198087473 DTPU CPU is overloaded................................... 218 198087480 Status of TX5 ilter alarm ................................. 219 12 Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198087481 Status of TX6 ilter alarm ................................. 219 198087483 GPS signal synchronization exception ................ 219 198087484 Second pulse lost alarm................................... 220 198087485 Antenna open-circuit alarm .............................. 220 198087486 Antenna short-circuit alarm .............................. 221 198087487 Lost satellite alarm ......................................... 221 198087505 GUP board connection failure............................ 222 198088000 DTPU does not support baseband freqency-hopping alarm...................................................................... 222 198088001 PA voltage adjusting path has broken. ............... 223 198088002 PA voltage adjusting read/write error. ................ 223 198088003 PA voltage adjusting parameter turns to be error. ................................................................................ 224 198088004 Access iBSC failure.......................................... 224 198088005 Control link broken ......................................... 225 198088006 Operation link broken(CS)................................ 225 198088007 Operation link broken(PS) ................................ 225 198088008 Parameter coniguration mismatch .................... 226 198088009 DSP initialization failure ................................... 226 198088010 Parameter coniguration failure of AD6537 ......... 227 198088011 Tx PLL lost lock alarm...................................... 227 198088012 Wrong parameter coniguration for EEPROM ......... 227 198088013 FLASH memory fault ....................................... 228 198088014 DSP works abnormally. .................................... 228 198088015 FPGA interface fault ........................................ 229 198088016 CHP frame porcessing error alarm ..................... 229 198088017 Wrong receive channel of RF ............................ 229 198088018 Acquiring DNS failure under dynamic conigured IP mode ......................................................................... 230 198088019 Analysis failure of DNS domain name ................ 230 198088020 IPSec start failure ........................................... 231 198088021 Frequency point and HTRG mismatch alarm ......... 231 198088022 DHCP automatically acquiring IP address failure ................................................................................ 231 198088023 Overhigh temperature alarm ............................ 232 198088024 Voltage abnormity........................................... 232 198088025 Abis link switch alarm...................................... 233 198088027 DIP E1 rack, rack type error ............................. 233 198088028 DIP E1 rack, rack number error ........................ 233 198088029 DIP E1 rack, slave rack port 1 error................... 234 198088030 DIP E1 rack, slave rack port 2 error................... 234 198088031 DIP E1 rack,satellite back up lag error .............. 235 198088032 DIP E1 rack, OAM time slot error. ...................... 235 198088033 DIP IP rack,access mode error(IP or IPOE) ......... 236 198088034 DIP IP rack,rack number error .......................... 236 198088035 DIP IP rack,site number error ........................... 236 198088036 DIP IP rack,sequence number error ................... 237 198088037 Mains power failure alarm ................................ 237 198000002 Loss of optical signal Alarm Property � � Alarm Code:198000002 Description:Loss of optical signal Conidential and Proprietary Information of ZTE CORPORATION 13 ZXG10 iBSC Alarm Handling Reference � Probable Cause � Severity:Major Alarm Type:Equipment Alarm 1. The receiving optical iber/module of local equipment is faulty. Receiving optical iber is faulty or disconnected. Optical connector is polluted. Receiving optical module is faulty. 2. The transmitting optical iber of opposite equipment is faulty. Transmitting optical iber is faulty or disconnected. Optical connector is polluted. 3. The receiving optical power at local end is excessively low. Optical power attenuation on the receiving iber transmission line at local end is too much. Transmitting optical power at opposite end is too low. 4. Operation of LOS insertion is performed at opposite end. Manual operation of LOS insertion is performed in diagnostic test, and optical module is shutdown by force. Speciic Problem 5. Optical iber and optical module is incompatible. The iber transmission rate and the optical module wavelength are incompatible. 1. The receiving optical iber/module of local equipment is faulty. Receiving optical iber is faulty or disconnected. Optical connector is polluted. Receiving optical module is faulty. 2. The transmitting optical iber of opposite equipment is faulty. Transmitting optical iber is faulty or disconnected. Optical connector is polluted. 3. The receiving optical power at local end is excessively low. Optical power attenuation on the receiving iber transmission line at local end is too much. Transmitting optical power at opposite end is too low. 4. Operation of LOS insertion is performed at opposite end. Manual operation of LOS insertion is performed in diagnostic test, and optical module is shutdown by force. System Impact Handling Suggestion 5. Optical iber and optical module is incompatible. The iber transmission rate and the optical module wavelength are incompatible. The optical interface fails to work normally. If the optical interface is conigured with APS protection, service will be switched to protection optical interface. Otherwise, all services on the optical interface will be down. 1. Carry out loop test to determine whether the alarm is caused by local end or opposite end. Perform iber self-loop at local equipment. If the alarm persists, fault might lie in local equipment. If the alarm disappears, inform the opposite end to troubleshoot. 2. Replace the optical module. 3. Replace iber. 4. Replace board. 14 Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198000256 Ethernet link to OMC is broken. Alarm Property Probable Cause � Alarm Code:198000256 � Severity:Minor � � Description:Ethernet link to OMC is broken. Alarm Type:Equipment Alarm 1. No network cable is connected with Network Port OMC or OMC2 on rear board. 2. Network cable is disconnected or cable connector is loose. Speciic Problem 3. Network port on the board is faulty. 1. No network cable is connected with Network Port OMC or OMC2 on rear board. 2. Network cable is disconnected or cable connector is loose. System Impact Handling Suggestion 3. Network port on the board is faulty. Master/slave switching will occur if OMP is conigured in master/slave mode. If master/slave switching is normal, system will not be affected. If master/slave switching is abnormal, OMP board will fail to obtain version package from NMS, leading to board power-on failure, UE access failure, and interruption of ongoing services. 1. Ensure that network cable is connected to Network Port OMC or OMC 2. Unplug and plug the network cable on Network Port OMC or OMC2 Of OMP board 3. Check if OMC or OMC2 network cable works normally. If no, replace the cable. 198000518 Trunk link is used for CSU loop back test Alarm Property Probable Cause Speciic Problem � Alarm Code:198000518 � Severity:Minor � � Description:Trunk link is used for CSU loop back test Alarm Type:Equipment Alarm The equipment at end A sends CSU link building code to end B, and this trunk link is set to loop back at end B. And CSU test starts.If this trunk link is not used for CSU loop back test, this alarm won't be triggered. The equipment at end A sends CSU link building code to end B, and this trunk link is set to loop back at end B. And CSU test starts.If Conidential and Proprietary Information of ZTE CORPORATION 15 ZXG10 iBSC Alarm Handling Reference System Impact Handling Suggestion Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion this trunk link is not used for CSU loop back test, this alarm won't be triggered. The conigured trunk link is blocked. End A sends the command of canceling CSU loop back to end B. 198001026 Loss of ATM Cell Synchronization over E1 Link � Alarm Code:198001026 � Severity:Minor � � Description:Loss of ATM Cell Synchronization over E1 Link Alarm Type:Equipment Alarm 1. Cell Header HEC (Header Error Check) is damaged, leading to cell location failure in physical layer frame. 2. The alarm is caused by bottom layer fault. Cell HEC is handled differently at local end and opposite end. 1. Cell Header HEC (Header Error Check) is damaged, leading to cell location failure in physical layer frame. 2. The alarm is caused by bottom layer fault. Cell HEC is handled differently at local end and opposite end. Data reception on E1 link is abnormal. If merely one E1 link is available for the port, all services on the board will be down. Otherwise, port bandwidth will be affected, leading to decreased access bandwidth. The number of successful upper-layer service access related to the port will decrease, but service interruption will not occur. 1. Check if the following alarm occurs in the board. If yes, refer to the corresponding alarm handling suggestion. Related alarms: 519 Trunk error 520 Trunk abnormal 2. On NMS coniguration management interface, check if SDH/SONET mode is conigured for both ends. Ensure that the coniguration at both ends is consistent. 3. Use meter measurement or loop test to judge whether the alarm is caused by local end or opposite end. Meter Measurement Use a trunk test meter to test whether the trunk receiving signals at local end are normal. If normal, fault might lie in local equipment. If abnormal, troubleshoot at opposite end. Loop Test Perform self-loop at local trunk. If the alarm persists, fault might lie in local equipment. If the alarm disappears, inform the opposite end to troubleshoot. 4. Replace trunk cable. 5. Replace board. 16 Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198001027 ATM link is down Alarm Property � Alarm Code:198001027 � Severity:Minor � � Description:ATM link is down Alarm Type:Equipment Alarm Probable Cause 1. Bottom layer physical link is abnormal. Speciic Problem 1. Bottom layer physical link is abnormal. System Impact Handling Suggestion 2. HEC handling at local end and opposite end is inconsistent. 2. HEC handling at local end and opposite end is inconsistent. Communication at ATM port is down. All services based on the trunk are interrupted. 1. Check if the following board alarm occurs. If yes, refer to corresponding alarm handling suggestion. Related alarms: 519 Trunk error 520 Trunk abnormal 2. On NMS coniguration management interface, check if SDH/SONET mode coniguration exists at both ends. Ensure that the coniguration at both ends is consistent. 3. Use meter measurement or loop test to judge whether the alarm is caused by local end or opposite end. Meter Measurement Use a trunk test meter to test whether the receiving trunk signals at local end are normal. If normal, fault might lie in local equipment. If abnormal, troubleshoot at opposite end. Loop Test Perform self-loop at local trunk. If the alarm persists, fault might lie in local equipment. If the alarm disappears, troubleshoot at opposite end. 4. Replace trunk cable. 5. Replace board. 198001284 The phase of 8K, 16K clock, input to backplane board, is not matched Alarm Property Probable Cause � Alarm Code:198001284 � Severity:Minor � � Description:The phase of 8K, 16K clock, input to backplane board, is not matched Alarm Type:Equipment Alarm 1. Clock cable is not properly connected. Conidential and Proprietary Information of ZTE CORPORATION 17 ZXG10 iBSC Alarm Handling Reference Speciic Problem System Impact Handling Suggestion 2. Clock board is faulty. 1. Clock cable is not properly connected. 2. Clock board is faulty. The system fails to achieve synchronization so that the board can not work normally. As a result, UE can not be accessed and services borne on the board are interrupted. 1. Check the clock input cable and ensure that the cable is good and well connected. 2. Clock board changeover. 3. UIM/GUIM board changeover. 4. Replace the board. 198001285 SDH/SONET:Ex cessive Error Code Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198001285 � Severity:Minor � � Description:SDH/SONET:Excessive Error Code Alarm Type:Equipment Alarm The board experiences reset. The SETS chip and the crystal oscillator need to be fully preheated. The board experiences reset. The SETS chip and the crystal oscillator need to be fully preheated. SDH/SONET equipment can work. However, call loss or noise occurs to all voice services on this optical path, and bit error occurs on the data service channel. Normal procedure after board reset, please wait for the end of warm-up procedure. Clock tests can be taken unless this alarm is cleared. 198001286 Input clock of board lost Alarm Property Probable Cause 18 � Alarm Code:198001286 � Severity:Minor � � Description:Input clock of board lost Alarm Type:Equipment Alarm 1. The board is not in place (not properly inserted) in the slot. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 2. Clock cable is disconnected. 3. Clock cable is faulty. Speciic Problem 4. Board is faulty. 1. The board is not in place (not properly inserted) in the slot. 2. Clock cable is disconnected. 3. Clock cable is faulty. System Impact Handling Suggestion 4. Board is faulty. The board fails to synchronize with system clock so that it can not work normally. As a result, UE can not be accessed and services borne on the board are interrupted. 1. Check if the clock (input) cable at the shelf is intact and properly connected. 2. Check if the following alarm occurs in the board. If yes, refer to the corresponding alarm handling suggestion. Related alarm: 5635 The board is not plugged irmly 3. Replace the board. 198001792 Loss of SDH transmission link Alarm Property Probable Cause � Alarm Code:198001792 � Severity:Major � � Description:Loss of SDH transmission link Alarm Type:Equipment Alarm 1. The alarm occurs when the receiving optical power is below optical receiver sensitivity. Generally speaking, normal receiving optical power range for optical modules is between -28 dBm and -8 dBm. Optical signals within this range can be detected. Probable causes for the alarm include: 1. The receiving optical iber/module of local SDH equipment is faulty. Receiving optical iber is faulty or disconnected. Optical connector is polluted. Receiving optical module is faulty. 2. The transmitting optical iber of opposite SDH equipment is faulty. Transmitting optical iber is faulty or disconnected. Optical connector is polluted. 3. The optical transmission line of SDH equipment is faulty. Tail iber and lange between iber distribution frame and the equipment at local end are faulty or disconnected. The related connector is in poor contact. 4. The receiving optical power at local end is excessively low. Optical power attenuation on the iber transmission line at receiving end is too much. Opposite-end transmitting optical power is too low. Conidential and Proprietary Information of ZTE CORPORATION 19 ZXG10 iBSC Alarm Handling Reference 5. Operation of LOS insertion is performed at opposite end. Manual operation of LOS insertion is performed in diagnostic test, and optical module is shutdown by force. Speciic Problem 6. Optical iber and optical module is incompatible. The iber transmission rate of STM signals and the optical module wavelength are incompatible. 1. The alarm occurs when the receiving optical power is below optical receiver sensitivity. Generally speaking, normal receiving optical power range for optical modules is between -28 dBm and -8 dBm. Optical signals within this range can be detected. Probable causes for the alarm include: 1. The receiving optical iber/module of local SDH equipment is faulty. Receiving optical iber is faulty or disconnected. Optical connector is polluted. Receiving optical module is faulty. 2. The transmitting optical iber of opposite SDH equipment is faulty. Transmitting optical iber is faulty or disconnected. Optical connector is polluted. 3. The optical transmission line of SDH equipment is faulty. Tail iber and lange between iber distribution frame and the equipment at local end are faulty or disconnected. The related connector is in poor contact. 4. The receiving optical power at local end is excessively low. Optical power attenuation on the iber transmission line at receiving end is too much. Opposite-end transmitting optical power is too low. 5. Operation of LOS insertion is performed at opposite end. Manual operation of LOS insertion is performed in diagnostic test, and optical module is shutdown by force. System Impact Handling Suggestion 6. Optical iber and optical module is incompatible. The iber transmission rate of STM signals and the optical module wavelength are incompatible. SDH/SONET fails to work normally, leading to UE access failure on SDH/SONET and interruption of ongoing services. 1. Use meter measurement or loop test to judge whether the alarm is caused by local end or opposite end. Meter Measurement Use a SDH test meter or optical power meter to test whether the receiving optical signals at local end are normal. If normal, fault might lie in local equipment. If abnormal, fault lies in opposite end or on transmission side. Inform the opposite end or transmission side to troubleshoot. Loop Test Perform iber self-loop at local SDH equipment. If the alarm persists, fault might lie in local equipment. If the alarm disappears, inform the opposite end to troubleshoot. 2. Replace optical module. 3. Replace optical iber. 4. Replace board. 20 Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198002560 Board CPU overload Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198002560 � Severity:Major � � Description:Board CPU overload Alarm Type:Equipment Alarm 1. Excessive data trafic at higher layer. 2. System is performing data synchronization or saving. 3. CPU alarm threshold setting is under conigured. 1. Excessive data trafic at higher layer. 2. System is performing data synchronization or saving. 3. CPU alarm threshold setting is under conigured. CPU occupancy indicates the current status of system operation. CPU overloaded, or over high occupancy, is usually caused by service or operation that consume much time. It has the following impact on the system: Services with low priority level have little or no access to the processing of CPU, which reduces processing speed of the services or even halts the processing. System board could reset under excessively overloading conditions, causing interruption to the service it performs. 1. Open the rack map on the Coniguration Management window, select Board, right click and select Board Property. Check the CPU overload threshold setting on the CPU Information tab. Please reset CPU overload threshold if the CPU overload threshold value is too low. It will take 30 seconds for the new setting to take effect. Recommended threshold value: 80% for low level load threshold, 90% for high level load threshold. 2. Check for the record of data synchronization, data saving or other ile operations in the network manager log iles. Those operations might increase the CPU utilization rate radically, and it might take 2 minutes. 3. Check for the record of new board added or version upgrade operation in the network manager log iles. Version upgrading operation might increase CPU utilization rate radically, and it might take 2 minutes. 198002561 High temperature on CPU board Alarm Property � Alarm Code:198002561 � Severity:Major � Description:High temperature on CPU board Conidential and Proprietary Information of ZTE CORPORATION 21 ZXG10 iBSC Alarm Handling Reference Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Type:Equipment Alarm 1. Fan faulty. 2. High temperature in rack. 3. CPU overload. 1. Fan faulty. 2. High temperature in rack. 3. CPU overload. Automatic CPU reset might occur. 1. In NMS Coniguration Management interface, click Rack. Right click the concerned board > Show Board Properties Page > CPU1 or CPU 2. Check 2 parameters: Low/High threshold of alarm temperature, Reset temperature. If the settings are low, please adjust the High threshold of alarm temperature and the Reset temperature. The new settings will be valid after 30 seconds. Recommended Thresholds: High threshold of alarm temperature: 90 degrees Celsius, Reset temperature: 95 degrees Celsius. 2. Observe the thermometer in machine room to know room temperature. If it is high, please take effective measures to cool down. 3. Check the surface of the boards. Does it have much dust? If yes, please clean it for better cooling. 4. Check the air intake and air outlet of the rack. Does it have much dust? If yes, please clean it for better ventilation. 5. Make sure the fan(s) on the rack works normally. 6. Replace the fault board. 198005121 Inter-shelf media plane links abnormal Alarm Property Probable Cause � Alarm Code:198005121 � Severity:Major � � Description:Inter-shelf media plane links abnormal Alarm Type:Equipment Alarm 1. The iber connection is error between shelves, or the iber is not physically plugged. 2. The background coniguration of the board is inconsistent with its foreground physical connection. Speciic Problem 22 3. The transceiver of the board link detection packet is exceptional. 1. The iber connection is error between shelves, or the iber is not physically plugged. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 2. The background coniguration of the board is inconsistent with its foreground physical connection. System Impact Handling Suggestion 3. The transceiver of the board link detection packet is exceptional. The inter-shelf service bandwidth is reduced. The inter-shelf services may be interrupted if no backup is conigured. 1. In the NMS Coniguration Management interface, select Unit Connection Relation, then compare the coniguration with actual physical connection. If it is different, adjust connection cables according to the coniguration. 2. Check the connection of optical iber and make sure it is in cross connection. Is there any relevant alarm? If yes, please solve the problem according to recommended handling suggestions. Relevant Alarm: 5125 GE optical transceiver module is wrongly connected to left/right board slots at opposite end 3. Replace the optical iber or the optical transceiver module so that the SD indicator for the corresponding port is on. 4. Replace the local board. 5. Replace the opposite board. 198005124 Capacity of TRUNK communication is insufficient Alarm Property Probable Cause � Alarm Code:198005124 � Severity:Minor � � Description:Capacity of TRUNK communication is insuficient Alarm Type:Equipment Alarm 1. Connection failure 2. Line failure 3. Board failure Speciic Problem 4. Rear board failure . 1. Connection failure 2. Line failure 3. Board failure System Impact 4. Rear board failure . There is no impact on services when TRUNK connection is not adopted for inter-shelf control plane communication. However if TRUNK connection is adopted, this alarm indicates insuficient network communication capability. This may cause congestion at control plane. During heavy trafic period, this may cause much delay or services interruption in extreme condition. Conidential and Proprietary Information of ZTE CORPORATION 23 ZXG10 iBSC Alarm Handling Reference Handling Suggestion 1. Check whether TRUNK connection is used for inter-shelf control plane. If not, no handling is required. 2. Check the number of connections, i.e. 4 FEs and 2 GEs are required. Complete the connections if there is any missing. 3. Check whether the connection is correct. The correct connection is described as below: For FE port trunk, if UIM board is installed on BUSN shelf, then TRUNK connection is not supported. In this case, this alarm won't occur. If UIM is installed on other shelf, FE7, FE8, FE9 and FE10 work together to form a TRUNK port. However if it is GUIM board, FE3, FE4, FE5 and FE6 form a TRUNK port. For CHUB board, every 4 adjacent FE ports form a TRUNK port, such as FE1~FE4, FE5~FE8 etc. For each trunk port, All the 4 RE ports must be connected, and direct connection is recommended. For GE port trunk, 2 GE interfaces (CHUB board inter-connection) are connected in cross-connection mode. The #1 GE port on the left board on the local shelf corresponds to the #1 GE port on the left board on the opposite shelf; the #2 GE port on the left board on the local shelf corresponds to the #2 GE port on the right board of opposite shelf. The #1 GE port on the right board on the local shelf corresponds to the #2 GE port on the left board on the opposite shelf, and the #2 GE port on the left board on the local shelf corresponds to the #2 GE port on the right board on the opposite shelf. 4. Replace the cable or optical module. 5. Replace the rear board. 6. Replace the connected board. 198005125 GE optical connection is cross connected Alarm Property Probable Cause Speciic Problem System Impact 24 � Alarm Code:198005125 � Severity:Minor � � Description:GE optical connection is cross connected Alarm Type:Equipment Alarm 1. ibre connected to wrong module. 2. GE optical transceiver module in wrong slot. 3. transmit and receive ibres crossed. 1. ibre connected to wrong module. 2. GE optical transceiver module in wrong slot. 3. transmit and receive ibres crossed. Cause interruption to all services performed on this shelf. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Handling Suggestion Check the iber optics for its proper cross connection 198005376 Internal media port of board is abnormal Alarm Property Probable Cause � Alarm Code:198005376 � Severity:Major � � Description:Internal media port of board is abnormal Alarm Type:Equipment Alarm 1. Physical failure of the IC at the internal port on the board. 2. Failure of local board connecting port on the switching IC of UIM. 3. Backplane wiring failure of local slot to UIM. 4. CPU overloaded on the irst level switching board, UIM board at the shelf, or local board. Speciic Problem 5. Service over the rated capability of the board. 1. Physical failure of the IC at the internal port on the board. 2. Failure of local board connecting port on the switching IC of UIM. 3. Backplane wiring failure of local slot to UIM. 4. CPU overloaded on the irst level switching board, UIM board at the shelf, or local board. System Impact Handling Suggestion 5. Service over the rated capability of the board. Because internal media stream can not be transmitted via this port, it will select another port for transmission. If all the internal ports are abnormal, the internal media stream will be interrupted and all the services provided on this board will be interrupted. 1. In Alarm Management interface, check the CPU rate, which is located on L1 switching board, the board or UIM/GUIM board of the same shelf. Is there a CPU overloaded alarm? If yes, please solve the problem according to the corresponding handling suggestions. Related Alarm: 2560 Board CPU Overloaded 2. In the Alarm Management interface, check whether there is an alarm, indicating abnormal link at inter-shelf media plane. If yes, please solve the problem according to the corresponding handling suggestions. Related Alarm: 5121 Inter-shelf media plane link fault 3. Replace the board. 4. Change a slot to insert the board. 5. Replace the UIM/GUIM of the same shelf. Conidential and Proprietary Information of ZTE CORPORATION 25 ZXG10 iBSC Alarm Handling Reference 198005381 Input clock is abnormal Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198005381 � Severity:Critical � � Description:Input clock is abnormal Alarm Type:Equipment Alarm 1. The Clock board is abnormal. 2. The clock board is not synchronized with reference clock. 3. The clock reference source is abnormal. 1. The Clock board is abnormal. 2. The clock board is not synchronized with reference clock. 3. The clock reference source is abnormal. The services are interrupted because the system can not get a proper clock. 1. Reconnect the cable between the board and the clock reference. 2. Replace the cable between the board and the clock reference. 3. Check the signal output from the reference clock source. 4. Replace the board. 198005389 CPU sub card in position is not configured in the database Alarm Property � Alarm Code:198005389 � Severity:Warning � � Description:CPU sub card in position is not conigured in the database Alarm Type:Equipment Alarm Probable Cause 1. Coniguration is incorrect. Speciic Problem 1. Coniguration is incorrect. System Impact 26 2. Board is misplaced. 2. Board is misplaced. Since the board where the unconigured sub card is located resets repeatedly, power resource of the equipment is wasted. However, services won't be affected. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Handling Suggestion Is the sub card needed? If no, remove the sub card. If yes, change the type of board so that it can support the sub card. 198005390 CPU sub card is missing from slot but is configured in database Alarm Property � Alarm Code:198005390 � Severity:Major � � Description:CPU sub card is missing from slot but is conigured in database Alarm Type:Equipment Alarm Probable Cause 1. The coniguration is wrong. Speciic Problem 1. The coniguration is wrong. System Impact Handling Suggestion 2. A wrong board is inserted. 2. A wrong board is inserted. The sub-card functions are unavailable, accordingly this board does not support relevant services. The inluence on the system is various according to different type of sub-card. If the sub-card is an interface board, the transmission link via this board is not connectable, then services will be accessed through other sub-card. If the sub-card is a signalling process board, the cell/Node B conigured for this board is not available for services. If the sub-card is a user's plane board, user plane process capability will decline, then services will be accessed through other sub-card. Is the sub-card required? If no, modify the type of board so that the new type doesn't support such sub-card; if yes, insert the subcard irmly. 198005395 External port abnormal Alarm Property Probable Cause � Alarm Code:198005395 � Severity:Major � � Description:External port abnormal Alarm Type:Equipment Alarm 1. The cable is not properly connected or not connected to the port. 2. The port chip on the board is faulty. Conidential and Proprietary Information of ZTE CORPORATION 27 ZXG10 iBSC Alarm Handling Reference Speciic Problem 3. The opposite board is faulty. 1. The cable is not properly connected or not connected to the port. 2. The port chip on the board is faulty. System Impact Handling Suggestion 3. The opposite board is faulty. This port is not available for services. If there is a standby port, data can be received or transmitted via the standby port. But in this case, totally data throughput will decline. Meanwhile, the reliability and stability of the system declines. If there is no standby port, all communication links via this port will be broken, and the services carried via this port will be interrupted. 1. Reconnect or replace the cable. 2. Replace the board. 3. Contact responsible engineers to check the opposite port and remove possible faults. 198005396 Exceptional communication on UIM board or back plane Alarm Property Probable Cause � Alarm Code:198005396 � Severity:Major � � Description:Exceptional communication on UIM board or back plane Alarm Type:Equipment Alarm 1. The internal port chip on the board has a physical fault. 2. The switch IC on UIM/GUIM provides a port, which is connected to the board. This port has a fault. 3. Backplane wiring failure, which connects the slot to UIM. 4. A CPU on L1 switching board, the board, or UIM board of the same shelf, is overloaded. Speciic Problem 5. Service exceeds the processing capability of the board. 1. The internal port chip on the board has a physical fault. 2. The switch IC on UIM/GUIM provides a port, which is connected to the board. This port has a fault. 3. Backplane wiring failure, which connects the slot to UIM. 4. A CPU on L1 switching board, the board, or UIM board of the same shelf, is overloaded. System Impact 28 5. Service exceeds the processing capability of the board. If the internal media plane stream can not be processed, packets may be lost. In this case, services provided by this board become Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Handling Suggestion unstable. If it is port fault or connector fault, the internal media plane is completely broken. In this case, services borne on this board are interrupted. If either CPU or trafic is overloaded, services carried on the board will be delayed. In serious situation, services may be interrupted. 1. In Alarm Management interface, check whether there is an internal media plane port abnormal alarm. If yes, please solve the problem according to corresponding handling suggestion. Related Alarm: 5376 Internal media plane port abnormal 2. In Alarm Management interface, check the CPU rate, which is located on L1 switching board, the board or UIM board of the shelf. Is there a CPU overloaded alarm? If yes, please solve the problem according to the corresponding handling suggestions. Related Alarm: 2560 Board CPU Overloaded 3. In the Alarm Management interface, check whether there is an alarm, indicating abnormal link at inter-shelf media plane. If yes, please solve the problem according to the corresponding handling suggestions. Related Alarm: 5121 Inter-shelf media plane link fault 4. Replace the board. 5. Change a slot to insert the board. 6. Replace the UIM of the same shelf. 198005399 DSP resource is unavailable Alarm Property Probable Cause � Alarm Code:198005399 � Severity:Major � � Description:DSP resource is unavailable Alarm Type:Equipment Alarm 1. This alarm indicates DSP resource is not available. It is monitored by higher-level layer. Once DSP is blocked, an alarm is given. This includes the following situations: 1. DSP version fails to be loaded so that the system is unable to operate normally. 2. The HPI port on DSP is abnormal. 3. The DSP media plane communication is disconnected. Speciic Problem 4. DSP resets. 1. This alarm indicates DSP resource is not available. It is monitored by higher-level layer. Once DSP is blocked, an alarm is given. This includes the following situations: 1. DSP version fails to be loaded so that the system is unable to operate normally. 2. The HPI port on DSP is abnormal. 3. The DSP media plane communication is disconnected. Conidential and Proprietary Information of ZTE CORPORATION 29 ZXG10 iBSC Alarm Handling Reference System Impact Handling Suggestion 4. DSP resets. All services processed by this DSP are interrupted, and those services will be re-created on other normal DSPs. If the DSP is unavailable for a long time, system performance will be degraded. 1. In network management system, check the operation & maintenance log ile. Is there a record, indicating DSP version replacing? If yes, this operation must cause DSP to reset. And having this alarm is a normal phenomenon. No handling is required. Please wait until DSP reset is complete. 2. Alarm details are displayed in NMS Alarm Management interface, where DSP index is given. Click System Rack Architecture. Right click the concerned board > Display Attributes > Subunit Coniguration. Then select the fault DSP and click Subunit Coniguration > Status Attribute> Query Status to view status. Is the Status of DSP Blocked? If it is Blocked, it means DSP is blocked manually. And this alarm is a normal phenomenon. In this case, click System Rack Architecture. Right click the concerned board and choose Subunit. Perform unblock DSP operation. After the operation, DSP restores to normal. 3. In Alarm Management interface, check whether there is one of the following alarms. If yes, please solve the problem according to corresponding handling suggestions. Related Alarms: 5701 Version Load Error 5655 DSP auto-detection abnormal 5700 DSP abnormally resets 4. Reset the board. 5. Replace the board. 198005403 Board SRAM self-check fails Alarm Property Alarm Code:198005403 � Severity:Major � � Description:Board SRAM self-check fails Alarm Type:Equipment Alarm Probable Cause Hardware fault of board. System Impact Board operation might be abnormal. Speciic Problem 30 � Hardware fault of board. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Handling Suggestion Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion Replace the board, and check whether this alarm disappears. 198005404 Board OCXO oven fault � Alarm Code:198005404 � Severity:Major � � Description:Board OCXO oven fault Alarm Type:Equipment Alarm Hardware fault of board. Hardware fault of board. Board operation might be abnormal. Replace the board, and check whether this alarm disappears. 198005405 Clock board phase-lock loop work mode abnormal � Alarm Code:198005405 � Severity:Major � � Description:Clock board phase-lock loop work mode abnormal Alarm Type:Equipment Alarm 1. There is no available reference source. 2. The clock distribution line is incorrect or there exists self loop. 3. The secondary clock locks the tertiary clock. 1. There is no available reference source. 2. The clock distribution line is incorrect or there exists self loop. 3. The secondary clock locks the tertiary clock. The designated reference clock cannot be phase-locked. 1. Check if the corresponding clock reference is correctly inputted. 2. Replace the board. Conidential and Proprietary Information of ZTE CORPORATION 31 ZXG10 iBSC Alarm Handling Reference 198005632 Hard disk usage rate exceeds threshold. Alarm Property � Alarm Code:198005632 � Severity:Major � � Description:Hard disk usage rate exceeds threshold. Alarm Type:Equipment Alarm Probable Cause 1. The conigured usage rate threshold is unreasonable. Speciic Problem 1. The conigured usage rate threshold is unreasonable. System Impact Handling Suggestion 2. The usage rate of hard disk is over high. 2. The usage rate of hard disk is over high. When hard disk usage rate exceeds its threshold, new data can not be written. The data may be lost. There is no impact on services. 1. In NMS Coniguration Management interface, click MPX86 or MPX86/2 Alarm Parameters > Hard Disk Full Alarm to check the threshold used to report a hard disk usage alarm. If the threshold value is low, please increase it. 2. Clean the space of hard disk. Delete the iles that are no longer used, or move them to external storage devices. 198005633 OMP hard disk is faulty Alarm Property Probable Cause Speciic Problem System Impact � Alarm Code:198005633 � Severity:Major � � Description:OMP hard disk is faulty Alarm Type:Equipment Alarm The ribbon cable is loose or the hard disk fails, usually a hardware failure. The ribbon cable is loose or the hard disk fails, usually a hardware failure. 1. This is an OMP alarm caused by hard disk breakage, which will affect the system in three ways: 1. The OMP can not boot and services can not access the board. 2. If the log server is abnormal, performance data temporarily stored in the hard disk of the OMP will be lost. Handling Suggestion 32 3. No peripheral board can be powered on because when a peripheral board boots, it will request for a version from the OMP. Replace the fault hard disk or replace the board, where the hard disk is installed. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198005635 The board is not plugged firmly Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198005635 � Severity:Major � � Description:The board is not plugged irmly Alarm Type:Equipment Alarm 1. The ENUM switch on the board is open, or in poor contact. 2. The EXCH button on the standby board is pressed twice within 3 seconds. 1. The ENUM switch on the board is open, or in poor contact. 2. The EXCH button on the standby board is pressed twice within 3 seconds. The active/standby board changeover or the APS changeover will fail. This board can not be switched to the active board. 1. Check whether the ENUM switch is closed. If not, close it. 2. Open and close the ENUM switch. 3. If the ENUM open status is simulated by pressing the EXCH key on the standby board twice within 3 seconds, press the EXCH key on the standby board twice within 3 seconds. 198005636 SMBUS error Alarm Property Probable Cause Speciic Problem System Impact � Alarm Code:198005636 � Severity:Major � � Description:SMBUS error Alarm Type:Equipment Alarm If the board is reset when the read-write time sequences of the SMBUS equipment are not inished, 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). If the board is reset when the read-write time sequences of the SMBUS equipment are not inished, 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). 1. In the case of SMBUS error, MPX86 board can be startup via coniguring BIOS. However, normal temperature check is impossible for the MPX86 board with SMBUS error. Therefore, the board might be running with high temperature without being known. 2. For the board with SMBUS error, memory size is conigured by default. Therefore, the conigured memory size might differ from the actual memory size. Conidential and Proprietary Information of ZTE CORPORATION 33 ZXG10 iBSC Alarm Handling Reference Handling Suggestion 1. ull out and plug the board, and check if the alarm is eliminated. Y->The alarm is eliminated. End alarm handling. N->Replace the board and end alarm handling. 198005637 Back card does not match with front board Alarm Property � Alarm Code:198005637 � Severity:Minor � � Description:Back card does not match with front board Alarm Type:Equipment Alarm Probable Cause 1. Incorrect rear board is used. Speciic Problem 1. Incorrect rear board is used. System Impact 2. Rear board failure. 2. Rear board failure. 1. When the rear board interface is used to connect other network element, it will cause link interruption at bottom layer, and services over the corresponding link will be interrupted. 2. When the rear board interface is used to connect internal control plane, it will cause communication error at internal control plane. As a result, the board can not exchange control plane messages and services borne on the board will be interrupted. Handling Suggestion 3. When the rear board interface of clock board is used to extract clock, it will cause loss of clock signal. Because without input clock, the system services will be interrupted. 1. Check the front board type for the correct rear board type, and use the correct rear board. 2. Replace the defective rear board with a new rear board. 198005638 LVDS signal unlocked Alarm Property Probable Cause Speciic Problem 34 � Alarm Code:198005638 � Severity:Major � � Description:LVDS signal unlocked Alarm Type:Equipment Alarm LVDS signal at the bottom layer is unlocked. LVDS signal at the bottom layer is unlocked. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm System Impact Handling Suggestion CS domain service of the resource shelves connected with the optical interface on TFI is down, HW loop back of the board in service fails. In the case of TSNB board fault, all circuit switch might fail. Switch or pull out and plug the board, and then check if the alarm is eliminated. Y->The alarm is eliminated. End alarm handling. N->Please contact ZTE Corporation. 198005639 High Error Rate of Optical Interface Alarm Property Probable Cause � Alarm Code:198005639 � Severity:Major � � Description:High Error Rate of Optical Interface Alarm Type:Equipment Alarm 1. The iber is not completed connected to the port, or is damaged, or is not compatible with the optical transceiver module in T-network switch. There is no light signal input into the optics module. This alarm is dedicated to the TDM optical port only. The possible causes of this alarm include: 1. TDM receiver iber optics failure, iber optics module failure. This type of failures include: damaged iber on the receiver, unconnected iber, contaminated iber or damaged optics module on the receiver. 2. Fiber optics failure at the transmitting module on the corresponding TDM. This type of failures include: damaged iber on the transmitter, unconnected iber, and contaminated iber. 3. Compatibility between iber optics and optics module. The iber transmission rate of TDM signal is incompatible with the wave length of the optics module. Speciic Problem 4. Loss of signal (LOS) alarm operation is performed on the corresponding SDH device. This includes the manual diagnosis test alarm operation. 1. The iber is not completed connected to the port, or is damaged, or is not compatible with the optical transceiver module in T-network switch. There is no light signal input into the optics module. This alarm is dedicated to the TDM optical port only. The possible causes of this alarm include: 1. TDM receiver iber optics failure, iber optics module failure. This type of failures include: damaged iber on the receiver, unconnected iber, contaminated iber or damaged optics module on the receiver. 2. Fiber optics failure at the transmitting module on the corresponding TDM. This type of failures include: damaged iber on the transmitter, unconnected iber, and contaminated iber. 3. Compatibility between iber optics and optics module. The iber transmission rate of TDM signal is incompatible with the wave length of the optics module. Conidential and Proprietary Information of ZTE CORPORATION 35 ZXG10 iBSC Alarm Handling Reference System Impact Handling Suggestion 4. Loss of signal (LOS) alarm operation is performed on the corresponding SDH device. This includes the manual diagnosis test alarm operation. There might be error in the data transmitted by the optical port which affects the quality of all the services performed on this optical port. 1. Perform loopback test to determine source of this alarm is on the local devices or the corresponding devices. Perform selfloop test on local device. If the failure persists, the failure source is on local device; if the failure disappears after self-loop test, then the source of failure is on the corresponding device. Contact the corresponding device for solution. 2. Replace optics module. 3. Replace the ibber optics. 4. Replace the board. 198005640 FPGA exception Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198005640 � Severity:Major � � Description:FPGA exception Alarm Type:Equipment Alarm FPGA runs abnormally, for example, FPGA is lost, or the board clock is lost. FPGA runs abnormally, for example, FPGA is lost, or the board clock is lost. The FPGA veriication will fail. The FPGA can not provide normal reading and writing functions. The board can not work normally or provide all of its functions. Services borne on the board will be interrupted. 1. Restart the board. In this case, the board downloads FPGA again. 2. Replace the board. 198005641 Port Link Down Alarm Property Probable Cause 36 � Alarm Code:198005641 � Severity:Major � � Description:Port Link Down Alarm Type:Equipment Alarm There is something wrong with the lan91 chip or BCM532x chip or M88E6095 chip. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Speciic Problem System Impact Handling Suggestion There is something wrong with the lan91 chip or BCM532x chip or M88E6095 chip. DSP is abnormal and call loss increases. 1. Reset the corresponding DSP chip or the board by using MML command on the background and then check the alarm is eliminated. 2. Replace the board. 198005643 Phase-lock loop work mode abnormal Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198005643 � Severity:Minor � � Description:Phase-lock loop work mode abnormal Alarm Type:Equipment Alarm 1. There is no available reference source. 2. The clock distribution line is incorrect or there exists self loop. 3. The secondary clock locks the tertiary clock. 1. There is no available reference source. 2. The clock distribution line is incorrect or there exists self loop. 3. The secondary clock locks the tertiary clock. The designated reference clock cannot be phase-locked. 1. Check if the corresponding clock reference is correctly inputted. Y->Replace the board and go to "2". N->Correctly input the clock reference and go to "2". 2. Check if the alarm is eliminated. Y->End. N->Please contact ZTE Corporation. 198005644 The channel in a sub card is down Alarm Property � Alarm Code:198005644 � Severity:Major � Description:The channel in a sub card is down Conidential and Proprietary Information of ZTE CORPORATION 37 ZXG10 iBSC Alarm Handling Reference � Alarm Type:Equipment Alarm Probable Cause 1. The sub-card is not inserted in position. Speciic Problem 1. The sub-card is not inserted in position. System Impact Handling Suggestion 2. The sub-card has hardware faults. 2. The sub-card has hardware faults. The sub-card channel is not initialized or the initialization fails. As a result, the channel corresponding to the alarm chip cannot be used normally. This affects the service carried by the board of the sub-card. After the channel is available and the alarm is eliminated, the service is recovered. 1. Unplug and plug the sub-card again. Wait for the board to be powered on. 2. Replace the sub-card. 198005645 Sub card abnormal Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198005645 � Severity:Minor � � Description:Sub card abnormal Alarm Type:Equipment Alarm 1. The GCS, EC or HPS subcard of UIMC/GUIM/CHUB is not inserted in position. 2. The subcard is faulty. 1. The GCS, EC or HPS subcard of UIMC/GUIM/CHUB is not inserted in position. 2. The subcard is faulty. 1. UIMC/GUIM/CHUB GCS sub-card functions abnormally. Packets may be lost, and even worse, link disconnection may occur on the control planes of some boards. For active/standby coniguration, there are two cases: 1. If the active board is abnormal while the standby board is normal, the system performs active/standby switchover. Thus, the standby board takes over the services of the faulty active board. In this case, the service is not affected. 2. If both the active and standby boards are abnormal, active/standby switchover is forbidden. In this case, the service is interrupted because the faulty board cannot restore to the normal status. 1. Check the sub-card connection on the board. If the sub-card is loosely inserted, tightly insert it and wait for the board to be powered on. 2. Replace the sub-card. 38 Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198005646 Phase-lock loop unlocked Alarm Property Probable Cause � Alarm Code:198005646 � Severity:Critical � � Description:Phase-lock loop unlocked Alarm Type:Equipment Alarm 1. Clock board faulty. 2. Reference clock has changed to another optical board. 3. Reference clock changed when a board has been removed or plugged in to the shelf. Speciic Problem 4. UIMC/GUIM input is disconnected, or UIMC/GUIM clock phase loop is abnormal. 1. Clock board faulty. 2. Reference clock has changed to another optical board. 3. Reference clock changed when a board has been removed or plugged in to the shelf. System Impact Handling Suggestion 4. UIMC/GUIM input is disconnected, or UIMC/GUIM clock phase loop is abnormal. The service clock and system clock are inconsistent on the board with unlocked phase-lock loop. As a result, the service carried by the board is interrupted. 1. Check whether there is the following clock alarm on the NMS Alarm Management interface. If yes, handle it according to the corresponding suggestions. 5381 Input Clock Abnormal 2. Check whether there is any of the following alarms about the clock extracting optical port on the NMS Alarm Management interface. If yes, handle it according to the corresponding suggestions. 1792 SDH/SONET fault 1824 Abnormal status in SDH/SONET 5639 High Error Rate of Optical Interface 2 Signal Loss of Optical Module 3. Check the operation and maintenance log in the NMS to see if there is a record about the change of the loop clock extraction reference. If yes, no handling is required. 4. Conduct an active/standby changeover to the clock board. 5. Conduct an active/standby changeover to the UIM/GUIM board. 6. Replace the board. Conidential and Proprietary Information of ZTE CORPORATION 39 ZXG10 iBSC Alarm Handling Reference 198005647 High BER on E1 link Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198005647 � Severity:Major � � Description:High BER on E1 link Alarm Type:Equipment Alarm 1. The E1/T1 link is faulty. 2. The device in the uplink direction of the trunk link is faulty. 3. The trunk cable or connector is in poor contact. 1. The E1/T1 link is faulty. 2. The device in the uplink direction of the trunk link is faulty. 3. The trunk cable or connector is in poor contact. The trunk fails to receive trunk signals. If the belonged port has only this link, all services on the port are interrupted. Otherwise, only the port bandwidth is affected. The quantity of upper layer access services associated with the port is decreased. The accessed bandwidth is reduced. The service, however, is not interrupted. 1. Conduct a meter measurement or loopback test to ind out whether the alarm is rooted in the local end or peer end. Meter measurement: Connect a trunk test meter to check if the signal received by the local end trunk is normal. If yes, the fault is rooted in the local end. If the test shows the problem persists, the fault is rooted in the peer end. In this case, inform the peer end to troubleshoot. Loopback test: Perform self-loop at the trunk where alarm occurs at local end. If the problem persists, it indicates that the fault is rooted in the local end. If the alarm is eliminated, it indicates that the alarm is rooted in the peer end. In this case, inform the peer end to troubleshoot. 2. Replace the trunk cable. 3. Replace the board. 198005648 Control plane port of backboard joining switching chip is exceptional Alarm Property � Alarm Code:198005648 � Severity:Major � � 40 Description:Control plane port of backboard joining switching chip is exceptional Alarm Type:Equipment Alarm Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Probable Cause Speciic Problem System Impact Handling Suggestion The control plane ports of such boards as SPB/SPB_2/SDU are down or do not send and receive packets for more than 5 minutes. The control plane ports of such boards as SPB/SPB_2/SDU are down or do not send and receive packets for more than 5 minutes. Connection between the switch chip and the backplane's control network is down. 1. heck the corresponding port status on UIM after fault diagnosis. Y->Reset or pull out and plug the board and then end alarm handling. N->Reset UIM and end alarm handling. 198005655 Errors detected in DSP Alarm Property � Alarm Code:198005655 � Severity:Major � � Description:Errors detected in DSP Alarm Type:Equipment Alarm Probable Cause 1. The HPI port fails Speciic Problem 1. The HPI port fails System Impact Handling Suggestion 2. Hardware failure. 2. Hardware failure. This DSP will be blocked and no longer available. The cell of this DSP is out of service; the subscriber using this DSP is out of service; call loss rate might increase when call trafic is high. 1. Reset the board. 2. Replace DSP sub-card. 3. Replace the board. 198005656 Input clock of subcard lost Alarm Property Probable Cause � Alarm Code:198005656 � Severity:Major � � Description:Input clock of subcard lost Alarm Type:Equipment Alarm 1. The subcard is loose. Conidential and Proprietary Information of ZTE CORPORATION 41 ZXG10 iBSC Alarm Handling Reference 2. The clock circuit of the subcard is damaged. Speciic Problem System Impact Handling Suggestion 3. The clock circuit of the mother board is damaged. 1. The subcard is loose. 2. The clock circuit of the subcard is damaged. 3. The clock circuit of the mother board is damaged. The unavailable sub-card clock affects the normal operation of the board. This may cause clock jittering, and the service that implements media stream exchange through this board becomes unstable. In the most serious case, the system clock is lost and the service carried by the board is interrupted. 1. Check the subcard connection status. If the subcard is loose, tightly connect it and power it on again. 2. Replace the subcard 3. Replace the board. 198005657 Error of LVDS path frame detection Alarm Property � Alarm Code:198005657 � Severity:Major � � Description:Error of LVDS path frame detection Alarm Type:Equipment Alarm Probable Cause Error occurs in LVDS path frame detection System Impact The board might not work normally. Speciic Problem Handling Suggestion Error occurs in LVDS path frame detection 1. Check if the TFI optical iber corresponding to this path is connected in position or is damaged. 2. Connect the iber in place or replace it with anther one, and check if the alarm is eliminated. 3. Check if the iber matches the optical transceiver module. 4. Replace the iber, and check if the alarm is eliminated. 5. Switch T network board. 42 Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198005658 Failure in diagnosing link loop back of large T network Alarm Property � Alarm Code:198005658 � Severity:Major � � Description:Failure in diagnosing link loop back of large T network Alarm Type:Equipment Alarm Probable Cause The 129th time slot loop back of LVDS has a failure. System Impact The board does not work normally. Speciic Problem Handling Suggestion The 129th time slot loop back of LVDS has a failure. 1. Check if the TFI optical iber corresponding to this path is connected in position or is damaged. 2. Connect the iber in place or replace it with anther one, and check if the alarm is eliminated. 3. Check if the iber matches the optical transceiver module. 4. Replace the iber, and check if the alarm is eliminated. 5. Switch T network board. 198005660 Physical link down between master port and slave port Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198005660 � Severity:Warning � � Description:Physical link down between master port and slave port Alarm Type:Equipment Alarm The running physical link between the master and the slave port is broken. The running physical link between the master and the slave port is broken. APS function disabled 1. Change another slot and check whether the alarm disappears. Y->End. N->Go to Step Conidential and Proprietary Information of ZTE CORPORATION 43 ZXG10 iBSC Alarm Handling Reference 2. Change the board and check whether the alarm disappears. Y->End. N->Contact ZTE Corporation. 198005661 Physical link down between media interface ports Alarm Property � Alarm Code:198005661 � Severity:Warning � � Description:Physical link down between media interface ports Alarm Type:Equipment Alarm Probable Cause The network port or board is faulty. System Impact The APS optical port data on the standby board cannot reach the active board. When the active optical port is normal, the service is not affected. When the active optical port is faulty, APS fails to protect optical port and thus all services carried by the optical port are interrupted. Speciic Problem Handling Suggestion The network port or board is faulty. 1. Replace the board. 2. Replace the other board, that is, the board rather than the faulty board in active/standby coniguration. 3. Replace the slot. Use the slot that supports GE channel between boards. . 198005662 IDE running overtime Alarm Property Alarm Code:198005662 � Severity:Warning � � Description:IDE running overtime Alarm Type:Equipment Alarm Probable Cause IDE is operated for longer time. System Impact When hard disk work for long time without sleep, engine will be in high speed spin state for long, this will inluence the life of disk, and data will lose when disk be abnormal. Disk of some model Speciic Problem 44 � IDE is operated for longer time. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Handling Suggestion will lock the engine when it keep work for long time to protect the disk. But this is out of the software controled, and may result in data lose when disk cannot be accessed transitorily. No handling is necessary. 198005663 Component fault Alarm Property � Alarm Code:198005663 � Severity:Major � � Description:Component fault Alarm Type:Equipment Alarm Probable Cause Devices or sub-cards on the board operate abnormally. System Impact This alarm only occurs to the IMAB. When it occurs, the IMAB can not operate normally and the trunk borne on the board will be broken. As a result, users can not access the board and the existing services will be interrupted. Speciic Problem Handling Suggestion Devices or sub-cards on the board operate abnormally. Replace the board. 198005665 Fault on board (GPS) Alarm Property Probable Cause Speciic Problem � Alarm Code:198005665 � Severity:Critical � � Description:Fault on board (GPS) Alarm Type:Equipment Alarm 1. According to alarm details, alarm status falls into two types: Type A fault on board (GPS) phase-lock equipment Phase-lock equipment of this board (GPS) is in power on status The causes for the two alarm types are described below. 1. Type A fault on board (GPS) phase-lock equipment Probable alarm causes include 16chip loss/out of lock, 1 2. M loss/out of lock, PP2S output loss, 8K output loss, 10M output loss, and 1PPS loss. 2. Phase-lock equipment of this board (GPS) is in power on status The alarm cause is that the GPS module of ICM board is in power on status, and power on has not been completed. 1. According to alarm details, alarm status falls into two types: Type A fault on board (GPS) phase-lock equipment Phase-lock equipment of this board (GPS) is in power on status The causes for the two alarm types are described below. 1. Type A fault Conidential and Proprietary Information of ZTE CORPORATION 45 ZXG10 iBSC Alarm Handling Reference on board (GPS) phase-lock equipment Probable alarm causes include 16chip loss/out of lock, 1 System Impact Handling Suggestion 2. M loss/out of lock, PP2S output loss, 8K output loss, 10M output loss, and 1PPS loss. 2. Phase-lock equipment of this board (GPS) is in power on status The alarm cause is that the GPS module of ICM board is in power on status, and power on has not been completed. 1. Be usually determined as hardware fault, which affects system clock. It might lead to the system clock loss and system synchronization failure. When system clock loss/offset occurs, its subsequent impact on service is described below. 1.For TDM transmission, all links based on the TDM transmission medium (including the transmission link currently in service for UE and cell transmission link) are affected. Packet loss might occur on these links, leading to degradation of service quality. In the case of serious packet loss, service interruption and handover failure will occur. Even worse, the cell might be out of service. 2. For non-TDM transmission (for example, IP transmission), Iub interface service is affected, while Iur interface and Iu interface services are not affected. The clock that Node B derives from RNC via IEEE1588 is inaccurate. When RNC clock frequency offset is no more than 0.05 ppm, Node B synchronization will not fail, but success rate of inter-RNC inter-Node B soft handover might fall. When RNC clock frequency offset exceeds 0.5 ppm, Node B will fail to lock the clock. In this case, Node B will oscillate freely and success rate of inter-Node B soft handover might fall. 1. On NMS fault management interface, view alarm Details where Error type information is given. Locate the corresponding alarm handling suggestion according to the error type. The alarm handling suggestions that correspond to the error types are described below. 1.Type A Fault on Board (GPS) Phase-lock Equipment 1) On NMS test management interface, perform diagnostic test on ICM board. Check the working status of the GPS module. If Class A fault persists in the GPS module, replace the board. 2) Check if output clock loss occurs. If yes, replace the board. 2. Phase-lock Equipment of This Board (GPS) Is in Power-on Status If the alarm persists, hardware fault might exist. Replace the board. 198005667 E1 is looped back Alarm Property Probable Cause 46 � Alarm Code:198005667 � Severity:Minor � � Description:E1 is looped back Alarm Type:Equipment Alarm 1. User has set loop back. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 2. Transmission is looped back by provider. 3. Local board is faulty. 4. Remote board is faulty. Speciic Problem 5. Loop back applied on DDF. 1. User has set loop back. 2. Transmission is looped back by provider. 3. Local board is faulty. 4. Remote board is faulty. System Impact Handling Suggestion 5. Loop back applied on DDF. 1. ata can not be sent out because of the loopback E1. 1. Disconnect the loopback E1. 2. Restart the board. 3. Replace the board. 4. Replace the opposite board. 198005668 Cross-linked E1 alarm Alarm Property � Alarm Code:198005668 � Severity:Minor � � Description:Cross-linked E1 alarm Alarm Type:Equipment Alarm Probable Cause 1. elf board has cross-linked E1. System Impact 1. ata can not be sent out because of cross-linked E1. Speciic Problem Handling Suggestion 1. elf board has cross-linked E1. 1. Disconnect the cross-linked E1, Wait for 1 minute and check whether the alarm disappears. 2. Restart the board and check whether the alarm disappears. 3. Replace the board by another one and check whether the alarm disappears. 4. Replace the board connected with this board, check whether the alarm disappears. Conidential and Proprietary Information of ZTE CORPORATION 47 ZXG10 iBSC Alarm Handling Reference 198005669 Synchronization status check of FPGA failed Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion Alarm Property Probable Cause Speciic Problem System Impact 48 � Alarm Code:198005669 � Severity:Critical � � Description:Synchronization status check of FPGA failed Alarm Type:Equipment Alarm Synchronization status check of FPGA and SPI4/VSC872/VSC874 failed. It's usually caused by hardware exceptions. For example, the clock chip works abnormally. Synchronization status check of FPGA and SPI4/VSC872/VSC874 failed. It's usually caused by hardware exceptions. For example, the clock chip works abnormally. If synchronization status check of FPGA fail, Media can not receive or send data normally. And the board will reset for the exception of the media check frame. Replace the board. 198005671 Sending or receiving packets using the cascade ports inner board failed � Alarm Code:198005671 � Severity:Critical � � Description:Sending or receiving packets using the cascade ports inner board failed Alarm Type:Equipment Alarm 1. The subcard GCS of UIM2 is not inserted in position. 2. The subcard GCS of UIM2 has hardware faults. 3. The UIM2/CHUB/GUIM board has hardware faults. 1. The subcard GCS of UIM2 is not inserted in position. 2. The subcard GCS of UIM2 has hardware faults. 3. The UIM2/CHUB/GUIM board has hardware faults. 1. Cascade ports inner UIMC/GUIM/CHUB functions abnormally. Packets may be lost, and even worse, link disconnection may occur on the control planes of some boards. For active/standby coniguration, there are two cases: 1. If the active board is abnormal while the standby board is normal, the system performs Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm active/standby switchover. Thus, the standby board takes over the services of the faulty active board. In this case, the service is not affected. Handling Suggestion 2. If both the active and standby boards are abnormal, active/standby switchover is forbidden. In this case, the service is interrupted because the faulty board cannot restore to the normal status. 1. Check the GCS subcard connection on the board. If the subcard is loosely inserted, tightly insert it and wait for the board to be powered on. 2. Replace the GCS subcard. 3. Replace the UIM2/GUIM/CHUB board. 198005893 Memory check failed Alarm Property � Alarm Code:198005893 � Severity:Critical � � Description:Memory check failed Alarm Type:Equipment Alarm Probable Cause Memory check failed. System Impact The operation related to the memory maybe failed. Speciic Problem Handling Suggestion Memory check failed. 1. Make records of the alarm information. 2. Replace the board or subcard. 198006400 Cx29704 runs abnormally Alarm Property Probable Cause Speciic Problem � Alarm Code:198006400 � Severity:Minor � � Description:Cx29704 runs abnormally Alarm Type:Equipment Alarm It is the chip fault. If it 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. It is the chip fault. If it 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. Conidential and Proprietary Information of ZTE CORPORATION 49 ZXG10 iBSC Alarm Handling Reference System Impact Handling Suggestion The board does not work normally. It is the chip fault. Please contact ZTE Corporation to replace the board. 198015874 Data traffic to PSN board is congested Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198015874 � Severity:Major � � Description:Data trafic to PSN board is congested Alarm Type:Equipment Alarm 1. The trafic low to the board is excessive. 2. The PSN board in the same shelf is abnormal. 3. The board has hardware faults. 1. The trafic low to the board is excessive. 2. The PSN board in the same shelf is abnormal. 3. The board has hardware faults. The services carried by the board are unstable. In most serious case, all services carried by the board are interrupted. 1. On NMS fault management interface, check if the PSN in the same shelf has generated related alarms. If yes, follow the suggestions on handling the related alarms. The related alarm is as follows: 19456 All high-speed links between line card and package switching board are out of synchronism 2. Unplug and plug the board. 3. Replace the board. 198015875 GLI table lookup failed Alarm Property Probable Cause 50 � Alarm Code:198015875 � Severity:Minor � � Description:GLI table lookup failed Alarm Type:Equipment Alarm 1. L1 table or L2 table error. 2. Destination IP of packets or hardware is error. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Speciic Problem System Impact Handling Suggestion Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion 1. L1 table or L2 table error. 2. Destination IP of packets or hardware is error. Packets would be dropped which would cause poor voice quality and other problems. Switch the master port to the partner board. 198015876 GLI exception packets statistic over threshold � Alarm Code:198015876 � Severity:Minor � � Description:GLI exception packets statistic over threshold Alarm Type:Equipment Alarm 1. Connection between iber and optic modules is not perfect. 2. Something wrong with iber optic module. 3. Board hardware error. 1. Connection between iber and optic modules is not perfect. 2. Something wrong with iber optic module. 3. Board hardware error. Packets would be dropped which would cause poor voice quality and other problems. 1. Check the connection between iber and optic modules. 2. Reboot the board. 198015877 GLIQV SRAM/DRAM error Alarm Property Probable Cause � Alarm Code:198015877 � Severity:Minor � � Description:GLIQV SRAM/DRAM error Alarm Type:Equipment Alarm 1. SRAM of GLIQV is error. 2. DRAM of GLIQV is error. 3. Micro engine of GLIQV is error. Conidential and Proprietary Information of ZTE CORPORATION 51 ZXG10 iBSC Alarm Handling Reference Speciic Problem System Impact Handling Suggestion 1. SRAM of GLIQV is error. 2. DRAM of GLIQV is error. 3. Micro engine of GLIQV is error. Packets would be dropped which would cause poor voice quality and other problems. 1. Reboot the board. 2. Change the master port to slave port. 3. Replace the board with a new board. 198019456 All high-speed links between line card and switching boards are out of synchronization Alarm Property � Alarm Code:198019456 � Severity:Critical � � Description:All high-speed links between line card and switching boards are out of synchronization Alarm Type:Equipment Alarm Probable Cause 1. Switching board hardware is abnormal. Speciic Problem 1. Switching board hardware is abnormal. System Impact 2. Line card hardware is faulty. 2. Line card hardware is faulty. 1. All services on the equipment are down if the alarm is caused by Cause 1 or Cause 2. All services on the line card are affected if the alarm is caused by Cause Handling Suggestion 52 3. If the service is not conigured in master/slave or load sharing mode, all services on the line card will be down. If the service is conigured in master/slave or load sharing mode, all services on the line card will soon be restored after being down temporarily. 1. Check whether PSN board reboots repeatedly. If yes, Check whether the PSN board type conigured is consistent with the PSN board type actually in use. If inconsistent (for example, the conigured board type is PSN4V and the board type actually in use is PSN8V), modify board type coniguration or replace the board actually in use to keep consistency between board coniguration and the board in use. If consistent, PSN board hardware might be faulty. In this case, replace PSN board. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 2. If the alarm occurs in line card, check if the same alarm occurs in other line card(s) located in the same shelf with the faulty line card. If the same alarm occurs in all other line cards, PSN board might be faulty. Reboot PSN board and check if the line card alarms are restored. If alarms are not restored, replace PSN board. If merely the line card where this alarm occurs reboots repeatedly, replace the board where the alarm is generated. 198019465 CSIX RX and TX packets is abnormal Alarm Property � Alarm Code:198019465 � Severity:Warning � � Description:CSIX RX and TX packets is abnormal Alarm Type:Equipment Alarm Probable Cause 1. Signal is unstable when rack or board is powering on. Speciic Problem 1. Signal is unstable when rack or board is powering on. System Impact Handling Suggestion 2. Switch chip is abnormal. 2. Switch chip is abnormal. The transceiver of the media plane is exceptional. 1. Reset the board. 2. Replace the board. 198019712 APS channel mismatched Alarm Property Probable Cause � Alarm Code:198019712 � Severity:Major � � Description:APS channel mismatched Alarm Type:Equipment Alarm 1. Fiber connection is wrong. 2. APS backup mode is conigured differently between local end and opposite end. 3. APS protection mode is conigured differently between local end and opposite end. Speciic Problem 4. The opposite equipment is faulty. 1. Fiber connection is wrong. Conidential and Proprietary Information of ZTE CORPORATION 53 ZXG10 iBSC Alarm Handling Reference 2. APS backup mode is conigured differently between local end and opposite end. 3. APS protection mode is conigured differently between local end and opposite end. System Impact Handling Suggestion 4. The opposite equipment is faulty. APS automatic protection switching function is paralyzed. When the working optical port is abnormal, the protection optical port will not work, leading to service interruption on this optical port. 1. Check ibber connection. Check ibber connection at both ends. Ensure that the work optical ports at both ends are interconnected, and the protection optical ports at both ends are interconnected. On NMS coniguration management interface, locate the relevant board in the rack. Right-Click the board and open board properties page. Click Optical port APS protection to view the "Work optical port" and "Protection optical port" conigured at local end. 2. Check APS backup mode coniguration at both ends. Check APS backup mode (1 1 or 1:1) at local end to ensure coniguration consistency at both ends. On NMS coniguration management interface, locate the relevant board in the rack. Right-Click the board and open board properties page. Click Optical port APS protection in the shortcut menu to view the "Protection Type" (1+1 or 1:1). 3. Check APS protection direction at both ends. Check APS protection direction (unidirectional or bidirectional) conigured at local end. Ensure coniguration consistency at both ends. On NMS coniguration management interface, locate the relevant board in the rack. Right-Click the board and open board properties page. Click Optical port APS protection to view the "Protection Direct" (unidirectional or bidirectional). 4. Check whether APS is supported by the opposite equipment. Check whether APS coniguration is correct and has taken effect. 198019713 APS mode mismatched Alarm Property Probable Cause Speciic Problem 54 � Alarm Code:198019713 � Severity:Major � � Description:APS mode mismatched Alarm Type:Equipment Alarm 1. Fiber connection is wrong. 2. APS backup mode is conigured differently between local end and opposite end. 3. APS protection mode is conigured differently between local end and opposite end. 1. Fiber connection is wrong. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 2. APS backup mode is conigured differently between local end and opposite end. System Impact Handling Suggestion 3. APS protection mode is conigured differently between local end and opposite end. 1. When ibber connection is correct and the working optical port can work normally, services won't be affected. 2. When the working optical port is faulty, APS automatic protection switching function doesn't work, and services carried via this optical port will be interrupted due to lack of protection. 1. Check ibber connection. Check ibber connection at both ends. Ensure that the work optical ports at both ends are interconnected, and the protection optical ports at both ends are interconnected. On NMS coniguration management interface, locate the relevant board in the rack. Right-Click the board and open board properties page. Click Optical port APS protection to view the "Work optical port" and "Protection optical port" conigured at local end. 2. Check APS backup mode coniguration at both ends. Check APS backup mode (1+1 or 1:1) at local end to ensure coniguration consistency at both ends. On NMS coniguration management interface, locate the relevant board in the rack. Right-Click the board and open board properties page. Click Optical port APS protection to view the "Protection Type" (1+1 or 1:1). 3. Check APS protection direction at both ends. Check APS protection direction (unidirectional or bidirectional) conigured at local end. Ensure coniguration consistency at both ends. On NMS coniguration management interface, locate the relevant board in the rack. Right-Click the board and open board properties page. Click Optical port APS protection to view the "Protection Direct" (unidirectional or bidirectional). 198019714 APS configuration alarm Alarm Property � Alarm Code:198019714 � Severity:Major � � Description:APS coniguration alarm Alarm Type:Equipment Alarm Probable Cause Optical interface are not conigured for APS in 1:1 mode. System Impact The board can not enter into normal working status. All board services fail to be established. Speciic Problem Handling Suggestion Optical interface are not conigured for APS in 1:1 mode. 1. If board backup mode is conigured as 1:1 or 1+1 and SDH optical interface is needed, at least one set of APS protection needs to be conigured. To conigure APS protection: On NMS coniguration management interface, locate the relevant board Conidential and Proprietary Information of ZTE CORPORATION 55 ZXG10 iBSC Alarm Handling Reference in the rack. Right-Click the board and open board properties page. Click Optical port APS protection. 2. If board master/slave mode is not needed, modify board backup mode into. To conigure board backup mode: Delete the relevant board on NMS coniguration management interface. Then recreate the board. Select board backup mode as "None" during board creation. 3. If board backup mode is conigured as 1:1 and no SDH optical interface is required, modify the board backup mode into 1+1. To conigure board backup mode: Delete the relevant board on NMS coniguration management interface. Then recreate the board. Select board backup mode as "1+1" during board creation. 198019715 MS APS channel gets errors Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198019715 � Severity:Major � � Description:MS APS channel gets errors Alarm Type:Equipment Alarm 1. APS Channel between Master and Slave Board gets hardware fault. 2. The connection on the backplane between the slot and the neighboring slot gets errors. 1. APS Channel between Master and Slave Board gets hardware fault. 2. The connection on the backplane between the slot and the neighboring slot gets errors. 1. ASP function is affected. 2. The board master/slave function is affected. 1. Reboot the board. 2. Replace the board. 3. Replace the neighboring board. 4. Replace the slots . 56 Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198019968 No response to request L2 Forwarding Table information from DBS. Alarm Property � Alarm Code:198019968 � Severity:Major � � Description:No response to request L2 Forwarding Table information from DBS. Alarm Type:Equipment Alarm Probable Cause 1. Omp is not powered on normally. Speciic Problem 1. Omp is not powered on normally. System Impact Handling Suggestion 2. Control plane messages are delayed. 2. Control plane messages are delayed. 1. If the alarm is reported by UIM, the media stream of the shelf where UIM is located is blocked. 2. If the alarm is reported by GSC, the media stream between shelves is blocked. 1. Restart OMP board to see if it works normally. Y->If so, go to "2". N->If not, go to "4". 2. Restart UIM/GSC board to see if it works normally. Y->If so, go to "3". N->If not, go to "4". 3. check if the alarm disappears. Y->If not, go to "4". N->If so, go to "5". 4. Record detailed information and contact ZTE Corporation. 5. Finish the alarm handling. 198019969 No response to request L2 Forwarding Table port information from SCS. Alarm Property � � Alarm Code:198019969 Description:No response to request L2 Forwarding Table port information from SCS. Conidential and Proprietary Information of ZTE CORPORATION 57 ZXG10 iBSC Alarm Handling Reference � Probable Cause Speciic Problem System Impact Handling Suggestion � Severity:Major Alarm Type:Equipment Alarm 1. System control process on UIM/GSC board is not powered on normally. 2. The number of IP addresses conigured for sub-units in one shelf is more than 200. 1. System control process on UIM/GSC board is not powered on normally. 2. The number of IP addresses conigured for sub-units in one shelf is more than 200. 1. If the alarm is reported by UIM, the media stream of the shelf where UIM is located is blocked. 2. If the alarm is reported by GSC, the media stream between shelves is blocked. 1. If the alarm is reported by UIM: 1.Restart UIM board to see if it works normally. Y->If so, go to "2". N->If not, go to "4". 2. Log in OAM background and enter into protocol mode to view IP coniguration of the port by using “show ip interface brief” command. Check if the number of IP addresses conigured for sub-units in one shelf is more than 200. Y->If so, go to "3". N->If not, go to "4". 3. Delete some IP addresses to make the number less than 200. Check if the alarm is still existing. Y->If so, go to "4". N->If not, go to "5". 4. Record detailed information and contact ZTE Corporation. 5. Finish the alarm handling. If the alarm is reported by GSC: 1.Check if the GSC board is in working state Y->If the GSC board is in working state,go to "2" N->If not,go to "5" 2.Check if the optical iber is connected correctly Y->If not,go to "3" N->If so,go to "4" 3.Check if the alarm still exists after connecting the optical iber correctly Y->If so,go to "4" N->If not,go to "6" 4.Restart GSC board to see if the alarm still exists Y->If so,go to "5" N->If not,go to "6" 5.Record detailed information and contact ZTE Corporation. 6. Finish the alarm handling. 58 Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198019970 Resource board can't get L2 Forwarding Table. Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198019970 � Severity:Major � � Description:Resource board can't get L2 Forwarding Table. Alarm Type:Equipment Alarm 1. The type of the shelf is not BUSN/BGSN. 2. UIM board on the shelf is not powered on normally. 3. Control plane messages are blocked. 1. The type of the shelf is not BUSN/BGSN. 2. UIM board on the shelf is not powered on normally. 3. Control plane messages are blocked. The resource board which has reported the alarm will be unable to forward media data. 1. Check if the resource shelf is BUSN/BGSN shelf and UIM board on the shelf is powered on normally. Y->If the shelf is not BUSN/BGSN shelf or UIM board is not powered on normally, go to "2". N->If the alarm disappears when the shelf is BUSN/BGSN shelf and UIM board is powered on normally, go to "4", otherwise, go to "3". 2. Replace resource shelf with BUSN/BGSN shelf and conigure the rack again, make sure that the UIM board is powered on normally. Check if the alarm disappears. Y->If not, go to "3". N->If so, go to "4". 3. Record detailed information and contact ZTE Corporation. 4. Finish the alarm handling. 198025601 TSNB internal connection chip fault Alarm Property � Alarm Code:198025601 � Severity:Major � � Description:TSNB internal connection chip fault Alarm Type:Equipment Alarm Conidential and Proprietary Information of ZTE CORPORATION 59 ZXG10 iBSC Alarm Handling Reference Probable Cause Speciic Problem System Impact Handling Suggestion Connection chip (73273/73260) faults on TDM Switch Network Board cause some 129 time slots of HW having connection faults. Connection chip (73273/73260) faults on TDM Switch Network Board cause some 129 time slots of HW having connection faults. If the fault occurs on master board, board state will be changed to slave; slave board will be reset immediately. 1. Try to replace the board and check if the alarm is eliminated. 2. Please contact ZTE Corporation. 198025602 TDM switch abnormal Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198025602 � Severity:Minor � � Description:TDM switch abnormal Alarm Type:Equipment Alarm 1. Check for any clock alarms. 2. TDM Switch chip is faulty 3. Wrong board in conigured slot. 1. Check for any clock alarms. 2. TDM Switch chip is faulty 3. Wrong board in conigured slot. The link with abnormal connection is interrupted. Accordingly, services are affected. 1. In NMS Coniguration Management interface, view the coniguration of IMA links. Do the values of HW and TS ields conigured for IMA links conlict (for example, two A ends are conigured with the same B end). If yes, modify the coniguration. 2. Replace the faulty board. 198026116 PP2S output clock lost Alarm Property Probable Cause 60 � Alarm Code:198026116 � Severity:Major � � Description:PP2S output clock lost Alarm Type:Equipment Alarm Hardware is faulty. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Speciic Problem System Impact Handling Suggestion Hardware is faulty. 1. If it is caused by the master clock board, the system will fail to get clock. Because of this, all clock-related boards can not work normally and services will be interrupted. The relevant boards include IMA protocol processing board and interface board with HW process capability. 2. If it is caused by the slave clock board, services will not be affected. 1. If the alarm is reported by master board rather than slave board, perform master/slave switching. 2. Replace the board where the alarm is reported. 198026117 PP2S clock reference lost Alarm Property � Alarm Code:198026117 � Severity:Major � � Description:PP2S clock reference lost Alarm Type:Equipment Alarm Probable Cause Hardware is faulty. System Impact The system can not get wanted clock, therefore all clock-related processes are abnormal. Speciic Problem Handling Suggestion Hardware is faulty. 1. If the board where the alarm is declared is ICM, please replace the board. 2. If the board where the alarm is declared is CLKG: Check the connection between CLKG and GCM. Replace the CLKG. Replace the GCM. 198026118 16CHIP clock reference lost Alarm Property Probable Cause Speciic Problem � Alarm Code:198026118 � Severity:Major � � Description:16CHIP clock reference lost Alarm Type:Equipment Alarm Hardware is faulty. Hardware is faulty. Conidential and Proprietary Information of ZTE CORPORATION 61 ZXG10 iBSC Alarm Handling Reference System Impact Handling Suggestion Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion The system can not get wanted clock, therefore all clock-related processes are abnormal. Replace the board. 198026127 Loss of Level 3 reference source clock � Alarm Code:198026127 � Severity:Minor � � Description: Loss of Level 3 reference source clock Alarm Type:Equipment Alarm 1. Input clock reference is in unavailable status for no more than 10 minutes. Probable causes include: 1. Clock reference input is abnormal. 2. The conigured clock reference does not exist. 1. Input clock reference is in unavailable status for no more than 10 minutes. Probable causes include: 1. Clock reference input is abnormal. 2. The conigured clock reference does not exist. When all conigured clock reference sources are lost, the clock board comes to free running or hold-over state. Accuracy of output clock is determined by the crystal oscillator of clock board. No impact on service. 1. Re-connect the input clock reference. 2. For the clock reference not in use, delete the corresponding “Circuitry Clock Reference” coniguration on NMS coniguration management interface (board property). 198026128 Loss of Level2 reference source clock Alarm Property Probable Cause � Alarm Code:198026128 � Severity:Major � � Description: Loss of Level2 reference source clock Alarm Type:Equipment Alarm 1. Input clock reference is in unavailable status for more than 10 minutes and less than 24 hours. Probable causes include: 1. Clock reference input is abnormal. 2. The conigured clock reference does not exist. 62 Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Speciic Problem System Impact Handling Suggestion 1. Input clock reference is in unavailable status for more than 10 minutes and less than 24 hours. Probable causes include: 1. Clock reference input is abnormal. 2. The conigured clock reference does not exist. When all conigured clock reference sources are lost, the clock board comes to free running or hold-over state. Accuracy of output clock is determined by the crystal oscillator of clock board. The clock loss leads to synchronization failure between system clock and clock reference source. Service interruption might occur. The system will not be affected if the following two events happen together. Input clock reference source is lost. The phase-locked loop locks other clock reference source. 1. Re-connect the input clock reference. 2. For the clock reference not in use, delete the corresponding “Circuitry Clock Reference” coniguration on NMS coniguration management interface (board property). 198026129 Loss of Level1 reference source clock Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198026129 � Severity:Critical � � Description:Loss of Level1 reference source clock Alarm Type:Equipment Alarm 1. Input clock reference is in unavailable status for more than 24 hours. Probable causes include: 1. Clock reference input is abnormal. 2. The conigured clock reference does not exist. 1. Input clock reference is in unavailable status for more than 24 hours. Probable causes include: 1. Clock reference input is abnormal. 2. The conigured clock reference does not exist. When all conigured clock reference sources are lost, the clock board comes to free running or hold-over state. Accuracy of output clock is determined by the crystal oscillator of clock board. The clock loss leads to synchronization failure between system clock and clock reference source. Service interruption will occur. The system will not be affected if the following two events happen together. Input clock reference source is lost. The phase-locked loop locks other clock reference source. 1. Re-connect the input clock reference. 2. For the clock reference not in use, delete the corresponding “Circuitry Clock Reference” coniguration on NMS coniguration management interface (board property). Conidential and Proprietary Information of ZTE CORPORATION 63 ZXG10 iBSC Alarm Handling Reference 198026131 CLKG board PLL is unlocked. Clock will drift Alarm Property � Alarm Code:198026131 � Severity:Minor � � Description:CLKG board PLL is unlocked. Clock will drift Alarm Type:Equipment Alarm Probable Cause Hardware fault of board System Impact System could not get the needed clock, which will cause processing abnormity related to the clock. Speciic Problem Handling Suggestion Hardware fault of board 1. If the alarm is reported by the master board, and the slave board is good, perform master/slave changeover operation. 2. Replace the fault board. 198026133 Output clock lost Alarm Property Alarm Code:198026133 � Severity:Major � � Description:Output clock lost Alarm Type:Equipment Alarm Probable Cause Hardware is faulty. System Impact 1. If this alarm occurs on the master board, system clock synchronization will fail and services will be interrupted. Speciic Problem Handling Suggestion 64 � Hardware is faulty. 2. If this alarm occurs on the slave board, services will not be affected. 1. If the alarm is declared by master board rather than slave board, perform master/slave switching. 2. Replace board. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198028672 80g chip abnormal Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198028672 � Severity:Critical � � Description:80g chip abnormal Alarm Type:Equipment Alarm 80g detects that the GLIQP board restarts, or the 80g chip is abnormal. 80g detects that the GLIQP board restarts, or the 80g chip is abnormal. Media plane messages are partially lost or unavailable. Restart the board for which the alarm is reported. Replace the board with a good one if the alarm still exists. Contact ZTE. if replacing the board does not work. 198029952 802.3ah link fault Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198029952 � Severity:Major � � Description:802.3ah link fault Alarm Type:Equipment Alarm Link Fault: The physical layer has determined a fault that occurred in the receive direction of the local DTE Dying Gasp: An unrecoverable local failure condition has occurred Critical Event: An unspeciied critical event has occurred Link Fault: The physical layer has determined a fault that occurred in the receive direction of the local DTE Dying Gasp: An unrecoverable local failure condition has occurred Critical Event: An unspeciied critical event has occurred Link Fault: The port can't receive data, the operations will interrupt. Dying Gasp: The port can't receive data, the operations will interrupt. Critical Event: The 802.3ah is failed, can't detect the fault of link. 1. Link Fault: 1. Check the peer is or not right. 2. If right, change the optical iber and check the alarm. 3. If the alarm is alive, change the and check the alarm. 4. If the alarm is alive, change the board. Dying Gasp: Check the peer is or not down. Critical Event: 1. Check the 802.3ah is or not enable, if it is disable, it can't receive PDU. 2. If the 802.3ah is enable, if the port is optical, check the alarm of Link Fault is or not alive, if the alarm is alive, the port can't receive Conidential and Proprietary Information of ZTE CORPORATION 65 ZXG10 iBSC Alarm Handling Reference the PDU 3. Or not, change the good network cable. 4. If the alarm is alive, change the peer board. 198030208 Fault alarm of CFM Alarm Property Probable Cause � Alarm Code:198030208 � Severity:Minor � � Description:Fault alarm of CFM Alarm Type:Equipment Alarm 1. xconCCMdef: The MAID of the received CCM dose not exactly match the MAID conigured in the receiving MEP. errorCCMdef: 1. The MEPID in the received CCM is not conigured in the receiving MEP. 2. The MEPID in the received CCM matches the MEPID of the receiving MEP. Speciic Problem 3. The CCM interval iled in the received CCM dose not match the conigured for the receiving MEP. someREMPCCMdef: The MEP is not receiving CCM in timeout. someRDIdef: The MEP is receiving CCM that have the RDI. someAISdef: The MEP is receiving AIS. 1. xconCCMdef: The MAID of the received CCM dose not exactly match the MAID conigured in the receiving MEP. errorCCMdef: 1. The MEPID in the received CCM is not conigured in the receiving MEP. 2. The MEPID in the received CCM matches the MEPID of the receiving MEP. System Impact Handling Suggestion 3. The CCM interval iled in the received CCM dose not match the conigured for the receiving MEP. someREMPCCMdef: The MEP is not receiving CCM in timeout. someRDIdef: The MEP is receiving CCM that have the RDI. someAISdef: The MEP is receiving AIS. 1. xconCCMdef: The conigure of MD is error. errorCCMdef: The conigure of MEP in MA is error. someREMPCCMdef: 1. the other mep is not enable. 2. the link is fault, mep can't receive PUD. someRDIdef: The receive of the last MEP is error. someAISdef: The receive of the former MEP is error. 1. xconCCMdef: Check the conigure of the peer MD. errorCCMdef: Check the conigure of all MEP in MA. someREMPCCMdef: 1. Check the fault of the link 2. Check the other MEP in MA is enabled or not. someRDIdef: Check the alarm of the last MEP. someAISdef: Check the alarm of the former MEP. 66 Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198066033 T-net center is fault Alarm Property � Alarm Code:198066033 � Severity:Major � � Description:T-net center is fault Alarm Type:Equipment Alarm Probable Cause The big T-net center board has a fault. System Impact T-net related resource is unavailable. Speciic Problem Handling Suggestion The big T-net center board has a fault. 1. Replace the slot. 2. Replace the board. 198066038 The version of the EPU does not accord with that of the RPU Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198066038 � Severity:Major � � Description:The version of the EPU does not accord with that of the RPU Alarm Type:Equipment Alarm The version of the EPU does not accord with that of the RPU. The version of the EPU does not accord with that of the RPU. EPU is not powered on normally. Replace the version of EPU consistent with the version of RPU. If the alarm still exists, please contact ZTE Corporation. Conidential and Proprietary Information of ZTE CORPORATION 67 ZXG10 iBSC Alarm Handling Reference 198066070 Board offline or CPU in reset status for a long period Alarm Property � Alarm Code:198066070 � Severity:Major � � Description:Board ofline or CPU in reset status for a long period Alarm Type:Equipment Alarm Probable Cause 1. The board is not in position. Speciic Problem 1. The board is not in position. System Impact Handling Suggestion 2. Hardware failure. 2. Hardware failure. If the board is normal, but its in-position indicator has a fault, then this alarm does not affect services. The board is in blocked status, no services can be accessed. If the board acts as a resource board, its resources can not be used. 1. Check whether the board is in position. If not, insert the board. 2. Plug/unplug the board. 3. Replace the board. 4. Replace the slot 5. Replace the UIM/GUIM of the same shelf. 198087000 Dry contact alarm 1 Alarm Property Alarm Code:198087000 � Severity: � � Description:Dry contact alarm 1 Alarm Type:Equipment Alarm Probable Cause The device connected with dry contact 1 had alarm. System Impact User deined Speciic Problem 68 � The device connected with dry contact 1 had alarm. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Handling Suggestion None 198087001 Dry contact alarm 2 Alarm Property � Alarm Code:198087001 � Severity: � � Description:Dry contact alarm 2 Alarm Type:Equipment Alarm Probable Cause The device connected with dry contact 2 had alarm. System Impact User deined Speciic Problem Handling Suggestion The device connected with dry contact 2 had alarm. None 198087002 Dry contact alarm 3 Alarm Property � Alarm Code:198087002 � Severity: � � Description:Dry contact alarm 3 Alarm Type:Equipment Alarm Probable Cause The device connected with dry contact 3 had alarm. System Impact User deined Speciic Problem Handling Suggestion The device connected with dry contact 3 had alarm. None 198087003 Dry contact alarm 4 Alarm Property � Alarm Code:198087003 � Severity: � � Description:Dry contact alarm 4 Alarm Type:Equipment Alarm Conidential and Proprietary Information of ZTE CORPORATION 69 ZXG10 iBSC Alarm Handling Reference Probable Cause The device connected with dry contact 4 had alarm. System Impact User deined Speciic Problem Handling Suggestion The device connected with dry contact 4 had alarm. None 198087004 Dry contact alarm 5 Alarm Property � Alarm Code:198087004 � Severity: � � Description:Dry contact alarm 5 Alarm Type:Equipment Alarm Probable Cause The device connected with dry contact 5 had alarm. System Impact User deined Speciic Problem Handling Suggestion The device connected with dry contact 5 had alarm. None 198087005 Dry contact alarm 6 Alarm Property Alarm Code:198087005 � Severity: � � Description:Dry contact alarm 6 Alarm Type:Equipment Alarm Probable Cause The device connected with dry contact 6 had alarm. System Impact User deined Speciic Problem 70 � The device connected with dry contact 6 had alarm. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Handling Suggestion None 198087006 Dry contact alarm 7 Alarm Property � Alarm Code:198087006 � Severity: � � Description:Dry contact alarm 7 Alarm Type:Equipment Alarm Probable Cause The device connected with dry contact 7 had alarm. System Impact User deined Speciic Problem Handling Suggestion The device connected with dry contact 7 had alarm. None 198087007 Dry contact alarm 8 Alarm Property � Alarm Code:198087007 � Severity: � � Description:Dry contact alarm 8 Alarm Type:Equipment Alarm Probable Cause The device connected with dry contact 8 had alarm. System Impact User deined Speciic Problem Handling Suggestion The device connected with dry contact 8 had alarm. None 198087008 Dry contact alarm 9 Alarm Property � Alarm Code:198087008 � Severity: � � Description:Dry contact alarm 9 Alarm Type:Equipment Alarm Conidential and Proprietary Information of ZTE CORPORATION 71 ZXG10 iBSC Alarm Handling Reference Probable Cause The device connected with dry contact 9 had alarm. System Impact User deined Speciic Problem Handling Suggestion The device connected with dry contact 9 had alarm. None 198087009 Dry contact alarm 10 Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087009 � Severity: � � Description:Dry contact alarm 10 Alarm Type:Equipment Alarm The device connected with dry contact 10 had alarm. The device connected with dry contact 10 had alarm. User deined None 198087010 Dry contact alarm 11 Alarm Property Probable Cause Speciic Problem System Impact 72 � Alarm Code:198087010 � Severity: � � Description:Dry contact alarm 11 Alarm Type:Equipment Alarm The device connected with dry contact 11 had alarm. The device connected with dry contact 11 had alarm. User deined Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Handling Suggestion None 198087011 Dry contact alarm 12 Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087011 � Severity: � � Description:Dry contact alarm 12 Alarm Type:Equipment Alarm The device connected with dry contact 12 had alarm. The device connected with dry contact 12 had alarm. User deined None 198087012 EAM dry contact 1 alarm Alarm Property � Alarm Code:198087012 � Severity:Warning � � Description:EAM dry contact 1 alarm Alarm Type:Equipment Alarm Probable Cause The device connected with EAM dry contact 1 had alarm. System Impact User deined Speciic Problem Handling Suggestion The device connected with EAM dry contact 1 had alarm. None 198087013 EAM dry contact 2 alarm Alarm Property � Alarm Code:198087013 � Severity:Warning � � Description:EAM dry contact 2 alarm Alarm Type:Equipment Alarm Conidential and Proprietary Information of ZTE CORPORATION 73 ZXG10 iBSC Alarm Handling Reference Probable Cause The device connected with EAM dry contact 2 had alarm. System Impact User deined Speciic Problem Handling Suggestion The device connected with EAM dry contact 2 had alarm. None 198087014 EAM dry contact 3 alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087014 � Severity:Warning � � Description:EAM dry contact 3 alarm Alarm Type:Equipment Alarm The device connected with EAM dry contact 3 had alarm. The device connected with EAM dry contact 3 had alarm. User deined None 198087015 EAM dry contact 4 alarm Alarm Property Probable Cause Speciic Problem System Impact 74 � Alarm Code:198087015 � Severity:Warning � � Description:EAM dry contact 4 alarm Alarm Type:Equipment Alarm The device connected with EAM dry contact 4 had alarm. The device connected with EAM dry contact 4 had alarm. User deined Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Handling Suggestion None 198087016 EAM dry contact 5 alarm Alarm Property � Alarm Code:198087016 � Severity:Warning � � Description:EAM dry contact 5 alarm Alarm Type:Equipment Alarm Probable Cause The device connected with EAM dry contact 5 had alarm. System Impact User deined Speciic Problem Handling Suggestion The device connected with EAM dry contact 5 had alarm. None 198087017 EAM dry contact 6 alarm Alarm Property � Alarm Code:198087017 � Severity:Warning � � Description:EAM dry contact 6 alarm Alarm Type:Equipment Alarm Probable Cause The device connected with EAM dry contact 6 had alarm. System Impact User deined Speciic Problem Handling Suggestion The device connected with EAM dry contact 6 had alarm. None 198087018 EAM dry contact 7 alarm Alarm Property � Alarm Code:198087018 � Severity:Warning � � Description:EAM dry contact 7 alarm Alarm Type:Equipment Alarm Conidential and Proprietary Information of ZTE CORPORATION 75 ZXG10 iBSC Alarm Handling Reference Probable Cause The device connected with EAM dry contact 7 had alarm. System Impact User deined Speciic Problem Handling Suggestion The device connected with EAM dry contact 7 had alarm. None 198087019 EAM dry contact 8 alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087019 � Severity:Warning � � Description:EAM dry contact 8 alarm Alarm Type:Equipment Alarm The device connected with EAM dry contact 8 had alarm. The device connected with EAM dry contact 8 had alarm. User deined None 198087100 CMM/CMB FLASH programming failure Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion 76 � Alarm Code:198087100 � Severity:Minor � � Description:CMM/CMB FLASH programming failure Alarm Type:Equipment Alarm There are too many FLASH programming times and read/write error. There are too many FLASH programming times and read/write error. No version can be downloaded or read. User cannot solve this problem which generally due to FLASH chip malfunction. Please replace CMM/CMB board in time. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198087101 HW link broken Alarm Property � Alarm Code:198087101 � Severity:Minor � � Description:HW link broken Alarm Type:Equipment Alarm Probable Cause BTS internal communication breaks System Impact Site can't work normally. Speciic Problem Handling Suggestion BTS internal communication breaks 1. Start HW self-loop test to check whether the cable connection goes wrong. 2. If all of DTRU fail to build link, re-plug CMB board. 3. If the software has problem, upgrade it. 198087102 Power overvoltage/undervoltage alarm Alarm Property � Alarm Code:198087102 � Severity:Minor � � Description:Power overvoltage/undervoltage alarm Alarm Type:Equipment Alarm Probable Cause CMM/CMB power voltage is out of adjustment range System Impact CMM/CMB can't work normally. Speciic Problem Handling Suggestion CMM/CMB power voltage is out of adjustment range Power LED displays alarm; please replace CMM/CMB board as soon as possible. 198087103 13M input clock failure Alarm Property � Alarm Code:198087103 � Severity:Minor � � Description:13M input clock failure Alarm Type:Equipment Alarm Conidential and Proprietary Information of ZTE CORPORATION 77 ZXG10 iBSC Alarm Handling Reference Probable Cause CMM/CMB clock unit works abnormally System Impact BTS inner transmission links broken, frame number error and frequency synthesizer abnormal. Speciic Problem Handling Suggestion CMM/CMB clock unit works abnormally 1 Test transmission index. If the transmission continuously has over-2Hz frequency offset in 4 seconds or the single frequency adjustment is more than 4 Hz for 15 times in 6 minutes, it is necessary to notify the engineer to adjust transmission. 2Reset CMB board and check whether the alarm disappears. 3If the alarm does not disappear, replace CMB board. 198087104 Frame No. inconsistent between software and hardware Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087104 � Severity:Minor � � Description:Frame No. hardware inconsistent between software and Alarm Type:Equipment Alarm Frame number accumulation is interrupted due to interference level on the circuit. Frame number accumulation is interrupted due to interference level on the circuit. Frame number accumulation is interrupted due to interference level on the circuit. If the fault cannot restore, the problem may result from CMM/CMB clock error, please replace the board in time. 198087105 FCLK clock failure Alarm Property Probable Cause Speciic Problem 78 � Alarm Code:198087105 � Severity:Minor � � Description:FCLK clock failure Alarm Type:Equipment Alarm CMM/CMB clock unit works abnormally CMM/CMB clock unit works abnormally Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm System Impact Handling Suggestion It induces BTS inner transmission links broken, frame number error and abnormal frequency synthesizer. 1 Test transmission index. If the transmission continuously has over-2Hz frequency offset in 4 seconds or the single frequency adjustment is more than 4 Hz for 15 times in 6 minutes, it is necessary to notify the engineer to adjust transmission. 2Reset CMB board and check whether the alarm disappears. 3If the alarm does not disappear, replace CMB board. 198087106 SYNCLK clock failure Alarm Property � Alarm Code:198087106 � Severity:Minor � � Description:SYNCLK clock failure Alarm Type:Equipment Alarm Probable Cause CMM/CMB clock unit works abnormally System Impact It induces BTS inner transmission links broken, frame number error and abnormal frequency synthesizer. Speciic Problem Handling Suggestion CMM/CMB clock unit works abnormally 1 Test transmission index. If the transmission continuously has over-2Hz frequency offset in 4 seconds or the single frequency adjustment is more than 4 Hz for 15 times in 6 minutes, it is necessary to notify the engineer to adjust transmission. 2Reset CMB board and check whether the alarm disappears. 3If the alarm does not disappear, replace CMB board. 198087107 Master and slave communication link failure Alarm Property Probable Cause Speciic Problem System Impact � Alarm Code:198087107 � Severity:Warning � � Description:Master and slave communication link failure Alarm Type:Equipment Alarm Standby CMM/CMB board is not powered on, or the communication between active-standby CMM/CMB board has error. Standby CMM/CMB board is not powered on, or the communication between active-standby CMM/CMB board has error. Master and slave CMM/CMB board cannot switch with each other. Conidential and Proprietary Information of ZTE CORPORATION 79 ZXG10 iBSC Alarm Handling Reference Handling Suggestion 1. Re-plug CMB board. 2. If the software has problem, upgrade it. 198087108 Standby CMM/CMB board is not in position. Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087108 � Severity:Warning � � Description:Standby CMM/CMB board is not in position. Alarm Type:Equipment Alarm Standby CMM/CMB board is not inserted Standby CMM/CMB board is not inserted Master CMB board cannot swith into the slave when it is abnoraml, and the system reliability reduces. Check whether standby board is present in the rack.If so, reset or re-insert the board ; Check if standby board state is normal (normal state: power LED lights; RUN LED keeps lighting); if not, insert a new CMM/CMB board accordingly. 198087109 Standby CMM/CMB board abnormal Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion 80 � Alarm Code:198087109 � Severity:Warning � � Description:Standby CMM/CMB board abnormal Alarm Type:Equipment Alarm Standby CMM/CMB board is started abnormally or not inserted properly. Standby CMM/CMB board is started abnormally or not inserted properly. Master and slave board cannot switch with each other. Check whether standby board is present in the rack.If so,please reset or re-insert the board (normal state: power LED lights; RUN LED keeps lighting); if not, insert a new CMB board accordingly. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198087110 CMM/CMB board has powered off. Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087110 � Severity:Minor � � Description:CMM/CMB board has powered off. Alarm Type:Equipment Alarm CMM/CMB board has powered off. CMM/CMB board has powered off. CMM/CMB can't work normally. E1 interface will bridge-connect automatically. Replace the CMB circuit board as quickly as possible. 198087111 Master rack communication link alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087111 � Severity:Warning � � Description:Master rack communication link alarm Alarm Type:Equipment Alarm Communication link failed between slave rack and master rack. Communication link failed between slave rack and master rack. Site cannot process data and software downloading as well as operation maintaince, thus working abnormally. (1) Check whether the cable between racks is connected or works well. If not, let it works well. (2) Start self-check of masterslave rack communication to conirm the problem lies in CMM/CMB hardware or software process, and solve corresponding problem then. Conidential and Proprietary Information of ZTE CORPORATION 81 ZXG10 iBSC Alarm Handling Reference 198087112 Communication link alarm between master and slave rack (left) Alarm Property � Alarm Code:198087112 � Severity:Warning � � Description:Communication link alarm between master and slave rack (left) Alarm Type:Equipment Alarm Probable Cause Communication link from master rack to slave rack failed. System Impact Site cannot process data and software downloading as well as operation maintaince, thus working abnormally. Speciic Problem Handling Suggestion Communication link from master rack to slave rack failed. (1) Check whether the cable between racks is connected or works well. If not, timely connect or replace it. (2) Start self-check of master-slave rack communication to conirm the problem lies in CMM/CMB hardware or software process, and solve corresponding problem then. 198087113 Communication link alarm between master and slave rack (right) Alarm Property Alarm Code:198087113 � Severity:Warning � � Description:Communication link alarm between master and slave rack (right) Alarm Type:Equipment Alarm Probable Cause Communication link from master rack to slave rack failed. System Impact Site cannot process data and software downloading as well as operation maintaince, thus working abnormally. Speciic Problem Handling Suggestion 82 � Communication link from master rack to slave rack failed. (1) Check whether the cable between racks is connected or works well. If not, timely connect or replace it. (2) Start self-check of master-slave rack communication to conirm the problem lies in CMM/CMB hardware or software process, and solve corresponding problem then. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198087114 A interface E1 recieves TRX alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087114 � Severity:Minor � � Description:A interface E1 recieves TRX alarm Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would induce abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable has malfunction. If so, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check whether the result is ok. If so, the problem turns to be transmission fault which need to be solved. If not , turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087115 A interface E1 reciever out of frame alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087115 � Severity:Minor � � Description:A interface E1 reciever out of frame alarm Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC or bad E1 connection and CMM board not support C/F interface conigurations (only limited in V2 series BTS) etc.will induce the alarm Situation like chip fault, clock abnormal, difference from BSC or bad E1 connection and CMM board not support C/F interface conigurations (only limited in V2 series BTS) etc.will induce the alarm it has little inluence on callings if it occurs once in a while.However, if it occurs frequently (once in a few minutes time), it would result in abnormal callings or broken links between TRM/DTRU and BSC. 1. Check whether E1 cable electrical connection performs well. If not, redo the cable to remove cable faults. If so, turn to step Conidential and Proprietary Information of ZTE CORPORATION 83 ZXG10 iBSC Alarm Handling Reference 2. Insert CMM/CMB board tightly and reset, watch if alarm restores. 3. If C/F interface alarm occurs, check whether CMM board hardware version is 030900 or 030903. If yes, only need to change to the version 030508 CMM board (only limited to V2 series BTS). 4. Check if E1 interface chip could pass self test and determine whether it is normal. 5. Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not, turn to step 6. Replace CMM/CMB board, and watch if alarm restores. 7. Replace the rear board. 198087116 A interface E1 sender forward-bit-slip indication Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion 84 � Alarm Code:198087116 � Severity:Minor � � Description:A interface E1 sender forward-bit-slip indication Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. it has a little inluence on callings if it occurs once in a while.However, if it occurs frequently (once in a few minutes time), it would result in abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable is malfunction. If so, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result is ok or not. If so, then it's transmission fault which need to be solved. If not, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace backboard. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198087117 A interface E1 sender backward-bit-slip indication Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087117 � Severity:Minor � � Description:A interface E1 sender backward-bit-slip indication Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would induce abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable has malfunction. If so, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087118 A interface E1 reciever forward-bit-slip indication Alarm Property Probable Cause Speciic Problem System Impact � Alarm Code:198087118 � Severity:Minor � � Description:A interface E1 reciever forward-bit-slip indication Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would induce abnormal callings or broken links between TRM/DTRU and BSC. Conidential and Proprietary Information of ZTE CORPORATION 85 ZXG10 iBSC Alarm Handling Reference Handling Suggestion (1) Loop-back check whether E1 cable has malfunction. If so, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087119 A interface E1 reciever backward-bit-slip indication Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087119 � Severity:Minor � � Description:A interface E1 reciever backward-bit-slip indication Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would induce abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable has malfunction. If so, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087120 A interface E1 remote alarm Alarm Property � Alarm Code:198087120 � Severity:Minor � � 86 Description:A interface E1 remote alarm Alarm Type:Equipment Alarm Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Probable Cause Speciic Problem System Impact Handling Suggestion The remote end possibly cannot receive data from the local due to broken send line. The remote end possibly cannot receive data from the local due to broken send line. BTS cannot provide service. (1) Loop-back check whether E1 cable has malfunction. If so, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087121 B interface E1 recieves TRX alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087121 � Severity:Minor � � Description:B interface E1 recieves TRX alarm Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would induce abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. Conidential and Proprietary Information of ZTE CORPORATION 87 ZXG10 iBSC Alarm Handling Reference 198087122 B interface E1 reciever out of frame alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087122 � Severity:Minor � � Description:B interface E1 reciever out of frame alarm Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC or bad E1 connection and CMM board not support C/F interface conigurations (only limited in V2 series BTS) etc.will induce the alarm Situation like chip fault, clock abnormal, difference from BSC or bad E1 connection and CMM board not support C/F interface conigurations (only limited in V2 series BTS) etc.will induce the alarm it has little inluence on callings if it occurs once in a while.However, if it occurs frequently (once in a few minutes time), it would result in abnormal callings or broken links between TRM/DTRU and BSC. 1. Check whether E1 cable electrical connection performs well. If not, redo the cable to remove cable faults. If yes, turn to step 2. Insert CMM/CMB board tightly and reset, watch if alarm restores. 3. If C/F interface alarm occurs, check whether CMM board hardware version is 030900 or 030903. If yes, only need to change to the version 030508 CMM board (only limited to V2 series BTS). 4. Check if E1 interface chip could pass self test and determine whether it is normal. 5. Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 5. 6. Replace CMM/CMB board, and watch if alarm restores. 7. Replace the rear board. 198087123 B interface E1 sender forward-bit-slip indication Alarm Property � Alarm Code:198087123 � Severity:Minor � � 88 Description:B interface E1 sender forward-bit-slip indication Alarm Type:Equipment Alarm Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Probable Cause Speciic Problem System Impact Handling Suggestion Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. it has a little inluence on callings if it occurs once in a while.However, if it occurs frequently (once in a few minutes time), it would result in abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable is malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result is ok or not. If yes, then it's transmission fault which need to be solved. If not, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace backboard. 198087124 B interface E1 sender backward-bit-slip indication Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087124 � Severity:Minor � � Description:B interface E1 sender backward-bit-slip indication Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would induce abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. Conidential and Proprietary Information of ZTE CORPORATION 89 ZXG10 iBSC Alarm Handling Reference 198087125 B interface E1 reciever forward-bit-slip indication Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087125 � Severity:Minor � � Description:B interface E1 reciever forward-bit-slip indication Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would induce abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087126 B interface E1 reciever backward-bit-slip indication Alarm Property Probable Cause Speciic Problem System Impact 90 � Alarm Code:198087126 � Severity:Minor � � Description:B interface E1 reciever backward-bit-slip indication Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would induce abnormal callings or broken links between TRM/DTRU and BSC. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Handling Suggestion (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087127 B interface E1 remote alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087127 � Severity:Minor � � Description:B interface E1 remote alarm Alarm Type:Equipment Alarm The remote end possibly cannot receive data from the local due to broken send line. The remote end possibly cannot receive data from the local due to broken send line. BTS cannot provide service. (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087128 C interface E1 recieves TRX alarm Alarm Property Probable Cause Speciic Problem � Alarm Code:198087128 � Severity:Minor � � Description:C interface E1 recieves TRX alarm Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Conidential and Proprietary Information of ZTE CORPORATION 91 ZXG10 iBSC Alarm Handling Reference System Impact Handling Suggestion If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would induce abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087129 C interface E1 reciever out of frame alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087129 � Severity:Minor � � Description:C interface E1 reciever out of frame alarm Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC or bad E1 connection and CMM board not support C/F interface conigurations (only limited in V2 series BTS) etc.will induce the alarm Situation like chip fault, clock abnormal, difference from BSC or bad E1 connection and CMM board not support C/F interface conigurations (only limited in V2 series BTS) etc.will induce the alarm it has little inluence on callings if it occurs once in a while.However, if it occurs frequently (once in a few minutes time), it would result in abnormal callings or broken links between TRM/DTRU and BSC. 1. Check whether E1 cable electrical connection performs well. If not, redo the cable to remove cable faults. If yes, turn to step 2. Insert CMM/CMB board tightly and reset, watch if alarm restores. 3. If C/F interface alarm occurs, check whether CMM board hardware version is 030900 or 030903. If yes, only need to change to the version 030508 CMM board (only limited to V2 series BTS). 4. Check if E1 interface chip could pass self test and determine whether it is normal. 5. Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 5. 6. Replace CMM/CMB board, and watch if alarm restores. 7. Replace the rear board. 92 Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198087130 C interface E1 sender forward-bit-slip indication Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087130 � Severity:Minor � � Description:C interface E1 sender forward-bit-slip indication Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. it has a little inluence on callings if it occurs once in a while.However, if it occurs frequently (once in a few minutes time), it would result in abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable is malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result is ok or not. If yes, then it's transmission fault which need to be solved. If not, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace backboard. 198087131 C interface E1 sender backward-bit-slip indication Alarm Property Probable Cause Speciic Problem System Impact � Alarm Code:198087131 � Severity:Minor � � Description:C interface E1 sender backward-bit-slip indication Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would induce abnormal callings or broken links between TRM/DTRU and BSC. Conidential and Proprietary Information of ZTE CORPORATION 93 ZXG10 iBSC Alarm Handling Reference Handling Suggestion (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087132 C interface E1 reciever forward-bit-slip indication Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087132 � Severity:Minor � � Description:C interface E1 reciever forward-bit-slip indication Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would induce abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087133 C interface E1 reciever backward-bit-slip indication Alarm Property 94 � � Alarm Code:198087133 Description:C interface E1 reciever backward-bit-slip indication Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm � Probable Cause Speciic Problem System Impact Handling Suggestion � Severity:Minor Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would induce abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087134 C interface E1 remote alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087134 � Severity:Minor � � Description:C interface E1 remote alarm Alarm Type:Equipment Alarm The remote end possibly cannot receive data from the local due to broken send line. The remote end possibly cannot receive data from the local due to broken send line. BTS cannot provide service. (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. Conidential and Proprietary Information of ZTE CORPORATION 95 ZXG10 iBSC Alarm Handling Reference 198087135 D interface E1 recieves TRX alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087135 � Severity:Minor � � Description:D interface E1 recieves TRX alarm Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would induce abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087136 D interface E1 reciever out of frame alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion 96 � Alarm Code:198087136 � Severity:Minor � � Description:D interface E1 reciever out of frame alarm Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC or bad E1 connection and CMM board not support C/F interface conigurations (only limited in V2 series BTS) etc.will induce the alarm Situation like chip fault, clock abnormal, difference from BSC or bad E1 connection and CMM board not support C/F interface conigurations (only limited in V2 series BTS) etc.will induce the alarm it has little inluence on callings if it occurs once in a while.However, if it occurs frequently (once in a few minutes time), it would result in abnormal callings or broken links between TRM/DTRU and BSC. 1. Check whether E1 cable electrical connection performs well. If not, redo the cable to remove cable faults. If yes, turn to step Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 2. Insert CMM/CMB board tightly and reset, watch if alarm restores. 3. If C/F interface alarm occurs, check whether CMM board hardware version is 030900 or 030903. If yes, only need to change to the version 030508 CMM board (only limited to V2 series BTS). 4. Check if E1 interface chip could pass self test and determine whether it is normal. 5. Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 5. 6. Replace CMM/CMB board, and watch if alarm restores. 7. Replace the rear board. 198087137 D interface E1 sender forward-bit-slip indication Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087137 � Severity:Minor � � Description:D interface E1 sender forward-bit-slip indication Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. it has a little inluence on callings if it occurs once in a while.However, if it occurs frequently (once in a few minutes time), it would result in abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable is malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result is ok or not. If yes, then it's transmission fault which need to be solved. If not, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace backboard. Conidential and Proprietary Information of ZTE CORPORATION 97 ZXG10 iBSC Alarm Handling Reference 198087138 D interface E1 sender backward-bit-slip indication Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087138 � Severity:Minor � � Description:D interface E1 sender backward-bit-slip indication Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would induce abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087139 D interface E1 reciever forward-bit-slip indication Alarm Property Probable Cause Speciic Problem System Impact 98 � Alarm Code:198087139 � Severity:Minor � � Description:D interface E1 reciever forward-bit-slip indication Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would induce abnormal callings or broken links between TRM/DTRU and BSC. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Handling Suggestion (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087140 D interface E1 reciever backward-bit-slip indication Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087140 � Severity:Minor � � Description:D interface E1 reciever backward-bit-slip indication Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would induce abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087141 D interface E1 remote alarm Alarm Property � Alarm Code:198087141 � Severity:Minor � � Description:D interface E1 remote alarm Alarm Type:Equipment Alarm Conidential and Proprietary Information of ZTE CORPORATION 99 ZXG10 iBSC Alarm Handling Reference Probable Cause Speciic Problem System Impact Handling Suggestion The remote end possibly cannot receive data from the local due to broken send line. The remote end possibly cannot receive data from the local due to broken send line. BTS cannot provide service. (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087142 E interface E1 recieves TRX alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion 100 � Alarm Code:198087142 � Severity:Minor � � Description:E interface E1 recieves TRX alarm Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would induce abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198087143 E interface E1 reciever out of frame alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087143 � Severity:Minor � � Description:E interface E1 reciever out of frame alarm Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC or bad E1 connection and CMM board not support C/F interface conigurations (only limited in V2 series BTS) etc.will induce the alarm Situation like chip fault, clock abnormal, difference from BSC or bad E1 connection and CMM board not support C/F interface conigurations (only limited in V2 series BTS) etc.will induce the alarm it has little inluence on callings if it occurs once in a while.However, if it occurs frequently (once in a few minutes time), it would result in abnormal callings or broken links between TRM/DTRU and BSC. 1. Check whether E1 cable electrical connection performs well. If not, redo the cable to remove cable faults. If yes, turn to step 2. Insert CMM/CMB board tightly and reset, watch if alarm restores. 3. If C/F interface alarm occurs, check whether CMM board hardware version is 030900 or 030903. If yes, only need to change to the version 030508 CMM board (only limited to V2 series BTS). 4. Check if E1 interface chip could pass self test and determine whether it is normal. 5. Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 5. 6. Replace CMM/CMB board, and watch if alarm restores. 7. Replace the rear board. 198087144 E interface E1 sender forward-bit-slip indication Alarm Property � Alarm Code:198087144 � Severity:Minor � � Description:E interface E1 sender forward-bit-slip indication Alarm Type:Equipment Alarm Conidential and Proprietary Information of ZTE CORPORATION 101 ZXG10 iBSC Alarm Handling Reference Probable Cause Speciic Problem System Impact Handling Suggestion Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. it has a little inluence on callings if it occurs once in a while.However, if it occurs frequently (once in a few minutes time), it would result in abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable is malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result is ok or not. If yes, then it's transmission fault which need to be solved. If not, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace backboard. 198087145 E interface E1 sender backward-bit-slip indication Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion 102 � Alarm Code:198087145 � Severity:Minor � � Description:E interface E1 sender backward-bit-slip indication Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would induce abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198087146 E interface E1 reciever forward-bit-slip indication Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087146 � Severity:Minor � � Description:E interface E1 reciever forward-bit-slip indication Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would induce abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087147 E interface E1 reciever backward-bit-slip indication Alarm Property Probable Cause Speciic Problem System Impact � Alarm Code:198087147 � Severity:Minor � � Description:E interface E1 reciever backward-bit-slip indication Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would induce abnormal callings or broken links between TRM/DTRU and BSC. Conidential and Proprietary Information of ZTE CORPORATION 103 ZXG10 iBSC Alarm Handling Reference Handling Suggestion (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087148 E interface E1 remote alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087148 � Severity:Minor � � Description:E interface E1 remote alarm Alarm Type:Equipment Alarm The remote end possibly cannot receive data from the local due to broken send line. The remote end possibly cannot receive data from the local due to broken send line. BTS cannot provide service. (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087149 F interface E1 recieves TRX alarm Alarm Property Probable Cause Speciic Problem 104 � Alarm Code:198087149 � Severity:Minor � � Description:F interface E1 recieves TRX alarm Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm System Impact Handling Suggestion If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would induce abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087150 F interface E1 reciever out of frame alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087150 � Severity:Minor � � Description:F interface E1 reciever out of frame alarm Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC or bad E1 connection and CMM board not support C/F interface conigurations (only limited in V2 series BTS) etc.will induce the alarm Situation like chip fault, clock abnormal, difference from BSC or bad E1 connection and CMM board not support C/F interface conigurations (only limited in V2 series BTS) etc.will induce the alarm it has little inluence on callings if it occurs once in a while.However, if it occurs frequently (once in a few minutes time), it would result in abnormal callings or broken links between TRM/DTRU and BSC. 1. Check whether E1 cable electrical connection performs well. If not, redo the cable to remove cable faults. If yes, turn to step 2. Insert CMM/CMB board tightly and reset, watch if alarm restores. 3. If C/F interface alarm occurs, check whether CMM board hardware version is 030900 or 030903. If yes, only need to change to the version 030508 CMM board (only limited to V2 series BTS). 4. Check if E1 interface chip could pass self test and determine whether it is normal. 5. Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 5. 6. Replace CMM/CMB board, and watch if alarm restores. 7. Replace the rear board. Conidential and Proprietary Information of ZTE CORPORATION 105 ZXG10 iBSC Alarm Handling Reference 198087151 F interface E1 sender forward-bit-slip indication Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087151 � Severity:Minor � � Description:F interface E1 sender forward-bit-slip indication Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. it has a little inluence on callings if it occurs once in a while.However, if it occurs frequently (once in a few minutes time), it would result in abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable is malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result is ok or not. If yes, then it's transmission fault which need to be solved. If not, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace backboard. 198087152 F interface E1 sender backward-bit-slip indication Alarm Property Probable Cause Speciic Problem System Impact 106 � Alarm Code:198087152 � Severity:Minor � � Description:F interface E1 sender backward-bit-slip indication Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would induce abnormal callings or broken links between TRM/DTRU and BSC. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Handling Suggestion (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087153 F interface E1 reciever forward-bit-slip indication Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087153 � Severity:Minor � � Description:F interface E1 reciever forward-bit-slip indication Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would induce abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087154 F interface E1 reciever backward-bit-slip indication Alarm Property � � Alarm Code:198087154 Description:F interface E1 reciever backward-bit-slip indication Conidential and Proprietary Information of ZTE CORPORATION 107 ZXG10 iBSC Alarm Handling Reference � Probable Cause Speciic Problem System Impact Handling Suggestion � Severity:Minor Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would induce abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087155 F interface E1 remote alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion 108 � Alarm Code:198087155 � Severity:Minor � � Description:F interface E1 remote alarm Alarm Type:Equipment Alarm The remote end possibly cannot receive data from the local due to broken send line. The remote end possibly cannot receive data from the local due to broken send line. BTS cannot provide service. (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198087156 G interface E1 recieves TRX alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087156 � Severity:Minor � � Description:G interface E1 recieves TRX alarm Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would induce abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087157 G interface E1 reciever out of frame alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087157 � Severity:Minor � � Description:G interface E1 reciever out of frame alarm Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC or bad E1 connection and CMM board not support C/F interface conigurations (only limited in V2 series BTS) etc.will induce the alarm Situation like chip fault, clock abnormal, difference from BSC or bad E1 connection and CMM board not support C/F interface conigurations (only limited in V2 series BTS) etc.will induce the alarm it has little inluence on callings if it occurs once in a while.However, if it occurs frequently (once in a few minutes time), it would result in abnormal callings or broken links between TRM/DTRU and BSC. 1. Check whether E1 cable electrical connection performs well. If not, redo the cable to remove cable faults. If yes, turn to step Conidential and Proprietary Information of ZTE CORPORATION 109 ZXG10 iBSC Alarm Handling Reference 2. Insert CMM/CMB board tightly and reset, watch if alarm restores. 3. If C/F interface alarm occurs, check whether CMM board hardware version is 030900 or 030903. If yes, only need to change to the version 030508 CMM board (only limited to V2 series BTS). 4. Check if E1 interface chip could pass self test and determine whether it is normal. 5. Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 5. 6. Replace CMM/CMB board, and watch if alarm restores. 7. Replace the rear board. 198087158 G interface E1 sender forward-bit-slip indication Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion 110 � Alarm Code:198087158 � Severity:Minor � � Description:G interface E1 sender forward-bit-slip indication Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. it has a little inluence on callings if it occurs once in a while.However, if it occurs frequently (once in a few minutes time), it would result in abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable is malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result is ok or not. If yes, then it's transmission fault which need to be solved. If not, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace backboard. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198087159 G interface E1 sender backward-bit-slip indication Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087159 � Severity:Minor � � Description:G interface E1 sender backward-bit-slip indication Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would induce abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087160 G interface E1 reciever forward-bit-slip indication Alarm Property Probable Cause Speciic Problem System Impact � Alarm Code:198087160 � Severity:Minor � � Description:G interface E1 reciever forward-bit-slip indication Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would induce abnormal callings or broken links between TRM/DTRU and BSC. Conidential and Proprietary Information of ZTE CORPORATION 111 ZXG10 iBSC Alarm Handling Reference Handling Suggestion (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087161 G interface E1 reciever backward-bit-slip indication Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087161 � Severity:Minor � � Description:G interface E1 reciever backward-bit-slip indication Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would induce abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087162 G interface E1 remote alarm Alarm Property � Alarm Code:198087162 � Severity:Minor � � 112 Description:G interface E1 remote alarm Alarm Type:Equipment Alarm Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Probable Cause Speciic Problem System Impact Handling Suggestion The remote end possibly cannot receive data from the local due to broken send line. The remote end possibly cannot receive data from the local due to broken send line. BTS cannot provide service. (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087163 H interface E1 recieves TRX alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087163 � Severity:Minor � � Description:H interface E1 recieves TRX alarm Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would induce abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. Conidential and Proprietary Information of ZTE CORPORATION 113 ZXG10 iBSC Alarm Handling Reference 198087164 H interface E1 reciever out of frame alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087164 � Severity:Minor � � Description:H interface E1 reciever out of frame alarm Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC or bad E1 connection and CMM board not support C/F interface conigurations (only limited in V2 series BTS) etc.will induce the alarm Situation like chip fault, clock abnormal, difference from BSC or bad E1 connection and CMM board not support C/F interface conigurations (only limited in V2 series BTS) etc.will induce the alarm it has little inluence on callings if it occurs once in a while.However, if it occurs frequently (once in a few minutes time), it would result in abnormal callings or broken links between TRM/DTRU and BSC. 1. Check whether E1 cable electrical connection performs well. If not, redo the cable to remove cable faults. If yes, turn to step 2. Insert CMM/CMB board tightly and reset, watch if alarm restores. 3. If C/F interface alarm occurs, check whether CMM board hardware version is 030900 or 030903. If yes, only need to change to the version 030508 CMM board (only limited to V2 series BTS). 4. Check if E1 interface chip could pass self test and determine whether it is normal. 5. Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 5. 6. Replace CMM/CMB board, and watch if alarm restores. 7. Replace the rear board. 198087165 H interface E1 sender forward-bit-slip indication Alarm Property � Alarm Code:198087165 � Severity:Minor � � 114 Description:H interface E1 sender forward-bit-slip indication Alarm Type:Equipment Alarm Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Probable Cause Speciic Problem System Impact Handling Suggestion Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. it has a little inluence on callings if it occurs once in a while.However, if it occurs frequently (once in a few minutes time), it would result in abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable is malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result is ok or not. If yes, then it's transmission fault which need to be solved. If not, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace backboard. 198087166 H interface E1 sender backward-bit-slip indication Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087166 � Severity:Minor � � Description:H interface E1 sender backward-bit-slip indication Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would induce abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. Conidential and Proprietary Information of ZTE CORPORATION 115 ZXG10 iBSC Alarm Handling Reference 198087167 H interface E1 reciever forward-bit-slip indication Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087167 � Severity:Minor � � Description:H interface E1 reciever forward-bit-slip indication Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would induce abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087168 H interface E1 reciever backward-bit-slip indication Alarm Property Probable Cause Speciic Problem System Impact 116 � Alarm Code:198087168 � Severity:Minor � � Description:H interface E1 reciever backward-bit-slip indication Alarm Type:Equipment Alarm Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. Situation like chip fault, clock abnormal, difference from BSC clock and poor E1 connection, etc. will induce the alarm. If it occurs once in a while, it has small impact on callings. However, if it occurs frequently (once in a few minutes time), it would Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Handling Suggestion induce abnormal callings or broken links between TRM/DTRU and BSC. (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087169 H interface E1 remote alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087169 � Severity:Minor � � Description:H interface E1 remote alarm Alarm Type:Equipment Alarm The remote end possibly cannot receive data from the local due to broken send line. The remote end possibly cannot receive data from the local due to broken send line. BTS cannot provide service. (1) Loop-back check whether E1 cable has malfunction. If yes, redo the cable to remove cable faults. If not, turn to step 2. (2) Insert CMM/CMB board tightly and power-on again, watch if alarm restores. (3) Start E1 interface self-loop test process and check the result. If the result is ok, the problem turns to be transmission fault which need to be solved. If not ok, turn to step 4. (4) Replace CMM/CMB board, and watch if alarm restores. (5) Replace the rear board. 198087170 Temperature alarm Alarm Property Probable Cause Speciic Problem � Alarm Code:198087170 � Severity:Warning � � Description:Temperature alarm Alarm Type:Equipment Alarm The alarm is due to fan fault or module over high temperature. The alarm is due to fan fault or module over high temperature. Conidential and Proprietary Information of ZTE CORPORATION 117 ZXG10 iBSC Alarm Handling Reference System Impact Handling Suggestion User deined Check whether environment temperature meets requirment. If so, continue observing and keep normal work status in the pemise of no faults lying in other modules; If not, please improve equipment working environment, and replace FCM module if it is faulty. 198087171 Fan not-in-position alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion Alarm Property � Alarm Code:198087171 � Severity:Warning � � Description:Fan not-in-position alarm Alarm Type:Equipment Alarm Fan is not inserted or inserted in right position. Fan is not inserted or inserted in right position. User deined Insert the fan or re-plug the fan and make it in right position. 198087172 Fan control board CPU alarm � Alarm Code:198087172 � Severity:Warning � � Description:Fan control board CPU alarm Alarm Type:Equipment Alarm Probable Cause CPU has faults. System Impact User deined Speciic Problem Handling Suggestion CPU has faults. 1. Check error-detection circuit fault and remove it. 2. Check FCM board fault and replace FCM control board. 198087173 Fan alarm Alarm Property 118 � � Alarm Code:198087173 Description:Fan alarm Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm � Probable Cause Speciic Problem System Impact Handling Suggestion � Severity:Warning Alarm Type:Equipment Alarm Fan stops rotating due to fault Fan stops rotating due to fault User deined 1. Check error-detection circuit fault and remove it. 2. Check fan engine fault and replace FCM. 3. Check whether TPU alarm acquisition circuit is correct, if not, replace corresponding TRM module. 198087174 Fan environment temperature alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087174 � Severity:Warning � � Description:Fan environment temperature alarm Alarm Type:Equipment Alarm The error is caused by fan engine fault or too high temperature of module . The error is caused by fan engine fault or too high temperature of module . it will lead to high temperature of TRM/DTRU, and affect the whole network performance. Check whether environment temperature meets requirment. If so, continue observing and keep normal work status in the pemise of no faults lying in other modules; If not, please improve equipment working environment, and replace FCM module if it is faulty. 198087175 Fan 1 alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087175 � Severity:Warning � � Description:Fan 1 alarm Alarm Type:Equipment Alarm Fan stops rotating due to fault Fan stops rotating due to fault Lead to over high temperature of same layer TRX frame. 1. Check whether corresponding fan engine has stopped rotating. If so, replace the fan engine plug-in box; if not, turn to step Conidential and Proprietary Information of ZTE CORPORATION 119 ZXG10 iBSC Alarm Handling Reference 2. Check whether the lines of fan engine and fan controller has fault. If so, turn to step 3; if not, turn to step 4. 3. Check whether fan engine cable or board-port connector has fault. If fan engine cable has malfunction, replace the fan plug-in box. If board-port connector has error, replace fan controller board DFCM/FNCB. 4. Check whether error-detection circuit exists fault. If yes, remove the alarm circuit fault; if not, turn to step 5. Check whether alarm collection of fan controller board is abnormal. If so, replace fan controller board DFCM/FNCB; if not, turn to step 6. Check whether TRM/DTRU alarm collection circuit is abnormal. If so replace corresponding TRM/DTRU. 198087176 Fan 2 alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087176 � Severity:Warning � � Description:Fan 2 alarm Alarm Type:Equipment Alarm Fan stops rotating due to fault Fan stops rotating due to fault Lead to over high temperature of same layer TRX frame. 1. Check whether corresponding fan engine stops rotating. If yes, replace the fan engine plug-in box; if not, turn to step 2. Check whether the lines of fan engine and fan controller exist fault. If so, turn to step 3; if not, turn to step 4. 3. Check whether fan engine cable or board-port connector exists fault. If fan engine cable has malfunction, replace the fan plug-in box. If board-port connector has error, replace fan controller board DFCM/FNCB. 4. Check whether error-detection circuit exists fault. If so, remove the alarm circuit fault; if not, turn to step 5. Check whether alarm collection of fan controller board is abnormal. If so, replace fan controller board DFCM/FNCB; if not, turn to step 6. Check whether TRM/DTRU alarm collection circuit is abnormal. If so, replace corresponding TRM/DTRU. 120 Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198087177 Fan controller module alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087177 � Severity:Warning � � Description:Fan controller module alarm Alarm Type:Equipment Alarm The alarm is due to fan engine fault or module over high temperature. The alarm is due to fan engine fault or module over high temperature. Lead to over high temperature of TRM/DTRU, and affect the whole network performance. Check whether environment temperature meets requirment. If so, continue observing and keep normal work status in the pemise of no faults lying in other modules; If not, please improve equipment working environment, and replace FCM module if it is faulty. 198087178 Low Noise Amplifier (LNA) alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087178 � Severity:Minor � � Description:Low Noise Ampliier (LNA) alarm Alarm Type:Equipment Alarm LNA current exceeds by 30% LNA current exceeds by 30% User deined Please replace AEM module as soon as possible. 198087179 Tower amplifier power alarm Alarm Property � Alarm Code:198087179 � Severity:Warning � Description:Tower ampliier power alarm Conidential and Proprietary Information of ZTE CORPORATION 121 ZXG10 iBSC Alarm Handling Reference � Alarm Type:Equipment Alarm Probable Cause AEM tower ampliier power triggers alarm. System Impact User deined Speciic Problem Handling Suggestion Alarm Property AEM tower ampliier power triggers alarm. Please replace tower ampliier module or AEM module in time. 198087180 SWR of AEM HYCOM minor alarm � Alarm Code:198087180 � Severity:Minor � � Description:SWR of AEM HYCOM minor alarm Alarm Type:Equipment Alarm Probable Cause 1. ombiner SWR exceeds 1.5 and triggers alarm. System Impact User deined Speciic Problem Handling Suggestion 1. ombiner SWR exceeds 1.5 and triggers alarm. Keep on observing and don’t replace AEM module if normal work isn's affected. 198087181 SWR of AEM HYCOM major alarm Alarm Property Probable Cause Speciic Problem System Impact 122 � Alarm Code:198087181 � Severity:Major � � Description:SWR of AEM HYCOM major alarm Alarm Type:Equipment Alarm Combiner SWR exceeds 3.0 and triggers alarm. Combiner SWR exceeds 3.0 and triggers alarm. User deined Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Handling Suggestion Please replace AEM and reset the TRM which connects to this AEM. 198087182 AEM power alarm(BTS V2) Alarm Property � Alarm Code:198087182 � Severity:Major � � Description:AEM power alarm(BTS V2) Alarm Type:Equipment Alarm Probable Cause AEM power triggers alarm. System Impact User deined Speciic Problem Handling Suggestion AEM power triggers alarm. Please replace AEM module as soon as possible. 198087183 AEM type alarm(BTS V2) Alarm Property � Alarm Code:198087183 � Severity:Major � � Description:AEM type alarm(BTS V2) Alarm Type:Equipment Alarm Probable Cause the coniguration of AEM type is wrong. System Impact User deined Speciic Problem Handling Suggestion the coniguration of AEM type is wrong. Check whether AEM conig type conforms to the actual type and whether is inserted well and powered on. If not conforms, replace AEM; if the type is correct, check whether the problem is back panel transportation fault or TPU collection circuits error, and replace corresponding cables or modules. Conidential and Proprietary Information of ZTE CORPORATION 123 ZXG10 iBSC Alarm Handling Reference 198087184 AEM not-in-posion alarm (BTS V2) Alarm Property Alarm Code:198087184 � Severity:Major � � Description:AEM not-in-posion alarm (BTS V2) Alarm Type:Equipment Alarm Probable Cause AEM is not in position and triggers alarm. System Impact User deined Speciic Problem Handling Suggestion Alarm Property AEM is not in position and triggers alarm. Please replace AEM and reset the TRM which connects to this AEM. 198087185 AEM power alarm � Alarm Code:198087185 � Severity:Major � � Description:AEM power alarm Alarm Type:Equipment Alarm Probable Cause There is something wrong with AEM power. System Impact Radio transmission is affected. Speciic Problem Handling Suggestion 124 � There is something wrong with AEM power. (1) Check whether there is PA temperature alarm or fan environment temperature alarm in the background. If so, address fan alarm irst, and insert virtual module if there is no TRX on the right side of TRM board. (2) Check whether the fuse of CDU is damaged. If so, replace the fuse of corresponding type. Please note: FU1 2A, FU2, 1A. (3) Pull out CDU and the same-layer DTRU module, and check whether the pins on the rear board are bent. If so, change the slot or replace the rear board, and power on the board again to see if alarm restores. (If changes the slot, the background need re-conigured) (4) Replace CDU. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198087186 LNA0 overcurrent alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087186 � Severity:Minor � � Description:LNA0 overcurrent alarm Alarm Type:Equipment Alarm LNA0 current exceeds by 30% LNA0 current exceeds by 30% The DTRU connected to this ATEM cannot work (if main sub-set LNA are all damaged) or cannot work normally (if only one LNA is damaged). (1) Check whether there is PA temperature alarm or fan environment temperature alarm in the background. If so, address fan alarm irst, and insert virtual module if there is no TRX on the right side of TRM board. (2) Pull out CDU and the same-layer DTRU module, and check whether the pins on the rear board are bent. If so, change the slot or replace the rear board, and power on the board again to see if alarm restores. (If changes the slot, the background need re-coniguring) (3) Replace CDU. 198087187 LNA0 overcurrent alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087187 � Severity:Minor � � Description:LNA0 overcurrent alarm Alarm Type:Equipment Alarm LNA1 current exceeds by 30% LNA1 current exceeds by 30% The DTRU connected to this ATEM cannot work (if main sub-set LNA are all damaged) or cannot work normally (if only one LNA is damaged). (1) Check whether there is PA temperature alarm or fan environment temperature alarm in the background. If yes, address fan alarm irst, and insert virtual module if there is no TRX on the right side of TRM board. (2) Pull out CDU and the same-layer DTRU module, and check whether the pins on the rear board are bent. If yes, change the slot or replace the rear board, and power on the board again to see if alarm restores. (If changes the slot, the background need re-coniguring) (3) Replace CDU. Conidential and Proprietary Information of ZTE CORPORATION 125 ZXG10 iBSC Alarm Handling Reference 198087188 Tower amplifier 0 overcurrent alarm Alarm Property � Alarm Code:198087188 � Severity:Warning � � Description:Tower ampliier 0 overcurrent alarm Alarm Type:Equipment Alarm Probable Cause AEM tower ampliier power 0 triggers alarm. System Impact The sensitivity of corresponding DTRU UL receiver is affected. Speciic Problem Handling Suggestion AEM tower ampliier power 0 triggers alarm. (1) Check whether there is PA temperature alarm or fan environment temperature alarm in the background. If yes, address fan alarm irst, and insert virtual module if there is no TRX on the right side of TRM board. (2) Pull of tower ampliier power cable, and its poisition is: open BTS rear cover and pull off the socket which labelled X31 TA_PWR (X31 PA_PWR for the old type rack), the tower ampliier power cable connets all the way to set top PWRTA_Ln. Check whether the alarm disappears, and the power cable is useless if no tower ampliier exists.While if the alarm disappears when tower ampliier exists, please check whether there is short between power cable and tower ampliier or whether PA goes wrong. (3) Pull out CDU and the same-layer DTRU module, and check whether the pins on the rear board are bent. If yes, change the slot or replace the rear board, and power on the board again to see if alarm restores. (If changes the slot, the background need re-coniguring). (4) Replace CDU, and reset the TRX which connects to it. 198087189 Tower amplifier 1 overcurrent alarm Alarm Property Alarm Code:198087189 � Severity:Warning � � Description:Tower ampliier 1 overcurrent alarm Alarm Type:Equipment Alarm Probable Cause AEM tower ampliier power 1 triggers alarm. System Impact The sensitivity of corresponding DTRU UL receiver is affected. Speciic Problem Handling Suggestion 126 � AEM tower ampliier power 1 triggers alarm. (1) Check whether there is PA temperature alarm or fan environment temperature alarm in the background. If yes, address fan alarm irst, and insert virtual module if there is no TRX on the right side of TRM board. (2) Pull of tower ampliier power cable, and its poisition is: open BTS rear cover and pull off the socket Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm which labelled X31 TA_PWR (X31 PA_PWR for the old type rack), the tower ampliier power cable connets all the way to set top PWRTA_Ln. Check whether the alarm disappears, and the power cable is useless if no tower ampliier exists.While if the alarm disappears when tower ampliier exists, please check whether there is short between power cable and tower ampliier or whether PA goes wrong. (3) Pull out CDU and the same-layer DTRU module, and check whether the pins on the rear board are bent. If yes, change the slot or replace the rear board, and power on the board again to see if alarm restores. (If changes the slot, the background need re-coniguring). (4) Replace CDU, and reset the TRX which connects to it. 198087190 SWR of AEM HYCOM minor alarm Alarm Property � Alarm Code:198087190 � Severity:Minor � � Description:SWR of AEM HYCOM minor alarm Alarm Type:Equipment Alarm Probable Cause Combiner SWR exceeds limit minorly and triggers alarm. System Impact Radio transmission is affected. Speciic Problem Handling Suggestion Combiner SWR exceeds limit minorly and triggers alarm. (1) Check whether the connection between the CDU antenna mouth and the RF jumper which connects all DTRU and CDU is tight or not, if not, fasten the connection with tool. After that, reset the TRX connecting with it and check whether the alarm disappears. (2) Measure SWR of the jumper between CDU and antenna with SITEMASTER. Check whether the SWR value exceeds standard. If yes, the antenna has fault, and then check the antenna system part by part upon the test result. Once the fault is found, fasten the antenna, make waterproof treatment on the antenna and replace the antenna. Reset the TRX connecting with it and check whether the alarm disappears. 3Replace the RF cable which connects DTRU with CDU. Reset the TRX connecting with it and check whether the alarm disappears. 4 Pull out CDU and the same-layer DTRU module, and check whether the pins on the rear board are bent. If yes, change the slot or replace the rear board, and power on the board again to see if alarm restores. (If changes the slot, the background need re-coniguring). 5Replace CDU, and reset the TRX which connects to it. Conidential and Proprietary Information of ZTE CORPORATION 127 ZXG10 iBSC Alarm Handling Reference 198087191 SWR of AEM HYCOM major alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087191 � Severity:Major � � Description:SWR of AEM HYCOM major alarm Alarm Type:Equipment Alarm Combiner SWR exceeds limit severely and triggers alarm. Combiner SWR exceeds limit severely and triggers alarm. Radio transmission is affected. (1) Check whether the connection between the CDU antenna mouth and the RF jumper which connects all DTRU and CDU is tight or not, if not, fasten the connection with tool. After that, reset the TRX connecting with it and check whether the alarm disappears. (2) Measure SWR of the jumper between CDU and antenna with SITEMASTER. Check whether the SWR value exceeds standard. If yes, the antenna has fault, and then check the antenna system part by part upon the test result. Once the fault is found, fasten the antenna, make waterproof treatment on the antenna and replace the antenna. Reset the TRX connecting with it and check whether the alarm disappears. 3Replace the RF cable which connects DTRU with CDU. Reset the TRX connecting with it and check whether the alarm disappears. 4 Pull out CDU and the same-layer DTRU module, and check whether the pins on the rear board are bent. If yes, change the slot or replace the rear board, and power on the board again to see if alarm restores. (If changes the slot, the background need re-coniguring). 5Replace CDU, and reset the TRX which connects to it. 198087192 AEM type alarm Alarm Property Alarm Code:198087192 � Severity:Major � � Description:AEM type alarm Alarm Type:Equipment Alarm Probable Cause AEM type triggers alarm. System Impact Radio transmission is affected. Speciic Problem Handling Suggestion 128 � AEM type triggers alarm. (1) Check whether there is PA temperature alarm or fan environment temperature alarm in the background. If yes, address fan alarm irst, and insert virtual module if there is no TRX on the right side of TRM board. (2) Check whether AEM coniguration type is consistent with the actual type, and whether DTRU is associated with the background. If not, change or modify the background coniguration. (3) Check whether AEM is powered on or plugged Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm properly. Shut down AEM module, pull off the module and re-insert, turn on the power again and check whether the alarm restores. (4) Check whether the board DIP switch of AEM is correct. If not, adjust the DIP switch till it is correct. Power on the equipment again and check whether the alarm restores. (5) Pull off the AEM and same-layer DTRU module, check whether the pins on the rear board are bent. If yes, replace the rear board, and power on the board again to see if alarm restores. (6) Plug in site id, and reset CMB. About ive minutes later, check whether the alarm is recovered. (7) Replace AEM module. 198087193 AEM not-in-posion alarm Alarm Property � Alarm Code:198087193 � Severity:Major � � Description:AEM not-in-posion alarm Alarm Type:Equipment Alarm Probable Cause AEM is not in position and triggers alarm. System Impact Radio transmission is affected. Speciic Problem Handling Suggestion AEM is not in position and triggers alarm. (1) Check whether there is PA temperature alarm or fan environment temperature alarm in the background. If yes, address fan alarm irst, and insert virtual module if there is no TRX on the right side of TRM board. (2) Check whether AEM coniguration type is consistent with the actual type, and whether DTRU is associated with the background. If not, change or modify the background coniguration. (3) Check whether AEM is powered on or plugged properly. Shut down AEM module, pull off the module and re-insert, turn on the power again and check whether the alarm restores. (4) Check whether the board DIP switch of AEM is correct. If not, adjust the DIP switch till it is correct. Check whether the fuse on CDU is broken, if so, change the fuse of the same type. Note: FU1 2A, FU2 1A. Power on the equipment again and check whether the alarm restores. (5) Pull off the AEM and same-layer DTRU module, check whether the pins on the rear board are bent. If yes, replace the rear board, and power on the board again to see if alarm restores. (6) Plug in site id, and reset CMB. About ive minutes later, check whether the alarm is recovered. (7) Replace AEM module. Conidential and Proprietary Information of ZTE CORPORATION 129 ZXG10 iBSC Alarm Handling Reference 198087194 CHP DSP0 of TPU initialization failure(BTS V2) Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087194 � Severity:Minor � � Description:CHP DSP0 of TPU initialization failure(BTS V2) Alarm Type:Equipment Alarm DSP software or hardware has error. DSP software or hardware has error. User deined 1. Download software of this DSP again. 2. Reset TRM shelf, restart DSP unit and check whether the alarm restores. If yes, the DSP initialization error is gennerally induced by exterior strong disturbance, and the TRM unit can still work normally; if the alarm doesn't restore, replace TRM module then. 198087195 CHP DSP1 of TPU initialization failure Alarm Property Alarm Code:198087195 � Severity:Warning � � Description:CHP DSP1 of TPU initialization failure Alarm Type:Equipment Alarm Probable Cause The software or hardware of DSP works abnormally. System Impact User deined Speciic Problem Handling Suggestion 130 � The software or hardware of DSP works abnormally. 1. Download software of this DSP again. 2. Reset TRM shelf, restart DSP unit and check whether the alarm restores. If yes, the DSP initialization error is gennerally induced by exterior strong disturbance, and the TRM unit can still work normally; if the alarm doesn't restore, replace TRM module then. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198087196 CHP DSP2 of TPU initialization failure Alarm Property � Alarm Code:198087196 � Severity:Warning � � Description:CHP DSP2 of TPU initialization failure Alarm Type:Equipment Alarm Probable Cause The software or hardware of DSP works abnormally. System Impact User deined Speciic Problem Handling Suggestion The software or hardware of DSP works abnormally. 1. Re-Download software of this DSP. 2. Reset TRM shelf, restart DSP unit and check whether the alarm restores. If so, the DSP initialization error is gennerally caused by exterior strong disturbance, and the TRM unit can still works well; if the alarm doesn't restore, replace TRM module then. 198087197 CHP DSP3 of TPU initialization failure Alarm Property � Alarm Code:198087197 � Severity:Warning � � Description:CHP DSP3 of TPU initialization failure Alarm Type:Equipment Alarm Probable Cause DSP software or hardware has error. System Impact User deined Speciic Problem Handling Suggestion DSP software or hardware has error. 1. Download software of this DSP again. 2. Reset TRM shelf, restart DSP unit and check whether the alarm restores. If yes, the DSP initialization error is gennerally induced by exterior strong disturbance, and the TRM unit can still work normally; if the alarm doesn't restore, replace TRM module then. Conidential and Proprietary Information of ZTE CORPORATION 131 ZXG10 iBSC Alarm Handling Reference 198087198 Uplink ADC chip initialization failure Alarm Property � Alarm Code:198087198 � Severity:Minor � � Description:Uplink ADC chip initialization failure Alarm Type:Equipment Alarm Probable Cause Uplink ADC chip initialization failed. System Impact User deined Speciic Problem Handling Suggestion Uplink ADC chip initialization failed. 1. Reset this module in order to work normally. 2. if reset is of no effect , please replace this module at once. 198087199 Uplink ADC resource unavailable Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087199 � Severity:Minor � � Description:Uplink ADC resource unavailable Alarm Type:Equipment Alarm Uplink ADC resource is not available. Uplink ADC resource is not available. User deined 1. Reset this module in order to work normally. 2. if reset is of no effect , please replace this module at once. 198087200 CIP resource unavailable Alarm Property Probable Cause 132 � Alarm Code:198087200 � Severity:Minor � � Description:CIP resource unavailable Alarm Type:Equipment Alarm Uplink/downlink loop data demodulation failed. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Speciic Problem System Impact Handling Suggestion Uplink/downlink loop data demodulation failed. User deined If this alarm occurs, and meantime there is trafic on this TRM, it indicates that the TRM is normal; if no trafic on this TRM or the RF_LOOP test launched by OMCR failed, it means this TRM is damaged and please replace it immediately. 198087201 Uplink failure Alarm Property � Alarm Code:198087201 � Severity:Minor � � Description: Uplink failure Alarm Type:Equipment Alarm Probable Cause Uplink data receiving is error. System Impact User deined Speciic Problem Handling Suggestion Uplink data receiving is error. 1. Reset the module,then it maybe work properly. 2. If it is not effective after Reset, please replace this module. 198087202 TPU FLASH Memory failure(BTS V2) Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087202 � Severity:Minor � � Description:TPU FLASH Memory failure(BTS V2) Alarm Type:Equipment Alarm Beacuse too many times of FLASH programming ,read/wirte Flash error or software calibration error. Beacuse too many times of FLASH programming ,read/wirte Flash error or software calibration error. User deined Reset this CU irst, and check whether the alarm restores. If yes, the alarm is induced by CPU reading FLASH MEMORY data which caused by exterior disturbances, and the CU could work normally after resetting resumes. If resetting can't restore the alarm, please replace TRM module . Conidential and Proprietary Information of ZTE CORPORATION 133 ZXG10 iBSC Alarm Handling Reference 198087203 Watchdog of TPU CHP DSP0 overflow(BTS V2) Alarm Property � Alarm Code:198087203 � Severity:Minor � � Description:Watchdog of TPU CHP DSP0 overlow(BTS V2) Alarm Type:Equipment Alarm Probable Cause DSP0 of channel processing unit has no response temporarily System Impact User deined Speciic Problem Handling Suggestion DSP0 of channel processing unit has no response temporarily Reset this CU irst, and check whether the alarm restores. If so, the alarm is caused by DSP interior abnormal condition, and the CU could work normally after resetting . If resetting can't restore the alarm, make BSC to start BCCH changeover strategy and replace TRM module at the meantime. 198087204 Watchdog of TPU CHP DSP1 overflow Alarm Property Alarm Code:198087204 � Severity:Warning � � Description:Watchdog of TPU CHP DSP1 overlow Alarm Type:Equipment Alarm Probable Cause DSP1 of channel processing unit has no response temporarily System Impact User deined Speciic Problem Handling Suggestion 134 � DSP1 of channel processing unit has no response temporarily Reset this CU irst, and check whether the alarm restores. If yest, the alarm is induced by DSP interior abnormal condition, and the CU could work normally after resetting resumes. If resetting can't restore the alarm, replace TRM module then. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198087205 Watchdog of TPU CHP DSP2 overflow Alarm Property � Alarm Code:198087205 � Severity:Warning � � Description:Watchdog of TPU CHP DSP2 overlow Alarm Type:Equipment Alarm Probable Cause DSP2 of channel processing unit has no response temporarily System Impact User deined Speciic Problem Handling Suggestion DSP2 of channel processing unit has no response temporarily Reset this CU irst, and check whether the alarm restores. If yest, the alarm is induced by DSP interior abnormal condition, and the CU could work normally after resetting resumes. If resetting can't restore the alarm, replace TRM module then. 198087206 Watchdog of TPU CHP DSP3 overflow Alarm Property � Alarm Code:198087206 � Severity:Warning � � Description:Watchdog of TPU CHP DSP3 overlow Alarm Type:Equipment Alarm Probable Cause DSP3 of channel processing unit has no response temporarily System Impact User deined Speciic Problem Handling Suggestion DSP3 of channel processing unit has no response temporarily Reset this CU irst, and check whether the alarm restores. If yest, the alarm is induced by DSP interior abnormal condition, and the CU could work normally after resetting resumes. If resetting doesn’t help on the alarm, replace TRM module then. 198087207 Watchdog of FUC overflow Alarm Property � Alarm Code:198087207 � Severity:Minor � Description:Watchdog of FUC overlow Conidential and Proprietary Information of ZTE CORPORATION 135 ZXG10 iBSC Alarm Handling Reference � Alarm Type:Equipment Alarm Probable Cause FUC program has no response temporarily System Impact User deined Speciic Problem Handling Suggestion FUC program has no response temporarily User can reset TPU to solve this prolbem. If it isn't solved, please replace TRM module. 198087208 Wrong configuration of TPU Channel 0 Alarm Property � Alarm Code:198087208 � Severity:Warning � � Description:Wrong coniguration of TPU Channel 0 Alarm Type:Equipment Alarm Probable Cause Parameter coniguration has error or conilcts each other occur. System Impact User deined Speciic Problem Handling Suggestion Parameter coniguration has error or conilcts each other occur. Wait ten minutes. If the alarm still exists,conigure parameters again from background,and synchronize them to base station. Otherwise replace TRM module. 198087209 Wrong configuration of TPU Channel 1 Alarm Property Alarm Code:198087209 � Severity:Warning � � Description:Wrong coniguration of TPU Channel 1 Alarm Type:Equipment Alarm Probable Cause Parameter coniguration has error or conilcts occur. System Impact User deined Speciic Problem 136 � Parameter coniguration has error or conilcts occur. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Handling Suggestion Wait ten minutes. If the alarm still exists,conigure parameters again from background,and synchronize them to base station. Otherwise replace TRM module. 198087210 Wrong configuration of TPU Channel 2 Alarm Property � Alarm Code:198087210 � Severity:Warning � � Description:Wrong coniguration of TPU Channel 2 Alarm Type:Equipment Alarm Probable Cause Parameter coniguration has error or conilcts occur. System Impact User deined Speciic Problem Handling Suggestion Parameter coniguration has error or conilcts occur. Wait ten minutes. If the alarm still exists,conigure parameters again from background,and synchronize them to base station. Otherwise replace TRM module. 198087211 Wrong configuration of TPU Channel 3 Alarm Property � Alarm Code:198087211 � Severity:Warning � � Description:Wrong coniguration of TPU Channel 3 Alarm Type:Equipment Alarm Probable Cause Parameter coniguration has error or conilcts occur. System Impact User deined Speciic Problem Handling Suggestion Parameter coniguration has error or conilcts occur. Wait ten minutes. If the alarm still exists,conigure parameters again from background,and synchronize them to base station. Otherwise replace TRM module. Conidential and Proprietary Information of ZTE CORPORATION 137 ZXG10 iBSC Alarm Handling Reference 198087212 Wrong configuration of TPU Channel 4 Alarm Property � Alarm Code:198087212 � Severity:Warning � � Description:Wrong coniguration of TPU Channel 4 Alarm Type:Equipment Alarm Probable Cause Parameter coniguration has error or conilcts occur. System Impact User deined Speciic Problem Handling Suggestion Parameter coniguration has error or conilcts occur. Wait ten minutes. If the alarm still exists,conigure parameters again from background,and synchronize them to base station. Otherwise replace TRM module. 198087213 Wrong configuration of TPU Channel 5 Alarm Property Alarm Code:198087213 � Severity:Warning � � Description:Wrong coniguration of TPU Channel 5 Alarm Type:Equipment Alarm Probable Cause Parameter coniguration has error or conilcts occur. System Impact User deined Speciic Problem Handling Suggestion 138 � Parameter coniguration has error or conilcts occur. Wait ten minutes. If the alarm still exists,conigure parameters again from background,and synchronize them to base station. Otherwise replace TRM module. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198087214 Wrong configuration of TPU Channel 6 Alarm Property � Alarm Code:198087214 � Severity:Warning � � Description:Wrong coniguration of TPU Channel 6 Alarm Type:Equipment Alarm Probable Cause Parameter coniguration has error or conilcts occur. System Impact User deined Speciic Problem Handling Suggestion Parameter coniguration has error or conilcts occur. Wait ten minutes. If the alarm still exists,conigure parameters again from background,and synchronize them to base station. Otherwise replace TRM module. 198087215 Wrong configuration of TPU Channel 7 Alarm Property � Alarm Code:198087215 � Severity:Warning � � Description:Wrong coniguration of TPU Channel 7 Alarm Type:Equipment Alarm Probable Cause Wrong coniguration or coniguration conilcts each other. System Impact User deined Speciic Problem Handling Suggestion Wrong coniguration or coniguration conilcts each other. Wait ten minutes. If the alarm still exists,conigure parameters again from background,and synchronize them to base station. Otherwise replace TRM module. Conidential and Proprietary Information of ZTE CORPORATION 139 ZXG10 iBSC Alarm Handling Reference 198087216 Cell parameter configuration mismatch (processing error) (BTS V2) Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087216 � Severity:Minor � � Description:Cell parameter coniguration mismatch (processing error) (BTS V2) Alarm Type:Equipment Alarm The alarm occurs when cell parameter coniguration is incorrect or conlicts with channel parameters and CU parameter coniguration; or TRX actual type is not consistent to the physical board. The alarm occurs when cell parameter coniguration is incorrect or conlicts with channel parameters and CU parameter coniguration; or TRX actual type is not consistent to the physical board. User deined 1. Wait for ten minutes. If the alarm still exists,conigure parameters again from background,and synchronize them to base station. Otherwise check the hardware and replace TRM/DTRM module in time. 2. Please check whether the TRX coniguration in OMCR is consistent with the physical board or not. 198087217 Software version of FUC mismatch(BTS V2) Alarm Property Probable Cause Speciic Problem System Impact 140 � Alarm Code:198087217 � Severity:Minor � � Description:Software version of FUC mismatch(BTS V2) Alarm Type:Equipment Alarm FUC software version load error. If one of the carriers is conigured as BCCH, then the whole cell can not work normally. FUC software version load error. If one of the carriers is conigured as BCCH, then the whole cell can not work normally. User deined Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Handling Suggestion If it is not effective after resetting the TRM , please replace TRM . 198087218 Software version of CHP mismatch(BTS V2) Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087218 � Severity:Minor � � Description:Software version of CHP mismatch(BTS V2) Alarm Type:Equipment Alarm CHP software version loading failed. CHP software version loading failed. User deined If it is not effective after resetting the TRM , please replace TRM . 198087219 FUC has not responsed with CMM in time (BTS V2) Alarm Property � Alarm Code:198087219 � Severity:Warning � � Description:FUC has not responsed with CMM in time (BTS V2) Alarm Type:Equipment Alarm Probable Cause MO software (has/has no) response temporarily (set by CMM) System Impact User deined Speciic Problem Handling Suggestion MO software (has/has no) response temporarily (set by CMM) 1. Waiting for ten minutes and observe if the alarm restores. 2. If the alarm doesn’t restore for a long time, please re-plug and reset FUC when trafic is not busy. 3. If alarm still exists after resetting, reset CMM when trafic is not busy. 4. If alarm still exists, replace TRM module. 5. If it is software problem, correct it and upgrade the version. Conidential and Proprietary Information of ZTE CORPORATION 141 ZXG10 iBSC Alarm Handling Reference 198087220 LAPD communication link between FUC and BSC broken Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087220 � Severity:Major � � Description:LAPD communication link between FUC and BSC broken Alarm Type:Equipment Alarm L2 layer software of FUC does not communicate with BSC for a certain period L2 layer software of FUC does not communicate with BSC for a certain period User deined 1. Check whether other FUCs of this BTS exist this alarm, if so, check E1 line connection and whether BSC's boards such as TIC, LAPD and DSN etc. has fault . If so, identify the fault and solve it. 2. Check the data of BSC, especially T network connection and SMB time slot relay data etc. 3. If LAPD of only one layer TRM breaks, check the line connectiong of back panel then. 4. If LAPD of only one TRM breaks, reset FUC then. 5. If the problem still exists, please replace TRM module. 198087221 Communication between CMM and FUC breaks (communication) (BTS V2) Alarm Property Probable Cause 142 � Alarm Code:198087221 � Severity:Minor � � Description:Communication between CMM and FUC breaks (communication) (BTS V2) Alarm Type:Equipment Alarm HDLC link between CMM and TPU breaks, or CMM hardware has error, etc. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Speciic Problem System Impact Handling Suggestion HDLC link between CMM and TPU breaks, or CMM hardware has error, etc. User deined 1. System keeps running, but no data coniguration could be processed. If only TPU link long-time breaks, user can exclude the problem through following method: 1. Check whether TPU board is tightly inserted. 2. Reset TPU board and check alarm status. 3. Check whether CMM board works properly. 4. Check address switch on the panel board. 5. Check whether the transimission line on the panel board is connected properly. 6. Judge whether it is software problem or harware problem through HW self-loop test, if it's hardware error, replace corresponding modules and if it is software problem, correct and upgrade software version. 198087222 CIP of TPU initialization failure Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087222 � Severity:Minor � � Description:CIP of TPU initialization failure Alarm Type:Equipment Alarm DSP software or hardware has error. DSP software or hardware has error. User deined 1. Download software of this DSP again. 2. Reset TRM shelf, restart DSP unit and check whether the alarm restores. If yes, the DSP initialization error is gennerally induced by exterior strong disturbance, and the TRM unit can still work normally; if the alarm doesn't restore, replace TRM module then. Conidential and Proprietary Information of ZTE CORPORATION 143 ZXG10 iBSC Alarm Handling Reference 198087223 Wrong parameter configuration for CIP Alarm Property � Alarm Code:198087223 � Severity:Minor � � Description:Wrong parameter coniguration for CIP Alarm Type:Equipment Alarm Probable Cause Parameter coniguration has error or conilcts occur. System Impact User deined Speciic Problem Handling Suggestion Parameter coniguration has error or conilcts occur. 1. Check software conigured parameters (frenquncy, mode, static power level), conigure parmeters again from background and synchronize them to BTS. 2. If above method doesn’t work, replace TRM module in time. 198087224 Watchdog of TPU CIP overflow Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion 144 � Alarm Code:198087224 � Severity:Minor � � Description:Watchdog of TPU CIP overlow Alarm Type:Equipment Alarm DSP program of demodulation module has no response temporarily DSP program of demodulation module has no response temporarily User deined Reset this CU irst, and check whether the alarm restores. If yest, the alarm is induced by DSP interior abnormal condition, and the CU could work normally after resetting resumes. If resetting doesn’t help on the alarm, replace TRM module. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198087225 Software version of CIP mismatch Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion Alarm Property � Alarm Code:198087225 � Severity:Minor � � Description:Software version of CIP mismatch Alarm Type:Equipment Alarm CIP software version load error. If one of the carriers is conigured as BCCH, then the whole cell can not work normally. CIP software version load error. If one of the carriers is conigured as BCCH, then the whole cell can not work normally. User deined Reset TRM, if it is of no effect, please replace TRM module. 198087226 Clock alarm for TPU and CMM � Alarm Code:198087226 � Severity:Major � � Description:Clock alarm for TPU and CMM Alarm Type:Equipment Alarm Probable Cause Clock between TPU and CMM is disconnected System Impact User deined Speciic Problem Handling Suggestion Clock between TPU and CMM is disconnected 1. If only this TPU alarms in the BTS, check whether rear board line is connected properly, if yes, replace TRM. 2. If other TPUs also have such alarm, check whether CMM board of the BTS has clock alarm, if yes, replace CMM. 198087227 TPU power alarm(BTS V2) Alarm Property � Alarm Code:198087227 � Severity:Major � Description:TPU power alarm(BTS V2) Conidential and Proprietary Information of ZTE CORPORATION 145 ZXG10 iBSC Alarm Handling Reference � Alarm Type:Equipment Alarm Probable Cause The power module on TPU board has alarm System Impact User deined Speciic Problem Handling Suggestion Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion The power module on TPU board has alarm Please replace TRM. 198087228 TPU frame No. alarm � Alarm Code:198087228 � Severity:Minor � � Description:TPU frame No. alarm Alarm Type:Equipment Alarm Frame clock FCLK has fault, or the frame numbers of CMM has problem. Frame clock FCLK has fault, or the frame numbers of CMM has problem. User deined 1. Check whether FCLK of each frame number generating point is normal (if it is directly transported, check if the wave shape of clock frequency distorts; if it is produced by phase lock, check whether there is lock lost alarm), if not, replace TRM module then. 2. Check transmission link (transmission clock, interface chip and bit error ratio size). 3. Check whether the synchronization source of upper-level frame number exists alarm. 198087229 TPU CHP DSP0 initialization failure Alarm Property Probable Cause Speciic Problem 146 � Alarm Code:198087229 � Severity:Minor � � Description:TPU CHP DSP0 initialization failure Alarm Type:Equipment Alarm DSP software or hardware has error. DSP software or hardware has error. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm System Impact Handling Suggestion The 16 channeds which affect dual-carrier doesn't work properly. If this DTRU is conigured as BCCH, the whole cell service is affected. 1. Re-download the software of this DSP. 2. Reset DTRU shelf and restart DSP, watch if alarm recovers. 3. Check whether environment temperature exceeds the allowable operating enviroment temperature of equipment. If so, adjust the environment; if not, re-plug the board and check whether alarm restores. 4. If the alarm doesn't restore, replace corresponding DTRU then. 198087230 ADC resource unavailable Alarm Property � Alarm Code:198087230 � Severity:Minor � � Description:ADC resource unavailable Alarm Type:Equipment Alarm Probable Cause AD6650 resource is not available. System Impact The TRM/DTRU with fault is not available. If this TRM/DTRU is conigured as BCCH, the whole cell performance is affected. Speciic Problem Handling Suggestion AD6650 resource is not available. 1. Reset this module and make it work properly. 2. Check whether environment temperature exceeds the allowable operating enviroment temperature of equipment. If yes, adjust the environment; if not, re-plug the board and check whether alarm restores. 3. If the alarm doesn't restore, replace corresponding DTRU then. 198087231 CHP frame numbers has fault. Alarm Property Probable Cause � Alarm Code:198087231 � Severity:Minor � � Description:CHP frame numbers has fault. Alarm Type:Equipment Alarm Frame clock FCLK has fault, and the frame numbers of FUC has fault. Conidential and Proprietary Information of ZTE CORPORATION 147 ZXG10 iBSC Alarm Handling Reference Speciic Problem System Impact Handling Suggestion Frame clock FCLK has fault, and the frame numbers of FUC has fault. This DTRU cannot work. If this DTRU is conigured as BCCH, the whole cell service is affected. 1. Reset this module and make it work well. 2. Check whether environment temperature exceeds the allowable operating enviroment temperature of equipment. If so, adjust the environment; if not, re-plug the board and check whether alarm restores. 3. If the alarm doesn't restore, replace corresponding DTRU then. 198087232 BURST interruption error Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087232 � Severity:Minor � � Description:BURST interruption error Alarm Type:Equipment Alarm BURST interruption has problem, and the synchronization source of upper-level BURST has problem BURST interruption has problem, and the synchronization source of upper-level BURST has problem This DTRU cannot work. If this DTRU is conigured as BCCH, the whole cell service is affected. Check whether the clock of BURST interruption generateing point is normal. If not, replace DTRU in time. 198087233 TPU FLASH memory failure Alarm Property Probable Cause Speciic Problem 148 � Alarm Code:198087233 � Severity:Minor � � Description:TPU FLASH memory failure Alarm Type:Equipment Alarm There are two many times of FLASH programming, read/wirte errors or software calibration errors. There are two many times of FLASH programming, read/wirte errors or software calibration errors. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm System Impact Handling Suggestion The Baseband Processing Unit (BPU) cannot get correct software version from FLASH MEMORY, the whole DTRU doesn't work properly. Reset this CU irst, and check whether the alarm restores. If so, the alarm is iresult from CPU reading FLASH MEMORY data which caused by exterior disturbances, and the CU could work normally after resetting . If resetting doesn’t restore the alarm, replace TRM module then. 198087234 TPU CHP DSP0 watchdog overflow Alarm Property � Alarm Code:198087234 � Severity:Minor � � Description:TPU CHP DSP0 watchdog overlow Alarm Type:Equipment Alarm Probable Cause Channel processing unit DSP0 has no response temporarily System Impact DSP0 of Channel Processing Unit (CPU) has no response temporarily, and the control unit reload software and reinitialize the DSP. If the alarm doesn’t restore, it indicates that the software loading on DSP fails all the time. And the problem causes two channels of one CU not working properly. If it is conigured as BCCH, the whole cell service is affected. Speciic Problem Handling Suggestion Channel processing unit DSP0 has no response temporarily 1. Reset this module and make it work properly. 2. Check whether environment temperature exceeds the allowable operating enviroment temperature of equipment. If yes, adjust the environment; if not, re-plug the board and check whether alarm restores. 3. If the alarm doesn't restore, replace corresponding DTRU then. 198087235 Wrong configuration for TRX Channel 0 Alarm Property � Alarm Code:198087235 � Severity:Warning � � Description:Wrong coniguration for TRX Channel 0 Alarm Type:Equipment Alarm Conidential and Proprietary Information of ZTE CORPORATION 149 ZXG10 iBSC Alarm Handling Reference Probable Cause Parameter coniguration has error or conilcts occur. System Impact Affect channel allocation and normal work. Speciic Problem Handling Suggestion Parameter coniguration has error or conilcts occur. 1. Reset TRX and wait for ten minutes and if alarm still exists, reconigure parameter . 2. Reset TRX, and then wait for 10 minutes to check if alarm restores. 3. Re-plug TRX module, and wait for 10 minutes to check if alarm disappears. 4. Replace corresponding TRX module. 198087236 Wrong configuration of TRX Channel 1 Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087236 � Severity:Warning � � Description:Wrong coniguration of TRX Channel 1 Alarm Type:Equipment Alarm Parameter coniguration has error or conilcts occur. Parameter coniguration has error or conilcts occur. Affect channel allocation and normal work. 1. Reset TRX and wait for ten minutes and if alarm still exists, reconigure parameter . 2. Reset TRX, and then wait for 10 minutes to check if alarm restores. 3. Re-plug TRX module, and wait for 10 minutes to check if alarm disappears. 4. Replace corresponding TRX module. 198087237 Wrong configuration of TRX Channel 2 Alarm Property 150 � � Alarm Code:198087237 Description:Wrong coniguration of TRX Channel 2 Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm � Probable Cause Speciic Problem System Impact Handling Suggestion � Severity:Warning Alarm Type:Equipment Alarm Parameter coniguration has error or conilcts occur. Parameter coniguration has error or conilcts occur. Affect channel allocation and normal work. 1. Reset TRX and wait for ten minutes and if alarm still exists, reconigure parameter . 2. Reset TRX, and then wait for 10 minutes to check if alarm restores. 3. Re-plug TRX module, and wait for 10 minutes to check if alarm disappears. 4. Replace corresponding TRX module. 198087238 Wrong configuration of TRX Channel 3 Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087238 � Severity:Warning � � Description:Wrong coniguration of TRX Channel 3 Alarm Type:Equipment Alarm Parameter coniguration has error or conilcts occur. Parameter coniguration has error or conilcts occur. Affect channel allocation and normal work. 1. Reset TRX and wait for ten minutes and if alarm still exists, reconigure parameter . 2. Reset TRX, and then wait for 10 minutes to check if alarm restores. 3. Re-plug TRX module, and wait for 10 minutes to check if alarm disappears. 4. Replace corresponding TRX module. Conidential and Proprietary Information of ZTE CORPORATION 151 ZXG10 iBSC Alarm Handling Reference 198087239 Wrong configuration of TRX Channel 4 Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087239 � Severity:Warning � � Description:Wrong coniguration of TRX Channel 4 Alarm Type:Equipment Alarm Parameter coniguration has error or conilcts occur. Parameter coniguration has error or conilcts occur. Affect channel allocation and normal work. 1. Reset TRX and wait for ten minutes and if alarm still exists, reconigure parameter . 2. Reset TRX, and then wait for 10 minutes to check if alarm restores. 3. Re-plug TRX module, and wait for 10 minutes to check if alarm disappears. 4. Replace corresponding TRX module. 198087240 Wrong configuration of TRX Channel 5 Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087240 � Severity:Warning � � Description:Wrong coniguration of TRX Channel 5 Alarm Type:Equipment Alarm Parameter coniguration has error or conilcts occur. Parameter coniguration has error or conilcts occur. Affect channel allocation and normal work. 1. Reset TRX and wait for ten minutes and if alarm still exists, reconigure parameter . 2. Reset TRX, and then wait for 10 minutes to check if alarm restores. 3. Re-plug TRX module, and wait for 10 minutes to check if alarm disappears. 4. Replace corresponding TRX module. 152 Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198087241 Wrong configuration of TRX Channel 6 Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087241 � Severity:Warning � � Description:Wrong coniguration of TRX Channel 6 Alarm Type:Equipment Alarm Parameter coniguration has error or conilcts occur. Parameter coniguration has error or conilcts occur. Affect channel allocation and normal work. 1. Reset TRX and wait for ten minutes and if alarm still exists, reconigure parameter . 2. Reset TRX, and then wait for 10 minutes to check if alarm restores. 3. Re-plug TRX module, and wait for 10 minutes to check if alarm disappears. 4. Replace corresponding TRX module. 198087242 Wrong configuration of TRX Channel 7 Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087242 � Severity:Warning � � Description:Wrong coniguration of TRX Channel 7 Alarm Type:Equipment Alarm Parameter coniguration has error or conilcts occur. Parameter coniguration has error or conilcts occur. Affect channel allocation and normal work. 1. Reset TRX and wait for ten minutes and if alarm still exists, reconigure parameter . 2. Reset TRX, and then wait for 10 minutes to check if alarm restores. 3. Re-plug TRX module, and wait for 10 minutes to check if alarm disappears. 4. Replace corresponding TRX module. Conidential and Proprietary Information of ZTE CORPORATION 153 ZXG10 iBSC Alarm Handling Reference 198087243 Cell configuration parameter mismatch Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087243 � Severity:Minor � � Description:Cell coniguration parameter mismatch Alarm Type:Equipment Alarm Cell parameter coniguration is incorrect or conlicts with channel parameters and CIP parameter coniguration Cell parameter coniguration is incorrect or conlicts with channel parameters and CIP parameter coniguration The BTS may not work well. 1. Reset TRX and wait for ten minutes and if alarm still exists, reconigure parameter . 2. Reset TRX, and then wait for 10 minutes to check if alarm restores. 3. Re-plug TRX module, and wait for 10 minutes to check if alarm disappears. 4. Replace corresponding TRX module. 198087244 FUC software version mismatch Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087244 � Severity:Minor � � Description:FUC software version mismatch Alarm Type:Equipment Alarm FUC software version load error. If one of the carriers is conigured as BCCH, then the whole cell can not work normally. FUC software version load error. If one of the carriers is conigured as BCCH, then the whole cell can not work normally. FUC software version load error. If one of the carriers is conigured as BCCH, then the whole cell can not work normally. 1. Reset the TRX, check whether the alarm is recovered. 2. Re-plug the TRX module, check whether the alarm is recovered. 3. Change the corresponding TRX module. 154 Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198087245 CHP software version mismatch Alarm Property � Alarm Code:198087245 � Severity:Minor � � Description:CHP software version mismatch Alarm Type:Equipment Alarm Probable Cause CHP software version loading failed. System Impact CHP DSP cannot work well. If one of carriers is conigured as BCCH, the whole cell cannot work normally. Speciic Problem Handling Suggestion CHP software version loading failed. 1. Reset the TRX, check whether the alarm is recovered. 2. Re-plug the TRX module, check whether the alarm is recovered. 3. Change the corresponding TRX module. 198087246 CU software version mismatch Alarm Property � Alarm Code:198087246 � Severity:Minor � � Description:CU software version mismatch Alarm Type:Equipment Alarm Probable Cause CHP software version loading failed. System Impact CHP DSP cannot work well. If one of carriers is conigured as BCCH, the whole cell cannot work normally. Speciic Problem Handling Suggestion CHP software version loading failed. 1. Reset the TRX, check whether the alarm is recovered. 2. Re-plug the TRX module, check whether the alarm is recovered. 3. Change the corresponding TRX module. Conidential and Proprietary Information of ZTE CORPORATION 155 ZXG10 iBSC Alarm Handling Reference 198087247 HDLC communication link between CMB and FUC broken Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087247 � Severity:Minor � � Description:HDLC communication link between CMB and FUC broken Alarm Type:Equipment Alarm HDLC link between CMB and TPU breaks, or CMB hardware has error, etc. HDLC link between CMB and TPU breaks, or CMB hardware has error, etc. TPU communication has error,and no data can be transmissed between TPU and CMB. Data coniguration for FUC, CHP and CIP cannot be inished and their states can not be reported. 1. Check whether DTRU is plugged tightly and properly. Re-plug DTRU module, add DTRU in corresponding position according to the coniguration, and check whether the alarm is recovered. 2. Reset DTRU board to check whether the alarm is recovered. 3. If alarms occur in all the cells, check whether CMB board works normally. Re-plug CMB to check whether the alarm is recovered. 4. Check whether the address switch on the backboard is correct. If not, adjust the switch to correct position, and check whether the alarm is recovered. 5. Check whether the transmission line of the rear board is connected correctly. Otherwise connect the line to correct position and check whether the alarm is recovered. 198087248 LAPD communication link between FUC and BSC broken Alarm Property � Alarm Code:198087248 � Severity:Minor � � 156 Description:LAPD communication link between FUC and BSC broken Alarm Type:Equipment Alarm Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Probable Cause Speciic Problem System Impact Handling Suggestion L2 layer software of FUC does not communicate with BSC for a certain period L2 layer software of FUC does not communicate with BSC for a certain period The FUC doesn’t work porperly. And if the FUC is conigured as BCCH-TPU, the whole cell service is affected. 1. Check whether other FUCs have alarm in the BTS, if all FUCs inside the base station have alarm, check whether E1 line is connected correctly and whether TIC board, LAPD board and DSN board etc.in the BSC have alarms. if yes, dig out the problem and resolve it. 2. Check whether BSC data coniguration is correct or not, especially the T net link and the time slot link of SMB data etc. 3. If only one layer of TRM LAPD breaks, then check whether rear board line is connected correctly. 4. If only one TRM/DTRU LAPD breaks, reset the FUC and check whether alarm restores. 5. If the problem still exists, replace TRM/DTRU module then. 198087249 CU initialization failure Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087249 � Severity:Minor � � Description:CU initialization failure Alarm Type:Equipment Alarm DSP software or hardware has error. DSP software or hardware has error. Modulator doesn’t work at all. And if the DTRU is conigured as BCCH, the whole cell cannot work normally. 1. Reset this module and make it work properly. 2. Check whether environment temperature exceeds the allowable operating enviroment temperature of equipment. If so, adjust the environment; if not, re-plug the board and check whether alarm restores. 3. If the alarm doesn't restore, replace corresponding DTRU then. Conidential and Proprietary Information of ZTE CORPORATION 157 ZXG10 iBSC Alarm Handling Reference 198087250 CU parameter configuration error Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087250 � Severity:Minor � � Description:CU parameter coniguration error Alarm Type:Equipment Alarm Parameter coniguration has error or conilcts occur. Parameter coniguration has error or conilcts occur. DTRU can't work normally. 1. Check software conigured parameters (frenquncy, mode, static power level), conigure parmeters again from background and synchronize them to BTS. 2. If above method doesn’t work, replace TRM module in time. 198087252 TPU power alarm Alarm Property � Alarm Code:198087252 � Severity:Major � � Description:TPU power alarm Alarm Type:Equipment Alarm Probable Cause The power module on TPU board has alarm System Impact This DTRU doesn’t work at all. If this DTRU is conigured as BCCH, the whole cell service is affected. Speciic Problem Handling Suggestion The power module on TPU board has alarm 1. Reset this module and make it work properly. 2. Check whether environment temperature exceeds the allowable operating enviroment temperature of equipment. If so, adjust the environment; if not, re-plug the board and check whether alarm restores. 3. If the alarm doesn't restore, replace corresponding DTRU then. 158 Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198087253 FU frame number error alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087253 � Severity:Minor � � Description:FU frame number error alarm Alarm Type:Equipment Alarm Frame clock FCLK has problem, upper-level frame number synchronization source CMB has problem Frame clock FCLK has problem, upper-level frame number synchronization source CMB has problem This DTRU doesn’t work at all. If this DTRU is conigured as BCCH, the whole cell service is affected. 1. Check whether FCLK of each frame number generateing point is normal. If it is directly transported, check if the frequency and wave shape of the clock distorts; if it is produced by phase lock, check whether there is lock lost alarm. If FCLK has malfunction, replace TRM module then. 2. Check transportation link. That is to check whether transportation clock is normal, interface chip alarms or bit error ratio size suits. 3. Check whether the synchronization source of upper-level frame number exists alarm. 198087254 Rx Local Oscillator (LO) PLL1 lost lock alarm Alarm Property � Alarm Code:198087254 � Severity:Minor � � Description:Rx Local Oscillator (LO) PLL1 lost lock alarm Alarm Type:Equipment Alarm Probable Cause Clock signal is unstable or TRM Phase-Locked Loop (PLL) has fault. System Impact User deined Speciic Problem Handling Suggestion Clock signal is unstable or TRM Phase-Locked Loop (PLL) has fault. 1. Check whether there is clock alarm through LMT and replace corresponding module if alarm exists. If not exists, check whether TP interface 13M clock of the front panel outputs data, if no output, the problem turns to be clock error from TPU to RCU and replace TRM/DTRM module then. Conidential and Proprietary Information of ZTE CORPORATION 159 ZXG10 iBSC Alarm Handling Reference 2. If problem still exists, it may be credited with LO error, replace TRM/DTRM in time then. 198087255 Rx Local Oscillator (LO) PLL2 lose lock alarm Alarm Property � Alarm Code:198087255 � Severity:Minor � � Description:Rx Local Oscillator (LO) PLL2 lose lock alarm Alarm Type:Equipment Alarm Probable Cause Clock signal is unstable or TRM Phase-Locked Loop (PLL) has fault. System Impact User deined Speciic Problem Handling Suggestion Clock signal is unstable or TRM Phase-Locked Loop (PLL) has fault. 1. Observe whether there is clock alarm through LMT and replace corresponding module if alarm exists. If not exists, check whether TP interface 13M clock of the front panel outputs data, if no output, the problem turns to be clock error from TPU to RCU and replace TRM/DTRM module then. 2. If problem still exists, it may be credited with LO error, replace TRM/DTRM in time then. 198087256 Tx Local Oscillator (LO) PLL1 lose lock alarm Alarm Property Probable Cause � Alarm Code:198087256 � Severity:Minor � � Description:Tx Local Oscillator (LO) PLL1 lose lock alarm Alarm Type:Equipment Alarm Clock signal is unstable or TRM Phase-Locked Loop (PLL) has fault. Speciic Problem Clock signal is unstable or TRM Phase-Locked Loop (PLL) has fault. Handling Suggestion 1. Observe whether there is clock alarm through LMT and replace corresponding module if alarm exists. If not exists, check whether TP interface 13M clock of the front panel outputs data, System Impact 160 User deined Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm if no output, the problem turns to be clock error from TPU to RCU and replace TRM/DTRM module then. 2. If problem still exists, it may be credited with LO error, replace TRM/DTRM in time then. 198087257 Tx Local Oscillator (LO) PLL2 lose lock alarm Alarm Property Probable Cause � Alarm Code:198087257 � Severity:Minor � � Description:Tx Local Oscillator (LO) PLL2 lose lock alarm Alarm Type:Equipment Alarm Clock signal is unstable or TRM Phase-Locked Loop (PLL) has fault. Speciic Problem Clock signal is unstable or TRM Phase-Locked Loop (PLL) has fault. Handling Suggestion 1. Check whether there is clock alarm through LMT and replace corresponding module if alarm exists. If not exists, check whether TP interface 13M clock of the front panel outputs data, if no output, the problem turns to be clock error from TPU to RCU and replace TRM/DTRM module then. System Impact User deined 2. If problem still exists, it may be credited with LO error, replace TRM/DTRM in time then. 198087258 52M reference clock PLL lose lock alarm Alarm Property � Alarm Code:198087258 � Severity:Minor � � Description:52M reference clock PLL lose lock alarm Alarm Type:Equipment Alarm Probable Cause Clock signal is unstable or TRM Phase-Locked Loop (PLL) has fault. System Impact User deined Speciic Problem Handling Suggestion Clock signal is unstable or TRM Phase-Locked Loop (PLL) has fault. 1. Check whether there is clock alarm through LMT and replace corresponding module if alarm exists. If not exists, check whether TP interface 13M clock of the front panel outputs data, Conidential and Proprietary Information of ZTE CORPORATION 161 ZXG10 iBSC Alarm Handling Reference if no output, the problem turns to be clock error from TPU to RCU and replace TRM/DTRM module then. 2. If problem still exists, it may be credited with LO error, replace TRM/DTRM in time then. 198087259 Tx IF Local Oscillator (LO) PLL lose lock alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087259 � Severity:Minor � � Description:Tx IF Local Oscillator (LO) PLL lose lock alarm Alarm Type:Equipment Alarm Clock signal is unstable or TRM Phase-Locked Loop (PLL) has fault. Clock signal is unstable or TRM Phase-Locked Loop (PLL) has fault. User deined 1. Check whether there is clock alarm through LMT and replace corresponding module if alarm exists. If not exists, check whether TP interface 13M clock of the front panel outputs data, if no output, the problem turns to be clock error from TPU to RCU and replace TRM/DTRM module then. 2. If problem still exists, it may be credited with LO error, replace TRM/DTRM in time then. 198087260 EEPROM resource unavailable alarm Alarm Property Probable Cause Speciic Problem System Impact 162 � Alarm Code:198087260 � Severity:Minor � � Description:EEPROM resource unavailable alarm Alarm Type:Equipment Alarm EEPROM has fault. EEPROM has fault. User deined Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Handling Suggestion Alarm Property Please replace TRM/DTRM module in time. 198087261 FPGA interface failure � Alarm Code:198087261 � Severity:Minor � � Description:FPGA interface failure Alarm Type:Equipment Alarm Probable Cause Communication between DSP and FPGA interface breaks System Impact User deined Speciic Problem Handling Suggestion Communication between DSP and FPGA interface breaks Please replace TRM/DTRM module in time. 198087262 PA VSWR alarm(BTS V2) Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087262 � Severity:Minor � � Description:PA VSWR alarm(BTS V2) Alarm Type:Equipment Alarm Direct reason: reverse power is too high. Possible reason: open circuit or high resistance exists in output end of PA Direct reason: reverse power is too high. Possible reason: open circuit or high resistance exists in output end of PA User deined 1. Check the connection between PA output and the cable, tighten the connection. 2. If alarm still exists, please replace TRM/DTRM module in time. Conidential and Proprietary Information of ZTE CORPORATION 163 ZXG10 iBSC Alarm Handling Reference 198087263 PA overtemperature minor alarm(BTS V2) Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087263 � Severity:Warning � � Description:PA overtemperature minor alarm(BTS V2) Alarm Type:Equipment Alarm PA temperature is over high, which is possibly induced by PA longtime full power operation, fan long-time shutdown, environmental temperature over high and detecting circuit fault, etc. PA temperature is over high, which is possibly induced by PA longtime full power operation, fan long-time shutdown, environmental temperature over high and detecting circuit fault, etc. User deined 1. Check whether fan works porperly and environmental temperature is over high. 2. If fan works properly and environmental temperature is normal, while PA temperature alarm still exists, the problem turns to be detecting circuit error and keep oberserving. 198087264 PA overtemperature major alarm(BTS V2) Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion 164 � Alarm Code:198087264 � Severity:Minor � � Description:PA overtemperature major alarm(BTS V2) Alarm Type:Equipment Alarm PA temperature is over high, which is possibly induced by PA longtime full power operation, fan long-time shutdown, environmental temperature over high and detecting circuit fault, etc. PA temperature is over high, which is possibly induced by PA longtime full power operation, fan long-time shutdown, environmental temperature over high and detecting circuit fault, etc. User deined 1. Check whether fan works porperly and environmental temperature is over high. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 2. If fan works properly and environmental temperature is normal, while PA temperature alarm still exists, the problem turns to be detecting circuit error and replace TRM/DTRM block in time. 198087265 PA output power alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087265 � Severity:Minor � � Description:PA output power alarm Alarm Type:Equipment Alarm Direct reason: Difference between PA output power and CIP control power is more than 3 db; Possible reason: PA aging, power detecting circuit fault, or detecting threshold too narrow Direct reason: Difference between PA output power and CIP control power is more than 3 db; Possible reason: PA aging, power detecting circuit fault, or detecting threshold too narrow User deined 1. Reset TRM/DTRM and observe. 2. If alarm still exists, replace TRM/DTRM module in time. 198087266 PA power overvoltage Alarm Property � Alarm Code:198087266 � Severity:Minor � � Description:PA power overvoltage Alarm Type:Equipment Alarm Probable Cause PA power is overvoltage. System Impact User deined Speciic Problem Handling Suggestion PA power is overvoltage. Check whether PA detecting circuit has problem, if yes, replace TRM/DTRM module in time. Conidential and Proprietary Information of ZTE CORPORATION 165 ZXG10 iBSC Alarm Handling Reference 198087267 PA power is undervoltage . Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087267 � Severity:Minor � � Description:PA power is undervoltage . Alarm Type:Equipment Alarm PA power is undervoltage. PA power is undervoltage. User deined Check whether PA detecting circuit has problem, if so, replace TRM/DTRM module in time. 198087268 Downlink checksum error of DLRC_AL1 Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087268 � Severity:Minor � � Description:Downlink checksum error of DLRC_AL1 Alarm Type:Equipment Alarm There occurs interference in the link between CHP and modulation module. There occurs interference in the link between CHP and modulation module. User deined 1. Check the signal and time sequence between CHP and modulation module. 2. If problem still exists, please replace TRM/DTRM in time. 198087269 DUC chip initialization failure Alarm Property 166 � � Alarm Code:198087269 Description: DUC chip initialization failure Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm � � Severity:Minor Alarm Type:Equipment Alarm Probable Cause DUC chip is not available. System Impact User deined Speciic Problem Handling Suggestion Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion DUC chip is not available. The TRM/DTRM has error, please replace it in time. 198087270 80w PA VSWR alarm � Alarm Code:198087270 � Severity:Minor � � Description:80w PA VSWR alarm Alarm Type:Equipment Alarm Direct reason: reverse power is too high; possible reason: open circuit or high resistance exists at the output end of PA. Direct reason: reverse power is too high; possible reason: open circuit or high resistance exists at the output end of PA. User deined 1. Check the connection of PA output with cable. 2. If alarm still exists,please replace TRM module as soon as possible. 198087271 80w PA 's temperature is a litter high. Alarm Property Probable Cause Speciic Problem System Impact � Alarm Code:198087271 � Severity:Warning � � Description:80w PA 's temperature is a litter high. Alarm Type:Equipment Alarm PA temperature is over high, which is possibly induced by PA longtime full power operation, fan long-time shutdown, environmental temperature over high and detecting circuit fault, etc. PA temperature is over high, which is possibly induced by PA longtime full power operation, fan long-time shutdown, environmental temperature over high and detecting circuit fault, etc. User deined Conidential and Proprietary Information of ZTE CORPORATION 167 ZXG10 iBSC Alarm Handling Reference Handling Suggestion 1. Check whether fan works porperly and environmental temperature is over high. 2. If fan works properly and environmental temperature is normal, while PA temperature alarm still exists, the problem turns to be detecting circuit error and keep oberserving. 198087272 80w PA overtemperature major alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087272 � Severity:Minor � � Description:80w PA overtemperature major alarm Alarm Type:Equipment Alarm PA temperature is over high, which is possibly induced by PA longtime full power operation, fan long-time shutdown, environmental temperature over high and detecting circuit fault, etc. PA temperature is over high, which is possibly induced by PA longtime full power operation, fan long-time shutdown, environmental temperature over high and detecting circuit fault, etc. User deined 1. Check whether fan works porperly and environmental temperature is over high. 2. If fan works properly and environmental temperature is normal, while PA temperature alarm still exists, the problem turns to be detecting circuit error and replace TRM/DTRM block in time. 198087273 80w PA output power alarm Alarm Property Probable Cause 168 � Alarm Code:198087273 � Severity:Minor � � Description:80w PA output power alarm Alarm Type:Equipment Alarm Direct reason: Difference between PA output power and CIP control power is more than 3 db; Possible reason: PA aging, power detecting circuit fault, or detecting threshold too narrow Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Speciic Problem System Impact Handling Suggestion Direct reason: Difference between PA output power and CIP control power is more than 3 db; Possible reason: PA aging, power detecting circuit fault, or detecting threshold too narrow User deined 1. Reset TRM/DTRM and observe. 2. If alarm still exists, replace TRM/DTRM module in time. 198087274 80w PA power overvoltage Alarm Property � Alarm Code:198087274 � Severity:Minor � � Description:80w PA power overvoltage Alarm Type:Equipment Alarm Probable Cause PA power is overvoltage. System Impact User deined Speciic Problem Handling Suggestion PA power is overvoltage. Check whether PA detecting circuit has problem, if yes, replace TRM/DTRM module in time. 198087275 80w PA 's power is undervoltage . Alarm Property � Alarm Code:198087275 � Severity:Minor � � Description:80w PA 's power is undervoltage . Alarm Type:Equipment Alarm Probable Cause PA power is undervoltage System Impact User deined Speciic Problem Handling Suggestion PA power is undervoltage Check whether PA detecting circuit has problem, if yes, replace TRM/DTRM module in time. Conidential and Proprietary Information of ZTE CORPORATION 169 ZXG10 iBSC Alarm Handling Reference 198087276 80w PA not-in-position alarm Alarm Property � Alarm Code:198087276 � Severity:Minor � � Description:80w PA not-in-position alarm Alarm Type:Equipment Alarm Probable Cause PA is not in position. System Impact User deined Speciic Problem Handling Suggestion PA is not in position. Check whether PA detecting circuit has problem, if yes, replace TRM/DTRM module in time. 198087277 TXIF lock is lost. Alarm Property Probable Cause � Alarm Code:198087277 � Severity:Minor � � Description:TXIF lock is lost. Alarm Type:Equipment Alarm Clock signal is unstable or TRM Phase-Locked Loop (PLL) has fault. Speciic Problem Clock signal is unstable or TRM Phase-Locked Loop (PLL) has fault. Handling Suggestion 1. Restart TRX, and if the fault disappears, it indicates there is no fault in DTRU. System Impact The DTRU possibly does not allow callings. 2. Check whether there is signal between pinout 2 and 15 of HW line; if not, replace the HW line and continue testing; if there is still no signal, the problem is possibly caused by CMB fault. Test set-top 13M clock port, and if there is signal, re-plug CMB board, if no signal, it is possibly CMB fault. 3. If the signal test is normal, re-plug this TRX. If fault still exists, replace the faulty TRX slot. And further replace DTRU if the problem continues. 198087278 TPF clock is unlocked. Alarm Property 170 � � Alarm Code:198087278 Description:TPF clock is unlocked. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm � Probable Cause � Severity:Minor Alarm Type:Equipment Alarm Clock signal is unstable or TRM Phase-Locked Loop (PLL) has fault. Speciic Problem Clock signal is unstable or TRM Phase-Locked Loop (PLL) has fault. Handling Suggestion 1. Restart TRX, and if the fault disappears, it indicates there is no fault in DTRU. System Impact The DTRU possibly does not accept callings. 2. Check whether there is signal between pinout 2 and 15 of HW line; if not, replace the HW line and continue testing; if there is still no signal, the problem is possibly caused by CMB fault. Test set-top 13M clock port, and if there is signal, re-plug CMB board, if no signal, it is possibly CMB fault. 3. If the signal test is normal, re-plug this TRX. If fault still exists, replace the faulty TRX slot. And further replace DTRU if the problem continues. 198087279 TXRF lost lock alarm Alarm Property Probable Cause � Alarm Code:198087279 � Severity:Minor � � Description:TXRF lost lock alarm Alarm Type:Equipment Alarm Clock signal is unstable or TRM Phase-Locked Loop (PLL) has fault. Speciic Problem Clock signal is unstable or TRM Phase-Locked Loop (PLL) has fault. Handling Suggestion 1. Restart TRX, and if the fault disappears, it indicates there is no fault in DTRU. System Impact The DTRU possibly does not allow callings. 2. Check whether there is signal between pinout 2 and 15 of HW line; if not, replace the HW line and continue testing; if there is still no signal, the problem is possibly caused by CMB fault. Test set-top 13M clock port, and if there is signal, re-plug CMB board, if no signal, it is possibly CMB fault. 3. If the signal test is normal, re-plug this TRX. If fault still exists, replace the faulty TRX slot. And further replace DTRU if the problem continues. Conidential and Proprietary Information of ZTE CORPORATION 171 ZXG10 iBSC Alarm Handling Reference 198087280 RXRF clock is unlocked . Alarm Property � Alarm Code:198087280 � Severity:Minor � � Description:RXRF clock is unlocked . Alarm Type:Equipment Alarm Probable Cause Clock signal is unstable or TRM Phase-Locked Loop (PLL) has fault. System Impact The DTRU possibly does not accept callings Speciic Problem Handling Suggestion Clock signal is unstable or TRM Phase-Locked Loop (PLL) has fault. 1. Check whether this alarm restores after resetting the DTRU 2. If this problem still exists, replace DTRU then. 198087281 13 MHz clock is lost. Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087281 � Severity:Minor � � Description:13 MHz clock is lost. Alarm Type:Equipment Alarm 13 MHz clock's receiving is abnormal, 13 MHz clock unit works abnormally. 13 MHz clock's receiving is abnormal, 13 MHz clock unit works abnormally. The DTRU possibly does not accept callings. 1. Restart TRX, and if the fault disappears, it indicates there is no fault in DTRU. 2. Check whether there is signal between pinout 2 and 15 of HW line; if not, replace the HW line and continue testing; if there is still no signal, the problem is possibly caused by CMB fault. Test set-top 13M clock port, and if there is signal, re-plug CMB board, if no signal, it is possibly CMB fault. 3. If the signal test is normal, re-plug this TRX. If fault still exists, replace the faulty TRX slot. And further replace DTRU if the problem continues. 172 Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198087282 60ms synchronous clock lost alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087282 � Severity:Minor � � Description:60ms synchronous clock lost alarm Alarm Type:Equipment Alarm 60ms synchronous clock receiving is abnormal, or 60ms synchronous clock unit work abnormally. 60ms synchronous clock receiving is abnormal, or 60ms synchronous clock unit work abnormally. The DTRU possibly does not allow callings. 1. Check the coniguration, and if there are excessive standby racks conigured, ignore this alarm. 2. Check whether 60ms cable is connected properly or damaged. Reconnect or replace the 60ms cable to check if the alarm restores. 3. Check wheather the CMB of standby rack works properly. If not, recover CMB working status and check whether the alarm restores. 198087283 8M clock of HW is lost. Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087283 � Severity:Minor � � Description:8M clock of HW is lost. Alarm Type:Equipment Alarm HW 8M clock receiving is abnormal, or HW 8M clock unit works abnormally. HW 8M clock receiving is abnormal, or HW 8M clock unit works abnormally. The DTRU possibly does not allow callings. 1. Check whether HW cable is connected abnormally. If so, adjust the cable to check whether the alarm is recovered. 2. If the alarm occurs in all cells, re-plug CMB and power on again, and check whether the alarm is recovered. If the alarm only occurs in certain cells, please take following steps for these cells. Conidential and Proprietary Information of ZTE CORPORATION 173 ZXG10 iBSC Alarm Handling Reference 3. Re-power on the TRX to check whether the alarm is recovered. 4. Re-plug the TRX to check whether the alarm is recovered. 5. Check whether the backboard socket which corresponds to the TRX is abnormal. If so, replace the backboard. 198087284 HW 8K synchronous signal is lost . Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087284 � Severity:Minor � � Description:HW 8K synchronous signal is lost . Alarm Type:Equipment Alarm HW 8K synchronous signal receiving is abnormal, or synchronous signal unit works abnormally. HW 8K synchronous signal receiving is abnormal, or synchronous signal unit works abnormally. HW 8K synchronous signal receiving is abnormal, or synchronous signal unit works abnormally. 1. Check whether HW cable is connected abnormally. If so, adjust the cable to check whether the alarm is recovered. 2. If the alarm occurs in all cells, re-plug CMB and power on again, and check whether the alarm is recovered. If the alarm only occurs in certain cells, please take following steps for these cells. 3. Re-power on the TRX to check whether the alarm is recovered. 4. Re-plug the TRX to check whether the alarm is recovered. 5. Check whether the backboard socket which corresponds to the TRX is abnormal. If so, replace the backboard. 198087285 RF board 52MHz clock lost alarm Alarm Property � Alarm Code:198087285 � Severity:Minor � � 174 Description:RF board 52MHz clock lost alarm Alarm Type:Equipment Alarm Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Probable Cause Speciic Problem System Impact Handling Suggestion RF board 52MHz clock receiving is abnormal, or RF board 52MHz clock unit works abnormally. RF board 52MHz clock receiving is abnormal, or RF board 52MHz clock unit works abnormally. The DTRU possibly does not allow callings. 1. Restart TRX, and if the fault disappears, it indicates there is no fault in DTRU. 2. Check whether there is signal between pinout 2 and 15 of HW line; if not, replace the HW line and continue testing; if there is still no signal, the problem is possibly caused by CMB fault. Test set-top 13M clock port, and if there is signal, re-plug CMB board, if no signal, it is possibly CMB fault. 3. If the signal test is normal, re-plug this TRX. If fault still exists, replace the faulty TRX slot. And further replace DTRU if the problem continues. 198087286 First ADC clock is lost. Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087286 � Severity:Minor � � Description:First ADC clock is lost. Alarm Type:Equipment Alarm AD6650 clock receiving is anormal, or AD6650 clock unit works abnormally. AD6650 clock receiving is anormal, or AD6650 clock unit works abnormally. The DTRU possibly does not accept callings. 1. Restart TRX, and if the fault disappears, it indicates there is no fault in DTRU. 2. Check whether there is signal between pinout 2 and 15 of HW line; if not, replace the HW line and continue testing; if there is still no signal, the problem is possibly caused by CMB fault. Test set-top 13M clock port, and if there is signal, re-plug CMB board, if no signal, it is possibly CMB fault. 3. If the signal test is normal, re-plug this TRX. If fault still exists, replace the faulty TRX slot. And further replace DTRU if the problem continues. Conidential and Proprietary Information of ZTE CORPORATION 175 ZXG10 iBSC Alarm Handling Reference 198087287 Second ADC clock is lost. Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087287 � Severity:Minor � � Description:Second ADC clock is lost. Alarm Type:Equipment Alarm AD6650 clock receiving is anormal, or AD6650 clock unit works abnormally. AD6650 clock receiving is anormal, or AD6650 clock unit works abnormally. The DTRU possibly does not allow callings. 1. Restart TRX, and if the fault disappears, it indicates there is no fault in DTRU. 2. Check whether there is signal between pinout 2 and 15 of HW line; if not, replace the HW line and continue testing; if there is still no signal, the problem is possibly caused by CMB fault. Test set-top 13M clock port, and if there is signal, re-plug CMB board, if no signal, it is possibly CMB fault. 3. If the signal test is normal, re-plug this TRX. If fault still exists, replace the faulty TRX slot. And further replace DTRU if the problem continues. 198087288 PA power is overvoltage. Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion 176 � Alarm Code:198087288 � Severity:Minor � � Description:PA power is overvoltage. Alarm Type:Equipment Alarm PA power is overvoltage. PA power is overvoltage. PA is possibly damaged, and modulation module protectively turns off power output. Check whether PA detection circuit breaks down. If yes, replace DTRU in time. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198087289 PA power is undervoltage. Alarm Property � Alarm Code:198087289 � Severity:Minor � � Description:PA power is undervoltage. Alarm Type:Equipment Alarm Probable Cause PA power is undervoltage. System Impact Output power is abnormal. Speciic Problem Handling Suggestion PA power is undervoltage. Check whether PA detection circuit breaks down. If so, replace DTRU in time. 198087290 PA VSWR alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087290 � Severity:Minor � � Description:PA VSWR alarm Alarm Type:Equipment Alarm Direct reason: reverse power is too high. Possible reason: open circuit or high resistance exists in output end of PA Direct reason: reverse power is too high. Possible reason: open circuit or high resistance exists in output end of PA This DTRU does not allow callings at all, PA is damaged. 1. Reset DTRU and check whether alarm restores. 2. Replace RF cable from DTRU to AEM and check whether this alram restores. 3. If this problem still exists, replace DTRU then. 198087291 PA temperature is a little high. (TRX level alarm, exceeds 80℃) Alarm Property � � Alarm Code:198087291 Description:PA temperature is a little high. (TRX level alarm, exceeds 80℃) Conidential and Proprietary Information of ZTE CORPORATION 177 ZXG10 iBSC Alarm Handling Reference � Probable Cause Speciic Problem System Impact Handling Suggestion � Severity:Warning Alarm Type:Equipment Alarm PA temperature is over high, which is possibly result from PA longtime full power operation, fan long-time shutdown, environmental temperature over high and detecting circuit fault, etc. PA temperature is over high, which is possibly result from PA longtime full power operation, fan long-time shutdown, environmental temperature over high and detecting circuit fault, etc. The DTRU still works, but PA aging speed accelerates. 1. heck whether fan works well. If so, turn to step 2; if not, correct the error and check whether alarm restores. 2, Check whether environmental temperature is over high. If not, turn to step 3; if so, improve equipment room environment and check whether alarm restores. 3. Reset TRX and check alarm status. 4. May be it is result from Detection circuit failure, in this case ,replace the TRX then. 198087292 PA temperature is much more higher. (TRX level alarm, exceeds 95 ℃) Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion 178 � Alarm Code:198087292 � Severity:Minor � � Description:PA temperature is much more higher. (TRX level alarm, exceeds 95 ℃) Alarm Type:Equipment Alarm PA temperature is over high, which is possibly result from PA longtime full power operation, fan long-time shutdown, environmental temperature over high and detecting circuit fault, etc. PA temperature is over high, which is possibly result from PA longtime full power operation, fan long-time shutdown, environmental temperature over high and detecting circuit fault, etc. Power output of this DTRU is terminated for protection, and PA aging speed accelerates. 1. heck whether fan works well. If so, turn to step 2; if not, correct the error and check whether alarm restores. 2, Check whether environmental temperature is over high. If not, turn to step 3; if so, improve equipment room environment and check whether alarm is recovered. 3. Reset TRX and check alarm status. 4. May be it is result from Detection circuit failure, in this case ,replace the TRX then. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198087293 PA forward power(3db) alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087293 � Severity:Minor � � Description:PA forward power(3db) alarm Alarm Type:Equipment Alarm Direct reason: Difference between PA output power and CHP control power is more than 3 db; Possible reason: PA aging, power detecting circuit fault, detecting threshold too narrow Direct reason: Difference between PA output power and CHP control power is more than 3 db; Possible reason: PA aging, power detecting circuit fault, detecting threshold too narrow The DTRU possibly does not allow callings, and power control is out of control, etc. 1. Reset DTRU and check whether alarm restores. 2. Replace RF cable from DTRU to AEM and check whether this alram restores. 3. If this problem still exists, replace DTRU then. 198087294 RTU power is abnormal. Alarm Property � Alarm Code:198087294 � Severity:Major � � Description:RTU power is abnormal. Alarm Type:Equipment Alarm Probable Cause Power module on the RTU board has alarm. System Impact The DRM/DTRM cannot work, if it is conigured as BCCH, whole cell service is affected. Speciic Problem Power module on the RTU board has alarm. Conidential and Proprietary Information of ZTE CORPORATION 179 ZXG10 iBSC Alarm Handling Reference Handling Suggestion Replace the RTU circuit board as quickly as possible 198087295 The temperature of RTU power is too high. Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087295 � Severity:Minor � � Description:The temperature of RTU power is too high. Alarm Type:Equipment Alarm RTU temperature is over high, which is possibly result from RTU long-time full power operation, fan long-time shutdown, environmental temperature over high and detecting circuit fault, etc. RTU temperature is over high, which is possibly result from RTU long-time full power operation, fan long-time shutdown, environmental temperature over high and detecting circuit fault, etc. Power output of this TRM/DTRU is terminated for protection, and RTU aging speed accelerates. 1. Check whether fan works well and environmental temperature is over high. 2. If fan works well and environmental temperature is normal but RTU temperature alarm still exists, the problem may be result from detecting circuit error. 198087296 The output of RTU power is overvoltage. Alarm Property Alarm Code:198087296 � Severity:Major � � Description:The output of RTU power is overvoltage. Alarm Type:Equipment Alarm Probable Cause RTU power output is overvoltage. System Impact RTU can't work well. Speciic Problem 180 � RTU power output is overvoltage. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Handling Suggestion Alarm Property Replace the RTU board. 198087297 RTU power input abnormal alarm � Alarm Code:198087297 � Severity:Major � � Description:RTU power input abnormal alarm Alarm Type:Equipment Alarm Probable Cause RTU power input exceeds adjustment range. System Impact RTU can't work well. Speciic Problem Handling Suggestion RTU power input exceeds adjustment range. Replace the RTU board. 198087298 IQ calibration parameters are abnormal. Alarm Property � Alarm Code:198087298 � Severity:Major � � Description:IQ calibration parameters are abnormal. Alarm Type:Equipment Alarm Probable Cause IQ calibration parameter is abnormal. System Impact The whole board of RTU are paralyzed. Speciic Problem Handling Suggestion IQ calibration parameter is abnormal. Replace the RTU board. 198087299 EAM heat exchanger alarm. Alarm Property � Alarm Code:198087299 � Severity:Warning � � Description:EAM heat exchanger alarm. Alarm Type:Equipment Alarm Conidential and Proprietary Information of ZTE CORPORATION 181 ZXG10 iBSC Alarm Handling Reference Probable Cause Speciic Problem System Impact Handling Suggestion Heat exchanger triggers alarm, which is reported by node of heat exchanger. Heat exchanger triggers alarm, which is reported by node of heat exchanger. Device's safety is affected. 1. Check the connection between EAM and heat exchanger, if connect right, to step2 . 2. Check whether heat exchanger provide power normally, if power right, to step 3. Replace the heat exchanger. 198087300 CMB0 heating film alarm. Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087300 � Severity:Warning � � Description: CMB0 heating ilm alarm. Alarm Type:Equipment Alarm CMB0 heating ilm has error. CMB0 heating ilm has error. Device low-temperature start up is affected. 1. Check whether CMB0 heating ilm is powered properly. 2. Check if heating ilm is damaged. If yes, replace CMB0 heating ilm. 198087301 CMB1 heating film alarm Alarm Property Probable Cause Speciic Problem System Impact 182 � Alarm Code:198087301 � Severity:Warning � � Description: CMB1 heating ilm alarm Alarm Type:Equipment Alarm CMB1 heating ilm has error. CMB1 heating ilm has error. Device starting up with low-temperature is affected. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Handling Suggestion 1. Check whether CMB1 heating ilm is powered properly. 2. Check if heating ilm is damaged. If yes, replace CMB1 heating ilm. 198087302 EAM has had smoke . Alarm Property � Alarm Code:198087302 � Severity:Minor � � Description:EAM has had smoke . Alarm Type:Equipment Alarm Probable Cause Device smoke results in alarm. System Impact Device's operation safety is affected. Speciic Problem Handling Suggestion Device smoke results in alarm. Perform onsite check immdiately to ind the root cause and check whether there occurs ire. After addressing the problem, reset EAM board and clear smoke alarm. 198087303 EAM has had water. Alarm Property � Alarm Code:198087303 � Severity:Minor � � Description:EAM has had water. Alarm Type:Equipment Alarm Probable Cause Water intrusion of device results in alarm. System Impact Device's operation safety is affected. Speciic Problem Water intrusion of device results in alarm. Conidential and Proprietary Information of ZTE CORPORATION 183 ZXG10 iBSC Alarm Handling Reference Handling Suggestion Check immediately to ind reason and handle the fault. 198087304 EAM lightning protection alarm. Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087304 � Severity:Minor � � Description:EAM lightning protection alarm. Alarm Type:Equipment Alarm Lightning protector fails and results in alarm. Lightning protector fails and results in alarm. Device's operation safety is affected. 1. Check whether lightening protector connection interface is connected well. 2. Check whether lightening protector is damaged itself. If so, replace lightening protector. 198087305 EAM backdoor access is intruded. Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion 184 � Alarm Code:198087305 � Severity:Warning � � Description:EAM backdoor access is intruded. Alarm Type:Equipment Alarm Back door is opened and results in alarm. Back door is opened and results in alarm. Affect device safety. Perform onsite check immdiately to check whether backdoor is opened. If so, close the backdoor; if not, check if it is door magnetic problem. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198087306 EAM frontdoor access is intruded. Alarm Property � Alarm Code:198087306 � Severity:Warning � � Description:EAM frontdoor access is intruded. Alarm Type:Equipment Alarm Probable Cause Front door is opened and results in alarm. System Impact Affect device safety. Speciic Problem Handling Suggestion Front door is opened and results in alarm. Perform onsite check immdiately to check whether frontdoor is opened. If so, close the frontdoor; if not, check if it is door magnetic problem. 198087307 EAM PWR monitoring unit has fault. Alarm Property � Alarm Code:198087307 � Severity:Warning � � Description:EAM PWR monitoring unit has fault. Alarm Type:Equipment Alarm Probable Cause PWR monitoring unit results in alarm. System Impact Affect device safety. Speciic Problem Handling Suggestion PWR monitoring unit results in alarm. 1. Check connection line between PWR and EAM. 2. Check whether power monitoring unit is normal. 3. Check if any other alarms exist in the power. 198087308 FIB heating film alarm Alarm Property � Alarm Code:198087308 � Severity:Minor � � Description: FIB heating ilm alarm Alarm Type:Equipment Alarm Conidential and Proprietary Information of ZTE CORPORATION 185 ZXG10 iBSC Alarm Handling Reference Probable Cause FIB heating ilm has error. System Impact Affect device low-temperature start up. Speciic Problem Handling Suggestion FIB heating ilm has error. 1. Check whether FIB heating ilm is powered properly. 2. Check if heating ilm is damaged. If yes, replace FIB heating ilm. 198087309 EAM heat exchanger control board has fault. Alarm Property � Alarm Code:198087309 � Severity:Minor � � Description:EAM heat exchanger control board has fault. Alarm Type:Equipment Alarm Probable Cause Heat exchanger control board triggers alarm. System Impact Affect device operation safety. Speciic Problem Handling Suggestion Heat exchanger control board triggers alarm. 1. Check connection line between EAM and heat exchanger. 2. Check whether heat exchanger is powered normally. 3. Replace heat exchanger control board. 198087310 EAM heat exchanger external circulation fan 2 alarm. Alarm Property Probable Cause Speciic Problem System Impact 186 � Alarm Code:198087310 � Severity:Minor � � Description:EAM heat exchanger external circulation fan 2 alarm. Alarm Type:Equipment Alarm Heat exchanger external circulation fan engine 2 results in alarm. Heat exchanger external circulation fan engine 2 results in alarm. Affect device operation safety. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Handling Suggestion 1. Check connection line between heat exchanger control board and fan. 2. Replace the fan. 198087311 EAM heat exchanger external circulation fan 1 alarm. Alarm Property Probable Cause � Alarm Code:198087311 � Severity:Minor � � Description:EAM heat exchanger external circulation fan 1 alarm. Alarm Type:Equipment Alarm Heat exchanger external circulation fan engine 1 results in alarm. Speciic Problem Heat exchanger external circulation fan engine 1 results in alarm. Handling Suggestion 1. Check connection line between heat exchanger control board and fan. System Impact Affect device operation safety. 2. Replace the fan. 198087312 EAM heat exchanger internal circulation fan 2 alarm Alarm Property � Alarm Code:198087312 � Severity:Major � � Description:EAM heat exchanger internal circulation fan 2 alarm Alarm Type:Equipment Alarm Probable Cause Heat exchanger internal circulation fan engine 2 triggers alarm. System Impact Affect device operation safety. Speciic Problem Handling Suggestion Heat exchanger internal circulation fan engine 2 triggers alarm. 1. Check connection line between heat exchanger control board and fan. 2. Replace the fan. Conidential and Proprietary Information of ZTE CORPORATION 187 ZXG10 iBSC Alarm Handling Reference 198087313 EAM heat exchanger internal circulation fan 1 alarm. Alarm Property � Alarm Code:198087313 � Severity:Major � � Description:EAM heat exchanger internal circulation fan 1 alarm. Alarm Type:Equipment Alarm Probable Cause Heat exchanger internal circulation fan engine 1 triggers alarm. System Impact Affect device operation safety. Speciic Problem Handling Suggestion Heat exchanger internal circulation fan engine 1 triggers alarm. 1. Check connection line between heat exchanger control board and fan. 2. Replace the fan. 198087314 EAM heat exchanger 's 485 communication has fault. Alarm Property � Alarm Code:198087314 � Severity:Minor � � Description:EAM heat exchanger 's 485 communication has fault. Alarm Type:Equipment Alarm Probable Cause Communication between EAM and heat exchanger breaks. System Impact Affect heat exchanger alarm report. Speciic Problem Handling Suggestion Communication between EAM and heat exchanger breaks. 1. Check connection line between EAM and heat exchanger. 2. Check whether heat exchanger is powered normally. 3. Replace heat exchanger control board. 188 Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198087315 EAM temperature is abnormal. Alarm Property � Alarm Code:198087315 � Severity:Minor � � Description:EAM temperature is abnormal. Alarm Type:Equipment Alarm Probable Cause Device internal environmental temperature is too high. System Impact Affect device operation safety. Speciic Problem Handling Suggestion Device internal environmental temperature is too high. 1. Check whether TRX layer fan processes normally. 2. Check whether heat exchanger works properly. 198087316 EAM TRX layer mixed-flow fan 1 has fault. Alarm Property � Alarm Code:198087316 � Severity:Minor � � Description:EAM TRX layer mixed-low fan 1 has fault. Alarm Type:Equipment Alarm Probable Cause Mixed-low fan engine 1 is damaged. System Impact Affect RTU normal work. Speciic Problem Handling Suggestion Mixed-low fan engine 1 is damaged. 1. Check wheter the connection line between FNIB and fan engine is good. If not, replace the line. 2. Check whether fan engine itself is damaged, if so, replace the fan engine. 198087317 EAM TRX layer mixed-flow fan 2 has fault. Alarm Property � Alarm Code:198087317 � Severity:Minor � � Description:EAM TRX layer mixed-low fan 2 has fault. Alarm Type:Equipment Alarm Conidential and Proprietary Information of ZTE CORPORATION 189 ZXG10 iBSC Alarm Handling Reference Probable Cause Mixed-low fan engine 2 is damaged. System Impact Affect RTU normal work. Speciic Problem Handling Suggestion Mixed-low fan engine 2 is damaged. 1. Check connection line between FNIB and fan engine. And replace the line if it breaks down. 2. Check whether fan engine itself is damaged, if yes, replace the fan engine. 198087318 EAM TRX layer mixed-flow fan 3 has fault. Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087318 � Severity:Minor � � Description:EAM TRX layer mixed-low fan 3 has fault. Alarm Type:Equipment Alarm Mixed-low fan engine 3 is damaged. Mixed-low fan engine 3 is damaged. Affect RTU normal work. 1. Check connection line between FNIB and fan engine. And replace the line if it breaks down. 2. Check whether fan engine itself is damaged, if yes, replace the fan engine. 198087319 Communication is broken between EAM and CMB. Alarm Property Alarm Code:198087319 � Severity:Minor � � Description:Communication is broken between EAM and CMB. Alarm Type:Equipment Alarm Probable Cause Communication between EAM and CMB breaks. System Impact Affect device alarm report. Speciic Problem Handling Suggestion 190 � Communication between EAM and CMB breaks. 1. Check whether EAM is powered on. 2. Check whether CMB works properly. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 3. Replace EAM board or backborad. 198087320 Power undervoltage alarm Alarm Property � Alarm Code:198087320 � Severity:Major � � Description:Power undervoltage alarm Alarm Type:Equipment Alarm Probable Cause Power voltage is lower than normal System Impact User deined Speciic Problem Handling Suggestion Power voltage is lower than normal Restore external power supply as soon as possible 198087321 Inner fan engine 2 alarm (for M8202) Alarm Property � Alarm Code:198087321 � Severity:Warning � � Description:Inner fan engine 2 alarm (for M8202) Alarm Type:Equipment Alarm Probable Cause Fan stops rotating because of some bugs. System Impact Cabinet temperature rises. Speciic Problem Handling Suggestion Fan stops rotating because of some bugs. 1. Check whether corresponding fan engine stops rotating. If yes, replace the fan engine plug-in box; if not, turn to step 2. Check whether the lines of fan engine and fan controller exist fault. If yes, turn to step 3; if not, turn to step 4. 3. Check whether fan engine cable exists fault, and whether board-port connector exists fault. If fan engine cable has malfunction, replace it then. If board-port connector malfunctions, replance fan controller board DFCM/FNCB. 4. Check whether error-detection circuit exists fault. If yes, remove the alarm circuit fault; if not, turn to step 5. Check whether alarm collection of fan controller board is abnormal. If yes, replace fan controller board DFCM/FNCB; if not, turn to step Conidential and Proprietary Information of ZTE CORPORATION 191 ZXG10 iBSC Alarm Handling Reference 6. Check whether TRM/DTRU alarm collection circuit is abnormal. If yes replace corresponding TRM/DTRU. 198087322 Inner fan engine 1 alarm (for M8202) Alarm Property � Alarm Code:198087322 � Severity:Warning � � Description:Inner fan engine 1 alarm (for M8202) Alarm Type:Equipment Alarm Probable Cause Fan stops rotating because of some bugs. System Impact Cabinet temperature rises. Speciic Problem Handling Suggestion Fan stops rotating because of some bugs. 1. Check whether corresponding fan engine stops rotating. If yes, replace the fan engine plug-in box; if not, turn to step 2. Check whether the lines of fan engine and fan controller exist fault. If yes, turn to step 3; if not, turn to step 4. 3. Check whether fan engine cable exists fault, and whether board-port connector exists fault. If fan engine cable has malfunction, replace it then. If board-port connector malfunctions, replance fan controller board DFCM/FNCB. 4. Check whether error-detection circuit exists fault. If yes, remove the alarm circuit fault; if not, turn to step 5. Check whether alarm collection of fan controller board is abnormal. If yes, replace fan controller board DFCM/FNCB; if not, turn to step 6. Check whether TRM/DTRU alarm collection circuit is abnormal. If yes replace corresponding TRM/DTRU. 198087323 Outer fan engine 2 and 4 alarm (for M8202) Alarm Property Probable Cause Speciic Problem 192 � Alarm Code:198087323 � Severity:Warning � � Description:Outer fan engine 2 and 4 alarm (for M8202) Alarm Type:Equipment Alarm Fan stops rotating because of some bugs. Fan stops rotating because of some bugs. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm System Impact Handling Suggestion Cabinet temperature rises. 1. Check whether error-detection circuit has malfunction, if yes, eliminate it. 2. Check whether fan engine has problem, and repair it. 3. Check whether dTPB alarm collection circuit works well or not, if not, replace dTPB board. 198087324 Outer fan engine 1 and 3 alarm (for M8202) Alarm Property � Alarm Code:198087324 � Severity:Warning � � Description:Outer fan engine 1 and 3 alarm (for M8202) Alarm Type:Equipment Alarm Probable Cause Fan stops rotating due to fault System Impact the temperature of rack to arise Speciic Problem Handling Suggestion Fan stops rotating due to fault 1. Check the alarm connection and eliminate the malfunction; 2. Check the fan and maintain the fault; 3. Check the collection system of the dTPB board and replace the wrong one. 198087325 Rack temperature minor alarm Alarm Property � Alarm Code:198087325 � Severity:Warning � � Description:Rack temperature minor alarm Alarm Type:Equipment Alarm Probable Cause Fan fault or module temperature too high System Impact lead to the temperaturn of TRM/DTRU was too high, affect the performance index Speciic Problem Handling Suggestion Fan fault or module temperature too high Check the environment temperature, if the temperature is normal, keep on observing while other modules works normally, otherwise, improve the equipment working conditions. Conidential and Proprietary Information of ZTE CORPORATION 193 ZXG10 iBSC Alarm Handling Reference 198087326 Rack temperature major alarm Alarm Property � Alarm Code:198087326 � Severity:Minor � � Description:Rack temperature major alarm Alarm Type:Equipment Alarm Probable Cause Fan fault or module temperature too high System Impact to make the device broken and affect the performance index Speciic Problem Handling Suggestion Fan fault or module temperature too high Check the environment temperature, if the temperature is normal, keep on observing while other modules works normally, otherwise, improve the equipment working conditions. 198087327 Layer 3 fan 1 alarm (for M8206) Alarm Property � Alarm Code:198087327 � Severity:Warning � � Description:Layer 3 fan 1 alarm (for M8206) Alarm Type:Equipment Alarm Probable Cause The failure of fans System Impact the temperature of rack to arise,affect the performance of work and the working life Speciic Problem Handling Suggestion The failure of fans 1. Examin the error-detection circuit; 2. Examin the fans; 3. Examin the RTU Alarm Collection Circuit, if any fault in it, replace the relevant unit. 198087328 Layer 3 fan 2 alarm (for M8206) Alarm Property 194 � � Alarm Code:198087328 Description:Layer 3 fan 2 alarm (for M8206) Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm � � Severity:Warning Alarm Type:Equipment Alarm Probable Cause The failure of fans System Impact the temperature of rack to arise,affect the performance of work and the working life Speciic Problem Handling Suggestion The failure of fans 1. Examin the error-detection circuit; 2. Examin the fans; 3. Examin the RTU Alarm Collection Circuit, if any fault in it, replace the relevant unit. 198087329 Layer 3 fan 3 alarm (for M8206) Alarm Property � Alarm Code:198087329 � Severity:Warning � � Description:Layer 3 fan 3 alarm (for M8206) Alarm Type:Equipment Alarm Probable Cause The failure of fans System Impact the temperature of rack to arise,affect the performance of work and the working life Speciic Problem Handling Suggestion The failure of fans 1. Examin the error-detection circuit; 2. Examin the fans; 3. Examin the RTU Alarm Collection Circuit, if any fault in it, replace the relevant unit. 198087330 Layer 2 fan 1 alarm (for M8206) Alarm Property Probable Cause Speciic Problem � Alarm Code:198087330 � Severity:Warning � � Description:Layer 2 fan 1 alarm (for M8206) Alarm Type:Equipment Alarm The failure of fans The failure of fans Conidential and Proprietary Information of ZTE CORPORATION 195 ZXG10 iBSC Alarm Handling Reference System Impact Handling Suggestion the temperature of rack to arise,affect the performance of work and the working life 1. Examin the error-detection circuit; 2. Examin the fans; 3. Examin the RTU Alarm Collection Circuit, if any fault in it, replace the relevant unit. 198087331 Layer 2 fan 2 alarm (for M8206) Alarm Property � Alarm Code:198087331 � Severity:Warning � � Description:Layer 2 fan 2 alarm (for M8206) Alarm Type:Equipment Alarm Probable Cause The failure of fans System Impact the temperature of rack to arise,affect the performance of work and the working life Speciic Problem Handling Suggestion The failure of fans 1. Examin the error-detection circuit; 2. Examin the fans; 3. Examin the RTU Alarm Collection Circuit, if any fault in it, replace the relevant unit. 198087332 Layer 2 fan 3 alarm (for M8206) Alarm Property Alarm Code:198087332 � Severity:Warning � � Description:Layer 2 fan 3 alarm (for M8206) Alarm Type:Equipment Alarm Probable Cause The failure of fans System Impact the temperature of rack to arise,affect the performance of work and the working life Speciic Problem Handling Suggestion 196 � The failure of fans 1. Examin the error-detection circuit; 2. Examin the fans; Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 3. Examin the RTU Alarm Collection Circuit, if any fault in it, replace the relevant unit. 198087333 Layer 1 fan 1 alarm (for M8206) Alarm Property � Alarm Code:198087333 � Severity:Warning � � Description:Layer 1 fan 1 alarm (for M8206) Alarm Type:Equipment Alarm Probable Cause The failure of fans System Impact the temperature of rack to arise,affect the performance of work and the working life Speciic Problem Handling Suggestion The failure of fans 1. Examin the error-detection circuit; 2. Examin the fans; 3. Examin the RTU Alarm Collection Circuit, if any fault in it, replace the relevant unit. 198087334 Layer 1 fan 2 alarm (for M8206) Alarm Property � Alarm Code:198087334 � Severity:Warning � � Description:Layer 1 fan 2 alarm (for M8206) Alarm Type:Equipment Alarm Probable Cause The failure of fans System Impact the temperature of rack to arise,affect the performance of work and the working life Speciic Problem Handling Suggestion The failure of fans 1. Examin the error-detection circuit; 2. Examin the fans; 3. Examin the RTU Alarm Collection Circuit, if any fault in it, replace the relevant unit. Conidential and Proprietary Information of ZTE CORPORATION 197 ZXG10 iBSC Alarm Handling Reference 198087335 Layer 1 fan 3 alarm (for M8206) Alarm Property � Alarm Code:198087335 � Severity:Warning � � Description:Layer 1 fan 3 alarm (for M8206) Alarm Type:Equipment Alarm Probable Cause The failure of fans System Impact the temperature of rack to arise,affect the performance of work and the working life Speciic Problem Handling Suggestion The failure of fans 1. Examin the error-detection circuit; 2. Examin the fans; 3. Examin the RTU Alarm Collection Circuit, if any fault in it, replace the relevant unit. 198087340 FR device failure Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087340 � Severity:Minor � � Description:FR device failure Alarm Type:Equipment Alarm N392 errors are detected in the latest N393 STATUS ENQUIRY events. N392 errors are detected in the latest N393 STATUS ENQUIRY events. BRCH of Gb interface is not accessible. 1. Check whether the alarm of E1 port corresponding to this BRCH is persistent. If so, check transmission devices and solve the problem. 2. Do self-loop check to local terminal device and ensure E1 works properly. If the local terminal is abnormal, replace E1 line then and watch whether the alarm disappears; If the local device works normally, then contact SGSN maintenance personnel to do self-loop to ensure that SGSN works properly. If SGSN works normally, go to step 3. Check the coniguration of both BSC and SGSN to ensure that E1 frames have the same format. 4. Check the E1 LED indicator on GIPB board. If it is in normal status, go to step 5; if not, replace the rear board and observe whether the alarm disappears. 198 Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 5. Check whether conigured parameters on BRCH interface are consistent with the corresponding ones in SGSN. If not, modify conigured parameters until they are the same. If consistent, go to step 6. , Replace GIPB board and observe whether the alarm disappears. 198087342 Cell interruption alarm Alarm Property � Alarm Code:198087342 � Severity:Minor � � Description:Cell interruption alarm Alarm Type:Equipment Alarm Probable Cause 1. The site to which the cell belongs is lost. Speciic Problem 1. The site to which the cell belongs is lost. System Impact Handling Suggestion 2. The cell BCCH frequency is faulty. 2. The cell BCCH frequency is faulty. The cell cannot provide any voice or data services. 1. On NMS fault management interface, check if related alarm exists. If yes, follow the instructions of handling related alarms. Related alarm: 198087337 Site Abis control link broken 2. On NMS dynamic data management interface, check if cell state is normal. On Radio Resource Management tab page in this interface, check BTS management, TRX management and TS management. (1) BTS management If manually blocked BTS exists, unblock it. If global reset blocked of the cell, check and rectify A interface faults. (2) TRX management If BCCH of the alarmed cell is manually blocked, unblock TRX. If block induced by Abis control link broken exists, restore the site's Abis control link. If CU or FU operation state of TRX is blocked, check and restore the BTS TRX faults. (3) TS management If BCCH of the alarmed cell is manually blocked, unblock time slot. Conidential and Proprietary Information of ZTE CORPORATION 199 ZXG10 iBSC Alarm Handling Reference 198087361 The CRC calibration of PA parameter turns to be error . Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087361 � Severity:Warning � � Description:The CRC calibration of PA parameter turns to be error . Alarm Type:Equipment Alarm PA parameter calibration has error. PA parameter calibration has error. PA does not have calibration curve, and affect RX indicators. (1) Reset the corresponding TRX and check whether alarm is recovered. (2) Power on the corresponding TRX and check alarm status. (3) Replace TRX. 198087379 OMP reboot alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion 200 � Alarm Code:198087379 � Severity:Major � � Description:OMP reboot alarm Alarm Type:Equipment Alarm This alarm is triggered after OMP board rebooted and recovers immediately. Generally, these alarms could only be queried in history alarm list after they are triggered. This alarm is triggered after OMP board rebooted and recovers immediately. Generally, these alarms could only be queried in history alarm list after they are triggered. This alarm affects the operation and maintenance during OMP malfunction. It has no effect on the services. OMP reports this alarm after rebooting and restores automatically, no handling operations are needed. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198087386 SYNCLK losing lock alarm Alarm Property � Alarm Code:198087386 � Severity:Warning � � Description:SYNCLK losing lock alarm Alarm Type:Equipment Alarm Probable Cause SYNCLK cannot be locked for a long time. System Impact Master and slave CMM/CMB board cannot switch with each other. Speciic Problem Handling Suggestion SYNCLK cannot be locked for a long time. Check whether SYNCLK board on BSC works well. If it works well and slave board exists, switch the master to slave board; if the slave board does not exist, reset the master board then. 198087387 Status of TX1 filter alarm Alarm Property � Alarm Code:198087387 � Severity:Major � � Description:Status of TX1 ilter alarm Alarm Type:Equipment Alarm Probable Cause TX1 channed is not well adjusted or the loss exceeds 5dB. System Impact Radio transmission is affected. Speciic Problem Handling Suggestion TX1 channed is not well adjusted or the loss exceeds 5dB. (1) Reset the corresponding TRX and check whether the alarm restores. (2) Replace FCU and check whether the alarm restores. 198087388 Status of TX2 filter alarm Alarm Property Probable Cause � Alarm Code:198087388 � Severity:Major � � Description:Status of TX2 ilter alarm Alarm Type:Equipment Alarm TX2 channed is not well adjusted or the loss exceeds 5dB. Conidential and Proprietary Information of ZTE CORPORATION 201 ZXG10 iBSC Alarm Handling Reference Speciic Problem System Impact Handling Suggestion TX2 channed is not well adjusted or the loss exceeds 5dB. Radio transmission is affected. (1) Reset the corresponding TRX and check whether the alarm restores. (2) Replace FCU and check whether the alarm restores. 198087389 Status of TX3 filter alarm Alarm Property � Alarm Code:198087389 � Severity:Major � � Description:Status of TX3 ilter alarm Alarm Type:Equipment Alarm Probable Cause TX3 channed is not well adjusted or the loss exceeds 5dB. System Impact Radio transmission is affected. Speciic Problem Handling Suggestion TX3 channed is not well adjusted or the loss exceeds 5dB. (1) Reset the corresponding TRX and check whether the alarm restores. (2) Replace FCU and check whether the alarm restores. 198087390 Status of TX4 filter alarm Alarm Property Alarm Code:198087390 � Severity:Major � � Description:Status of TX4 ilter alarm Alarm Type:Equipment Alarm Probable Cause TX4 channed is not well adjusted or the loss exceeds 5dB. System Impact Radio transmission is affected. Speciic Problem Handling Suggestion 202 � TX4 channed is not well adjusted or the loss exceeds 5dB. (1) Reset the corresponding TRX and check whether the alarm restores. (2) Replace FCU and check whether the alarm restores. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198087391 FCU power undervoltage alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087391 � Severity:Major � � Description:FCU power undervoltage alarm Alarm Type:Equipment Alarm +12V power is undervoltage and triggers alarm. +12V power is undervoltage and triggers alarm. FCU works abnormally. 1. Check whether FCU power LED displays alarm. If yes, turn to step 2; if not, turn to step 3. 2. Check whether FCU corresponding slots' 12V power is normal. If not, replace FCU; otherwise, turn to step 3. Replace FCU, and watch whether the alarm restores. 198087392 FCU minor alarm Alarm Property � Alarm Code:198087392 � Severity:Minor � � Description:FCU minor alarm Alarm Type:Equipment Alarm Probable Cause FCU digital board assistant circuit triggers alarm. System Impact FCU works abnormally. Speciic Problem Handling Suggestion FCU digital board assistant circuit triggers alarm. Keep on observing and don't replace FCU board if normal service is not affected. 198087403 ABIS-E1 transmission related clock alarm of CCI board Alarm Property � � Alarm Code:198087403 Description:ABIS-E1 transmission related clock alarm of CCI board Conidential and Proprietary Information of ZTE CORPORATION 203 ZXG10 iBSC Alarm Handling Reference � Probable Cause Speciic Problem System Impact Handling Suggestion � Severity:Minor Alarm Type:Equipment Alarm Reference source is missed or ABIS-E1 transmission clock PLL(Phase Locked Loop) lost. Reference source is missed or ABIS-E1 transmission clock PLL(Phase Locked Loop) lost. User deined Examine the Abis-E1 interface. 198087404 Local working clock alarm of CCI board Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087404 � Severity:Minor � � Description:Local working clock alarm of CCI board Alarm Type:Equipment Alarm Local working clock failed. Local working clock failed. User deined Switch into slave baord as soon as possible, and replace CCI circuit board if necessary. 198087405 13M clock alarm of CCI board . Alarm Property Probable Cause Speciic Problem System Impact 204 � Alarm Code:198087405 � Severity:Minor � � Description:13M clock alarm of CCI board . Alarm Type:Equipment Alarm Reference source is missed or concerned clock PLL(Phase Locked Loop) lost. Reference source is missed or concerned clock PLL(Phase Locked Loop) lost. User deined Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Handling Suggestion Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion Alarm Property Check reference source or replace CCI. 198087406 CCI opposite board alarm � Alarm Code:198087406 � Severity:Warning � � Description:CCI opposite board alarm Alarm Type:Equipment Alarm CCI opposite board is not in position or clock has error. CCI opposite board is not in position or clock has error. User deined Replace the CCI circuit board. 198087407 IQ FPGA internal clock alarm � Alarm Code:198087407 � Severity:Minor � � Description:IQ FPGA internal clock alarm Alarm Type:Equipment Alarm Probable Cause IQ FPGA internal source clock is lost. System Impact User deined Speciic Problem Handling Suggestion Alarm Property IQ FPGA internal source clock is lost. Detect whether the CLK FPGA is running. 198087408 IQ FPGA light interface alarm � Alarm Code:198087408 � Severity:Minor � � Description:IQ FPGA light interface alarm Alarm Type:Equipment Alarm Conidential and Proprietary Information of ZTE CORPORATION 205 ZXG10 iBSC Alarm Handling Reference Probable Cause IQ FPGA light interface link connection is abnormal. System Impact User deined Speciic Problem Handling Suggestion Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion IQ FPGA light interface link connection is abnormal. Replace the optical module or optical iber. 198087409 IQ FPGA LVDS interface alarm � Alarm Code:198087409 � Severity:Minor � � Description:IQ FPGA LVDS interface alarm Alarm Type:Equipment Alarm LVDS interface is abnormal. LVDS interface is abnormal. User deined Check the rear board and SERDES chip condition on the corresponding GBP board. 198087410 IQ FPGA internal data alarm Alarm Property Alarm Code:198087410 � Severity:Minor � � Description:IQ FPGA internal data alarm Alarm Type:Equipment Alarm Probable Cause The format of detected internal data is abnormal System Impact User deined Speciic Problem Handling Suggestion 206 � The format of detected internal data is abnormal Check the reason for abnornal data format with whole system alarms. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198087411 13M and 61.44M clock lost alarm Alarm Property � Alarm Code:198087411 � Severity:Minor � � Description:13M and 61.44M clock lost alarm Alarm Type:Equipment Alarm Probable Cause Clock is lost. System Impact User deined Speciic Problem Handling Suggestion Clock is lost. f there is 13M or 61.44M clock lost alarm in CCI board and the alarm still exists after resetting CCI, please check the clock source; if there is no 13M or 61.44M clock lost alarm while alarm still exists after resetting GBP, please check LVDS access malfunction. 198087412 FR or FN has error. Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087412 � Severity:Minor � � Description:FR or FN has error. Alarm Type:Equipment Alarm FR or FN has error. FR or FN has error. User deined If there is FR or FN error in CCI and the error still exists after resetting CCI, please check hardware malfunction; if there is no FR or FN error while 60ms clock lost alarm still exists after resetting GBP, please check LVDS access malfunction. Conidential and Proprietary Information of ZTE CORPORATION 207 ZXG10 iBSC Alarm Handling Reference 198087413 26MHz and 52MHz Phase Locked Loop (PLL) lose lock alarm Alarm Property � Alarm Code:198087413 � Severity:Minor � � Description:26MHz and 52MHz Phase Locked Loop (PLL) lose lock alarm Alarm Type:Equipment Alarm Probable Cause PLL is unlocked. System Impact User deined Speciic Problem Handling Suggestion PLL is unlocked. If there is 13M clock lost alarm and still exists after resetting CCI, please check the clock source; if there is no 13M clock lost alarm and lock-lost alarm still exists after resetting GBP, then check whether 13M LVDS access has malfunction. If not, problem turns to be FPGA PLL failure and replace FPGA then. 198087414 Detect failure alarm of uplink 60ms hyperframe synchronization head Alarm Property Alarm Code:198087414 � Severity:Minor � � Description:Detect failure alarm of uplink 60ms hyperframe synchronization head Alarm Type:Equipment Alarm Probable Cause No 60ms hyperframe head is detected in uplink. System Impact User deined Speciic Problem Handling Suggestion 208 � No 60ms hyperframe head is detected in uplink. If there is detect failure alarm of uplink 60ms hyperframe synchronization head in CCI board, and the alarm still exists after resetting CCI, please check corresponding hardware error; If no such alarm in uplink while alarm still exists after resetting GBP, please check the LVDS access malfunction then. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198087415 Checking block data error alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087415 � Severity:Warning � � Description:Checking block data error alarm Alarm Type:Equipment Alarm Frame data has error. Frame data has error. User deined None 198087416 Uplink LVDS SERDES lost lock alarm Alarm Property � Alarm Code:198087416 � Severity:Minor � � Description:Uplink LVDS SERDES lost lock alarm Alarm Type:Equipment Alarm Probable Cause Frame number from CCI has error. System Impact User deined Speciic Problem Handling Suggestion Frame number from CCI has error. If there is FN error in CCI and the error still exists after resetting CCI, please check hardware error; if there is no FN error while the alarm still exists after resetting GBP, please check LVDS access malfunction. 198087417 FN error alarm Alarm Property Probable Cause Speciic Problem System Impact � Alarm Code:198087417 � Severity:Warning � � Description:FN error alarm Alarm Type:Equipment Alarm Frame number from CCI has error. Frame number from CCI has error. User deined Conidential and Proprietary Information of ZTE CORPORATION 209 ZXG10 iBSC Alarm Handling Reference Handling Suggestion If there is FN error in CCI and the error still exists after resetting CCI, please check hardware error; if there is no FN error while the alarm still exists after resetting GBP, please check LVDS access malfunction. 198087432 Diversity antenna lost. Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087432 � Severity:Major � � Description:Diversity antenna lost. Alarm Type:Equipment Alarm Two diversity antennae receive signal and one of which is abnormal. Two diversity antennae receive signal and one of which is abnormal. One of the diversity antennae breaks down and doesn’t play the role of diversity reception, thus impacting sensitivity and coverage. Reset the TRX and if error still exists, replace the slot. And replace DTRU if alarm still exists. 198087433 Diversity antenna identical. Alarm Property Alarm Code:198087433 � Severity:Major � � Description:Diversity antenna identical. Alarm Type:Equipment Alarm Probable Cause Connection of two diversity antennae is wrong. System Impact Antenna are connected identically and cannot work properly. Speciic Problem 210 � Connection of two diversity antennae is wrong. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Handling Suggestion Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion Alarm Property Check the connection of antenna as quickly as possible. 198087443 Diversity antenna lost alarm � Alarm Code:198087443 � Severity:Warning � � Description:Diversity antenna lost alarm Alarm Type:Equipment Alarm Two diversity antennae receive signal and one of which is abnormal. Two diversity antennae receive signal and one of which is abnormal. User deined Check the receive channel of RF as quickly as possible. 198087444 Diversity antenna identical alarm � Alarm Code:198087444 � Severity:Warning � � Description:Diversity antenna identical alarm Alarm Type:Equipment Alarm Probable Cause The connection between two diversity antennae is wrong. System Impact User deined Speciic Problem Handling Suggestion The connection between two diversity antennae is wrong. Check the connection of ant line as quickly as possible. 198087451 Board does not support 16MHW. Alarm Property � Alarm Code:198087451 � Severity:Warning � Description:Board does not support 16MHW. Conidential and Proprietary Information of ZTE CORPORATION 211 ZXG10 iBSC Alarm Handling Reference � Alarm Type:Equipment Alarm Probable Cause Current board doesn’t support 16MHW. System Impact It partially supports IP ABIS function and some TRX cannot work properly. Speciic Problem Handling Suggestion Alarm Property Current board doesn’t support 16MHW. Replace with the board that supports 16MHW. 198087452 CMB CPU overload alarm � Alarm Code:198087452 � Severity:Warning � � Description:CMB CPU overload alarm Alarm Type:Equipment Alarm Probable Cause CPU usage rate exceeds 85%. System Impact Some service cannot be processed. Speciic Problem Handling Suggestion Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion CPU usage rate exceeds 85%. Wait for a while until alarm restores, and process service then. 198087453 Signalling HDLC is broken . � Alarm Code:198087453 � Severity:Major � � Description:Signalling HDLC is broken . Alarm Type:Equipment Alarm HDLC communication between TRX and FIB breaks or hardware has error, etc. HDLC communication between TRX and FIB breaks or hardware has error, etc. No callings can through this DTRU. 1. Check whether DTRU board is inserted, plugged tightly or powered on, watch if alarm restores. 2. Reset DTRU board to check whether the alarm is recovered. 3. Check FIB board work status. 4. Check whether the DIP address switch on the rear board is correct. 212 Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 5. Check whether the transmission line of the rear board is connected correctly. 198087454 Main dimensional HDLC broken alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087454 � Severity:Major � � Description:Main dimensional HDLC broken alarm Alarm Type:Equipment Alarm HDLC link between CMB and FIB breaks, or CMB or FIB hardware has error. HDLC link between CMB and FIB breaks, or CMB or FIB hardware has error. No data can be transmissed between CMB and FIB. 1. Check whether CMB or FIB processes properly. If CMB is abnormal, reset CMB and check alarm status. If FIB is abnormal. Reset FIB and check alarm status. 2. If alarm doesn’t recover for a long time, please replace CMB or FIB and check whether it restores. 198087455 FIB configuration exception alarm Alarm Property � Alarm Code:198087455 � Severity:Warning � � Description:FIB coniguration exception alarm Alarm Type:Equipment Alarm Probable Cause Parameter coniguration is timeout or occurs error. System Impact In general, BSC background checks data legality before synchronizing data, and only after the data passed legality check can it be synchronized, therefore, this alarm rarely occurs. Speciic Problem Handling Suggestion Parameter coniguration is timeout or occurs error. 1. Wait for ten minutes and observe if the alarm restores. 2. If alarm doesn’t restore, reconigure parameter from background and synchronize to BTS. Conidential and Proprietary Information of ZTE CORPORATION 213 ZXG10 iBSC Alarm Handling Reference 3. If alarm still exists, replace FIB module. 198087456 FIB software layer 3 no response Alarm Property � Alarm Code:198087456 � Severity:Warning � � Description:FIB software layer 3 no response Alarm Type:Equipment Alarm Probable Cause FIB software (has/has not) reponse temporarily (set by CMB). System Impact FIB running state cannot be detected from background. Speciic Problem Handling Suggestion FIB software (has/has not) reponse temporarily (set by CMB). 1. Wait for ten minutes and observe if alarm restores. 2. If the alarm doesn’t restore for a long time, please re-plug and reset FUC when trafic is not busy. 3. Reset CMB when trafic is not busy and check if alarm recovers. 4. Replace FIB module and check if alarm recovers. 5. Correct software and upgrade the version. 198087457 FIB CPU overload alarm Alarm Property Probable Cause Speciic Problem System Impact 214 � Alarm Code:198087457 � Severity:Warning � � Description:FIB CPU overload alarm Alarm Type:Equipment Alarm CPU usage rate exceeds 85%. CPU usage rate exceeds 85%. Some service cannot be processed. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Handling Suggestion Alarm Property Wait for a while unitl alarm restores, and process service then. 198087458 BVC block alarm � Alarm Code:198087458 � Severity:Minor � � Description:BVC block alarm Alarm Type:Equipment Alarm Probable Cause The DSP on UPPB/UPBB2 board is abnormal. System Impact The cell fails to provide data service. Speciic Problem Handling Suggestion The DSP on UPPB/UPBB2 board is abnormal. 1. On NMS Dynamic Data Management interface, select Radio Resource Management under BTS Dynamic Data Management. Click the BVC Management tab and check if the cell state is blocked. If yes, unblock the cell. 2. On NMS Coniguration Management interface, ind the faulty cell through Coniguration Resource tree. In the GPRS Basic Params tab page of Cell Parameters interface, check if the conigurations of SGSN ID, NSEI, BVCI, UPPB Unit, and DSP No. are correct. If not, correct them and synchronize the data on BSC and NMS. 3. Log in UPPB/UPPB2 board through telnet. Input "SCSShowDSPStatus" command to check if the corresponding DSP status is running. If not, it indicates that the DSP is damaged. In this case, replace the board. 198087460 +12V voltage alarm Alarm Property � Alarm Code:198087460 � Severity:Major � � Description:+12V voltage alarm Alarm Type:Equipment Alarm Probable Cause The +12V power module on DPB board of DTRU module has alarm. System Impact The cell LNA cannot work properly and affect normal service. Speciic Problem The +12V power module on DPB board of DTRU module has alarm. Conidential and Proprietary Information of ZTE CORPORATION 215 ZXG10 iBSC Alarm Handling Reference Handling Suggestion Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion Replace DTRU module or BBTR backboard. 198087461 -12V voltage alarm � Alarm Code:198087461 � Severity:Major � � Description:-12V voltage alarm Alarm Type:Equipment Alarm The -12V power module on DPB board of DTRU module has alarm. The -12V power module on DPB board of DTRU module has alarm. The cell LNA cannot work properly and affect normal service. Replace DTRU module or BBTR backboard. 198087462 DSP 1.2V voltage alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion Alarm Property 216 � Alarm Code:198087462 � Severity:Major � � Description:DSP 1.2V voltage alarm Alarm Type:Equipment Alarm The 1.2V power module on DPB board of DTRU module has alarm. The 1.2V power module on DPB board of DTRU module has alarm. The DTRU cannot work and affect whole cell servvice if it is conigured as BCCH. Repace DTRU module. 198087463 6.4V voltage alarm � Alarm Code:198087463 � Severity:Major � Description:6.4V voltage alarm Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Type:Equipment Alarm The 6.4V power module on DPB board of DTRU module has alarm. The 6.4V power module on DPB board of DTRU module has alarm. The DTRU cannot work and affect whole cell servvice if it is conigured as BCCH. Repace DTRU module. 198087464 5V voltage alarm Alarm Property � Alarm Code:198087464 � Severity:Major � � Description:5V voltage alarm Alarm Type:Equipment Alarm Probable Cause The 5V power module on DPB board of DTRU module has alarm. System Impact The DTRU cannot work and affect whole cell servvice if it is conigured as BCCH. Speciic Problem Handling Suggestion The 5V power module on DPB board of DTRU module has alarm. Repace DTRU module. 198087470 Fan engine not-in-position alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087470 � Severity:Warning � � Description:Fan engine not-in-position alarm Alarm Type:Equipment Alarm The alarm is due to fan engine fault or module over high temperature. The alarm is due to fan engine fault or module over high temperature. Lead to over high temperature of TRM/DTRU, and affect the whole network performance. Check whether environment temperature meets requirment. If so, continue observing and keep normal work status in the pemise of no faults lying in other modules; If not, please improve equipment working environment, and replace FCM module if it is faulty. Conidential and Proprietary Information of ZTE CORPORATION 217 ZXG10 iBSC Alarm Handling Reference 198087471 Fan engine rotation speed alarm Alarm Property � Alarm Code:198087471 � Severity:Warning � � Description:Fan engine rotation speed alarm Alarm Type:Equipment Alarm Probable Cause Fan is not in position. System Impact Lead to over high temperature of TRM/DTRU, and affect the whole network performance. Speciic Problem Handling Suggestion Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion Fan is not in position. Let Fan in position or reinsert the fan and let it works well . 198087472 CMB and FNCB RS485 link broken alarm � Alarm Code:198087472 � Severity:Warning � � Description:CMB and FNCB RS485 link broken alarm Alarm Type:Equipment Alarm CPU is abnormal CPU is abnormal Fan engine is out of control, but doesn't affect cooling. (1) Check whether alarm circuit has fault. If so, solve this problem; if not, turn to step 2. (2) Replace fan controller board DFCM/FNCB. 198087473 DTPU CPU is overloaded. Alarm Property Probable Cause Speciic Problem 218 � Alarm Code:198087473 � Severity:Major � � Description:DTPU CPU is overloaded. Alarm Type:Equipment Alarm CPU usage rate exceeds 85%. CPU usage rate exceeds 85%. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm System Impact Handling Suggestion Alarm Property Service on this DTRU cannot be processed. Wait for about 10 minutes and process service after alarm restores. 198087480 Status of TX5 filter alarm � Alarm Code:198087480 � Severity:Major � � Description:Status of TX5 ilter alarm Alarm Type:Equipment Alarm Probable Cause TX5 channed is not well adjusted or the loss exceeds 5dB. System Impact Radio transmission is affected. Speciic Problem Handling Suggestion TX5 channed is not well adjusted or the loss exceeds 5dB. (1) Reset the corresponding TRX and check whether the alarm restores. (2) Replace FCU and check whether the alarm restores. 198087481 Status of TX6 filter alarm Alarm Property � Alarm Code:198087481 � Severity:Major � � Description:Status of TX6 ilter alarm Alarm Type:Equipment Alarm Probable Cause TX6 channed is not well adjusted or the loss exceeds 5dB. System Impact Radio transmission is affected. Speciic Problem Handling Suggestion TX6 channed is not well adjusted or the loss exceeds 5dB. (1) Reset the corresponding TRX and check whether the alarm restores. (2) Replace FCU and check whether the alarm restores. 198087483 GPS signal synchronization exception Alarm Property � � Alarm Code:198087483 Description:GPS signal synchronization exception Conidential and Proprietary Information of ZTE CORPORATION 219 ZXG10 iBSC Alarm Handling Reference � Probable Cause Speciic Problem System Impact Handling Suggestion � Severity:Minor Alarm Type:Equipment Alarm GPS synchronization is not supported, GPS clock synchronization fails or GPS has fault. GPS synchronization is not supported, GPS clock synchronization fails or GPS has fault. Cannot process GPS clock synchronization, and switch to internal synchronization mode. 1. Check current CMB board type, and if it doesn’t supports GPS synchronization, replace it with one that supports. 2. Check whether EIB/FIB supports GPs, if not replace with one that supports. 198087484 Second pulse lost alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087484 � Severity:Minor � � Description:Second pulse lost alarm Alarm Type:Equipment Alarm GPS 1PPS signal is lost. GPS 1PPS signal is lost. It cannot process GPS clock synchronization. 1. Check GPS antennae installation out of the cabinet, and remove fault if there is any. 2. Check adapter cable from EIB/FIB module to set-top GPS, and remove fault if there is any. 3. Check EIB/FIB module, and replace it if there is malufunction. 4. Check GPS second pulse alarm collection circuit of CMB module, and replace it if it is abnormal. 198087485 Antenna open-circuit alarm Alarm Property � Alarm Code:198087485 � Severity:Minor � � 220 Description:Antenna open-circuit alarm Alarm Type:Equipment Alarm Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Probable Cause Speciic Problem System Impact Handling Suggestion GPS antennae appear open-circuit exception. GPS antennae appear open-circuit exception. It cannot process GPS clock synchronization. 1. Check whether GPS antennae installation out of the cabinet has open circuit, if so, remove it. 2. Check whether adapter cable from EIB/FIB module to set-top GPS has open circuit, if so, remove it. 3. Check EIB/FIB module, and replace it if there is malufunction. 198087486 Antenna short-circuit alarm Alarm Property � Alarm Code:198087486 � Severity:Minor � � Description:Antenna short-circuit alarm Alarm Type:Equipment Alarm Probable Cause GPS antennae appeared short-circuit exception. System Impact It cannot process GPS clock synchronization. Speciic Problem Handling Suggestion GPS antennae appeared short-circuit exception. 1. Check whether GPS antennae installation out of the cabinet has open circuit, if so, remove it. 2. Check whether adapter cable from EIB/FIB module to set-top GPS has open circuit, if so, remove it. 3. Check EIB/FIB module, and replace it if there is malufunction. 198087487 Lost satellite alarm Alarm Property � Alarm Code:198087487 � Severity:Minor � � Description:Lost satellite alarm Alarm Type:Equipment Alarm Probable Cause GPS does not recognize the satellite System Impact It cannot process GPS clock synchronization. Speciic Problem Handling Suggestion GPS does not recognize the satellite 1. Check whether GPS antennae installation out of the cabinet has open circuit, if so, remove it. Conidential and Proprietary Information of ZTE CORPORATION 221 ZXG10 iBSC Alarm Handling Reference 2. Check whether adapter cable from EIB/FIB module to set-top GPS has open circuit, if so, remove it. 3. Check EIB/FIB module, and replace it if there is malufunction. 198087505 GUP board connection failure Alarm Property � Alarm Code:198087505 � Severity:Major � � Description:GUP board connection failure Alarm Type:Equipment Alarm Probable Cause 1. The board could not be allocated with connection resources. Speciic Problem 1. The board could not be allocated with connection resources. System Impact Handling Suggestion 2. If the board type is AIPB, it may caused by UDP port or next hop error. 2. If the board type is AIPB, it may caused by UDP port or next hop error. Part of CS and PS service is unavailable, and no service could be provided if situation worsens. 1. Reboot the board. 2. If the board type is AIPB, check UDP port and next hop coniguration. 198088000 DTPU does not support baseband freqency-hopping alarm. Alarm Property Probable Cause Speciic Problem System Impact 222 � Alarm Code:198088000 � Severity:Major � � Description:DTPU does not support baseband freqency-hopping alarm. Alarm Type:Equipment Alarm DTPU does not support baseband freqency-hopping. DTPU does not support baseband freqency-hopping. 1. No DTRU 875DTRU. supports baseband Conidential and Proprietary Information of ZTE CORPORATION frequency-hopping except Chapter 2 Equipment Alarm Handling Suggestion 2. If the DTPB is not the latest version, the whole layer TRX cannot support baseband frequency-hopping. 1. Check if the DTRU is DTPB080300 module, if not, change to DTPB080300 module. 2. If alarm still exists, please check whether rear board is BBTR070401 type, if not, change to BBTR070401 backpanel. 198088001 PA voltage adjusting path has broken. Alarm Property � Alarm Code:198088001 � Severity:Warning � � Description:PA voltage adjusting path has broken. Alarm Type:Equipment Alarm Probable Cause I2C path disconnects. System Impact Energy-saving is not achieved. Speciic Problem Handling Suggestion I2C path disconnects. 1. Plug out DTRU and check whether 6-pin to 6-pin data cable exists in current DTRU. If not, this DTRU doesn’t support PA voltage adjustment function. 2. Check whether 6-pin to 6-pin data cable is inserted well. If not, insert it properly and try again. 3. Replace the cable and try again.If alarm still exists, turn to 3. 4. This function doesn't affect the general use of DTRU, While this DTRU could still be used until new DTRU which supports PA power adjustment function arrives, and then replace it. 198088002 PA voltage adjusting read/write error. Alarm Property � Alarm Code:198088002 � Severity:Warning � � Description:PA voltage adjusting read/write error. Alarm Type:Equipment Alarm Probable Cause I2C data read/write has error. System Impact Energy-saving is not achieved. Speciic Problem I2C data read/write has error. Conidential and Proprietary Information of ZTE CORPORATION 223 ZXG10 iBSC Alarm Handling Reference Handling Suggestion 1. Please redownload PA voltage adjustment coniguration and wait for 1 minute. If problem still exists,turn to 2. check and reconnect 6-pin to 6-pin data cable and redownload coniguration.If problem still exists,turn to 3. This function doesn't affect the general use of DTRU, While this DTRU could still be used until new DTRU which supports PA power adjustment function arrives, and then replace it. 198088003 PA voltage adjusting parameter turns to be error. Alarm Property � Alarm Code:198088003 � Severity:Warning � � Description:PA voltage adjusting parameter turns to be error. Alarm Type:Equipment Alarm Probable Cause Static power setting data exceeds the range. System Impact Energy-saving is not achieved. Speciic Problem Handling Suggestion Static power setting data exceeds the range. 1. Static power data exceeds the level deined by GSM related protocal, please correct the data.If alarm still exists, turn to 2. Reconigure data and issue afterwards. 198088004 Access iBSC failure Alarm Property Alarm Code:198088004 � Severity:Major � � Description:Access iBSC failure Alarm Type:Equipment Alarm Probable Cause Authentication failed or unconnected response System Impact User deined Speciic Problem Handling Suggestion 224 � Authentication failed or unconnected response 1. Authentication again 2. Check physical link Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198088005 Control link broken Alarm Property � Alarm Code:198088005 � Severity:Major � � Description:Control link broken Alarm Type:Equipment Alarm Probable Cause Communication broken between BTS and BSC System Impact User deined Speciic Problem Handling Suggestion Communication broken between BTS and BSC 1. First of all, decide the problem is HomeBTS failure or transmission line problem. 2. Check whether it is software process problem by signaling analyzer if all device work well, and determine it is BSC or BTS prolbem. 3. Correct relevant software problem and announce to upgrade the software version. 198088006 Operation link broken(CS) Alarm Property � Alarm Code:198088006 � Severity:Minor � � Description:Operation link broken(CS) Alarm Type:Equipment Alarm Probable Cause The transmission line disconnects. System Impact User deined Speciic Problem Handling Suggestion The transmission line disconnects. Check the transmission line. 198088007 Operation link broken(PS) Alarm Property � � Alarm Code:198088007 Description:Operation link broken(PS) Conidential and Proprietary Information of ZTE CORPORATION 225 ZXG10 iBSC Alarm Handling Reference � � Severity:Minor Alarm Type:Equipment Alarm Probable Cause The transmission line disconnects. System Impact User deined Speciic Problem Handling Suggestion The transmission line disconnects. Check the transmission line. 198088008 Parameter configuration mismatch Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion 226 � Alarm Code:198088008 � Severity:Minor � � Description:Parameter coniguration mismatch Alarm Type:Equipment Alarm iBSC parameter coniguration failed, time out or process is interrupted (timeout or link breaks). iBSC parameter coniguration failed, time out or process is interrupted (timeout or link breaks). User deined Reconigure parameters. 198088009 DSP initialization failure � Alarm Code:198088009 � Severity:Minor � � Description:DSP initialization failure Alarm Type:Equipment Alarm DSP software or hardware has error. DSP software or hardware has error. User deined 1. Download software of this DSP again. 2. Reset DSP and check whether the alarm restores. If not, replace corresponding HBTS. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198088010 Parameter configuration failure of AD6537 Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198088010 � Severity:Minor � � Description:Parameter coniguration failure of AD6537 Alarm Type:Equipment Alarm AD6537 register read/write has error. AD6537 register read/write has error. User deined Power-down restart and reconigure AD6537 register to send corresponding alarm message. 198088011 Tx PLL lost lock alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198088011 � Severity:Minor � � Description:Tx PLL lost lock alarm Alarm Type:Equipment Alarm Clock signal is unstable or TRM PLL has fault. Clock signal is unstable or TRM PLL has fault. User deined 1. Check HW between CMM and DTRU and reset DTRU . 2. If this alarm still exsits, replace DTRU as soon as possible. 198088012 Wrong parameter configuration for EEPROM Alarm Property � � Alarm Code:198088012 Description:Wrong parameter coniguration for EEPROM Conidential and Proprietary Information of ZTE CORPORATION 227 ZXG10 iBSC Alarm Handling Reference � Probable Cause Speciic Problem System Impact Handling Suggestion Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Severity:Minor Alarm Type:Equipment Alarm EEPROM hardware error or invalid parameter which is written into EEPROM previously, and result in the problem that EEPROM RF parameter cannot be read normally. EEPROM hardware error or invalid parameter which is written into EEPROM previously, and result in the problem that EEPROM RF parameter cannot be read normally. User deined Replace the DTRU. 198088013 FLASH memory fault � Alarm Code:198088013 � Severity:Major � � Description:FLASH memory fault Alarm Type:Equipment Alarm There are too many FLASH programming times, read/write error or software calibration error. There are too many FLASH programming times, read/write error or software calibration error. User deined Reset HBTS and check alarm status; reload software version and check whether alarm restores, otherwise replace HBTS. 198088014 DSP works abnormally. Alarm Property Alarm Code:198088014 � Severity:Major � � Description:DSP works abnormally. Alarm Type:Equipment Alarm Probable Cause DSP program has error. System Impact User deined Speciic Problem Handling Suggestion 228 � DSP program has error. Reset DSP, reload DSP software version and reconigure CHP parameters. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198088015 FPGA interface fault Alarm Property � Alarm Code:198088015 � Severity:Major � � Description:FPGA interface fault Alarm Type:Equipment Alarm Probable Cause DSP and FPGA interface disconnected. System Impact User deined Speciic Problem Handling Suggestion DSP and FPGA interface disconnected. Reload FPGA version and reset HBTS, if problem still exists, replace HBTS. 198088016 CHP frame porcessing error alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198088016 � Severity:Minor � � Description:CHP frame porcessing error alarm Alarm Type:Equipment Alarm Because of interferen level on the circuit, frame number cumulation is interrupted. Because of interferen level on the circuit, frame number cumulation is interrupted. User deined Reset HBTS 198088017 Wrong receive channel of RF Alarm Property � Alarm Code:198088017 � Severity:Minor � � Description:Wrong receive channel of RF Alarm Type:Equipment Alarm Conidential and Proprietary Information of ZTE CORPORATION 229 ZXG10 iBSC Alarm Handling Reference Probable Cause Speciic Problem System Impact Handling Suggestion Reveiving channel has error, and cannot receive uplink signal properly. Reveiving channel has error, and cannot receive uplink signal properly. User deined Redownload FPGA and DSP version, and reconigure system parameters. 198088018 Acquiring DNS failure under dynamic configured IP mode Alarm Property Alarm Code:198088018 � Severity:Major � � Description:Acquiring DNS failure under dynamic conigured IP mode Alarm Type:Equipment Alarm Probable Cause HBTS cannot acquire IP address from DNS server. System Impact User deined Speciic Problem Handling Suggestion Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion 230 � HBTS cannot acquire IP address from DNS server. Manually conigure DNS IP address by means of LMT tool. 198088019 Analysis failure of DNS domain name � Alarm Code:198088019 � Severity:Major � � Description:Analysis failure of DNS domain name Alarm Type:Equipment Alarm HBTS cannot acquire IP adress which analysis iBSC domain name correctly from DNS server. HBTS cannot acquire IP adress which analysis iBSC domain name correctly from DNS server. User deined Manually conigure the information such as accessed iBSC IP address, interface number and so on by means of LMT tool. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm 198088020 IPSec start failure Alarm Property � Alarm Code:198088020 � Severity:Major � � Description:IPSec start failure Alarm Type:Equipment Alarm Probable Cause It cannot access properly. System Impact User deined Speciic Problem Handling Suggestion Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion It cannot access properly. Reconigure IPSec parameters. 198088021 Frequency point and HTRG mismatch alarm � Alarm Code:198088021 � Severity:Minor � � Description:Frequency point and HTRG mismatch alarm Alarm Type:Equipment Alarm Hardward board type doesn’t support conigured frequency point information. Hardward board type doesn’t support conigured frequency point information. User deined 1. Reconigure the frequency point to match HTRG. 2. Replace HTRG that supports frequency point coniguration range. 198088022 DHCP automatically acquiring IP address failure Alarm Property � Alarm Code:198088022 � Severity:Major � Description:DHCP automatically acquiring IP address failure Conidential and Proprietary Information of ZTE CORPORATION 231 ZXG10 iBSC Alarm Handling Reference � Alarm Type:Equipment Alarm Probable Cause HBTS cannot acquire IP address automatically from DHCP server. System Impact User deined Speciic Problem Handling Suggestion HBTS cannot acquire IP address automatically from DHCP server. Use LMT tool to manually conigure HBTS IP address, submask, gateway and interface number, as well as accessed iBSC IP address, gateway and interface number, etc. 198088023 Overhigh temperature alarm Alarm Property � Alarm Code:198088023 � Severity:Minor � � Description:Overhigh temperature alarm Alarm Type:Equipment Alarm Probable Cause BTS temperature is overhigh. System Impact User deined Speciic Problem Handling Suggestion BTS temperature is overhigh. Turn off power and check. 198088024 Voltage abnormity Alarm Property Alarm Code:198088024 � Severity:Minor � � Description:Voltage abnormity Alarm Type:Equipment Alarm Probable Cause BTS voltage is abnormal System Impact User deined Speciic Problem 232 � BTS voltage is abnormal Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Handling Suggestion Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion Check the power. 198088025 Abis link switch alarm � Alarm Code:198088025 � Severity:Warning � � Description:Abis link switch alarm Alarm Type:Equipment Alarm Satellite backup BTS: if Abis link on the earth surface is broken, service will be switched to satellite backup link. Satellite backup BTS: if Abis link on the earth surface is broken, service will be switched to satellite backup link. If switched successfully, there is no impact on service. Check Abis link on the earth surface and restore it as soon as possible. 198088027 DIP E1 rack, rack type error Alarm Property � Alarm Code:198088027 � Severity:Warning � � Description:DIP E1 rack, rack type error Alarm Type:Equipment Alarm Probable Cause E1 rack DIP bit 15 to 12 indicates rack type error. System Impact E1 rack reboot possibly cannot setup link. Speciic Problem Handling Suggestion E1 rack DIP bit 15 to 12 indicates rack type error. Check E1 rack DIP switch bit 15 to 12. 198088028 DIP E1 rack, rack number error Alarm Property � � Alarm Code:198088028 Description:DIP E1 rack, rack number error Conidential and Proprietary Information of ZTE CORPORATION 233 ZXG10 iBSC Alarm Handling Reference � Probable Cause Speciic Problem System Impact Handling Suggestion � Severity:Warning Alarm Type:Equipment Alarm E1 rack DIP bit 11 to 10 indicates rack number error. E1 rack DIP bit 11 to 10 indicates rack number error. E1 rack reboot possibly cannot setup link. Check E1 rack DIP switch bit 11 to 10. 198088029 DIP E1 rack, slave rack port 1 error Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198088029 � Severity:Warning � � Description:DIP E1 rack, slave rack port 1 error Alarm Type:Equipment Alarm E1 rack DIP bit 9 to 8 indicates slave rack port 1 error. E1 rack DIP bit 9 to 8 indicates slave rack port 1 error. E1 site slave rack 1 possibly doesn’t work properly. Check E1 rack DIP switch bit 9 to 8. 198088030 DIP E1 rack, slave rack port 2 error Alarm Property Probable Cause Speciic Problem System Impact 234 � Alarm Code:198088030 � Severity:Warning � � Description:DIP E1 rack, slave rack port 2 error Alarm Type:Equipment Alarm E1 rack DIP bit 7 to 6 indicates slave rack port 2 error. E1 rack DIP bit 7 to 6 indicates slave rack port 2 error. E1 site slave rack 2 possibly doesn’t work properly. Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm Handling Suggestion Check E1 rack DIP switch bit 7 to 6. 198088031 DIP E1 rack,satellite back up flag error Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198088031 � Severity:Warning � � Description:DIP E1 rack,satellite back up lag error Alarm Type:Equipment Alarm E1 rack DIP bit 5 indicates satellite backup lag error. E1 rack DIP bit 5 indicates satellite backup lag error. Satellite backup link of E1 site possibly doesn’t work properly. Check E1 rack DIP switch bit 5. 198088032 DIP E1 rack, OAM time slot error. Alarm Property � Alarm Code:198088032 � Severity:Warning � � Description: DIP E1 rack, OAM time slot error. Alarm Type:Equipment Alarm Probable Cause E1 rack DIP bit 4 to 0 indicates OAM time slot error. System Impact E1 rack reboot possibly cannot setup link. Speciic Problem E1 rack DIP bit 4 to 0 indicates OAM time slot error. Conidential and Proprietary Information of ZTE CORPORATION 235 ZXG10 iBSC Alarm Handling Reference Handling Suggestion Check E1 rack DIP switch bit 4 to 0. 198088033 DIP IP rack,access mode error(IP or IPOE) Alarm Property � Alarm Code:198088033 � Severity:Warning � � Description:DIP IP rack,access mode error(IP or IPOE) Alarm Type:Equipment Alarm Probable Cause IP rack DIP bit 15 to 14 indicates access mode error (IP or IPOE). System Impact IP rack reboot possibly cannot setup link. Speciic Problem Handling Suggestion IP rack DIP bit 15 to 14 indicates access mode error (IP or IPOE). Check IP rack DIP switch bit 15 to 14. 198088034 DIP IP rack,rack number error Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198088034 � Severity:Warning � � Description:DIP IP rack,rack number error Alarm Type:Equipment Alarm IP rack DIP bit 13 to 12 indicates rack number error. IP rack DIP bit 13 to 12 indicates rack number error. IP rack reboot possibly cannot setup link. Check IP rack DIP switch bit 13 to 12. 198088035 DIP IP rack,site number error Alarm Property 236 � � Alarm Code:198088035 Description:DIP IP rack,site number error Conidential and Proprietary Information of ZTE CORPORATION Chapter 2 Equipment Alarm � Probable Cause Speciic Problem System Impact Handling Suggestion � Severity:Warning Alarm Type:Equipment Alarm IP rack DIP bit 11 to 0 indicates site number error. IP rack DIP bit 11 to 0 indicates site number error. IP rack reboot possibly cannot setup link. Check IP rack DIP switch bit 11 to 0. 198088036 DIP IP rack,sequence number error Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion Alarm Property � Alarm Code:198088036 � Severity:Warning � � Description:DIP IP rack,sequence number error Alarm Type:Equipment Alarm IP rack: sequence number conigured on NMS is wrong. IP rack: sequence number conigured on NMS is wrong. IP rack reboot possibly cannot setup link. Check the sequence number of corresponding IP site on NMS. 198088037 Mains power failure alarm � Alarm Code:198088037 � Severity:Major � � Description:Mains power failure alarm Alarm Type:Equipment Alarm Probable Cause AC mains failure System Impact user deine Speciic Problem Handling Suggestion AC mains failure check AC Conidential and Proprietary Information of ZTE CORPORATION 237 ZXG10 iBSC Alarm Handling Reference This page is intentionally blank. 238 Conidential and Proprietary Information of ZTE CORPORATION Chapter 3 Communication Alarm Table of Contents 198000519 Trunk error .................................................... 240 198000520 Trunk abnormal .............................................. 241 198001824 Abnormal status in SDH/SONET ........................ 242 198001825 High BER on SDH / Sonet link........................... 246 198003841 The control plane retransfer ratio over the threshold ................................................................................ 247 198005122 Loss of Active/standby communication link ......... 247 198005126 Incorrect FE Routing Connection ....................... 248 198005127 FE Link Error Alarm ......................................... 249 198005128 Duplicate rack and shelf................................... 249 198005378 Board HW Error .............................................. 250 198005382 Communication between power board and OMP is abnormal ....................................................................... 251 198005397 Communication of RAWMACIP channel is abnormal ............................................................................... 251 198005401 Test packet check abnormal ............................. 252 198005651 IP / MAC address conlict ................................. 253 198005664 The rate of error code in a mate link is high at GUIM ............................................................................. 253 198005666 The number of the error packets from MAC port exceeds the threshold ...................................................... 254 198015617 Some frames Received by FE/GE/ATM/MP/POS/ E1 Port are faulty ............................................................ 255 198015618 Faulty frames received by port over threshold ................................................................................ 256 198015873 PSN board is sending out incorrect frames.......... 257 198018689 UID unavailable .............................................. 257 198019208 Timing of Near-End IMA Group Failure ............... 258 198019212 Near-End Sending Link Broken ......................... 258 198019213 LIF Alarm of Near-End Receiving Link ................ 259 198019214 LODS Alarm of Near-End Receiving Link ............. 259 198019215 RDI Alarm of Far End Receiving Link .................. 260 198019216 Near-End Receiving Link Faults ......................... 261 198019218 Near-End Receiving Link Broken ....................... 261 198019223 Ne Group is in fault state. ................................ 262 198022784 BFD Session Interrupted .................................. 262 198029953 The Ethernet port state is OAM loop back .......... 264 198066000 Abis link broken.............................................. 264 198066003 Control plane communication is abnormal between board and its home module ..................................... 265 198066004 Control plane communication is abnormal between MP and OMP .......................................................... 266 198066005 SCCP subsystem unavailable ............................ 266 198066007 Broadband link overload .................................. 267 198066008 MTP2 link sending overload ............................. 268 198066009 MTP2 link reception overload ........................... 269 Conidential and Proprietary Information of ZTE CORPORATION 239 ZXG10 iBSC Alarm Handling Reference 198066010 MTP3 Signalling Point Inaccessible .................... 269 198066011 MTP3 link unavailable ...................................... 270 198066012 MTP3 cluster inaccessible ................................. 271 198066014 M3UA Signalling Point Inaccessible .................... 271 198066015 SUA subsystem unavailable.............................. 272 198066016 SUA ofice inaccessible .................................... 273 198066019 Association link broken .................................... 274 198066020 STC Signalling Point Inaccessible ...................... 275 198066026 Association path broken................................... 275 198066029 PPP link broken............................................... 276 198066030 BSCIP coniguration error in database................ 277 198066066 AAL2 Path locally blocked................................. 278 198066067 AAL2 Path remotely blocked ............................. 278 198066068 AAL2 Path blocked by broken PVC ..................... 279 198066071 Link broken for board fault ............................... 279 198087336 Rack Abis control link broken............................ 279 198087337 Site Abis control link broken ............................. 280 198087343 Front PC communication link broken alarm ......... 281 198087352 NSVC failure alarm.......................................... 282 198087775 super site exchanged to the satellitic ABIS link................................................................................ 282 198088026 IPOE uplink and downlink congestion alarm ......... 283 198000519 Trunk error Alarm Property Probable Cause � Alarm Code:198000519 � Severity:Major � � Description:Trunk error Alarm Type:Communications Alarm 1. The receiving cable of local trunk equipment is faulty. The cable is disconnected, or cable connector is broken. 2. The transmitting cable of opposite trunk equipment is faulty. The cable is disconnected, or cable connector is broken. 3. Trunk transmission line is faulty. The local DDF and equipment are not properly connected. Speciic Problem 4. Operation of LOS insertion is operated at opposite trunk equipment. Manual inset alarm operation is performed in diagnostic test. 1. The receiving cable of local trunk equipment is faulty. The cable is disconnected, or cable connector is broken. 2. The transmitting cable of opposite trunk equipment is faulty. The cable is disconnected, or cable connector is broken. 3. Trunk transmission line is faulty. The local DDF and equipment are not properly connected. System Impact 240 4. Operation of LOS insertion is operated at opposite trunk equipment. Manual inset alarm operation is performed in diagnostic test. The trunk equipment fails to work normally. All services based on the trunk are interrupted. Conidential and Proprietary Information of ZTE CORPORATION Chapter 3 Communication Alarm Handling Suggestion 1. Check whether the alarm is caused by local end or opposite end via meter measurement or loop test. Meter Measurement Use a trunk test meter to test whether the trunk receiving signals at local end are normal. If yes, fault might lie in local equipment. If no, troubleshoot at opposite end. Loop test Perform trunk self-loop at local end. If the alarm persists, fault might lie in local equipment. If the alarm disappears, troubleshoot at opposite end. 2. Replace trunk cable. 3. Replace the board. 198000520 Trunk abnormal Alarm Property Probable Cause � Alarm Code:198000520 � Severity:Major � � Description:Trunk abnormal Alarm Type:Communications Alarm 1. Trunk frame formats at local end and at opposite end are inconsistent. 2. The transmitting end of opposite trunk equipment is faulty. 3. Local trunk equipment is faulty. 4. Equipment grounding at both ends is bad. Speciic Problem 5. Impedance mismatch occurs. 1. Trunk frame formats at local end and at opposite end are inconsistent. 2. The transmitting end of opposite trunk equipment is faulty. 3. Local trunk equipment is faulty. 4. Equipment grounding at both ends is bad. System Impact Handling Suggestion 5. Impedance mismatch occurs. All services based on the trunk are interrupted. 1. Alarm details are displayed in NMS Alarm Management interface, where fault type is given. You can easily ind handling suggestions according to the fault type. The handling suggestions for each fault type are described as below: 1.Loss of E1 trunk frame, loss of E1 trunk multi-frame, E1 trunk alarm indication i. In NMS Coniguration Management interface, right click the board and select Subunit Coniguration to check whether frame format at both ends is the same. ii. In NMS Coniguration Management interface, right click the board and select Subunit Coniguration to check whether impedance is correct. iii. Check whether the grounding at both ends is proper. iv. If possible, locate alarm position, either at local end or at opposite end, by means of measurement instrument, loopback test, or board/cable replacement. 2. E1 trunk receives an alarm indication from opposite end. Check the alarm status of opposite end. Because the alarm indicaConidential and Proprietary Information of ZTE CORPORATION 241 ZXG10 iBSC Alarm Handling Reference tion is sent from opposite end, please solve the opposite-end problem irst. 198001824 Abnormal status in SDH/SONET Alarm Property Probable Cause � Alarm Code:198001824 � Severity:Minor � � Description:Abnormal status in SDH/SONET Alarm Type:Communications Alarm 1. The upriver SDH equipment has faults. 2. The optical iber on the optical distribution frame is wrongly connected during optic iber cutover and scheduling, or the expected value is wrongly set in the network management system. 3. The upriver equipment has faults, such as LOS,LOF,RS TIM etc. 4. The up direction of the downstream equipment has faults. 5. As for all NEs in the multiplexing section where the board is located, the iber pigtail connectors in the down direction are contaminated and the transmission line attenuation enhances, or optical transmission mode changes, which result in error codes; It may also be caused by ADM transmitting device failure. 6. The upriver AU pointer processing unit has faults. 7. The upriver VC channel control unit has faults. 8. The optical iber on the optical distribution frame is wrongly connected, or the expected value is wrongly set in the network management system during optic iber cutover and scheduling. 9. During project installation, the internal cross connection of SDH network is not complete, or the SDT Board or Subcard remote device isn't equipped with the channel where SDT Board or Subcard locates. 10. During project installation, the internal cross connection of SDH network is not complete. 11. Network Node Failure in VC Channel Where Board Locates 12. Failure of the upstream VC channel control unit. 13. Failure of the upstream TU pointer processing unit. 14. Failure of the upstream TU tributary pointer processing unit, which may includes TU AIS\TU LOM\TU LOP\TU UNEQ. 15. )Fault of local TU tributary function. 2)The equipment of other nodes on TU tributary may has tributary function faults." 16. Failure of the upstream VC tributary control unit. 242 Conidential and Proprietary Information of ZTE CORPORATION Chapter 3 Communication Alarm 17. The cable on the optical distribution frame (DDF) is wrongly connected, or the expected value is wrongly set in the network management system during cable cutover and scheduling. 18. During project installation, the internal cross connection of SDH network is not complete, or the remote device isn't equipped with the tributary. 19. The upstream and downstream circuit coniguration of each DXC during the corresponding timeslot is incomplete. The information of V5 signal label is inconsistent with that at the peer end. 20. As for all NEs in the multiplexing section where the board is located, the iber pigtail connectors in the down direction are contaminated and the transmission line attenuation enhances, or optical transmission mode changes, which result in error codes; It may also be caused by ADM transmitting device failure. 21. )Signal reception attenuation excessive. 2)Failure of transmitting part of directly connected transmission equipment. 3)Unclean optical iber connectors or incorrect connection of them. 4)Local-end receiving part failure." Speciic Problem 22. )Signal reception attenuation excessive. 2)Failure of transmitting part of directly connected transmission equipment. 3)Unclean optical iber connectors or incorrect connection of them. 4)Local-end receiving part failure." 1. The upriver SDH equipment has faults. 2. The optical iber on the optical distribution frame is wrongly connected during optic iber cutover and scheduling, or the expected value is wrongly set in the network management system. 3. The upriver equipment has faults, such as LOS,LOF,RS TIM etc. 4. The up direction of the downstream equipment has faults. 5. As for all NEs in the multiplexing section where the board is located, the iber pigtail connectors in the down direction are contaminated and the transmission line attenuation enhances, or optical transmission mode changes, which result in error codes; It may also be caused by ADM transmitting device failure. 6. The upriver AU pointer processing unit has faults. 7. The upriver VC channel control unit has faults. 8. The optical iber on the optical distribution frame is wrongly connected, or the expected value is wrongly set in the network management system during optic iber cutover and scheduling. 9. During project installation, the internal cross connection of SDH network is not complete, or the SDT Board or Subcard remote device isn't equipped with the channel where SDT Board or Subcard locates. 10. During project installation, the internal cross connection of SDH network is not complete. 11. Network Node Failure in VC Channel Where Board Locates 12. Failure of the upstream VC channel control unit. Conidential and Proprietary Information of ZTE CORPORATION 243 ZXG10 iBSC Alarm Handling Reference 13. Failure of the upstream TU pointer processing unit. 14. Failure of the upstream TU tributary pointer processing unit, which may includes TU AIS\TU LOM\TU LOP\TU UNEQ. 15. )Fault of local TU tributary function. 2)The equipment of other nodes on TU tributary may has tributary function faults." 16. Failure of the upstream VC tributary control unit. 17. The cable on the optical distribution frame (DDF) is wrongly connected, or the expected value is wrongly set in the network management system during cable cutover and scheduling. 18. During project installation, the internal cross connection of SDH network is not complete, or the remote device isn't equipped with the tributary. 19. The upstream and downstream circuit coniguration of each DXC during the corresponding timeslot is incomplete. The information of V5 signal label is inconsistent with that at the peer end. 20. As for all NEs in the multiplexing section where the board is located, the iber pigtail connectors in the down direction are contaminated and the transmission line attenuation enhances, or optical transmission mode changes, which result in error codes; It may also be caused by ADM transmitting device failure. 21. )Signal reception attenuation excessive. 2)Failure of transmitting part of directly connected transmission equipment. 3)Unclean optical iber connectors or incorrect connection of them. 4)Local-end receiving part failure." System Impact Handling Suggestion 22. )Signal reception attenuation excessive. 2)Failure of transmitting part of directly connected transmission equipment. 3)Unclean optical iber connectors or incorrect connection of them. 4)Local-end receiving part failure." 1. If alarm occurs on optical path, all trunk signals and services on this path are interrupted. 2. If alarm occurs on tributary, all trunk signals on this path are interrupted, and all services on this trunk are interrupted. 1. Alarm details are displayed in NMS Alarm Management interface, where fault type is given. You can easily ind handling suggestions according to the fault type. The handling suggestions for each fault type are described as below: 1.Regenerator section trace identiier mismatch In NMS Coniguration Management interface, click SDH parameter coniguration and select SDH Optical Channel Parameter to check whether the coniguration of "J0 coniguration mode" and "regenerator section trace" at local end is consistent with those at opposite end. If no, modify the coniguration to keep consistency. 2. Multiplex section remote defect indication Check alarm status in the multiplex section of opposite end. Because the alarm origin is from the opposite end, please solve the problem at opposite end irst. 3. Multiplex section remote error indication Check alarm status in the multiplex section of opposite end. Because the alarm origin is from opposite end (B2 bit error), please solve the problem at opposite end irst. 244 Conidential and Proprietary Information of ZTE CORPORATION Chapter 3 Communication Alarm 4. High order path trace identiier mismatch In NMS Coniguration Management interface, click SDH parameter coniguration and select SDH Optical Channel Parameter to check whether the coniguration of "J1 Mode 0" and "high order path trace 0" at local end is consistent with those at opposite end. If no, modify the coniguration to keep consistency. 5. High order path unequipped In NMS Coniguration Management interface, click SDH parameter coniguration and select SDH Optical Channel Parameter to check the coniguration of optical channel payload type. If the conigured value is 0, modify the coniguration. 6. High order path signal label mismatch In NMS Coniguration Management interface, click SDH parameter coniguration and select SDH Optical Channel Parameter to check the coniguration of optical channel payload type. Ensure that the parameter coniguration at both sides is the same. 7. High order path remote defect indication Check alarm status in the high order path of opposite end. Because the alarm origin is from opposite end, please solve the problem at at opposite end irst. 8. High order path remote error indication Check alarm status in the high order path of opposite end. Because the alarm origin is from opposite end (B3 bit error), please solve the problem at opposite end irst. 9. Tributary unit remote defect indication/Tributary remote defect indication (VC-11) Check alarm status in the corresponding tributary unit at opposite end. Because the alarm origin is from opposite end, please solve the problem at opposite end irst. 10. Tributary unit trace identiier mismatch In NMS Coniguration Management interface, click SDH parameter coniguration and select SDH Optical Channel Parameter to check whether the coniguration of "J2 mode" and "low order path trace" at local end is consistent with those at opposite end. If no, modify coniguration to keep consistency. 11. Tributary unit unequipped In NMS Coniguration Management interface, click SDH parameter coniguration and select SDH Optical Channel Parameter to check the coniguration of tributary unit payload type. If the conigured value is 0, modify the coniguration. 12. Tributary unit signal label identiier mismatch In NMS Coniguration Management interface, click SDH parameter coniguration and select SDH Optical Channel Parameter to check the coniguration of tributary unit payload type. Ensure that the parameter coniguration at both sides is the same. 13. Others i. Use measurement instrument or loopback test to judge whether the alarm is caused by local end or opposite end. a. Measurement instrument Use a SDH test instrument to test whether the received optical signals at local end are normal. If normal, it means opposite end has a fault. Please solve the relevant problem. b. Loop Test Carry out a self-loop test at local SDH equipment. If the alarm still occurs, it means local end has a fault. If the alarm disappears, it means opposite end has a fault. P... Conidential and Proprietary Information of ZTE CORPORATION 245 ZXG10 iBSC Alarm Handling Reference 198001825 High BER on SDH / Sonet link Alarm Property Probable Cause � Alarm Code:198001825 � Severity:Warning � � Description:High BER on SDH / Sonet link Alarm Type:Communications Alarm 1. Attenuation of receiving signals of local SDH equipment is large. 2. The transmitting part of opposite SDH equipment is faulty. 3. Fiber connector is polluted or misconnected. 4. The receiving part of local SDH equipment is faulty. Speciic Problem 5. Operation of bit error insertion is performed at opposite end. 1. Attenuation of receiving signals of local SDH equipment is large. 2. The transmitting part of opposite SDH equipment is faulty. 3. Fiber connector is polluted or misconnected. 4. The receiving part of local SDH equipment is faulty. System Impact Handling Suggestion 5. Operation of bit error insertion is performed at opposite end. SDH/SONET equipment can work. However, call loss or noise occurs to all voice services on this optical path, and bit error occurs on the data service channel. 1. Use meter measurement or loop test to judge whether the alarm is caused by local end or opposite end. Meter Measurement Use a SDH test meter or optical power meter to test whether the receiving optical signals at local end are normal. If normal, fault might lie in local equipment. If abnormal, fault lies in opposite end or on transmission side. Inform the opposite end or transmission side to troubleshoot. Loop Test Perform iber self-loop at local SDH equipment. If the alarm persists, fault might lie in local equipment. If the alarm disappears, inform the opposite end to troubleshoot. 2. Replace optical module. 3. Replace optical iber. 4. Replace board. 246 Conidential and Proprietary Information of ZTE CORPORATION Chapter 3 Communication Alarm 198003841 The control plane retransfer ratio over the threshold Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198003841 � Severity:Major � � Description:The control plane retransfer ratio over the threshold Alarm Type:Communications Alarm There are some badly-touched boards in the system environment and the retransfer-ratio of RUDP packets increases. There are some badly-touched boards in the system environment and the retransfer-ratio of RUDP packets increases. The master board will change when slave is exist. Make records of the alarm information and contact ZTE Corporation. 198005122 Loss of Active/standby communication link Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198005122 � Severity:Minor � � Description:Loss of Active/standby communication link Alarm Type:Communications Alarm 1. The board is conigured to be in active/standby mode, but the opposite board is not in position. 2. Hardware Problem. 1. The board is conigured to be in active/standby mode, but the opposite board is not in position. 2. Hardware Problem. The active board can not communicate with the standby board. As a result, active/standby changeover operation fails. There is no impact on services. 1. Make sure the board is conigured in active/standby mode, and both active/standby boards are in position. 2. Check whether the opposite board has the following alarm. If yes, please solve the problem according to recommended han- Conidential and Proprietary Information of ZTE CORPORATION 247 ZXG10 iBSC Alarm Handling Reference dling suggestions. Description: 8393987 Board ofline or CPU in reset status for a long period 3. Replace the opposite board. 4. Change the slots of the active board and the slave board. 198005126 Incorrect FE Routing Connection Alarm Property Probable Cause � Alarm Code:198005126 � Severity:Critical � � Description:Incorrect FE Routing Connection Alarm Type:Communications Alarm 1. FE-C3/4 is used for FE routing port when RUIM1 rear board is used. 2. When CHUB is connected to UIM/GUIM, CHUB rear card (RCHUB1/RCHUB2) uses discrete ports (e.g. port1/port3) to connect UIM rear card. 3. When UIM/GUIM is connected to UIM/GUIM CHUB, connections used for FE routing connection are not in pairs (e.g.FE-C2/4). Speciic Problem 4. When UIM is connected to UIM/CHUB, only one cable is used for FE inter-connection. 1. FE-C3/4 is used for FE routing port when RUIM1 rear board is used. 2. When CHUB is connected to UIM/GUIM, CHUB rear card (RCHUB1/RCHUB2) uses discrete ports (e.g. port1/port3) to connect UIM rear card. 3. When UIM/GUIM is connected to UIM/GUIM CHUB, connections used for FE routing connection are not in pairs (e.g.FE-C2/4). System Impact Handling Suggestion 4. When UIM is connected to UIM/CHUB, only one cable is used for FE inter-connection. Control plane routing is disconnected; ports are switched over in cycle; all services on this shelf are interrupted. 1. Reconnect the FE wire. 1. If the UIM board on the BUSN shelf uses RUIM1 backcard, make sure FE-C1/2 port is used for routing port. 2. If the GUIM board is on BGSN shelf, make sure FE1 and FE2 ports are used as routing ports. 3. If TRUNK mode is used, numerous FE ports make up of a TRUNK port for cascaded connection. In this case, make sure the both ends are paired ports. If the boards of the local board or the opposite board are not paired port, please reconnect the FE wire and make sure the both ends are used paired ports. Here is an example of connection method: i. When CHUB is connected with UIM/GUIM, the connecting wire on RCHUB1/RCHUB2 of CHUB backcard must be used 248 Conidential and Proprietary Information of ZTE CORPORATION Chapter 3 Communication Alarm continuous ports ( such as port1/port2 pair, port3/port4 pair, port5/port6 pair, port7/port8 pair ) to connect with the pairs on the UIM/GUIM backcard. ii. When UIM is connected with UIM/GUIM/CHUB, the ports on UIM backcard must be used as paired .If RUIM1 backcard is used, then two FE-C1/2 ports must be used for FE routing ports; if RUIM2/RUIM3 backcard is used, then use FE1/FE2 pair, FE3/FE4 pair or FE5/FE6 pair for the FE routing ports. iii. When GUIM is connected with UIM/GUIM/CHUB, the ports on GUIM backcard must be used as pair, i. e. , FE1 and FE2 must be used for FE routing ports. 198005127 FE Link Error Alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198005127 � Severity:Minor � � Description:FE Link Error Alarm Alarm Type:Communications Alarm 1. In a pair of FE ports, one has normal link but the other has link error. 2. The hardware is faulty. 1. In a pair of FE ports, one has normal link but the other has link error. 2. The hardware is faulty. Because one FE port has normal control plane link, services are not affected. However if this port is faulty, services can not be switched to the other port, leading to service interruption. 1. Check if only one cable is used to connect the port pair of the rear board to the peer-end FE port. Ensure that both cables are connected to the peer end. 2. Reconnect the cables or replace the cables. 3. Replace the rear board. 4. Replace the board. 198005128 Duplicate rack and shelf Alarm Property � Alarm Code:198005128 � Severity:Minor � Description:Duplicate rack and shelf Conidential and Proprietary Information of ZTE CORPORATION 249 ZXG10 iBSC Alarm Handling Reference � Alarm Type:Communications Alarm Probable Cause Shelf connect to the system with duplicate physical ID System Impact Boards in the shelf which power-on later power-on failure. Speciic Problem Handling Suggestion Shelf connect to the system with duplicate physical ID 1. Check whether two shelf with same physical ID exists. Modify the switch of one of the two shelfs and reset the shelf and board if such connection exists. 2. Check if the board link to the same board by different link type. Remove one of link type and reset the board if such connection exists. 198005378 Board HW Error Alarm Property � Alarm Code:198005378 � Severity:Major � � Description:Board HW Error Alarm Type:Communications Alarm Probable Cause 1. Clock is not synchronous. Speciic Problem 1. Clock is not synchronous. System Impact Handling Suggestion 2. Either the board or the slot has a hardware fault. 2. Either the board or the slot has a hardware fault. HW connection is affected and services carried over this HW are interrupted. 1. Check whether the board has one of the following alarms. If yes, please solve the problem according to corresponding handling suggestions. Related Alarms 1286 Loss of input clock 5646 Phase-locked Loop Unlocked 2. Check whether the clock board has one of the following alarms. If yes, please solve the problem according to corresponding handling suggestions. Related Alarms 26133 Output clock lost 26129 Clock reference source lost (Level 1 alarm) 26128 Clock reference source lost (Level 2 alarm) 26127 Clock reference source lost (Level 3 alarm) 3. In Coniguration Management interface, check whether APS protection is conigured when the SDTB/SDTB2 works in master/slave mode. How to check APS protection coniguration: In the Coniguration Management interface, click Rack, select the concerned board (SDTB/SDTB2). Then right click it. A shortcut menu appears. Then select Optical Port APS Protection. 4. Replace the board. 5. Replace the slot 6. Replace the UIM/GUIM of the same shelf. 250 Conidential and Proprietary Information of ZTE CORPORATION Chapter 3 Communication Alarm 198005382 Communication between power board and OMP is abnormal Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198005382 � Severity:Major � � Description:Communication between power board and OMP is abnormal Alarm Type:Communications Alarm 1. The power board is not connected to the OMP or the connection is wrong. 2. The power board locates in a rack. The conigured rack number is different from that where DIP switch of the power board locates. 1. The power board is not connected to the OMP or the connection is wrong. 2. The power board locates in a rack. The conigured rack number is different from that where DIP switch of the power board locates. The system can not monitor the status of power supply and environmental situation. However, there is no impact on services. 1. Reconnect the RS485 cable between the power board and OMP. 2. Make sure the rack number conigured for the rack in which this power board locates is consistent with the rack number switch set for the power board. 198005397 Communication of RAWMACIP channel is abnormal Alarm Property Probable Cause Speciic Problem � Alarm Code:198005397 � Severity:Major � � Description:Communication of RAWMACIP channel is abnormal Alarm Type:Communications Alarm 1. The CPU usage of the UIM/GUIM in the shelf is too high. 2. The service media stream exceeds the threshold. 3. The hardware is faulty. 1. The CPU usage of the UIM/GUIM in the shelf is too high. Conidential and Proprietary Information of ZTE CORPORATION 251 ZXG10 iBSC Alarm Handling Reference 2. The service media stream exceeds the threshold. System Impact Handling Suggestion 3. The hardware is faulty. The channel between user plane processing board and signaling processing board is abnormal. This causes degradation of QoS. In serious situation, services will be interrupted. 1. In NMS Alarm Management interface, check whether the UIM/GUIM board of the same shelf has a relevant alarm. If yes, please solve the problem according to corresponding handling suggestions. Related alarm: 2560 Board CPU overloaded 2. Replace the board. 3. Replace the UIM/GUIM of the same shelf. 4. Replace the slot. 198005401 Test packet check abnormal Alarm Property � Alarm Code:198005401 � Severity:Major � � Description:Test packet check abnormal Alarm Type:Communications Alarm Probable Cause 1. The board is faulty. Speciic Problem 1. The board is faulty. System Impact Handling Suggestion 2. The line from UIM/GUIM to GLI is abnormal. 2. The line from UIM/GUIM to GLI is abnormal. 1. Service transfer at medial plane is affected. The alarm details include fault type. Each fault type has different impacts on the system. 1. If fault type is "ATM abnormal", the ATM board can not provide normal ATM services. Thus, services carried by the board is interrupted. 2. If fault type is "L1 switch abnormal", it indicates that media plane communication is abnormal. This causes all services carried on the shelf to be interrupted. 1. Alarm details are displayed in NMS Alarm Management interface, where fault type is given. You can easily ind handling suggestions according to the fault type. The handling suggestions for each type are described as below. 1. Fault type: ATM abnormal The link between C5 and APC of ATM processing board is abnormal. In this case, replace the board. 2. Fault type: L1 switch abnormal The L1 media plane switching from UIM/GUIM to GLI is abnormal. This is usually caused by abnormal link between UIM/GUIM and GLI. In this case, reconnect the cable between UIM/GUIM and GLI, or replace the cable. If optical iber is used, replace the optical module. 252 Conidential and Proprietary Information of ZTE CORPORATION Chapter 3 Communication Alarm 198005651 IP / MAC address conflict Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198005651 � Severity:Major � � Description:IP / MAC address conlict Alarm Type:Communications Alarm 1. Board has rebooted and MAC address is incorrect. 2. Board has recalculated the MAC address, which is incorrect. 3. Addition of new shelf on the rack that has the same DIP settings as the other shelf. 1. Board has rebooted and MAC address is incorrect. 2. Board has recalculated the MAC address, which is incorrect. 3. Addition of new shelf on the rack that has the same DIP settings as the other shelf. If IPMAC conlicts, control plane communication may become abnormal. For the board that has been powered on, packets may be lost and services are unstable. In serious situation, link interruption may occur and all services borne on the board will be interrupted. For the board that is being powered on, the board may reset repeatedly, and services can not be accessed. 1. Unplug and plug the board. 2. Compare 2 DIP switches on 2 backplane boards, one is related to the board, the other is related to OMP board. If the 2 DIP switches have different settings, please correct the settings to keep consistency. Reset the relevant boards after setting. 3. Reset the board. 198005664 The rate of error code in a mate link is high at GUIM Alarm Property Probable Cause Speciic Problem System Impact � Alarm Code:198005664 � Severity:Minor � � Description:The rate of error code in a mate link is high at GUIM Alarm Type:Communications Alarm The rate of error code in a mate link is high. The rate of error code in a mate link is high. The data transferred via mate link are incorrect. Conidential and Proprietary Information of ZTE CORPORATION 253 ZXG10 iBSC Alarm Handling Reference Handling Suggestion 1. heck if the board is inserted tightly. Y->Please contact ZTE Corporation. N->Insert the board tightly,and then check if the alarm is eliminated: Y->end, N->contact ZTE Corporation. 198005666 The number of the error packets from MAC port exceeds the threshold Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198005666 � Severity:Minor � � Description:The number of the error packets from MAC port exceeds the threshold Alarm Type:Communications Alarm The number of the error packets from MAC port exceeds the threshold. The number of the error packets from MAC port exceeds the threshold. The MAC port is unavailable or the low is limited. 1. Check whether the connection between this port and the peer port is correct. Y->Go to "2" N->Check whether the cable connecting two ports is damaged. It is recommended to replace a new cable. If the alarm disappears: Y-> End, N-> Go to "2". 2. Try to replace the network interface on the peer end and then check if the alarm disappears. Y->End. N->Go to "3" 3. Try to replace the board or the network interface on the local end and then check if the alarm disappears. Y->End. N->Please contact ZTE Corporation. 254 Conidential and Proprietary Information of ZTE CORPORATION Chapter 3 Communication Alarm 198015617 Some frames Received by FE/GE/ATM/MP/POS/E1 Port are faulty Alarm Property Probable Cause � Alarm Code:198015617 � Severity:Minor � � Description:Some frames Received by FE/GE/ATM/MP/POS/E1 Port are faulty Alarm Type:Communications Alarm 1. The network connected with FE/GE/ATM/MP/POS/E1 port is abnormal. 2. The board is in abnormal status. 3. Board hardware is faulty. For example, the network processor sub card is not tightly inserted. Speciic Problem 4. Other board hardware faults. 1. The network connected with FE/GE/ATM/MP/POS/E1 port is abnormal. 2. The board is in abnormal status. 3. Board hardware is faulty. For example, the network processor sub card is not tightly inserted. System Impact Handling Suggestion 4. Other board hardware faults. Datagram reception of the board is affected. The service on this port might be unstable. Worst of all, all services on the board might be interrupted. 1. Unplug and plug port ibber/network cable. 2. Replace port ibber/network cable. 3. Reset the board. 4. Unplug and plug board. 5. Replace the board. Conidential and Proprietary Information of ZTE CORPORATION 255 ZXG10 iBSC Alarm Handling Reference 198015618 Faulty frames received by port over threshold Alarm Property Probable Cause � Alarm Code:198015618 � Severity:Minor � � Description:Faulty frames received by port over threshold Alarm Type:Communications Alarm 1. Network status of FE/GE/ATM/MP/POS/E1 port is abnormal. 2. Board hardware faults. 3. Other faults of the board cause faulty FE/GE/ATM/MP/POS/E1 reception. Speciic Problem 4. Network processor sub-card which has worked normally is loose. 1. Network status of FE/GE/ATM/MP/POS/E1 port is abnormal. 2. Board hardware faults. 3. Other faults of the board cause faulty FE/GE/ATM/MP/POS/E1 reception. System Impact Handling Suggestion 4. Network processor sub-card which has worked normally is loose. Datagram reception of the board is affected. The service on the board might be unstable. 1. Pull out/insert in the iber/network cables to check if the fault is eliminated. Y-> Finish the alarm handling. N-> go to "2". 2. Replace iber/network cables to check if the fault is eliminated. Y-> Finish the alarm handling. N-> go to "3". 3. Restart the board to check if the fault is eliminated. Y-> Finish the alarm handling. N-> go to "4". 4. Pull out/insert the board to check if the fault is eliminated. Y-> Finish the alarm handling. N-> go to "5". 5. Replace the board to check if the fault is eliminated. Y-> Finish the alarm handling. N-> For other reasons, please contact ZTE Corporation. 256 Conidential and Proprietary Information of ZTE CORPORATION Chapter 3 Communication Alarm 198015873 PSN board is sending out incorrect frames Alarm Property � Alarm Code:198015873 � Severity:Major � � Description:PSN board is sending out incorrect frames Alarm Type:Communications Alarm Probable Cause 1. PSN board in the same shelf is abnormal. Speciic Problem 1. PSN board in the same shelf is abnormal. System Impact Handling Suggestion 2. PSN board is faulty 2. PSN board is faulty If the fault lies in PSN board, service of the entire RNC NE will become unstable. If the alarm persists, all services will be interrupted. If the fault lies in the board where the alarm is declared, only the services on this board are affected. 1. Check if the following alarm exists in PSN board at the same shelf. If yes, refer to the corresponding alarm handling suggestion. Related alarm: 19456 All high-speed links between line card and package (packet) switching board are out of synch 2. Unplug and plug board. 3. Replace board. 198018689 UID unavailable Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198018689 � Severity:Major � � Description:UID unavailable Alarm Type:Communications Alarm 1. This alarm occurs when a UID is created, and disappears when the link gets through. 2. The link is broken. 1. This alarm occurs when a UID is created, and disappears when the link gets through. 2. The link is broken. The service on the UID will be interrupted. The UID becomes available one at least one HDCL under this UID becomes available, and this alarm disappears automatically in this case. To make the HDLC available, perform according to the alarm for HDLC unavailable. Conidential and Proprietary Information of ZTE CORPORATION 257 ZXG10 iBSC Alarm Handling Reference 198019208 Timing of Near-End IMA Group Failure Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198019208 � Severity:Major � � Description:Timing of Near-End IMA Group Failure Alarm Type:Communications Alarm Far end IMA group clock template sent by the remote end through ICP cells does not match with the near-end one. For example, ITC (Independence Transmit Clock) on the remote end does not match with CTC (Common Transmit Clock) on the near end. Far end IMA group clock template sent by the remote end through ICP cells does not match with the near-end one. For example, ITC (Independence Transmit Clock) on the remote end does not match with CTC (Common Transmit Clock) on the near end. IMA link may fail to be established. 1. heck if the clock mode on the near end is matched with that on the far end. Y->If it is matched, contact ZTE Corporation. N->If not, modify the coniguration. If the alarm is eliminated, inish the alarm handling. If not, please contact ZTE Corporation. 198019212 Near-End Sending Link Broken Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion 258 � Alarm Code:198019212 � Severity:Major � � Description:Near-End Sending Link Broken Alarm Type:Communications Alarm When some sending link could not connect to the far end IMA group like other links, this alarm appears. When some sending link could not connect to the far end IMA group like other links, this alarm appears. IMA link fails to be established. 1. heck if IMA chip works normally and each link can connect to the far end IMA group normally. Y->If the chip works normally and each link connects to the far end IMA group successfully, contact ZTE Corporation for help. N->If not, conigure them again. If the alarm is eliminated, inish the alarm handling. If not, please contact ZTE Corporation. Conidential and Proprietary Information of ZTE CORPORATION Chapter 3 Communication Alarm 198019213 LIF Alarm of Near-End Receiving Link Alarm Property � Alarm Code:198019213 � Severity:Major � � Description:LIF Alarm of Near-End Receiving Link Alarm Type:Communications Alarm Probable Cause Physical fault or connection error occurs to E1 link. System Impact IMA link is down. If several links are available in the IMA group, bandwidth of the IMA group will be affected, and the number of successful upper-layer service access will decrease. However, service interruption will not occur. If merely one link is available in the IMA group, all services on the IMA group are interrupted. Speciic Problem Handling Suggestion Physical fault or connection error occurs to E1 link. 1. On NMS fault management interface, view alarm Details where information of IMA chip ID, IMA group ID, IMA link ID, and E1 index is given. Locate the faulty IMA link according to the given information. 1. Refer to user's networking plan to see if connection error exists. 2. On NMS fault management interface, check if E1-related alarm exists in the board. If yes, refer to the corresponding alarm handling suggestion. Related alarms: 519 Trunk error 519 Trunk abnormal 1026 Cell delineation do not synchronization about cell on E1 link 198019214 LODS Alarm of Near-End Receiving Link Alarm Property Probable Cause � Alarm Code:198019214 � Severity:Major � � Description:LODS Alarm of Near-End Receiving Link Alarm Type:Communications Alarm 1. Operation of the input clock is abnormal. 2. Transmission quality of the link is poor. 3. Self-loop occurs to some cable connection in IMA group 4. Cable connection is incorrect in IMA group. Speciic Problem 5. Hardware is faulty. 1. Operation of the input clock is abnormal. 2. Transmission quality of the link is poor. 3. Self-loop occurs to some cable connection in IMA group Conidential and Proprietary Information of ZTE CORPORATION 259 ZXG10 iBSC Alarm Handling Reference 4. Cable connection is incorrect in IMA group. System Impact Handling Suggestion 5. Hardware is faulty. IMA link is down. If several links are available in the IMA group, bandwidth of the IMA group will be affected, and the number of successful upper-layer service access will decrease. However, service interruption will not occur. If merely one link is available in the IMA group, all services on the IMA group are interrupted. 1. Check alarm details on the NMS Alarm Management interface to ind the IMA chip ID, IMA group ID, IMA link ID, and E1 ID, and locate the faulty IMA link. 1. Check the RUN indicator on the clock board. If the indicator is green and lashes slowly, it means the clock board is normal; otherwise, reboot or replace the clock board. 2. Check whether there is any of the following clock-related alarms on UIM/GUIM on the NMS Alarm Management interface. If yes, the input clock source must be wrong. Handle it according to the corresponding suggestions. 1286 Loss of input clock 5646 Phase-locked Loop Unlocked 3. Check whether there is any of the following E1-related alarms on the NMS Alarm Management interface. If yes, handle it according to the corresponding suggestions. 519 Trunk error 520 Trunk abnormal 1026 Cell delineation do not synchronization about cell on E1 link 4. Check whether there is any self-loop in the IMA group at remote end. If yes, correct the connection according to the networking plan. 5. Check cable connections according to the networking plan to make sure that each cable is correctly connected. 6. Reboot the faulty board. 7. Replace the faulty board. 198019215 RDI Alarm of Far End Receiving Link Alarm Property � Alarm Code:198019215 � Severity:Major � � Description:RDI Alarm of Far End Receiving Link Alarm Type:Communications Alarm Probable Cause 1. Remote IMA link is not in activated status. Speciic Problem 1. Remote IMA link is not in activated status. System Impact 260 2. Remote receiving direction is faulty. 2. Remote receiving direction is faulty. IMA link is down. If several links are available in the IMA group, bandwidth of the IMA group will be affected, and the number of successful upper-layer service access will decrease. However, ser- Conidential and Proprietary Information of ZTE CORPORATION Chapter 3 Communication Alarm Handling Suggestion vice interruption will not occur. If merely one link is available in the IMA group, all services on the IMA group are interrupted. On NMS fault management interface, view alarm Details where information of IMA chip ID, IMA group ID, IMA link ID, and E1 index is given. Locate the faulty IMA link according to the given information. Check the working status of the relevant remote receiving link by referring to the opposite equipment operation guide. If remote receiving link is not in activated status, activate the link. 198019216 Near-End Receiving Link Faults Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198019216 � Severity:Major � � Description:Near-End Receiving Link Faults Alarm Type:Communications Alarm If a receiving link on near end has faults, this alarm appears on the near end. If a receiving link on near end has faults, this alarm appears on the near end. IMA link fails to be established. 1. heck if IMA chip works normally and each link can connect to the near IMA group normally. Y->If the chip works normally and each link connects to the near IMA group successfully, contact ZTE Corporation for help. N->If IMA chip works abnormally or there is a link which does not access to near end IMA group, handle this problem. If the alarm is eliminated, inish the alarm handling. If not, please contact ZTE Corporation for help. 198019218 Near-End Receiving Link Broken Alarm Property Probable Cause Speciic Problem � Alarm Code:198019218 � Severity:Major � � Description:Near-End Receiving Link Broken Alarm Type:Communications Alarm When some receiving links can not connect to the remote IMA group like other links, this alarm appears. When some receiving links can not connect to the remote IMA group like other links, this alarm appears. Conidential and Proprietary Information of ZTE CORPORATION 261 ZXG10 iBSC Alarm Handling Reference System Impact Handling Suggestion The physical link on Iu interface fails to be established. 1. heck receiving link connections on the two ends to see if each receiving link is connected to the remote IMA group normally and if the proper local E1 link is connected to the corresponding E1 link on far end. Y->If so, contact ZTE Corporation for help. N->If not, ind the fault causes and handle the problem. If the alarm is eliminated, inish the alarm handling. If not, please contact ZTE Corporation for help. 198019223 Ne Group is in fault state. Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198019223 � Severity:Major � � Description:Ne Group is in fault state. Alarm Type:Communications Alarm 1. All IMA links of this IMA group are broken. 2. The peer-end IMA group is broken. 1. All IMA links of this IMA group are broken. 2. The peer-end IMA group is broken. The IMA Group does not work Fix the broken IMA links in the IMA group. 198022784 BFD Session Interrupted Alarm Property Probable Cause � Alarm Code:198022784 � Severity:Minor � � Description:BFD Session Interrupted Alarm Type:Communications Alarm 1. The network cable connection on relevant equipment (including local/intermediate/opposite equipment) is loose or disconnected. 2. Intermediate equipment is faulty. 3. Opposite equipment is faulty. 4. Local equipment is faulty. 5. Coniguration related to the BFD session is incorrect. 262 Conidential and Proprietary Information of ZTE CORPORATION Chapter 3 Communication Alarm Speciic Problem 1. The network cable connection on relevant equipment (including local/intermediate/opposite equipment) is loose or disconnected. 2. Intermediate equipment is faulty. 3. Opposite equipment is faulty. 4. Local equipment is faulty. System Impact Handling Suggestion 5. Coniguration related to the BFD session is incorrect. All services on the path relating to the BFD session will be switched to the standby path. Service interruption will occur if no standby path exists. 1. Check alarm details on the NMS Alarm Management interface to ind the source address and the destination address of the BFD session. The source address refers to the address of local equipment. The destination address refers to the address of the opposite BFD session equipment. 1. Check the status of the line card at the local end. If the line card restarts repeatedly, replace it and power on. 2. Check the physical connection between the BFD session-related port and the local line card. If the connection is loose or broken, tighten or replace the cable. If the port indicator is on, it means the physical connection is normal. 3. Ping intermediate and termination equipment in turn with correct IP address. i. Telnet to the interface board to check the link by making a ping test. For example, if the destination address is 2.2.2.10, enter the following command in the telnet interface. brs_ping_b "2.2.2.10" ii. Wait for 5 seconds, and then enter the next command. BrsShowLog "ICMP" a. If "PING===>destine 2.2.2.10 timeout" displays on the screen, it means the response times out. b. If "ping_receive:Reply from 2.2.2.10: bytes=60 time<1ms" displays on the screen, it means the link is normal. iii. In case of timeout, check if the related route and address are conigured correctly. If not, correct the reconiguration and do a ping test again. iv. If the route/address is conigured correctly but the repsonse still times out, it means a link is broken or the intermediate equipment is faulty. In this case, check to see if there is any broken network cable, loose connection or abnormal equipment along the BFD session path. If yes, take necessary actions, such as replacing the broken cable, tightening the connection, or repairing or replacing the fault equipment, to solve the problem. 4. If the ping test indicates that packets can be received and sent normally at both ends, check to see if the BFD session at both ends is conigured correctly by performing the following steps: i. Check the coniguration of BFD session on the NMS Coniguration Management interface to ensure the BFD switch is in "enabled" status. ii. Make sure that the BFD session is conigured with the same working mode at both sides. iii. Make sure that at least one device plays an "active" role for the BFD session. iv. Make sure that the BFD session exists at both ends, and that the source and the destination IP addresses are matched. v. Make sure that the hop mode (single hop/multi-hop) is consistent at both ends. vi. Make sure that the authentication information is consistent at both ends. 5. Reboot the board where the interface is located. Conidential and Proprietary Information of ZTE CORPORATION 263 ZXG10 iBSC Alarm Handling Reference 198029953 The Ethernet port state is OAM loop back Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198029953 � Severity:Minor � � Description:The Ethernet port state is OAM loop back Alarm Type:Communications Alarm The local port state is loop back because the peer port starts Ethernet OAM loop back request of 802.3ah. The local port state is loop back because the peer port starts Ethernet OAM loop back request of 802.3ah. The Ethernet link which is in loop back test can't bear service data. Check if the peer port has started Ethernet OAM loop back test. If yes, stop it, if no, disable local port Ethernet OAM. 198066000 Abis link broken Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion 264 � Alarm Code:198066000 � Severity:Major � � Description:Abis link broken Alarm Type:Communications Alarm 1. A newly conigured link is initially broken. 2. The link status changes to broken. 3. The link may switchover. break frequently during active/standby 1. A newly conigured link is initially broken. 2. The link status changes to broken. 3. The link may switchover. break frequently BTS break-down during active/standby If the new Abis link. Please synchronize and wait with no other operation, the alarm will resume after 1 minute. If master/slave change happened before, the alarm will resume after 1 minute, no need any operation. Check the board has alarm "2560 Board cpu overload", please deal with irst. Conidential and Proprietary Information of ZTE CORPORATION Chapter 3 Communication Alarm 198066003 Control plane communication is abnormal between board and its home module Alarm Property Probable Cause � Alarm Code:198066003 � Severity:Major � � Description:Control plane communication is abnormal between board and its home module Alarm Type:Communications Alarm 1. The board is not in position. 2. The board is blocked. 3. The inserted board is different from board coniguration. 4. The board is faulty. 5. The control plane communication is abnormal. Speciic Problem 6. The board is reset. 1. The board is not in position. 2. The board is blocked. 3. The inserted board is different from board coniguration. 4. The board is faulty. 5. The control plane communication is abnormal. System Impact Handling Suggestion 6. The board is reset. The services carried by the board are interrupted. 1. Check whether the board is in position. If not, insert the board. 2. Check whether the board is in blocked status. If yes, unblock the board. 3. Check whether the inserted board is the same as the conigured board. If not, insert a correct board. 4. Reset the board. Wait for the board to be powered on. 5. Replace the board. 6. Replace the board slot. 7. Replace the UIM/GUIM board of the same shelf. Conidential and Proprietary Information of ZTE CORPORATION 265 ZXG10 iBSC Alarm Handling Reference 198066004 Control plane communication is abnormal between MP and OMP Alarm Property Probable Cause � Alarm Code:198066004 � Severity:Major � � Description:Control plane communication is abnormal between MP and OMP Alarm Type:Communications Alarm 1. The board is not in position. 2. The board is faulty. 3. The control plane communication is abnormal. Speciic Problem 4. The board resets. 1. The board is not in position. 2. The board is faulty. 3. The control plane communication is abnormal. System Impact Handling Suggestion 4. The board resets. The board is blocked so that it can not provide functions. Furthermore, all services under the relevant module become unavailable. 1. Check if the board is in position. If not, insert the board. 2. Reset the board. Wait for the board to be powered on. 3. Replace the board. 4. Replace the board slot. 5. Replace the UIM/GUIM board in the same shelf. 198066005 SCCP subsystem unavailable Alarm Property Probable Cause � Alarm Code:198066005 � Severity:Minor � � Description:SCCP subsystem unavailable Alarm Type:Communications Alarm 1. From the perspective of A, remote signaling point subsystem is out of service. 2. From the perspective of A, remote signaling point is inaccessible. 266 Conidential and Proprietary Information of ZTE CORPORATION Chapter 3 Communication Alarm 3. Remote subsystem (for B) is conigured at A end, but the corresponding local subsystem (for B) is not conigured at B end. 4. Local subsystem (for B) is blocked at B end. Speciic Problem 5. From the perspective of A, SCCP user is not conigured in remote MTP3 or M3UA user coniguration. 1. From the perspective of A, remote signaling point subsystem is out of service. 2. From the perspective of A, remote signaling point is inaccessible. 3. Remote subsystem (for B) is conigured at A end, but the corresponding local subsystem (for B) is not conigured at B end. 4. Local subsystem (for B) is blocked at B end. System Impact Handling Suggestion 5. From the perspective of A, SCCP user is not conigured in remote MTP3 or M3UA user coniguration. Signaling data can not be sent to/received from the relevant subsystem. New service can not access to the corresponding ofice. And existing services are interrupted abnormally. 1. Check whether there exists ofice (the ofice that corresponds to the subsystem) inaccessible alarm. If yes, refer to the corresponding alarm handling suggestion. Related alarms: i. 8400128 MTP3 ofice inaccessible ii. 8400384 M3UA ofice inaccessible 2. Unblock the subsystem in dynamic data management. 3. On NMS coniguration management interface, check the coniguration of signaling point code (for A) at A end. See if SCCP user is included in user type coniguration. If no, add the coniguration. Meanwhile, check the corresponding coniguration at B end. 4. Check whether the status of signaling point subsystem (for B) is available at B end. If no, the signaling point subsystem at B end must be out of service. Locate the cause for the abnormal status. 5. Check whether the signaling point subsystem (for B) is conigured at B end. If no, add the coniguration at B end. 198066007 Broadband link overload Alarm Property Probable Cause � Alarm Code:198066007 � Severity:Minor � � Description:Broadband link overload Alarm Type:Communications Alarm 1. There are too many messages from upper layer service. 2. The number of links is insuficient. Conidential and Proprietary Information of ZTE CORPORATION 267 ZXG10 iBSC Alarm Handling Reference Speciic Problem System Impact Handling Suggestion 3. Link load is uneven. 1. There are too many messages from upper layer service. 2. The number of links is insuficient. 3. Link load is uneven. Link overload leads to the loss of all upper-layer service messages. Call loss will occur and access success rate of PS services will fall. 1. Check the counter of "Peak Trafic of Signaling Link" in MTP3B signaling link performance statistics. If the load (nearly) reached 6000 during alarm occurrence, upper layer trafic must be heavy. Add links to share load. 2. On NMS coniguration management interface, check the signaling link coniguration of NE. Add or delete links to ensure that the number of links in a link set is two to the power of N. If there are two link sets in the current route, ensure that two link sets have the same number of links. 198066008 MTP2 link sending overload Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion 268 � Alarm Code:198066008 � Severity:Major � � Description:MTP2 link sending overload Alarm Type:Communications Alarm The trafic low carried by the MTP2 is excessive under the condition of current link bandwidth. It exceeds the alarm threshold of link transmission load. The alarm threshold is related to MITP2 link type. For 64K link, the alarm threshold is: bandwidth occupation ratio reaches 0.8. For N*64k or 2M link, the alarm threshold is: bandwidth occupation ratio reaches 0.6. The trafic low carried by the MTP2 is excessive under the condition of current link bandwidth. It exceeds the alarm threshold of link transmission load. The alarm threshold is related to MITP2 link type. For 64K link, the alarm threshold is: bandwidth occupation ratio reaches 0.8. For N*64k or 2M link, the alarm threshold is: bandwidth occupation ratio reaches 0.6. If MTP2 link is overloaded for quite a long time, the signalling link will be congested. As a result, service messages will be lost by MTP2 and the service will be interrupted. 1. Add links to the ofice that is in service for the congested link. 2. Take the following measures to improve transmission quality of physical links. Replace bottom layer lines. Ensure that connector contact and cable connection are normal. Conidential and Proprietary Information of ZTE CORPORATION Chapter 3 Communication Alarm 198066009 MTP2 link reception overload Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198066009 � Severity:Major � � Description:MTP2 link reception overload Alarm Type:Communications Alarm The trafic low carried by the MTP2 is excessive under the condition of current link bandwidth. It exceeds the alarm threshold of link transmission load. The alarm threshold is related to MITP2 link type. For 64K link, the alarm threshold is: bandwidth occupation ratio reaches 0.8. For N*64k or 2M link, the alarm threshold is: bandwidth occupation ratio reaches 0.6. The trafic low carried by the MTP2 is excessive under the condition of current link bandwidth. It exceeds the alarm threshold of link transmission load. The alarm threshold is related to MITP2 link type. For 64K link, the alarm threshold is: bandwidth occupation ratio reaches 0.8. For N*64k or 2M link, the alarm threshold is: bandwidth occupation ratio reaches 0.6. This alarm has little impact on the local. If MTP2 link reception is overloaded for quite a long time, the signalling reception will be congested. This may trigger the signalling low control of MTP2 layer. In most serious case, package loss may occur, which leads to call loss or decrease of PS access success rate. 1. Add links to the ofice that is in service for the congested link. 2. Take the following measures to improve transmission quality of physical links. Replace bottom layer lines. Ensure that connector contact and cable connection are normal. 198066010 MTP3 Signalling Point Inaccessible Alarm Property � Alarm Code:198066010 � Severity:Major � � Description:MTP3 Signalling Point Inaccessible Alarm Type:Communications Alarm Probable Cause 1. No service link exists in the ofice route. Speciic Problem 1. No service link exists in the ofice route. 2. TFP is received. 2. TFP is received. Conidential and Proprietary Information of ZTE CORPORATION 269 ZXG10 iBSC Alarm Handling Reference System Impact Handling Suggestion UE fails to receive/transmit messages from/to the relevant ofice. New services can not be accessed to this ofice, and existing services are interrupted abnormally. 1. Check whether there is an unavailable link alarm. If yes, please solve the problem according to corresponding handling suggestions. Related alarm: 8400129 MTP3 link unavailable 2. Check whether the coniguration of ofice and link at opposite end is correct. 198066011 MTP3 link unavailable Alarm Property Probable Cause � Alarm Code:198066011 � Severity:Minor � � Description:MTP3 link unavailable Alarm Type:Communications Alarm 1. Physical link at bottom layer is broken or link quality is poor. 2. Link test fails. 3. This link is deactivated in dynamic data management. 4. The opposite end has released this link. Speciic Problem 5. SMP or SPB/SPB2/APBE/APBE2 board resets 1. Physical link at bottom layer is broken or link quality is poor. 2. Link test fails. 3. This link is deactivated in dynamic data management. 4. The opposite end has released this link. System Impact Handling Suggestion 5. SMP or SPB/SPB2/APBE/APBE2 board resets If several MTP3 links are available for the ofice, services will not be affected. In the case of heavy trafic, link congestion may occur, leading to loss of packets/calls and decreased PS call access rate. If merely one link is available to the destination signalling point, the ofice may become inaccessible. UE fails to receive/transmit messages from/to the relevant ofice. New services can not be accessed to this ofice, and existing services are interrupted abnormally. 1. IN NMS Coniguration Management interface, click Signalling Link Coniguration to check PVC coniguration. Make sure that the coniguration of CVPI and CVCI should be the same at both ends. 2. In Dynamic Data Management, check link status. If it is interrupted and connected now and then, it means the link unavailability is caused by MTP3 link test failure. 1) In NMS Coniguration Management interface, check the coniguration of signalling point code at both ends. Ensure that the coniguration is consistent at both ends. 2) In NMS Coniguration Man- 270 Conidential and Proprietary Information of ZTE CORPORATION Chapter 3 Communication Alarm agement interface, check the coniguration of signalling link at both ends. Ensure that the coniguration of SLC (Signalling Link Code) is consistent at both ends. 3. Re-activate the link in Dynamic Data Management. 4. Check board status. If it is abnormal, reset or replace the board. 5. The opposite end has released the relevant link. Ask the opposite end to deal with the alarm as link unavailable. 198066012 MTP3 cluster inaccessible Alarm Property � Alarm Code:198066012 � Severity:Major � � Description:MTP3 cluster inaccessible Alarm Type:Communications Alarm Probable Cause 1. No service link exists in the cluster route. Speciic Problem 1. No service link exists in the cluster route. System Impact Handling Suggestion 2. TCP is received. 2. TCP is received. Reception and sending of messages from/to the relevant cluster fail. Access of new service under this cluster fails, and abnormal release of the ongoing service occurs. 1. Check if there exists unavailable link alarm. If yes, refer to the corresponding alarm handling suggestion. Related alarms: 8400129 MTP3 link unavailable 2. Check if cluster and link coniguration at opposite end is correct. 198066014 M3UA Signalling Point Inaccessible Alarm Property Probable Cause � Alarm Code:198066014 � Severity:Major � � Description:M3UA Signalling Point Inaccessible Alarm Type:Communications Alarm 1. Association link is broken or application server (AS) is not in serving status. Conidential and Proprietary Information of ZTE CORPORATION 271 ZXG10 iBSC Alarm Handling Reference Speciic Problem System Impact Handling Suggestion 2. M3UA ofice is inaccessible because the remote ofice gives a DUNS (destination signalling point unavailable) report. 1. Association link is broken or application server (AS) is not in serving status. 2. M3UA ofice is inaccessible because the remote ofice gives a DUNS (destination signalling point unavailable) report. UE fails to receive/transmit messages from/to the relevant ofice. New services can not be accessed to this ofice, and existing services are interrupted abnormally. 1. Check whether there is an association link broken alarm. If yes, please solve the problem according to corresponding handling suggestions. Related alarm: 8402690 Association link broken 2. In NMS Coniguration Management interface, view AS Static Information to check whether a routing context exists. If yes, view the relevant coniguration such as routing context ID, AS ID and AS service mode. The correct coniguration is described below. i. The routing context ID and AS service mode must be the same at both ends. ii. AS ID must meet the following requirements: if ASP is conigured for local end, SGP should be conigured for opposite end; if IPSP client is conigured for local end, IPSP server should be conigured for opposite end. 3. Re-activate the ASP in Dynamic Data Management. 4. Check whether the coniguration of relevant ofice is correct at opposite end. 198066015 SUA subsystem unavailable Alarm Property Probable Cause � Alarm Code:198066015 � Severity:Minor � � Description:SUA subsystem unavailable Alarm Type:Communications Alarm 1. Remote signaling point is inaccessible. 2. Remote subsystem (for B) is conigured at A end, but the corresponding local subsystem (for B) is not conigured at B end. 3. Local subsystem (for B) is blocked at B end. Speciic Problem 4. Remote signaling point subsystem is out of service. 1. Remote signaling point is inaccessible. 2. Remote subsystem (for B) is conigured at A end, but the corresponding local subsystem (for B) is not conigured at B end. 3. Local subsystem (for B) is blocked at B end. 4. Remote signaling point subsystem is out of service. 272 Conidential and Proprietary Information of ZTE CORPORATION Chapter 3 Communication Alarm System Impact Handling Suggestion Signaling data cannot be sent to and received from the relevant subsystem. Access of new service under the corresponding ofice fails, and release of the ongoing service occurs. 1. Check whether there exists ofice (the ofice that corresponds to the subsystem) inaccessible alarm. If yes, refer to the corresponding alarm handling suggestion. Related alarms: 8401153 SUA ofice inaccessible 2. Check whether the signaling point subsystem (for A) is conigured at A end. If no, add the coniguration at A end. 3. Check whether the status of signaling point subsystem (for B) is available at B end. If no, the signaling point subsystem at B end must be out of service. Locate the cause for the abnormal status. 4. Check whether the signaling point subsystem (for B) is conigured at B end. If no, add the coniguration at B end. 198066016 SUA office inaccessible Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198066016 � Severity:Major � � Description:SUA ofice inaccessible Alarm Type:Communications Alarm 1. Association link is broken or application server (AS) is not in serving status. 2. DUNA (destination signaling point unavailable) is reported by remote ofice of the association. 1. Association link is broken or application server (AS) is not in serving status. 2. DUNA (destination signaling point unavailable) is reported by remote ofice of the association. Reception and sending of messages from/to the relevant ofice fail. Access of new service under this ofice fails, and abnormal release of the ongoing service occurs. 1. Check if there exists broken association link alarm. If yes, refer to the corresponding alarm handling suggestion. Related alarm: Association link broken 2. Check AS coniguration on NMS coniguration management interface. Main checking items include the existence of routing context, routing context ID, APP server AS ID, and trafic mode. Correct coniguration is described below. i. The routing context ID and trafic mode at both ends must be the same. ii. APP server AS ID coniguration must meet the following requirements. If ASP is conigured for local end, SGP should be conigured for Opposite end. If IPSP client is conigured for local end, IPSP server should be conigured for opposite end. Conidential and Proprietary Information of ZTE CORPORATION 273 ZXG10 iBSC Alarm Handling Reference 3. Reactivate the ASP in dynamic data management. 4. Check whether the coniguration of the relevant ofice is correct at opposite end. 198066019 Association link broken Alarm Property Probable Cause � Alarm Code:198066019 � Severity:Major � � Description:Association link broken Alarm Type:Communications Alarm 1. The association is released in dynamic data management. 2. Association coniguration is modiied at local end. 3. Association is released at opposite end. Speciic Problem 4. Bottom layer link is faulty. 1. The association is released in dynamic data management. 2. Association coniguration is modiied at local end. 3. Association is released at opposite end. System Impact Handling Suggestion 4. Bottom layer link is faulty. If several association links are available to the destination ofice, service will not be affected. In the case of heavy trafic, congestion of available association(s) might occur, leading to upper layer call loss or increasing PS call access failures. If merely one association link is available to the destination ofice, the ofice might become inaccessible. Reception and sending of messages from/to the relevant ofice fail. Access of new services under this ofice fails, and abnormal release of ongoing services occurs. 1. Establish the association in dynamic data management. 2. On NMS coniguration management interface, check ASP coniguration at local end and opposite end. Checking items include protocol type of SCTP association, SMP module No, local IP address, local port No., remote IP address, remote port No., the number of in/out streams. If the coniguration at both ends is inconsistent, modify coniguration to keep consistency. 3. Ping the opposite board address to see if the network cable or other intermediate link is faulty. Replace the cable if ping fails. 4. Check if the association is released at opposite end. If yes, troubleshoot according to the corresponding cause. 274 Conidential and Proprietary Information of ZTE CORPORATION Chapter 3 Communication Alarm 198066020 STC Signalling Point Inaccessible Alarm Property � Alarm Code:198066020 � Severity:Major � � Description:STC Signalling Point Inaccessible Alarm Type:Communications Alarm Probable Cause No association is in the servicing state. System Impact The corresponding ofice cannot receive or send messages. Speciic Problem Handling Suggestion No association is in the servicing state. 1. Check whether no association to the adjacent ofice is available. Y->Perform further handling according to the alarm reason for association broken. N->Go to Step 2. Note down detailed information. 2.1 Back up related local ofice coniguration data and peer-end ofice coniguration data. 2.2 Back up related local ofice and peer-end ofice history alarms and notiications, as well as current alarms. 2.3 Contact ZTE Corporation and end the alarm handling procedure. 198066026 Association path broken Alarm Property Probable Cause � Alarm Code:198066026 � Severity:Major � � Description:Association path broken Alarm Type:Communications Alarm 1. SCTP link is broken 2. Control plane path in NE is interrupted. 3. Opposite equipment is faulty. Speciic Problem 4. The route to remote address is lost. 1. SCTP link is broken 2. Control plane path in NE is interrupted. 3. Opposite equipment is faulty. System Impact 4. The route to remote address is lost. If multiple paths are available for the association and there exists normal path, relevant services will not be affected. If merely one Conidential and Proprietary Information of ZTE CORPORATION 275 ZXG10 iBSC Alarm Handling Reference Handling Suggestion path is available for the association, all services on the association is down. 1. On NMS fault management interface, view alarm Details, where information of association ID, local address, and remote address is given. 1. On NMS coniguration management interface (static route), query the route information of the remote address. Locate the out port according to the route information. Check if network cable of the out port is disconnected or loose. If yes, unplug and plug the cable or replace the cable. 2. On NMS coniguration management interface (ASP coniguration), query the ID of the module where the association is located. Check if the following alarm occurs in the relevant board. If yes, refer to the corresponding alarm handling suggestion. Related alarm: 8393985 Control plane communication abnormal between board and its home module 3. On NMS coniguration management interface (static route), query if the route to the remote address of the association is conigured. If not, add the coniguration. 4. Check the intermediate equipment on association path. If the routes to local address and remote address of the association are not conigured, add the coniguration according to equipment operation manual. 5. Check at opposite end if the route to the local address of the association is conigured. If not, add the coniguration. 6. Check if the opposite equipment is faulty. If yes, troubleshoot at opposite end. 198066029 PPP link broken Alarm Property Probable Cause � Alarm Code:198066029 � Severity:Major � � Description:PPP link broken Alarm Type:Communications Alarm 1. The alarm occurs in PPP port creating, modifying, deleting when PPP port is created by command. 2. The alarm occurs once in PPP port during board power-on, and recovers after successful PPP negotiation. 3. Physical link is down, or link transmission quality is poor. Speciic Problem 4. Adjustment of PPP link parameter leads to link re-negotiation, causing the alarm. 1. The alarm occurs in PPP port creating, modifying, deleting when PPP port is created by command. 2. The alarm occurs once in PPP port during board power-on, and recovers after successful PPP negotiation. 3. Physical link is down, or link transmission quality is poor. 276 Conidential and Proprietary Information of ZTE CORPORATION Chapter 3 Communication Alarm System Impact Handling Suggestion 4. Adjustment of PPP link parameter leads to link re-negotiation, causing the alarm. This will cause disconnection of user plane data and services. 1. Check alarm details on the NMS Alarm Management interface to ind the faulty PPP port ID. 1. Check the cable connections at both ends to see if they are loose or broken. If yes, tighten the connection or replace the broken cable. 2. Refer to the networking plan to check if the E1 cable is correctly connected. 3. Click IPOverE1 Coniguration on the NMS Coniguration Management interface to check E1 ID and time slot. Make sure that the time slot coniguration is consistent at both ends. 4. Check PPP parameters on the NMS Coniguration Management interface to ensure that the coniguration is consistent at both ends. 5. Check the connection relation of DT and EIPI on the NMS Coniguration Management interface to ensure that the PPP port coniguration is consistent at both ends. 198066030 BSCIP configuration error in database Alarm Property � Alarm Code:198066030 � Severity:Warning � � Description:BSCIP coniguration error in database Alarm Type:Communications Alarm Probable Cause 1. BSCIP is not conigured. Speciic Problem 1. BSCIP is not conigured. System Impact Handling Suggestion 2. Illegal BSCIP coniguration, for example, all 0s or 1s. 2. Illegal BSCIP coniguration, for example, all 0s or 1s. ABPM cannot locate other problems with the self-loop method. 1. Check whether the BSCIP coniguration is correct. Y->Go to "2". N->Modify the coniguration, and go to "2" if this alarm still exists. 2. Check whether the internal link between OMP and ABPM is normal. Y->Go to "3". N->Check alarms for related internal communication, and perform further handling according to the alarm information, and go to "3" if this alarm still exists. Conidential and Proprietary Information of ZTE CORPORATION 277 ZXG10 iBSC Alarm Handling Reference 3. Check whether the coniguration data of the last coniguration or modiication have been uploaded to the foreground. Y->Go to "4". N->Wait a moment and try again, and go to "4" if this alarm still exists. 4. Note down the current BSCIP coniguration and contact ZTE. 198066066 AAL2 Path locally blocked Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198066066 � Severity:Minor � � Description:AAL2 Path locally blocked Alarm Type:Communications Alarm The Path is manually blocked from this AAL2 Node. The Path is manually blocked from this AAL2 Node. No AAL2 connection can be established on the blocked path. You can unblock the Path which is generated manually from the operating interface. 198066067 AAL2 Path remotely blocked Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion 278 � Alarm Code:198066067 � Severity:Minor � � Description:AAL2 Path remotely blocked Alarm Type:Communications Alarm The adjacent AAL2 node initiates blocking process and then the path of this node is remotely blocked when receiving the blocking message from the adjacent node. The adjacent AAL2 node initiates blocking process and then the path of this node is remotely blocked when receiving the blocking message from the adjacent node. No AAL2 connection can be established on the blocked path. You can unblock the Path which is generated by adjacent node from the operating interface of the adjacent node. Conidential and Proprietary Information of ZTE CORPORATION Chapter 3 Communication Alarm 198066068 AAL2 Path blocked by broken PVC Alarm Property � Alarm Code:198066068 � Severity:Minor � � Description:AAL2 Path blocked by broken PVC Alarm Type:Communications Alarm Probable Cause The Path is blocked because of the broken PVC. System Impact No AAL2 connection can be established on the blocked path. Speciic Problem Handling Suggestion Alarm Property The Path is blocked because of the broken PVC. The path can be available when PVC becomes available. 198066071 Link broken for board fault � Alarm Code:198066071 � Severity:Minor � � Description:Link broken for board fault Alarm Type:Communications Alarm Probable Cause Board internal fault. System Impact This alarm may render some ofices inaccessible, or may result in the congestion of other links. Speciic Problem Handling Suggestion Board internal fault. 1. ote down detailed information. 1.1 Back up related local ofice coniguration data and peer-end ofice coniguration data. 1.2 Back up related local ofice and peer-end ofice history alarms and notiications, as well as current alarms. 1.3 Contact ZTE Corporation and end the alarm handling procedure. 198087336 Rack Abis control link broken Alarm Property � Alarm Code:198087336 � Severity:Critical � � Description:Rack Abis control link broken Alarm Type:Communications Alarm Conidential and Proprietary Information of ZTE CORPORATION 279 ZXG10 iBSC Alarm Handling Reference Probable Cause 1. The rack conigured on NMS client does not actually exist. 2. In IP site, IP coniguration on NMS client is not correct. 3. In E1 site, Abis time slot of slave rack coniguration on NMS client is not correct. Speciic Problem 4. Cable connection is abnormal. 1. The rack conigured on NMS client does not actually exist. 2. In IP site, IP coniguration on NMS client is not correct. 3. In E1 site, Abis time slot of slave rack coniguration on NMS client is not correct. System Impact Handling Suggestion 4. Cable connection is abnormal. Alarmed rack cannot provide service. 1. Check BTS coniguration in Resource Tree Coniguration on NMS coniguration management interface if conigured slave rack actually exists. If not, delete the virtual one and synchronize the data to BSC on NMS. 2. In IP site, on NMS coniguration interface, check Coniguration Resource/IP related coniguration/Interface coniguration. Among which, IPBB item is conigured with the IP address of the gateway from BTS to BSC; RPU item is conigured with virtual IP address of the SCTP link from BTS to BSC. If the coniguration is not consistent with the NMS at BTS side, correct it and synchronize the data on BSC and BTS. 3. In E1 site, check Abis time slot of slave rack coniguration in Coniguration Resource tree on NMS coniguration management interface. 4. Check cable connection between BTS and BSC to ensure it works properly. 198087337 Site Abis control link broken Alarm Property Probable Cause � Alarm Code:198087337 � Severity:Critical � � Description:Site Abis control link broken Alarm Type:Communications Alarm 1. The rack conigured on NMS client does not actually exist. 2. In IP site, IP coniguration on NMS client is not correct. 3. In E1 site, Abis time slot of slave rack coniguration on NMS client is not correct. Speciic Problem 280 4. Cable connection is abnormal. 1. The rack conigured on NMS client does not actually exist. 2. In IP site, IP coniguration on NMS client is not correct. Conidential and Proprietary Information of ZTE CORPORATION Chapter 3 Communication Alarm 3. In E1 site, Abis time slot of slave rack coniguration on NMS client is not correct. System Impact Handling Suggestion 4. Cable connection is abnormal. The cells under this site cannot provide any voice or data services. 1. Check BTS coniguration in Coniguration Resource tree on NMS coniguration management interface if conigured slave rack actually exists. If not, delete the virtual one and synchronize the data on BSC and NMS. 2. In IP site, on NMS coniguration interface, check Coniguration Resource/IP related coniguration/Interface coniguration. Among which, IPBB item is conigured with the IP address of the gateway from BTS to BSC; RPU item is conigured with virtual IP address of the SCTP link from BTS to BSC. If the coniguration is not consistent with the NMS at BTS side, correct it and synchronize the data on BSC and BTS. 3. In E1 site, check Abis time slot of slave rack coniguration in Coniguration Resource tree on NMS coniguration management interface. 4. Check cable connection between BTS and BSC to ensure it works properly. 198087343 Front PC communication link broken alarm Alarm Property � Alarm Code:198087343 � Severity:Minor � � Description:Front PC communication link broken alarm Alarm Type:Communications Alarm Probable Cause 1. NFS service of Linux system on NMS server is abnormal. Speciic Problem 1. NFS service of Linux system on NMS server is abnormal. System Impact Handling Suggestion 2. The link communication between NMS server and OMP board is abnormal. 2. The link communication between NMS server and OMP board is abnormal. During the alarm period, performance data cannot be reported to NMS. 1. Log in OMP board through telnet and input "NfsShowState" command. If NFS device is abnormal, the command result shows corresponding indications in English. And then, check NFS service of Linux system on NMS server, if it is abnormal, NFS service need to be restarted immediately, for example, use Linux command "service nfs restart". Conidential and Proprietary Information of ZTE CORPORATION 281 ZXG10 iBSC Alarm Handling Reference 2. Check the network cables between SBCX and OMP and ensure the connections are correct. 198087352 NSVC failure alarm Alarm Property � Alarm Code:198087352 � Severity:Minor � � Description:NSVC failure alarm Alarm Type:Communications Alarm Probable Cause The physical link between BSC and SGSN is broken. System Impact For signal NSVC link coniguration, the PS service is interrupted. For multi-NSVC link coniguration, the bandwidth is decreased. Speciic Problem Handling Suggestion The physical link between BSC and SGSN is broken. 1. On NMS fault management interface, check if alarm which is related to FR device malfunction exists. If so, follow the instructions of handling related alarms. Related alarm: 198087340 FR device Failure 2. On NMS dynamic data management interface, check if NSVC coniguration parameters are consistent with those on SGSN. 3. Check if the E1 and the network cables between BSC and SGSN are intact and inserted correctly. 198087775 super site exchanged to the satellitic ABIS link Alarm Property Probable Cause Speciic Problem System Impact 282 � Alarm Code:198087775 � Severity:Major � � Description:super site exchanged to the satellitic ABIS link Alarm Type:Communications Alarm the subaerial ABIS link is broken, site exchanged to satellitic ABIS link the subaerial ABIS link is broken, site exchanged to satellitic ABIS link None Conidential and Proprietary Information of ZTE CORPORATION Chapter 3 Communication Alarm Handling Suggestion restore the subaerial ABIS link 198088026 IPOE uplink and downlink congestion alarm Alarm Property � Alarm Code:198088026 � Severity:Warning � � Description:IPOE uplink and downlink congestion alarm Alarm Type:Communications Alarm Probable Cause IPOE site detects uplink and downlink congestion. System Impact Service quality degrades or even interrupts. Speciic Problem Handling Suggestion IPOE site detects uplink and downlink congestion. Check the transmission line. Conidential and Proprietary Information of ZTE CORPORATION 283 ZXG10 iBSC Alarm Handling Reference This page is intentionally blank. 284 Conidential and Proprietary Information of ZTE CORPORATION Chapter 4 Handling Alarm Table of Contents 198005120 T Network Connection Not Conform to Coniguration ............................................................................... 286 198005123 Incorrect coniguration for inserted board or device ............................................................................... 286 198005387 Alarm due to inconsistent MP type..................... 287 198005388 Startup ile does not exist ................................ 287 198005398 Ofice ID is not set correctly with control shelf .............................................................................. 288 198005402 Database conig is different from ile named bootcfg.ini ...................................................................... 288 198005649 Port coniguration is incorrect ........................... 289 198005659 Formats of audio resource inconsistent .............. 290 198005889 Version Switches While Board Doesn't Reset ................................................................................ 290 198005890 Function EPLD Update Failure ........................... 291 198005891 Inconsistent BOOT/EPLD Version No. with Database Conigurations ......................................................... 291 198005892 Boot Version Fails to Write to Backup Region ......... 292 198007936 Memory ile buffer overlow .............................. 292 198015360 Microcode Is Abnormal .................................... 293 198018944 PVC link is down ............................................. 293 198019207 Near-End IMA Group Coniguration Failure.......... 294 198020225 Protocol stack requested system coniguration information timeout............................................................ 295 198023040 Number of alarms exceeds threshold. ................ 296 198025600 Connection Check be Disabled in board.............. 296 198066006 Broadband link congestion .............................. 297 198066013 MTP3 link congestion....................................... 298 198066018 Association congestion .................................... 298 198066021 STC ofice congestion ...................................... 299 198066027 SNTP failure ................................................... 299 198066031 OMP alarm pool is full, unable to store any more alarms. .......................................................................... 300 198066032 Loss of NTP time synchronisation ...................... 300 198066063 MTP3 link sending low control alarm ................. 301 198087251 FUC L3 software no response temporarily........... 301 198087380 TRX manual block alarm .................................. 302 198087482 Data loading exception alarm ........................... 302 198087513 Board Ethernet port overload alarm................... 303 198087768 Resource Availability Alarm of UPPB DSP ............ 303 Conidential and Proprietary Information of ZTE CORPORATION 285 ZXG10 iBSC Alarm Handling Reference 198005120 T Network Connection Not Conform to Configuration Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198005120 � Severity:Critical � � Description:T Network Connection Not Conform to Coniguration Alarm Type:Handling Alarm T network iber connection does not conform to optical interface connection relation conigured on the background. T network iber connection does not conform to optical interface connection relation conigured on the background. T Net switch of the shelf is in disorder. Modify the iber connection or the connection coniguration to keep the coniguration consistent with the physical connection. 198005123 Incorrect configuration for inserted board or device Alarm Property � Alarm Code:198005123 � Severity:Minor � � Description:Incorrect coniguration for inserted board or device Alarm Type:Handling Alarm Probable Cause 1. Incorrect board in slot Speciic Problem 1. Incorrect board in slot System Impact Handling Suggestion 2. Board hardware does not match the OMC-R coniguration. 2. Board hardware does not match the OMC-R coniguration. The board fails to be normally powered on. The services carried by the board are interrupted. 1. The NMS coniguration management interface gives the rack diagram. Select the board and check if the Basic Information and CPU Information of the rack are correct. If the settings are incorrect, delete the board and create a new one. 2. Check if a correct board is inserted in the slot on the rack. If not, insert the correct one. 286 Conidential and Proprietary Information of ZTE CORPORATION Chapter 4 Handling Alarm 198005387 Alarm due to inconsistent MP type Alarm Property � Alarm Code:198005387 � Severity:Major � � Description:Alarm due to inconsistent MP type Alarm Type:Handling Alarm Probable Cause 1. The MP type is changed on NMS and the board is not restarted. Speciic Problem 1. The MP type is changed on NMS and the board is not restarted. System Impact Handling Suggestion 2. The active MP type on the local board is not consistent with that conigured on NMS. 2. The active MP type on the local board is not consistent with that conigured on NMS. There is no impact on services 1. For CMP and SMP, reset the board. 2. For OMP, set the start mode as "foreground start" on NMS and then reset the board. Do as follows: On NMS software version management interface, select the menu for querying foreground (that is, RNC NE) board start mode. In the pop-up dialog box, set the start mode to "foreground start". 198005388 Startup file does not exist Alarm Property � Alarm Code:198005388 � Severity:Major � � Description:Startup ile does not exist Alarm Type:Handling Alarm Probable Cause The startup coniguration ile is deleted. System Impact This alarm may cause OMP work abnormally, and the entire network element services are affected. Speciic Problem Handling Suggestion The startup coniguration ile is deleted. 1. Reset the active and standby OMPs. 2. Replace the board. Conidential and Proprietary Information of ZTE CORPORATION 287 ZXG10 iBSC Alarm Handling Reference 198005398 Office ID is not set correctly with control shelf Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198005398 � Severity:Major � � Description:Ofice ID is not set correctly with control shelf Alarm Type:Handling Alarm The ofice ID of a shelf where DIP switch locates is different from that of a shelf where OMP locates. The ofice ID of a shelf where DIP switch locates is different from that of a shelf where OMP locates. The MAC address conlicts. The MAC and IP address veriication fails. All boards on the shelf can not be powered on. All services carried by the shelf are interrupted. Set the ofice ID of the shelf where DIP switch locates to be the same as that of OMP belonged shelf. 198005402 Database config is different from file named bootcfg.ini Alarm Property Probable Cause Speciic Problem System Impact 288 � Alarm Code:198005402 � Severity:Major � � Description:Database conig is different from ile named bootcfg.ini Alarm Type:Handling Alarm After the start information of OMP is modiied, the active and standby OMP boards are not restarted. After the start information of OMP is modiied, the active and standby OMP boards are not restarted. System startup is abnormal, MP may not work normally. Conidential and Proprietary Information of ZTE CORPORATION Chapter 4 Handling Alarm Handling Suggestion Restart the active and the standby OMP boards at the same time. 198005649 Port configuration is incorrect Alarm Property � Alarm Code:198005649 � Severity:Major � � Description:Port coniguration is incorrect Alarm Type:Handling Alarm Probable Cause 1. Port Coniguration is incorrect. Speciic Problem 1. Port Coniguration is incorrect. System Impact Handling Suggestion 2. Incorrect coniguration for this board. 2. Incorrect coniguration for this board. 1. The port fails to work in the preset mode. This causes the port to be unavailable and all services of the port are interrupted. 2. For Auto mode, the bandwidth of the external port becomes insuficient. As a result, some services of the port are interrupted. On NMS fault management interface, view the alarm details, which give the reason of mode error. You can quickly locate the handling method according to the reason of mode error. The handling suggestion for each reason of mode error is as follows: Speed mode error i. Determine the speed to be conigured. Replace the existing board with the one supporting the conigured speed mode. ii. For Force mode, conigure the port with the speed supported by the bottom layer in actual working status. Do as follows: On NMS coniguration management interface, in Basic Information tab of board property, set the speed in outer port information to the speed supported by the bottom layer in actual working status. iii. For Auto mode, re-conigure the expected speed and ensure that it is consistent with the actual port speed. Do as follows: On NMS coniguration management interface, in Basic Information tab of board property, set the speed in outer port information to the expected one. Duplex mode error i. Determine the required mode. Replace the existing board with the one supporting the mode conigured on BSC. ii. For Force mode, conigure the port with the duplex mode supported by the bottom layer in actual working status. Do as follows: On NMS coniguration management interface, in Basic Information tab of board property, set the work mode in outer port information to the work mode supported by the bottom layer in actual working status. iii. For Auto mode, re-conigure the expected duplex and ensure that it is consistent with the actual port duplex. Do as follows: On NMS coniguration management interface, in Basic Information tab of board property, set the work mode in outer port information to the expected one. Conidential and Proprietary Information of ZTE CORPORATION 289 ZXG10 iBSC Alarm Handling Reference 198005659 Formats of audio resource inconsistent Alarm Property � Alarm Code:198005659 � Severity:Major � � Description:Formats of audio resource inconsistent Alarm Type:Handling Alarm Probable Cause Different formats of tones can't coexist in the board. System Impact The current service cannot be used by DSP. Speciic Problem Handling Suggestion Different formats of tones can't coexist in the board. By using the formatting button of OMC background tools, set the audio format to the same audio format. 198005889 Version Switches While Board Doesn't Reset Alarm Property Probable Cause Speciic Problem System Impact 290 � Alarm Code:198005889 � Severity:Warning � � Description:Version Switches While Board Doesn't Reset Alarm Type:Handling Alarm 1. Appoint the version for OMP and select the option of restart after switch,but the version ile have existed on OMP's DOC0. 2. Swtich the BOOT version. 1. Appoint the version for OMP and select the option of restart after switch,but the version ile have existed on OMP's DOC0. 2. Swtich the BOOT version. The board version will not take effect if the board does not reset. Conidential and Proprietary Information of ZTE CORPORATION Chapter 4 Handling Alarm Handling Suggestion Restart the board manually. 198005890 Function EPLD Update Failure Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198005890 � Severity:Warning � � Description:Function EPLD Update Failure Alarm Type:Handling Alarm Function EPLD update failure,or the version ile of Function EPLD is bigger than 64K Function EPLD update failure,or the version ile of Function EPLD is bigger than 64K If the board is reset before the alarm is eliminated, the board may fail to boot. 1. Use the version management tool to switch to a correct functional EPLD version. 2. Replace the board. 198005891 Inconsistent BOOT/EPLD Version No. with Database Configurations Alarm Property Probable Cause Speciic Problem System Impact � Alarm Code:198005891 � Severity:Warning � � Description:Inconsistent BOOT/EPLD Version No. with Database Conigurations Alarm Type:Handling Alarm Inconsistent BOOT/EPLD version No. tions. Inconsistent BOOT/EPLD version No. tions. with database conigurawith database conigura- If the running EPLD version does not match database, the board may not function properly; if the running BOOT version does not matched database, the slave CPU of the multi-CPU board may fail to boot. Conidential and Proprietary Information of ZTE CORPORATION 291 ZXG10 iBSC Alarm Handling Reference Handling Suggestion Switch BOOT/EPLD again and restart the board manually. 198005892 Boot Version Fails to Write to Backup Region Alarm Property Alarm Code:198005892 � Severity:Warning � � Description:Boot Version Fails to Write to Backup Region Alarm Type:Handling Alarm Probable Cause Boot version fails to be written to backup region. System Impact BOOT backup version is unavailable. Speciic Problem Handling Suggestion Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion 292 � Boot version fails to be written to backup region. Switch BOOT again and restart the board manually. 198007936 Memory file buffer overflow � Alarm Code:198007936 � Severity:Major � � Description:Memory ile buffer overlow Alarm Type:Handling Alarm The transferred data records exceed the maximum capacity of the table, and the capacity of the receiver memory ile buffer is insuficient. The transferred data records exceed the maximum capacity of the table, and the capacity of the receiver memory ile buffer is insuficient. If the board is powering on, the excessive data records (beyond table capacity) are discarded, otherwise the synchronization will be aborted. 1. Lookup if the capacity of the table is correct, please make records of the alarm information and contact ZTE Corporation. 2. Synchronize the capacity tables, then synchronize all tables to the foreground and reboot the board. If the alarm still has not restored, please make records of the alarm information and contact ZTE Corporation. Conidential and Proprietary Information of ZTE CORPORATION Chapter 4 Handling Alarm 198015360 Microcode Is Abnormal Alarm Property � Alarm Code:198015360 � Severity:Major � � Description:Microcode Is Abnormal Alarm Type:Handling Alarm Probable Cause Network Processor hardware is faulty. System Impact The board will reboot. If the alarm can be restored after board rebooting, all board services during rebooting will be down, but access of new services to the board after rebooting will be successful. If the alarm cannot be restored after board rebooting, all board services during and after rebooting will be down. Speciic Problem Handling Suggestion Network Processor hardware is faulty. Wait for the board to reboot. If the alarm cannot be restored after board rebooting, unplug and then plug the board. If the alarm still cannot be restored, replace the board. 198018944 PVC link is down Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198018944 � Severity:Minor � � Description:PVC link is down Alarm Type:Handling Alarm 1. PVC connection for the equipment is loose or disconnected. PVC connection falls into the following three types. Fibber connection, carried by optical interface. E1/T1 connection, carried by IMA port. Fibber connection, carried by IMA port. 2. Continuity Check (CC) test is started at local end, but not started at opposite end. 1. PVC connection for the equipment is loose or disconnected. PVC connection falls into the following three types. Fibber connection, carried by optical interface. E1/T1 connection, carried by IMA port. Fibber connection, carried by IMA port. 2. Continuity Check (CC) test is started at local end, but not started at opposite end. PVC is in faulty status. All services on the PVC are interrupted. 1. Check alarm details on the NMS fault management interface to ind the PVC ID and locate the faulty port. For example, the PVC ID is 1. Select PVC Coniguration on the NMS Coniguration Management interface to ind a record with a PVC ID of 1. Check the record for the Subsystem NO, Unit NO, and ATM Port No. By using the information, you can ind the location of the corresponding interface board and port. Conidential and Proprietary Information of ZTE CORPORATION 293 ZXG10 iBSC Alarm Handling Reference 2. Check the relevant equipment according to the physical bearer type of the port. 1) If the faulty PVC port is carried by an optical interface, check the optical port and make sure that the ibber is well connected. Replace the ibber if necessary. 2) If the faulty PVC port is carried by an IMA port, check whether the corresponding IMA group/link has one of the following alarms. If yes, handle it according to the corresponding suggestions. a. 19207 Near-end IMA group coniguration failure b. 19213 LIF alarm of near-end receiving link c. 19214 LODS alarm of near-end receiving link d. 19215 RDI alarm of far end receiving Link 3. Check if the peer-end equipment is powered on successfully. If not, refer to the corresponding equipment maintenance manual to solve the problem. 4. Check whether the peer-end equipment has normal PVC status. If not, please refer to corresponding equipment maintenance manual to solve the problem. 5. Deactivate the CC test at the local end, or activate the CC test at the peer end. For IMAB/APBE board: To deactivate the CC test at the local end, start the test on the NMS Test Management interface, and then select "0: Deactivate CC" for activation type and "1: B-A" for test type (A stands for local end and B stands for peer end). To activate the CC test at the peer end, start the test on the NMS Test Management interface, and then select "1: Activate CC" for activation type and "1: B-A" for test type. For APBE2/DTA board: Modify PVC CCINFO parameter of coniguration to active or deactivate CC test. CC test parameter is same to APBE/IMAB. 198019207 Near-End IMA Group Configuration Failure Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion 294 � Alarm Code:198019207 � Severity:Major � � Description:Near-End IMA Group Coniguration Failure Alarm Type:Handling Alarm IMA group coniguration at local end and at opposite end is inconsistent. IMA group coniguration at local end and at opposite end is inconsistent. All services on the IMA port are interrupted. On NMS fault management interface , view alarm Details where information of the faulty IMA group is given. On NMS coniguration management interface (IMA group coniguration), locate the corresponding IMA group according to the information given in alarm Details. Compare the coniguration of the following parameters at both ends. If the coniguration at both ends is inconsistent, modify coniguration at either end to keep consistency. "Near-End Conidential and Proprietary Information of ZTE CORPORATION Chapter 4 Handling Alarm OMA Label" "Rx Frame Length (cells)" "Tx Frame Length (cells)" "Near-End Symmetry" 198020225 Protocol stack requested system configuration information timeout Alarm Property Probable Cause � Alarm Code:198020225 � Severity:Major � � Description:Protocol stack requested system coniguration information timeout Alarm Type:Handling Alarm 1. The EPU or RPU requests coniguration from the database, but the database makes no response. 2. Or the database has made a response but the content is incorrect. 3. The message that the EPU or RPU sends to the database is lost. Speciic Problem 4. The control-plane communication is broken. 1. The EPU or RPU requests coniguration from the database, but the database makes no response. 2. Or the database has made a response but the content is incorrect. 3. The message that the EPU or RPU sends to the database is lost. System Impact Handling Suggestion 4. The control-plane communication is broken. The protocol process could not enter working state. 1. RPU is rebooting when EPU registers to RPU. Y->No need to handle. N->Go to "2". 2. Check whether the home module MP and the local board system control are normal and whether their communication is normal. Y->Go to "5". N->Go to "3". 3. Unplug and plug the board. Reset the hardware. whether the alarm disappears. Check Y->End. N->Maybe the board hardware is abnormal, go to "4". Conidential and Proprietary Information of ZTE CORPORATION 295 ZXG10 iBSC Alarm Handling Reference 4. Replace with a new board and check whether the alarm disappears. Y->End. N->Go to "5". 5. Contact ZTE Corporation. 198023040 Number of alarms exceeds threshold. Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion Alarm Property Probable Cause Speciic Problem System Impact 296 � Alarm Code:198023040 � Severity:Major � � Description:Number of alarms exceeds threshold. Alarm Type:Handling Alarm This board has too many alarms so that the relevant alarm pool is full. This board has too many alarms so that the relevant alarm pool is full. Alarms may be lost, but there is no impact on user services. Check and remove the current alarms in the system. 198025600 Connection Check be Disabled in board � Alarm Code:198025600 � Severity:Warning � � Description:Connection Check be Disabled in board Alarm Type:Handling Alarm The connection check switch is off, causing PP service process unable to execute connection check. The connection check switch is off, causing PP service process unable to execute connection check. Board connection check disabled, automatic check of connection error cannot be performed. Thus the connection error might not be self-cured. Conidential and Proprietary Information of ZTE CORPORATION Chapter 4 Handling Alarm Handling Suggestion Please contact ZTE Corporation. 198066006 Broadband link congestion Alarm Property � Alarm Code:198066006 � Severity:Minor � � Description:Broadband link congestion Alarm Type:Handling Alarm Probable Cause 1. The conigured signaling PVC bandwidth is low. Speciic Problem 1. The conigured signaling PVC bandwidth is low. System Impact Handling Suggestion 2. The quality of physical transmission at bottom layer is poor. 2. The quality of physical transmission at bottom layer is poor. Link congestion leads to transmission delay. If congestion is not serious, service will not be affected. Otherwise, packet loss or call loss might occur, and access success rate of PS service might fall. 1. Check the value of "Peak trafic of Signaling Link" in MTP3B signaling performance statistic information. If the load nearly reaches 6000 when the congestion alarm occurs, upper layer trafic must be heavy. In this case, you need to increase PVC bandwidth or add links to share load. 2. Check alarms/notiications in NMS to see whether there is a physical transmission alarm/notiication that occurs simultaneously with this alarm. If yes, please solve the problem according to corresponding handling suggestions. The relevant physical transmission alarms/notiications are listed below by access mode. 1) Fiber Access Mode 1792 SDH/SONET fault 1824 Abnormal status in SDH/SONET 1825 SDH/SONET: Excessive Error Code 5639 High Error Rate of Optical Interface 2)E1 Access Mode 5647 High Error Rate at E1 Bottom Layer 519 Trunk error 520 Trunk abnormal 576 Trunk Slide 3. View the statistic performance data of SSCOP link. Check whether "Number of PDU Retransmitted" is retransmitted when the congestion alarm occurs. If yes, packets must be lost during transmission. Since packet loss may occur at opposite end, please try to solve the problem at opposite end. Conidential and Proprietary Information of ZTE CORPORATION 297 ZXG10 iBSC Alarm Handling Reference 198066013 MTP3 link congestion Alarm Property � Alarm Code:198066013 � Severity:Major � � Description:MTP3 link congestion Alarm Type:Handling Alarm Probable Cause 1. There are too many messages at upper layer. Speciic Problem 1. There are too many messages at upper layer. System Impact Handling Suggestion 2. The quality of bottom layer link is so poor that many messages are retransmitted. 2. The quality of bottom layer link is so poor that many messages are retransmitted. Link congestion will cause transmission delay. If congestion is not serious, services will not be affected. However, if it is serious, packet loss or call loss may occur, and access success rate of PS services may fall. 1. Add links to the ofice, which provides support for the congested link. 2. Take the following measures to improve transmission quality of physical links. Replace physical links. Ensure that connectors are in well contact and cables are correctly connected. 198066018 Association congestion Alarm Property � Alarm Code:198066018 � Severity:Minor � � Description:Association congestion Alarm Type:Handling Alarm Probable Cause 1. Transmission quality of bottom layer link is poor. Speciic Problem 1. Transmission quality of bottom layer link is poor. System Impact Handling Suggestion 298 2. Upper layer trafic in sending service data is heavy. 2. Upper layer trafic in sending service data is heavy. Link congestion will cause transmission delay. If congestion is not serious, services will not be affected. However, if it is serious, packet loss or call loss may occur, and access success rate of PS services may fall. 1. Check network cable connection. Ensure that the network cable is tightly inserted. Conidential and Proprietary Information of ZTE CORPORATION Chapter 4 Handling Alarm 2. Add association links to the ofice that is in service for the congested association. 3. If intermediate equipment exists between local end and opposite end, check the transmission quality of intermediate equipment. 198066021 STC office congestion Alarm Property � Alarm Code:198066021 � Severity:Minor � � Description:STC ofice congestion Alarm Type:Handling Alarm Probable Cause At least one association connected to the ofice is congested. System Impact Association congestion leads to transmission delay. If congestion is not serious, service is not affected. Speciic Problem Handling Suggestion At least one association connected to the ofice is congested. Association congestion exists in this ofice,refer to the corresponding alarm handling suggestion. Related alarm: 8402688 Association congestion. 198066027 SNTP failure Alarm Property Probable Cause � Alarm Code:198066027 � Severity:Minor � � Description:SNTP failure Alarm Type:Handling Alarm 1. SNTP server does not exist or it works abnormally. 2. The conigured SNTP IP address in database is different from its real IP address. 3. The communication between RNC and SNTP server is broken. Speciic Problem 4. The time synchronization period conigured in the database might be 0. 1. SNTP server does not exist or it works abnormally. 2. The conigured SNTP IP address in database is different from its real IP address. 3. The communication between RNC and SNTP server is broken. 4. The time synchronization period conigured in the database might be 0. Conidential and Proprietary Information of ZTE CORPORATION 299 ZXG10 iBSC Alarm Handling Reference System Impact Handling Suggestion SNTP synchronization failure may cause time difference between system time and real time. For example, the real time is 1:00 am, but the system time is 2:00 am. Since the system clock frequency is correct, services will not be affected. 1. Alarm details are displayed in NMS Alarm Management interface, where fault type is given. You can easily ind handling suggestions according to the fault type. The handling suggestions for each type are described as below. 1. Invalid database coniguration. In NMS Coniguration Management interface, click RNC Ground Resource Management to check whether the IP address of SNTP server is invalid, or SNTP synchronization period is wrong. If the IP address of SNTP server is 255.255.255.255 or SNTP synchronization period is 0, please correct the coniguration. 2. Failure in getting time from SNTP server 1) Ensure that SNTP server exists and it works normally. 2) Ensure that the conigured IP address of SNTP server in database is the same as its real IP address. 198066031 OMP alarm pool is full, unable to store any more alarms. Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198066031 � Severity:Major � � Description:OMP alarm pool is full, unable to store any more alarms. Alarm Type:Handling Alarm There are too many system alarms. The alarm pool is full of system alarms. There are too many system alarms. The alarm pool is full of system alarms. Alarms may be lost, but there is no impact on user services. Delete the trivial alarms on NMS fault management interface. 198066032 Loss of NTP time synchronisation Alarm Property 300 � Alarm Code:198066032 � Severity:Minor � Description:Loss of NTP time synchronisation Conidential and Proprietary Information of ZTE CORPORATION Chapter 4 Handling Alarm � Alarm Type:Handling Alarm Probable Cause 1. Link between OMP and RPU is down. Speciic Problem 1. Link between OMP and RPU is down. System Impact Handling Suggestion 2. NTP time and local time differs greatly. 2. NTP time and local time differs greatly. NTP time synchronization terminates, leading to interruption of ongoing services. On NMS fault management interface, check if the alarm related to RPU board exists. If yes, refer to the corresponding alarm handling suggestion. Related alarm: 8393988 Control plane communication abnormal between MP and OMP 198066063 MTP3 link sending flow control alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198066063 � Severity:Major � � Description:MTP3 link sending low control alarm Alarm Type:Handling Alarm The sending payload of MTP3 link exceeds the threshold set by sending low control. The sending payload of MTP3 link exceeds the threshold set by sending low control. WCS network element, for call setup request message, the link load exceeds a certain percentage threshold will be rejected in order to achieve out of the link load does not exceed the purpose of setting threshold; non-WCS network element, does not affect. 1. Reduce trafic or add links. 2. Increase low control threshold. 198087251 FUC L3 software no response temporarily Alarm Property Probable Cause � Alarm Code:198087251 � Severity:Warning � � Description:FUC L3 software no response temporarily Alarm Type:Handling Alarm MO software (has/has no) response temporarily (set by CMB) Conidential and Proprietary Information of ZTE CORPORATION 301 ZXG10 iBSC Alarm Handling Reference Speciic Problem System Impact Handling Suggestion MO software (has/has no) response temporarily (set by CMB) FUC operation status cannot be detected from background, but callings are not affected. 1. Reset this module and make it work properly. 2. Check whether environment temperature exceeds the allowable operating enviroment temperature of equipment. If yes, adjust the environment; if not, re-plug the board and check whether alarm restores. 3. If the alarm doesn't restore, reset CMB when service is idle. 4. If it is software problem, upgrade the version then. 5. If the alarm still exists, replace corresponding DTRU. 198087380 TRX manual block alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087380 � Severity:Minor � � Description:TRX manual block alarm Alarm Type:Handling Alarm The TRX indicated in the alarm is manually blocked. The TRX indicated in the alarm is manually blocked. The TRX is out of service. On NMS Dynamic Data Management interface, check TRX state in TRX Management tab, and manually unblock the blocked TRX. 198087482 Data loading exception alarm Alarm Property Probable Cause 302 � Alarm Code:198087482 � Severity:Major � � Description:Data loading exception alarm Alarm Type:Handling Alarm Data exception is detected when database is loading or data is synchronizing. Please refer to R_DATAERRLOG table of alarm related module, and modify or delete abnormal data. Notice the following information in the table: NAME: the error table KEYINDEXINFO: the main index of the error data storage information DATAERRSTR: error info string Conidential and Proprietary Information of ZTE CORPORATION Chapter 4 Handling Alarm Speciic Problem System Impact Handling Suggestion Data exception is detected when database is loading or data is synchronizing. Please refer to R_DATAERRLOG table of alarm related module, and modify or delete abnormal data. Notice the following information in the table: NAME: the error table KEYINDEXINFO: the main index of the error data storage information DATAERRSTR: error info string Database is abnormal, service has exception, etc. 1. Refer to R_DATERRLOG table to modify the error data, and after that, please synchronize all data to conirm the error is eliminated. 2. Before master to slave exchange, if this alarm exists in the old master board.Please synchronize all data to conirm whether the exception exists in the new master board after the exchange. 198087513 Board Ethernet port overload alarm Alarm Property � Alarm Code:198087513 � Severity:Major � � Description:Board Ethernet port overload alarm Alarm Type:Handling Alarm Probable Cause Ethernet port resource allocation is unbalanced and overloaded. System Impact Impact service quality Speciic Problem Handling Suggestion Ethernet port resource allocation is unbalanced and overloaded. Redistribute resources and balance them. 198087768 Resource Availability Alarm of UPPB DSP Alarm Property Probable Cause � Alarm Code:198087768 � Severity:Major � � Description:Resource Availability Alarm of UPPB DSP Alarm Type:Handling Alarm 1. Failure ratio for allocating memory exceeds setting threshold. 2. Use ratio of mac instance exceeds setting threshold. 3. Use ratio of bssgp instance exceeds setting threshold. Conidential and Proprietary Information of ZTE CORPORATION 303 ZXG10 iBSC Alarm Handling Reference 4. Use ratio of mac-tlli index exceeds setting threshold. 5. Use ratio of bssgp-tlli index exceeds setting threshold. 6. Use ratio of radio channel instance exceeds setting threshold. Speciic Problem 7. Use ratio of TS instance exceeds setting threshold. 1. Failure ratio for allocating memory exceeds setting threshold. 2. Use ratio of mac instance exceeds setting threshold. 3. Use ratio of bssgp instance exceeds setting threshold. 4. Use ratio of mac-tlli index exceeds setting threshold. 5. Use ratio of bssgp-tlli index exceeds setting threshold. 6. Use ratio of radio channel instance exceeds setting threshold. System Impact Handling Suggestion 7. Use ratio of TS instance exceeds setting threshold. Congestion or exception may occur in the DSP, new PS service of the DSP is affected. 1. Checking whether alram thresholds of all resources are lower, if alarm threshold of failure ratio for allocating memory is less than ive percent or alarm threshold of other resources is less than seventy percent, increasing alarm thresold and keeping on observation. 2. If failure ratio of allocating memory exceeds alarm threshold, checking RLC throughput and TBF establishing success rate of correlative cells which are handled by this DSP. While RLC throughput is changeless or decreasing, and TBF establishing success rate drops largeish percent, consider resetting the DSP. Keeping on observation in other situations. 3. If use ratio of mac instance exceeds alarm threshold, or use ratio of bssgp instance exceeds alram threshold, or use ratio of mac-tlli index exceeds alram threshold, or use ratio of bssgp-tlli index exceeds alarm threshold, or use ratio of radio channel instance exceeds alarm threshold, or use ratio of TS instance exceeds alarm threshold, checking RLC throughput and TBF establishing success rate of correlative cells which are handled by this DSP. While RLC throughput is changeless or decreasing, and TBF establishing success rate drops largeish percent, consider resetting the DSP. In other situations, consider moving some cells of this DSP to other idle DSP. 304 Conidential and Proprietary Information of ZTE CORPORATION Chapter 5 Environment Alarm Table of Contents 198025856 Rack temperature is high ................................. 305 198025857 Low temperature in Rack ................................ 306 198025858 Room temperature is higher than high threshold .................................................................................... 307 198025859 Room temperature is lower than low threshold .................................................................................... 307 198025860 Rack voltage is high ....................................... 308 198025861 rack voltage is low .......................................... 309 198025862 Humidity is high ............................................. 309 198025863 Humidity is low............................................... 310 198025864 Fault in fan plug-in box ................................... 310 198025865 Rack door alarm ............................................. 311 198025866 Smoke detected ............................................. 311 198025867 Infrared alarm ................................................ 312 198025868 Lightning alarm .............................................. 313 198025869 Loss of DC power supply to rack ....................... 313 198029184 SNTP server is unavailable ............................... 314 198025856 Rack temperature is high Alarm Property Probable Cause � Alarm Code:198025856 � Severity:Minor � � Description:Rack temperature is high Alarm Type:Environment Alarm 1. Fan is not working. 2. Fan has failed. 3. No fan connected. Speciic Problem 4. Temperature sensor is faulty or setting is incorrect. 1. Fan is not working. 2. Fan has failed. 3. No fan connected. 4. Temperature sensor is faulty or setting is incorrect. Conidential and Proprietary Information of ZTE CORPORATION 305 ZXG10 iBSC Alarm Handling Reference System Impact Handling Suggestion 1. If an unreasonable threshold is conigured, services will not be affected. 2. If the alarm is caused by high rack temperature, board may work abnormally and board services may be interrupted. 1. In NMS Coniguration Management interface, click Power Board Alarm Parameters to view the upper threshold of rack temperature. If the coniguration is unreasonable, please modify it. The recommended value of upper threshold is 70 degrees in Celsius. 2. Check the thermometer in equipment room to see if the actual temperature is too high. If yes, take necessary cooling measures. 3. Remove dust from air intake and outlet of the rack. Remove any obstacle nearby which may affect ventilation. 4. Ensure that the rack fan works normally. 198025857 Low temperature in Rack Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198025857 � Severity:Minor � � Description:Low temperature in Rack Alarm Type:Environment Alarm 1. Threshold is incorrect. 2. Temperature sensor is not working 3. External room heating control not working. 1. Threshold is incorrect. 2. Temperature sensor is not working 3. External room heating control not working. 1. If an unreasonable threshold is conigured, services will not be affected. 2. If the alarm is caused by low rack temperature, board may work abnormally and board services may be interrupted. 1. In NMS Coniguration Management interface, click Power Board Alarm Parameters to view the lower threshold of rack temperature. If the coniguration is unreasonable, please modify it. The recommended value of lower threshold is 0 degrees Celsius. 2. Check the thermometer in equipment room to see if the actual temperature is too low. If yes, take necessary warming measures. 3. Setting the sensor correctly. 306 Conidential and Proprietary Information of ZTE CORPORATION Chapter 5 Environment Alarm 198025858 Room temperature is higher than high threshold Alarm Property � Alarm Code:198025858 � Severity:Minor � � Description:Room temperature is higher than high threshold Alarm Type:Environment Alarm Probable Cause 1. Threshold coniguration is unreasonable. Speciic Problem 1. Threshold coniguration is unreasonable. System Impact Handling Suggestion 2. Actual temperature in equipment room is too high. 2. Actual temperature in equipment room is too high. 1. If an unreasonable threshold is conigured, services will not be affected. 2. If the alarm is caused by high room temperature, board may work abnormally and board services may be interrupted. 1. On NMS coniguration management interface (power board alarm parameters), check the upper limit of equipment room temperature. Modify the threshold value if the previous coniguration is unreasonable. The recommended high threshold value is 40. 2. Check the thermometer in equipment room to see if the actual temperature is too high. If yes, take necessary cooling and ventilation measures. 198025859 Room temperature is lower than low threshold Alarm Property Probable Cause Speciic Problem � Alarm Code:198025859 � Severity:Minor � � Description:Room temperature is lower than low threshold Alarm Type:Environment Alarm 1. The conigured threshold is unreasonable. 2. Actual temperature in equipment room is too low. 3. Setting of the sensor is incorrect. 1. The conigured threshold is unreasonable. Conidential and Proprietary Information of ZTE CORPORATION 307 ZXG10 iBSC Alarm Handling Reference 2. Actual temperature in equipment room is too low. System Impact Handling Suggestion 3. Setting of the sensor is incorrect. 1. If an unreasonable threshold is conigured, services will not be affected. 2. If the alarm is caused by low room temperature, board may work abnormally and board services may be interrupted. 1. In NMS Coniguration Management interface, click Power Board Alarm Parameters to view the lower threshold of room temperature. If the coniguration is unreasonable, please modify it. The recommended value of lower threshold is 0 degrees Celsius. 2. Check the thermometer in equipment room to see if the actual temperature is too low. If yes, take necessary warming measures. 3. Setting the sensor correctly. 198025860 Rack voltage is high Alarm Property � Alarm Code:198025860 � Severity:Minor � � Description:Rack voltage is high Alarm Type:Environment Alarm Probable Cause 1. The conigured threshold is unreasonable. Speciic Problem 1. The conigured threshold is unreasonable. System Impact Handling Suggestion 2. Actual voltage is too high. 2. Actual voltage is too high. 1. If an unreasonable threshold is conigured, services will not be affected. 2. If the alarm is caused by high voltage, board may work abnormally and board services may be interrupted. 1. In NMS Coniguration Management interface, click Power Board Alarm Parameters to view the upper threshold of rack voltage. If the coniguration is unreasonable, please modify it. For 48V power supply, the recommended value of upper threshold is 57V; for 60V power supply, the recommended value is 7 2. Find out which line voltage exceeds upper threshold by using the voltage index given in alarm details. Lower down the input voltage of this line. 308 Conidential and Proprietary Information of ZTE CORPORATION Chapter 5 Environment Alarm 198025861 rack voltage is low Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198025861 � Severity:Minor � � Description:rack voltage is low Alarm Type:Environment Alarm 1. Voltage value is under the low threshold. 2. The setting of the votage detector is error. 3. Power input of a road may have been disconnected. 1. Voltage value is under the low threshold. 2. The setting of the votage detector is error. 3. Power input of a road may have been disconnected. 1. If an unreasonable threshold is conigured, services will not be affected. 2. If the alarm is caused by low voltage, board may work abnormally and board services may be interrupted. 1. In NMS Coniguration Management interface, click Power Board Alarm Parameters to view the lower threshold of rack voltage. If the coniguration is unreasonable, please modify it. For 48V power supply, the recommended value of lower threshold is 40V; for 60V power supply, the recommended value is 50. 2. Find out which line voltage is below lower threshold by using the voltage index given in alarm details. Increase the input voltage of this line. 198025862 Humidity is high Alarm Property � Alarm Code:198025862 � Severity:Minor � � Description:Humidity is high Alarm Type:Environment Alarm Probable Cause 1. The conigured threshold is unreasonable. Speciic Problem 1. The conigured threshold is unreasonable. System Impact 2. Actual humidity in equipment room is too high. 2. Actual humidity in equipment room is too high. 1. If an unreasonable threshold is conigured, services will not be affected. 2. If the alarm is caused by high room humidity, board may work abnormally and board services may be interrupted. Conidential and Proprietary Information of ZTE CORPORATION 309 ZXG10 iBSC Alarm Handling Reference Handling Suggestion 1. In NMS Coniguration Management interface, click Power Board Alarm Parameters to view the upper threshold of room humidity. If the coniguration is unreasonable, please modify it. The recommended value of upper threshold is 90. 2. Check the hygrometer in equipment room to see if the actual humidity is too high. If yes, take necessary dehumidifying measures. 198025863 Humidity is low Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198025863 � Severity:Minor � � Description:Humidity is low Alarm Type:Environment Alarm 1. The conigured threshold is unreasonable. 2. Actual humidity in equipment room is too low. 3. Setting of the sensor is incorrect. 1. The conigured threshold is unreasonable. 2. Actual humidity in equipment room is too low. 3. Setting of the sensor is incorrect. 1. If an unreasonable threshold is conigured, services will not be affected. 2. If the alarm is caused by low room humidity, board may work abnormally and board services may be interrupted. 1. In NMS Coniguration Management interface, click Power Board Alarm Parameters to view the lower threshold of room humidity. If the coniguration is unreasonable, please modify it. The recommended value of upper threshold is 90. 2. Check the hygrometer in equipment room to see if the actual humidity is too low. If yes, take necessary humidifying measures. 3. Setting the sensor correctly. 198025864 Fault in fan plug-in box Alarm Property � Alarm Code:198025864 � Severity:Minor � � 310 Description:Fault in fan plug-in box Alarm Type:Environment Alarm Conidential and Proprietary Information of ZTE CORPORATION Chapter 5 Environment Alarm Probable Cause Speciic Problem System Impact Handling Suggestion 1. The fan subrack is not tightly inserted into the rack. 2. The fan subrack has a hardware fault. 3. Setting of the sensor is incorrect. 1. The fan subrack is not tightly inserted into the rack. 2. The fan subrack has a hardware fault. 3. Setting of the sensor is incorrect. This alarm may cause very high rack temperature. As a result, the relevant board may work abnormally and board services may be interrupted. 1. Check whether the FAN subrack is tightly inserted into the rack. If no, unplug and plug it. 2. Replace the fan subrack. 3. Setting the sensor correctly. 198025865 Rack door alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198025865 � Severity:Minor � � Description:Rack door alarm Alarm Type:Environment Alarm 1. The rack door is not closed. 2. The connection for door access control device is incorrect. 3. Setting of the sensor is incorrect. 1. The rack door is not closed. 2. The connection for door access control device is incorrect. 3. Setting of the sensor is incorrect. Services won't be affected, but there is a potential safety problem. 1. Open and close the rack door so that it is tightly closed. 2. Open the rack door to check the door access control device. Ensure that it is correctly installed and connected. After that, close the rack door. 3. Setting the sensor correctly. 198025866 Smoke detected Alarm Property � Alarm Code:198025866 � Severity:Minor � Description:Smoke detected Conidential and Proprietary Information of ZTE CORPORATION 311 ZXG10 iBSC Alarm Handling Reference Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Type:Environment Alarm 1. The alarm device is faulty. 2. The smoke density in equipment room is too high. 3. Setting of the sensor is incorrect. 1. The alarm device is faulty. 2. The smoke density in equipment room is too high. 3. Setting of the sensor is incorrect. Services won't be affected, but there is a potential safety problem. 1. Quick ind the origin of smog. 2. If there is no smog in the equipment room, replace the smog detector. 3. Setting the sensor correctly. 198025867 Infrared alarm Alarm Property Probable Cause � Alarm Code:198025867 � Severity:Minor � � Description:Infrared alarm Alarm Type:Environment Alarm 1. Heat source (e.g. animal/human being) approaches near. 2. The coniguration of infra-red sensor is wrong. 3. The infrared sensor is faulty. Speciic Problem 4. Setting of the sensor is incorrect. 1. Heat source (e.g. animal/human being) approaches near. 2. The coniguration of infra-red sensor is wrong. 3. The infrared sensor is faulty. System Impact Handling Suggestion 4. Setting of the sensor is incorrect. 1. If the coniguration of infra-red sensor is wrong, the system won't be affected. 2. If the infra-red light in the equipment room is over threshold, there is a potential safety problem. 1. Does an animal or a person approach near the infrared sensor? If yes, remove the heat source. If no, please check the coniguration of infra-red sensor. If the coniguration is correct, sensor sensitivity may be reduced to some extent. 2. The infra-red sensor is faulty. Replace the sensor. 3. Setting the sensor correctly. 312 Conidential and Proprietary Information of ZTE CORPORATION Chapter 5 Environment Alarm 198025868 Lightning alarm Alarm Property � Alarm Code:198025868 � Severity:Minor � � Description:Lightning alarm Alarm Type:Environment Alarm Probable Cause 1. Outdoor unit or equipment damaged by lightening Speciic Problem 1. Outdoor unit or equipment damaged by lightening System Impact Handling Suggestion 2. Setting of the sensor is incorrect. 2. Setting of the sensor is incorrect. The board may work abnormally due to lightning stroke. Accordingly, board services will be interrupted. 1. Check earthing connection. 2. Check lightning protection antenna. 3. Setting the sensor correctly. 198025869 Loss of DC power supply to rack Alarm Property � Alarm Code:198025869 � Severity:Minor � � Description:Loss of DC power supply to rack Alarm Type:Environment Alarm Probable Cause 1. Circuit breaker has tripped. Speciic Problem 1. Circuit breaker has tripped. System Impact Handling Suggestion 2. No incoming DC supply from rectiier 2. No incoming DC supply from rectiier This shelf can not be supplied with power. All boards on the shelf can not work and board services are interrupted. 1. Is this shelf needed? 1. If yes, ensure that the atmosphere switch is closed and ALM indicator is normal. 2. If no, screen the function of monitoring atmosphere switch. In NMS Coniguration Management interface, click Power Board Alarm Parameters; then set the status of atmosphere switch to be screened. 3. Setting the sensor correctly. Conidential and Proprietary Information of ZTE CORPORATION 313 ZXG10 iBSC Alarm Handling Reference 198029184 SNTP server is unavailable Alarm Property � Alarm Code:198029184 � Severity:Minor � � Description:SNTP server is unavailable Alarm Type:Environment Alarm Probable Cause SNTP server is faulty or communication broken. System Impact NO impact to trafic only loss of Time synchronisation data for time stamp of events and reporting. Speciic Problem Handling Suggestion SNTP server is faulty or communication broken. 1. Check whether the physical link is normal by using Ping command. Y->Solve the physical link problem. N->go to "2". 2. Check whether the server IP is correct. Y->Conigure the IP address. N->Contact ZTE. 314 Conidential and Proprietary Information of ZTE CORPORATION Chapter 6 QoS Alarm Table of Contents 198015361 Ring and queue overload alarm......................... 315 198023296 Inter-board message communication low rate exceeds the alarm threshold ............................................. 316 198066069 The number of times of signaling data transfer exceeds the allowed threshold of the license ....................... 316 198087341 FR congestion ................................................ 317 198087344 MSC overload control alarm at FUC mode........... 317 198087345 CPU overload control alarm at FUC mode ........... 318 198087346 Signaling point congestion control alarm at FUC mode ............................................................................. 318 198087347 MSC overload control alarm at SYS mode........... 319 198087348 CPU overload control alarm at SYS mode ........... 319 198087349 Signaling point congestion control alarm at SYS mode ............................................................................. 320 198087350 CS CCCH overload .......................................... 320 198087351 PS CCCH overload........................................... 321 198087435 A interface resource statistic alarm.................... 321 198087436 NSVC resource statistics alarm ......................... 322 198087437 TCH resources statistics alarm .......................... 322 198087438 Assignment failure alarm ................................. 323 198087468 LAPD congestion alarm .................................... 323 198087506 NSE block alarm ............................................. 324 198087507 SGSN is blocked. ............................................ 324 198087758 Manual User Access control alarm ..................... 325 198087759 CPU overload control alarm at Paging mode ......... 325 198015361 Ring and queue overload alarm Alarm Property � Alarm Code:198015361 � Severity:Major � � Description:Ring and queue overload alarm Alarm Type:Qos Alarm Probable Cause Service overload in the board. System Impact Service quality will get bad, even make service lost. Speciic Problem Service overload in the board. Conidential and Proprietary Information of ZTE CORPORATION 315 ZXG10 iBSC Alarm Handling Reference Handling Suggestion You should readjust board's resource to reduce service load in this board. 198023296 Inter-board message communication flow rate exceeds the alarm threshold Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198023296 � Severity:Minor � � Description:Inter-board message communication low rate exceeds the alarm threshold Alarm Type:Qos Alarm The conigured alarm threshold is less than the usual inter-board communication trafic in input and output directions of the board control plane. The conigured alarm threshold is less than the usual inter-board communication trafic in input and output directions of the board control plane. Packet of the control plane loss might occur. No impact on user service. On NMS coniguration management interface, check if the conigured alarm threshold of communication trafic in input and output directions of the board control plane is too low. Recommended value: 0xffffffff(4096M). 198066069 The number of times of signaling data transfer exceeds the allowed threshold of the license Alarm Property � Alarm Code:198066069 � Severity:Major � � 316 Description:The number of times of signaling data transfer exceeds the allowed threshold of the license Alarm Type:Qos Alarm Conidential and Proprietary Information of ZTE CORPORATION Chapter 6 QoS Alarm Probable Cause Speciic Problem System Impact Handling Suggestion The number of transfer that passes MTP3/M3UA/SCCP/SUA exceed the permission of license. The number of transfer that passes MTP3/M3UA/SCCP/SUA exceed the permission of license. The data transferred may be discarded when The number of transfer exceed the permission of license. Contact the related personnel and get proper license again. 198087341 FR congestion Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087341 � Severity:Minor � � Description:FR congestion Alarm Type:Qos Alarm When Gb interface connects through FR, if the number of frames with BECN set to 1 is more than or equal to the ones with BECN set to 0 for a certain NS-VC in a unit time, then it is considered as backward congestion. When Gb interface connects through FR, if the number of frames with BECN set to 1 is more than or equal to the ones with BECN set to 0 for a certain NS-VC in a unit time, then it is considered as backward congestion. Quality of PS service for some users degrades. Increase BRCH links or BRCH time slots. 198087344 MSC overload control alarm at FUC mode Alarm Property � Alarm Code:198087344 � Severity:Minor � � Description:MSC overload control alarm at FUC mode Alarm Type:Qos Alarm Probable Cause MSC sends overload message, and BSC starts FUC low control. System Impact Some users fail to gain access. Speciic Problem Handling Suggestion MSC sends overload message, and BSC starts FUC low control. BSC can implement low control automatically. Observe the alarm without taking any handling measures. Conidential and Proprietary Information of ZTE CORPORATION 317 ZXG10 iBSC Alarm Handling Reference 198087345 CPU overload control alarm at FUC mode Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087345 � Severity:Minor � � Description:CPU overload control alarm at FUC mode Alarm Type:Qos Alarm The CPU load exceeds the low control threshold in system coniguration parameter setting. The CPU load exceeds the low control threshold in system coniguration parameter setting. Some users fail to gain access. 1. On NMS Fault Management interface, check alarm details, which indicate the low control level. If the low control level is 3 or lower than 3, observe 3 minutes and wait for alarm restoring. 2. Block some cells in Dynamic Data Management interface to prevent CPU load from further increasing. After the alarm is eliminated, unblock related cells. 198087346 Signaling point congestion control alarm at FUC mode Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion 318 � Alarm Code:198087346 � Severity:Minor � � Description:Signaling point congestion control alarm at FUC mode Alarm Type:Qos Alarm MSC sends the signaling congestion message. BSC starts FUC low control. MSC sends the signaling congestion message. BSC starts FUC low control. Some users fail to gain access. BSC can implement low control automatically. Observe the alarm without taking any handling measures. Conidential and Proprietary Information of ZTE CORPORATION Chapter 6 QoS Alarm 198087347 MSC overload control alarm at SYS mode Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087347 � Severity:Minor � � Description:MSC overload control alarm at SYS mode Alarm Type:Qos Alarm MSC sends the overload message. BSC starts system message low control. MSC sends the overload message. BSC starts system message low control. Some users fail to gain access. BSC can implement low control automatically. Observe the alarm without taking any handling measures. 198087348 CPU overload control alarm at SYS mode Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087348 � Severity:Minor � � Description:CPU overload control alarm at SYS mode Alarm Type:Qos Alarm The excessive trafic causes the CPU load to exceed the low control threshold in module parameter setting. The excessive trafic causes the CPU load to exceed the low control threshold in module parameter setting. The system automatically initiates low control management and induce unavailable access for some users. If the trafic is still excessive after low control, CPU load will further increase. 1. On NMS Fault Management interface, check alarm details, which indicate the low control level. If the low control level is 3 or lower than 3, observe 3 minutes and wait for alarm restoring. 2. Block some cells in Dynamic Data Management interface to prevent CPU load from further increasing. After the alarm is eliminated, unblock related cells. Conidential and Proprietary Information of ZTE CORPORATION 319 ZXG10 iBSC Alarm Handling Reference 198087349 Signaling point congestion control alarm at SYS mode Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087349 � Severity:Minor � � Description:Signaling point congestion control alarm at SYS mode Alarm Type:Qos Alarm The excessive trafic causes the MSC to send signaling congestion message. BSC starts system message low control. The excessive trafic causes the MSC to send signaling congestion message. BSC starts system message low control. The system automatically initiates low control management and cause unavailable access for some users. If the trafic is still excessive after low control, it will induce A interface signaling to interrupt and service interruption. 1. On NMS fault management interface, check alarm details, which indicate the low control level. If the low control level is 3 or lower than 3, observe 3 minutes and wait for alarm restoring. 2. Block some cells in Dynamic Data Management interface to prevent CPU load from further increasing. After the alarm is eliminated, unblock related cells. 198087350 CS CCCH overload Alarm Property Alarm Code:198087350 � Severity:Minor � � Description:CS CCCH overload Alarm Type:Qos Alarm Probable Cause Too many MSs request to gain access on CS CCH. System Impact The system automatically initiates low control management, causing some MSs under this cell to fail to access CS services. Speciic Problem Handling Suggestion 320 � Too many MSs request to gain access on CS CCH. 1. On NMS fault management interface, check alarm details, which indicate the low control level. If the low control level is 8 or lower than 8, observe 10 minutes and wait for alarm restoring. Conidential and Proprietary Information of ZTE CORPORATION Chapter 6 QoS Alarm 2. If the alarm occurs frequently, add CS CCCH to the channel information under BTS coniguration on Coniguration Management Interface, or expand the capacity of overload site or share trafic. 198087351 PS CCCH overload Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087351 � Severity:Minor � � Description:PS CCCH overload Alarm Type:Qos Alarm Too many MSs request to gain access on PS CCH. Too many MSs request to gain access on PS CCH. The system automatically initiates low control management, causing some MSs under this cell to fail to access PS services. 1. On NMS fault management interface, check alarm details, which indicate the low control level. If the low control level is 8 or lower than 8, observe 10 minutes and wait for alarm restoring. 2. If the alarm occurs frequently, add CS CCCH to the channel information under BTS coniguration on Coniguration Management Interface, or expand the capacity of overload site or share trafic. 198087435 A interface resource statistic alarm Alarm Property Probable Cause Speciic Problem System Impact � Alarm Code:198087435 � Severity:Major � � Description:A interface resource statistic alarm Alarm Type:Qos Alarm Alarm is triggered when A interface resource block rate in OMP/IMP is higher than the threshold. Alarm is triggered when A interface resource block rate in OMP/IMP is higher than the threshold. If the alarm is not addressed, long-time CS service access will be affected, and telephone is hard or event not able to get through, thus affecting trafic. Conidential and Proprietary Information of ZTE CORPORATION 321 ZXG10 iBSC Alarm Handling Reference Handling Suggestion 1. On NMS Dynamic Data Management interface, check if A interface circuit state is normal. 1. Check DTB board of A interface or the physical connection of E1 on SPB/SPB2, and ensure they are ok. 2. Check whether MSC is blocked or uninstalled. If yes, contact MSC maintenance personnel to check MSC. 3. Check whether PCM is blocked. If yes, unblock PCM. 4. Check whether DRTB/DRTB2 board works properly. If not, reset, re-insert or replace the board. 5. Check whether PCM number in BSC side is the same as the one in MSC side. If not, modify BSC side PCM number to be consistent with MSC one, and observe whether the alarm is restored. 198087436 NSVC resource statistics alarm Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087436 � Severity:Major � � Description:NSVC resource statistics alarm Alarm Type:Qos Alarm Alarm is triggered whenNSVC resource block rate in OMP/IMP is higher than the threshold. Alarm is triggered whenNSVC resource block rate in OMP/IMP is higher than the threshold. PS service of some cells is unavailable. 1. Check whether FR device failure alarm exists persistently. If yes, please refer to the addressing method of " 2. FR device failure" alarm. After eliminating FR device failure alarm, observe whether this alarm disappears. 2. Check whether NSVC data coniguration is the same as SGSN side. If not, modify NSVC data coniguration to be consistent with SGSN side, and observe whetheralarm disappears. 3. Check whether manually blocked NSVC exists, if so, manually unblock it. 198087437 TCH resources statistics alarm Alarm Property 322 � � Alarm Code:198087437 Description:TCH resources statistics alarm Conidential and Proprietary Information of ZTE CORPORATION Chapter 6 QoS Alarm � Probable Cause Speciic Problem System Impact Handling Suggestion � Severity:Major Alarm Type:Qos Alarm Alarm is triggered when CMP/IMP TCH resource block rate is higher than the threshold. Alarm is triggered when CMP/IMP TCH resource block rate is higher than the threshold. If the alarm were not handled, it might induce call failure. 1. Check whether channels are manually blocked, if yes, unblock them. 2. Check whether TRX state is normal, if not, reset, re-insert or replace TRX. 3. Check cells' work state and disturbance situation. If cells work abnormal or disturbance happens severely, the network need to be optimized. 198087438 Assignment failure alarm Alarm Property � Alarm Code:198087438 � Severity:Major � � Description:Assignment failure alarm Alarm Type:Qos Alarm Probable Cause TCH assignment fails in large scale and exceeds threshold. System Impact Service quality will remain low for a long time if alarm is not handled. Speciic Problem Handling Suggestion TCH assignment fails in large scale and exceeds threshold. 1. Check whether channels are manually blocked, if yes, unblock them. 2. Check whether TRX state is normal, if not, reset, re-insert or replace TRX. 3. Check cells' work state and disturbance situation. If cells work abnormally or disturbance happens severely, the network need to be optimized. 198087468 LAPD congestion alarm Alarm Property � � Alarm Code:198087468 Description:LAPD congestion alarm Conidential and Proprietary Information of ZTE CORPORATION 323 ZXG10 iBSC Alarm Handling Reference � � Severity:Critical Alarm Type:Qos Alarm Probable Cause LAPD link is congested. System Impact Abnormal communication or even link break might be induced because of serious LAPD frame discarding Speciic Problem Handling Suggestion LAPD link is congested. 1. Check whether conigured LAPD channels are enough according to site-conigured carriers, and add more LAPD channels if not. 2. Check whether there are trunk circuits alarm and trunk slip notiication on E1, and solve E1 transmission problem irst if it appears. 3. Check whether site voltage is unstable or too low. 198087506 NSE block alarm Alarm Property � Alarm Code:198087506 � Severity:Major � � Description:NSE block alarm Alarm Type:Qos Alarm Probable Cause All NSVCs of the NSE are blocked System Impact The NSE can not run PS Speciic Problem Handling Suggestion All NSVCs of the NSE are blocked 1. If NSVC is manually blocked, please unblock it in Dynamic Data Management interface of NMS. 2. Otherwise, please check Gb link. 198087507 SGSN is blocked. Alarm Property Alarm Code:198087507 � Severity:Critical � � Description:SGSN is blocked. Alarm Type:Qos Alarm Probable Cause All NSEs of the SGSN are blocked System Impact All NSEs of the SGSN can not run PS Speciic Problem 324 � All NSEs of the SGSN are blocked Conidential and Proprietary Information of ZTE CORPORATION Chapter 6 QoS Alarm Handling Suggestion 1. If NSVC is manually blocked, please unblock it in Dynamic Data Management interface of NMS. 2. Otherwise, please check Gb link. 198087758 Manual User Access control alarm Alarm Property � Alarm Code:198087758 � Severity:Minor � � Description:Manual User Access control alarm Alarm Type:Qos Alarm Probable Cause Start manual user access control System Impact Some users fail to gain access. Speciic Problem Handling Suggestion Start manual user access control BSC can implement low control automatically. Observe the alarm without taking any handling measures. 198087759 CPU overload control alarm at Paging mode Alarm Property Probable Cause Speciic Problem System Impact Handling Suggestion � Alarm Code:198087759 � Severity:Minor � � Description:CPU overload control alarm at Paging mode Alarm Type:Qos Alarm The excessive trafic causes the CPU load to exceed the low control threshold in module parameter setting. The excessive trafic causes the CPU load to exceed the low control threshold in module parameter setting. The system automatically initiates low control management and thus some users cannot gain access. If the trafic is still excessive after low control, the CPU load will grow further. Block some cells through dynamic data management to prohibit some users to access. After the alarm is eliminated, restore the coniguration or unblock the related cells. Conidential and Proprietary Information of ZTE CORPORATION 325 ZXG10 iBSC Alarm Handling Reference This page is intentionally blank. 326 Conidential and Proprietary Information of ZTE CORPORATION Glossary OAM - Operation, Administration and Maintenance Conidential and Proprietary Information of ZTE CORPORATION 327
0
advertisement
Related documents
Download
advertisement
Add this document to collection(s)
You can add this document to your study collection(s)
Sign in Available only to authorized usersAdd this document to saved
You can add this document to your saved list
Sign in Available only to authorized users