ZXWN MGW Alarm and Notification Information PDF

ZXWN MGW
Media Gateway
Alarm and Notification Information

Version 3.07.20
ZTE CORPORATION
ZTE Plaza, Keji Road South,
Hi-Tech Industrial Park,
Nanshan District, Shenzhen,
P. R. China
518057
Tel: (86) 755 26771900 800-9830-9830
Fax: (86) 755 26772236
URL: http://support.zte.com.cn
E-mail: doc@zte.com.cn
LEGAL INFORMATION
Copyright 2006 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Date
Revision No.
Serial No.
Reason for Issue
July 20, 2008
R1.0
sjzl20082310
First edition
ZTE CORPORATION
Values Your Comments & Suggestions!
Your opinion is of great value and will help us improve the quality of our product
documentation and offer better services to our customers.
Please fax to (86) 755-26772236 or mail to Documentation R&D Department, ZTE
CORPORATION, ZTE Plaza, A Wing, Keji Road South, Hi-Tech Industrial Park,
Shenzhen, P. R. China 518057.
Thank you for your cooperation!
Document
Name
ZXWN MGW Media Gateway Alarm and Notification Information
Product Version
V3.07.20
Document Revision
Number
Serial No.
sjzl20082310
Equipment
Installation Date
R1.0
Presentation:
(Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization,
Appearance)
Good
Your evaluation
of this
documentation
Fair
Average
Poor
Bad
N/A
Accessibility:
(Contents, Index, Headings, Numbering, Glossary)
Good
Fair
Average
Poor
Bad
N/A
Intelligibility:
(Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content)
Good
Fair
Average
Poor
Bad
N/A
Please check the suggestions which you feel can improve this documentation:
Improve the overview/introduction
Your
suggestions for
improvement of
this
documentation
Make it more concise/brief
Improve the Contents
Add more step-by-step procedures/tutorials
Improve the organization
Add more troubleshooting information
Include more figures
Make it less technical
Add more examples
Add more/better quick reference aids
Add more detail
Improve the index
Other suggestions
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
# Please feel free to write any comments on an attached sheet.
If you wish to be contacted regarding your comments, please complete the following:
Name
Company
Postcode
Address
Telephone
E-mail
This page is intentionally blank.
Contents
About This Manual ............................................................ i
Purpose ................................................................................ i
Intended Audience ................................................................. i
Prerequisite Skill and Knowledge ............................................. ii
What Is in This Manual .......................................................... ii
Conventions ......................................................................... ii
How to Get in Touch............................................................. iii
Declaration of RoHS Compliance..................................... v

Chapter 1.......................................................................... 1
Alarm Message Handling ................................................. 1
Overview .......................................................................1
Summary of Alarm Messages ............................................1
Environment Alarm ....................................................... 17
CPU Overload Alarm ............................................................ 17
Excess Temperature of CPU on Board..................................... 18
RACK Temperature over Alarm Threshold ............................... 19
RACK Temperature Lower than Alarm Threshold ...................... 20
House temperature is higher than high threshold..................... 20
House temperature is lower than low threshold ....................... 21
Voltage is higher than high threshold ..................................... 22
Voltage is lower than low threshold ....................................... 22
Humidity is higher than high threshold ................................... 23
Humidity is lower than low threshold ..................................... 23
Fault in Fan Plug-in Box ....................................................... 24
Rack Door Access Control Alarm............................................ 24
Smoke Alarm ..................................................................... 25
Infrared Alarm.................................................................... 25
Lightning Alarm .................................................................. 26
Communication Alarm.................................................... 26
Ethernet Controllers Physical Link off .................................... 26
Trunk Frame Loss................................................................27

Trunk Signal Loss ................................................................28
Trunk Alarm Indication.........................................................29
Trunk Multi-frame Loss ........................................................29
Far-End CRC Multi-frame Alarm Indication ..............................29
Far-End Alarm ....................................................................30
The Link between the OMC and the Alarm Box is Broken ...........30
Cell Delineation not Synchronized ..........................................31
Loss of Cell Delineation ........................................................31
The Link between the OMC and the NE is Broken .....................32
Communication Link between Active and Standby Boards Off.....32
Board HW Error...................................................................33
Board Does not Exist/CPU Is Long in Reset Status....................34
PWRD 485 Communicate Link Break ......................................34
External Port of Board Is Down..............................................35
DSP Port Link Down .............................................................36
Receive Bad Packet .............................................................37
PVC FAULTS .......................................................................37
Timing of Near-End IMA Group Failure....................................38
NE Group Is in Insufficient Links State....................................38
FE RXLSM Is in Unusable State..............................................39
Implementation Specific TX Fault Declared at the NE ................39
Near-End Sending Link Broken ..............................................40
LIF Alarm of Near-End Receiving Link .....................................40
LODS Alarm of Near-End Receiving Link .................................41
RDI Alarm of Near-End Receiving Link ....................................41
Near-End Receiving Link Faults..............................................42
Implementation Specific Rx Failed Declared at the NE...............42
Near-End Receiving Link Broken ............................................42
Far end TXLSM Is in Unusable State .......................................43
All High-Speed Serial Links Out of Synchronism .......................43
Control Plane Communication Abnormal Between Board and Its
Home Module .....................................................................44
MPOMP_COMM_OFF between mp and omp ..............................45
MTP3 Office Inaccessible ......................................................46
MTP3 Link Unavailable .........................................................47
MTP3 Cluster Inaccessible.....................................................48
MTP3 Link Congestion ..........................................................49
M3UA Office Inaccessible ......................................................50
SUA SSN Is Invalid ............................................................. 51

SUA Office Inaccessible........................................................ 52
M2PA Link Broken ............................................................... 53
Association Congested ......................................................... 54
An IUA Association Broken ................................................... 55
Link between Igate and NE has Broken .................................. 55
Link between Igate and LIC Has Broken ................................. 56
Link to Device Is Broken ...................................................... 56
The link Between the Native OMC and the Superior Is Broken.... 56
BFD Session Interrupted ...................................................... 57
Association Link Broken ....................................................... 57
Association Path Broken down .............................................. 59
STC Office Inaccessible ........................................................ 59
Test Pack Check Abnormal ................................................... 60
QoS Alarm ................................................................... 60

Dual Homing Office Blocked.................................................. 60
Dual Homing Link Blocked .................................................... 61
Dual Homing Association Blocked .......................................... 62
Resource Board Unable to Get Secondary Forwarding Table from
UIM .................................................................................. 62
Broadband Link Congestion .................................................. 63
Broadband Link Overload ..................................................... 64
MTP2 Link Transmission Overload.......................................... 65
MTP2 Link Reception Overload .............................................. 66
Performance Level 4 Alarm................................................... 66
QOS Alarm from PM ............................................................ 68
Inter-board Message Communication Flow Rate over Alarm
Threshold .......................................................................... 68
Equipment Alarm .......................................................... 69

Loss of Optical Transceiver Module Signal ............................... 69
Clock Phase Does not Match When Inputting 8K, 16M Clock to
Backboard ......................................................................... 70
Clock Chip of This Board Is in Preheat Status .......................... 70
Inconsistent BOOT/EPLD Version No. with Database Configurations
........................................................................................ 71
Boot Version Fails to Be Written to Backup Region ................... 71
Board Connection Check Is Off.............................................. 72
IDE Initialize Fail .................................................................72

Internal Port of Board Is Down ..............................................72
Input Clock Abnormal ..........................................................73
IDE THRESHOLD Alarm ........................................................74
Hard Disk Broken ................................................................74
ENUM Switch of Board Opened ..............................................75
SMBUS Error ......................................................................75
Error in Rear Board that Mismatches with Front Board ..............76
LVDS Signal Unlocked ..........................................................76
High Error Rate of Optical Interface........................................77
FPGA Exception...................................................................77
Hardware Reliability Down ....................................................78
The Channel in a Subcard Is Down.........................................78
Subcard Abnormal ...............................................................79
Phase-lock Loop Unlock ........................................................79
High Error Rate at E1 Bottom Layer .......................................80
Microcode Is Abnormal .........................................................80
Faulty Frames Received by Internal Switching Interface Faulty...81
Board Link-Level Flow Control ...............................................82
Automatic Protection Switching Channels Mismatched...............82
APS Protection Mode Mismatch ..............................................83
APS Reset Board .................................................................84
CLKG 32M Output Clock Lost.................................................84
CLKG 32M8K Output Clock Lost .............................................85
CLKG 16M Output Clock Lost.................................................85
CLKG 16M8K Output Clock Lost .............................................85
CLKG PP2S Output Clock Lost................................................86
PP2S Clock Reference Lost....................................................86
16CHIP Clock Reference Lost ................................................87
All Clock Bases Had Lost.......................................................87
CLKG I2MB0 Clock Base Lost.................................................87
CLKG I2MB1 Clock Base Lost.................................................88
CLKG I2MHZ0 Clock Base Lost ..............................................88
CLKG I2MHZ1 Clock Base Lost ..............................................88
CLKG I8KBASE Clock Base Lost .............................................89
CLKG I8KGPS Clock Base Lost ...............................................89
CLKG I8KUIM Clock Base Lost ...............................................89
Clock Reference Source Lost (Level 3 Alarm) ...........................90
Clock Reference Source Lost (Level 2 Alarm) ...........................90
Clock Reference Source Lost (Level 1 Alarm) .......................... 91

Clock Base Lost .................................................................. 91
The Client of Sntp Failed in Fetching Net Time......................... 92
TRUNK Is Down .................................................................. 92
OMP to NTP Server Sync Failure ............................................ 92
MAC Address Conflict Exists in Boards of Same Shelf................ 93
Type A Fault on Board (GPS) Phase-lock Equipment ................. 93
Type B Fault on Board (GPS) Phase-lock Equipment ................. 94
Phase-lock Equipment of This Board (GPS) Is in Power-on Status
........................................................................................ 94
Cx29704 Runs Abnormally ................................................... 95
The Port Connection between the GLI and the UIM Is Inconsistent
with the Configuration ......................................................... 95
Stack Overflow ................................................................... 96
Process Deadlocked............................................................. 96
IDE Version Synchronization Information................................ 96
Board Device Is Abnormal .................................................... 97
Exceptional Internal Media Plane Communication..................... 97
Loss of Clock When Input to Board ........................................ 98
SDH/SONET: Loss of Signal .................................................. 98
SDH/SONET: Loss of Frame.................................................. 99
SDH/SONET: Regenerator Section Trace Mismatch/Section Trace
Mismatch ......................................................................... 100
SDH/SONET: MS-AIS, Line Alarm Indication Signal ................ 101
SDH/SONET: Multiplex Section Far-end Reception Failure/Line Farend Reception Failure ........................................................ 101
SDH/SONET: Signal Failure ................................................ 102
SDH/SONET: Signal Deterioration ....................................... 102
SDH/SONET: Loss of AU-4 Pointer/Loss of Channel Pointer ..... 103
SDH/SONET: AU-AIS/Channel-AIS ...................................... 104
SDH/SONET: HP-Trace Mismatch/Patch Trace Mismatch ......... 104
SDH/SONET: HP Unassembled/Path Unassembled ................. 105
SDH/SONET: HP Label Mismatch/Path Label Mismatch............ 105
SDH/SONET: HP Remote Reception Failure ........................... 106
SDH/SONET: LOM ............................................................. 106
SDH/SONET: Loss of TU Pointer/Loss of Virtual Tributary Pointer
...................................................................................... 107
SDH/SONET: Tributary Unit Alarm Indication Signal/Virtual
Tributary Alarm Indication Signal ........................................ 107
SDH/SONET: LP Remote Defect Indication/Virtual Tributary
Remote Defect Indication ................................................... 108
SDH/SONET: LP-RFI/Virtual Tributary-RFI............................. 108

SDH/SONET: LP-Trace Mismatch/Virtual Tributary Trace Mismatch
...................................................................................... 109
SDH/SONET: LP-Unloaded/Virtual Tributary Unloaded............. 110
SDH/SONET: LP Label Mismatch/Virtual Tributary Label Mismatch
...................................................................................... 111
SDH/SONET: VC-4 Signal Failure ......................................... 112
SDH/SONET: VC-4 Signal Deterioration ................................ 112
SDH/SONET: MS-Remote Error Indication ............................. 113
SDH/SONET: HP-Remote Error Indication ............................. 114
Semi-fixed Connection Error ............................................... 115
T-net Center Fault ............................................................. 115
BGP Interface Down, Neighbor Link Broken ........................... 116
Incorrect OSPFv3 Virtual Interface Configuration.................... 116
Incorrect OSPFv3 Interface Configuration.............................. 117
Router ID not Configured for OSPFv3 ................................... 117
RouterID Conflict in OSPFv3 Area ........................................ 118
OMS Alarm................................................................. 118

Frequency of Warning Overload ........................................... 118
The Time in which the Designated Alarm Remains Active has
Expired ............................................................................ 119
The Time in which the Designated Alarm Remains Unacknowledged
has Expired ...................................................................... 119
Hard Disk Usage of Database Server Overload ....................... 119
CPU Usage of Application Server Overload ............................ 120
Ram Usage of Application Server Overload ............................ 120
Hard Disk Usage of Application Server Overload..................... 121
Log Table Usage of Application Server Overload..................... 121
Directory Size Exceed the Threshold..................................... 121
Link to Office Is Broken ...................................................... 122
Database Space Usage too Large ......................................... 122
User Continuously Input Invalid Password while Logining ........ 122
Processing Alarm ........................................................ 123

FLASH Device Failure Alarm ................................................ 123
The Config Data of Sntp in DBS Is Wrong.............................. 123
T Network Connection Not Conform to Configuration .............. 124
GE Routing Exceptional ...................................................... 124
DB Config Doesn't Fit for Device .......................................... 125
Alarm Due to Inconsistent Office No. .................................... 125
Alarm Due to Inconsistent Area Code ................................... 126
Alarm Due to Inconsistent MAC Address of Background OMP (OMC)

...................................................................................... 126
Alarm Due to Inconsistent IP Address of Background OMP (OMC)
...................................................................................... 127
Alarm Due to Inconsistent MP Type ..................................... 127
Start File Does Not Exist .................................................... 128
A (CPU) Subcard Is Online, but Is not Configurated by Database.
...................................................................................... 128
A (CPU) Subcard Is not Online, but Has Been Configured by
Database. ........................................................................ 129
OMP GateWay IP Different from DBs .................................... 129
OMC Server IP Different from DBs ....................................... 130
OMC Gateway Mask Different from DBs ................................ 130
OMP Config Changes ......................................................... 131
Far End Is in Starting-up State ........................................... 131
FE Reports Unacceptable Configuration Parameters (M size) .... 132
Far End Reports Unacceptable Configuration Parameters
(Unadaptable Symmetry) ................................................... 132
Far End Reports Unacceptable Configuration Parameters
(Unadaptable IMA version) ................................................. 133
Far End reports Unacceptable Configuration Parameters (Other
reasons) .......................................................................... 133
FE Is in Blocked State........................................................ 134
FE Is in Insufficient Links State ........................................... 134
Near-End IMA Group Configuration Failure............................ 134
No Response to Requesting Database for Secondary Forwarding
Table Information ............................................................. 135
No Response to Requesting the System for Secondary Forwarding
Table Port Information....................................................... 136
SCCP SSN Is Invalid .......................................................... 137
Port Work Mode Doesn't Match Settings ............................... 138
Number of Management Module Alarms Exceeds the Threshold 138
Number of Alarms over Threshold ....................................... 139
NTP Time Exceeds Threshold .............................................. 139
Routers with Conflicting System Id Exist in Network............... 140
Chapter 2...................................................................... 141

Notification Message Handling....................................141
Overview ................................................................... 141
Summary of Notification Messages ................................ 141
Notification Information ............................................... 151
Trunk Slide ...................................................................... 152
One of CPUs on One of Boards in This Shelf Resets Exceptionally

...................................................................................... 152
APS CHANGE .................................................................... 152
CPU Dead-loop.................................................................. 152
Disk Is Full ....................................................................... 153
File Operation Failure ......................................................... 153
Shortage of Timer Resources .............................................. 154
UB Resource Shortage ....................................................... 154
Full Communication Buffer Queue ........................................ 154
Transfer Functions of Message Byte Order Registered Repeatedly
...................................................................................... 154
Base Process Power on Failed.............................................. 155
Base Process Power on Time out.......................................... 155
UIM CS Changeover........................................................... 155
Notification of Active/Standby Changeover ............................ 156
FE Link Error Alarm ........................................................... 156
Board's Workmode Unsupported .......................................... 157
Notification of the Power-on Status of the Basic Process.......... 157
Port Status on GLI Media Plane Is Changed ........................... 158
485 Set Failure ................................................................. 158
Exceptional DSP Reset ....................................................... 158
Load error ........................................................................ 159
Trunk Configuration Is Inconsistent with Function of Board...... 159
Backboard Switch Set Change. ............................................ 160
Work Mode of Network Interface Changed............................. 160
Board Version Error ........................................................... 160
Doc Space Is not enough to Save VerFile .............................. 161
IDE Files Synchronization Information .................................. 161
Dbs Table Load Failure after Date of Foreground and Background
Are Synchronized .............................................................. 162
Master to Slave Sync Failure ............................................... 162
OMP to MP Sync Failure...................................................... 162
MP Data Distribution Failure................................................ 163
Failure of Saving One Table ................................................ 163
Dbs File Buffer Overflow ..................................................... 163
Notification of Modifying Data Configuration Failed ................. 164
Save File Failed in Master or Slave Path ................................ 164
OMP Fails to Perform Power-on Loading of Version Table ......... 164
DBS Require Configuration Failed......................................... 164
NID Is Not Configured........................................................ 165
NID Translation Failure ...................................................... 165

ISNI Constrained Route Information Repeat.......................... 166
ISNI Unable to Support the Route Function........................... 166
NID Route Prompt Failure................................................... 166
Wrong Message Type Use ISNI Function ............................... 167
Failed to Config Multi-channel Controller............................... 167
Failed to Config Digital Switch Chip...................................... 167
Failure in Getting Config Information from Database .............. 167
Faulty 2400 Configuration Data........................................... 168
Faulty 1200 Configuration Data........................................... 168
IP Fail to Get Route Table Head or Entry............................... 168
IP Opr Static Rte Fail: Del Srte............................................ 169
IP Has no Match Epu Globalport .......................................... 169
IP Create or Enable Ifb Fail................................................. 169
IP Rcv Epu Inform Intf Up .................................................. 169
IP Rcv Eepu Inform Intf Down............................................. 169
SCS Informs RPU that EPU Is down ..................................... 170
SCS Informs RPU that EPU Is Removed. ............................... 170
IP Opr Static Rte Fail: Add Srte. .......................................... 170
Port Configuration Failure................................................... 171
Failure in Creating PVC ...................................................... 172
Failure in Deleting PVC ...................................................... 173
IMA Group Related Operations Failure .................................. 173
IMA Link Operations Failure ................................................ 174
Some of High-Speed Serial Links out of Synchronism ............. 174
Number of SFrame with Erroneous Frame Format Exceeds
Threshold ........................................................................ 175
Number of CFrames Discarded at the CSIX Port N due to
Horizontal Check Error Exceeds Threshold ............................ 175
Number of CFrames Discarded at the CSIX Port N due to Vertical
Check Error Exceeds Threshold ........................................... 175
Number of incomplete CFrames Discarded at the CSIX Port N
Exceeds Threshold ............................................................ 176
Number of CFrames Discarded at the CSIX Port N Due to Invalid
Frame Type Exceeds Threshold ........................................... 176
Number of CFrames Discarded at the CSIX Port N due to Invalid
Frame Length Exceeds Threshold ........................................ 176
Number of Out-of-Sequence Frames Discarded exceeds the
Threshold ........................................................................ 177
Number of Discarded Frames due to CRC Check Error Exceeds
Threshold ........................................................................ 177
2400 Configuration Failure ................................................. 177
VSC872 Configuration Failure.............................................. 177

APS Protection Change Is Overtime...................................... 178
Aps Switchover Happens .................................................... 178
Level-2 Forwarding Table Initialization Failure ....................... 178
Ethernet Port Initialization on Media Plane of UIM Board Failure 179
Brs Main Config Request Timeout......................................... 179
Brs Main Epu Register Timeout ............................................ 179
Protocol Stack Process Fails to Be Powered on ....................... 179
Conflicting MAC Address on Local Office Port ......................... 180
Alarm Pool Is over in OAM ALARMMANAGER Process............... 181
OAM Frequently Receives Alarms and Notifications ................. 181
Board Self-Check Failure .................................................... 181
Board Initialization Failure .................................................. 181
Abnormal Half-Fixed Connection Changes ............................. 182
Erroneous Half-fixed Connection Data Configuration ............... 182
Master MP Power-on .......................................................... 182
MP Changeover to Master Mode........................................... 183
Swap Resource Shortage .................................................... 183
Version Switch Information ................................................. 183
Notice of Power-on Status of C51 Board/ Board Soft Reset ...... 184
Microcode Is Abnormal ....................................................... 184
Faulty 2350 Configuration Data ........................................... 184
Inconsistent CPU Version with DSP Version ........................... 184
Clock Reference Changed ................................................... 185
CLKG Reference Quality Changed ........................................ 185
CLKG Work Mode Changed ................................................. 185
Clock Source Invalidation Reason Changed ........................... 185
SCCP GT Translation Failure................................................ 186
No Message Response in the Link for a Long Time .................. 186
Successful MGW Registration .............................................. 187
MGW Registration Failure ................................................... 187
SUA GT Translation Failure ................................................. 188
M2PA Link Congested......................................................... 188
M2PA Processor Outage...................................................... 189
ASP Status Changed .......................................................... 190
AS Status Changed............................................................ 190
Receiving SIGTRAN Error Message ....................................... 190
Receiving SIGTRAN Notification Message .............................. 191
Association Establishment Failure ........................................ 191
SIG_IPI Forwards Service Messages Abnormally .................... 192

IUAs ASP State Changed ................................................... 193
IUAs AS State Changed..................................................... 193
IUA Receives an ERR Message ............................................ 194
IUA Receives an NTFY Message ........................................... 194
TCP Received RST Packet ................................................... 194
TCP Connection Aborted..................................................... 195
IP Offline Setting: Invalid Interface ..................................... 195
IP Offline Setting: Disable This IP Using No IP Unnumbered
Command Firstly............................................................... 196
IP Offline Setting: Interface Address Addition Failure.............. 196
IP Offline Setting: Failure in Writing to a Database................. 197
IP Offline Setting: IP Address Deletion Failure ....................... 197
IP Offline Setting: Invalid Address ....................................... 198
IP Offline Setting: Invalid Nexthop ...................................... 198
IP Offline Setting: Inconsistent IP Address and Subnet Mask ... 199
IP Offline Setting: Route Addition Failure .............................. 199
IP Offline Setting: No Matched Route ................................... 200
IP Offline Setting: Routing Deletion Failure ........................... 200
IP Offline Setting: Next Hop Conflicts ................................... 201
IP Offline Setting: Next Hop not Connected Directly ............... 201
IP Offline Setting: None-Existent IP Address ......................... 202
IP Offline Setting: Failure in Reading Database...................... 202
IP Offline Setting: Not an Ethernet Port ................................ 203
IP Offline Setting: MAC beyond Valid Range .......................... 203
IP Offline Setting: Incorrect MAC Type Transferred by Database
...................................................................................... 204
IP Offline Setting: The Same IP Address in the Network Section
Has Existed ...................................................................... 204
IP Offline Configuration: Invalid IP Broadcast Address ............ 205
IP Offline Configuration: One Interface Can Only Be Configured
Four IP Addresses at Most .................................................. 205
IP Offline Configuration: Parameter Imported From DB Is Null . 206
IP Offline Setting: IP Address Has Existed............................. 207
IP Offline Setting: Invalid Mask or Network Prefix .................. 207
Failure in Allocating Memory for ARP Table Instance............... 208
Failure in Allocating Memeory for ARP Table Cache................. 208
Conflicting IP Addresses..................................................... 208
Conflicting MAC Addresses in Subnet ................................... 209
RIP Neighbor Configuration Errors ....................................... 209
RIP Interface Authentication Errors ...................................... 210

RIP Neighbor Age Out ........................................................ 210
RIP Port Disabled .............................................................. 210
RIP Port Enabled ............................................................... 211
Conflicting Router ID ......................................................... 211
OSPF Virtual Link State Changed ......................................... 211
OSPF Interface State Changed ............................................ 212
Erroneous OSPF Virtual Interface Configuration ..................... 212
Erroneous OSPF Interface Configuration ............................... 212
OSPF Virtual Interface Authentication Failure......................... 213
OSPF Interface Authentication Failure................................... 213
Status of OSPF Virtual Neighbor Transfers............................. 214
Status of OSPF Neighbor Transfers....................................... 214
LSDB Overflow.................................................................. 215
Failure in Creating BGP Instance.......................................... 216
Failure in Creating BGP Neighbor ......................................... 216
Failure in Getting TCB when BGP Connection is Passively Open 216
Failure in Getting TCB when BGP Connection is Actively Started217
BGP Fails to Enable Passive Listening ................................... 217
BGP Fails to Enable Actively Started TCB .............................. 217
BGP Failed to Add Neighbor to Group ................................... 218
BGP Neighbor Failed to Read Receive Buffer .......................... 218
Neighbor Hold Timer Expires ............................................... 218
BGP Neighbor FSM Error..................................................... 218
BGP State Changed. .......................................................... 219
Courier Create BGP Fail ...................................................... 219
Courier Create OSPF Fail .................................................... 219
Courier Enable OSPF by the RTR_ID Fail ............................... 219
IP Forwarding Table Fails to Create Routes............................ 220
Incompatible RIP Version Number........................................ 220
BGP State Changed ........................................................... 221
ISIS Timer Creation Failure................................................. 221
ISIS Hello Message Authentication Failure............................. 221
ISIS LSP Message Authentication Failure .............................. 222
ISIS SNP Message Authentication Failure .............................. 223
ISIS Neighbor Status Change.............................................. 223
Abnormal Message is Received ............................................ 224
BFD Faults ....................................................................... 224
Abbreviations ............................................................... 225

Glossary........................................................................ 229
Tables ........................................................................... 233
Index ............................................................................ 235
About This Manual

Purpose
At first, thank you for choosing ZXWN wireless core network
system of ZTE Corporation!
ZXWN system is the 3G mobile communication system
developed based on the UMTS technology. ZXWN system boasts
powerful service processing capability in both CS domain and PS
domain, providing more abundant service contents. Comparing
with the GSM, ZXWN provides telecommunication services in
wider range, capable of transmitting sound, data, graphics and
other multi-media services. In addition, ZXWN has higher speed
and resource utilization rate. ZXWN wireless core network
system supports both 2G and 3G subscriber access, and
provides various services related with the 3G core network.
ZXWN MGW Media Gateway boasts the functions of media
control, providing transmission resources, and medial stream
control. ZXWN MGW is totally compatible with 3GPP R4 of June
2003, and is downward compatible with 3GPP R99 of June 2002.
ZXWN MGW not only supports the networking mode of bearer
independent of control in 3GPP R4, but also can be bound to a
MSC with ZXWN MSCS, supporting the networking mode of 3GPP
R99. Besides satisfying the requirements of constructing the
common mobile switching network, ZXWN MGW also can satisfy
the requirements of construct the No.7 signaling network and
mobile intelligent network, and can be adapted to various
complicated networking modes of the mobile switching network.
Thus the continuity development capability of the network is
improved.
The purpose of writing this manual is to enable operators to
know all alarms and notifications on ZXWN MGW NetNumen M31
(CN) Mobile Network Element Management System, and to
facilitate query during troubleshooting and daily maintenance.
Intended Audience
This manual is intended for engineers and technicians who
perform emergency maintenance activities on the ZXWN MGW.
Confidential and Proprietary Information of ZTE CORPORATION
Prerequisite Skill and Knowledge

To use this manual effectively, users should have a general
understanding of wireless telecommunications technology.
Familiarity with the following is helpful:
ZXWN MGW system and its various components
User interfaces on the ZXWN MGW
ZXWN MGW operating procedures
What Is in This Manual

This manual contains the following chapters:
TABLE 1 CHAPTER SUMM ARY
Chapter
Summary
Chapter 1, Alarm
Message Handling
Introduces the alarm information that may

appear in the ZXWN MGW system and the
related solutions
Chapter 2, Notification
Message Handling
Introduces the notification information that

may appear in the ZXWN MGW system and
the related solutions
Conventions
Typographical
Conventions
ZTE documents employ the following typographical conventions.

TABLE 2 TYPOGRAPHICAL CONVENTIONS
ii
Typeface
Meaning
Italics
References to other Manuals and documents.
Quotes
Links on screens.
Bold
Menus, menu options, function names, input

fields, radio button names, check boxes, dropdown lists, dialog box names, window names.
CAPS
Keys on the keyboard and buttons on screens

and company name.
Constant width
Text that you type, program code, files and

directory names, and function names.
[]
Optional parameters.
{}
Mandatory parameters.
Select one of the parameters that are delimited

by it.
About This Manual
Typeface
Meaning
Note: Provides additional information about a
certain topic.
Checkpoint: Indicates that a particular step needs
to be checked before proceeding further.
Tip: Indicates a suggestion or hint to make things
easier or more productive for the reader.
Mouse
Operation
Conventions
TABLE 3 MOUSE OPERATION CONVENTIONS
Typeface
Meaning
Click
Refers to clicking the primary mouse button (usually

the left mouse button) once.
Double-click
Refers to quickly clicking the primary mouse button

(usually the left mouse button) twice.
Right-click
Refers to clicking the secondary mouse button

(usually the right mouse button) once.
Drag
Refers to pressing and holding a mouse button and

moving the mouse.
How to Get in Touch

The following sections provide information on how to obtain
support for the documentation and the software.
Customer
Support
Documentation
Support
If you have problems, questions, comments, or suggestions

regarding
your
product,
contact
us
by
e-mail
at
support@zte.com.cn. You can also call our customer support
center at (86) 755 26771900 and (86) 800-9830-9830.
ZTE welcomes your comments and suggestions on the quality
and usefulness of this document. For further questions,
comments, or suggestions on the documentation, you can
contact us by e-mail at doc@zte.com.cn; or you can fax your
comments and suggestions to (86) 755 26772236. You can also
browse our website at http://support.zte.com.cn, which contains
various interesting subjects like documentation, knowledge base,
forum and service request.
iii
iv
Declaration of RoHS
Compliance
To minimize the environmental impact and take more
responsibility to the earth we live, this document shall serve as
formal declaration that the ZXWN MGW manufactured by ZTE
CORPORATION are in compliance with the Directive 2002/95/EC
of the European Parliament - RoHS (Restriction of Hazardous
Substances) with respect to the following substances:
Lead (Pb)
Mercury (Hg)
Cadmium (Cd)
Hexavalent Chromium (Cr (VI))
PolyBrominated Biphenyls (PBBs)
PolyBrominated Diphenyl Ethers (PBDEs)
The ZXWN MGW manufactured by ZTE CORPORATION meet the

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

in the ZXWN MGW system and the related solutions.
This chapter includes the following sections.
Sections
Page No.
Summary of Alarm Messages
Environment Alarm
17
Communication Alarm
26
QoS Alarm
60
Equipment Alarm
69
OMS Alarm
118
Processing Alarm
123
Summary of Alarm
Messages
Alarm messages are the information prompt for the problems or
faults that occur during the operation of the ZXWN MGW. Usually,
alarm messages last a time and do not disappear until the
corresponding problems or faults are cleared. Based on severity,
alarm messages can be classified into 4 levels: critical alarms,
major alarms, minor alarms and warning. The alarm severity can
be modified in the NMS as required. Table 4 shows all the
possible alarm description that may occur in the NMS of the
MGW. For the alarms at different levels, different measures
should be taken. In the case of critical and major alarm
messages, contact ZTE Corporations local office as soon as
possible and handle the problems under the guidance of ZTEs

engineers. In the case of minor and warning alarm messages,
the maintenance personnel of the equipment room can solve the
problems according to the steps recommended by this article
after making a record about the problem/fault symptoms.
Contact ZTE Corporations local office as soon as possible for any
problem.
TABLE 4 SUMM ARY OF AL ARM MESSAGES
Alarm Type
Alarm
Code
System
Type
Default
Severity
Alarm
Description
Environment
Alarm
2560
MP NE
Equipment
Alarm
Major
CPU Overload
Alarm
Environment
Alarm
2561
MP NE
Equipment
Alarm
Major
Excess
Temperature of
CPU on Board
Environment
Alarm
25856
MP NE
Equipment
Alarm
Minor
RACK
Temperature over
Alarm Threshold
25857
MP NE
Equipment
Alarm
Minor
RACK
Temperature
Lower than Alarm
Threshold
25858
MP NE
Equipment
Alarm
Minor
House
temperature is
higher than high
threshold
Environment
Alarm
25859
MP NE
Equipment
Alarm
Minor
House
temperature is
lower than low
threshold
Environment
Alarm
25860
MP NE
Equipment
Alarm
Minor
Voltage is higher
than high
threshold
Environment
Alarm
25861
MP NE
Equipment
Alarm
Minor
Voltage is lower
than low threshold
Environment
Alarm
25862
MP NE
Equipment
Alarm
Minor
Humidity is higher
than high
threshold
Environment
Alarm
25863
MP NE
Equipment
Alarm
Minor
Humidity is lower
than low threshold
Environment
Alarm
25864
MP NE
Equipment
Alarm
Minor
Fault in Fan Plugin Box
Environment
Alarm
25865
MP NE
Equipment
Alarm
Minor
Rack Door Access

Control Alarm
Environment
Alarm
Environment
Alarm
Chapter 1 Alarm Message Handling
Alarm Type
Alarm
Code
System
Type
Default
Severity
Alarm
Description
Environment
Alarm
25866
MP NE
Equipment
Alarm
Minor
Smoke Alarm
Environment
Alarm
25867
MP NE
Equipment
Alarm
Minor
Infrared Alarm
Environment
Alarm
25868
MP NE
Equipment
Alarm
Minor
Lightning Alarm
Communicati
on Alarm
Polling Link
Alarm
Major
Link to Device Is
Broken
Communicati
on Alarm
256
MP NE
Equipment
Alarm
Major
Ethernet
Controllers
Physical Link off
Communicati
on Alarm
512
MP NE
Equipment
Alarm
Warning
Trunk Frame Los
Communicati
on Alarm
513
MP NE
Equipment
Alarm
Warning
Trunk Signal Loss
Communicati
on Alarm
514
MP NE
Equipment
Alarm
Warning
Trunk Alarm
Indication
Communicati
on Alarm
515
MP NE
Equipment
Alarm
Warning
Trunk Multi-frame
Los
Communicati
on Alarm
516
MP NE
Equipment
Alarm
Warning
Far-End CRC
Multi-frame Alarm
Indication
Communicati
on Alarm
517
MP NE
Equipment
Alarm
Warning
Far-End Alarm
1000
AlarmBox
Link Break
Alarm
Critical
The Link between

the OMC and the
Alarm Box is
Broken
Communicati
on Alarm
1000
Broken
Link with
Superior
OMC
Critical
The link Between

the Native OMC
and the Superior
Is Broken
Communicati
on Alarm
1000
Link Alarm
Critical
The Link between

the OMC and the
NE is Broken
Communicati
on Alarm
1024
MP NE
Equipment
Alarm
Warning
Cell Delineation
not Synchronized
Communicati
on Alarm
Alarm Type
Alarm
Code
System
Type
Default
Severity
Alarm
Description
Communicati
on Alarm
1025
MP NE
Equipment
Alarm
Warning
Loss of Cell
Delineation
Communicati
on Alarm
5122
MP NE
Equipment
Alarm
Minor
Communication
Link between
Active and
Standby Boards
Off
Communicati
on Alarm
5378
MP NE
Equipment
Alarm
Major
Board HW Error
Communicati
on Alarm
5379
MP NE
Equipment
Alarm
Major
Board Does not

Exist/CPU Is Long
in Reset Status
Communicati
on Alarm
5382
MP NE
Equipment
Alarm
Major
PWRD 485
Communicate Link
Break
Communicati
on Alarm
5395
MP NE
Equipment
Alarm
Major
External Port of
Board Is Down
Communicati
on Alarm
5401
MP NE
Equipment
Alarm
Major
Test Pack Check

