ZTE RNC Alarm and Notification Handling Reference

ZXWR RNCRadio Network Controller

Alarm and Notifica-tion Handling Reference

Version 3.09.30

ZTE CORPORATIONNO. 55, Hi-tech Road South, ShenZhen, P.R.ChinaPostcode: 518057Tel: (86) 755 26771900Fax: (86) 755 26770801URL: http://ensupport.zte.com.cnE-mail: [email protected]

LEGAL INFORMATION

Copyright © 2010 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution ofthis document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPO-RATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATIONor of their respective owners.

This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions are dis-claimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-in-fringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on theinformation contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subjectmatter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee,the user of this document shall not acquire any license to the subject matter herein.

ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.

Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.

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

Revision History

Revision No. Revision Date Revision Reason

R1.0 20100609 First Edition (V3.09.30.03)

R2.0 20100915 Second Edition (V3.09.30.06)

Add new alarm and Notification: 198002625,198002880, 198003841, 198005189, 198005403,198005404, 198005405, 198005669, 198005718,198005893, 198015168, 198020805, 198020806,198026176, 198029952, 198029953, 198066066,198066067, 198066068, 198066071, 198083042,198083043, 198083044 and 198083045

Delete alarm and Notification: 198083031

Update alarm and Notification: 198000256,198001286, 198005121, 198005121, 198005122,198005126, 198005645, 198005646, 198005649,198018243, 198018944, 198023106, 198025861,198066064, 198083003, 198083025, 198083029,198083032, 198083033, 198083039, 198083040,198000002, 198000576, 198001026, 198001284,198001600, 198001792, 198003394, 198003395,198005122, 198005389, 198005390, 198005396,198005398, 198005448, 198005663, 198005667,198005711, 198015617, 198018944, 198019207,198019712, 198019713, 198019714, 198019777,198020802, 198020803, 198025602, 198025856,198025857, 198025860, 198025861, 198025862,198025863, 198025866, 198025868, 198026118,198066010, 198066011, 198066014, 198066047,198066048, 198066049, 198066050, 198066064,198070003, 198070004, 198070005, 198070008,198070009, 198070010, 198070011, 198083003,198083017, 198083020, 198083021, 198083022,198083023, 198083025, 198083027, 198083028and 198083029

Serial Number: SJ-20100603155704-004

This page is intentionally blank.

Contents

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

Overview...........................................................1Overview of Fault Management......................................... 1

Fault View ..................................................................... 1

Alarm ....................................................................... 1

Notification ................................................................ 2

Alarm ........................................................................... 2

Alarm Property........................................................... 2

Alarm Code ....................................................... 2

Description........................................................ 2

Severity............................................................ 2

Alarm Type........................................................ 3

Probable Cause .......................................................... 3

System Impact........................................................... 3

Handling Suggestion ................................................... 4

Notification .................................................................... 4

Notification Property ................................................... 4

Notification Code................................................ 4

Description........................................................ 4

Importance ....................................................... 4

Notification Type ................................................ 4

Probable Cause .......................................................... 5

System Impact........................................................... 5

Handling Suggestion ................................................... 5

Alarm ................................................................7Equipment Alarm............................................................ 7

198083003 Log server unavailable................................ 7

198083022 Cell is out of service ................................... 8

198083023 Node B out-of-service alarm.......................10

198083027 RSVB board offline alarm ...........................11

198019456 HSSLS are all out of synchronization ...........11

Confidential and Proprietary Information of ZTE CORPORATION I

ZXWR RNC Alarm and Notification Handling Reference

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

198005633 Hard Disk Broken......................................12

198005635 The board is not plugged firmly ..................13

198005639 High Error Rate of Optical Interface ............14

198005640 FPGA Exception ........................................14

198005644 The Channel in a Subcard Is Down ..............15

198005645 Subcard Abnormal ...................................15

198005646 Phase-locked Loop Unlocked.......................16

198005647 High Error Rate at E1 Bottom Layer ............17

198005656 Loss of Clock When Input to Sub-card .........18

198005663 M28529 chip failure on board IMAB or DTA

affecting services...............................................18

198066044 Fault on Board (GPS) ................................19

198001284 The phase of 8K, 16K clock, input to

backplane board, is not matched .........................20

198001286 Input clock of board lost ............................21

198000002 Loss of optical signal .................................21

198015874 Physical channel for data transmission

blocked ............................................................22

198015875 GLI table lookup failed...............................23

198015876 GLI exception packets statistic over

threshold..........................................................23

198002560 The usage of CPU is over the threshold .........24

198002561 CPU temperature over threshold .................24

198005376 Internal Port of Board Is Down....................25

198066070 Board Doesn't Exist/ CPU is in Reset Status

for a Long Time.................................................26

198005381 Input clock is abnormal .............................27

198005389 CPU sub card in position is not configured

in the database. ................................................27

198005390 CPU sub card is missing from slot but is

configured in database .......................................28

198005395 External Port of Board Is Down ...................28

198005399 DSP resource is unavailable........................29

198026116 CLKG PP2S Output Clock Lost ....................30

198026117 PP2S clock reference lost ...........................30

198026118 16CHIP clock reference lost........................31

198026127 Clock reference source lost (Level 3 alarm)

.......................................................................31

II Confidential and Proprietary Information of ZTE CORPORATION


.......................................................................32


.......................................................................32

198026131 CLKG board PLL out-of-lock .......................33

198026133 Output clock lost.......................................34

198005632 Usage rate of board hard disk above

threshold .........................................................34

198005637 Error in Rear Board That Mismatches With

Front Board ......................................................35

198005661 Physical link down between master/slave

media interactive ports.......................................35

198005662 IDE running overtime ................................36

198005667 E1 is looped back......................................36

198005671 Incorrect FE Routing Connection .................37

198005668 Self board has cross-linked E1 ....................38

198005655 DSP Reports Exceptions After

Detection .........................................................38

198005124 Capacity of intra-shelf control plane TRUNK

communication is insufficient...............................39

198005125 Incorrect Connection of GE Optical

Transceiver Module ...........................................40

198025602 TDM switch abnormal ................................40

198029952 802.3ah link fault .....................................41

198005669 Synchronization status check of FPGA

failed ...............................................................42

198005893 Memory check failed..................................42

198005403 Board SRAM self-check fails .......................43

198005404 Board OCXO oven fault ..............................43

198005405 Clock board phase-lock loop work mode

abnormal..........................................................43

Communication Alarm....................................................44

198000256 Ethernet physical link broken......................44

198083021 CCP transmission link fault .........................45

198001792 SDH/SONET fault ......................................45

198083036 DSAR Alarm .............................................47

198083038 Transport Path group Occupied Bandwidth

Overload ..........................................................48

198083039 IP channel of Iub interface is faulty .............48

Confidential and Proprietary Information of ZTE CORPORATION III


198083040 TCP connect on IuBC interface is

interrupted ......................................................49

198022784 BFD Session Interrupted ............................49

198066029 PPP link broken.........................................51

198018944 PVC link is down. ......................................52

198019213 LIF Alarm of Near-End Receiving Link ..........53

198019214 LODS Alarm of Near-End Receiving Link

.......................................................................54

198019215 RDI alarm of far end receiving link ..............55

198019223 Ne Group is in fault state ...........................55

198066026 Association path broken.............................56

198005666 The number of the error packets from MAC

port exceeds the threshold..................................57

198066045 Trunk error ..............................................57

198066046 Trunk abnormal ........................................58

198066047 Abnormal status in SDH/SONET ..................59

198066048 SDH/SONET Excessive Error Code ..............63

198001026 Loss of ATM Cell Synchronization over E1

Link ................................................................64

198066049 ATM link is down ......................................65

198015617 Frames Received by

FE/GE/ATM/MP/POS/E1 Port are faulty. .................66

198015873 Faulty frames received by internal

switching interface.............................................66

198005378 Board HW Error ........................................67

198005651 IPMAC conflict when OSS detects control

plane ...............................................................68

198066003 Control plane communication is abnormal

between board and its home module ....................69

198066004 Control plane communication is abnormal

between MP and OMP.........................................69

198005382 Communication between power board and

OMP board is abnormal ......................................70

198005396 Exceptional communication on UIM board

or back plane ...................................................70

198005397 Communication of RAWMACIP channel is

abnormal..........................................................71

198005401 Test packet check abnormal .......................72

198005121 Inter-shelf media plane links abnormal .........73

IV Confidential and Proprietary Information of ZTE CORPORATION

198005122 Loss of Active/standby communication

link..................................................................74

198066060 FE Link Error Alarm ...................................74

198005128 Duplicate rack and shelf.............................75

198066005 SCCP subsystem unavailable .....................75

198066007 Broadband link overload ............................76

198066010 RNC unable to connect to MTP3 office ..........77

198066011 MTP3 link unavailable ................................77

198066014 RNC unable to connect to M3UA office .........78

198066019 Association link broken ..............................79

198029953 The Ethernet port state is OAM loop back

.......................................................................80

198003841 The control plane retransfer ratio over the

threshold..........................................................80

198083045 Common Channel setup failed Alarm ...........81

198066071 Link broken for board fault .........................82

198066066 AAL2 Path locally blocked...........................82

198066067 AAL2 Path remotely blocked .......................83

198066068 AAL2 Path blocked by broken PVC ...............83

Processing Alarm...........................................................84

198083020 RNC system resources limits reached, no

new UE's can attach to the network ....................84

198083024 GPS receiver on ICM is abnormal ................84

198019207 Near-End IMA Group Configuration

Failure .............................................................85

198015360 Microcode Is Abnormal ..............................85

198023040 The number of board alarms exceeds the

threshold..........................................................86

198066031 The number of OMP alarms exceeds the

threshold..........................................................86

198066032 NTP time exceeds threshold .......................87

198066027 SNTP failure .............................................87

198005387 Alarm Due to Inconsistent MP Type .............88

198005388 Startup File Does Not Exist.........................89

198005398 Office ID is not set correctly with control

shelf. ..............................................................89

198066057 Database config is different from file

named bootcfg ini..............................................90

198005649 Port working mode doesn't match with its

setting. ............................................................90

Confidential and Proprietary Information of ZTE CORPORATION V


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

198005126 Incorrect FE Routing Connection .................92

198066006 Broadband link congestion ........................93

198066013 MTP3 link congestion.................................94

198066018 Association congestion...............................95

198019712 loss of protection switching ........................95

198019713 loss of protection switching ........................96

198019714 APS configuration alarm. ..........................97

Environment Alarm........................................................98

198025856 Rack temperature is high. ..........................98

198025857 Low temperature in Rack ...........................99

198025858 House temperature is higher than high

threshold .........................................................99

198025859 House temperature is lower than low

threshold ....................................................... 100

198025860 Rack voltage is high ............................... 100

198025861 rack voltage is low .................................. 101

198025862 Humidity is high .................................... 102

198025863 Humidity is low....................................... 102

198025864 Fault in fan plug-in box ........................... 103

198025865 Rack door alarm ..................................... 103

198025866 Smoke detected...................................... 104

198025867 Infrared alarm........................................ 104

198025868 Lightning alarm ...................................... 105

198066064 Loss of DC power supply to rack ............... 105

QoS Alarm.................................................................. 106

198023296 Inter-board message communication flow

rate exceeds the alarm threshold ....................... 106

198066069 The number of times of signaling data

transfer exceeds the allowed threshold of the

license ........................................................... 106

198083042 IU PS traffic over load alarm..................... 107

198083043 IU CS traffic over load alarm .................... 107

198083044 IU traffic over load alarm ......................... 108

Notification ...................................................109198083017 RUB board has reached maximum number of

routes................................................................ 111

198070002 Iu interface global reset notification............... 111

198070003 Iu interface resource reset notification........... 112

VI Confidential and Proprietary Information of ZTE CORPORATION

198070004 RNC initiate Iu interface global reset failure

notification ......................................................... 113

198070005 RNC initiate Iu interface resource reset failure

notification ......................................................... 113

198070008 RNC and Node B are configured with different

CCPID................................................................ 114

198070009 Broadcast failure......................................... 114

198083025 Common Channel is abnormal ...................... 116

198070010 FTP failure and file lost ................................ 117

198070011 RNC alarm storage disc is full ....................... 118

198083028 Performance file server unavailable ............... 118

198083029 Unable to save Performance File ................... 119

198083019 MicroCode subsystem failed to get the table

of configuration ................................................... 120

198083026 MicroCode subsystem failed to handle DHCP

message from other network................................. 122

198083030 Bandwidth automatic adjustment is

useless............................................................... 123

198083032 TCP connect on IuBC interface is interrupted

......................................................................... 124

198083033 The deviation of slave clock is too large. ......... 125

198083034 External Clock of Slave lost notification.......... 125

198083035 Transport Path Occupied BandWidth

Overload ............................................................ 126

198083037 All Local Cell ID configured at RNC side are

differ from which on Node B side ........................... 126

198020291 Protocol stack process failed to initialize

during power on .................................................. 127

198020802 Conflicting IP address in subnet. .................. 127

198020803 Conflicting MAC Addresses in Subnet ............. 128

198020804 Failed to generate static ARP from IP

address.............................................................. 129

198066065 SCTP Primary Path Set Failed........................ 130

198030016 Ethernet link OAM event .............................. 130

198000576 Loss of Frame on Trunk ............................... 131

198066050 MCC is faulty.............................................. 131

198001600 CPU resets on a board ................................. 132

198017216 Error in MCS Multi-Core processor receiving

configuration data from DBS ................................. 132

198018240 TCP Receives RST Packet ............................. 133

Confidential and Proprietary Information of ZTE CORPORATION VII


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

198018242 MD5 Verification Failure ............................... 134

198018243 Wrong MD5 Message Abstract....................... 134

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

198023107 The board initialization failure....................... 135

198023617 Configuration file is unusable........................ 136

198003138 FLASH device initialize failed ........................ 136

198003394 Start daylight saving time ............................ 137

198003395 End daylight saving time.............................. 137

198005441 Port status on internal media plane

changed. ............................................................ 138

198005448 485 seriel bus link between CLKG/PWRD and

OMP is broken..................................................... 139

198026177 CLKG reference quality changed ................... 139

198026178 Clock work mode changed............................ 140

198005705 MCU resets for abnormities .......................... 140

198005710 The result of base selection of sets chip ......... 140

198005711 clock reference selection is being

executed. ........................................................... 141

198005712 The manual select base will be run, please

wait for the result ................................................ 141

198005713 APC's RAM error ......................................... 142

198005715 PP2S source switched.................................. 142

198005717 The physical address information of the board

is incorrect ......................................................... 143

198005716 Type B fault on board (GPS) phase-lock

equipment .......................................................... 143

198005700 DSP resets for abnormities........................... 144

198005701 Version Load Error ...................................... 145

198019777 APS switch over occurred............................. 146

198005188 UIM CS Changeover .................................... 147

198005192 Board's Work Mode Unsupported................... 148

198005193 Notification of the power-on status of the

basic process ...................................................... 148

198005956 Board Version Error..................................... 149

198005958 IDE Version Files Synchronization

Information ........................................................ 150

198005961 OMP Version Check Information .................... 150

198005962 Patch version operate fail ............................. 151

VIII Confidential and Proprietary Information of ZTE CORPORATION

198010560 No message response in the link for a long

time .................................................................. 152

198011840 M3UA user office status change .................... 152

198013888 ASP status changed .................................... 153

198013889 AS status changed ...................................... 154

198013890 Sigtran error message received .................... 154

198013891 Sigtran notification message received ............ 155

198013892 Allocate memory fail ................................... 156

198014144 Association establishment failed.................... 156

198014145 Association restart ...................................... 157

198025664 Abnormal Half-fixed Connection

Changes............................................................. 158

198008005 Memory file buffer overflow.......................... 159

198002625 Process is deadlocked.................................. 159

198002880 CPU occurs dead-loop.................................. 160

198005718 Two master clock ports is directly

connected........................................................... 160

198005189 Notification of Active/Standby

Changeover ........................................................ 161

198026176 Clock reference changed.............................. 161

198020805 ARP detect failed ........................................ 162

198020806 ARP detect that the static ARP is not

match ................................................................ 162

198015168 AAL2 Path blocked by resetting process ......... 163

Figures ..........................................................165

Tables ...........................................................167

Confidential and Proprietary Information of ZTE CORPORATION IX



X Confidential and Proprietary Information of ZTE CORPORATION

About This Manual

Purpose At first, thank you for choosing ZTE UMTS RAN of ZTE Corporation!

ZXWR RNC, the new generation radio network controller of ZTEUMTS V3 series products, performs functions of system accesscontrol, security mode control, mobility management, and radioresource management and control, etc.

ZXWR RNC provides all the functions defined in the 3GPPR99/R4/R5/R6/R7 protocol, and offers Iu, Iub, and Iur seriesstandard interfaces.

ZXWR RNC is based on ZTE all IP unified hardware platform, uti-lizes distributed design, supports ATM/IP dual protocol stack andcan smoothly evolve to IP UTRAN. It aims at saving operator’s in-vestment in 3G network construction by offering a large capacityand linear expandable system once and for all.

This manual introduces the alarms that might occur during theinstallation, operation and maintenance of the ZXWR RNC product.

IntendedAudience

This guide is intended for engineers and technicians who performoperational activities on ZXWR RNC.

Prerequisite Skilland Knowledge

To use this guide effectively, users should have a general under-standing of telecommunications technology. Familiarity with thefollowing is helpful:

� ZXWR RNC system and its various components

� User interfaces on the ZXWR RNC system

� Local operating procedures of the ZXWR RNC system

What is in ThisManual Chapter Summary

Chapter 1, Overview Introduces the concept of faultmanagement, as well as the definition,type, level classification of alarm andnotification.

Chapter 2, Alarm Introduces RNC alarms with respect toalarm property, probable cause, systemimpact, and handling suggestion.

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

FCC ComplianceStatement

This device complies with part 15 of the FCC Rules. Operation issubject to the following two conditions.

1. This device may not cause harmful interference.

2. This device must accept any interference received, includinginterference that may cause undesired operation.

Confidential and Proprietary Information of ZTE CORPORATION I


Changes or modifications not expressly approved by the party re-sponsible for compliance could void the user's authority to operatethe equipment.

II Confidential and Proprietary Information of ZTE CORPORATION

C h a p t e r 1

Overview

Table of ContentsOverview of Fault Management............................................. 1Fault View ......................................................................... 1Alarm ............................................................................... 2Notification ........................................................................ 4

Overview of FaultManagementFault management is responsible for collecting information of fail-ures and events that occur during system operation or service pro-cessing.

The information, in the form of alarm or notification, is stored indatabase or displayed on realtime basis via a user-oriented faultmonitoring platform. Means such as visual-interface monitor orhistory information query can be used to view current or histor-ical system operation and service processing status. Fault man-agement enables maintenance personnel to troubleshoot and takepreventive measures to remove potential fault and restore systemand services as early as possible.

Fault ViewFault is displayed in the form of alarm or notification.

Alarm

The fault that persists during system operation and affects systemreliability and normal services is referred to as an alarm. Alarmusually lasts until fault removal.

Due to its possible impact on normal system operation, alarm re-quires timely troubleshooting in which alarm cause is identified,and the fault is located and handled.

Confidential and Proprietary Information of ZTE CORPORATION 1


Notification

Notification refers to the non-repeated/instantaneous fault orevent that occurs during system operation. Examples includeboard reset, signaling overload, etc.

Notification is mostly caused by sudden environment changeor other accidental factors. No special handling is required forthe notification, which can be automatically removed by thesystem. Only the notification that occurs persistently requirestroubleshooting.

AlarmAlarm Property

Alarm Code

Alarm code is the identifier which differentiates alarms.

Alarm code is defined by a 32-bit field indicating the specific codevalue.

Description

Alarm description reflects such content as fault cause and faultphenomenon in a simple and straightforward way.

Severity

There are four alarm levels, which are indicated in descending or-der of severity as Critical, Major, Minor, and Warning.

� Critical alarm causes system breakdown and service interrup-tion. It requires immediate troubleshooting.

� Major alarm significantly affects system operation or weakensnetwork service capability. It requires troubleshooting as soonas possible.

� Minor alarm affects system operation and network servicecapability in a nonsignificant way. It requires timely trou-bleshooting so as to avoid severity escalation.

� Warning poses a potential hazard to system operation and net-work service capability. It requires troubleshooting at an ap-propriate time so as to avoid severity escalation.

2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Overview

The degree of impact as described in the definition of alarm sever-ity refers to the impact of a single index, such as reliability andsecurity. Once the impact on any of the index reaches the speci-fied threshold, the severity level of the alarm can be roughly de-termined. If an alarm has an impact on multiple indices, alarmseverity should be escalated accordingly.

Note:

Alarm severity can be modified in NetNumen M31 NMS (networkmanagement 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 tousers to define the severity of such alarms.

Alarm Type

Alarm is classified into six types according to alarm trigger condi-tion and its system impact.

� Equipment alarm: related with device hardware.

� Communication alarm: related with information transmission(ITU-T Recommendation X.733).

� Processing alarm: related with software or process fault (ITU-TRecommendation X.733).

� Environment alarm: related with the environment where theequipment is located (ITU-T Recommendation X.733).

� QoS alarm: related with degradation of service quality (ITU-TRecommendation X.733).

� OMS alarm: related with the network management system.

Probable Cause

Probable alarm causes are enumerated to help users troubleshoot,find preventive measures, and restore the system to normal statein a timely manner.

System Impact

System impact refers to the impact that the alarm incurs on sys-tem or services.



Handling Suggestion

Troubleshooting measures and suggestions are provided.

Pay attention to the following tips when handling alarms.

� After recording the fault phenomenon, O&M personnel mayhandle the fault step by step as described in the Handling Sug-gestion Section of this manual. If the fault is removed (alarmrestored) 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 assoon as possible.

NotificationNotification Property

Notification Code

Notification code is the identifier to differentiate notifications.

Notification code is defined by a 32-bit field indicating the specificcode value.

Description

Notification description reflects such content as fault cause andfault phenomenon in a simple and straightforward way.

Importance

There are two levels of notification importance: Important andOrdinary.

Notification Type

No notification type exists.


Chapter 1 Overview

Probable Cause

Probable notification causes are enumerated to help users trou-bleshoot the system in a timely manner and take preventive mea-sures to ensure stable system operation.

System Impact

System impact refers to the impact that the notification incurs onsystem or services.

Handling Suggestion

Troubleshooting measures and suggestions are provided.

Pay attention to the following tips when handling notifications.

� After recording the fault phenomenon, O&M personnel mayhandle the fault step by step as described in the Handling Sug-gestion Section of this manual. If the fault is removed (alarmrestored) 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 assoon as possible.





C h a p t e r 2

Alarm

Table of ContentsEquipment Alarm................................................................ 7Communication Alarm........................................................44Processing Alarm...............................................................84Environment Alarm............................................................98QoS Alarm...................................................................... 106

Equipment Alarm198083003 Log server unavailable

Alarm Type Equipment Alarm

Alarm Purpose External Alarm

Alarm Classifica-tion

Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Log server is unavailable.

2. Break in communication between RNC and Log server.

ProcessingSuggestion

1. Check the log server by performing the following steps to seeif the control-plane communication is normal:

i. Open a terminal dialog box in the LINUX system.

ii. Enter the SHELL command "ping 128.0.31.1" to see if the pingtest is successful. If not, troubleshoot the control-plane commu-nication.

2. Check the log server to see if the LogService runs normally.If not, restart the LogService by running “/startsys” under the“/home/zte/LogService/bin” directory.

Alarm Impact Log/performance files cannot be reported to the log server.



198083022 Cell is out of service




Alarm

Alarm Level Critical

Disaster Alarm Yes

FrequentlyReported

Yes

Cause of Alarm 1. RRU faulty.

2. cell is blocked by user.

3. Cell ID is incorrect or deleted.

4. Node B or BTS restarted or down.

5. Node B Cell frequency is not consistent with RNC.


View alarm details on the NMS Alarm Management interface tocheck the Alarm reason, which can help you easily find the corre-sponding handling suggestions.

The handling suggestions for each alarm are as follows:

1. Alarm reason: Node B returns a message, indicating cell setupfailure.

1) Check the frequency points of the RNC and the Node B to seeif they are consistent with those of the local cell by following thesteps below:

