SJ-20100603155704-004-ZXWR RNC (V3.09.30) Alarm and Notification Handling Reference - 331818

ZXWR RNC
Radio Network Controller
Alarm and Notification Handling Reference

Version:V3.09.30
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: (86) 755 26771900
Fax: (86) 755 26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2010 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No.
Revision Date
Revision Reason
R1.0
20100609
First Edition (V3.09.30.03)
R2.0
20100915
Second Edition (V3.09.30.06)
R3.0
20110226
Third Edition (V3.09.30.09)
Serial Number: SJ-20100603155704-004

Publishing Date: 2011-02-26(R3.0)
Contents
About This Manual ......................................................................................... I
Chapter 1 Overview .................................................................................... 1-1
1.1 Overview of Fault Management........................................................................... 1-1
1.2 Alarm Code........................................................................................................ 1-1
1.3 Alarm Type ........................................................................................................ 1-1
1.4 Alarm Classification ............................................................................................ 1-2
1.4.1 Alarm ...................................................................................................... 1-2
1.4.2 Notification............................................................................................... 1-2
1.5 Severity ............................................................................................................. 1-2
1.6 Probable Cause ................................................................................................. 1-3
1.7 Handling Suggestion .......................................................................................... 1-3
1.8 Alarm Impact ..................................................................................................... 1-3
Chapter 2 Alarm.......................................................................................... 2-1

2.1 Equipment Alarm................................................................................................ 2-1
2.1.1 198083003 Log server is offline alarm ....................................................... 2-1
2.1.2 198083027 RSVB Offline alarm................................................................. 2-2
2.1.3 198019456 HSSLS are all out of synchronization ....................................... 2-3
2.1.4 198019465 CSIX RX and TX packets is abnormal ...................................... 2-4
2.1.5 198005633 Hard Disk Broken ................................................................... 2-5
2.1.6 198005635 The board is not plugged firmly................................................ 2-6
2.1.7 198005639 High Error Rate of Optical Interface ......................................... 2-7
2.1.8 198005640 FPGA Exception ..................................................................... 2-8
2.1.9 198005644 The Channel in a Subcard Is Down.......................................... 2-9
2.1.10 198005645 Subcard Abnormal .............................................................. 2-10
2.1.11 198005646 Phase-lock Loop Unlock .......................................................2-11
2.1.12 198005647 High Error Rate at E1 Bottom Layer ..................................... 2-12
2.1.13 198005656 Loss of Clock When Input to Sub-card.................................. 2-13
2.1.14 198005663 Board device is abnormal .................................................... 2-14
2.1.15 198000256 Ethernet Controller's Physical Link Off.................................. 2-15
2.1.16 198001284 Clock Phase Does not Match When Inputting 8k, 16M Clock
to Backboard. ....................................................................................... 2-16
2.1.17 198001286 Loss of Clock When Input to Board ...................................... 2-17
2.1.18 198000002 Loss of Optical Transceiver Module Signal ........................... 2-18
2.1.19 198001792 SDH/SONET fault ............................................................... 2-19

2.1.20 198001026 Cell delineation do not synchronization about cell on E1
link....................................................................................................... 2-21
2.1.21 198015874 Physical channel for data transmission blocked .................... 2-22
2.1.22 198015875 GLI table lookup failed ........................................................ 2-23
2.1.23 198015876 GLI exception packets statistic over threshold....................... 2-24
2.1.24 198002560 The usage of CPU is over the threshold ............................... 2-25
2.1.25 198002561 CPU temperature over threshold.......................................... 2-26
2.1.26 198005376 Internal Port of Board Is Down ............................................. 2-27
2.1.27 198066070 Board Doesn't Exist/ CPU is in Reset Status for a Long
Time..................................................................................................... 2-28
2.1.28 198005381 Input clock is abnormal........................................................ 2-29
2.1.29 198005389 A (CPU) Subcard Is Online, but Is not Configured in
Database.............................................................................................. 2-30
2.1.30 198005390 A (CPU) Subcard Is not Online, but Has Been Configured
by Database. ........................................................................................ 2-31
2.1.31 198005395 External Port of Board Is Down ............................................ 2-32
2.1.32 198005396 Test packet of internal media plane is abnormal .................... 2-33
2.1.33 198005399 DSP resource is unavailable................................................ 2-34
2.1.34 198026116 CLKG PP2S Output Clock Lost ............................................ 2-36
2.1.35 198026117 PP2S clock reference lost.................................................... 2-37
2.1.36 198026118 16CHIP clock reference lost................................................. 2-37
2.1.37 198026127 Clock reference source lost (Level 3 alarm) .......................... 2-38
2.1.40 198026131 CLKG board PLL out-of-lock................................................ 2-41
2.1.41 198026133 Output clock lost ................................................................. 2-42
2.1.42 198005632 Usage rate of board hard disk above threshold ..................... 2-43
2.1.43 198005637 Error in Rear Board That Mismatches With Front Board ........ 2-44
2.1.44 198005661 Physical link down between master/slave media interactive
ports .................................................................................................... 2-45
2.1.45 198005662 IDE running overtime .......................................................... 2-46
2.1.46 198005667 E1 line is loop-line............................................................... 2-47
2.1.47 198005671 Incorrect FE Routing Connection ......................................... 2-47
2.1.48 198005668 Self board has cross-linked E1 ............................................ 2-49
2.1.49 198005655 DSP Reports Exceptions After Detection .............................. 2-50
2.1.50 198019712 APS channel mismatched ................................................... 2-50
2.1.51 198019713 APS mode mismatched....................................................... 2-52
II
2.1.52 198019714 Conflicting between APS configuration and board backup

mode ................................................................................................... 2-53
2.1.53 198005121 Inter-shelf media plane links abnormal ................................. 2-54
2.1.54 198005124 Capacity of intra-shelf control plane TRUNK communication
is insufficient......................................................................................... 2-55
2.1.55 198005125 Incorrect Connection of GE Optical Transceiver Module ........ 2-57
2.1.56 198025602 Half-fixed connection error................................................... 2-58
2.1.57 198005665 Fault on board (GPS) ......................................................... 2-58
2.1.58 198005650 Conflicted MAC addresses of boards on the same shelf ........ 2-60
2.1.59 198005405 Clock board phase-lock loop work mode abnormal................ 2-61
2.1.60 198005404 Board OCXO oven fault....................................................... 2-62
2.1.61 198005403 Board SRAM self-check fails ............................................... 2-62
2.1.62 198001825 High BER on SDH / Sonet link ............................................. 2-63
2.1.63 198001027 ATM link is down................................................................. 2-64
2.1.64 198030208 Fault alarm of CFM ............................................................. 2-66
2.1.65 198029952 802.3ah link fault ................................................................ 2-67
2.1.66 198015882 GLI buffer allocate fail ......................................................... 2-69
2.1.67 198015881 GLI port transmit error ......................................................... 2-70
2.1.68 198015880 GLI board host and ME communication error ........................ 2-71
2.1.69 198015879 GLI Port receive error.......................................................... 2-71
2.1.70 198015878 GLI internal fabric port receive error ..................................... 2-72
2.1.71 198015877 GLIQV SRAM/DRAM error .................................................. 2-73
2.1.72 198005893 Memory check failed ........................................................... 2-74
2.1.73 198005673 Backboard switch set is changed ......................................... 2-75
2.1.74 198005672 Synchronization Ethernet clock source is unusable ............... 2-76
2.1.75 198005670 Oscillator status abnormal ................................................... 2-77
2.1.76 198005669 Synchronization status check of FPGA failed ........................ 2-77
2.2 Communication Alarm ...................................................................................... 2-78
2.2.1 198083021 CCP link fault alarm .............................................................. 2-78
2.2.2 198083036 DSAR Alarm......................................................................... 2-79
2.2.3 198022784 BFD Session Interrupted ....................................................... 2-81
2.2.4 198066029 PPP link broken.................................................................... 2-83
2.2.5 198019213 LIF Alarm of Near-End Receiving Link.................................... 2-84
2.2.6 198019214 LODS Alarm of Near-End Receiving Link ............................... 2-85
2.2.7 198019215 RDI alarm of far end receiving link ......................................... 2-87
2.2.8 198019223 Ne Group is in fault state....................................................... 2-88
2.2.9 198066026 Association path broken ........................................................ 2-88
III
2.2.10 198005666 The number of the error packets from MAC port exceeds
the threshold......................................................................................... 2-90
2.2.11 198015617 Faulty Frames Received by FE/GE/ATM/MP/POS/E1 Port ..... 2-91
2.2.12 198015873 Faulty frames received by internal switching interface ........... 2-92
2.2.13 198005378 Board HW Error .................................................................. 2-93
2.2.14 198005651 IPMAC conflict when OSS detects control plane ................... 2-94
2.2.15 198066003 Control plane communication is abnormal between board
and its home module ............................................................................. 2-95
2.2.16 198066004 Control plane communication is abnormal between MP and
OMP .................................................................................................... 2-96
2.2.17 198005382 Communication between power board and OMP board is
abnormal .............................................................................................. 2-97
2.2.18 198005397 Communication of RAWMACIP channel is abnormal ............. 2-98
2.2.19 198005401 Test packet check abnormal ................................................ 2-99
2.2.20 198005122 Communication Link between Active and Standby Boards
Off ......................................................................................................2-100
2.2.21 198005126 Incorrect FE Routing Connection ........................................2-101
2.2.22 198005128 Duplicate rack and shelf .....................................................2-102
2.2.23 198066005 SCCP subsystem unavailable.............................................2-103
2.2.24 198066007 Broadband link overload.....................................................2-105
2.2.25 198066010 MTP3 office inaccessible ....................................................2-106
2.2.26 198066011 MTP3 link unavailable ........................................................2-106
2.2.27 198066014 M3UA office inaccessible ...................................................2-108
2.2.28 198066019 Association link broken.......................................................2-109
2.2.29 198083045 Common Channel setup failed Alarm .................................. 2-110
2.2.30 198083048 Transport Path Occupied Bandwidth Overload..................... 2-112
2.2.31 198083049 Transport Path group Occupied Bandwidth Overload ........... 2-113
2.2.32 198083050 IP channel of Iub interface is faulty...................................... 2-114
2.2.33 198066067 AAL2 Path remotely blocked............................................... 2-114
2.2.34 198066068 AAL2 Path blocked by broken PVC ..................................... 2-115
2.2.35 198066071 All SSCOP links in an IMA group broken ............................. 2-116
2.2.36 198394014 Control plane communication interrupted for a long time or
high frequency between board and its home module .............................. 2-117
2.2.37 198000519 Trunk error ........................................................................ 2-118
2.2.38 198000520 Trunk abnormal ................................................................. 2-119
2.2.39 198003841 The control plane retransfer ratio over the threshold.............2-120
2.2.40 198005127 FE Link Error Alarm ...........................................................2-121
2.2.41 198005129 Ethernet port loop back error ..............................................2-122
IV
2.2.42 198015618 Faulty frames received by port over threshold......................2-123

2.2.43 198029953 The Ethernet port state is OAM loop back ...........................2-124
2.2.44 198066066 AAL2 Path locally blocked ..................................................2-125
2.3 Processing Alarm ............................................................................................2-125
2.3.1 198083020 Token control overload alarm................................................2-125
2.3.2 198083022 Cell is out of service.............................................................2-126
2.3.3 198083023 Node B is out of service .......................................................2-129
2.3.4 198083024 GPS receiver on ICM is abnormal .........................................2-130
2.3.5 198018944 PVC CC timeout ..................................................................2-131
2.3.6 198019207 Near-End IMA Group Configuration Failure ...........................2-132
2.3.7 198015360 Microcode Is Abnormal ........................................................2-133
2.3.8 198023040 The number of board alarms exceeds the threshold ...............2-134
2.3.9 198066031 The number of OMP alarms exceeds the threshold ................2-135
2.3.10 198066032 NTP time exceeds threshold...............................................2-135
2.3.11 198066027 SNTP failure ......................................................................2-136
2.3.12 198005387 Alarm Due to Inconsistent MP Type ....................................2-138
2.3.13 198005388 Startup File Does Not Exist.................................................2-138
2.3.14 198005398 Inconsistent Office ID Settings of DIP Switch .......................2-139
2.3.15 198005649 Port Work Mode Doesn't Match Settings..............................2-140
2.3.16 198005123 DB Configuration Doesn't Fit for Device...............................2-142
2.3.17 198066006 Broadband link congestion .................................................2-143
2.3.18 198066013 MTP3 link congestion.........................................................2-144
2.3.19 198066018 Association congestion.......................................................2-145
2.3.20 198005402 Database config is different from file named bootcfg.ini ........2-146
2.4 Environment Alarm..........................................................................................2-147
2.4.1 198025856 Rack temperature is higher than high threshold .....................2-147
2.4.2 198025857 Rack temperature is lower than low threshold........................2-148
2.4.3 198025858 House temperature is higher than high threshold ..................2-149
2.4.4 198025859 House temperature is lower than low threshold .....................2-150
2.4.5 198025860 Voltage is higher than high threshold.....................................2-151
2.4.6 198025861 Voltage is lower than low threshold .......................................2-152
2.4.7 198025862 Humidity is higher than high threshold...................................2-153
2.4.8 198025863 Humidity is lower than low threshold .....................................2-154
2.4.9 198025864 Fault in fan plug-in box.........................................................2-155
2.4.10 198025865 Rack door alarm ................................................................2-155
2.4.11 198025866 Smog alarm .......................................................................2-156
2.4.12 198025867 Infrared alarm ....................................................................2-157
2.4.13 198025868 Lightning alarm ..................................................................2-158

2.4.14 198025869 Loss of DC power supply to rack.........................................2-159
2.5 QoS Alarm......................................................................................................2-160
2.5.1 198023296 Inter-board message communication flow rate exceeds the
alarm threshold ....................................................................................2-160
2.5.2 198066069 The number of times of signaling data transfer exceeds the
allowed threshold of the license ............................................................2-161
2.5.3 198083051 IU PS traffic over load alarm .................................................2-162
2.5.4 198083052 IU CS traffic over load alarm.................................................2-162
2.5.5 198083053 IU traffic over load alarm ......................................................2-163
2.5.6 198015361 Ring and queue overload alarm ............................................2-164
Chapter 3 Notification ................................................................................ 3-1

3.1 198083017 the route table of MicroCode subsystem of this board is overloaded ..... 3-3
3.2 198070002 Iu interface global reset notification .................................................... 3-4
3.3 198070003 Iu interface resource reset notification ................................................ 3-5
3.4 198070004 RNC started Iu interface global reset failure notification....................... 3-6
3.5 198070005 RNC started Iu interface resource reset failure notification................... 3-7
3.6 198070008 RNC and Node B CCPID configuration are not identical ...................... 3-8
3.7 198070009 Broadcast fail ................................................................................... 3-9
3.8 198083025 Common Channel is abnormal......................................................... 3-10
3.9 198070010 OMCR failed to fetch FTP file .......................................................... 3-12
3.10 198070011 File operation failure between OMCR and RNC NE ........................ 3-12
3.11 198083028 Logservice is unavailable............................................................... 3-13
3.12 198083029 Performance file store failed .......................................................... 3-14
3.13 198083019 MicroCode subsystem failed to get the table of configuration ........... 3-16
3.14 198083026 MicroCode subsystem failed to handle DHCP message from other
network.......................................................................................................... 3-18
3.15 198083030 Bandwidth automatic adjustment is useless .................................... 3-20
3.16 198083032 TCP connect on IuBC interface establishment failed. ...................... 3-21
3.17 198083033 Clock Deviation over threshold notification...................................... 3-22
3.18 198083034 External Clock of Slave lost notification .......................................... 3-23
3.19 198083037 All Local Cell ID configured at RNC side are differ from which on
Node B side ................................................................................................... 3-24
3.20 198020291 Protocol stack process failed to initialize during power on ................ 3-25
3.21 198020802 Conflicting IP addresses................................................................ 3-25
3.22 198020803 Conflicting MAC Addresses in Subnet ............................................ 3-27
3.23 198020804 Failed to generate static ARP from IP address ................................ 3-28
3.24 198030016 Ethernet link OAM event................................................................ 3-29
VI
3.25 198000576 Trunk Slide ................................................................................... 3-29

3.26 198001600 One of CPUs on One of Boards in This Shelf Resets
(Exceptionally)................................................................................................ 3-30
3.27 198017216 Error in MCS Multi-Core processor receiving configuration data
from DBS ....................................................................................................... 3-31
3.28 198018240 TCP Receives RST Packet............................................................ 3-32
3.29 198018241 TCP Connection Aborted............................................................... 3-33
3.30 198018242 MD5 Verification Failure ................................................................ 3-34
3.31 198018243 Wrong MD5 Message Abstract ...................................................... 3-34
3.32 198023106 Board self-check fails .................................................................... 3-35
3.33 198023107 The board initialization failure ........................................................ 3-36
3.34 198023617 Configuration file is unusable ......................................................... 3-37
3.35 198003138 FLASH device initialize failed......................................................... 3-38
3.36 198003394 Entering Daylight Savings Time ..................................................... 3-39
3.37 198003395 Quitting Daylight Savings Time ...................................................... 3-39
3.38 198005441 Port status on internal media plane changed................................... 3-40
3.39 198005448 485 Set Failure ............................................................................. 3-41
3.40 198026177 CLKG reference quality changed ................................................... 3-42
3.41 198026178 Clock work mode changed ............................................................ 3-43
3.42 198005705 MCU resets for abnormities ........................................................... 3-44
3.43 198005710 The result of base selection of sets chip ......................................... 3-44
3.44 198005711 The action of select base is working ............................................... 3-45
3.45 198005712 The manual select base will be run, please wait for the result .......... 3-46
3.46 198005713 APC's RAM error .......................................................................... 3-47
3.47 198005715 PP2S source switched .................................................................. 3-48
3.48 198005716 Type B fault on board (GPS) phase-lock equipment ........................ 3-48
3.49 198005700 DSP resets for abnormities ............................................................ 3-50
3.50 198005701 Version Load Error ........................................................................ 3-51
3.51 198019777 APS Switchover Happens.............................................................. 3-52
3.52 198005188 UIM CS Changeover ..................................................................... 3-53
3.53 198005192 Board's Work Mode Unsupported................................................... 3-54
3.54 198005193 Notification of the power-on status of the basic process................... 3-55
3.55 198005956 Board Version Error ...................................................................... 3-56
3.56 198005958 IDE Version Files Synchronization Information ................................ 3-57
3.57 198005961 OMP Version Check Information .................................................... 3-58
3.58 198005962 Patch version operate fail .............................................................. 3-59
3.59 198010560 No message response in the link for a long time ............................. 3-60
3.60 198011840 M3UA user office status change..................................................... 3-61
VII
3.61 198013888 ASP status changed ..................................................................... 3-62

3.62 198013889 AS status changed........................................................................ 3-63
3.63 198013890 Sigtran error message received ..................................................... 3-64
3.64 198013891 Sigtran notification message received ............................................ 3-65
3.65 198013892 Allocate memory fail...................................................................... 3-66
3.66 198014144 Association establishment failed .................................................... 3-67
3.67 198014145 Association restart ........................................................................ 3-68
3.68 198025664 Abnormal Half-fixed Connection Changes ...................................... 3-69
3.69 198008005 Memory file buffer overflow............................................................ 3-70
3.70 198083046 DSP memory check fail notification ................................................ 3-71
3.71 198083047 TCP connect on IuBC interface is interrupted ................................. 3-72
3.72 198015168 AAL2 Path blocked by resetting process......................................... 3-73
3.73 198020805 ARP detect failed .......................................................................... 3-74
3.74 198020806 ARP detect that the static ARP is not match ................................... 3-74
3.75 198026176 Clock reference changed............................................................... 3-75
3.76 198026179 Clock source invalidation reason changed ...................................... 3-76
3.77 198028993 SCTP Primary Path Set Failed....................................................... 3-77
3.78 198031040 ACL config failed .......................................................................... 3-78
3.79 198000834 MCC is faulty ................................................................................ 3-79
3.80 198002625 Process is deadlocked. ................................................................. 3-79
3.81 198002880 CPU dead-loop ............................................................................. 3-80
3.82 198003650 The data in user buffer is corrupted ................................................ 3-81
3.83 198005189 Notification of Active/Standby Changeover .................................... 3-82
3.84 198005195 Board mix plug occurred................................................................ 3-83
3.85 198005718 Two master clock ports is directly connected .................................. 3-84
3.86 198005719 FPGA receive/send packets abnormally ......................................... 3-85
Figures............................................................................................................. I
Tables ............................................................................................................ III
VIII
About This Manual

Manual Description
This manual is a handling reference for the ZXWR RNC alarms and notifications, it helps
users to analyze and handle the alarms and notifications reported on the NMS during the
operation of ZXWR RNC.
What Is in This Manual

Chapter
Summary
Chapter 1, Overview
Introduces the concepts and terms used in this manual.
Chapter 2, Alarm
Introduces the ZXWR RNC alarms.
Chapter 3, Notification
Introduces the ZXWR RNC notifications.
Target Group
l
l
l
EMS Engineer
Network Optimization Engineer
Testing Engineer
II
Chapter 1
Overview
Table of Contents
Overview of Fault Management ..................................................................................1-1
Alarm Code ................................................................................................................1-1
Alarm Type.................................................................................................................1-1
Alarm Classification....................................................................................................1-2
Severity ......................................................................................................................1-2
Probable Cause .........................................................................................................1-3
Handling Suggestion ..................................................................................................1-3
Alarm Impact ..............................................................................................................1-3
1.1 Overview of Fault Management

Fault management is responsible for collecting information of failures and events that occur
during system operation or service processing.
The information, in the form of alarm or notification, is stored in database or displayed
on realtime basis via a user-oriented fault monitoring platform. Means such as
visual-interface monitor or history information query can be used to view current or
historical system operation and service processing status. Fault management enables
maintenance personnel to troubleshoot and take preventive measures to remove potential
fault and restore system and services as early as possible.
1.2 Alarm Code

Alarm code is the identifier which differentiates alarms.
Alarm code is defined by a 32-bit field indicating the specific code value.
1.3 Alarm Type

Alarm is classified into six types according to alarm trigger condition and its system impact.
l
l
l
l
Equipment alarm: related with device hardware.

Communication alarm: related with information transmission (ITU-T
Recommendation X.733).
Processing alarm: related with software or process fault (ITU-T Recommendation
X.733).
Environment alarm: related with the environment where the equipment is located
(ITU-T Recommendation X.733).
1-1
SJ-20100603155704-004|2011-02-26(R3.0)
ZTE Proprietary and Confidential
ZXWR RNC Alarm and Notification Handling Reference
l
l
QoS alarm: related with degradation of service quality (ITU-T Recommendation

X.733).
OMS alarm: related with the network management system.
1.4 Alarm Classification

1.4.1 Alarm
The fault that persists during system operation and affects system reliability and normal
services is referred to as an alarm. Alarm usually lasts until fault removal.
Due to its possible impact on normal system operation, alarm requires timely
troubleshooting in which alarm cause is identified, and the fault is located and handled.
1.4.2 Notification
Notification refers to the non-repeated/instantaneous fault or event that occurs during
system operation. Examples include board reset, signaling overload, etc.
Notification is mostly caused by sudden environment change or other accidental factors.
No special handling is required for the notification, which can be automatically removed by
the system. Only the notification that occurs persistently requires troubleshooting.
1.5 Severity
There are five alarm severity levels, which are indicated in descending order of severity as
Critical, Major, Minor, Warning and Undefined.
l
l
l
l
Critical alarm causes system breakdown and service interruption. It requires

immediate troubleshooting.
Major alarm significantly affects system operation or weakens network service
capability. It requires troubleshooting as soon as possible.
Minor alarm affects system operation and network service capability in a
nonsignificant way. A timely troubleshooting is required to avoid severity escalation.
Warning alarm poses a potential hazard to system operation and network service
capability. It requires troubleshooting at an appropriate time so as to avoid severity
escalation.
Undefined alarm have the least impact on the system operation.
The degree of impact as described in the definition of alarm severity refers to the impact of
a single index, such as reliability and security. Once the impact on any of the index reaches
the specified threshold, the severity level of the alarm can be roughly determined. If an
alarm has an impact on multiple indices, alarm severity should be escalated accordingly.
1-2
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 1 Overview
Note
Alarm severity can be modified in NetNumen M31 NMS (network management system) if
necessary.
Generally speaking, the default alarm severity is reasonably set. Users should think twice
before making any modification.
In addition, the severity of few alarms is undefined. It is up to users to define the severity
of such alarms.
1.6 Probable Cause

Probable alarm causes are enumerated to help users troubleshoot, find preventive
measures, and restore the system to normal state in a timely manner.
1.7 Handling Suggestion

Troubleshooting measures and suggestions are provided.
Pay attention to the following tips when handling alarms.
l
After recording the fault phenomenon, O&M personnel may handle the fault step by
step as described in the Handling Suggestion Section of this manual. If the fault is
removed (alarm restored) at any handling step, terminate the handling process. If
the fault is not removed, go ahead to the next handling step.
If the fault cannot be removed, contact the local ZTE office as soon as possible.
1.8 Alarm Impact

Alarm impact refers to the impact that the alarm incurs on system or services.
1-3
SJ-20100603155704-004|2011-02-26(R3.0)
This page intentionally left blank.
1-4
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2
Alarm
Table of Contents
Equipment Alarm........................................................................................................2-1
Communication Alarm ..............................................................................................2-78
Processing Alarm ...................................................................................................2-125
Environment Alarm.................................................................................................2-147
QoS Alarm .............................................................................................................2-160
2.1 Equipment Alarm

