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 operators 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.

Alarm

Alarm Property

Alarm Code

Alarm code is the identifier which differentiates alarms.

Alarm code is defined by a 32-bit field indicating the specific 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.

Notification

Notification 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 Alarm

198083003 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.

198001792 SDH/SONET fault

198066047 Abnormal status in SDH/SONET

198005639 High Error Rate of Optical Interface

198000002 Signal Loss of Optical Module

3. Check the operation and maintenance log in the NMS to 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.

Optical connector is polluted.

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 DSPs. 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




zte rnc alarm and notification handling reference

Documents