Click Base Station Radio Resource Management > WCDMA Ra-dio Resource Management > Baseband Resource Pool on the NMSConfiguration Management interface, and then select the local cellto be viewed. Check Rx Frequency and Tx Frequency in "Local CellBasic Parameters" to see if they are consistent with those at theRNC side. If not, modify the RNC or Node B configurations to makethem consistent.

2) Check if the Node B generates a "198084129 Board rebootsalarm" on the NMS Alarm Management interface. If yes, it indi-cates that the Node B was started or its hardware was replaced oradded just now. In this case, wait until the Node B is powered on.

2. Alarm reason: The Cell Configuration Generation ID (CGID)audited and reported by the Node B is zero.

1) The local cell is blocked.

Click Base Station Radio Resource Management > WCDMA Ra-dio Resource Management > Baseband Resource Pool on the NMSConfiguration Management interface, and then select the cell to beviewed. Check "Local Cell Status Parameters" to see its manage-ment status. If the cell is blocked, unblock it.

2) Node B is blocked or faulty.

Check the status of the Node B on the Ground Resource Configu-ration interface. If it is blocked, unblock the Node B. If the NodeB fails, the FS board may be faulty. In this case, check if any of


Chapter 2 Alarm

the following alarms occurs. If yes, follow the corresponding sug-gestions to handle it.

198084117 Application software monitoring alarm

198084123 Board communication link is interrupted

198084107 Board parameter synchronization abnormality

3) The local cell is faulty.

Check the "Local Cell Status Parameters" interface. If the currentstatus is faulty, it indicates that the FS or the RTR board is faulty orrestarted. In this case, check if any of the following alarms occurs.If yes, follow the corresponding suggestions to handle it.




198084129 Board reboots alarm

4) The baseband board is blocked.

Check the status of the BPC board. If the board is blocked, unblockit.

5) The baseband board is faulty.

Check the status of the BPC board. If the status is faulty, check ifany of the following alarms occurs. If yes, follow the correspondingsuggestions to handle it.




198084129 Board reboots alarm

3. Alarm reason: There is a real-time cell blocking at the Node Bside.

Click Base Station Radio Resource Management > WCDMA RadioResource Management > Baseband Resource Pool On the NMSConfiguration Management interface, and then select the cell tobe viewed. If the cell is blocked, unblock it.

4. Alarm reason: The failure to update system message results incell deletion or creation.

Handle it according to the suggestions given for "198070009Broadcast failure".

5. Alarm reason: The cell parameters configured at RNC side isincorrect.

On NMS configuration management interface, select the RNCWire-less Resource Management > Service Cell, check the cell param-eters as follows:

1) Cell Capability and Cell Reselect Parameters

2) Senior Parameters: Load Control, Balance Parameters, AcceptControl, HSPA Configure, Mbms Configure.

6. Local cell is blocked at Node B side.



On NMS configuration management interface, select the cell to beviewed under Base Station Radio Resource Management >WCDMARadio Resource Management >Baseband Resource Pool. View theStatus in Local Cell Status Parameters. If the status is blocked,unblock it.

7. For other alarm causes, the system will automatically recreatecells. In this case, no manual operation is required.

Alarm Impact The cell is unavailable and inaccessible, providing no service.

198083023 Node B out-of-servicealarm




Alarm


Disaster Alarm Yes

FrequentlyReported

Yes

Cause of Alarm 1. Transmission is faulty.

2. Node B is down.


The handling suggestions are classified by transmission mode.

1. IP mode

Check the Alarm Management interface according to the associa-tion ID to see if there is any of the following association-relatedalarms. If yes, follow the corresponding suggestions to handle it.

198066018 Association congestion

198066019 Association link broken

2. ATM mode

1) Bottom layer transmission fault

Check to see if there is any of the following alarms. If yes, followthe corresponding suggestions to handle it.

198001792 SDH/SONET fault

198066047 Abnormal status in SDH/SONET

198066048 SDH/SONET: Excessive Error Code

198005639 High Error Rate of Optical Interface

2) Unavailable PVC link

Check to see if the following alarm exists. If yes, follow the corre-sponding suggestions to handle it.

198018944 PVC Fault

Alarm Impact The Node B is unavailable and inaccessible, providing no service.


Chapter 2 Alarm

198083027 RSVB board offline alarm




Alarm


Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. RSVB board is not plugged into shelf.

2. RSVB board is faulty.

3. RSVB board is not firmly inserted into slot.


1. Check if the RSVB is extracted.

If yes, insert the RSVB into the rear slot again.

If not, extract and insert the RSVB.

2. Replace the RSVB.

Alarm Impact If the SBCX to which the RSVB corresponds acts as a log server,the OMM cannot obtain performance data from the log server.

198019456 HSSLS are all out ofsynchronization




Alarm


Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. The PSN board type configured does not accord with the PSNboard type actually in use.

2. PSN board hardware (VSC882 chip) is faulty.

3. Line card hardware (VSC872/VSC874 chip) is faulty.


1. Check whether PSN board reboots repeatedly. If yes, Checkwhether the PSN board type configured is consistent with the PSNboard type actually in use.

1) If inconsistent (for example, the configured board type is PSN4Vand the board type actually in use is PSN8V), modify board typeconfiguration or replace the board actually in use to keep consis-tency between board configuration and the board in use.



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

2. If the alarm occurs in line card, check if the same alarm occursin other line card(s) located in the same shelf with the faulty linecard.

1) If the same alarm occurs in all other line cards, PSN board mightbe faulty. Reboot PSN board and check if the line card alarms arerestored. If alarms are not restored, replace PSN board.

2) If merely the line card where this alarm occurs reboots repeat-edly, replace the board where the alarm is generated.

Alarm Impact 1. All services on the equipment are down if the alarm is causedby Cause 1 or Cause 2.

2. All services on the line card are affected if the alarm is causedby Cause

3. If the service is not configured in master/slave or load sharingmode, all services on the line card will be down. If the service isconfigured in master/slave or load sharing mode, all services onthe line card will soon be restored after being down temporarily.

198019465 CSIX RX and TX packetsis abnormal




Alarm

Alarm Level Warning

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Signal is unstable when rack or board is powering on.

2. Switch chip is abnormal.


1. Reset the board.

2. Replace the board.

Alarm Impact The transceiver of the media plane is exceptional.

198005633 Hard Disk Broken




Alarm

Alarm Level Major


Chapter 2 Alarm

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm There is failure in ribbon cable connection or the hard disk. Thisis usually a hardware failure.


Replace the hard disk on the board or replace the board.

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 startup failure and service accessing failure.

2. Hard disk failure in the log server may cause data loss of theperformance data stored on the ROMP hard disk in the abnormalstatus.

3. When a peripheral board is starting up and requesting versionfrom ROMP, Hard disk failure may cause start up failure and poweroff of the peripheral board.

198005635 The board is not pluggedfirmly




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. The ENUM switch on the board is ON, or is not firmly connected.

2. Or the EXCH key on the standby board is pressed twice within3 seconds.


1. Check the ENUM switch and turn it on. If it is not turned on.

2. Switch off and switch on ENUM.

3. If the ENUM open status is simulated by pressing the EXCH keyon the standby board twice within 3 seconds, press the EXCH keyon the standby board twice within 3 seconds.

Alarm Impact Cause failure in active/standby board switching, or cause failurein APS switching. Do not switch this board into active board.



198005639 High Error Rate of OpticalInterface




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm The fiber is not completed connected to the port, or is damaged,or is not compatible with the optical transceiver module in T-net-work switch. There is no light signal input into the optics module.This alarm is dedicated to the TDM optical port only. The possiblecauses of this alarm include:

1. TDM receiver fiber optics failure, fiber optics module failure.This type of failures include: damaged fiber on the receiver, un-connected fiber, contaminated fiber or damaged optics module onthe receiver.

2. Fiber optics failure at the transmitting module on the corre-sponding TDM. This type of failures include: damaged fiber on thetransmitter, unconnected fiber, and contaminated fiber.

3. Compatibility between fiber optics and optics module. Thefiber transmission rate of TDM signal is incompatible with the wavelength of the optics module.

4. Loss of signal (LOS) alarm operation is performed on the cor-responding SDH device. This includes the manual diagnosis testalarm operation.


1. Perform loopback test to determine source of this alarm is onthe local devices or the corresponding devices. Perform self-looptest on local device. If the failure persists, the failure source ison local device; if the failure disappears after self-loop test, thenthe source of failure is on the corresponding device. Contact thecorresponding 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 portwhich affects the quality of all the services performed on this op-tical port.

198005640 FPGA Exception



Chapter 2 Alarm



Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm FPGA runs abnormally, for example, FPGA is lost, or the boardclock is lost.


1. Restart the board. In this case, the board downloads FPGAagain.


Alarm Impact FPGA verification fails. The read and write function of FPGA cannotbe ensured. The board cannot provide complete functions andwork normally. The service carried by the board is interrupted.

198005644 The Channel in aSubcard Is Down




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. The sub-card is not inserted in position.

2. The sub-card has hardware faults.


1. Unplug and plug the sub-card again. Wait for the board to bepowered 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 cannotbe used normally. This affects the service carried by the boardof the sub-card. After the channel is available and the alarm iseliminated, the service is recovered.

198005645 Subcard Abnormal






Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. The GCS, EC or HPS subcard of UIMC/GUIM/CHUB is not in-serted in position.

2. The subcard is faulty.


1. Check the sub-card connection. If the connection is loose,tightly insert the sub-card and wait for the board to be poweredon.

2. Replace the sub-card.

Alarm Impact The GCS sub-card of the UIMC/GUIM/CHUB can not function nor-mally. Packets will be lost. In some cases, control plane links willbe disconnected. For active/standby configuration, there are twocases:

1. If the active board is abnormal but the standby board is normal,the system will perform an active/standby changeover. As a result,the standby board will take over the services borne on the faultyactive board. In this case, services may not be affected.

2. If both the active and standby boards are abnormal, the ac-tive/standby changeover can not be performed. In this case, ser-vices will be interrupted because the faulty board can not be backto normal.

198005646 Phase-locked LoopUnlocked




Alarm


Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. The clock extraction reference is changed. For example, theclock output is disabled by the interface board when the opticalport is faulty, which results in changes in clock input. The config-uration in the NMS is changed, so that a new optical port is usedto extract clock signals.

2. The input of the clock board is changed and the output ischanged accordingly.

3. The UIMC/GUIM input is disconnected, or the PLL on theUIMC/GUIM is abnormal.


Chapter 2 Alarm

4. The hardware of the PLL on the board is faulty.


1. Check whether there is the following clock alarm on the NMSAlarm Management interface. If yes, handle it according to thecorresponding suggestions.

198005381 Input Clock Abnormal

2. Check whether there is any of the following alarms about theclock extracting optical port on the NMS Alarm Management inter-face. If yes, handle it according to the corresponding suggestions.




198000002 Signal Loss of Optical Module

3. Check the operation and maintenance log in the NMS to seeif there is a record about the change of the loop clock extractionreference. If yes, no handling is required.

4. Conduct an active/standby changeover to the clock board.

5. Conduct an active/standby changeover to the UIM/GUIM board.


Alarm Impact The service clock and the system clock will be asynchronous be-cause of the unlocked PLL on this board. As a result, servicesborne on the board will be interrupted.

198005647 High Error Rate at E1Bottom Layer




Alarm

Alarm Level Major

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm 1. The E1/T1 link is faulty.

2. The device in the uplink direction of the trunk link is faulty.

3. The trunk cable or connector is in poor contact.


1. Conduct a meter measurement or loopback test to find outwhether the alarm is rooted in the local end or peer end. Metermeasurement: Connect a trunk test meter to check if the signalreceived by the local end trunk is normal. If yes, the fault is rootedin the local end. If the test shows the problem persists, the faultis rooted in the peer end. In this case, inform the peer end totroubleshoot. Loopback test: Perform self-loop at the trunk wherealarm occurs at local end. If the problem persists, it indicates thatthe 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 hasonly this link, all services on the port are interrupted. Otherwise,only the port bandwidth is affected. The quantity of upper layer ac-cess services associated with the port is decreased. The accessedbandwidth is reduced. The service, however, is not interrupted.

198005656 Loss of Clock When Inputto Sub-card




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. The sub-card is not inserted in position.

2. The clock circuit of the sub-card is damaged.

3. The clock circuit of the mother board is damaged.


1. Check the sub-card connection status. If the sub-card is loose,tightly connect it and power it on again.

2. Replace the sub-card


Alarm Impact The unavailable sub-card clock affects the normal operation of theboard. This may cause clock jittering, and the service that imple-ments media stream exchange through this board becomes un-stable. In the most serious case, the system clock is lost and theservice carried by the board is interrupted.

198005663 M28529 chip failureon board IMAB or DTA affectingservices.




Alarm


Chapter 2 Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm Devices or sub-cards on the board operate abnormally.


Replace the board.

Alarm Impact This alarm only occurs to the IMAB. When it occurs, the IMAB cannot operate normally and the trunk borne on the board will be bro-ken. As a result, users can not access the board and the existingservices will be interrupted.

198066044 Fault on Board (GPS)




Alarm


Disaster Alarm No

FrequentlyReported

No

Cause of Alarm According to alarm details, alarm status falls into three types: TypeA Fault on Board (GPS) Phase-lock Equipment Phase-lock Equip-ment of This Board (GPS) Is in Power-on Status The causes for thethree alarm types are described below.

1.Type A Fault on Board (GPS) Phase-lock Equipment Probablealarm causes include 16chip loss/out of lock, 12.8M loss/out oflock, PP2S output loss, 8K output loss, 10M output loss, and 1PPSloss.

2.Phase-lock Equipment of This Board (GPS) Is in Power-on Sta-tus The alarm cause is that the GPS module of ICM board is inpower-on status, and power-on has not been completed.


On NMS fault management interface, view alarm Details whereError type information is given. Locate the corresponding alarmhandling suggestion according to the error type. The alarm han-dling suggestions that correspond to the error types are describedbelow.

1.Type A Fault on Board (GPS) Phase-lock Equipment

1) On NMS test management interface, perform diagnostic test onICM board. Check the working status of the GPS module. If ClassA fault persists in the GPS module, replace the board.

2) Check if output clock loss occurs. If yes, replace the board.

2.Phase-lock Equipment of This Board (GPS) Is in Power-on Sta-tus If the alarm persists, hardware fault might exist. Replace theboard.



Alarm Impact Be usually determined as hardware fault, which affects systemclock. It might lead to the system clock loss and system synchro-nization failure. When system clock loss/offset occurs, its subse-quent impact on service is described below.

1.For TDM transmission, all links based on the TDM transmissionmedium (including the transmission link currently in service for UEand cell transmission link) are affected. Packet loss might occur onthese links, leading to degradation of service quality. In the caseof serious packet loss, service interruption and handover failurewill occur. Even worse, the cell might be out of service.

2.For non-TDM transmission (for example, IP transmission), Iubinterface service is affected, while Iur interface and Iu interfaceservices are not affected. The clock that Node B derives from RNCvia IEEE1588 is inaccurate. When RNC clock frequency offset isno more than 0.05 ppm, Node B synchronization will not fail, butsuccess rate of inter-RNC inter-Node B soft handover might fall.When RNC clock frequency offset exceeds 0.5 ppm, Node B willfail to lock the clock. In this case, Node B will oscillate freely andsuccess rate of inter-Node B soft handover might fall.

198001284 The phase of 8K, 16Kclock, input to backplane board, isnot matched




Alarm

Alarm Level Minor

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm 1. clock cable is not properly connected.

2. clock board is faulty.


1. Check the clock input cable and ensure that the cable is goodand well connected.

2. Clock board changeover.

3. UIM/GUIM board changeover.


Alarm Impact The system fails to achieve synchronization so that the board cannot work normally. As a result, UE can not be accessed and ser-vices borne on the board are interrupted.


Chapter 2 Alarm

198001286 Input clock of board lost




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. The board is not properly inserted to a slot.

2. A clock cable is not connected.

3. The clock cable is broken.

4. The board is faulty.


1. Check whether the clock input cable is properly connected.

2. Does the board have the following alarm? If yes, please solvethe problem according to corresponding handling suggestion.

Related alarm: 198005635 The board is not plugged firmly.


Alarm Impact The board fails to synchronize with system clock so that it can notwork normally. As a result, UE can not be accessed and servicesborne on the board are interrupted.

198000002 Loss of optical signal




Alarm


Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm 1. The receiving optical fiber/module of local equipment is faulty.

Receiving optical fiber is faulty or disconnected.

Optical connector is polluted.

Receiving optical module is faulty.

2. The transmitting optical fiber of opposite equipment is faulty.

Transmitting optical fiber is faulty or disconnected.


3. The receiving optical power at local end is excessively low.



Optical power attenuation on the receiving fiber transmission lineat local end is too much.

Transmitting optical power at opposite end is too low.

4. Operation of LOS insertion is performed at opposite end.

Manual operation of LOS insertion is performed in diagnostic test,and optical module is shutdown by force.

5. Optical fiber and optical module is incompatible.

The fiber transmission rate and the optical module wavelength areincompatible.


1. Carry out loop test to determine whether the alarm is causedby local end or opposite end. Perform fiber self-loop at local equip-ment. If the alarm persists, fault might lie in local equipment. Ifthe alarm disappears, inform the opposite end to troubleshoot.

2. Replace the optical module.

3. Replace fiber.

4. Replace board.

Alarm Impact The optical interface fails to work normally. If the optical inter-face is configured with APS protection, service will be switched toprotection optical interface. Otherwise, all services on the opticalinterface will be down.

198015874 Physical channel for datatransmission blocked




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. The traffic flow to the board is excessive.

2. The PSN board in the same shelf is abnormal.

3. The board has hardware faults.


1. On NMS fault management interface, check if the PSN in thesame shelf has generated related alarms. If yes, follow the sug-gestions on handling the related alarms. The related alarm is asfollows:

198019456 All high-speed links between line card and packageswitching board are out of synchronism

2. Unplug and plug the board.



Chapter 2 Alarm

Alarm Impact The services carried by the board are unstable. In most seriouscase, all services carried by the board are interrupted.

198015875 GLI table lookup failed




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. L1 table or L2 table error.

2. Destination IP of packets or hardware is error.


Switch the master port to the partner board.

Alarm Impact Packets would be dropped which would cause poor voice qualityand other problems.

198015876 GLI exception packetsstatistic over threshold




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Connection between fiber and optic modules is not perfect.

2. Something wrong with fiber optic module.

3. Board hardware error.


1. Check the connection between fiber and optic modules.

2. Reboot the board.

Alarm Impact Packets would be dropped which would cause poor voice qualityand other problems.



198002560 The usage of CPU is overthe threshold




Alarm

Alarm Level Major

Disaster Alarm Yes

FrequentlyReported

Yes

Cause of Alarm 1. Excessive data traffic at higher layer.

2. System is performing data synchronization or saving.

3. CPU alarm threshold setting is under configured.


1. Open the rack map on the Configuration Management window,select Board, right click and select Display Properties Tab. Checkthe CPU overload threshold setting on the Processor tab. Pleasereset CPU overload threshold if the CPU overload threshold value istoo 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 orother file operations in the network manager log files. Those op-erations might increase the CPU utilization rate radically, and itmight take 2 minutes.

3. Check for the record of new board added or version upgradeoperation in the network manager log files. Version upgradingoperation might increase CPU utilization rate radically, and it mighttake 2 minutes.

Alarm Impact CPU occupancy indicates the current status of system operation.CPU overloaded, or over high occupancy, is usually caused by ser-vice or operation that consume much time. It has the followingimpact on the system. Services with low priority level have littleor no access to the processing of CPU, which reduces processingspeed of the services or even halts the processing. System boardcould reset under excessively overloading conditions, causing in-terruption to the service it performs.

198002561 CPU temperature overthreshold




Alarm


Chapter 2 Alarm

Alarm Level Major

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm 1. Environmental temperature around rack is too high

2. Board hardware fault

3. The alarm threshold value is under configured.


1. Open the rack map on the Configuration Management window,select Board, right click and select Display Properties Tab. Checkthe Upper limit for alarm setting and reboot temperature setting onthe Processor tab. Please adjust the threshold value if the thresh-old value is too low. It will take 30 seconds for the new settingto take effect. Recommended Threshold: Upper limit for temper-ature alarm: 90 degree. Reboot Temperature: 95 degree.

2. Check the thermometer in machine room for accurate tempera-ture, and take effective measures when actual temperature is overhigh.

3. Check and clean the boards for dust accumulation which maycause heat trapped in the system.

4. Check and clean the air inlet and air outlet for dust accumulationor remove the impediments if any.

5. Check and make sure the fan(s) on the rack is in normal oper-ation.

6. Replace the relevant boards.

Alarm Impact The over high temperature of CPU may cause CPU to mal-operate,or even reset CPU and shut down the board service.

198005376 Internal Port of Board IsDown




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Physical failure of the IC at the internal port on the board.

2. Failure of local board connecting port on the switching IC ofUIM.

3. Backplane wiring failure of the local slot to UIM.

4. CUP overloaded on the first level switching board, UIM boardat the shelf, or local board.



5. Service over the rated capability of the board.


1. Check the Alarm Management window for the CUP overloadedon the first level switching board, UIM board at the shelf, or localboard. Perform recommended solution to process the alarm(s) ifany. Related Alarm:

198002560 Board CPU Overloaded

2. Check the Alarm Management window for the alarms of In-ter-shelf media plane links abnormal. Perform the recommendedsolution to process the alarm(s) if any. Related Alarm:

198005121 Inter-shelf Media Plane Link Error


4. Change the slot of the board.

5. Replace the UIM in the same shelf.

Alarm Impact When this port is not available for internal media stream trans-mission, the internal media stream will select other normal portsfor transmission.If all the internal ports fail to operate normally,the internal media stream will be interrupted and all the servicesprovided on this board will be interrupted

198066070 Board Doesn't Exist/ CPUis in Reset Status for a Long Time




Alarm

Alarm Level Major

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm 1. Board not properly positioned.

2. Hardware failure.


1. Check for the proper placing of the board, and insert the boardfirmly if it is nor properly placed.

2. Plug/unplug the board.


4. Replace the slot

5. Replace the UIM in the same shelf.

Alarm Impact If the board is operational, and the alarm is board position failure,it does not affect the service operation. The board is in blockedstatus, and no service by this board is available. If the board withalarm is resource board, then the resource is not available on thisboard.


Chapter 2 Alarm

198005381 Input clock is abnormal




Alarm


Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm 1. The clock does not stay the working state .

2. The base of the clock does not input to the clock board.

3. The base of the clock is abnormal.


1. Reconnect the cable between the board and the clock reference.

2. Replace the cable between the board and the clock reference.

3. Check the signal output from the reference clock source.


Alarm Impact System services is interrupted as no proper clock information isprovided to the system.

198005389 CPU sub card in positionis not configured in the database.




Alarm

Alarm Level Warning

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Configuration is incorrect.

2. Board is misplaced.


Is the subcard needed?

If no, remove the subcard.

If yes, change the type of board so that it can support the subcard.

Alarm Impact Since the board where the unconfigured subcard is located resetsrepeatedly, power resource of the equipment is wasted. However,services won't be affected.



198005390 CPU sub card is missingfrom slot but is configured in database




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. The configuration is wrong.

2. A wrong board is inserted.


Is the sub-card required?

If no, modify the type of board so that the new type doesn't sup-port such sub-card.

If yes, insert the sub-card firmly.

Alarm Impact The sub-card functions are unavailable, accordingly this boarddoes not support relevant services. The influence on the systemis various according to different type of sub-card.

