ZXUN iCX (MSCS)

MSC Server
Alarm Handling

Version: V4.12.10

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: [email protected]
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.0 2012-09-30 First edition

Serial Number: SJ-20120730093520-019

Publishing Date: 2012-09-30 (R1.0)

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Contents
About This Manual ......................................................................................... I
Chapter 1 Overview .................................................................................... 1-1
1.1 Alarm Management ............................................................................................ 1-1
1.2 Fault View.......................................................................................................... 1-1
1.3 Alarm ................................................................................................................ 1-2
1.4 Notification......................................................................................................... 1-3
1.5 Detailed Alarm Information.................................................................................. 1-4

Chapter 2 Alarm Messages Handling ....................................................... 2-1

2.1 1~9999 .............................................................................................................. 2-1
2.1.1 170 The Switch Board Occurred Loopback Port ......................................... 2-1
2.1.2 256 OMC Port's Link Is Down.................................................................... 2-1
2.1.3 512 Trunk Loss of Frame .......................................................................... 2-3
2.1.4 513 Trunk Loss of Signal .......................................................................... 2-4
2.1.5 514 Trunk Alarm Indication Signal ............................................................. 2-5
2.1.6 515 Trunk Loss of CRC Multi-Frame.......................................................... 2-5
2.1.7 517 Trunk Remote Alarm Indication........................................................... 2-6
2.1.8 518 Trunk Link Is Used for CSU Loopback Test.......................................... 2-7
2.1.9 1024 Cell Delineation Not Synchronized .................................................... 2-7
2.1.10 1025 Loss of Cell Delineation .................................................................. 2-8
2.1.11 1026 Cell Delineation Do Not Synchronization About Cell on E1/T1 Link ..... 2-9
2.1.12 1285 Clock Chip Is in Preheat Status..................................................... 2-10
2.1.13 1286 Input Clock of the Board Is Lost .................................................... 2-10
2.1.14 1792 SDH/SONET: Loss of Signal ..........................................................2-11
2.1.15 1793 SDH/SONET: Loss of Frame......................................................... 2-12
2.1.16 1794 SDH/SONET: Regenerator Section Trace Mismatch/Section Trace
Mismatch.............................................................................................. 2-12
2.1.17 1795 SDH/SONET:MS Alarm Indication Signal/Line Alarm Indication
Signal................................................................................................... 2-13
2.1.18 1796 SDH/SONET:MS Far-End Reception Failure/Line Far-End
Reception Failure.................................................................................. 2-14
2.1.19 1797 SDH/SONET: Signal Failure.......................................................... 2-14
2.1.20 1798 SDH/SONET: Signal Deterioration................................................. 2-15
2.1.21 1799 SDH/SONET:Loss of AU Pointer/Loss of Path Pointer .................... 2-16

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 2.1.22 1800 SDH/SONET:AU Alarm Indication Signal/Path Alarm Indication
Signal................................................................................................... 2-17
2.1.23 1801 SDH/SONET:HP Trace Mismatch/ Path Trace Mismatch................. 2-17
2.1.24 1802 SDH/SONET:HP Unequipped/Path Unequipped............................. 2-18
2.1.25 1803 SDH/SONET: HP Label Mismatch/Path Label Mismatch ................. 2-19
2.1.26 1804 SDH/SONET:HP Remote Reception Failure/Path Remote
Reception Failure.................................................................................. 2-19
2.1.27 1805 SDH/SONET: Loss of Multi-Frame................................................. 2-20
2.1.28 1806 SDH/SONET: Loss of TU Pointer/Loss of Virtual Tributary
Pointer ................................................................................................. 2-20
2.1.29 1807 SDH/SONET: Tributary Unit Alarm Indication Signal/Virtual
Tributary Alarm Indication Signal............................................................ 2-21
2.1.30 1808 SDH/SONET: LP Remote Defect Indication/Virtual Tributary
Remote Defect Indication ...................................................................... 2-21
2.1.31 1809 SDH/SONET:LP Remote Failure Indication/Virtual Tributary
Remote Failure Indication ...................................................................... 2-22
2.1.32 1810 SDH/SONET:LP Trace Mismatch/Virtual Tributary Trace
Mismatch.............................................................................................. 2-23
2.1.33 1811 SDH/SONET:LP Unequipped/Virtual Tributary Unequipped ............. 2-24
2.1.34 1812 SDH/SONET: LP Label Mismatch/Virtual Tributary Label
Mismatch.............................................................................................. 2-25
2.1.35 1816 SDH/SONET:Severely B1 Error Code............................................ 2-26
2.1.36 1817 SDH/SONET:Severely B2 Error Code............................................ 2-26
2.1.37 1818 SDH/SONET:Severely B3 Error Code............................................ 2-27
2.1.38 1819 SDH/SONET:Severely BIP-2 Error Code ....................................... 2-28
2.1.39 1820 SDH/SONET:MS Remote Error Indication...................................... 2-29
2.1.40 1821 SDH/SONET:HP Remote Error Indication ...................................... 2-30
2.1.41 1826 SDH/SONET:LP Remote Error Indication....................................... 2-30
2.1.42 2560 CPU Utilization Exceeds Alarm Limit ............................................. 2-31
2.1.43 2565 GPS Receiver Does Not Support the Work Mode Configuration ...... 2-33
2.1.44 3073 FLASH Device Initialize Failed ...................................................... 2-34
2.1.45 3584 Memory Lack Alarm ..................................................................... 2-34
2.1.46 3841 The Control Plane Retransfer Ratio Over the Threshold ................. 2-35
2.1.47 4357 The System Bureau Changed ....................................................... 2-35
2.1.48 5122 Loss of Active/Standby Communication Link .................................. 2-36
2.1.49 5123 The Configuration Is Not Supported .............................................. 2-37
2.1.50 5128 Rack or Shelf Conflict ................................................................... 2-37
2.1.51 5200 Board Configuration Information Is Not Compatible ........................ 2-38
2.1.52 5201 The Number of Logic CPU Is Out of Range.................................... 2-39

II

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 2.1.53 5382 Environment Monitor Board Communication Is Abnormal................ 2-39
2.1.54 5400 Configuration Conflicts Between OMP and CMM............................ 2-40
2.1.55 5405 Clock Board Phase-lock Loop Work Mode Is Abnormal .................. 2-41
2.1.56 5407 The Board Is Power Off ................................................................ 2-41
2.1.57 5632 The Hard Disk Used-Rate Is Over Threshold ................................. 2-42
2.1.58 5633 File System Is Abnormal............................................................... 2-43
2.1.59 5634 The Hard Disk on Board Gets IO Error .......................................... 2-43
2.1.60 5645 Subcard Is Abnormal.................................................................... 2-44
2.1.61 5666 Error Packets of MAC Is Higher Than the Specified Threshold ........ 2-45
2.1.62 5670 Oscillator Status Abnormal ........................................................... 2-45
2.1.63 5672 Clock Source for SyncE Is Not Available........................................ 2-46
2.1.64 5673 The Setting of the Dial Switch Is Changed ..................................... 2-46
2.1.65 5674 Sending or Receiving Packets Between Administration Port and
CPU Control Port Failed ........................................................................ 2-47
2.1.66 5760 Ethernet Port's Link Is Down ......................................................... 2-48
2.1.67 5761 The Speed Mode of Ethernet Port Doesn't Match With Settings ...... 2-49
2.1.68 5768 All of the Board Input Clocks Which Have the Same Frequency
Are Lost ............................................................................................... 2-49
2.1.69 5769 The Master and Slave Mode of Ethernet Port Doesn't Match With
Settings................................................................................................ 2-50
2.1.70 5770 The OMP Board Doesn't Have Any OMC Port................................ 2-51
2.1.71 5771 The Duplex Mode of Ethernet Port Doesn't Match With Settings...... 2-51
2.1.72 5772 Board Device Fault....................................................................... 2-52
2.1.73 5773 High CRC Error Rate at E1/T1 Bottom Layer ................................. 2-53
2.1.74 5774 High FAS Error Rate at E1/T1 Bottom Layer .................................. 2-53
2.1.75 5775 High EBIT Error Rate at E1 Bottom Layer ...................................... 2-54
2.1.76 5784 Please Reboot the Board After You Have Saved the New
Configuration to Make It Effective........................................................... 2-55
2.1.77 5785 GPS Module Is Abnormal ............................................................. 2-55
2.1.78 5786 Flash-Formatting Warning From USCC/GFC/XFC Subcard............. 2-56
2.1.79 5787 General Fault and Warning From USCC/GFC/XFC Subcard ........... 2-56
2.1.80 5788 Serious Fault and Warning From USCC/GFC/XFC Subcard............ 2-57
2.1.81 5789 Critical Fault and Warning From USCC/GFC/XFC Subcard............. 2-57
2.1.82 5790 The Configuration of Clock Shelf Function Is Error ......................... 2-58
2.1.83 5791 TX Power High Alarm ................................................................... 2-59
2.1.84 5792 TX Power Low Alarm.................................................................... 2-59
2.1.85 5793 RX Power High Alarm................................................................... 2-60
2.1.86 5794 RX Power Low Alarm ................................................................... 2-61

III

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 2.1.87 5795 The Optical Transceiver Transmitter Has Detected a Fault.............. 2-62
2.1.88 5796 Clock of This Board Is Abnormal ................................................... 2-62
2.1.89 5797 The Hard Disk Is Abnormal ........................................................... 2-63
2.1.90 5798 The Raid of Hard Disks Is Abnormal.............................................. 2-64
2.1.91 5799 Hard Disk Online.......................................................................... 2-65
2.1.92 5800 Hard Disk Offline.......................................................................... 2-65
2.1.93 5801 Memory Size Is Abnormal............................................................. 2-66
2.1.94 5908 Lack of Version ............................................................................ 2-66
2.1.95 5909 Download Version Failed .............................................................. 2-67
2.1.96 5910 Process Execute Failed ................................................................ 2-68
2.1.97 5930 Version Load Failed ..................................................................... 2-68
2.1.98 5932 The Third Party Firmware Version Load Failed............................... 2-69
2.1.99 5933 Shutdown Board to Valid the Third Party Firmware ......................... 2-69
2.1.100 7168 Port Trunk Failed........................................................................ 2-70
2.1.101 7169 Inner Port Error .......................................................................... 2-70
2.1.102 7170 Trunk Connect Asymmetry.......................................................... 2-71
2.1.103 7171 Outer Media Trunk Failed ........................................................... 2-72
2.1.104 7172 Port Physical State Restore ........................................................ 2-73
2.1.105 7173 Control panel port down.............................................................. 2-73
2.1.106 7174 Connect Port Loopback .............................................................. 2-74
2.2 10000~99999................................................................................................... 2-74
2.2.1 18944 The State of PVC Link Is Faulty .................................................... 2-74
2.2.2 19207 Fail to Configure Near-End IMA Group .......................................... 2-76
2.2.3 19208 Fail to Fix the Time of Near-End IMA Group................................... 2-77
2.2.4 19212 Near-End Transmitting Link Is Broken ........................................... 2-77
2.2.5 19213 Near-End Receives the LIF Alarm of the Link................................. 2-78
2.2.6 19214 Near-End Receives the LODS Alarm of the Link............................. 2-79
2.2.7 19215 Near-End Receives the RDI Alarm of the Link ................................ 2-80
2.2.8 19216 Near-End Receives the Alarm That the Link Is in Trouble ............... 2-81
2.2.9 19218 Near-End Receives the Alarm That the Link Is Broken.................... 2-81
2.2.10 19223 Near-End IMA Group Has Faults ................................................. 2-82
2.2.11 19712 APS Channel Mismatch .............................................................. 2-83
2.2.12 19713 APS Mode Mismatch .................................................................. 2-84
2.2.13 19715 APS Channel Between Master and Slave Board Becomes
Errors................................................................................................... 2-85
2.2.14 19971 Request Gateway Information Timeout ........................................ 2-86
2.2.15 20225 Protocol Stack Requests for Configuration Information Timeout ..... 2-86

IV

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 2.2.16 23042 The Number of Physical Alarms on the Board Exceeds the
Threshold ............................................................................................. 2-87
2.2.17 23050 Fan Device Absent ..................................................................... 2-88
2.2.18 23051 Power Unit Absent ..................................................................... 2-88
2.2.19 23106 Board Initialized Test Failed ........................................................ 2-89
2.2.20 25600 Connection Check Be Disabled in Board...................................... 2-90
2.2.21 25602 Abnormal Half-Fixed Connection Changes................................... 2-90
2.2.22 25856 Rack Temperature Is Higher Than High Threshold........................ 2-91
2.2.23 25857 Rack Temperature Is Lower Than Low Threshold ......................... 2-92
2.2.24 25858 Room Temperature Is Higher Than High Threshold ...................... 2-92
2.2.25 25859 Room Temperature Is Lower Than Low Threshold........................ 2-93
2.2.26 25860 Voltage Is Higher Than High Threshold........................................ 2-94
2.2.27 25861 Voltage Is Lower Than Low Threshold ......................................... 2-95
2.2.28 25862 Humidity Is Higher Than High Threshold...................................... 2-95
2.2.29 25863 Humidity Is Lower Than Low Threshold ....................................... 2-96
2.2.30 25864 Fault in Fan Plug-in Box.............................................................. 2-97
2.2.31 25865 Rack Door Access Control Alarm or Other Monitor Alarm.............. 2-98
2.2.32 25866 Smoke Alarm ............................................................................. 2-98
2.2.33 25867 Infrared Alarm ............................................................................ 2-99
2.2.34 25868 Lightning Alarm .........................................................................2-100
2.2.35 25869 Power Switch Alarm ..................................................................2-100
2.2.36 25870 Power Type Configured Does Not Accord With Physical ..............2-101
2.2.37 25871 Communication Abnormal Between the Shelf Management
Board and Switch Board in the Same Shelf............................................2-101
2.2.38 26127 Clock Reference Source Lost (Level 3 Alarm) .............................2-102
2.2.39 26128 Clock Reference Source Lost (Level 2 Alarm) .............................2-103
2.2.40 26129 Clock Reference Source Lost (Level 1 Alarm) .............................2-104
2.2.41 26133 Output Clock of the Board Is Lost ...............................................2-105
2.2.42 29184 SNTP Failed to Synchronize Time ..............................................2-105
2.2.43 29952 Ethernet Link Fault Alarm ..........................................................2-106
2.2.44 29953 The Ethernet Port Is in the OAM Loopback State.........................2-107
2.2.45 30208 CFM Fault.................................................................................2-108
2.2.46 30721 Temperature Is Lower Than Lower-Non-Critical Threshold ........... 2-110
2.2.47 30722 Temperature Is Lower Than Lower-Critical Threshold .................. 2-111
2.2.48 30723 Temperature Is Lower Than Lower-Non-Recoverable
Threshold ............................................................................................ 2-112
2.2.49 30724 Temperature Is Higher Than Upper-Non-Critical Threshold .......... 2-112
2.2.50 30725 Temperature Is Higher Than Upper-Critical Threshold.................. 2-113

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 2.2.51 30726 Temperature Is Higher Than Upper-Non-Recoverable
Threshold ............................................................................................ 2-114
2.2.52 30727 Voltage Is Lower Than Lower-Non-Critical Threshold................... 2-114
2.2.53 30728 Voltage Is Lower Than Lower-Critical Threshold .......................... 2-115
2.2.54 30729 Voltage Is Lower Than Lower-Non-Recoverable Threshold .......... 2-116
2.2.55 30730 Voltage Is Higher Than Upper-Non-Critical Threshold .................. 2-116
2.2.56 30731 Voltage Is Higher Than Upper-Critical Threshold ......................... 2-117
2.2.57 30732 Voltage Is Higher Than Upper-Non-Recoverable Threshold ......... 2-117
2.2.58 30734 Velocity of Fan Is Lower Than Lower-Critical Threshold ............... 2-118
2.2.59 30735 Filter Tray Is Present for Too Long (Non-Recoverable)................. 2-119
2.2.60 30736 Filter Tray Is Present for Too Long (Critical) ................................ 2-119
2.2.61 30737 Filter Tray Is Present for Too Long (Non-Critical) .........................2-120
2.2.62 30738 State Is Abnormal......................................................................2-120
2.2.63 30739 Current Is Lower Than Lower-Non-Critical Threshold...................2-121
2.2.64 30740 Current Is Lower Than Lower-Critical Threshold ..........................2-121
2.2.65 30741 Current Is Lower Than Lower-Non-Recoverable Threshold ..........2-122
2.2.66 30742 Current Is Higher Than Upper-Non-Critical Threshold ..................2-122
2.2.67 30743 Current Is Higher Than Upper-Critical Threshold .........................2-123
2.2.68 30744 Current Is Higher Than Upper-Non-Recoverable Threshold .........2-123
2.2.69 30745 Velocity of Fan Is Lower Than Lower-Non-Critical Threshold ........2-124
2.2.70 30746 Velocity of Fan Is Lower Than Lower-Non-Recoverable
Threshold ............................................................................................2-124
2.2.71 30747 Module/Board Device Absent .....................................................2-125
2.2.72 30748 Power On Failed Due to S5 .......................................................2-126
2.2.73 30749 Difference Between Ambient and Outlet Sensor Exceeded
Limit....................................................................................................2-126
2.2.74 30750 RAID1 Degradation Detected .....................................................2-127
2.2.75 30751 MCElog Detected ......................................................................2-128
2.2.76 30752 RAID1 Degradation Detected .....................................................2-128
2.2.77 30753 FC Controller Unavailable ..........................................................2-129
2.2.78 30754 FC Port Continuous Up-down Status Detected ............................2-129
2.2.79 30808 Processor Internal Error.............................................................2-130
2.2.80 30809 Processor Thermal Trip .............................................................2-131
2.2.81 41737 Near-End TC Link Fault .............................................................2-131
2.3 1000000~9999999 ..........................................................................................2-132
2.3.1 8392706 Time Synchronization Over Alarm Limit.....................................2-132
2.3.2 8392707 Request SNTP Time Failed......................................................2-133
2.3.3 8392708 Time Synchronization Over Alarm Limit in RPU Access Type ......2-134

VI

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 2.3.4 8393985 Control Plane Communication Abnormal Between Board and
Its Home Module..................................................................................2-134
2.3.5 8393986 Control Plane Communication Is Abnormal Between This Board
and the Active Independent Board ........................................................2-135
2.3.6 8393987 Board Off Line.........................................................................2-136
2.3.7 8393988 Control Plane Communication Abnormal Between MP and
OMP ...................................................................................................2-137
2.3.8 8398848 SCCP Subsystem Unavailable .................................................2-138
2.3.9 8399104 Broadband Link Congestion .....................................................2-139
2.3.10 8399105 Broadband Link Overload.......................................................2-140
2.3.11 8399616 LAPD Link Break ...................................................................2-141
2.3.12 8399872 MTP2 Link Sent Load Overloaded ..........................................2-142
2.3.13 8399873 MTP2 Link Received Load Overloaded ...................................2-143
2.3.14 8400128 MTP3 Office Inaccessible.......................................................2-144
2.3.15 8400129 MTP3 Link Unavailable ..........................................................2-145
2.3.16 8400130 MTP3 Cluster Inaccessible.....................................................2-147
2.3.17 8400131 MTP3 Link Congestion...........................................................2-147
2.3.18 8400132 MTP3 Link Sent Flow Control Alarm .......................................2-148
2.3.19 8400384 M3UA Office Inaccessible ......................................................2-149
2.3.20 8401152 SUA Subsystem Unavailable ..................................................2-150
2.3.21 8401153 SUA Office Inaccessible .........................................................2-151
2.3.22 8402688 Association Congested ..........................................................2-153
2.3.23 8402690 Association Broken ................................................................2-154
2.3.24 8402944 STC Office Inaccessible .........................................................2-157
2.3.25 8402945 STC Office Congested ...........................................................2-157
2.3.26 8403456 Number of Signaling Message Transferring Exceeds Allowed
Threshold of the License ......................................................................2-158
2.3.27 8406528 The Protocol State of Port-Channel Interface Is Down..............2-159
2.3.28 8406529 The Protocol State of Supervlan Interface Is Down ..................2-159
2.3.29 8407043 PPP Link Is Down..................................................................2-160
2.3.30 8407298 The Configuration of BSCIP in Database Is Wrong ..................2-162
2.3.31 8411392 BFD Session Interruption .......................................................2-162
2.3.32 8411393 BFD Session Negotiation Failure ............................................2-163
2.3.33 8411649 The Number of Alarms on the Manager Board Exceeds the
Threshold ............................................................................................2-164
2.3.34 8411651 The Number of Logical Alarms on the Board Exceeds the
Threshold ............................................................................................2-165
2.3.35 8412416 Fail to Load XML Script Files..................................................2-165

VII

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 2.3.36 8417537 Association Path Broken ........................................................2-166
2.3.37 8419073 Bearer Network Is Unavailable ...............................................2-167
2.3.38 8419074 Bearer Network Get Worse ....................................................2-168
2.3.39 8419840 PTP Failed to Get Clock Attribute ...........................................2-169
2.3.40 8429568 Broadband Link Unavailable...................................................2-170
2.4 10000000~99999999.......................................................................................2-171
2.4.1 25167105 Alarm of Server Disconnected With MGW ...............................2-171
2.4.2 25167106 MGW Is Out of Service ..........................................................2-171
2.4.3 25167872 D-Channel Signal Link Is Broken ............................................2-172
2.4.4 25170946 ENUM/DNS BYPASS Is Evoked by Manual.............................2-173
2.4.5 25170947 ENUM/DNS BYPASS Is Evoked by System Automatically........2-173
2.4.6 25171456 SIP Office Is Unreachable ......................................................2-174
2.4.7 25171458 SIP Node Switch ...................................................................2-175
2.4.8 25172481 System Now Is in IP Congestion Situation ...............................2-175
2.4.9 25172482 IPQos Test Calls During a Period All Failed .............................2-176
2.4.10 25172992 System Dynamic Recovery Monitor Index Abnormity .............2-177
2.4.11 25173248 LIG TCP Link Is Broken........................................................2-177
2.4.12 25173249 LIG TCP Link Initiation Failed ...............................................2-178
2.4.13 33560234 Down Link Between NE and CU ...........................................2-178
2.4.14 33560235 Generate Backlog CDR File .................................................2-179
2.4.15 33560236 Read or Write Backlog CDR Files Failed ...............................2-180
2.4.16 33560237 The Free Space of MP for CDR Is Less Than 50M.................2-180
2.4.17 33560238 The Free Space of MP for CDR Is Less Than 100M...............2-181
2.4.18 33560239 The Free Space of MP for CDR Is Less Than 200M...............2-182
2.4.19 33560240 The Backlog CDR File Is Over 600M.....................................2-183
2.4.20 33560241 The Backlog CDR File Is Over 1.2G......................................2-184
2.4.21 33560242 Generate Backlog ACR File..................................................2-184
2.4.22 33560243 Read ACR File Failed in OCG ..............................................2-186
2.4.23 33560244 The Free Space for ACR Is Less Than 50M in OCG ..............2-186
2.4.24 33560245 The Free Space for ACR Is Less Than 100M in OCG.............2-188
2.4.25 33560246 The Free Space for ACR Is Less Than 200M in OCG.............2-189
2.4.26 33560247 The Backlog ACR File in the OCG Is Over 600M ...................2-190
2.4.27 33560248 The Backlog ACR File in the OCG Is Over 1.2G ....................2-191
2.4.28 33560249 Buffer of CDR Is Full ............................................................2-193
2.4.29 33560252 Type of Received CDR Is Not Identified.................................2-193
2.4.30 33560253 Length of Received CDR Is Not Correct ................................2-194
2.4.31 33560254 CCF Is in Bypass Situation ...................................................2-194

VIII

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 2.4.32 33560255 CCF Failure.........................................................................2-195
2.4.33 33575140 CIC Resource Is Insufficient .................................................2-195
2.4.34 33575153 Delete CIC Which Is Connected With MTL ............................2-196
2.4.35 33575171 Inter-Switch TDM Circuit on MGW Controlled by MSC Server
Link Broken .........................................................................................2-197
2.4.36 33575172 TDM Circuit Between MGWs Controlled by MSC Server Link
Broken ................................................................................................2-198
2.4.37 33575173 The Usage of DB Table Space Exceeds the Limit Value .........2-198
2.4.38 33575174 MSRN in Common Module Usage Exceeds the Pre-Defined
Limit....................................................................................................2-200
2.4.39 33575175 MSRN Usage Exceeds the Pre-Defined Limit ........................2-201
2.4.40 33575176 HONUM Usage Exceeds the Pre-Defined Limit .....................2-201
2.4.41 33575177 CPU Load Too High in MGW ................................................2-202
2.4.42 33575178 RTP Load Too High in MGW.................................................2-203
2.4.43 33575179 Table Related to ALS Is Full .................................................2-203
2.4.44 33575463 MSCS Service Overload ......................................................2-204
2.4.45 33575466 CMP Overload.....................................................................2-205
2.4.46 33576632 The Heartbeat of Dualhome Is Down ....................................2-207
2.4.47 33576634 Exceptions Occurred When Two MSCS of Dualhome Are
Master.................................................................................................2-208
2.4.48 33576635 Exceptions Occurred When Two MSCS of Dualhome Are
Slave ..................................................................................................2-209
2.4.49 33576636 The Usage of Data Area Exceeds the Pre-Defined Limit.........2-209
2.4.50 33576664 The Alarm of Paging Congestion ..........................................2-210
2.4.51 33576665 Links of Office Is in Congest .................................................2-210
2.4.52 33576669 Abnormal Heartbeat Detected Between MSC Pool User Data
Synchronization Peers ......................................................................... 2-211
2.4.53 33576670 The Number of MGW Registered Is Inconsistent With
Configure ............................................................................................2-212
2.4.54 33576671 MSCS Act as Slave When Power On ....................................2-213
2.4.55 33576672 Dualhome Work Role Is Conflicting .......................................2-214
2.4.56 33576673 The Number of MGW in Service Is Conflict in Domain............2-215
2.4.57 33576675 Congestion Detected Between MSC Pool User Data
Synchronization Peers .........................................................................2-216
2.4.58 33576900 More Than 90% DEP Dialogs Is Used...................................2-216
2.4.59 33576901 DEP Process Register Failed ...............................................2-217
2.4.60 33576903 DEP Dialog Resource Is Exhausted ......................................2-219
2.4.61 33576904 DEP Transaction Resource Is Exhausted ..............................2-219
2.4.62 33576905 DAP Get Config Data of Link Fail..........................................2-220

IX

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 2.4.63 33576906 DAP Process Register Failed ...............................................2-221
2.4.64 33576907 Diameter Link Broken ..........................................................2-223
2.4.65 33576909 GREG Get Configuration Data Fail .......................................2-224
2.4.66 33576912 LREG Failed to Access Basic Data .......................................2-225
2.4.67 33576913 Initiation of UB Pool Failed ...................................................2-226
2.4.68 33577432 SIP Config Error ..................................................................2-227
2.4.69 33577433 SIP Insufficient Memory .......................................................2-227
2.4.70 33577434 SIP Socket Init Fail ..............................................................2-228
2.4.71 33577435 SIP Link Broken...................................................................2-229
2.4.72 33577532 License Alert .......................................................................2-230
2.4.73 33610283 Media IP Address of BSC Can't Be Connected ......................2-230
2.5 1000000000~9999999999 ...............................................................................2-231
2.5.1 2013659137 License File Is Inconsistent With Database Backup..............2-231
2.5.2 2365980673 Performance QoS Critical Alarm .........................................2-231
2.5.3 2365980674 Performance QoS Major Alarm ...........................................2-232
2.5.4 2365980675 Performance QoS Common Alarm ......................................2-233
2.5.5 2365980676 Performance QoS Warning Alarm .......................................2-234
2.5.6 2365980929 Internal Controlled Account Number and Password Will
Expire Soon.........................................................................................2-235
2.5.7 2365980930 Internal Controlled Account Number and Password Already
Expired................................................................................................2-237
2.5.8 2365980931 Internal Controlled Account Number and Password Do Not
Meet Requirements..............................................................................2-238
2.5.9 2365980932 3 Consecutive Wrong Passwords During Login....................2-239
2.5.10 2365980934 Interface Inner Control Account Password Will Expire
Soon ...................................................................................................2-240
2.5.11 2365980935 Interface Inner Control Account Password Already
Expired................................................................................................2-241
2.5.12 2365980936 Interface Inner Control Account Password Do Not Meet
Requirements ......................................................................................2-242
2.5.13 2365981185 OMM CPU Usage Rate Exceeds Criterion .........................2-243
2.5.14 2365981186 OMM Memory Usage Rate Exceeds Criterion ....................2-245
2.5.15 2365981187 OMM Hard Disk Usage Rate Exceeds Criterion(Level 1
Alarm) .................................................................................................2-247
2.5.16 2365981188 OMM Hard Disk Usage Rate Exceeds Criterion(Level 2
Alarm) .................................................................................................2-248
2.5.17 2365981189 OMM Hard Disk Usage Rate Exceeds Criterion(Level 3
Alarm) .................................................................................................2-250

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 2.5.18 2365981190 OMM Hard Disk Usage Rate Exceeds Criterion(Level 4
Alarm) .................................................................................................2-252
2.5.19 2365981191 Directory Usage Rate Exceeds Criterion (Level 1
Alarm) .................................................................................................2-253
2.5.20 2365981192 Directory Usage Rate Exceeds Criterion (Level 2
Alarm) .................................................................................................2-255
2.5.21 2365981193 Directory Usage Rate Exceeds Criterion (Level 3
Alarm) .................................................................................................2-256
2.5.22 2365981194 Directory Usage Rate Exceeds Criterion (Level 4
Alarm) .................................................................................................2-257
2.5.23 2365981441 License File Illegal ...........................................................2-259
2.5.24 2365981443 License File Unavailable...................................................2-259
2.5.25 2365981444 Multiple License Files Exist...............................................2-260
2.5.26 2365981445 Loaded License File Expires .............................................2-260
2.5.27 2365981697 Link Broken Between NE and OMM ..................................2-261
2.5.28 2365981698 Link Broken Between Alarm Box and OMM .......................2-261
2.5.29 2365981699 OMM Changeover Success ..............................................2-262
2.5.30 2365981700 Link Broken Between Independent Board and OMM ..........2-263
2.5.31 2365981703 SNMP Configuration Inconsistent With Independent
Board ..................................................................................................2-264
2.5.32 2365981953 Link Broken Between NTP Server and OMM .....................2-265
2.5.33 2365981954 Time of NTP Server Unsynchronized.................................2-265
2.5.34 2365981955 NTP Clock Offset Over Maximum Threshold ......................2-266
2.5.35 2365982209 Automatic Backup Failed ..................................................2-267

Chapter 3 Notification Message Handling................................................ 3-1

3.1 1~9999 .............................................................................................................. 3-1
3.1.1 31 Power On Failed Inform ....................................................................... 3-1
3.1.2 576 Trunk Slip.......................................................................................... 3-2
3.1.3 834 MCC Is Abnormal .............................................................................. 3-2
3.1.4 1600 CPU Resets on a Board in the Same Shelf ........................................ 3-3
3.1.5 2625 There Is a Dead Lock in Process ...................................................... 3-3
3.1.6 2880 CPU Dead-Loop .............................................................................. 3-4
3.1.7 3136 Disk Is Full ...................................................................................... 3-4
3.1.8 3137 File Operation Is Fail ........................................................................ 3-5
3.1.9 3392 Timer Resource Is Deficient.............................................................. 3-6
3.1.10 3393 Predefine Timer Is Not Config or Is Config But Not Restart the
Board ..................................................................................................... 3-6
3.1.11 3648 Ub Is Deficient ............................................................................... 3-7

XI

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 3.1.12 3649 Sblock Is Deficient.......................................................................... 3-7
3.1.13 3904 Communication Buffer Is Full .......................................................... 3-8
3.1.14 3905 Convert Function Is Registered Repeated........................................ 3-8
3.1.15 3907 Write CMM's CDM Failed ............................................................... 3-9
3.1.16 3909 The CDM's Configuration About Net Address Is Invalid..................... 3-9
3.1.17 4417 Exception Information................................................................... 3-10
3.1.18 4418 Logic CPU Is Power on Successfully ..............................................3-11
3.1.19 4419 Logic CPU Is Power on Failed .......................................................3-11
3.1.20 5189 Board Change Over Notice ........................................................... 3-12
3.1.21 5192 Board's Working Mode Unsupported ............................................. 3-12
3.1.22 5193 Notification of Board's Power-on Status ......................................... 3-13
3.1.23 5448 Environment Parameters Set Fail.................................................. 3-14
3.1.24 5715 PP2S Source Has Switched.......................................................... 3-15
3.1.25 5718 Two Master Clock Ports Is Directly Connected ............................... 3-15
3.1.26 5720 The CDM Data Was Covered........................................................ 3-16
3.1.27 5762 The Board Is Selecting Clock Base ............................................... 3-16
3.1.28 5763 There Is No Valid Reference of the Clock Board to Be Selected ...... 3-17
3.1.29 5764 Lock Timeout When Manual Selecting Clock Reference ................. 3-17
3.1.30 5765 Lock the Wrong Base When Manual Selecting Clock Reference ..... 3-18
3.1.31 5766 Lock the Right Base When Manual Selecting Clock Reference ....... 3-19
3.1.32 5767 The Manual Selecting Reference Command Is Useless Because
the Clock Board Is in Preheat Status ...................................................... 3-19
3.1.33 5976 Download Version Failed .............................................................. 3-20
3.1.34 5977 Running Version Not Match With Database Configuration............... 3-21
3.1.35 5978 Boottype Different With Configure ................................................. 3-22
3.1.36 5979 Execute Version File Failed........................................................... 3-23
3.1.37 5980 Match Version Failed.................................................................... 3-23
3.1.38 5981 Special Firmware Version Load Information ................................... 3-24
3.1.39 5982 Patch Operation Failed ................................................................. 3-25
3.1.40 5983 Write Back Version Information ..................................................... 3-25
3.1.41 5984 Check Version Information............................................................ 3-26
3.1.42 5985 Synchronize Version Information ................................................... 3-26
3.1.43 6720 Notice of Power-on Status of C51 Board/ Board Soft Reset ............ 3-27
3.1.44 7492 The Master OMP Power On.......................................................... 3-27
3.1.45 8000 Loading Data Failed ..................................................................... 3-28
3.1.46 8007 Saving Database Files(.zdb) Failed ............................................... 3-28
3.1.47 8512 Sync Failed From Master to Slave................................................. 3-29
3.1.48 8769 Sync Failed Between CPU............................................................ 3-30

XII

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 3.1.49 8770 Loading Data Failed After Sync..................................................... 3-31
3.1.50 8771 Sync Failed by FTP ...................................................................... 3-32
3.1.51 9024 Configuration Change Notification Failed ....................................... 3-32
3.2 10000~99999................................................................................................... 3-33
3.2.1 10048 Insufficient Memory ...................................................................... 3-33
3.2.2 10049 DLL Registration Failed ................................................................ 3-33
3.2.3 10050 Get Lock Timeout......................................................................... 3-34
3.2.4 10051 Transaction Commit Timeout ........................................................ 3-34
3.2.5 10304 SCCP GT Translation Is Failed ..................................................... 3-35
3.2.6 10305 NID Is Not Configured .................................................................. 3-35
3.2.7 10306 NID Translation Is Failed .............................................................. 3-36
3.2.8 10307 The ISNI Constrained Route Information Is Repeated..................... 3-36
3.2.9 10308 ISNI Does Not Support This Route Function .................................. 3-37
3.2.10 10309 Fail to Prompt NID Route ............................................................ 3-37
3.2.11 10310 Wrong Message Type Use ISNI Function ..................................... 3-38
3.2.12 11072 LAPD Alarm Information ............................................................. 3-38
3.2.13 11073 LAPD Initial HDLC Failed ............................................................ 3-39
3.2.14 11330 Fail to Obtain Configuration Information From the Database or
Fail to Register Configuration Changing Notify ........................................ 3-40
3.2.15 11331 Fail to Initialize MTP2 ................................................................. 3-40
3.2.16 11332 Fail to Add or Delete HDLC Channel............................................ 3-41
3.2.17 11333 MTP2 Initial HDLC Failed............................................................ 3-41
3.2.18 11584 MTP3 Link State Is Offline........................................................... 3-42
3.2.19 11840 M3UA User Office Status Change................................................ 3-43
3.2.20 12096 Fail to Get the Functional Configuration ....................................... 3-43
3.2.21 12097 The File of Sig Config Updated ................................................... 3-44
3.2.22 12352 Fail to Allocate Memory .............................................................. 3-44
3.2.23 12353 SIG Failed to Save Configuration ................................................ 3-45
3.2.24 12609 SUA ASBuf Application Failure ................................................... 3-45
3.2.25 13632 M2PA Link Congestion ............................................................... 3-46
3.2.26 13633 M2PA Processor Outage ............................................................ 3-47
3.2.27 13634 M2PA Link Buffer Allocate Fail .................................................... 3-47
3.2.28 13888 ASP Status Changed.................................................................. 3-48
3.2.29 13889 AS Status Changed.................................................................... 3-49
3.2.30 13890 Sigtran Error Message Received ................................................. 3-50
3.2.31 13891 Sigtran Notification Message Received........................................ 3-52
3.2.32 14144 Association Establishment Failure ............................................... 3-53
3.2.33 14145 Restart the Association............................................................... 3-54

XIII

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 3.2.34 14146 Dynamic Association Link Broken................................................ 3-55
3.2.35 14148 One User of Share Association Is in Service ................................ 3-55
3.2.36 14149 One User of Share Association Is Out of Service.......................... 3-56
3.2.37 14150 Association Config Error ............................................................. 3-56
3.2.38 14151 SSM Malloc Memory Failure ....................................................... 3-57
3.2.39 14152 Dynamic Association Config Error ............................................... 3-58
3.2.40 17990 RPU Detected Board Down......................................................... 3-59
3.2.41 17992 Protocol State of the Port-Channel Member Interface Is Down ...... 3-59
3.2.42 18240 TCP RST Packets Received ....................................................... 3-60
3.2.43 18241 TCP Connection Closed ............................................................. 3-61
3.2.44 18242 Failed to Verify MD5 ................................................................... 3-62
3.2.45 18243 MD5 Message Error ................................................................... 3-62
3.2.46 18244 Socket Receive Buffer Occupancy Exceeded Threshold ............... 3-63
3.2.47 18245 Data in Socket Buffer Can Not Be Sent or Received in 120
Seconds ............................................................................................... 3-63
3.2.48 18500 The Peer IP Address Is the Same as the Local IP Address of the
PPP Link .............................................................................................. 3-64
3.2.49 18501 Fail to Create the HDLC Channel ................................................ 3-65
3.2.50 18502 Fail to Initialize the HDLC Chip.................................................... 3-66
3.2.51 18503 Fail to Create the Queue or Thread of PPP .................................. 3-67
3.2.52 18504 The HDLC Channel Is Created Successfully ................................ 3-68
3.2.53 18753 The Configuration of UID/HDLC/IPE1 in Database Is Wrong ......... 3-68
3.2.54 18755 HDLC Status Changed ............................................................... 3-69
3.2.55 19008 Fail to Configure the ATM Port .................................................... 3-70
3.2.56 19264 Fail to Operate IMA Group .......................................................... 3-71
3.2.57 19265 Fail to Operate the Link of the IMA Group .................................... 3-72
3.2.58 19777 APS Switchover Happens ........................................................... 3-73
3.2.59 20554 Failed to Add the Route .............................................................. 3-73
3.2.60 20571 Failed to Perform Offline Configuration ........................................ 3-74
3.2.61 20802 There Is an IP Address Conflict With Another System on the
Subnet ................................................................................................. 3-75
3.2.62 20803 There Is a MAC Address Conflict With Another System on the
Subnet ................................................................................................. 3-75
3.2.63 20805 ARP Detecting Failed ................................................................. 3-76
3.2.64 20806 ARP Detecting Reply Is Different From Static ARP ....................... 3-77
3.2.65 21059 RIP Neighbor Configuration Error ................................................ 3-78
3.2.66 21060 RIP Interface Authentication Error ............................................... 3-78
3.2.67 21065 Incompatible RIP Version Number ............................................... 3-79

XIV

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 3.2.68 21329 LSDB Overflow .......................................................................... 3-80
3.2.69 21330 Configuration of OSPF Mismatched............................................. 3-80
3.2.70 21573 BGP Gets TCB Fail on Active Connection.................................... 3-81
3.2.71 21584 Neighbor Hold Timer Expired ...................................................... 3-81
3.2.72 21585 BGP Interface Down and Neighbor Link Broken ........................... 3-82
3.2.73 21837 Fail to Add Dynamic Route ......................................................... 3-83
3.2.74 22336 MAC Addresses Conflict Among the Ports of the Office ................ 3-84
3.2.75 22593 ISIS Hello Message Authentication Failure................................... 3-84
3.2.76 22594 ISIS LSP Message Authentication Failure .................................... 3-85
3.2.77 22595 ISIS SNP Message Authentication Failure ................................... 3-86
3.2.78 22597 Abnormal Message Is Received .................................................. 3-87
3.2.79 22598 Routers With Conflicting System ID Exist in Network .................... 3-88
3.2.80 26176 The Currently Locked Reference of the Clock Board Has Been
Changed .............................................................................................. 3-89
3.2.81 26178 Clock Work Mode Is Changed ..................................................... 3-89
3.2.82 28231 Router ID Not Configured for OSPFv3 ......................................... 3-90
3.2.83 28233 Configuration of OSPFv3 Mismatched ......................................... 3-90
3.2.84 28993 Setting SCTP Primary Path Failed............................................... 3-91
3.2.85 28994 A Switchover Is Made From One SCTP Link to Another................ 3-92
3.2.86 28998 SCTP Congested for a Long Time ............................................... 3-92
3.2.87 28999 The Number of Static Associations in One Module Are Out of
Range .................................................................................................. 3-93
3.2.88 29000 SCTP Receive Buffer Occupancy Exceeded Threshold ................ 3-93
3.2.89 29001 Association Link Broken.............................................................. 3-94
3.2.90 29760 DNS Server Unreachable ........................................................... 3-95
3.2.91 30016 Ethernet Link OAM Event ........................................................... 3-95
3.2.92 30528 The Result of Starting PD Task ................................................... 3-96
3.2.93 30787 ATCA FRU Power On ................................................................. 3-97
3.2.94 30790 ATCA FRU Power Off ................................................................. 3-97
3.2.95 30794 ATCA FRU Communication Lost ................................................. 3-98
3.2.96 30800 ATCA FRU Communication Regain ............................................. 3-98
3.2.97 30812 IPMB State Change(IPMB-A Enable\IPMB-B Disable) .................. 3-99
3.2.98 30813 IPMB State Change(IPMB-A Disable\IPMB-B Enable) .................. 3-99
3.2.99 30814 IPMB State Change(IPMB-A Enable\IPMB-B Enable) ..................3-100
3.2.100 30815 HOST CPU Reset Event ..........................................................3-100
3.2.101 30816 The Board Reset .....................................................................3-101
3.2.102 30817 BIOS Start-up Inform ...............................................................3-101
3.2.103 30818 IPMB Linkstate Event ..............................................................3-102

XV

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 3.2.104 30820 BIOS Memory Inform ...............................................................3-102
3.2.105 30821 Power on Failed Inform............................................................3-103
3.2.106 30822 No RAID Detected...................................................................3-103
3.2.107 30823 High Disk Partition Utilization ...................................................3-104
3.2.108 30824 High Memory Utilization ...........................................................3-104
3.2.109 30825 Less Than 4 NIC Ports Recognised ..........................................3-105
3.2.110 30826 NIC Port Statistics Error Detected.............................................3-105
3.2.111 30827 FC Controller Statistics Error Detected ......................................3-106
3.2.112 30828 ATCA FRU Present..................................................................3-106
3.2.113 30829 ATCA FRU Absent...................................................................3-107
3.2.114 30830 SMART Parameter Error ..........................................................3-107
3.2.115 30831 Fault Memory Isolation.............................................................3-108
3.2.116 31041 ACL Query Table Is Unavailable ...............................................3-109
3.2.117 31296 PTP Failed to Cancel Slave Port...............................................3-109
3.2.118 31554 The IP Address Which Will be Allocated to the Client by DHCP
Server Confilcts With the IP Address Existed on the Network.................. 3-110
3.2.119 41794 Fail to Operate TC Link ............................................................ 3-110
3.3 10000000~9999999999................................................................................... 3-111
3.3.1 16778560 MGW Unable to Work and Withdrawal Service ........................ 3-111
3.3.2 16778562 MSCe/MSC Server (H248 Request) Does Not Receive the
Response Message From Gateway....................................................... 3-112
3.3.3 16778565 H248S Process Data Area Allocates Failed............................. 3-113
3.3.4 16779080 GTP-C Create Socket Fail...................................................... 3-113
3.3.5 16781632 TUP RSV 2 Times Hardware Oriented Group Blocking ............ 3-114
3.3.6 16781633 TUP Wait CLF Expiry Stop Send CFL ..................................... 3-114
3.3.7 16781634 TUP Wait RLG Expiry Stop Send CLF..................................... 3-115
3.3.8 16781635 TUP Wait BLA Expiry............................................................. 3-116
3.3.9 16781636 TUP Wait UBA Expiry ............................................................ 3-116
3.3.10 16781637 TUP Timer 19 Delay to Send RSC ........................................ 3-117
3.3.11 16781638 TUP Timer 22 Delay to Send GRS ........................................ 3-117
3.3.12 16781639 TUP Timer 27 Delay to Send MGB........................................ 3-118
3.3.13 16781640 TUP Timer 29 Delay to Send MGU ....................................... 3-119
3.3.14 16781641 TUP Timer 33 Delay to Send HGB ........................................ 3-119
3.3.15 16781642 TUP Timer 35 Delay to Send HGU........................................3-120
3.3.16 16781643 TUP: Signal Block CIC by Local Switch During T19 Expiry ......3-120
3.3.17 16781647 TUP Circuit Continuity Recheck Succeed ..............................3-121
3.3.18 16781648 TUP Circuit Continuity Recheck Failed..................................3-121

XVI

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 3.3.19 16781649 TUP Blocking CIC After Sent Hardware Group Blocking
Message Twice ....................................................................................3-122
3.3.20 16781888 ISUP Wait RLC (After Send REL) Expiry ...............................3-123
3.3.21 16781889 ISUP Wait BLA Expiry ..........................................................3-123
3.3.22 16781890 ISUP Wait UBA Expiry .........................................................3-124
3.3.23 16781891 ISUP Wait RLC (After Send RSC) Expiry...............................3-124
3.3.24 16781892 ISUP Wait CGA Expiry .........................................................3-125
3.3.25 16781893 ISUP Wait CGUA Expiry.......................................................3-126
3.3.26 16781894 ISUP Wait GRA Expiry .........................................................3-126
3.3.27 16781895 ISUP Wait CQR Expiry.........................................................3-127
3.3.28 16781896 ISUP Wait INF Expiry...........................................................3-127
3.3.29 16781897 ISUP RMT Block..................................................................3-128
3.3.30 16781898 ISUP Unblock RMT by Call...................................................3-128
3.3.31 16781899 ISUP CG RMT Block (Maintenance Oriented) (Without
Release) .............................................................................................3-129
3.3.32 16781900 ISUP CG RMT Block (Hardware Oriented) (With Release) ......3-129
3.3.33 16781901 ISUP: Receive UCIC Message From Opposite Switch
Equipment ...........................................................................................3-130
3.3.34 16781902 ISUP: Signal Block CIC by Local Switch During to T17
Expiry..................................................................................................3-130
3.3.35 16781903 ISUP Circuit Is Locally Blocked by Man-Machine
Command ...........................................................................................3-131
3.3.36 16781904 ISUP Circuit Is Locally Blocked by Call Processing ................3-132
3.3.37 16781905 ISUP Circuit Is Locally Unblocked When It Is Reset ...............3-132
3.3.38 16781906 ISUP Circuit Is Remotely Blocked When It Is Reset ...............3-133
3.3.39 16781907 ISUP Circuit Is Remotely Unblocked When It Is Reset............3-133
3.3.40 16781908 ISUP Circuit Group Is Locally Blocked by Man-Machine
Command (Maintenance) .....................................................................3-134
3.3.41 16781909 ISUP Circuit Group Is Locally Blocked by Man-Machine
Command (Hardware) ..........................................................................3-134
3.3.42 16781910 ISUP Circuit Continuity Recheck Failed.................................3-135
3.3.43 16781911 ISUP Circuit Continuity Recheck Succeed .............................3-135
3.3.44 16781912 ISUP Can Not Carry Out the Continuity Check for Busy
Circuit .................................................................................................3-136
3.3.45 16781913 SS7UP Failed to Recognize the Circuit .................................3-136
3.3.46 16781914 ISUP Detected Inconsistency Between Circuit Group
Maintenance Request and Acknowledge ...............................................3-137
3.3.47 16781921 Office or DPC Unreachable Call Release ..............................3-138
3.3.48 16783937 Current IP Congestion Level of Bearer ..................................3-138

XVII

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 3.3.49 16784448 System Dynamic Recovery Monitor Item Abnormity ...............3-139
3.3.50 16784704 Data Synchronization Failed.................................................3-140
3.3.51 16784705 LIG Link Check Failed..........................................................3-140
3.3.52 25170948 DNS Link Status Change .....................................................3-141
3.3.53 25172483 Remote IP Addresses of the IPQos Test Calls During a
Period Do Not Match ............................................................................3-142
3.3.54 33576914 Svc Register Fail .................................................................3-142
3.3.55 33576915 More than 80% DEP Dialogs Is Used ....................................3-143
3.3.56 33576916 Diameter Version Is Not Supported .......................................3-143
3.3.57 33604560 Calling Party Long Time Conversation...................................3-144
3.3.58 33604561 Called Party Long Time Conversation ...................................3-144
3.3.59 33604562 BICC T17 Time Out When Waiting for RLC After Sending
RSC....................................................................................................3-145
3.3.60 33604563 BICC T19 Time out when Waiting for CGBA ..........................3-145
3.3.61 33604564 BICC T21 Time Out When Waiting for CGUA ........................3-146
3.3.62 33604565 BICC T23 Time Out When Waiting for GRA ...........................3-146
3.3.63 33604566 BICC T33 Time Out When Waiting for INF.............................3-147
3.3.64 33604567 BICC Unblocking CIC Remotely for Calls ..............................3-148
3.3.65 33604568 BICC T28 Time Out When Waiting for CQR...........................3-148
3.3.66 33604569 BICC Detected Unequipped CIC...........................................3-149
3.3.67 33604570 BICC Blocked Circuit Group Locally ......................................3-149
3.3.68 33604571 BICC Blocked Circuit Group Remotely ..................................3-150
3.3.69 33604572 BICC Blocked CIC Remotely for Group Reset .......................3-150
3.3.70 33604573 BICC Unblocked CIC Remotely for Reset..............................3-151
3.3.71 33604574 BICC Unblocked CIC Locally for Reset .................................3-151
3.3.72 33604575 BICC Detected Inconsistency Between Circuit Group
Maintenance Request and Acknowledge ...............................................3-152
3.3.73 33604576 BICC T5 Time Out When Waiting for RLC After Sending
REL ....................................................................................................3-152
3.3.74 33604577 Call Duration Limited by Fraud Profile ...................................3-153
3.3.75 33609432 SIP Link Blocked by OMC ....................................................3-154
3.3.76 33609433 SIP Link UnBlocked by OMC ................................................3-154
3.3.77 33609434 SIP Link Blocked by APP .....................................................3-155
3.3.78 33609435 SIP Link UnBLocked by APP ................................................3-155
3.3.79 33610240 DH Block Signal Link Failed .................................................3-156
3.3.80 33610241 DH Block Signal Link Part Failed ..........................................3-156
3.3.81 33610242 DH Unblock Signal Link Failed .............................................3-157
3.3.82 33610243 DH Unblock Signal Link Part Failed ......................................3-158

XVIII

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 3.3.83 33610254 BSC Reset MSCS ...............................................................3-158
3.3.84 33610255 BSC Reset Circuit................................................................3-159
3.3.85 33610256 BSC Block Circuit ................................................................3-159
3.3.86 33610257 BSC UnBlock Circuit ............................................................3-160
3.3.87 33610258 BSC Block Circuit Group ......................................................3-160
3.3.88 33610259 BSC UnBlock Circuit Group..................................................3-161
3.3.89 33610260 BSC Overload .....................................................................3-161
3.3.90 33610261 MSC Reset BSC..................................................................3-161
3.3.91 33610262 MSCS Reset BSC Fail .........................................................3-162
3.3.92 33610263 MSCS Reset Circuit .............................................................3-162
3.3.93 33610264 MSCS Reset Circuit Fail.......................................................3-163
3.3.94 33610265 BSC Unequipped Circuit ......................................................3-163
3.3.95 33610266 MSCS Unequipped Circuit....................................................3-164
3.3.96 33610267 MSCS A Interface Overload .................................................3-164
3.3.97 33610268 RNC Reset MSCS ...............................................................3-165
3.3.98 33610269 RNC Overload .....................................................................3-165
3.3.99 33610270 MSC Reset RNC .................................................................3-165
3.3.100 33610271 MSC Reset RNC Fail .........................................................3-166
3.3.101 33610273 MSCS Iu Interface Overload ...............................................3-166
3.3.102 33610274 Backup MSCS Switched to Master......................................3-167
3.3.103 33610275 Master MSCS Switched to Backup......................................3-167
3.3.104 33610278 The MSC Server Becomes the Master MSC Server of the
MSC Pool User Data Synchronization ...................................................3-168
3.3.105 33610279 The MSC Server Is No Longer the Master MSC Server of
the MSC Pool User Data Synchronization..............................................3-169
3.3.106 33610284 Access Bearer Error...........................................................3-169
3.3.107 33610285 Jitter Occurs on Access Bearer Status Judgment.................3-170
3.3.108 33610286 ZDB Records Conflict.........................................................3-171
3.3.109 33610287 ZDB Record Number Exceeds Capacity ..............................3-171
3.3.110 33610334 IMEI Check Failed..............................................................3-172
3.3.111 33610338 VLR Received HLR Reset...................................................3-173
3.3.112 33610339 Failed to Get SCCP Address According to IMSI ...................3-173
3.3.113 33610342 VLR Failed to Send Reset to SGSN ....................................3-174
3.3.114 33610343 The Initiative Page Rate of Fast Load Redistribution
Exceeds the Limitation of VLR Capacity ................................................3-175
3.3.115 33610834 Received Length of ACR Has Error .....................................3-175
3.3.116 33610835 Received ACR Type Has Error............................................3-176
3.3.117 33611076 DAP Process Registered Successfully.................................3-176

XIX

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 3.3.118 33611077 DAP Disconnected Link Successfully...................................3-177
3.3.119 33611078 DAP Updated Link Data Successfully ..................................3-177
3.3.120 33611079 Some LREG reboot............................................................3-178
3.3.121 33611080 GREG Changed Over Successfully .....................................3-178
3.3.122 33611081 GREG Power on Successfully.............................................3-179
3.3.123 33611082 GREG Failed to Synchronize Data to LREG ........................3-179
3.3.124 33611083 Some LREG on GREG module has no heartbeat .................3-180
3.3.125 33611084 LREG Failed to Register With the Process of
Master-Slave .......................................................................................3-181
3.3.126 33611085 LREG Process Registered Successfully ..............................3-182
3.3.127 33611086 LREG Changed Over Successfully......................................3-182
3.3.128 33611087 DTP Initialized Data Successfully ........................................3-183
3.3.129 33611088 DTP Failed to Get UB.........................................................3-183
3.3.130 33611092 DEP Process Registered Successfully.................................3-184
3.3.131 33611093 DEP Changed Over Successfully ........................................3-184
3.3.132 33611094 The Bear Link That DAP Used Is Available ..........................3-185
3.3.133 33611095 DAP Changed Over Successfully ........................................3-185
3.3.134 33611096 The Number of DEPs on GREG Module Exceeds the
Maximum ............................................................................................3-186
3.3.135 33611097 The Number of DAPs on GREG Module Exceeds the
Maximum ............................................................................................3-187
3.3.136 33611098 The Number of Links on GREG Module Exceeds the
Maximum ............................................................................................3-188
3.3.137 33611099 Failed to Get UB ................................................................3-189
3.3.138 2365980933 Subscriber Login Notification...........................................3-189
3.3.139 2365981442 Loaded License File Will Expire ......................................3-190
3.3.140 2365981701 Wrong CMM Type ..........................................................3-190
3.3.141 2365981702 Wrong Independent Board Type......................................3-191
3.3.142 2365981956 Synchronize NTP Time Failed.........................................3-191
3.3.143 2365982210 Automatic Backup Succeeded ........................................3-192

Glossary .......................................................................................................... I

XX

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 About This Manual
Purpose
This manual describes how to enable operators to know all alarms and notifications on
the ZXUN iCX (MSCS) system, and to facilitate query during troubleshooting and daily
maintenance.

Intended Audience
This manual is intended for:
l Maintenance engineers
l Equipment installation engineers

Prerequisite Skills and Knowledge

For effective use of this manual, users should have a general understanding of 3G wireless
telecommunications technology. Familiarity with the following is helpful:
ZXUN iCX (MSCS) system and its various components

What Is in This Manual

This manual contains the following chapters:

Chapter Summary

1, Overview Describes the functions of alarm management, alarm occurring modes,

and the meanings of alarms and notifications in the ZXUN iCX (MSCS)
system.

2, Alarm Messages Describes the alarm messages that may appear in the ZXUN iCX
Handling (MSCS) system and the related handling.

3, Notification Message Describes the notification messages that may appear in the ZXUN iCX
Handling (MSCS) system and the related handling.

Related Documentation
The following documentation is related to this manual:
l ZXUN iCX (MSCS) MSC Server Alarm Management Operation Guide
l ZXUN iCX (MSCS) MSC Server Parts Replacement Guide

FCC Compliance Statement

This device complies with part 15 of the FCC Rules. Operation is subject to the following
two conditions.
l This device may not cause harmful interference.

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 l This device must accept any interference received, including interference that may
cause undesired operation.
Changes or modifications not expressly approved by the party responsible for compliance
could void the user's authority to operate the equipment.

Conventions
This manual uses the following typographical conventions:

Typeface Meaning

Italics Variables in commands. It may also refer to other related manuals and documents.

Bold Menus, menu options, function names, input fields, option button names, check boxes,
drop-down lists, dialog box names, window names, parameters, and commands.

Constant Text that you type, program codes, filenames, directory names, and function names.
width

Caution: Indicates a potentially hazardous situation. Failure to comply can result in

moderate injury, equipment damage, or interruption of minor services.

Note: Provides additional information about a certain topic.

II

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 1
Overview
Table of Contents
Alarm Management ....................................................................................................1-1
Fault View ..................................................................................................................1-1
Alarm .........................................................................................................................1-2
Notification .................................................................................................................1-3
Detailed Alarm Information .........................................................................................1-4

1.1 Alarm 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 real-time 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 Fault View

Fault is displayed in the form of alarm or notification.
l 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.
l Notification
Notification belongs to the prompt alarm, which prompts the immediate events, such
as board reset and signaling overload, occurring during the running of the equipment.
Notification belongs to the accidental events occurring during the running of the
equipment, which could not be recovered automatically.
Notification is mostly caused by sudden environment change or other accidental
factors. No special handling is required for the notification. Only the notification that
occurs persistently requires troubleshooting.

1-1

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

1.3 Alarm
Alarm Information
l Alarm Code
Alarm code is the identifier that differentiates alarms. Alarm code is defined by a 32-bit
field indicating the specific code value.
l Alarm Name

Alarm description reflects such content as fault cause and fault phenomenon in a
simple and straightforward way.
l Severity

There are four alarm levels, which are indicated in descending order of severity as
Critical, Major, Minor, and Warning.
à Critical
Critical alarm causes system breakdown and service interruption. It requires
immediate troubleshooting.
à Major
Major alarm significantly affects system operation or weakens network service
capability. It requires troubleshooting as soon as possible.
à Minor
Minor alarm affects system operation and network service capability in an
insignificant way. It requires timely troubleshooting to avoid severity escalation.
à Warning
Warning poses a potential hazard to system operation and network service
capability. It requires troubleshooting at an appropriate time 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.
l Alarm Type

Alarm is classified into six types according to alarm trigger condition and its system
impact.
à Communication alarm: Related with information transmission (ITU-T
Recommendation X.733).

à Processing error alarm: Related with software or process fault (ITU-T

Recommendation X.733).

1-2

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 1 Overview

à QoS alarm: Related with degradation of service quality (ITU-T Recommendation

X.733).
à Equipment alarm: Related with device hardware.
à Environment alarm: Related with the environment where the equipment is located
(ITU-T Recommendation X.733).

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.

System Impact
System impact refers to the impact that the alarm incurs on system or services.

Handling Suggestion
Troubleshooting measures and suggestions are provided.
Pay attention to the following tips when handling alarms.
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.4 Notification
Notification Message
l Notification Code
Notification code is the identifier to differentiate notifications. It is defined by a 32-bit
field indicating the specific code value.
l Notification Name
Notification name reflects such content as fault cause and fault phenomenon in a
simple and straightforward way.

l Severity
There are four notification levels, which are indicated in descending order of severity
as Critical, Major, Minor, and Warning.

l Alarm Type
Notification is classified into six types according to trigger condition and its system
impact.

1-3

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

à Communication alarm: Related with information transmission (ITU-T

Recommendation X.733).
à Processing error alarm: Related with software or process fault (ITU-T
Recommendation X.733).
à QoS alarm: Related with degradation of service quality (ITU-T Recommendation
X.733).
à Equipment alarm: Related with device hardware.
à Environment alarm: Related with the environment where the equipment is located
(ITU-T Recommendation X.733).

Probable Cause
Probable notification causes are enumerated to help users troubleshoot, find preventive
measures, and restore the system to normal state in a timely manner.

System Impact
System impact refers to the impact that the notification incurs on system or services.

Handling Suggestion
Troubleshooting measures and suggestions are provided.
Pay attention to the following tips when handling notifications.
l After recording the fault phenomenon, operation and maintenance personnel may
handle the fault gradually as described in the Handling Suggestion Section in this
manual. If the fault is removed at any handling step, terminate the handling process.
If the fault is not removed, go ahead to the next handling step.
l If the fault cannot be removed, or the system normal operation cannot be restored,
contact the local ZTE office as soon as possible.

1.5 Detailed Alarm Information

In the Local Maintenance Terminal, open the Fault Management window by any of the
following ways:
l Click the icon in the lower left corner of Local Maintenance Terminal.
l Click System Menu > Application Management > Fault Management.

In the Fault Management window, double-click an alarm in the alarm list. The Current
Alarm Detailed Information dialog box is displayed. Figure 1-1 shows the Detailed
Information tab. Figure 1-2 shows the Advice tab.

1-4

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 1 Overview

Figure 1-1 Detailed Information Tab

Figure 1-2 Advice Tab

1-5

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

This page intentionally left blank.

1-6

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2
Alarm Messages Handling
Table of Contents
1~9999.......................................................................................................................2-1
10000~99999 ...........................................................................................................2-74
1000000~9999999 .................................................................................................2-132
10000000~99999999 .............................................................................................2-171
1000000000~9999999999......................................................................................2-231

2.1 1~9999
2.1.1 170 The Switch Board Occurred Loopback Port
Alarm Information
l Alarm code: 170
l Alarm name: The switch board occurred loopback port
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
A loopback port exists on the switching board.

System Impact
This loopback port is blocked.

Handling Suggestion
Remove the loopback on the port, wait for a few seconds, and check whether this alarm
is cleared.

l Yes: End alarm handling.

l No: Contact ZTE for help.

2.1.2 256 OMC Port's Link Is Down

Alarm Information
l Alarm code: 256

2-1

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Alarm name: OMC port's link is down

l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
l The network cable is faulty.
l The network interface of the local end or the remote end is faulty.
l The Negotiate Mode parameters configured for the two ends are inconsistent
(self-adaptive, forcible).

System Impact
The OMC port can't transfer data.

Handling Suggestion
1. Check whether the cable is plugged well.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Re-plug the cable, and then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether the cable is damaged.
l Yes: Go to Step 4.
l No: Go to Step 5.
4. Replace the cable, and then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 5.
5. Check whether the network interface of the local end or the remote end is faulty.
l Yes: Go to Step 6.
l No: Go to Step 7.
6. Replace the corresponding GPBB0 board, and then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 7.
7. Run the SHOW ENETPORTPARA command to check whether the port configuration
at the two end is reasonable.
l Yes: Contact ZTE for help.
l No: Go to Step 8.

2-2

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Note:
The Negotiate Mode parameters (self-adaptive, forcible) at the two ends must be the
same. When the Negotiate Mode parameters are configured to forcible, the Speed
and Work Mode parameters must be the same.

8. Modify the port configuration, and then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.3 512 Trunk Loss of Frame

Alarm Information
l Alarm code: 512
l Alarm name: Trunk loss of frame
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
l Two ends have no common ground.
l The clocks are not synchronous.
l The transmission equipment is faulty.

System Impact
The receiving signals over this trunk are interrupted.

Handling Suggestion
1. Check whether the equipment matches the cable impedance. Check whether the DIP
switch on the board match the cable type.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Re-set the DIP switch on the board, and then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Use the multimeter to detect whether the grounding signals of the both ends of the
equipment are reliable.
l Yes: Go to Step 5.
l No: Go to Step 4.
4. Make grounding signals be reliable, and then check whether the alarm disappears.
l Yes: End alarm handling.

2-3

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l No: Go to Step 5.
5. Check whether the clock daughter card locks the clock.
l Yes: Go to Step 8.
l No: Go to Step 6.
6. Check whether the clock references of two interconnected NEs or nodes are
consistent.
l Yes: Go to Step 8.
l No: Go to Step 7.
7. Check whether the FSWA1 board locks the clock (T/C indicator is green). Reconnect
to the reference input of the clock, and the clock daughter card restores the clock.
After the clock is locked, check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 8.
8. Check if the clock references of two matching NEs or nodes are consistent.
l Yes: Go to Step 10.
l No: Go to Step 9.
9. Modify the clock base, ensuring the clock references of two matching NEs or nodes
are consistent. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 10.
10. Ask for assistant of the transmission equipment maintaining personnel to check if the
transmission equipment is exceptional.
l Yes: Locate the fault through step-by-step physical diagnosis and circulating test.
l No: Contact ZTE for help.

2.1.4 513 Trunk Loss of Signal

Alarm Information
l Alarm code: 513
l Alarm name: Trunk loss of signal
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
l The E1 line is not connected or incorrectly connected on the DDF.
l The E1 line is broken.
l The upstream equipment is exceptional.

System Impact
The receiving signals over this trunk are interrupted.

Handling Suggestion
1. Check whether the E1 line on the DDF is connected well.

2-4

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l Yes: Go to Step 3.
l No: Go to Step 2.
2. Have the E1 line connected well on the DDF, and then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Self-loop this E1 line at the equipment side, and then check whether the alarm
disappears.
l Yes: Go to Step 4.
l No: Go to Step 5.
4. Detect the upstream equipment.
l Yes: Contact the maintenance engineer of upstream equipment for handling.
l No: Contact ZTE for help.
5. Replace the board, and then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.5 514 Trunk Alarm Indication Signal

Alarm Information
l Alarm code: 514
l Alarm name: Trunk alarm indication signal
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
The upstream equipment is faulty.

System Impact
The receiving signals over this trunk are interrupted.

Handling Suggestion
Check the alarms related to the E1 of the upstream equipment. Based on the alarm
handling suggestion to handle alarms. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.6 515 Trunk Loss of CRC Multi-Frame

Alarm Information
l Alarm code: 515

2-5

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Alarm name: Trunk loss of CRC multi-frame

l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
The frame format is inconsistent.

System Impact
The receiving signals over this trunk are interrupted.

Handling Suggestion
1. Run the SHOW E1T1 command to check whether the CRC4 mode for the two
interconnected ends are consistent.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Run the SET E1T1 command to configure the same frame formats for the two ends,
and then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.7 517 Trunk Remote Alarm Indication

Alarm Information
l Alarm code: 517
l Alarm name: Trunk remote alarm indication
l Severity: Major
l Alarm type: Equipment alarm

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 at the peer
end would probably cause this alarm.

System Impact
The receiving signals over this trunk are interrupted.

Handling Suggestion
1. Check whether the intermediate transmission equipment of this trunk link is faulty.
l Yes: Contact the maintenance engineer of transmission equipment for handling.
l No: Go to Step 2.

2-6

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

2. At this time, at least one alarm appears on the peer end, such as LOS, AIS, LOF, check
and record the alarm of the peer end. Check whether the signals sent by local end are
faulty.
l Yes: Go to Step 3.
l No: Contact ZTE for help.
3. Troubleshoot the faulty signals sent by local end, and check whether the alarm
disappears.
l Yes: End the alarm handling.
l No: Contact ZTE for help.

2.1.8 518 Trunk Link Is Used for CSU Loopback Test

Alarm Information
l Alarm code: 518
l Alarm name: Trunk link is used for CSU loopback test
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
The equipment at end A sends a CSU link establishment code to end B, and end B loops
back this trunk link and starts the CSU test.
If this trunk link is not used for the CSU loopback test, the alarm will not be triggered.

System Impact
The configured trunk link is blocked.

Handling Suggestion
Select Maintenance Management > Diagnostic Test in the Terminal window, and set the
T1 CSU loopback command from end A to end B. After above operations, check whether
the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.9 1024 Cell Delineation Not Synchronized

Alarm Information
l Alarm code: 1024
l Alarm name: Cell delineation not synchronized
l Severity: Minor
l Alarm type: Equipment alarm

2-7

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

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 whether there is any physical-layer alarm accompanying this alarm.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Eliminate other physical layer alarm. After that, check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check if both two ends are configured to SDH mode or SONET mode.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. configure a correct signal mode for them, check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.10 1025 Loss of Cell Delineation

Alarm Information
l Alarm code: 1025
l Alarm name: Loss of cell delineation
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
LCD is triggered after OCD lasts for 4ms.

System Impact
The ATM communication is interrupted.

Handling Suggestion
1. Check whether there is any physical-layer alarm accompanying this alarm.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Eliminate other physical layer alarm. After that, check whether the alarm disappears.

2-8

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l Yes: End alarm handling.

l No: Go to Step 3.
3. Check if both two ends are configured to SDH mode or SONET mode.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. configure a correct signal mode for them, check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.11 1026 Cell Delineation Do Not Synchronization About Cell

on E1/T1 Link
Alarm Information
l Alarm code: 1026
l Alarm name: Cell delineation do not synchronization about cell on E1/T1 link
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l Cell Header HEC is damaged, leading to cell location failure in physical layer frame.
l The alarm is caused by bottom layer fault. Cell HEC is handled differently at local end
and remote end.

System Impact
Data reception on E1/T1 link is abnormal. If merely one E1/T1 link is available for the port,
all services on the board will be down. Otherwise, port bandwidth will be affected, leading
to decreased access bandwidth. The number of successful upper-layer service access
related to the port will decrease, but service interruption will not occur.

Handling Suggestion
1. Check whether there is any physical-layer alarm accompanying this alarm.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Eliminate other physical-layer alarm. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Unplug/plug this board, and reset the board. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-9

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

2.1.12 1285 Clock Chip Is in Preheat Status

Alarm Information
l Alarm code: 1285
l Alarm name: Clock chip is in preheat status
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
The board is reset. The SETS chip and the crystal oscillator needs to be fully preheated.

System Impact
The output clock is unstable.

Handling Suggestion
Follow the normal procedure after the board power-on, and wait for the end of the clock
daughter card preheating. Perform clock performance tests after the preheating. Then
check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.13 1286 Input Clock of the Board Is Lost

Alarm Information
l Alarm code: 1286
l Alarm name: Input clock of the board is lost
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l The board is not in place (not properly inserted into the slot).
l The clock cable is disconnected.
l One clock daughter card in the same shelf is faulty or is not in place.
l The board is faulty.

System Impact
The board fails to be synchronized with the system clock and fails to work properly, leading
to UE access failure and interruption of ongoing services.

2-10

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Handling Suggestion
1. Check whether the two clock daughter cards in the same shelf are normal.
l One of them is normal: Make no intervention, and wait for the system to be
automatically restored.
l Both of them are faulty, go to Step 2.
2. Replace the clock daughter cards. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether the clock (input) cable at the shelf is properly connected.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Adjust the clock (input) cable. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.14 1792 SDH/SONET: Loss of Signal

Alarm Information
l Alarm code: 1792
l Alarm name: SDH/SONET: loss of signal
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
l The upstream optical transmitting equipment is faulty.
l The optical fiber transmission line is faulty.
l The fiber pigtail and the flange between the local-end optical-fiber distribution frame
and the equipment are faulty.
l The local-end optical receiver is faulty.

System Impact
All received trunk signals are broken.

Handling Suggestion
1. Use the optical power meter to detect the power for receiving optical signals at the
local end to see whether the power is within the normal range (-28dBm~-8dBm).
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Replace the optical module or the board, check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.

2-11

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

3. Detect the power for transmitting optical signals by using the transmitting end at the
peer-end office to see whether it is within the normal range.
l Yes: Go to Step 5.
l No: Go to Step 4.
4. Contact the maintenance personnel of the peer-end office to solve the faults at the
peer end. Check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 5.
5. There may be something wrong with the transmission equipment. It is required to ask
the transmission equipment maintenance personnel to troubleshoot the transmission
equipment. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.15 1793 SDH/SONET: Loss of Frame

Alarm Information
l Alarm code: 1793
l Alarm name: SDH/SONET: loss of frame
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
The upstream SDH equipment is faulty.

System Impact
All received trunk signals are broken.

Handling Suggestion
The SDH transmission equipment is faulty. Contact the transmission equipment
maintenance personnel to troubleshoot the SDH equipment. And then check whether the
alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.16 1794 SDH/SONET: Regenerator Section Trace

Mismatch/Section Trace Mismatch
Alarm Information
l Alarm code: 1794

2-12

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l Alarm name: SDH/SONET: regenerator section trace mismatch/section trace

mismatch
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
During optical fiber cutover and scheduling, the optical fiber on the optical distribution frame
is wrongly connected, 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 whether the optical fibers on the ODF are correctly connected at the local end
and the peer end.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Have the optical fibers well connected, and check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether the default values of Section access point identifier at the two ends
are consistent.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Configure the default values of Section access point identifier at the two ends to
make them be consistent.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.17 1795 SDH/SONET:MS Alarm Indication Signal/Line Alarm

Indication Signal
Alarm Information
l Alarm code: 1795
l Alarm name: SDH/SONET:MS alarm indication signal/Line alarm indication signal
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
There are faults in the upstream equipment, including LOS, LOF and RS TIM.

2-13

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
All received 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. And then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.18 1796 SDH/SONET:MS Far-End Reception Failure/Line

Far-End Reception Failure
Alarm Information
l Alarm code: 1796
l Alarm name: SDH/SONET:MS far-end reception failure/Line far-end reception failure
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
There are faults in the uplink direction of the downstream equipment.

System Impact
All sent 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. And then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.19 1797 SDH/SONET: Signal Failure

Alarm Information
l Alarm code: 1797
l Alarm name: SDH/SONET: signal failure
l Severity: Major
l Alarm type: Equipment alarm

2-14

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Probable Cause
l Bit errors occur because the fiber pigtail on the downlink direction is contaminated,
transmission line attenuation enhances, or the optical transmission mode changes.
l The ADM sending equipment is faulty.

System Impact
All received trunk signals transmitted by this SDH/SONET line generate kinds of alarms.

Handling Suggestion
1. Check whether the fiber pigtails are contaminated.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Clean the fiber pigtails, and check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Use the optical power meter to detect the optical power attenuation of each connection
point in the downlink direction in the corresponding multiplexing section to see whether
it is excessive.
l Yes: Go to Step 4.
l No: Go to Step 5.
4. Adjust the attenuation to the normal value, and check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 5.
5. Ask the transmission network maintenance personnel to check whether the ADM
sending equipment is faulty. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.20 1798 SDH/SONET: Signal Deterioration

Alarm Information
l Alarm code: 1798
l Alarm name: SDH/SONET: signal deterioration
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l Eliminate SF first when SD and SF occur at the same time.
l If SD occurs alone, it can be concluded that the ADM NE transmission device is faulty.

System Impact
Alarms indicated for partial trunks.

2-15

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Handling Suggestion
1. If SF occurs, eliminate SF first. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Check the optical fibers and the optical modules at the local end and the peer end,
and make sure that the optical fibers are well connected and that the optical modules
are not loose. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Replace the optical module or the board. And then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 4.
4. Contact the maintenance personnel of the peer-end office to check the peer-end office.
After the faults in the peer-end office are solved, check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 5.
5. There may be something wrong with the transmission equipment. It is required to ask
the transmission equipment maintenance personnel to troubleshoot the transmission
equipment. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.21 1799 SDH/SONET:Loss of AU Pointer/Loss of Path Pointer

Alarm Information
l Alarm code: 1799
l Alarm name: SDH/SONET:Loss of AU pointer/Loss of path pointer
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
The upstream AU-4 pointer processing unit is faulty.

System Impact
All received trunk signals transmitted by this SDH/SONET line are broken.

Handling Suggestion
Contact the maintenance personnel for the transmission network to check whether
the upstream AU-4 channel control unit is faulty. And then check whether the alarm
disappears.
l Yes: End alarm handling.

2-16

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l No: Contact ZTE for help.

2.1.22 1800 SDH/SONET:AU Alarm Indication Signal/Path Alarm

Indication Signal
Alarm Information
l Alarm code: 1800
l Alarm name: SDH/SONET:AU alarm indication signal/Path alarm indication signal
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
The upstream VC-4 channel control unit is faulty.

System Impact
All received trunk signals transmitted by this SDH line are broken.

Handling Suggestion
Contact the maintenance personnel for the transmission network to check whether
the upstream VC-4 channel control unit is faulty. And then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.23 1801 SDH/SONET:HP Trace Mismatch/ Path Trace Mismatch

Alarm Information
l Alarm code: 1801
l Alarm name: SDH/SONET:HP trace mismatch/ Path trace mismatch
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
l During cutover and scheduling of optical fibers, the optical fiber on the ODF is
incorrectly connected.
l The expected value is incorrectly set in the network management system.

System Impact
The connection of all trunks is incorrect.

2-17

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Handling Suggestion
1. Check whether the connection of the optical fiber on ODFs at the local end and the
peer end is correct.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Correctly connect the optical fibers on ODFs at the local end and the peer end, and
then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether the default values of VC-4 channel access point identifier (J1B) at
the two ends are consistent.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Configure the same expected value for the VC-4 channel access point identifier
(J1B) at the two ends, and then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.24 1802 SDH/SONET:HP Unequipped/Path Unequipped

Alarm Information
l Alarm code: 1802
l Alarm name: SDH/SONET:HP unequipped/Path unequipped
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
l During project installation, the internal cross connection of the SDH network is not
complete.
l The remote device where DTI is located is not equipped with this path.

System Impact
All received trunk signals transmitted by this SDH line are broken.

Handling Suggestion
Contact the maintenance personnel for the transmission network to check whether the
upstream VC-4 path control unit is faulty (C2B). And then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-18

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

2.1.25 1803 SDH/SONET: HP Label Mismatch/Path Label Mismatch

Alarm Information
l Alarm code: 1803
l Alarm name: SDH/SONET: HP label mismatch/path label mismatch
l Severity: Major
l Alarm type: Equipment alarm

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

System Impact
All received trunk signals transmitted by this SDH line may be broken.

Handling Suggestion
Contact the maintenance personnel for the transmission network to check whether the
upstream and downstream circuit configuration (C2B) of the corresponding time slot of the
Digital Cross Connect (DXC) devices is correct.

2.1.26 1804 SDH/SONET:HP Remote Reception Failure/Path Remote

Reception Failure
Alarm Information
l Alarm code: 1804
l Alarm name: SDH/SONET:HP remote reception failure/path remote reception failure
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
There are faults in the VC-4 channel where the board is located.

System Impact
All sent 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 VC-4 channel where the board is located. And then check whether the
alarm disappears.
l Yes: End alarm handling.

2-19

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l No: Contact ZTE for help.

2.1.27 1805 SDH/SONET: Loss of Multi-Frame

Alarm Information
l Alarm code: 1805
l Alarm name: SDH/SONET: Loss of multi-frame
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
The upstream VC-4 channel control unit is faulty.

System Impact
All received trunk signals transmitted by this SDH line may be broken.

Handling Suggestion
Contact the maintenance personnel for the transmission network to check whether the
upstream VC-4 channel control unit (H4) is faulty.

2.1.28 1806 SDH/SONET: Loss of TU Pointer/Loss of Virtual

Tributary Pointer
Alarm Information
l Alarm code: 1806
l Alarm name: SDH/SONET: Loss of TU pointer/loss of virtual tributary pointer
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
The upstream TU tributary pointer processing unit is faulty.

System Impact
The received trunk signal transmitted by this tributary unit is broken.

Handling Suggestion
Contact the maintenance personnel for the transmission network to check whether the
upstream TU-12 tributary pointer processing unit is faulty.

2-20

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

2.1.29 1807 SDH/SONET: Tributary Unit Alarm Indication

Signal/Virtual Tributary Alarm Indication Signal
Alarm Information
l Alarm code: 1807
l Alarm name: SDH/SONET: tributary unit alarm indication signal/virtual tributary alarm
indication signal
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
A fault occurs in the upstream TU-12 tributary pointer processing unit, which may be
TU-AIS, TU-LOM, TU-LOP, or TU UNEQ.

System Impact
The received trunk signal transmitted by this tributary unit is broken.

Handling Suggestion
Contact the maintenance personnel for the transmission network to check whether the
upstream TU-12 tributary pointer processing unit is faulty.

2.1.30 1808 SDH/SONET: LP Remote Defect Indication/Virtual

Tributary Remote Defect Indication
Alarm Information
l Alarm code: 1808
l Alarm name: SDH/SONET: LP remote defect indication/virtual tributary remote defect
indication
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
l A function fault occurs in the local TU-12 branch.
l Function faults occur in the equipment of other nodes on the TU-12 tributary.

System Impact
The trunk signal transmitted by this tributary unit is broken.

2-21

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Handling Suggestion
1. Check whether there is something wrong with the connection of the optical fiber on the
ODF at the local end and the peer end.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Have the optical fiber well connected, and check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Contact the maintenance personnel for the transmission network to check whether the
upstream TU-12 tributary pointer processing unit is faulty.
l Yes: ask the maintenance personnel for the transmission network to handle the
fault.
l No: Go to Step 4.
4. Check the alarm forms at both ends. Firstly detect the peer-end alarm form. Eliminate
the peer-end alarms firstly. Trough loopback operations, troubleshoot the local-end
equipment, transmission equipment, and peer-end equipment step by step. Software
loopback and hardware loopback can be used.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.31 1809 SDH/SONET:LP Remote Failure Indication/Virtual

Tributary Remote Failure Indication
Alarm Information
l Alarm code: 1809
l Alarm name: SDH/SONET:LP remote failure indication/Virtual tributary remote failure
indication
l Severity: Warning
l Alarm type: Equipment alarm

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

System Impact
The received trunk signal transmitted by this tributary unit is broken.

Handling Suggestion
1. Check whether there is something wrong with the connection of the optical fiber on the
ODF at the local end and the peer end.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Have the optical fiber well connected, and check whether the alarm disappears.

2-22

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l Yes: End alarm handling.

l No: Go to Step 3.
3. Contact the maintenance personnel for the transmission network to check whether the
upstream TU-12 tributary pointer processing unit is faulty.
l Yes: Contact the maintenance personnel for the transmission network to handle
the fault.
l No: Go to Step 4.
4. Check the alarm forms at both ends. Firstly detect the peer-end alarm form. Eliminate
the peer-end alarms firstly. Trough loopback operations, troubleshoot the local-end
equipment, transmission equipment, and peer-end equipment step by step. Software
loopback and hardware loopback can be used.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.32 1810 SDH/SONET:LP Trace Mismatch/Virtual Tributary Trace

Mismatch
Alarm Information
l Alarm code: 1810
l Alarm name: SDH/SONET:LP trace mismatch/virtual tributary trace mismatch
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
l During the cutover and dispatching of the cable, the cable connection on DDF is
wrong.
l The expected value is incorrectly set in the network management system.

System Impact
The connection of the trunk signal on this tributary unit is incorrect.

Handling Suggestion
1. Check whether the connection of the optical fiber on ODF at the local end and the peer
end is correct.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Correctly connect the optical fibers on ODF at the local end and the peer end, and
then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether the default values of VC-12 channel access point identifier (J2B) at
the two ends are consistent.

2-23

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Yes: Contact ZTE for help.

l No: Go to Step 4.
4. Configure the same expected value for the VC-12 channel access point identifier
(J2B) at the two ends, and then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.33 1811 SDH/SONET:LP Unequipped/Virtual Tributary

Unequipped
Alarm Information
l Alarm code: 1811
l Alarm name: SDH/SONET:LP unequipped/virtual tributary unequipped
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
l During project installation, the internal cross connection of the SDH network is not
complete.
l The remote tributary device is not equipped.

System Impact
The received trunk signal transmitted by this tributary unit may be broken.

Handling Suggestion
1. Check the optical fibers and the optical modules at the local end and the peer end,
and make sure that the optical fibers are well connected and that the optical modules
are not loose. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Contact the transmission equipment maintenance personnel to check the configuration
connections at both ends. Check whether the signal label received by this tributary is
consistent with that configured at local end. After confirmation, check whether the
alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Contact the transmission equipment maintenance personnel to use the SDH
tester to check whether the upstream and downstream circuit configuration of the
corresponding time slot of each DXC node device on the transmission line is correct.
Check whether V5 byte configuration is consistent with that at the peer end (The
default configuration at local end is asynchronous mapping.)
l Yes: Go to Step 4.

2-24

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l No: Contact the transmission equipment maintenance personnel to modify the

configuration.
4. Replace the optical fiber interface board.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.34 1812 SDH/SONET: LP Label Mismatch/Virtual Tributary Label

Mismatch
Alarm Information
l Alarm code: 1812
l Alarm name: SDH/SONET: LP label mismatch/virtual tributary label mismatch
l Severity: Warning
l Alarm type: Equipment alarm

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.

Handling Suggestion
1. Check the optic 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. And
then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 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.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Replace the board. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-25

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

2.1.35 1816 SDH/SONET:Severely B1 Error Code

Alarm Information
l Alarm code: 1816
l Alarm name: SDH/SONET:Severely B1 error code
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
l Signal reception attenuation excessive.
l Failure of transmitting part of directly connected transmission equipment.
l Unclean optical fiber connectors or incorrect connection of them.
l Local-end receiving part 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
1. Check the optic 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.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Replace this fiber module or board. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. It needs to ask maintenance personnel to check the peer-end office. After
troubleshooting at the peer end, check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 4.
4. There may be something wrong with the transmission equipment. It needs to ask
the maintenance personnel special for maintaining transmission equipment to do
troubleshooting or contact ZTE for help.

2.1.36 1817 SDH/SONET:Severely B2 Error Code

Alarm Information
l Alarm code: 1817
l Alarm name: SDH/SONET:Severely B2 error code
l Severity: Major
l Alarm type: Equipment alarm

2-26

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Probable Cause
l Signal reception attenuation excessive.
l Unclean optical fiber connectors or incorrect connection of them.
l Peer-end transmitting part failure in multiplexing section.
l Local-end receiving part failure in multiplexing section.
l B1 error code.

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
1. Check the optic 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.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Replace this fiber module or board. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. It needs to ask maintenance personnel to check the peer-end office. After
troubleshooting at the peer end, check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 4.
4. There may be something wrong with the transmission equipment. It needs to ask
the maintenance personnel special for maintaining transmission equipment to do
troubleshooting or contact ZTE for help.

2.1.37 1818 SDH/SONET:Severely B3 Error Code

Alarm Information
l Alarm code: 1818
l Alarm name: SDH/SONET:Severely B3 Error Code
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
l Signal reception attenuation excessive.
l Unclean optical fiber connectors or incorrect connection of them.
l Failure of the peer-end transmitting part based on higher order path.
l Local-end receiving part failure.
l B1, B2 error codes.

2-27

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
Noise or call lose appears in the tone service on this HP. Error code appears in the data
service path.

Handling Suggestion
1. Check the optic 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.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Replace this fiber module or board. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. It needs to ask maintenance personnel to check the peer-end office. After
troubleshooting at the peer end, check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 4.
4. There may be something wrong with the transmission equipment. It needs to ask
the maintenance personnel special for maintaining transmission equipment to do
troubleshooting or contact ZTE for help.

2.1.38 1819 SDH/SONET:Severely BIP-2 Error Code

Alarm Information
l Alarm code: 1819
l Alarm name: SDH/SONET:Severely BIP-2 error code
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
l The lower-order path is interfered.
l The peer-end transmitting part of the lower-order path is faulty.
l The local-end receiving part is faulty.

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
1. Check the optical fibers and the optical modules at the local end and the peer end,
and make sure that the optical fibers are well connected and that the optical modules
are not loose.
l Yes: End alarm handling.

2-28

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l No: Go to Step 2.
2. Replace this fiber module or board. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Contact the maintenance personnel of the peer-end office to solve the faults at the
peer end. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 4.
4. There may be something wrong with the transmission equipment. It is required to ask
the transmission equipment maintenance personnel to troubleshoot the transmission
equipment.

2.1.39 1820 SDH/SONET:MS Remote Error Indication

Alarm Information
l Alarm code: 1820
l Alarm name: SDH/SONET: MS remote error indication
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
l The signal reception attenuation is excessive.
l The transmitting part of the directly connected transmission equipment is faulty.
l The optical fiber connectors are unclean or incorrectly connected.
l The local-end receiving part is faulty.

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
1. Check the optical fibers and the optical modules at the local end and the peer end,
and make sure that the optical fibers are well connected and that the optical modules
are not loose.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Replace this fiber module or board. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Contact the maintenance personnel of the peer-end office to solve the faults at the
peer end. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 4.

2-29

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

4. There may be something wrong with the transmission equipment. It is required to ask
the transmission equipment maintenance personnel to troubleshoot the transmission
equipment.

2.1.40 1821 SDH/SONET:HP Remote Error Indication

Alarm Information
l Alarm code: 1821
l Alarm name: SDH/SONET: HP remote error indication
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
l Signal reception attenuation excessive.
l Failure of transmitting part of directly connected transmission equipment.
l Unclean optical fiber connectors or incorrect connection of them.
l Local-end receiving part 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
1. Check the optic 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.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Replace this fiber module or board. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. It needs to ask maintenance personnel to check the peer-end office. After
troubleshooting at the peer end. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 4.
4. There may be something wrong with the transmission equipment. It needs to ask
the maintenance personnel special for maintaining transmission equipment to do
troubleshooting or contact ZTE for help.

2.1.41 1826 SDH/SONET:LP Remote Error Indication

Alarm Information
l Alarm code: 1826

2-30

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l Alarm name: SDH/SONET: LP remote error indication

l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
l Signal reception attenuation excessive.
l There is failure of transmitting part of directly connected transmission equipment.
l Optical fiber connectors are unclean or connection of them is incorrect.
l 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
1. Check the optic 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.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Replace this fiber module or board. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. It needs to ask maintenance personnel to check the peer-end office. After
troubleshooting at the peer end, check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 4.
4. There may be something wrong with the transmission equipment. It needs to ask
the maintenance personnel special for maintaining transmission equipment to do
troubleshooting or contact ZTE for help.

2.1.42 2560 CPU Utilization Exceeds Alarm Limit

Alarm Information
l Alarm code: 2560
l Alarm name: CPU utilization exceeds alarm limit
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
l When the upper-layer service traffic is heavy, the CPU usage may be too high and
exceed the CPU usage threshold.
l The system is synchronizing or saving data.

2-31

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l The set CPU overload threshold is small.

System Impact
The CPU usage reflects the running status of the current system. Usually, CPU overload
(that is, the CPU usage is too high) occurs because the current system is processing a
time-consuming service or operation.
CPU overload has the following influences on the system:
l The lower-priority services fail to seize CPU, so they fail to be processed or cannot
be processed in time.
l Sever CPU overload (100%) may cause board reset, which causes normal service
interrupted.

Handling Suggestion
1. Run the SHOW CPUTHR command to query the CPU overload threshold. In general,
the lower-level through the CPU overload threshold is set to 80%, while the higher-level
one is set to 90%.
l Set CPU overload threshold is too small, go to Step 2.
l Set CPU overload threshold is rational, go to Step 3.
2. Run the SET CPUTHR command to re-set the CPU overload threshold. Synchronize
the settings to the foreground, and wait for 30s. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Under the Log Management node of the Terminal window, check whether data
synchronization, data saving, or file operation is being performed.
l Yes: After the operation is finished, end alarm handling.
l No: Go to Step 4.
4. Check the current traffic to see whether the service is busy. Check whether a new
board is added, or the current software version is being updated and the new version
is being downloaded.
l If the current service is busy and the version software is being downloaded, wait
until the current service is idle or the software is downloaded completely, and then
end alarm handling.
l If the current service is not busy and no new version software is being downloaded,
wait until the CPU load drops automatically, and then end alarm handling.
l In case of other reasons, contact ZTE for help.

2-32

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Note:
a. In the Performance Management window, select Global Traffic > Basic Traffic
Measurement to view the current traffic information.
b. In the Terminal window, select Maintenance Management > Version
Management to view the version download information.

2.1.43 2565 GPS Receiver Does Not Support the Work Mode
Configuration
Alarm Information
l Alarm code: 2565
l Alarm name: GPS receiver does not support the work mode configuration
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
GPS receiver does not support the work mode configuration.

System Impact
The configuration of GPS receiver work mode does not take effect.

Handling Suggestion
1. Check whether the current work mode is configured correctly.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Check whether the GPS receiver is correct.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
3. Re-configure the correct work mode for the GPS receiver and check whether the alarm
is cleared.
l Yes: End alarm handling.
l No: Contact ZTE for help.
4. Replace the GPS receiver and restart the board. Check whether the alarm is cleared.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-33

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

2.1.44 3073 FLASH Device Initialize Failed

Alarm Information
l Alarm code: 3073
l Alarm name: FLASH device initialize failed
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
FLASH is destroyed.

System Impact
All operations on FLASH fail.

Handling Suggestion
Replace the board. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.45 3584 Memory Lack Alarm

Alarm Information
l Alarm code: 3584
l Alarm name: Memory lack alarm
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
The remaining memory is not greater than the memory alarm threshold.

System Impact
The memory is insufficient.

Handling Suggestion
1. Check whether the memory alarm threshold is set too high.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Reset the memory alarm threshold, wait several seconds, and then check whether the
alarm disappears.
l Yes: End alarm handling.

2-34

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l No: Contact ZTE for help.

2.1.46 3841 The Control Plane Retransfer Ratio Over the Threshold
Alarm Information
l Alarm code: 3841
l Alarm name: The control plane retransfer ratio over the threshold
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
l There are some poorly-touched boards in the rack, which increases the retransfer
ratio of the Reliable User Datagram Protocol (RUDP).
l The Ethernet communication equipment is exceptional on the board or the switching
board.
l The address of the Transparent Interprocess Communication (TIPC) node conflicts.

System Impact
When the standby board exists, the active board automatically initiates the switching
operation.

Handling Suggestion
1. Plug and unplug the board where the alarm exists. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: The board may be faulty or still poorly-touched, go to Step 2.
2. It is recommended to switch the network switching boards. Then check whether the
alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.47 4357 The System Bureau Changed

Alarm Information
l Alarm code: 4357
l Alarm name: The system bureau changed
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
The office ID of the system is modified.

2-35

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
The office ID of the system is modified, but it does not take effect. It is required to restart
the NE to make the modification take effect.

Handling Suggestion
Restart the system. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.48 5122 Loss of Active/Standby Communication Link

Alarm Information
l Alarm code: 5122
l Alarm name: Loss of Active/standby communication link
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
l The boards are configured to the active/standby mode, but the standby board is not
in place.
l The standby board exists, but the communication link between the active board and
the standby one is broken.

System Impact
The active board fails to communicate with the standby board communication, and the
active/standby switchover fails. It has no impact to the services.

Handling Suggestion
1. Check whether the boards are configured to active/standby mode, and both the active
board and standby board are in place.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Configure the boards to active/standby mode, and both the active board and standby
board are in place. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
3. Check whether there are related alarms or notifications on the standby board.
l Yes: Handle it according to its handling suggestion.
l No: Go to Step 4.
4. Replace the standby board. Then check whether the alarm disappears.
l Yes: End alarm handling.

2-36

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l No: Go to Step 5.
5. Change the slots of both the active board and the standby board. Then check whether
the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.49 5123 The Configuration Is Not Supported

Alarm Information
l Alarm code: 5123
l Alarm name: The configuration is not supported
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
Errors occur in the configuration data.

System Impact
The board does not work in the set mode.

Handling Suggestion
1. Check the additional information of this alarm, and judge which configuration item
suffers from configuration errors.
2. Check whether the configuration window of OMM supports this configuration item.
l Yes: Go to Step 3.
l No: Contact ZTE for help.
3. Modify this configuration item. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.50 5128 Rack or Shelf Conflict

Alarm Information
l Alarm code: 5128
l Alarm name: Rack or shelf conflict
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
A rack or shelf with the same configuration exists on the NE.

2-37

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
The conflicting rack or shelf cannot operate properly.

Handling Suggestion
Check rack and shelf configurations.

2.1.51 5200 Board Configuration Information Is Not Compatible

Alarm Information
l Alarm code: 5200
l Alarm name: Board configuration information is not compatible
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
l The boards are configured to active/standby mode, but the standby board is not
inserted into the slot.
l The communication link between the active board and the standby board is broken.

System Impact
The active board fails to communicate with the standby one.

Handling Suggestion
1. Check whether the boards are configured to active/standby mode, and both active and
standby boards are inserted into the slots.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Configure the boards to active/standby mode, and both the active board and standby
board are in place. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
3. Check the active and standby boards for the related alarms and notifications.
l Yes: Perform the recommended solution to handle the possible alarms and
notifications.
l No: Go to Step 4.
4. Replace the corresponding active or standby board. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 5.
5. Change the slots of both the active and standby boards. Then check whether the
alarm disappears.
l Yes: End alarm handling.

2-38

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l No: Contact ZTE for help.

2.1.52 5201 The Number of Logic CPU Is Out of Range

Alarm Information
l Alarm code: 5201
l Alarm name: The number of logic CPU is out of range
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
The logical CPU number is greater than the maximum number of logical addresses
specified in the resource configuration file.

System Impact
The out-of-range logical entity cannot be powered on.

Handling Suggestion
1. Delete all out-of-range logical addresses. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Modify the maximum number of logical addresses in the resource configuration file
and restart the board. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.53 5382 Environment Monitor Board Communication Is

Abnormal
Alarm Information
l Alarm code: 5382
l Alarm name: Environment monitor board communication is abnormal
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
l The environment monitoring board is not connected to the network switching board
or the connection is wrong.
l The environment monitoring board locates in a rack. The configured rack number is
different from that where DIP switch of the environment monitoring board locates.

2-39

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
The system can not monitor the status of power supply and environmental situation.
However, there is no impact on services.

Handling Suggestion
1. Reconnect the RS485 cable between the environment monitoring board and network
switching board. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Check whether the rack number in which this environment monitoring board locates is
consistent with the rack number switch set for the environment monitoring board.
l Yes: Contact ZTE for help.
l No: Go to Step 3.
3. Modify the configuration to make sure the rack number in which this environment
monitoring board locates is consistent with the rack number switch set for the
environment monitoring board. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.54 5400 Configuration Conflicts Between OMP and CMM

Alarm Information
l Alarm code: 5400
l Alarm name: Configuration conflicts between OMP and CMM
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
l A slot is configured to OMP type in the CMM, but it is not configured to OMP type in
the database of the OMP.
l A slot is not configured to OMP type in the CMM, but it is configured to OMP type in
the database of the OMP.

System Impact
An exception exists in the communication with the OMP.

Handling Suggestion
1. On the OMP, re-configure the physical address of the OMP, or re-configure the data
on the CMM according to the configured physical address on the OMP.
2. Restart the GPBB0 board where the OMP is located. Then check whether the alarm
disappears.
l Yes: End alarm handling.

2-40

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l No: Contact ZTE for help.

2.1.55 5405 Clock Board Phase-lock Loop Work Mode Is Abnormal

Alarm Information
l Alarm code: 5405
l Alarm name: Clock board phase-lock loop work mode is abnormal
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l There is no available reference source.
l The clock distribution line is incorrect, or a self loop exists.
l The level-2 clock locks the level-3 clock.

System Impact
The specified reference clock fails to be clocked.

Handling Suggestion
1. Check whether the corresponding clock reference is correctly input.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Replace the clock daughter card. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
3. Correctly input this clock reference. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.56 5407 The Board Is Power Off

Alarm Information
l Alarm code: 5407
l Alarm name: The board is power off
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
HOST receives poweroff command from IPMC. The probable reason is as follows.
l Powered off by NCMM.
l Power control.

2-41

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
The board where the slot is located or CPU running is abnormal. Related services cannot
be provided.

Handling Suggestion
1. Check whether the board is online.
l Yes: Go to Step 2.
l No: Insert the board.
2. Check whether the extractor is open.
l Yes: Go to Step 3.
l No: Close the extractor.
3. Check whether the board is powered off by NCMM.
l Yes: Go to Step 4.
l No: Contact ZTE for help.
4. Powered on by NCMM. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.57 5632 The Hard Disk Used-Rate Is Over Threshold

Alarm Information
l Alarm code: 5632
l Alarm name: The hard disk used-rate is over threshold
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
The used space of the hard disk exceeds the set alarm threshold.

System Impact
The hard disk fails to work properly.

Handling Suggestion
1. In the hard-disk-full alarm settings under hard disk parameter settings, check severity
configuration of the hard disk usage and see whether the hard disk use threshold is
set lower than the expected.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Raise the threshold. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.

2-42

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

3. Clear the hard disk by deleting unused files or move them to other external devices.
Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.58 5633 File System Is Abnormal

Alarm Information
l Alarm code: 5633
l Alarm name: File system is abnormal
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
l The hard disk doesn't exist.
l The hard disk isn't formatted.
l The file system is abnormal.

System Impact
Memory capability is affected. The system may not operate properly, some processes may
not operate properly, and data may be lost. When the alarm occurs, the active board may
be switched over to the standby one.

Handling Suggestion
l If no hard disk exists, install a hard disk. Check whether the alarm is cleared.
à Yes: End alarm handling.
à No: Contact ZTE for help.
l If the hard disk is not formatted, format it. Check whether the alarm is cleared.
à Yes: End alarm handling.

à No: Contact ZTE for help.

l If the alarm is caused by other reasons, contact ZTE for help.

2.1.59 5634 The Hard Disk on Board Gets IO Error

Alarm Information
l Alarm code: 5634
l Alarm name: The hard disk on board gets IO error
l Severity: Minor
l Alarm type: Equipment alarm

2-43

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Probable Cause
The file system of the hard disk has an error in the read/write operation.

System Impact
The hard disk cannot operate properly. When the alarm is reported, active/standby board
changeover may occur.

Handling Suggestion
1. Check whether the hard disk is broken.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Repair the hard disk. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Replace the hard disk. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.60 5645 Subcard Is Abnormal

Alarm Information
l Alarm code: 5645
l Alarm name: Subcard is abnormal
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
The subcard is abnormal or is formatting flash.

System Impact
The subcard can not operate properly.

Handling Suggestion
1. Check whether the subcard is formatting flash.
l Yes: Waiting for completion of formatting, end alarm handling.
l No: Go to Step 2.
2. Check whether the subcard is error.
l Yes: Go to Step 3.
l No: Contact ZTE for help.
3. Repair the subcard. Then check whether the alarm disappears.
l Yes: End alarm handling.

2-44

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l No: Contact ZTE for help.

2.1.61 5666 Error Packets of MAC Is Higher Than the Specified

Threshold
Alarm Information
l Alarm code: 5666
l Alarm name: Error packets of MAC is higher than the specified threshold
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
Error packets of MAC is higher than the specified threshold.

System Impact
The MAC port cannot be used or packets flow is limited.

Handling Suggestion
1. Check the connection between the port on this board and the remote end one if it is
correct.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Replace the board on the local end or the interface on the remote end. Then check
whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Replace the remote board or the interface on the local end. Then check whether the
alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.62 5670 Oscillator Status Abnormal

Alarm Information
l Alarm code: 5670
l Alarm name: Oscillator status abnormal
l Severity: Critical
l Alarm type: Equipment alarm

Probable Cause
Oscillator stops oscillating or suffers from frequency deviation.

2-45

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
Board cannot operate properly with this crucial device error.

Handling Suggestion
Replace the board. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.63 5672 Clock Source for SyncE Is Not Available

Alarm Information
l Alarm code: 5672
l Alarm name: Clock source for SyncE is not available
l Severity: Critical
l Alarm type: Equipment alarm

Probable Cause
l No ESMC PDU packet is received within 5 seconds.
l The received SSM CODE is DNU.
l The port rate is 10 M.
l The physical link of the port is broken.

System Impact
The system cannot obtain the clock from the clock source.

Handling Suggestion
1. Check whether the physical link is normal.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Re-configure the port or re-connect it. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.64 5673 The Setting of the Dial Switch Is Changed

Alarm Information
l Alarm code: 5673
l Alarm name: The setting of the dial switch is changed
l Severity: Major
l Alarm type: Equipment alarm

2-46

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Probable Cause
The setting of the dial switch on the CDM board has been changed.

System Impact
The boards can not operate properly.

Handling Suggestion
1. Check whether the setting of the dial switch on the CDM board is changed or not.
l Yes: Go to Step 2.
l No: Go to Step 5.
2. Check whether the new rack and shelf configuration in the CDM jumper configuration
is correct.
l Yes: Go to Step 3.
l No: Go to Step 4.
3. Reset CMM board, then reset all the boards in the same shelf. Then check whether
the board can be powered on normally.
l Yes: Wait for alarm recovery, and then end alarm handling.
l No: Go to Step 5.
4. Update the setting of the dial switch on the CDM board to the configuration value.
Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 5.
5. Replace the CMM board and make the correct dial witch setting. Then check whether
the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.65 5674 Sending or Receiving Packets Between Administration

Port and CPU Control Port Failed
Alarm Information
l Alarm code: 5674
l Alarm name: Sending or receiving packets between administration port and CPU
control port failed
l Severity: Critical
l Alarm type: Equipment alarm

Probable Cause
l The switching chip fails.
l The connection between the switching chip and the CPU has some software or
hardware problem.

2-47

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
Board island effect may occur, and detection packets or messages sent between cascaded
shelves may be abnormal. Thus, services will be interrupted.

Handling Suggestion
Replace the board. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.66 5760 Ethernet Port's Link Is Down

Alarm Information
l Alarm code: 5760
l Alarm name: Ethernet port's link is down
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
The physical link of Ethernet port is disconnected.

System Impact
The link is disconcerted.

Handling Suggestion
1. Check whether the link is connected.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Reconnect the physical link to the Ethernet port. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether the port mode is reasonably configured.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Modify the port mode. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-48

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

2.1.67 5761 The Speed Mode of Ethernet Port Doesn't Match With
Settings
Alarm Information
l Alarm code: 5761
l Alarm name: The speed mode of Ethernet port doesn't match with settings
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
l The duplex mode at the remote end is not set successfully.
l The working mode configuration of the external port is not valid.
l The working mode of the port is not set to duplex mode.

System Impact
Port does not work on the speed mode selected.

Handling Suggestion
1. Check whether the speed work mode on the remote end match the speed work mode
on the local end.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Modify the speed work mode setting on the remote end, which should match the speed
work mode setting on the local end. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check if the speed work mode on the local end is correctly set.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Modify the speed work mode setting on the local end is correctly. Then check whether
the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.68 5768 All of the Board Input Clocks Which Have the Same
Frequency Are Lost
Alarm Information
l Alarm code: 5768
l Alarm name: All of the board input clocks which have the same frequency are lost
l Severity: Major

2-49

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Alarm type: Equipment alarm

Probable Cause
l The board is not in place (not properly inserted into the slot).
l Two clock boards at the same shelf do not output clock.
l The clock boards are faulty.
l The clock line is faulty.
l The board is faulty.

System Impact
The board fails to be synchronized with the system clock and fails to work properly, leading
to UE access failure and interruption of ongoing services.

Handling Suggestion
1. Check whether the clock boards in the same shelf are normal, and whether the clock
cable is properly connected.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Replace the boards. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.69 5769 The Master and Slave Mode of Ethernet Port Doesn't
Match With Settings
Alarm Information
l Alarm code: 5769
l Alarm name: The master and slave mode of Ethernet port doesn't match with settings
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
The master and slave mode of the port doesn't match with settings.

System Impact
Port does not work on the master and slave mode which is set.

Handling Suggestion
1. Check whether the master/slave mode is configured consistently and correctly at both
ends.
l If the configuration is consistent and correct, contact ZTE for help.

2-50

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l If the configuration is not consistent or correct, go to Step 2.

2. Modify the master/slave mode configuration to ensure that the configuration is consis-
tent and correct at both ends. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.70 5770 The OMP Board Doesn't Have Any OMC Port
Alarm Information
l Alarm code: 5770
l Alarm name: The OMP board doesn't have any OMC port
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
The OMP board doesn't have OMC port.

System Impact
The OMP board could not communicate by OMC port.

Handling Suggestion
1. Check the rear board to make sure it is correct and inserted well.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Plug/unplug the rear board. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether the hardware of the board is normal, and whether it supports OMC
port.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Make sure the board supports OMC port. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.71 5771 The Duplex Mode of Ethernet Port Doesn't Match With
Settings
Alarm Information
l Alarm code: 5771
l Alarm name: The duplex mode of Ethernet port doesn't match with settings

2-51

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
l The duplex mode at the remote end is not set successfully.
l The working mode configuration of the external port is not valid.
l The working mode of the port is not set to duplex mode.

System Impact
Port does not work on the duplex mode which is set.

Handling Suggestion
1. In the Terminal window, run the SHOW ENETPORTPARA command to check
whether the Work Mode on the local end match the Work Mode on the remote end.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Run the SET ENETPORTPARA command to modify the Work Mode. Make sure the
Work Mode of the local end match that of the remote end. Then check whether the
alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.72 5772 Board Device Fault

Alarm Information
l Alarm code: 5772
l Alarm name: Board device fault
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
This is may be the hardware fault.

System Impact
Board works abnormal.

Handling Suggestion
Replace the board. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-52

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

2.1.73 5773 High CRC Error Rate at E1/T1 Bottom Layer

Alarm Information
l Alarm code: 5773
l Alarm name: High CRC error rate at E1/T1 bottom layer
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
The E1/T1 link is faulty or the uplink equipment is faulty.

System Impact
The receiving signals over this trunk are interrupted.

Handling Suggestion
1. Check whether the trunk link at the local end is faulty, and eliminate the primary fault.
Then check whether the alarm disappears.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Handle the problem according to the handling suggestion of the alarm on the local
trunk link. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether there is any other equipment fault in the uplink direction of this trunk
link.
l Yes: Go to Step 4.
l No: Contact ZTE for help.
4. Handle the problem according to the handling suggestion of other equipment fault in
the uplink of the trunk. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.74 5774 High FAS Error Rate at E1/T1 Bottom Layer

Alarm Information
l Alarm code: 5774
l Alarm name: High FAS error rate at E1/T1 bottom layer
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
The E1/T1 link is faulty or the uplink equipment is faulty.

2-53

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
The receiving signals over this trunk are interrupted.

Handling Suggestion
1. Check whether the trunk link at the local end is faulty, and eliminate the primary fault.
Check whether the alarm disappears.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Handle the problem according to the handling suggestion of the alarm on the local
trunk link. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether there is any other equipment fault in the uplink direction of this trunk
link.
l Yes: Go to Step 4.
l No: Contact ZTE for help.
4. Handle the problem according to the handling suggestion of other equipment fault in
the uplink of the trunk. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.75 5775 High EBIT Error Rate at E1 Bottom Layer

Alarm Information
l Alarm code: 5775
l Alarm name: High EBIT error rate at E1 bottom layer
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
The E1 link is faulty or the downlink equipment is faulty.

System Impact
The receiving signals over this trunk are interrupted.

Handling Suggestion
At this moment, at least CRC bit errors exist at the remote end. View and record the alarms
at the remote end. Check whether the intermediate transmission equipment of this trunk
link is faulty.
l Yes: Contact the transmission equipment maintenance personnel to handle the
related fault.
l No: Contact ZTE for help.

2-54

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

2.1.76 5784 Please Reboot the Board After You Have Saved the
New Configuration to Make It Effective
Alarm Information
l Alarm code: 5784
l Alarm name: Please reboot the board after you have saved the new configuration to
make it effective
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
The configuration is changed.

System Impact
The new configuration does not take effect.

Handling Suggestion
1. Save the configuration and restart the board manually. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Use the old configuration. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.77 5785 GPS Module Is Abnormal

Alarm Information
l Alarm code: 5785
l Alarm name: GPS module is abnormal
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
l The GPS module is in star searching state.
l The number of stars found by the GPS module is less than 4.
l The GPS PP1S output jitter is extremely bad.
l The GPS antenna feeder is abnormal.

System Impact
The system has no reference clock and the system clock cannot be synchronized.

2-55

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Handling Suggestion
1. Check whether the GPS antenna input and the receiver are normal.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore the GPS antenna input and the receiver to be in normal state. Then check
whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.78 5786 Flash-Formatting Warning From USCC/GFC/XFC

Subcard
Alarm Information
l Alarm code: 5786
l Alarm name: Flash-formatting warning from USCC/GFC/XFC subcard
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
The subcard is formatting the Flash.

System Impact
The subcard cannot work properly.

Handling Suggestion
Check whether the subcard is formatting the flash.
l Yes: Waiting for completion of formatting, end alarm handling.
l No: Contact ZTE for help.

2.1.79 5787 General Fault and Warning From USCC/GFC/XFC

Subcard
Alarm Information
l Alarm code: 5787
l Alarm name: General fault and warning from USCC/GFC/XFC subcard
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
The status of the subcard is abnormal.

2-56

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

System Impact
The subcard cannot work properly.

Handling Suggestion
1. Check whether the subcard is faulty.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Replace the subcard. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.80 5788 Serious Fault and Warning From USCC/GFC/XFC

Subcard
Alarm Information
l Alarm code: 5788
l Alarm name: Serious fault and warning from USCC/GFC/XFC subcard
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
The status of the subcard is abnormal.

System Impact
The subcard cannot work properly.

Handling Suggestion
1. Check whether the subcard is faulty.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Replace a subcard. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.81 5789 Critical Fault and Warning From USCC/GFC/XFC

Subcard
Alarm Information
l Alarm code: 5789
l Alarm name: Critical fault and warning from USCC/GFC/XFC subcard

2-57

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Severity: Critical
l Alarm type: Equipment alarm

Probable Cause
The status of the subsard is abnormal.

System Impact
The subcard cannot work properly.

Handling Suggestion
1. Check whether the subcard is faulty.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Replace the subcard. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.82 5790 The Configuration of Clock Shelf Function Is Error

Alarm Information
l Alarm code: 5790
l Alarm name: The configuration of clock shelf function is error
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
l Multiple shelves holding clock daughter cards in the system are configured to master
clock shelves.
l The master/slave clock shelf type is not configured.
l The master/slave clock shelf type is set to "self-adaptive".

System Impact
The clock daughter card cannot provide clock to the system normally.

Handling Suggestion
1. View details of the alarm to identify the reason:
l If multiple shelves holding clock daughter cards in the system are configured to
master clock shelves, go to Step 2.
l If the master/slave clock shelf type is not configured, go to Step 3.
l If the master/slave clock shelf type is "self-adaptive", go to Step 4.
l In case of other reasons, contact ZTE for help.

2-58

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

2. Modify the master/slave clock shelf configuration to ensure that there is only one
master clock shelf in the system. Then go to Step 5.
3. Configure the master/slave clock shelf information. Then go to Step 5.
4. Modify the master/slave clock shelf configuration. Then go to Step 5.
5. Reset the clock daughter card (including its partner card) to validate the configuration.
Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.83 5791 TX Power High Alarm

Alarm Information
l Alarm code: 5791
l Alarm name: TX power high alarm
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l The optical module is faulty.
l The transmission equipment is faulty.

System Impact
This fault affects data transmission of the optical module and may burn the optical module
on the opposite end of the connection.

Handling Suggestion
1. Replace the local optical module, and check whether the alarm is cleared.
l Yes: End alarm handling.
l No: Go to Step 2.
2. A problem may exist in the transmission equipment. Contact the maintenance
personnel of the transmission equipment to troubleshoot the fault of the transmission
equipment.

2.1.84 5792 TX Power Low Alarm

Alarm Information
l Alarm code: 5792
l Alarm name: TX power low alarm
l Severity: Minor
l Alarm type: Equipment alarm

2-59

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Probable Cause
l The optical module is faulty.
l The transmission equipment is faulty.

System Impact
This fault affects data transmission of the optical module.

Handling Suggestion
1. Replace the local optical module, and check whether the alarm is cleared.
l Yes: End alarm handling.
l No: Go to Step 2.
2. A problem may exist in the transmission equipment. Contact the maintenance
personnel of the transmission equipment to troubleshoot the fault of the transmission
equipment.

2.1.85 5793 RX Power High Alarm

Alarm Information
l Alarm code: 5793
l Alarm name: RX power high alarm
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l The configuration of the opposite optical module is faulty.
l The configuration of the optical fiber type is faulty.
l The optical module is faulty.

System Impact
This fault affects data transmission of the optical module and may burn the optical module.

Handling Suggestion
1. Check whether the opposite optical module is configured as too long transmission
distance.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Modify the configuration of the opposite optical module and check whether the alarm
is cleared.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Replace the opposite optical module and check whether the alarm is cleared.

2-60

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l Yes: End alarm handling.

l No: Go to Step 4.
4. Check the optical fiber type and check whether the configuration is wrong (should use
the single-mode optical fiber).
l Yes: Go to Step 5.
l No: Go to Step 6.
5. Modify the optical fiber type and check whether the alarm is cleared.
l Yes: End alarm handling.
l No: Go to Step 6.
6. Replace the local module and check whether the alarm is cleared.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.86 5794 RX Power Low Alarm

Alarm Information
l Alarm code: 5794
l Alarm name: RX power low alarm
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l The configuration of the opposite optical module is faulty.
l The configuration of the optical fiber type is faulty.
l The optical module is faulty.

System Impact
This fault affects data transmission of the optical module.

Handling Suggestion
1. Check whether the opposite optical module is configured as too short transmission
distance.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Modify the configuration of the opposite optical module and check whether the alarm
is cleared.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Replace the opposite optical module and check whether the alarm is cleared.
l Yes: End alarm handling.
l No: Go to Step 4.
4. Check the optical fiber type and check whether the configuration is wrong (should use
the multi-mode optical fiber).

2-61

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Yes: Go to Step 5.
l No: Go to Step 6.
5. Modify the optical fiber type and check whether the alarm is cleared.
l Yes: End alarm handling.
l No: Go to Step 6.
6. Replace the local module and check whether the alarm is cleared.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.87 5795 The Optical Transceiver Transmitter Has Detected a

Fault
Alarm Information
l Alarm code: 5795
l Alarm name: The optical transceiver transmitter has detected a fault
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l The optical module is faulty.
l The transmission equipment is faulty.

System Impact
This fault affects data transmission of the optical module.

Handling Suggestion
1. Remove the local module and reinstall it.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Replace the local module and check whether the alarm is cleared.
l Yes: End alarm handling.
l No: Go to Step 3.
3. A problem may exist in the transmission equipment. Contact the maintenance
personnel of the transmission equipment to troubleshoot the fault of the transmission
equipment.

2.1.88 5796 Clock of This Board Is Abnormal

Alarm Information
l Alarm code: 5796
l Alarm name: Clock of this board is abnormal

2-62

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l Severity: Critical
l Alarm type: Equipment alarm

Probable Cause
l The clock extraction reference is changed. For example, the clock output is closed by
the interface board when the optical port is faulty, or configuration of clock extraction
is modified at NMS, which will change the input of clock daughter card.
l The clock daughter card has faults which changes clock output.
l The board phase-lock loop has hardware faults.
l The oscillator may stop oscillating or meet frequency deviation.

System Impact
The service clock is inconsistent witch the system clock, and the service carried by the
board will be interrupted, and this board can not work normally.

Handling Suggestion
1. In the Fault Management window of the LMT, check whether there is related clock
alarm.
l Yes: Handle the alarm by referring to the corresponding suggestions.
l No: Go to Step 2.
2. In the Fault Management window of the LMT, check whether there is related alarm of
the optical port for clock extraction.
l Yes: Handle the alarm by referring to the corresponding suggestions.
l No: Go to Step 2.
3. Replace the board. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.89 5797 The Hard Disk Is Abnormal

Alarm Information
l Alarm code: 5797
l Alarm name: The hard disk is abnormal
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
l The hard disk doesn't exist.
l The hard disk has serious fault cause the system not to find it.
l The SMART of the hard disk is abnormal.

2-63

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
The hard disk can not work normally.

Handling Suggestion
1. In the Fault Management window of the LMT, check the alarm additional information
to make sure the abnormal hard disk location and the abnormal reason.
l If the abnormal reason is that the hard disk doesn't exist, go to Step 2.
l If the abnormal reason is that SMART is abnormal, go to Step 3.
2. Check that whether the hard disk exist or not.
l Yes: Go to Step 3.
l No: Go to Step 4.
3. Exchange the hard disk. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
4. Insert a new hard disk. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.90 5798 The Raid of Hard Disks Is Abnormal

Alarm Information
l Alarm code: 5798
l Alarm name: The raid of hard disks is abnormal
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
l The hard disk doesn't exist.
l The hard disk has serious fault cause the system not to find it.
l The SMART of the hard disk is abnormal.
l The Disks are not in RAID mode.
l Other unknown reasons.

System Impact
The hard disk can not work normally.

Handling Suggestion
1. In the Fault Management window of the LMT, check the alarm additional information
to make sure the abnormal reason.
l If the abnormal reason is that “The Disks are not in RAID mode”, go to Step 2.
l If the abnormal reason is unknown, contact ZTE for help.
l Otherwise, go to Step 3.

2-64

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

2. Set RAID mode. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Exchange the hard disk according to the abnormal reason. And then check whether
the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.91 5799 Hard Disk Online

Alarm Information
l Alarm code: 5799
l Alarm name: Hard disk online
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
l Hard disk is inserted.
l SAS controller is abnormal.

System Impact
l The hard disk can not work normally.
l The board reboots.

Handling Suggestion
Make sure whether the hard disk is inserted.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.92 5800 Hard Disk Offline

Alarm Information
l Alarm code: 5800
l Alarm name: Hard disk offline
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
l Hard disk is removed.
l SAS controller is abnormal.

2-65

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
l The hard disk can not work normally.
l The board reboots.

Handling Suggestion
Make sure whether the hard disk is removed.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.93 5801 Memory Size Is Abnormal

Alarm Information
l Alarm code: 5801
l Alarm name: Memory size is abnormal
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
Memory size of SPD is not equal to visible memory size of operating system.

System Impact
If the memory size is too small, the board cannot operate properly.

Handling Suggestion
1. Replace the board memory and re-power on the board. Check whether the alarm is
cleared.
l Yes End alarm handling.
l No: Go to Step 2.
2. Replace the board and check whether the alarm is cleared.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.94 5908 Lack of Version

Alarm Information
l Alarm code: 5908
l Alarm name: Lack of version
l Severity: Minor
l Alarm type: Processing error alarm

2-66

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Probable Cause
The version information returned by the version server is incomplete.

System Impact
Some function of the board is lost.

Handling Suggestion
1. Check the version server logs to see whether the version file is unavailable.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Add the version file and activate it. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.95 5909 Download Version Failed

Alarm Information
l Alarm code: 5909
l Alarm name: Download version failed
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
Downloading the version file from the version server failed.

System Impact
Some function of the board is lost.

Handling Suggestion
1. View the logs of the board to find the version file that failed to be downloaded.
2. Check whether the version file exists on the version server.
l Yes: Go to Step 3.
l No: Go to Step 4.
3. Check whether there is any communication alarm.
l Yes: Handle the alarm by referring to the corresponding handling suggestions.
l No: Contact ZTE for help.
4. Add the version file and activate it. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-67

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

2.1.96 5910 Process Execute Failed

Alarm Information
l Alarm code: 5910
l Alarm name: Process execute failed
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
Fails to start the process.

System Impact
Some function of the board is lost.

Handling Suggestion
Check the log file to find the corresponding failure code and then analyze the reason.

2.1.97 5930 Version Load Failed

Alarm Information
l Alarm code: 5930
l Alarm name: Version load failed
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
Special firmware version load failed.

System Impact
Special firmware running error.

Handling Suggestion
1. In the Fault Management window of the LMT, check additional information of the alarm
information, whether the reason is "no DSP version configuration", "no DSP self-check
version", "no DSP TFTP version" or "no DSP service version".
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Load, activate and enable the version package. And then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 3.

2-68

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

3. Change hardware device (board of subcard). And then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.98 5932 The Third Party Firmware Version Load Failed

Alarm Information
l Alarm code: 5932
l Alarm name: The third party firmware version load failed
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
The third party firmware version load failed.

System Impact
The third party firmware operates improperly.

Handling Suggestion
1. Check whether the third party firmware version configuration is correct.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Re-configure the third party firmware version, and check whether the alarm is
eliminated.
l Yes: End alarm handing.
l No: Contact ZTE for help.

2.1.99 5933 Shutdown Board to Valid the Third Party Firmware

Alarm Information
l Alarm code: 5932
l Alarm name: The third party firmware version load failed
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
The new firmware takes effect only after the board is power off.

System Impact
The new version of the third party firmware does not take effect.

2-69

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Handling Suggestion
Power off the board and power on it again, and then check whether this alarm disappears.
l Yes: End alarm handing.
l No: Contact ZTE for help.

2.1.100 7168 Port Trunk Failed

Alarm Information
l Alarm code: 7168
l Alarm name: Port trunk failed
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l PP board port aggregation failure: Switch Board is not in place, or port transceiver
package exception.
l Switch board stack port aggregation failure: Mate Board is not in place, or stack port
transceiver package exception.

System Impact
l As for normal board, the link connected with media switch board does not work.
l As for switch board, if all of the stack ports trunk failed, all ports of the poor board do
not work.

Handling Suggestion
1. In the Fault Management window, view the alarm details and determine the probable
cause is PP board port aggregation failure or switch board stack port aggregation
failure.
l PP board port aggregation failure: Go to Step 2.
l Switch board stack port aggregation failure: Go to Step 3.
2. Check whether the switch boards in the right and left slots are in place.
l Yes: Contact ZTE for help.
l No: Normal alarm, no handling is required.
3. Check whether the mate board is in place.
l Yes: Contact ZTE for help.
l No: Normal alarm, no handling is required.

2.1.101 7169 Inner Port Error

Alarm Information
l Alarm code: 7169

2-70

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l Alarm name: Inner port error

l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l The duplex mode of the internal port on another slot in the same shelf with the
switching board is exceptional, and cannot restore to be normal by itself.
l The rate of the internal port on another slot in the same shelf with the switching board
is exceptional, and cannot restore to be normal by itself.
l The duplex mode of the network port on the PP board is exceptional, and cannot
restore to be normal by itself.
l The rate of the network port on the PP board is exceptional, and cannot restore to be
normal by itself.

System Impact
l The internal media-plane streams in this board cannot be properly processed. The
services on this board are interrupted.
l If this alarm occurs because of faults in the port or the connection, the services on this
board are interrupted.
l If this alarm occurs because of too high CPU load or service load, the services are
delayed or even interrupted.

Handling Suggestion
Restart the board where this alarm occurs. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.102 7170 Trunk Connect Asymmetry

Alarm Information
l Alarm code: 7170
l Alarm name: Trunk connect asymmetry
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
Ports in a trunk are asymmertic.

System Impact
The system does not operate properly.

2-71

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Handling Suggestion
1. Check whether the port connections are correct.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Change the port connections. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.103 7171 Outer Media Trunk Failed

Alarm Information
l Alarm code: 7171
l Alarm name: Outer media trunk failed
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
Media ports between the shelf are not linked or trunk failed.

System Impact
Adjunct shelf's media work abnormally.

Handling Suggestion
1. Check both media switch board's out ports are connected or not.
l Yes: Go to Step 3.
l No: Go to Step 2
2. Add fiber connection at the vacant ports. And then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check fiber connection and optical module, change the poor. And then check whether
the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 4.
4. Check whether the gateway of the NE is configured correctly.
l Yes: Contact ZTE for help.
l No: Go to Step 5.
5. Configure the correct gateway. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-72

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

2.1.104 7172 Port Physical State Restore

Alarm Information
l Alarm code: 7172
l Alarm name: Port physical state restore
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
Port physical state restore.

System Impact
Switch work abnormally.

Handling Suggestion
1. Wait for 30 seconds and check whether the alarm is cleared.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Restart the board and wait for the OK indicator on the board to be lit. Wait for another
20 minutes and check whether the alarm is cleared.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Replace the board and wait for the OK indicator on the board to be lit. Wait for another
20 minutes and check whether the alarm is cleared.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.105 7173 Control panel port down

Alarm Information
l Alarm code: 7173
l Alarm name: Control panel port down
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
The control-plane port is down.

System Impact
The control-plane communication of the board is abnormal.

2-73

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Handling Suggestion
1. Check whether the port and the connection between the port and the control-plane
switching board are normal.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore the port and the connection between the port and the control-plane switching
board. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.1.106 7174 Connect Port Loopback

Alarm Information
l Alarm code: 7174
l Alarm name: Connect port loopback
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
A loopback exists in the wiring between inter-shelf cascading ports.

System Impact
The inter-shelf port loopback may result in network storms.

Handling Suggestion
1. Check whether there is a loopback in the wiring between inter-shelf cascading ports.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Remove the cable on this port and check whether the alarm is cleared.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2 10000~99999
2.2.1 18944 The State of PVC Link Is Faulty
Alarm Information
l Alarm code: 18944
l Alarm name: The state of PVC link is faulty
l Severity: Minor

2-74

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l Alarm type: Processing error alarm

Probable Cause
l PVC connection for the equipment is loose or disconnected. PVC connection falls
into the following three types.
à Fiber connection, carried by optical interface.
à E1/T1 connection, carried by IMA port.
à Fiber connection, carried by IMA port.
l The Continuity Check (CC) function is started at the local end, but not started at the
remote end.

System Impact
The PVC is faulty. All services on the PVC are interrupted.

Handling Suggestion
1. In the Terminal window, Locate the faulty port according to the PVC ID given in alarm
details.
For example, the PVC ID is 1. Locate the PVC whose ID is 1. View the related
subsystem ID, unit ID, ATM port ID to locate the corresponding interface board and
port.
2. Check the relevant equipment based on the physical bearer of the port.
l The faulty PVC port is carried by optical interface: Go to Step 3.
l The faulty PVC port is carried by IMA port: Go to Step 5.
3. check whether fiber connector and interface are in good contact.
l Yes: Go to Step 4.
l No: Go to Step 6.
4. Replace the fiber. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 6.
5. Check if the following alarms occur to the corresponding IMA group/link.
l Yes: Handle it according to the its handling suggestion.
l No: Go to Step 6.
6. Check whether the equipment power-on at remote end is successful.
l Yes: Go to Step 7.
l No: Handle the alarm according to interconnection equipment maintenance
manual.
7. Check if the PVC status at remote end is successful.
l Yes: Go to Step 8.
l No: Handle the alarm according to interconnection equipment maintenance
manual.
8. Deactivate CC test at local end, or activate CC test at remote end. Then check whether
the alarm disappears.

2-75

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Yes: End alarm handling.

l No: Contact ZTE for help.

Note:
l Deactivate CC test at local end
Initiate “TEST PVC A/D CC”. When configuring test parameters, select inactivate
CC for AD type, and select BTOA for direction (A indicates local end and B
indicates remote end).
l Activate the peer CC.
In the diagnosis test window, originate the PVC CC functional test, select activate
CC , and for AD type; select BTOA for direction

2.2.2 19207 Fail to Configure Near-End IMA Group

Alarm Information
l Alarm code: 19207
l Alarm name: Fail to configure near-end IMA group
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
Because the group parameters configured for the near-end IMA group does not match that
configured for the far-end IMA group, and the IMA configuration parameters sent by the
remote end through ICP cells are rejected. The system enters the Config_Aborted status.

System Impact
All services on the IMA port are interrupted.

Handling Suggestion
1. In the Fault Management window of the LMT, select the Real-time Current Alarm
Monitoring tab. Double-click the alarm information, and the Detail Information tab
pops up, where information of the faulty IMA group is given.
2. In the Terminal window of the LMT, locate the corresponding IMA group according to
the information given in alarm Detail Information. Check whether the configuration
of the following parameters at both ends is inconsistent,.
l “Local OAM Label”
l “TX Frame Length (cell)”
l “RX Frame Length (cell)”
l “Local Symmetry”

2-76

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l Yes: Contact ZTE for help.

l No: Go to Step 3.
3. Modify configuration at either end to keep consistency. After the configuration is
modified, check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.3 19208 Fail to Fix the Time of Near-End IMA Group

Alarm Information
l Alarm code: 19208
l Alarm name: Fail to fix the time of near-end IMA group
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
The far-end IMA-group clock mode sent by the far end through ICP cells does not match
the near-end one. For example, Independent Transmit Clock (ITC) at the far end does not
match the Common Transmit Clock (CTC) at the near end.

System Impact
IMA link may fail to be established.

Handling Suggestion
1. Check whether the clock mode at the near end matches that at the far end.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Modify the configuration to make the clock modes match. And then check whether the
alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.4 19212 Near-End Transmitting Link Is Broken

Alarm Information
l Alarm code: 19212
l Alarm name: Near-end transmitting link is broken
l Severity: Major
l Alarm type: Communication alarm

2-77

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Probable Cause
When a transmitting link is not connected to the far-end IMA group like other links in a
group, this alarm appears.

System Impact
IMA link fails to be established.

Handling Suggestion
1. Check whether the IMA chip works properly, and whether each link can be connected
to the far-end IMA group properly.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Configure the data again. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.5 19213 Near-End Receives the LIF Alarm of the Link

Alarm Information
l Alarm code: 19213
l Alarm name: Near-end receives the LIF alarm of the link
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
A physical fault or connection error occurs on the 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
1. Refer to user networking plan to see whether connection error exists.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Connect again according to network planning. And then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 3.

2-78

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

3. In the Fault Management window of the LMT, check whether any E1-related alarm
exists in the board.
l Yes: Go to Step 4.
l No: Contact ZTE for help.
4. Solve the alarm according the relevant suggestions. And then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.6 19214 Near-End Receives the LODS Alarm of the Link

Alarm Information
l Alarm code: 19214
l Alarm name: Near-end receives the LODS alarm of the link
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
l The input clock does not work properly.
l The transmission quality of the physical link is poor.

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
In the Fault Management window of the LMT, view the detailed alarm information. In
the detailed alarm information, the IMA chip ID, the IMA group ID, the IMA link ID in the
IMA group, and the E1 ID are given. Locate the faulty IMA link according to the given
information.

1. Check whether the R1 to R4 indicator on the FSWA1 board is green.

Note:

The indicator is green means the clock works properly.

l Yes: Go to Step 2.
l No: Go to step 3.
2. Reset or replace the FSWA1 board. And then check whether the alarm disappears.

2-79

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Yes: End alarm handling.

l No: Go to Step 3.
3. In the Fault Management window of the LMT, check whether any clock-related alarm
exists in the switching board.
l Yes: Go to Step 4.
l No: Go to Step 5.
4. Handle it according to its handling suggestion. And then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 5.
5. In the Fault Management window of the LMT, check whether any E1-related alarm
exists.
l Yes: Handle it according to its handling suggestion.
l No: Contact ZTE for help.

2.2.7 19215 Near-End Receives the RDI Alarm of the Link

Alarm Information
l Alarm code: 19215
l Alarm name: Near-end receives the RDI alarm of the link
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
l The far-end IMA link is not in the active status.
l The far-end IMA link has faults in the receiving direction.

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
1. In the Fault Management window of the LMT, view the detailed alarm information. In
the detailed alarm information, the IMA chip ID, the IMA group ID, the IMA link ID in
the IMA group, and the E1 ID are given. Locate the faulty IMA link according to the
given information.
2. Check whether the relevant far-end receiving link connected with the local-end link is
in active state by referring to the operation guide of the far-end equipment.
l Yes: Contact ZTE for help.
l No: Go to Step 3.
3. Activate the link. And then check whether the alarm disappears.
l Yes: End alarm handling.

2-80

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l No: Contact ZTE for help.

2.2.8 19216 Near-End Receives the Alarm That the Link Is in Trouble
Alarm Information
l Alarm code: 19216
l Alarm name: Near-end receives the alarm that the link is in trouble
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
If a near-end link in the receiving direction has faults, this alarm appears at the near end.

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
1. Check whether the IMA chip works properly, and whether each link can be connected
to the near-end IMA group properly.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Handle the problem. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.9 19218 Near-End Receives the Alarm That the Link Is Broken
Alarm Information
l Alarm code: 19218
l Alarm name: Near-end receives the alarm that the link is broken
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
When a receiving link is not connected to the far-end IMA group like other links in a group,
this alarm appears.

2-81

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

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
1. Check the receiving link connections at the both sides to see whether each receiving
link is connected to the far-end IMA group properly, and whether the expected local
E1 link is connected to the corresponding E1 link at the far end.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Find the fault causes and handle the problem. And then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.10 19223 Near-End IMA Group Has Faults

Alarm Information
l Alarm code: 19223
l Alarm name: Near-end IMA group has faults
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
All links in the IMA group are faulty, or the peer-end IMA group is faulty.

System Impact
The IMA Group does not work normally.

Handling Suggestion
1. Check whether the number of active links in an IMA group is less than the minimum
number of active links required for the IMA group to work properly.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Check the faulty links in the non-active status in the IMA group, and restore them to
be normal. Make sure that the number of active links in the IMA group is not less than
the minimum number required. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-82

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

2.2.11 19712 APS Channel Mismatch

Alarm Information
l Alarm code: 9712
l Alarm name: APS channel mismatch
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
Peer-end faults (configuration faults or devices do not support. The symptom is the
bridging channel that the remote end indicates through K2 is not the one required by the
local.)

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.

Handling Suggestion
1. Check fiber connection between two ends.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Restore the fiber connection between two ends, ensure and protect interconnection
between operating optical interfaces. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether the APS backup type (1+1 backup, 1:1 backup) configured locally is
consistent with that configured on the peer end.
l Yes: Go to Step 5.
l No: Go to Step 4.
4. Modify the APS backup type on both ends to be consistent. Then check whether the
alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 5.
5. Check whether the APS protection direction configured locally (uni-directional and
bi-directional) is consistent with the peer end.
l Yes: Go to Step 7.
l No: Go to Step 6.
6. Modify the APS protection direction of both ends to be consistent. Then check whether
the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 7.

2-83

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

7. Contact the maintenance personnel of the peer end to check whether the equipment
supports the APS, and whether the APS is configured properly and effective.
l Yes: Contact ZTE for help.
l No: Contact the maintenance engineer of the peer end for handling.

2.2.12 19713 APS Mode Mismatch

Alarm Information
l Alarm code: 19713
l Alarm name: APS mode mismatch
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
l Fiber connection is wrong.
l Configuration of APS backup mode at local end and opposite end is inconsistent.
l Configuration of APS protection direction at local end and opposite end is inconsistent.
l 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.

Handling Suggestion
1. Check fiber connection between two ends.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Restore the fiber connection between two ends, ensure and protect interconnection
between operating optical interfaces. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether the APS backup type (1+1 backup, 1:1 backup) configured locally is
consistent with that configured on the peer end.
l Yes: Go to Step 5.
l No: Go to Step 4.
4. Modify the APS backup type on both ends to be consistent. Then check whether the
alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 5.
5. Check whether the APS protection direction configured locally (uni-directional and
bi-directional) is consistent with the peer end.
l Yes: Contact ZTE for help.

2-84

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l No: Go to Step 6.
6. Modify the APS protection direction of both ends to be consistent. Then check whether
the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.13 19715 APS Channel Between Master and Slave Board

Becomes Errors
Alarm Information
l Alarm code: 19715
l Alarm name: APS channel between master and slave board becomes errors
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
l APS channel between master and slave board gets hardware fault.
l The connection on the backplane between the slot and the neighboring slot gets
errors.

System Impact
l APS function is affected.
l The board master to slave function is affected.

Handling Suggestion
1. Restart the board. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Replace the board. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Replace the neighboring board. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 4.
4. Change the location of two neighboring boards. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-85

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

2.2.14 19971 Request Gateway Information Timeout

Alarm Information
l Alarm code: 19971
l Alarm name: Request gateway information timeout
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
Requesting SCS for gateway configuration times out.

System Impact
The layer 3 forwarding table cannot be created.

Handling Suggestion
Wait for the system to recover automatically. Wait for 30s, check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.15 20225 Protocol Stack Requests for Configuration Information

Timeout
Alarm Information
l Alarm code: 20225
l Alarm name: Protocol stack requests for configuration information timeout
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
l Failed to register on the TCP/IP protocol stack.
l Failed to request for database configuration, such as SNTP configuration, DSCP
configuration and UID PPP configuration. Refer to detailed alarm information.
l Failed to request for interface configuration information, such as Ethernet interface.
Refer to detailed alarm information.
l Failed to initialize the TCP/IP protocol stack process resource, such as HDLC IC
initialization failure, or memory loss. Refer to detailed alarm information.

System Impact
Some functions of the board where the alarm is generated or that is described in the alarm
are unavailable. If the "configuration request type" in the additional information of the

2-86

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

alarm is "media-plane IP configuration", only media-plane functions are affected. For other
reasons, the whole TCP/IP protocol stack cannot be used.

Handling Suggestion
1. Wait for several minutes, and check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Check whether there exists the alarm "control plane communication abnormal between
board and its home module" (alarm code: 8393985).
l Yes: Handle the alarm by referring to the corresponding handling suggestions.
l No: Go to Step 3.
3. Plug the board again and reset the hardware. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 4.
4. Replace the fault board. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

Related Alarm
2.3.4 8393985 Control Plane Communication Abnormal Between Board and Its Home
Module

2.2.16 23042 The Number of Physical Alarms on the Board Exceeds

the Threshold
Alarm Information
l Alarm code: 23042
l Alarm name: The number of physical alarms on the board exceeds the threshold
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
There are too many alarm messages on this board, and the alarm pool saving the alarm
messages on this board is full.

System Impact
Alarm messages are lost, which has no influence on the service.

Handling Suggestion
1. Check whether there is any virtually configured resource that is not used temporarily.

2-87

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Delete the virtually configured resources. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.17 23050 Fan Device Absent

Alarm Information
l Alarm code: 23050
l Alarm name: Fan device absent
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l The fan is pulled out.
l The IPMB line between the CMM and the fan is exceptional.

System Impact
The temperature of the boards in the shelf increases, which may cause other faults.

Handling Suggestion
1. Check whether the fan on the slot where the alarm occurs is in place.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Insert the fan. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.18 23051 Power Unit Absent

Alarm Information
l Alarm code: 23051
l Alarm name: Power unit absent
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l The PEM is pulled out.
l The IPMB line between the CMM and the PEM is exceptional.

2-88

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

System Impact
Half of or even the whole shelf is powered off.

Handling Suggestion
1. Check whether the PEM on the slot where the alarm occurs is in place.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Insert the PEM. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.19 23106 Board Initialized Test Failed

Alarm Information
l Alarm code: 23106
l Alarm name: Board initialized test failed
l Severity: Critical
l Alarm type: Equipment alarm

Probable Cause
The board is faulty.

System Impact
The board cannot be used.

Handling Suggestion
1. Check the alarm information and see whether the memory fails.
l Yes: Go to Step 2.
l No: Go to Step 4.
2. Plug the memory bank again and power on the device. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Replace the memory bank with a new one and power on the device. Then check
whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 4.
4. Replace and re-power on the board. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Record current alarm information, Contact ZTE for help.

2-89

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

2.2.20 25600 Connection Check Be Disabled in Board

Alarm Information
l Alarm code: 25600
l Alarm name: Connection check be disabled in board
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
After the connection check function is disabled, it is not enabled.

System Impact
The connection check function is disabled. Connection errors cannot be detected
automatically and thus sometimes connections cannot heal actively.

Handling Suggestion
1. Check whether the "PP_DbgDisableConnCheck()" command has been executed on
the board.
l Yes: Please input "PP_DbgEnableConnCheck()"on the board.
l No: Go to Step 2.
2. Check whether some functions are executed in pairs on the background. For example,
trunk loop delay check function, TNet diagnosis function, appointed resource loop
function, and monitor voice function.
l Yes: Contact ZTE for help.
l No: Execute these functions in pairs.

2.2.21 25602 Abnormal Half-Fixed Connection Changes

Alarm Information
l Alarm code: 25602
l Alarm name: Abnormal half-fixed connection changes
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
l The line clock of the shelf where this board is located suffers from exceptional jitter.
l A hardware fault occurs on the switching chip of this board.

System Impact
The links using exceptional connection are broken. The services on the links using
exceptional connection are impacted.

2-90

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Handling Suggestion
1. Check whether the chip clock works properly.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Replace the connection chip or board. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.22 25856 Rack Temperature Is Higher Than High Threshold

Alarm Information
l Alarm code: 25856
l Alarm name: Rack temperature is higher than high threshold
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l The threshold configuration is unreasonable.
l The actual rack temperature is too high.

System Impact
l If the alarm is caused by unreasonable threshold configuration, service will not be
affected.
l If the alarm is caused by high rack temperature, the board may not work properly and
board services may be interrupted.

Handling Suggestion
1. Check whether the high threshold configured on the background for the rack
temperature is reasonable.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Cool the rack. Observe whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
3. Modify the high threshold for the rack temperature, and synchronize it to the
foreground. Observe whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-91

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

2.2.23 25857 Rack Temperature Is Lower Than Low Threshold

Alarm Information
l Alarm code: 25857
l Alarm name: Rack temperature is lower than low threshold
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l The threshold configuration is unreasonable.
l The actual rack temperature is too low.

System Impact
l If the alarm is caused by unreasonable threshold configuration, service will not be
affected.
l If the alarm is caused by low rack temperature, the board may not work properly and
board services may be interrupted.

Handling Suggestion
1. Check whether the low threshold configured on the background for the rack
temperature is reasonable.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Increase the rack temperature. Observe whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
3. Modify the low threshold for the rack temperature, Observe whether the alarm
disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.24 25858 Room Temperature Is Higher Than High Threshold

Alarm Information
l Alarm code: 25858
l Alarm name: Room temperature is higher than high threshold
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l The threshold configuration is unreasonable.

2-92

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l The actual temperature in equipment room is too high.

System Impact
l If the alarm is caused by unreasonable threshold configuration, service will not be
affected.
l If the alarm is caused by high temperature in the equipment room, the board may not
work properly and board services may be interrupted.

Handling Suggestion
1. Check whether the high threshold configured on the background for the temperature
in the equipment room is reasonable.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Cool the equipment room. Observe whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
3. Modify the high threshold for the temperature in the equipment room, and synchronize
it to the foreground. Observe whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.25 25859 Room Temperature Is Lower Than Low Threshold

Alarm Information
l Alarm code: 25859
l Alarm name: Room temperature is lower than low threshold
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l The threshold configuration is unreasonable
l The actual temperature in the equipment room is too low.

System Impact
l If the alarm is caused by unreasonable threshold configuration, service will not be
affected.
l If the alarm is caused by too low temperature in the equipment, the board may not
work properly and board services may be interrupted.

Handling Suggestion
1. Check whether the low threshold configured on the background for the temperature in
the equipment room is reasonable.

2-93

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Yes: Go to Step 2.
l No: Go to Step 3.
2. Increase the temperature in the equipment room. Observe whether the alarm
disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
3. Modify the low threshold for the temperature in the equipment room, and synchronize
it to the foreground. Observe whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.26 25860 Voltage Is Higher Than High Threshold

Alarm Information
l Alarm code: 25860
l Alarm name: Voltage is higher than high threshold
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l The threshold configuration is unreasonable.
l The actual voltage is too high.

System Impact
l If the alarm is caused by unreasonable threshold configuration, service will not be
affected.
l If the alarm is caused by high voltage, the board may not work properly and board
services may be interrupted.

Handling Suggestion
1. Check whether the high threshold configured on the background for the rack voltage
is reasonable.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Lower the voltage. Observe whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
3. Modify the high threshold for the rack voltage, and synchronize it to the foreground.
Observe whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-94

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

2.2.27 25861 Voltage Is Lower Than Low Threshold

Alarm Information
l Alarm code: 25861
l Alarm name: Voltage is lower than low threshold
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l The threshold configuration is unreasonable.
l The actual voltage is too low.

System Impact
l If the alarm is caused by unreasonable threshold configuration, service will not be
affected.
l If the alarm is caused by low voltage, the board may not work properly and board
services may be interrupted.

Handling Suggestion
1. Check whether the low threshold configured on the background for the rack voltage is
reasonable.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Increase the voltage. Observe whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
3. Modify the low threshold for the rack voltage, and synchronize it to the foreground.
Observe whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.28 25862 Humidity Is Higher Than High Threshold

Alarm Information
l Alarm code: 25862
l Alarm name: Humidity is higher than high threshold
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l The threshold configuration is unreasonable.

2-95

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l The actual humidity in the equipment room is too high.

System Impact
l If the alarm is caused by unreasonable threshold configuration, services will not be
affected.
l If the alarm is caused by high humidity in the equipment room, the board may not work
properly and board services may be interrupted.

Handling Suggestion
1. Check whether the high threshold configured on the background for the humidity in
the equipment room is reasonable.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Lower the humidity in the equipment room. Observe whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
3. Modify the high threshold for the humidity in the equipment room, and synchronize it
to the foreground. Observe whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.29 25863 Humidity Is Lower Than Low Threshold

Alarm Information
l Alarm code: 25863
l Alarm name: Humidity is lower than low threshold
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l The threshold configuration is unreasonable.
l The actual humidity in the equipment room is too low.

System Impact
l If the alarm is caused by unreasonable threshold configuration, services will not be
affected.
l If the alarm is caused by low humidity in the equipment room, the board may not work
properly and board services may be interrupted.

Handling Suggestion
1. Check whether the low threshold configured on the background for the humidity in the
equipment room is reasonable.

2-96

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l Yes: Go to Step 2.
l No: Go to Step 3.
2. Increase the humidity in the equipment room. Observe whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
3. Modify the low threshold for the humidity in the equipment room, and synchronize it to
the foreground. Observe whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.30 25864 Fault in Fan Plug-in Box

Alarm Information
l Alarm code: 25864
l Alarm name: Fault in fan plug-in box
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
l The fan in the rack does not run properly.
l The sensor of the fan plug-in box is set incorrectly.

System Impact
This alarm may lead to excessively high rack temperature, resulting in exceptional board
operations and interruption of board services.

Handling Suggestion
1. Check whether the fan plug-in box is tightly inserted into the rack, and whether the
power is connected well.
l If the fan plug-in box is not tightly inserted into the rack, and the power is not
connected well, go to Step 2.
l If the fan plug-in box is tightly inserted into the rack, and the power is connected
well, go to Step 3.
2. Secure the fan plug-in box and connect the power. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Replace the fan plug-in box with a good one. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-97

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

2.2.31 25865 Rack Door Access Control Alarm or Other Monitor

Alarm
Alarm Information
l Alarm code: 25865
l Alarm name: Rack door access control alarm or other monitor alarm
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l The access control of the corresponding rack is not closed.
l The access control sensor is set incorrectly.

System Impact
Services are not affected, but the alarm may bring a potential safety hazard.

Handling Suggestion
1. Check whether the rack door is closed.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Close the rack door. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether the access control system is correctly connected.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Connect the access control system and close the rack door. Then check whether the
alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.32 25866 Smoke Alarm

Alarm Information
l Alarm code: 25866
l Alarm name: Smoke alarm
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l The smoke sensor is set incorrectly.

2-98

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l The smoke density in equipment room is too high.

System Impact
Services are not affected, but the alarm may bring a potential safety hazard.

Handling Suggestion
1. Check whether there is smoke in the equipment room.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Clear away smoke. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.33 25867 Infrared Alarm

Alarm Information
l Alarm code: 25867
l Alarm name: Infrared alarm
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l Heat sources (such as animal/human) come near.
l The infrared sensor is set incorrectly.
l The infrared sensor is faulty.

System Impact
l If the infrared sensor is set incorrectly, the system is not affected.
l If the infrared in the equipment exceeds the threshold, potential safety hazards may
exist.

Handling Suggestion
1. Check whether there is any animal or human near the infrared sensor.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Make the animal or human away from the infrared sensor. Observe whether the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Correctly set the infrared sensor, and observe whether this alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-99

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

2.2.34 25868 Lightning Alarm

Alarm Information
l Alarm code: 25868
l Alarm name: Lightning alarm
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l In bad weather, the equipment room is hit by lightning stroke.
l The lightning-protection sensor is set incorrectly.

System Impact
The board may not work properly and board services may be interrupted.

Handling Suggestion
1. Check whether there is any lightning hazard.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Take lightning protection measures. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.35 25869 Power Switch Alarm

Alarm Information
l Alarm code: 25869
l Alarm name: Power switch alarm
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l The air switch is not closed.
l The air switch sensor is set incorrectly.

System Impact
The power supply for the shelf is affected. All boards on this shelf fail to work properly, and
the services provided by the boards on this shelf are interrupted.

Handling Suggestion
1. Check whether the air switch is closed, and whether the ALM indicator is normal.

2-100

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l Yes: Go to Step 3.
l No: Go to Step 2.
2. Close the air switch. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether the background shields this air switch.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.36 25870 Power Type Configured Does Not Accord With

Physical
Alarm Information
l Alarm code: 25870
l Alarm name: Power type configured does not accord with physical
l Severity: Minor
l Alarm type: Equipment alarm

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

System Impact
The board fails to work properly.

Handling Suggestion
1. Check the configuration data according to the additional information of the alarm to
see if the configuration conforms to the hardware of this board.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Modify the configuration according to the hardware equipment. Re-power on the
board. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.37 25871 Communication Abnormal Between the Shelf

Management Board and Switch Board in the Same Shelf
Alarm Information
l Alarm code: 25871

2-101

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Alarm name: Communication abnormal between the shelf management board and
switch board in the same shelf
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
l The link between the shelf management board and the switching board on the same
shelf is broken.
l The 485 communication between the switching board and the environment monitoring
board configured for this shelf is abnormal.

System Impact
l The shelf management board cannot implement hardware management functions.
l The power status and environment status cannot be monitored.

Handling Suggestion
1. Check whether the switching board is on position.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Make sure that the switching board is on position. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether the link between the switching board and the environment monitoring
board configured for this shelf is normal.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Make sure that the link between the switching board and the environment monitoring
board configured for this shelf is normal. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.38 26127 Clock Reference Source Lost (Level 3 Alarm)

Alarm Information
l Alarm code: 26127
l Alarm name: Clock reference source lost (Level 3 alarm)
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
The input clock reference is in unavailable status for no more than 10 minutes.

2-102

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l The input clock reference is exceptional.

l The configured clock reference does not exist.

System Impact
When all configured clock references are lost, the clock daughter card comes to free
running or holding status. Accuracy of the output clock is determined by the crystal
oscillator of the clock daughter card. There is no impact on the service.

Handling Suggestion
1. Check whether there is any input clock reference.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Re-connect the input clock reference. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
3. Run the SET CLOCK BASE command to set the corresponding configuration of the
clock reference. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.39 26128 Clock Reference Source Lost (Level 2 Alarm)

Alarm Information
l Alarm code: 26128
l Alarm name: Clock reference source lost (Level 2 alarm)
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
The input clock reference is in unavailable status for more than 10 minutes and less than
24 hours.
l The input clock reference is exceptional.
l The configured clock reference does not exist.

System Impact
When all configured clock reference sources are lost, the clock daughter card comes to free
running or holding status. Accuracy of output clock is determined by the crystal oscillator
of clock daughter card. The clock loss leads to synchronization failure between system
clock and clock reference source. Service interruption will occur.
The system will not be affected if the following two events happen together.
l Input clock reference source is lost.

2-103

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l The phase-locked loop locks another clock reference source.

Handling Suggestion
1. Check whether there is any input clock reference.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Re-connect the input clock reference. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
3. Run the SET CLOCK BASE command to set the corresponding configuration of the
clock reference. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.40 26129 Clock Reference Source Lost (Level 1 Alarm)

Alarm Information
l Alarm code: 26129
l Alarm name: Clock reference source lost (Level 1 alarm)
l Severity: Critical
l Alarm type: Equipment alarm

Probable Cause
The input clock reference is in unavailable status for more than 24 hours.
l The input clock reference is exceptional.
l The configured clock reference does not exist.

System Impact
When all configured clock reference sources are lost, the clock daughter card comes to free
running or holding status. Accuracy of output clock is determined by the crystal oscillator
of clock daughter card. The clock loss leads to synchronization failure between system
clock and clock reference source. Service interruption will occur.
The system will not be affected if the following two events happen together.
l Input clock reference source is lost.
l The phase-locked loop locks other clock reference source.

Handling Suggestion
1. Check whether there is any input clock reference.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Re-connect the input clock reference. Then check whether the alarm disappears.

2-104

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l Yes: End alarm handling.

l No: Contact ZTE for help.
3. Run the SET CLOCK BASE command to set the corresponding configuration of the
clock reference. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.41 26133 Output Clock of the Board Is Lost

Alarm Information
l Alarm code: 26133
l Alarm name: Output clock of the board is lost
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
The hardware is faulty.

System Impact
l If the active board does not output clock, the system clock is not synchronous, which
causes services interrupted.
l If the standby board does not output clock, the services are not impacted.

Handling Suggestion
1. Check whether the alarm occurs on the active board or the standby board.
l Active board, go to Step 2.
l Standby board, go to Step 3.
2. Perform active/standby switching. Then check whether the alarm disappears.
l Yes: Go to Step 3.
l No: Contact ZTE for help.
3. Replace the standby board. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.42 29184 SNTP Failed to Synchronize Time

Alarm Information
l Alarm code: 29184
l Alarm name: SNTP failed to synchronize time
l Severity: Minor
l Alarm type: Equipment alarm

2-105

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Probable Cause
l The source addresses of SNTP client configuration is error.
l SNTP servers faults.
l Network communication faults.

System Impact
SNTP server is not available.

Handling Suggestion
1. Check whether the source addresses of SNTP client configuration is correct.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Configure the correct source addresses of SNTP client again, then check whether the
alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether the SNTP server is available.
l Yes: Go to Step 5.
l No: Go to Step 4.
4. Solve SNTP server problem. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 5.
5. Check whether the link between SNTP servers and client is available.
l Yes: Contact ZTE for help.
l No: Go to Step 6.
6. Solve the link problem. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.43 29952 Ethernet Link Fault Alarm

Alarm Information
l Alarm code: 29952
l Alarm name: Ethernet link fault alarm
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
l A critical event has occurred.
l The local fault cannot be restored.
l The link receiving direction is faulty.

2-106

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

System Impact
The system service is lost.

Handling Suggestion
1. Check whether the contact of fiber receiving direction is poor or the network cable of
the electrical interface is loose.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Unplug and then plug the fiber or the network cable. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Confirm whether the Ethernet OAM function of the remote end is enabled or not.
l Yes: Go to Step 5.
l No: Go to Step 4.
4. Contact the engineer of the remote end to enable the Ethernet OAM function. Then
check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 5.
5. Plug the network cable into a new peer port on the same device, and duplicate all
configuration of the old port to this new port except the physical port number. Then
check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.44 29953 The Ethernet Port Is in the OAM Loopback State

Alarm Information
l Alarm code: 29953
l Alarm name: The ethernet port is in the OAM loopback state
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
The port of the local end was in loopback status because the Ethernet OAM loopback
function of the remote end was enabled.

System Impact
Services are interrupted.

2-107

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Handling Suggestion
1. Contact the remote end to check whether the Ethernet OAM loopback function is
enabled or not.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Confirm whether the loopback test is completed and disable the Ethernet OAM
loopback function of the remote end. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.45 30208 CFM Fault

Alarm Information
l Alarm code: 30208
l Alarm name: CFM fault
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
Connetivty fault management is in fault.

System Impact
Traffic may be lost partially.

Handling Suggestion
1. In the Falut Management window of the LMT, observe the additional information of
the alarm. There are five kinds of additional informations.
l receive remote Rx fault indication signal: Go to Step 2.
l receive server layer's alarm indication signal: Go to Step 7.
l lost continuity from the remote MEP: Go to Step 9.
l recevie incorrect CCM frame: Go to Step 11.
l receive a CCM frame from other MD: Go to Step 17.
l receive server layer's lock signal: Go to Step 22.
2. Check whether remote MEP's(Maintanence end point)'Rx is unidirection.
l Yes: Go to Step 3.
l No: Contact ZTE for help.
3. Check the receiving end and see whether the optical fiber connected to the receiving
port of the remote MEP is loose.
l Yes: Go to Step 4.
l No: Go to Step 5.
4. Fasten the optical fiber connected to the receiving port of the remote MEP. Then check
whether the alarm disappears.

2-108

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l Yes: End alarm handling.

l No: Go to Step 5.
5. Check whether network cables connected to intermediate devices are loose or whether
any device fails.
l Yes: Go to Step 6.
l No: Contact ZTE for help.
6. Ensure that all intermediate devices operate properly and links between devices are
all in UP state. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
7. Check the link between two intermediate service layer MEPs (an AIS sending MEP is
the border) between two AIS receiving MEPs and see whether the link ports connected
to intermediate devices are all in UP state.
l Yes: Contact ZTE for help.
l No: Go to Step 8.
8. Replace the network cable or fasten the cable to the ports to restore the faulty link.
Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
9. Check the network path between two MEPs and see whether link ports connected to
intermediate devices are all in UP state.
l Yes: Contact ZTE for help.
l No: Go to Step 10.
10. Replace the network cable or fasten the cable to the ports to restore the faulty link.
Thus, packet sending/receiving statistics on the ports bound with the local and remote
MEPs are normal. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
11. Check the networking plan of MD and MA domains managed by Ethernet OAM
(IEEE802.1ag) and see whether any incorrect MEPID is configured in remote MEP
configuration of the local MEP. Note that you need to know VLAN, MD, and MA
configuration in the whole network.
l Yes: Go to Step 12.
l No: Contact ZTE for help.
12. Modify the incorrect MEPIDs. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 13.
13. In the remote MEP configuration of the local MEP, check whether any CCM sending
interval is inconsistent with the interval configured for the local MEP.
l Yes: Go to Step 14.
l No: Go to Step 15.
14. Modify the CCM sending intervals at both ends to be consistent. Then check whether
the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 15.

2-109

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

15. In the remote MEP configuration of the local MEP, check whether the configured MAC
address of a remote MEP is inconsistent with the actual MAC address.
l Yes: Go to Step 16.
l No: Contact ZTE for help.
16. Modify the MAC address to be consistent with the actual MAC address. Then check
whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
17. Check the networking plan of MD and MA domains managed by Ethernet OAM
(IEEE802.1ag) and see whether any incorrect MEPID is configured in remote MEP
configuration of the local MEP. Note that you need to know VLAN, MD, and MA
configuration in the whole network. Check whether border MEPs of the whole MD
domain are closed and complete.
l Yes: Contact ZTE for help.
l No: Go to Step 18.
18. Modify the border MEPs of the whole MD domain to be closed and complete. Then
check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 19.
19. Check whether any MEP is missing in the MD domain and thus packets from other
MD domains come into this MD domain.
l Yes: Go to Step 20.
l No: Contact ZTE for help.
20. Configure the missing MEPs in the MD domain. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
21. Check 802.1ag configuration of two intermediate service layer MEPs between LOCK
signal receiving MEPs and see whether the network between the two service layer
MEPs is being administratively locked. If yes, check whether the alarm can be
eliminated.
l Yes: Go to Step 22.
l No: Contact ZTE for help.
22. Notify the network management system of the service layer MEPs to disable
administrative locking. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.46 30721 Temperature Is Lower Than Lower-Non-Critical

Threshold
Alarm Information
l Alarm code: 30721

2-110

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l Alarm name: Temperature is lower than lower-non-critical threshold

l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
The ambient temperature is low.

System Impact
The device may not function properly.

Handling Suggestion
1. Wait for a moment, and check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Check whether the temperature in the equipment room is low.
l Yes: Go to Step 3.
l No: Contact ZTE for help.
3. Increase the temperature in the equipment room to normal range. Then check whether
the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.47 30722 Temperature Is Lower Than Lower-Critical Threshold

Alarm Information
l Alarm code: 30722
l Alarm name: Temperature is lower than lower-critical threshold
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
The ambient temperature is too low.

System Impact
The device may not function properly.

Handling Suggestion
1. Wait for a moment, and check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Check whether the temperature in the equipment room is low.

2-111

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Yes: Go to Step 3.
l No: Contact ZTE for help.
3. Increase the temperature in the equipment room to normal range. Then check whether
the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.48 30723 Temperature Is Lower Than Lower-Non-Recoverable

Threshold
Alarm Information
l Alarm code: 30723
l Alarm name: Temperature is lower than lower-non-recoverable threshold
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
The ambient temperature is too low.

System Impact
The device is destroyed, and the system function is unavailable.

Handling Suggestion
Immediately plug the device from the shelf. Contact ZTE for help.

2.2.49 30724 Temperature Is Higher Than Upper-Non-Critical

Threshold
Alarm Information
l Alarm code: 30724
l Alarm name: Temperature is higher than upper-non-critical threshold.
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
l The velocity of the fan in the shelf are slow.
l The ambient temperature is high.
l The dust-proof net is dirty.

2-112

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

System Impact
The device does not function properly.

Handling Suggestion
1. Wait for a moment, and check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Check whether the temperature in the equipment room is high, whether the velocity of
the fan are slow, and whether the dust screen is dirty.
l Yes: Go to Step 3.
l No: Contact ZTE for help.
3. Adjust the fan speed and clean or replace the dust screen, until the temperature in the
equipment room drops to normal. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.50 30725 Temperature Is Higher Than Upper-Critical Threshold

Alarm Information
l Alarm code: 30725
l Alarm name: Temperature is higher than upper-critical threshold
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l The velocity of the fan in the shelf are too slow.
l The ambient temperature is too high.
l The dust-proof net is too dirty.

System Impact
The device may not function properly.

Handling Suggestion
1. Wait for a moment, and check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Check whether the temperature in the equipment room is high, whether the velocity of
the fan are slow, and whether the dust screen is dirty.
l Yes: Go to Step 3.
l No: Contact ZTE for help.
3. Adjust the fan speed and clean or replace the dust screen, until the temperature in the
equipment room drops to normal. Then check whether the alarm disappears.

2-113

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Yes: End alarm handling.

l No: Contact ZTE for help.

2.2.51 30726 Temperature Is Higher Than Upper-Non-Recoverable

Threshold
Alarm Information
l Alarm code: 30726
l Alarm name: Temperature is higher than upper-non-recoverable threshold
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
l The velocity of the fan in the shelf are too slow.
l The ambient temperature is too high.
l The dust-proof net is too dirty.

System Impact
The device is destroyed, and the system function is unavailable.

Handling Suggestion
Wait for two minutes, and check whether the alarm disappears.
l Yes: End alarm handling.
l No: Immediately plug the device from the shelf. Contact ZTE for help.

2.2.52 30727 Voltage Is Lower Than Lower-Non-Critical Threshold

Alarm Information
l Alarm code: 30727
l Alarm name: Voltage is lower than lower-non-critical threshold
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
l The voltage fluctuates.
l The resistance is invalid.
l The load on the device changes.
l Exceptional ambient temperature of the shelf causes voltage deviation.

2-114

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

System Impact
Some services on the device are exceptional.

Handling Suggestion
1. Wait for a moment, and check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Check whether the power supply in the equipment room is exceptional.
l Yes: Contact the engineer of power supply for handling.
l No: Contact ZTE for help.

2.2.53 30728 Voltage Is Lower Than Lower-Critical Threshold

Alarm Information
l Alarm code: 30728
l Alarm name: Voltage is lower than lower-critical threshold
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l The voltage fluctuates.
l The resistance is invalid.
l The load on the device changes.
l Exceptional ambient temperature of the shelf causes voltage deviation.

System Impact
Most of or all the services on the device are exceptional.

Handling Suggestion
1. Wait for a moment, and check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Check whether the power supply in the equipment room is exceptional.
l Yes: Contact the engineer of power supply for handling.
l No: Contact ZTE for help.

2-115

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

2.2.54 30729 Voltage Is Lower Than Lower-Non-Recoverable

Threshold
Alarm Information
l Alarm code: 30729
l Alarm name: Voltage is lower than lower-non-recoverable threshold
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
l The voltage fluctuates.
l The resistance is invalid.
l The load on the device changes.
l Exceptional ambient temperature of the shelf causes voltage deviation.

System Impact
The device is destroyed, and the system function is unavailable.

Handling Suggestion
Immediately plug the device from the shelf. Contact ZTE for help.

2.2.55 30730 Voltage Is Higher Than Upper-Non-Critical Threshold

Alarm Information
l Alarm code: 30730
l Alarm name: Voltage is higher than upper-non-critical threshold
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
l The voltage fluctuates.
l The resistance is invalid.
l The load on the device changes.
l Exceptional ambient temperature of the shelf causes voltage deviation.

System Impact
Some services on the device are exceptional.

Handling Suggestion
1. Wait for a moment, and check whether the alarm disappears.

2-116

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l Yes: End alarm handling.

l No: Go to Step 2.
2. Check whether the power supply in the equipment room is exceptional.
l Yes: Contact the engineer of power supply for handling.
l No: Contact ZTE for help.

2.2.56 30731 Voltage Is Higher Than Upper-Critical Threshold

Alarm Information
l Alarm code: 30731
l Alarm name: Voltage is higher than upper-critical threshold
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l The voltage fluctuates.
l The resistance is invalid.
l The load on the device changes.
l Exceptional ambient temperature of the shelf causes voltage deviation.

System Impact
Most of or all the services on the device are exceptional.

Handling Suggestion
1. Wait for a moment, and check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Check whether the power supply in the equipment room is exceptional.
l Yes: Contact the engineer of power supply for handling.
l No: Contact ZTE for help.

2.2.57 30732 Voltage Is Higher Than Upper-Non-Recoverable

Threshold
Alarm Information
l Alarm code: 30732
l Alarm name: Voltage is higher than upper-non-recoverable threshold
l Severity: Major
l Alarm type: Equipment alarm

2-117

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Probable Cause
l The voltage fluctuates.
l The resistance is invalid.
l The load on the device changes.
l Exceptional ambient temperature of the shelf causes voltage deviation.

System Impact
The device is destroyed, and the system function is unavailable.

Handling Suggestion
Immediately plug the device from the shelf. Contact ZTE for help.

2.2.58 30734 Velocity of Fan Is Lower Than Lower-Critical Threshold

Alarm Information
l Alarm code: 30734
l Alarm name: Velocity of fan is lower than lower-critical threshold
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l The fan suffers from a serious fault.
l The voltage of the fan suffers from a serious exception.

System Impact
The temperature in the shelf increases, which causes other hardware in the shelf being
destroyed.

Handling Suggestion
1. Wait for a moment, and check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Check whether the fan inhales foreign substances.
l Yes: Go to Step 3.
l No: Contact ZTE for help.
3. Take foreign substances away from the fan. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-118

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

2.2.59 30735 Filter Tray Is Present for Too Long (Non-Recoverable)

Alarm Information
l Alarm code: 30735
l Alarm name: Filter tray is present for too long (non-recoverable)
l Severity: Major
l Alarm type: Environment alarm

Probable Cause
The dust screen has not been cleaned or replaced for a long time.

System Impact
Heat dissipation in the shelf is seriously impacted, which may easily cause other devices
being destroyed.

Handling Suggestion
Immediately clean or replace the dust screen. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.60 30736 Filter Tray Is Present for Too Long (Critical)

Alarm Information
l Alarm code: 30736
l Alarm name: Filter tray is present for too long(critical)
l Severity: Minor
l Alarm type: Environment alarm

Probable Cause
The dust screen has not been cleaned or replaced for a long time.

System Impact
Heat dissipation in the shelf is seriously impacted, which may cause other devices being
destroyed.

Handling Suggestion
Immediately clean or replace the dust screen. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-119

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

2.2.61 30737 Filter Tray Is Present for Too Long (Non-Critical)

Alarm Information
l Alarm code: 30737
l Alarm name: Filter tray is present for too long (non-critical)
l Severity: Warning
l Alarm type: Environment alarm

Probable Cause
The dust screen is not cleaned or replaced in time.

System Impact
Heat dissipation in the shelf is impacted.

Handling Suggestion
Immediately clean or replace the dust screen. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.62 30738 State Is Abnormal

Alarm Information
l Alarm code: 30738
l Alarm name: State is abnormal
l Severity: Minor
l Alarm type: Environment alarm

Probable Cause
l The voltage of the voltage regulation circuit is too high.
l The voltage regulation circuit is invalid.
l The power switch is opened.
l The electricity of the battery is too low.

System Impact
Some services on the device are exceptional.

Handling Suggestion
1. Check whether the air switch of the power is opened.
l Yes: Go to Step 2.
l No: Go to Step 3.

2-120

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

2. Close the air switch of the power. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether the power supply in the equipment room is normal.
l Yes: Contact ZTE for help.
l No: Contact the maintenance engineer of power supply for handling.

2.2.63 30739 Current Is Lower Than Lower-Non-Critical Threshold

Alarm Information
l Alarm code: 30739
l Alarm name: Current is lower than lower-non-critical threshold
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
Power fluctuate.

System Impact
Some services on the device are exceptional.

Handling Suggestion
Check whether the payload and power are normal.

l Yes: Contact ZTE for help.

l No: Contact the maintenance engineer of power supply for handling.

2.2.64 30740 Current Is Lower Than Lower-Critical Threshold

Alarm Information
l Alarm code: 30740
l Alarm name: Current is lower than lower-critical threshold
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
Maybe aroused by payload changing.

System Impact
Most of or all the services on the device are exceptional.

2-121

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Handling Suggestion
Check whether the payload and power are normal.
l Yes: Contact ZTE for help.
l No: Contact the maintenance engineer of power supply for handling.

2.2.65 30741 Current Is Lower Than Lower-Non-Recoverable

Threshold
Alarm Information
l Alarm code: 30741
l Alarm name: Current is lower than lower-non-recoverable threshold
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
l Resistance invalid.
l Influenced by environment.

System Impact
The device is destroyed, and the system function is unavailable.

Handling Suggestion
Power off right now, and Contact ZTE for help.

2.2.66 30742 Current Is Higher Than Upper-Non-Critical Threshold

Alarm Information
l Alarm code: 30742
l Alarm name: Current is higher than upper-non-critical threshold
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
Power fluctuate.

System Impact
Some services on the device are exceptional.

2-122

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Handling Suggestion
Check whether the payload and power are normal.
l Yes: Contact ZTE for help.
l No: Contact the maintenance engineer of power supply for handling.

2.2.67 30743 Current Is Higher Than Upper-Critical Threshold

Alarm Information
l Alarm code: 30743
l Alarm name: Current is higher than upper-critical threshold
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
Maybe aroused by payload changing.

System Impact
Most of or all the services on the device are exceptional.

Handling Suggestion
Check whether the payload is normal.
l Yes: Contact ZTE for help.
l No: Contact the maintenance engineer of power supply for handling.

2.2.68 30744 Current Is Higher Than Upper-Non-Recoverable

Threshold
Alarm Information
l Alarm code: 30744
l Alarm name: Current is higher than upper-non-recoverable threshold
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
l Resistance invalid.
l Exceptional ambient temperature causes voltage deviation.

System Impact
The device is destroyed, and the system function is unavailable.

2-123

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Handling Suggestion
Power off right now, and contact ZTE for help.

2.2.69 30745 Velocity of Fan Is Lower Than Lower-Non-Critical

Threshold
Alarm Information
l Alarm code: 30745
l Alarm name: Velocity of fan is lower than lower-non-critical threshold
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
l The fan suffers from a serious fault.
l The voltage of the fan suffers from a serious exception.

System Impact
The temperature in the shelf increases, which causes other hardware in the shelf being
destroyed.

Handling Suggestion
1. Wait for a moment, and check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Check whether the fan inhales foreign substances.
l Yes: Go to Step 3.
l No: Contact ZTE for help.
3. Take foreign substances away from the fan. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.70 30746 Velocity of Fan Is Lower Than Lower-Non-Recoverable

Threshold
Alarm Information
l Alarm code: 30746
l Alarm name: Velocity of fan is lower than lower-non-recoverable threshold
l Severity: Major
l Alarm type: Equipment alarm

2-124

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Probable Cause
l The fan suffers from a serious fault.
l The voltage of the fan suffers from a serious exception.

System Impact
The temperature in the shelf increases, which causes other hardware in the shelf being
destroyed.

Handling Suggestion
1. Wait for a moment, and check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Check whether the fan inhales foreign substances.
l Yes: Go to Step 3.
l No: Contact ZTE for help.
3. Take foreign substances away from the fan. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.71 30747 Module/Board Device Absent

Alarm Information
l Alarm code: 30747
l Alarm name: Module/Board Device Absent
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
The module or board is absent.

System Impact
The services on this module or board are interrupted.

Handling Suggestion
1. On the Real-time Current Alarm Monitoring tab of the Fault Management window,
double-click the alarm to display the alarm details, and record the related module or
board.
2. Check whether the related module or board works properly.
l Yes: Contact ZTE for help.
l No: Go to Step 3.

2-125

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

3. Restore the module or board to normal. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.72 30748 Power On Failed Due to S5

Alarm Information
l Alarm code: 30748
l Alarm name: Power on failed due to S5
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
Hardware exception.

System Impact
The related board cannot work normally.

Handling Suggestion
1. Check whether the hardware of the board is normal.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Replace the board. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.73 30749 Difference Between Ambient and Outlet Sensor

Exceeded Limit
Alarm Information
l Alarm code: 30739
l Alarm name: Difference between ambient and outlet sensor exceeded limit
l Severity: Minor
l Alarm type: Environment alarm

Probable Cause
l The temperature within the shelf is abnormal.
l The cooling of the shelf is abnormal.
l The fans are abnormal.

2-126

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

System Impact
The device may not be able to operate properly.

Handling Suggestion
1. Check whether the surrounding environment of the shelf is normal.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Restore the ambient environment of the shelf to normal. Then check whether the alarm
disappears.
l Yes: Contact ZTE for help.
l No: Go to Step 3.
3. Check whether the fans work properly.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Restore the fans to normal. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.74 30750 RAID1 Degradation Detected

Alarm Information
l Alarm code: 30750
l Alarm name: RAID1 degradation detected
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
RAID1 degradation detected.

System Impact
RAID1 function invalided.

Handling Suggestion
1. Check whether the hard disk is error.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Replace the error disk. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Replace the board. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-127

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

2.2.75 30751 MCElog Detected

Alarm Information
l Alarm code: 30751
l Alarm name: MCElog detected
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
MCElog detected.

System Impact
The board maybe work abnormally.

Handling Suggestion
1. Extract and reinsert the board. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Replace the board. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.76 30752 RAID1 Degradation Detected

Alarm Information
l Alarm code: 30752
l Alarm name: RAID1 degradation detected
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
NIC port continuous up-down status detected.

System Impact
Network Connection is abnormal.

Handling Suggestion
1. Check whether Ethernet port is connected stable.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Reset the board. And then check whether the alarm disappears.

2-128

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l Yes: End alarm handling.

l No: Go to Step 4.
3. Fixed the Ethernet connector. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 4.
4. Replace the board. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.77 30753 FC Controller Unavailable

Alarm Information
l Alarm code: 30753
l Alarm name: FC controller unavailable
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
FC controller detected, but unavailable (Driver not found).

System Impact
FC controller can not work normally.

Handling Suggestion
1. Re-install FC controller driver. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Replace the board. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.78 30754 FC Port Continuous Up-down Status Detected

Alarm Information
l Alarm code: 30754
l Alarm name: FC port continuous up-down status detected
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
FC port continuous up-down status detected.

2-129

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
Network connection is abnormal.

Handling Suggestion
1. Check whether FC port is connected stable.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Reset the board. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 4.
3. Fixed the FC connector. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 4.
4. Replace the board. And then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.79 30808 Processor Internal Error

Alarm Information
l Alarm code: 30808
l Alarm name: Processor Internal Error
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
An internal error occurs within the processor.

System Impact
The device is damaged and cannot be used. The system loses its functions.

Handling Suggestion
1. Check whether the hardware of the board is normal.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Replace the board. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-130

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

2.2.80 30809 Processor Thermal Trip

Alarm Information
l Alarm code: 30809
l Alarm name: Processor Thermal Trip
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
The temperature of the processor is too high.

System Impact
The device is damaged and cannot be used. The system loses its functions.

Handling Suggestion
1. Check whether the hardware of the board is normal.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Replace the board. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.2.81 41737 Near-End TC Link Fault

Alarm Information
l Alarm code: 41737
l Alarm name: Near-end TC link fault
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
The physical trunk of the TC link or the input clock is exceptional.

System Impact
The TC link is disconnected.

Handling Suggestion
1. Check whether the physical trunk is connected properly.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Restore the physical trunk connection. Then check whether the alarm disappears.

2-131

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Yes: End alarm handling.

l No: Go to Step 3.
3. Check whether the input clock works properly.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Adjust the input clock to make it work properly. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.3 1000000~9999999
2.3.1 8392706 Time Synchronization Over Alarm Limit
Alarm Information
l Alarm code: 8392706
l Alarm name: Time synchronization over alarm limit
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
The clock synchronization exceeds the threshold.

System Impact
The time got from the NTP is not used.

Handling Suggestion
1. Run the SHOW SNTP command to check the Error Threshold.
l The set threshold is too small, go to Step 2.
l The set threshold is normal, go to Step 3.
2. Run the SET SNTP command to re-set Error Threshold. Then check whether the
alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. In the Fault Management window of the LMT, click the Realtime Current Alarms
Monitoring tab to check whether any “8392707 Request NTP time failed” alarm exists.
l Yes: Handle the alarm by referring to the corresponding handling suggestions.
l No: Go to Step 4.
4. Run the SYN SNTPTIME command to synchronize the NTP time. Then check whether
the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-132

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Related Alarm
2.3.2 8392707 Request SNTP Time Failed

2.3.2 8392707 Request SNTP Time Failed

Alarm Information
l Alarm code: 8392707
l Alarm name: Request SNTP time failed
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
l SNTP server does not exist or server operation is abnormal.
l The IP address of the NTP server configured in Chassis Data Module (CDM) does
not accord with its actual IP address.
l The IP address of the NTP server configured in CDM might be 0 or 0XFFFFFFFF.

System Impact
SNTP synchronization failure might lead to inconsistency between system time and real
time. For example, the real time is 1:00 am, but the displayed system time is 2:00 am.
Since system clock frequency is correct, service will not be affected.

Handling Suggestion
1. Check if the configuration of SNTP server is correct.
l Yes: Contact ZTE for help.
l No: Go to Step 2.

Note:

Log in to CDM through a serial port or network port, and run the cdmtool command
to check NTP settings. It is suggested that the NTP server be set as the OMM
server. It is required that the OMM server should enable the NTP service and that
the communication between the OMC address of the CMM and the OMM server is
normal.

2. Modify NTP settings. Then check whether the alarm disappears.

l Yes: End alarm handling.
l No: Contact ZTE for help.

2-133

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

2.3.3 8392708 Time Synchronization Over Alarm Limit in RPU

Access Type
Alarm Information
l Alarm code: 8392708
l Alarm name: Time synchronization over alarm limit in RPU access type
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
The difference between the time on OMP and the time on the SNTP server exceeds the
threshold.

System Impact
The system time is incorrect.

Handling Suggestion
1. Check whether the alarm threshold is set too low.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Reset the alarm threshold and wait for the next synchronization. Then check whether
the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check the SNTP server time and the system time to see which time is more accurate.
l The SNTP server time is more accurate, go to Step 4.
l The system time is more accurate, go to Step 5.
4. Initiate SNTP time synchronization by force, and wait for several seconds. Then check
whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
5. Check the networking of the SNTP server and locate the reason for the inaccuracy of
the SNTP server time. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.3.4 8393985 Control Plane Communication Abnormal Between

Board and Its Home Module
Alarm Information
l Alarm code: 8393985

2-134

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l Alarm name: Control plane communication abnormal between board and its home
module
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
l The board is configured in the database, but it is not powered on.
l The board is powered on, but the control plane link to its home MP is broken.

System Impact
The services carried by the board are interrupted.

Handling Suggestion
1. Check whether the switching board in the same shelf with this board, and the switching
board in the shelf where the home module of this board is located work properly.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Restore them to the normal status. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether this board is successfully powered on.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Re-power on this board. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.3.5 8393986 Control Plane Communication Is Abnormal Between

This Board and the Active Independent Board
Alarm Information
l Alarm code: 8393986
l Alarm name: Control plane communication is abnormal between this board and the
active independent board
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
l The board is configured in the active/standby mode, but the standby board is not
inserted.
l The standby board exists, but the communication link between the active and standby
boards is broken.

2-135

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
The services of the board are interrupted.

Handling Suggestion
1. Check whether the board is configured in the active/standby mode.
l Yes: Go to Step 2.
l No: Go to Step 4.
2. Make sure that both the active and standby boards are on position.
l Yes: Go to Step 4.
l No: Go to Step 3.
3. Restore the active/standby boards back in position. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 4.
4. Check whether related alarm exists on both the active and standby boards.
l Yes: Handle the alarm by referring to the corresponding handling suggestions.
l No: Go to Step 5.
5. Replace the active or standby board. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 6.
6. Move both the active and standby boards to other slots. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.3.6 8393987 Board Off Line

Alarm Information
l Alarm code: 8393987
l Alarm name: Board off line
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
l The board configured in the database is not on position.
l The link between the shelf management board (CMM) and this board fails.

System Impact
The board cannot provide services.

Handling Suggestion
1. Check whether the board is properly placed.

2-136

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l Yes: Go to Step 3.
l No: Go to Step 2.
2. Plug/unplug the board. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Replace the board. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 4.
4. Move the board to other slot. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 5.
5. Replace the CMM board in the same shelf. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.3.7 8393988 Control Plane Communication Abnormal Between

MP and OMP
Alarm Information
l Alarm code: 8393988
l Alarm name: Control plane communication abnormal between MP and OMP
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
l The MP module is configured in the database, but the board is not powered on.
l The board is powered on, but the control plane link to its home MP module is broken.

System Impact
The board is blocked, and the functions of the board are unavailable. As a result, all
services of the units under this module are unavailable.

Handling Suggestion
1. Check whether the switching board in the same shelf with this module, and the
switching board in the shelf where the home module of this module is located work
properly.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Restore them to the normal status. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether this board is successfully powered on.

2-137

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Yes: Contact ZTE for help.

l No: Go to Step 4.
4. Re-power on the board. Then check whether the alarm disappears.
l Yes: End alarm handling
l No: Contact ZTE for help.

2.3.8 8398848 SCCP Subsystem Unavailable

Alarm Information
l Alarm code: 8398848
l Alarm name: SCCP subsystem unavailable
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
l The remote signaling point subsystem is out of service.
l The remote signaling point is inaccessible.
l An Sub-System Number (SSN) is deleted from the remote office, and the local end
reports alarms.
l An SSN is not configured in the remote office, but the SSN of the remote office is
configured at the local end, causing Subsystem Status Test (SST) test failure.

System Impact
Messages cannot be sent to or received from the relevant subsystem. New services under
the corresponding office fail to be accessed, and some existing services are released
exceptionally.

Handling Suggestion
1. Check whether there exists any office (the office that corresponds to the subsystem)
inaccessible alarm (alarm code: 8400128 and 8400384).
l Yes: Handle the alarm by referring to the corresponding handling suggestions.
l No: Go to Step 2.
2. Run the SHOW OPC command to check the local signaling point configuration. Check
whether SCCP is included in the Application Type.
l Yes: Go to Step 4.
l No: Go to Step 3.
3. Add user type configuration. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 4.
4. Ask the remote office to check whether the SCCP user type is configured for its
signaling points.
l Yes: Go to Step 5.
l No: Ask the remote office to add the user type configuration.

2-138

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

5. Contact the remote end to check whether the status of signaling point subsystem is
available.
l Yes: Go to Step 6.
l No: It indicates that the local sub system of the remote office exits service state.
Ask the remote office to check the reason why the sub system exits service state
and handle the problem accordingly.
6. Contact the remote end to check whether the local signaling point subsystem is
configured.
l Yes: Contact ZTE for help.
l No: Ask the remote office to configure the sub system.

Related Alarms
2.3.14 8400128 MTP3 Office Inaccessible
2.3.19 8400384 M3UA Office Inaccessible

2.3.9 8399104 Broadband Link Congestion

Alarm Information
l Alarm code: 8399104
l Alarm name: Broadband link congestion
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
l The traffic is heavy.
l The load on links is uneven.
l The physical transmission quality of the bottom layer is poor.
l The configured bandwidth for the link is too small.

System Impact
Link congestion leads to transmission delay. If congestion is not serious, service will not
be affected. Otherwise, packet loss or call loss might occur, and the access success rate
of PS service might decrease.

Handling Suggestion
1. Make no intervention, and wait for the system to be automatically restored. After 30
seconds, check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Check the system to see whether the service in process is busy.
l Yes: Go to Step 3.
l No: Contact ZTE for help.

2-139

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

3. Check whether the configured links are sufficient.

l Yes: Go to Step 5.
l No: Go to Step 4.
4. Add links. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
5. Check whether the load on links is even.
l Yes: Wait for the alarm to be restored, end alarm handling.
l No: Go to Step 6.
6. Check whether modification is done on the link configuration.
l Yes: Contact ZTE for help.
l No: Go to Step 7.
7. Check whether any alarm exists on the bottom-layer transmission.
l Yes: Contact the transmission engineer for handling.
l No: Contact ZTE for help.

2.3.10 8399105 Broadband Link Overload

Alarm Information
l Alarm code: 8399105
l Alarm name: Broadband link overload
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
l The traffic is heavy.
l The load on links is uneven.
l The physical transmission quality of the bottom layer is poor.
l The configured bandwidth for the link is too small.

System Impact
Packet loss, call loss, and even link breaking may occur.

Handling Suggestion
1. Make no intervention, and wait for the system to be automatically restored. After 30
seconds, check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Check the system to see whether the service in process is busy.
l Yes: Go to Step 3.
l No: Contact ZTE for help.
3. Check whether the configured links are sufficient.
l Yes: Go to Step 5.

2-140

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l No: Go to Step 4.
4. Add links. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
5. Check whether the load on links is even.
l Yes: Wait for the alarm to be restored, end alarm handling.
l No: Go to Step 6.
6. Check whether modification is done on the link configuration.
l Yes: Contact ZTE for help.
l No: Go to Step 7.
7. Check whether any alarm exists on the bottom-layer transmission.
l Yes: Contact the transmission engineer for handling.
l No: Contact ZTE for help.

2.3.11 8399616 LAPD Link Break

Alarm Information
l Alarm code: 8399616
l Alarm name: LAPD link break
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
l 0: L3 link establishment request
l 1: L3 link release request
l 2: SABME is received.
l 3: DISC is received.
l 4: DM is received.
l 5: FRMR is received.
l 6: T200N200
l 7: CONTROL_ERROR
l 8: INFO_NOT_PERMIT
l 9: INCORRECT_LEN
l 10: I_FRAME_TOO_LONG
l 11: UA is received.
l 12: L3 sends a data request.
l 13: Link activation request
l 14: PERSISTENT_DEACT
l 15: T200 timeout
l 16: T203 timeout
l 17: An incorrect RR frame is received.
l 18: An incorrect REJ frame is received.
l 19: An incorrect RNR frame is received.

2-141

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l 20: An incorrect I frame is received.

l 21: An incorrect RR/REJ frame is received.
l 22: An incorrect RR/REJ frame is received.
l 23: An RNR frame is received.
l 0xff: Invalid

System Impact
Service failed.

Handling Suggestion
Record alarm details, and Contact ZTE for help.

2.3.12 8399872 MTP2 Link Sent Load Overloaded

Alarm Information
l Alarm code: 8399872
l Alarm name: MTP2 link sent load overloaded
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
l The traffic at the local end is heavy.
l The load on links is uneven.
l The link resource is insufficient.

System Impact
The MTP2 link being in overload status for a long time causes congestion in the MTP2
signaling link, which may cause service messages loss, and call loss.

Handling Suggestion
1. Make no intervention, and wait for the system to be automatically restored. After 30
seconds, check whether the alarm disappears.
l The alarm can automatically disappear, and does not appear frequently: End
alarm handling.
l The alarm cannot automatically disappear, or the alarm can automatically
disappear, but it appears frequently, go to Step 2.
2. View all MTP3 signaling link performance statistics of the alarming office.
l The sending load on all the links is high and fairly even, go to Step 3.
l The load on links is uneven: Contact ZTE for help.

2-142

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Note:
In the Performance Management window, select Signal Measurement > N7
Measurement > MTP3 Signaling Link Measurement to create a measurement task.
Uneven load means that the difference between the most heavily loaded link and the
most lightly loaded link is almost or greater than 1 time.

3. Add signaling links. Then check whether the alarm disappears.

l Yes: End alarm handling.
l No: Contact ZTE for help.

2.3.13 8399873 MTP2 Link Received Load Overloaded

Alarm Information
l Alarm code: 8399873
l Alarm name: MTP2 link received load overloaded
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
l The traffic at the remote end is heavy.
l The load on links is uneven.
l The link resource is insufficient.

System Impact
The MTP2 link being in overload status for a long time causes congestion when the MTP2
link receives signaling, which further triggers the signaling traffic control on the MTP2 layer.

Handling Suggestion
1. Make no intervention, and wait for the system to be automatically restored. After 30
seconds, check whether the alarm disappears.
l The alarm can automatically disappear, and does not appear frequently: End
alarm handling.
l The alarm cannot automatically disappear, or the alarm can automatically
disappear, but it appears frequently, go to Step 2.
2. View all MTP3 signaling link performance statistics of the alarming office.
l The sending load on all the links is high and fairly even, go to Step 3.
l The load on links is uneven: Contact ZTE for help.

2-143

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Note:
In the Performance Management window, select Signal Measurement > N7
Measurement > MTP3 Signaling Link Measurement to create a measurement task.
Uneven load means that the difference between the most heavily loaded link and the
most lightly loaded link is almost or greater than 1 time.

3. Add signaling links. Then check whether the alarm disappears.

l Yes: End alarm handling.
l No: Contact ZTE for help.

2.3.14 8400128 MTP3 Office Inaccessible

Alarm Information
l Alarm code: 8400128
l Alarm name: MTP3 office inaccessible
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
l The office and routing configuration is incorrect.
l The link is disconnected.

System Impact
Reception and sending of messages from/to the relevant office fail. New services under
this office fail to be accessed, and some existing services are released exceptionally.

Handling Suggestion
1. On the Real-time Current Alarm Monitoring tab of the Fault Management window,
check whether there exists any related alarm (alarm code: 8400129).
l Yes: Handle the alarm by referring to the corresponding handling suggestions.
l No: Go to Step 2.
2. Run the SHOW N7ROUTE command to query whether the link set configured in the
signaling routing configuration is correct.
l Yes: Go to Step 4.
l No: Go to Step 3.
3. Run the SET N7ROUTE command re-associate the correct link set. Then check
whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 4.

2-144

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

4. Run the SHOW N7OFC command to query whether the signaling route configured in
the signaling office configuration is correct.
l Yes: Go to Step 6.
l No: Go to Step 5.
5. Run the SET N7OFC command to re-associate the correct signaling route. Then check
whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 6.
6. Check whether the office and link configuration at the remote end is correct.
l Yes: Contact ZTE for help.
l No: Contact the maintenance engineer at the remote end for handling.

Related Alarm
2.3.15 8400129 MTP3 Link Unavailable

2.3.15 8400129 MTP3 Link Unavailable

Alarm Information
l Alarm code: 8400129
l Alarm name: MTP3 link unavailable
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
l The bottom-layer physical link is disconnected or suffers from poor quality.
l The link test fails to be passed.
l Link deactivation is performed in the Dynamic Management.
l The link is released at the remote end.
l The SMP module is restarted, or the board connected with the MTP3 link is restarted.

System Impact
If several MTP3 links are available under the office, services will not be affected. In the
case of heavy traffic, congestion in other available links might occur, leading to packet/call
loss or even decreasing the service access success ratio.
If only one link is available to the destination signaling point, the office will become
inaccessible. Reception and sending of messages from/to the relevant office fail. New
services under this office fail to be accessed, and some existing services are released
exceptionally.

Handling Suggestion
1. Check whether there are new data configured for the link or the configuration has been
modified.

2-145

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Yes: Go to Step 2.
l No: Go to Step 4.
2. Run the SHOW SMPLNKSTAT command to check the signaling link status.
l Normal, go to Step 4.
l The link is intermittently disconnected: Link unavailability might be caused by
MTP3 link test failure, go to Step 3.
3. Restore the signaling link to normal. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 4.

Note:

a. Run the SHOW OPC and SHOW ADJOFC command to check the SPC
configuration at both ends. Ensure that the configuration at both ends is
consistent.
b. Run the SHOW ADJOFC command to check the configured application types at
both ends. Ensure that the application types at both ends are the same.
c. Run the SHOW TDMN7LNK command to check the signaling link configuration
at both ends. Ensure that the SLC configuration at both ends is consistent.

4. Run the ACT LNK command to reactivate this link. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 5.
5. Perform physical self-loop of the link, self looping the devices at the both ends of the
link at the DDF frame. Then check whether the alarm disappears.
l Yes: Contact ZTE for help.
l No: Release the self-loop of the link, go to Step 6.
6. Check whether the board status is normal.
l Yes: Go to Step 7.
l No: Go to Step 6.
7. Restart or replace the board. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 7.
8. Check whether the remote end releases the related link.
l Yes: Contact the maintenance engineer at the remote end for handling.
l No: Contact ZTE for help.

2-146

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

2.3.16 8400130 MTP3 Cluster Inaccessible

Alarm Information
l Alarm code: 8400130
l Alarm name: MTP3 cluster inaccessible
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
l There are errors in the cluster and route configuration.
l The link is disconnected.

System Impact
The service messages to the corresponding office fail to be sent out, or the office is
inaccessible. The new services to this office fail to be accessed, and the existing services
are exceptionally released.

Handling Suggestion
1. On the Real-time Current Alarm Monitoring tab of the Fault Management window,
check whether there exists any related alarm (alarm code: 8400129).
l Yes: Handle the alarm by referring to the corresponding handling suggestions.
l No: Go to Step 2.
2. Check whether the cluster and link configuration at the remote end is correct.
l Yes: Contact ZTE for help.
l No: Contact the maintenance engineer at the remote end for handling.

Related Alarm
2.3.15 8400129 MTP3 Link Unavailable

2.3.17 8400131 MTP3 Link Congestion

Alarm Information
l Alarm code: 8400131
l Alarm name: MTP3 link congestion
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
l The quality of the bottom-layer link is poor, leading to frequent message
retransmission.
l There are too many upper-layer service messages, leading to link congestion.

2-147

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
Link congestion leads to transmission delay. If congestion is not serious, the service is not
affected. Otherwise, packet loss or call loss might occur.

Handling Suggestion
1. Replace the lower layer links. Ensure that connector contact and wiring are good
for providing high quality physical link transmission. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Check the office to which the link belongs. Add a link to this office. Then check whether
the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.3.18 8400132 MTP3 Link Sent Flow Control Alarm

Alarm Information
l Alarm code: 8400132
l Alarm name: MTP3 link sent flow control alarm
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
The sending load on the MTP3 link exceeds the set sending flow control threshold..

System Impact
Packet loss and call loss occur.

Handling Suggestion
1. Make no intervention, and wait for the system to be automatically restored. After 30
seconds, check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Check the system to see whether the service in process is busy.
l Yes: Go to Step 3.
l No: Contact ZTE for help.
3. Check whether the configured links are sufficient.
l Yes: Go to Step 5.
l No: Go to Step 4.
4. Add links. Then check whether the alarm disappears.
l Yes: End alarm handling.

2-148

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l No: Contact ZTE for help.

5. Check whether the load on links is even.
l Yes: Wait for the alarm to be restored, end alarm handling.
l No: Contact ZTE for help.

2.3.19 8400384 M3UA Office Inaccessible

Alarm Information
l Alarm code: 8400384
l Alarm name: M3UA office inaccessible
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
l The association is broken or the AS is not in the serving status.
l A Destination Signaling Point Unavailable (DUNS) message is reported by the
remote-end office of the association.

System Impact
Reception and sending of messages from/to the relevant office fail. The new services to
this office fail to be accessed, and the existing services are exceptionally released.

Handling Suggestion
1. On the Real-time Current Alarm Monitoring tab of the Fault Management window,
check whether there exists any related alarm (alarm code: 8402690).
l Yes: Handle the alarm by referring to the corresponding handling suggestions.
l No: Go to Step 2.
2. Run the SHOW AS command to check whether the AS configuration is correct.
l Yes: Go to Step 4.
l No: Go to Step 3.

Note:
l Routing Context ID and Service Mode at both ends must be the same.
l The Usage Tag of the AS must meet the following requirements. If ASP is
configured for the local end, the SGP must be configured for the remote end. If
the CLT (IPSP client) is configured for the local end, the SVR (IPSP server) must
be configured for the remote end.

3. Modify the AS configuration. Then check whether the alarm disappears.

l Yes: End alarm handling.

2-149

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l No: Go to Step 4.
4. Run the SHOW M3UART command to check whether the AS ID configured in the
M3UA static route configuration is correct.
l Yes: Go to Step 6.
l No: Go to Step 5.
5. Run the SET M3UART command to re-associate the correct AS ID. Then check
whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 6.
6. Run the SHOW SIOLOCAS command to check whether Service Indication and
M3UA Static Route ID configured in the SIO-locationg-AS configuration are correct.
l Yes: Go to Step 8.
l No: Go to Step 7.
7. Run the SET SIOLOCAS command to re-configure the correct Service Indication and
M3UA Static Route ID. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 8.
8. Check whether the configuration related to this office is correct at the remote end.
l Yes: Contact ZTE for help.
l No: Contact the maintenance engineer at the remote end for handling.

Related Alarm
2.3.23 8402690 Association Broken

2.3.20 8401152 SUA Subsystem Unavailable

Alarm Information
l Alarm code: 8401152
l Alarm name: SUA subsystem unavailable
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
l An adjacent signaling point subsystem is out of service.
l The destination signaling point of the SUA adjacent office is inaccessible.
l The local office or the remote-end adjacent office is not configured with the signaling
point subsystem.

System Impact
There is no outgoing route for services, which causes service failure.

2-150

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Handling Suggestion
1. On the Real-time Current Alarm Monitoring tab of the Fault Management window,
check whether there exists any related alarm (alarm code: 8401153).
l Yes: Handle the alarm by referring to the corresponding handling suggestions.
l No: Go to Step 2.
2. Run the SHOW N7SSN command to check whether the local office is configured
with the corresponding subsystem (including the local office being configured with
the corresponding subsystem, and the adjacent office being configured with the
corresponding subsystem).
l Yes: Go to Step 4.
l No: Go to Step 3.
3. Run the ADD N7SSN command to configure the corresponding subsystem. Then
check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 4.
4. Contact the remote-end-adjacent-office maintenance personnel to check the data
configuration of the remote-end adjacent office, checking whether the remote-end
adjacent office is configured with the corresponding subsystem (including the local
office being configured with the corresponding subsystem, and the adjacent office
being configured with the corresponding subsystem).
l Yes: Contact ZTE for help.
l No: Contact the maintenance engineer at the remote end for handling.

Related Alarm
2.3.21 8401153 SUA Office Inaccessible

2.3.21 8401153 SUA Office Inaccessible

Alarm Information
l Alarm code: 8401153
l Alarm name: SUA office inaccessible
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
l The association is broken, or the AS is not in the service status.
l The configured ASs for the local office or the adjacent office mismatch each other.
l No SSN-location-AS to this office is configured.
l The adjacent office of the association reports a DUNA (Destination Unavailable)
message, which causes the office inaccessible.

2-151

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
Messages cannot be sent to or received from the corresponding office. The new services
to this office fail to be accessed, and the existing services are exceptionally released.

Handling Suggestion
1. On the Real-time Current Alarm Monitoring tab of the Alarm Management window,
check whether there exists any related alarm (alarm code: 8402690).
l Yes: Handle the alarm by referring to the corresponding handling suggestions.
l No: Go to Step 2.
2. Run the SHOW SUAAS command to check the AS configuration at both ends. Check
whether the AS configuration at the local end matches the AS configuration at the
remote end.
l Yes: Go to Step 4.
l No: Go to Step 3.

Note:
Routing Context ID and Service Mode at both ends must be the same.
The Usage Tag of the AS must meet the following requirements. If ASP is configured
for the local end, the SGP must be configured for the remote end. If the CLT (IPSP
client) is configured for the local end, the SVR (IPSP server) must be configured for
the remote end.

3. Run the SET SUAAS command to modify the AS configuration. Then check whether
the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 4.
4. Run the SHOW SSNLOCAS command to check whether the SSN location to the
remote office is configured.
l Yes: Go to Step 6.
l No: Go to Step 5.
5. Run the ADD SSNLOCAS command to configure the SSN location to the remote office.
Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 6.
6. In the Trace Management window, trace the link to the SUA adjacent office. Check
whether the local office receives a DUNA message from the remote office.
l Yes: Contact the maintenance engineer at the remote end for handling.
l No: Contact ZTE for help.

2-152

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Related Alarm
2.3.23 8402690 Association Broken

2.3.22 8402688 Association Congested

Alarm Information
l Alarm code: 8402688
l Alarm name: Association congested
l Severity: Minor
l Alarm type: QoS alarm

Probable Cause
l The transmission quality of bottom layer link is poor.
l The upper-layer traffic in sending service data is heavy.

System Impact
Transmission delay, or even packet loss will occur. If congestion is not serious, the service
will not be affected. Otherwise, call loss may occur, and the access success rate of the
service may decrease.

Handling Suggestion
1. Check whether the network cable connection is proper.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Insert the network cable tightly. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Run the ADD M3UASCTP command to add SCTP to the office that is served by the
congested association.
l Yes: End alarm handling.
l No: Go to Step 4.
4. Check whether the intermediate equipment exists between the local end and the
remote end.
l Yes: Go to Step 5.
l No: Contact ZTE for help.
5. Check there exists any transmission alarm of the intermediate equipment.
l Yes: Contact the transmission engineer for handling.
l No: Contact ZTE for help.

2-153

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

2.3.23 8402690 Association Broken

Alarm Information
l Alarm code: 8402690
l Alarm name: Association broken
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
l The association configuration is modified.
l The association configuration is modified.
l The SIPI module is faulty.
l The network cable at the GE interface on the rear board of the GPBB0 board is loose.
l The IP bearer network is faulty.
l The IP bearer network suffers from severe packet loss.
l The switch suffers from broadcast storm.

System Impact
l This case may cause congestion in associations, and further cause call loss.
l Association breaking may cause load rising on the CPU of the SMP modules where
other associations sharing loads belong.
l If this association is the exclusive association to the signaling office, association
breaking will cause signaling office inaccessible, which will further affect normal
services.

Handling Suggestion
1. Run the SHOW CMDLOG command to check whether the association configuration
is recently modified in the Terminal window.
l Yes: Go to Step 2.
l No: Go to Step 4.
2. In the Terminal window, click the SIGTRAN Configuration node under the Protocol
Configuration node to check whether the association data configuration at the local
end and the remote end is consistent.
l The association data configuration at the local end and the remote end is
consistent, go to Step 4.
l The association data configuration at the local end and the remote end is not
consistent, go to Step 3.

2-154

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Note:
Check whether the following items are configured to be consistent:
a. The local port and remote port configuration at the local end is consistent with the
configuration at the remote end.
b. The local IP and remote IP configuration at the local end is consistent with the
configuration at the remote end.
c. The local application attribute and remote application attribute configuration at the
local end is consistent with the configuration at the remote end.

3. Modify the association data configuration, and synchronize it to the foreground. Then
wait for 30 seconds, check whether the alarm disappears.
l Yes: End alarm handling.
l No: The association still fails to be established, go to Step 4.
4. Run the SHOW SCTPSTAT command to check whether all associations are blocked.
l All associations are blocked, go to Step 5.
l One association is blocked, go to Step 6.
5. Run the RESTART SCTP command to restart all associations. Then check whether
the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 6.
6. Observe the additional information of the association breaking alarm to check
whether the reason for association breaking is Sctp BrokenDown: Receive
ShutDownAckfrom SCTP.
l Yes: The association is manually blocked, go to Step 7.
l No: Go to Step 8.
7. Run the EST SCTP command to activate the association. Then check whether the
alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 8.
8. Check the running status of the active SIPI module.
l The SIPI module runs normally, go to Step 9.
l The SIPI module is faulty and it is configured to 1+1 active/standby mode, go to
Step 11.
l The SIPI module is faulty, and it has no standby module, go to Step 14.
9. Check whether the network cable is well connected to the rear card of the SIPI module.
l Yes: Go to Step 16.
l No: Go to Step 10.
10. Adjust the local network cable connection. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 16.

2-155

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

11. The system automatically switches all services to the standby SIPI module. Check
whether the automatic switching is successful.
l Yes: Go to Step 12.
l No: Go to Step 13.
12. Wait for a while. Then check whether the active module runs normally and the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 16.
13. Run the SWP NORMAL command to switch the faulty SIPI module to the standby
module, and switch the originally standby module to the active one. Then check
whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 12.
14. Run the RESET NORMAL command to reset the faulty SIPI module. The check
whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 15.
15. Replace the board. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 16.
16. On the Real-time Current Alarm Monitoring tab of the Fault Management window,
check whether there is any bottom-layer transmission alarm in the SIPI slot where the
faulty association is located.
l Yes: Contact the transmission engineer for handling.
l No: Go to Step 17.
17. On the Real-time Current Alarm Monitoring tab of the Fault Management window,
check whether there exists any related alarm (alarm code: 8417537).
l Yes: Handle the alarm by referring to the corresponding handling suggestions.
l No: Go to Step 18.
18. Run the PING command to ping the real-interface address of the remote-end SIPI
module. Check whether there is sever packet loss on the physical link.
l Yes: Contact the transmission engineer for handling.
l No: Go to Step 19.
19. Check whether the switch connecting NEs through SIPI has broadcast storm that
causes an interface exception. Connect a cross-connect cable temporarily to an GE
port on the rear card of an SIPI module. Then check whether the alarm disappears.
l Yes: The switch has some problem. Contact the special data maintenance
engineer for handling.
l No: Contact ZTE for help.

Related Alarm
2.3.36 8417537 Association Path Broken

2-156

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

2.3.24 8402944 STC Office Inaccessible

Alarm Information
l Alarm code: 8402944
l Alarm name: STC office inaccessible
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
All the associations to this STC office are not in service status.

System Impact
MSCS fail to receive/send messages from/to the corresponding office. The new services
to this office fail to be accessed, and the existing services are exceptionally released.

Handling Suggestion
1. On the Real-time Current Alarm Monitoring tab of the Fault Management window,
check whether there exists any related alarm (alarm code: 8402690).
l Yes: Handle the alarm by referring to the corresponding handling suggestions.
l No: Go to Step 2.
2. In the Terminal window, click the SIGTRAN Configuration node under the Protocol
Configuration node to check whether the related association to this office is
configured.
l Yes: Contact ZTE for help.
l No: Go to Step 3.
3. Add the related association to this office. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

Related Alarm
2.3.23 8402690 Association Broken

2.3.25 8402945 STC Office Congested

Alarm Information
l Alarm code: 8402945
l Alarm name: STC office congested
l Severity: Minor
l Alarm type: QoS alarm

2-157

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Probable Cause
There are available associations to this office, but at least one association is in the
congested status.

System Impact
Transmission delay, or even packet loss will occur. If congestion is not serious, the service
will not be affected. Otherwise, call loss may occur, and the access success rate of the
service may decrease.

Handling Suggestion
1. On the Real-time Current Alarm Monitoring tab of the Fault Management window,
record the STC office ID where this alarm appears, and user type in the Details row,
such as H.248 and BICC.
2. On the Real-time Current Alarm Monitoring tab of the Fault Management window,
check whether the office recorded in Step 1 has related alarm (alarm code: 8402688).
l Yes: Handle the alarm by referring to the corresponding handling suggestions.
l No: all the associations to this STC office are not in the congested status, the
alarm will automatically disappear.

Related Alarm
2.3.22 8402688 Association Congested

2.3.26 8403456 Number of Signaling Message Transferring Exceeds

Allowed Threshold of the License
Alarm Information
l Alarm code: 8403456
l Alarm name: Number of signaling message transferring exceeds allowed threshold
of the license
l Severity: Major
l Alarm type: QoS alarm

Probable Cause
The number of messages forwarded by MTP3/M3UA/SCCP/SUA is greater than the
maximum number specified in the license.

System Impact
When the number of messages forwarded is greater than the maximum number specified
in the license, extra messages may be discarded.

2-158

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Handling Suggestion
Obtain a new license as appropriate. Contact ZTE for help.

2.3.27 8406528 The Protocol State of Port-Channel Interface Is

Down
Alarm Information
l Alarm code: 8406528
l Alarm name: The protocol state of port-channel interface is down
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
l The aggregate port has no member ports.
l All member ports of the aggregate port are in Down state.

System Impact
The upper layer services may be interrupted.

Handling Suggestion
1. Check whether the aggregate port has member ports.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Configure member ports for the aggregate port. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether all member ports are in Down state.
l Yes: Go to Step 4.
l No: Contact ZTE for help.
4. Check the links of the member ports and restore the ports to Up state. Then check
whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.3.28 8406529 The Protocol State of Supervlan Interface Is Down

Alarm Information
l Alarm code: 8406529
l Alarm name: The protocol state of supervlan interface is down
l Severity: Minor

2-159

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Alarm type: Communication alarm

Probable Cause
l The supervlan port has no member ports.
l All member ports of the supervlan port are in Down state.

System Impact
The upper layer services may be interrupted.

Handling Suggestion
1. Check whether the supervlan port has member ports.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Configure member ports for the supervlan port. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether all member ports are in Down state.
l Yes: Go to Step 4.
l No: Contact ZTE for help.
4. Check the links of the member ports and restore the ports to Up state. Then check
whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.3.29 8407043 PPP Link Is Down

Alarm Information
l Alarm code: 8407043
l Alarm name: PPP link is down
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
l The physical link is broken, or the transmission quality of link is poor.
l A PPP port is created or modified.
l The active board is powered on, or the standby board is successfully switched to the
active one.
l Modifying the parameter of the PPP link causes link re-negotiation.
l The other side of the link re-initiates negotiation.
l The ports of the two sides of the link is inconsistent.

2-160

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

System Impact
The service is interrupted.

Handling Suggestion
1. Make no intervention, and wait for the system to be automatically restored. After 30
seconds, check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 2.
2. Check whether the connection cable between the equipment at two sides is
disconnected or loose according to the PPP port number in the detailed alarm
information.
l The connection cable is disconnected or loose, go to Step 3.
l The connection cable is normal, go to Step 4.
3. Plug and unplug the cable again, or replace the cable. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 4.
4. Refer to the networking planning information of users to check whether the E1
connection is correct.
l Yes: Go to Step 6.
l No: Go to Step 5.
5. Connect cables according to the planning information. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 6.
6. Run the IPSTACK command to enter the IP stack mode. Run the SHOW CHANNEL
command to check whether Unit and Sub-unit are configured to be consistent with
those at the remote end.
l Yes: Go to Step 8.
l No: Go to Step 7.
7. Modify the configuration to keep consistency between two ends. Then check whether
the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 8.
8. Run the IPSTACK command to enter the IP stack mode. Run the SHOW PPP INTE
RFACE command to check whether the data configuration is correct.
l Yes: Contact ZTE for help.
l No: Go to Step 9.
9. Modify the configuration to keep the connections of the PPP port consistent between
two ends. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-161

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

2.3.30 8407298 The Configuration of BSCIP in Database Is Wrong

Alarm Information
l Alarm code: 8407298
l Alarm name: The configuration of BSCIP in database is wrong
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
l BSCIP is not configured.
l The IP address in BSCIP configuration is illegal.

System Impact
ABPM cannot locate other problems by self-loop.

Handling Suggestion
1. Check whether BSCIP configuration is correct.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Modify the BSCIP configuration correctly. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check the internal link between OMP and ABPM is normal.
l Yes: Go to Step 5.
l No: Go to Step 4.
4. Check alarms related to internal communication, and handle the alarm by referring to
the corresponding handling suggestions. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 5.
5. Ensure that data synchronization is performed after previous data configuration. Wait
for a while and configure again. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Record current BSCIP configuration, Contact ZTE for help.

2.3.31 8411392 BFD Session Interruption

Alarm Information
l Alarm code: 8411392
l Alarm name: BFD Session Interruption
l Severity: Minor
l Alarm type: Communication alarm

2-162

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Probable Cause
The UDP layer link over which the BFD session runs fails, and thus the BFD session enters
Down state.

System Impact
The service is interrupted.

Handling Suggestion
1. Check whether the physical link between the source IP address and the destination
IP address of the session is clear.
l Link is broken, go to Step 2.
l Link is clear, go to Step 3.
2. Repair the link or replace the cable. After 30 seconds, check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether the intermediate transmission equipment works properly.
l Yes: Contact ZTE for help.
l No: Contact the transmission engineer for handling.

2.3.32 8411393 BFD Session Negotiation Failure

Alarm Information
l Alarm code: 8411393
l Alarm name: BFD session negotiation failure
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
l The remote-end equipment is configured with no BFD session.
l The bottom-layer link where the BFD session runs is faulty.

System Impact
The service is interrupted.

Handling Suggestion
1. Check whether the remote-end equipment is configured with a BFD session.
l Yes: Go to Step 3.
l No: Go to Step 2.

2-163

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

2. Configure a BFD session on the remote-end equipment, or delete the BFD session
from the local equipment according to the actual situation. Then check whether the
alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether the physical link between the source IP address and the destination
IP address of the session is clear.
l Yes: Go to Step 5.
l No: Go to Step 4.
4. Repair the link or replace the cable. After 30 seconds, check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 5.
5. Check whether the intermediate transmission equipment works properly.
l Yes: Contact ZTE for help.
l No: Contact the transmission engineer for handling.

2.3.33 8411649 The Number of Alarms on the Manager Board

Exceeds the Threshold
Alarm Information
l Alarm code: 8411649
l Alarm name: The number of alarms on the manager board exceeds the threshold
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
There are too many alarm messages on this board, and the alarm pool saving the alarm
messages on this board is full.

System Impact
Alarm messages are lost, which has no influence on the service.

Handling Suggestion
In the Fault Management window of the LMT, delete the alarms you are not concerned
with. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-164

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

2.3.34 8411651 The Number of Logical Alarms on the Board

Exceeds the Threshold
Alarm Information
l Alarm code: 8411651
l Alarm name: The number of logical alarms on the board exceeds the threshold
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
There are too many alarm messages on this board, and the alarm pool saving the alarm
messages on this board is full.

System Impact
Alarm messages are lost, which has no influence on the service.

Handling Suggestion
Check whether there are virtually configured resources not used temporarily. If yes, delete
them. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.3.35 8412416 Fail to Load XML Script Files

Alarm Information
l Alarm code: 8412416
l Alarm name: Fail to load XML script files
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
Reading the XML script file fails, or the file format is incorrect.

System Impact
Related OAM functions cannot be used.

Handling Suggestion
1. Check whether the format of the XML files are correct.
l Yes: Go to Step 2.
l No: Contact ZTE for help.

2-165

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

2. Re-loading version package.

l Yes: End alarm handling.
l No: Contact ZTE for help.

2.3.36 8417537 Association Path Broken

Alarm Information
l Alarm code: 8417537
l Alarm name: Association path broken
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
l Network communication is faulty.
l Control plane path in NE is interrupted.
l Opposite equipment is faulty.
l The route to remote address is lost.

System Impact
If multiple paths are available for the association and there exists normal path, relevant
services will not be affected. If merely one path is available for the association, all services
on the association is down.

Handling Suggestion
1. In the Terminal window, select Protocol Configuration > SIGTRAN Configuration >
M3UA Configuration > M3UA Static Route Configuration to query the information
about the router to the remote address. Check whether the network cable on the
egress is loose or broken.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Unplug the network cable or replace it with a new one. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. In the Terminal window, select Protocol Configuration > SIGTRAN Configuration
to query the module number to which the association belongs. Check whether the
board corresponding to the module number has a related alarm (code: 8393985).
l Yes: Handle the alarm by referring to the corresponding handling suggestions.
l No: Go to Step 4.
4. In the Terminal window, select Protocol Configuration > SIGTRAN Configuration
> M3UA Configuration > M3UA Static Route Configuration to check whether there
is any route to the remote address of the association.
l Yes: Go to Step 6.

2-166

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l No: Go to Step 5.
5. Add a route to th remote address. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 6.
6. Check the interim devices along the association route and see whether they have any
route to the local and remote addresses of the association.
l Yes: Go to Step 8.
l No: Go to Step 7.
7. Refer to the operation manual of the related devices to add a route. Then check
whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 8.
8. Ask the remote office to check the remote device and see whether it has any route to
the local address of the association.
l Yes: Go to Step 9.
l No: Contact the maintenance engineer at the remote end for handling.
9. Ask the remote office to check whether the remote device has any failure.
l Yes: Contact the maintenance engineer at the remote end for handling.
l No: Contact ZTE for help.

Related Alarm
2.3.4 8393985 Control Plane Communication Abnormal Between Board and Its Home
Module

2.3.37 8419073 Bearer Network Is Unavailable

Alarm Information
l Alarm code: 8419073
l Alarm name: Bearer network is unavailable
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
l The intermediate device loses packets, which possibly causes the quality of the bearer
network decreasing.
l 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.

2-167

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Handling Suggestion
1. Check whether the intermediate device is faulty.
l Yes: Go to Step 4.
l No: Go to Step 2.
2. Check whether the network interface of the board is normal.
l Yes: Contact ZTE for help.
l No: Go to Step 3.
3. Check whether any hardware problem causes the network interface failing to function
properly.
l Yes: Go to Step 4.
l No: Contact ZTE for help.
4. Replace the related device, and check whether the link is normal. Then check whether
the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.3.38 8419074 Bearer Network Get Worse

Alarm Information
l Alarm code: 8419074
l Alarm name: Bearer network get worse
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
l The intermediate device loses packets, which possibly causes the quality of the bearer
network decreasing.
l Packet loss occurs in some section of the environment of both the sides, which also
possibly causes the quality of the bearer network decreasing.

System Impact
The quality of the services on the bear network get worse.

Handling Suggestion
1. Check whether the intermediate device is faulty.
l Yes: Go to Step 4.
l No: Go to Step 2.
2. Check whether the network interface of the board is normal.
l Yes: Contact ZTE for help.
l No: Go to Step 3.
3. Check whether any hardware problem causes the network interface failing to function
properly.

2-168

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l Yes: Go to Step 4.
l No: Contact ZTE for help.
4. Replace the related device, and check whether the link is normal. Then check whether
the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.3.39 8419840 PTP Failed to Get Clock Attribute

Alarm Information
l Alarm code: 8419840
l Alarm name: PTP failed to get clock attribute
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
PTP fails to obtain the clock attribute.

System Impact
The PTP function cannot be used.

Handling Suggestion
1. Check whether the clock board is powered on successfully (the RUN indicator flashes
at 1 Hz).
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Reset the board to normal. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
3. In the Fault Management window, check whether there exists any control-plane
communication exception alarm (alarm code: 8393985).
l Yes: Handle the alarm by referring to the corresponding handling suggestions.
l No: Contact ZTE for help.

Related Alarm
2.3.4 8393985 Control Plane Communication Abnormal Between Board and Its Home
Module

2-169

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

2.3.40 8429568 Broadband Link Unavailable

Alarm Information
l Alarm code: 8429568
l Alarm name: Broadband link unavailable
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
l The bottom-layer physical transmission is disconnected.
l The remote end disconnects the link.
l Too many messages not confirming with the protocols or error packets are received.

System Impact
The office may be inaccessible, or other available links are congested.

Handling Suggestion
1. Check whether there are new data configured for the link or the configuration has been
modified.
l Yes: Go to Step 2.
l No: Go to Step 4.
2. Check the data configuration of the link, focusing on the VPIs and VCIs of the two
ends, and the port of the remote end.
l Yes: Go to Step 4.
l No: Go to Step 3.
3. Modify the configuration. Ensure that the configuration of the two sides of the link is
correct. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 4.
4. Check whether any alarm exists on the bottom-layer transmission.
l Yes: Contact the transmission engineer for handling.
l No: Go to Step 5.
5. Perform physical self-loop of the link, self looping the devices at the both ends of the
link at the DDF frame. Check whether the alarm disappears.
l Yes: Contact the transmission engineer for handling.
l No: Contact ZTE for help.

2-170

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

2.4 10000000~99999999
2.4.1 25167105 Alarm of Server Disconnected With MGW
Alarm Information
l Alarm code: 25167105
l Alarm name: Alarm of server disconnected with mgw
l Severity: Critical
l Alarm type: Communication alarm

Probable Cause
l If the MSCS has the intermittent-disconnection protection function (ADD MGSMOD),
when the connection with the MGW is broken, and the connection is not restored when
the intermittent-disconnection protection timer (ADD MGSMOD) expires, this alarm is
reported.
l When the intermittent-disconnection protection switch is not opened, the H248S
directly reports the alarm of MGW being inaccessible after receiving the message of
MGW being inaccessible (including SCTP/M3UA).

System Impact
The calls related with this MGW fail.

Handling Suggestion
1. Check whether the connection with the MGW is normal.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Re-establish the link with the gateway. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.4.2 25167106 MGW Is Out of Service

Alarm Information
l Alarm code: 25167106
l Alarm name: MGW is out of service
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
The MGW is out of service.

2-171

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
The call involving this node failed to be initiated.

Handling Suggestion
1. Check the link status between the MSCS and the MGW.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Re-establish the link between MSCS and MGW. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether the MGW is manually set to be out of service.
l Yes: Go to Step 5.
l No: Go to Step 4.
4. Start the MGW. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 5.
5. Check whether any exception exists on the corresponding MGW.
l Yes: Contact the maintenance engineer at the MGW side for handling.
l No: Contact ZTE for help.

2.4.3 25167872 D-Channel Signal Link Is Broken

Alarm Information
l Alarm code: 25167872
l Alarm name: D-channel signal link is broken
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
D-channel signal link is broken.

System Impact
Services on the D-channel signal link are interrupted.

Handling Suggestion
1. Check whether the D-channel is configured correctly.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Re-configure the D-channel data. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.

2-172

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

3. Check whether the office status at the remote end is normal.

l Yes: Contact ZTE for help.
l No: Contact the maintenance engineer of the remote end for handling.

2.4.4 25170946 ENUM/DNS BYPASS Is Evoked by Manual

Alarm Information
l Alarm code: 25170946
l Alarm name: ENUM/DNS BYPASS is evoked by manual
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
The ENUM/DNS BYPASS function is enabled manually.

System Impact
The link between the MSCS and the DNS/ENUM server is in unreachable status. It is
required to enable the standby static route to complete call routing.

Handling Suggestion
1. Check whether the operation of manually enabling the DNS BYPASS function is
performed unintentionally.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Disable the DNS BYPASS function. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.4.5 25170947 ENUM/DNS BYPASS Is Evoked by System

Automatically
Alarm Information
l Alarm code: 25170947
l Alarm name: ENUM/DNS BYPASS is evoked by system automatically
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
The ENUM/DNS BYPASS function is enabled automatically by the system.

2-173

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
The link between the MSCS and the DNS/ENUM server is in unreachable status. It is
required to enable the standby static route to complete call routing.

Handling Suggestion
1. Check whether the quality of bearer between the DNS server and the NE and bearer
related interface boards are normal.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore the quality of bearer between the DNS server and the NE and bearer related
interface boards to normal. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.4.6 25171456 SIP Office Is Unreachable

Alarm Information
l Alarm code: 25171456
l Alarm name: SIP office is unreachable
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
There is no serving link to the SIP office.

System Impact
Messages cannot be sent to or received from the corresponding office. New services under
this office fail to be accessed, and some existing services are released exceptionally.

Handling Suggestion
1. On the Real-time Current Alarm Monitoring tab of the Fault Management window,
check whether there exists any related alarm (alarm code: 33577435).
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. handle the alarm by referring to the corresponding handling suggestions. Then check
whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact the maintenance engineer of the remote end to check the office
configuration.

2-174

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Related Alarm
2.4.71 33577435 SIP Link Broken

2.4.7 25171458 SIP Node Switch

Alarm Information
l Alarm code: 25171458
l Alarm name: SIP node switch
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
SIP node changeover occurs.

System Impact
The alarming office experiences disaster recovery.

Handling Suggestion
1. Check whether the changeover mode is manual or automatic.
l Automatic, go to Step 2.
l Manual, go to Step 4.
2. Check whether the SIP node is in normal state.
l Yes: Contact ZTE for help.
l No: Go to Step 3.
3. Restore the SIP node to normal. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
4. View operation logs and check whether the operations are correct.
l Yes: Contact ZTE for help.
l No: Go to Step 5.
5. Correct the operations. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.4.8 25172481 System Now Is in IP Congestion Situation

Alarm Information
l Alarm code: 25172481
l Alarm name: System now is in IP Congestion situation.
l Severity: Major
l Alarm type: Processing error alarm

2-175

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Probable Cause
The bearer QoS corresponding to the bearer ID decreases. Congestion occurs.

System Impact
The speech quality of calls is very poor.

Handling Suggestion
1. Check whether the call quantity on the corresponding bearer is normal.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Expand the bearer capacity to solve the congestion. After the call quantity on the
bearer becomes normal, check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.4.9 25172482 IPQos Test Calls During a Period All Failed

Alarm Information
l Alarm code: 25172482
l Alarm name: IPQos test calls during a period all failed
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
All the tests calls within a period fail, and none of the failures is due to bearer establishment
errors.

System Impact
All the IP QoS tests calls within a period fail.

Handling Suggestion
1. Check whether the test numbers are configured correctly.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Modify the configuration of test numbers. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether the routes associated with the test numbers are configured correctly.
l Yes: Contact ZTE for help.
l No: Go to Step 4.

2-176

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

4. Modify the configuration of the route associated with the test numbers. Then check
whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.4.10 25172992 System Dynamic Recovery Monitor Index

Abnormity
Alarm Information
l Alarm code: 25172992
l Alarm name: System dynamic recovery monitor index abnormity
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
The dynamic recovery monitoring index in system self-testing is abnormal.

System Impact
The index monitoring condition is abnormal.

Handling Suggestion
1. Check whether monitoring index configuration is correct.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Modify monitoring index configuration properly. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.4.11 25173248 LIG TCP Link Is Broken

Alarm Information
l Alarm code: 25173248
l Alarm name: LIG tcp link is broken.
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
The TCP link to LIG is broken.

2-177

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
The lawful interception function is exceptional.

Handling Suggestion
1. Check whether the bottom-layer communication is normal.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. LIG automatically establishes a TCP link to the NE. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.4.12 25173249 LIG TCP Link Initiation Failed

Alarm Information
l Alarm code: 25173249
l Alarm name: LIG TCP link initiation failed
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
Initialization of the TCP link to LIG is abnormal.

System Impact
The TCP link to LIG is broken.

Handling Suggestion
1. Check whether the bottom-layer communication is normal.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Check whether LIG runs normally.
l Yes: Contact ZTE for help.
l No: Contact the maintenance engineer of the LIG equipment for handling.

2.4.13 33560234 Down Link Between NE and CU

Alarm Information
l Alarm code: 33560234
l Alarm name: Down link between NE and CU.
l Severity: Minor
l Alarm type: Communication alarm

2-178

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Probable Cause
The connection between the charging forwarding proxy and the charging server is
interrupted.

System Impact
CDR files cannot be sent.

Handling Suggestion
1. Check whether the link between the charging forwarding proxy and the charging server
is normal.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Restore the link between the charging forwarding proxy and the charging server to
normal. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether the charging server is in working state.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Restore the charging server to working state. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.4.14 33560235 Generate Backlog CDR File

Alarm Information
l Alarm code: 33560235
l Alarm name: Generate backlog CDR file
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
The charging forwarding proxy cannot send CDRs to the charging server in time, so many
CDRs are accumulated.

System Impact
CDRs are overstocked, which impacts on billing.

Handling Suggestion
1. Check whether the link between the MSCS and charging server is normal.

2-179

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Yes: Go to Step 3.
l No: Go to Step 2.
2. Restore the link between the MSCS and charging server to normal. Then check
whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether the charging server is in working state.
l Yes: Go to Step 5.
l No: Go to Step 4.
4. Restore the charging server to working state. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 5.
5. Check whether the processing capability of the charging server is insufficient.
l Yes: Go to Step 6.
l No: Contact ZTE for help.
6. Restore the processing capability of the charging server. Then check whether the
alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.4.15 33560236 Read or Write Backlog CDR Files Failed

Alarm Information
l Alarm code: 33560236
l Alarm name: Read or write backlog CDR files failed
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
The overstocked CDR files fail to be read/written.

System Impact
CDR files may be lost.

Handling Suggestion
Download the error files to the local computer, and Contact ZTE for help.

2.4.16 33560237 The Free Space of MP for CDR Is Less Than 50M
Alarm Information
l Alarm code: 33560237

2-180

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l Alarm name: The free space of MP for CDR is less than 50M
l Severity: Critical
l Alarm type: QoS alarm

Probable Cause
l There is no sufficient space for saving CDRs on the billing foreground.
l The hard disk is faulty.
l The hard disk does not exist.

System Impact
l CDRs cannot be sent to the billing center.
l Because there is no free space to save CDRs on the MP, CDRs will be lost.

Handling Suggestion
1. Check whether the link between the billing forwarding proxy and the CU is normal.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Restore the link between the charging forwarding proxy and the charging server to
normal. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether the CU is in the working status.
l Yes: Go to Step 5.
l No: Go to Step 4.
4. Restore the charging server to normal. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 5.
5. Check the status of the hard disk of the foreground.
l Yes: Contact ZTE for help.
l No: Go to Step 6.
6. Repaid the hard disk on foreground. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.4.17 33560238 The Free Space of MP for CDR Is Less Than 100M
Alarm Information
l Alarm code: 33560238
l Alarm name: The free space of MP for CDR is less than 100M
l Severity: Major
l Alarm type: QoS alarm

2-181

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Probable Cause
l There is no sufficient space for saving CDRs on the billing foreground.
l The link between the charging forwarding proxy and the charging server is abnormal.

System Impact
l CDRs cannot be sent to the billing center.
l Because there is no free space to save CDRs on the MP, CDRs will be lost.

Handling Suggestion
1. Check the link between the billing forwarding proxy and the CU.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Restore the link between the charging forwarding proxy and the charging server to
normal. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether the CU is in the working status.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Restore the charging server to normal. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.4.18 33560239 The Free Space of MP for CDR Is Less Than 200M
Alarm Information
l Alarm code: 33560237
l Alarm name: The free space of MP for CDR is less than 200M
l Severity: Minor
l Alarm type: QoS alarm

Probable Cause
l There is no sufficient space for saving CDRs on the billing foreground.
l The link between the billing forwarding proxy and the CU is broken.

System Impact
l CDRs cannot be sent to the billing center.
l Because there is no free space to save CDRs on the MP, CDRs will be lost.

Handling Suggestion
1. Check the link between the billing forwarding proxy and the CU.

2-182

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l Yes: Go to Step 3.
l No: Go to Step 2.
2. Restore the link between the charging forwarding proxy and the charging server to
normal. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether the CU is in the working status.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Restore the charging server to normal. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.4.19 33560240 The Backlog CDR File Is Over 600M

Alarm Information
l Alarm code: 33560240
l Alarm name: The backlog CDR file is over 600M
l Severity: Major
l Alarm type: QoS alarm

Probable Cause
l The physical link between the billing forwarding proxy and the CU is disconnected.
l The CU does not work.

System Impact
l CDRs cannot be sent to the billing center.
l Because there is no free space to save CDRs on the MP, CDRs will be lost.

Handling Suggestion
1. Check whether the link between the billing forwarding proxy and the CU is normal.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Restore the link between the charging forwarding proxy and the charging server to
normal. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether the CU is in working status.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Restore the charging server to normal. Then check whether the alarm disappears.
l Yes: End alarm handling.

2-183

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l No: Contact ZTE for help.

2.4.20 33560241 The Backlog CDR File Is Over 1.2G

Alarm Information
l Alarm code: 33560241
l Alarm name: The backlog CDR file of NE is over 1.2G
l Severity: Critical
l Alarm type: QoS alarm

Probable Cause
l The physical link between the billing forwarding proxy and the CU is disconnected.
l The CU does not work.

System Impact
l CDRs cannot be sent to the billing center.
l Because there is no free space to save CDRs on the MP, CDRs will be lost

Handling Suggestion
1. Check whether the link between the billing forwarding proxy and the CU is normal.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Restore the link between the charging forwarding proxy and the charging server to
normal. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether the CU is in working status.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Restore the charging server to normal. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.4.21 33560242 Generate Backlog ACR File

Alarm Information
l Alarm code: 33560242
l Alarm name: Generate backlog ACR file
l Severity: Minor
l Alarm type: Processing error alarm

2-184

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Probable Cause
l The physical link between the GPBB0 and the CU is broken.
l The CU does not work.
l The CU configuration is incorrect.

System Impact
CDRs cannot be sent to the billing center.

Handling Suggestion
1. Check whether there is Diameter signaling interaction at the Rf interface between the
MGCF and the CU.
l Yes: The link between the OCG and the CU is clear, go to Step 2.
l No: The link between the OCG and the CU is broken, handle the alarm by referring
to the corresponding handling suggestions.

Note:
In the MML Terminal window of the Charging Management Console, select View >
Signaling Trace to open the Signaling Trace window. Click the Diameter node under
the Signaling Trace node to check whether there is Diameter signaling interaction at
the Rf interface between the MGCF and the CU.

2. Check whether the CU is in working status.

l Yes: Contact ZTE for help.
l No: Go to Step 3.

Note:
In the MML Terminal window of the Charging Management Console, run the SHOW
CGSTAT command to check whether the CU is in working status.

3. Check whether the CU configuration has been changed recently.

l Yes: Go to Step 4.
l No: Contact ZTE for help.
4. Recover its original configuration.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-185

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Related Alarm
2.4.64 33576907 Diameter Link Broken

2.4.22 33560243 Read ACR File Failed in OCG

Alarm Information
l Alarm code: 33560243
l Alarm name: Read ACR file failed in OCG
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
The hard disk of the GPBB0 is destroyed.

System Impact
Failing to read CDR files on the MP may cause CDR files lost.

Handling Suggestion
Check whether the hard disk functions properly.
l Yes: End alarm handling after the alarm disappears.
l No: Contact the ZTE technical support personnel to replace the hard disk.

2.4.23 33560244 The Free Space for ACR Is Less Than 50M in OCG
Alarm Information
l Alarm code: 33560244
l Alarm name: The free space for ACR is less than 50M in OCG
l Severity: Critical
l Alarm type: QoS alarm

Probable Cause
l The physical link between the GPBB0 and the CU is broken.
l The CU does not work.
l The CU configuration is incorrect.
l The hard disk of the GPBB0 is destroyed.

System Impact
l CDRs cannot be sent to the billing center.
l Because there is no free space to save CDRs on the MP, CDRs will be lost.

2-186

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Handling Suggestion
1. Check whether there is Diameter signaling interaction at the Rf interface between the
MGCF and the CU.
l Yes: The link between the OCG and the CU is clear, go to Step 2.
l No: The link between the OCG and the CU is broken, handle the alarm by referring
to the corresponding handling suggestions.

Note:
In the MML Terminal window of the Charging Management Console, select View >
Signaling Trace to open the Signaling Trace window. Click the Diameter node under
the Signaling Trace node to check whether there is Diameter signaling interaction at
the Rf interface between the MGCF and the CU.

2. Check whether the CU is in working status.

l Yes: Contact ZTE for help.
l No: Go to Step 3.

Note:
In the MML Terminal window of the Charging Management Console, run the SHOW
CGSTAT command to check whether the CU is in working status.

3. Check whether the CU configuration has been changed recently.

l Yes: Go to Step 4.
l No: Contact ZTE for help.
4. Recover its original configuration.
l Yes: End alarm handling.
l No: Contact ZTE for help.
5. Check whether the hard disk functions properly.
l Yes: End alarm handling after the alarm disappears.
l No: Contact the ZTE technical support personnel to replace the hard disk.

Related Alarm
2.4.64 33576907 Diameter Link Broken

2-187

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

2.4.24 33560245 The Free Space for ACR Is Less Than 100M in OCG
Alarm Information
l Alarm code: 33560245
l Alarm name: The free space for ACR is less than 100M in OCG
l Severity: Major
l Alarm type: QoS alarm

Probable Cause
l The physical link between the GPBB0 and the CU is broken.
l The CU does not work.
l The CU configuration is incorrect.

System Impact
CDRs cannot be sent to the billing center.

Handling Suggestion
1. Check whether there is Diameter signaling interaction at the Rf interface between the
MGCF and the CU.
l Yes: The link between the OCG and the CU is clear, go to Step 2.
l No: The link between the OCG and the CU is broken, handle the alarm by referring
to the corresponding handling suggestions.

Note:
In the MML Terminal window of the Charging Management Console, select View >
Signaling Trace to open the Signaling Trace window. Click the Diameter node under
the Signaling Trace node to check whether there is Diameter signaling interaction at
the Rf interface between the MGCF and the CU.

2. Check whether the CU is in working status.

l Yes: Contact ZTE for help.
l No: Go to Step 3.

Note:

In the MML Terminal window of the Charging Management Console, run the SHOW
CGSTAT command to check whether the CU is in working status.

2-188

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

3. Check whether the CU configuration has been changed recently.

l Yes: Go to Step 4.
l No: Contact ZTE for help.
4. Recover its original configuration.
l Yes: End alarm handling.
l No: Contact ZTE for help.

Related Alarm
2.4.64 33576907 Diameter Link Broken

2.4.25 33560246 The Free Space for ACR Is Less Than 200M in OCG
Alarm Information
l Alarm code: 33560245
l Alarm name: The free space for ACR is less than 200M in OCG
l Severity: Minor
l Alarm type: QoS alarm

Probable Cause
l The physical link between the GPBB0 and the CU is broken.
l The CU does not work.
l The CU configuration is incorrect.

System Impact
CDRs cannot be sent to the billing center.

Handling Suggestion
1. Check whether there is Diameter signaling interaction at the Rf interface between the
MGCF and the CU.
l Yes: The link between the OCG and the CU is clear, go to Step 2.
l No: The link between the OCG and the CU is broken, handle the alarm by referring
to the corresponding handling suggestions.

Note:

In the MML Terminal window of the Charging Management Console, select View >
Signaling Trace to open the Signaling Trace window. Click the Diameter node under
the Signaling Trace node to check whether there is Diameter signaling interaction at
the Rf interface between the MGCF and the CU.

2-189

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

2. Check whether the CU is in working status.

l Yes: Contact ZTE for help.
l No: Go to Step 3.

Note:
In the MML Terminal window of the Charging Management Console, run the SHOW
CGSTAT command to check whether the CU is in working status.

3. Check whether the CU configuration has been changed recently.

l Yes: Go to Step 4.
l No: Contact ZTE for help.
4. Recover its original configuration.
l Yes: End alarm handling.
l No: Contact ZTE for help.

Related Alarm
2.4.64 33576907 Diameter Link Broken

2.4.26 33560247 The Backlog ACR File in the OCG Is Over 600M
Alarm Information
l Alarm code: 33560247
l Alarm name: The backlog ACR file in the OCG is over 600M
l Severity: Major
l Alarm type: QoS alarm

Probable Cause
l The physical link between the GPBB0 and the CU is broken.
l The CU does not work.
l The CU configuration is incorrect.

System Impact
CDRs cannot be sent to the billing center.

Handling Suggestion
1. Check whether there is Diameter signaling interaction at the Rf interface between the
MGCF and the CU.
l Yes: The link between the OCG and the CU is clear, go to Step 2.

2-190

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l No: The link between the OCG and the CU is broken, handle the alarm by referring
to the corresponding handling suggestions.

Note:
In the MML Terminal window of the Charging Management Console, select View >
Signaling Trace to open the Signaling Trace window. Click the Diameter node under
the Signaling Trace node to check whether there is Diameter signaling interaction at
the Rf interface between the MGCF and the CU.

2. Check whether the CU is in working status.

l Yes: Contact ZTE for help.
l No: Go to Step 3.

Note:
In the MML Terminal window of the Charging Management Console, run the SHOW
CGSTAT command to check whether the CU is in working status.

3. Check whether the CU configuration has been changed recently.

l Yes: Go to Step 4.
l No: Contact ZTE for help.
4. Recover its original configuration.
l Yes: End alarm handling.
l No: Contact ZTE for help.

Related Alarm
2.4.64 33576907 Diameter Link Broken

2.4.27 33560248 The Backlog ACR File in the OCG Is Over 1.2G
Alarm Information
l Alarm code: 33560248
l Alarm name: The backlog ACR file in the OCG is over 1.2G
l Severity: Critical
l Alarm type: QoS alarm

Probable Cause
l The physical link between the GPBB0 and the CU is broken.

2-191

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l The CU does not work.

l The CU configuration is incorrect.

System Impact
CDRs cannot be sent to the billing center.

Handling Suggestion
1. Check whether there is Diameter signaling interaction at the Rf interface between the
MGCF and the CU.
l Yes: The link between the OCG and the CU is clear, go to Step 2.
l No: The link between the OCG and the CU is broken, handle the alarm by referring
to the corresponding handling suggestions.

Note:
In the MML Terminal window of the Charging Management Console, select View >
Signaling Trace to open the Signaling Trace window. Click the Diameter node under
the Signaling Trace node to check whether there is Diameter signaling interaction at
the Rf interface between the MGCF and the CU.

2. Check whether the CU is in working status.

l Yes: Contact ZTE for help.
l No: Go to Step 3.

Note:
In the MML Terminal window of the Charging Management Console, run the SHOW
CGSTAT command to check whether the CU is in working status.

3. Check whether the CU configuration has been changed recently.

l Yes: Go to Step 4.
l No: Contact ZTE for help.
4. Recover its original configuration.
l Yes: End alarm handling.
l No: Contact ZTE for help.

Related Alarm
2.4.64 33576907 Diameter Link Broken

2-192

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

2.4.28 33560249 Buffer of CDR Is Full

Alarm Information
l Alarm code: 33560249
l Alarm name: Buffer of CDR is full
l Severity: Critical
l Alarm type: QoS alarm

Probable Cause
The CDR receiving buffer of the billing NE is full.

System Impact
CDRs may be lost.

Handling Suggestion
1. Check whether the link between the NE and the CU is normal.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Restore the link between the NE and CU. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether the CU is in working status.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Handle the CU problem. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.4.29 33560252 Type of Received CDR Is Not Identified

Alarm Information
l Alarm code: 33560252
l Alarm name: Type of received CDR is not identified
l Severity: Major
l Alarm type: QoS alarm

Probable Cause
The billing foreground receives CDRs of unknown types.

System Impact
Incorrect CDR types exist.

2-193

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Handling Suggestion
1. On the Real-time Current Alarm Monitoring tab of the Alarm Management window,
view the alarm details and record the incorrect CDR types.
2. Contact ZTE for help.

2.4.30 33560253 Length of Received CDR Is Not Correct

Alarm Information
l Alarm code: 33560253
l Alarm name: Length of received CDR is not correct
l Severity: Major
l Alarm type: QoS alarm

Probable Cause
The length of CDR is incorrect.

System Impact
It may cause CDR types wrong.

Handling Suggestion
1. On the Real-time Current Alarm Monitoring tab of the Fault Management window,
view the alarm details and record the incorrect CDR types, the length of the incorrect
CDR, and the length of the real CDR.
2. Contact ZTE for help.

2.4.31 33560254 CCF Is in Bypass Situation

Alarm Information
l Alarm code: 33560254
l Alarm name: CCF is in bypass situation.
l Severity: Critical
l Alarm type: Equipment alarm

Probable Cause
The CCF enters the BYPASS state.

System Impact
CDRs will be saved locally. After a long period, CDRs may be lost.

2-194

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Handling Suggestion
1. Check whether the configuration of CCF routing is correct.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Modify the configuration of CCF routing. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check the configuration of CCF BYPASS is correct.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Modify the configuration of CCF BYPASS. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.4.32 33560255 CCF Failure

Alarm Information
l Alarm code: 33560255
l Alarm name: CCF Failure
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
CCF Failure, No response for ACR.

System Impact
None

Handling Suggestion
1. Check whether the CCF is configured properly and its status is normal.
l Yes: Contact ZTE for help..
l No: Go to Step 2.
2. Modify the CCF configuration and restore its status to normal. Then check whether
the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.4.33 33575140 CIC Resource Is Insufficient

Alarm Information
l Alarm code: 33575140

2-195

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Alarm name: CIC resource is insufficient

l Severity: Changed
l Alarm type: Processing error alarm

Probable Cause
The CIC circuit resources are overused.

System Impact
Call loss occurs.

Handling Suggestion
1. Check whether many circuits are blocked.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Unblock the circuits. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
3. Add E1 resource, that is, increase the number of CICs in the trunk group. Then check
whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.4.34 33575153 Delete CIC Which Is Connected With MTL

Alarm Information
l Alarm code: 33575153
l Alarm name: Delete cic which is connected with MTL
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
The CIC bound with the MTL is deleted.

System Impact
If there is only one CIC bound with the MTL, the interception function cannot be used. If
there are multiple CICs bound with the MTL, the interception function is not impacted.

Handling Suggestion
Run the ADD CIC command to configure the CIC in the trunk group associated with the
SORMUP signaling type or to delete the undesired MTLs. Then check whether the alarm
disappears.

2-196

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l Yes: End alarm handling.

l No: Contact ZTE for help.

2.4.35 33575171 Inter-Switch TDM Circuit on MGW Controlled by

MSC Server Link Broken
Alarm Information
l Alarm code: 33575171
l Alarm name: Inter-Switch TDM Circuit on MGW controlled by MSC Server link broken
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
The TDM connection from the MGW to another office is disconnected.

System Impact
If only some TDM circuits to this office are disconnected, the load on other circuits to this
office increases. Too high load may cause call loss.
If all the TDM circuits to this office are disconnected, MSCS cannot obtain the outgoing
circuits. If there is an alternate route, the circuit load of this alternate route increases.
Too high load may cause call loss. If there is no alternate route, all the service will be
interrupted.

Handling Suggestion
1. On the Real-time Current Alarm Monitoring tab of the Fault Management window,
double-click the alarm information. Record the office ID, trunk group ID and PCM ID
of the MGW where the alarm is generated.
2. Check whether any alarm related to trunk circuits exists.
l Yes: Handle the alarm by referring to the corresponding handling suggestions.
l No: Go to Step 3.
3. Follow the Step 4 to Step 6 to check whether the MSCS has the CIC circuit that
occupies the same timeslots as those occupied by the DTB link on the MGW.
4. In the Terminal window of the MGW, run the SHOW N7LNKDT command to query the
DTB access link. Type the trunk unit No. and sub-unit No. queried in Step 1. Check
whether the DTB link and the link-occupied timeslots are configured to this E1.
5. In the Terminal window of the MGW, run the SHOW MPCM command. Type the trunk
unit No. and the sub–unit No. Query the PCM No. of the E1 on the MGW.
6. In the Terminal window of the MSCS, run the SHOW CIC command. Type the node
No. of MGW and the PCM No. queried in Step 5 to query the CIC circuit configuration
of this E1 on the MSCS. Check whether the timeslots queried in Step 4 are configured
to the CIC circuit.
l Yes: Go to Step 7.

2-197

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l No: End alarm handing after the alarm disappears.

7. Follow the Steps 8 and 9 to delete the CIC circuit that occupies the same timeslots as
those occupied by the DTB link on the MGW from the MSCS.
8. In the Terminal window of the MSCS, run the BLO CIC command to block the CIC
circuit that has the repeated configuration with the DTB link on the MGW.
9. In the Terminal window of the MSCS, run the DEL CIC command to delete the CIC
circuit that is blocked in Step 8. When the CIC circuit is deleted, end alarm handing
after the alarm disappears.

2.4.36 33575172 TDM Circuit Between MGWs Controlled by MSC

Server Link Broken
Alarm Information
l Alarm code: 33575172
l Alarm name: TDM Circuit between MGWs controlled by MSC Server link broken
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
The TDM circuit between MGWs is disconnected.

System Impact
Applying for the TDM circuit between intra-office MGWs fails, which may affect the calls
between these two directly connected MGWs.

Handling Suggestion
1. On the Real-time Current Alarm Monitoring tab of the Fault Management window,
double-click the alarm information. Record the Node ID of the MGW, Node ID of the
MGW on the other port, trunk group ID and PCM ID.
2. On the Real-time Current Alarm Monitoring tab of the Fault Management window,
check whether any alarm related to trunk circuits exists.
l Yes: Handle the alarm by referring to the corresponding handling suggestions.
l No: Contact ZTE for help.

2.4.37 33575173 The Usage of DB Table Space Exceeds the Limit

Value
Alarm Information
l Alarm code: 33575173
l Alarm name: The usage of DB table space exceeds the limit value
l Severity: Minor

2-198

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l Alarm type: Processing error alarm

Probable Cause
The traffic is too heavy, or the set table capacity is too small.

System Impact
The CPU load of the system increases, and the service providing capability is severely
impacted.

Handling Suggestion
1. On the Real-time Current Alarm Monitoring tab of the Fault Management window,
double-click the alarm information to view the Details. Record the name of the table
with too high usage, and the module No. where this alarm appears in the Detail row.
l This alarm appears in one module, go to Step 2.
l This alarm appears in multiple modules, go to Step 4.
2. Check whether there are too many VLR users shared by this module.
l Yes: Go to Step 3.
l No: Contact ZTE for help.
3. Adjust the IMSI load sharing configuration. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

Note:
a. Run the SHOW IMSILOAD command to query the corresponding IMSI Hash
Value of each module.

b. Run the SET IMSILOAD command to configure the IMSI hash of the module with
too heavy load to other modules with lower load.

4. Check whether the load of the local office is too heavy.

l Yes: Decrease the traffic volume or increase the system capacity properly. Handle
the alarm by referring to the corresponding handling suggestions.
l No: Contact ZTE for help.

Related Alarm
2.4.44 33575463 MSCS Service Overload

2-199

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

2.4.38 33575174 MSRN in Common Module Usage Exceeds the

Pre-Defined Limit
Alarm Information
l Alarm code: 33575174
l Alarm name: MSRN in common module usage exceeds the pre-defined limit
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
The usage of the MSRN number resources in common modules is too high.

System Impact
The MSRN resources are exhausted, which affects the call completion ratio of the system.

Handling Suggestion
1. Run the SHOW MSRNINFO command to check whether the usage of the MSRN
resources is too high.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Run the SET MSCCAP command to expand the capacity of the MSRN table. It is
recommended that the added capacity of every time should not exceed 10% of the
original capacity. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

Caution!
After the capacity of the VLR system is modified, it is required to restart the MP to make
the modification take effect. Restarting the MP will interrupts the existing services, so
perform system backup before modifying the capacity of the VLR system. Contact the
ZTE technical support personnel for technical support, and modify the capacity when
the traffic is the lowest.

After the MP is restarted, do service tests and observation to ensure that the services
are restored to normal status.

2-200

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

2.4.39 33575175 MSRN Usage Exceeds the Pre-Defined Limit

Alarm Information
l Alarm code: 33575175
l Alarm name: MSRN usage exceeds the pre-defined limit
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
The usage of the MSRN resources of this VLR module is too high.

System Impact
The MSRN resources are exhausted, which affects the call completion ratio of the system.

Handling Suggestion
1. Run the SHOW MSRNINFO command to check whether the usage of the MSRN
resources is too high.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Run the SET MSCCAP command to expand the capacity of the MSRN table. It is
recommended that the added capacity of every time should not exceed 10% of the
original capacity. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

Caution!
After the capacity of the VLR system is modified, it is required to restart the MP to make
the modification take effect. Restarting the MP will interrupts the existing services, so
perform system backup before modifying the capacity of the VLR system. Contact the
ZTE technical support personnel for technical support, and modify the capacity when
the traffic is the lowest.
After the MP is restarted, do service tests and observation to ensure that the services
are restored to normal status.

2.4.40 33575176 HONUM Usage Exceeds the Pre-Defined Limit

Alarm Information
l Alarm code: 33575176
l Alarm name: HONUM usage exceeds the pre-defined limit

2-201

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
The usage of the handover number resources is too high.

System Impact
The handover number resources are exhausted, which affects the handover of subscribers
and the call completion ratio of the system.

Handling Suggestion
1. Run the SHOW MSRNINFO command to check whether the usage of the HON
resources is too high.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Run the SET MSCCAP command to expand the capacity of the HON table. It is
recommended that the added capacity of every time should not exceed 10% of the
original capacity. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

Caution!
After the capacity of the VLR system is modified, it is required to restart the MP to make
the modification take effect. Restarting the MP will interrupts the existing services, so
perform system backup before modifying the capacity of the VLR system. Contact the
ZTE technical support personnel for technical support, and modify the capacity when
the traffic is the lowest.
After the MP is restarted, do service tests and observation to ensure that the services
are restored to normal status.

2.4.41 33575177 CPU Load Too High in MGW

Alarm Information
l Alarm code: 33575177
l Alarm name: CPU load too high in MGW
l Severity: Minor
l Alarm type: QoS alarm

2-202

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Probable Cause
The CPU load is too high in the MGW.

System Impact
Some service requests are rejected.

Handling Suggestion
It is recommended to expand the processing capability of the MGW.

2.4.42 33575178 RTP Load Too High in MGW

Alarm Information
l Alarm code: 33575178
l Alarm name: RTP load too high in MGW
l Severity: Minor
l Alarm type: QoS alarm

Probable Cause
The RTP load is too high in the MGW.

System Impact
Some service requests are rejected.

Handling Suggestion
It is recommended to expand the user-plane processing capability of the MGW.

2.4.43 33575179 Table Related to ALS Is Full

Alarm Information
l Alarm code: 33575179
l Alarm name: Table related to ALS is full
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
The capacity of the ALS table is set too small during the VLR system capacity configuration.

System Impact
New ALS subscription information fails to be inserted.

2-203

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Handling Suggestion
1. Run the SHOW MSCCAP command to query the current capacity of the ALS table.
2. Run the SHOW DATAALMTHD command to query the alarm threshold of the table
capacity usage.
3. Run the SET MSCCAP command to add the capacity of the ALS database according
to the query results in Steps 1 and 2.
4. Transfer all tables to the foreground, and reset the OMP module after saving data. The
table capacity is re-created according to the configuration requirements. Then check
whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.4.44 33575463 MSCS Service Overload

Alarm Information
l Alarm code: 33575463
l Alarm name: MSCS Service Overload
l Severity: Minor
l Alarm type: QoS alarm

Probable Cause
The traffic is heavy. The service access requests per second exceed the configured
threshold. Note that too-low acceptance or too-high service weighting may cause the
actual CPU usage relatively low whether the alarm of service overload is generated.

System Impact
The MSCS will reject accessing some new services due to overload.

Handling Suggestion
1. Check whether the load of each MP CPU is high.
l The load of all the MP CPUs is high: The system load is really heavy. It is required
to add more MP modules.
l Only one CPU has high load: The service load is not balanced. It is required to
share the load again.
l The CPU usage is not high, go to Step 2.

2-204

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Note:
In the navigation tree of the Performance Management window, click the Global
Measurement > Resource Load Measurement node to check the load of each MP
CPU.

2. Check whether the traffic of the discarded service exceeds its limit.
l Yes: Go to Step 3.
l No: Make no intervention. End the alarm handling after the alarm disappears.

Note:
l In the navigation tree of the Performance Management window, click the Special
Operation > Load Control > MSCS Load Control Measurement node to check
which service is discarded, and its corresponding traffic.
l Run the SHOW MSCSRVLMT command to check whether the traffic of the
discarded service exceeds its limit.

3. Run the SET MSCSRVLMT command to modify the configuration of service capability
limit. Then check whether the alarm disappears.
The rules for modifying the service capability are as follows. Take short message for
example.
a. Modify single service control first. Modify the times of short messages per
second according to their traffic to make the threshold larger than the current
short message traffic. The short message traffic is less than the times of short
message per second after modification.
l If the alarm still exists after one minute later, go to Step b.
l End alarm handling after the alarm disappears.

b. Modify the threshold of All Traffic Per Second. Increase the threshold of total
traffic per second.

l End alarm handing after the alarm disappears.

l If the alarm still exists, Contact ZTE for help.

2.4.45 33575466 CMP Overload

Alarm Information
l Alarm code: 33575466
l Alarm name: CMP overload
l Severity: Changed

2-205

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Alarm type: QoS alarm

Probable Cause
l The service of MSCS is overloaded.
l A single CMP is overloaded.

System Impact
Service requests are rejected.

Handling Suggestion
1. On the Real-time Current Alarm Monitoring tab of the Fault Management window,
double-click the alarm information. Record the CPU usage shown in the Details row.
2. Check the CPU usage of other CMPs.
l The CPU usages of some CMP modules are low: There is a problem with the
load sharing, go to Step 3.
l The CPU usages of other modules are also high, go to Step 4.

Note:
In the navigation tree of the Performance Management window, click the Special
Operation > Load Control > MSCS Load Control Measurement node to check the
CPU usage of other CMPs.

3. Modify the service load sharing. Wait until the CPU usage of the CMP module is
reduced. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

Note:
l When SMP and CMP are integrated, move the associations/signaling links
configured to this module or some terrestrial circuits to the modules with lower
CPU usage.
l When CMP is independent, move some terrestrial circuits to the modules with
lower CPU usage.

4. Check whether the service traffic is heavy.

l Yes: Go to Step 5.
l No: Contact ZTE for help.

2-206

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Note:
In the navigation tree of the Performance Management window, click the Global
Traffic > Base Traffic Measurement node to check the service traffic.

5. Add more CMP modules. After more CMP modules are added, the CPU usage of
each CMP module decreases. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.4.46 33576632 The Heartbeat of Dualhome Is Down

Alarm Information
l Alarm code: 33576632
l Alarm name: The heartbeat of dualhome is down
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
The partner MSCS or the heartbeat link is faulty.

System Impact
The dual-homing changeover may be triggered in the automatic mode.

Handling Suggestion
1. On the Real-time Current Alarm Monitoring tab of the Fault Management window,
double-click the alarm information. Record the ID of the dual-homing work domain
shown in the Details row.
2. Run the SHOW WORKDOMAIN command to query the adjacent office ID of the
partner MSCS.
3. Run the SHOW SCTPSTAT command to check whether the status of the association
to the dual-homing partner is normal.
l Yes: Go to Step 4.
l No: Handle the alarm by referring to the corresponding handling suggestions, and
restore the unavailable association.
4. Check whether the opposite message is received.
l Yes: The partner office works normally. End alarm handling after the alarm
disappears.
l No: There is a problem with the partner office. Contact its maintenance personnel
to solve the problem.

2-207

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Note:
In the navigation tree of the Trace Management window, click the Signaling Trace
> Sigtran Signaling Trace > SCTP node to trace the heartbeat association to the
dual-homing partner office. Check whether the opposite message is received, thus to
judge whether the partner office sends a heartbeat message on the heartbeat link.

Related Alarm
2.3.23 8402690 Association Broken

2.4.47 33576634 Exceptions Occurred When Two MSCS of

Dualhome Are Master
Alarm Information
l Alarm code: 33576634
l Alarm name: Exceptions occurred when two MSCS of dualhome are master
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
Both the active MSCS and the standby one are in active status.

System Impact
Once this alarm appears (even if it has been recovered), it needs great attention. Both the
active MSCS and the standby one are in active status, which causes service flow exception
or service failure.

Handling Suggestion
1. On the Real-time Current Alarm Monitoring tab of the Fault Management window,
double-click the alarm information. Record the ID of the dual-homing work domain
shown in the Details row.
2. Run the SHOW WORKDOMAIN command to query the adjacent office ID of the
partner MSCS and the work role of the local office.
3. In the Fault Management window, click the Real-time Notification Monitoring tab
to check whether there is any related notification (notification code: 33610274).
l Yes: Handle the alarm by referring to the corresponding handling suggestions.
l No: Contact ZTE for help.

2-208

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Related Alarm
3.3.102 33610274 Backup MSCS Switched to Master

2.4.48 33576635 Exceptions Occurred When Two MSCS of

Dualhome Are Slave
Alarm Information
l Alarm code: 33576635
l Alarm name: Exceptions occurred when two MSCS of dualhome are slave
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
Both the active MSCS and the standby one are in standby status.

System Impact
Once this alarm appears (even if it has been recovered), it needs great attention. Both the
active MSCS and the standby one are in standby status, which causes all services failing.

Handling Suggestion
1. On the Real-time Current Alarm Monitoring tab of the Fault Management window,
double-click the alarm information. Record the ID of the dual-homing work domain
shown in the Details row.
2. Run the SHOW WORKDOMAIN command to query the adjacent office ID of the
partner MSCS and the work role of the local office.
3. In the Fault Management window, click the Real-time Notification Monitoring tab
to check whether there is any related notification (notification code: 33610275).
l Yes: Handle the alarm by referring to the corresponding handling suggestions.
l No: Contact ZTE for help.

Related Alarm
3.3.103 33610275 Master MSCS Switched to Backup

2.4.49 33576636 The Usage of Data Area Exceeds the Pre-Defined

Limit
Alarm Information
l Alarm code: 33576636
l Alarm name: The usage of data area exceeds the pre-defined limit
l Severity: Minor

2-209

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Alarm type: Processing error alarm

Probable Cause
l The traffic is too heavy.
l A data area is exceptionally suspended.

System Impact
The success ratios of the services using the resources of this area are impacted.

Handling Suggestion
Contact ZTE for help.

2.4.50 33576664 The Alarm of Paging Congestion

Alarm Information
l Alarm code: 33576664
l Alarm name: The alarm of paging congestion
l Severity: Minor
l Alarm type: QoS alarm

Probable Cause
The number of paging attempts exceeds the wireless resource capability in this location
area, which causes low paging success ratio.

System Impact
The paging success ratio decreases, and the call loss ratio increases.

Handling Suggestion
Check whether the times of attempted paging is too high in the Performance Management
window.
l Yes: Contact the maintenance engineer at the wireless side for handling.
l No: Contact ZTE for help.

2.4.51 33576665 Links of Office Is in Congest

Alarm Information
l Alarm code: 33576665
l Alarm name: Links of office is in congest
l Severity: Changed
l Alarm type: QoS alarm

2-210

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Probable Cause
The traffic of the adjacent office is too heavy and exceeds the capability of the link.

System Impact
The link congestion may result in transmission delay, but has no effect on the service in
general. However, serious congestion may result in packet loss, call loss, or reduced
service access success rate.

Handling Suggestion
1. On the Real-time Current Alarm Monitoring tab of the Fault Management window,
double-click the alarm information. Record the office number shown in the Details
row.
2. Add signaling links to the office. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.4.52 33576669 Abnormal Heartbeat Detected Between MSC Pool

User Data Synchronization Peers
Alarm Information
l Alarm code: 33576669
l Alarm name: Abnormal heartbeat detected between MSC pool user data
synchronization Peers
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
l The FlexSyn association between the partner offices for synchronizing subscriber data
in the MSC Pool is interrupted.
l The subscriber data synchronization office in the MSC Pool is faulty.

System Impact
The standby subscriber data on the standby MSC Server may be inconsistent with the
subscriber data on the active MSC Server. In this case, when the active MSC Server is
faulty, call loss occurs when the standby MSC Server processes the called service of the
subscriber of the previously active MSC Server.

Handling Suggestion
1. On the Real-time Current Alarm Monitoring tab of the Fault Management window,
double-click the alarm information. Record the partner office ID in the Details row.

2-211

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

2. Run the SHOW SCTPSTAT command to check whether the status of the association
to the dual-homing partner is "established".
l Yes: Go to Step 3.
l No: Handle the alarm by referring to the corresponding handling suggestions, and
recover the unavailable SCTP.
3. Check whether one partner office receives any messages from the remote end.
l Yes: The partner offices operate properly. End alarm handling after the alarm
disappears.
l No: This alarm is caused by the partner offices. Contact the partner office
maintenance personnel for handling.

Note:
In the navigation tree of the Trace Management, click the Signaling Trace > Sigtran
Signaling Trace > SCTP node to trace the FlexSyn association between the partner
offices. Check whether one partner office receives any messages from the remote
end, thereby judge whether any message is sent to the partner offices through the
FlexSyn association.

Related Alarm
2.3.23 8402690 Association Broken

2.4.53 33576670 The Number of MGW Registered Is Inconsistent

With Configure
Alarm Information
l Alarm code: 33576670
l Alarm name: The number of MGW registered is inconsistent with configure
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
The number of the actually registered MGWs in the domain is less or greater than the
configured number put into use.

System Impact
If the number of the actually registered MGWs is less than the number of the MGWs put
into use, the MSCS will not request resources from the unregistered MGW, resulting in
failure of the services configured to this MGW. If the number of the actually registered
MGWs is greater than the number of MGWs put into use, the number of the MGWs is not

2-212

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

configured correctly. This may result in the incorrect judgment made during the automatic
dual-homing changeover.

Handling Suggestion
1. On the Real-time Current Alarm Monitoring tab of the Fault Management window,
double-click the alarm information. Record the working domain ID, configured MGW
number, and registered MGW number shown in the Details row.
2. Run the SHOW ADJOFC command to query the number of MGW offices whose work
domain ID are consistent with that queried in Step 1. That is the actual number of the
MGWs in the work domain.
l The actual number of MGWs is inconsistent with the configured one, go to Step 3.
l The actual number of MGWs is inconsistent with the registered one, go to Step 4.
3. Run the SET WORKDOMAIN to modify the number of MGWs configured in the work
domain. Make this number consistent with the actual number of MGWs. Then check
whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
4. Check whether there exists any related alarm (alarm code: 25167105 and 25167106).
l Yes: Handle the alarm by referring to the corresponding handling suggestions.
l No: Contact ZTE for help.

Related Alarms
l 2.4.1 25167105 Alarm of Server Disconnected With MGW
l 2.4.2 25167106 MGW Is Out of Service

2.4.54 33576671 MSCS Act as Slave When Power On

Alarm Information
l Alarm code: 33576671
l Alarm name: MSCS act as slave when power on
l Severity: Critical
l Alarm type: Processing error alarm

Probable Cause
In the dual-homing networking mode, the local MSCS acts as the standby server after
being powered on.

System Impact
If both MSCSs are in standby status, all services in the domain will be affected.

2-213

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Handling Suggestion
1. On the Real-time Current Alarm Monitoring tab of the Fault Management window,
double-click the alarm information. Record the working domain ID shown in the Details
row.
2. Run the SHOW WORKDOMAIN command to query the working role of the local office.
3. Run the SHOW DHSTATE command to view the active/standby relation between the
local office and partner office.
l Active-Standby: Clear the alarm manually. End alarm handling.
l Standby-Standby, go to Step 4.
4. According to the working role found in Step 2, change one standby MSCS into active
MSCS. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.4.55 33576672 Dualhome Work Role Is Conflicting

Alarm Information
l Alarm code: 33576672
l Alarm name: Dualhome work role is conflicting
l Severity: Critical
l Alarm type: Equipment alarm

Probable Cause
In the dual-homing networking mode, both the active and standby servers are configured
to pre-defined active servers or pre-defined standby servers.

System Impact
The active and standby servers are powered on exceptionally, resulting in the system
failing to work normally.

Handling Suggestion
1. On the Real-time Current Alarm Monitoring tab of the Fault Management window,
double-click the alarm information. Record the domain ID, local work role, and remote
work role shown in the Details row.
2. Run the SET WORKDOMAIN command to modify the work domain of either the local
office or the partner office to MASTER (Main Domain), and the rest to SLAVE (Standby
Domain). After modification, synchronize the data with the foreground. Then check
whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-214

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

2.4.56 33576673 The Number of MGW in Service Is Conflict in

Domain
Alarm Information
l Alarm code: 33576673
l Alarm name: The number of mgw in service is conflict in domain
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
In the dual-homing domain, the number of the MGWs put to use configured on the active
server is inconsistent with that configured on the standby server.

System Impact
When the decision on active and standby dual-homing servers is abnormal, both servers
are active or standby at the same time, which may cause abnormal services.

Handling Suggestion
1. On the Real-time Current Alarm Monitoring tab of the Fault Management window,
double-click the alarm information. Record the Domain ID, Local MGW Number in
service, and Peer MGW Number in service shown in the Details row.
2. Run the SHOW ADJOFC command to query the number of MGW offices whose work
domain ID are consistent with that queried in Step 1. That is the actual number of the
MGWs in the work domain.
l The number of local-office-configured MGWs in the work domain is incorrect, go
to Step 3.
l The number of partner-office-configured MGWs in the working domain is incorrect,
go to Step 4.
3. In the Terminal window of the local office, run the SET WORKDOMAIN command
to modify the "MGW Amount in Domain" parameter to make it consistent with that
of the dual-homing partner office. After modification, synchronize the data with the
foreground. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
4. In the Terminal window of the dual-homing partner office, run the SET WORKD
OMAIN command to modify the "MGW Amount in Domain" parameter to make it
consistent with that of the local office. After modification, synchronize the data with
the foreground. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-215

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

2.4.57 33576675 Congestion Detected Between MSC Pool User

Data Synchronization Peers
Alarm Information
l Alarm code: 33576675
l Alarm name: Congestion detected between MSC pool user data synchronization
Peers
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
Congestion occurs during the synchronization of the user data in the MSC Pool.

System Impact
The backup user data on the standby MSCS may be inconsistent with the user data on
the active MSCS. When the active MSCS fails and the standby MSCS takes over calls of
the users on the previously active MSCS, call loss may occur.

Handling Suggestion
1. Check whether the status of the standby MSC Server is normal.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Restore the the status of the standby MSCS to normal. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether the status of the association used for user data synchronization is
normal.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Restore the status of the association used for user data synchronization to normal.
Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.4.58 33576900 More Than 90% DEP Dialogs Is Used

Alarm Information
l Alarm code: 33576900
l Alarm name: More than 90% DEP Dialogs is used
l Severity: Major
l Alarm type: Communication alarm

2-216

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Probable Cause
The service process creates too many sessions, or the protocol stack dialog expires.

System Impact
The services with lower priority fail to seize DEP session resources, so they are processed
slowly or fail to be processed.

Note:
The Diameter Execute Point (DEP) logic module completes the service-related
functions defined in the Diameter protocol, including transaction management, session
management, and Relay/Redirect

Handling Suggestion
The protocol stack session is automatically released in the following two cases, so it needs
no intervention.
l The service process receives an answer message.
l The protocol stack sets the timer for test. If the timer expires, the protocol stack
session is automatically released.

2.4.59 33576901 DEP Process Register Failed

Alarm Information
l Alarm code: 33576901
l Alarm name: DEP process register failed
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
l The L-REG initialization fails.
l The L-REG fails to find the DEP ID.

2-217

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Note:
l The L-REG is a logic module on the CMP/SMP/OCG logic module, which is used
to receive the Diameter protocol stack data synchronized from the G-REG. Each
CMP/SMP/OCG logic module in the MGCF is fixedly configured with one L-REG.
The L-REG ID is the No. of the corresponding CMP/SMP/OCG module.
l The DEP logic module completes the service-related functions defined in the
Diameter protocol, including transaction management, session management, and
Relay/Redirect. Each OCG module in the MGCF is fixedly configured with one DEP
logic module. The DepID is the No. of the corresponding OCG module.

System Impact
The Diameter protocol stack fails to work temporarily, and the service process fails to send
request messages temporarily.

Handling Suggestion
1. In the Fault Management window LMT, choose the Real-time Current Alarm
Monitoring tab. Double-click the alarm information to pop up the Details dialog box.
Record the module No. in the Details row.
2. On the debugging PC, select Start > Run, and the Run dialog box pops up. Type
telnet IP address of the OMP module, and click OK. The telnet window
pops up. Type the user name and password (zte/zte in general) as prompted.
Then type command showGlobalData to check whether filed btCommStatus in
g_tGlbLRegSet.tLRegData is 0 (0 means this L-REG does not work normally).
l Yes: record the L-REG ID, and go to Step 3.
l No: Go to Step 5.
3. On the MGCF foreground, check whether the GPBB1 board is normal, on which, the
OCG module where this L-REG is located is configured.
l Yes: wait for a while. If the alarm disappears, end alarm handling.
l No: go to Step 4.
4. Extract and insert the board. If the board does not work normally after being extracted
and inserted, it is required to replace it. Check whether the L-REG works normally
after the board works normally and whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 5.
5. In the telnet window, type command showGlobalData to check whether the DepID in
g_tGlbDepSet.DepData is consistent with the OCG module No., and to check whether
the DEP is configured.
l If the DEP is not configured, try synchronizing data to the foreground again.
l If the DEP is still not configured after data are synchronized to the foreground,
delete the OCG module and add it again. After adding the OCG module,

2-218

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

synchronize data to the foreground, and the system automatically creates the
DEP.

2.4.60 33576903 DEP Dialog Resource Is Exhausted

Alarm Information
l Alarm code: 33576903
l Alarm name: DEP Dialog resource is exhausted
l Severity: Critical
l Alarm type: Communication alarm

Probable Cause
l The service process creates too many sessions.
l The service process uses sessions for a long time, and does not release them.
l The protocol stack dialog expires.

System Impact
The Diameter protocol stack fails to work temporarily, and the service process fails to create
new sessions.

Note:
The Diameter Execute Point (DEP) logic module completes the service-related
functions defined in the Diameter protocol, including transaction management, session
management, and Relay/Redirect.

Handling Suggestion
The protocol stack session is automatically released in the following two cases, so it needs
no intervention.
l The service process receives an answer message.
l The protocol stack sets the timer for test. If the timer expires, the protocol stack
session is automatically released.

2.4.61 33576904 DEP Transaction Resource Is Exhausted

Alarm Information
l Alarm code: 33576904
l Alarm name: DEP transaction resource is exhausted
l Severity: Minor

2-219

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Alarm type: Communication alarm

Probable Cause
The DEP needs to process too many services.

System Impact
The Diameter protocol stack fails to work temporarily, and the service process fails to send
request messages temporarily.

Note:
The DEP logic module completes the service-related functions defined in the Diameter
protocol, including transaction management, session management, and Relay/Redirect.

Handling Suggestion
The protocol stack sets the timer for test. If the timer expires, the protocol stack session
is automatically released, and no manual intervention is required.

2.4.62 33576905 DAP Get Config Data of Link Fail

Alarm Information
l Alarm code: 33576905
l Alarm name: DAP get config data of link fail
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
L-REG initialization fails.

System Impact
The Diameter link is broken, so the service messages based on the Diameter protocol
stack fail to be sent/received.

Handling Suggestion
1. On the Real-time Current Alarm Monitoring tab of the Fault Management window,
double-click the alarm information. Record the Diameter link No. in the Details row.
2. Run the SHOW DIAMLNK command to query the association No. bearing the
Diameter link according to the Diameter link No.

2-220

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

3. Run the SHOW SCTP command to query the SMP module No. where this SCTP is
located according to the SCTP connection No. (that is the association No. get in Step
2).
4. In the telnet window, run the zte command to view the process ID of DIM_LREG of
the LREG module.

Note:
On the debugging PC that can connect the foreground module, select Start > Run.
In the pop-up Run dialog box, set IP address of telnet SMP module, and click OK.
In the popup telnet window, enter the user name and password (generally, both are
"zte") according to the prompts.

5. In the telnet window, run the OSS_GetProcState DIM_LREG process ID command to

view the status of the LREG module process.
l The status value is 1: It indicates that the process is in working state. No handling
is needed.
l The status value is 0: It indicates that the process is not in working state. Go to
Step 6.
6. Restart the SMP module. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.4.63 33576906 DAP Process Register Failed

Alarm Information
l Alarm code: 33576906
l Alarm name: DAP process register failed
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
l The L-REG initialization fails.
l The L-REG fails to find the DAP ID.

System Impact
The Diameter link is broken, so the service messages based on the Diameter protocol
stack fail to be sent/received.

2-221

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Note:
l The L-REG is a logic module on the CMP/SMP/OCG logic module, which is used
to receive the Diameter protocol stack data synchronized from the G-REG. Each
CMP/SMP/OCG logic module in the MGCF is fixedly configured with one L-REG.
The L-REG ID is the No. of the corresponding CMP/SMP/OCG module.
l The Diameter Access Point (DAP) logic module completes the access control and
bearer management functions of the adjacent point in the Diameter network. Each
SMP logic module in the MGCF is fixedly configured with one DAP logic module. The
DapID is the No. of the corresponding SMP module.

Handling Suggestion
1. In the Fault Management window of the LMT window, choose the Realtime Current
Alarm Monitoring tab. Double-click the alarm information to pop up the Details dialog
box. Record the module No. in the Details row.
2. On the debugging PC, select Start > Run, and the Run dialog box pops up. Type
telnet IP address of the OMP module, and click OK. The telnet window
pops up. Type the user name and password (zte/zte in general) as prompted.
Then type command showGlobalData to check whether filed btCommStatus in
g_tGlbLRegSet.tLRegData is 0 (0 means this L-REG does not work normally).
l Yes: record the L-REG ID, and go to Step 3.
l No: Go to Step 5.
3. On the MGCF foreground, check whether the GPBB1 board is normal, on which, the
OCG module where this L-REG is located is configured.
l Yes: wait for a while. If the alarm disappears, end alarm handling.
l No: go to Step 4.
4. Extract and insert the board. If the board does not work normally after being extracted
and inserted, it is required to replace it. Check whether the L-REG works normally
after the board works normally and whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 5.
5. In the telnet window, type command showGlobalData to check whether the DapID in
g_tGlbDepSet.DepData is consistent with the SMP module No., and to check whether
the DAP is configured.
l If the DAP is not configured, try synchronizing data to the foreground again.
l If the DAP is still not configured after data are synchronized to the foreground,
delete the SMP module and add it again. After adding the SMP module,
synchronize data to the foreground, and the system automatically creates the
DAP.

2-222

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

2.4.64 33576907 Diameter Link Broken

Alarm Information
l Alarm code: 33576907
l Alarm name: Diameter link broken
l Severity: Critical
l Alarm type: Communication alarm

Probable Cause
l Network communication is interrupted.
l The configuration of connecting data is incorrect, including host name, address,
mismatched capabilities, and other items.

System Impact
The sending and receiving of service messages based on Diameter protocol stack will fail.

Handling Suggestion
1. On the Real-time Current Alarm Monitoring tab of the Fault Management window,
double-click the alarm information. Record the information of Diameter link shown in
the Details row, including Connection ID, Local Address, and Dest Address.
2. Check whether there exists any related alarm (alarm code: 8402690).
l Yes: Go to Step 3.
l No: Go to Step 4.
3. Check whether it is the association between the MGCF and CCF server, according to
the Local Address and Dest Address queried in Step 1.
l Yes: Handle the alarm by referring to the corresponding handling suggestions.
l No: Contact ZTE for help.
4. Run the UNBLOCK DIALINK command to unblock the link queried in Step 1. Then
check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 5.
5. Run the SHOW DIAMLNK command to check whether the configuration of the
Diameter link is correct. For example, check whether the host and domain names are
consistent with those of the opposite end office, whether the quoted number is that of
the association between the local office and the CCF.
l Yes: End alarm handling after the alarm disappears.
l No: Go to Step 6.
6. Run the SET DIAMLNK command to modify the configuration of the Diameter link.
Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-223

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Related Alarm
2.3.23 8402690 Association Broken

2.4.65 33576909 GREG Get Configuration Data Fail

Alarm Information
l Alarm code: 33576909
l Alarm name: GREG get configuration data fail
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
Obtaining data from the database fails.

System Impact
l The GREG power-on fails.
l The DAP link setup of the Diameter protocol stack fails.
l The off-line billing service flow is abnormal.
l Sending and receiving Diameter protocol messages fails.

Handling Suggestion
1. Check the configuration of Diameter protocol stack. If it is incorrect, modify it with
relevant commands.
a. In the Terminal window of the LMT, run the SHOW DIAM command to query the
Diameter common parameters. Check the TC timer and the local operator ID.
b. In the Terminal window of the LMT, run the SHOW DIAMLNK command to query
the Diameter link data. Check whether the host and domain names of the local
end are consistent with those in the SIP configuration, whether the opposite-end
office’s host and domain names configured on the local office are consistent with
the local host and domain names configured on the opposite-end office, and
whether the protocol type is SCTP.
c. In the Terminal window of the LMT, run the SHOW DIAMRT command to query
the static route data of Diameter. Check the destination URI, host and domain
names of the local end.
2. On the debugging PC, select Start > Run. On the pop-up Run dialog box, type
telnet IP address of OMP module in the Open drop-down combination box.
Click OK. On the pop-up Telnet dialog box, type the user name and password
(generally, they are zte/zte). Type the showGlobalData command to check whether
the following configuration data are correct.
a. GREG (g_tGlbProductInfo): Check whether the TC timer and VendorID are
consistent with those queried with the SHOW DIAM command.

2-224

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

b. Service (g_tGlbSvcSet): Check whether the service host name is configured

(tIsPrensentHost=1).
c. LREG (g_tGlbLRegSet): Check whether each SMP/OCG/CMP with SIP attribute
is configured with the corresponding LREG, and whether LREG works normally
(btCommStatus=1).
d. DEP (g_tGlbDepSet): Check whether each OCG module is configured with the
corresponding DEP, and whether the DEP works normally (ConStatus=1).
e. DAP (g_tGlbDapSet): Check whether each SMP module is configured with the
corresponding DAP, and whether the DAP works normally (ConStatus=1).
f. Link configuration (g_tGlbConnSet): Check the configuration of the Diameter
links to see they are consistent with those queried with the SHOW DIAMLNK
command.

2.4.66 33576912 LREG Failed to Access Basic Data

Alarm Information
l Alarm code: 33576912
l Alarm name: LREG failed to access basic data
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
LREG fails to obtain data from the database.

System Impact
l The LREG power-on fails.
l The DAP link setup of the Diameter protocol stack fails.
l The off-line billing service flow is abnormal.
l Sending and receiving Diameter protocol messages fails.

Handling Suggestion
1. Check the configuration of Diameter protocol stack. If it is incorrect, modify it with
relevant commands.
a. In the Terminal window of the LMT, run the SHOW DIAM command to query the
Diameter common parameters. Check the TC timer and the local operator ID.
b. In the Terminal window of the LMT, run the SHOW DIAMLNK command to query
the Diameter link data. Check whether the host and domain names of the local
end are consistent with those in the SIP configuration, whether the opposite-end
office’s host and domain names configured on the local office are consistent with
the local host and domain names configured on the opposite-end office, and
whether the protocol type is SCTP.

2-225

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

c. In the Terminal window of the LMT, run the SHOW DIAMRT command to query
the static route data of Diameter. Check the destination URI, host and domain
names of the local end.
2. On the debugging PC, select Start > Run. On the pop-up Run dialog box, type
telnet IP address of OMP module in the Open drop-down combination box.
Click OK. On the pop-up Telnet dialog box, type the username and password
(generally, they are zte/zte). Type the showGlobalData command to check whether
the following configuration data are correct.
a. GREG (g_tGlbProductInfo): Check whether the TC timer and VendorID are
consistent with those queried with the SHOW DIAM command.
b. Service (g_tGlbSvcSet): Check whether the service host name is configured
(tIsPrensentHost=1).
c. LREG (g_tGlbLRegSet): Check whether each SMP/OCG/CMP with SIP attribute
is configured with the corresponding LREG, and whether LREG works normally
(btCommStatus=1).
d. DEP (g_tGlbDepSet): Check whether each OCG module is configured with the
corresponding DEP, and whether the DEP works normally (ConStatus=1).
e. DAP (g_tGlbDapSet): Check whether each SMP module is configured with the
corresponding DAP, and whether the DAP works normally (ConStatus=1).
f. Link configuration (g_tGlbConnSet): Check the configuration of the Diameter
links to see they are consistent with those queried with the SHOW DIAMLNK
command.
3. On the debugging PC, select Start > Run. On the pop-up Run dialog box, type
telnet IP address of OMP module in the Open drop-down combination box.
Click OK. On the pop-up Telnet dialog box, type the username and password
(generally, they are zte/zte). Type the zte command to see the DIM_GREG process
ID. And then on the Telnet dialog box, execute the OSS_GetProcState DIM_GRE
process ID command. If the result is shown as 1, the GREG process works normally.
If the result is shown as 0. the GREG process does not work. At this time, OMP
module should be restarted.

2.4.67 33576913 Initiation of UB Pool Failed

Alarm Information
l Alarm code: 33576913
l Alarm name: Initiation UB pool failed
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
The UB resource space is insufficient.

2-226

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

System Impact
The LREG fails to be powered on, so the service messages based on the Diameter protocol
stack fail to be sent/received.

Handling Suggestion
On the debugging PC, select Start > Run, and the Run dialog box pops up. Type telnet
IP address of the OMP module, and click OK. The telnet window pops up. Type
the user name and password (zte/zte in general) as prompted. The type command mem
Show to check whether the memory resource is used up. If it is used up, contact ZTE to
add memory.

2.4.68 33577432 SIP Config Error

Alarm Message
l Alarm code: 33577432
l Alarm name: SIP config error
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
SIP configuration is incorrect.

System Impact
The alarming SIP process cannot be powered on.

Handling Suggestion
Check the usage condition of the memory of the module to ensure that the available space
of the memory is greater than 104K. If the available space of the memory is insufficient,
add memory before restarting the module. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.4.69 33577433 SIP Insufficient Memory

Alarm Message
l Alarm code: 33577433
l Alarm name: SIP insufficient memory
l Severity: Minor
l Alarm type: Processing error alarm

2-227

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Probable Cause
SIP memory resources are insufficient.

System Impact
The alarming SIP process cannot be powered on.

Handling Suggestion
1. Contact the ZTE technical support personnel to add memory for the OMP module.
If the condition for adding memory is not satisfied temporarily, perform the following
steps to reduce the capacity of the SIP protocol data area.
2. In the Terminal window of the LMT, run the SHOW MSCCAP command to check the
capacity configuration of the SIP protocol data area.
3. In the Terminal window of the LMT, run the SET MSCCAP command to decrease
10% of the capacity (SIPSOCKET capacity, SIPCMTU capacity, SIPTR capacity,
SIPTUMSG capacity, SIPCMSDP capacity, and SIPCMRFCHG capacity).
4. Transfer all tables to the foreground, and reset the OMP module after data saving
is completed. The table capacity is re-created according to the configuration
requirements. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.4.70 33577434 SIP Socket Init Fail

Alarm Message
l Alarm code: 33577434
l Alarm name: SIP socket Init fail
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
SIP socket initialization fails.

System Impact
The SIP transmission layer cannot send or receive the SIP message, which makes all
SIP-related services unavailable.

Handling Suggestion
In the Terminal window of the LMT, run the SHOW UDPBR command to check whether
the IP address, port number, and the module number configured in the UDP bearer
configuration of the local end are consistent with those as planned.
l Yes: Contact ZTE for help.

2-228

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l No: execute command SET UDPBR to modify the UDP bearer configuration.

2.4.71 33577435 SIP Link Broken

Alarm Message
l Alarm code: 33577435
l Alarm name: SIP link broken
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
The SIP link is broken.

System Impact
The SIP message cannot be sent or received on the link reporting alarms, and the
SIP-related services on this link cannot work normally.

Handling Suggestion
1. In the Fault Management window of the LMT, select the Real-time Current Alarm
Monitoring tab, check whether the SIP Socket status alarm appears.
l Yes: refer to “33577434 SIP socket init fail” for handling.
l No: Go to Step 2.
2. In the Terminal window of the LMT, run the SHOW SIPLNKSTAT command to query
whether the SIP link is in service.
l Yes: End alarm handling.
l No: Go to Step 3.
3. In the Terminal window of the LMT, run the UBL SIPLNK command to unblock this
SIP signaling link. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 4.
4. In the Terminal window of the LMT, run the SHOW SIPLNK command to query
whether the SIP signaling link ID, connection ID, and interval of sending heartbeat
messages are correct.
l Yes: Contact ZTE for help.
l No: Go to Step 5.
5. In the Terminal window of the LMT, run the SET SIPLNK command to modify the SIP
signaling link configuration. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-229

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

2.4.72 33577532 License Alert

Alarm Information
l Alarm code: 33577532
l Alarm name: License alert
l Severity: Changed
l Alarm type: QoS alarm

Probable Cause
The actual capacity is about to exceed the License capacity.

System Impact
The services exceeding the license capacity fail.

Handling Suggestion
The License capacity alarm is generated, indicating that the License capacity bought at
that time is inadequate. Capacity expansion is required. Based on the details of the alarm,
determine which service exceeds the license, and then apply for a new license from ZTE.

2.4.73 33610283 Media IP Address of BSC Can't Be Connected

Alarm Information
l Alarm code: 33610283
l Alarm name: Media IP Address of BSC can't be connected
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
The IP connection of the media plane to the BSC was faulty.

System Impact
The IP bearer on the A interface is unavailable.

Handling Suggestion
1. Check whether the connection of the media plane to the BSC is normal.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore the connection of the media plane to the BSC. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-230

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

2.5 1000000000~9999999999
2.5.1 2013659137 License File Is Inconsistent With Database
Backup
Alarm Information
l Alarm code: 2013659137
l Alarm name: License file is inconsistent with database backup
l Severity: Critical
l Alarm type: Processing error alarm

Probable Cause
l The license is not reloaded after configuration data recovery.
l The license file is replaced, but the new license is not loaded. Run the LOAD LICEN
SE command to load the license.

System Impact
The license control parameter of the current service is inconsistent with that in the license
file. The service may be affected.

Handling Suggestion
In the Terminal window, run the LOAD LICENSE command to load the License. Then
check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.5.2 2365980673 Performance QoS Critical Alarm

Alarm Information
l Alarm code: 2365980673
l Alarm name: Performance QoS Critical Alarm
l Severity: Critical
l Alarm type: QoS alarm

Probable Cause
Based on monitoring indexes, the performance threshold alarms share different alarm
reasons. Generally speaking, you must confirm the data resources of the monitoring index
and then take appropriate measures to eliminate the alarm.
For example, if the access rate reduces, you have to confirm the detailed reason
according to the access rate formula: call completion rate=(call completion times/call

2-231

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

attempt times)*100%, and you find the main cause is the low call completion times, check
whether it is caused by link faults or insufficient device capacity , and finally decide the
measures to increase the call completion times.

System Impact
The specific system impact is determined by the index monitoring threshold set by the user
and the severity level. When alarms related to some indexes appear, QoS of services may
be affected.
For example,
l Call completion rate: If this index is lower than 90%, a critical alarm appears, and calls
of subscribers may have a lower possibility to be connected.
l Network bandwidth usage ratio: If this index is higher than 80%, a critical alarm
appears. If the alarm does not disappear, it indicates that the current system load
is very high. In that case, you need to upgrade the hardware to satisfy normal system
operation.

Handling Suggestion
1. In the Fault Management window, view and record the alarm details.
2. In the Terminal window, run the SHOW PMMONITOR command to check whether
the setting of corresponding performance threshold is proper.
l Yes: Go to Step 4.
l No: Go to Step 3.
3. In the Terminal window, run the SET PMMONITOR command to modify the
performance threshold. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
4. Check service running status by specific counter or index type, troubleshoot the
services and check whether the alarm is eliminated.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.5.3 2365980674 Performance QoS Major Alarm

Alarm Information
l Alarm code: 2365980674
l Alarm name: Performance QoS major alarm
l Severity: Major
l Alarm type: QoS alarm

Probable Cause
Based on monitoring indexes, the performance threshold alarms share different alarm
reasons. Generally, you can follow these steps to identify the alarm reason:

2-232

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l Confirm the data resources of the monitoring index.

l Take appropriate measures to eliminate the alarm.
For example, if a call completion rate alarm appears, you have to confirm the detailed
reason according to the call completion rate formula: call completion rate=(call
completion times/call attempt times)*100%, and you find the main cause is the low
call completion times, check whether it is caused by link faults or insufficient device
capacity , and finally decide the measures to increase the call completion times.

System Impact
The specific system impact is determined by the index monitoring threshold set by the user
and the severity level. When alarms related to some indexes appear, QoS of services may
be affected.

Handling Suggestion
1. In the Fault Management window, view and record the alarm details.
2. In the Terminal window, run the SHOW PMMONITOR command to check whether
the setting of corresponding performance threshold is proper.
l Yes: Go to Step 4.
l No: Go to Step 3.
3. In the Terminal window, run the SET PMMONITOR command to modify the
performance threshold. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
4. Based on specific counters or index category, check the service status and eliminate
the service failure. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.5.4 2365980675 Performance QoS Common Alarm

Alarm Information
l Alarm code: 2365980675
l Alarm name: Performance QoS Common Alarm
l Severity: Minor
l Alarm type: QoS alarm

Probable Cause
Based on monitoring indexes, the performance threshold alarms share different alarm
reasons. Generally, you can follow these steps to identify the alarm reason:

l Confirm the data resources of the monitoring index.

l Take appropriate measures to eliminate the alarm.

2-233

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

For example, if a call completion rate alarm appears, you have to confirm the detailed
reason according to the call completion rate formula: call completion rate=(call
completion times/call attempt times)*100%, and you find the main cause is the low
call completion times, check whether it is caused by link faults or insufficient device
capacity , and finally decide the measures to increase the call completion times.

System Impact
The specific system impact is determined by the index monitoring threshold set by the user
and the severity level. When alarms related to some indexes appear, QoS of services may
be affected.

Handling Suggestion
1. In the Fault Management window, view and record the alarm details.
2. In the Terminal window, run the SHOW PMMONITOR command to check whether
the setting of corresponding performance threshold is proper.
l Yes: Go to Step 4.
l No: Go to Step 3.
3. In the Terminal window, run the SET PMMONITOR command to modify the
performance threshold. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
4. Based on specific counters or index category, check the service status and eliminate
the service failure. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.5.5 2365980676 Performance QoS Warning Alarm

Alarm Information
l Alarm code: 2365980676
l Alarm name: Performance QoS Warning Alarm
l Severity: Warning
l Alarm type: QoS alarm

Probable Cause
Based on monitoring indexes, the performance threshold alarms share different alarm
reasons. Generally, you can follow these steps to identify the alarm reason:
l Confirm the data resources of the monitoring index.
l Take appropriate measures to eliminate the alarm.
For example, if a call completion rate alarm appears, you have to confirm the detailed
reason according to the call completion rate formula: call completion rate=(call
completion times/call attempt times)*100%, and you find the main cause is the low

2-234

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

call completion times, check whether it is caused by link faults or insufficient device
capacity , and finally decide the measures to increase the call completion times.

System Impact
The specific system impact is determined by the index monitoring threshold set by the user
and the severity level. When alarms related to some indexes appear, QoS of services may
be affected.

Handling Suggestion
1. In the Fault Management window, view and record the alarm details.
2. In the Terminal window, run the SHOW PMMONITOR command to check whether
the setting of corresponding performance threshold is proper.
l Yes: Go to Step 4.
l No: Go to Step 3.
3. In the Terminal window, run the SET PMMONITOR command to modify the
performance threshold. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
4. Based on specific counters or index category, check the service status and eliminate
the service failure. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.5.6 2365980929 Internal Controlled Account Number and

Password Will Expire Soon
Alarm Information
l Alarm code: 2365980929
l Alarm name: Internal Controlled Account Number and Password Will Expire Soon
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
"Send Alarm or Not When Password Expired" is set in the internal control password policy,
"Reminding Days Before Password Expired" is not 0, and the password changed by the
administrator last time now satisfies the expiry reminder condition.

2-235

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Note:
The "Password Validity(d)" and "The Last Time Password Changed" of the internally
controlled account can be queried with the SHOW ACCOUNTINFO command.

System Impact
The normal operation of the network management system is not affected. The alarm is
only a security reminder of the administrator action. If you do not want any reminder, you
can disable this policy.

Handling Suggestion
1. In the Terminal window, run the SHOW PASSWDTACTIC command to check whether
the password expiry reminder is set in the internal control password policy of the
system.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Check whether the application scenario requires a password expiry reminder policy
(for example, for a public network, it is suggested to set a password expiry reminder.)
l Yes: Go to Step 4.
l No: Go to Step 3.
3. In the Terminal window, run the SET PASSWDTACTIC command to set "Send Alarm
or Not When Password Expired" to "No". Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
4. Check whether the system reminds users only when the password expires.
l Yes: Go to Step 5.
l No: Go to Step 6.
5. In the Terminal window, run the SET PASSWDTACTIC command to modify
"Reminding Days Before Password Expired" to "0". Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Go to Step 6.
6. In the Terminal window, run the SET ACCOUNTPASSWD command to change the
internal control password (the initial password is identical to the account name). Wait
for 30 seconds, and then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-236

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Caution!
SET ACCOUNTPASSWD is a dangerous command. When using this command to
change the internal control password, do not perform other network management
operations at the same time.

2.5.7 2365980930 Internal Controlled Account Number and

Password Already Expired
Alarm Information
l Alarm code: 2365980930
l Alarm name: Internal Controlled Account Number and Password Already Expired
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
"Send Alarm or Not When Password Expired" is set in the internal control password policy,
and the administrator does not change the internal control password within the validity
period.

System Impact
The normal operation of the network management system is not affected. The alarm is
only a security reminder of the administrator action. If you do not want any reminder, you
can disable this policy.

Handling Suggestion
1. In the Terminal window, run the SHOW PASSWDTACTIC command to check whether
"Send Alarm or Not When Password Expired" is set in the internal control password
policy of the system.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Check whether the application scenario requires a password expiry reminder policy
(for example, for a public network, it is suggested to set a password expiry reminder.)
l Yes: Go to Step 4.
l No: Go to Step 3.
3. In the Terminal window, run the SET PASSWDTACTIC command to set "Send Alarm
or Not When Password Expired" to "No". Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-237

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

4. In the Terminal window, run the SET ACCOUNTPASSWD command to change the
internal control password (the initial password is identical to the account name). Wait
for 30 seconds, and then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

Caution!
SET ACCOUNTPASSWD is a dangerous command. When using this command to
change the internal control password, do not perform other network management
operations at the same time.

2.5.8 2365980931 Internal Controlled Account Number and

Password Do Not Meet Requirements
Alarm Information
l Alarm code: 2365980931
l Alarm name: Internal Controlled Account Number and Password Do Not Meet
Requirements
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
l The internal control password is shorter than the "Min Length of Password" set in the
internal control password policy.
l The internal control password is longer than the "Max Length of Password" set in the
internal control password policy.
l The password complexity policy is enforced in the internal control password policy,
but the password does not meet the password complexitiy policy.
l The password meets the policy of "Can Not Use Recently Used Password Times" set
in the internal control password policy.

System Impact
The normal operation of the network management system is not affected. The alarm
only reminds the administrator to change the internal control password in compliance with
requirements.

Handling Suggestion
1. In the Terminal window, run the SHOW PASSWDTACTIC command to check the "Min
Length of Password", "Max Length of Password", "Weak Password Check", and "Can

2-238

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Not Use Recently Used Password Times" set in the internal control password policy of
the system. Ensure that the password satisfies the requirements of the internal control
password policy.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. In the Terminal window, run the SET ACCOUNTPASSWD command to change the
internal control password (the initial password is identical to the account name). Wait
for 30 seconds, and then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

Caution!
SET ACCOUNTPASSWD is a dangerous command. When using this command to
change the internal control password, do not perform other network management
operations at the same time.

2.5.9 2365980932 3 Consecutive Wrong Passwords During Login

Alarm Information
l Alarm code: 2365980932
l Alarm name: 3 Consecutive Wrong Passwords During Login
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
The user enters three consecutive wrong passwords during login.

System Impact
If this alarm appears frequently for the same client IP address, the system may be
maliciously attacked by an illegal user.

Handling Suggestion
1. According to the username and login IP address in the additional information of the
alarm, determine whether an illegal user is attacking the system maliciously.
l Yes: Go to Step 2.
l No: Enter the correct password to log in to the system. Then check whether the
alarm disappears.
2. It is suggested that the user set a strong and complex password, so that the user's
account information cannot be stolen, and the user should change the password
regularly. Then check whether the alarm disappears.

2-239

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Yes: End alarm handling.

l No: Contact ZTE for help.

2.5.10 2365980934 Interface Inner Control Account Password Will

Expire Soon
Alarm Information
l Alarm code: 2365980934
l Alarm name: Interface inner control account password will expire soon
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
"Send Alarm or Not When Password Expired" is set in the internal control password policy,
"Reminding Days Before Password Expired" is not 0, and the password changed by the
administrator last time now satisfies the expiry reminder condition.

System Impact
The normal operation of the network management system is not affected. The alarm is
only a security reminder of the administrator action. If you do not want any reminder, you
can disable this policy.

Handling Suggestion
1. In the Terminal window, run the SHOW IFPASSWDTACTIC command to check
whether the password expiry reminder is set.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Check whether the application scenario requires a password expiry reminder policy
(for example, for a public network, it is suggested to set a password expiry reminder.)
l Yes: Go to Step 4.
l No: Go to Step 3.
3. In the Terminal window, run the SET IFPASSWDTACTIC command to set "Send
Alarm or Not When Password Expired" to "No". Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
4. Check whether the system reminds users only when the password expires.
l Yes: Go to Step 5.
l No: Go to Step 6.
5. In the Terminal window, run the SET IFPASSWDTACTIC command to modify
"Reminding Days Before Password Expired" to "0". Then check whether the alarm
disappears.

2-240

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l Yes: End alarm handling.

l No: Go to Step 6.
6. In the Terminal window, run the SET IFACCOUNTPASSWD command to change the
interface inner control password (the initial password is identical to the account name).
Wait for 30 seconds, and then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

Caution!

SET IFACCOUNTPASSWD is a dangerous command. When using this command

to change the internal control password, do not perform other network management
operations at the same time.

2.5.11 2365980935 Interface Inner Control Account Password

Already Expired
Alarm Information
l Alarm code: 2365980935
l Alarm name: Interface inner control account password already expired
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
"Send Alarm or Not When Password Expired" is set in the internal control password policy,
and the administrator does not change the interface internal control password within the
validity period.

System Impact
The normal operation of the network management system is not affected. The alarm is
only a security reminder of the administrator action. If you do not want any reminder, you
can disable this policy.

Handling Suggestion
1. In the Terminal window, run the SHOW IFPASSWDTACTIC command to check
whether "Send Alarm or Not When Password Expired" is set in the interface internal
control password policy of the system.
l Yes: Go to Step 2.
l No: Contact ZTE for help.

2-241

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

2. Check whether the application scenario requires a password expiry reminder policy
(for example, for a public network, it is suggested to set a password expiry reminder.)
l Yes: Go to Step 4.
l No: Go to Step 3.
3. In the Terminal window, run the SET IFPASSWDTACTIC command to set "Send
Alarm or Not When Password Expired" to "No". Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
4. In the Terminal window, run the SET IFACCOUNTPASSWD command to change the
internal control password (the initial password is identical to the account name). Wait
for 30 seconds, and then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

Caution!
SET IFACCOUNTPASSWD is a dangerous command. When using this command
to change the internal control password, do not perform other network management
operations at the same time.

2.5.12 2365980936 Interface Inner Control Account Password Do

Not Meet Requirements
Alarm Information
l Alarm code: 2365980936
l Alarm name: Interface inner control account password do not meet requirements
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
l The interface internal control password is shorter than the "Min Length of Password"
set in the interface internal control password policy.
l The interface internal control password is longer than the "Max Length of Password"
set in the interface internal control password policy.
l The password complexity policy is enforced in the interface internal control password
policy, but the password does not meet the password complexitiy policy.
l The password meets the policy of "Can Not Use Recently Used Password Times" set
in the internal control password policy.

2-242

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

System Impact
The normal operation of the network management system is not affected. The alarm
only reminds the administrator to change the internal control password in compliance with
requirements.

Handling Suggestion
1. In the Terminal window, run the SHOW IFPASSWDTACTIC command to check the
"Min Length of Password", "Max Length of Password", "Weak Password Check", and
"Can Not Use Recently Used Password Times" set in the interface internal control
password policy of the system. Ensure that the password satisfies the requirements
of the internal control password policy.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. In the Terminal window, run the SET IFACCOUNTPASSWD command to change
the interface internal control password (the initial password is identical to the account
name). Wait for 30 seconds, and then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

Caution!

SET IFACCOUNTPASSWD is a dangerous command. When using this command

to change the internal control password, do not perform other network management
operations at the same time.

2.5.13 2365981185 OMM CPU Usage Rate Exceeds Criterion

Alarm Information
l Alarm code: 2365981185
l Alarm name: OMM CPU usage rate exceeds criterion
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
CPU resource monitoring is enabled, and the CPU usage rate of the OMM server exceeds
the usage rate threshold for N times during the monitoring period ("N" is the threshold of
consecutive threshold-crossing times of CPU usage rate, which can be specified with the
SET CPUPARA command). So, this alarm appears.

l The task statistics granularity is too small, so there are too many task objects and
numerous performance statistics tasks are registered.

2-243

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Signaling tracing tasks that have numerous reported messages are registered.
l The CPU monitoring parameter is set improperly.
l It is during a traffic peak period.
l A large batch of network management operations are performed (for example,
allocating numbers with a batch command script).
l The network management backup and restoration operation is being performed.
l Numerous alarms are being reported now.
l The number of NEs managed by the OMM server exceeds the planned capacity.

System Impact
The OMM system cannot be installed, upgraded, or operate properly. Users cannot log in
to the OMM system. Logs cannot be recorded normally. Operation and maintenance may
be affected.

Handling Suggestion
1. In the Terminal window, run the SHOW PMSYSTASK command to check whether
there are numerous activated performance tasks in the OMM system, the task
granularity is small, and there are too many task objects.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. In the Terminal window, run the SET PMSYSTASK command to modify the
performance measurement task to increase the task granularity and reduce the
number of task objects. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. In the Trace Management window, check whether signaling tracing tasks of large
traffic volume are registered in the system.
l Yes: Go to Step 4.
l No: Go to Step 5.
4. Suspend or delete the registered signaling tracing tasks of large traffic volume as
required. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 5.
5. In the Terminal window, run the SHOW CPUPARA command to check whether the
CPU resource monitoring parameter is set properly. The default threshold is 80%.
l Yes: Go to Step 7.
l No: Go to Step 6.
6. In the Terminal window, run the SET CPUPARA command to modify the CPU usage
rate threshold as required. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 7.
7. In the Fault Management window, check whether numerous alarms are being
reported.
l Yes: Go to Step 8.

2-244

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l No: Go to Step 9.
8. Handle the system problems according to the reported alarms. Then check whether
the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 9.
9. Check whether the number of NEs managed by the OMM server exceeds the
maximum capacity.
l Yes: Go to Step 10.
l No: Go to Step 11.
10. Adjust the number of managed NEs according to the system requirement. Then check
whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 11.
11. Check whether it is necessary to monitor CPU resource usage.
l Yes: Contact ZTE for help.
l No: Go to Step 12.

Note:

If a speal operation (for example, backup and restoration operation or number

allocation in batch mode) causes temporary increase in CPU usage, do not monitor
CPU temporarily.

12. In the Terminal window, run the SET CPUPARA command to disable CPU usage
monitoring. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.5.14 2365981186 OMM Memory Usage Rate Exceeds Criterion

Alarm Information
l Alarm code: 2365981186
l Alarm name: OMM Memory Usage Rate Exceeds Criterion
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
Memory resource monitoring is enabled, and the memory usage rate of the OMM server
exceeds the usage rate threshold for N times during the monitoring period ("N" is the
threshold of consecutive threshold-crossing times of memory usage rate, which can be
specified with the SET MEMPARA command). So, this alarm appears.

2-245

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l The memory monitoring parameter is set improperly.

l The number of NEs managed by the OMM server exceeds the planned capacity.

System Impact
The OMM system cannot be installed, upgraded, or operate properly. Users cannot log in
to the OMM system. Logs cannot be recorded normally. Operation and maintenance may
be affected.

Handling Suggestion
1. In the Terminal window, run the SHOW MEMPARA command to check whether the
memory resource monitoring parameter is set properly. The default threshold is 80%.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. In the Terminal window, run the SET MEMPARA command to modify the memory
usage rate threshold as required. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Check whether the number of NEs managed by the OMM server exceeds the
maximum capacity.
l Yes: Go to Step 4.
l No: Go to Step 5.
4. Adjust the number of managed NEs according to the system requirement. Then check
whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 5.
5. Check whether it is necessary to monitor memory resource usage.
l Yes: Contact ZTE for help.
l No: Go to Step 6.

Note:
If a speal operation (for example, manual backup and restoration of a database)
causes temporary increase in memory usage, do not monitor memory temporarily.

6. In the Terminal window, run the SET MEMPARA command to disable CPU usage
monitoring. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-246

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

2.5.15 2365981187 OMM Hard Disk Usage Rate Exceeds

Criterion(Level 1 Alarm)
Alarm Information
l Alarm code: 2365981187
l Alarm name: OMM Hard Disk Usage Rate Exceeds Criterion(Level 1 Alarm)
l Severity: Critical
l Alarm type: Equipment alarm

Probable Cause
Hard disk monitoring is enabled globally. For a specific partition, the monitoring type
parameter is set to "by absolute value" or "by percentage", and the critical alarm threshold
is not 0. The usage rate of this partition exceeds the critical alarm threshold during the
monitoring period, so this alarm appears.
l The performance data export/cleanup period is set improperly. It is recommended to
set the period to 7 days.
l The alarm data export/cleanup period is set improperly. It is recommended to set the
period to 7 days.
l The log data export/cleanup period is set improperly. It is recommended to set the
period to 60 days.
l Call history record (CHR) logs are preserved for too long.
l Temporary files (such as performance and alarm files) reported by NEs to the upper
level NMS (such as NetNumen) are preserved for too long.
l Hardware monitoring parameters are set improperly (by default, level 1-4 alarm
thresholds respectively are 90%, 80%, 70%, and 60%).

System Impact
The OMM system cannot be installed, upgraded, or operate properly. Users cannot log in
to the OMM system. Logs cannot be recorded normally. Operation and maintenance may
be affected.

Handling Suggestion
1. In the Terminal window, run the SHOW PMCLEANPARA command to check whether
the performance data export/cleanup period is set properly.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Adjust the performance data export/cleanup period properly (the recommended period
is 7 days). Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. In the Terminal window, run the SHOW FMCLEARPARA command to check whether
the alarm data export/cleanup period is set properly.

2-247

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Yes: Go to Step 5.
l No: Go to Step 4.
4. Adjust the alarm data export/cleanup period properly (the recommended period is 7
days). Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 5.
5. In the Terminal window, run the SHOW LOGCLEAR PARAM command to check
whether the log data export/cleanup period is set properly.
l Yes: Go to Step 7.
l No: Go to Step 6.
6. Adjust the log data export/cleanup period properly (the recommended period is 60
days). Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 7.
7. In the Terminal window, run the SHOW PARTITIONPARA command to check
whether the monitoring thresholds in hard disk partition monitoring settings are set
properly.
l Yes: Go to Step 9.
l No: Go to Step 8.
8. Adjust the monitoring thresholds in hard disk partition monitoring settings properly (It is
recommended to use the default level 1-4 alarm thresholds, namely, 90%, 80%, 70%,
and 60%). Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 9.
9. According to the additional information of the alarm and actual requirements, delete
unused files from the hard disk partition to provide more free space, so that the usage
rate drops below the corresponding alarm threshold. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.5.16 2365981188 OMM Hard Disk Usage Rate Exceeds

Criterion(Level 2 Alarm)
Alarm Information
l Alarm code: 2365981188
l Alarm name: OMM Hard Disk Usage Rate Exceeds Criterion(Level 2 Alarm)
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
Hard disk monitoring is enabled globally. For a specific partition, the monitoring type
parameter is set to "by absolute value" or "by percentage", and the major alarm threshold

2-248

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

is not 0. The usage rate of this partition exceeds the major alarm threshold (but below the
critical alarm threshold) during the monitoring period, so this alarm appears.
l The performance data export/cleanup period is set improperly. It is recommended to
set the period to 7 days.
l The alarm data export/cleanup period is set improperly. It is recommended to set the
period to 7 days.
l The log data export/cleanup period is set improperly. It is recommended to set the
period to 60 days.
l Call history record (CHR) logs are preserved for too long.
l Temporary files (such as performance and alarm files) reported by NEs to the upper
level NMS (such as NetNumen) are preserved for too long.
l Hardware monitoring parameters are set improperly (by default, level 1-4 alarm
thresholds respectively are 90%, 80%, 70%, and 60%).

System Impact
The OMM system cannot be installed, upgraded, or operate properly. Users cannot log in
to the OMM system. Logs cannot be recorded normally. Operation and maintenance may
be affected.

Handling Suggestion
1. In the Terminal window, run the SHOW PMCLEANPARA command to check whether
the performance data export/cleanup period is set properly.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Adjust the performance data export/cleanup period properly (the recommended period
is 7 days). Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. In the Terminal window, run the SHOW FMCLEARPARA command to check whether
the alarm data export/cleanup period is set properly.
l Yes: Go to Step 5.
l No: Go to Step 4.
4. Adjust the alarm data export/cleanup period properly (the recommended period is 7
days). Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 5.
5. In the Terminal window, run the SHOW LOGCLEAR PARAM command to check
whether the log data export/cleanup period is set properly.
l Yes: Go to Step 7.
l No: Go to Step 6.
6. Adjust the log data export/cleanup period properly (the recommended period is 60
days). Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 7.

2-249

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

7. In the Terminal window, run the SHOW PARTITIONPARA command to check

whether the monitoring thresholds in hard disk partition monitoring settings are set
properly.
l Yes: Go to Step 9.
l No: Go to Step 8.
8. Adjust the monitoring thresholds in hard disk partition monitoring settings properly (It is
recommended to use the default level 1-4 alarm thresholds, namely, 90%, 80%, 70%,
and 60%). Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 9.
9. According to the additional information of the alarm and actual requirements, delete
unused files from the hard disk partition to provide more free space, so that the usage
rate drops below the corresponding alarm threshold. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.5.17 2365981189 OMM Hard Disk Usage Rate Exceeds

Criterion(Level 3 Alarm)
Alarm Information
l Alarm code: 2365981189
l Alarm name: OMM Hard Disk Usage Rate Exceeds Criterion(Level 3 Alarm)
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
Hard disk monitoring is enabled globally. For a specific partition, the monitoring type
parameter is set to "by absolute value" or "by percentage", and the minor alarm threshold
is not 0. The usage rate of this partition exceeds the minor alarm threshold (but below the
major alarm threshold) during the monitoring period, so this alarm appears.

l The performance data export/cleanup period is set improperly. It is recommended to

set the period to 7 days.
l The alarm data export/cleanup period is set improperly. It is recommended to set the
period to 7 days.
l The log data export/cleanup period is set improperly. It is recommended to set the
period to 60 days.
l Call history record (CHR) logs are preserved for too long.
l Temporary files (such as performance and alarm files) reported by NEs to the upper
level NMS (such as NetNumen) are preserved for too long.
l Hardware monitoring parameters are set improperly (by default, level 1-4 alarm
thresholds respectively are 90%, 80%, 70%, and 60%).

2-250

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

System Impact
The OMM system cannot be installed, upgraded, or operate properly. Users cannot log in
to the OMM system. Logs cannot be recorded normally. Operation and maintenance may
be affected.

Handling Suggestion
1. In the Terminal window, run the SHOW PMCLEANPARA command to check whether
the performance data export/cleanup period is set properly.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Adjust the performance data export/cleanup period properly (the recommended period
is 7 days). Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. In the Terminal window, run the SHOW FMCLEARPARA command to check whether
the alarm data export/cleanup period is set properly.
l Yes: Go to Step 5.
l No: Go to Step 4.
4. Adjust the alarm data export/cleanup period properly (the recommended period is 7
days). Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 5.
5. In the Terminal window, run the SHOW LOGCLEAR PARAM command to check
whether the log data export/cleanup period is set properly.
l Yes: Go to Step 7.
l No: Go to Step 6.
6. Adjust the log data export/cleanup period properly (the recommended period is 60
days). Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 7.
7. In the Terminal window, run the SHOW PARTITIONPARA command to check
whether the monitoring thresholds in hard disk partition monitoring settings are set
properly.
l Yes: Go to Step 9.
l No: Go to Step 8.
8. Adjust the monitoring thresholds in hard disk partition monitoring settings properly (It is
recommended to use the default level 1-4 alarm thresholds, namely, 90%, 80%, 70%,
and 60%). Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 9.
9. According to the additional information of the alarm and actual requirements, delete
unused files from the hard disk partition to provide more free space, so that the usage
rate drops below the corresponding alarm threshold. Then check whether the alarm
disappears.

2-251

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Yes: End alarm handling.

l No: Contact ZTE for help.

2.5.18 2365981190 OMM Hard Disk Usage Rate Exceeds

Criterion(Level 4 Alarm)
Alarm Information
l Alarm code: 2365981190
l Alarm name: OMM Hard Disk Usage Rate Exceeds Criterion(Level 4 Alarm)
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
Hard disk monitoring is enabled globally. For a specific partition, the monitoring type
parameter is set to "by absolute value" or "by percentage", and the warning alarm threshold
is not 0. The usage rate of this partition exceeds the warning alarm threshold (but below
the minor alarm threshold) during the monitoring period, so this alarm appears.
l The performance data export/cleanup period is set improperly. It is recommended to
set the period to 7 days.
l The alarm data export/cleanup period is set improperly. It is recommended to set the
period to 7 days.
l The log data export/cleanup period is set improperly. It is recommended to set the
period to 60 days.
l Call history record (CHR) logs are preserved for too long.
l Temporary files (such as performance and alarm files) reported by NEs to the upper
level NMS (such as NetNumen) are preserved for too long.
l Hardware monitoring parameters are set improperly (by default, level 1-4 alarm
thresholds respectively are 90%, 80%, 70%, and 60%).

System Impact
The OMM system cannot be installed, upgraded, or operate properly. Users cannot log in
to the OMM system. Logs cannot be recorded normally. Operation and maintenance may
be affected.

Handling Suggestion
1. In the Terminal window, run the SHOW PMCLEANPARA command to check whether
the performance data export/cleanup period is set properly.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Adjust the performance data export/cleanup period properly (the recommended period
is 7 days). Then check whether the alarm disappears.
l Yes: End alarm handling.

2-252

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l No: Go to Step 3.
3. In the Terminal window, run the SHOW FMCLEARPARA command to check whether
the alarm data export/cleanup period is set properly.
l Yes: Go to Step 5.
l No: Go to Step 4.
4. Adjust the alarm data export/cleanup period properly (the recommended period is 7
days). Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 5.
5. In the Terminal window, run the SHOW LOGCLEAR PARAM command to check
whether the log data export/cleanup period is set properly.
l Yes: Go to Step 7.
l No: Go to Step 6.
6. Adjust the log data export/cleanup period properly (the recommended period is 60
days). Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 7.
7. In the Terminal window, run the SHOW PARTITIONPARA command to check
whether the monitoring thresholds in hard disk partition monitoring settings are set
properly.
l Yes: Go to Step 9.
l No: Go to Step 8.
8. Adjust the monitoring thresholds in hard disk partition monitoring settings properly (It is
recommended to use the default level 1-4 alarm thresholds, namely, 90%, 80%, 70%,
and 60%). Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 9.
9. According to the additional information of the alarm and actual requirements, delete
unused files from the hard disk partition to provide more free space, so that the usage
rate drops below the corresponding alarm threshold. Then check whether the alarm
disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.5.19 2365981191 Directory Usage Rate Exceeds Criterion (Level 1

Alarm)
Alarm Information
l Alarm code: 2365981191
l Alarm name: Directory Usage Rate Exceeds Criterion (Level 1 Alarm)
l Severity: Critical
l Alarm type: Equipment alarm

2-253

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Probable Cause
In resource monitoring configuration, a monitored object is uniquely determined by three
parameters: directory description, file type, and whether to include sub folders. For a
specific monitored directory, monitoring is enabled and the critical alarm threshold is not
0. The file size of the directory exceeds the critical alarm threshold during the monitoring
period, so this alarm appears.
l There are too many files in the directory.
l The directory monitoring parameter is set improperly.

System Impact
This alarm helps you learn the usage of important directories promptly.
l If the monitored directory is the installation directory of the OMM system, possible
system impacts are as follows: The OMM system cannot be installed, upgraded, or
operate properly. Users cannot log in to the OMM system. Logs cannot be recorded
normally.
l If the monitored directory is a database directory, insufficient free space may lead to
unsuccessful data import and thus the system cannot operate properly.
l If the monitored directory is some other user directory, user data cannot be added or
modified normally.

Handling Suggestion
1. In the Terminal window, run the SHOW DIRPARA command to view the additional
information and see whether the monitoring function is enabled for the corresponding
directory and the monitoring period is reasonable.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Check whether it is necessary to enable directory resource monitoring.
l Yes: Go to Step 4.
l No: Go to Step 3.
3. In the Terminal window, run the SET DIRPARA command to disable the monitoring
function for the corresponding directory in directory resource monitoring settings (this
operation is not recommended). Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
4. In the Terminal window, run the SHOW DIRPARA command to check whether the
monitoring thresholds in directory resource monitoring settings are set properly.
l Yes: Go to Step 6.
l No: Go to Step 5.
5. In the Terminal window, run the SET DIRPARA command to modify the monitoring
thresholds properly. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-254

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

6. According to actual requirements, delete unused files of specified types from the
directory to provide more free space, so that the directory usage rate drops below the
corresponding alarm threshold. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.5.20 2365981192 Directory Usage Rate Exceeds Criterion (Level 2

Alarm)
Alarm Information
l Alarm code: 2365981192
l Alarm name: Directory Usage Rate Exceeds Criterion (Level 2 Alarm)
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
In resource monitoring configuration, a monitored object is uniquely determined by three
parameters: directory description, file type, and whether to include sub folders. For a
specific monitored directory, monitoring is enabled and the major alarm threshold is not
0. The file size of the directory exceeds the major alarm threshold (but below the critical
alarm threshold) during the monitoring period, so this alarm appears.
l There are too many files in the directory.
l The directory monitoring parameter is set improperly.

System Impact
This alarm helps you learn the usage of important directories promptly.
l If the monitored directory is the installation directory of the OMM system, possible
system impacts are as follows: The OMM system cannot be installed, upgraded, or
operate properly. Users cannot log in to the OMM system. Logs cannot be recorded
normally.
l If the monitored directory is a database directory, insufficient free space may lead to
unsuccessful data import and thus the system cannot operate properly.
l If the monitored directory is some other user directory, user data cannot be added or
modified normally.

Handling Suggestion
1. In the Terminal window, run the SHOW DIRPARA command to view the additional
information and see whether the monitoring function is enabled for the corresponding
directory and the monitoring period is reasonable.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Check whether it is necessary to enable directory resource monitoring.

2-255

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Yes: Go to Step 4.
l No: Go to Step 3.
3. In the Terminal window, run the SET DIRPARA command to disable the monitoring
function for the corresponding directory in directory resource monitoring settings (this
operation is not recommended). Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
4. In the Terminal window, run the SHOW DIRPARA command to check whether the
monitoring thresholds in directory resource monitoring is set properly.
l Yes: Go to Step 6.
l No: Go to Step 5.
5. In the Terminal window, run the SET DIRPARA command to modify the monitoring
thresholds properly. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
6. According to actual requirements, delete unused files of specified types from the
directory to provide more free space, so that the directory usage rate drops below the
corresponding alarm threshold. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.5.21 2365981193 Directory Usage Rate Exceeds Criterion (Level 3

Alarm)
Alarm Information
l Alarm code: 2365981193
l Alarm name: Directory Usage Rate Exceeds Criterion (Level 3 Alarm)
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
In resource monitoring configuration, a monitored object is uniquely determined by three
parameters: directory description, file type, and whether to include sub folders. For a
specific monitored directory, monitoring is enabled and the minor alarm threshold is not 0.
The file size of the directory exceeds the minor alarm threshold (but below the major alarm
threshold) during the monitoring period, so this alarm appears.

l There are too many files in the directory.

l The directory monitoring parameter is set improperly.

System Impact
This alarm helps you learn the usage of important directories promptly.

2-256

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l If the monitored directory is the installation directory of the OMM system, possible
system impacts are as follows: The OMM system cannot be installed, upgraded, or
operate properly. Users cannot log in to the OMM system. Logs cannot be recorded
normally.
l If the monitored directory is a database directory, insufficient free space may lead to
unsuccessful data import and thus the system cannot operate properly.
l If the monitored directory is some other user directory, user data cannot be added or
modified normally.

Handling Suggestion
1. In the Terminal window, run the SHOW DIRPARA command to view the additional
information and see whether the monitoring function is enabled for the corresponding
directory and the monitoring period is reasonable.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Check whether it is necessary to enable directory resource monitoring.
l Yes: Go to Step 4.
l No: Go to Step 3.
3. In the Terminal window, run the SET DIRPARA command to disable the monitoring
function for the corresponding directory in directory resource monitoring settings (this
operation is not recommended). Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
4. In the Terminal window, run the SHOW DIRPARA command to check whether the
monitoring thresholds in directory resource monitoring settings are set properly.
l Yes: Go to Step 6.
l No: Go to Step 5.
5. In the Terminal window, run the SET DIRPARA command to modify the monitoring
thresholds properly. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
6. According to actual requirements, delete unused files of specified types from the
directory to provide more free space, so that the directory usage rate drops below the
corresponding alarm threshold. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.5.22 2365981194 Directory Usage Rate Exceeds Criterion (Level 4

Alarm)
Alarm Information
l Alarm code: 2365981194
l Alarm name: Directory Usage Rate Exceeds Criterion (Level 4 Alarm)

2-257

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
In resource monitoring configuration, a monitored object is uniquely determined by three
parameters: directory description, file type, and whether to include sub folders. For a
specific monitored directory, monitoring is enabled and the warning alarm threshold is not
0. The file size of the directory exceeds the warning alarm threshold (but below the minor
alarm threshold) during the monitoring period, so this alarm appears.
l There are too many files in the directory.
l The directory monitoring parameter is set improperly.

System Impact
This alarm helps you learn the usage of important directories promptly.
l If the monitored directory is the installation directory of the OMM system, possible
system impacts are as follows: The OMM system cannot be installed, upgraded, or
operate properly. Users cannot log in to the OMM system. Logs cannot be recorded
normally.
l If the monitored directory is a database directory, insufficient free space may lead to
unsuccessful data import and thus the system cannot operate properly.
l If the monitored directory is some other user directory, user data cannot be added or
modified normally.

Handling Suggestion
1. In the Terminal window, run the SHOW DIRPARA command to view the additional
information and see whether the monitoring function is enabled for the corresponding
directory and the monitoring period is reasonable.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Check whether it is necessary to enable directory resource monitoring.
l Yes: Go to Step 4.
l No: Go to Step 3.
3. In the Terminal window, run the SET DIRPARA command to disable the monitoring
function for the corresponding directory in directory resource monitoring settings (this
operation is not recommended). Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
4. In the Terminal window, run the SHOW DIRPARA command to check whether the
monitoring thresholds in directory resource monitoring settings are set properly.
l Yes: Go to Step 6.
l No: Go to Step 5.
5. In the Terminal window, run the SET DIRPARA command to modify the monitoring
thresholds properly. Then check whether the alarm disappears.

2-258

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

l Yes: End alarm handling.

l No: Contact ZTE for help.
6. According to actual requirements, delete unused files of specified types from the
directory to provide more free space, so that the directory usage rate drops below the
corresponding alarm threshold. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.5.23 2365981441 License File Illegal

Alarm Information
l Alarm code: 2365981441
l Alarm name: License File illegal
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
l User information set in the license file is inconsistent with the license file name
(excluding the suffix).
l The MAC address set in the license file does not match the MAC address of any
network card of the OMM server.
l The license file format is illegal. The file is not generated by the license tool.

System Impact
If the license is not loaded successfully, all network management or service functions
controlled by the license cannot be used.

Handling Suggestion
Make a new license file. Contact ZTE for help.

2.5.24 2365981443 License File Unavailable

Alarm Information
l Alarm code: 2365981443
l Alarm name: License File Unavailable
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
No license file is available.

2-259

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
If the license is not loaded successfully, all network management or service functions
controlled by the license cannot be used.

Handling Suggestion
Purchase a license file. Contact ZTE for help.

2.5.25 2365981444 Multiple License Files Exist

Alarm Information
l Alarm code: 2365981444
l Alarm name: Multiple License Files Exist
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
There are more than one license file in the license directory.

System Impact
If the license is not loaded successfully, all network management or service functions
controlled by the license cannot be used.

Handling Suggestion
Contact ZTE for help.

2.5.26 2365981445 Loaded License File Expires

Alarm Information
l Alarm code: 2365981445
l Alarm name: Loaded License File Expires
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
The license file loaded by the OMM system expires its committed validity period. If a client
logs in to the OMM system or when it is 5:00 a.m. of the next day, this alarm appears.

System Impact
If the license is not valid, all network management or service functions controlled by the
license cannot be used.

2-260

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Handling Suggestion
Upgrade the license file. Contact ZTE for help.

2.5.27 2365981697 Link Broken Between NE and OMM

Alarm Information
l Alarm code: 2365981697
l Alarm name: Link Broken Between NE and OMM
l Severity: Critical
l Alarm type: Communication alarm

Probable Cause
l The network connection fails.
l The IP address or port number of this node configured on the OMM server is incorrect.

System Impact
NE data cannot be reported. OMM configuration commands cannot be sent. Operations
related to foreground services cannot be performed. Operation and maintenance of the
OMM is affected.

Handling Suggestion
1. Check whether the physical link between the faulty node and the OMM server is
normal.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Eliminate the physical link failure. Then check whether the notification disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. In the Terminal window, run the CHECK OMC LINK command to check whether the
IP address and port number of the node configured on the OMM server are correct.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Create a correct OMS Socket link and delete the incorrect link. Then check whether
the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.5.28 2365981698 Link Broken Between Alarm Box and OMM

Alarm Information
l Alarm code: 2365981698

2-261

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Alarm name: Link broken between alarm box and OMM

l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
l The alarm box is not connected.
l The communication between the alarm box and the OMM server is broken.

System Impact
Alarm status cannot be shown by the alarm box.

Handling Suggestion
1. Check whether the physical link between the faulty node and the OMM server is
normal.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Eliminate the physical link failure. Then check whether the notification disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. In the Terminal window, run the SHOW ALARMBOX command to to check whether
the server-end listening port configured on the OMM server is occupied, and the
address of the alarm box is consistent with that set on the OMM server and is unused.
l Yes: Go to Step 4.
l No: Go to Step 5.
4. In the Terminal window, run the SET ALARMBOX command to modify the port
settings of the alarm box. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 5.
5. Determine whether it is necessary to ignore the alarm temporarily.
l Yes: Go to Step 6.
l No: Contact ZTE for help.
6. In the Terminal window, run the SET ALARMBOX command to disable the alarm box
in the OMM server alarm settings. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.5.29 2365981699 OMM Changeover Success

Alarm Information
l Alarm code: 2365981699
l Alarm name: OMM changeover success
l Severity: Warning
l Alarm type: Processing error alarm

2-262

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

Probable Cause
Active/Standby OMM server changeover is performed manually, or the old OMM server
detects a resource failure that cannot be eliminated and thus triggers active/standby
changeover. After the standby OMM server becomes active, this alarm appears.

System Impact
During the changeover process, OMM commands cannot be executed on EMS.

Handling Suggestion
1. Check whether the changeover is performed manually.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Complete the manual changeover. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Go to Step 3.
3. Refer to the dual-node OMM server configuration document to handle the resource
failure of the previously active OMM server. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.5.30 2365981700 Link Broken Between Independent Board and

OMM
Alarm Information
l Alarm code: 2365981700
l Alarm name: Link Broken Between Independent Board and OMM
l Severity: Critical
l Alarm type: Communication alarm

Probable Cause
The communication is abnormal.

System Impact
Alarms/Notifications of the independent board cannot be reported to the OMM, and thus
OMM cannot learn the status of the independent board or even the whole rack.

Handling Suggestion
1. Check whether the connection between the OMM and independent board is normal.
l Yes: Go to Step 2.
l No: Contact ZTE for help.

2-263

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

2. Restore the link between the OMM and independent board to normal. Then check
whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.5.31 2365981703 SNMP Configuration Inconsistent With

Independent Board
Alarm Information
l Alarm code: 2365981703
l Alarm name: SNMP configuration inconsistent with independent board
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
l Link between the independent board and OMM is broken.
l Local SNMP configuration (IP or SNMP read community ) is wrong.
l The SNMP configuration on the independent board is wrong, so OMM access is
forbidden on the board.

System Impact
The system fails to get information from this board initially, so alarm synchronization fails
and possibly the alarms on this board are inconsistent with those on the front end.

Handling Suggestion
1. Check whether the physical link between this board and OMM is normal.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Eliminate the fault with the physical connection of the network, and then check whether
the alarm disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Check whether the IP address and SNMP read community in this alarm are configured
correctly.
l Yes: Contact ZTE for help.
l If the IP configuration is wrong: Go to Step 4.
l If the configuration of the SNMP read community is wrong: Go to Step 5.
4. In the Terminal window of the LMT window, run the DEL FMSNMPCFG command
to delete the wrong board configuration and run the ADD FMSNMPCFG command to
add the correct board configuration. Then, check whether the alarm disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

2-264

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

5. In the Terminal window of the LMT window, run the SET FMSNMPCFG command
to configure the correct SNMP read community, and then check whether the alarm
disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

2.5.32 2365981953 Link Broken Between NTP Server and OMM

Alarm Information
l Alarm code: 2365981953
l Alarm name: Link broken between NTP server and OMM
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
The communication is abnormal.

System Impact
The local system time cannot be updated.

Handling Suggestion
1. Check whether the network of the upper level NTP server is normal and the NTP server
is started.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. In the Terminal window, run the SHOW SYSLOG command to view detailed error
description and handle the problem accordingly. Then check whether the alarm
disappears.
The command format is: SHOW SYSLOG:FUNCNAME="NTP";
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.5.33 2365981954 Time of NTP Server Unsynchronized

Alarm Information
l Alarm code: 2365981954
l Alarm name: Time of NTP server unsynchronized
l Severity: Major
l Alarm type: Equipment alarm

2-265

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Probable Cause
The NTP service is abnormal.

System Impact
The local system time cannot be updated.

Handling Suggestion
1. Check whether the network of the upper level NTP server is normal and the NTP server
is started.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. In the Terminal window, run the SHOW SYSLOG command to view detailed error
description and handle the problem accordingly. Then check whether the alarm
disappears.
The command format is: SHOW SYSLOG:FUNCNAME="NTP";
l Yes: End alarm handling.
l No: Contact ZTE for help.

2.5.34 2365981955 NTP Clock Offset Over Maximum Threshold

Alarm Information
l Alarm code: 2365981955
l Alarm name: NTP clock offset over maximum threshold
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
The NTP time offset exceeds the threshold.

System Impact
The local system time cannot be updated.

Handling Suggestion
1. In the Terminal window, run the SYNC NTPTIME command to synchronize the NTP
time manually. Then check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.
2. In the Terminal window, run the SHOW SYSLOG command to view detailed error
description and handle the problem accordingly. Then check whether the alarm
disappears.

2-266

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 2 Alarm Messages Handling

The command format is: SHOW SYSLOG:FUNCNAME="NTP";

l Yes: End alarm handling.
l No: Contact ZTE for help.

2.5.35 2365982209 Automatic Backup Failed

Alarm Information
l Alarm code: 2365982209
l Alarm name: Automatic Backup Failed
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
An automatic backup task of the OMM server fails to be executed.

System Impact
The automatic backup task of the OMM server fails to be executed.

Handling Suggestion
1. In the In the Fault Management window, view the backup log ID in the additional
information of the alarm.
2. According to the backup log ID, open the Terminal window and run the SHOW BAK
LOG command to query details of the backup log.
3. According to the failure cause in the backup log, handle the backup failure. Then
check whether the alarm disappears.
l Yes: End alarm handling.
l No: Contact ZTE for help.

2-267

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

This page intentionally left blank.

2-268

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3
Notification Message
Handling
Table of Contents
1~9999.......................................................................................................................3-1
10000~99999 ...........................................................................................................3-33
10000000~9999999999 ......................................................................................... 3-111

3.1 1~9999
3.1.1 31 Power On Failed Inform
Notification Message
l Notification code: 31
l Notification name: Power On Failed Inform
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
The hardware or the software of the board was abnormal.

System Impact
The board could not run properly.

Handling Suggestion
In the Fault Management window, view the notification details.

According to the detailed information, locate the reason why the board cannot be powered
on and solve the problem. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3-1

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

3.1.2 576 Trunk Slip

Notification Message
l Notification code: 576
l Notification name: Trunk slip
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
Because frequency difference exists between the trunk line clock and the locally received
clock, the trunk-received clock is not synchronous with the sent clock.

System Impact
The data service or the signaling channel in the trunk link is faulty instantaneously, which
has no impact on services. If this notification is reported frequently, it may render services
unstable.

Handling Suggestion
1. Check whether the clock status on both sides is consistent.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Check whether there is an alarm of the clock generator losing lock (alarm code: 26127,
26128 and 26129).
l Yes: Handle the alarm by referring to the corresponding handling suggestions.
l No: Contact ZTE for help.

Related Alarms
l 2.2.38 26127 Clock Reference Source Lost (Level 3 Alarm)
l 2.2.39 26128 Clock Reference Source Lost (Level 2 Alarm)
l 2.2.40 26129 Clock Reference Source Lost (Level 1 Alarm)

3.1.3 834 MCC Is Abnormal

Notification Message
l Notification code: 834
l Notification name: MCC is abnormal
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
The Management Communication Channel (MCC) hardware is faulty.

3-2

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

System Impact
All channels of MCC cannot send or receive data.

Handling Suggestion
Extract the board. Wait for about five seconds until the board discharges completely. Then
check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.1.4 1600 CPU Resets on a Board in the Same Shelf

Notification Message
l Notification code: 1600
l Notification name: CPU resets on a board in the same shelf
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
The board was abnormal or it was reset by man-machine command.

System Impact
The board could not run properly after it was reset.

Handling Suggestion
1. Check whether the board is reset by man-machine command.
l Yes: You do not need to handle this fault because it is a normal notification.
l No: Go to Step 2.
2. Check whether the board is faulty or not.
l Yes: Go to Step 3.
l No: Contact ZTE for help.
3. Eliminate the board fault. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.1.5 2625 There Is a Dead Lock in Process

Notification Message
l Notification code: 2625
l Notification name: There is a dead lock in process
l Severity: Major
l Alarm type: Processing error alarm

3-3

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Probable Cause
A resource deadlock occurs, for example, semaphore deadlock.

System Impact
The resuorce cannot be released in time, and thus the resource is used up, or the process
cannot be scheduled for ever.

Handling Suggestion
Record the notification information, and Contact ZTE for help.

3.1.6 2880 CPU Dead-Loop

Notification Message
l Notification code: 2880
l Notification name: CPU dead-loop
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
A dead loop exists in the process or system task.

System Impact
The process or task with lower priorities cannot be scheduled.

Handling Suggestion
The board is automatically restarted when the notification appears. Then check whether
the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.1.7 3136 Disk Is Full

Notification Message
l Notification code: 3136
l Notification name: Disk is full
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
l The notification possibly appears on a CMM and other charging related boards.

3-4

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

l On a CMM, the notification appears possibly because there are too many unused
versions.
l On other charging related boards, the alarm appears possibly because the link be-
tween foreground and background is interrupted for so long that much charging infor-
mation is stored on the disk.

System Impact
When the disk is full, the write operation on the disk or the operation of creating a file or
directory may fail. Hence, disk operations performed by the background on the foreground
may fail.

Handling Suggestion
1. Check whether the target board of the notification is CMM.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Delete unused version files from the CMM. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Check whether the target board of the notification is a charging related board.
l Yes: Go to Step 4.
l No: Contact ZTE for help.
4. Check whether the link between the charging board and the charging background is
normal and whether the charging server is normal.
l Yes: Contact ZTE for help.
l No: Go to Step 5.
5. Make sure that the link between the charging board and the charging background
is normal and the charging server is normal. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.1.8 3137 File Operation Is Fail

Notification Message
l Notification code: 3137
l Notification name: File operation is fail
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
The notification appears when the disk is damaged, full, or operating outdated file
descriptors.

3-5

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
Analyze the system impact according to the additional information.

Handling Suggestion
Record the notification information, and contact ZTE for help.

3.1.9 3392 Timer Resource Is Deficient

Notification Message
l Notification code: 3392
l Notification name: Timer resource is deficient
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
Timer resources are not enough.

System Impact
Setting the timers fails.

Handling Suggestion
Record the notification information, and contact ZTE for help.

3.1.10 3393 Predefine Timer Is Not Config or Is Config But Not

Restart the Board
Notification Message
l Notification code: 3393
l Notification name: Predefine timer is not config or is config but not restart the board
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
l The related pre-defined timer is not configured.
l After CMM configuration is completed, the corresponding board is not restarted to
validate the new configuration.

System Impact
Setting the timers fails.

3-6

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Handling Suggestion
Record the notification information, and contact ZTE for help.

3.1.11 3648 Ub Is Deficient

Notification Message
l Notification code: 3648
l Notification name: Ub is deficient
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
l UB resources are not enough.
l Messages are not processed in time, and thus the UB resources are occupied for a
long time and cannot be released.

System Impact
l The link is interrupted.
l Messages cannot be sent successfully.

Handling Suggestion
Record the notification information, and contact ZTE for help.

3.1.12 3649 Sblock Is Deficient

Notification Message
l Notification code: 3649
l Notification name: Sblock is deficient
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
l UB resources are not enough.
l Messages are not processed in time, and thus the UB resources are occupied for a
long time and cannot be released.

System Impact
l The link is interrupted.
l Messages cannot be sent successfully.

3-7

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Handling Suggestion
Record the notification information, and contact ZTE for help.

3.1.13 3904 Communication Buffer Is Full

Notification Message
l Notification code: 3904
l Notification name: Communication buffer is full
l Severity: Warning
l Alarm type: Environment alarm

Probable Cause
Too many messages are sent within a short period.

System Impact
None

Handling Suggestion
Record the notification information, and contact ZTE for help.

3.1.14 3905 Convert Function Is Registered Repeated

Notification Message
l Notification code: 3905
l Notification name: Convert function is registered repeated
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
The byte order conversion function is repeatedly registered for the same message.

System Impact
UB may be damaged or abnormal data access may occur.

Handling Suggestion
Record the notification information, and contact ZTE for help.

3-8

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

3.1.15 3907 Write CMM's CDM Failed

Notification Message
l Notification code: 3907
l Notification name: Write CMM's CDM failed
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
When the CMM writes configuration information to two CDMs, the CDMs probably are not
in position or are unavailable.

System Impact
The CDM configuration is not updated. The system may not load the new configuration
after the next restart.

Handling Suggestion
1. Check whether the two CDMs are in position or are available.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Check whether the CDM boards are inserted well.
l Yes: Go to Step 4.
l No: Go to Step 3.
3. Insert the CDM boards well. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 4.
4. Contact the ZTE technical support personnel to replace the CDM boards.

Note:
After replacing the CDM boards, it is required to re-configure them, and restart these
two CMM boards.

3.1.16 3909 The CDM's Configuration About Net Address Is Invalid

Notification Message
l Notification code: 3909
l Notification name: The CDM's configuration about net address is invalid
l Severity: Warning
l Alarm type: Processing error alarm

3-9

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Probable Cause
l Configuration error
l Invalid address input

System Impact
The board may not obtain the right IP address after power-on.

Handling Suggestion
1. In the Terminal window, run the SHOW LEFTCDMCFG / SHOW RIGHTCDM CFG
command to query whether the Debug Address and OMC Address parameters are
correctly configured.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. In the Terminal window, run the SET LEFTCDMCFG / SET RIGHTCDMCFG
command to configure the Debug Address and OMC Address parameters.
3. In the Terminal window, run the RESET LEFTCMM / RESET RIGHTCMM command
to restart the two CMM boards under the guide of the ZTE technical support personnel.
Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.1.17 4417 Exception Information

Notification Message
l Notification code: 4417
l Notification name: Exception information
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
A deadlock, endless loop, or system exception occurs.

System Impact
The system does not operate properly.

Handling Suggestion
Locate the position and the cause of the exception according to the alarm messages and
records of this exception. Contact ZTE for help.

3-10

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

3.1.18 4418 Logic CPU Is Power on Successfully

Notification Message
l Notification code: 4418
l Notification name: Logic CPU is power on successfully
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
Logical CPU is successfully powered on.

System Impact
None

Handling Suggestion
No handling is required.

3.1.19 4419 Logic CPU Is Power on Failed

Notification Message
l Notification code: 4419
l Notification name: Logic CPU is power on failed
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
Logical CPU fails to be powered on.

System Impact
None

Handling Suggestion
1. Check whether the OMP module is working normally.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Ensure that the OMP module is powered on successfully and is working normally.
Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.
3. Check whether the communications between this logic CPU and OMP module is in
order.

3-11

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Yes: Contact ZTE for help.

l No: Go to Step 4.
4. Check whether the related switching board is working normally.
l Yes: Contact ZTE for help.
l No: Go to Step 5.
5. Restore the related switching board to normal. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.1.20 5189 Board Change Over Notice

Notification Message
l Notification code: 5189
l Notification name: Board change over notice
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
l The hardware system of the board has some failure.
l The MML command for changeover is executed.

System Impact
If the changeover fails, the boards are reset automatically.

Handling Suggestion
1. In the Fault Management window, view details of the notification and see whether the
changeover is due to a system failure.
l Yes: Go to Step 2.
l No: No handling is required.
2. Eliminate the system fault. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.1.21 5192 Board's Working Mode Unsupported

Notification Message
l Notification code: 5192
l Notification name: Board's working mode unsupported
l Severity: Minor
l Alarm type: Processing error alarm

3-12

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Probable Cause
l Unsupported working mode of the board is configured on the OMM.
l An error occurs in setting the working mode of the board because the FPGA is not
loaded or due to other reasons.

System Impact
This results in the board losing the active/standby function.

Handling Suggestion
1. Check the backup mode of the board and confirm whether this board supports this
active/standby mode.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Modify the backup mode of the board supporting active/standby mode. Then check
whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Replace the board with another board supporting active/standby mode. Then check
whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 4.
4. Insert and extract the board, and then reload the FPGA version. Then check whether
the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.1.22 5193 Notification of Board's Power-on Status

Notification Message
l Notification code: 5193
l Notification name: Notification of board's power-on status
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
l All basic processes are started successfully.
l One particular process fails to be started.

System Impact
l If the notification says that the board is powered on successfully, no service is affected.
l If the notification says that starting some basic process fails or times out, the related
service cannot be used and the board is reset.

3-13

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Handling Suggestion
1. In the Fault Management window, view details of the notification and handle it
according to the power-on status:
l Power-on succeeded: No handling is required.
l Power-on timed out, go to Step 2.
l Power-on failed, go to Step 2.
2. Check whether the board has loaded a correct version.
l Yes: Contact ZTE for help.
l No: Go to Step 3.

Note:
Version numbers of boards within an NE must be identical.

3. Reload a correct version for the board. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.1.23 5448 Environment Parameters Set Fail

Notification Message
l Notification code: 5448
l Notification name: Environment parameters set fail
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
l PDU is abnormal.
l The board is abnormal.

System Impact
Configured environment parameters cannot get valid, but no service is affected.

Handling Suggestion
1. Unplug/plug the 485-connection line. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 2.
2. Replace the 485-connection line. Then check whether the notification disappears.
l Yes: End notification handling.

3-14

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

l No: Go to Step 3.
3. Replace the board. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.1.24 5715 PP2S Source Has Switched

Notification Message
l Notification code: 5715
l Notification name: PP2S source has switched
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
The Pulse Per 2 Seconds (PP2S) source handoff occurs among the PP2S at the system
side, the PP2S at the GPS receiver and the PP2S at the 1588 synchronization clock.

System Impact
Multicast time depends on whether the PP2S comes from the receiver, the system and the
1588 synchronization clock.

Handling Suggestion
No handling is required.

3.1.25 5718 Two Master Clock Ports Is Directly Connected

Notification Message
l Notification code: 5718
l Notification name: Two master clock ports is directly connected
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
The network port in the synchronous Ethernet is configured as a master clock, and the two
network ports configured as master clocks are directly interconnected.

System Impact
l If the notification is normal, no service is affected.
l If the notification is caused by a networking error, the remote end cannot obtain the
clock.

3-15

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Handling Suggestion
1. Chech whether the remote end refuses to restore the clock from the local port.
l Yes: In normal cases, no handling is required.
l No: If a networking error occurs, go to Step 2.
2. Reconfigure the port type. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Reconnect the wires. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.1.26 5720 The CDM Data Was Covered

Notification Message
l Notification code: 5720
l Notification name: The CDM data was covered
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
The information in the left CDM board and the right CDM board is inconsistent.

System Impact
None

Handling Suggestion
No handling is required.

3.1.27 5762 The Board Is Selecting Clock Base

Notification Message
l Notification code: 5762
l Notification name: The board is selecting clock base
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
During the manual selection of a reference, if the system is processing the previous
operation and the operation result is not given, the system masks this selection and
simultaneously reports this notification to the user.

3-16

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

System Impact
The reference cannot be selected manually.

Handling Suggestion
Wait until the last execution is over, that is, select the reference after an execution result
notification is given. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.1.28 5763 There Is No Valid Reference of the Clock Board to Be

Selected
Notification Message
l Notification code: 5763
l Notification name: There is no valid reference of the clock board to be selected.
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
The clock generator has no available reference for manual selection because the reference
is not configured or there is no externally accessed reference.

System Impact
The system probably fails to obtain the required clock, thus leading to abnormal processing
related to the clock.

Handling Suggestion
Select a reference again after the valid reference is accessed or configured. Then check
whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.1.29 5764 Lock Timeout When Manual Selecting Clock Reference

Notification Message
l Notification code: 5764
l Notification name: Lock timeout when manual selecting clock reference
l Severity: Warning
l Alarm type: Equipment alarm

3-17

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Probable Cause
After the command is carried out to manually select a reference, the selected reference is
valid, but the clock generator does not enter the locked status for a long time.

System Impact
The system probably fails to obtain the required clock, thus leading to abnormal processing
related to the clock.

Handling Suggestion
Run the command again to select a reference manually. Then check whether the
notification disappears.

l Yes: End notification handling.

l No: Contact ZTE for help.

3.1.30 5765 Lock the Wrong Base When Manual Selecting Clock
Reference
Notification Message
l Notification code: 5765
l Notification name: Lock the wrong base when manual selecting clock reference
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
After the command is carried out to select a reference manually, the system locks another
reference instead of the selected reference.

System Impact
The system probably fails to get the required clock, thus leading to abnormal processing
related to the clock.

Handling Suggestion
Run the command again to select a reference manually. Then check whether the
notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3-18

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

3.1.31 5766 Lock the Right Base When Manual Selecting Clock
Reference
Notification Message
l Notification code: 5766
l Notification name: Lock the right base when manual selecting clock reference
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
After the command of manually selecting a reference is carried out, the system locks the
selected reference within a period.

System Impact
None

Handling Suggestion
No handling is required.

3.1.32 5767 The Manual Selecting Reference Command Is Useless

Because the Clock Board Is in Preheat Status
Notification Message
l Notification code: 5767
l Notification name: The manual selecting reference command is useless because the
clock board is in preheat status
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
Because the clock generator is being preheated, the system cannot query the validity of the
reference source and the status of the phase-locked loop. Therefore, the system cannot
respond to the command of manually selecting a reference.

System Impact
None

Handling Suggestion
After preheating of the clock daughter card is finished, check whether the notification
disappears.

3-19

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Yes: Select a reference manually. End notification handling.

l No: Contact ZTE for help.

3.1.33 5976 Download Version Failed

Notification Message
l Notification code: 5976
l Notification name: Download version failed
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
l The control-plane communication is abnormal, for example, the switching board is
abnormal or OMP is reset abnormally.
l The version file does not exist in the version package, and thus the version file of PP
does not exist on the hard disk of OMP.

System Impact
Downloading the version files fails. The version file of the board is missing. The board
cannot be powered on and provide related functions.

Handling Suggestion
1. Check the control-plane switching board on the same shelf where the OMP module is
located and see whether the switching board works normally.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Eliminate the problem of the control-plane switching board on the same shelf where
the OMP module is located. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Check whether there is an alarm about abnormal communication between a module
and the OMP module, or an alarm about abnormal control-plane communication
between the board and its owner module.
l Yes: Go to Step 4.
l No: Contact ZTE for help.
4. According to the detailed notification information, check whether the version files on
the OMP module are complete.
l Yes: Contact ZTE for help.
l No: Go to Step 5.
5. In the Terminal window, run the LOAD APTPKG command to reload and activate
the version package, and run the ENABLE PKG command to validate the version
package. Then check whether the notification disappears.
l Yes: End notification handling.

3-20

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

l No: Contact ZTE for help.

3.1.34 5977 Running Version Not Match With Database

Configuration
Notification Message
l Notification code: 5977
l Notification name: Running version not match with database configuration
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
l When an active OMP or active standalone board is started from OMM, version
configuration on OMM is not consistent with the database.
l When a standby OMP or standby standalone board is started locally, the running
version is not consistent with configuration of the active OMP or standalone board.

System Impact
The running version of the board is not consistent with board configuration, and thus some
board functions may be missing or abnormal.

Handling Suggestion
1. Check whether the basic version and dependent version of OMP are consistent with
the version configured in the database.
l Yes: Contact ZTE for help.
l No: Go to Step 2.

Note:
l In the Terminal window, run the SHOW RUNPKG command to query the running
version.
l In the Terminal window, run the SHOW DFTPKG command to query the default
version package of the OMP module.

2. In the Terminal window, run the LOAD APTPKG command to reload and activate
version package, and run the ENABLE PKG command to make the version package
take effect. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Check whether any problem exists in the communication between the foreground and
the background.

3-21

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Yes: Go to Step 4.
l No: Go to Step 5.
4. Eliminate the problem in the communication between the foreground and the
background, and restart the OMP module. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Go to Step 5.
5. Check whether the version file exists in the board or whether it is normal.
l Yes: Go to Step 6.
l No: Contact ZTE for help.
6. In the Terminal window, run the SET BOOTMODE command to set the OMP start
mode, modify Boot Mode to OMM (boot from DHCP server), load the version package
from the OMM, and restart the OMP module. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.1.35 5978 Boottype Different With Configure

Notification Message
l Notification code: 5978
l Notification name: Boottype different with configure
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
l A boot failure triggers automatic shift of the booting mode in the BOOT phase.
l After the version gets valid, the boot type is changed to "boot from local".

System Impact
The current boot mode is inconsistent with that expected by the user.

Handling Suggestion
1. Confirm whether it is required to adjust the current booting mode.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Set the booting mode according to the requirement. Then check whether the
notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3-22

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

3.1.36 5979 Execute Version File Failed

Notification Message
l Notification code: 5979
l Notification name: Execute version file failed
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
l The version file is damaged.
l The version file attribute is incorrect and it is not executable.

System Impact
Executing the version file fails. The board cannot be powered on and provide related
functions.

Handling Suggestion
1. In the Terminal window, run the RESET NORMAL command to restart the board.
Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 2.
2. According to the detailed notification information, identify the reason for the version
file execution failure and check whether the loaded version package is correct.
l Yes: Contact ZTE for help.
l No: Go to Step 3.
3. In the Terminal window, run the LOAD APTPKG command to reload and activate the
version package, and run the ENABLE PKG command to make the version package
take effect. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.1.37 5980 Match Version Failed

Notification Message
l Notification code: 5980
l Notification name: Match version failed
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
l The corresponding version package is not activated.

3-23

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l The version file does not exist in the version package.

System Impact
The version file is missing. The board cannot be powered on and provide related functions.

Handling Suggestion
1. In the Terminal window, run the SHOW RUNPKG command to query the running
version, and check whether this version package is activated.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. In the Terminal window, run the ACT APTPKG command to activate the version
package including this file, run the ENABLE PKG command to make the version
package take effect. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. According to the detailed notification information, check whether the file exists in the
corresponding version package.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. In the Terminal window, run the LOAD APTPKG command to reload and activate the
version package, run the ENABLE PKG command to make the version package take
effect. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.1.38 5981 Special Firmware Version Load Information

Notification Message
l Notification code: 5981
l Notification name: Special firmware version load information
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
Special firmware version load information

System Impact
The special firmware device does not run normally.

Handling Suggestion
1. Check whether the corresponding firmware version exists.
l Yes: Go to Step 3.

3-24

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

l No: Go to Step 2.
2. Download the firmware version, power on the device, and reload the version. Then
check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Restart the firmware. Then check whether the notification disappears.
l Yes: Go to Step 4.
l No: Contact ZTE for help.
4. Replace the hardware and reload the version. Then check whether the firmware
device runs normally.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.1.39 5982 Patch Operation Failed

Notification Message
l Notification code: 5982
l Notification name: Patch operation failed
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
The operation on the hot patch fails.

System Impact
The hot patch cannot operate properly.

Handling Suggestion
According to the detailed notification information, record the corresponding hot patch, and
contact ZTE for help.

3.1.40 5983 Write Back Version Information

Notification Message
l Notification code: 5983
l Notification name: Write back version information
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
Write back version starting and finishing notification.

3-25

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
None

Handling Suggestion
It only means the system enters the version writing back flow. No handling is required.

3.1.41 5984 Check Version Information

Notification Message
l Notification code: 5984
l Notification name: Check version information
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
Version check starting and finishing notification.

System Impact
None

Handling Suggestion
It only means the system enters the version check flow. No handling is required.

3.1.42 5985 Synchronize Version Information

Notification Message
l Notification code: 5985
l Notification name: Synchronize version information
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
l Version synchronization starts.
l Version synchronization ends successfully.
l Version synchronization is in progress.
l Establishing an FTP connection with the partner fails. Synchronization ends.
l Querying the database fails. Synchronization ends.
l Version synchronization ends unsuccessfully.

3-26

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

System Impact
Version file synchronization on the active/standby OMP or standalone board fails. This
possibly causes inconsistency or incompleteness of the version files on the active and
standby boards, and thus the system has potential dangers.

Handling Suggestion
1. According to the synchronization information in the detailed notification information,
choose to perform the following steps as appropriate:
l Version synchronization is completed: No handling is required.
l The remote board is not powered on: Synchronization is not required.
l Synchronization has not started, go to Step 2.
l Synchronization fails, go to Step 2.
l Obtaining file records fails during the synchronization process: Contact ZTE for
help.
2. Initiate synchronization again. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.1.43 6720 Notice of Power-on Status of C51 Board/ Board Soft

Reset
Notification Message
l Notification code: 6720
l Notification name: Notice of power-on status of C51 board/ Board soft reset
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
The C51 board is powered on or reset successfully.

System Impact
None

Handling Suggestion
No handling is required.

3.1.44 7492 The Master OMP Power On

Notification Message
l Notification code: 7492
l Notification name: The master OMP power on

3-27

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
The master OMP power on successfully.

System Impact
None

Handling Suggestion
No handling is required.

3.1.45 8000 Loading Data Failed

Notification Message
l Notification code: 8000
l Notification name: Loading data failed
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
Loading data fails.

System Impact
l The system cannot be powered on.
l Configuration data cannot be loaded properly.

Handling Suggestion
Reload the data. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.1.46 8007 Saving Database Files(.zdb) Failed

Notification Message
l Notification code: 8007
l Notification name: Saving database files(.zdb) failed
l Severity: Major
l Alarm type: Processing error alarm

3-28

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Probable Cause
l The disk (flash) is full.
l The disk was not formatted or damage.
l I/O busy.
l There was no free memory in database.

System Impact
Loading data failed after the system is restarted, which causes unsuccessful power-on.

Handling Suggestion
1. Check whether there is any alarm about a disk damage.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Replace the disk. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Check whether the disk is used up.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Check whether the database has enough memory.
l Yes: Contact ZTE for help.
l No: Go to Step 5.
5. Check whether the I/O busy.
l Yes: Go to Step 6.
l No: Contact ZTE for help.
6. Try to save the data again later. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.1.47 8512 Sync Failed From Master to Slave

Notification Message
l Notification code: 8512
l Notification name: Sync failed from master to slave
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
l The active and standby boards are not compatible.
l Compressing files on the active board fails.
l Extracting files on the standby board fails.
l The table capacity on the standby board overflows.

3-29

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
l Data on the active and standby boards is inconsistent.
l Active/Standby changeover data is lost.

Handling Suggestion
1. Check whether the switching board works normally.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Restore the switching board to normal. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Check whether the communication between the active and standby boards is normal.
l Yes: Go to Step 5.
l No: Go to Step 4.
4. Restore the communication between the active and standby boards to normal. Then
check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 5.
5. Check whether the active and standby boards can be powered on successfully.
l Yes: Go to Step 7.
l No: Go to Step 6.
6. Power on the active and standby boards. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Go to Step 7.
7. Check whether numerous messages are accumulated on the active and standby
boards.
l Yes: Go to Step 8.
l No: Contact ZTE for help.
8. Process the accumulated messages and restore the active and standby boards to
normal. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.1.48 8769 Sync Failed Between CPU

Notification Message
l Notification code: 8769
l Notification name: Sync failed between CPU
l Severity: Major
l Alarm type: Processing error alarm

3-30

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Probable Cause
l The table structure is inconsistent during data synchronization.
l Loading data fails after synchronization.

System Impact
Data on different boards is inconsistent.

Handling Suggestion
1. Check whether the table structure is consistent.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Replace the version. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Restart the system. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.1.49 8770 Loading Data Failed After Sync

Notification Message
l Notification code: 8770
l Notification name: Loading data failed after sync
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
Loading data fails.

System Impact
The data is incorrect.

Handling Suggestion
1. Replace the ZDB file and reload it. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 2.
2. Restart the system. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3-31

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

3.1.50 8771 Sync Failed by FTP

Notification Message
l Notification code: 8771
l Notification name: Sync failed by FTP
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
FTP data synchronization fails.

System Impact
The data is inconsistent with the ZDB file transferred through FTP.

Handling Suggestion
1. Replace the ZDB file and reload it. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 2.
2. Restart the system. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.1.51 9024 Configuration Change Notification Failed

Notification Message
l Notification code: 9024
l Notification name: Configuration change notification failed
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
Sending the configuration change notification message fails.

System Impact
None

Handling Suggestion
No handling is required.

3-32

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

3.2 10000~99999
3.2.1 10048 Insufficient Memory
Notification Message
l Notification code: 10048
l Notification name: Insufficient memory
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
The memory is not enough.

System Impact
None

Handling Suggestion
No handling is required.

3.2.2 10049 DLL Registration Failed

Notification Message
l Notification code: 10049
l Notification name: DLL registration failed
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
l DLL files are missing in the version package.
l The version is incompatible.

System Impact
Power-on fails.

Handling Suggestion
1. According to the version file name and function name, check whether the
corresponding DLL files exist in the version package.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Check whether the versions of the DLL files in the version package are consistent.

3-33

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Yes: Contact ZTE for help.

l No: Go to Step 3.
3. Keep the versions of the DLL files in the version package consistent. Then check
whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.3 10050 Get Lock Timeout

Notification Message
l Notification code: 10050
l Notification name: Get Lock Timeout
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
Getting the lock times out.

System Impact
Getting the lock times out.

Handling Suggestion
No handling is required.

3.2.4 10051 Transaction Commit Timeout

Notification Message
l Notification code: 10051
l Notification name: Transaction commit timeout
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
Submitting the transaction times out.

System Impact
None

Handling Suggestion
No handling is required.

3-34

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

3.2.5 10304 SCCP GT Translation Is Failed

Notification Message
l Notification code: 10304
l Notification name: SCCP GT translation is failed
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
l The GT number contained in the signaling message is not configured locally.
l The subsystem in the GT translation result is not configured locally or this subsystem
is unavailable.
l The destination office direction in the GT translation result is unreachable.

System Impact
This service fails. Frequent GT translation failures probably lead to CPU overload.

Handling Suggestion
1. Check whether the GT in this notification has been configured.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Add the GT configuration. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Backup the data configuration, current alarms, history alarms and history notifications
of the local end and the opposite end, then contact ZTE for help.

3.2.6 10305 NID Is Not Configured

Notification Message
l Notification code: 10305
l Notification name: NID is not configured
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
During NID translation based on the American standard SCCP, NID is not configured in
the database.

System Impact
This service fails. If this notification appears frequently, the CPU may be overloaded.

3-35

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Handling Suggestion
1. Check whether the NID translation indicated by this notification is configured.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Check configuration data planning, and accordingly add ISNI NID translation data.
Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Backup the data configuration, current alarms, history alarms and history notifications
of the local end and the opposite end, then contact ZTE for help.

3.2.7 10306 NID Translation Is Failed

Notification Message
l Notification code: 10306
l Notification name: NID translation is failed
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
The database NID translation fails during the NID translation in American SCCP coding
mode.

System Impact
This service fails. If this notification appears frequently, the CPU may be overloaded.

Handling Suggestion
1. Check whether the ISNI NID translation data specified in the notification is correct.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Check configuration data planning, and accordingly modify ISNI NID translation data.
Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Backup the data configuration, current alarms, history alarms and history notifications
of the local end and the opposite end, then contact ZTE for help.

3.2.8 10307 The ISNI Constrained Route Information Is Repeated

Notification Message
l Notification code: 10307

3-36

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

l Notification name: The ISNI constrained route information is repeated

l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
During NID translation based on American standard SCCP, there are duplicate NIDs in the
NID list in ISNI forced route information, and the duplicate NIDs are local NIDs.

System Impact
This service fails. If this notification appears frequently, the CPU may be overloaded.

Handling Suggestion
Backup the data configuration, current alarms, history alarms and history notifications of
the local end and the opposite end, then contact ZTE for help.

3.2.9 10308 ISNI Does Not Support This Route Function

Notification Message
l Notification code: 10308
l Notification name: ISNI does not support this route function
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
During NID translation based on the American standard SCCP, the route type indicator in
the message is incorrect or is not supported.

System Impact
This service fails. If this notification appears frequently, the CPU may be overloaded.

Handling Suggestion
Backup the data configuration, current alarms, history alarms and history notifications of
the local end and the opposite end, then contact ZTE for help.

3.2.10 10309 Fail to Prompt NID Route

Notification Message
l Notification code: 10309
l Notification name: Fail to prompt NID route
l Severity: Minor
l Alarm type: Communication alarm

3-37

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Probable Cause
Processing the routing indication fails during the NID translation in American SCCP coding
mode because of too long NID list of the routing indication.

System Impact
This service fails. If this notification appears frequently, the CPU may be overloaded.

Handling Suggestion
Backup the data configuration, current alarms, history alarms and history notifications of
the local end and the opposite end, then contact ZTE for help.

3.2.11 10310 Wrong Message Type Use ISNI Function

Notification Message
l Notification code: 10310
l Notification name: Wrong message type use ISNI function
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
A non-XUDT message uses the ISNI function during the NID translation in American SCCP
coding mode.

System Impact
This service fails. If this notification appears frequently, the CPU may be overloaded.

Handling Suggestion
Backup the data configuration, current alarms, history alarms and history notifications of
the local end and the opposite end, then contact ZTE for help.

3.2.12 11072 LAPD Alarm Information

Notification Message
l Notification code: 11072
l Notification name: LAPD alarm information
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l EMD initialization fails.

3-38

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

l MCC initialization fails.

l Obtaining JID fails.
l Requesting memory fails.
l Requesting shared memory fails.
l Creating a queue fails.
l HDLC chip initialization fails.
l PP connection table initialization fails.
l MCS channel bandwidth table initialization fails.
l LAPD fails to obtain database configuration.
l Obtaining an HDLC channel fails.
l Adding an HDLC channel fails.
l Deleting an HDLC channel fails.
l Querying PP connection fails.
l The LAPD link is broken.
l Adding an HDLC channel succeeds.

System Impact
The signaling processes cannot work. The service fails this time.

Handling Suggestion
Backup the data configuration, current alarms, history alarms and history notifications of
the local end and the opposite end, then contact ZTE for help.

3.2.13 11073 LAPD Initial HDLC Failed

Notification Message
l Notification code: 11073
l Notification name: LAPD initial HDLC failed
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l The HDLC chip has some problem.
l There are some errors in the port configuration of the board.

System Impact
LAPD power-on fails.

Handling Suggestion
1. Check whether the port is configured as T1 or E1.
l Yes: Go to Step 3.
l No: Go to Step 2.

3-39

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

2. Configure the port to E1 or T1. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.
3. Replace the board. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.14 11330 Fail to Obtain Configuration Information From the

Database or Fail to Register Configuration Changing Notify
Notification Message
l Notification code: 11330
l Notification name: Fail to obtain configuration information from the database or fail to
register configuration changing notify
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
l The module where the DTI unit belongs to operates improperly.
l There are some errors in the configuration.

System Impact
The related link is out of service.

Handling Suggestion
Contact ZTE for help.

3.2.15 11331 Fail to Initialize MTP2

Notification Message
l Notification code: 11331
l Notification name: Fail to initialize MTP2
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
l Initializing the EMD fails.
l Initializing the MCC fails.
l Obtaining the JID fails.
l Applying for memory fails.
l Applying for shared memory fails.

3-40

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

l Creating a queue fails.

l HDLC chip initialization fails.
l PP connection table initialization fails.
l MCS channel bandwidth table initialization fails.
l Configuration data is incorrect.
l Deleting all HDLC channels after system restart fails.
l Deleting all EMD queues after system restart fails.

System Impact
The related link is out of service.

Handling Suggestion
Contact ZTE for help.

3.2.16 11332 Fail to Add or Delete HDLC Channel

Notification Message
l Notification code: 11332
l Notification name: Fail to add or delete HDLC channel
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
l Obtaining an HDLC channel fails.
l Adding an HDLC channel fails.
l Deleting an HDLC channel fails.
l Querying PP connection fails.
l Adding an HDLC succeeds.

System Impact
The related link is out of service.

Handling Suggestion
Contact ZTE for help.

3.2.17 11333 MTP2 Initial HDLC Failed

Notification Message
l Notification code: 11333
l Notification name: MTP2 initial HDLC failed
l Severity: Minor

3-41

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Alarm type: Equipment alarm

Probable Cause
The HDLC chip has some problem or port type configuration is incorrect.

System Impact
MTP2 power-on fails.

Handling Suggestion
1. Check whether the port is configured as T1 or E1.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Configure the port to E1 or T1. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.
3. Replace the board. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.18 11584 MTP3 Link State Is Offline

Notification Message
l Notification code: 11584
l Notification name: MTP3 link state is offline
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
The link configured by the user is in offline state.

System Impact
The link in offline state cannot provide services.

Handling Suggestion
1. Check whether the link is set to the offline state.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Modify the link state to a non-offline state. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3-42

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

3.2.19 11840 M3UA User Office Status Change

Notification Message
l Notification code: 11840
l Notification name: M3UA user office status change
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
The state of the corresponding AS changes.

System Impact
A user in the corresponding office cannot send or receive messages.

Handling Suggestion
1. Check whether the SIO location of the corresponding user exists.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Check whether the corresponding AS is activated.
l Yes: Go to Step 3.
l No: Go to Step 4.
3. Deactivate/Activate the corresponding association. Then check whether the
notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.
4. Activate the corresponding association. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.20 12096 Fail to Get the Functional Configuration

Notification Message
l Notification code: 12096
l Notification name: Fail to get the functional configuration
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
The Sig process fails to obtain the configuration file.

3-43

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
The configuration function is missing.

Handling Suggestion
After updating the signaling configuration file, restart the board. Then check whether the
notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.21 12097 The File of Sig Config Updated

Notification Message
l Notification code: 12097
l Notification name: The file of sig config updated
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
The signaling configuration file is updated again.

System Impact
The signaling process cannot work.

Handling Suggestion
Restart all the boards where the signaling processes reside. Then check whether the
notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.22 12352 Fail to Allocate Memory

Notification Message
l Notification code: 12352
l Notification name: Fail to allocate memory
l Severity: Warning
l Alarm type: Equipment alarm

System Impact
Memory is insufficient.

3-44

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Probable Cause
The Sig process fails to obtain memory.

Handling Suggestion
Restart the board after adding more memory. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.23 12353 SIG Failed to Save Configuration

Notification Message
l Notification code: 12353
l Notification name: SIG failed to save configuration
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
Signal data failed to be saved.

System Impact
The configuration does not take effect after restart.

Handling Suggestion
Save the signaling data by manual. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.24 12609 SUA ASBuf Application Failure

Notification Message
l Notification code: 12609
l Notification name: SUA ASBuf application failure
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
Dynamically requesting memory fails during process power-on.

3-45

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
None

Handling Suggestion
Restart the board after adding more memory. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.25 13632 M2PA Link Congestion

Notification Message
l Notification code: 13632
l Notification name: M2PA link congestion
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
l The lower layer association is congested.
l There are too many upper-layer service messages, leading to link congestion.
l The links of this office are insufficient.
l Poor lower-layer link causes high retransmission rate of messages.

System Impact
Congestion may cause packet loss, call loss, or even link interruption.

Handling Suggestion
1. Check whether there is a related alarm of association congestion (alarm code:
8402688).
l Yes: Handle the alarm by referring to the corresponding handling suggestions.
l No: Go to Step 2.
2. Add other links for the office that this link is serving. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Replace the lower-layer link and check the physical connection line, thus improving
the transmission quality of the physical link. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3-46

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Related Alarm
2.3.22 8402688 Association Congested

3.2.26 13633 M2PA Processor Outage

Notification Message
l Notification code: 13633
l Notification name: M2PA processor outage
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
l The MTP3 layer of this end is faulty.
l Communication between the local M2PA and the local MTP3 fails.
l The processor at the opposite end is faulty.
l The fault of the processor at the local end or the opposite end is eliminated.

System Impact
The related link is out of service.

Handling Suggestion
1. Check whether the module where the links of this end belong to runs properly.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Check whether the module where the links of this end belong to this module is
restarting.
l Yes: The notification disappears after this module is powered on. End notification
handling.
l No: Contact ZTE for help.
3. Check whether the module where the links of the opposite end belong to runs properly.
l Yes: Contact ZTE for help.
l No: Contact the maintenance engineer at the remote end for handling.

3.2.27 13634 M2PA Link Buffer Allocate Fail

Notification Message
l Notification code: 13634
l Notification name: M2PA link buffer allocate fail
l Severity: Warning
l Alarm type: Processing error alarm

3-47

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Probable Cause
Dynamically requesting memory fails when the process is powered on or new link is added.

System Impact
The link that fails to request memory cannot be created.

Handling Suggestion
Restart the board after adding more memory. Then check whether the notification
disappears.

l Yes: End notification handling.

l No: Contact ZTE for help.

3.2.28 13888 ASP Status Changed

Notification Message
l Notification code: 13888
l Notification name: ASP status changed
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The ASP status changed.

System Impact
The state of the corresponding AS may be affected.

Handling Suggestion
1. In the Fault Management window, check all associations corresponding to the ASP in
AS configuration to see whether there exists any link interruption related alarm (alarm
code: 8402690).
l Yes: Handle the alarm by referring to the corresponding handling suggestions.
l No: Go to Step 2.

Note:

In the Terminal window, run the SHOW AS command to query all associations
corresponding to the ASP in AS configuration.

3-48

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

2. In the Terminal window, run the ASP ACTIVE command to activate this ASP. Then
check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Ask the maintenance personnel of the opposite end to check whether he/she has
performed some operations on the ASP.
l Yes: Contact the maintenance engineer at the remote end for handling.
l No: Contact ZTE for help.

Related Alarm
2.3.23 8402690 Association Broken

3.2.29 13889 AS Status Changed

Notification Message
l Notification code: 13889
l Notification name: AS status changed
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The AS status changed.

System Impact
The state of the office AS may be affected.

Handling Suggestion
1. In the Fault Management window, check all associations corresponding to the ASP in
AS configuration to see whether there exists any link interruption related alarm (alarm
code: 8402690).
l Yes: Handle the alarm by referring to the corresponding handling suggestions.
l No: Go to Step 2.

Note:

In the Terminal window, run the SHOW AS command to query all associations
corresponding to the ASP in AS configuration.

2. In the Terminal window, run the ASP ACTIVE command to activate this ASP. Then
check whether the notification disappears.

3-49

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Yes: End notification handling.

l No: Go to Step 3.
3. Ask the maintenance personnel of the opposite end to check whether he/she has per-
formed some operations on the ASP.
l Yes: Contact the maintenance engineer at the remote end for handling.
l No: Contact ZTE for help.

Related Alarm
2.3.23 8402690 Association Broken

3.2.30 13890 Sigtran Error Message Received

Notification Message
l Notification code: 13890
l Notification name: Sigtran error message received
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
An error message is received.

System Impact
Different errors may have different impacts on the system, for example, no impact, office
blocking, and service loss.

Handling Suggestion
1. In the Terminal window, run the SHOW AS command to check whether the Service
Mode of the two interconnected offices are consistent.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Modify the service mode of either office to make them consistent. Then check whether
the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. In the Terminal window, run the SHOW AS command to check whether the Usage
Tag of the AS at both interconnected ends are consistent.
l Yes: Go to Step 5.
l No: Go to Step 4.

3-50

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Note:
l If the local end is configured to the ASP, the opposite end must be configured to
the SGP, and vice versa.
l If the local end is configured to the IPSP client, the opposite end must be
configured to the IPSP server, and vice versa.

4. Modify the Usage Tag of the ASs at both ends, so that they comply with configuration
requirements. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 5.
5. In the Terminal window, run the ASP ACTIVE command to activate the ASP. Then
check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 6.
6. In the Terminal window, run the SHOW AS command to check whether the If Routing
Context exists at both interconnected ends.
l Routing context does not exist, go to Step 7.
l Routing context exists, go to Step 8.
7. Modify the Routing Context parameter to Routing context exists on the ASs at both
ends. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 8.
8. In the Terminal window, run the SHOW AS command to check whether the Routing
Context ID of the AS at both interconnected ends are consistent.
l Yes: Go to Step 10.
l No: Go to Step 9.
9. Modify the Routing Context ID parameter of the ASs at both ends to be identical.
Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 10.
10. In the Terminal window, run the SHOW AS command to check whether the ASP of
the local end is configured with a serving AS.
l Yes: Go to Step 12.
l No: Go to Step 11.
11. Configure an AS in the AS configuration for this ASP. Then check whether the
notification disappears.
l Yes: End notification handling.
l No: Go to Step 12.
12. Check whether the protocol versions used at both ends are the same.
l Yes: Contact ZTE for help.
l No: Go to Step 13.

3-51

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

13. Modify the protocol versions used at both end to make sure that they use the same
version. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.31 13891 Sigtran Notification Message Received

Notification Message
l Notification code: 13891
l Notification name: Sigtran notification message received
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
An AS-ASP state notification message is received.

System Impact
None

Handling Suggestion
1. In the Fault Management window, check all associations corresponding to the ASP in
AS configuration to see whether there exists any link interruption related alarm (alarm
code: 8402690).
l Yes: Handle the alarm by referring to the corresponding handling suggestions.
l No: Go to Step 2.

Note:
In the Terminal window, run the SHOW AS command to query all associations
corresponding to the ASP in AS configuration.

2. In the Terminal window, run the ASP ACTIVE command to activate the ASP again.
Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Confirm whether the opposite end performs some operations on the ASP.
l Yes: Contact the maintenance engineer at the remote end for handling.
l No: Contact ZTE for help.

3-52

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Related Alarm
2.3.23 8402690 Association Broken

3.2.32 14144 Association Establishment Failure

Notification Message
l Notification code: 14144
l Notification name: Association Establishment Failure
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
The SCTP association cannot be established.

System Impact
l If there are other available associations configured to the destination office, the
failure in establishing an association has no impact on services. In case of heavy
traffic, these available associations are probably congested, leading to call loss of
upper-layer services or decrease in the success rate of service access.
l If only this association is configured to the destination office, this destination office
may be unreachable. Users fail to transmit messages to and receive messages from
this office. This office cannot access services.

Handling Suggestion
1. In the Terminal window, run the SHOW SCTP command to check whether the Local
port and the Remote port are consistent, and check whether the Local IP address
and the Remote IP address are in the same network segment.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Modify the SCTP configuration, so that Local port and Remote port are consistent,
and Local IP address and Remote IP address are in the same network segment.
Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. In the Terminal window, run the SHOW SCTP command to check whether Application
Attribute of the SCTP association complies with configuration requirements. That is,
if the local end is configured as the SCTP client, the remote end must be the SCTP
server; if the local end is configured as the SCTP server, the remote end must be the
SCTP client.
l Yes: Go to Step 5.
l No: Go to Step 4.

3-53

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

4. Modify Application Attribute of the SCTP association, so that it complies with

configuration requirements. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 5.
5. Check local associations to see whether associations of different protocol types have
the same Local IP address and Local Port.
l Yes: Go to Step 6.
l No: Go to Step 7.
6. Modify Local IP address and Local Port of the associations of different protocol types.
Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 7.
7. Check whether the interface board addresses in protocol stack configuration at both
ends are in different network segments.
l Yes: Go to Step 8.
l No: Go to Step 9.
8. Modify the interface board addresses at both ends so that they are in the same network
segment. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 9.
9. Check whether the interface board address of the remote end can be pinged
successfully from the local end.
l Yes: Contact ZTE for help.
l No: Go to Step 10.
10. Replace the cable. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.33 14145 Restart the Association

Notification Message
l Notification code: 14145
l Notification name: Restart the association
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
l The opposite association is established immediately after disconnection.
l Because the physical link is unstable, the detecting time difference results in different
association status at both ends in short time. The association at the opposite end is
reestablished immediately.

3-54

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

System Impact
This has no impact on the system. Under the most unfavorable conditions, this association
is interrupted transiently. It will be recovered immediately.

Handling Suggestion
1. Ask the maintenance personnel at the opposite end to check the cause of association
disconnection and handle it.
2. Check whether the external ports of the interface board are available.
l Yes: Go to Step 4.
l No: Go to Step 3.
3. Replace the interface board. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 4.
4. Check whether there is a problem with the transmission line quality.
l Yes: Go to Step 5.
l No: Contact ZTE for help.
5. Replace the transmission line. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.34 14146 Dynamic Association Link Broken

Notification Message
l Notification code: 14146
l Notification name: Dynamic association link broken
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
A dynamic association is interrupted.

System Impact
The office may be unreachable, which leads to congestion of other available associations.

Handling Suggestion
No handling is required.

3.2.35 14148 One User of Share Association Is in Service

Notification Message
l Notification code: 14148

3-55

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Notification name: One user of share association is in service

l Severity: Major
l Alarm type: Communication alarm

Probable Cause
A shared association is activated.

System Impact
None

Handling Suggestion
No handling is required.

3.2.36 14149 One User of Share Association Is Out of Service

Notification Message
l Notification code: 14149
l Notification name: One user of share association is out of service
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
An upper-layer user of the shared association is out of service.

System Impact
Establishing an association fails, directly leading to the related upper-layer user link and
ASP being in incorrect status. This may affect the AS and the office status in different
configuration.

Handling Suggestion
No handling is required.

3.2.37 14150 Association Config Error

Notification Message
l Notification code: 14150
l Notification name: Association config error
l Severity: Major
l Alarm type: Communication alarm

3-56

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Probable Cause
The number of association streams is configured improperly or is not configured at the
SCTP layer.

System Impact
The association with wrong configuration will not enter the signaling data area.

Handling Suggestion
1. Modify the configuration of the incoming/outgoing association stream range. Then
check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 2.

Note:
The number of the incoming /outgoing streams of each protocol is as follows:
l M2PA: 2
l M2UA/SUA/M3UA/IUA: 2~17
l Other protocols: 1~7

2. Check whether the association is configured at the SCTP layer.

l Yes: Contact ZTE for help.
l No: Go to Step 3.
3. Configure the association at the SCTP layer. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.38 14151 SSM Malloc Memory Failure

Notification Message
l Notification code: 14151
l Notification name: SSM malloc memory failure
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
The process fails to request memory dynamically.

3-57

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
None

Handling Suggestion
Restart the board after adding more memory. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.39 14152 Dynamic Association Config Error

Notification Message
l Notification code: 14152
l Notification name: Dynamic association config error
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
A dynamic association is configured improperly.

System Impact
If the configuration is wrong, the association will not enter the data area of signaling.

Handling Suggestion
1. Check whether the remote IP address and port number are configured for the dynamic
association.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Delete the remote IP address and port number are configured for the dynamic
association. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Check whether the dynamic association is configured as a client.
l Yes: Go to Step 4.
l No: Go to Step 5.
4. Set the dynamic association to a server. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Go to Step 5.
5. Check whether the protocol type supported by the dynamic association is correct.
l Yes: Contact ZTE for help.
l No: Go to Step 6.

3-58

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

6. Set the protocol type of the dynamic association properly. Then check whether the
notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.40 17990 RPU Detected Board Down

Notification Message
l Notification code: 17990
l Notification name: RPU detected board down
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
The heartbeat of the EPU board is lost.

System Impact
The port of this board fails to function properly.

Handling Suggestion
1. Extract the board, and then insert the board securely. Then check whether the
notification disappears.
l Yes: End notification handling.
l No: Go to Step 2.
2. Turn on the ENUM switch to see whether this notification appears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.41 17992 Protocol State of the Port-Channel Member Interface

Is Down
Notification Message
l Notification code: 17992
l Notification name: Protocol state of the port-channel member interface is down
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
An aggregate member port in 8023AD mode detects that the protocol state is "down".

3-59

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
The upper layer services may be interrupted.

Handling Suggestion
1. Check whether the links in the link group have some problem.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Eliminate the link problems of the link group. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.42 18240 TCP RST Packets Received

Notification Message
l Notification code: 18240
l Notification name: TCP RST packets received
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
l The opposite end actively resets this TCP connection, and sends an RST message.
l The opposite end receives a wrong TCP connection, and replies an RST message.

System Impact
l The TCP server discards the received reset packet, and the server keeps in monitoring
state.
l The upper layer services of the server are not affected at all.

Handling Suggestion
1. In the Terminal window, enter IP Stack Mode, then run the PING command to check
whether there is serious packet loss in the physical link.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Troubleshoot the physical link failure. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3-60

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

3.2.43 18241 TCP Connection Closed

Notification Message
l Notification code: 18241
l Notification name: TCP connection closed
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
l Hardware failure. For example, the external interface on the local or remote device is
down, the intermediate switching device is down, or the transmission link fails.
l Bearer network failure. For example, the external interface on the local or remote
device fails, the intermediate device has a physical or routing problem, or the bearer
link fails.
l Configuration problem. For example, the route or interface address of the local or
remote device is changed.
l Device failure. For example, the control-plane communication within the NE of the
local or remote device is broken.

System Impact
The TCP link is disconnected. Services over TCP are all interrupted.

Handling Suggestion
1. In the Terminal window, enter IP Stack Mode, then run the PING command to check
whether there is serious packet loss in the physical link.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Troubleshoot the physical link failure. Then check whether the notification disappears.
l Yes: Go to Step 3.
l No: Contact ZTE for help.
3. In the Fault Management window, check whether the module to which the association
belongs has any control-plane communication exception alarm (alarm code: 8393985
and 8393988).
l Yes: Handle the alarm by referring to the corresponding handling suggestions.
l No: Go to Step 4.
4. Check whether the remote NE fails.
l Yes: Contact the maintenance personnel at the opposite end for handling.
l No: Contact ZTE for help.

Related Alarms
l 2.3.4 8393985 Control Plane Communication Abnormal Between Board and Its Home
Module

3-61

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l 2.3.7 8393988 Control Plane Communication Abnormal Between MP and OMP

3.2.44 18242 Failed to Verify MD5

Notification Message
l Notification code: 18242
l Notification name: Failed to verify MD5
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
MD5 verification is not set for the messages in the application layer.

System Impact
TCP discards received packets, and thus application layer communication fails.

Handling Suggestion
1. Check two ends of the application layer to see whether one of them is not set with
MD5 encryption.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Set with MD5 encryption for this end. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.45 18243 MD5 Message Error

Notification Message
l Notification code: 18243
l Notification name: MD5 Message Error
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
When the application layer transmits and receives messages, the MD5 keys set at both
ends are inconsistent.

System Impact
TCP discards received packets, and thus application layer communication fails.

3-62

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Handling Suggestion
1. Check both ends of the application layer to verify whether the MD5 keys set at both
ends are consistent.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Set the same MD5 keys at both ends of the application layer. Then check whether the
notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.46 18244 Socket Receive Buffer Occupancy Exceeded

Threshold
Notification Message
l Notification code: 18244
l Notification name: Socket receive buffer occupancy exceeded threshold
l Severity: Warning
l Alarm type: QoS alarm

Probable Cause
The receiving caching data of the socket queue has reached the threshold for generating
a notification.

System Impact
This results in upper-layer service error.

Handling Suggestion
Contact ZTE for help.

3.2.47 18245 Data in Socket Buffer Can Not Be Sent or Received in

120 Seconds
Notification Message
l Notification code: 18245
l Notification name: Data in socket buffer can not be sent or received in 120 seconds
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
The sending or receiving buffer of the socket is abnormal.

3-63

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
The socket is closed, and the corresponding communication is interrupted.

Handling Suggestion
Without manual interference, wait for the system to recover automatically. Wait about two
minutes, check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.48 18500 The Peer IP Address Is the Same as the Local IP

Address of the PPP Link
Notification Message
l Notification code: 18500
l Notification name: The peer IP address is the same as the local IP address of the
PPP link
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The local IP address configuration of the PPP link is the same as that of the remote end.

System Impact
The network communication is abnormal.

Handling Suggestion
1. Check whether the port is self-looped.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Cancel the self-loop. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Check the PPP link to see whether the IP address of the local end is consistent with
that of the remote end.
l Yes: Go to Step 4.
l No: Contact ZTE for help.
4. Set the PPP link IP address of one port to non-duplicate address. Then check whether
the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3-64

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

3.2.49 18501 Fail to Create the HDLC Channel

Notification Message
l Notification code: 18501
l Notification name: Fail to create the HDLC channel
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
l The EPU board is configured to the T1 board. However, the time slot number of the
port exceeds 24.
l The service type of the E1 subunit corresponding to this port is not PPP.
l The configured port exceeds the maximum port number.
l The used E1 number exceeds the maximum E1 number.
l Invoking the lower layer interface fails.

System Impact
The PPP link is not generated.

Handling Suggestion
1. Check whether the board is configured to the T1 board.
l Yes: Go to Step 2.
l No: Go to Step 4.
2. Check whether the time slot number exceeds 24.
l Yes: Go to Step 3.
l No: Go to Step 4.
3. Modify the configuration and make sure that the time slot number is less than 24..
Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.
4. Check whether the configured service of the E1 subunit is PPP or not.
l Yes: Go to Step 6.
l No: Go to Step 5.
5. Modify the service type of the E1 sub unit to "PPP". Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Go to Step 6.
6. Check whether the port number exceeds the maximum port number.
l Yes: The configuration is invalid. Go to Step 7.
l No: Go to Step 8.
7. Delete this port. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 8.

3-65

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

8. Check whether the number of configured E1s exceeds the maximum number set by
the board.
l Yes: Go to Step 9.
l No: Contact ZTE for help.
9. Modify the E1 number. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.50 18502 Fail to Initialize the HDLC Chip

Notification Message
l Notification code: 18502
l Notification name: Fail to initialize the HDLC chip
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
HDLC chip initialization fails.

System Impact
l The IPE1 port cannot be generated.
l The PPP queue cannot be generated.

Handling Suggestion
1. Check whether all processes on the board are in working state.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Reset the board, reload and activate the version, and then check whether the board
can enter working state and be initialized successfully after power-on.
l Yes: End notification handling.
l No: Go to Step 3.
3. Check whether the data in R_PORTPARA is consistent with the port type configured
for the board.
l Yes: Go to Step 5.
l No: Go to Step 4.
4. Modify board configuration. Then power on the board, and check whether HDLC
initialization is successful.
l Yes: End notification handling.
l No: Go to Step 5.
5. Check whether the sub cards of the board operate properly.
l Yes: Go to Step 7.
l No: Go to Step 6.

3-66

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

6. Replace the sub cards with new ones, power on the board again, and check whether
HDLC initialization is successful.
l Yes: End notification handling.
l No: Go to Step 7.
7. Check whether there is any other HDLC related hardware failure alarm.
l Yes: Go to Step 8.
l No: Contact ZTE for help.
8. Replace related hardware, and check whether HDLC initialization is successful.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.51 18503 Fail to Create the Queue or Thread of PPP

Notification Message
l Notification code: 18503
l Notification name: Fail to create the queue or thread of PPP
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
Creating a task for receivign PPP packets fails.

System Impact
The PPP thread or queue cannot be created successfully.

Handling Suggestion
1. In the Fault Management window, check whether the board has any notification about
HDLC chip initialization failure.
l Yes: Handle it according to the relevant handling suggestion.
l No: Go to Step 2.
2. Check the board property and see whether the board supports PPP.
l Yes: Go to Step 4.
l No: Go to Step 3.
3. Replace the board with one that supports PPP. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Go to Step 4.
4. Check whether the EPU process is in working state.
l Yes: Contact ZTE for help.
l No: Go to Step 5.
5. Power on the board again and see whether the EPU works normally.
l Yes: End notification handling.
l No: Contact ZTE for help.

3-67

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Related Alarm
3.2.50 18502 Fail to Initialize the HDLC Chip

3.2.52 18504 The HDLC Channel Is Created Successfully

Notification Message
l Notification code: 18504
l Notification name: The HDLC channel is created successfully
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
The cause for the previous HDLC channel creation failure does not exist now. This
notification indicates that HDLC channel creation succeeds.

System Impact
None

Handling Suggestion
No handling is required.

3.2.53 18753 The Configuration of UID/HDLC/IPE1 in Database Is

Wrong
Notification Message
l Notification code: 18753
l Notification name: The configuration of UID/HDLC/IPE1 in database is wrong
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
l UID/HDLC/IPE1 configuration is incorrect.
l The internal link between OMP and ABPM is broken.

System Impact
The new configuration data is invalid.

Handling Suggestion
1. Check whether UID/HDLC configuration is correct.
l Yes: Go to Step 3.

3-68

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

l No: Go to Step 2.
2. Modify UID/HDLC configuration properly. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Check whether there is any alarm related to the internal link between OMP and ABPM.
l Yes: Handle the alarm by referring to the corresponding handling suggestions.
l No: Go to Step 4.
4. Check whether data synchronization is performed after data configuration.
l Yes: Record the current UID/HDLC configuration, and contact ZTE for help.
l No: Go to Step 5.
5. Wait for a while and retry the configuration. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Record the current UID/HDLC configuration, and contact ZTE for help.

3.2.54 18755 HDLC Status Changed

Notification Message
l Notification code: 18755
l Notification name: HDLC status changed
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
l The notification is given after an HDLC is created.
l The HDLC link is broken or restored.

System Impact
l If the HDLC is the last available HDLC in the corresponding UID binding, all services
on the UID are interrupted.
l If the HDLC is not the last available HDLC in the corresponding UID binding, the traffic
volume on the UID decreases.

Handling Suggestion
1. Check HDLC channel configuration and see whether the E1/T1 and timeslot used by
the HDLC are consistent with the configuration at the remote end.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Modify the local HDLC configuration according to the HDLC configuration at the remote
end. Then check whether the notification disappears.
l Yes: End notification handling.

3-69

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l No: Go to Step 3.
3. Check whether the physical connections are correct.
l Yes: Go to Step 5.
l No: Go to Step 4.
4. Adjust the physical connections properly so that they are consistent with the
configuration at both ends. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 5.
5. Check whether the E1/T1 wires have any quality problem.
l Yes: Go to Step 6.
l No: Record the packet sending/receiving statistics on the HDLC, and contact ZTE
for help.
6. Replace the E1/T1 cable. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Record the packet sending/receiving statistics on the HDLC, and contact ZTE
for help.

3.2.55 19008 Fail to Configure the ATM Port

Notification Message
l Notification code: 19008
l Notification name: Fail to configure the ATM port
l Severity: Minor
l Alarm type: Processing error alarm

Probable Causes
l When the ATM port is created, the port rate is higher than the rate limit of the physical
port.
l There is a PVC on the port when it is deleted.
l When the port rate is modified, the new rate is less than the sum of the rates of the
PVCs of this ATM port.

System Impact
PVC cannot be configured for this port, so the ATM fails to work properly.

Handling Suggestion
1. Make sure that the parameters of the port rate are correct. When the port is created,
the port rate should not exceed the maximum bandwidth of all ports. Check whether
the port rate exceeds the range.
l Yes: Go to Step 2.
l No: Go to Step 3.

The bandwidth range of each port (Unit: Kbit/s) is listed as follows.

3-70

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

l NP: 0~622,000
l Optical: 0~155,000
l IMA: 0~64,000
2. Set the bandwidth parameter again. Then check whether you can create the port
successfully.
l Yes: End alarm handling.
l No: Go to Step 3.
3. When you modify the port rate, the rate you set should not be lower than the bandwidth
used.
l Yes: Go to step 4.
l No: Go to step 5.
4. Re-configure a bandwidth parameter greater than the currently used one. Check
whether you can modify the port rate successfully.
l Yes: End alarm handling.
l No: Go to step 5.
5. Delete the port. Meanwhile, verify that this is no PVC configuration on the port.
l Yes: Contact ZTE for help.
l No: Go to Step 6
6. Delete the PVC on the port. Then check whether you can delete the port successfully.
l Yes: End alarm handling.
l No: Contact ZTE for help.

3.2.56 19264 Fail to Operate IMA Group

Notification Message
l Notification code: 19264
l Notification name: Fail to operate IMA group
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
This notification appears when the OMM fails to initiate an IMA group-related operation
(such as adding, deleting or modifying the group). In general, the reason is that the group
parameters are incorrect when the operation is initiated.

System Impact
The specified configuration does not take effect on the corresponding board.

Handling Suggestion
1. Check whether the parameters related to the initiated operation are correct.
l Yes: Go to step 3.
l No: Go to step 2.
2. Check whether you can modify the parameters and perform the operation successfully.

3-71

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Yes: End notification handling.

l No: Go to Step 3.
3. Check whether the operation steps are legal.
l Yes: Go to step 4.
l No: Contact ZTE for help.
4. Perform the operation by following the legal steps. Check whether the notification
appears.
l Yes: Contact ZTE for help.
l No: End notification handling.

3.2.57 19265 Fail to Operate the Link of the IMA Group

Notification Message
l Notification code: 19265
l Notification name: Fail to operate the link of the IMA Group
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
This notification appears when the OMM fails to initiate an IMA link-related operation (such
as adding, deleting or modifying the link). In general, the reason is that the link parameters
are incorrect when the operation is initiated.

System Impact
The specified configuration does not take effect on the corresponding board.

Handling Suggestion
1. Check whether the parameters related to the initiated operation are correct.
l Yes: Go to step 3.
l No: Go to step 2.
2. Check whether you can modify the parameters and perform the operation successfully.
l Yes: End notification handling.
l No: Go to Step 3.
3. Check whether the operation steps are legal.
l Yes: Go to step 4.
l No: Contact ZTE for help.
4. Perform the operation by following the legal steps. Check whether the notification
appears.
l Yes: Contact ZTE for help.
l No: End notification handling.

3-72

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

3.2.58 19777 APS Switchover Happens

Notification Message
l Notification code: 19777
l Notification name: APS switchover happens
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
l Optical interface is faulty. LOS/SF/SD alarms might exist.
l During inter-board backup, any of the following events occurs.
à Input clock loss
à Internal HW/LVDS alarm
à Internal media plane port alarm
à ENUM open
à Board reset (the board where the working optical interface is located)
l Switching is initiated by remote end.
l In recovery mode, fault recovery time in optical interface exceeds 5 minutes.
l APS switching request/clearance is initiated by NMS.

System Impact
During the switching, the port is interrupted for 10 to 50 ms and a few packets are
discarded, but the 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.
Related alarms:
1792 SDH/SONET:Loss of Signal

3.2.59 20554 Failed to Add the Route

Notification Message
l Notification code: 20554
l Notification name: Failed to add the route
l Severity: Warning
l Alarm type: Processing error alarm

3-73

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Probable Cause
Adding a UID or PPP route fails.

System Impact
This has an impact on transmitting and receiving messages.

Handling Suggestion
1. Check whether the destination IP address of the route is already used by another route.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Configure another destination IP address for the route. Then check whether the route
can be added successfully.
l Yes: End notification handling.
l No: Go to Step 3.
3. Check whether the number of routes reaches the maximum capacity.
l Yes: Go to Step 4.
l No: Contact ZTE for help.
4. Expand the route capacity, and check whether the route can be added successfully.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.60 20571 Failed to Perform Offline Configuration

Notification Message
l Notification code: 20571
l Notification name: Failed to perform offline configuration
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
Offline configuration fails.

System Impact
Configuration data is lost.

Handling Suggestion
1. Check whether the configuration data is correct.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Modify the configuration data properly, and check whether offline configuration is
successful.

3-74

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

l Yes: End notification handling.

l No: Contact ZTE for help.

3.2.61 20802 There Is an IP Address Conflict With Another System

on the Subnet
Notification Message
l Notification code: 20802
l Notification name: There is an IP address conflict with another system on the subnet
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
l The IP address (including the virtual address in the same network segment) of this
network interface is the same as that of another host computer in the local network.
l A loop exists in the opposite switch that is connected to this network interface.
l No VLANs are divided or VLAN division is incorrect.

System Impact
There is some device in the network whose IP address is the same as that of the alarming
interface. If the system continues using this interface, services on the interface will be
unavailable, and connections over the interface will be discontinuous. In addition, ARP
entries of other devices in the LAN may be frequently updated.

Handling Suggestion
1. Check whether there is some device in the network whose IP address is the same as
that of the alarming interface.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Modify either IP address. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.62 20803 There Is a MAC Address Conflict With Another System

on the Subnet
Notification Message
l Notification code: 20803
l Notification name: There is a MAC address conflict with another system on the subnet
l Severity: Minor
l Alarm type: Communication alarm

3-75

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Probable Cause
l The MAC address of the local network interface is the same as that in the associated
network.
l A loop exists in the opposite switch that is connected to this network interface.
l No VLANs are divided or VLAN division is incorrect.

System Impact
Layer-2 devices forward packets according to the destination MAC addresses within the
packets. If MAC addresses conflict in the network, layer-2 devices cannot learn MAC
addresses properly, and thus packet sending/receiving becomes discontinuous.

Handling Suggestion
1. Check whether the same MAC address as that of this port is configured in the network.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Modify either MAC address. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.63 20805 ARP Detecting Failed

Notification Message
l Notification code: 20805
l Notification name: ARP detecting failed
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
If the port ARP detection function is enabled, CE periodically uses the IP address in the
ARP entry as a request IP to send an ARP request. If no response is received from the
remote end within a specified period, this notification is given.

System Impact
Communication may be interrupted.

Handling Suggestion
1. Check whether the IP address of the interconnected device is configured properly.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Modify the IP address of the interconnected device properly. Then check whether the
notification disappears.

3-76

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

l Yes: End notification handling.

l No: Go to Step 3.
3. Check whether the physical link is normal.
l Yes: Go to Step 5.
l No: Go to Step 4.
4. Eliminate the physical link failure. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 5.
5. Check whether the swtich VLAN configuration is wrong.
l Yes: Go to Step 6.
l No: Contact ZTE for help.
6. Modify the switch VLAN conguration properly. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.64 20806 ARP Detecting Reply Is Different From Static ARP

Notification Message
l Notification code: 20806
l Notification name: ARP detecting reply is different from static ARP
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
If the port ARP detection function is enabled, CE periodically uses the IP address in
the static ARP entry as a request IP to send a static ARP detection request packet.
If the source MAC address in the response returned from the remote ARP within a
specified period is inconsistent with the MAC address in the local static ARP entry, or the
encapsulated VLAN is inconsistent, this notification is given.

System Impact
Communication may be interrupted.

Handling Suggestion
1. Check whether the MAC address of the interconnected device is configured properly.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Modify the MAC address of the interconnected device properly. Then check whether
the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Check whether the switch VLAN configuration is wrong.

3-77

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Yes: Go to Step 4.
l No: Contact ZTE for help.
4. Modify the switch VLAN configuration properly. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.65 21059 RIP Neighbor Configuration Error

Notification Message
l Notification code: 21059
l Notification name: RIP Neighbor Configuration Error
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
When a neighbor is added, the neighbor address does not match the interface address.

System Impact
The dynamic route that is expected to be obtained by the neighbor cannot be established.

Handling Suggestion
1. Check whether the configured RIP neighbor address and the interface address are in
the same network segment.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Check whether the configured neighbor address is a network number or broadcast
address.
l Yes: Go to Step 3.
l No: Contact ZTE for help.
3. Re-configure the neighbor address properly. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.66 21060 RIP Interface Authentication Error

Notification Message
l Notification code: 21060
l Notification name: RIP Interface Authentication Error
l Severity: Minor
l Alarm type: Processing error alarm

3-78

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Probable Cause
If the interface needs authentication and the authentication code is incorrect, this
notification is given.

System Impact
RIP packets cannot be received correctly.

Handling Suggestion
1. Check whether the authentication types configured at both ends are consistent.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Modify the authentication types at both ends to be consistent. Then check whether
the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Check whether the authentication keys are consistent.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Modify the authentication keys at both ends to be consistent. Then check whether the
notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.67 21065 Incompatible RIP Version Number

Notification Message
l Notification code: 21065
l Notification name: Incompatible RIP Version Number
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
The version number of the remote interface is not consistent with that of the local interface.

System Impact
RIP packets cannot be received correctly.

Handling Suggestion
1. Check whether the version number of the remote interface is consistent with that of
the local interface.
l Yes: Contact ZTE for help.

3-79

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l No: Go to Step 2.
2. Modify the version numbers at both ends to be consistent. Then check whether the
notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.68 21329 LSDB Overflow

Notification Message
l Notification code: 21329
l Notification name: LSDB overflow
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
LSDB overflows.

System Impact
Adding an LSA fails, and the LSDB cannot be synchronized.

Handling Suggestion
Reduce the number of LSAs by configuring route aggregation. Then check whether the
notification disappears.

l Yes: End notification handling.

l No: Contact ZTE for help.

3.2.69 21330 Configuration of OSPF Mismatched

Notification Message
l Notification code: 21330
l Notification name: Configuration of OSPF mismatched
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
Configuraion information does not match, and thus the OSPF protocol is abnormal.

System Impact
Routes cannot be learned and calculated properly.

3-80

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Handling Suggestion
According to the detailed notification information, view related configuration and modify
related configuration items consistently. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.70 21573 BGP Gets TCB Fail on Active Connection

Notification Message
l Notification code: 21573
l Notification name: BGP Gets TCB Fail on Active Connection
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
A TCP link with the remote neighbor cannot be established.

System Impact
A BGP session cannot be established proactively.

Handling Suggestion
1. Check whether the adjacent office configuration at the remote end is correct.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Modify the adjacent office configuration at the remote end properly. Then check
whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Check whether a route exists from the local end to the adjacent office of the remote
end.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Modify the configuration so that a reachable route is available to the adjacent office of
the remote end. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.71 21584 Neighbor Hold Timer Expired

Notification Message
l Notification code: 21584

3-81

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Notification name: Neighbor Hold Timer Expired

l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
l The physical link is interrupted.
l The TCP connection is interrupted.

System Impact
The BGP session is disconnected.

Handling Suggestion
1. Check whether the network configuration is correct.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Modify the network configuration properly. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Check whether the network connection and topology are correct.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Restore the network connection and topology to normal. Then check whether the
notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.72 21585 BGP Interface Down and Neighbor Link Broken

Notification Message
l Notification code: 21585
l Notification name: BGP Interface down and Neighbor Link Broken
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
A message is received which says that the local interface is down.

System Impact
The BGP neighbor session on the interface is disconnected.

3-82

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Handling Suggestion
1. Check whether the interface state is active.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Check whether the interface is connected to the network.
l Yes: Contact ZTE for help.
l No: Go to Step 3.
3. Connect the interface to the network and activate it. Then check whether the
notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.73 21837 Fail to Add Dynamic Route

Notification Message
l Notification code: 21837
l Notification name: Fail to add dynamic route
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
Forwarding table overflow causes the failure in adding a dynamic route.

System Impact
The dynamic route is lost.

Handling Suggestion
1. Query routes on RPU and see whether there is unused IP interface or static route.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Delete redundant static routes and interface IP addresses. Then check whether the
notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. On the opposite router, reduce its distributed routing information quantity with route
aggregation as much as possible.
l Yes: End notification handling.
l No: Go to Step 4.
4. Record the detailed configuration of the interface IP address and static route, as well
as the dynamic route information. Contact ZTE for help.

3-83

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

3.2.74 22336 MAC Addresses Conflict Among the Ports of the Office
Notification Message
l Notification code: 22336
l Notification name: MAC addresses conflict among the ports of the office
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
The default MAC address of the port conflicts with the MAC address of another port in the
same office.

System Impact
Communication between the two ports with MAC conflict cannot be established.

Handling Suggestion
1. Check whether the MAC address of an existing port conflicts with the one you want to
configure.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Allocate another MAC address to this port. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.75 22593 ISIS Hello Message Authentication Failure

Notification Message
l Notification code: 22593
l Notification name: ISIS Hello Message Authentication Failure
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
Hello message authentication modes or keys configured on the routers of the two ends
are inconsistent.

System Impact
The packet is ignored after hello message authentication failure. The local router cannot
synchronize the LSDB with the corresponding router.

3-84

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Handling Suggestion
1. Check whether the protocol authentication modes (MD5/TEXT) of the local and remote
routers are consistent.
l Yes: Go to Step 3.
l No: Go to Step 2.

Note:
l According to System ID in the detailed notification information, find the remote
router. Run the show running config command respectively on the local and
remote routers to display device operation configuration.
l In the ISIS protocol instance configuration, check whether the protocol
authentication modes (MD5/TEXT) of the local and remote routers are consistent.

2. Modify the protocol authentication modes at both ends to be consistent. Then check
whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Check whether the protocol packet authentication keys of the local and remote routers
are consistent.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Modify the protocol authentication modes at both ends to be consistent. Then check
whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.76 22594 ISIS LSP Message Authentication Failure

Notification Message
l Notification code: 22594
l Notification name: ISIS LSP Message Authentication Failure
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
LSP message authentication modes or keys configured on the routers of the two ends are
inconsistent.

3-85

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
The packet is ignored after LSP authentication failure. The local router cannot synchronize
the LSDB with the corresponding router.

Handling Suggestion
1. Check whether the protocol authentication modes (MD5/TEXT) of the local and remote
routers are consistent.
l Yes: Go to Step 3.
l No: Go to Step 2.

Note:
l According to System ID in the detailed notification information, find the remote
router. Run the show running config command respectively on the local and
remote routers to display device operation configuration.
l In the ISIS protocol instance configuration, check whether the protocol
authentication modes (MD5/TEXT) of the local and remote routers are consistent.

2. Modify the protocol authentication modes at both ends to be consistent. Then check
whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Check whether the protocol packet authentication keys of the local and remote routers
are consistent.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Modify the protocol authentication modes at both ends to be consistent. Then check
whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.77 22595 ISIS SNP Message Authentication Failure

Notification Message
l Notification code: 22595
l Notification name: ISIS SNP Message Authentication Failure
l Severity: Minor
l Alarm type: Processing error alarm

3-86

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Probable Cause
SNP message authentication modes or keys configured on the routers of the two ends are
inconsistent.

System Impact
The packet is ignored after SNP authentication failure. The local router cannot synchronize
the LSDB with the corresponding router.

Handling Suggestion
1. Check whether the protocol authentication modes (MD5/TEXT) of the local and remote
routers are consistent.
l Yes: Go to Step 3.
l No: Go to Step 2.

Note:
l According to System ID in the detailed notification information, find the remote
router. Run the show running config command respectively on the local and
remote routers to display device operation configuration.
l In the ISIS protocol instance configuration, check whether the protocol
authentication modes (MD5/TEXT) of the local and remote routers are consistent.

2. Modify the protocol authentication modes at both ends to be consistent. Then check
whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Check whether the protocol packet authentication keys of the local and remote routers
are consistent.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Modify the protocol authentication modes at both ends to be consistent. Then check
whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.78 22597 Abnormal Message Is Received

Notification Message
l Notification code: 22597
l Notification name: Abnormal Message is Received
l Severity: Minor

3-87

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Alarm type: Processing error alarm

Probable Cause
An incorrect protocol packet is received.

System Impact
The incorrect packet is discard.

Handling Suggestion
1. Check whether the lower layer link is abnormal.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Restore the lower layer link. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Check whether there is any illegal system in the network.
l Yes: Go to Step 4.
l No: Contact ZTE for help.
4. Eliminate the illegal systems in the network. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.79 22598 Routers With Conflicting System ID Exist in Network

Notification Message
l Notification code: 22598
l Notification name: Routers with Conflicting System ID Exist in Network
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
In protocol stack configuration mode, System ID is incorrect in the ISIS instance
configuration.

System Impact
Normal ISIS neighbor relationship cannot be established between adjacent routers whose
system IDs conflict.

3-88

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Handling Suggestion
1. Run the show running config command on the router to check whether the system ID
in the ISIS instance configuration conflicts with other system IDs.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Modify the system ID in the instance. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.80 26176 The Currently Locked Reference of the Clock Board

Has Been Changed
Notification Message
l Notification code: 26176
l Notification name: The currently locked reference of the clock board has been
changed
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
The reference currently locked by the clock has changed.

System Impact
The system cannot get required clock, causing abnormal processing related to the clock.

Handling Suggestion
No handling is required.

3.2.81 26178 Clock Work Mode Is Changed

Notification Message
l Notification code: 26178
l Notification name: Clock work mode is changed
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
The working mode of the clock generator has changed.

3-89

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
The system cannot get required clock, causing abnormal processing related to the clock.

Handling Suggestion
No handling is required.

3.2.82 28231 Router ID Not Configured for OSPFv3

Notification Message
l Notification code: 28231
l Notification name: Router ID not configured for OSPFv3
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
No router ID is configured for OSPFv3.

System Impact
An OSPF instance cannot be created.

Handling Suggestion
Set an IPv4 interface address (a loopback interface address is recommended) as a router
ID, and create OSPFv3 again. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.83 28233 Configuration of OSPFv3 Mismatched

Notification Message
l Notification code: 28233
l Notification name: Configuration of OSPFv3 Mismatched
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
Due to configuration inconsistency, routes cannot be learned or calculated.

System Impact
Routes cannot be learned and calculated properly.

3-90

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Handling Suggestion
According to the detailed notification information, view related configuration and modify
related configuration items consistently. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.84 28993 Setting SCTP Primary Path Failed

Notification Message
l Notification code: 28993
l Notification name: Setting SCTP primary path failed
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
The remote address of the SCTP primary path set on the application layer does not exist
in the SCTP path list.

System Impact
SCTP cannot send traffic in the path expected by the user.

Handling Suggestion
Modify the local SCTP association configuration. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

Note:
l At the remote end of the association, run the SHOW SCTP command to view the
remote SCTP association configuration, and record local IP address and bearer
protocol type.
l At the local end of the association, select a proper MML command according to bearer
protocol type recorded at the remote end to modify the local association configuration
as planned.
à SIP: SET SIPSCTP
à H248: SET H248SCTP
à DIAMETER: SET DIMSCTP
à IUA: SET IUASCTP

3-91

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

3.2.85 28994 A Switchover Is Made From One SCTP Link to Another

Notification Message
l Notification code: 28994
l Notification name: A switchover is made from one SCTP link to another
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
Due to a link problem, the retransmission occurred three times in the association, or the
quality of the next hop deteriorated, leading to the association is handed over to another
next hop. When the previously allocated next hop was recovered, the association was
handed back to this next hop.

System Impact
The problem with link communication quality may lead to uneven load sharing of the
association.

Handling Suggestion
1. Refer to previous notifications and see whether this notification a revertive switching
notification after link recovery.
l Yes: No handling is required.
l No: Go to Step 2.
2. Check the link of the previous next hop based on the notification to see whether there
is a problem with the intermediate device.
l Yes: Go to Step 3.
l No: Contact ZTE for help.
3. Eliminate the problem of the intermediate device. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.86 28998 SCTP Congested for a Long Time

Notification Message
l Notification code: 28998
l Notification name: SCTP congested for a long time
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
The SCTP has been congested for a long time.

3-92

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

System Impact
Because the SCTP is disconnected, the corresponding communication is interrupted.

Handling Suggestion
Without manual interference, wait for the system to recover automatically. Wait two
minutes, check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.87 28999 The Number of Static Associations in One Module

Are Out of Range
Notification Message
l Notification code: 28999
l Notification name: The number of static associations in one module are out of range
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The number of the associations configured for a module is out of range.

System Impact
Out-of-range associations cannot be established.

Handling Suggestion
Delete out-of-range static associations. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.88 29000 SCTP Receive Buffer Occupancy Exceeded Threshold

Notification Message
l Notification code: 29000
l Notification name: SCTP receive buffer occupancy exceeded threshold
l Severity: Warning
l Alarm type: QoS alarm

Probable Cause
The receiving caching data of the SCTP has reached the threshold for generating a
notification.

3-93

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
This results in upper-layer service error.

Handling Suggestion
1. Query the alarming threshold value of the SCTP queue to see whether this threshold
is set too low.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Set the threshold again. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.89 29001 Association Link Broken

Notification Message
l Notification code: 29001
l Notification name: Association link broken
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
l The association is in offline state.
l The association link is broken for other reasons (see the detailed notification
information).

System Impact
The association is in offline state, and alarm information is shielded.

Handling Suggestion
1. Check whether the association is in offline state.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Restore the association. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. According to the detailed notification information, check for other reasons for the link
break and restore the association. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3-94

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

3.2.90 29760 DNS Server Unreachable

Notification Message
l Notification code: 29760
l Notification name: DNS server unreachable
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
The DNS server does not respond. It is possibly because the link is broken or the DNS
server is down.

System Impact
DNS functions cannot be used.

Handling Suggestion
1. Check whether the link between the NE where the DNS client resides and the DNS
server is available (tested with the Ping command).
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Eliminate the physical link fault. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Check the status of the DNS server to see whether it is listening to port 53.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Eliminate the DNS server fault. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.91 30016 Ethernet Link OAM Event

Notification Message
l Notification code: 30016
l Notification name: Ethernet link OAM event
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The link quality or the MAC transmission frame quality of the corresponding port is poor.

3-95

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
Some services may be lost.

Handling Suggestion
1. Check whether the contact of fiber receiving direction is poor or the network cable of
the electrical interface is loose.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Unplug and then plug the fiber or the network cable. Then check whether the
notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Plug the network cable into a new peer port on the same device, and duplicate all
configuration of the old port to this new port except the physical port number. Then
check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.92 30528 The Result of Starting PD Task

Notification Message
l Notification code: 30528
l Notification name: The result of starting PD task
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
l The configured PD task fails to be started due to incorrect parameter configuration.
l Because the task pool is full, the task cannot be started.

System Impact
The PD task cannot be started this time, which does not affect services.

Handling Suggestion
1. Check whether the PD task is initiated successfully.
l Yes: No handling is required.
l No: Go to Step 2.
2. Check whether the IP addresses of the local end and the opposite end are configured
correctly.
l Yes: Go to Step 4.
l No: Go to Step 3.

3-96

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

3. Modify the IP addresses of the local end and the opposite end, and check whether the
PD task is initiated successfully.
l Yes: End notification handling.
l No: Go to Step 4.
4. Check whether the destination address is the address of this NE.
l Yes: Go to Step 6.
l No: Go to Step 5.
5. Modify the destination IP address, and check whether the PD task is initiated
successfully.
l Yes: End notification handling.
l No: Go to Step 4.
6. Check whether there is a route.
l Yes: Contact ZTE for help.
l No: Go to Step 7.
7. Configure a route and check the link status, and then check whether the PD task is
initiated successfully.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.93 30787 ATCA FRU Power On

Notification Message
l Notification code: 30787
l Notification name: ATCA FRU Power On
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
ATCA FRU is powered on and works normally.

System Impact
None

Handling Suggestion
It is a normal power-on flow. No handling is required.

3.2.94 30790 ATCA FRU Power Off

Notification Message
l Notification code: 30790
l Notification name: ATCA FRU Power Off
l Severity: Warning

3-97

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Alarm type: Equipment alarm

Probable Cause
ATCA FRU power-off completed.

System Impact
None

Handling Suggestion
It is a normal power-off flow. No handling is required.

3.2.95 30794 ATCA FRU Communication Lost

Notification Message
l Notification code: 30794
l Notification name: ATCA FRU Communication Lost
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The communication between ATCA FRU and CMM is lost.

System Impact
If the notification is reported frequently, CMM may lose control of the ATCA FRU, which
may increase the risk of device damage.

Handling Suggestion
1. Check whether the IPMB link is normal.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore the IPMB link. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.96 30800 ATCA FRU Communication Regain

Notification Message
l Notification code: 30800
l Notification name: ATCA FRU Communication Regain
l Severity: Warning

3-98

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

l Alarm type: Communication alarm

Probable Cause
The communication between the ATCA FRU and the CMM recovers to normal.

System Impact
None

Handling Suggestion
No handling is required.

3.2.97 30812 IPMB State Change(IPMB-A Enable\IPMB-B Disable)

Notification Message
l Notification code: 30812
l Notification name: IPMB state change(IPMB-A enable\IPMB-B disable)
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
Path A of the IPMB bus is enabled, path B of the IPMB bus is disabled.

System Impact
None

Handling Suggestion
This notification seldom occurs. If it appears, contact the technical support personnel of
ZTE for proper handling.

3.2.98 30813 IPMB State Change(IPMB-A Disable\IPMB-B Enable)

Notification Message
l Notification code: 30813
l Notification name: IPMB state change(IPMB-A disable\IPMB-B enable)
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
Path A of the IPMB bus is disabled, path B of the IPMB bus is enabled.

3-99

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
None

Handling Suggestion
This notification seldom occurs. If it appears, contact the technical support personnel of
ZTE for proper handling.

3.2.99 30814 IPMB State Change(IPMB-A Enable\IPMB-B Enable)

Notification Message
l Notification code: 30814
l Notification name: IPMB state change(IPMB-A enable\IPMB-B enable)
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
Both path A and path B of the IPMB bus are opened.

System Impact
None

Handling Suggestion
It is a normal flow. No handling is required.

3.2.100 30815 HOST CPU Reset Event

Notification Message
l Notification code: 30815
l Notification name: HOST CPU Reset Event
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
l Hearbeat detection is lost.
l CMM sends a reset command.
l Pressing the reset button on the panel resets the CPU.
l The hardware watchdog program resets the CPU.
l A global reset occurs.

3-100

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

System Impact
Some functions on the board are unavailable.

Handling Suggestion
1. Check whether the board load is proper.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore the board load to normal. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.101 30816 The Board Reset

Notification Message
l Notification code: 30816
l Notification name: The board reset
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
l CMM sends a reset command.
l Pressing the reset button on the panel resets the CPU.
l The hardware watchdog program resets the CPU.
l A global reset occurs.

System Impact
Temporarily, the functions of the board are unavailable.

Handling Suggestion
View detailed notification information and record the reason for reset. Contact the ZTE
technical support personnel for handling.

3.2.102 30817 BIOS Start-up Inform

Notification Message
l Notification code: 30817
l Notification name: BIOS Start-up Inform
l Severity: Warning
l Alarm type: Equipment alarm

3-101

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Probable Cause
BIOS startup detection notification.

System Impact
None

Handling Suggestion
Handle it according to the details of the notification. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.103 30818 IPMB Linkstate Event

Notification Message
l Notification code: 30818
l Notification name: IPMB linkstate event
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
Hardware exception.

System Impact
Communication may time out.

Handling Suggestion
1. Check whether the link is normal.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore the link to normal. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.104 30820 BIOS Memory Inform

Notification Message
l Notification code: 30820
l Notification name: BIOS Memory Inform
l Severity: Warning

3-102

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

l Alarm type: Equipment alarm

Probable Cause
The BIOS reports a memory related notification.

System Impact
None

Handling Suggestion
Handle it according to the details of the notification. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.105 30821 Power on Failed Inform

Notification Message
l Notification code: 30821
l Notification name: Power on failed inform
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
Hardware exception or software exception.

System Impact
The board fails to be powered on, and thus the services on the board fail.

Handling Suggestion
Handle it according to the details of the notification. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.106 30822 No RAID Detected

Notification Message
l Notification code: 30822
l Notification name: No RAID detected
l Severity: Warning

3-103

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Alarm type: Equipment alarm

Probable Cause
The hard disk does not make the RAID configuration or its RAID configuration is deleted.

System Impact
The RAID function does not take effect.

Handling Suggestion
1. Check whether the hard disk does not need to make RAID configuration.
l Yes: End notification handling.
l No: Go to Step 2.
2. Configure the hard disk to the RAID mode. Check whether the notification is cleared.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.107 30823 High Disk Partition Utilization

Notification Message
l Notification code: 30823
l Notification name: High disk partition utilization
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
The space utilization ratio of the hard disk partition is too high.

System Impact
The board cannot function properly.

Handling Suggestion
Clear the hard disk partition or increase the hard disk capacity. Check whether the
notification is cleared.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.108 30824 High Memory Utilization

Notification Message
l Notification code: 30824

3-104

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

l Notification name: High memory utilization

l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
The memory utilization ratio is too high.

System Impact
The board cannot operate properly.

Handling Suggestion
1. Add the memory and restart the board. Check whether the notification is cleared.
l Yes: End notification handling.
l No: Go to Step 2.
2. Replace the board and check whether the notification is cleared.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.109 30825 Less Than 4 NIC Ports Recognised

Notification Message
l Notification code: 30825
l Notification name: Less than 4 NIC ports recognised
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
The number of NIC ports that can be recognized by the system is less than four.

System Impact
The NIC port is lost.

Handling Suggestion
No handling is required.

3.2.110 30826 NIC Port Statistics Error Detected

Notification Message
l Notification code: 30826
l Notification name: NIC port statistics error detected

3-105

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
An error occurs to the NIC port statistics.

System Impact
The NIC port cannot operate properly.

Handling Suggestion
No handling is required.

3.2.111 30827 FC Controller Statistics Error Detected

Notification Message
l Notification code: 30827
l Notification name: FC controller statistics error detected
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
An error occurs to the statistics of the FE controller chip.

System Impact
The FE controller cannot operate properly.

Handling Suggestion
No handling is required.

3.2.112 30828 ATCA FRU Present

Notification Message
l Notification code: 30828
l Notification name: ATCA FRU present
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
The ATCA Field Replaceable Unit (FRU) is present.

3-106

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

System Impact
None

Handling Suggestion
1. Check whether the FRU is installed properly.
l Yes: End notification handling.
l No: Go to Step 2.
2. Remove the FRU and verify that the FRU is offline. Check whether the notification is
cleared.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.113 30829 ATCA FRU Absent

Notification Message
l Notification code: 30829
l Notification name: ATCA FRU absent
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
The ATCA FRU is offline.

System Impact
None

Handling Suggestion
1. Check whether the FRU is removed normally.
l Yes: End notification handling.
l No: Go to Step 2.
2. Reinstall the FRU and make sure that the FRU is present. Check whether the
notification is cleared.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.114 30830 SMART Parameter Error

Notification Message
l Notification code: 30830
l Notification name: SMART parameter error
l Severity: Warning

3-107

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Alarm type: Equipment alarm

Probable Cause
An error occurs to the Self Monitoring Analysis and Reporting Technology (SMART)
parameter.

System Impact
The hard disk does not operate properly.

Handling Suggestion
1. Check whether the hard disk is faulty.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Replace the hard disk and check whether the notification is cleared.
l Yes: End notification handling.
l No: Go to Step 3.
3. Replace the board and check whether the notification is cleared.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.115 30831 Fault Memory Isolation

Notification Message
l Notification code: 30831
l Notification name: Fault memory isolation
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
Fault Memory is isolated by BIOS.

System Impact
None

Handling Suggestion
1. Check whether the memory is error.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Replace the error memory. Then check whether the notification still appears.
l Yes: Go to Step 3.
l No: End notification handling.

3-108

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

3. Replace the board. Then check whether the notification still appears.
l Yes: Contact ZTE for help.
l No: End notification handling.

3.2.116 31041 ACL Query Table Is Unavailable

Notification Message
l Notification code: 31041
l Notification name: ACL query table is unavailable
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
l Requesting an ACL query table fails due to short of memory.
l Constructing an ACL query table fails.

System Impact
Functions (such as packet filtering, policy routing, and IPSEC) corresponding to the ACL
query table are unavailable.

Handling Suggestion
1. Check whether too much memory of the board is used.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Modify memory configuration to reduce the memory occupied by other modules. Then
check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Modify ACL configuration to reduce the number of ACL entries. Then check whether
the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.117 31296 PTP Failed to Cancel Slave Port

Notification Message
l Notification code: 31296
l Notification name: PTP failed to cancel slave port
l Severity: Minor
l Alarm type: Equipment alarm

3-109

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Probable Cause
PTP fails to cancel the slave port.

System Impact
There may be two slave ports in the system at the same time.

Handling Suggestion
No handling is required.

3.2.118 31554 The IP Address Which Will be Allocated to the Client

by DHCP Server Confilcts With the IP Address Existed on
the Network
Notification Message
l Notification code: 31554
l Notification name: The IP address which will be allocated to the client by DHCP server
confilcts with the IP address existed on the network
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
The DHCP server detects that the IP address allocated by the DHCP server to the client
conflicts with an existing IP address in the network.

System Impact
The client cannot obtain the IP address.

Handling Suggestion
1. Check whether the IP address configured on OMM conflicts with any existing IP
address in the network and whether any illegal user is using the IP address.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Reconfigure the IP address. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.2.119 41794 Fail to Operate TC Link

Notification Message
l Notification code: 41794

3-110

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

l Notification name: Fail to operate TC link

l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
This notification appears when the OMM fails to initiate a TC link-related operation (such
as adding, deleting or modifying the link). In general, the reason is that the link parameters
are incorrect when the operation is initiated.

System Impact
The specified configuration does not take effect on the corresponding board.

Handling Suggestion
1. Check whether the parameters related to the initiated operation are correct.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Modify the parameters and perform the operation again. Then check whether the
notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Check whether the operation steps are legal.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Perform the operation by following legal steps. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3 10000000~9999999999
3.3.1 16778560 MGW Unable to Work and Withdrawal Service
Notification Message
l Notification code: 16778560
l Notification name: MGW unable to work and withdrawal service
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
l Dynamic Management change the service status of MGW.
l Link detected that MGW is not in service status.

3-111

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Received MGW service change message.

System Impact
The MGW may not be able to process calls.

Handling Suggestion
Handle the problem according to the detailed notification information. Then check whether
the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.2 16778562 MSCe/MSC Server (H248 Request) Does Not

Receive the Response Message From Gateway
Notification Message
l Notification code: 16778562
l Notification name: MSCe/MSC Server (H248 request) does not receive the response
message from gateway
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
The H248 request message except the notify command does not receive any response
from the gateway.

System Impact
It probably results in call failure of this gateway.

Handling Suggestion
1. Check whether the connection to the gateway is normal.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore the connection with the gateway to normal. Then check whether the
notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3-112

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

3.3.3 16778565 H248S Process Data Area Allocates Failed

Notification Message
l Notification code: 16778565
l Notification name: H248S Process data area allocates failed
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
Data area allocation of the H248S process fails.

System Impact
H248S process fails to power on.

Handling Suggestion
Add more memory. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.4 16779080 GTP-C Create Socket Fail

Notification Message
l Notification code: 16779080
l Notification name: GTP-C create socket fail
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
GTP-C create socket fail.

System Impact
The system cannot receive SRVCC messages from interface Sv.

Handling Suggestion
1. The system will retry to create socket.
2. Try to reboot the SMP module.

3-113

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

3.3.5 16781632 TUP RSV 2 Times Hardware Oriented Group

Blocking
Notification Message
l Notification code: 16781632
l Notification name: TUP RSV 2 Times Hardware Oriented Group Blocking
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
In the duration required by Timer 30, the HGB (Hardware Failure Oriented Group Blocking
message) has been received twice.

System Impact
The circuit group is blocked and unavailable.

Handling Suggestion
1. Check whether the circuits at both ends are available.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Restore the circuits to be available. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.
3. Check whether PCM and trunk group configuration is correct.
l Yes: Go to Step 5.
l No: Go to Step 4.
4. Modify PCM and trunk group configuration properly. Then check whether the
notification disappears.
l Yes: End notification handling.
l No: Go to Step 5.
5. According to the office type of the remote end, identify the reason for receiving HGB
and handle it properly. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.6 16781633 TUP Wait CLF Expiry Stop Send CFL

Notification Message
l Notification code: 16781633
l Notification name: TUP Wait CLF Expiry Stop Send CFL
l Severity: Warning
l Alarm type: Processing error alarm

3-114

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Probable Cause
Timer 5 expires when the TUP is waiting for CLF (Clear-Forward signal) after sending the
first CFL (Call-Failure signal). The TUP stops sending the CFL message.

System Impact
The CIC is probably blocked.

Handling Suggestion
1. Check whether CIC is in normal state.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore CIC to normal. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.7 16781634 TUP Wait RLG Expiry Stop Send CLF

Notification Message
l Notification code: 16781634
l Notification name: TUP Wait RLG Expiry Stop Send CLF
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
Timer 7 expires when the TUP is waiting for RLG (Release Guard signal) after sending the
first CLF (Clear Forward signal). The TUP stops sending the CLF message.

System Impact
The CIC is probably blocked.

Handling Suggestion
1. Check whether CIC is in normal state.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore CIC to normal. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3-115

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

3.3.8 16781635 TUP Wait BLA Expiry

Notification Message
l Notification code: 16781635
l Notification name: TUP Wait BLA Expiry
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
Timer 13 expires when the TUP is waiting for BLA (Blocking Acknowledgement signal).
Afterwards, the TUP sends a BLO message every one minute. If it has not received the
BLA message for four minutes, the TUP stops sending the BLO message.

System Impact
The CIC is probably blocked.

Handling Suggestion
1. Check whether CIC is in normal state.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore CIC to normal. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.9 16781636 TUP Wait UBA Expiry

Notification Message
l Notification code: 16781636
l Notification name: TUP Wait UBA Expiry
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
Timer 16 expires when the TUP is waiting for UBA (Unblocking Acknowledgement
message). Afterwards, the TUP sends a UBL message every one minute. If it has not
received the UBA message for four minutes, the TUP stops sending the UBL message.

System Impact
Because unblocking CIC fails, the unblocking operation fails.

3-116

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Handling Suggestion
1. Check whether circuits are in normal state.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore the circuits to normal. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.10 16781637 TUP Timer 19 Delay to Send RSC

Notification Message
l Notification code: 16781637
l Notification name: TUP Timer 19 Delay to Send RSC
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
Timer 19 expires when the TUP is waiting for CLF (Clear Forward signal) or RLG
(Release-Guide signal) after sending the first RSC (Circuit Reset signal). Afterwards, the
TUP sends an RSC message every one minute. If it has not received the CLF or RLG for
four minutes, the TUP stops sending the RSC message.

System Impact
The CIC is probably blocked.

Handling Suggestion
1. Check whether circuits are in normal state.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore the circuits to normal. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.11 16781638 TUP Timer 22 Delay to Send GRS

Notification Message
l Notification code: 16781638
l Notification name: TUP Timer 22 Delay to Send GRS
l Severity: Warning
l Alarm type: Processing error alarm

3-117

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Probable Cause
Timer 22 expires when the TUP is waiting for a circuit GRA (Group Reset
Acknowledgement message). Afterwards, the TUP sends a GRS message very one
minute. If it has not received the GRA message for four minutes, the TUP stops sending
the GRS message.

System Impact
The circuit group is probably blocked.

Handling Suggestion
1. Check whether circuits are in normal state.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore the circuits to normal. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.12 16781639 TUP Timer 27 Delay to Send MGB

Notification Message
l Notification code: 16781639
l Notification name: TUP Timer 27 Delay to Send MGB
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
Timer 27 expires when the TUP is waiting for MBA (Maintenance Oriented Group
Blocking-Acknowledgement message). Afterwards, the TUP sends a MGB message
every one minute. If it has not received the MBA message for four minutes, the TUP
stops sending the MGB message.

System Impact
The circuit group is probably blocked.

Handling Suggestion
1. Check whether circuits are in normal state.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore the circuits to normal. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3-118

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

3.3.13 16781640 TUP Timer 29 Delay to Send MGU

Notification Message
l Notification code: 16781640
l Notification name: TUP Timer 29 Delay to Send MGU
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
Timer 29 expires when the TUP is waiting for MUA (Maintenance Oriented Group
Unblocking-Acknowledgement message). Afterwards, the TUP sends an MGU message
every one minute. If it has not received the MUA message for four minutes, the TUP
stops sending the MGU message.

System Impact
The circuit group fails to be unblocked.

Handling Suggestion
1. Check whether circuits are in normal state.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore the circuits to normal. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.14 16781641 TUP Timer 33 Delay to Send HGB

Notification Message
l Notification code: 16781641
l Notification name: TUP Timer 33 Delay to Send HGB
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
Timer 33 expires when the TUP is waiting for HBA (Hardware Failure Oriented Group
Blocking-Acknowledgement message). Afterwards, the TUP sends an HGB message
every one minute. If it has not received the HBA message for four minutes, the TUP
stops sending the HGB message.

System Impact
The faulty circuit group fails to be blocked.

3-119

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Handling Suggestion
1. Check whether circuits are in normal state.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore the circuits to normal. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.15 16781642 TUP Timer 35 Delay to Send HGU

Notification Message
l Notification code: 16781642
l Notification name: TUP Timer 35 Delay to Send HGU
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
Timer 35 expires when the TUP is waiting for HUA (Hardware Failure Oriented Group
Unblocking-Acknowledgement message). Afterwards, the TUP sends an HGU message
every one minute. If it has not received the HUA message for four minutes, the TUP stops
sending the HGU message.

System Impact
The circuit group fails to be unblocked.

Handling Suggestion
1. Check whether circuits are in normal state.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore the circuits to normal. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.16 16781643 TUP: Signal Block CIC by Local Switch During

T19 Expiry
Notification Message
l Notification code: 16781643
l Notification name: TUP: Signal Block CIC by Local Switch During to T19 Expiry
l Severity: Warning
l Alarm type: Processing error alarm

3-120

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Probable Cause
The TUP stops sending the RSC message when it has not received the CLF (Clear Forward
signal) or the RLG (Release-Guard signal) for five minutes.

System Impact
The CIC is probably blocked.

Handling Suggestion
1. Check whether local configuration is correct.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Modify local configuration properly. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Ask the remote office's maintenance personnel to check whether its CIC is in normal
state.
l Yes: Contact ZTE for help.
l No: Contact the maintenance engineer at the remote end for handling.

3.3.17 16781647 TUP Circuit Continuity Recheck Succeed

Notification Message
l Notification code: 16781647
l Notification name: TUP circuit continuity recheck succeed.
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
The TUP continuity rechecking succeeds.

System Impact
None

Handling Suggestion
No handling is required.

3.3.18 16781648 TUP Circuit Continuity Recheck Failed

Notification Message
l Notification code: 16781648
l Notification name: TUP circuit continuity recheck failed

3-121

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
The TUP Continuity rechecking fails.

System Impact
The continuity check fails. If a call requiring to perform the continuity check, this call fails,
too.

Handling Suggestion
1. Check whether tone resources and trunk resources on the gateway are available.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore tone and trunk resources to be available. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.19 16781649 TUP Blocking CIC After Sent Hardware Group

Blocking Message Twice
Notification Message
l Notification code: 16781649
l Notification name: TUP start blocking CIC after sending hardware group blocking
message twice.
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
After the TUP sends the hardware oriented circuit group blocking signal twice, it starts
blocking the circuit group.

System Impact
The circuit is blocked, and the corresponding CIC resources are unavailable.

Handling Suggestion
1. Check whether this circuit has a hardware fault.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Handle the hardware fault, then check whether the notification disappears.

3-122

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

l Yes: End notification handling.

l No: Go to Step 3.
3. In the Terminal window, run the HWUBL CIC command to Unblock the circuit. Then
check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.20 16781888 ISUP Wait RLC (After Send REL) Expiry

Notification Message
l Notification code: 16781888
l Notification name: ISUP Wait RLC (After Send REL) Expiry
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
Timer 5 expires when the ISUP is waiting from RLC (Release Complete message) after
sending the first REL (Release message).

System Impact
Message processing fails during the release process. This CIC may be blocked.

Handling Suggestion
1. Check whether signaling links are in normal state.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore the signaling links to normal. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.21 16781889 ISUP Wait BLA Expiry

Notification Message
l Notification code: 16781889
l Notification name: ISUP Wait BLA Expiry
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
Timer 13 expires when the ISUP is waiting for BLA (Blocking-Acknowledgement message).

3-123

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
Message processing fails during the blocking process. Blocking fails.

Handling Suggestion
1. Check whether signaling links are in normal state.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore the signaling links to normal. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.22 16781890 ISUP Wait UBA Expiry

Notification Message
l Notification code: 16781890
l Notification name: ISUP Wait UBA Expiry
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
Timer 15 expires when the ISUP is waiting for UBA (Unblocking Acknowledgement
message).

System Impact
Message processing fails during the unblocking process. Unblocking fails.

Handling Suggestion
1. Check whether signaling links are in normal state.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore the signaling links to normal. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.23 16781891 ISUP Wait RLC (After Send RSC) Expiry

Notification Message
l Notification code: 16781891
l Notification name: ISUP Wait RLC (After Send RSC) Expiry
l Severity: Warning
l Alarm type: Processing error alarm

3-124

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Probable Cause
Timer 17 expires when the ISUP is waiting for RLC (Release Complete message) after
sending the first RSC (Reset Circuit message).

System Impact
Message processing fails during the circuit reset process. Circuit reset fails.

Handling Suggestion
1. Check whether signaling links are in normal state.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore the signaling links to normal. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.24 16781892 ISUP Wait CGA Expiry

Notification Message
l Notification code: 16781892
l Notification name: ISUP Wait CGA Expiry
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
Timer 19 expires when the ISUP is waiting for CGA (Circuit Group Blocking
Acknowledgement message).

System Impact
l Message processing fails during the circuit group blocking process.
l The circuit group fails to be blocked.

Handling Suggestion
1. Check whether signaling links are in normal state.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore the signaling links to normal. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3-125

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

3.3.25 16781893 ISUP Wait CGUA Expiry

Notification Message
l Notification code: 16781893
l Notification name: ISUP Wait CGUA Expiry
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
Timer 21 expires occurs when the ISUP is waiting for CGUA (Circuit Group Unblocking
Acknowledgement message).

System Impact
l Message processing fails during the circuit group unblocking process.
l The circuit group fails to be unblocked.

Handling Suggestion
1. Check whether CIC is in normal state.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore the CIC to normal.. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.26 16781894 ISUP Wait GRA Expiry

Notification Message
l Notification code: 16781894
l Notification name: ISUP Wait GRA Expiry
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
Timer 23 expires when the ISUP is waiting for a circuit GRA (Group Reset
Acknowledgement message).

System Impact
Message processing fails during the circuit group reset process. Circuit group reset fails.

Handling Suggestion
1. Check whether CIC is in normal state.

3-126

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

l Yes: Contact ZTE for help.

l No: Go to Step 2.
2. Restore the CIC to normal.. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.27 16781895 ISUP Wait CQR Expiry

Notification Message
l Notification code: 16781895
l Notification name: ISUP Wait CQR Expiry
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
Timer 28 expires when the ISUP is waiting for CQR (Circuit Group Query Response
message).

System Impact
Message processing failed during the process of circuit group query. The circuit group
query fails.

Handling Suggestion
1. Check whether CIC is in normal state.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore the CIC to normal.. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.28 16781896 ISUP Wait INF Expiry

Notification Message
l Notification code: 16781896
l Notification name: ISUP Wait INF Expiry
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
Timer 33 expires when the ISUP is waiting for INF (Information message).

3-127

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
Message processing fails during the information request process. Information query fails.

Handling Suggestion
1. Check whether CIC is in normal state.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore the CIC to normal.. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.29 16781897 ISUP RMT Block

Notification Message
l Notification code: 16781897
l Notification name: ISUP RMT Block
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
The ISUP receives a remote Blocking Signal (BLO).

System Impact
This CIC is blocked and unavailable.

Handling Suggestion
1. Check whether the notification can disappear automatically.
l Yes: No handling is required.
l No: Go to Step 2.
2. Ask the remote office's maintenance personnel to check whether its circuits are in
normal state.
l Yes: Contact ZTE for help.
l No: Contact the maintenance engineer at the remote end for handling.

3.3.30 16781898 ISUP Unblock RMT by Call

Notification Message
l Notification code: 16781898
l Notification name: ISUP Unblock RMT by Call
l Severity: Warning
l Alarm type: Processing error alarm

3-128

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Probable Cause
The ISUP receives a non-test IAM message on the circuit blocked by the remote end.

System Impact
None

Handling Suggestion
It is a circuit operation performed by the opposite end. No handling is required.

3.3.31 16781899 ISUP CG RMT Block (Maintenance Oriented)

(Without Release)
Notification Message
l Notification code: 16781899
l Notification name: ISUP CG RMT Block (Maintenance Oriented) (Without Release)
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
The ISUP receives CGB (Circuit Group Blocking message) (maintenance oriented) from
the remote end.

System Impact
This circuit group is blocked and unavailable.

Handling Suggestion
It is a circuit operation performed by the opposite end. No handling is required.

3.3.32 16781900 ISUP CG RMT Block (Hardware Oriented) (With

Release)
Notification Message
l Notification code: 16781900
l Notification name: ISUP CG RMT Block (Hardware Oriented) (With Release)
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
The ISUP receives CGB(Circuit Group Blocking message) (hardware failure oriented) from
the remote end.

3-129

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
This circuit group is blocked and unavailable.

Handling Suggestion
It is a circuit operation performed by the opposite end. No handling is required.

3.3.33 16781901 ISUP: Receive UCIC Message From Opposite

Switch Equipment
Notification Message
l Notification code: 16781901
l Notification name: ISUP: Receive UCIC message from opposite switch equipment.
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
The ISUP receives Unallocated CIC message (UCIC).

System Impact
This CIC is blocked.

Handling Suggestion
1. Check whether local configuration is correct.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Modify local configuration properly. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Ask the remote office's maintenance personnel to check whether its CIC is in normal
state.
l Yes: Contact ZTE for help.
l No: Contact the maintenance engineer at the remote end for handling.

3.3.34 16781902 ISUP: Signal Block CIC by Local Switch During

to T17 Expiry
Notification Message
l Notification code: 16781902
l Notification name: ISUP: Signal Block CIC by local switch during T17 expiry
l Severity: Warning

3-130

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

l Alarm type: Processing error alarm

Probable Cause
Timer 17 expires again when the ISUP is waiting for Release Complete message (RLC).
The ISUP blocks this CIC, which triggers the circuit reset flow.

System Impact
This CIC is blocked.

Handling Suggestion
1. Check whether local configuration is correct.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Modify local configuration properly. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Ask the remote office's maintenance personnel to check whether its CIC is in normal
state.
l Yes: Contact ZTE for help.
l No: Contact the maintenance engineer at the remote end for handling.

3.3.35 16781903 ISUP Circuit Is Locally Blocked by Man-Machine

Command
Notification Message
l Notification code: 16781903
l Notification name: ISUP circuit is locally blocked by man-machine command
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
A circuit is manually blocked by a man-machine command.

System Impact
Because the circuit is locally blocked, no call can seize it.

Handling Suggestion
In Terminal window, run the UBL CIC command to unblock the circuit. Then check
whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3-131

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

3.3.36 16781904 ISUP Circuit Is Locally Blocked by Call Processing

Notification Message
l Notification code: 16781904
l Notification name: ISUP circuit is locally blocked by call processing
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
Call processing locally blocks the ISUP circuit.

System Impact
The circuit seized by a call is blocked after the call is released. Another call cannot seize
this circuit.

Handling Suggestion
1. Check whether the "refuse to release trunk after call is over" security variable is set to
0 and the settings are consistent on foreground and background.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Modify the "refuse to release trunk after call is over" security variable to 0, and keep
the settings on foreground and background consistent. Then check whether the
notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.
3. Check whether the incoming circuit is blocked in the incoming direction.
l Yes: Go to Step 4.
l No: Contact ZTE for help.
4. Check whether the blocked circuit can still receive incoming calls.
l Yes: It is clear that the remote circuit state is abnormal. Contact the maintenance
engineer at the remote end for handling.
l No: Contact ZTE for help.

3.3.37 16781905 ISUP Circuit Is Locally Unblocked When It Is Reset

Notification Message
l Notification code: 16781905
l Notification name: ISUP circuit is locally unblocked when it is reset
l Severity: Warning
l Alarm type: Processing error alarm

3-132

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Probable Cause
An ISUP circuit is unblocked locally due to resetting.

System Impact
The circuit is brought into service again after being unblocked.

Handling Suggestion
No handling is required.

3.3.38 16781906 ISUP Circuit Is Remotely Blocked When It Is Reset

Notification Message
l Notification code: 16781906
l Notification name: ISUP circuit is remotely blocked when it is reset
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
An ISUP circuit is remotely blocked due to resetting.

System Impact
Because the circuit is remotely blocked, no call can seize it.

Handling Suggestion
According to detailed notification information, find the corresponding circuilt time slot,
re-send the circuit group recovery (GRS) message. Check whether the circuit state is
"BLOCK" in the received GRS ACK (GRA) message.
l Yes: Contact the maintenance engineer at the remote end for handling.
l No: Contact ZTE for help.

3.3.39 16781907 ISUP Circuit Is Remotely Unblocked When It Is

Reset
Notification Message
l Notification code: 16781907
l Notification name: ISUP circuit is remotely unblocked when it is reset.
l Severity: Warning
l Alarm type: Processing error alarm

3-133

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Probable Cause
An ISUP circuit is remotely unblocked due to resetting.

System Impact
The circuit is brought into service again after being unblocked.

Handling Suggestion
No handling is required.

3.3.40 16781908 ISUP Circuit Group Is Locally Blocked by

Man-Machine Command (Maintenance)
Notification Message
l Notification code: 16781908
l Notification name: ISUP circuit group is locally blocked by man-machine command
(maintenance)
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
An ISUP circuit group is locally blocked by a man-machine command (maintenance
oriented).

System Impact
Because the circuits in this circuit group are locally blocked, no call can seize it.

Handling Suggestion
No handling is required.

3.3.41 16781909 ISUP Circuit Group Is Locally Blocked by

Man-Machine Command (Hardware)
Notification Message
l Notification code: 16781909
l Notification name: ISUP circuit group is locally blocked by man-machine command
(hardware)
l Severity: Warning
l Alarm type: Processing error alarm

3-134

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Probable Cause
An ISUP circuit group is locally blocked by a man-machine command (hardware failure).

System Impact
Because the circuits in this circuit group are locally blocked, no call can seize it.

Handling Suggestion
No handling is required.

3.3.42 16781910 ISUP Circuit Continuity Recheck Failed

Notification Message
l Notification code: 16781910
l Notification name: ISUP circuit continuity recheck failed
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
The ISUP circuit continuity rechecking fails.

System Impact
The continuity check fails. If a call that requires to perform the continuity check, this call
also fails.

Handling Suggestion
1. Check whether tone and trunk resources on the gateway are available.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore tone and trunk resources to be available. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.43 16781911 ISUP Circuit Continuity Recheck Succeed

Notification Message
l Notification code: 16781911
l Notification name: ISUP circuit continuity recheck succeed
l Severity: Warning
l Alarm type: Processing error alarm

3-135

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Probable Cause
The ISUP continuity rechecking succeeds.

System Impact
None

Handling Suggestion
No handling is required.

3.3.44 16781912 ISUP Can Not Carry Out the Continuity Check for
Busy Circuit
Notification Message
l Notification code: 16781912
l Notification name: ISUP can not carry out the continuity check for busy circuit
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
The continuity check fails when the circuit is busy.

System Impact
None

Handling Suggestion
Carry out the continuity check again when the circuit is idle. Then check whether the
notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.45 16781913 SS7UP Failed to Recognize the Circuit

Notification Message
l Notification code: 16781913
l Notification name: SS7UP failed to recognize the circuit
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
The SS7UP fails to identify this circuit.

3-136

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

System Impact
An adjacent office originates an outgoing call on this circuit, which results in the call loss
of the local office.

Handling Suggestion
1. Check whether a circuit is configured corresponding to the circuit ID reported in the
notification.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Configure a circuit corresponding to the circuit ID reported in the notification. Then
check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Check whether circuit configuration at both ends is correct.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Modify circuit configuration properly. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.46 16781914 ISUP Detected Inconsistency Between Circuit

Group Maintenance Request and Acknowledge
Notification Message
l Notification code: 16781914
l Notification name: ISUP detected inconsistency between circuit group maintenance
request and acknowledge
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
The ISUP circuit group maintenance acknowledgement is inconsistent with the request.

System Impact
None

Handling Suggestion
1. Check whether trunk configuration or circuit state in the two switching offices is
inconsistent.
l Yes: Go to Step 2.
l No: Contact ZTE for help.

3-137

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

2. Modify trunk configuration or circuit state in the two switching offices to be consistent.
Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.47 16781921 Office or DPC Unreachable Call Release

Notification Message
l Notification code: 16781921
l Notification name: Office or DPC Unreachable Call Release
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
The call is released because the office signaling point is unreachable.

System Impact
The signaling point of an adjacent office is interrupted. The online-call of the corresponding
office will be interrupted.

Handling Suggestion
1. Check whether the link between the two offices is in normal state.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Restore the link between the two offices to normal. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Check whether the corresponding No.7, Sigtran, and SIP signaling links are normal.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Restore the corresponding No.7, Sigtran, and SIP signaling links to normal. Then
check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.48 16783937 Current IP Congestion Level of Bearer

Notification Message
l Notification code: 16783937
l Notification name: Current IP Congestion Level of Bearer
l Severity: Warning

3-138

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

l Alarm type: Processing error alarm

Probable Cause
This notification indicates the current IP congestion level of bearer.

System Impact
None.

Handling Suggestion
1. Check whether the number of calls over the corresponding bearer is normal.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore the number of calls over the corresponding bearer to normal. Then check
whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.49 16784448 System Dynamic Recovery Monitor Item Abnormity

Notification Message
l Notification code: 16784448
l Notification name: System dynamic recovery monitor item abnormity
l Severity: Warning
l Alarm type: Equipment alarm

Probable Cause
The dynamic recovery monitoring index in system self-testing is abnormal.

System Impact
The monitor value in the index reaches the threshold.

Handling Suggestion
1. Check whether abnormal index and monitoring index configuration is correct.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Modify abnormal index and monitoring index configuration properly. Then check
whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3-139

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

3.3.50 16784704 Data Synchronization Failed

Notification Message
l Notification code: 16784704
l Notification name: Data synchronization failed
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
The data synchronization between the LMP and the LIG fails.

System Impact
The interception function is abnormal.

Handling Suggestion
1. Check whether lower layer communication is normal.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Restore lower layer communication to normal.
3. LIG automatically initiates a TCL connection to the NE. Check whether synchronization
succeeds.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.51 16784705 LIG Link Check Failed

Notification Message
l Notification code: 16784705
l Notification name: LIG link check failed
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The detection of the TCP link to the LIG fails.

System Impact
The interception function is abnormal.

Handling Suggestion
1. Check whether lower layer communication is normal.
l Yes: Go to Step 3.

3-140

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

l No: Go to Step 2.
2. Restore lower layer communication to normal.
3. Check whether the LIG device runs normally.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Restore the LIG device to normal. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.52 25170948 DNS Link Status Change

Notification Message
l Notification code: 25170948
l Notification name: DNS link status change
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The status of the DNS link changes.

System Impact
The DNS query is affected.

Handling Suggestion
1. In the Terminal window of the LMT, run the SHOW DNSGRP command to check
whether the DNS server configuration is correct.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. In the Terminal window of the LMT, run the SET DNSGRP to modify the DNS server
configuration. Then check whether the notification still appears.
l Yes: Go to Step 3.
l No: End notification handling.
3. In the Terminal window of the LMT, run the SHOW DNSLINK STATUS to check
whether the DNS link status is reachable.
l Yes: End notification handling.
l No: Go to Step 4.
4. Eliminate the physical link fault. Then check whether the notification still appears.
l Yes: Go to Step 5.
l No: End notification handling.
5. In the Terminal window of the LMT, run the SET DNSLINK to check whether the dest
port is 53.
l Yes: Contact ZTE for help.
l No: Go to Step 6.

3-141

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

6. In the Terminal window of the LMT, run the SET DNSLINK to set the dest port to 53.
Then check whether the notification still appears.
l Yes: Contact ZTE for help.
l No: End notification handling.

3.3.53 25172483 Remote IP Addresses of the IPQos Test Calls

During a Period Do Not Match
Notification Message
l Notification code: 25172483
l Notification name: Remote IP addresses of the IPQos test calls during a period do
not match.
l Severity: Minor
l Alarm type: Equipment alarm

Probable Cause
The remote IP addresses in an IPQOS test call during a period do not match.

System Impact
None

Handling Suggestion
No handling is required.

3.3.54 33576914 Svc Register Fail

Notification Message
l Notification code: 33576914
l Notification name: Svc register fail
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
The host name is missing during service registration.

System Impact
Diameter is not affected, but message cannot be sent or received by the host.

Handling Suggestion
1. Check whether the name of the service host is configured.

3-142

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

l Yes: Contact ZTE for help.

l No: Go to Step 2.
2. Configure the name of the service host. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.55 33576915 More than 80% DEP Dialogs Is Used

Notification Information
l Notification code: 33576915
l Notification name: More than 80% DEP Dialogs is used
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
The service process creates too many sessions, or the protocol stack dialog expires.

System Impact
The services with lower priority fail to seize DEP session resources, so they are processed
slowly or fail to be processed.

Handling Suggestion
The protocol stack session is automatically released in the following two cases, so it needs
no intervention.
l The service process receives an answer message.
l The protocol stack sets the timer for test. If the timer expires, the protocol stack
session is automatically released.

3.3.56 33576916 Diameter Version Is Not Supported

Notification Message
l Notification code: 33576916
l Notification name: Diameter Version is not supported
l Severity: Critical
l Alarm type: Communication alarm

Probable Cause
Diameter version is not supported.

3-143

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
Diameter version is not supported.

Handling Suggestion
Check current diameter version.

3.3.57 33604560 Calling Party Long Time Conversation

Notification Message
l Notification code: 33604560
l Notification name: Calling Party long time conversation
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
The call duration of the calling party exceeds the set threshold.

System Impact
None

Handling Suggestion
No handling is required.

3.3.58 33604561 Called Party Long Time Conversation

Notification Message
l Notification code: 33604561
l Notification name: Called Party long time conversation
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
The call duration of the called party exceeds the set threshold.

System Impact
None

Handling Suggestion
No handling is required.

3-144

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

3.3.59 33604562 BICC T17 Time Out When Waiting for RLC After
Sending RSC
Notification Message
l Notification code: 33604562
l Notification name: BICC T17 time out when waiting for RLC after sending RSC
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
Timeout occurs when the BICC is waiting for an RLC message after sending a RSC
message.

System Impact
If the remote office does not respond within a long period, the CIC circuit in the local office
will enter signaling blocked state and calls cannot be originated.

Handling Suggestion
1. Check whether signaling transmission between the local and remote offices is normal.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore signaling transmission between the local and remote offices to normal. Then
check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.60 33604563 BICC T19 Time out when Waiting for CGBA
Notification Message
l Notification code: 33604563
l Notification name: BICC T19 time out when waiting for CGBA
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
Timer T19 times out when BICC is waiting for CGBA (Circuit Group Blocking-Acknowledg
ement message).

System Impact
The circuit state of the local office is inconsistent with that of the remote office. The remote
office will continue using the abnormal CIC.

3-145

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Handling Suggestion
1. Check whether signaling transmission between the local and remote offices is normal.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore signaling transmission between the local and remote offices to normal. Then
check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.61 33604564 BICC T21 Time Out When Waiting for CGUA
Notification Message
l Notification code: 33604564
l Notification name: BICC T21 time out when waiting for CGUA
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
Timer T21 times out when BICC is waiting for CGUA (Circuit Group Unblocking-Acknowl
edgement Message).

System Impact
The circuit state of the local office is inconsistent with that of the remote office.

Handling Suggestion
1. Check whether signaling transmission between the local and remote offices is normal.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore signaling transmission between the local and remote offices to normal. Then
check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.62 33604565 BICC T23 Time Out When Waiting for GRA
Notification Message
l Notification code: 33604565
l Notification name: BICC T23 time out when waiting for GRA
l Severity: Warning
l Alarm type: Processing error alarm

3-146

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Probable Cause
Timer T23 times out when BICC is waiting for GRA (Group Reset Acknowledgement
message).

System Impact
The circuit state of the local office is inconsistent with that of the remote office.

Handling Suggestion
1. Check whether signaling transmission between the local and remote offices is normal.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore signaling transmission between the local and remote offices to normal. Then
check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.63 33604566 BICC T33 Time Out When Waiting for INF
Notification Message
l Notification code: 33604566
l Notification name: BICC T33 time out when waiting for INF
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
Timer T33 times out when BICC is waiting for the INF message.

System Impact
Subsequent calls fail to get calling numbers.

Handling Suggestion
1. Check whether the remote office supports INR messages.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Select the trunk tag "Connection allowed in case of no calling number" of the local
office. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.
3. Select the trunk tag "TUP does not request calling number immediately after receiving
IAM" of the local office. Then check whether the notification disappears.
l Yes: End notification handling.

3-147

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l No: Contact ZTE for help.

3.3.64 33604567 BICC Unblocking CIC Remotely for Calls

Notification Message
l Notification code: 33604567
l Notification name: BICC unblocking CIC remotely for calls
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
The remote blocking of the BICC circuit is removed due to call processing.

System Impact
The blocked circuit at the remote end resumes service.

Handling Suggestion
No handling is required.

3.3.65 33604568 BICC T28 Time Out When Waiting for CQR
Notification Message
l Notification code: 33604568
l Notification name: BICC T28 time out when waiting for CQR
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
Timer 28 expires when the BICC is waiting for CQR (Circuit Group Query Response
message).

System Impact
Querying circuit groups fails.

Handling Suggestion
Check whether the remote office supports CQM messages.

l Yes: Contact ZTE for help.

l No: Contact the maintenance engineer at the remote end for handling.

3-148

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

3.3.66 33604569 BICC Detected Unequipped CIC

Notification Message
l Notification code: 33604569
l Notification name: BICC detected unequipped CIC
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
The BICC is not configured with this CIC.

System Impact
When an adjacent office originates an outgoing call on this circuit, call loss may occur in
the local office.

Handling Suggestion
1. Check whether a circuit is configured corresponding to the circuit ID reported in the
notification.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Configure a circuit corresponding to the circuit ID reported in the notification. Then
check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. Check whether circuit configuration at both ends is correct.
l Yes: Contact ZTE for help.
l No: Go to Step 4.
4. Modify circuit configuration properly. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.67 33604570 BICC Blocked Circuit Group Locally

Notification Message
l Notification code: 33604570
l Notification name: BICC blocked circuit group locally
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
The BICC circuit group is blocked locally.

3-149

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
Circuits in the circuit group are in maintenance blocked state. Calls cannot use these
circuits.

Handling Suggestion
Unblock the circuit group. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.68 33604571 BICC Blocked Circuit Group Remotely

Notification Message
l Notification code: 33604571
l Notification name: BICC blocked circuit group remotely
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
A BICC circuit group is remotely blocked.

System Impact
Circuits in the circuit group are in remote maintenance blocked state. Calls cannot use
these circuits.

Handling Suggestion
Check whether the remote end initiates circuit group blocking for a normal reason.
l Yes: Contact ZTE for help.
l No: Contact the maintenance engineer at the remote end for handling.

3.3.69 33604572 BICC Blocked CIC Remotely for Group Reset

Notification Message
l Notification code: 33604572
l Notification name: BICC blocked CIC remotely for group reset
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
A BICC circuit is remotely blocked because of reset of the BICC circuit group.

3-150

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

System Impact
The corresponding CIC fails to be normally reset, so the outgoing calls of the local office
cannot seize this circuit.

Handling Suggestion
According to detailed notification information, find the corresponding circuilt time slot,
re-send the circuit group recovery (GRS) message. Check whether the circuit state is
"BLOCK" in the received GRS ACK (GRA) message.
l Yes: Contact the maintenance engineer at the remote end for handling.
l No: Contact ZTE for help.

3.3.70 33604573 BICC Unblocked CIC Remotely for Reset

Notification Message
l Notification code: 33604573
l Notification name: BICC unblocked CIC remotely for reset
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
A BICC circuit is remotely unblocked due to reset.

System Impact
The blocked circuit at the remote end resumes service.

Handling Suggestion
No handling is required.

3.3.71 33604574 BICC Unblocked CIC Locally for Reset

Notification Message
l Notification code: 33604574
l Notification name: BICC unblocked CIC locally for reset
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
A BICC circuit is locally unblocked because of reset.

3-151

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
The blocked circuit at the local end resumes service.

Handling Suggestion
No handling is required.

3.3.72 33604575 BICC Detected Inconsistency Between Circuit

Group Maintenance Request and Acknowledge
Notification Message
l Notification code: 33604575
l Notification name: BICC detected inconsistency between circuit group maintenance
request and acknowledge
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
The BICC circuit group maintenance acknowledgement is inconsistent with the request.

System Impact
The system cannot block or reset some requested CIC circuits.

Handling Suggestion
1. Check whether trunk configuration or circuit state in the two switching offices is
inconsistent.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Modify trunk configuration or circuit state in the two switching offices to be consistent.
Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.73 33604576 BICC T5 Time Out When Waiting for RLC After
Sending REL
Notification Message
l Notification code: 33604576
l Notification name: BICC T5 time out when waiting for RLC after Sending REL
l Severity: Warning
l Alarm type: Processing error alarm

3-152

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Probable Cause
Timer 5 expires when the BICC is waiting from an RLC message after sending an REL
message.

System Impact
If the remote office does not respond within a long period, the CIC circuit in the local office
will enter signaling blocked state and calls cannot be originated.

Handling Suggestion
1. Check whether signaling transmission between the local and remote offices is normal.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore signaling transmission between the local and remote offices to normal. Then
check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.74 33604577 Call Duration Limited by Fraud Profile

Notification Message
l Notification code: 33604577
l Notification name: Call duration limited by fraud profile
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
The duration of this call reaches the threshold of "Fraud Profile" subscribed by the
subscriber.

System Impact
l If the subscriber subscribes to service "The call is released after the call duration
reaches the threshold of Fraud Profile", the call will be released after this notification
is reported.
l If the subscriber subscribes to service "Report the notification when the call duration
reaches the threshold of Fraud Profile", the system only reports this call and the call
is not released.

Handling Suggestion
No handling is required.

3-153

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

3.3.75 33609432 SIP Link Blocked by OMC

Notification Message
l Notification code: 33609432
l Notification name: SIP link Blocked by OMC
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
The SIP link is blocked by the network management system.

System Impact
SIP messages cannot be transmitted or received through the blocked link, and all the
SIP–related services though this link are unavailable.

Handling Suggestion
Check whether the SIP link is manually blocked.
l Yes: No handling is required.
l No: Contact ZTE for help.

3.3.76 33609433 SIP Link UnBlocked by OMC

Notification Message
l Notification code: 33609433
l Notification name: SIP link UnBlocked by OMC
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
The SIP link is unblocked by the network management system.

System Impact
There is no impact on the system.

Handling Suggestion
Check whether the SIP link is manually unblocked.
l Yes: No handling is required.
l No: Contact ZTE for help.

3-154

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

3.3.77 33609434 SIP Link Blocked by APP

Notification Message
l Notification code: 33609434
l Notification name: SIP link Blocked by APP
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
In the dual-homing networking mode, the SIP link is blocked by the service.

System Impact
The system fails to transmit and receive SIP messages through the blocked link. All the
SIP related services through this link are unavailable.

Handling Suggestion
Check whether the local office is active or standby.
l Active: Contact ZTE for help.
l Standby: No handling is required.

3.3.78 33609435 SIP Link UnBLocked by APP

Notification Message
l Notification code: 33609435
l Notification name: SIP link UnBLocked by APP
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
The SIP link is unblocked by a service.

System Impact
There is no impact on the system.

Handling Suggestion
The SIP link is unblocked. The link is recovered.No handling is required.

3-155

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

3.3.79 33610240 DH Block Signal Link Failed

Notification Message
l Notification code: 33610240
l Notification name: DH block signal link failed
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
The working role of the MSCS office is not converted successfully.

System Impact
The link of the dual-homing standby office is not blocked successfully. If the service flow
interacts with the standby office, the service flow will be abnormal, or the service will fail.

Handling Suggestion
1. In the Terminal window, run the SHOW OFCSTAT command by using the office
number in the detailed notification information to check whether the office is available.
l Yes: Go to Step 2.
l No: No handling is required.
2. Perform dual-home changover again so that the local office becomes standby. Then
check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. In the Terminal window, run the INACT LINK command to deactivate the
corresponding link. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.80 33610241 DH Block Signal Link Part Failed

Notification Message
l Notification code: 33610241
l Notification name: DH block signal link part failed
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
The working role of the MSCS office is not converted successfully.

3-156

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

System Impact
The link of the dual-homing standby office is not blocked successfully. If the service flow
interacts with the standby office, the service flow will be abnormal or fail.

Handling Suggestion
1. In the Terminal window, run the SHOW OFCSTAT command by using the office
number in the detailed notification information to check whether the office is available.
l Yes: Go to Step 2.
l No: No handling is required.
2. Perform dual-home changover again so that the local office becomes standby. Then
check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. In the Terminal window, run the INACT LINK command to deactivate the
corresponding link. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.81 33610242 DH Unblock Signal Link Failed

Notification Message
l Notification code: 33610242
l Notification name: DH unblock signal link failed
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
The working role of the MSCS office is converted unsuccessfully.

System Impact
The link of the dual-homing standby office is blocked unsuccessfully. If the service flow
interacts with the standby office, the service flow will be abnormal, or fail.

Handling Suggestion
1. In the Terminal window, run the SHOW OFCSTAT command by using the office
number in the detailed notification information to check whether the office is available.
l Yes: No handling is required.
l No: Go to Step 2.
2. Perform dual-home changover again so that the local office becomes active. Then
check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.

3-157

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

3. In the Terminal window, run the ACT LINK command to activate the corresponding
link. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.82 33610243 DH Unblock Signal Link Part Failed

Notification Message
l Notification code: 33610243
l Notification name: DH unblock signal link part failed
l Severity: Minor
l Alarm type: Communication alarm

Probable Cause
The working role of the MSCS office is converted unsuccessfully.

System Impact
If the links of the adjacent office are unblocked unsuccessfully, all the services of this office
will fail. If some links of the adjacent office are unblocked unsuccessfully, the link load
increases. Too high load results in call loss.

Handling Suggestion
1. In the Terminal window, run the SHOW OFCSTAT command by using the office
number in the detailed notification information to check whether the office is available.
l Yes: No handling is required.
l No: Go to Step 2.
2. Perform dual-home changover again so that the local office becomes active. Then
check whether the notification disappears.
l Yes: End notification handling.
l No: Go to Step 3.
3. In the Terminal window, run the ACT LINK command to activate the corresponding
link. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.83 33610254 BSC Reset MSCS

Notification Message
l Notification code: 33610254
l Notification name: BSC Reset MSCS
l Severity: Major
l Alarm type: Communication alarm

3-158

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Probable Cause
A BSC is reset.

System Impact
The BSC-related services fail during reset, and the BSC-related resources are released.

Handling Suggestion
No handling is required.

3.3.84 33610255 BSC Reset Circuit

Notification Message
l Notification code: 33610255
l Notification name: BSC Reset Circuit
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The BSC resets the circuit.

System Impact
The MSCS releases the related resources and services on this reset circuit.

Handling Suggestion
No handling is required.

3.3.85 33610256 BSC Block Circuit

Notification Message
l Notification code: 33610256
l Notification name: BSC Block Circuit
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The BSC blocks the circuit.

System Impact
The MSCS does not allocate this circuit any longer.

3-159

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Handling Suggestion
No handling is required.

3.3.86 33610257 BSC UnBlock Circuit

Notification Message
l Notification code: 33610257
l Notification name: BSC UnBlock Circuit
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The BSC unblocks the circuit.

System Impact
This circuit is available for services.

Handling Suggestion
No handling is required.

3.3.87 33610258 BSC Block Circuit Group

Notification Message
l Notification code: 33610258
l Notification name: BSC Block Circuit Group
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The BSC blocks a circuit group.

System Impact
The MSCS does not allocate the related circuits any longer.

Handling Suggestion
No handling is required.

3-160

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

3.3.88 33610259 BSC UnBlock Circuit Group

Notification Message
l Notification code: 33610259
l Notification name: BSC UnBlock Circuit Group
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The BSC unblocks the circuit group.

System Impact
Related circuits are available for services.

Handling Suggestion
No handling is required.

3.3.89 33610260 BSC Overload

Notification Message
l Notification code: 33610260
l Notification name: BSC Overload
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The BSC is overloaded. The MSCS receives an Overload message of the BSC.

System Impact
Some handoff and paging services may be discarded.

Handling Suggestion
No handling is required. The system automatically starts the load control process.

3.3.90 33610261 MSC Reset BSC

Notification Message
l Notification code: 33610261
l Notification name: MSC Reset BSC
l Severity: Major

3-161

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Alarm type: Communication alarm

Probable Cause
l The network management system of the MSCS initiates the operation of resetting the
BSC.
l The BSC office changes from being disconnected to being connected.

System Impact
At the MSCS side, the resources and services related to this BSC are released. During
the period of resetting, all the services newly accessed by this BSC are rejected.

Handling Suggestion
No handling is required.

3.3.91 33610262 MSCS Reset BSC Fail

Notification Message
l Notification code: 33610262
l Notification name: MSCS Reset BSC Fail
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The MSC resets the BSC, but does not receive a response message from the BSC.

System Impact
After three consecutive reset operations, the system considers that the BSC is already
reset.

Handling Suggestion
No handling is required.

3.3.92 33610263 MSCS Reset Circuit

Notification Message
l Notification code: 33610263
l Notification name: MSCS Reset Circuit
l Severity: Warning
l Alarm type: Communication alarm

3-162

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Probable Cause
The MSC resets the circuit.

System Impact
The services borne on the reset circuit of the BSC are released.

Handling Suggestion
No handling is required.

3.3.93 33610264 MSCS Reset Circuit Fail

Notification Message
l Notification code: 33610264
l Notification name: MSCS Reset Circuit Fail
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The MSCS fails to reset the BSC circuit.

System Impact
None

Handling Suggestion
No handling is required.

3.3.94 33610265 BSC Unequipped Circuit

Notification Message
l Notification code: 33610265
l Notification name: BSC Unequipped Circuit
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The MSCS sets the corresponded BSC circuit to unequipped after receiving an
UNEQUIPPED CIRCUIT message from the BSC.

System Impact
The MSCS will not allocate the corresponding circuit.

3-163

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Handling Suggestion
No handling is required.

3.3.95 33610266 MSCS Unequipped Circuit

Notification Message
l Notification code: 33610266
l Notification name: MSCS Unequipped Circuit
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The circuits at the MSCS side are not equipped.

System Impact
The MSCS does not allocate the corresponding circuit any longer.

Handling Suggestion
No handling is required.

3.3.96 33610267 MSCS A Interface Overload

Notification Message
l Notification code: 33610267
l Notification name: MSCS A Interface Overload
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
l Because the A interface of the local office is overloaded, the MSCS sends an
OVERLOAD message to the BSC.
l The CMP is overloaded.

System Impact
Some services accessed by the BSC may be discarded.

Handling Suggestion
No handling is required.

3-164

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

3.3.97 33610268 RNC Reset MSCS

Notification Message
l Notification code: 33610268
l Notification name: RNC Reset MSCS
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
MSC Server Receive Reset Message From RNC.

System Impact
The resources and services related to this RNC are released at the MSCS side. During a
resetting period, all the services accessed by this RNC are rejected.

Handling Suggestion
No handling is required.

3.3.98 33610269 RNC Overload

Notification Message
l Notification code: 33610269
l Notification name: RNC Overload
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
Because the RNC is overloaded, the MSCS receives an Overload message from the RNC.

System Impact
Some handoff and paging services on the RNC may be discarded.

Handling Suggestion
No handling is required.

3.3.99 33610270 MSC Reset RNC

Notification Message
l Notification code: 33610270
l Notification name: MSC Reset RNC

3-165

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Severity: Major
l Alarm type: Communication alarm

Probable Cause
l The network management system of the MSCS initiates a reset of the RNC.
l The status of the RNC office changes from disconnected to connected.

System Impact
The resources and services related to this RNC are released at the MSCS side. During a
resetting period, all the services accessed by this RNC are rejected.

Handling Suggestion
No handling is required.

3.3.100 33610271 MSC Reset RNC Fail

Notification Message
l Notification code: 33610271
l Notification name: MSC Reset RNC Fail
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The MSC sends reset messages to RNC for three consecutive times, but does not receive
a response message from the RNC.

System Impact
After three consecutive reset operations, the system considers that the BSC is already
reset.

Handling Suggestion
No handling is required.

3.3.101 33610273 MSCS Iu Interface Overload

Notification Message
l Notification code: 33610273
l Notification name: MSCS Iu Interface Overload
l Severity: Warning
l Alarm type: Communication alarm

3-166

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Probable Cause
The Iu interface of the MSC is overloaded.

System Impact
Some services accessed by the RNC may be discarded.

Handling Suggestion
No handling is required.

3.3.102 33610274 Backup MSCS Switched to Master

Notification Message
l Notification code: 33610274
l Notification name: Backup MSCS switched to master
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
The dual-home working domain is switched to the active state.

System Impact
The user is notified that the system has a dual-home changeover. Services are still normal
as long as one MSCS is active and partner MSCSs are standby.

Handling Suggestion
According to the detailed notification information, identify reasons for the system
changeover and handle the problem properly. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.103 33610275 Master MSCS Switched to Backup

Notification Message
l Notification code: 33610275
l Notification name: Master MSCS switched to backup
l Severity: Major
l Alarm type: Communication alarm

3-167

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Probable Cause
The dual-home working domain is switched to the standby state.

System Impact
The user is notified that the system has a dual-home changeover. Services are still normal
as long as one MSCS is active and partner MSCSs are standby.

Handling Suggestion
According to the detailed notification information, identify reasons for the system
changeover and handle the problem properly. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.104 33610278 The MSC Server Becomes the Master MSC Server
of the MSC Pool User Data Synchronization
Notification Message
l Notification code: 33610278
l Notification name: The MSC Server becomes the master MSC Server of the MSC
Pool user data synchronization
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
This is a very important configuration notification. It is generated when a user uses the
SET POOLFELLOW command to change the role of the local office from SLAVE (standby
role) to MASTER (active role).

System Impact
This notification tells you that the MSC pool fellowship changes, without affecting the
system.

Handling Suggestion
1. Check whether configuration of the local office and the adjacent office attribute of the
partner office in MSC Pool user data synchronization is correct.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Modify configuration of the local office and the adjacent office attribute of the partner
office in MSC Pool user data synchronization. Then check whether the notification
disappears.

3-168

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

l Yes: End notification handling.

l No: Contact ZTE for help.

3.3.105 33610279 The MSC Server Is No Longer the Master MSC

Server of the MSC Pool User Data Synchronization
Notification Message
l Notification code: 33610279
l Notification name: The MSC Server is no longer the master MSC Server of the MSC
Pool user data synchronization
l Severity: Major
l Alarm type: Communication alarm

Probable Cause
This is a very important configuration notification. It is generated when a user uses the SET
POOLFELLOW command to change the role of the local office from MASTER (active role)
to SLAVE (standby role).

System Impact
This notification tells you that the MSC pool fellowship changes, without affecting the
system.

Handling Suggestion
1. Check whether configuration of the local office and the adjacent office attribute of the
partner office in MSC Pool user data synchronization is correct.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Modify configuration of the local office and the adjacent office attribute of the partner
office in MSC Pool user data synchronization. Then check whether the notification
disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.106 33610284 Access Bearer Error

Notification Message
l Notification code: 33610284
l Notification name: Access Bearer Error
l Severity: Major
l Alarm type: Equipment alarm

3-169

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Probable Cause
The media plane on the access side fails.

System Impact
The media plane on the access side is unavailable.

Handling Suggestion
1. Check whether the media-plane connection to RNC or BSC is normal.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore the media-plane connection to RNC or BSC to normal. Then check whether
the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.107 33610285 Jitter Occurs on Access Bearer Status Judgment

Notification Message
l Notification code: 33610285
l Notification name: Jitter occurs on access bearer status judgment
l Severity: Major
l Alarm type: Equipment alarm

Probable Cause
The state of the access bearer is jitter.

System Impact
The media plane on the access side is unavailable.

Handling Suggestion
1. Check whether the interface bearer fails.
l Yes: Go to Step 2.
l No: Contact ZTE for help.
2. Restore the interface bearer to normal. Stop detection of the bearer to the faulty
interface if necessary. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3-170

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

3.3.108 33610286 ZDB Records Conflict

Notification Message
l Notification code: 33610286
l Notification name: ZDB records conflict
l Severity: Critical
l Alarm type: Processing error alarm

Probable Cause
ZDB records conflict when loading ZDB.

System Impact
During the system loading, only the records before the index collision is loaded. The
records after the index collision cannot be loaded. In this case, the manual intervention is
required to ensure the consistency between the configuration data and the OMP loading
data.

Handling Suggestion
Check the configuration, and delete the conflicting records in accordance with the
configuration table displayed in the additional information of the notification.

3.3.109 33610287 ZDB Record Number Exceeds Capacity

Notification Message
l Notification code: 33610287
l Notification name: ZDB record number exceeds capacity
l Severity: Critical
l Alarm type: Processing error alarm

Probable Cause
ZDB record number exceeds capacity.

System Impact
When the system is loading data, remaining data is discarded if the database is full. In
this case, the manual intervention is required to ensure the consistency between the
configuration data and the OMP loading data.

Handling Suggestion
Check the configuration, and delete the exceeding record in accordance with the
configuration table displayed in the additional information of the notification.

3-171

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

3.3.110 33610334 IMEI Check Failed

Notification Message
l Notification code: 33610334
l Notification name: IMEI check failed
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
During performing access processing or location update, the VLR does not receive any
response or receives the following responses after sending an IMEI check request to the
EIR through the MSC.
l This IMEI is in the blacklist.
l This IMEI is in the grey list.
l This IMEI is unknown.

System Impact
l If this IMEI is in the blacklist, stop providing services tor this subscriber.
l If this IMEI is in the grey list, the carrier determines whether to provide services to this
subscriber.
l If this IMEI is unknown or no response is received, the carrier handles the problem
according to the actual situations.

Handling Suggestion
1. Double-click the notification information you want to view to open the Details dialog
box. Take down the IMEI number shown in this dialog box.
l If this IMEI is in the blacklist, go to Step 2.
l If this IMEI is in the grey list, go to Step 3.
l If this IMEI is unknown, go to Step 4.
l If no response is received, go to Step 5.
2. stop providing services to this subscriber and trace his/her signaling messages. Then
check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.
3. this subscriber can use the services. The carrier determines whether to carry out a
subscriber signaling trace. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.
4. the carrier handles the problem according to the actual situations. Then check whether
the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.
5. check whether the status of the link between the VLR and the EIR is normal.

3-172

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

l Yes: Contact ZTE for help.

l No: Go to Step 6.
6. recover the link status, then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.111 33610338 VLR Received HLR Reset

Notification Message
l Notification code: 33610338
l Notification name: VLR received HLR reset
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
l The HLR where the subscribers in the VLR belong to is reset.
l The status of the HLR office is changed from disconnected to connected.

System Impact
In the VLR, the subscribers belonging to this HLR are forced to go to this HLR for location
update, which increases the load on the link between the VLR and the HLR.

Handling Suggestion
Update the location verification flag of subscribers that belongs to the HLR. Then check
whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.112 33610339 Failed to Get SCCP Address According to IMSI

Notification Message
l Notification code: 33610339
l Notification name: Failed to get SCCP address according to IMSI
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
A failure occurs in obtaining the SCCP address according to the IMSI.

System Impact
Location update fails.

3-173

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Handling Suggestion
1. In the Terminal window, run the SHOW IMSIANA command to check whether IMSI
number analysis configuration is correct.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. In the Terminal window, run the SET IMSIANA command to modify IMSI number
analysis configuration. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.113 33610342 VLR Failed to Send Reset to SGSN

Notification Message
l Notification code: 33610342
l Notification name: VLR failed to send reset to SGSN
l Severity: Minor
l Alarm type: Processing error alarm

Probable Cause
The VLR sends a Reset message to the SGSN during being restarted. If the operation
fails, the VLR sends this message again. The number of times that the message is resent
exceeds the maximum value.

System Impact
None

Handling Suggestion
In the Terminal window, run the SHOW OFCSTAT command to check whether the SGSN
office is normal.
l Yes: Contact ZTE for help.
l No: Locate and handle the problem according to "8400384 M3UA Office
Unreachable".

Related Alarm
2.3.19 8400384 M3UA Office Inaccessible

3-174

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

3.3.114 33610343 The Initiative Page Rate of Fast Load

Redistribution Exceeds the Limitation of VLR Capacity
Notification Message
l Notification code: 33610343
l Notification name: The Initiative Page Rate of Fast Load Redistribution exceeds the
limitation of VLR capacity
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
The initiative unloading rate of the fast load redistribution exceeds the maximum
processing capacity of a VLR module.

System Impact
If the paging rate of the fast load redistribution exceeds the maximum processing capacity
of a VLR module, the VLR module modifies it to the upper limit to perform unloading. It
may cause the unloading timer expiring "in advance" and terminate the unloading process,
thus failing to reach the requirements of users for unloading.

Handling Suggestion
No handling is required.

3.3.115 33610834 Received Length of ACR Has Error

Notification Message
l Notification code: 33610834
l Notification name: Received length of ACR has error
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
The OCG module receives the CDRs with an incorrect length.

System Impact
The OCG module cannot process these CDRs, which will be lost.

Handling Suggestion
This notification seldom occurs. If it appears, contact the technical support personnel of
ZTE for proper handling.

3-175

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

3.3.116 33610835 Received ACR Type Has Error

Notification Message
l Notification code: 33610835
l Notification name: Received ACR type has error
l Severity: Major
l Alarm type: Processing error alarm

Probable Cause
The OCG module receives the CDRs with an incorrect type.

System Impact
The OCG module cannot process these CDRs, which will be lost.

Handling Suggestion
This notification seldom occurs. If it appears, contact the technical support personnel of
ZTE for proper handling.

3.3.117 33611076 DAP Process Registered Successfully

Notification Information
l Notification code: 33611076
l Notification name: DAP process registered successfully
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The DAP process on the SMP module registers successfully.

System Impact
The link can be established, so the messages based on the Diameter protocol stack can
be normally sent/received.

Note:
The DAP logic module completes the access control and bearer management functions
of the adjacent point in the Diameter network. Each SMP logic module in the MGCF is
fixedly configured with one DAP logic module. The DapID is the No. of the corresponding
SMP module.

3-176

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Handling Suggestion
This notification is a normal system event, so no manual intervention is required.

3.3.118 33611077 DAP Disconnected Link Successfully

Notification Information
l Notification code: 33611077
l Notification name: DAP disconnected link successfully
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The peer end requires the local end to disconnect the Diameter link, and the Diameter link
is successfully disconnected.

System Impact
The Diameter protocol stack fails to use this link to send/receive messages.

Note:
The DAP logic module completes the access control and bearer management functions
of the adjacent point in the Diameter network. Each SMP logic module in the MGCF is
fixedly configured with one DAP logic module. The DapID is the No. of the corresponding
SMP module.

Handling Suggestion
This notification is a normal system event, so no manual intervention is required.

3.3.119 33611078 DAP Updated Link Data Successfully

Notification Information
l Notification code: 33611078
l Notification name: DAP updated link data successfully
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
After the DAP bottom-layer bearer association is available, the DAP updates link data
successfully.

3-177

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
None

Handling Suggestion
This notification is a normal system event, so no manual intervention is required.

3.3.120 33611079 Some LREG reboot

Notification Message
l Notification code: 33611079
l Notification name: Some LREG reboot.
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
Some L-REG is normally restarted during a handling process.

Note:
The L-REG that is a logical module on the logical CMP/SMP/OCG module receives the
Diameter protocol stack data synchronized from the G-REG.

System Impact
During the restart of the L-REG module, the messages based on the Diameter protocol
stack may fail to be sent.

Handling Suggestion
It is a normal system event. No handling is required.

3.3.121 33611080 GREG Changed Over Successfully

Notification Information
l Notification code: 33611080
l Notification name: GREG changed over successfully
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The standby GREG module is successfully switched to the active one.

3-178

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Note:
The G-REG is a module for synchronizing Diameter protocol stack data to each L-REG.
Each OMP module in the MGCF is fixedly configured with one G-REG logic module.
The active/standby OMPs are configured with active/standby G-REG logic modules
respectively.

System Impact
None

Handling Suggestion
This notification is a normal system event, so no manual intervention is required.

3.3.122 33611081 GREG Power on Successfully

Notification Information
l Notification code: 33611081
l Notification name: GREG power on successfully
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The GREG process on the OMP module is successfully powered on.

System Impact
None

Handling Suggestion
This notification is a normal system event, so no manual intervention is required.

3.3.123 33611082 GREG Failed to Synchronize Data to LREG

Notification Information
l Notification code: 33611082
l Notification name: GREG failed to synchronize data to LREG
l Severity: Warning
l Alarm type: Communication alarm

3-179

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Probable Cause
The G-REG fails to synchronize data to the L-REG, which is generally caused by UB
resources being exhausted.

Note:
The G-REG is a module on the OMP, which is used to synchronize Diameter protocol stack
data to each L-REG. The L-REG is a logic module on the CMP/SMP/OCG logic module,
which is used to receive the Diameter protocol stack data synchronized from the G-REG

System Impact
The messages based on the Diameter protocol stack fail to be sent/received.

Handling Suggestion
On the debugging PC, choose menus Start > Run, and the Run dialog box pops up.
Type telnet IP address of the OMP module, and click OK. The telnet window
pops up. Type the user name and password (zte/zte in general) as prompted. Then type
command stt_show_diamub to view the total number of configured UB resources and the
number of idle UB resources. If the number of idle UB resources is close to the total
number of configured UB resources, contact the ZTE technical support personnel to add
memory.

3.3.124 33611083 Some LREG on GREG module has no heartbeat

Notification Message
l Notification code: 33611083
l Notification name: Some LREG on GREG module has no heartbeat
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The LREG module synchronizing data to the GREG module has no heartbeat information.

3-180

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Note:
The G-REG is a module on the OMP, which is used to synchronize the Diameter
protocol stack data to each L-REG. The L-REG that is a logical module on the logical
CMP/SMP/OCG module (configured on the SMP module) receives the Diameter protocol
stack data synchronized from the G-REG.

System Impact
This L-REG fails to operate properly, so the messages based on the Diameter protocol
stack may fail to be sent.

Handling Suggestion
1. Check whether LREG works normally.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. Restore LREG to normal work. Then check whether the notification disappears.
l Yes: End notification handling.
l No: Contact ZTE for help.

3.3.125 33611084 LREG Failed to Register With the Process of

Master-Slave
Notification Information
l Notification code: 33611084
l Notification name: LREG failed to register with the process of master-slave
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The LREG fails to register to the master/slave process of the home board.

Note:

The L-REG is a logic module on the CMP/SMP/OCG logic module, which is used to receive
the Diameter protocol stack data synchronized from the G-REG.

3-181

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
The LREG fails to be powered on, which disables the DIAMETER protocol stack to work
normally.

Handling Suggestion
1. On the debugging PC, choose menus Start > Run, and the Run dialog box pops
up. Type telnet IP address of the OMP module, and click OK. The telnet
window pops up. Type the user name and password (zte/zte in general) as prompted.
Then type command zte to check the No. of the master/slave synchronization process.
2. In the telnet window, type command OSS_GetProcState CmsSync process No. to check
the status value of CmsSync.
l If the status value is 1, the master/slave process is in working status. In this case,
no handling is required.
l If the status value is 0, the master/slave process is not in working status. In this
case, it is required to restart the board where this notification is generated.

3.3.126 33611085 LREG Process Registered Successfully

Notification Information
l Notification code: 33611085
l Notification name: LREG process registered successfully
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The LREG process on the CMP/SMP/OCG module registers successfully.

System Impact
None

Handling Suggestion
This notification is a normal system event, so no manual intervention is required.

3.3.127 33611086 LREG Changed Over Successfully

Notification Information
l Notification code: 33611086
l Notification name: LREG changed over successfully
l Severity: Warning
l Alarm type: Communication alarm

3-182

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Probable Cause
The active/standby switchover for the LREG modules is successful.

System Impact
None

Handling Suggestion
This notification is a normal system event, so no manual intervention is required.

3.3.128 33611087 DTP Initialized Data Successfully

Notification Information
l Notification code: 3611087
l Notification name: DTP initialized data successfully
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The configuration channel (used for the GREG to synchronize data to the LREG)
successfully initializes data.

System Impact
None

Handling Suggestion
This notification is a normal system event, so no manual intervention is required.

3.3.129 33611088 DTP Failed to Get UB

Notification Information
l Notification code: 33611088
l Notification name: DTP failed to get UB
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The configuration channel (used for the GREG to synchronize data to the LREG) fails to
get UB.

3-183

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

System Impact
The service messages based on the Diameter protocol stack fail to be sent/received.

Handling Suggestion
If this notification frequently appears, it is required to check whether the load on the SMP
module is too high. Refer to “33575466 CMP Overload” for handling.

3.3.130 33611092 DEP Process Registered Successfully

Notification Information
l Notification code: 33611092
l Notification name: DEP process registered successfully
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The DEP process on the OCG module registers successfully.

Note:
The DEP logic module completes the service-related functions defined in the Diameter
protocol, including transaction management, session management, and Relay/Redirect.
Each OCG module in the MGCF is fixedly configured with one DEP logic module. The
DepID is the No. of the corresponding OCG module.

System Impact
None

Handling Suggestion
This notification is a normal system event, so no manual intervention is required.

3.3.131 33611093 DEP Changed Over Successfully

Notification Information
l Notification code: 33611093
l Notification name: DEP changed over successfully
l Severity: Warning
l Alarm type: Communication alarm

3-184

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Probable Cause
The active/standby switchover for the DEP modules is successful.

Note:
The DEP logic module completes the service-related functions defined in the Diameter
protocol, including transaction management, session management, and Relay/Redirect.
Each OCG module in the MGCF is fixedly configured with one DEP logic module. The
DepID is the No. of the corresponding OCG module. If the active/standby OCGs are
configured in the MGCF, the DEP modules are in active/standby mode.

System Impact
None

Handling Suggestion
This notification is a normal system event, so no manual intervention is required.

3.3.132 33611094 The Bear Link That DAP Used Is Available

Notification Information
l Notification code: 33611094
l Notification name: The bear link that DAP used is available
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The DAP bearer association is available.

System Impact
None

Handling Suggestion
This notification is a normal system event, so no manual intervention is required.

3.3.133 33611095 DAP Changed Over Successfully

Notification Information
l Notification code: 33611095
l Notification name: DAP changed over successfully

3-185

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The active/standby switchover for the DAP modules is successful.

Note:
The DAP logic module completes the access control and bearer management functions
of the adjacent point in the Diameter network. Each SMP logic module in the MGCF is
fixedly configured with one DAP logic module. The DapID is the No. of the corresponding
SMP module. If the active/standby SMP modules are configured, the DAP logic modules
can also be configured to active/standby mode.

System Impact
None

Handling Suggestion
This notification is a normal system event, so no manual intervention is required.

3.3.134 33611096 The Number of DEPs on GREG Module Exceeds

the Maximum
Notification Information
l Notification code: 33611096
l Notification name: The number of DEPs on GREG module exceeds the maximum
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
Each OCG module in the MGCF is fixedly configured with one DEP logic module, and the
number of DEPs on the GREG module exceeds 128.

3-186

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Note:
l The G-REG is a module on the OMP, which is used to synchronize Diameter protocol
stack data to each L-REG.
l The OCG is Offline Charging Agent logic module. It implements the Rf interface
function through interacting with the Diameter protocol stack. It is usually configured
on the SMP module with hard disks.
l The DEP logic module completes the service-related functions defined in the
Diameter protocol, including transaction management, session management, and
Relay/Redirect. Each OCG module in the MGCF is fixedly configured with one DEP
logic module. The DepID is the No. of the corresponding OCG module.

System Impact
The GREG fails to get protocol stack configuration data, and the DIAMETER protocol stack
fails to work normally.

Handling Suggestion
On the debugging PC, choose menus Start > Run, and the Run dialog box pops up.
Type telnet IP address of the OMP module, and click OK. The telnet window
pops up. Type the user name and password (zte/zte in general) as prompted. Then type
command showGlobalData to check whether DepNum (the number of DEPs) exceeds 128.
If it exceeds 128, deletes some OCG modules accordingly.

3.3.135 33611097 The Number of DAPs on GREG Module Exceeds

the Maximum
Notification Information
l Notification code: 33611097
l Notification name: The number of DAPs on GREG module exceeds the maximum
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
Each SMP module in the MGCF is fixedly configured with one DAP logic module, and the
number of DAPs on the GREG module exceeds 128.

3-187

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Note:
The G-REG is a module on the OMP, which is used to synchronize Diameter protocol stack
data to each L-REG.
The DAP logic module completes the access control and bearer management functions
of the adjacent point in the Diameter network. Each SMP logic module in the MGCF is
fixedly configured with one DAP logic module. The DapID is the No. of the corresponding
SMP module.

System Impact
The GREG fails to get protocol stack configuration data, and the DIAMETER protocol stack
fails to work normally.

Handling Suggestion
On the debugging PC, choose menus Start > Run, and the Run dialog box pops up.
Type telnet IP address of the OMP module, and click OK. The telnet window
pops up. Type the user name and password (zte/zte in general) as prompted. Then type
command showGlobalData to check whether DapNum (the number of DAPs) exceeds 128.
If it exceeds 128, deletes some SMP modules accordingly.

3.3.136 33611098 The Number of Links on GREG Module Exceeds

the Maximum
Notification Information
l Notification code: 33611098
l Notification name: The number of Links on GREG module exceeds the maximum
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
The number of Diameter links on the GREG module exceeds the maximum.

Note:
The G-REG is a module on the OMP, which is used to synchronize Diameter protocol stack
data to each L-REG.

3-188

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

System Impact
The GREG fails to get protocol stack configuration data, and the DIAMETER protocol stack
fails to work normally.

Handling Suggestion
In the Terminal window of the LMT, run the SHOW DIAMLNK command to query the
number of configured links. If the number of Diameter links exceeds 128, delete some
links to make the number not exceed 128.

3.3.137 33611099 Failed to Get UB

Notification Information
l Notification code: 33611099
l Notification name: Failed to get UB
l Severity: Warning
l Alarm type: Communication alarm

Probable Cause
A failure occurs in getting UB resources.

System Impact
The messages based on the Diameter protocol stack fail to be sent/received.

Handling Suggestion
1. In the Fault Management window of the LMT, choose the Real-time Notification
Monitoring tab. Double-click notification information, and the Details tab pops up.
Record the board No. in the Details row.
2. On the debugging PC, choose menus Start > Run, and the Run dialog box pops
up. Type telnet IP address of the OMP module, and click OK. The telnet
window pops up. Type the user name and password (zte/zte in general) as prompted.
Then type command stt_show_diamub to view the total number of configured UB
resources and the number of idle UB resources. If the number of idle UB resources
is close to the total number of configured UB resources, contact the ZTE technical
support personnel to add memory.

3.3.138 2365980933 Subscriber Login Notification

Notification Message
l Notification code: 2365980933
l Notification name: Subscriber Login Notification
l Severity: Warning

3-189

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

l Alarm type: Processing error alarm

Probable Cause
Subscriber login notification.

System Impact
None

Handling Suggestion
Check whether the login user is the maintenance person.
l Yes: No handling is required.
l No: Contact the system manager for handling.

3.3.139 2365981442 Loaded License File Will Expire

Notification Message
l Notification code: 2365981442
l Notification name: Loaded License File Will Expire
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
OMM loaded license file will exceed the valid date agreed when buying license file, and it
will expire in 15 days at most.

System Impact
This notification reminds the user that the license will expire soon. It has no impact on the
system before the license expires.

Handling Suggestion
Contact ZTE technical support personnel to upgrade the license file.

3.3.140 2365981701 Wrong CMM Type

Notification Message
l Notification code: 2365981701
l Notification name: Wrong CMM type
l Severity: Warning
l Alarm type: Processing error alarm

3-190

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Notification Message Handling

Probable Cause
Type of CMM board is wrong.

System Impact
If the CMM board type is configured wrongly, when the communication is normal, no CMM
link disconnection alarm is reported. Because the interface is different, the CMM alarm
cannot be reported.

Handling Suggestion
Confirm the CMM type and run the SET FMSNMPCFG command to re-configure it.

3.3.141 2365981702 Wrong Independent Board Type

Notification Message
l Notification code: 2365981702
l Notification name: Wrong independent board type
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
Type of independent board is wrong.

System Impact
If the independent board type is configured wrongly, when the communication is normal,
no link disconnection alarm is reported. Because the interface is different, the independent
board alarm cannot be reported.

Handling Suggestion
Confirm the independent board type and run the SET FMSNMPCFG command to
re-configure it.

3.3.142 2365981956 Synchronize NTP Time Failed

Notification Message
l Notification code: 2365981956
l Notification name: Synchronize NTP time failed
l Severity: Warning
l Alarm type: Equipment alarm

3-191

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

Probable Cause
The upper-layer NTP server is faulty, and the upper-layer backup NTP server is
automatically switched over to the current upper-layer NTP server.

System Impact
The local system time cannot be updated.

Handling Suggestion
1. Check whether the network of the upper level NTP server is normal and the NTP server
is started.
l Yes: Contact ZTE for help.
l No: Go to Step 2.
2. In the Terminal window, run the SHOW SYSLOG command to view detailed error
description and handle the problem accordingly. Then check whether the notification
still appears.

The command format is: SHOW SYSLOG:FUNCNAME="NTP";

l Yes: Contact ZTE for help.
l No: End alarm handling.

3.3.143 2365982210 Automatic Backup Succeeded

Notification Message
l Notification code: 2365982210
l Notification name: Automatic Backup Succeeded
l Severity: Warning
l Alarm type: Processing error alarm

Probable Cause
OMM automatic backup task succeeded.

System Impact
None

Handling Suggestion
No handling is required.

3-192

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Glossary
ADM
- Asynchronous Disconnected Mode
AIS
- Alarm Indication Signal
AS
- Application Server
ATCA
- Advanced Telecommunications Computing Architecture
AU
- Admininstrative Unit
CDM
- Chassis Data Module
CMM
- Chassis Management Module
CRC
- Cyclic Redundancy Check

DDF
- Digital Distribution Frame

DUNA
- Destination Unavailable
DXC
- Digital Cross Connect
FRU
- Field Replaceable Unit
HDLC
- High-level Data Link Control
IPMB
- Intelligent Platform Management Bus
LIF
- Loss of IMA Frame

LODS
- Link Out of Delay Synchronization defect
LOF
- Loss Of Frame

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

ZXUN iCX (MSCS) Alarm Handling

LOS
- Loss Of Signal
LP
- Lower order Path
LVDS
- Low Voltage Differential Signaling
M2PA
- MTP2-User Peer-to-Peer Adaptation Layer Protocol
MS
- Multiplex Section
NE
- Network Element
NTP
- Network Time Protocol
ODF
- Optical Distribution Frame

PDU
- Power Distribution Unit
PP2S
- Pulse Per 2 Seconds
RDI
- Remote Defect Indication
RUDP
- Reliable User Datagram Protocol
SCS
- System Control Subsystem
SD
- Signal Degrade

SDH
- Synchronous Digital Hierarchy
SF
- Signal Failure
SMART
- Self Monitoring Analysis and Reporting Technology
SONET
- Synchronous Optical NETwork

SSN
- Sub-System Number

II

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential

 Glossary

SST
- Subsystem Status Test
SUA
- SCCP User Adaptation
TIM
- Trace Identifier Mismatch
TIPC
- Transparent Interprocess Communication
TU
- Tributary Unit
TU-LOP
- Tributary Unit-Loss of Pointer
UNEQ
- UN-Equipped
VC
- Virtual Container

III

SJ-20120730093520-019|2012-09-30 (R1.0) ZTE Proprietary and Confidential