Dokumen - Tips Zte RNC Alarm and Notification Handling Reference

ZXWR RNC
Radio Network Controller

Alarm and Notifica-
tion Handling Reference
Version 3.09.30
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: (86) 755 26771900
Fax: (86) 755 26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2010 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution of
this document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPO-
RATION 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 dis-
claimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-in-
fringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on the
information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subject
matter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee,
the user of this document shall not acquire any license to the subject matter herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason

R1.0 20100609 First Edition (V3.09.30.03)
R2.0 20100915 Second Edition (V3.09.30.06)
Add new alarm and Notification: 198002625,
198002880, 198003841, 198005189, 198005403,
198005404, 198005405, 198005669, 198005718,
198005893, 198015168, 198020805, 198020806,
198026176, 198029952, 198029953, 198066066,
198066067, 198066068, 198066071, 198083042,
198083043, 198083044 and 198083045
Delete alarm and Notification: 198083031
Update alarm and Notification: 198000256,
198001286, 198005121, 198005121, 198005122,
198005126, 198005645, 198005646, 198005649,
198018243, 198018944, 198023106, 198025861,
198066064, 198083003, 198083025, 198083029,
198083032, 198083033, 198083039, 198083040,
198000002, 198000576, 198001026, 198001284,
198001600, 198001792, 198003394, 198003395,
198005122, 198005389, 198005390, 198005396,
198005398, 198005448, 198005663, 198005667,
198005711, 198015617, 198018944, 198019207,
198019712, 198019713, 198019714, 198019777,
198020802, 198020803, 198025602, 198025856,
198025857, 198025860, 198025861, 198025862,
198025863, 198025866, 198025868, 198026118,
198066010, 198066011, 198066014, 198066047,
198066048, 198066049, 198066050, 198066064,
198070003, 198070004, 198070005, 198070008,
198070009, 198070010, 198070011, 198083003,
198083017, 198083020, 198083021, 198083022,
198083023, 198083025, 198083027, 198083028
and 198083029
Serial Number: SJ-20100603155704-004
This page is intentionally blank.
Contents
About This Manual............................................. I

Overview ...........................................................1
Overview of Fault Management......................................... 1
Fault View ..................................................................... 1
Alarm ....................................................................... 1
Notification ................................................................ 2
Alarm ........................................................................... 2
Alarm Property........................................................... 2
Alarm Code ....................................................... 2
Description........................................................ 2
Severity............................................................ 2
Alarm Type........................................................ 3
Probable Cause .......................................................... 3
System Impact........................................................... 3
Handling Suggestion ................................................... 4
Notification .................................................................... 4
Notification Property ................................................... 4
Notification Code................................................ 4
Description........................................................ 4
Importance ....................................................... 4
Notification Type ................................................ 4
Probable Cause .......................................................... 5
System Impact........................................................... 5
Handling Suggestion ................................................... 5
Alarm ................................................................7
Equipment Alarm............................................................ 7
198083003 Log server unavailable................................ 7
198083022 Cell is out of service ................................... 8
198083023 Node B out-of-service alarm .......................10
198083027 RSVB board offline alarm ...........................11
198019456 HSSLS are all out of synchronization ...........11
Confidential and Proprietary Information of ZTE CORPORATION I

ZXWR RNC Alarm and Notification Handling Reference
198019465 CSIX RX and TX packets is abnormal ...........12

198005633 Hard Disk Broken......................................12
198005635 The board is not plugged firmly ..................13
198005639 High Error Rate of Optical Interface ............14
198005640 FPGA Exception ........................................14
198005644 The Channel in a Subcard Is Down ..............15
198005645 Subcard Abnormal ...................................15
198005646 Phase-locked Loop Unlocked.......................16
198005647 High Error Rate at E1 Bottom Layer ............17
198005656 Loss of Clock When Input to Sub-card .........18
198005663 M28529 chip failure on board IMAB or DTA
affecting services...............................................18
198066044 Fault on Board (GPS) ................................19
198001284 The phase of 8K, 16K clock, input to
backplane board, is not matched .........................20
198001286 Input clock of board lost ............................21
198000002 Loss of optical signal .................................21
198015874 Physical channel for data transmission
blocked ............................................................22
198015875 GLI table lookup failed...............................23
198015876 GLI exception packets statistic over
threshold..........................................................23
198002560 The usage of CPU is over the threshold .........24
198002561 CPU temperature over threshold .................24
198005376 Internal Port of Board Is Down....................25
198066070 Board Doesn't Exist/ CPU is in Reset Status
for a Long Time .................................................26
198005381 Input clock is abnormal .............................27
198005389 CPU sub card in position is not configured
in the database. ................................................27
198005390 CPU sub card is missing from slot but is
configured in database .......................................28
198005395 External Port of Board Is Down ...................28
198005399 DSP resource is unavailable........................29
198026116 CLKG PP2S Output Clock Lost ....................30
198026117 PP2S clock reference lost ...........................30
198026118 16CHIP clock reference lost ........................31
198026127 Clock reference source lost (Level 3 alarm)
.......................................................................31
II Confidential and Proprietary Information of ZTE CORPORATION

.......................................................................32
.......................................................................32
198026131 CLKG board PLL out-of-lock .......................33
198026133 Output clock lost.......................................34
198005632 Usage rate of board hard disk above
threshold .........................................................34
198005637 Error in Rear Board That Mismatches With
Front Board ......................................................35
198005661 Physical link down between master/slave
media interactive ports.......................................35
198005662 IDE running overtime ................................36
198005667 E1 is looped back......................................36
198005671 Incorrect FE Routing Connection .................37
198005668 Self board has cross-linked E1 ....................38
198005655 DSP Reports Exceptions After
Detection .........................................................38
198005124 Capacity of intra-shelf control plane TRUNK
communication is insufficient...............................39
198005125 Incorrect Connection of GE Optical
Transceiver Module ...........................................40
198025602 TDM switch abnormal ................................40
198029952 802.3ah link fault .....................................41
198005669 Synchronization status check of FPGA
failed ...............................................................42
198005893 Memory check failed..................................42
198005403 Board SRAM self-check fails .......................43
198005404 Board OCXO oven fault ..............................43
198005405 Clock board phase-lock loop work mode
abnormal..........................................................43
Communication Alarm ....................................................44
198000256 Ethernet physical link broken......................44
198083021 CCP transmission link fault .........................45
198001792 SDH/SONET fault ......................................45
198083036 DSAR Alarm .............................................47
198083038 Transport Path group Occupied Bandwidth
Overload ..........................................................48
198083039 IP channel of Iub interface is faulty .............48
Confidential and Proprietary Information of ZTE CORPORATION III

198083040 TCP connect on IuBC interface is

interrupted ......................................................49
198022784 BFD Session Interrupted ............................49
198066029 PPP link broken.........................................51
198018944 PVC link is down. ......................................52
198019213 LIF Alarm of Near-End Receiving Link ..........53
198019214 LODS Alarm of Near-End Receiving Link
.......................................................................54
198019215 RDI alarm of far end receiving link ..............55
198019223 Ne Group is in fault state ...........................55
198066026 Association path broken.............................56
198005666 The number of the error packets from MAC
port exceeds the threshold..................................57
198066045 Trunk error ..............................................57
198066046 Trunk abnormal ........................................58
198066047 Abnormal status in SDH/SONET ..................59
198066048 SDH/SONET Excessive Error Code ..............63
198001026 Loss of ATM Cell Synchronization over E1
Link ................................................................64
198066049 ATM link is down ......................................65
198015617 Frames Received by
FE/GE/ATM/MP/POS/E1 Port are faulty. .................66
198015873 Faulty frames received by internal
switching interface.............................................66
198005378 Board HW Error ........................................67
198005651 IPMAC conflict when OSS detects control
plane ...............................................................68
198066003 Control plane communication is abnormal
between board and its home module ....................69
198066004 Control plane communication is abnormal
between MP and OMP .........................................69
198005382 Communication between power board and
OMP board is abnormal ......................................70
198005396 Exceptional communication on UIM board
or back plane ...................................................70
198005397 Communication of RAWMACIP channel is
abnormal..........................................................71
198005401 Test packet check abnormal .......................72
198005121 Inter-shelf media plane links abnormal .........73
IV Confidential and Proprietary Information of ZTE CORPORATION

198005122 Loss of Active/standby communication
link..................................................................74
198066060 FE Link Error Alarm ...................................74
198005128 Duplicate rack and shelf.............................75
198066005 SCCP subsystem unavailable .....................75
198066007 Broadband link overload ............................76
198066010 RNC unable to connect to MTP3 office ..........77
198066011 MTP3 link unavailable ................................77
198066014 RNC unable to connect to M3UA office .........78
198066019 Association link broken ..............................79
198029953 The Ethernet port state is OAM loop back
.......................................................................80
198003841 The control plane retransfer ratio over the
threshold..........................................................80
198083045 Common Channel setup failed Alarm ...........81
198066071 Link broken for board fault .........................82
198066066 AAL2 Path locally blocked...........................82
198066067 AAL2 Path remotely blocked .......................83
198066068 AAL2 Path blocked by broken PVC ...............83
Processing Alarm ...........................................................84
198083020 RNC system resources limits reached, no
new UE's can attach to the network ....................84
198083024 GPS receiver on ICM is abnormal ................84
198019207 Near-End IMA Group Configuration
Failure .............................................................85
198015360 Microcode Is Abnormal ..............................85
198023040 The number of board alarms exceeds the
threshold..........................................................86
198066031 The number of OMP alarms exceeds the
threshold..........................................................86
198066032 NTP time exceeds threshold .......................87
198066027 SNTP failure .............................................87
198005387 Alarm Due to Inconsistent MP Type .............88
198005388 Startup File Does Not Exist.........................89
198005398 Office ID is not set correctly with control
shelf. ..............................................................89
198066057 Database config is different from file
named bootcfg ini. .............................................90
198005649 Port working mode doesn't match with its
setting. ............................................................90
Confidential and Proprietary Information of ZTE CORPORATION V

198005123 DB Configuration Doesn't Fit for Device .........92

198005126 Incorrect FE Routing Connection .................92
198066006 Broadband link congestion ........................93
198066013 MTP3 link congestion .................................94
198066018 Association congestion...............................95
198019712 loss of protection switching ........................95
198019713 loss of protection switching ........................96
198019714 APS configuration alarm. ..........................97
Environment Alarm ........................................................98
198025856 Rack temperature is high. ..........................98
198025857 Low temperature in Rack ...........................99
198025858 House temperature is higher than high
threshold .........................................................99
198025859 House temperature is lower than low
threshold ....................................................... 100
198025860 Rack voltage is high ............................... 100
198025861 rack voltage is low .................................. 101
198025862 Humidity is high .................................... 102
198025863 Humidity is low....................................... 102
198025864 Fault in fan plug-in box ........................... 103
198025865 Rack door alarm ..................................... 103
198025866 Smoke detected...................................... 104
198025867 Infrared alarm ........................................ 104
198025868 Lightning alarm ...................................... 105
198066064 Loss of DC power supply to rack ............... 105
QoS Alarm.................................................................. 106
198023296 Inter-board message communication flow
rate exceeds the alarm threshold ....................... 106
198066069 The number of times of signaling data
transfer exceeds the allowed threshold of the
license ........................................................... 106
198083042 IU PS traffic over load alarm..................... 107
198083043 IU CS traffic over load alarm .................... 107
198083044 IU traffic over load alarm ......................... 108
Notification ................................................... 109
198083017 RUB board has reached maximum number of
routes ................................................................ 111
198070002 Iu interface global reset notification............... 111
198070003 Iu interface resource reset notification ........... 112
VI Confidential and Proprietary Information of ZTE CORPORATION

198070004 RNC initiate Iu interface global reset failure
notification ......................................................... 113
198070005 RNC initiate Iu interface resource reset failure
notification ......................................................... 113
198070008 RNC and Node B are configured with different
CCPID ................................................................ 114
198070009 Broadcast failure......................................... 114
198083025 Common Channel is abnormal ...................... 116
198070010 FTP failure and file lost ................................ 117
198070011 RNC alarm storage disc is full ....................... 118
198083028 Performance file server unavailable ............... 118
198083029 Unable to save Performance File ................... 119
198083019 MicroCode subsystem failed to get the table
of configuration ................................................... 120
198083026 MicroCode subsystem failed to handle DHCP
message from other network................................. 122
198083030 Bandwidth automatic adjustment is
useless............................................................... 123
198083032 TCP connect on IuBC interface is interrupted
......................................................................... 124
198083033 The deviation of slave clock is too large. ......... 125
198083034 External Clock of Slave lost notification .......... 125
198083035 Transport Path Occupied BandWidth
Overload ............................................................ 126
198083037 All Local Cell ID configured at RNC side are
differ from which on Node B side ........................... 126
198020291 Protocol stack process failed to initialize
during power on .................................................. 127
198020802 Conflicting IP address in subnet. .................. 127
198020803 Conflicting MAC Addresses in Subnet ............. 128
198020804 Failed to generate static ARP from IP
address .............................................................. 129
198066065 SCTP Primary Path Set Failed........................ 130
198030016 Ethernet link OAM event .............................. 130
198000576 Loss of Frame on Trunk ............................... 131
198066050 MCC is faulty.............................................. 131
198001600 CPU resets on a board ................................. 132
198017216 Error in MCS Multi-Core processor receiving
configuration data from DBS ................................. 132
198018240 TCP Receives RST Packet ............................. 133
Confidential and Proprietary Information of ZTE CORPORATION VII

198018241 TCP Connection Aborted .............................. 133

198018242 MD5 Verification Failure ............................... 134
198018243 Wrong MD5 Message Abstract....................... 134
198023106 Board Self-Check Failure .............................. 135
198023107 The board initialization failure....................... 135
198023617 Configuration file is unusable........................ 136
198003138 FLASH device initialize failed ........................ 136
198003394 Start daylight saving time ............................ 137
198003395 End daylight saving time.............................. 137
198005441 Port status on internal media plane
changed. ............................................................ 138
198005448 485 seriel bus link between CLKG/PWRD and
OMP is broken. .................................................... 139
198026177 CLKG reference quality changed ................... 139
198026178 Clock work mode changed............................ 140
198005705 MCU resets for abnormities .......................... 140
198005710 The result of base selection of sets chip ......... 140
198005711 clock reference selection is being
executed. ........................................................... 141
198005712 The manual select base will be run, please
wait for the result ................................................ 141
198005713 APC's RAM error ......................................... 142
198005715 PP2S source switched .................................. 142
198005717 The physical address information of the board
is incorrect ......................................................... 143
198005716 Type B fault on board (GPS) phase-lock
equipment .......................................................... 143
198005700 DSP resets for abnormities ........................... 144
198005701 Version Load Error ...................................... 145
198019777 APS switch over occurred ............................. 146
198005188 UIM CS Changeover .................................... 147
198005192 Board's Work Mode Unsupported................... 148
198005193 Notification of the power-on status of the
basic process ...................................................... 148
198005956 Board Version Error..................................... 149
198005958 IDE Version Files Synchronization
Information ........................................................ 150
198005961 OMP Version Check Information .................... 150
198005962 Patch version operate fail ............................. 151
VIII Confidential and Proprietary Information of ZTE CORPORATION

198010560 No message response in the link for a long
time .................................................................. 152
198011840 M3UA user office status change .................... 152
198013888 ASP status changed .................................... 153
198013889 AS status changed ...................................... 154
198013890 Sigtran error message received .................... 154
198013891 Sigtran notification message received ............ 155
198013892 Allocate memory fail ................................... 156
198014144 Association establishment failed.................... 156
198014145 Association restart ...................................... 157
198025664 Abnormal Half-fixed Connection
Changes............................................................. 158
198008005 Memory file buffer overflow .......................... 159
198002625 Process is deadlocked .................................. 159
198002880 CPU occurs dead-loop.................................. 160
198005718 Two master clock ports is directly
connected........................................................... 160
198005189 Notification of Active/Standby
Changeover ........................................................ 161
198026176 Clock reference changed .............................. 161
198020805 ARP detect failed ........................................ 162
198020806 ARP detect that the static ARP is not
match ................................................................ 162
198015168 AAL2 Path blocked by resetting process ......... 163
Figures .......................................................... 165
Tables ........................................................... 167
Confidential and Proprietary Information of ZTE CORPORATION IX

X Confidential and Proprietary Information of ZTE CORPORATION

About This Manual
Purpose At first, thank you for choosing ZTE UMTS RAN of ZTE Corporation!
ZXWR RNC, the new generation radio network controller of ZTE
UMTS V3 series products, performs functions of system access
control, security mode control, mobility management, and radio
resource management and control, etc.
ZXWR RNC provides all the functions defined in the 3GPP
R99/R4/R5/R6/R7 protocol, and offers Iu, Iub, and Iur series
standard interfaces.
ZXWR RNC is based on ZTE all IP unified hardware platform, uti-
lizes distributed design, supports ATM/IP dual protocol stack and
can smoothly evolve to IP UTRAN. It aims at saving operator’s in-
vestment in 3G network construction by offering a large capacity
and linear expandable system once and for all.
This manual introduces the alarms that might occur during the
installation, operation and maintenance of the ZXWR RNC product.
Intended This guide is intended for engineers and technicians who perform
Audience operational activities on ZXWR RNC.
Prerequisite Skill To use this guide effectively, users should have a general under-
and Knowledge standing of telecommunications technology. Familiarity with the
following is helpful:
� ZXWR RNC system and its various components
� User interfaces on the ZXWR RNC system
� Local operating procedures of the ZXWR RNC system
What is in This
Manual Chapter Summary
Chapter 1, Overview Introduces the concept of fault

management, as well as the definition,
type, level classification of alarm and
notification.
Chapter 2, Alarm Introduces RNC alarms with respect to

alarm property, probable cause, system
impact, and handling suggestion.
Chapter 3, Notification Introduces RNC notifications with respect

to notification property, probable cause,
system impact, and handling suggestion.
FCC Compliance This device complies with part 15 of the FCC Rules. Operation is
Statement subject to the following two conditions.
1. This device may not cause harmful interference.
2. This device must accept any interference received, including
interference that may cause undesired operation.
Confidential and Proprietary Information of ZTE CORPORATION I

Changes or modifications not expressly approved by the party re-

sponsible for compliance could void the user's authority to operate
the equipment.
II Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1
Overview
Table of Contents
Overview of Fault Management............................................. 1
Fault View ......................................................................... 1
Alarm ............................................................................... 2
Notification ........................................................................ 4
Overview of Fault
Management
Fault management is responsible for collecting information of fail-
ures and events that occur during system operation or service pro-
cessing.
The information, in the form of alarm or notification, is stored in
database or displayed on realtime basis via a user-oriented fault
monitoring platform. Means such as visual-interface monitor or
history information query can be used to view current or histor-
ical system operation and service processing status. Fault man-
agement enables maintenance personnel to troubleshoot and take
preventive measures to remove potential fault and restore system
and services as early as possible.
Fault View
Fault is displayed in the form of alarm or notification.
Alarm
The fault that persists during system operation and affects system
reliability and normal services is referred to as an alarm. Alarm
usually lasts until fault removal.
Due to its possible impact on normal system operation, alarm re-
quires timely troubleshooting in which alarm cause is identified,
and the fault is located and handled.
Confidential and Proprietary Information of ZTE CORPORATION 1

Notification
Notification refers to the non-repeated/instantaneous fault or
event that occurs during system operation. Examples include
board reset, signaling overload, etc.
Notification is mostly caused by sudden environment change
or other accidental factors. No special handling is required for
the notification, which can be automatically removed by the
system. Only the notification that occurs persistently requires
troubleshooting.
Alarm
Alarm Property
Alarm Code
Alarm code is the identifier which differentiates alarms.
Alarm code is defined by a 32-bit field indicating the specific code
value.
Description
Alarm description reflects such content as fault cause and fault
phenomenon in a simple and straightforward way.
Severity
There are four alarm levels, which are indicated in descending or-
der of severity as Critical, Major, Minor, and Warning.
� Critical alarm causes system breakdown and service interrup-
tion. It requires immediate troubleshooting.
� Major alarm significantly affects system operation or weakens
network service capability. It requires troubleshooting as soon
as possible.
� Minor alarm affects system operation and network service
capability in a nonsignificant way. It requires timely trou-
bleshooting so as to avoid severity escalation.
� Warning poses a potential hazard to system operation and net-
work service capability. It requires troubleshooting at an ap-
propriate time so as to avoid severity escalation.
2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Overview
The degree of impact as described in the definition of alarm sever-

ity refers to the impact of a single index, such as reliability and
security. Once the impact on any of the index reaches the speci-
fied threshold, the severity level of the alarm can be roughly de-
termined. If an alarm has an impact on multiple indices, alarm
severity should be escalated accordingly.
Note:
Alarm severity can be modified in NetNumen M31 NMS (network
management system) if necessary.
Generally speaking, the default alarm severity is reasonably set.
Users should think twice before making any modification.
In addition, the severity of few alarms is undefined. It is up to

users to define the severity of such alarms.
Alarm Type
Alarm is classified into six types according to alarm trigger condi-
tion and its system impact.
� Equipment alarm: related with device hardware.
� Communication alarm: related with information transmission
(ITU-T Recommendation X.733).
� Processing alarm: related with software or process fault (ITU-T
Recommendation X.733).
� Environment alarm: related with the environment where the
equipment is located (ITU-T Recommendation X.733).
� QoS alarm: related with degradation of service quality (ITU-T
Recommendation X.733).
� OMS alarm: related with the network management system.
Probable Cause
Probable alarm causes are enumerated to help users troubleshoot,
find preventive measures, and restore the system to normal state
in a timely manner.
System Impact
System impact refers to the impact that the alarm incurs on sys-
tem or services.

Handling Suggestion
Troubleshooting measures and suggestions are provided.
Pay attention to the following tips when handling alarms.
� After recording the fault phenomenon, O&M personnel may
handle the fault step by step as described in the Handling Sug-
gestion Section of this manual. If the fault is removed (alarm
restored) at any handling step, terminate the handling process.
If the fault is not removed, go ahead to the next handling step.
� If the fault cannot be removed, contact the local ZTE office as
soon as possible.
Notification
Notification Property
Notification Code
Notification code is the identifier to differentiate notifications.
Notification code is defined by a 32-bit field indicating the specific
code value.
Description
Notification description reflects such content as fault cause and
fault phenomenon in a simple and straightforward way.
Importance
There are two levels of notification importance: Important and
Ordinary.
Notification Type
No notification type exists.

Chapter 1 Overview
Probable Cause
Probable notification causes are enumerated to help users trou-
bleshoot the system in a timely manner and take preventive mea-
sures to ensure stable system operation.
System Impact
System impact refers to the impact that the notification incurs on
system or services.
Handling Suggestion
Troubleshooting measures and suggestions are provided.
Pay attention to the following tips when handling notifications.
� After recording the fault phenomenon, O&M personnel may
handle the fault step by step as described in the Handling Sug-
gestion Section of this manual. If the fault is removed (alarm
restored) at any handling step, terminate the handling process.
If the fault is not removed, go ahead to the next handling step.
� If the fault cannot be removed, contact the local ZTE office as
soon as possible.


Chapter 2
Alarm
Table of Contents
Equipment Alarm................................................................ 7
Communication Alarm ........................................................44
Processing Alarm...............................................................84
Environment Alarm ............................................................98
QoS Alarm...................................................................... 106
Equipment Alarm
198083003 Log server unavailable
Alarm Type Equipment Alarm
Alarm Purpose External Alarm
Alarm Classifica- Alarm
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Log server is unavailable.
2. Break in communication between RNC and Log server.
Processing 1. Check the log server by performing the following steps to see
Suggestion if the control-plane communication is normal:
i. Open a terminal dialog box in the LINUX system.
ii. Enter the SHELL command "ping 128.0.31.1" to see if the ping
test is successful. If not, troubleshoot the control-plane commu-
nication.
2. Check the log server to see if the LogService runs normally.
If not, restart the LogService by running “/startsys” under the
“/home/zte/LogService/bin” directory.
Alarm Impact Log/performance files cannot be reported to the log server.

198083022 Cell is out of service

tion
Alarm Level Critical
Disaster Alarm Yes
Frequently Yes
Reported
Cause of Alarm 1. RRU faulty.
2. cell is blocked by user.
3. Cell ID is incorrect or deleted.
4. Node B or BTS restarted or down.
5. Node B Cell frequency is not consistent with RNC.
Processing View alarm details on the NMS Alarm Management interface to
Suggestion check the Alarm reason, which can help you easily find the corre-
sponding handling suggestions.
The handling suggestions for each alarm are as follows:
1. Alarm reason: Node B returns a message, indicating cell setup
failure.
1) Check the frequency points of the RNC and the Node B to see
if they are consistent with those of the local cell by following the
steps below:
Click Base Station Radio Resource Management > WCDMA Ra-
dio Resource Management > Baseband Resource Pool on the NMS
Configuration Management interface, and then select the local cell
to be viewed. Check Rx Frequency and Tx Frequency in "Local Cell
Basic Parameters" to see if they are consistent with those at the
RNC side. If not, modify the RNC or Node B configurations to make
them consistent.
2) Check if the Node B generates a "198084129 Board reboots
alarm" on the NMS Alarm Management interface. If yes, it indi-
cates that the Node B was started or its hardware was replaced or
added just now. In this case, wait until the Node B is powered on.
2. Alarm reason: The Cell Configuration Generation ID (CGID)
audited and reported by the Node B is zero.
1) The local cell is blocked.
Click Base Station Radio Resource Management > WCDMA Ra-
dio Resource Management > Baseband Resource Pool on the NMS
Configuration Management interface, and then select the cell to be
viewed. Check "Local Cell Status Parameters" to see its manage-
ment status. If the cell is blocked, unblock it.
2) Node B is blocked or faulty.
Check the status of the Node B on the Ground Resource Configu-
ration interface. If it is blocked, unblock the Node B. If the Node
B fails, the FS board may be faulty. In this case, check if any of