If the sub-card is an interface board, the transmission link via thisboard is not connectable, then services will be accessed throughother sub-card. If the sub-card is a signaling process board, thecell/Node B configured for this board is not available for services. Ifthe sub-card is a user's plane board, user plane process capabilitywill decline, then services will be accessed through other sub-card.

198005395 External Port of Board IsDown




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. The port cable is not properly connected, or is not connected.

2. The IC of external board port is faulty.

3. The corresponding board is faulty.


Chapter 2 Alarm


1. Reconnect or replace the cable.


3. Contact the opposite engineers to check the opposite ports forpossible failure.

Alarm Impact This port is not available for the service. If there is a back for thisport, then data communicate through the back port, but the totalcommunication rate will decline. Also the reliability and stability ofthe system declines too. If there is no back for this port, then allthe office communication links through this port will not be avail-able, and the services through this port are not available.

198005399 DSP resource isunavailable




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm This alarm indicates the DSP resource is not available. It is mon-itored by higher level layer, and is reported once DSP is blocked,the report conditions include:

1. DSP version loaded failure, system is unable to operate nor-mally.

2. HPI port error on DSP

3. DSP media plane communication failure.

4. DSP reset.


1. Check the operation maintenance log files in network managerfor the operations of DSP version replacing. If there is operationof DSP version replacing which would cause DSP reset, then thealarm does not require procession, the DSP will resume operationalafter the resetting.

2. There is a DSP index in the detailed information of the alarm.Open the rack map on the Configuration Management window, se-lect Board, right click and select "Subunit Configuration". Selectthe DSP with alarm, and click Status at Subunit ConfigurationSta-tus Attribute Query Status. Then check if the Management Statusof DSP is Blocked. If it is Blocked, it means the alarm is a normalconsequence of manually blocking the DSP. Open the rack map onthe Configuration Management window, select Board, right clickand select "Subunit". Run Unblock DSP to resume DSP operation.

3. Check the Alarm Management window for the correspondingalarms. Perform the recommended solution to process the alarm,if any. Related Alarms:



198005701 Failure in Version Loading of DSP, Firmware, Microcodeand Single Board Computer

198005655 DSP Reports Exceptions After Detection

198005700 DSP resets for error.

4. Reset the board.


Alarm Impact All the services performed on this DSP is interrupted, and thoseservices will be re-created on other normal DSP’s. The long periodabsence of this DSP might cause decline to the performance of thesystem.

198026116 CLKG PP2S OutputClock Lost




Alarm

Alarm Level Major

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm Hardware is faulty.


1. If the alarm is declared by master board rather than slaveboard, perform master/slave switching.

2. Replace the board where the alarm is declared.

Alarm Impact 1. If this alarm occurs to master clock board, the system will failto get clock, leading to processing failure of clock-related boardsand interruption of board services. Relevant boards include IMAprotocol processing board and the interface board capable of HWprocessing.

2. If this alarm occurs to slave board, service will not be affected.

198026117 PP2S clock referencelost




Alarm

Alarm Level Major

Disaster Alarm Yes


Chapter 2 Alarm

FrequentlyReported

No



1. If the board where the alarm is declared is ICM, please replacethe board.

2. If the board where the alarm is declared is CLKG: 1)Check theconnection between CLKG and GCM. 2)Replace the CLKG. 3)Re-place the GCM.

Alarm Impact System could not get the needed clock, which will cause processingabnormity related to the clock.

198026118 16CHIP clock referencelost




Alarm

Alarm Level Major

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm Replace the board that is alarming.


Replace the board.

Alarm Impact The system can not get wanted clock, therefore all clock-relatedprocesses are abnormal.

198026127 Clock reference sourcelost (Level 3 alarm)




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm Input clock reference is in unavailable status for no more than 10minutes. Probable causes include:

1. Clock reference input is abnormal.



2. The configured clock reference does not exist.


1. Re-connect the input clock reference.

2. For the clock reference not in use, delete the correspond-ing "Circuitry Clock Reference" configuration on NMS configurationmanagement interface (board property).

Alarm Impact When all configured clock reference sources are lost, the clockboard comes to free running or hold-over state. Accuracy of out-put clock is determined by the crystal oscillator of clock board. Noimpact on service.





Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm Input clock reference is in unavailable status for more than 10minutes and less than 24 hours. Probable causes include:






Alarm Impact When all configured clock reference sources are lost, the clockboard comes to free running or hold-over state. Accuracy of out-put clock is determined by the crystal oscillator of clock board. Theclock loss leads to synchronization failure between system clockand clock reference source. Service interruption might occur. Thesystem will not be affected if the following two events happen to-gether.

1. Input clock reference source is lost.

2. The phase-locked loop locks other clock reference source.




Chapter 2 Alarm



Alarm


Disaster Alarm No

FrequentlyReported

No

Cause of Alarm Input clock reference is in unavailable status for more than 24hours. Probable causes include:






Alarm Impact When all configured clock reference sources are lost, the clockboard comes to free running or hold-over state. Accuracy of out-put clock is determined by the crystal oscillator of clock board. Theclock loss leads to synchronization failure between system clockand clock reference source. Service interruption will occur. Thesystem will not be affected if the following two events happen to-gether.

1. Input clock reference source is lost.

2. The phase-locked loop locks other clock reference source.

198026131 CLKG board PLLout-of-lock




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No




2. Replace board.

Alarm Impact 1. If this alarm occurs to master board, system clock synchroniza-tion will fail and service interruption will occur.




198026133 Output clock lost




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No




2. Replace board.

Alarm Impact 1. If this alarm occurs to master board, system clock synchroniza-tion will fail and service interruption will occur.


198005632 Usage rate of board harddisk above threshold




Alarm

Alarm Level Major

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm 1. Usage rate threshold configuration is improper.

2. The usage of hard disk is over high.


1. Open the Configuration Management windowMPX86 or MPX86/2alarm parameter Hard Disk Full, check the threshold value in theconfiguration of Hard Disk Usage Alarm level. Increase the thresh-old value if the setting is not larger enough.

2. Clear the disk and delete the unnecessary files or move the filesto other external storage devices.

Alarm Impact When hard disk usage is over threshold, there may be error forthe write-in operation of new data, or data loss. It has no impactto the service.


Chapter 2 Alarm

198005637 Error in Rear Board ThatMismatches With Front Board




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Incorrect rear board is used.

2. Rear board failure.


1. Check the front board type for the correct rear board type, anduse the correct rear board.

2. Replace the defective rear board with a new rear board.

Alarm Impact 1. When the rear board is used for the access of other NE, it wouldcause link interruption on the bottom layer, and service interrup-tion of the corresponding link.

2. When the rear board is used for the access of internal con-trol plane, it would cause communication error of internal controlplane, failure of the board in exchanging control plane message,and service interruption of the corresponding link.

3. The rear board of clock board is for clock synchronization, errorin this board would result in clock signal loss. The system serviceswould be interrupted when clock signal input is absent.

198005661 Physical link downbetween master/slave mediainteractive ports




Alarm

Alarm Level Warning

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm The network port or board is faulty.





2. Replace the other board, that is, the board rather than thefaulty board in active/standby configuration.

3. Replace the slot. Use the slot that supports GE channel betweenboards.

Alarm Impact The APS optical port data on the standby board cannot reach theactive board. When the active optical port is normal, the serviceis not affected. When the active optical port is faulty, APS fails toprotect optical port and thus all services carried by the optical portare interrupted.

198005662 IDE running overtime




Alarm

Alarm Level Warning

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm IDE is operated for longer time.


No handling is necessary.

Alarm Impact When hard disk work for long time without sleep, engine will be inhigh speed spin state for long, this will influence the life of disk,and data will lose when disk be abnormal. Disk of some modelwill lock the engine when it keep work for long time to protect thedisk. But this is out of the software controled, and may result indata lose when disk cannot be accessed transitorily.

198005667 E1 is looped back.




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. User has set loop back.

2. Transmission is looped back by provider.

3. Local board is faulty.


Chapter 2 Alarm

4. Remote board is faulty.

5. Loop back applied on DDF.


1. Disconnect the loopback E1.

2. Restart the board.


4. Replace the opposite board.

Alarm Impact Data can not be sent out because of the loopback E1.

198005671 Incorrect FE RoutingConnection




Alarm


Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. FE-C3/4 is used for FE routing port when RUIM1 rear board isused.

2. When CHUB is connected to UIM/GUIM, CHUB rear card(RCHUB1/RCHUB2) uses discrete ports (e.g. port1/port3) toconnect UIM rear card.

3. When UIM/GUIM is connected to UIM/GUIM CHUB, connectionsused 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 usedfor FE inter-connection.


Reconnect FE cables.

1. If RUIM1 rear board is used on BUSN shelf for FE routing con-nection, make sure to select FE-C1/2 port as routing port.

2. If GUIM on BGSN shelf is used, make sure to select FE1 and FE2ports as routing ports. Either double-shelf or multi-shelf cascadingconnection is acceptable.

3. If TRUNK mode is used, multiple FE ports form a TRUNK portand they are connected in cascading mode. In this case, makesure each end must use ports in pairs. If either local end or oppo-site end doesn't use FE ports in pairs, please reconnect FE cablesand make sure each end uses ports in pairs. Here is an exampleof connection method: i. When CHUB is connected to UIM/GUIM,the CHUB rear board (RCHUB1/RCHUB2) must use consecutiveports (e.g. port1/port2 pair, port3/port4 pair, port5/port6 pair,port7/port8 pair ) to connect the ports (also in pair) on UIM/GUIMrear board. ii. When UIM is connected to UIM/CHUB, the UIM rearboard must use ports in pairs. If RUIM1 is used, 2 FE-C1/2 portsmust be used for FE routing ports; if RUIM2/RUIM3 is used, use



FE1/FE2 pair, FE3/FE4 pair and FE5/FE6 pair for FE routing ports.iii. When GUIM is connected to UIM/GUIM/CHUB, the GUIM rearboard must use ports in pairs, FE1/FE2 pair must be used for FErouting ports.

Alarm Impact Control plane routing is disconnected; ports are switched over incycle; all services on this shelf are interrupted.

198005668 Self board hascross-linked E1




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm elf board has cross-linked E1.


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.

198005655 DSP Reports ExceptionsAfter Detection




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. The HPI port fails

2. Hardware failure.


1. Reset the board.

2. Replace DSP sub-card.


Chapter 2 Alarm


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

198005124 Capacity of intra-shelfcontrol plane TRUNK communicationis insufficient




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Connection failure.

2. Circuitry failure.

3. Board failure.

4. Rear board failure.


1. Check about whether TRUNK connection is used for Inter-shelfcontrol plane. If not used, no processing is needed.

2. Check for the connection number: 4 Fe’s, 2 GE’s are required.Complete the connection if there is any missing.

3. Check whether the connection is proper. The proper connectionshow as the following: For the FE port trunk, the UIM board onBUSN shelf does not support TRUNK connection, so this alarm doesnot exist. For other shelf, FE7, FE8, FE9 and FE10 set up TRUNKports. 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 portmust 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 GEport on the left board on the local shelf corresponds to the #2 GEport on the right board on the opposite shelf. The #1 GE port onthe right board on the local shelf corresponds to the #2 GE porton the left board on the opposite shelf, and the #2 GE port on theleft board on the local shelf corresponds to the #2 GE port on theright board on the opposite shelf.

4. Replace the cable or optics module.

5. Replace the rear board.

6. Replace the board connected.



Alarm Impact No system impact is resulted when TRUNK connection is not usedbetween Inter-Shelf Control Plane. When TRUNK connection isused, this means the network communication capability is notenough, and it may cause congestion to control plane. Duringhigh traffic period, this may cause large delay or even serviceinterruption at extreme condition..

198005125 Incorrect Connection ofGE Optical Transceiver Module




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm The fiber optics connection error.


Check the fiber optics for its proper cross connection, the detailedsteps are as below: Each connection kit includes 4 cables, 2 boards( one at each ends of the connection kit). Each board provides 2ports which are to connect to the 2 boards on the peer side. Thecross-connection method is as below: the #1 port on the left boardon the local shelf corresponds to the #1 port on the left board onthe opposite shelf, the #2 port on the left board on the local shelfcorresponds to the #1 port on the right board on the opposite shelf.The #1 port on the right board on the local shelf corresponds tothe #2 port on the left board on the opposite shelf, and the #2port on the left board on the local shelf corresponds to the #2 porton the right board on the opposite shelf

Alarm Impact Cause interruption to all services performed on this shelf.

198025602 TDM switch abnormal




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Check for any clock alarms.

2. TDM Switch chip is faulty.


Chapter 2 Alarm

3. Wrong board in configured slot.


1. In NMS Configuration Management interface, view the configu-ration of IMA links. Do the values of HW and TS fields configuredfor IMA links conflict (for example, two A ends are configured withthe same B end). If yes, modify the configuration.

2. Replace the faulty board.

Alarm Impact The link with abnormal connection is interrupted. Accordingly, ser-vices are affected.

198029952 802.3ah link fault




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm Link Fault: The physical layer has determined a fault that occurredin the receive direction of the local DTE.

Dying Gasp: An unrecoverable local failure condition has occurred.

Critical Event: An unspecified critical event has occurred.


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'treceive PDU.

2. If the 802.3ah is enable, if the port is optical, check the alarmof Link Fault is or not alive, if the alarm is alive, the port can'treceive the PDU

3. Or not, change the good network cable.

4. If the alarm is alive, change the peer board.

Alarm Impact Link Fault:

The port can't receive data, the operations will interrupt.

Dying Gasp:

The port can't receive data, the operations will interrupt.



Critical Event:

The 802.3ah is failed, can't detect the fault of link.

198005669 Synchronization statuscheck of FPGA failed




Alarm


Disaster Alarm No

FrequentlyReported

No

Cause of Alarm Synchronization status check of FPGA and SPI4/VSC872/VSC874failed. It's usually caused by hardware exceptions. For example,the clock chip works abnormally.


Replace the board.

Alarm Impact If synchronization status check of FPGA fail, Media can not receiveor send data normally. And the board will reset for the exceptionof the media check frame.

198005893 Memory check failed




Alarm


Disaster Alarm No

FrequentlyReported

No

Cause of Alarm Memory check failed.


1. Make records of the alarm information.

2. Replace the board or subcard.

Alarm Impact The operation related to the memory maybe failed.


Chapter 2 Alarm

198005403 Board SRAM self-checkfails




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm Hardware fault of board.


Replace the board, and check whether this alarm disappears.

Alarm Impact Board operation might be abnormal.

198005404 Board OCXO oven fault




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm Hardware fault of board.


Replace the board, and check whether this alarm disappears.

Alarm Impact Board operation might be abnormal.

198005405 Clock board phase-lockloop work mode abnormal




Alarm

Alarm Level Major

Disaster Alarm No



FrequentlyReported

No

Cause of Alarm 1. There is no available reference source.

2. The clock distribution line is incorrect or there exists self loop.

3. The secondary clock locks the tertiary clock.


1. Check if the corresponding clock reference is correctly inputted.


Alarm Impact The designated reference clock cannot be phase-locked.

Communication Alarm198000256 Ethernet physical linkbroken

Alarm Type Communication Alarm



Alarm

Alarm Level Minor

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm 1. No network cable is connected to port OMC2 on rear board.

2. A network cable is disconnected or in poor contact.

3. The network port on the board is faulty.


1. Check whether a network cable is connected to port OMC2.

2. Unplug and plug the network cable from/to port OMC2 on OMPboard.

3. Check whether OMC2 network cable works normally. If not,replace the cable.

Alarm Impact Master/slave changeover will occur if OMP (ROMB board) works inmaster/slave mode.

If the master/slave changeover operation is successful, the systemwill not be affected.

If master/slave changeover operation is unsuccessful, OMP boardcan not obtain version package from NMS. In this case, the boardfails to be powered on, UE can not be accessed, and the existingservices are interrupted.


Chapter 2 Alarm

198083021 CCP transmission linkfault




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm Transmission fault to Node B


Check the Node B corresponding to the faulty CCP to see if thereis any of the following transmission-related alarms. If yes, followthe corresponding suggestions to handle it.

1. IP mode

Check the Alarm Management interface according to the associa-tion ID to see if there is any of the following association-relatedalarms. If yes, follow the corresponding suggestions to handle it.

198066018 Association link congested


2. ATM mode

1) Bottom layer transmission fault






2) Unavailable PVC link


198018944 PVC Fault

Alarm Impact The CCP transmission link is unavailable, so it cannot be used dur-ing radio link establishment. If the Node B still selects this CCP,RNC messages cannot be sent to the Node B and the current ser-vices will be interrupted.







Alarm


Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm The alarm occurs when the receiving optical power is below opticalreceiver sensitivity. Generally speaking, normal receiving opticalpower 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 isfaulty.

Receiving optical fiber is faulty or disconnected.


Receiving optical module is faulty.

2. The transmitting optical fiber of opposite SDH equipment isfaulty.

Transmitting optical fiber is faulty or disconnected.


3. The optical transmission line of SDH equipment is faulty.

Tail fiber and flange between fiber distribution frame and the equip-ment at local end are faulty or disconnected.

The related connector is in poor contact.

4. The receiving optical power at local end is excessively low.

Optical power attenuation on the fiber transmission line at receiv-ing end is too much.

Opposite-end transmitting optical power is too low.

5. Operation of LOS insertion is performed at opposite end.

Manual operation of LOS insertion is performed in diagnostic test,and optical module is shutdown by force.

6. Optical fiber and optical module is incompatible.

The fiber transmission rate of STM signals and the optical modulewavelength are incompatible.


1. Use meter measurement or loop test to judge whether thealarm is caused by local end or opposite end.

Meter Measurement

Use a SDH test meter or optical power meter to test whether thereceiving optical signals at local end are normal. If normal, faultmight lie in local equipment. If abnormal, fault lies in opposite endor on transmission side. Inform the opposite end or transmissionside to troubleshoot.

Loop Test

Perform fiber self-loop at local SDH equipment. If the alarm per-sists, fault might lie in local equipment. If the alarm disappears,inform the opposite end to troubleshoot.


Chapter 2 Alarm

2. Replace optical module.

3. Replace optical fiber.

4. Replace board.

Alarm Impact SDH/SONET fails to work normally, leading to UE access failure onSDH/SONET and interruption of ongoing services.

198083036 DSAR Alarm




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. User plane resource initialization failure.

2. CCH setup failure at Node B side.

3. CCH configuration is deleted by OMCR.

4. The Bearer type of common transport channel is modified byOMCR.


View alarm details on the NMS Alarm Management interface tocheck the Alarm Reason, which can help you easily find the corre-sponding handling suggestions. The handling suggestions for eachalarm are as follows:

1.Alarm Reason: User plane resource initialization failure.

1) Click NE Information Configuration on the NMS ConfigurationManagement interface and select the corresponding Node B. Selectthe Path Configuration tab to check if all parameters, including theforwarding bandwidth, are correctly configured.

2) Click Path Group Configuration on the NMS Configuration Man-agement interface to check if all parameters are correctly config-ured.

2. Alarm Reason: CCH setup failure at Node B side. Click BaseStation Ground Resource Management on the NMS ConfigurationManagement interface and select IP and Route Management tocheck the IP parameters. Make sure that at least one "COS" isselected.

3. Alarm Reason: CCH configuration is deleted by OMCR. Thisalarm will be processed automatically by the system. The RNCwill initiate the process of common channel deletion. No manualhandling is required.

4. Others. The system will automatically reestablish the commonchannel. 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/PSservices initiated by the UE will fail.

2. If the S-CCPCH that carries PCH is unavailable, the paging func-tion of the system cannot be used and the CS/PS services initiatedby the CN will fail.

3. If the PRACH that carries RACH is unavailable, the UE cannotaccess this cell.

198083038 Transport Path groupOccupied Bandwidth Overload




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm Available bandwidth of transport path group is less than occupiedbandwidth. Probable causes for the alarm include:

1.E1 link is broken.

2.Transmission quality of the transmission line is poor.

3.Intermediate equipment is faulty.


1.Check the E1 link.

2.Check the transmission quality of intermediate equipment.

Alarm Impact The available bandwidth to destination is less than occupied band-width.So service rate on this path group will be degraded.

198083039 IP channel of Iubinterface is faulty




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. IP channel is down.


Chapter 2 Alarm

2. Packet loss rate exceed 25%.


Check the transmission quality of intermediate equipment.

Alarm Impact Service and OMCB will choose other IP channel to transfer data.

198083040 TCP connect on IuBCinterface is interrupted




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Interface board (GIPI) of local equipment is faulty.

2. Intermediate equipment or opposite equipments faulty.

3. The network cable connection is loose or disconnected.


1. Check the interface board(GIPI) for the Related Alarms. Per-form the recommended solution to process the possible alarms.

Related Alarms: 198066070 Board Offline or the CPU is in longperiod reset status

2. Telnet to the interface board. Set a destination IP and ping it.In the case of direct connection, ping the direct connect interfaceboard address. In the case of not direct connection, ping the inter-mediate equipment. If response timeout, contact the equipmentprovider for solution.

3 .Check the physical connection on IuBC interface. If the connec-tion is loose or broken, unplug and plug the cable or replace thecable. If port indicator is on, the physical link must be normal.

Alarm Impact The IuBC Broadcast is disabled.

198022784 BFD Session Interrupted




Alarm

Alarm Level Minor

Disaster Alarm No



FrequentlyReported

No

Cause of Alarm 1. The network cable connection on relevant equipment (includinglocal/ intermediate/opposite equipment) is loose or disconnected.

2. Intermediate equipment is faulty.

3. Opposite equipment is faulty.

4. Local equipment is faulty.

5. Configuration related to the BFD session is incorrect.


On NMS fault management interface, view alarm Details where in-formation of source address and destination address of the BFDsession is given. The source address is the address of local equip-ment. The destination address is the address of BFD session ter-minal equipment.

1. Check the operation status of line card at local end. If the linecard resets repeatedly, replace board. Then power-on the board.

2. Check the physical connection at the BFD session-related porton local line card. If the connection is loose or broken, unplugand plug the cable or replace the cable. If port indicator is on, thephysical link must be normal.

3. Set a destination IP. Ping intermediate equipment and oppositeequipment in turn.

i. Telnet to the interface board. Test if the link is normal via ping. Ifthe destination address is 2.2.2.10, issue the following commandin telnet interface. brs_ping_b "2.2.2.10"

ii. Wait for 5 seconds and issue the following command.BrsShowLog "ICMP" a. If "PING=== destine 2.2.2.10 timeout,Response timeout must occur" appears on the interface, responsetimeout must occur. b. If “ping_receive:Reply from 2.2.2.10:bytes=60 time<1ms” appears, response must be normal, indicat-ing that the link is normal.

iii. In the case of response timeout, check if the configuration ofrelated route and address is correct. If not, perform reconfigura-tion and retest.

iv. In the case of response timeout despite correct route/addressconfiguration, certain link or intermediate equipment might befaulty. Check if disconnected network cable, loose connection, orabnormal equipment status exists on the faulty link along the BFDsession path. If yes, take necessary measures, including cablereplacement and replugging, equipment repair or replacement.

4. If packet reception and transmission are normal as confirmedby ping, check if the BFD session configuration at both ends iscorrect. On NMS configuration management interface,

i. Check BFD switch. Ensure that the switch is in "enable" status.

ii. Ensure that BFD session working modes at both sides are con-sistent.

iii. Ensure that BFD session in at least one equipment plays the“active” role.

iv. Ensure that BFD session exists at both ends, and configurationof source IP and destination IP matches.


Chapter 2 Alarm

v. Ensure that the hop mode (single hop/multihop) at both endsare consistent.

vi. Check configuration authentication information. Ensure thatthe number of authentication information configured at both endsare consistent.

5. Reset the board where the interface is located.

Alarm Impact All services on the path related to the BFD session will be switchedto the slave path. Service interruption will occur if slave path doesnot exist.

198066029 PPP link broken




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. The alarm occurs once in PPP port during board power-on, andrecovers 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.


On NMS fault management interface, view alarm Details, wherethe faulty PPP port ID is given.

