ZXWR RNC
Radio Network Controller
Alarm and Notiication 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 CORPORATION is prohibited. Additionally, the contents of this document are protected by contractual conidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATION
or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions are disclaimed, including without limitation any implied warranty of merchantability, itness for a particular purpose, title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on the
information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subject
matter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee,
the user of this document shall not acquire any license to the subject matter herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No.
R1.0
R2.0
Revision Date
20100609
20100915
Revision Reason
First Edition (V3.09.30.03)
Second Edition (V3.09.30.06)
Add new alarm and Notiication: 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 Notiication: 198083031
Update alarm and Notiication:
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
Notiication ................................................................ 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
Notiication .................................................................... 4
Notiication Property ................................................... 4
Notiication Code................................................ 4
Description........................................................ 4
Importance ....................................................... 4
Notiication 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 ofline alarm ...........................11
198019456 HSSLS are all out of synchronization ...........11
Conidential and Proprietary Information of ZTE CORPORATION
I
ZXWR RNC Alarm and Notiication Handling Reference
198019465 CSIX RX and TX packets is abnormal ...........12
198005633 Hard Disk Broken......................................12
198005635 The board is not plugged irmly ..................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 conigured
in the database. ................................................27
198005390 CPU sub card is missing from slot but is
conigured 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
Conidential and Proprietary Information of ZTE CORPORATION
198026128 Clock reference source lost (Level 2 alarm)
.......................................................................32
198026129 Clock reference source lost (Level 1 alarm)
.......................................................................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 insuficient...............................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
Conidential and Proprietary Information of ZTE CORPORATION
III
ZXWR RNC Alarm and Notiication Handling Reference
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 conlict 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
Conidential 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 ofice ..........77
198066011 MTP3 link unavailable ................................77
198066014 RNC unable to connect to M3UA ofice .........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 Coniguration
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 Ofice ID is not set correctly with control
shelf. ..............................................................89
198066057 Database conig is different from ile
named bootcfg ini. .............................................90
198005649 Port working mode doesn't match with its
setting. ............................................................90
Conidential and Proprietary Information of ZTE CORPORATION
V
ZXWR RNC Alarm and Notiication Handling Reference
198005123 DB Coniguration 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 coniguration 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 low
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 trafic over load alarm..................... 107
198083043 IU CS trafic over load alarm .................... 107
198083044 IU trafic over load alarm ......................... 108
Notiication ................................................... 109
198083017 RUB board has reached maximum number of
routes ................................................................ 111
198070002 Iu interface global reset notiication............... 111
198070003 Iu interface resource reset notiication ........... 112
VI
Conidential and Proprietary Information of ZTE CORPORATION
198070004 RNC initiate Iu interface global reset failure
notiication ......................................................... 113
198070005 RNC initiate Iu interface resource reset failure
notiication ......................................................... 113
198070008 RNC and Node B are conigured with different
CCPID ................................................................ 114
198070009 Broadcast failure......................................... 114
198083025 Common Channel is abnormal ...................... 116
198070010 FTP failure and ile lost ................................ 117
198070011 RNC alarm storage disc is full ....................... 118
198083028 Performance ile server unavailable ............... 118
198083029 Unable to save Performance File ................... 119
198083019 MicroCode subsystem failed to get the table
of coniguration ................................................... 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 notiication .......... 125
198083035 Transport Path Occupied BandWidth
Overload ............................................................ 126
198083037 All Local Cell ID conigured at RNC side are
differ from which on Node B side ........................... 126
198020291 Protocol stack process failed to initialize
during power on .................................................. 127
198020802 Conlicting IP address in subnet. .................. 127
198020803 Conlicting 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
coniguration data from DBS ................................. 132
198018240 TCP Receives RST Packet ............................. 133
Conidential and Proprietary Information of ZTE CORPORATION
VII
ZXWR RNC Alarm and Notiication Handling Reference
198018241 TCP Connection Aborted .............................. 133
198018242 MD5 Veriication Failure ............................... 134
198018243 Wrong MD5 Message Abstract....................... 134
198023106 Board Self-Check Failure .............................. 135
198023107 The board initialization failure....................... 135
198023617 Coniguration ile 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 Notiication 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
Conidential and Proprietary Information of ZTE CORPORATION
198010560 No message response in the link for a long
time .................................................................. 152
198011840 M3UA user ofice status change .................... 152
198013888 ASP status changed .................................... 153
198013889 AS status changed ...................................... 154
198013890 Sigtran error message received .................... 154
198013891 Sigtran notiication message received ............ 155
198013892 Allocate memory fail ................................... 156
198014144 Association establishment failed.................... 156
198014145 Association restart ...................................... 157
198025664 Abnormal Half-ixed Connection
Changes............................................................. 158
198008005 Memory ile buffer overlow .......................... 159
198002625 Process is deadlocked .................................. 159
198002880 CPU occurs dead-loop.................................. 160
198005718 Two master clock ports is directly
connected........................................................... 160
198005189 Notiication 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
Conidential and Proprietary Information of ZTE CORPORATION
IX
ZXWR RNC Alarm and Notiication Handling Reference
This page is intentionally blank.
X
Conidential and Proprietary Information of ZTE CORPORATION
About This Manual
Purpose
At irst, 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 deined 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 uniied hardware platform, utilizes distributed design, supports ATM/IP dual protocol stack and
can smoothly evolve to IP UTRAN. It aims at saving operator’s investment in 3G network construction by offering a large capacity
and linear expandable system once and for all.
Intended
Audience
Prerequisite Skill
and Knowledge
This manual introduces the alarms that might occur during the
installation, operation and maintenance of the ZXWR RNC product.
This guide is intended for engineers and technicians who perform
operational activities on ZXWR RNC.
To use this guide effectively, users should have a general understanding of telecommunications technology. Familiarity with the
following is helpful:
�
ZXWR RNC system and its various components
�
Local operating procedures of the ZXWR RNC system
�
What is in This
Manual
User interfaces on the ZXWR RNC system
Chapter
Summary
Chapter 2, Alarm
Introduces RNC alarms with respect to
alarm property, probable cause, system
impact, and handling suggestion.
Chapter 1, Overview
Chapter 3, Notiication
FCC Compliance
Statement
Introduces the concept of fault
management, as well as the deinition,
type, level classiication of alarm and
notiication.
Introduces RNC notiications with respect
to notiication property, probable cause,
system impact, and handling suggestion.
This device complies with part 15 of the FCC Rules. Operation is
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.
Conidential and Proprietary Information of ZTE CORPORATION
I
ZXWR RNC Alarm and Notiication Handling Reference
Changes or modiications not expressly approved by the party responsible for compliance could void the user's authority to operate
the equipment.
II
Conidential and Proprietary Information of ZTE CORPORATION
Chapter
1
Overview
Table of Contents
Overview of Fault Management.............................................
Fault View .........................................................................
Alarm ...............................................................................
Notiication ........................................................................
1
1
2
4
Overview of Fault
Management
Fault management is responsible for collecting information of failures and events that occur during system operation or service processing.
The information, in the form of alarm or notiication, is stored in
database or displayed on realtime basis via a user-oriented fault
monitoring platform. Means such as visual-interface monitor or
history information query can be used to view current or historical system operation and service processing status. Fault management enables maintenance personnel to troubleshoot and take
preventive measures to remove potential fault and restore system
and services as early as possible.
Fault View
Fault is displayed in the form of alarm or notiication.
Alarm
The fault that persists during system operation and affects system
reliability and normal services is referred to as an alarm. Alarm
usually lasts until fault removal.
Due to its possible impact on normal system operation, alarm requires timely troubleshooting in which alarm cause is identiied,
and the fault is located and handled.
Conidential and Proprietary Information of ZTE CORPORATION
1
ZXWR RNC Alarm and Notiication Handling Reference
Notification
Notiication refers to the non-repeated/instantaneous fault or
event that occurs during system operation. Examples include
board reset, signaling overload, etc.
Notiication is mostly caused by sudden environment change
or other accidental factors. No special handling is required for
the notiication, which can be automatically removed by the
system. Only the notiication that occurs persistently requires
troubleshooting.
Alarm
Alarm Property
Alarm Code
Alarm code is the identiier which differentiates alarms.
Alarm code is deined by a 32-bit ield indicating the speciic code
value.
Description
Alarm description relects 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 order of severity as Critical, Major, Minor, and Warning.
�
�
�
�
2
Critical alarm causes system breakdown and service interruption. It requires immediate troubleshooting.
Major alarm signiicantly affects system operation or weakens
network service capability. It requires troubleshooting as soon
as possible.
Minor alarm affects system operation and network service
capability in a nonsigniicant way. It requires timely troubleshooting so as to avoid severity escalation.
Warning poses a potential hazard to system operation and network service capability. It requires troubleshooting at an appropriate time so as to avoid severity escalation.
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 1 Overview
The degree of impact as described in the deinition of alarm severity refers to the impact of a single index, such as reliability and
security. Once the impact on any of the index reaches the speciied threshold, the severity level of the alarm can be roughly determined. If an alarm has an impact on multiple indices, alarm
severity should be escalated accordingly.
Note:
Alarm severity can be modiied 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 modiication.
In addition, the severity of few alarms is undeined. It is up to
users to deine the severity of such alarms.
Alarm Type
Alarm is classiied into six types according to alarm trigger condition and its system impact.
�
Equipment alarm: related with device hardware.
�
Processing alarm: related with software or process fault (ITU-T
Recommendation X.733).
�
�
�
�
Communication alarm: related with information transmission
(ITU-T Recommendation X.733).
Environment alarm: related with the environment where the
equipment is located (ITU-T Recommendation X.733).
QoS alarm: related with degradation of service quality (ITU-T
Recommendation X.733).
OMS alarm: related with the network management system.
Probable Cause
Probable alarm causes are enumerated to help users troubleshoot,
ind preventive measures, and restore the system to normal state
in a timely manner.
System Impact
System impact refers to the impact that the alarm incurs on system or services.
Conidential and Proprietary Information of ZTE CORPORATION
3
ZXWR RNC Alarm and Notiication Handling Reference
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 Suggestion Section of this manual. If the fault is removed (alarm
restored) at any handling step, terminate the handling process.
If the fault is not removed, go ahead to the next handling step.
If the fault cannot be removed, contact the local ZTE ofice as
soon as possible.
Notification
Notification Property
Notification Code
Notiication code is the identiier to differentiate notiications.
Notiication code is deined by a 32-bit ield indicating the speciic
code value.
Description
Notiication description relects such content as fault cause and
fault phenomenon in a simple and straightforward way.
Importance
There are two levels of notiication importance: Important and
Ordinary.
Notification Type
No notiication type exists.
4
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 1 Overview
Probable Cause
Probable notiication causes are enumerated to help users troubleshoot the system in a timely manner and take preventive measures to ensure stable system operation.
System Impact
System impact refers to the impact that the notiication incurs on
system or services.
Handling Suggestion
Troubleshooting measures and suggestions are provided.
Pay attention to the following tips when handling notiications.
�
�
After recording the fault phenomenon, O&M personnel may
handle the fault step by step as described in the Handling Suggestion Section of this manual. If the fault is removed (alarm
restored) at any handling step, terminate the handling process.
If the fault is not removed, go ahead to the next handling step.
If the fault cannot be removed, contact the local ZTE ofice as
soon as possible.
Conidential and Proprietary Information of ZTE CORPORATION
5
ZXWR RNC Alarm and Notiication Handling Reference
This page is intentionally blank.
6
Conidential and Proprietary Information of ZTE CORPORATION
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
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Equipment Alarm
External Alarm
Alarm
Major
No
No
1. Log server is unavailable.
2. Break in communication between RNC and Log server.
1. Check the log server by performing the following steps to see
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 communication.
Alarm Impact
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.
Log/performance iles cannot be reported to the log server.
Conidential and Proprietary Information of ZTE CORPORATION
7
ZXWR RNC Alarm and Notiication Handling Reference
198083022 Cell is out of service
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Equipment Alarm
External Alarm
Alarm
Critical
Yes
Yes
1. RRU faulty.
2. cell is blocked by user.
3. Cell ID is incorrect or deleted.
4. Node B or BTS restarted or down.
Processing
Suggestion
5. Node B Cell frequency is not consistent with RNC.
View alarm details on the NMS Alarm Management interface to
check the Alarm reason, which can help you easily ind the corresponding 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 Radio Resource Management > Baseband Resource Pool on the NMS
Coniguration 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 conigurations 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 indicates 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 Coniguration 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 Radio Resource Management > Baseband Resource Pool on the NMS
Coniguration Management interface, and then select the cell to be
viewed. Check "Local Cell Status Parameters" to see its management 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 Coniguration 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
8
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
the following alarms occurs. If yes, follow the corresponding suggestions 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.
198084117 Application software monitoring alarm
198084123 Board communication link is interrupted
198084107 Board parameter synchronization abnormality
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.
198084117 Application software monitoring alarm
198084123 Board communication link is interrupted
198084107 Board parameter synchronization abnormality
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
Coniguration 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 conigured at RNC side is
incorrect.
On NMS coniguration management interface, select the RNC Wireless Resource Management > Service Cell, check the cell parameters as follows:
1) Cell Capability and Cell Reselect Parameters
2) Senior Parameters: Load Control, Balance Parameters, Accept
Control, HSPA Conigure, Mbms Conigure.
6. Local cell is blocked at Node B side.
Conidential and Proprietary Information of ZTE CORPORATION
9
ZXWR RNC Alarm and Notiication Handling Reference
On NMS coniguration 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.
Alarm Impact
7. For other alarm causes, the system will automatically recreate
cells. In this case, no manual operation is required.
The cell is unavailable and inaccessible, providing no service.
198083023 Node B out-of-service
alarm
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Equipment Alarm
External Alarm
Alarm
Critical
Yes
Yes
1. Transmission is faulty.
2. Node B is down.
The handling suggestions are classiied by transmission mode.
1. IP mode
Check the Alarm Management interface according to the association ID to see if there is any of the following association-related
alarms. If yes, follow the corresponding suggestions to handle it.
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 corresponding suggestions to handle it.
Alarm Impact
10
198018944 PVC Fault
The Node B is unavailable and inaccessible, providing no service.
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
198083027 RSVB board offline alarm
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Equipment Alarm
External Alarm
Alarm
Critical
No
No
1. RSVB board is not plugged into shelf.
2. RSVB board is faulty.
3. RSVB board is not irmly inserted into slot.
1. Check if the RSVB is extracted.
If yes, insert the RSVB into the rear slot again.
If not, extract and insert the RSVB.
Alarm Impact
2. Replace the RSVB.
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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Equipment Alarm
External Alarm
Alarm
Critical
No
No
1. The PSN board type conigured does not accord with the PSN
board type actually in use.
2. PSN board hardware (VSC882 chip) is faulty.
Processing
Suggestion
3. Line card hardware (VSC872/VSC874 chip) is faulty.
1. Check whether PSN board reboots repeatedly. If yes, Check
whether the PSN board type conigured is consistent with the PSN
board type actually in use.
1) If inconsistent (for example, the conigured board type is PSN4V
and the board type actually in use is PSN8V), modify board type
coniguration or replace the board actually in use to keep consistency between board coniguration and the board in use.
Conidential and Proprietary Information of ZTE CORPORATION
11
ZXWR RNC Alarm and Notiication Handling Reference
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.
Alarm Impact
2) If merely the line card where this alarm occurs reboots repeatedly, replace the board where the alarm is generated.
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 conigured in master/slave or load sharing
mode, all services on the line card will be down. If the service is
conigured in master/slave or load sharing mode, all services on
the line card will soon be restored after being down temporarily.
198019465 CSIX RX and TX packets
is abnormal
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Equipment Alarm
External Alarm
Alarm
Warning
No
No
1. Signal is unstable when rack or board is powering on.
2. Switch chip is abnormal.
1. Reset the board.
2. Replace the board.
The transceiver of the media plane is exceptional.
198005633 Hard Disk Broken
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
12
Equipment Alarm
External Alarm
Alarm
Major
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
Disaster Alarm
Yes
Frequently
Reported
No
Processing
Suggestion
Replace the hard disk on the board or replace the board.
Cause of Alarm
Alarm Impact
There is failure in ribbon cable connection or the hard disk. This
is usually a hardware failure.
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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Equipment Alarm
External Alarm
Alarm
Major
No
No
1. The ENUM switch on the board is ON, or is not irmly connected.
2. Or the EXCH key on the standby board is pressed twice within
3 seconds.
1. Check the ENUM switch and turn it on. If it is not turned on.
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.
Cause failure in active/standby board switching, or cause failure
in APS switching. Do not switch this board into active board.
Conidential and Proprietary Information of ZTE CORPORATION
13
ZXWR RNC Alarm and Notiication Handling Reference
198005639 High Error Rate of Optical
Interface
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Equipment Alarm
External Alarm
Alarm
Major
No
No
The iber is not completed connected to the port, or is damaged,
or is not compatible with the optical transceiver module in T-network switch. There is no light signal input into the optics module.
This alarm is dedicated to the TDM optical port only. The possible
causes of this alarm include:
1. TDM receiver iber optics failure, iber optics module failure.
This type of failures include: damaged iber on the receiver, unconnected iber, contaminated iber or damaged optics module on
the receiver.
2. Fiber optics failure at the transmitting module on the corresponding TDM. This type of failures include: damaged iber on the
transmitter, unconnected iber, and contaminated iber.
3. Compatibility between iber optics and optics module. The
iber transmission rate of TDM signal is incompatible with the wave
length of the optics module.
Processing
Suggestion
4. Loss of signal (LOS) alarm operation is performed on the corresponding SDH device. This includes the manual diagnosis test
alarm operation.
1. Perform loopback test to determine source of this alarm is on
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 iber optics.
Alarm Impact
4. Replace the board.
There might be error in the data transmitted by the optical port
which affects the quality of all the services performed on this optical port.
198005640 FPGA Exception
Alarm Type
14
Equipment Alarm
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
Alarm Purpose
Alarm Classiication
Alarm Level
External Alarm
Alarm
Major
Disaster Alarm
No
Cause of Alarm
FPGA runs abnormally, for example, FPGA is lost, or the board
clock is lost.
Frequently
Reported
No
Processing
Suggestion
1. Restart the board. In this case, the board downloads FPGA
again.
Alarm Impact
FPGA veriication 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.
2. Replace the board.
198005644 The Channel in a
Subcard Is Down
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Equipment Alarm
External Alarm
Alarm
Major
No
No
1. The sub-card is not inserted in position.
2. The sub-card has hardware faults.
Processing
Suggestion
1. Unplug and plug the sub-card again. Wait for the board to be
powered on.
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.
2. Replace the sub-card.
198005645 Subcard Abnormal
Alarm Type
Alarm Purpose
Equipment Alarm
External Alarm
Conidential and Proprietary Information of ZTE CORPORATION
15
ZXWR RNC Alarm and Notiication Handling Reference
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Alarm
Minor
No
No
1. The GCS, EC or HPS subcard of UIMC/GUIM/CHUB is not inserted in position.
2. The subcard is faulty.
1. Check the sub-card connection. If the connection is loose,
tightly insert the sub-card and wait for the board to be powered
on.
2. Replace the sub-card.
The GCS sub-card of the UIMC/GUIM/CHUB can not function normally. Packets will be lost. In some cases, control plane links will
be disconnected. For active/standby coniguration, 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 active/standby changeover can not be performed. In this case, services will be interrupted because the faulty board can not be back
to normal.
198005646 Phase-locked Loop
Unlocked
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Equipment Alarm
External Alarm
Alarm
Critical
No
No
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 coniguration 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.
16
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
Processing
Suggestion
4. The hardware of the PLL on the board is faulty.
1. Check whether there is the following clock alarm on the NMS
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 interface. If yes, handle it according to the corresponding suggestions.
198001792 SDH/SONET fault
198066047 Abnormal status in SDH/SONET
198005639 High Error Rate of Optical Interface
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
6. Replace the board.
The service clock and the system clock will be asynchronous because 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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Equipment Alarm
External Alarm
Alarm
Major
Yes
No
1. The E1/T1 link is faulty.
2. The device in the uplink direction of the trunk link is faulty.
3. The trunk cable or connector is in poor contact.
1. Conduct a meter measurement or loopback test to ind out
whether the alarm is rooted in the local end or peer end. Meter
measurement: Connect a trunk test meter to check if the signal
received by the local end trunk is normal. If yes, the fault is rooted
in the local end. If the test shows the problem persists, the fault
is rooted in the peer end. In this case, inform the peer end to
troubleshoot. Loopback test: Perform self-loop at the trunk where
alarm occurs at local end. If the problem persists, it indicates that
the fault is rooted in the local end. If the alarm is eliminated, it
Conidential and Proprietary Information of ZTE CORPORATION
17
ZXWR RNC Alarm and Notiication Handling Reference
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
3. Replace the board.
The trunk fails to receive trunk signals. If the belonged port has
only this link, all services on the port are interrupted. Otherwise,
only the port bandwidth is affected. The quantity of upper layer access services associated with the port is decreased. The accessed
bandwidth is reduced. The service, however, is not interrupted.
198005656 Loss of Clock When Input
to Sub-card
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Equipment Alarm
External Alarm
Alarm
Major
No
No
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.
1. Check the sub-card connection status. If the sub-card is loose,
tightly connect it and power it on again.
2. Replace the sub-card
3. Replace the board.
The unavailable sub-card clock affects the normal operation of the
board. This may cause clock jittering, and the service that implements media stream exchange through this board becomes unstable. In the most serious case, the system clock is lost and the
service carried by the board is interrupted.
198005663 M28529 chip failure
on board IMAB or DTA affecting
services.
Alarm Type
Alarm Purpose
Alarm Classiication
18
Equipment Alarm
External Alarm
Alarm
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Major
No
No
Devices or sub-cards on the board operate abnormally.
Replace the board.
This alarm only occurs to the IMAB. When it occurs, the IMAB can
not operate normally and the trunk borne on the board will be broken. As a result, users can not access the board and the existing
services will be interrupted.
198066044 Fault on Board (GPS)
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Equipment Alarm
External Alarm
Alarm
Critical
No
No
According to alarm details, alarm status falls into three types: Type
A Fault on Board (GPS) Phase-lock Equipment Phase-lock Equipment of This Board (GPS) Is in Power-on Status The causes for the
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.
Processing
Suggestion
2.Phase-lock Equipment of This Board (GPS) Is in Power-on Status The alarm cause is that the GPS module of ICM board is in
power-on status, and power-on has not been completed.
On NMS fault management interface, view alarm Details where
Error type information is given. Locate the corresponding alarm
handling suggestion according to the error type. The alarm handling suggestions that correspond to the error types are described
below.
1.Type A Fault on Board (GPS) Phase-lock Equipment
1) On NMS test management interface, perform diagnostic test on
ICM board. Check the working status of the GPS module. If Class
A fault persists in the GPS module, replace the board.
2) Check if output clock loss occurs. If yes, replace the board.
2.Phase-lock Equipment of This Board (GPS) Is in Power-on Status If the alarm persists, hardware fault might exist. Replace the
board.
Conidential and Proprietary Information of ZTE CORPORATION
19
ZXWR RNC Alarm and Notiication Handling Reference
Alarm Impact
Be usually determined as hardware fault, which affects system
clock. It might lead to the system clock loss and system synchronization failure. When system clock loss/offset occurs, its subsequent impact on service is described below.
1.For TDM transmission, all links based on the TDM transmission
medium (including the transmission link currently in service for UE
and cell transmission link) are affected. Packet loss might occur on
these links, leading to degradation of service quality. In the case
of serious packet loss, service interruption and handover failure
will occur. Even worse, the cell might be out of service.
2.For non-TDM transmission (for example, IP transmission), Iub
interface service is affected, while Iur interface and Iu interface
services are not affected. The clock that Node B derives from RNC
via IEEE1588 is inaccurate. When RNC clock frequency offset is
no more than 0.05 ppm, Node B synchronization will not fail, but
success rate of inter-RNC inter-Node B soft handover might fall.
When RNC clock frequency offset exceeds 0.5 ppm, Node B will
fail to lock the clock. In this case, Node B will oscillate freely and
success rate of inter-Node B soft handover might fall.
198001284 The phase of 8K, 16K
clock, input to backplane board, is
not matched
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Equipment Alarm
External Alarm
Alarm
Minor
Yes
No
1. clock cable is not properly connected.
2. clock board is faulty.
1. Check the clock input cable and ensure that the cable is good
and well connected.
2. Clock board changeover.
3. UIM/GUIM board changeover.
Alarm Impact
20
4. Replace the board.
The system fails to achieve synchronization so that the board can
not work normally. As a result, UE can not be accessed and services borne on the board are interrupted.
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
198001286 Input clock of board lost
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Equipment Alarm
External Alarm
Alarm
Minor
No
No
1. The board is not properly inserted to a slot.
2. A clock cable is not connected.
3. The clock cable is broken.
Processing
Suggestion
4. The board is faulty.
1. Check whether the clock input cable is properly connected.
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 irmly.
Alarm Impact
3. Replace the board.
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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Equipment Alarm
External Alarm
Alarm
Critical
Yes
No
1. The receiving optical iber/module of local equipment is faulty.
Receiving optical iber is faulty or disconnected.
Optical connector is polluted.
Receiving optical module is faulty.
2. The transmitting optical iber of opposite equipment is faulty.
Transmitting optical iber is faulty or disconnected.
Optical connector is polluted.
3. The receiving optical power at local end is excessively low.
Conidential and Proprietary Information of ZTE CORPORATION
21
ZXWR RNC Alarm and Notiication Handling Reference
Optical power attenuation on the receiving iber transmission line
at local end is too much.
Transmitting optical power at opposite end is too low.
4. Operation of LOS insertion is performed at opposite end.
Manual operation of LOS insertion is performed in diagnostic test,
and optical module is shutdown by force.
5. Optical iber and optical module is incompatible.
Processing
Suggestion
The iber transmission rate and the optical module wavelength are
incompatible.
1. Carry out loop test to determine whether the alarm is caused
by local end or opposite end. Perform iber self-loop at local equipment. If the alarm persists, fault might lie in local equipment. If
the alarm disappears, inform the opposite end to troubleshoot.
2. Replace the optical module.
3. Replace iber.
Alarm Impact
4. Replace board.
The optical interface fails to work normally. If the optical interface is conigured with APS protection, service will be switched to
protection optical interface. Otherwise, all services on the optical
interface will be down.
198015874 Physical channel for data
transmission blocked
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Equipment Alarm
External Alarm
Alarm
Major
No
No
1. The trafic low to the board is excessive.
2. The PSN board in the same shelf is abnormal.
3. The board has hardware faults.
1. On NMS fault management interface, check if the PSN in the
same shelf has generated related alarms. If yes, follow the suggestions on handling the related alarms. The related alarm is as
follows:
198019456 All high-speed links between line card and package
switching board are out of synchronism
2. Unplug and plug the board.
3. Replace the board.
22
Conidential and Proprietary Information of ZTE CORPORATION
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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Equipment Alarm
External Alarm
Alarm
Minor
No
No
1. L1 table or L2 table error.
2. Destination IP of packets or hardware is error.
Switch the master port to the partner board.
Packets would be dropped which would cause poor voice quality
and other problems.
198015876 GLI exception packets
statistic over threshold
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Equipment Alarm
External Alarm
Alarm
Minor
No
No
1. Connection between iber and optic modules is not perfect.
2. Something wrong with iber optic module.
3. Board hardware error.
1. Check the connection between iber and optic modules.
2. Reboot the board.
Packets would be dropped which would cause poor voice quality
and other problems.
Conidential and Proprietary Information of ZTE CORPORATION
23
ZXWR RNC Alarm and Notiication Handling Reference
198002560 The usage of CPU is over
the threshold
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Equipment Alarm
External Alarm
Alarm
Major
Yes
Yes
1. Excessive data trafic at higher layer.
2. System is performing data synchronization or saving.
3. CPU alarm threshold setting is under conigured.
1. Open the rack map on the Coniguration Management window,
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 ile operations in the network manager log iles. Those operations might increase the CPU utilization rate radically, and it
might take 2 minutes.
Alarm Impact
3. Check for the record of new board added or version upgrade
operation in the network manager log iles. Version upgrading
operation might increase CPU utilization rate radically, and it might
take 2 minutes.
CPU occupancy indicates the current status of system operation.
CPU overloaded, or over high occupancy, is usually caused by service or operation that consume much time. It has the following
impact on the system. Services with low priority level have little
or no access to the processing of CPU, which reduces processing
speed of the services or even halts the processing. System board
could reset under excessively overloading conditions, causing interruption to the service it performs.
198002561 CPU temperature over
threshold
Alarm Type
Alarm Purpose
Alarm Classiication
24
Equipment Alarm
External Alarm
Alarm
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Major
Yes
No
1. Environmental temperature around rack is too high
2. Board hardware fault
3. The alarm threshold value is under conigured.
1. Open the rack map on the Coniguration Management window,
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 threshold value is too low. It will take 30 seconds for the new setting
to take effect. Recommended Threshold: Upper limit for temperature alarm: 90 degree. Reboot Temperature: 95 degree.
2. Check the thermometer in machine room for accurate temperature, 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 operation.
Alarm Impact
6. Replace the relevant boards.
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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Equipment Alarm
External Alarm
Alarm
Major
No
No
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 irst level switching board, UIM board
at the shelf, or local board.
Conidential and Proprietary Information of ZTE CORPORATION
25
ZXWR RNC Alarm and Notiication Handling Reference
Processing
Suggestion
5. Service over the rated capability of the board.
1. Check the Alarm Management window for the CUP overloaded
on the irst 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 Inter-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
3. Replace the board.
4. Change the slot of the board.
Alarm Impact
5. Replace the UIM in the same shelf.
When this port is not available for internal media stream transmission, 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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Equipment Alarm
External Alarm
Alarm
Major
Yes
No
1. Board not properly positioned.
2. Hardware failure.
1. Check for the proper placing of the board, and insert the board
irmly if it is nor properly placed.
2. Plug/unplug the board.
3. Replace the board.
4. Replace the slot
Alarm Impact
26
5. Replace the UIM in the same shelf.
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.
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
198005381 Input clock is abnormal
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Equipment Alarm
External Alarm
Alarm
Critical
Yes
No
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.
1. Reconnect the cable between the board and the clock reference.
2. Replace the cable between the board and the clock reference.
3. Check the signal output from the reference clock source.
Alarm Impact
4. Replace the board.
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.
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Equipment Alarm
External Alarm
Alarm
Warning
Disaster Alarm
No
Cause of Alarm
1. Coniguration is incorrect.
Frequently
Reported
Processing
Suggestion
Alarm Impact
No
2. Board is misplaced.
Is the subcard needed?
If no, remove the subcard.
If yes, change the type of board so that it can support the subcard.
Since the board where the unconigured subcard is located resets
repeatedly, power resource of the equipment is wasted. However,
services won't be affected.
Conidential and Proprietary Information of ZTE CORPORATION
27
ZXWR RNC Alarm and Notiication Handling Reference
198005390 CPU sub card is missing
from slot but is configured in database
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Equipment Alarm
External Alarm
Alarm
Major
No
No
1. The coniguration is wrong.
2. A wrong board is inserted.
Is the sub-card required?
If no, modify the type of board so that the new type doesn't support such sub-card.
If yes, insert the sub-card irmly.
The sub-card functions are unavailable, accordingly this board
does not support relevant services. The inluence on the system
is various according to different type of sub-card.
If the sub-card is an interface board, the transmission link via this
board is not connectable, then services will be accessed through
other sub-card. If the sub-card is a signaling process board, the
cell/Node B conigured for this board is not available for services. If
the sub-card is a user's plane board, user plane process capability
will decline, then services will be accessed through other sub-card.
198005395 External Port of Board Is
Down
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Equipment Alarm
External Alarm
Alarm
Major
No
No
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.
28
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
Processing
Suggestion
Alarm Impact
1. Reconnect or replace the cable.
2. Replace the board.
3. Contact the opposite engineers to check the opposite ports for
possible failure.
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 ofice communication links through this port will not be available, and the services through this port are not available.
198005399 DSP resource is
unavailable
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Equipment Alarm
External Alarm
Alarm
Major
No
No
This alarm indicates the DSP resource is not available. It is monitored 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 normally.
2. HPI port error on DSP
3. DSP media plane communication failure.
Processing
Suggestion
4. DSP reset.
1. Check the operation maintenance log iles in network manager
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 Coniguration Management window, select Board, right click and select "Subunit Coniguration". Select
the DSP with alarm, and click Status at Subunit ConigurationStatus 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 Coniguration 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:
Conidential and Proprietary Information of ZTE CORPORATION
29
ZXWR RNC Alarm and Notiication Handling Reference
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
5. Replace the board.
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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Equipment Alarm
External Alarm
Alarm
Major
Yes
Frequently
Reported
No
Processing
Suggestion
1. If the alarm is declared by master board rather than slave
board, perform master/slave switching.
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.
Cause of Alarm
Hardware is faulty.
2. Replace the board where the alarm is declared.
2. If this alarm occurs to slave board, service will not be affected.
198026117 PP2S clock reference
lost
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
30
Equipment Alarm
External Alarm
Alarm
Major
Yes
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
No
Hardware is faulty.
1. If the board where the alarm is declared is ICM, please replace
the board.
2. If the board where the alarm is declared is CLKG: 1)Check the
connection between CLKG and GCM. 2)Replace the CLKG. 3)Replace the GCM.
System could not get the needed clock, which will cause processing
abnormity related to the clock.
198026118 16CHIP clock reference
lost
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Equipment Alarm
External Alarm
Alarm
Major
Yes
Frequently
Reported
No
Processing
Suggestion
Replace the board.
Cause of Alarm
Alarm Impact
Replace the board that is alarming.
The system can not get wanted clock, therefore all clock-related
processes are abnormal.
198026127 Clock reference source
lost (Level 3 alarm)
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Equipment Alarm
External Alarm
Alarm
Minor
No
No
Input clock reference is in unavailable status for no more than 10
minutes. Probable causes include:
1. Clock reference input is abnormal.
Conidential and Proprietary Information of ZTE CORPORATION
31
ZXWR RNC Alarm and Notiication Handling Reference
Processing
Suggestion
Alarm Impact
2. The conigured clock reference does not exist.
1. Re-connect the input clock reference.
2. For the clock reference not in use, delete the corresponding "Circuitry Clock Reference" coniguration on NMS coniguration
management interface (board property).
When all conigured clock reference sources are lost, the clock
board comes to free running or hold-over state. Accuracy of output clock is determined by the crystal oscillator of clock board. No
impact on service.
198026128 Clock reference source
lost (Level 2 alarm)
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Equipment Alarm
External Alarm
Alarm
Major
No
No
Input clock reference is in unavailable status for more than 10
minutes and less than 24 hours. Probable causes include:
1. Clock reference input is abnormal.
Processing
Suggestion
Alarm Impact
2. The conigured clock reference does not exist.
1. Re-connect the input clock reference.
2. For the clock reference not in use, delete the corresponding "Circuitry Clock Reference" coniguration on NMS coniguration
management interface (board property).
When all conigured clock reference sources are lost, the clock
board comes to free running or hold-over state. Accuracy of output clock is determined by the crystal oscillator of clock board. The
clock loss leads to synchronization failure between system clock
and clock reference source. Service interruption might occur. The
system will not be affected if the following two events happen together.
1. Input clock reference source is lost.
2. The phase-locked loop locks other clock reference source.
198026129 Clock reference source
lost (Level 1 alarm)
Alarm Type
32
Equipment Alarm
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
Alarm Purpose
Alarm Classiication
Alarm Level
External Alarm
Alarm
Critical
Disaster Alarm
No
Cause of Alarm
Input clock reference is in unavailable status for more than 24
hours. Probable causes include:
Frequently
Reported
No
1. Clock reference input is abnormal.
Processing
Suggestion
Alarm Impact
2. The conigured clock reference does not exist.
1. Re-connect the input clock reference.
2. For the clock reference not in use, delete the corresponding "Circuitry Clock Reference" coniguration on NMS coniguration
management interface (board property).
When all conigured clock reference sources are lost, the clock
board comes to free running or hold-over state. Accuracy of output clock is determined by the crystal oscillator of clock board. The
clock loss leads to synchronization failure between system clock
and clock reference source. Service interruption will occur. The
system will not be affected if the following two events happen together.
1. Input clock reference source is lost.
2. The phase-locked loop locks other clock reference source.
198026131 CLKG board PLL
out-of-lock
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Equipment Alarm
External Alarm
Alarm
Minor
No
No
Hardware is faulty.
1. If the alarm is declared by master board rather than slave
board, perform master/slave switching.
2. Replace board.
1. If this alarm occurs to master board, system clock synchronization will fail and service interruption will occur.
2. If this alarm occurs to slave board, service will not be affected.
Conidential and Proprietary Information of ZTE CORPORATION
33
ZXWR RNC Alarm and Notiication Handling Reference
198026133 Output clock lost
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Equipment Alarm
External Alarm
Alarm
Major
No
No
Hardware is faulty.
1. If the alarm is declared by master board rather than slave
board, perform master/slave switching.
2. Replace board.
1. If this alarm occurs to master board, system clock synchronization will fail and service interruption will occur.
2. If this alarm occurs to slave board, service will not be affected.
198005632 Usage rate of board hard
disk above threshold
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
34
Equipment Alarm
External Alarm
Alarm
Major
Yes
No
1. Usage rate threshold coniguration is improper.
2. The usage of hard disk is over high.
1. Open the Coniguration Management windowMPX86 or MPX86/2
alarm parameter Hard Disk Full, check the threshold value in the
coniguration of Hard Disk Usage Alarm level. Increase the threshold value if the setting is not larger enough.
2. Clear the disk and delete the unnecessary iles or move the iles
to other external storage devices.
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.
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
198005637 Error in Rear Board That
Mismatches With Front Board
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Equipment Alarm
External Alarm
Alarm
Minor
No
No
1. Incorrect rear board is used.
2. Rear board failure.
Processing
Suggestion
1. Check the front board type for the correct rear board type, and
use the correct 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 interruption of the corresponding link.
2. Replace the defective rear board with a new rear board.
2. When the rear board is used for the access of internal control 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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Equipment Alarm
External Alarm
Alarm
Warning
Disaster Alarm
No
Cause of Alarm
The network port or board is faulty.
Frequently
Reported
No
Conidential and Proprietary Information of ZTE CORPORATION
35
ZXWR RNC Alarm and Notiication Handling Reference
Processing
Suggestion
Alarm Impact
1. Replace the board.
2. Replace the other board, that is, the board rather than the
faulty board in active/standby coniguration.
3. Replace the slot. Use the slot that supports GE channel between
boards.
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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Equipment Alarm
External Alarm
Alarm
Warning
No
No
IDE is operated for longer time.
No handling is necessary.
When hard disk work for long time without sleep, engine will be in
high speed spin state for long, this will inluence the life of disk,
and data will lose when disk be abnormal. Disk of some model
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.
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Equipment Alarm
External Alarm
Alarm
Major
No
No
1. User has set loop back.
2. Transmission is looped back by provider.
3. Local board is faulty.
36
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
4. Remote board is faulty.
Processing
Suggestion
5. Loop back applied on DDF.
1. Disconnect the loopback E1.
2. Restart the board.
3. Replace the board.
Alarm Impact
4. Replace the opposite board.
Data can not be sent out because of the loopback E1.
198005671 Incorrect FE Routing
Connection
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Equipment Alarm
External Alarm
Alarm
Critical
No
No
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).
Processing
Suggestion
4. When UIM is connected to UIM/CHUB, only one cable is used
for FE inter-connection.
Reconnect FE cables.
1. If RUIM1 rear board is used on BUSN shelf for FE routing connection, 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 opposite 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
Conidential and Proprietary Information of ZTE CORPORATION
37
ZXWR RNC Alarm and Notiication Handling Reference
Alarm Impact
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.
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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Equipment Alarm
External Alarm
Alarm
Major
No
No
elf board has cross-linked E1.
1. Disconnect the cross-linked E1.
2. Restart the board.
3. Replace the board.
Alarm Impact
4. Replace the board which connected to this board.
The data of cross-linked E1 can not be send out.
198005655 DSP Reports Exceptions
After Detection
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
38
Equipment Alarm
External Alarm
Alarm
Major
No
No
1. The HPI port fails
2. Hardware failure.
1. Reset the board.
2. Replace DSP sub-card.
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
Alarm Impact
3. Replace the board.
This DSP will be blocked and no longer available. The cell of this
DSP is out of service; the subscriber using this DSP is out of service; call loss rate might increase when call trafic is high.
198005124 Capacity of intra-shelf
control plane TRUNK communication
is insufficient
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Equipment Alarm
External Alarm
Alarm
Minor
No
No
1. Connection failure.
2. Circuitry failure.
3. Board failure.
Processing
Suggestion
4. Rear board failure.
1. Check about whether TRUNK connection is used for Inter-shelf
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.
Conidential and Proprietary Information of ZTE CORPORATION
39
ZXWR RNC Alarm and Notiication Handling Reference
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 trafic period, this may cause large delay or even service
interruption at extreme condition..
198005125 Incorrect Connection of
GE Optical Transceiver Module
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Equipment Alarm
External Alarm
Alarm
Minor
No
No
The iber optics connection error.
Check the iber optics for its proper cross connection, the detailed
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
Cause interruption to all services performed on this shelf.
198025602 TDM switch abnormal
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
40
Equipment Alarm
External Alarm
Alarm
Minor
No
No
1. Check for any clock alarms.
2. TDM Switch chip is faulty.
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
Processing
Suggestion
Alarm Impact
3. Wrong board in conigured slot.
1. In NMS Coniguration Management interface, view the coniguration of IMA links. Do the values of HW and TS ields conigured
for IMA links conlict (for example, two A ends are conigured with
the same B end). If yes, modify the coniguration.
2. Replace the faulty board.
The link with abnormal connection is interrupted. Accordingly, services are affected.
198029952 802.3ah link fault
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Equipment Alarm
External Alarm
Alarm
Major
No
No
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.
Processing
Suggestion
Critical Event: An unspeciied critical event has occurred.
Link Fault:
1. Check the peer is or not right.
2. If right, change the optical iber and check the alarm.
3. If the alarm is alive, change the and check the alarm.
4. If the alarm is alive, change the board.
Dying Gasp:
Check the peer is or not down.
Critical Event:
1. Check the 802.3ah is or not enable, if it is disable, it can't
receive PDU.
2. If the 802.3ah is enable, if the port is optical, check the alarm
of Link Fault is or not alive, if the alarm is alive, the port can't
receive the PDU
3. Or not, change the good network cable.
Alarm Impact
4. If the alarm is alive, change the peer board.
Link Fault:
The port can't receive data, the operations will interrupt.
Dying Gasp:
The port can't receive data, the operations will interrupt.
Conidential and Proprietary Information of ZTE CORPORATION
41
ZXWR RNC Alarm and Notiication Handling Reference
Critical Event:
The 802.3ah is failed, can't detect the fault of link.
198005669 Synchronization status
check of FPGA failed
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Equipment Alarm
External Alarm
Alarm
Critical
No
No
Synchronization status check of FPGA and SPI4/VSC872/VSC874
failed. It's usually caused by hardware exceptions. For example,
the clock chip works abnormally.
Replace the board.
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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
42
Equipment Alarm
External Alarm
Alarm
Critical
No
No
Memory check failed.
1. Make records of the alarm information.
2. Replace the board or subcard.
The operation related to the memory maybe failed.
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
198005403 Board SRAM self-check
fails
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Equipment Alarm
External Alarm
Alarm
Major
No
No
Hardware fault of board.
Replace the board, and check whether this alarm disappears.
Board operation might be abnormal.
198005404 Board OCXO oven fault
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Equipment Alarm
External Alarm
Alarm
Major
No
No
Hardware fault of board.
Replace the board, and check whether this alarm disappears.
Board operation might be abnormal.
198005405 Clock board phase-lock
loop work mode abnormal
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Equipment Alarm
External Alarm
Alarm
Major
No
Conidential and Proprietary Information of ZTE CORPORATION
43
ZXWR RNC Alarm and Notiication Handling Reference
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
No
1. There is no available reference source.
2. The clock distribution line is incorrect or there exists self loop.
3. The secondary clock locks the tertiary clock.
1. Check if the corresponding clock reference is correctly inputted.
2. Replace the board.
The designated reference clock cannot be phase-locked.
Communication Alarm
198000256 Ethernet physical link
broken
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Communication Alarm
External Alarm
Alarm
Minor
Yes
No
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.
1. Check whether a network cable is connected to port OMC2.
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.
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.
44
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
198083021 CCP transmission link
fault
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Communication Alarm
External Alarm
Alarm
Major
Disaster Alarm
No
Cause of Alarm
Transmission fault to Node B
Frequently
Reported
Processing
Suggestion
No
Check the Node B corresponding to the faulty CCP to see if there
is any of the following transmission-related alarms. If yes, follow
the corresponding suggestions to handle it.
1. IP mode
Check the Alarm Management interface according to the association ID to see if there is any of the following association-related
alarms. If yes, follow the corresponding suggestions to handle it.
198066018 Association link congested
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 corresponding suggestions to handle it.
Alarm Impact
198018944 PVC Fault
The CCP transmission link is unavailable, so it cannot be used during radio link establishment. If the Node B still selects this CCP,
RNC messages cannot be sent to the Node B and the current services will be interrupted.
198001792 SDH/SONET fault
Alarm Type
Alarm Purpose
Communication Alarm
External Alarm
Conidential and Proprietary Information of ZTE CORPORATION
45
ZXWR RNC Alarm and Notiication Handling Reference
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Alarm
Critical
Yes
No
The alarm occurs when the receiving optical power is below optical
receiver sensitivity. Generally speaking, normal receiving optical
power range for optical modules is between -28 dBm and -8 dBm.
Optical signals within this range can be detected.
Probable causes for the alarm include:
1. The receiving optical iber/module of local SDH equipment is
faulty.
Receiving optical iber is faulty or disconnected.
Optical connector is polluted.
Receiving optical module is faulty.
2. The transmitting optical iber of opposite SDH equipment is
faulty.
Transmitting optical iber is faulty or disconnected.
Optical connector is polluted.
3. The optical transmission line of SDH equipment is faulty.
Tail iber and lange between iber distribution frame and the equipment at local end are faulty or disconnected.
The related connector is in poor contact.
4. The receiving optical power at local end is excessively low.
Optical power attenuation on the iber transmission line at receiving end is too much.
Opposite-end transmitting optical power is too low.
5. Operation of LOS insertion is performed at opposite end.
Manual operation of LOS insertion is performed in diagnostic test,
and optical module is shutdown by force.
6. Optical iber and optical module is incompatible.
Processing
Suggestion
The iber transmission rate of STM signals and the optical module
wavelength are incompatible.
1. Use meter measurement or loop test to judge whether the
alarm is caused by local end or opposite end.
Meter Measurement
Use a SDH test meter or optical power meter to test whether the
receiving optical signals at local end are normal. If normal, fault
might lie in local equipment. If abnormal, fault lies in opposite end
or on transmission side. Inform the opposite end or transmission
side to troubleshoot.
Loop Test
Perform iber self-loop at local SDH equipment. If the alarm persists, fault might lie in local equipment. If the alarm disappears,
inform the opposite end to troubleshoot.
46
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
2. Replace optical module.
3. Replace optical iber.
Alarm Impact
4. Replace board.
SDH/SONET fails to work normally, leading to UE access failure on
SDH/SONET and interruption of ongoing services.
198083036 DSAR Alarm
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Communication Alarm
External Alarm
Alarm
Minor
Disaster Alarm
No
Cause of Alarm
1. User plane resource initialization failure.
Frequently
Reported
No
2. CCH setup failure at Node B side.
3. CCH coniguration is deleted by OMCR.
Processing
Suggestion
4. The Bearer type of common transport channel is modiied by
OMCR.
View alarm details on the NMS Alarm Management interface to
check the Alarm Reason, which can help you easily ind the corresponding handling suggestions. The handling suggestions for each
alarm are as follows:
1.Alarm Reason: User plane resource initialization failure.
1) Click NE Information Coniguration on the NMS Coniguration
Management interface and select the corresponding Node B. Select
the Path Coniguration tab to check if all parameters, including the
forwarding bandwidth, are correctly conigured.
2) Click Path Group Coniguration on the NMS Coniguration Management interface to check if all parameters are correctly conigured.
2. Alarm Reason: CCH setup failure at Node B side. Click Base
Station Ground Resource Management on the NMS Coniguration
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 coniguration 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.
Alarm Impact
4. Others. The system will automatically reestablish the common
channel. No manual handling is required.
The common channel is unavailable, which falls into three cases.
Conidential and Proprietary Information of ZTE CORPORATION
47
ZXWR RNC Alarm and Notiication Handling Reference
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 function 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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Communication Alarm
External Alarm
Alarm
Minor
No
No
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.
Processing
Suggestion
Alarm Impact
3.Intermediate equipment is faulty.
1.Check the E1 link.
2.Check the transmission quality of intermediate equipment.
The available bandwidth to destination is less than occupied bandwidth.So service rate on this path group will be degraded.
198083039 IP channel of Iub
interface is faulty
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
48
Communication Alarm
External Alarm
Alarm
Minor
No
No
1. IP channel is down.
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
Processing
Suggestion
Alarm Impact
2. Packet loss rate exceed 25%.
Check the transmission quality of intermediate equipment.
Service and OMCB will choose other IP channel to transfer data.
198083040 TCP connect on IuBC
interface is interrupted
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Communication Alarm
External Alarm
Alarm
Minor
Disaster Alarm
No
Cause of Alarm
1. Interface board (GIPI) of local equipment is faulty.
Frequently
Reported
Processing
Suggestion
No
2. Intermediate equipment or opposite equipments faulty.
3. The network cable connection is loose or disconnected.
1. Check the interface board(GIPI) for the Related Alarms. Perform the recommended solution to process the possible alarms.
Related Alarms: 198066070 Board Ofline 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 intermediate equipment. If response timeout, contact the equipment
provider for solution.
Alarm Impact
3 .Check the physical connection on IuBC interface. If the connection is loose or broken, unplug and plug the cable or replace the
cable. If port indicator is on, the physical link must be normal.
The IuBC Broadcast is disabled.
198022784 BFD Session Interrupted
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Communication Alarm
External Alarm
Alarm
Minor
No
Conidential and Proprietary Information of ZTE CORPORATION
49
ZXWR RNC Alarm and Notiication Handling Reference
Frequently
Reported
Cause of Alarm
No
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.
Processing
Suggestion
5. Coniguration related to the BFD session is incorrect.
On NMS fault management interface, view alarm Details where information of source address and destination address of the BFD
session is given. The source address is the address of local equipment. The destination address is the address of BFD session terminal 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, indicating that the link is normal.
iii. In the case of response timeout, check if the coniguration of
related route and address is correct. If not, perform reconiguration and retest.
iv. In the case of response timeout despite correct route/address
coniguration, 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 conirmed
by ping, check if the BFD session coniguration at both ends is
correct. On NMS coniguration 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 consistent.
iii. Ensure that BFD session in at least one equipment plays the
“active” role.
iv. Ensure that BFD session exists at both ends, and coniguration
of source IP and destination IP matches.
50
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
v. Ensure that the hop mode (single hop/multihop) at both ends
are consistent.
vi. Check coniguration authentication information. Ensure that
the number of authentication information conigured at both ends
are consistent.
Alarm Impact
5. Reset the board where the interface is located.
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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Communication Alarm
External Alarm
Alarm
Major
Disaster Alarm
No
Cause of Alarm
1. The alarm occurs once in PPP port during board power-on, and
recovers after successful PPP negotiation..
Frequently
Reported
No
2. Physical link is down, or link transmission quality is poor.
Processing
Suggestion
3. Adjustment of PPP link parameter leads to link re-negotiation,
causing the alarm.
On NMS fault management interface, view alarm Details, where
the faulty PPP port ID is given.
1. Check cable connection at both ends. If the cable is disconnected 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 coniguration management interface (IPOverE1 coniguration), check Interface E1 No. and time slot coniguration.
Ensure that the relevant coniguration is consistent at both ends.
4. On NMS coniguration management interface, check PPP coniguration. Ensure that the relevant coniguration at both sides is
consistent.
Alarm Impact
5. On NMS coniguration management interface, check coniguration of DT and EIPI connection. Ensure the connection continuity
of PPP port at both ends.
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.
Conidential and Proprietary Information of ZTE CORPORATION
51
ZXWR RNC Alarm and Notiication Handling Reference
198018944 PVC link is down.
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Communication Alarm
External Alarm
Alarm
Minor
No
No
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.
1. On NMS fault management interface, view alarm Details where
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 coniguration management interface (PVC coniguration), 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 iber connector and interface are in good contact, or replace
the iber.
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 coniguration 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 troubleshooting.
6. Deactivate CC test at local end, or activate CC test at opposite
end.
For IMAB/APBE board:
52
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
To deactivate CC test at local end, initiate "PVC CC test" on NMS
test management interface. When coniguring 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 coniguring test parameters,
select "1: Activate CC" for activation type, select "1: B-A" for test
type.
For APBE2/DTA board:
Alarm Impact
Modify PVC CCINFO parameter of coniguration to active or deactivate CC test. CC test parameter is same to APBE/IMAB.
PVC is in faulty status. All services on the PVC are interrupted.
198019213 LIF Alarm of Near-End
Receiving Link
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Communication Alarm
External Alarm
Alarm
Major
Disaster Alarm
No
Cause of Alarm
Physical fault or connection error occurs to E1 link.
Frequently
Reported
Processing
Suggestion
No
On NMS fault management interface, view alarm Details where
information of IMA chip ID, IMA group ID, IMA link ID, and E1
index is given. Locate the faulty IMA link according to the given
information.
1. Refer to user’s networking plan to see if connection error exists.
2. On NMS fault management interface, check if E1-related alarm
exists in the board. If yes, refer to the corresponding alarm handling suggestion. Related alarms:
198066045 Trunk error
198066046 Trunk abnormal
Alarm Impact
198001026 Cell delineation do not synchronization about cell on
E1 link
IMA link is down. If several links are available in the IMA group,
bandwidth of the IMA group will be affected, and the number of
successful upper-layer service access will decrease. However, service interruption will not occur. If merely one link is available in
the IMA group, all services on the IMA group are interrupted.
Conidential and Proprietary Information of ZTE CORPORATION
53
ZXWR RNC Alarm and Notiication Handling Reference
198019214 LODS Alarm of Near-End
Receiving Link
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Communication Alarm
External Alarm
Alarm
Major
No
No
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.
Processing
Suggestion
5. Hardware is faulty.
On NMS fault management interface, view alarm Details where
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 lashes slowly, operation of the clock board must be normal.
Otherwise, reset/replace the clock board.
2. On NMS fault management interface, check if clock-related
alarm occurs in UIM/GUIM. If yes, input clock source must be abnormal. Refer to the corresponding alarm handling suggestion.
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 suggestion. Related alarms:
198066045 Trunk error
198066046 Trunk abnormal
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.
54
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
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, service interruption will not occur. If merely one link is available in
the IMA group, all services on the IMA group are interrupted.
198019215 RDI alarm of far end
receiving link
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Communication Alarm
External Alarm
Alarm
Major
Disaster Alarm
No
Cause of Alarm
1. Remote IMA link is not in activated status.
Frequently
Reported
Processing
Suggestion
Alarm Impact
No
2. Remote receiving direction is faulty.
On NMS fault management interface, view alarm Details where information of IMA chip ID, IMA group ID, IMA link ID, and E1 index
is given. Locate the faulty IMA link according to the given information. Check the working status of the relevant remote receiving
link by referring to the opposite equipment operation guide. If remote receiving link is not in activated status, activate the link.
IMA link is down. If several links are available in the IMA group,
bandwidth of the IMA group will be affected, and the number of
successful upper-layer service access will decrease. However, service interruption will not occur. If merely one link is available in
the IMA group, all services on the IMA group are interrupted.
198019223 Ne Group is in fault state
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Communication Alarm
External Alarm
Alarm
Major
Disaster Alarm
No
Cause of Alarm
1.All IMA links of this IMA group are broken.
Frequently
Reported
No
2.The peer-end IMA group is broken.
Conidential and Proprietary Information of ZTE CORPORATION
55
ZXWR RNC Alarm and Notiication Handling Reference
Processing
Suggestion
Alarm Impact
Fix the broken IMA links in the IMA group.
The IMA Group does not work.
198066026 Association path broken
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Communication Alarm
External Alarm
Alarm
Major
Yes
No
1. Network communication is faulty.
2. Control plane path in NE is interrupted.
3. Opposite equipment is faulty.
Processing
Suggestion
4. The route to remote address is lost.
On NMS fault management interface, view alarm Details, where
information of association ID, local address, and remote address
is given.
1. On NMS coniguration management interface (static route),
query the route information of the remote address. Locate the out
port according to the route information. Check if network cable of
the out port is disconnected or loose. If yes, unplug and plug the
cable or replace the cable.
2. On NMS coniguration management interface (SCTP association
coniguration), query the ID of the module where the association is
located. Check if the following alarm occurs in the relevant board.
If yes, refer to the corresponding alarm handling suggestion. Related alarm:
198066003 Control plane communication abnormal between board
and its home module
3. On NMS coniguration management interface (static route),
query if the route to the remote address of the association is conigured. If not, add the coniguration.
4. Check the intermediate equipment on association path. If the
routes to local address and remote address of the association are
not conigured, add the coniguration according to equipment operation manual.
5. Check at opposite end if the route to the local address of the
association is conigured. If not, add the coniguration.
Alarm Impact
56
6. Check if the opposite equipment is faulty. If yes, troubleshoot
at opposite end.
If multiple paths are available for the association and there exists
normal path, relevant services will not be affected. If merely one
Conidential and Proprietary Information of ZTE CORPORATION
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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Communication Alarm
External Alarm
Alarm
Minor
Disaster Alarm
No
Cause of Alarm
1. The port cable is not properly connected.
Frequently
Reported
No
2. The port cable is faulty.
2. The IC of external board port is faulty.
Processing
Suggestion
3. The corresponding board is faulty.
1. Reconnect the cable, ensure that the connection between this
port and the peer port is correct.
2. Replace the cable.
3. Replace the board.
Alarm Impact
4. Contact the opposite engineers to check the opposite ports for
possible failure.
The MAC port is unavailable or the low is limited.
198066045 Trunk error
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Communication Alarm
External Alarm
Alarm
Major
Disaster Alarm
No
Cause of Alarm
1. The receiving cable of local trunk equipment is faulty. The cable
is disconnected, or cable connector is broken.
Frequently
Reported
No
2. The transmitting cable of opposite trunk equipment is faulty.
The cable is disconnected, or cable connector is broken.
Conidential and Proprietary Information of ZTE CORPORATION
57
ZXWR RNC Alarm and Notiication Handling Reference
3. Trunk transmission line is faulty. The local DDF and equipment
are not properly connected.
Processing
Suggestion
4. Operation of LOS insertion is operated at opposite trunk equipment. Manual inset alarm operation is performed in diagnostic test
1. check whether the alarm is caused by local end or opposite end
via meter measurement or loop test. Meter Measurement Use a
trunk test meter to test whether the trunk receiving signals at local
end are normal. If yes, fault might lie in local equipment. If no,
troubleshoot at opposite end. Loop test Perform trunk self-loop at
local end. If the alarm persists, fault might lie in local equipment.
If the alarm disappears, troubleshoot at opposite end.
2. Replace trunk cable.
Alarm Impact
3. Replace board.
The trunk equipment fails to work normally. All services based on
the trunk are interrupted.
198066046 Trunk abnormal
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Communication Alarm
External Alarm
Alarm
Major
No
No
1. Trunk frame formats at local end and at opposite end are inconsistent.
2. The transmitting end of opposite trunk equipment is faulty.
3. Local trunk equipment is faulty.
4. Equipment grounding at both ends is bad.
Processing
Suggestion
5. Impedance mismatch occurs.
On NMS fault management interface, view alarm Details, where
Error type is listed. Locate the speciic handling suggestion according 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 coniguration management interface (subunit coniguration), Check whether frame type coniguration at local end and
at opposite end is consistent.
ii. On NMS coniguration management interface (subunit coniguration), Check whether impedance coniguration is correct.
iii. Check whether the grounding at both ends is proper.
58
Conidential and Proprietary Information of ZTE CORPORATION
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
Alarm Impact
2.Far-end alarm indication received by trunk of E1. Check the
alarm status at opposite end. Since the alarm origin is opposite
end, irst troubleshoot at opposite end.
All services based on the trunk are interrupted.
198066047 Abnormal status in
SDH/SONET
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Communication Alarm
External Alarm
Alarm
Critical
Disaster Alarm
No
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.
Frequently
Reported
No
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 identiier mismatch
This alarm will occur when J0 byte in "access point identiier" at receiving end and transmitting end is inconsistent with the expected
(the previous agreement between two ends). The alarm might be
caused by coniguration 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 section overhead) of local SDH equipment when alarms of optical signal 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.
Conidential and Proprietary Information of ZTE CORPORATION
59
ZXWR RNC Alarm and Notiication Handling Reference
When multiplex section B2 bit error 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.
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 equipment 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 identiier
mismatch, and high order path signal label mismatch are declared
in opposite SDH equipment.
10. High order path trace identiier mismatch.
This alarm will occur when J1 byte in "VC-4 path access point identiier" 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 coniguration inconsistency of J1
byte mode/value at both ends.
11. High order path unequipped.
This alarm will occur when the "VC-4 path signal identiier" received 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 opposite end.
The path conigured at opposite end is 0.
12. High order path signal label mismatch.
This alarm will occur when the "VC-4 path signal identiier" received by local SDH equipment is different from the expected one.
The alarm might be caused by coniguration inconsistency of C2
byte at both ends.
13. High order path 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 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.
60
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
The H4 byte in VC-4 path overhead is used as tributary unit multiframe indication. This alarm will occur when the following two
conditions are satisied.
Local- SDH equipment fails to receive the correct multiframe indication code.
Multiframe alignment fails for consecutive 8 frames
16. Tributary unit loss of pointer.
This alarm will occur, when for consecutive 8 frames, SDH equipment 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 identiier mismatch, and tributary unit signal
label mismatch are declared in opposite SDH equipment.
18. Tributary unit 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 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
identiier 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 conigured for the trunk.
20. Tributary unit trace identiier mismatch.
This alarm will occur when J2 byte in "TU-12 access point identiier"
received by local SDH equipment is different from the expected
(the previous agreement between two ends). The alarm might be
caused by coniguration inconsistency of J2 byte mode/value at
both ends.
21. Tributary unit unequipped.
This alarm will occur when the "VC-12 path signal identiier" received 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 conigured at opposite end is 0.
22. Tributary unit signal label identiier mismatch.
Processing
Suggestion
This alarm will occur when the "VC-12 path signal identiier" received by local SDH equipment is different from the expected code.
The alarm might be caused by coniguration inconsistency of V5
byte (bit5-bit7) at both ends.
Alarm details are displayed in NMS Alarm Management interface,
where fault type is given. You can easily ind handling suggestions
according to the fault type.
The handling suggestions for each fault type are described as below:
1.Regenerator section trace identiier mismatch
Conidential and Proprietary Information of ZTE CORPORATION
61
ZXWR RNC Alarm and Notiication Handling Reference
In NMS Coniguration Management interface, click SDH parameter
coniguration and select SDH Optical Channel Parameter to check
whether the coniguration of "J0 coniguration mode" and "regenerator section trace" at local end is consistent with those at opposite end. If no, modify the coniguration to keep consistency.
2. Multiplex section remote defect indication
Check alarm status in the multiplex section of opposite end. Because the alarm origin is from the opposite end, please solve the
problem at opposite end irst.
3. Multiplex section remote error indication
Check alarm status in the multiplex section of opposite end. Because the alarm origin is from opposite end (B2 bit error), please
solve the problem at opposite end irst.
4. High order path trace identiier mismatch
In NMS Coniguration Management interface, click SDH parameter
coniguration and select SDH Optical Channel Parameter to check
whether the coniguration of "J1 Mode 0" and "high order path
trace 0" at local end is consistent with those at opposite end. If
no, modify the coniguration to keep consistency.
5. High order path unequipped
In NMS Coniguration Management interface, click SDH parameter
coniguration and select SDH Optical Channel Parameter to check
the coniguration of optical channel payload type. If the conigured
value is 0, modify the coniguration.
6. High order path signal label mismatch
In NMS Coniguration Management interface, click SDH parameter
coniguration and select SDH Optical Channel Parameter to check
the coniguration of optical channel payload type. Ensure that the
parameter coniguration at both sides is the same.
7. High order path remote defect indication
Check alarm status in the high order path of opposite end. Because
the alarm origin is from opposite end, please solve the problem at
opposite end irst.
8. High order path remote error indication
Check alarm status in the high order path of opposite end. Because
the alarm origin is from opposite end (B3 bit error), please solve
the problem at opposite end irst.
9. Tributary unit remote defect indication/Tributary remote defect
indication (VC-11)
Check alarm status in the corresponding tributary unit at opposite
end. Because the alarm origin is from opposite end, please solve
the problem at opposite end irst.
10. Tributary unit trace identiier mismatch
In NMS Coniguration Management interface, click SDH parameter
coniguration and select SDH Optical Channel Parameter to check
whether the coniguration of "J2 mode" and “low order path trace”
at local end is consistent with those at opposite end. If no, modify
coniguration to keep consistency.
11. Tributary unit unequipped
62
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
In NMS Coniguration Management interface, click SDH parameter
coniguration and select SDH Optical Channel Parameter to check
the coniguration of tributary unit payload type. If the conigured
value is 0, modify the coniguration.
12. Tributary unit signal label identiier mismatch
In NMS Coniguration Management interface, click SDH parameter
coniguration and select SDH Optical Channel Parameter to check
the coniguration of tributary unit payload type. Ensure that the
parameter coniguration at both sides is the same.
13. Others
i. Use measurement instrument or loopback test to judge whether
the alarm is caused by local end or opposite end.
a. Measurement instrument
Use a SDH test instrument to test whether the received optical
signals at local end are normal. If normal, it means opposite end
has a fault. Please solve the relevant problem.
b. Loop Test
Carry out a self-loop test at local SDH equipment. If the alarm still
occurs, it means local end has a fault. If the alarm disappears, it
means opposite end has a fault. Please solve the relevant problem.
ii. Replace the optical module.
iii. Replace the optical iber.
Alarm Impact
iv. Replace the board.
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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Communication Alarm
External Alarm
Alarm
Minor
Disaster Alarm
No
Cause of Alarm
1. Attenuation of receiving signals of local SDH equipment is large.
Frequently
Reported
No
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.
Conidential and Proprietary Information of ZTE CORPORATION
63
ZXWR RNC Alarm and Notiication Handling Reference
Processing
Suggestion
1. Use meter measurement or loop test to judge whether the
alarm is caused by local end or opposite end.
Meter Measurement
Use a SDH test meter or optical power meter to test whether the
receiving optical signals at local end are normal. If normal, fault
might lie in local equipment. If abnormal, fault lies in opposite end
or on transmission side. Inform the opposite end or transmission
side to troubleshoot.
Loop Test
Perform iber self-loop at local SDH equipment. If the alarm persists, fault might lie in local equipment. If the alarm disappears,
inform the opposite end to troubleshoot.
2. Replace optical module.
3. Replace optical iber.
Alarm Impact
4. Replace board.
SDH/SONET equipment can work. However, call loss or noise occurs to all voice services on this optical path, and bit error occurs
on the data service channel.
198001026 Loss of ATM Cell
Synchronization over E1 Link
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Communication Alarm
External Alarm
Alarm
Major
No
No
1. Cell Header HEC (Header Error Check) is damaged, leading to
cell location failure in physical layer frame.
2. The alarm is caused by bottom layer fault. Cell HEC is handled
differently at local end and opposite end.
1. Check if the following alarm occurs in the board. If yes, refer
to the corresponding alarm handling suggestion.
Related alarms:
198066045 Trunk error
198066046 Trunk abnormal
2.
On NMS coniguration management interface, check if
SDH/SONET mode is conigured for both ends. Ensure that the
coniguration at both ends is consistent.
3. Use meter measurement or loop test to judge whether the
alarm is caused by local end or opposite end.
64
Conidential and Proprietary Information of ZTE CORPORATION
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 equipment. If abnormal, troubleshoot at opposite end.
Loop Test
Perform self-loop at local trunk. If the alarm persists, fault might
lie in local equipment. If the alarm disappears, inform the opposite
end to troubleshoot.
4. Replace trunk cable.
Alarm Impact
5. Replace board.
Data reception on E1 link is abnormal. If merely one E1 link is
available for the port, all services on the board will be down. Otherwise, port bandwidth will be affected, leading to decreased access
bandwidth. The number of successful upper-layer service access
related to the port will decrease, but service interruption will not
occur.
198066049 ATM link is down
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Communication Alarm
External Alarm
Alarm
Critical
Disaster Alarm
No
Cause of Alarm
1. Bottom layer physical link is abnormal.
Frequently
Reported
Processing
Suggestion
No
2. HEC handling at local end and opposite end is inconsistent.
1. Check if the following board alarm occurs. If yes, refer to corresponding alarm handling suggestion.
Related alarms:
198066045 Trunk error
198066046 Trunk abnormal
2.
On NMS coniguration management interface, check if
SDH/SONET mode coniguration exists at both ends. Ensure that
the coniguration at both ends is consistent.
3. Use meter measurement or loop test to judge whether the
alarm is caused by local end or opposite end.
Meter Measurement
Use a trunk test meter to test whether the receiving trunk signals
at local end are normal. If normal, fault might lie in local equipment. If abnormal, troubleshoot at opposite end.
Loop Test
Conidential and Proprietary Information of ZTE CORPORATION
65
ZXWR RNC Alarm and Notiication Handling Reference
Perform self-loop at local trunk. If the alarm persists, fault might
lie in local equipment. If the alarm disappears, troubleshoot at
opposite end.
4. Replace trunk cable.
Alarm Impact
5. Replace board.
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.
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Communication Alarm
External Alarm
Alarm
Minor
No
Yes
1. The network connected with FE/GE/ATM/MP/POS/E1 port is abnormal.
2. The board is in abnormal status.
3. Board hardware is faulty. For example, the network processor
subcard is not tightly inserted.
Processing
Suggestion
4. Other board hardware faults.
1. Unplug and plug port iber/network cable.
2. Replace port iber/network cable.
3. Reset board.
4. Unplug and plug board.
Alarm Impact
5. Replace board.
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
Alarm Type
Alarm Purpose
66
Communication Alarm
External Alarm
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm
Major
No
No
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.
1. Check if the following alarm exists in PSN board at the same
shelf. If yes, refer to the corresponding alarm handling suggestion.
Related alarm:
198019456 All high-speed links between line card and package
switching board are out of synchronism
2. Unplug and plug board.
Alarm Impact
3. Replace board.
If the fault lies in PSN board, service of the entire RNC NE will
become unstable. If the alarm persists, all services will be interrupted. If the fault lies in the board where the alarm is declared,
only the services on this board are affected.
198005378 Board HW Error
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Communication Alarm
External Alarm
Notiication
Minor
Disaster Alarm
No
Cause of Alarm
1. Clock is not synchronous.
Frequently
Reported
Processing
Suggestion
No
2. Either the board or the slot has a hardware fault.
1. Check whether the board has one of the following alarms. If
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 handling suggestions. Related Alarms
198026133 Output clock lost
198026129 Clock reference source lost (Level 1 alarm)
Conidential and Proprietary Information of ZTE CORPORATION
67
ZXWR RNC Alarm and Notiication Handling Reference
198026128 Clock reference source lost (Level 2 alarm)
198026127 Clock reference source lost (Level 3 alarm)
3. In Coniguration Management interface, check whether APS
protection is conigured when the SDTB/SDTB2 works in master/slave mode. How to check APS protection coniguration: In
the Coniguration Management interface, click Rack, select the
concerned board (SDTB/SDTB2). Then right click it. A shortcut
menu appears. Then select Optical Port APS Protection.
4. Replace the board.
Alarm Impact
5. Replace the slot 6. Replace the UIM/GUIM of the same shelf.
HW connection is affected and services carried over this HW are
interrupted.
198005651 IPMAC conflict when
OSS detects control plane
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
68
Communication Alarm
External Alarm
Alarm
Major
No
No
1. The board is not plugged in place.
2. Backplane DIP switch coniguration has been modiied.
1. Unplug and plug board.
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, reconigure the DIP
switch to keep consistency. Reset the relevant boards after reconiguration.
3. Reset board.
IPMAC Conlict 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.
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
198066003 Control plane
communication is abnormal between
board and its home module
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Communication Alarm
External Alarm
Alarm
Major
Yes
No
1. The board is not in position.
2. The board is faulty.
3. The control plane communication is abnormal.
Processing
Suggestion
4. The board is reset.
1. Check if the board is in position. If not, insert the board.
2. Reset the board. Wait for the board to be powered on.
3. Replace the board.
4. Replace the board slot.
Alarm Impact
5. Replace the UIM/GUIM board in the same shelf.
The services carried by the board are interrupted.
198066004 Control plane
communication is abnormal between
MP and OMP
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Communication Alarm
External Alarm
Alarm
Major
Yes
No
1. The board is not in position.
2. The board is faulty.
3. The control plane communication is abnormal.
Conidential and Proprietary Information of ZTE CORPORATION
69
ZXWR RNC Alarm and Notiication Handling Reference
Processing
Suggestion
4. The board is reset.
1. Check if the board is in position. If not, insert the board.
2. Reset the board. Wait for the board to be powered on.
3. Replace the board.
4. Replace the board slot.
Alarm Impact
5. Replace the UIM/GUIM board in the same shelf.
The board is blocked and the functions of the board are unavailable. As a result, all services of the units under this module are
unavailable.
198005382 Communication between
power board and OMP board is
abnormal
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Communication Alarm
External Alarm
Alarm
Major
No
No
1. The power board is not connected to the OMP or connection
failure occurs.
2. The rack number conigured for the rack in which this power
board locates is not consistent with the rack number switch set for
the power board.
1. Reconnect the 485 cable between the power board and OMP.
2. Make sure the rack number conigured for the rack in which this
power board locates is consistent with the rack number switch set
for the power board.
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
Alarm Type
Alarm Purpose
70
Communication Alarm
External Alarm
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Alarm
Major
No
No
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.
Processing
Suggestion
5. Service exceeds the processing capability of the board.
1. In Alarm Management interface, check whether there is an
internal media plane port abnormal alarm. If yes, please solve the
problem according to corresponding handling suggestion.
Related Alarm: 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
4. Replace the board.
5. Change a slot to insert the board.
Alarm Impact
6. Replace the UIM of the same shelf.
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 trafic is overloaded, services carried on the board
will be delayed. In serious situation, services may be interrupted.
198005397 Communication of
RAWMACIP channel is abnormal
Alarm Type
Alarm Purpose
Communication Alarm
External Alarm
Conidential and Proprietary Information of ZTE CORPORATION
71
ZXWR RNC Alarm and Notiication Handling Reference
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm
Major
No
No
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.
1. On NMS fault management interface, check if the UIM/GUIM
board in the same shelf has related alarms. If yes, follow the
suggestions on handling the related alarms. Related alarm:
198002560 Board CPU overloaded
2. Replace the board.
3. Replace the UIM/GUIM in the same shelf.
Alarm Impact
4. Replace the slot.
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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Communication Alarm
External Alarm
Alarm
Major
No
No
1. The board is faulty.
2. The line from UIM/GUIM to GLI is abnormal.
On NMS fault management interface, view the alarm details, which
give the test alarm type. You can quickly locate the handling
method according to the test alarm type. The handling suggestion 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
72
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
Alarm Impact
case, reconnect the cables between UIM/GUIM and GLI or replace
the cables. If optical ibers are used, replace the optical module.
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 indicates that media plane communication is abnormal. This causes
the service carried by this shelf to be interrupted.
198005121 Inter-shelf media plane
links abnormal
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Communication Alarm
External Alarm
Alarm
Major
Yes
No
1. The iber connection is error between shelves, or the iber is
not physically plugged.
2. The background coniguration of the board is inconsistent with
its foreground physical connection.
Processing
Suggestion
3. The transceiver of the board link detection packet is exceptional.
1. In the NMS Coniguration Management interface, select Unit
Connection Relation, then compare the coniguration with actual
physical connection. If it is different, adjust connection cables according to the coniguration.
2. Check the connection of optical iber and make sure it is in cross
connection. Is there any relevant alarm? If yes, please solve the
problem according to recommended handling suggestions.
Relevant Alarm: 198005125 GE optical transceiver module is
wrongly connected to left/right board slots at opposite end.
3. Replace the optical iber or the optical transceiver module so
that the SD indicator for the corresponding port is on.
4. Replace the local board.
Alarm Impact
5. Replace the opposite board.
The inter-shelf service bandwidth is reduced. The inter-shelf services may be interrupted if no backup is conigured.
Conidential and Proprietary Information of ZTE CORPORATION
73
ZXWR RNC Alarm and Notiication Handling Reference
198005122 Loss of Active/standby
communication link.
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Communication Alarm
External Alarm
Alarm
Minor
No
No
1. The board is conigured to be in active/standby mode, but the
opposite board is not in position.
2. Hardware Problem.
1. Make sure the board is conigured in active/standby mode, and
both active/standby boards are in position.
2. Check whether the opposite board has the following alarm. If
yes, please solve the problem according to recommended handling
suggestions.
Description: 198005379 Board ofline or CPU in reset status for a
long period
3. Replace the opposite board.
Alarm Impact
4. Change the slots of the active board and the slave board.
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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
74
Communication Alarm
External Alarm
Alarm
Minor
No
No
1. In a pair of FE ports, one has normal link but the other has link
error.
2. The hardware is faulty.
1. Check if only one cable is used to connect the port pair of the
rear board to the peer-end FE port. Ensure that both cables are
connected to the peer end.
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
2. Reconnect the cables or replace the cables.
3. Replace the rear board.
Alarm Impact
4. Replace the board.
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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Communication Alarm
External Alarm
Alarm
Minor
Disaster Alarm
No
Cause of Alarm
Shelf connect to the system with duplicate physical ID
Frequently
Reported
Processing
Suggestion
Alarm Impact
No
1.Check whether two shelf with same physical ID exists. Modify
the switch of one of the two shelfs and reset the shelf and board
if such connection exists.
2.Check if the board link to the same board by different link type.
Remove one of link type and reset the board if such connection
exists.
Boards in the shelf which power-on later power-on failure.
198066005 SCCP subsystem
unavailable
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Communication Alarm
External Alarm
Alarm
Minor
Yes
No
1. From the perspective of A, remote signaling point subsystem is
out of service.
2. From the perspective of A, remote signaling point is inaccessible.
Conidential and Proprietary Information of ZTE CORPORATION
75
ZXWR RNC Alarm and Notiication Handling Reference
3. Remote subsystem (for B) is conigured at A end, but the corresponding local subsystem (for B) is not conigured at B end.
4. Local subsystem (for B) is blocked at B end.
Processing
Suggestion
5. From the perspective of A, SCCP user is unconigured in remote
MTP3 or M3UA user coniguration.
1. Check whether there exists ofice (the ofice that corresponds
to the subsystem) inaccessible alarm. If yes, refer to the corresponding alarm handling suggestion. Related alarms:
198066010 MTP3 ofice inaccessible
198066014 M3UA ofice inaccessible
2. Unblock the subsystem in dynamic data management.
3. On NMS coniguration management interface, check the coniguration of signaling point code (for A) at A end. See if SCCP user
is included in user type coniguration. If no, add the coniguration.
Meanwhile, check the corresponding coniguration at B end.
4. Check whether the status of signaling point subsystem (for B)
is available at B end. If no, the signaling point subsystem at B end
must be out of service. Locate the cause for the abnormal status.
Alarm Impact
5. Check whether the signaling point subsystem (for B) is conigured at B end. If no, add the coniguration at B end.
Signaling data cannot be sent to and received from the relevant
subsystem. Access of new service under the corresponding ofice
fails, and release of the ongoing service occurs.
198066007 Broadband link overload
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Communication Alarm
External Alarm
Alarm
Minor
No
No
1.There are too many messages from upper layer service.
2.The number of links is insuficient.
3.Link load is uneven.
1. Check the counter of "Peak Trafic of Signalling Link" in MTP3B
signaling link performance statistics. If the load (nearly) reached
6000 during alarm occurrence, upper layer trafic must be heavy.
Add links to share load.
2. On NMS coniguration management interface, check the signaling link coniguration of NE. Add or delete links to ensure that the
number of links in a link set is two to the power of N. If there are
two link sets in the current route, ensure that two link sets have
the same number of links.
76
Conidential and Proprietary Information of ZTE CORPORATION
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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Communication Alarm
External Alarm
Alarm
Major
Yes
No
1. No service link exists in the ofice route.
2. TFP is received.
1. Check whether there is an unavailable link alarm. If yes, please
solve the problem according to corresponding handling suggestions. Related alarm: 198066011 MTP3 link unavailable.
2. Check whether the coniguration of ofice and link at opposite
end is correct.
UE fails to receive/transmit messages from/to the relevant ofice.
New services can not be accessed to this ofice, and existing services are interrupted abnormally.
198066011 MTP3 link unavailable
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Communication Alarm
External Alarm
Alarm
Major
Yes
No
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.
Conidential and Proprietary Information of ZTE CORPORATION
77
ZXWR RNC Alarm and Notiication Handling Reference
Processing
Suggestion
1. IN NMS Coniguration Management interface, click Signalling
Link Coniguration to check PVC coniguration. Make sure that the
coniguration of CVPI and CVCI should be the same at both ends.
2. In Dynamic Data Management, check link status. If it is interrupted and connected now and then, it means the link unavailability is caused by MTP3 link test failure.
1) In NMS Coniguration Management interface, check the coniguration of signaling point code at both ends. Ensure that the
coniguration is consistent at both ends.
2) In NMS Coniguration Management interface, check the coniguration of signaling link at both ends. Ensure that the coniguration
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.
Alarm Impact
5. The opposite end has released the relevant link. Ask the opposite end to deal with the alarm as link unavailable.
If several MTP3 links are available for the ofice, services will not
be affected. In the case of heavy trafic, link congestion may occur,
leading to loss of packets/calls and decreased PS call access rate.
If merely one link is available to the destination signaling point,
the ofice may become inaccessible. UE fails to receive/transmit
messages from/to the relevant ofice. New services can not be
accessed to this ofice, and existing services are interrupted abnormally.
198066014 RNC unable to connect
to M3UA office
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Communication Alarm
External Alarm
Alarm
Major
No
No
1. Association link is broken or application server (AS) is not in
serving status.
2. M3UA ofice is inaccessible because the remote ofice gives a
DUNS (destination signaling point unavailable) report.
1. Check whether there is an association link broken alarm. If
yes, please solve the problem according to corresponding handling
suggestions.
Related alarm: 198066019 Association link broken
78
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
2. In NMS Coniguration Management interface, view AS Static
Information to check whether a routing context exists. If yes,
view the relevant coniguration such as routing context ID, AS ID
and AS service mode.
The correct coniguration is described below.
i. The routing context ID and AS service mode must be the same
at both ends.
ii. AS ID must meet the following requirements: if ASP is conigured for local end, SGP should be conigured for opposite end; if
IPSP client is conigured for local end, IPSP server should be conigured for opposite end.
3. Re-activate the ASP in Dynamic Data Management.
Alarm Impact
4. Check whether the coniguration of relevant ofice is correct at
opposite end.
UE fails to receive/transmit messages from/to the relevant ofice.
New services can not be accessed to this ofice, and existing services are interrupted abnormally.
198066019 Association link broken
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Communication Alarm
External Alarm
Alarm
Major
Disaster Alarm
No
Cause of Alarm
1. The association is released in dynamic data management.
Frequently
Reported
No
2. Association coniguration is modiied at local end.
3. Association is released at opposite end.
Processing
Suggestion
4. Bottom layer link is faulty.
1. Establish the association in dynamic data management.
2. On NMS coniguration management interface, check association coniguration at local end and opposite end. Checking items
include protocol type of SCTP association, SMP module No, local
IP address, local port No., remote IP address, remote port No.,
the number of in/out streams. If the coniguration at both ends is
inconsistent, modify coniguration to keep consistency.
3. Ping the opposite board address to see if the network cable or
other intermediate link is faulty. Replace the cable if ping fails.
Alarm Impact
4. Check if the association is released at opposite end. If yes,
troubleshoot according to the corresponding cause.
1. If several association links are available to the destination ofice,
service will not be affected. In the case of heavy trafic, conges-
Conidential and Proprietary Information of ZTE CORPORATION
79
ZXWR RNC Alarm and Notiication Handling Reference
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
ofice, the ofice might become inaccessible. Reception and sending of messages from/to the relevant ofice fail. Access of new
services under this ofice fails, and abnormal release of ongoing
services occurs.
198029953 The Ethernet port state
is OAM loop back
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Communication Alarm
External Alarm
Alarm
Minor
No
No
The local port state is loop back because the peer port starts Ethernet OAM loop back request of 802.3ah.
Check if the peer port has started Ethernet OAM loop back test. If
yes, stop it, if no, disable local port Ethernet OAM.
The Ethernet link which is in loop back test can't bear service data.
198003841 The control plane
retransfer ratio over the threshold
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
80
Communication Alarm
External Alarm
Alarm
Major
No
No
There are some badly-touched boards in system environment and
the retransfer-ratio of RUDP packets increases.
Make records of the alarm information and contact ZTE Corporation.
The master board will change when slave is exist.
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
198083045 Common Channel setup
failed Alarm
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Communication Alarm
External Alarm
Alarm
Minor
Disaster Alarm
No
Cause of Alarm
1. Use plane resource initialization fails.
Frequently
Reported
No
2. Common channel establishment fails on Node B side.
3. CCH transport bearer setup fail.
4. Common channel coniguration is deleted in NMS.
Processing
Suggestion
5. Inner Procedure Fail.
Check the coniguration according to the following steps:
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 coniguration management interface (NE information
coniguration), select the relevant Node B. Check the correctness
of parameter coniguration on path coniguration interface. "Peer
service IP address" must be conigured in the same network segment with Node B IP address.
5. On NMS coniguration management interface (BS ground resource management), view IP parameter coniguration in IP and
route management. Ensure that at least one “COS” is selected.
6. On NMS coniguration management interface (NE information
coniguration), select the relevant Node B. Check the correctness
of parameter coniguration on path coniguration interface. Check
if forwarding bandwidth is conigured.
7.On NMS coniguration management interface (path group coniguration), view path group coniguration. Check the correctness
of parameter.
8. Check whether Node B alarm exist.
Alarm Impact
9. Contact with ZTE Corporation.
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.
Conidential and Proprietary Information of ZTE CORPORATION
81
ZXWR RNC Alarm and Notiication Handling Reference
3. If the PRACH carrying RACH is unavailable, UE access to the
cell will fail.
198066071 Link broken for board
fault
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Communication Alarm
External Alarm
Alarm
Minor
No
No
Board internal fault.
1. Note down detailed information.
1.1 Back up related local ofice coniguration data and peer-end
ofice coniguration data.
1.2 Back up related local ofice and peer-end ofice history alarms
and notiications, as well as current alarms.
Alarm Impact
1.3 Contact ZTE Corporation and end the alarm handling procedure.
This alarm may render some ofices inaccessible, or may result in
the congestion of other links.
198066066 AAL2 Path locally
blocked
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
82
Communication Alarm
External Alarm
Alarm
Minor
No
No
The Path is manually blocked from this AAL2 Node.
You can unblock the Path which is generated manually from the
operating interface.
No AAL2 connection can be established on the blocked path.
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
198066067 AAL2 Path remotely
blocked
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Communication Alarm
External Alarm
Alarm
Minor
Disaster Alarm
No
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.
Frequently
Reported
Processing
Suggestion
Alarm Impact
No
You can unblock the Path which is generated by adjacent node
from the operating interface of the adjacent node.
No AAL2 connection can be established on the blocked path.
198066068 AAL2 Path blocked by
broken PVC
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Communication Alarm
External Alarm
Alarm
Minor
Disaster Alarm
No
Cause of Alarm
The Path is blocked because of the broken PVC.
Frequently
Reported
Processing
Suggestion
Alarm Impact
No
The path can be available when PVC becomes available.
No AAL2 connection can be established on the blocked path.
Conidential and Proprietary Information of ZTE CORPORATION
83
ZXWR RNC Alarm and Notiication Handling Reference
Processing Alarm
198083020 RNC system resources
limits reached, no new UE's can
attach to the network
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Processing Alarm
External Alarm
Alarm
Major
No
No
1. High number of users trying to access the network.
2. Total number of tokens exhausted.
It is recommended to expand the capacity of the system.
The system will reject new services to ensure the quality of the
existing services.
198083024 GPS receiver on ICM is
abnormal
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
84
Processing Alarm
External Alarm
Alarm
Major
No
No
1. GPS subcard is not tightly inserted.
2. Hardware of GPS subcard is faulty.
1. Unplug and plug GPS subcard.
2. Replace GPS subcard.
GPS subcard mainly provides positioning function for RNC NE. The
subcard fault leads to handset positioning failure. Service is not
affected.
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
198019207 Near-End IMA Group
Configuration Failure
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Processing Alarm
External Alarm
Alarm
Critical
No
No
IMA group coniguration at local end and at opposite end is inconsistent.
On NMS fault management interface, view alarm Details where
information of the faulty IMA group is given.
On NMS coniguration management interface (IMA group coniguration), locate the corresponding IMA group according to the information given in alarm Details. Compare the coniguration of the
following parameters at both ends. If the coniguration at both
ends is inconsistent, modify coniguration at either end to keep
consistency.
"Near-End OMA Label"
"Rx Frame Length (cells)"
"Tx Frame Length (cells)"
Alarm Impact
"Near-End Symmetry"
All services on the IMA port are interrupted.
198015360 Microcode Is Abnormal
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Processing Alarm
External Alarm
Alarm
Major
Yes
Frequently
Reported
No
Processing
Suggestion
Wait for the board to reboot. If the alarm cannot be restored after
board rebooting, unplug and then plug the board. If the alarm still
cannot be restored, replace the board.
Cause of Alarm
Alarm Impact
Network Processor hardware is faulty.
The board will reboot. If the alarm can be restored after board
rebooting, all board services during rebooting will be down, but
Conidential and Proprietary Information of ZTE CORPORATION
85
ZXWR RNC Alarm and Notiication Handling Reference
access of new services to the board after rebooting will be successful. If the alarm cannot be restored after board rebooting, all
board services during and after rebooting will be down.
198023040 The number of board
alarms exceeds the threshold
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Processing Alarm
External Alarm
Alarm
Major
No
No
There are too many alarms for this board. The alarm pool is full
of board alarms.
Troubleshoot the current alarms in the system.
Alarm information loss might occur. No impact on user service.
198066031 The number of OMP
alarms exceeds the threshold
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
86
Processing Alarm
External Alarm
Alarm
Major
No
No
There are too many system alarms. The alarm pool is full of system alarms.
Delete the trivial alarms on NMS fault management interface.
Alarm information loss might occur. No impact on user service.
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
198066032 NTP time exceeds
threshold
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Processing Alarm
External Alarm
Alarm
Minor
No
No
1. Link between OMP and RPU is down.
2. NTP time and local time differs greatly.
1. On NMS fault management interface, check if the alarm related
to RPU board exists. If yes, refer to the corresponding alarm handling suggestion. Related alarm:
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 conigured from 0 to 100.
3. Please try to recover the alarm by synchronizing the NTP time
with the board local time manually.
Alarm Impact
4. Check whether the interval between alarm time and the current
environmental time exceeds 8 alarm periods. Check the synchronization period and modify it if it is too long. Make sure the NTP
server is working properly.
NTP time synchronization terminates, leading to interruption of
ongoing services.
198066027 SNTP failure
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing Alarm
External Alarm
Alarm
Minor
No
No
1. SNTP server does not exist or server operation is abnormal.
2. The conigured SNTP IP address in the database is inconsistent
with the real IP address.
3. Communication between RNC NE and SNTP server is down.
Conidential and Proprietary Information of ZTE CORPORATION
87
ZXWR RNC Alarm and Notiication Handling Reference
Processing
Suggestion
4. The time synchronization period conigured in the database
might be 0.
On NMS fault management interface, view alarm Details where
Alarm Reason is given. Locate the speciic handling suggestion
according to the given reason. The handling suggestions that correspond to different alarm reasons are described below.
1. Illegal DB coniguration. On NMS coniguration management interface (RNC ground resource management), check if SNTP server
IP address or SNTP synchronization period are incorrectly conigured. If yes, which means SNTP server IP is conigured as
255.255.255.255 or SNTP synchronization period is 0, correct the
coniguration.
2. Failed to get time from SNTP server.
i. Ensure that SNTP server exists and server operation is normal.
Alarm Impact
ii. Ensure that the conigured SNTP server IP address in the database and the real server IP are consistent.
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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
88
Processing Alarm
External Alarm
Alarm
Major
Yes
No
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
conigured on NMS.
1. For CMP and SMP, reset the board.
2. For OMP, set the start mode as "foreground start" on NMS and
then reset the board. Do as follows: On NMS software version
management interface, select the menu for querying foreground
(that is, RNC NE) board start mode. In the pop-up dialog box, set
the start mode to "foreground start".
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
Alarm Impact
This alarm has no effect on the service.
198005388 Startup File Does Not
Exist
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Processing Alarm
External Alarm
Alarm
Major
Yes
Frequently
Reported
No
Processing
Suggestion
1. Reset the active and standby OMPs.
Cause of Alarm
Alarm Impact
The startup coniguration ile is deleted.
2. Replace the board.
This alarm may cause OMP work abnormally, and the entire NE
services are affected.
198005398 Office ID is not set
correctly with control shelf.
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Processing Alarm
External Alarm
Alarm
Major
No
No
The ofice ID of a shelf where DIP switch locates is different from
that of a shelf where OMP locates.
Set the ofice ID of the shelf where DIP switch locates to be the
same as that of OMP belonged shelf.
The MAC address conlicts. The MAC and IP address veriication
fails. All boards on the shelf can not be powered on. All services
carried by the shelf are interrupted.
Conidential and Proprietary Information of ZTE CORPORATION
89
ZXWR RNC Alarm and Notiication Handling Reference
198066057 Database config is
different from file named bootcfg ini.
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Processing Alarm
External Alarm
Alarm
Major
No
No
After the start information of OMP is modiied, the active and
standby OMP boards are not restarted.
Restart the active and standby OMPs.
The bootcfg ini. ile contains the information on the ofice ID, district ID, OMP gateway, OMC MAC address, and OMC gateway mask.
If the information is modiied, the OMP cannot connect to OMC and
external network normally.
198005649 Port working mode
doesn't match with its setting.
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Processing Alarm
External Alarm
Alarm
Major
No
No
1. The local device does not support this mode setting.
2. The opposite device does not support this mode setting.
Alarm details are displayed in NMS Alarm Management interface,
where error mode type is given. You can easily ind handling suggestions 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 conigured. Replace the existing
board with one that supports such rate mode.
ii. For force mode, conigure the port with a suitable rate that is
supported by bottom layer in actual working status.
90
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
Do as follows:
In NMS Coniguration Management interface, irst ind subunit details, then set a suitable rate that is supported by bottom layer in
actual working status.
iii. For auto-adaptive mode, re-conigure an expected rate so that
it is consistent with actual port rate.
Do as follows:
In NMS Coniguration Management interface, irst ind subunit details, then set the rate to be expected one.
2. Duplex mode error
i. Determine which mode should be conigured. Replace the existing board with one that supports such mode conigured on RNC.
ii. For force mode, re-conigure the port to be in duplex mode that
is supported by bottom layer in actual working status.
Do as follows:
In NMS Coniguration Management interface, irst ind subunit details, then set a suitable working mode that is supported by bottom
layer in actual working status.
iii. For Auto-adaptive mode, re-conigure an expected duplex
mode so that it is consistent with actual port duplex mode.
Do as follows:
In NMS Coniguration Management interface, irst ind subunit details, 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 existing board with the one that supports master and slave mode
conigured on RNC.
ii. For force mode, conigure the port to be in master/slave mode
that is supported by bottom layer in actual working status.
Do as follows:
In NMS Coniguration Management interface, irst ind subunit details, then set a suitable GE port master/slave mode that is supported by bottom layer in actual working status.
iii. For Auto-adaptive mode, re-conigure an expected master/slave mode and ensure that it is consistent with actual port
master/slave mode.
Do as follows:
Alarm Impact
In NMS Coniguration Management interface, irst ind subunit details, then set the GE port master/slave mode to an expected one.
1. The port fails to work in conigured mode, therefore, it can not
be used. All services via the port are interrupted.
2. For auto-adaptive mode, the bandwidth of external port becomes insuficient. As a result, some services via the port are
interrupted.
Conidential and Proprietary Information of ZTE CORPORATION
91
ZXWR RNC Alarm and Notiication Handling Reference
198005123 DB Configuration Doesn't
Fit for Device
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Processing Alarm
External Alarm
Alarm
Minor
No
No
1. The type of physical board is incorrectly conigured.
2. A wrong board is inserted
1. The NMS coniguration management interface gives the rack
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.
The board fails to be normally powered on. The services carried
by the board are interrupted.
198005126 Incorrect FE Routing
Connection
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing Alarm
External Alarm
Alarm
Critical
No
No
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.
92
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
Processing
Suggestion
Reconnect the FE wire.
1. If the UIM board on the BUSN shelf uses RUIM1 backcard, make
sure FE-C1/2 port is used for routing port.
2. If the GUIM board is on BGSN shelf, make sure FE1 and FE2
ports are used as routing ports.
3. If TRUNK mode is used, numerous FE ports make up of a TRUNK
port for cascaded connection. In this case, make sure the both
ends are paired ports.
If the boards of the local board or the opposite board are not paired
port, please reconnect the FE wire and make sure the both ends
are used paired ports.
Here is an example of connection method:
i. When CHUB is connected with UIM/GUIM, the connecting wire
on RCHUB1/RCHUB2 of CHUB backcard must be used continuous
ports ( such as port1/port2 pair, port3/port4 pair, port5/port6 pair,
port7/port8 pair ) to connect with the pairs on the UIM/GUIM backcard.
ii. When UIM is connected with UIM/GUIM/CHUB, the ports on
UIM backcard must be used as paired. If RUIM1 backcard is used,
then two FE-C1/2 ports must be used for FE routing ports; if
RUIM2/RUIM3 backcard is used, then use FE1/FE2 pair, FE3/FE4
pair or FE5/FE6 pair for the FE routing ports.
Alarm Impact
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.
Control plane routing is disconnected, ports are switched over in
cycle, all services on this shelf are interrupted.
198066006 Broadband link
congestion
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Processing Alarm
External Alarm
Alarm
Minor
Yes
No
1. The conigured signaling PVS bandwidth is insuficient.
2. Bottom-layer physical transmission quality is poor.
1. Check the counter of "Peak Trafic of Signaling Link" in MTP3B
signaling link performance statistics. If the load (nearly) reached
6000 during alarm occurrence, upper layer trafic must be heavy.
Increase PVC bandwidth or add links to share load.
Conidential and Proprietary Information of ZTE CORPORATION
93
ZXWR RNC Alarm and Notiication Handling Reference
2. Check NMS alarms/notiications to see whether there exists
physical transmission alarm(s) /notiication(s) that occurred simultaneously with this alarm. If yes, refer to the corresponding
alarm handling suggestion. Alarms/Notiications related to physical transmission are listed below, with respect to access mode.
1) Fiber Access Mode
198001792 SDH/SONET fault
198066047 Abnormal status in SDH/SONET
198066048 SDH/SONET:Excessive Error Code
198005639 High Error Rate of Optical Interface
2)E1 Access Mode
198005647 High Error Rate at E1 Bottom Layer
198066045 Trunk error
198066046 Trunk abnormal
198000576 Trunk Slide
Alarm Impact
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.
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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
94
Processing Alarm
External Alarm
Alarm
Major
Yes
No
1. There are too many upper layer service messages.
2. Bottom layer link quality is poor, leading to frequent message
retransmission.
Processing
Suggestion
1. Add links to the ofice that is in service for the congested link.
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.
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.
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
198066018 Association congestion
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Processing Alarm
External Alarm
Alarm
Minor
No
No
1. Transmission quality of bottom layer link is poor.
2. Upper layer trafic in sending service data is heavy.
1. Check network cable connection. Ensure that the network cable
is tightly inserted.
2. Add association links to the ofice that is in service for the
congested association.
3. If intermediate equipment exists between local end and opposite end, check the transmission quality of intermediate equipment.
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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing Alarm
External Alarm
Alarm
Critical
No
No
1. Fiber connection is wrong.
2. APS backup mode is conigured differently between local end
and opposite end.
3. APS protection mode is conigured differently between local end
and opposite end.
4. The opposite equipment is faulty.
Conidential and Proprietary Information of ZTE CORPORATION
95
ZXWR RNC Alarm and Notiication Handling Reference
Processing
Suggestion
1. Check iber connection.
Check iber connection at both ends. Ensure that the work optical
ports at both ends are interconnected, and the protection optical
ports at both ends are interconnected.
On NMS coniguration management interface, locate the relevant
board in the rack. Right-Click the board and open board properties
page. Click Optical port APS protection to view the "Work optical
port" and "Protection optical port" conigured at local end.
2. Check APS backup mode coniguration at both ends.
Check APS backup mode (1 1 or 1:1) at local end to ensure coniguration consistency at both ends.
On NMS coniguration management interface, locate the relevant
board in the rack. Right-Click the board and open board properties
page. Click Optical port APS protection in the shortcut menu to
view the "Protection Type" (1+1 or 1:1).
3. Check APS protection direction at both ends.
Check APS protection direction (unidirectional or bidirectional)
conigured at local end. Ensure coniguration consistency at both
ends.
On NMS coniguration management interface, locate the relevant
board in the rack. Right-Click the board and open board properties
page. Click Optical port APS protection to view the "Protection
Direct" (unidirectional or bidirectional).
Alarm Impact
4. Check whether APS is supported by the opposite equipment.
Check whether APS coniguration is correct and has taken effect.
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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing Alarm
External Alarm
Alarm
Critical
No
No
1. Fiber connection is wrong.
2. APS backup mode is conigured differently between local end
and opposite end.
3. APS protection mode is conigured differently between local end
and opposite end.
96
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
Processing
Suggestion
1. Check iber connection.
Check iber connection at both ends. Ensure that the work optical
ports at both ends are interconnected, and the protection optical
ports at both ends are interconnected.
On NMS coniguration management interface, locate the relevant
board in the rack. Right-Click the board and open board properties
page. Click Optical port APS protection to view the "Work optical
port" and "Protection optical port" conigured at local end.
2. Check APS backup mode coniguration at both ends.
Check APS backup mode (1 1 or 1:1) at local end to ensure coniguration consistency at both ends.
On NMS coniguration management interface, locate the relevant
board in the rack. Right-Click the board and open board properties
page. Click Optical port APS protection to view the "Protection
Type" (1+1 or 1:1).
3. Check APS protection direction at both ends.
Check APS protection direction (unidirectional or bidirectional)
conigured at local end. Ensure coniguration consistency at both
ends.
Alarm Impact
On NMS coniguration management interface, locate the relevant
board in the rack. Right-Click the board and open board properties
page. Click Optical port APS protection to view the "Protection
Direct" (unidirectional or bidirectional).
1. When iber connection is correct and the working optical port
can work normally, services won't be affected.
2. When the working optical port is faulty, APS automatic protection switching function doesn't work, and services carried via this
optical port will be interrupted due to lack of protection.
198019714 APS configuration alarm.
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Processing Alarm
External Alarm
Alarm
Critical
No
No
Optical interface are not conigured for APS in 1:1 mode.
1. If board backup mode is conigured as 1:1 or 1+1 and SDH
optical interface is needed, at least one set of APS protection needs
to be conigured.
To conigure APS protection:
On NMS coniguration management interface, locate the relevant
board in the rack. Right-Click the board and open board properties
page. Click Optical port APS protection.
Conidential and Proprietary Information of ZTE CORPORATION
97
ZXWR RNC Alarm and Notiication Handling Reference
2. If board master/slave mode is not needed, modify board backup
mode into.
To conigure board backup mode:
Delete the relevant board on NMS coniguration management interface. Then recreate the board. Select board backup mode as
"None" during board creation.
3. If board backup mode is conigured as 1:1 and no SDH optical
interface is required, modify the board backup mode into 1+1.
To conigure board backup mode:
Alarm Impact
Delete the relevant board on NMS coniguration management interface. Then recreate the board. Select board backup mode as
"1+1" during board creation.
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
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Environment Alarm
External Alarm
Alarm
Minor
Yes
No
1. Fan is not working.
2. Fan has failed.
3. No fan connected.
Processing
Suggestion
4. Temperature sensor is faulty or setting is incorrect.
1. In NMS Coniguration Management interface, click Power Board
Alarm Parameters to view the upper threshold of rack temperature. If the coniguration is unreasonable, please modify it. The
recommended value of upper threshold is 70 degrees in Celsius.
2. Check the thermometer in equipment room to see if the actual
temperature is too high. If yes, take necessary cooling measures.
3. Remove dust from air intake and outlet of the rack. Remove
any obstacle nearby which may affect ventilation.
Alarm Impact
98
4. Ensure that the rack fan works normally.
1. If an unreasonable threshold is conigured, services will not be
affected.
Conidential and Proprietary Information of ZTE CORPORATION
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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Environment Alarm
External Alarm
Alarm
Minor
Yes
No
1. temperature sensor is not working.
2. Treshold is incorrect.
3. External room heating control not working.
1. In NMS Coniguration Management interface, click Power Board
Alarm Parameters to view the lower threshold of rack temperature. If the coniguration is unreasonable, please modify it. The
recommended value of lower threshold is 0 degrees Celsius.
2. Check the thermometer in equipment room to see if the actual
temperature is too low. If yes, take necessary warming measures.
Alarm Impact
3. Setting the sensor correctly.
1. If an unreasonable threshold is conigured, services will not be
affected.
2. If the alarm is caused by low rack temperature, board may work
abnormally and board services may be interrupted.
198025858 House temperature is
higher than high threshold
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Environment Alarm
External Alarm
Alarm
Minor
No
No
1. Threshold coniguration is unreasonable.
2. Actual temperature in equipment room is too high.
Conidential and Proprietary Information of ZTE CORPORATION
99
ZXWR RNC Alarm and Notiication Handling Reference
Processing
Suggestion
Alarm Impact
1. On NMS coniguration management interface (power board
alarm parameters), check the upper limit of equipment room temperature. Modify the threshold value if the previous coniguration
is unreasonable. The recommended high threshold value is 40.
2. Check the thermometer in equipment room to see if the actual
temperature is too high. If yes, take necessary cooling and ventilation measures.
1. If the alarm is caused by unreasonable threshold coniguration,
service will not be affected.
2. If the alarm is caused by high room temperature, board operation might be abnormal and board services might be interrupted.
198025859 House temperature is
lower than low threshold
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Environment Alarm
External Alarm
Alarm
Minor
No
No
1. Threshold coniguration is unreasonable.
2. Actual temperature in equipment room is too low.
1. On NMS coniguration management interface (power board
alarm parameters), check the lower limit of equipment room temperature. Modify the threshold value if the previous coniguration
is unreasonable. The recommended low threshold value is 0.
2. Check the thermometer in equipment room to see if the actual
temperature is too high. If yes, take necessary cooling and ventilation measures.
1. If the alarm is caused by unreasonable threshold coniguration,
service will not be affected.
2. If the alarm is caused by low room temperature, board operation might be abnormal and board services might be interrupted.
198025860 Rack voltage is high
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
100
Environment Alarm
External Alarm
Alarm
Minor
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Yes
No
1. The conigured threshold is unreasonable.
2. Actual voltage is too high.
1. In NMS Coniguration Management interface, click Power Board
Alarm Parameters to view the upper threshold of rack voltage. If
the coniguration is unreasonable, please modify it. For 48V power
supply, the recommended value of upper threshold is 57V; for 60V
power supply, the recommended value is 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.
1. If an unreasonable threshold is conigured, services will not be
affected.
2. If the alarm is caused by high voltage, board may work abnormally and board services may be interrupted.
198025861 rack voltage is low
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Environment Alarm
External Alarm
Alarm
Minor
Yes
No
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.
1. On NMS coniguration management interface (power board
alarm parameters), check the lower limit of rack voltage. Modify
the threshold value if the previous coniguration 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 speciic line whose voltage is below low threshold
according to the voltage index listed in alarm Details. Increase the
input voltage of that line.
1. If an unreasonable threshold is conigured, services will not be
affected.
2. If the alarm is caused by low voltage, board may work abnormally and board services may be interrupted.
Conidential and Proprietary Information of ZTE CORPORATION
101
ZXWR RNC Alarm and Notiication Handling Reference
198025862 Humidity is high
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Environment Alarm
External Alarm
Alarm
Minor
No
No
1. The conigured threshold is unreasonable.
2. Actual humidity in equipment room is too high.
1. In NMS Coniguration Management interface, click Power Board
Alarm Parameters to view the upper threshold of room humidity.
If the coniguration is unreasonable, please modify it. The recommended value of upper threshold is 90.
2. Check the hygrometer in equipment room to see if the actual
humidity is too high. If yes, take necessary dehumidifying measures.
1. If an unreasonable threshold is conigured, services will not be
affected.
2. If the alarm is caused by high room humidity, board may work
abnormally and board services may be interrupted.
198025863 Humidity is low
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Environment Alarm
External Alarm
Alarm
Minor
No
No
1. The conigured threshold is unreasonable.
2. Actual humidity in equipment room is too low.
3. Setting of the sensor is incorrect.
1. In NMS Coniguration Management interface, click Power Board
Alarm Parameters to view the lower threshold of room humidity.
If the coniguration is unreasonable, please modify it. The recommended value of upper threshold is 90.
2. Check the hygrometer in equipment room to see if the actual
humidity is too low. If yes, take necessary humidifying measures.
102
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
Alarm Impact
3. Setting the sensor correctly.
1. If an unreasonable threshold is conigured, services will not be
affected.
2. If the alarm is caused by low room humidity, board may work
abnormally and board services may be interrupted.
198025864 Fault in fan plug-in box
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Environment Alarm
External Alarm
Alarm
Minor
Yes
No
1. FAN module is not tightly inserted into the rack.
2. FAN module hardware is faulty.
Processing
Suggestion
1. Check if the FAN module is tightly inserted into the rack. If no,
unplug and plug the FAN module.
Alarm Impact
This alarm might lead to excessively high rack temperature, resulting in abnormal board operation and interruption of board services
2. Replace FAN module.
198025865 Rack door alarm
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Environment Alarm
External Alarm
Alarm
Minor
Yes
No
1. The rack door is not closed.
2. Door control connection is incorrect.
1. Open and re-close the rack door to ensure that the rack door
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 connected. Then close the rack door.
Conidential and Proprietary Information of ZTE CORPORATION
103
ZXWR RNC Alarm and Notiication Handling Reference
Alarm Impact
Service is not affected, but the alarm poses a potential safety hazard.
198025866 Smoke detected
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Environment Alarm
External Alarm
Alarm
Minor
Yes
No
1. The alarm device is faulty.
2. The smoke density in equipment room is too high.
3. Setting of the sensor is incorrect.
1. Quick ind the origin of smog.
2. If there is no smog in the equipment room, replace the smog
detector.
3. Setting the sensor correctly.
Services won't be affected, but there is a potential safety problem.
198025867 Infrared alarm
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
104
Environment Alarm
External Alarm
Alarm
Minor
Yes
No
1. Heat source (such as animal/human) comes near.
2. Coniguration of Infrared sensor is incorrect.
3. Infrared sensor is faulty.
1. Check if any animal or human comes near the infrared sensor.
If yes, remove the heat source. If no, check the infrared sensor
coniguration. If appropriate, sensor sensitivity can be somewhat
reduced.
2. The infrared sensor is faulty. Replace sensor.
1. If the alarm is caused by infrared sensor coniguration error,
system is not affected.
Conidential and Proprietary Information of ZTE CORPORATION
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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Environment Alarm
External Alarm
Alarm
Major
Yes
Frequently
Reported
No
Processing
Suggestion
1. Check earthing connection.
Cause of Alarm
Alarm Impact
Outdoor unit or equipment damaged by lightening.
2. Check lightning protection antenna.
3. Setting the sensor correctly.
The board may work abnormally due to lightning stroke. Accordingly, board services will be interrupted.
198066064 Loss of DC power supply
to rack
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Environment Alarm
External Alarm
Alarm
Minor
No
No
1. Circuit breaker has tripped.
2. No incoming DC supply from rectiier.
Is this shelf needed?
1. If yes, ensure that the atmosphere switch is closed and ALM
indicator is normal.
2. If no, screen the function of monitoring atmosphere switch.
In NMS Coniguration Management interface, click Power Board
Alarm Parameters; then set the status of atmosphere switch to be
screened.
3. Setting the sensor correctly.
Conidential and Proprietary Information of ZTE CORPORATION
105
ZXWR RNC Alarm and Notiication Handling Reference
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
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
QoS Alarm
External Alarm
Alarm
Minor
No
No
The conigured alarm threshold is less than the usual inter-board
communication trafic in input and output directions of the board
control plane.
On NMS coniguration management interface, check if the conigured alarm threshold of communication trafic in input and output
directions of the board control plane is too low. Recommended
value: 0xffffffff(4096M).
No impact on user service.
198066069 The number of times of
signaling data transfer exceeds the
allowed threshold of the license
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
106
QoS Alarm
External Alarm
Alarm
Major
No
Yes
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Alarm
Cause of Alarm
Processing
Suggestion
Alarm Impact
1.The number of allowed times of transfer is less than the actual
demand.
2.No proper license purchased.
1.Set the number of allowed times of transfer to a rational value.
2.Purchase proper license
The data transferred may be discarded
198083042 IU PS traffic over load
alarm
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
QoS Alarm
External Alarm
Alarm
Minor
No
No
IU PS trafic throughput exceed the threshold of license control.
Check if the whole throughput is over the provider's guaranteed
bandwidth limit authorized by license.
The trafic over the license threshold would cause packet loss and
service quality decrease.
198083043 IU CS traffic over load
alarm
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
QoS Alarm
External Alarm
Alarm
Minor
No
No
IU CS trafic throughput exceed the threshold of license control.
Check if the whole throughput is over the provider's guaranteed
bandwidth limit authorized by license.
The trafic over the license threshold would cause user service access reject.
Conidential and Proprietary Information of ZTE CORPORATION
107
ZXWR RNC Alarm and Notiication Handling Reference
198083044 IU traffic over load alarm
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
108
QoS Alarm
External Alarm
Alarm
Minor
No
No
IU CS and PS trafic throughput exceed the threshold of license
control.
Check if the whole throughput is over the provider's guaranteed
bandwidth limit authorized by license.
The trafic over the license threshold would cause CS user service
access reject or PS service quality decrease.
Conidential and Proprietary Information of ZTE CORPORATION
Chapter
3
Notification
Table of Contents
198083017 RUB board has reached maximum number of
routes............................................................................ 111
198070002 Iu interface global reset notiication .................. 111
198070003 Iu interface resource reset notiication ............... 112
198070004 RNC initiate Iu interface global reset failure notiication .......................................................................... 113
198070005 RNC initiate Iu interface resource reset failure notiication......................................................................... 113
198070008 RNC and Node B are conigured with different
CCPID............................................................................ 114
198070009 Broadcast failure ............................................ 114
198083025 Common Channel is abnormal .......................... 116
198070010 FTP failure and ile lost .................................... 117
198070011 RNC alarm storage disc is full ........................... 118
198083028 Performance ile server unavailable ................... 118
198083029 Unable to save Performance File ....................... 119
198083019 MicroCode subsystem failed to get the table of
coniguration .................................................................. 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 notiication .............. 125
198083035 Transport Path Occupied BandWidth Overload............................................................................... 126
198083037 All Local Cell ID conigured at RNC side are differ
from which on Node B side ............................................... 126
198020291 Protocol stack process failed to initialize during
power on........................................................................ 127
198020802 Conlicting IP address in subnet. ...................... 127
198020803 Conlicting 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 coniguration data from DBS .................................................. 132
198018240 TCP Receives RST Packet ................................. 133
198018241 TCP Connection Aborted .................................. 133
198018242 MD5 Veriication Failure ................................... 134
198018243 Wrong MD5 Message Abstract........................... 134
Conidential and Proprietary Information of ZTE CORPORATION
109
ZXWR RNC Alarm and Notiication Handling Reference
198023106 Board Self-Check Failure .................................. 135
198023107 The board initialization failure........................... 135
198023617 Coniguration ile 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 Notiication 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
198010560 No message response in the link for a long
time .............................................................................. 152
198011840 M3UA user ofice status change ........................ 152
198013888 ASP status changed ........................................ 153
198013889 AS status changed .......................................... 154
198013890 Sigtran error message received ........................ 154
198013891 Sigtran notiication message received ................ 155
198013892 Allocate memory fail ....................................... 156
198014144 Association establishment failed........................ 156
198014145 Association restart .......................................... 157
198025664 Abnormal Half-ixed Connection Changes ........... 158
198008005 Memory ile buffer overlow .............................. 159
198002625 Process is deadlocked...................................... 159
198002880 CPU occurs dead-loop...................................... 160
198005718 Two master clock ports is directly connected ........................................................................... 160
198005189 Notiication 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
110
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 3 Notiication
198083017 RUB board has
reached maximum number
of routes
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing Alarm
External Alarm
Notiication
Major
No
No
Too many route entries are conigured 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
Suggestion
1. Open the NMS Coniguration Management interface to delete
unused routes from Static Routes.
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. Open the NMS Coniguration Management interface to delete
the IP address of the unused port from Interface Coniguration.
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
Alarm Type
Alarm Purpose
Processing Alarm
External Alarm
Conidential and Proprietary Information of ZTE CORPORATION
111
ZXWR RNC Alarm and Notiication Handling Reference
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Notiication
Minor
No
No
1. RESET message is sent by CN.
2. The signaling point of the ofice related to the CN is inaccessible.
3. Global reset is triggered by NMS.
On NMS fault management interface, view notiication Details
where Alarm Reason is given. Locate the speciic alarm handling
suggestion according to the given reason. The handling suggestions 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. Related alarms:
198066005 SCCP SSN is invalid
198066010 MTP3 ofice inaccessible
198066014 M3UA ofice inaccessible
2.CN unaccessible. Check if transmission-related/board alarm occurs. If yes, refer to the corresponding alarm handling suggestion.
Related alarms:
198066005 SCCP SSN is invalid
198066010 MTP3 ofice inaccessible
198066014 M3UA ofice inaccessible
Alarm Impact
3.OMCR initiate IU reset. The alarm is caused by manual reset
operation. Check RNC NMS operation log to see if the reset operation exists. If yes, no handling is necessary.
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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
112
Processing Alarm
External Alarm
Notiication
Major
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 3 Notiication
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
No
No
RNC sends a RESET RESOURCE message.
Check if there is any of the following transmission-related alarms.
If yes, follow the corresponding suggestions to handle it.
198066005 SCCP subsystem unavailable
198066010 MTP3 ofice inaccessible
Alarm Impact
198066014 M3UA ofice inaccessible
The resource resetting service is released.
198070004 RNC initiate Iu
interface global reset failure
notification
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Equipment Alarm
External Alarm
Notiication
Major
No
No
The CN fails to respond to the resetting request from the RNC.
Check the basic information in the MSC SERVER/SGSN tab on the
NMS Coniguration Management interface to see if "MCC and MNC"
is consistent with that conigured for the CN. If not, modify the
coniguration.
New services will be rejected for 3 seconds.
198070005 RNC initiate
Iu interface resource reset
failure notification
Alarm Type
Alarm Purpose
Processing Alarm
External Alarm
Conidential and Proprietary Information of ZTE CORPORATION
113
ZXWR RNC Alarm and Notiication Handling Reference
Alarm Classiication
Alarm Level
Disaster Alarm
Notiication
Major
No
Frequently
Reported
No
Processing
Suggestion
Check the basic information in the MSC SERVER/SGSN tab on the
NMS Coniguration Management interface to see if "MCC and MNC"
is consistent with that conigured for the CN. If not, modify the
coniguration.
Cause of Alarm
Alarm Impact
The CN fails to respond to the resource resetting request from the
RNC.
It has no impact on services.
198070008 RNC and Node B
are configured with different
CCPID
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Processing Alarm
External Alarm
Notiication
Major
No
No
The CCP ID conigured on the RNC side is different from that on
the Node B side.
1. Click Base Station Ground Resource Management > Transport
Layer Management > SCTP stream coniguration on the NMS Coniguration Management interface, and then modify the CCP ID.
2. Click NE Information Coniguration on the NMS Coniguration
Management interface. Select the corresponding Node B and modify its CCP ID in Node B port coniguration.
Neither CCP ID will be available during service establishments.
198070009 Broadcast failure
Alarm Type
Alarm Purpose
114
Communication Alarm
External Alarm
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 3 Notiication
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Notiication
Major
Yes
Yes
1. The system broadcast of the cell is conigured incorrectly.
2. The transmission fails.
View alarm details on the NMS Alarm Management interface to
check the alarm cause, which can help you easily ind the corresponding handling suggestions.
The handling suggestions for each alarm are as follows:
1. Alarm cause: Failure in getting system information from database.
Check notiication details, where "bySIBType" is given. For example, "SIB type = 1" means that obtaining SIB1 fails. In this case,
check the Sib1-related parameters and make sure the coniguration is correct and complete.
Different types of SIBs correspond to different conigurations,
which must be checked as follows:
1) SIB type = 1
On NMS coniguration management interface (UE timers and constants information), check UE timers and counters in idle and connected status.
2) SIB type = 1
On NMS coniguration management interface (UTRAN cell), check
URA ID in UTRAN cell global information.
3) SIB type = 1
On NMS coniguration management interface (cell selection and
reselection), check cell selection/reselection information parameters and cell access limit parameters.
4) SIB type = 1
On NMS coniguration 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.
198066018 Association congestion
198066019 Association link broken
2) ATM Mode
a. Bottom layer transmission fault
Conidential and Proprietary Information of ZTE CORPORATION
115
ZXWR RNC Alarm and Notiication Handling Reference
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
b. Unavailable PVC link
Check to see if the following alarm exists. If yes, follow the corresponding suggestions to handle it.
Alarm Impact
Related alarm: 198018944 PVC Fault
The cell is unavailable and inaccessible, providing no service.
198083025 Common
Channel is abnormal
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Communication Alarm
External Alarm
Notiication
Major
No
No
1. User plane resource initialization failure.
2. CCH setup failure at Node B side.
3. CCH coniguration is deleted by OMCR.
Processing
Suggestion
4. The Bearer type of common transport channel is modiied by
OMCR.
View alarm details on the NMS Alarm Management interface to
check the Alarm Reason, which can help you easily ind the corresponding handling suggestions.
The handling suggestions for each alarm are as follows:
1. Alarm Reason: User plane resource initialization failure.
1) Click NE Information Coniguration on the NMS Coniguration
Management interface and select the corresponding Node B. Select
the Path Coniguration tab to check if all parameters, including the
forwarding bandwidth, are correctly conigured.
2) Click Path Group Coniguration on the NMS Coniguration Management interface to check if all parameters are correctly conigured.
2. Alarm Reason: CCH setup failure at Node B side.
116
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 3 Notiication
Click Base Station Ground Resource Management on the NMS Coniguration 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 coniguration 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.
Alarm Impact
The system will automatically reestablish the common channel. No
manual handling is required.
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 function 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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Processing Alarm
External Alarm
Notiication
Major
No
No
The FTP channel between NMS and RNC NE is faulty.
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.
The NMS cannot obtain alarm iles from the RNC and the alarm
information is lost. It has no impact on services.
Conidential and Proprietary Information of ZTE CORPORATION
117
ZXWR RNC Alarm and Notiication Handling Reference
198070011 RNC alarm
storage disc is full
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Processing Alarm
External Alarm
Notiication
Minor
No
No
1. Disk is full.
2. Disk is faulty.
1. Delete unnecessary iles from the hard disk or move them to
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.
The RNC cannot save alarm iles and the alarm information is lost.
It has no impact on services.
198083028 Performance file
server unavailable
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
118
Processing Alarm
External Alarm
Notiication
Minor
No
No
1. Performance ile server unavailable.
2. Break in communication between RNC and PM server
1. 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.
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 3 Notiication
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.
Alarm Impact
ii. Enter the SHELL command "ping 128.0.31.1" to see if the ping
test is successful. If not, troubleshoot the control-plane communication.
The Logservice cannot receive performance iles and the performance iles are saved on the ROMP..
198083029 Unable to save
Performance File
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing Alarm
External Alarm
Notiication
Minor
No
No
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.
Processing
Suggestion
5. The Logservice is unavailable, and the PM iles have already
existed for over two hours.
Check alarm details to ind the Failure cause during saving performance ile, and handle the alarm accordingly.
1. If the Failure cause is "Logservice disk space less than 100M",
delete unnecessary iles 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 iles 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 ile can not be saved", it means the board time has
been adjusted. In this case, no handling is required.
Conidential and Proprietary Information of ZTE CORPORATION
119
ZXWR RNC Alarm and Notiication Handling Reference
Alarm Impact
5. If the Failure cause is "The Logservice is unavailable, and the
PM iles have already existed for over two hours." the suggestion
is given for the alarm "198083028 Logservice is unavailable".
Either the LogService or the ROMP cannot save the performance
iles. Performance data will be lost.
It has no impact on services.
198083019 MicroCode
subsystem failed to get the
table of configuration
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing Alarm
External Alarm
Notiication
Minor
No
No
1. Failed to get the information of the RUIB.
2. Failed to get the coniguration of OMCB server.
3. Failed to get the coniguration of signal dispatch table.
4. Failed to get the coniguration of IP/UDP.
5. Failed to get the coniguration of L2 table.
6. Failed to get the coniguration of path information.
7. Failed to get the coniguration of pathgroup information.
Processing
Suggestion
8. Failed to get the coniguration of IUBC signal dispatch table.
On NMS alarm management interface, view notiication Details
where Alarm Reason is given. Locate the speciic handling suggestion 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 coniguration management interface, check whether “Board
Reassembling IP Fragments” is conigured. If no, perform the corresponding coniguration according to network planning. Make
sure to synchronize the coniguration data at NMS and RNC NE
after coniguration modiication. Only after synchronization can
the coniguration data take effect at RNC NE.
2.Alarm Reason: Failed to get the coniguration of OMCB server.
On NMS coniguration management interface, check whether master OMP IP is conigured. If no, perform the corresponding coniguration according to network planning. Make sure to synchronize the coniguration data at NMS and RNC NE after coniguration
120
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 3 Notiication
modiication. Only after synchronization can the coniguration data
take effect at RNC NE.
3.Alarm Reason: Failed to get the coniguration of signal dispatch
table. On NMS coniguration management interface (SCTP association coniguration), check whether the relevant ofice is conigured. If no, perform the corresponding coniguration according
to network planning. Make sure to synchronize the coniguration
data at NMS and RNC NE after coniguration modiication. Only after synchronization can the coniguration data take effect at RNC
NE.
4.Alarm Reason: Failed to get the coniguration of IP/UDP. On NMS
coniguration management interface (service IP for DSP), check
whether the relevant ofice is conigured in DSP service IP address.
If no, perform the corresponding coniguration according to network planning. Make sure to synchronize the coniguration data
at NMS and RNC NE after coniguration modiication. Only after
synchronization can the coniguration data take effect at RNC NE.
5.Alarm Reason: Failed to get the coniguration of L2 table. Make
sure to synchronize the coniguration data at NMS and RNC NE
after coniguration modiication. Only after synchronization can
the coniguration data take effect at RNC NE.
6.Alarm Reason: Failed to get the coniguration of path information. On NMS coniguration management interface (path coniguration), check whether the relevant ofice is conigured. If no, perform the corresponding coniguration according to network planning. Make sure to synchronize the coniguration data at NMS and
RNC NE after coniguration modiication. Only after synchronization can the coniguration data take effect at RNC NE.
7.Alarm Reason: Failed to get the coniguration of pathgroup information. On NMS coniguration management interface (path group
coniguration), check whether the relevant ofice is conigured. If
no, perform the corresponding coniguration according to network
planning. Make sure to synchronize the coniguration data at NMS
and RNC NE after coniguration modiication. Only after synchronization can the coniguration data take effect at RNC NE.
Alarm Impact
8.Alarm Reason: Failed to get the coniguration of IUBC signal dispatch table. On NMS coniguration management interface (IUBC
dispatch coniguration), check whether the dispatch information
is conigured. If no, perform the corresponding coniguration according to network planning. Make sure to synchronize the coniguration data at NMS and RNC NE after coniguration modiication.
Only after synchronization can the coniguration data take effect
at RNC NE.
The system impacts that correspond to different alarm causes are
described below.
1. Failed to get the information of the RUIB. The coniguration
information is used to reassemble the fragments of IP packets inputted into the equipment. Lacking the coniguration information
may cause processing failure of fragments of IP packets. Service interruption might occur or service processing rate might slow
down.
2. Failed to get the coniguration of OMCB server. Lacking the
coniguration information may paralyze OMCB function.
3. Failed to get the coniguration of signal dispatch table. Lacking
the coniguration information causes SCTP data transmission failConidential and Proprietary Information of ZTE CORPORATION
121
ZXWR RNC Alarm and Notiication Handling Reference
ure on the interface board. The service related to SCTP Protocol
on this board is down.
4. Failed to get the coniguration of IP/UDP. Lacking the coniguration information may cause processing failure of IUPS service,
or processing failure of other data based on IP transmission.
5. Failed to get the coniguration of L2 table. Lacking the coniguration information may cause communication failure within the
equipment. All services on the board might be down.
6. Failed to get the coniguration of path information. In the case
of ATM interface board, lacking the coniguration 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 ofice. In the case of IP interface board, lacking the
coniguration information may incur processing failure of IP packet
trafic control, leading to interruption of all services under this ofice.
7. Failed to get the coniguration of pathgroup information. In the
case of ATM interface board, lacking the coniguration 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 ofice. In the case of IP interface board, service
is not affected.
8. Failed to get the coniguration of IUBC signal dispatch table.
Lacking the coniguration information causes IUBC signal transmission 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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing Alarm
External Alarm
Notiication
Minor
No
No
1. OMCB IP is unconigured by RNC.
2. The remote IP address of PPP/MLPPP link is unconigured.
3. Information of DHCP Client is unconigured.
122
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 3 Notiication
Processing
Suggestion
On NMS fault management interface, view notiication Details
where Fail Cause is given. Locate the speciic 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 conigured.
On NMS coniguration management interface, check if “Manager
Node B IP” is conigured. If no, add the coniguration.
2.Fail Cause: Peer IP Address of PPP/MLPPP Link has not been
conigured. On NMS coniguration management interface (PPP parameter), check if remote IP address is conigured. If not, add the
coniguration.
Alarm Impact
3.Fail Cause: Information of DHCP Client has not been conigured. Compare DHCP Client's Identiier Information with engineering plan, and conig corresponding DHCP Client's Information On
NMS coniguration management interface.
The system impacts that correspond to different notiication
causes are described below.
1. RNC OMCB IP to Node B has not been conigured. Case 1 If Node
B has never fetched the OMCB channel coniguration information
(including OMCB SERVER IP address, OMCB gateway IP, and Node
B IP address) before notiication 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 coniguration information. Thus the
service as a whole is affected. Case 2 Node B has fetched the
OMCB channel coniguration information (including OMCB SERVER
IP address, OMCB gateway IP, and Node B IP address) before notiication occurs. If there is no coniguration modiication, OMCB
channel would not be affected. If there is coniguration modiication before notiication occurs, OMCB channel would be affected
in such a way that modiied service coniguration data fail to take
effect on Node B.
2. Peer IP Address of PPP/MLPPP Link has not been conigured.
Association link is interrupted. All services on the board are down.
3. Information of DHCP Client has not been conigured. DHCP
Client will not get Trafic Address, and service to the Client is broken.
198083030 Bandwidth
automatic adjustment is
useless
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Processing Alarm
External Alarm
Notiication
Minor
No
Conidential and Proprietary Information of ZTE CORPORATION
123
ZXWR RNC Alarm and Notiication Handling Reference
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
No
The intermediate equipment such as Router or Switch is out of service, 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 adjustment does not be executed.
Check the intermediate equipment.
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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Communication Alarm
External Alarm
Notiication
Minor
No
No
1. The local IP address or remote IP address coniguration is incorrect.
2. Interface board (GIPI) of local equipment is faulty.
3. Intermediate equipment or opposite equipments faulty.
Processing
Suggestion
4. The network cable connection is loose or disconnected.
1. On NMS coniguration management interface, check local IP
address, remote IP address and TCP connection mode. If the connection mode at local end is conigured as client, the connection
mode at opposite end should be conigured as server. Vice Versa.
2. On NMS coniguration management interface, check protocol
stack coniguration at both ends. In the case of direct connection, ensure that interface board addresses at both ends are in the
same network segment, and the next hop address is direct connect interface board address. In the case of not direct connection,
ensure that the next hop address is the intermediate equipment
address.
3. Check the interface board (GIPI) for the Related Alarms. Perform the recommended solution to process the possible alarms.
Related Alarms: 198066070 Board Ofline 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 inter124
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 3 Notiication
mediate equipment. If response timeout, contact the equipment
provider for solution.
Alarm Impact
5. Check the physical connection on IuBC interface. If the connection is loose or broken, unplug and plug the cable or replace
the cable. If port indicator is on, the physical link must be normal.
The IuBC Broadcast is disabled.
198083033 The deviation of
slave clock is too large.
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Equipment Alarm
External Alarm
Notiication
Minor
No
No
Clock crystal oscillator of Slave or Host is inaccurate. The inaccuracy result in Clock Deviation between Slave and Host over threshold (default threshold is 36 sec/hr) .
Lock the faulty Slave.
KPI Index of service in RNC will be low.
198083034 External Clock
of Slave lost notification
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Equipment Alarm
External Alarm
Notiication
Minor
No
No
External Clock of Slave Lost.
Lock the faulty Slave.
Conidential and Proprietary Information of ZTE CORPORATION
125
ZXWR RNC Alarm and Notiication Handling Reference
Alarm Impact
KPI Index of service in RNC will be low.
198083035 Transport
Path Occupied BandWidth
Overload
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing Alarm
External Alarm
Notiication
Minor
No
No
Available bandWidth of transport path is less than occupied bandWidth. Probable causes for the alarm include:
1.E1 link is broken.
2.Transmission quality of the transmission line is poor.
Processing
Suggestion
Alarm Impact
3.Intermediate equipment is faulty.
1.Check the E1 link.
2.Check the transmission quality of intermediate equipment.
The available bandwidth to destination is less than occupied bandwidth. Some services would be released in this transport path
selectively to avoid transport path congestion.
198083037 All Local Cell ID
configured at RNC side are
differ from which on Node B
side
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
126
Processing Alarm
External Alarm
Notiication
Minor
No
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 3 Notiication
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
No
1. The RNC is connected with other Node B incorrectly, not the
wanted Node B.
2. The radio resource data conigured at RNC side and Node B side
is inconsistent.
1Check if the RNC is connected with Node B correctly on Iub interface. If not, please reconnect RNC and Node B, and synchronize
the coniguration data to Node B. 2Check if the radio resource data
conigured at RNC and Node B is consistent. If not, please modify
the radio resource data correctly, and synchronize the coniguration data to RNC and Node B.
All cell belong to the Node B can not be established.
198020291 Protocol stack
process failed to initialize
during power on
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Equipment Alarm
External Alarm
Notiication
Major
No
No
Physical memory is insuficient
Ensure that the actual capacity of the physical memory is more
than 1GB.
RPU board will reboot automatically after 10 seconds.
198020802 Conflicting IP
address in subnet.
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Communication Alarm
External Alarm
Notiication
Major
Conidential and Proprietary Information of ZTE CORPORATION
127
ZXWR RNC Alarm and Notiication Handling Reference
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
No
No
1. This network port is conigured with the same IP address (including the virtual address in the same network segment) as another host in the local network.
2. The peer-end switch that connects with this network port has
a loop.
When an IP address conlict occur, the NMS will display the conlicted IP address. Meanwhile, the 5-tuple information of the conlicted local port, as well as the conlicted MAC address of the external device, can be detected.
1. Click Interface Coniguration on the NMS Coniguration interface
to check the local interface address. Modify the local interface
address or the IP address of the conlicted 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 satisied:
1) "198020802 Conlicting IP Address" and "198020803 Conlicting MAC Address in Subnet" concur;
2) Even though the local port IP address is changed, the two alarms
still exist.
Alarm Impact
In this case, check whether there is a cable that connects both
ports of the peer-end switch. If yes, remove the cable.
Board operation is normal. Communication network is faulty. All
services on this port are down.
198020803 Conflicting MAC
Addresses in Subnet
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
128
Communication Alarm
External Alarm
Notiication
Major
No
No
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.
When an MAC address conlict occurs, the NMS will display the
conlicted MAC address. Meanwhile, the 5-tuple information of the
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 3 Notiication
conlicted local port, as well as the conlicted MAC address of the
external device, can be detected.
1. Modify the MAC address of the local port or the conlicted MAC
address of the external device.
Find the conlicted local port according to the displayed 5-tuple information. Click Interface Coniguration on the NMS Coniguration
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 satisied:
1) "198020802 Conlicting IP Address" and "198020803 Conlicting MAC Address in Subnet" concur;
2) Even though the local port IP is changed, the two alarms still
exist.
Alarm Impact
In this case, check whether there is a cable that connects both
ports of the peer-end switch. If yes, remove the cable.
Board operation is normal. The notiication 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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Communication Alarm
External Alarm
Notiication
Minor
Disaster Alarm
No
Cause of Alarm
Failed to generate static ARP from the newly added IP address,because the number of static ARPs which generated by IP has
reached the maximum.
Frequently
Reported
Processing
Suggestion
Alarm Impact
No
Delete some proxy addresses conigured for virtual ports and
re-conigure IP address within the limit of static ARPs.
The external device failed to communicate with the IP address from
which no static ARP is generated.
Conidential and Proprietary Information of ZTE CORPORATION
129
ZXWR RNC Alarm and Notiication Handling Reference
198066065 SCTP Primary
Path Set Failed
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Processing Alarm
External Alarm
Notiication
Minor
No
No
The remote IP of the SCTP primary path conigured at application
layer is not included in the local address list of SCTP at opposite
end
On NMS fault management interface, view notiication Details,
where information of association ID and the primary path remote
IP address is given. If the primary path remote IP address listed
in notiication 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.
Alarm Impact
2. Add the "primary path remote IP address" given in notiication
Details into the local IP address list of the relevant SCTP.
This notiication 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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
130
Communication Alarm
External Alarm
Notiication
Major
No
Yes
The number of wrong frames or wrong symbols exceeds the
threshold.
Check Ethernet linkreceiver and transmitter of link.
Ethernet links can not transmit data credibly.
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 3 Notiication
198000576 Loss of Frame
on Trunk
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Equipment Alarm
External Alarm
Notiication
Major
No
No
Since frequency difference might exist between trunk line clock
and local receive clock, the trunk receive clock is not synchronous
with the transmit clock.
Check the clock synchronization status at both sides. If the status
is unsynchronized, check if LOL-related (loss of lock) alarm occurs
in clock board. If yes, refer to the corresponding alarm handling
suggestion.
Related alarms:
198026127 Clock reference source lost (Level 3 alarm)
198026128 Clock reference source lost (Level 2 alarm)
Alarm Impact
198026129 Clock reference source lost (Level 1 alarm)
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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Equipment Alarm
External Alarm
Notiication
Major
No
No
Check SPB/SPB_2/IWFB if they are working normal.
1. Unplug the board for 5 seconds, and plug it again after a full
discharge.
2. Replace the board.
Conidential and Proprietary Information of ZTE CORPORATION
131
ZXWR RNC Alarm and Notiication Handling Reference
Alarm Impact
All MCC channels cannot transmit or receive data.
198001600 CPU resets on a
board
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Equipment Alarm
External Alarm
Notiication
Major
Yes
No
1. User request CPU reset.
2. Board has reset itself due to fault.
Processing
Suggestion
1. Check the NMS operation log to see whether there is a manual
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.
2. Replace the board.
198017216 Error in MCS
Multi-Core processor
receiving configuration
data from DBS
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
132
Equipment Alarm
External Alarm
Notiication
Major
No
Yes
1.The coniguration data from DBS are exceptional.
2.Failure in adding a vital data table
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 3 Notiication
Processing
Suggestion
Alarm Impact
Check the data coniguration, if there is a coniguring error, correct
it and reboot the board.
It may cause packet forwarding problem since some vital data table is absent.
198018240 TCP Receives
RST Packet
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Communication Alarm
External Alarm
Notiication
Minor
Disaster Alarm
No
Cause of Alarm
1.The peer end initiates tcp connection resetting and sends a RST
packet.
Frequently
Reported
Processing
Suggestion
Alarm Impact
No
2.The peer end receives invalid tcp connection and returns a RST
packet.
Check if there is severe packet loss in physical link (It can be
checked by ping command), and handle physical link faults.
The corresponding connection aborts.
198018241 TCP Connection
Aborted
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Communication Alarm
External Alarm
Notiication
Major
Disaster Alarm
No
Cause of Alarm
1. The RNC is connected with other Node B incorrectly, not the
wanted Node B.
Frequently
Reported
No
2. The radio resource data conigured at RNC side and Node B side
is inconsistent.
Conidential and Proprietary Information of ZTE CORPORATION
133
ZXWR RNC Alarm and Notiication Handling Reference
Processing
Suggestion
Alarm Impact
1Check if the RNC is connected with Node B correctly on Iub interface. If not, please reconnect RNC and Node B, and synchronize
the coniguration data to Node B. 2Check if the radio resource data
conigured at RNC and Node B is consistent. If not, please modify
the radio resource data correctly, and synchronize the coniguration data to RNC and Node B.
All cell belong to the Node B can not be established.
198018242 MD5 Verification
Failure
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Processing Alarm
External Alarm
Notiication
Minor
No
No
MD5 veriication is not set for packets in application layer.
Check MD5 encrypted option of the two ends of application layer.
If an end does not set with MD5 encrypted option, then set MD5
encrypted option for this end.
Application layer communication failure.
198018243 Wrong MD5
Message Abstract
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
134
Processing Alarm
External Alarm
Notiication
Minor
No
No
When application layer is receiving messages, MD5 cryptographic
keys set on both ends are inconsistent.
Check if MD5 cryptographic keys set on both ends are the same.
Y->Please contact ZTE Corporation.
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 3 Notiication
Alarm Impact
N->Set the same MD5 cryptographic keys for both ends of application layer and inish the alarm handling.
Application layer communication failure.
198023106 Board
Self-Check Failure
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Equipment Alarm
External Alarm
Notiication
Minor
No
No
Board hardware is faulty.
Replace board.
The board fails to power on possibly, and the service or communication link related to this board is down.
198023107 The board
initialization failure
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Equipment Alarm
External Alarm
Notiication
Minor
No
No
Board hardware is faulty.
Replace board.
The board fails to power on and operate, resulting in UE access
failure and interruption of ongoing services.
Conidential and Proprietary Information of ZTE CORPORATION
135
ZXWR RNC Alarm and Notiication Handling Reference
198023617 Configuration
file is unusable
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Processing Alarm
External Alarm
Notiication
Major
No
No
During the process of system power-on,the DAT ile obtained from
VMM is unusable or the txt ile which saves coniguration data is
unusable.
On NMS fault management interface, view the alarm details, which
give the Additional Reason.
1.If it's the DAT ile error, then we need to reload the ile from VMM
and switch to the new ile.
2.if it's the TXT ile error,then take the following step:
1)Get the TXT ile from "/DOC0/DATA1" directory at RPU with File
Manager method.
2)Open the TXT ile and delete line "[CRC_DATFILE]=" and
"[CRC_TXTFILE]=".
3)Transmit the modiied TXT ile.
Alarm Impact
4)Reboot RPU.
1. DAT ile is unusable This error will make the saved data unrestorable and unconigurable if the conigured data was saved in
TXT ile.
2. TXT ile is unusable This error will make the saved data unrestorable.
198003138 FLASH device
initialize failed
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
136
Equipment Alarm
External Alarm
Notiication
Major
Yes
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 3 Notiication
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
No
The lash on the board is damaged.
Replace the relevant boards.
1. For a single OMP board, the lash fault may cause board start
up failure. For both master/slave boards with lash 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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Equipment Alarm
External Alarm
Notiication
Minor
No
No
Daylight saving time activated, clock changed accordingly
No handling is necessary.
No impact
198003395 End daylight
saving time
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Equipment Alarm
External Alarm
Notiication
Minor
No
No
Daylight saving time is de-activated and the system is back to
normal country clock
Conidential and Proprietary Information of ZTE CORPORATION
137
ZXWR RNC Alarm and Notiication Handling Reference
Processing
Suggestion
Alarm Impact
No handling is necessary.
No impact
198005441 Port status
on internal media plane
changed.
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Equipment Alarm
External Alarm
Notiication
Minor
No
No
1. Connection between UIM/GUIM and GLI is faulty.
2. Board is faulty.
On NMS fault management interface, view notiication Details
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.
Alarm Impact
2.If the port status is others, no handling is necessary.
The impact varies depending on the "Port status" given in notiication 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.
138
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 3 Notiication
198005448 485 seriel bus
link between CLKG/PWRD
and OMP is broken.
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Equipment Alarm
External Alarm
Notiication
Minor
No
No
1. 485 communication is interrupted.
2. The board is abnormal.
1. Unplug and plug the 485 cable.
2. Replace the 485 cable.
3. Replace the board.
The conigured clock reference/environment threshold fails to take
into effect. There is no impact on services.
198026177 CLKG reference
quality changed
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Equipment Alarm
External Alarm
Notiication
Minor
No
No
Clock quality of the CLKG board has changed.
Check the quality of external clock source.
System could not get the needed clock.
Conidential and Proprietary Information of ZTE CORPORATION
139
ZXWR RNC Alarm and Notiication Handling Reference
198026178 Clock work
mode changed
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Equipment Alarm
External Alarm
Notiication
Minor
No
No
The clock work mode of the CLKG board has changed.
No handling is necessary.
System could not get the needed clock.
198005705 MCU resets for
abnormities
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Equipment Alarm
External Alarm
Notiication
Major
No
No
Cause of Alarm
MCU Hardware is faulty.
Alarm Impact
CLKG_2 board is faulty.
Processing
Suggestion
Replace the board.
198005710 The result of
base selection of sets chip
Alarm Type
Alarm Purpose
140
Processing Alarm
External Alarm
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 3 Notiication
Alarm Classiication
Alarm Level
Disaster Alarm
Notiication
Minor
No
Frequently
Reported
No
Processing
Suggestion
No handling is necessary.
Cause of Alarm
Alarm Impact
After manual base switchover, man-machine command, or pressing panel button, SETS chip performs base locking operation (at
most for 2 minutes). This notiication is to inform the user of the
operation result of manual base selection
None.
198005711 clock reference
selection is being executed.
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Processing Alarm
External Alarm
Notiication
Minor
No
No
If previous operation about clock reference selection doesn't inish
and relevant result is not given yet, the system will screen any
new attempt to manually select clock reference. And in this case,
this notiication is declared.
No handling is necessary.
No impact on service.
198005712 The manual
select base will be run,
please wait for the result
Alarm Type
Alarm Purpose
Processing Alarm
External Alarm
Conidential and Proprietary Information of ZTE CORPORATION
141
ZXWR RNC Alarm and Notiication Handling Reference
Alarm Classiication
Alarm Level
Disaster Alarm
Notiication
Minor
No
Frequently
Reported
No
Processing
Suggestion
No handling is necessary.
Cause of Alarm
Alarm Impact
The notiication 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
None.
198005713 APC's RAM
error
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Equipment Alarm
External Alarm
Notiication
Major
No
No
Board hardware is faulty.
Replace board.
The board where RAM is located is down. ATM cell fails to be forwarded, and all board services are interrupted.
198005715 PP2S source
switched
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
142
Equipment Alarm
External Alarm
Notiication
Minor
No
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 3 Notiication
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
No
PP2S (Pulse Per 2 Seconds) source is changed at both system clock
and GPS receiver sides.
GPS-side PP2S has a higher priority. If PP2S is switched over from
GPS-side to system-side, check the GPS receiver and antenna feed
status.
None.
198005717 The physical
address information of the
board is incorrect
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Equipment Alarm
External Alarm
Notiication
Major
No
No
1. The DIP switch setting changes
2. The board is not inserted in position
Processing
Suggestion
1. Reset the board. After the resetting, the board re-calculates
and sets the MAC address according to the DIP switch.
Alarm Impact
The board fails to start up, or control plane communication is abnormal. As a result, users cannot gain access and existing services
are interrupted.
2. Insert the board tightly. Or, unplug and plug the board.
198005716 Type B fault on
board (GPS) phase-lock
equipment
Alarm Type
Alarm Purpose
Alarm Classiication
Equipment Alarm
External Alarm
Notiication
Conidential and Proprietary Information of ZTE CORPORATION
143
ZXWR RNC Alarm and Notiication Handling Reference
Alarm Level
Disaster Alarm
Major
No
Frequently
Reported
No
Processing
Suggestion
Check the antenna feeder input circuit of ICM board to ensure that
the board can best receive GPS signal source. The checking items
include:
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 dificulty in receiving satellite signals, and large phase
difference of 10M OCXO assistant phase control.
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.
Alarm Impact
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.
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 subsequent impact on service is described below.
1.For TDM transmission, all links based on the TDM transmission
medium (including the transmission link currently in service for UE
and cell transmission link) are affected. Packet loss might occur on
these links, leading to degradation of service quality. In the case
of serious packet loss, service interruption and handover failure
will occur. Even worse, the cell might be out of service.
2.For non-TDM transmission (for example, IP transmission), Iub
interface service is affected, while Iur interface and Iu interface
services are not affected. The clock that Node B derives from RNC
via IEEE1588 is inaccurate. When RNC clock frequency offset is
no more than 0.05 ppm, Node B synchronization will not fail, but
success rate of inter-RNC inter-Node B soft handover might fall.
When RNC clock frequency offset exceeds 0.5 ppm, Node B will
fail to lock the clock. In this case, Node B will oscillate freely and
success rate of inter-Node B soft handover might fall.
198005700 DSP resets for
abnormities
Alarm Type
Alarm Purpose
Alarm Classiication
144
Equipment Alarm
External Alarm
Notiication
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 3 Notiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Major
Yes
No
1. DSP chip is faulty.
2. Board is faulty.
DSP resets automatically and abnormally.
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.
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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Equipment Alarm
External Alarm
Notiication
Major
Yes
No
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.
Processing
Suggestion
3. Chip hardware is faulty.
On NMS fault management interface, view notiication Details
where "Loading corresponding alarm information" is given. Locate the corresponding handling suggestion based on the given
information.
1. Any of the following items displayed by "Loading corresponding alarm information" indicates that the chip fails to obtain the
needed version. On NMS software management interface, check
the conigured version for the chip and version status. Ensure that
the needed version is conigured for the chip and the version is activated.
i. DSP6416 No.d : No Version Information
ii.DSP5402 No.d : No Version Information
iii. MC fail to get version information
Conidential and Proprietary Information of ZTE CORPORATION
145
ZXWR RNC Alarm and Notiication Handling Reference
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.
Alarm Impact
iii.Replace board.
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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Equipment Alarm
External Alarm
Notiication
Major
No
No
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 exceeds 5 minutes.
Processing
Suggestion
146
5. APS changeover request/clearance is initiated by NMS.
View operation & maintenance log to see whether there is a
record, indicating an operator manually initiates APS changeover
request/clearance. If yes, no handling is necessary. If no, check
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 3 Notiication
whether there is one of the following alarms. If yes, please solve
the problem according to corresponding handling suggestions.
Related alarms:
198001792 SDH/SONET fault
198005396 Exceptional Internal Media Plane Communication
198005378 Board HW Error
Alarm Impact
198005635 The board is not plugged irmly.
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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Equipment Alarm
External Alarm
Notiication
Minor
No
No
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.
Processing
Suggestion
5. Bit error rate on the master/slave interconnecting link of GUIM
board is high.
Check if the following alarm occurs in local/opposite board. If
yes, refer to the corresponding alarm handling suggestion. Related alarms:
198001286 Loss of Clock When Input to Board
198005639 High Error Rate of Optical Interface
Alarm Impact
198005646 Phase-lock Loop Unlock
No impact on service.
Conidential and Proprietary Information of ZTE CORPORATION
147
ZXWR RNC Alarm and Notiication Handling Reference
198005192 Board's Work
Mode Unsupported
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Processing Alarm
External Alarm
Notiication
Minor
No
No
1. The conigured board backup mode is unsupported
2. FPGA is unloaded, leading to setting failure of board working
mode.
1. Check the coniguration of board backup mode. If the conigured backup mode is not supported by the board, modify coniguration or replace the board with one that supports such coniguration.
2. Unplug and plug board. Reload FPGA version.
Board master/slave backup function is disabled.
198005193 Notification of
the power-on status of the
basic process
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
148
Equipment Alarm
External Alarm
Notiication
Minor
No
No
1. Board power-on is successful.
2. Board power-on fails or expires.
On NMS fault management interface, view notiication Details
where information of power-on status ("Board poweron successful/failed/timeout") is given. Locate the corresponding handling
suggestion based on the given information. The handling sugges-
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 3 Notiication
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 Ensure that the board loads the proper version. The boards in a NE
must use the version of the same version No..
Alarm Impact
3. Board poweron successful/failed/timeout: Poweron failed Ensure that the board loads the proper version. The boards in a NE
must use the version of the same version No..
If the notiication is power-on success, service will not be affected.
If the notiication is power-on failure, the services on the board will
be unavailable.
198005956 Board Version
Error
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Processing Alarm
External Alarm
Notiication
Minor
No
No
1. A board is in the slot which is not conigured with any board.
2. Board version is unconigured.
3. Board version has been conigured, but version ile does not
exist or is damaged.
1. On NMS coniguration management interface (rack), view rack
layout. Check if the slot is conigured with any board. If no board
coniguration exists, unplug the board in the slot.
2. On NMS fault management interface, view notiication Details
where "Version type of abnormal board" is given. Load and activate the version on NMS software management interface according
to the given "Version type".
The board fails to obtain version, leading to abnormal board operation and access failure of board services.
Conidential and Proprietary Information of ZTE CORPORATION
149
ZXWR RNC Alarm and Notiication Handling Reference
198005958 IDE Version
Files Synchronization
Information
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Processing Alarm
External Alarm
Notiication
Minor
No
No
Synchronization of master/slave OMP version iles occurs.
On NMS fault management interface, view notiication Details
where "Synchronization information" is given.
1. If synchronization information is "Failed to obtain ile record
during synchronization" or "Synchronization failed", ind the name
of the version ile in notiication Details. According to the given ile
name, locate on NMS software management interface the corresponding version coniguration in the version ile database. Reload
the version ile to RNC NE. Delete the version ile if it is not in use.
2. If synchronization information is others, no handling is necessary.
1. IDE version ile synchronization occurs between master and
slave OMP (ROMB board). Service will not be affected by synchronization result.
2. In the case of synchronization failure, partial loss of version ile
will occur to slave OMP
198005961 OMP Version
Check Information
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
150
Processing Alarm
External Alarm
Notiication
Minor
No
No
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 3 Notiication
Cause of Alarm
Processing
Suggestion
Alarm Impact
The version ile in software version coniguration does not exist in
RNC NE.
On NMS fault management interface, view notiication Details
where "Version ile name" is given. According to the given
ile name, locate on NMS software management interface the
corresponding version coniguration in the version ile database.
Reload the version ile to RNC NE.
1. If the non-existent version ile is not in use, service will not be
affected.
2. If the non-existent version ile 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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing Alarm
External Alarm
Notiication
Minor
No
No
1. Patch version ile and CPU version ile do not match.
2. Patch version ile does not exist in RNC NE.
3. The patch version ile related to the patch does not exist in RNC
NE.
Processing
Suggestion
1. If the patch version is not needed, delete the corresponding
version coniguration on NMS software management interface.
Alarm Impact
Patch version activation fails. New functions of the patch version
are unavailable. No impact on service.
2. If the patch version is needed, locate on NMS software management interface the version coniguration of patch version ile
and related patch version ile in the version ile database. Reload
the version iles to RNC NE.
Conidential and Proprietary Information of ZTE CORPORATION
151
ZXWR RNC Alarm and Notiication Handling Reference
198010560 No message
response in the link for a
long time
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Communication Alarm
External Alarm
Notiication
Major
No
No
Bottom layer link quality is poor, there is no message response for
the link for a long time.
1. Check if physical connection works normally.
2. Check NMS alarms/notiications to see whether there exists
physical transmission alarm(s) /notiication(s) that occurred simultaneously with this alarm. If yes, refer to the corresponding alarm/notiication handling suggestion. Alarms/Notiications
related to physical transmission are listed below, with respect to
access mode.
1) Fiber Access Mode
198001792 SDH/SONET fault
198066047 Abnormal status in SDH/SONET
198066048 SDH/SONET:Excessive Error Code
198005639 High Error Rate of Optical Interface
2)E1 Access Mode
198005647 High Error Rate at E1 Bottom Layer
198066045 Trunk error
198066046 Trunk abnormal
Alarm Impact
198000576 Trunk Slide
Related link will be interrupted and cannot bear service.
198011840 M3UA user
office status change
Alarm Type
Alarm Purpose
152
Communication Alarm
External Alarm
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 3 Notiication
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Notiication
Major
No
No
1. User coniguration of this ofice is changed.
2. Bottom-layer links are unavailable.
3. The signaling network management message from opposite
end is received.
1. Check whether link interruption alarm occurs to the link/association. If yes, refer to the corresponding alarm handling suggestion. Related alarms:
198066011 MTP3 link unavailable
198066019 Association link broken
2. On NMS coniguration management interface, check if the M3UA
user is conigured in the relevant ofice. If no, add the coniguration.
Alarm Impact
3. Locate the cause for ofice status change at opposite end.
If M3UA user ofice status changes from accessible to inaccessible,
reception and sending of messages from/to the ofice fail. Access
of new services under the ofice fails, and abnormal release of the
ongoing service occurs. If M3UA user ofice status changes from
inaccessible to accessible, the system will return to normal state.
198013888 ASP status
changed
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Communication Alarm
External Alarm
Notiication
Minor
Disaster Alarm
No
Cause of Alarm
1. Association status is changed.
Frequently
Reported
Processing
Suggestion
No
2. ASP operation is performed at opposite end.
3. ASP operation is performed in dynamic data management at
local end.
1. Check whether association interruption alarm occurs. If yes,
refer to the corresponding alarm handling suggestion. Related
alarm:
Conidential and Proprietary Information of ZTE CORPORATION
153
ZXWR RNC Alarm and Notiication Handling Reference
198066019 Association link broken
2. Activate the ASP in dynamic data management.
Alarm Impact
3. Check whether ASP operation is performed at the opposite end.
If this notiication and the alarm of "198066014 M3UA ofice inaccessible" are declared at the same time, access failure of new
services under this ofice and abnormal release of ongoing services
will occur. If merely this notiication is declared, service will not
be affected.
198013889 AS status
changed
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Communication Alarm
External Alarm
Notiication
Minor
No
No
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.
1. Check whether association interruption alarm occurs. If yes,
refer to the corresponding alarm handling suggestion. Related
alarm:
198066019 Association link broken
2. Activate ASP under the AS in dynamic data management.
Alarm Impact
3. Check whether ASP operation is performed at the opposite end.
If this notiication and the alarm of "198066014 M3UA ofice inaccessible" are declared at the same time, access failure of new
services under this ofice and abnormal release of ongoing services
will occur. If only this notiication is declared, service will not be
affected.
198013890 Sigtran error
message received
Alarm Type
154
Communication Alarm
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 3 Notiication
Alarm Purpose
Alarm Classiication
Alarm Level
External Alarm
Notiication
Minor
Disaster Alarm
No
Cause of Alarm
1. AS coniguration is wrong.
Frequently
Reported
Processing
Suggestion
Yes
2. Protocol versions used at both sides are different.
1. Check AS coniguration to see whether the conigured trafic
mode at both sides are consistent. If no, modify coniguration to
keep consistency.
2. APP server AS ID coniguration must meet the following requirements. If ASP is conigured for local end, SGP should be conigured
for Opposite end. Vice versa. If IPSP client is conigured for local end, IPSP server should be conigured for opposite end. Vice
Versa.
3. Activate the ASP in dynamic data management.
4. On NMS coniguration management interface (AS coniguration), check if routing context and routing context ID are conigured. Ensure that the routing contexts conigured at both ends
are the same.
5. On NMS coniguration management interface, check whether
the local ASP in service for AS is conigured. If no, add the coniguration.
Alarm Impact
6. Check the protocol versions used at both sides. Ensure that the
protocol versions are the same.
The corresponding AS fails to be activated, making M3UA ofice
inaccessible. Reception and sending of message from/to the ofice
fail. Access of new services under the ofice fails.
198013891 Sigtran
notification message
received
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Communication Alarm
External Alarm
Notiication
Minor
No
Yes
Conidential and Proprietary Information of ZTE CORPORATION
155
ZXWR RNC Alarm and Notiication Handling Reference
Cause of Alarm
Processing
Suggestion
1. The broken association leads to insuficiency of the number of
ASP in service for AS.
2. Release of ASP in dynamic data management leads to insuficiency of the number of ASP in service for AS.
1. On NMS coniguration management interface (AS coniguration), query ASP-related associations. Check whether interruption
alarm occurs in the association(s). If yes, refer to the corresponding alarm handling suggestion. Related alarm:
198066019 Association link broken
2. Reactivate ASP in dynamic data management.
Alarm Impact
3. Check whether ASP operation is performed at the opposite end.
The number of ASP in service for AS is insuficient. If trafic is
heavy, congestion or packet loss might occur, leading to call loss
or increasing PS call access failures. Otherwise, service is not affected.
198013892 Allocate memory
fail
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Processing Alarm
External Alarm
Notiication
Minor
No
No
Memory is insuficient, that result in dynamic memory allocation
failure when the processor is is powered on.
1. Enlarge memory capacity and then restart the board.
2. If Application Server/Application Server Process is not conigured on this board, then the alarm should be ignored.
If Application Server/Application Server Process is not conigured
on this board, system will not be affected. Or else process will be
unstable.
198014144 Association
establishment failed
Alarm Type
156
Communication Alarm
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 3 Notiication
Alarm Purpose
Alarm Classiication
Alarm Level
External Alarm
Notiication
Major
Disaster Alarm
No
Cause of Alarm
1. Association coniguration at both sides is inconsistent.
Frequently
Reported
Processing
Suggestion
No
2. No less than two associations are conigured with same local
address and port, but with different protocol types.
3. Interface board IP address is wrong, or physical link is down.
1. On NMS coniguration management interface, check association coniguration at local end and opposite end. Checking items
include local IP address, local port No., remote IP address, remote
port No., and application property of SCTP association. If the association at local end is conigured as client, the association at
opposite end should be conigured as server. Vice Versa.
2. At local end, check whether the associations conigured with
different protocol types have the same local IP address and local
port No.. If yes, perform coniguration modiication to differentiate
the local IP address and local port No. of these associations.
3. Check protocol stack coniguration at both ends to see if interface board addresses are in the same network segment. If no,
modify coniguration to put two addresses in the same network
segment.
Alarm Impact
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.
If several association links are available to the destination ofice,
service will not be affected by establishment failure of one association. In the case of heavy trafic, congestion of available association(s) might occur, leading to upper layer call loss or increasing
PS call access failures. If merely one association link is available to
the destination ofice, the ofice might become inaccessible. Reception and sending of messages from/to the relevant ofice fail.
Access of services under this ofice fails.
198014145 Association
restart
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Communication Alarm
External Alarm
Notiication
Minor
No
Conidential and Proprietary Information of ZTE CORPORATION
157
ZXWR RNC Alarm and Notiication Handling Reference
Frequently
Reported
Cause of Alarm
No
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.
Processing
Suggestion
Alarm Impact
2.The Association link is reestablished at peer end.
No handling is necessarywait association to restart
None.
198025664 Abnormal
Half-fixed Connection
Changes
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Equipment Alarm
External Alarm
Notiication
Major
No
Yes
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.
1.Check alarms and notiications to see if the alarm(s)/notiication(s) related to input clock exist(s).Related alarm(s) and notiication(s) are listed below.
198026116 CLKG PP2S Output Clock Lost
198026127 Clock reference source lost (Level 3 alarm)
198026128 Clock reference source lost (Level 2 alarm)
198026129 Clock reference source lost (Level 1 alarm)
198026133 Clock Output Loss
Alarm Impact
158
2.Replace the faulty board.
TMD channel is interrupted momentarily, which might have a minor impact on service.
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 3 Notiication
198008005 Memory file
buffer overflow
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Processing Alarm
External Alarm
Notiication
Warning
Disaster Alarm
No
Cause of Alarm
The transferred data records exceed the maximum capacity of the
table, and the capacity of the receiver memory ile buffer is insuficient.
Frequently
Reported
Processing
Suggestion
Alarm Impact
No
Delete the excessive data records of the false table.
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
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Processing Alarm
External Alarm
Notiication
Major
Yes
Frequently
Reported
No
Processing
Suggestion
Note down the alarm information and contact ZTE Corporation.
Cause of Alarm
Alarm Impact
Maybe some resource ,such as semaphore, is deadlocked.
The process will never be scheduled, or timely resource release
fails, which results in resource exhaustion.
Conidential and Proprietary Information of ZTE CORPORATION
159
ZXWR RNC Alarm and Notiication Handling Reference
198002880 CPU occurs
dead-loop
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Processing Alarm
External Alarm
Notiication
Major
Yes
Frequently
Reported
No
Processing
Suggestion
The board will restart automatically when this alarm occurs. The
alarm will automatically disappear after restart.
Cause of Alarm
Alarm Impact
There exist dead loops in the processes or the system tasks.
The process or task of low priority level fails to be scheduled.
198005718 Two master
clock ports is directly
connected
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
160
Equipment Alarm
External Alarm
Notiication
Minor
No
No
The port is conigured as a master clock port in synchronous Ethernet, two master clock ports is directly connected.
Processing
Suggestion
If users do not want the other side to recover clock from this SyncE
port, it is normal.
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 master clock port.
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 reconigure the clock port or reconnect
the port.
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 3 Notiication
198005189 Notification of
Active/Standby Changeover
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Equipment Alarm
External Alarm
Notiication
Minor
No
No
It is hardware system fault. The CS domain of the UIM switches
over due to artiicial operation.
1. Analyze the switchover reason according to the additional information about the alarm .If it is not because of the system fault
but due to control of MML command at the background or caused
by non-active/standby 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
irstly.
The board whose changeover fails will reset automatically.
198026176 Clock reference
changed
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Equipment Alarm
External Alarm
Notiication
Warning
Disaster Alarm
No
Cause of Alarm
The currently locked clock reference has changed.
Frequently
Reported
Processing
Suggestion
Alarm Impact
No
No need to handle.
System could not get the needed clock, which will cause processing
abnormity related to the clock.
Conidential and Proprietary Information of ZTE CORPORATION
161
ZXWR RNC Alarm and Notiication Handling Reference
198020805 ARP detect
failed
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
Communication Alarm
External Alarm
Notiication
Minor
No
Yes
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.
1. Please check the device's IP address coniguration of the peer
end.
2. Please check physical link.
3. Please check the exchanger's VLAN coniguration.
The communication will be interrupted possibly.
198020806 ARP detect that
the static ARP is not match
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Disaster Alarm
Frequently
Reported
Cause of Alarm
Processing
Suggestion
Alarm Impact
162
Communication Alarm
External Alarm
Notiication
Minor
No
No
When the switch of the ARP detecting enabled, CE can send static
ARP request packet with the static ARP's IP periodically, if CE receives 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.
1. Please check remote device's MAC address.
2. Please check the switch VLAN coniguration.
The communication will be interrupted possibly.
Conidential and Proprietary Information of ZTE CORPORATION
Chapter 3 Notiication
198015168 AAL2 Path
blocked by resetting process
Alarm Type
Alarm Purpose
Alarm Classiication
Alarm Level
Communication Alarm
External Alarm
Notiication
Minor
Disaster Alarm
No
Cause of Alarm
The adjacent node doesn't has the same path.
Frequently
Reported
Processing
Suggestion
Alarm Impact
No
You can unblock the Path by adding the same path on the adjacent
node.
No AAL2 connection can be established on the blocked path.
Conidential and Proprietary Information of ZTE CORPORATION
163
ZXWR RNC Alarm and Notiication Handling Reference
This page is intentionally blank.
164
Conidential and Proprietary Information of ZTE CORPORATION
Figures
Conidential and Proprietary Information of ZTE CORPORATION
165
ZXWR RNC Alarm and Notiication Handling Reference
This page is intentionally blank.
166
Conidential and Proprietary Information of ZTE CORPORATION
Tables
Conidential and Proprietary Information of ZTE CORPORATION
167