Abnormal
Communicati
on Alarm
5641
MP NE
Equipment
Alarm
Critical
DSP Port Link

Down
Communicati
on Alarm
15616
MP NE
Equipment
Alarm
Minor
Receive Bad
Packet
Communicati
on Alarm
18944
MP NE
Equipment
Alarm
Minor
PVC FAULTS
Communicati
on Alarm
19208
MP NE
Equipment
Alarm
Major
Timing of NearEnd IMA Group

Failure
Communicati
on Alarm
19209
MP NE
Equipment
Alarm
Major
NE Group Is in
Insufficient Links
State
Communicati
on Alarm
19210
MP NE
Equipment
Alarm
Major
FE RXLSM Is in
Unusable State
Communicati
on Alarm
19211
MP NE
Equipment
Alarm
Major
Implementation
Specific TX Fault
Declared at the
NE
Communicati
on Alarm
19212
MP NE
Equipment
Alarm
Major
Near-End Sending
Link Broken
Alarm Type
Alarm
Code
System
Type
Default
Severity
Alarm
Description
Communicati
on Alarm
19213
MP NE
Equipment
Alarm
Major
LIF Alarm of NearEnd Receiving

Link
Communicati
on Alarm
19214
MP NE
Equipment
Alarm
Major
LODS Alarm of
Near-End
Receiving Link
Communicati
on Alarm
19215
MP NE
Equipment
Alarm
Major
RDI Alarm of
Near-End
Receiving Link
Communicati
on Alarm
19216
MP NE
Equipment
Alarm
Major
Near-End
Receiving Link
Faults
Communicati
on Alarm
19217
MP NE
Equipment
Alarm
Major
Implementation
Specific Rx Failed
Declared at the
NE
Communicati
on Alarm
19218
MP NE
Equipment
Alarm
Major
Near-End
Receiving Link
Broken
Communicati
on Alarm
19219
MP NE
Equipment
Alarm
Major
Far end TXLSM Is

in Unusable State
Communicati
on Alarm
19456
MP NE
Equipment
Alarm
Critical
All High-Speed
Serial Links Out of
Synchronism
Communicati
on Alarm
22784
MP NE
Equipment
Alarm
Major
BFD Session
Interrupted
Communicati
on Alarm
83939
85
MP NE
Equipment
Alarm
Major
Control Plane
Communication
Abnormal
Between Board
and Its Home
Module
Communicati
on Alarm
83939
88
MP NE
Equipment
Alarm
Major
MPOMP_COMM_O
FF between mp
and omp
Communicati
on Alarm
84001
28
MP NE
Equipment
Alarm
Major
MTP3 Office
Inaccessible
Communicati
on Alarm
84001
29
MP NE
Equipment
Alarm
Minor
MTP3 Link
Communicati
on Alarm
84001
30
MP NE
Equipment
Alarm
Major
MTP3 Cluster
Inaccessible
Alarm Type
Alarm
Code
System
Type
Default
Severity
Alarm
Description
Communicati
on Alarm
84001
31
MP NE
Equipment
Alarm
Major
MTP3 Link
Congestion
Communicati
on Alarm
84003
84
MP NE
Equipment
Alarm
Major
M3UA Office
Inaccessible
Communicati
on Alarm
84011
52
MP NE
Equipment
Alarm
Minor
SUA SSN Is
Invalid
Communicati
on Alarm
84011
53
MP NE
Equipment
Alarm
Major
SUA Office
Inaccessible
Communicati
on Alarm
84021
77
MP NE
Equipment
Alarm
Minor
M2PA Link Broken
Communicati
on Alarm
84026
88
MP NE
Equipment
Alarm
Minor
Association
Congested
Communicati
on Alarm
84026
90
MP NE
Equipment
Alarm
Major
Association Link
Broken
Communicati
on Alarm
84026
91
MP NE
Equipment
Alarm
Minor
Association Path
Broken down
Communicati
on Alarm
84029
44
MP NE
Equipment
Alarm
Major
STC Office
Inaccessible
Communicati
on Alarm
33575
462
MP NE
Equipment
Alarm
Minor
An IUA
Association
Broken
Communicati
on Alarm
33576
732
Monitoring
Server
Alarm
Major
Link between
Igate and NE has
Broken
Communicati
on Alarm
33576
733
Monitoring
Server
Alarm
Major
Link between
Igate and LIC Has
Broken
QoS Alarm
14592
MP NE
Equipment
Alarm
Minor
Dual Homing
Office Blocked
QoS Alarm
14593
MP NE
Equipment
Alarm
Minor
Dual Homing Link

Blocked
QoS Alarm
14594
MP NE
Equipment
Alarm
Minor
Dual Homing
Association
Blocked
Alarm
Code
System
Type
Default
Severity
Alarm
Description
19970
MP NE
Equipment
Alarm
Major
Resource Board
Unable to Get
Secondary
Forwarding Table
from UIM
23296
MP NE
Equipment
Alarm
Minor
Inter-board
Message
Communication
Flow Rate over
Alarm Threshold
QoS Alarm
QoS Alarm
83991
04
MP NE
Equipment
Alarm
Minor
Broadband Link
Congestion
QoS Alarm
83991
05
MP NE
Equipment
Alarm
Minor
Broadband Link
Overload
QoS Alarm
83998
72
MP NE
Equipment
Alarm
Major
MTP2 Link
Transmission
Overload
QoS Alarm
83998
73
MP NE
Equipment
Alarm
Major
MTP2 Link
Reception
Overload
QoS Alarm
33575
632
CN
Performanc
e Manager
Warning
Performance Level
4 Alarm
QoS Alarm
33575
633
CN
Performanc
e Manager
Minor
Performance Level
3 Alarm
QoS Alarm
33575
634
CN
Performanc
e Manager
Major
Performance Level
2 Alarm
QoS Alarm
33575
635
CN
Performanc
e Manager
Critical
Performance Level
1 Alarm
QoS Alarm
33575
636
CN
Performanc
e Manager
Unknown
QOS Alarm from

PM
Equipment
Alarm
MP NE
Equipment
Alarm
Major
Loss of Optical
Transceiver
Module Signal
Equipment
Alarm
1284
MP NE
Equipment
Alarm
Minor
Clock Phase Does

not Match When
Inputting 8K, 16M
Clock to
Backboard
Equipment
Alarm
1285
MP NE
Equipment
Alarm
Minor
Clock Chip of This

Board Is in
Preheat Status
Alarm Type
QoS Alarm
Alarm Type
Alarm
Code
System
Type
Default
Severity
Alarm
Description
Equipment
Alarm
1286
MP NE
Equipment
Alarm
Minor
Loss of Clock
When Input to
Board
Equipment
Alarm
1792
MP NE
Equipment
Alarm
Major
SDH/SONET: Loss
of Signal
Equipment
Alarm
1793
MP NE
Equipment
Alarm
Major
SDH/SONET: Loss
of Frame
Equipment
Alarm
1794
MP NE
Equipment
Alarm
Major
SDH/SONET:
Regenerator
Section Trace
Mismatch
Equipment
Alarm
1795
MP NE
Equipment
Alarm
Major
SDH/SONET: MSAIS, Line Alarm

Indication Signal
Equipment
Alarm
1796
MP NE
Equipment
Alarm
Minor
SDH/SONET:
Multiplex Section
Far-end Reception
Failure/Line Farend Reception
Failure
Equipment
Alarm
1797
MP NE
Equipment
Alarm
Major
SDH/SONET:
Signal Failure
Equipment
Alarm
1798
MP NE
Equipment
Alarm
Minor
SDH/SONET:
Signal
Deterioration
Equipment
Alarm
1799
MP NE
Equipment
Alarm
Minor
SDH/SONET: Loss
of AU-4 Pointer
Equipment
Alarm
1800
MP NE
Equipment
Alarm
Minor
SDH/SONET: AUAIS/Channel-AIS
Equipment
Alarm
1801
MP NE
Equipment
Alarm
Minor
SDH/SONET: HPTrace Mismatch
Equipment
Alarm
1802
MP NE
Equipment
Alarm
Minor
SDH/SONET: HP
Unassembled/Path
Unassembled
Equipment
Alarm
1803
MP NE
Equipment
Alarm
Minor
SDH/SONET: HP
Label
Mismatch/Path
Label Mismatch
Equipment
Alarm
1804
MP NE
Equipment
Alarm
Minor
SDH/SONET: HP
Remote Reception
Failure
Alarm Type
Alarm
Code
System
Type
Default
Severity
Alarm
Description
Equipment
Alarm
1805
MP NE
Equipment
Alarm
Major
SDH/SONET: LOM
1806
MP NE
Equipment
Alarm
Warning
SDH/SONET: Loss
of TU Pointer/Loss
of Virtual
Tributary Pointer
1807
MP NE
Equipment
Alarm
Warning
SDH/SONET:
Tributary Unit
Alarm Indication
Signal
Equipment
Alarm
1808
MP NE
Equipment
Alarm
Warning
SDH/SONET: LP
Remote Defect
Indication/Virtual
Tributary Remote
Defect Indication
Equipment
Alarm
1809
MP NE
Equipment
Alarm
Warning
SDH/SONET: LPRFI/Virtual
Tributary-RFI
1810
MP NE
Equipment
Alarm
Warning
SDH/SONET: LPTrace
Mismatch/Virtual
Tributary Trace
Mismatch
1811
MP NE
Equipment
Alarm
Warning
SDH/SONET: LPUnloaded/Virtual
Tributary
Unloaded
Equipment
Alarm
1812
MP NE
Equipment
Alarm
Warning
SDH/SONET: LP
Label
Mismatch/Virtual
Tributary Label
Mismatch
Equipment
Alarm
1814
MP NE
Equipment
Alarm
Major
SDH/SONET: VC-4
Signal Failure
Equipment
Alarm
1815
MP NE
Equipment
Alarm
Minor
SDH/SONET: VC-4
Signal
Deterioration
Equipment
Alarm
1820
MP NE
Equipment
Alarm
Major
SDH/SONET: MSRemote Error

Indication
Equipment
Alarm
1821
MP NE
Equipment
Alarm
Major
SDH/SONET: HPRemote Error

Indication
Equipment
Alarm
2624
MP NE
Equipment
Alarm
Minor
Stack Overflow
Equipment
Alarm
Equipment
Alarm
Equipment
Alarm
Equipment
Alarm
10
Alarm Type
Alarm
Code
System
Type
Default
Severity
Alarm
Description
Equipment
Alarm
2625
MP NE
Equipment
Alarm
Minor
Process
Deadlocked
Equipment
Alarm
3072
MP NE
Equipment
Alarm
Major
IDE Initialize Fail
Equipment
Alarm
5187
MP NE
Equipment
Alarm
Minor
The Port
Connection
between the GLI
and the UIM Is
Inconsistent with
the Configuration
Equipment
Alarm
5376
MP NE
Equipment
Alarm
Major
Internal Port of
Board Is Down
Equipment
Alarm
5381
MP NE
Equipment
Alarm
Major
Input Clock
Abnormal
Equipment
Alarm
5396
MP NE
Equipment
Alarm
Major
Exceptional
Internal Media
Plane
Communication
Equipment
Alarm
5632
MP NE
Equipment
Alarm
Critical
IDE THRESHOLD
Alarm
Equipment
Alarm
5633
MP NE
Equipment
Alarm
Critical
Hard Disk Broken
Equipment
Alarm
5635
MP NE
Equipment
Alarm
Critical
ENUM Switch of
Board Open
Equipment
Alarm
5636
MP NE
Equipment
Alarm
Critical
SMBUS Error
Equipment
Alarm
5637
MP NE
Equipment
Alarm
Critical
Error in Rear
Board that
Mismatches with
Front Board
Equipment
Alarm
5638
MP NE
Equipment
Alarm
Major
LVDS Signal
Unlocked
Equipment
Alarm
5639
MP NE
Equipment
Alarm
Major
High Error Rate of

Optical Interface
Equipment
Alarm
5640
MP NE
Equipment
Alarm
Major
FPGA Exception
Alarm Type
Alarm
Code
System
Type
Default
Severity
Alarm
Description
Equipment
Alarm
5642
MP NE
Equipment
Alarm
Major
Hardware
Reliability Down
Equipment
Alarm
5644
MP NE
Equipment
Alarm
Minor
The Channel in a
Subcard Is Down
Equipment
Alarm
5645
MP NE
Equipment
Alarm
Critical
Subcard Abnormal
Equipment
Alarm
5646
MP NE
Equipment
Alarm
Critical
Phase-lock Loop
Unlock
Equipment
Alarm
5647
MP NE
Equipment
Alarm
Critical
High Error Rate at

E1 Bottom Layer
5650
MP NE
Equipment
Alarm
Minor
MAC Address
Conflict Exists in
Boards of Same
Shelf
5652
MP NE
Equipment
Alarm
Critical
Type A Fault on
Board (GPS)
Phase-lock
Equipment
5653
MP NE
Equipment
Alarm
Major
Type B Fault on
Board (GPS)
Phase-lock
Equipment
Equipment
Alarm
5654
MP NE
Equipment
Alarm
Critical
Phase-lock
Equipment of This
Board (GPS) Is in
Power-on Status
Equipment
Alarm
5663
MP NE
Equipment
Alarm
Major
Board Device Is
Abnormal
Equipment
Alarm
5891
MP NE
Equipment
Alarm
Minor
Inconsistent
BOOT/EPLD
Version No. with
Database
Configurations
Equipment
Alarm
5892
MP NE
Equipment
Alarm
Minor
Boot Version Fails

to Be Written to
Backup Region
Equipment
Alarm
5960
MP NE
Equipment
Alarm
Minor
IDE Version
Synchronization
Information
Equipment
Alarm
6400
MP NE
Equipment
Alarm
Minor
Cx29704 Runs
Abnormally
Equipment
Alarm
Equipment
Alarm
Equipment
Alarm
11
12
Alarm Type
Alarm
Code
System
Type
Default
Severity
Alarm
Description
Equipment
Alarm
15360
MP NE
Equipment
Alarm
Critical
Microcode Is
Abnormal
Equipment
Alarm
15873
MP NE
Equipment
Alarm
Critical
Faulty Frames
Received by
Internal Switching
Interface Faulty
Equipment
Alarm
15874
MP NE
Equipment
Alarm
Critical
Board Link-Level
Flow Control
Equipment
Alarm
19712
MP NE
Equipment
Alarm
Major
Automatic
Protection
Switching
Channels
Mismatched
Equipment
Alarm
19713
MP NE
Equipment
Alarm
Major
APS Protection
Mode Mismatch
Equipment
Alarm
19714
MP NE
Equipment
Alarm
Major
APS Reset Board
Equipment
Alarm
21585
MP NE
Equipment
Alarm
Major
BGP Interface
Down, Neighbor
Link Broken
Equipment
Alarm
25602
MP NE
Equipment
Alarm
Minor
Semi-fixed
Connection Error
Equipment
Alarm
28224
MP NE
Equipment
Alarm
Minor
RouterID Conflict
in OSPFv3 Area
Equipment
Alarm
28227
MP NE
Equipment
Alarm
Minor
Incorrect OSPFv3
Virtual Interface
Configuration
Equipment
Alarm
28228
MP NE
Equipment
Alarm
Minor
Incorrect OSPFv3
Interface
Configuration
Equipment
Alarm
28231
MP NE
Equipment
Alarm
Minor
Router ID not
Configured for
OSPFv3
Equipment
Alarm
25600
MP NE
Equipment
Alarm
Warning
Board Connection
Check Is Off
Equipment
Alarm
26112
MP NE
Equipment
Alarm
Major
CLKG 32M Output

Clock Lost
Equipment
Alarm
26113
MP NE
Equipment
Alarm
Major
CLKG 32M8K
Output Clock Lost
Alarm Type
Alarm
Code
System
Type
Default
Severity
Alarm
Description
Equipment
Alarm
26114
MP NE
Equipment
Alarm
Major
CLKG 16M Output

Clock Lost
Equipment
Alarm
26115
MP NE
Equipment
Alarm
Major
CLKG 16M8K
Output Clock Lost
Equipment
Alarm
26116
MP NE
Equipment
Alarm
Major
CLKG PP2S
Output Clock Lost
Equipment
Alarm
26117
MP NE
Equipment
Alarm
Major
PP2S Clock
Reference Lost
Equipment
Alarm
26118
MP NE
Equipment
Alarm
Major
16CHIP Clock
Reference Lost
Equipment
Alarm
26119
MP NE
Equipment
Alarm
Major
All Clock Bases

Had Lost
Equipment
Alarm
26120
MP NE
Equipment
Alarm
Minor
CLKG I2MB0 Clock

Base Lost
Equipment
Alarm
26121
MP NE
Equipment
Alarm
Minor
CLKG I2MB1 Clock

Base Lost
Equipment
Alarm
26122
MP NE
Equipment
Alarm
Minor
CLKG I2MHZ0
Clock Base Lost
Equipment
Alarm
26123
MP NE
Equipment
Alarm
Minor
CLKG I2MHZ1
Clock Base Lost
Equipment
Alarm
26124
MP NE
Equipment
Alarm
Minor
CLKG I8KBASE
Clock Base Lost
Equipment
Alarm
26125
MP NE
Equipment
Alarm
Minor
CLKG I8KGPS
Clock Base Lost
Equipment
Alarm
26126
MP NE
Equipment
Alarm
Minor
CLKG I8KUIM
Clock Base Lost
Equipment
Alarm
26127
MP NE
Equipment
Alarm
Minor
Clock Reference
Source Lost
Equipment
Alarm
26128
MP NE
Equipment
Alarm
Major
Clock Reference
Source Lost (Level
2 Alarm)
Equipment
Alarm
26129
MP NE
Equipment
Alarm
Critical
Clock Reference
Source Lost (Level
1 Alarm)
13
Alarm Type
Alarm
Code
System
Type
Default
Severity
Alarm
Description
Equipment
Alarm
26130
MP NE
Equipment
Alarm
Minor
Clock Base Lost
Equipment
Alarm
83927
05
MP NE
Equipment
Alarm
Minor
The Client of Sntp

Failed in Fetching
Net Time
Equipment
Alarm
83940
08
MP NE
Equipment
Alarm
Major
T-net Center Fault
Equipment
Alarm
83942
42
MP NE
Equipment
Alarm
Minor
TRUNK Is Down
Equipment
Alarm
33554
432
MP NE
Equipment
Alarm
Minor
OMP to NTP
Server Sync
Failure
OMS Alarm
Correlation
Alarm
Unknown
Frequency of
Warning Overload
Correlation
Alarm
Unknown
The Time in which

the Designated
Alarm Remains
Active has Expired
Unknown
The Time in which

the Designated
Alarm Remains
Unacknowledged
has Expired
OMS Alarm
Correlation
Alarm
OMS Alarm
1000
Security
Alarm
Major
User Continuously
Input Invalid
Password while
Logining
OMS Alarm
1001
System
Manageme
nt
Unknown
Hard Disk Usage

of Database
Server Overload
OMS Alarm
1002
System
Manageme
nt
Major
CPU Usage of
Application Server
Overload
OMS Alarm
1003
System
Manageme
nt
Major
Ram Usage of
Application Server
Overload
OMS Alarm
1004
System
Manageme
nt
Major
Hard Disk Usage

of Application
Server Overload
OMS Alarm
1005
System
Manageme
nt
Major
Log Table Usage

of Application
Server Overload
OMS Alarm
1006
System
Manageme
nt
Major
Directory Size
Exceed the
Threshold
OMS Alarm
14
Alarm Type
Alarm
Code
System
Type
Default
Severity
Alarm
Description
OMS Alarm
1007
System
Manageme
nt
Major
Link to Office Is
Broken
OMS Alarm
1008
System
Manageme
nt
Unknown
Database Space
Usage too Large
Processing
Alarm
3073
MP NE
Equipment
Alarm
Major
FLASH Device
Failure Alarm
Processing
Alarm
4096
MP NE
Equipment
Alarm
Minor
The Config Data

of Sntp in DBS Is
Wrong
Processing
Alarm
5120
MP NE
Equipment
Alarm
Minor
T Network
Connection Not
Conform to
Configuration
Processing
Alarm
5121
MP NE
Equipment
Alarm
Minor
GE Routing
Exceptional
Processing
Alarm
5123
MP NE
Equipment
Alarm
Minor
DB Config Doesn't
Fit for Device
Processing
Alarm
5383
MP NE
Equipment
Alarm
Major
Alarm Due to
Inconsistent Office
No.
Processing
Alarm
5384
MP NE
Equipment
Alarm
Major
Alarm Due to
Inconsistent Area
Code
5385
MP NE
Equipment
Alarm
Major
Alarm Due to
Inconsistent MAC
Address of
Background OMP
(OMC)
Processing
Alarm
5386
MP NE
Equipment
Alarm
Major
Alarm Due to
Inconsistent IP
Address of
Background OMP
(OMC)
Processing
Alarm
5387
MP NE
Equipment
Alarm
Major
Alarm Due to
Inconsistent MP
Type
Processing
Alarm
5388
MP NE
Equipment
Alarm
Major
Start File Does

Not Exist
5389
MP NE
Equipment
Alarm
Warning
A (CPU) Subcard
Is Online, but Is
not Configurated
by Database.
Processing
Alarm
Processing
Alarm
15
Alarm
Code
System
Type
Default
Severity
Alarm
Description
5390
MP NE
Equipment
Alarm
Major
A (CPU) Subcard
Is not Online, but
Has Been
Configured by
Database.
Processing
Alarm
Processing
Alarm
5391
MP NE
Equipment
Alarm
Major
OMP GateWay IP
Different from
DBs
Processing
Alarm
5392
MP NE
Equipment
Alarm
Major
OMC Server IP
Different from
DBs
Processing
Alarm
5393
MP NE
Equipment
Alarm
Major
OMC Gateway
Mask Different
from DBs
Processing
Alarm
5394
MP NE
Equipment
Alarm
Critical
OMP Config
Changes
Processing
Alarm
5649
MP NE
Equipment
Alarm
Major
Port Work Mode

Doesn't Match
Settings
Processing
Alarm
19200
MP NE
Equipment
Alarm
Major
Far End Is in
Starting-up State
19201
MP NE
Equipment
Alarm
Major
FE Reports
Unacceptable
Configuration
Parameters (M
size)
Major
Far End Reports

Unacceptable
Configuration
Parameters
(Unadaptable
Symmetry)
Major
Far End Reports

Unacceptable
Configuration
Parameters
(Unadaptable IMA
version)
Alarm Type
Processing
Alarm
Processing
Alarm
MP NE
Equipment
Alarm
19203
MP NE
Equipment
Alarm
Processing
Alarm
19204
MP NE
Equipment
Alarm
Major
Far End reports

Unacceptable
Configuration
Parameters (Other
reasons)
Processing
Alarm
19205
MP NE
Equipment
Alarm
Major
FE Is in Blocked
State
Processing
Alarm
16
19202
Alarm Type
Alarm
Code
System
Type
Default
Severity
Alarm
Description
Processing
Alarm
19206
MP NE
Equipment
Alarm
Major
FE Is in
Insufficient Links
State
19207
MP NE
Equipment
Alarm
Major
Near-End IMA
Group
Configuration
Failure
Major
No Response to
Requesting
Database for
Secondary
Forwarding Table
Information
Processing
Alarm
Processing
Alarm
19968
MP NE
Equipment
Alarm
Processing
Alarm
19969
MP NE
Equipment
Alarm
Major
No Response to
Requesting the
System for
Secondary
Forwarding Table
Port Information
Processing
Alarm
23040
MP NE
Equipment
Alarm
Major
Number of Alarms
over Threshold
Processing
Alarm
22598
MP NE
Equipment
Alarm
Minor
Routers with
Conflicting System
Id Exist in
Network
Processing
Alarm
83927
06
MP NE
Equipment
Alarm
Minor
NTP Time Exceeds

Threshold
Processing
Alarm
83988
48
MP NE
Equipment
Alarm
Minor
SCCP SSN Is
Invalid
84116
49
MP NE
Equipment
Alarm
Major
Number of
Management
Module Alarms
Exceeds the
Threshold
Processing
Alarm
Environment Alarm
This section introduces the environment alarm description.
CPU Overload Alarm

Alarm
Information
Alarm code: 2560
17
Reason
System type: MP NE Equipment Alarm
Severity: Major
Alarm description: The CPU usage is too high.
1. When the upper-layer service traffic is huge, the CPU usage

is too high and may exceed the threshold of CPU occupancy.
2. The set threshold value of the CPU overload alarm is small.
Peocessing
Method
1. Query the threshold value of the CPU overload alarm through

the background to see whether the set value is small.
Y-> Reset the threshold value if it is small and then wait for
30 seconds to see whether the alarm disappears. Y-> End.
N-> Goto step 2.
N-> Goto Step 2.
2. Do nothing but wait for the system to recover itself.
After waiting for 30 seconds, check whether the alarm
disappears.
Y-> End.
N-> Goto Step 3.
3. Check the system to see whether the service in process is
busy.
i.
Check whether the current service is busy, or if there is

any software being downloaded.
Y-> Goto Step 2.
N->Goto Step 4.
ii. Wait until the current service processing ends.

Wait until the current service processing or software
downloading ends, and then check whether the alarm
disappears.
Y-> End.
N-> Goto Step 4.
4. Contact ZTE Corporation.
Verification
The alarm disappears and the system works normally.
Precautions
None
Excess Temperature of CPU on

Board
Alarm
Information
18
Alarm code: 2561
Severity: Major
Reason
Alarm description: The CPU temperature is too high.
1. The fans do not work normally or are insufficient.

2. The temperature in the equipment room is too high.
Processing
Method
1.
Check whether the fans work normally.

i.
Check whether the fans are insufficient.

Y-> Add some fans and power on them. After waiting for
10 minutes, check whether the alarm disappears. Y->
End. N-> Goto step 2.
N-> Goto Step 2.
ii. Check whether all the fans are powered on.

Y-> Goto Step 2.
N-> Power on them. After powering on the fans, wait for
10 minutes and then check whether the alarm disappears.
Y-> End. N-> Goto step 2.
2. Check whether the temperature in the equipment room is too
high at that time.
Y-> Improve ventilation and take other measures to reduce
the temperature in the equipment room. After the
temperature reduces to a normal range, check whether the
alarm disappears. Y-> End. N-> Goto step 3.
N-> Goto Step 3.
Verification
The alarm disappears and the temperature is within the normal

range.
Precautions
Too high temperature may cause that the CPU is automatically

reset.
RACK Temperature over Alarm

Threshold
Alarm
Information
Alarm code: 25856
Severity: Minor
Reason
Processing
Method
Alarm description: The temperature of the rack exceeds the

high threshold.
The temperature of the rack exceeds the pre-set high threshold.

1. Check whether the pre-set high threshold
temperature on the background is rational.
for
rack
Y->Goto step 2
19
N-> Modify the high threshold for the rack temperature, and
synchronize it to the foreground. Observe whether the alarm
disappears. Y-> End. N-> Goto step 2.
2. Cool the rack. Observer whether the alarm disappears.
Y-> End.
N-> Contact ZTE Corporation.
Verification
The alarm disappears, and the temperature in the equipment

room and that of the rack are within the normal range.
Precautions
None.
RACK Temperature Lower than

Alarm Threshold
Alarm
Information
Alarm code: 25857
Severity: Minor
Reason
Processing
Method
Alarm description: The temperature of the rack is lower than

the low threshold.
The temperature of the rack is lower than the pre-set low

threshold.
1. Check whether the low threshold configured
background for rack temperature is rational.
in
the
Y-> Goto Step 2.

N-> Modify the low threshold and synchronize it to the
foreground. Check whether the alarm disappears. Y-> End.
N-> Goto step 2.
2. Increase the temperature of the rack and check whether the
alarm disappears.
Y->End.
N->Contact ZTE Corporation.
Verification

room and that of the rack are within the normal range.
Precautions
None.
House temperature is higher than

high threshold
Alarm
Information
20
Alarm code: 25858
Severity: Minor
Alarm description: The temperature in the equipment room
exceeds the high threshold.
Reason
The temperature in the equipment room exceeds the pre-set

high threshold.
Processing
Method
1. Check the high threshold for equipment room temperature

on background to see whether it is rational.
Y-> Goto Step 2.
N-> Modify the high threshold and synchronize it to the
N-> Goto step 2.
2. Cool the equipment room, and check whether the alarm
disappears.
Y-> End.
Verification

room is within the normal range.
Precautions
None.
House temperature is lower than low

threshold
Alarm
Information
Alarm code: 25859
Severity: Minor
Alarm description: The temperature in the equipment room is

lower than the low threshold.
Reason
The temperature in the equipment room is lower than the preset low threshold.
Processing
Method
1. Check the low threshold of equipment room temperature on

background to see whether it is rational.
Y-> Goto Step 2.
N-> Modify the threshold and synchronize it to the
N-> Goto step 2.
2. Warm up the equipment room, and check whether the alarm
disappears.
Y-> End.
Verification

room is within the normal range.
21
Precautions
None.
Voltage is higher than high threshold

Alarm
Information
Alarm code: 25860
Severity: Minor
Reason
Processing
Method
Alarm description: Any line of voltage exceeds the high

threshold.
One line of voltage exceeds the pre-set high threshold.

1. Check the high voltage threshold on background to see
whether it is rational.
Y-> Goto Step 2.
N-> Modify the threshold and synchronize it to the
foreground, and then check whether the alarm disappears.
Y-> End. N-> Goto step 2.
2. Lower the voltage, and check whether the alarm disappears.
Y-> End.
Verification
The alarm disappears.
Precautions
None.
Voltage is lower than low threshold

Alarm
Information
Alarm code: 25861
Severity: Minor
Alarm description: Any line of voltage is lower than the low

threshold.
Reason
One line of voltage is lower than the pre-set low voltage

threshold.
Processing
Method
1. Check the low voltage threshold on background to see

Y-> Goto Step 2.
N-> Modify the threshold and upload it to the foreground,
and then check whether the alarm disappears. Y-> End. N->
Goto step 2.
2. Increase the
disappears.
22
voltage,
and
check
whether
the
alarm
Y-> End.
Verification
Precautions
None.
Humidity is higher than high

threshold
Alarm
Information
Alarm code: 25862
Severity: Minor
Alarm description: The humidity exceeds the high threshold.
Reason
The humidity in the equipment room exceeds the pre-set high

threshold.
Processing
Method
1. Check the high humidity threshold on background to see

Y-> Goto Step 2.
Goto step 2.
2. Lower the humidity, and check whether the alarm disappears.
Y-> End.
Verification
Precautions
None.
Humidity is lower than low threshold

Alarm
Information
Alarm code: 25863
Severity: Minor
Alarm description: The humidity is lower than the low

threshold.
Reason
The humidity in the equipment room is lower than the pre-set

low humidity threshold.
Processing
Method
1. Check the low humidity threshold on background to see

Y-> Goto Step 2.
23

Goto step 2.
2. Increase the
disappears.
humidity,
and
check
whether
the
alarm
Y-> End.
Verification
Precautions
None.
Fault in Fan Plug-in Box

Alarm
Information
Reason
Processing
Method
Alarm code: 25864
Severity: Minor
Alarm description: There are faults in the fan shelf.
The fan is faulty.

1. Check whether the fan plug-in box and its power line are
connected securely (indicators are normal).
Y-> Goto Step 2.
N-> Secure the fan plug-in box and connect the power line,
and then check whether this alarm disappears. Y-> End. N->
Goto step 2.
2. Replace the fan plug-in box with a good one and check
whether the alarm disappears.
Y-> End.
Verification
The alarm disappears, and the fan work normally.
Precautions
None.
Rack Door Access Control Alarm

Alarm
Information
Reason
Processing
Method
24
Alarm code: 25865
Severity: Minor
Alarm description: access control alarm.
The access control of the corresponding rack is not closed.

1. Check whether the rack door is closed.
Y-> Goto Step 2.

N-> Close the rack door, and check whether this alarm
disappears. Y-> End. N-> goto Step 2.
2. Check whether the rack door access control system is
correctly connected.
Y-> Contact ZTE Corporation.
N-> Connect the access control system and close the rack
door, and check whether this alarm disappears. Y-> End. N> Contact ZTE Corporation.
Verification
Precautions
None.
Smoke Alarm
Alarm
Information
Reason
Processing
Method
Alarm code: 25866
Severity: Minor
Alarm description: smoke alarm.
The smoke detector detects smoke.

Check whether there is smoke in the equipment room.
Y-> Dispel the smoke, and check whether this alarm disappears.
Y-> End. N-> Contact ZTE Corporation.
Verification
Precautions
None.
Infrared Alarm
Alarm
Information
Reason
Processing
Method
Alarm code: 25867
Severity: Minor
Alarm description: infrared alarm.
The infrared is too strong.

1. Check whether there is any animal or human near the
infrared detector.
Y-> Make the animal or human away from the detector.
N-> Goto Step 2.
2. Check whether the setting of the infrared detector is correct.
25
Y or do not know how to check -> Contact ZTE Corporation.

N-> Set the infrared detector, and check whether this alarm
disappears. Y-> End. N-> Contact ZTE Corporation.
Verification
Precautions
None.
Lightning Alarm
Alarm
Information
Reason
Processing
Method
Alarm code: 25868
Severity: Minor
Alarm description: Lightning alarm.
The equipment room is influenced by thunder stroke in bad

weather.
Check whether there is lightning hazard.
Y-> Take protection measures, and check whether this alarm
disappears. Y-> End. N-> Contact ZTE Corporation.
Verification
Precautions
None.
Communication Alarm
This section introduces the communication Alarm description.
Ethernet Controllers Physical Link

off
Alarm
Information
Alarm code: 256
Severity: Major
Reason
Alarm description: The physical link of Ethernet controller is

broken. This alarm may cause breaking of the one Ethernetrelated link.
1. No network cable is connected to the network interface omc1

or omc2 on the rear board.
2. The network cable connection fails or looses.
3. Network interfaces on the board are broken.
26
Processing
Method
The network interfaces OMC1 and OMC2 on CIB board need to

be checked and only network interfaces OMC2 on other OMP
boards need to be checked.
1. Check whether both OMC1 and OMC2 connect with network
cables and if the connection looses.
Y-> Goto Step 2
N-> Goto Step 3
2. Connect the network cables to OMC1 or OMC2 on both ends
once again and check whether the alarm disappears.
Y-> End.
N-> Goto Step 3
3. Replace the network cables for OMC1 or OMC2, and check
Y-> End.
N-> Goto Step 4
4. Try to use both crossover and straight network cables to
connect OMC1 or OMC2, and check whether the alarm
disappears.
Y-> End.
Verification
The alarm disappears, and the link connection is normal.
Precautions
None.
Trunk Frame Loss

Alarm
Information
Reason
Alarm code: 512
Severity: Warning
Alarm description: The trunk frame is lost.
1. Two ends have no common ground.

2. The clocks are not synchronous.
3. Transmission equipment is faulty.
Processing
method
1. Check whether the equipment cable impedance matches, if

the boards DIP switch matches the cable, and if the rear
boards jumper cap matches the cable.
Y-> Goto Step 2
N-> Re-set the boards DIP switch or rear boards jumper
cap, and check whether the alarm disappears. Y-> End. N->
Goto Step 2.
27
2. Use the multimeter to detect if the grounding signal of the

both ends of the equipment is reliable.
Y-> Goto Step 3
N-> Check whether the alarm disappears. Y-> End. N->
Goto Step 3.
3. Check whether the CLKG board locks the clock (the TRACE
indicator is always on).
Y-> Goto Step 4
N-> Lock the clock.
4. Check whether the clock references of two interconnected
NEs or nodes are consistent.
Y-> Goto Step 5.
N-> Modify the clock references to ensure that the clock
references of two interconnected NEs or nodes are consistent.
5. Ask the transmission equipment maintenance personnel to
assist in checking if the transmission equipment is
exceptional. If there is any exception, locate the fault
through step-by-step physical diagnosis and circulating test.
Please Contact ZTE Corporation if the problem still can not be
solved.
Verification
Precautions
None
Trunk Signal Loss

Alarm
Information
Reason
Alarm code: 513
Severity: Warning
Alarm description: The trunk signal is lost.
1. The E1 line is not connected or wrongly connected on the