1. Check cable connection at both ends. If the cable is discon-nected or connection is loose, unplug and plug the cable or replacethe cable.

2. Refer to user’s networking plan to see if E1 cable connection iscorrect.

3. On NMS configuration management interface (IPOverE1 con-figuration), check Interface E1 No. and time slot configuration.Ensure that the relevant configuration is consistent at both ends.

4. On NMS configuration management interface, check PPP con-figuration. Ensure that the relevant configuration at both sides isconsistent.

5. On NMS configuration management interface, check configura-tion of DT and EIPI connection. Ensure the connection continuityof PPP port at both ends.

Alarm Impact The PPP link is down. If merely one PPP link is available for theport or all available PPP links are down, the service on the portwill be down. Otherwise, only port bandwidth will be affected.The number of successful service access will decrease, but serviceinterruption will not occur.



198018944 PVC link is down.




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm Receive AIS/RDI cells from far end. If CC function is activated, itmay be caused by a timeout that missing CC cells and user cellsfrom far end.


1. On NMS fault management interface, view alarm Details wherePVC ID is given. Locate the faulty port according to the giveninformation.

For example, the PVC ID given in alarm Details is 1. On NMS con-figuration management interface (PVC configuration), try to locatethe 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 ofthe port.

If the faulty PVC port is carried by optical interface, ensure thatthe fiber connector and interface are in good contact, or replacethe fiber.

If the faulty PVC port is carried by IMA port, check if the followingalarms occur to the corresponding IMA group/link. If yes, refer tothe corresponding alarm handling suggestion.

Related alarms:

19207 Near end IMA group configuration failure

19213 LIF alarm of near end receiving link

19214 LODS alarm of near end receiving link

19215 RDI alarm of near end receiving link

19221 Remote receiving link ID mismatched

3. Check if the CC had been activated If it is, check the stepsfollowed.

4. Check if the equipment power-on at opposite end is successful.If no, refer to the maintenance manual of opposite equipment fortroubleshooting.

5. Check if the PVC status at opposite end is successful. If no,refer to the maintenance manual of opposite equipment for trou-bleshooting.

6. Deactivate CC test at local end, or activate CC test at oppositeend.

For IMAB/APBE board:


Chapter 2 Alarm

To deactivate CC test at local end, initiate "PVC CC test" on NMStest management interface. When configuring test parameters,select "0: Deactivate CC" for activation type, select "1: B-A" fortest type (A indicates local end and B indicates opposite end).

To activate CC test at opposite end, initiate "PVC CC test" on NMStest management interface. When configuring test parameters,select "1: Activate CC" for activation type, select "1: B-A" for testtype.

For APBE2/DTA board:

Modify PVC CCINFO parameter of configuration to active or deac-tivate CC test. CC test parameter is same to APBE/IMAB.

Alarm Impact PVC is in faulty status. All services on the PVC are interrupted.

198019213 LIF Alarm of Near-EndReceiving Link




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm Physical fault or connection error occurs to E1 link.


On NMS fault management interface, view alarm Details whereinformation of IMA chip ID, IMA group ID, IMA link ID, and E1index is given. Locate the faulty IMA link according to the giveninformation.

1. Refer to user’s networking plan to see if connection error exists.

2. On NMS fault management interface, check if E1-related alarmexists in the board. If yes, refer to the corresponding alarm han-dling suggestion. Related alarms:

198066045 Trunk error

198066046 Trunk abnormal

198001026 Cell delineation do not synchronization about cell onE1 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 ofsuccessful upper-layer service access will decrease. However, ser-vice interruption will not occur. If merely one link is available inthe IMA group, all services on the IMA group are interrupted.



198019214 LODS Alarm of Near-EndReceiving Link




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Operation of the input clock is abnormal.

2. Transmission quality of the link is poor.

3. Self-loop occurs to some cable connection in IMA group

4. Cable connection is incorrect in IMA group.

5. Hardware is faulty.


On NMS fault management interface, view alarm Details whereinformation of IMA chip ID, IMA group ID, IMA group link ID, andIMA link ID is given. Locate the faulty IMA link according to thegiven information.

1. Check the RUN indicator of clock board. If the indicator is greenand 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-relatedalarm occurs in UIM/GUIM. If yes, input clock source must be ab-normal. Refer to the corresponding alarm handling suggestion.Related alarms:

198001286 Loss of clock when input to board

198005646 Phase-lock loop unlock

3. On NMS fault management interface, check if E1-related alarmexists. If yes, refer to the corresponding alarm handling sugges-tion. Related alarms:



198001026 Cell delineation do not synchronization about cell onE1 link

4. Check if remote self-loop occurs to any physical connection inthe faulty IMA group. If yes, properly connect the cable accordingto the networking planning information.

5. Check cable connection according to the networking planninginformation. Ensure that the cabling is correct.

6. Reset board.

7. Replace board.


Chapter 2 Alarm


198019215 RDI alarm of far endreceiving link




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Remote IMA link is not in activated status.

2. Remote receiving direction is faulty.


On NMS fault management interface, view alarm Details where in-formation of IMA chip ID, IMA group ID, IMA link ID, and E1 indexis given. Locate the faulty IMA link according to the given infor-mation. Check the working status of the relevant remote receivinglink by referring to the opposite equipment operation guide. If re-mote receiving link is not in activated status, activate the link.


198019223 Ne Group is in fault state




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1.All IMA links of this IMA group are broken.

2.The peer-end IMA group is broken.




Fix the broken IMA links in the IMA group.

Alarm Impact The IMA Group does not work.

198066026 Association path broken




Alarm

Alarm Level Major

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm 1. Network communication is faulty.

2. Control plane path in NE is interrupted.

3. Opposite equipment is faulty.

4. The route to remote address is lost.


On NMS fault management interface, view alarm Details, whereinformation of association ID, local address, and remote addressis given.

1. On NMS configuration management interface (static route),query the route information of the remote address. Locate the outport according to the route information. Check if network cable ofthe out port is disconnected or loose. If yes, unplug and plug thecable or replace the cable.

2. On NMS configuration management interface (SCTP associationconfiguration), query the ID of the module where the association islocated. Check if the following alarm occurs in the relevant board.If yes, refer to the corresponding alarm handling suggestion. Re-lated alarm:

198066003 Control plane communication abnormal between boardand its home module

3. On NMS configuration management interface (static route),query if the route to the remote address of the association is con-figured. If not, add the configuration.

4. Check the intermediate equipment on association path. If theroutes to local address and remote address of the association arenot configured, add the configuration according to equipment op-eration manual.

5. Check at opposite end if the route to the local address of theassociation is configured. If not, add the configuration.

6. Check if the opposite equipment is faulty. If yes, troubleshootat opposite end.

Alarm Impact If multiple paths are available for the association and there existsnormal path, relevant services will not be affected. If merely one


Chapter 2 Alarm

path is available for the association, all services on the associationis down.

198005666 The number of the errorpackets from MAC port exceeds thethreshold




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. The port cable is not properly connected.

2. The port cable is faulty.

2. The IC of external board port is faulty.

3. The corresponding board is faulty.


1. Reconnect the cable, ensure that the connection between thisport and the peer port is correct.

2. Replace the cable.


4. Contact the opposite engineers to check the opposite ports forpossible failure.

Alarm Impact The MAC port is unavailable or the flow is limited.





Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. The receiving cable of local trunk equipment is faulty. The cableis 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 equipmentare not properly connected.

4. Operation of LOS insertion is operated at opposite trunk equip-ment. Manual inset alarm operation is performed in diagnostic test


1. check whether the alarm is caused by local end or opposite endvia meter measurement or loop test. Meter Measurement Use atrunk test meter to test whether the trunk receiving signals at localend are normal. If yes, fault might lie in local equipment. If no,troubleshoot at opposite end. Loop test Perform trunk self-loop atlocal end. If the alarm persists, fault might lie in local equipment.If the alarm disappears, troubleshoot at opposite end.

2. Replace trunk cable.

3. Replace board.

Alarm Impact The trunk equipment fails to work normally. All services based onthe trunk are interrupted.





Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Trunk frame formats at local end and at opposite end are in-consistent.

2. The transmitting end of opposite trunk equipment is faulty.

3. Local trunk equipment is faulty.

4. Equipment grounding at both ends is bad.

5. Impedance mismatch occurs.


On NMS fault management interface, view alarm Details, whereError type is listed. Locate the specific handling suggestion ac-cording to the listed error type. The handling suggestions thatcorresponds to different error types are presented below.

1.Frame loss of trunk of E1; Multiple frame loss of trunk of E1;Alarm indication signal of trunk of E1.

i. On NMS configuration management interface (subunit configu-ration), Check whether frame type configuration at local end andat opposite end is consistent.

ii. On NMS configuration management interface (subunit configu-ration), Check whether impedance configuration is correct.

iii. Check whether the grounding at both ends is proper.


Chapter 2 Alarm

iv. If possible, check whether the alarm is caused by local end oropposite end via meter measurement, loop test, or board/cablereplacement

2.Far-end alarm indication received by trunk of E1. Check thealarm status at opposite end. Since the alarm origin is oppositeend, first troubleshoot at opposite end.

Alarm Impact All services based on the trunk are interrupted.

198066047 Abnormal status inSDH/SONET




Alarm


Disaster Alarm No

FrequentlyReported

No

Cause of Alarm On NMS fault management interface, view alarm Details whereError type information is given. Each error type corresponds toan alarm status Altogether there are twenty-two types of alarmstatus. Probable causes which correspond to different alarm statusare listed below.

1. Loss of frame

This alarm will occur when the A1A2 frame aligning signal in SDHregenerator section overhead fails to be received properly for aconsecutive 3 ms.

2. Regenerator section trace identifier mismatch

This alarm will occur when J0 byte in "access point identifier" at re-ceiving end and transmitting end is inconsistent with the expected(the previous agreement between two ends). The alarm might becaused by configuration inconsistency of J0 byte mode/value atboth ends.

3. Multiplex section alarm indication signal.

All "1"s will be sent in the STM signal (excluding regenerator sec-tion overhead) of local SDH equipment when alarms of optical sig-nal loss or optical path frame loss are declared in opposite SDHequipment.

4. Multiplex section remote defect indication.

This alarm is a remote alarm indication. It is an indication of analarm currently reported at opposite equipment. The alarm whichoriginates from remote multiplex section is in return indicated bythe local SDH equipment.

5. Multiplex section remote error indication.



When multiplex section B2 bit error occurs in opposite SDH equip-ment, the number of bit errors can be detected at local end. Thealarm will be reported if the number of bit errors reaches a certainlimit.

6. Signal failure.

This alarm will occur when bit error rate in the multiplex sectionof receiving signals exceeds 1E-3.

7. Signal deterioration.

This alarm will occur when bit error rate in the multiplex sectionof receiving signals exceeds 1E-6.

8. Administration unit loss of pointer.

This alarm will occur, when for consecutive 8 frames, SDH equip-ment fails to receive valid pointer value or the received pointervalue is NDF.

9. Administration unit alarm indication signal.

All "1"s will be sent in the administration unit (including pointer)of local SDH equipment when alarms of high order path pointerloss, high order path unequipped, high order path trace identifiermismatch, and high order path signal label mismatch are declaredin opposite SDH equipment.

10. High order path trace identifier mismatch.

This alarm will occur when J1 byte in "VC-4 path access point iden-tifier" at the receiving end and the transmitting end is inconsistentwith the expected (the previous agreement between two ends).The alarm might be caused by configuration inconsistency of J1byte mode/value at both ends.

11. High order path unequipped.

This alarm will occur when the "VC-4 path signal identifier" re-ceived by local SDH equipment is coded in all zero mode. Thefollowing two reasons might account for the alarm.

The path in local SDH equipment has not been equipped by oppo-site end.

The path configured at opposite end is 0.

12. High order path signal label mismatch.

This alarm will occur when the "VC-4 path signal identifier" re-ceived by local SDH equipment is different from the expected one.The alarm might be caused by configuration inconsistency of C2byte at both ends.

13. High order path remote defect indication.

This alarm is a remote alarm indication. It is an indication of analarm currently reported at opposite equipment. The alarm whichoriginates from remote high order path is in return indicated bythe local SDH equipment.

14. High order path remote error indication.

When B3 bit error of the high order path occurs in opposite SDHequipment, the number of bit errors can be detected at local end.The alarm will be reported if the number of bit errors reaches acertain limit.

15. Tributary unit loss of multiframe.


Chapter 2 Alarm

The H4 byte in VC-4 path overhead is used as tributary unit mul-tiframe indication. This alarm will occur when the following twoconditions are satisfied.

Local- SDH equipment fails to receive the correct multiframe indi-cation code.

Multiframe alignment fails for consecutive 8 frames

16. Tributary unit loss of pointer.

This alarm will occur, when for consecutive 8 frames, SDH equip-ment fails to receive valid pointer value or the received pointervalue is NDF.

17. Tributary unit alarm indication signal.

All "1"s will be sent in the tributary of local SDH equipment whenalarms of tributary unit pointer loss, tributary unit unequipped,tributary unit trace identifier mismatch, and tributary unit signallabel mismatch are declared in opposite SDH equipment.

18. Tributary unit remote defect indication.

This alarm is a remote alarm indication. It is an indication of analarm currently reported at opposite equipment. The alarm whichoriginates from the remote tributary is in return indicated by thelocal SDH equipment. The remote defects include tributary unitmultiframe loss, tributary unit pointer loss, tributary unit traceidentifier mismatch, and tributary unit unequipped, etc.

19. Tributary unit remote defect indication (VC-11).

This alarm is the same with Alarm 18, except in that it applies toVC-11 structure, where T1 is configured for the trunk.

20. Tributary unit trace identifier mismatch.

This alarm will occur when J2 byte in "TU-12 access point identifier"received by local SDH equipment is different from the expected(the previous agreement between two ends). The alarm might becaused by configuration inconsistency of J2 byte mode/value atboth ends.

21. Tributary unit unequipped.

This alarm will occur when the "VC-12 path signal identifier" re-ceived by local SDH equipment is coded in all zero mode. Thefollowing two reasons might account for the alarm.

The relevant tributary has not been equipped by opposite end.

The relevant tributary configured at opposite end is 0.

22. Tributary unit signal label identifier mismatch.

This alarm will occur when the "VC-12 path signal identifier" re-ceived by local SDH equipment is different from the expected code.The alarm might be caused by configuration inconsistency of V5byte (bit5-bit7) at both ends.


Alarm details are displayed in NMS Alarm Management interface,where fault type is given. You can easily find handling suggestionsaccording to the fault type.

The handling suggestions for each fault type are described as be-low:

1.Regenerator section trace identifier mismatch



In NMS Configuration Management interface, click SDH parameterconfiguration and select SDH Optical Channel Parameter to checkwhether the configuration of "J0 configuration mode" and "regen-erator section trace" at local end is consistent with those at oppo-site end. If no, modify the configuration to keep consistency.

2. Multiplex section remote defect indication

Check alarm status in the multiplex section of opposite end. Be-cause the alarm origin is from the opposite end, please solve theproblem at opposite end first.

3. Multiplex section remote error indication

Check alarm status in the multiplex section of opposite end. Be-cause the alarm origin is from opposite end (B2 bit error), pleasesolve the problem at opposite end first.

4. High order path trace identifier mismatch

In NMS Configuration Management interface, click SDH parameterconfiguration and select SDH Optical Channel Parameter to checkwhether the configuration of "J1 Mode 0" and "high order pathtrace 0" at local end is consistent with those at opposite end. Ifno, modify the configuration to keep consistency.

5. High order path unequipped

In NMS Configuration Management interface, click SDH parameterconfiguration and select SDH Optical Channel Parameter to checkthe configuration of optical channel payload type. If the configuredvalue is 0, modify the configuration.

6. High order path signal label mismatch

In NMS Configuration Management interface, click SDH parameterconfiguration and select SDH Optical Channel Parameter to checkthe configuration of optical channel payload type. Ensure that theparameter configuration at both sides is the same.

7. High order path remote defect indication

Check alarm status in the high order path of opposite end. Becausethe alarm origin is from opposite end, please solve the problem atopposite end first.

8. High order path remote error indication

Check alarm status in the high order path of opposite end. Becausethe alarm origin is from opposite end (B3 bit error), please solvethe problem at opposite end first.

9. Tributary unit remote defect indication/Tributary remote defectindication (VC-11)

Check alarm status in the corresponding tributary unit at oppositeend. Because the alarm origin is from opposite end, please solvethe problem at opposite end first.

10. Tributary unit trace identifier mismatch

In NMS Configuration Management interface, click SDH parameterconfiguration and select SDH Optical Channel Parameter to checkwhether the configuration of "J2 mode" and “low order path trace”at local end is consistent with those at opposite end. If no, modifyconfiguration to keep consistency.

11. Tributary unit unequipped


Chapter 2 Alarm

In NMS Configuration Management interface, click SDH parameterconfiguration and select SDH Optical Channel Parameter to checkthe configuration of tributary unit payload type. If the configuredvalue is 0, modify the configuration.

12. Tributary unit signal label identifier mismatch

In NMS Configuration Management interface, click SDH parameterconfiguration and select SDH Optical Channel Parameter to checkthe configuration of tributary unit payload type. Ensure that theparameter configuration at both sides is the same.

13. Others

i. Use measurement instrument or loopback test to judge whetherthe alarm is caused by local end or opposite end.

a. Measurement instrument

Use a SDH test instrument to test whether the received opticalsignals at local end are normal. If normal, it means opposite endhas a fault. Please solve the relevant problem.

b. Loop Test

Carry out a self-loop test at local SDH equipment. If the alarm stilloccurs, it means local end has a fault. If the alarm disappears, itmeans opposite end has a fault. Please solve the relevant problem.

ii. Replace the optical module.

iii. Replace the optical fiber.

iv. Replace the board.

Alarm Impact 1. If alarm occurs on optical path, all trunk signals and serviceson this path are interrupted.

2. If alarm occurs on tributary, all trunk signals on this path areinterrupted, and all services on this trunk are interrupted.

198066048 SDH/SONET ExcessiveError Code




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Attenuation of receiving signals of local SDH equipment is large.

2. The transmitting part of opposite SDH equipment is faulty.

3. Fiber connector is polluted or misconnected.

4. The receiving part of local SDH equipment is faulty.

5. Operation of bit error insertion is performed at opposite end.





Meter Measurement

Use a SDH test meter or optical power meter to test whether thereceiving optical signals at local end are normal. If normal, faultmight lie in local equipment. If abnormal, fault lies in opposite endor on transmission side. Inform the opposite end or transmissionside to troubleshoot.

Loop Test

Perform fiber self-loop at local SDH equipment. If the alarm per-sists, fault might lie in local equipment. If the alarm disappears,inform the opposite end to troubleshoot.

2. Replace optical module.

3. Replace optical fiber.

4. Replace board.

Alarm Impact SDH/SONET equipment can work. However, call loss or noise oc-curs to all voice services on this optical path, and bit error occurson the data service channel.

198001026 Loss of ATM CellSynchronization over E1 Link




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Cell Header HEC (Header Error Check) is damaged, leading tocell location failure in physical layer frame.

2. The alarm is caused by bottom layer fault. Cell HEC is handleddifferently at local end and opposite end.


1. Check if the following alarm occurs in the board. If yes, referto the corresponding alarm handling suggestion.

Related alarms:



2. On NMS configuration management interface, check ifSDH/SONET mode is configured for both ends. Ensure that theconfiguration at both ends is consistent.



Chapter 2 Alarm

Meter Measurement

Use a trunk test meter to test whether the trunk receiving signalsat local end are normal. If normal, fault might lie in local equip-ment. If abnormal, troubleshoot at opposite end.

Loop Test

Perform self-loop at local trunk. If the alarm persists, fault mightlie in local equipment. If the alarm disappears, inform the oppositeend to troubleshoot.


5. Replace board.

Alarm Impact Data reception on E1 link is abnormal. If merely one E1 link isavailable for the port, all services on the board will be down. Other-wise, port bandwidth will be affected, leading to decreased accessbandwidth. The number of successful upper-layer service accessrelated to the port will decrease, but service interruption will notoccur.

198066049 ATM link is down




Alarm


Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Bottom layer physical link is abnormal.

2. HEC handling at local end and opposite end is inconsistent.


1. Check if the following board alarm occurs. If yes, refer to cor-responding alarm handling suggestion.

Related alarms:



2. On NMS configuration management interface, check ifSDH/SONET mode configuration exists at both ends. Ensure thatthe configuration at both ends is consistent.


Meter Measurement

Use a trunk test meter to test whether the receiving trunk signalsat local end are normal. If normal, fault might lie in local equip-ment. If abnormal, troubleshoot at opposite end.

Loop Test



Perform self-loop at local trunk. If the alarm persists, fault mightlie in local equipment. If the alarm disappears, troubleshoot atopposite end.


5. Replace board.

Alarm Impact Communication at ATM port is down. All services based on thetrunk are interrupted.

198015617 Frames Received byFE/GE/ATM/MP/POS/E1 Port arefaulty.




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

Yes

Cause of Alarm 1. The network connected with FE/GE/ATM/MP/POS/E1 port is ab-normal.

2. The board is in abnormal status.

3. Board hardware is faulty. For example, the network processorsubcard is not tightly inserted.

4. Other board hardware faults.


1. Unplug and plug port fiber/network cable.

2. Replace port fiber/network cable.

3. Reset board.

4. Unplug and plug board.

5. Replace board.

Alarm Impact Datagram reception of the board is affected. The service on thisport might be unstable. Worst of all, all services on the boardmight be interrupted.

198015873 Faulty frames receivedby internal switching interface




Chapter 2 Alarm


Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. The PSN board in the same shelf is abnormal.

2. Network processor subcard of the board is not tightly inserted.

3. Board hardware is faulty. For example, the switching chip isfaulty.


1. Check if the following alarm exists in PSN board at the sameshelf. If yes, refer to the corresponding alarm handling suggestion.Related alarm:

198019456 All high-speed links between line card and packageswitching board are out of synchronism


3. Replace board.

Alarm Impact If the fault lies in PSN board, service of the entire RNC NE willbecome unstable. If the alarm persists, all services will be inter-rupted. If the fault lies in the board where the alarm is declared,only the services on this board are affected.

198005378 Board HW Error




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Clock is not synchronous.

2. Either the board or the slot has a hardware fault.


1. Check whether the board has one of the following alarms. Ifyes, please solve the problem according to corresponding handlingsuggestions. Related Alarms

198001286 Loss of input clock

198005646 Phase-locked Loop Unlocked

2. Check whether the clock board has one of the following alarms.If yes, please solve the problem according to corresponding han-dling suggestions. Related Alarms

198026133 Output clock lost






3. In Configuration Management interface, check whether APSprotection is configured when the SDTB/SDTB2 works in mas-ter/slave mode. How to check APS protection configuration: Inthe Configuration Management interface, click Rack, select theconcerned board (SDTB/SDTB2). Then right click it. A shortcutmenu 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 areinterrupted.

198005651 IPMAC conflict whenOSS detects control plane




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. The board is not plugged in place.

2. Backplane DIP switch configuration has been modified.



2. Check the backplane DIP switch at the shelf where the boardis located and the switch at the shelf where OMP is located. Ifthe switches at two shelves are inconsistent, reconfigure the DIPswitch to keep consistency. Reset the relevant boards after recon-figuration.

3. Reset board.

Alarm Impact IPMAC Conflict leads to communication fault in board control plane.For the board that has powered on, packet loss occurs and boardservices is unstable. Even worse, link interruption might occur andall services on the board might be interrupted. For the board thatis powering on, board resets repeatedly, and service access to theboard fails.


Chapter 2 Alarm

198066003 Control planecommunication is abnormal betweenboard and its home module




Alarm

Alarm Level Major

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm 1. The board is not in position.


3. The control plane communication is abnormal.

4. The board is reset.


1. Check if the board is in position. If not, insert the board.

2. Reset the board. Wait for the board to be powered on.


4. Replace the board slot.

5. Replace the UIM/GUIM board in the same shelf.