Chapter 2 Alarm
the following alarms occurs. If yes, follow the corresponding sug-

gestions to handle it.
198084117 Application software monitoring alarm
198084123 Board communication link is interrupted
198084107 Board parameter synchronization abnormality
3) The local cell is faulty.
Check the "Local Cell Status Parameters" interface. If the current
status is faulty, it indicates that the FS or the RTR board is faulty or
restarted. In this case, check if any of the following alarms occurs.
If yes, follow the corresponding suggestions to handle it.
198084129 Board reboots alarm
4) The baseband board is blocked.
Check the status of the BPC board. If the board is blocked, unblock
it.
5) The baseband board is faulty.
Check the status of the BPC board. If the status is faulty, check if
any of the following alarms occurs. If yes, follow the corresponding
suggestions to handle it.
198084129 Board reboots alarm
3. Alarm reason: There is a real-time cell blocking at the Node B
side.
Click Base Station Radio Resource Management > WCDMA Radio
Resource Management > Baseband Resource Pool On the NMS
Configuration Management interface, and then select the cell to
be viewed. If the cell is blocked, unblock it.
4. Alarm reason: The failure to update system message results in
cell deletion or creation.
Handle it according to the suggestions given for "198070009
Broadcast failure".
5. Alarm reason: The cell parameters configured at RNC side is
incorrect.
On NMS configuration management interface, select the RNC Wire-
less Resource Management > Service Cell, check the cell param-
eters as follows:
1) Cell Capability and Cell Reselect Parameters
2) Senior Parameters: Load Control, Balance Parameters, Accept
Control, HSPA Configure, Mbms Configure.
6. Local cell is blocked at Node B side.

On NMS configuration management interface, select the cell to be

viewed under Base Station Radio Resource Management > WCDMA
Radio Resource Management >Baseband Resource Pool. View the
Status in Local Cell Status Parameters. If the status is blocked,
unblock it.
7. For other alarm causes, the system will automatically recreate
cells. In this case, no manual operation is required.
Alarm Impact The cell is unavailable and inaccessible, providing no service.
198083023 Node B out-of-service

alarm
tion
Disaster Alarm Yes
Frequently Yes
Reported
Cause of Alarm 1. Transmission is faulty.
2. Node B is down.
Processing The handling suggestions are classified by transmission mode.
Suggestion
1. IP mode
Check the Alarm Management interface according to the associa-
tion ID to see if there is any of the following association-related
alarms. If yes, follow the corresponding suggestions to handle it.
198066018 Association congestion
198066019 Association link broken
2. ATM mode
1) Bottom layer transmission fault
Check to see if there is any of the following alarms. If yes, follow
the corresponding suggestions to handle it.
198001792 SDH/SONET fault
198066047 Abnormal status in SDH/SONET
198066048 SDH/SONET: Excessive Error Code
198005639 High Error Rate of Optical Interface
2) Unavailable PVC link
Check to see if the following alarm exists. If yes, follow the corre-
sponding suggestions to handle it.
198018944 PVC Fault
Alarm Impact The Node B is unavailable and inaccessible, providing no service.

Chapter 2 Alarm
198083027 RSVB board offline alarm

tion
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. RSVB board is not plugged into shelf.
2. RSVB board is faulty.
3. RSVB board is not firmly inserted into slot.
Processing 1. Check if the RSVB is extracted.
Suggestion
If yes, insert the RSVB into the rear slot again.
If not, extract and insert the RSVB.
2. Replace the RSVB.
Alarm Impact If the SBCX to which the RSVB corresponds acts as a log server,
the OMM cannot obtain performance data from the log server.
198019456 HSSLS are all out of

synchronization
tion
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. The PSN board type configured does not accord with the PSN
board type actually in use.
2. PSN board hardware (VSC882 chip) is faulty.
3. Line card hardware (VSC872/VSC874 chip) is faulty.
Processing 1. Check whether PSN board reboots repeatedly. If yes, Check
Suggestion whether the PSN board type configured is consistent with the PSN
board type actually in use.
1) If inconsistent (for example, the configured board type is PSN4V
and the board type actually in use is PSN8V), modify board type
configuration or replace the board actually in use to keep consis-
tency between board configuration and the board in use.

2) If consistent, PSN board hardware might be faulty. In this case,

replace PSN board.
2. If the alarm occurs in line card, check if the same alarm occurs
in other line card(s) located in the same shelf with the faulty line
card.
1) If the same alarm occurs in all other line cards, PSN board might
be faulty. Reboot PSN board and check if the line card alarms are
restored. If alarms are not restored, replace PSN board.
2) If merely the line card where this alarm occurs reboots repeat-
edly, replace the board where the alarm is generated.
Alarm Impact 1. All services on the equipment are down if the alarm is caused
by Cause 1 or Cause 2.
2. All services on the line card are affected if the alarm is caused
by Cause
3. If the service is not configured in master/slave or load sharing
mode, all services on the line card will be down. If the service is
configured in master/slave or load sharing mode, all services on
the line card will soon be restored after being down temporarily.
198019465 CSIX RX and TX packets

is abnormal
tion
Alarm Level Warning
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Signal is unstable when rack or board is powering on.
2. Switch chip is abnormal.
Processing 1. Reset the board.
Suggestion
2. Replace the board.
Alarm Impact The transceiver of the media plane is exceptional.
198005633 Hard Disk Broken

tion
Alarm Level Major

Chapter 2 Alarm
Disaster Alarm Yes

Frequently No
Reported
Cause of Alarm There is failure in ribbon cable connection or the hard disk. This
is usually a hardware failure.
Processing Replace the hard disk on the board or replace the board.
Suggestion
Alarm Impact This alarm is dedicated to OMP only. Its system impact is:
1. Hard disk failure in ROMP start up may cause ROMP board start
up failure and service accessing failure.
2. Hard disk failure in the log server may cause data loss of the
performance data stored on the ROMP hard disk in the abnormal
status.
3. When a peripheral board is starting up and requesting version
from ROMP, Hard disk failure may cause start up failure and power
off of the peripheral board.
198005635 The board is not plugged

firmly
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. The ENUM switch on the board is ON, or is not firmly connected.
2. Or the EXCH key on the standby board is pressed twice within
3 seconds.
Processing 1. Check the ENUM switch and turn it on. If it is not turned on.
Suggestion
2. Switch off and switch on ENUM.
3. If the ENUM open status is simulated by pressing the EXCH key
on the standby board twice within 3 seconds, press the EXCH key
on the standby board twice within 3 seconds.
Alarm Impact Cause failure in active/standby board switching, or cause failure
in APS switching. Do not switch this board into active board.

198005639 High Error Rate of Optical

Interface
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm The fiber is not completed connected to the port, or is damaged,
or is not compatible with the optical transceiver module in T-net-
work switch. There is no light signal input into the optics module.
This alarm is dedicated to the TDM optical port only. The possible
causes of this alarm include:
1. TDM receiver fiber optics failure, fiber optics module failure.
This type of failures include: damaged fiber on the receiver, un-
connected fiber, contaminated fiber or damaged optics module on
the receiver.
2. Fiber optics failure at the transmitting module on the corre-
sponding TDM. This type of failures include: damaged fiber on the
transmitter, unconnected fiber, and contaminated fiber.
3. Compatibility between fiber optics and optics module. The
fiber transmission rate of TDM signal is incompatible with the wave
length of the optics module.
4. Loss of signal (LOS) alarm operation is performed on the cor-
responding SDH device. This includes the manual diagnosis test
alarm operation.
Processing 1. Perform loopback test to determine source of this alarm is on
Suggestion the local devices or the corresponding devices. Perform self-loop
test on local device. If the failure persists, the failure source is
on local device; if the failure disappears after self-loop test, then
the source of failure is on the corresponding device. Contact the
corresponding device for solution.
2. Replace optics module.
3. Replace the fiber optics.
Alarm Impact There might be error in the data transmitted by the optical port
which affects the quality of all the services performed on this op-
tical port.
198005640 FPGA Exception


Chapter 2 Alarm

tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm FPGA runs abnormally, for example, FPGA is lost, or the board
clock is lost.
Processing 1. Restart the board. In this case, the board downloads FPGA
Suggestion again.
Alarm Impact FPGA verification fails. The read and write function of FPGA cannot
be ensured. The board cannot provide complete functions and
work normally. The service carried by the board is interrupted.
198005644 The Channel in a

Subcard Is Down
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. The sub-card is not inserted in position.
2. The sub-card has hardware faults.
Processing 1. Unplug and plug the sub-card again. Wait for the board to be
Suggestion powered on.
2. Replace the sub-card.
Alarm Impact The sub-card channel is not initialized or the initialization fails.
As a result, the channel corresponding to the alarm chip cannot
be used normally. This affects the service carried by the board
of the sub-card. After the channel is available and the alarm is
eliminated, the service is recovered.
198005645 Subcard Abnormal



tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. The GCS, EC or HPS subcard of UIMC/GUIM/CHUB is not in-
serted in position.
2. The subcard is faulty.
Processing 1. Check the sub-card connection. If the connection is loose,
Suggestion tightly insert the sub-card and wait for the board to be powered
on.
2. Replace the sub-card.
Alarm Impact The GCS sub-card of the UIMC/GUIM/CHUB can not function nor-
mally. Packets will be lost. In some cases, control plane links will
be disconnected. For active/standby configuration, there are two
cases:
1. If the active board is abnormal but the standby board is normal,
the system will perform an active/standby changeover. As a result,
the standby board will take over the services borne on the faulty
active board. In this case, services may not be affected.
2. If both the active and standby boards are abnormal, the ac-
tive/standby changeover can not be performed. In this case, ser-
vices will be interrupted because the faulty board can not be back
to normal.
198005646 Phase-locked Loop

Unlocked
tion
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. The clock extraction reference is changed. For example, the
clock output is disabled by the interface board when the optical
port is faulty, which results in changes in clock input. The config-
uration in the NMS is changed, so that a new optical port is used
to extract clock signals.
2. The input of the clock board is changed and the output is
changed accordingly.
3. The UIMC/GUIM input is disconnected, or the PLL on the
UIMC/GUIM is abnormal.

Chapter 2 Alarm
4. The hardware of the PLL on the board is faulty.

Processing 1. Check whether there is the following clock alarm on the NMS
Suggestion Alarm Management interface. If yes, handle it according to the
corresponding suggestions.
198005381 Input Clock Abnormal
2. Check whether there is any of the following alarms about the
clock extracting optical port on the NMS Alarm Management inter-
face. If yes, handle it according to the corresponding suggestions.
198000002 Signal Loss of Optical Module
3. Check the operation and maintenance log in the NMS to see
if there is a record about the change of the loop clock extraction
reference. If yes, no handling is required.
4. Conduct an active/standby changeover to the clock board.
5. Conduct an active/standby changeover to the UIM/GUIM board.
Alarm Impact The service clock and the system clock will be asynchronous be-
cause of the unlocked PLL on this board. As a result, services
borne on the board will be interrupted.
198005647 High Error Rate at E1

Bottom Layer
tion
Alarm Level Major
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm 1. The E1/T1 link is faulty.
2. The device in the uplink direction of the trunk link is faulty.
3. The trunk cable or connector is in poor contact.
Processing 1. Conduct a meter measurement or loopback test to find out
Suggestion whether the alarm is rooted in the local end or peer end. Meter
measurement: Connect a trunk test meter to check if the signal
received by the local end trunk is normal. If yes, the fault is rooted
in the local end. If the test shows the problem persists, the fault
is rooted in the peer end. In this case, inform the peer end to
troubleshoot. Loopback test: Perform self-loop at the trunk where
alarm occurs at local end. If the problem persists, it indicates that
the fault is rooted in the local end. If the alarm is eliminated, it

indicates that the alarm is rooted in the peer end. In this case,
inform the peer end to troubleshoot.
2. Replace the trunk cable.
Alarm Impact The trunk fails to receive trunk signals. If the belonged port has
only this link, all services on the port are interrupted. Otherwise,
only the port bandwidth is affected. The quantity of upper layer ac-
cess services associated with the port is decreased. The accessed
bandwidth is reduced. The service, however, is not interrupted.
198005656 Loss of Clock When Input

to Sub-card
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. The sub-card is not inserted in position.
2. The clock circuit of the sub-card is damaged.
3. The clock circuit of the mother board is damaged.
Processing 1. Check the sub-card connection status. If the sub-card is loose,
Suggestion tightly connect it and power it on again.
2. Replace the sub-card
Alarm Impact The unavailable sub-card clock affects the normal operation of the
board. This may cause clock jittering, and the service that imple-
ments media stream exchange through this board becomes un-
stable. In the most serious case, the system clock is lost and the
service carried by the board is interrupted.
198005663 M28529 chip failure

on board IMAB or DTA affecting
services.
tion

Chapter 2 Alarm
Alarm Level Major

Disaster Alarm No
Frequently No
Reported
Cause of Alarm Devices or sub-cards on the board operate abnormally.
Processing Replace the board.
Suggestion
Alarm Impact This alarm only occurs to the IMAB. When it occurs, the IMAB can
not operate normally and the trunk borne on the board will be bro-
ken. As a result, users can not access the board and the existing
services will be interrupted.
198066044 Fault on Board (GPS)

tion
Disaster Alarm No
Frequently No
Reported
Cause of Alarm According to alarm details, alarm status falls into three types: Type
A Fault on Board (GPS) Phase-lock Equipment Phase-lock Equip-
ment of This Board (GPS) Is in Power-on Status The causes for the
three alarm types are described below.
1.Type A Fault on Board (GPS) Phase-lock Equipment Probable
alarm causes include 16chip loss/out of lock, 12.8M loss/out of
lock, PP2S output loss, 8K output loss, 10M output loss, and 1PPS
loss.
2.Phase-lock Equipment of This Board (GPS) Is in Power-on Sta-
tus The alarm cause is that the GPS module of ICM board is in
power-on status, and power-on has not been completed.
Processing On NMS fault management interface, view alarm Details where
Suggestion Error type information is given. Locate the corresponding alarm
handling suggestion according to the error type. The alarm han-
dling suggestions that correspond to the error types are described
below.
1.Type A Fault on Board (GPS) Phase-lock Equipment
1) On NMS test management interface, perform diagnostic test on
ICM board. Check the working status of the GPS module. If Class
A fault persists in the GPS module, replace the board.
2) Check if output clock loss occurs. If yes, replace the board.
2.Phase-lock Equipment of This Board (GPS) Is in Power-on Sta-
tus If the alarm persists, hardware fault might exist. Replace the
board.

Alarm Impact Be usually determined as hardware fault, which affects system

clock. It might lead to the system clock loss and system synchro-
nization failure. When system clock loss/offset occurs, its subse-
quent impact on service is described below.
1.For TDM transmission, all links based on the TDM transmission
medium (including the transmission link currently in service for UE
and cell transmission link) are affected. Packet loss might occur on
these links, leading to degradation of service quality. In the case
of serious packet loss, service interruption and handover failure
will occur. Even worse, the cell might be out of service.
2.For non-TDM transmission (for example, IP transmission), Iub
interface service is affected, while Iur interface and Iu interface
services are not affected. The clock that Node B derives from RNC
via IEEE1588 is inaccurate. When RNC clock frequency offset is
no more than 0.05 ppm, Node B synchronization will not fail, but
success rate of inter-RNC inter-Node B soft handover might fall.
When RNC clock frequency offset exceeds 0.5 ppm, Node B will
fail to lock the clock. In this case, Node B will oscillate freely and
success rate of inter-Node B soft handover might fall.
198001284 The phase of 8K, 16K

clock, input to backplane board, is
not matched
tion
Alarm Level Minor
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm 1. clock cable is not properly connected.
2. clock board is faulty.
Processing 1. Check the clock input cable and ensure that the cable is good
Suggestion and well connected.
2. Clock board changeover.
3. UIM/GUIM board changeover.
Alarm Impact The system fails to achieve synchronization so that the board can
not work normally. As a result, UE can not be accessed and ser-
vices borne on the board are interrupted.

Chapter 2 Alarm
198001286 Input clock of board lost

tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. The board is not properly inserted to a slot.
2. A clock cable is not connected.
3. The clock cable is broken.
4. The board is faulty.
Processing 1. Check whether the clock input cable is properly connected.
Suggestion
2. Does the board have the following alarm? If yes, please solve
the problem according to corresponding handling suggestion.
Related alarm: 198005635 The board is not plugged firmly.
Alarm Impact The board fails to synchronize with system clock so that it can not
work normally. As a result, UE can not be accessed and services
borne on the board are interrupted.
198000002 Loss of optical signal

tion
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm 1. The receiving optical fiber/module of local equipment is faulty.
Receiving optical fiber is faulty or disconnected.
Optical connector is polluted.
Receiving optical module is faulty.
2. The transmitting optical fiber of opposite equipment is faulty.
Transmitting optical fiber is faulty or disconnected.
3. The receiving optical power at local end is excessively low.

Optical power attenuation on the receiving fiber transmission line

at local end is too much.
Transmitting optical power at opposite end is too low.
4. Operation of LOS insertion is performed at opposite end.
Manual operation of LOS insertion is performed in diagnostic test,
and optical module is shutdown by force.
5. Optical fiber and optical module is incompatible.
The fiber transmission rate and the optical module wavelength are
incompatible.
Processing 1. Carry out loop test to determine whether the alarm is caused
Suggestion by local end or opposite end. Perform fiber self-loop at local equip-
ment. If the alarm persists, fault might lie in local equipment. If
the alarm disappears, inform the opposite end to troubleshoot.
2. Replace the optical module.
3. Replace fiber.
4. Replace board.
Alarm Impact The optical interface fails to work normally. If the optical inter-
face is configured with APS protection, service will be switched to
protection optical interface. Otherwise, all services on the optical
interface will be down.
198015874 Physical channel for data

transmission blocked
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. The traffic flow to the board is excessive.
2. The PSN board in the same shelf is abnormal.
3. The board has hardware faults.
Processing 1. On NMS fault management interface, check if the PSN in the
Suggestion same shelf has generated related alarms. If yes, follow the sug-
gestions on handling the related alarms. The related alarm is as
follows:
198019456 All high-speed links between line card and package
switching board are out of synchronism
2. Unplug and plug the board.

Chapter 2 Alarm
Alarm Impact The services carried by the board are unstable. In most serious
case, all services carried by the board are interrupted.
198015875 GLI table lookup failed

tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. L1 table or L2 table error.
2. Destination IP of packets or hardware is error.
Processing Switch the master port to the partner board.
Suggestion
Alarm Impact Packets would be dropped which would cause poor voice quality
and other problems.
198015876 GLI exception packets

statistic over threshold
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Connection between fiber and optic modules is not perfect.
2. Something wrong with fiber optic module.
3. Board hardware error.
Processing 1. Check the connection between fiber and optic modules.
Suggestion
2. Reboot the board.
Alarm Impact Packets would be dropped which would cause poor voice quality
and other problems.

198002560 The usage of CPU is over

the threshold
tion
Alarm Level Major
Disaster Alarm Yes
Frequently Yes
Reported
Cause of Alarm 1. Excessive data traffic at higher layer.
2. System is performing data synchronization or saving.
3. CPU alarm threshold setting is under configured.
Processing 1. Open the rack map on the Configuration Management window,
Suggestion select Board, right click and select Display Properties Tab. Check
the CPU overload threshold setting on the Processor tab. Please
reset CPU overload threshold if the CPU overload threshold value is
too low. It will take 30 seconds for the new setting to take effect.
Recommended threshold value: 80% for low level load threshold,
90% for high level load threshold.
2. Check for the record of data synchronization, data saving or
other file operations in the network manager log files. Those op-
erations might increase the CPU utilization rate radically, and it
might take 2 minutes.
3. Check for the record of new board added or version upgrade
operation in the network manager log files. Version upgrading
operation might increase CPU utilization rate radically, and it might
take 2 minutes.
Alarm Impact CPU occupancy indicates the current status of system operation.
CPU overloaded, or over high occupancy, is usually caused by ser-
vice or operation that consume much time. It has the following
impact on the system. Services with low priority level have little
or no access to the processing of CPU, which reduces processing
speed of the services or even halts the processing. System board
could reset under excessively overloading conditions, causing in-
terruption to the service it performs.
198002561 CPU temperature over

threshold
tion

Chapter 2 Alarm
Alarm Level Major

Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm 1. Environmental temperature around rack is too high
2. Board hardware fault
3. The alarm threshold value is under configured.
Processing 1. Open the rack map on the Configuration Management window,
Suggestion select Board, right click and select Display Properties Tab. Check
the Upper limit for alarm setting and reboot temperature setting on
the Processor tab. Please adjust the threshold value if the thresh-
old value is too low. It will take 30 seconds for the new setting
to take effect. Recommended Threshold: Upper limit for temper-
ature alarm: 90 degree. Reboot Temperature: 95 degree.
2. Check the thermometer in machine room for accurate tempera-
ture, and take effective measures when actual temperature is over
high.
3. Check and clean the boards for dust accumulation which may
cause heat trapped in the system.
4. Check and clean the air inlet and air outlet for dust accumulation
or remove the impediments if any.
5. Check and make sure the fan(s) on the rack is in normal oper-
ation.
6. Replace the relevant boards.
Alarm Impact The over high temperature of CPU may cause CPU to mal-operate,
or even reset CPU and shut down the board service.
198005376 Internal Port of Board Is

Down
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Physical failure of the IC at the internal port on the board.
2. Failure of local board connecting port on the switching IC of
UIM.
3. Backplane wiring failure of the local slot to UIM.
4. CUP overloaded on the first level switching board, UIM board
at the shelf, or local board.

5. Service over the rated capability of the board.

Processing 1. Check the Alarm Management window for the CUP overloaded
Suggestion on the first level switching board, UIM board at the shelf, or local
board. Perform recommended solution to process the alarm(s) if
any. Related Alarm:
198002560 Board CPU Overloaded
2. Check the Alarm Management window for the alarms of In-
ter-shelf media plane links abnormal. Perform the recommended
solution to process the alarm(s) if any. Related Alarm:
198005121 Inter-shelf Media Plane Link Error
4. Change the slot of the board.
5. Replace the UIM in the same shelf.
Alarm Impact When this port is not available for internal media stream trans-
mission, the internal media stream will select other normal ports
for transmission.If all the internal ports fail to operate normally,
the internal media stream will be interrupted and all the services
provided on this board will be interrupted
198066070 Board Doesn't Exist/ CPU

is in Reset Status for a Long Time
tion
Alarm Level Major
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm 1. Board not properly positioned.
2. Hardware failure.
Processing 1. Check for the proper placing of the board, and insert the board
Suggestion firmly if it is nor properly placed.
2. Plug/unplug the board.
4. Replace the slot
5. Replace the UIM in the same shelf.
Alarm Impact If the board is operational, and the alarm is board position failure,
it does not affect the service operation. The board is in blocked
status, and no service by this board is available. If the board with
alarm is resource board, then the resource is not available on this
board.

Chapter 2 Alarm
198005381 Input clock is abnormal

tion
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm 1. The clock does not stay the working state .
2. The base of the clock does not input to the clock board.
3. The base of the clock is abnormal.
Processing 1. Reconnect the cable between the board and the clock reference.
Suggestion
2. Replace the cable between the board and the clock reference.
3. Check the signal output from the reference clock source.
Alarm Impact System services is interrupted as no proper clock information is
provided to the system.
198005389 CPU sub card in position

is not configured in the database.
tion
Alarm Level Warning
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Configuration is incorrect.
2. Board is misplaced.
Processing Is the subcard needed?
Suggestion
If no, remove the subcard.
If yes, change the type of board so that it can support the subcard.
Alarm Impact Since the board where the unconfigured subcard is located resets
repeatedly, power resource of the equipment is wasted. However,
services won't be affected.

198005390 CPU sub card is missing

from slot but is configured in database
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. The configuration is wrong.
2. A wrong board is inserted.
Processing Is the sub-card required?
Suggestion
If no, modify the type of board so that the new type doesn't sup-
port such sub-card.
If yes, insert the sub-card firmly.
Alarm Impact The sub-card functions are unavailable, accordingly this board
does not support relevant services. The influence on the system
is various according to different type of sub-card.
If the sub-card is an interface board, the transmission link via this
board is not connectable, then services will be accessed through
other sub-card. If the sub-card is a signaling process board, the
cell/Node B configured for this board is not available for services. If
the sub-card is a user's plane board, user plane process capability
will decline, then services will be accessed through other sub-card.
198005395 External Port of Board Is

Down
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. The port cable is not properly connected, or is not connected.
2. The IC of external board port is faulty.
3. The corresponding board is faulty.

Chapter 2 Alarm
Processing 1. Reconnect or replace the cable.

Suggestion
3. Contact the opposite engineers to check the opposite ports for
possible failure.
Alarm Impact This port is not available for the service. If there is a back for this
port, then data communicate through the back port, but the total
communication rate will decline. Also the reliability and stability of
the system declines too. If there is no back for this port, then all
the office communication links through this port will not be avail-
able, and the services through this port are not available.
198005399 DSP resource is