2.1.1 198083003 Log server is offline alarm
Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm Classification
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. Log service is unavailable.
2. Communication between log server and RNC NE is faulty.
2-1
SJ-20100603155704-004|2011-02-26(R3.0)
Handling Suggestion
1. Check whether the control plane communication of the log server is normal The
checking method is as follows.
a. Open a terminal dialog box in the LINUX system.
b. Issue SHELL command of "ping 128.0.31.1" at terminal to see if ping operation is
successful. If no, troubleshoot communication fault in control plane.
2. Check whether the log service operation in log server is normal. If no, restart
log service. The checking method is as follows. Run "/startsys" under the
"/home/zte/LogService/bin" directory.
Alarm Impact
Log/performance files fail to be reported to the log server.
2.1.2 198083027 RSVB Offline alarm

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Critical
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. RSVB rear board of SBCX is manually unplugged from the slot.
2. RSVB board hardware is faulty.
3. RSVB board is not tightly inserted.
2-2
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Handling Suggestion
1. Check if RSVB board is manually unplugged. If yes, the alarm is certain to be declared.
Plug the RSVB board back into the slot. If no, unplug and plug RSVB board.
2. Replace RSVB board.
Alarm Impact
When the SBCX board which corresponds to the rear board is used as log server, OMM
will fail to fetch performance data from the log server.
2.1.3 198019456 HSSLS are all out of synchronization

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Critical
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. The PSN board type configured does not accord with the PSN board type actually in
use.
2. PSN board hardware (VSC882 chip) is faulty.
3. Line card hardware (VSC872/VSC874 chip) is faulty.
Handling Suggestion
1. Check whether PSN board reboots repeatedly. If yes, Check whether the PSN board
type configured is consistent with the PSN board type actually in use.
2-3
SJ-20100603155704-004|2011-02-26(R3.0)
a. If inconsistent (for example, the configured board type is PSN4V and the board
type actually in use is PSN8V), modify board type configuration or replace the
board actually in use to keep consistency between board configuration and the
board in use.
b. If consistent, PSN board hardware might be faulty. In this case, replace PSN
board.
2. If the alarm occurs in line card, check if the same alarm occurs in other line card(s)
located in the same shelf with the faulty line card.
a. If the same alarm occurs in all other line cards, PSN board might be faulty. Reboot
PSN board and check if the line card alarms are restored. If alarms are not
restored, replace PSN board.
b. If merely the line card where this alarm occurs reboots repeatedly, replace the
board where the alarm is generated.
Alarm Impact
1. All services on the equipment are down if the alarm is caused by Cause 1 or Cause 2.
2. All services on the line card are affected if the alarm is caused by Cause 3.
3. If the service is not configured in master/slave or load sharing mode, all services on
the line card will be down. If the service is configured in master/slave or load sharing
mode, all services on the line card will soon be restored after being down temporarily.
2.1.4 198019465 CSIX RX and TX packets is abnormal

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Warning
Disaster Alarm
No
Frequently Reported
No
2-4
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Probable Cause
1. Signal is unstable when rack or board is powering on.
2. Switch chip is abnormal.
Handling Suggestion
1. Reset the board.
2. Replace the board.
Alarm Impact
The transceiver of the media plane is exceptional.
2.1.5 198005633 Hard Disk Broken

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
There is failure in ribbon cable connection or the hard disk. This is usually a hardware
failure.
Handling Suggestion
Replace the hard disk on the board or replace the board.
2-5
SJ-20100603155704-004|2011-02-26(R3.0)
Alarm Impact
This alarm is dedicated to OMP only. Its system impact is:
1. Hard disk failure in ROMP start up may cause ROMP board start up failure and service
accessing failure.
2. Hard disk failure in the log server may cause data loss of the performance data stored
on the ROMP hard disk in the abnormal status.
3. When a peripheral board is starting up and requesting version from ROMP, Hard disk
failure may cause start up failure and power off of the peripheral board.
2.1.6 198005635 The board is not plugged firmly

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. The ENUM switch on the board is ON, or is not firmly connected.
2. Or the EXCH key on the standby board is pressed twice within 3 seconds.
Handling Suggestion
1. Check the ENUM switch and turn it on. If it is not turned on.
2. Switch off and switch on ENUM.
3. If the ENUM open status is simulated by pressing the EXCH key on the standby board
twice within 3 seconds, press the EXCH key on the standby board twice within 3
seconds.
2-6
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Alarm Impact
Cause failure in active/standby board switching, or cause failure in APS switching. Do not
switch this board into active board.
2.1.7 198005639 High Error Rate of Optical Interface

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
The fiber is not completed connected to the port, or is damaged, or is not compatible with
the optical transceiver module in T-network switch. There is no light signal input into the
optics module. This alarm is dedicated to the TDM optical port only. The possible causes
of this alarm include:
1. TDM receiver fiber optics failure, fiber optics module failure. This type of failures
include: damaged fiber on the receiver, unconnected fiber, contaminated fiber or
damaged optics module on the receiver.
2. Fiber optics failure at the transmitting module on the corresponding TDM. This
type of failures include: damaged fiber on the transmitter, unconnected fiber, and
contaminated fiber.
3. Compatibility between fiber optics and optics module. The fiber transmission rate of
TDM signal is incompatible with the wave length of the optics module.
4. Loss of signal(LOS) alarm operation is performed on the corresponding SDH device.
This includes the manual diagnosis test alarm operation.
2-7
SJ-20100603155704-004|2011-02-26(R3.0)
Handling Suggestion
1. Perform loopback test to determine source of this alarm is on the local devices or the
corresponding devices. Perform self-loop test on local device. If the failure persists,
the failure source is on local device; if the failure disappears after self-loop test, then
the source of failure is on the corresponding device. Contact the corresponding device
for solution.
2. Replace optics module.
3. Replace the fiber optics.
Alarm Impact
There might be error in the data transmitted by the optical port which affects the quality of
all the services performed on this optical port.
2.1.8 198005640 FPGA Exception

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
FPGA runs abnormally, for example, FPGA is lost, or the board clock is lost.
Handling Suggestion
1. Restart the board. In this case, the board downloads FPGA again.
2-8
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Alarm Impact
FPGA verification fails. The read and write function of FPGA cannot be ensured. The
board cannot provide complete functions and work normally. The service carried by the
board is interrupted.
2.1.9 198005644 The Channel in a Subcard Is Down

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. The sub-card is not inserted in position.
2. The sub-card has hardware faults.
Handling Suggestion
1. Unplug and plug the sub-card again. Wait for the board to be powered on.
2. Replace the sub-card.
Alarm Impact
The sub-card channel is not initialized or the initialization fails. As a result, the channel
corresponding to the alarm chip cannot be used normally. This affects the service carried
by the board of the sub-card. After the channel is available and the alarm is eliminated,
the service is recovered.
2-9
SJ-20100603155704-004|2011-02-26(R3.0)
2.1.10 198005645 Subcard Abnormal

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. The GCS sub-card of UIMC/GUIM/CHUB is not inserted in position.
2. The sub-card is faulty.
Handling Suggestion
1. Check the sub-card connection on the board. If the sub-card is loosely inserted, tightly
insert it and wait for the board to be powered on.
Alarm Impact
UIMC/GUIM/CHUB GCS sub-card functions abnormally. Packets may be lost, and
even worse, link disconnection may occur on the control planes of some boards. For
active/standby configuration, there are two cases:
1. If the active board is abnormal while the standby board is normal, the system performs
active/standby switchover. Thus, the standby board takes over the services of the
faulty active board. In this case, the service is not affected.
2. If both the active and standby boards are abnormal, active/standby switchover is
forbidden. In this case, the service is interrupted because the faulty board cannot
restore to the normal status.
2-10
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
2.1.11 198005646 Phase-lock Loop Unlock

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Critical
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. The clock extraction reference is changed, including the case that the clock output is
closed by the interface board when optical port is faulty. This leads to the change of
clock board input. Or, configuration is modified at NMS and a new optical port is used
to extract the clock.
2. The change in input of clock board results in the change in output.
3. UIMC/GUIM input is disconnected, or UIMC/GUIM clock phase loop is abnormal.
4. The board lock phase loop has hardware faults.
Handling Suggestion
1. On NMS fault management interface, check if the related clock alarm occur. If yes,
handle the alarm by referring to the corresponding suggestions.
Related alarm:
198005381 Input Clock Abnormal
2. On NMS fault management interface, check if related alarms occur on the optical
port for clock extraction. If yes, handle the alarm by referring to the corresponding
suggestions.
Related alarms:
l
198001792 SDH/SONET fault

2-11
SJ-20100603155704-004|2011-02-26(R3.0)
l
l
l
198066047 Abnormal status in SDH/SONET

198005639 High Error Rate of Optical Interface
198000002 Loss of Optical Transceiver Module Signal
3. Check the operation and maintenance logs. If the operation of changing the
clock extraction reference for the loop is recorded, report the alarm as a normal
phenomenon. In this case, no handling operation is required.
4. Switch to the standby clock board.
5. Switch to the standby UIM/GUIM board.
Alarm Impact
The service clock and system clock are inconsistent on the board with unlocked phase-lock
loop. As a result, the service carried by the board is interrupted.
2.1.12 198005647 High Error Rate at E1 Bottom Layer

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
1. The E1/T1 link is faulty.
2. The device in the uplink direction of the trunk link is faulty.
3. The trunk cable or connector is in poor contact.
2-12
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Handling Suggestion
1. Conduct a meter measurement or loopback test to find out whether the alarm is rooted
in the local end or peer end.
l Meter measurement: Connect a trunk test meter to check if the signal received
by the local end trunk is normal. If yes, the fault is rooted in the local end. If the
test shows the problem persists, the fault is rooted in the peer end. In this case,
inform the peer end to troubleshoot.
l Loopback test: Perform self-loop at the trunk where alarm occurs at local end.
If the problem persists, it indicates that the fault is rooted in the local end. If the
alarm is eliminated, it indicates that the alarm is rooted in the peer end. In this
case, inform the peer end to troubleshoot.
2. Replace the trunk cable.
Alarm Impact
The trunk fails to receive trunk signals. If the belonged port has only this link, all services
on the port are interrupted. Otherwise, only the port bandwidth is affected. The quantity
of upper layer access services associated with the port is decreased. The accessed
bandwidth is reduced. The service, however, is not interrupted.
2.1.13 198005656 Loss of Clock When Input to Sub-card

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
2-13
SJ-20100603155704-004|2011-02-26(R3.0)
Probable Cause
1. The sub-card is not inserted in position.
2. The clock circuit of the sub-card is damaged.
3. The clock circuit of the mother board is damaged.
Handling Suggestion
1. Check the sub-card connection status. If the sub-card is loose, tightly connect it and
power it on again.
Alarm Impact
The unavailable sub-card clock affects the normal operation of the board. This may cause
clock jittering, and the service that implements media stream exchange through this board
becomes unstable. In the most serious case, the system clock is lost and the service
carried by the board is interrupted.
2.1.14 198005663 Board device is abnormal

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
The board device or sub-card is working abnormally.
2-14
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Handling Suggestion
Replace the board.
Alarm Impact
This alarm only occurs on IMAB board. When this fault occurs, IMAB board cannot work
normally and the trunk link that the board bears is broken. As a result, users cannot gain
access and the ongoing service is interrupted.
2.1.15 198000256 Ethernet Controller's Physical Link Off

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
1. No network cable is connected with Network Port OMC2 on rear board.
2. Network port on the board is faulty.
Network cable is disconnected or cable connector is loose.
3.
Handling Suggestion
1. Ensure that network cable is connected to Network Port OMC2.
2. Unplug and plug the network cable on Network Port OMC2 Of OMP board.
3. Check if OMC2 network cable works normally. If no, replace the cable.
2-15
SJ-20100603155704-004|2011-02-26(R3.0)
Alarm Impact
Master/slave switching will occur if OMP (ROMB board) is configured in master/slave
mode. If master/slave switching is normal, system will not be affected. If master/slave
switching is abnormal, OMP board will fail to obtain version package from NMS, leading
to board power-on failure, UE access failure, and interruption of ongoing services.
2.1.16 198001284 Clock Phase Does not Match When Inputting 8k,
16M Clock to Backboard.
Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
1. Clock cable is broken or cable connection is incorrect.
2. Clock board is faulty.
Handling Suggestion
1. Check the clock input cable at the shelf. Ensure that the cable is intact and properly
inserted.
2. Switch clock board.
3. Switch UIM/GUIM board.
4. Replace board.
2-16
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Alarm Impact
System synchronization fails and board operation is abnormal, leading to UE access failure
and interruption of board services.
2.1.17 198001286 Loss of Clock When Input to Board

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. The board is not in place (not properly inserted) in the slot.
2. Clock cable is disconnected.
3. Clock cable is faulty.
4. Board is faulty.
Handling Suggestion
1. Check if the clock (input) cable at the shelf is intact and properly connected.
2. Check if the following alarm occurs in the board. If yes, refer to the corresponding
alarm handling suggestion.
Related alarm:
198005635 The board is not plugged firmly
3. Replace board.
2-17
SJ-20100603155704-004|2011-02-26(R3.0)
Alarm Impact
The board fails to synchronize with system clock and fails to work normally, leading to UE
access failure and interruption of board services.
2.1.18 198000002 Loss of Optical Transceiver Module Signal

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
1. The receiving optical fiber/module of local equipment is faulty.
Receiving optical fiber is faulty or disconnected.
Optical connector is polluted.
Receiving optical module is faulty.
2. The transmitting optical fiber of opposite equipment is faulty.
Transmitting optical fiber is faulty or disconnected.
3. The receiving optical power at local end is excessively low.
Optical power attenuation on the receiving fiber transmission line at local end is too
much.
Transmitting optical power at opposite end is too low.
4. Operation of LOS insertion is performed at opposite end.
2-18
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Manual operation of LOS insertion is performed in diagnostic test, and optical module
is shutdown by force.
5. Optical fiber and optical module is incompatible.
The fiber transmission rate and the optical module wavelength are incompatible.
Handling Suggestion
1. Carry out loop test to determine whether the alarm is caused by local end or opposite
end. Perform fiber self-loop at local equipment. If the alarm persists, fault might lie in
local equipment. If the alarm disappears, inform the opposite end to troubleshoot.
2. Replace the optical module.
3. Replace fiber.
4. Replace board.
Alarm Impact
The optical interface fails to work normally. If the optical interface is configured with APS
protection, service will be switched to protection optical interface. Otherwise, all services
on the optical interface will be down.
2.1.19 198001792 SDH/SONET fault

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

3. Replace optical fiber.
2-20
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
4. Replace board.
Alarm Impact
SDH/SONET fails to work normally, leading to UE access failure on SDH/SONET and
interruption of ongoing services.
2.1.20 198001026 Cell delineation do not synchronization about

cell on E1 link
Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. Cell Header HEC (Header Error Check) is damaged, leading to cell location failure in
physical layer frame.
2. The alarm is caused by bottom layer fault. Cell HEC is handled differently at local end
and opposite end.
Handling Suggestion
1. Check if the following alarm occurs in the board. If yes, refer to the corresponding
Related alarms:
l
l
198066045 Trunk error

198066046 Trunk abnormal
2-21
SJ-20100603155704-004|2011-02-26(R3.0)
2. On NMS configuration management interface, check if SDH/SONET mode is

configured for both ends. Ensure that the configuration at both ends is consistent.
l Meter Measurement
Use a trunk test meter to test whether the trunk receiving signals at local end are
normal. If normal, fault might lie in local equipment. If abnormal, troubleshoot at
opposite end.
l
Loop Test
Perform self-loop at local trunk. If the alarm persists, fault might lie in local
equipment. If the alarm disappears, inform the opposite end to troubleshoot.
4. Replace trunk cable.

5. Replace board.
Alarm Impact
Data reception on E1 link is abnormal. If merely one E1 link is available for the port, all
services on the board will be down. Otherwise, port bandwidth will be affected, leading
to decreased access bandwidth. The number of successful upper-layer service access
related to the port will decrease, but service interruption will not occur.
2.1.21 198015874 Physical channel for data transmission blocked

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
2-22
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Probable Cause
1. The traffic flow to the board is excessive.
2. The PSN board in the same shelf is abnormal.
3. The board has hardware faults.
Handling Suggestion
1. On NMS fault management interface, check if the PSN in the same shelf has generated
related alarms. If yes, follow the suggestions on handling the related alarms.
Related alarm:
198019456 All high-speed links between line card and package switching board are
out of synchronism
2. Unplug and plug the board.
Alarm Impact
The services carried by the board are unstable. In most serious case, all services carried
by the board are interrupted.
2.1.22 198015875 GLI table lookup failed

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
2-23
SJ-20100603155704-004|2011-02-26(R3.0)
Probable Cause
1. L1 table or L2 table error.
2. Destination IP of packets or hardware is error.
Handling Suggestion
Switch the master port to the partner board.
Alarm Impact
Packets would be dropped which would cause poor voice quality and other problems.
2.1.23 198015876 GLI exception packets statistic over threshold

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. Connection between fiber and optic modules is not perfect.
2. Something wrong with fiber optic module.
3. Board hardware error.
Handling Suggestion
1. Check the connection between fiber and optic modules.
2. Reboot the board.
2-24
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Alarm Impact
2.1.24 198002560 The usage of CPU is over the threshold

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

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

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
2-27
SJ-20100603155704-004|2011-02-26(R3.0)
Probable Cause
1. Physical failure of the IC at the internal port on the board.
2. Failure of local board connecting port on the switching IC of UIM.
3. Backplane wiring failure of the local slot to UIM.
4. CUP overloaded on the first level switching board, UIM board at the shelf, or local
board.
5. Service over the rated capability of the board.
Handling Suggestion
1. Check the Alarm Management window for the CUP overloaded on the first level
switching board, UIM board at the shelf, or local board. Perform recommended
solution to process the alarm(s) if any.
Related alarm:
198002560 Board CPU Overloaded
2. Check the Alarm Management window for the alarms of Inter-shelf media plane links
abnormal. Perform the recommended solution to process the alarm(s) if any.
Related alarm:
198005121 Inter-shelf Media Plane Link Error
4. Change the slot of the board.
5. Replace the UIM in the same shelf.
Alarm Impact
When this port is not available for internal media stream transmission, the internal media
stream will select other normal ports for transmission. If all the internal ports fail to operate
normally, the internal media stream will be interrupted and all the services provided on this
board will be interrupted.
2.1.27 198066070 Board Doesn't Exist/ CPU is in Reset Status for

a Long Time
Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
2-28
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Alarm
Severity
Major
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
1. Board not properly positioned.
2. Hardware failure.
Handling Suggestion
1. Check for the proper placing of the board, and insert the board firmly if it is nor properly
placed.
2. Plug/unplug the board.
4. Replace the slot.
Alarm Impact
If the board is operational, and the alarm is board position failure, it does not affect the
service operation. The board is in blocked status, and no service by this board is available.
If the board with alarm is resource board, then the resource is not available on this board.
2.1.28 198005381 Input clock is abnormal

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
2-29
SJ-20100603155704-004|2011-02-26(R3.0)
Severity
Critical
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
1. The clock does not stay the working state.
2. The base of the clock does not input to the clock board.
3. The base of the clock is abnormal.
Handling Suggestion
1. Reconnect the cable between the board and the clock reference(Upper-level clock
source).
2. Replace the cable between the board and the clock reference.
3. Check the signal output from the reference clock source.
Alarm Impact
System services is interrupted as no proper clock information is provided to the system.
2.1.29 198005389 A (CPU) Subcard Is Online, but Is not Configured

in Database.
Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Warning
2-30
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. Configuration is incorrect.
2. Board is misplaced.
Handling Suggestion
Check if the subcard is needed. If not, unplug the subcard. If yes, configure board type
into the one that supports the subcard.
Alarm Impact
Since the board where the unconfigured subcard is located resets repeatedly, power
resource of the equipment is wasted. Service is not affected.
2.1.30 198005390 A (CPU) Subcard Is not Online, but Has Been

Configured by Database.
Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
2-31
SJ-20100603155704-004|2011-02-26(R3.0)
Probable Cause
1. Configuration error.
2. The Board plugged is incorrect.
Handling Suggestion
Check whether the sub-card is required. If this sub-card is not required, modify the board
type as none sub-card board; If the sub-card is required, plug the sub-card firmly.
Alarm Impact
The sub-card not operational. This board does not support this sub-card, and the impact of
this error is subject to actual functions of the board. If the sub-card is an interface board,
then the transmission link on this board is not connectable, and the service will access
through other sub-card; If the sub-card is a signaling processor board, then the cell/Node
B on this board is not available for service; If the sub-card is a users panel, then the user
plane processing capability will decline and the service will access through other sub-card.
2.1.31 198005395 External Port of Board Is Down

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. The port cable is not properly connected, or is not connected.
2. The IC of external board port is faulty.
2-32
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
3. The corresponding board is faulty.
Handling Suggestion
1. Reconnect or replace the cable.
3. Check the peer end port of the faulty port for possible failure.
Alarm Impact
This port is not available for the service. If there is a back for this port, then data
communicate through the back port, but the total communication rate will decline. Also
the reliability and stability of the system declines too. If there is no back for this port, then
all the office communication links through this port will not be available, and the services
through this port are not available.
2.1.32 198005396 Test packet of internal media plane is abnormal

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. Physical failure of the IC at the internal port on the board.
2. Failure of local board connecting port on the switching IC of UIM.
3. Backplane wiring failure of local slot to UIM.
2-33
SJ-20100603155704-004|2011-02-26(R3.0)
4. CPU overloaded on the first level switching board, UIM board at the shelf, or local
board.
5. Service overloaded the rated capability of the board.
Handling Suggestion
Related alarm:
198005376 internal media plane port failure.
2. Check the Alarm Management window for the CUP overloaded on the first level
switching board, UIM board at the shelf, or local board. Perform recommended
solution to process the alarm(s) if any.
Related alarm:
198002560 Board CPU Overloaded
Related alarm:
198005121 Inter-shelf Media Plane Link Error
5. Change the slot of the board.
Alarm Impact
l
l
l
In the case of the internal media plane stream processing failure of the board, and
packet loss occurs, the service provided by this board might become unstable.
In the case of port failure of connector failure, the internal media plane is completely
interrupted, and none of the services provided by this board is available.
If the alarm source is CPU overload, or service overloaded, services provided by this
board may be delayed, or interrupted under serious conditions.
2.1.33 198005399 DSP resource is unavailable

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
2-34
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
This alarm indicates the DSP resource is not available. It is monitored by higher level layer,
and is reported once DSP is blocked, the report conditions include:
1. DSP version loaded failure, system is unable to operate normally.
2. HPI port error on DSP.
3. DSP media plane communication failure.
4. DSP reset.
Handling Suggestion
1. Check the operation maintenance log files in network manager for the operations of
DSP version replacing. If there is operation of DSP version replacing which would
cause DSP reset, then the alarm does not require procession, the DSP will resume
operational after the resetting.
2. There is a DSP index in the detailed information of the alarm. Open the rack map on
the Configuration Management interface, select Board, right click and select Subunit
Configuration. Select the DSP with alarm, and click Status at Subunit Configuration
> Status Attribute > Query Status. Then check if the Management Status of DSP
is Blocked. If it is Blocked, it means the alarm is a normal consequence of manually
blocking the DSP. Open the rack map on the Configuration Management interface,
select Board, right click and select Subunit. Run Unblock DSP to resume DSP
operation.
3. Check the Alarm Management window for the corresponding alarms. Perform the
recommended solution to process the alarm, if any.
Related alarms:
l
l
l
198005701 Failure in Version Loading of DSP, Firmware, Microcode and Single

Board Computer
198005655 DSP Reports Exceptions After Detection
198005700 DSP resets for error
2-35
SJ-20100603155704-004|2011-02-26(R3.0)
4. Reset the board.

Alarm Impact
All the services performed on this DSP is interrupted, and those services will be re-created
on other normal DSPs. The long period absence of this DSP might cause decline to the
performance of the system.
2.1.34 198026116 CLKG PP2S Output Clock Lost

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
Hardware is faulty.
Handling Suggestion
1. If the alarm is declared by master board rather than slave board, perform master/slave
switching.
2. Replace the board where the alarm is declared.
Alarm Impact
l
If this alarm occurs to master clock board, the system will fail to get clock, leading
to processing failure of clock-related boards and interruption of board services.
2-36
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Relevant boards include IMA protocol processing board and the interface board
capable of HW processing.
If this alarm occurs to slave board, service will not be affected.
2.1.35 198026117 PP2S clock reference lost

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
Hardware is faulty.
Handling Suggestion
Replace the board.
Alarm Impact
System could not get the needed clock, which will cause processing abnormity related to
the clock.
2.1.36 198026118 16CHIP clock reference lost

Alarm Type
Equipment Alarm
2-37
SJ-20100603155704-004|2011-02-26(R3.0)
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
Hardware is faulty.
Handling Suggestion
Replace the board.
Alarm Impact
the clock.
2.1.37 198026127 Clock reference source lost (Level 3 alarm)

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
2-38
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Disaster Alarm
No
Frequently Reported
No
Probable Cause
Input clock reference is in unavailable status for no more than 10 minutes. Probable causes
include:
1. Clock reference input is abnormal.
2. The configured clock reference does not exist.
Handling Suggestion
1. Reconnect the input clock reference.
2. For the clock reference not in use, delete the corresponding "Circuitry Clock
Reference" configuration on NMS configuration management interface (board
property).
Alarm Impact
When all configured clock reference sources are lost, the clock board comes to free running
or hold-over state. Accuracy of output clock is determined by the crystal oscillator of clock
board. No impact on service.

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
2-39
SJ-20100603155704-004|2011-02-26(R3.0)
Frequently Reported
No
Probable Cause
Input clock reference is in unavailable status for more than 10 minutes and less than 24
hours. Probable causes include:
Handling Suggestion
property).
Alarm Impact
board. The clock loss leads to synchronization failure between system clock and clock
reference source. Service interruption might occur. The system will not be affected if the
following two events happen together:
1. Input clock reference source is lost.
2. The phase-locked loop locks other clock reference source.

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Critical
2-40
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Disaster Alarm
No
Frequently Reported
No
Probable Cause
Input clock reference is in unavailable status for more than 24 hours. Probable causes
include:
Handling Suggestion
property).
Alarm Impact
board. The clock loss leads to synchronization failure between system clock and clock
reference source. Service interruption will occur. The system will not be affected if the
following two events happen together:
1. Input clock reference source is lost.
2. The phase-locked loop locks other clock reference source.
2.1.40 198026131 CLKG board PLL out-of-lock

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
2-41
SJ-20100603155704-004|2011-02-26(R3.0)
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
Hardware is faulty.
Handling Suggestion
switching.
2. Replace board.
Alarm Impact
l
l
If this alarm occurs to master board, system clock synchronization will fail and
service interruption will occur.
2.1.41 198026133 Output clock lost

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
2-42
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Frequently Reported
No
Probable Cause
Hardware is faulty.
Handling Suggestion
switching.
2. Replace board.
Alarm Impact
l
l
If this alarm occurs to master board, system clock synchronization will fail and
service interruption will occur.
2.1.42 198005632 Usage rate of board hard disk above threshold

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
1. Usage rate threshold configuration is improper.
2. The usage of hard disk is over high.
2-43
SJ-20100603155704-004|2011-02-26(R3.0)
Handling Suggestion
1. Open the NMS Configuration Management interface, on MPX86 or MPX86/2 alarm
parameter > Hard Disk Full, check the threshold value in the configuration of Hard
Disk Usage Alarm level. Increase the threshold value if the setting is not larger enough.
2. Clear the disk and delete the unnecessary files or move the files to other external
storage devices.
Alarm Impact
When hard disk usage is over threshold, there may be error for the write-in operation of
new data, or data loss. It has no impact to the service.
2.1.43 198005637 Error in Rear Board That Mismatches With Front

