SJ-20120319104909-012-ZXUR 9000 UMTS (V4.11.20) Alarm and Notification Handling Reference

ZXUR 9000 UMTS
Radio Network Controller

Alarm and Notification Handling Reference
Version: V4.11.20
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 © 2012 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R1.1 2012–07–20 Second edition
R1.0 2012–05–18 First edition
Serial Number: SJ-20120319104909-012
Publishing Date: 2012-07-20（R1.1）
SJ-20120319104909-012|2012-07-20（R1.1） ZTE Proprietary and Confidential

Contents
About This Manual ......................................................................................... I
Chapter 1 Overview .................................................................................... 1-1
1.1 Overview of Fault Management........................................................................... 1-1
1.2 Alarm Code........................................................................................................ 1-1
1.3 Alarm Type ........................................................................................................ 1-1
1.4 Alarm Classification ............................................................................................ 1-2
1.4.1 Alarm ...................................................................................................... 1-2
1.4.2 Notification............................................................................................... 1-2
1.5 Severity ............................................................................................................. 1-2
1.6 Probable Cause ................................................................................................. 1-3
1.7 Handling Suggestion .......................................................................................... 1-3
1.8 Alarm Impact ..................................................................................................... 1-3
Chapter 2 Alarm.......................................................................................... 2-1

2.1 Equipment Alarm................................................................................................ 2-1
2.1.1 199000256 OMC port's link is down 0........................................................ 2-1
2.1.2 199000512 Trunk loss of frame 0 .............................................................. 2-2
2.1.3 199000513 Trunk loss of signal 0 .............................................................. 2-3
2.1.4 199000514 Trunk alarm indication signal 0 ................................................ 2-3
2.1.5 199000515 Trunk loss of CRC multi-frame 0 .............................................. 2-4
2.1.6 199000517 Trunk remote alarm indication 0............................................... 2-4
2.1.7 199000518 Trunk link is used for CSU loopback test 0................................ 2-5
2.1.8 199001024 Cell Delineation Not Synchronized 0 ........................................ 2-5
2.1.9 199001025 Loss of Cell Delineation 0........................................................ 2-6
2.1.10 199001026 Cell delineation do not synchronization about cell on E1 link
0 ............................................................................................................ 2-7
2.1.11 199001285 Clock chip is in preheat status 0 ............................................. 2-8
2.1.12 199001286 Input clock of the board is lost 0............................................. 2-8
2.1.13 199001792 SDH/SONET Loss of signal 0 ................................................ 2-9
2.1.14 199001793 SDH/SONET Loss of frame 0 .............................................. 2-10
2.1.15 199001794 SDH/SONET Regenerator section trace mismatch/Section
trace mismatch 0 .................................................................................. 2-10
2.1.16 199001795 SDH/SONET MS alarm indication signal/Line alarm
indication signal 0 ..................................................................................2-11

2.1.17 199001796 SDH/SONET MS far-end reception failure/Line far-end
reception failure 0 ................................................................................. 2-12
2.1.18 199001797 SDH/SONET Signal failure 0 ............................................... 2-12
2.1.19 199001798 SDH/SONET Signal deterioration 0...................................... 2-13
2.1.20 199001799 SDH/SONET Loss of AU pointer/Loss of path pointer 0 ......... 2-14
2.1.21 199001800 SDH/SONET AU alarm indication signal/Path alarm
indication signal 0 ................................................................................. 2-15
2.1.22 199001801 SDH/SONET HP trace mismatch/ Path trace mismatch 0 ...... 2-15
2.1.23 199001802 SDH/SONET HP unequipped/Path unequipped 0 ................. 2-16
2.1.24 199001803 SDH/SONET HP Label mismatch/Path label mismatch 0....... 2-17
2.1.25 199001804 SDH/SONET HP remote reception failure/Path remote
reception failure 0 ................................................................................. 2-17
2.1.26 199001805 SDH/SONET Loss of multi-frame 0 ...................................... 2-18
2.1.27 199001806 SDH/SONET Loss of TU pointer/Loss of virtual tributary
pointer 0 ............................................................................................... 2-18
2.1.28 199001807 SDH/SONET Tributary unit alarm indication signal/Virtual
tributary alarm indication signal 0 ........................................................... 2-19
2.1.29 199001808 SDH/SONET LP remote defect indication/Virtual tributary
remote defect indication 0...................................................................... 2-19
2.1.30 199001809 SDH/SONET LP remote failure indication/Virtual tributary
remote failure indication 0...................................................................... 2-20
2.1.31 199001810 SDH/SONET LP trace mismatch/Virtual tributary trace
mismatch 0........................................................................................... 2-21
2.1.32 199001811 SDH/SONET LP unequipped/Virtual tributary unequipped
0 .......................................................................................................... 2-22
2.1.33 199001812 SDH/SONET LP label mismatch/Virtual tributary label
mismatch 0........................................................................................... 2-23
2.1.34 199001816 SDH/SONET Severe B1 error code 0................................... 2-24
2.1.37 199001819 SDH/SONET Severe BIP-2 error code 0............................... 2-26
2.1.38 199001820 SDH/SONET MS remote error indication 0 ........................... 2-27
2.1.39 199001821 SDH/SONET HP remote error indication 0............................ 2-28
2.1.40 199001826 SDH/SONET LP remote error indication 0 ............................ 2-29
2.1.41 199005123 The configuration is not supported 0 .................................... 2-30
2.1.42 199005405 Clock board phase-lock loop work mode is abnormal 0 ......... 2-31
2.1.43 199005632 The hard disk used-rate is over threshold 0 .......................... 2-31
2.1.44 199005633 The hard disk is error or does not exist 0 .............................. 2-32
2.1.45 199005634 The hard disk on board gets IO error. 0 ................................ 2-33
II

2.1.46 199005646 Phase-lock loop of the board is unlocked 0 ........................... 2-33
2.1.47 199005666 Error packets of MAC is higher than the specified threshold
0 .......................................................................................................... 2-34
2.1.48 199005670 Oscillator status is abnormal 0 ............................................. 2-35
2.1.49 199005672 Clock source is not available 0............................................. 2-35
2.1.50 199005673 The setting of the dial switch is changed 0............................ 2-36
2.1.51 199005760 Ethernet port's link is down 0 ............................................... 2-37
2.1.52 199005761 The speed mode of Ethernet port doesn't match with
settings 0.............................................................................................. 2-38
2.1.53 199005768 All of the board input clocks which have the same frequency
are lost. 0 ............................................................................................. 2-38
2.1.54 199005769 The master and slave mode of Ethernet port doesn't match
with settings 0....................................................................................... 2-39
2.1.55 199005770 The OMP board doesn't have any OMC port 0...................... 2-40
2.1.56 199005771 The duplex mode of Ethernet port doesn't match with
settings 0.............................................................................................. 2-40
2.1.57 199005772 Board device fault 0 ............................................................ 2-41
2.1.58 199005773 High CRC error rate at E1/T1 bottom layer 0 ........................ 2-41
2.1.59 199005774 High FAS error rate at E1/T1 bottom layer 0 ......................... 2-42
2.1.60 199005775 High EBIT error rate at E1 bottom layer 0 ............................. 2-43
2.1.61 199005785 GPS module is abnormal 0.................................................. 2-44
2.1.62 199005890 Functional EPLD update failed 0 .......................................... 2-44
2.1.63 199005930 NCPU version load failed 0.................................................. 2-45
2.1.64 199007168 Port trunk fail 0 ................................................................... 2-46
2.1.65 199007169 Inner port error 0................................................................. 2-46
2.1.66 199007170 Trunk connect asymmetry 0................................................. 2-47
2.1.67 199007171 Outer media trunk failed 0 ................................................... 2-48
2.1.68 199015360 Media status abnormal 0 ..................................................... 2-48
2.1.69 199015618 Too many bad frames received 0 ......................................... 2-49
2.1.70 199019712 APS channel mismatch 0 .................................................... 2-49
2.1.71 199019713 APS mode mismatch 0........................................................ 2-50
2.1.72 199019715 MS APS channel gets errors 0............................................. 2-51
2.1.73 199023050 Fan Device Absent 0........................................................... 2-51
2.1.74 199023051 Power Unit Absent 0 ........................................................... 2-52
2.1.75 199023106 Board initialized test failed 0 ................................................ 2-52
2.1.76 199025602 Half-Fixed Connection abnormal 0 ....................................... 2-53
2.1.77 199025856 Rack temperature is higher than high threshold 0.................. 2-54
2.1.78 199025857 Rack temperature is lower than low threshold 0 .................... 2-54
III

2.1.79 199025858 Room temperature is higher than high threshold 0 ................ 2-55
2.1.80 199025859 Room temperature is lower than low threshold 0 ................... 2-56
2.1.81 199025860 Voltage is higher than high threshold 0 ................................. 2-57
2.1.82 199025861 Voltage is lower than low threshold 0.................................... 2-57
2.1.83 199025862 Humidity is higher than high threshold 0 ............................... 2-58
2.1.84 199025863 Humidity is lower than low threshold 0.................................. 2-58
2.1.85 199025864 Fault in fan plug-in box 0 ..................................................... 2-59
2.1.86 199025865 Rack door access control alarm 0 ........................................ 2-60
2.1.87 199025866 Smoke alarm 0 ................................................................... 2-60
2.1.88 199025867 Infrared alarm 0 .................................................................. 2-61
2.1.89 199025868 Lightning alarm 0 ................................................................ 2-62
2.1.90 199025869 Power switch alarm 0 .......................................................... 2-62
2.1.91 199025870 Power type configured does not accord with physical 0 ......... 2-63
2.1.92 199026127 Clock reference source lost (Level 3 alarm) 0 ....................... 2-64
2.1.95 199026133 Output clock of the board is lost 0 ........................................ 2-66
2.1.96 199029184 SNTP time-synchronization failed 0...................................... 2-66
2.1.97 199030721 Temperature is lower than lower-non-critical threshold. 0....... 2-67
2.1.98 199030722 Temperature is lower than lower-critical threshold. 0 ............. 2-68
2.1.99 199030723 Temperature is lower than lower-non-recoverable threshold.
0 .......................................................................................................... 2-68
2.1.100 199030724 Temperature is higher than upper-non-critical threshold.
0 .......................................................................................................... 2-69
2.1.101 199030725 Temperature is higher than upper-critical threshold. 0 ......... 2-69
2.1.102 199030726 Temperature is higher than upper-non-recoverable
threshold. 0 .......................................................................................... 2-70
2.1.103 199030727 Voltage is lower than lower-non-critical threshold. 0 ............ 2-70
2.1.104 199030728 Voltage is lower than lower-critical threshold. 0 ................... 2-71
2.1.105 199030729 Voltage is lower than lower-non-recoverable threshold. 0 ..... 2-71
2.1.106 199030730 Voltage is higher than upper-non-critical threshold. 0 .......... 2-72
2.1.107 199030731 Voltage is higher than upper-critical threshold. 0 ................. 2-72
2.1.108 199030732 Voltage is higher than upper-non-recoverable threshold.
0 .......................................................................................................... 2-73
2.1.109 199030734 Velocity of fan is lower than lower-critical threshold. 0 ......... 2-73
2.1.110 199030739 Current is lower than lower-non-critical threshold. 0............. 2-74
2.1.111 199030740 Current is lower than lower-critical threshold. 0 ................... 2-74
2.1.112 199030741 Current is lower than lower-non-recoverable threshold. 0 ..... 2-75
IV

2.1.113 199030742 Current is higher than upper-non-critical threshold. 0........... 2-75
2.1.114 199030743 Current is higher than upper-critical threshold. 0 ................. 2-76
2.1.115 199030744 Current is higher than upper-non-recoverable threshold.
0 .......................................................................................................... 2-76
2.1.116 199030745 Velocity of fan is lower than lower-non-critical threshold.
0 .......................................................................................................... 2-77
2.1.117 199030746 Velocity of fan is lower than lower-non-recoverable
threshold. 0 .......................................................................................... 2-77
2.1.118 199030747 Module/Board Device Absent 0 .......................................... 2-78
2.1.119 199030748 Power On Failed due to S5 0 ............................................. 2-78
2.1.120 199030808 Processor Internal Error 0.................................................. 2-79
2.1.121 199030809 Processor Thermal Trip 0 .................................................. 2-79
2.1.122 199083851 Dry contact alarm - Waterlog 0........................................... 2-80
2.1.123 199083852 Dry contact alarm - Power loss 0........................................ 2-80
2.1.124 199083853 Dry contact alarm - No.1 air conditioner fault 0.................... 2-81
2.1.125 199083854 Dry contact alarm - No.2 air conditioner fault 0.................... 2-81
2.1.126 199083855 Dry contact alarm - AC power abnormal 0 .......................... 2-82
2.1.127 199083856 Dry contact alarm - Battery under-voltage 0 ........................ 2-82
2.1.128 199083857 Dry contact alarm - SMR abnormal 0.................................. 2-83
2.1.129 199083858 Dry contact alarm - Under-voltage insulate drop 0 ............... 2-83
2.1.130 199083859 Dry contact alarm - Device suspended 0............................. 2-84
2.1.131 199083860 User-defined Dry contact alarm 1 0 .................................... 2-84
2.1.140 199083869 User-defined Dry contact alarm 10 0 .................................. 2-89
2.1.141 199083870 User-defined Dry contact alarm 11 0................................... 2-90
2.1.142 199105025 the rate of abnormal service on SLAVE is high 0 ................. 2-90
2.1.143 199105029 OMP reboot alarm 0.......................................................... 2-91
2.1.144 199393987 Board off line 0 ................................................................. 2-91
2.1.145 199419840 PTP failed to get clock attribute 0 ....................................... 2-92
2.2 Processing Alarm ............................................................................................. 2-93
2.2.1 199002560 CPU utilization over alarm limit 0 ........................................... 2-93

2.2.2 199004357 The system bureau changed 0 .............................................. 2-93
2.2.3 199005400 Configuration conflicts between OMP and CMM 0................... 2-94
2.2.4 199005908 Lack of version 0 .................................................................. 2-94
2.2.5 199005909 Download version failed 0 ..................................................... 2-95
2.2.6 199005910 Process execute failed 0 ....................................................... 2-95
2.2.7 199015362 Fail to process MCS APP Dlib 0 ............................................ 2-96
2.2.8 199018944 PVC link is down 0................................................................ 2-97
2.2.9 199019207 Near-End IMA Group Configuration Fault 0 ............................ 2-97
2.2.10 199020225 Protocol Stack Requests for Configuration Information
Timeout 0 ............................................................................................. 2-98
2.2.11 199023042 The number of board physical alarms exceeds the threshold
0 .......................................................................................................... 2-99
2.2.12 199025600 Connection check be disabled in board 0 ............................2-100
2.2.13 199029953 Port is in ethernet OAM loopback state 0.............................2-100
2.2.14 199066006 broadband link congestion 0 ...............................................2-101
2.2.15 199066007 broadband link overload 0 ..................................................2-102
2.2.16 199066013 MTP3 link congestion 0 ......................................................2-103
2.2.17 199066027 Request time from SNTP server failed 0..............................2-104
2.2.18 199066031 The number of OMP alarms exceeds the threshold 0 ...........2-105
2.2.19 199066032 Time synchronization over alarm limit 0 ...............................2-105
2.2.20 199066063 MTP3 link sending flow control alarm 0 ...............................2-106
2.2.21 199083022 Cell is out of service 1 ........................................................2-107
2.2.22 199083022 Cell is out of service 10 ......................................................2-108
2.2.23 199083022 Cell is out of service 11 ...................................................... 2-110
VI

VII

2.2.76 199083023 NodeB is out of service 1....................................................2-189
2.2.79 199083054 Incomplete Dbs config alarm 0............................................2-192
2.2.80 199083056 System Information Block overlength Alarm 0 ......................2-193
2.2.81 199392708 Time synchronization over alarm limit in RPU accesstype
0 .........................................................................................................2-194
2.2.82 199411651 The number of board logical alarms exceeds the threshold
0 .........................................................................................................2-194
2.3 Communications Alarm....................................................................................2-195
2.3.1 199003841 The control plane retransfer ratio over the threshold 0............2-195
2.3.2 199005382 Environment monitor board communication is abnormal 0 ......2-196
2.3.3 199005396 Packet test of internal media plane is abnormal 0 ..................2-196
2.3.4 199005397 Communication of RAW MAC channel is abnormal 0 .............2-197
2.3.5 199005406 Sub-unit state is abnormal 0 .................................................2-198
2.3.6 199019208 Timing of Near-End IMA Group Fault 0..................................2-198
2.3.7 199019212 Near-End Transmitting Link Disconnection 0 .........................2-199
2.3.8 199019213 LIF Alarm of Near-End Receiving Link 0................................2-200
2.3.9 199019214 LODS Alarm of Near-End Receiving Link 0............................2-200
2.3.10 199019215 RDI Alarm of Far-End Receiving Link 0 ...............................2-201
2.3.11 199019216 Near-End Receiving Link Fault 0 .........................................2-202
2.3.12 199019218 Near-End Receiving Link Disconnection 0 ...........................2-202
2.3.13 199019223 Near-End IMA Group Fault 0 ..............................................2-203
2.3.14 199019971 Request gate info timeout 0 ................................................2-204
2.3.15 199025631 LVDS link error 0................................................................2-204
2.3.16 199025871 Communication abnormal between the shelf management
board and switch board in the same shelf 0 ...........................................2-205
2.3.17 199029952 Ethernet link fault alarm 0 ...................................................2-206
2.3.18 199030208 Connectivity fault alarm 0 ...................................................2-206
2.3.19 199041737 Near-End TC Link Fault 0 ...................................................2-208
2.3.20 199066003 Control plane communication abnormal between board and
its home module 0................................................................................2-208
2.3.21 199066005 SCCP subsystem unavailable 0 ..........................................2-209
2.3.22 199066010 MTP3 office inaccessible 0 .................................................2-210
2.3.23 199066011 MTP3 link unavailable 0...................................................... 2-211
2.3.24 199066012 MTP3 cluster inaccessible 0 ...............................................2-212
2.3.25 199066014 M3UA office inaccessible 0.................................................2-213
VIII

2.3.26 199066019 Broken Association 0 .........................................................2-214
2.3.27 199066026 Association Channel Broken 0 ............................................2-215
2.3.28 199083021 CCP link fault alarm 1 ........................................................2-216
2.3.32 199083036 Domain Specific Access Restriction Alarm 0........................2-220
2.3.33 199083045 Common Channel setup failed alarm 0................................2-221
2.3.34 199105021 IP channel of Iub interface is faulty 0 ...................................2-222
2.3.35 199105028 The IP domain is inconsistent in UDP context 0 ...................2-223
2.3.36 199393986 Control plane communication is abnormal between this
board and the active independent board 0 .............................................2-223
2.3.37 199393988 Control plane communication abnormal between MP and
OMP 0 ................................................................................................2-224
2.3.38 199407043 PPP Link Broken 0.............................................................2-225
2.3.39 199411392 BFD Session Interruption 0 .................................................2-226
2.3.40 199411393 BFD Session Negotiation Failure 0......................................2-228
2.3.41 199419073 Bearer network is unavailable 0 ..........................................2-229
2.3.42 199419074 Bearer network get worse 0 ................................................2-230
2.3.43 199420352 IPD Session Interruption 0..................................................2-232
2.3.44 199429568 broadband link unavailable 0 ..............................................2-233
2.4 Environment Alarm..........................................................................................2-234
2.4.1 199030749 Difference between ambient and outlet sensor exceeded limit
. 0.......................................................................................................2-234
2.5 Qos Alarm ......................................................................................................2-234
2.5.1 199066018 Association congested 0 ......................................................2-234
2.5.2 199105022 IU PS traffic over load alarm 0 ..............................................2-235
2.5.3 199105023 IU CS traffic over load alarm 0 ..............................................2-235
2.5.4 199105024 IU traffic over load alarm 0 ...................................................2-236
Chapter 3 Notification ................................................................................ 3-1

3.1 199000576 Trunk slip 0 ...................................................................................... 3-4
3.2 199000834 MCC is abnormal 0 ........................................................................... 3-5
3.3 199001600 CPU resets on a board in the same shelf 0......................................... 3-6
3.4 199004417 Exception information 0..................................................................... 3-6
3.5 199004418 Logic cpu is power on successfully 0.................................................. 3-7
3.6 199004419 Logic cpu is power on failed 0............................................................ 3-7
3.7 199005189 Board change over notice 0............................................................... 3-8
3.8 199005448 Environment parameters set fail 0...................................................... 3-8
IX

3.9 199005715 PP2S source has switched 0 ............................................................. 3-9
3.10 199005718 Two master clock ports is directly connected 0.................................. 3-9
3.11 199005720 The CDM data was covered 0........................................................ 3-10
3.12 199005762 The board is selecting clock base 0.................................................3-11
3.13 199005763 There is no valid reference of the clock board to be selected. 0 ........3-11
3.14 199005764 Lock timeout when manual selecting clock reference 0.................... 3-12
3.15 199005765 Lock the wrong base when manual selecting clock reference 0........ 3-12
3.16 199005766 Lock the right base when manual selecting clock reference 0 .......... 3-13
3.17 199005767 The manual selecting reference command is unuseful because the
clock board is in preheat status. 0 ................................................................... 3-13
3.18 199005956 Board version error. 0 ................................................................... 3-14
3.19 199005958 IDE version file synchronization information 0 ................................. 3-14
3.20 199005976 Download version failed 0.............................................................. 3-15
3.21 199005977 Running version not match with database configuration 0................ 3-16
3.22 199005978 Boottype different with configure 0 ................................................. 3-16
3.23 199005979 Execute version file failed 0 ........................................................... 3-17
3.24 199005980 Match version failed 0 ................................................................... 3-17
3.25 199005981 NCPU version load information 0 ................................................... 3-18
3.26 199005982 Patch operation failed 0................................................................. 3-18
3.27 199005983 Write back version information 0 .................................................... 3-19
3.28 199005984 Check version information 0 .......................................................... 3-19
3.29 199005985 Synchronize version information 0 ................................................. 3-20
3.30 199006017 The Sunit resets by MML command . 0 .......................................... 3-20
3.31 199006018 block The Sunit 0 .......................................................................... 3-21
3.32 199006720 Notice of power-on status of C51 board/ Board soft reset 0.............. 3-21
3.33 199008000 Load Data Fail 0 ........................................................................... 3-22
3.34 199008007 Save database failed 0.................................................................. 3-22
3.35 199008512 Msater-Slave Fail 0 ....................................................................... 3-23
3.36 199008769 Data Sync Between Boards Fail 0.................................................. 3-23
3.37 199008770 Data Sync Loading Fail 0 .............................................................. 3-24
3.38 199008771 Sync by Ftp Fail 0 ......................................................................... 3-24
3.39 199009024 Notify Fail 0 .................................................................................. 3-25
3.40 199010048 Mem Fail 0 ................................................................................... 3-25
3.41 199010049 DLL Register Fail 0 ....................................................................... 3-26
3.42 199010050 Get Lock Timeout 0....................................................................... 3-26
3.43 199010051 Transaction Timeout 0................................................................... 3-27
3.44 199010304 SCCP GT translation failure 0........................................................ 3-27
3.45 199010305 NID not configured 0 ..................................................................... 3-28
X

3.46 199010306 NID translation failure 0 ................................................................. 3-28
3.47 199010307 ISNI constrained route information repetition 0................................ 3-29
3.48 199010308 ISNI does not support this route function 0 ..................................... 3-30
3.49 199010309 NID route prompt failure 0 ............................................................. 3-30
3.50 199010310 Wrong message type use ISNI function 0 ....................................... 3-31
3.51 199011840 M3UA user office status change 0 .................................................. 3-31
3.52 199012096 failed for sig process get the info of config 0 ................................... 3-32
3.53 199012097 The file of sig config updated 0 ...................................................... 3-32
3.54 199012352 failed for sig process get memory resource 0 .................................. 3-33
3.55 199013888 ASP status changed 0................................................................... 3-33
3.56 199013889 AS status changed 0 ..................................................................... 3-34
3.57 199013890 Sigtran error message received 0 .................................................. 3-35
3.58 199013891 Sigtran notification message received 0 ......................................... 3-35
3.59 199014144 Association Establishment Failure 0 ............................................... 3-36
3.60 199014145 Association restart 0 ..................................................................... 3-37
3.61 199014146 Dynamic Association link broken 0 ................................................. 3-37
3.62 199014148 One user of share association is in service 0 .................................. 3-38
3.63 199014149 One user of share association is out of service 0............................. 3-38
3.64 199014150 Association config error 0 .............................................................. 3-39
3.65 199014151 SSM malloc memory failure 0 ........................................................ 3-39
3.66 199014152 Dynamic association config error 0................................................. 3-40
3.67 199017472 Data configuration abnormal 0 ....................................................... 3-40
3.68 199017473 Configuration file abnormal 0 ......................................................... 3-41
3.69 199017728 Database access abnormal 0 ........................................................ 3-41
3.70 199017990 RPU detected board down 0.......................................................... 3-42
3.71 199018240 TCP Receiving RST Packet 0 ........................................................ 3-42
3.72 199018241 TCP Connection Disconnected 0 ................................................... 3-43
3.73 199018242 MD5 Verification Failure 0.............................................................. 3-44
3.74 199018243 MD5 Message Error 0 ................................................................... 3-45
3.75 199018244 SOCKET received queue over threshold value 0............................. 3-46
3.76 199018245 SOCKET abnormally closed 0 ....................................................... 3-46
3.77 199018500 The peer IP address configuration and the local IP address
configuration of PPP link is the same 0 ............................................................ 3-47
3.78 199018501 The HDLC channel of EPU created fail 0........................................ 3-47
3.79 199018504 The HDLC channel created unsuccessfully before is created
successfully now. 0......................................................................................... 3-48
3.80 199018755 HDLC status changed 0 ................................................................ 3-49
3.81 199019008 Fail to config the ATM port 0 .......................................................... 3-50
XI

3.82 199019264 IMA Group Related Operations Failure 0 ........................................ 3-50
3.83 199019265 IMA Link Operations Failure 0........................................................ 3-51
3.84 199019777 APS switchover happens 0............................................................ 3-52
3.85 199020290 Failed to Power on Protocol Stack 0............................................... 3-52
3.86 199020554 Add IP route failed 0 ..................................................................... 3-53
3.87 199020802 Conflicting IP addresses 0 ............................................................. 3-54
3.88 199020803 Conflicting MAC Addresses in Subnet 0 ......................................... 3-54
3.89 199021059 RIP Neighbor Configuration Error 0................................................ 3-55
3.90 199021060 RIP Interface Authentication Error 0 ............................................... 3-56
3.91 199021065 Incompatible RIP Version Number 0............................................... 3-56
3.92 199021329 LSDB overflow 0 ........................................................................... 3-57
3.93 199021330 Configuration of OSPF mismatched 0 ............................................ 3-58
3.94 199021573 BGP Gets TCB Fail on Active Connection 0.................................... 3-58
3.95 199021584 Neighbor Hold Timer Expired 0 ...................................................... 3-59
3.96 199021585 BGP Interface down and Neighbor Link Broken 0............................ 3-59
3.97 199021837 Failure in adding dynamic routings 0 .............................................. 3-60
3.98 199022336 Intra-Office Port MAC Conflict 0 ..................................................... 3-61
3.99 199022593 ISIS Hello Message Authentication Failure 0 .................................. 3-62
3.100 199022594 ISIS LSP Message Authentication Failure 0 .................................. 3-62
3.101 199022595 ISIS SNP Message Authentication Failure 0 ................................. 3-63
3.102 199022597 Abnormal Message is Received 0 ................................................ 3-64
3.103 199022598 Routers with Conflicting System Id Exist in Network 0 ................... 3-65
3.104 199025620 Top resource insufficient 0 ........................................................... 3-65
3.105 199026176 The currently locked reference of the clock board has been
changed 0 ...................................................................................................... 3-66
3.106 199026178 Clock work mode is changed 0 .................................................... 3-66
3.107 199028231 Router ID not configured for OSPFv3 0 ........................................ 3-67
3.108 199028233 Configuration of OSPFv3 Mismatched 0 ....................................... 3-67
3.109 199028993 SCTP Primary Path Set Failed 0 .................................................. 3-68
3.110 199028994 SCTP Change Nexthop 0 ............................................................ 3-68
3.111 199028998 SCTP abnormally congested 0 ..................................................... 3-69
3.112 199028999 Module Asso Num Exceed 0 ........................................................ 3-70
3.113 199029000 SCTP receive queue over threshold value 0.................................. 3-70
3.114 199029760 DNS server inaccessible 0 ........................................................... 3-71
3.115 199030016 Ethernet link OAM event 0 ........................................................... 3-71
3.116 199030528 The result of configured PD task start 0 ........................................ 3-72
3.117 199030787 ATCA Fru Power On 0 ................................................................. 3-73
3.118 199030790 ATCA Fru Power Off 0 ................................................................. 3-73
XII

3.119 199030794 ATCA Fru Communication Lost 0 ................................................. 3-74
3.120 199030800 ATCA Fru Communication Regain 0 ............................................. 3-74
3.121 199030815 HOST CPU RESET EVENT 0...................................................... 3-75
3.122 199030817 BIOS Start-up Inform 0 ................................................................ 3-75
3.123 199030820 BIOS Memory Inform 0................................................................ 3-76
3.124 199030821 Power On Failed Inform 0 ............................................................ 3-76
3.125 199030828 ATCA FRU present 0................................................................... 3-77
3.126 199030829 ATCA FRU absent 0.................................................................... 3-77
3.127 199031296 PTP failed to cancel slave port 0 .................................................. 3-78
3.128 199031554 IP address of DHCP server alloc to client is conflict 0 .................... 3-78
3.129 199041473 Fail to config the ATM pvc 0......................................................... 3-79
3.130 199041794 TC Link Operations Failure 0 ....................................................... 3-80
3.131 199070002 Iu interface global reset notification 0............................................ 3-80
3.132 199070003 Iu interface resource reset notification 0 ....................................... 3-81
3.133 199070004 RNC started Iu interface global reset failure notification 0 .............. 3-82
3.134 199070005 RNC started Iu interface resource reset failure notification 0 .......... 3-82
3.135 199070008 RNC and Node B CCPID configuration are not identical 0.............. 3-83
3.136 199070009 Broadcast fail 0 ........................................................................... 3-83
3.137 199083025 Common Channel is abnormal 0 .................................................. 3-85
3.138 199083037 All Local Cell ID configured at RNC side are differ from which on
Node B side 0................................................................................................. 3-86
3.139 199083057 Excluded Neighbour Cells In SysInfoBlock Notification 0 ............... 3-86
3.140 199105001 Failed to get the table of configuration 0 ....................................... 3-87
3.141 199105002 The route table is overloaded 0 .................................................... 3-88
3.142 199105003 Failed to handle DHCP message from other network 0.................. 3-89
3.143 199105004 Failed to operate multicast group 0 .............................................. 3-90
3.144 199105005 Clock difference of slave is large 0 ............................................... 3-90
3.145 199105006 Slave losted external clock 0........................................................ 3-91
3.146 199105007 TCP connection on IuBC interface establish failure 0..................... 3-91
3.147 199105008 Bandwidth automatic adjustment is useless 0 ............................... 3-92
3.148 199105009 No acknowledge of SLA query request 0 ...................................... 3-93
3.149 199105018 Unable to save Performance File 0 .............................................. 3-93
3.150 199105019 SLAVE memory check fail notification 0 ........................................ 3-94
3.151 199105020 TCP connect on IuBC interface is interrupted 0 ............................. 3-95
3.152 199105030 OMP received data is not complete 0 ........................................... 3-95
3.153 199105031 Transport path bandwidth modified from far end 0 ......................... 3-96
3.154 199105032 Transport Path Occupied BandWidth Overload 0 .......................... 3-96
3.155 199105033 Transport Path group Occupied Bandwidth Overload 0.................. 3-97
XIII

Glossary .......................................................................................................... I
XIV

About This Manual
Manual Description
This manual is a handling reference for the ZXUR 9000 UMTS alarms and notifications,
it helps users to analyze and handle the alarms and notifications reported on the NMS
during the operation of ZXUR 9000 UMTS.
Target Group
l EMS Engineer
l Network Optimization Engineer
l Testing Engineer
What Is in This Manual
Chapter Summary
Chapter 1, Overview Introduces the concepts and terms used in this manual.
Chapter 2, Alarm Introduces the ZXUR 9000 UMTS alarms.
Chapter 3, Notification Introduces the ZXUR 9000 UMTS notifications.

II

Chapter 1
Overview
Table of Contents
Overview of Fault Management ..................................................................................1-1
Alarm Code ................................................................................................................1-1
Alarm Type.................................................................................................................1-1
Alarm Classification....................................................................................................1-2
Severity ......................................................................................................................1-2
Probable Cause .........................................................................................................1-3
Handling Suggestion ..................................................................................................1-3
Alarm Impact ..............................................................................................................1-3
1.1 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 notification, is stored in database or displayed
on realtime basis via 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.
1.2 Alarm Code