unavailable
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm This alarm indicates the DSP resource is not available. It is mon-
itored by higher level layer, and is reported once DSP is blocked,
the report conditions include:
1. DSP version loaded failure, system is unable to operate nor-
mally.
2. HPI port error on DSP
3. DSP media plane communication failure.
4. DSP reset.
Processing 1. Check the operation maintenance log files in network manager
Suggestion for the operations of DSP version replacing. If there is operation
of DSP version replacing which would cause DSP reset, then the
alarm does not require procession, the DSP will resume operational
after the resetting.
2. There is a DSP index in the detailed information of the alarm.
Open the rack map on the Configuration Management window, se-
lect Board, right click and select "Subunit Configuration". Select
the DSP with alarm, and click Status at Subunit ConfigurationSta-
tus Attribute Query Status. Then check if the Management Status
of DSP is Blocked. If it is Blocked, it means the alarm is a normal
consequence of manually blocking the DSP. Open the rack map on
the Configuration Management window, select Board, right click
and select "Subunit". Run Unblock DSP to resume DSP operation.
3. Check the Alarm Management window for the corresponding
alarms. Perform the recommended solution to process the alarm,
if any. Related Alarms:

198005701 Failure in Version Loading of DSP, Firmware, Microcode

and Single Board Computer
198005655 DSP Reports Exceptions After Detection
198005700 DSP resets for error.
4. Reset the board.
Alarm Impact All the services performed on this DSP is interrupted, and those
services will be re-created on other normal DSP’s. The long period
absence of this DSP might cause decline to the performance of the
system.
198026116 CLKG PP2S Output

Clock Lost
tion
Alarm Level Major
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm Hardware is faulty.
Processing 1. If the alarm is declared by master board rather than slave
Suggestion board, perform master/slave switching.
2. Replace the board where the alarm is declared.
Alarm Impact 1. If this alarm occurs to master clock board, the system will fail
to get clock, leading to processing failure of clock-related boards
and interruption of board services. Relevant boards include IMA
protocol processing board and the interface board capable of HW
processing.
2. If this alarm occurs to slave board, service will not be affected.
198026117 PP2S clock reference

lost
tion
Alarm Level Major
Disaster Alarm Yes

Chapter 2 Alarm
Frequently No
Reported
Processing 1. If the board where the alarm is declared is ICM, please replace
Suggestion the board.
2. If the board where the alarm is declared is CLKG: 1)Check the
connection between CLKG and GCM. 2)Replace the CLKG. 3)Re-
place the GCM.
Alarm Impact System could not get the needed clock, which will cause processing
abnormity related to the clock.
198026118 16CHIP clock reference

lost
tion
Alarm Level Major
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm Replace the board that is alarming.
Suggestion
Alarm Impact The system can not get wanted clock, therefore all clock-related
processes are abnormal.
198026127 Clock reference source

lost (Level 3 alarm)
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm Input clock reference is in unavailable status for no more than 10
minutes. Probable causes include:
1. Clock reference input is abnormal.

2. The configured clock reference does not exist.

Processing 1. Re-connect the input clock reference.
Suggestion
2. For the clock reference not in use, delete the correspond-
ing "Circuitry Clock Reference" configuration on NMS configuration
management interface (board property).
Alarm Impact When all configured clock reference sources are lost, the clock
board comes to free running or hold-over state. Accuracy of out-
put clock is determined by the crystal oscillator of clock board. No
impact on service.

tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm Input clock reference is in unavailable status for more than 10
minutes and less than 24 hours. Probable causes include:
Suggestion
put clock is determined by the crystal oscillator of clock board. The
clock loss leads to synchronization failure between system clock
and clock reference source. Service interruption might occur. The
system will not be affected if the following two events happen to-
gether.
1. Input clock reference source is lost.
2. The phase-locked loop locks other clock reference source.


Chapter 2 Alarm

tion
Disaster Alarm No
Frequently No
Reported
Cause of Alarm Input clock reference is in unavailable status for more than 24
hours. Probable causes include:
Suggestion
put clock is determined by the crystal oscillator of clock board. The
clock loss leads to synchronization failure between system clock
and clock reference source. Service interruption will occur. The
system will not be affected if the following two events happen to-
gether.
1. Input clock reference source is lost.
2. The phase-locked loop locks other clock reference source.
198026131 CLKG board PLL

out-of-lock
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
2. Replace board.
Alarm Impact 1. If this alarm occurs to master board, system clock synchroniza-
tion will fail and service interruption will occur.

198026133 Output clock lost

tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
2. Replace board.
Alarm Impact 1. If this alarm occurs to master board, system clock synchroniza-
tion will fail and service interruption will occur.
198005632 Usage rate of board hard

disk above threshold
tion
Alarm Level Major
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm 1. Usage rate threshold configuration is improper.
2. The usage of hard disk is over high.
Processing 1. Open the Configuration Management windowMPX86 or MPX86/2
Suggestion alarm parameter Hard Disk Full, check the threshold value in the
configuration of Hard Disk Usage Alarm level. Increase the thresh-
old value if the setting is not larger enough.
2. Clear the disk and delete the unnecessary files or move the files
to other external storage devices.
Alarm Impact When hard disk usage is over threshold, there may be error for
the write-in operation of new data, or data loss. It has no impact
to the service.

Chapter 2 Alarm
198005637 Error in Rear Board That

Mismatches With Front Board
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Incorrect rear board is used.
2. Rear board failure.
Processing 1. Check the front board type for the correct rear board type, and
Suggestion use the correct rear board.
2. Replace the defective rear board with a new rear board.
Alarm Impact 1. When the rear board is used for the access of other NE, it would
cause link interruption on the bottom layer, and service interrup-
tion of the corresponding link.
2. When the rear board is used for the access of internal con-
trol plane, it would cause communication error of internal control
plane, failure of the board in exchanging control plane message,
and service interruption of the corresponding link.
3. The rear board of clock board is for clock synchronization, error
in this board would result in clock signal loss. The system services
would be interrupted when clock signal input is absent.
198005661 Physical link down

between master/slave media
interactive ports
tion
Alarm Level Warning
Disaster Alarm No
Frequently No
Reported
Cause of Alarm The network port or board is faulty.

Processing 1. Replace the board.

Suggestion
2. Replace the other board, that is, the board rather than the
faulty board in active/standby configuration.
3. Replace the slot. Use the slot that supports GE channel between
boards.
Alarm Impact The APS optical port data on the standby board cannot reach the
active board. When the active optical port is normal, the service
is not affected. When the active optical port is faulty, APS fails to
protect optical port and thus all services carried by the optical port
are interrupted.
198005662 IDE running overtime

tion
Alarm Level Warning
Disaster Alarm No
Frequently No
Reported
Cause of Alarm IDE is operated for longer time.
Processing No handling is necessary.
Suggestion
Alarm Impact When hard disk work for long time without sleep, engine will be in
high speed spin state for long, this will influence the life of disk,
and data will lose when disk be abnormal. Disk of some model
will lock the engine when it keep work for long time to protect the
disk. But this is out of the software controled, and may result in
data lose when disk cannot be accessed transitorily.
198005667 E1 is looped back.

tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. User has set loop back.
2. Transmission is looped back by provider.
3. Local board is faulty.

Chapter 2 Alarm
4. Remote board is faulty.

5. Loop back applied on DDF.
Processing 1. Disconnect the loopback E1.
Suggestion
2. Restart the board.
4. Replace the opposite board.
Alarm Impact Data can not be sent out because of the loopback E1.
198005671 Incorrect FE Routing

Connection
tion
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. FE-C3/4 is used for FE routing port when RUIM1 rear board is
used.
2. When CHUB is connected to UIM/GUIM, CHUB rear card
(RCHUB1/RCHUB2) uses discrete ports (e.g. port1/port3) to
connect UIM rear card.
3. When UIM/GUIM is connected to UIM/GUIM CHUB, connections
used for FE routing connection are not in pairs (e.g.FE-C2/4).
4. When UIM is connected to UIM/CHUB, only one cable is used
for FE inter-connection.
Processing Reconnect FE cables.
Suggestion
1. If RUIM1 rear board is used on BUSN shelf for FE routing con-
nection, make sure to select FE-C1/2 port as routing port.
2. If GUIM on BGSN shelf is used, make sure to select FE1 and FE2
ports as routing ports. Either double-shelf or multi-shelf cascading
connection is acceptable.
3. If TRUNK mode is used, multiple FE ports form a TRUNK port
and they are connected in cascading mode. In this case, make
sure each end must use ports in pairs. If either local end or oppo-
site end doesn't use FE ports in pairs, please reconnect FE cables
and make sure each end uses ports in pairs. Here is an example
of connection method: i. When CHUB is connected to UIM/GUIM,
the CHUB rear board (RCHUB1/RCHUB2) must use consecutive
ports (e.g. port1/port2 pair, port3/port4 pair, port5/port6 pair,
port7/port8 pair ) to connect the ports (also in pair) on UIM/GUIM
rear board. ii. When UIM is connected to UIM/CHUB, the UIM rear
board must use ports in pairs. If RUIM1 is used, 2 FE-C1/2 ports
must be used for FE routing ports; if RUIM2/RUIM3 is used, use

FE1/FE2 pair, FE3/FE4 pair and FE5/FE6 pair for FE routing ports.
iii. When GUIM is connected to UIM/GUIM/CHUB, the GUIM rear
board must use ports in pairs, FE1/FE2 pair must be used for FE
routing ports.
Alarm Impact Control plane routing is disconnected; ports are switched over in
cycle; all services on this shelf are interrupted.
198005668 Self board has

cross-linked E1
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm elf board has cross-linked E1.
Processing 1. Disconnect the cross-linked E1.
Suggestion
2. Restart the board.
4. Replace the board which connected to this board.
Alarm Impact The data of cross-linked E1 can not be send out.
198005655 DSP Reports Exceptions

After Detection
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. The HPI port fails
2. Hardware failure.
Processing 1. Reset the board.
Suggestion
2. Replace DSP sub-card.

Chapter 2 Alarm

Alarm Impact This DSP will be blocked and no longer available. The cell of this
DSP is out of service; the subscriber using this DSP is out of ser-
vice; call loss rate might increase when call traffic is high.
198005124 Capacity of intra-shelf

control plane TRUNK communication
is insufficient
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Connection failure.
2. Circuitry failure.
3. Board failure.
4. Rear board failure.
Processing 1. Check about whether TRUNK connection is used for Inter-shelf
Suggestion control plane. If not used, no processing is needed.
2. Check for the connection number: 4 Fe’s, 2 GE’s are required.
Complete the connection if there is any missing.
3. Check whether the connection is proper. The proper connection
show as the following: For the FE port trunk, the UIM board on
BUSN shelf does not support TRUNK connection, so this alarm does
not exist. For other shelf, FE7, FE8, FE9 and FE10 set up TRUNK
ports. For the GUIM board, FE3, FE4, FE5, FE6 set up TRUNK ports.
For CHUB board, every 4 neighboring FE ports set up a TRUNK port,
such as FE1~FE4, FE5~FE8 etc. All the 4 ports on the TRUNK port
must be connected. The direct connect method is recommended.
For the GE port trunk, 2 GE interfaces (CHUB board connection)
are both connected and the connection is cross-connection. The
#1 GE port on the left board on the local shelf corresponds to the
#1 GE port on the left board on the opposite shelf, and the #2 GE
port on the left board on the local shelf corresponds to the #2 GE
port on the right board on the opposite shelf. The #1 GE port on
the right board on the local shelf corresponds to the #2 GE port
on the left board on the opposite shelf, and the #2 GE port on the
left board on the local shelf corresponds to the #2 GE port on the
right board on the opposite shelf.
4. Replace the cable or optics module.
5. Replace the rear board.
6. Replace the board connected.

Alarm Impact No system impact is resulted when TRUNK connection is not used
between Inter-Shelf Control Plane. When TRUNK connection is
used, this means the network communication capability is not
enough, and it may cause congestion to control plane. During
high traffic period, this may cause large delay or even service
interruption at extreme condition..
198005125 Incorrect Connection of

GE Optical Transceiver Module
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm The fiber optics connection error.
Processing Check the fiber optics for its proper cross connection, the detailed
Suggestion steps are as below: Each connection kit includes 4 cables, 2 boards
( one at each ends of the connection kit). Each board provides 2
ports which are to connect to the 2 boards on the peer side. The
cross-connection method is as below: the #1 port on the left board
on the local shelf corresponds to the #1 port on the left board on
the opposite shelf, the #2 port on the left board on the local shelf
corresponds to the #1 port on the right board on the opposite shelf.
The #1 port on the right board on the local shelf corresponds to
the #2 port on the left board on the opposite shelf, and the #2
port on the left board on the local shelf corresponds to the #2 port
on the right board on the opposite shelf
Alarm Impact Cause interruption to all services performed on this shelf.
198025602 TDM switch abnormal

tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Check for any clock alarms.
2. TDM Switch chip is faulty.

Chapter 2 Alarm
3. Wrong board in configured slot.

Processing 1. In NMS Configuration Management interface, view the configu-
Suggestion ration of IMA links. Do the values of HW and TS fields configured
for IMA links conflict (for example, two A ends are configured with
the same B end). If yes, modify the configuration.
2. Replace the faulty board.
Alarm Impact The link with abnormal connection is interrupted. Accordingly, ser-
vices are affected.
198029952 802.3ah link fault

tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm Link Fault: The physical layer has determined a fault that occurred
in the receive direction of the local DTE.
Dying Gasp: An unrecoverable local failure condition has occurred.
Critical Event: An unspecified critical event has occurred.
Processing Link Fault:
Suggestion
1. Check the peer is or not right.
2. If right, change the optical fiber and check the alarm.
3. If the alarm is alive, change the and check the alarm.
4. If the alarm is alive, change the board.
Dying Gasp:
Check the peer is or not down.
Critical Event:
1. Check the 802.3ah is or not enable, if it is disable, it can't
receive PDU.
2. If the 802.3ah is enable, if the port is optical, check the alarm
of Link Fault is or not alive, if the alarm is alive, the port can't
receive the PDU
3. Or not, change the good network cable.
4. If the alarm is alive, change the peer board.
Alarm Impact Link Fault:
The port can't receive data, the operations will interrupt.
Dying Gasp:
The port can't receive data, the operations will interrupt.

Critical Event:
The 802.3ah is failed, can't detect the fault of link.
198005669 Synchronization status

check of FPGA failed
tion
Disaster Alarm No
Frequently No
Reported
Cause of Alarm Synchronization status check of FPGA and SPI4/VSC872/VSC874
failed. It's usually caused by hardware exceptions. For example,
the clock chip works abnormally.
Suggestion
Alarm Impact If synchronization status check of FPGA fail, Media can not receive
or send data normally. And the board will reset for the exception
of the media check frame.
198005893 Memory check failed

tion
Disaster Alarm No
Frequently No
Reported
Cause of Alarm Memory check failed.
Processing 1. Make records of the alarm information.
Suggestion
2. Replace the board or subcard.
Alarm Impact The operation related to the memory maybe failed.

Chapter 2 Alarm
198005403 Board SRAM self-check

fails
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm Hardware fault of board.
Processing Replace the board, and check whether this alarm disappears.
Suggestion
Alarm Impact Board operation might be abnormal.
198005404 Board OCXO oven fault

tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm Hardware fault of board.
Processing Replace the board, and check whether this alarm disappears.
Suggestion
Alarm Impact Board operation might be abnormal.
198005405 Clock board phase-lock

loop work mode abnormal
tion
Alarm Level Major
Disaster Alarm No

Frequently No
Reported
Cause of Alarm 1. There is no available reference source.
2. The clock distribution line is incorrect or there exists self loop.
3. The secondary clock locks the tertiary clock.
Processing 1. Check if the corresponding clock reference is correctly inputted.
Suggestion
Alarm Impact The designated reference clock cannot be phase-locked.
Communication Alarm
198000256 Ethernet physical link
broken
Alarm Type Communication Alarm
tion
Alarm Level Minor
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm 1. No network cable is connected to port OMC2 on rear board.
2. A network cable is disconnected or in poor contact.
3. The network port on the board is faulty.
Processing 1. Check whether a network cable is connected to port OMC2.
Suggestion
2. Unplug and plug the network cable from/to port OMC2 on OMP
board.
3. Check whether OMC2 network cable works normally. If not,
replace the cable.
Alarm Impact Master/slave changeover will occur if OMP (ROMB board) works in
master/slave mode.
If the master/slave changeover operation is successful, the system
will not be affected.
If master/slave changeover operation is unsuccessful, OMP board
can not obtain version package from NMS. In this case, the board
fails to be powered on, UE can not be accessed, and the existing
services are interrupted.

Chapter 2 Alarm
198083021 CCP transmission link

fault
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm Transmission fault to Node B
Processing Check the Node B corresponding to the faulty CCP to see if there
Suggestion is any of the following transmission-related alarms. If yes, follow
1. IP mode
Check the Alarm Management interface according to the associa-
tion ID to see if there is any of the following association-related
alarms. If yes, follow the corresponding suggestions to handle it.
198066018 Association link congested
2. ATM mode
1) Bottom layer transmission fault
2) Unavailable PVC link
198018944 PVC Fault
Alarm Impact The CCP transmission link is unavailable, so it cannot be used dur-
ing radio link establishment. If the Node B still selects this CCP,
RNC messages cannot be sent to the Node B and the current ser-
vices will be interrupted.



tion
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm The alarm occurs when the receiving optical power is below optical
receiver sensitivity. Generally speaking, normal receiving optical
power range for optical modules is between -28 dBm and -8 dBm.
Optical signals within this range can be detected.
Probable causes for the alarm include:
1. The receiving optical fiber/module of local SDH equipment is
faulty.
Receiving optical fiber is faulty or disconnected.
Receiving optical module is faulty.
2. The transmitting optical fiber of opposite SDH equipment is
faulty.
Transmitting optical fiber is faulty or disconnected.
3. The optical transmission line of SDH equipment is faulty.
Tail fiber and flange between fiber distribution frame and the equip-
ment at local end are faulty or disconnected.
The related connector is in poor contact.
4. The receiving optical power at local end is excessively low.
Optical power attenuation on the fiber transmission line at receiv-
ing end is too much.
Opposite-end transmitting optical power is too low.
5. Operation of LOS insertion is performed at opposite end.
Manual operation of LOS insertion is performed in diagnostic test,
and optical module is shutdown by force.
6. Optical fiber and optical module is incompatible.
The fiber transmission rate of STM signals and the optical module
wavelength are incompatible.
Processing 1. Use meter measurement or loop test to judge whether the
Suggestion alarm is caused by local end or opposite end.
Meter Measurement
Use a SDH test meter or optical power meter to test whether the
receiving optical signals at local end are normal. If normal, fault
might lie in local equipment. If abnormal, fault lies in opposite end
or on transmission side. Inform the opposite end or transmission
side to troubleshoot.
Loop Test
Perform fiber self-loop at local SDH equipment. If the alarm per-
sists, fault might lie in local equipment. If the alarm disappears,
inform the opposite end to troubleshoot.

Chapter 2 Alarm
2. Replace optical module.

3. Replace optical fiber.
4. Replace board.
Alarm Impact SDH/SONET fails to work normally, leading to UE access failure on
SDH/SONET and interruption of ongoing services.
198083036 DSAR Alarm

tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. User plane resource initialization failure.
2. CCH setup failure at Node B side.
3. CCH configuration is deleted by OMCR.
4. The Bearer type of common transport channel is modified by
OMCR.
Suggestion check the Alarm Reason, which can help you easily find the corre-
sponding handling suggestions. The handling suggestions for each
alarm are as follows:
1.Alarm Reason: User plane resource initialization failure.
1) Click NE Information Configuration on the NMS Configuration
Management interface and select the corresponding Node B. Select
the Path Configuration tab to check if all parameters, including the
forwarding bandwidth, are correctly configured.
2) Click Path Group Configuration on the NMS Configuration Man-
agement interface to check if all parameters are correctly config-
ured.
2. Alarm Reason: CCH setup failure at Node B side. Click Base
Station Ground Resource Management on the NMS Configuration
Management interface and select IP and Route Management to
check the IP parameters. Make sure that at least one "COS" is
selected.
3. Alarm Reason: CCH configuration is deleted by OMCR. This
alarm will be processed automatically by the system. The RNC
will initiate the process of common channel deletion. No manual
handling is required.
4. Others. The system will automatically reestablish the common
channel. No manual handling is required.
Alarm Impact The common channel is unavailable, which falls into three cases.

1. If the S-CCPCH that carries FACH is unavailable, the CS/PS

services initiated by the UE will fail.
2. If the S-CCPCH that carries PCH is unavailable, the paging func-
tion of the system cannot be used and the CS/PS services initiated
by the CN will fail.
3. If the PRACH that carries RACH is unavailable, the UE cannot
access this cell.
198083038 Transport Path group

Occupied Bandwidth Overload
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm Available bandwidth of transport path group is less than occupied
bandwidth. Probable causes for the alarm include:
1.E1 link is broken.
2.Transmission quality of the transmission line is poor.
3.Intermediate equipment is faulty.
Processing 1.Check the E1 link.
Suggestion
2.Check the transmission quality of intermediate equipment.
Alarm Impact The available bandwidth to destination is less than occupied band-
width.So service rate on this path group will be degraded.
198083039 IP channel of Iub

interface is faulty
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. IP channel is down.

Chapter 2 Alarm
2. Packet loss rate exceed 25%.

Processing Check the transmission quality of intermediate equipment.
Suggestion
Alarm Impact Service and OMCB will choose other IP channel to transfer data.
198083040 TCP connect on IuBC

interface is interrupted

tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Interface board (GIPI) of local equipment is faulty.
2. Intermediate equipment or opposite equipments faulty.
3. The network cable connection is loose or disconnected.
Processing 1. Check the interface board(GIPI) for the Related Alarms. Per-
Suggestion form the recommended solution to process the possible alarms.
Related Alarms: 198066070 Board Offline or the CPU is in long
period reset status
2. Telnet to the interface board. Set a destination IP and ping it.
In the case of direct connection, ping the direct connect interface
board address. In the case of not direct connection, ping the inter-
mediate equipment. If response timeout, contact the equipment
provider for solution.
3 .Check the physical connection on IuBC interface. If the connec-
tion is loose or broken, unplug and plug the cable or replace the
cable. If port indicator is on, the physical link must be normal.
Alarm Impact The IuBC Broadcast is disabled.
198022784 BFD Session Interrupted

tion
Alarm Level Minor
Disaster Alarm No

Frequently No
Reported
Cause of Alarm 1. The network cable connection on relevant equipment (including
local/ intermediate/opposite equipment) is loose or disconnected.
2. Intermediate equipment is faulty.
3. Opposite equipment is faulty.
4. Local equipment is faulty.
5. Configuration related to the BFD session is incorrect.
Processing On NMS fault management interface, view alarm Details where in-
Suggestion formation of source address and destination address of the BFD
session is given. The source address is the address of local equip-
ment. The destination address is the address of BFD session ter-
minal equipment.
1. Check the operation status of line card at local end. If the line
card resets repeatedly, replace board. Then power-on the board.
2. Check the physical connection at the BFD session-related port
on local line card. If the connection is loose or broken, unplug
and plug the cable or replace the cable. If port indicator is on, the
physical link must be normal.
3. Set a destination IP. Ping intermediate equipment and opposite
equipment in turn.
i. Telnet to the interface board. Test if the link is normal via ping. If
the destination address is 2.2.2.10, issue the following command
in telnet interface. brs_ping_b "2.2.2.10"
ii. Wait for 5 seconds and issue the following command.
BrsShowLog "ICMP" a. If "PING=== destine 2.2.2.10 timeout,
Response timeout must occur" appears on the interface, response
timeout must occur. b. If “ping_receive:Reply from 2.2.2.10:
bytes=60 time<1ms” appears, response must be normal, indicat-
ing that the link is normal.
iii. In the case of response timeout, check if the configuration of
related route and address is correct. If not, perform reconfigura-
tion and retest.
iv. In the case of response timeout despite correct route/address
configuration, certain link or intermediate equipment might be
faulty. Check if disconnected network cable, loose connection, or
abnormal equipment status exists on the faulty link along the BFD
session path. If yes, take necessary measures, including cable
replacement and replugging, equipment repair or replacement.
4. If packet reception and transmission are normal as confirmed
by ping, check if the BFD session configuration at both ends is
correct. On NMS configuration management interface,
i. Check BFD switch. Ensure that the switch is in "enable" status.
ii. Ensure that BFD session working modes at both sides are con-
sistent.
iii. Ensure that BFD session in at least one equipment plays the
“active” role.
iv. Ensure that BFD session exists at both ends, and configuration
of source IP and destination IP matches.

Chapter 2 Alarm
v. Ensure that the hop mode (single hop/multihop) at both ends

are consistent.
vi. Check configuration authentication information. Ensure that
the number of authentication information configured at both ends
are consistent.
5. Reset the board where the interface is located.
Alarm Impact All services on the path related to the BFD session will be switched
to the slave path. Service interruption will occur if slave path does
not exist.
198066029 PPP link broken

tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. The alarm occurs once in PPP port during board power-on, and
recovers after successful PPP negotiation..
2. Physical link is down, or link transmission quality is poor.
3. Adjustment of PPP link parameter leads to link re-negotiation,
causing the alarm.
Processing On NMS fault management interface, view alarm Details, where
Suggestion the faulty PPP port ID is given.
1. Check cable connection at both ends. If the cable is discon-
nected or connection is loose, unplug and plug the cable or replace
the cable.
2. Refer to user’s networking plan to see if E1 cable connection is
correct.
3. On NMS configuration management interface (IPOverE1 con-
figuration), check Interface E1 No. and time slot configuration.
Ensure that the relevant configuration is consistent at both ends.
4. On NMS configuration management interface, check PPP con-
figuration. Ensure that the relevant configuration at both sides is
consistent.
5. On NMS configuration management interface, check configura-
tion of DT and EIPI connection. Ensure the connection continuity
of PPP port at both ends.
Alarm Impact The PPP link is down. If merely one PPP link is available for the
port or all available PPP links are down, the service on the port
will be down. Otherwise, only port bandwidth will be affected.
The number of successful service access will decrease, but service
interruption will not occur.

198018944 PVC link is down.

tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm Receive AIS/RDI cells from far end. If CC function is activated, it
may be caused by a timeout that missing CC cells and user cells
from far end.
Processing 1. On NMS fault management interface, view alarm Details where
Suggestion PVC ID is given. Locate the faulty port according to the given
information.
For example, the PVC ID given in alarm Details is 1. On NMS con-
figuration management interface (PVC configuration), try to locate
the PVC whose ID is 1. View the related subsystem No., unit No.,
ATM port No. to locate the corresponding interface board and port.
2. Check the relevant equipment based on the physical bearer of
the port.
If the faulty PVC port is carried by optical interface, ensure that
the fiber connector and interface are in good contact, or replace
the fiber.
If the faulty PVC port is carried by IMA port, check if the following
alarms occur to the corresponding IMA group/link. If yes, refer to
the corresponding alarm handling suggestion.
Related alarms:
19207 Near end IMA group configuration failure
19213 LIF alarm of near end receiving link
19214 LODS alarm of near end receiving link
19215 RDI alarm of near end receiving link
19221 Remote receiving link ID mismatched
3. Check if the CC had been activated If it is, check the steps
followed.
4. Check if the equipment power-on at opposite end is successful.
If no, refer to the maintenance manual of opposite equipment for
troubleshooting.
5. Check if the PVC status at opposite end is successful. If no,
refer to the maintenance manual of opposite equipment for trou-
bleshooting.
6. Deactivate CC test at local end, or activate CC test at opposite
end.
For IMAB/APBE board:

Chapter 2 Alarm
To deactivate CC test at local end, initiate "PVC CC test" on NMS

test management interface. When configuring test parameters,
select "0: Deactivate CC" for activation type, select "1: B-A" for
test type (A indicates local end and B indicates opposite end).
To activate CC test at opposite end, initiate "PVC CC test" on NMS
test management interface. When configuring test parameters,
select "1: Activate CC" for activation type, select "1: B-A" for test
type.
For APBE2/DTA board:
Modify PVC CCINFO parameter of configuration to active or deac-
tivate CC test. CC test parameter is same to APBE/IMAB.
Alarm Impact PVC is in faulty status. All services on the PVC are interrupted.
198019213 LIF Alarm of Near-End

Receiving Link
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm Physical fault or connection error occurs to E1 link.
Suggestion information of IMA chip ID, IMA group ID, IMA link ID, and E1
index is given. Locate the faulty IMA link according to the given
information.
1. Refer to user’s networking plan to see if connection error exists.
2. On NMS fault management interface, check if E1-related alarm
exists in the board. If yes, refer to the corresponding alarm han-
dling suggestion. Related alarms:
198066045 Trunk error
198066046 Trunk abnormal
198001026 Cell delineation do not synchronization about cell on
E1 link
Alarm Impact IMA link is down. If several links are available in the IMA group,
bandwidth of the IMA group will be affected, and the number of
successful upper-layer service access will decrease. However, ser-
vice interruption will not occur. If merely one link is available in
the IMA group, all services on the IMA group are interrupted.

198019214 LODS Alarm of Near-End

Receiving Link
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Operation of the input clock is abnormal.
2. Transmission quality of the link is poor.
3. Self-loop occurs to some cable connection in IMA group
4. Cable connection is incorrect in IMA group.
5. Hardware is faulty.
Suggestion information of IMA chip ID, IMA group ID, IMA group link ID, and
IMA link ID is given. Locate the faulty IMA link according to the
given information.
1. Check the RUN indicator of clock board. If the indicator is green
and flashes slowly, operation of the clock board must be normal.
Otherwise, reset/replace the clock board.
2. On NMS fault management interface, check if clock-related
alarm occurs in UIM/GUIM. If yes, input clock source must be ab-
normal. Refer to the corresponding alarm handling suggestion.
Related alarms:
198001286 Loss of clock when input to board
198005646 Phase-lock loop unlock
3. On NMS fault management interface, check if E1-related alarm
exists. If yes, refer to the corresponding alarm handling sugges-
tion. Related alarms:
198001026 Cell delineation do not synchronization about cell on
E1 link
4. Check if remote self-loop occurs to any physical connection in
the faulty IMA group. If yes, properly connect the cable according
to the networking planning information.
5. Check cable connection according to the networking planning
information. Ensure that the cabling is correct.
6. Reset board.
7. Replace board.

Chapter 2 Alarm
198019215 RDI alarm of far end

receiving link
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Remote IMA link is not in activated status.
2. Remote receiving direction is faulty.
Processing On NMS fault management interface, view alarm Details where in-
Suggestion formation of IMA chip ID, IMA group ID, IMA link ID, and E1 index
is given. Locate the faulty IMA link according to the given infor-
mation. Check the working status of the relevant remote receiving
link by referring to the opposite equipment operation guide. If re-
mote receiving link is not in activated status, activate the link.
198019223 Ne Group is in fault state

tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1.All IMA links of this IMA group are broken.
2.The peer-end IMA group is broken.

Processing Fix the broken IMA links in the IMA group.

Suggestion
Alarm Impact The IMA Group does not work.
198066026 Association path broken

tion
Alarm Level Major
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm 1. Network communication is faulty.
2. Control plane path in NE is interrupted.
3. Opposite equipment is faulty.
4. The route to remote address is lost.
Suggestion information of association ID, local address, and remote address
is given.
1. On NMS configuration management interface (static route),
query the route information of the remote address. Locate the out
port according to the route information. Check if network cable of
the out port is disconnected or loose. If yes, unplug and plug the
cable or replace the cable.
2. On NMS configuration management interface (SCTP association
configuration), query the ID of the module where the association is
located. Check if the following alarm occurs in the relevant board.
If yes, refer to the corresponding alarm handling suggestion. Re-
lated alarm:
198066003 Control plane communication abnormal between board
and its home module
3. On NMS configuration management interface (static route),
query if the route to the remote address of the association is con-
figured. If not, add the configuration.
4. Check the intermediate equipment on association path. If the
routes to local address and remote address of the association are
not configured, add the configuration according to equipment op-
eration manual.
5. Check at opposite end if the route to the local address of the
association is configured. If not, add the configuration.
6. Check if the opposite equipment is faulty. If yes, troubleshoot
at opposite end.
Alarm Impact If multiple paths are available for the association and there exists
normal path, relevant services will not be affected. If merely one

Chapter 2 Alarm
path is available for the association, all services on the association

is down.
198005666 The number of the error

packets from MAC port exceeds the
threshold
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. The port cable is not properly connected.
2. The port cable is faulty.
2. The IC of external board port is faulty.
3. The corresponding board is faulty.
Processing 1. Reconnect the cable, ensure that the connection between this
Suggestion port and the peer port is correct.
2. Replace the cable.
4. Contact the opposite engineers to check the opposite ports for
possible failure.
Alarm Impact The MAC port is unavailable or the flow is limited.

tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. The receiving cable of local trunk equipment is faulty. The cable
is disconnected, or cable connector is broken.
2. The transmitting cable of opposite trunk equipment is faulty.
The cable is disconnected, or cable connector is broken.

3. Trunk transmission line is faulty. The local DDF and equipment

are not properly connected.
4. Operation of LOS insertion is operated at opposite trunk equip-
ment. Manual inset alarm operation is performed in diagnostic test
Processing 1. check whether the alarm is caused by local end or opposite end
Suggestion via meter measurement or loop test. Meter Measurement Use a
trunk test meter to test whether the trunk receiving signals at local
end are normal. If yes, fault might lie in local equipment. If no,
troubleshoot at opposite end. Loop test Perform trunk self-loop at
local end. If the alarm persists, fault might lie in local equipment.
If the alarm disappears, troubleshoot at opposite end.
2. Replace trunk cable.
3. Replace board.
Alarm Impact The trunk equipment fails to work normally. All services based on
the trunk are interrupted.

tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Trunk frame formats at local end and at opposite end are in-
consistent.
2. The transmitting end of opposite trunk equipment is faulty.
3. Local trunk equipment is faulty.
4. Equipment grounding at both ends is bad.
5. Impedance mismatch occurs.
Suggestion Error type is listed. Locate the specific handling suggestion ac-
cording to the listed error type. The handling suggestions that
corresponds to different error types are presented below.
1.Frame loss of trunk of E1; Multiple frame loss of trunk of E1;
Alarm indication signal of trunk of E1.
i. On NMS configuration management interface (subunit configu-
ration), Check whether frame type configuration at local end and
at opposite end is consistent.
ii. On NMS configuration management interface (subunit configu-
ration), Check whether impedance configuration is correct.
iii. Check whether the grounding at both ends is proper.

Chapter 2 Alarm
iv. If possible, check whether the alarm is caused by local end or

opposite end via meter measurement, loop test, or board/cable
replacement
2.Far-end alarm indication received by trunk of E1. Check the
alarm status at opposite end. Since the alarm origin is opposite
end, first troubleshoot at opposite end.
Alarm Impact All services based on the trunk are interrupted.
198066047 Abnormal status in

SDH/SONET
tion
Disaster Alarm No
Frequently No
Reported
Cause of Alarm On NMS fault management interface, view alarm Details where
Error type information is given. Each error type corresponds to
an alarm status Altogether there are twenty-two types of alarm
status. Probable causes which correspond to different alarm status
are listed below.
1. Loss of frame
This alarm will occur when the A1A2 frame aligning signal in SDH
regenerator section overhead fails to be received properly for a
consecutive 3 ms.
2. Regenerator section trace identifier mismatch
This alarm will occur when J0 byte in "access point identifier" at re-
ceiving end and transmitting end is inconsistent with the expected
(the previous agreement between two ends). The alarm might be
caused by configuration inconsistency of J0 byte mode/value at
both ends.
3. Multiplex section alarm indication signal.
All "1"s will be sent in the STM signal (excluding regenerator sec-
tion overhead) of local SDH equipment when alarms of optical sig-
nal loss or optical path frame loss are declared in opposite SDH
equipment.
4. Multiplex section remote defect indication.
This alarm is a remote alarm indication. It is an indication of an
alarm currently reported at opposite equipment. The alarm which
originates from remote multiplex section is in return indicated by
the local SDH equipment.
5. Multiplex section remote error indication.

When multiplex section B2 bit error occurs in opposite SDH equip-

ment, the number of bit errors can be detected at local end. The
alarm will be reported if the number of bit errors reaches a certain
limit.
6. Signal failure.
This alarm will occur when bit error rate in the multiplex section
of receiving signals exceeds 1E-3.
7. Signal deterioration.
This alarm will occur when bit error rate in the multiplex section
of receiving signals exceeds 1E-6.
8. Administration unit loss of pointer.
This alarm will occur, when for consecutive 8 frames, SDH equip-
ment fails to receive valid pointer value or the received pointer
value is NDF.
9. Administration unit alarm indication signal.
All "1"s will be sent in the administration unit (including pointer)
of local SDH equipment when alarms of high order path pointer
loss, high order path unequipped, high order path trace identifier
mismatch, and high order path signal label mismatch are declared
in opposite SDH equipment.
10. High order path trace identifier mismatch.
This alarm will occur when J1 byte in "VC-4 path access point iden-
tifier" at the receiving end and the transmitting end is inconsistent
with the expected (the previous agreement between two ends).
The alarm might be caused by configuration inconsistency of J1
byte mode/value at both ends.
11. High order path unequipped.
This alarm will occur when the "VC-4 path signal identifier" re-
ceived by local SDH equipment is coded in all zero mode. The
following two reasons might account for the alarm.
The path in local SDH equipment has not been equipped by oppo-
site end.
The path configured at opposite end is 0.
12. High order path signal label mismatch.
ceived by local SDH equipment is different from the expected one.
The alarm might be caused by configuration inconsistency of C2
byte at both ends.
13. High order path remote defect indication.
originates from remote high order path is in return indicated by
the local SDH equipment.
14. High order path remote error indication.
When B3 bit error of the high order path occurs in opposite SDH
equipment, the number of bit errors can be detected at local end.
The alarm will be reported if the number of bit errors reaches a
certain limit.
15. Tributary unit loss of multiframe.

Chapter 2 Alarm
The H4 byte in VC-4 path overhead is used as tributary unit mul-

tiframe indication. This alarm will occur when the following two
conditions are satisfied.
Local- SDH equipment fails to receive the correct multiframe indi-
cation code.
Multiframe alignment fails for consecutive 8 frames
16. Tributary unit loss of pointer.
This alarm will occur, when for consecutive 8 frames, SDH equip-
ment fails to receive valid pointer value or the received pointer
value is NDF.
17. Tributary unit alarm indication signal.
All "1"s will be sent in the tributary of local SDH equipment when
alarms of tributary unit pointer loss, tributary unit unequipped,
tributary unit trace identifier mismatch, and tributary unit signal
label mismatch are declared in opposite SDH equipment.
18. Tributary unit remote defect indication.
originates from the remote tributary is in return indicated by the
local SDH equipment. The remote defects include tributary unit
multiframe loss, tributary unit pointer loss, tributary unit trace
identifier mismatch, and tributary unit unequipped, etc.
19. Tributary unit remote defect indication (VC-11).
This alarm is the same with Alarm 18, except in that it applies to
VC-11 structure, where T1 is configured for the trunk.
20. Tributary unit trace identifier mismatch.
This alarm will occur when J2 byte in "TU-12 access point identifier"
received by local SDH equipment is different from the expected
(the previous agreement between two ends). The alarm might be
caused by configuration inconsistency of J2 byte mode/value at
both ends.
21. Tributary unit unequipped.
ceived by local SDH equipment is coded in all zero mode. The
following two reasons might account for the alarm.
The relevant tributary has not been equipped by opposite end.
The relevant tributary configured at opposite end is 0.
22. Tributary unit signal label identifier mismatch.
ceived by local SDH equipment is different from the expected code.
The alarm might be caused by configuration inconsistency of V5
byte (bit5-bit7) at both ends.
Processing Alarm details are displayed in NMS Alarm Management interface,
Suggestion where fault type is given. You can easily find handling suggestions
according to the fault type.
The handling suggestions for each fault type are described as be-
low:
1.Regenerator section trace identifier mismatch

In NMS Configuration Management interface, click SDH parameter

configuration and select SDH Optical Channel Parameter to check
whether the configuration of "J0 configuration mode" and "regen-
erator section trace" at local end is consistent with those at oppo-
site end. If no, modify the configuration to keep consistency.
2. Multiplex section remote defect indication
Check alarm status in the multiplex section of opposite end. Be-
cause the alarm origin is from the opposite end, please solve the
problem at opposite end first.
3. Multiplex section remote error indication
Check alarm status in the multiplex section of opposite end. Be-
cause the alarm origin is from opposite end (B2 bit error), please
solve the problem at opposite end first.
4. High order path trace identifier mismatch
whether the configuration of "J1 Mode 0" and "high order path
trace 0" at local end is consistent with those at opposite end. If
no, modify the configuration to keep consistency.
5. High order path unequipped
the configuration of optical channel payload type. If the configured
value is 0, modify the configuration.
6. High order path signal label mismatch
the configuration of optical channel payload type. Ensure that the
parameter configuration at both sides is the same.
7. High order path remote defect indication
Check alarm status in the high order path of opposite end. Because
the alarm origin is from opposite end, please solve the problem at
opposite end first.
8. High order path remote error indication
Check alarm status in the high order path of opposite end. Because
the alarm origin is from opposite end (B3 bit error), please solve
the problem at opposite end first.
9. Tributary unit remote defect indication/Tributary remote defect
indication (VC-11)
Check alarm status in the corresponding tributary unit at opposite
end. Because the alarm origin is from opposite end, please solve
the problem at opposite end first.
10. Tributary unit trace identifier mismatch
whether the configuration of "J2 mode" and “low order path trace”
at local end is consistent with those at opposite end. If no, modify
configuration to keep consistency.
11. Tributary unit unequipped

Chapter 2 Alarm

the configuration of tributary unit payload type. If the configured
value is 0, modify the configuration.
12. Tributary unit signal label identifier mismatch
the configuration of tributary unit payload type. Ensure that the
parameter configuration at both sides is the same.
13. Others
i. Use measurement instrument or loopback test to judge whether
the alarm is caused by local end or opposite end.
a. Measurement instrument
Use a SDH test instrument to test whether the received optical
signals at local end are normal. If normal, it means opposite end
has a fault. Please solve the relevant problem.
b. Loop Test
Carry out a self-loop test at local SDH equipment. If the alarm still
occurs, it means local end has a fault. If the alarm disappears, it
means opposite end has a fault. Please solve the relevant problem.
ii. Replace the optical module.
iii. Replace the optical fiber.
iv. Replace the board.
Alarm Impact 1. If alarm occurs on optical path, all trunk signals and services
on this path are interrupted.
2. If alarm occurs on tributary, all trunk signals on this path are
interrupted, and all services on this trunk are interrupted.
198066048 SDH/SONET Excessive

Error Code
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Attenuation of receiving signals of local SDH equipment is large.
2. The transmitting part of opposite SDH equipment is faulty.
3. Fiber connector is polluted or misconnected.
4. The receiving part of local SDH equipment is faulty.
5. Operation of bit error insertion is performed at opposite end.

Processing 1. Use meter measurement or loop test to judge whether the

Suggestion alarm is caused by local end or opposite end.
Meter Measurement
Use a SDH test meter or optical power meter to test whether the
receiving optical signals at local end are normal. If normal, fault
might lie in local equipment. If abnormal, fault lies in opposite end
or on transmission side. Inform the opposite end or transmission
side to troubleshoot.
Loop Test
Perform fiber self-loop at local SDH equipment. If the alarm per-
sists, fault might lie in local equipment. If the alarm disappears,
inform the opposite end to troubleshoot.
2. Replace optical module.
3. Replace optical fiber.
4. Replace board.
Alarm Impact SDH/SONET equipment can work. However, call loss or noise oc-
curs to all voice services on this optical path, and bit error occurs
on the data service channel.
198001026 Loss of ATM Cell

Synchronization over E1 Link
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Cell Header HEC (Header Error Check) is damaged, leading to
cell location failure in physical layer frame.
2. The alarm is caused by bottom layer fault. Cell HEC is handled
differently at local end and opposite end.
Processing 1. Check if the following alarm occurs in the board. If yes, refer
Suggestion to the corresponding alarm handling suggestion.
Related alarms:
2. On NMS configuration management interface, check if
SDH/SONET mode is configured for both ends. Ensure that the
configuration at both ends is consistent.
3. Use meter measurement or loop test to judge whether the
alarm is caused by local end or opposite end.

Chapter 2 Alarm
Meter Measurement
Use a trunk test meter to test whether the trunk receiving signals
at local end are normal. If normal, fault might lie in local equip-
ment. If abnormal, troubleshoot at opposite end.
Loop Test
Perform self-loop at local trunk. If the alarm persists, fault might
lie in local equipment. If the alarm disappears, inform the opposite
end to troubleshoot.
5. Replace board.
Alarm Impact Data reception on E1 link is abnormal. If merely one E1 link is
available for the port, all services on the board will be down. Other-
wise, port bandwidth will be affected, leading to decreased access
bandwidth. The number of successful upper-layer service access
related to the port will decrease, but service interruption will not
occur.
198066049 ATM link is down

tion
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Bottom layer physical link is abnormal.
2. HEC handling at local end and opposite end is inconsistent.
Processing 1. Check if the following board alarm occurs. If yes, refer to cor-
Suggestion responding alarm handling suggestion.
Related alarms:
2. On NMS configuration management interface, check if
SDH/SONET mode configuration exists at both ends. Ensure that
the configuration at both ends is consistent.
3. Use meter measurement or loop test to judge whether the
alarm is caused by local end or opposite end.
Meter Measurement
Use a trunk test meter to test whether the receiving trunk signals
at local end are normal. If normal, fault might lie in local equip-
ment. If abnormal, troubleshoot at opposite end.
Loop Test

Perform self-loop at local trunk. If the alarm persists, fault might

lie in local equipment. If the alarm disappears, troubleshoot at
opposite end.
5. Replace board.
Alarm Impact Communication at ATM port is down. All services based on the
trunk are interrupted.
198015617 Frames Received by

FE/GE/ATM/MP/POS/E1 Port are
faulty.
tion
Alarm Level Minor
Disaster Alarm No
Frequently Yes
Reported
Cause of Alarm 1. The network connected with FE/GE/ATM/MP/POS/E1 port is ab-
normal.
2. The board is in abnormal status.
3. Board hardware is faulty. For example, the network processor
subcard is not tightly inserted.
4. Other board hardware faults.
Processing 1. Unplug and plug port fiber/network cable.
Suggestion
2. Replace port fiber/network cable.
3. Reset board.
4. Unplug and plug board.
5. Replace board.
Alarm Impact Datagram reception of the board is affected. The service on this
port might be unstable. Worst of all, all services on the board
might be interrupted.
198015873 Faulty frames received

by internal switching interface

Chapter 2 Alarm

tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. The PSN board in the same shelf is abnormal.
2. Network processor subcard of the board is not tightly inserted.
3. Board hardware is faulty. For example, the switching chip is
faulty.
Processing 1. Check if the following alarm exists in PSN board at the same
Suggestion shelf. If yes, refer to the corresponding alarm handling suggestion.
Related alarm:
198019456 All high-speed links between line card and package
switching board are out of synchronism
2. Unplug and plug board.
3. Replace board.
Alarm Impact If the fault lies in PSN board, service of the entire RNC NE will
become unstable. If the alarm persists, all services will be inter-
rupted. If the fault lies in the board where the alarm is declared,
only the services on this board are affected.
198005378 Board HW Error

Alarm Classifica- Notification
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Clock is not synchronous.
2. Either the board or the slot has a hardware fault.
Processing 1. Check whether the board has one of the following alarms. If
Suggestion yes, please solve the problem according to corresponding handling
suggestions. Related Alarms
198001286 Loss of input clock
198005646 Phase-locked Loop Unlocked
2. Check whether the clock board has one of the following alarms.
If yes, please solve the problem according to corresponding han-
dling suggestions. Related Alarms
198026133 Output clock lost


3. In Configuration Management interface, check whether APS
protection is configured when the SDTB/SDTB2 works in mas-
ter/slave mode. How to check APS protection configuration: In
the Configuration Management interface, click Rack, select the
concerned board (SDTB/SDTB2). Then right click it. A shortcut
menu appears. Then select Optical Port APS Protection.
5. Replace the slot 6. Replace the UIM/GUIM of the same shelf.
Alarm Impact HW connection is affected and services carried over this HW are
interrupted.
198005651 IPMAC conflict when

OSS detects control plane
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. The board is not plugged in place.
2. Backplane DIP switch configuration has been modified.
Processing 1. Unplug and plug board.
Suggestion
2. Check the backplane DIP switch at the shelf where the board
is located and the switch at the shelf where OMP is located. If
the switches at two shelves are inconsistent, reconfigure the DIP
switch to keep consistency. Reset the relevant boards after recon-
figuration.
3. Reset board.
Alarm Impact IPMAC Conflict leads to communication fault in board control plane.
For the board that has powered on, packet loss occurs and board
services is unstable. Even worse, link interruption might occur and
all services on the board might be interrupted. For the board that
is powering on, board resets repeatedly, and service access to the
board fails.

Chapter 2 Alarm
198066003 Control plane

communication is abnormal between
board and its home module
tion
Alarm Level Major
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm 1. The board is not in position.
3. The control plane communication is abnormal.
4. The board is reset.
Processing 1. Check if the board is in position. If not, insert the board.
Suggestion
2. Reset the board. Wait for the board to be powered on.
4. Replace the board slot.
5. Replace the UIM/GUIM board in the same shelf.
Alarm Impact The services carried by the board are interrupted.
198066004 Control plane

communication is abnormal between
MP and OMP
tion
Alarm Level Major
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm 1. The board is not in position.
3. The control plane communication is abnormal.

4. The board is reset.

Processing 1. Check if the board is in position. If not, insert the board.
Suggestion
2. Reset the board. Wait for the board to be powered on.
4. Replace the board slot.
5. Replace the UIM/GUIM board in the same shelf.
Alarm Impact The board is blocked and the functions of the board are unavail-
able. As a result, all services of the units under this module are
unavailable.
198005382 Communication between