Alarm Impact The services carried by the board are interrupted.

198066004 Control planecommunication is abnormal betweenMP and OMP




Alarm

Alarm Level Major

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm 1. The board is not in position.


3. The control plane communication is abnormal.



4. The board is reset.


1. Check if the board is in position. If not, insert the board.

2. Reset the board. Wait for the board to be powered on.


4. Replace the board slot.

5. Replace the UIM/GUIM board in the same shelf.

Alarm Impact The board is blocked and the functions of the board are unavail-able. As a result, all services of the units under this module areunavailable.

198005382 Communication betweenpower board and OMP board isabnormal




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. The power board is not connected to the OMP or connectionfailure occurs.

2. The rack number configured for the rack in which this powerboard locates is not consistent with the rack number switch set forthe power board.


1. Reconnect the 485 cable between the power board and OMP.

2. Make sure the rack number configured for the rack in which thispower board locates is consistent with the rack number switch setfor the power board.

Alarm Impact Unable to monitor the power supply condition and the environmentcondition. It has no impact to the services.

198005396 Exceptionalcommunication on UIM boardor back plane




Chapter 2 Alarm


Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. The internal port chip on the board has a physical fault.

2. The switch IC on UIM/GUIM provides a port, which is connectedto the board. This port has a fault.

3. Backplane wiring failure, which connects the slot to UIM.

4. A CUP on L1 switching board, the board, or UIM board of thesame shelf, is overloaded.

5. Service exceeds the processing capability of the board.


1. In Alarm Management interface, check whether there is aninternal media plane port abnormal alarm. If yes, please solve theproblem according to corresponding handling suggestion.

Related Alarm: 198005376 Internal media plane port abnormal

2. In Alarm Management interface, check the CPU rate, which islocated on L1 switching board, the board or UIM board of the shelf.Is there a CPU overloaded alarm? If yes, please solve the problemaccording to the corresponding handling suggestions.

Related Alarm: 198002560 Board CPU Overloaded

3. In the Alarm Management interface, check whether there is analarm, indicating abnormal link at inter-shelf media plane. If yes,please solve the problem according to the corresponding handlingsuggestions.

Related Alarm: 198005121 Inter-shelf media plane link fault


5. Change a slot to insert the board.

6. Replace the UIM of the same shelf.

Alarm Impact If the internal media plane stream can not be processed, packetsmay be lost. In this case, services provided by this board becomeunstable.

If it is port fault or connector fault, the internal media plane iscompletely broken. In this case, services borne on this board areinterrupted.

If either CPU or traffic is overloaded, services carried on the boardwill be delayed. In serious situation, services may be interrupted.

198005397 Communication ofRAWMACIP channel is abnormal






Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1The CPU usage of the UIM/GUIM in the shelf is too high.

2The service media stream exceeds the threshold.

3The hardware is faulty.


1. On NMS fault management interface, check if the UIM/GUIMboard in the same shelf has related alarms. If yes, follow thesuggestions 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 signalingprocessing board is abnormal. This causes the degradation of QoS.In most serious case, the service is totally interrupted.

198005401 Test packet checkabnormal




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. The board is faulty.

2. The line from UIM/GUIM to GLI is abnormal.


On NMS fault management interface, view the alarm details, whichgive the test alarm type. You can quickly locate the handlingmethod according to the test alarm type. The handling sugges-tion for each test alarm type is as follows:

1.Test alarm type: ATM test abnormal The link between C5 andAPC of ATM processing board is abnormal. In this case, replacethe board.

2.Test alarm type: Level 1 switch test abnormal The level 1 mediaplane switching from UIM/GUIM to GLI is abnormal. This is alwayscaused by the abnormal link between UIM/GUIM and GLI. In this


Chapter 2 Alarm

case, reconnect the cables between UIM/GUIM and GLI or replacethe cables. If optical fibers are used, replace the optical module.

Alarm Impact This alarm affects the service transfer on media plane. In alarmdetails, the detected alarm type gives the error type of the alarm.The alarm impact varies depending on the alarm type.

1.If the test alarm type is "ATM test abnormal", the ATM boardcannot normally provide ATM services. Thus, the service carriedby the board is interrupted.

2.If the test alarm type is "Level 1 switch test abnormal", it indi-cates that media plane communication is abnormal. This causesthe service carried by this shelf to be interrupted.

198005121 Inter-shelf media planelinks abnormal




Alarm

Alarm Level Major

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm 1. The fiber connection is error between shelves, or the fiber isnot physically plugged.

2. The background configuration of the board is inconsistent withits foreground physical connection.

3. The transceiver of the board link detection packet is excep-tional.


1. In the NMS Configuration Management interface, select UnitConnection Relation, then compare the configuration with actualphysical connection. If it is different, adjust connection cables ac-cording to the configuration.

2. Check the connection of optical fiber and make sure it is in crossconnection. Is there any relevant alarm? If yes, please solve theproblem according to recommended handling suggestions.

Relevant Alarm: 198005125 GE optical transceiver module iswrongly connected to left/right board slots at opposite end.

3. Replace the optical fiber or the optical transceiver module sothat the SD indicator for the corresponding port is on.

4. Replace the local board.


Alarm Impact The inter-shelf service bandwidth is reduced. The inter-shelf ser-vices may be interrupted if no backup is configured.



198005122 Loss of Active/standbycommunication link.




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. The board is configured to be in active/standby mode, but theopposite board is not in position.

2. Hardware Problem.


1. Make sure the board is configured in active/standby mode, andboth active/standby boards are in position.

2. Check whether the opposite board has the following alarm. Ifyes, please solve the problem according to recommended handlingsuggestions.

Description: 198005379 Board offline or CPU in reset status for along period


4. Change the slots of the active board and the slave board.

Alarm Impact The active board can not communicate with the standby board.As a result, active/standby changeover operation fails. There isno impact on services.

198066060 FE Link Error Alarm




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. In a pair of FE ports, one has normal link but the other has linkerror.

2. The hardware is faulty.


1. Check if only one cable is used to connect the port pair of therear board to the peer-end FE port. Ensure that both cables areconnected to the peer end.


Chapter 2 Alarm

2. Reconnect the cables or replace the cables.

3. Replace the rear board.


Alarm Impact Since one FE port in the control plane link can work normally, theservice is not affected. If this port is also faulty, the service willbe interrupted because the service cannot be switched over to theother port.

198005128 Duplicate rack and shelf




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm Shelf connect to the system with duplicate physical ID


1.Check whether two shelf with same physical ID exists. Modifythe switch of one of the two shelfs and reset the shelf and boardif 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 connectionexists.

Alarm Impact Boards in the shelf which power-on later power-on failure.

198066005 SCCP subsystemunavailable




Alarm

Alarm Level Minor

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm 1. From the perspective of A, remote signaling point subsystem isout of service.

2. From the perspective of A, remote signaling point is inaccessi-ble.



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

4. Local subsystem (for B) is blocked at B end.

5. From the perspective of A, SCCP user is unconfigured in remoteMTP3 or M3UA user configuration.


1. Check whether there exists office (the office that correspondsto the subsystem) inaccessible alarm. If yes, refer to the corre-sponding alarm handling suggestion. Related alarms:

198066010 MTP3 office inaccessible

198066014 M3UA office inaccessible

2. Unblock the subsystem in dynamic data management.

3. On NMS configuration management interface, check the config-uration of signaling point code (for A) at A end. See if SCCP useris 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 endmust be out of service. Locate the cause for the abnormal status.

5. Check whether the signaling point subsystem (for B) is config-ured at B end. If no, add the configuration at B end.

Alarm Impact Signaling data cannot be sent to and received from the relevantsubsystem. Access of new service under the corresponding officefails, and release of the ongoing service occurs.

198066007 Broadband link overload




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1.There are too many messages from upper layer service.

2.The number of links is insufficient.

3.Link load is uneven.


1. Check the counter of "Peak Traffic of Signalling Link" in MTP3Bsignaling link performance statistics. If the load (nearly) reached6000 during alarm occurrence, upper layer traffic must be heavy.Add links to share load.

2. On NMS configuration management interface, check the signal-ing link configuration of NE. Add or delete links to ensure that thenumber of links in a link set is two to the power of N. If there aretwo link sets in the current route, ensure that two link sets havethe same number of links.


Chapter 2 Alarm

Alarm Impact Link overload leads to upper layer service message loss. Call losswill occur, and access success rate of PS service will fall.

198066010 RNC unable to connectto MTP3 office




Alarm

Alarm Level Major

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm 1. No service link exists in the office route.

2. TFP is received.


1. Check whether there is an unavailable link alarm. If yes, pleasesolve the problem according to corresponding handling sugges-tions. Related alarm: 198066011 MTP3 link unavailable.

2. Check whether the configuration of office and link at oppositeend is correct.

Alarm Impact UE fails to receive/transmit messages from/to the relevant office.New services can not be accessed to this office, and existing ser-vices are interrupted abnormally.

198066011 MTP3 link unavailable




Alarm

Alarm Level Major

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm 1. Physical link at bottom layer is broken or link quality is poor.

2. Link test fails.

3. This link is deactivated in dynamic data management.

4. The opposite end has released this link.

5. SMP or SPB/SPB2/APBE/APBE2 board resets.




1. IN NMS Configuration Management interface, click SignallingLink Configuration to check PVC configuration. Make sure that theconfiguration of CVPI and CVCI should be the same at both ends.

2. In Dynamic Data Management, check link status. If it is inter-rupted and connected now and then, it means the link unavailabil-ity is caused by MTP3 link test failure.

1) In NMS Configuration Management interface, check the con-figuration of signaling point code at both ends. Ensure that theconfiguration is consistent at both ends.

2) In NMS Configuration Management interface, check the configu-ration of signaling link at both ends. Ensure that the configurationof SLC (Signaling Link Code) is consistent at both ends.

3. Re-activate the link in Dynamic Data Management.

4. Check board status. If it is abnormal, reset or replace theboard.

5. The opposite end has released the relevant link. Ask the oppo-site end to deal with the alarm as link unavailable.

Alarm Impact If several MTP3 links are available for the office, services will notbe affected. In the case of heavy traffic, link congestion may occur,leading to loss of packets/calls and decreased PS call access rate.

If merely one link is available to the destination signaling point,the office may become inaccessible. UE fails to receive/transmitmessages from/to the relevant office. New services can not beaccessed to this office, and existing services are interrupted ab-normally.

198066014 RNC unable to connectto M3UA office




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Association link is broken or application server (AS) is not inserving status.

2. M3UA office is inaccessible because the remote office gives aDUNS (destination signaling point unavailable) report.


1. Check whether there is an association link broken alarm. Ifyes, please solve the problem according to corresponding handlingsuggestions.

Related alarm: 198066019 Association link broken


Chapter 2 Alarm

2. In NMS Configuration Management interface, view AS StaticInformation to check whether a routing context exists. If yes,view the relevant configuration such as routing context ID, AS IDand AS service mode.

The correct configuration is described below.

i. The routing context ID and AS service mode must be the sameat both ends.

ii. AS ID must meet the following requirements: if ASP is config-ured for local end, SGP should be configured for opposite end; ifIPSP client is configured for local end, IPSP server should be con-figured for opposite end.

3. Re-activate the ASP in Dynamic Data Management.

4. Check whether the configuration of relevant office is correct atopposite end.

Alarm Impact UE fails to receive/transmit messages from/to the relevant office.New services can not be accessed to this office, and existing ser-vices are interrupted abnormally.





Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. The association is released in dynamic data management.

2. Association configuration is modified at local end.

3. Association is released at opposite end.

4. Bottom layer link is faulty.


1. Establish the association in dynamic data management.

2. On NMS configuration management interface, check associa-tion configuration at local end and opposite end. Checking itemsinclude protocol type of SCTP association, SMP module No, localIP address, local port No., remote IP address, remote port No.,the number of in/out streams. If the configuration at both ends isinconsistent, modify configuration to keep consistency.

3. Ping the opposite board address to see if the network cable orother intermediate link is faulty. Replace the cable if ping fails.

4. Check if the association is released at opposite end. If yes,troubleshoot according to the corresponding cause.

Alarm Impact 1. If several association links are available to the destination office,service will not be affected. In the case of heavy traffic, conges-



tion of available association(s) might occur, leading to upper layercall loss or increasing PS call access failures.

2. If merely one association link is available to the destinationoffice, the office might become inaccessible. Reception and send-ing of messages from/to the relevant office fail. Access of newservices under this office fails, and abnormal release of ongoingservices occurs.

198029953 The Ethernet port stateis OAM loop back




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm The local port state is loop back because the peer port starts Eth-ernet OAM loop back request of 802.3ah.


Check if the peer port has started Ethernet OAM loop back test. Ifyes, stop it, if no, disable local port Ethernet OAM.

Alarm Impact The Ethernet link which is in loop back test can't bear service data.

198003841 The control planeretransfer ratio over the threshold




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm There are some badly-touched boards in system environment andthe retransfer-ratio of RUDP packets increases.


Make records of the alarm information and contact ZTE Corpora-tion.

Alarm Impact The master board will change when slave is exist.


Chapter 2 Alarm

198083045 Common Channel setupfailed Alarm




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Use plane resource initialization fails.

2. Common channel establishment fails on Node B side.

3. CCH transport bearer setup fail.

4. Common channel configuration is deleted in NMS.

5. Inner Procedure Fail.


Check the configuration according to the following steps:

1. Check whether DSP run normally.

2. Check whether IUB interface board run normally.

3. Check whether alarms of transport bearers fail exist or not.

4. On NMS configuration management interface (NE informationconfiguration), select the relevant Node B. Check the correctnessof parameter configuration on path configuration interface. "Peerservice IP address" must be configured in the same network seg-ment with Node B IP address.

5. On NMS configuration management interface (BS ground re-source management), view IP parameter configuration in IP androute management. Ensure that at least one “COS” is selected.

6. On NMS configuration management interface (NE informationconfiguration), select the relevant Node B. Check the correctnessof parameter configuration on path configuration interface. Checkif forwarding bandwidth is configured.

7.On NMS configuration management interface (path group con-figuration), view path group configuration. Check the correctnessof parameter.

8. Check whether Node B alarm exist.

9. Contact with ZTE Corporation.

Alarm Impact Common Channel is unavailable, which falls into the followingthree cases.

1. If the SCCPCH carrying FACH is unavailable, UE-initiated CS/PSservices will be down.

2. If the SCCPCH carrying PCH is unavailable, paging functionwill be unavailable in the system, leading to failure of UE-initiatedCS/PS services.



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

198066071 Link broken for boardfault




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm Board internal fault.


1. Note down detailed information.

1.1 Back up related local office configuration data and peer-endoffice configuration data.

1.2 Back up related local office and peer-end office history alarmsand notifications, as well as current alarms.

1.3 Contact ZTE Corporation and end the alarm handling proce-dure.

Alarm Impact This alarm may render some offices inaccessible, or may result inthe congestion of other links.

198066066 AAL2 Path locallyblocked




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm The Path is manually blocked from this AAL2 Node.


You can unblock the Path which is generated manually from theoperating interface.

Alarm Impact No AAL2 connection can be established on the blocked path.


Chapter 2 Alarm

198066067 AAL2 Path remotelyblocked




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm The adjacent AAL2 node initiates blocking process and then thepath of this node is remotely blocked when receiving the blockingmessage from the adjacent node.


You can unblock the Path which is generated by adjacent nodefrom the operating interface of the adjacent node.


198066068 AAL2 Path blocked bybroken PVC




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm The Path is blocked because of the broken PVC.


The path can be available when PVC becomes available.




Processing Alarm198083020 RNC system resourceslimits reached, no new UE's canattach to the network

Alarm Type Processing Alarm



Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. High number of users trying to access the network.

2. Total number of tokens exhausted.


It is recommended to expand the capacity of the system.

Alarm Impact The system will reject new services to ensure the quality of theexisting services.

198083024 GPS receiver on ICM isabnormal




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. GPS subcard is not tightly inserted.

2. Hardware of GPS subcard is faulty.


1. Unplug and plug GPS subcard.

2. Replace GPS subcard.

Alarm Impact GPS subcard mainly provides positioning function for RNC NE. Thesubcard fault leads to handset positioning failure. Service is notaffected.


Chapter 2 Alarm

198019207 Near-End IMA GroupConfiguration Failure




Alarm


Disaster Alarm No

FrequentlyReported

No

Cause of Alarm IMA group configuration at local end and at opposite end is incon-sistent.


On NMS fault management interface, view alarm Details whereinformation of the faulty IMA group is given.

On NMS configuration management interface (IMA group configu-ration), locate the corresponding IMA group according to the infor-mation given in alarm Details. Compare the configuration of thefollowing parameters at both ends. If the configuration at bothends is inconsistent, modify configuration at either end to keepconsistency.

"Near-End OMA Label"

"Rx Frame Length (cells)"

"Tx Frame Length (cells)"

"Near-End Symmetry"

Alarm Impact All services on the IMA port are interrupted.

198015360 Microcode Is Abnormal




Alarm

Alarm Level Major

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm Network Processor hardware is faulty.


Wait for the board to reboot. If the alarm cannot be restored afterboard rebooting, unplug and then plug the board. If the alarm stillcannot be restored, replace the board.

Alarm Impact The board will reboot. If the alarm can be restored after boardrebooting, all board services during rebooting will be down, but



access of new services to the board after rebooting will be suc-cessful. If the alarm cannot be restored after board rebooting, allboard services during and after rebooting will be down.

198023040 The number of boardalarms exceeds the threshold




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm There are too many alarms for this board. The alarm pool is fullof board alarms.


Troubleshoot the current alarms in the system.

Alarm Impact Alarm information loss might occur. No impact on user service.

198066031 The number of OMPalarms exceeds the threshold




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm There are too many system alarms. The alarm pool is full of sys-tem alarms.


Delete the trivial alarms on NMS fault management interface.

Alarm Impact Alarm information loss might occur. No impact on user service.


Chapter 2 Alarm

198066032 NTP time exceedsthreshold




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Link between OMP and RPU is down.

2. NTP time and local time differs greatly.


1. On NMS fault management interface, check if the alarm relatedto RPU board exists. If yes, refer to the corresponding alarm han-dling suggestion. Related alarm:

198066004 Control plane communication abnormal between MPand OMP

2. Please change the value of the threshold to 0 or larger than 100if the value of the threshold is configured from 0 to 100.

3. Please try to recover the alarm by synchronizing the NTP timewith the board local time manually.

4. Check whether the interval between alarm time and the currentenvironmental time exceeds 8 alarm periods. Check the synchro-nization period and modify it if it is too long. Make sure the NTPserver is working properly.

Alarm Impact NTP time synchronization terminates, leading to interruption ofongoing services.

198066027 SNTP failure




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. SNTP server does not exist or server operation is abnormal.

2. The configured SNTP IP address in the database is inconsistentwith the real IP address.

3. Communication between RNC NE and SNTP server is down.



4. The time synchronization period configured in the databasemight be 0.


On NMS fault management interface, view alarm Details whereAlarm Reason is given. Locate the specific handling suggestionaccording to the given reason. The handling suggestions that cor-respond to different alarm reasons are described below.

1. Illegal DB configuration. On NMS configuration management in-terface (RNC ground resource management), check if SNTP serverIP address or SNTP synchronization period are incorrectly con-figured. If yes, which means SNTP server IP is configured as255.255.255.255 or SNTP synchronization period is 0, correct theconfiguration.

2. Failed to get time from SNTP server.

i. Ensure that SNTP server exists and server operation is normal.

ii. Ensure that the configured SNTP server IP address in the data-base and the real server IP are consistent.

Alarm Impact SNTP synchronization failure might lead to inconsistency betweensystem time and real time. For example, the real time is 1:00 am,but the displayed system time is 2:00 am. Since system clockfrequency is correct, service will not be affected.

198005387 Alarm Due to InconsistentMP Type




Alarm

Alarm Level Major

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm 1. The MP type is changed on NMS and the board is not restarted.

2. The active MP type on the local board is not consistent with thatconfigured on NMS.


1. For CMP and SMP, reset the board.

2. For OMP, set the start mode as "foreground start" on NMS andthen reset the board. Do as follows: On NMS software versionmanagement interface, select the menu for querying foreground(that is, RNC NE) board start mode. In the pop-up dialog box, setthe start mode to "foreground start".


Chapter 2 Alarm

Alarm Impact This alarm has no effect on the service.

198005388 Startup File Does NotExist




Alarm

Alarm Level Major

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm The startup configuration file is deleted.


1. Reset the active and standby OMPs.


Alarm Impact This alarm may cause OMP work abnormally, and the entire NEservices are affected.

198005398 Office ID is not setcorrectly with control shelf.




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm The office ID of a shelf where DIP switch locates is different fromthat of a shelf where OMP locates.


Set the office ID of the shelf where DIP switch locates to be thesame as that of OMP belonged shelf.

Alarm Impact The MAC address conflicts. The MAC and IP address verificationfails. All boards on the shelf can not be powered on. All servicescarried by the shelf are interrupted.



198066057 Database config isdifferent from file named bootcfg ini.




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm After the start information of OMP is modified, the active andstandby OMP boards are not restarted.


Restart the active and standby OMPs.

Alarm Impact The bootcfg ini. file contains the information on the office ID, dis-trict ID, OMP gateway, OMC MAC address, and OMC gateway mask.If the information is modified, the OMP cannot connect to OMC andexternal network normally.

198005649 Port working modedoesn't match with its setting.




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. The local device does not support this mode setting.

2. The opposite device does not support this mode setting.


Alarm details are displayed in NMS Alarm Management interface,where error mode type is given. You can easily find handling sug-gestions according to the error mode type.

The handling suggestions for each type are described as below.

1. Speed rate mode error

i. Determine which rate should be configured. Replace the existingboard with one that supports such rate mode.

ii. For force mode, configure the port with a suitable rate that issupported by bottom layer in actual working status.


Chapter 2 Alarm

Do as follows:

In NMS Configuration Management interface, first find subunit de-tails, then set a suitable rate that is supported by bottom layer inactual working status.

iii. For auto-adaptive mode, re-configure an expected rate so thatit is consistent with actual port rate.

Do as follows:

In NMS Configuration Management interface, first find subunit de-tails, then set the rate to be expected one.

2. Duplex mode error

i. Determine which mode should be configured. Replace the exist-ing board with one that supports such mode configured on RNC.

ii. For force mode, re-configure the port to be in duplex mode thatis supported by bottom layer in actual working status.

Do as follows:

In NMS Configuration Management interface, first find subunit de-tails, then set a suitable working mode that is supported by bottomlayer in actual working status.

iii. For Auto-adaptive mode, re-configure an expected duplexmode so that it is consistent with actual port duplex mode.

Do as follows:

In NMS Configuration Management interface, first find subunit de-tails, then set the working mode to be expected one.

3. GE port master/slave mode error

i. Make sure the master/slave mode is required. Replace the ex-isting board with the one that supports master and slave modeconfigured on RNC.

ii. For force mode, configure the port to be in master/slave modethat is supported by bottom layer in actual working status.

Do as follows:

In NMS Configuration Management interface, first find subunit de-tails, then set a suitable GE port master/slave mode that is sup-ported by bottom layer in actual working status.

iii. For Auto-adaptive mode, re-configure an expected mas-ter/slave mode and ensure that it is consistent with actual portmaster/slave mode.

Do as follows:

In NMS Configuration Management interface, first find subunit de-tails, then set the GE port master/slave mode to an expected one.

Alarm Impact 1. The port fails to work in configured mode, therefore, it can notbe used. All services via the port are interrupted.

2. For auto-adaptive mode, the bandwidth of external port be-comes insufficient. As a result, some services via the port areinterrupted.



198005123 DB Configuration Doesn'tFit for Device




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. The type of physical board is incorrectly configured.

2. A wrong board is inserted


1. The NMS configuration management interface gives the rackdiagram. Select the board and check if the board and subunitsettings of rack are correct. If the settings are incorrect, deletethe board and create a new one.