Alarm code is the identifier which differentiates alarms.
Alarm code is defined by a 32-bit field indicating the specific code value.
Alarm sub-code is the identifier which same alarms alarm code.
1.3 Alarm Type

Alarm is classified into six types according to alarm trigger condition and its system impact.
l Equipment alarm: related with device hardware.

l Communication alarm: related with information transmission (ITU-T Recommendation
X.733).
l Processing alarm: related with software or process fault (ITU-T Recommendation
X.733).
1-1

ZXUR 9000 UMTS Alarm and Notification Handling Reference
l Environment alarm: related with the environment where the equipment is located
(ITU-T Recommendation X.733).
l QoS alarm: related with degradation of service quality (ITU-T Recommendation
X.733).
l OMS alarm: related with the network management system.
1.4 Alarm Classification

1.4.1 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.
Due to its possible impact on normal system operation, alarm requires timely
troubleshooting in which alarm cause is identified, and the fault is located and handled.
1.4.2 Notification
Notification refers to the non-repeated/instantaneous fault or event that occurs during
system operation. Examples include board reset, signaling overload, etc.
Notification is mostly caused by sudden environment change or other accidental factors.

No special handling is required for the notification, which can be automatically removed by
the system. Only the notification that occurs persistently requires troubleshooting.
1.5 Severity
There are four alarm severity levels, which are indicated in descending order of severity
as Critical, Major, Minor and Warning.
l Critical alarm causes system breakdown and service interruption. It requires
immediate troubleshooting.
l Major alarm significantly affects system operation or weakens network service
capability. It requires troubleshooting as soon as possible.
l Minor alarm affects system operation and network service capability in a nonsignificant
way. A timely troubleshooting is required to avoid severity escalation.
l Warning alarm 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 definition 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 specified 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.
1-2

Chapter 1 Overview
Note:
Alarm severity can be modified in NetNumen M31 NMS (network management system) if
necessary.
Generally speaking, the default alarm severity is reasonably set. Users should think twice
before making any modification.
In addition, the severity of few alarms is Undefined. It is up to users to define the severity
of such alarms.
1.6 Probable Cause

Probable alarm causes are enumerated to help users troubleshoot, find preventive
measures, and restore the system to normal state in a timely manner.
1.7 Handling Suggestion

Troubleshooting measures and suggestions are provided.
Pay attention to the following tips when handling alarms.

l After recording the fault phenomenon, O&M 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.
l If the fault cannot be removed, contact the local ZTE office as soon as possible.
1.8 Alarm Impact

Alarm impact refers to the impact that the alarm incurs on system or services.
1-3

This page intentionally left blank.
1-4

Chapter 2
Alarm
Table of Contents
Equipment Alarm........................................................................................................2-1
Processing Alarm .....................................................................................................2-93
Communications Alarm ..........................................................................................2-195
Environment Alarm.................................................................................................2-234
Qos Alarm ..............................................................................................................2-234
2.1 Equipment Alarm

2.1.1 199000256 OMC port's link is down 0
Alarm Property
l Alarm Code:199000256
l Alarm Sub-code：0
l Description:OMC port's link is down
l Severity:Warning
l Alarm Type:Equipment Alarm
Probable Cause
OMCport's link is down.
System Impact
OMC port can't transfer data.
Handling Suggestion
1. If OMM is outside, please check OMC port's link if it is up.

2. If OMM is inside, OMC over fabric, please check if there is inner media fault. OMC over base,
please check if there is control fault. Yes, deal with them first. No, Please contact ZTE Corporation.
2-1

2.1.2 199000512 Trunk loss of frame 0

Alarm Property
l Description:Trunk loss of frame
l Severity:Major
Probable Cause
Two ends have no common ground; the clocks are not synchronous; transmission equipment has a
failure.
System Impact
Trunk signal is broken
Handling Suggestion
Check if the equipment cable impedance of our company matches, if the board's DIP switch matches
the cable and if the rear board's jumper cap matches the cable.
Y-> Go to "2"
Re-set the board's DIP switch or rear board's jumper cap and then check if the alarm is eliminated. If
the alarm is eliminated, end alarm handling, otherwise, go to "2".
2. Use the multimeter to detect if the grounding signal of the equipment from both ends is reliable.
Y-> Go to "3"
Use the multimeter to detect if the grounding signal of the equipment from both ends is reliable and
then check if the alarm is eliminated. If the alarm is eliminated, end alarm handling, otherwise,
go to "3".
3. Check if the CLKG board locks the clock (TRACE evergreen)
Y-> Go to "4"
N-> Lock the clock.
4. Check if the clock references of two matching NEs or nodes are consistent.
Y-> Go to "5"
4. Modify the clock benchmark, ensuring the clock references of two matching NEs or nodes are
consistent.
5. Ask for assistant of the transmission equipment maintaining personnel to check if the transmission
equipment is exceptional. If there is any exception, locate the fault through step-by-step physical
diagnosis and circulating test. Please contact ZTE Corporation if the problem can not be solved.
2-2

Chapter 2 Alarm
2.1.3 199000513 Trunk loss of signal 0

Alarm Property
l Description:Trunk loss of signal
l Severity:Major
Probable Cause
The wire E1 is not connected or wrongly connected on DDF ; E1 breaks; the upstream equipment is
exceptional.
System Impact
Trunk signal is broken.
Handling Suggestion
1. Check if E1 on DDF is connected and then check if the alarm is eliminated.

Y-> The alarm is eliminated. End alarm handling.
N-> Go to "2"
2. Make a self-loop E1 on the local end and then check if the alarm is eliminated.
Y->Detect the upstream equipment, referring to suggestions on upstream equipment troubleshooting.
N-> Go to "3"
3. Replace the board and end alarm handling.
2.1.4 199000514 Trunk alarm indication signal 0

Alarm Property
l Description:Trunk alarm indication signal
l Severity:Major
Probable Cause
There is something wrong with upstream equipment.
System Impact
2-3

Handling Suggestion
Check and remove alarms relating to E1 of upstream equipment. If the alarm can not be eliminated,
please contact ZTE Corporation.
2.1.5 199000515 Trunk loss of CRC multi-frame 0

Alarm Property
l Description:Trunk loss of CRC multi-frame
l Severity:Major
Probable Cause
Multi-frame format is inconsistent.
System Impact
Handling Suggestion
Check if the frame format for the two matching ends is consistent. If it is not consistent, configure the
same one for the two ends. If the alarm can not be eliminated, please contact ZTE Corporation.
2.1.6 199000517 Trunk remote alarm indication 0

Alarm Property
l Description:Trunk remote alarm indication
l Severity:Major
Probable Cause
There is something wrong with the signals sent by the local end or with the intermediate transmission
equipment. All kinds of faults that may result in LOS, AIS, LOF on the peer end would probably
cause this alarm.
2-4

Chapter 2 Alarm
System Impact
Handling Suggestion
1.At this time, at least one alarm among LOS, AIS LOF occurs on the peer end. Check and record the
peer-end alarm. Check the intermediate transmission equipment for this trunk link to see if there
is any failure. If there is , eliminate the failure.
2. Please contact ZTE Corporation if the problem can not be solved.
2.1.7 199000518 Trunk link is used for CSU loopback test 0

Alarm Property
l Description:Trunk link is used for CSU loopback test
l Severity:Minor
Probable Cause
The equipment at end A sends CSU link building code to end B, and this trunk link is set to loopback
at end B. And CSU test starts. If this trunk link is not used for CSU loopback test, this alarm won't be
triggered.
System Impact
Trunk will be blocked when it is configed.
Handling Suggestion
After diagnosis and test, do some settings, where end A sends the command of canceling CSU
loopback to end B.
2.1.8 199001024 Cell Delineation Not Synchronized 0

Alarm Property
l Description:Cell Delineation Not Synchronized
l Severity:Minor
2-5

Probable Cause
HEC is damaged. The cell can not be located from the physical layer's frame.Usually it is triggered
by bottom faults or it is because the local-end equipment and the peer-end equipment process
HEC in different ways.
System Impact
Possibly communication cannot work well
Handling Suggestion
1. Check if there are other alarms accompanying it's occurrence. If there are, eliminate other alarms
firstly and then check if this alarm is eliminated.
N-> Go to "2"
2. Check if both two ends are configured to SDH mode or SONET mode. If the mode is not same,
configure a correct signal mode for them and then check if the alarm is eliminated.
N->Please contact ZTE Corporation.
2.1.9 199001025 Loss of Cell Delineation 0

Alarm Property
l Description:Loss of Cell Delineation
l Severity:Minor
Probable Cause
LCD is triggered after OCD lasting for 4ms.
System Impact
Possibly communication cannot work.
2-6

Chapter 2 Alarm
Handling Suggestion
1. Check if there are other alarms accompanying it's occurrence. If there are, eliminate other alarms
N-> Go to "2"
2. Check if both two ends are configured to SDH mode or SONET mode. If the mode is not same,
configure a correct signal mode for them and then check if the alarm is eliminated.
2.1.10 199001026 Cell delineation do not synchronization about

cell on E1 link 0
Alarm Property
l Description:Cell delineation do not synchronization about cell on E1 link
l Severity:Minor
Probable Cause
The HEC field of cell header is corrupted which result in loss of delineation. This may happen when
physical layer problem occurs or different HEC processes by two ends are taken.
System Impact
Data reception is failure and signaling link is down.
Handling Suggestion
1.Check if there are other alarms accompanying it's occurrence. If there are, eliminate other alarms
Y->The alarm is eliminated. End alarm handling.
N->Go to "2"
2. Pull out and insert the board. Reset the board to check if the alarm is eliminated.
Y->End.
2-7

2.1.11 199001285 Clock chip is in preheat status 0

Alarm Property
l Description:Clock chip is in preheat status
l Severity:Minor
Probable Cause
The board experiences reset. The SETS chip and the crystal oscillator needs to be fully preheated.
System Impact
Output clock is unstable.
Handling Suggestion
Normal procedure after board reset, please wait for the end of warm-up procedure. Clock tests can
be taken unless this alarm is cleared.
2.1.12 199001286 Input clock of the board is lost 0

Alarm Property
l Description:Input clock of the board is lost
l Severity:Minor
Probable Cause
1. The board is not in place (not properly inserted) in the slot.

2. Clock cable is disconnected.
3. One clock board in the same shelf is faulty or not exist.
4. Board is faulty.
System Impact
Board operaton might be abnormal.
2-8

Chapter 2 Alarm
Handling Suggestion
1. Check if the two clock boards in the same shelf are normal, if one of them is normal, then no
need to handle.
2. Replace the board.
2.1.13 199001792 SDH/SONET Loss of signal 0

Alarm Property
l Description:SDH/SONET Loss of signal
l Severity:Major
Probable Cause
Upstream optical transmit device has faults; Optical fiber transmission line has faults; Fiber pigtail
and flange between local-end optical distribution frame and equipment have faults; Local-end
fiber-optical receiver has faults.
System Impact
All received trunk signals are broken.
Handling Suggestion
The normal receiving optical power should be less than -8dBm and more than -28dBm.
1. It needs to check if the fiber modules of both ends are matching,including data rate、optical
wavelength、multi mode、single mode and so on.
If they are not matching,please replace the correct fiber module.
N-> Go to "2"
2. Use optical power meter to detect the power for receiving optical signal at local end to see if
the power is within the above-mentioned range.
Y-> If it is within this range, go to step 4.
Y-> If it is not within this range, it can be concluded that the optical transceiver module has faults. In
this case, go to step 3.
3. Replace this fiber module or board, and then check if the alarm is eliminated.
N-> Go to "4"
4. Detect the transmitting optical signal by use of the transmitting end at the peer end office to
see if it is within the prescribed range.
Y-> If it is within this range, go to step 6.
2-9

Y-> If it is not within this range, it can be concluded that some faults have occurred at the peer
end. In this case, go to step 5.
5. It needs to ask maintenance personnel to check the peer-end office. After troubleshooting at
the peer end, check if the alarm is eliminated.
N-> Go to "6"
6. There may be something wrong with the transmission equipment. It needs to ask the maintenance
personnel to do troubleshooting of maintaining transmission equipment or contact ZTE Corporation.
2.1.14 199001793 SDH/SONET Loss of frame 0

Alarm Property
l Description:SDH/SONET Loss of frame
l Severity:Major
Probable Cause
The upriver SDH equipment has faults.
System Impact
All received trunk signals are broken.
Handling Suggestion
Ask relating maintenance personnel to do troubleshooting of SDH transmission equipment. Please

contact ZTE Corporation if the problem can not be solved.
2.1.15 199001794 SDH/SONET Regenerator section trace

mismatch/Section trace mismatch 0
Alarm Property
l Description:SDH/SONET Regenerator section trace mismatch/Section trace
mismatch
l Severity:Major
2-10

Chapter 2 Alarm
Probable Cause
The optical fiber on the optical distribution frame is wrongly connected during optical fiber cutover and
scheduling, or the expected value is wrongly set in the network management system.
System Impact
The connection of all trunks is incorrect.
Handling Suggestion
1. Check if there is something wrong with the optical fiber connections on ODFs at the local end
and the peer end.
Y-> If there is, go to step 2.
Y-> If there isn't , go to step 3.
2. Have the optical fiber well connected, and check if the alarm is eliminated.
N-> Go to "3"
3. Check if the expected values of the "section access point identifier" at both ends are consistent.
Y-> If they are consistent, go to step 5.
Y-> If they aren't consistent, go to step 4.
4. Configure the same expected value for the "section access point identifier" at both ends, and
then check if the alarm is eliminated.
N-> Go to "5"
5. Please contact ZTE Corporation if the problem can not be solved.
2.1.16 199001795 SDH/SONET MS alarm indication signal/Line

alarm indication signal 0
Alarm Property
l Description:SDH/SONET MS alarm indication signal/Line alarm indication signal
l Severity:Major
Probable Cause
The upriver equipment has faults, such as LOS,LOF etc.
System Impact
All received trunk signals transmitted by this SDH/SONET line are broken.
2-11

Handling Suggestion
Eliminate the "primary fault" according to the alarm generated from the network node equipment in
the corresponding multiplexing section. If the alarm can not be eliminated, please contact ZTE
Corporation.
2.1.17 199001796 SDH/SONET MS far-end reception failure/Line

far-end reception failure 0
Alarm Property
l Description:SDH/SONET MS far-end reception failure/Line far-end reception failure
l Severity:Minor
Probable Cause
The up direction of the downstream equipment has faults.
System Impact
All sended trunk signals transmitted by this SDH/SONET line are broken.
Handling Suggestion
Eliminate the "primary fault" according to the alarm generated from the network node equipment in
the corresponding multiplexing section. If the alarm can not be eliminated, please contact ZTE
Corporation.
2.1.18 199001797 SDH/SONET Signal failure 0

Alarm Property
l Description:SDH/SONET Signal failure
l Severity:Major
2-12

Chapter 2 Alarm
Probable Cause
As for all NEs in the multiplexing section where the board is located, the fiber 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.
System Impact
All recevied trunk signals transmitted by this SDH/SONET line generate kinds of alarms.
Handling Suggestion
1. Check if the fiber pigtail heads are contaminated.

Y-> If they are contaminated, go to step 2.
N-> Go to "3".
2. Clean the fiber connectors, and check if the alarm is eliminated.
N-> Go to "3"
3. Use optical power meter to detect the optical power attenuation of each connection point in the
down direction in the corresponding multiplexing section to see if it is excessive.
Y-> If it is, go to step 4.
N-> Go to "5"
4. Adjust the attenuation to normal value, and check if the alarm is eliminated.
N-> Go to "5"
5. Ask the transmission equipment maintaining personnel to check ADM transmitting device to
see if there is any fault. End alarm handling.
2.1.19 199001798 SDH/SONET Signal deterioration 0

Alarm Property
l Description:SDH/SONET Signal deterioration
l Severity:Minor
Probable Cause
Eliminate SF first when SD and SF occur at the same time; If SD occurs alone, it can be concluded
that the ADM transmission device has faults.
2-13

System Impact
Alarms indicated for partial Trunks.
Handling Suggestion
1. If SF occurs, eliminate SF first. If the problem can still not be eliminated after SF is eliminated, go
to step 2.
2. Check the optical fibers and fiber optical transceivers at the local end and the peer end, and make
sure the fibers are well connected and the optical transceiver modules are not loose.
N-> Go to "3"
N-> Go to "4"
N-> Go to "5"
personnel to do troubleshooting of transmission equipment, or contact ZTE Corporation.
2.1.20 199001799 SDH/SONET Loss of AU pointer/Loss of path

pointer 0
Alarm Property
l Description:SDH/SONET Loss of AU pointer/Loss of path pointer
l Severity:Major
Probable Cause
The upriver AU-4 pointer processing unit has faults.
System Impact
All received trunk signals transmitted by this SDH/SONET line are broken.
Handling Suggestion
Ask the maintenance personnel of transmission network to check if the upstream VC-4 channel
control unit has faults. If the transmission is found no problem, please contact ZTE Corporation.
2-14

Chapter 2 Alarm
2.1.21 199001800 SDH/SONET AU alarm indication signal/Path

alarm indication signal 0
Alarm Property
l Description:SDH/SONET AU alarm indication signal/Path alarm indication signal
l Severity:Major
Probable Cause
The upriver VC-4 channel control unit has faults.
System Impact
All received trunk signals transmitted by this SDH line are broken.
Handling Suggestion
Ask the maintenance personnel of transmission network to check if the upstream VC-4 channel
control unit has faults. If the transmission is found no problem, please contact ZTE Corporation.
2.1.22 199001801 SDH/SONET HP trace mismatch/ Path trace

mismatch 0
Alarm Property
l Description:SDH/SONET HP trace mismatch/ Path trace mismatch
l Severity:Major
Probable Cause
The optical fiber on the optical distribution frame is wrongly connected, or the expected value is
wrongly set in the network management system during optical fiber cutover and scheduling.
System Impact
The connection of all trunks is incorrect.
2-15

Handling Suggestion
and the peer end.
Y-> Go to "3"
N-> Go to "2"
2. Correctly connect the optical fibers on ODFs at the local end and the peer end and then check if
the alarm is eliminated.
N-> Go to "3"
3. Check if the expected values of the "VC-4 channel access point identifier (J1B)" at both ends
are consistent.
Y-> Go to "5"
N-> Go to "4"
4. Configure the same expected values for the "VC-4 channel access point identifier (J1B)" at both
ends, and then check if the alarm is eliminated.
N-> Go to "5"
5. Please contact ZTE Corporation.
2.1.23 199001802 SDH/SONET HP unequipped/Path unequipped 0

Alarm Property
l Description:SDH/SONET HP unequipped/Path unequipped
l Severity:Major
Probable Cause
During project installation, the internal cross connection of SDH network is not complete, or the SDTB
remote device isn't equipped with the channel where SDTB locates.
System Impact
All received trunk signals transmitted by this SDH line are broken.
Handling Suggestion
Ask the maintenance personnel for transmission network to check if the upstream VC-4 channel
control unit has faults(C2B).
2-16

Chapter 2 Alarm
2.1.24 199001803 SDH/SONET HP Label mismatch/Path label

mismatch 0
Alarm Property
l Description:SDH/SONET HP Label mismatch/Path label mismatch
l Severity:Major
Probable Cause
During project installation, the internal cross connection of SDH network is not complete.
System Impact
All received trunk signals transmitted by this SDH line may be broken.
Handling Suggestion
Ask the maintenance personnel for transmission network to check if the upstream and downstream
circuit configuration (C2B) of the DXC devices in each station during the corresponding timeslot
is correct.
2.1.25 199001804 SDH/SONET HP remote reception failure/Path

remote reception failure 0
Alarm Property
l Description:SDH/SONET HP remote reception failure/Path remote reception failure
l Severity:Minor
Probable Cause
There is network node failure in VC-4 channel where board locates.
System Impact
All sended trunk signals transmitted by this SDH/SONET line are broken.
2-17

Handling Suggestion
Eliminate the "source fault" according to the alarm generated from the network node equipment in
VC-4 channel where the board locates. If the alarm can not be eliminated, please contact ZTE
Corporation.
2.1.26 199001805 SDH/SONET Loss of multi-frame 0

Alarm Property
l Description:SDH/SONET Loss of multi-frame
l Severity:Major
Probable Cause
There is failure of the upstream VC-4 channel control unit.
System Impact
All received trunk signals transmitted by this SDH line may be broken.
Handling Suggestion
Ask the maintenance personnel for transmission network to check if the upstream VC-4 channel
control unit (H4) has faults.
2.1.27 199001806 SDH/SONET Loss of TU pointer/Loss of virtual

tributary pointer 0
Alarm Property
l Description:SDH/SONET Loss of TU pointer/Loss of virtual tributary pointer
l Severity:Warning
Probable Cause
The upstream TU pointer processing unit is failure.
2-18

Chapter 2 Alarm
System Impact
The received trunk signal transmitted by this tributary unit is broken.
Handling Suggestion
Ask the maintenance personnel of transmission network to check if the upstream TU-12 tributary
pointer has faults. If the problem can still not be solved, please contact ZTE Corporation.
2.1.28 199001807 SDH/SONET Tributary unit alarm indication

signal/Virtual tributary alarm indication signal 0
Alarm Property
l Description:SDH/SONET Tributary unit alarm indication signal/Virtual tributary alarm
indication signal
l Severity:Warning
Probable Cause
There is failure of the upstream TU-12 tributary pointer processing unit, which may includes TU
AIS\TU LOM\TU LOP\TU UNEQ.
System Impact
Handling Suggestion
Ask the maintenance personnel of transmission network to check if the upstream TU-12 tributary
pointer has faults. If the problem can still not be solved, please contact ZTE Corporation.
2.1.29 199001808 SDH/SONET LP remote defect indication/Virtual

tributary remote defect indication 0
Alarm Property
l Description:SDH/SONET LP remote defect indication/Virtual tributary remote defect
indication
2-19

l Severity:Warning
Probable Cause
1. Local TU-12 tributary function is fault. 2. The equipment of other nodes on TU-12 tributary may
has tributary function faults.
System Impact
The sended trunk signal transmitted by this tributary unit is broken.
Handling Suggestion
1. Check if there is something wrong with the optical fiber connections on ODFs at the local end and
the peer end and check if the processing of TU-12 tributary pointer of the upstream equipment
has faults.
Y-> If there isn't, go to step 3.
2. Have the optic fiber well connected, and check if the alarm is eliminated. This is upstream
troubleshooting.
N-> Go to "3"
3. Check the alarm forms at both ends. Firstly detect the peer-end alarm forms. The peer-end
alarms should be firstly eliminated.Trough loopback operation, perform troubleshooting for local-end
equipment, transmission equipment and peer-end equipment step by step. Software loopback and
hardware loopback can be applied.
Please contact ZTE Corporation or replace the board if the problem can not be solved.
2.1.30 199001809 SDH/SONET LP remote failure indication/Virtual

tributary remote failure indication 0
Alarm Property
l Description:SDH/SONET LP remote failure indication/Virtual tributary remote failure
indication
l Severity:Warning
Probable Cause
The upstream VC-12 tributary control unit is failure.
2-20

Chapter 2 Alarm
System Impact
Handling Suggestion
1. Check if there is something wrong with the optical fiber connections on ODFs at the local end and
the peer end and check if the processing of TU-12 tributary pointer of the upstream equipment
has faults.
Y-> If there isn't, go to step 3.
2. Have the optic fiber well connected, and check if the alarm is eliminated. This is the upstream
troubleshooting.
N-> Go to "3"
3. Check the alarm forms at both ends. Firstly detect the peer-end alarm forms. The peer-end
alarms should be firstly eliminated.Trough loopback operation, perform troubleshooting for local-end
equipment, transmission equipment and peer-end equipment step by step. Software loopback and
hardware loopback can be applied.
Please contact ZTE Corporation or replace the board if the problem can not be solved.
2.1.31 199001810 SDH/SONET LP trace mismatch/Virtual tributary

trace mismatch 0
Alarm Property
l Description:SDH/SONET LP trace mismatch/Virtual tributary trace mismatch
l Severity:Warning
Probable Cause
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.
System Impact
The connection of the trunk signal on this tributary unit is incorrect.
2-21

Handling Suggestion
and the peer end.
Y-> Go to "3"
N-> Go to "2"
2. Correctly connect the optic fibers on ODFs at the local end and the peer end and then check if
N-> Go to "3"
3. Check if the expected values of the "VC-12 channel access point identifier (J2B)" at both ends
are consistent.
Y-> Go to "5"
N-> Go to "4"
4. Configure the same expected values for the "VC-12 channel access point identifier (J2B)" at both
ends, and then check if the alarm is eliminated.
N-> Go to "5"
5. Please contact ZTE Corporation or replace the board.
2.1.32 199001811 SDH/SONET LP unequipped/Virtual tributary

unequipped 0
Alarm Property
l Description:SDH/SONET LP unequipped/Virtual tributary unequipped
l Severity:Warning
Probable Cause
During project installation, the internal cross connection of SDH network is not complete, or the
remote device isn't equipped with the tributary.
System Impact
The received trunk signal transmitted by this tributary unit may be broken.
2-22

Chapter 2 Alarm
Handling Suggestion
1. Check the optical fibers and fiber transceiver modules at the local end and the peer end, and make
sure the fibers are well connected and the fiber modules are not loose.
N-> Go to "2"
2. The configuration connection at both ends needs to be checked by the maintenance personnel.
Check if the signal label received by this tributary is consistent with that configured at local end. After
confirmation, check if the alarm has been eliminated.
N-> Go to "3"
Ask the maintenance personnel for transmission equipment to use SDH tester to check if the
upstream and downstream circuit configuration of each DXC node device on the transmission line
during the corresponding timeslot is correct, and check if V5 byte configuration is consistent with that
at peer-end. (The default configuration at local end is asynchronous mapping.)
4.Replace the board, view alarm information, or contact ZTE Corporation.
2.1.33 199001812 SDH/SONET LP label mismatch/Virtual tributary

label mismatch 0
Alarm Property
l Description:SDH/SONET LP label mismatch/Virtual tributary label mismatch
l Severity:Warning
Probable Cause
The upstream and downstream circuit configuration of each DXC during the corresponding timeslot is
incomplete. The information of V5 signal label is inconsistent with that at the peer end.
System Impact
The received trunk signal transmitted by this tributary unit may be broken.
2-23

Handling Suggestion
N-> Go to "2"
2. The configuration connection at both ends needs to be checked by the maintenance personnel.
Check if the information of V5 signal label is consistent with that at the peer end. After confirmation,
check if the alarm has been eliminated.
N-> Go to "3"
3. Replace the board, view alarm information, or contact ZTE Corporation.
2.1.34 199001816 SDH/SONET Severe B1 error code 0

Alarm Property
l Description:SDH/SONET Severe B1 error code
l Severity:Major
Probable Cause
(1) Signal reception attenuation is excessive. (2) There is failure of transmitting part of directly
connected transmission equipment. (3)Optical fiber connectors is unclean or connection of them is
incorrect.(4) Local-end receiving part is failure.
System Impact
Noise or call lose appears in the tone service on this SDH line. Error code appears in the data
service path.
Handling Suggestion
N-> Go to "2"
N-> Go to "3"
2-24

Chapter 2 Alarm

N-> Go to "4"
personnel special for maintaining transmission equipment to do troubleshooting or contact ZTE
Corporation.

Alarm Property
l Severity:Major
Probable Cause
(1) Signal reception attenuation is excessive. (2) Optical fiber connectors are unclean or connection
of them are incorrect. (3)Peer-end transmitting part failed in multiplexing section.(4) Local-end
receiving part failure in multiplexing section. (5) B1 error code.
System Impact
service path.
Handling Suggestion
N-> Go to "2"
N-> Go to "3"
N-> Go to "4"
Corporation.
2-25


Alarm Property
l Severity:Major
Probable Cause
(1) Signal reception attenuation is excessive. (2) Optical fiber connectors are unclean or connection
of them is incorrect. (3)There is failure of the peer-end transmitting part based on higher order path
(4) Local-end receiving part is failure. (5) B1, B2 error codes.
System Impact
Noise or call lose appears in the tone service on this HP. Error code appears in the data service path.
Handling Suggestion
N-> Go to "2"
N-> Go to "3"
N-> Go to "4"
Corporation.
2.1.37 199001819 SDH/SONET Severe BIP-2 error code 0

Alarm Property
l Description:SDH/SONET Severe BIP-2 error code
l Severity:Warning
2-26

Chapter 2 Alarm
Probable Cause
(1) Low order path is interfered. (2) There is failure of the peer-end transmitting part based on lower
order path. (3) Local-end receiving part is failure.
System Impact
Noise or call lose appears in the tone service on this tributary unit. Error code appears in the data
service path.
Handling Suggestion
N-> Go to "2"
N-> Go to "3"
N-> Go to "4"
Corporation.
2.1.38 199001820 SDH/SONET MS remote error indication 0

Alarm Property
l Description:SDH/SONET MS remote error indication
l Severity:Major
Probable Cause
connected transmission equipment. (3) Optical fiber connectors are unclean or connection of them is
incorrect. (4) Local-end receiving part is failure.
2-27

System Impact
service path.
Handling Suggestion
N-> Go to "2"
N-> Go to "3"
N-> Go to "4"
Corporation.
2.1.39 199001821 SDH/SONET HP remote error indication 0

Alarm Property
l Description:SDH/SONET HP remote error indication
l Severity:Major
Probable Cause
connected transmission equipment. (3) Optical fiber connectors are unclean or connection of them is
incorrect.(4) Local-end receiving part is failure.
System Impact
service path.
2-28

Chapter 2 Alarm
Handling Suggestion
N-> Go to "2"
N-> Go to "3"
N-> Go to "4"
Corporation.
2.1.40 199001826 SDH/SONET LP remote error indication 0

Alarm Property
l Description:SDH/SONET LP remote error indication
l Severity:Warning
Probable Cause
(1) Signal reception attenuation is excessive. (2)There is failure of transmitting part of directly
connected transmission equipment. (3)Optical fiber connectors are unclean or connection of them is
incorrect. (4) Local-end receiving part is failure.
System Impact
Noise or call lose appears in the tone service on this tributary unit. Error code appears in the data
service path.
2-29

Handling Suggestion
N-> Go to "2"
N-> Go to "3"
N-> Go to "4"
Corporation.
2.1.41 199005123 The configuration is not supported 0

Alarm Property
l Description:The configuration is not supported
l Severity:Warning
Probable Cause
Configure is error.
System Impact
The board do not work on the configuration .
Handling Suggestion
1. Check the additional information for this alarm, and look for the configuration error.
2.If this configuration-item is supported in the configure-dialog?
Y->Goto 3
N->Contact ZTE
3. If setting is incorrect, re-configure this item to correct value.
4. If setting is correct, replace the board with witch surpport the setting.
5. If the alarm is still existing?
Y->Goto 4
2-30

Chapter 2 Alarm
N->Contact ZTE
2.1.42 199005405 Clock board phase-lock loop work mode is

abnormal 0
Alarm Property
l Description:Clock board phase-lock loop work mode is abnormal
l Severity:Minor
Probable Cause
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.
System Impact
The designated reference clock cannot be phase-locked.
Handling Suggestion
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.
2.1.43 199005632 The hard disk used-rate is over threshold 0

Alarm Property
l Description:The hard disk used-rate is over threshold
l Severity:Minor
2-31

Probable Cause
The hard disk capacity of used has been over the alarm threshold which configured by user.
System Impact
The hard disk can not work normaly.
Handling Suggestion
1. Please make sure the hard disk usage settings are appropriate. If inappropriate please modify
as appropriate value.
2: Remove non-used data on the hard disk.
2.1.44 199005633 The hard disk is error or does not exist 0

Alarm Property
l Description:The hard disk is error or does not exist
l Severity:Major
Probable Cause
The hard disk becomes error or can not been detected by system.
System Impact
the hard disk can not use, the date can not be stored.
Handling Suggestion
1. Check the hard disk which user configure is exist or not.

Y: Check whether the harddisk has some errors;
if have, go to "2",
if have not, please contact ZTE;
N: End;
2. Fixed the errors or change another good harddisk,
check whether the alarm is clear;
Y: End;
N: Please contact ZTE
2-32

Chapter 2 Alarm
2.1.45 199005634 The hard disk on board gets IO error. 0

Alarm Property
l Description:The hard disk on board gets IO error.
l Severity:Minor
Probable Cause
The hard disk file system gets error when reading or writing.
System Impact
The hard disk can not work normaly.
Handling Suggestion
1. Check the hard disk is damaged or not;

Y: Repair the hard disk. If it's still gets IO error, go to "2";
N: Go to "2";
2. Change another good hard disk, Check the hard disk has IO error or not;
Y: Contact the ZTE;
N: End
2.1.46 199005646 Phase-lock loop of the board is unlocked 0