power board and OMP board is
abnormal
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. The power board is not connected to the OMP or connection
failure occurs.
2. The rack number configured for the rack in which this power
board locates is not consistent with the rack number switch set for
the power board.
Processing 1. Reconnect the 485 cable between the power board and OMP.
Suggestion
2. Make sure the rack number configured for the rack in which this
power board locates is consistent with the rack number switch set
for the power board.
Alarm Impact Unable to monitor the power supply condition and the environment
condition. It has no impact to the services.
198005396 Exceptional
communication on UIM board
or back plane

Chapter 2 Alarm

tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. The internal port chip on the board has a physical fault.
2. The switch IC on UIM/GUIM provides a port, which is connected
to the board. This port has a fault.
3. Backplane wiring failure, which connects the slot to UIM.
4. A CUP on L1 switching board, the board, or UIM board of the
same shelf, is overloaded.
5. Service exceeds the processing capability of the board.
Processing 1. In Alarm Management interface, check whether there is an
Suggestion internal media plane port abnormal alarm. If yes, please solve the
problem according to corresponding handling suggestion.
Related Alarm: 198005376 Internal media plane port abnormal
2. In Alarm Management interface, check the CPU rate, which is
located on L1 switching board, the board or UIM board of the shelf.
Is there a CPU overloaded alarm? If yes, please solve the problem
according to the corresponding handling suggestions.
Related Alarm: 198002560 Board CPU Overloaded
3. In the Alarm Management interface, check whether there is an
alarm, indicating abnormal link at inter-shelf media plane. If yes,
please solve the problem according to the corresponding handling
suggestions.
Related Alarm: 198005121 Inter-shelf media plane link fault
5. Change a slot to insert the board.
6. Replace the UIM of the same shelf.
Alarm Impact If the internal media plane stream can not be processed, packets
may be lost. In this case, services provided by this board become
unstable.
If it is port fault or connector fault, the internal media plane is
completely broken. In this case, services borne on this board are
interrupted.
If either CPU or traffic is overloaded, services carried on the board
will be delayed. In serious situation, services may be interrupted.
198005397 Communication of
RAWMACIP channel is abnormal


tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1The CPU usage of the UIM/GUIM in the shelf is too high.
2The service media stream exceeds the threshold.
3 The hardware is faulty.
Processing 1. On NMS fault management interface, check if the UIM/GUIM
Suggestion board in the same shelf has related alarms. If yes, follow the
suggestions on handling the related alarms. Related alarm:
198002560 Board CPU overloaded
3. Replace the UIM/GUIM in the same shelf.
4. Replace the slot.
Alarm Impact The channel between user plane processing board and signaling
processing board is abnormal. This causes the degradation of QoS.
In most serious case, the service is totally interrupted.
198005401 Test packet check

abnormal
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. The board is faulty.
2. The line from UIM/GUIM to GLI is abnormal.
Processing On NMS fault management interface, view the alarm details, which
Suggestion give the test alarm type. You can quickly locate the handling
method according to the test alarm type. The handling sugges-
tion for each test alarm type is as follows:
1.Test alarm type: ATM test abnormal The link between C5 and
APC of ATM processing board is abnormal. In this case, replace
the board.
2.Test alarm type: Level 1 switch test abnormal The level 1 media
plane switching from UIM/GUIM to GLI is abnormal. This is always
caused by the abnormal link between UIM/GUIM and GLI. In this

Chapter 2 Alarm
case, reconnect the cables between UIM/GUIM and GLI or replace

the cables. If optical fibers are used, replace the optical module.
Alarm Impact This alarm affects the service transfer on media plane. In alarm
details, the detected alarm type gives the error type of the alarm.
The alarm impact varies depending on the alarm type.
1.If the test alarm type is "ATM test abnormal", the ATM board
cannot normally provide ATM services. Thus, the service carried
by the board is interrupted.
2.If the test alarm type is "Level 1 switch test abnormal", it indi-
cates that media plane communication is abnormal. This causes
the service carried by this shelf to be interrupted.
198005121 Inter-shelf media plane

links abnormal
tion
Alarm Level Major
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm 1. The fiber connection is error between shelves, or the fiber is
not physically plugged.
2. The background configuration of the board is inconsistent with
its foreground physical connection.
3. The transceiver of the board link detection packet is excep-
tional.
Processing 1. In the NMS Configuration Management interface, select Unit
Suggestion Connection Relation, then compare the configuration with actual
physical connection. If it is different, adjust connection cables ac-
cording to the configuration.
2. Check the connection of optical fiber and make sure it is in cross
connection. Is there any relevant alarm? If yes, please solve the
problem according to recommended handling suggestions.
Relevant Alarm: 198005125 GE optical transceiver module is
wrongly connected to left/right board slots at opposite end.
3. Replace the optical fiber or the optical transceiver module so
that the SD indicator for the corresponding port is on.
4. Replace the local board.
Alarm Impact The inter-shelf service bandwidth is reduced. The inter-shelf ser-
vices may be interrupted if no backup is configured.

198005122 Loss of Active/standby

communication link.
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. The board is configured to be in active/standby mode, but the
opposite board is not in position.
2. Hardware Problem.
Processing 1. Make sure the board is configured in active/standby mode, and
Suggestion both active/standby boards are in position.
2. Check whether the opposite board has the following alarm. If
yes, please solve the problem according to recommended handling
suggestions.
Description: 198005379 Board offline or CPU in reset status for a
long period
4. Change the slots of the active board and the slave board.
Alarm Impact The active board can not communicate with the standby board.
As a result, active/standby changeover operation fails. There is
no impact on services.
198066060 FE Link Error Alarm

tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. In a pair of FE ports, one has normal link but the other has link
error.
2. The hardware is faulty.
Processing 1. Check if only one cable is used to connect the port pair of the
Suggestion rear board to the peer-end FE port. Ensure that both cables are
connected to the peer end.

Chapter 2 Alarm
2. Reconnect the cables or replace the cables.

3. Replace the rear board.
Alarm Impact Since one FE port in the control plane link can work normally, the
service is not affected. If this port is also faulty, the service will
be interrupted because the service cannot be switched over to the
other port.
198005128 Duplicate rack and shelf

tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm Shelf connect to the system with duplicate physical ID
Processing 1.Check whether two shelf with same physical ID exists. Modify
Suggestion the switch of one of the two shelfs and reset the shelf and board
if such connection exists.
2.Check if the board link to the same board by different link type.
Remove one of link type and reset the board if such connection
exists.
Alarm Impact Boards in the shelf which power-on later power-on failure.
198066005 SCCP subsystem

unavailable
tion
Alarm Level Minor
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm 1. From the perspective of A, remote signaling point subsystem is
out of service.
2. From the perspective of A, remote signaling point is inaccessi-
ble.

3. Remote subsystem (for B) is configured at A end, but the cor-

responding local subsystem (for B) is not configured at B end.
4. Local subsystem (for B) is blocked at B end.
5. From the perspective of A, SCCP user is unconfigured in remote
MTP3 or M3UA user configuration.
Processing 1. Check whether there exists office (the office that corresponds
Suggestion to the subsystem) inaccessible alarm. If yes, refer to the corre-
sponding alarm handling suggestion. Related alarms:
198066010 MTP3 office inaccessible
198066014 M3UA office inaccessible
2. Unblock the subsystem in dynamic data management.
3. On NMS configuration management interface, check the config-
uration of signaling point code (for A) at A end. See if SCCP user
is included in user type configuration. If no, add the configuration.
Meanwhile, check the corresponding configuration at B end.
4. Check whether the status of signaling point subsystem (for B)
is available at B end. If no, the signaling point subsystem at B end
must be out of service. Locate the cause for the abnormal status.
5. Check whether the signaling point subsystem (for B) is config-
ured at B end. If no, add the configuration at B end.
Alarm Impact Signaling data cannot be sent to and received from the relevant
subsystem. Access of new service under the corresponding office
fails, and release of the ongoing service occurs.
198066007 Broadband link overload

tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1.There are too many messages from upper layer service.
2.The number of links is insufficient.
3.Link load is uneven.
Processing 1. Check the counter of "Peak Traffic of Signalling Link" in MTP3B
Suggestion signaling link performance statistics. If the load (nearly) reached
6000 during alarm occurrence, upper layer traffic must be heavy.
Add links to share load.
2. On NMS configuration management interface, check the signal-
ing link configuration of NE. Add or delete links to ensure that the
number of links in a link set is two to the power of N. If there are
two link sets in the current route, ensure that two link sets have
the same number of links.

Chapter 2 Alarm
Alarm Impact Link overload leads to upper layer service message loss. Call loss
will occur, and access success rate of PS service will fall.
198066010 RNC unable to connect

to MTP3 office
tion
Alarm Level Major
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm 1. No service link exists in the office route.
2. TFP is received.
Processing 1. Check whether there is an unavailable link alarm. If yes, please
Suggestion solve the problem according to corresponding handling sugges-
tions. Related alarm: 198066011 MTP3 link unavailable.
2. Check whether the configuration of office and link at opposite
end is correct.
Alarm Impact UE fails to receive/transmit messages from/to the relevant office.
New services can not be accessed to this office, and existing ser-
vices are interrupted abnormally.
198066011 MTP3 link unavailable

tion
Alarm Level Major
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm 1. Physical link at bottom layer is broken or link quality is poor.
2. Link test fails.
3. This link is deactivated in dynamic data management.
4. The opposite end has released this link.
5. SMP or SPB/SPB2/APBE/APBE2 board resets.

Processing 1. IN NMS Configuration Management interface, click Signalling

Suggestion Link Configuration to check PVC configuration. Make sure that the
configuration of CVPI and CVCI should be the same at both ends.
2. In Dynamic Data Management, check link status. If it is inter-
rupted and connected now and then, it means the link unavailabil-
ity is caused by MTP3 link test failure.
1) In NMS Configuration Management interface, check the con-
figuration of signaling point code at both ends. Ensure that the
configuration is consistent at both ends.
2) In NMS Configuration Management interface, check the configu-
ration of signaling link at both ends. Ensure that the configuration
of SLC (Signaling Link Code) is consistent at both ends.
3. Re-activate the link in Dynamic Data Management.
4. Check board status. If it is abnormal, reset or replace the
board.
5. The opposite end has released the relevant link. Ask the oppo-
site end to deal with the alarm as link unavailable.
Alarm Impact If several MTP3 links are available for the office, services will not
be affected. In the case of heavy traffic, link congestion may occur,
leading to loss of packets/calls and decreased PS call access rate.
If merely one link is available to the destination signaling point,
the office may become inaccessible. UE fails to receive/transmit
messages from/to the relevant office. New services can not be
accessed to this office, and existing services are interrupted ab-
normally.
198066014 RNC unable to connect

to M3UA office
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Association link is broken or application server (AS) is not in
serving status.
2. M3UA office is inaccessible because the remote office gives a
DUNS (destination signaling point unavailable) report.
Processing 1. Check whether there is an association link broken alarm. If
Suggestion yes, please solve the problem according to corresponding handling
suggestions.
Related alarm: 198066019 Association link broken

Chapter 2 Alarm
2. In NMS Configuration Management interface, view AS Static

Information to check whether a routing context exists. If yes,
view the relevant configuration such as routing context ID, AS ID
and AS service mode.
The correct configuration is described below.
i. The routing context ID and AS service mode must be the same
at both ends.
ii. AS ID must meet the following requirements: if ASP is config-
ured for local end, SGP should be configured for opposite end; if
IPSP client is configured for local end, IPSP server should be con-
figured for opposite end.
3. Re-activate the ASP in Dynamic Data Management.
4. Check whether the configuration of relevant office is correct at
opposite end.
Alarm Impact UE fails to receive/transmit messages from/to the relevant office.
New services can not be accessed to this office, and existing ser-
vices are interrupted abnormally.

tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. The association is released in dynamic data management.
2. Association configuration is modified at local end.
3. Association is released at opposite end.
4. Bottom layer link is faulty.
Processing 1. Establish the association in dynamic data management.
Suggestion
2. On NMS configuration management interface, check associa-
tion configuration at local end and opposite end. Checking items
include protocol type of SCTP association, SMP module No, local
IP address, local port No., remote IP address, remote port No.,
the number of in/out streams. If the configuration at both ends is
inconsistent, modify configuration to keep consistency.
3. Ping the opposite board address to see if the network cable or
other intermediate link is faulty. Replace the cable if ping fails.
4. Check if the association is released at opposite end. If yes,
troubleshoot according to the corresponding cause.
Alarm Impact 1. If several association links are available to the destination office,
service will not be affected. In the case of heavy traffic, conges-

tion of available association(s) might occur, leading to upper layer

call loss or increasing PS call access failures.
2. If merely one association link is available to the destination
office, the office might become inaccessible. Reception and send-
ing of messages from/to the relevant office fail. Access of new
services under this office fails, and abnormal release of ongoing
services occurs.
198029953 The Ethernet port state

is OAM loop back
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm The local port state is loop back because the peer port starts Eth-
ernet OAM loop back request of 802.3ah.
Processing Check if the peer port has started Ethernet OAM loop back test. If
Suggestion yes, stop it, if no, disable local port Ethernet OAM.
Alarm Impact The Ethernet link which is in loop back test can't bear service data.
198003841 The control plane

retransfer ratio over the threshold
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm There are some badly-touched boards in system environment and
the retransfer-ratio of RUDP packets increases.
Processing Make records of the alarm information and contact ZTE Corpora-
Suggestion tion.
Alarm Impact The master board will change when slave is exist.

Chapter 2 Alarm
198083045 Common Channel setup

failed Alarm
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Use plane resource initialization fails.
2. Common channel establishment fails on Node B side.
3. CCH transport bearer setup fail.
4. Common channel configuration is deleted in NMS.
5. Inner Procedure Fail.
Processing Check the configuration according to the following steps:
Suggestion
1. Check whether DSP run normally.
2. Check whether IUB interface board run normally.
3. Check whether alarms of transport bearers fail exist or not.
4. On NMS configuration management interface (NE information
configuration), select the relevant Node B. Check the correctness
of parameter configuration on path configuration interface. "Peer
service IP address" must be configured in the same network seg-
ment with Node B IP address.
5. On NMS configuration management interface (BS ground re-
source management), view IP parameter configuration in IP and
route management. Ensure that at least one “COS” is selected.
6. On NMS configuration management interface (NE information
configuration), select the relevant Node B. Check the correctness
of parameter configuration on path configuration interface. Check
if forwarding bandwidth is configured.
7.On NMS configuration management interface (path group con-
figuration), view path group configuration. Check the correctness
of parameter.
8. Check whether Node B alarm exist.
9. Contact with ZTE Corporation.
Alarm Impact Common Channel is unavailable, which falls into the following
three cases.
1. If the SCCPCH carrying FACH is unavailable, UE-initiated CS/PS
services will be down.
2. If the SCCPCH carrying PCH is unavailable, paging function
will be unavailable in the system, leading to failure of UE-initiated
CS/PS services.

3. If the PRACH carrying RACH is unavailable, UE access to the

cell will fail.
198066071 Link broken for board

fault
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm Board internal fault.
Processing 1. Note down detailed information.
Suggestion
1.1 Back up related local office configuration data and peer-end
office configuration data.
1.2 Back up related local office and peer-end office history alarms
and notifications, as well as current alarms.
1.3 Contact ZTE Corporation and end the alarm handling proce-
dure.
Alarm Impact This alarm may render some offices inaccessible, or may result in
the congestion of other links.
198066066 AAL2 Path locally

blocked
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm The Path is manually blocked from this AAL2 Node.
Processing You can unblock the Path which is generated manually from the
Suggestion operating interface.
Alarm Impact No AAL2 connection can be established on the blocked path.

Chapter 2 Alarm
198066067 AAL2 Path remotely

blocked
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm The adjacent AAL2 node initiates blocking process and then the
path of this node is remotely blocked when receiving the blocking
message from the adjacent node.
Processing You can unblock the Path which is generated by adjacent node
Suggestion from the operating interface of the adjacent node.
198066068 AAL2 Path blocked by

broken PVC
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm The Path is blocked because of the broken PVC.
Processing The path can be available when PVC becomes available.
Suggestion

Processing Alarm
198083020 RNC system resources
limits reached, no new UE's can
attach to the network
Alarm Type Processing Alarm
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. High number of users trying to access the network.
2. Total number of tokens exhausted.
Processing It is recommended to expand the capacity of the system.
Suggestion
Alarm Impact The system will reject new services to ensure the quality of the
existing services.
198083024 GPS receiver on ICM is

abnormal
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. GPS subcard is not tightly inserted.
2. Hardware of GPS subcard is faulty.
Processing 1. Unplug and plug GPS subcard.
Suggestion
2. Replace GPS subcard.
Alarm Impact GPS subcard mainly provides positioning function for RNC NE. The
subcard fault leads to handset positioning failure. Service is not
affected.

Chapter 2 Alarm
198019207 Near-End IMA Group

Configuration Failure
tion
Disaster Alarm No
Frequently No
Reported
Cause of Alarm IMA group configuration at local end and at opposite end is incon-
sistent.
Suggestion information of the faulty IMA group is given.
On NMS configuration management interface (IMA group configu-
ration), locate the corresponding IMA group according to the infor-
mation given in alarm Details. Compare the configuration of the
following parameters at both ends. If the configuration at both
ends is inconsistent, modify configuration at either end to keep
consistency.
"Near-End OMA Label"
"Rx Frame Length (cells)"
"Tx Frame Length (cells)"
"Near-End Symmetry"
Alarm Impact All services on the IMA port are interrupted.
198015360 Microcode Is Abnormal

tion
Alarm Level Major
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm Network Processor hardware is faulty.
Processing Wait for the board to reboot. If the alarm cannot be restored after
Suggestion board rebooting, unplug and then plug the board. If the alarm still
cannot be restored, replace the board.
Alarm Impact The board will reboot. If the alarm can be restored after board
rebooting, all board services during rebooting will be down, but

access of new services to the board after rebooting will be suc-

cessful. If the alarm cannot be restored after board rebooting, all
board services during and after rebooting will be down.
198023040 The number of board

alarms exceeds the threshold
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm There are too many alarms for this board. The alarm pool is full
of board alarms.
Processing Troubleshoot the current alarms in the system.
Suggestion
Alarm Impact Alarm information loss might occur. No impact on user service.
198066031 The number of OMP

alarms exceeds the threshold
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm There are too many system alarms. The alarm pool is full of sys-
tem alarms.
Processing Delete the trivial alarms on NMS fault management interface.
Suggestion
Alarm Impact Alarm information loss might occur. No impact on user service.

Chapter 2 Alarm
198066032 NTP time exceeds

threshold
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Link between OMP and RPU is down.
2. NTP time and local time differs greatly.
Processing 1. On NMS fault management interface, check if the alarm related
Suggestion to RPU board exists. If yes, refer to the corresponding alarm han-
dling suggestion. Related alarm:
198066004 Control plane communication abnormal between MP
and OMP
2. Please change the value of the threshold to 0 or larger than 100
if the value of the threshold is configured from 0 to 100.
3. Please try to recover the alarm by synchronizing the NTP time
with the board local time manually.
4. Check whether the interval between alarm time and the current
environmental time exceeds 8 alarm periods. Check the synchro-
nization period and modify it if it is too long. Make sure the NTP
server is working properly.
Alarm Impact NTP time synchronization terminates, leading to interruption of
ongoing services.
198066027 SNTP failure

tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. SNTP server does not exist or server operation is abnormal.
2. The configured SNTP IP address in the database is inconsistent
with the real IP address.
3. Communication between RNC NE and SNTP server is down.

4. The time synchronization period configured in the database

might be 0.
Suggestion Alarm Reason is given. Locate the specific handling suggestion
according to the given reason. The handling suggestions that cor-
respond to different alarm reasons are described below.
1. Illegal DB configuration. On NMS configuration management in-
terface (RNC ground resource management), check if SNTP server
IP address or SNTP synchronization period are incorrectly con-
figured. If yes, which means SNTP server IP is configured as
255.255.255.255 or SNTP synchronization period is 0, correct the
configuration.
2. Failed to get time from SNTP server.
i. Ensure that SNTP server exists and server operation is normal.
ii. Ensure that the configured SNTP server IP address in the data-
base and the real server IP are consistent.
Alarm Impact SNTP synchronization failure might lead to inconsistency between
system time and real time. For example, the real time is 1:00 am,
but the displayed system time is 2:00 am. Since system clock
frequency is correct, service will not be affected.
198005387 Alarm Due to Inconsistent

MP Type
tion
Alarm Level Major
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm 1. The MP type is changed on NMS and the board is not restarted.
2. The active MP type on the local board is not consistent with that
configured on NMS.
Processing 1. For CMP and SMP, reset the board.
Suggestion
2. For OMP, set the start mode as "foreground start" on NMS and
then reset the board. Do as follows: On NMS software version
management interface, select the menu for querying foreground
(that is, RNC NE) board start mode. In the pop-up dialog box, set
the start mode to "foreground start".

Chapter 2 Alarm
Alarm Impact This alarm has no effect on the service.
198005388 Startup File Does Not

Exist
tion
Alarm Level Major
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm The startup configuration file is deleted.
Processing 1. Reset the active and standby OMPs.
Suggestion
Alarm Impact This alarm may cause OMP work abnormally, and the entire NE
services are affected.
198005398 Office ID is not set

correctly with control shelf.
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm The office ID of a shelf where DIP switch locates is different from
that of a shelf where OMP locates.
Processing Set the office ID of the shelf where DIP switch locates to be the
Suggestion same as that of OMP belonged shelf.
Alarm Impact The MAC address conflicts. The MAC and IP address verification
fails. All boards on the shelf can not be powered on. All services
carried by the shelf are interrupted.

198066057 Database config is

different from file named bootcfg ini.
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm After the start information of OMP is modified, the active and
standby OMP boards are not restarted.
Processing Restart the active and standby OMPs.
Suggestion
Alarm Impact The bootcfg ini. file contains the information on the office ID, dis-
trict ID, OMP gateway, OMC MAC address, and OMC gateway mask.
If the information is modified, the OMP cannot connect to OMC and
external network normally.
198005649 Port working mode

doesn't match with its setting.
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. The local device does not support this mode setting.
2. The opposite device does not support this mode setting.
Processing Alarm details are displayed in NMS Alarm Management interface,
Suggestion where error mode type is given. You can easily find handling sug-
gestions according to the error mode type.
The handling suggestions for each type are described as below.
1. Speed rate mode error
i. Determine which rate should be configured. Replace the existing
board with one that supports such rate mode.
ii. For force mode, configure the port with a suitable rate that is
supported by bottom layer in actual working status.

Chapter 2 Alarm
Do as follows:
In NMS Configuration Management interface, first find subunit de-
tails, then set a suitable rate that is supported by bottom layer in
actual working status.
iii. For auto-adaptive mode, re-configure an expected rate so that
it is consistent with actual port rate.
Do as follows:
tails, then set the rate to be expected one.
2. Duplex mode error
i. Determine which mode should be configured. Replace the exist-
ing board with one that supports such mode configured on RNC.
ii. For force mode, re-configure the port to be in duplex mode that
is supported by bottom layer in actual working status.
Do as follows:
tails, then set a suitable working mode that is supported by bottom
layer in actual working status.
iii. For Auto-adaptive mode, re-configure an expected duplex
mode so that it is consistent with actual port duplex mode.
Do as follows:
tails, then set the working mode to be expected one.
3. GE port master/slave mode error
i. Make sure the master/slave mode is required. Replace the ex-
isting board with the one that supports master and slave mode
configured on RNC.
ii. For force mode, configure the port to be in master/slave mode
that is supported by bottom layer in actual working status.
Do as follows:
tails, then set a suitable GE port master/slave mode that is sup-
ported by bottom layer in actual working status.
iii. For Auto-adaptive mode, re-configure an expected mas-
ter/slave mode and ensure that it is consistent with actual port
master/slave mode.
Do as follows:
tails, then set the GE port master/slave mode to an expected one.
Alarm Impact 1. The port fails to work in configured mode, therefore, it can not
be used. All services via the port are interrupted.
2. For auto-adaptive mode, the bandwidth of external port be-
comes insufficient. As a result, some services via the port are
interrupted.

198005123 DB Configuration Doesn't

Fit for Device
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. The type of physical board is incorrectly configured.
2. A wrong board is inserted
Processing 1. The NMS configuration management interface gives the rack
Suggestion diagram. Select the board and check if the board and subunit
settings of rack are correct. If the settings are incorrect, delete
the board and create a new one.
2. Check if a correct board is inserted in the slot on the rack. If
not, insert the correct one.
Alarm Impact The board fails to be normally powered on. The services carried
by the board are interrupted.
198005126 Incorrect FE Routing

Connection
tion
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. FE-C3/4 is used for FE routing port when RUIM1 rear board is
used.
2. When CHUB is connected to UIM/GUIM, CHUB rear card
(RCHUB1/RCHUB2) uses discrete ports (e.g. port1/port3) to
connect UIM rear card.
3. When UIM/GUIM is connected to UIM/GUIM CHUB, connections
used for FE routing connection are not in pairs (e.g.FE-C2/4).
4. When UIM is connected to UIM/CHUB, only one cable is used
for FE inter-connection.

Chapter 2 Alarm
Processing Reconnect the FE wire.