Board
Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. Incorrect rear board is used.
2. Rear board failure.
Handling Suggestion
1. Check the front board type for the correct rear board type, and use the correct rear
board.
2-44
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
2. Replace the defective rear board with a new rear board.
Alarm Impact
l
l
When the rear board is used for the access of other NE, it would cause link
interruption on the bottom layer, and service interruption of the corresponding link.
When the rear board is used for the access of internal control plane, it would cause
communication error of internal control plane, failure of the board in exchanging
control plane message, and service interruption of the corresponding link.
The rear board of clock board is for clock synchronization, error in this board would
result in clock signal loss. The system services would be interrupted when clock
signal input is absent.
2.1.44 198005661 Physical link down between master/slave media

interactive ports
Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Warning
Disaster Alarm
No
Frequently Reported
No
Probable Cause
The network port or board is faulty.
Handling Suggestion
2. Replace the other board, that is, the board rather than the faulty board in active/standby
configuration.
2-45
SJ-20100603155704-004|2011-02-26(R3.0)
3. Replace the slot. Use the slot that supports GE channel between boards.
Alarm Impact
The APS optical port data on the standby board cannot reach the active board. When the
active optical port is normal, the service is not affected. When the active optical port is
faulty, APS fails to protect optical port and thus all services carried by the optical port are
interrupted.
2.1.45 198005662 IDE running overtime

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Warning
Disaster Alarm
No
Frequently Reported
No
Probable Cause
IDE is operated for longer time.
Handling Suggestion
No handling is necessary.
Alarm Impact
When hard disk work for long time without sleep, engine will be in high speed spin state
for long, this will influence the life of disk, and data will lose when disk be abnormal. Disk
of some model will lock the engine when it keep work for long time to protect the disk.
But this is out of the software controlled, and may result in data lose when disk cannot be
accessed transitorily.
2-46
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
2.1.46 198005667 E1 line is loop-line

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
The Rx and Tx E1 line is loop-line.
Handling Suggestion
1. Disconnect the looped E1.
2. Restart the board.
4. Replace the board which connected to this board.
Alarm Impact
The data of looped E1 can not be send out.
2.1.47 198005671 Incorrect FE Routing Connection

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
2-47
SJ-20100603155704-004|2011-02-26(R3.0)
Alarm
Severity
Critical
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. FE-C3/4 is used for FE routing port when RUIM1 rear board is used.
2. When CHUB is connected to UIM/GUIM, CHUB rear card (RCHUB1/RCHUB2) uses
discrete ports (e.g. port1/port3) to connect UIM rear card.
3. When UIM/GUIM is connected to UIM/GUIM CHUB, connections used for FE routing
connection are not in pairs (e.g.FE-C2/4).
4. When UIM is connected to UIM/CHUB, only one cable is used for FE inter-connection.
Handling Suggestion
Reconnect FE cables.
1. If RUIM1 rear board is used on BUSN shelf for FE routing connection, make sure to
select FE-C1/2 port as routing port.
2. If GUIM on BGSN shelf is used, make sure to select FE1 and FE2 ports as routing
ports. Either double-shelf or multi-shelf cascading connection is acceptable.
3. If TRUNK mode is used, multiple FE ports form a TRUNK port and they are connected
in cascading mode. In this case, make sure each end must use ports in pairs. If either
local end or opposite end doesn't use FE ports in pairs, please reconnect FE cables
and make sure each end uses ports in pairs.
Here is an example of connection method:
l
When CHUB is connected to UIM/GUIM, the CHUB rear board

(RCHUB1/RCHUB2) must use consecutive ports (e.g.
port1/port2 pair,
port3/port4 pair, port5/port6 pair, port7/port8 pair ) to connect the ports (also in
pair) on UIM/GUIM rear board.
When UIM is connected to UIM/CHUB, the UIM rear board must use ports in
pairs. If RUIM1 is used, 2 FE-C1/2 ports must be used for FE routing ports; if
RUIM2/RUIM3 is used, use FE1/FE2 pair, FE3/FE4 pair and FE5/FE6 pair for FE
routing ports.
2-48
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
When GUIM is connected to UIM/GUIM/CHUB, the GUIM rear board must use
ports in pairs, FE1/FE2 pair must be used for FE routing ports.
Alarm Impact
Control plane routing is disconnected; ports are switched over in cycle; all services on this
shelf are interrupted.
2.1.48 198005668 Self board has cross-linked E1

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
Self board has cross-linked E1.
Handling Suggestion
1. Disconnect the cross-linked E1.
2. Restart the board.
4. Replace the board which connected to this board.
Alarm Impact
The data of cross-linked E1 can not be send out.
2-49
SJ-20100603155704-004|2011-02-26(R3.0)
2.1.49 198005655 DSP Reports Exceptions After Detection

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
Hardware failure.
Handling Suggestion
1. Reset the board.
Alarm Impact
This DSP will be blocked and no longer available. The cell of this DSP is out of service;
The subscriber using this DSP is out of service; Call loss rate might increase when call
traffic is high.
2.1.50 198019712 APS channel mismatched

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
2-50
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. Fiber connection is wrong.
2. Configuration of APS backup mode at local end and opposite end is inconsistent.
3. Configuration of APS protection mode at local end and opposite end is inconsistent.
4. Opposite equipment is faulty.
Handling Suggestion
1. Check fiber connection. Check fiber connection at both ends. Ensure that the work
optical ports at both ends are interconnected, and the protection optical ports at both
ends are interconnected. On NMS configuration management interface, locate the
relevant board in the rack. Right-Click the board and shortcut menu appears. Click
Optical port APS protection in the shortcut menu to view the "Work optical port" and
"Protection optical port" configured at local end.
2. Check APS backup mode configuration at both ends. Check APS backup mode (1
1 or 1:1) at local end to ensure configuration consistency at both ends. On NMS
configuration management interface, locate the relevant board in the rack. Right-Click
the board and shortcut menu appears. Click Optical port APS protection in the shortcut
menu to view the "Protection Type" (1+1 or 1:1).
3. Check APS protection direction at both ends. Check APS protection direction
(unidirectional or bidirectional) configured at local end.
Ensure configuration
consistency at both ends. On NMS configuration management interface, locate the
Optical port APS protection in the shortcut menu to view the "Protection Direct"
(unidirectional or bidirectional).
4. Check whether APS is supported by the opposite equipment. Check whether APS
configuration is correct and has taken effect.
2-51
SJ-20100603155704-004|2011-02-26(R3.0)
Alarm Impact
APS automatic protection switching function is paralyzed. When the work optical port is
abnormal, protection optical port will not work, leading to service interruption on this optical
interface.
2.1.51 198019713 APS mode mismatched

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. Fiber connection is wrong.
2. Configuration of APS backup mode at local end and opposite end is inconsistent.
3. Configuration of APS protection mode at local end and opposite end is inconsistent.
Handling Suggestion
1. Check fiber connection. Check fiber connection at both ends. Ensure that the work
optical ports at both ends are interconnected, and the protection optical ports at both
ends are interconnected. On NMS configuration management interface, locate the
Optical port APS protection in the shortcut menu to view the "Work optical port" and
"Protection optical port" configured at local end.
2. Check APS backup mode configuration at both ends. Check APS backup mode (1
1 or 1:1) at local end to ensure configuration consistency at both ends. On NMS
configuration management interface, locate the relevant board in the rack. Right-Click
2-52
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
the board and shortcut menu appears. Click Optical port APS protection in the shortcut
menu to view the "Protection Type" (1+1 or 1:1).
3. Check APS protection direction at both ends. Check APS protection direction
(unidirectional or bidirectional) configured at local end.
Ensure configuration
consistency at both ends. On NMS configuration management interface, locate the
Optical port APS protection in the shortcut menu to view the "Protection Direct"
(unidirectional or bidirectional).
Alarm Impact
1. When fiber connection is correct and work optical port works, service is not affected.
2. When work optical port is faulty, APS automatic protection switching might fail, and
service on this optical interface might be interrupted due to lack of protection.
2.1.52 198019714 Conflicting between APS configuration and board

backup mode
Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
Board backup mode is configured as 1:1 or 1+1. APS protection mode is unconfigured.
2-53
SJ-20100603155704-004|2011-02-26(R3.0)
Handling Suggestion
l
If board backup mode is configured as 1:1 or 1+1 and SDH optical interface is
needed, at least one set of APS protection needs to be configured. To configure
APS protection: On NMS configuration management interface, locate the relevant
board in the rack. Right-Click the board and shortcut menu appears. Click Optical
port APS protection in the shortcut menu.
If board master/slave mode is not needed, modify board backup mode into. To
configure board backup mode: Delete the relevant board on NMS configuration
management interface. Then recreate the board. Select board backup mode as
"None" during board creation.
If board backup mode is configured as 1:1 and no SDH optical interface is required,
modify the board backup mode into 1+1. To configure board backup mode: Delete
the relevant board on NMS configuration management interface. Then recreate the
board. Select board backup mode as "1+1" during board creation.
Alarm Impact
Board operation status is abnormal. All board services fail to be established.
2.1.53 198005121 Inter-shelf media plane links abnormal

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
1. The fiber connection is error between UIM/GLI and UIM, or the fiber is not physically
plugged.
2-54
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
2. The background configuration of UIM is inconsistent with its foreground physical

connection.
3. The transceiver of UIM link detection packet is exceptional.
Handling Suggestion
1. Check the Unit Connection Relation in the configuration management interface to
make sure it is consistent with actual connection settings. Change the connection
cables according to actual configuration if they are inconsistent.
2. Check fiber optics for its proper cross connection and relevant alarm(s). Perform
recommended solution to process the possible alarm(s).
Related Alarm:
198005125 The GE optical transceiver module is incorrectly connected on the left and
right board slot on the peer-end
3. Replace the fiber optics cable or the optical transceiver module until the SD indicator
is ON on the corresponding port.
4. Replace the local optical board.
5. Replace the optical board at the peer end.
Alarm Impact
Reduces the inter-shelf service bandwidth. The inter-shelf service may be interrupted if
no backup system is configured.
2.1.54 198005124 Capacity of intra-shelf control plane TRUNK

communication is insufficient
Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
2-55
SJ-20100603155704-004|2011-02-26(R3.0)
Frequently Reported
No
Probable Cause
1. Connection failure.
2. Circuitry failure.
3. Board failure.
4. Rear board failure.
Handling Suggestion
1. Check about whether TRUNK connection is used for Inter-shelf control plane. If not
used, no processing is needed.
2. Check for the connection number: 4 Fe's, 2 GE's are required.
connection if there is any missing.
Complete the
3. Check whether the connection is proper. The proper connection show as the
following: For the FE port trunk, the UIM board on BUSN shelf does not support
TRUNK connection, so this alarm does not exist. For other shelf, FE7, FE8, FE9
and FE10 set up TRUNK ports. For the GUIM board, FE3, FE4, FE5, FE6 set up
TRUNK ports. For CHUB board, every 4 neighboring FE ports set up a TRUNK
port, such as FE1-FE4, FE5-FE8 etc. All the 4 ports on the TRUNK port must be
connected. The direct connect method is recommended. For the GE port trunk, 2
GE interfaces (CHUB board connection) are both connected and the connection is
cross-connection. The #1 GE port on the left board on the local shelf corresponds
to the #1 GE port on the left board on the opposite shelf, and the #2 GE port on the
left board on the local shelf corresponds to the #2 GE port on the right board on the
opposite shelf. The #1 GE port on the right board on the local shelf corresponds to
the #2 GE port on the left board on the opposite shelf, and the #2 GE port on the
left board on the local shelf corresponds to the #2 GE port on the right board on the
opposite shelf.
4. Replace the cable.
5. Replace the rear board.
6. Replace the board connected.
Alarm Impact
No system impact is resulted when TRUNK connection is not used between Inter-Shelf
Control Plane. When TRUNK connection is used, this means the network communication
capability is not enough, and it may cause congestion to control plane. During high traffic
period, this may cause large delay or even service interruption at extreme condition.
2-56
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
2.1.55 198005125 Incorrect Connection of GE Optical Transceiver

Module
Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
The fiber optics connection error.
Handling Suggestion
Check the fiber optics for its proper cross connection, the detailed steps are as below:
Each connection kit includes 4 cables, 2 boards (one at each ends of the connection kit).
Each board provides 2 ports which are to connect to the 2 boards on the peer side. The
cross-connection method is as below: the #1 port on the left board on the local shelf
corresponds to the #1 port on the left board on the opposite shelf, the #2 port on the left
board on the local shelf corresponds to the #1 port on the right board on the opposite shelf.
The #1 port on the right board on the local shelf corresponds to the #2 port on the left board
on the opposite shelf, and the #2 port on the left board on the local shelf corresponds to
the #2 port on the right board on the opposite shelf.
Alarm Impact
Cause interruption to all services performed on this shelf.
2-57
SJ-20100603155704-004|2011-02-26(R3.0)
2.1.56 198025602 Half-fixed connection error

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. Configuration of semi-fixed connection chip is incorrect.
2. Connection chip is faulty.
Handling Suggestion
1. On NMS configuration management interface, view IMA link configuration information.
Check HW and TS fields configured for the links to see if there exists value conflict (for
example, two A ends are configured for the same B end). If yes, modify configuration.
2. Replace the faulty board.
Alarm Impact
The link using the abnormal connection is interrupted, affecting the link services.
2.1.57 198005665 Fault on board (GPS)

Alarm Type
Equipment Alarm
2-58
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Critical
Disaster Alarm
No
Frequently Reported
No
Probable Cause
According to alarm details, alarm status falls into two types:
l
l
Type A fault on board (GPS) phase-lock equipment.

Phase-lock equipment of this board (GPS) is in power on status.
The causes for the two alarm types are described below.
1. Type A fault on board (GPS) phase-lock equipment Probable alarm causes include
16chip loss/out of lock, 12.8M loss/out of lock, PP2S output loss, 8K output loss, 10M
output loss, and 1PPS loss.
2. Phase-lock equipment of this board (GPS) is in power on status The alarm cause is
that the GPS module of ICM board is in power on status, and power on has not been
completed.
Handling Suggestion
On NMS fault management interface, view alarm Details where Error type information is
given. Locate the corresponding alarm handling suggestion according to the error type.
The alarm handling suggestions that correspond to the error types are described below.
1. Type A Fault on Board (GPS) Phase-lock Equipment
a. On NMS test management interface, perform diagnostic test on ICM board. Check
the working status of the GPS module. If Class A fault persists in the GPS module,
replace the board.
b. Check if output clock loss occurs. If yes, replace the board.
2. Phase-lock Equipment of This Board (GPS) Is in Power-on Status If the alarm persists,
hardware fault might exist. Replace the board.
2-59
SJ-20100603155704-004|2011-02-26(R3.0)
Alarm Impact
Be usually determined as hardware fault, which affects system clock. It might lead to
the system clock loss and system synchronization failure. When system clock loss/offset
occurs, its subsequent impact on service is described below.
1. For TDM transmission, all links based on the TDM transmission medium (including the
transmission link currently in service for UE and cell transmission link) are affected.
Packet loss might occur on these links, leading to degradation of service quality. In
the case of serious packet loss, service interruption and handover failure will occur.
Even worse, the cell might be out of service.
2. For non-TDM transmission (for example, IP transmission), Iub interface service is
affected, while Iur interface and Iu interface services are not affected. The clock that
Node B derives from RNC via IEEE1588 is inaccurate. When RNC clock frequency
offset is no more than 0.05 ppm, Node B synchronization will not fail, but success rate
of inter-RNC inter-Node B soft handover might fall. When RNC clock frequency offset
exceeds 0.5 ppm, Node B will fail to lock the clock. In this case, Node B will oscillate
freely and success rate of inter-Node B soft handover might fall.
2.1.58 198005650 Conflicted MAC addresses of boards on the

same shelf
Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Critical
Disaster Alarm
Frequently Reported
No
Probable Cause
1. The board is not inserted in position.
2. The board is not consistent with the backboard information.
2-60
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
3. UIM may have the loop back phenomena.
Handling Suggestion
1. Check whether the DIP switch setting is changed or the board is not restarted after the
change.
2. Plug and unplug the board and then check if the alarm is eliminated.
Alarm Impact
The board fails to start up, or control plane communication is abnormal. As a result, users
cannot gain access and existing services are interrupted.
2.1.59 198005405 Clock board phase-lock loop work mode

abnormal
Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. There is no available reference source.
2. The clock distribution line is incorrect or there exists self loop.
3. The secondary clock locks the tertiary clock.
Handling Suggestion
1. Check if the corresponding clock reference is correctly inputted.
2-61
SJ-20100603155704-004|2011-02-26(R3.0)
Alarm Impact
The designated reference clock cannot be phase-locked.
2.1.60 198005404 Board OCXO oven fault

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
Hardware fault of board.
Handling Suggestion
Replace the board, and check whether this alarm disappears.
Alarm Impact
Board operation might be abnormal.
2.1.61 198005403 Board SRAM self-check fails

Alarm Type
Equipment Alarm
2-62
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
Hardware fault of board.
Handling Suggestion
Replace the board, and check whether this alarm disappears.
Alarm Impact
Board operation might be abnormal.
2.1.62 198001825 High BER on SDH / Sonet link

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Warning
2-63
SJ-20100603155704-004|2011-02-26(R3.0)
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. Attenuation of receiving signals of local SDH equipment is large.
2. The transmitting part of opposite SDH equipment is faulty.
3. Fiber connector is polluted or misconnected.
4. The receiving part of local SDH equipment is faulty.
5. Operation of bit error insertion is performed at opposite end.
Handling Suggestion
l Meter Measurement
Use a SDH test meter or optical power meter to test whether the receiving optical
signals at local end are normal. If normal, fault might lie in local equipment. If
abnormal, fault lies in opposite end or on transmission side. Inform the opposite
end or transmission side to troubleshoot.
l
Loop Test
Perform fiber self-loop at local SDH equipment. If the alarm persists, fault
might lie in local equipment. If the alarm disappears, inform the opposite end to
troubleshoot.
2. Replace optical module.

3. Replace optical fiber.
4. Replace board.
Alarm Impact
SDH/SONET equipment can work. However, call loss or noise occurs to all voice services
on this optical path, and bit error occurs on the data service channel.
2.1.63 198001027 ATM link is down

Alarm Type
Equipment Alarm
2-64
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. Bottom layer physical link is abnormal.
2. HEC handling at local end and opposite end is inconsistent.
Handling Suggestion
1. On NMS configuration management interface, check if SDH/SONET mode
configuration exists at both ends. Ensure that the configuration at both ends is
consistent.
l Meter Measurement
Use a trunk test meter to test whether the receiving trunk signals at local end are
normal. If normal, fault might lie in local equipment. If abnormal, troubleshoot at
opposite end.
l
Loop Test
Perform self-loop at local trunk. If the alarm persists, fault might lie in local
equipment. If the alarm disappears, troubleshoot at opposite end.

4. Replace board.
Alarm Impact
Communication at ATM port is down. All services based on the trunk are interrupted.
2-65
SJ-20100603155704-004|2011-02-26(R3.0)
2.1.64 198030208 Fault alarm of CFM

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
l
DefXconCCM:
The MAID of the received CCM dose not exactly match the MAID configured in the
receiving MEP. DefErrorCCM:
1. The MEPID in the received CCM is not configured in the receiving MEP.
2. The MEPID in the received CCM matches the MEPID of the receiving MEP.
3. The CCM interval filed in the received CCM dose not match the configured for the
receiving MEP.
4. The source mac of CCM is not match the mac of rmep's configured.
DefRemoteCCM:
The MEP is not receiving CCM in timeout.
DefRDICCM:
The MEP is receiving CCM that have the RDI.
AIS:
The MEP is receiving AIS.
LCK:
The MEP is receiving LCK.
2-66
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Handling Suggestion
l
DefXconCCM:
Check the configure of the peer MD.
DefErrorCCM:
Check the configure of all MEP in MA.
DefRemoteCCM:
1. Check the fault of the link.
2. Check the other MEP in MA is enabled or not.
DefRDICCM:
Check the alarm of the last MEP.
AIS:
Check the alarm of the former MEP.
LCK:
Check the alarm of the former MEP.
Alarm Impact
l
DefXconCCM:
The configure of MD is error.
DefErrorCCM:
The configure of MEP in MA is error.
DefRemoteCCM:
1. The other mep is not enable.
2. The link is fault, mep can't receive PUD.
DefRDICCM:
The receive of the last MEP is error.
AIS:
The receive of the former MEP is error.
LCK:
The receive of the former MEP is error.
2.1.65 198029952 802.3ah link fault

Alarm Type
Equipment Alarm
2-67
SJ-20100603155704-004|2011-02-26(R3.0)
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
l
Link Fault:
The physical layer has determined a fault that occurred in the receive direction of the
local DTE.
Dying Gasp:
An unrecoverable local failure condition has occurred.
Critical Event:
An unspecified critical event has occurred.
Handling Suggestion
l
Link Fault:
1. Check the peer is or not right.
2. If right, change the optical fiber and check the alarm.
3. If the alarm is alive, change the and check the alarm.
4. If the alarm is alive, change the board.
Dying Gasp:
Check the peer is or not down.
Critical Event:
1. Check the 802.3ah is or not enable, if it is disable, it can't receive PDU.
2. If the 802.3ah is enable, if the port is optical, check the alarm of Link Fault is or
not alive, if the alarm is alive, the port can't receive the PDU.
3. Or not, change the good network cable.
2-68
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
4. If the alarm is alive, change the peer board.
Alarm Impact
l
Link Fault:
The port can't receive data, the operations will interrupt.
Dying Gasp:
The port can't receive data, the operations will interrupt.
Critical Event:
The 802.3ah is failed, can't detect the fault of link.
2.1.66 198015882 GLI buffer allocate fail

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. The traffic is over the capability of the board.
2. SRAM or DRAM error.
Handling Suggestion
1. Check the state of all ports of the alarmed board, if more than 2 ports of this board is
in master state, switch 1 or 2 ports to its partner port.
2-69
SJ-20100603155704-004|2011-02-26(R3.0)
2. If the alarm is still active, reboot the board.

3. If the alarm being triggered again after the board rebooted, replace the board.
Alarm Impact
2.1.67 198015881 GLI port transmit error

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. Packets error.
Handling Suggestion
1. Check all the GLI board in the same shelf to confirm whether there were any other
alarms, if this is the ONLY alarmed board, switch all master port of this board to its
partner board, and replace this board.
2. If this alarm being triggered again after the board replaced, connect ZTE.
3. If more than one GLI triggered this alarm, connect ZTE.
Alarm Impact
2-70
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
2.1.68 198015880 GLI board host and ME communication error

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. SRAM or DRAM error.
Handling Suggestion
Alarm Impact
2.1.69 198015879 GLI Port receive error

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
2-71
SJ-20100603155704-004|2011-02-26(R3.0)
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. Connection between fiber and optic modules is not perfect.
2. Something wrong with fiber optic modules.
Handling Suggestion
1. Check the connection between fiber and optic modules.
2. Replace optic modules.
Alarm Impact
2.1.70 198015878 GLI internal fabric port receive error

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
2-72
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. Network Processor or Switch Chip error.
2. PSN Board Hardware error.
Handling Suggestion
1. If only ONE GLI triggered this alarm, switch all master port of this board to its partner
board, and reboot the board.
2. If the alarm being triggered again after the board rebooted, replace the board.
3. If the alarm being triggered again after the board replaced, connect ZTE.
4. If the more than one GLI triggered this alarm, connect ZTE.
Alarm Impact
2.1.71 198015877 GLIQV SRAM/DRAM error

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
2-73
SJ-20100603155704-004|2011-02-26(R3.0)
Probable Cause
1. SRAM of GLIQV is error.
2. DRAM of GLIQV is error.
3. Micro engine of GLIQV is error.
Handling Suggestion
2. Change the master port to slave port.
3. Replace the board with a new board.
Alarm Impact
2.1.72 198005893 Memory check failed

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Critical
Disaster Alarm
No
Frequently Reported
No
Probable Cause
Memory check failed.
Handling Suggestion
1. Make records of the alarm information.
2-74
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
2. Replace the board or subcard.
Alarm Impact
The operation related to the memory maybe failed.
2.1.73 198005673 Backboard switch set is changed

Alarm Type
Equipment Alarm
Alarm Purpose
Internal Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
The setting of the DIP switch on the backboard has been changed.
Handling Suggestion
1. Plug the uim/UIM_2/GUIM/GUIM_2 board tightly to the slot again.
2. Replace the backplane of the shelf.
Alarm Impact
Other board faults
2-75
SJ-20100603155704-004|2011-02-26(R3.0)
2.1.74 198005672 Synchronization Ethernet clock source is

unusable
Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. The slave clock port does not receive ESMC PDU for 5 seconds.
2. The SSM value that the slave clock port received is DNU.
3. The port speed is 10M.
4. Physical link of the port is broken.
Handling Suggestion
1. Check the synchronization Ethernet's master/slave clock configuration of the
connected port, the configuration should be master;
2. Check local and connected port speed, port speed should not be 10M;
3. Check if the physical connection is correct.
Alarm Impact
The slave clock port can not synchronize with the connected port, which will cause
processing abnormity related to the clock.
2-76
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
2.1.75 198005670 Oscillator status abnormal

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Critical
Disaster Alarm
No
Frequently Reported
No
Probable Cause
Oscillator may stop oscillating or meet frequency deviation.
Handling Suggestion
Replace the board.
Alarm Impact
Board cannot work normally with this crucial device error.
2.1.76 198005669 Synchronization status check of FPGA failed

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Alarm
2-77
SJ-20100603155704-004|2011-02-26(R3.0)
Severity
Critical
Disaster Alarm
No
Frequently Reported
No
Probable Cause
Synchronization status check of FPGA and SPI4/VSC872/VSC874 failed. It's usually
caused by hardware exceptions. For example, the clock chip works abnormally.
Handling Suggestion
Replace the board.
Alarm Impact
If synchronization status check of FPGA fail, Media can not receive or send data normally.
And the board will reset for the exception of the media check frame.
2.2 Communication Alarm