Alarm Property
l Description:Phase-lock loop of the board is unlocked
l Severity:Critical
Probable Cause
1. The clock extraction reference is changed, including the case that the clock output is closed by
the interface board when optical port is faulty. This leads to the change of clock board input. Or,
configuration is modified at NMS and a new optical port is used to extract the clock.
2. The change in input of clock board results in the change in output.
3. The board lock phase loop has hardware faults.
2-33

System Impact
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.
Handling Suggestion
1. On NMS fault management interface, check if the related clock alarm occur. If yes, handle the
alarm by referring to the corresponding suggestions.
2. On NMS fault management interface, check if related alarms occur on the optical port for clock
extraction. If yes, handle the alarm by referring to the corresponding suggestions.
3. Check the operation and maintenance logs. If the operation of changing the clock extraction
reference for the loop is recorded, report the alarm as a normal phenomenon. In this case, no
handling operation is required.
4. Switch to the standby clock board.
2.1.47 199005666 Error packets of MAC is higher than the specified

threshold 0
Alarm Property
l Description:Error packets of MAC is higher than the specified threshold
l Severity:Minor
Probable Cause
Error packets of MAC is higher than specified threshold.
System Impact
The MAC port cannot be used or packets flow is limited.
2-34

Chapter 2 Alarm
Handling Suggestion
1.Check the connection between the port on this board and the peer end one if it is correct.
Y->Go to "2"
N->Check physical cable ,if it is not good, please replace a good cable, and check the alarm if
it is eliminated.
Y-> End.
N-> Go to "2".
2.Replace the board on the local end or the interface on the remote peer end and then check the
alarm if it is eliminated.
Y->End.
N->Go to "3"
3.Replace the remote peer board or the interface on the local end and then check the alarm if it is
eliminated.
Y->End.
2.1.48 199005670 Oscillator status is abnormal 0

Alarm Property
l Description:Oscillator status is abnormal
l Severity:Critical
Probable Cause
Oscillator may stop oscillating or meet frequency deviation.
System Impact
Board cannot work normally with this crucial device error.
Handling Suggestion
Replace the board.
2.1.49 199005672 Clock source is not available 0

Alarm Property
2-35

l Description:Clock source is not available
l Severity:Critical
Probable Cause
There are four reasons:

1. The slave clock port does not receive ESMC PDU for 5 seconds.
2. The SSM code that the slave clock port received is DNU.
3. The speed mode of the port is 10M.
4. Physical link of the port is broken.
System Impact
The slave clock port can not synchronize to the connected port.
Handling Suggestion
Check the physical connection, reconfigure the clock port or reconnect the port.
2.1.50 199005673 The setting of the dial switch is changed 0

Alarm Property
l Description:The setting of the dial switch is changed
l Severity:Major
Probable Cause
The setting of the dial switch on the CMM board has been changed.
System Impact
The board can not power on nomally.
2-36

Chapter 2 Alarm
Handling Suggestion
1) Checking the setting of dial switch is changed or not .

Y-> Go to 2)
N-> Go to 3)
2) Whether the user has modified the rack and shelf configuration and wants to update dial switch
setting to the configuration value.
Y-> Reset CMM board, then reset all the boards in the same shelf. If the boards power on normally,
to the end; otherwise, go to 3)
N-> Modify the setting to the correct value. If the alarm is recovered, to the end; otherwise go to 3)
3) Replace the CMM board and make the correct dial switch setting. Checking the alarm is recovered
or not.
Y-> To the end;
N-> Contact to ZTE.
2.1.51 199005760 Ethernet port's link is down 0

Alarm Property
l Description:Ethernet port's link is down
l Severity:Warning
Probable Cause
Ethernet port's link is down.
System Impact
MAC port can't transfer data.
Handling Suggestion
1. Reconnect or replace the cable.

3. Check the opposite port to make sure if it is falut.
4. Please modify the settings of the port to be correct. Please make work mode, speed mode, duplex
mode of both ends to be same. Please make master and slave mode to be match with each other.
2-37

2.1.52 199005761 The speed mode of Ethernet port doesn't match

with settings 0
Alarm Property
l Description:The speed mode of Ethernet port doesn't match with settings
l Severity:Major
Probable Cause
The speed mode settings of Ethernet port does not take effect.
System Impact
Ethernet port does not work on the speed mode which is set.
Handling Suggestion
1.Check the speed settings on the both end ports if they are correct and consistent.
Y->Go to "2".
N->Modify the speed settings on the both end to make it correct and consistent with each other, and
then check the alarm if it is eliminated.
Y->End.
N->Go to "2".
2.Please contact ZTE Corporation.
2.1.53 199005768 All of the board input clocks which have the same
frequency are lost. 0
Alarm Property
l Description:All of the board input clocks which have the same frequency are lost.
l Severity:Major
2-38

Chapter 2 Alarm
Probable Cause
1. The board is not in place (not properly inserted) in the slot.
2. The output clock of the clock board in the same shelf is error.
3. Clock board is faulty.
4. Clock cable is faulty.
5. Board is faulty.
System Impact
The board fails to synchronize with system clock and fails to work normally, leading to UE access
failure and interruption of board services.
Handling Suggestion
1. Check if the clock board in the same shelf is normal and the clock input cable is properly connected.
2.1.54 199005769 The master and slave mode of Ethernet port

doesn't match with settings 0
Alarm Property
l Description:The master and slave mode of Ethernet port doesn't match with settings
l Severity:Major
Probable Cause
The master and slave mode settings of Ethernet port does not take effect.
System Impact
The Ethernet port does not work on the master and slave mode which is set.
Handling Suggestion
1.Check the master and slave mode settings on the both end ports if they are correct and consistent.
Y->Go to "2".
N->Modify the master and slave mode settings on the both end ports to make them correct and
consistent with each other, and then check the alarm if it is eliminated.
Y->End.
N->Go to "2".
2-39

2.1.55 199005770 The OMP board doesn't have any OMC port 0
Alarm Property
l Description:The OMP board doesn't have any OMC port
l Severity:Warning
Probable Cause
The OMP board doesn't have any OMC port.
System Impact
The OMP board could not communicate by OMC port.
Handling Suggestion
1.Check the backcard to make sure it is correct and inserted well.

2.Check the hardware of the board to make sure it supports OMC port.
2.1.56 199005771 The duplex mode of Ethernet port doesn't match

with settings 0
Alarm Property
l Description:The duplex mode of Ethernet port doesn't match with settings
l Severity:Major
Probable Cause
The duplex mode settings of Ethernet port does not take effect.
System Impact
Ethernet port does not work on the duplex mode which is set.
2-40

Chapter 2 Alarm
Handling Suggestion
1.Check the duplex mode settings on the both ports end if they are correct and consistent.
Y->Go to "2".
N->Modify the duplex mode settings on the both end ports to make them correct and consistent with
each other, and then check the alarm if it is eliminated.
Y->End.
N->Go to "2".
2.1.57 199005772 Board device fault 0

Alarm Property
l Description:Board device fault
l Severity:Minor
Probable Cause
Fault occur when read or write the register on the board, this is may be the hardware fault.
System Impact
Board operation might be abnormal.
Handling Suggestion
Replace the board.
2.1.58 199005773 High CRC error rate at E1/T1 bottom layer 0

Alarm Property
l Description:High CRC error rate at E1/T1 bottom layer
l Severity:Major
2-41

Probable Cause
The E1/T1 link is faulty or there is any other equipment fault in the uplink direction of the trunk link.
System Impact
Handling Suggestion
1. Check whether the trunk link at the local end is faulty and eliminate the primary fault. After that,
check if the alarm is eliminated.
N-> Go to "2"
2. Check whether there is any other equipment fault in the uplink direction of the trunk link. After
that, check if the alarm is eliminated.
2.1.59 199005774 High FAS error rate at E1/T1 bottom layer 0

Alarm Property
l Description:High FAS error rate at E1/T1 bottom layer
l Severity:Major
Probable Cause
The E1/T1 link is faulty or there is any other equipment fault in the uplink direction of the trunk link.
System Impact
2-42

Chapter 2 Alarm
Handling Suggestion
N-> Go to "2"
2.1.60 199005775 High EBIT error rate at E1 bottom layer 0

Alarm Property
l Description:High EBIT error rate at E1 bottom layer
l Severity:Major
Probable Cause
The E1 link is faulty or there is any other equipment fault in the downlink direction of the trunk link.
System Impact
Handling Suggestion
N-> Go to "2"
2-43

2.1.61 199005785 GPS module is abnormal 0

Alarm Property
l Description:GPS module is abnormal
l Severity:Major
Probable Cause
1.GPS is in searching state.

2.Satellite number that the GPS device searched is less than 4.
3.GPS PP1S output dither is very bad.
4.GPS antenna is abnormal.
System Impact
The board fails to synchronize with system clock and fails to work normally, leading to UE access
failure and interruption of board services.
Handling Suggestion
Check the GPS receiver and antenna feed status.
2.1.62 199005890 Functional EPLD update failed 0

Alarm Property
l Description:Functional EPLD update failed
l Severity:Warning
Probable Cause
Function EPLD update failed.
System Impact
EPLD version is not update.
2-44

Chapter 2 Alarm
Handling Suggestion
1.Check whether the switch board is in the same shelf as this board, or the switch board in the shelf
where the OMP is located and the switch board (if there is any) are working normally.
Y-> Go to Step 2
N-> Restore the boards above to normal state, and check whether this alarm disappears: Y-> Go
to Step 2, N-> Contact ZTE.
2.Update the EPLD version again, and chek the board EPLD version is the new version number.
Y-> End.
N-> Contact ZTE.
2.1.63 199005930 NCPU version load failed 0

Alarm Property
l Description:NCPU version load failed
l Severity:Major
Probable Cause
NCPU version load failed.
System Impact
NCPU RUNNING ERR
Handling Suggestion
1.Check the Version exist.

Y.Turn 2.
N.Load the version and reload.
2.reboot the Ncpu device, and chek the alarm also existed.
Y.Alarm restore;
N.Turn 3.
3.change the board ,and reload.
Y.Load success ,hardware problem,turn 4.
N.Turn 4.
4.contact ZTE Corporation .
2-45

2.1.64 199007168 Port trunk fail 0

Alarm Property
l Description:Port trunk fail
l Severity:Minor
Probable Cause
PP board port aggregation failure:

1.Switch Board is not in place.
2.Port transceiver package exception.
switch board stack port aggregation failure：
1.Mate Board is not in place.
2.stack port transceiver package exception.
System Impact
as for PP board,the link connected with switch board does not work. As for switch board,if all of the
stack ports trunk failed, all ports of the poor board do not work.
Handling Suggestion
PP board port aggregation failure:

1.Check the both Switch Boards are in place.
Y->turn to 2.
N.if one is not in place,the port connected to tht switch board is at down state, the PP baord will
report warning information.
2.record the warning inforation,and contact with ZTE.
switch board stack port aggregation failure：
1.Check the mate Board is in place.
Y->turn to 2.
N.if it is not in place,the switch board will report warning information.
2.record the warning inforation,and contact with ZTE.
2.1.65 199007169 Inner port error 0

Alarm Property
l Description:Inner port error
2-46

Chapter 2 Alarm
l Severity:Minor
Probable Cause
1. The duplex mode of the switch port is abnormal and can't heal self.
2. The speed of the switch port is abnormal and can't heal self.
3. The duplex mode of the mac port is abnormal and can't heal self.
4. The speed of the mac port is abnormal and can't heal self.
System Impact
1. PP board: link broken

2. switch board: can't link to the pp board
Handling Suggestion
1. Reboot the board and check whether the alarm is restored.

Y-> End alarm handling.
N-> Make record of the related information and contact ZTE.
2.1.66 199007170 Trunk connect asymmetry 0

Alarm Property
l Description:Trunk connect asymmetry
l Severity:Minor
Probable Cause
Ports of the trunk are not symmetry
System Impact
System work abnormally
Handling Suggestion
check ports connect
2-47

2.1.67 199007171 Outer media trunk failed 0

Alarm Property
l Description:Outer media trunk failed
l Severity:Minor
Probable Cause
1.Media ports between the shelf are not linked or trunk failed
System Impact
adjunct shelf's media work abnormally
Handling Suggestion
check ports connect
2.1.68 199015360 Media status abnormal 0

Alarm Property
l Description:Media status abnormal
l Severity:Major
Probable Cause
the network process part such as the media cores, microengines or APP650/APP100 are abnormal
System Impact
The media process doesn't work
Handling Suggestion
Most probably because of the hardware error. If occurs repeatly, replace the board.
2-48

Chapter 2 Alarm
2.1.69 199015618 Too many bad frames received 0

Alarm Property
l Description:Too many bad frames received
l Severity:Minor
Probable Cause
the number of bad frames that the media interfaces have received at a certain period of time exceeds
the threshold
System Impact
May reduce the quality of communication
Handling Suggestion
Check the connection of fibre/wire.If occurs repeatly, replace the board.
2.1.70 199019712 APS channel mismatch 0

Alarm Property
l Description:APS channel mismatch
l Severity:Major
Probable Cause
Peer-end faults (configuration faults or devices which do not support exist, the symptom is the
bridging channel that the remote end indicates through K2 is not the one required by the local).
System Impact
APS automatic protection switching function is paralyzed. When the work optical port is abnormal,
protection optical port will not work, leading to service interruption on this optical interface.
2-49

Handling Suggestion
1. Check fiber connection.

Check fiber 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.
2. Check APS backup mode configuration at both ends.
Check APS backup mode (1+1 or 1:1) at local end to ensure configuration consistency at both ends.
3. Check APS protection direction at both ends.
Check APS protection direction (unidirectional or bidirectional) configured at local end. Ensure
configuration consistency at both ends.
4. Check whether APS is supported by the opposite equipment. Check whether APS configuration is
correct and has taken effect.
2.1.71 199019713 APS mode mismatch 0

Alarm Property
l Description:APS mode mismatch
l Severity:Major
Probable Cause
1. Fiber connection is wrong.

2. Configuration of APS backup mode at local end and opposite end is inconsistent.
3. Configuration of APS protection direction at local end and opposite end is inconsistent.
4. The equipment of the peer end is abnormal.
System Impact
When fiber connection is correct and work optical port works, service is not affected.
When work optical port is faulty, APS automatic protection switching might fail, and service on this
optical interface might be interrupted due to lack of protection.
2-50

Chapter 2 Alarm
Handling Suggestion
1. Check fiber connection.

Check fiber 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.
2. Check APS backup mode configuration at both ends.
Check APS backup mode (1+1 or 1:1) at local end to ensure configuration consistency at both ends.
3. Check APS protection direction at both ends.
Check APS protection direction (unidirectional or bidirectional) configured at local end. Ensure
configuration consistency at both ends.
2.1.72 199019715 MS APS channel gets errors 0

Alarm Property
l Description:MS APS channel gets errors
l Severity:Major
Probable Cause
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.
System Impact
1. APS function is affected.

2. The board master/slave function is affected.
Handling Suggestion
Please try the following steps:

1. Reboot the board.
3. Replace the neighboring board.
4. Replace the slots .
2.1.73 199023050 Fan Device Absent 0

Alarm Property
2-51

l Description:Fan Device Absent
l Severity:Major
Probable Cause
Fan Device Removed /Fan Device Absent
System Impact
Device damaged
Handling Suggestion
Check fantray module
2.1.74 199023051 Power Unit Absent 0

Alarm Property
l Description:Power Unit Absent
l Severity:Major
Probable Cause
Power Unit Removed /Power Unit Absent
System Impact
Power Supply may be not enough
Handling Suggestion
Check power unit
2.1.75 199023106 Board initialized test failed 0

Alarm Property
2-52

Chapter 2 Alarm
l Description:Board initialized test failed

l Severity:Critical
Probable Cause
There are devices failure on the board.
System Impact
The devices of the board is not available.
Handling Suggestion
1. Check Alarm information of the board.

1) Whether there is memory's fault.
Y-> Remove and plug the memory card again, power on the board to check if the alarm restored. Y->
The troubleshooting completes. N-> go to "2)".
N-> no memory’s fault,go to "2".
2) Replace the memory card by a new one and power on the board,then check if the alarm restored.
Y-> The troubleshooting completes. N-> go to "2".
2. Replace the faulty board by a new one
and power one the board to check if the alarm restored. Y-> The troubleshooting completes. N->
go to "3".
3. Make records of the alarm
information and contact ZTE Cooperation.
2.1.76 199025602 Half-Fixed Connection abnormal 0

Alarm Property
l Description:Half-Fixed Connection abnormal
l Severity:Major
Probable Cause
Reason A: The line clock of the frame where this board is located in has jitters.
Reason B: There is a hardware fault in the switching chip of this board.
System Impact
The bear link maybe not work
2-53

Handling Suggestion
1.Check connect chip clock is working order. Check whether the problem is repaired when the
worked out clock error.
Y->Done N->Go to step2
2.Change the board, Check whether the problem is repaired when changed the board.
Y->Done N->contact ZTE
2.1.77 199025856 Rack temperature is higher than high threshold 0

Alarm Property
l Description:Rack temperature is higher than high threshold
l Severity:Minor
Probable Cause
The temperature of the rack exceeds the pre-set upper limit of the alarm threshold.
System Impact
Handling Suggestion
1.Check if the pre-set high limit of the alarm threshold configured in the background for rack
temperature is reasonable.
Y->Go to "2".
N->Modify the alarm threshold and synchronize it to the foreground. Check if the alarm is eliminated:
if so, end. If not, go to "2".
2.Increase the temperature of the rack and check if the alarm is eliminated.
Y->End.
N->Contact ZTE Corporation.
2.1.78 199025857 Rack temperature is lower than low threshold 0

Alarm Property
l Description:Rack temperature is lower than low threshold
2-54

Chapter 2 Alarm
l Severity:Minor
Probable Cause
1.Rack temperature value reported now is under the low threshold.

2.The setting of the rack temperature detector is error.
System Impact
Handling Suggestion
1.Check if the pre-set lower limit of the alarm threshold configured in the background for rack
temperature is reasonable.
Y->Go to "2".
N->Modify the alarm threshold and synchronize it to the foreground. Check if the alarm is eliminated:
if so, end. If not, go to "2".
2.Increase the temperature of the rack and check if the alarm is eliminated.
Y->End.
2.1.79 199025858 Room temperature is higher than high threshold 0

Alarm Property
l Description:Room temperature is higher than high threshold
l Severity:Minor
Probable Cause
The temperature in the equipment room exceeds the upper limit of the alarm threshold
System Impact
2-55

Handling Suggestion
1.Check the high threshold of equipment room temperature on background to see whether it is
rational.
Y->Go to "2".
N->Modify the threshold and upload it to the foreground, and then check whether the alarm
disappears. The handling of this alarm is ended if it disappears, or go to "2" if it does not.
2.Cool the equipment room, and check whether the alarm disappears.
Y->End.
N->Contact ZTE.
2.1.80 199025859 Room temperature is lower than low threshold 0

Alarm Property
l Description:Room temperature is lower than low threshold
l Severity:Minor
Probable Cause
1.Room temperature value reported now is under the low threshold

2.The setting of the room temperature detector is error.
System Impact
Handling Suggestion
1.Check the low threshold of equipment room temperature on background to see whether it is rational.
Y->Go to "2".
2.Warm up the equipment room, and check whether the alarm disappears.
Y->End.
N->Contact ZTE.
2-56

Chapter 2 Alarm
2.1.81 199025860 Voltage is higher than high threshold 0

Alarm Property
l Description:Voltage is higher than high threshold
l Severity:Minor
Probable Cause
Voltage of a line exceeds the upper limit of the alarm threshold
System Impact
Handling Suggestion
1.Check the high voltage threshold on background to see whether it is rational.

Y->Go to "2".
2. Lower down the voltage, and check whether the alarm disappears.
Y->End.
N->Contact ZTE.
2.1.82 199025861 Voltage is lower than low threshold 0

Alarm Property
l Description:Voltage is lower than low threshold
l Severity:Minor
Probable Cause
1.Voltage value is under the low threshold

2.The setting of the votage detector is error
System Impact
2-57

Handling Suggestion
1.Check the low voltage threshold on background to see whether it is rational.

Y->Go to "2".
2.Increase the voltage, and check whether the alarm disappears.
Y->End.
N->Contact ZTE.
2.1.83 199025862 Humidity is higher than high threshold 0

Alarm Property
l Description:Humidity is higher than high threshold
l Severity:Minor
Probable Cause
The humidity in equipment room exceeds the upper limit of the alarm threshold.
System Impact
Handling Suggestion
1.Check the high humidity threshold on background to see whether it is rational.

Y->Go to "2".
2.Lower down the humidity, and check whether the alarm disappears.
Y->End.
N->Contact ZTE.
2.1.84 199025863 Humidity is lower than low threshold 0

Alarm Property
2-58

Chapter 2 Alarm
l Description:Humidity is lower than low threshold

l Severity:Minor
Probable Cause
1.Room humidity value is under the low threshold

2.The setting of the room humidity detector is error
System Impact
Handling Suggestion
1.Check the low humidity threshold on background to see whether it is rational.

Y->Go to "2".
2.Increase the humidity, and check whether the alarm disappears.
Y->End.
N->Contact ZTE.
2.1.85 199025864 Fault in fan plug-in box 0

Alarm Property
l Description:Fault in fan plug-in box
l Severity:Minor
Probable Cause
1.Fan works in error

2.The setting of the fan detector is error
System Impact
2-59

Handling Suggestion
1.Check whether the fan plug-in box and its power line are connected securely (indicators are normal).
Y->go to "2".
N->Secure the fan plug-in box and connect the power line, and then check whether this alarm
2.Replace the fan plug-in box with a good one and check whether the alarm disappears.
Y->End.
N->Contact ZTE.
2.1.86 199025865 Rack door access control alarm 0

Alarm Property
l Description:Rack door access control alarm
l Severity:Minor
Probable Cause
1.The related rack door is not closed.

2.The setting of the door detector is error
System Impact
Handling Suggestion
1.Check whether the rack door is closed.

Y->go to "2".
N->Close the rack door, and check whether this alarm disappears. Y->End., N->go to "2".
2.Check whether the rack door access control system is correctly connected.
Y->Contact ZTE.
N->Connect the access control system and close the rack door, and check whether this alarm
disappears. Y->End., N->Contact ZTE.
2.1.87 199025866 Smoke alarm 0

Alarm Property
2-60

Chapter 2 Alarm
l Description:Smoke alarm
l Severity:Minor
Probable Cause
1.Alarm because of fume exceed the high threshold

2.The setting of the fume detector is error
System Impact
Handling Suggestion
1.Check whether there is smoke in the equipment room.

Y->Dispel the smoke, and check whether this alarm disappears. Y->End., N->Contact ZTE.
N->Contact ZTE.
2.1.88 199025867 Infrared alarm 0

Alarm Property
l Description:Infrared alarm
l Severity:Minor
Probable Cause
1.The infrared is too strong.

2.The setting of the infrared detector is error.
System Impact
2-61

Handling Suggestion
1.Check whether there is any animals or human near the infrared detector.
Y->Make the animal or human away from the detector.
N->go to "2".
2.Check whether the setting of the infrared detector is correct.
Y or do not know how to check ->Contact ZTE.
N->Set the infrared detector, and check whether this alarm disappears. Y->End., N->Contact ZTE.
2.1.89 199025868 Lightning alarm 0

Alarm Property
l Description:Lightning alarm
l Severity:Minor
Probable Cause
1.Alarm because of thunder

2.The setting of the thunder detector is error
System Impact
Handling Suggestion
1.Check whether there is lightning hazard.

Y->Take protection measures, and check whether this alarm disappears. Y->End., N->Contact ZTE.
N->Contact ZTE.
2.1.90 199025869 Power switch alarm 0

Alarm Property
l Description:Power switch alarm
l Severity:Minor
2-62

Chapter 2 Alarm
Probable Cause
1.Atmosphere switch is open and configured.
2.The setting of the atmosphere switch detector is error
System Impact
Shelf power supply might be affected.
Handling Suggestion
1.Check if the power switch is closed and check if the ALM indicator light is normal
Y->Go to "2"
N->Close the power switch please Y->The end, N->Go to "2"
2.Check if the power switch signal is shielded by the background
Y->The end
2.1.91 199025870 Power type configured does not accord with

physical 0
Alarm Property
l Description:Power type configured does not accord with physical
l Severity:Minor
Probable Cause
The power type configured in the database does not accord with the board hardware equipment.
System Impact
The board is faulty.
Handling Suggestion
1.Check the background configuration according to the additional information of the alarm to see
if the configuration conforms to the board hardware equipment.
Y->If yes, go to "2".
N->If no, modify the configuration according to the hardware equipment and re-power on the board.
The alarm will be eliminated.
2.The database configuration is consistent with the equipment hardware while the alarm still can not
be eliminated. In this case, please contact ZTE Corporation.
2-63

2.1.92 199026127 Clock reference source lost (Level 3 alarm) 0

Alarm Property
l Description:Clock reference source lost (Level 3 alarm)
l Severity:Minor
Probable Cause
Input clock reference is in unavailable status for no more than 10 minutes.

Probable causes include:
1. Clock reference input is abnormal.
2. The configured clock reference does not exist.
System Impact
When all configured 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.
Handling Suggestion
1. Reconnect the input clock reference.

2. For the clock reference not in use, delete the corresponding "Circuitry Clock Reference"
configuration on NMS configuration management interface (board property).

Alarm Property
l Severity:Major
Probable Cause
Input clock reference is in unavailable status for more than 10 minutes and less than 24 hours.
2-64

Chapter 2 Alarm
System Impact
Handling Suggestion


Alarm Property
l Severity:Critical
Probable Cause
Input clock reference is in unavailable status for more than 24 hours.

System Impact
Handling Suggestion

2-65

2.1.95 199026133 Output clock of the board is lost 0

Alarm Property
l Description:Output clock of the board is lost
l Severity:Major
Probable Cause
Hardware is faulty.
System Impact
The synchronization of system clock will fail and service interruption will occur.
Handling Suggestion
Replace the board.
2.1.96 199029184 SNTP time-synchronization failed 0

Alarm Property
l Description:SNTP time-synchronization failed
l Severity:Minor
Probable Cause
1.The source addresses of SNTP client configuration is error.

2.SNTP servers faults.
3.Network communication faults.
System Impact
SNTP doesn't work.
2-66

Chapter 2 Alarm
Handling Suggestion
1.Check whether the source addresses of SNTP client configuration is correct.

Y->go to "3".
N->go to "2".
2.Configure the correct source addresses of SNTP client again, then check whether the alarm
is restored.
Y->over.
N->go to "3".
3.Check whether the SNTP server is available.
Y->go to "5".
N->go to "4".
4.Solve SNTP server problem，then check whether the alarm is restored.
Y->over.
N->go to "5".
5.Check whether the link between SNTP servers and client is available.
Y->Contact ZTE.
N->Solve the link problem.
2.1.97 199030721 Temperature is lower than lower-non-critical

threshold. 0
Alarm Property
l Description:Temperature is lower than lower-non-critical threshold.
l Severity:Warning
Probable Cause
Velocity of fan is larger than normal;Temperature of environment is too low( Not often happen)
System Impact
Maybe make the velocity of data processing go down
Handling Suggestion
Depressing the velocity of fan;Improving the temperature of environment
2-67

2.1.98 199030722 Temperature is lower than lower-critical

threshold. 0
Alarm Property
l Description:Temperature is lower than lower-critical threshold.
l Severity:Minor
Probable Cause
Velocity of fan is too larger;Temperature of environment is too lower(Not often happen)
System Impact
Maybe make the velocity of processing going down and some data missing
Handling Suggestion
Depressing the velocity of fan;Improving the temperature of environment
2.1.99 199030723 Temperature is lower than lower-non-recoverable

threshold. 0
Alarm Property
l Description:Temperature is lower than lower-non-recoverable threshold.
l Severity:Major
Probable Cause
Too lower temperature lead to circuit damaged(Not often happen)
System Impact
Some functions of System maybe lost
Handling Suggestion
Power off right now and repaired it
2-68

Chapter 2 Alarm
2.1.100 199030724 Temperature is higher than upper-non-critical

threshold. 0
Alarm Property
l Description:Temperature is higher than upper-non-critical threshold.
l Severity:Warning
Probable Cause
Velocity of fan is lower than normal;Temperature of environment is too high.(Not often happen)
System Impact
Maybe the velocity of processing will go down
Handling Suggestion
Improving the velocity of fan;Depressing the temperature of

environment
2.1.101 199030725 Temperature is higher than upper-critical

threshold. 0
Alarm Property
l Description:Temperature is higher than upper-critical threshold.
l Severity:Minor
Probable Cause
Velocity of fan is too low or the temperature of environment is too high(Not often happen)
System Impact
Maybe the velocity of processing will go down and some data missing.
2-69

Handling Suggestion
Improving the velocity of fan;Depressing the temperature of

environment
2.1.102 199030726 Temperature is higher than upper-non-recovera

ble threshold. 0
Alarm Property
l Description:Temperature is higher than upper-non-recoverable threshold.
l Severity:Major
Probable Cause
Too high temperature lead to circuit damaged
System Impact
Handling Suggestion
2.1.103 199030727 Voltage is lower than lower-non-critical

threshold. 0
Alarm Property
l Description:Voltage is lower than lower-non-critical threshold.
l Severity:Warning
Probable Cause
Power fluctuate
2-70

Chapter 2 Alarm
System Impact
Some system functions maybe lost
Handling Suggestion
Check the power and payload
2.1.104 199030728 Voltage is lower than lower-critical threshold. 0

Alarm Property
l Description:Voltage is lower than lower-critical threshold.
l Severity:Minor
Probable Cause
Maybe aroused by payload changing
System Impact
Some system functions maybe lost or arouse more serous trouble
Handling Suggestion
Check the payload and power
2.1.105 199030729 Voltage is lower than lower-non-recoverable

threshold. 0
Alarm Property
l Description:Voltage is lower than lower-non-recoverable threshold.
l Severity:Major
Probable Cause
Resistance invalid;Influenced by environment
2-71

System Impact
Parts of circuit may be damaged
Handling Suggestion
2.1.106 199030730 Voltage is higher than upper-non-critical

threshold. 0
Alarm Property
l Description:Voltage is higher than upper-non-critical threshold.
l Severity:Warning
Probable Cause
Power fluctuate
System Impact
Handling Suggestion
Check the power and payload situation
2.1.107 199030731 Voltage is higher than upper-critical threshold. 0

Alarm Property
l Description:Voltage is higher than upper-critical threshold.
l Severity:Minor
Probable Cause
2-72

Chapter 2 Alarm
System Impact
Parts of system functions maybe lost or arouse more serous trouble
Handling Suggestion
Check the payload
2.1.108 199030732 Voltage is higher than upper-non-recoverable

threshold. 0
Alarm Property
l Description:Voltage is higher than upper-non-recoverable threshold.
l Severity:Major
Probable Cause
System Impact
Handling Suggestion
2.1.109 199030734 Velocity of fan is lower than lower-critical

threshold. 0
Alarm Property
l Description:Velocity of fan is lower than lower-critical threshold.
l Severity:Major
2-73

Probable Cause
Machine malfunction;Voltage abnormal
System Impact
Will arouse the rising of shelf temperature
Handling Suggestion
Check the fan
2.1.110 199030739 Current is lower than lower-non-critical

threshold. 0
Alarm Property
l Description:Current is lower than lower-non-critical threshold.
l Severity:Warning
Probable Cause
Power fluctuate
System Impact
Handling Suggestion
Check the power and payload
2.1.111 199030740 Current is lower than lower-critical threshold. 0

Alarm Property
l Description:Current is lower than lower-critical threshold.
l Severity:Minor
2-74

Chapter 2 Alarm
Probable Cause
System Impact
Some system functions maybe lost or arouse more serous trouble
Handling Suggestion
Check the payload and power
2.1.112 199030741 Current is lower than lower-non-recoverable

threshold. 0
Alarm Property
l Description:Current is lower than lower-non-recoverable threshold.
l Severity:Major
Probable Cause
System Impact
Handling Suggestion
2.1.113 199030742 Current is higher than upper-non-critical

threshold. 0
Alarm Property
l Description:Current is higher than upper-non-critical threshold.
l Severity:Warning
2-75

Probable Cause
Power fluctuate
System Impact
Handling Suggestion
Check the power and payload situation
2.1.114 199030743 Current is higher than upper-critical threshold. 0

Alarm Property
l Description:Current is higher than upper-critical threshold.
l Severity:Minor
Probable Cause
System Impact
Parts of system functions maybe lost or arouse more serous trouble
Handling Suggestion
Check the payload
2.1.115 199030744 Current is higher than upper-non-recoverable

threshold. 0
Alarm Property
l Description:Current is higher than upper-non-recoverable threshold.
l Severity:Major
2-76

Chapter 2 Alarm
Probable Cause
System Impact
Handling Suggestion
2.1.116 199030745 Velocity of fan is lower than lower-non-critical

threshold. 0
Alarm Property
l Description:Velocity of fan is lower than lower-non-critical threshold.
l Severity:Minor
Probable Cause
System Impact
Handling Suggestion
Check the fan
2.1.117 199030746 Velocity of fan is lower than lower-non-recovera

