ZXSDR BS8900 GU360 (V4.00) Outdoor GSM&UMTS Dual Mode Macro Node B Alarm Code Reference

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

Chapter 1.......................................................................... 1
Alarm Management ......................................................... 1
Overview .......................................................................1
Introduction of Terms ......................................................1
Alarm Code .......................................................................... 1
Severity .............................................................................. 2
Alarm Type .......................................................................... 2
Cause ................................................................................. 2
Handling.............................................................................. 2
Chapter 2.......................................................................... 3
Alarm Code....................................................................... 3
198084000 .......................................................................... 3
198084001 .......................................................................... 4
198084002 .......................................................................... 4
198084003 .......................................................................... 5
198084004 .......................................................................... 7
198084005 ........................................................................ 10
198084006 ........................................................................ 10
198084007 ........................................................................ 12
198084008 ........................................................................ 13
198084009.........................................................................15
198084010.........................................................................16
198084011.........................................................................18
198084012.........................................................................20
198084013.........................................................................20
198084014.........................................................................21
198084015.........................................................................21
198084016.........................................................................23
198084017.........................................................................24
198084018.........................................................................26
198084019.........................................................................28
198084020.........................................................................28
198084021.........................................................................30
198084022.........................................................................32
198084023.........................................................................33
198084024.........................................................................35
198084025.........................................................................36
198084026.........................................................................36
198084027.........................................................................37
198084028.........................................................................38
198084029.........................................................................40
198084030.........................................................................41
198084031.........................................................................42
198084032.........................................................................42
198084033.........................................................................42
198084034.........................................................................43
198084035.........................................................................44
198084036.........................................................................44
198084037.........................................................................45
198084038.........................................................................45
198084039.........................................................................46
198084040.........................................................................47
198084041.........................................................................48
198084042.........................................................................49
198084043.........................................................................50
198084044.........................................................................51
198084045.........................................................................52
198084046.........................................................................53
198084047.........................................................................53
198084048 ........................................................................ 54
198084049 ........................................................................ 55
198084050 ........................................................................ 55
198084051 ........................................................................ 55
198084052 ........................................................................ 56
198084053 ........................................................................ 56
198084054 ........................................................................ 57
198084055 ........................................................................ 57
198084056 ........................................................................ 58
198084057 ........................................................................ 59
198084058 ........................................................................ 60
198084059 ........................................................................ 60
198084060 ........................................................................ 60
198084061 ........................................................................ 61
198084062 ........................................................................ 61
198084063 ........................................................................ 62
198084064 ........................................................................ 62
198084065 ........................................................................ 63
198084066 ........................................................................ 64
198084067 ........................................................................ 64
198084068 ........................................................................ 65
198084069 ........................................................................ 66
198084070 ........................................................................ 68
198084071 ........................................................................ 70
198084072 ........................................................................ 71
198084073 ........................................................................ 74
198084074 ........................................................................ 75
198084075 ........................................................................ 76
198084076 ........................................................................ 77
198084077 ........................................................................ 78
198084078 ........................................................................ 78
198084079 ........................................................................ 79
198084080 ........................................................................ 81
198084081 ........................................................................ 82
198084082 ........................................................................ 83
198084083 ........................................................................ 83
198084084 ........................................................................ 83
198084085 ........................................................................ 84
198084086 ........................................................................ 85
198084087.........................................................................85
198084088.........................................................................86
198084089.........................................................................87
198084090.........................................................................88
198084091.........................................................................88
198084092.........................................................................89
198084093.........................................................................89
198084094.........................................................................90
198084095.........................................................................90
198084096.........................................................................91
198084097.........................................................................91
198084098.........................................................................92
198084099.........................................................................92
198084100.........................................................................92
198084101.........................................................................93
198084102.........................................................................93
198084103.........................................................................94
198084104.........................................................................95
198084105.........................................................................95
198084106.........................................................................96
198084107.........................................................................97
198084108.........................................................................98
198084109.........................................................................99
198084110....................................................................... 100
198084111....................................................................... 101
198084112....................................................................... 102
198084113....................................................................... 103
198084114....................................................................... 104
198084115....................................................................... 104
198084116....................................................................... 104
198084117....................................................................... 105
198084118....................................................................... 106
198084119....................................................................... 107
198084120....................................................................... 107
198084121....................................................................... 108
198084122....................................................................... 109
198084123....................................................................... 110
198084124....................................................................... 111
198084125....................................................................... 112
198084126 ...................................................................... 113

198084127 ...................................................................... 113
198084128 ...................................................................... 114
198084129 ...................................................................... 115
198084130 ...................................................................... 115
198084131 ...................................................................... 115
198084132 ...................................................................... 116
198084133 ...................................................................... 116
198084134 ...................................................................... 117
198084135 ...................................................................... 117
198084136 ...................................................................... 117
198084137 ...................................................................... 118
198084138 ...................................................................... 118
198084139 ...................................................................... 119
198084140 ...................................................................... 120
198084141 ...................................................................... 121
198084142 ...................................................................... 122
198084143 ...................................................................... 123
198084144 ...................................................................... 123
198084145 ...................................................................... 125
198084146 ...................................................................... 125
198084147 ...................................................................... 126
198084148 ...................................................................... 126
198084149 ...................................................................... 127
198084150 ...................................................................... 127
198084151 ...................................................................... 127
198084152 ...................................................................... 129
198084153 ...................................................................... 130
198084154 ...................................................................... 131
198084155 ...................................................................... 131
198084156 ...................................................................... 132
198084157 ...................................................................... 133
198084158 ...................................................................... 134
198084159 ...................................................................... 135
198084160 ...................................................................... 135
198084161 ...................................................................... 136
198084162 ...................................................................... 136
198084163 ...................................................................... 136
198084164 ...................................................................... 137
198084165....................................................................... 137
198084166....................................................................... 138
198084167....................................................................... 138
198084168....................................................................... 139
198084169....................................................................... 140
198084170....................................................................... 140
198084171....................................................................... 142
198084172....................................................................... 144
198084173....................................................................... 145
198084174....................................................................... 147
198084175....................................................................... 148
198084176....................................................................... 150
198084177....................................................................... 151
198084178....................................................................... 153
198084179....................................................................... 154
198084180....................................................................... 156
198084181....................................................................... 157
198084182....................................................................... 159
198084183....................................................................... 160
198084184....................................................................... 161
198084185....................................................................... 161
198084186....................................................................... 162
198084187....................................................................... 162
198084188....................................................................... 163
198084189....................................................................... 163
198084190....................................................................... 163
198084191....................................................................... 163
198084192....................................................................... 164
198084193....................................................................... 164
198084194....................................................................... 164
198084195....................................................................... 165
198084196....................................................................... 165
198084197....................................................................... 165
198084198....................................................................... 166
198084199....................................................................... 167
198084200....................................................................... 168
198084201....................................................................... 169
198084202....................................................................... 170
198084203....................................................................... 171
198084204 ...................................................................... 171

198084205 ...................................................................... 172
198084206 ...................................................................... 172
198084207 ...................................................................... 172
198084208 ...................................................................... 173
198084209 ...................................................................... 173
198084210 ...................................................................... 174
198084211 ...................................................................... 174
198084212 ...................................................................... 174
198084213 ...................................................................... 175
198084214 ...................................................................... 175
198084215 ...................................................................... 176
198084216 ...................................................................... 176
198084217 ...................................................................... 176
198084218 ...................................................................... 177
198084219 ...................................................................... 178
198084220 ...................................................................... 178
198084221 ...................................................................... 179
198084222 ...................................................................... 179
198084223 ...................................................................... 179
198084224 ...................................................................... 180
198084225 ...................................................................... 180
198084226 ...................................................................... 181
198084227 ...................................................................... 181
198084228 ...................................................................... 182
198084229 ...................................................................... 183
198084230 ...................................................................... 183
198084231 ...................................................................... 183
198084232 ...................................................................... 184
198084233 ...................................................................... 185
198084234 ...................................................................... 185
198084235 ...................................................................... 186
198084236 ...................................................................... 186
198084237 ...................................................................... 187
198084238 ...................................................................... 187
198084239 ...................................................................... 188
198084240 ...................................................................... 189
198084241 ...................................................................... 189
198084242 ...................................................................... 190
198084243....................................................................... 190
198084244....................................................................... 192
198084245....................................................................... 192
198084246....................................................................... 193
198084247....................................................................... 194
198084248....................................................................... 194
198084249....................................................................... 195
198084250....................................................................... 195
198084251....................................................................... 196
198084252....................................................................... 196
198084253....................................................................... 197
198084254....................................................................... 197
198084255....................................................................... 198
198084256....................................................................... 199
198084257....................................................................... 200
198084258....................................................................... 200
198084259....................................................................... 200
198084260....................................................................... 200
198084261....................................................................... 200
198084262....................................................................... 201
198084263....................................................................... 201
198084264....................................................................... 201
198084265....................................................................... 201
198084266....................................................................... 202
198084267....................................................................... 203
198084268....................................................................... 203
198084269....................................................................... 204
198084270....................................................................... 204
198084271....................................................................... 204
198084272....................................................................... 205
198084273....................................................................... 206
198084274....................................................................... 206
198084275....................................................................... 206
198084276....................................................................... 207
198084277....................................................................... 207
198084278....................................................................... 208
198084279....................................................................... 208
198084280....................................................................... 209
198084281....................................................................... 209
198084282 ...................................................................... 210

198084283 ...................................................................... 210
198084284 ...................................................................... 211
198084285 ...................................................................... 211
198084286 ...................................................................... 211
198084287 ...................................................................... 212
198084288 ...................................................................... 212
198084289 ...................................................................... 212
198084290 ...................................................................... 213
Appendix A ................................................................... 215

Abbreviations ............................................................... 215
About This Manual

Purpose
This manual provides procedures and guidelines that support the
operation of the NetNumenM31 (V3.10.400) Integrated
Network
Operation
System
Reference
Manual
(Fault
Management) (ZXSDR Node B Alarm Code).
Intended Audience
This manual is intended for engineers and technicians who
perform operation activities on the NetNumenM31 (V3.10.400)
Integrated Network Operation System Reference Manual (Fault
Management) (ZXSDR Node B Alarm Code).
Prerequisite Skill and Knowledge

To use this manual effectively, users should have a general
understanding of wireless telecommunications technology.
Familiarity with the following is helpful:
ZXSDR system and its various components
User interfaces on the Mobile Switching Center (MSC)
Local operating procedures
What Is in This Manual

This manual contains the following chapters:
TABLE 1 CHAPTER SUMMARY
Section
Summary
Chapter 1, Alarm
Management
Introduces the basic concepts and terms of

the alarm code.
Chapter 2, Alarm Code
Introduces the definition, cause and

handling of the alarm code.
Confidential and Proprietary Information of ZTE CORPORATION
ZXSDR BS8900 GU360 Alarm Code Reference
Section
Summary
Appendix A,
Abbreviations
Lists all the abbreviations used in the

manual.
Related Documentation
The following documentation is related to this manual:
ZXSDR BS8900 GU360 (V4.00) Outdoor GSM&UMTS Dual
Mode Macro Node B Documentation Guide

Mode Macro Node B System Description

Mode Macro Node B Hardware Description

Mode Macro Node B Hardware Installation Guide

Mode Macro Node B Configuration Guide

Mode Macro Node B Configuration Parameter Reference

Mode Macro Node B Maintenance Guide
Conventions
Typographical
Conventions
ZTE documents employ the following typographical conventions.

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

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

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

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

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

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

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

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

moving the mouse.
How to Get in Touch

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

regarding
your
product,
contact
us
by
e-mail
at
support@zte.com.cn. You can also call our customer support
center at (86) 755 26771900 and (86) 800-9830-9830.
ZTE welcomes your comments and suggestions on the quality
and usefulness of this document. For further questions,
comments, or suggestions on the documentation, you can
contact us by e-mail at doc@zte.com.cn. Or you can fax your
comments and suggestions to (86) 755 26772236. You can also
browse our website at http://support.zte.com.cn, which contains
various interesting subjects like documentation, knowledge base,
forum and service request.
iii
iv
Declaration of RoHS
Compliance
To minimize the environmental impact and take more
responsibility to the earth we live, this document shall serve as
formal declaration that the ZXSDR BS8900 GU360 (V4.00)
Outdoor GSM&UMTS Dual Mode Macro Node B manufactured by
ZTE CORPORATION are in compliance with the Directive
2002/95/EC of the European Parliament - RoHS (Restriction of
Hazardous Substances) with respect to the following substances:
Lead (Pb)
Mercury (Hg)
Cadmium (Cd)
Hexavalent Chromium (Cr (VI))
PolyBrominated Biphenyls (PBBs)
PolyBrominated Diphenyl Ethers (PBDEs)
vi
Chapter
Alarm Management
Overview
Description
Alarm management is responsible for collecting fault and event

information during system running process. The alarm
information is displayed on a real-time basis on a user-oriented
alarm monitoring platform or stored in database in the form of
alarm and notification. Both past and instantaneous running
state of the system can be traced through visual interface
monitoring or history query. Based on the information provided
by alarm management, operation and maintenance personnel
can perform troubleshooting and take precaution measures to
restore service and system to the normal state in time.
Introduction of Terms
This section introduces several common terms in the alarm
management system.
Alarm Code
Description
Alarm code is a non-exclusive identifier to differentiate alarms.

Alarm code falls into foreground alarm code and background
alarm code. Foreground alarm code refers to a fixed value
defined and allocated by macro in order to differentiate alarms in
program. The same alarm code is used for the generated alarm
and its corresponding recovery. Therefore, only alarm code and
notification code need to be defined. Macro name is specified in
the alarm identifier macro bar by the faulty source based on the
template provided by alarm management. Meanwhile, macro
value is defined by alarm management. Background alarm code
is for display on the alarm monitoring platform. It is mapped in
relation to foreground alarm code according to certain rules.
Severity
Description
There are four recommended alarm levels. Level 1 alarm is the

most severe alarm that affects all services and all NE resources.
Level 2 alarm is a major one that affects most services and
resources. Level 3 alarm is an ordinary one that hinders the
normal operation of some services. Level 4 alarm is a minor one
that affects a certain service or resource. Alarm level is
determined by the faulty source. The four alarm levels are
indicated respectively as Critical, Major, Ordinary, Minor
and Notification in the alarm level bar of the alarm template.
There is no level classification for notification.
Alarm Type
Description
Alarm information (3GPP) is classified into four types shown as

below.
Communication Alarm: related with information transmission
(defined in ITU-T and suggested as X.733)
Handle Error alarm: related with software or process fault
(defined in ITU-T and suggested as X.733)
Environmental Alarm: related with the environment where
equipment is located (defined in ITU-T and suggested as X.733)
Duality of Service Alarm: related with degradation of service
quality (defined in ITU-T and suggested as X.733)
Cause
Description
Possible alarm causes explaining trigger condition and trigger

frequency are enumerated to help operators find ways of
removing the fault and take precaution measures. In this way,
system can be restored to the normal running state as soon as
possible.
Handling
Description
Corresponding measures and advices for fault removal are

provided.
Chapter
Alarm Code
198084000
Description
Severity
Cause
Handling
process
Fail to run FPGA software

Critical
Software version error or board fault
1. Check whether there is software version fault alarm.
i.
Check whether there is related software version fault

alarm.
Y --> Go to ii. Process software version fault alarm
N --> Go to 2 Reset the board.
ii. Process software version fault alarm.

According to relevant suggestions for software version
fault alarm, try to remove the alarm. Check whether the
alarm recovers.
Y --> The alarm handling process completes.
2. Reset the board.
Reset the faulty board, wait for two minutes, and then check
whether the alarm recovers.
N --> Go to 3. Replace the board.
3. Replace the board.
Replace the faulty board, wait for two minutes, and then
check whether the alarm recovers.
N --> Please contact ZTE Corporation.
198084001
Description
Severity
Cause
Handling
process
Fail to run DSP software

Critical
i.

alarm.
N --> Go to 2 Reset the board

alarm recovers.
2. Reset the board.
Y --> Alarm recovers, The alarm handling process completes.
N --> Go to 3. Replace the board
198084002
Description
Severity
Cause
Handling
process
Fail to load NLE table

Major
i.

alarm.
N --> Go to 2 Reset the board
Chapter 2 - Alarm Code

alarm recovers.
N --> Go to 2 Rest the board.
2. Reset the board.
N --> Go to 3 Replace the board.
198084003
Description
Severity
Cause
Handling
process
Clock module fault

Critical
Hardware fault
1. Check type of the faulty board.
Query the type of the faulty board from OMC console.
For the master main control board, Go to 2 Check whether
peripheral board has clock module fault alarm.
For the slave main control board, Go to 3 Check whether
the peer board of master main control board has clock lost
alarm.
For the peripheral board, Go to 4 Check whether master
main control board has clock module fault alarm.
2. Check whether the peripheral board has clock module fault
alarm.
Y --> Go to 5 Reset the faulty board
3. Check whether the peer board of the master main control
board has clock lost alarm.
4. Check whether master main control board has clock module
fault alarm.
i.
Check whether master main control board has clock

module fault alarm.
Y --> Go to ii. Process the fault of clock module on
master main control board
N --> Go to 5 Reset the faulty board.
ii. Process the fault of clock module on master main

control board.
According to suggestions for main control board alarm,
try to remove the alarm. Check whether the current
alarm recovers.
5. Reset the faulty board.
Note:
Reset or Unplug-and-plug board will cause interruption of all
services carried by the board. Therefore, please choose
appropriate time to operate it.
i.
Reset the faulty board through OMC console, wait for two
minutes until the board runs normally, and then check
N --> Go to 6 Replace the faulty board.
ii. Unplug-and-plug the faulty board, wait for two minutes

until the board runs normally, and then check whether
the alarm recovers.
6. Replace the faulty board.
Note:
Replacing the board will cause interruption of all services carried
by the board. Therefore, please choose appropriate time to
replace it.
Replace the faulty board, wait for two minutes until the
board runs normally, and then check whether the alarm
recovers.
198084004
Description
Severity
Cause
Clock reference source is lost

Minor
1. The configured clock reference source doesn't exist.
2. External reference clock has a fault.
3. Board fault
4. Cable fault
Handling
process
1. Check whether wrong reference source is configured.