DDF.
2. The E1 is broken.
3. The upstream equipment is exceptional.
Processing
method
1. Check whether E1 on DDF is connected and then check

Y-> End.
N-> Goto Step 2.
2. Self loop E1 on the local end and then check whether the
alarm disappears.
Y-> Detect the upstream equipment, referring to suggestions
on upstream equipment troubleshooting.
28
N-> Goto Step 3.

3. Replace the board and end the alarm handling procedure.
Verification
The alarm disappears and the system works normally.
Precautions
None
Trunk Alarm Indication

Alarm
Information
Reason
Processing
method
Alarm code: 514
Severity: Warning
Alarm description: Trunk alarm indication signal.
The upstream equipment is faulty.

Check and remove alarms related to the E1 of the upstream
equipment. If the alarm can not be eliminated, please Contact
ZTE Corporation.
Verification
The alarm disappears, and the system works normally.
Precautions
None
Trunk Multi-frame Loss

Alarm
Information
Reason
Processing
method
Alarm code: 515
Severity: Warning
Alarm description: The trunk multiframe is lost.
The frame format is inconsistent.

Check whether the frame formats for the two interconnected
ends are consistent. If they are not consistent, configure the
same one for the two ends. If the alarm can not be eliminated,
Contact ZTE Corporation.
Verification
Precautions
None
Far-End CRC Multi-frame Alarm

Indication
Alarm
Information
Alarm code: 516
29
Reason
Processing
method
Severity: Warning
Alarm description: The alarm indication occurs when the
trunk receives remote CRC multiframes.
Inconsistent multiframe format

1. Check whether the frame formats for the interconnected two
ends are consistent. If they are not consistent, configure the
same one for the two ends.
2. If the alarm can not be eliminated, contact ZTE Corporation.
Verification
Precautions
None
Far-End Alarm
Alarm
Information
Alarm code: 517
Severity: Warning
Alarm description: The alarm occurs in the remote receiving

end.
Reason
A problem occurs when the local end sends signal, or the middle
transmission equipment is faulty. All kinds of faults that may
result in LOS, AIS, and LOF on the peer end would probably
cause this alarm.
Processing
method
Check the communication between the board and the control

plane of its home module.
1. At this time, at least one alarm among LOS, AIS, and LOF
occurs on the peer end. Check and record the alarm on the
peer end. Check the intermediate transmission equipment for
this trunk link to see if there is any fault. If there is,
eliminate the fault.
2. Please Contact ZTE Corporation if the problem can not be
solved.
Verification
Precautions
None
The Link between the OMC and the

Alarm Box is Broken
Alarm
Information
30
Alarm code: 1000
System type: AlarmBox Link Break Alarm
Severity: Critical
Alarm description: The communication link between the
alarm box and the OMC server is interrupted.
Reason
The connection line or the link between the alarm box and the
OMC server is faulty.
Processing
method
Check whether the connection between the alarm box and the
OMC server is faulty.
Verification
Precautions
None
Cell Delineation not Synchronized

Alarm
Information
Alarm code: 1024
Severity: Warning
Alarm description:
synchronized.
The
cell
delineation
cannot
be
Reason
Header Error Control (HEC) is damaged. The cell can not be

located from the frame at the physical layer. Usually it is
triggered by bottom-layer faults or it is because the local-end
equipment and the peer-end equipment process HEC in different
ways.
Processing
method
1. Check whether there is any other physical-layer alarm. If

there is, eliminate it first. Check whether the alarm
disappears.
Y-> End.
N-> Goto Step 2
2. Check whether both ends are configured to SDH mode or
SONET mode. If the modes are different, configure a correct
signal mode for them. Check whether the alarm disappears.
Y-> End.
Verification
Precautions
None
Loss of Cell Delineation

Alarm
Information
Alarm code: 1025
Severity: Warning
31
Reason
Processing
method
Alarm description: The cell delineation is lost.
LCD is triggered after OCD lasts for 4ms.

1. Check whether there is any other physical-layer alarm. If
there is, eliminate it first. Check whether the alarm
disappears.
Y-> End.
N-> Goto Step 2.
2. Check whether both ends are configured to SDH mode or
SONET mode. If the modes are different, configure a correct
signal mode for them. Check whether the alarm disappears.
Y-> End.
N-> Goto Step 2.
Verification
Precautions
None
The Link between the OMC and the

NE is Broken
Alarm
Information
Alarm code: 1000
System type: Link Alarm
Severity: Warning
Reason
Processing
method
Alarm description: The link between the NE and the OMC

server is interrupted.
The link between the NE and the OMC server is interrupted.

Check whether the connection between the foreground and the
background is normal.
Verification
Precautions
None
Communication Link between Active

and Standby Boards Off
Alarm
Information
Alarm code: 5122
Severity: Minor
Alarm description:
communication link.
Interruption
Reason
32
of
the
active/standby
1. The board is configured to active/standby mode, but the

standby board is not inserted.
2. The standby board exists, but the communication link
between the active board and the standby board is broken.
Processing
method
1. Check whether the board is configured to active/standby

mode. If it is, check whether the standby board is in the
position.
Y-> Goto Step 2.
N-> Insert the standby board, and then power on it. Then
the alarm disappears.
2. If the standby board runs abnormally, replace it. Then check
whether the alarm disappears after it is powered on.
Y-> End.
N-> Goto Step 3.
3. Check the communication on the control plane, and
troubleshoot the fault according to the alarm (related to
control-plane
communication
interruption)
handling
suggestions. After troubleshooting the control-plane fault,
contact ZTE Corporation Corporation if the alarm is still not
eliminated.
Verification
Precautions
None
Board HW Error
Alarm
Information
Reason
Alarm code: 5378
Severity: Major
Alarm description: Board HW loop test failure.
1. The HW eletrionic switch is not opened.

2. The NE clock is exceptional.
3. The TDM connection chip is exceptional.
4. The board hardware is faulty.
5. The back board hardware is faulty.
Processing
method
1. Check the number of HWs configured for this board and

neighboring slots to see if the number exceeds the allowed
number.
Y-> Goto Step 2
N-> Modify the configuration and synchronize data. Then
restart the board to see if the alarm disappears: Y-> end, N> goto Step 2.
33
2. Check whether there is any vacant slot.

Y-> Replace the configured slots with the vacant slot, and
check whether the alarm disappears: Y-> end, N-> Contact
ZTE Corporation.
Verification
Precautions
None
Board Does not Exist/CPU Is Long in

Reset Status
Alarm
Information
Alarm code: 5379
Severity: Major
Reason
The board configured in the database is not in position.
A fault occurs during the board reset.
Processing
method
Alarm description: The board is not in the position, or the

CPU is in the reset status for a long time.
The Healthy hardware pin of this slot on the backboard is

destroyed.
1. Check whether this board is in position.

Y-> Goto Step 2.
N-> Insert the board and then check whether the alarm
disappears: Y-> end, N-> goto Step 2.
2. Pull out the board and then plug it again in position. Then
check whether the alarm disappears.
Y-> End.
N-> Goto Step 3.
3. Replace the
disappears.
slot
and
then
check
whether
the
alarm
Y-> End.
Verification
Precautions
None
PWRD 485 Communicate Link Break

Alarm
Information
34
Alarm code: 5382
Severity: Major
Reason
Alarm
description:
interruption.
PWRD
485
communication
link
1. The 485 communication link between the PWRD and the OMP
is interrupted.
2. There is no connection between the PWRD and the OMP, or
the connection line between the PWRD and the OMP is faulty.
3. The number configured for the rack where the PWRD is
located in inconsistent with that set by PWRD DIP switches.
Processing
method
1. Check whether the connection between the PWRD and the

OMP is correct.
Y-> Goto Step 2
N-> Correctly connect the OMP and the PWRD and then
check whether the alarm disappears: Y-> end, N-> goto
Step 2.
2. Check whether the configured rack number is consistent with
that set by the PWRD DIP switches.
N-> Adjust the value set by the PWRD DIP switches, and
then check whether the alarm disappears: Y-> end, N->
Verification
Precautions
None
External Port of Board Is Down

Alarm
Information
Reason
Alarm code: 5395
Severity: Major
Alarm description: The external port of the board is down.
1. The network interface at the local end or the peer end is

faulty.
2. The work modes of network interfaces at both ends do not
match.
3. Faults occur in the physical connection.
Processing
method
1. Check whether the connection between the port on this

board and the peer-end one is correct.
Y-> Goto Step 2.
35
N-> Correctly connect the port on this board with the peerend one, and then check whether the alarm disappears: Y->
end, N-> Goto Step 2.
2. Configure the work mode of the port on the local end to
make it consistent with that of the port on the peer end.
Then check whether the alarm disappears.
Y-> End.
N-> Goto Step 3.
3. Replace the board or the used network interface on the local
end and then check whether the alarm disappears.
Y-> End.
N-> Goto Step 4.
4. Replace the used network interface on the peer end and then
Y-> End.
Verification
Precautions
None
DSP Port Link Down

Alarm
Information
Reason
Processing
method
Alarm code: 5641
Severity: Critical
Alarm description: The port link is broken.
There is something wrong with the lan91 chip or bcm5328 chip.

1. Reset the corresponding DSP chip or the board by using MML
commands on the background. Check the alarm disappears.
Y-> End.
N-> Goto Step 2.
2. Replace the board and then check whether the alarm
disappears.
Y-> End.
36
Verification
Precautions
None
Receive Bad Packet

Alarm
Information
Alarm code: 15616
Severity: Minor
Reason
Processing
method
Alarm description: The number of frames discarded at the

external port exceeds the threshold.
The status of the network connected with the external port is
exceptional.
The hardware of the board is faulty.
The 2400 sub-card originally working normally is loosed due
to vibration.
Check whether the board and the link are normal or whether
there is any exceptional attack message.
Verification
Precautions
None
PVC FAULTS
Alarm
Information
Reason
Alarm code: 18944
Severity: Minor
Alarm description: Faults in PVC.
Processing
method
When the PVC CC function is started, the PVC changes from

the working status to non-working status.
The CC function is started at the local end but not at the peer
end.
The signal on the physical link deteriorates. For example, the
optical signal on the optical interface deteriorates.
The local continuity check times out.
The OAM fault cell is received, such as AIS and RDI cells.
1. Check whether the physical link is normal. Confirm that the

fiber and optical module are in good status, and the port
indicator indicates normal link connection.
2. Check whether the local end starts the CC function, and acts
as the receiving end.
Y-> If the local end fails to receive the CC cells from the
sending end, or user cells, it means that the link continuity is
lost. Start the CC function through the background, and
check whether the link is normal.
37
3. Check whether other part of this PVC is faulty. If other NEs

on this PVC link indicate that this PVC link is faulty, the AIS
or RDI cell that the local NE receives also indicates that this
PVC link is faulty. Refer to Steps 1 and 2 to check the reason
why other NEs indicate that this PVC is faulty.
Verification
Precautions
None
Timing of Near-End IMA Group

Failure
Alarm
Information
Alarm code: 19208
Severity: Major
Alarm description: Mismatch between the clock mode sent by

the remote IMA group and that sent by the local IMA group.
Reason
The remote-end IMA group clock mode sent by the remote end
through ICP cells does not match with the near-end one. For
example, ICT (Independent Clock Template) on the remote end
does not match with CTC (Common Transmit Clock) on the near
end.
Processing
method
Check whether the clock-mode-related configuration on the near

end matches that on the remote end.
N-> Modify the configuration to be consistent. If the alarm
disappears, end the alarm handling. If not, Contact ZTE
Corporation.
Verification
Precautions
None
NE Group Is in Insufficient Links

State
Alarm
Information
Alarm code: 19209
Severity: Major
Reason
38
Alarm description: The links in the local IMA group are

insufficient.
The number of links in the ACTIVE status at the local end does
not reach the minimum number of sending/receiving links set by
the user.
Processing
method
The alarm will automatically disappear when the number of

links in the ACTIVE status in the corresponding group
exceeds or equals the minimum number of sending/receiving
links configured in the group.
Check whether the number of links configured in the group is
less than the minimum number of sending/receiving links. If
yes, configure more links in the group.
Verification
Precautions
None
FE RXLSM Is in Unusable State

Alarm
Information
Alarm code: 19210
Severity: Major
Reason
Processing
method
Alarm description: The remote receiving link connected with

the local end is unusable.
A receiving link at the remote end is faulty, so it is changed
to the Unusable status from the ACITIVE status.
The link enters into the Unusable status after the link is
just enabled.
The alarm will automatically disappear in case that the link
enters into the Unusable status after the link is just
enabled.
For the alarm caused by the fault in the remote receiving link,
check whether the IMA link configuration such as scrambling
code and direction at the remote end matches with that at
the local end.
Check whether the RUN indicator on the clock board is green
and flash slowly, and use the debugging function ppdbgpslot
(BYTE ucSlot) to check the UIM/DTB connection relationship,
and check whether the E1 cable is loosed.
Verification
Precautions
None
Implementation Specific TX Fault

Declared at the NE
Alarm
Information
Alarm code: 19211
Severity: Major
39
Alarm description: Fault in the local sending link, which is

generally caused by the equipment.
Reason
In general, the IMA equipment fault causes the fault in the local
sending link.
Processing
method
Check whether the IMA chip works normally and the E1 cable
connection.
Verification
Precautions
None
Near-End Sending Link Broken

Alarm
Information
Alarm code: 19212
Severity: Major
Alarm description: The local sending link is broken.
Reason
The alarm occurs when a sending link in the group is not

connected to the remote IMA group as others are.
Processing
method
Check whether the IMA chip works normally and each link can
connect to the remote IMA group normally.
N-> Configure them again. If the alarm disappears, end the
alarm handling. If not, Contact ZTE Corporation.
Verification
Precautions
None
LIF Alarm of Near-End Receiving

Link
Alarm
Information
Alarm code: 19213
Severity: Major
Reason
Processing
method
Alarm description: The local receiving link loses the IMA

frame.
There are physical faults in the E1 link.

In general, the fault in the E1 physical connection causes the
loss of the IMA frame. Check whether the E1 link is normally
connected with the corresponding remote link to avoid errors in
the connection sequence of the E1 link.
40
N-> Connect them again. If the alarm disappears, end the alarm
handling. If not, Contact ZTE Corporation.
Verification
Precautions
None
LODS Alarm of Near-End Receiving

Link
Alarm
Information
Alarm code: 19214
Severity: Major
Reason
Processing
method
Alarm description: The delay synchronization signal of the

local receiving link is lost.
The access clock is abnormal.

Check whether the access clock of the IMAB works normally and
whether the RUN indicator on the clock board of the
corresponding NE is green and flashes slowly.
N-> Set the access clock again according to handling
suggestions for clock alarms. If the alarm disappears, end the
Verification
Precautions
None
RDI Alarm of Near-End Receiving

Link
Alarm
Information
Alarm code: 19215
Severity: Major
Reason
Processing
method
Alarm description: The alarm will occur when the local

receiving link receives the remote failure indication.
The remote IMA link is not in activated status.

Check whether the remote receiving link is active by using the
DDM dynamic management tool of the background.
N-> Set the link to the activated status. If the alarm disappears,
end the alarm handling. If not, Contact ZTE Corporation.
Verification
41
Precautions
None
Near-End Receiving Link Faults

Alarm
Information
Alarm code: 19216
Severity: Major
Alarm description: The local receiving link is faulty.
Reason
If a local receiving link is faulty, this alarm appears on the local

end.
Processing
method
Check whether the IMA chip works normally, and whether each
link can be normally connected to the local IMA group.
N-> Handle this problem. If the alarm disappears, end the alarm
Verification
Precautions
None
Implementation Specific Rx Failed

Declared at the NE
Alarm
Information
Reason
Processing
method
Alarm code: 19217
Severity: Major
Alarm description: The local receiving link is disabled.
The local receiving link is disabled.

It can automatically recover to normal status.
Verification
Precautions
None
Near-End Receiving Link Broken

Alarm
Information
42
Alarm code: 19218
Severity: Major
Alarm description: The local receiving link is broken.
Reason
A receiving link in the group is not connected to the remote IMA

group as others are.
Processing
method
Check the connection condition of each receiving link at both the

local end and the remote end to make sure that each receiving
link is normally connected to the local IMA group. Check whether
the specified local E1 link is connected with the corresponding
remote E1 link.
N-> Find the fault causes, and handle the problem. If the alarm
disappears, end the alarm handling. If not, Contact ZTE
Corporation.
Verification
Precautions
None
Far end TXLSM Is in Unusable State

Alarm
Information
Alarm code: 19219
Severity: Major
Reason
Processing
method
Alarm description: The remote sending link connected with

the local end is unusable.
A sending link at the remote end is faulty, so it is changed to
the Unusable status from the ACITIVE status.
The link enters into the Unusable status after the link is
just enabled.
The alarm will automatically disappear in case that the link
enters into the Unusable status after the link is just
enabled.
For the alarm caused by the fault in the remote sending link,
check whether the IMA link configuration such as scrambling
code and direction at the remote end matches with that at
the local end.
Check whether the E1 cable is loosed.
Verification
Precautions
None
All High-Speed Serial Links Out of

Synchronism
Alarm
Information
Alarm code: 19456
43
Reason
Severity: Critical
Alarm description: All the high-speed serial links are out of
synchronization.
1. All the high-speed serial links connected to the PSN are out
of synchronism. Chip 827 may be faulty.
2. Chip 882 on the PSN board may be faulty.
3. The PSN board is faulty.
Processing
method
1. Check whether PSN boards are configured to load sharing

work mode.
Y-> Goto Step 2.
N-> Configure the load sharing work mode for PSN boards.
Restart PSN boards and the board giving this alarm.
2. Check whether PSN boards are in running status.
Y-> Goto Step 3.
N-> Check which board is not powered on successfully
through processes. Contact ZTE Corporation to enable the
board to be powered on successfully.
3. If PSN boards work normally, restart the faulty board and
Y-> End.
N-> Goto Step 4.
4. Replace the board giving this alarm and check whether the
alarm disappears.
Y-> End.
Y-Contact ZTE Corporation.
Verification
Precautions
None
Control Plane Communication

Abnormal Between Board and Its
Home Module
Alarm
Information
Alarm code: 8393985
Severity: Major
Reason
44
Alarm description: The OSS-layer communication between

the serving board and the homing module is interrupted.
1. The board is configured in the database, but it is not

normally powered on.
2. The board is powered on, but the control panel link between
the board and its homed MP is broken.
3. After the board is powered on, the ENUM switch is opened.
Processing
method
1. Check whether the ENUM indicator on the board where the

alarm occurs is always on.
Y-> Switch on the ENUM switch of the board, and check
whether this alarm disappears. Y-> End, N-> Goto Step 2.
N-> Goto Step 2.
2. Check whether the UIM board in the same shelf with this
board, the UIM board in the shelf where the home module of
this board is located and the CHUB board (if there is any)
work normally.
Y-> Goto Step 3.
N-> Restore the boards above to normal status, and check
3. Check whether this board is successfully powered on (the
RUN indicator flashes at 1HZ).
N-> Power on the board and check whether this alarm
disappears. Y-> End, N-> Contact ZTE Corporation.
Verification
Precautions
None
MPOMP_COMM_OFF between mp
and omp
Alarm
Information
Alarm code: 8393988
Severity: Major
Reason
Alarm description: The communication between the module

and the OMP is interrupted. The status of the unit belonging
to the MP is unknown.
1. The MP board is configured in the database but not powered

on.
2. The MP board is powered on but the control plane link to the
OMP is broken.
3. The MP board is powered on and the ENUM switch is
switched on.
Processing
method
1. Check whether the ENUM indicator is always on.

Y-> Switch on the ENUM switch and check whether this
alarm disappears. Y-> End, N-> Goto Step 2.
45
N-> Goto Step 2.

2. Check whether the UIM board in the same shelf with this
board, the UIM board in the shelf where the OMP is located
and the CHUB (if there is any) work normally.
Y-> Goto Step 3.
N-> Restore the boards above to normal status, and check
3. Check whether this board is successfully powered on (the
RUN indicator flashes at 1HZ).
N-> Power on the board and check whether this alarm
disappears. Y-> End, N-> Contact ZTE Corporation.
Verification
Precautions
None
MTP3 Office Inaccessible

Alarm
Information
Alarm code: 8400128
Severity: Major
Reason
Alarm description: The MTP3 office direction is inaccessible.

The system failed to receive/send any message to the
corresponding office direction.
1. There are errors

configuration.
in
the
office
direction
and
route
2. The link is broken.

Processing
method
1. Check whether the static route settings of the destination

office are correct.
Y-> Goto 2.
N-> Configure or modify related static routes.
f
Check whether the office is accessible (this alarm

disappears).
Y-> End.
N-> Goto 2.
2. Query link status in the route table through the dynamic

management tool on the background to check whether there
are links available.
Y-> Goto Step 4.
N-> Goto Step 3.
3. Check alarms on the background to see whether there are
alarms prompting no link available.
46
Y-> Perform further handling according to the alarms

prompting no link available.
N-> Goto Step 4.
4. Note down detailed information.
i.
Back up the related local office configuration data and

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

alarms and notifications, as well as current alarms.
iii. Contact ZTE Corporation.
Verification
Precautions
None
MTP3 Link Unavailable

Alarm
Information
Alarm code: 8400129
Severity: Minor
Reason
Alarm description: The MTP3 link is unavailable, which may

cause the office direction inaccessible and congestion in
other available links.
1. The link is physically broken.

2. The link test fails.
3. The SMP board or the SPB/APBE board is restarted.
Processing
method
1. Check whether there is new data configuration or the

configuration is changed.
Y->
i.
Check link configuration data, especially signaling point

code (SPC), SLC and network type (international or
domestic) to see whether they accord with those at the
peer end of the link.
Y-> Goto 2.
N-> Modify the configuration and goto step ii.
iii. Check whether this alarm disappears after modifying the

configuration.
Y-> End
N-> Goto 2.
N-> Goto 2.
2. Check whether there is any alarm for the bottom-layer
transmission if the link configuration is changed.
Y-> Ask a transmission engineer to handle the problem.
47
N-> Goto Step 3.

3. Perform a self loop for the physical link on the DDF, and
check whether this alarm disappears.
Y-> Check the bottom-layer transmission
transmission engineer to solve the problem.
and
ask
N-> Goto Step 4.

i.


Verification
Precautions
None
MTP3 Cluster Inaccessible

Alarm
Information
Reason
Alarm code: 8400130
Severity: Major
Alarm description: Cluster unreachable.
1. There are errors in the cluster and route configuration.

2. The link is obstructed.
Processing
method
1. Check whether the static route configuration of the cluster is

correct.
Y-> Goto Step 2.
N-> Configure or modify the related static routes.
f
Check whether the cluster is accessible.

Y-> End.
N-> Goto 2.
2. Query link status in the route table through the dynamic

management tool on the background to check whether there
are links available.
Y-> Goto Step 4.
N-> Goto Step 3.
3. Check alarms on the background to see whether there are
alarms prompting no link available.
Y-> Perform further handling according to the alarms
prompting no link available.
48
N-> Goto Step 4.

i.

ii. Back up the related local office and peer-end office

history alarms and notifications, as well as current alarms.
Verification
Precautions
None
MTP3 Link Congestion

Alarm
Information
Reason
Alarm code: 8400131
Severity: Major
Alarm description: MTP3 link congestion.
1. The traffic is heavy.

2. The loads on links are uneven.
3. The link resource is insufficient.
Processing
method
1. Make no manual intervention and just wait for the system to

recover to the normal status. Check whether this alarm
disappears 30 seconds later.
Y-> End.
N-> Goto Step 2.
2. Check whether the system has a heavy traffic.
Y-> Goto Step 3.
N-> Goto Step 4.
3. Check whether the link resource is sufficient.
Y-> Query performance statistics data to check whether the
load is evenly shared among links. Y-> Goto Step 1. N->
Goto Step 4.
N-> Add new links and check whether this alarm disappears.
Y-> End. N-> Goto Y option in Step 3.
i.


49
Verification
Precautions
None
M3UA Office Inaccessible

Alarm
Information
Alarm code: 8400384
Severity: Major
Reason
Alarm description: The M3UA office direction is inaccessible.

The system failed to receive/send any message to the
corresponding office direction.
1. The association is released or the AS does not go into service

state, which causes office inaccessible.
2. No SIOLOCAS table data to this office are configured, which
causes AS unable to be bound with the office managed by
M3UA.
3. This alarm does not occur frequently.
Processing
method
1. Check the configuration data to see whether SIO location of

this office is configured.
Y-> Goto Step 2.
N-> Configure SIO location.
f
Check whether this alarm disappears after the SIO

location data are configured.
Y-> End
N-> Goto step 2.
2. Check the data configuration to see whether the AS

corresponding to the SIO location of this office is activated.
Y-> Goto Step 3.
N-> Goto Step i.
i.
Check whether ASPs under this AS are activated.

Y-> Goto Step 4 if there are ASPs activated under this AS
and the number of them exceeds the necessary number.
N-> Goto Step i if there is no ASP activated under this AS
or the number of activated ASPs does not reach the
necessary number.
ii. Check whether the association of ASP is activated.

Y-> Goto Step 3 if the association is activated but the
ASP is not.
N-> Perform further handling according to the alarm for
association unavailable if the association of the ASP is not
activated.
50
3. Deactivate and then activate the associations serving this

office, and check whether this alarm disappears.
Y-> End.
N-> Goto Step 4.
i.


Verification
Precautions
None
SUA SSN Is Invalid

Alarm
Information
Reason
Alarm code: 8401152
Severity: Minor
Alarm description: SUA subsystem is unusable.
1. A signaling point sub-system exits services.

2. The association or AS is not in serving state, which causes a
signaling point inaccessible.
3. SSN location AS is not configured.
Processing
method
1. Check through Alarm Management to see whether there

are corresponding alarms of adjacent office inaccessible.
Y-> Perform further handling according to the alarms of SUA
office inaccessible.
N-> Goto Step 2.
2.
Check the configuration data of the local office to see

whether the corresponding sub-system is configured in local
office configuration and adjacent office configuration as well.
Y-> Goto Step 3.
N-> Configure the sub-system. Check whether this alarm
disappears after configuring the sub-system. Y-> End. N->
Goto Step 3.
3. Check configuration data of the peer-end adjacent office to

see whether the corresponding sub-system is configured in
Local Office Configuration and Adjacent Office Configuration
as well.
Y-> Goto Step 4.
51
N-> Contact the personnel of the peer-end office to configure

the data. Check whether this alarm disappears after the
peer-end office is configured with the sub-system. Y-> End.
N-> Goto Step 4.
i.


Verification
Precautions
None
SUA Office Inaccessible

Alarm
Information
Alarm code: 8401153
Severity: Major
Reason
Alarm description:
unreachable
Alarm
due
to
SUA
office
direction
1. The association or AS is not in service status, which causes a

signaling point inaccessible.
2. No SSN location AS to this office is configured.
Processing
method
1. Check configuration data to see whether SSN location of this

office is configured.
Y-> Goto Step 2.
N-> Configure the SSN location data.
f
Check whether this alarm disappears after configuring the

SSN data.
Y-> End.
N-> Goto Step 2.
2. Check the data configuration to see whether the AS

corresponding to the SSN location of this office is activated.
Y-> Goto Step 3.
N-> Goto Step i.
i.
Check whether ASPs under this AS are activated.

Y-> Goto Step 4 if there are ASPs activated under this AS
and the number of them exceeds the necessary number.
N-> Goto Step ii if there is no ASP activated under this
AS or the number of activated ASPs does not reach the
necessary number.
52
iii. Check whether the association of ASP is activated.

Y-> Goto Step 3 if the association is activated but the
ASP is not.
N-> Perform further handling according to the alarm for
association unavailable if the association of the ASP is not
activated.
3. Deactivate and then activate the associations serving this
office, and check whether this alarm disappears.
Y-> End.
N-> Goto Step 4.
i.


Verification
Precautions
None
M2PA Link Broken

Alarm
Information
Reason
Alarm code: 8402177
Severity: Minor
Alarm description: The M2PA signaling link is broken.
1. The association is broken.

2. Upper-layer services are stopped.
3. The peer end originates a release.
Processing
method
1. Check whether the association for the M2PA link is available

by checking alarms for the related association broken in
Alarm Management.
Y-> Goto 2.
N-> Perform further handling according to the alarm.
2. Check whether the protocols at the two ends of the M2PA
link are consistent.
Y-> Goto Step 3.
N-> Change the protocols and make them consistent, and
goto check whether this alarm disappears after the
protocols are made accordant. Y-> End. N-> Goto Step 3.
53
3. Check whether the associations used at the two end of the

M2PA link are consistent.
Y-> Goto Step 4 if the associations are consistent and
available.
N-> Modify the associations and make them consistent,
check whether this alarm disappears after the association
numbers are changed and made consistent. Y-> End. N->
Goto Step 4.
i.


Verification
Precautions
None
Association Congested
Alarm
Information
Reason
Alarm code: 8402688
Severity: Minor
Alarm description: association congestion.

2. The loads on associations are uneven.
3. The association resource is insufficient.
Processing
method

Y-> End.
N-> Goto Step 2.
Y-> Goto Step 3.
N-> Goto Step 4.
3. Check whether the association resource is sufficient.
Y-> Check whether the load is evenly shared among
associations. Y-> Goto Step 1. N-> Goto Step 4.
N-> Add new associations and check whether this alarm
disappears. Y-> End. N-> Goto Y option in Step 3.
54
i.


Verification
Precautions
None
An IUA Association Broken

Alarm
Information
Reason
Processing
method
Alarm code: 33575462
Severity: Minor
Alarm description: One IUA association is broken.
One IUA association is broken.

Check whether the SCTP at both the local end and the opposite
end works normally and whether the IP connection between the
two ends is normal.
Verification
Precautions
None
Link between Igate and NE has

Broken
Alarm
Information
System type: Monitoring Server Alarm
Severity: Major

lawful interface server and the monitored NE is broken.
Reason
The communication link between the lawful interface server and

the monitored NE is broken.
Processing
method
Check the communication link between the lawful interface

server and the lawful MP on the monitored NE.
Verification
Precautions
None
55
Link between Igate and LIC Has

Broken
Alarm
Information
System type: Monitoring Server Alarm
Severity: Major

lawful interface server and the lawful information center is
broken.
Reason
The communication link between the lawful interface server and

the lawful center is broken.
Processing
method
Check the communication link between the lawful interface

server and the lawful information center.
Verification
Precautions
None
Link to Device Is Broken

Alarm
Information
Alarm code: 1
System type: Polling Link Alarm
Severity: Major
Reason
Processing
method
Alarm description: The

equipment is broken.
communication
The
network
management
system
communication with the NE is interrupted.
link
detects
with
the
that
the
On the network management server, check whether the

communication link with the OMP of the NE is normal by using
the ping command.
Verification
Precautions
None
The link Between the Native OMC

and the Superior Is Broken
Alarm
Information
56
Alarm code: 1000
System type: Local and Remote OMC Linkdown Alarm
Severity: Critical
Reason
Processing
method
Alarm description: The link between the local OMC and the
superior OMC is broken.
The communication is abnormal.

Check whether the link between the local OMC and the superior
OMC is normal.
Verification
Precautions
None
BFD Session Interrupted

Alarm
Information
Alarm code: 22784
Severity: Critical
Alarm description: The BFD session is down.
Reason
Links in the UDP layer where the BFD session runs are faulty,
causing the BFD session in down status.
Processing
method
1. Check whether the physical link between source IP address

and destination IP address of the session is normal.
Y-> Goto Step 3.
N-> Goto Step 2.
2. If the link is broken or the network cable is not connected
well, repair the link or replace the cable.
After 30 seconds, check whether the alarm disappears.
Y-> End.
N-> Goto Step 3.
3. Check whether the intermediate equipment works normally.
Y-> Goto Step 4.
N-> Contact providers of these equipment, and then goto
Step 4.
Verification
Precautions
None
Association Link Broken

Alarm
Information
Alarm code: 8402690
Severity: Major
57
Reason
Alarm description: The association is broken.
1. The association is deleted.

2. The association is manually release.
3. Other causes (See
association broken.
the
alarm
information)
cause
the
4. This alarm does not occur frequently.

Processing
method
1. Check whether the association is newly configured or

changed.
Y-> The association is newly configured or changed.
i.
Check the configuration data of this association to see if

the data are consistent with that of the peer end,
especially port numbers and IP addresses of the local end
and the peer end. Check whether the association client
accords with the association server.
Y-> Goto Step 2 if the configuration of the two ends are
accordant.
N-> Goto Step ii if the configuration data are not
accordant.
iii. Check whether this alarm disappears after modifying the

configuration.
Y-> End.
N-> Goto 2.
2. Check whether there is any alarm for bottom-layer
transmission if the association configuration is not changed.
Y-> Forward the problem to a transmission engineer for
further handling.
N-> Goto Step 3.
3. Deactivate and activate again the association and check
Y-> End
N-> Goto Step 4.
i.


58
Verification
Precautions
None
Association Path Broken down

Alarm
Information
Alarm code: 8402691
Severity: Minor
Reason
Processing
method
Verification
Precautions
Alarm description: One channel in the SSM association is

broken.
One channel (corresponding to one peer-end IP address) in the

SSM association is broken.
Check the association.

None
STC Office Inaccessible

Alarm
Information
Reason
Processing
method
Alarm code: 8402944
Severity: Major
Alarm description: The STC office is inaccessible.
All the associations are out of service.

1. Check whether all the associations to the adjacent office are
unavailable.
Y-> Perform further handling according to the alarm of
association broken.
N-> If all the associations to the adjacent office are available,
goto Step 2.
i.


Verification
Precautions
This alarm will cause subscribers unable to receive or send

messages to the corresponding office.
59
Test Pack Check Abnormal

Alarm
information
Reason
Processing
method
Alarm code: 5401
Severity: Major
Alarm description: The test message check is abnormal.
The Atm communication within a board is abnormal.

1. Restart the board, and check whether the alarm disappears.
Y-> End.
No-> Goto Step 2.
2. Replace the board, and check whether the alarm disappears.
Y-> End.
No-> Contact ZTE Corporation.
Verification
Precautions
None
QoS Alarm
This section introduces the Quality of Service (QoS) Alarm
description.
Dual Homing Office Blocked

Alarm
Information
Reason
Processing
method
Alarm code: 14592
Severity: Minor
Alarm description: The dual-homing office is blocked.
The dual-homing office is switched to the standby domain, and

the service DH process initiates the procedure of blocking the
office.
1. Check whether the dual-homing office is in standby domain.
Y-> It is not necessary to handle this alarm. End the alarm
handling.
N-> Goto Step 2.
2. Perform dynamic management operations on the dual
homing office and unblock the blocked office. Check whether
Y-> End.
60
N-> Goto Step 3.

3. Record detailed information
i.


Verification
Precautions
None
Dual Homing Link Blocked

Alarm
Information
Alarm code: 14593
Severity: Minor
Alarm description: The dual-homing link is blocked.
Reason

the service DH process initiates the procedure of blocking all the
links in the office.
Processing
method
1. Check whether the dual-homing office is in the standby

domain.
handling.
N-> Goto Step 2.
2. Perform dynamic management operations on the related
links and unblock the blocked links. Check whether the alarm
disappears.
Y-> End.
N-> Goto Step 3.
i.


Verification
Precautions
None
61
Dual Homing Association Blocked

Alarm
Information
Alarm code: 14594
Severity: Minor
Alarm description: The dual-homing association is blocked.
Reason

the service DH process initiates the procedure of blocking all the
associations in the office.
Processing
method
1. Check whether the dual-homing office is in the standby

domain.
handling.
N-> Goto Step 2.
2. Perform dynamic management operations on the related
associations and unblock the blocked associations. Check
Y-> End.
N-> Goto Step 3.
i.


Verification
Precautions
None
Resource Board Unable to Get

Secondary Forwarding Table from
UIM
Alarm
Information
Alarm code: 19970
Severity: Major
Reason
62
Alarm description: The resource board can not get the

information of the level-2 forwarding table from the UIM
board.
1. This shelf is not a BUSN shelf.
2. The UIM board on this shelf is not powered on normally.

3. Control plane messages are blocked.
Processing
method
1. Check whether the resource shelf is a BUSN shelf and the