ble threshold. 0
Alarm Property
l Description:Velocity of fan is lower than lower-non-recoverable threshold.
l Severity:Major
2-77

Probable Cause
System Impact
Handling Suggestion
Check the fan
2.1.118 199030747 Module/Board Device Absent 0

Alarm Property
l Description:Module/Board Device Absent
l Severity:Minor
Probable Cause
Module/Board Device Removed / Device Absent
System Impact
Handling Suggestion
Check Module/Board in Add-info
2.1.119 199030748 Power On Failed due to S5 0

Alarm Property
l Description:Power On Failed due to S5
l Severity:Minor
2-78

Chapter 2 Alarm
Probable Cause
Hardware may be abnormal
System Impact
Board can't enter word status.
Handling Suggestion
Check board
2.1.120 199030808 Processor Internal Error 0

Alarm Property
l Description:Processor Internal Error
l Severity:Minor
Probable Cause
Processor Internal Error happens.
System Impact
System can not work normally.
Handling Suggestion
Check Board Hardware
2.1.121 199030809 Processor Thermal Trip 0

Alarm Property
l Description:Processor Thermal Trip
l Severity:Minor
2-79

Probable Cause
Processor Thermal Trip。
System Impact
System can not work normally.
Handling Suggestion
Check Board Hardware
2.1.122 199083851 Dry contact alarm - Waterlog 0

Alarm Property
l Description:Dry contact alarm - Waterlog
l Severity:Major
Probable Cause
Waterlog alarm
System Impact
N/A
Handling Suggestion
Perform different process methods according to the type of the exterior device. User can define the
treatment measures according to the actual situation.
2.1.123 199083852 Dry contact alarm - Power loss 0

Alarm Property
l Description:Dry contact alarm - Power loss
l Severity:Major
2-80

Chapter 2 Alarm
Probable Cause
Power loss
System Impact
N/A
Handling Suggestion
2.1.124 199083853 Dry contact alarm - No.1 air conditioner fault 0

Alarm Property
l Description:Dry contact alarm - No.1 air conditioner fault
l Severity:Major
Probable Cause
No.1 air conditioner fault
System Impact
N/A
Handling Suggestion
2.1.125 199083854 Dry contact alarm - No.2 air conditioner fault 0

Alarm Property
l Description:Dry contact alarm - No.2 air conditioner fault
l Severity:Major
2-81

Probable Cause
No.2 air conditioner fault
System Impact
N/A
Handling Suggestion
2.1.126 199083855 Dry contact alarm - AC power abnormal 0

Alarm Property
l Description:Dry contact alarm - AC power abnormal
l Severity:Major
Probable Cause
AC power abnormal
System Impact
N/A
Handling Suggestion
2.1.127 199083856 Dry contact alarm - Battery under-voltage 0

Alarm Property
l Description:Dry contact alarm - Battery under-voltage
l Severity:Major
2-82

Chapter 2 Alarm
Probable Cause
Battery under-voltage
System Impact
N/A
Handling Suggestion
2.1.128 199083857 Dry contact alarm - SMR abnormal 0

Alarm Property
l Description:Dry contact alarm - SMR abnormal
l Severity:Major
Probable Cause
SMR(selenium module rectifier) abnormal
System Impact
N/A
Handling Suggestion
2.1.129 199083858 Dry contact alarm - Under-voltage insulate drop

0
Alarm Property
l Description:Dry contact alarm - Under-voltage insulate drop
l Severity:Major
2-83

Probable Cause
Under-voltage insulate drop
System Impact
N/A
Handling Suggestion
2.1.130 199083859 Dry contact alarm - Device suspended 0

Alarm Property
l Description:Dry contact alarm - Device suspended
l Severity:Major
Probable Cause
Device suspended
System Impact
N/A
Handling Suggestion
2.1.131 199083860 User-defined Dry contact alarm 1 0

Alarm Property
l Description:User-defined Dry contact alarm 1
2-84

Chapter 2 Alarm
l Severity:Major
Probable Cause
There is a fault on the User-defined dry contact.
System Impact
N/A
Handling Suggestion

Alarm Property
l Severity:Major
Probable Cause
System Impact
N/A
Handling Suggestion

Alarm Property
2-85


l Severity:Major
Probable Cause
System Impact
N/A
Handling Suggestion

Alarm Property
l Severity:Major
Probable Cause
System Impact
N/A
Handling Suggestion

Alarm Property
2-86

Chapter 2 Alarm
l Severity:Major
Probable Cause
System Impact
N/A
Handling Suggestion

Alarm Property
l Severity:Major
Probable Cause
System Impact
N/A
Handling Suggestion
2-87


Alarm Property
l Severity:Major
Probable Cause
System Impact
N/A
Handling Suggestion

Alarm Property
l Severity:Major
Probable Cause
System Impact
N/A
Handling Suggestion
2-88

Chapter 2 Alarm

Alarm Property
l Severity:Major
Probable Cause
System Impact
N/A
Handling Suggestion

Alarm Property
l Severity:Major
Probable Cause
System Impact
N/A
Handling Suggestion
2-89


Alarm Property
l Severity:Major
Probable Cause
System Impact
N/A
Handling Suggestion
2.1.142 199105025 the rate of abnormal service on SLAVE is high 0

Alarm Property
l Description:the rate of abnormal service on SLAVE is high
l Severity:Minor
Probable Cause
The abnormal rate of service on the SLAVE is high
System Impact
KPI Index of Service in RNC will be low.
Handling Suggestion
Reset the Slave reported in the alarm
2-90

Chapter 2 Alarm
2.1.143 199105029 OMP reboot alarm 0

Alarm Property
l Description:OMP reboot alarm
l Severity:Major
Probable Cause
After OMP board is restarted, it reports this alarm and then the alarm is restored immediately.
Generally, after this alarm is generated, it can only be queried in history alarms.
System Impact
This alarm affects the operation and maintenance during OMP malfunction. It has no effect on
the services.
Handling Suggestion
OMP reports this alarm when being reset and then restores the alarm. No handling operations
are required.
2.1.144 199393987 Board off line 0

Alarm Property
l Description:Board off line
l Severity:Major
Probable Cause
1.The board configured in the database is not online.

2. The board lose contact with the CMM of the same shelf.
System Impact
Related services cannot be provided.
2-91

Handling Suggestion
1. Check for the proper placing of the board, and insert the board firmly if it is not properly placed.
2. Plug/unplug the board.
4. Change the slot.
5. Replace the CMM of the same shelf.
2.1.145 199419840 PTP failed to get clock attribute 0

Alarm Property
l Description:PTP failed to get clock attribute
l Severity:Minor
Probable Cause
PTP failed to get clock attribute
System Impact
PTP doesn't work.
Handling Suggestion
1.Check whether clock board is powered on (indicator RUN is flashing at 1HZ).

Y-> Go to Step "2".
N-> Reset the board to restore the board to normal state, and check whether this alarm disappears:
Y-> End, N-> Go to Step 3.
2.Check the Alarm Management window for the alarm of control plane communication abnormal,
which is 8393985(Control plane communication abnormal between board and its home module).
Y-> Perform the recommended solution to process the alarm, and check whether this alarm
disappears: Y-> End, N-> Go to Step "3".
N-> Go to Step "3".
3.Please contact ZTE.
2-92

Chapter 2 Alarm
2.2 Processing Alarm

2.2.1 199002560 CPU utilization over alarm limit 0
Alarm Property
l Description:CPU utilization over alarm limit
l Severity:Major
l Alarm Type:Processing Alarm
Probable Cause
CPU utilization over alarm limit
System Impact
System runs slowly so some function may be affected
Handling Suggestion
1. Inquire CPU alarm limit from backstage, judge if CPU alarm limit is too low
Y-> Reset the CPU alarm limit, wait dozens of seconds, check if the alarm is eliminated, if alarm is
restored, end, else go to "2".
N-> Go to "2".
2. Do nothing, wait dozens of seconds for the system recover automatically, check if the alarm is
eliminated
Y-> End.
N-> Go to "3".
3. Check if the business is running busily
Y-> Wait until the business finished, check if the alarm is eliminated, if alarm is restored, end, else
go to "4".
N-> Go to "4".
4. Please record the alarm information and contact ZTE Corporation
2.2.2 199004357 The system bureau changed 0

Alarm Property
l Description:The system bureau changed
l Severity:Major
2-93

Probable Cause
The configuration of system bureau changed
System Impact
Need restart system to validate the changed bureau configuration
Handling Suggestion
1. Restart the system, wait 30 seconds, check if the alarm is eliminated

Y-> End.
N-> Please record the alarm information and contact ZTE Corporation
2.2.3 199005400 Configuration conflicts between OMP and CMM 0

Alarm Property
l Description:Configuration conflicts between OMP and CMM
l Severity:Major
Probable Cause
1. The slot is configured to 'OMP'type in CMM, but is not configured to OMP in the database of OMP.
System Impact
OMP can't run normally, so the services in this net element are affected.
Handling Suggestion
1.Change OMP address on CMM board or OMP board, and reboot board.
2.2.4 199005908 Lack of version 0

Alarm Property
l Description:Lack of version
l Severity:Minor
2-94

Chapter 2 Alarm
Probable Cause
Several version not found in version server.
System Impact
Board work with exception
Handling Suggestion
Get log file, and find out lacked version. Then add and active it.
2.2.5 199005909 Download version failed 0

Alarm Property
l Description:Download version failed
l Severity:Minor
Probable Cause
Download version from version server failed.
System Impact
Handling Suggestion
Get log file,and find out download failed version. Then check if file exist in version server.
2.2.6 199005910 Process execute failed 0

Alarm Property
l Description:Process execute failed
l Severity:Minor
2-95

Probable Cause
Several process execute failed.
System Impact
Handling Suggestion
Get log file, and find error code. Then anylize it.
2.2.7 199015362 Fail to process MCS APP Dlib 0

Alarm Property
l Description:Fail to process MCS APP Dlib
l Severity:Critical
Probable Cause
1.fail to open App Dll;

2.fail to excute app init;
3.customized-thread changed
System Impact
reason 1. 2: board poweroff or reboot; reason 3: board reset, then be normal
Handling Suggestion
1. Check whether the reason info is 2

Y-> It is normally restarted for the configuration changed
N-> Go to "2"
2.Check whether the reason is 0
Y-> Check whether the DLL was correctly uploaded, Go to "3"
N-> It may be caused by abnormal upper layer service ,Go to "4"
3. make and upload the correct version
4.Make records of the alarm information and contact ZTE Corporation.
2-96

Chapter 2 Alarm
2.2.8 199018944 PVC link is down 0

Alarm Property
l Description:PVC link is down
l Severity:Minor
Probable Cause
AIS or RDI cell is received, or PVC continuity check is timeout.
System Impact
PVC is in faulty status, all services on the PVC are interrupted.
Handling Suggestion
1. Check alarm details on the NMS fault management interface to find the PVC ID and locate the
faulty port.
For example, the PVC ID is 1. Select PVC Configuration on the NMS Configuration Management
interface to find 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 find the location of the corresponding interface
board and port.
2. If the faulty PVC port is carried by an optical interface, check the optical port and make sure that
the fibber is well connected. Replace the fibber if necessary.
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. Check whether the PVC continuity check is started, If it is started, please deactivate the CC test at
the local end, or activate the CC test at the peer end.
2.2.9 199019207 Near-End IMA Group Configuration Fault 0

Alarm Property
l Description:Near-End IMA Group Configuration Fault
l Severity:Major
2-97

Probable Cause
Since the group parameters configured in near end IMA group does not match with that configured in
far end IMA group and the IMA configuration parameters sent by the remote end through ICP cells
are rejected. The system comes into Config_Aborted status.
System Impact
All services on the IMA port are interrupted.
Handling Suggestion
On NMS fault management interface, view alarm details where information of the faulty IMA group is
given.
On NMS configuration management interface (IMA group configuration), locate the corresponding
IMA group according to the information given in alarm details. Compare the configuration of the
following parameters on both sides. If the configuration on both sides is inconsistent, modify
configuration at either end to keep consistency.The parameters can be modified are as follows:
'Near-End OAM Label'
'Rx Frame Length (cells)'
'Tx Frame Length (cells)'
'Near-End Symmetry'.
2.2.10 199020225 Protocol Stack Requests for Configuration

Information Timeout 0
Alarm Property
l Description: Protocol Stack Requests for Configuration Information Timeout
l Severity:Major
Probable Cause
1. Failed to register on the TCP/IP protocol stack RPU board.

2. Failed to request for database configuration, such as SNTP configuration, DSCP
configuration and UID PPP configuration. Refer to detailed alarm information.
3. Failed to request for interface configuration information, such as Ethernet interface or
ATM interface. Refer to detailed alarm information.
4. Failed to initialize the TCP/IP protocol stack process resource, such as HDLC IC
initialization failure, or memory loss. Refer to detailed alarm information.
2-98

Chapter 2 Alarm
System Impact
Some board functions listed in alarm description are unavailable. When "configuration
request type" in additional alarm information is "media panel IP configuration", the media
panel function will be impacted, other reasons will result in an entire unavailable TCP/IP
protocol stack.
Handling Suggestion
1. Wait for several mins, and check whether the alarm is eliminated.
Y->End
N->2
2. Check whether an alarm ALM-8393985 Communication Exception of
Control panel Between Board and Affiliated Module occurs.
Y->3
N->4
3. Refer to the handling suggestions of ALM-8393985 Communication Exception
of Control panel Between Board and Affiliated Module occurs, and
check whether the alarm is eliminated.
Y->End
N->6
4. Plug this board and reset hardware, and check whether the alarm is eliminated.
Y->End
N->5
5. Replace the faulty board, and check whether the alarm is eliminated.
Y->End
N->6
6. Contact the ZTE office.
2.2.11 199023042 The number of board physical alarms exceeds

the threshold 0
Alarm Property
l Description:The number of board physical alarms exceeds the threshold
l Severity:Major
Probable Cause
There are too many alarms for this board, and the alarm pool is full of board alarms.
2-99

System Impact
Alarm information might be lost. No impact on user service.
Handling Suggestion
Check and delete some temporarily useless virtual configuration resources.
2.2.12 199025600 Connection check be disabled in board 0

Alarm Property
l Description:Connection check be disabled in board
l Severity:Warning
Probable Cause
The connection check switch is off, causing PP service process unable to execute connection check.
System Impact
Board connection check disabled, automatic check of connection error cannot be performed. Thus
the connection error might not be self-cured.
Handling Suggestion
Please input "ppenableconncheck" on the board
2.2.13 199029953 Port is in ethernet OAM loopback state 0

Alarm Property
l Description:Port is in ethernet OAM loopback state
l Severity:Minor
Probable Cause
Local port goes to oam loopback state because remote enable loopback.
2-100

Chapter 2 Alarm
System Impact
System service halt
Handling Suggestion
1.Check remote Oam configuratio ，see if remote enable ethernet oam loopback function,if it is
enable,check loopback test is over. Disable remote’s ethernet oam loopback。Observe if alarm
restore.
Yes->alarm restore
No->phone ZTE corporation
2.2.14 199066006 broadband link congestion 0

Alarm Property
l Description:broadband link congestion
l Severity:Major
Probable Cause
1.Heavy traffic
2.Uneven load among links
3.Poor physical transmission
4.Low links Bandwidth
System Impact
Congestion may cause packet loss, call abortion and even link breakdown.
Handling Suggestion
1.Make no manual intervention and wait for automatic system recovery. Check whether this alarm
disappears after 30 seconds.
Y->End.
N->Go to Step 2.
2.Check whether the system is busy with its current services.
Y->Go to Step 3.
N->Go to Step 4.
3.Check whether there are sufficient link resources.
Y->3.1 Query performance statistic data to check whether the load is evenly shared among links.
Y->Go to Step 1.
N->Go to Step 4.
2-101

N->3.2 Add new links and check whether this alarm disappears.
Y->End.
N->Go to Step 3.1.
5.Perform physical link self-loop on the devices at the both ends of the link, and check whether
this alarm disappears.
Y->Check the bottom layer transmission and ask a transmission engineer to solve the problem.
N->Go to Step 5.
5.Note down detailed information.
5.1 Back up related local office configuration data and peer-end office configuration data.
5.2 Back up related local office and peer-end office history alarms and notifications, as well as
current alarms.
5.3 Contact ZTE Corporation and end the alarm handling procedure.
2.2.15 199066007 broadband link overload 0

Alarm Property
l Description:broadband link overload
l Severity:Major
Probable Cause
1.Heavy traffic
2.Uneven load among links
3.Poor physical transmission
4.Low links Bandwidth
System Impact
Overload may cause packet loss, call abortion and even link breakdown.
Handling Suggestion
Y->End.
N->Go to Step 2.
Y->Go to Step 3.
N->Go to Step 4.
2-102

Chapter 2 Alarm
Y->Go to Step 1.
N->Go to Step 4.
Y->End.
N->Go to Step 3.1.
N->Go to Step 5.
current alarms.
2.2.16 199066013 MTP3 link congestion 0

Alarm Property
l Description:MTP3 link congestion
l Severity:Major
Probable Cause
1.Heavy traffic.
2.Uneven load among links.
3.Insufficient link resources.
System Impact
Congestion may cause packet loss, call abortion and even link breakdown.
Handling Suggestion
Y->End.
N->Go to Step 2.
Y->Go to Step 3.
N->Go to Step 4.
2-103

Y->Go to Step 1.
N->Go to Step 4.
Y->End.
N->Go to Step 3.1.
current alarms.
2.2.17 199066027 Request time from SNTP server failed 0

Alarm Property
l Description:Request time from SNTP server failed
l Severity:Major
Probable Cause
Request time from Sntp server failed
System Impact
Can't synchronize time from SNTP server
Handling Suggestion
1. Check if the configuration of SNTP server is correct

Y-> Go to "2" .
N-> Reset SNTP server's configuration, enforce SNTP time synchronization, check if the alarm is
eliminated, if alarm is restored, end, else go to "2".
2-104

Chapter 2 Alarm
2.2.18 199066031 The number of OMP alarms exceeds the threshold

0
Alarm Property
l Description:The number of OMP alarms exceeds the threshold
l Severity:Major
Probable Cause
There are too many alarms for OMP board, and the alarm pool is full of board alarms.
System Impact
Handling Suggestion
2.2.19 199066032 Time synchronization over alarm limit 0

Alarm Property
l Description:Time synchronization over alarm limit
l Severity:Major
Probable Cause
The minus of time on OMP and time from Sntp server over alarm limit
System Impact
System time may not be correct
2-105

Handling Suggestion
1. Inquire time difference alarm limit from backstage, judge if time difference alarm limit is too low
Y-> Reset the time difference alarm limit, wait dozens of seconds, check if the alarm is eliminated, if
alarm is restored, end, else go to "2".
N-> Go to "2".
2. check time on SNTP server and the system time, judge which time is more accurater
Time on SNTP server-> Enforce SNTP time synchronization from SNTP server, wait dozens of
seconds, check if the alarm is eliminated, if alarm is restored, end, else go to "3".
System time-> Check SNTP server organization, find out the reason of the inaccurate time, if cannot
solve, go to "3".
2.2.20 199066063 MTP3 link sending flow control alarm 0

Alarm Property
l Description:MTP3 link sending flow control alarm
l Severity:Major
Probable Cause
The sending payload of MTP3 link exceeds the threshold set by sending flow control.
System Impact
Packet loss and call abortion.
Handling Suggestion
1.Make no manual intervention and just wait the system to recover. Check whether this alarm
disappears 30 seconds later.
Y->End.
N->Go to "2".
2.Check whether the system has a heavy traffic.
Y->Go to "3".
N->Go to "4".
Y->3.1 Query performance statistic data to check whether load are evenly shared among links.
Y->Go to "1"
N->Go to "4"
2-106

Chapter 2 Alarm
Y->End.
N->Go to "3.1"
current alarms.
2.2.21 199083022 Cell is out of service 1

Alarm Property
l Description:Cell is out of service
l Severity:Critical
Probable Cause
Unknown
System Impact
The cell is unavailable and fails to provide services. Users fail to gain access through this cell.
Handling Suggestion
1.Baseband Resource Pool. Check if the values of Local Cell ID, Receiving Frequency Point, and
Transmitting Frequency Point in"Local Cell Basic Parameters" are consistent with those at RNC side.
If not, modify the RNC or Node B configurations to make them consistent.
2) On NMS fault management interface, check if Node B has generated "199084129 Board reboots
alarm". If yes, it indicates that the Node B has just been started or hardware has been just replaced
or added. In this case, wait for the Node B to finish powering on.
2.Alarm reason: Cell CGID is zero audit by NodeB.
1) Local cell is blocked
On NMS configuration management interface, select the cell to be viewed under Base Station Radio
Resource Management > WCDMA Radio Resource Management >Baseband Resource Pool. View
the Status in Local Cell Status Parameters. If the status is blocked, unblock it.
2) Node B is blocked or faulty
On the ground resource configuration interface, view Node B status. If the status is blocked, unblock
the Node B. If the status is faulty, it indicates that FS board may be faulty. In this case, check if related
alarms exist. If yes, follow the suggestions on handling the related alarms.
The related alarms are as follows:
Application software monitoring alarm
2-107

Board communication link is interrupted.

Board parameter synchronization abnormity
3) Local cell is faulty
View the"Local Cell Status Parameters" interface. If the current status is faulty, it indicates that FS
board or RTR board is faulty or restarted. In this case, check if the following alarms are generated. If
yes, follow the suggestions on handling the related alarms:
Board reboots alarm
4) Baseband board is blocked
View the BPC board status. If the status is blocked, unblock it.
5) Baseband board is faulty
View the BPC board status. If the status is faulty, handle the alarm by referring to the following
suggestions:
Board reboots alarm
3.Alarm reason: Cell is blocked at NodeB side.
Resource Management > WCDMA Radio Resource Management > Baseband Resource Pool. If
the cell status is blocked, unblock it.
4.Alarm reason: System information update fail.
The alarm is caused by the failure to update system messages, that is, system message broadcast
fails. Handle the alarm by referring to the suggestion for "Broadcast fail".
5.For other alarm causes, the system re-establishes the cell automatically. No human intervention
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete:Cell SSCH at RNC side is not consistent with which at Node B side
2-108

Chapter 2 Alarm
System Impact
Handling Suggestion
Board reboots alarm
suggestions:
Board reboots alarm
2-109


is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete:Cell PCPICH at RNC side is not consistent with which at NodeB side
System Impact
Handling Suggestion
2-110

Chapter 2 Alarm

Board reboots alarm
suggestions:
Board reboots alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete:Cell SCPICH at RNC side is not consistent with which at Node B side
System Impact
2-111

Handling Suggestion
Board reboots alarm
suggestions:
Board reboots alarm
2-112

Chapter 2 Alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete:Cell PCCPCH at RNC side is not consistent with which at Node B side
System Impact
Handling Suggestion
2-113

Board reboots alarm
suggestions:
Board reboots alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete:Cell BCH at RNC side is not consistent with which at Node B side
System Impact
2-114

Chapter 2 Alarm
Handling Suggestion
Board reboots alarm
suggestions:
Board reboots alarm
2-115

is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete:RNC allocat user plane board failed
System Impact
Handling Suggestion
2-116

Chapter 2 Alarm
Board reboots alarm
suggestions:
Board reboots alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete:RNC allocat user plane SLAVE failed
System Impact
2-117

Handling Suggestion
Board reboots alarm
suggestions:
Board reboots alarm
2-118

Chapter 2 Alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete:RNC allocat user plane SLAVE timeout
System Impact
Handling Suggestion
2-119

Board reboots alarm
suggestions:
Board reboots alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete:Node B setup cell failed
System Impact
2-120

Chapter 2 Alarm
Handling Suggestion
Board reboots alarm
suggestions:
Board reboots alarm
2-121

is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete:Node B setup cell timeout
System Impact
Handling Suggestion
2-122

Chapter 2 Alarm
Board reboots alarm
suggestions:
Board reboots alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell is out of service at Node B Side
System Impact
2-123

Handling Suggestion
Board reboots alarm
suggestions:
Board reboots alarm
2-124

Chapter 2 Alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete: RNC control plane and user plane handshake timeout
System Impact
Handling Suggestion
2-125

Board reboots alarm
suggestions:
Board reboots alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete:User plane resource transfer to other SLAVE failed
System Impact
2-126

Chapter 2 Alarm
Handling Suggestion
Board reboots alarm
suggestions:
Board reboots alarm
2-127

is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete:User plane resource transfer to other SLAVE timeout
System Impact
Handling Suggestion
2-128

Chapter 2 Alarm
Board reboots alarm
suggestions:
Board reboots alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete: OMCR reset Cell
System Impact
2-129

Handling Suggestion
Board reboots alarm
suggestions:
Board reboots alarm
2-130

Chapter 2 Alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete:RNC release User plane resource SLAVE
System Impact
Handling Suggestion
2-131

Board reboots alarm
suggestions:
Board reboots alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete: OMCR delete cell
System Impact
2-132

Chapter 2 Alarm
Handling Suggestion
Board reboots alarm
suggestions:
Board reboots alarm
2-133

is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete:RNC control plane handshake with CRM fail
System Impact
Handling Suggestion
2-134

Chapter 2 Alarm
Board reboots alarm
suggestions:
Board reboots alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete:system information update fail
System Impact
2-135

Handling Suggestion
Board reboots alarm
suggestions:
Board reboots alarm
2-136

Chapter 2 Alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete:RNC control plane align with database fail
System Impact
Handling Suggestion
2-137

Board reboots alarm
suggestions:
Board reboots alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete:cause by Node B deletion
System Impact
2-138

Chapter 2 Alarm
Handling Suggestion
Board reboots alarm
suggestions:
Board reboots alarm
2-139

is required.

Alarm Property
l Severity:Critical
Probable Cause
NCP link break
System Impact
Handling Suggestion
2-140

Chapter 2 Alarm
Board reboots alarm
suggestions:
Board reboots alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete:cause by board Active/Standby Changeover
System Impact
2-141

Handling Suggestion
Board reboots alarm
suggestions:
Board reboots alarm
2-142

Chapter 2 Alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete:cell in RNC database is deleted
System Impact
Handling Suggestion
2-143

Board reboots alarm
suggestions:
Board reboots alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete:RNC control plane inner cause
System Impact
2-144

Chapter 2 Alarm
Handling Suggestion
Board reboots alarm
suggestions:
Board reboots alarm
2-145

is required.

Alarm Property
l Severity:Critical
Probable Cause
NBAP signal link transmission switched from ATM to IP
System Impact
Handling Suggestion
2-146

Chapter 2 Alarm
Board reboots alarm
suggestions:
Board reboots alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
NBAP signal link transmission switched from IP to ATM.
System Impact
2-147

Handling Suggestion
Board reboots alarm
suggestions:
Board reboots alarm
2-148

Chapter 2 Alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
System Infomation Broadcast Abnormal.
System Impact
Handling Suggestion
2-149

Board reboots alarm
suggestions:
Board reboots alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete: The Bearer type of common transport channel is modified in NMS.
System Impact
2-150

Chapter 2 Alarm
Handling Suggestion
Board reboots alarm
suggestions:
Board reboots alarm
2-151

is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete: The transmission is break between RNC and Node B for a long time.
System Impact
Handling Suggestion
2-152

Chapter 2 Alarm
Board reboots alarm
suggestions:
Board reboots alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete: The Node B which cell is belong to is changed.
System Impact
2-153

Handling Suggestion
Board reboots alarm
suggestions:
Board reboots alarm
2-154

Chapter 2 Alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete: Established cell information is not exist in the audit response message.
System Impact
Handling Suggestion
2-155

Board reboots alarm
suggestions:
Board reboots alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell is blocked at Node B side
System Impact
2-156

Chapter 2 Alarm
Handling Suggestion
Board reboots alarm
suggestions:
Board reboots alarm
2-157

is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete: Cell instance at Idle status fails to send message.
System Impact
Handling Suggestion
2-158

Chapter 2 Alarm
Board reboots alarm
suggestions:
Board reboots alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete: Cell instance at Idle status fails to set timer.
System Impact
2-159

Handling Suggestion
Board reboots alarm
suggestions:
Board reboots alarm
2-160

Chapter 2 Alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete: Cell instance at CCIU-setup status fails to send message.
System Impact
Handling Suggestion
2-161

Board reboots alarm
suggestions:
Board reboots alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete: Cell instance at CCIU-setup status fails to set timer.
System Impact
2-162

Chapter 2 Alarm
Handling Suggestion
Board reboots alarm
suggestions:
Board reboots alarm
2-163

is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete: Cell instance at cell-setup status fails to send message.
System Impact
Handling Suggestion
2-164

Chapter 2 Alarm
Board reboots alarm
suggestions:
Board reboots alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete: Cell instance at cell-setup status fails to set timer.
System Impact
2-165

Handling Suggestion
Board reboots alarm
suggestions:
Board reboots alarm
2-166

Chapter 2 Alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
The cell parameters configured at RNC side is incorrect.
System Impact
Handling Suggestion
2-167

Board reboots alarm
suggestions:
Board reboots alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete: Cell instance at CRM-setup status fail to receive setup response message form CRM
module.
System Impact
2-168

Chapter 2 Alarm
Handling Suggestion
Board reboots alarm
suggestions:
Board reboots alarm
2-169

is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete: Cell Instance at CRM-setup status fails to send message.
System Impact
Handling Suggestion
2-170

Chapter 2 Alarm
Board reboots alarm
suggestions:
Board reboots alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete: Cell Instance at CRM-setup status fails to set timer.
System Impact
2-171

Handling Suggestion
Board reboots alarm
suggestions:
Board reboots alarm
2-172

Chapter 2 Alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete:Local Cell ID configured only at RNC side, not at Node B side
System Impact
Handling Suggestion
2-173

Board reboots alarm
suggestions:
Board reboots alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete: Cell Instance at CRM-setup status fails to write information in DBS.
System Impact
2-174

Chapter 2 Alarm
Handling Suggestion
Board reboots alarm
suggestions:
Board reboots alarm
2-175

is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete: Cell Instance at established status fails to send message.
System Impact
Handling Suggestion
2-176

Chapter 2 Alarm
Board reboots alarm
suggestions:
Board reboots alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete: Instance at established status fails to set timer.
System Impact
2-177

Handling Suggestion
Board reboots alarm
suggestions:
Board reboots alarm
2-178

Chapter 2 Alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete: Cell Instance at established status fails to write info in dbs.
System Impact
Handling Suggestion
2-179

Board reboots alarm
suggestions:
Board reboots alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete: Cell Instance at established status fails to read info from dbs.
System Impact
2-180

Chapter 2 Alarm
Handling Suggestion
Board reboots alarm
suggestions:
Board reboots alarm
2-181

is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete: local cell is blocked at Node B side
System Impact
Handling Suggestion
2-182

Chapter 2 Alarm
Board reboots alarm
suggestions:
Board reboots alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete:Local Cell ID at RNC side is not consistent with which at Node B side
System Impact
2-183

Handling Suggestion
Board reboots alarm
suggestions:
Board reboots alarm
2-184

Chapter 2 Alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete: Cell audit by Node B is not exist at RNC side
System Impact
Handling Suggestion
2-185

Board reboots alarm
suggestions:
Board reboots alarm
is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete: Cell CGID is zero audit by Node B
System Impact
2-186

Chapter 2 Alarm
Handling Suggestion
Board reboots alarm
suggestions:
Board reboots alarm
2-187

is required.

Alarm Property
l Severity:Critical
Probable Cause
Cell delete:Cell PSCH at RNC side is not consistent with which at NodeB side
System Impact
Handling Suggestion
2-188

Chapter 2 Alarm
Board reboots alarm
suggestions:
Board reboots alarm
is required.
2.2.76 199083023 NodeB is out of service 1

Alarm Property
l Description:NodeB is out of service
l Severity:Critical
Probable Cause
Unknown
System Impact
The Node B is unavailable and fails to provide services. Users fail to gain access through this Node B.
2-189

Handling Suggestion
The handling suggestions are classified by transmission mode.

1. IP mode
Check the Alarm Management interface according to the association ID to see if there is any of the
following association-related alarms. If yes, follow the corresponding suggestions to handle it.
199066018 Association congestion
199066019 Association link broken
2.ATM mode
1) Bottom layer transmission fault
Check to see if there is any of the following alarms. If yes, follow the corresponding suggestions to
handle it.
199001792 SDH/SONET fault
199066047 Abnormal status in SDH/SONET
199066048 SDH/SONET: Excessive Error Code
199005639 High Error Rate of Optical Interface
2) Unavailable PVC link
Check to see if the following alarm exists. If yes, follow the corresponding suggestions to handle it.
199018944 PVC Fault

Alarm Property
l Severity:Critical
Probable Cause
NCP link break
System Impact
2-190

Chapter 2 Alarm
Handling Suggestion