Suggestion
1. If the UIM board on the BUSN shelf uses RUIM1 backcard, make
sure FE-C1/2 port is used for routing port.
2. If the GUIM board is on BGSN shelf, make sure FE1 and FE2
ports are used as routing ports.
3. If TRUNK mode is used, numerous FE ports make up of a TRUNK
port for cascaded connection. In this case, make sure the both
ends are paired ports.
If the boards of the local board or the opposite board are not paired
port, please reconnect the FE wire and make sure the both ends
are used paired ports.
Here is an example of connection method:
i. When CHUB is connected with UIM/GUIM, the connecting wire
on RCHUB1/RCHUB2 of CHUB backcard must be used continuous
ports ( such as port1/port2 pair, port3/port4 pair, port5/port6 pair,
port7/port8 pair ) to connect with the pairs on the UIM/GUIM back-
card.
ii. When UIM is connected with UIM/GUIM/CHUB, the ports on
UIM backcard must be used as paired. If RUIM1 backcard is used,
then two FE-C1/2 ports must be used for FE routing ports; if
RUIM2/RUIM3 backcard is used, then use FE1/FE2 pair, FE3/FE4
pair or FE5/FE6 pair for the FE routing ports.
iii. When GUIM is connected with UIM/GUIM/CHUB, the ports on
GUIM backcard must be used as pair, i.e, FE1 and FE2 must be
used for FE routing ports.
Alarm Impact Control plane routing is disconnected, ports are switched over in
cycle, all services on this shelf are interrupted.
198066006 Broadband link

congestion
tion
Alarm Level Minor
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm 1. The configured signaling PVS bandwidth is insufficient.
2. Bottom-layer physical transmission quality is poor.
Processing 1. Check the counter of "Peak Traffic of Signaling Link" in MTP3B
Suggestion signaling link performance statistics. If the load (nearly) reached
6000 during alarm occurrence, upper layer traffic must be heavy.
Increase PVC bandwidth or add links to share load.

2. Check NMS alarms/notifications to see whether there exists

physical transmission alarm(s) /notification(s) that occurred si-
multaneously with this alarm. If yes, refer to the corresponding
alarm handling suggestion. Alarms/Notifications related to physi-
cal transmission are listed below, with respect to access mode.
1) Fiber Access Mode
198066048 SDH/SONET:Excessive Error Code
2)E1 Access Mode
198005647 High Error Rate at E1 Bottom Layer
198000576 Trunk Slide
3. Check the performance statistics of SSCOP link. Check if there
was message retransmission of "Number of PDU Retransmitted"
during alarm occurrence. If yes, packet loss must have occurred
during transmission. Since packet loss might occur at opposite
end, ask opposite end to cooperate in troubleshooting.
Alarm Impact Link congestion leads to transmission delay. If congestion is not
serious, service will not be affected. Otherwise, packet loss or call
loss might occur, and access success rate of PS service might fall.
198066013 MTP3 link congestion

tion
Alarm Level Major
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm 1. There are too many upper layer service messages.
2. Bottom layer link quality is poor, leading to frequent message
retransmission.
Processing 1. Add links to the office that is in service for the congested link.
Suggestion
2. Take the following measures to improve transmission quality of
physical links. Replace bottom layer links. Ensure that connector
contact and cable connection are normal.
Alarm Impact Link congestion leads to transmission delay. If congestion is not
serious, service is not affected. Otherwise, packet loss or call loss
might occur, and access success rate of PS service might fall.

Chapter 2 Alarm

tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Transmission quality of bottom layer link is poor.
2. Upper layer traffic in sending service data is heavy.
Processing 1. Check network cable connection. Ensure that the network cable
Suggestion is tightly inserted.
2. Add association links to the office that is in service for the
congested association.
3. If intermediate equipment exists between local end and op-
posite end, check the transmission quality of intermediate equip-
ment.
Alarm Impact Transmission delay, or even packet loss will occur. If congestion is
not serious, service will not be affected. Otherwise, call loss might
occur, and access success rate of PS service might fall.
198019712 loss of protection

switching
tion
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Fiber connection is wrong.
2. APS backup mode is configured differently between local end
and opposite end.
3. APS protection mode is configured differently between local end
and opposite end.
4. The opposite equipment is faulty.

Processing 1. Check fiber connection.

Suggestion
Check fiber connection at both ends. Ensure that the work optical
ports at both ends are interconnected, and the protection optical
ports at both ends are interconnected.
On NMS configuration management interface, locate the relevant
board in the rack. Right-Click the board and open board properties
page. Click Optical port APS protection to view the "Work optical
port" and "Protection optical port" configured at local end.
2. Check APS backup mode configuration at both ends.
Check APS backup mode (1 1 or 1:1) at local end to ensure con-
figuration consistency at both ends.
page. Click Optical port APS protection in the shortcut menu to
view the "Protection Type" (1+1 or 1:1).
3. Check APS protection direction at both ends.
Check APS protection direction (unidirectional or bidirectional)
configured at local end. Ensure configuration consistency at both
ends.
page. Click Optical port APS protection to view the "Protection
Direct" (unidirectional or bidirectional).
4. Check whether APS is supported by the opposite equipment.
Check whether APS configuration is correct and has taken effect.
Alarm Impact APS automatic protection switching function is paralyzed. When
the working optical port is abnormal, the protection optical port
will not work, leading to service interruption on this optical port.
198019713 loss of protection

switching
tion
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Fiber connection is wrong.
2. APS backup mode is configured differently between local end
and opposite end.
3. APS protection mode is configured differently between local end
and opposite end.

Chapter 2 Alarm
Processing 1. Check fiber connection.

Suggestion
Check fiber connection at both ends. Ensure that the work optical
ports at both ends are interconnected, and the protection optical
ports at both ends are interconnected.
page. Click Optical port APS protection to view the "Work optical
port" and "Protection optical port" configured at local end.
2. Check APS backup mode configuration at both ends.
Check APS backup mode (1 1 or 1:1) at local end to ensure con-
figuration consistency at both ends.
Type" (1+1 or 1:1).
3. Check APS protection direction at both ends.
Check APS protection direction (unidirectional or bidirectional)
configured at local end. Ensure configuration consistency at both
ends.
Direct" (unidirectional or bidirectional).
Alarm Impact 1. When fiber connection is correct and the working optical port
can work normally, services won't be affected.
2. When the working optical port is faulty, APS automatic protec-
tion switching function doesn't work, and services carried via this
optical port will be interrupted due to lack of protection.
198019714 APS configuration alarm.

tion
Disaster Alarm No
Frequently No
Reported
Cause of Alarm Optical interface are not configured for APS in 1:1 mode.
Processing 1. If board backup mode is configured as 1:1 or 1+1 and SDH
Suggestion optical interface is needed, at least one set of APS protection needs
to be configured.
To configure APS protection:
page. Click Optical port APS protection.

2. If board master/slave mode is not needed, modify board backup

mode into.
To configure board backup mode:
Delete the relevant board on NMS configuration management in-
terface. Then recreate the board. Select board backup mode as
"None" during board creation.
3. If board backup mode is configured as 1:1 and no SDH optical
interface is required, modify the board backup mode into 1+1.
To configure board backup mode:
Delete the relevant board on NMS configuration management in-
terface. Then recreate the board. Select board backup mode as
"1+1" during board creation.
Alarm Impact The board can not enter into normal working status. All board
services fail to be established.
Environment Alarm
198025856 Rack temperature is high.
Alarm Type Environment Alarm
tion
Alarm Level Minor
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm 1. Fan is not working.
2. Fan has failed.
3. No fan connected.
4. Temperature sensor is faulty or setting is incorrect.
Processing 1. In NMS Configuration Management interface, click Power Board
Suggestion Alarm Parameters to view the upper threshold of rack tempera-
ture. If the configuration is unreasonable, please modify it. The
recommended value of upper threshold is 70 degrees in Celsius.
2. Check the thermometer in equipment room to see if the actual
temperature is too high. If yes, take necessary cooling measures.
3. Remove dust from air intake and outlet of the rack. Remove
any obstacle nearby which may affect ventilation.
4. Ensure that the rack fan works normally.
Alarm Impact 1. If an unreasonable threshold is configured, services will not be
affected.

Chapter 2 Alarm
2. If the alarm is caused by high rack temperature, board may

work abnormally and board services may be interrupted.
198025857 Low temperature in Rack

tion
Alarm Level Minor
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm 1. temperature sensor is not working.
2. Treshold is incorrect.
3. External room heating control not working.
Suggestion Alarm Parameters to view the lower threshold of rack tempera-
ture. If the configuration is unreasonable, please modify it. The
recommended value of lower threshold is 0 degrees Celsius.
temperature is too low. If yes, take necessary warming measures.
3. Setting the sensor correctly.
affected.
2. If the alarm is caused by low rack temperature, board may work
abnormally and board services may be interrupted.
198025858 House temperature is

higher than high threshold
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Threshold configuration is unreasonable.
2. Actual temperature in equipment room is too high.

Processing 1. On NMS configuration management interface (power board

Suggestion alarm parameters), check the upper limit of equipment room tem-
perature. Modify the threshold value if the previous configuration
is unreasonable. The recommended high threshold value is 40.
temperature is too high. If yes, take necessary cooling and venti-
lation measures.
Alarm Impact 1. If the alarm is caused by unreasonable threshold configuration,
service will not be affected.
2. If the alarm is caused by high room temperature, board opera-
tion might be abnormal and board services might be interrupted.
198025859 House temperature is

lower than low threshold
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Threshold configuration is unreasonable.
2. Actual temperature in equipment room is too low.
Suggestion alarm parameters), check the lower limit of equipment room tem-
perature. Modify the threshold value if the previous configuration
is unreasonable. The recommended low threshold value is 0.
temperature is too high. If yes, take necessary cooling and venti-
lation measures.
Alarm Impact 1. If the alarm is caused by unreasonable threshold configuration,
service will not be affected.
2. If the alarm is caused by low room temperature, board opera-
tion might be abnormal and board services might be interrupted.
198025860 Rack voltage is high

tion
Alarm Level Minor

Chapter 2 Alarm
Disaster Alarm Yes

Frequently No
Reported
Cause of Alarm 1. The configured threshold is unreasonable.
2. Actual voltage is too high.
Suggestion Alarm Parameters to view the upper threshold of rack voltage. If
the configuration is unreasonable, please modify it. For 48V power
supply, the recommended value of upper threshold is 57V; for 60V
power supply, the recommended value is 72.
2. Find out which line voltage exceeds upper threshold by using
the voltage index given in alarm details. Lower down the input
voltage of this line.
affected.
2. If the alarm is caused by high voltage, board may work abnor-
mally and board services may be interrupted.
198025861 rack voltage is low

tion
Alarm Level Minor
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm 1. Voltage value is under the low threshold.
2. The setting of the voltage detector is error.
3. Power input of a road may have been disconnected.
Suggestion alarm parameters), check the lower limit of rack voltage. Modify
the threshold value if the previous configuration is unreasonable.
For 48 V power, the recommended low threshold value is 40. For
60 V power, the recommended value is 50.
2. Locate the specific line whose voltage is below low threshold
according to the voltage index listed in alarm Details. Increase the
input voltage of that line.
affected.
2. If the alarm is caused by low voltage, board may work abnor-
mally and board services may be interrupted.

198025862 Humidity is high

tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
2. Actual humidity in equipment room is too high.
Suggestion Alarm Parameters to view the upper threshold of room humidity.
If the configuration is unreasonable, please modify it. The recom-
mended value of upper threshold is 90.
2. Check the hygrometer in equipment room to see if the actual
humidity is too high. If yes, take necessary dehumidifying mea-
sures.
affected.
2. If the alarm is caused by high room humidity, board may work
198025863 Humidity is low

tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
2. Actual humidity in equipment room is too low.
3. Setting of the sensor is incorrect.
Suggestion Alarm Parameters to view the lower threshold of room humidity.
If the configuration is unreasonable, please modify it. The recom-
mended value of upper threshold is 90.
2. Check the hygrometer in equipment room to see if the actual
humidity is too low. If yes, take necessary humidifying measures.

Chapter 2 Alarm

affected.
2. If the alarm is caused by low room humidity, board may work
198025864 Fault in fan plug-in box

tion
Alarm Level Minor
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm 1. FAN module is not tightly inserted into the rack.
2. FAN module hardware is faulty.
Processing 1. Check if the FAN module is tightly inserted into the rack. If no,
Suggestion unplug and plug the FAN module.
2. Replace FAN module.
Alarm Impact This alarm might lead to excessively high rack temperature, result-
ing in abnormal board operation and interruption of board services
198025865 Rack door alarm

tion
Alarm Level Minor
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm 1. The rack door is not closed.
2. Door control connection is incorrect.
Processing 1. Open and re-close the rack door to ensure that the rack door
Suggestion is tightly closed.
2. Open the rack door to check the installation of door control.
Ensure that the door access control is correctly installed and con-
nected. Then close the rack door.

Alarm Impact Service is not affected, but the alarm poses a potential safety haz-
ard.
198025866 Smoke detected

tion
Alarm Level Minor
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm 1. The alarm device is faulty.
2. The smoke density in equipment room is too high.
3. Setting of the sensor is incorrect.
Processing 1. Quick find the origin of smog.
Suggestion
2. If there is no smog in the equipment room, replace the smog
detector.
Alarm Impact Services won't be affected, but there is a potential safety problem.
198025867 Infrared alarm

tion
Alarm Level Minor
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm 1. Heat source (such as animal/human) comes near.
2. Configuration of Infrared sensor is incorrect.
3. Infrared sensor is faulty.
Processing 1. Check if any animal or human comes near the infrared sensor.
Suggestion If yes, remove the heat source. If no, check the infrared sensor
configuration. If appropriate, sensor sensitivity can be somewhat
reduced.
2. The infrared sensor is faulty. Replace sensor.
Alarm Impact 1. If the alarm is caused by infrared sensor configuration error,
system is not affected.

Chapter 2 Alarm
2. If the alarm is caused by infrared over threshold, be careful of

potential safety hazard in the equipment room.
198025868 Lightning alarm

tion
Alarm Level Major
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm Outdoor unit or equipment damaged by lightening.
Processing 1. Check earthing connection.
Suggestion
2. Check lightning protection antenna.
Alarm Impact The board may work abnormally due to lightning stroke. Accord-
ingly, board services will be interrupted.
198066064 Loss of DC power supply

to rack
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Circuit breaker has tripped.
2. No incoming DC supply from rectifier.
Processing Is this shelf needed?
Suggestion
1. If yes, ensure that the atmosphere switch is closed and ALM
indicator is normal.
2. If no, screen the function of monitoring atmosphere switch.
In NMS Configuration Management interface, click Power Board
Alarm Parameters; then set the status of atmosphere switch to be
screened.

Alarm Impact This shelf can not be supplied with power. All boards on the shelf
can not work and board services are interrupted.
QoS Alarm
198023296 Inter-board message
communication flow rate exceeds the
alarm threshold
Alarm Type QoS Alarm
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm The configured alarm threshold is less than the usual inter-board
communication traffic in input and output directions of the board
control plane.
Processing On NMS configuration management interface, check if the config-
Suggestion ured alarm threshold of communication traffic in input and output
directions of the board control plane is too low. Recommended
value: 0xffffffff(4096M).
Alarm Impact No impact on user service.
198066069 The number of times of

signaling data transfer exceeds the
allowed threshold of the license
tion
Alarm Level Major
Disaster Alarm No
Frequently Yes
Reported

Chapter 2 Alarm
Cause of Alarm 1.The number of allowed times of transfer is less than the actual
demand.
2.No proper license purchased.
Processing 1.Set the number of allowed times of transfer to a rational value.
Suggestion
2.Purchase proper license
Alarm Impact The data transferred may be discarded
198083042 IU PS traffic over load

alarm
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm IU PS traffic throughput exceed the threshold of license control.
Processing Check if the whole throughput is over the provider's guaranteed
Suggestion bandwidth limit authorized by license.
Alarm Impact The traffic over the license threshold would cause packet loss and
service quality decrease.
198083043 IU CS traffic over load

alarm
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm IU CS traffic throughput exceed the threshold of license control.
Alarm Impact The traffic over the license threshold would cause user service ac-
cess reject.

198083044 IU traffic over load alarm

tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm IU CS and PS traffic throughput exceed the threshold of license
control.
Alarm Impact The traffic over the license threshold would cause CS user service
access reject or PS service quality decrease.

Chapter 3
Notification
Table of Contents
198083017 RUB board has reached maximum number of
routes............................................................................ 111
198070002 Iu interface global reset notification .................. 111
198070003 Iu interface resource reset notification ............... 112
198070004 RNC initiate Iu interface global reset failure noti-
fication .......................................................................... 113
198070005 RNC initiate Iu interface resource reset failure no-
tification......................................................................... 113
198070008 RNC and Node B are configured with different
CCPID............................................................................ 114
198070009 Broadcast failure ............................................ 114
198083025 Common Channel is abnormal .......................... 116
198070010 FTP failure and file lost .................................... 117
198070011 RNC alarm storage disc is full ........................... 118
198083028 Performance file server unavailable ................... 118
198083029 Unable to save Performance File ....................... 119
198083019 MicroCode subsystem failed to get the table of
configuration .................................................................. 120
198083026 MicroCode subsystem failed to handle DHCP mes-
sage from other network .................................................. 122
198083030 Bandwidth automatic adjustment is useless ......... 123
198083032 TCP connect on IuBC interface is interrupted
.................................................................................... 124
198083033 The deviation of slave clock is too large. ............ 125
198083034 External Clock of Slave lost notification .............. 125
198083035 Transport Path Occupied BandWidth Over-
load............................................................................... 126
198083037 All Local Cell ID configured at RNC side are differ
from which on Node B side ............................................... 126
198020291 Protocol stack process failed to initialize during
power on........................................................................ 127
198020802 Conflicting IP address in subnet. ...................... 127
198020803 Conflicting MAC Addresses in Subnet ................. 128
198020804 Failed to generate static ARP from IP ad-
dress ............................................................................. 129
198066065 SCTP Primary Path Set Failed ........................... 130
198030016 Ethernet link OAM event .................................. 130
198000576 Loss of Frame on Trunk ................................... 131
198066050 MCC is faulty.................................................. 131
198001600 CPU resets on a board ..................................... 132
198017216 Error in MCS Multi-Core processor receiving con-
figuration data from DBS .................................................. 132
198018240 TCP Receives RST Packet ................................. 133
198018241 TCP Connection Aborted .................................. 133
198018242 MD5 Verification Failure ................................... 134
198018243 Wrong MD5 Message Abstract........................... 134

198023106 Board Self-Check Failure .................................. 135

198023107 The board initialization failure........................... 135
198023617 Configuration file is unusable............................ 136
198003138 FLASH device initialize failed ............................ 136
198003394 Start daylight saving time ................................ 137
198003395 End daylight saving time.................................. 137
198005441 Port status on internal media plane
changed. ........................................................................ 138
198005448 485 seriel bus link between CLKG/PWRD and OMP
is broken. ....................................................................... 139
198026177 CLKG reference quality changed ....................... 139
198026178 Clock work mode changed ............................... 140
198005705 MCU resets for abnormities .............................. 140
198005710 The result of base selection of sets chip ............. 140
198005711 clock reference selection is being executed. ......... 141
198005712 The manual select base will be run, please wait
for the result .................................................................. 141
198005713 APC's RAM error ............................................. 142
198005715 PP2S source switched ...................................... 142
198005717 The physical address information of the board is
incorrect ........................................................................ 143
198005716 Type B fault on board (GPS) phase-lock equip-
ment ............................................................................. 143
198005700 DSP resets for abnormities ............................... 144
198005701 Version Load Error .......................................... 145
198019777 APS switch over occurred ................................. 146
198005188 UIM CS Changeover ........................................ 147
198005192 Board's Work Mode Unsupported....................... 148
198005193 Notification of the power-on status of the basic
process .......................................................................... 148
198005956 Board Version Error......................................... 149
198005958 IDE Version Files Synchronization Informa-
tion ............................................................................... 150
198005961 OMP Version Check Information ........................ 150
198005962 Patch version operate fail................................. 151
198010560 No message response in the link for a long
time .............................................................................. 152
198011840 M3UA user office status change ........................ 152
198013888 ASP status changed ........................................ 153
198013889 AS status changed .......................................... 154
198013890 Sigtran error message received ........................ 154
198013891 Sigtran notification message received ................ 155
198013892 Allocate memory fail ....................................... 156
198014144 Association establishment failed........................ 156
198014145 Association restart .......................................... 157
198025664 Abnormal Half-fixed Connection Changes ........... 158
198008005 Memory file buffer overflow .............................. 159
198002625 Process is deadlocked...................................... 159
198002880 CPU occurs dead-loop...................................... 160
198005718 Two master clock ports is directly con-
nected ........................................................................... 160
198005189 Notification of Active/Standby Changeover ......... 161
198026176 Clock reference changed .................................. 161
198020805 ARP detect failed ............................................ 162
198020806 ARP detect that the static ARP is not match ......... 162
198015168 AAL2 Path blocked by resetting process ............. 163

Chapter 3 Notification
198083017 RUB board has

reached maximum number
of routes
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm Too many route entries are configured in the routing table.
For a VTCD-type RUB, the routing table can contain at most 360
entries. For a VTCD_2-type RUB, the routing table can contain at
most 1024 entries. The alarm is given when 90% capacity of the
routing table is used.
Processing 1. Open the NMS Configuration Management interface to delete
Suggestion unused routes from Static Routes.
2. Open the NMS Configuration Management interface to delete
the IP address of the unused port from Interface Configuration.
Alarm Impact 1. If the number of route entries does not exceed the capacity of
the RUB routing table, no service will be affected.
2. If the number of route entries exceeds the capacity of the RUB
routing table, some routes will be missing.
1) If the missing routes are from RNC to Node B or CN, UE services
will fail to access this board.
2) If the missing routes are from RNC to other RNC NEs, inter-RNC
UE services will fail to access this board. Meanwhile, the tick clock
for MBMS among relevant RNC NEs cannot be synchronized, which
will reduce the quality of MBMS.
3. If the number of route entries exceeds the capacity of the RUB
routing table, the SLA diagnosis function from RNC to a relevant
network element will fail.
198070002 Iu interface
global reset notification


tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. RESET message is sent by CN.
2. The signaling point of the office related to the CN is inaccessible.
3. Global reset is triggered by NMS.
Processing On NMS fault management interface, view notification Details
Suggestion where Alarm Reason is given. Locate the specific alarm handling
suggestion according to the given reason. The handling sugges-
tions that correspond to different reasons are described below.
1.CN reset.
1) RESET message is initiated by CN NMS. View CN NMS operation
log to see if the reset is initiated. If yes, no handling is necessary.
2) Check if transmission-related/board alarm occurs in the board.
If yes, refer to the corresponding alarm handling suggestion. Re-
lated alarms:
198066005 SCCP SSN is invalid
2.CN unaccessible. Check if transmission-related/board alarm oc-
curs. If yes, refer to the corresponding alarm handling suggestion.
Related alarms:
198066005 SCCP SSN is invalid
3.OMCR initiate IU reset. The alarm is caused by manual reset
operation. Check RNC NMS operation log to see if the reset oper-
ation exists. If yes, no handling is necessary.
Alarm Impact The services that have been established are released. Access of
new service is denied. Service access will be restored in 3 seconds.
198070003 Iu interface
resource reset notification
tion
Alarm Level Major

Disaster Alarm No
Frequently No
Reported
Cause of Alarm RNC sends a RESET RESOURCE message.
Processing Check if there is any of the following transmission-related alarms.
Suggestion If yes, follow the corresponding suggestions to handle it.
198066005 SCCP subsystem unavailable
Alarm Impact The resource resetting service is released.
198070004 RNC initiate Iu

interface global reset failure
notification
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm The CN fails to respond to the resetting request from the RNC.
Processing Check the basic information in the MSC SERVER/SGSN tab on the
Suggestion NMS Configuration Management interface to see if "MCC and MNC"
is consistent with that configured for the CN. If not, modify the
configuration.
Alarm Impact New services will be rejected for 3 seconds.
198070005 RNC initiate

Iu interface resource reset
failure notification


tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm The CN fails to respond to the resource resetting request from the
RNC.
Processing Check the basic information in the MSC SERVER/SGSN tab on the
Suggestion NMS Configuration Management interface to see if "MCC and MNC"
is consistent with that configured for the CN. If not, modify the
configuration.
Alarm Impact It has no impact on services.
198070008 RNC and Node B

are configured with different
CCPID
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm The CCP ID configured on the RNC side is different from that on
the Node B side.
Processing 1. Click Base Station Ground Resource Management > Transport
Suggestion Layer Management > SCTP stream configuration on the NMS Con-
figuration Management interface, and then modify the CCP ID.
2. Click NE Information Configuration on the NMS Configuration
Management interface. Select the corresponding Node B and mod-
ify its CCP ID in Node B port configuration.
Alarm Impact Neither CCP ID will be available during service establishments.
198070009 Broadcast failure



tion
Alarm Level Major
Disaster Alarm Yes
Frequently Yes
Reported
Cause of Alarm 1. The system broadcast of the cell is configured incorrectly.
2. The transmission fails.
Suggestion check the alarm cause, which can help you easily find the corre-
1. Alarm cause: Failure in getting system information from data-
base.
Check notification details, where "bySIBType" is given. For exam-
ple, "SIB type = 1" means that obtaining SIB1 fails. In this case,
check the Sib1-related parameters and make sure the configura-
tion is correct and complete.
Different types of SIBs correspond to different configurations,
which must be checked as follows:
1) SIB type = 1
On NMS configuration management interface (UE timers and con-
stants information), check UE timers and counters in idle and con-
nected status.
2) SIB type = 1
On NMS configuration management interface (UTRAN cell), check
URA ID in UTRAN cell global information.
3) SIB type = 1
On NMS configuration management interface (cell selection and
reselection), check cell selection/reselection information parame-
ters and cell access limit parameters.
4) SIB type = 1
On NMS configuration management interface (UTRAN cell), check
common transport channel parameters in SCCPCH and RACH.
2. Alarm cause: The system broadcast is beyond its capability.
Check if the Node B to which the faulty cell belongs generates any
of the following transmission-related alarms. If yes, follow the
corresponding suggestions to handle it.
1) IP Mode
Check to see if there is any of the following alarms according to
the association ID. If yes, follow the corresponding suggestions to
handle it.
2) ATM Mode
a. Bottom layer transmission fault