UIM board on the shelf is powered on normally.
Y-> If the alarm still exists, goto Step 4. Otherwise, goto
Step 3.
N-> Goto Step 2.
2. Replace the resource shelf with a BUSN shelf and configure
the rack again, making sure that the UIM board is powered
on normally. Check whether the alarm disappears.
Y-> Goto Step 4.
N-> Goto Step 3.
3. Record detailed information and Contact ZTE Corporation.
4. End the alarm handling.
Verification
Precautions
None
Broadband Link Congestion

Alarm
Information
Reason
Alarm code: 8399104
Severity: Minor
Alarm description: Congestion in the broadband link.

Processing
method

Y-> End.
N-> Goto Step 2.
Y-> Goto Step 3.
N-> Goto Step 4.
Goto Step 4.
63
i.


Verification
Precautions
None
Broadband Link Overload

Alarm
Information
Alarm code: 8399105
Severity: Minor
Reason
Alarm description: Alarm due to overload in the broad-band

link.

Processing
method

Y-> End.
N-> Goto Step 2.
Y-> Goto Step 3.
N-> Goto Step 4.
Goto Step 4.
i.


64

Verification
Precautions
None
MTP2 Link Transmission Overload

Alarm
Information
Alarm code: 8399872
Severity: Major
Reason
Alarm description: Alarm due to sent traffic overload on the

MTP2 link.
1. The traffic at the local end is heavy.

Processing
method

Y-> End.
N-> Goto Step 2.
Y-> Goto Step 3.
N-> Goto Step 4.
Goto Step 4.
i.


Verification
Precautions
None
65
MTP2 Link Reception Overload

Alarm
Information
Alarm code: 8399873
Severity: Major
Reason
Alarm description: Alarm due to received traffic overload on

the MTP2 link.
1. The traffic at the peer end is heavy.

Processing
method

Y-> End.
N-> Goto Step 2.
Y-> Goto Step 3.
N-> Goto Step 4.
Goto Step 4.
i.


Verification
Precautions
None
Performance Level 4 Alarm

Alarm
Information
66
System type: CN Performance Manager
Severity: Warning
Reason
Processing
method
Alarm description: Level-4 performance alarm.
The performance index exceeds the defined monitoring threshold.

If the performance index exceeds the defined monitoring
threshold, perform further analysis and processing through data
query function of the performance statistics system.
Verification
Precautions
None

Alarm
Information
Reason
Processing
method
Severity: Minor

Verification
Precautions
None

Alarm
Information
Reason
Processing
method
Severity: Major

Verification
Precautions
None

Alarm
Information
67
Reason
Processing
method
Severity: Critical

Verification
Precautions
None
QOS Alarm from PM

Alarm
Information
Reason
Processing
method
Severity: Unknown
Alarm description: Performance QoS alarm.
The performance QoS exceeds the defined monitoring threshold.

If the performance QoS exceeds the defined monitoring
Verification
Precautions
None
Inter-board Message Communication

Flow Rate over Alarm Threshold
Alarm
Information
Alarm code: 23296
Severity: Minor
Reason
Processing
method
Alarm description: The inter-board message communication

traffic exceeds the alarm threshold.
Calculate the communication traffic within a cycle, and judge

whether the communication traffic in outgoing and incoming
directions of the control plane exceeds the alarm threshold (By
default, the alarm threshold is the maximum, and the
restoration thereshold is 19/20 of the alarm threshold.
1. Check whether the configured threshold is reasonable.
Y-> Goto Step 3.
N-> Goto Step 2.
68
2. Modify the configuration and synchronize the data. Check

Y-> End.
N-> Goto Step 3.
3. It is necessary to check whether the configuration model has
faults according to additional information of this alarm.
Please contact ZTE Corporation.
Verification
Precautions
None
Equipment Alarm
This section introduces the equipment Alarm description.
Loss of Optical Transceiver Module

Signal
Alarm
Information
Reason
Alarm code: 2
Severity: Major
Alarm description: The optical module has no signal.
1. The local receiving fiber (RX) or peer-end transmitting fiber

(TX) is not connected well.
2. The optical module of the local end or peer end is faulty.
3. The peer end is forbidden to export optical signal.
Processing
method
1. Connect the local and the peer-end fibers, and check

Y-> End.
N-> Goto Step 2.
2. Replace this fiber, and check whether the alarm disappears.
Y-> End.
N-> Goto Step 3.
3. Replace the local optical module, and check whether the
alarm disappears.
Y-> End.
N-> Goto Step 4.
69
4. Replace the peer-end optical module, and check whether the

alarm disappears.
Y-> End.
N-> Goto Step 5.
5. Check whether the peer-end equipment is forbidden to
export optical signal and if the alarm disappears.
Y-> End.
Verification
The alarm disappears, this optical module and the link work
normally.
Precautions
None
Clock Phase Does not Match When

Inputting 8K, 16M Clock to
Backboard
Alarm
Information
Alarm code: 1284
Severity: Minor
Reason
Processing
method
Alarm description: The input 8K clock phase of the backplane

does not match the input 16M clock phase of the backplane.
There is something wrong with clock input to this shelf. The

clock line is not well connected or has faults.
1. Check whether the clock line is well connected to this shelf.
Y-> Check whether the alarm disappears. Y-> End. N-> Goto
Step 2.
Verification
Precautions
None
Clock Chip of This Board Is in

Preheat Status
Alarm
Information
Alarm code: 1285
Severity: Minor
70
Alarm description: The clock chip of this board is in preheat

status
Reason
Processing
method
The board goes through cold reset. The crystal oscillator of the
SETS chip needs to be fully preheated
Record the alarm information and Contact ZTE Corporation.
Verification
Precautions
None
Inconsistent BOOT/EPLD Version

No. with Database Configurations
Alarm
Information
Alarm code: 5891
Severity: Minor
Reason
Alarm description: The BOOT/EPLD version

inconsistent with the database configuration.
No.
is
1. The running BOOT version does not match the database

version.
2. The running EPLD version does not match the database
version.
Processing
method
Switch BOOT/EPLD again and restart the board manually. After

the board begins running normally, the alarm disappears.
Verification
Precautions
None
Boot Version Fails to Be Written to

Backup Region
Alarm
Information
Alarm code: 5892
Severity: Minor
Reason
Processing
method
Alarm description: BOOT version backup area fails to be

covered.
Bootflash backup area fails to be covered.

Switch BOOT again and restart the board manually. After the
board begins running normally, the alarm disappears.
Verification
Precautions
None
71
Board Connection Check Is Off

Alarm
Information
Alarm code: 25600
Severity: Minor
Alarm description: The board connection check is disabled.
Reason
The connection check switch is off, causing PP service process

unable to execute connection check.
Processing
method
It is necessary to stop the connection check. Contact ZTE

Corporation.
Verification
Precautions
None
IDE Initialize Fail

Alarm
Information
Alarm code: 3072
Severity: Major
Reason
Processing
method
Alarm description: Maybe IDE is physically destroyed or in

write protection for MP board
The hard disk is broken.
The hard disk enters into the read-write protection status
because it is used for a too long time.
The hard disk is not formatted before delivery.
Check the exceptional logs. If it is recorded in the logs that the

restart reason is that the hard disk is broken, it is recommended
to replace the hard disk that failed to be initialized.
Verification
Precautions
None
Internal Port of Board Is Down

Alarm
Information
Alarm code: 5376
Severity: Major
72
Alarm description:
exceptional.
The
port
on
the
media
plane
is
Reason
1. The number of internal ports configured for this board and

the neighboring slots exceeds the number that the physical
slots can provide.
2. The pin of this slot on the backplane is damaged.
Processing
method
1. Check whether the number of internal ports configured for

this board and the neighboring slots exceeds the number
that the physical slots can provide.
Y-> Goto Step 2.
N-> Modify the configuration and synchronize data. Then
check the alarm disappears. Y-> End. N-> Goto Step 2.
2. Check the board to see if there is any clock input alarm.
Y-> Follow the handling suggestions of the related alarms to
do troubleshooting. Check whether the alarm disappears. Y> End. N-> Goto Step 3.
N-> Goto Step 3.
3. Replace the backplane or change the configured slot. Check
Y-> End.
N-> Goto Step 4.
4. Switch the active/standby UIM boards in the same shelf and
then check whether the alarm disappears.
Y-> End.
N-> Goto Step 5.
disappears.
Y-> End.
Verification
Precautions
When the alarm occurs, the BRS cannot perform any processing
related with the level-2 forwarding table.
Input Clock Abnormal

Alarm
Information
Reason
Alarm code: 5381
Severity: Major
Alarm description: The input clock is exceptional.
The clock board runs exceptionally, and is not in the normal

working status.
No clock reference is input to the clock board or the clock
reference is exceptional.
73
Processing
method
1. Check whether the configured clock reference is correctly

inputted.
Y-> Goto Step 2.
N-> Input the clock reference and then check whether the
alarm disappears. Y-> End. N-> goto Step 2.
disappears.
Y-> End.
Verification
Precautions
None.
IDE THRESHOLD Alarm

Alarm
Information
Alarm code: 5632
Severity: Critical
Alarm description: The hard disk is full.
Reason
The usage rate of the hard disk exceeds the threshold of one
level.
Processing
method
1. Check whether the threshold value configured on the

background is too low.
Y-> Goto Step 2.
N-> Goto Step 3.
2. Modify the threshold value to a normal one and synchronize
data. Check whether the alarm disappears.
Y-> End.
N-> Goto Step 3.
3. Delete those useless data. Then goto Step 4.
4. Switch the board and use the hard disk on the new main
board. End the alarm handling.
Verification
Precautions
The alarm may cause data loss.
Hard Disk Broken

Alarm
Information
74
Alarm code: 5633
Reason
Processing
method
Severity: Critical
Alarm description: The hard disk of the board is broken.
The hard disk of the board is broken.

1. Switch the board and use the hard disk on the new main
board.
2. Contact ZTE Corporation for hard disk replacement.
Verification
Precautions
The alarm may cause data loss.
ENUM Switch of Board Opened

Alarm
Information
Alarm code: 5635
Severity: Critical
Alarm description: The ENUM switch of the broad is opened.
Reason
The ENUM switch of the broad is opened. Or the EXCH key on

the standby board is pressed down for twice within 3 seconds.
Processing
method
1. Check the ENUM switch and switch it on. Check whether the
alarm disappears.
Y-> End.
N-> Goto Step 2.
2. If it is caused by pressing the EXCH key, switch it on/off
again. Check whether the alarm disappears.
Y-> End.
Verification
Precautions
None.
SMBUS Error
Alarm
Information
Reason
Alarm code: 5636
Severity: Critical
Alarm description: SMBUS error
If the board is reset when the read-write time sequences of the

SMBUS equipment are not finished, the SMBUS cannot be
enabled after the south bridge is reset. All the SMBUS
equipments need be reset again (the board need be pulled out
and plugged).
75
Processing
method
Pull out and plug the board, and check whether the alarm
disappears.
Y-> End.
N-> Replace the board and end the alarm handling.
Verification
Precautions
If the SMBUS is disabled, start the MPX86 board through the

BIOS setting. After the version runs, the temperature of the
board should be measured. For the MPX86 board whose SMBUS
is faulty, its temperature cannot be normally measured, so it is
possible that the board runs in the high-temperature condition,
but the maintenance personnel does not know it.
In addition, for the MPX86 board whose SMBUS is faulty, its
memory size is configured by default, but does not definitely
accord with the actual configuration.
Error in Rear Board that Mismatches

with Front Board
Alarm
Information
Alarm code: 5637
Severity: Critical
Reason
Processing
method
Alarm description: Error in the back board that mismatches

the front board.
The rear board mismatches the front board.

1. Replace the rear board with one matching the front board,
and then check whether the alarm disappears.
Y-> End.
N-> Goto Step 2.
Verification
Precautions
None
LVDS Signal Unlocked

Alarm
Information
Alarm code: 5638
Severity: Major
Reason
76
Alarm description: LVDS signal at the bottom layer is

unlocked.
LVDS signal at the bottom layer is unlocked.
Processing
method
Switch or pull out and plug the board, and then check whether
Y-> End.
Verification
Precautions
None
High Error Rate of Optical Interface

Alarm
Information
Alarm code: 5639
Severity: Major
Reason
Alarm description: The bit error rate of the optical interface

is too high, which does not frequently happen.
1. The fiber is not connected well or is damaged.

2. The fiber does not match the optical module.
Processing
method
1. Check whether the fiber is connected well.

Y-> Goto Step 3.
N-> Goto Step 2.
2. Connect the fiber or replace it with anther one. Check
Y-> End.
N-> Goto Step 3.
3. Check whether the fiber matches the optical module.
N-> Goto Step 4
4. Replace the fiber, and check whether the alarm disappears.
Y-> End.
Verification
Precautions
None
FPGA Exception
Alarm
Information
Alarm code: 5640
Severity: Major
77
Alarm description: FPGA exception, such as FPGA loss and

the loss of the clock on the mother board.
Reason
The FPGA runs abnormally. For example, the FPGA is lost and
the mother board clock is lost.
Processing
method
1. Restart the board, and the board will download the FPGA
again.
2. If the alarm still exists, Contact ZTE Corporation.
Verification
Precautions
None
Hardware Reliability Down

Alarm
Information
Reason
Processing
method
Alarm code: 5642
Severity: Major
Alarm description: The reliability of the hard disk declines.
There are hardware faults in the hard disk.

1. Use a new hard disk and configure it. Then check whether
the new hard disk gives this alarm.
Y-> Goto Step 2.
N-> End.
2. Switch the active/standby boards and use the hard disk on
the new main board. Then check whether this hard disk gives
this alarm.
Y-> Goto Step 3.
N-> End.
Verification
Precautions
The alarm may cause data loss or system paralysis.
The Channel in a Subcard Is Down

Alarm
Information
Reason
78
Alarm code: 5644
Severity: Minor
Alarm description: The sub-card channel is exceptional.
There are hardware faults in the sub-card channel, or it is not

inserted in position.
Processing
method
1. Insert the sub-card in position, and check whether the alarm

disappears.
Y-> End.
N-> Goto Step 2.
2. Reset the board, and check whether the alarm disappears.
Y-> End.
Verification
Precautions
None
Subcard Abnormal
Alarm
Information
Reason
Alarm code: 5645
Severity: Critical
Alarm description: The sub-card is exceptional.
The UIM/CHUB GCS sub-card is exceptional. The possible

reasons are:
1. The sub-card is not inserted in position.
2. Packet loss occurs in case of heavy traffic.
3.
Processing
method
Other reasons cause this fault.
Check the sub-card connection to see if it looses. Insert the subcard in position and then check whether the alarm disappears.
Y-> End.
N-> Contact ZTE Corporation for sub-card replacement.
Verification
Precautions
None
Phase-lock Loop Unlock

Alarm
Information
Reason
Processing
method
Alarm code: 5646
Severity: Critical
Alarm description: The phase-locked loop is unlocked.
The phase-locked loop is unlocked due to the hardware fault.

Contact ZTE Corporation to replace the board.
79
Verification
Precautions
None
High Error Rate at E1 Bottom Layer

Alarm
Information
Alarm code: 5647
Severity: Critical
Alarm description: The bit error rate at the E1 bottom layer

is too high.
Reason
The E1/T1 link is faulty, or there is any other equipment fault in

the uplink direction of the trunk link.
Processing
method
1. Check whether the trunk link at the local end is faulty and
eliminate the primary fault. After that, check whether the
alarm disappears.
Y-> End.
N-> Goto Step 2.
2. Check whether there is any other equipment fault in the
uplink direction of the trunk link, and eliminate it if there is.
After that, check whether the alarm disappears.
Y-> End.
Verification
Precautions
None
Microcode Is Abnormal
Alarm
Information
Reason
Alarm code: 15360
Severity: Critical
Alarm description: The microcode runs abnormally.
1. The microcode gets into an endless loop.

2. There are hardware faults in the micro engine.
3. There are hardware faults in Cp or Xp.
Processing
method
1. Restart the board where the alarm occurs (board of Release

version restarts automatically). Check whether the fault is
eliminated after the board is restarted.
Y-> End.
N-> Goto Step 2.
80
2. Pull out/insert the board to check whether the fault is

eliminated after the board is restarted.
Y-> End.
N-> Goto Step 3.
3. Replace the board to see whether the fault is eliminated.
Y-> End.
N-> Contact ZTE Corporation Cooperation.
Verification
Precautions
None
Faulty Frames Received by Internal

Switching Interface Faulty
Alarm
Information
Alarm code: 15873
Severity: Critical
Reason
Alarm description: The number of horizontal-check errors

received by the CSIX exceeds the threshold.
1. There are hardware faults in the switching chips of this board.

2. The PSN board in the same shelf is abnormal.
3. The sub-card of the network processor is loose.
Processing
method

version can restart automatically).
2. After the board is restarted, check whether the fault is
eliminated.
Y-> End.
N-> goto Step 3.
3. Pull out/insert the board where the alarm occurs to check
whether the fault is eliminated.
Y-> End.
N-> Goto Step 4.
4. Replace the board, and check whether the fault is eliminated.
Y-> End.
Verification
Precautions
None
81
Board Link-Level Flow Control

Alarm
Information
Alarm code: 15874
Severity: Critical
Reason
Alarm description: The link-level flow control failed to be

eliminated.
1. There are hardware faults in the board.

2. The traffic to this board is too heavy.
3. One board in the same shelf is reset when there is traffic to
this board.
4. The PSN board in the same shelf is abnormal.
5. The sub-card of the network processor is loose.
Processing
method

version can restart automatically).
2. After the board is restarted, check whether the fault is
eliminated.
Y-> End.
N-> Goto Step 3.
3. It is necessary to check whether PSN in the same shelf is
faulty.
Y-> Refer to the handling method of the corresponding alarm.
N-> Goto Step 4.
4. Plug out and insert the board where the alarm appears, and
check whether the fault is eliminated.
Y-> End.
N-> Goto Step 5.
Y-> End.
Verification
Precautions
None
Automatic Protection Switching

Channels Mismatched
Alarm
Information
82
Alarm code: 19712
Severity: Major
Alarm description: Mismatch of the automatic protection
switchover channel
Reason
There are faults at the peer end (configuration faults or devices

not supported, and the symptom is that the bridging channel
that the remote end indicates through K2 is not the one required
by the local end.)
Processing
method
1. Check whether the configurations on the two ends are

consistent. (1+1 or 1:1 (1:N))
Y-> Goto Step 2.
N-> Modify them to be consistent and check whether the
alarm disappears. Y-> End, N-> Goto Step 2.
2. Check whether the optical fiber connections are correct.
Y->Contact ZTE Corporation.
N-> Connect the optical fibers correctly and check whether
the alarm disappears. Y-> End. N-> Contact ZTE Corporation.
Verification
Precautions
None
APS Protection Mode Mismatch

Alarm
Information
Alarm code: 19713
Severity: Major
Reason
Alarm description: Mismatch of the automatic protection

switchover mode
The protection types at the two ends are inconsistent. The

protection type at one end is 1+1, and that at the other end is 1:
n.
Protection types on the two ends are inconsistent, one end
adopts 1+1 mode, and the other end adopts 1: n mode, (oneway or two-way)
Processing
method
1. Check whether the configured protection types on the two

ends are consistent. Both of them are 1+1 or 1:1(1: N) and
one-way mode or two-way mode.
Y-> Goto Step 2.
N-> Modify them on two ends to be consistent, and check
whether the alarm disappears. Y-> End. N-> Goto Step 2.
2. Check whether the fiber connections are correct.
N-> Connect the optical fibers correctly and check whether
83
Verification
Precautions
None
APS Reset Board

Alarm
Information
Reason
Alarm code: 19714
Severity: Major
Alarm description: APS resets the board.
1. The board is configured to 1+1 mode, without aps configured.

2. The FE or the HW fails to be opened.
Processing
method
Check whether the backup mode configured on the board is

consistent with that of the APS optical port.
(1:1 backup mode of the board corresponds to inter-board
backup mode of the APS optical port, non-backup mode of the
board corresponds to the inner-board backup or non-backup
mode of APS optical port).
Y-> goto Step 2.
N-> Modify the configured backup modes to be consistent, and
check whether the alarm disappears. Y-> End. N-> Contact ZTE
Corporation.
Verification
Precautions
None
CLKG 32M Output Clock Lost

Alarm
Information
Reason
Processing
method
84
Alarm code: 26112
Severity: Major
Alarm description: The 32M output clock is lost.
The 32M output clock of the CLKG board is lost.

Check (measure) the output clock of the CLKG board. If the
output clock is exceptional, replace the CLKG board.
Verification
Precautions
None
CLKG 32M8K Output Clock Lost

Alarm
Information
Reason
Processing
method
Alarm code: 26113
Severity: Major
Alarm description: The 32M8K output clock is lost.
The 32M8K output clock of the CLKG board is lost.

Verification
Precautions
None
CLKG 16M Output Clock Lost

Alarm
Information
Reason
Processing
method
Alarm code: 26114
Severity: Major
Alarm description: The 16M output clock is lost.
The 16M output clock of the CLKG board is lost.

Check the CLKG board and the software.
Verification
Precautions
None.
CLKG 16M8K Output Clock Lost

Alarm
Information
Reason
Processing
method
Alarm code: 26115
Severity: Major
Alarm description: The 16M8K output clock is lost.
The 16M8K output clock of the CLKG board is lost.

Verification
Precautions
None.
85
CLKG PP2S Output Clock Lost

Alarm
Information
Reason
Processing
method
Alarm code: 26116
Severity: Major
Alarm description: The CLKG PP2S output clock is lost.
There are hardware faults in the board.

Replace the board, and check whether this alarm disappears.
Y-> End.
Verification
Precautions
None
PP2S Clock Reference Lost

Alarm
Information
Reason
Processing
method
Alarm code: 26117
Severity: Major
Alarm description: The PP2S clock reference is lost.

1. Check type of the alarm board.
CLKG-> Goto Step 2.
ICM-> Goto Step 3
2. Check whether the PP2S clock is correctly led to the CLKG
from the GCM.
Y-> Goto Step 3.
N-> Correctly lead the PP2S clock to the CLKG, and check
whether this alarm disappears. Y-> End. N-> Goto Step 3.
3. Replace the board, and check whether this alarm disappears.
Y-> End.
86
Verification
Precautions
None
16CHIP Clock Reference Lost

Alarm
Information
Reason
Processing
method
Alarm code: 26118
Severity: Major
Alarm description: The 16CHIP clock reference is lost.

Replace the board, and check whether this alarm disappears.
Y-> End.
Verification
Precautions
None
All Clock Bases Had Lost

Alarm
Information
Reason
Processing
method
Alarm code: 26119
Severity: Major
Alarm description: All the clock reference sources are lost.
The loss of the clock reference is successfully detected for the

first time.
Check the access reference of the CLKG board (through the
back board) and the background configuration.
Verification
Precautions
None
CLKG
CLKG I2MB0 Clock Base Lost

Alarm
Information
Reason
Processing
method
Verification
Alarm code: 26120
Severity: Minor
Alarm description: The I2MB0 clock reference is lost.
The I2MB0 clock reference is lost.
Check 2MB0 input of the RCKG.
Check the background configuration.
87
Precautions
None
CLKG I2MB1 Clock Base Lost

Alarm
Information
Reason
Processing
method
Alarm code: 26121
Severity: Minor
Alarm description: The I2MB1 clock reference source is lost.
The I2MB1 clock reference source is lost.
Check 2MB1 input of the RCKG.
Verification
Precautions
None
CLKG I2MHZ0 Clock Base Lost

Alarm
Information
Reason
Processing
method
Alarm code: 26122
Severity: Minor
Alarm description: The I2MHZ0 clock reference source is lost.
The I2MHZ0 clock reference source is lost.
Check 2MHZ0 input of the RCKG.
Verification
Precautions
None
CLKG I2MHZ1 Clock Base Lost

Alarm
Information
Reason
Processing
method
Verification
88
Alarm code: 26123
Severity: Minor
Alarm description: The I2MHZ1 clock reference source is lost.
The I2MHZ1 clock reference source is lost.
Check 2MHZ1 input of the RCKG.
Precautions
None
CLKG I8KBASE Clock Base Lost

Alarm
Information
Alarm code: 26124
Severity: Minor
Reason
Processing
method
Alarm description: The I8KBASE clock reference source is

lost.
The I8KBASE clock reference source is lost.
Check 8KBASE input of the RCKG.
Verification
Precautions
None
CLKG I8KGPS Clock Base Lost

Alarm
Information
Reason
Processing
method
Alarm code: 26125
Severity: Minor
Alarm description: The I8KGPS clock reference source is lost.
The I8KGPS clock reference source is lost.
Check 8KGPS input of the RCKG.
Verification
Precautions
None
CLKG I8KUIM Clock Base Lost

Alarm
Information
Reason
Processing
method
Verification
Alarm code: 26126
Severity: Minor
Alarm description: The I8KUIM clock reference source is lost.
The I8KUIM clock reference source is lost.

As the CLKG, this reference should not act as the reference
source.
89
Precautions
None
Clock Reference Source Lost (Level

3 Alarm)
Alarm
Information
Alarm code: 26127
Severity: Minor
Reason
Processing
method
Alarm description: Level-3 alarm due to the loss of the clock

reference source.
Clock reference loss is detected for the first time.

1. Check whether the corresponding clock reference is correctly
led in.
Y-> Replace the board, and goto Step 2.
N-> Correctly lead in this clock reference, and goto Step 2.
2. Check whether this alarm disappears.
Y-> End.
Verification
Precautions
None

2 Alarm)
Alarm
Information
Alarm code: 26128
Severity: Major
Reason
Processing
method

reference source.
The clock reference has been lost for more than 10 minutes.
led in.
Y-> End.
90
Verification
Precautions
None

1 Alarm)
Alarm
Information
Alarm code: 26129
Severity: Critical
Reason
Processing
method

reference source.
The clock reference has been lost for more than 24 hours.
led in.
Y-> End.
Verification
Precautions
None
Clock Base Lost

Alarm
Information
Alarm code: 26130
Severity: Minor
Reason
Processing
method
Alarm description: Alarm due to the loss of the clock

reference source.
The clock reference source configured at the background is lost.
Check the access reference of the