1. IP mode
2.ATM mode
handle it.
199018944 PVC Fault

Alarm Property
l Severity:Critical
Probable Cause
ALL CCP link break
System Impact
2-191

Handling Suggestion

1. IP mode
2.ATM mode
handle it.
199018944 PVC Fault
2.2.79 199083054 Incomplete Dbs config alarm 0

Alarm Property
l Description:Incomplete Dbs config alarm
l Severity:Minor
Probable Cause
1.Incomplete local RNC data.

2.Timer of Iu Inteface not config.
3.GPS card info not config.
4.The signal point of adjacent office not config.
System Impact
1.Incomplete local RNC data,the RNC system can't work normal

2.Timer of Iu Inteface not config,KPI Index of Service in RNC will be low.
3.GPS card info not config,the GPS can't work normal.
4.The signal point of adjacent office not config,the adjacent office can't work normal.
2-192

Chapter 2 Alarm
Handling Suggestion
On NMS fault management interface, view Details where Cause of failure is given. Locate the specific
handling suggestion which corresponds to the listed cause.
The handling suggestions that correspond to different causes are described below.
1.cause: incomplete local RNC data.
On NMS configuration management interface, check if “RNC ID”and "PLMN" is configured. If not,
add the configuration.
2.cause: Timer of Iu Inteface not config.
On NMS configuration management interface, check if Iu Timer is configured. If not, add the
configuration.
3.cause: GPS card info not config
On NMS configuration management interface, check if GPS card is configured. If not, add the
configuration.
4.cause: The signal point of adjacent office not config
On NMS configuration management interface, check if signal point of adjacent office is configured. If
not, add the configuration.
2.2.80 199083056 System Information Block overlength Alarm 0

Alarm Property
l Description:System Information Block overlength Alarm
l Severity:Major
Probable Cause
The neighbour cells of the cell is too many.
System Impact
some neighbour cells are not broadcasted by SIB.
Handling Suggestion
Reduce the number of neighbour cells of local cell till the alarm is disappeared
2-193

2.2.81 199392708 Time synchronization over alarm limit in RPU

accesstype 0
Alarm Property
l Description:Time synchronization over alarm limit in RPU accesstype
l Severity:Major
Probable Cause
The minus of time on OMP and time from SNTP server over alarm limit
System Impact
System time may not be correct
Handling Suggestion
1. Inquire time difference alarm limit from backstage, judge if time difference alarm limit is too low
Y-> Reset the time difference alarm limit, wait dozens of seconds, check if the alarm is eliminated, if
alarm is restored, end, else go to "2".
N-> Go to "2".
2. check time on SNTP server and the system time, judge which time is more accurater
Time on SNTP server-> Enforce SNTP time synchronization from SNTP server, wait dozens of
seconds, check if the alarm is eliminated, if alarm is restored, end, else go to "3".
System time-> Check SNTP server organization, find out the reason of the inaccurate time, if cannot
solve, go to "3".
2.2.82 199411651 The number of board logical alarms exceeds the

threshold 0
Alarm Property
l Description:The number of board logical alarms exceeds the threshold
l Severity:Major
2-194

Chapter 2 Alarm
Probable Cause
There are too many alarms for this board, and the alarm pool is full of board alarms.
System Impact
Handling Suggestion
2.3 Communications Alarm

2.3.1 199003841 The control plane retransfer ratio over the
threshold 0
Alarm Property
l Description:The control plane retransfer ratio over the threshold
l Severity:Minor
l Alarm Type:Communications Alarm
Probable Cause
1.There are some badly-touched boards in the system environment and the retransfer-ratio of control
plane increases.
2.The ethernet communication equipment is abnormal on board or switch board.
3.The node address of TIPC conflicts.
System Impact
The message is delayed on control plane between boards.
Handling Suggestion
1. Reset the board.

2. Reset the control plane switch board of the same shelf.
4. Change the slot.
5. Check whether other board run abnormally, if it is abnormal, please resolve fault board due to
fault alarm.
2-195

2.3.2 199005382 Environment monitor board communication is

abnormal 0
Alarm Property
l Description:Environment monitor board communication is abnormal
l Severity:Major
Probable Cause
1. The environment board is not connected to the switch board or the connection is wrong.
2. The environment board locates in a rack. The configured rack number is different from that where
DIP switch of the environment board locates.
System Impact
There is no impact on services. However, the system can not monitor the status of power supply
and environment situation.
Handling Suggestion
1. Reconnect the RS485 cable between the environment monitor board and switch board.
2. Modify the rack number configured for the environment monitor board to consistent with the rack
number switch set for the environment monitor board.
2.3.3 199005396 Packet test of internal media plane is abnormal 0

Alarm Property
l Description:Packet test of internal media plane is abnormal
l Severity:Major
2-196

Chapter 2 Alarm
Probable Cause
1. The internal port chip on the board has a physical fault.

2. The switch chip on media switch board provides a port, which is connected to the board. This
port has a fault.
3. Backplane wiring abnormal, which connects the slot to media switch board.
4. The CPU on the board, or media switch board of the same shelf, is overloaded.
5. Traffic exceeds the processing payload of the board.
System Impact
Media stream can not be transfored normally.
Handling Suggestion
1. Check the alarm management window for the CPU overloaded on the switch board at the shelf, or
local board. Perform recommended solution to process the alarm(s) if any.
2. Check the alarm management window for the alarms of inter-shelf media plane links abnormal.
Perform the recommended solution to process the alarm(s) if any.
4. Change the slot of the board.
5. Replace the switch board in the same shelf.
2.3.4 199005397 Communication of RAW MAC channel is abnormal

0
Alarm Property
l Description:Communication of RAW MAC channel is abnormal
l Severity:Major
Probable Cause
1. The service media stream exceeds the payload.

2. The board hardware is faulty.
System Impact
The channel between media and control plane is abnormal, and it maybe cause the service quality
decline or the service may be wholly interrupted.
2-197

Handling Suggestion
1. Reset the board.

3. Change the slot.
2.3.5 199005406 Sub-unit state is abnormal 0

Alarm Property
l Description:Sub-unit state is abnormal
l Severity:Major
Probable Cause
1.The process which reports sub-unit state is abnormal.

2.The device that is associated with sub-unit is abnormal.
System Impact
Some resource in system is blocked and is unavailable, the services carried by the board are affected.
Handling Suggestion
1. Reset the board.

3. Change the slot.
2.3.6 199019208 Timing of Near-End IMA Group Fault 0

Alarm Property
l Description:Timing of Near-End IMA Group Fault
l Severity:Major
2-198

Chapter 2 Alarm
Probable Cause
Far end IMA group clock mode sent by the far end through ICP cell does not match with the near-end
one. For example, ITC (Independent Transmit Clock) on the far end does not match with CTC
(Common Transmit Clock) on the near end.
System Impact
IMA link may fail to be established.
Handling Suggestion
1.Check if the clock mode on the near end matches with that on the far end.
Y->If it matches, please contact ZTE Corporation.
N->If not, modify the configuration. If the alarm is eliminated, finish the alarm handling. If not, please
contact ZTE Corporation.
2.3.7 199019212 Near-End Transmitting Link Disconnection 0

Alarm Property
l Description:Near-End Transmitting Link Disconnection
l Severity:Major
Probable Cause
When a transmitting link is not connected to the far end IMA group like other links, this alarm appears.
System Impact
IMA link fails to be established.
Handling Suggestion
1.Check if IMA chip works normally and each link can be connected to the far end IMA group normally.
Y->If the chip works normally and each link is connected to the far end IMA group successfully,please
contact ZTE Corporation for help.
N->If not, configure them again. If the alarm is eliminated, finish the alarm handling. If not, please
contact ZTE Corporation.
2-199

2.3.8 199019213 LIF Alarm of Near-End Receiving Link 0

Alarm Property
l Description:LIF Alarm of Near-End Receiving Link
l Severity:Major
Probable Cause
Physical fault or connection error occurs on 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 available upper-layer service access will decrease. Otherwise, all service
will not be interrupted if merely one link is available in the IMA group.
Handling Suggestion
On NMS fault management interface, view alarm Details where information of IMA chip ID, IMA group
ID, IMA link ID, and E1 index are 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 so, refer to
the corresponding alarm handling suggestion.
2.3.9 199019214 LODS Alarm of Near-End Receiving Link 0

Alarm Property
l Description:LODS Alarm of Near-End Receiving Link
l Severity:Major
Probable Cause
1. The input ima clock is abnormal.

2. Transmission quality of the physical link is bad.
2-200

Chapter 2 Alarm
System Impact
Handling Suggestion
1. Check the RUN indicator of clock board. If the indicator is green and flashes slowly, operation of
the clock board must be normal. Otherwise, reset/replace the clock board.
2. On NMS fault management interface, check if clock-related alarm occurs in UIM/GUIM. If yes,
input clock source must be abnormal. Refer to the corresponding alarm handling suggestion.
3. On NMS fault management interface, check if E1-related alarm exists. If yes, refer to the
corresponding alarm handling suggestion.
2.3.10 199019215 RDI Alarm of Far-End Receiving Link 0

Alarm Property
l Description:RDI Alarm of Far-End Receiving Link
l Severity:Major
Probable Cause
1. Far end IMA link is not in active status.

2. Far end IMA link has faults in receiving direction.
System Impact
Handling Suggestion
Check the working status of the relevant far end receiving link by referring to the opposite equipment
operation guide. If far end receiving link is not in active status, please activate the link.
2-201

2.3.11 199019216 Near-End Receiving Link Fault 0

Alarm Property
l Description:Near-End Receiving Link Fault
l Severity:Major
Probable Cause
If a near-end link in receiving direction has faults,this alarm appears on the near end.
System Impact
Handling Suggestion
1.Check if IMA chip works normally and each link can be connected to the near IMA group normally.
Y->If the chip works normally and each link is connected to the near IMA group properly, please
contact ZTE Corporation for help.
N->If IMA chip works abnormally or there is a link which does not belong to near end IMA group,
handle this problem. If the alarm is eliminated, finish the alarm handling. If not, please contact ZTE
Corporation for help.
2.3.12 199019218 Near-End Receiving Link Disconnection 0

Alarm Property
l Description:Near-End Receiving Link Disconnection
l Severity:Major
Probable Cause
When some receiving links can not be connected to the far end IMA group like other links, this
alarm appears.
2-202

Chapter 2 Alarm
System Impact
Handling Suggestion
1.Check receiving link connections on the both sides to see if each receiving link is connected to the
far end IMA group properly and if the anticipant local E1 link is connected to the corresponding E1
link on far end.
Y->If so, please contact ZTE Corporation for help.
N->If not, find the fault causes and handle the problem. If the alarm is eliminated, finish the alarm
handling. If not, please contact ZTE Corporation for help.
2.3.13 199019223 Near-End IMA Group Fault 0

Alarm Property
l Description:Near-End IMA Group Fault
l Severity:Major
Probable Cause
All ima links of this ima group are broken.
System Impact
The IMA Group does not work normally.
Handling Suggestion
1.Check whether the number of active links of an IMA group is smaller than the minimum number of
active links required for the IMA group to work normally.
Y->If so, please check the broken IMA links and make sure that the number of active links is not
smaller than the minimum number required. If alarm is restored, the troubleshooting completes,
otherwise contact ZTE Corporation for help.
N->If not,please contact ZTE Corporation for help.
2-203

2.3.14 199019971 Request gate info timeout 0

Alarm Property
l Description:Request gate info timeout
l Severity:Minor
Probable Cause
Request gate info from scs timeout
System Impact
Can't create L3fwdTbl
Handling Suggestion
Y->End.
N->Contact ZTE Corporation
2.3.15 199025631 LVDS link error 0

Alarm Property
l Description:LVDS link error
l Severity:Major
Probable Cause
1.The NE clock is abnormal.

2.The TDM connection chip is abnormal.
3.The board hardware has faults.
4.The back board hardware has faults.
System Impact
CS domain service might be down.
2-204

Chapter 2 Alarm
Handling Suggestion
1. Check the local board for the Related Alarms. Perform the recommended solution to process
the possible alarms.
Related Alarms:
1286 Loss of clock when input to board
5646 Phase-lock loop unlock
2. Check the clock board for the Related Alarms. Perform the recommended solution to process
Related Alarms:
26133 Output clock lost
26129 Clock reference source lost (Level 1 alarm)
3. Open the Configuration Management window and check whether the EMSI has configured APS
while the active/standby board is configure.
How to check APS protection configuration: open the rack map on the Configuration Management
window, find the EMSI board, right click to pop up shortcut menu, and select Optical port APS
Protection.
5. Replace the slot.
6. Replace the ETAS in the same shelf.
2.3.16 199025871 Communication abnormal between the shelf

management board and switch board in the same shelf 0
Alarm Property
l Description:Communication abnormal between the shelf management board and
switch board in the same shelf
l Severity:Major
Probable Cause
1. The connection is wrong between the shelf management board and switch board in the same shelf.
2. The 485 communication is wrong between switch board and the rack configuration of the
environmental monitoring board.
System Impact
Board operaton might be abnormal.It has no impact to the services.
2-205

Handling Suggestion
1. Check if switch board is in place.

2. Make sure the RS485 cable between the rack configuration of environmental monitor board
and switch board.
2.3.17 199029952 Ethernet link fault alarm 0

Alarm Property
l Description:Ethernet link fault alarm
l Severity:Minor
Probable Cause
A critical event has occurred.An unrecoverable local failure condition has occurred.Local device's
receive pash has detected a fault.
System Impact
Lost of system service
Handling Suggestion
1. Check the fiber Rx if connetivity is good or electric cable is loose。Put out the fiber or cable and
put in it。Observe if the alarm restore.
Yes-> alarm restore
No-> jump“2”\
2. Check peer device’s ethernet OAM function is enable。If it is disable，make peer device enable
ethernet OAM function. Observe if the alarm restore.
Yes->alarm restore
No->jump“3”
3. Replace the cable to peer port on the same device。Insure peer move the other port on the device.
Yes-> alarm restor
No->phone ZTE corporation
2.3.18 199030208 Connectivity fault alarm 0

Alarm Property
2-206

Chapter 2 Alarm
l Description:Connectivity fault alarm
l Severity:Minor
Probable Cause
Connetivty fault management is in fault
System Impact
service may lost partly.
Handling Suggestion
1. Observe the additional information of the alarm.There are five kinds of additional informations.
(1) receive remote rx fault indication signal,jump to "2"
(2) receive server layer's alarm indication signal,jump to "3"
(3) lost continuity from the remote MEP,jump to "4"
(4) recevie incorrect CCM frame,jump to "5"
(5) receive a CCM frame from other MD,jump to "6"
(6) receive server layer's lock signal,jump to "7"
2. Check if remote Mep's(Maintanence end point)"rx is unidirection. Check rx's link state, for
example,rx's fiber is loose.If rx's fiber is loose,then put in it.Sure the devices between localc and
remote mep if good and their port is up.Observer if alarm restore.
Yes->alarm restore,alarm process end.
No->jump to "8"
3. Check the link work state between the server layer's MEP. Sure the port of intermediate devices
is up. If some links of intermediate server layer's devices if fault.Restore the fault links(replace the
cable or put out and put in the port).Observe if the alarm restore.
Yes->alarm restore, alarm process end.
No->jump to "8"
4. Check network path matter between two MEP. Check if link ports of intermediate devices are up. If
intermediate server layer's network have fault link between MEP. Restore fault links(replace cable
or put up and put in port).Check local and remote MEP's bind port's packet statics can increase.
Observe if alarm can restore.
No->jump to "8"
5. Check the whole network plane of Ethernet OAM(IEEE 802.1ag)administration. You inspect the
device's VLAN,MD,MA configuration. Check the remote MEP configuration belong to local MEP.
Check if it has incorrect configuration, CCM send interval is different from local CCM send interval, or
local MEP's MAC is different from remote MAC.Amend it to same. Observe if the alarm can restore.
No->jump to "8"
2-207

6. Check the whole network plane of Ethernet OAM(IEEE 802.1ag)administration. You inspect the
device's VLAN,MD,MA configuration. Check the edge MEPs of the whole MD domain is are full close
in. Check if there are packets from other MD domains. Observe if the alarm can restore.
No->jump to "8"
7. Check the 802.1ag configuration of the server layer's from which our device receive lock
signal.Check if the server layer's MEPs are doing administrator lock. If it is in administrator lock
state,then turn off it.Observe if the alarm restore.
No->jump to "8"
8. We suggest that you adopt expert's advice to eliminate the alarm.
Yes->alarm restore, then phone ZTE to analyse the network.
No->phone ZTE.
2.3.19 199041737 Near-End TC Link Fault 0

Alarm Property
l Description:Near-End TC Link Fault
l Severity:Major
Probable Cause
The physical trunk has faults or input clock is abnormal.
System Impact
Tc link fails to be established.
Handling Suggestion
1. Check if physical trunk has faults. 2. Check if input ima clock work normally.
2.3.20 199066003 Control plane communication abnormal between

board and its home module 0
Alarm Property
2-208

Chapter 2 Alarm
l Description:Control plane communication abnormal between board and its home

module
l Severity:Major
Probable Cause
1. The board is offline.

2. The inserted is different from configuration.
3. The board is abnormal.
4. The control plane communication is abnormal.
5. The board is resetting.
System Impact
The board is blocked so that the services carried by the board are interrupted.
Handling Suggestion
1. Check whether the board is online. If not, insert the board.

2. Check whether the inserted board is the same as the configured board. If not, insert a correct
board.
3. Reset the board. Wait for the board to be powered on.
6. Replace the control plane switch board of the same shelf.
2.3.21 199066005 SCCP subsystem unavailable 0

Alarm Property
l Description:SCCP subsystem unavailable
l Severity:Minor
Probable Cause
1.The remote signaling point subsystem has exit services.

2.The remote signaling point is inaccessible.
3.The remote office has deleted the SSN configuration, and the local end reports alarms.
4.This SSN is not configured in the remote office, but the SSN of the remote office is configured at the
local end, causing SST test failure.
2-209

System Impact
The corresponding subsystem cannot receive or send messages.
Handling Suggestion
1.Check through Alarm Management whether there is any alarm prompting that the adjacent office
is inaccessible.
Y->Perform further handling according to the office inaccessible alarms if there are MTP3 office
inaccessible alarms or M3UA office inaccessible alarms.
N->Go to Step 2.
2.Check the local data configuration to see whether the subsystem is correctly configured in the local
office configuration and adjacent office configuration.
Y->Go to Step 3.
N->Configure the subsystem.
2.1 Check whether this alarm disappears after configuring the subsystem.
Y->End.
N->Go to Step 3.
3.Check the peer-end data configuration to see whether the subsysem is correctly configured in its
local office configuration and adjacent office configuration.
Y->Go to Step 4.
N->Ask the peer end to configure the subsystem.
3.1 Check whether this alarm disappears after the peer end has configured the subsystem.
Y->End.
N->Go to Step 4.
current alarms.
2.3.22 199066010 MTP3 office inaccessible 0

Alarm Property
l Description:MTP3 office inaccessible
l Severity:Major
Probable Cause
1.Office and route configuration error.
2.Link broken.
2-210

Chapter 2 Alarm
System Impact
The corresponding office cannot receive or send messages.
Handling Suggestion
1.Check whether the static route settings of the destination office are correct.
Y->Go to Step 2.
N->Configure or modify the related static route.
1.1 Check whether the office is accessible (this alarm disappears).
Y->End
N->Go to Step 2.
2.Query link status in the route table through Dynamic Management on the background to check
whether there are links available.
Y->Go to Step 4.
N->Go to Step 3.
3.Check alarms on the background to see whether there are alarms prompting that no link is available.
Y->Perform further handling according to the alarms prompting no link available.
N->Go to Step 4.
current alarms.
2.3.23 199066011 MTP3 link unavailable 0

Alarm Property
l Description:MTP3 link unavailable
l Severity:Minor
Probable Cause
1.The link is physically broken.

2.Link test failed.
3.SMP board or the board where the signalling links are configured restarted.
System Impact
This alarm may render some offices inaccessible, or may result in the congestion of other links.
2-211

Handling Suggestion
1.Check whether there is new data configuration or the configuration has been changed.
Y->1.1 Check link configuration data, especially signaling point code (SPC), SLC and network type
(international or domestic) to see whether they accord with the peer end of the link.
Y->Go to Step 2.
N->Modify the configuration and go to Step 1.2.
1.2 Check whether this alarm disappears after modifying the configuration.
Y->End
N->Go to Step 2.
N->Go to Step 2.
2.Check whether there is any alarm for bottom layer transmission if the link configuration has not
been changed.
Y->Ask a transmission engineer to handle the problem.
N->Go to Step 3.
N->Go to Step 4.
current alarms.
2.3.24 199066012 MTP3 cluster inaccessible 0

Alarm Property
l Description:MTP3 cluster inaccessible
l Severity:Major
Probable Cause
1.Incorrect cluster and route configuration.

2.Link broken.
System Impact
The corresponding cluster cannot receive or send messages.
2-212

Chapter 2 Alarm
Handling Suggestion
1.Check whether the static route configuration of the destination cluster is correct.
Y->Go to Step 2 if the static route configuration of the destination cluster is correct.
N->Configure or modify related static route.
1.1 Check whether the cluster is accessible.
Y->End
N->Go to Step 2.
2.Query link status in the route table through Dynamic Management on the background to check
whether there are links available.
Y->Go to Step 4.
N->Go to Step 3.
3.Check alarms on the background to see whether there are alarms prompting no link available.
Y->Perform further handling according to the alarms prompting no link available.
N->Go to Step 4.
current alarms.
2.3.25 199066014 M3UA office inaccessible 0

Alarm Property
l Description:M3UA office inaccessible
l Severity:Major
Probable Cause
1. Association link is broken or application server (AS) is not in serving status.

2. Receive DUNA from peer office.
System Impact
Reception and sending of messages from/to the relevant office fail. Access of new service under this
office fails, and abnormal release of the ongoing service occurs.
2-213

Handling Suggestion
1.Check if there is SIO location records of the corresponding users.

2.After the corresponding SIO location has been configured, check if the corresponding AS is
activated.
3.Deactivate and activate the corresponding association. Check if the alarm is eliminated.
2.3.26 199066019 Broken Association 0

Alarm Property
l Description:Broken Association
l Severity:Major
Probable Cause
1. The association is manually release.

2. All the channels configured by this association are disconnected, or max. resending
times of this association exceeds Association.Max.Retrans.
3. Other association disconnection causes except for the association deletion (See the
additional alarm information)
System Impact
Association interruption, data cannot be transmited, upper layer services will be impacted,
for example, signaling office is unreachable and other available association of an identical office
is blocked.
Handling Suggestion
1. Query association configuration by SHOW SCTP based on association number in

additional information, check whether local/remote port IDs, destination IP, active local
IP are set properly. You should set local association a to local IP a. a. a. a, local port
to Port A, remote IP to b. b. b. b, remote port to Port B, remote association b to local
IP b. b. b. b, local port to Port B, remote IP to a. a. a. a, and remote port to Port A.
Y->3
N->2
2. Modify association by SET SCTP, and check whether the alarm is eliminated.
Y->End
N->3
3. Check whether alarm cause is "receive shutdown request" based on alarm reasons in
additional information.
2-214

Chapter 2 Alarm
Y->4
N->6
4. The association is blocked manually, check whether required to block the association
manually.
Y->End
N->5
5. Activate corresponding association by dynamic management tool, and check whether
Y->End
N->6
2.3.27 199066026 Association Channel Broken 0

Alarm Property
l Description:Association Channel Broken
l Severity:Major
Probable Cause
1. Hardware fault, for example, external interfaces of local/remote devices are broken,
the intermediate switch device is broken, or the transmission channel is interrupted.
2. Bear network communication fault, for example, external interfaces of local/remote
devices are broken, the intermediate switch device is broken or the bear link is
interrupted.
3. Configuration fault, for example, routes or interface addresses of local/remote devices
change.
4. Device fault, for example, NE control panel channels of local or remote device are
interrupted.
System Impact
This channel is unavailable, all channel interruption will result in association interruption.SCTP will
shift transmission to another channel without impact on signaling transmission and service.
2-215

Handling Suggestion
1. Enter the protocol mode by IPSTACK, and check whether the physical link lost lots of
packages by PING and exit this mode by EXIT MODE.
Y->2
N->3
2. Troubleshooting the physical links, and check whether the alarm is eliminated.
Y->End
N->3
3. In the NM alarm management window, check whether the ALM-8393985 Abnormal
Control Plane Communication Between Board and Home ModuleALM-8393988
Abnormal Control Plane Communication Between Module and OMP alarms are
reported on the home module.
Y->5
N->4
4. Handle the fault according to related suggestions, and check whether the alarm is
eliminated.
Y->End
N->5
5. Check whether the remote device of the association is faulty, troubleshoot the remote
faults, and check whether the alarm is eliminated.
Y->End
N->6
2.3.28 199083021 CCP link fault alarm 1

Alarm Property
l Description:CCP link fault alarm
l Severity:Major
Probable Cause
Unknown
System Impact
The CCP transmission link is unavailable. Therefore, the CCP cannot be used during radio link
establishment. If Node B continues to select this CCP, RNC messages cannot reach Node B and the
current service is interrupted.
2-216

Chapter 2 Alarm
Handling Suggestion
Check if the Node B corresponding to the faulty CCP has generated associated alarms. Follow the
suggestions on handling the related alarms. The related alarms are as follows:
1.IP mode
According to the association link number, check if alarms related to association links exist through the
fault management interface. If yes, follow the suggestions on handling the related alarms:
Association congested
Association link broken
2.ATM mode
Check if related alarms exist. If yes, follow the suggestions on handling the related alarms.
SDH/SONET fault
Abnormal status in SDH/SONET
SDH/SONET: Excessive Error Code
High Error Rate of Optical Interface
2) PVC link break
Check if the related alarm exists. If yes, follow the suggestions on handling the related alarm.
The related alarm is as follows:
PVC Fault

Alarm Property
l Severity:Major
Probable Cause
SSCOP link broken
System Impact
2-217

Handling Suggestion
1.IP mode
2.ATM mode
SDH/SONET fault
2) PVC link break
PVC Fault

Alarm Property
l Severity:Major
Probable Cause
PVC link broken
System Impact
2-218

Chapter 2 Alarm
Handling Suggestion
1.IP mode
2.ATM mode
SDH/SONET fault
2) PVC link break
PVC Fault

Alarm Property
l Severity:Major
Probable Cause
SCTP link broken
System Impact
2-219

Handling Suggestion
1.IP mode
2.ATM mode
SDH/SONET fault
2) PVC link break
PVC Fault
2.3.32 199083036 Domain Specific Access Restriction Alarm 0

Alarm Property
l Description:Domain Specific Access Restriction Alarm
l Severity:Minor
Probable Cause
CN domain is unaccessible or overload.
System Impact
The service in the CN domain can not be accessed.
2-220

Chapter 2 Alarm
Handling Suggestion
On NMS fault management interface, view Alarm Details where Alarm Reason is given. Locate the
specific alarm handling suggestion according to the given reason.
The handling suggestions that correspond to different reasons are described below.
1.CN Overload.
1) CN Overload. View CN NMS operation log to see if CN is in overload condition. If yes, no
handling is necessary.
2) Check if transmission-related/board alarm occurs in the board. If yes, refer to the corresponding
alarm handling suggestion.
Related alarms:
199066005 SCCP SSN is invalid
199066010 MTP3 office inaccessible
199066014 M3UA office inaccessible
2.CN unaccessible.
Check if transmission-related/board alarm occurs. If yes, refer to the corresponding alarm handling
suggestion.
Related alarms:
199066005 SCCP SSN is invalid
199066010 MTP3 office inaccessible
199066014 M3UA office inaccessible
2.3.33 199083045 Common Channel setup failed alarm 0

Alarm Property
l Description:Common Channel setup failed alarm
l Severity:Major
Probable Cause
1. Use plane resource initialization fails.

2. Common channel establishment fails on Node B side.
3. CCH transport bearer setup fail.
4. Common channel configuration is deleted in NMS.
5. Inner Procedure Fail.
2-221

System Impact
Common Channel is unavailable, which falls into the following three cases.
1. If the SCCPCH carrying FACH is unavailable, UE-initiated CS/PS services will be down.
2. If the SCCPCH carrying PCH is unavailable, paging function will be unavailable in the system,
leading to failure of UE-initiated CS/PS services.
3. If the PRACH carrying RACH is unavailable, UE access to the cell will fail.
Handling Suggestion
Check the configuration according to the following steps:

1. Check whether DSP run normally.
2. Check whether IUB interface board run normally.
3. On NMS configuration management interface (NE information configuration), select the relevant
Node B. Check the correctness of parameter configuration on path configuration interface. "Peer
service IP address" must be configured in the same network segment with NODEB IP address.
4. On NMS configuration management interface (BS ground resource management), view IP
parameter configuration in IP and route management. Ensure that at least one “COS” is selected.
5. On NMS configuration management interface (NE information configuration), select the relevant
Node B. Check the correctness of parameter configuration on path configuration interface. Check if
forwarding bandwidth is configured.
6.On NMS configuration management interface (path group configuration), view path group
configuration. Check the correctness of parameter
7. Check whether NODEB alarm exist.
8. Contact with ZTE Corporation.
2.3.34 199105021 IP channel of Iub interface is faulty 0

Alarm Property
l Description:IP channel of Iub interface is faulty
l Severity:Minor
Probable Cause
1.IP channel is down.

2.Packet loss rate exceed 25% or Continuous Packet loss num exceed 2.
3.RNC and NODEB configuration is not matching.
System Impact
Service and OMCB will choose other IP channel to transfer data.
2-222

Chapter 2 Alarm
Handling Suggestion
1) Check the transmission quality of intermediate equipment.

2) Check the configuration of IpDomainNo、Omcb Inner Ip、NodeB OMCB gateway between RNC
and NODEB.
2.3.35 199105028 The IP domain is inconsistent in UDP context 0

Alarm Property
l Description:The IP domain is inconsistent in UDP context
l Severity:Minor
Probable Cause
The IP domain configuration of RNC and NodeB is inconsistent in UDP context .
System Impact
It may affect the path selection function in multi-path protection, and also affect the quality of service.
Handling Suggestion
Check and correct the configuration of IP domain in both RNC and NodeB.
2.3.36 199393986 Control plane communication is abnormal

between this board and the active independent board 0
Alarm Property
l Description:Control plane communication is abnormal between this board and the
active independent board
l Severity:Major
2-223

Probable Cause
1.Boards are configured backup mode, but the slave board is offline.
2.The slave board is online, but the communication link between master and slave independent
boards is abnormal.
System Impact
The master board and the slave board can't communicate. When the master board works abnormally,
change over won't happen. It has no impact to the services.
Handling Suggestion
1. Make sure the board is configured backup mode, and the master and slave boards are firmly online.
2. Check the opposite board for the related alarms. If there are related alarms, perform the
recommended solution to process the possible alarms.
3. Replace the opposite board.
4. Change the slots of both the master and slave boards.
2.3.37 199393988 Control plane communication abnormal between

MP and OMP 0
Alarm Property
l Description:Control plane communication abnormal between MP and OMP
l Severity:Major
Probable Cause
1. The board is not online.

2. The board is blocked.
3. The inserted board is different from the configured.
5. The control plane communication is abnormal.
6. The board is resetting.
7. The module has been powered off, and the service on this board will be failed or switch over
other module.
System Impact
The board is blocked so that it can not provide functions. Furthermore, all services under the relevant
module become unavailable.
2-224

Chapter 2 Alarm
Handling Suggestion
1. Check whether the board is online. If not, insert the board.

2. Check whether the inserted board is the same as the configured board. If not, insert a correct
board.
3. Reset the board and wait power on.
6. Replace the control plane switch board of the same shelf.
2.3.38 199407043 PPP Link Broken 0

Alarm Property
l Description:PPP Link Broken
l Severity:Major
Probable Cause
1. EPU Create HDLC channel failed.

2. Physical link is broken, or the transmission quality of link is poor.
3. PPP port is creating or modifying by user.
4. Master board power on, or slave board became to master.
5. Users modify its' parameter of PPP link or peer's.
6. The other side of link is re-negotiation.
7. Two sides of link is inconsistent
System Impact
This will cause disconnection of user plane data and services.
Handling Suggestion
1Is there a alarminfo called "18501 EPU create HDLC channel failed"
Y->go to "2"
N->go to "7"
2.Observe the alarm information for a few minutes, check whether the alarm will be restored.
Y->alarm can be restored, end(link broken reason may be 2,3,4,5,6)
N->go to "3"
3.Check cable connection at both ends. If the cable is disconnected or connection is loose
Y-> unplug and plug the cable or replace the cable,if the alarm is restored after operation,end(link
broken reason:2) ,otherwise, go to "4".
2-225