i.
Check whether wrong reference source is configured (e.g.

Link clock 1 reference is configured, but the system
doesn't have link clock 1 in reality).
Y --> Go to ii. Change the configuration of clock
reference source.
N --> Go to 2.
ii. Change the configuration of clock reference source.

Change the configuration of clock reference source from
OMC console so that it is consistent with real situation.
Check whether the alarm recovers.
N --> Go to 2 Check whether external reference clock is
normal.
2. Check whether external reference clock is normal.
Determine the type of clock reference source
f
For link clock reference source, Go to 3.
For GPS clock reference source, Go to 4
For BITS clock reference source, Go to 5.
3. Check whether link clock reference source is normal.

i.
Check whether master/slave main control boards are

configured in the system.
Check whether the system has configured master/slave
main control boards, and then check whether both boards
work normally
Y --> Go to ii. Check whether another main control
board has the same alarm.
N --> Go to 3 Check whether Iub interface board has
physical link fault.
ii. Check whether another main control board has the same
alarm.
Y --> Go to 3 Check whether Iub interface board has
physical link alarm.
N --> Go to 6 Reset fault main control board.
iii. Check whether Iub interface board has physical link
alarm.
Solve the Iub physical link alarm, and then check
whether the current alarm about clock reference source
recovers.
N --> Go to 6 Reset fault main control board.
4. Check whether GPS clock reference source is normal.
i.
Check whether the cable is connected normally.

Check the GPS card on EMU, and the cable from EMU to
front panel of CCS, and then check whether GPS card and
the cable are good, the cable is well connected.
Y --> Go to iii. Replace GPS card.
N --> Re-connect the cable and Go to ii. Check whether
the alarm recovers.
ii. Check whether the alarm recovers.

N --> Go to iii. Replace GPS card.
iii. Replace GPS card.
Replace GPS card, and then check whether the alarm
recovers.
N --> Go to 7.
5. Check whether BITS clock reference source is normal.
i.
Check whether EMC has an alarm, which indicates EMU

external clock is lost.
Y --> Go to ii. Process the alarm that indicates EMU
external clock is lost
N --> Go to 7 Process the fault of main control board.
ii. Process the alarm that indicates EMU external clock is

lost.
According to relevant suggestions for EMU external clock
lost alarm, try to remove the alarm. Check whether the
current Recovered.
N --> Go to 7 Process the fault of main control board..
6. Process the fault of Iub interface board.
Note:
Replacing or resetting the Iub interface board will cause
interruption of all services carried by it. Therefore, please choose
appropriate time to replace or reset it.
i.
Reset Iub interface board.

Reset the Iub interface board, which provides link clock
reference source, wait for two minutes until the board
runs normally, and then check whether the Recovered.
N --> Go to ii. Replace Iub interface board.
ii. Replace Iub interface board.

Replace the Iub interface board, which provides link clock
reference source, wait for two minutes until the board
runs normally, and then check whether the Recovered.
N --> Go to 7.
7. Process the fault of main control board.
Note:
Replacing or resetting main control board will cause interruption
of all services carried by it. Therefore, please choose appropriate
time to replace or reset it.
i.
Reset fault main control board.

Wait for three minutes until the board runs normally, and
then check whether the Recovered.
N --> Go to ii. Replace fault main control board.
ii. Replace fault main control board.

Replace the fault main control board, wait for three
minutes until the board runs normally, and then check
whether the Recovered.
198084005
Description
Severity
Cause
EMU external clock is lost

Minor
1. The configured clock reference source doesn't exist.
2. External reference clock has a fault.
3. Board fault"
Handling
process

Reset the fault EMC, wait for two minutes until the board
runs normally, and then check whether the alarm recovers.
N --> Go to 2 Replace the faulty board
Replace the faulty board, wait for two minutes until the
board runs normally, and then check whether the alarm
recovers.
198084006
Description
Severity
Cause
Clock reference source is degraded

Minor
1. Poor quality of transmission clock
2. Board fault
3. Cable fault"
Handling
process
1. Replace transmission clock reference source.

i.
Check whether there is other available reference clock.

Y --> Switch to other transmission clock and Go to ii.
N --> Go to 2 Check clock reference source

N --> Go to 2 Check clock reference source.
2. Check clock reference source.
f
10
For Link clock reference source, Go to 3 Check whether

transmission link is normal
For GPS clock, Go to 4. Check whether GPS device is

normal
For BITS clock, Go to 5. Check whether synchronization
network clock is normal
3. Check whether transmission link is normal.

i.
Check whether transmission link is normal.

Y --> Go to 6 Check whether main control board is
normal
N --> Solve the problem of transmission link and Go to ii.

N --> Go to 6 Check whether main control board is
normal.
4. Check whether GPS device is normal.
i.
Check whether GPS antenna feeder and GPS card are

normal.
normal.
N --> Re-install GPS card and antenna feeder, and Go to

N --> Go to 6 Check whether main control board is
normal.
5. Check whether synchronization network clock is normal.
i.
Check whether synchronization network clock is normal.

normal.
N --> Please solve the abnormity of synchronization
network clock.
6. Check whether main control board is normal.

i.
If the system has configured master/slave main control

board, and then check another board which is related to
the faulty board, and then check whether it has
reference source degradation alarm.
Y --> Yes, Please contact ZTE Corporation.
N --> Go to ii. Replace the faulty board.
ii. Replace the faulty board.
11
Note:
Replacing main control board will cause interruption of all
appropriate time to replace it.
Replace the fault main control board, wait until the board
runs normally, and then check whether the alarm
recovers.
198084007
Description
Severity
Cause
Handling
process
Transmission clock is lost

Minor
Hardware fault
1. Check type of alarm board.
For the main control board, Go to 3 Reset the faulty board

For the Iub interface board, Go to 2 Check whether main
control board has transmission clock lost alarm.
2. Check whether main control board has transmission clock

lost alarm.
i.
Check whether main control board has transmission clock

lost alarm, which is related to the faulty board.
Y --> Go to ii. Process transmission clock alarm on main
control board.
N --> Go to 4 Reset the faulty board
ii. Process transmission clock alarm on main control board.

According to relevant suggestion for transmission clock
lost alarm, try to remove the alarm. Check whether there
still is transmission clock lost alarm.
Note:
Resetting the main control board will cause interruption of all
appropriate time to reset it.
12
Reset the faulty board, wait until the board runs normally,
and then check whether the alarm recovers.
N --> Go to 5 Unplug-and-plug the faulty board.
4. Unplug-and-plug the faulty board.
Note:
Unplugding-and-plugging the main control board will cause
interruption of all services carried by the board. Therefore,
please choose appropriate time to operate it.
Unplug and plug the faulty board, wait until the board
runs normally, and then check whether the alarm
recovers.
Note:
Replacing the main control board will cause interruption of all
Replace the faulty board, wait until the board runs

normally, and then check whether the alarm recovers.
198084008
Description
Severity
Cause
Handling
process
Transmission clock is unlocked.

Minor
Hardware fault
1. Check whether main control board has clock reference source
being degraded alarm.
i.
Through OMC console, check whether there is clock

reference source degradation alarm.
13
Y --> Go to ii.
degradation alarm.
Process
clock
reference
source

ii. Process clock reference source degradation alarm.
According to relevant suggestions for clock reference
source degradation alarm, try to remove the alarm.
Check whether the unlocked transmission clock alarm
recovers.
Note:
Resetting main control board will cause interruption of all
N --> Go to 3 Unplug-and-plug the faulty board
Note:
Unplugging-and-plugging the faulty board will cause interruption
of all services carried by the board. Therefore, please choose
Unplug and plug the faulty board, wait until the board runs
Note:
14
Replace the faulty board, wait until the board runs normally,
198084009
Description
Severity
Cause
The peer board clock is lost

Minor
1. Peer board clock is lost.
2. Backplane connection is not good.
3. Local board hardware has s fault.
Handling
process
1. Check whether the peer board has clock lost alarm.

i.
Through OMC console, check whether the peer board of

the faulty board has corresponding clock lost alarm.
Y --> Go to ii. Process clock lost alarm on the peer
board.
ii. Process clock lost alarm on the peer board.

According to relevant suggestions for clock module fault
alarm, try to remove the alarm. Check whether the
current board alarm recovers.
Note:
15
Note:
Unplug-and-plug the main control board will cause interruption
Unplug and plug the faulty board, wait until the board runs
Note:
198084010
Description
Severity
Cause
Downlink service link fault

Major
1. LVDS fault
2. At transmitting and receiving ends of LVDS link, there is
board fault.
Handling
process
1. Check the configuration of the peer board.

i.
View the configuration of fault LVDS connected board,

and then check whether the configuration is consistent
with real one inserted in Node B rack.
Y --> Go to 2 Check whether the peer board is normal.
N --> Change board configuration so that it is matched
with real one in Node B rack. Go to ii. Check whether the
alarm recovers.

16
N --> Go to 2 Check whether the peer board is normal.

2. Check whether the peer board is normal.
i.
Check whether the peer board runs normally.

Y --> Go to 3 Unplug-and-plug the peer board.
N --> Go to ii. Process the abnormity of the peer board.
ii. Process the abnormity of the peer board

Solve the abnormity of the peer board so that it can run
normally. Check whether the current alarm recovers.
N --> Go to 3 Unplug-and-plug the peer board.
3. Unplug-and-plug the peer board.
Note:
Unplugging-and-plugging the board will cause interruption of all
services carried on the board. Therefore, please choose
Unplug and plug the peer board again, wait until the board
Note:
Unplug and plug the faulty board again, wait until the board
Note:
17

on the board. Therefore, please choose appropriate time to
replace it.
N --> Go to 6 Replace the peer board
6. Replace the peer board.
Note:
on the board. Therefore, please choose appropriate to replace it.
Replace the peer board, wait until the board runs normally,
198084011
Description
Severity
Cause
Uplink service link fault

Major
1. LVDS fault
2. At transmitting and receiving ends of LVDS link, there is
board fault."
Handling
process
1. Check the configuration of the peer board.

i.
View the configuration of fault LVDS connected board,

and then check whether the configuration is consistent
with real one inserted in Node B rack.
Y --> Go to 2 Check whether the peer board is normal.
N --> Inconsistent, change board configuration so that it
is matched with real one in Node B rack. Go to ii. Check

N --> Go to 2 Check whether the peer board is normal.
2. Check whether the peer board is normal.
i.
18
Check whether the peer board runs normally.
Y --> Go to 3 Unplug-and-plug the peer board.

N --> Go to ii. Process the abnormity of the peer board
ii. Process the abnormity of the peer board.
Solve the abnormity of the peer board so that it can run
normally. Check whether the current alarm recovers.
N --> Go to 2 Unplug-and-plug the peer board
3. Unplug-and-plug the peer board.
Note:
Unplug and plug the peer board again, wait until the board
Note:
Unplug and plug the faulty board again, wait until the board
Note:
on the board. Therefore, please choose appropriate time to
replace it.
19
N --> Go to 6 Replace the peer board
6. Replace the peer board.
Note:
on the board. Therefore, please choose appropriate to replace it.
Replace the peer board, wait until the board runs normally,
198084012
Description
Severity
Cause
Board hardware fault

Critical
Board hardware initialization is failed.
Hardware components on the board have a fault.
Handling
process

198084013
Description
Severity
20
Ir optical port has LOS alarm

Critical
Cause
FS optical module is broken, optical fiber is not connected, or

corresponding RRU optical module is broken.
Handling
process
Check if the optical fiber is connected normally. If the answer is

no, connect it correctly; otherwise, replace FS board.
198084014
Description
Severity
Cause
GPS clock reference source is useless

Minor
1. Initializing
2. Antenna open circuit
3. Antenna overcurrent
4. The number of autotraced satellites is less than 4
5. GPS card is not-in-position
6. Not in 3D status
7. TRAIM alarm"
Handling
process
1. Initializing
2. Antenna open circuit
3. Antenna overcurrent
4. The number of autotraced satellites is less than 4
5. GPS card is not-in-position
6. Not in 3D status, please wait
7. TRAIM alarm"
198084015
Description
Severity
Cause
Handling
process
STM-1 optical signals are lost.

Major
Antenna open circuit
1. Check whether fiber connection is abnormal.
i.
Check whether receiving and transmitting fibers are

reversely connected.
Y --> Re-connect fibers according to correct receiving
and transmitting direction, then Go to ii. Check whether
the alarm recovers.
N --> Go to 2 Check and clear fiber abnormity.

21

2. Check and clear fiber abnormity. Check and clear fiber
abnormity. Check whether the alarm recovers.
N --> Go to 3 Check whether local optical interface
module is abnormal.
3. Check whether local optical interface module is abnormal.
i.
Check whether local optical interface module is abnormal.
Note:
Setting the faulty optical interface to work in loop back mode
cannot remove this alarm.
Y --> Go to ii. Handle the fault on the local optical

interface board.
N --> Go to 5 Check whether the peer fiber link is
abnormal
ii. Handle the fault on the local optical interface board.
Handle the fault on the local optical interface board.
N --> Go to 4 Replace optical interface board
4. Replace optical interface board.
Note:
Replacing optical interface board will cause interruption of all
Replace optical interface board and wait for two minutes.

When the board runs normally, check whether the alarm
recovers.
abnormal
5. Check whether the peer fiber link is abnormal.
Check whether the peer fiber link is abnormal.
f
22
For the remote device fault, please remove the fault of

the peer device. The alarm handling process completes.
For the optical fiber fault, please ask your customer for
help to solve the optical transmission problem. The alarm
handling process completes.
198084016
Description
Severity
Cause
Handling
process
STM-1 loses frame synchronization

Major
Antenna overcurrent
1. Check whether local optical interface board has LOS alarm.
i.
Check whether the corresponding optical interface board

has LOS alarm.
Y --> Go to ii. Process LOS alarm.
N --> Go to 2 Check whether the optical interface board
has clock alarm.
ii. Process LOS alarm.

According to suggestions for LOS alarm, try to remove
this alarm. Check whether current alarm recovers
has clock alarm.
2. Check whether the optical interface board has clock alarm.
i.
Check whether the corresponding optical interface board

has transmission clock alarm.
Y --> Go to ii. Process transmission clock alarm occurred
on optical interface board
module is abnormal
ii. Process transmission clock alarm occurred on optical

interface board.
According to suggestions for transmission clock alarm on
optical interface board, try to remove this alarm. Check
whether current alarm recovers.
Y --> Alarm recovers, The alarm handling process
completes.
module is abnormal
i.

Y --> The local optical interface module is Go to ii.
Handle the fault on the local interface board.
23
N --> The local optical interface module is Go to 4 Check

whether RNC or transport device clock status is normal.
ii. Process the abnormity of local optical interface board.
N --> Go to iii. Replace optical interface board.
iii. Replace optical interface board.
Note:
Replace optical interface board. Wait until the board has

finished booting. Check whether the alarm recovers.
4. Check whether RNC or transport device clock status is
normal.
Try to remove RNC or transport device clock fault, and Check
abnormal."
f

198084017
Description
Severity
Cause
Handling
process
24
STM-1 MSAIS (MS Alarm Indicator Signal)

Major
The number of autotraced satellites is less than 4.
1. Check whether fiber connection is abnormal.
i.
Check whether receiving and transmitting fibers are

Y --> Re-connect fibers according to correct receiving

and transmitting direction, and Go to ii. Check is the
alarm recovers.
2. Check and clear fiber abnormity.
Check and clear the abnormity of optical fiber. Check
N --> Go to 3 Check whether local optical interface module
is abnormal.
i.

Y --> Go to ii. Handle the fault on the local optical
interface board.
abnormal.

N --> Go to 4 Replace optical interface board.
Note:

f

help to solve the optical transmission problem. Alarm
process ends.
25
198084018
Description
Severity
Cause
Handling
process
STM-1 AU4 loss of pointer

Major
GPS card is not-in-position
1. Check whether local optical interface board has relevant
alarm.
i.
Check whether the related optical interface board has

LOS or LOF alarm.
Y --> Go to ii. Process relevant alarm
N --> Go to 2 Check whether optical interface board has
clock alarm
ii. Process relevant alarm.

Check whether local optical interface board has relevant
alarm
i.

LOS or LOF alarm.
Y --> Go to ii. Process relevant alarm
clock alarm
ii. Process relevant alarm.

According to relevant suggestions for these alarms, try to
remove these alarms. Check whether current alarm
recovers.
has clock alarm.
2. Check whether the optical interface board has clock alarm.
i.

transmission clock alarm.
Y --> Go to ii. Process transmission clock alarm occurred
on optical interface board
module is abnormal
ii. Process transmission clock alarm occurred on optical

interface board.
According to suggestions for transmission clock alarm on
optical interface board, try to remove this alarm. Check
whether current alarm recovers.
26

module is abnormal.
i.

Y --> The local optical interface module is Go to ii.
Handle the fault on the local interface board.
N --> The local optical interface module is Go to 5 Check

N --> Go to 4 Replace optical interface board.
Note:

normal.
Try to remove RNC or transport device clock fault, and Check
abnormal.
f

27
198084019
Description
Severity
Cause
Handling
process
E1/T1 LOS (Loss Of Signal) alarm

Major
Hardware fault or link fault
1. Check if E1/T1 link connection is abnormal.
i.
Check if E1/T1 connection is abnormal.

Y->Abnormal connection, skip to "ii. Reconnect E1/T1
link"
N->Normal connection, skip to "2 Check if the local E1/T1
device has a fault".
ii. Re-connect E1/T1 link.

Check if the alarm is recovered.
Y->Alarm is recovered, end alarm process.
N->Alarm is not recovered,skip to "2.Check if the local
E1/T1 device has a default".
2. Check if the local E1/T1 device has a default.
i.
check if the local E1/T1 device has a default

Y->The local E1/T1 device has a default,skip to "2)
Process the default of local interface board".
N->The local E1/T1 device is normal,skip to "3 Check if
the peer-end E1/T1 trunk is abnormal".
ii. Process the fault of local interface board.

Process the abnormity of local E1/T1 interface board
3. Check if the peer-end E1/T1 trunk is abnormal.
Check if the peer-end E1/T1 trunk is abnormal
Transport trunk has no fault Please remove the fault of
peer-end device. Alarm process ends.
TRansport trunk has a fault. Please ask customer's
transport maintenance engineer to check trunk and solve
th problem.Alarm process ends.
198084020
Description
Severity
Cause
28
E1/T1 link loss of frame alarm

Major
Handling
process
1. Check if the local interface board has E1/T1 LOS alarm.

i.
Check if the corresponding interface board has E1 LOS

alarm.
Y->Yes, skip to "ii. Process E1/T1 LOS alarm"
N->No, skip to "2 Check if optical interface board has
clock alarm"
ii. Process E1/T1 LOS alarm.

According to the relevant suggestions for E1 LOS alarm,
try to remove the alarm. Check if current alarm is
recovered.
N->Alarm is not recovered, skip to "2 Check if optical
interface board has clock alarm".
2. Check if optical interface board has clock alarm.
i.
From O&M console, check if the corresponding interface

board has 2M transport clock alarm.
Y->Yes, skip to "ii. Process 2M transport clock alarm on
the interface board"
N->No, skip to "3 Check if E1/T1 setting is correct".
ii. Process 2M transport clock alarm on the interface board.

According to the relevant suggestions for 2M transport
clock alarm on interface board, try to remove the alarm.
N->Alarm is not recovered, skip to "3 Check if E1/T1
setting is correct".
3. Check if E1/T1 setting is correct.
Check E1/T1 setting, Check if the alarm is recovered.
N->Alarm is not recovered, skip to "4 Check if the
corresponding E1/T1 connection is abnormal".
4. Check if corresponding E1/T1 connection is abnormal.
i.
Check if E1/T1 connection is abnormal.

Y->Connection is abnormal, skip to "ii. Re-connect E1/T1
link"
N->Connection is normal, skip to "5 Check if local E1/T1
ii. Re-connect E1/T1 link and check if the alarm is recovered.

N->Alarm is not recovered, skip to "5 Check if local E1/T1
29
5. Check if local E1/T1 device has a fault.

i.
Check if local E1/T1 device has a fault

Y->Local E1/T1 device has a fault, skip to "ii Process the
fault of local interface board".
N->Local E1/T1 device is normal, skip to "6 Check if the
peer-end E1/T1 trunk is abnormal".

Process the fault of local interface board
6. Check if the peer-end E1/T1 trunk is abnormal.
Check if the peer-end E1/T1 trunk is abnormal.
Transport trunk has no fault, Please remove the fault of
peer-end device. Alarm process ends.
Transport trunk has a fault, Please ask customer's
the problem.Alarm process ends.
198084021
Description
Severity
Cause
E1/T1 loss of cell delineation alarm

Major
1. E1/T1 setting is incorrect.
2. E1/T1 transport link connection is abnormal.
3. E1/T1 transport trunk has a problem.
4. The peer device is abnormal."
Handling
process
1. Check whether local interface board has E1/T1 link relevant

alarm.
i.
Check whether corresponding interface board has LOS or

LOF alarm, or other E1/T1 link relevant alarm.
Y --> Go to ii. Process E1/T1 link relevant alarm
board has clock alarm.
ii. Process E1/T1 link relevant alarm.

According to relevant suggestions, try to remove the
alarm. Check whether the current alarm recovers.
board has clock alarm
2. Check whether local optical interface board has clock alarm.
i.
30
Check whether the corresponding interface board has 2M

transport clock alarm.
Y --> Go to ii. Process 2M transport clock alarm on the

interface board
N --> Go to 3 Check whether E1/T1 setting is correct.
According to the relevant suggestions of 2M transport
3. Check whether E1/T1 setting is correct.
i. 8 Check E1/T1 setting,.Check whether the alarm recovers.
N --> Go to 4 Check whether the corresponding E1/T1
connection is abnormal.
4. Check whether corresponding E1/T1 connection is abnormal.
Y --> Connection is Go to ii. Re-connect E1/T1 link.
N --> Connection is Go to 5 Check whether local E1/T1
device has a fault.
N --> Go to 5 Check whether local E1/T1 device has a
fault.
5. Check whether local E1/T1 device has a fault.
i.
Check whether local E1/T1 device has a fault.

Y --> Local E1/T1 device has a fault, Go to ii.
the fault of local interface board.
Process
N --> Local E1/T1 device is Go to 6 Check whether the

peer E1/T1 trunk is abnormal.
Process the abnormity of local E1/T1 interface board.
6. Check whether the peer E1/T1 trunk is abnormal.
Check whether the peer E1/T1 trunk is abnormal.
f
For the transport trunk has no fault, please remove the

fault of the peer device. Alarm process ends.
For the transport trunk has a fault, please ask customer's
the problem. The alarm handling process completes.
31
198084022
Description
Severity
Cause
E1/T1 link loss of IMA frame alarm

Major
1. E1/T1 fault
2. IMA link belonged group setting has a problem.
3. Local IMA is fault.
4. The peer IMA fault
5. Clock is not synchronous."
Handling
process
1. Check whether local interface board has E1/T1 relevant

alarm.
i.
Check whether the corresponding interface board has

E1/T1 relevant alarm, such as LOS or LOF.
Y --> Go to ii. Process E1/T1 relevant alarm
N --> Go to 2 Check whether local interface board has
clock alarm
ii. Process E1/T1 relevant alarm.

According to the relevant suggestions for E1 LOS alarm,
try to remove the alarm. Check whether the current
alarm recovers.
clock alarm.
2. Check whether local interface board has clock alarm.
i.

Y --> Go to ii. Process 2M transport clock alarm on the
interface board.
N --> Go to 3 Check IMA setting.

N --> Go to 3 Check IMA setting.
3. Check IMA setting.
Check IMA setting and check whether the alarm recovers.
32
4. Check whether
abnormal.
i.
the
corresponding
E1/T1 connection
is
Check whether E1/T1 connection is abnormal.

N --> Connection is Go to 5 Check whether local IMA
group has a fault.
ii. Re-connect E1/T1 link and Check whether the alarm

recovers.
N --> Go to 5 Check whether local IMA group has a
fault.
5. Check whether local IMA group has a fault.
i.
Check whether local IMA group has a fault.

Check whether local IMA link has a fault.
Y --> Go to ii. Process the fault of local interface board.
N --> Go to 6 Check the fault of E1/T1 trunk or remote
IMA group.
ii. Process the fault of local interface board

6. Check the fault of E1/T1 trunk or remote IMA group.
f

fault of the peer device. The alarm handling process
completes.
198084023
Description
Severity
Cause
E1/T1 IMA group is not operational

Major
1. E1/T1 fault.
2. IMA link belonged group setting has a problem.
3. Local IMA fault.
4. The peer IMA fault.
Handling
process
1. Check whether local interface board has E1/T1 relevant

alarm.
i.
Check whether the corresponding interface board has

E1/T1 relevant alarm, such as LOS or LOF.
33
Y --> Go to ii. Process E1/T1 relevant alarm.

clock alarm.
ii. Process E1/T1 relevant alarm.
According to the relevant suggestions, try to remove the
alarm. Check whether the current alarm recovers.
clock alarm.
2. Check whether local interface board has clock alarm.
i.

Y --> Go to ii.
Process 2M transport clock alarm on
the interface board.

3. Check whether E1/T1 setting is correct.
i.
8 Check E1/T1 setting,. Check whether the alarm

recovers.
4. Check whether corresponding E1/T1 connection is abnormal.

i. Check whether corresponding E1/T1 connection is
abnormal.
N --> Connection is Go to 5 Check whether local E1/T1
device has a fault.
N --> Alarm is not recovered, sip to 5 Check whether
local E1/T1 device has a fault.
i.
34
Y --> Local E1/T1 device has a fault, Go to ii.

the fault on local interface board.
Process
N --> Local E1/T1 device is Go to 6 Check whether the

peer E1/T1 trunk is abnormal.
ii. Process the fault on local interface board.
Process the fault on local E1/T1 interface board.
For the transport trunk has no fault, please remove the fault
of the peer device. The alarm handling process completes.
transport maintenance engineer to check trunk and solve the
problem. Alarm process ends.
198084024
Description
Severity
Cause
E1/T1 remote receiving fault

Major
3. The peer device is abnormal.
4. Local device has a fault.
Handling
process
1. Check whether
abnormal.
the
corresponding
E1/T1connection
is
Check whether E1/T1 connection is abnormal.

N --> Go to 2 Check whether local E1/T1 device has a fault.
i.

Y --> Go to ii. Process the fault of local interface board.
N --> Go to 3 Check whether the peer E1/T1 trunk is
abnormal.

35

completes.
For the transport trunk has fault, please ask customer's
198084025
Description
Severity
Cause
Handling
process
E1/T1 link self-loop

Minor
Customer has set E1 link to be looped back locally or remotely.
1. Cancel loop-back setting of E1 link locally or remotely.
i.
Check whether E1 link is in self-loop state.

Y --> Cancel the self-loop setting and Go to ii. Check

198084026
Description
Severity
Cause
Handling
process
PVC fault
Major
Fail to receive response, and this case occurred 3 times
1. Check whether PVC parameter is correctly configured.
i.
Through OMC console, check whether PVC parameter is

correctly configured.
Y --> Configuration is Go to 2 Check whether PVC
related IUB port has an alarm.
N --> Configuration is wrong, Go to ii. Change PVC link
parameter
ii. Change PVC link parameter, and check whether the alarm
recovers.
N --> Go to 2 Check whether PVC related IUB port has
an alarm.
2. Check whether PVC related IUB port has an alarm.
36
Solve the problem of IUB port (STM1, IMA, TC) alarm, which
affects PVC link. Check whether the alarm recovers.
N --> Go to 3 Check whether remote device supports OAM
F5 loop-back test function
3. Check whether remote device supports OAM F5 loop-back
test function.
Y --> Go to 4 Self-loop test.
N --> Cancel this function from local OMC terminal and the
alarm handling process completes.
4. Self-loop test.
Use self-loop test function and check whether local alarm
recovers.
Y --> Go to 6 Check whether the fault is about the
connection to remote device
N --> Go to 5 Process the fault on local interface board.
5. Process the fault on local interface board.
Process the fault on local E1/T1 interface board.
6. Check whether the fault is about the connection to remote
device.
Check whether the E1/T1 trunk, connecting to remote device,
is abnormal.
f

completes.
198084027
Description
Severity
Cause
FE network port connection is broken

Major
1. Network cable fault.
2. Remote network port fault.
3. Local network port fault.
Handling
process
1. Check whether network cable is connected normally.

Please check whether the network cable has the following
problems.
i.
Network cable is not tightly connected.
ii. Network cable is bad.
37
Please solve the above problem if there is any. After that,

please check whether the alarm recovers.
N --> Go to 2 Check whether local network port is
abnormal".
2. Check whether local network port is abnormal.
i.
Check whether local network port is abnormal.

Use a good network cable to directly connect the alarm
network port and another network port. Check whether
the alarm recovers.
Y Go to ii. Process the fault of local interface board.
N Go to 3 Process the fault of remote network port.
Note:
Resetting or replacing the interface board will cause interruption
appropriate time to reset or replace it.
Reset the fault interface board. After successful booting,

please check whether the alarm recovers.
Y The alarm handling process completes
N Please contact ZTE Corporation.
iii. Replace fault interface board.
Replace the interface board. Wait until the board has
finished booting and RUN light flashes normally (in 1Hz
frequency). Query the alarm status of the corresponding
board and Check whether the original alarm still exists.
Y --> Please contact ZTE Corporation.
N --> The alarm handling process completes.
3. Process the fault of remote network port.
Please try to remove the fault of remote device. The alarm
198084028
Description
Severity
Cause
38
SSCOP signaling link is broken

Major
1. Physical link, which carries PVC link, has a fault.
2. The configuration of PVC parameters is wrong.

3. Board is abnormal."
Handling
process
1. Check whether there is Iub (STM1, IMA, TC) interface alarm,

which affects PVC link.
i.
Solve the Iub (STM1, IMA, TC) alarm, which affects PVC
link.

N --> Go to 2 Check whether the configuration of PVC
parameter is correct.
2. Check whether the configuration of PVC parameters is
correct.
i.
From OMC console, check the configuration of PVC link

parameters.
ii. Check Port ID, bandwidth of VPI, VCI and PVC, ATM
address, and then check whether the configuration is
consistent with the peer.
Y --> Configuration is Go to 4 Link self-test.
N --> Configuration is Go to 3 Reconfigure PVC link.
3. Reconfigure PVC link.
i.
Delete the fault PVC link from PVE link configuration

screen.
ii. Add PVC link from PVC link configuration screen, where
attribute should be kept same as the peer. After setting,
N --> Go to 4 Link self-loop test.
4. Link self-loop test.
Conduct link self-test, and then check whether the alarm
recovers.
Y The remote transmission device has a fault. Please
remove it. The alarm handling process completes.
N Go to 5 Reset alarm board.
5. Reset alarm board.
Wait for two minutes until the board runs normally, and then
Y The alarm handling process completes.
39
198084029
Description
Severity
Cause
SSCOP transmission buffer is overflow.

Major
1. Node B clock fault.
2. Poor transmission quality.
3. The PVC belonged board has a fault.
4. The configured link bandwidth is very small."
Handling
process
1. Check whether there is Iub (STM1, IMA, TC) interface alarm,

which affects PVC link.
i.
Solve the Iub (STM1, IMA, TC) interface alarm, which

affects PVC link.

N --> Go to 2 Check whether there is clock alarm, which
affects Iub interface.
2. Check whether there is clock alarm, which affects Iub
interface.
i.
Solve the clock alarm, which affects Iub interface.

N --> Go to 3 Check whether bandwidth meets
transmission requirement
3. Check whether bandwidth meets transmission requirement.
i.
View PVC link bandwidth from OMC console.

Y --> Bandwidth meets requirement, Go to 4 Reset the
faulty board.
N --> Bandwidth doesn't meet requirement, Go to ii.
Change the configuration of PVC link bandwidth.
ii. Change the configuration of PVC link bandwidth, and then

Reset the faulty board, wait for two minutes until the board
N --> Go to 5 Check and improve quality of transmission
link.
40
5. Check and improve quality of transmission link.

Ask
transmission
maintenance
engineers
to
check
transmission link and try to solve the problem. If
transmission becomes normal, but the alarm still exists,
Please contact ZTE Corporation.
198084030
Description
Severity
Cause
SCTP association is interrupted.

Major
1. Local FE configuration error.
2. Association parameter is wrongly configured locally
remotely.
or
3. Bottom layer cannot communicate with its peer end.

4. Board fault.
Handling
process
1. Check whether there is FE port related alarm.

i.
Check whether there is FE port related alarm.

Y --> Go to ii. Process FE port related alarm.
N --> Go to 2 Check whether
parameter is correctly configured.
SCTP
association
ii. Process FE port related alarm.

According to relevant suggestions for FE port related
current alarm recovers.
N --> Go to 2. Check whether SCTP association
parameter is correctly configured.
2. Check whether SCTP association parameter is correctly
configured.
i.
From OMC console, view the configuration of SCTP

association parameter.
ii. Check whether remote address and remote port ID of

SCTP association are consistent with local address and
local port ID, if FE port selection is consistent with local
configuration.
Y Go to iii. Wait for alarm recovery.
N Go to 3 Reconfigure SCTP association.
iii. Wait for alarm recovery.
Wait for a period of time and Check whether the alarm
recovers.
41

3. Reconfigure SCTP association.
i.
Delete the fault association

configuration screen.
from
SCTP
association
ii. Add SCTP association from SCTP association configuration

screen, where attribute should be kept the same as the
peer. After setting, check whether the alarm recovers.
198084031
Description
Severity
Cause
Handling
process
SCTP association stream buffer is congested.

Major
Application layer frequently sends data to one SCTP association
stream.
1. Wait until system auto-recovery.
Wait for fifteen minutes, and then check whether the alarm
recovers.
198084032
Description
Severity
Cause
SCTP association network is congested.

Major
1. The peer cannot timely give any response due to very high
load.
2. Physical link connection has a fault.
Handling
process
1. Wait for system auto-recovery.

recovers.
198084033
Description
42
RNC IP is unavailable
Severity
Cause
Warning
2. The configuration of local FE parameters is wrong.
4. Local network fault.
Handling
process
1. Check whether network cable is abnormal.

Please check whether network cable has the following
problem.
i.

Please solve the above problem if there is any.
2. Check whether FE parameters of local network port are
Check FE parameters such as NODE B IP address, gateway
IP, subnet mask. Make sure the parameters are correctly
configured.
3. If router or network gateway is connected, please check the
corresponding configuration.
198084034
Description
Severity
Cause
Handling
process
PPP Link Broken

Major
Iub link fault
1. If PPP Link is configed on E1/STM1/FE link,Check Check
whether there is a E1/STM1/FE alarm
Y --> Go to 2. Deal E1/STM1/FE link alarm
N --> Go to 3. Reset the faulty board
2. Deal E1/STM1/FE link alarm
Deal this alarm first. Check whether the alarm recovers.
N --> Go to 3.Reset the faulty board.
3. Reset the faulty board
43
Replace the faulty board, wait for two minutes, and check
198084035
Description
Severity
Cause
Handling
process
PPP LinkUnusable
Major
Iub link fault
1. If PPP Link is configured on PPPoE/HDLC, check whether
there is a FE/HDLC alarm
Y --> Go to 2.Deal FE/HDLC link alarm
N --> Go to 3.Reset the faulty board
2. Process FE/HDLC link alarm
Process this alarm first. Check whether the alarm recovers.
N --> Go to 3.Reset the faulty board.
3. Reset the faulty board
Reset the faulty board, wait for two minutes, and check
N --> Go to 4.Replace the faulty board
198084036
Description
Severity
Cause
Handling
process
SCTP stream number mismatch

Major
SCTP stream number mismatch
1. Check up RNC maximum of link is the same as Node B
configuration
2. Delete this SCTP association and reconfigure it. Check
44

198084037
Description
Severity
Cause
TMB downlink bypass alarm

Minor
1. Primary channel over-power alarm: when the maximum
output power exceeds 47.3dBm +- 0.5dB.
2. Primary channel over-VSWR alarm: when VSWR exceeds 1.8,
only alarm, auto-protection shut-down function is not
required. When VSWR exceeds 2.8 and output power is
greater than 35dBm, alarm and auto-protection shut-down
function is required.
3. Primary channel over-temperature alarm: when its internal
maximum working temperature exceeds 95.C +- 5.C.
4. Primary channel DC over-current alarm: when the DC current
exceeds 150%.
5. Primary channel device fault alarm: e.g. working voltage is
out of -40VDC~-57VDC range, PA is broken.
6. TMB gate alarm: when TMB gate is opened, alarm shown at
PAU panel. The alarm may be viewed through RS485.
7. PAU and TMB communication abnormal alarm: PAU
communicates with TMB through RS485. This type of alarm
includes: software download is abnormal, RF channel
between PAU and TMB is not connected, etc. The alarm may
be viewed through RS485.
Handling
process
1. TMB is powered down and powered on.

Power down and power on TMB, and then check whether the
alarm recovers.
198084038
Description
Severity
Cause
Handling
process
TMB uplink bypass alarm

Minor
Receiving channel LNA is abnormal.
1. TMB is powered down and powered on.
Power down and power on TMB, and then check whether the
alarm recovers.
45

198084039
Description
Severity
Cause
TMA channel current input is interrupted.

Major
1. The TMA related power cable is not well connected.
2. The configured threshold is different from real TMA threshold.
3. The TMA related power cable is in the state of open circuit.
4. TAC fault.
5. TMA fault
Handling
process
1. Check whether the alarm threshold of TMA power supply is

configured correctly.
i.
Check whether the configured minimum current is

consistent with real TMA threshold (Generally speaking, it
is assumed as fault when TMA power current is less than
40mA).
Y --> Go to 2 Check whether power cable of TMA
channel is well connected.
N --> Go to ii. Change the alarm threshold of TMA power
supply.
ii. Change the alarm threshold of TMA power supply.

Change the configured minimum threshold of power
current so that it is consistent with real TAM threshold.
N --> Go to 2 Check whether power cable of TMA
channel is well connected.
2. Check whether
connected.
i.
power
cable
of
TMA
channel
is
well
Check whether the related power cable of TMA channel is

well connected.
Y --> Connection is Go to 3 Check whether the state
between TMA power cable and ground is open circuit or
high resistance.
N --> Cable connection error, re-connect the cable, Go to

46
N --> Go to 3 Check whether the state between TMA

power cable and ground is open circuit or high resistance.
3. Check whether the state between TMA power cable and
ground is open circuit or high resistance.
i.
Use multi-meter to detect if the state between TMA

Y --> Open circuit or high resistance state, replace this
cable, Go to ii. Check whether the alarm recovers.
N --> Go to 4. Replace TAC.

N --> Go to 4 Replace TAC.
4. Replace TAC.
Replace TAC, wait for two minutes, and then check whether
the alarm recovers.
N --> Go to 5 Replace TMA.
5. Replace TMA.
Replace TMA, wait for two minutes, and then check whether
the alarm recovers.
198084040
Description
Severity
Cause
TMA channel input is over current

Major
1. The configured threshold is not consistent with real TMA
threshold.
2. The connection between TMA power cable and ground is in
the state of short circuit or low resistance.
3. TAC fault
4 TMA fault
Handling
process

i.
Check whether the configured minimum current is

consistent with real TMA threshold (General speaking, it
is assumed as over current when the TMA power current
is greater than 135mA and less than 200mA).
Y --> Go to 2 Check whether the state between TMA
power cable and ground is short circuit or low resistance.
47

supply.
Change the configured upper limit of working current so
that it is consistent with real TMA threshold. Check
power cable and ground is short circuit or low resistance.
2. Check whether the state between TMA power cable and the
ground is short circuit or low resistance.
i.
Use multi-meter to Check whether the state between

TMA power cable and ground is short circuit or low
resistance.
Y --> Short circuit or low resistance, replace the cable,
Go to ii.
N --> Go to 3.
Replace TAC.

3. Replace TAC.
the alarm recovers.
4. Replace TMA.
the alarm recovers.
198084041
Description
Severity
Cause
TMA channel input is over current seriously.

Major
1. The configured threshold is inconsistent with real TMA
threshold.
2. The connection between TMA cable and ground is in the state
of short circuit.
3. TAC fault.
48
4. TMA fault.
Handling
process
1. Check whether TMA power current is normal.

Stop TAC from powering ATMA, and then use the multi-meter
to check whether TAC output voltage is normal.
Y --> Go to 2 Check whether the state between TMA power
cable and ground is short circuit or low resistance.
ground is short circuit or low resistance.
i.

TMA power cable and ground is short circuit or low
resistance.
Y --> Short circuit or low resistance, replace this cable,
Go to ii.
N --> Go to 3. Replace TAC.

3. Replace TAC.
the alarm recovers.
N --> Go to 4 Replace TMA
4. Replace TMA.
the alarm recovers.
198084042
Description
Severity
Cause
TMA channel input is under current.

Major
1. The configured threshold is incorrect.
2. The TMA related power cable is in the state of open circuit or
high resistance.
3. TAC fault
4. TMA fault
Handling
process

49
i.
Check whether the configured lower limit of working

current is consistent (Generally speaking, the default
threshold of TMA under-current alarm is 70~80mA).
Y --> Go to 2 Check whether the state between TMA
supply

Change the configured lower limit of TMA working current,
ground is open circuit or high resistance.
i.

TMA power cable and ground is open circuit or high
resistance.
Y --> Open circuit or high resistance state, replace this
cable, Go to ii. Check whether the alarm recovers.

3. Replace TAC.
the alarm recovers.
4. Replace TMA.
the alarm recovers.
198084043
Description
Severity
Cause
50
ATMA bypass alarm

Major
1. ATMA is seriously over-current or without any gain.
2. Power supply part of TAC is broken.

Handling
process
1. Reset TAC.
Reset TAC through OMC console, wait for two minutes, and
then check whether the alarm recovers.
N --> Go to 2 Check whether ATMA power supply is normal.
2. Check whether ATMA power supply is normal.
Let TAC not provide power to ATMA. Use multi-meter to
check whether TAC output voltage is normal.
Y --> Go to 3 Replace ATMA
3. Replace ATMA.
Replace ATMA, and then check whether the alarm recovers.
4. Replace TAC.
Replace TAC, and then check whether the alarm recovers.
198084044
Description
Severity
Cause
ATMA LNA alarm

Warning
1. ATMA is over current for a short time or its gain is reduced.
2. The internal alarm detection circuit of ATMA LNA is broken,
which causes false alarm."
Handling
process
1. Reset TAC.
Reset TAC through OMC console, wait for two minutes, and
N --> Go to 2 Check whether TMA power supply is normal.
2. Check whether ATMA power supply is normal.
Let TAC not provide power to ATMA. Use multi-meter to
Check whether TAC output voltage is normal
Y --> Go to 3 Replace ATMA
N --> Go to 4 Replace TAC
3. Replace ATMA.
51
Replace ATMA, and then check whether the alarm recovers.

4. Replace TAC.
Replace TAC, and then check whether the alarm recovers.
198084045
Description
Severity
Cause
Antenna VSWR alarm

Minor
1. DDL or antenna is not well connected with cables.
2. The cable between DDL and antenna is damaged.
3. Antenna fault"
Handling
process
1. Check whether the corresponding PA has VSWR alarm.

i.
Check whether the PA has VSWR alarm.

Y --> Go to ii. Process VSWR alarm of the PA
N --> Go to 2 Check whether antenna connection is
normal.
ii. Process VSWR alarm of the PA.

According to relevant suggestions for PA VSWR alarm, try
to remove the alarm. Check whether the current alarm
recovers.
N --> Go to 2 Check whether antenna connection is
normal.
2. Check whether antenna connection is normal.
i.
Check whether the corresponding DDL antenna port is

normally connected with antenna.
Y --> Go to 3 Replace the antenna.
N --> Go to ii. Check whether the alarm recovers.

N --> Go to 3 Replace the antenna.
3. Replace the antenna.
Replace the antenna, which is related to the DDL antenna
port, and then check whether the alarm recovers.
52

198084046
Description
Severity
Cause
Antenna over VSWR alarm

Major
1. DDL or antenna is not well connected with cables.
2. The cable between DDL and antenna is damaged.
3. Antenna fault"
Handling
process
1. Check whether antenna is connected normally.

i.
Check whether the corresponding DDL antenna port is

normally connected with antenna.
Y --> Go to 2 Replace antenna.

N --> Go to 2 Replace antenna.
2. Replace antenna.
Replace the antenna, which is related to the DDL antenna
port, and then check whether the alarm recovers.
198084047
Description
Severity
Cause
Over power alarm at calibration port

Warning
1. The calibration port at front panel of RDM board receives
large power signals, higher than 30dBm.
2. The power detected at RDM calibration port is inaccurate."
Handling
process
1. Check whether there is RF cable which connects RDM

calibration port and DDL antenna port.
Y --> Go to 2 Check whether the corresponding DDL bears
any cell.
N --> Go to 3 Check whether PA power is greater than
32dBm.
2. Check whether the corresponding DDL bears any cell.
53
i.
Check whether the corresponding DDL bears any local

cell.
Y --> Go to ii. Check whether the local cell related cell is
blocked.
32dBm.
ii. Check whether the local cell related cell is blocked.

Y --> Go to 3 Check whether PA power is greater than
32dBm.
N --> Go to iii. Block local cell.
iii. Block local cell.
Block local cell and Check whether the alarm recovers.
32dBm.
3. Check whether PA power is greater than 32dBm.
Y --> Please contact ZTE. Assist ZTE to determine the
abnormity of transmission channel, including related Tx
board and PA.
N --> Go to 4 Reset RDM board.
4. Reset RDM board.
Wait for two minutes. When the status of the board becomes
normal, conduct RDM static calibration. Check whether the
alarm still occurs.
Y --> Go to 5 Replace RDM board.
5. Replace RDM board.
Wait for two minutes. When the status of the board becomes
normal, conduct RDM static calibration. Check whether the
alarm still occurs.
198084048
Description
Severity
Cause
Handling
process
54
Calibration file on TRx board is abnormal.

Minor
The corresponding board calibration data is incomplete or
damaged.
198084049
Description
Severity
Cause
Handling
process
Forward channel bottom layer calibration file on RDM board is

abnormal
Minor
Forward channel bottom layer calibration file data on RDM board
is incomplete or damaged.
198084050
Description
Severity
Cause
Handling
process
Reverse channel bottom layer calibration file on RDM board is

abnormal
Minor
Reverse channel bottom layer calibration file data on RDM board
198084051
Description
Severity
Cause
Calibration port bottom layer calibration file on RDM board is

abnormal
Minor
Calibration port bottom layer calibration file data on RDM board
55
Handling
process

198084052
Description
Severity
Cause
Handling
process
Temperature compensation file on RDM board is abnormal.

Minor
Temperature compensation file data on RDM board is incomplete
or damaged.
198084053
Description
Severity
Cause
Handling
process
Forward channel system calibration file on RDM board is

abnormal.
Minor
Forward channel system
incomplete or damaged.
calibration
file
data
on
RDM
is
1. Conduct RDM static calibration.

Conduct static calibration on the corresponding port and
reset the board. Check whether the alarm recovers.
Replace the faulty board and re-conduct static calibration.
56
198084054
Description
Severity
Cause
Handling
process
Reverse channel system calibration file on RDM board is

abnormal.
Minor
Reverse channel system
incomplete or damaged.
calibration
file
data
on
RDM
is
1. Conduct static calibration.

Conduct static calibration on the corresponding port and
reset the board. Check whether the alarm recovers.
Replace the faulty board and re-conduct static calibration.
198084055
Description
Severity
Cause
Downlink digital IF crest factor reduction alarm

Minor
1. Digital signal PAR is very high.
2. Hardware is damaged.
3. DAC clock is unlocked.
4. Baseband board or interface board fault.
5. PA fault
6. Main control board fault
7. RDM board fault"
Handling
process
1. Check whether RF cables are connected correctly.

i.
Check RF cable connection, especially Check whether PA

feedback cable is connected correctly.
Y --> Go to 2 Check whether PA works normally

N --> Go to 2 Check whether PA works normally.
57
2. Check whether PA works normally.

i.
Check whether the PA works

connected with the faulty board.
normally,
which
is

N --> Go to ii. Process the abnormity of PA
ii. Process the abnormity of PA.
Solve the PA abnormity and Check whether the current
alarm recovers.
N --> Go to 4 Check whether digital power output is
normal.
4. Check whether digital power output is normal.
i.
Check whether digital power output is normal.

Y --> Go to 5 Unplug and plug in the faulty board.
N --> Go to ii. Process the abnormity of digital power
ii. Process the abnormity of digital power.

Solve the abnormal problem of digital power. Check
whether the current alarm recovers.
N --> Go to 5 Unplug and plug in the faulty board.
5. Unplug and plug in the faulty board.
Unplug and plug in the faulty board, wait for two minutes,
198084056
Description
58
Downlink digital IF pre-distortion alarm
Severity
Cause
Minor
1. DPD chip runs abnormally;
2. Software operation on DPD is failed.
Handling
process
1. Reset the fault board

Reset the fault board, wait for 5 minutes, then check if the
alarm is recovered or not.
Y-> Yes, end alarm processing
N-> No, skip to"2 Replace the fault board"
2. Replace the fault board
Replace the fault board, wait for 5 minutes, then check if the
Y-> Yes, end alarm processing.
N-> No, Please contact ZTE
198084057
Description
Severity
Cause
Downlink digital IF DAC clock is unlocked.

Major
1. Reference clock fault
2. Hardware is damaged."
Handling
process
1. Check whether the faulty board has PLL unlocked alarm.

i.
Check whether the faulty board has PLL unlocked alarm.

Y --> Go to ii. Process PLL unlocked alarm
ii. Process PLL unlocked alarm.

According to relevant suggestions for PLL alarm, try to
remove this alarm. Check whether the current alarm
recovers.
59
198084058
Description
Severity
Cause
Handling
process
Downlink digital power exceeds rated power slightly.

Warning
Input digital signal is wrong.
When this alarm occurs, Please contact ZTE Corporation.
198084059
Description
Severity
Cause
Handling
process
Downlink digital power greatly exceeds rated power.

Major
Input digital signal is wrong.
When this alarm occurs, Please contact ZTE Corporation.
198084060
Description
Severity
Cause
RF board PLL alarm

Major
1. Clock input from main control board is wrong.
2. Board hardware fault
Handling
process
1. Unplug and plug in the faulty board.

Unplug and plug in the faulty board, wait for two minutes,
60
198084061
Description
Severity
Cause
RDM PLL alarm

Major
1. Clock input from main control board is wrong.
2. RDM board hardware fault
Handling
process

N --> Go to 2 Check whether other board has PLL unlocked
alarm
2. Check whether other board has PLL unlocked alarm.
Y --> The main control board has a fault and please solved
the problem first.
198084062
Description
Severity
Cause
Handling
process
Transmission RF channel fault

Major
Fail to initialize chips on RF board.
61
198084063
Description
Severity
Cause
Handling
process
Receiving RF channel fault

Major
Fail to initialize chips on RF board.
198084064
Description
Severity
Cause
LNA alarm
Major
1. Board is not properly installed or backplane slot has a
problem.
2. The internal LNA is damaged.
3. The internal LNA alarm detection circuit is broken. Therefore,
false alarm is reported.
Handling
process
1. Unplug and plug in board.

Unplug and plug in board, and then check whether the alarm
recovers.
N --> Go to 2 Check whether board is normal.
2. Check whether board is normal.
Use a board with good LNA and plug it in the slot. Check
Y --> Go to 3 Replace the faulty board.
Replace the faulty board and Check whether the alarm
recovers.
62

198084065
Description
Severity
Cause
Abnormal power
Major
1. PA is not enabled.
2. PA transmit power is abnormal.
3. TRx board has a fault."
Handling
process
1. Check whether PA is enabled.

i.
Check whether the corresponding PA is enabled.

Y --> Go to 2 Reset PA.
N --> Go to ii. Enable PA
ii. Enable PA and Check whether the alarm recovers.

N --> Go to 2 Reset PA.
2. Reset PA.
Reset PA, wait until the PA works normally, and check
N --> Go to 3 Replace PA board.
3. Replace PA board
Replace PA board and check whether the alarm recovers.
N --> Go to 4 Reset the fault TRx board.
4. Reset the faulty TRx board
Reset the faulty TRx board and check whether the alarm
recovers.
N --> Go to 5 Replace the fault TRx board.
5. Replace the faulty TRx board.
Replace the faulty TRx board and check whether the alarm
recovers.
63
198084066
Description
Severity
Cause
Handling
process
DSP load failure

Major
The loading of DSP software failed
Reset the faulty board, wait for two minutes, and check
198084067
Description
Severity
Cause
Handling
process
DSP run error

Major
DSP run error
1. Check whether the status of PA is stopped.
Y --> Yes, start the PA, if the alarm recovers, alarm process
ends.
N --> Go to 2.Check the connected line.
2. Check whether the connected line of RF between the RF
board and PA is normal.
Y --> It indicates that the connected line is open. Connect it
well. If the alarm recovers, the alarm handling process
completes.
N --> Go to 3. Reboot the faulty board.
3. Reboot the faulty board.
Reboot the faulty board, wait for two minutes, and check
N --> Go to 4.Replace the faulty board.
64
198084068
Description
Severity
Cause
Environmental temperature is high

Major
1. The environmental temperature of Node B rack is higher than
system configured upper limit.
2. Fan fault.
3. Air conditioner problem.
4. The temperature sensor in fan box at PA layer has a fault.
5. The FCD (Flow Control Device) in fan box at PA layer has a
fault.
6. EMU fault.
Handling
process
1. Please check if the air conditioner in equipment room works

normally.
Y->Normal, skip to 5. Detect and remove the temperature
sensor fault in fan box at PA layer.
N->Abnormal, please solve the abnormity of air conditioner.
2. Detect and remove the temperature sensor fault in fan box
at PA layer.
i.
Check and detect the fault of temperature sensor in fan

box of PA layer. Check if the alarm is recovered.
Y->Alarm is recovered, alarm process ends.

N->Alarm is not recovered, skip to 6. Reset environmental
monitoring unit.
3. Reset environmental monitoring unit (EMU).
i.
Deplug and plug the EMC; wait for 2 minutes; check if

the alarm is recovered.

N->Alarm is not recovered, skip to 7. Detect and remove
the connector fault, which locates at EMU backplane.
4. Detect and remove the connector fault, which is located at
EMU backplane.
i.
Detect and remove the fault of connector, which is

located at EMU backplane Check if the alarm is recovered.
65
N->Alarm is not recovered, skip to 8. Replace the FCD in

fan box at PA layer.
5. Replace the FCD in fan box at PA layer.
i.
Replace FCD; check if the alarm is recovered.

the cable fault, which connects EMU backplane and fan box.
6. Detect and remove the cable fault, which connects EMU
backplane and fan box.
i.
Detect and remove the fault cable between EMU

backplane and fan box Check if the alarm is recovered.

N->Alarm is not recovered, skip to 10. Replace the EMC
board.
7. Replace the EMC board.
i.
Replace the EMC board; wait for 2 minutes; check if the

alarm is recovered.

N->Alarm is not recovered, please contact ZTE.
198084069
Description
Severity
Cause
Environmental temperature is low.

Major
1. The environmental temperature of Node B rack is under
lower limited, configured by the system.
4. The FCD (Flow control Device) in fan box at PA layer has a
fault.
5. EMU fault."
Handling
process
1. Check the configured lower limit of system environmental

temperature.
i.
Check
whether
the
configured
lower
environmental temperature is too high.
limit
of
Y --> Go to 2. Check real value of environmental

temperature.
N --> Go to ii. Change
environmental temperature.
the
alarm
threshold
of
ii. Change
the
alarm
threshold
of
environmental
temperature. Check whether the alarm recovers.
66

N --> Go to 2. Check real value of environmental
temperature.
2. Check the difference between real value and system detected
value of environmental temperature.
i.
Check whether the difference between real environmental

temperature and system detected temperature exceeds
60C.
Y --> Go to 5. Detect and remove the environmental
N --> Go to 3. Check whether there is a fan alarm.
3. Check whether there is a fan alarm.

i.
Check whether there is a fan alarm.

Y --> Go to ii. Process fan alarm.
N --> Go to 4. Check whether air conditioner works
normally.
ii. Process fan alarm.

According to relevant suggestions for fan alarm, try to
remove this alarm. Check whether the current alarm
recovers.
normally.
4. Check whether air conditioner works normally.
i.
Please check whether the air conditioner in equipment

room works normally.
Y --> Go to 5. Detect and remove the temperature
N --> Please solve the abnormity of air conditioner.

at PA layer.
i.
Check and detect the fault of temperature sensor in fan

box of PA layer. Check whether the alarm recovers.
N --> Go to 6. Reset environmental monitoring unit.
6. Reset environmental monitoring unit (EMU).

i.
Unplug and plug the EMC, wait for two minutes, and then
N --> Go to 7. Detect and remove the connector fault,
which locates at EMU backplane.
67
7. Detect and remove the connector fault, which locates at EMU

backplane.
i.
15 Detect and remove the fault of connector, which is

located at EMU backplane. Check whether the alarm
recovers.
N --> Go to 8. Replace the FCD in fan box at PA layer.
8. Replace the FCD in fan box at PA layer.

i. Replace FCD, and then check whether the alarm recovers.
N --> Go to 9. Detect and remove the cable fault, which
connects EMU backplane and fan box.
i.
16 Detect and remove the fault cable between EMU

backplane and fan box. Check whether the alarm
recovers.
N --> Go to 10. Replace EMC board.
10. Replace EMC board.

i.
Replace the EMC, wait for two minutes, and check

198084070
Description
Severity
Cause
Device temperature is high

Major
1. Device temperature is over high;
2. Fan problem;
3. Air conditioner problem;
4. The temperature sensor in fan box at control layer has a
fault.
5. The FCC (Fan Centrifugal Control) board in fan box at control
layer has a fault.
6. EMU fault
Handling
process
1. Check if the temperature at air outlet of control layer is

higher than 70C.
Y->Skip to 2. Check if there is a fan alarm.
68
N->Skip to 5. Detect and remove the temperature sensor

fault in fan box at control layer.
2. Check if there is a fan alarm.
i.
Check if there is a fan alarm.
Y->Yes, skip to ii Process fan alarm.

N->No, skip to 3. Detect and remove the temperature
sensor fault in fan box at control layer.
According to relevant suggestions for fan alarm, try to
remove this alarm. Check if the current alarm is recovered.
the temperature sensor fault in fan box at control layer.
at control layer.
i.
Detect and remove the fault of temperature sensor in fan

box at PA layer Check if the alarm is recovered.

N->Alarm is not recovered, skip to 4. Reset EMU.
4. Reset EMU.
i.
Deplug and plug the EMC; wait for 2 minutes; check if


the connector fault, which locates at EMU backplane.
backplane.
i. Detect and remove the fault of connector, which is
located at EMU backplane Check if the alarm is recovered.
N->Alarm is not recovered, skip to 6. Replace FCC board in
fan box at control layer.
6. Replace FCC board in fan box at control layer.
i.
Replace the FCC board in fan box at control layer; check

if the alarm is recovered.

the cable fault, which connects EMU backplane and fan box.
69
i.
Detect and remove the fault cable between EMU

backplane and fan box Check if the alarm is recovered.

N->Alarm is not recovered, skip to 8. Replace EMC.
8. Replace EMC.
198084071
Description
Severity
Cause
Device temperature is low

Major
1. Device temperature is too low.
fault.
layer has a fault.
5. EMU fault
Handling
process
1. Check whether device temperature is lower than -15oC.

Check whether the temperature at air outlet of control layer
is lower than -15oC.
Y --> Go to 2. Check whether air conditioner works
normally.
N --> Go to 3. Detect and remove the temperature sensor
2. Check whether air conditioner works normally.
Please check whether the air conditioner in equipment room
works normally.
Y --> Go to 3. Detect and remove the temperature sensor
fault in fan box at PA layer.
N --> Please solve the abnormity of air conditioner.
at control layer.
box at PA layer. Check whether the alarm recovers.
N --> Go to 4 Reset EMU.
4. Reset EMU.
Y --> Alarm recovers, alarm process ends.
70

backplane.
Detect and remove the fault of connector, which is located at
EMU backplane. Check whether the alarm recovers.
N --> Go to 6. Replace the FCC board in fan box at control
layer.
6. Replace the FCC board in fan box at control layer.
Replace the FCC board in fan box at control layer, and then
Detect and remove the fault cable between EMU backplane
and fan box. Check whether the alarm recovers.
N --> Go to 8. Replace EMC.
8. Replace EMC.
198084072
Description
Severity
Cause
Whole set temperature rising alarm

Major
1. The
difference
between
device
temperature
environmental temperature exceeds 15oC.
and
2. Fan problem.
4. Dust-proof net of the Node B rack is blocked.
fault.
layer has a fault.
71
8. The FCD (Flow Control Device) in fan box at control layer has
a fault.
9. EMU fault.
Handling
process
1. Check whether the difference between device temperature

and environmental temperature exceeds 15oC.
i.
Query the values of temperature at air outlet of control

layer and air intake of PA layer.
ii. Compare the two values, and then check whether the
difference exceeds 15oC.
Y --> Go to 2. Check whether there is a fan alarm.
N --> Go to 5. Detect and remove the temperature
sensor fault in fan box at control layer.
2. Check whether there is a fan alarm.
i.
Check whether there is a fan alarm.

Y --> Go to ii. Process fan alarm.
abnormally.

According to the relevant suggestions for fan alarm, try
to remove this alarm. Check whether the current alarm
recovers.
abnormally
3. Check whether air conditioner works abnormally.
Please check whether the air conditioner in equipment room
works abnormally.
Y --> Please solve the abnormity of air conditioner.
N --> Go to 4. Check whether dust-proof net on Node B
rack is blocked.
4. Check whether dust-proof net on Node B rack is blocked.
Y --> Clean it up.
at control layer.
fault in fan box at PA layer.
72

at PA layer.
Check and detect the fault of temperature sensor in fan box
of PA layer. Check whether the alarm recovers.
N --> Go to 7. Reset EMU.
7. Reset EMU.
Unplug and plug the EMC board, wait for two minutes, and
backplane.
N --> Go to 9. Replace FCC board in fan box at control
layer.
9. Replace FCC board in fan box at control layer.
Replace the FCC board, and then check whether the alarm
recovers.
N --> Go to 10. Replace FCD in fan box at PA layer.
10. Replace FCD in fan box at PA layer.
Replace the FCD, and then check whether the alarm recovers.
10. Replace EMC.
Replace the EMC, wait for two minutes, and then check
73
198084073
Description
Severity
Cause
Temperature sensor abnormity alarm

Warning
1. Temperature sensor fault in fan box at control layer.
2. Temperature sensor fault in fan box at PA layer.
3. FCC fault in fan box at control layer.
4. FCD fault in fan box at PA layer.
Handling
process
1. Detect and remove the cable fault between EMU and fan box.
N --> Go to 2. Detect the location of fault sensor.
2. Detect the location of fault sensor.
Temperature sensor at air outlet of control layer, Go to 3.

box at control layer.
Temperature sensor at air intake of PA layer, Go to 4.
box at PA layer.
3. Detect and remove the fault of temperature sensor in fan

box at control layer.
4. Detect and remove the fault of temperature sensor in fan
box at PA layer.
5. Reset EMU.
Unplug and plug EMC, wait for two minutes, and then check
backplane.
74

7. Replace EMC.
Replace EMC, wait for two minutes, and then check whether
the alarm recovers.
198084074
Description
Severity
Cause
Temperature sensor not on-duty alarm

Warning
1. The control cable between EMU and fan box has connection
problem.
fault.
4. The FCC in fan box at control layer has a fault.
5. The FCD in fan box at PA layer has a fault.
6. EMU fault.
Handling
process
1. Detect and remove the cable fault, which connects EMU and
fan box.
N --> Go to 2. Detect the location of fault sensor.
2. Detect the location of fault sensor.
For the temperature sensor at air outlet of control layer, Go

to 3. Detect and remove the temperature sensor fault in fan
box of control layer.
For the temperature sensor at air intake of PA layer, Go to 4.
Detect and remove the temperature sensor fault in fan box
of PA layer.

of control layer.
75

of PA layer.
5. Reset EMU.
backplane.
N --> Go to 7. Replace EMC
7. Replace EMC.
the alarm recovers.
198084075
Description
Severity
Cause
Fan alarm
Major
1. The black power cable is not connected or has a problem,
which connects X2 connector at front panel of fan box.
2. Either FCC or FCD has a fault.
3. Fan fault.
4. EMU fault."
Handling
process
1. Detect and remove the cable fault, which locates at front

panel of fan box.
Detect and remove the cable fault, which connects the front
panel of fan box. Check whether the alarm recovers.
N --> Go to 2. Check whether fan control board is normal.
76
2. Check whether fan control board is normal.
For the fan alarm occurring at upper layer, go to i.

and remove FCC fault at control layer.
Detect
For the fan alarm occurring at lower layer, go to ii. Detect

and remove FCD fault at PA layer.
i.
Detect and remove the FCC fault, which locates at control

layer.
Detect and remove the FCC fault at control layer, Go to
iii. Check whether the alarm recovers.
ii. Detect and remove the FCD fault at PA layer.

Detect and remove the FCD fault, which locates at PA
layer. Go to iii. Check whether the alarm recovers.
iii. Check whether the alarm recovers.
N --> Go to 3. Replace the fault fan.
3. Replace the fault fan.
Replace the fan, which stops rotation, and check whether the
alarm recovers.
N --> Go to 4 Check whether EMU works normally.
4. Check whether EMU works normally.
i.
Reset EMU.
Unplug and plug the EMC, wait for two minutes, and
N --> Go to ii. Replace EMC.
ii. Replace EMC.

Wait for two minutes, and check whether the alarm
recovers after the board works normal.
198084076
Description
Severity
Cause
Handling
process
Heat exchanger alarm

Major
Heat exchanger fault
1. Detect and remove the heat exchanger fault, and then check
77

198084077
Description
Severity
Cause
Gate safety alarm

Minor
1. The door is not closed.
2. The sensor is broken, which is used to detect gate safety."
Handling
process
1. Close the door, and then check whether the alarm recovers.
N --> Go to 2. Check whether gate safety sensor is broken.
2. Check whether gate safety sensor is broken.
Replace the gate safety sensor, and then check whether the
alarm recovers.
198084078
Description
Severity
Cause
Surge protection device has a fault alarm

Minor
1. SPD fault.
2. EMU fault"
Handling
process
1. Check whether the SPD cable is connected normally.

i.
Check whether the cable is well connected, which

connects the connector (denoted with LSP) on EMU or
BEMU.
Y --> Normal connection, Go to 2 Reset EMU.
N --> Reconnect cable, Go to ii. Check whether the
alarm recovers.

2. Reset EMU.
78
N --> Go to 3. Replace SPD and Check whether the alarm

recovers.
3. Replace SPD and Check whether the alarm recovers.
Replace SPD and Check whether the alarm recovers.
N --> Go to 4. Replace EMU.
4. Replace EMU.
Replace EMU or EMC, and then check whether the alarm
recovers.
198084079
Description
Severity
Cause
Rack power supply is under voltage.

Major
1. For B09, The detected power voltage of Node B rack is below
40V ( 1V). For B8912, The detected power voltage of Node
B rack is below the bound of under-voltage alarm (The bound
value is coincide with the setting value, the error is 1V).
2. For B09, EMU fault. For B8912, EM fault.
Handling
process
1. For B09, check whether rack power is under voltage.

i.
Open the power box at top of Node B rack. Use multimeter to measure voltage difference between two
terminals denoted with -48 V and -48 VGND, and then
check whether the voltage of rack power is below 40V
(1 V).
Note:
Be aware of short circuiting during voltage measurement.
Y --> Over low voltage, adjust the value of rack power

voltage to normal range. Go to ii. Check whether the
alarm recovers.
N --> Normal voltage. Go to 2. Reset EMU
Y --> Yes, The alarm handling process completes.
2. Reset EMU.
79
backplane.
4. Replace EMC.
Wait for EMC boards entering into normal state and Check
5. For B8912, check whether rack power is under voltage.
i.
Look up the voltage of rack power at LMT, and check

whether it belows the bound of under-voltage alarm (The
bound value is coincide with the setting value, the error
is +-1V).
Y --> Yes, adjust the value of rack power voltage to
normal range, Go to ii. Check whether the alarm
recovers.
N --> No, Look up and set the rational bound of voltage
alarm, Go to ii. Check whether the alarm recovers.

N --> Go to 6. Reset EM.
6. Reset EM.
Unplug and plug the EM, wait for two minutes, and then
N --> Go to 7.Replace EM.
7. Replace EM.
Wait for EM board entering into normal state and Check
80
198084080
Description
Severity
Cause
Rack power is over voltage

Major
1. For B09, The detected power voltage of Node B rack is above
57V (1V). For B8912, The detected power voltage of Node
B rack is above the bound of over-voltage alarm (The bound
value is coincide with the setting value, the error is 1V).
2. For B09, EMU fault. For B8912, EM fault
Handling
process
1. For B09, check whether rack power is over voltage.

i.
Open the power box at top of Node B rack. Use multimeter to measure voltage difference between two
terminals denoted with -48 V and -48 VGND, and then
check whether the voltage of rack power supply is above
57V (+-1V).
Note:
Be aware of short circuiting during voltage measurement.
Y --> Voltage is over high. Adjust the value of rack power

voltage to normal range. Go to ii. Check whether the
alarm recovers.
N --> Voltage is Go to 2. Reset EMU.
2. Reset EMU.
backplane.
4. Replace EMC.
81
the alarm recovers.
5. For B8912, check whether rack power is over voltage.
i.
Look up the power voltage of Node B rack at LMT, and

check whether the voltage of rack power supply is above
the bound of the over-voltage alarm(The bound value is
coincide with the setting value, the error is +-1V).
Y --> Adjust the value of rack power voltage to normal
range. Go to ii. Check whether the alarm recovers.
N --> Look up and set the rational bound of voltage
alarm. Go to ii. Check whether the alarm recovers.

N --> Go to 6. Reset EM.
6. Reset EM.
Unplug and plug the EM, wait for two minutes, and then
N --> Go to 7. Replace EM.
7. Replace EM.
Replace EM, wait for two minutes, and then check whether
the alarm recovers.
198084081
Description
Severity
Cause
Handling
process
Air conditioner has a fault, which is reported through dry contact.

Minor
Air conditioner fault
1. Check whether external air conditioner works normally.
i.
Check whether
normally.
the
external
air
conditioner
works
Y --> Normal, Please contact ZTE Corporation.

N --> Go to ii. Solve air conditioner fault.
ii. Solve air conditioner fault and Check whether the alarm
recovers.
82
198084082
Description
Severity
Cause
Handling
process
Air conditioner heater has a fault, which is reported through dry

contact.
Minor
Air conditioner heater fault
1. Check whether
normally.
i.
external
air
conditioner
heater
works
Check whether external air conditioner heater works

normally.
N --> Go to ii. Solve the air conditioner heater fault.
ii. Solve the air conditioner heater fault and Check whether
the alarm recovers.
198084083
Description
Severity
Air conditioner power has a fault, which is reported through dry

contact.
Minor
Cause
Air conditioner power supply is over/under voltage.
Handling
process
1. Check whether air conditioner power is normal.

i.
Check whether air conditioner power is normal.

N --> Go to ii. Solve the air conditioner power fault.
ii. Solve the air conditioner power fault and Check whether
the alarm recovers.
198084084
Description
Heat exchanger has a fault, which is reported through dry

contact.
83
Severity
Cause
Handling
process
Minor
External heat exchanger fault
1. Check whether external heat exchanger works normally.
i.
Check whether external heat exchanger works normally.

N --> Go to ii. Solve the heat exchanger fault.
ii. Solve the heat exchanger fault and check whether the
alarm recovers.
198084085
Description
Severity
Cause
Main power supply has a fault alarm

Major
1. Main power supply fault.
2. EMU fault
Handling
process
1. Check whether main power supply is normal.

i.
Check whether main power supply is normal.

Y --> Go to 2 Reset EMU.
N --> Go to ii. Process the fault of main power supply.
ii. Process the fault of main power supply.

Solve the fault of main power supply, and then check
2. Reset EMU.
backplane.
N --> Go to 4. Replace EMS
84
4. Replace EMS.
Replace EMS, wait for two minutes, and then check whether
the alarm recovers.
5. Replace EMC.
the alarm recovers.
198084086
Description
Severity
External device fault connected via dry contact

Minor
Cause
Fault location and alarm cause are determined according to

different types of external devices.
Handling
process
Problem solution is determined according to different types of

external devices.
198084087
Description
Severity
Cause
Surge protection device in cabinet has a fault alarm

Minor
1. SPD fault;
2. EMU fault
Handling
process
1. Check whether the SPD cable is connected normally.

i.
Check whether the cable is well connected, which

connects the connector (denoted with LSP) on EMU or
BEMU.
Y --> Normal connection, Go to 2 Reset EMU.
N --> Reconnect cable, Go to ii. Check whether the
alarm recovers.

2. Reset EMU.
85

N --> Go to 3. Replace SPD and Check whether the alarm
recovers.
3. Replace SPD and Check whether the alarm recovers.
Replace SPD and Check whether the alarm recovers.
N --> Go to 4. Replace EMU.
4. Replace EMU.
Replace EMU or EMC, and then check whether the alarm
recovers.
198084088
Description
Severity
Cause
Handling
process
Remote input power over-voltage alarm

Major
The input AC voltage of power module is higher than alarm
threshold 280v (error 1V), or the direct current voltage of
power module is higher than alarm threshold 60v (error 1V).
1. Check whether the voltage of RRU power supply is normal.
i.
Switch off RRU power. Unplug RRU-48V power plug. Use

multimeter to measure the difference between -48V
power socket and -48VGND terminal (i.e. Rack power
voltage). Observe if the power supply is normal.
Note:
Be aware of short circuit during measurement.
Y --> No voltage, try to remove the power supply fault so

that the voltage of Node B rack power supply is within
normal range, Go to ii.
Check whether the alarm
recovers.
N --> Normal voltage, Go to 2. Replace RRU power
module: RPWDC.
Switch on and wait until the system has finished booting.
N --> Go to 2. Replace RRU power module: RPWDC.
86
2. Replace RRU power module: RPWDC.

Replace the RRU power module : RPWDC. Correctly connect
power cables from RPWDC to internal modules of RRU.
198084089
Description
Severity
Remote input power under-voltage alarm

Major
Cause
The input AC voltage of power module is lower than alarm

threshold 80v (error 1V), or the direct current voltage of power
module is lower than alarm threshold 36v (error 1V).
Handling
process
1. Check whether the voltage of RRU power supply is under low.

i.

the multimeter to measure the difference between -48V
power socket and -48 VGND terminal (i.e. Rack power
voltage). Observe if the absolute value is lower than 37V
(error +-1V).
Note:
Y --> Under voltage. Adjust power supply of Node B rack

so that power voltage is within normal range. Go to ii.
N --> Normal voltage. Go to 2. Replace RRU power
module: RPWDC.
Replace the RRU power module: RPWDC. Correctly connect
87
198084090
Description
Severity
Cause
Handling
process
Remote input power powered-down alarm

Major
Power module is abnormal
i.

multimeter to measure the difference between -48V
power socket and -48VGND terminal (i.e. Rack power
voltage). Observe if the power supply is normal.
Note:
Y --> No voltage. Try to remove the power supply fault

so that the voltage of Node B rack power supply is within
normal range, Go to ii. Check whether the alarm
recovers.
module: RPWDC.
198084091
Description
Severity
Cause
Handling
process
88
Remote output power over-current alarm

Major
Power module output is abnormal.
1. Replace RRU power module.

198084092
Description
Severity
Cause
Handling
process
Remote output power under-voltage alarm

Major
198084093
Description
Severity
Cause
Handling
process
Remote antenna over VSWR alarm

Major
Antenna VSWR is over than limit[2.5~3.0], or there has strong
interferential signals of the same frequency, or RRU has fault.
1. Reset RRU.
2. Check whether the alarm recovers.
N --> Go to 3. Check whether the antenna connector is
screwed down tightly. If not, screw down it.
3. Check whether the antenna connector is screwed down
tightly. If not, screw down it.
4. Wait for three minutes, and check whether the alarm
recovers.
N --> Go to 5. Measure VSWR of antenna system use the
VSWR apparatus, and check whether the VSWR of antenna is
normal.
5. Measure VSWR of antenna system use the VSWR apparatus,
and check whether the VSWR of antenna is normal.
Y --> Maybe the part of RRU has fault.
N --> Repair the antenna.
89
6. Finish the above, wait for three minutes, and check whether
the alarm recovers.
198084094
Description
Severity
Cause
Handling
process
Remote antenna VSWR alarm

Major
Antenna VSWR is higher than limit[1.5~2.0] and lower than
limit[2.5~3.0], or there has strong interferential signals of the
same frequency, or RRU has fault.
1. Reset RRU.
screwed down tightly.
recovers.
N --> Go to 5. Measure VSWR of antenna system use the
VSWR apparatus, and check whether the VSWR of antenna is
normal.
5. Measure VSWR of antenna system use the VSWR apparatus,
and check whether the VSWR of antenna is normal.
Y --> Maybe the part of RRU has fault.
N --> Repair the antenna.
6. Finish the above, wait for three minutes, and check whether
the alarm recovers.
198084095
Description
Severity
Cause
90
Main power supply has a normal alarm

Minor
1.Main power supply normal fault.
Handling
process
1. Check whether external Main power supply works normally.

i.
Check whether
normally.
external
Main
power
supply
works

N --> Go to ii. Solve the Main power supply normal
fault.
ii. Solve the Main power supply normal fault and Check
198084096
Description
Severity
Cause
Handling
process
Flooded Fault
Minor
Flooding detected
1. Check whether Node B has been flooded.
i.
Check whether Node B has been flooded.

Y --> Go to ii. Solve the flood case.
ii. Solve flood case and Check whether the alarm recovers.
198084097
Description
Severity
Cause
Handling
process
Smog Fault
Minor
Smog detected
1. Check whether there is smog in Node B
i.
Check whether there is smog in Node B.

Y --> Go to ii. Solve the smog case.
ii. Solve smog case and Check whether the alarm recovers.
91
198084098
Description
Severity
Cause
Handling
process
Battery Fault
Minor
Battery fault detected
1. Check whether battery works normally.
i.
Check whether battery works normally.

N --> Go to ii. Solve the battery fault.
ii. Solve battery fault and Check whether the alarm recovers.
198084099
Description
Severity
Cause
Handling
process
Remote output power over-voltage alarm

Major
198084100
Description
Severity
Cause
Handling
process
Remote output power abnormal voltage alarm

Major
The output voltage of power module is abnormal.
92
198084101
Description
Severity
Cause
Handling
process
Fail to configure TC port

Major
Parameter error
1. Check configuration data.
i.
Upload the Node B configuration data through OMC

system. From configuration management system, open
the configuration data and Check whether it is correct.
Y --> Go to 2 Reset the faulty board.
N --> Go to ii. Change the wrong configuration data.
ii. Change the wrong configuration data.

According to checking results, change the wrong
configuration data, and then check whether the alarm
recovers.
198084102
Description
Severity
Cause
Handling
process
Fail to configure PVC

Major
Configuration parameter error
i.

93

According to the checking results, change the wrong
recovers.
198084103
Description
Severity
Cause
Handling
process
Fail to configure FE port

Major
i.


recovers.
94

198084104
Description
Severity
Cause
Handling
process
Fail to configure OMCB channel

Major
i.


recovers.
198084105
Description
Fail to configure SCTP association
95
Severity
Cause
Handling
process
Major
i.


According to the check results, change the wrong
recovers.
198084106
Description
Severity
Cause
Handling
process
Fail to configure TSI

Major
i.

Y --> Configuration data is Go to 2 Reset the faulty
board.
N --> Configuration data is wrong, Go to ii.
the wrong configuration data.
96
Change

recovers.
198084107
Description
Severity
Cause
Board parameter synchronization abnormity

Major
1. The board is configured, but not inserted.
2. The board link is interrupted.
3. The board software runs abnormally.
Handling
process
1. Check whether the board is well inserted.

i.
Check whether the faulty board is well inserted on the

rack.
Y --> Go to 2 Check whether the board has link
interruption alarm.
N --> Unplug and plug the board. Go to ii. Reconfigure
parameters.
ii. Reconfigure parameters.

Wait until the board enters normal state. Reconfigure its
parameters, and then check whether the board
parameter synchronization abnormity alarm recovers.
2. Check whether the board has link interruption alarm.
i.
Check whether the board has link interruption alarm.

Y --> Go to ii. Process board link interruption alarm.
97
N --> Go to 3. Check whether the board has application

software monitoring alarm.
ii. Process board link interruption alarm.
According to suggestions for board link interruption alarm,
try to remove the alarm. Go to 3 Check whether the
board has application software monitoring alarm.
3. Check whether the board has application software monitoring
alarm.
i.
Check whether the

monitoring alarm.
board
has
application
software
Y --> Go to ii. Process application software monitoring

alarm.
N --> Go to iii. Reconfigure parameters.
ii. Process application software monitoring alarm.
According to suggestions for application
monitoring alarm, try to remove the alarm.
software
iii. Reconfigure parameters.

From OMC console, reconfigure the board. Check whether
the board parameter synchronization abnormity alarm
recovers.
N --> Please contact ZTE Corporation."
198084108
Description
Severity
Board wrong insertion alarm

Major
Cause
The configured type of board is not consistent with that inserted

on the rack.
Handling
process
1. Check whether the board configured in database is consistent

with that inserted on the rack.
i.
Check whether the board configured in database is

consistent with that inserted on the rack.
Y --> Go to 2 Check whether the configured board
supports daughter board.
N --> Go to ii. Reconfigure the board.
ii. Reconfigure the board.

Either modify the board configured in database or replace
the board inserted on the rack so as to keep consistency.
98
N --> Go to ii. Reconfigure the board.

2. Check whether the configured board supports daughter
board.
i.
Check whether the board supports daughter board.

Y --> Go to ii. Check whether the configured daughter
board is consistent with the real board
ii. Check whether the configured

consistent with the real board.
daughter
board
is
Check whether the configured daughter board in

database is consistent with that actually inserted on the
rack.
Y --> Go to iii. Reconfigure the board.
iii. Reconfigure the board.
Modify the board configuration in database or replace the
board on the rack so as to keep consistency. Check
198084109
Description
Severity
Cause
Handling
process
SNTP time adjustment failure alarm

Minor
SNTP server doesn't boot or its link has a fault.
1. Check whether SNTP server is booted.
i.
From windows operation system, select Control Panel -->

Administrative Tools --> Service, and check whether
STNP service is booted or not.
Y --> Go to 2 Check whether the link between SNTP
server and Node B is normal.
N --> Go to ii. Start SNTP server.
ii. Start SNTP server.

Start SNTP server. Initiate the process of SNTP time
adjustment manually, and then check whether the alarm
recovers.
N --> Go to 2 Check whether the link between SNTP
server and Node B is normal.
99
2. Check whether the link between SNTP server and Node B is

normal.
i.
Check whether the link between SNTP server and Node B

is normal.
N --> Please solve the link problem first. When the link
becomes Go to ii. SNTP time adjustment
ii. SNTP time adjustment.

Initiate the process of SNTP time adjustment, and then
198084110
Description
Severity
Cause
Handling
process
Running software version synchronization failure

Major
This alarm is given when synchronization process is unsuccessful.
1. Check whether the master main control board has wrong
version alarm.
i.
Check whether the master main control board has wrong

software version alarm.
Y --> Go to ii. Process the wrong software version alarm
occurred on the master main control board.
N --> Go to 2 Check whether the slave main control
board has insufficient DOM space alarm.
ii. Process the wrong software version alarm occurred on

the master main control board.
According to relevant suggestions for main control board
wrong version alarm, try to remove the alarm. Check
2. Check whether the slave main control board has insufficient
DOM space alarm.
i.
Check whether the slave main

insufficient DOM space alarm.
control
board
has
Y --> Go to ii. Process the insufficient DOM space alarm

N --> Go to 3 Reset the slave main control board.
ii. Process the insufficient DOM space alarm.
100
According to relevant suggestions for insufficient DOM

space alarm, try to remove the alarm. Check whether the
alarm recovers.
3. Reset the slave main control board.
Reset the slave main control board, wait for two minutes,
N --> Go to 4 Replace the slave main control board
4. Replace the slave main control board.
Replace the slave main control board, wait for two minutes,
198084111
Description
Severity
Cause
Handling
process
Slave software version synchronization failure

Minor
This alarm is given when synchronization is unsuccessful.
version alarm.
i.

software version alarm.
Y --> Go to ii. Process the wrong software version alarm
occurred on the master main control board.

DOM space alarm.
i.

control
board
has
101
Y --> Go to ii. Process the insufficient DOM space alarm.

ii. Process the insufficient DOM space alarm.
According to the relevant suggestions for insufficient DOM
alarm recovers.
N --> Go to 4 Replace the slave main control board.
Y --> The original Please contact ZTE Corporation.
N --> The original alarm recovers, The alarm handling
process completes.
198084112
Description
Severity
Cause
Handling
process
Special software version synchronization failure

Minor
This alarm is given when synchronization is unsuccessful.
version alarm.
i.

version alarm.
Y --> Go to ii.
Process the wrong software version
alarm occurred on the master main control board.

102

DOM space alarm.
i.

Y --> Go to ii.
alarm.
control
board
has
Process the insufficient DOM space

ii. Process the insufficient DOM space alarm
According to relevant suggestions for insufficient DOM
alarm recovers.
N --> Go to 4 Replace the slave main control board.
198084113
Description
Severity
Cause
Handling
process
Running Software version fault

Major
There is no relevant record of this type of software at foreground.
Or this type of software file saved at foreground is damaged and
is rolled back manually. The version record has been updated
before the version is rolled back.
1. Please re-download the running software version package.
Re-download the running software version package, wait
until download is successful, and then check whether the
alarm recovers.
103
198084114
Description
Severity
Cause
Handling
process
Slave Software version fault

Minor
Or this type of software file saved at foreground is damaged.
1. Re-download slave software version package.
Re-download slave software version package, wait until
download is successful, and then check whether the alarm
recovers.
198084115
Description
Severity
Cause
Handling
process
Special Software version fault

Minor
Or this type of software file saved at foreground is damaged.
1. Re-download special software version package.
Re-download special software version package, wait until
download is successful, and then check whether the alarm
recovers.
198084116
Description
Severity
Cause
Handling
process
Insufficient DOM space alarm

Major
DOM has no available space.
1. Delete slave version package file.
Delete slave version package file through network
management console, and then check whether the alarm
recovers.
N --> Go to 2 Delete unused master software version.
2. Delete unused master software version.
104
Through network management console, delete the unused

software version file from the running software package, and
198084117
Description
Severity
Cause
Application software monitoring alarm

Critical
1. The communication between the faulty board and master
main control board is interrupted.
2. Wrong board parameter is configured.
Handling
process
1. Check whether the faulty board has corresponding board

communication link interruption alarm.
Y --> Go to 2. According to the suggestions for board
communication link interruption alarm, try to remove the
alarm.
N --> Go to 3. Check whether the faulty board has
corresponding board configuration parameter error alarm.
2. According to the suggestions for board communication link
interruption alarm, try to remove the alarm.
N --> Go to 3. Check whether the faulty board has
corresponding board configuration parameter error alarm.
3. Check whether the faulty board has corresponding board
configuration parameter error alarm.
Y --> Go to 4. According to suggestions for board
configuration parameter error alarm, try to remove the
alarm.
4. According to suggestions for board configuration parameter
error alarm, try to remove the alarm.
Reset the faulty board, wait for two minutes. Observe if the
alarm recovers.
N --> Go to 7 Wait for two minutes, observe if the alarm
recovers.
105

7. Wait for two minutes, observe if the alarm recovers.
198084118
Description
Severity
Cause
Fail to set ATMA gain.

Major
1. Parameter error.
2. ATMA device link is interrupted.
3. ATMA device is not on-duty.
Handling
process

i.

board.
N --> Configure data is wrong, Go to ii.
wrong configuration data
Change
the
ii. Change the wrong configure data.

recovers.
106
198084119
Description
Severity
Cause
Board configuration parameter error

Major
1. The system has no such board configuration parameter.
2. Configuration parameter error.
3. Hardware error.
Handling
process

i.
Upload Node B configuration data through OMC system.

Use configuration management system to open it, and
then check whether configuration parameter is needed by
the board.
N --> Go to ii. Add configuration data.
ii. Add configuration data.

According to real requirement, add board configuration
data or change configuration data. Check whether the
alarm recovers.
198084120
Description
Severity
Cause
Board parameter configuration is failed.

Major
3. Hardware error.
Handling
process

i.

then check whether the configuration data is correct.
board.
N --> Configuration data is wrong, Go to ii. Change
wrong configuration data.
ii. Change wrong configuration data.
107
According to real situation, change the wrong

recovers.
Note:
Resetting the board will cause interruption of all services carried
by the board. Therefore, please choose appropriate time to reset
it.
Reset the faulty board, wait for two minutes and Check
Note:
by the board. Therefore, please choose appropriate time to
replace it.
Replace the faulty board, wait for two minutes and check
198084121
Description
Severity
Cause
No configuration parameter for the board

Minor
3. Hardware error.
Handling
process
108

i.

then check whether the board required parameters are

configured.
N --> Go to ii. Add configuration data.
ii. Add configuration data.
According to real requirements, add or change
configuration data for the board, and then check whether
the alarm recovers.
198084122
Description
Severity
Cause
CPU over loading

Major
1. Too many test tasks or tracing tasks are initiated on the
board.
2. The tasks run on the board CPU are abnormal.
Handling
process
1. Do not intervene and wait for system auto-recovery.

Wait for thirty seconds, and then check whether the alarm
recovers.
N --> Go to 2 Check whether the system is busy in running
some services.
2. Check whether the system is busy in running some services.
i.
Check whether current service is busy or the system is

downloading software.
Y --> Go to ii. Wait until the current service is finished.
N --> Go to 3 Record detailed information.
ii. Wait until the current service is finished.

Wait for current service is finished or software has been
downloaded, and check whether the alarm recovers.
N --> Go to 3 Record detailed information.
3. Record detailed information.
i.
From OMC console, execute VME running information

querying function. Select the faulty board and CPU
usage rate.
109
ii. Record CPU usage rate of each task and process, record
current service and operations. Then Please contact ZTE
Corporation.
198084123
Description
Severity
Cause
Board communication link is interrupted.

Critical
1. This board is configured, but not inserted on Node B rack.
2. The board is Fail to download high layer software.
3. The board is Fail to run high layer software.
4. The link between the board and master main control board
has a fault.
Handling
process
1. Check type of interrupted link.
If the board direct link is interrupted, go to 3 Check whether

the board is inserted on Node B rack
IF the board transfer link is interrupted, go to 2 Process the
interrupted transfer link
2. Process the interrupted transfer link.

i.
Check whether the transfer board has link interruption

alarm between the faulty board and master main control
board.
Y --> Go to ii. Check whether alarm recovers.

N --> Go to 3 Check whether the board is inserted on
Node B rack.
3. Check whether the board is inserted on Node B rack.
i.
Check relevant Node B slot and find if the configured

board is inserted.
Y --> Go to ii. Insert the board
N --> Go to 4 Check whether there is software running
failure alarm.
ii. Insert the board.

Insert the configured board into the slot, wait for two
minutes, and then check whether the alarm recovers.
N --> Go to 4 Check whether there is software running
failure alarm
110
4. Check whether there is software running failure alarm.

i.
Check whether the main control board has an alarm,

which indicates the faulty board has software running
failure problem.
Y --> Go to ii. Process software running failure alarm
ii. Process software running failure alarm.

According to relevant suggestions for software running
failure alarm, try to remove the alarm. Check whether
the interrupted communication link alarm recovers.
198084124
Description
Severity
Cause
Database saved on master/slave board is Fail to be kept

synchronous
Major
1. Software version runs on master board is inconsistent with
that runs on slave board.
2. The link between master and slave board is congested or
interrupted, which causes data synchronization time-out.
Handling
process
1. Check whether software version runs on master board is

consistent with that runs on slave board.
i.
Use RJ45 network cable to connect debugging PC with

master board. Run ShowCurVer command to view
software version. If correct version information cannot be
displayed by running ShowCurVer command, run
ShowDbsVersion and check database version.
ii. Use RJ45 network cable to connect debugging PC with

slave board. Run ShowCurVer command to view
software version. If correct version information cannot be
displayed by running ShowCurVer command, run
ShowDbsVersion and check database version.
iii. Compare master and slave software version, and then
check whether it is not consistent.
N --> Go to 2 Wait for system auto-recovery.
i.
Do not intervene, wait for 10 minutes, and then check

111
N --> Go to ii. Reset slave board.

ii. Reset slave board.
If the system cannot auto-recovery, reset the slave board.
Wait until the board runs normally, and then check
198084125
Description
Severity
Cause
Database save failure

Major
1. DOM doesn't have sufficient space.
2. DOM file system is wrong.
3. DOM has a fault.
Handling
process
1. Check whether the faulty board has related insufficient DOM

space alarm.
i.
From OMC console, check whether main control board

has insufficient DOM space alarm.
Y --> Go to ii. Process DOM insufficient space alarm
N --> Go to 2 Check whether it is file system error
ii. Process DOM insufficient space alarm.

According to relevant suggestions for DOM insufficient
space alarm, try to remove the alarm. Check whether
the database saving failure alarm recovers.
N --> Go to 2 Check whether it is file system error.
2. Check whether it is file system error.
i.
Reset the faulty board.
ii. Wait for two minutes, and then check whether the alarm
recovers.
N --> Go to 3 Process DOM fault.
3. Process DOM fault.
Replace the faulty board, and then check whether the alarm
recovers.
112
198084126
Description
Severity
Cause
Handling
process
Fail to configure STM-1

Major
i.

then check whether configuration data is correct.
Y --> Correct configuration data, Go to 2 Reset the
faulty board.
N --> Wrong configuration data, Go to ii. Change wrong
configuration data.

According to real situation, change configuration data,
198084127
Description
Severity
Cause
Handling
process
Fail to configure CES

Major
i.

then check whether configuration data is correct.
113

faulty board.
configuration data.
According to real situation, change configuration data,
198084128
Description
Severity
Cause
Handling
process
Fail to configure channelized STM-1

Major
i.

faulty board.
configuration data.

According to real situation, change the configuration data,
114
Replace teh the faulty board, wait for two minutes, and then
198084129
Description
Severity
Cause
Board reboots alarm

Warning
1. A user sends a reset command.
2. The board is powered on and boots.
3. Software abnormity causes the board to auto reset.
Handling
process
1. Find the reason to reset the board.

Find the reason to reset the board.
f
If the user resets the board, there is no need for any

process.
If the board auto resets, Please contact ZTE Corporation.
198084130
Description
Severity
Cause
Handling
process
Dry contact configuration Failed

Minor
The operation of dry contact configuration failed
Reconfigure the dry contact that has this alarm
198084131
Description
Severity
Cause
Handling
process
Node B reboot notification

Warning
A user resets Node B or Node B is powered down and reboots.
1. Find the reason to reset Node B.
115
If the user resets the Node B, there is no need for any

process.
Node B is powered down and reboots. Please check whether
the power supply is normal.
If the Node B auto resets, Please contact ZTE Corporation.
198084132
Description
Severity
Cause
Handling
process
PPP Link Configer Failed

Major
Wrong configuration data
1. Check whether the link is OK
Y --> Go to 2. Check the configuration data
N --> Please deal the link fault
2. Check the configuration data
N --> Go to 3. Reconfigure data
3. Reconfigure data
198084133
Description
Severity
Cause
Handling
process
PPP Bundle Configer Failed

Major
Wrong configuration data
1. Check whether the link is OK
Y --> Go to 2. Check the configuration data
N --> Please deal the link fault
2. Check the configuration data
N --> Go to 3. Reconfigure data
3. Reconfigure data
116
198084134
Description
Severity
Cause
Handling
process
Master/slave changeover alarm

Warning
The changeover operation is initiated by a user or it is because
the master main control board has a fault.
1. Find the reason
operation.
to
initiate
master/slave
changeover
If the user initiates the master/slave changeover operation,

there is no need for any process.
If the system auto initiates the master/slave changeover
operation, please check whether the current slave board has
a fault.
198084135
Description
Severity
Cause
Handling
process
Database load fail

Critical
Loading database fail
1. Check out which table loading fails.
i.
R_SWPAT and R_SWCONF loading fail.

Download software and test it again.
ii. R_TESTSW loading fails.

Test software again.
ii. R_PMTASK loading fails.
Originating
the
task
measurement again.
of
statistical
performance
iv. Please contact ZTE Corporation.
198084136
Description
Severity
Cause
Uplink channel runs abnormally

Critical
1. CRA (an uplink DSP process unit on baseband board)
program runs abnormally.
2. ULSR (an uplink DSP process unit on baseband board)
3. Uplink core chip on baseband board works abnormally.
117
4. CPU on baseband board works abnormally.

Handling
process
This is because CRA and ULSR (uplink DSP process units on

baseband board) programs run abnormally, or the core chip
works abnormally. When this alarm happens, Please contact ZTE
Corporation.
198084137
Description
Severity
Cause
Downlink channel runs abnormally

Critical
1. HSDSP (a downlink DSP process unit on baseband board)
2. DLSR (a downlink DSP process unit on baseband board)
3. Downlink core chip on baseband board works abnormally.
4. CPU on baseband board works abnormally.
Handling
process
This is because DLSR and HSDSP (downlink DSP process units

on baseband board) programs run abnormally, or the core chip
works abnormally. When this alarm happens, Please contact ZTE
Corporation.
198084138
Description
Severity
Rx channel signal quality is abnormal

Major
Cause
"When the cell adopts receiving diversity mode, this alarm will
be reported if either primary or secondary antenna is not well
connected."
Handling
process
1. Check whether the receiving RF unit of the related local cell

is configured correctly.
i.
View the configuration of receiving RF unit of local cell

through OMC console. Check whether the configuration is
correct.
Y --> Go to 2 Check whether the cell related antenna is
well connected.

N --> Go to 2 Check whether the cell related antenna is
well connected.
2. Check whether the cell related antenna is well connected.
118
i.
Check the primary and secondary antennas, related to

the cell, and then check whether the antenna is well
connected.
Y --> Go to ii. Check whether diversity antenna of
adjacent sector is reversely connected.

N --> Go to iii. Check whether diversity antenna of
adjacent sector is reversely connected.
iii. Check whether diversity antenna of adjacent sector is
Y --> Go to iv. Check whether the alarm recovers.
N --> Go to v. Replace faulty antenna.
iv. Check whether the alarm recovers.
N --> Go to v. Replace faulty antenna.
v. Replace faulty antenna.
Replace the faulty antenna, and then check whether the
alarm recovers.
198084139
Description
Severity
Cause
PA over power alarm

Critical
1. Baseband power is abnormal, which causes very high input
power of PA.
2. TRx board is abnormal, which causes very high input power
of PA.
3. RDM hasn't been calibrated, which causes very high input
power of PA.
4. PA its own fault.
Handling
process
1. Enable or reset the protected PA, and then check whether

the alarm recovers.
N --> Go to 2 Conduct RDM system calibration.
2. Conduct RDM system calibration, and then check whether
the alarm recovers.
119

N --> Go to 3 Check whether downlink power is very high.
3. Check whether downlink power is very high.
Start downlink power self-test and Check whether downlink
power is very high.
Y --> Go to 4 Replace TRx board.
N --> Go to 5 Replace PA.
4. Replace TRx board.
Replace TRx board and Wait for two minutes and check
5. Replace PA.
Replace PA and wait for two minutes. Check whether the
alarm recovers.
198084140
Description
Severity
Cause
PA over VSWR alarm

Critical
1. The cable between the corresponding DDL antenna port and
antenna is either broken or not well-connected.
2. Antenna fault.
3. PA is abnormal."
Handling
process
1. Check whether there is antenna VSWR alarm.

i.
Check whether there is antenna VSWR alarm.

Y --> Go to ii. Process antenna VSWR alarm
N --> Go to 2 Check whether the cable is normally
connected
ii. Process antenna VSWR alarm.

According to the relevant suggestions for antenna VSWR
current alarm recovers.
N --> Go to 2 Check the cable between PA output and
DDL.
2. Check the cable between PA output and DDL.
120
Screw down the corresponding cable between PA output and

DDL. Check whether the alarm recovers.
N --> Go to 3 Replace the corresponding cable between PA
output and DDL.
3. Replace the corresponding cable between PA output and DDL.
Replace the corresponding cable between PA output and DDL.
N --> Go to 4 Enable or reset PA.
4. Enable or reset PA.
Enable or reset PA, wait until the PA works normally, and
Y --> Alarm recovers, The alarm handling process completes.
5. Replace PA.
Replace PA and wait until the PA works normally. Check
198084141
Description
Severity
Cause
PA over temperature alarm

Critical
1. The fan at PA layer cannot work normally. Therefore, cooling
problem occurs.
2. PA is abnormal.
Handling
process
1. Check whether there is a fan related alarm at PA layer.

i.
Check whether there is a fan related alarm at PA layer.

Y --> Go to ii. Process the fan related alarm
N --> Go to 2 Enable PA
ii. Process the fan related alarm.

According to the relevant suggestions for fan alarm, try
to remove the alarm. Check whether the current alarm
recovers.
N --> Go to 2 Enable PA.
2. Enable PA.
121
Try to remove the alarm by enabling the protected PA board

again. Check whether the alarm recovers.
3. Reset PA.
Reset PA board, wait until the PA works normally, and then
4. Replace PA.
Replace PA board, wait until the PA works normally, and then
198084142
Description
Severity
Cause
Handling
process
PA over current alarm

Critical
PA is abnormal.
1. Enable PA.
2. Reset PA.
Reset PA board and wait until the PA works normally. Check
3. Replace PA.
Replace PA board and wait until the PA works normally.
122
198084143
Description
Severity
Cause
Handling
process
PA device fault alarm

Critical
PA is abnormal.
1. Enable PA.
2. Reset PA.
Reset PA board and wait until the PA works normally. Check
3. Replace PA.
Replace PA board and wait until the PA works normally.
198084144
Description
Severity
Cause
PA VSWR alarm
Minor
1. The cable is not screwed down tightly, which connects the
DDL antenna port and antenna in the corresponding alarming
cell.
2. Antenna is abnormal.
3.
Handling
process
PA internal fault.
1. Check the cable between DDL antenna port and antenna.

Screw down the corresponding cable between DDL antenna
port and antenna. Check whether the alarm recovers.
N --> Go to 2 Replace the cable between DDL antenna port
and antenna.
2. Replace the cable between DDL antenna port and antenna.
123
Replace the cable between DDL antenna port and antenna.

Check whether the alarm recovers. Check whether the alarm
recovers.
N --> Go to 3 Check whether antenna has a fault.
3. Check whether antenna has a fault.
i.
Check whether antenna has a fault.

Y --> Go to ii.
Process antenna fault

DDL.
ii. Process antenna fault.
Replace antenna and Check whether the alarm recovers.
DDL.
4. Check the cable between PA output and DDL.
Screw down the corresponding cable between PA output and
DDL. Check whether the alarm recovers.
N --> Go to 5 Replace the cable between PA output and
DDL.
5. Replace the cable between PA output and DDL.
Replace the corresponding cable between PA output and DDL.
N --> Go to 6 Enable or reset PA.
6. Enable or reset PA.
Enable or reset PA, wait until the PA works normally, and
7. Replace PA.
Replace PA and wait until the PA works normally. Check
124
198084145
Description
Severity
Cause
Handling
process
PA communication fault
Critical
PA communication module has a fault or the cable is loosen,
which connects PA and monitoring module.
1. Reset RRU.
N --> Go to step 3.
3. Tightly connect the cable between monitoring and PA module,
replace PA module or replace monitoring module.
4. Wait for three minutes and then check whether the alarm
recovers.
198084146
Description
Severity
Cause
RET motor fault

Major
1. RET motor fault.
2. EMC fault.
Handling
process
1. Check whether RET motor is normal.

i.
Check whether RET motor is normal.

Y --> Go to 2 Reset EMC
N --> Go to ii. Process RET motor fault
ii. Process RET motor fault.

N --> Go to 2 Reset EMC
2. Reset EMC.
Wait for two minutes and Check whether the alarm recovers.
N --> Go to 3 Replace EMC.
3. Replace EMC.
125

198084147
Description
Severity
Cause
RET hardware fault

Major
1. RET hardware fault.
2. EMC fault.
Handling
process
1. Check whether RET hardware is normal.

i.
Check whether RET hardware is normal.

Y --> Go to 2 Reset EMC
N --> Go to ii. Process RET hardware fault
ii. Process RET hardware fault.

N --> Go to 2. Reset EMC
2. Reset EMC.
N --> Go to 3 Replace EMC
3. Replace EMC.
198084148
Description
Severity
Cause
Handling
process
RET software fault

Major
Parameter error
1. Reset EMC.
2. Replace EMC.
126
Wait for two minutes, and then check whether the alarm
recovers.
198084149
Description
Severity
Cause
Handling
process
ATMA hardware fault

Major
Parameter error
1. Reset EMC.
2. Replace EMC.
198084150
Description
Severity
Cause
Handling
process
ATMA software fault

Major
Parameter error
1. Reset EMC.
2. Replace EMC.
198084151
Description
ATMA communication link is interrupted.
127
Severity
Cause
Major
1. ATMA device fault.
2. The communication link between ATMA device and the
system has a problem.
3. TAC board fault.
4. EMC fault.
Handling
process
1. Check whether ATMA device has an alarm.

i.
Check whether ATMA device has an alarm.

Y --> Go to ii. Process ATMA device alarm.
N --> Go to 2 Check whether the communication link
between ATMA device and the system is connected
normally.
ii. Process ATMA device alarm.

According to the relevant suggestions for ATMA device
alarm, try to remove the alarm. Check whether the ATMA
communication link alarm recovers.
normally.
2. Check whether the communication link between ATMA device
and the system is connected normally.
i.
Check whether the communication link between ATMA

device and the Node B system is connected normally.
Y --> Go to iii. Replace communication cable
N --> Re-connect the cable, Go to ii.
the alarm recovers.
Check whether

N --> Go to iii. Replace communication cable.
iii. Replace communication cable.
Replace communication cable and Check whether the
alarm recovers.
N --> Go to 3 Reset TAC board.
3. Reset TAC board.
Reset TAC board, wait for two minutes, and check whether
the alarm recovers.
N --> Go to 4 Reset EMC.
128
4. Reset EMC.
Reset EMC, wait for two minutes, and check whether the
alarm recovers.
N --> Go to 5 Replace TAC board.
5. Replace TAC board.
6. Replace EMC.
198084152
Description
Severity
Cause
RET communication link is interrupted.

Major
1. RET device fault.
2. The communication cable between RET device and the
3. TAC board fault.
4. EMC fault.
Handling
process
1. Check whether RET device has an alarm.

i.
Check whether RET device has an alarm.

Y --> Go to ii. Process RET device alarm.
N --> Go to 2 Check whether the communication cable
between RET device and the system is connected
normally.
ii. Process RET device alarm.

According to relevant suggestions for RET device alarm,
try to remove the alarm. Check whether the RET
N --> Go to 2 Check whether the communication cable
between RET device and the system is connected
normally.
2. Check whether the communication cable between RET device
129
i.
Check whether the communication cable between RET

Y --> Go to iii. Replace communication cable
N --> Re-connect the cable, Go to ii. Check whether the
alarm recovers.

alarm recovers.
3. Reset TAC board.
the alarm recovers.
N --> Go to 4 Reset EMC
4. Reset EMC.
Reset EMC, wait for two minutes, and then check whether
the alarm recovers.
6. Replace EMC.
Wait for two minutes, and check whether the alarm recovers.
198084153
Description
Severity
Cause
130
ACOM hardware fault

Major
Parameter error
Handling
process
1. Reset EMC.
2. Replace EMC.
198084154
Description
Severity
Cause
Handling
process
ACOM software fault

Major
Parameter error
1. Reset EMC.
2. Replace EMC.
198084155
Description
Severity
Cause
ACOM address conflict

Notification
1. This alarm notification may be given if quick Unplug-and-plug
the connected AISG device.
2. Otherwise, new device is inserted, which has conflict address
with existing AISG device. "
Handling
process
1. If someone quick Unplugs and plugs the connected AISG

device, there is no need for any process. The original device
can resume to normal communication. If not, please go to 2.
Scan AISG device and add the new device."
2. Scan AISG device and add the new device.
131
198084156
Description
Severity
Cause
ACOM communication link is interrupted.

Major
1. ACOM device fault.
2. The communication link between ACOM device and the
3. TAC board fault.
4. EMC fault.
Handling
process
1. Check whether ATMA device has an alarm.

i.
Check whether ATMA device has an alarm.

Y --> Go to ii. Process ATMA device alarm.
normally.
ii. Process ATMA device alarm.

According to the relevant suggestions for ATMA device
alarm, try to remove the alarm. Check whether the ATMA
normally.
2. Check whether the communication link between ATMA device
i.
Check whether the communication link between ATMA

Y --> Go to iii. Replace communication cable.
N --> Re-connect the cable, Go to ii. Check whether the
alarm recovers.

alarm recovers.
3. Reset TAC board.
132
the alarm recovers.
N --> Go to 4 Reset EMC.
4. Reset EMC.
Reset EMC, wait for two minutes, and check whether the
alarm recovers.
6. Replace EMC.
198084157
Description
Severity
Remote input power over-voltage alarm

Major
Cause
The input voltage of power module is higher than alarm

threshold 60v(error+-1V).
Handling
process
1. Check whether the voltage of RRU power supply is over high.

i.

multimeter to measure the difference between -48 V
power socket and -48 VGND terminal (i.e. power voltage).
Observe if the absolute value is higher than 60 V (error
+-1V).
Note:
Y --> Over voltage, adjust power supply of Node B rack

so that power voltage is within normal range, Go to ii.
N --> Normal voltage, Go to 2. Replace RRU power
module: RPWDC.
133

N --> Alarm is not recovered, 2. Replace RRU power
module: RPWDC.
198084158
Description
Severity
Remote input power under-voltage alarm

Major
Cause
The input voltage of power module is lower than alarm threshold

37 v (error+-1V).
Handling
process
1. Check whether the voltage of RRU power supply is under low.

i.

Observe if the absolute value is lower than 37 V(error +1 V).
Note:
Y --> Under voltage Adjust power supply of Node B rack

so that power voltage is within normal range. Go to ii.
module: RPWDC.
134

198084159
Description
Severity
Cause
Handling
process
Remote input power breaking-current alarm

Major
Power module is abnormal.
i.

Observe if the power supply is normal.
Note:
Y --> No voltage. Try to remove the power supply fault
so that the voltage of Node B rack power supply is within
normal range. Go to ii. Check whether the alarm
recovers.
module: RPWDC.
198084160
Description
Remote output power over-current alarm
135
Severity
Cause
Handling
process
Major
Power supply fault
198084161
Description
Severity
Cause
Handling
process
Remote output power over-voltage alarm

Major
Power supply fault
198084162
Description
Severity
Cause
Handling
process
Remote power output under-voltage alarm

Major
Power supply fault
198084163
Description
Severity
Remote hardware fault

Critical
Cause
136
The system shall set the status of local cell, borne by RRU, to be
faulty.
Handling
process
1. Reset RRU.
2. Wait for two minutes, and then check whether the alarm
recovers.
N --> Go to 3. Replace faulty RRU.
3. Replace faulty RRU.
4. Wait for three minutes, and then check whether the alarm
recovers.
198084164
Description
Severity
Cause
Handling
process
Remote heater alarm

Major
Remote heater can not work normally
1. Reset RRU.
N --> Go to 3. replace the heater.
3. Replace the heater.
recovers.
198084165
Description
Severity
Cause
Handling
process
Remote antenna over VSWR alarm

Major
Auto close PA output. Set the status of corresponding
transmission channel to be fault. if the corresponding local cell
has no available transmission channel, the local cell shall be in
the status of fault. Meanwhile, the related cell shall be deleted. "
1. Reset RRU.
137

N --> Go to step 3.
recovers.
198084166
Description
Severity
Cause
Handling
process
Remote antenna VSWR

Major
Remote antenna hardware fault
1. Reset RRU.
screwed down tightly. If not, screw down it.
recovers.
198084167
Description
Severity
Cause
Handling
process
Low noise amplifier alarm

Major
Amplifier is damaged or input signal is large
1. Reset RRU.
2. Check whether the alarm recovers or not.
N --> Go to 3. Replace RRU.
3. Replace RRU.
4. Wait for three minutes and observe if the alarm recovers or
not.
138

N --> Please contact to ZTE office.
198084168
Description
Severity
Cause
Local benchmark clock is unlocked

Notification
1. Reference source is not configured.
2. Reference source is lost or degraded.
Handling
process
1. Check whether clock reference source is configured.

i.
Through OMC console, check whether reference source is

configured.
Y --> Go to 2 Check whether clock reference source is
normal.
N --> Go to ii. Configure clock reference source.
ii. Configure clock reference source.

Through OMC console, configure the usable clock
reference source, and then check whether the alarm
recovers.
N --> Go to 2 Check whether clock reference source is
normal.
2. Check whether clock reference source is normal.
i.
Check whether there is clock reference source lost or

degradation alarm.
Y --> Go to ii. Process clock reference source alarm.
ii. Process clock reference source alarm.

According to relevant suggestions for clock reference
source alarm, try to remove the alarm. Check whether
the clock lost alarm on the board recovers.
Note:
139
Note:
198084169
Description
Severity
Cause
GPS serial port fault

Notification
1. GPS card fault.
2. The connection between GPS card and the board is poor.
Handling
process
1. Unplug and plug GPS card.

Unplug and plug GPS card, and check whether the alarm still
exists.
Y --> Alarm still exists, Go to 2 Replace GPS card
2. Replace GPS card, and check whether the alarm recovers.
Replace GPS card, and check whether the alarm still exists.
198084170
Description
Severity
140
STM-1 B1 error code alarm

None
Cause
Handling
process
The transmission quality is deteriorated (optical signal is overpower or under-power). There is strong electromagnetic
interference source near optical port. Optical connector is
unclean. Device working environment is over-temperature, etc. "
1. Check whether STM-1 physical link has an alarm.
i.
Check whether STM-1 physical link has an alarm.

Y --> Go to ii. Solve physical link alarm
ii. Solve physical link alarm problem.

According to relevant suggestions, try to solve the alarm.
Wait for fifteen minutes. Observe if the alarm still exists.
Y --> Go to 2 Check whether optical interface board has
2. Check whether optical interface board has transmission clock
alarm.
i.
Check whether optical interface board has transmission

clock alarm.
Y --> Go to ii. Process transmission clock alarm.
module is abnormal.
ii. Process transmission clock alarm.

According to relevant suggestions for transmission clock
alarm, try to remove this alarm. Wait for fifteen minutes.
Observe if the alarm still exists.
Y --> Go to 3 Check whether local optical interface
module is abnormal.
i.

Y --> Go to ii. Process the abnormity of local optical
interface module.
N --> Go to 4 Check whether RNC or transport device
clock status is normal.
ii. Process the abnormity of local optical interface module.

Process the abnormity of local optical interface board.
Y --> Go to iii. Replace the faulty optical interface board
iii. Replace the faulty optical interface board.
141

finished booting. Observe if the alarm still exists.
Y --> Go to 4 Check whether RNC or transport device
normal.
i.
Check whether RNC or transport device clock status is

normal.
N --> Go to ii. Remove RNC or transport device clock
fault.
ii. Remove RNC or transport device clock fault. Observe if

this alarm still exists.
198084171
Description
Severity
Cause
Handling
process

Notification
unclean. Device working environment is over-temperature, etc.
i.


alarm.
i.

clock alarm.
Y --> Go to ii. Process transmission clock alarm
142

module is abnormal.
module is abnormal.
3. Check whether local optical interface board module is
abnormal.
i.

interface module.

Y --> Go to iii. Replace the faulty optical interface board.
normal.
i.

normal.
Y --> Clock status is normal, Please contact ZTE
Corporation.
N --> Clock status is Go to ii. Remove RNC or transport
device clock fault

143
198084172
Description
Severity
Cause
STM-1 B2 FEBEI (Far End Block

Notification
1. Sending fiber is abnormal.
2. The peer optical port has a fault.
3. Local optical port has a fault.
4. Transmission BER is very big.
5 Transmission clock is not synchronous.
Handling
process

i.


alarm.
i.

clock alarm.
module is abnormal.

module is abnormal.
i.

interface module.
144

normal.
i.

normal.
fault.

198084173
Description
Severity
Cause
Handling
process

Notification
unclean. Device working environment is over-temperature, etc.
i.

Y --> Go to ii. Solve physical link alarm.

145

alarm.
i.

clock alarm.
module is abnormal.

module is abnormal.
i.

interface board.

normal.
i.

normal.
Y --> Clock status is normal, Please contact ZTE
Corporation.
device clock fault.

146

198084174
Description
Severity
Cause
STM-1 B3 FEBEI (Far End Block Error Indicator) alarm

Notification
Handling
process

i.


alarm.
i.

clock alarm.
module is abnormal.

alarm, try to remove the alarm. Wait for fifteen minutes.
module is abnormal.
i.
147

interface module.
normal.
i.

normal.
fault.

198084175
Description
Severity
Cause
STM-1 MSRDI (MS Remote Defect Indicator) alarm

Notification
Handling
process

i.

148

alarm.
i.

clock alarm.
module is abnormal.

module is abnormal.
i.

interface module
abnormal.

Y --> Go to 4 Check whether the peer fiber link is
abnormal.
N --> Alarm process ends.
149
Check whether the peer fiber link is abnormal. .Observe if

the alarm still exists.
If it is the remote device fault, please remove the fault of the

peer device. The alarm handling process completes.
If it is the optical fiber fault, please ask your customer for
198084176
Description
Severity
Cause
STM-1 HPRDI (High-order Path Remote Defect Indicator) alarm

Notification
Handling
process

i.

Y --> Go to ii. Solve physical link alarm.

alarm.
i.

clock alarm.
module is abnormal.

module is abnormal.
150

i.

interface module
N --> Go to 4 Check is the peer fiber link is abnormal.

abnormal.
Check whether the peer fiber link is abnormal. Observe if the
alarm still exists.

198084177
Description
Severity
Cause
STM-1 HPPLM (High-order Path Payload Level Mismatch)

Notification
1. Receiving fiber is abnormal.
Handling
process

i.

151
ii. Solve physical link alarm problem

alarm.
i.

clock alarm.
module is abnormal.

module is abnormal.
i.

interface module.
abnormal

abnormal.
alarm still exists.
152

198084178
Description
Severity
Cause
STM-1 loss of cell delineation

Notification
Handling
process

i.

transmission clock alarm

alarm.
i.

clock alarm.
module is abnormal.

module is abnormal.
153
i.

interface module.
abnormal.

abnormal.
alarm still exists.

198084179
Description
Severity
Cause
STM-1 Rx cell CRC error

Notification
1. Transmission clock is not synchronous.
Handling
process

i.

transmission clock alarm
154

alarm.
i.

clock alarm.
module is abnormal.

module is abnormal.
i.

interface module.
abnormal.

abnormal
alarm still exists.

155

198084180
Description
Severity
Cause
E1/T1 HDB3 coding violation alarm

Notification
1. E1/T1 setting is incorrect.
4. The peer device is abnormal.
5. E1/T1 grounding does not meet relevant criterion.
Handling
process
1. Check whether E1physical link has an alarm.

i.
Check whether E1 physical link has an alarm.

Y --> Go to ii. Check whether the alarm problem is
solved.
ii. Check whether the alarm problem is solved.

Y --> Go to 2 Check whether local interface board has
N --> No, The alarm handling process completes.
2. Check whether local interface board has transmission clock
alarm.
i.
Check whether local interface board has transmission

clock alarm.
N --> Go to 3 Check whether local interface board is
abnormal.

Y --> Go to 3 Check whether local interface board is
abnormal.
3. Check whether local interface board is abnormal.
156
i.
Use a good E1 cable to connect receiving end and

transmitting end of the fault E1 link. Wait for fifteen
minutes. Observe if the alarm still exists.
Y --> Go to ii. Process the abnormity of local interface
board.
N --> Go to 4 Check whether the device is grounded
correctly.
ii. Process the abnormity of local interface board.

4. Check whether the device is grounded correctly.
i.
Check whether E1 line is grounded correctly.

Y --> E1 link is grounded normally, Go to 5 Check
N --> E1 link grounding does not meet criterion, Go to ii.
Re-connect the grounding line of E1 link
ii. Re-connect the grounding line of E1 link.

N --> No, alarm process ends.
normal.
i.

normal.
fault.
ii. Remove RNC or transport device clock fault.

iii. Observe if the alarm still exists.
Y --> It is the link fault. Please ask your customer for
help to process transport problem. The alarm handling
process completes.
N --> It is the remote device fault. Please remove the
completes.
198084181
Description
Severity
Cause
E1/T1 link slip code alarm

Notification
1. Transport clock is abnormal.
157

3. E1/T1 transport trunk has problem.
4. E1/T1 grounding does not meet relevant criterion.
Handling
process
1. Check whether E1 physical link has an alarm.

i.
Check whether E1 physical link has an alarm.

Y --> Go to ii. Check whether the alarm problem is
solved.
ii. Check whether the alarm problem is solved.

Y --> Go to 2 Check whether local interface board has
2. Check whether local interface board has transmission clock
alarm.
i.
Check whether local interface board has transmission

clock alarm.
N --> Go to 3 Check whether local interface board is
abnormal.

Y --> Go to 3 Check whether local interface board is
abnormal.
3. Check whether local interface board is abnormal.
i.
Use a good E1 cable to connect receiving end and

transmitting end of the fault E1 link. Wait for fifteen
minutes. Observe if the alarm still exists.
Y --> Go to ii. Process the abnormity of local interface
board.
N --> Go to 4 Check whether the device is grounded
correctly.
ii. Process the abnormity of local interface board.

4. Check whether the device is grounded correctly.
i.
158
Check whether E1 line is grounded correctly.
Y --> E1 link is grounded normally, Go to 5 Check

N --> E1 link grounding does not meet criterion, Go to ii.
Re-connect the grounding line of E1 link.
ii. Re-connect the grounding line of E1 link.
normal.
i.

normal.
Y --> Clock status is normal, indicating the peer is
normal. Please contact ZTE Corporation.
device clock fault.
ii. Remove RNC or transport device clock fault.

iii. Observe if the alarm still exists.
Y --> It is the link fault. Please ask your customer for
help to process transport problem. The alarm handling
process completes.
N --> It is the remote device fault. Please remove the
completes.
198084182
Description
Severity
Cause
Handling
process
ATM is overload
Notification
ATM traffic exceeds normal range.
1. Check whether the corresponding PVC parameter is correctly
configured.
i.
Through
OMC
console,
change
PVC
bandwidth
configuration so that it is consistent with RNC. Wait for
fifteen minutes. Observe if the alarm still exists.
Y --> Go to 2 Process the abnormity of local interface
board.
2. Process the abnormity of local interface board.

i.
159
After single board has finished booting and RUN light

flashes normally (in 1Hz frequency), query the alarm
status of corresponding board. Check whether the alarm
still exists.
Y --> Go to ii. Replace the alarming interface board.
ii. Replace the alarming interface board.
Note:
Replacing interface board may cause the services carried on the
board being interrupted. Therefore, please choose appropriate
time to replace it.
After single board has finished booting and RUN light

flashes normally(in 1Hz frequency), query the alarm
status of corresponding board. Check whether the alarm
still exists.
198084183
Description
Severity
Cause
SSCOP fault
Notification
1. Node B clock fault.
2. The configured bandwidth of AAL5 PVC at Node B side is too
small.
3. Poor transmission quality.
Handling
process
1. Check whether there is clock alarm, which affects Iub

interface.
Solve the clock alarm, which affects Iub interface. Go to 2
Check whether bandwidth meets transmission requirement.
2. Check whether bandwidth meets transmission requirement.
View PVC link bandwidth from OMC console.
Y --> Go to 3 Check and improve quality of transmission
link
N --> Change the configuration of PVC link bandwidth.
3. Check and improve quality of transmission link.
Ask
transmission
maintenance
engineers
to
check
transmission link and try to solve the problem. If
160
transmission
Corporation.
becomes
normal,
Please
contact
ZTE
198084184
Description
Severity
Cause
ALCAP link fault

None
This is related to the above alarm sub-code.
1: Local AAL2 link is in the state of blocking.
2: Node B ALCAP has no idle instance, indicating some ALCAP
instances are not released.
3, 4, 5, 7: ALCAP protocol version at both ends is not matched.
6: ALCAP resources at both ends are not matched.
9: Node B cid is occupied.
Other value: none
Handling
process
1. Check whether ALCAP link is blocked.

According to alarm sub-code, check whether ALCAP link is
blocked.
Y --> Unblock the corresponding AAL2 path.
N --> Go to 2 Check whether ALCAP protocol version is
unmatched.
2. Check whether ALCAP protocol version is unmatched.
According to alarm sub-code (related to 3, 4, 5, 7), check
whether ALCAP protocol version is unmatched.
Y --> Change software version so that both ends have the
same protocol version.
N --> Go to 4 Other reason process.
3. Other reason process.
Please contact ZTE to solve the problem.
198084185
Description
Severity
Cause
Handling
process
SCTP association fault

Notification
It is impossible to apply and obtain resources from the system.
recovers.
161

198084186
Description
Severity
Error PATHID alarm is received.

Notification
Cause
The configuration of AAL2 Pathid at Node B side is inconsistent

with that at RNC side.
Handling
process
1. Check whether the configuration of AAL2 link parameter is

consistent with its peer end.
N --> According to AAL2 resources at RNC side, add or
change AAL2 link configuration at Node B side. The alarm
198084187
Description
Severity
Cause
RNC IP is unavailable
Notification
2. The configuration of local FE parameters is wrong.
4. Local network fault.
Handling
process
Check whether network cable is abnormal.

Please check whether network cable has the following problem:
1. Network cable is not tightly connected.
2. Network cable is bad.
Please solve the above problem if there is any.
162
Check whether FE parameters of local network port are

Check FE parameters such as NODE B IP address, gateway
IP, subnet mask. Make sure the parameters are correctly
configured.
If router or network gateway is connected, please check the
corresponding configuration.
198084188
Description
Severity
Cause
Handling
process
PPP Link Recycle

Notification
Iub Link has recycled
If HDLC configured on E1/STM1/FE link, check whether the link
has recycled.
Y --> Cancel the link recycle.
N --> Do not care.
198084189
Description
Severity
Cause
Handling
process
PAP authorize failed

Notification
Wrong user password
Check whether the user password is right.
N --> Please reconfigure the data.
198084190
Description
Severity
Cause
Handling
process
CHAP authorize failed

Notification
Wrong user password
Check whether the user password is right.
198084191
Description
Severity
Cause
Handling
process
CHAP oppose authorize failed

Notification
Wrong user password
Check whether the user password is right
163
198084192
Description
Severity
Cause
Handling
process
Alarm storm notification

Notification
Some alarms occurred frequently
1. Check the alarm, which causes this alarm storm.
From network management console, check the parameters
attached in alarm storm notification and finds which alarm
causes this alarm storm.
2. Try to remove the alarm which causes this alarm storm
according to the relevant suggestions for this alarm.
3. Check whether the alarm storm notification disappears.
198084193
Description
Severity
Cause
Handling
process
Cell deletion notification

Notification
A user has initiated the operation of blocking local cell or the
system has cell resource fault.
1. Find the reason to delete the cell.
i.
f
Find the reason to delete the cell.

If the user initiates the operation of blocking the
corresponding local cell, there is no need for any process.
If the system auto deletes the cell, go to ii. Check
whether there is an alarm, which affects the local cell.
ii. Check whether there is an alarm, which affects the local

cell.
Y --> Handle the alarm according to relevant suggestions.
198084194
Description
Severity
Cause
164
Node B reboot notification

Notification
A user resets Node B or Node B is powered down and reboots.
Handling
process
1. Find the reason to reset Node B.
If the user resets the Node B, there is no need for any

process.
Node B is powered down and reboots, please check whether
the power supply is normal.
If Node B auto resets, Please contact ZTE Corporation.
198084195
Description
Severity
Cause
Handling
process
Master/slave changeover alarm

Notification
The changeover operation is initiated by a user or it is because
the master main control board has a fault.
1. Find the reason
operation.
to
initiate
master/slave
changeover
If the user initiates the master/slave changeover operation,

there is no need for any process.
If the system auto initiates the master/slave changeover
operation, please check whether the current slave board has
a fault.
198084196
Description
Severity
Cause
ATMA device address conflict

Notification
Handling
process

can resume to normal communication. If not, go to 2. Scan
AISG device and add the new device."
198084197
Description
Severity
RET device address conflict

Notification
Cause
165

Handling
process

has resumed to normal communication. If not, go to 2. Scan
AISG device and add the new device."
198084198
Description
Severity
Cause
CSU not locked

Major
1. Optic port belonged board is not tightly connected.
2. Optic port belonged board has fault.
Handling
process
1. Optic port 0~3 belong to the main control board and optic
port 4~5 belong to BRIS board.
Check whether the faulty board is main control board type.
Y --> Go to 2. Deal with main control board fault
N --> Go to 3. Deal with BRIS board fault
2. Deal with main control board fault.
Note:
Replace or reset main control board. which lead to the board will
cause interruption of all services carried on the board. Therefore,
please choose appropriate time to replace it.
i.
Reset fault main control board

Reset fault main control board. Wait for three minutes
until the board is normal. Check whether the alarm
recovers.
N --> Go to ii. Replace fault main control board.
ii. Replace fault main control board

Replace fault main control board. Wait for three minutes
until the board is normal. Check whether the alarm
recovers.
166
3. Deal with BRIS board fault.
Note:
Replace or reset BRIS board so that reset main control board.
which lead to the board will cause interruption of all services
carried on the board. therefore, please choose appropriate time
to replace it.
i.
Check whether BRIS board is not tightly connected.

Check and BRIS board is tightly connected
N --> Go to ii. Reset board
ii. Reset board.

Reset BRIS board belonged main control board. Wait for
three minutes until the board is normal. Check whether
the alarm recovers
N --> Go to iii. Replace fault BRIS board
iii. Replace fault BRIS board
Replace BRIS board. Wait for three minutes until the
board is normal. Check whether the alarm recovers
198084199
Description
Severity
Receiving antenna is imbalance

Major
Cause
When the receive mode of cell antenna is diversity or mulantenna receive, if there is configure wrong of receive antenna
or not well contacted in cell, will reported this alarm.
Handling
process
1. Check whether the receive RF unit of local cell related with

the cell is configured rightly.
i.
Check whether the receive RF unit of local cell is

configured rightly in LMT.
Y --> Go to2 Check whether the antenna of related cell
is contacted well.
167

N --> Go to 2 Check whether the antenna of related cell
is contacted well.
2. Check whether the antenna of related cell is contacted well.
i.
Check whether the Master and Slave antennas of related

cell contacted well.
Y --> Go to iii. Check whether the diversity antenna of
neighborhood sector contacted rightly.

N --> Go to iii. Check whether the diversity antenna of
neighborhood sector contacted rightly.
iii. Check whether the diversity antenna of neighborhood
sector contacted rightly.
Y --> Go to iv. Check whether the alarm recovers.
N --> Go to v. Replace the faulty antenna.
iv. Check whether the alarm recovers.
N --> Go to v. Replace the faulty antenna.
v. Replace the faulty antenna.
Replace the antenna, and check whether the alarm
recovers.
198084200
Description
Severity
Cause
Main input power over-voltage alarm

Major
1. Input voltage of main power is abnormal.
2. Environment monitor unit EMU is broken."
Handling
process
1. Check support voltage of BPWC is normal.

i.
Turn off BPWC power, take off BPWC -48 V plug, measure
the difference of voltage between -48 V and -48 VGND by
multimeter (the support voltage of rack), and then check
whether it is normal.
Note:
168
Don't make short circuit while measuring.
Y --> Go to ii. Check whether the alarm recovers.

N --> Go to 2.Change the power module of BPWC.
Turn on the power and wait for the start of system.
Y --> the alarm handling process completes.
N --> Go to 2. Change the power module of BPWC.
2. Change the power module of BPWC.
Change the power module of BPWC, link the inner lines of
modules between BPWC and BBU by the right ways, turn on
the power, and wait for the start of system. Check whether
the alarm recovers.
198084201
Description
Severity
Cause
Main input power under-voltage alarm

Major
Handling
process
1. Check support voltage of BPWC is normal.

i.
Turn off BPWC power,take off BPWC -48V plug, measure

the difference of voltage between -48 V and -48 VGND by
multimeter(the support voltage of rack), and check
whether the absolute value is below 37 V(error is 1 V).
Note:
Don't make short circuit while measuring.
Y --> Go to ii. Check whether the alarm recovers.

N --> Go to 2. Change the power module RPWDC of
RRU.
Turn on the power, and wait for the start of system.
169
Y --> The alarm handling process completed.

N --> Go to 2.Change the power module RPWDC of
RRU.
2. Change the power module RPWDC of RRU.
Change the power module RPWDC of RRU, link the inner
lines of modules between BPWC and BBU by the right
ways, turn on the power, and wait for the start of system.
198084202
Description
Severity
Cause
Main input power powered-down alarm

Major
Handling
process
1. Check whether the main power is normal.

i.
Check whether the main power is normal.

Y --> Go to 2. Restart the environment monitor unit.
N --> Go to ii. Handle the main power fault.
ii. Handle the main power fault.

Deal with the main power fault, and check whether the
alarm recovers.
N --> Go to 2. Restart the environment monitor unit.
2. Restart the environment monitor unit.
Pull out and push in the EMC board, wait for two minutes,
and check whether the alarm recovers.
N --> Go to 3.Exclude the linker fault of back board in EMU.
3. Exclude the linker fault of back board in EMU.
Exclude the linker fault of back board in EMU, and check
N --> Go to 4.Replace the accessorial board of environment
monitor.
4. Replace the accessorial board of environment monitor.
170
Replace the accessorial board EMS of environment monitor,

wait for two minutes, and check whether the alarm recovers.
N Go to 5. Replace the environment monitor board.
5. Replace the environment monitor board.
Replace the environment monitor board EMC, wait for two
minutes, and check whether the alarm recovers.
198084203
Description
Severity
Cause
Handling
process
Subcard is not exist,although it has configured

Major
Subcard which is configured is not exist.
1. Check whether the subcard is configured rightly.
Y --> Go to 2.Check whether the alarm recovers.
N --> Go to 3.Config the subcard rightly.
3. Config the subcard rightly.
198084204
Description
Severity
Insert Subcard error

Major
Cause
The configured subcard type is not coincided with the actual

subcard type.
Handling
process
1. Check whether the configured subcard type is coincided with

the actual subcard type.
N --> Go to 3.Config the subcard type that is coincided with
the actual subcard type.
171

3. Configure the subcard type that is coincided with the actual
subcard type.
198084205
Description
Severity
Cause
Handling
process
Detect the unconfigured subcard

Minor
"There has subcard in board, but has not configured for use."
1. Check whether the subcard is configured.
N --> Go to 3.Config the subcard for use or remove it.
3. Configure the subcard for use or remove it.
198084206
Description
Severity
Cause
Handling
process
Software file is not identical with the DataBase record

Major
There has record in DB while software file is not existed.
Download the software again, and Check whether the alarm
recovers.
198084207
Description
172
Firmware file is not identical with the DataBase record
Severity
Major
Cause
Firmware file is not exist or its size is not identical with the DB
record.
Handling
process
Download the firmware package of the same version again, and

198084208
Description
Severity
Cause
Handling
process
AISG EEPROM error

Minor
Parameter error
1. Reset AISG device
Wait for two minutes. Check whether the alarm recovers.
N --> Go to 2. Replace AISG device
2. Replace AISG device
Wait for two minutes and check whether the alarm recovers.
198084209
Description
Severity
Cause
Handling
process
AISG flash erase error

Minor
Parameter error
N --> Go to 2. Replace AISG device.
173
198084210
Description
Severity
Cause
Handling
process
AISG flash error

Minor
Parameter error
N --> Go to 2. Replace AISG device.
198084211
Description
Severity
Cause
Handling
process
AISG other hardware error

Minor
Parameter error
N --> Go to 2.Replace AISG device.
198084212
Description
Severity
Cause
Handling
process
AISG other software error

Minor
Parameter error
174

198084213
Description
Severity
Cause
Handling
process
AISG RAM error

Minor
Parameter error
198084214
Description
Severity
Cause
Handling
process
AISG UART error

Minor
Parameter error
175
198084215
Description
Severity
Cause
Handling
process
RET motor fault

Major
RET motor fault
1. Please adjust device again.
N --> Go to 2. Please install RET motor again and adjust
2. Please install RET motor again and adjust.
N --> Go to 3. Replace RET motor.
3. Replace RET motor
198084216
Description
Severity
Cause
Handling
process
RET motor can't adjust

Major
RET motor can't adjust
198084217
Description
Severity
176
RET motor don't response the adjusting command

Minor
Cause
Handling
process
RET motor don't response the adjusting command

N --> Go to 2. Please install RET motor again and adjust.
198084218
Description
Severity
Cause
Handling
process
RET don't calibrated

Major
RET don't calibrated
N --> Go to 2. Please restart device.
2. Please restart device
N --> Go to 3. Checked configure file and antenna type is
consistent
3. Checked configure file and antenna type is consistent. If not
then send right configure data to device.
N --> Go to 4.Please install RET motor again and adjust.
4. Please install RET motor again and adjust
N --> Go to 5.Replace RET motor.
177

198084219
Description
Severity
Cause
Handling
process
RET data don't scaled

Major
RET data don't scaled
1. Checked device data is abnormal.
Y --> Go to 2. Send right configure data to device
N --> Go to 3. Replace Ret motor
2. Send right configure data to device
198084220
Description
Severity
Cause
Handling
process
RET position lost

Minor
RET position lost
N --> Go to 2.Please install RET motor again and adjust.
N --> Go to 3.Replace RET motor.
178
198084221
Description
Severity
Cause
Handling
process
ATMA minor alarm

Minor
ATMA minor fault
2. Replace AISG device.
198084222
Description
Severity
Cause
Handling
process
ATMA major alarm

Major
ATMA major fault
198084223
Description
Severity
ACOM minor alarm

Minor
179
Cause
Handling
process
ACOM minor fault

198084224
Description
Severity
Cause
Handling
process
ACOM major alarm

Major
ACOM major fault
N --> Go to 2.Replace AISG device
198084225
Description
Severity
Cause
Handling
process
PA_License permission limit

Major
This alarm notification may be given if the sum of all cells
transmission power output on the board which to create the cell
is larger than the PA_License was set.
1. Check configure data.
Send config-data to station on Operation System, and PA
license selection open.
Y --> Go to 2. Check Cell TX Power.
N --> Go to 2. Check Cell TX Power.
2. Check Cell TX Power.
180
Check the sum of all cells transmission power output on the

board.
198084226
Description
Severity
Cause
Handling
process
Subcard fault is detected

Major
Subcard is broken.
1. Check whether the subcard is broken.
Y --> Go to2. Replace the subcard
2. Replace the subcard
Check whether the alarm recovers
198084227
Description
Severity
Cause
Handling
process
Configuration IMA group failure

Major
IUB port already exists, parameter is wrong, or both ends of IMA
group parameters are not configured consistently.
i.


recovers.
181
198084228
Description
Severity
Cause
Handling
process
IpVlan Configure Failed

Major
The configured parameters mistake.
i.
Upload Node B configuration data through O&M system.

N --> Go to ii. Change wrong configuration data.

According to real situation, change the configuration data,
182
198084229
Description
Severity
Cause
Handling
process
Power alarm
Critical
Power occur error!
None
198084230
Description
Severity
Cause
Ir link LCV (line code violation) alarm

Notification
1. Poor fiber connection.
2. Optical module defect.
3. Ir interface chipset work abnormally.
Handling
process
1. Check whether the fiber is connected well.

Check the fiber connection and check whether the alarm still
exists.
Y --> Go to 2 Replace the optical module.
2. Replace the optical module.
Replace the optical module and check whether the alarm still
exists.
Y --> Go to 3 Reset the RRU.
3. Reset the RRU.
Reset the RRU and check whether the alarm still exists.
Y --> Go to 4 Replace the RRU.
4. Replace the RRU.
Replace the RRU and check whether the alarm still exists.
198084231
Description
RRU clock frequency drift
183
Severity
Cause
Notification
1. RRU local oscillator aged, the initial frequency drifts too
much.
2. BBU's local clock frequency drifts too much.
Handling
process
1. Check whether there has the same alarm in RRU under the
same BBU.
If it is, then BBU clock is broken. Try to replace the BBU
clock board, and check whether the alarm recovers.
N --> Go to 2. Reset the RRU.
2. Reset the RRU.
Reset the RRU and check whether the alarm recovers.
N --> Go to 3. Replace the RRU.
3. Replace the RRU.
Replace the RRU and check whether the alarm recovers.
198084232
Description
Severity
Cause
Digital power abnormal

Major
1. Logical cell is closed.
2. Fiber transport is disconnected instantaneously.
3. Ir interface or BRIC chip is abnormal.
Handling
process
1. Check the fiber

i.
Check whether the fiber is connected well.

Y --> Go to ii. Please replace the fiber or fix it.
N --> Go to iii. Check whether the alarm recovers.
ii. Please replace the fiber or fix it, and check whether the
alarm recovers.
N --> Go to 2. Check whether the clock is degraded in
CCI.
iii. Check whether the alarm recovers
184
N --> Go to 2. Check whether the clock is degraded in

CCI.
2. Check whether the clock is degraded in CCI
Y --> Go to 3. Please replace the CCI board
N --> Go to i. Check whether the alarm recovers
i.

3. Please replace the CCI board

Replace the CCI board, and check whether the alarm
recovers.
198084233
Description
Severity
Cause
Digital PA over power alarm

Minor
1. When CPU detects the output power of digital PA exceeds
rated power by 2dbm will report this alarm.
2. When intermediate frequency FPGA detects the output power
of PA exceeds rated power by 2.5dbm will report this alarm
by CPU.
3. Not the same with PA over power alarm, when Digital PA
recovers, Digital PA over power alarm will recover.
Handling
process
1. Check if there has PA over power alarm at the same time.

Y->Yes, look up the handle of alarm 3000(PA over power
alarm).
N->No, ignore this alarm.
198084234
Description
Severity
Cause
Handling
process
PA Run Failed alarm

Major
PA is defected.
1. Check if the PA is turned on.
Check if the PA status is "RUNNING"
Y->Yes, skip to "2.Replace the RRU"
185
N->No, turn on the PA and check if the alarm is recovered. If

not recovered, please contact ZTE
2. Replace the RRU.
Replace the fault RRU; Check if the alarm is recovered.
N->Alarm is not recovered, please contact ZTE
198084235
Description
Severity
Cause
Handling
process
Ir signal of port 0 lost

Major
The fiber loose or broken, or the optical module is damaged.
1. Check the fiber.
Check if the fiber looses. If so, connect the fiber and check if
Y->Yes, end alarm process.
N->No, skip to "2.Check if the fiber is damaged."
2. Check if the fiber is damaged.
If the fiber is damaged, replace it and check if the alarm is
recovered.
N->No, skip to "3.Check if the optical module broken."
3. Check if the optical module broken.
If the optical module broken, replace it and check if the
alarm is recovered.
N->No, please contact ZTE
198084236
Description
Severity
Cause
Ir link FIFO abnormal

Warning
1. RRU clock does not synchronize to the BBU clock.
2. RRU local clock defected.
Handling
process
1. Check if there are more than one RRU under the same BBU
having this alarm at almost the same time.
Y->Yes, check if the BBU clock board has any alarm of clock.
186
N->No, skip to "2.Check if the RRU PLLs are all in LOCK

status"
2. Check if the RRU PLLs are all in LOCK status.
Y->Yes, skip to "3.Replace the RRU."
N->No, please contact ZTE.
3. Replace the RRU.
Replace the RRU, check if the alarm is recovered.
198084237
Description
Severity
Cause
RRU RTWP abnormal

Minor
1. Poor antenna connection, or Feeder/Jumper defect.
2. LNA defect.
3. RRU internal poor connection.
4. RRU internal receiver circuit defect.
Handling
process
1. Check the antenna connection, or replace the defective

Feeder/Jumper defect, check if the alarm is recovered.
N->No, skip to "2. Reset the RRU."
2. Reset the RRU.
Reset the RRU, check if the alarm is recovered.
N->No, skip to "3. Replace the RRU."
3. Replace the RRU.
Replace the RRU, check if the alarm is recovered.
198084238
Description
Severity
Cause
Frame SeqNo Failed

Critical
1. FPGA timesyn on UBPG board transfer failed or timesyn clock
failed;
187
2. Frame terminate clock failed.

Handling
process
1. Check whether UBPG exists 61.44M clock alarm

Y->Exist, jump to "3 Reboot Board"
N->Not exist, jump to"2 check CC exists 61.44M clock alarm"
2. Check CC exists 61.44M clock alarm
Y->exist, jump to"3 Reboot Board"
N->not exist, reboot UBPG, then reboot CC, jump to"3
Reboot Board:"
3. Reboot Board
Reboot board, wait for 2 minutes,judge whether the alarm is
resumed.
Y->resume, end.
N->not resume, jump to"4.change board"
4. Change board
Change the board, wait for 2 minutes, judge whether the
alarm is resumed.
Y->resume, end.
N->not resume, please contact ZTE
198084239
Description
Severity
Cause
HardWare TimeSlot Terminate Failed

Critical
1. FPGA software vertion is abnormal.
2. UBPG 61.44M clock failed.
Handling
process
1. Change FPGA software

Change FPGA software, judge whether the alarm is resumed.
Y->resumed, end.
N->not resumed, jump to "2.Reboot Board"
2. Reboot Board
Reboot board, wait for 2 minutes, judge whether the alarm is
resumed.
Y->resume, end.
3. change board
alarm is resumed.
188
Y->resume, end.
198084240
Description
Severity
Cause
AIF Interface Failed

Critical
1. FPGA abnormal
2. DSP abnormal
Handling
process
1. Reboot Board
resumed.
Y->resume, end.
2. change board
alarm is resumed.
Y->resume, end.
198084241
Description
Severity
Cause
Handling
process
Out RAM Read/Write Failed

Minor
UBPG board is failed.
1. Reboot Board
resumed.
Y->resume, end.
2. change board
alarm is resumed.
Y->resume, end.
189
198084242
Description
Severity
Cause
Dsp watchdog overflow

Critical
1. DSP software vertion is abnormal
2. UBPG board is failed.
Handling
process
1. Check whether the alarm is reported frequently.

Y->yes, jump to"2 change DSP software"
N->no, the signal is outware, can resume byself.
2. Change Dsp software
Change Dsp software, judge whether the alarm is resumed.
Y->resume, end.
N->not resume, jump to "3.Reboot Board"
3. Reboot Board
resumed.
Y->resume, end.
4. change board
alarm is resumed.
Y->resume, end.
198084243
Description
Severity
Cause
Uplink Trx 60ms Abnormal

Critical
1. FS board is abnormal.
2. Link between BBU and RRU failed.
3. RRU board is abnormal.
Handling
process
1. Check the FD link.

i.
Check the FD link is normal.

Y->normal, jump to"2 check rru board is normal"
N->abnormal, link FD again, jump to"2judge whether
the alarm is resumed"
ii. Judge whether the alarm is resumed
190
Y->resumed, end.
N->not resume, jump to"2 check rru board is normal"
2. Check rru board is normal
i.
Check whether rru board is normal.

Y->normal, jump to"3 check FS board is normal".
N->abnormal, jump to"2) process rru board abnormal"
ii. process rru board abnormal

Resolve board fault, judge whether the alarm is resumed.
Y->resumed, end.
N->not resumed, jump to"3 check FS board is normal"
3. Check FS board is normal
i.
Check FS board is normal

Y->normal, jump to"4 reboot UBPG board"
N->abnormal, jump to"2) process FS board Fault"
ii. Process FS board Fault

Resolve board fault, judge the alarm is resumed.
Y->resumed, end.
N->not resumed,jump to"4 reboot UBPG board"
4. Reboot UBPG board
Reboot UBPG board, judge whether the alarm is resumed.
Y->resumed, end.
N->not resumed, jump to"5 reboot rru board"
5. Reboot rru board
reboot rru board, judge the alarm is resumed.
Y->resumed, end.
N->not resumed, jump to"6 reboot FS board"
6. Reboot FS board
reboot FS board, judge the alarm is resumed.
Y->resumed, end.
N->not resumed, jump to"7 Change UBPG board"
7. Change UBPG board
Change UBPG board, judge whether the alarm is resumed.
Y->resumed, end.
N->not resumed, jump to"8 Change rru board"
8. Change rru board
Change rru board, judge whether the alarm is resumed.
191
Y->resumed, end.
N->not resumed, jump to"9 change FS board"
9. Change FS board
Change FS board, judge whether the alarm is resumed.
Y->resumed, end.
N->not resumed, please contact ZTE
198084244
Description
Severity
Cause
Software Load Abnormal

Critical
1. Dsp or FPGA software vertion is abnormal
2. UBPG board is failed.
Handling
process
1. Change DSP/FPGA software

Change DSP/FPGA software, judge whether the alarm is
resumed.
Y->resumed, end.
2. Reboot Board
resumed.
Y->resume, end.
3. Change board
alarm is resumed.
Y->resume, end.
198084245
Description
Severity
Cause
Handling
process
Physical param not consistent with radio param

Critical
OMCR parameter is not consistent with OMCB parameter.
1. Check whether OMCR and OMCB parameter is consistent with
each other
Y->not consistent, synchronize OMCR and OMCB parameters,
end.
192
N->consistent, jump to "2.Reboot Board"

2. Reboot Board
resumed.
Y->resume, end.
N->not resume, jump to "4.change board"
3. Change board
alarm is resumed.
Y->resume, end.
198084246
Description
Severity
Cause
Handling
process
Radio param error

Critical
OMCR radio param configuration error.
1. Check OMCR parameters
Y->abnormal, modify parameter configuration, end.
N->normal, jump to "2.delete TRX/Sector, Add again"
2. Delete TRX/Sector, Add again
Judge whether alarm is resumed.
Y->resumed, end.
3. Reboot Board
resumed.
Y->resume, end.
4. Change board
alarm is resumed.
Y->resume, end.
193
198084247
Description
Severity
Cause
Link3 of BUC software not response

Minor
1. BUC software runs abnormally.
2. Link between CC and BUC failed.
Handling
process
1. Check link
Y->abnormal, jump to link fail process.
N->normal, jump to "2 Reboot Board"
2. Reboot Board
reboot board, wait for 2 minutes, judge whether the alarm is
resumed.
Y->resume, end.
3. Change board
alarm is resumed.
Y->resume, end.
198084248
Description
Severity
Cause
Handling
process
Dsp software on UBPG not response

Critical
DSP software runs abnormally.
Judge whether the alarm is resumed.
Y->resumed, end.
2. Reboot Board
resumed.
Y->resume, end.
3. Change board
alarm is resumed.
194
Y->resume, end.
198084249
Description
Severity
Cause
Handling
process
DBB param response error

Minor
DSP software runs abnormally.
judge whether the alarm is resumed.
Y->resumed, end.
2. Reboot Board
resumed.
Y->resume, end.
3. Change board
change the board, wait for 2 minutes, judge whether the
alarm is resumed.
Y->resume, end.
198084250
Description
Severity
Cause
Handling
process
IQ Config Failed
Critical
Peripheral board or hardware failed.
1. check whether other boards exist alarm.
Y->exist, end.
N->not exist, jump to "2.Reboot Board"
2. Reboot Board
resumed.
Y->resume, end.
3. Change board
195

alarm is resumed.
Y->resume, end.
198084251
Description
Severity
Cause
IPTB Setup Link Failed

Critical
1. Software runs abnormally.
2. Board failed.
Handling
process
1. Change CC software
Change CC software, judge whether the alarm is resumed.
Y->resumed, end.
2. Reboot Board
resumed.
Y->resume, end.
3. Change board
alarm is resumed.
Y->resume, end.
198084252
Description
Severity
Cause
Require Radio Param timeout for times

Minor
1. OMCR had not param.
2. SCTP link failed.
Handling
process
1. Change CC software
Change CC software, judge whether the alarm is resumed.
Y->resumed, end.
2. Reboot Board
196

resumed.
Y->resume, end.
3. Change board
alarm is resumed.
Y->resume, end.
198084253
Description
Severity
Cause
Handling
process
Emac Interface Error Control face

Critical
Emac interface lost data
1. Reboot Board
resumed.
Y->resume, end.
2. Change board
alarm is resumed.
Y->resume, end.
198084254
Description
Severity
Cause
Emac Interface Error User face

Critical
1. Transmit error
2. Microcode processed error
Handling
process
1. Check link way

Check link between BSC and CC.
Y->ok, jump to "2.Reboot Board".
N->not ok, fix it, end.
2. Reboot Board
197

resumed.
Y->resume, end.
3. Change board
alarm is resumed.
Y->resume, end.
198084255
Description
Severity
Cause
Handling
process
E1T1 sliding code

None
1. Check if there is software version fault alarm.
i.
Check if the fault board has corresponding software

version fault alarm.
Y->Yes, skip to "2) handle software version fault alarm".
N->No, skip to "2 Reset board".
ii. Handle software version fault alarm

According to suggestions on handling software version
fault alarm, remove this alarm. Check if the alarm is
recovered.
Y->Yes, end alarm processing.
2. Reset board
Reset the fault board and wait for 2 minutes. Check is the
alarm is recovered.
N->No, skip to "3 Replace board".
3. Replace board
Replace the fault board, wait for 2 minutes, check if the
alarm is recovered.
N-> No, Please contact ZTE.
198
198084256
Description
Severity
Cause
Handling
process
GPS receiver alarm

Critical
Antenna problem or GPS receiver broken
i.

Y->Yes, skip to "ii. handle software version fault alarm".

recovered.
N->No, skip to "2 Check if GPS antenna is connected
normally".
2. Check antenna
i.
Check if GPS antenna is connected normally.

Y->Normal connection
N->Not connected or antenna is broken
ii. Connect or replace antenna. Then check if the alarm is

recovered.
3. Reset board
alarm is recovered.
N-> No, skip to "4.Replace board".
4. Replace board
alarm is recovered.
199
198084257
Description
Severity
Cause
Handling
process
UL IQ abnormal
Minor
Data from FS has CRC error.
Unplug and plug the board; if the alarm isn't recovered, unplug
and plug FS board; if it doesn't work, then replace BPC board.
198084258
Description
Severity
Intra-board network port error

none
Cause
Data packets received from DSP is not continuous, packets may

be lost
Handling
process
Intra-board network port has a problem, please replace the

board.
198084259
Description
Severity
Cause
Handling
process
UL buffer is used up
Critical
Data received from DSP cannot be saved because memory is
used up.
Reset board
198084260
Description
Severity
Cause
Handling
process
HDLC link has CRC alarm

Minor
RRU signaling data over optical fiber has CRC error
Unplug and plug corresponding optical fiber; if the alarm isn't
recovered, unplug and plug FS board; if it doesn't work, then
replace FS board.
198084261
Description
200
The received frame number is not continuous
Severity
Cause
Handling
process
None
The frame number sent from RRU is not continuous.
Unplug and plug optical fiber, or do nothing.
198084262
Description
Severity
Cause
Handling
process
TDM CRC alarm

Minor
TDM channel between FS and BPC has CRC error
If the alarm lasts for more than 1 minute, please unplug and
plug the board; if the alarm isn't recovered, unplug and plug the
corresponding BPC board; if it doesn't work, then replace FS
board.
198084263
Description
Severity
Cause
Handling
process
RRU LOS alarm

Critical
The corresponding RRU has detected LOS error.
Check if the corresponding optical fiber is normally connected.
Unplug and plug the optical fiber. If the alarm isn't recovered,
check the RRU and try to solve the problem.
198084264
Description
Severity
Cause
Handling
process
RRU LOF alarm

Critical
The corresponding RRU has detected LOF error.
Check if the corresponding optical fiber is normally connected.
Unplug and plug the optical fiber. If the alarm isn't recovered,
check the RRU and try to solve the problem.
198084265
Description
Severity
Cause
RRU powered-down alarm

Critical
The corresponding RRU is powered down.
201
Handling
process
Check the status of RRU
198084266
Description
Severity
Cause
Handling
process
Clock has a critical alarm

Critical
Clock reference source is lost.
i.

Y->Yes, skip to "2) handle software version fault alarm".

recovered.
N->No, skip to "2 Check the configured clock reference
source is connected or not".
2. Check if the configured clock reference source is connected
or not
Y-> Yes, skip to "3 Reset board".
N-> No, connect clock reference source.
3. Reset board
alarm is recovered.
Y-> Yes,end alarm processing.
N-> No, skip to "4. Replace board".
4. Replace board
alarm is recovered.
N->No, Please contact ZTE.
202
198084267
Description
Severity
Cause
Handling
process
Clock minor alarm

Minor
Clock reference source is unlocked.
i.

Y->Yes, skip to ii handle software version fault alarm".

recovered.
2. Reset board
alarm is recovered.
N->No, skip to "3. Replace board".
3. Replace board
alarm is recovered.
N->No, Please contact ZTE.
198084268
Description
Severity
Cause
IQ delay compensation value exceeds limitation

Minor
1. The fiber of the farther RRUs at Low or Mid carrier is longer
for 56km than that of the nearer RRU at the same carrier in
OTSR cell.
2. The fiber of the farther RRUs at High carrier is longer for
28km than that of the nearer RRU at high carrier in OTSR cell.
Handling
process
1. Adjust the location of RRU;

2. Change the topology structure.
203
198084269
Description
Severity
Cause
Handling
process
MAC address conflict

None
Another board/host on the network has the same MAC address.
1. Find the board/host which has the same MAC address.
2. Change the
board/host.
conflict
MAC
address
or
disconnect
the
3. Check if this alarm is recovered.

198084270
Description
Severity
Cause
Handling
process
IP address conflict
None
Another board/host on the network has the same IP address.
1. Find the board/host which has the same IP address.
2. Change the conflict IP address or disconnect the board/host.
3. Check if this alarm is recovered.
198084271
Description
Severity
Cause
Ethernet light and electricity lose

Major
1. Network cable fault;
2. Remote network port fault;
3. Local network port fault;
Handling
process
1. Check if network cable is connected normally.

Please check if the network cable has the following problems:
i.

Please solve the above problem if there is any. After that,
please check if the alarm is recovered.
204
Y->Alarm process ends.

N->Skip to "2 Check if local network port is abnormal".
2. Check if local network port is abnormal.
i.
Check if local network port is abnormal.

Use a good network cable to directly connect the alarm
network port and another network port. Check if the
alarm is recovered:
Alarm is recovered, which indicates remote network port
has a fault, skip to "3 Process the fault of remote network
port".
Alarm is not recovered, which indicates local network port
has a fault, skip to "2) Process the fault of local interface
board".

Note: Resetting or replacing the interface board will
cause interruption of all services carried by the board,
therefore, please choose appropriate time to reset or
replace it.
Reset the fault interface board. After successful booting,
please check if the alarm is recovered.
Alarm is recovered, alarm process ends.
Alarm is not recovered, which indicates interface board
has a hardware fault, skip to "iii Replace fault interface
board".
iii. Replace fault interface board.
Replace the interface board. Wait until the board has
finished booting and RUN light flashes normally (in 1Hz
frequency). Query the alarm status of the corresponding
board and check if the original alarm still exists.
Y->Yes, please contact ZTE.
N->The original alarm disappears, alarm process ends.
3. Process the fault of remote network port.
Please try to remove the fault of remote device, this alarm
process ends.
198084272
Description
Severity
Cause
Lightning arrester alarm at indoor lightning protection box

Minor
1. Lightning arrester has a fault, including broken by lightning
stroke, poor grounding, aging failure.
2. Dry contact connection or configuration is abnormal.
205
Handling
process
1. Check the alarm-related polarity configuration.

2. Make sure dry contact is normally connected, lightning
arrester is well grounded.
3. If the above is OK, it means lightning arrester is broken. In
this case, lightning protection box needs be replaced.
198084273
Description
Severity
Cause
Circuit breaker alarm at indoor lightning protection box

Major
1. Circuit breaker is in the state of overcurrent-protection or
open-circuit
2. Dry contact connection or configuration is abnormal
Handling
process

2. Make sure dry contact is normally connected.
3. Check the switch of circuit breaker to find out the reason for
overcurrent protection or open circuit. Try to remove the
fault.
198084274
Description
Severity
Cause
Outdoor lightning protection box alarm

Minor
1. Lightning arrester has a fault, including broken by lightning
stroke, poor grounding, aging failure.
2. Dry contact connection or configuration is abnormal.
Handling
process

2. Make sure dry contact is normally connected, lightning
arrester is well grounded.
3. If the above is OK, it means lightning arrester is broken. In
this case, lightning protection box needs be replaced.
198084275
Description
Severity
Cause
Handling
process
206
Failed to download software

Critical
Link error or board fault
i.
Check if there is associated software version fault alarm.
Y->Yes, skip to ii. Process software version fault alarm

N->No, skip to 2 Reset the board.
fault alarm, try to remove the alarm. Check if the alarm
is recovered.
N->Alarm is not recovered, skip to 2 Reset the board.
2. Reset the board.
Reset the fault board; wait for 2 minutes; check if the alarm
is recovered.
N->Alarm is not recovered, skip to 3. Replace the board.
Replace the fault board; wait for 2 minutes; check if the
alarm is recovered.
N->Alarm is not recovered, please contact ZTE.
198084276
Description
Severity
Cause
Handling
process
Downlink DAC PLL unlock

Major
If the FuncID of RTR is 0, the chip AD9779 is unlocked. If the
FuncID of RTR is 1, the chip AD9788 is unlocked.
1. Reset RRU.
2. Change RRU.
198084277
Description
Severity
Cause
PTP link interruption

Minor
1. FE link is interrupted.
2. Peer-end doesn't support IP clock.
Handling
process
1. Check if there is a "FE link interruption" alarm.

If yes, please follow relevant suggestion to deal with it. Wait
for 1 minute after "FE link interruption" fault is solved, then
check if the alarm is recovered or not.
207

N->No, skip to "2.Check if peer-end supports IP clock or not"
2. Check if peer-end supports IP clock or not.
If not, please select other clock reference source. Then check
if the alarm is recovered or not.
Y->Yes, end alarm processing
N->No, Please contact ZTE
198084278
Description
Severity
Cause
Handling
process
RRU delay too long

Minor
RRU delay exceeds its limit.
1. Check if fixed delay of local cell is configured properly or not.
Y-> Yes, skip to "2. Reset RRU"
N-> No, skip to "3. Reconfigure fixed delay of local cell"
2. Reset RRU, and check if the alarm is recovered.
N->No, skip to "4. Replace optical fiber with a shorter one"
3. Reconfigure fixed delay of local cell, then check if the alarm
is recovered.
N-> No, skip to "4. Replace optical fiber with a shorter one"
4. Replace optical fiber with a shorter one, then check is the
alarm is recovered.
198084279
Description
Severity
Cause
Handling
process
Cell delay too long

Minor
Cell delay too long
1. Check if fixed delay of local cell is configured properly or not.
Y-> Yes, skip to "2. Reset corresponding RRU"
N-> No, skip to "3. Reconfigure fixed delay of local cell"
208
2. Reset corresponding
recovered.
RRU, and
check
if
the
alarm
is

N->No, skip to "4. replace optical fiber of corresponding
RRU"
3. Reconfigure fixed delay of local cell, then check if the alarm
is recovered.
N-> No, skip to "4. Replace optical fiber of corresponding
RRU"
4. Replace optical fiber of corresponding RRU, then check isfthe
alarm is recovered.
198084280
Description
Severity
Cause
Handling
process
Write MDB and DBS failure

Critical
Database operation error
1. Check transmission link.
Check if CC and BSC's transmission link is normal or not.
Y-->Yes, skip to "2. Reset board"
N-->No, repair the link, and end alarm processing.
2. Reset board
Reset fault board, wait for 2 minutes, then check if the alarm
is recovered.
N->No, skip to "3. Replace board".
3. Replace board
Replace fault board, wait for 2 minutes, then check if the
alarm is recovered.
198084281
Description
Lack of RRU resource
209
Severity
Cause
Handling
process
Critical
Lack of RRU resource
1. Reset board
Reset fault board, wait for 2 minutes, then check if the alarm
is recovered.
N->No, skip to "2. Replace board"
2. Replace board
Replace fault board, wait for 2 minutes, then check if the
alarm is recovered.
198084282
Description
Severity
Cause
Lost of frame number at optical port

Minor
1. Optical module is not on-duty
2. Frame number received via optical port is lost.
Handling
process
1. Check if optical module is normal or not (Is optical module

installed? Is optical fiber connected?)
Y->Yes, Skip to 2.
N-> If there is no optical fiber or optical module, this alarm
is normal.
2. Check FS board in BBU is normal or not.
198084283
Description
Severity
Cause
Lost of frame rate and frame number

Minor
1. Frame number is discontinuous.
2. There is no frame rate received within 160ms.
Handling
process
1. Check if softlock is normal or not.

Y->skip to 2.
N-> Please refer to relevant suggestion to deal with softlock
unlocking problem.
2. Check if FS board in BBU is normal or not.
210
198084284
Description
Severity
PM under-voltage alarm
Major
Cause
An under-voltage alarm is reported when power output is lower

than 40 V; this alarm is recovered when power output returns to
42 V.
Handling
process
1. Please make sure power supply is well connected when this

alarm occurs. Is the alarm recovered?
N->No, skip to "2.Replace power supply board".
2. Replace power supply board
Wait until the board enters normal state, and check if the
alarm recovered.
198084285
Description
Severity
PM over-voltage alarm
Major
Cause
An over-voltage alarm is reported when power output is higher

than 58 V; this alarm is recovered when power output returns to
56 V.
Handling
process
1. Please make sure power supply is well connected when this

alarm occurs. Is the alarm recovered?
N->No, skip to "2.Replace power supply board".
2. Replace power supply board
Wait until the board enters normal state, and check if the
alarm recovered.
198084286
Description
PWR monitoring unit alarm
211
Severity
Cause
Handling
process
Minor
PW monitoring unit is broken.
1. Check and remove the fault of PWR monitoring unit; then
check if the alarm is recovered or not.
198084287
Description
Severity
Cause
Handling
process
AC power-cut alarm
Minor
AC power is cut, or there is no AC input due to other problems.
1. Quick find a method to restore AC power, or adopt gasoline
generator in emergency.
Y-> The alarm is recovered, end alarm processing.
N-> The alarm is not recovered, Please contact ZTE.
198084288
Description
Severity
Cause
Handling
process
Battery in low-voltage alarm

Minor
The voltage of the battery is too low.
1. Quick find a method to recharge the battery, and wait for the
voltage restores to normal level.
198084289
Description
Severity
Cause
Handling
process
Rectifier alarm
Minor
The rectifier works abnormally.
1. Replace the rectifier, then check if the alarm is recovered or
not.
212
198084290
Description
Severity
Cause
Handling
process
ETH port mode is unmatched with peer end

Minor
The configured mode of network port is unmatched with peer
end.
1. Check if the Ethernet has LOS alarm or not.
i.
Check if the Ethernet has LOS alarm or not.

Y-> Yes, skip to "ii Process the LOS fault"
N-> No, skip to "2 Check the mode of network port at
peer end"
ii. Process the LOS fault

According to relevant suggestions for Ethernet LOS fault,
try to remove the fault. Then check if the alarm is
recovered or not.
N-> No, skip to "2 Check the mode of network port at
peer end".
2. Check the mode of network port at peer end.
Check the mode of network port at peer end; change the
mode of local network port so that it is matched with peer
end. Then check if the alarm is recovered or not.
N-> No, skip to "3. Reset single board"
3. Reset single board
Reset single board and wait for 2 minutes; check if the alarm
is recovered or not.
N-> No, skip to "4.Replace single board".
4. Replace single board
Replace the fault board and wait for 2 minutes; check if the
213
214
Appendix
Abbreviations
Abbreviation
Full Name
A
AFS
Adaptive Full-Rate Speech
AGND
Analog Ground
AHS
Adaptive Half-Rate Speech
ANT
Antenna
B
BBU
Base Band Unit
BCCH
Broadcast Control Channel
BNC
Bayonet Nut Connector
BSC
Base Station Controller
BSS
Base Station Subsystem
BTS
Base Transceiver Station
C
CIB
CTU Interface Board
CM
Configuration Management
CPRI
Common Public Radio Interface
CS
Control & Switch Board
CTU
Control Translation Unit
D
DCHP
Dual -carrier Channel Processor
DCMM
Dual -carrier Controller & Maintenance Module
DDT
Delay Diversity Transmission
DFCA
Dynamic Frequency and Channel Allocation
DGND
Digital Ground
DPCT
Dual Power Combining Transmission
DTX
Discontinuous Transmission
215
Abbreviation
Full Name
E
EDGE
Enhanced Data Rates for GSM Evolution
EFS
Enhanced Full Rate Speech
EGSM900
Enhanced Global System for Mobile

Communications
F
FAQ
Frequently Asked Questions
FCLK
Frame Clock
FPGA
Field Programmable Gate Array
FS
Fiber Switch Board
G
GERAN
GSM/EDGE Radio Access Network
GMSK
Gaussian Filtered Minimum Shifting Keying
GND
Ground
GPRS
General Packet Radio Service
GSM
Global System for Mobile Communications
H
HDLC
High Level Data Link Controller
HEATER
Heater
HSDPA
High Speed Downlink Packet Access
HSUPA
High Speed Uplink Packet Access
HW
High Way Line
I
IP
Internet Protocol
IRC
Interference Rejection Combining
L
LAPD
Link Access Procedure on the D-channel
LAPDm
Link Access Procedure Dmmobile D

Channel
LAU
Low noise Amplifier Unit
LMT
Local Maintenance Terminal
LNA
Low Noise Amplifier
LTE
Long Term Evolution
LVDS
Low Voltage Differential Signal
216
MAC
Media Access Control
MM
Mobility Management
Appendix A - Abbreviations
Abbreviation
Full Name
MMI
Man-Machine Interface
MS
Mobile Station
MTBF
Mean Time Between Failures
MTTR
Mean Time To Repair
O
OAM
Operation/Administration & Maintenance
P
PA
Power Amplifier
PBCCH
Packet Broadcast Control Channel
PC
Personal Computer
PCM
Pulse Code Modulation
PDH
Plesiochronous Digital Hierarchy
PDM
Power Distribution Module
PE
Protective Earth
PGND
Protective Ground
PLMN
Public Land Mobile Network
PRACH
Packet Random Access Channel
PS
Packet Switch
PTCCH
Packet Timing advance Control Channel
PWR
Power
R
RLC
Radio Link Control
RR
Radio Resource management
RRU
Remote Radio Unit
RST
Reset
RX
Receiver
RXD
Receiver for diversity
S
SDCCH
Separate Dedicated Control Channel
SDH
Synchronous Digital Hierarchy
SDR
Software Defined Radio
SWR
Standing Wave Ratio
SYNC
Synchronous Communication
T
TA
Tower Amplifier
TCH
Traffic Channel
217
Abbreviation
Full Name
TDM
Time Division Multiplexing
TDMA
Time Division Multiple Access
TRAU
Transcoding and Rate Adaptation Unit
TRX
Transceiver Board
TS
Time Slot
TX
Transmitter
V
VSWR
218
Voltage Standing Wave Ratio

ZXSDR BS8900 GU360 (V4.00) Outdoor GSM&amp;UMTS Dual Mode Macro Node B Alarm Code Reference

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

ZXSDR BS8900 GU360 (V4.00) Outdoor GSM&amp;UMTS Dual Mode Macro Node B Alarm Code Reference

Caricato da

Copyright:

Formati disponibili

ZXSDR BS8900 GU360

Outdoor GSM&UMTS Dual Mode Macro Node B

Alarm Code Reference

Reason for Issue

Make it more concise/brief

Improve the Contents

Add more step-by-step procedures/tutorials

Improve the organization

Add more troubleshooting information

Include more figures

Make it less technical

Add more examples

Add more/better quick reference aids

Add more detail

Improve the index

This page is intentionally blank.

Declaration of RoHS Compliance..................................... v

198084126 ...................................................................... 113

198084204 ...................................................................... 171

198084282 ...................................................................... 210

Appendix A ................................................................... 215

This page is intentionally blank.

About This Manual

Prerequisite Skill and Knowledge

ZXSDR system and its various components

User interfaces on the Mobile Switching Center (MSC)

Local operating procedures

What Is in This Manual

Introduces the basic concepts and terms of

Chapter 2, Alarm Code

Introduces the definition, cause and

Confidential and Proprietary Information of ZTE CORPORATION

ZXSDR BS8900 GU360 Alarm Code Reference

Lists all the abbreviations used in the