CLKG back board).
CLKG
board (through the
Check whether the back board is loose.
Verification
Precautions
None
91
The Client of Sntp Failed in Fetching

Net Time
Alarm
Information
Alarm code: 8392705
Severity: Minor
Reason
Processing
method
Alarm description: The Sntp client failed to get the network

clock.
The NTP server does not exist or work normally.
The IP address of the NTP server configured in the database
does not conform to the actual situation.
Check whether the NTP server exists or works normally.
Make sure that the IP address of the NTP server configured
in the database conforms to the actual situation.
Verification
Precautions
None
TRUNK Is Down
Alarm
Information
Reason
Processing
method
Alarm code: 8394242
Severity: Minor
Alarm description: TRUNK port down.
The TRUNK ports are not all connected through network cable,
or the network cable or the BCM5615 port is faulty.
Check whether the network cable or the BCM5615 port is normal.
Verification
Precautions
None
OMP to NTP Server Sync Failure

Alarm
Information
Severity: Minor
92
Alarm description: The OMP does not synchronize the time

with the NTP server.
Reason
Processing
method
The OMP does not synchronize the time with the NTP server.
Check whether the corresponding NTP server is configured in the
local office; check whether the configured NTP server works
normally; and check whether the communication between the
local office and the NTP server is normal
Verification
Precautions
None
MAC Address Conflict Exists in

Boards of Same Shelf
Alarm
Information
Alarm code: 5650
Severity: Minor
Reason
Processing
method
Alarm description: MAC address conflict exists in boards of

the same shelf.
The board is not inserted in position.
The DIP switch setting changes.
Other reasons cause this alarm.
1. Check whether the DIP switch setting changes or if the board

is restarted after modifying DIP switch setting.
N-> If the DIP switch setting is not changed, goto Step 2. If
the board is not restarted after modifying DIP switch setting,
restart the board and check whether the alarm disappears.
Y-> End. No-> Goto Step 2.
2. Pull out and plug the board and then check whether the
alarm disappears.
Y-> End.
Verification
Precautions
None
Type A Fault on Board (GPS)

Phase-lock Equipment
Alarm
Information
Alarm code: 5652
Severity: Critical
93
Reason
Processing
method
Alarm description: The A-class error occurs to the GPS

phase-locked equipment.

Verification
Precautions
The alarm is often related to the exceptional working of the

SETS chip.
Type B Fault on Board (GPS)

Phase-lock Equipment
Alarm
Information
Alarm code: 5653
Severity: Major
Reason
Processing
method
Alarm description: There are class-B faults in the PLL of the

GPS board.

Verification
Precautions
None
Phase-lock Equipment of This Board

(GPS) Is in Power-on Status
Alarm
Information
Alarm code: 5654
Severity: Critical
Reason
Processing
method
94
Alarm description: The PLL of the GPS board is in power-on

status.

Contact ZTE Corporation to replace the faulty board.
Verification
Precautions
None
Cx29704 Runs Abnormally

Alarm
Information
Alarm code: 6400
Severity: Minor
Reason
Processing
method
Alarm description:
exceptional.
The
working
status
of
Cx29704
is
It is a chip fault. If it can be recovered immediately, it is a false

alarm. If it can not be recovered, it must result from some chip
bugs. In that case, it is required to reset the board.
It is a chip fault. Contact ZTE Corporation to replace the board.
Verification
Precautions
None
The Port Connection between the

GLI and the UIM Is Inconsistent with
the Configuration
Alarm
Information
Alarm code: 5187
Severity: Minor
Reason
Processing
method
Alarm description: The port connection between the GLI and

the UIM is inconsistent with the configuration.
The fiber connection between the GLI and the

inconsistent with that configured on the background.
UIM
is
1. Check the GLI optical interface connection relation configured

on the background to see if the configuration is consistent
with the actual connection.
Y-> Goto Step 2.
N-> Modify the fiber connection according to the
configuration, and check whether the alarm disappears. Y->
End. N-> Goto Step 2.
Verification
Precautions
None
95
Stack Overflow
Alarm
Information
Reason
Processing
method
Alarm code: 2624
Severity: Minor
Alarm description: The stack overflows.
The number of stacks used by the process reaches the threshold

value or the protection page is modified.
Record the alarm information, and Contact ZTE Corporation.
Verification
Precautions
None
Process Deadlocked
Alarm
Information
Reason
Processing
method
Alarm code: 2625
Severity: Minor
Alarm description: The process is in the dead lock state.
Maybe it results from occurrence of resource deadlocks, such as

semaphore deadlocks.
Reset the board, and check whether the alarm disappears.
Y-> End.
Verification
Precautions
None
IDE Version Synchronization

Information
Alarm
Information
Reason
96
Alarm code: 5960
Severity: Minor
Alarm description: Version switch fails.
There exist active processes on the standby board when

updating EPLD.
Processing
method
Switch some active functions (such as optical interfaces) to

standby ones on the standby board through MML commands on
the background. Check whether the alarm disappears.
Y-> End.
Verification
Precautions
None
Board Device Is Abnormal

Alarm
Information
Reason
Processing
method
Alarm code: 5663
Severity: Major
Alarm description: The board element is faulty.
An element or sub-card on the board work abnormally.

Replace the board.
Verification
Precautions
None
Exceptional Internal Media Plane

Communication
Alarm
Information
Alarm code: 5396
Severity: Major
Reason
Processing
method
Alarm description: The internal media plane test message is

exceptional.
The message loss rate of the media plane in a board exceeds the
set threshold (25% by default), which seldom happens.
For the level-1 switching board:
1. Restart the board and then check whether the alarm
disappears.
Y-> End.
N-> Goto Step 2.
2. Restart the PSN that is associated with the board, and then
Y-> End.
97
N-> Goto Step 3.

3.
Replace the slot, and then check whether the alarm

disappears.
Y-> End.
For the non-level-1 switching board:

1. Restart the board, and then check whether the alarm
disappears.
Y-> End.
N-> Goto Step 2.
2. Switch the active/standby UIM boards in the same shelf, and
then check whether the alarm disappears.
Y-> End.
N-> Goto Step 3.
3. Replace the slot, and then check whether the alarm
disappears.
Y-> End.
Verification
Precautions
None
Loss of Clock When Input to Board

Alarm
Information
Reason
Processing
method
Alarm code: 1286
Severity: Minor
Alarm description: The input clock of the board is lost.
There are problems in the input clock of this shelf.

Check whther the clock input cable is well connected.
N-> Connect it well.
Verification
Precautions
None
SDH/SONET: Loss of Signal

Alarm
Information
98
Alarm code: 1792
Reason
Severity: Major
Alarm description: SDH/SONET: Loss Of Signal (LOS).
The upstream optical sending equipment is faulty;
The optical fiber transmission line is faulty;
Processing
method
The tail fiber and the flange between the local-end ODF and
the equipment are faulty;
The local-end optical receiver is faulty.
The normal receiving optical power should be less than -8dBm

and greater than -28dBm.
1. Use the optical power meter to detect the power for receiving
optical signal at local end to see if the power is within the
above-mentioned range.
Y-> Goto step 3.
N-> It means the optical module is faulty. In this case, goto
step 2.
2. Replace the optical module or board, and then check whether
Y-> End.
N-> Goto Step 3.
3. Detect the transmitting optical signal at the transmitting end
of the peer-end office to see if the power is within the
specified range.
Y-> Goto step 5.
N-> It means that there are faults at the peer end. In this
case, goto step 4.
4. Check the peer-end office. After troubleshooting the peerend office, check whether the alarm disappears.
Y-> End.
N-> Goto step 5.
5. There may be something wrong with the transmission
equipment. Troubleshoot the transmission equipment or
Verification
Precautions
None
SDH/SONET: Loss of Frame

Alarm
Information
Alarm code: 1793
99
Reason
Processing
method
Severity: Major
Alarm description: SDH/SONET: Loss Of Frame (LOF).
The upstream SDH equipment is faulty.

Ask the related maintenance personnel to troubleshoot the SDH
transmission equipment. Contact ZTE Corporation if the problem
can not be solved.
Verification
Precautions
None
SDH/SONET: Regenerator Section

Trace Mismatch/Section Trace
Mismatch
Alarm
Information
Alarm code: 1794
Severity: Major
Alarm description: SDH/SONET: regeneration section track

mismatch (RS_TIM).
Reason
The optical fiber on the Optical Distribution Frame (ODF) is

wrongly connected during optic fiber cutover and scheduling, or
the expected value is wrongly set in the network management
system.
Processing
method
1. Check whether there is something wrong with the optic fiber

connections on ODFs at the local end and the peer end.
Y-> Goto step 2.
N-> Goto step 3.
2. Have the optic fiber well connected, and check whether the
alarm disappears.
Y-> End.
N-> Goto Step 3
3. Check whether the expected values of the section access
point identifier at both ends are consistent.
Y-> Goto step 5.
N-> Goto step 4.
4. Configure the same expected value for the section access
point identifier at both ends, and then check whether the
alarm disappears.
Y-> End.
N-> Goto Step 5
100
5. Contact ZTE Corporation if the problem can not be solved.

Verification
Precautions
None
SDH/SONET: MS-AIS, Line Alarm

Indication Signal
Alarm
Information
Alarm code: 1795
Severity: Major
Alarm description: SDH/SONET: Multiplexing Section Alarm

Indication Signal (MSAIS).
Reason
There are faults in the upstream equipment, including LOS, LOF

and RS TIM.
Processing
method
Eliminate the primary fault according to the alarm generated

from the network node equipment in the corresponding
multiplexing section. If the alarm can not be eliminated, Contact
ZTE Corporation.
Verification
Precautions
None
SDH/SONET: Multiplex Section Farend Reception Failure/Line Far-end

Reception Failure
Alarm
Information
Alarm code: 1796
Severity: Minor
Alarm description: SDH/SONET: multiplexing section remote

receiving failure (MSFERF).
Reason
There are faults in the uplink direction of the downstream

equipment.
Processing
method

from the network node equipment in the corresponding
multiplexing section. If the alarm can not be eliminated, Contact
ZTE Corporation.
Verification
Precautions
None
101
SDH/SONET: Signal Failure

Alarm
Information
Reason
Alarm code: 1797
Severity: Major
Alarm description: SDH/SONET: Signal Failure (SF).
Processing
method
Error codes occur because the fiber pigtail on the downlink

direction of all the NEs in the multiplexing section where the
board is located is contaminated, transmission line
attenuation enhances or the optical transmission mode
changes.
The ADM sending equipment is faulty.
1. Check whether the fiber pigtails are contaminated.

Y-> Goto step 2.
N-> Goto Step 3
2. Clean the fiber pigtails, and check whether the alarm
disappears.
Y-> End.
N-> Goto 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 if it
is excessive.
Y-> Goto step 4.
N-> Goto Step 5
4. Adjust the attenuation to normal value, and check whether
Y-> End.
N-> Goto Step 5
5. Ask the transmission network maintenance personnel to
check whether the ADM sending equipment is faulty. End
alarm handling.
Verification
Precautions
None
SDH/SONET: Signal Deterioration

Alarm
Information
102
Alarm code: 1798
Severity: Minor
Alarm description: SDH/SONET: Signal Deterioration (SD).
Reason
Eliminate SF first when SD and SF occur at the same time. If SD

occurs alone, it can be concluded that the ADM transmission
device is faulty.
Processing
method
1. If SF occurs, eliminate SF first. If the problem still can not be

eliminated after SF is eliminated, goto step 2.
2. Check the optical fibers and fiber optical modules at the local
end and the peer end, and make sure the optical fibers are
well connected and the optical modules do not loose. Check
Y-> End.
N-> Goto Step 3.
3. Replace the optical modules or boards, and then check
Y-> End.
N-> Goto Step 4.
4. It is required to ask the maintenance personnel to check the
peer-end office. After troubleshooting the peer end, check
Y-> End.
N-> Goto Step 5.
equipment. It is required to ask the maintenance personnel
troubleshoot the transmission equipment, or Contact ZTE
Corporation.
Verification
Precautions
None
SDH/SONET: Loss of AU-4

Pointer/Loss of Channel Pointer
Alarm
Information
Reason
Processing
method
Alarm code: 1799
Severity: Minor
Alarm description: SDH/SONET: Loss of AU-4 pointer.
The upstream AU-4 pointer processing unit is faulty.

Ask the transmission network maintenance personnel to check
whether the upstream AU-4 pointer processing unit is faulty. If
no fault is found in the upstream AU-4 pointer processing unit,
103
Verification
Precautions
None
SDH/SONET: AU-AIS/Channel-AIS
Alarm
Information
Alarm code: 1800
Severity: Minor
Reason
Processing
method
Alarm description:
Signal (AU4AIS).
SDH/SONET:
AU-4
Alarm
Indication
The upstream VC-4 channel control unit is faulty.

Check whether the upstream VC-4 channel control unit is faulty.
whether the upstream VC-4 channel control unit is faulty. If no
fault is found in the upstream VC-4 channel control unit, Contact
ZTE Corporation.
Verification
Precautions
None
SDH/SONET: HP-Trace
Mismatch/Patch Trace Mismatch
Alarm
Information
Alarm code: 1801
Severity: Minor
Alarm description: SDH/SONET: VC-4 signal trace mismatch

(VC4TIM).
Reason
The optical fiber on the ODF is wrongly connected, or the

expected value is wrongly set in the network management
system during optic fiber cutover and scheduling.
Processing
method
1. Check whether there is something wrong with the optical

fiber connections on ODFs at the local end and the peer end.
Y-> Goto Step 3.
N-> Goto 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.
Y-> End.
N-> Goto Step 3.
104
3. Check whether the expected values of the VC-4 channel

access point identifier (J1B) at both ends are consistent.
Y-> Goto Step 5.
N-> Goto Step 4.
4. Configure the same expected value for the VC-4 channel
access point identifier (J1B) at both ends, and then check
Y-> End.
N-> Goto Step 5.
Verification
Precautions
None
SDH/SONET: HP
Unassembled/Path Unassembled
Alarm
Information
Alarm code: 1802
Severity: Minor
Alarm description: SDH/SONET: VC-4 unequipped (UNEQ).
Reason
During engineering installation, the internal cross connection of

SDH network is not complete, or the SDTB remote device is not
equipped with the channel where SDTB is located.
Processing
method

whether the upstream VC-4 channel control unit is faulty (C2B).
Verification
Precautions
None
SDH/SONET: HP Label
Mismatch/Path Label Mismatch
Alarm
Information
Alarm code: 1803
Severity: Minor
Reason
Alarm description: SDH: VC-4 channel label mismatch

(VC4PLM).

SDH network is not complete.
105
Processing
method
Ask the maintenance personnel for transmission network to

check whether the upstream and downstream circuit
configuration (C2B) of the corresponding timeslot of the DXC
devices in each station is correct.
Verification
Precautions
None
SDH/SONET: HP Remote Reception

Failure
Alarm
Information
Alarm code: 1804
Severity: Minor
Reason
Processing
method
Alarm description:
failure (VC4FERF).
SDH/SONET:
VC-4
remote
receiving
There are faults in the VC-4 channel where the board is located.
from the network node equipment in the VC-4 channel where
the board is located. If the alarm can not be eliminated, Contact
ZTE Corporation.
Verification
Precautions
None
SDH/SONET: LOM
Alarm
Information
Alarm code: 1805
Severity: Major
Reason
Processing
method
106
Alarm description:
multiframe.
SDH/SONET:
Loss
of
the
tributary
The upstream VC-4 channel control unit is faulty.

whether the upstream VC-4 channel control unit (H4) is faulty.
Verification
Precautions
None
SDH/SONET: Loss of TU
Pointer/Loss of Virtual Tributary
Pointer
Alarm
Information
Reason
Processing
method
Alarm code: 1806
Severity: Warning
Alarm description: Loss of the tributary pointer (TU12LOP).
The upstream TU tributary pointer processing unit is faulty.

whether the upstream TU-12 tributary pointer processing unit is
faulty. If the problem still cannot be solved, Contact ZTE
Corporation.
Verification
Precautions
None
SDH/SONET: Tributary Unit Alarm

Indication Signal/Virtual Tributary
Alarm Indication Signal
Alarm
Information
Alarm code: 1807
Severity: Warning
Alarm description: SDH/SONET: Tributary alarm indication

signal (TU12AIS)
Reason
A fault occurs in the upstream TU-12 tributary pointer

processing unit, which may be TU AIS, TU LOM, TU LOP, or TU
UNEQ.
Processing
method

whether the upstream TU-12 tributary pointer processing unit is
faulty. If the problem still can not be solved, Contact ZTE
Corporation.
Verification
Precautions
None
107
SDH/SONET: LP Remote Defect

Indication/Virtual Tributary Remote
Defect Indication
Alarm
Information
Alarm code: 1808
Severity: Warning
Reason
Alarm description: SDH/SONET: Tributary remote defect

indication.
1. A function fault occurs in the local TU-12 tributary.

2. Function faults occur in the equipment of other nodes on the
TU-12 tributary.
Processing
method

connections on ODFs at the local end and the peer end, and
check whether the TU-12 tributary pointer processing unit of
the upstream equipment is faulty.
Y-> Goto step 2.
N-> Goto step 3.
2. Have the optic fiber well connected (which is upstream
troubleshooting), and check whether the alarm disappears.
Y-> End.
N-> Goto Step 3
3. Check the alarm forms at both ends. Firstly detect the peerend alarm forms. Eliminate the peer-end alarms firstly.
Trough loopback operation, troubleshoot the local-end
equipment, transmission equipment and peer-end equipment
step by step. Software loopback and hardware loopback can
be applied.
4. Contact ZTE Corporation or replace the board if the problem
can not be solved.
Verification
Precautions
None
SDH/SONET: LP-RFI/Virtual
Tributary-RFI
Alarm
Information
108
Alarm code: 1809
Severity: Warning
Reason
Processing
method
Alarm description: SDH/SONET: Tributary remote failure

indication.
The upstream VC-12 tributary control unit is faulty.

connections on ODFs at the local end and the peer end, and
check whether the TU-12 tributary pointer processing unit of
the upstream equipment is faulty.
Y-> Goto step 2.
N-> Goto step 3.
2. Have the optic fiber well connected (which is upstream
troubleshooting), and check whether the alarm disappears.
Y-> End.
N-> Goto Step 3.
3. Check the alarm forms at both ends. Firstly detect the peerend alarm forms. Eliminate the peer-end alarms firstly.
Trough loopback operation, troubleshoot the local-end
equipment, transmission equipment and peer-end equipment
step by step. Software loopback and hardware loopback can
be applied.
4. Contact ZTE Corporation or replace the board if the problem
can not be solved.
Verification
Precautions
None
SDH/SONET: LP-Trace
Mismatch/Virtual Tributary Trace
Mismatch
Alarm
Information
Alarm code: 1810
Severity: Warning
Alarm description:
mismatch.
SDH/SONET:
Tributary
signal
track
Reason
During the cutover and dispatching of the cable, the cable

connection on Digital Distribution Frame (DDF) is wrong or the
expected value is wrongly set in the network management
system.
Processing
method
1. Check whether there is something wrong with the optical

fiber connections on ODFs at the local end and the peer end.
Y-> Goto Step 3.
N-> Goto Step 2.
109
2. Correctly connect the optical fibers on ODFs at the local end

and the peer end, and then check whether the alarm
disappears.
Y-> End.
N-> Goto Step 3.
3. Check whether the expected values of the VC-12 channel
access point identifier (J2B) at both ends are consistent.
Y-> Goto Step 5.
N-> Goto Step 4.
4. Configure the same expected value for the VC-12 channel
access point identifier (J2B) at both ends, and then check
Y-> End.
N-> Goto Step 5.
5. Contact ZTE Corporation or replace the board.
Verification
Precautions
None
SDH/SONET: LP-Unloaded/Virtual
Tributary Unloaded
Alarm
Information
Alarm code: 1811
Severity: Warning
Alarm description: SDH/SONET: Tributary unequipped.
Reason

SDH network is not complete, or the remote tributary device is
not equipped.
Processing
method
Y-> End.
N-> Goto Step 2.
configuration connection 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 has been eliminated.
Y-> End.
N-> Goto Step 3.
110
3. Ask the transmission equipment maintenance personnel to

use the SDH tester to check whether the upstream and
downstream circuit configuration of the corresponding
timeslot of each DXC node device on the transmission line is
correct. Check whether V5 byte configuration is consistent
with that at peer-end (The default configuration at local end
is asynchronous mapping.)
4. Replace the board, view alarm information, or Contact ZTE
Corporation.
Verification
Precautions
None
SDH/SONET: LP Label
Mismatch/Virtual Tributary Label
Mismatch
Alarm
Information
Alarm code: 1812
Severity: Warning
Alarm description: SDH/SONET: Tributary channel label

mismatch.
Reason
The upstream and downstream circuit configuration of the

corresponding timeslot of each DXC is incomplete. The
information of V5 signal label is inconsistent with that at the
peer end.
Processing
method
Y-> End.
N-> Goto Step 2.
configuration connection at both ends. Check whether the
information of V5 signal label is consistent with that at the
peer end. After confirmation, check whether the alarm
disappears.
Y-> End.
N-> Goto Step 3.
3. Replace the board, view alarm information, or Contact ZTE
Corporation.
Verification
Precautions
None
111
SDH/SONET: VC-4 Signal Failure

Alarm
Information
Reason
Alarm code: 1814
Severity: Major
Alarm description: SDH/SONET: High-order signal failure.
Processing
method
Error codes occur because the fiber pigtail on the downlink

direction of all the NEs in the multiplexing section where the
board is located is contaminated, transmission line
attenuation enhances or the optical transmission mode
changes.
The ADM sending equipment is faulty.
1. Check the optical fibers and optical modules at the local end
and the peer end, and make sure the optical fibers are well
connected and the optical modules do not loose. Check
Y-> End.
N-> Goto Step 2.
2. Replace the optical modules or boards, and then check
Y-> End.
N-> Goto Step 3.
Y-> End.
N-> Goto Step 4.
equipment. It is required to ask the transmission equipment
maintenance personnel to do troubleshooting or Contact ZTE
Corporation.
Verification
Precautions
None
SDH/SONET: VC-4 Signal

Deterioration
Alarm
Information
112
Alarm code: 1815
Severity: Minor
Alarm description: SDH/SONET: VC-4 signal deterioration.
Reason
When SD and SF occur at the same time, eliminate SF first.

When only SD occurs, it can be concluded that the ADM sending
equipment is faulty.
Processing
method
1. If there is SF in VC-4, eliminate it first. If the problem still

cannot be eliminated, goto step 2.
2. Check the optic fibers and fiber optical modules at the local
end and the peer end, and make sure the fibers are well
connected and the optical modules do not loose.
Y-> End.
N-> Goto Step 3.
3. Replace optical modules or boards, and then check whether
Y-> End.
N-> Goto Step 4.
Y-> End.
N-> Goto Step 5.
equipment. It is required to ask the transmission equipment
maintenance personnel to do troubleshooting or Contact ZTE
Corporation.
Verification
Precautions
None
SDH/SONET: MS-Remote Error

Indication
Alarm
Information
Reason
Alarm code: 1820
Severity: Major
Alarm description: SDH/SONET: MS-remote error indication.
The receiving signal attenuation is big.
The sending part of the directly-connected transmission

The fiber pigtail is not clean, or the connector is incorrect.
The receiving part of the local end is faulty.
113
Processing
method
1. Check the optic fibers and optic modules at the local end and
the peer end, and make sure the fibers are well connected
and the optic modules are not loose. Then check whether the
alarm disappears.
Y-> End.
N-> Goto Step 2.
2. Replace the optic modules or boards, and then check
Y-> End.
N-> Goto Step 3.
3. The maintenance personnel are required to check the peerend office. After troubleshooting at the peer end, check
Y-> End.
N-> Goto Step 4.
equipment. The transmission equipment maintenance
personnel are required to troubleshoot the transmission
equipment, or contact ZTE Corporation.
Verification
Precautions
None
SDH/SONET: HP-Remote Error

Indication
Alarm
Information
Reason
Alarm code: 1821
Severity: Major
Alarm description: SDH/SONET: HP-remote error indication.
The receiving signal attenuation is big.
Processing
method
The sending part of the directly-connected transmission

The fiber pigtail is not clean, or the connector is incorrect.
The receiving part of the local end is faulty.
1. Check the optic fibers and optic modules at the local end and
the peer end, and make sure the fibers are well connected
and the optic modules are not loose. Then check whether the
alarm disappears.
Y-> End.
N-> Goto Step 2.
114
2. Replace the optic modules or boards, and then check

Y-> End.
N-> Goto Step 3.
3. The maintenance personnel are required to check the peerend office. After troubleshooting at the peer end, check
Y-> End.
N-> Goto Step 4.
equipment. The transmission equipment maintenance
personnel are required to troubleshoot the transmission
equipment, or contact ZTE Corporation.
Verification
Precautions
None
Semi-fixed Connection Error

Alarm
Information
Reason
Processing
method
Alarm code: 25602
Severity: Minor
Alarm description: The semi-fixed connection is exceptional.
There are errors in the configuration, or the chip is faulty.

Check the configuration and replace the board. If the alarm still
exists, contact ZTE Corporation.
Verification
Precautions
None
T-net Center Fault

Alarm
Information
Reason
Processing
method
Alarm code: 8394008
Severity: Major
Alarm description: There are faults in the T-net center.
There are faults in the board of the T-net center.

1. Replace the slot, and check whether the alarm disappears.
Y-> End.
N-> Goto Step 2.
115
2. Replace the board, and check whether the alarm disappears.

Y-> End.
Verification
Precautions
None
BGP Interface Down, Neighbor Link

Broken
Alarm
Information
Alarm code: 21585
Severity: Major
Reason
Processing
method
Alarm description: The BGP interface is down, and the

neighbor link is broken.
The message that the local port is down is received.

1. Check whether the interface is activated (using command
show ip interface brief).
N-> Goto Step 2.
2. Check whether the port is connected to the network correctly.
N-> Connect the port to the network correctly.
Verification
Precautions
None
Incorrect OSPFv3 Virtual Interface

Configuration
Alarm
Information
Alarm code: 28227
Severity: Minor
Reason
Processing
method
Alarm description: There are errors in the OSPFv3 virtual

interface configuration.
There are errors in the virtual link configuration.

Check whether parameters HelloInterval, DeadInterval and
Options are identical with those of the neighbor at the peer end.
116
N-> Modify configuration parameters and make OSPF parameter

settings identical at both ends.
Verification
Precautions
None
Incorrect OSPFv3 Interface

Configuration
Alarm
Information
Alarm code: 28228
Severity: Minor
Reason
Processing
method
Alarm description: There are errors in the OSPFv3 interface

configuration.
There are errors in the interface configuration.

Check whether parameters HelloInterval, DeadInterval and
Options are identical with those of the neighbor at the peer end.
N-> Modify configuration parameters and make OSPF parameter
settings identical at both ends.
Verification
Precautions
None
Router ID not Configured for

OSPFv3
Alarm
Information
Alarm code: 28231
Severity: Minor
Reason
Processing
method
Alarm description: The OSPFv3 is not configured with router

ID.
The OSPFv3 is not configured with router ID.

Configure an IPv4 address for an interface (It is recommended
to configure an IPv4 address for the Loopback interface), make
it to be a RouterID, and then re-create an OSPF process. Check
Y-> End.
Verification
117
Precautions
None
RouterID Conflict in OSPFv3 Area

Alarm
Information
Reason
Processing
method
Alarm code: 28224
Severity: Minor
Alarm description: The RouterIDs conflict in the OSPFv3 area.
The RouterIDs conflict.

Modify the RouterID of the local end or peer end, restart the
OSPF process, and check whether this alarm disappears.
Y-> End.
Verification
Precautions
None
OMS Alarm
This section introduces the Network Management System (NMS)
Alarm description.
Frequency of Warning Overload

Alarm
Information
Alarm code: 1
System type: Correlation alarm
Severity: Unknown
Reason
Processing
method
118
Alarm description: The frequency of the specified alarm

exceeds the threshold.
The frequency of the specified alarm exceeds the threshold.

Solve the problem according to the reason of the original alarm,
and reduce the frequency of the original alarm.
Verification
Precautions
None
The Time in which the Designated

Alarm Remains Active has Expired
Alarm
Information
Alarm code: 2
Severity: Unknown
Alarm description: The duration of the specified alarm being

in the active status exceeds the threshold.
Reason
The duration of the specified alarm being in the active status

Processing
method
Process the original alarm according to the reason in time to

eliminate it.
Verification
Precautions
None
The Time in which the Designated

Alarm Remains Unacknowledged
has Expired
Alarm
Information
Alarm code: 3
Severity: Unknown
Alarm description: The duration of the specified alarm being

in the unknown status exceeds the threshold.
Reason
The duration of the specified alarm being in the unknown status

Processing
method
Confirm the original alarm in time, or process the original alarm

according to the reason in time to eliminate it.
Verification
Precautions
None
Hard Disk Usage of Database Server

Overload
Alarm
Information
Alarm code: 1001
System type: System management
Severity: Unknown
119
Reason
Processing
method
Alarm description: The usage rate of the database hard disk

The usage rate of the database hard disk is too high.

Periodically clear up the database and export the history data.
Verification
Precautions
None
CPU Usage of Application Server

Overload
Alarm
Information
Alarm code: 1002
Severity: Major
Reason
Processing
method
Alarm description: The usage rate of the COP of the

application server exceeds the threshold.
The usage rate of the COP of the application server exceeds the
threshold.
Ask the system administrator to check it.
Verification
Precautions
None
Ram Usage of Application Server

Overload
Alarm
Information
Alarm code: 1003
Severity: Major
120
Alarm description: The usage rate of the memory of the

Reason
The usage rate of the memory of the application server exceeds

the threshold.
Processing
method
Ask the system administrator to check it or expand the memory.
Verification
Precautions
None
Hard Disk Usage of Application

Server Overload
Alarm
Information
Alarm code: 1004
Severity: Major
Alarm description: The used rate of the hard disk of the

Reason
The usage rate of the hard disk of the application server exceeds
the threshold.
Processing
method
Ask the system administrator to clear up the system or expand

the space of the hard disk.
Verification
Precautions
None
Log Table Usage of Application

Server Overload
Alarm
Information
Alarm code: 1005
Severity: Major
Alarm description: The space used by the logs on the

Reason
The space used by the logs on the application server exceeds

the threshold.
Processing
method
Ask the system administrator to clear the log table data or

export the data.
Verification
Precautions
None
Directory Size Exceed the Threshold

Alarm
Information
Alarm code: 1006
Severity: Major
Reason
Alarm description: The size of the directory exceeds the

threshold.
The size of the directory exceeds the threshold.
121
Processing
method
Ask the system administrator to clear the data under the

directory.
Verification
Precautions
None
Link to Office Is Broken

Alarm
Information
Reason
Processing
method
Alarm code: 1007
Severity: Major
Alarm description: The link to the superior office is broken.
The link to the superior office is broken.

The system administrator checks the status of the link to the
superior office.
Verification
Precautions
None
Database Space Usage too Large

Alarm
Information
Alarm code: 1008
Severity: Unknown
Alarm description: The available space of the database is too

small.
Reason
The available space of the network management database is too

small, which is less than the set threshold.
Processing
method
Periodically clear up the database and export the history data;

or add the space of the database.
Verification
Precautions
None
User Continuously Input Invalid

Password while Logining
Alarm
Information
122
Alarm code: 1000
System type: Security alarm
Severity: Major
Alarm description: The user continuously inputs invalid

passwords while logging in the network management system.
Reason
The user uses invalid usernames and passwords to log in the

network management system.
Processing
method
Use valid usernames and passwords to log in the network

management system again and check the validity of the user.
Verification
Precautions
None
Processing Alarm
This section introduces the processing error alarm.
FLASH Device Failure Alarm

Alarm
Information
Alarm code: 3073
Severity: Major
Reason
Processing
method
Alarm description: The FLASH equipment failed to be

initialized.
Flash is damaged.
1. Check whether there is any backup board for replacement.
Y-> Replace the board, and then check whether the alarm
disappears. Yes-> End. No-> Goto Step 2.
N-> Goto Step 2
2. Record the alarm information and Contact ZTE Corporation.
Verification
Precautions
None
The Config Data of Sntp in DBS Is

Wrong
Alarm
Information
Alarm code: 4096
Severity: Minor
Reason
Alarm description: The configuration data of the database

that the Sntp client gets is illegal.
There are errors in the data configuration.
123
Processing
method
Check the configuration data of the database.
Verification
Precautions
None
T Network Connection Not Conform

to Configuration
Alarm
Information
Alarm code: 5120
Severity: Minor
Alarm description: The fibers are incorrectly connected.
Reason
T network fiber connection does not conform to the optical

interface connection relation configured on the background.
Processing
method
1. Check the connection relation configured for the board and

the fiber connection on the rack in the configuration
management, making sure the fiber is connected in position.
Then check whether the fiber connection conforms to the
configured connection relation.
Y-> Goto Step 2.
N-> Modify the fiber connection or the connection
configuration to keep them consistent. End the alarm
handling.
Verification
Precautions
None
GE Routing Exceptional
Alarm
Information
Reason
Alarm code: 5121
Severity: Minor
Alarm description: Exception in the GE routing.
1. The fiber connection between the UIM and the UIM/GLI is

incorrect, or no fiber is inserted.
2. The UIM background configuration is inconsistent with the
foreground physical configuration.
3. There are exceptions in receiving/sending the detection
packets on the UIM link.
124
Processing
method
1. The BUSN-BUSN double-shelf interconnection or BUSN-BPSN

multi-shelf cascade connection can be configured for the UIM.
Then check whether the background configuration is
consistent with the foreground physical connection.
N-> Adjust the connection according to the configuration
requirements, and the alarm will disappear.
Y-> Goto Step 2.
2. If the configuration is consistent with the actual connection,
but the alarm still exists, check the fiber connection to see if
there is cross interconnection.
N-> Change the fiber physical connection.
Verification
Precautions
None
DB Config Doesn't Fit for Device

Alarm
Information
Alarm code: 5123
Severity: Minor
Alarm description: The database configuration does not

conform to the hardware equipment.
Reason
The equipment type configured in the database is not consistent

with the board hardware.
Processing
method
1. Check the background configuration according to the

additional information of the alarm to see if the configuration
conforms to the board hardware.
Y-> Goto step 2.
N-> Modify the configuration according to the board
hardware and re-power on the board. The alarm will
disappear.
2. If the database configuration is consistent with the board
hardware, but the alarm still exists, Contact ZTE Corporation.
Verification
Precautions
None
Alarm Due to Inconsistent Office No.

Alarm
Information
Alarm code: 5383
125
Reason
Processing
method
Severity: Major
Alarm description: Alarm due to the office No. inconsistent.
The office No. exported from the OMP database is inconsistent

with that previously saved on the OMP.
Restart the active and the standby OMP boards at the same time,
Y-> End.
Verification
Precautions
None
Alarm Due to Inconsistent Area

Code
Alarm
Information
Reason
Processing
method
Alarm code: 5384
Severity: Major
Alarm description: Alarm due to the area code inconsistent.
The area code exported from the OMP database is inconsistent

Y-> End.
Verification
Precautions
None
Alarm Due to Inconsistent MAC

Address of Background OMP (OMC)
Alarm
Information
Alarm code: 5385
Severity: Major
Reason
126
Alarm description: The OMP gives the alarm because the mac
address of the background OMP is inconsistent.
The OMC Mac address read from the OMP database

inconsistent with that previously saved on the OMP.
is
Processing
method
Y-> End.
Verification
Precautions
None
Alarm Due to Inconsistent IP

Address of Background OMP (OMC)
Alarm
Information
Alarm code: 5386
Severity: Major
Reason
Processing
method
Alarm description: The OMP gives the alarm because the IP

address of the background OMP is inconsistent.
The OMC IP address read from the OMP database is inconsistent

Y-> End.
Verification
Precautions
None
Alarm Due to Inconsistent MP Type

Alarm
Information
Alarm code: 5387
Severity: Major
Reason
Processing
method
Alarm description: The OMP gives the alarm because the MP

type is inconsistent.
The module type read from the MP database is inconsistent with

that previously saved on the MP.
1. Check whether the MP is OMP.
Y-> Goto Step 2.
N-> Restart the board, and then check whether the alarm
disappears. Y-> end. N-> Contact ZTE Corporation.
127
2. Set the start mode to foreground start, or modify the startup

file configuration on the background to make it consistent
with the database configuration.
Restart the active and the standby OMP boards at the same
time, and then check whether the alarm disappears.
Y-> End.
Verification
Precautions
None
Start File Does Not Exist

Alarm
Information
Alarm code: 5388
Severity: Major
Reason
Processing
method
Alarm description: The Bootcfg.ini startup file does not

exist.
The Bootcfg.ini startup file does not exist.

Y-> End.
Verification
Precautions
None
A (CPU) Subcard Is Online, but Is

not Configurated by Database.
Alarm
Information
Alarm code: 5389
Severity: Warning
Reason
Processing
method
Alarm description: The (CPU) sub-card is physically in

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

configured in the database.
1. Confirm if it is required to use this sub-card.
Y- Configure the related CPU in the database, and goto Step
2.
N-> Pull out this CPU sub-card and then goto Step 2.
128
2. Check whether the alarm disappears.

Y-> End.
Verification
Precautions
None
A (CPU) Subcard Is not Online, but

Has Been Configured by Database.
Alarm
Information
Alarm code: 5390
Severity: Major
Reason
Processing
method
Alarm description: The (CPU) sub-card is not physically in

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

configured in the database.
1. Check whether this sub-card is inserted in position.
Y-> Pull out the board and insert the sub-card in position.
Then power on the board again and goto step 3.
N-> Goto Step 2.
2. Confirm if it is required to use this sub-card.
Y-> Insert this CPU sub-card and then goto Step 3.
N-> Delete the related configuration in the database, and
goto Step 3.
Y-> End.
Verification
Precautions
None
OMP GateWay IP Different from DBs

Alarm
Information
Alarm code: 5391
Severity: Major
Alarm description: The IP address of the gateway of the OMP

in the BootCfg.ini file is inconsistent with that configured in
the database.
129
Reason
The IP address of the gateway read from the OMP database is

Processing
method
Restart the active and the standby OMP boards at the same time
Y-> End.
Verification
Precautions
None
OMC Server IP Different from DBs

Alarm
Information
Alarm code: 5392
Severity: Major
Alarm description: The IP address of the OMC Server in the

BootCfg.ini file is inconsistent with that configured in the
database.
Reason
The IP address of the OMC Server read from the OMP database
is inconsistent with that previously saved on the OMP.
Processing
method
Y-> End.
Verification
Precautions
None
OMC Gateway Mask Different from

DBs
Alarm
Information
Alarm code: 5393
Severity: Major
130
Alarm description: The mask of the gateway in the

BootCfg.ini file is inconsistent with that configured in the
database.
Reason
The mask of the OMC gateway read from the OMP database is
Processing
method
Y-> End.
Verification
Precautions
None
OMP Config Changes

Alarm
Information
Reason
Processing
method
Alarm code: 5394
Severity: Critical
Alarm description: The OMP configuration was changed.
The key configuration data of the OMP is changed.

Y-> End.
Verification
Precautions
None
Far End Is in Starting-up State

Alarm
Information
Alarm code: 19200
Severity: Major
Alarm description: The remote IMA group connected with the

local IMA group is in the startup status.
Reason
The alarm occurs when the local IMA group receives the report
of the remote IMA group status machine being in the startup
status.
Processing
method
Check whether the UIM/DTB connection, the clock and the trunk
cable connection are correct, and confirm that the IMA
equipment at the opposite end runs normally.
Verification
Precautions
None
131
FE Reports Unacceptable
Configuration Parameters (M size)
Alarm
Information
Alarm code: 19201
Severity: Major
Alarm description: The remote IMA group enters into the

status of configuration failure because the local end refuses
to participate in the negotiable parameter (frame length)
configuration.
Reason
of the remote IMA group being in the configuration failure
status. The reason why the remote IMA group enters into this
status is because the local end refuses to configure the frame
length.
Processing
method
Check whether the frame length configurations at both the local

group and the remote group are consistent.
Verification
Precautions
None
Far End Reports Unacceptable

Configuration Parameters
(Unadaptable Symmetry)
Alarm
Information
Alarm code: 19202
Severity: Major
132

to participate in the negotiable parameter (symmetry of
configuration and operation) configuration.
Reason
status is because the local end refuses to configure the
symmetry-related parameters.
Processing
method
Check whether the group symmetry-related parameters at the

remote group are correctly configured.
Verification
Precautions
None
Far End Reports Unacceptable

Configuration Parameters
(Unadaptable IMA version)
Alarm
Information
Alarm code: 19203
Severity: Major

to participate in the negotiable parameter (IMA protocol
version number) configuration.
Reason
status is because the local end refuses to configure the IMA
protocol version number.
Processing
method
Check whether the protocol version parameters at both the local

group and the remote group are correctly configured.
Verification
Precautions
None
Far End reports Unacceptable

Configuration Parameters (Other
reasons)
Alarm
Information
Alarm code: 19204
Severity: Major

to participate in the negotiable parameter configuration
(other reasons).
Reason
status is because the local end refuses to participate in the
negotiable parameter configuration.
Processing
method
Check whether the parameters at both the local group and the
remote group are correctly configured.
Verification
133
Precautions
None
FE Is in Blocked State
Alarm
Information
Alarm code: 19205
Severity: Major
Reason
Processing
method

local IMA group is in the blocking status.
of the remote IMA group status machine being in the blocking
status.
Check the status of the remote IMA group.
Verification
Precautions
None
FE Is in Insufficient Links State

Alarm
Information
Alarm code: 19206
Severity: Major

local IMA group is in the status of having insufficient links.
Reason
of the remote IMA group status machine being in the status of
having insufficient links.
Processing
method
Check the statuses of the links in the remote IMA group to

confirm that the number of active links is greater than or equal
to the configured minimum number of activated links.
Verification
Precautions
None
Near-End IMA Group Configuration

Failure
Alarm
Information
134
Alarm code: 19207
Severity: Major
Alarm description: The local IMA group goes into the status
of configuration failure because the remote IMA group
refuses to participate in the negotiable parameter
configuration.
Reason
Since the group parameters configured in the local IMA group do

not match those configured in the remote IMA group, and the
IMA configuration parameters sent from the remote end through
ICP cells are rejected, the local IMA group goes into
Config_Aborted status.
Processing
method
Check whether IMA group parameters configured on both local

end and remote end are correct and match each other.
N-> Modify IMA group parameters, and check whether the alarm
disappears. Y-> End. No-> Contact ZTE Corporation.
Verification
Precautions
None
No Response to Requesting
Database for Secondary Forwarding
Table Information
Alarm
Information
Alarm code: 19968
Severity: Major
Reason
Alarm description: There is no response to getting the

information of the level-2 forwarding table from the database.
1. The OMP is not powered on normally.

2. Control plane messages are delayed.
Processing
method
1. Restart the OMP board to see if it works normally.

Y-> Goto Step 2.
N-> Goto Step 4.
2. Restart the UIM board to see if it works normally.
Y-> Goto Step 3.
N-> Goto Step 4.
Y-> Goto Step 5.
N-> Goto Step 4.
4. Record the detailed information and contact ZTE Corporation.
135

Verification
Precautions
None
No Response to Requesting the

System for Secondary Forwarding
Table Port Information
Alarm
Information
Alarm code: 19969
Severity: Major
Reason
Alarm description: There is no response to getting the port

information of the level-2 forwarding table from the system.
1. The system control process on the UIM board is not powered

on normally.
2. The number of IP addresses configured for sub-units in one
shelf is more than 200 (that is the maximum).
Processing
method
1. Restart the UIM board to see if it works normally.

Y-> Goto Step 2.
N-> Goto Step 4.
2. Log in the oam background and enter the protocol mode to
view the IP configuration of the port by using the show ip
interface brief command. Check whether the number of of
IP addresses configured for sub-units in one shelf is more
than 200.
Y-> Goto Step 3.
N-> Goto Step 4.
3. Delete some IP addresses to make the number less than 200.
Check whether the alarm disappears.
Y-> Goto Step 4.
N-> Goto Step 5.
4. Record the detailed information and contact ZTE Corporation.
136
Verification
Precautions
None
SCCP SSN Is Invalid

Alarm
Information
Reason
Alarm code: 8398848
Severity: Minor
Alarm description: The SCCP subsystem is unavailable.
1. The remote signaling point sub-system exits services.

2. The remote signaling point is inaccessible.
3. The remote office deletes a SSN.
4. The SSN is not configured in the remote office, but the SSN
of the remote office is configured at the local end, causing
SST test failure at the local end.
Processing
method

Y-> End.
N-> Goto Step 2.
Y-> Goto Step 3.
N-> Goto Step 4.
Goto Step 4.
i.


Verification
Precautions
None
137
Port Work Mode Doesn't Match

Settings
Alarm
information
Alarm code: 5649
System type: NE Alarm
Severity: Major
Alarm description: The port work mode does not match the
settings.
Reason
Setting work mode for this external port fails because of

performance or peer end factors.
Processing
method
1. Check whether the work mode on the peer end is correctly

set, which should match the work mode set on the local end.
Y-> Goto Step 2.
N-> Modify the work mode setting on the peer end to make
it consistent with that on the local end, and then check
whether the alarm disappears. Y-> End. N-> Goto Step 2.
2. Check whether the work mode on the local end is correctly
set.
N-> Modify the work mode setting on the local end, and then
check if the alarm is eliminated. Y-> End. N-> Contact ZTE
Corporation.
Verification
Precautions
None
Number of Management Module

Alarms Exceeds the Threshold
Alarm
information
Alarm code: 8411649
Severity: Major
Reason
Processing
method
Alarm description: The number of management module

alarms exceeds the threshold.
The foreground alarm pool is full of alarm information.

1. Check whether there is any virtually configured resource
temporarily not in use.
Y-> Delete the virtually configured resources. Go to Step
Y-> End
138

Verification
Precautions
None
Number of Alarms over Threshold

Alarm
information
Alarm code: 23040
Severity: Major
Reason
Processing
method
Alarm description: The number of board alarms exceeds the

threshold.
The foreground alarm pool is full of alarm information.

1. Check whether there is any virtually configured resource
temporarily not in use.
Y-> Delete the virtually configured resources. Go to Step
Y-> End
Verification
Precautions
None
NTP Time Exceeds Threshold

Alarm
information
Alarm code: 8392706
Severity: Minor
Alarm description: The NTP time exceeds the threshold.
Reason
Having a big difference with the local time, the NTP time
Processing
method
1. Check whether the interval between the alarm time and the
current environmental time exceeds 8 alarm periods.
Y-> Goto Step 3.
N-> Check whether the configured synchronization period is
too long. Y-> Adjust the synchronization period, wait for 8
alarm periods, and then goto Step 2.
2. Check whether the overload alarm disappears.
Y-> End.
N-> Go to Step 1.
139
3. Check whether this is any NTP server failure alarm.

Y-> Eliminate this alarm and goto Step 4.
N-> Goto Step 4.
4. Check whether the link between the OMP and the RPU is
broken.
Y-> Restore the link and goto Step 1.
N-> Goto Step 5.
5. Check whether the alarm threshold is too low.
Y-> Increase the threshold or change it to 0 if it is too small
(non-0 and generally smaller than 100), and then goto Step
1.
N-> Goto Step 6, if the threshold is larger than 100.
6. Initiate manually time synchronization from the background
and check whether this alarm disappears.
Y-> End.
N-> Note down the alarm information and contact ZTE
Corporation.
Verification
Precautions
None
Routers with Conflicting System Id

Exist in Network
Alarm
information
Alarm code: 22598
Severity: Minor
Alarm description: Routers with conflicting system ID exist in

the network.
Reason
Under the protocol stack configuration mode, there are errors in

the system ID configuration in the ISIS instance configuraiton.
Processing
method
1. Check the system IF configuration in the ISIS instance on

the router by command show running config to see
whether there is any conflict.
Y-> Modify the system ID configuration in the instance.
Contact ZTE Corporation if the alarm still exists.
140
Verification
Precautions
None
Chapter
Notification Message
Handling
Overview
Introduction
Contents
This chapter introduces the notification information that may

appear in the ZXWN MGW system and the related solutions.
This chapter includes the following sections.
Sections
Page No.
Summary of Notification Messages
141
Notification Information
151
Summary of Notification
Messages
Notification messages refer to some normal events (or abnormal
events) during system running, such as module power-on,
active/standby changeover, and successful startup of the
database. As ordinary prompts or alerts, notification messages
do not need restoration.
Notification messages are not classified into levels.
Table 5 shows the summary of the notification messages.
141
TABLE 5 SUMM ARY OF NOTIFICATION MESSAGES
142
System Type
Alarm
Code
Alarm Description
Processing
Required
MP NE Equipment
Alarm
576
Trunk Slide
Yes
MP NE Equipment
Alarm
1600
One of CPUs on One

of Boards in This
Shelf Resets
Exceptionally
No
MP NE Equipment
Alarm
1856
APS CHANGE
No
MP NE Equipment
Alarm
2880
CPU Dead-loop
Yes
MP NE Equipment
Alarm
3136
Disk Is Full
Yes
MP NE Equipment
Alarm
3137
File Operation Failure
No
MP NE Equipment
Alarm
3392
Shortage of Timer
Resources
No
MP NE Equipment
Alarm
3648
UB Resource Shortage
No
MP NE Equipment
Alarm
3649
Swap Resource
Shortage
No
MP NE Equipment
Alarm
3904
Full Communication
Buffer Queue
No
MP NE Equipment
Alarm
3905
Transfer Functions of
Message Byte Order
Registered Repeatedly
Yes
MP NE Equipment
Alarm
5184
Base Process Power

on Failed
Yes
MP NE Equipment
Alarm
5185
Base Process Power

on Time out
Yes
MP NE Equipment
Alarm
5188
UIM CS Changeover
MP NE Equipment
Alarm
5189
Notification of
Active/Standby
Changeover
Yes
MP NE Equipment
Alarm
5192
Board's Workmode
Unsupported
Yes
MP NE Equipment
Alarm
5193
Notification of the
Power-on Status of
the Basic Process
Yes
MP NE Equipment
Alarm
5441
Port Status on GLI

Media Plane Is
Changed
No
MP NE Equipment
Alarm
5448
485 Set Failur
Yes
Yes
Chapter 2 Notification Message Handling
System Type
Alarm
Code
Alarm Description
Processing
Required
MP NE Equipment
Alarm
5700
Exceptional DSP
Reset
Yes
MP NE Equipment
Alarm
5701
Load error
Yes
MP NE Equipment
Alarm
5702
Trunk Configuration
Is Inconsistent with
Function of Boar
Yes
MP NE Equipment
Alarm
5703
Backboard Switch Set

Change.
Yes
MP NE Equipment
Alarm
5704
Work Mode of
Network Interface
Change
No
MP NE Equipment
Alarm
5709
Inconsistent CPU
Version with DSP
Version
Yes
MP NE Equipment
Alarm
5956
Board Version Error
Yes
MP NE Equipment
Alarm
5957
Doc Space Is not

enough to Save
VerFile
Yes
MP NE Equipment
Alarm
5958
IDE Files
Synchronization
Information
No
MP NE Equipment
Alarm
5959
Version Switch
Information
No
MP NE Equipment
Alarm
6720
Notice of Power-on
Status of C51 Board/
Board Soft Reset
No
MP NE Equipment
Alarm
8000
Dbs Table Load

Failure
Yes
MP NE Equipment
Alarm
8001
Master to Slave Sync

Failure
Yes
MP NE Equipment
Alarm
8002
OMP to MP Sync
Failure
Yes
MP NE Equipment
Alarm
8003
MP Data Distribution
Failure
Yes
MP NE Equipment
Alarm
8004
Failure of Saving One

Table
Yes
MP NE Equipment
Alarm
8005
Dbs File Buffer

Overflow
Yes
MP NE Equipment
Alarm
8006
Notification of
Modifying Data
Configuration Failed
Yes
MP NE Equipment
Alarm
8007
Save File Failed in

Master or Slave Path
Yes
143
144
System Type
Alarm
Code
Alarm Description
Processing
Required
MP NE Equipment
Alarm
8008
OMP Fails to Perform

Power-on Loading of
Version Table
Yes
MP NE Equipment
Alarm
8009
DBS Require
Yes
MP NE Equipment
Alarm
10304
SCCP GT Translation
Failure
Yes
MP NE Equipment
Alarm
10305
NID Is Not Configured
Yes
MP NE Equipment
Alarm
10306
NID Translation
Failure
No
MP NE Equipment
Alarm
10307
ISNI Constrained
Route Information
Repeat
Yes
MP NE Equipment
Alarm
10308
ISNI Unable to
Support the Route
Function
Yes
MP NE Equipment
Alarm
10309
NID Route Prompt

Failure
Yes
MP NE Equipment
Alarm
10310
Wrong Message Type

Use ISNI Function
Yes
MP NE Equipment
Alarm
10560
No Message Response
in the Link for a Long
Time
Yes
MP NE Equipment
Alarm
10822
Successful MGW
Registration
No
MP NE Equipment
Alarm
10823
MGW Registration
Failure
Yes
MP NE Equipment
Alarm
11328
Failed to Config Multichannel Controller
Yes
MP NE Equipment
Alarm
11329
Failed to Config
Digital Switch Chip
Yes
MP NE Equipment
Alarm
11330
Failure in Getting
Config Information
from Database
Yes
MP NE Equipment
Alarm
12608
SUA GT Translation
Failure
Yes
MP NE Equipment
Alarm
13632
M2PA Link Congested
No
MP NE Equipment
Alarm
13633
M2PA Processor
Outage
No
MP NE Equipment
Alarm
13888
ASP Status Changed
No
MP NE Equipment
Alarm
13889
AS Status Changed
No
System Type
Alarm
Code
Alarm Description
Processing
Required
MP NE Equipment
Alarm
13890
Receiving SIGTRAN
Error Message
Yes
MP NE Equipment
Alarm
13891
Receiving SIGTRAN
Notification Message
No
MP NE Equipment
Alarm
14144
Association
Establishment Failure
Yes
MP NE Equipment
Alarm
15424
Microcode Is
Abnormal
Yes
MP NE Equipment
Alarm
15936
Faulty 2400
Configuration Data
Yes
MP NE Equipment
Alarm
16192
Faulty 1200
Configuration Data
Yes
MP NE Equipment
Alarm
16193
SIG_IPI Forwards
Service Messages
Abnormally
Yes
MP NE Equipment
Alarm
16704
Faulty 2350
Configuration Data
Yes
MP NE Equipment
Alarm
17984
IP Fail to Get Route

Table Head or Entry
Yes
MP NE Equipment
Alarm
17985
IP Opr Static Rte Fail:

Del Srte
Yes
MP NE Equipment
Alarm
17986
IP Has no Match Epu

Globalport
Yes
MP NE Equipment
Alarm
17987
IP Create or Enable
Ifb Fail
Yes
MP NE Equipment
Alarm
17988
IP Rcv Epu Inform

Intf Up
No
MP NE Equipment
Alarm
17989
IP Rcv Eepu Inform

Intf Down
Yes
MP NE Equipment
Alarm
17990
SCS Informs RPU that

EPU Is down
Yes
MP NE Equipment
Alarm
17991
SCS Informs RPU that

EPU Is Removed.
Yes
MP NE Equipment
Alarm
17992
IP Opr Static Rte Fail:

Add Srte.
Yes
MP NE Equipment
Alarm
18240
TCP Received RST

Packet
Yes
MP NE Equipment
Alarm
18241
TCP Connection
Aborted
Yes
MP NE Equipment
Alarm
19008
Port Configuration
Failure
Yes
MP NE Equipment
Alarm
19009
Failure in Creating
PVC
Yes
145
System Type
Alarm
Code
Alarm Description
Processing
Required
MP NE Equipment
Alarm
19010
Failure in Deleting
PVC
Yes
MP NE Equipment
Alarm
19264
IMA Group Related

Operations Failure
Yes
MP NE Equipment
Alarm
19265
IMA Link Operations

Failure
Yes
MP NE Equipment
Alarm
19520
Some of High-Speed
Serial Links out of
Synchronism
Yes
Yes
19521
Number of SFrame
with Erroneous Frame
Format Exceeds
Threshold
Yes
19522
Number of CFrames
Discarded at the CSIX
Port N due to
Horizontal Check
Error Exceeds
Threshold
Yes
19523
Number of CFrames
Port N due to Vertical
Check Error Exceeds
Threshold
Yes
19524
Number of incomplete
CFrames Discarded at
the CSIX Port N
Exceeds Threshold
Yes
19525
Number of CFrames
Port N Due to Invalid
Frame Type Exceeds
Threshold
Yes
19526
Number of CFrames
Port N due to Invalid
Frame Length
Exceeds Threshold
Yes
19527
Number of Out-ofSequence Frames

Discarded exceeds
the Threshold
19528
Number of Discarded
Frames due to CRC
Check Error Exceeds
Threshold
Yes
MP NE Equipment
Alarm
MP NE Equipment
Alarm
19529
2400 Configuration
Failure
Yes
MP NE Equipment
Alarm
MP NE Equipment
Alarm
MP NE Equipment
Alarm
MP NE Equipment
Alarm
MP NE Equipment
Alarm
MP NE Equipment
Alarm
MP NE Equipment
Alarm
146
System Type
Alarm
Code
Alarm Description
Processing
Required
MP NE Equipment
Alarm
19530
VSC872 Configuration
Failure
MP NE Equipment
Alarm
19776
APS Protection
Change Is Overtime
Yes
MP NE Equipment
Alarm
19777
Aps Switchover
Happens
Yes
MP NE Equipment
Alarm
20032
Level-2 Forwarding
Table Initialization
Failure
Yes
20033
Ethernet Port
Initialization on Media
Plane of UIM Board
Failure
Yes
MP NE Equipment
Alarm
MP NE Equipment
Alarm
20288
Brs Main Config

Request Timeout
Yes
MP NE Equipment
Alarm
20289
Brs Main Epu Register

Timeout
Yes
MP NE Equipment
Alarm
20290
Protocol Stack
Process Fails to Be
Powered on
Yes
MP NE Equipment
Alarm
20544
IP Offline Setting:
Invalid Interface
Yes
MP NE Equipment
Alarm
20545
IP Offline Setting:
Disable This IP Using
No IP Unnumbered
Command Firstly
Yes
MP NE Equipment
Alarm
20546
IP Offline Setting:
Interface Address
Addition Failure
Yes
MP NE Equipment
Alarm
20547
IP Offline Setting:
Failure in Writing to a
Database
Yes
MP NE Equipment
Alarm
20548
IP Offline Setting: IP
Address Deletion
Failure
Yes
MP NE Equipment
Alarm
20549
IP Offline Setting:
Invalid Address
Yes
MP NE Equipment
Alarm
20550
IP Offline Setting:
Invalid Nexthop
Yes
MP NE Equipment
Alarm
20553
IP Offline Setting:
Inconsistent IP
Address and Subnet
Mask
Yes
MP NE Equipment
Alarm
20554
IP Offline Setting:
Route Addition Failure
Yes
MP NE Equipment
Alarm
20555
IP Offline Setting: No
Matched Route
Yes
Yes
147
System Type
Alarm
Code
Alarm Description
Processing
Required
MP NE Equipment
Alarm
20556
IP Offline Setting:
Routing Deletion
Failure
Yes
MP NE Equipment
Alarm
20557
IP Offline Setting:
Next Hop Conflicts
Yes
MP NE Equipment
Alarm
20558
IP Offline Setting:
Next Hop not
Connected Directly
Yes
MP NE Equipment
Alarm
20559
IP Offline Setting:
None-Existent IP
Address
Yes
MP NE Equipment
Alarm
20561
IP Offline Setting:
Failure in Reading
Database
Yes
MP NE Equipment
Alarm
20562
IP Offline Setting: Not

an Ethernet Port
Yes
MP NE Equipment
Alarm
20563
IP Offline Setting:
MAC beyond Valid
Range
Yes
20564
IP Offline Setting:
Incorrect MAC Type
Transferred by
Database
Yes
MP NE Equipment
Alarm
20565
IP Offline Setting: The

Same IP Address in
the Network Section
Has Existed
Yes
MP NE Equipment
Alarm
20566
IP Offline
Configuration: Invalid
IP Broadcast Address
Yes
20567
IP Offline
Configuration: One
Interface Can Only Be
Configured Four IP
Addresses at Most
Yes
MP NE Equipment
Alarm
20568
IP Offline
Configuration:
Parameter Imported
From DB Is Null
Yes
MP NE Equipment
Alarm
20569
IP Offline Setting: IP
Address Has Existed
Yes
MP NE Equipment
Alarm
20570
IP Offline Setting:
Invalid Mask or
Network Prefix
Yes
MP NE Equipment
Alarm
20800
Failure in Allocating
Memory for ARP Table
Instance
Yes
MP NE Equipment
Alarm
MP NE Equipment
Alarm
148
System Type
Alarm
Code
Alarm Description
Processing
Required
MP NE Equipment
Alarm
20801
Failure in Allocating
Memeory for ARP
Table Cache
Yes
MP NE Equipment
Alarm
20802
Conflicting IP
Addresses
Yes
MP NE Equipment
Alarm
20803
Conflicting MAC
Addresses in Subnet
Yes
MP NE Equipment
Alarm
21059
RIP Neighbor
Configuration Errors
Yes
MP NE Equipment
Alarm
21060
RIP Interface
Authentication Errors
Yes
MP NE Equipment
Alarm
21062
RIP Neighbor Age Out
Yes
MP NE Equipment
Alarm
21063
RIP Port Disabled
Yes
MP NE Equipment
Alarm
21064
RIP Port Enabled
No
MP NE Equipment
Alarm
21065
Incompatible RIP
Version Number
Yes
MP NE Equipment
Alarm
21312
Conflicting Router ID
Yes
MP NE Equipment
Alarm
21315
OSPF Virtual Link

State Changed
Yes
MP NE Equipment
Alarm
21316
OSPF Interface State

Changed
Yes
MP NE Equipment
Alarm
21319
Erroneous OSPF
Virtual Interface
Configuration
Yes
MP NE Equipment
Alarm
21320
Erroneous OSPF
Interface
Configuration
Yes
MP NE Equipment
Alarm
21324
OSPF Virtual Interface

Authentication Failure
Yes
MP NE Equipment
Alarm
21325
OSPF Interface
Yes
MP NE Equipment
Alarm
21326
Status of OSPF Virtual

Neighbor Transfers
Yes
MP NE Equipment
Alarm
21327
Status of OSPF
Neighbor Transfers
Yes
MP NE Equipment
Alarm
21329
LSDB Overflow
Yes
MP NE Equipment
Alarm
21568
Failure in Creating
BGP Instance
Yes
MP NE Equipment
Alarm
21570
Failure in Creating
BGP Neighbor
Yes
149
150
System Type
Alarm
Code
Alarm Description
Processing
Required
MP NE Equipment
Alarm
21572
Failure in Getting TCB

when BGP Connection
is Passively Open
Yes
MP NE Equipment
Alarm
21573
Failure in Getting TCB

when BGP Connection
is Actively Started
Yes
MP NE Equipment
Alarm
21575
BGP Fails to Enable

Passive
Yes
MP NE Equipment
Alarm
21576
BGP Fails to Enable

Actively Started TCB
Yes
MP NE Equipment
Alarm
21579
BGP Failed to Add

Neighbor to Group
Yes
MP NE Equipment
Alarm
21582
BGP Neighbor Failed

to Read Receive
Buffer
Yes
MP NE Equipment
Alarm
21584
Neighbor Hold Timer

Expires
Yes
MP NE Equipment
Alarm
21586
BGP Neighbor FSM

Error
Yes
MP NE Equipment
Alarm
21587
BGP State Changed
Yes
MP NE Equipment
Alarm
21607
BGP State Changed.
Yes
MP NE Equipment
Alarm
21825
Courier Create BGP

Fail
Yes
MP NE Equipment
Alarm
21826
Courier Create OSPF

Fail
Yes
MP NE Equipment
Alarm
21831
Courier Enable OSPF

by the RTR_ID Fail
Yes
MP NE Equipment
Alarm
21837
IP Forwarding Table
Fails to Create Routes
Yes
MP NE Equipment
Alarm
22336
Conflicting MAC
Address on Local
Office Port
Yes
MP NE Equipment
Alarm
22592
ISIS Timer Creation

Failure
Yes
MP NE Equipment
Alarm
22593
ISIS Hello Message

Yes
MP NE Equipment
Alarm
22594
ISIS LSP Message

Yes
MP NE Equipment
Alarm
22595
ISIS SNP Message

Yes
MP NE Equipment
Alarm
22596
ISIS Neighbor Status

Change
No
System Type
Alarm
Code
Alarm Description
Processing
Required
MP NE Equipment
Alarm
22597
Abnormal Message is
Received
No
MP NE Equipment
Alarm
22848
BFD Faults
Yes
MP NE Equipment
Alarm
23104
Alarm Pool Is over in

OAM ALARMMANAGER
Process
Yes
MP NE Equipment
Alarm
23105
OAM Frequently
Receives Alarms and
Notifications
No
MP NE Equipment
Alarm
23106
Board Self-Check
Failure
Yes
MP NE Equipment
Alarm
23107
Board Initialization
Failure
Yes
MP NE Equipment
Alarm
25664
Abnormal Half-Fixed
Connection Changes
Yes
MP NE Equipment
Alarm
25665
Erroneous Half-fixed
Connection Data
Configuration
Yes
MP NE Equipment
Alarm
26176
Clock Reference
Changed
No
MP NE Equipment
Alarm
26177
CLKG Reference
Quality Changed
Yes
MP NE Equipment
Alarm
26178
CLKG Work Mode

Changed
Yes
MP NE Equipment
Alarm
26179
Clock Source
Invalidation Reason
Changed
Yes
MP NE Equipment
Alarm
33604738
IUAs ASP State

Changed
Yes
MP NE Equipment
Alarm
33604739
IUAs AS State
Changed
Yes
MP NE Equipment
Alarm
33604740
IUA Receives an ERR

Message
Yes
MP NE Equipment
Alarm
33604741
IUA Receives an NTFY

Message
Yes
Notification Information
This section introduces the notification information that may
appear in the ZXWN MGW system and the related solutions.
151
Trunk Slide
Alarm
information
Reason
Processing
method
Alarm code: 576
Alarm information: E1 trunk slide.
The trunk receiving

transmitting clock.
clock
is
not
synchronous
with
the
There may be frequency difference between the trunk line clock

and the local receiving clock. Contact ZTE Corporation.
One of CPUs on One of Boards in

This Shelf Resets Exceptionally
Alarm
information
Reason
Processing
method
Alarm code: 1600

Alarm description: One CPU of a board in the shelf is
(exceptionally) reset.
A CPU of a board in the shelf is (exceptionally) reset. The cause

can be found out through viewing the error log of the OMP.
None
APS CHANGE
Alarm
information
Reason
Processing
method
Alarm code: 1856

Alarm description: SDH: Automatic protection switchover
event.
The APS switchover event occurs.

1. If it is because of manual restart of the board or manually
pulling out the board, report this alarm routinely. If it is not,
goto Step 2.
CPU Dead-loop
Alarm
information
Reason
Processing
method
152
Alarm code: 2880
Alarm description: Endless loop in the CPU.
There is an endless loop in the process or the system task.

The board will restart automatically when this alarm occurs. The
alarm will automatically disappear after the board restarts.
Disk Is Full
Alarm
information
Reason
Alarm code: 3136
Alarm description: The disk is full.
1. This notification may occur on the OMP board or the billingrelated board.
2. There may be too many useless versions on the OMP board.
3. On the billing-related board, usually a large amount of billing
information is saved on the disk due to overtime interruption
of the communication link between the foreground and the
background.
Processing
method
1. Check whether the board where this notification occurs is an

OMP board.
Y-> Delete useless version files on this OMP board.
N-> Goto Step 2
2. Check whether the board where this notification occurs is a
billing-related board.
Y-> Usually a large amount of billing information is saved on
the foreground disk due to failure in communication between
the billing board and the billing background. Check whether
the communication between the billing board and the billing
background, and the billing server are normal. Y-> Goto Step
3. N-> Make sure that the communication between the
billing board and the billing background, and the billing
server are normal.
N-> Goto Step 3
3. Record the alarm information and Contact ZTE Corporation.
File Operation Failure

Alarm
information
Reason
Processing
method
Alarm code: 3137
Alarm description: File operation failure
The disk is damaged.
The disk is full
The out-of-date file descriptors are operated.
153
Shortage of Timer Resources

Alarm
information
Reason
Processing
method
Alarm code: 3392

Alarm description: The resources of the timer control block
are insufficient.
The configured timers are insufficient.

UB Resource Shortage
Alarm
information
Reason
Alarm code: 3648
Alarm description: No available memory block.
The configured UB is insufficient.
Processing
method
The messages are not processed in time, which causes that

the UB is occupied for a long time and cannot be released in
time.
Full Communication Buffer Queue

Alarm
information
Reason
Processing
method
Alarm code: 3904
Alarm description: The communication buffer queue is full.
There are too many messages sent in an instant.

Transfer Functions of Message Byte

Order Registered Repeatedly
Alarm
information
Reason
Processing
method
154
Alarm code: 3905

Alarm description: The message byte sequence transfer
function is repeatedly registered.
The byte sequence transfer function of the same message is

repeatedly registered.
Base Process Power on Failed

Alarm
information
Reason
Processing
method
Alarm code: 5184
Alarm description: The basic process failed to be powered on.
The basic process failed to be powered on.

Check the failure reason and power on the board again.
Base Process Power on Time out

Alarm
information
Reason
Processing
method
Alarm code: 5185

Alarm description: The power-on of the basic process times
out.
The power-on of the basic process times out.

Check the timeout reason and power on the board again.
UIM CS Changeover
Alarm
information
Alarm code: 5188
Alarm description: The big T net of the UIM switches over.
Reason
There are hardware system faults. The CS-domain switchover of

the UIM occurs due to manual operations.
Processing
method
1. Check whether the CS optical interface changeover is

initiated on the background through manual operations.
Y-> This alarm is a normal phenomenon, so there is no need
to handle it.
N-> Goto Step 2.
2. Replace the previously active UIM board, and then check
Y-> End.
N-> Goto Step 3.
3. Switch over the active TSNB board, and then check whether
the fault is eliminated.
Y-> End.
N-> Goto Step 4.
155
Notification of Active/Standby
Changeover
Alarm
information
Reason
Processing
method
Alarm code: 5189
Alarm description: Active/standby switchover.
It is a hardware system fault. Manual operation

switchover between the active and standby boards.
cause
1. Analyze the reason why switchover between the active and

standby boards occurs according to the additional
information in the alarm to see if the alarm is caused by
system faults.
Y-> Goto Step 2.
N-> If it is not because of system faults but due to control of
MML commands at the background, non-active/standby
changeover, or inexistence of the standby board. In this case,
do nothing for this alarm.
2. Check the active and standby boards to see if there are other
hardware alarms.
Y-> Eliminate these alarms firstly and then check whether
the alarm disappears. If it still exists, Contact ZTE
Corporation.
FE Link Error Alarm

Alarm
information
Alarm code: 5127
Alarm description: The FE routing is exceptional.
Reason
There are one pair of FE routing ports. One is normal, while the
other is abnormal.
Processing
method
1. Check whether only one cable of the port pair of the

corresponding rear board is connected to the peer-end FE
port.
Y-> Connect the other cable of the port pair to the peer-end
FE port to ensure that this pair of ports can be connected to
the peer-end FE port. Then check whether the alarm
disappears. If it still exists, Contact ZTE Corporation.
N-> Goto Step 2.
2. Check whether one cable of this pair of ports is connected to
the normal FE port of the peer end, while the other cable is
connected to the debugging machine or Sig_Ipi.
Y-> Pull out the FE routing cable, and then check whether
156
Or pull out the cable connected to the debugging machine or

Sig_Ipi, and connect it to the normal FE routing port. Then
check whether the alarm disappears. Y-> End. N-> Contact
ZTE Corporation.
Board's Workmode Unsupported

Alarm
information
Reason
Alarm code: 5192

Alarm description: The board does not support the working
mode.
1. The working mode that the board does not support is

configured on the background.
2. Such reasons as FPGA not loading cause that there are errors
in setting the working mode for the board.
Processing
method
1. Check the background configuration to see if the board

supports the work mode configured on the background.
Y-> Goto Step 2.
N-> Configure a work mode supported by the board, or
replace the board with the one that can meet the
requirements.
2. If there is no problem in the background configuration of the
board, maybe the FPGA loading causes the alarm. Try to
replace the board and then check whether the alarm
disappears.
Y-> End.
Notification of the Power-on Status

of the Basic Process
Alarm
information
Reason
Alarm code: 5193

Alarm description: Notification of the power-on status of the
basic process.
1. All the basic processes are successfully powered on.

2. One specific process fails to be powered on.
Processing
method
1. Check the additional information in the alarm to see if it is

reported that the board is powered on successfully.
Y-> It is normal that the alarm occurs, so there is no need to
handle it.
N-> Goto Step 2.
157
2. Contact ZTE Corporation if the power-on of the board fails or

times out.
Port Status on GLI Media Plane Is

Changed
Alarm
information
Reason
Processing
method
Alarm code: 5441

Alarm description: The port status on the GLI media plane is
changed.
The status of the GLI optical port is changed.

1. Check the port status in the additional information. If the
status is normal, the alarm is a normal phenomenon, so
there is no need to handle it.
2. If the port status is abnormal, check whether there is optical
signal in the corresponding optical port, and check physical
connections of the fiber.
485 Set Failure

Alarm
information
Reason
Processing
method
Alarm code: 5448
Alarm description: Failure in setting 485 offline.
The 485 communication

exceptional.
is
interrupted
or
the
board
is
1. Check whether the 485 connection line is normal.

Y-> Goto Step 2
N-> Correctly connect the 485 connection line.
2. There are hardware faults. Replace the board, and check
whether this notification disappears.
Y-> End.
Exceptional DSP Reset

Alarm
information
Reason
158
Alarm code: 5700

Alarm description: The DSP halts when running normally, the
dsp program runs away, and the handshaking fails.
The DSP halts when running normally, the dsp program runs
away, and the handshaking fails.
Processing
method
1. Reset the halted DSP, and check whether this alarm

disappears.
Y-> End.
N-> Goto Step 2.
2. Replace the board if allowed, and check whether this alarm
disappears.
Y-> End.
Load error
Alarm
information
Reason
Processing
method
Alarm code: 5701
Alarm description: The version failed to be loaded.
The version does not exist.
Errors occur during loading the version.
Errors occur in getting the version data.
1. Use the version management tool to check whether the

version of firmware/DSP required for the board is correctly
configured and already exists.
Y-> Goto Step 2.
N->Re-configure a version of firmware /DSP for the board on
the background, and synchronize the data to the foreground.
Observe if the alarm disappears. Y-> End. N-> Contact ZTE
Corporation.
2. Reset the board and then observe if the alarm disappears.
Y-> End.
Trunk Configuration Is Inconsistent

with Function of Board
Alarm
information
Reason
Processing
method
Alarm code: 5702

Alarm description: The trunk configuration is inconsistent
with the function of the board.
The board does not support the trunk configuration in the

database.
1. Check whether the board configuration is correct.
Y-> Goto Step 2
159
N-> Modify the board configuration and then restart the

board. Check whether the alarm appears. Y-> goto Step 2.
N-> End.
2. Replace the board with one that matches the configuration,
and check whether this alarm still appears.
Y-> End.
Backboard Switch Set Change.

Alarm
information
Reason
Processing
method
Alarm code: 5703

Alarm description: The setting of the DIP switch on the
backboard has been changed.
The setting of the DIP switch on the backplane is changed.

1. Plug the uim/UIM_2/GUIM board tightly to the slot again and
then observe if the alarm notification appears.
Y-> Goto Step 2
Y-> End.
2. Replace the backplane of the shelf, and check whether this
alarm appears.
N-> End.
Work Mode of Network Interface

Changed
Alarm
information
Reason
Processing
method
Alarm code: 5704

Alarm description: The working mode of the network
interface has been changed.
The working mode of the network interface is changed due to

problems at the local end or the opposite end.
Board Version Error

Alarm
information
160
Alarm code: 5956

Alarm description: An error occurs when the periphery board
requests for the version information or download/load the
version software.
Reason
Refer to additional information of the notification for locating the

fault that the version can not be got.
Processing
method
Check the actual attributes of the board and configure the

correct version for it. Then re-load the board version, and see if
the fault is eliminated.
Y-> End.
Doc Space Is not enough to Save

VerFile
Alarm
information
Alarm code: 5957

Alarm description: The DOC space on the OMP is insufficient,
and the version file cannot be downloaded to the DOC.
Reason
The DOC space on the OMP is insufficient, and the version file
cannot be downloaded to the DOC.
Processing
method
Clear up the DOC space on the OMP, deleting the trash files and
useless old version files, and restart the board.
IDE Files Synchronization

Information
Alarm
information
Reason
Alarm code: 5958
Alarm description: IDE version synchronization information.
The standby OMP board is not in the position, and the

synchronization cannot be performed.
The version synchronization is finished.
1. The version synchronization is finished.

2. The standby OMP board is not in the position and the
synchronization cannot be performed.
3. The file synchronization fails.
4. Database records fail to be got.
Processing
method
Check whether there are the corresponding files on the hard

disks of the active and standby boards if version synchronization
fails.
N-> Add the required version file. After the version runs
normally, the alarm disappears.
Y-> Ask the engineers from the R&D department to troubleshoot
this problem.
161
Take different measures according to the error code type in the

additional information.
Version synchronization end: it means the synchronization is

completed normally, and there is no need to handle it.
The standby OMP board is not in the position and the
synchronization cannot be performed: It is required to add
this version manually after the standby board is powered on
normally.
The file synchronization fails: It is required to add this
version manually.
Database
records
Corporation.
acquisition
failure:
Contact
ZTE
Dbs Table Load Failure after Date of

Foreground and Background Are
Synchronized
Alarm
information
Reason
Processing
method
Alarm code: 8000

Alarm description: After the data of the foreground and the
background are synchronized, the MP loads data, and a
datasheet fails to be loaded.
The data configuration on the background is incorrect, so the

datasheet of the foreground fails to be loaded.
Master to Slave Sync Failure

Alarm
information
Reason
Processing
method
Alarm code: 8001

Alarm description: The master datasheet and the slave one
fail to be synchronized.
There are many reasons for failure in synchronizing the master

datasheet with the slave one, which can be described according
to the returned error ID to the background. The meaning and
the value of err rids are explained in the description of ucErrold
(not including 7).
OMP to MP Sync Failure

Alarm
information
162
Alarm code: 8002
Reason
Processing
method
Alarm description: The data synchronization from the OMP to

the MP failed.
There are many reasons for failure in synchronizing data from

the MP to the OMP while the MP is powered on, which can be
described according to the returned errorID to the background.
The meaning and the value of errorIDs are explained in the
description of ucErrold (not including 7).
MP Data Distribution Failure

Alarm
information
Reason
Processing
method
Alarm code: 8003

Alarm description: The data synchronization from the MP to
the PP failed.
The reasons for failure in synchronizing data from the OMP to

the MP, or the MP to the PP can be described according to the
returned errorID to the background. The meaning and the value
of errorIDs are explained in the description of ucErrold (not
including 7).
Failure of Saving One Table

Alarm
information
Reason
Processing
method
Alarm code: 8004
Alarm description: A single data table failed to be saved.
When the table structure is inconsistent with that in zdb, or the

zdb file structure is incomplete, a single data table fails to be
saved.
Dbs File Buffer Overflow

Alarm
information
Reason
Processing
method
Alarm code: 8005

Alarm description: The capacity of the memory file buffer is
insufficient, and the subsequent transferred records are
discarded.
The transferred data records exceed the maximum capacity of

the table, and the capacity of the foreground memory file buffer
is insufficient.
163
Notification of Modifying Data

Alarm
information
Reason
Processing
method
Alarm code: 8006
Alarm description: Data configuration modification failure
The 3-times-of notification is adopted for the data configuration

modification (P_notify process). If 3 times of notification all fails,
this notification will occur.
Save File Failed in Master or Slave

Path
Alarm
information
Reason
Processing
method
Alarm code: 8007

Alarm description: The notification occurs when the saving in
one of the active and the standby directories fails. The
additional message contains the path of saving failure.
The disk is full.
The media is faulty.
OMP Fails to Perform Power-on

Loading of Version Table
Alarm
information
Reason
Processing
method
Alarm code: 8008

Alarm description: Compared with ZDB, the board memory
version table has newly-added fields or type-incompatible
fields, which causes failure in loading the version table
records.
When the OMP performs power-on loading of the version table

during running the new version, and if the new version has
newly-added fields or type-incompatible fields, the version table
is not loaded.
DBS Require Configuration Failed

Alarm
information
164
Alarm code: 8009
Reason
Processing
method
Alarm description: The database configuration request is

rejected.
This board is not configured to the upper -level homing module

is not configured with this board, or the link is faulty.
NID Is Not Configured

Alarm
information
Reason
Processing
method
Alarm code: 10305
Alarm description: NID not configured.
When the NID translation is performed, it is not configured in

the database (which frequently happens).
1. Check whether the NID is configured in the background.
Y-> Goto Step 2.
N-> Configure the corresponding NID. After configuration,
check whether the alarm disappears. Y-> End. N-> Goto
Step 2.
i.


NID Translation Failure

Alarm
information
Reason
Alarm code: 10306
Alarm description: NID translation failure.
Processing
method
The database failed to translate the NID (which frequently

happens).
The database is exceptional, which seldom happens).