N->go to "4"
4.Refer to user's networking plan to see if E1 cable connection is correct
Y-> connection refer to user's networking.if the alarm is restored after operation,end(link broken
reason:2) ,otherwise, go to "5".
N->go to "5"
5.On NMS configuration management interface (IPOverE1 configuration), check whether Interface E1
No. and time slot configuration of two sides is accord
Y-> modify congiguration,Ensure that the relevant configuration is consistent at both ends.if the alarm
is restored after operation,end(link broken reason:7) ,otherwise, go to "6".
N->go to "6"
6.On NMS configuration management interface, check whether configuration of relay board and
interface board connection is accord.
Y-> modify congiguration,Ensure the connection continuity of PPP port at both ends.if the alarm is
restored after operation,end(link broken reason:7) ,otherwise, go to "10".
N->go to "10"
7.Check if EPU board property is T1.
Y->go to "8"
N->go to "9"
8.Check if the timeslot of port is excess No.24
Y->modify the configuration,make sure timeslot is not overrun No.24,end(link broken reason:1)
,otherwise, go to "9".
N->go to "9"
9.Check if the E1 Num is excess max num.
Y->modify the E1 num,,end(link broken reason:1) ,otherwise, go to "10".
N->go to "10"
10.Contact ZTE corporation,use expert advice
2.3.39 199411392 BFD Session Interruption 0

Alarm Property
l Description:BFD Session Interruption
l Severity:Minor
2-226

Chapter 2 Alarm
Probable Cause
1. The physical link of the BFD link is faulty.

2. The physical link of the BFD link is faulty.
3. The physical link of the BFD link loses packages or is blocked.
4. The opposite BFD session is removed.
5. The software of the BFD session is faulty.
6. Related BFD configuration is modified.
System Impact
BFD is used to test the accessibility to the opposite device and link quality. BFD interruption means
the link to the opposite device is disconnected, and all static routes which treat this opposite device
as the new-hop path will be disconnected or switched. If there is a standby path, then the system
will change over to this path, if not, the services are unavailable.
Handling Suggestion
1. Abundant data caused by the burst traffic or some configurations will result in BFD
disconnection in a flash, observe this alarm information for a while, and check whether
Y->End
N->2
2. Check the indicators of the BFD session source address interface and destination
interface are on normally.
Y->4
N->3
3. Replace the network cables, or re-insert the link cables of the BFD session, wait for
30 secs, re-check the indicators of the BFD session source address interface and
destination interface, and check whether the alarm is eliminated.
Y->End
N->4
4. Enter the protocol mode by IPSTACK, and check network connection between BFD
source address and destination address by PING and exit this mode by EXIT MODE.
Y->6
N->5
5. Troubleshoot the network connection and check whether the alarm is eliminated.
Y->End
N->6
2-227

2.3.40 199411393 BFD Session Negotiation Failure 0

Alarm Property
l Description:BFD Session Negotiation Failure
l Severity:Minor
Probable Cause
1. You have not configured BFD session on the opposite end.

2. Related BFD configurations are inaccurate.
3. The physical link of the BFD session is faulty.
4. The device interface of the BFD is faulty.
5. The physical link of the BFD link loses packages or is blocked.
6. The software of the BFD session is faulty.
System Impact
All services on the path related to the BFD session will be switched to the slave path. Service
interruption will occur if slave path does not exist.
Handling Suggestion
1. Time different of both parties may result in unsuccessful BFD negotiation, observe
alarm information for a while, and check whether the alarm is eliminated.
Y->End
N->2
2. Check the indicators of the BFD session source address interface and destination
interface are on normally.
Y->4
N->3
3. Replace the network cables, or re-insert the link cables of the BFD session, wait for
30 secs, re-check the indicators of the BFD session source address interface and
Y->End
N->4
4. Enter the protocol mode by IPSTACK, and check network connection between BFD
Y->6
N->5
Y->End
N->6
2-228

Chapter 2 Alarm
6. Contact ZTE Corporation.
2.3.41 199419073 Bearer network is unavailable 0

Alarm Property
l Description:Bearer network is unavailable
l Severity:Major
Probable Cause
1. The intermediate device drop packets which possibly causes the bearer network to be unavailable.
2. Some section of both sides environment's drop packets which also possibly cause the bearer
network to be unavailable.
System Impact
Seriously affect the service on the bearer network
Handling Suggestion
1 Ping the address each other to sure if the link is break or loss packet badly
Y - >Goto 2.1
N - > please contact zte, End the alarm handling.
2 Use the PD trace function to detect through the Web Master:
2.1 Check the every part coording to each nexthop
2.1.1 the link between mp and interface board is broken,Goto 2.2
2.1.2 the link between interface board and intermediate equipment is broken, Goto 2.4
2.1.3 the link between intermediate equipment and other intermediate equipmentis broken, Goto 2.4
2.2 check to see if the routing configuration with wrong
Y - > Check to see if the route configuration is wrong
Y - > Change route configuration ,Goto 2.1.1
N - > Goto 2.3
2.2.1 This part is ok?
Y - > make sure the alarm is eliminated or not,goto 2.2.2
N - > Goto 2.3
2.2.2 Check if the alarm is eliminated
Y - > End the alarm handling.
N - > Goto 2.3
2.3 Check The port of interface board is down or not
Y - > Replace the cable,Goto 2.3.1
2-229

2.3.1 Check port of interface board again

Y - > Check if the alarm is eliminated ,goto 2.3.2
N - > Goto 2.4
2.4 Check intermediate equipment, such as eht configuration of switch to find if it has errors
Y - > Change configuration, Goto 2.4.1
N - > Goto 2.4.2
N - > Goto 2.4.2
2.4.2 Replace the intermediate equipment,goto 2.4.3
N - > Please contact zte
2.3.42 199419074 Bearer network get worse 0

Alarm Property
l Description:Bearer network get worse
l Severity:Minor
Probable Cause
1. The intermediate device drop packets which possibly causes the bearer network worst.
2. Some section of both sides environment's drop packets which also possibly cause the bearer
network worst.
System Impact
Possible to affect the service on the bearer network.
2-230

Chapter 2 Alarm
Handling Suggestion
1 Ping the address each other to sure if the link is break or loss packet badly
Y - >Goto 2.1
2 Use the PD trace function to detect through the Web Master:
2.1 Check the every part coording to each nexthop
2.1.1 the link between mp and interface board is broken,Goto 2.2
2.1.2 the link between interface board and intermediate equipment is broken, Goto 2.4
2.1.3 the link between intermediate equipment and other intermediate equipmentis broken, Goto 2.4
2.2 check to see if the routing configuration with wrong
Y - > Check to see if the route configuration is wrong
Y - > Change route configuration ,Goto 2.1.1
N - > Goto 2.3
N - > Goto 2.3
N - > Goto 2.3
2.3 Check The port of interface board is down or not
Y - > Replace the cable,Goto 2.3.1
2.3.1 Check port of interface board again
Y - > Check if the alarm is eliminated ,goto 2.3.2
N - > Goto 2.4
2.4 Check intermediate equipment, such as eht configuration of switch to find if it has errors
Y - > Change configuration, Goto 2.4.1
N - > Goto 2.4.2
N - > Goto 2.4.2
2.4.2 Replace the intermediate equipment,goto 2.4.3
N - > Please contact zte
2-231

2.3.43 199420352 IPD Session Interruption 0

Alarm Property
l Description:IPD Session Interruption
l Severity:Minor
Probable Cause
1. The physical link of the IPD link is faulty.

2. The device interface link of the IPD link is faulty.
3. The link of the IPD session is blocked or losing packages.
4. The software of the IPD session is faulty.
5. Related configuration of the IPD session is modified.
System Impact
IPD is used to test the accessibility to the opposite device and link quality. IPD interruption means
the link to the opposite device is disconnected, and all static routes which treat this opposite device
as the new-hop path will be disconnected or switched. If there is a standby path, then the system
will change over to this path, if not, the services are unavailable.
Handling Suggestion
1. Abundant data caused by the burst traffic or some configurations will result in IPD
disconnection in a flash, observe this alarm information for a period of time, and check whether
Y->End
N->2
2. Check the indicators of the IPD session source address interface and destination
interface are normal.
Y->4
N->3
3. Replace the network cables, or re-insert the link cables of the IPD session, wait for
30 seconds, re-check the indicators of the IPD session source address interface and
Y->End
N->4
4. Enter the protocol mode by IPSTACK, and check network connection between IPD
Y->6
N->5
2-232

Chapter 2 Alarm
Y->End
N->6
2.3.44 199429568 broadband link unavailable 0

Alarm Property
l Description:broadband link unavailable
l Severity:Minor
Probable Cause
1.physical transmission broken

2.Receiving end pdu from the peer
3.Receiving error pdu from the peer or too many error pdu etc.
System Impact
This alarm may render some offices inaccessible, or may result in the congestion of other links.
Handling Suggestion
1.Check whether there is new data configuration or the configuration has been changed.
Y->1.1 Check link configuration data, especially the link's vpi,vci and the port to see whether they
accord with the peer end of the link.
Y->Go to Step 2.
N->Modify the configuration and go to Step 1.2.
1.2 Check whether this alarm disappears after modifying the configuration.
Y->End
N->Go to Step 2.
N->Go to Step 2.
2.Check whether there is any alarm for bottom layer transmission if the link configuration has not
been changed.
Y->Ask a transmission engineer to handle the problem.
N->Go to Step 3.
N->Go to Step 4.
2-233

current alarms.
2.4 Environment Alarm

2.4.1 199030749 Difference between ambient and outlet sensor
exceeded limit . 0
Alarm Property
l Description:Difference between ambient and outlet sensor exceeded limit .
l Severity:Minor
l Alarm Type:Environmental Alarm
Probable Cause
Shelf envirotment temperature changed;Fantray may be abnormal.
System Impact
A hidden danger occurs.
Handling Suggestion
check shelf condition; check fantrays.
2.5 Qos Alarm

2.5.1 199066018 Association congested 0
Alarm Property
l Description:Association congested
l Severity:Minor
l Alarm Type:Qos Alarm
2-234

Chapter 2 Alarm
Probable Cause
1.Heavy traffic
2.Uneven load among associations
3.Insufficient association resources
System Impact
Transmission delay, or even packet loss will occur. If congestion is not serious, service will not be
affected. Otherwise, call loss might occur, and access success rate of PS service might fall.
Handling Suggestion
1. Check network cable connection. Ensure that the network cable is tightly inserted.
2. Add association links to the office 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.
2.5.2 199105022 IU PS traffic over load alarm 0

Alarm Property
l Description:IU PS traffic over load alarm
l Severity:Minor
Probable Cause
IU PS traffic throughput exceed the threshold of license control.
System Impact
The traffic over the license threshold would cause packet loss and service quality decrease.
Handling Suggestion
Check if the whole thpoughput is over the provider's guaranteed bandwidth limit authorized by license.
2.5.3 199105023 IU CS traffic over load alarm 0

Alarm Property
2-235

l Description:IU CS traffic over load alarm
l Severity:Minor
Probable Cause
IU CS traffic throughput exceed the threshold of license control.
System Impact
The traffic over the license threshold would cause user service access reject.
Handling Suggestion
2.5.4 199105024 IU traffic over load alarm 0

Alarm Property
l Description:IU traffic over load alarm
l Severity:Minor
Probable Cause
IU CS and PS traffic throughput exceed the threshold of license control.
System Impact
The traffic over the license threshold would cause CS user service access reject or PS service
quality decrease.
Handling Suggestion
2-236

Chapter 3
Notification
Table of Contents
199000576 Trunk slip 0 ..............................................................................................3-4
199000834 MCC is abnormal 0 ..................................................................................3-5
199001600 CPU resets on a board in the same shelf 0 ..............................................3-6
199004417 Exception information 0 ...........................................................................3-6
199004418 Logic cpu is power on successfully 0 .......................................................3-7
199004419 Logic cpu is power on failed 0 ..................................................................3-7
199005189 Board change over notice 0 .....................................................................3-8
199005448 Environment parameters set fail 0............................................................3-8
199005715 PP2S source has switched 0 ...................................................................3-9
199005718 Two master clock ports is directly connected 0.........................................3-9
199005720 The CDM data was covered 0................................................................3-10
199005762 The board is selecting clock base 0 .......................................................3-11
199005763 There is no valid reference of the clock board to be selected. 0 .............3-11
199005764 Lock timeout when manual selecting clock reference 0 ..........................3-12
199005765 Lock the wrong base when manual selecting clock reference 0..............3-12
199005766 Lock the right base when manual selecting clock reference 0 ................3-13
199005767 The manual selecting reference command is unuseful because the
clock board is in preheat status. 0 ............................................................................3-13
199005956 Board version error. 0 ............................................................................3-14
199005958 IDE version file synchronization information 0 ........................................3-14
199005976 Download version failed 0 ......................................................................3-15
199005977 Running version not match with database configuration 0 ......................3-16
199005978 Boottype different with configure 0 .........................................................3-16
199005979 Execute version file failed 0 ...................................................................3-17
199005980 Match version failed 0 ............................................................................3-17
199005981 NCPU version load information 0 ...........................................................3-18
199005982 Patch operation failed 0 .........................................................................3-18
199005983 Write back version information 0 ............................................................3-19
199005984 Check version information 0...................................................................3-19
199005985 Synchronize version information 0 .........................................................3-20
199006017 The Sunit resets by MML command . 0..................................................3-20
199006018 block The Sunit 0 ...................................................................................3-21
199006720 Notice of power-on status of C51 board/ Board soft reset 0....................3-21
199008000 Load Data Fail 0 ....................................................................................3-22
199008007 Save database failed 0 ..........................................................................3-22
199008512 Msater-Slave Fail 0 ................................................................................3-23
199008769 Data Sync Between Boards Fail 0..........................................................3-23
3-1

199008770 Data Sync Loading Fail 0 .......................................................................3-24

199008771 Sync by Ftp Fail 0 ..................................................................................3-24
199009024 Notify Fail 0............................................................................................3-25
199010048 Mem Fail 0.............................................................................................3-25
199010049 DLL Register Fail 0 ................................................................................3-26
199010050 Get Lock Timeout 0................................................................................3-26
199010051 Transaction Timeout 0 ...........................................................................3-27
199010304 SCCP GT translation failure 0 ................................................................3-27
199010305 NID not configured 0 ..............................................................................3-28
199010306 NID translation failure 0 .........................................................................3-28
199010307 ISNI constrained route information repetition 0.......................................3-29
199010308 ISNI does not support this route function 0.............................................3-30
199010309 NID route prompt failure 0......................................................................3-30
199010310 Wrong message type use ISNI function 0 ..............................................3-31
199011840 M3UA user office status change 0..........................................................3-31
199012096 failed for sig process get the info of config 0...........................................3-32
199012097 The file of sig config updated 0 ..............................................................3-32
199012352 failed for sig process get memory resource 0 .........................................3-33
199013888 ASP status changed 0 ...........................................................................3-33
199013889 AS status changed 0..............................................................................3-34
199013890 Sigtran error message received 0 ..........................................................3-35
199013891 Sigtran notification message received 0 .................................................3-35
199014144 Association Establishment Failure 0.......................................................3-36
199014145 Association restart 0 ..............................................................................3-37
199014146 Dynamic Association link broken 0.........................................................3-37
199014148 One user of share association is in service 0 .........................................3-38
199014149 One user of share association is out of service 0 ...................................3-38
199014150 Association config error 0.......................................................................3-39
199014151 SSM malloc memory failure 0 ................................................................3-39
199014152 Dynamic association config error 0 ........................................................3-40
199017472 Data configuration abnormal 0 ...............................................................3-40
199017473 Configuration file abnormal 0 .................................................................3-41
199017728 Database access abnormal 0.................................................................3-41
199017990 RPU detected board down 0 ..................................................................3-42
199018240 TCP Receiving RST Packet 0 ................................................................3-42
199018241 TCP Connection Disconnected 0 ...........................................................3-43
199018242 MD5 Verification Failure 0 ......................................................................3-44
199018243 MD5 Message Error 0............................................................................3-45
199018244 SOCKET received queue over threshold value 0 ...................................3-46
199018245 SOCKET abnormally closed 0................................................................3-46
199018500 The peer IP address configuration and the local IP address
configuration of PPP link is the same 0.....................................................................3-47
199018501 The HDLC channel of EPU created fail 0 ...............................................3-47
199018504 The HDLC channel created unsuccessfully before is created
successfully now. 0 ..................................................................................................3-48
3-2

Chapter 3 Notification
199018755 HDLC status changed 0 .........................................................................3-49

199019008 Fail to config the ATM port 0 ..................................................................3-50
199019264 IMA Group Related Operations Failure 0 ...............................................3-50
199019265 IMA Link Operations Failure 0................................................................3-51
199019777 APS switchover happens 0 ....................................................................3-52
199020290 Failed to Power on Protocol Stack 0 ......................................................3-52
199020554 Add IP route failed 0 ..............................................................................3-53
199020802 Conflicting IP addresses 0 .....................................................................3-54
199020803 Conflicting MAC Addresses in Subnet 0.................................................3-54
199021059 RIP Neighbor Configuration Error 0........................................................3-55
199021060 RIP Interface Authentication Error 0.......................................................3-56
199021065 Incompatible RIP Version Number 0 ......................................................3-56
199021329 LSDB overflow 0 ....................................................................................3-57
199021330 Configuration of OSPF mismatched 0 ....................................................3-58
199021573 BGP Gets TCB Fail on Active Connection 0...........................................3-58
199021584 Neighbor Hold Timer Expired 0 ..............................................................3-59
199021585 BGP Interface down and Neighbor Link Broken 0 ..................................3-59
199021837 Failure in adding dynamic routings 0......................................................3-60
199022336 Intra-Office Port MAC Conflict 0 .............................................................3-61
199022593 ISIS Hello Message Authentication Failure 0..........................................3-62
199022594 ISIS LSP Message Authentication Failure 0 ...........................................3-62
199022595 ISIS SNP Message Authentication Failure 0 ..........................................3-63
199022597 Abnormal Message is Received 0 ..........................................................3-64
199022598 Routers with Conflicting System Id Exist in Network 0............................3-65
199025620 Top resource insufficient 0 .....................................................................3-65
199026176 The currently locked reference of the clock board has been changed 0 .3-66
199026178 Clock work mode is changed 0 ..............................................................3-66
199028231 Router ID not configured for OSPFv3 0..................................................3-67
199028233 Configuration of OSPFv3 Mismatched 0 ................................................3-67
199028993 SCTP Primary Path Set Failed 0............................................................3-68
199028994 SCTP Change Nexthop 0.......................................................................3-68
199028998 SCTP abnormally congested 0...............................................................3-69
199028999 Module Asso Num Exceed 0 ..................................................................3-70
199029000 SCTP receive queue over threshold value 0 ..........................................3-70
199029760 DNS server inaccessible 0 .....................................................................3-71
199030016 Ethernet link OAM event 0 .....................................................................3-71
199030528 The result of configured PD task start 0 .................................................3-72
199030787 ATCA Fru Power On 0 ...........................................................................3-73
199030790 ATCA Fru Power Off 0 ...........................................................................3-73
199030794 ATCA Fru Communication Lost 0 ...........................................................3-74
199030800 ATCA Fru Communication Regain 0 ......................................................3-74
199030815 HOST CPU RESET EVENT 0................................................................3-75
199030817 BIOS Start-up Inform 0 ..........................................................................3-75
199030820 BIOS Memory Inform 0 ..........................................................................3-76
199030821 Power On Failed Inform 0 ......................................................................3-76
3-3

199030828 ATCA FRU present 0 .............................................................................3-77

199030829 ATCA FRU absent 0 ..............................................................................3-77
199031296 PTP failed to cancel slave port 0............................................................3-78
199031554 IP address of DHCP server alloc to client is conflict 0 ............................3-78
199041473 Fail to config the ATM pvc 0 ...................................................................3-79
199041794 TC Link Operations Failure 0 .................................................................3-80
199070002 Iu interface global reset notification 0 .....................................................3-80
199070003 Iu interface resource reset notification 0.................................................3-81
199070004 RNC started Iu interface global reset failure notification 0 ......................3-82
199070005 RNC started Iu interface resource reset failure notification 0 ..................3-82
199070008 RNC and Node B CCPID configuration are not identical 0......................3-83
199070009 Broadcast fail 0 ......................................................................................3-83
199083025 Common Channel is abnormal 0............................................................3-85
199083037 All Local Cell ID configured at RNC side are differ from which on Node
B side 0 ....................................................................................................................3-86
199083057 Excluded Neighbour Cells In SysInfoBlock Notification 0 .......................3-86
199105001 Failed to get the table of configuration 0.................................................3-87
199105002 The route table is overloaded 0..............................................................3-88
199105003 Failed to handle DHCP message from other network 0 ..........................3-89
199105004 Failed to operate multicast group 0 ........................................................3-90
199105005 Clock difference of slave is large 0.........................................................3-90
199105006 Slave losted external clock 0..................................................................3-91
199105007 TCP connection on IuBC interface establish failure 0 .............................3-91
199105008 Bandwidth automatic adjustment is useless 0 ........................................3-92
199105009 No acknowledge of SLA query request 0 ...............................................3-93
199105018 Unable to save Performance File 0 ........................................................3-93
199105019 SLAVE memory check fail notification 0 .................................................3-94
199105020 TCP connect on IuBC interface is interrupted 0......................................3-95
199105030 OMP received data is not complete 0.....................................................3-95
199105031 Transport path bandwidth modified from far end 0 .................................3-96
199105032 Transport Path Occupied BandWidth Overload 0 ...................................3-96
199105033 Transport Path group Occupied Bandwidth Overload 0 ..........................3-97
3.1 199000576 Trunk slip 0

Notification Property
l Notification Code:199000576
l Notification Sub-code:0
l Description:Trunk slip
l Severity:Minor
3-4

Probable Cause
Since frequency difference might exist between trunk line clock and local receive clock, the trunk
receive clock is not synchronous with the transmit clock.
System Impact
Momentary fault occurs to trunk data service or signaling channel. If fault occurs repeatedly, CS/PS
service might become unstable. Otherwise, service is not affected.
Handling Suggestion
Check the clock synchronization status at both sides. If the status is unsynchronized, check if
LOL-related (loss of lock) alarm occurs in clock board. If yes, refer to the corresponding alarm
handling suggestion.
Related alarms:
3.2 199000834 MCC is abnormal 0

l Description:MCC is abnormal
l Severity:Major
Probable Cause
MCC Hardware Fault.
System Impact
All MCC channels cannot transmit or receive data.
Handling Suggestion
Pull out the board for 5 seconds and insert it again after a full discharge. If the problem can still
not be solved, please contact ZTE Corporation.
3-5

3.3 199001600 CPU resets on a board in the same shelf

0
l Description:CPU resets on a board in the same shelf
l Severity:Major
Probable Cause
The board becomes err or resets by manual command.
System Impact
The board can not work normaly.
Handling Suggestion
1. Whether the board resets by manual command.

Y: Belongs to normal alarm inform.
N: Go to "2".
2. The board has other alarms, fix them first.
Y: Then check if this alarm is clear, if not, contact to ZTE .
N: Contact to ZTE
3.4 199004417 Exception information 0

l Description:Exception information
l Severity:Major
Probable Cause
Deadlock,deadloop or exception of system happened
System Impact
System work abnormally
3-6

Handling Suggestion
Please get exception record file and contact ZTE Corporation
3.5 199004418 Logic cpu is power on successfully 0

l Description:Logic cpu is power on successfully
l Severity:Major
Probable Cause
Logic cpu power on success
System Impact
None
Handling Suggestion
Report of normal state, nothing need to do.
3.6 199004419 Logic cpu is power on failed 0

l Description:Logic cpu is power on failed
l Severity:Major
Probable Cause
Logic cpu power on fail
System Impact
Powering failed
3-7

Handling Suggestion
1.Check whether the OMP board is working normally.

Y-> Go to Step 2
N-> Power on the OMP board successfully first: Y-> Go to Step 2, N-> Contact ZTE.
2.Check whether the communitcation between this logic Cpu and OMP is in order.
Y-> Go to Step 3.
N-> Check whether the related switch board is working normally:Y->Go to Step 3,N->Contact ZTE.
3.Record the abnormal process of this logic Cpu and contact ZTE.
3.7 199005189 Board change over notice 0

l Description:Board change over notice
l Severity:Minor
Probable Cause
It is hardware system fault or the board changes over due to artificial operation.
System Impact
The board whose change over failed will reset automatically.
Handling Suggestion
1. Analyze the change over reason according to the additional information about the alarm. If it is
not because of the system fault but due to control of MML command at the background or caused
by non-active/standby change over, or the standby board does not exist physically, nothing would
be done for this alarm.
2. If it is because of the system fault, eliminate those alarms firstly.
3.8 199005448 Environment parameters set fail 0

l Description:Environment parameters set fail
l Severity:Minor
3-8

Probable Cause
1. Environment monitor board communication is abnormal.

System Impact
The configured environment parameters fail to take effect. There is no impact on services.
Handling Suggestion
1. Unplug and plug the 485 cable.

2. Replace the 485 cable.
3.9 199005715 PP2S source has switched 0

l Description:PP2S source has switched
l Severity:Minor
Probable Cause
PP2S (Pulse Per 2 Seconds) source has switched within system clock, GPS receiver sides and
1588 synchronize clock.
System Impact
The broadcast time is triggered by GPS-side PP2S, system-side PP2S or 1588-side PP2S.
Handling Suggestion
No need to handle.
3.10 199005718 Two master clock ports is directly

connected 0
3-9

l Description:Two master clock ports is directly connected

l Severity:Minor
Probable Cause
The port is configured as a master clock port in synchronous Ethernet, two master clock ports
is directly connected.
System Impact
If it is normal, then there is no impact; if it is network connecting mistake, then the port can not
synchronize to the connected master clock port.
Handling Suggestion
If users do not want the other side to recover clock from this SyncE port, it is normal.
otherwise, it maybe has a mistake on network
connecting. If it is normal, there is no need to handle; if it is network connecting mistake,there is need
to reconfigure the clock port or reconnect the port.
3.11 199005720 The CDM data was covered 0

l Description:The CDM data was covered
l Severity:Major
Probable Cause
The CDM information dismatched between left and right.
System Impact
None
Handling Suggestion
No need to handle.
3-10

3.12 199005762 The board is selecting clock base 0

l Description:The board is selecting clock base
l Severity:Minor
Probable Cause
When base is manually selected, if the previous base selection is still in process and operation result
is not yet to be given, the present manual base selection is shut down and this notification is declared.
System Impact
None
Handling Suggestion
Don't select base until last action result is given.
3.13 199005763 There is no valid reference of the clock

board to be selected. 0
l Description:There is no valid reference of the clock board to be selected.
l Severity:Minor
Probable Cause
There is no valid reference of the clock board to be selected, because all references are invalid
or are not configured.
System Impact
System could not get the needed clock, which will cause processing abnormity related to the clock.
Handling Suggestion
Select clock reference again after the base valid or configured.
3-11

3.14 199005764 Lock timeout when manual selecting

clock reference 0
l Description:Lock timeout when manual selecting clock reference
l Severity:Minor
Probable Cause
The selected reference is valid, but the phase-lock loop can not be lock status in a long time.
System Impact
Handling Suggestion
Execute the manual selecting clock reference command again.
3.15 199005765 Lock the wrong base when manual

selecting clock reference 0
l Description:Lock the wrong base when manual selecting clock reference
l Severity:Minor
Probable Cause
The clock board locks the other reference but not the selected reference.
System Impact
Handling Suggestion
Execute the manual selecting clock reference command again.
3-12

3.16 199005766 Lock the right base when manual

selecting clock reference 0
l Description:Lock the right base when manual selecting clock reference
l Severity:Minor
Probable Cause
The clock board locks the selected reference.
System Impact
None
Handling Suggestion
No need to handle.
3.17 199005767 The manual selecting reference

command is unuseful because the clock board is
in preheat status. 0
l Description:The manual selecting reference command is unuseful because the clock
board is in preheat status.
l Severity:Minor
Probable Cause
Clock board is in preheat status，and does not check the reference and the work mode.So, it does
not response the manual selecting reference command.
System Impact
None
3-13

Handling Suggestion
Execute the manual selecting clock reference command again after the preheat status is over.
3.18 199005956 Board version error. 0

l Description:Board version error.
l Severity:Minor
Probable Cause
Please refer to additional information of the notification for locating the cause that the version can not
be found.
System Impact
Board can not get version file, it may not work.
Handling Suggestion
1.Check the actual attributes of the board and configure the correct version for it. Then re-config the
board version to see if the fault is eliminated.
Y->End alarm handling.
3.19 199005958 IDE version file synchronization

information 0
l Description:IDE version file synchronization information
l Severity:Minor
3-14

Probable Cause
1.Version synchronization is finished.

2.The mate board is not at position and the synchronization cannot be performed.
3.Version synchronization failed.
4.Database records acquisition failed.
System Impact
Some board may not get needed version if OMP board change over after synchronization fail.
Handling Suggestion
1.Check whether there are the corresponding files on the hard disks of the active and the mate
boards if version synchronization fails.
N->Add the required version occurred check if the alarm still occurred, if there is no corresponding file.
Y->Ask the engineers from the R&D department to troubleshoot this problem, if there are
corresponding files.
Take different measures according to the error code type in the additional information.
(1)Version synchronization ends: it means the synchronization is completed normally, there is no
need to handle it.
(2)Mate board is not at position and the synchronization can not be performed.
(3)The file synchronization fails: It needs to add this version manually.
(4)Database records acquisition fails: Please contact ZTE Corporation.
3.20 199005976 Download version failed 0

l Description:Download version failed
l Severity:Minor
Probable Cause
Download version failed.
System Impact
Vesion file download failed.
Handling Suggestion
Check Communications, or Package info.
3-15

3.21 199005977 Running version not match with

database configuration 0
l Description:Running version not match with database configuration
l Severity:Minor
Probable Cause
1.Version datebase configuration changed while board start up.

2.Board boot from OMC, but version configuration of OMC different from version datebase.
System Impact
Running version not match with version database configuration.
Handling Suggestion
Take different measures according to the maybe reason

(1)Upgrade version database configuration by add and active version package.
(2)Check and upgrade OMC or version database configuration,make sure they are match.
3.22 199005978 Boottype different with configure 0

l Description:Boottype different with configure
l Severity:Minor
Probable Cause
1.Boot type auto changed in BOOT state for power-on failed.

2.Upgrade boot type to local triggered by version validation.
System Impact
Current boot type may not agree with user expectation.
3-16

Handling Suggestion
(1)Confirm if it is needed to change current boot type, and configure boot type if needed.
3.23 199005979 Execute version file failed 0

l Description:Execute version file failed
l Severity:Minor
Probable Cause
1.Version file is destroyed.

2.Not a executable file.
3.The logical address that version file belong to is not accurate.
System Impact
Version file execute failed
Handling Suggestion
(1)Backup version package.

(2)Please contact ZTE Corporation.
3.24 199005980 Match version failed 0

l Description:Match version failed
l Severity:Minor
Probable Cause
1.Version configuration is not completed.
System Impact
The relate board's running version is not complete
3-17

Handling Suggestion
(1)Add according version package the version file belong to.

(2)Please contact ZTE Corporation.
3.25 199005981 NCPU version load information 0

l Description:NCPU version load information
l Severity:Minor
Probable Cause
The information of NCPU load.
System Impact
NCPU RUNNING ERR
Handling Suggestion
Restart NCPU device.
3.26 199005982 Patch operation failed 0

l Description:Patch operation failed
l Severity:Minor
Probable Cause
Patch operation failed.
System Impact
Patch can't work correctly
3-18

Handling Suggestion
1.Check the additional information for this alarm, and look for the error patch package.
3.27 199005983 Write back version information 0

l Description:Write back version information
l Severity:Minor
Probable Cause
Write back start and finish information.
System Impact
None
Handling Suggestion
Denote entering into write back version.
3.28 199005984 Check version information 0

l Description:Check version information
l Severity:Minor
Probable Cause
Check version start and finish information.
System Impact
None
Handling Suggestion
Denote entering into check version.
3-19

3.29 199005985 Synchronize version information 0

l Description:Synchronize version information
l Severity:Minor
Probable Cause
Synchronize version start and finish information.
System Impact
None
Handling Suggestion
Denote entering into synchronize version.
3.30 199006017 The Sunit resets by MML command . 0

l Description:The Sunit resets by MML command .
l Severity:Minor
Probable Cause
The Sunit resets by MML command .
System Impact
The Sunit can't be used
Handling Suggestion
Make no manual intervention and just wait the system to recover.
3-20

3.31 199006018 block The Sunit 0

l Description:block The Sunit
l Severity:Minor
Probable Cause
block The Sunit
System Impact
block The Sunit
Handling Suggestion
1.You can control by OMC to cause or resume
3.32 199006720 Notice of power-on status of C51

board/ Board soft reset 0
l Description:Notice of power-on status of C51 board/ Board soft reset
l Severity:Minor
Probable Cause
C51 board is powered on or soft reset successfully.
System Impact
None
Handling Suggestion
No need to handle.
3-21

3.33 199008000 Load Data Fail 0