2.2.1 198083021 CCP link fault alarm
Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
2-78
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Frequently Reported
No
Probable Cause
The transmission is faulty.
Handling Suggestion
Check if the Node B corresponding to the faulty CCP has generated associated alarms.
Follow the suggestions on handling the related alarms.
1. IP mode
According to the association link number, check if alarms related to association
links exist through the fault management interface. If yes, follow the suggestions on
handling the related alarms.
Related alarms:
l
l
198066018 Association congested

198066019 Association link broken
2. ATM mode
a. Bottom layer transmission fault Check if related alarms exist. If yes, follow the
suggestions on handling the related alarms.
Related alarms:
l
l
l
l
198001792
198066047
198066048
198005639
SDH/SONET fault
Abnormal status in SDH/SONET
SDH/SONET: Excessive Error Code
High Error Rate of Optical Interface
b. PVC link break Check if the related alarm exists. If yes, follow the suggestions on
handling the related alarm.
Related alarm:
198018944 PVC Fault
Alarm Impact
The CCP transmission link is unavailable. Therefore, the CCP cannot be used during radio
link establishment. If Node B continues to select this CCP, RNC messages cannot reach
Node B and the current service is interrupted.
2.2.2 198083036 DSAR Alarm

Alarm Type
Communication Alarm
2-79
SJ-20100603155704-004|2011-02-26(R3.0)
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. User plane resource initialization failure.
2. CCH setup failure at Node B side.
3. CCH configuration is deleted by OMCR.
4. The Bearer type of common transport channel is modified by OMCR.
Handling Suggestion
View alarm details on the NMS Alarm Management interface to check the Alarm Reason,
which can help you easily find the corresponding handling suggestions. The handling
suggestions for each alarm are as follows:
1. Alarm Reason: User plane resource initialization failure.
a. Click NE Information Configuration on the NMS Configuration Management
interface and select the corresponding Node B. Select the Path Configuration
tab to check if all parameters, including the forwarding bandwidth, are correctly
configured.
b. Click Path Group Configuration on the NMS Configuration Management interface
to check if all parameters are correctly configured.
2. Alarm Reason: CCH setup failure at Node B side. Click Base Station Ground
Resource Management on the NMS Configuration Management interface and select
IP and Route Management to check the IP parameters. Make sure that at least one
"COS" is selected.
3. Alarm Reason: CCH configuration is deleted by OMCR. This alarm will be processed
automatically by the system. The RNC will initiate the process of common channel
deletion. No manual handling is required.
2-80
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
4. Others. The system will automatically reestablish the common channel. No manual
handling is required.
Alarm Impact
The common channel is unavailable, which falls into three cases.
1. If the S-CCPCH that carries FACH is unavailable, the CS/PS services initiated by the
UE will fail.
2. If the S-CCPCH that carries PCH is unavailable, the paging function of the system
cannot be used and the CS/PS services initiated by the CN will fail.
3. If the PRACH that carries RACH is unavailable, the UE cannot access this cell.
2.2.3 198022784 BFD Session Interrupted

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. The
network
cable
connection
on
relevant
equipment(including
local/intermediate/opposite equipment) is loose or disconnected.
2. Intermediate equipment is faulty.
4. Local equipment is faulty.
5. Configuration related to the BFD session is incorrect.
2-81
SJ-20100603155704-004|2011-02-26(R3.0)
Handling Suggestion
On NMS fault management interface, view alarm Details where information of source
address and destination address of the BFD session is given. The source address is
the address of local equipment. The destination address is the address of BFD session
terminal equipment.
1. Check the operation status of line card at local end. If the line card resets repeatedly,
replace board. Then power-on the board.
2. Check the physical connection at the BFD session-related port on local line card. If
the connection is loose or broken, unplug and plug the cable or replace the cable. If
port indicator is on, the physical link must be normal.
3. Set a destination IP. Ping intermediate equipment and opposite equipment in turn.
a. Telnet to the interface board. Test if the link is normal via ping. If the destination
address is 2.2.2.10, issue the following command in telnet interface:
brs_ping_b "2.2.2.10"
b. Wait for 5 seconds and issue the following command:
BrsShowLog "ICMP"
l
l
c.
If "PING===> destine 2.2.2.10 timeout, Response timeout must occur"

appears on the interface, response timeout must occur.
If "ping_receive: Reply from 2.2.2.10: bytes=60 time<1ms" appears,
response must be normal, indicating that the link is normal.
In the case of response timeout, check if the configuration of related route and
address is correct. If not, perform reconfiguration and retest.
d. In the case of response timeout despite correct route/address configuration,

certain link or intermediate equipment might be faulty. Check if disconnected
network cable, loose connection, or abnormal equipment status exists on the
faulty link along the BFD session path. If yes, take necessary measures, including
cable replacement and replugging, equipment repair or replacement.
4. If packet reception and transmission are normal as confirmed by ping, check if the
BFD session configuration at both ends is correct.
On NMS configuration management interface
a. Check BFD switch. Ensure that the switch is in "enable" status.
b. Ensure that BFD session working modes at both sides are consistent.
c.
Ensure that BFD session in at least one equipment plays the active role.
d. Ensure that BFD session exists at both ends, and configuration of source IP and
destination IP matches.
e. Ensure that the hop mode (single hop/multihop) at both ends are consistent.
f.
Check configuration authentication information. Ensure that the number of

authentication information configured at both ends are consistent.
2-82
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
5. Reset the board where the interface is located.
Alarm Impact
All services on the path related to the BFD session will be switched to the slave path.
Service interruption will occur if slave path does not exist.
2.2.4 198066029 PPP link broken

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. The alarm occurs once in PPP port during board power-on, and recovers after
successful PPP negotiation.
2. Physical link is down, or link transmission quality is poor.
3. Adjustment of PPP link parameter leads to link re-negotiation, causing the alarm.
Handling Suggestion
On NMS fault management interface, view alarm Details, where the faulty PPP port ID is
given.
1. Check cable connection at both ends. If the cable is disconnected or connection is
loose, unplug and plug the cable or replace the cable.
2. Refer to users networking plan to see if E1 cable connection is correct.
2-83
SJ-20100603155704-004|2011-02-26(R3.0)
3. On NMS configuration management interface (IPOverE1 configuration), check

Interface E1 No. and time slot configuration. Ensure that the relevant configuration
is consistent at both ends.
4. On NMS configuration management interface, check PPP configuration. Ensure that
the relevant configuration at both sides is consistent.
5. On NMS configuration management interface, check configuration of DT and EIPI
connection. Ensure the connection continuity of PPP port at both ends.
Alarm Impact
The PPP link is down. If merely one PPP link is available for the port or all available PPP
links are down, the service on the port will be down. Otherwise, only port bandwidth will be
affected. The number of successful service access will decrease, but service interruption
will not occur.
2.2.5 198019213 LIF Alarm of Near-End Receiving Link

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
Physical fault or connection error occurs to E1 link.
2-84
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Handling Suggestion
On NMS fault management interface, view alarm Details where information of IMA chip
ID, IMA group ID, IMA link ID, and E1 index is given. Locate the faulty IMA link according
to the given information.
1. Refer to users networking plan to see if connection error exists.
2. On NMS fault management interface, check if E1-related alarm exists in the board. If
yes, refer to the corresponding alarm handling suggestion.
Related alarms:
l
l
l

198001026 Cell delineation do not synchronization about cell on E1 link
Alarm Impact
IMA link is down. If several links are available in the IMA group, bandwidth of the IMA group
will be affected, and the number of successful upper-layer service access will decrease.
However, service interruption will not occur. If merely one link is available in the IMA group,
all services on the IMA group are interrupted.
2.2.6 198019214 LODS Alarm of Near-End Receiving Link

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. Operation of the input clock is abnormal.
2-85
SJ-20100603155704-004|2011-02-26(R3.0)
2. Transmission quality of the link is poor.

3. Self-loop occurs to some cable connection in IMA group.
4. Cable connection is incorrect in IMA group.
5. Hardware is faulty.
Handling Suggestion
ID, IMA group ID, IMA group link ID, and IMA link ID is given. Locate the faulty IMA link
according to the given information.
1. Check the RUN indicator of clock board. If the indicator is green and flashes slowly,
operation of the clock board must be normal. Otherwise, reset/replace the clock board.
2. On NMS fault management interface, check if clock-related alarm occurs in UIM/GUIM.
If yes, input clock source must be abnormal. Refer to the corresponding alarm handling
suggestion.
Related alarms:
l
l
198001286 Loss of clock when input to board

198005646 Phase-lock loop unlock
3. On NMS fault management interface, check if E1-related alarm exists. If yes, refer to
the corresponding alarm handling suggestion.
Related alarms:
l
l
l

198001026 Cell delineation do not synchronization about cell on E1 link
4. Check if remote self-loop occurs to any physical connection in the faulty IMA group. If
yes, properly connect the cable according to the networking planning information.
5. Check cable connection according to the networking planning information. Ensure that
the cabling is correct.
6. Reset board.
7. Replace board.
Alarm Impact
2-86
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
2.2.7 198019215 RDI alarm of far end receiving link

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. Remote IMA link is not in activated status.
2. Remote receiving direction is faulty.
Handling Suggestion
ID, IMA group ID, IMA link ID, and E1 index is given. Locate the faulty IMA link according
to the given information. Check the working status of the relevant remote receiving link
by referring to the opposite equipment operation guide. If remote receiving link is not in
activated status, activate the link.
Alarm Impact
2-87
SJ-20100603155704-004|2011-02-26(R3.0)
2.2.8 198019223 Ne Group is in fault state

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. All IMA links of this IMA group are broken.
2. The peer-end IMA group is broken.
Handling Suggestion
Fix the broken IMA links in the IMA group.
Alarm Impact
The IMA Group does not work.
2.2.9 198066026 Association path broken

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
2-88
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Alarm
Severity
Major
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
1. Network communication is faulty.
2. Control plane path in NE is interrupted.
4. The route to remote address is lost.
Handling Suggestion
On NMS fault management interface, view alarm Details, where information of association
ID, local address, and remote address is given.
1. On NMS configuration management interface (static route), query the route information
of the remote address. Locate the out port according to the route information. Check
if network cable of the out port is disconnected or loose. If yes, unplug and plug the
cable or replace the cable.
2. On NMS configuration management interface (SCTP association configuration),
query the ID of the module where the association is located. Check if the following
alarm occurs in the relevant board. If yes, refer to the corresponding alarm handling
suggestion.
Related alarm:
198066003 Control plane communication abnormal between board and its home
module
3. On NMS configuration management interface (static route), query if the route to the
remote address of the association is configured. If not, add the configuration.
4. Check the intermediate equipment on association path. If the routes to local address
and remote address of the association are not configured, add the configuration
according to equipment operation manual.
5. Check at opposite end if the route to the local address of the association is configured.
If not, add the configuration.
2-89
SJ-20100603155704-004|2011-02-26(R3.0)
6. Check if the opposite equipment is faulty. If yes, troubleshoot at opposite end.
Alarm Impact
If multiple paths are available for the association and there exists normal path, relevant
services will not be affected. If merely one path is available for the association, all services
on the association is down.
2.2.10 198005666 The number of the error packets from MAC port
exceeds the threshold
Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. The port cable is not properly connected.
2. The port cable is faulty.
3. The IC of external board port is faulty.
4. The corresponding board is faulty.
Handling Suggestion
1. Reconnect the cable, ensure that the connection between this port and the peer port
is correct.
2. Replace the cable.
2-90
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
4. Contact the opposite engineers to check the opposite ports for possible failure.
Alarm Impact
The MAC port is unavailable or the flow is limited.
2.2.11 198015617 Faulty Frames Received by FE/GE/ATM/MP/PO

S/E1 Port
Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
Yes
Probable Cause
1. The network connected with FE/GE/ATM/MP/POS/E1 port is abnormal.
2. The board is in abnormal status.
3. Board hardware is faulty. For example, the network processor subcard is not tightly
inserted.
4. Other board hardware faults.
Handling Suggestion
1. Unplug and plug port fiber/network cable.
2. Replace port fiber/network cable.
3. Reset board.
4. Unplug and plug board.
2-91
SJ-20100603155704-004|2011-02-26(R3.0)
5. Replace board.
Alarm Impact
Datagram reception of the board is affected. The service on this port might be unstable.
Worst of all, all services on the board might be interrupted.
2.2.12 198015873 Faulty frames received by internal switching

interface
Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. The PSN board in the same shelf is abnormal.
2. Network processor subcard of the board is not tightly inserted.
3. Board hardware is faulty. For example, the switching chip is faulty.
Handling Suggestion
1. Check if the following alarm exists in PSN board at the same shelf. If yes, refer to the
corresponding alarm handling suggestion.
Related alarm:
198019456 All high-speed links between line card and package switching board are
out of synchronism
2-92
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
3. Replace board.
Alarm Impact
If the fault lies in PSN board, service of the entire RNC NE will become unstable. If the
alarm persists, all services will be interrupted. If the fault lies in the board where the alarm
is declared, only the services on this board are affected.
2.2.13 198005378 Board HW Error

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. Clock is not synchronous.
2. Either the board or the slot has a hardware fault.
Handling Suggestion
1. Check whether the board has one of the following alarms. If yes, please solve the
problem according to corresponding handling suggestions.
Related alarms:
l
l
198001286 Loss of input clock

198005646 Phase-locked Loop Unlocked
2. Check whether the clock board has one of the following alarms. If yes, please solve
the problem according to corresponding handling suggestions.
2-93
SJ-20100603155704-004|2011-02-26(R3.0)
Related alarms:
l
l
l
l
198026133 Output clock lost

198026129 Clock reference source lost (Level 1 alarm)
3. In Configuration Management interface, check whether APS protection is configured

when the SDTB/SDTB2 works in master/slave mode: In the Configuration
Management interface, double-click on the Rack node to open the rack view.
Right-click on the concerned board (SDTB/SDTB2), a shortcut menu appears. Then
select Optical Port APS Protection.
5. Replace the slot
6. Replace the UIM/GUIM of the same shelf.
Alarm Impact
HW connection is affected and services carried over this HW are interrupted.
2.2.14 198005651 IPMAC conflict when OSS detects control plane

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. The board is not plugged in place.
2-94
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
2. Backplane DIP switch configuration has been modified.
Handling Suggestion
2. Check the backplane DIP switch at the shelf where the board is located and the switch
at the shelf where OMP is located. If the switches at two shelves are inconsistent,
reconfigure the DIP switch to keep consistency. Reset the relevant boards after
reconfiguration.
3. Reset board.
Alarm Impact
IPMAC Conflict leads to communication fault in board control plane.
For the board that has powered on, packet loss occurs and board services is unstable.
Even worse, link interruption might occur and all services on the board might be interrupted.
For the board that is powering on, board resets repeatedly, and service access to the board
fails.
2.2.15 198066003 Control plane communication is abnormal

between board and its home module
Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
Yes
Frequently Reported
No
2-95
SJ-20100603155704-004|2011-02-26(R3.0)
Probable Cause
1. The board is not in position.
2. The board is faulty.
3. The control plane communication is abnormal.
4. The board is reset.
Handling Suggestion
1. Check if the board is in position. If not, insert the board.
2. Reset the board. Wait for the board to be powered on.
4. Replace the board slot.
5. Replace the UIM/GUIM board in the same shelf.
Alarm Impact
The services carried by the board are interrupted.
2.2.16 198066004 Control plane communication is abnormal

between MP and OMP
Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
Yes
Frequently Reported
No
2-96
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Probable Cause
1. The board is not in position.
3. The control plane communication is abnormal.
4. The board is reset.
Handling Suggestion
1. Check if the board is in position. If not, insert the board.
2. Reset the board. Wait for the board to be powered on.
4. Replace the board slot.
5. Replace the UIM/GUIM board in the same shelf.
Alarm Impact
The board is blocked and the functions of the board are unavailable. As a result, all
services of the units under this module are unavailable.
2.2.17 198005382 Communication between power board and OMP

board is abnormal
Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
2-97
SJ-20100603155704-004|2011-02-26(R3.0)
Probable Cause
1. The power board is not connected to the OMP or connection failure occurs.
2. The rack number configured for the rack in which this power board locates is not
consistent with the rack number switch set for the power board.
Handling Suggestion
1. Reconnect the serial cable between the power board and the OMP.
2. Make sure the rack number configured for the rack in which this power board locates
is consistent with the rack number switch set for the power board.
Alarm Impact
Unable to monitor the power supply condition and the environment condition. It has no
impact to the services.
2.2.18 198005397 Communication of RAWMACIP channel is

abnormal
Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. The CPU usage of the UIM/GUIM in the shelf is too high.
2. The service media stream exceeds the threshold.
3. The hardware is faulty.
2-98
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Handling Suggestion
1. On NMS fault management interface, check if the UIM/GUIM board in the same shelf
has related alarms. If yes, follow the suggestions on handling the related alarms.
Related alarm:
198002560 Board CPU overloaded
3. Replace the UIM/GUIM in the same shelf.
4. Replace the slot.
Alarm Impact
The channel between user plane processing board and signaling processing board is
abnormal. This causes the degradation of QoS. In most serious case, the service is totally
interrupted.
2.2.19 198005401 Test packet check abnormal

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
2. The line from UIM/GUIM to GLI is abnormal.
2-99
SJ-20100603155704-004|2011-02-26(R3.0)
Handling Suggestion
On NMS fault management interface, view the alarm details, which give the test alarm
type. You can quickly locate the handling method according to the test alarm type. The
handling suggestion for each test alarm type is as follows:
1. Test alarm type: ATM test abnormal. The link between the internal IC of ATM
processing board is abnormal. In this case, replace the board.
2. Test alarm type: Level 1 switch test abnormal. The level 1 media plane switching from
UIM/GUIM to GLI is abnormal. This is always caused by the abnormal link between
UIM/GUIM and GLI. In this case, reconnect the cables between UIM/GUIM and GLI
or replace the cables. If optical fibers are used, replace the optical module.
Alarm Impact
This alarm affects the service transfer on media plane. In alarm details, the detected alarm
type gives the error type of the alarm. The alarm impact varies depending on the alarm
type.
l
l
If the test alarm type is "ATM test abnormal", the ATM board cannot normally provide
ATM services. Thus, the service carried by the board is interrupted.
If the test alarm type is "Level 1 switch test abnormal", it indicates that media plane
communication is abnormal. This causes the service carried by this shelf to be
interrupted.
2.2.20 198005122 Communication Link between Active and Standby

Boards Off
Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
2-100
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Frequently Reported
No
Probable Cause
1. The board is configured as Active/Standby mode, but one of these two boards is not
in place.
2. Hardware fault.
Handling Suggestion
1. Make sure the board is Active/Standby configuration, and the active board and standby
board are firmly in place.
2. Check the active board and standby board for the following related alarms:
198005379 Board Offline or the CPU is in long period reset status
3. Replace the opposite board.
4. Change the slots of both the active board and the standby board.
Alarm Impact
The active board and standby board communication fails, and the active/standby
switchover fails. It has no impact to the services.
2.2.21 198005126 Incorrect FE Routing Connection

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Critical
Disaster Alarm
No
Frequently Reported
No
2-101
SJ-20100603155704-004|2011-02-26(R3.0)
Probable Cause
1. FE-C3/4 is used for FE routing port when RUIM1 rear board is used in the UIM
2. When CHUB connects UIM/GUIM, the connector cable from CHUB rear card
RCHUB1/RCHUB2 uses none continuous ports, (example: port1/port3) to connect
UIM rear card.
3. When UIM/GUIM connects UIM/GUIM CHUB, pairless connection (such as FE-C2/4)
is used for FE routing connection.
4. When UIM is connected to UIM/CHUB, only 1 piece of cable is used for FE connection.
Handling Suggestion
Reconnect the FE wire.
1. If the UIM on the BUSN shelf uses RUIM1 rear board for FE routing connection, make
sure FE-C1/2 port is used for routing port.
2. If the GUIM on BGSN shelf, make sure FE1,FE2 ports as routing ports for dual shelf
cascaded connection or multiple shelf cascaded connection.
3. If TRUNK mode is used, please use multiple FE ports for the TRUNK port of cascaded
connection. In this case, make sure the both ends are paired ports. If the local end or
opposite end is not paired port, please reconnect the FE wire and make sure the both
ends are paired ports. Here is an example of connection method:
a. When CHUB is connected to UIM/GUIM, the connecting wire from CHUB rear
board RCHUB1/RCHUB2 must use continuous ports ( such as port1/port2 pair,
port3/port4, pair, port5/port6 pair, port7/port8 pair ) to connect to the port pairs on
the UIM/GUIM rear board.
b. When UIM is connected to UIM/CHUB, UIM rear board paired ports must be used.
If RUIM1 rear board is used, then 2 FE-C1/2 ports must be used for FE routing
ports; if RUIM2/RUIM3 rear board is used, then use FE1/FE2 pair, FE3/FE4 pair
and FE5/FE6 pair for the FE routing ports.
c.
When GUIM is connected to UIM/GUIM/CHUB, the GUIM rear board ports must
be in pair too, i.e., FE1/FE2 pair must be used for FE routing ports.
Alarm Impact
Control plane routing disconnection, or circularly handover of the ports. Cause interruption
to all the services performed on this shelf.
2.2.22 198005128 Duplicate rack and shelf

Alarm Type
Communication Alarm
2-102
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
Shelf connect to the system with duplicate physical ID.
Handling Suggestion
1. Check whether two shelf with same physical ID exists. Modify the switch of one of the
two shelves and reset the shelf and board if such connection exists.
2. Check if the board link to the same board by different link type. Remove one of link
type and reset the board if such connection exists.
Alarm Impact
Boards in the shelf which power-on later power-on failure.
2.2.23 198066005 SCCP subsystem unavailable

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
2-103
SJ-20100603155704-004|2011-02-26(R3.0)
Severity
Minor
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
1. From the perspective of A, remote signaling point subsystem is out of service.
2. From the perspective of A, remote signaling point is inaccessible.
3. Remote subsystem(for B) is configured at A end, but the corresponding local
subsystem (for B) is not configured at B end.
4. Local subsystem(for B) is blocked at B end.
5. From the perspective of A, SCCP user is unconfigured in remote MTP3 or M3UA user
configuration.
Handling Suggestion
1. Check whether there exists office (the office that corresponds to the subsystem)
inaccessible alarm. If yes, refer to the corresponding alarm handling suggestion.
Related alarms:
l
l
198066010 MTP3 office inaccessible

198066014 M3UA office inaccessible
2. Unblock the subsystem in dynamic data management.

3. On NMS configuration management interface, check the configuration of signaling
point code (for A) at A end. See if SCCP user is included in user type configuration.
If no, add the configuration. Meanwhile, check the corresponding configuration at B
end.
4. Check whether the status of signaling point subsystem (for B) is available at B end. If
no, the signaling point subsystem at B end must be out of service. Locate the cause
for the abnormal status.
5. Check whether the signaling point subsystem (for B) is configured at B end. If no, add
the configuration at B end.
Alarm Impact
Signaling data cannot be sent to and received from the relevant subsystem. Access of new
service under the corresponding office fails, and release of the ongoing service occurs.
2-104
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
2.2.24 198066007 Broadband link overload

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. There are too many messages from upper layer service.
2. The number of links is insufficient.
3. Link load is uneven.
Handling Suggestion
1. Check the counter of "Peak Traffic of Signalling Link" in MTP3B signaling link
performance statistics. If the load (nearly) reached 6000 during alarm occurrence,
upper layer traffic must be heavy. Add links to share load.
2. On NMS configuration management interface, check the signaling link configuration
of NE. Add or delete links to ensure that the number of links in a link set is two to the
power of N. If there are two link sets in the current route, ensure that two link sets have
the same number of links.
Alarm Impact
Link overload leads to upper layer service message loss. Call loss will occur, and access
success rate of PS service will fall.
2-105
SJ-20100603155704-004|2011-02-26(R3.0)
2.2.25 198066010 MTP3 office inaccessible

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
1. No service link exists in the office route.
2. TFP is received.
Handling Suggestion
1. Check if there exists unavailable link alarm. If yes, refer to the corresponding alarm
handling suggestion.
Related alarm:
198066011 MTP3 link unavailable
2. Check whether office and link configuration at opposite end is correct.
Alarm Impact
Reception and sending of messages from/to the relevant office fail. Access of new service
under this office fails, and abnormal release of the ongoing service occurs.
2.2.26 198066011 MTP3 link unavailable

Alarm Type
Communication Alarm
2-106
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
1. Bottom layer physical link is down or link quality is poor.
2. Link test fails to be passed.
3. Link deactivation is performed in dynamic data management.
4. The link is released at opposite end.
5. SMP SPB/SPB2/APBE/APBE2 board resets.
Handling Suggestion
1. On NMS configuration management interface (signaling link configuration), check PVC
configuration. Configuration of CVPI and CVCI at both ends should be consistent.
2. Check link status in dynamic data management. If link interruption occurs now and
then, link unavailability might be caused by MTP3 link test failure.
a. On NMS configuration management interface, check the signaling point code
configuration at both ends. Ensure that the configuration at both ends is
consistent.
b. On NMS configuration management interface, check the signaling link
configuration at both ends. Ensure that the SLC(signaling Link Code) configuration
at both ends is consistent.
3. Reactivate the link in dynamic data management.
4. Check board status. If board status is abnormal, reset/replace the board.
5. The relevant link is released at opposite end. Ask the opposite end to perform handling
as link is unavailable.
2-107
SJ-20100603155704-004|2011-02-26(R3.0)
Alarm Impact
If several MTP3 links are available under the office, service will not be affected. In the case
of heavy traffic, congestion of available link(s) might occur, leading to packet/call loss or
increasing PS call access failures. If merely one link is available to the destination signaling
point, the office might become inaccessible. Reception and sending of messages from/to
the relevant office fail. Access of new service under this office fails, and abnormal release
of the ongoing service occurs.
2.2.27 198066014 M3UA office inaccessible

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. Association link is broken or application server (AS) is not in serving status.
2. DUNA (destination signaling point unavailable) is reported by remote office of the
association.
Handling Suggestion
1. Check if there exists broken association link alarm. If yes, refer to the corresponding
Related alarm:
2-108
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
2. Check AS configuration on NMS configuration management interface. Main checking