Y-> Check whether the corresponding NID is configured
correctly. If so, goto Step 2.
Step 2.
i.

165

ISNI Constrained Route Information

Repeat
Alarm
information
Reason
Processing
method
Alarm code: 10307

Alarm description: There
information in the ISNI.
The SCCP
incorrectly.
upper-layer
user
is
repeated
enters
the
forcible
ISNI
route
parameters
ISNI Unable to Support the Route

Function
Alarm
information
Reason
Processing
method
Alarm code: 10308

Alarm description: The ISNI does not support the route
function.
The SCCP upper-layer user enters route indicators incorrectly.

NID Route Prompt Failure

Alarm
information
Reason
Processing
method
Alarm code: 10309
Alarm description: INID route prompt failure.
The NID configuration is incorrect.

Y-> Check whether the corresponding NID is configured
correctly. If so, goto Step 2.
Step 2.
i.


166
Wrong Message Type Use ISNI

Function
Alarm
information
Reason
Processing
method
Alarm code: 10310

Alarm description: The message type uses the ISNI function
by mistake.
The non-XUDT message uses the ISNI function.

Failed to Config Multi-channel

Controller
Alarm
information
Reason
Processing
method
Alarm code: 11328

Alarm description: Failure in configuring the MTP2 multichannel controller.
There are hardware/software faults in the sub-card.