l Description:Load Data Fail
l Severity:Major
Probable Cause
data load from zdb fail
System Impact
power on fail
Handling Suggestion
NA
3.34 199008007 Save database failed 0

l Description:Save database failed
l Severity:Major
Probable Cause
1:the disk(flash) is full

2:the disk was not formatted
3:IO busy
4:there was no free memory in db's shm
System Impact
After the system reboot, the board fails in power-on because of loading data failure.
3-22

Handling Suggestion
1. Lookup if there is an alarm of the disk's break, please change a new disk.
2. Lookup if the disk is full, please make records of the alarm information and contact ZTE Corporation.
3. Lookup if the db's memory(shm) is full, please make records of the alarm information and contact
ZTE Corporation.
4. Lookup if IO is busy,please wait for a minute and try again.
3.35 199008512 Msater-Slave Fail 0

l Description:Msater-Slave Fail
l Severity:Major
Probable Cause
1.compatible failed;
2.master pack failed;
3.slave up failed;
4.slave table overflow
System Impact
1.data between master and slave is different;2.After ms switch,master lost data
Handling Suggestion
3.36 199008769 Data Sync Between Boards Fail 0

l Description:Data Sync Between Boards Fail
l Severity:Major
3-23

Probable Cause
1、the table struct is inconsistent between boards

2、load data fail after sync finish
System Impact
data is different between boards
Handling Suggestion
1、the table struct is inconsistent between boards ,change version ;

2、reboot
3.37 199008770 Data Sync Loading Fail 0

l Description:Data Sync Loading Fail
l Severity:Major
Probable Cause
load data error
System Impact
data error or dbs system error
Handling Suggestion
1、change zdb file,and ftp data again;

2、reboot
3.38 199008771 Sync by Ftp Fail 0

l Description:Sync by Ftp Fail
l Severity:Major
3-24

Probable Cause
load data error when ftp loading
System Impact
data is different with zdb file.
Handling Suggestion
1、change zdb file,and ftp data again;

2、reboot
3.39 199009024 Notify Fail 0

l Description:Notify Fail
l Severity:Major
Probable Cause
send notify msg fail
System Impact
NA
Handling Suggestion
NA
3.40 199010048 Mem Fail 0

l Description:Mem Fail
l Severity:Major
3-25

Probable Cause
no mem
System Impact
NA
Handling Suggestion
NA
3.41 199010049 DLL Register Fail 0

l Description:DLL Register Fail
l Severity:Major
Probable Cause
1. no *.so file in version pkg 2. mismatch of *.so in pkg
System Impact
power on fail
Handling Suggestion
check files in version, if the .so file is exist and the version is wright
3.42 199010050 Get Lock Timeout 0

l Description:Get Lock Timeout
l Severity:Major
Probable Cause
get lock timeout
3-26

System Impact
NA
Handling Suggestion
get lock timeout
3.43 199010051 Transaction Timeout 0

l Description:Transaction Timeout
l Severity:Major
Probable Cause
transaction commit timeout
System Impact
NA
Handling Suggestion
NA
3.44 199010304 SCCP GT translation failure 0

l Description:SCCP GT translation failure
l Severity:Minor
Probable Cause
1. The GT number of the message can't match in the configuration.

2. Local isn't configured subsystem by translated or subsystem can't be used.
3. The SP by GT translation can't access.
3-27

System Impact
Handling Suggestion
1. Check the GT number if or not configured. If it isn't configured, please add, otherwise:
2. Collecting information and ask for support:
(1) Backup data of configuration about local and remote.
(2) Backup information about alarm of history,alarm of notice,alarm of current.
3.45 199010305 NID not configured 0

l Description:NID not configured
l Severity:Minor
Probable Cause
When the NID translation is performed, it is not configured in the database.
System Impact
Service failed, maybe cause CPU rate is up.
Handling Suggestion
1. Check NID is configured or not about appear in the alarm notice. If isn't configured, please add.
2. Collection information, ask for supporting.
(2) Backup information about alarm of history、alarm of notice、alarm of current.
3.46 199010306 NID translation failure 0

l Description:NID translation failure
l Severity:Minor
3-28

Probable Cause
When the NID translation is performed, it is not translated in the database.
System Impact
Handling Suggestion
1. Check NID of configured right or not about appear in the alarm notice. If isn't right, please modify.
2. Collection information, ask for supporting.
(2) Backup information about alarm of history, alarm of notice, alarm of current.
3.47 199010307 ISNI constrained route information

repetition 0
l Description:ISNI constrained route information repetition
l Severity:Minor
Probable Cause
SCCP ANSI NID translating, the information of NID in the message is repeat, and it is the local NID.
System Impact
Handling Suggestion
Collection information, ask for supporting.

3-29

3.48 199010308 ISNI does not support this route

function 0
l Description:ISNI does not support this route function
l Severity:Minor
Probable Cause
SCCP ANSI NID translating, the indicate information of NID is error.
System Impact
Handling Suggestion

3.49 199010309 NID route prompt failure 0

l Description:NID route prompt failure
l Severity:Minor
Probable Cause
SCCP ANSI NID translating, the route indication of NID is failed, the list of NID is too large.
System Impact
3-30

Handling Suggestion

3.50 199010310 Wrong message type use ISNI function

0
l Description:Wrong message type use ISNI function
l Severity:Minor
Probable Cause
SCCP ANSI NID translating, the non-XUDT message use ISNI function.
System Impact
Handling Suggestion

3.51 199011840 M3UA user office status change 0

l Description:M3UA user office status change
l Severity:Major
Probable Cause
The corresponding AS status is changed
3-31

System Impact
A certain M3UA user under the corresponding office cannot receive or send messages.
Handling Suggestion
1.Check if there is SIO location records of the corresponding users.

2.After the corresponding SIO location has been configured, check if the corresponding AS is
activated.
3.Deactivate and activate the corresponding association. Check if the alarm is eliminated.
3.52 199012096 failed for sig process get the info of

config 0
l Description:failed for sig process get the info of config
l Severity:Minor
Probable Cause
Sig process get the info of config failed
System Impact
The Miss of the function has configed
Handling Suggestion
Add the file of config for sig,and restart the board.
3.53 199012097 The file of sig config updated 0

l Description:The file of sig config updated
l Severity:Major
3-32

Probable Cause
The config file is updated
System Impact
Sig process can't work
Handling Suggestion
Reboot board which have sig process
3.54 199012352 failed for sig process get memory

resource 0
l Description:failed for sig process get memory resource
l Severity:Minor
Probable Cause
Sig process get memory resource failed
System Impact
lack of memory
Handling Suggestion
Add memory,and restart the board.
3.55 199013888 ASP status changed 0

l Description:ASP status changed
l Severity:Minor
3-33

Probable Cause
ASP status is changed.
System Impact
The status of related AS may be impacted.
Handling Suggestion
1. Check whether association interruption alarm occurs. If yes, refer to the corresponding alarm
Related alarm: 8417538 Association link broken
2. Activate the ASP in dynamic data management.
3. Check whether ASP operation is performed at the opposite end.
3.56 199013889 AS status changed 0

l Description:AS status changed
l Severity:Minor
Probable Cause
AS Status is changed.
System Impact
May result in changes of corresponding adjacent office state.
Handling Suggestion
1. Check whether association interruption alarm occurs. If yes, refer to the corresponding alarm
2. Activate ASP under the AS in dynamic data management.
3-34

3.57 199013890 Sigtran error message received 0

l Description:Sigtran error message received
l Severity:Minor
Probable Cause
Error message received.
System Impact
Different errors have different influences upon the system, such as no influence, office inaccessible,
and service loss.
Handling Suggestion
1. Check AS configuration to see whether the configured traffic mode at both sides are consistent. If
no, modify configuration to keep consistency.
2. APP server AS ID configuration must meet the following requirements. If ASP is configured for
local end, SGP should be configured for Opposite end. Vice versa. If IPSP client is configured for
local end, IPSP server should be configured for opposite end. Vice Versa.
3. Activate the ASP in dynamic data management.
4. On NMS configuration management interface (AS configuration), check if routing context and
routing context ID are configured. Ensure that the routing contexts configured at both ends are
the same.
5. On NMS configuration management interface, check whether the local ASP in service for AS is
configured. If no, add the configuration.
6. Check the protocol versions used at both sides. Ensure that the protocol versions are the same.
3.58 199013891 Sigtran notification message received

0
l Description:Sigtran notification message received
l Severity:Minor
3-35

Probable Cause
Notification message on AS-ASP status received.
System Impact
None
Handling Suggestion
1. On NMS configuration management interface (AS configuration), query ASP-related associations.

Check whether interruption alarm occurs in the association(s). If yes, refer to the corresponding
alarm handling suggestion.
2. Reactivate ASP in dynamic data management.
3.59 199014144 Association Establishment Failure 0

l Description:Association Establishment Failure
l Severity:Major
Probable Cause
The Sctp fails to create the association.
System Impact
If several association links are available to the destination office, service will not be affected by
establishment failure of one association. In the case of heavy traffic, 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 office, the office might become
inaccessible. Reception and sending of messages from/to the relevant office fail. Access of services
under this office fails.
3-36

Handling Suggestion
1. On NMS configuration management interface, check association configuration at local end and
opposite end. Checking items include local IP address, local port No., remote IP address, remote port
No., and application property of SCTP association. If the association at local end is configured as
client, the association at opposite end should be configured as server. Vice Versa.
2. At local end, check whether the associations configured with different protocol types have the
same local IP address and local port No.. If yes, perform configuration modification to differentiate the
local IP address and local port No. of these associations.
3. Check protocol stack configuration at both ends to see if interface board addresses are in the same
network segment. If no, modify configuration to put two addresses in the same network segment.
4. Ping the opposite-end interface board address to see if the network cable or other intermediate link
is faulty. Replace the cable if ping fails.
3.60 199014145 Association restart 0

l Description:Association restart
l Severity:Major
Probable Cause
1. At remote end,association breakdown but restart at once.

2. Bottom layer link unstable, so check time point at both ends is not same in a short time and
association restart at remote end.
System Impact
Usually, there is no effect to process, at worst condition, association breakdown and restart at once.
Handling Suggestion
1. Please contact related personnel on the remote end to find out why association breakdown.
2. Ensure that connector contact and cable connection are normal.
3.61 199014146 Dynamic Association link broken 0

3-37

l Description:Dynamic Association link broken

l Severity:Minor
Probable Cause
The dynamic association link broken..
System Impact
may result a office unaccessible ,or may result other association congested
Handling Suggestion
No need to handle.
3.62 199014148 One user of share association is in

service 0
l Description:One user of share association is in service
l Severity:Major
Probable Cause
The sctp associocation is established
System Impact
none
Handling Suggestion
No need to handle.
3.63 199014149 One user of share association is out

of service 0
3-38

l Description:One user of share association is out of service
l Severity:Major
Probable Cause
One user of share association is out of service
System Impact
The unestablished assoc will result in the status(down) of asp directly , and in some case the status of
As and office maybe not correct also.
Handling Suggestion
No need to handle.
3.64 199014150 Association config error 0

l Description:Association config error
l Severity:Major
Probable Cause
The config of association's stream is error or is not configured in SCTP layer yet
System Impact
The associated can't set up
Handling Suggestion
1. Please check streams: M2PA:2, M2UA/SUA/M3UA/IUA:2-17, other:1-17
2. Please check if the assoication is already configured in SCTP layer
3.65 199014151 SSM malloc memory failure 0

3-39

l Description:SSM malloc memory failure

l Severity:Minor
Probable Cause
Dynamic memory application is failed
System Impact
None
Handling Suggestion
Enlarge memory capacity and then restart the board.
3.66 199014152 Dynamic association config error 0

l Description:Dynamic association config error
l Severity:Minor
Probable Cause
The config of dynamic association is error
System Impact
The associated can't set up
Handling Suggestion
Please check the config of dynamic assoc:
1.The dynamic assoc can't config remote IP and PORT
2.The dynamic assoc can't config the client property
3.The dynamic assoc can't support the protocal
3.67 199017472 Data configuration abnormal 0

3-40

l Description:Data configuration abnormal

l Severity:Minor
Probable Cause
the data that MTMA of PP received from OMP is abnormal
System Impact
Maybe the PP board cann't work properly.
Handling Suggestion
Check the configuration data.
3.68 199017473 Configuration file abnormal 0

l Description:Configuration file abnormal
l Severity:Minor
Probable Cause
That MTMA get and parse configuration file is abnormal or configuration file is updated
System Impact
configuration information have not enabled or mcs process is restarted
Handling Suggestion
Check the configuration file
3.69 199017728 Database access abnormal 0

l Description:Database access abnormal
l Severity:Major
3-41

Probable Cause
exception occurs when MTMS access database
System Impact
The MCS cann't work
Handling Suggestion
Check the OMP
3.70 199017990 RPU detected board down 0

l Description:RPU detected board down
l Severity:Minor
Probable Cause
The board heartbeat was lost.
System Impact
Interfaces on this board are unavailable.
Handling Suggestion
1. Reinsert the board tightly, review whether this alarm still presents.
Y->go to "2".
N->End.
2. Turn off ENUM switch, review whether this alarm still presents.
Y->Please contact ZTE Corporation.
N->End.
3.71 199018240 TCP Receiving RST Packet 0

l Description:TCP Receiving RST Packet
3-42

l Severity:Minor
Probable Cause
1. The remote end reset this TCP connection through sending RST packet.
2. The remote end receives the TCP connection that is unavailable and responds by
sending RST packet.
System Impact
1. The TCP service discards received reset reports, and the service stays in monitoring
status.
2. There is no impact on the upper layer services.
Handling Suggestion
Y->2
N->3
2. Troubleshoot the physical connection, and check whether the alarm is eliminated.
Y->End
N->3
3.72 199018241 TCP Connection Disconnected 0

l Description:TCP Connection Disconnected
l Severity:Major
Probable Cause
1. Hardware fault, for example, external interfaces of local/remote devices are broken,
the intermediate switch device is broken, or the transmission channel is interrupted.
2. Bearer network communication fault, such as external interfaces of local/opposite
device are faulty, physical intermediate device or route is faulty, or the bearer link is
faulty.
3. Configuration is improper, for example, the route or interface address of the local/opposite
device changes.
4. Device is faulty, for example, the NE control panel channel of local/opposite device is
disconnected.
3-43

System Impact
TCP connection is disconnected and the communication is disconnected.
Handling Suggestion
Y->2
N->3
2. Troubleshoot the physical connection, and check whether the alarm is eliminated.
Y->End
N->3
3. In the NM alarm management window, check whether the ALM-8393985 Abnormal
Control Plane Communication Between Board and Home ModuleALM-8393988
Abnormal Control Plane Communication Between Module and OMP alarms are
reported on the home module.
Y->4
N->5
4. Handle the faults according to the alarm suggestions, and check whether the alarm is
eliminated.
Y->End
N->5
5. Contact the opposite device maintenance personnel to remove the NE fault. Check
whether the notification is removed.
Y->End
N->6
3.73 199018242 MD5 Verification Failure 0

l Description:MD5 Verification Failure
l Severity:Minor
Probable Cause
MD5 check is not configured in the message of the application layer.
System Impact
TCP discards the received reports, which results in application layer communication failure.
3-44

Handling Suggestion
1. Observe both ends of the application layer and check whether MD5 is not configured.
Y->2
N->3
2. Set MD5 and check whether the notification is removed.
Y->End
N->3
3.74 199018243 MD5 Message Error 0

l Description:MD5 Message Error
l Severity:Minor
Probable Cause
The MD5 keys at both ends are not consistent with each other when the application layer
sends and receives packets.
System Impact
TCP discards the received reports, which results in application layer communication failure.
Handling Suggestion
1. Check whether the MD5 passwords at both ends are not consistent with each other.
Y->2
N->3
2. Set the same MD5 passwords at two ends and check whether the notification is
removed.
Y->End
N->3
3-45

3.75 199018244 SOCKET received queue over

threshold value 0
l Description:SOCKET received queue over threshold value
l Severity:Minor
Probable Cause
The used of the socket received queue over threshold value
System Impact
lead application service into error
Handling Suggestion
1.Check whether the threshold of socket queue is too low through debug function in EPU.
Y->Set a large value. The troubleshooting completes.
N->It may be caused by abnormal upper layer service,Go to "2"
3.76 199018245 SOCKET abnormally closed 0

l Description:SOCKET abnormally closed
l Severity:Major
Probable Cause
Socket send or receive buffer error.
System Impact
Socket closed and the corresponding communication interrupted.
3-46

Handling Suggestion
1.Make no manual intervention and just wait the system to recover.Check whether the alarm
disappears after 2 minutes.
Y->End.
N->Contact ZTE.
3.77 199018500 The peer IP address configuration and

the local IP address configuration of PPP link is
the same 0
l Description:The peer IP address configuration and the local IP address configuration
of PPP link is the same
l Severity:Minor
Probable Cause
The peer IP address configuration and the local IP address configuration of PPP link is the same.
System Impact
Network communication will be interrupted.
Handling Suggestion
1. Check if the port is self-loop.
Y->cancel loopback
N->go to "2"
2. Check if the peer IP address configuration is same as the local IP address configuration of PPP link.
Y->reconfigure unrepeatable IP address
3.78 199018501 The HDLC channel of EPU created fail 0

l Description:The HDLC channel of EPU created fail
3-47

l Severity:Minor
Probable Cause
1.EPU board property is T1,but timeslot of port overrun No.24

2.The E1 sunit of port is not belong to PPP.
3.The number of port is exceed the max.
4.The E1 No.of port is exceed the max E1 No.
5.creat Hdlc channel failed.
System Impact
The link of PPP is creat failed.
Handling Suggestion
1.Check if EPU board property is T1.

Y->go to "2"
N->go to "3"
2.Check if the timeslot of port is excess No.24
Y->modify the configuration,make sure timeslot is not overrun No.24
N->go to "3"
3.Check if the E1 sunit of port is not belong to PPP
Y->modify the E1 sunit,make it belong to PPP.
N->go to "4"
4.Check if the port No is excess the max
Y->this configure is invalid ,Please delete this port.
N->go to "5"
5.Check if the E1 Num is excess max num.
Y->modify the E1 num
N->go to "6"
6.Please contact with ZTE corporation.
3.79 199018504 The HDLC channel created

unsuccessfully before is created successfully now.
0
l Description:The HDLC channel created unsuccessfully before is created successfully
now.
3-48

l Severity:Minor
Probable Cause
1.Because of disappear of error environment before, now HDLC create successfully now
System Impact
The HDLC link created fail before now is created successfully.
Handling Suggestion
NONE.
3.80 199018755 HDLC status changed 0

l Description:HDLC status changed
l Severity:Major
Probable Cause
1. This notification occurs when an HDLC is created;

2. The link is broken or recovered.
System Impact
If the HDLC is the last available one in the UID,the service on the UID will be interrupted. If the HDLC
is not the last available one in the UID, the traffic on the UID will be reduced.
Handling Suggestion
1.Check the settings of HDLC channel to see whether the E1/TI of this HDLC and its time slots are
accordant with the peer end.
Y->Go to "2".
N->Modify HDLC settings and make it accordant with the peer end HDLC, and go to "2" if this alarm
still exists.
2.Check whether the physical connection is correct.
Y->Go to "3".
N->Change physical connection and make it accordant with the peer end, and go to "3" if this alarm
still exists.
3.Check whether the E1/T1 line is damaged.
Y->Change the E1/T1 line, and go to "4" if this alarm still exists.
3-49

N->Go to "4".
4.Note down the statistic data of messages received and sent from the HDLC, and contact ZTE.
3.81 199019008 Fail to config the ATM port 0

l Description:Fail to config the ATM port
l Severity:Minor
Probable Cause
1.The port rate is larger than the limit of pyhsical port when creating atm port;
2.There is at least one atm pvc on the atmport when deleting atm port;
3.The port rate is less than the sum of the pvc rate on the atm port when modifing atm port;
System Impact
Can not config PVC on the port,ATM can not be work normally.
Handling Suggestion
Check the parameters of the port:1.The port rate isn't out of the range about the type.
2.The rate must be enough for the current pvc on the port when you modify the port rate.
3.Please confirm there is not pvc on the port.
3.82 199019264 IMA Group Related Operations Failure

0
l Description:IMA Group Related Operations Failure
l Severity:Minor
Probable Cause
When the IMA group related operations (such as adding, deleting or modifying a group) initiated by
the oamback fail,this alarm appears. In general, the reason is that the group parameters are incorrect
when the operations are initiated.
3-50

System Impact
The designated configuration does not go into effect in relating board.
Handling Suggestion
1.Check whether the parameters related to the initiated operations are correct.
Y->If so, go to '2'.
N->If not, modify them and perform operations again. If the operations can be performed successfully,
finish the alarm handling. If not, go to '2'.
2. Check if the operation steps are legal.
N->If not, perform the operations according to correct steps. If the operations can be performed
successfully, finish the alarm handling. If the operations fail, please contact ZTE Corporation for help.
3.83 199019265 IMA Link Operations Failure 0

l Description:IMA Link Operations Failure
l Severity:Minor
Probable Cause
When the IMA link related operations (such as adding or deleting a ima link) initiated by the oamback
fail, this alarm appears. In general, the reason is that the link parameters are incorrect when the
operations are initiated.
System Impact
Handling Suggestion
1.Check whether the parameters related with the initiated operations are correct.
Y-> If so, go to '2'.
N-> If not, modify them and perform the operations again. If the operations can be performed
successfully, finish the alarm handling. If they can not be performed successfully, please go to '2'.
2.Check if the operation steps are legal.
3-51

3.84 199019777 APS switchover happens 0

l Description:APS switchover happens
l Severity:Minor
Probable Cause
1. Optical interface is faulty. LOS/SF/SD alarms might exist.

2. When board backup mode is 1:1, any of the following events occurs.
Input clock loss;
Inner HW/LVDS alarm;
Inner media plane port alarm;
Board power off;
Board reset (the board where the working optical interface is located);
3. Switching is initiated by opposite end.
4. In recovery mode, fault recovery time in optical interface exceeds 5 minutes.
5. APS switching request/clearance is initiated by OAM.
System Impact
During APS switching, the link is interrupted for 10 to 50 ms. Few packets loss might occur, but
service is not affected.
Handling Suggestion
Check operation and maintenance log to see if O&M personnel initiated manual APS switching
request/clearance. If yes, no handling is necessary. If no, check if the following alarms are declared
in the board. If such alarm exists, refer to the corresponding alarm handling suggestion.
3.85 199020290 Failed to Power on Protocol Stack 0

l Description:Failed to Power on Protocol Stack
l Severity:Major
3-52

Probable Cause
1. RPU fails to register.
2. Protocol stack fails to request for system configuration.
3. The control-plane communication is broken.
System Impact
The protocol process could not enter working state.
Handling Suggestion
1. Check whether the home module MP and the local board system control are normal
and whether their communication is normal.
Y->4
N->2
2. Plug this board and reset hardware, check whether the fault is eliminated.
Y->End
N->3
3. Replace the faulty board, and check whether the alarm is eliminated.
Y->End
N->4
3.86 199020554 Add IP route failed 0

l Description:Add IP route failed
l Severity:Minor
Probable Cause
Add UID or PPP route failed.
System Impact
Communication failed.
Handling Suggestion
1.Check whether the destination IP of new route has been used by other routes.
2.Check whether the route table is full.
3-53

3.87 199020802 Conflicting IP addresses 0

l Description:Conflicting IP addresses
l Severity:Minor
Probable Cause
1. The IP address (including virtual addresses in the same network section) configured
for this gateway is same with that of other host in the network.
2. This is a loop in the networking.
3. VLAN is not divided or divided improperly.
System Impact
The device and alarm interface in the network share the same IP address, if you continue
to use this interface, its services will be unavailable and its connection will be connected and
disconnected intermittently. Meanwhile, ARP pf other communication devices will be
updated frequently.
Handling Suggestion
1. Check the port configuration to see if the same IP address has been configured.
Y->2
N->3
2. Modify a port IP address, and check whether the notification is eliminated.
Y->End
N->3
3.88 199020803 Conflicting MAC Addresses in Subnet 0

l Description:Conflicting MAC Addresses in Subnet
l Severity:Minor
3-54

Probable Cause
1. The MAC address of this network is the same with the other MAC address in the
associated network.
2. This is a loop in the networking.
3. VLAN is not divided or divided improperly.
System Impact
The lay-2 device will transfer MAC based on the target MAC, and port MAC influences
layer-2 MAC recording. In case of MAC address conflict, MAC recording will be influenced,
and the reports will be sent and received intermittently,
Handling Suggestion
1. Check whether the port has configured the same MAC address.
Y->2
N->3
2. Modify the MAC address of a port, and check whether the notification is eliminated.
Y->End
N->3
3.89 199021059 RIP Neighbor Configuration Error 0

l Description:RIP Neighbor Configuration Error
l Severity:Minor
Probable Cause
When adding a neighbor, the address of the neighbor mismatches with that of the interface.
System Impact
The dynamic routes needed to be from this neighbor can not be established.
3-55

Handling Suggestion
1.Check the address of interface to see whether it is in the same network segment with that of RIP
neighbor.
Y->If so, go to "3".
N->If not, go to "2".
2.Check if the configured neighbor address is the network number or broadcast address.
N->go to "4".
3.Reconfigure the neighbor address to finish the alarm handling.
4.Contact ZTE Corporation.
3.90 199021060 RIP Interface Authentication Error 0

l Description:RIP Interface Authentication Error
l Severity:Minor
Probable Cause
When the interface needs to be authenticated, the authentication code is wrong.
System Impact
RIP messages cannot be properly received.
Handling Suggestion
1.Check if the authentication types on the two ends are consistent. If not, go to "2". Y-> If so, go to "3".
2.Modify authentication types on two ends as consistent ones. And Finish the alarm handling.
3.If the authentication types are consistent, check if the authentication keys are consistent, if so, go to
"4". If not, modify them as consistent ones. Finish the alarm handling.
3.91 199021065 Incompatible RIP Version Number 0

l Description:Incompatible RIP Version Number
3-56

l Severity:Minor
Probable Cause
The version number of the interface on remote device is inconsistent with that on local device.
System Impact
RIP messages cannot be properly received.
Handling Suggestion
1.Check if the version number of the interface on remote device is inconsistent with that on local
device.
Y->Go to "3".
N->Go to "2".
2.Reconfigure it and finish the alarm handling.
3.92 199021329 LSDB overflow 0

l Description:LSDB overflow
l Severity:Major
Probable Cause
The LSDB (Link Status Database) overflows.
System Impact
Failed to synchronize of LSDB with other routers.
Handling Suggestion
1.Configure route aggregation to reduce the number of LSAs. Check if the alarm is eliminated.
Y->If so, finish the alarm handling.
3-57

3.93 199021330 Configuration of OSPF mismatched 0

l Description:Configuration of OSPF mismatched
l Severity:Minor
Probable Cause
Configuration mismatched, OSPF cannot run in normal.
System Impact
Cannot learn and calculate route.
Handling Suggestion
1.To modify the relevant configuration of OSPF and make them being coordinated. Check if the
alarm is eliminated.
3.94 199021573 BGP Gets TCB Fail on Active

Connection 0
l Description:BGP Gets TCB Fail on Active Connection
l Severity:Major
Probable Cause
Neighbors can not be completed with the TCP session.
System Impact
BGP session fails to be created on active connection.
3-58

Handling Suggestion
1.Check if configuration of peer router is correct.

N->If not, ensure that the router is configured correctly.
2.Check if the route from the neighbor end to local is exist.
Y->If so, please contact ZTE corporation.
N->If not, ensure that the route from the neighbor end to local is exist.
3.95 199021584 Neighbor Hold Timer Expired 0

l Description:Neighbor Hold Timer Expired
l Severity:Minor
Probable Cause
1.The physical link is interrupted.

2.TCP connection is interrupted.
System Impact
BGP session is disconnected.
Handling Suggestion
1.Check if the network configuration is correct.

Y->Go to "2".
N->Configure correctly and finish the alarm handling.
2.Check if the interface network connection and network topology are correct.
N->Connect the port to the network correctly and finish the alarm handling.
3.96 199021585 BGP Interface down and Neighbor Link

Broken 0
3-59

l Description:BGP Interface down and Neighbor Link Broken

l Severity:Major
Probable Cause
Message 'local interface is down' is received.
System Impact
The session of the BGP neighbor on this interface is unavailable.
Handling Suggestion
1.Check if the interface is activated (using show ip interface brief command).

Y->Please contact ZTE Corporation,
N->Go to "2".
2.Check if the port is connected to the network correctly.
N->Connect the port to the network correctly. And check if the alarm disappears, if so, finish the
alarm handling.
3.97 199021837 Failure in adding dynamic routings 0

l Description:Failure in adding dynamic routings
l Severity:Major
Probable Cause
Forwarding table overflow causes the failure in adding routes.
System Impact
Lost of routes from Routing Protocol
3-60

Handling Suggestion
1.Check routes on RPU to see if there are any needless interface addresses and static routes.
Y->If there are, delete the unwanted IP interface addresses or static routes, go to "2".
N->If IP address is not configured on the interface, go to "3".
3.Reduce the quantity of its distributed route information through route aggregation on the peer router.
And check if the alarm is eliminated on the local.
4.Record the detailed information.
1)Record IP address and static route information on the interface.
2)Record the dynamic route information. Contact ZTE Corporation.
3.98 199022336 Intra-Office Port MAC Conflict 0

l Description:Intra-Office Port MAC Conflict
l Severity:Minor
Probable Cause
The default MAC of the port conflicts with a configured MAC of an intra-office port.
System Impact
The NE MAC addresses conflict, and these two ports cannot communicate with each other.
Handling Suggestion
1. Check whether the existing port MAC conflicts with the MAC you want to configure.
Y->2
N->3
2. Change to other MAC value, and check whether the notification is eliminated.
Y->End
N->3
3-61

3.99 199022593 ISIS Hello Message Authentication

Failure 0
l Description:ISIS Hello Message Authentication Failure
l Severity:Minor
Probable Cause
Hello message authentication modes or keys configured on the routers of the two ends are
inconsistent.
System Impact
The report that fails in the Hello authentication is omitted and the local router can not synchronize
the link status with the corresponding router.
Handling Suggestion
1.Find out the peer-end router according to system id in the alarm message.
2.Execute the show running config command locally and remotely. Check the routers on the two ends
in the displayed device running configuration to see if the protocol authentication modes in ISIS
protocol stack instance configuration are consistent (MD5/TEXT).
Y->Go to "3".
N->Modify the protocol authentication modes on the routers of the two ends as the consistent ones
and perform the interconnection operations again. Finish the alarm handling.
in the displayed device running configuration to see if the protocol message authentication keys in
ISIS protocol instance configuration are consistent (MD5/TEXT).
3.100 199022594 ISIS LSP Message Authentication

Failure 0
l Description:ISIS LSP Message Authentication Failure
3-62

l Severity:Minor
Probable Cause
LSP message authentication modes or keys configured on the routers of the two ends are
inconsistent.
System Impact
The report that fails in the LSP authentication is omitted and the local router can not synchronize
Handling Suggestion
Y->Go to "3".
3.101 199022595 ISIS SNP Message Authentication

Failure 0
l Description:ISIS SNP Message Authentication Failure
l Severity:Minor
Probable Cause
SNP message authentication modes or keys configured on the routers of the two ends are
inconsistent.
3-63

System Impact
The report that fails in the SNP authentication is omitted and the local router can not synchronize
Handling Suggestion
Y->Go to "3".
3.102 199022597 Abnormal Message is Received 0

l Description:Abnormal Message is Received
l Severity:Minor
Probable Cause
The erroneous message is received.
System Impact
The erroneous report is discarded.
Handling Suggestion
1.Check if the bottom link has communication problems and if there is any illegal system in the
network.
3-64

3.103 199022598 Routers with Conflicting System Id

Exist in Network 0
l Description:Routers with Conflicting System Id Exist in Network
l Severity:Minor
Probable Cause
In ISIS instance configuration under protocol stack configuration mode, System-id has wrong
configuration.
System Impact
ISIS Protocol-Neighbor can not set up between the Routers with system id conflicting.
Handling Suggestion
1.Check system id configuration in ISIS instance on the router by show running config command
for conflict.
Y->Modify system id configuration in the instance, go to "2".
Y->Finish the alarm handling.
3.104 199025620 Top resource insufficient 0

l Description:Top resource insufficient
l Severity:Minor
Probable Cause
Top resource insufficient.
System Impact
Top Resource of the board is not available.
3-65

Handling Suggestion
Check remain top resource
3.105 199026176 The currently locked reference of the

clock board has been changed 0
l Description:The currently locked reference of the clock board has been changed
l Severity:Minor
Probable Cause
The currently locked reference of the clock board has been changed.
System Impact
Handling Suggestion
No need to handle.
3.106 199026178 Clock work mode is changed 0

l Description:Clock work mode is changed
l Severity:Minor
Probable Cause
The clock work mode of the clock board has changed.
System Impact
3-66