items include the existence of routing context, routing context ID, APP server AS ID,
and traffic mode. Correct configuration is described below.
a. The routing context ID and traffic mode at both ends must be the same.
b. APP server AS ID configuration must meet the following requirements. If ASP
is configured for local end, SGP should be configured for Opposite end. If IPSP
client is configured for local end, IPSP server should be configured for opposite
end.
3. Reactivate the ASP in dynamic data management.
4. Check whether the configuration of the relevant office is correct at opposite end.
Alarm Impact
Reception and sending of messages from/to the relevant office fail. Access of new service
under this office fails, and abnormal release of the ongoing service occurs.
2.2.28 198066019 Association link broken

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. The association is released in dynamic data management.
2. Association configuration is modified at local end.
3. Association is released at opposite end.
2-109
SJ-20100603155704-004|2011-02-26(R3.0)
4. Bottom layer link is faulty.
Handling Suggestion
1. Establish the association in dynamic data management.
2. On NMS configuration management interface, check association configuration at local
end and opposite end. Checking items include protocol type of SCTP association,
SMP module No, local IP address, local port No., remote IP address, remote port No.,
the number of in/out streams. If the configuration at both ends is inconsistent, modify
configuration to keep consistency.
3. Ping the opposite board address to see if the network cable or other intermediate link
is faulty. Replace the cable if ping fails.
4. Check if the association is released at opposite end. If yes, troubleshoot according to
the corresponding cause.
Alarm Impact
l
If several association links are available to the destination office, service will not be
affected. In the case of heavy traffic, congestion of available association(s) might
occur, leading to upper layer call loss or increasing PS call access failures.
If merely one association link is available to the destination office, the office might
become inaccessible. Reception and sending of messages from/to the relevant
office fail. Access of new services under this office fails, and abnormal release of
ongoing services occurs.
2.2.29 198083045 Common Channel setup failed Alarm

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
2-110
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Frequently Reported
No
Probable Cause
1. Use plane resource initialization fails.
2. Common channel establishment fails on Node B side.
3. CCH transport bearer setup fail.
4. Common channel configuration is deleted in NMS.
5. Inner Procedure Fail.
Handling Suggestion
Check the configuration according to the following steps:
1. Check whether DSP run normally.
2. Check whether IUB interface board run normally.
3. On NMS configuration management interface (NE information configuration), select
the relevant Node B. Check the correctness of parameter configuration on path
configuration interface. "Peer service IP address" must be configured in the same
network segment with NODEB IP address.
4. On NMS configuration management interface (BS ground resource management),
view IP parameter configuration in IP and route management. Ensure that at least
one COS is selected.
5. On NMS configuration management interface (NE information configuration), select
the relevant Node B. Check the correctness of parameter configuration on path
configuration interface. Check if forwarding bandwidth is configured.
6. On NMS configuration management interface (path group configuration), view path
group configuration. Check the correctness of parameter.
7. Check whether NODEB alarm exist.
8. Contact with ZTE Corporation.
Alarm Impact
Common Channel is unavailable, which falls into the following three cases.
1. If the SCCPCH carrying FACH is unavailable, UE-initiated CS/PS services will be
down.
2. If the SCCPCH carrying PCH is unavailable, paging function will be unavailable in the
system, leading to failure of UE-initiated CS/PS services.
3. If the PRACH carrying RACH is unavailable, UE access to the cell will fail.
2-111
SJ-20100603155704-004|2011-02-26(R3.0)
2.2.30 198083048 Transport Path Occupied Bandwidth Overload

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
Available bandwidth of transport path is less than occupied bandwidth. Probable causes
for the alarm include:
1. E1 link is broken.
2. Transmission quality of the transmission line is poor.
Handling Suggestion
1. Check the E1 link.
2. Check the transmission quality of intermediate equipment.
Alarm Impact
The available bandwidth to destination is less than occupied bandwidth. Some services
would be released in this transport path selectively to avoid transport path congestion.
2-112
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
2.2.31 198083049 Transport Path group Occupied Bandwidth

Overload
Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
Available bandwidth of transport path group is less than occupied bandwidth. Probable
causes for the alarm include:
1. E1 link is broken.
2. Transmission quality of the transmission line is poor.
Handling Suggestion
1. Check the E1 link.
Alarm Impact
The available bandwidth to destination is less than occupied bandwidth. So service rate
on this path group will be degraded.
2-113
SJ-20100603155704-004|2011-02-26(R3.0)
2.2.32 198083050 IP channel of Iub interface is faulty

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. IP channel is down.
2. Packet loss rate exceed 25%.
Handling Suggestion
2. Check the configuration of NodeBNo/IpAddr/IpDomain of RNC, check the
configuration of OMCB Gateway/Inner IP of NodeB.
Alarm Impact
If the multi-path protect switch is on, the Service and OMCB will choose other IP channel
to transfer data, and if there is no available IP channel, the Service and OMCB will fail.
2.2.33 198066067 AAL2 Path remotely blocked

Alarm Type
Communication Alarm
2-114
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
The adjacent AAL2 node initiates blocking process and then the path of this node is
remotely blocked when receiving the blocking message from the adjacent node.
Handling Suggestion
You can unblock the Path which is generated by adjacent node from the operating interface
of the adjacent node.
Alarm Impact
No AAL2 connection can be established on the blocked path.
2.2.34 198066068 AAL2 Path blocked by broken PVC

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
2-115
SJ-20100603155704-004|2011-02-26(R3.0)
Disaster Alarm
No
Frequently Reported
No
Probable Cause
The Path is blocked because of the broken PVC.
Handling Suggestion
The path can be available when PVC becomes available.
Alarm Impact
2.2.35 198066071 All SSCOP links in an IMA group broken

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. SSCOP or AAL5 links on Node B are deleted or not configured.
2. All SSCOP or AAL5 links in a IMA group are down. (IMA chip and IMA group in detailed
information)
2-116
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
3. Board internal fault.
Handling Suggestion
Please check the IMA and signaling links configuration on both sides and the status of
signaling links are in data transfer ready. Checking solution: find the IUB office by the
combination of board slot, IMA chip and IMA group, and to find out the SSCOP or AAL5
links by IUB office, and last to see the status of links by dynamic management function.
Alarm Impact
This alarm may render some offices inaccessible, or may result in the congestion of other
links.
2.2.36 198394014 Control plane communication interrupted for a

long time or high frequency between board and its home
module
Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
8393985 "Control plane communication interrupted for a long time or high frequency
between board and its home module" occurs for a long time or high frequency.
2-117
SJ-20100603155704-004|2011-02-26(R3.0)
Handling Suggestion
On NMS fault management interface, check if control plane communication abnormal
between board and its home module alarm exists in the board. If yes, refer to the
corresponding alarm handling suggestion. If not, you can delete it manually or wait for it
restored automatically.
Alarm Impact
The services carried by the board may interrupted.
2.2.37 198000519 Trunk error

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. The receiving cable of local trunk equipment is faulty. The cable is disconnected, or
cable connector is broken.
2. The transmitting cable of opposite trunk equipment is faulty. The cable is disconnected,
or cable connector is broken.
3. Trunk transmission line is faulty. The local DDF and equipment are not properly
connected.
4. Operation of LOS insertion is operated at opposite trunk equipment. Manual inset
alarm operation is performed in diagnostic test.
2-118
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Handling Suggestion
1. Check whether the alarm is caused by local end or opposite end via meter
measurement or loop test.
Meter Measurement
Use a trunk test meter to test whether the trunk receiving signals at local end are
normal. If yes, fault might lie in local equipment. If no, troubleshoot at opposite end.
Loop test Perform trunk self-loop at local end. If the alarm persists, fault might lie in
local equipment. If the alarm disappears, troubleshoot at opposite end.
Alarm Impact
The trunk equipment fails to work normally. All services based on the trunk are interrupted.
2.2.38 198000520 Trunk abnormal

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. Trunk frame formats at local end and at opposite end are inconsistent.
2. The transmitting end of opposite trunk equipment is faulty.
3. Local trunk equipment is faulty.
2-119
SJ-20100603155704-004|2011-02-26(R3.0)
4. Equipment grounding at both ends is bad.

5. Impedance mismatch occurs.
Handling Suggestion
Alarm details are displayed in NMS Alarm Management interface, where fault type is
given. You can easily find handling suggestions according to the fault type. The handling
suggestions for each fault type are described as below:
1. Loss of E1 trunk frame, loss of E1 trunk multi-frame, E1 trunk alarm indication.
a. In NMS Configuration Management interface, right click the board and select
Subunit Configuration to check whether frame format at both ends is the same.
b. In NMS Configuration Management interface, right click the board and select
Subunit Configuration to check whether impedance is correct.
c.
Check whether the grounding at both ends is proper.
d. If possible, locate alarm position, either at local end or at opposite end, by means
of measurement instrument, loopback test, or board/cable replacement.
2. E1 trunk receives an alarm indication from opposite end. Check the alarm status of
opposite end. Because the alarm indication is sent from opposite end, please solve
the opposite-end problem first.
Alarm Impact
All services based on the trunk are interrupted.
2.2.39 198003841 The control plane retransfer ratio over the

threshold
Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
2-120
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Frequently Reported
No
Probable Cause
There are some badly-touched boards in the system environment and the retransfer-ratio
of RUDP packets increases.
Handling Suggestion
Make records of the alarm information and contact ZTE Corporation.
Alarm Impact
The master board will change when slave is exist.
2.2.40 198005127 FE Link Error Alarm

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. In a pair of FE ports, one has normal link but the other has link error.
2. The hardware is faulty.
2-121
SJ-20100603155704-004|2011-02-26(R3.0)
Handling Suggestion
1. Check if only one cable is used to connect the port pair of the rear board to the peer-end
FE port. Ensure that both cables are connected to the peer end.
2. Reconnect the cables or replace the cables.
3. Replace the rear board.
Alarm Impact
Because one FE port has normal control plane link, services are not affected. However
if this port is faulty, services can not be switched to the other port, leading to service
interruption.
2.2.41 198005129 Ethernet port loop back error

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
Ethernet port loop back occurs.
Handling Suggestion
1. Check alarm info of the board.
2-122
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
a. Check if the debug port loops back. Check the HUB or other device linked to the
debug port. If there is loop back, destroy the loop back and check if the alarm
restored.
b. Check if the port which linked to shelves loops back. Check if the connection
between shelves is incorrect. Correct the connection and check if the alarm
restored.
2. Make records of the alarm information and contact ZTE Corporation.
Alarm Impact
There is a fault of the network in the system.
2.2.42 198015618 Faulty frames received by port over threshold

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
Yes
Probable Cause
1. Network status of FE/GE/ATM/MP/POS/E1 port is abnormal.
2. Board hardware faults.
3. Other faults of the board cause faulty FE/GE/ATM/MP/POS/E1 reception.
4. Network processor sub-card which has worked normally is loose.
Handling Suggestion
1. Pull out/insert in the fiber/network cables to check if the fault is eliminated.
2-123
SJ-20100603155704-004|2011-02-26(R3.0)
2. Replace fiber/network cables to check if the fault is eliminated.

3. Restart the board to check if the fault is eliminated.
4. Pull out/insert the board to check if the fault is eliminated.
5. Replace the board to check if the fault is eliminated.
Alarm Impact
Datagram reception of the board is affected. The service on the board might be unstable.
2.2.43 198029953 The Ethernet port state is OAM loop back

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
The local port state is loop back because the peer port starts Ethernet OAM loop back
request of 802.3ah.
Handling Suggestion
Check if the peer port has started Ethernet OAM loop back test. If yes, stop it, if no, disable
local port Ethernet OAM.
Alarm Impact
The Ethernet link which is in loop back test can't bear service data.
2-124
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
2.2.44 198066066 AAL2 Path locally blocked

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
The Path is manually blocked from this AAL2 Node.
Handling Suggestion
You can unblock the Path which is generated manually from the operating interface.
Alarm Impact
2.3 Processing Alarm

2.3.1 198083020 Token control overload alarm
Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
2-125
SJ-20100603155704-004|2011-02-26(R3.0)
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
Access of current services in the system reaches the limit of system processing capacity.
Handling Suggestion
If possible, perform system capacity expansion.
Alarm Impact
To protect the quality of current services, access of new UE service is denied.
2.3.2 198083022 Cell is out of service

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
Yes
2-126
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Frequently Reported
Yes
Probable Cause
1. Node B returns the message that the cell fails to be established.
2. Cell Configuration Generation ID (CGID) audited by Node B is zero.
3. Real-time cell blockage is performed at Node B side.
4. The failure to update system message results in cell deletion and creation.
5. The cell parameters configured at RNC side is incorrect.
Handling Suggestion
On NMS fault management interface, view the alarm details, which give the alarm cause.
You can quickly locate the handling method according to the alarm cause. The handling
suggestions for each alarm type are as follows:
1. Alarm reason: Node B setup cell failed.
a. Check if the frequency points of RNC and Node B are consistent with the local cell
ID. Do as follows: On NMS configuration management interface, select the cell to
be viewed under Base Station Radio Resource Management > WCDMA Radio
Resource Management > Baseband Resource Pool. Check if the values of
Local Cell ID, Receiving Frequency Point, and Transmitting Frequency Point
in Local Cell Basic Parameters are consistent with those at RNC side. If not,
modify the RNC or Node B configurations to make them consistent.
b. On NMS fault management interface, check if Node B has generated 198084129
Board reboots alarm. If yes, it indicates that the Node B has just been started or
hardware has been just replaced or added. In this case, wait for the Node B to
finish powering on.
2. Alarm reason: Cell CGID is zero audit by NodeB.
a. Local cell is blocked.
On NMS configuration management interface, select the cell to be viewed under
Base Station Radio Resource Management > WCDMA Radio Resource
Management > Baseband Resource Pool. View the Status in Local Cell Status
Parameters. If the status is blocked, unblock it.
b. Node B is blocked or faulty.
On the ground resource configuration interface, view Node B status. If the status
is blocked, unblock the Node B. If the status is faulty, it indicates that FS board may
be faulty. In this case, check if related alarms exist. If yes, follow the suggestions
on handling the related alarms.
Related alarms:
l
198084117 Application software monitoring alarm

2-127
SJ-20100603155704-004|2011-02-26(R3.0)
l
l
c.
198084123 Board communication link is interrupted

198084107 Board parameter synchronization abnormity
Local cell is faulty.

View the Local Cell Status Parameters interface. If the current status is faulty, it
indicates that FS board or RTR board is faulty or restarted. In this case, check if
the following alarms are generated. If yes, follow the suggestions on handling the
related alarms:
l
l
l
l

198084129 Board reboots alarm
d. Baseband board is blocked.

View the BPC board status. If the status is blocked, unblock it.
e. Baseband board is faulty
View the BPC board status. If the status is faulty, handle the alarm by referring to
the following related alarm suggestions:
l
l
l
l

198084129 Board reboots alarm
3. Alarm reason: Cell is blocked at NodeB side. On NMS configuration management

interface, select the cell to be viewed under Base Station Radio Resource
Management > WCDMA Radio Resource Management > Baseband Resource
Pool. If the cell status is blocked, unblock it.
4. Alarm reason: System information update fail. The alarm is caused by the failure to
update system messages, that is, system message broadcast fails. Handle the alarm
by referring to the suggestion for 198070009 Broadcast fail.
5. Alarm reason: The cell parameters configured at RNC side is incorrect. On NMS
configuration management interface, select the RNC Radio Resource Management
> Service Cell, check the cell parameters as follows:
a. Cell Capability and Cell Reselect Parameters
b. Senior Parameters: Load Control, Balance Parameters, Accept Control, Hspa
Configure, Mbms Configure.
6. For other alarm causes, the system re-establishes the cell automatically. No human
intervention is required.
Alarm Impact
The cell is unavailable and fails to provide services. Users fail to gain access through this
cell.
2-128
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
2.3.3 198083023 Node B is out of service

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
Yes
Frequently Reported
Yes
Probable Cause
The transmission is faulty.
Handling Suggestion
The handling suggestions classified by transmission mode are as follows:
1. IP mode
According to the association link number, check if alarms related to association
links exist through the fault management interface. If yes, follow the suggestions on
handling the related alarms.
Related alarms:
l
l

2. ATM mode
a. Bottom layer link fault Check if related alarms exist on the board. If yes, follow the
Related alarms:
l
l
l

198066048 SDH/SONET:Excessive Error Code
2-129
SJ-20100603155704-004|2011-02-26(R3.0)
b. Unavailable PVC Check if related alarms exist on the board. If yes, follow the
Related alarm:
198018944 PVC Fault
Alarm Impact
The Node B is unavailable and fails to provide services. Users fail to gain access through
this Node B.
2.3.4 198083024 GPS receiver on ICM is abnormal

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. GPS subcard is not tightly inserted.
2. Hardware of GPS subcard is faulty.
Handling Suggestion
1. Unplug and plug GPS subcard.
2. Replace GPS subcard.
2-130
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Alarm Impact
GPS subcard mainly provides positioning function for RNC NE. The subcard fault leads to
handset positioning failure. Service is not affected.
2.3.5 198018944 PVC CC timeout

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. PVC connection for the equipment is loose or disconnected. PVC connection falls into
the following three types:
l Fiber connection, carried by optical interface.
l E1/T1 connection, carried by IMA port.
l Fiber connection, carried by IMA port.
2. Continuity Check(CC) test is started at local end, but not started at opposite end.
Handling Suggestion
1. On NMS fault management interface, view alarm Details where PVC ID is given.
Locate the faulty port according to the given information. For example, the PVC
ID given in alarm Details is 1. On NMS configuration management interface(PVC
configuration), try to locate the PVC whose ID is 1. View the related subsystem No.,
unit No., ATM port No. to locate the corresponding interface board and port.
2. Check the relevant equipment based on the physical bearer of the port.
2-131
SJ-20100603155704-004|2011-02-26(R3.0)
a. If the faulty PVC port is carried by optical interface, ensure that the fiber connector
and interface are in good contact, or replace the fiber.
b. If the faulty PVC port is carried by IMA port, check if the following alarms occur to
the corresponding IMA group/link. If yes, refer to the corresponding alarm handling
suggestion.
Related alarms:
l
l
l
l
198019207 Near-End IMA Group Configuration Failure

198019213 LIF Alarm of Near-End Receiving Link
198019214 LODS Alarm of Near-End Receiving Link
198019215 RDI Alarm of Near-End Receiving Link
3. Check if the equipment power-on at opposite end is successful. If no, refer to the
maintenance manual of opposite equipment for troubleshooting.
4. Check if the PVC status at opposite end is successful. If no, refer to the maintenance
manual of opposite equipment for troubleshooting.
5. Deactivate CC test at local end, or activate CC test at opposite end. For IMAB/APBE
board: To deactivate CC test at local end, initiate PVC CC test on NMS test
management interface. When configuring test parameters, select 0: Deactivate CC
for activation type; select 1: B-A for test type(A indicates local end and B indicates
opposite end). To activate CC test at opposite end, initiate PVC CC test on NMS
test management interface. When configuring test parameters, select 1: Activate
CC for activation type; select 1: B-A for test type. For APBE2/DTA board: Modify
PVC CCINFO parameter of configuration to active or deactivate CC test. CC test
parameter is same to APBE/IMAB.
Alarm Impact
PVC is in faulty status. All services on the PVC are interrupted.
2.3.6 198019207 Near-End IMA Group Configuration Failure

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
2-132
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Disaster Alarm
No
Frequently Reported
No
Probable Cause
IMA group configuration at local end and at opposite end is inconsistent.
Handling Suggestion
On NMS fault management interface , view alarm Details where information of the
faulty IMA group is given. On NMS configuration management interface(IMA group
configuration), locate the corresponding IMA group according to the information given in
alarm Details. Compare the configuration of the following parameters at both ends:
l
l
l
l
Near-End OMA Label

Rx Frame Length(cells)
Tx Frame Length(cells)
Near-End Symmetry
If the configuration at both ends is inconsistent, modify configuration at either end to keep
consistency.
Alarm Impact
All services on the IMA port are interrupted.
2.3.7 198015360 Microcode Is Abnormal

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
Yes
2-133
SJ-20100603155704-004|2011-02-26(R3.0)
Frequently Reported
No
Probable Cause
Network Processor hardware is faulty.
Handling Suggestion
Wait for the board to reboot. If the alarm cannot be restored after board rebooting, unplug
and then plug the board. If the alarm still cannot be restored, replace the board.
Alarm Impact
The board will reboot.
l
If the alarm can be restored after board rebooting, all board services during
rebooting will be down, but access of new services to the board after rebooting
will be successful.
If the alarm cannot be restored after board rebooting, all board services during
and after rebooting will be down.
2.3.8 198023040 The number of board alarms exceeds the threshold

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
There are too many alarms for this board. The alarm pool is full of board alarms.
2-134
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Handling Suggestion
Troubleshoot the current alarms in the system.
Alarm Impact
Alarm information loss might occur. No impact on user service.
2.3.9 198066031 The number of OMP alarms exceeds the threshold

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
There are too many system alarms. The alarm pool is full of system alarms.
Handling Suggestion
Delete the trivial alarms on NMS fault management interface.
Alarm Impact
Alarm information loss might occur. No impact on user service.
2.3.10 198066032 NTP time exceeds threshold

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

Alarm Type
Processing Alarm
2-136
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. SNTP server does not exist or server operation is abnormal.
2. The configured SNTP IP address in the database is inconsistent with the real IP
address.
3. Communication between RNC NE and SNTP server is down.
4. The time synchronization period configured in the database might be 0.
Handling Suggestion
On NMS fault management interface, view alarm Details where Alarm Reason is given.
Locate the specific handling suggestion according to the given reason. The handling
suggestions that correspond to different alarm reasons are described below:
1. Illegal DB configuration. On NMS configuration management interface(RNC ground
resource management), check if SNTP server IP address or SNTP synchronization
period are incorrectly configured. If yes, which means SNTP server IP is configured
as 255.255.255.255 or SNTP synchronization period is 0, correct the configuration.
2. Failed to get time from SNTP server.
a. Ensure that SNTP server exists and server operation is normal.
b. Ensure that the configured SNTP server IP address in the database and the real
server IP are consistent.
Alarm Impact
SNTP synchronization failure might lead to inconsistency between system time and real
time. For example, the real time is 1:00 am, but the displayed system time is 2:00 am.
Since system clock frequency is correct, service will not be affected.
2-137
SJ-20100603155704-004|2011-02-26(R3.0)
2.3.12 198005387 Alarm Due to Inconsistent MP Type

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
1. The MP type is changed on NMS and the board is not restarted.
2. The active MP type on the local board is not consistent with that configured on NMS.
Handling Suggestion
1. For CMP and SMP, reset the board through the MML command of the NMS.
2. For OMP, set the start mode as "foreground start" on NMS and then reset the board.
Do as follows: On NMS software version management interface, select the menu for
querying foreground (that is, RNC NE) board start mode. In the pop up dialog box, set
the start mode to "foreground start".
Alarm Impact
This alarm has no effect on the service.
2.3.13 198005388 Startup File Does Not Exist

Alarm Type
Processing Alarm
2-138
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
The startup configuration file is deleted.
Handling Suggestion
1. Reset the active and standby OMPs through the MML command of the NMS.
Alarm Impact
This alarm may cause OMP work abnormally, and the entire NE services are affected.
2.3.14 198005398 Inconsistent Office ID Settings of DIP Switch

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
2-139
SJ-20100603155704-004|2011-02-26(R3.0)
Disaster Alarm
No
Frequently Reported
No
Probable Cause
The office ID setting of this shelf is different from that of the shelf where OMP is located.
Handling Suggestion
Set the office ID through the DIP switch in this shelf to that of the shelf where OMP is
located.
Alarm Impact
The MAC addresses conflict. The board MAC and IP address verification fails. All boards
in the shelf cannot be powered on. All services carried by the shelf are interrupted.
2.3.15 198005649 Port Work Mode Doesn't Match Settings

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. The local device does not support this mode setting.
2-140
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
2. The peer device does not support this mode setting.
Handling Suggestion
On NMS fault management interface, view the alarm details, which give the reason of
mode error. You can quickly locate the handling method according to the reason of mode
error. The handling suggestion for each reason of mode error is as follows:
1. Speed mode error
a. Determine the rate to be configured. Replace the existing board with the one
supporting the configured rate mode.
b. For Force mode, configure the port with the rate supported by the bottom layer
in actual working status. Do as follows: On NMS configuration management
interface, set the rate in subunit details to the rate supported by the bottom layer
in actual working status.
c.
For Auto mode, re-configure the expected rate and ensure that it is consistent with
the actual port rate. Do as follows: On NMS configuration management interface,
set the rate in subunit details to the expected one.
2. Duplex mode error

a. Determine the required mode. Replace the existing board with the one supporting
the mode configured on RNC.
b. For Force mode, configure the port with the duplex mode supported by the bottom
layer in actual working status. Do as follows: On NMS configuration management
interface, set the Work Mode in subunit details to the work mode supported by the
bottom layer in actual working status.
c.
For Auto mode, re-configure the expected duplex and ensure that it is consistent
with the actual port duplex. Do as follows: On NMS configuration management
interface, set the work mode in subunit details to the expected one.
3. GE port master and slave mode error

a. Determine the required master and slave mode. Replace the existing board with
the one supporting the master and slave mode configured on RNC.
b. For Force mode, configure the port with the master and slave mode supported by
the bottom layer in actual working status. Do as follows: On NMS configuration
management interface, set the GE port master and slave mode in subunit details
to the master and slave mode supported by the bottom layer in actual working
status.
c.
For Auto mode, re-configure the expected master and slave mode and ensure
that it is consistent with the actual port master and slave mode. Do as follows:
On NMS configuration management interface, set the GE port master and slave
mode in subunit details to the expected one.
2-141
SJ-20100603155704-004|2011-02-26(R3.0)
Alarm Impact
1. The port fails to work in the preset mode. This causes the port to be unavailable and
all services of the port are interrupted.
2. For Auto mode, the bandwidth of the external port becomes insufficient. As a result,
some services of the port are interrupted.
2.3.16 198005123 DB Configuration Doesn't Fit for Device

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. The type of physical board is incorrectly configured.
2. A wrong board is inserted.
Handling Suggestion
1. The NMS configuration management interface gives the rack diagram. Select the
board and check if the board and subunit settings of rack are correct. If the settings
are incorrect, delete the board and create a new one.
2. Check if a correct board is inserted in the slot on the rack. If not, insert the correct one.
Alarm Impact
The board where this alarm occurs fails to be normally powered on. The services carried
by this board are interrupted.
2-142
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
2.3.17 198066006 Broadband link congestion

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
1. The configured signaling PVS bandwidth is insufficient.
2. Bottom-layer physical transmission quality is poor.
Handling Suggestion
1. Check the counter of "Peak Traffic of Signaling Link" in MTP3B signaling link
performance statistics. If the load (nearly) reached 6000 during alarm occurrence,
upper layer traffic must be heavy. Increase PVC bandwidth or add links to share load.
2. Check NMS alarms/notifications to see whether there exists physical transmission
alarm(s) /notification(s) that occurred simultaneously with this alarm. If yes, refer to
the corresponding alarm handling suggestion. Alarms/Notifications related to physical
transmission are listed below, with respect to access mode.
l Fiber Access Mode
198066048 SDH/SONET:Excessive Error Code
E1 Access Mode
198005647 High Error Rate at E1 Bottom Layer