Failed to Config Digital Switch Chip

Alarm
information
Reason
Processing
method
Alarm code: 11329

Alarm description: Failure in configuring the MTP2 switching
chip.
There are hardware/software faults in the sub-card.

Failure in Getting Config Information

from Database
Alarm
information
Reason
Alarm code: 11330

Alarm description: MTP2 failed to get the configuration
information from the database.
1. The SPB home module runs abnormally.

2. There are errors in the configuration.
167
Processing
method
Faulty 2400 Configuration Data

Alarm
information
Reason
Alarm code: 15936

Alarm description: Error in the 2400 configuration data
returned from the database.
1. The response message returned from the database is empty.

2. The data in the message body returned from the database is
empty.
3. The number of the returned records exceeds the limit of the
table.
4. There are errors in the data configuration of the dispatching
weight value table.
5. There are errors in data of the slot VOQ mapping table.
Processing
method

Alarm
information
Reason
Processing
method
Alarm code: 16192

Alarm description: Exception in the configuration data
returned from the database or error in configuration data
update.
Configuration data obtained by board 1200 from database are

abnormal.
IP Fail to Get Route Table Head or

Entry
Alarm
information
Reason
Processing
method
168
Alarm code: 17984
Alarm description: Failed to get the route table head or item.
Failed to get the route table head or item.
Configure route information again.
Check whether the configured route parameters are correct.
IP Opr Static Rte Fail: Del Srte

Alarm
information
Reason
Processing
method
Alarm code: 17985
Alarm description: Failed to delete the static route item.
Failed to delete the static route item.

IP Has no Match Epu Globalport

Alarm
information
Reason
Processing
method
Alarm code: 17986
Alarm description: No matched EPU network port.
There is no matched EPU network port.
Check whether the EPU is successfully powered on.
IP Create or Enable Ifb Fail

Alarm
information
Reason
Processing
method
Alarm code: 17987
Alarm description: Failed to create or activate the IFB.
Failed to create or activate the IFB.

Check whether the size of the configuration file exceeds the
configured capacity.
IP Rcv Epu Inform Intf Up

Alarm
information
Reason
Processing
method
Alarm code: 17988

Alarm description: The EPU receives the port up message
reported by the SCS.
The EPU receives the port up message reported by the SCS.

None
IP Rcv Eepu Inform Intf Down

Alarm
information
Reason
Alarm code: 17989

Alarm description: The EPU receives the message of port
down reported by the SCS.
The EPU receives the message of port down reported by the SCS.
169
Processing
method
Check the port status.
SCS Informs RPU that EPU Is down

Alarm
information
Reason
Processing
method
Alarm code: 17990

Alarm description: The RPU receives the message of EPU port
down reported by the SCS.
The EPU board is powered down or pulled out.

1. Pull out and insert the board well. Check whether the alarm
notification appears.
Y-> Goto Step 2.
N-> End.
2. Turn off the ENUM switch. Check whether the alarm
notification appears.
N-> End.
SCS Informs RPU that EPU Is

Removed.
Alarm
information
Reason
Alarm code: 17991

Alarm description: The RPU receives the message reported
by the SCS that the EPU board has been deleted.
The configuration of the EPU board is deleted or the board type

is changed.
Processing
method
This notification needs no handling.
Precaution
This notification will cause that all the protocol stack messages
on the board will be cleared.
IP Opr Static Rte Fail: Add Srte.

Alarm
information
Reason
Processing
method
170
Alarm code: 17992
Alarm description: Failed to add the static route item.
Failed to add the static route item.

Port Configuration Failure

Alarm
information
Reason
Alarm code: 19008
Alarm description: Failed to configure the port.
1. The port rate is incorrect. The port rate can not exceed the
maximum band width of each kind of ports when a port is
created.
2. The port is configured with the PVC when it is deleted.
3. The MAXVPI or MAXVCI value of the port is illegal.
4. The amount of PVCs of the board exceeds 62K.
Processing
method
1. Check whether the port rate is correct. The port rate can not
exceed the maximum band width of each kind of ports when
a port is created (Units: Kbits/s.NP:(0,622000],Optical:
(0,155000],IMA: (0,64000]).
Y-> Goto Step 2.
N-> Configure the bandwidth parameter again. If a port is
successfully created after the the port parameters are reconfigured, end the alarm handling. If port creation fails,
goto Step 2.
2. When modifying the port rate, the newly-set port rate must
not be lower than the currently used bandwidth.
Y-> Configure a larger one. If the rate is successfully
modified after the re-configuration, end the alarm handling.
If not, goto Step 3.
N-> Goto Step 3.
3. Check whether there is PVC configured on the port when the
port is deleted.
Y-> Delete it first. If the port can be deleted successfully
after the PVC is deleted, end the alarm handling. If not, goto
Step 4.
N-> Goto Step 4.
4. Check whether the MAXVPI and the MAXVCI values are legal.
The values must be nth power of 2 on the IMAB and the APBE.
For the MAXVCI, 6=<N<=14; for the MAXVPI on the UNI
port, 1=<N<=8; for the MAXVPI on the NNI port, 1=<N<=9.
Y-> Goto Step 5.
N-> Modify them. If the port can be configured successfully
after modification, end the alarm handling. If not, goto Step
5.
5. Check whether the value of MAXVCI multiplying MAXVPI on
all ports is less than 62K.
171
N-> Modify the values. If the port can be configured

successfully after modification, end the alarm handling. If not,
Failure in Creating PVC

Alarm
information
Reason
Alarm code: 19009

Alarm description: Failed to create the inner-(inter-)board
signal-(both-) way unicast (multicast) PVC.
1. The PVCID is illegal.

2. The PVC crosses the board.
3. The incoming direction and the outgoing direction of the
both-way PVC conflict with each other.
4. The traffic parameters are illegal.
5. The port is illegal.
6. The service type mismatches the traffic type.
7. The PVC that is being created exists.
Processing
method
1. Check whether the PVCID in the range 112600.

Y-> Goto Step 2.
N-> Modify its value and create the PVC again. If the
creation is successful, end the alarm handling. If it fails, goto
Step 2.
2. Check whether the incoming and outgoing directions of PVC
are on the same board.
Y-> Goto Step 3.
N-> Modify the configuration and create the PVC again. If
the creation is successful, end the alarm handling. If it fails,
goto Step 3.
3. Check whether the incoming and outgoing VPIs of the twoway VP connection conflict with each other, and if the
incoming and outgoing VPI and VCI of the two-way VC
connection conflict with each other.
Y-> Modify the values of VCI and VPI and create the PVC. If
the PVC can be created successfully, end the alarm handling.
If not, goto Step 4.
N-> Goto Step 4.
4. Check whether the traffic parameter of the PVC is within the
traffic range of chips.
Y-> Goto Step 5.
N-> Modify it and create the PVC again. If the PVC can be
created successfully, end the alarm handling. If not, goto
Step 5.
172
5. Check whether the port configuration related to the PVC is

correct, and if the VPI and VCI values of the PVC are less the
MAXVPI and MAXVCI on the port.
Y-> Goto Step 6.
N-> Modify them and create the PVC again. If PVC can be
created successfully, end the alarm handling. If not, goto
Step 6.
6. Check whether the service type matches the traffic type.
N-> Modify the above types to make them match each other
and create the PVC again. If PVC can be created successfully,
end the alarm handling. If not, Contact ZTE Corporation.
Failure in Deleting PVC

Alarm
information
Reason
Processing
method
Alarm code: 19010

Alarm description: Failed to delete the inner-(inter-)board
single-(both-) way unicast (multicast) PVC.
The bottom-layer chip is faulty.

The bottom-layer chip works abnormally. Restart or replace the
board.
Y-> Restart the board, or restart it after replacement. If the PVC
recovers to the normal status, end the alarm handling. If not,
N->Contact ZTE Corporation.
IMA Group Related Operations

Failure
Alarm
information
Alarm code: 19264

Alarm description: The IMA-group-related
initiated by the background fail.
operations
Reason
This notification occurs when the IMA-group-related operations

(such as adding or deleting a group) initiated by the background
fail. In general, the reason is that the group parameters are
incorrect when the operations are initiated.
Processing
method
1. Check whether the parameters related with the initiated

operations are correct.
Y-> Goto Step 2.
N-> Modify them and perform operations again. If the alarm
disappears, end the alarm handling. If not, goto Step 2.
173
2. Check whether the operation steps are legal.

N-> Perform the operations according to correct steps. If the
operations can be performed successfully, end the alarm
IMA Link Operations Failure

Alarm
information
Alarm code: 19265

Alarm description: The IMA-link-related operations initiated
by the background fail.
Reason
The notification occurs when the IMA-link-related operations

(such as adding or deleting a link) initiated by the background
fail. In general, the reason is that the link parameters are
incorrect when the operations are initiated.
Processing
method
1. Check whether the parameters related with the initiated

operations are correct.
Y-> Goto Step 2.
N-> Modify them and perform the operations again. If the
handling. If not, goto Step 2.
2. Check whether the operation steps are legal.
N-> Perform the operations according to correct steps. If the
Some of High-Speed Serial Links out

of Synchronism
Alarm
information
Reason
Processing
method
174
Alarm code: 19520

Alarm description: Some high-speed serial links are out of
synchronization.
Some high-speed serial links are out of synchronization, which

may be because the PSN board is not inserted or the chip 882 is
broken.
Number of SFrame with Erroneous

Frame Format Exceeds Threshold
Alarm
information
Reason
Processing
method
Alarm code: 19521

Alarm description: The number of SFrames with frame
format mode errors exceeds the threshold.
Maybe there is a problem in the chip 872.

Number of CFrames Discarded at

the CSIX Port N due to Horizontal
Check Error Exceeds Threshold
Alarm
information
Reason
Processing
method
Alarm code: 19522

Alarm description: The number of CFrames discarded at the
CSIX port N due to horizontal check error exceeds the
threshold.


the CSIX Port N due to Vertical
Check Error Exceeds Threshold
Alarm
information
Reason
Processing
method
Alarm code: 19523

CSIX port N due to vertical check error exceeds the threshold.

175
Number of incomplete CFrames

Discarded at the CSIX Port N
Exceeds Threshold
Alarm
information
Reason
Processing
method
Alarm code: 19524

Alarm description: The number of incomplete CFrames
discarded at the CSIX port N exceeds the threshold.


the CSIX Port N Due to Invalid
Frame Type Exceeds Threshold
Alarm
information
Reason
Processing
method
Alarm code: 19525

CSIX port N due to invalid frame type exceeds the threshold.


the CSIX Port N due to Invalid
Frame Length Exceeds Threshold
Alarm
information
Reason
Processing
method
176
Alarm code: 19526

CSIX port N due to invalid frame length exceeds the
threshold.

Number of Out-of-Sequence Frames

Discarded exceeds the Threshold
Alarm
information
Reason
Processing
method
Alarm code: 19527

Alarm description: The number of out-of-sequence frames
discarded exceeds the threshold.

Number of Discarded Frames due to

CRC Check Error Exceeds
Threshold
Alarm
information
Reason
Processing
method
Alarm code: 19528

Alarm description: The number of frames discarded due to
CRC check error exceeds the threshold.

2400 Configuration Failure

Alarm
information
Reason
Alarm code: 19529

Alarm description: The traffic control fails to perform
initialization configuration on some traffic control tables of
the 2400.
The traffic control fails to perform initialization configuration on

some traffic control tables of the 2400.
The main reason may be failure in invoking the table operation
interface.
Processing
method
VSC872 Configuration Failure

Alarm
information
Alarm code: 19530

Alarm description: The traffic control fails to perform
initialization configuration on some traffic control parameters
of the 872.
Reason
177
The traffic control fails to perform initialization configuration on

some traffic control tables of the 872.
The main reason may be failure in invoking the OSS interface.
Processing
method
APS Protection Change Is Overtime

Alarm
information
Reason
Processing
method
Alarm code: 19776
Alarm description: Automatic protection switchover timeout.
The local end does not receive the response to the local request
from the opposite end for 3 times.
Check the status of the optical path.
Aps Switchover Happens

Alarm
information
Reason
Processing
method
Alarm code: 19777
Alarm description: Aps switchover occurs.
There are los alarms in the optical interface; the ENUM is lighted;
the clock is lost; the HW and the FE are broken; the opposite
end initiates switchover; and the background initiates the
forcible switchover.
Level-2 Forwarding Table

Initialization Failure
Alarm
information
Reason
Processing
method
178
Alarm code: 20032

Alarm description: Failed to initialize the level-2 forwarding
table.
Memory fails to be allocated.

Restart the board. If the alarm notification still appears, it is
concluded that the memory is insufficient. Add the physical
memory. At the same time, record the detailed information and
collect the printing records through Brs_MemPrintfShow. Contact
ZTE Corporation.
Ethernet Port Initialization on Media

Plane of UIM Board Failure
Alarm
information
Reason
Processing
method
Alarm code: 20033

Alarm description: Failed to initialize the Ethernet port on the
media plane of the UIM board.
There are hardware faults.

1. Check whether the physical configuration of the UIM board is
correct.
2. Restart the board. If the alarm notification still appears,
record the detailed information and collect the printing
records
through
Brs_MemPrintfShow.
Contact
ZTE
Corporation.
Brs Main Config Request Timeout

Alarm
information
Alarm code: 20288

Alarm description: The timer of the protocol stack for
requesting for the system configuration information from the
background database and the configuration data times out.
Reason
There is no response to the protocol configuration request, and

the configuration request timer times out for 3 times.
Processing
method
Check whether the MP and the RPU of the module where the
configuration provider belongs work normally.
Brs Main Epu Register Timeout

Alarm
information
Alarm code: 20289
Alarm description: Timeout when registering in the RPU.
Reason
There is no response when the EPU is registered in the RUP, and

the timer times out for 3 times.
Processing
method
Check whether the MP and the RPU of the module where the
configuration provider belongs work normally.
Protocol Stack Process Fails to Be

Powered on
Alarm
information
Alarm code: 20290
179
Reason
Alarm description: The power-on of the protocol stack

process failed.
1. The RPU fails to be registered.

2. The protocol stack fails to request for system configuration.
3. The communication on the control plane is interrupted.
Processing
method
1. Check whether the module MP providing configuration and

system control of the board are normal, and whether the
communication with them is normal.
Y-> Goto Step 4.
N-> Goto Step 2.
2. Pull out and insert the board, and then perform hardware
reset on the board. Check whether the alarm disappears.
Y->End.
N-> The hardware of the board may be faulty, and goto Step
3.
3. Replace the faulty board and check whether the fault is
eliminated.
Y->End.
N-> For other causes, goto Step 4.
Conflicting MAC Address on Local

Office Port
Alarm
information
Reason
Processing
method
Alarm code: 22336

Alarm description: The MAC
calculating or deleting the MAC.
address
conflicts
when
In general, the reason is the inconsistence between the protocol

stack and the database. The data is saved in the protocol stack
before being saved in the database. If the data is successfully
saved in the protocol stack, but fails to be saved in the database
(because the memory application fails, the database node is
broken, and so on, which will be fed back on the background.),
inconsistence will be caused.
1. Check whether the database node is broken.
Y->Restart RPU. If the alarm disappears, end the alarm
handling. If not, goto Step 2.
N-> Goto Step 2.
2. Check whether the memory application fails.
Y-> Delete extra tunnels. If the alarm disappears, end the
180
Alarm Pool Is over in OAM

ALARMMANAGER Process
Alarm
information
Reason
Processing
method
Alarm code: 23104

Alarm description: The alarm pool of the foreground OAM is
full.
The alarm pool of the OAM alarm management module is full.

Restart the system.
OAM Frequently Receives Alarms

and Notifications
Alarm
information
Reason
Processing
method
Alarm code: 23105

Alarm description: The OAM alarm management module
frequently receives alarms and notifications.
The OAM alarm management module frequently receives alarms

and notifications.
Board Self-Check Failure

Alarm
information
Reason
Processing
method
Alarm code: 23106
Alarm description: The board failed to self check itself.
Board hardware faults cause failure in board self-check.

Replace the board.
Board Initialization Failure

Alarm
information
Reason
Processing
method
Alarm code: 23107
Alarm description: The board Failed to be initialized.
The board fails to be initialized.

Replace the board.
181
Abnormal Half-Fixed Connection

Changes
Alarm
information
Reason
Processing
method
Alarm code: 25664

Alarm description: The half-fixed connection is abnormally
changed.
The line clock of the shelf where this board is located jitters.
There is a hardware fault in the switching chip of this board.
1. Check the clock source (if the shelf where the board is
located is configured with a CLKG board, check it. If no CLKG
board is configured, check the CLKG board that the clock
cable on the back of UIM board is connected to) to see
whether the indicator on the CLKG panel providing the clock
to this board is in the "TRACE" status.
Y-> Goto Step 2.
2. Contact ZTE Corporation to replace the faulty board.
Erroneous Half-fixed Connection

Data Configuration
Alarm
information
Reason
Processing
method
Alarm code: 25665

Alarm description: There is an error in the half-fixed
connection data configuration.
There is an error in the half-fixed connection data configuration.

1. Background configuration data may be conflict, so it is
necessary to check them. For BSC NEs, check R_BSSHDLC
and R_PHYLINK2. For CN, check R_SPC and R_PHYLINK2.
And check whether the corresponding HW and TS of each
HDLC link are legal.
Y-> If all configuration data are correct, goto Step 2.
N-> If there are any wrongly configured data, delete them
and reconfigure the data.
Master MP Power-on
Alarm
information
182
Alarm description: The master MP is powered on.
Reason
Processing
method
The master MP is powered on.

Check whether it is configured that the call will be released when
the call duration exceeds the set maximum call duration.
MP Changeover to Master Mode

Alarm
information
Reason
Processing
method
Alarm description: The MP is switched to the active status.
The MP is switched to the active status.

It is a normal notification, which needs no manual intervention.
Swap Resource Shortage

Alarm
information
Reason
Alarm code: 3649
Alarm description: There is no available switching block.
1. The configured UBs are insufficient.

2. Messages are not processed in time, which causes that the
UB is occupied for a long time and cannot be released in time.
Processing
method
Record the alarm information and contact ZTE Corporation.
Version Switch Information

Alarm
Information
Reason
Alarm code: 5959
Severity: Minor
Alarm description: Version switch information
1. The version same with that of the OMP is switched.

2. The BOOT version is switched.
Processing
method
Manually restart the OMP board.
Verification
Precautions
None
183
Notice of Power-on Status of C51

Board/ Board Soft Reset
Alarm
information
Reason
Processing
method
Alarm code: 6720
Alarm description: The C51 board is successfully powered on.
The C51 board is successfully powered on.

Microcode Is Abnormal
Alarm
information
Reason
Processing
method
Precautions
Alarm code: 15424
Alarm description: The microcode runs abnormally.
The microcode runs abnormally.

Restart the board.
The board may be unable to receive/send messages.

Alarm
information
Reason
Processing
method
Alarm code: 16704

Alarm description: There are errors in the data configuration
related to the MNIC/2 board.
The configuration data obtained by the 2350 board from the

database are abnormal.
Inconsistent CPU Version with DSP

Version
Alarm
information
184
Alarm code: 5709

Alarm description: The loaded DSP version is inconsistent
with the current CPU version.
Reason
The loaded DSP version is inconsistent with the current CPU

version.
Processing
method
Modify and configure the version of tone resource to make it

consistent with the CPU version, and then check whether the
alarm disappears.
Y-> End.
Clock Reference Changed

Alarm
information
Reason
Processing
method
Alarm code: 26176
Alarm description: The clock reference is changed.
The currently locked clock reference is changed.

CLKG Reference Quality Changed

Alarm
information
Reason
Processing
method
Alarm code: 26177

Alarm description: The reference quality of the CLKG board is
changed.
The clock quality of the CLKG board is changed.

Check the quality of the input clock (check the quality of the
external clock source equipment) if the clock quality decreases.
CLKG Work Mode Changed

Alarm
information
Reason
Processing
method
Alarm code: 26178

Alarm description: The clock work mode of the CLKG board is
changed.
The clock work mode of the CLKG board is changed.

Clock Source Invalidation Reason

Changed
Alarm
information
Reason
Processing
method
Alarm code: 26179

Alarm description: The clock reference failure reason is
changed.
The clock reference becomes invalid.

185
SCCP GT Translation Failure

Alarm
information
Reason
Alarm code: 10304
Alarm description: GT translation failure.
1. The address of called party has no signaling point code and is

not configured with a GT number.
2. The GT number indicator is incorrect.
3. The corresponding subsystem of the called GT number is
unavailable.
4. The corresponding signaling point of the called GT number is
inaccessible.
5. The called GT number is not configured in the database.
Processing
method
1. Check whether the GT number, which fails to be translated,

is configured at the background.
Y-> Goto Step 2.
N-> Configure the corresponding GT number. After
configuration, check whether the alarm disappears. Y-> End.
N-> Goto Step 2.
i.


No Message Response in the Link

for a Long Time
Alarm
information
Reason
Processing
method
Alarm code: 10560

Alarm description: There is no message response in the
SSCS link for a long time.
There is no message response in the link for a long time, maybe

because the physical layer does not work normally.
1. Check whether there are abnormal alarms in transmission.
Y-> Contact transmission engineers to handle them.
N-> Goto Step 2.
2. Check whether the optical fibers are connected well.
Y-> Goto Step 3.
186
N-> Connect them well and check whether the alarm still
exists. Y-> goto Step 3. N-> End.
i.


Successful MGW Registration

Alarm
information
Reason
Processing
method
Alarm code: 10822
Alarm description: The MGW has been registered.
The MGW is successfully registered to the MSCS, and it can

process services.
None.
MGW Registration Failure

Alarm
information
Reason
Alarm code: 10823

Alarm description: The MGW is not registered in the MGC
because the system is just powered on, the office direction in
unaccessible, or there is an error in the configuration.
1. The MSCS office is obstructed.

2. The configuration related to MGW-and-SERVER registration is
incorrect.
Processing
method
1. Make no manual intervention and wait for 90 seconds. Then

judge whether there is a notification of successful MGW
registration.
Y-> End.
N-> Goto Step 2.
2. Check whether the SERVER office is accessible.
Y-> Goto Step 3.
N-> Refer to the handling suggestion on the alarm of office
inaccessible.
i.
Back up the related configuration data on local office and

peer end office
187
ii. Back up the related history alarms, history alarm

notifications and current alarms on local office and peer
end office
SUA GT Translation Failure

Alarm
information
Reason
Alarm code: 12608
Alarm description: GT translation failure.
1. When the address of the called party has no signaling point

code and is not configured with a GT number.
2. The input GT number indicator of the address of the called
party is incorrect.
3. The corresponding subsystem of the called GT number is
unavailable.
4. The corresponding signaling point of the called GT number is
unreachable.
5. The called GT number is not configured in the database.
Processing
method
1. Check whether the GT number, which fails to be translated,

is configured at the background.
Y-> Goto Step 2.
N-> Configure the corresponding GT number. After
configuration, check whether the alarm disappears. Y-> End.
N-> Goto Step 2.
i.


M2PA Link Congested

Alarm
information
Reason
Alarm code: 13632

Alarm description: Notification due to M2PA signaling link
congestion.
1. There is heavy traffic in the local end or the remote end.

2. Load on links is uneven.
3. Links configured are insufficient.
188
Processing
method

Y-> End.
N-> Goto Step 2.
2. Check whether there is heavy traffic in the local end or the
remote end.
Y-> Goto Step 3.
N-> Goto Step 4.
Y-> Check whether the load is evenly shared among links. Y> Goto Step 1. N-> Goto Step 4.
i.


M2PA Processor Outage

Alarm
information
Reason
Alarm code: 13633

Alarm description: Notification due to faults in the M2P
processor.
1. The home module of the local links runs abnormally.

2. The remote processor is faulty.
Processing
method
1. If the remote processor is faulty, contact the related

personnel in the remote office. If the local processor is faulty,
check whether the home SMP module of the M2PA link runs
normally.
Y-> Goto Step 2.
N-> Switch and reset the SMP module. If the problem still
exists, goto Step 2.
i.


189
ASP Status Changed

Alarm
information
Reason
Processing
method
Alarm code: 13888
Alarm description: The ASP status is changed.
The ASP status is changed

Y-> End.
N-> Goto Step 2.
i.


AS Status Changed
Alarm
information
Reason
Processing
method
Alarm code: 13889
Alarm description: The AS status is changed.
The AS status is changed

Y-> End.
N-> Goto Step 2.
i.


Receiving SIGTRAN Error Message

Alarm
information
190
Alarm code: 13890

Alarm description:
messages.
Notification
due
to
receiving
error
Reason
Processing
method
Error messages are received.

Y-> End.
N-> Goto Step 2.
2. Handle the problem according to the additional information
of this notification. If the alarm is still reported, goto Step 3.
i.


Receiving SIGTRAN Notification

Message
Alarm
information
Reason
Processing
method
Alarm code: 13891

Alarm description: Received the notification message of the
ASASP status.
The notification messages about the ASASP status is received.

Y-> End.
N-> Goto Step 2.
i.


Association Establishment Failure

Alarm
information
Reason
Alarm code: 14144
Alarm description: Failed to create the association.
The Sctp fails to create the association.
191
Processing
method

Y-> End.
N-> Goto Step 2.
2. If the alarm does not disappear, refer to "Troubleshooting for
blocked association".
i.


SIG_IPI Forwards Service Messages

Abnormally
Alarm
information
Reason
Alarm code: 16193

Alarm description: There is an exception when the SIG_IPI
forwards the service message.
In a certain period of time, SIG_IPI forwards the service

messages abnormally. The detection time is configured on
network management background. If there is no incoming or
outgoing service message in a detection period, this alarm
appears. Generally, it is caused by the following reasons:
1. In case of multiple SIGIPIs, messages in one direction may
only be transmitted in one port because of router or switch
configuration. In this case, disable this function.
2. The association configuration (source and destination IP
addresses, VPN ID, source and destination port numbers) of
the local and remote equipment is inconsistent, causing
SIG_IPI unable to forward messages.
3. There are errors in network transmission, causing one-way
connection or two-way connectionless.
4. The peer-end equipment is faulty, sending no messages.
Processing
method
1. In case of multiple SIGIPIs, messages in one direction may

only be transmitted in one port because of router or switch
configuration. Judge whether it is required to enable this
function.
Y-> Goto Step 2.
N-> Goto Step 3.
192
2. It is required that load sharing should be configured in two

ways of the SIGIPI. Check whether the configuration is
correct.
Y-> Goto Step 4.
N-> Modify the configuration to end the alarm handling.
3. It is required to disable this function through the background
configuration. Check whether it is disabled.
Y-> Goto Step 4.
N-> Modify the configuration to end the alarm handling.
4. Check whether the association configuration,
connection, and peer-end equipment are normal.
network
Y-> Goto Step 5.

N-> Modify the association configuration, and repair the
network connection or peer-end equipment. End the alarm
handling.
5. Restart the SIGIPI board. Check whether the fault is
eliminated.
Y-> End.
IUAs ASP State Changed

Alarm
information
Alarm description: The ASP status of the IUA is changed.
Reason
The ASP status of the IUA is changed because of the status of

the association or some ASP operations.
Processing
method
Check whether the status of the association corresponding to the

ASP is normal.
IUAs AS State Changed

Alarm
information
Alarm description: The AS status of the IUA is changed.
Reason
The AS status of the IUA is changed because the ASP status is

changed.
Processing
method
Check whether the status of the association corresponding to the

AS is normal.
193
IUA Receives an ERR Message

Alarm
information
Alarm description: IUA receives the ERR message.
Reason
The ASP of the opposite-end IUA sends an ERR message to the

local end, containing the error code.
Processing
method
This notification message is used as the reference information in

case that the AS has problems. So these ERR notifications need
no handling if the status of every AS is normal.
Handle the problem according to specific error codes if the
status of the AS is abnormal. In other cases except that the
error code is 2, 6 and 7, there are problems in the program,
which needs to be updated.
In case that the error code is 2, there are errors in the
configuration problem. In this case, check whether the IID
configuration is consistent between the two ends.
In case that the error code is 6, no handling is needed if AS is in
normal status.
In case that the error code is 7, decoding errors occur. In this
case, locate the fault according to code stream analysis.
IUA Receives an NTFY Message

Alarm
information
Alarm description: IUA receives the NTFY message.
Reason
The ASP of the opposite-end IUA sends an NTFY message to the

local end, generally when the AS status is changed.
Processing
method
This notification message is used as the reference information in

case that the AS has problems. So these NTFY notifications need
no handling if the status of every AS is normal.
NTFY notifications help you to know the change of peer-end AS
status.
TCP Received RST Packet

Alarm
information
Reason
Alarm code: 18240
Alarm description: The TCP receives the RST message.
1. The peer end initiates the tcp connection reset, and sends a
RST message.
2. The peer end receives invalid tcp connection, and returns a
RST message.
194
Processing
method
Check whether there is severe packet loss in the physical link.

(It can be checked through the ping command).
Y-> Handle physical link faults and end the alarm handling.
TCP Connection Aborted

Alarm
information
Reason
Alarm code: 18241
Alarm description: The TCP connection is broken.
1. There are faults in the network communication.

2. The peer end closes this TCP connection normally/abnormally.
3. There are faults in the peer-end equipment.
Processing
method
Check whether there is severe packet loss in the physical link.

(It can be checked through the ping command).
Y-> Handle physical link faults and end the alarm handling.
IP Offline Setting: Invalid Interface

Alarm
information
Reason
Processing
method
Alarm code: 20544
Alarm description: IP offline setting: invalid interface.
The interface does not exist.

1. Check whether the configured parameters are correct.
Y-> Goto Step 3.
N-> Goto Step 2.
2. Configure the parameters correctly, and check whether the
alarm disappears.
Y-> End.
N-> There may be hardware faults in the board. Goto Step 3.
3. Reset the board, and check whether the fault is eliminated.
Y-> End.
195
IP Offline Setting: Disable This IP

Using No IP Unnumbered Command
Firstly
Alarm
information
Reason
Processing
method
Alarm code: 20545

Alarm description: IP offline configuration: Use the no ip
unnumbered command to make IP processing at the
interface invalid.
Use the no ip unnumbered command to make IP processing at

the interface invalid.
Y-> Goto Step 3.
N-> Goto Step 2.
alarm disappears.
Y-> End.
Y-> End.
IP Offline Setting: Interface Address

Addition Failure
Alarm
information
Reason
Processing
method
Alarm code: 20546

Alarm description: IP offline configuration: Failure in adding
an interface address.
Failure in adding an address route causes failure in adding an

interface address.
Y-> Goto Step 3.
N-> Goto Step 2.
alarm disappears.
Y-> End.
N-> There may be software faults in the board. Goto Step 3.
196

Y-> End.
IP Offline Setting: Failure in Writing

to a Database
Alarm
information
Reason
Processing
method
Alarm code: 20547

Alarm description: IP offline configuration: Failure in writing
the database.
Failed to write the database.

Y-> Goto Step 3.
N-> Goto Step 2.
alarm disappears.
Y-> End.
Y-> End.
IP Offline Setting: IP Address

Deletion Failure
Alarm
information
Reason
Processing
method
Alarm code: 20548

Alarm description: IP offline configuration: Failure in deleting
the IP address.
The IP address fails to be deleted.

Y-> Goto Step 3.
N-> Goto Step 2.
alarm disappears.
Y-> End.
197

Y-> End.
IP Offline Setting: Invalid Address

Alarm
information
Reason
Processing
method
Alarm code: 20549

Alarm description: ip offline configuration: Invalid host
address.
The host address is invalid.

Y-> Goto Step 3.
N-> Goto Step 2.
alarm disappears.
Y-> End.
Y-> End.
IP Offline Setting: Invalid Nexthop

Alarm
information
Reason
Processing
method
Alarm code: 20550
Alarm description: IP offline configuration: Invalid next hop.
The next hop is invalid.

Y-> Goto Step 3.
N-> Goto Step 2.
alarm disappears.
Y-> End.
198
Y-> End.
IP Offline Setting: Inconsistent IP

Address and Subnet Mask
Alarm
information
Reason
Processing
method
Alarm code: 20553

Alarm description: IP offline configuration: Inconsistent IP
address and subnet mask.
The IP address and the subnet mask are inconsistent.

Y-> Goto Step 3.
N-> Goto Step 2.
alarm disappears.
Y-> End.
Y-> End.
IP Offline Setting: Route Addition

Failure
Alarm
information
Reason
Processing
method
Alarm code: 20554

Alarm description: IP offline configuration: Failure in adding
a route.
A route fails to be added.

Y-> Goto Step 3.
N-> Goto Step 2.
alarm disappears.
Y-> End.
199

Y-> End.
IP Offline Setting: No Matched Route

Alarm
information
Reason
Processing
method
Alarm code: 20555

Alarm description: IP offline configuration: Failure in finding
the matched route to be deleted.
The matched route to be deleted fails to be found.

Y-> Goto Step 3.
N-> Goto Step 2.
alarm disappears.
Y-> End.
Y-> End.
IP Offline Setting: Routing Deletion

Failure
Alarm
information
Reason
Processing
method
Alarm code: 20556

Alarm description: IP offline configuration: Failure in deleting
a route.
A route fails to be deleted.

Y-> Goto Step 3.
N-> Goto Step 2.
alarm disappears.
Y-> End.
200

Y-> End.
IP Offline Setting: Next Hop Conflicts

Alarm
information
Reason
Processing
method
Alarm code: 20557
Alarm description: IP offline configuration: Next hop conflict.
The next hop conflicts.

Y-> Goto Step 3.
N-> Goto Step 2.
alarm disappears.
Y-> End.
Y-> End.
IP Offline Setting: Next Hop not

Connected Directly
Alarm
information
Reason
Processing
method
Alarm code: 20558

Alarm description: IP offline configuration: The next hop is
not directly connected.
The next hop is not directly connected.

Y-> Goto Step 3.
N-> Goto Step 2.
alarm disappears.
Y-> End.
201
Y-> End.
IP Offline Setting: None-Existent IP

Address
Alarm
information
Reason
Processing
method
Alarm code: 20559

Alarm description: IP offline configuration: The IP address
does not exist.
The IP address does not exist.

Y-> Goto Step 3.
N-> Goto Step 2.
alarm disappears.
Y-> End.
Y-> End.
IP Offline Setting: Failure in Reading

Database
Alarm
information
Reason
Processing
method
Alarm code: 20561

Alarm description: IP offline configuration: Failure in reading
the database.
The protocol stack fails to be powered on due to incorrect

configuration obtained.
Y-> Goto Step 3.
N-> Goto Step 2.
alarm disappears.
Y-> End.
202

3. Replace the faulty board, and check whether the fault is
eliminated.
Y-> End.
IP Offline Setting: Not an Ethernet

Port
Alarm
information
Reason
Processing
method
Alarm code: 20562

Alarm description: IP offline configuration: This is not an
Ethernet port.
This is not an Ethernet port.

Y-> Goto Step 3.
N-> Goto Step 2.
alarm disappears.
Y-> End.
Y-> End.
IP Offline Setting: MAC beyond Valid

Range
Alarm
information
Reason
Processing
method
Alarm code: 20563

Alarm description: IP offline configuration: The MAC address
exceeds the range.
The MAC address exceeds the range.

Y-> Goto Step 3.
N-> Goto Step 2.
203

alarm disappears.
Y-> End.
Y-> End.
IP Offline Setting: Incorrect MAC

Type Transferred by Database
Alarm
information
Reason
Processing
method
Alarm code: 20564

Alarm description: IP offline configuration: The MAC
configuration type transferred by the database is incorrect.
The MAC configuration type transferred by the database is

incorrect.
Y-> Goto Step 3.
N-> Goto Step 2.
alarm disappears.
Y-> End.
Y-> End.
IP Offline Setting: The Same IP