Handling Suggestion
No need to handle.
3.107 199028231 Router ID not configured for OSPFv3 0

l Description:Router ID not configured for OSPFv3
l Severity:Minor
Probable Cause
Router ID not configured for OSPFv3.
System Impact
Can't create OSPFv3 instance.
Handling Suggestion
1.Configure an IPv4 address for an interface (It is recommended to configured an IPv4 address for a
Loopback interface) , make it a Router ID, and then re-create an OSPF process. Check whether
the alarm disappears.
Y->End.
N->Contact ZTE.
3.108 199028233 Configuration of OSPFv3 Mismatched

0
l Description:Configuration of OSPFv3 Mismatched
l Severity:Minor
Probable Cause
Cannot learn and calculate route because of configuration mismatched.
3-67

System Impact
Failed to learn and calculate route.
Handling Suggestion
1.To modify the relevant configuration of OSPF and make them being coordinated. Check if the
alarm is eliminated.
3.109 199028993 SCTP Primary Path Set Failed 0

l Description:SCTP Primary Path Set Failed
l Severity:Minor
Probable Cause
The remote address of the first choice channel is not in the address list of the TCB
association.
System Impact
SCTP fails to send the service data to the expected path.
Handling Suggestion
1. At the remote end, execute the SHOW SCTPAC command to query the SCTP
association configuration and the local IP address configuration.
2. At the local association end, modify the remote IP address to the local IP address
obtained in step 1.
Y->End
N->3
3.110 199028994 SCTP Change Nexthop 0

3-68

l Description:SCTP Change Nexthop
l Severity:Minor
Probable Cause
Due to a link problem, the retransmission occurred three time in the association, or the previously-fixed
next hop was done with a poor quality, which caused the SCTP next hop to switch,or the SCTP next
hop switched back when the originally allocated next hop was recovered.
System Impact
Abnormal link communication may cause uneven payload of the association.
Handling Suggestion
The user can check the previous next hop link based on notifications to determine whether a problem
has occurred to any middle device.Compare the previous notifications to determine whether it is a
switch back after the link is recovered.
3.111 199028998 SCTP abnormally congested 0

l Description:SCTP abnormally congested
l Severity:Minor
Probable Cause
SCTP congesting for a long time whitout recover.
System Impact
Association broken down,the corresponding communication interrupted.
Handling Suggestion
1.Make no manual intervention and just wait the system to recover. Check whether the alarm
disappears after 2 minutes.
Y->End.
N->Contact ZTE.
3-69

3.112 199028999 Module Asso Num Exceed 0

l Description:Module Asso Num Exceed
l Severity:Minor
Probable Cause
Configured static asso number in the module is exceed
System Impact
the exceed assocation can't established
Handling Suggestion
delete some assocation configure
3.113 199029000 SCTP receive queue over threshold

value 0
l Description:SCTP receive queue over threshold value
l Severity:Minor
Probable Cause
The used of the sctp received queue over threshold value
System Impact
lead application service into error
Handling Suggestion
1.Check whether the threshold of sctp queue is too low through debug function in EPU.
Y->Set a large value. The troubleshooting completes.
N->It may be caused by abnormal upper layer service,Go to "2"
3-70

3.114 199029760 DNS server inaccessible 0

l Description:DNS server inaccessible
l Severity:Minor
Probable Cause
DNS server makes no response, so the link may be broken or the DNS server is down.
System Impact
DNS doesn't work.
Handling Suggestion
1.Use command Ping to check whether the link between the network element which the DNS client
belongs to and the DNS server is available.
Y->Go to "2".
N->Solve the physical link problem.
2.Check the status of DNS server to see whether it is listening at port 53.
Y->Contact ZTE.
N->Solve equipment problem.
3.115 199030016 Ethernet link OAM event 0

l Description:Ethernet link OAM event
l Severity:Minor
Probable Cause
Link quality or port Mac quality is poor
System Impact
service may lost partly.
3-71

Handling Suggestion
1. Check the fiber Rx if connetivity is good or electric cable is loose.Put out the fiber or cable and
put in it.Observe if the alarm restore.
Yes-> alarm restore
No-> jump "2"\
2. Replace the cable to peer port on the same device.Insure peer move the other port on the device.
Yes-> alarm restore
No-> phone ZTE corporation
3.116 199030528 The result of configured PD task start

0
l Description:The result of configured PD task start
l Severity:Minor
Probable Cause
1. As the result of the parameter is wrong such as wrong configurations of source address and
destination address, the configured PD task fail to start.
2. Failed to start task because the task pool is full.
System Impact
The PD task fails to start, service is not affected.
Handling Suggestion
1. Check whether or not the PD task start successfully:

Y->End.
N->Go to step 2;
2. Check whether or not the local IP address and peer IP address configured are true:
Y->Go to step 3;
N->Go to step 5;
3. Check whether or not the destination IP address is local net element:
Y->Go to step 6;
N->Go to step 4;
4. Check whether or not there is route:
Y->Contact ZTE Corporation.
N->Go to step 7;
3-72

5. Change the configuration of the local IP address and peer IP address,and check whether or not
the PD task start successfully:
Y->End.
N->Go to step 3;
6. Change the configuration of the destination IP address,and check whether or not the PD task
start successfully:
Y->End;
N->Go to step 4;
7. Configure the route,and check whether or not the PD task start successfully:
Y->End.
3.117 199030787 ATCA Fru Power On 0

l Description:ATCA Fru Power On
l Severity:Minor
Probable Cause
ATCA FRU Power On.
System Impact
none
Handling Suggestion
NONE
3.118 199030790 ATCA Fru Power Off 0

l Description:ATCA Fru Power Off
l Severity:Minor
3-73

Probable Cause
ATCA FRU Power Off.
System Impact
none
Handling Suggestion
NONE
3.119 199030794 ATCA Fru Communication Lost 0

l Description:ATCA Fru Communication Lost
l Severity:Minor
Probable Cause
ATCA FRU Communication Lost.
System Impact
none
Handling Suggestion
Check IPMB bus.
3.120 199030800 ATCA Fru Communication Regain 0

l Description:ATCA Fru Communication Regain
l Severity:Minor
Probable Cause
ATCA FRU Communication Regain.
3-74

System Impact
none
Handling Suggestion
NONE
3.121 199030815 HOST CPU RESET EVENT 0

l Description:HOST CPU RESET EVENT
l Severity:Minor
Probable Cause
Heartbeat lost;CMM command;Panel reset-keypress;Hardware watchdog;Global reset
System Impact
Board reboot, board function invalid
Handling Suggestion
Check Payload
3.122 199030817 BIOS Start-up Inform 0

l Description:BIOS Start-up Inform
l Severity:Minor
Probable Cause
BIOS Start-up Inform
System Impact
none
3-75

Handling Suggestion
Check BIOS
3.123 199030820 BIOS Memory Inform 0

l Description:BIOS Memory Inform
l Severity:Minor
Probable Cause
BIOS Memory Inform
System Impact
none
Handling Suggestion
Check Memory
3.124 199030821 Power On Failed Inform 0

l Description:Power On Failed Inform
l Severity:Minor
Probable Cause
Hardware or software may be abnormal.
System Impact
Board can't enter word status.
Handling Suggestion
Check board according to attached detail.
3-76

3.125 199030828 ATCA FRU present 0

l Description:ATCA FRU present
l Severity:Minor
Probable Cause
ATCA FRU is present.
System Impact
none
Handling Suggestion
1.Check whether it is expected

Y->End
N->2
2.Extract the FRU,check whether there is an ALM-30829 reported.
Y->End
N->3
3.contact the ZTE office
3.126 199030829 ATCA FRU absent 0

l Description:ATCA FRU absent
l Severity:Minor
Probable Cause
ATCA FRU is offline.
System Impact
The board maybe work abnormally
3-77

Handling Suggestion
1.Check whether it is expected

Y->End
N->2
2.Insert the FRU,check whether there is an ALM-30828 reported.
Y->End
N->3
3.contact the ZTE office
3.127 199031296 PTP failed to cancel slave port 0

l Description:PTP failed to cancel slave port
l Severity:Minor
Probable Cause
PTP failed to cancel slave port
System Impact
Two salve ports may exist at the same time
Handling Suggestion
No need to handle.
3.128 199031554 IP address of DHCP server alloc to

client is conflict 0
l Description:IP address of DHCP server alloc to client is conflict
l Severity:Minor
3-78

Probable Cause
The IP address which DHCP server is assigned to client is conflict
System Impact
The client can't get the IP address
Handling Suggestion
Check whether the configuration of IP is conflict, or there are other users use this IP on the network
3.129 199041473 Fail to config the ATM pvc 0

l Description:Fail to config the ATM pvc
l Severity:Minor
Probable Cause
1.PVCID is invalid;
2.The ingress connection and the egress connection is not in same board;
3.The VPI or VCI of the ingress connection is conflicting between the egress connection.
4.The traffic parameters is invalid;
5.The port number is invalid.
6. The service category has not accorded with traffic type.
System Impact
Up layer link is bad.The service on the PVC can not be supllied
Handling Suggestion
Check the parameters of the pvc:

1.PVCID must be in the range of 1-12600;
2.The ingress and egress is in the same board;
3.The VPI or VCI of the ingress is not conflicting between the egress;
4.The traffic parameters accorded the require of chip;
5.The port was configed correctly.The VPI is smaller or equal to the MAXVPI of the port. The VCI
is smaller or equal to the MAXVCI of the port.
6. The service category must accorded with traffic type.
3-79

3.130 199041794 TC Link Operations Failure 0

l Description:TC Link Operations Failure
l Severity:Minor
Probable Cause
When the TC link-related operations (such as adding or deleting a tc link) initiated by the oamback
fail, this alarm appears. In general, the reason is that the tc link parameters are incorrect when
the operations are initiated.
System Impact
Handling Suggestion
1.Check whether the parameters related with the initiated operations are correct.
Y->If so, go to '2'.
N->If not, modify them and perform the operations again. If the operations can be performed
successfully, finish the alarm handling. If they can not be performed successfully, go to '2'.
2.Check if the operation steps are legal.
Y->If so, please contact ZTE Coroperaton for help.
3.131 199070002 Iu interface global reset notification 0

l Description:Iu interface global reset notification
l Severity:Minor
Probable Cause
1. RESET message is sent by CN.

2. The signaling point of the office related to the CN is inaccessible.
3. Global reset is triggered by NMS.
3-80

System Impact
The services that have been established are released. Access of new service is denied. Service
access will be restored in 3 seconds.
Handling Suggestion
View alarm details on the NMS Alarm Management interface to check the alarm reason, which can
help you easily find the corresponding handling suggestions.
The handling suggestions for each alarm are as follows:
1.Alarm reason: The CN sends a RESET message.
1) Check the operation log of the NMS to see if any resetting is initiated. If yes, no handling is required.
2) Check if there is any of the following transmission-related alarms. If yes, follow the corresponding
suggestions to handle it:
199066005 SCCP subsystem unavailable
199066010 MTP3 office inaccessible.
199066014 M3UA office inaccessible.
2.Alarm reason: The signaling point of the CN-related office direction is inaccessible.
Check if there is any of the following transmission-related alarm. If yes, follow the corresponding
handling suggestions to handle it:
199066005 SCCP subsystem unavailable
199066010 MTP3 office inaccessible.
199066014 M3UA office inaccessible.
3.Alarm reason: Global reset operation is initiated by the NMS.
Check the operation log of the RNC NMS to see if there is any resetting. If yes, no handling is required.
3.132 199070003 Iu interface resource reset notification

0
l Description:Iu interface resource reset notification
l Severity:Minor
Probable Cause
RESET RESOURCE message is sent by RNC.
System Impact
The service that initiates resource reset is released.
3-81

Handling Suggestion
Check if transmission-related/board alarm occurs. If yes, refer to the corresponding alarm handling
suggestion.
Related alarms:
SCCP SSN is invalid
MTP3 office inaccessible
M3UA office inaccessible
3.133 199070004 RNC started Iu interface global reset

failure notification 0
l Description:RNC started Iu interface global reset failure notification
l Severity:Major
Probable Cause
RNC fails to receive reset response message from CN.
System Impact
Access of new service fails. Service access is restored to normal state in 3 seconds.
Handling Suggestion
On NMS configuration management interface (MSC SERVER/SGSN in transmission configuration),

check if the "MCC and MNC" configured by RNC and that configured by CN are consistent. If no,
modify configuration to keep consistency.
3.134 199070005 RNC started Iu interface resource

reset failure notification 0
l Description:RNC started Iu interface resource reset failure notification
l Severity:Major
3-82

Probable Cause
RNC fails to receive resource reset response message from CN.
System Impact
Handling Suggestion
On NMS configuration management interface (MSC SERVER/SGSN in transmission configuration),

check if the "MCC and MNC" configured by RNC and that configured by CN are consistent. If no,
modify configuration to keep consistency.
3.135 199070008 RNC and Node B CCPID configuration

are not identical 0
l Description:RNC and Node B CCPID configuration are not identical
l Severity:Major
Probable Cause
The CCP ID configured on the RNC side is different from that on the Node B side.
System Impact
Neither CCP ID will be available during service establishments.
Handling Suggestion
Click NE Information Configuration on the NMS Configuration Management interface. Select the
corresponding Node B and modify its CCP ID in Node B port configuration.
3.136 199070009 Broadcast fail 0

l Description:Broadcast fail
3-83

l Severity:Major
Probable Cause
1. Configuration related to the system broadcast information of the cell is incorrect.

2. Transmission is faulty
System Impact
The cell is unavailable. UE access to the cell fails, and all cell services are down.
Handling Suggestion
On NMS fault management interface, view notification Details where Alarm Reason is given. Locate
the specific handling suggestion according to the given reason.
The handling suggestions that correspond to the reasons are described below.
1.Alarm reason: Get system information from database failed.
View notification Details where "bySIBType" information is given. For example, "SIB type=1" indicates
fetching failure of Sib1. Check if the Sib1-related parameter configuration is correct and if the
configuration exists in the cell.
The mapping relationship between SIB type and the configuration required to be checked is listed
below.
1) SIB type=1
On NMS configuration management interface (UE timers and constants information), check UE
timers and counters in idle and connected status.
2) SIB type=2
On NMS configuration management interface (UTRAN cell), check URA ID in UTRAN cell global
information.
3) SIB type=3
On NMS configuration management interface (cell selection and reselection), check cell
selection/reselection information parameters and cell access limit parameters.
4) SIB type=5
On NMS configuration management interface (UTRAN cell), check common transport channel
parameters in SCCPCH and RACH.
2.Alarm reason: Exceed system broadcast ability.
The notification might be caused by transmission fault. Check if transmission-related alarm exists in
the Node B that the cell belongs to. If yes, refer to the corresponding alarm handling suggestion.
1) IP Mode
Check if related alarm exists according to the given association ID.
Related alarms:
199066018 Association congested
2) ATM Mode
a. Bottom layer transmission fault.
Check if related alarm exists.
Related alarms:
3-84

SDH/SONET fault
b. PVC unavailable.
Check if related alarm exists.
Related alarm: PVC Fault
3.137 199083025 Common Channel is abnormal 0

l Description:Common Channel is abnormal
l Severity:Major
Probable Cause
1. Use plane resource initialization fails.

2. Common channel establishment fails on Node B side.
3. Common channel configuration is deleted in NMS.
System Impact
Common Channel is unavailable, which falls into the following three cases.
1. If the SCCPCH carrying FACH is unavailable, UE-initiated CS/PS services will be down.
2. If the SCCPCH carrying PCH is unavailable, paging function will be unavailable in the system,
leading to failure of UE-initiated CS/PS services.
3. If the PRACH carrying RACH is unavailable, UE access to the cell will fail.
Handling Suggestion
On NMS alarm management interface, view notification Details where Alarm Reason is given. Locate
the specific handling suggestion according to the given reason.
The handling suggestions that correspond to different reasons are described below.
1.Alarm reason: User plane resource unit initialization fail.
1) On NMS configuration management interface (NE information configuration), select the relevant
Node B. Check the correctness of parameter configuration on path configuration interface. Check if
forwarding bandwidth is configured.
2). On NMS configuration management interface (path group configuration), view path group
configuration. Check the correctness of parameter configuration.
2.Alarm reason: CCH setup fail at NodeB side.
3-85

On NMS configuration management interface (BS ground resource management), view IP parameter
configuration in IP and route management. Ensure that at least one "COS" is selected.
3.Alarm reason: CCH delete by OMCR.
Automatic processing is performed by the system. Common channel deletion is initiated by RNC. No
handling is necessary
4. Others.
Common channel will be automatically reestablished by the system. No handling is necessary.
3.138 199083037 All Local Cell ID configured at RNC

side are differ from which on Node B side 0
l Description:All Local Cell ID configured at RNC side are differ from which on Node B
side
l Severity:Minor
Probable Cause
1. The RNC is connected with other Node B incorrectly, not the wanted Node B.
2. The radio resource data configured at RNC side and Node B side is inconsistent.
System Impact
All cell belong to the Node B can not be established.
Handling Suggestion
1、Check if the RNC is connected with Node B correctly on Iub interface. If not, please reconnect
RNC and Node B, and synchronize the configuration data to Node B.
2、Check if the radio resource data configured at RNC and Node B is consistent. If not, please
modify the radio resource data correctly, and synchronize the configuration data to RNC and Node B.
3.139 199083057 Excluded Neighbour Cells In

SysInfoBlock Notification 0
3-86

l Description:Excluded Neighbour Cells In SysInfoBlock Notification

l Severity:Minor
Probable Cause
The neighbour cells of the cell is too many.
System Impact
some neighbour cells are not broadcasted by SIB, and the cell re-selection procedure does not
work well.
Handling Suggestion
On NMS alarm management interface, view notification Details

The handling suggestions that correspond to different SibType are described below.
1.if the notification is related to SIB11, reduce the neighbour cells which are broadcasted in SIB11
2.if the notification is related to SIB11Bis, reduce the neighbour cells which are broadcasted in
SIB11Bis
3.if the notification is related to SIB12, reduce the neighbour cells which are broadcasted in SIB12
3.140 199105001 Failed to get the table of configuration

0
l Description:Failed to get the table of configuration
l Severity:Minor
Probable Cause
MicroCode subsystem failed to get the table of configuration from database subsystem during the
power on procedure, or failed to update the table of configuration.
3-87

System Impact
The system impacts that correspond to different alarm causes are described below.
1. Failed to get the information of the reassemble board.
The configuration information is used to reassemble the fragments of IP packets inputted into the
equipment. Lacking the configuration information may cause processing failure of fragments of IP
packets. Service interruption might occur or service processing rate might slow down.
2. Failed to get the configuration of OMCB server.
Lacking the configuration information may paralyze OMCB function.
3. Failed to get the configuration of signal dispatch table.
Lacking the configuration information causes SCTP data transmission failure on the interface board.
The service related to SCTP Protocol on this board is down.
4. Failed to get the configuration of IP/UDP.
Lacking the configuration information may cause processing failure of IUPS service, or processing
failure of other data based on IP transmission.
5. Failed to get the configuration of L2 table.
Lacking the configuration information may cause communication failure within the equipment. All
services on the board might be down.
6. Failed to get the configuration of path information.
In the case of ATM interface board, lacking the configuration information may incur processing failure
of the AAL2 data based on ATM Adaptation Layer Protocol, leading to interruption of IUB/IUCS/IUR
services under this office.
In the case of IP interface board, lacking the configuration information may incur processing failure of
IP packet traffic control, leading to interruption of all services under this office.
7. Failed to get the configuration of pathgroup information.
In the case of ATM interface board, lacking the configuration information may incur processing failure
of the AAL2 data based on ATM Adaptation Layer Protocol, leading to interruption of IUB/IUCS/IUR
services under this office.
In the case of IP interface board, service is not affected.
Handling Suggestion
The operator should add the configuration or re-synchronize the configuration according to the
addition information of this report.
3.141 199105002 The route table is overloaded 0

l Description:The route table is overloaded
l Severity:Minor
3-88

Probable Cause
There are too many configured route entries.The alarm is declared when the number of route entries
reaches 90% of the table capacity threshold.
System Impact
1.If the number of route entries does not exceed the RUB board route table capacity, service will
not be affected.
2.If the number of route entries exceeds the RUB board route table capacity, information of some
route entries will be lost.
1) If the missing route are the route to Node B or CN, UE service access to the board will fail.
2) If the missing route are the route to other RNC NE, access of Inter-RNC UE services to the board
will fail. Meanwhile, tick clock synchronization of the MBMS service between the relevant RNC NEs
will fail, degrading the MBMS service quality
3.If the number of route entries exceeds the RUB board route table capacity, the SLA diagnostic test
function from RNC to related NE will be disabled.
Handling Suggestion
1. On NMS configuration management interface (static route), delete the routes that are not in use.
2. On NMS configuration management interface (interface configuration), delete the port IP that is
no longer in use.
3.142 199105003 Failed to handle DHCP message from

other network 0
l Description:Failed to handle DHCP message from other network
l Severity:Minor
Probable Cause
Failed to assign DHCP Configuration to Client, may be one of the following causes:
1） OMCB Server Ip Configuration Absent
2) Peer Ip Address of PPP Link Absent
3） RNC Omcb Service Ip of Node Operation and Maintain Absent
4) Failed to Get Client DHCP Configuration from DBS
System Impact
DHCP Client can not get it's DHCP Configuration Information
3-89

Handling Suggestion
1) Check whether configed OMCB Server IP, if not, config it.

2) Check whether configed Peer IP of PPP/MLPPP Link, if not, config it.
3) Check whether configed RNC Omcb Service Ip of Node Operation and Maintain, if not, config it.
4) Check whether DHCP Configuration of Client is correct, if not, correct it.
3.143 199105004 Failed to operate multicast group 0

l Description:Failed to operate multicast group
l Severity:Minor
Probable Cause
Failed to join to Mulicast group of Link Trace
System Impact
Link Trace Function can not work
Handling Suggestion
contect with engneers of OSS
3.144 199105005 Clock difference of slave is large 0

l Description:Clock difference of slave is large
l Severity:Minor
Probable Cause
1. Clock Deviation between Slave and Host over threshold(default threshold 36sec/hr)
2. Clock crystal oscillator of Slave or Host is inaccurate
3-90

System Impact
KPI Index of Service in RNC will be low
Handling Suggestion
Block the Slave reported in the notification, and inform hardware manager
3.145 199105006 Slave losted external clock 0

l Description:Slave losted external clock
l Severity:Minor
Probable Cause
External Clock of Slave Lost
System Impact
KPI Index of Service in RNC will be low
Handling Suggestion
Block the Slave reported in the notification, and inform hardware manager
3.146 199105007 TCP connection on IuBC interface

establish failure 0
l Description:TCP connection on IuBC interface establish failure
l Severity:Minor
3-91

Probable Cause
1.The local IP address or remote IP address configuration is incorrect.

2.IP interface board of local equipment is faulty.
3.Intermediate equipment or opposite equipmentis faulty.
4.The network cable connection is loose or disconnected.
System Impact
The IuBC Broadcast is disabled.
Handling Suggestion
1.On NMS configuration management interface, check local IP address, remote IP address and TCP
connection mode. If the connection mode at local end is configured as client, the connection mode at
opposite end should be configured as server. Vice Versa.
2.On NMS configuration management interface, check protocol stack configuration at both ends. In
the case of direct connection, ensure that interface board addresses at both ends are in the same
network segment, and the next hop address is direct connect interface board address. In the case of
not direct connection, ensure that the next hop address is the intermediate equipment address.
3.Check the IP interface board for the Related Alarms. Perform the recommended solution to process
Related Alarms: 199066070 Board Offline or the CPU is in long period reset status
4.Telnet to the interface board. Set a destination IP and ping it. In the case of direct connection, ping
the direct connect interface board address. In the case of not direct connection, ping the intermediate
equipment. If response timeout, contact the equipment provider for solution.
5.Check the physical connection on IuBC interface. If the connection is loose or broken, unplug and
plug the cable or replace the cable. If port indicator is on, the physical link must be normal.
3.147 199105008 Bandwidth automatic adjustment is

useless 0
l Description:Bandwidth automatic adjustment is useless
l Severity:Minor
Probable Cause
Adjust the transmission path bandwidth to the low thehold can not radically improve packet loss
rate of this path.
3-92

System Impact
The packet loss rate higher than the reference value will depress the quality of service (QoS), even
lead to the access failure and service disconnection.
Handling Suggestion
Check the intermediate equipment between RNC and peer NE，make sure the intermediate
equipment runs normally .
3.148 199105009 No acknowledge of SLA query

request 0
l Description:No acknowledge of SLA query request
l Severity:Minor
Probable Cause
Not recived the SLA query request.
System Impact
IPBM can not recive the SLA acknowledge,the function of the band width adjust is useless.
Handling Suggestion
Check the state of interface board is normal,the PD query entity is exsit.
3.149 199105018 Unable to save Performance File 0

l Description:Unable to save Performance File
l Severity:Minor
3-93

Probable Cause
1. The disk space of OMP is less than 500M.

2. The communication link between OMM and OMP broken more than 2 hours.
3. The time of OMP adjusted.
System Impact
Either the LogService or the OMP cannot save the performance files. Performance data will be lost.
It has no impact on services.
Handling Suggestion
Check alarm details to find the Failure cause during saving performance file, and handle the alarm
accordingly.
1. If the Failure cause is "the space of OMP disk is less than 500M"Please delete unnecessary files
from the OMP disk to release enough space.
4. If the Failure cause is "The session ends abnormally and the performance file can not be saved", it
means the board time has been adjusted. In this case, no handling is required.
5. If the Failure cause is "PM files have already existed for over two hours.", the suggestion is given
for the alarm "199083028 Logservice is unavailable".
3.150 199105019 SLAVE memory check fail notification

0
l Description:SLAVE memory check fail notification
l Severity:Minor
Probable Cause
SLAVE memory check fail
System Impact
KPI Index of Service in RNC will be low.
Handling Suggestion
Reset the Slave reported in the notification.
3-94

3.151 199105020 TCP connect on IuBC interface is

interrupted 0
l Description:TCP connect on IuBC interface is interrupted
l Severity:Minor
Probable Cause
1.IP interface board of local equipment is faulty.

2.Intermediate equipment or opposite equipmentis faulty..
3.The network cable connection is loose or disconnected.
System Impact
The IuBC Broadcast is disabled.
Handling Suggestion
1.Check the IP interface board for the Related Alarms. Perform the recommended solution to process
Related Alarms: 198005379 Board Offline or the CPU is in long period reset status
2.TCheck the physical connection on IuBC interface. If the connection is loose or broken, unplug and
plug the cable or replace the cable. If port indicator is on, the physical link must be normal.
3.152 199105030 OMP received data is not complete 0

l Description:OMP received data is not complete
l Severity:Minor
Probable Cause
MP can not finish transfering data to OMP in five minutes.
System Impact
Performance file is not complete, the counter value is not accurate.
3-95

Handling Suggestion
Check communication status between CMP, DMP and OMP.
3.153 199105031 Transport path bandwidth modified

from far end 0
l Description:Transport path bandwidth modified from far end
l Severity:Minor
Probable Cause
NodeB detect the transport path bandwidth changed.
System Impact
If the bandwidth is lesser than configured bandwidth, lesser calls will be adopted in the relative
transport path.
Handling Suggestion
If the bandwidth of the inform is lesser than the configured bandwidth, it means that there is
something wrong with the transport path and it is more possible that fault is more possible at the
Nodeb side. If the bandwidth of the inform is equal to the configured bandwidth, it means the fault
has been recovered.
3.154 199105032 Transport Path Occupied BandWidth

Overload 0
l Description:Transport Path Occupied BandWidth Overload
l Severity:Minor
3-96

Probable Cause
Available bandWidth of transport path is less than occupied bandWidth. Probable causes for the
alarm include:
1.E1 link is broken.
2.Transmission quality of the transmission line is poor.
3.Intermediate equipment is faulty.
System Impact
The available bandwidth to destination is less than occupied bandwidth. Some services would be
released in this transport path selectively to avoid transport path congestion.
Handling Suggestion
1.Check the E1 link.

2.Check the transmission quality of intermediate equipment.
3.155 199105033 Transport Path group Occupied

Bandwidth Overload 0
l Description:Transport Path group Occupied Bandwidth Overload
l Severity:Minor
Probable Cause
Available bandwidth of transport path group is less than occupied bandwidth. Probable causes
for the alarm include:
1.E1 link is broken.
2.Transmission quality of the transmission line is poor.
3.Intermediate equipment is faulty.
System Impact
The available bandwidth to destination is less than occupied bandwidth.So service rate on this
path group will be degraded.
Handling Suggestion
1.Check the E1 link.

2.Check the transmission quality of intermediate equipment.
3-97

This page intentionally left blank.
3-98

Glossary
OMC
- Operation & Maintenance Center
- 操作维护中心

SJ-20120319104909-012-ZXUR 9000 UMTS (V4.11.20) Alarm and Notification Handling Reference

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SJ-20120319104909-012-ZXUR 9000 UMTS (V4.11.20) Alarm and Notification Handling Reference

Uploaded by

Copyright:

Available Formats

ZXUR 9000 UMTS

Radio Network Controller

Revision No. Revision Date Revision Reason

R1.1 2012–07–20 Second edition

R1.0 2012–05–18 First edition

Serial Number: SJ-20120319104909-012

Publishing Date: 2012-07-20（R1.1）

SJ-20120319104909-012|2012-07-20（R1.1） ZTE Proprietary and Confidential

Chapter 2 Alarm.......................................................................................... 2-1

SJ-20120319104909-012|2012-07-20（R1.1） ZTE Proprietary and Confidential

SJ-20120319104909-012|2012-07-20（R1.1） ZTE Proprietary and Confidential

SJ-20120319104909-012|2012-07-20（R1.1） ZTE Proprietary and Confidential

SJ-20120319104909-012|2012-07-20（R1.1） ZTE Proprietary and Confidential

SJ-20120319104909-012|2012-07-20（R1.1） ZTE Proprietary and Confidential

SJ-20120319104909-012|2012-07-20（R1.1） ZTE Proprietary and Confidential

SJ-20120319104909-012|2012-07-20（R1.1） ZTE Proprietary and Confidential

SJ-20120319104909-012|2012-07-20（R1.1） ZTE Proprietary and Confidential

Chapter 3 Notification ................................................................................ 3-1

SJ-20120319104909-012|2012-07-20（R1.1） ZTE Proprietary and Confidential

SJ-20120319104909-012|2012-07-20（R1.1） ZTE Proprietary and Confidential

SJ-20120319104909-012|2012-07-20（R1.1） ZTE Proprietary and Confidential

SJ-20120319104909-012|2012-07-20（R1.1） ZTE Proprietary and Confidential

SJ-20120319104909-012|2012-07-20（R1.1） ZTE Proprietary and Confidential

SJ-20120319104909-012|2012-07-20（R1.1） ZTE Proprietary and Confidential

What Is in This Manual

Chapter 2, Alarm Introduces the ZXUR 9000 UMTS alarms.

Chapter 3, Notification Introduces the ZXUR 9000 UMTS notifications.

SJ-20120319104909-012|2012-07-20（R1.1） ZTE Proprietary and Confidential

SJ-20120319104909-012|2012-07-20（R1.1） ZTE Proprietary and Confidential

1.1 Overview of Fault Management

1.2 Alarm Code

1.3 Alarm Type

l Equipment alarm: related with device hardware.

SJ-20120319104909-012|2012-07-20（R1.1） ZTE Proprietary and Confidential

1.4 Alarm Classification

Notification is mostly caused by sudden environment change or other accidental factors.

SJ-20120319104909-012|2012-07-20（R1.1） ZTE Proprietary and Confidential

1.6 Probable Cause

1.7 Handling Suggestion

Pay attention to the following tips when handling alarms.

1.8 Alarm Impact

SJ-20120319104909-012|2012-07-20（R1.1） ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20120319104909-012|2012-07-20（R1.1） ZTE Proprietary and Confidential

2.1 Equipment Alarm

OMCport's link is down.

OMC port can't transfer data.

1. If OMM is outside, please check OMC port's link if it is up.

SJ-20120319104909-012|2012-07-20（R1.1） ZTE Proprietary and Confidential

2.1.2 199000512 Trunk loss of frame 0

Trunk signal is broken

SJ-20120319104909-012|2012-07-20（R1.1） ZTE Proprietary and Confidential

2.1.3 199000513 Trunk loss of signal 0

Trunk signal is broken.

1. Check if E1 on DDF is connected and then check if the alarm is eliminated.

2.1.4 199000514 Trunk alarm indication signal 0

There is something wrong with upstream equipment.

Trunk signal is broken

SJ-20120319104909-012|2012-07-20（R1.1） ZTE Proprietary and Confidential

2.1.5 199000515 Trunk loss of CRC multi-frame 0

Multi-frame format is inconsistent.

Trunk signal is broken

2.1.6 199000517 Trunk remote alarm indication 0

SJ-20120319104909-012|2012-07-20（R1.1） ZTE Proprietary and Confidential