2-143
SJ-20100603155704-004|2011-02-26(R3.0)
198000576 Trunk Slide
3. Check the performance statistics of SSCOP link. Check if there was message
retransmission of "Number of PDU Retransmitted" during alarm occurrence. If yes,
packet loss must have occurred during transmission. Since packet loss might occur
at opposite end, ask opposite end to cooperate in troubleshooting.
Alarm Impact
Link congestion leads to transmission delay. If congestion is not serious, service will not
be affected. Otherwise, packet loss or call loss might occur, and access success rate of
PS service might fall.
2.3.18 198066013 MTP3 link congestion

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
1. There are too many upper layer service messages.
2. Bottom layer link quality is poor, leading to frequent message retransmission.
Handling Suggestion
1. Add links to the office that is in service for the congested link.
2-144
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
2. Take the following measures to improve transmission quality of physical links. Replace
bottom layer links. Ensure that connector contact and cable connection are normal.
Alarm Impact
Link congestion leads to transmission delay. If congestion is not serious, service is not
affected. Otherwise, packet loss or call loss might occur, and access success rate of PS
service might fall.
2.3.19 198066018 Association congestion

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. Transmission quality of bottom layer link is poor.
2. Upper layer traffic in sending service data is heavy.
Handling Suggestion
1. Check network cable connection. Ensure that the network cable is tightly inserted.
2. Add association links to the office that is in service for the congested association.
3. If intermediate equipment exists between local end and opposite end, check the
transmission quality of intermediate equipment.
2-145
SJ-20100603155704-004|2011-02-26(R3.0)
Alarm Impact
Transmission delay, or even packet loss will occur. If congestion is not serious, service will
not be affected. Otherwise, call loss might occur, and access success rate of PS service
might fall.
2.3.20 198005402 Database config is different from file named

bootcfg.ini
Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
After the start information of OMP is modified, the active and standby OMP boards are not
restarted.
Handling Suggestion
Restart the active and the standby OMP boards at the same time.
Alarm Impact
System startup is abnormal, MP may not work normally.
2-146
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
2.4 Environment Alarm

2.4.1 198025856 Rack temperature is higher than high threshold
Alarm Type
Environment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
1. Threshold configuration is unreasonable.
2. Actual rack temperature is too high.
Handling Suggestion
1. On NMS configuration management interface (power board alarm parameters),
check the upper limit of rack temperature. Modify the threshold value if the previous
configuration is unreasonable. The recommended upper threshold value is 70.
2. Check the thermometer in equipment room to see if the actual temperature is too high.
If yes, take necessary cooling measures.
3. Remove dust at the air inlet and outlet of the rack. Remove the nearby object that
obstructs rack ventilation.
4. Ensure that the rack fan works normally.
Alarm Impact
1. If the alarm is caused by unreasonable threshold configuration, service will not be
affected.
2-147
SJ-20100603155704-004|2011-02-26(R3.0)
2. If the alarm is caused by high rack temperature, board operation might be abnormal
and board services might be interrupted.
2.4.2 198025857 Rack temperature is lower than low threshold

Alarm Type
Environment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
2. Actual rack temperature is too low.
Handling Suggestion
1. On NMS configuration management interface (power board alarm parameters),
check the lower limit of rack temperature. Modify the threshold value if the previous
configuration is unreasonable. The recommended low threshold value is 0.
2. Check the thermometer in equipment room to see if the actual temperature is too low.
If yes, take necessary warming measures.
Alarm Impact
affected.
2. If the alarm is caused by low rack temperature, board operation might be abnormal
2-148
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
2.4.3 198025858 House temperature is higher than high threshold

Alarm Type
Environment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
2. Actual temperature in equipment room is too high.
Handling Suggestion
1. On NMS configuration management interface (power board alarm parameters), check
the upper limit of equipment room temperature. Modify the threshold value if the
previous configuration is unreasonable. The recommended high threshold value is
40.
If yes, take necessary cooling and ventilation measures.
Alarm Impact
affected.
2. If the alarm is caused by high room temperature, board operation might be abnormal
2-149
SJ-20100603155704-004|2011-02-26(R3.0)
2.4.4 198025859 House temperature is lower than low threshold

Alarm Type
Environment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
2. Actual temperature in equipment room is too low.
Handling Suggestion
the lower limit of equipment room temperature. Modify the threshold value if the
previous configuration is unreasonable. The recommended low threshold value is 0.
If yes, take necessary cooling and ventilation measures.
Alarm Impact
affected.
2. If the alarm is caused by low room temperature, board operation might be abnormal
2-150
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
2.4.5 198025860 Voltage is higher than high threshold

Alarm Type
Environment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
2. Actual voltage is too high.
Handling Suggestion
the upper limit of rack voltage. Modify the threshold value if the previous configuration
is unreasonable. For 48 V power, the recommended high threshold value is 57. For
60 V power, the recommended value is 72.
2. Locate the specific line which voltage is over the threshold according to the voltage
index listed in the alarm details. Reduce the input voltage of that line by reducing the
power supply's output voltage.
Alarm Impact
affected.
2. If the alarm is caused by high voltage, board operation might be abnormal and board
services might be interrupted.
2-151
SJ-20100603155704-004|2011-02-26(R3.0)
2.4.6 198025861 Voltage is lower than low threshold

Alarm Type
Environment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
2. Actual voltage is too low.
Handling Suggestion
1. On NMS configuration management interface(power board alarm parameters), check
the lower limit of rack voltage. Modify the threshold value if the previous configuration
is unreasonable. For 48 V power, the recommended low threshold value is 40. For 60
V power, the recommended value is 50.
2. Locate the specific line whose voltage is below low threshold according to the voltage
index listed in alarm details. Increase the input voltage of that line.
Alarm Impact
affected.
2. If the alarm is caused by low voltage, board operation might be abnormal and board
services might be interrupted.
2-152
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
2.4.7 198025862 Humidity is higher than high threshold

Alarm Type
Environment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
2. Actual humidity in equipment room is too high.
Handling Suggestion
the upper limit of equipment room humidity. Modify the threshold value if the previous
configuration is unreasonable. The recommended high threshold value is 90.
2. Check the hygrometer in equipment room to see if the actual humidity is too high. If
yes, take necessary dehumidifying measures.
Alarm Impact
affected.
2. If the alarm is caused by high room humidity, board operation might be abnormal and
board services might be interrupted.
2-153
SJ-20100603155704-004|2011-02-26(R3.0)
2.4.8 198025863 Humidity is lower than low threshold

Alarm Type
Environment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
2. Actual humidity in equipment room is too low.
Handling Suggestion
the lower limit of equipment room humidity. Modify the threshold value if the previous
configuration is unreasonable. The recommended low threshold value is 20.
2. Check the hygrometer in equipment room to see if the actual humidity is too low. If
yes, take necessary humidifying measures.
Alarm Impact
affected.
2. If the alarm is caused by low room humidity, board operation might be abnormal and
board services might be interrupted.
2-154
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
2.4.9 198025864 Fault in fan plug-in box

Alarm Type
Environment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
1. FAN module is not tightly inserted into the rack.
2. FAN module hardware is faulty.
Handling Suggestion
1. Check if the FAN module is tightly inserted into the rack. If no, unplug and plug the
FAN module.
2. Replace FAN module.
Alarm Impact
This alarm might lead to excessively high rack temperature, resulting in abnormal board
operation and interruption of board services
2.4.10 198025865 Rack door alarm

Alarm Type
Environment Alarm
2-155
SJ-20100603155704-004|2011-02-26(R3.0)
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
1. The rack door is not closed.
2. Door control connection is incorrect.
Handling Suggestion
1. Open and re-close the rack door to ensure that the rack door is tightly closed.
2. Open the rack door to check the installation of door control. Ensure that the door
access control is correctly installed and connected. Then close the rack door.
Alarm Impact
Service is not affected, but the alarm poses a potential safety hazard.
2.4.11 198025866 Smog alarm

Alarm Type
Environment Alarm
Alarm Purpose
External Alarm
Alarm
2-156
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Severity
Minor
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
1. The alarm is faulty.
2. The smog density in equipment room is too high.
Handling Suggestion
1. Locate and handle the smog origin as soon as possible.
2. If no smog exists in the equipment room, replace the smog detector.
Alarm Impact
Service is not affected, but the alarm poses a potential safety hazard and needs to be fixed
immediately.
2.4.12 198025867 Infrared alarm

Alarm Type
Environment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
Yes
2-157
SJ-20100603155704-004|2011-02-26(R3.0)
Frequently Reported
No
Probable Cause
1. Heat source(such as animal/human) comes near.
2. Infrared sensor is faulty.
Handling Suggestion
1. Check if any animal or human comes near the infrared sensor. If yes, remove the heat
source. If no, check the infrared sensor configuration. If appropriate, sensor sensitivity
can be somewhat reduced.
2. The infrared sensor is faulty. Replace sensor.
Alarm Impact
1. If the alarm is caused by infrared sensor configuration error, system is not affected.
2. If the alarm is caused by infrared over threshold, be careful of potential safety hazard
in the equipment room.
2.4.13 198025868 Lightning alarm

Alarm Type
Environment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
Yes
Frequently Reported
No
2-158
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Probable Cause
In bad weather, the equipment room is hit by lightning stroke.
Handling Suggestion
1. Check earthing connection.
2. Check lightning protection antenna.
Alarm Impact
The board operation might be abnormal due to the lightning stroke. Interruption of board
services might occur.
2.4.14 198025869 Loss of DC power supply to rack

Alarm Type
Environment Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. Circuit breaker has tripped.
2. No incoming DC supply from rectifier.
Handling Suggestion
Is this shelf needed?
If yes, ensure that the atmosphere switch is closed and ALM indicator is normal.
2-159
SJ-20100603155704-004|2011-02-26(R3.0)
If no, screen the function of monitoring atmosphere switch. In NMS Configuration

Management interface, click Power Board Alarm Parameters; then set the status of
atmosphere switch to be screened.
Setting the sensor correctly.
Alarm Impact
This shelf can not be supplied with power. All boards on the shelf can not work and board
services are interrupted.
2.5 QoS Alarm

2.5.1 198023296 Inter-board message communication flow rate
exceeds the alarm threshold
Alarm Type
QoS Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
The configured alarm threshold is less than the usual inter-board communication traffic in
input and output directions of the board control plane.
2-160
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Handling Suggestion
On NMS configuration management interface, check if the configured alarm threshold of
communication traffic in input and output directions of the board control plane is too low.
Recommended value: 0xffffffff(4096M).
Alarm Impact
No impact on user service.
2.5.2 198066069 The number of times of signaling data transfer

exceeds the allowed threshold of the license
Alarm Type
QoS Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
Yes
Probable Cause
1. The number of allowed times of transfer is less than the actual demand.
2. No proper license purchased.
Handling Suggestion
1. Set the number of allowed times of transfer to a rational value.
2. Purchase proper license.
Alarm Impact
The data transferred may be discarded
2-161
SJ-20100603155704-004|2011-02-26(R3.0)
2.5.3 198083051 IU PS traffic over load alarm

Alarm Type
QoS Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
IU PS traffic throughput exceed the threshold of license control.
Handling Suggestion
Check if the whole throughput is over the provider's guaranteed bandwidth limit authorized
by license.
Alarm Impact
The traffic over the license threshold would cause packet loss and service quality decrease.
2.5.4 198083052 IU CS traffic over load alarm

Alarm Type
QoS Alarm
Alarm Purpose
External Alarm
2-162
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Alarm
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
IU CS traffic throughput exceed the threshold of license control.
Handling Suggestion
by license.
Alarm Impact
The traffic over the license threshold would cause user service access reject.
2.5.5 198083053 IU traffic over load alarm

Alarm Type
QoS Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Minor
Disaster Alarm
No
2-163
SJ-20100603155704-004|2011-02-26(R3.0)
Frequently Reported
No
Probable Cause
IU CS and PS traffic throughput exceed the threshold of license control.
Handling Suggestion
by license.
Alarm Impact
The traffic over the license threshold would cause CS user service access reject or PS
service quality decrease.
2.5.6 198015361 Ring and queue overload alarm

Alarm Type
QoS Alarm
Alarm Purpose
External Alarm
Alarm
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
Service overload in the board.
Handling Suggestion
You should readjust board's resource to reduce service load in this board.
2-164
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 2 Alarm
Alarm Impact
Service quality will get bad, even make service lost.
2-165
SJ-20100603155704-004|2011-02-26(R3.0)
2-166
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 3
Notification
Table of Contents
198083017 the route table of MicroCode subsystem of this board is overloaded ........3-3
198070002 Iu interface global reset notification ..........................................................3-4
198070003 Iu interface resource reset notification......................................................3-5
198070004 RNC started Iu interface global reset failure notification ...........................3-6
198070005 RNC started Iu interface resource reset failure notification .......................3-7
198070008 RNC and Node B CCPID configuration are not identical ..........................3-8
198070009 Broadcast fail...........................................................................................3-9
198083025 Common Channel is abnormal...............................................................3-10
198070010 OMCR failed to fetch FTP file ................................................................3-12
198070011 File operation failure between OMCR and RNC NE ...............................3-12
198083028 Logservice is unavailable .......................................................................3-13
198083029 Performance file store failed ..................................................................3-14
198083019 MicroCode subsystem failed to get the table of configuration .................3-16
198083026 MicroCode subsystem failed to handle DHCP message from other
network ....................................................................................................................3-18
198083030 Bandwidth automatic adjustment is useless ...........................................3-20
198083032 TCP connect on IuBC interface establishment failed. .............................3-21
198083033 Clock Deviation over threshold notification.............................................3-22
198083034 External Clock of Slave lost notification..................................................3-23
198083037 All Local Cell ID configured at RNC side are differ from which on Node
B side.......................................................................................................................3-24
198020291 Protocol stack process failed to initialize during power on ......................3-25
198020802 Conflicting IP addresses ........................................................................3-25
198020803 Conflicting MAC Addresses in Subnet....................................................3-27
198020804 Failed to generate static ARP from IP address.......................................3-28
198030016 Ethernet link OAM event ........................................................................3-29
198000576 Trunk Slide ............................................................................................3-29
198001600 One of CPUs on One of Boards in This Shelf Resets (Exceptionally) .....3-30
198017216 Error in MCS Multi-Core processor receiving configuration data from
DBS .........................................................................................................................3-31
198018240 TCP Receives RST Packet ....................................................................3-32
198018241 TCP Connection Aborted .......................................................................3-33
198018242 MD5 Verification Failure .........................................................................3-34
198018243 Wrong MD5 Message Abstract ..............................................................3-34
198023106 Board self-check fails.............................................................................3-35
198023107 The board initialization failure ................................................................3-36
198023617 Configuration file is unusable .................................................................3-37
3-1
SJ-20100603155704-004|2011-02-26(R3.0)
198003138 FLASH device initialize failed .................................................................3-38

198003394 Entering Daylight Savings Time .............................................................3-39
198003395 Quitting Daylight Savings Time ..............................................................3-39
198005441 Port status on internal media plane changed..........................................3-40
198005448 485 Set Failure ......................................................................................3-41
198026177 CLKG reference quality changed ...........................................................3-42
198026178 Clock work mode changed.....................................................................3-43
198005705 MCU resets for abnormities ...................................................................3-44
198005710 The result of base selection of sets chip.................................................3-44
198005711 The action of select base is working.......................................................3-45
198005712 The manual select base will be run, please wait for the result ................3-46
198005713 APC's RAM error ...................................................................................3-47
198005715 PP2S source switched ...........................................................................3-48
198005716 Type B fault on board (GPS) phase-lock equipment...............................3-48
198005700 DSP resets for abnormities ....................................................................3-50
198005701 Version Load Error.................................................................................3-51
198019777 APS Switchover Happens ......................................................................3-52
198005188 UIM CS Changeover..............................................................................3-53
198005192 Board's Work Mode Unsupported ..........................................................3-54
198005193 Notification of the power-on status of the basic process .........................3-55
198005956 Board Version Error ...............................................................................3-56
198005958 IDE Version Files Synchronization Information.......................................3-57
198005961 OMP Version Check Information ............................................................3-58
198005962 Patch version operate fail.......................................................................3-59
198010560 No message response in the link for a long time ....................................3-60
198011840 M3UA user office status change.............................................................3-61
198013888 ASP status changed ..............................................................................3-62
198013889 AS status changed.................................................................................3-63
198013890 Sigtran error message received .............................................................3-64
198013891 Sigtran notification message received....................................................3-65
198013892 Allocate memory fail...............................................................................3-66
198014144 Association establishment failed ............................................................3-67
198014145 Association restart .................................................................................3-68
198025664 Abnormal Half-fixed Connection Changes..............................................3-69
198008005 Memory file buffer overflow ....................................................................3-70
198083046 DSP memory check fail notification ........................................................3-71
198083047 TCP connect on IuBC interface is interrupted ........................................3-72
198015168 AAL2 Path blocked by resetting process ................................................3-73
198020805 ARP detect failed ...................................................................................3-74
198020806 ARP detect that the static ARP is not match...........................................3-74
198026176 Clock reference changed .......................................................................3-75
198026179 Clock source invalidation reason changed .............................................3-76
198028993 SCTP Primary Path Set Failed...............................................................3-77
198031040 ACL config failed....................................................................................3-78
198000834 MCC is faulty .........................................................................................3-79
3-2
SJ-20100603155704-004|2011-02-26(R3.0)
Chapter 3 Notification
198002625 Process is deadlocked. ..........................................................................3-79

198002880 CPU dead-loop ......................................................................................3-80
198003650 The data in user buffer is corrupted........................................................3-81
198005189 Notification of Active/Standby Changeover ...........................................3-82
198005195 Board mix plug occurred ........................................................................3-83
198005718 Two master clock ports is directly connected..........................................3-84
198005719 FPGA receive/send packets abnormally.................................................3-85
3.1 198083017 the route table of MicroCode subsystem

of this board is overloaded
Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
There are too many configured route entries For RUB board (VTCD), the table can contain
at most 360 route entries. For RUB board (VTCD_2), the table can contain at most 1024
route entries. The alarm is declared when the number of route entries reaches 90% of the
table capacity threshold.
Handling Suggestion
1. On NMS configuration management interface(static route), delete the routes that are
not in use.
2. On NMS configuration management interface(interface configuration), delete the port
IP that is no longer in use.
3-3
SJ-20100603155704-004|2011-02-26(R3.0)
Alarm Impact
1. If the number of route entries does not exceed the RUB board route table capacity,
service will not be affected.
2. If the number of route entries exceeds the RUB board route table capacity, information
of some route entries will be invalid.
a. If the missing route are the route to Node B or CN, UE service access to the board
will fail.
b. If the missing route are the route to other RNC NE, access of Inter-RNC UE
services to the board will fail. Meanwhile, tick clock synchronization of the MBMS
service between the relevant RNC NEs will fail, degrading the MBMS service
quality.
3. If the number of route entries exceeds the RUB board route table capacity, the SLA
diagnostic test function from RNC to related NE will be disabled.
3.2 198070002 Iu interface global reset notification

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. RESET message is sent by CN.
2. The signaling point of the office related to the CN is inaccessible.
3. Global reset is triggered by NMS.
3-4
SJ-20100603155704-004|2011-02-26(R3.0)
Handling Suggestion
On NMS fault management interface, view notification Details where Alarm Reason is
given. Locate the specific alarm handling suggestion according to the given reason. The
handling suggestions that correspond to different reasons are described below.
1. CN reset.
a. RESET message is initiated by CN NMS. View CN NMS operation log to see if the
reset is initiated. If yes, no handling is necessary.
b. Check if transmission-related/board alarm occurs in the board. If yes, refer to the
Related alarms:
l
l
l
198066005 SCCP SSN is invalid

2. CN inaccessible. Check if transmission-related/board alarm occurs. If yes, refer to the

Related alarms:
l
l
l

3. OMCR initiate IU reset. The alarm is caused by manual reset operation. Check RNC
NMS operation log to see if the reset operation exists. If yes, no handling is necessary.
Alarm Impact
The services that have been established are released. Access of new service is denied.
Service access will be restored in 3 seconds.
3.3 198070003 Iu interface resource reset notification

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
3-5
SJ-20100603155704-004|2011-02-26(R3.0)
Disaster Alarm
No
Frequently Reported
No
Probable Cause
RESET RESOURCE message is sent by RNC.
Handling Suggestion
Check if transmission-related/board alarm occurs. If yes, refer to the corresponding alarm
Related alarms:
l
l
l

Alarm Impact
The interface service that initiates resource reset is released.
3.4 198070004 RNC started Iu interface global reset

failure notification
Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
3-6
SJ-20100603155704-004|2011-02-26(R3.0)
Frequently Reported
No
Probable Cause
RNC fails to receive reset response message from CN.
Handling Suggestion
On NMS configuration management interface(MSC SERVER/SGSN in transmission
configuration), check if the MCC and MNC configured by RNC and that configured by
CN are consistent. If no, modify configuration to keep consistency.
Alarm Impact
New services will be rejected for 3 seconds.
3.5 198070005 RNC started Iu interface resource reset

failure notification
Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
RNC fails to receive resource reset response message from CN.
3-7
SJ-20100603155704-004|2011-02-26(R3.0)
Handling Suggestion
On NMS configuration management interface(MSC SERVER/SGSN in transmission
configuration), check if the MCC and MNC configured by RNC and that configured by
CN are consistent. If no, modify configuration to keep consistency.
Alarm Impact
No impact on service.
3.6 198070008 RNC and Node B CCPID configuration

are not identical
Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
The CCP ID configured on RNC side and on Node B side is inconsistent.
Handling Suggestion
Click NE Information Configuration on the NMS Configuration Management interface.
Select the corresponding Node B and modify its CCP ID in Node B port configuration.
Alarm Impact
The relevant CCP is unavailable during service establishment.
3-8
SJ-20100603155704-004|2011-02-26(R3.0)
3.7 198070009 Broadcast fail

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
Yes
Frequently Reported
Yes
Probable Cause
1. Configuration related to the system broadcast information of the cell is incorrect.
2. Transmission is faulty.
Handling Suggestion
On NMS fault management interface, view notification Details where Alarm Reason
is given. Locate the specific handling suggestion according to the given reason. The
handling suggestions that correspond to the reasons are described below:
1. Alarm reason: Get system information from database failed. View notification Details
where bySIBType information is given. For example, SIB type=1 indicates fetching
failure of Sib1. Check if the Sib1-related parameter configuration is correct and if the
configuration exists in the cell. The mapping relationship between SIB type and the
configuration required to be checked is listed below:
a. SIB type=1 On NMS configuration management interface(UE timers and constants
information), check UE timers and counters in idle and connected status.
b. SIB type=2 On NMS configuration management interface(UTRAN cell), check
URA ID in UTRAN cell global information.
c.
SIB type=3 On NMS configuration management interface(cell selection and

reselection), check cell selection/reselection information parameters and cell
access limit parameters.
3-9
SJ-20100603155704-004|2011-02-26(R3.0)
d. SIB type=5 On NMS configuration management interface(UTRAN cell), check

common transport channel parameters in SCCPCH and RACH.
2. Alarm reason: Exceed system broadcast ability. The notification might be caused by
transmission fault. Check if transmission-related alarm exists in the Node B that the
cell belongs to. If yes, refer to the corresponding alarm handling suggestion.
a. IP Mode:
Check if related alarm exists according to the given association ID.
Related alarms:
l
l

b. ATM Mode:
Bottom layer transmission fault. Check if related alarm exists.
Related alarms:
l
l
l
l
198001792
198066047
198066048
198005639
SDH/SONET fault
SDH/SONET: Excessive Error Code
PVC unavailable. Check if related alarm exists.

Related alarm:
198018944 PVC Fault
Alarm Impact
The cell is unavailable. UE access to the cell fails, and all cell services are down.
3.8 198083025 Common Channel is abnormal

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
3-10
SJ-20100603155704-004|2011-02-26(R3.0)
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. Use plane resource initialization fails.
2. Common channel establishment fails on Node B side.
3. Common channel configuration is deleted in NMS.
4. The Bearer type of common transport channel is modified in NMS.
Handling Suggestion
On NMS alarm management interface, view notification Details where Alarm Reason
handling suggestions that correspond to different reasons are described below:
1. Alarm reason: User plane resource unit initialization fail.
a. On NMS configuration management interface(NE information configuration),
select the relevant Node B. Check the correctness of parameter configuration on
path configuration interface. Check if forwarding bandwidth is configured.
b. On NMS configuration management interface(path group configuration), view path
group configuration. Check the correctness of parameter configuration.
2. Alarm reason: CCH setup fail at NodeB side. On NMS configuration management
interface (BS ground resource management), view IP parameter configuration in IP
and route management. Ensure that at least one COS is selected.
3. Alarm reason: CCH delete by OMCR. Automatic processing is performed by the
system. Common channel deletion is initiated by RNC. No handling is necessary
4. Others: Common channel will be automatically reestablished by the system. No
handling is necessary.
Alarm Impact
Common Channel is unavailable, which falls into the following three cases.
1. If the SCCPCH carrying FACH is unavailable, UE-initiated CS/PS services will be
down.
2. If the SCCPCH carrying PCH is unavailable, paging function will be unavailable in the
system, leading to failure of UE-initiated CS/PS services.
3. If the PRACH carrying RACH is unavailable, UE access to the cell will fail.
3-11
SJ-20100603155704-004|2011-02-26(R3.0)
3.9 198070010 OMCR failed to fetch FTP file

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
The FTP channel between NMS and RNC NE is faulty.
Handling Suggestion
When the link between NMS and RNC NE is normal, open NMS fault management
interface to perform alarm synchronization and fetch the latest alarm information of RNC
NE, so that the alarm information of NMS and that of RNC NE is consistent.
Alarm Impact
NMS fails to fetch alarm files from RNC NE, and alarm information is lost. No impact on
user service.
3.10 198070011 File operation failure between OMCR