b. Unavailable PVC link
Related alarm: 198018944 PVC Fault
Alarm Impact The cell is unavailable and inaccessible, providing no service.
198083025 Common
Channel is abnormal
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. User plane resource initialization failure.
2. CCH setup failure at Node B side.
3. CCH configuration is deleted by OMCR.
4. The Bearer type of common transport channel is modified by
OMCR.
Suggestion check the Alarm Reason, which can help you easily find the corre-
1. Alarm Reason: User plane resource initialization failure.
1) Click NE Information Configuration on the NMS Configuration
Management interface and select the corresponding Node B. Select
the Path Configuration tab to check if all parameters, including the
forwarding bandwidth, are correctly configured.
2) Click Path Group Configuration on the NMS Configuration Man-
agement interface to check if all parameters are correctly config-
ured.
2. Alarm Reason: CCH setup failure at Node B side.

Click Base Station Ground Resource Management on the NMS Con-

figuration Management interface and select IP and Route Manage-
ment to check the IP parameters. Make sure that at least one
"COS" is selected.
3. Alarm Reason: CCH configuration is deleted by OMCR.
This alarm will be processed automatically by the system. The RNC
will initiate the process of common channel deletion. No manual
handling is required.
4. Others.
The system will automatically reestablish the common channel. No
manual handling is required.
Alarm Impact The common channel is unavailable, which falls into three cases.
1. If the S-CCPCH that carries FACH is unavailable, the CS/PS
services initiated by the UE will fail.
2. If the S-CCPCH that carries PCH is unavailable, the paging func-
tion of the system cannot be used and the CS/PS services initiated
by the CN will fail.
3. If the PRACH that carries RACH is unavailable, the UE cannot
access this cell.
198070010 FTP failure and

file lost
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm The FTP channel between NMS and RNC NE is faulty.
Processing Perform alarm synchronization on the NMS Alarm Management in-
Suggestion terface to obtain the latest alarm information from the RNC when
the link between the NMS and the RNC is normal, so that the alarm
information of the NMS is consistent with that of the RNC.
Alarm Impact The NMS cannot obtain alarm files from the RNC and the alarm
information is lost. It has no impact on services.

198070011 RNC alarm

storage disc is full
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Disk is full.
2. Disk is faulty.
Processing 1. Delete unnecessary files from the hard disk or move them to
Suggestion an external storage device.
2. Replace the hard disk, or the board where the hard disk is
installed.
3. Perform alarm synchronization on the NMS Alarm Management
interface to obtain the latest alarm information from the RNC when
the link between the NMS and the RNC is normal, so that the alarm
information of the NMS is consistent with that of the RNC.
Alarm Impact The RNC cannot save alarm files and the alarm information is lost.
It has no impact on services.
198083028 Performance file

server unavailable
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Performance file server unavailable.
2. Break in communication between RNC and PM server
Processing 1. Check the log server to see if the LogService runs normally.
Suggestion If not, restart the LogService by running "/startsys" under the
"/home/zte/LogService/bin" directory.

2. Check if the control-plane communication between the log

server and the ROMP is normal by performing the following steps:
i. Open a terminal dialog box in the LINUX system.
ii. Enter the SHELL command "ping 128.0.31.1" to see if the ping
test is successful. If not, troubleshoot the control-plane commu-
nication.
Alarm Impact The Logservice cannot receive performance files and the perfor-
mance files are saved on the ROMP..
198083029 Unable to save

Performance File
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. The free disk space of the LogService is less than 100M.
2. The LogService version is incompatible with the ROMP version.
3. The LogService is unavailable and the free disk space of the
ROMP is less than 100M.
4. Board time is adjusted.
5. The Logservice is unavailable, and the PM files have already
existed for over two hours.
Processing Check alarm details to find the Failure cause during saving perfor-
Suggestion mance file, and handle the alarm accordingly.
1. If the Failure cause is "Logservice disk space less than 100M",
delete unnecessary files from the Logservice disk to release
enough space.
2. If the Failure cause is "Directory on Logservice is different from
that on ROMP", it means the Logservice version is incompatible
with the ROMP version. Use the correct Logservice version.
3. If the Failure cause is "Logservice is unavailable and the space
of ROMP disk is less than 100M"
1) Delete unnecessary files from the ROMP disk to release enough
space.
2) Handle it according to the suggestions given for the alarm
"198083028 Logservice is unavailable".
4. If the Failure cause is "The session ends abnormally and the
performance file can not be saved", it means the board time has
been adjusted. In this case, no handling is required.

5. If the Failure cause is "The Logservice is unavailable, and the

PM files have already existed for over two hours." the suggestion
is given for the alarm "198083028 Logservice is unavailable".
Alarm Impact Either the LogService or the ROMP cannot save the performance
files. Performance data will be lost.
It has no impact on services.
198083019 MicroCode
subsystem failed to get the
table of configuration
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Failed to get the information of the RUIB.
2. Failed to get the configuration of OMCB server.
3. Failed to get the configuration of signal dispatch table.
4. Failed to get the configuration of IP/UDP.
5. Failed to get the configuration of L2 table.
6. Failed to get the configuration of path information.
7. Failed to get the configuration of pathgroup information.
8. Failed to get the configuration of IUBC signal dispatch table.
Processing On NMS alarm management interface, view notification Details
Suggestion where Alarm Reason is given. Locate the specific handling sug-
gestion according to the given reason. The handling suggestions
that correspond to different reasons are described below.
1.Alarm Reason: Failed to get the information of the RUIB. On
NMS configuration management interface, check whether “Board
Reassembling IP Fragments” is configured. If no, perform the cor-
responding configuration according to network planning. Make
sure to synchronize the configuration data at NMS and RNC NE
after configuration modification. Only after synchronization can
the configuration data take effect at RNC NE.
2.Alarm Reason: Failed to get the configuration of OMCB server.
On NMS configuration management interface, check whether mas-
ter OMP IP is configured. If no, perform the corresponding con-
figuration according to network planning. Make sure to synchro-
nize the configuration data at NMS and RNC NE after configuration

modification. Only after synchronization can the configuration data

take effect at RNC NE.
3.Alarm Reason: Failed to get the configuration of signal dispatch
table. On NMS configuration management interface (SCTP asso-
ciation configuration), check whether the relevant office is con-
figured. If no, perform the corresponding configuration according
to network planning. Make sure to synchronize the configuration
data at NMS and RNC NE after configuration modification. Only af-
ter synchronization can the configuration data take effect at RNC
NE.
4.Alarm Reason: Failed to get the configuration of IP/UDP. On NMS
configuration management interface (service IP for DSP), check
whether the relevant office is configured in DSP service IP address.
If no, perform the corresponding configuration according to net-
work planning. Make sure to synchronize the configuration data
at NMS and RNC NE after configuration modification. Only after
synchronization can the configuration data take effect at RNC NE.
5.Alarm Reason: Failed to get the configuration of L2 table. Make
sure to synchronize the configuration data at NMS and RNC NE
after configuration modification. Only after synchronization can
the configuration data take effect at RNC NE.
6.Alarm Reason: Failed to get the configuration of path informa-
tion. On NMS configuration management interface (path configu-
ration), check whether the relevant office is configured. If no, per-
form the corresponding configuration according to network plan-
ning. Make sure to synchronize the configuration data at NMS and
RNC NE after configuration modification. Only after synchroniza-
tion can the configuration data take effect at RNC NE.
7.Alarm Reason: Failed to get the configuration of pathgroup infor-
mation. On NMS configuration management interface (path group
configuration), check whether the relevant office is configured. If
no, perform the corresponding configuration according to network
planning. Make sure to synchronize the configuration data at NMS
and RNC NE after configuration modification. Only after synchro-
nization can the configuration data take effect at RNC NE.
8.Alarm Reason: Failed to get the configuration of IUBC signal dis-
patch table. On NMS configuration management interface (IUBC
dispatch configuration), check whether the dispatch information
is configured. If no, perform the corresponding configuration ac-
cording to network planning. Make sure to synchronize the config-
uration data at NMS and RNC NE after configuration modification.
Only after synchronization can the configuration data take effect
at RNC NE.
Alarm Impact The system impacts that correspond to different alarm causes are
described below.
1. Failed to get the information of the RUIB. The configuration
information is used to reassemble the fragments of IP packets in-
putted into the equipment. Lacking the configuration information
may cause processing failure of fragments of IP packets. Ser-
vice interruption might occur or service processing rate might slow
down.
2. Failed to get the configuration of OMCB server. Lacking the
configuration information may paralyze OMCB function.
3. Failed to get the configuration of signal dispatch table. Lacking
the configuration information causes SCTP data transmission fail-

ure on the interface board. The service related to SCTP Protocol

on this board is down.
4. Failed to get the configuration of IP/UDP. Lacking the config-
uration information may cause processing failure of IUPS service,
or processing failure of other data based on IP transmission.
5. Failed to get the configuration of L2 table. Lacking the config-
uration information may cause communication failure within the
equipment. All services on the board might be down.
6. Failed to get the configuration of path information. In the case
of ATM interface board, lacking the configuration information may
incur processing failure of the AAL2 data based on ATM Adaptation
Layer Protocol, leading to interruption of IUB/IUCS/IUR services
under this office. In the case of IP interface board, lacking the
configuration information may incur processing failure of IP packet
traffic control, leading to interruption of all services under this of-
fice.
7. Failed to get the configuration of pathgroup information. In the
case of ATM interface board, lacking the configuration information
may incur processing failure of the AAL2 data based on ATM Adap-
tation Layer Protocol, leading to interruption of IUB/IUCS/IUR ser-
vices under this office. In the case of IP interface board, service
is not affected.
8. Failed to get the configuration of IUBC signal dispatch table.
Lacking the configuration information causes IUBC signal trans-
mission failure on the interface board. The service related to IUBC
signal on this board is down.
198083026 MicroCode
subsystem failed to handle
DHCP message from other
network
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. OMCB IP is unconfigured by RNC.
2. The remote IP address of PPP/MLPPP link is unconfigured.
3. Information of DHCP Client is unconfigured.


Suggestion where Fail Cause is given. Locate the specific handling suggestion
which corresponds to the listed cause. The handling suggestions
that correspond to different causes are described below.
1.Fail Cause: RNC OMCB IP to Node B has not been configured.
On NMS configuration management interface, check if “Manager
Node B IP” is configured. If no, add the configuration.
2.Fail Cause: Peer IP Address of PPP/MLPPP Link has not been
configured. On NMS configuration management interface (PPP pa-
rameter), check if remote IP address is configured. If not, add the
configuration.
3.Fail Cause: Information of DHCP Client has not been config-
ured. Compare DHCP Client's Identifier Information with engineer-
ing plan, and config corresponding DHCP Client's Information On
NMS configuration management interface.
Alarm Impact The system impacts that correspond to different notification
causes are described below.
1. RNC OMCB IP to Node B has not been configured. Case 1 If Node
B has never fetched the OMCB channel configuration information
(including OMCB SERVER IP address, OMCB gateway IP, and Node
B IP address) before notification occurs, OMCB channel of the Node
B would be blocked. Node B’s failure to fetch IP address would
lead to its failure to get other configuration information. Thus the
service as a whole is affected. Case 2 Node B has fetched the
OMCB channel configuration information (including OMCB SERVER
IP address, OMCB gateway IP, and Node B IP address) before no-
tification occurs. If there is no configuration modification, OMCB
channel would not be affected. If there is configuration modifica-
tion before notification occurs, OMCB channel would be affected
in such a way that modified service configuration data fail to take
effect on Node B.
2. Peer IP Address of PPP/MLPPP Link has not been configured.
Association link is interrupted. All services on the board are down.
3. Information of DHCP Client has not been configured. DHCP
Client will not get Traffic Address, and service to the Client is bro-
ken.
198083030 Bandwidth
automatic adjustment is
useless
tion
Alarm Level Minor
Disaster Alarm No

Frequently No
Reported
Cause of Alarm The intermediate equipment such as Router or Switch is out of ser-
vice, all the packets will be lost at the brocken-down equipment,
packet loss rate on this path is invariable. In this case, decrease
the available bandwidth is useless, so bandwidth automatic ad-
justment does not be executed.
Processing Check the intermediate equipment.
Suggestion
Alarm Impact Packet loss rate on this path is invariable, call loss might occur,
and access success rate of PS service might decline.
198083032 TCP connect on

IuBC interface is interrupted
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. The local IP address or remote IP address configuration is in-
correct.
2. Interface board (GIPI) of local equipment is faulty.
3. Intermediate equipment or opposite equipments faulty.
4. The network cable connection is loose or disconnected.
Processing 1. On NMS configuration management interface, check local IP
Suggestion address, remote IP address and TCP connection mode. If the con-
nection mode at local end is configured as client, the connection
mode at opposite end should be configured as server. Vice Versa.
2. On NMS configuration management interface, check protocol
stack configuration at both ends. In the case of direct connec-
tion, ensure that interface board addresses at both ends are in the
same network segment, and the next hop address is direct con-
nect interface board address. In the case of not direct connection,
ensure that the next hop address is the intermediate equipment
address.
3. Check the interface board (GIPI) for the Related Alarms. Per-
form the recommended solution to process the possible alarms.
Related Alarms: 198066070 Board Offline or the CPU is in long
period reset status
4. Telnet to the interface board. Set a destination IP and ping it.
In the case of direct connection, ping the direct connect interface
board address. In the case of not direct connection, ping the inter-

mediate equipment. If response timeout, contact the equipment

provider for solution.
5. Check the physical connection on IuBC interface. If the con-
nection is loose or broken, unplug and plug the cable or replace
the cable. If port indicator is on, the physical link must be normal.
Alarm Impact The IuBC Broadcast is disabled.
198083033 The deviation of

slave clock is too large.
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm Clock crystal oscillator of Slave or Host is inaccurate. The inaccu-
racy result in Clock Deviation between Slave and Host over thresh-
old (default threshold is 36 sec/hr) .
Processing Lock the faulty Slave.
Suggestion
Alarm Impact KPI Index of service in RNC will be low.
198083034 External Clock

of Slave lost notification
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm External Clock of Slave Lost.
Processing Lock the faulty Slave.
Suggestion

Alarm Impact KPI Index of service in RNC will be low.
198083035 Transport
Path Occupied BandWidth
Overload
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm Available bandWidth of transport path is less than occupied band-
Width. Probable causes for the alarm include:
1.E1 link is broken.
2.Transmission quality of the transmission line is poor.
3.Intermediate equipment is faulty.
Processing 1.Check the E1 link.
Suggestion
2.Check the transmission quality of intermediate equipment.
Alarm Impact The available bandwidth to destination is less than occupied band-
width. Some services would be released in this transport path
selectively to avoid transport path congestion.
198083037 All Local Cell ID

configured at RNC side are
differ from which on Node B
side
tion
Alarm Level Minor
Disaster Alarm No

Frequently No
Reported
Cause of Alarm 1. The RNC is connected with other Node B incorrectly, not the
wanted Node B.
2. The radio resource data configured at RNC side and Node B side
is inconsistent.
Processing 1Check if the RNC is connected with Node B correctly on Iub inter-
Suggestion face. If not, please reconnect RNC and Node B, and synchronize
the configuration data to Node B. 2Check if the radio resource data
configured at RNC and Node B is consistent. If not, please modify
the radio resource data correctly, and synchronize the configura-
tion data to RNC and Node B.
Alarm Impact All cell belong to the Node B can not be established.
198020291 Protocol stack

process failed to initialize
during power on
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm Physical memory is insufficient
Processing Ensure that the actual capacity of the physical memory is more
Suggestion than 1GB.
Alarm Impact RPU board will reboot automatically after 10 seconds.
198020802 Conflicting IP
address in subnet.
tion
Alarm Level Major

Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. This network port is configured with the same IP address (in-
cluding the virtual address in the same network segment) as an-
other host in the local network.
2. The peer-end switch that connects with this network port has
a loop.
Processing When an IP address conflict occur, the NMS will display the con-
Suggestion flicted IP address. Meanwhile, the 5-tuple information of the con-
flicted local port, as well as the conflicted MAC address of the ex-
ternal device, can be detected.
1. Click Interface Configuration on the NMS Configuration interface
to check the local interface address. Modify the local interface
address or the IP address of the conflicted external device.
Refer to the corresponding equipment maintenance manual to
learn how to query the IP address of external device.
2. The switch connected with the local port must have a loop if
the following two conditions are satisfied:
1) "198020802 Conflicting IP Address" and "198020803 Conflict-
ing MAC Address in Subnet" concur;
2) Even though the local port IP address is changed, the two alarms
still exist.
In this case, check whether there is a cable that connects both
ports of the peer-end switch. If yes, remove the cable.
Alarm Impact Board operation is normal. Communication network is faulty. All
services on this port are down.
198020803 Conflicting MAC

Addresses in Subnet
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. The MAC address of this port is the same with another MAC
address in the direct connect network.
2. Loop exists in the remote switch connected with this port.
Processing When an MAC address conflict occurs, the NMS will display the
Suggestion conflicted MAC address. Meanwhile, the 5-tuple information of the

conflicted local port, as well as the conflicted MAC address of the

external device, can be detected.
1. Modify the MAC address of the local port or the conflicted MAC
address of the external device.
Find the conflicted local port according to the displayed 5-tuple in-
formation. Click Interface Configuration on the NMS Configuration
interface and select "MAC Address" to check and modify the MAC
address of the local port.
Refer to the corresponding equipment maintenance manual to
learn how to query the MAC address of the external device.
2. The switch connected with the local port must have a loop if
the following two conditions are satisfied:
1) "198020802 Conflicting IP Address" and "198020803 Conflict-
ing MAC Address in Subnet" concur;
2) Even though the local port IP is changed, the two alarms still
exist.
In this case, check whether there is a cable that connects both
ports of the peer-end switch. If yes, remove the cable.
Alarm Impact Board operation is normal. The notification leads to packet lookup
failure in Layer 2 forwarding table. Then packet loss occurs and
all services related to this port will be down.
198020804 Failed to
generate static ARP from IP
address
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm Failed to generate static ARP from the newly added IP address,be-
cause the number of static ARPs which generated by IP has
reached the maximum.
Processing Delete some proxy addresses configured for virtual ports and
Suggestion re-configure IP address within the limit of static ARPs.
Alarm Impact The external device failed to communicate with the IP address from
which no static ARP is generated.

198066065 SCTP Primary

Path Set Failed
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm The remote IP of the SCTP primary path configured at application
layer is not included in the local address list of SCTP at opposite
end
Processing On NMS fault management interface, view notification Details,
Suggestion where information of association ID and the primary path remote
IP address is given. If the primary path remote IP address listed
in notification Details is selected as the primary path, follow the
steps below at opposite end.
1. Add the IP as an interface address at opposite end.
2. Add the "primary path remote IP address" given in notification
Details into the local IP address list of the relevant SCTP.
Alarm Impact This notification informs user of the update failure of SCTP primary
path. The primary path currently in use is not affected. No impact
on service.
198030016 Ethernet link

OAM event
tion
Alarm Level Major
Disaster Alarm No
Frequently Yes
Reported
Cause of Alarm The number of wrong frames or wrong symbols exceeds the
threshold.
Processing Check Ethernet linkreceiver and transmitter of link.
Suggestion
Alarm Impact Ethernet links can not transmit data credibly.

198000576 Loss of Frame

on Trunk
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm Since frequency difference might exist between trunk line clock
and local receive clock, the trunk receive clock is not synchronous
with the transmit clock.
Processing Check the clock synchronization status at both sides. If the status
Suggestion is unsynchronized, check if LOL-related (loss of lock) alarm occurs
in clock board. If yes, refer to the corresponding alarm handling
suggestion.
Related alarms:
Alarm Impact Momentary fault occurs to trunk data service or signaling channel.
If fault occurs repeatedly, CS/PS service might become unstable.
Otherwise, service is not affected.
198066050 MCC is faulty

tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm Check SPB/SPB_2/IWFB if they are working normal.
Processing 1. Unplug the board for 5 seconds, and plug it again after a full
Suggestion discharge.

Alarm Impact All MCC channels cannot transmit or receive data.
198001600 CPU resets on a

board
tion
Alarm Level Major
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm 1. User request CPU reset.
2. Board has reset itself due to fault.
Processing 1. Check the NMS operation log to see whether there is a manual
Suggestion reset record. If yes, no handling is necessary.
Alarm Impact The relevant services or communication links will be interrupted
or disconnected. This alarm will be recovered after the board is
powered on normally.
198017216 Error in MCS

Multi-Core processor
receiving configuration
data from DBS
tion
Alarm Level Major
Disaster Alarm No
Frequently Yes
Reported
Cause of Alarm 1.The configuration data from DBS are exceptional.
2.Failure in adding a vital data table

Processing Check the data configuration, if there is a configuring error, correct

Suggestion it and reboot the board.
Alarm Impact It may cause packet forwarding problem since some vital data ta-
ble is absent.
198018240 TCP Receives

RST Packet
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1.The peer end initiates tcp connection resetting and sends a RST
packet.
2.The peer end receives invalid tcp connection and returns a RST
packet.
Processing Check if there is severe packet loss in physical link (It can be
Suggestion checked by ping command), and handle physical link faults.
Alarm Impact The corresponding connection aborts.
198018241 TCP Connection

Aborted
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. The RNC is connected with other Node B incorrectly, not the
wanted Node B.
2. The radio resource data configured at RNC side and Node B side
is inconsistent.

Processing 1Check if the RNC is connected with Node B correctly on Iub inter-
Suggestion face. If not, please reconnect RNC and Node B, and synchronize
the configuration data to Node B. 2Check if the radio resource data
configured at RNC and Node B is consistent. If not, please modify
the radio resource data correctly, and synchronize the configura-
tion data to RNC and Node B.
Alarm Impact All cell belong to the Node B can not be established.
198018242 MD5 Verification

Failure
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm MD5 verification is not set for packets in application layer.
Processing Check MD5 encrypted option of the two ends of application layer.
Suggestion If an end does not set with MD5 encrypted option, then set MD5
encrypted option for this end.
Alarm Impact Application layer communication failure.
198018243 Wrong MD5

Message Abstract
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm When application layer is receiving messages, MD5 cryptographic
keys set on both ends are inconsistent.
Processing Check if MD5 cryptographic keys set on both ends are the same.
Suggestion
Y->Please contact ZTE Corporation.

N->Set the same MD5 cryptographic keys for both ends of appli-
cation layer and finish the alarm handling.
Alarm Impact Application layer communication failure.
198023106 Board
Self-Check Failure
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm Board hardware is faulty.
Processing Replace board.
Suggestion
Alarm Impact The board fails to power on possibly, and the service or communi-
cation link related to this board is down.
198023107 The board

initialization failure
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Suggestion
Alarm Impact The board fails to power on and operate, resulting in UE access
failure and interruption of ongoing services.

198023617 Configuration
file is unusable
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm During the process of system power-on,the DAT file obtained from
VMM is unusable or the txt file which saves configuration data is
unusable.
Processing On NMS fault management interface, view the alarm details, which
Suggestion give the Additional Reason.
1.If it's the DAT file error, then we need to reload the file from VMM
and switch to the new file.
2.if it's the TXT file error,then take the following step:
1)Get the TXT file from "/DOC0/DATA1" directory at RPU with File
Manager method.
2)Open the TXT file and delete line "[CRC_DATFILE]=" and
"[CRC_TXTFILE]=".
3)Transmit the modified TXT file.
4)Reboot RPU.
Alarm Impact 1. DAT file is unusable This error will make the saved data un-
restorable and unconfigurable if the configured data was saved in
TXT file.
2. TXT file is unusable This error will make the saved data un-
restorable.
198003138 FLASH device

initialize failed
tion
Alarm Level Major
Disaster Alarm Yes

Frequently No
Reported
Cause of Alarm The flash on the board is damaged.
Processing Replace the relevant boards.
Suggestion
Alarm Impact 1. For a single OMP board, the flash fault may cause board start
up failure. For both master/slave boards with flash fault the entire
system may have start up failure.
2. For other boards, the board may start up normally with out
impact on its service.
198003394 Start daylight

saving time
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm Daylight saving time activated, clock changed accordingly
Suggestion
Alarm Impact No impact
198003395 End daylight

saving time
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm Daylight saving time is de-activated and the system is back to
normal country clock


Suggestion
Alarm Impact No impact
198005441 Port status