2. Check if a correct board is inserted in the slot on the rack. Ifnot, insert the correct one.

Alarm Impact The board fails to be normally powered on. The services carriedby the board are interrupted.

198005126 Incorrect FE RoutingConnection




Alarm


Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. FE-C3/4 is used for FE routing port when RUIM1 rear board isused.

2. When CHUB is connected to UIM/GUIM, CHUB rear card(RCHUB1/RCHUB2) uses discrete ports (e.g. port1/port3) toconnect UIM rear card.

3. When UIM/GUIM is connected to UIM/GUIM CHUB, connectionsused 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 usedfor FE inter-connection.


Chapter 2 Alarm


Reconnect the FE wire.

1. If the UIM board on the BUSN shelf uses RUIM1 backcard, makesure FE-C1/2 port is used for routing port.

2. If the GUIM board is on BGSN shelf, make sure FE1 and FE2ports are used as routing ports.

3. If TRUNK mode is used, numerous FE ports make up of a TRUNKport for cascaded connection. In this case, make sure the bothends are paired ports.

If the boards of the local board or the opposite board are not pairedport, please reconnect the FE wire and make sure the both endsare used paired ports.

Here is an example of connection method:

i. When CHUB is connected with UIM/GUIM, the connecting wireon RCHUB1/RCHUB2 of CHUB backcard must be used continuousports ( such as port1/port2 pair, port3/port4 pair, port5/port6 pair,port7/port8 pair ) to connect with the pairs on the UIM/GUIM back-card.

ii. When UIM is connected with UIM/GUIM/CHUB, the ports onUIM backcard must be used as paired. If RUIM1 backcard is used,then two FE-C1/2 ports must be used for FE routing ports; ifRUIM2/RUIM3 backcard is used, then use FE1/FE2 pair, FE3/FE4pair or FE5/FE6 pair for the FE routing ports.

iii. When GUIM is connected with UIM/GUIM/CHUB, the ports onGUIM backcard must be used as pair, i.e, FE1 and FE2 must beused for FE routing ports.

Alarm Impact Control plane routing is disconnected, ports are switched over incycle, all services on this shelf are interrupted.

198066006 Broadband linkcongestion




Alarm

Alarm Level Minor

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm 1. The configured signaling PVS bandwidth is insufficient.

2. Bottom-layer physical transmission quality is poor.


1. Check the counter of "Peak Traffic of Signaling Link" in MTP3Bsignaling link performance statistics. If the load (nearly) reached6000 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 existsphysical transmission alarm(s) /notification(s) that occurred si-multaneously with this alarm. If yes, refer to the correspondingalarm handling suggestion. Alarms/Notifications related to physi-cal transmission are listed below, with respect to access mode.

1) Fiber Access Mode



198066048 SDH/SONET:Excessive Error Code


2)E1 Access Mode

198005647 High Error Rate at E1 Bottom Layer



198000576 Trunk Slide

3. Check the performance statistics of SSCOP link. Check if therewas message retransmission of "Number of PDU Retransmitted"during alarm occurrence. If yes, packet loss must have occurredduring transmission. Since packet loss might occur at oppositeend, ask opposite end to cooperate in troubleshooting.

Alarm Impact Link congestion leads to transmission delay. If congestion is notserious, service will not be affected. Otherwise, packet loss or callloss might occur, and access success rate of PS service might fall.

198066013 MTP3 link congestion




Alarm

Alarm Level Major

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm 1. There are too many upper layer service messages.

2. Bottom layer link quality is poor, leading to frequent messageretransmission.


1. Add links to the office that is in service for the congested link.

2. Take the following measures to improve transmission quality ofphysical links. Replace bottom layer links. Ensure that connectorcontact and cable connection are normal.

Alarm Impact Link congestion leads to transmission delay. If congestion is notserious, service is not affected. Otherwise, packet loss or call lossmight occur, and access success rate of PS service might fall.


Chapter 2 Alarm





Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Transmission quality of bottom layer link is poor.

2. Upper layer traffic in sending service data is heavy.


1. Check network cable connection. Ensure that the network cableis tightly inserted.

2. Add association links to the office that is in service for thecongested association.

3. If intermediate equipment exists between local end and op-posite end, check the transmission quality of intermediate equip-ment.

Alarm Impact Transmission delay, or even packet loss will occur. If congestion isnot serious, service will not be affected. Otherwise, call loss mightoccur, and access success rate of PS service might fall.

198019712 loss of protectionswitching




Alarm


Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Fiber connection is wrong.

2. APS backup mode is configured differently between local endand opposite end.

3. APS protection mode is configured differently between local endand opposite end.

4. The opposite equipment is faulty.




1. Check fiber connection.

Check fiber connection at both ends. Ensure that the work opticalports at both ends are interconnected, and the protection opticalports at both ends are interconnected.

On NMS configuration management interface, locate the relevantboard in the rack. Right-Click the board and open board propertiespage. Click Optical port APS protection to view the "Work opticalport" and "Protection optical port" configured at local end.

2. Check APS backup mode configuration at both ends.

Check APS backup mode (11 or 1:1) at local end to ensure con-figuration consistency at both ends.

On NMS configuration management interface, locate the relevantboard in the rack. Right-Click the board and open board propertiespage. Click Optical port APS protection in the shortcut menu toview 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 bothends.

On NMS configuration management interface, locate the relevantboard in the rack. Right-Click the board and open board propertiespage. Click Optical port APS protection to view the "ProtectionDirect" (unidirectional or bidirectional).

4. Check whether APS is supported by the opposite equipment.Check whether APS configuration is correct and has taken effect.

Alarm Impact APS automatic protection switching function is paralyzed. Whenthe working optical port is abnormal, the protection optical portwill not work, leading to service interruption on this optical port.

198019713 loss of protectionswitching




Alarm


Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Fiber connection is wrong.

2. APS backup mode is configured differently between local endand opposite end.

3. APS protection mode is configured differently between local endand opposite end.


Chapter 2 Alarm


1. Check fiber connection.

Check fiber connection at both ends. Ensure that the work opticalports at both ends are interconnected, and the protection opticalports at both ends are interconnected.

On NMS configuration management interface, locate the relevantboard in the rack. Right-Click the board and open board propertiespage. Click Optical port APS protection to view the "Work opticalport" and "Protection optical port" configured at local end.

2. Check APS backup mode configuration at both ends.

Check APS backup mode (11 or 1:1) at local end to ensure con-figuration consistency at both ends.

On NMS configuration management interface, locate the relevantboard in the rack. Right-Click the board and open board propertiespage. Click Optical port APS protection to view the "ProtectionType" (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 bothends.

On NMS configuration management interface, locate the relevantboard in the rack. Right-Click the board and open board propertiespage. Click Optical port APS protection to view the "ProtectionDirect" (unidirectional or bidirectional).

Alarm Impact 1. When fiber connection is correct and the working optical portcan work normally, services won't be affected.

2. When the working optical port is faulty, APS automatic protec-tion switching function doesn't work, and services carried via thisoptical port will be interrupted due to lack of protection.

198019714 APS configuration alarm.




Alarm


Disaster Alarm No

FrequentlyReported

No

Cause of Alarm Optical interface are not configured for APS in 1:1 mode.


1. If board backup mode is configured as 1:1 or 1+1 and SDHoptical interface is needed, at least one set of APS protection needsto be configured.

To configure APS protection:

On NMS configuration management interface, locate the relevantboard in the rack. Right-Click the board and open board propertiespage. Click Optical port APS protection.



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

To configure board backup mode:

Delete the relevant board on NMS configuration management in-terface. Then recreate the board. Select board backup mode as"None" during board creation.

3. If board backup mode is configured as 1:1 and no SDH opticalinterface is required, modify the board backup mode into 1+1.

To configure board backup mode:

Delete the relevant board on NMS configuration management in-terface. Then recreate the board. Select board backup mode as"1+1" during board creation.

Alarm Impact The board can not enter into normal working status. All boardservices fail to be established.

Environment Alarm198025856 Rack temperature is high.

Alarm Type Environment Alarm



Alarm

Alarm Level Minor

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm 1. Fan is not working.

2. Fan has failed.

3. No fan connected.

4. Temperature sensor is faulty or setting is incorrect.


1. In NMS Configuration Management interface, click Power BoardAlarm Parameters to view the upper threshold of rack tempera-ture. If the configuration is unreasonable, please modify it. Therecommended value of upper threshold is 70 degrees in Celsius.

2. Check the thermometer in equipment room to see if the actualtemperature is too high. If yes, take necessary cooling measures.

3. Remove dust from air intake and outlet of the rack. Removeany obstacle nearby which may affect ventilation.

4. Ensure that the rack fan works normally.

Alarm Impact 1. If an unreasonable threshold is configured, services will not beaffected.


Chapter 2 Alarm

2. If the alarm is caused by high rack temperature, board maywork abnormally and board services may be interrupted.

198025857 Low temperature in Rack




Alarm

Alarm Level Minor

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm 1. temperature sensor is not working.

2. Treshold is incorrect.

3. External room heating control not working.


1. In NMS Configuration Management interface, click Power BoardAlarm Parameters to view the lower threshold of rack tempera-ture. If the configuration is unreasonable, please modify it. Therecommended value of lower threshold is 0 degrees Celsius.

2. Check the thermometer in equipment room to see if the actualtemperature is too low. If yes, take necessary warming measures.

3. Setting the sensor correctly.


2. If the alarm is caused by low rack temperature, board may workabnormally and board services may be interrupted.

198025858 House temperature ishigher than high threshold




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Threshold configuration is unreasonable.

2. Actual temperature in equipment room is too high.




1. On NMS configuration management interface (power boardalarm parameters), check the upper limit of equipment room tem-perature. Modify the threshold value if the previous configurationis unreasonable. The recommended high threshold value is 40.

2. Check the thermometer in equipment room to see if the actualtemperature is too high. If yes, take necessary cooling and venti-lation measures.

Alarm Impact 1. If the alarm is caused by unreasonable threshold configuration,service will not be affected.

2. If the alarm is caused by high room temperature, board opera-tion might be abnormal and board services might be interrupted.

198025859 House temperature islower than low threshold




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Threshold configuration is unreasonable.

2. Actual temperature in equipment room is too low.


1. On NMS configuration management interface (power boardalarm parameters), check the lower limit of equipment room tem-perature. Modify the threshold value if the previous configurationis unreasonable. The recommended low threshold value is 0.

2. Check the thermometer in equipment room to see if the actualtemperature is too high. If yes, take necessary cooling and venti-lation measures.

Alarm Impact 1. If the alarm is caused by unreasonable threshold configuration,service will not be affected.

2. If the alarm is caused by low room temperature, board opera-tion might be abnormal and board services might be interrupted.

198025860 Rack voltage is high




Alarm

Alarm Level Minor


Chapter 2 Alarm

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm 1. The configured threshold is unreasonable.

2. Actual voltage is too high.


1. In NMS Configuration Management interface, click Power BoardAlarm Parameters to view the upper threshold of rack voltage. Ifthe configuration is unreasonable, please modify it. For 48V powersupply, the recommended value of upper threshold is 57V; for 60Vpower supply, the recommended value is 72.

2. Find out which line voltage exceeds upper threshold by usingthe voltage index given in alarm details. Lower down the inputvoltage of this line.


2. If the alarm is caused by high voltage, board may work abnor-mally and board services may be interrupted.

198025861 rack voltage is low




Alarm

Alarm Level Minor

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm 1. Voltage value is under the low threshold.

2. The setting of the voltage detector is error.

3. Power input of a road may have been disconnected.


1. On NMS configuration management interface (power boardalarm parameters), check the lower limit of rack voltage. Modifythe threshold value if the previous configuration is unreasonable.For 48 V power, the recommended low threshold value is 40. For60 V power, the recommended value is 50.

2. Locate the specific line whose voltage is below low thresholdaccording to the voltage index listed in alarm Details. Increase theinput voltage of that line.


2. If the alarm is caused by low voltage, board may work abnor-mally and board services may be interrupted.



198025862 Humidity is high




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No


2. Actual humidity in equipment room is too high.


1. In NMS Configuration Management interface, click Power BoardAlarm Parameters to view the upper threshold of room humidity.If the configuration is unreasonable, please modify it. The recom-mended value of upper threshold is 90.

2. Check the hygrometer in equipment room to see if the actualhumidity is too high. If yes, take necessary dehumidifying mea-sures.


2. If the alarm is caused by high room humidity, board may workabnormally and board services may be interrupted.

198025863 Humidity is low




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No


2. Actual humidity in equipment room is too low.

3. Setting of the sensor is incorrect.


1. In NMS Configuration Management interface, click Power BoardAlarm Parameters to view the lower threshold of room humidity.If the configuration is unreasonable, please modify it. The recom-mended value of upper threshold is 90.

2. Check the hygrometer in equipment room to see if the actualhumidity is too low. If yes, take necessary humidifying measures.


Chapter 2 Alarm



2. If the alarm is caused by low room humidity, board may workabnormally and board services may be interrupted.

198025864 Fault in fan plug-in box




Alarm

Alarm Level Minor

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm 1. FAN module is not tightly inserted into the rack.

2. FAN module hardware is faulty.


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 alarmmight lead to excessively high rack temperature, result-ing in abnormal board operation and interruption of board services

198025865 Rack door alarm




Alarm

Alarm Level Minor

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm 1. The rack door is not closed.

2. Door control connection is incorrect.


1. Open and re-close the rack door to ensure that the rack dooris tightly closed.

2. Open the rack door to check the installation of door control.Ensure that the door access control is correctly installed and con-nected. Then close the rack door.



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

198025866 Smoke detected




Alarm

Alarm Level Minor

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm 1. The alarm device is faulty.

2. The smoke density in equipment room is too high.

3. Setting of the sensor is incorrect.


1. Quick find the origin of smog.

2. If there is no smog in the equipment room, replace the smogdetector.


Alarm Impact Services won't be affected, but there is a potential safety problem.

198025867 Infrared alarm




Alarm

Alarm Level Minor

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm 1. Heat source (such as animal/human) comes near.

2. Configuration of Infrared sensor is incorrect.

3. Infrared sensor is faulty.


1. Check if any animal or human comes near the infrared sensor.If yes, remove the heat source. If no, check the infrared sensorconfiguration. If appropriate, sensor sensitivity can be somewhatreduced.

2. The infrared sensor is faulty. Replace sensor.

Alarm Impact 1. If the alarm is caused by infrared sensor configuration error,system is not affected.


Chapter 2 Alarm

2. If the alarm is caused by infrared over threshold, be careful ofpotential safety hazard in the equipment room.

198025868 Lightning alarm




Alarm

Alarm Level Major

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm Outdoor unit or equipment damaged by lightening.


1. Check earthing connection.

2. Check lightning protection antenna.


Alarm Impact The board may work abnormally due to lightning stroke. Accord-ingly, board services will be interrupted.

198066064 Loss of DC power supplyto rack




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Circuit breaker has tripped.

2. No incoming DC supply from rectifier.


Is this shelf needed?

1. If yes, ensure that the atmosphere switch is closed and ALMindicator is normal.

2. If no, screen the function of monitoring atmosphere switch.In NMS Configuration Management interface, click Power BoardAlarm Parameters; then set the status of atmosphere switch to bescreened.




Alarm Impact This shelf can not be supplied with power. All boards on the shelfcan not work and board services are interrupted.

QoS Alarm198023296 Inter-board messagecommunication flow rate exceeds thealarm threshold

Alarm Type QoS Alarm



Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm The configured alarm threshold is less than the usual inter-boardcommunication traffic in input and output directions of the boardcontrol plane.


On NMS configuration management interface, check if the config-ured alarm threshold of communication traffic in input and outputdirections of the board control plane is too low. Recommendedvalue: 0xffffffff(4096M).

Alarm Impact No impact on user service.

198066069 The number of times ofsignaling data transfer exceeds theallowed threshold of the license




Alarm

Alarm Level Major

Disaster Alarm No

FrequentlyReported

Yes


Chapter 2 Alarm

Cause of Alarm 1.The number of allowed times of transfer is less than the actualdemand.

2.No proper license purchased.


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

198083042 IU PS traffic over loadalarm




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm IU PS traffic throughput exceed the threshold of license control.


Check if the whole throughput is over the provider's guaranteedbandwidth limit authorized by license.

Alarm Impact The traffic over the license threshold would cause packet loss andservice quality decrease.

198083043 IU CS traffic over loadalarm




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm IU CS traffic throughput exceed the threshold of license control.



Alarm Impact The traffic over the license threshold would cause user service ac-cess reject.



198083044 IU traffic over load alarm




Alarm

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm IU CS and PS traffic throughput exceed the threshold of licensecontrol.



Alarm Impact The traffic over the license threshold would cause CS user serviceaccess reject or PS service quality decrease.


C h a p t e r 3

Notification

Table of Contents198083017 RUB board has reached maximum number ofroutes............................................................................ 111198070002 Iu interface global reset notification .................. 111198070003 Iu interface resource reset notification............... 112198070004 RNC initiate Iu interface global reset failure noti-fication .......................................................................... 113198070005 RNC initiate Iu interface resource reset failure no-tification......................................................................... 113198070008 RNC and Node B are configured with differentCCPID............................................................................ 114198070009 Broadcast failure ............................................ 114198083025 Common Channel is abnormal .......................... 116198070010 FTP failure and file lost .................................... 117198070011 RNC alarm storage disc is full ........................... 118198083028 Performance file server unavailable ................... 118198083029 Unable to save Performance File ....................... 119198083019 MicroCode subsystem failed to get the table ofconfiguration .................................................................. 120198083026 MicroCode subsystem failed to handle DHCP mes-sage from other network .................................................. 122198083030 Bandwidth automatic adjustment is useless ......... 123198083032 TCP connect on IuBC interface is interrupted.................................................................................... 124198083033 The deviation of slave clock is too large. ............ 125198083034 External Clock of Slave lost notification.............. 125198083035 Transport Path Occupied BandWidth Over-load............................................................................... 126198083037 All Local Cell ID configured at RNC side are differfrom which on Node B side ............................................... 126198020291 Protocol stack process failed to initialize duringpower on........................................................................ 127198020802 Conflicting IP address in subnet. ...................... 127198020803 Conflicting MAC Addresses in Subnet ................. 128198020804 Failed to generate static ARP from IP ad-dress ............................................................................. 129198066065 SCTP Primary Path Set Failed ........................... 130198030016 Ethernet link OAM event .................................. 130198000576 Loss of Frame on Trunk ................................... 131198066050 MCC is faulty.................................................. 131198001600 CPU resets on a board ..................................... 132198017216 Error in MCS Multi-Core processor receiving con-figuration data from DBS .................................................. 132198018240 TCP Receives RST Packet ................................. 133198018241 TCP Connection Aborted .................................. 133198018242 MD5 Verification Failure ................................... 134198018243 Wrong MD5 Message Abstract........................... 134



198023106 Board Self-Check Failure.................................. 135198023107 The board initialization failure........................... 135198023617 Configuration file is unusable............................ 136198003138 FLASH device initialize failed ............................ 136198003394 Start daylight saving time ................................ 137198003395 End daylight saving time.................................. 137198005441 Port status on internal media planechanged. ........................................................................ 138198005448 485 seriel bus link between CLKG/PWRD and OMPis broken........................................................................ 139198026177 CLKG reference quality changed ....................... 139198026178 Clock work mode changed ............................... 140198005705 MCU resets for abnormities .............................. 140198005710 The result of base selection of sets chip ............. 140198005711 clock reference selection is being executed. ......... 141198005712 The manual select base will be run, please waitfor the result .................................................................. 141198005713 APC's RAM error ............................................. 142198005715 PP2S source switched...................................... 142198005717 The physical address information of the board isincorrect ........................................................................ 143198005716 Type B fault on board (GPS) phase-lock equip-ment ............................................................................. 143198005700 DSP resets for abnormities............................... 144198005701 Version Load Error .......................................... 145198019777 APS switch over occurred................................. 146198005188 UIM CS Changeover ........................................ 147198005192 Board's Work Mode Unsupported....................... 148198005193 Notification of the power-on status of the basicprocess .......................................................................... 148198005956 Board Version Error......................................... 149198005958 IDE Version Files Synchronization Informa-tion ............................................................................... 150198005961 OMP Version Check Information ........................ 150198005962 Patch version operate fail................................. 151198010560 No message response in the link for a longtime .............................................................................. 152198011840 M3UA user office status change ........................ 152198013888 ASP status changed ........................................ 153198013889 AS status changed .......................................... 154198013890 Sigtran error message received ........................ 154198013891 Sigtran notification message received ................ 155198013892 Allocate memory fail ....................................... 156198014144 Association establishment failed........................ 156198014145 Association restart .......................................... 157198025664 Abnormal Half-fixed Connection Changes ........... 158198008005 Memory file buffer overflow.............................. 159198002625 Process is deadlocked...................................... 159198002880 CPU occurs dead-loop...................................... 160198005718 Two master clock ports is directly con-nected ........................................................................... 160198005189 Notification of Active/Standby Changeover ......... 161198026176 Clock reference changed.................................. 161198020805 ARP detect failed ............................................ 162198020806 ARP detect that the static ARP is not match ......... 162198015168 AAL2 Path blocked by resetting process ............. 163


Chapter 3 Notification

198083017 RUB board hasreached maximum numberof routes




Notification

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm Too many route entries are configured in the routing table.

For a VTCD-type RUB, the routing table can contain at most 360entries. For a VTCD_2-type RUB, the routing table can contain atmost 1024 entries. The alarm is given when 90% capacity of therouting table is used.


1. Open the NMS Configuration Management interface to deleteunused routes from Static Routes.

2. Open the NMS Configuration Management interface to deletethe IP address of the unused port from Interface Configuration.

Alarm Impact 1. If the number of route entries does not exceed the capacity ofthe RUB routing table, no service will be affected.

2. If the number of route entries exceeds the capacity of the RUBrouting table, some routes will be missing.

1) If the missing routes are from RNC to Node B or CN, UE serviceswill fail to access this board.

2) If the missing routes are from RNC to other RNC NEs, inter-RNCUE services will fail to access this board. Meanwhile, the tick clockfor MBMS among relevant RNC NEs cannot be synchronized, whichwill reduce the quality of MBMS.

3. If the number of route entries exceeds the capacity of the RUBrouting table, the SLA diagnosis function from RNC to a relevantnetwork element will fail.

198070002 Iu interfaceglobal reset notification






Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. RESET message is sent by CN.

2. The signaling point of the office related to the CN is inaccessible.

3. Global reset is triggered by NMS.


On NMS fault management interface, view notification Detailswhere Alarm Reason is given. Locate the specific alarm handlingsuggestion according to the given reason. The handling sugges-tions that correspond to different reasons are described below.

1.CN reset.

1) RESET message is initiated by CN NMS. View CN NMS operationlog to see if the reset is initiated. If yes, no handling is necessary.

2) Check if transmission-related/board alarm occurs in the board.If yes, refer to the corresponding alarm handling suggestion. Re-lated alarms:

198066005 SCCP SSN is invalid



2.CN unaccessible. Check if transmission-related/board alarm oc-curs. If yes, refer to the corresponding alarm handling suggestion.Related alarms:

198066005 SCCP SSN is invalid



3.OMCR initiate IU reset. The alarm is caused by manual resetoperation. Check RNC NMS operation log to see if the reset oper-ation exists. If yes, no handling is necessary.

Alarm Impact The services that have been established are released. Access ofnew service is denied. Service access will be restored in 3 seconds.

198070003 Iu interfaceresource reset notification




Notification

Alarm Level Major



Disaster Alarm No

FrequentlyReported

No

Cause of Alarm RNC sends a RESET RESOURCE message.


Check if there is any of the following transmission-related alarms.If yes, follow the corresponding suggestions to handle it.

198066005 SCCP subsystem unavailable



Alarm Impact The resource resetting service is released.

198070004 RNC initiate Iuinterface global reset failurenotification




Notification

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm The CN fails to respond to the resetting request from the RNC.