and RNC NE
Alarm Type
Processing Alarm
3-12
SJ-20100603155704-004|2011-02-26(R3.0)
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. The disk of ROMB board is full.
2. Disk is faulty.
Handling Suggestion
1. Clean the hard disk space. Delete the files no longer in use or move such files to other
external devices.
2. Replace board or board hard disk.
3. When the link between NMS and RNC NE is normal, open NMS fault management
interface to perform alarm synchronization and to fetch the latest alarm information of
RNC NE, so that the alarm information of NMS and that of RNC NE is consistent.
Alarm Impact
RNC NE fails to save alarm files, and alarm information is lost. No impact on user service.
3.11 198083028 Logservice is unavailable

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
3-13
SJ-20100603155704-004|2011-02-26(R3.0)
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. Log service is unavailable.
2. Communication between log server and ROMP is faulty.
Handling Suggestion
1. Check the log server to see if the LogService runs normally. If not, restart the
LogService by running "/startsys" under the "/home/zte/LogService/bin" directory.
2. Check if the control-plane communication between the log server and the ROMP is
normal by performing the following steps:
a. Open a terminal dialog box in the LINUX system.
b. Check the shelf of the ROMP. If the shelf at 11th slot, the IP of main ROMP is
128.0.31.1. If it at 9th slot, the IP of main ROMP is 128.0.31.9.
c.
Enter the SHELL command to ping the IP of main ROMP(for example, if the IP of
main ROMP is 128.0.31.1, use the command "ping 128.0.31.1"). If can not ping
the IP, then troubleshoot the control-plane communication.
Alarm Impact
The Logservice cannot receive performance files and the performance files are saved on
the ROMP.
3.12 198083029 Performance file store failed

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
3-14
SJ-20100603155704-004|2011-02-26(R3.0)
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. Logservice disk space less than 100M.
2. Logservice version is consistent with ROMP version.
3. Logservice is unavailable, and ROMP disk space less than 100M.
4. Board time be adjusted.
5. The unavailable duration of Logservice has exceeded two hours.
Handling Suggestion
Take different action according to Alarm Reason in alarm Details:
1. If Alarm Reason is "Logservice disk space less than 100M", clean up disk of
Logservice.
2. If Alarm Reason is "Directory on Logservice conflict with which on ROMP", it mean
Logservice version is consistent with ROMP version, use the correct Logservice
version.
3. If Alarm Reason is "Logservice is unavailable, and ROMP disk space less than 100M"
a. Clean up disk of ROMP.
b. Refer to the corresponding alarm handling suggestion.
Related alarms:
198083028 Logservice is unavailable.
4. If Alarm Reason is "Session can not end normally, performance file can not be saved",
it mean board time be adjusted, no handling is necessary.
5. If Alarm Reason is "Logservice is unavailable, and file number more than limit on
ROMP", it mean The unavailable duration of Logservice has exceeded two hours,
refer to the corresponding alarm handling suggestion.
Related alarms:
198083028 Logservice is unavailable.
3-15
SJ-20100603155704-004|2011-02-26(R3.0)
Alarm Impact
Logservice or ROMP can not save performance file, performance data may be lost.
3.13 198083019 MicroCode subsystem failed to get the

table of configuration
Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. Failed to get the information of the RUIB.
2. Failed to get the configuration of OMCB server.
3. Failed to get the configuration of signal dispatch table.
4. Failed to get the configuration of IP/UDP.
5. Failed to get the configuration of L2 table.
6. Failed to get the configuration of path information.
7. Failed to get the configuration of pathgroup information.
8. Failed to get the configuration of IUBC signal dispatch table.
Handling Suggestion
On NMS alarm management interface, view notification Details where Alarm Reason
handling suggestions that correspond to different reasons are described below:
3-16
SJ-20100603155704-004|2011-02-26(R3.0)
1. Alarm Reason: Failed to get the information of the RUIB. On NMS configuration
management interface, check whether Board Reassembling IP Fragments is
configured. If no, perform the corresponding configuration according to network
planning. Make sure to synchronize the configuration data at NMS and RNC NE after
configuration modification. Only after synchronization can the configuration data take
effect at RNC NE.
2. Alarm Reason: Failed to get the configuration of OMCB server. On NMS globle
configuration management interface, check whether OMCB server IP is configured.
If not, perform the corresponding configuration according to network planning. Make
sure to synchronize the configuration data at NMS and RNC NE after configuration
modification. Only after synchronization can the configuration data take effect at RNC
NE.
3. Alarm Reason: Failed to get the configuration of signal dispatch table. On NMS
configuration management interface(SCTP association configuration), check whether
the relevant office is configured. If no, perform the corresponding configuration
according to network planning. Make sure to synchronize the configuration data at
NMS and RNC NE after configuration modification. Only after synchronization can
the configuration data take effect at RNC NE.
4. Alarm Reason: Failed to get the configuration of IP/UDP. On NMS configuration
management interface(service IP for DSP), check whether the relevant office is
configured in DSP service IP address. If no, perform the corresponding configuration
NMS and RNC NE after configuration modification. Only after synchronization can
the configuration data take effect at RNC NE.
5. Alarm Reason: Failed to get the configuration of L2 table. Make sure to synchronize
the configuration data at NMS and RNC NE after configuration modification. Only after
synchronization can the configuration data take effect at RNC NE.
6. Alarm Reason: Failed to get the configuration of path information. On NMS
configuration management interface(path configuration), check whether the relevant
office is configured. If no, perform the corresponding configuration according to
network planning. Make sure to synchronize the configuration data at NMS and RNC
NE after configuration modification. Only after synchronization can the configuration
data take effect at RNC NE.
7. Alarm Reason: Failed to get the configuration of pathgroup information. On NMS
configuration management interface(path group configuration), check whether the
relevant office is configured. If no, perform the corresponding configuration according
to network planning. Make sure to synchronize the configuration data at NMS
and RNC NE after configuration modification. Only after synchronization can the
configuration data take effect at RNC NE.
8. Alarm Reason: Failed to get the configuration of IUBC signal dispatch table. On NMS
configuration management interface(IUBC dispatch configuration), check whether the
dispatch information is configured. If no, perform the corresponding configuration
3-17
SJ-20100603155704-004|2011-02-26(R3.0)

NMS and RNC NE after configuration modification. Only after synchronization can the
configuration data take effect at RNC NE.
Alarm Impact
The system impacts that correspond to different alarm causes are described below:
1. Failed to get the information of the RUIB. The configuration information is used to
reassemble the fragments of IP packets inputted into the equipment. Lacking the
configuration information may cause processing failure of fragments of IP packets.
Service interruption might occur or service processing rate might slow down.
2. Failed to get the configuration of OMCB server. Lacking the configuration information
may paralyze OMCB function.
3. Failed to get the configuration of signal dispatch table. Lacking the configuration
information causes SCTP data transmission failure on the interface board. The
service related to SCTP Protocol on this board is down.
4. Failed to get the configuration of IP/UDP. Lacking the configuration information may
cause processing failure of IUPS service, or processing failure of other data based on
IP transmission.
5. Failed to get the configuration of L2 table. Lacking the configuration information may
cause communication failure within the equipment. All services on the board might be
down.
6. Failed to get the configuration of path information. In the case of ATM interface board,
lacking the configuration information may incur processing failure of the AAL2 data
based on ATM Adaptation Layer Protocol, leading to interruption of IUB/IUCS/IUR
services under this office. In the case of IP interface board, lacking the configuration
information may incur processing failure of IP packet traffic control, leading to
interruption of all services under this office.
7. Failed to get the configuration of pathgroup information. In the case of ATM interface
board, lacking the configuration information may incur processing failure of the AAL2
data based on ATM Adaptation Layer Protocol, leading to interruption of IUB/IUCS/IUR
services under this office. In the case of IP interface board, service is not affected.
8. Failed to get the configuration of IUBC signal dispatch table. Lacking the configuration
information causes IUBC signal transmission failure on the interface board. The
service related to IUBC signal on this board is down.
3.14 198083026 MicroCode subsystem failed to handle

DHCP message from other network
Alarm Type
Processing Alarm
3-18
SJ-20100603155704-004|2011-02-26(R3.0)
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. OMCB IP is unconfigured by RNC.
2. The remote IP address of PPP/MLPPP link is unconfigured.
3. Information of DHCP Client is unconfigured.
Handling Suggestion
On NMS fault management interface, view notification Details where Fail Cause is given.
Locate the specific handling suggestion which corresponds to the listed cause. The
handling suggestions that correspond to different causes are described below:
1. Fail Cause: RNC OMCB IP to Node B has not been configured. On NMS configuration
management interface, check if Manager Node B IP is configured. If no, add the
configuration.
2. Fail Cause: Peer IP Address of PPP/MLPPP Link has not been configured. On NMS
configuration management interface (PPP parameter), check if remote IP address is
configured. If not, add the configuration.
3. Fail Cause: Information of DHCP Client has not been configured. Compare DHCP
Client's Identifier Information with engineering plan, and config corresponding DHCP
Client's Information On NMS configuration management interface.
Alarm Impact
The system impacts that correspond to different notification causes are described below.
1. RNC OMCB IP to Node B has not been configured.
l Case 1: If Node B has never fetched the OMCB channel configuration information
(including OMCB SERVER IP address, OMCB gateway IP, and Node B IP
address) before notification occurs, OMCB channel of the Node B would be
3-19
SJ-20100603155704-004|2011-02-26(R3.0)
blocked. Node Bs failure to fetch IP address would lead to its failure to get other
configuration information. Thus the service as a whole is affected.
Case 2: Node B has fetched the OMCB channel configuration information
(including OMCB SERVER IP address, OMCB gateway IP, and Node B IP
address) before notification occurs. If there is no configuration modification,
OMCB channel would not be affected. If there is configuration modification
before notification occurs, OMCB channel would be affected in such a way that
modified service configuration data fail to take effect on Node B.
2. Peer IP Address of PPP/MLPPP Link has not been configured. Association link is
interrupted. All services on the board are down.
3. Information of DHCP Client has not been configured. DHCP Client will not get Traffic
Address, and service to the Client is broken.
3.15 198083030 Bandwidth automatic adjustment is

useless
Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
The intermediate equipment such as Router or Switch is out of service, all the packets will
be lost at the brocken-down equipment, packet loss rate on this path is invariable. In this
case, decrease the available bandwidth is useless, so bandwidth automatic adjustment
does not be executed.
3-20
SJ-20100603155704-004|2011-02-26(R3.0)
Handling Suggestion
Check the intermediate equipment between RNC and peer NE.
Alarm Impact
Packet loss rate on this path is invariable, call loss might occur, and access success rate
of PS service might decline.
3.16 198083032 TCP connect on IuBC interface

establishment failed.
Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. The local IP address or remote IP address configuration is incorrect.
2. Interface board (GIPI) of local equipment is faulty.
3. Intermediate equipment or opposite equipment faulty.
4. The network cable connection is loose or disconnected.
Handling Suggestion
1. On NMS configuration management interface, check local IP address, remote IP
address and TCP connection mode. If the connection mode at local end is configured
as client, the connection mode at opposite end should be configured as server. Vice
Versa.
3-21
SJ-20100603155704-004|2011-02-26(R3.0)
2. On NMS configuration management interface, check protocol stack configuration at

both ends. In the case of direct connection, ensure that interface board addresses
at both ends are in the same network segment, and the next hop address is direct
connect interface board address. In the case of not direct connection, ensure that the
next hop address is the intermediate equipment address.
3. Check the interface board(GIPI) for the Related Alarms. Perform the recommended
solution to process the possible alarms.
Related Alarms:
4. Check the physical connection on IuBC interface. If the connection is loose or broken,
unplug and plug the cable or replace the cable. If port indicator is on, the physical link
must be normal.
Alarm Impact
The IuBC Broadcast is disabled.
3.17 198083033 Clock Deviation over threshold

notification
Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
3-22
SJ-20100603155704-004|2011-02-26(R3.0)
Probable Cause
Clock crystal oscillator of Slave or Host is inaccurate in the RUB board. The inaccuracy
result in Clock Deviation between Slave and Host over threshold (default threshold is
36sec/hr).
Handling Suggestion
Lock the faulty Slave.
Alarm Impact
KPI Index of service in RNC will be low.
3.18 198083034 External Clock of Slave lost notification

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
External Clock of Slave Lost.
Handling Suggestion
Lock the faulty Slave.
Alarm Impact
KPI Index of service in RNC will be low.
3-23
SJ-20100603155704-004|2011-02-26(R3.0)
3.19 198083037 All Local Cell ID configured at RNC

side are differ from which on Node B side
Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. The RNC is connected with other Node B incorrectly, not the wanted Node B.
2. The radio resource data configured at RNC side and Node B side is inconsistent.
Handling Suggestion
1. Check if the RNC is connected with Node B correctly on Iub interface. If not, please
reconnect RNC and Node B, and synchronize the configuration data to Node B.
2. Check if the radio resource data configured at RNC and Node B is consistent. If not,
please modify the radio resource data correctly, and synchronize the configuration
data to RNC and Node B.
Alarm Impact
All cell belong to the Node B can not be established.
3-24
SJ-20100603155704-004|2011-02-26(R3.0)
3.20 198020291 Protocol stack process failed to

initialize during power on
Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Notification
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
Physical memory is insufficient
Handling Suggestion
Ensure that the actual capacity of the physical memory is more than 1GB.
Alarm Impact
RPU board will reboot automatically after 10 seconds.
3.21 198020802 Conflicting IP addresses

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
3-25
SJ-20100603155704-004|2011-02-26(R3.0)
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. The IP address of this port (including the virtual address in the same network section)
is the same with that of another host in the local network.
2. Loop exists in the opposite switch connected with this port.
Handling Suggestion
When this notification occurs, the NMS will display the conflicting IP address, detects the
5-tuple information of the conflicting local port, and detects the MAC address of the external
equipment whose IP conflicts with the NE IP.
1. To view and modify local port IP, open NMS configuration management interface
and perform the corresponding operation in interface configuration(IP address). To
query external equipment port IP, please refer to the maintenance manual of the
corresponding equipment.
2. The notification must be caused by the existence of loop in the switch connected
with the local port, if the following two conditions are satisfied: Notifications of
"198020802 Conflicting IP Address" and "198020803 Conflicting MAC Address in
Subnet" occur concurrently; Modification of local port IP does not work in restoring
the two notifications mentioned above. In this case, check whether loop connection
between two ports exists on the opposite switch. Remove the loop connection if such
connection exists.
Alarm Impact
Board operation is normal. Communication network is faulty. All services on this port are
down.
3-26
SJ-20100603155704-004|2011-02-26(R3.0)
3.22 198020803 Conflicting MAC Addresses in Subnet

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. The MAC address of this port is the same with another MAC address in the direct
connect network.
2. Loop exists in the remote switch connected with this port.
Handling Suggestion
When this notification occurs, the NMS will display the conflicting MAC address, detects the
5-tuple information of the conflicting local port, and detects the IP address of the external
equipment whose MAC address conflicts with the NE MAC address.
1. Modify local port MAC address, or the conflicting port MAC address of external
equipment. Refer to the 5-tuple information displayed in notification Details to locate
the conflicting local port. Local port MAC address can be viewed and modified in
interface configuration (MAC Address) on NMS configuration management interface.
To query the port MAC address of external equipment, please refer to the maintenance
manual of the corresponding equipment.
2. The notification must be caused by the existence of loop in the switch connected
with the local port, if the following two conditions are satisfied: Notifications of
"198020802 Conflicting IP Address" and "198020803 Conflicting MAC Address in
Subnet" occur concurrently; Modification of local port IP does not work in restoring
the two notifications mentioned above. In this case, check whether loop connection
3-27
SJ-20100603155704-004|2011-02-26(R3.0)
between two ports exists on the remote switch. Remove the loop connection if such
connection exists.
Alarm Impact
Board operation is normal. The notification leads to packet lookup failure in Layer 2
forwarding table. Then packet loss occurs and all services related to this port will be down.
3.23 198020804 Failed to generate static ARP from IP

address
Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
Failed to generate static ARP from the newly added IP address, because the number of
static ARPs which generated by IP has reached the maximum.
Handling Suggestion
Delete some proxy addresses configured for virtual ports and re-configure IP address
within the limit of static ARPs.
Alarm Impact
The external device failed to communicate with the IP address from which no static ARP
is generated.
3-28
SJ-20100603155704-004|2011-02-26(R3.0)
3.24 198030016 Ethernet link OAM event

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Notification
Severity
Major
Disaster Alarm
No
Frequently Reported
Yes
Probable Cause
The number of wrong frames or wrong symbols exceeds the threshold.
Handling Suggestion
Check Ethernet link, receiver and transmitter of link.
Alarm Impact
Ethernet links can not transmit data credibly.
3.25 198000576 Trunk Slide

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Notification
3-29
SJ-20100603155704-004|2011-02-26(R3.0)
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
Since frequency difference might exist between trunk line clock and local receive clock,
the trunk receive clock is not synchronous with the transmit clock.
Handling Suggestion
Check the clock synchronization status at both sides. If the status is unsynchronized,
check if LOL-related (loss of lock) alarm occurs in clock board. If yes, refer to the
Related alarms:
l
l
l

Alarm Impact
Momentary fault occurs to trunk data service or signaling channel. If fault occurs
repeatedly, CS/PS service might become unstable. Otherwise, service is not affected.
3.26 198001600 One of CPUs on One of Boards in This

Shelf Resets (Exceptionally)
Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Notification
3-30
SJ-20100603155704-004|2011-02-26(R3.0)
Severity
Major
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
A certain CPU of a certain board in the shelf abnormally resets. Probable causes include:
1. Manual operation(for example, unplugging and plugging board, resetting NMS, or
pressing panel reset button)
2. Abnormal board reset
Handling Suggestion
1. Check the NMS operation log to see if manual reset operation has been performed. If
yes, no handling is necessary.
2. Replace board.
Alarm Impact
The service or communication link related to the resetting board is down, but will be
restored after board power-on.
3.27 198017216 Error in MCS Multi-Core processor

receiving configuration data from DBS
Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Notification
Severity
Major
3-31
SJ-20100603155704-004|2011-02-26(R3.0)
Disaster Alarm
No
Frequently Reported
Yes
Probable Cause
1. The configuration data from DBS are exceptional.
2. Failure in adding a vital data table.
Handling Suggestion
Check the data configuration, if there is a configuring error, correct it and reboot the board.
Alarm Impact
It may cause packet forwarding problem since some vital data table is absent.
3.28 198018240 TCP Receives RST Packet

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. The peer end initiates tcp connection resetting and sends a RST packet.
2. The peer end receives invalid tcp connection and returns a RST packet.
3-32
SJ-20100603155704-004|2011-02-26(R3.0)
Handling Suggestion
Check if there is severe packet loss in physical link (It can be checked by ping command),
and handle physical link faults.
Alarm Impact
The corresponding connection aborts.
3.29 198018241 TCP Connection Aborted

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Notification
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. The RNC is connected with other Node B incorrectly, not the wanted Node B.
2. The radio resource data configured at RNC side and Node B side is inconsistent.
Handling Suggestion
1. Check if the RNC is connected with Node B correctly on Iub interface. If not, please
reconnect RNC and Node B, and synchronize the configuration data to Node B.
2. Check if the radio resource data configured at RNC and Node B is consistent. If not,
please modify the radio resource data correctly, and synchronize the configuration
data to RNC and Node B.
3-33
SJ-20100603155704-004|2011-02-26(R3.0)
Alarm Impact
All cell belong to the Node B can not be established.
3.30 198018242 MD5 Verification Failure

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
MD5 verification is not set for packets in application layer.
Handling Suggestion
Check MD5 encrypted option of the two ends of application layer. If an end does not set
with MD5 encrypted option, then set MD5 encrypted option for this end.
Alarm Impact
Application layer communication failure.
3.31 198018243 Wrong MD5 Message Abstract

Alarm Type
Processing Alarm
3-34
SJ-20100603155704-004|2011-02-26(R3.0)
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
When application layer is receiving messages, MD5 cryptographic keys set on both ends
are inconsistent.
Handling Suggestion
Check if MD5 cryptographic keys set on both ends are the same. If not, set the same MD5
cryptographic keys for both ends of application layer.
Alarm Impact
Application layer communication failure.
3.32 198023106 Board self-check fails

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
3-35
SJ-20100603155704-004|2011-02-26(R3.0)
Disaster Alarm
No
Frequently Reported
No
Probable Cause
Board hardware is faulty.
Handling Suggestion
Replace board.
Alarm Impact
The board fails to power on and operate, resulting in UE access failure and interruption of
ongoing services.
3.33 198023107 The board initialization failure

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
Board hardware is faulty.
3-36
SJ-20100603155704-004|2011-02-26(R3.0)
Handling Suggestion
Replace board.
Alarm Impact
The board fails to power on and operate, resulting in UE access failure and interruption of
ongoing services.
3.34 198023617 Configuration file is unusable

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Notification
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
During the process of system power-on, the DAT file obtained from VMM is unusable or
the txt file which saves configuration data is unusable.
Handling Suggestion
On NMS fault management interface, view the alarm details, which give the Additional
Reason.
1. If it's the DAT file error, then we need to reload the file from VMM and switch to the
new file.
2. if it's the TXT file error,then take the following step:
a. Get the TXT file from "/DOC0/DATA1" directory at RPU with File Manager method.
b. Open the TXT file and delete line "[CRC_DATFILE]=" and "[CRC_TXTFILE]=".
3-37
SJ-20100603155704-004|2011-02-26(R3.0)
c.
Transmit the modified TXT file.
d. Reboot RPU.
Alarm Impact
1. DAT file is unusable This error will make the saved data unrestorable and
unconfigurable if the configured data was saved in TXT file.
2. TXT file is unusable This error will make the saved data unrestorable.
3.35 198003138 FLASH device initialize failed

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Notification
Severity
Major
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
The flash on the board is damaged.
Handling Suggestion
Replace the relevant boards.
Alarm Impact
1. For a single OMP board, the flash fault may cause board start up failure. For both
master/slave boards with flash fault the entire system may have start up failure.
2. For other boards, the board may start up normally with out impact on its service.
3-38
SJ-20100603155704-004|2011-02-26(R3.0)
3.36 198003394 Entering Daylight Savings Time

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
The pre-configured Daylight Saving Time starts for the system.
Handling Suggestion
Alarm Impact
None.
3.37 198003395 Quitting Daylight Savings Time

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Notification
3-39
SJ-20100603155704-004|2011-02-26(R3.0)
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
The pre-configured Daylight Saving Time ends for the system.
Handling Suggestion
Alarm Impact
None.
3.38 198005441 Port status on internal media plane

changed.
Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
3-40
SJ-20100603155704-004|2011-02-26(R3.0)
Probable Cause
1. Connection between UIM/GUIM and GLI is faulty.
2. Board is faulty.
Handling Suggestion
On NMS fault management interface, view notification Details where information of "Port
status" is given.
1. If the port status is "Master port invalid status" or "Master port abnormal", refer to the
following handling suggestions.
a. Reconnect the cable between UIM/GUIM and GLI.
b. Replace the optical module or cable used for the connection between UIM/GUIM
and GLI.
c.
Replace UIM/GUIM board.
d. Replace GLI board.

2. If the port status is others, no handling is necessary.
Alarm Impact
The impact varies depending on the "Port status" given in notification Details.
1. If the port status is "Master port invalid status" or "Master port abnormal", the master
port fails to forward inner media stream, and the services on master port will be
switched to slave port. If the slave port is also unavailable, services on the port will
be interrupted.
2. If the port status is "Slave port invalid status" or "Slave port abnormal", service will not
be affected. However, the potential hazard will emerge once master/slave switching
occurs.
3. If the port status is others, service will not be affected.
3.39 198005448 485 Set Failure

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Notification
3-41
SJ-20100603155704-004|2011-02-26(R3.0)
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. 485 communication is interrupted.
2. The board is abnormal.
Handling Suggestion
1. Unplug and plug 485 cable.
2. Replace 485 cable.
3. Replace CLKG/PWRD board.
Alarm Impact
The configured clock reference/environment threshold fails to take effect. No impact on
service.
3.40 198026177 CLKG reference quality changed

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
3-42
SJ-20100603155704-004|2011-02-26(R3.0)
Frequently Reported
No
Probable Cause
Clock quality of the CLKG board has changed.
Handling Suggestion
Check the quality of external clock source.
Alarm Impact
System could not get the needed clock.
3.41 198026178 Clock work mode changed

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
The clock work mode of the CLKG board has changed.
Handling Suggestion
3-43
SJ-20100603155704-004|2011-02-26(R3.0)
Alarm Impact
System could not get the needed clock.
3.42 198005705 MCU resets for abnormities

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Notification
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
Hardware fault.
Handling Suggestion
Replace the board on which the alarm occurs.
Alarm Impact
The system clock is affected.
3.43 198005710 The result of base selection of sets

chip
Alarm Type
Processing Alarm
3-44
SJ-20100603155704-004|2011-02-26(R3.0)
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
After switching clock reference manually, by MML command, or by pressing panel
button, clock board performs reference locking operation(needs 2 minutes at most). This
notification is to inform the result of this reference selection operation.
Handling Suggestion
Alarm Impact
None.
3.44 198005711 The action of select base is working

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
3-45
SJ-20100603155704-004|2011-02-26(R3.0)
Disaster Alarm
No
Frequently Reported
No
Probable Cause
When selecting base manually, if the previous base selection is still in process and
operation result is yet to be given, the present manual base selection is shut down and
this notification is declared.
Handling Suggestion
Alarm Impact
None.
3.45 198005712 The manual select base will be run,