Address in the Network Section Has
Existed
Alarm
information
Reason
204
Alarm code: 20565

Alarm description: IP offline configuration: The same IP
address in one network section has existed.
The IP address to be added exists in the same network section.
Processing
method

Y-> Goto Step 3.
N-> Goto Step 2.
alarm disappears.
Y-> End.
Y-> End.
IP Offline Configuration: Invalid IP

Broadcast Address
Alarm
information
Reason
Processing
method
Alarm code: 20566

Alarm description: IP offline configuration: Invalid broadcast
address.
The broadcast address is invalid.

Y-> Goto Step 3.
N-> Goto Step 2.
alarm disappears.
Y-> End.
Y-> End.
IP Offline Configuration: One

Interface Can Only Be Configured
Four IP Addresses at Most
Alarm
information
Alarm code: 20567
205
Reason
Processing
method
Alarm description: IP offline configuration: One interface can

be configured at most four IP addresses.
One interface can be configured at most four IP addresses.

Y-> Goto Step 3.
N-> Goto Step 2.
alarm disappears.
Y-> End.
Y-> End.
IP Offline Configuration: Parameter

Imported From DB Is Null
Alarm
information
Reason
Processing
method
Alarm code: 20568

Alarm description: IP offline configuration: The parameter
imported from the DB is null.
The parameter imported from the DB is null.

Y-> Goto Step 3.
N-> Goto Step 2.
alarm disappears.
Y-> End.
Y-> End.
206
IP Offline Setting: IP Address Has

Existed
Alarm
information
Reason
Processing
method
Alarm code: 20569

Alarm description: IP offline configuration: The IP address
has existed.
The IP address already exists.

Y-> Goto Step 3.
N-> Goto Step 2.
alarm disappears.
Y-> End.
Y-> End.
IP Offline Setting: Invalid Mask or

Network Prefix
Alarm
information
Reason
Processing
method
Alarm code: 20570

Alarm description: IP offline configuration: Invalid mask or
network prefix.
The mask or the network prefix is invalid.

Y-> Goto Step 3.
N-> Goto Step 2.
alarm disappears.
Y-> End.
Y-> End.
207
Failure in Allocating Memory for ARP

Table Instance
Alarm
information
Reason
Processing
method
Alarm code: 20800

Alarm description: Failure in allocating memory for the arp
table instance.
The memory of the board is insufficient.

Restart the board. If this alarm notification still appears, it is
ZTE Corporation.
Failure in Allocating Memeory for

ARP Table Cache
Alarm
information
Reason
Processing
method
Alarm code: 20801

Alarm description: Failure in allocating memory for the arp
table cache.
The memory of the board is insufficient.

Restart the board. If this alarm notification still appears, it is
ZTE Corporation.
Conflicting IP Addresses
Alarm
information
Alarm code: 20802

Alarm description: The configured IP address conflicts with
the address of other host in the network.
Reason
The IP address (including virtual addresses in the same network

section) configured for this gateway is the same with that of
other host in the network.
Processing
method
1. Check the port configuration to see if the same IP address is

configured.
Y-> Goto Step 2.
N-> Goto Step 3.
2. Modify the IP address of one port to end the alarm handling.
208
Conflicting MAC Addresses in

Subnet
Alarm
information
Reason
Processing
method
Alarm code: 20803

Alarm description: In the received ARP message, the source
MAC address is same with that of the interface receiving the
ARP message.
The MAC address of this network is same with other MAC

address in the associated network.
1. Check whether the same mac address is configured.
Y-> Goto Step 2.
N-> Goto Step 3.
2. Modify one MAC address on a port to finish the alarm
handling.
RIP Neighbor Configuration Errors

Alarm
information
Reason
Processing
method
Alarm code: 21059
Alarm description: RIP neighbor configuration error.
During adding a neighbor, the

mismatches that of the interface.
address
of
the
neighbor
1. Check the interface address to see whether it is in the same

network segment with that of the neighbor of the rip.
Y-> Goto Step 3.
N-> Goto Step 2.
2. Check whether the configured neighbor address is the
network number or broadcasting address.
Y-> Goto Step 3.
N-> Goto Step 4.
3. Reconfigure the neighbor address to end the alarm handling.
Precautions
This notification will cause that the static route that should be
got through the neighbor cannot be created.
209
RIP Interface Authentication Errors

Alarm
information
Alarm code: 21060
Alarm description: Error in RIP port verification.
Reason
When the interface needs authenticating, the authentication

code is wrong.
Processing
method
1. Check whether the authentication types on the two ends are

consistent.
Y-> Goto Step 3.
N-> Goto Step 2.
2. Modify authentication types on the two ends to make them
consistent. End the alarm handling.
3. If the authentication types are consistent, check whether the
authentication keys are consistent. Yes-> Goto Step 4. No->
modify them to be consistent. End the alarm handling.
RIP Neighbor Age Out

Alarm
information
Reason
Processing
method
Alarm code: 21062
Alarm description: The RIP neighbor expires.
The timer of the neighbor expiring is triggered.

It is an important notification, which needs no processing.
RIP Port Disabled

Alarm
information
Reason
Processing
method
Alarm code: 21063
Alarm description: The RIP interface is disabled.
The interface is disabled.

1. Check whether this port is changed from rip interface to nonrip interface.
Y-> This phenomenon is normal, so end the alarm handling.
N-> Goto Step 2.
2. Check whether the interface is disabled.
Y-> If the interface is not required to be disabled, enable the
interface and end the alarm handling.
If the interface is required to be disabled, this phenomenon
is normal. End the alarm handling.
210
3. If the interface is not disabled, check the physical status of it.

If it is down, check the physical link connection. End the
alarm handling. If it is up, goto Step 4.
RIP Port Enabled

Alarm
information
Reason
Processing
method
Alarm code: 21064
Alarm description: The RIP port is enabled.
The RIP interface is enabled.

1. Check whether this interface is set as a rip interface.
Y-> This phenomenon is normal, so end the alarm handling.
N-> Goto Step 2.
Conflicting Router ID
Alarm
information
Reason
Processing
method
Alarm code: 21312

Alarm description: The routerID in the received hello packet
is same with its own one.
The Router IDs configured on local end and peer end conflict.
Modify the RouterIDs configured on local end or peer end and
restart the OSPF process. Check whether the alarm disappears.
Y-> End.
OSPF Virtual Link State Changed

Alarm
information
Reason
Processing
method
Alarm code: 21315

Alarm description: The status of the OSPF virtual interface is
transferred.
The status of the virtual link is changed.

Check the physical link of the virtual link and the configuration
parameters of the virtual interface.
211
OSPF Interface State Changed

Alarm
information
Reason
Processing
method
Alarm code: 21316

Alarm description: The status of the OSPF interface is
transferred.
The status of the interface is changed.

Check the physical link and the configuration parameters of the
virtual interface.
Erroneous OSPF Virtual Interface

Configuration
Alarm
information
Reason
Processing
method
Alarm code: 21319
Alarm description: Error in OSPF virtual link configuration.
There are errors in the virtual link configuration.

1. Check whether the HelloInterval, DeadInterval, Options and
other parameters of the virtual link conflict with those of the
peer-end neighbor.
N-> Goto Step 2.
2. Modify OSPF configuration parameters to make them same
at the two ends. Check whether the alarm disappears.
Y-> End.
Erroneous OSPF Interface

Configuration
Alarm
information
Reason
Processing
method
Alarm code: 21320
Alarm description: Error in OSPF interface configuration.
There are errors in interface configuration.

other parameters of the virtual link conflict with those of the
peer-end neighbor.
N-> Goto Step 2.
2. Modify OSPF configuration parameters to make them same
at the two ends. Check whether the alarm disappears.
212
Y-> End.
OSPF Virtual Interface

Alarm
information
Alarm code: 21324

Alarm description:
authentication.
Failure
in
OSPF
virtual
interface
Reason
The authentication information configured for the virtual link is

incorrect.
Processing
method
1. Check whether the authentication mode configured at the

local end is the same with that configured on the peer end.
Y-> Goto Step 2.
N-> Reconfigure authentication modes
identical and end the alarm handling.
to
make
them
2. If the configured authentication mode is the password

authentication mode, check whether the passwords
configured on the two ends are the same.
Y-> Goto Step 3.
N-> Modify them to the same ones and end the alarm
handling.
3. Check whether the authentication mode is the MD5 key
authentication mode.
N-> Check whether the MD5 keys configured on the two
ends are the same. If they are different, modify them to the
same ones and end the alarm handling.
OSPF Interface Authentication

Failure
Alarm
information
Alarm code: 21325
Alarm description: Failure in OSPF interface authentication.
Reason
The authentication information of the interface configuration is

incorrect.
Processing
method
1. Check whether the authentication mode configured at the

local end is the same with that configured on the peer end.
Y-> goto Step 2.
213
N-> Reconfigure authentication modes

identical and end the alarm handling.
to
make
them
2. If the configured authentication mode is the password

authentication mode, check whether the passwords
configured on the two ends are the same.
Y-> Goto Step 3.
N-> Modify them to the same ones and end the alarm
handling.
3. Check whether the authentication mode is the MD5 key
authentication mode.
N-> Check whether the MD5 keys configured on the two
ends are the same. If they are different, modify them to the
same ones and end the alarm handling.
Status of OSPF Virtual Neighbor

Transfers
Alarm
information
Reason
Alarm code: 21326

Alarm description: The status of the OSPF virtual neighbor is
transferred.
1. The configuration is wrong.

3. There is no route.
Processing
method
1. Check whether there is any route from the neighbor end to

the local end.
Yes-> Goto Step 2.
No-> Find the reason or Contact ZTE Corporation.
other parameters of the virtual link are the same with those
of the peer-end neighbor. If they are different, modify them
to be the same.
Y-> End.
Status of OSPF Neighbor Transfers

Alarm
information
214
Alarm code: 21327
Reason
Alarm description: The status of the OSPF neighbor is

transferred.
1. The configuration is wrong.

Processing
method
1. Check whether the network cable from the neighbor device

to the switch is connected well.
Y-> goto Step 2.
N-> Connect it again and end the alarm handling.
2. Check whether the IP addresses on the two ends are in the
same network section.
Y-> Goto Step 3.
N-> Modify the IP addresses to make them be in the same
network section, and wait for the status of the neighbor
device to become UP. End the alarm handling.
3. Check whether interfaces on both ends start the OSPF
function.
Y-> goto Step 4.
N-> Start the OSPF function, and wait for the status of the
neighbor device to become UP. End the alarm handling.
4. Check whether the OSPF interface parameters on both ends
are the same.
N-> Modify the OSPF interface parameters to make them be
the same, and wait for the status of the neighbor device to
become UP. End the alarm handling.
LSDB Overflow
Alarm
information
Reason
Processing
method
Alarm code: 21329

Alarm description:
overflows.
The
LSDB
(Link
Status
DataBase)
The LSDB (Link Status DataBase) overflows.

Configure route aggregation to reduce the number of LSAs.
Check whether the alarm disappears.
Y-> End.
215
Failure in Creating BGP Instance

Alarm
information
Reason
Processing
method
Alarm code: 21568
Alarm description: The BGP Failed to create the BGP instance.
The memory fails to be allocated.

1. Check whether other routing protocols are normal.
Y-> Goto Step 2.
2. Delete all routing protocols and reconfigure the BGP. Check
Y-> End.
Failure in Creating BGP Neighbor

Alarm
information
Reason
Processing
method
Alarm code: 21570
Alarm description: Failed to create the BGP neighbor.
The Ipi pointer of the BGP instance is NULL.

1. Check whether other routing protocols are normal.
Y-> Goto Step 2.
2. Delete all routing protocols and reconfigure the BGP. Check
Y-> End.
Failure in Getting TCB when BGP

Connection is Passively Open
Alarm
information
216
Alarm code: 21572

Alarm description: Failed to
connection is passively opened.
get
TCB
when
the
BGP
Reason
TCB fails to be gotten since the destination address and the

destination port are occupied.
Processing
method
Check all TCP connections to see if there is a connection, whose

source address is the neighbor IP address, destination address is
the local IP address and the destination port is 179.
Y-> Disable this connection. The alarm disappears, and end the
alarm handling.
Failure in Getting TCB when BGP

Connection is Actively Started
Alarm
information
Alarm code: 21573

Alarm description: Failed to
connection is actively opened.
get
TCB
when
the
BGP
Reason
TCB fails to be gotten because the source address and the

source port are occupied.
Processing
method
Check all TCP connections to see if there is a connection whose

source address is the local IP address, destination address is the
neighbor IP address, and the destination port is 179.
Y-> Disable this connection. The alarm disappears. End the
alarm handling.
BGP Fails to Enable Passive

Listening
Alarm
information
Reason
Processing
method
Alarm code: 21575

Alarm description: Failed to get the TCB when the local BGP
connection is passively opened.
The number of started TCBs is greater than the maximum.

Check whether the number of TCP connections exceeds 256.
Y->Disable some useless TCP connections. The alarm disappears.
End the alarm handling.
BGP Fails to Enable Actively Started

TCB
Alarm
information
Reason
Alarm code: 21576

Alarm description: Failed to get the TCB when the local BGP
connection is actively opened.
The number of started TCBs is greater than the maximum.
217
Processing
method
Check whether the number of TCP connections exceeds 256.

Y->Disable some useless TCP connections. The alarm disappears.
BGP Failed to Add Neighbor to

Group
Alarm
information
Reason
Processing
method
Alarm code: 21579

Alarm description: The BGP Failed to add a neighbor to the
group.
BGP failed to create a group; BGP failed to enable a group.

Check the BGP configuration.
BGP Neighbor Failed to Read

Receive Buffer
Alarm
information
Reason
Processing
method
Alarm code: 21582

Alarm description: The BGP Failed to read the receiving
buffer.
The returned cache length is incorrect when reading messages.

Use the packet capture tool to check the received BGP message.
Neighbor Hold Timer Expires

Alarm
information
Reason
Alarm code: 21584
Alarm description: The BGP neighbor Hold timer times out.
1. The physical link is interrupted.

2. TCP connection is interrupted.
Processing
method
Check the network configuration to see if the IP address of the

neighbor can be successfully pinged. If it can not, check the
network cable connection to make it can be successfully pinged.
If it still can not, Contact ZTE Corporation.
BGP Neighbor FSM Error

Alarm
information
218
Alarm code: 21586
Reason
Processing
method
Alarm description: Error in the BGP neighbor limited status

machine.
There are errors in the neighbor limited status machine.

Check the BGP event.
BGP State Changed.

Alarm
information
Reason
Processing
method
Alarm code: 21607
Alarm description: The status of the BGP is transferred.
The status machine is changed.

Check the BGP connection status.
Courier Create BGP Fail

Alarm
information
Reason
Processing
method
Alarm code: 21825
Alarm description: Courier Failed to create a BGP instance.
There is no router ID or getting the router ID failed.

Check the router
configuration.
ID
configuration
and
the
interface
IP
Courier Create OSPF Fail

Alarm
information
Reason
Processing
method
Alarm code: 21826
Alarm description: Failed to create an OSPF instance.
Failed to create OSPF-related timers and tables.

Check the router
configuration.
ID
configuration
and
the
interface
IP
Courier Enable OSPF by the

RTR_ID Fail
Alarm
information
Reason
Processing
method
Alarm code: 21831

Alarm description: Failed to create an OSPF instance by using
one RTR_ID.
Failed to create OSPF-related timers and tables.

Check the timer and the memory of the protocol stack. Use the
debugging
functions
Brs_CourierMemPrintfShow
and
Brs_MemPrintfShow in shell of rpu to check the utilization
219
condition of the memory; use courier_show_timerq_info to

check the courier clock information.
IP Forwarding Table Fails to Create

Routes
Alarm
information
Alarm code: 21837
Alarm description: Failed to synchronize the IP route table.
Reason
Overflow of the forwarding table causes failure in adding

dynamic routes.
Processing
method
1. Check the routes on the RPU to see if there are useless

interface addresses and static routes.
Y-> Delete the useless IP interface addresses and static
routes, and goto Step 2.
N-> If no IP address is configured on the interface, goto Step
3.
Y-> End.
N-> Goto Step 3.
3. Reduce the amount of routing information distributed by the
peer-end router through route aggregation. Check whether
the alarm disappears on the local.
Y-> End.
N-> Goto Step 4.
4. Record the detailed information.
i.
Record the IP address and static route information on the

interface.
ii. Record the dynamic route information. Contact ZTE

Corporation.
Incompatible RIP Version Number

Alarm
information
220
Alarm code: 21065

Alarm description: The version number of the interface is
inconsistent with that of the routing update message, so the
routing update message is refused to be received.
Reason
The version number of the interface on the peer-end equipment

is inconsistent with that on local-end equipment.
Processing
method
1. Check whether the version number of the interface on the

peer-end equipment is inconsistent with that on local-end
equipment.
Y-> Goto Step 3.

N-> Goto Step 2.
2. If the version numbers are inconsistent, reconfigure them to
be consistent, and end the alarm handling.
BGP State Changed

Alarm
information
Reason
Processing
method
Alarm code: 21587
Alarm description: The BGP state changes.
The state machine changes.

Check the BGP connection status.
ISIS Timer Creation Failure

Alarm
information
Reason
Processing
method
Alarm code: 22592
Alarm description: ISIS timer creation failure.
The ISIS module fails to create a timer when being initialized.

Restart the system and check whether the alarm disappears.
Y-> End.
N-Contact ZTE Corporation.
ISIS Hello Message Authentication

Failure
Alarm
information
Alarm code: 22593
Alarm description: ISIS Hello message authentication failure.
Reason
The Hello message authentication modes or keys configured on

the routers at the two ends are inconsistent.
Processing
method
1. Find out the peer-end router according to system id in the

alarm message.
2. Execute the show running config command for both the
local router and the peer-end router. Check the routers on
the two ends in the displayed equipment running
configuration to see if the Hello message authentication
modes in ISIS protocol configuration on the interface are
consistent (MD5/TEXT).
Y-> Goto Step 3.
221
N-> Modify the authentication modes on the two ends to be

consistent, and perform the interconnection operations again.
configuration to see if the Hello message authentication keys
in ISIS protocol configuration on the interface are consistent
(MD5/TEXT).
N-> Modify the authentication modes on the routers of the
two ends to be consistent, and perform the interconnection
operations again. End the alarm handling.
ISIS LSP Message Authentication

Failure
Alarm
information
Alarm code: 22594
Alarm description: ISIS LSP message authentication failure.
Reason
The LSP message authentication modes or keys configured on

the routers of the two ends are inconsistent.
Processing
method

alarm message.
configuration to see if protocol authentication modes in ISIS
protocol instance configuration are consistent (MD5/TEXT).
Y-> Goto Step 3.
configuration to see if the protocol message authentication
keys in ISIS protocol stack instance configuration are
Precautions
222
The NE cannot receive network topology information.
ISIS SNP Message Authentication

Failure
Alarm
information
Alarm code: 22595
Alarm description: ISIS SNP message authentication failure.
Reason
The SNP message authentication modes or keys configured on

the routers of the two ends are inconsistent.
Processing
method

alarm message.
configuration to see if protocol authentication modes in ISIS
protocol instance configuration are consistent (MD5/TEXT).
Y-> Goto Step 3.
configuration to see if the protocol message authentication
keys in ISIS protocol stack instance configuration are
ISIS Neighbor Status Change

Alarm
information
Reason
Processing
method
Alarm code: 22596

Alarm description: The
relationship changes.
status
The peer-end router is down.
The corresponding link is down.
of
the
ISIS
neighbor
1. Check the alarm information to see if the neighbor status is

changed from up to down.
Y-> Goto Step 2.
N-> No handling is required.
223
2. Find out the peer-end router according to the system id, and
check whether the status of the link with the peer-end router
is normal.
Y-> Goto Step 3.
N-> Repair the corresponding link and end the alarm
handling.
3. Check whether the peer-end router runs normally.
Y-> End.
N-> Enable the peer-end router run normally and end the
alarm handling.
Abnormal Message is Received

Alarm
information
Reason
Processing
method
Precautions
Alarm code: 22597
Alarm description: Error protocol messages are received.
Error protocol messages are received.

Check whether the bottom link has communication problems and
if there are any illegal systems in the network.
The messages are discarded.
BFD Faults
Alarm
information
Reason
Processing
method
Alarm code: 22848
Alarm description: BFD faults occur.
The link is faulty, and L3 fails to be connected with the opposite

end. The specific reason may be that the BFD session is not
rationally configured.
1. Check whether the BFD session is configured correctly.
Y-> Goto Step 3.
N-> Goto Step 2.
2. Reconfigure it.
Y-> If the session can be created
reconfiguration, end the alarm handling.
successfully
after
N-> If the session still fails to be created after configuration,

goto Step 3.
3. Record the detailed configuration information.
i.
Save the configuration, and record the configuration

procedure.
ii. Contact ZTE Corporation.
224
Abbreviations
Abbreviations
Full Name
A
ACK
Acknowledgement
ACM
Accumulated Call Meter
ACM
Address Complete Message
AE
Application Entity
APB
ATM Process Board
AoC
Advice of Charge
AoCC
Advice of Charge Charging supplementary service
AoCI
Advice of Charge Information supplementary

service
ASE
Application Service Element
ASIG
Analog Signaling
AuC
Authentication Centre
B
BAIC
Barring of All Incoming Calls supplementary

service
BAOC
Barring of All Outgoing Calls supplementary

service
BCCH
Broadcast Control Channel
BCTL
Back Control
BCSN
Backplane of Circuit Switch Network
BDT
Back Digital Trunk
BCTC
Backplane of Control Center
BFBI
Back Fiber Bus Interface
BHCA
Busy hour Calling Attempt
BIC-Roam
Barring of Incoming Calls when Roaming outside

the home PLMN country supplementary service
BNET
Back Network
BO
all Barring of Outgoing call supplementary services
BOIC
Barring of Outgoing International Calls

supplementary service
225
Abbreviations
Full Name
BOIC-exHC
Barring of Outgoing International Calls except

those directed to the home PLMN Country
BPSN
Backplane of Packet Switch Network
BS
Basic Service (group)
BS
Bearer Service
BSG
Basic Service Group
BTS
Base Transceiver Station
BUSN
Backplane of Universal Switch Network
C
CAI
Charge Advice Information
CB
Cell Broadcast
CBC
Cell Broadcast Centre
CBCH
Cell Broadcast Channel
CBK
Clear Back signal
CC
Country Code
Call Control
CCF
Conditional Call Forwarding
CCITT
The International Telegraph and Telephone

Consultative Committee
Cct
Circuit
CF
all Call Forwarding services
CFB
Call Forwarding on mobile subscriber Busy

CFNRc
Call Forwarding on mobile subscriber Not

Reachable supplementary service
CFNRy
Call Forwarding on No Reply supplementary

service
CFU
Call Forwarding Unconditional supplementary

service
CG
Charging Gateway
CGC
Circuit Group Congestion signal
CI
Cell Identity
CUG Index
226
CLKG
CLOCK Generator
CLKI
CLOCK Interface
CLI
Calling Line Identity
CLIP
Calling Line Identification Presentation

Abbreviations
Abbreviations
Full Name
CLIR
Calling Line Identification Restriction

CM
Connection Management
CMD
Command
CMP
Control Main Processor
COLI
Connected Line Identity
COLP
Connected Line identification Presentation

COLR
Connected Line identification Restriction

D
DTB
Digital Trunk Board
G
COLP
Connected Line identification Presentation

GLI
GE Line Interface
GERAN
GSM Enhanced Radio Access Network
I
IMAB
IMA Board
IPB
IP Process Board
IPI
IP bearer Interface
IWFB
IWF Board
M
MNIC
Multi-service Network Interface Card
MONB
Monitor Board
MPB
Main Process Board
MRB
Media Resource Board
O
OMP
Operation Main Processor
P
PLI
POS Line Interface
PSN
Packet Switch Network
PWRD
POWER Distributor
S
SDHB
SDH Board
SDTB
Sonnet Digital Trunk Board
SDU
Selection and Distribution Unit
SMP
Signal Main Processor
227
Abbreviations
Full Name
SPB
Signaling Process Board
T
TFI
TDM Fiber Interface
TSNB
TDM Switch Network Board
U
UIM
Universal Interface Module
V
VTC
228
Voice Trancoder Card
Glossary
3G
3G refers to next generation of mobile communication systems.

These offer enhanced services, such as multimedia and video.
Main 3G technologies include UMTS and CDMA2000.
3GPP
3GPP was formed in December 1998 as a collaboration

agreement bringing together a number of telecommunication
standards bodies. These standards bodies are referred to as
Organizational Partners. Aim of 3GPP was to produce globally
applicable technical specifications for third generation mobile
systems based on evolved GSM Core Networks and the radio
access technology Universal Terrestrial Radio Access (UTRAN).
3GPP2
3GPP2 is a sister project to 3GPP and is a collaboration

agreement regarding third generation mobile networks. It is
comprised of five Standards Development Organizations similar
to Organizational Partners in 3GPP. 3GPP2 mainly deals with the
following five areas: A-interface system, CDMA2000, American
National Standards Institute-41 (ANSI-41), wireless packet data
inter-working, and services & systems aspects.
Access Point
An Access Point is a network device which provides the point of

interconnection between wireless station (laptop computer, PDA)
and wired network.
Bearer Service
Bearer Service is a type of telecommunication service that
provides the capability for transmission of signals between

access points.
Broadband
Broadband in radio systems identifies a type of communication

channel capable of carrying a large portion of electromagnetic
spectrum. It may also be applied to fixed communication
systems when referring to bearers capable of carrying high
volumes of traffic.
FTP
A client server application protocol using well known ports 20

and 21. It uses the services of Transmission Control Protocol
(TCP) to provide reliability in the transfer of data files between
network nodes. FTP was first defined as a standard in Request
for Comments (RFC 959).
GE
Gigabit Ethernet (GE) is the Ethernet standard offering Gigabit

services and typically employs fibre. This technology has been
used for backbone networks and desktops for high end servers
and intensive graphical applications.
229
230
Handoff or
Handover
A Handoff, or Handover, is the process in which a cellular phone

is handed from one cell to the next in order to maintain a radio
connection with the network
IMEI
International Mobile Equipment Identity is a unique identifier

allocated to each Mobile Equipment (ME). It consists of a Type
Approval Code (TAC), a Final Assembly Code, Serial Number
(SNR) and a Spare Digit.
IMSI
International Mobile Subscriber Identity is a unique identifier

allocated to each mobile subscriber in a GSM and UMTS network.
It consists of a Mobile Country Code (MCC), a Mobile Network
Code (MNC) and a Mobile Station Identification Number (MSIN).
ISUP
ISDN User Part is part of the SS7 protocol layer and used in
setting up, management, and release of trunks that carry voice
and data between calling and called parties.
Iu-CS
This is the interface in UMTS which links the Radio Network

Controller with MSC Server.
Iu-PS
This is the interface in UMTS which links the RNC with SGSN.
LAI
Location Area Identity uniquely identifies a Location Area (LA)

within any Public Land Mobile Network (PLMN). It is comprised of
the Mobile Country Code (MCC), Mobile Network Code (MNC)
and the Location Area Code (LAC).
MAC Address
MAC address refers to hardware address and uniquely identifies

a device within a defined network area.
MSISDN
Mobile Station ISDN (MSISDN) Number is the standard

international telephone number used to identify a given
subscriber.
MSISDN
is
based
on
the
International
Telecommunications Union-Telecommunication Standardization
Sector (ITU-T) E.164 standard.
MSRN
Mobile Station Roaming Number is an E.164 defined telephone

number used to route telephone calls in a mobile network from a
Gateway Mobile Switching Centre (GMSC) to the target MSC.
MTP
Message Transfer Part forms part of the SS7 protocol stack and
provides reliable routing usually within a network.
Network
Management
A set of procedures, software, equipment etc in order to keep a

network operating in an efficient manner. ITU-T have developed
a series of standards for Network Management which are
referred to as the Telecommunication Management Network
(TMN). This sub-divides Network Management into the following
five categories; Fault, Configuration, Performance, Accounting
and Security.
Node B
Node B is the function within the UMTS network that provides

physical radio link between User Equipment (UE) and the
network.
Physical
Channel
A physical channel supports physical media, usually in an

encoded format. This may be pulses of light, a modulated
voltage or radio waves.
Glossary
Protocol Stack
Conceptual model of layered architecture of communication

protocols in which, layers within a station are represented in
hierarchical order. Each layer in the protocol stack is defined in
generic terms describing functionality and mode of operation.
QoS
Performance of a communications channel or system is usually

expressed in terms of Quality of Service (QoS). Depending upon
the communication system, QoS may relate to service
performance, Signal to Noise Ratio (SNR), Bit Error Ratio (BER),
maximum and mean throughput rate, reliably, priority and other
factors specific to each service.
Radio Access
Network
Radio Access Network (RAN) performs the radio functionality of

network, as well providing connection to Core Network. RAN
typically includes a controller Radio Network Controller (RNC) in
3GPP and BSC in 3GPP2 and several transmitter/receivers Node
B in 3GPP, BTS in 3GPP2.
RANAP
Radio Access Network Application Part (RANAP) is used in a

UMTS system on the Iu interface. It is responsible for function
including setting up of a Radio Access Bearer (RAB) between the
Core Network and RNC.
SCCP
Signalling Connection Control Part is used to provide a means for

the transfer of messages between any two signalling points in
the same or different SS7 networks.
SCTP
Streaming Control Transmission Protocol (SCTP) is a reliable

transport protocol operating on top of IP. It provides
acknowledged error free non duplicated transfer of data. STCP
also detects data corruption, loss of data and duplication of data
by using checksums and sequence numbers.
Signaling
Gateway
A Signaling Gateway is used to support the transport of

signalling traffic received from one network and passed into
another network.
TMSI
In order to ensure subscriber identity confidentiality VLR and

SGSN may allocate Temporary Mobile Subscriber Identities
(TMSI) to visiting mobile subscribers. VLR and SGSN must be
capable of correlating an allocated TMSI with IMSI of MS to
which it is allocated. A MS may be allocated two TMSI, one for
services provided through VLR, and the other known as the
Packet TMSI (P-TMSI) services provided through the SGSN.
TUP
Telephone User Part was an earlier implementation of SS7 that

did not allow for data type applications, hence the introduction
of ISDN User Part (ISUP).
UMTS
A 3G mobile communications system which provides an

enhanced range of multimedia services. UMTS will speed
convergence between telecommunications, IT, media and
content industries to deliver new services and create fresh
revenue generating opportunities. UMTS will deliver low cost,
high capacity mobile communications offering data rates as high
as 2Mbps under stationary conditions with global roaming and
other advanced capabilities. The specifications defining UMTS
are formulated by 3GPP.
231
232
VCI
The identifier in ATM cell header that identifies to which virtual

channel the cell belongs.
WAP
A standard designed to allow the content of Internet to be

viewed on the screen of a mobile device such as mobile phones,
personal organisers and pagers. WAP also overcomes the
processing limitation of such devices. Information and services
available are stripped down to their basic text format.
Tables
Table 1 Chapter Summary ................................................... ii
Table 2 Typographical Conventions ....................................... ii
Table 3 Mouse Operation Conventions .................................. iii
Table 4 Summary of Alarm Messages ....................................2
Table 5 Summary of Notification messages ........................ 142
233
234
Index
active status....... 119, 183, 184
Alarm
Alarm management ....... 181
authentication .... 149, 210, 213
Backplane ................. 225, 226
Clock running mode
free ............................. 231
trace ........................... 104
Congestion....................... 226
Control plane...................... 30
Data configuration..... 123, 162,
164, 182
data synchronization ......... 163
DIP Switch ....................... 160
Equipment commissioning
process
Cutover........................ 109
Handover ..................... 230
FTP ................................. 229
Instance ................... 149, 216
IP address... 92, 127, 129, 130,
197, 199, 202, 204, 206,
207, 208
label......................... 105, 111
link ... 4, 11, 26, 27, 31, 32, 33,
35, 36, 37, 39, 40, 41, 42,
43, 45, 46, 47, 48, 49, 55,
56, 57, 61, 63, 64, 65, 66,
70, 82, 122, 124, 174, 186,
211, 212, 213, 230
signaling link ...........53, 188
M3UA ................................ 50
MAC address180, 203, 209, 230
MAC configuration ............. 204
mask................. 130, 199, 207
MP 2, 3, 4, 5, 6, 7, 8, 9, 10, 11,
12, 13, 14, 15, 16, 17, 18,
19, 20, 21, 22, 23, 24, 25,
26, 27, 28, 29, 30, 31, 32,
33, 34, 35, 36, 37, 38, 39,

40, 41, 42, 43, 44, 45, 46,
47, 48, 49, 50, 51, 52, 53,
54, 55, 57, 59, 60, 61, 62,
63, 64, 65, 66, 68, 69,
70, 71, 72, 73, 74, 75, 76,
77, 78, 79, 80, 81, 82, 83,
84, 85, 86, 87, 88, 89, 90,
91, 92, 93, 94, 95, 96, 97,
98, 99, 100, 101, 102, 103,
104, 105, 106, 107, 108,
109, 110, 111, 112, 113,
114, 115, 116, 117, 118,
123, 124, 125, 126, 127,
128, 129, 130, 131, 132,
133, 134, 135, 136, 137,
142, 143, 144, 145, 146,
147, 148, 149, 150, 151,
162, 163, 179, 182, 183
MTP ................................ 230
MTP3 ..................6, 46, 47, 49
Office
local office ................. 1, 93
Office No...................... 126
Performance
Performance alarm .....67, 68
Performance statistics.67, 68
Phase
Phase-locked .................. 79
Physical configuration ........ 124
Power on ... 141, 155, 157, 164,
180
Prefix ....................... 148, 207
Remains ..................... 14, 119
Server
OMC server ...............31, 32
signaling point........... 186, 188
switchover ....83, 152, 156, 178
235

ZXWN MGW Alarm and Notification Information PDF

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

ZXWN MGW Alarm and Notification Information PDF

Încărcat de

Drepturi de autor:

Formate disponibile

ZXWN MGW

Alarm and Notification Information

Reason for Issue

July 20, 2008

ZXWN MGW Media Gateway Alarm and Notification Information

Make it more concise/brief

Improve the Contents

Add more step-by-step procedures/tutorials

Improve the organization

Add more troubleshooting information

Include more figures

Make it less technical

Add more examples

Add more/better quick reference aids

Add more detail

Improve the index

This page is intentionally blank.

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

Trunk Frame Loss................................................................27

SUA SSN Is Invalid ............................................................. 51

QoS Alarm ................................................................... 60

Equipment Alarm .......................................................... 69

IDE Initialize Fail .................................................................72

Clock Reference Source Lost (Level 1 Alarm) .......................... 91

SDH/SONET: LP-RFI/Virtual Tributary-RFI............................. 108

OMS Alarm................................................................. 118

Processing Alarm ........................................................ 123

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

Chapter 2...................................................................... 141

One of CPUs on One of Boards in This Shelf Resets Exceptionally

NID Translation Failure ...................................................... 165

VSC872 Configuration Failure.............................................. 177

SIG_IPI Forwards Service Messages Abnormally .................... 192

RIP Interface Authentication Errors ...................................... 210

Abbreviations ............................................................... 225

This page is intentionally blank.

About This Manual

Confidential and Proprietary Information of ZTE CORPORATION

ZXWN MGW Media Gateway Alarm and Notification Information

Prerequisite Skill and Knowledge

ZXWN MGW system and its various components

User interfaces on the ZXWN MGW

ZXWN MGW operating procedures

What Is in This Manual

Introduces the alarm information that may

Introduces the notification information that

ZTE documents employ the following typographical conventions.

References to other Manuals and documents.

Menus, menu options, function names, input

Keys on the keyboard and buttons on screens

Text that you type, program code, files and

Select one of the parameters that are delimited

Confidential and Proprietary Information of ZTE CORPORATION

About This Manual

TABLE 3 MOUSE OPERATION CONVENTIONS

Refers to clicking the primary mouse button (usually

Refers to quickly clicking the primary mouse button

Refers to clicking the secondary mouse button

Refers to pressing and holding a mouse button and

How to Get in Touch

If you have problems, questions, comments, or suggestions

Confidential and Proprietary Information of ZTE CORPORATION