Check the basic information in the MSC SERVER/SGSN tab on theNMS Configuration Management interface to see if "MCC and MNC"is consistent with that configured for the CN. If not, modify theconfiguration.

Alarm Impact New services will be rejected for 3 seconds.

198070005 RNC initiateIu interface resource resetfailure notification






Notification

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm The CN fails to respond to the resource resetting request from theRNC.


Check the basic information in the MSC SERVER/SGSN tab on theNMS Configuration Management interface to see if "MCC and MNC"is consistent with that configured for the CN. If not, modify theconfiguration.

Alarm Impact It has no impact on services.

198070008 RNC and Node Bare configured with differentCCPID




Notification

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm The CCP ID configured on the RNC side is different from that onthe Node B side.


1. Click Base Station Ground Resource Management > TransportLayer Management > SCTP stream configuration on the NMS Con-figuration Management interface, and then modify the CCP ID.

2. Click NE Information Configuration on the NMS ConfigurationManagement interface. Select the corresponding Node B and mod-ify its CCP ID in Node B port configuration.

Alarm Impact Neither CCP ID will be available during service establishments.

198070009 Broadcast failureAlarm Type Communication Alarm





Notification

Alarm Level Major

Disaster Alarm Yes

FrequentlyReported

Yes

Cause of Alarm 1. The system broadcast of the cell is configured incorrectly.

2. The transmission fails.


View alarm details on the NMS Alarm Management interface tocheck the alarm cause, which can help you easily find the corre-sponding handling suggestions.


1. Alarm cause: Failure in getting system information from data-base.

Check notification details, where "bySIBType" is given. For exam-ple, "SIB type = 1" means that obtaining SIB1 fails. In this case,check the Sib1-related parameters and make sure the configura-tion is correct and complete.

Different types of SIBs correspond to different configurations,which must be checked as follows:

1) SIB type = 1

On NMS configuration management interface (UE timers and con-stants information), check UE timers and counters in idle and con-nected status.

2) SIB type = 1

On NMS configuration management interface (UTRAN cell), checkURA ID in UTRAN cell global information.

3) SIB type = 1

On NMS configuration management interface (cell selection andreselection), check cell selection/reselection information parame-ters and cell access limit parameters.

4) SIB type = 1

On NMS configuration management interface (UTRAN cell), checkcommon transport channel parameters in SCCPCH and RACH.

2. Alarm cause: The system broadcast is beyond its capability.

Check if the Node B to which the faulty cell belongs generates anyof the following transmission-related alarms. If yes, follow thecorresponding suggestions to handle it.

1) IP Mode

Check to see if there is any of the following alarms according tothe association ID. If yes, follow the corresponding suggestions tohandle it.



2) ATM Mode

a. Bottom layer transmission fault








b. Unavailable PVC link


Related alarm: 198018944 PVC Fault

Alarm Impact The cell is unavailable and inaccessible, providing no service.

198083025 CommonChannel is abnormal




Notification

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. User plane resource initialization failure.

2. CCH setup failure at Node B side.

3. CCH configuration is deleted by OMCR.

4. The Bearer type of common transport channel is modified byOMCR.


View alarm details on the NMS Alarm Management interface tocheck the Alarm Reason, which can help you easily find the corre-sponding handling suggestions.


1. Alarm Reason: User plane resource initialization failure.

1) Click NE Information Configuration on the NMS ConfigurationManagement interface and select the corresponding Node B. Selectthe Path Configuration tab to check if all parameters, including theforwarding bandwidth, are correctly configured.

2) Click Path Group Configuration on the NMS Configuration Man-agement interface to check if all parameters are correctly config-ured.

2. Alarm Reason: CCH setup failure at Node B side.



Click Base Station Ground Resource Management on the NMS Con-figuration Management interface and select IP and Route Manage-ment to check the IP parameters. Make sure that at least one"COS" is selected.

3. Alarm Reason: CCH configuration is deleted by OMCR.

This alarm will be processed automatically by the system. The RNCwill initiate the process of common channel deletion. No manualhandling is required.

4. Others.

The system will automatically reestablish the common channel. Nomanual 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/PSservices initiated by the UE will fail.

2. If the S-CCPCH that carries PCH is unavailable, the paging func-tion of the system cannot be used and the CS/PS services initiatedby the CN will fail.

3. If the PRACH that carries RACH is unavailable, the UE cannotaccess this cell.

198070010 FTP failure andfile lost




Notification

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm The FTP channel between NMS and RNC NE is faulty.


Perform alarm synchronization on the NMS Alarm Management in-terface to obtain the latest alarm information from the RNC whenthe link between the NMS and the RNC is normal, so that the alarminformation of the NMS is consistent with that of the RNC.

Alarm Impact The NMS cannot obtain alarm files from the RNC and the alarminformation is lost. It has no impact on services.



198070011 RNC alarmstorage disc is full




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Disk is full.

2. Disk is faulty.


1. Delete unnecessary files from the hard disk or move them toan external storage device.

2. Replace the hard disk, or the board where the hard disk isinstalled.

3. Perform alarm synchronization on the NMS Alarm Managementinterface to obtain the latest alarm information from the RNC whenthe link between the NMS and the RNC is normal, so that the alarminformation of the NMS is consistent with that of the RNC.

Alarm Impact The RNC cannot save alarm files and the alarm information is lost.It has no impact on services.

198083028 Performance fileserver unavailable




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Performance file server unavailable.

2. Break in communication between RNC and PM server


1. Check the log server to see if the LogService runs normally.If not, restart the LogService by running "/startsys" under the"/home/zte/LogService/bin" directory.



2. Check if the control-plane communication between the logserver and the ROMP is normal by performing the following steps:

i. Open a terminal dialog box in the LINUX system.

ii. Enter the SHELL command "ping 128.0.31.1" to see if the pingtest is successful. If not, troubleshoot the control-plane commu-nication.

Alarm Impact The Logservice cannot receive performance files and the perfor-mance files are saved on the ROMP..

198083029 Unable to savePerformance File




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. The free disk space of the LogService is less than 100M.

2. The LogService version is incompatible with the ROMP version.

3. The LogService is unavailable and the free disk space of theROMP is less than 100M.

4. Board time is adjusted.

5. The Logservice is unavailable, and the PM files have alreadyexisted for over two hours.


Check alarm details to find the Failure cause during saving perfor-mance file, and handle the alarm accordingly.

1. If the Failure cause is "Logservice disk space less than 100M",delete unnecessary files from the Logservice disk to releaseenough space.

2. If the Failure cause is "Directory on Logservice is different fromthat on ROMP", it means the Logservice version is incompatiblewith the ROMP version. Use the correct Logservice version.

3. If the Failure cause is "Logservice is unavailable and the spaceof ROMP disk is less than 100M"

1) Delete unnecessary files from the ROMP disk to release enoughspace.

2) Handle it according to the suggestions given for the alarm"198083028 Logservice is unavailable".

4. If the Failure cause is "The session ends abnormally and theperformance file can not be saved", it means the board time hasbeen adjusted. In this case, no handling is required.



5. If the Failure cause is "The Logservice is unavailable, and thePM files have already existed for over two hours."the suggestionis given for the alarm "198083028 Logservice is unavailable".

Alarm Impact Either the LogService or the ROMP cannot save the performancefiles. Performance data will be lost.

It has no impact on services.

198083019 MicroCodesubsystem failed to get thetable of configuration




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Failed to get the information of the RUIB.

2. Failed to get the configuration of OMCB server.

3. Failed to get the configuration of signal dispatch table.

4. Failed to get the configuration of IP/UDP.

5. Failed to get the configuration of L2 table.

6. Failed to get the configuration of path information.

7. Failed to get the configuration of pathgroup information.

8. Failed to get the configuration of IUBC signal dispatch table.


On NMS alarm management interface, view notification Detailswhere Alarm Reason is given. Locate the specific handling sug-gestion according to the given reason. The handling suggestionsthat correspond to different reasons are described below.

1.Alarm Reason: Failed to get the information of the RUIB. OnNMS configuration management interface, check whether “BoardReassembling IP Fragments” is configured. If no, perform the cor-responding configuration according to network planning. Makesure to synchronize the configuration data at NMS and RNC NEafter configuration modification. Only after synchronization canthe configuration data take effect at RNC NE.

2.Alarm Reason: Failed to get the configuration of OMCB server.On NMS configuration management interface, check whether mas-ter OMP IP is configured. If no, perform the corresponding con-figuration according to network planning. Make sure to synchro-nize the configuration data at NMS and RNC NE after configuration



modification. Only after synchronization can the configuration datatake effect at RNC NE.

3.Alarm Reason: Failed to get the configuration of signal dispatchtable. On NMS configuration management interface (SCTP asso-ciation configuration), check whether the relevant office is con-figured. If no, perform the corresponding configuration accordingto network planning. Make sure to synchronize the configurationdata at NMS and RNC NE after configuration modification. Only af-ter synchronization can the configuration data take effect at RNCNE.

4.Alarm Reason: Failed to get the configuration of IP/UDP. On NMSconfiguration management interface (service IP for DSP), checkwhether the relevant office is configured in DSP service IP address.If no, perform the corresponding configuration according to net-work planning. Make sure to synchronize the configuration dataat NMS and RNC NE after configuration modification. Only aftersynchronization can the configuration data take effect at RNC NE.

5.Alarm Reason: Failed to get the configuration of L2 table. Makesure to synchronize the configuration data at NMS and RNC NEafter configuration modification. Only after synchronization canthe configuration data take effect at RNC NE.

6.Alarm Reason: Failed to get the configuration of path informa-tion. On NMS configuration management interface (path configu-ration), check whether the relevant office is configured. If no, per-form the corresponding configuration according to network plan-ning. Make sure to synchronize the configuration data at NMS andRNC NE after configuration modification. Only after synchroniza-tion can the configuration data take effect at RNC NE.

7.Alarm Reason: Failed to get the configuration of pathgroup infor-mation. On NMS configuration management interface (path groupconfiguration), check whether the relevant office is configured. Ifno, perform the corresponding configuration according to networkplanning. Make sure to synchronize the configuration data at NMSand RNC NE after configuration modification. Only after synchro-nization can the configuration data take effect at RNC NE.

8.Alarm Reason: Failed to get the configuration of IUBC signal dis-patch table. On NMS configuration management interface (IUBCdispatch configuration), check whether the dispatch informationis configured. If no, perform the corresponding configuration ac-cording to network planning. Make sure to synchronize the config-uration data at NMS and RNC NE after configuration modification.Only after synchronization can the configuration data take effectat RNC NE.

Alarm Impact The system impacts that correspond to different alarm causes aredescribed below.

1. Failed to get the information of the RUIB. The configurationinformation is used to reassemble the fragments of IP packets in-putted into the equipment. Lacking the configuration informationmay cause processing failure of fragments of IP packets. Ser-vice interruption might occur or service processing rate might slowdown.

2. Failed to get the configuration of OMCB server. Lacking theconfiguration information may paralyze OMCB function.

3. Failed to get the configuration of signal dispatch table. Lackingthe configuration information causes SCTP data transmission fail-



ure on the interface board. The service related to SCTP Protocolon this board is down.

4. Failed to get the configuration of IP/UDP. Lacking the config-uration information may cause processing failure of IUPS service,or processing failure of other data based on IP transmission.

5. Failed to get the configuration of L2 table. Lacking the config-uration information may cause communication failure within theequipment. All services on the board might be down.

6. Failed to get the configuration of path information. In the caseof ATM interface board, lacking the configuration information mayincur processing failure of the AAL2 data based on ATM AdaptationLayer Protocol, leading to interruption of IUB/IUCS/IUR servicesunder this office. In the case of IP interface board, lacking theconfiguration information may incur processing failure of IP packettraffic control, leading to interruption of all services under this of-fice.

7. Failed to get the configuration of pathgroup information. In thecase of ATM interface board, lacking the configuration informationmay incur processing failure of the AAL2 data based on ATM Adap-tation Layer Protocol, leading to interruption of IUB/IUCS/IUR ser-vices under this office. In the case of IP interface board, serviceis not affected.

8. Failed to get the configuration of IUBC signal dispatch table.Lacking the configuration information causes IUBC signal trans-mission failure on the interface board. The service related to IUBCsignal on this board is down.

198083026 MicroCodesubsystem failed to handleDHCP message from othernetwork




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. OMCB IP is unconfigured by RNC.

2. The remote IP address of PPP/MLPPP link is unconfigured.

3. Information of DHCP Client is unconfigured.




On NMS fault management interface, view notification Detailswhere Fail Cause is given. Locate the specific handling suggestionwhich corresponds to the listed cause. The handling suggestionsthat 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 “ManagerNode B IP” is configured. If no, add the configuration.

2.Fail Cause: Peer IP Address of PPP/MLPPP Link has not beenconfigured. On NMS configuration management interface (PPP pa-rameter), check if remote IP address is configured. If not, add theconfiguration.

3.Fail Cause: Information of DHCP Client has not been config-ured. Compare DHCP Client's Identifier Information with engineer-ing plan, and config corresponding DHCP Client's Information OnNMS configuration management interface.

Alarm Impact The system impacts that correspond to different notificationcauses are described below.

1. RNC OMCB IP to Node B has not been configured. Case 1 If NodeB has never fetched the OMCB channel configuration information(including OMCB SERVER IP address, OMCB gateway IP, and NodeB IP address) before notification occurs, OMCB channel of the NodeB would be blocked. Node B’s failure to fetch IP address wouldlead to its failure to get other configuration information. Thus theservice as a whole is affected. Case 2 Node B has fetched theOMCB channel configuration information (including OMCB SERVERIP address, OMCB gateway IP, and Node B IP address) before no-tification occurs. If there is no configuration modification, OMCBchannel would not be affected. If there is configuration modifica-tion before notification occurs, OMCB channel would be affectedin such a way that modified service configuration data fail to takeeffect 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. DHCPClient will not get Traffic Address, and service to the Client is bro-ken.

198083030 Bandwidthautomatic adjustment isuseless




Notification

Alarm Level Minor

Disaster Alarm No



FrequentlyReported

No

Cause of Alarm The intermediate equipment such as Router or Switch is out of ser-vice, all the packets will be lost at the brocken-down equipment,packet loss rate on this path is invariable. In this case, decreasethe available bandwidth is useless, so bandwidth automatic ad-justment does not be executed.


Check the intermediate equipment.

Alarm Impact Packet loss rate on this path is invariable, call loss might occur,and access success rate of PS service might decline.

198083032 TCP connect onIuBC interface is interrupted




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. The local IP address or remote IP address configuration is in-correct.

2. Interface board (GIPI) of local equipment is faulty.

3. Intermediate equipment or opposite equipments faulty.

4. The network cable connection is loose or disconnected.


1. On NMS configuration management interface, check local IPaddress, remote IP address and TCP connection mode. If the con-nection mode at local end is configured as client, the connectionmode at opposite end should be configured as server. Vice Versa.

2. On NMS configuration management interface, check protocolstack configuration at both ends. In the case of direct connec-tion, ensure that interface board addresses at both ends are in thesame network segment, and the next hop address is direct con-nect interface board address. In the case of not direct connection,ensure that the next hop address is the intermediate equipmentaddress.

3. Check the interface board (GIPI) for the Related Alarms. Per-form the recommended solution to process the possible alarms.

Related Alarms: 198066070 Board Offline or the CPU is in longperiod reset status

4. Telnet to the interface board. Set a destination IP and ping it.In the case of direct connection, ping the direct connect interfaceboard address. In the case of not direct connection, ping the inter-



mediate equipment. If response timeout, contact the equipmentprovider for solution.

5. Check the physical connection on IuBC interface. If the con-nection is loose or broken, unplug and plug the cable or replacethe cable. If port indicator is on, the physical link must be normal.

Alarm Impact The IuBC Broadcast is disabled.

198083033 The deviation ofslave clock is too large.




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm Clock crystal oscillator of Slave or Host is inaccurate. The inaccu-racy result in Clock Deviation between Slave and Host over thresh-old (default threshold is 36 sec/hr) .


Lock the faulty Slave.

Alarm Impact KPI Index of service in RNC will be low.

198083034 External Clockof Slave lost notification




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm External Clock of Slave Lost.


Lock the faulty Slave.



Alarm Impact KPI Index of service in RNC will be low.

198083035 TransportPath Occupied BandWidthOverload




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm Available bandWidth of transport path is less than occupied band-Width. Probable causes for the alarm include:

1.E1 link is broken.

2.Transmission quality of the transmission line is poor.

3.Intermediate equipment is faulty.


1.Check the E1 link.

2.Check the transmission quality of intermediate equipment.

Alarm Impact The available bandwidth to destination is less than occupied band-width. Some services would be released in this transport pathselectively to avoid transport path congestion.

198083037 All Local Cell IDconfigured at RNC side arediffer from which on Node Bside




Notification

Alarm Level Minor

Disaster Alarm No



FrequentlyReported

No

Cause of Alarm 1. The RNC is connected with other Node B incorrectly, not thewanted Node B.

2. The radio resource data configured at RNC side and Node B sideis inconsistent.


1Check if the RNC is connected with Node B correctly on Iub inter-face. If not, please reconnect RNC and Node B, and synchronizethe configuration data to Node B. 2Check if the radio resource dataconfigured at RNC and Node B is consistent. If not, please modifythe radio resource data correctly, and synchronize the configura-tion data to RNC and Node B.

Alarm Impact All cell belong to the Node B can not be established.

198020291 Protocol stackprocess failed to initializeduring power on




Notification

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm Physical memory is insufficient


Ensure that the actual capacity of the physical memory is morethan 1GB.

Alarm Impact RPU board will reboot automatically after 10 seconds.

198020802 Conflicting IPaddress in subnet.




Notification

Alarm Level Major



Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. This network port is configured with the same IP address (in-cluding the virtual address in the same network segment) as an-other host in the local network.

2. The peer-end switch that connects with this network port hasa loop.


When an IP address conflict occur, the NMS will display the con-flicted IP address. Meanwhile, the 5-tuple information of the con-flicted local port, as well as the conflicted MAC address of the ex-ternal device, can be detected.

1. Click Interface Configuration on the NMS Configuration interfaceto check the local interface address. Modify the local interfaceaddress or the IP address of the conflicted external device.

Refer to the corresponding equipment maintenance manual tolearn how to query the IP address of external device.

2. The switch connected with the local port must have a loop ifthe following two conditions are satisfied:

1) "198020802 Conflicting IP Address" and "198020803 Conflict-ing MAC Address in Subnet" concur;

2) Even though the local port IP address is changed, the two alarmsstill exist.

In this case, check whether there is a cable that connects bothports of the peer-end switch. If yes, remove the cable.

Alarm Impact Board operation is normal. Communication network is faulty. Allservices on this port are down.

198020803 Conflicting MACAddresses in Subnet




Notification

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. The MAC address of this port is the same with another MACaddress in the direct connect network.

2. Loop exists in the remote switch connected with this port.


When an MAC address conflict occurs, the NMS will display theconflicted MAC address. Meanwhile, the 5-tuple information of the



conflicted local port, as well as the conflicted MAC address of theexternal device, can be detected.

1. Modify the MAC address of the local port or the conflicted MACaddress of the external device.

Find the conflicted local port according to the displayed 5-tuple in-formation. Click Interface Configuration on the NMS Configurationinterface and select "MAC Address" to check and modify the MACaddress of the local port.

Refer to the corresponding equipment maintenance manual tolearn how to query the MAC address of the external device.

2. The switch connected with the local port must have a loop ifthe following two conditions are satisfied:

1) "198020802 Conflicting IP Address" and "198020803 Conflict-ing MAC Address in Subnet" concur;

2) Even though the local port IP is changed, the two alarms stillexist.

In this case, check whether there is a cable that connects bothports of the peer-end switch. If yes, remove the cable.

Alarm Impact Board operation is normal. The notification leads to packet lookupfailure in Layer 2 forwarding table. Then packet loss occurs andall services related to this port will be down.

198020804 Failed togenerate static ARP from IPaddress




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm Failed to generate static ARP from the newly added IP address,be-cause the number of static ARPs which generated by IP hasreached the maximum.


Delete some proxy addresses configured for virtual ports andre-configure IP address within the limit of static ARPs.

Alarm Impact The external device failed to communicate with the IP address fromwhich no static ARP is generated.



198066065 SCTP PrimaryPath Set Failed




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm The remote IP of the SCTP primary path configured at applicationlayer is not included in the local address list of SCTP at oppositeend


On NMS fault management interface, view notification Details,where information of association ID and the primary path remoteIP address is given. If the primary path remote IP address listedin notification Details is selected as the primary path, follow thesteps below at opposite end.

1. Add the IP as an interface address at opposite end.

2. Add the "primary path remote IP address" given in notificationDetails into the local IP address list of the relevant SCTP.

Alarm Impact This notification informs user of the update failure of SCTP primarypath. The primary path currently in use is not affected. No impacton service.

198030016 Ethernet linkOAM event




Notification

Alarm Level Major

Disaster Alarm No

FrequentlyReported

Yes

Cause of Alarm The number of wrong frames or wrong symbols exceeds thethreshold.


Check Ethernet linkreceiver and transmitter of link.

Alarm Impact Ethernet links can not transmit data credibly.



198000576 Loss of Frameon Trunk




Notification

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm Since frequency difference might exist between trunk line clockand local receive clock, the trunk receive clock is not synchronouswith the transmit clock.


Check the clock synchronization status at both sides. If the statusis unsynchronized, check if LOL-related (loss of lock) alarm occursin clock board. If yes, refer to the corresponding alarm handlingsuggestion.

Related alarms:




Alarm Impact Momentary fault occurs to trunk data service or signaling channel.If fault occurs repeatedly, CS/PS service might become unstable.Otherwise, service is not affected.

198066050 MCC is faultyAlarm Type Equipment Alarm



Notification

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm Check SPB/SPB_2/IWFB if they are working normal.


1. Unplug the board for 5 seconds, and plug it again after a fulldischarge.




Alarm Impact All MCC channels cannot transmit or receive data.

198001600 CPU resets on aboard




Notification

Alarm Level Major

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm 1. User request CPU reset.

2. Board has reset itself due to fault.


1. Check the NMS operation log to see whether there is a manualreset record. If yes, no handling is necessary.


Alarm Impact The relevant services or communication links will be interruptedor disconnected. This alarm will be recovered after the board ispowered on normally.

198017216 Error in MCSMulti-Core processorreceiving configurationdata from DBS




Notification

Alarm Level Major

Disaster Alarm No

FrequentlyReported

Yes

Cause of Alarm 1.The configuration data from DBS are exceptional.

2.Failure in adding a vital data table




Check the data configuration, if there is a configuring error, correctit and reboot the board.

Alarm Impact It may cause packet forwarding problem since some vital data ta-ble is absent.

198018240 TCP ReceivesRST Packet




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1.The peer end initiates tcp connection resetting and sends a RSTpacket.

2.The peer end receives invalid tcp connection and returns a RSTpacket.


Check if there is severe packet loss in physical link (It can bechecked by ping command), and handle physical link faults.

Alarm Impact The corresponding connection aborts.

198018241 TCP ConnectionAborted




Notification

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. The RNC is connected with other Node B incorrectly, not thewanted Node B.

2. The radio resource data configured at RNC side and Node B sideis inconsistent.




1Check if the RNC is connected with Node B correctly on Iub inter-face. If not, please reconnect RNC and Node B, and synchronizethe configuration data to Node B. 2Check if the radio resource dataconfigured at RNC and Node B is consistent. If not, please modifythe radio resource data correctly, and synchronize the configura-tion data to RNC and Node B.

Alarm Impact All cell belong to the Node B can not be established.

198018242 MD5 VerificationFailure




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm MD5 verification is not set for packets in application layer.


Check MD5 encrypted option of the two ends of application layer.If an end does not set with MD5 encrypted option, then set MD5encrypted option for this end.

Alarm Impact Application layer communication failure.

198018243 Wrong MD5Message Abstract




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm When application layer is receiving messages, MD5 cryptographickeys set on both ends are inconsistent.