on internal media plane
changed.
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Connection between UIM/GUIM and GLI is faulty.
2. Board is faulty.
Suggestion where information of "Port status" is given.
1.If the port status is "Master port invalid status" or "Master port
abnormal", refer to the following handling suggestions.
i. Reconnect the cable between UIM/GUIM and GLI.
ii. Replace the optical module or cable used for the connection
between UIM/GUIM and GLI.
iii. Replace UIM/GUIM board.
iv. Replace GLI board.
2.If the port status is others, no handling is necessary.
Alarm Impact The impact varies depending on the "Port status" given in notifi-
cation Details.
1. If the port status is "Master port invalid status" or "Master port
abnormal", the master port fails to forward inner media stream,
and the services on master port will be switched to slave port.
If the slave port is also unavailable, services on the port will be
interrupted.
2.If the port status is "Slave port invalid status" or "Slave port
abnormal", service will not be affected. However, the potential
hazard will emerge once master/slave switching occurs
3.If the port status is others, service will not be affected.

198005448 485 seriel bus

link between CLKG/PWRD
and OMP is broken.
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. 485 communication is interrupted.
2. The board is abnormal.
Processing 1. Unplug and plug the 485 cable.
Suggestion
2. Replace the 485 cable.
Alarm Impact The configured clock reference/environment threshold fails to take
into effect. There is no impact on services.
198026177 CLKG reference

quality changed
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm Clock quality of the CLKG board has changed.
Processing Check the quality of external clock source.
Suggestion
Alarm Impact System could not get the needed clock.

198026178 Clock work

mode changed
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm The clock work mode of the CLKG board has changed.
Suggestion
Alarm Impact System could not get the needed clock.
198005705 MCU resets for

abnormities
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm MCU Hardware is faulty.
Suggestion
Alarm Impact CLKG_2 board is faulty.
198005710 The result of

base selection of sets chip


tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm After manual base switchover, man-machine command, or press-
ing panel button, SETS chip performs base locking operation (at
most for 2 minutes). This notification is to inform the user of the
operation result of manual base selection
Suggestion
Alarm Impact None.
198005711 clock reference

selection is being executed.
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm If previous operation about clock reference selection doesn't finish
and relevant result is not given yet, the system will screen any
new attempt to manually select clock reference. And in this case,
this notification is declared.
Suggestion
Alarm Impact No impact on service.
198005712 The manual

select base will be run,
please wait for the result


tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm The notification is declared after selecting base via panel button,
to remind user that the base selection is in process and to request
user to wait for the operation result
Suggestion
Alarm Impact None.
198005713 APC's RAM

error
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Suggestion
Alarm Impact The board where RAM is located is down. ATM cell fails to be for-
warded, and all board services are interrupted.
198005715 PP2S source

switched
tion
Alarm Level Minor
Disaster Alarm No

Frequently No
Reported
Cause of Alarm PP2S (Pulse Per 2 Seconds) source is changed at both system clock
and GPS receiver sides.
Processing GPS-side PP2S has a higher priority. If PP2S is switched over from
Suggestion GPS-side to system-side, check the GPS receiver and antenna feed
status.
Alarm Impact None.
198005717 The physical

address information of the
board is incorrect
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. The DIP switch setting changes
2. The board is not inserted in position
Processing 1. Reset the board. After the resetting, the board re-calculates
Suggestion and sets the MAC address according to the DIP switch.
2. Insert the board tightly. Or, unplug and plug the board.
Alarm Impact The board fails to start up, or control plane communication is ab-
normal. As a result, users cannot gain access and existing services
are interrupted.
198005716 Type B fault on

board (GPS) phase-lock
equipment
tion

Alarm Level Major

Disaster Alarm No
Frequently No
Reported
Cause of Alarm Type B Fault on Board (GPS) Phase-lock Equipment are generated
by singlechip processor. Probable alarm causes include antenna
feeder short circuit or open circuit, poor quality of received satellite
signals or difficulty in receiving satellite signals, and large phase
difference of 10M OCXO assistant phase control.
Processing Check the antenna feeder input circuit of ICM board to ensure that
Suggestion the board can best receive GPS signal source. The checking items
include:
1) The position of the receiving antenna. The antenna should be
installed in an open area, far away from high buildings and clear
from shades. The effective visibility angle of the antenna should
be greater than 150 degrees.
2) The connection of the power splitter and front panel. The power
splitter and the front panel connector should be in good contact
and properly connected.
Alarm Impact Class B fault has no impact on system clock and services in 48
hours. After 48 hours, the fault might lead to system clock offset
and system synchronization failure. When GPS signal is poor, the
alarm will be repeatedly declared/restored. As long as the alarm
persists for no more than 48 hours, system clock and service will
not be affected. When system clock loss/offset occurs, its subse-
quent impact on service is described below.
1.For TDM transmission, all links based on the TDM transmission
medium (including the transmission link currently in service for UE
and cell transmission link) are affected. Packet loss might occur on
these links, leading to degradation of service quality. In the case
of serious packet loss, service interruption and handover failure
will occur. Even worse, the cell might be out of service.
2.For non-TDM transmission (for example, IP transmission), Iub
interface service is affected, while Iur interface and Iu interface
services are not affected. The clock that Node B derives from RNC
via IEEE1588 is inaccurate. When RNC clock frequency offset is
no more than 0.05 ppm, Node B synchronization will not fail, but
success rate of inter-RNC inter-Node B soft handover might fall.
When RNC clock frequency offset exceeds 0.5 ppm, Node B will
fail to lock the clock. In this case, Node B will oscillate freely and
success rate of inter-Node B soft handover might fall.
198005700 DSP resets for

abnormities
tion

Alarm Level Major

Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm 1. DSP chip is faulty.
2. Board is faulty.
Processing DSP resets automatically and abnormally.
Suggestion
1.If power-on is normal after DSP reset, the board can be restored
to normal state.
2.If DSP resets repeatedly, replace the board or subcard.
Alarm Impact DSP is unavailable during reset, but will be restored to normal
state after reset. During reset, cells on the DSP are out of service,
services on the DSP are interrupted, and call loss increases.
198005701 Version Load

Error
tion
Alarm Level Major
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm The equipment is abnormal in the process of version loading, which
falls into three cases.
1. The equipment fails to fetch the needed version.
2. Version loading to chip fails.
3. Chip hardware is faulty.
Suggestion where "Loading corresponding alarm information" is given. Lo-
cate the corresponding handling suggestion based on the given
information.
1. Any of the following items displayed by "Loading correspond-
ing alarm information" indicates that the chip fails to obtain the
needed version. On NMS software management interface, check
the configured version for the chip and version status. Ensure that
the needed version is configured for the chip and the version is ac-
tivated.
i. DSP6416 No.d : No Version Information
ii.DSP5402 No.d : No Version Information
iii. MC fail to get version information

iv. OCT6100 fail to get version information

v. M82620 : Index = d fail to get version information
2. If information other than the items listed above appears, refer
to the following handling suggestion.
i. Reset board.
ii. Replace DSP subcard.
iii.Replace board.
Alarm Impact 1. Microcode version loading fails, leading to repeated board reset
and interruption of board services.
2. Firmware/single-chip computer version loading fails, leading to
abnormal board operation and interruption of board services.
3. DSP version loading fails. Cells on the DSP will be out of service.
Services on the DSP are interrupted, and the number of call loss
increases.
198019777 APS switch over

occurred
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Optical interface is faulty such as LOS/SF/SD alarm.
2. In inter-board backup mode, one of the following events occurs.
i. Input clock lost
ii. Inner HW/LVDS alarm
iii. Inner media plane port alarm
iv. ENUM open (board not properly inserted)
v. Board reset (the board where the working optical interface is
located)
3. Changeover operation is initiated by the opposite end.
4. In recovery mode, fault recovery time at optical interface ex-
ceeds 5 minutes.
5. APS changeover request/clearance is initiated by NMS.
Processing View operation & maintenance log to see whether there is a
Suggestion record, indicating an operator manually initiates APS changeover
request/clearance. If yes, no handling is necessary. If no, check

whether there is one of the following alarms. If yes, please solve

the problem according to corresponding handling suggestions.
Related alarms:
198005396 Exceptional Internal Media Plane Communication
198005378 Board HW Error
198005635 The board is not plugged firmly.
Alarm Impact During APS changeover process, the link is interrupted for 10 ~
50 ms. Few packets may be lost, but services won't be affected.
198005188 UIM CS
Changeover
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Optical module signal loss occurs.
2. Board input clock loss occurs.
3. Bit error rate at the optical interface is high.
4. Lock loss occurs to the phase-locked loop.
5. Bit error rate on the master/slave interconnecting link of GUIM
board is high.
Processing Check if the following alarm occurs in local/opposite board. If
Suggestion yes, refer to the corresponding alarm handling suggestion. Re-
lated alarms:
198001286 Loss of Clock When Input to Board
198005646 Phase-lock Loop Unlock
Alarm Impact No impact on service.

198005192 Board's Work

Mode Unsupported
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. The configured board backup mode is unsupported
2. FPGA is unloaded, leading to setting failure of board working
mode.
Processing 1. Check the configuration of board backup mode. If the config-
Suggestion ured backup mode is not supported by the board, modify config-
uration or replace the board with one that supports such configu-
ration.
2. Unplug and plug board. Reload FPGA version.
Alarm Impact Board master/slave backup function is disabled.
198005193 Notification of
the power-on status of the
basic process
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Board power-on is successful.
2. Board power-on fails or expires.
Suggestion where information of power-on status ("Board poweron success-
ful/failed/timeout") is given. Locate the corresponding handling
suggestion based on the given information. The handling sugges-

tions that correspond to different power-on status are described

below.
1. Board poweron successful/failed/timeout: Poweron successful
No handling is necessary.
2. Board poweron successful/failed/timeout: Poweron timeout En-
sure that the board loads the proper version. The boards in a NE
must use the version of the same version No..
3. Board poweron successful/failed/timeout: Poweron failed En-
sure that the board loads the proper version. The boards in a NE
must use the version of the same version No..
Alarm Impact If the notification is power-on success, service will not be affected.
If the notification is power-on failure, the services on the board will
be unavailable.
198005956 Board Version

Error
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. A board is in the slot which is not configured with any board.
2. Board version is unconfigured.
3. Board version has been configured, but version file does not
exist or is damaged.
Processing 1. On NMS configuration management interface (rack), view rack
Suggestion layout. Check if the slot is configured with any board. If no board
configuration exists, unplug the board in the slot.
2. On NMS fault management interface, view notification Details
where "Version type of abnormal board" is given. Load and acti-
vate the version on NMS software management interface according
to the given "Version type".
Alarm Impact The board fails to obtain version, leading to abnormal board oper-
ation and access failure of board services.

198005958 IDE Version

Files Synchronization
Information
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm Synchronization of master/slave OMP version files occurs.
Suggestion where "Synchronization information" is given.
1. If synchronization information is "Failed to obtain file record
during synchronization" or "Synchronization failed", find the name
of the version file in notification Details. According to the given file
name, locate on NMS software management interface the corre-
sponding version configuration in the version file database. Reload
the version file to RNC NE. Delete the version file if it is not in use.
2. If synchronization information is others, no handling is neces-
sary.
Alarm Impact 1. IDE version file synchronization occurs between master and
slave OMP (ROMB board). Service will not be affected by synchro-
nization result.
2. In the case of synchronization failure, partial loss of version file
will occur to slave OMP
198005961 OMP Version

Check Information
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported

Cause of Alarm The version file in software version configuration does not exist in
RNC NE.
Suggestion where "Version file name" is given. According to the given
file name, locate on NMS software management interface the
corresponding version configuration in the version file database.
Reload the version file to RNC NE.
Alarm Impact 1. If the non-existent version file is not in use, service will not be
affected.
2. If the non-existent version file is the activated version, the
corresponding board will fail to fetch version during powering-on,
leading to service access failure. This rarely happens.
198005962 Patch version

operate fail
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Patch version file and CPU version file do not match.
2. Patch version file does not exist in RNC NE.
3. The patch version file related to the patch does not exist in RNC
NE.
Processing 1. If the patch version is not needed, delete the corresponding
Suggestion version configuration on NMS software management interface.
2. If the patch version is needed, locate on NMS software man-
agement interface the version configuration of patch version file
and related patch version file in the version file database. Reload
the version files to RNC NE.
Alarm Impact Patch version activation fails. New functions of the patch version
are unavailable. No impact on service.

198010560 No message
response in the link for a
long time
tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm Bottom layer link quality is poor, there is no message response for
the link for a long time.
Processing 1. Check if physical connection works normally.
Suggestion
2. Check NMS alarms/notifications to see whether there exists
physical transmission alarm(s) /notification(s) that occurred si-
multaneously with this alarm. If yes, refer to the correspond-
ing alarm/notification handling suggestion. Alarms/Notifications
related to physical transmission are listed below, with respect to
access mode.
1) Fiber Access Mode
198066048 SDH/SONET:Excessive Error Code
2)E1 Access Mode
198005647 High Error Rate at E1 Bottom Layer
198000576 Trunk Slide
Alarm Impact Related link will be interrupted and cannot bear service.
198011840 M3UA user

office status change


tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. User configuration of this office is changed.
2. Bottom-layer links are unavailable.
3. The signaling network management message from opposite
end is received.
Processing 1. Check whether link interruption alarm occurs to the link/asso-
Suggestion ciation. If yes, refer to the corresponding alarm handling sugges-
tion. Related alarms:
198066011 MTP3 link unavailable
2. On NMS configuration management interface, check if the M3UA
user is configured in the relevant office. If no, add the configura-
tion.
3. Locate the cause for office status change at opposite end.
Alarm Impact If M3UA user office status changes from accessible to inaccessible,
reception and sending of messages from/to the office fail. Access
of new services under the office fails, and abnormal release of the
ongoing service occurs. If M3UA user office status changes from
inaccessible to accessible, the system will return to normal state.
198013888 ASP status

changed
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Association status is changed.
2. ASP operation is performed at opposite end.
3. ASP operation is performed in dynamic data management at
local end.
Processing 1. Check whether association interruption alarm occurs. If yes,
Suggestion refer to the corresponding alarm handling suggestion. Related
alarm:


2. Activate the ASP in dynamic data management.
3. Check whether ASP operation is performed at the opposite end.
Alarm Impact If this notification and the alarm of "198066014 M3UA office in-
accessible" are declared at the same time, access failure of new
services under this office and abnormal release of ongoing services
will occur. If merely this notification is declared, service will not
be affected.
198013889 AS status
changed
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Association status is changed.
2. ASP operation is performed at opposite end.
3. ASP operation is performed in dynamic data management at
local end.
Processing 1. Check whether association interruption alarm occurs. If yes,
Suggestion refer to the corresponding alarm handling suggestion. Related
alarm:
2. Activate ASP under the AS in dynamic data management.
Alarm Impact If this notification and the alarm of "198066014 M3UA office in-
accessible" are declared at the same time, access failure of new
services under this office and abnormal release of ongoing services
will occur. If only this notification is declared, service will not be
affected.
198013890 Sigtran error

message received


tion
Alarm Level Minor
Disaster Alarm No
Frequently Yes
Reported
Cause of Alarm 1. AS configuration is wrong.
2. Protocol versions used at both sides are different.
Processing 1. Check AS configuration to see whether the configured traffic
Suggestion mode at both sides are consistent. If no, modify configuration to
keep consistency.
2. APP server AS ID configuration must meet the following require-
ments. If ASP is configured for local end, SGP should be configured
for Opposite end. Vice versa. If IPSP client is configured for lo-
cal end, IPSP server should be configured for opposite end. Vice
Versa.
3. Activate the ASP in dynamic data management.
4. On NMS configuration management interface (AS configura-
tion), check if routing context and routing context ID are config-
ured. Ensure that the routing contexts configured at both ends
are the same.
5. On NMS configuration management interface, check whether
the local ASP in service for AS is configured. If no, add the con-
figuration.
6. Check the protocol versions used at both sides. Ensure that the
protocol versions are the same.
Alarm Impact The corresponding AS fails to be activated, making M3UA office
inaccessible. Reception and sending of message from/to the office
fail. Access of new services under the office fails.
198013891 Sigtran
notification message
received
tion
Alarm Level Minor
Disaster Alarm No
Frequently Yes
Reported

Cause of Alarm 1. The broken association leads to insufficiency of the number of

ASP in service for AS.
2. Release of ASP in dynamic data management leads to insuffi-
ciency of the number of ASP in service for AS.
Processing 1. On NMS configuration management interface (AS configura-
Suggestion tion), query ASP-related associations. Check whether interruption
alarm occurs in the association(s). If yes, refer to the correspond-
ing alarm handling suggestion. Related alarm:
2. Reactivate ASP in dynamic data management.
Alarm Impact The number of ASP in service for AS is insufficient. If traffic is
heavy, congestion or packet loss might occur, leading to call loss
or increasing PS call access failures. Otherwise, service is not af-
fected.
198013892 Allocate memory

fail
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm Memory is insufficient, that result in dynamic memory allocation
failure when the processor is is powered on.
Processing 1. Enlarge memory capacity and then restart the board.
Suggestion
2. If Application Server/Application Server Process is not config-
ured on this board, then the alarm should be ignored.
Alarm Impact If Application Server/Application Server Process is not configured
on this board, system will not be affected. Or else process will be
unstable.
198014144 Association
establishment failed


tion
Alarm Level Major
Disaster Alarm No
Frequently No
Reported
Cause of Alarm 1. Association configuration at both sides is inconsistent.
2. No less than two associations are configured with same local
address and port, but with different protocol types.
3. Interface board IP address is wrong, or physical link is down.
Processing 1. On NMS configuration management interface, check associa-
Suggestion tion configuration at local end and opposite end. Checking items
include local IP address, local port No., remote IP address, remote
port No., and application property of SCTP association. If the as-
sociation at local end is configured as client, the association at
opposite end should be configured as server. Vice Versa.
2. At local end, check whether the associations configured with
different protocol types have the same local IP address and local
port No.. If yes, perform configuration modification to differentiate
the local IP address and local port No. of these associations.
3. Check protocol stack configuration at both ends to see if in-
terface board addresses are in the same network segment. If no,
modify configuration to put two addresses in the same network
segment.
4. Ping the opposite-end interface board address to see if the
network cable or other intermediate link is faulty. Replace the
cable if ping fails.
Alarm Impact If several association links are available to the destination office,
service will not be affected by establishment failure of one associ-
ation. In the case of heavy traffic, congestion of available associ-
ation(s) might occur, leading to upper layer call loss or increasing
PS call access failures. If merely one association link is available to
the destination office, the office might become inaccessible. Re-
ception and sending of messages from/to the relevant office fail.
Access of services under this office fails.
198014145 Association
restart
tion
Alarm Level Minor
Disaster Alarm No

Frequently No
Reported
Cause of Alarm The local end receives a link creation request but detects no link
break,and the association restarts.Probable causes for the alarm
include:
1.Relevant board at peer end resets.
2.The Association link is reestablished at peer end.
Processing No handling is necessarywait association to restart
Suggestion
Alarm Impact None.
198025664 Abnormal
Half-fixed Connection
Changes
tion
Alarm Level Major
Disaster Alarm No
Frequently Yes
Reported
Cause of Alarm 1.Abnormal jitter occurs to the line clock of the shelf where the
board is located.
2.The switching chip of the board is faulty.
Processing 1.Check alarms and notifications to see if the alarm(s)/notifica-
Suggestion tion(s) related to input clock exist(s).Related alarm(s) and notifi-
cation(s) are listed below.
198026116 CLKG PP2S Output Clock Lost
198026133 Clock Output Loss
2.Replace the faulty board.
Alarm Impact TMD channel is interrupted momentarily, which might have a mi-
nor impact on service.

198008005 Memory file

buffer overflow
tion
Alarm Level Warning
Disaster Alarm No
Frequently No
Reported
Cause of Alarm The transferred data records exceed the maximum capacity of the
table, and the capacity of the receiver memory file buffer is insuf-
ficient.
Processing Delete the excessive data records of the false table.
Suggestion
Alarm Impact If the board is powering on, the excessive data records (beyond
table capacity) are discarded, otherwise the synchronization will
be aborted.
198002625 Process is
deadlocked
tion
Alarm Level Major
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm Maybe some resource ,such as semaphore, is deadlocked.
Processing Note down the alarm information and contact ZTE Corporation.
Suggestion
Alarm Impact The process will never be scheduled, or timely resource release
fails, which results in resource exhaustion.

198002880 CPU occurs

dead-loop
tion
Alarm Level Major
Disaster Alarm Yes
Frequently No
Reported
Cause of Alarm There exist dead loops in the processes or the system tasks.
Processing The board will restart automatically when this alarm occurs. The
Suggestion alarm will automatically disappear after restart.
Alarm Impact The process or task of low priority level fails to be scheduled.
198005718 Two master

clock ports is directly
connected
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm The port is configured as a master clock port in synchronous Eth-
ernet, two master clock ports is directly connected.
Processing If users do not want the other side to recover clock from this SyncE
Suggestion port, it is normal.
Otherwise, it maybe has a mistake on network connecting. If it
is normal, there is no need to handle; if it is network connecting
mistake, there is need to reconfigure the clock port or reconnect
the port.
Alarm Impact If it is normal, then there is no impact, if it is network connecting
mistake, then the port can not synchronize to the connected mas-
ter clock port.

198005189 Notification of
Active/Standby Changeover
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm It is hardware system fault. The CS domain of the UIM switches
over due to artificial operation.
Processing 1. Analyze the switchover reason according to the additional in-
Suggestion formation about the alarm .If it is not because of the system fault
but due to control of MML command at the background or caused
by non-active/standby changeover, or the standby board does not
exist physically, nothing would be done for this alarm.
2. If it is because of the system fault, eliminate those alarms
firstly.
Alarm Impact The board whose changeover fails will reset automatically.
198026176 Clock reference

changed
tion
Alarm Level Warning
Disaster Alarm No
Frequently No
Reported
Cause of Alarm The currently locked clock reference has changed.
Processing No need to handle.
Suggestion
Alarm Impact System could not get the needed clock, which will cause processing
abnormity related to the clock.

198020805 ARP detect

failed
tion
Alarm Level Minor
Disaster Alarm No
Frequently Yes
Reported
Cause of Alarm When the switch of the ARP detecting enabled, CE can send ARP
request packet with the ARP's IP periodically, if CE can not receive
the ARP respond packet during the set time, CE will report this
alarm information.
Processing 1. Please check the device's IP address configuration of the peer
Suggestion end.
2. Please check physical link.
3. Please check the exchanger's VLAN configuration.
Alarm Impact The communication will be interrupted possibly.
198020806 ARP detect that

the static ARP is not match
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm When the switch of the ARP detecting enabled, CE can send static
ARP request packet with the static ARP's IP periodically, if CE re-
ceives the ARP respond packet whose MAC or dot1q encapsulation
is not the same as static ARP's during the set time, CE will report
this alarm information.
Processing 1. Please check remote device's MAC address.
Suggestion
2. Please check the switch VLAN configuration.
Alarm Impact The communication will be interrupted possibly.

198015168 AAL2 Path

blocked by resetting process
tion
Alarm Level Minor
Disaster Alarm No
Frequently No
Reported
Cause of Alarm The adjacent node doesn't has the same path.
Processing You can unblock the Path by adding the same path on the adjacent
Suggestion node.


Figures


Tables

Dokumen - Tips Zte RNC Alarm and Notification Handling Reference

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Dokumen - Tips Zte RNC Alarm and Notification Handling Reference

Uploaded by

Copyright:

Available Formats

ZXWR RNC

Radio Network Controller

Copyright © 2010 ZTE CORPORATION.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision No. Revision Date Revision Reason

About This Manual............................................. I

Confidential and Proprietary Information of ZTE CORPORATION I

198019465 CSIX RX and TX packets is abnormal ...........12

II Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION III

198083040 TCP connect on IuBC interface is

IV Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION V

198005123 DB Configuration Doesn't Fit for Device .........92

VI Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION VII

198018241 TCP Connection Aborted .............................. 133

VIII Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION IX

This page is intentionally blank.

X Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1, Overview Introduces the concept of fault

Chapter 2, Alarm Introduces RNC alarms with respect to

Chapter 3, Notification Introduces RNC notifications with respect

Confidential and Proprietary Information of ZTE CORPORATION I

Changes or modifications not expressly approved by the party re-

II Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION 1

2 Confidential and Proprietary Information of ZTE CORPORATION

The degree of impact as described in the definition of alarm sever-

In addition, the severity of few alarms is undefined. It is up to

Confidential and Proprietary Information of ZTE CORPORATION 3

4 Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION 5

This page is intentionally blank.

6 Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION 7

198083022 Cell is out of service

8 Confidential and Proprietary Information of ZTE CORPORATION

the following alarms occurs. If yes, follow the corresponding sug-

Confidential and Proprietary Information of ZTE CORPORATION 9

On NMS configuration management interface, select the cell to be

198083023 Node B out-of-service

10 Confidential and Proprietary Information of ZTE CORPORATION

198083027 RSVB board offline alarm

198019456 HSSLS are all out of

Confidential and Proprietary Information of ZTE CORPORATION 11

2) If consistent, PSN board hardware might be faulty. In this case,

198019465 CSIX RX and TX packets

198005633 Hard Disk Broken

12 Confidential and Proprietary Information of ZTE CORPORATION

Disaster Alarm Yes

198005635 The board is not plugged

Confidential and Proprietary Information of ZTE CORPORATION 13

198005639 High Error Rate of Optical

198005640 FPGA Exception

14 Confidential and Proprietary Information of ZTE CORPORATION

Alarm Purpose External Alarm

198005644 The Channel in a

198005645 Subcard Abnormal

Confidential and Proprietary Information of ZTE CORPORATION 15

Alarm Classifica- Alarm

198005646 Phase-locked Loop