please wait for the result
Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
3-46
SJ-20100603155704-004|2011-02-26(R3.0)
Probable Cause
The notification is declared after selecting base via panel button, to remind user that the
base selection is in process and to request user to wait for the operation result
Handling Suggestion
Alarm Impact
None.
3.46 198005713 APC's RAM error

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Notification
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
Hardware fault.
Handling Suggestion
Replace the board on which the alarm occurs.
Alarm Impact
The board on which the alarm occurs is down. ATM cell fails to be forwarded, and all the
services carrying on this board are interrupted.
3-47
SJ-20100603155704-004|2011-02-26(R3.0)
3.47 198005715 PP2S source switched

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
PP2S(Pulse Per 2 Seconds) source is changed at both system clock and GPS receiver
sides.
Handling Suggestion
GPS-side PP2S has a higher priority. If PP2S is switched over from GPS-side to
system-side, check if the GPS receiver and antenna feeder working status is abnormal.
Alarm Impact
None.
3.48 198005716 Type B fault on board (GPS) phase-lock

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

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Notification
Severity
Major
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
1. The DSP chip is faulty.
2. Board is faulty.
Handling Suggestion
DSP resets automatically and abnormally.
1. If there is an alarm "198005399 DSP resource is unavailable" restored after DSP reset,
the board can be restored to a normal state.
2. If DSP resets repeatedly, replace the board.
Alarm Impact
DSP is unavailable during reset, but will be restored to normal state after reset. During
reset, cells on the DSP are out of service, services on the DSP are interrupted, and call
loss increases.
3-50
SJ-20100603155704-004|2011-02-26(R3.0)
3.50 198005701 Version Load Error

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Notification
Severity
Major
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
The equipment is abnormal in the process of version loading, which falls into three cases.
1. The equipment fails to fetch the needed version.
2. Version loading to chip fails.
3. Chip hardware is faulty.
Handling Suggestion
On NMS fault management interface, view notification Details where "Loading
corresponding alarm information" is given. Locate the corresponding handling suggestion
based on the given information.
1. Any of the following items displayed by "Loading corresponding alarm information"
indicates that the chip fails to obtain the needed version. On NMS software
management interface, check the configured version for the chip and version status.
Ensure that the needed version is configured for the chip and the version is activated.
a. DSP6416 No.d : No Version Information
b. DSP5402 No.d : No Version Information
c.
MC fail to get version information
d. OCT6100 fail to get version information

3-51
SJ-20100603155704-004|2011-02-26(R3.0)
e. M82620 : Index = d fail to get version information

2. If information other than the items listed above appears, refer to the following handling
suggestion.
a. Reset board.
b. Replace DSP subcard.
c.
Replace board.
Alarm Impact
1. Microcode version loading fails, leading to repeated board reset and interruption of
board services.
2. Firmware/single-chip computer version loading fails, leading to abnormal board
operation and interruption of board services.
3. DSP version loading fails. Cells on the DSP will be out of service. Services on the
DSP are interrupted, and the number of call loss increases.
3.51 198019777 APS Switchover Happens

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. Optical interface is faulty.
2. During inter-board backup, any of the following events occurs.
3-52
SJ-20100603155704-004|2011-02-26(R3.0)
a. Input clock loss

b. Inner HW/LVDS alarm
c.
Inner media plane port alarm
d. ENUM open(board not properly inserted)

e. Board reset(the board where the working optical interface is located)
3. Switching is initiated by opposite end.
4. In recovery mode, fault recovery time in optical interface exceeds 5 minutes.
5. APS switching request/clearance is initiated by NMS.
Handling Suggestion
Check operation and maintenance log to see if O&M personnel initiated manual APS
switching request/clearance. If yes, no handling is necessary. If no, check if the following
alarms are declared in the board. If such alarm exists, refer to the corresponding alarm
Related alarms:
l
l
l
l

198005396 Exceptional Internal Media Plane Communication
198005378 Board HW Error
198005635 The board is not plugged firmly
Alarm Impact
During APS switching, the link is interrupted for 1050 ms. Few packet loss might occur,
but service is not affected.
3.52 198005188 UIM CS Changeover

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
3-53
SJ-20100603155704-004|2011-02-26(R3.0)
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. Optical module signal loss occurs.
2. Board input clock loss occurs.
3. Bit error rate at the optical interface is high.
4. Lock loss occurs to the phase-locked loop.
5. Bit error rate on the master/slave interconnecting link of GUIM board is high.
Handling Suggestion
Check if the following alarm occurs in local/opposite board.
If yes, refer to the
Related alarms:
l
l
l
198001286 Loss of Clock When Input to Board

198005646 Phase-lock Loop Unlock
Alarm Impact
No impact on service.
3.53 198005192 Board's Work Mode Unsupported

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
3-54
SJ-20100603155704-004|2011-02-26(R3.0)
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. The configured board backup mode is unsupported.
2. FPGA is unloaded, leading to setting failure of board working mode.
Handling Suggestion
1. Check the configuration of board backup mode. If the configured backup mode is
not supported by the board, modify configuration or replace the board with one that
supports such configuration.
2. Unplug and plug board. Reload FPGA version.
Alarm Impact
Board master/slave backup function is disabled.
3.54 198005193 Notification of the power-on status of

the basic process
Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
3-55
SJ-20100603155704-004|2011-02-26(R3.0)
Probable Cause
1. Board power-on is successful.
2. Board power-on fails or expires.
Handling Suggestion
On NMS fault management interface, view notification Details where information of
power-on status ("Board poweron successful/failed/timeout") is given. Locate the
corresponding handling suggestion based on the given information. The handling
suggestions that correspond to different power-on status are described below:
1. Board power on successful/failed/timeout: Power on successful No handling is
necessary.
2. Board power on successful/failed/timeout: Power on timeout Ensure that the board
loads the proper version. The boards in a NE must use the version of the same version
No..
3. Board power on successful/failed/timeout: Power on failed Ensure that the board loads
the proper version. The boards in a NE must use the version of the same version No..
Alarm Impact
If the notification is power-on success, service will not be affected. If the notification is
power-on failure, the services on the board will be unavailable.
3.55 198005956 Board Version Error

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
3-56
SJ-20100603155704-004|2011-02-26(R3.0)
Frequently Reported
No
Probable Cause
1. A board is in the slot which is not configured with any board.
2. Board version is unconfigured.
3. Board version has been configured, but version file does not exist or is damaged.
Handling Suggestion
1. On NMS configuration management interface, open the rack view. Check if the boards
configured on the NMS is consistent with the boards configured on the equipment.
2. On NMS fault management interface, view notification details where "Version type
of abnormal board" is given. Load and activate the version on NMS software
management interface according to the given "Version type".
Alarm Impact
The board fails to obtain version, leading to abnormal board operation and access failure
of board services.
3.56 198005958 IDE Version Files Synchronization

Information
Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
3-57
SJ-20100603155704-004|2011-02-26(R3.0)
Probable Cause
Synchronization of master/slave OMP version files occurs.
Handling Suggestion
On NMS fault management interface, view notification Details where "Synchronization
information" is given.
1. If synchronization information is "Failed to obtain file record during synchronization"
or "Synchronization failed", find the name of the version file in notification Details.
According to the given file name, locate on NMS software management interface the
corresponding version configuration in the version file database. Reload the version
file to RNC NE. Delete the version file if it is not in use.
2. If synchronization information is others, no handling is necessary.
Alarm Impact
1. IDE version file synchronization occurs between master and slave OMP (ROMB
board). Service will not be affected by synchronization result.
2. In the case of synchronization failure, partial loss of version file will occur to slave OMP.
3.57 198005961 OMP Version Check Information

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
3-58
SJ-20100603155704-004|2011-02-26(R3.0)
Probable Cause
The version file in software version configuration does not exist in RNC NE.
Handling Suggestion
On NMS fault management interface, view notification Details where "Version file name"
is given. According to the given file name, locate on NMS software management interface
the corresponding version configuration in the version file database. Reload the version
file to RNC NE.
Alarm Impact
1. If the non-existent version file is not in use, service will not be affected.
2. If the non-existent version file is the activated version, the corresponding board will fail
to fetch version during powering-on, leading to service access failure.
3.58 198005962 Patch version operate fail

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. Patch version file and CPU version file do not match.
2. Patch version file does not exist in RNC NE.
3. The patch version file related to the patch does not exist in RNC NE.
3-59
SJ-20100603155704-004|2011-02-26(R3.0)
Handling Suggestion
1. If the patch version is not needed, delete the corresponding version configuration on
NMS software management interface.
2. If the patch version is needed, locate on NMS software management interface the
version configuration of patch version file and related patch version file in the version
file database. Reload the version files to RNC NE.
Alarm Impact
Patch version activation fails. New functions of the patch version are unavailable. No
impact on service.
3.59 198010560 No message response in the link for

a long time
Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Notification
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
Bottom layer link quality is poor, there is no message response for the link for a long time.
Handling Suggestion
1. Check if the physical link connection and configuration between this NE and its
connecting NE is consistent with planning.
3-60
SJ-20100603155704-004|2011-02-26(R3.0)
2. Check if there is a physical transmission alarm occurred simultaneously with this alarm
on NMS. If yes, refer to the corresponding alarm handling suggestion. Alarms related
to physical transmission are listed below, with respect to access mode.
Fiber Access Mode
l
l
l
l
198001792
198066047
198066048
198005639
SDH/SONET fault
SDH/SONET:Excessive Error Code
E1 Access Mode
l
l
l
l
198005647
198066045
198066046
198000576
High Error Rate at E1 Bottom Layer

Trunk error
Trunk abnormal
Trunk Slide
Alarm Impact
Related link will be interrupted and cannot bear service.
3.60 198011840 M3UA user office status change

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Notification
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. User configuration of this office is changed.
3-61
SJ-20100603155704-004|2011-02-26(R3.0)
2. Bottom-layer links are unavailable.

3. The signaling network management message from opposite end is received.
Handling Suggestion
1. Check whether link interruption alarm occurs to the link/association. If yes, refer to the
Related alarms:
l
l
198066011 MTP3 link unavailable

2. On NMS configuration management interface, check if the M3UA user is configured

in the relevant office. If no, add the configuration.
3. Locate the cause for office status change at opposite end.
Alarm Impact
If M3UA user office status changes from accessible to inaccessible, reception and sending
of messages from/to the office fail. Access of new services under the office fails, and
abnormal release of the ongoing service occurs. If M3UA user office status changes from
inaccessible to accessible, the system will return to normal state.
3.61 198013888 ASP status changed

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
3-62
SJ-20100603155704-004|2011-02-26(R3.0)
Probable Cause
1. Association status is changed.
2. ASP operation is performed at opposite end.
3. ASP operation is performed in dynamic data management at local end.
Handling Suggestion
1. Check whether association interruption alarm occurs. If yes, refer to the corresponding
Related alarm:
2. Activate the ASP in dynamic data management.
3. Check whether ASP operation is performed at the opposite end.
Alarm Impact
If this notification and the alarm of "198066014 M3UA office inaccessible" are declared
at the same time, access failure of new services under this office and abnormal release
of ongoing services will occur. If merely this notification is declared, service will not be
affected.
3.62 198013889 AS status changed

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
3-63
SJ-20100603155704-004|2011-02-26(R3.0)
Probable Cause
1. Association status is changed.
2. ASP operation is performed at opposite end.
3. ASP operation is performed in dynamic data management at local end.
Handling Suggestion
1. Check whether association interruption alarm occurs. If yes, refer to the corresponding
Related alarm:
2. Activate ASP under the AS in dynamic data management.
Alarm Impact
If this notification and the alarm of "198066014 M3UA office inaccessible" are declared at
the same time, access failure of new services under this office and abnormal release of
ongoing services will occur. If only this notification is declared, service will not be affected.
3.63 198013890 Sigtran error message received

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
Yes
3-64
SJ-20100603155704-004|2011-02-26(R3.0)
Probable Cause
1. AS configuration is wrong.
2. Protocol versions used at both sides are different.
Handling Suggestion
1. Check AS configuration to see whether the configured traffic mode at both sides are
consistent. If no, modify configuration to keep consistency.
2. APP server AS ID configuration must meet the following requirements. If ASP is
configured for local end, SGP should be configured for Opposite end. Vice versa. If
IPSP client is configured for local end, IPSP server should be configured for opposite
end. Vice Versa.
3. Activate the ASP in dynamic data management.
4. On NMS configuration management interface (AS configuration), check if routing
context and routing context ID are configured. Ensure that the routing contexts
configured at both ends are the same.
5. On NMS configuration management interface, check whether the local ASP in service
for AS is configured. If no, add the configuration.
6. Check the protocol versions used at both sides. Ensure that the protocol versions are
the same.
Alarm Impact
The corresponding AS fails to be activated, making M3UA office inaccessible. Reception
and sending of message from/to the office fail. Access of new services under the office
fails.
3.64 198013891 Sigtran notification message received

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
3-65
SJ-20100603155704-004|2011-02-26(R3.0)
Disaster Alarm
No
Frequently Reported
Yes
Probable Cause
1. The broken association leads to insufficiency of the number of ASP in service for AS.
2. Release of ASP in dynamic data management leads to insufficiency of the number of
ASP in service for AS.
Handling Suggestion
1. On NMS configuration management interface (AS configuration), query ASP-related
associations. Check whether interruption alarm occurs in the association(s). If yes,
refer to the corresponding alarm handling suggestion.
Related alarm:
2. Reactivate ASP in dynamic data management.
Alarm Impact
The number of ASP in service for AS is insufficient. If traffic is heavy, congestion or packet
loss might occur, leading to call loss or increasing PS call access failures. Otherwise,
service is not affected.
3.65 198013892 Allocate memory fail

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
3-66
SJ-20100603155704-004|2011-02-26(R3.0)
Disaster Alarm
No
Frequently Reported
No
Probable Cause
Memory is insufficient, that result in dynamic memory allocation failure when the processor
is powered on.
Handling Suggestion
1. Expand memory capacity of the board on which the alarm occurs and then restart the
board.
2. If Application Server/Application Server Process is not configured on this board, then
the alarm should be ignored.
Alarm Impact
If Application Server/Application Server Process is not configured on this board, system
will not be affected. Or else process will be unstable.
3.66 198014144 Association establishment failed

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

Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Notification
3-68
SJ-20100603155704-004|2011-02-26(R3.0)
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
The local end receives a link creation request but detects no link break, and the association
restarts. Probable causes for the alarm include:
1. Relevant board at peer end resets.
2. The Association link is reestablished at peer end.
Handling Suggestion
No handling is necessary, wait association to restart
Alarm Impact
None.
3.68 198025664 Abnormal Half-fixed Connection

Changes
Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Notification
Severity
Major
Disaster Alarm
No
3-69
SJ-20100603155704-004|2011-02-26(R3.0)
Frequently Reported
Yes
Probable Cause
1. Abnormal jitter occurs to the line clock of the shelf where the board is located.
2. Hardware fault.
Handling Suggestion
1. Check if there is an alarm related to input clock exists on NMS. If yes, refer to the
Related alarms:
l
l
l
l
l
198026116 CLKG PP2S Output Clock Lost

198026133 Clock Output Loss
2. Replace the faulty board.
Alarm Impact
TMD channel is interrupted momentarily, which might have a minor impact on service.
3.69 198008005 Memory file buffer overflow

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Notification
Severity
Warning
Disaster Alarm
No
3-70
SJ-20100603155704-004|2011-02-26(R3.0)
Frequently Reported
No
Probable Cause
The transferred data records exceed the maximum capacity of the table, and the capacity
of the receiver memory file buffer is insufficient.
Handling Suggestion
Check the table capacity corresponding to the NE version, delete the excessive data
records configured on NMS, make sure the data capacity to be transferred from NMS to
NE will not exceeds the table capacity of NE.
Alarm Impact
If the board is powering on, the excessive data records (beyond table capacity) are
discarded, otherwise the synchronization will be aborted.
3.70 198083046 DSP memory check fail notification

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
DSP memory check fail.
3-71
SJ-20100603155704-004|2011-02-26(R3.0)
Handling Suggestion
Reset the Slave reported in the notification.
Alarm Impact
KPI Index of Service in RNC will be low.
3.71 198083047 TCP connect on IuBC interface is

interrupted
Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. Interface board (GIPI) of local equipment is faulty.
2. Intermediate equipment or opposite equipments faulty.
3. The network cable connection is loose or disconnected.
Handling Suggestion
1. Check the interface board(GIPI) for the Related Alarms. Perform the recommended
solution to process the possible alarms.
Related Alarms:
3-72
SJ-20100603155704-004|2011-02-26(R3.0)
2. Check the physical connection on IuBC interface. If the connection is loose or broken,
unplug and plug the cable or replace the cable. If port indicator is on, the physical link
must be normal.
Alarm Impact
The IuBC Broadcast is disabled.
3.72 198015168 AAL2 Path blocked by resetting

process
Alarm Type
Communication Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
The adjacent node doesn't has the same path.
Handling Suggestion
You can unblock the Path by adding the same path on the adjacent node.
Alarm Impact
3-73
SJ-20100603155704-004|2011-02-26(R3.0)
3.73 198020805 ARP detect failed

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

match
Alarm Type
Communication Alarm
3-74
SJ-20100603155704-004|2011-02-26(R3.0)
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
When the switch of the ARP detecting enabled, CE can send static ARP request packet
with the static ARP's IP periodically, if CE receives the ARP respond packet whose MAC
or dot1q encapsulation is not the same as static ARP's during the set time, CE will report
this alarm information.
Handling Suggestion
1. Please check remote device's MAC address.
2. Please check the switch VLAN configuration.
Alarm Impact
The communication will be interrupted possibly.
3.75 198026176 Clock reference changed

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Notification
3-75
SJ-20100603155704-004|2011-02-26(R3.0)
Severity
Undefined
Disaster Alarm
No
Frequently Reported
No
Probable Cause
The currently locked clock reference has changed.
Handling Suggestion
No need to handle.
Alarm Impact
the clock.
3.76 198026179 Clock source invalidation reason

changed
Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Notification
Severity
Undefined
Disaster Alarm
No
Frequently Reported
No
3-76
SJ-20100603155704-004|2011-02-26(R3.0)
Probable Cause
The clock reference becomes invalid.
Handling Suggestion
No need to handle.
Alarm Impact
the clock.
3.77 198028993 SCTP Primary Path Set Failed

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Notification
Severity
Warning
Disaster Alarm
No
Frequently Reported
No
Probable Cause
The remote IP of the SCTP primary path configured at application layer is not included in
the local address list of SCTP at opposite end
Handling Suggestion
Check notification details on the NMS Alarm Management interface to find the SCTP ID
and the primary remote IP address. To use the primary remote IP address as the primary
SCTP path, perform the following steps:
1. Add the IP address as an interface address at the peer-end equipment.
3-77
SJ-20100603155704-004|2011-02-26(R3.0)
2. Add the "primary remote IP address" to the "local SCTP IP address" list.
Alarm Impact
This notification informs user of the update failure of SCTP primary path. The primary path
currently in use is not affected. No impact on service.
3.78 198031040 ACL config failed

Alarm Type
Processing Alarm
Alarm Purpose
External Alarm
Notification
Severity
Undefined
Disaster Alarm
No
Frequently Reported
No
Probable Cause
BRS protocol processes ACL configuration data which synchronized by DBS from ACL
offline configuration failed.
Handling Suggestion
1. Check the ACL configuration type and error information from alarm inform.
2. Correct the ACL offline configuration data base on alarm inform.
3. Synchronize the ACL offline configuration data.
Alarm Impact
The ACL configuration data will not take effect.
3-78
SJ-20100603155704-004|2011-02-26(R3.0)
3.79 198000834 MCC is faulty

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Notification
Severity
Major
Disaster Alarm
No
Frequently Reported
No
Probable Cause
MCC Hardware is faulty.
Handling Suggestion
1. Unplug the board for 5 seconds, and plug it again after a full discharge.
Alarm Impact
All MCC channels cannot transmit or receive data.
3.80 198002625 Process is deadlocked.

Alarm Type
Processing Alarm
Alarm Purpose
Internal Alarm
3-79
SJ-20100603155704-004|2011-02-26(R3.0)
Notification
Severity
Major
Disaster Alarm
Yes
Frequently Reported
No
Probable Cause
Maybe some resource, such as semaphore, is deadlocked.
Handling Suggestion
Note down the alarm information and contact ZTE Corporation.
Alarm Impact
The process will never be scheduled, or timely resource release fails, which results in
resource exhaustion.
3.81 198002880 CPU dead-loop

Alarm Type
Processing Alarm
Alarm Purpose
Internal Alarm
Notification
Severity
Major
Disaster Alarm
Yes
3-80
SJ-20100603155704-004|2011-02-26(R3.0)
Frequently Reported
No
Probable Cause
There exist dead loops in the processes or the system tasks.
Handling Suggestion
The board will restart automatically when this alarm occurs. The alarm will automatically
disappear after restart.
Alarm Impact
The process or task of low priority level fails to be scheduled.
3.82 198003650 The data in user buffer is corrupted

Alarm Type
Processing Alarm
Alarm Purpose
Internal Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. The check or control information of user buffer is corrupted.
2. The control information of swap block is corrupted.
Handling Suggestion
Make records of the alarm and exception information, then contact ZTE Corporation.
3-81
SJ-20100603155704-004|2011-02-26(R3.0)
Alarm Impact
1. Data corrupt may cause the dirty data is used by the application and then error occur.
2. A few of memory is leaked maybe.
3.83 198005189 Notification of Active/Standby

Changeover
Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Notification
Severity
Warning
Disaster Alarm
No
Frequently Reported
No
Probable Cause
It is hardware system fault. The CS domain of the UIM switches over due to artificial
operation.
Handling Suggestion
1. Analyze the switchover reason according to the additional information about the alarm.
If it is not because of the system fault but due to control of MML command at the
background or caused by non-active/standby changeover, or the standby board does
not exist physically, nothing would be done for this alarm.
2. If it is because of the system fault, eliminate those alarms firstly.
Alarm Impact
The board whose changeover fails will reset automatically.
3-82
SJ-20100603155704-004|2011-02-26(R3.0)
3.84 198005195 Board mix plug occurred

Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
1. The PCB ID is inconsistent between master board and slave board.
2. The BOM ID is inconsistent between master board and slave board.
3. The physical board type is inconsistent between master board and slave board.
Handling Suggestion
Depend on PCB ID, BOM ID and physical board type of the self board and the mate
board according to the additional information about the inform, inquire "Board mix plug
test conclusion.xls" and check the two boards can mix plug into shelf? If yes ignore it, if
not use the same PCB ID, BOM ID and physical boar type please.
Alarm Impact
Not support to mix plug into shelf, the board can't work normally.
3-83
SJ-20100603155704-004|2011-02-26(R3.0)
3.85 198005718 Two master clock ports is directly

connected
Alarm Type
Equipment Alarm
Alarm Purpose
External Alarm
Notification
Severity
Undefined
Disaster Alarm
No
Frequently Reported
No
Probable Cause
The port is configured as a master clock port in synchronous Ethernet, two master clock
ports is directly connected.
Handling Suggestion
If users do not want the other side to recover clock from this SyncE port, it is normal.
Otherwise, it maybe has a mistake on network connecting.
l
l
If it is normal, there is no need to handle;

If it is network connecting mistake, there is need to reconfigure the clock port or
reconnect the port.
Alarm Impact
l
l
If it is normal, then there is no impact;

If it is network connecting mistake, then the port can not synchronize to the
connected master clock port.
3-84
SJ-20100603155704-004|2011-02-26(R3.0)
3.86 198005719 FPGA receive/send packets abnormally

Alarm Type
Equipment Alarm
Alarm Purpose
Internal Alarm
Notification
Severity
Minor
Disaster Alarm
No
Frequently Reported
No
Probable Cause
The packets in FPGA are blocked because of FPGA exception.
receive/send packets.
The board can't
Handling Suggestion
1. Update latest FPGA file and wait some minutes to check whether exception occur
again.
2. Replace the board and wait some minutes to check whether exception occur again.
Alarm Impact
The board can't receive/send packets. All services carried by the board may interrupted.
3-85
SJ-20100603155704-004|2011-02-26(R3.0)
3-86
SJ-20100603155704-004|2011-02-26(R3.0)
Figures
Figures
Tables
III

SJ-20100603155704-004-ZXWR RNC (V3.09.30) Alarm and Notification Handling Reference - 331818

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SJ-20100603155704-004-ZXWR RNC (V3.09.30) Alarm and Notification Handling Reference - 331818

Uploaded by

Copyright:

Available Formats

ZXWR RNC

Radio Network Controller

Alarm and Notification Handling Reference

First Edition (V3.09.30.03)

Second Edition (V3.09.30.06)

Third Edition (V3.09.30.09)

Serial Number: SJ-20100603155704-004

Chapter 2 Alarm.......................................................................................... 2-1

2.1.19 198001792 SDH/SONET fault ............................................................... 2-19

2.1.52 198019714 Conflicting between APS configuration and board backup

2.2.42 198015618 Faulty frames received by port over threshold......................2-123

2.4.13 198025868 Lightning alarm ..................................................................2-158

Chapter 3 Notification ................................................................................ 3-1

3.25 198000576 Trunk Slide ................................................................................... 3-29

3.61 198013888 ASP status changed ..................................................................... 3-62

About This Manual

What Is in This Manual

Introduces the concepts and terms used in this manual.

Introduces the ZXWR RNC alarms.

Introduces the ZXWR RNC notifications.

1.1 Overview of Fault Management

1.2 Alarm Code

1.3 Alarm Type

Equipment alarm: related with device hardware.

ZTE Proprietary and Confidential

ZXWR RNC Alarm and Notification Handling Reference

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

1.4 Alarm Classification

Critical alarm causes system breakdown and service interruption. It requires

ZTE Proprietary and Confidential

1.6 Probable Cause

1.7 Handling Suggestion

1.8 Alarm Impact

ZTE Proprietary and Confidential

ZXWR RNC Alarm and Notification Handling Reference

This page intentionally left blank.

ZTE Proprietary and Confidential

2.1 Equipment Alarm

ZTE Proprietary and Confidential

ZXWR RNC Alarm and Notification Handling Reference

2.1.2 198083027 RSVB Offline alarm

ZTE Proprietary and Confidential

2.1.3 198019456 HSSLS are all out of synchronization

ZTE Proprietary and Confidential

ZXWR RNC Alarm and Notification Handling Reference

2.1.4 198019465 CSIX RX and TX packets is abnormal

ZTE Proprietary and Confidential

2.1.5 198005633 Hard Disk Broken

ZTE Proprietary and Confidential

ZXWR RNC Alarm and Notification Handling Reference

2.1.6 198005635 The board is not plugged firmly

ZTE Proprietary and Confidential

2.1.7 198005639 High Error Rate of Optical Interface

ZTE Proprietary and Confidential

ZXWR RNC Alarm and Notification Handling Reference

2.1.8 198005640 FPGA Exception

ZTE Proprietary and Confidential

2. Replace the board.

2.1.9 198005644 The Channel in a Subcard Is Down

ZTE Proprietary and Confidential

ZXWR RNC Alarm and Notification Handling Reference

2.1.10 198005645 Subcard Abnormal

ZTE Proprietary and Confidential