Check if MD5 cryptographic keys set on both ends are the same.

Y->Please contact ZTE Corporation.



N->Set the same MD5 cryptographic keys for both ends of appli-cation layer and finish the alarm handling.

Alarm Impact Application layer communication failure.

198023106 BoardSelf-Check Failure




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm Board hardware is faulty.


Replace board.

Alarm Impact The board fails to power on possibly, and the service or communi-cation link related to this board is down.

198023107 The boardinitialization failure




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No



Replace board.

Alarm Impact The board fails to power on and operate, resulting in UE accessfailure and interruption of ongoing services.



198023617 Configurationfile is unusable




Notification

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm During the process of system power-on,the DAT file obtained fromVMM is unusable or the txt file which saves configuration data isunusable.


On NMS fault management interface, view the alarm details, whichgive the Additional Reason.

1.If it's the DAT file error, then we need to reload the file from VMMand switch to the new file.

2.if it's the TXT file error,then take the following step:

1)Get the TXT file from "/DOC0/DATA1" directory at RPU with FileManager method.

2)Open the TXT file and delete line "[CRC_DATFILE]=" and"[CRC_TXTFILE]=".

3)Transmit the modified TXT file.

4)Reboot RPU.

Alarm Impact 1. DAT file is unusable This error will make the saved data un-restorable and unconfigurable if the configured data was saved inTXT file.

2. TXT file is unusable This error will make the saved data un-restorable.

198003138 FLASH deviceinitialize failed




Notification

Alarm Level Major

Disaster Alarm Yes



FrequentlyReported

No

Cause of Alarm The flash on the board is damaged.


Replace the relevant boards.

Alarm Impact 1. For a single OMP board, the flash fault may cause board startup failure. For both master/slave boards with flash fault the entiresystem may have start up failure.

2. For other boards, the board may start up normally with outimpact on its service.

198003394 Start daylightsaving time




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm Daylight saving time activated, clock changed accordingly



Alarm Impact No impact

198003395 End daylightsaving time




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm Daylight saving time is de-activated and the system is back tonormal country clock





Alarm Impact No impact

198005441 Port statuson internal media planechanged.




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Connection between UIM/GUIM and GLI is faulty.

2. Board is faulty.


On NMS fault management interface, view notification Detailswhere information of "Port status" is given.

1.If the port status is "Master port invalid status" or "Master portabnormal", refer to the following handling suggestions.

i. Reconnect the cable between UIM/GUIM and GLI.

ii. Replace the optical module or cable used for the connectionbetween UIM/GUIM and GLI.

iii. Replace UIM/GUIM board.

iv. Replace GLI board.

2.If the port status is others, no handling is necessary.

Alarm Impact The impact varies depending on the "Port status" given in notifi-cation Details.

1. If the port status is "Master port invalid status" or "Master portabnormal", 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 beinterrupted.

2.If the port status is "Slave port invalid status" or "Slave portabnormal", service will not be affected. However, the potentialhazard will emerge once master/slave switching occurs

3.If the port status is others, service will not be affected.



198005448 485 seriel buslink between CLKG/PWRDand OMP is broken.




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. 485 communication is interrupted.

2. The board is abnormal.


1. Unplug and plug the 485 cable.

2. Replace the 485 cable.


Alarm Impact The configured clock reference/environment threshold fails to takeinto effect. There is no impact on services.

198026177 CLKG referencequality changed




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm Clock quality of the CLKG board has changed.


Check the quality of external clock source.

Alarm Impact System could not get the needed clock.



198026178 Clock workmode changed




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm The clock work mode of the CLKG board has changed.



Alarm Impact System could not get the needed clock.

198005705 MCU resets forabnormities




Notification

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm MCU Hardware is faulty.


Replace the board.

Alarm Impact CLKG_2 board is faulty.

198005710 The result ofbase selection of sets chip






Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm After manual base switchover, man-machine command, or press-ing panel button, SETS chip performs base locking operation (atmost for 2 minutes). This notification is to inform the user of theoperation result of manual base selection



Alarm Impact None.

198005711 clock referenceselection is being executed.




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm If previous operation about clock reference selection doesn't finishand relevant result is not given yet, the system will screen anynew attempt to manually select clock reference. And in this case,this notification is declared.



Alarm Impact No impact on service.

198005712 The manualselect base will be run,please wait for the result






Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm The notification is declared after selecting base via panel button,to remind user that the base selection is in process and to requestuser to wait for the operation result



Alarm Impact None.

198005713 APC's RAMerror




Notification

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No



Replace board.

Alarm Impact The board where RAM is located is down. ATM cell fails to be for-warded, and all board services are interrupted.

198005715 PP2S sourceswitched




Notification

Alarm Level Minor

Disaster Alarm No



FrequentlyReported

No

Cause of Alarm PP2S (Pulse Per 2 Seconds) source is changed at both system clockand GPS receiver sides.


GPS-side PP2S has a higher priority. If PP2S is switched over fromGPS-side to system-side, check the GPS receiver and antenna feedstatus.

Alarm Impact None.

198005717 The physicaladdress information of theboard is incorrect




Notification

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. The DIP switch setting changes

2. The board is not inserted in position


1. Reset the board. After the resetting, the board re-calculatesand sets the MAC address according to the DIP switch.

2. Insert the board tightly. Or, unplug and plug the board.

Alarm Impact The board fails to start up, or control plane communication is ab-normal. As a result, users cannot gain access and existing servicesare interrupted.

198005716 Type B fault onboard (GPS) phase-lockequipment




Notification



Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm Type B Fault on Board (GPS) Phase-lock Equipment are generatedby singlechip processor. Probable alarm causes include antennafeeder short circuit or open circuit, poor quality of received satellitesignals or difficulty in receiving satellite signals, and large phasedifference of 10M OCXO assistant phase control.


Check the antenna feeder input circuit of ICM board to ensure thatthe board can best receive GPS signal source. The checking itemsinclude:

1) The position of the receiving antenna. The antenna should beinstalled in an open area, far away from high buildings and clearfrom shades. The effective visibility angle of the antenna shouldbe greater than 150 degrees.

2) The connection of the power splitter and front panel. The powersplitter and the front panel connector should be in good contactand properly connected.

Alarm Impact Class B fault has no impact on system clock and services in 48hours. After 48 hours, the fault might lead to system clock offsetand system synchronization failure. When GPS signal is poor, thealarm will be repeatedly declared/restored. As long as the alarmpersists for no more than 48 hours, system clock and service willnot be affected. When system clock loss/offset occurs, its subse-quent impact on service is described below.

1.For TDM transmission, all links based on the TDM transmissionmedium (including the transmission link currently in service for UEand cell transmission link) are affected. Packet loss might occur onthese links, leading to degradation of service quality. In the caseof serious packet loss, service interruption and handover failurewill occur. Even worse, the cell might be out of service.

2.For non-TDM transmission (for example, IP transmission), Iubinterface service is affected, while Iur interface and Iu interfaceservices are not affected. The clock that Node B derives from RNCvia IEEE1588 is inaccurate. When RNC clock frequency offset isno more than 0.05 ppm, Node B synchronization will not fail, butsuccess rate of inter-RNC inter-Node B soft handover might fall.When RNC clock frequency offset exceeds 0.5 ppm, Node B willfail to lock the clock. In this case, Node B will oscillate freely andsuccess rate of inter-Node B soft handover might fall.

198005700 DSP resets forabnormities




Notification



Alarm Level Major

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm 1. DSP chip is faulty.

2. Board is faulty.


DSP resets automatically and abnormally.

1.If power-on is normal after DSP reset, the board can be restoredto normal state.

2.If DSP resets repeatedly, replace the board or subcard.

Alarm Impact DSP is unavailable during reset, but will be restored to normalstate after reset. During reset, cells on the DSP are out of service,services on the DSP are interrupted, and call loss increases.

198005701 Version LoadError




Notification

Alarm Level Major

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm The equipment is abnormal in the process of version loading, whichfalls into three cases.

1. The equipment fails to fetch the needed version.

2. Version loading to chip fails.

3. Chip hardware is faulty.


On NMS fault management interface, view notification Detailswhere "Loading corresponding alarm information" is given. Lo-cate the corresponding handling suggestion based on the giveninformation.

1. Any of the following items displayed by "Loading correspond-ing alarm information" indicates that the chip fails to obtain theneeded version. On NMS software management interface, checkthe configured version for the chip and version status. Ensure thatthe needed version is configured for the chip and the version is ac-tivated.

i. DSP6416 No.d : No Version Information

ii.DSP5402 No.d : No Version Information

iii. MC fail to get version information



iv. OCT6100 fail to get version information

v. M82620 : Index = d fail to get version information

2. If information other than the items listed above appears, referto the following handling suggestion.

i. Reset board.

ii. Replace DSP subcard.

iii.Replace board.

Alarm Impact 1. Microcode version loading fails, leading to repeated board resetand interruption of board services.

2. Firmware/single-chip computer version loading fails, leading toabnormal 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 lossincreases.

198019777 APS switch overoccurred




Notification

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Optical interface is faulty such as LOS/SF/SD alarm.

2. In inter-board backup mode, one of the following events occurs.

i. Input clock lost

ii. Inner HW/LVDS alarm

iii. Inner media plane port alarm

iv. ENUM open (board not properly inserted)

v. Board reset (the board where the working optical interface islocated)

3. Changeover operation is initiated by the opposite end.

4. In recovery mode, fault recovery time at optical interface ex-ceeds 5 minutes.

5. APS changeover request/clearance is initiated by NMS.


View operation & maintenance log to see whether there is arecord, indicating an operator manually initiates APS changeoverrequest/clearance. If yes, no handling is necessary. If no, check



whether there is one of the following alarms. If yes, please solvethe problem according to corresponding handling suggestions.

Related alarms:


198005396 Exceptional Internal Media Plane Communication

198005378 Board HW Error

198005635 The board is not plugged firmly.

Alarm Impact During APS changeover process, the link is interrupted for 10 ~50 ms. Few packets may be lost, but services won't be affected.

198005188 UIM CSChangeover




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Optical module signal loss occurs.

2. Board input clock loss occurs.

3. Bit error rate at the optical interface is high.

4. Lock loss occurs to the phase-locked loop.

5. Bit error rate on the master/slave interconnecting link of GUIMboard is high.


Check if the following alarm occurs in local/opposite board. Ifyes, refer to the corresponding alarm handling suggestion. Re-lated alarms:

198001286 Loss of Clock When Input to Board


198005646 Phase-lock Loop Unlock

Alarm Impact No impact on service.



198005192 Board's WorkMode Unsupported




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. The configured board backup mode is unsupported

2. FPGA is unloaded, leading to setting failure of board workingmode.


1. Check the configuration of board backup mode. If the config-ured backup mode is not supported by the board, modify config-uration or replace the board with one that supports such configu-ration.

2. Unplug and plug board. Reload FPGA version.

Alarm Impact Board master/slave backup function is disabled.

198005193 Notification ofthe power-on status of thebasic process




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Board power-on is successful.

2. Board power-on fails or expires.


On NMS fault management interface, view notification Detailswhere information of power-on status ("Board poweron success-ful/failed/timeout") is given. Locate the corresponding handlingsuggestion based on the given information. The handling sugges-



tions that correspond to different power-on status are describedbelow.

1. Board poweron successful/failed/timeout: Poweron successfulNo handling is necessary.

2. Board poweron successful/failed/timeout: Poweron timeout En-sure that the board loads the proper version. The boards in a NEmust use the version of the same version No..

3. Board poweron successful/failed/timeout: Poweron failed En-sure that the board loads the proper version. The boards in a NEmust 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 willbe unavailable.

198005956 Board VersionError




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. A board is in the slot which is not configured with any board.

2. Board version is unconfigured.

3. Board version has been configured, but version file does notexist or is damaged.


1. On NMS configuration management interface (rack), view racklayout. Check if the slot is configured with any board. If no boardconfiguration exists, unplug the board in the slot.

2. On NMS fault management interface, view notification Detailswhere "Version type of abnormal board" is given. Load and acti-vate the version on NMS software management interface accordingto the given "Version type".

Alarm Impact The board fails to obtain version, leading to abnormal board oper-ation and access failure of board services.



198005958 IDE VersionFiles SynchronizationInformation




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm Synchronization of master/slave OMP version files occurs.


On NMS fault management interface, view notification Detailswhere "Synchronization information" is given.

1. If synchronization information is "Failed to obtain file recordduring synchronization" or "Synchronization failed", find the nameof the version file in notification Details. According to the given filename, locate on NMS software management interface the corre-sponding version configuration in the version file database. Reloadthe version file to RNC NE. Delete the version file if it is not in use.

2. If synchronization information is others, no handling is neces-sary.

Alarm Impact 1. IDE version file synchronization occurs between master andslave OMP (ROMB board). Service will not be affected by synchro-nization result.

2. In the case of synchronization failure, partial loss of version filewill occur to slave OMP

198005961 OMP VersionCheck Information




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No



Cause of Alarm The version file in software version configuration does not exist inRNC NE.


On NMS fault management interface, view notification Detailswhere "Version file name" is given. According to the givenfile name, locate on NMS software management interface thecorresponding 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 beaffected.

2. If the non-existent version file is the activated version, thecorresponding board will fail to fetch version during powering-on,leading to service access failure. This rarely happens.

198005962 Patch versionoperate fail




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Patch version file and CPU version file do not match.

2. Patch version file does not exist in RNC NE.

3. The patch version file related to the patch does not exist in RNCNE.


1. If the patch version is not needed, delete the correspondingversion configuration on NMS software management interface.

2. If the patch version is needed, locate on NMS software man-agement interface the version configuration of patch version fileand related patch version file in the version file database. Reloadthe version files to RNC NE.

Alarm Impact Patch version activation fails. New functions of the patch versionare unavailable. No impact on service.



198010560 No messageresponse in the link for along time




Notification

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm Bottom layer link quality is poor, there is no message response forthe link for a long time.


1. Check if physical connection works normally.

2. Check NMS alarms/notifications to see whether there existsphysical transmission alarm(s) /notification(s) that occurred si-multaneously with this alarm. If yes, refer to the correspond-ing alarm/notification handling suggestion. Alarms/Notificationsrelated to physical transmission are listed below, with respect toaccess mode.

1) Fiber Access Mode



198066048 SDH/SONET:Excessive Error Code


2)E1 Access Mode

198005647 High Error Rate at E1 Bottom Layer



198000576 Trunk Slide

Alarm Impact Related link will be interrupted and cannot bear service.

198011840 M3UA useroffice status change






Notification

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. User configuration of this office is changed.

2. Bottom-layer links are unavailable.

3. The signaling network management message from oppositeend is received.


1. Check whether link interruption alarm occurs to the link/asso-ciation. If yes, refer to the corresponding alarm handling sugges-tion. Related alarms:

198066011 MTP3 link unavailable


2. On NMS configuration management interface, check if the M3UAuser is configured in the relevant office. If no, add the configura-tion.

3. Locate the cause for office status change at opposite end.

Alarm Impact If M3UA user office status changes from accessible to inaccessible,reception and sending of messages from/to the office fail. Accessof new services under the office fails, and abnormal release of theongoing service occurs. If M3UA user office status changes frominaccessible to accessible, the system will return to normal state.

198013888 ASP statuschanged




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Association status is changed.

2. ASP operation is performed at opposite end.

3. ASP operation is performed in dynamic data management atlocal end.


1. Check whether association interruption alarm occurs. If yes,refer to the corresponding alarm handling suggestion. Relatedalarm:




2. Activate the ASP in dynamic data management.

3. Check whether ASP operation is performed at the opposite end.

Alarm Impact If this notification and the alarm of "198066014 M3UA office in-accessible" are declared at the same time, access failure of newservices under this office and abnormal release of ongoing serviceswill occur. If merely this notification is declared, service will notbe affected.

198013889 AS statuschanged




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Association status is changed.

2. ASP operation is performed at opposite end.

3. ASP operation is performed in dynamic data management atlocal end.


1. Check whether association interruption alarm occurs. If yes,refer to the corresponding alarm handling suggestion. Relatedalarm:


2. Activate ASP under the AS in dynamic data management.


Alarm Impact If this notification and the alarm of "198066014 M3UA office in-accessible" are declared at the same time, access failure of newservices under this office and abnormal release of ongoing serviceswill occur. If only this notification is declared, service will not beaffected.

198013890 Sigtran errormessage received






Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

Yes

Cause of Alarm 1. AS configuration is wrong.

2. Protocol versions used at both sides are different.


1. Check AS configuration to see whether the configured trafficmode at both sides are consistent. If no, modify configuration tokeep consistency.

2. APP server AS ID configuration must meet the following require-ments. If ASP is configured for local end, SGP should be configuredfor Opposite end. Vice versa. If IPSP client is configured for lo-cal end, IPSP server should be configured for opposite end. ViceVersa.

3. Activate the ASP in dynamic data management.

4. On NMS configuration management interface (AS configura-tion), check if routing context and routing context ID are config-ured. Ensure that the routing contexts configured at both endsare the same.

5. On NMS configuration management interface, check whetherthe local ASP in service for AS is configured. If no, add the con-figuration.

6. Check the protocol versions used at both sides. Ensure that theprotocol versions are the same.

Alarm Impact The corresponding AS fails to be activated, making M3UA officeinaccessible. Reception and sending of message from/to the officefail. Access of new services under the office fails.

198013891 Sigtrannotification messagereceived




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

Yes



Cause of Alarm 1. The broken association leads to insufficiency of the number ofASP in service for AS.

2. Release of ASP in dynamic data management leads to insuffi-ciency of the number of ASP in service for AS.


1. On NMS configuration management interface (AS configura-tion), query ASP-related associations. Check whether interruptionalarm occurs in the association(s). If yes, refer to the correspond-ing alarm handling suggestion. Related alarm:


2. Reactivate ASP in dynamic data management.


Alarm Impact The number of ASP in service for AS is insufficient. If traffic isheavy, congestion or packet loss might occur, leading to call lossor increasing PS call access failures. Otherwise, service is not af-fected.

198013892 Allocate memoryfail




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm Memory is insufficient, that result in dynamic memory allocationfailure when the processor is is powered on.


1. Enlarge memory capacity and then restart the board.

2. If Application Server/Application Server Process is not config-ured on this board, then the alarm should be ignored.

Alarm Impact If Application Server/Application Server Process is not configuredon this board, system will not be affected. Or else process will beunstable.

198014144 Associationestablishment failed






Notification

Alarm Level Major

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm 1. Association configuration at both sides is inconsistent.

2. No less than two associations are configured with same localaddress and port, but with different protocol types.

3. Interface board IP address is wrong, or physical link is down.


1. On NMS configuration management interface, check associa-tion configuration at local end and opposite end. Checking itemsinclude local IP address, local port No., remote IP address, remoteport No., and application property of SCTP association. If the as-sociation at local end is configured as client, the association atopposite end should be configured as server. Vice Versa.

2. At local end, check whether the associations configured withdifferent protocol types have the same local IP address and localport No.. If yes, perform configuration modification to differentiatethe local IP address and local port No. of these associations.

3. Check protocol stack configuration at both ends to see if in-terface board addresses are in the same network segment. If no,modify configuration to put two addresses in the same networksegment.

4. Ping the opposite-end interface board address to see if thenetwork cable or other intermediate link is faulty. Replace thecable if ping fails.

Alarm Impact If several association links are available to the destination office,service will not be affected by establishment failure of one associ-ation. In the case of heavy traffic, congestion of available associ-ation(s) might occur, leading to upper layer call loss or increasingPS call access failures. If merely one association link is available tothe destination office, the office might become inaccessible. Re-ception and sending of messages from/to the relevant office fail.Access of services under this office fails.

198014145 Associationrestart




Notification

Alarm Level Minor

Disaster Alarm No



FrequentlyReported

No

Cause of Alarm The local end receives a link creation request but detects no linkbreak,and the association restarts.Probable causes for the alarminclude:

1.Relevant board at peer end resets.

2.The Association link is reestablished at peer end.


No handling is necessarywait association to restart

Alarm Impact None.

198025664 AbnormalHalf-fixed ConnectionChanges




Notification

Alarm Level Major

Disaster Alarm No

FrequentlyReported

Yes

Cause of Alarm 1.Abnormal jitter occurs to the line clock of the shelf where theboard is located.

2.The switching chip of the board is faulty.


1.Check alarms and notifications to see if the alarm(s)/notifica-tion(s) related to input clock exist(s).Related alarm(s) and notifi-cation(s) are listed below.

198026116 CLKG PP2S Output Clock Lost




198026133 Clock Output Loss

2.Replace the faulty board.

Alarm Impact TMD channel is interrupted momentarily, which might have a mi-nor impact on service.



198008005 Memory filebuffer overflow




Notification

Alarm Level Warning

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm The transferred data records exceed the maximum capacity of thetable, and the capacity of the receiver memory file buffer is insuf-ficient.


Delete the excessive data records of the false table.

Alarm Impact If the board is powering on, the excessive data records (beyondtable capacity) are discarded, otherwise the synchronization willbe aborted.

198002625 Process isdeadlocked




Notification

Alarm Level Major

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm Maybe some resource ,such as semaphore, is deadlocked.


Note down the alarm information and contact ZTE Corporation.

Alarm Impact The process will never be scheduled, or timely resource releasefails, which results in resource exhaustion.



198002880 CPU occursdead-loop




Notification

Alarm Level Major

Disaster Alarm Yes

FrequentlyReported

No

Cause of Alarm There exist dead loops in the processes or the system tasks.


The board will restart automatically when this alarm occurs. Thealarm will automatically disappear after restart.

Alarm Impact The process or task of low priority level fails to be scheduled.

198005718 Two masterclock ports is directlyconnected




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm The port is configured as a master clock port in synchronous Eth-ernet, two master clock ports is directly connected.


If users do not want the other side to recover clock from this SyncEport, it is normal.

Otherwise, it maybe has a mistake on network connecting. If itis normal, there is no need to handle; if it is network connectingmistake, there is need to reconfigure the clock port or reconnectthe port.

Alarm Impact If it is normal, then there is no impact, if it is network connectingmistake, then the port can not synchronize to the connected mas-ter clock port.



198005189 Notification ofActive/Standby Changeover




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm It is hardware system fault. The CS domain of the UIM switchesover due to artificial operation.


1. Analyze the switchover reason according to the additional in-formation about the alarm .If it is not because of the system faultbut due to control of MML command at the background or causedby non-active/standby changeover, or the standby board does notexist physically, nothing would be done for this alarm.

2. If it is because of the system fault, eliminate those alarmsfirstly.

Alarm Impact The board whose changeover fails will reset automatically.

198026176 Clock referencechanged




Notification

Alarm Level Warning

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm The currently locked clock reference has changed.


No need to handle.

Alarm Impact System could not get the needed clock, which will cause processingabnormity related to the clock.



198020805 ARP detectfailed




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

Yes

Cause of Alarm When the switch of the ARP detecting enabled, CE can send ARPrequest packet with the ARP's IP periodically, if CE can not receivethe ARP respond packet during the set time, CE will report thisalarm information.


1. Please check the device's IP address configuration of the peerend.

2. Please check physical link.

3. Please check the exchanger's VLAN configuration.

Alarm Impact The communication will be interrupted possibly.

198020806 ARP detect thatthe static ARP is not match




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm When the switch of the ARP detecting enabled, CE can send staticARP request packet with the static ARP's IP periodically, if CE re-ceives the ARP respond packet whose MAC or dot1q encapsulationis not the same as static ARP's during the set time, CE will reportthis alarm information.


1. Please check remote device's MAC address.

2. Please check the switch VLAN configuration.

Alarm Impact The communication will be interrupted possibly.



198015168 AAL2 Pathblocked by resetting process




Notification

Alarm Level Minor

Disaster Alarm No

FrequentlyReported

No

Cause of Alarm The adjacent node doesn't has the same path.


You can unblock the Path by adding the same path on the adjacentnode.






Figures





Tables


Documents

ZTE RNC Alarm and Notification Handling Reference